YuppieScum

Don't forget, the native drivers work fine with SMP - it's Liveware that doesn't.

This isn't really a question for the W2K Hardware Compatibility forum. Try the multimedia newsgroups on USENET.

Yeah! Bring it on...

well, life sucks, and your script has bugs . . .

The best way to check out this kid of prob is to remove all the non-essential stuff (Sound, DVD, etc), fire the box up, check it out, then start adding one piece at a time until it goes wrong... Also, don't forget that the current G400 drivers suck donkey balls...

Tim - All the 3.6x drivers are for RC3 and above only. Ekstreme - Have you used the /cg_draw3dicons 0 command in Q3A? Try it - it worked for me!

In what way does UT fail to run under Glide? I've been using the hacked Voodoo2 drivers for months with UT, FreeSpace, FreeSpace2 and others...

Make sure the video card is being allocated an IRQ by the mobo's BIOS. Also, undo any CPU overclocking by "odd" FSB amounts (75,110,etc) unless the AGP/PCI bus is adjusted back to 66/33Mhz by the BIOS. Also, when posting questions, it help to include details like - W2K version, mobo, BIOS revision, vid card, etc.

IIRC, the Voodoo3 drivers that ship with w2k don't support D3D, so the games are probably not running with h/w acceleration. There are beta drivers available... Your ADSL "modem" connects to your PC via a standard ethernet card - so what is missing is support for that card, not the ADSL box. Buy yourself a generic 3Com or Intel card for about $40...

After installing a printer, you then need to share it. When you do, NT or W2K will ask you which clients to support, and will put those drivers on the print server. Then when you conect from the client, the correct drivers are passed over the network and installed. Failing that (if the server doesn't have drivers for the client), install the drivers for the printer manually, then change the properties to redirect it to the print server.

There are currently no D3D W2K Voodoo2 drivers. Search the message base for details.

The G400 drivers are sh1t...

Jesus - how many times do we have to go through this? What error? What drivers? What GFX mode - OpenGL or D3D? Have you searched the other messages? Using the "search" function?

You can also try http://win2kbox.8m.com Or you could just search the message base here, and find all these links without having to ask...

As has been stated elsewhere on this message board (by myself and others)... Replace the 3.65 OGL driver with that from the 3.52 or 3.56 driver release. At the Q3A console, type /cg_draw3dicons 0

Which drivers are you using? Don't forget that MS stated they won't ship any OpenGL drivers "in the box"...

If you're not using a hub or switch between the machines, you'll need to use a "back-to-back" cable - the regular network cable won't work.

Uninstall LiveWare. Uninstall the sound card. Possibly even delete the drivers. Then install using the "shipped-with-W2K" drivers. The native drivers work great for the game port and audio (as long as you're happy with regular stereo). If you dick around, stuff breaks...

Do you have another device on the same IDE channel as the source CD? That could be causing I/O latency...especially if the swap file, or temp directory are located there...

Ronin- >. If I want to complain then this is the best place. Bollocks. The best place to complain is in polite e-mail to the hardware vendors. All whining about a lack of drivers here achieves is to 1. Use up bandwidth 2. Make it harder for people to find answers to their problems. 3. Piss off those of us who are trying to help other. And Seldzar - good point, but dude, you gotta chill a bit. It's Christmas, remember

Won't let you install the printer? In what way? Nasty error message? Hand reaches out from the monitor and slaps you? No drivers? Parallel port not working? Give us something to work with...

As long as you're not dual-booting, then go with a single, big NTFS partition. While the one-for-OS, one-for-data can make some file organisation a bit easier, it significantly reduces your I/O speed, as the head has to traverse at least half the drive almost every access - especially when paging. In terms of recovery, I always keep an old IDE ready-to-go with Win9x and the NTFS-driver - then if something goes seriously wrong, i can just slap that on the primary. If you want to spend the time, you can also make a bootable emergency ZIP...

Did you "uninstall" the ATI drivers? It may well be those that are causing the problem...

This is the glory of SMP! Burn a CD, download another build via FTP, run AIM and Outlook and a couple of browsers AND have distributed.net as a service...

Have you tried creating "Boot Floppies" from either the NT4 or W2K CDs, and then using them to re-partition the HD?