allanf

When you boot WinPE, drive letters are assigned in the "default order". Exactly what this "default order" is, has proven to be a bit of a mystery. Here's a kb article, "Order in Which MS-DOS and Windows Assign Drive Letters". Only experience will tell if this is the "default order" used by Windows PE 3.0. I would say that Dells Recovery Partition is the first Primary Partition on the first HDD, and so Windows PE sees it as c:, unlike on your laptop where Vista is on the first Primary Partition of the first HDD. It's a different story when creating partitions using diskpart in Windows PE. Drive letters are assigned in the order of creation. But Windows PE has no way of storing this order for the next time it reboots, so defaults to the "default order" Regards

OK. I'm a bit lost. You are booting a WinPE 3.0 UFD plugged into a Windows 7 Laptop. Then connecting on a network to a Dell E6500 at work, and mapping a directory/partition on the Dell E6500 as c:\. The problem is that the wrong partition on the Dell is being mapped as c:\. Is that the situation? What is the situation where it works OK? That is, when c:\ shows the right partition and all the right folders and files?

Hi cyberwatchers, Could it be that, in the first case, you are looking at some proprietary recovery partition, which WinPE sees as c:\? To find out what's what, use: diskpart list disk select disk 0 list part list vol exit Regards

Hi PC, Are you simply wanting to add an "imagex /apply" routine to the startup script, or have I missed something? Regards

Three files: Windows\system32\drivers\wimfltr.sys Windows\system32\drivers\wimfltr.inf Windows\system32\wimgapi.dll After booting WinPE: rundll32 setupapi,InstallHinfSection DefaultInstall 132 %SystemDrive%\windows\system32\drivers\wimfltr.inf Net start wimfltr ... something like that. First line is mostly case-sensitive too. I put the lines in WinPE's startnet.cmd to start at boot up.

How many times does the process boot to WinPE? If only one boot to WinPE - the first boot - it seems to me that the WinPE partition, including the WinPE boot structure can be deleted with diskpart as soon as WinPE is up and running in RAM. Do it before starting to install another OS. If WinPE and the Imaging stufF are combined into a single partition, then they can be deleted at the same time ... possibly ... After installing XP? There might be a trick to intalling XP on a machine already booting with Vista's (WinPE 2.x's) Boot Manager.

In previous versions of the WAIK, including the one for Windows 7 beta, the C:\Program Files\Windows AIK\Tools\PETools\copype.cmd contained this line: copy "%SOURCE%\winpe.wim" "%DEST%\%TEMPL%\sources\boot.wim" The sources\boot.wim may have been automatically created to allow the rapid creation of an uncustomized Windows PE. For customized versions, the existing sources\boot.wim was deleted and replaced with the customized boot.wim file. It seems that the WAIK for Windows 7 RC has dropped that line from copype.cmd, so that the boot.wim needs to be manually added to the sources folder. From 'Windows Preinstallation Environment (Windows PE) User's Guide' Build Date: 2009-03-04-182032: Regards

On Windows 7 Beta with Windows AIK 2.0 installed. Start > All Programs > Microsoft Windows AIK > Deployment Tools Command Prompt -> Right-Click > Run as administrator > Yes diskpart create vdisk file=d:\winpe.vhd type=fixed maximum=1024 select vdisk file=d:\winpe.vhd attach vdisk create partition primary assign format quick label=vhd exit imagex /apply "c:\program files\windows aik\tools\petools\x86\winpe.wim" 1 e: diskpart select vdisk file=d:\winpe.vhd detach vdisk exit bcdedit /create /d "vhd" /application osloader bcdedit /set {GUID} device vhd=[d:]\winpe.vhd bcdedit /set {GUID} osdevice vhd=[d:]\winpe.vhd bcdedit /set {GUID} path \windows\system32\winload.exe bcdedit /set {GUID} systemroot \windows bcdedit /set {GUID} detecthal yes bcdedit /set {GUID} winpe yes bcdedit /displayorder {GUID} /addlast e: is the Drive Letter assigned to the attached VDISK. {GUID} is returned following the command: bcdedit /create /d "vhd" /application osloader d: is the partition holding the .vhd file. In the BCD, [d:] may be replaced by [locate]. Compared to other methods of booting the unmodified winpe.wim volume image - from Boot Manager select to the appearance of the Command Prompt: vhd - 34 seconds wim - 33 seconds flat - 32 seconds (... give or take a second or two ... ...) Regards

OK. But as previously said, the project has been permanently withdrawn. There is no link to post. BTW. I updated the first post so that readers don't waste their time. I hope it's clear. Regards

Thanks. That means a lot. I was hoping to finish a new improved version before expressing my thanks. Unfortunately, there are some incompatibility issues with winbuilder and its new developer, and the project has been permanently withdrawn. @tripredacus This thread is now fairly pointless. At your own discretion, you may delete it. I won't bother you again ... ... Good luck

Under WinPE 2.1, the correct Path for the PassMark folder is: ProgramData is a hidden directory. Regards

Both BIT Std and BIT Pro seem to work fine when installed in an online WinPE 2.1. However, repeated online installation does enter a grey area in terms of the license, which is why I try to avoid shareware. The one requirement is an externally-sourced msvfw32.dll, and that, to me, means that the program is not supported under Windows PE 2.1 - strictly speaking. Regards

Hi, A new version compatible with XP and Win7 beta - pe21.003g! (gamma is the third letter. oh well!) Added to the Programs Selection List: wincontig Defragmenter * Double Commander File Manager (has a small error when starting.) New Users. Download the .zip, extract it, double-click winbuilder.exe and press 'Play'! ... ... .zip Package including WinBuilder 076 Old Users. Winbuilder's Download Center - pe2.winbuilder.net More Credits added: Credits=www.boot-land.net Community, Nightman for VistaPE, damian666 for the Wallpaper, Filip Hasa for x64, wimb for U_XP_SET, Holger for PENetwork, TheHive for the sheep, nikzzzz for cmd tips, ludovici for the Thanks, jaclaz and script-writers everywhere, all the Open Source and Free Program Developers, Microsoft and Nuno Brito. Thanks

peimg /prep and imagex /export Both 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

Thank s Nuno, I was hoping to post a project update to address an issue with Vista's UAC. Testing simultaneously on Win 7 beta has slowed things down, although WinBuilder is performing very well under the new OS beta. Here's a screenshot of the WinBuilder Interface showing some of the options that can be selected when building a customized Windows PE 2.1. Regards

There's a Walk-thorugh titled "Boot Windows PE from CD-ROM" (... as opposed to booting from RAM disk.) 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: or Then: mkdir <your directory>\boot cd /d <your directory>\Windows\System32 bcdedit /createstore <your directory>\boot\BCD bcdedit ... etc ... etc ... from the Walk-through Note 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>.iso etfsboot.com can be found at, for example: or Regards

Not really ... ... How would quoting the kernel version help anyone when you have hacked the Servicing Stack? ... ... Regards

I can't help you with your licensing issues. You indicated that you had used the Windows 7 pre-installation tools. If this is correct, and you are using the tools in an OEM environment, I strongly suggest that you reveiw your licenses, or have someone explain them to you, particularly the MS Pre-release Software Terms. Regarding your issues with the User's Guides for the Windows 7 pre-installation tools, you can access them from the 'Start' Button', provided that you have installed a Windows 7 pre-installation kit. If you haven't installed any Windows 7 pre-installation tools, and would like to read the Documentation before testing them out, you can download the latest English version from here: http://www.microsoft.com/downloads/details...;displaylang=en Note that you cannot install the Windows 7 pre-installation tolls on a PC that has previous versions installed. You must uninstall the previous versions first. Perhaps that is why you have gotten so mixed up. Regards

The current version 'HTA Interface for Windows deployment' from: http://geezery.pp.fi/ redistributes setres.exe (Copyright © 2001 Ladislav Sedivy) which can be downloaded from: http://sedivy.com/utils/ Regards EDIT: I don't use it. Read the disclaimer on the link.

32MB by default. It can be increased to 512MB for Windows PE 2.1 and Windows PE 3.0. I think the limit on Windows PE 2.0 was 256MB. Regards

Try telling that to MS! 'Windows PE 2.0', 'Windows PE 2.1', and 'Windows PE 3.0' are the terms used by MS in the Documentation accompanying the WAIK. You should have a browse through the Users Guides. They're quite informative. For example, page 1 of the 'Windows Preinstallation Environment (Windows PE) Users Guide for Windows 7': Also, everywhere on the web. For example: http://www.svrops.com/svrops/articles/winvistape2.htm @gregorsamsa11, regarding the peimg error... It would be helpful to state the steps that you have used to customize the WinPE 2.0 leading up to the error with peimg. It's an issue that I have not really understood. What is it that signals to peimg whether or not the image is a Windows PE image - particularly when doing extensive customizations. But it should always work with a fresh winpe.wim from the WAIK. It may be best to execute the peimg command immediately after mounting the image - before all other customizations. Some XP drivers do work OK with Windows PE 2.x. Regards

As previously advised, it makes no difference to the erratic and errant behaviour of the mounting tools whether the WAIK 2.0 is installed on XP or Windows 7 beta. However, it seems that you may have come across unreleased versions of the WAIK. The latest released was version 2.0 (for Win 7 beta). You should go to Control Panel > 'Programs and Features' | 'Add or Remove Programs' > Select 'Windows Automated Installation Kit' [> Click here for support information']. Confirm whether or not you have a version 2.1 as you stated. If you do, could you please advise of the origination of the WAIK 2.1. It may be warez. It is very important to know which version you are using when discussing System Requirements. It's not my bold. The text is copied and pasted directly from the MS Downloads page. You should check the system requirements from the relevent page. A link was provided in the first post. The information you provide is doubtful. Again, please visit the MS Downloads page for system requirements. Also read the Documentation, and you will see that the Requirements for a Technician Computer are: (Again, copied and pasted and it's not my bold.. This time from the latest WAIK User's Guide, Build Date: 2008-11-16-190528. Obviously needs updating by MS!) I am unable to find a Walk-Through with "DVD Windows PE" in the title? It may be helpful if you can provide the full title. 'Walkthrough: Create a Bootable Windows PE RAM Disk on CD-ROM' makes no mention at all of dism.exe, and normally a DVD is not required for Windows PE - CDs are sufficient if you are inclined to use optical media for booting. It seems you are the only fortunate who has found WAIK 2.0's imagex to perform satisfactorily. Have you tried the previous imagex (WAIK 1.1)? You will be surprised. It's very quick, and will make you realise that the new imagex has some serious issues. Also, refer to: Regards

Hi, Initially, I trialled the new WAIK 2.0 (relaesed for Win7) under XP Pro, after first uninstalling WAIK 1.1 (released for Vista SP1). http://www.microsoft.com/downloads/details...;displaylang=en Mounting and Unmounting of .wim images using either the new imagex or the new dism was erratic and caused sporadic errors particularly when Unmounting with dism. Worse was the length of time taken to Mount and Unmount - up to twenty tiimes more than using WAIK 1.1's imagex. The first Mount in a session using the newly installed tools, always seems to be the longest, so I guess that something is initialized. I assumed that the behaviour was the result of using the new WAIK tools under an unsupported OS. From the download page: (Why two 'Supported Operating Systems' sections?) So I set up Win7 beta and installed WAIK 2.0. It is no better than using the WAIK under XP! IMO, the deprecation of the handy little tool peimg was a mistake by MS! Its functions are now rolled into dism. The incorporation of imagex functioality into dism may also have been unwarranted. IMO, it would be better to retain one very efficient tool that is dedicated to Mounting and Unmounting .wim images, like the previous imagex. So, what happened with the new imagex? Why is it struggling too? On the other hand, dism does seem to provide a friendlier interface for the pkgmgr functions. The help screen is informative, and error messages are more available. Generally, after trialling the new WAIK tools under XP, Win7 beta and Windows PE 3.0, I would have to say that it might have been better if dism took on the functions of pkgmgr only, and the left the other efficient and dedicated tools alone! When time is an issue, as it usually is, it is better to stick with WAIK 1.1 (released for Vista SP!) - at least until things improve on the .wim front. However, the new diskpart, with its VDISK functionality, can be found installed in WAIK 2.0's winpe.wim images (and Win7 beta itself). For some, this may be a compelling reason to move on to the new WAIK. Regards Edit: Sorry Tripredacus that this is a general report, and not a specific bug reoprt as you requested.

From the WinPE 2.1 User's Guide (referring to WinPE 2.0): I assume by 'USB Key' that you mean a USB Flash Drive/Device ... ... Have you tried inserting the 'USB Key', and from the Command Prompt, changing drive letters, starting with: d: ? Have you made any customizations to your Windows PE 2.x? Regards

In the registry: HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\Control\Session Manager\Environment (... from XP, but should be the same for Windows PE 2.x/3/0.) In Windows PE Command Prompt, type: SET or SET PATH Regards