Userinit.exe - "no disk in drive d:" when I boot- HELP

[zebratech]

Hi,
Just installed 3 Dell OptiPlex160L pc's at work with XP Pro SP1, win 2000 server network, tcp/ip. These desktops are replacing win 2000 workstations that were already there, same programs running, same users. After attaching them to the domain, on startup I get a screen that says "userinit.exe- no disk in drive d:" ok, retry, cancel. How do I stop this from happenning?
Thanks in advance.

 

[bcastner]

Go to the BIOS setup.

You want the boot order to show your first drive (C) as the first entry. Remove any duplicates, and place removable drives near the bottom of the list.

 

[zebratech]

Hi,
Thanks for the answerand I'll try it out. But why does this happen only when I logon to the domain? When I logon locally this doesn't happen?

 

[bcastner]

Your Sysprep is messed up somehow.

If you "cloned" these devices at some point prior to the sysprep you were using the eventual source for the image and referred to the CD Rom or a network share.

You then created as a result registry entries that cannot be duplicated in the image. Or your image source had a different drive letter.

A comment from one Forum:

Your UserInit value is pointing to the "wrong" drive

http://www.storageadmin.com/Articles/Index.cfm?ArticleID=15264

Alternately, you could change the Userinit value to just "userinit.exe" (instead of C:\Winnt\System32\Userinit.exe), then reboot and test a login.

Links to some similar problems/solutions:

http://www.experts-exchange.com/Operating_Systems/Win2000/Q_20186326.html

http://www.jsifaq.com/SUBM/tip6300/rh6346.htm

http://www.jsiinc.com/SUBF/Tip2500/rh2596.htm

Another thing you could try is to delete all of the entries under HKLM\System\MountedDevices, and then reboot: while the system will not tolerate inaccurate entries at that location, it will self-correct the absence of these values.

 

[zebratech]

Hi,
Thank you! This is exactly what happened. Drive d is the partition from the server that I had the image on, not my local drive d: which gave rise to the confusion. I can see the problem clearly now.
Thanks for the quick response.