For some weird reason my base image was set tp ACPI Multiprocessor. I set that to ACPI PC (1 processor), re cloned, and it was able to do the minisetup on the new computer

Problem:
After it was done with the setup and it does its typical reboot, we ran into the same probelm where we got the screen "windows did not start successfully" with the normal, safe mode, etc options..

Could this be the HAL again? Could MySysprep of messed up?

I created a "universal" image in VMware of Windows XP Pro (multi processor) and injected all the drivers, etc. MySysprepped it. Ghosted it. It will boot successfully on another VMware computer so long as I do a disk image, not partition image.

Problem:

Finally tried it on an older physical (single processor), it ghosts just fine except when it boots up for the first time we get the message "windows did not start successfully" with the normal, safe mode, etc options..

If you hit normal it just sits there with no hard drive light activity

If you hit safe mode it just stops after a certain driver (which could be normal since safe mode normally does this till safemode appears)

What do you suggest would be the best first step to diagnose?

Originally I thought maybe the boot.ini or MBR was messed up but not sure.

Thanks,

Chase

I found out why I am getting blue screens and solved that issue. It is a problem with VMWare actually when it comes to SysPrep.

Using this post:
http://www.altirigos.com/vbulletin/vmwa … creen.html

I followed this and it works now:
Try this.. Edit the VM guest's .VMX file.

"Set this line: scsi0.present = "TRUE"

to

scsi0.present = "FALSE"

No, I don't understand it. It just works."

Just an FYI for you all now.

Well.... for now I have given up. I have tried a lot of different driver injections methods but I still could not get my C drive to be recognized with SCSI drives. As for my IDE drive x86 test, I got my C: to be detected only once. With the x86 capture I was given an error of a corrupt windows file so I never made it to the capture screen. With the x64 capture file, I was able to get it to recognize my C: drive once. I then repeated the procedure (by reverting back via snapshot) only to have it now bluescreen me saying my ACPI wasn't compatible. I even dumbed it down to the ACPI PC HAL but I still got that message. I just wish there was an image of XP someone created in Vmware that is recognized by WDS, then I could work off of that. I'm sure one day I'll get it....

So what are some 3rd party deployment solution software pieces?

First I just want to thank you for taking the time to read my post and help me out.  My main issue is in Windows Deployment Services when I try to capture an image it shows no drives to be captured. I believe it does not have th driver for the SCSI Virtual drive. Shift + F10 shows no C: drive, hence my reasoning. I have now since been trying to fix it, now trying method below.

OverFlow wrote:

The best plan is
use Galepos offline sysprep for our mass storage pack
then use the DriverPacks BASE SAD feature with Method 2, calling dp_inst_tool.cmd from runonce or guirunonce reg entry added when the machine is resealed.

It was a little difficult but let me tell you what I have done so far....
I downloaded the offline sysprep and loaded up my basemachine's hard drive on another virtual so I could edit it.

I had trouble finding a guide since the sticky post from Galepos simply talks about him releasing it.

I extracted the driver pack mass storage drivers to the root of offline sysprep. Ran offline sysprep. Pointed it to the Windows OS on the attached drive. I didnt tell it to sysprep, instead I clicked a few check marks to do some fixes. I then told it to run. What the heck did it do... I have no idea. I'm not sure if or how it even injected the drivers. If it did inject them, why would I even DriverPacks BASE SAD feature?

Here is the log from offline sysprep.

2009-07-01 08:29:59 : <INIT> DriverPacks BASE 8.12.5 initialized.
2009-07-01 08:29:59 : <INIT> Host environment: WIN_XP Service Pack 3 on X86 CPU.
2009-07-01 08:29:59 : <INIT> Created temporary working directory.
2009-07-01 08:29:59 : <INIT> Imported proxy settings from Internet Explorer.
2009-07-01 08:29:59 : <INIT> Start scanning for DriverPacks for the wnt5_x86-32 platform.
2009-07-01 08:29:59 : <INIT> 	Could not detect any (official) DriverPacks.
2009-07-01 08:29:59 : <INIT> 	Could not detect any 3rd party DriverPacks for wnt5_x86-32.
2009-07-01 08:29:59 : <INIT> 	Finished scanning.
2009-07-01 08:29:59 : <INIT> Detected settings file "E:\Sysprep\DriverPacks\DPs_BASE.ini".
2009-07-01 08:29:59 : <INIT> Imported settings from settings file.
2009-07-01 08:29:59 : <INIT> [Settings]\DPsMethod not specified: default (2) was set.
2009-07-01 08:29:59 : <INIT> [Settings]\finisherMethod not specified: default (GUIRunOnce) was set.
2009-07-01 08:29:59 : <INIT> [OptionalSettings]\KTD not specified: default (none) was set.
2009-07-01 08:29:59 : <INIT> [OptionalSettings]\QSC not specified: default (yes) was set.
2009-07-01 08:29:59 : <INIT> [OptionalSettingsOther]\ATI_cpl not specified: default (None) was set.
2009-07-01 08:29:59 : <INIT> [OptionalSettingsOther]\Nvidia_cpl not specified: default (None) was set.
2009-07-01 08:29:59 : <INIT> QuickStream Cache directory not found!
2009-07-01 08:29:59 : <GUI>  Initialized GUI.
2009-07-01 08:29:59 : <GUI>  Created a list of all available language files.
2009-07-01 08:29:59 : <GUI>  Set the last used language, English, as the GUI language.
2009-07-01 08:30:47 : <GUI>  Changed Windows installation files OR export (depending on the installation platform) location to E:\WINDOWS.
2009-07-01 08:30:47 : <GUI>  No OS could be detected.
2009-07-01 08:31:15 : <GUI>  Refreshed UpdateChecker with success.
2009-07-01 08:32:11 : <GUI>  Downloaded DriverPack MassStorage 9.01.
2009-07-01 08:32:41 : <GUI>  Downloaded DriverPack LAN 8.12.1.
2009-07-01 08:32:42 : <GUI>  Downloaded DriverPack CPU 8.04.
2009-07-01 08:32:54 : <GUI>  Downloaded DriverPack Chipset 9.02.
2009-07-01 08:32:54 : <GUI>  Start scanning for DriverPacks for the wnt5_x86-32 platform.
2009-07-01 08:32:54 : <GUI>  	Detected DriverPack Chipset 902!
2009-07-01 08:32:54 : <GUI>  	Detected DriverPack CPU 804!
2009-07-01 08:32:54 : <GUI>  	Detected DriverPack LAN 8121!
2009-07-01 08:32:54 : <GUI>  	Detected DriverPack MassStorage 901!
2009-07-01 08:32:54 : <GUI>  	Could not detect any 3rd party DriverPacks for wnt5_x86-32.
2009-07-01 08:32:54 : <GUI>  	Finished scanning.
2009-07-01 08:32:55 : <GUI>  Refreshed UpdateChecker with success.
2009-07-01 08:33:29 : <GUI>  Changed Windows installation files OR export (depending on the installation platform) location to E:\WINDOWS.
2009-07-01 08:33:29 : <GUI>  No OS could be detected.
2009-07-01 08:33:43 : <GUI>  Changed Windows installation files OR export (depending on the installation platform) location to E:\WINDOWS\system32.
2009-07-01 08:33:43 : <GUI>  No OS could be detected.
2009-07-01 08:34:05 : <GUI>  Changed Windows installation files OR export (depending on the installation platform) location to E:\WINDOWS.
2009-07-01 08:34:05 : <GUI>  No OS could be detected.
2009-07-01 08:34:18 : <GUI>  wnt5_x86-32_StandAloneDrivers is the selected installation platform .
2009-07-01 08:34:18 : <GUI>  Changed installation platform from "disc" to "StandAloneDrivers".
2009-07-01 08:38:34 : <GUI>  Saved settings!
2009-07-01 08:38:34 : <GUI>  Closed GUI.
2009-07-01 08:38:35 : <SEL>  Selected module: wnt5_x86-32_m2 Stand Alone DriverPacks.
2009-07-01 08:38:35 : <SEL>  Selected Location E:\WINDOWS\DriverPacks.net.
2009-07-01 08:38:35 : <COPY> Created necessary directory structure for method 2.
2009-07-01 08:38:35 : <COPY> Copying files necessary for method 2.
2009-07-01 08:38:36 : <COPY> Extracted additional files necessary for method 2.
2009-07-01 08:38:36 : <COPY> Copied DriverPack Chipset to \OEM.
2009-07-01 08:38:36 : <COPY> Copied DriverPack CPU to \OEM.
2009-07-01 08:38:36 : <COPY> Copied DriverPack LAN to \OEM.
2009-07-01 08:38:36 : <COPY> Copied DriverPack MassStorage to \OEM.
2009-07-01 08:38:36 : <COPY> Copied DriverPacks to \OEM.
2009-07-01 08:38:36 : <COPY> Updated DPsFnshr.ini to disable KTD.
2009-07-01 08:38:38 : <COPY> DP_Install_Tool was copied successfully
2009-07-01 08:38:38 : <COPY> Slipstream finished in 4 seconds.
2009-07-01 08:38:47 : <CLNP> Temporary working directory successfully deleted.
- = DriverPacks BASE ini settings used = -
[General]
; preferred language
prefLang	= "English"
; yes/no, enable or disable the wizard-style buttons, if not specified: yes
wizardButtons	= "yes"
; yes/no, enable or disable the GUI, if not specified: yes
GUI		= "yes"


[Settings]
; disc/bartpe/multibootDisc
instPlatform	= "StandAloneDrivers"
; trailing backslash is allowed, but not necessary
location	= "E:\WINDOWS"
; none/all/select, if select, specify them below, if not specified: all
DriverPacks	= "select"
; 1/2, method to install the DriverPacks, if not specified: 2
DPsMethod	= "2"
; GUIRunOnce/RunOnceEx/custom, if not specified: GUIRunOnce
finisherMethod	= "GUIRunOnce"


; this section is optional!
[OptionalSettings]
; none/all/select/paths/patterns, enable or disable Keep The Drivers (KTD) , if not specified: none
KTD		= "false"
; <path>, to specify a custom KTD cache location, if not specified: default (%SystemRoot%\DriverPacks)
KTDlocation	= "%SystemRoot%\DriverPacks"
; yes/no, enable or disable QuickStream Cache (QSC), if not specified: yes
QSC		= "yes"


; you should only add this section if you've set [Settings]\DriverPacks to "select"
[SelectDriverPacks]
DP_Chipset	= "yes"
DP_CPU		= "yes"
DP_LAN		= "yes"
DP_MassStorage	= "yes"
DP_MassStorage_textmode = "yes"
2009-07-01 08:38:47 : <CLNP> Create a DPs_Base.log backup @ E:\Sysprep\DriverPacks\LogFiles\DPs_BASE_09-07-01_08-38.log
2009-07-01 08:38:47 : <CLNP> Program terminated.

Did it inject the drivers? My Windows installation is E:

As for the DriverPacks BASE. I pointed it to the E:\Window directory and selected the Stand Alone Drivers. I had to stop and go to work so I wasn't able to finish the guide at the moment, but I stopped at:
6) Move extracted DriverPacks ('D' folder) and wnt5_x86-32.ini files to C:\

Last question for now, where is the dp_inst_tool.cmd file? Sorry if it's in an obvious place.

I am having trouble getting an image to even caputre with WDS but that'll be in another thread later.

Is the how-to guide updated with all the corrections talked about throughout the thread? Is the whole process considered "up-to-date"?