It may be pushing the limits of the license for MS Windows PE a little bit. Occasionally one needs to view a document or a spreadsheet, or edit a corporate logo; maybe watch a technet video, or blow the cobwebs out with a number puzzle while waiting for that Windows to deploy.
You need installed, the Windows AIK 1.1 (released for Vista SP1), because the project uses the imagex.exe, peimg.exe and oscdimg.exe tools found in the WAIK. The project is built from the winpe.wim image (WinPE 2.1) located in '...\Windows AIK\Tools\PETools\x86\'.
Using WinPE 3.0 (based on Win7 beta)
You can use the latest version of the winpe.wim found in Windows AIK 2.0 for Win7 Beta, provided that the new winpe.wim image (index:1) has, at the least, the 'Scripting' Package installed using the new dism.exe tool.
The new dism.exe (and WAIK 2.0) are not officially supported under XP. The packages can be found in WAIK 2.0's '...\Windows AIK\Tools\PETools\x86\WinPE_OCs\'. It seems necessary to install the WAIK 2.0, if only to get hold of the new winpe.wim and its packages. Then uninstall it and return to WAIK 1.1 to create a basic bootable WinPE 3.0 from the new winpe.wim. Boot that basic WinPE 3.0 and use its tools to add packages to the new winpe.wim which you have kept on the hard-drive.
The old peimg.exe cannot install packages into the new winpe.wim - it simply skips over the process when the project is being built.
For a look at Win7 with its dazzling start screen and magical 'Aero Snaps', simply replace the old winpe.wim in the WAIK sub-folder with the new packaged-up winpe.wim.
peimg.exe is able to install drivers into both the new and the old winpe.wim files (and /prep them as well.) If you need drivers for Mass Storage or Network Adaptors, place the extracted driver package in a folder. In Winbuilder's Interface for pePA.com, click the folder icon and navigate to the folder containing the extracted driver package(s). Each extracted driver package must include an .inf file. To install the driver, make sure that, in the Interface, the scrollbox (dropdown) under 'Configuration' is set to 'Individual Settings', because the default is for no driver installation.
Lastly, you must be online while Winbuilder is running pePA.com. You may have noticed that the project files total a mere 60KB. The Windows Tools come locally from the WAIK folders, but the other Apps have got to come from somewhere!
Alternatively, you can manually download each App from the websites listed below, and place the downloaded file inside '...\Winbuilder\Projects\pe2ArchiveDir\'. Perhaps some of these archive or installer files are already thereabouts. If they are in that folder, Winbuilder will not try to download them a second time provided they have the exact same file name as indicated in the following.
Corrected a Web Download Address in 'script.project'.
PortableApps.com_Platform_Setup_1.1.exe which was provided by Filip Hasa to make installtion easier.
The source is here: http://www.boot-land...?...ost&id=5470
Original PortableApps version is: PortableApps.com_Platform_Setup_1.1.exe
EDIT: The following two files are ClamWin's Virus Definitions. NB: Clicking on the links may cause your browser to attempt to open the files, and hang.
FAR Manager's download link went dead. It has been replaced by A43 File Manager.
Please let me know of any faulty downloads, as I am not able to repeatedly check... high maintenannce.. Of course, once the programs have been downloaded the first time, everything should be 'smooth sailing' from there after. ... ...
BTW. I couldn't get that video to play properly with VLC - even with VLC installed on my XP. And of course there is still no sound.
Here's a log of my last build.
and scripts in text format;
This project seems compatible with Winbuilder 075 beta 6. However most of my testing has been done with WB 074.
Corrected a Web Download Address and include Winbuilder 076 (Hot Fix #1) in the following package:
Winbuilder.zip containing Winbuilder v.076 Hotfix 1
For an easy start if you do not have Winbuilder.exe already; download one of the following .zip files which contain a complete package ready to run. Extract the contents of the .zip to a path that does not contain any spaces in any folder names - NO '...\Documents and Settings...\Desktop...' or '...\Program Files...'. A recommended path is simply a 'c:\Winbuilder\' folder which contains the Winbuilder.exe and a Projects folder containing the pePA project.
EDIT: Do not use the following. Please see above for UPDATE v.003.
Winbuilder.zip containing Winbuilder v.074
Winbuilder.zip containing Winbuilder v.0075 beta 6
If you already have Winbuilder: In Winbuilder's 'Download Center', add pe2.winbuilder.net to the list of servers (if it not there), and download and PLAY! ... ...
If something goes wrong and you find that your HardDrive appears to have been hijacked by PortableApps.com® and you see something like this after rebooting your computer:
Don't panic like I did. (Don't ever use 'System Restore' except as your last-hope option!) If you see the PortableApps.com® name and icon, then the extraction of the PortableApps Menu file has gone wrong and placed an 'autorun.inf' file in the root of your Drive. Firstly open the autorun.inf with notepad to make sure that it is the PortableApps file, then delete it and reboot.