8 replies to this topic

[your_father_darth_tater]

1. I successfully created a Win7PE iso file (I wanted a USB disk however, it errored out on USB creation so instead)
2. I used WintoFlash to write the iso file to a USB disk (actually a small 2.5 hard disk using a USB-IDE adaptor)

It worked, and I understand that you can use srcipts to add drivers, or even programs, but I was wondering if there is a way to install drivers/programs from within Win7PE.

Example:
My basic 7PE USB disk boots fine, but won't detect my NIC card, so I installed them from some files on another drive. I reboot, but then, the drivers are GONE! I did this with video drivers too.

Anyway, like I said, I know about scripts, but I ask because there might come a time when I buy say a bluetooth dongle, or whatever and need to install drivers OR, I download a game and want to install the game. Aside from doing this using scripts or having it slip-streamed or pre-built into the image, or modifying the image, is there a way to install software on Win7PE while running Win7PE? You know, installing software the way you normally would on an installed OS.

I also worry about game saves? I clicked on folder properties and it looks like they are read-only. And any modifications I made to the permissions would not stick. Any help would be appreciated.

[MedEvil]

Yes you can install software into a running PE, but as you already found out, a PE will always revert to it's build stage upon next boot.

This is not a flaw, but a PE is actually designeed to be that way, because it is advantageous for a PEs primary role.

What you're looking for, sounds like a portable Windows.
Wimbs "Universal HDD Images" are probaly what you're after.

You can find it explained here: http://reboot.pro/9830/

Download here: http://www.mediafire.../?233dka636369k

[homes32]

Yes you can install software into a running PE, but as you already found out, a PE will always revert to it's build stage upon next boot.

not always true.

As long as the media is writable your changes will persist. by default Win7PE will use boot.wim to load the PE into RAM and uses a write filter (FBWF) to simulate writing to a .wim file that isn't writeable. obvously changes will be lost on reboot as everything is stored in RAM.

However if you change the Build Model to Normal (Main Configuration script) the entire PE will be built to USB without packing files in a .wim. this results in a larger build size as the system files are not compressed but everything is writable. As medevil stated though, this isn't generally desirable so it is "off" by default.

[your_father_darth_tater]

Thanks guys, both of you! No thank button? Well, it was EXACTLY the info I needed. I will give both a try.

Edited by your_father_darth_tater, 12 October 2012 - 04:03 PM.

[homes32]

No thank button?

there is a "Like This" button on the post on the right hand side.

Anyways glad you found the info you needed.

regards,
Homes32

[MedEvil]

Have to correct homes a bit.
Normal build works only for applications, which do not need to store settings in the registry to work, as the registry will even on a flat build of a PE, always revert to it's clean state.

[Tony4219]

Aha! I had tried Normal build unsuccessfully a while back. I wanted a Persistent, Live version like BackTrack can do, only with winbuilder. I guess it was the missing Registry items that foiled me.

 

@your_father_darth  I have used the suggested technique of just running an Install after booting winbuilder. There is a script for MSI installers that might be handy to run MSI apps. EXE usually run okay. As long as you don't need a reboot to finish the install, it usually works just for that session. Just create a script to run the installer EXE from the startmenu.

[Sha0]

Windows PE does not have a persistent Registry.  PE was not designed to be persistent, so it's not really appropriate to use it with that goal.  Any strategies you find to make it persistent seem more complicated than simply using a non-PE that runs from a RAM disk.

[lianzi2000]

not always true.

As long as the media is writable your changes will persist. by default Win7PE will use boot.wim to load the PE into RAM and uses a write filter (FBWF) to simulate writing to a .wim file that isn't writeable. obvously changes will be lost on reboot as everything is stored in RAM.

However if you change the Build Model to Normal (Main Configuration script) the entire PE will be built to USB without packing files in a .wim. this results in a larger build size as the system files are not compressed but everything is writable. As medevil stated though, this isn't generally desirable so it is "off" by default.

 

Green softs may be, but all registry mods will be lost -- when ntoskrnl boots in PE mode, the registry loaded into memory are disconnected with the actual files on whatever media, so modifications made in a running PE will not be written back to disk. That is the major reason why PE can boot from read-only media.