Motherboard or other component incompatible with W2K Server only???

[Rockhound]

Has anyone ever installed Windows 2000 Server on an Intel D865PERL motherboard? If so, did it work?

Interesting problem I have run into...

System configuration is

Intel D865PERL mb, 2.8GHz 800 fsb cpu
512MB Corsair RAM
ATI 9800 Pro video
WD 20GB hard drives (x2)
Lite-On CDRW

Installing W2K Server causes all sorts of problems, namely applications not being able to run with the message "Application not able to initialize properly (0xc0000142)". This happens with virtually anything I try to open whether it is Explorer, looking at specific events in event viewer, My computer, etc. Trying to use Disk Management in Admin tools/Computer Mgmt gives "Failed to open Logical Disk Manager Service". All these problems seem to occur AFTER video drivers are installed.

Installing W2K Professional =====> NO PROBLEMS WHATSOEVER!!!

What gives?? How can this be?

 

[spyordie007]

All these problems seem to occur AFTER video drivers are installed.

The source of the problem would appear to be clear, if it is running with the default windows ATI drivers than let it be. You dont need 3d video performance for your server.

 

[Smilin]

You're getting some kinda trouble with msgina, userinit or one of the processes firing up around logon time. All of them are identical between 2k pro and 2k server. The only difference that could possibly come into play is terminal services. Are you using that? Anything else different? Are you installing any remote control software in there somewhere? As much as I like my ATI, their drivers are ass. Wouldn't be surprised if they have some sort of issue. Try one of the older versions or a WHQL driver to see if it clears up.

 

[Automan]

Well I definitely will not be able to solve your issue (my apologies in advance), but I can sympathize with your issue.

I have an AIW 9600Pro and have experienced issues not exactly like, but maybe somewhat related to what it sounds like you are describing when I was trying to load Windows 2000 Advanced Server. As soon as the ATI drivers are loaded my system will not logon. Everything runs perfectly up until I install the drivers in my case as well. As soon as they are loaded I reboot, and get the logon prompt, but then nothing works beyond that (normally can't even logon, but if I do happen to get past the logon it will hang before getting to the desktop every time in my case). Booting to safe mode and removing the ATI drivers does allow the system to recover, so I, like mentioned above, am also convinced it is the drivers. I am running a nForce2 board and have loaded the ATI drivers as old as 3.6's (okay, so not that old, but still 'older") and as new as the 4.1 and 4.2's, with no luck.

I was not running Terminal Services on several of the install attempts, as there was a note in the ATI software somewhere that I found concerning running Terminal Services on Windows 2000 Advanced Server with the ATI software. On a couple of the installs I took the system down to the most minimal install available before I loaded the drivers and still no luck. I tried with no Service Pack, with Service Pack 1, Service Pack 2, and Service Pack 4. I tried with and without DirectX 9 loaded and with all and with none of the critical updates loaded. In all cases I was running in a workgroup and was logged in as the local administrator at installation time.

I spent the better part of a weekend on it before I finally had to move on (my 'need to know' got the better of me). In my case I hadn't actually been looking for anything related to the 3D performance from the new drivers, I was really trying just to get off of the 640x480 and 16 color mode to something above that and could not get any of the generic drivers to load and allow me off of the low-end resolutions as the testing I was trying to perform required me to run at a higher resolution. I finally just loaded Win2k on an older system with an nVidia card and completed testing what I needed on that machine intead. One of these days I would like to go back and try to figure this one out, but for now my issues has remained a mystery to me as well.

Last thing I will note is that Win2k Pro does work in my case as well. Just seems odd.

Here's to hoping that we can find a solution or workaround for this in the future.