Oh Microsoft how I hate thee, let me count the ways
Ok so first off what the hell is wrong with this picture?
That's how it shows up in the "Device Manager" or should I call that the 'Device Mis-manager'? How on earth does a system messup a driver for the damn processor? Check the device and it gives me a code to chase (code 32) whatever the hell that is :\ Anyway, so I go and check Windows Support website and find this:
A driver (service) for this device has been disabled. An alternate driver may be providing this functionality. (Code 32)
Recommended resolution
The start type for this driver is set to disabled in the registry. Uninstall the driver, and then click Scan for hardware changes to reinstall or upgrade the driver.
On the General Properties tab of the device, click Troubleshoot to start the Troubleshooting Wizard. If the driver is required, and if reinstalling or upgrading does not work, change the start type in the registry using Registry Editor. For more information, see the Registry Reference in the Microsoft Windows 2000 Server Resource Kit.
Yes that's right, uninstall the driver for the processor, that shouldn't cause any problems... Amazingly it didn't. So I'm jumping ahead of myself, so here's a quick background. The user of above referred to system called to tell me her system is running like garbage. It is, seriously. We're talking +20mins to boot to the login screen. While I'm ranting, may aswell mention another stoopid M$ oddity. Twice today, on two completely seperate systems, Win XP has managed to fragment the hell out of a drive that is 85% free. That's right two seperate systems, two seperate users, two seperate drives with 45% file fragmentation. That's just... just... sad really.
