81 replies to this topic

[PaPeuser]

First let me say thanks to all who have work so hard at Win7PE

Next when we talk about Win7PE what version or source
Multiple PEs can be built using
1. Vista SP-0, 1, 2 for 32 & 64bit
2. Windows server 2k8 SP-0 0,1,2 for 32bit & 64bit
3. Windows 7 for 32bit & 64bit

Then what project
Download from in Winbuilder - best used with 32bit builds
Update package and WoW updates from Yahoouk
JFX now has a package and updated WoW - best used with 64 bit builds

Scripts I use and TRY to test in most of the above are
Total Commander
Malwarebytes
Spybot
Hijack This
McAfee
AVZ
DrWeb AV03
Avira
Dart65
Salapassword
DreamPack
Ghost
Easy recovery
Test disk
And I have not and can not test every possibility.
Question does what is downloaded in Winbuilder need updated? - No 32bit should use download in Winbuilder
Has any updated package been tested enough? - No

I have a hard time answering questions about what scripts work with what project and i can hear it now where do i find these scripts!!

[sbaeder]

First let me say thanks to all who have work so hard at Win7PE

I'm guessing you mean the now named Multi 7 PE

Question does what is downloaded in Winbuilder need updated? - No 32bit should use download in Winbuilder
Has any updated package been tested enough? - No

I have a hard time answering questions about what scripts work with what project and i can hear it now where do i find these scripts!!

Yes, this is the real question we should be focusing on here on the forums (and not some petty syntax issues ) (sarcasm)

I would really like to see some sort of changes to combine Peters Native_Ex7 approach (where the CD is all you need) and there is some caching of the basic PE with a good set of scripts that manage the rest of the process...Not sure which is really a better "foundation" - the rescue7 PE of the Multi 7 PE...I think each has some Plus and Minus

But one thing I would really like to see is that the "project" have all the tools that are needed...it is very frustrating to DL a "project" and to get a pop up in notepad that says go get these tools...

Anyway, that's my $0.02

[PaPeuser]

This link will help you Build your first Multi Win7PE
Download to a new folder and check it out
Win7PE 10-3-10

Set source and go
Then if you want to follow along get the updates .. from same page

The only thing that bothers me is inconsistency
Then I remember the only thing constant is change

[paraglider]

project does not appear to build if source is win7 x86.

script.project contains:

%SourceArch%=x64
%TargetWOW64%=x86


project.info appears to contain:

SysType=%SysType%

Could not work out how %SysType% gets set.

Also has a win7info and a projectinfo section.

[paraglider]

Believe this is missing from 0-preconfig.script:

If,ExistDir,"%Source_win%\SysWOW64",Set,%SourceArch%,x64,Permanent
If,ExistDir,"%Source_win%\winsxs\Backup\ia64",Set,%SourceArch%,ia64,Permanent
If,NotExistDir,"%Source_win%\SysWOW64",If,NotExistDir,"%Source_win%\winsxs\Backup\ia64",Set,%SourceArch%,x86,Permanent
Set,%TargetWOW64%,%SourceArch%,Permanent
If,ExistDir,"%WindowsDir%\SysWOW64",Set,%SysType%,"amd64",Permanent
If,NotExistDir,"%WindowsDir%\SysWOW64",Set,%SysType%,"x86",Permanent

[dera]

in project.ini the section [win7info] left from the past and seems currently it is not used

the valid section is the [ProjectInfo]

[dera]

regarding the
If,ExistDir,"%WindowsDir%\SysWOW64",Set, etc.
i found a strange post here

don't know how much typical is it,
i mean: is it really true that in normal circumstances in some case the folder 'Windows\SysWOW64' exists on x86 host?

[paraglider]

Winbuilder provides a variable, %Wow64%, that is only set to true on a 64 bit os. So:

If,%Wow64%,equal,True,Set,%SysType%,"amd64",Permanent

works.

It does not however detect the difference between ia64 and amd64. Neither method does that.

[PaPeuser]

Hello

A new update is available

Link to post

[PaPeuser]

Lancelot has made another up date available

in this post

I will test by adding scripts and report here!!

In Vmware I get a please insert disk into drive A: - click try agin and it goes away

Scripts with problems
Avira -WebGetNotExit - went away after a few builds all by its self
When Hijack This was running during build Winbuilder closed .. poof
Runscanner same thing Winbuilder closes .. poof gone
When this happens there is no logfile

Testing with
Avira antivir – eroded -WebGetNotExit
Avz antivir
Ghost
Hijack this – Winbuilder closed .. poof gone
Mcafee antivir
Runscanner - Winbuilder closed
Sala’s password
Spybot
Malwarebytes - runtime error '0' vbAccelerator SGrid II control?
DrWeb

still testing

[Lancelot]

Hijack this – Winbuilder closed .. poof gone
Runscanner - Winbuilder closed

Hi PaPeuser, I can easly reproduce Runscanner test (not tested but I feel same on Hijack this too), I need "time" to figure out what is going on, you can stop testing and continue after fix. Thanks for reporting.

[PaPeuser]

Lancelot
LiveXP Application scripts can now be integrated easily into the Win7PE_SE project.
Test built on a Win7 x64 host using a Win7 x64 source

Using the Win7PE_SE project package (found here) download package to a new folder and run Winbuilder.
Download the LiveXP project.
Now you should have both projects Multi Win7PE_SE and LiveXP in Winbuilder

Add Link_Creater_MPE (found here) to your Multi Win7PE_SE project.
Click or activate the Link Creater script

Now all Apps from LiveXP will be listed under Multi Win7PE_SE in Winbuilder

This part works as intended ...

Now I have to figure out what scripts work with a x64 build and what does not.. More later

Edited
Shortcuts work, but I can not add everything, lots of testing as to what works in a x64 build

[Lancelot]

Thanks for testing PaPeuser,

This is one of my old goal to easly share scripts between projects.
After a heavy pm & topic traffic with JonF and Max_Real QNX , getting their full support (thanks both a lot again) we (more or lesss) reached that goal, hence resulted with this annoucment.

I am waiting JonF active again to get full syncronisation with VistaPE-Capi. Applications on above integrator script mostly tested with VistaPE-Capi for a successful share. I cripled things and made the script to be used with Win7PE following Win7PE requirements.
(after JonF active, it would be easy to share script between 3 projects, and after leopard finished 4 ........)

Going back to subject, On apps scripts, there maybe missings, and as usual will be added in time with support and reports.
Everything takes time

[PaPeuser]

One thing ..

Win7PE_SE x64 build

When I use the Link Creator script
Shortcuts in start menu\programs are not a problem. Desktop icons work,
The store and display recently opened programs in start menu on longer works

More later

[Lancelot]

The store and display recently opened programs in start menu on longer works

I do not understand this. Can you give a basic reproducable method and explanation. (I need specific reproducable instruction to test x64 on qemu )

[Lancelot]

sorry PaPeuser, Since I do not use that feature, now i understand what you mean.
At least i can say, it is %99 caused by a script (not directly related to link creation)

Well I do not know what can effect this, but if you can track down to a script (it is really imposible for me to make frequent pe2-3-x64 tests with qemu) we can figure out what went wrong.

[PaPeuser]

I think most build problems are with scripts and tools folder.
When a script needs to unzipped or extracted and looks for the tools folder,

LiveXP has .........Project \LiveXP\ tools

Win7PE_SE has. Project\ tools\win7pe-se

Some scripts that error are
GImax – Stop build error
Zone Alarm – Stop build error
OfflineSysprep -Stops build

Fixed Win7PE_SE tools folder just does not include all the tools needed.. this fixed many script errors during build.

[PaPeuser]

Hello………..

More on using the.. Link_Creater_MPE in Win7PE_SE
Tested using Win7 x64 build…tested most scripts not all, I don’t have the time

Build errors are fixed once you get the proper tools in the WinPE_SE tools folder,

Next we find a few files are needed
Example
DriveImage XML PE needs sfc.dll

So far I have had good results … i will get a list together of files missing,

[Lancelot]

Thanks a lot for reports PaPeuser,

here are news:
"Link_Creator_MPE v2" now available at post 129
fix: required files from tools now copied if not exists .

also update LiveXP scripts from server:
infos:
"DriveImage XML PE" sfc.dll added to requirements.
GImagex –--> locked for pe1 builds (I have not tried, but I feel if you copy GImageex and use (with "Additional Files" script of MultiPE), it would work directly without any requirements, make good tests and keep me updated about that so I can make required changes on script)
Zone Alarm –--> locked for pe1 builds ==> it is currently too much work to make script pe2/3 compatible.
On relevant scripts description I add "PE1 only" note, besides even you enable these scripts they will not process giving warning on log (totally harmless). They are low in number and a lot time needed to make all them pe2/3 compatible. I can not do everything quickly, they are waiting support from pe2/3 users .
On Virtualization, only "VMXBuilder" will run, rest locked. There is a bugy on MultiPE, disable "hide shortcut cmd" box on VMXBuilder to have shortcut work.
Double Commander --> "Run From Ram" please . I put a note on script interface.
OfflineSysprep --> I just noticed your post (since edit). OfflineSysprep is Galapo's precious , I need to check and contact Galapo first.


I feel you are spending nice time through testing. Keep the good work

[PaPeuser]

I started over with a new folder….again

Win7PE_SE_04_10_2010
-Thanks JFX

Added new PENetwork – and net work card was detected without running PnP first
– Thanks Holger

Did a recommended downloaded of LiveXP..
Used the Link_Creator_MPE v2
Also all tools were copied over using the tools option in Link Creator
– Thanks Lancelot

Tested both Win7 x64 and Win7 x86, both built and booted in VMware without error……

[Lancelot]

Did a recommended downloaded of LiveXP..

just a comment, you do not have to download again and again. mostly using winbuilder do download new version(s) of scripts will be enough.

Since you are now an experienced user, To keep a perfect update without re-downloading all again Try blexactserver.

Idea of using blexactserver is having a seperate (untouched) folder to download and keep update of a project from server. As a result, when you need to test or make build, just copy this folder to another place and make your tests there . If you start to use bleaxctserver, you will understand what i mean in a short time and be sure you will like it.

[PaPeuser]

I understand and that is great idea..

I wanted to act like a new user,,,, do everything new.. Get a new clean start ..

There are a few things I have to look at ..

Running apps or scripts in PE (after boot) this will tell me more about missing files

Start menu is a little different, I need to see what scripts may have affected start menu

Basically this is one Great PE, many thanks, to many people who have made this possible.

[PaPeuser]

I do see the advantage of using blexactserver from another folder.

This updates LiveXP scripts in Apps folder and saves backups of old scripts. Then I can take the entire Apps folder that has been updated and add it to the Apps folder in Win7PE_SE, without downloading LiveXP in Winbuilder and using the Links script.

Now all Apps in LiveXP are in Win7PE_SE and can be updated easily

[PaPeuser]

Noticed a few strange things
This has been driving me nuts
First if I do a full files copy using LiveXP scripts I see the flying windows loading

If I do a standard file copy I see the Vista loading bar

Something I just noticed

With a standard file copy I see the vista loading windows and thats good, LiveXP scripts that have been added are in start menu and start menu is correct,

When I use a full files copy I see the win7 flying windows starting and start menu is different, I don’t have the recently used programs showing up or anything in list on right or start menu. -Computer -Documents (shortcuts)

Things are different with a full file copy and a standard.
Things work better with a standard file copy
EDITED in fact using a standard file copy.. things are almost perfect

i am

I dont feel like --- "Since you are now an experienced user"

[pscEx]

I do see the advantage of using blexactserver from another folder.

This updates LiveXP scripts in Apps folder and saves backups of old scripts. Then I can take the entire Apps folder that has been updated and add it to the Apps folder in Win7PE_SE, without downloading LiveXP in Winbuilder and using the Links script.

Now all Apps in LiveXP are in Win7PE_SE and can be updated easily

Maybe you do a compare with downloadEx
The advantage is that you directly can "Cross-Download"

Peter