alfreire Posted March 15, 2013 Posted March 15, 2013 (edited) Hi... Can Win Toolkit mount Windows 7 PE (wim file)...? Can integrate drivers...?Thanks and regards... ;-) Edited March 15, 2013 by alfreire Quote
myselfidem Posted March 15, 2013 Posted March 15, 2013 (edited) WinToolkit can customize boot.wim and install.wim files, but not winpe.wim file: http://www.wincert.net/forum/topic/11080-bug-unable-to-create-an-iso-of-a-winpewim-file/#entry96788 ;-) Edited March 15, 2013 by myselfidem Quote
alfreire Posted March 15, 2013 Author Posted March 15, 2013 WinToolkit can customize boot.wim and install.wim files, but not winpe.wim file: http://www.wincert.net/forum/topic/11080-bug-unable-to-create-an-iso-of-a-winpewim-file/#entry96788 ;-)Thanks, friend... ;-) Quote
myselfidem Posted March 15, 2013 Posted March 15, 2013 (edited) Maybe you'll be interested? http://www.msfn.org/board/topic/149758-win7pe-se/page__view__findpost__p__955693 Regards ;-) *Edit: Maybe on the future, Legolash2o would add the possibility to WinToolkit to costumize winpe.wim file ? Edited March 15, 2013 by myselfidem Quote
alfreire Posted March 15, 2013 Author Posted March 15, 2013 Well... as I am a bit stubborn :cap: I made a test with wimpe.wim file to add drivers and work without problem... Thanks again... ;-) [3556] Caller did not request sparse mount[3556] Mounting new image.Wim: [C:\Make_PE3\win7pe_amd64\BOOT.WIM]Image Index: [1]Mount Path: [C:\W7T\Mount][3556] Wimserv process started for guid f8c38e4a-b66b-40f0-a464-8cf5915a68cf. Id is 924[924] [ INFO ] ImageUnmarshallHandle: Reconstituting wim at C:\Make_PE3\win7pe_amd64\BOOT.WIM.[924] [ INFO ] Mounted image at C:\W7T\Mount.[924] [ INFO ] Received unmount request for image with guid f8c38e4a-b66b-40f0-a464-8cf5915a68cf.[924] [ INFO ] Unmount for image at C:\W7T\Mount complete. Quote
myselfidem Posted March 15, 2013 Posted March 15, 2013 Yes!You made an test with boot.wim file. Wim: [C:\Make_PE3\win7pe_amd64\BOOT.WIM] Quote
alfreire Posted March 15, 2013 Author Posted March 15, 2013 (edited) Yes!You made an test with boot.wim file. Wim: [C:\Make_PE3\win7pe_amd64\BOOT.WIM]boot.wim is basically all WinPE image... Edited March 15, 2013 by alfreire Quote
myselfidem Posted March 15, 2013 Posted March 15, 2013 (edited) You are customizing WinRE (Microsoft Windows Recovery Environment (x64)) with boot.wim 1 file!Look at your image ! WinToolkit can't customize winpe.wim file! ;-) Edited March 15, 2013 by myselfidem Quote
myselfidem Posted March 15, 2013 Posted March 15, 2013 (edited) However, I made a full test successfully using instructions here: http://technet.microsoft.com/en-us/library/dd744533(WS.10).aspx Updating path to include dism, oscdimg, imagex C:\Program Files\Windows AIK\Tools\PETools\ C:\Program Files\Windows AIK\Tools\PETools\..\x86 C:\Program Files\Windows AIK\Tools\PETools\..\x86\Servicing;C:\Program Files\Windows AIK\Tools\PETools>cd..C:\Program Files\Windows AIK\Tools>cd x86C:\Program Files\Windows AIK\Tools\x86>copype.cmd x86 C:\winpe_x86===================================================Creating Windows PE customization working directory C:\winpe_x86=================================================== 1 fichier(s) copié(s). 1 fichier(s) copié(s).C:\Program Files\Windows AIK\Tools\PETools\x86\boot\bcdC:\Program Files\Windows AIK\Tools\PETools\x86\boot\boot.sdiC:\Program Files\Windows AIK\Tools\PETools\x86\boot\bootfix.binC:\Program Files\Windows AIK\Tools\PETools\x86\boot\etfsboot.comC:\Program Files\Windows AIK\Tools\PETools\x86\boot\fonts\chs_boot.ttfC:\Program Files\Windows AIK\Tools\PETools\x86\boot\fonts\cht_boot.ttfC:\Program Files\Windows AIK\Tools\PETools\x86\boot\fonts\jpn_boot.ttfC:\Program Files\Windows AIK\Tools\PETools\x86\boot\fonts\kor_boot.ttfC:\Program Files\Windows AIK\Tools\PETools\x86\boot\fonts\wgl4_boot.ttf9 fichier(s) copié(s)C:\Program Files\Windows AIK\Tools\PETools\x86\EFI\microsoft\boot\bcdC:\Program Files\Windows AIK\Tools\PETools\x86\EFI\microsoft\boot\fonts\chs_boot.ttfC:\Program Files\Windows AIK\Tools\PETools\x86\EFI\microsoft\boot\fonts\cht_boot.ttfC:\Program Files\Windows AIK\Tools\PETools\x86\EFI\microsoft\boot\fonts\jpn_boot.ttfC:\Program Files\Windows AIK\Tools\PETools\x86\EFI\microsoft\boot\fonts\kor_boot.ttfC:\Program Files\Windows AIK\Tools\PETools\x86\EFI\microsoft\boot\fonts\wgl4_boot.ttf6 fichier(s) copié(s) 1 fichier(s) copié(s).SuccessUpdating path to include peimg, cdimage, imagex C:\Program Files\Windows AIK\Tools\PETools\ C:\Program Files\Windows AIK\Tools\PETools\..\x86C:\winpe_x86>copy C:\winpe_x86\winpe.wim C:\winpe_x86\ISO\sources\boot.wim 1 fichier(s) copié(s).C:\winpe_x86>cd..C:\>Dism /Mount-Wim /Wimfile:c:\winpe_x86\ISO\sources\boot.wim /index:1 /MountDir:C:\winpe_x86\mountOutil Gestion et maintenance des images de déploiementVersion : 6.1.7600.16385Montage de l'image[==========================100.0%==========================]L'opération a réussi.C:\>copy c:\winpe_x86\ISO\bootmgr c:\winpe_x86\mount 1 fichier(s) copié(s).C:\>mkdir c:\winpe_x86\mount\bootC:\>xcopy /cherky C:\winpe_x86\ISO\boot C:\winpe_x86\mount\boot\C:\winpe_x86\ISO\boot\bcdC:\winpe_x86\ISO\boot\boot.sdiC:\winpe_x86\ISO\boot\bootfix.binC:\winpe_x86\ISO\boot\etfsboot.comC:\winpe_x86\ISO\boot\fonts\chs_boot.ttfC:\winpe_x86\ISO\boot\fonts\cht_boot.ttfC:\winpe_x86\ISO\boot\fonts\jpn_boot.ttfC:\winpe_x86\ISO\boot\fonts\kor_boot.ttfC:\winpe_x86\ISO\boot\fonts\wgl4_boot.ttf9 fichier(s) copié(s)C:\>copy "c:\program files\Windows AIK\Tools\x86\ImageX.exe" c:\winpe_x86\mount 1 fichier(s) copié(s).C:\>Del c:\winpe_x86\mount\boot\BCDC:\>Bcdedit /createstore c:\winpe_x86\mount\boot\BCDL'opération a réussi.C:\>Bcdedit /store c:\winpe_x86\mount\boot\BCD -create {bootmgr} /d "Boot Manager"L'entrée {bootmgr} a été correctement créée.C:\>Bcdedit /store c:\winpe_x86\mount\boot\BCD -set {bootmgr} device bootL'opération a réussi.C:\>Bcdedit /store c:\winpe_x86\mount\boot\BCD -create /d "WINPE" -application osloaderL'entrée {153b4f21-8d9a-11e2-9d06-0011d88ce374} a été correctement créée.C:\>Bcdedit /store c:\winpe_x86\mount\boot\BCD -set {153b4f21-8d9a-11e2-9d06-0011d88ce374} osdevice bootL'opération a réussi.C:\>Bcdedit /store c:\winpe_x86\mount\boot\BCD -set {153b4f21-8d9a-11e2-9d06-0011d88ce374} device bootL'opération a réussi.C:\>Bcdedit /store c:\winpe_x86\mount\boot\BCD -set {153b4f21-8d9a-11e2-9d06-0011d88ce374} path \windows\system32\winload.exeL'opération a réussi.C:\>Bcdedit /store c:\winpe_x86\mount\boot\BCD -set {153b4f21-8d9a-11e2-9d06-0011d88ce374} systemroot \windowsL'opération a réussi.C:\>Bcdedit /store c:\winpe_x86\mount\boot\BCD -set {153b4f21-8d9a-11e2-9d06-0011d88ce374} winpe yesL'opération a réussi.C:\>Bcdedit /store c:\winpe_x86\mount\boot\BCD -displayorder {153b4f21-8d9a-11e2-9d06-0011d88ce374} -addlastL'opération a réussi.C:\>Dism /Unmount-Wim /MountDir:C:\winpe_x86\mount /CommitOutil Gestion et maintenance des images de déploiementVersion : 6.1.7600.16385Fichier image : c:\winpe_x86\ISO\sources\boot.wimIndex de l'image : 1Enregistrement de l'image[==========================100.0%==========================]Démontage de l'image[==========================100.0%==========================]L'opération a réussi.C:\>Oscdimg -n -m -o -bC:\winpe_x86\Etfsboot.com C:\winpe_x86\ISO C:\winpe_x86\winpex86.isoOSCDIMG 2.55 CD-ROM and DVD-ROM Premastering UtilityCopyright © Microsoft, 1993-2007. All rights reserved.Licensed only for producing Microsoft authorized content.Scanning source treeScanning source tree complete (17 files in 8 directories)Computing directory information completeImage file is 150906880 bytes (before optimization)Writing 17 files in 8 directories to C:\winpe_x86\winpex86.iso100% completeStorage optimization saved 1 files, 2371584 bytes (2% of image)After optimization, image file is 148535296 bytesDone.C:\> Errors.txt using WinToolkitException:Open Files (20 Max):C:\zMount\bootmgrC:\zMount\imagex.exeC:\zMount\Windows\bfsvc.exeC:\zMount\Windows\fveupdate.exeC:\zMount\Windows\regedit.exeC:\zMount\Windows\system.iniC:\zMount\Windows\win.iniC:\zMount\Windows\WindowsShell.ManifestC:\zMount\Windows\wpeprofiles\all.wpfC:\zMount\Windows\wpeprofiles\core.wpfC:\zMount\Windows\winsxs\pending.xmlC:\zMount\Windows\winsxs\x86_wvmic.inf_31bf3856ad364e35_6.1.7600.16385_none_01b814f7adc00eda\IcCoinstall.dllC:\zMount\Windows\winsxs\x86_wvmic.inf_31bf3856ad364e35_6.1.7600.16385_none_01b814f7adc00eda\vmicres.dllC:\zMount\Windows\winsxs\x86_wvmic.inf_31bf3856ad364e35_6.1.7600.16385_none_01b814f7adc00eda\vmicsvc.exeC:\zMount\Windows\winsxs\x86_wvmic.inf_31bf3856ad364e35_6.1.7600.16385_none_01b814f7adc00eda\vmictimeprovider.dllC:\zMount\Windows\winsxs\x86_wvmic.inf_31bf3856ad364e35_6.1.7600.16385_none_01b814f7adc00eda\wvmic.infC:\zMount\Windows\winsxs\x86_wvmbushid.inf_31bf3856ad364e35_6.1.7600.16385_none_f08c80e00dbb37cf\vmbushid.sysC:\zMount\Windows\winsxs\x86_wvmbushid.inf_31bf3856ad364e35_6.1.7600.16385_none_f08c80e00dbb37cf\wvmbushid.infC:\zMount\Windows\winsxs\x86_wvmbus.inf_31bf3856ad364e35_6.1.7600.16385_none_3956fbc30b5af3ca\vmbus.sysC:\zMount\Windows\winsxs\x86_wvmbus.inf_31bf3856ad364e35_6.1.7600.16385_none_3956fbc30b5af3ca\vmbuscoinstaller.dllC:\zMount\Windows\winsxs\x86_wvmbus.inf_31bf3856ad364e35_6.1.7600.16385_none_3956fbc30b5af3ca\vmbuspipe.dllOpen Directories (20 Max):C:\zMount\bootC:\zMount\Program FilesC:\zMount\ProgramDataC:\zMount\UsersC:\zMount\WindowsC:\zMount\Windows\BootC:\zMount\Windows\BrandingC:\zMount\Windows\FontsC:\zMount\Windows\fr-FRC:\zMount\Windows\GlobalizationC:\zMount\Windows\HelpC:\zMount\Windows\infC:\zMount\Windows\L2SchemasC:\zMount\Windows\LogsC:\zMount\Windows\Microsoft.NETC:\zMount\Windows\PolicyDefinitionsC:\zMount\Windows\resourcesC:\zMount\Windows\schemasC:\zMount\Windows\securityC:\zMount\Windows\servicingC:\zMount\Windows\System32Running Processes:Agent, armsvc, Ati2evxx, audiodg, CCC, csrss, dllhost, dwm, EuWatch, Everything, explorer, GuardAgent, Idle, lsass, lsm, MOM, MsMpEng, msseces, NisSrv, RtHDVCpl, SeaPort, SearchFilterHost, SearchIndexer, SearchProtocolHost, services, sidebar, smss, spoolsv, svchost, System, taskeng, taskhost, TrayNotify, TuneUpUtilitiesApp32, TuneUpUtilitiesService32, vds, vspdfprsrv, wimserv, wininit, winlogon, WinToolkit, WLIDSVC, WLIDSVCM, wmpnetwk, WUDFHost, XSnapShotTip, WinToolkit can't customize winpe.wim file! Edited March 15, 2013 by myselfidem Quote
alfreire Posted March 15, 2013 Author Posted March 15, 2013 (edited) But what is winpe.wim...? Windows 7 PE only has a boot.wim into sources folder, not...? I meant to integrate drivers into Windows PE (boot.wim), and some more, not to customize Windows PE as if an Operating System... Note: I only use Win Toolkit to customize Install.wim or Boot.wim files from Windows 7... Edited March 15, 2013 by alfreire Quote
myselfidem Posted March 15, 2013 Posted March 15, 2013 (edited) boot.wim files and winpe.wim files are different. http://technet.microsoft.com/en-us/library/cc709665(v=ws.10).aspx About WinPE Image:A Windows PE RAM disk boots directly into memory and is assigned the drive letter X, which does not correspond to the media (for example, a UFD or a CD-ROM) from which you booted. Ensure that you have sufficient memory to support the size of your Windows PE image plus any additional memory requirements, for example, if you plan on running any customized applications that need additional working memory. Edited March 15, 2013 by myselfidem Quote
myselfidem Posted March 15, 2013 Posted March 15, 2013 Well... as I am a bit stubborn :cap: I made a test with wimpe.wim file to add drivers and work without problem... [3556] Caller did not request sparse mount[3556] Mounting new image.Wim: [C:\Make_PE3\win7pe_amd64\BOOT.WIM]Image Index: [1]Mount Path: [C:\W7T\Mount][3556] Wimserv process started for guid f8c38e4a-b66b-40f0-a464-8cf5915a68cf. Id is 924[924] [ INFO ] ImageUnmarshallHandle: Reconstituting wim at C:\Make_PE3\win7pe_amd64\BOOT.WIM.[924] [ INFO ] Mounted image at C:\W7T\Mount.[924] [ INFO ] Received unmount request for image with guid f8c38e4a-b66b-40f0-a464-8cf5915a68cf.[924] [ INFO ] Unmount for image at C:\W7T\Mount complete. Like many guys there is an confusion about boot.wim (2 images) and winpe.wim files! And you asked about winpe.wim ! Quote
alfreire Posted March 15, 2013 Author Posted March 15, 2013 Sorry, I've explained badly... :dizzy: Quote
alfreire Posted March 15, 2013 Author Posted March 15, 2013 (edited) boot.wim files and winpe.wim files are different. http://technet.microsoft.com/en-us/library/cc709665(v=ws.10).aspx About WinPE Image:Hey... But then my boot.wim file is wimpe.wim, because when you boot appears as drive X: (load into RAM)...I made Win PE ISO with Make_PE3 https://sites.google.com/a/rmprepusb.com/www/tutorials/make_pe3 Edited March 15, 2013 by alfreire Quote
myselfidem Posted March 16, 2013 Posted March 16, 2013 Hey... But then my boot.wim file is wimpe.wim... No. boot.wim file is not winpe.wim file ! The boot.wim files are Inside your Windows 7 DVD. winpe.wim file is Inside Windows OPK or Windows AIK Quote
alfreire Posted March 16, 2013 Author Posted March 16, 2013 (edited) No. boot.wim file is not winpe.wim file ! The boot.wim files are Inside your Windows 7 DVD. winpe.wim file is Inside Windows OPK or Windows AIKOk, understood... ;-) Edited March 16, 2013 by alfreire Quote
x23piracy Posted March 16, 2013 Posted March 16, 2013 Hi, maybe that helps? http://www.wincert.net/forum/topic/11055-installation-of-windows-7-over-network-boot-pxe/#entry96470 Look at the part: Prepare WinPE to Start Windows Setup Greetz X23 Stimpy 1 Quote
x23piracy Posted March 17, 2013 Posted March 17, 2013 Hey, also look here: http://www.wincert.net/forum/topic/11137-tool-pex%C2%B2%C2%B3-little-winpe-helper/ Greetz X23 Stimpy 1 Quote
Recommended Posts
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.