multiPE

Download the latest changes.

They also contain ShutdownPE.Script with the Arch bug fixed.

Now BFE and mpssvc services can be started.

Peter

Yes, firewall service loads & can be disabled. Well done Peter!

Now few other annoying bits

Windows Explorer windows open in new window each time, no matter what the settings are.

By default show hidden & system protected files is ON (looks ugly seining desktop.ini)

Run is not available on Start Menu

These options are no configurable in a script (ofcourse can be done by hand loading the default hive), which would be easier

%SystemDrive%\Program Files\BGInfo\RunBGInfo.exe does not get found while executed from easydriveletter.ini

PENM does not (always) get successfully executed on startup, even if it does there is a delay to obtain IP from DHCP server (again I am comparing it to WinPESE, which with same server works instantly)

All in all the final configuration of loaded WinPE takes too long (as ie comparing to WinPESE).

Yes, the iso is smaller, but it actually takes longer to get to usable desktop (both booted from same PXE/ipxe/http or local iso in Workstation9 )

@sebus,

Thanks for your comments!

All in all the final configuration of loaded WinPE takes too long (as ie comparing to WinPESE).

multiPE is designed with many functionality during the boot process. E.g. you can get the "original" drive letters of your host, when booting in PE.

I do not intend to change multiPE's general functionality.

If boot time is an important argument (you boot the PE propably several 100 times a day), multiPE is not what you need. Switch to a different project.

Windows Explorer windows open in new window each time, no matter what the settings are.

This is already making me angry since a long time. When the "high level" issues are solved, I'll look for that. Maybe you or another PE expert gives a hint how to solve.

By default show hidden & system protected files is ON (looks ugly seining desktop.ini)

See above.

Additionally: Removing Desktop.ini is one of the time consuming tasks (first item). You can activate it by defining in

multiPE > Core > Tweaks > Desktop tweaks

Run is not available on Start Menu

I decided to make it available in the taskbar's 'Start' button by defining in

multiPE > Core > Tweaks > Desktop tweaks

%SystemDrive%\Program Files\BGInfo\RunBGInfo.exe does not get found while executed from easydriveletter.ini

Sounds like a bug. I'll check. I need the log how RunBGInfo.exe is activated during the build.

PENM does not (always) get successfully executed on startup, even if it does there is a delay to obtain IP from DHCP server (again I am comparing it to WinPESE, which with same server works instantly)

I did not recognize that until now. PENM is only an executed script made by Holger.

If it makes troubles for you, see first item.

Peter

Hi I am very new to using winbuilder. I've used this several times today and I have run into a few problems.

1. I use the PENetwork script option to add drivers but the disk never detects my NIC.

2. I have had no luck creating an automatic drive mapping with PENetwork. I want it to prompt for username and password, how do I do that?

3. The files that I place in the custom files folder aren't being copied over. If they are I don't know where on the system they would apear. I have been unable to find them. I just want to include gimagex in there so I can take and apply images to and from machines.

Any help with this will be greatly appreciated.

Thanks!

Thanks Peter, it was fun to try, but as I need the speed PESE is way to go for me.
As to Explorer Windows opening each new window - I reckon it is not settings (as I have changed them), but something else must be missing. It is just easier to use Q-dir

I wonder if it is the existence of space in Program Files that makes RunBGInfo troubles - tested as progra~2 but this time it does not complain

show hidden & system protected files is ON - it was easier for me to change the settings in default registry hive

If you mean Run being described as:

Execute Task in Start Menu

You could add in same place tweaks for Hidden 0x00000002 & ShowSuperHidden 0x00000000

I believe timeout.exe (which is only 27kb) is also a good one to have (for batch files that one might need to run, like the firewall services)

sebus

Thanks Peter, it was fun to try, but as I need the speed PESE is way to go for me.

I'm afraid that you are comparing apples with pineapples. The common property here are just the characters 'apple'.

You are using the "competition" version of multiPE, which, to minimize the ISO size, uses ONLY one CPU and no PAE, regardless what the host can offer.

That is truelly much slower than a "standard" PE.

The common property here is the physical source CD.

Peter

EDIT: Added the 'common Property' hint

Sorry, I have to contradict that the CPU number and other hardware facts only affect the running system.

I made a test including all ntkrnl*.* in the build and created the ISO.

Then I started the ISO in VirtualBox

One CPU, no PAE, vo VT-X : about 65 seconds between "VirualBox" screen appearing and having a usable desktop.

Two CPUs, PAE anabled, VT-X enabled: about 15 seconds between "VirualBox" screen appearing and having a usable desktop.

I assume that in a real environment times are comparable.

You can reproduce the test by including the line

    FileCopy,%b32%\ntkr*.exe,%t32%
into microBuild.script.

BTW: In several posts I already told that I usually do not try to force people to use my tools. If the user can use it, I'm glad. If he cannot use it, no problem when he uses the app of his choice.

I only try to defend when a sophisticated and well constructed application gets the image of "not sufficient" or "not suited"

Peter

Two CPUs, PAE anabled, VT-X enabled test is pointless as I have no such physical hardware which I use for imagining. Single CPU 3 Gb of RAM is as good as it gets

Ofcourse you can not force users, but that should not stop project having some extra options selectable by the end user...

It was pleasure, learned few things on the way, time to move on, thanks

Version 65 is uploaded.

What's New in Version 65

That is excellent, but I test it on VMW9 & could never get to these times, but will give it a go one more time to check...

What is VMW9? Latest VmWare? I stopped at 5.x, when I retired. Buying all the licenses became to expensive for a "hobby worker".

Peter

Sorry, the uploaded version 65 has all scripts from 65, but script.projects tells 64.

I replaced the upload with the correct version number.

Version 65 users can just download the latest project.script via WinBuilder's download GUI, or just edit script.project and fix the version number.

Peter

I have to confess that dism is an unloved child in multiPE.

I never worked on it seriously.

Peter

Version 66 is uploaded

What's New in Version 66

Good Job pscEx can not wait till Windows 8 is out of alfa

Good Job pscEx can not wait till Windows 8 is out of alfa

Thanks, DarkPhoeniX!

But but for me personally the multiPE win8 track currently will remain alpha.

I'm only one person, which has a 36 hours / day job to hold the established projects actual.

I cannot spend any time to win8. For that I need the help of forum members with new / updated win8 scripts.

As soon as I get such a suggested script, I'll include.

Peter

Version 67 uploaded!

What's New in Version 67

New "Standard":

Built in 4 to 5 minutes

Iso size less than 109 MB

Boot time (in VirtualBox) about 30 seconds

That is remarkably better than the old Standard, based on historic Vista and Win7 projects.

Fast Mount:

Wims of Vista and Win7 SP0 sources can be mounted by ImageX from Vista SP1 WAIK.

This is done in less than 1 second with boot.wim and less than 10 seconds for install.wim.

Win7 SP1 sources are also mounted within this time, but reading from the mounted wims sometimes gives truncated files.

Therefore for Win7 SP1 sources a normal, time consuming mount with DISM or WimCaptEx, or an (one times) extract to HDD has to be done.

If a SP1 source is choosen, multiPE brings a warning hint.

Currently in the multiPE builds there are no advantages of SP1 sources against SP0 sources known.

Therefore the use of SP0 sources is recommended.

Peter

multiPE > Core > 1 - Core Basics > WaikFilesEx > Show Current

Post the resulting %WaikConfig% (= ?:\multiPE_Depot\WaikFiles\WaikFiles.cfg)

And the line of the log which shows the DISM call.

...  W7 x86 source as mounted iso

Try with an extracted ISO as source. There are several times issues reported when using a mounted ISO as source.

See e.g. http://reboot.pro/to...rce/#entry61925

Peter

See my edit above.

New issues:
1) Also with dism selected for mount, no matter what option is chosen wims are always stored (even if the user does not want that)

The only way is to use Auto for mount & dism for creation (works very well, created wim is smaller then with InageX & much more useful - one can edit it with dism later outside the project ie add drivers etc)

2) new errors (did not exist previously)

Exec - Failed to find section [Do-Micro] in file: [%BaseDir%\Projects\multiPE\Core\2 - Core Files\2 - Build\microBuild.Script]

(had to rename section called Process to Do-Micro to build OK)

IniRead - Failed to find file: [%BaseDir%\Target\multiPE_Win7\windows\system32\ShutdownPE_lng.ini]

3) and diskpart (which worked fine in 0.65 with same options selected for the build) does NOT work any more (osuninst.dll was not copied at all - had to copy by hand, still vds does not start) - same issue like I had here

4) and dhcpcsvc.dll & dhcpcsvc6.dll copied to build are in fact fonts (not the dlls) - had to copy them by hand

sebus

You need to add /ReadOnly to dism command (as it is a must for .wim image that is mounted from read only source) in

Thanks!

Peter

hi, thanks for your hard work

W7x64 host, W7x86sp0 extracted source

failed error 5 (error retreiving temp path)

here is the log

http://www.mediafire...p79qmcdemtg2cp4

hi, thanks for your hard work

 

W7x64 host, W7x86sp0 extracted source

failed error 5 (error retreiving temp path)

here is the log

 

http://www.mediafire...p79qmcdemtg2cp4

Sorry, a real design bug!

For the extract a temp directory is needed, which in the very first run does not exist yet.

I'll fix it soon.

As temporary solution:

Run multiPE > Core > 2 - Core Files 1 > Prepare > Create Directories

manually.

Peter