Jump to content


  • Posts

  • Joined

  • Last visited

  • Donations

    0.00 USD 
  • Country


Everything posted by scp

  1. 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.
  2. I forgot something... you also have to copy folder d:\vistape\install\windows\branding to d:\vistape\test\windows\branding.
  3. 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
  4. 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
  5. 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
  6. Long time ago, I must look at it again. But maybe this week I do it with the current build.
  7. 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.
  8. 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
  9. What about IF NOT EXIST %SystemRoot%\system32\LegitCheckControl.DLL WUv6.exe /wuforce /quiet /norestart
  10. 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.
  11. I hate EWF. FBWF is much more flexible, easier to handle and volume-type-independend.
  12. syssetup.pdb is only for debugging purposes, you don't need it in a normal runtime environment.
  13. Now I looked at command-line help, I think it should work with your syntax. Just try it.
  14. Just delete the bootfix.bin in I386 folder. I currently have no idea what the -ib does.
  15. 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
  16. The network adapters included in windows will be all automatically included by Bart PE. Laptops sometimes have a special need of drivers, so it may be missing. Now I think it would be better you post some data. 1.) what Bart PE version you use 2.) from what Windows Version you use the Installation CD-ROM 3.) what networking card does the Laptops gave 4.) which Laptop Manfucturer and Model 5.) What does the blue screen contain (0x0000007B or KnownDLLs error or something else) PS: I also forgot to say, that I use InfCacheBuild by Sherpya, which is now included in "Build Scripts". May be it helps you.
  17. Now I have used a totally slimmed down version of BartPE and it worked. Look in ghostpe.txt which plugins I only used. If you use automatic DHCP only you don't need to use penetcfg, just use bartpe.exe with the autorun1startnet.cmd like I created. ghostpe.zip
  18. Now I finally found the "bugs": 1. DHCP needs time to init, so we must something do to wait for it 2. mode=restore instead of mode=load must be used for restoring an image 3. If you still have trouble with the packet driver error, try enabling the "Dos 16-bit support for WinPE" plugin Here is the final .cmd file which waits until the server is reachable: @echo off set _ghostserver=myserver set _pingmax=200 set _pingcur=0 :_tryping If "%_pingcur%"=="%_pingmax%" goto _err set /A _pingcur=%_pingcur%+1 echo. echo %_pingcur% of %_pingmax%... ping %_ghostserver% If errorlevel 1 goto _tryping echo Server found. echo. echo Now starting Ghost... %SystemDrive%\Programs\ghost8\ghost32.exe -clone,mode=restore,src=@MCdeploy,dst=1 -sure -rb -JL:E=%Temp%\ghosterr.log -afile=%Temp%\ghostera.log echo Done. goto _end :_err echo. echo ERROR: Server not found! echo. pause :_end exit Just replace "myserver" at the top of the script with the DNS name or IP address of your GhostCast server and change the ghost32 command in the middle like you need it. PS: my server/dhcp took 94 pings to react, maybe you set a value higher than "200" if it takes longer.
  19. Does it work if you start it manually? If not it may be that we need "legacy network" support in PE. Maybe I have to do a longer test with various combinations.
  20. No i finally found the switches which should work, tested with ghost32.exe under PE. This creates a image from a workstation: %SystemDrive%\Programs\ghost8\ghost32.exe -clone,mode=dump,src=1,dst=@MC001 -sure -rb -JL:E=%Temp%\ghosterr.log -afile=%Temp%\ghostera.log This writes the image back to the workstation: %SystemDrive%\Programs\ghost8\ghost32.exe -clone,mode=restore,src=@MC001,dst=1 -sure -rb -JL:E=%Temp%\ghosterr.log -afile=%Temp%\ghostera.log PS: You can use NUL instead of %Temp%\ghosterr.log to create no log. PPS: Write the whole command and switches in one line.
  21. remote desktop may be to difficult, I tried it but haven't get it. This parameters are for multicasting, so it should be right.
  22. I use Ghost for boot only on DOS, but maybe the syntax ist the same. This creates a image from a workstation: %SystemDrive%\Programs\ghost8\ghost32.exe -clone,src=1,dst=@MC001 -sure -rb This writes the image back to the workstation: %SystemDrive%\Programs\ghost8\ghost32.exe -clone,src=@MC001,dst=1 -sure -rb "001" is the sessions name.
  23. Oh now, I think we have found the problem: You don't have to copy the file in the i386 folder of the source folder, where Bart PE takes the files. It must be in the build folder, e.g.: C:\pebuilder313\BartPE\i386 Ab better way: Copy the autorun9ghostsrv.cmd to C:\pebuilder313\plugin\ghost8. Then open ghost.inf and add this line under [sourceDisksFiles]: autorun9ghostsrv.cmd=2,,1
  24. If you use Nu2Menu you can create a cmd file and copy it to i386\system32: autorun9ghostsrv.cmd @echo off start %SystemDrive%\Programs\ghost8\ghostsrv.exe exit If you use XPE you can use something like CurrentVersion\Run in registry. Add this to a plugin .inf: [Software.AddReg] 0x2,"Microsoft\Windows\CurrentVersion\Run","ghostsrv","%SystemDrive%\Programs\ghost8\ghostsrv.exe" EDIT: This will be executed AFTER Explorer is loaded: [Default.AddReg] 0x2,"Software\Microsoft\Windows\CurrentVersion\RunOnce","ghostsrv","%SystemDrive%\Programs\ghost8\ghostsrv.exe"
  25. Used Alcohol for a very long time until I switched to Daemon Tools. Both are good.

  • Create New...