Jazkal

unless the hardware is an exact match, then yes, sysprep is needed.

Your problem could be that the winload.exe is not in the system32 folder. copy all the files in the System32\Boot folder to the root of System32. This is a known bug that was reported to Microsoft, and was supposed to be fixed for the RTM release, but wasn't. I use this command in my build script xcopy "%source%\mount\Windows\System32\Boot\*.*" %source%\mount\Windows\System32\*.* /e /y

copy all the files in the System32\Boot folder to the root of System32. This is a known bug that was reported to Microsoft, and was supposed to be fixed for the RTM release, but wasn't. EDIT: I use this command in my build script xcopy "%source%\mount\Windows\System32\Boot\*.*" %source%\mount\Windows\System32\*.* /e /y This should fix your winload.exe error

Get your WinXP CD, and look here: %ROOTOFCD%\SUPPORT\TOOLS\ here you will find a deploy.cab file. extract this out and have a look at these two files: deploy.chm ref.chm These two files will answer most of your questions.

From the download page : I can't find it anywhere, anyone have it, or know what it is?

His method won't help in this instance. Even if you had a WIM with a captured WinXp install (syspreped), it would still see the same problem when you laid the image down. The problem is with WinPE v2's diskpart or bootsect. Now to answer you question on how to to this: You have a base install of WinXP, configured how you want it. Then you configure your sysprep answer file for mini-setup. Then you run sysprep to prepare the OS. Then you bring the machine up into WinPE and run imagex to capture your new WIM. From this point you can deploy this image to other boxes.

kyor, What mother boards did you see this issue on? Do you know what chipset (north/south bridge) it is using? I'm trying to narrow down the issue to what chipsets are effected, because I think Microsoft is going to say that it is the chipset makers problem. Let us know what Microsoft says.

Have installed the vmware drivers into WinPE2? I have WinPE2 networking working in VMWare Workstation using the default nic devices. here is the list of vmware drivers I preload into winpe2: vmware-nic.inf vmxnet.inf vmx_svga.inf vmmouse.inf vmmemctl.inf

I have read that WinPE2 sometimes has issues on some BIOS's hard drive detection methods. If yours is set to "Auto" detect drives, set it to "Large" or disable LBA mode. See if that makes a difference.

I have WinPE2 networking working in VMWare Workstation using the default nic devices. here is the list of vmware drivers I preload into winpe2: vmware-nic.inf vmxnet.inf vmx_svga.inf vmmouse.inf vmmemctl.inf

Yes

try: bootsect /nt52 c: /force

The only thing I see that "may" be a problem, is the name of your wim file. Try naming it exactly like what the BCD config file shows.

It is the replacement for the recovery console.

can you post your BCD config? bcdedit -store %FULLPATH%\BCD EDIT: You can run bcdedit from Vista or PE2.

ok, a short background: I have WinPE working great. I am trying to install an unattended Win2k3 Server install. 1) I use diskpart to clean and partition the drive 2) Then use format to format to ntfs. 3) Then run the winnt32.exe with command line switches. Once it is done, it reboots to a black screen with a flashing cursor. Things I have tried (on PATA, SATA, SCSI, SAS): 1) running "bootsect /nt52 c: /force", right before the winnt32.exe setup is run 2) running "MbrFix /drive 0 fixmbr /yes", right before the winnt32.exe setup is run If I do the same steps on WinPE 2005 based on Win2k3SP1, it works fine. Any ideas? Am I missing something obvious?

Thanks for the updated info.

EDIT: removed

ok, make sure the Boot folder has a capital "B". And that the BCD file is all capitals. Also check your /var/log/messages. You may have to lookup how to do the "TFTP slash hack", it's where "\" are converted to "/" or something like that. Sorry I don't have more info, but I'm not a linux guy.

Here is an autoit3 GUI script for ImageX: ImageXGUI

that error message looks like you gave it the folder and not the inf file. a full example of a correct command line: "C:\Program Files\Windows AIK\Tools\PETools\peimg.exe" /inf:e:\Sil\name.inf C:\PE2\Mount\Windows is that what you used? All mass storage device drivers should come with a txtsetup.oem file, but this command requires a .inf file.

While you still have the WinPE2 wim file mounted, run this command: %PETOOLS%\peimg.exe /inf:%DRIVERINF% %MOUNTROOTDIR%\Mount\Windows

I found the regkey that needs to be added to run the win2k setup from WinPE2: Run this command to mount the reghive: reg load HKLM\PE-SFT %MOUNTROOTDIR%\Mount\Windows\system32\config\software Then load regedit and make these changes, you will have to add them because they aren't there. [HKEY_LOCAL_MACHINE\PE-SFT\Microsoft\Windows NT\CurrentVersion] "ProductID"="50293-000-1234567-12345" Then unmount the reghive with: reg unload HKLM\PE-SFT

wpeutil.exe DisableFirewall

No, I'm trying to figure out how to get it back. I just want to make sure everyone is having this problem, and it's not just something stupid I'm missing. Does anyone have the SRT package since RTM?