halen

I'm using an Abit BH6 which uses the 440BX Intel chipset, so its not a chipset problem. I talked today with a tech from Creative and he told me that this problem is a bug that's been present in the Nvidia drivers since 5.22. He says that it will probably be fixed in the next revision, although he didn't say who's revision, CL's or Nvidia's. I have the feeling that whatever the bug is, it isn't removed by standard uninstallation procedures, since downgrading doesn't seem to help, except for the first instance of a reinstall before a reboot, where it works for a bit. As far as you, Cuke, did you ever install 5.22? I think that 5.25 and 5.30 don't have the bug, but also don't remove it if you are upgrading from a 5.22 installation. The guy from CL did say that they've been hearing a lot about this one, and that they should be fixing it real soon. I won't be holding my breath.

I'm pretty much convinced now that its a video driver issue. From what I can tell it is seperate from the driver files or the known registry keys, because I've even tried to go back to the 5.13 reference drivers and the original Creative Win2k drivers and the problem doesn't go away. I've been trying to reference between my home PC (the one with the problem) and my work Laptop, which has the properties button and has the driver in device manager, to find any differences in the registry. If and when I find anything, I will post it here first.

Anyone?

The problem with that is that I even just recently installed over 20 Win2k workstations at a site and every single one of them has the option to change the monitor driver. I have a 17" with BNC connectors, so the DDC auto-detect-plug-n-play thing doesn't cut it.

In my opinion, BIOS and hardware vendors need to start bundling their updates as disk images and Winimage or something that will work. With all the people using Win2000, WindowsME and even Linux, this would be so much easier.