don't try this at home kiddies

Ok,
ACPI was putting a bunch of stuff on irq 11 and it pissed me off that I couldn't assign my own irq's so I disabled it. No problems there but I didn't find any performance increase and found I missed some of the acpi functionality. So, I decided to re-enable it. I went into device manager and upgraded the driver for 'computer' to uniprocessor acpi, disregarding the warning that this could cause major computer problems. Well, they weren't kidding. System wouldn't boot past windows loading, no matter what I did (including taking out all my cards and even putting a pci video card). I also tried repairing windows 2000 which proceded normally but just ended up showing me a new set of blue screens. Finally I gave and had to delete the partition and do a fresh os install. Setting all this crap up was a lot funner the first time through.

The good news is I learned a bit and everything is back up and running again.

thanks for mentioning it. I did a second install of Win2k disabling ACPI because I'd had some weird lockups and I thought it my be due to everything freaking sharing IRQ9!!! So that didn't help, and I eventually discovered it was the Voodoo3 drivers causing the problem. (the final release 1.03 suck but at least they don't lock the machine up). But I'm still left with a machine that won't handle new hardware too well. Guess I'll have to reinstall Win2k if I want ACPI.



***Hey I run Intel... but let's get real***