YuppieScum

Damn - just re-read your original post. How are you incresing the FSB? Where is the BIOS option? I've got a P6DBS (same as your mobo but with SCSI) and ver 2.2 BIOS, and I don't have an option to up the FSB... Also, regarding SoftFSB, you'll need to take your machine apart, and look for the 20 (or so) pin DIL chip on the mobo...

I have this problem if I don't stop the "distributed.net" RC64 client first. Ensure that nothing "odd" is running before trying again...

You might try SoftFSB - it does on-the-fly reprogramming of the FSB speed-controlling chip. However, increasing the FSB also increases the bus speed of the mobos PCI and AGP. This can cause immense instability...

Nope - it's a BIOS setting - part or the AGP spec. It determines the maximum system memory to use for texture caching. Maybe your BIOS determines it automatically - a good rule of thumb is 25% of main memory - or maybe there's a BIOS update you need... Anyway, its not something you ned to worry about unless your system is mis-behaving...

The only driver that are absolutely sure to work are those that ship on the W2K CD, and will install during the hardware detection phase on the W2K setup. There is no "official" W2K version of LiveWare at this time. There is a hacked version of the NT4 LiveWare - which may or may not work for you...

The new 5.50.005 drivers are Win9x only. There haven't been any new G400 W2K drivers since early December, at least according to the web-site... [This message has been edited by YuppieScum (edited 14 January 2000).]

I also use a CL TNT1 and V2 CLI - the combination of latest version (3.69 now) drivers with a OpenGL driver from 3.52 works in Q3A a treat - no extreme darkness at all... Just install the new version drivers, reboot, then overwrite the NVOGLNT.DLL in WINNT\SYSTEM32 with the 3.52 (1.1.4 internal version) file.

The existing G400 beta drivers for W2K are crap. I still use my TNT1 card as it surpasses the performance of my G400 under W2K... Maybe we'll get good drivers one day...

The registry hack is for Win9x, not for W2K. It is very unlikely that any "proper" drivers will include overclocking capability, as this would directly compromise system stability - which is what NT is all about. Why not use PowerStrip instead?

FWIW, mine too is a bog-standard CL TNT1 16Mb AGP card, and its performance has been flawless with W2K since the very early builds. If you've had the same problem using Win9x, then I'd expect its more to do with the mobo than the card - get the latest BIOS and ensure it's allocating an IRQ to the card...

"Biometrics" refer to fingerprints, handprints, facial recognition, things of that sort. You can also integrate card swipes and the like into the NT login process too...

I have a regular TNT and it's always worked fine under W2K. You'll find posts elsewhere that will suggest ensuring the BIOS has allocated an IRQ to the card. Also, you don't say what card maker, what card BIOS, what mobo, mobo BIOS, and driver revision...

Recommended is "as much as you can afford." Absolute min would be 64Mb...

Not easily. NT doesn't give you that info by default for "security reasons". You can, however, write your own login process to replace the MSGINA.DLL - this is what the "biometric" login schemes do.

Oops - remember that Win9x can't read NTFS, so if you dual boot and need that partition under both - don't convert.

Yup - apps will continue to run - in general they don't care what the FS is, they just ask the OS for data... You speicify the root directory for FTP, so if it's C:\ then the whole drive is exposed (this is a bad thing)... Also under NTFS, you can assign permissions (for FTP and other things) on a file and directory basis.

Hm...something that's not supported, officially "doesn't work", causes huge numbers of people problems and was hacked together out of the kindness of someones heart, doesn't work for you, and all you can do it ***** and moan? GET A F**KING GRIP YOU WHINEY LAMER.

Hm. You don't mention drivers, or any overclocking you may have done, but the first thing I'd try is removal of the SB and net card. Also put the HD onto the regular IDE channel...

Odd. SOunds like something is fsck'd. The driver is called "Create SB Live! Basic (WDM)" in the device manager...

Hmmm... What is the DHCP server running on?

You might like to give a teensy bit more info with your question. Maybe the version of W2K you're running, what hardware and driver versions, and perhaps even the actual error you get. Just a thought...

Congrats on getting where you are! As far as LiveWare is concerned, I'd recommend staying well clear until Creative get off the dime and release a W2K-compatible version. The hacked NT4 Liveware drivers can be made to work (with luck and a following wind - YMMV) but it seems to be more trouble than it's worth...

Easiest way is to yank the card, uninstall the drivers, then drop the card back in and let the h/w detection deal with it - worked for me!

The DHCP server is supposed to not care about what is asking for a lease on an address. I have heard that the set-up process may fsck up when configuring IP - so the best plan is probably to drop the stack, reboot and re-add it.

The native W2K drivers for SB Live DO support DirectSound, and any EAX that doesn't require additional local s/w support (ie Liveware).