paxamime

Windows RE is nothing more than the repair tools portion of Windows PE. As far as networking capability, it is already there. Perhaps the way that you are getting your Windows RE is where you are having trouble. The way that I do it is with the following command: imagex /compress None /check /boot /scroll /export F:\sources\boot.wim 2 C:\Pe\WinREFromCD.wim Maybe it is just me but I have never had any problems with standard networking inside of the WinRE environment. To enable the networking there are a couple of things you can do, manually enable it, or my personal favorite.. Via an Asynchronous.xml file: <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <EnableNetwork>true</EnableNetwork> <EnableFirewall>true</EnableFirewall> </component> </settings> </unattend> If this does not work for you guys let me know and I will dive into it deeper and see where you are having problems.

At this point the best route is to install a third-party application (in other words not explorer.exe) to handle launching applications. My personal favorite is Rocket Dock because of how simple it is to use and customize. There are plenty of other ones out there but Rocket Dock is portable and looks pretty at the same time. I am not sure what your level you are at with customizing Windows PE but the easiest way to launch the shell is to use winpeshl.ini in the Windows\System32 directory. You will basically replace the path in this file with that of your shell. If your Windows PE does not have this file you can create it by making a text file and renaming it then adding this into it: [LaunchApp] AppPath = %SYSTEMDRIVE%\Windows\RocketDock\RocketDock.exe [LaunchApps] This assumes that you add in the RocketDock application directory into the Windows directory for Windows PE. EDIT:: Here are some other good launchers. Not all of them can be used in Windows PE but you can check them out and see if there are is another one you like more than RocketDock http://www.osattack.com/alternative-shell/...rs-for-windows/

Thanks for the input! I have been feeling the same way. Thank you for reinforcing my belief.

I am creating a disk of utilities for some friends and I am wanting other peoples opinions on what is the best way to organize the files. There are both x86 and x64 applications as well as components. Is it better to put both files in the same directory? Or should I separate them out into x86 and x64 subfolders? For example: Utility 1 (Folder) Utility 1 - x64.exe Utility 1 - x86.exe Or Utility 1 (Folder) x64\ (Sub Directory) Utility 1 - x64.exe x86\ (Sub Directory) Utility 1 - x86.exe Does this make sense to anyone else? Even if you have no preference of what you think would be better let me know.

More than likely you are pressing the wrong key on the computer to boot the Pendrive. Other boot keys to try are Esc, F1 or F2. Typically it is HP's that use F10 but a more universal option is just simply Esc.

For those that don't know how to add Defrag command line to Windows PE, Here is how you can do it. You can see the full version of it at OS Attack. As far as making the GUI work I am sure that it is possible (I don't think its .net based) but it has multiple dependencies you would also have to add and that gets out of control for the pay-off of a GUI. Registry Keys To Add To WinPE: Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\EXTERNALSOFTWARE\Classes\CLSID\{80EE4901-33A8-11d1-A213-0080C88593A5}] @=”Defrag NTFS engine” [HKEY_LOCAL_MACHINE\EXTERNALSOFTWARE\Classes\CLSID\{80EE4901-33A8-11d1-A213-0080C88593A5}\LocalServer32] @=hex(2):25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,00,6f,00,74,00,25,\ 00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,66,00,\ 72,00,67,00,4e,00,74,00,66,00,73,00,2e,00,65,00,78,00,65,00,00,00 [HKEY_LOCAL_MACHINE\EXTERNALSOFTWARE\Classes\CLSID\{80EE4902-33A8-11d1-A213-0080C88593A5}] @=”Defrag FAT engine” [HKEY_LOCAL_MACHINE\EXTERNALSOFTWARE\Classes\CLSID\{80EE4902-33A8-11d1-A213-0080C88593A5}\LocalServer32] @=hex(2):25,00,73,00,79,00,73,00,74,00,65,00,6d,00,72,00,6f,00,6f,00,74,00,25,\ 00,5c,00,73,00,79,00,73,00,74,00,65,00,6d,00,33,00,32,00,5c,00,44,00,66,00,\ 72,00,67,00,46,00,61,00,74,00,2e,00,65,00,78,00,65,00,00,00 For these files you can copy them from a Vista machine but make sure that the Vista service pack version matches the WinPE service pack version. Make sure to place them in the same locations as they are located on Vista. Files To Add: Windows\System32\Defrag.exe Windows\System32\dfrgfat.exe Windows\System32\DfrgNtfs.exe Windows\System32\DfrgRes.dll Windows\System32\en-US\Defrag.exe.mui Windows\System32\en-US\DfrgFat.exe.mui Windows\System32\en-US\DfrgNtfs.exe.mui Windows\System32\en-US\DfrgRes.dll.mui

For those that are looking at working with Windows PE 3.0 and have not had the time to research them you can check out the updated commands at OS Attack. I copied these commands from the post there. http://www.osattack.com/windows/commands-f...-windows-pe-30/ Create winpe_x86 directory in C:\PE (this WILL delete it if the directory already exists): rd /s/q C:\PE\winpe_x86 cd “c:\Program files\windows aik\tools\petools” call copype.cmd x86 C:\PE\winpe_x86 Mount the WIM image: cd “C:\Program Files\Windows AIK\Tools\x86\Servicing” DISM.exe /Mount-Wim /WimFile:C:\PE\winpe_x86\ISO\sources\boot.wim /index:1 /MountDir:C:\PE\winpe_x86\mount UnMount the WIM image commiting changes: cd “C:\Program Files\Windows AIK\Tools\x86\Servicing” DISM.exe /unmount-Wim /MountDir:C:\PE\winpe_x86\mount /Commit Add packages into your WIM, this can be edited to only add in what you need to reduce the size of the WIM: cd “C:\Program Files\Windows AIK\Tools\x86\Servicing\” dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe.cab” dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-wmi.cab” dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-hta.cab” dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-legacysetup.cab” dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-mdac.cab” dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-scripting.cab” dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-setup.cab” dism /image:C:\PE\winpe_x86\mount /Add-Package /PackagePath:”C:\Program Files\Windows AIK\Tools\PETools\x86\WinPE_OCs\winpe-wds-tools.cab” Check what packages are installed: cd “C:\Program Files\Windows AIK\Tools\x86\Servicing\” dism /image:c:\PE\winpe_x86\mount\ /Get-Packages UnMount the WIM image discarding changes: cd “C:\Program Files\Windows AIK\Tools\x86\Servicing” DISM.exe /unmount-Wim /MountDir:C:\PE\winpe_x86\mount /discard Create Windows PE ISO: cd “C:\Program Files\Windows AIK\Tools\x86″ oscdimg -n -bc:\PE\winpe_x86\etfsboot.com c:\PE\winpe_x86\ISO c:\PE\winpe_x86\winpe_x86.iso

You can't use both versions on the same machine but you can modify a PE 2.0 with the PE 3.0 WAIK. I actually was doing quite a bit with it before I actually built a full PE 3.0.

That is the WAIK which is easily obtainable. What we are looking for is the OEM Preinstallation Kit (I think thats right) which is more commonly called the OPK.

I still havent been able to find the OPK beta. Has anyone else had better luck?

I am surprised no one has posted this yet but the WAIK Beta for PE 3.0 is available for download. There have been quite a few changes to it most of which look pretty good. My internet sucks too bad right now to find it again on the MS site but they have the link at OS Attack. http://www.osattack.com The best change I saw on the list though is the addition of the ability to boot from a USB device or at least thats what it looks like the command means.

Today the guys from Cairo Shell sent out the notifications to testers that they are going to be starting testing soon. So far there is no word yet as to whether or not it will work in PE but I hope to find out soon. It looks like a lot of eye candy but it would look pretty cool on a system where PE is installed as the default operating system to the hard drive. I really hope it works so I can replace Rocket Dock which has gotten a little boring. http://www.osattack.com/?p=36 What shells does everyone else use if any? I know there are a couple others out there but I have not liked the way they worked.

http://winpe2.blogspot.com/2008/12/aerosna...windows-pe.html

You have no idea....

Do you mean make it Autorun in general or autorun in PE?

If your looking for a cleaner way of launching multiple programs I suggest doing it a different way. Create an xml file with your applications you want to run, save it in system32 and edit your Startnet.cmd In Startnet.cmd: wpeinit.exe /Unattend=X:\Windows\System32\wpeinit.xml <?xml version="1.0" encoding="utf-8"?> <unattend xmlns="urn:schemas-microsoft-com:unattend"> <settings pass="windowsPE"> <component name="Microsoft-Windows-Setup" processorArchitecture="x86" publicKeyToken="31bf3856ad364e35" language="neutral" versionScope="nonSxS" xmlns:wcm="http://schemas.microsoft.com/WMIConfig/2002/State" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <EnableNetwork>true</EnableNetwork> <EnableFirewall>true</EnableFirewall> </component> <RunSynchronous> <!-- First synchronous command to execute --> <RunSynchronousCommand> <Order>1</Order> <Path>\\MyNetworkShare\MyApplication.exe</Path> <Description>DescriptionOfMyApplication</Description> <Credentials> <Domain>FabrikamDomain</Domain> <UserName>MyUserName</UserName> <Password>MyPassword</Password> </Credentials> </RunSynchronousCommand> <!-- Second synchronous command to execute --> <RunSynchronousCommand> <Order>2</Order> <Path>C:\AnotherApplication.exe</Path> <Description>DescriptionOfMyApplication</Description> </RunSynchronousCommand> </RunSynchronous> </settings> </unattend> For the documentation on this go to your Windows AIK Documentation directory: C:\Program Files\Windows AIK\Docs\CHMs\Unattended.chm

I have been having the same thing happen but only with the newer AIK. I went back to the old version (1.0) and did the same commands with the same files and it worked perfectly. When I have gotten it to work with AIK 1.5 it has bluescreened my PE at boot. This happened with adding only simple drivers none of which were used for the machine I tested it on.

And merely stating not to use something is not constructive. While I build everything manualy I have used Nuno's Winbuilder just to check it out. And if your looking for something similar to Barts PE then that is the closest thing your going to find at this time. I suggest you ask for help using it as opposed to blatantly just saying for anyone else to not use it.

Perfect! This is exactly what I was looking for, much appreciated First start by ripping your wim from a Vista disk and not the AIK one. This will be the WinRE wim and will be a lot smaller. My wim with files and programs added such as Ghost is 84 MB. I could make it a lot smaller but I need to have wmi and other packages (which have to be added manually if you use the WinRE wim). You could also use a configuration.ini file when you create your wim. This will allow for you to always exclude files that you dont want Here is part of mine..... [ExclusionList] \$ntfs.log \hiberfil.sys \pagefile.sys "\System Volume Information" \RECYCLER \Windows\CSC \setup.exe \ProgramData \Program Files\Internet Explorer \sources\adprep \sources\inf \sources\license \sources\servicing \sources\dlmanifests \sources\actionqueue.dll \sources\alert.gif \sources\apds.dll \sources\apircl.dll \sources\appcompat.xsl \sources\appcompat_bidi.xsl \sources\appcompat_detailed.xsl \sources\appcompat_detailed_bidi.xsl \sources\apss.dll \sources\arunimg.dll \sources\arunres.dll \sources\autorun.dll \sources\cbscore.dll \sources\cbscore.mof \sources\cbsmsg.dll \sources\cmi2migxml.dll \sources\cmiadapter.dll \sources\cmitrust.dll \sources\cmiv2.dll \sources\cntrtextinstaller.dll \sources\compliance.ini \sources\compres.dll \sources\csiagent.dll \sources\diager.dll \sources\diagnostic.dll \sources\dpx.dll \sources\drupdate.dll \sources\drvmain.sdb \sources\drvmgrtn.dll \sources\drvstore.dll \sources\envmig.xml \sources\esscli.dll \sources\fastprox.dll \sources\fveupg.dll \sources\globalinstallorder.xml \sources\helpcins.dll \sources\hwcompat.dll \sources\hwcompat.txt \sources\hwexclude.txt \sources\idwbinfo.txt \sources\input.dll \sources\lang.ini \sources\locale.nls \sources\locdrv.dll \sources\migcore.dll \sources\mighost.exe \sources\migisol.dll \sources\migres.dll \sources\migtestplugin.dll \sources\mofd.dll \sources\mofinstall.dll \sources\mrt.exe \sources\msdelta.dll \sources\mspatcha.dll \sources\msxml6.dll \sources\msxml6r.dll \sources\mxeagent.dll \sources\nlsbres.dll \sources\ntdsupg.dll \sources\oemhelpins.dll \sources\offline.xml \sources\oscomps.xml \sources\osfilter.inf \sources\pidgenx.dll \sources\pkeyconfig.xrm-ms \sources\pkgmgr.exe \sources\pnpibs.dll \sources\product.ini \sources\readme.rtf \sources\repdrvfs.dll \sources\rescinst.dll \sources\rollback.exe \sources\schema.dat \sources\sdbapiu.dll \sources\segoeui.ttf \sources\setup.exe \sources\sflist2k.dat \sources\sflistlh.dat \sources\sflistxp.dat \sources\sfpat.inf \sources\sfpat2k.inf \sources\sfpatlh.inf \sources\sfpatxp.inf \sources\smiengine.dll \sources\smipi.dll \sources\sperr32.exe \sources\spflvrnt.dll \sources\spprgrss.dll \sources\spwizeng.dll \sources\spwizimg.dll \sources\spwizres.dll \sources\sqmapi.dll \sources\sysmain.sdb \sources\unattend.dll \sources\unbcl.dll \sources\uninstallustlib.mof \sources\upgcompat.inf \sources\upgdriver.dll \sources\upgloader.dll \sources\upgradeagent.dll \sources\upgradeagent.xml \sources\upgrade_bulk.xml \sources\upgreport.dll \sources\upgwow_bulk.xml \sources\ustlib.mof \sources\vofflps.rtf \sources\w32uiimg.dll \sources\w32uires.dll \sources\warning.gif \sources\wbemcomn.dll \sources\wbemcore.dll \sources\wbemprox.dll \sources\wcmtypes.xsd \sources\wcp.dll \sources\wdsclient.dll \sources\wdsclientapi.dll \sources\wdscore.dll \sources\wdscsl.dll \sources\wdsimage.dll \sources\wdsutil.dll \sources\win32ui.dll \sources\winsetup.dll \sources\wmiutils.dll \sources\wmi_tracing.mof \sources\en-US\dlmanifests\microsoft-windows-storagemigration\stormigplugin.dll.mui \sources\en-US\apds.dll.mui \sources\en-US\apircl.dll.mui \sources\en-US\apss.dll.mui \sources\en-US\arunres.dll.mui \sources\en-US\cbsmsg.dll.mui \sources\en-US\compres.dll.mui \sources\en-US\du_help_what_info_sent_to_ms.rtf \sources\en-US\du_help_why_get_updates.rtf \sources\en-US\help_what_is_activation.rtf \sources\en-US\input.dll.mui \sources\en-US\migres.dll.mui \sources\en-US\mofd.dll.mui \sources\en-US\msxml6r.dll.mui \sources\en-US\nlsbres.dll.mui \sources\en-US\pkgmgr.exe.mui \sources\en-US\pnpibs.dll.mui \sources\en-US\readme.rtf \sources\en-US\rollback.exe.mui \sources\en-US\setup.exe.mui \sources\en-US\setup_help_upgrade_or_custom.rtf \sources\en-US\smiengine.dll.mui \sources\en-US\sperr32.exe.mui \sources\en-US\spwizres.dll.mui \sources\en-US\upgdriver.dll.mui \sources\en-US\upgloader.dll.mui \sources\en-US\vofflps.rtf \sources\en-US\w32uires.dll.mui \sources\en-US\wbemcore.dll.mui \sources\en-US\wdsclient.dll.mui \sources\en-US\wdsimage.dll.mui \sources\en-US\winsetup.dll.mui \sources\en-US\wmiutils.dll.mui \Windows\Boot \Windows\Branding \Windows\Globalization \Windows\resources \Windows\security \Windows\tracing \Windows\Microsoft.NET \Windows\PolicyDefinitions \Windows\LiveKernelReports \Windows\L2Schemas \Windows\Help \Windows\debug \Windows\System32\ar-SA \Windows\System32\bg-BG \Windows\System32\Branding \Windows\System32\cs-CZ \Windows\System32\da-DK \Windows\System32\de-DE \Windows\System32\el-GR \Windows\System32\et-EE \Windows\System32\fi-FI \Windows\System32\GroupPolicy \Windows\System32\GroupPolicyUsers \Windows\System32\he-IL \Windows\System32\hr-HR \Windows\System32\hu-HU \Windows\System32\it-IT \Windows\System32\ja-JP \Windows\System32\ko-KR \Windows\System32\lt-LT \Windows\System32\lv-LV \Windows\System32\nb-NO \Windows\System32\nl-NL \Windows\System32\oobe \Windows\System32\pl-PL \Windows\System32\pt-BR \Windows\System32\pt-PT \Windows\System32\RemInst \Windows\System32\restore \Windows\System32\ro-RO \Windows\System32\ru-RU \Windows\System32\sk-SK \Windows\System32\sl-SI \Windows\System32\SMI \Windows\System32\sr-Latn-CS \Windows\System32\sv-SE \Windows\System32\sysprep \Windows\System32\th-TH \Windows\System32\uk-UA \Windows\System32\wfp \Windows\System32\winevt

The first thing you should do is download the new WAIK that came out on Feb 4 which comes with scripts for creating WinRe partitions. I have not used them but in reading over them I suspect they would make your life a lot easier with attempting to do this. http://www.microsoft.com/downloads/details...;DisplayLang=en

To enable mouse wheel support in PE 2.0...... Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\i8042prt\Parameters] "EnableWheelDetection"=dword:00000002 Mount your PE hive in the registry and then add that key to the PE registry.

Use Process Monitor to see what the program is trying to do or where its failure occurs. http://www.microsoft.com/technet/sysintern...essmonitor.mspx

I have not used a mounted floppy but I have updated the bios from PE 2.0 Here is something that may help you in your quest.... http://chitchat.at.infoseek.co.jp/vmware/vfd.html UPDATE: I just used this program and it works very well for mounting a floppy image in PE. I did not update a BIOS but I think it will work for what you need to do.

Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Services\FBWF] "WinPECacheThreshold"=dword:00000010 ;dword:00000010 = 16 ; 0x10 = 16Mb ; 0x18 = 24Mb ; 0x20 = 32Mb ; 0x30 = 48Mb ; 0x40 = 64Mb ; 0x48 = 72Mb ; 0x60 = 96Mb ; 0x80 = 128Mb ; 0x100 = 256Mb This will allow for you to change the size of your ram drive. Mount the hive and then change the settings.

One thing your forgetting about is machines that only have 256 mb of Ram probably have onboard video which can also then be shared ram. I have a PE 2.0 that works with 250 mb of ram leaving 6 for the video card. So far as long as in the Bios the video ram is reduced to 4 mb (if it can be) then it works correctly. The size includes 32MB for the ram drive. My wim file is 84 MB.