scp

Also works for Vista RC1 (5600), with some strange side effect: The buttons in the upper right corner do not contain Symbols and some Text in a window is not displayed. Also wpeinit.exe takes long time to load. Remember winload.exe and winresume.exe is stored in system32 and the correspondending .mui files are in the sub folder of your language (e.g. system32\de-DE). If you directly manipulatie the boot.wim image it works. PS: Updated script above with some bcdedit lines.

I forgot something... you also have to copy folder d:\vistape\install\windows\branding to d:\vistape\test\windows\branding.

You can get the Start Menu working... in Classic mode. Just load system32\config\DEFAULT as hive in regedit, i.e. named as DEFAULT_PE. Then go under HKEY_LOCAL_MACHINE\DEFAULT_PE\Software\Microsoft\Windows\CurrentVersion\Explorer sand find or create a binary value named "ShellState". Change it to something like this: 24,00,00,00,33,A8,00,00,00,00,00,00,00,00,00,00,00,00,00,00,01,00,00,00,0D,00,00,00,00,00,00,00,00,00,00,00I think the only important value is the first pair in the last row, it may be 02 if existing and must be 00. Windows Registry Editor Version 5.00 [HKEY_LOCAL_MACHINE\DEFAULT_PE\Software\Microsoft\Windows\CurrentVersion\Explorer]"ShellState"=hex:24,00,00,00,33,A8,00,00,00,00,00,00,00,00,00,00,00,00,00,00,\ 01,00,00,00,0D,00,00,00,00,00,00,00,00,00,00,00

Update: Works also for Beta 2 (Build 5384) Here is a little script for steps 8 to 10: prepwpe.cmd @echo off set CDROOT=E:\LH5384\$WINDOWS.~BT\ If not exist %~dp0bcdedit.exe copy %CDROOT%Windows\system32\bcdedit.exe %~dp0 bcdedit /store %CDROOT%boot\bcd /set {default} device BOOT bcdedit /store %CDROOT%boot\bcd /set {default} osdevice BOOT bcdedit /store %CDROOT%boot\bcd /set {default} path \windows\system32\winload.exe bcdedit /store %CDROOT%boot\bcd /set {default} systemroot \windows bcdedit /store %CDROOT%boot\bcd /set {default} winpe yes bcdedit /store %CDROOT%boot\bcd /set {default} detecthal yes If exist %CDROOT%Setup.exe ren %CDROOT%Setup.exe Setuq.exe If exist %CDROOT%Sources\Setup.exe ren %CDROOT%Sources\Setup.exe Setuq.exe If you want to get Recovery options from command-line, run X:\Sources\Recovery\recenv.exe

OK, first part of using PE from 5342 is done. 1. Requirements for your (maybe virtual) PC: You need at least 256MB of RAM Create one empty partition with at least 8 GB space Create a second smaller empty partition with at least 4 GB space 2. Install Windows 2000 or XP on the first partition, format the second 3. Run Vista Setup within Windows 2000 or XP, select first partition as target 4. Don't let Setup reboot! Insert a bootdisk or CD-ROM 5. Now you can save the Windows PE files and folders to another location: $WINDOWS.~BT boot $bootdrive$ $DRVLTR$ $dwnlvldrive$ boot.ini bootmgr (arcldr.exe) (arcsetup.exe) (NTDETECT.COM) (NTLDR) 6. Copy folders "boot" and "efi" and files "bootmgr" and "bootmgr.efi" from Vista DVD into "$WINDOWS.~BT" 7. Get the boot sector from Vista DVD 8. Copy bcdedit.exe from $WINDOWS.~BT\Windows\system32 to some other folder 9. In command-line run bcdedit /store E:\LH5342\$WINDOWS.~BT\boot\bcd /set {default} device BOOT bcdedit /store E:\LH5342\$WINDOWS.~BT\boot\bcd /set {default} osdevice BOOT where you must replace "E:\LH5342\$WINDOWS.~BT" with your own location of $WINDOWS.~BT 10. Rename Setup.exe and Sources\Setup.exe to Setuq.exe or delete them 11. Burn $WINDOWS.~BT onto CD or DVD 12. The contents of the CD should now look like this: boot efi Program Files ProgramData Sources Users Windows autorun.inf bootmgr bootmgr.efi readme.htm readme.rtf setuq.exe

Long time ago, I must look at it again. But maybe this week I do it with the current build.

Does anyone know what kind of release "Windows Powered" is? I found it in english SP4 / USP50 but not in german SP4. THe CD-ROM tag ist CDROM_IW.5, the SP subfolder is iw.

Are you using Windows 2000 or Windows XP with no SP? Then you should download Microsoft Data Access Components (MDAC) 2.8 and try to start it with /q switch before your app

What about IF NOT EXIST %SystemRoot%\system32\LegitCheckControl.DLL WUv6.exe /wuforce /quiet /norestart

For each build you create with Bart PE you need a separate license for the source Windows you used. So, if you build 20 clients with it and have VLK, 20 licenses are used of this. But with this, its legal. It is legal only to distribute your plugin inf + own .exe and .dll's. But if you want to add the whole Bart PE Builder (without Windows binaries), you must ask Bart Lagerweij.

I hate EWF. FBWF is much more flexible, easier to handle and volume-type-independend.

syssetup.pdb is only for debugging purposes, you don't need it in a normal runtime environment.

Now I looked at command-line help, I think it should work with your syntax. Just try it.

Just delete the bootfix.bin in I386 folder. I currently have no idea what the -ib does.

I finally got the fbwf (File Based Write Filter Driver) working on a current Windows PE build. If you used that, you get write access "on" your CD/DVD, the status of drive X: shows 32 MB of free space and you can create/modify files and folders! In the attached zip file is a plugin for Bart PE and a fbwfmanual.txt which contains the required TXTSETUP.SIF end registry entrys for use in original WinPE. Tested on Bart PE 3.1.3, WinXP SP2 source with ramdisk.sys from Server 2003 SP1. Required files are from Longhorn/Vista Beta 1 Build 5112, you find them in the boot.wim image as described in an earlier post from me. PS: wimfsf.sys will also be copied but currently not used, because its not working and not required for fbwf. EDIT: Modified Bart PE plugin inf for SAC fbwf.zip