Richie Firestorm Posted March 25, 2009 Share Posted March 25, 2009 Is there any way to cut down a WinPE wim image that will load into RAM for calling an XP install from WDS?I've got it working on computers with over 384mb, but I have a large number of computers with 256mb (less with shared VGA) that networking fails to work on.This is a limitation with WinPE, so I was wondering if it was possible to chop out everything except the ability to boot from PXE then call the wim image from WDSI know I could buld a bootable USB drive to do this, but it would be better to just PXE boot WinPE which would then call the XP wim.Any ideas or is it just not possible? Link to comment Share on other sites More sharing options...
Richie Firestorm Posted March 26, 2009 Author Share Posted March 26, 2009 Ok, I've managed to build both a USB and CD WinPE 2 that installs fine on PCs >=512mb.However, I'm having the same problem with the <=256mb PCs. It dawned on me that the USB/CD WinPE is still loading the RAMDisk version, so I need to know how to create a "flat file" version. Anyone know how I can do this? Link to comment Share on other sites More sharing options...
allanf Posted March 27, 2009 Share Posted March 27, 2009 There's a Walk-thorugh titled "Boot Windows PE from CD-ROM"(... as opposed to booting from RAM disk.)This walkthrough describes how to boot Windows PE directly from CD-ROM/DVD-ROM media but not into a RAM disk. This method enables you to start a computer that has fewer than 512 megabytes (MB) of memory for the purpose of deployment or recovery.From the 'Windows PE Tools Command Prompt':imagex /apply <your .wim> <your index number> <your directory>Then the boot info is added to the directory.copy <bootmgr> <your directory>bootmgr can be found at, for example:C:\Program Files\Windows AIK\Tools\PETools\x86\bootmgrorC:\winpe_x86\ISO\bootmgrThen:mkdir <your directory>\bootcd /d <your directory>\Windows\System32bcdedit /createstore <your directory>\boot\BCDbcdedit ... etc... etc... from the Walk-throughNote that the bcdedit used is from the applied image and, therefore, the applied image must be the same architecture as the current architecture.Then create the .iso.oscdimg -n -m -o -b<etfsboot.com> <your directory> <your new ISO directory>/<your ISO name>.isoetfsboot.com can be found at, for example:C:\Program Files\Windows AIK\Tools\PETools\x86\boot\etfsboot.comorC:\winpe_x86\etfsboot.comRegards Link to comment Share on other sites More sharing options...
Richie Firestorm Posted March 28, 2009 Author Share Posted March 28, 2009 Thanks for that info.I've managed to come to that conclusion myself (tested and working on a computer with 220mb RAM)I did the following:1. Created a WinPE 2.0 CD (not RAMDisk version)2. Booted client PC with the WinPE CD3. Mapped to a network share that had my prebuilt (and pre-sysprepped) XP WIM file4. Ran diskpart with the following: select disk 0 clean create partition primary active assign letter=c format fs=ntfs quick exit5. imagex.exe /apply <mapped drive>\xp.wim 1 c:6. once download completed, exited cmd prompt and PC rebooted into sysprep stage of XP installationThis is probably the best I can manage, unless there is some way of PXE booting to a really tiny WinPE that provides networking, diskpart and the imagex tools Link to comment Share on other sites More sharing options...
killerb255 Posted March 30, 2009 Share Posted March 30, 2009 It is possible to make a WinPE 2.1 flat file disc.Follow the instructions here, for the most part (special thanks to paxamime for going through the trouble to make those batch files in the first place!):http://www.msfn.org/board/index.php?s=&...st&p=577244However, you will need to make these modifications:1) On 2Mount.bat, change boot.wim to winpe.wim.2) Create a new batch to run after 5Unmount.bat called 6Apply.bat with the following:REM 6-Apply.batREM This will apply the winpe.wim image to a new directory called winpe_flat.REM No mounting or unmounting of images are necessary in a flat file structure.%systemdrive%echo Applying the current winpe.wim to C:\PE\winpe_flat to create a flat-file structure.mkdir c:\PE\winpe_flatcd \cd %programfiles%\Windows AIK\Tools\x86ImageX /apply c:\PE\winpe_x86\winpe.wim 1 c:\PE\winpe_flatecho Adding a boot directory to C:\PE\winpe_flatmkdir c:\PE\winpe_flat\bootxcopy c:\PE\winpe_x86\ISO\boot]*.* /e /f c:\PE\winpe_flat\boot\pause3) Make a 7Bootloader.bat file with the following contents:@echo offecho 7-Bootloader.batecho This will create a new BCD database for your flat-file PE disc.:STEP1set peiso=%systemdrive%\PE\winpe_flatgoto STEP2:STEP2echo Deleting the existing BCD directory and preparing to create a new one.del C:\PE\winpe_flat\boot /qgoto STEP3:STEP3echo Creating a new bcdBcdedit /createstore %peiso%\boot\BCDBcdedit /store %peiso%\boot\BCD /create {bootmgr} /d "Boot Manager"Bcdedit /store %peiso%\boot\BCD /set {bootmgr} device bootBcdedit /store %peiso%\boot\BCD /create /d "WinPE" /application OSLoader > guid.txtgoto STEP4:STEP4echo The previous command returns a GUID value.echo The next command parses the GUID and adds it to the remaining commands.for /f "tokens=3" %%h in (guid.txt) do (set guid=%%h)goto STEP5:STEP5Bcdedit /store %peiso%\boot\BCD /set %guid% osdevice bootBcdedit /store %peiso%\boot\BCD /set %guid% device bootBcdedit /store %peiso%\boot\BCD /set %guid% path \windows\system32\winload.exeBcdedit /store %peiso%\boot\BCD /set %guid% systemroot \windowsBcdedit /store %peiso%\boot\BCD /set %guid% winpe yesBcdedit /store %peiso%\boot\BCD /set %guid% detecthal yesBcdedit /store %peiso%\boot\BCD /displayorder %guid% /addlastecho The custom boot loader has been created.pause4) Change 6MakeISO.bat to 8MakeISO.bat.5) Burn ISO to CD.6) Boot from it. You will NOT be asked to "Press any key to boot from CD or DVD..." Link to comment Share on other sites More sharing options...
allanf Posted March 30, 2009 Share Posted March 30, 2009 This is probably the best I can manage, unless there is some way of PXE booting to a really tiny WinPE that provides networking, diskpart and the imagex toolspeimg /prepandimagex /exportBoth help to reduce the size of the final boot.wim (and .iso). The first one removes unwanted 'staged' packages. The second removes extraneous code created when customizing the image.Regards Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now