mbkowns
asked on
Windows 2000 Sysprep Virtual PC VHD BSOD while moving the sealed image to a physical computer.
I have created a Virtual PC image with windows 2000 and all the updates. I have not installed any software so it is a completely stock setup. I am using sysprep version 5.00.2195.6685 which is for Windows 2000 SP4. I have tired all the prior versions with sysprep and windows 2000 SP3, SP2 and SP1. All give me the same problem.
The image seals in a matter of seconds and I image the computer with RDeploy which is altiris's image solution that just clones the drive to a another one. I mount the VHD hard drive with windows virtual server 2005. Then from that altiris clones it to another IDE drive. I stick the drive in the physical computer and it BSOD's right before the mini setup loads while still on the windows 2000 loading screen...
STOP 0x000001E kmode_exception_not_handle d
I have tried converting the disk in virutal pc from dynamic to fixed which the exact same error as the result. I have also tried to do another installed of windows 2000 with the same problem even another one without the updates.
I use virutal pc all the time for syspreping the windows xp / tablet machines and have used the exact same percedures and everything works fine. I think the problem lies with the mass storage controllers. Using Windows 2000 SP4 sysprep (1.1) should work with the default set of mass storage drivers. I am really stuck but it seems like the HAL is fine since it shows the windows 2000 screen. I know for a fact that this machine and the virtual pc use the same HAL. So with that ruled out it has to be the mass storage drivers not being loaded. Also this machine does not need to have F6 pressed during the install so the stock drivers should work which is what is also below. As for the device drivers I use a program found here.
http://www.vernalex.com/tools/spdrvscn/index.shtml
Here is my Sysprep.inf
;SetupMgrTag
[Unattended]
OemSkipEula=Yes
InstallFilesPath=C:\syspre p\i386
DriverSigningPolicy=Ignore
UpdateInstalledDrivers=Yes
[GuiUnattended]
OEMSkipRegional=1
TimeZone=4
OemSkipWelcome=1
[UserData]
ProductID=XXXXX-XXXXX-XXXX X-XXXXX-XX XXX
FullName="myfullname"
OrgName="myorg"
ComputerName=*
[Display]
BitsPerPel=32
Xresolution=800
YResolution=600
[TapiLocation]
CountryCode=1
Dialing=Tone
AreaCode=951
LongDistanceAccess="1"
[SetupMgr]
DistFolder=C:\sysprep\i386
DistShare=windist
[Identification]
JoinWorkgroup=myorg
[Networking]
InstallDefaultComponents=Y es
[SysprepMassStorage]
PCMCIA\*PNP0600=%systemroo t%\inf\msh dc.inf
PCMCIA\KME-KXLC005-A99E=%s ystemroot% \inf\mshdc .inf
PCMCIA\_-NinjaATA--3768=%s ystemroot% \inf\mshdc .inf
PCMCIA\FUJITSU-IDE-PC_CARD -DDF2=%sys temroot%\i nf\mshdc.i nf
*AZT0502=%systemroot%\inf\ mshdc.inf
PCI\CC_0101=%systemroot%\i nf\mshdc.i nf
PCI\VEN_10B9&DEV_5215=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_10B9&DEV_5219=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_10B9&DEV_5229=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_1097&DEV_0038=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_1095&DEV_0640=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_1095&DEV_0646=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_0E11&DEV_AE33=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_8086&DEV_1222=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_8086&DEV_1230=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_8086&DEV_7010=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_8086&DEV_7111=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_8086&DEV_2411=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_8086&DEV_2421=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_8086&DEV_7199=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_1042&DEV_1000=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_1039&DEV_0601=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_1039&DEV_5513=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_10AD&DEV_0001=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_10AD&DEV_0150=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_105A&DEV_4D33=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_1106&DEV_0571=%sys temroot%\i nf\mshdc.i nf
PCI\VEN_105A&DEV_4D69="C:\ sysprep\dr ivers\Mass \3400DT-Pr omise\ULTR A.INF"
PCI\VEN_105A&DEV_4D68="C:\ sysprep\dr ivers\Mass \3400DT-Pr omise\ULTR A.INF"
PCI\VEN_105A&DEV_4D30&SUBS YS_4D33105 A="C:\sysp rep\driver s\Mass\340 0DT-Promis e\ULTRA.IN F"
PCI\VEN_105A&DEV_0D30&SUBS YS_4D33105 A="C:\sysp rep\driver s\Mass\340 0DT-Promis e\ULTRA.IN F"
PCI\VEN_105A&DEV_4D38&SUBS YS_4D33105 A="C:\sysp rep\driver s\Mass\340 0DT-Promis e\ULTRA.IN F"
PCI\VEN_105A&DEV_4D33="C:\ sysprep\dr ivers\Mass \3400DT-Pr omise\ULTR A.INF"
The image seals in a matter of seconds and I image the computer with RDeploy which is altiris's image solution that just clones the drive to a another one. I mount the VHD hard drive with windows virtual server 2005. Then from that altiris clones it to another IDE drive. I stick the drive in the physical computer and it BSOD's right before the mini setup loads while still on the windows 2000 loading screen...
STOP 0x000001E kmode_exception_not_handle
I have tried converting the disk in virutal pc from dynamic to fixed which the exact same error as the result. I have also tried to do another installed of windows 2000 with the same problem even another one without the updates.
I use virutal pc all the time for syspreping the windows xp / tablet machines and have used the exact same percedures and everything works fine. I think the problem lies with the mass storage controllers. Using Windows 2000 SP4 sysprep (1.1) should work with the default set of mass storage drivers. I am really stuck but it seems like the HAL is fine since it shows the windows 2000 screen. I know for a fact that this machine and the virtual pc use the same HAL. So with that ruled out it has to be the mass storage drivers not being loaded. Also this machine does not need to have F6 pressed during the install so the stock drivers should work which is what is also below. As for the device drivers I use a program found here.
http://www.vernalex.com/tools/spdrvscn/index.shtml
Here is my Sysprep.inf
;SetupMgrTag
[Unattended]
OemSkipEula=Yes
InstallFilesPath=C:\syspre
DriverSigningPolicy=Ignore
UpdateInstalledDrivers=Yes
[GuiUnattended]
OEMSkipRegional=1
TimeZone=4
OemSkipWelcome=1
[UserData]
ProductID=XXXXX-XXXXX-XXXX
FullName="myfullname"
OrgName="myorg"
ComputerName=*
[Display]
BitsPerPel=32
Xresolution=800
YResolution=600
[TapiLocation]
CountryCode=1
Dialing=Tone
AreaCode=951
LongDistanceAccess="1"
[SetupMgr]
DistFolder=C:\sysprep\i386
DistShare=windist
[Identification]
JoinWorkgroup=myorg
[Networking]
InstallDefaultComponents=Y
[SysprepMassStorage]
PCMCIA\*PNP0600=%systemroo
PCMCIA\KME-KXLC005-A99E=%s
PCMCIA\_-NinjaATA--3768=%s
PCMCIA\FUJITSU-IDE-PC_CARD
*AZT0502=%systemroot%\inf\
PCI\CC_0101=%systemroot%\i
PCI\VEN_10B9&DEV_5215=%sys
PCI\VEN_10B9&DEV_5219=%sys
PCI\VEN_10B9&DEV_5229=%sys
PCI\VEN_1097&DEV_0038=%sys
PCI\VEN_1095&DEV_0640=%sys
PCI\VEN_1095&DEV_0646=%sys
PCI\VEN_0E11&DEV_AE33=%sys
PCI\VEN_8086&DEV_1222=%sys
PCI\VEN_8086&DEV_1230=%sys
PCI\VEN_8086&DEV_7010=%sys
PCI\VEN_8086&DEV_7111=%sys
PCI\VEN_8086&DEV_2411=%sys
PCI\VEN_8086&DEV_2421=%sys
PCI\VEN_8086&DEV_7199=%sys
PCI\VEN_1042&DEV_1000=%sys
PCI\VEN_1039&DEV_0601=%sys
PCI\VEN_1039&DEV_5513=%sys
PCI\VEN_10AD&DEV_0001=%sys
PCI\VEN_10AD&DEV_0150=%sys
PCI\VEN_105A&DEV_4D33=%sys
PCI\VEN_1106&DEV_0571=%sys
PCI\VEN_105A&DEV_4D69="C:\
PCI\VEN_105A&DEV_4D68="C:\
PCI\VEN_105A&DEV_4D30&SUBS
PCI\VEN_105A&DEV_0D30&SUBS
PCI\VEN_105A&DEV_4D38&SUBS
PCI\VEN_105A&DEV_4D33="C:\
I would say the issue you are having is because of a driver that is required to operate your physical hardware is missing. Windows XP would probably handle this better than Windows 2000.
ASKER
... Its not a device driver but it would be the mass storage controller. I have all the default ones and the computer I am using does not require F6 so it does not need a alternate driver.
Still looking for a solution.
Still looking for a solution.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.