I have a client running Win2K server. His motherboard & CPU crashed a few weeks ago. After replacing both of them, the system will now boot up and operate. (I won't go into the issues I had with getting Win2K to recognize the IDE controller.)
But here's what's going on now:
The old CPU was an Athlon XP 1800+ with 512MB ram. The new CPU is an Athlon XP 2600+, which required new, faster memory (also 512MB). I have been finding that if I run the new CPU at 1533 MHz, and the memory at 333 MHz, I have no problem with the OS running. However, when I go into the BIOS and increase the speed to 2300 MHz and the memory speed to 400 MHz (which is what it's rated for), I can't get the system past the blue screens.
I'm wondering: Is this some kind of built-in stupid security thing with Win2K thinking it's gotten moved to a new computer, or what? Is there a way around this? I just think it's a shame to have spent $120 more on a CPU that can only run at the lower speed.
Incidentally, I've tried running with the cache disabled, and it was ridiculously slow, so that's not an option.
Any help will be appreciated.