acyang Posted March 27, 2007 Posted March 27, 2007 1. I can't find "bootsect.exe" on my UFD. I followed the steps from WAIK Walkthrough "Create a Bootable Windows PE RAM Disk on UFD", (In LRMOPK_TW.iso, we can find bootsect.exe in the BOOT folder) but I didn't find bootsect.exe in the BOOT folder on my UFD. So I copied it from "C:\Program Files\Windows AIK\Tools\PETools\x86" to BOOT folder.That's correct you have to copy it from your opk kit to your WinPE CD or to a network share.2. The winnt32.exe will close after "Preparing installation". I followed the steps you mentioned above, I run winnt32.exe without unattended file, I typed the regist key then the setup program went on. But after "Preparing installation", the setup program closed and return to the command line promote.could somebody do me a favort?I've bothered about this for months .Normaly, after typing in the reg key the setup Program copies the necessary files to your harddisk andreturn to the command prompt. after that you have to exit winpe. type exit in winpe and remove your winpe source (i.e. USB Stick, CD)Hi,kyorThanks for your help.Now I can complete my winpe UFD.By the way,at first I typed the following commond %SOURCE%\i386\winnt32.exe /syspart:c: /unattend:%SOURCE%\i386\WINNT.SIFAfter the computer reboot, the setup program asked me to put "windows xp sp2" setup cd into the cdrom.So I used /makelocalsource and /tempdrive:c: parameters,the full commond is%SOURCE%\i386\winnt32.exe /syspart:c: /unattend:%SOURCE%\i386\WINNT.SIF /makelocalsource /tempdrive:c: the unattend setup went on successfully, just like it run from unattend setup CD.Is it possible run a unattend Xp setup under winpe 2.0 ram disk on UFD without copying all source files to the Hard disk?
kyor Posted March 27, 2007 Author Posted March 27, 2007 I think it's not possible. You need the Harddisk for the necessary installation files
twalk482 Posted April 10, 2007 Posted April 10, 2007 (edited) Did you try just creating another folder in your mount or mount\Windows folder before the Prepare your image step?This would compress it on the .WIM file ... it ceratinly would increase the boot time.I haven't seen if there is a maximum size for the RAM Drive used (I don't think that information is in TFM)I am actually going to try this today. Edited April 10, 2007 by twalk482
twalk482 Posted April 11, 2007 Posted April 11, 2007 So, this worked (having the i386 source on the RAMDrive). However, I did not have the option of a USB Key ... So, I created an ISO I added the logic to get the "WINSRC" directory on the RAMDrive to the batch file I have to create WinPE 2.0Should be adble to modify the SET statements here to make it work for youSET ARCH=x86SET UFDRIVE=G:SET WAIKTOOLS_DIR=C:\Program Files\Windows AIK\ToolsSET PETOOLS_DIR=%WAIKTOOLS_DIR%\PEToolsSET PEROOT_DIR=D:\WINPE2.0SET PETEMP_DIR=%PEROOT_DIR%\winpe_%ARCH%SET WINSRC_DIR=D:\2003R2SET STARTNET_FILE=D:\STARTNET.CMDIF EXIST %PETEMP_DIR% (RD /S /Q %PETEMP_DIR%) MD %PETEMP_DIR%MD %PETEMP_DIR%\ISOMD %PETEMP_DIR%\MOUNTCOPY "%PETOOLS_DIR%\%ARCH%\BOOTMGR" "%PETEMP_DIR%\ISO"COPY "%PETOOLS_DIR%\%ARCH%\BOOTMGR.EFI" "%PETEMP_DIR%\ISO"COPY "%PETOOLS_DIR%\%ARCH%\BOOT\ETFSBOOT.COM" "%PETEMP_DIR%"COPY "%PETOOLS_DIR%\%ARCH%\BOOT\EFISYS.BIN" "%PETEMP_DIR%"XCOPY /CHERKY "%PETOOLS_DIR%\%ARCH%\BOOT" "%PETEMP_DIR%\ISO\BOOT\"XCOPY /CHERKY "%PETOOLS_DIR%\%ARCH%\EFI" "%PETEMP_DIR%\ISO\EFI\"MKDIR "%PETEMP_DIR%\ISO\SOURCES"COPY "%PETOOLS_DIR%\%ARCH%\WINPE.WIM" "%PETEMP_DIR%\WINPE.WIM"COPY "%PETOOLS_DIR%\%ARCH%\WINPE.WIM" "%PETEMP_DIR%\ISO\SOURCES\BOOT.WIM""%WAIKTOOLS_DIR%\%ARCH%\IMAGEX" /MOUNTRW %PETEMP_DIR%\WINPE.WIM 1 %PETEMP_DIR%\MOUNT"%PETOOLS_DIR%\PEIMG" /install=WinPE-HTA-Package %PETEMP_DIR%\MOUNT\WINDOWS"%PETOOLS_DIR%\PEIMG" /install=WinPE-MDAC-Package %PETEMP_DIR%\MOUNT\WINDOWS"%PETOOLS_DIR%\PEIMG" /install=WinPE-Scripting-Package %PETEMP_DIR%\MOUNT\WINDOWS"%PETOOLS_DIR%\PEIMG" /install=WinPE-XML-Package %PETEMP_DIR%\MOUNT\WINDOWS"%PETOOLS_DIR%\PEIMG" /LIST %PETEMP_DIR%\MOUNT\WINDOWSCOPY "%WAIKTOOLS_DIR%\%ARCH%\IMAGEX.EXE" %PETEMP_DIR%\ISO\ECHO D|XCOPY /CHERKYS "%WAIKTOOLS_DIR%\%ARCH%\SERVICING" %PETEMP_DIR%\ISO\SERVICINGCOPY %STARTNET_FILE% %PETEMP_DIR%\MOUNT\WINDOWS\SYSTEM32MD %PETEMP_DIR%\MOUNT\WINSRC\I386ECHO D|XCOPY /CHERKYS "%WINSRC_DIR%\I386\*.*" %PETEMP_DIR%\MOUNT\WINSRC\I386"%PETOOLS_DIR%\PEIMG" /PREP /F %PETEMP_DIR%\MOUNT\WINDOWS:UNMOUNT"%WAIKTOOLS_DIR%\%ARCH%\IMAGEX" /UNMOUNT %PETEMP_DIR%\MOUNT /COMMITCOPY %PETEMP_DIR%\WINPE.WIM %PETEMP_DIR%\ISO\SOURCES\BOOT.WIM:COPYUFDXCOPY /CHERKYS %PETEMP_DIR%\*.* %UFDRIVE%GOTO :END:MAKEISOOSCDIMG -N -M -O -B%PETEMP_DIR%\ETFSBOOT.COM %PETEMP_DIR%\ISO %PETEMP_DIR%\WINPE_%ARCH%.ISO:ENDHere would be the line(s) that I added to my custom STARTNET.CMD CD /D X:\WINSRC\i386WINNT32.EXE /DUDISABLE /SX:\WINSRC\i386 /SYSPART:C /TEMPDRIVE:C /MAKELOCALSOURCE /UNATTEND:C:\UNATTEND.TXT
randalldale Posted May 29, 2007 Posted May 29, 2007 Well I'm still gettting the error even with the fix to the diskpart.txt file. Oh and I have Intel based boards that are on the most current BIOS.
toastycheese678 Posted June 4, 2007 Posted June 4, 2007 (edited) I am currently having problems with WinPE 2.0 and XP install. I am trying to use one WinPE disk to install both XP and Vista. I have the disk set so that the Vista install initiates. Then I create the partitions I want through Vista Setup. If I hit next then Vista installs on the C: Partition. If I exit the Vista Installation after the partitions are created then XP tries to install on the C: Partition.After creating the partitions and exiting the Vista Setup I am sitting with a 40 GB C Partition and a 120 GB D Partition. I then run the following commands:DiskpartSelect Disk 0Select Partition 1Assign Letter CActiveExitformat c: /fs:ntfs /q /y /v:Boot\\XP\I386\winnt32 /s:\\XP\I386 /unattend:\\XP\I386\winnt.sif /dudisable /syspart:cThis copies over the installation files for Windows XP to the local machine. The computer is then restartedImmediately following the POST i receive the following message:A disk read error occurredPress Ctrl+Alt+Del to restartI tried updating the bios of the motherboard and using bootsect.exe /nt52 c: /force, and changing the disk type to Auto, CHS, Large, LHSIve also integrated the following registry entries into my WinPE diskreg load HKLM\PE-SYS c:\Winpe_x86\Mount\Windows\system32\config\systemReg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v LessThan4GB /d 0 /fReg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v Between4_8GB /d 0 /fRegAdd "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v Between8_32GB /d 0 /fReg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v GreaterThan32GB /d 0 /freg unload HKLM\PE-SYSAll result in the same errorAny ideas? Edited June 4, 2007 by toastycheese678
killerb255 Posted June 7, 2007 Posted June 7, 2007 I am currently having problems with WinPE 2.0 and XP install. I am trying to use one WinPE disk to install both XP and Vista. I have the disk set so that the Vista install initiates. Then I create the partitions I want through Vista Setup. If I hit next then Vista installs on the C: Partition. If I exit the Vista Installation after the partitions are created then XP tries to install on the C: Partition.After creating the partitions and exiting the Vista Setup I am sitting with a 40 GB C Partition and a 120 GB D Partition. I then run the following commands:DiskpartSelect Disk 0Select Partition 1Assign Letter CActiveExitformat c: /fs:ntfs /q /y /v:Boot\\XP\I386\winnt32 /s:\\XP\I386 /unattend:\\XP\I386\winnt.sif /dudisable /syspart:cThis copies over the installation files for Windows XP to the local machine. The computer is then restartedImmediately following the POST i receive the following message:A disk read error occurredPress Ctrl+Alt+Del to restartI tried updating the bios of the motherboard and using bootsect.exe /nt52 c: /force, and changing the disk type to Auto, CHS, Large, LHSIve also integrated the following registry entries into my WinPE diskreg load HKLM\PE-SYS c:\Winpe_x86\Mount\Windows\system32\config\systemReg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v LessThan4GB /d 0 /fReg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v Between4_8GB /d 0 /fRegAdd "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v Between8_32GB /d 0 /fReg Add "HKLM\PE-SYS\ControlSet001\Services\vds\Alignment" /t Reg_Dword /v GreaterThan32GB /d 0 /freg unload HKLM\PE-SYSAll result in the same errorAny ideas?There is a website that hosts hotfixes that Microsoft doesn't give out publicly:In this case, you can get this:http://support.microsoft.com/kb/931760from here:http://thehotfixshare.net/download/index.p...h/Windows%20XP/Try slipstreaming this fix into your installation to avoid the registry edits.
killerb255 Posted June 7, 2007 Posted June 7, 2007 I'm having an extremely weird problem when I try to install XP using a network share and WinPE 2.0.Here's what I do (even after using the fix I posted above):diskpartselect disk 0cleancreate partition primaryactiveassign letter cformatexitnet use t: \\%sharename%\xppro <<asks for credentials...I enter themt:\cd wkst << has an i386 folder as well as several text files used as unattended setup files.wkst32.bat %textfile%.txtInside the wkst32.bat:@echo offSET TRACK=%1echo %TRACK%.txtt:\i386\winnt32 /m:t:\i386\ /syspart:c: /tempdrive:c: /unattend:t:\wkst\%TRACK%.txtexitAnyway, after running this, the setup files copy correctly, then the textmode part runs correctly. Once the GUI comes up, I get the following error message:Fatal Error-SXS.DLL: Syntax error in manifest or policy file C:\$win_nt$.~ls\I386\asms\6000\MSFT\VCRTL\VCRTL.MAN on LINE 11A component's file does not match the verification information present in the component manifestNow here's the kicker:The EXACT same source files work fine when using a variation of a DOS-based Ultimate Boot CD. The only difference is that winnt.exe is used with a wkst.bat file:@echo offSET TRACK=%1echo %TRACK%.txtt:\i386\winnt /s:t:\i386 /t:c:\ /u:t:\wkst\%TRACK%.txtAny ideas?
killerb255 Posted June 11, 2007 Posted June 11, 2007 (edited) Never mind--I solved the problem.wkst32 edits:Omissions in bold. Additions in italicst:\i386\winnt32 /m:t:\i386\ /syspart:c: /tempdrive:c: /makelocalsource /unattend:t:\wkst\%TRACK%.txtIn any case, slipstreaming the hotfix for the Vista diskpart craziness combined with this worked like a charm! Edited June 11, 2007 by killerb255
HJW Posted July 3, 2007 Posted July 3, 2007 Someone here who wants to make a little walkthrough how to use winpe2.0 with xp setup.. I am looking for a stepbystep guide - otherwise I know i will not suceed in doing this ;(
kyor Posted July 4, 2007 Author Posted July 4, 2007 (edited) @HJWSummarydo the following only for xp and win2003 installations.On vista you will get performance problems with raid controllersif you use the fixbootxp.reg1. run winpe 2.02. regedit /s fixbootxp.reg (attached in this post)3. use diskpart (you can use diskpart /s diskpart.ini if you want to format your HDD automatically)4. bootsect /nt52 c: (you get bootsect from OPK Kit)5. start winnt32.exe example t:\i386\winnt32 /m:t:\i386\ /syspart:c: /tempdrive:c: /makelocalsource /unattend:t:\unattend.txtHINT:When you do this kind of installation you get a error message in Windows when it's installed (see picture). But this is normal and doesn't affectthis Installation. I haven't found another way. When you use the chkdsk in GUI Mode you didn't get a error messagehttp://support.microsoft.com/kb/931760/enGreetings kyorfixbootxp.regdiskpart.ini Edited July 21, 2007 by kyor
JuMz Posted July 20, 2007 Posted July 20, 2007 Wow. This is an amazing thread and well worth the 3-page read. I thank you guys for sharing this information!
Matt A. Tobin Posted December 4, 2007 Posted December 4, 2007 Heh old thread... anyway i created an XP install image using imagex and winpe2.0I programed a simple GUI to execute commands like quickformat diskpart and bootsect and such...anyway.. i use an nLited XP install so its all automated so to prep a drive to capture the install image.... run: winnt32 /unattend:winnt.sif /makelocalsource /noreboot (you could just run winnt32 /makelocalsource and enter your licence info and whatever...)then I use ImageX to capture that imageand what i end up with is an image all ready for deployment under winpe2.0then when i pop in my disc it boots to winpe and my custom shell launcher doober comes up...Diskpart (or just a quick format if the partition exists)apply imagebootsect /nt52more or less three clicks and a Y (to confirm i want to quick format) and i am ready to reboot and it does the normal blue textmode then gui then done.. in like less then 25 min...My PE Shell has the following commandsApply image (I call it Install Windows)Quick Format C:Run Disk Partitioner (Diskpart till i find a WinPE2 compadible diskpart gui)Apply NT5x Boot Sector (bootsect /nt52)Open Command Prompt (cmd.exe)the kickass ImageX GUI (for imageing jobs beyond the simple apply image)Open Registry Editor (regedit.exe) Everyone needs a registry editor avilableand a readme.. which i havent programed yet because im a lazy son of a b***hit looks nifty the coding is horrific but it all worksbut that winnt32 /makelocalsource then capture with ImageX should work... just be sure you apply the NT5x bootsector so it loads NTLDR if you format and not do bootsect it will want to run BOOTMGR and windows xp doesnt come with it...this method should work with win2k and server03 also
JuMz Posted January 4, 2008 Posted January 4, 2008 You should note that if you are using Windows XP Table PC or Media Center (or .Net option in the PRO), you should have /makelocalsource:allThis will copy the 'CMPNENTS' folder also...
blchee Posted March 12, 2008 Posted March 12, 2008 Hi ,I'm trying to create a server deployment image for Windows 2003 with WinPE 2.1.My steps are: 1. Boot into Winpe2.12. delete partition using diskpart3. configure HP Disk Array configuration and create an array4. create new partition5. format disk6. install from commandline (X:\W2K3\I386\WINNT32.EXE /syspart:c: /s:X:\W2K3\I386 /unattend:X:\DiskProfilesA\unattend.txt /makelocalsourcestep 2 to 6 is run from a vbscript that I had created and compiled as a .exe file and being called out from startnet.cmd. The W2K3 installation files are copied to a new folder named W2K3 under the winpe\mount folder.My problem is when I include the W2K3 folder, winpe will load but immediately finish loading, it prompt error and notexecute the startnet.cmd. (I guess it straight jump to the w2k3 setup, but at that point the harddisk is not parepare yethence it gives error)But if I exclude the W2K3 folder, I have no problem, winpe will load then trigger the startnet.cmd and I can type and execute some array configuration manually from the command prompt.Is anyone have any idea why I can't include the W2K3 installation files together with winpe?I have no problem with this when I use winpe 2005 in our previous image version.Thanks!!
Recommended Posts
Please sign in to comment
You will be able to leave a comment after signing in
Sign In Now