wierd_w wrote on 2026-09-18, 16:51:

They seemed to always *Say* a specific card was unsupported by a driver pack, that supported more expensive versions of that gpu core, and manually adding in the IDs almost always worked.

Not an exclusive Nvidia habit but, for sure, they were the king of the hill

XP's weird. Last time I messed with it, loading official NVIDIA AHCI driver for my motherboard's SATA controller would just BSOD 32-bit version. But x64 driver on XP x64 worked.

I could not use KeePassNatMsg plugin for KeePass on x86 XP, it threw exception about unsupported cipher. But worked on XP x64.

EAX didn't work on XP x64 with Audigy Rx (Daniel K's drivers) AND limiting RAM. At least not through DirectSound, OpenAL was fine.

I remember Explorer on XP x64 glitching once and taking most of the 4 GB of RAM.

2 words, holy mess!

Is it just me or are Creative drivers a dumpster fire that you deliberately start in your OS?

They were. Creative Labs' drivers for the AWE32 and AWE64 allowed games to dynamically load soundfonts to them, but almost always broke in spectacular ways, only worked with very specific configurations, and were more fragile than raku pottery.

Ive noticed this on forums now, XP got the blame for a lot of stuff it just didnt deserve.
UCyborg last post about XP's weird...
What he is talking about is a known driver problem to do with the nForce driver and NCQ on the SATA controller. It was fixed by using the generic microsoft driver, which im sure you know about on here, but it doesnt stop people saying its an XP thing when it really wasnt, XP was just there while it was happening.
Nvidia are some of the worst in the business for driver shenanigans. How else to you get, on the older cards, two basically identical cards to function completely differently!
The Quadro GeForce gap.
Famous on forums like this of course but all that messing about trying to control who gets access to the power of their card through drivers when they really needed to concentrate on making decent drivers that didnt break the OS they were running on to the point of instability. And then forcing Microsoft to remove the access to memory over 4Gb to stop the problem they were being blamed for.