Diablo 2 doesn't seem to accept the fact that DirectX is even running. On the back of the jewel case it lists Win2k as one of the supported operating systems. When it does a search for supported video modes with the vidtest program, it says that none are supported.
This error will appear if I just try to load it up: Diablo II Critical Error Error 22: A critical error has occurred while initializing DirectDraw.
Oh, and for the hell of it I downloaded version 1.9 so Diablo2 is up to date in that respect unless there's a more recent patch for it out right now.
Now here's the ironic part. If I go ahead and reinstall DirectX 8.0a, it will work after I reboot... but only once. Anytime after that, I get the same error message. Really pretty gay. I have very little desire to go back to WinME, but I probably will if I can't get this problem licked with so many of the games out there.
With Civilizations 3, the game will load up until the sound begins. About half a second into the first sound file being played the game locks. After I downloaded the latest 5.1 drivers that they released for 2000/XP and ran it... the program ran fine ONCE. After that, the same results. The idea of loading drivers for my sound card just to be able to play Civ3 one time, and Diablo 2 reloading DirectX drivers to be able to play it one time is obscenely retarded.
With Operation Flashpoint, it's the same thing with the sound. I didn't try reinstalling the sound drivers for that one... but according to the problems I've been having so far. I think it's safe to say the same results would occur.
Does anyone that runs Win2k know what the problem might be? I'd love to continue to use it, but I love to play computer games and if Win2k just won't run them then there's little need for me to use it. Thanks.
This error will appear if I just try to load it up: Diablo II Critical Error Error 22: A critical error has occurred while initializing DirectDraw.
Oh, and for the hell of it I downloaded version 1.9 so Diablo2 is up to date in that respect unless there's a more recent patch for it out right now.
Now here's the ironic part. If I go ahead and reinstall DirectX 8.0a, it will work after I reboot... but only once. Anytime after that, I get the same error message. Really pretty gay. I have very little desire to go back to WinME, but I probably will if I can't get this problem licked with so many of the games out there.
With Civilizations 3, the game will load up until the sound begins. About half a second into the first sound file being played the game locks. After I downloaded the latest 5.1 drivers that they released for 2000/XP and ran it... the program ran fine ONCE. After that, the same results. The idea of loading drivers for my sound card just to be able to play Civ3 one time, and Diablo 2 reloading DirectX drivers to be able to play it one time is obscenely retarded.
With Operation Flashpoint, it's the same thing with the sound. I didn't try reinstalling the sound drivers for that one... but according to the problems I've been having so far. I think it's safe to say the same results would occur.
Does anyone that runs Win2k know what the problem might be? I'd love to continue to use it, but I love to play computer games and if Win2k just won't run them then there's little need for me to use it. Thanks.