Jump to content











pscEx's Content

There have been 1000 items by pscEx (Search limited from 15-July 10)



Sort by                Order  

#69955 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 17 June 2009 - 06:46 PM in Win7PE

In my new networking beta script (not published yet) I add these _additional_ files:
icmp.dll
ikeext.dll
kerberos.dll
msafd.dll
ncsi.dll
webio.dll
winhttp.dll
WinSCard.dll
wmi.dll

I'm already dreaming about the day, where I can see my well known nativeEx - PENetwork GUI in Win7PE.

Then build the ISO and Google in VirtualBox ;)

One small hint (not especially for Win7PE, but generally).

In next versions WinBuilder will give a (can be switched off) warning, if an existing file is overwritten.

To avoid these (unnecessary, author's 'failure') warning, for nativeEx_barebone (and valid for the complete nativeEx world) I added some code like this to your script:
If,Not,EXISTVAR,%ModelRam%,Begin

  CopyOrExpand,"%SourceDir%\i386\advapi32.dll","%TargetDir%\i386\system32"

  CopyOrExpand,"%SourceDir%\i386\dnsapi.dll","%TargetDir%\i386\system32"

  CopyOrExpand,"%SourceDir%\i386\iphlpapi.dll","%TargetDir%\i386\system32"

  CopyOrExpand,"%SourceDir%\i386\mpr.dll","%TargetDir%\i386\system32"

  CopyOrExpand,"%SourceDir%\i386\msv1_0.dll","%TargetDir%\i386\system32"

  CopyOrExpand,"%SourceDir%\i386\msvcrt.dll","%TargetDir%\i386\system32"

  CopyOrExpand,"%SourceDir%\i386\nddeapi.dll","%TargetDir%\i386\system32"

  CopyOrExpand,"%SourceDir%\i386\netapi32.dll","%TargetDir%\i386\system32"

  CopyOrExpand,"%SourceDir%\i386\regapi.dll","%TargetDir%\i386\system32"

  CopyOrExpand,"%SourceDir%\i386\ws2_32.dll","%TargetDir%\i386\system32"

  CopyOrExpand,"%SourceDir%\i386\ws2help.dll","%TargetDir%\i386\system32"

End
(you can download from the nativeEx server)
If %ModelRam% exists, you are in the nativeEx world, and these files are already well known from Copy&Expand script.

I think, something similar can be done for the Win7 world.

Peter



#70318 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 22 June 2009 - 07:57 PM in Win7PE

Maybe the 'shortcut' developers/users have a look here
I did not answer in this topic, in order not to become propably OFFTOPIC or 'second line'

Peter



#69442 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 11 June 2009 - 06:36 PM in Win7PE

Suggestions for 7 - Create ISO:

1. Replace the [Interface] section with:


and replace the [Grub4DosMGR] section with:

Adding a file to menu.lst is needed because the entire menu.lst file is deleted and created after all other scripts have run. If someone wants to add a script (such as Parted Magic) that needs an entry in menu.lst, it has to write some other file that CreateIso will then add.

Of course, if two scripts want to add entries to menu.lst there is a problem ... they have to agree on what extra file to write their entires in. I think that the creation of the beginning of menu.lst should be moved to some place early in the build, as it was in VistaPE. Then scripts can add their entries directly.

2. Update Grub4DOS to version 0.4.4 2009-05-23, Memtest+ to version 2.11, and memdisk to version 3.82.

Here's a copy of the resulting script file:

Looks good (As far as I can see from GUI)! ;)

Maybe that me fool will understand GRUB and WIM and WIN7 and WPEINIT and IKEEXT and ... and ... and other strange things in some Latin weeks.

I'm working on that. My interest in my nativeEx baby decreased a lot last days.

It's the same like with human parents.

When your children join other son and daughter-in-law with different interests, then it is better to let them live their life ...

Peter



#69410 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 11 June 2009 - 07:10 AM in Win7PE

Get a FileCopy Error

FileCopy - Failed to copy
[%BaseDir%\Temp\Win7PE\BootWimSrc\Windows\system32\wdscapture.inf] to:
[%BaseDir%\Target\Win7PE\Windows\system32\]

no such "wdscapture.inf" in ...\BootWimSrc\Windows\system32 folder.

*** OS - Win7RC, WALK - v2.0 (for Win7RC), WinBuilder - v77rc ***

Try a different WAIK. I have Vista 1.1 OPK and that works on OS Win7RC1 with WB77RC1.

@yahooUK: When I tried to build from WAIK only (like nu852 does), 0 - PreConfig did not find winpe.wim in my 'OPK'
You only use hardcoded 'AIK'

Try to use the contents of the FileBox
StrFormat,CTRIM,%pFileBox1%,\,%path%

If,ExistFile,"%path%\Tools\PETools\x86\winpe.wim",Set, ...

Peter



#69276 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 09 June 2009 - 03:25 PM in Win7PE

Hello eveybody ;)

Why not use the autorun.cmd and remove [autorun] section in the goal to autostart application / service in startup of WinPE ? ;)

How can i add a line in autorun.cmd with my script (As the clid.reg...) ? :)
I have test :
TXTAddLine,"X:\Windows\System32\autorun.cmd","#$qregedit.exe /s x:\Windows\System32\SideBySideXn5.reg#$q"

But no result in my autorun.cmd ? :)

You forgot to tell WinBuilder where to place the line! :angry:

TXTAddLine,Filenam,StringLine,APPEND
TXTAddLine,Filenam,StringLine,PLACE,LineNumber
TXTAddLine,Filenam,StringLine,PREPEND

Peter



#70680 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 28 June 2009 - 01:10 PM in Win7PE

[%GlobalTemplate% issue will be solved by experts.

%GlobalTemplates% is used in the nativeEx world.

If in the Win7 world there are files to share with / from nativeEx, like Joshua I recommend same names.

Peter



#70692 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 28 June 2009 - 03:37 PM in Win7PE

at me in "Finalize/USBDevice.script"
the line

ShellExecute,Open,"%BaseDir%\Temp\HPUSBFW.exe" -f,"#$q%pFileBox1% #$q"
doesn't work
i have to change into
ShellExecute,Open,"%BaseDir%\Temp\HPUSBFW.exe"

Is the space behind %pFileBox1% just a typo here, or is it in the real command?

And the ShellExecute cmmd syntax is ...<exe><comma><parameters>
I think, it should be like (Sorry, I do not know the exact hpusbfw syntax)
ShellExecute,Open,&#34;%BaseDir%\Temp\HPUSBFW.exe&#34;,&#34;-f#$c#$s#$q%pFileBox1%#$q&#34;

Peter



#70929 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 02 July 2009 - 04:21 PM in Win7PE

Actualy in liveXP Parameter #4 is for copy MUI file but i think to push it to parameter #5
and use Parameter #4 for the new Command PRESERVE

:lol:

Thanks, Pedro!

This shows that you are really following reality in development. ;)

On the other hand:
Reality is also 'Existing scripts'. What about compatibility?

I would add PRESERVE as '#latest'

Peter



#70918 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 02 July 2009 - 03:04 PM in Win7PE

As we are currently speaking about future:

Mainly @Joshua:

Pedro's API in cooperation with a section inside the nativeEx buildModel.Script generates a 'general shortcut description (INI style) file' like this:
&#91;Created&#93;

Program=shortcutParse

Version=1.1.2

&#91;Shortcut&#93;

targetDir=V&#58;\WB\wb debug\Workbench\nativeEx_barebone\UserData

modelDir=V&#58;\WB\wb debug\Workbench\nativeEx_barebone\UserData

shortCutName=WinServices

shortCutType=SM

shortCutLocation=Develop

shortCutExe=%SystemDrive%\Programme\WinServices\WinServices.exe

shortCutToolTip=

shortCutParameters=

shortCutShow=

shortCutDir=%SystemDrive%\Programme\WinServices\

shortCutHotKey=

shortCutIconFile=

shortCutIcon=0
After that, in the nativeEx world the section [Add-Shortcut] of the %ActiveScript% is called to creatwe the shell depending shortcuts.
%ActiveShell% is usually explorer, but there also exists e.g. such a (working) section in the xoblite.Script which I wrote for sample.

Could it be possible to generate shortcuts using such a 'general description'?

Peter



#70813 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 30 June 2009 - 10:07 PM in Win7PE

I'm rather outside and sure that you see the details better than me.

I only wanted to tell some doubts:

Do you think I need to change those variables to compactable with all projects working?

If you replace the NEED by SHOULD: A clear YES

Without changing, all projects are not working anymore?

The suggestion only affects Win7PE. If you (do not) do anything, no other project is disturbed in any way.

Doing Win7PE Project, why the words "Win7pe" can't be used as variables?

If you look into different projects, they do not use the project name as (a part of) the variable name, but as the variable value.

And that is what Pedro suggests.

Sample, I know that you do not use it, and it has no connection to a real world, just to explain:
Do NEVER use %Win7PE%=%BaseDir%\Win7PE
Use instead %MyProject%=%BaseDir%\Win7PE.

Peter :lol:



#70807 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 30 June 2009 - 08:53 PM in Win7PE

I mean I have given tons of hours to work all my scripts, files and registries.
And finally, these scripts did work, and have worked, and are working, and will work.
I like some ideas in your scripts but not variables.
My scripts are working with Vista as well as Windows 2008, I suppose.(not tested but I'm sure)
Therefore my variables are not possible to change under your idea now and never.

@YahooUK:

I do not demand, I do not recommend, I do not suggest. I only as friend tell you something very quietly:
Please think again about Pedro's suggestion.

The vision is:

Any (well written) app script from nativeEx world, Vista world, ??? world can be inserted into Win7PE w/o any adaption.
That is an exciting target, and you can help to reach it.

Peter :lol:



#69207 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 08 June 2009 - 05:39 PM in Win7PE

New win7peldr is ready! ;)
http://www.drowaelde...r/win7peldr.exe
It reads [main] autorun from Win7PE.cfg
autorun=normal
or
autorun=background

If autorun=none, it will not call autorun.cmd


Next on todo list is reading [main] screen from Win7PE.cfg to set the correct screen resolution. ;)

Joshua

I'm only engaged in trying to improve the 'standard' Win7PE project's commands more efficient.

But I have the feeling that you are becoming the second architect of a project which can become the second flagship of WinBuilder!

:)

Peter



#69193 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 08 June 2009 - 12:33 PM in Win7PE

"Now it is ready for download from http://win7pe.winbuilder.net.".
why don`t open this website?

That's the root of the server, which appearentyl is non-public.

The whole project can be found at http://win7pe.winbuilder.net/Projects/
Or try this link in WinBuilder's download center.

@yahoouk: You should update the link!

Peter



#68586 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 31 May 2009 - 07:08 PM in Win7PE

error filecopy in WB77b3.
Please see attached log.

If in a FileCopy command with wildcards no file has been copied, 077B3 gives an error, while older versions do not.
This is the same reaction like for FileCopy a single file.

If there would't be this error, you would never see a misspell of the file name / path, and you could search for days, why your project does not work.

If in a command there it is possible that there are no files to copy, you can write as previous command:
System,ERROROFF

Peter



#68591 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 31 May 2009 - 08:10 PM in Win7PE

So no wildcards support in Beta 3, is it right?



Not clear what you mean. My reading is so bad.
Sorry.

Thanks for your reply.

B Regards,

yahooUK

Your quote has been incomplete, and that can lead to misunderstandings.
It should be:

If in a FileCopy command with wildcards no file has been copied, 077B3 gives an error, while older versions do not.


Maybe it's my fault, I should better have written:

If in a FileCopy command with wildcards no matching file for copy has been found, ...


Of course, there is still wildcard support!

Try in codebox
&#91;process&#93;

	 If,Not,EXISTDIR,%BaseDir%\CopyTest,DirMake,%BaseDir%\CopyTest

	 FileCopy,%WindowsDir%\System32\*ga*,%BaseDir%\CopyTest

	 FileCopy,%WindowsDir%\System32\*xxx*,%BaseDir%\CopyTest
The '*ga*' line will copy a lot of files.

The '*xxx*' line will give an error, because there is no *xxx* file.

To avoid the error message, use
&#91;process&#93;

	 If,Not,EXISTDIR,%BaseDir%\CopyTest,DirMake,%BaseDir%\CopyTest

	 FileCopy,%WindowsDir%\System32\*ga*,%BaseDir%\CopyTest

	 System,ERROROFF

	 FileCopy,%WindowsDir%\System32\*xxx*,%BaseDir%\CopyTest

Peter

BTW: WB 074 copies with the line
FileCopy,&#34;%iw%\winsxs\*pwindowmanager.udwm*&#34;,&#34;%tx%\&#34;
no file.

WB 077 beta3 copies with the line
FileCopy,&#34;%iw%\winsxs\*pwindowmanager.udwm*&#34;,&#34;%tx%\&#34;
also no no file, but gives an error.

I'm sure that some files should be copied here.

That is the situation I meant with

If there would't be this error, you would never see a misspell of the file name / path, and you could search for days, why your project does not work.




#68434 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 28 May 2009 - 12:28 PM in Win7PE

@Psc,

Maybe winbuilder should have an option to update the progress bar during FileCopy. Don't want to have to look at an ugly command window whilst doing the build.

This morning I've had the same idea.
Results:
Filecopy with wildcards can have an additional argument 'SHOW'.
ShellExecute can have an additional argument 'SHOW'.

Peter



#68408 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 27 May 2009 - 06:43 PM in Win7PE

May I make two suggestions:

#1: 0-preconfig.script:
The script should detect 'orphan' mounts from previous build and unmount them. Also the script should halt the build when the mount task has no success.

#2: 1-files.Script:
It takes several minutes to process this script. During this time, an unexperienced user thinks that WinBuilder hangs, and may kill the build.
(And then he is in issue #1 ...)

Suggestion to replace the 'FileCopy...*.* by a Shellexecute,...xcopy

Two advantages:
  • The cmd window can be shown by shellexecute,OPEN,... and therefore the user sees that something is happening
  • xcopy accepts an 'exclude' list, in this case a list of all not-used-language-specific-files (nice word? :D )
The modified scripts you can download as http://nativeex.boot...st/New_win7.zip
(They are too big to attach here)

Peter



#68289 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 25 May 2009 - 07:39 PM in Win7PE

When I try the 'Full Copy' I get the same errors like JonF.

That seems to be a project issue (I do not want to solve right now :D )

@yahoouk: I do not see any BIG LOGICAL difference between the files copied by 'Standard' or 'Full' (besides this 'small' error).

I suggest, to remove the 'Full' option and do everything 'Standard'.


Peter



#68610 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 01 June 2009 - 07:59 AM in Win7PE

Why FileCopy failed to copy a lot files even there is no wildcards?

As you see that are not errors, that are warnings.

The file to copy already exists at the target and is overwritten.

Reason for the warning: There could be a different file (different version etc.) which is lost by the copy.

BTW: To NOT overwrite an existing file, use
FileCopy,<source>,<target>,PRESERVE
But this also will give a warning.

You can avoid the warnings by checking:
If,Not,EXISTFILE,<target>,FileCopy, ...

Peter



#68637 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 01 June 2009 - 02:57 PM in Win7PE

Also noticed that even though I have 'standard file copy' selected it shows 'processing full copy' will look again to see for sure.

There is (I think from debug) a command line left to do the full copy independent from the option.

Peter



#69182 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 08 June 2009 - 11:19 AM in Win7PE

I agree to JonF

In 'Factory setting' shortcuts should be at a 'logical' place.

For me between 'shortcut' and 'net' there is no logical relationship.

@yahoouk: Please do not worry in this early stage to make a couple of changes (including the spent hours).

That makes your project 'professional' and open for future addons.

Peter



#69069 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 06 June 2009 - 09:10 PM in Win7PE

A question for all:

We now have two projects which are based on non-XP sources and many projects based on XP sources. Sometimes scripts need to know which type of source is being used.

I've been using

[cpde]StrFormat,Left,%ProjectName%,7,%Project_Type%
If,%Project_Type%,Equal,VistaPE,Begin[/code]

but that doesn't work in Win7PE.

How should we standardze this?

In nativeEx based projects there are some variables defined in script.project
(Sample, I do not know whether complete)
%OS%=XP

%SourceLocale%=00000407

%Locale%=00000407

%DefaultLayout%=00000407

%spCabFile%=SP3.cab

%drCabFile%=driver.cab

%OSSubType%=Pro

%OSServicePack%=SP3
Maybe in Vista / Win7 projects the same variables should be introduced.
Maybe a question of API, to perform some currently project specific tasks like (nativeEx) ProjectInfo.Script
Peter



#69025 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 06 June 2009 - 03:21 PM in Win7PE

Why not use a dynamical size?

Set,%BootBlock%,<boot sector file name(no path)>
Run,%ScriptFile%,GetBlocks,%BootBlock%
Set,%cmd%,"-iso-level#$s4#$s-force-uppercase#$s-volid#$s#$q%pTextBox1%#$q#$s-b#$s%BootBlock%#$s-no-emul-boot#$s-boot-load-size#$s%BootSize%#$s-hide#$s%BootBlock%#$s-hide#$sboot.catalog#$s-duplicates-once#$s-o#$s#$q%IsoFile%#$q#$s#$q%targetdir%#$q"
ShellExecute,Hide,%Tools%\mkisofs.exe,%cmd%

[GetBlocks]
Retrieve,FILESIZE,%TargetDir%\#1,%BootSize%
StrFormat,DIV,%BootSize%,512

@Sonny, again thanks for your help in the 'Voodoo'

Peter



#68728 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 02 June 2009 - 11:26 AM in Win7PE

Hmm, been doing some testing now, and to work in Win7 PE the explorer needs CLID.reg to be run in autorun.cmd before explorer.exe.

The problem with this is that it basically overwrites the whole classes -registry and if some program script has added some classes- values those will be overwritten as well. So in order to get those programs working you have to manually make another reg import that will again write the classes -values after CLID.reg in autorun.cmd

The solution would be to find what components in CLID.reg are necessary for explorer.exe operation to slim it down (I know, it's a lot of work..). As some might know, if you don't run CLID.reg before explorer.exe in autorun the explorer shell will not load and system will reboot.

Please allow the question of a fool:

Why not include the (needed) contents of CLID.reg in the explorer script?

Peter



#70931 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 02 July 2009 - 04:32 PM in Win7PE

Nearly everything is possible. ;)

You are reacting nearly like Jaclaz with "Yes/No" (and also using Jaclaz's smiley for that ;))!

Peter :lol:



#70950 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 02 July 2009 - 07:11 PM in Win7PE

Good question PSC, i will test the compatibility with 'Existing scripts' in VistaPE and Win7PE...

:lol:
And if there are any incompatibilities which propably can be solved by a WB.exe change, please tell here and I'll try to solve.

As I already told anywhere, I have the feeling, that Win7PE is becoming the new flagship. nativeEx is ice-age. But some relevant nativeEx parts can help the 21th century to become successful.
So, if your results violate some nativeEx rules, do not worry. I can change that. In my schedule I do not support nativeEx after WB 078. The motivation to support is gone.

Peter



#73827 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 06 August 2009 - 10:35 AM in Win7PE

I use WinBuilder_077_RC2 and WinBuilder_077_BETA3. Both works for me.
WinBuilder_077_BETA3 is a little faster. :idea:

Joshua

That depends on the overwrite checks which are added in RC2.
They are currently 'ON' by default, in order to force developers to revide some scripts.
(I think RCs are mainly used by developers)

In the final version they are 'OFF' by default.

Peter



#74179 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 10 August 2009 - 07:10 PM in Win7PE

Please allow me a remark:
A comment line is started by two slashes // (two ## are accepted for old VistaPE compatibility)

A semicolon currently causes that the complete line is ignored. But what in next WB release ...

Peter



#73337 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 01 August 2009 - 02:38 PM in Win7PE

I built with WB077Rc2 from Win7 RC1 German source, and got a lot of errors telling that some English mui files are not found.

But the PE booted fine in VirtualBox.

Suggestion: Would be nice if Joshua's passwort protection is switched OFF in factory setting.

It took a while until I found anywhere (nearly hidden) a small hint about the password. :idea:

Peter



#73273 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 31 July 2009 - 08:37 PM in Win7PE

exactly the same

on root of D in a folder called win7petest and source files are in a folder called win7source

I copied the whole file structure from my Windows 7 PC to my XP machine, so everything is identical

Sorry, if I nerve you with stupid intentions:

Can you post log.html, hives and a 'DIR <target> /B /s' of both?

Peter



#73266 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 31 July 2009 - 08:12 PM in Win7PE

Made one change and now it builds fine!!

Instead of building on my Windows 7 RTM machine, I copied the whole build folder over to a Windows XP machine and it builds fine - so perhaps part of these problems is simply what OS you are building on?

Will now boot the ISO and report back if it works okay

Is your machine 64 bit?

If yes, maybe a new issue for the '64 bit' topic.

Peter



#74183 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 10 August 2009 - 07:19 PM in Win7PE

ok, changed

&#91;DetectSourceType&#93;

;If,ExistDir,&#34;%BootSRC%\Windows\SysWOW64&#34;,run,%ScriptFile%,WrongBootWim

;If,ExistDir,&#34;%InstallSRC%\Windows\SysWOW64&#34;,run,%ScriptFile%,WrongInstallWim
See log attached


Uncheck Tools > Options > Debug Log in the middle right and rebuild the project. Then post the resulting log.

Peter



#78808 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 17 September 2009 - 08:40 PM in Win7PE

As a result:
Because I do not really believe on ;) :
Boomdude, please post the log w/o your fix (where your trouble occurs)

Peter



#95865 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 25 March 2010 - 08:47 PM in Win7PE

The questions of PaPeuser's last post are understandable, but IMO UNNECESSARY!

Every member should know (by reading the board rules) that nobody of us has a working Crystal Ball, and that therefore members should add as much information as possible to their question, at least a log of their build.

Peter



#81068 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 06 October 2009 - 10:00 AM in Win7PE

Hello,

Just downloaded the project and build it to a isb drive. Booting works fine then i get a Prelogin box that ask for a password

What is the password ?


Greetings

See e.g. here: http://www.boot-land...?...ost&p=78347

I got it from a forum's search with "+win7pe +password" :hypocrite:


EDIT:
BTW: This is for Win7RescuePE, I'm not sure whether it is also valid for YahooUK's Win7PE.
But the 'Search' should bring success

Peter



#78909 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 18 September 2009 - 02:48 PM in Win7PE

:unsure:
:(

Peter



#78905 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 18 September 2009 - 02:12 PM in Win7PE

Just downloaded & built one successfully, couple of Avira errors but as a whole, the thing works. So, should I / we start using the Rescue project instead of just Win7PE?

The projects are different, and I have no recommendation, not even an opinion, whether to use #1 or #2.

The user, in this case you, decides.

Peter



#73257 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 31 July 2009 - 06:36 PM in Win7PE

What I meant with 'difficult to find':

I know that the project can be got by using WinBuilder's download manager.

But I think as a 'foolish' new user wanting to download your project.

This topic tells a lot about the Win7PE project, but NOWHERE (exception your last post) there is a link where to get -or did I oversee a link?
And in the 'standard WinBuilder' this link is not included yet.
In my opinion you should edit the first post and add the link there, better, explain how to add it to WinBuilder's download center.

This helps new users to get your project, and not to say 'forget it' because they cannot find it.

Peter



#73249 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 31 July 2009 - 05:50 PM in Win7PE

My scripts are horrible or something is going wrong???

I cannot say that your scripts are horrible, (they in deed are interesting and promizing some new solution) but sometimes they seem to be ... :idea:
Seriously:
The project is not only tested by experienced members like you and me.
The project is also tested by new members or guests with a low level of WinBuilder experience.

You should do everything possible that a new user cannot make unwanted mistakes.

If. e.g for some new scripts WB 077 RC2 or later is necessary, include in the script something like
If,%version%,SMALLER.77,Halt,&#34;For this script WinBuilder Version 077 or higher is needed&#34;

BTW: To unmount an 'left orphan' mounted WIM, there should be a command in one of the earliest scripts like:
If,EXISTFILE,<some typical WIM file in mounted WIM>,Run,%ScriptFile%,&#34;UnMount the WIM&#34;

BTW2: It is very difficult to find the latest version of your project.
What about to add a link to the latest version to your signature?

Peter



#71471 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 10 July 2009 - 11:22 AM in Win7PE

Some more tests showed that this difference propably is not important.

I mounted the two different BCDs with regedit and exported them to a *.reg.
The two *.regs are 100% identical.

So I continue to search.

Peter



#71231 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 07 July 2009 - 02:51 PM in Win7PE

Maybe that helped in your case, but I'm sure that the path name is NOT the reason for the troubles. Maybe that the project went correctly now, because some other conditions, like some Temp contents etc. also has been changed or deleted during install to the new directory.

The WinBuilder development team members have intentionally the %BaseDir% = "?:\WB Debug". For me is ? = V.

I also have had sometimes the black screen, but that always had to do with some environment issues, maybe a not correctly mounted WIM, or missing mui files and similar.

In my opinion

is a rumor.
(Provided that there is no file to copy which exceeds the Windows defined maximum length of a path name. But in my oppinion with Win7PE that cannot happen with most 'simple names'. If on the other hand your %BaseDir% is like "X:\My base Installation directory to test WinBulder\This is for testing Vista\And this is for testing SP1\And a lot of other definitions ...", maybe the maximum path length can be reached. But in this case WinBuilder brings an error message.)

If you find a project which UNCHANGED runs at a 'simple' folder, and fails at a 'complex' folder, please post BOTH complete projects (even if you think that they are identical).

I would be glad to have the possibility to catch a new ;) .

Peter

Thanks to onycs :lol:
He sent me a DVD containing a lot of material to examine.

What I found:

Different BCDs are written.

The Black Screen BCD is corrupted (?) The first part of the path 'C:\Users\****\Documents\*****\WinBu' is lost.
(names overwritten by me with *)
35 characters, no 'binary' number.
Win7_Compare_Black.gif

The BCD of the booting ISO is ok:
Win7_Compare_Boots.gif

The Black Screen is really path dependent. But I cannot see the 'How' yet.
Therefore my questions to the Vista / Win7 experts:

Is that difference relevant?
Where in the project (and how) BCD is written / changed?

Peter



#70989 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 03 July 2009 - 11:05 AM in Win7PE

Tomorrow I'm going to compare beta3, RC1 and RC2 and will report.

Here the results:
WB077 B 3:
Main Configuration Version&#91;10&#93;  0.234 seconds 

 Extended Configuration Version&#91;10&#93;  0.172 seconds 

 0 - PreConfig Version&#91;11&#93;  8.284 seconds 

 1 - Copy Files Version&#91;11&#93;  53.133 seconds 

 2 - New Hives for win7PE Version&#91;11&#93;  4.477 seconds 

 3 - Shell & Config Version&#91;11&#93;  2.387 seconds 

 PEshell Version&#91;10&#93;  0.312 seconds 

 qDir Version&#91;10&#93;  0.390 seconds 

 Additional Files Version&#91;10&#93;  0.470 seconds 

 Windows 7 Explorer Version&#91;11&#93;  24.445 seconds 

 Explorer Tweaks Version&#91;1&#93;  1.919 seconds 

 MMC Version&#91;9&#93;  4.524 seconds 

 PENetCfg Version&#91;10&#93;  1.622 seconds 

 VMWare Ethernet Version&#91;3&#93;  0.780 seconds 

 8 - Create Shortcuts Version&#91;9&#93;  0.500 seconds 

 6 - PostConfig Version&#91;10&#93;  52.291 seconds 



 16 scripts processed. 

 Project time&#58; 2 minutes, 35 seconds and 251 miliseconds
WB 077 RC 1:
Main Configuration Version&#91;10&#93;  0.234 seconds 

 Extended Configuration Version&#91;10&#93;  0.187 seconds 

 0 - PreConfig Version&#91;11&#93;  8.206 seconds 

 1 - Copy Files Version&#91;11&#93;  42.307 seconds 

 2 - New Hives for win7PE Version&#91;11&#93;  6.474 seconds 

 3 - Shell & Config Version&#91;11&#93;  3.136 seconds 

 PEshell Version&#91;10&#93;  0.312 seconds 

 qDir Version&#91;10&#93;  0.765 seconds 

 Additional Files Version&#91;10&#93;  0.310 seconds 

 Windows 7 Explorer Version&#91;11&#93;  1 minute, 11.325 seconds 

 Explorer Tweaks Version&#91;1&#93;  1.825 seconds 

 MMC Version&#91;9&#93;  3.432 seconds 

 PENetCfg Version&#91;10&#93;  1.389 seconds 

 VMWare Ethernet Version&#91;3&#93;  0.940 seconds 

 8 - Create Shortcuts Version&#91;9&#93;  0.468 seconds 

 6 - PostConfig Version&#91;10&#93;  58.671 seconds 



 16 scripts processed. 

 Project time&#58; 3 minutes, 19 seconds and 308 miliseconds
WB 077 RC2:
Main Configuration Version&#91;10&#93;  0.281 seconds 

 Extended Configuration Version&#91;10&#93;  0.187 seconds 

 0 - PreConfig Version&#91;11&#93;  8.127 seconds 

 1 - Copy Files Version&#91;11&#93;  43.743 seconds 

 2 - New Hives for win7PE Version&#91;11&#93;  5.928 seconds 

 3 - Shell & Config Version&#91;11&#93;  2.964 seconds 

 PEshell Version&#91;10&#93;  0.468 seconds 

 qDir Version&#91;10&#93;  0.733 seconds 

 Additional Files Version&#91;10&#93;  0.470 seconds 

 Windows 7 Explorer Version&#91;11&#93;  1 minute, 12.134 seconds 

 Explorer Tweaks Version&#91;1&#93;  2.137 seconds 

 MMC Version&#91;9&#93;  5.258 seconds 

 PENetCfg Version&#91;10&#93;  1.248 seconds 

 VMWare Ethernet Version&#91;3&#93;  0.171 seconds 

 8 - Create Shortcuts Version&#91;9&#93;  0.546 seconds 

 6 - PostConfig Version&#91;10&#93;  1 minute, 1.308 seconds 



 16 scripts processed. 

 Project time&#58; 3 minutes, 25 seconds and 718 miliseconds
Is it right that explorer processing is remarkably slower. On the other hand processing of 'copy files' is remarkably faster.

I'll observe this and try to find which internal process used especially for explorer, might be slowed down.

Peter



#70963 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 02 July 2009 - 08:24 PM in Win7PE

Is there anybody who tried with WB77RC1?
I've experience with speed, it's quite slow compare with Beta3.(Build time's gone up from 6 to nearly 10 minutes for my testing one)

I do not have this feeling.
(I'm using RC2)
Tomorrow I'm going to compare beta3, RC1 and RC2 and will report.

Please tell me: Original like downloaded? Or some API / Joshua / ??? addons?
And to be sure, repeat download URL.

But now please allow me ;)

Peter :lol:



#71897 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 16 July 2009 - 08:08 AM in Win7PE

@onycs!

I have the (crazy) idea that the black screen can be caused by a NTFS compressed %BaseDir%.

Can you please check whether your 'bad' %basedir% is compressed, while the 'good' is not?

If yes, try to uncompress the 'bad' dir and try again.

Thanks

Peter



#72686 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 26 July 2009 - 07:36 PM in Win7PE

And also tried to fix the black screen to test for Onycs :P

Any explanation how the black screen is caused (I currently have none, and am fishing in the dark)?

If yes, I'll try to suggest you for the next Nobel Price, Oscar, ... :)

Peter :idea:



#73124 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 30 July 2009 - 02:59 PM in Win7PE

Peter it just finished and I have the log but how do I generate a 'complete project build log'? It seems like no WIM is generated that I can see! WTH is going on? :P

Can't attach log, it is too large :idea: lame..

Rebuild the COMPLETE project, and ZIP the log.html. Then it is rather small and can be attached.

Peter



#73120 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 30 July 2009 - 02:41 PM in Win7PE

Running another build now but with the Debug Log enabled for a more verbose output log.

That's nice that you did so. But where is the log :idea:

On the other hand, it would not help more than the previous log.

It just tells us that robocopy copies somethnimg.

But who knows, what is copied ...

No idea, whether a *.wim is generated, and if yes, whith which content.

What is needed, is the complete project's build log.

Peter



#73017 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 29 July 2009 - 06:37 PM in Win7PE

Here ya go :P

Your log shows that copying of gpedit.msc was not successfull. and the build stopped therefore.
I cannot decide why. But maybe this file is not essential for the PE.
@yahooUK: you should check and maybe correct :idea: :)
@Corio: Try in WinBuilder > Tools > Options >> uncheck 'Stop Build on Error' and rebuild.

If this PE runs well, the 'gpedit' should be a different topic.

Peter



#72994 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 29 July 2009 - 04:26 PM in Win7PE

After updating with the new script when I play my build it doesn't create/copy any .wim files to my build, any ideas? Does this have to do with the 'pre-config' boot.wim and install.wim containers?

Thanks..

Sorry, currently my magic crystal ball is out of order.

To get an idea about your troubles, please, post your log.html

Peter



#68286 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 25 May 2009 - 07:19 PM in Win7PE

@JonF!

In 'Copy Files', please try 'Standard' rather than 'Full'

Maybe in the 'Full copy' there is an issue.


Peter



#68200 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 24 May 2009 - 10:20 AM in Win7PE

Have problem with WinBuilder 77 beta 2.

The process stop at a command "DirCopy", I don't know whether or not it is the problem of WinBuilder 77 beta 2.


Testing under VirtualBox v2.2.2
--------------------------------------
VirtualBox Client - Windows 7 RC (Eng)
Win 7 DVD Source - Windows 7 RC (Eng)
WALK - Walk 3.0 beta (Eng)

Previous to that error there is a warning that the WIMs are not mounted.
So the directory to copy does not exist and the error is ok.

@yahoouk: The project should stop at the warning already.

Peter



#66148 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 27 April 2009 - 08:50 PM in Win7PE

Fantastic!
:)

YahooUK

OOPS, I found another one:
wb49.gif
:)
Peter



#66150 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 27 April 2009 - 08:56 PM in Win7PE

I did not use "must" word in my post. Because sometimes WB skips something. e.g. cscui.dll file. Sometimes it is not been copied even it is obviously in the folder. So I commented that line.
Sometime WB unmounted the wim file, I mean imageX. I am sure some people would have experienced with that mount error in starting it.
I'm not sure what is wrong with it. WB bug or source bug. Therefore, I recommend the simplest way and the way least error occurs during process. I am not arguring with any body. I run this project over hundreds of time before uploading.
That is my way. If anybody wants going any way, go ahead. They have their rights. :)

B Regards,

yahooUK

Great!

Then we can go step by step through these :)
You give me the food and I'll eat!

Let's start with:

What's the issue with cscui.dll?

I promise you: If you supply, in some (mediterranean) days there are no more :) s

Peter



#66145 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 27 April 2009 - 08:31 PM in Win7PE

And your project folder should be in root e.g c:\7pe d:\7pe e:\7pe ect.

@yahoouk!

As you se on my 'thanks', I appriciate your post very much.

It is something that in my opinion has also been necessary (but never given) for the logical parent of your project.

And the explanation is clear and understandable.

But as usual, one complain.

The requirements
  • Must be in the root
  • Must not contain spaces
are not requirements of WinBuilder.
Maybe that is only a rumor or remainder of some old bugs from the early 52th to the late 72th
Maybe that is 'proofed' by a erroneous script. But then the script MUST be corrected.

Fact is: The WinBuilder development team has INTENTIONALLY the WinBuilder develop %BaseDir% directory, in my case V:\WB\wb debug)
  • Not on C:
  • Having a space in the name
And there never have been troubles with this directory.
As you can see some posts above, I did a very successful build of the latest Win7PE in this %BaseDir%

@yahoouk: Your recommendation about the %BaseDir% path implies a hint on a bug of WinBuilder, which really does not exist.

Please do me a favour and edit.

Peter



#66142 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 27 April 2009 - 08:16 PM in Win7PE

how long has that big blue button been their??!?

The oldest one I have in my archive: :)
wb52.gif
Peter :)



#66136 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 27 April 2009 - 07:43 PM in Win7PE

Hi, I'm new here. But I'm an old reader, wrote scipts and compiled many custom builds with WinBuilder in the past 2 years. Thanks for the experts I learned much here.

First of all, yahoouk you did a nice work! ...but I don't want to follow the way you do it.
Your script is copying the whole MS BootWIM to the new compilation. It takes very much time and almost 1GB of diskspace.

I started my own 7 PE scripts in february (based on the last VistaPE scripts) but I stopped doing it, because my experiment finished in a nice Bluescreen (because of a missing component).
You are a step before us, because your 7 PE is running. :)

I think that we must follow the old way, to putting each component after the other stable/working component. Therefore we should start from the simplest working base system.

Any opinion?


Welcome ec!

I agree for 200% to your opinion. :)

If you look at 'my baby' nativeEx:

The core should contain only what is necessary to build a working PE.

Every script should add reg entries, files etc. what it needs to run.

I hope that yahoouk agrees to
  • remove all 'unnecessary stuff' from the core and just build a booting 'minimized W7 core' project
  • edit the addons like apps step by step and add the necessary functionality.
I remember that with nativeEx that has been a hard way:
Try and Error: Remove one component from registry / files and see whether the project still works ... :)

Peter



#66157 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 27 April 2009 - 09:32 PM in Win7PE

I have successfully builded win7_pe. Problem was with RoadKill plugin (I disabled it).

I have tried booting with vmware but there is something strange - it hangs on manual installing of net adapter and penetcfg don't start.

Booting with virtualbox works fine, but penetcfg cannot configure network. I have slightly modified penetwork plugin (desription in previous posts) but it also cannot get ip address.

From things which alsa don't work is "start menu" - Programs category is empty.

Great!

You now are about 90% in the success area!

The missing 10 % may follow tomorrow (for me it's late enogh now).

But please try to describe the issues with VMWare and VirtualBox more specific.
(@Nuno, @Jaclaz: Where is the link to the board rules?)

Peter

BTW: Theoretically it is possible that these functionalities in the project under development are not yet implemented, and you have to spend us some patience ...



#66199 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 28 April 2009 - 08:10 AM in Win7PE

Link added to the right side column of the site! :)

Where?
bootland.gif
Peter :)



#66270 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 28 April 2009 - 04:56 PM in Win7PE

@jaclaz!

As paraglider already stated, this topic is totally running 'Out of order'.

If I would be yahoouk, I would be very unhappy with the fact, that the visitor needs a map to navigate through my project's topic

Can you try to move the according posts to a new 'licence discussion' topic?
(and during move delet this -then unnecessary- post)

Thanks

Peter



#66242 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 28 April 2009 - 12:38 PM in Win7PE

...and in the meantime not-redistributable files are hosted and available for download....

I disagree!

Not to your sentence, but to the fact if it is true.
Maybe you remember that, whenever I saw such a file attached to a script, I asked the author to remove.

But there are so many scripts...
And I look not into all of them...
Especially in this actual project I only 'Run it' to see whether it works for me.

If you know some 'warez' files, please ask the author to work legal.
The 'Ask' must not be necessarily public.

Peter



#66239 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 28 April 2009 - 12:11 PM in Win7PE

This thread is out of control. Too many irrelevant posts.

Note MS components should not be redistributed. That includes any component from the WAIK. Only legal way to use any component from the WAIK is to download the WAIK from MS

You misunderstood.

It is never intended to distribute any file of the WAIK.

The WinBuilder Development Team is currently working on raw read and write *.WIM files.
And RAW means: Also not using wimgapi.dll. :)

Peter :)



#66225 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 28 April 2009 - 10:31 AM in Win7PE

Classic skin updated too, it's placed on the top bar.

:) :)

Peter, would it be possible to include the WIM read/write feature without compression?

In my opinion that is the highlight (but then with compression) for WinBuilder 080.

As to be seen from reaction to 077 beta 2, RC1 soon can be published and then the final release.

To add such new things here may disturb the flow.

Peter



#66126 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 27 April 2009 - 06:58 PM in Win7PE

psc sorry for not answering the question about downloading problem - I just downloaded 7zip file. I have tried now from home (previous was from company ;-) ) and everything with download is ok.

Now there is problem with building, described previously. I would be appreciate for help...


I'm not sure what the zipped project contains. I did not try. But the 'normal' way is download center.

Try what I suggested to darren rose in post #173 (please respect the EXACTLY).

And if there are troubles, tell us EXACTLY the first issue (the following ones are usually unimportant, because they usually are caused by the first one).

Peter



#66125 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 27 April 2009 - 06:52 PM in Win7PE

it was zipped, hence why I gave up and pasted it in

Have managed to get a working build by pressing play button on each script in turn and it works okay, but if I press play button on start page, it just stops without seemingly doing anything

Just an addition to Lancelot's post and to explain to less experienced users:
If your 'play button' is the small green triangle, clicking it, starts processing the actual script, and ONLY this script.

In the actual case, the actual script is 'script.project' and in 'script.project' there is (depending on the project) either nothing to be done, or just some small things like defining exit code etc.

But the currently known script.project-s never will process the complete project (that would demand a 'Run' for all scripts beeing included).

Now: See Lancelot's post

Peter



#65828 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 24 April 2009 - 11:37 AM in Win7PE

When you post the version can you make sure that no scripts have a version line like:

Version=

That causes download errors with winbuilder.

Not any more!

Fixed in 077 beta 2 :)

Peter



#65570 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 22 April 2009 - 10:44 AM in Win7PE

I think it does not have drivers for vmware eternet controller. It does'nt installs.

LiveXP contains a VMWare ethernet driver

Peter



#65527 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 21 April 2009 - 10:10 PM in Win7PE

Hi,

It builds without errors (wb 077b1), but after booting there is no penetcfg. Manually runing of it displays error that there is no netcfg ora factory.exe fount...

Maybe someone can customize Holger's penetwork for vistape?

Regards, voyteckst

Can you please post the (zipped) log?

Peter



#65377 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 20 April 2009 - 05:50 PM in Win7PE

That happens if in updates.ini instead of an integer value for version or length there is an empty value.

Next beta will be more fault lolerant in this case and just assume the empty value to be null.

Peter



#65834 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 24 April 2009 - 12:47 PM in Win7PE

Is winbuilder 77 / beta 2 available? I must have missed the post.

You did not miss!

I spoke about what I'm preparing to publish next days.

Peter



#66086 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 27 April 2009 - 12:03 PM in Win7PE

with winbuilder 077beta2 cannot even download a project as keep getting "list index out of bounds(0)"

I just downloaded the complete project with beta 2 w/o any error.

Peter



#66112 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 27 April 2009 - 05:20 PM in Win7PE

Build environment is Vista SP1, AIK is installed - all setup same as when I succesfully build VistaPE - AIK is v1.1

Have been through and corrected invalid locations (K:, L: etc), and checked project.ini

...

Can you try EXACTLY what I wrote in post #169 (Of course, defining your paths) (And also of course, using a fresh generated direcory as %BaseDir%)

BTW: One suggestion: Your posts are much better readable if you do not have logs inside. You can attach a log as .zip :)


Peter



#66110 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 27 April 2009 - 05:15 PM in Win7PE

Build environment: Win7 build 7100, WinBuilder 077 beta 1/2.

Error: RegHiveLoad - Failed to load registry hive: [WB-software] From file: [%TargetSys32%\config\software]

Sorry, voyteckst.

I'll stop to try to help you.

To solve an issue, we have to go 'step by step' not 'jump by jump'

There has been a post of you about download troubles.
And I asked some questions.

Instead of giving any answer, you mention new troubles.

But appearently the first trobles are are gone.
If they would still exist, it would not be possible to start the project and get the new troubles.

After you have read the board rules, and react accordingly, maybe I continue trying to help.

Peter



#66092 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 27 April 2009 - 12:40 PM in Win7PE

With WinBuilder 077 beta 2 (%BaseDir% path with space, not on C: "V:\WB\wb debug". I do not believe the C:\NoSpace suggestions)

Complete Download

Defined source CD: V:\BCD\cds\W7_32_EN
Defined WAIK: C:\Programme\Windows AIK (would be nice to have the WinBuilder variable %ProgramFilesDir% as default path to WAIK)

Built the project

Run into VMWare:
w7pe.gif

@yahoouk:
:) :) :) :)

Peter

BTW: Some smaller adaptions still have to be done.

E.g. Do you see the 'VistaPE' in my screen shoot.



#66087 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 27 April 2009 - 12:07 PM in Win7PE

I also cannot download with wb077 beta2 (it states that I shoult have internet connection...).

Are you behind a proxy?

If yes: Are the proxy access data defined correctly?

If they are defined correctly, maybe that your proxy / firewall disallows access to wwww.google.com.
Then you can define a different 'allways available' host to check for internet connection.

Peter



#66272 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 28 April 2009 - 05:01 PM in Win7PE

I feel very sorry about yesterday misunderstanding each other.
You are right. Finding a bug and killing is the heart of good programmer. So I shouldn't say my last two sentenses which was very strong upon you. I'm thinking the whole night, and feeling not well. Sorry guru for my agression.

No problem for me with you!
I think that it is allowed to show emotions.

Peter :)



#66276 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 28 April 2009 - 05:48 PM in Win7PE

I had a story to tell you. Three men was separately travelling on a mountain. They were run out of water and felt very thirsty but no where to find a water. First one luckily found out a water pot under a banyan tree. He went straight there and drank the water and left the journey. After he left, second man saw the pot and he drank the water and prayed for whom filled the water in. And then he left for the journey. Soon after the last man arrived there. He drank and took the water as much as he could and broke the pot just for fun.

Just curious
Maybe my English is too bad, maybe I do not understand your association:

Who is the third man here:
  • Me (If me, I do not have the feeling, but please tell me by PM, why)
  • You
  • Nuno
  • Jaclaz
  • or ...
Or does it tell us:

If you find some benefits and use them, do not destroy them after!


Peter :)



#66979 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 06 May 2009 - 02:54 PM in Win7PE

I can't seem to get it to build cleanly running with WAIK, on win7 x64.

Since some days I'm trying to bring it to run under host Vista 64.
And since today under W7 RC1 64, too

Result until now: Build is error free, ISO starts, but when starting Win7PE from startup menu, the screen becomes black with a living mouse cursor.
Sorry, currently only a build on a 32 bit host os is possible.

Also, where do I get the project now? I see no zip file that I can just grab like I used to... I have winbuilder 76 but your project does not show up in the list... which sucks.

In the WinBuilder download center, you can download the project from the server "win7pe.winbuilder.net/Projects".
If this server is not in the list, you can manually add it (Then it will remain in your list 'for ever'). Take care on uc / lc letters.

Peter



#66996 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 06 May 2009 - 06:24 PM in Win7PE

with buildings under XP 32 Bit SP3 MUI (english with german language pack activated) and 7' 32Bit german.

Thanks Holger, that is a new point of view which perhaps can can help.
Maybe there is some unknown MUI influence ...

In those configs I'm a noob. Please can you tell me how I can
  • use enu source
  • activate German mui
for my build
(Or is it the installed host OS?)

Peter



#66765 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 03 May 2009 - 05:14 PM in Win7PE

New Test:

Environment:
  • Host XP SP3 German
  • WAIK installed as ' ... _AIK' to avoid 'hardcoded find'
  • Source W7 English Build 7000
Download of fresh Win7PE, defined my individual source CD
Defined my individual path to WAIK
Added my VirtualBox.script
Unselected Shell > Add node
Unselected Shell > explorer
In Shell > qDir, selected "Set as default shell in PE Shell"
Unselected VirtualTest > VMWare
Selected VirtualTest > VirtualBox

Test #1 (ImageX active)
Run
Result: :D

Test #2:
Undefined path to WAIK (WimUtils active)
Run
Result: :D

Combined result:

Both possible builds, with and w/o WAIK bring IN A MINIMUM CONFIGURATION a bootabel and well running PE.
@YahooUK: ;)

BTW: Test #3: Test #1 under a 64 bit OS host: (bulls***), not an primary issue of the project, ...... I'm working on that.

Peter



#66709 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 02 May 2009 - 04:55 PM in Win7PE

Great,


I thought possibly an oversight and was just trying to help as this would be a repedative issue with newcomers if its left as is.
BTW: the download does appears to work correctly now.

Sonny

:D

Peter



#66706 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 02 May 2009 - 04:20 PM in Win7PE

I meant attach of devcon.exe, not the download command.

IMO commenting out the command is either just a minor failure of YahooUK, or there are some troubles with the URL and he decided not to activate yet.

Imagine: The whole project is in the middle of development.

Peter



#66997 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 06 May 2009 - 06:32 PM in Win7PE

Building with english iso files works fine for me. :D
(7100.0.090421-1700_x86fre_client_en-us_retail_ultimate-grc1culfrer_en_dvd.iso)

Does that mean:
You build a host os using this source.
And inside this host WinBulder builds a bootable PE using same (or other W7) souce CD?

Peter



#67001 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 06 May 2009 - 07:06 PM in Win7PE

@Joshua, @Holger:

Thanks for your input.

I have to coordinate the facts and to try to find the root.

But not today. Late enough. Give me one (Mediterrenean) hour ...

Peter :D



#67704 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 16 May 2009 - 11:09 AM in Win7PE

Easier to only omit the title [DelUnneeded] and replace in [lanpack] all the DirDelete lines.

To only copy the %DistLang% would be possible, but that would demand that you split the

##To copy all dir from Boot.wim\windows to target Dir

DirCopy,&#34;%BootSRC%\Windows\*.*&#34;,&#34;%TargetDir%\Windows\&#34;
This command already copies all the different languages.

BTW: The final best way would be to copy only what is needed, rather than to copy all and then delete unneeded things.
That saves a lot of building time.

Peter



#67700 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 16 May 2009 - 10:34 AM in Win7PE

The following code in 1-files.script deletes all languages besides en-US and %DisplayLang%
&#91;DelUnneeded&#93;

Set,%tst%,ar-SA#$ccs-CZ#$cda-DK#$cde-DE#$cel-GR#$ces-ES#$cbg-BG#$cet-EE#$cfi-FI#$cfr-FR#$che-IL#$chr-HR#$chu-HU

#$cit-IT#$cja-JP#$cko-KR#$clt-LT#$clv-LV#$cnb-NO#$cnl-NL#$cpl-PL#$cpt-BR#$cpt-PT#$cro-RO#$cru-RU#$csk-SK#$csl-SI

#$csr-Latn-CS#$csv-SE#$cth-TH#$ctr-TR#$cuk-UA#$czh-CN#$czh-HK#$czh-TW

StrFormat,SPLIT,%tst%,#$c,0,%num%

Loop,%ScriptFile%,TheLoop,1,%num%,%tst%,%DisplayLang%



&#91;TheLoop&#93;

StrFormat,SPLIT,#1,#$c,#c,%actLang%

Set,%cand%,%TargetDir%\windows\System32\%ActLang%

If,EXISTDIR,%Cand%,If,Not,%ActLang%,Equal,#2,If,Not,%ActLang%,Equal,en-US,DirDelete,%Cand%
It can replace the Dirdelete lines in [LanPack]

In addition the line
&#91;FileCopyStandard&#93;

...

//If,&#34;%DistLang%&#34;,NotEqual,&#34;en-US&#34;,run,%ScriptFile%,LanPackUS
must be commented. That would delete the previously reserved language.

Peter



#67674 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 15 May 2009 - 07:20 PM in Win7PE

What helped, was the opposite from what you suggested:

Uncomment all lines besides
DirDelete,&#34;%TargetDir%\windows\System32\de-DE&#34;
Now for the first time I can see my German Win7PE built with WinBuilder 077 beta 3!

Maybe we have to find a mechanism which depending on the source CD does the right "DirDelete-s"

Peter



#67660 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 15 May 2009 - 05:11 PM in Win7PE

Looks like the project has an issue with non-English source CDs.

Please have a look here.

Peter



#66704 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 02 May 2009 - 04:10 PM in Win7PE

Failed at devcon download (its commented out)

I have had the same issue on my (rather empty) 64 bit system.
devcon is not provided by standard OS.

But it is used in the project and you have to download (or have it already).

To include it in the script would be a bit outside legality.

Peter



#66702 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 02 May 2009 - 03:58 PM in Win7PE

use winbuilder077b2 to download, than use winbuilder076 to build :D

Why change?
I use 077b2 for the build (as I reported above) and it boots fine.

Peter



#66411 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 29 April 2009 - 07:08 PM in Win7PE

If,%Wow64%,EQUAL,False,Begin

Sorry: exchange the line
If,%Wow64%,EQUAL,False,Begin
to
If,%Wow64%,EQUAL,True,Begin

The 'False' has been for my test, because I'm working under 32 bit
(I already changed in my original post)

Peter



#66408 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 29 April 2009 - 06:48 PM in Win7PE

@ALL

It think that there is a remarkable difference between building on a 32 bit host os or on 64 bit.

Please if you report issues:

Also tell us your host OS.

Thanks

Peter



#66406 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 29 April 2009 - 06:35 PM in Win7PE

After building the project successful under XP SP3 32bit host, I made a new test:

Copied the COMPLETE WinBuilder directory to a Vista 64bit host.

I built the project, and got the same result Brian Hoover reported some posts ago.

A compare of the generated ISO showed, that under the 64 bit host the boot.wim was remarkable smaller that one from the 32 bit host.

My opinion:

This seems to be an issue of 'Building a WinBuilder project under 64 bit host'
Here are the same mechanisms active, which Lancelot successful fixed in LiveXP.

To make his fixes possible, WinBuilder already offers some help to work with 'Running WinBuilder in a 64 bit host environment'
  • The Variables
    • %Wow64%
    • %Wow64Dir%
    • %Programs64%
  • The commands
    • System,REGREDIRECT
    • System,FILEREDIRECT
The currently only open issue is that under Wow64 the %ProgramFiles% MUST be written in lowercase as %programfiles%
That cannot be handled by WinBuilder, but has to be defined in the individual scripts using this Variable.

I'm sure that with help of these explanations in some days also the Win7PE can be build on 64 bit hosts.

@YahooUK:
To avoid disappointment and support questins, before these fixes are active:

Just add under [process] in script.project:
If,%Wow64%,EQUAL,True,Begin
Set,%Msg%,"Sorry, this project cannot (yet) be built under 64 bit host"
Halt,%msg%
End

Peter

EDIT: Sorry: exchanged the line
If,%Wow64%,EQUAL,False,Begin
to
If,%Wow64%,EQUAL,True,Begin

The 'False' has been for my test, because I'm working under 32 bit



#66384 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 29 April 2009 - 02:59 PM in Win7PE

Ok, let me post an update on my "black screen" issue and offer up a question.

I am now using a new computer running Windows XP SP3. I am using Winbuilder 074, 076, and 077 beta 2. I have updated my source to Windows 7 builder 7100 32-bit Ultimate. I also have WAIK 3.0 beta installed.

The project builds fine, takes about 12 minutes and is 198MB ISO. Whenever I try to use this ISO either in VMWare, on a physical computer booting via DVD or USB I get a black screen with a mouse cursor after it boots to Win7.

First, is anyone building this project on XP with WAIK 3.0?

Second, should I build with WAIK 2.0 instead?

Third, should I be running Winbuilder on Vista or Window 7?

Last, is there any other suggestions to what is going on?

Thank you.

1st: Not me
2nd: I built successful with WAIK 2.0 under XP SP3 (but my source is 7000, not 7100)
3rd: better is to stay with XP

Peter



#66434 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 29 April 2009 - 09:03 PM in Win7PE

Thanks, Paraglider.

That proofs my opinion that we have to examine script by script whether they do something 'bad' when running under 64 bit host.

Peter



#66482 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 30 April 2009 - 01:52 PM in Win7PE

During my 64-bit tests I found a bug in '3-explorer.script':
The attached UserDefault.reg causes a permanent entry in the host's registry.
userdefaultregbug.gif
Maybe the above mentioned 'disappearing of the network environment' is caused by a similar bug in a different script.

Peter



#66671 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 02 May 2009 - 11:18 AM in Win7PE

Positive,

Because of the Filesharing script I have reinstalled clean several times in the last week.

Contents of "C:\Documents and Settings\Sonny\Local Settings\Temp"
WCESLog.log
WCESCOMM.LOG
WcesView.log

Contents of "C:\WINDOWS\Temp"
Perflib_Perfdata_3d8.dat
Perflib_Perfdata_7f4.dat
Perflib_Perfdata_78c.dat
Perflib_Perfdata_230.dat
Perflib_Perfdata_738.dat
Perflib_Perfdata_ce4.dat

All other temp dir's are empty ie:
"C:\Documents and Settings\Default User\Local Settings\Temp"

Sonny

SORRY!

My fault. I meant the Tools directory, not the Temp. :D

Peter



#66664 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 02 May 2009 - 08:33 AM in Win7PE

The wiak may be an issue. I use XP sp3 with no wiak installed.
You only need this installed if it is the source.

Are you sure that you have logically no WAIK installed?

Have a look into the temp directory.

If there are the files imagex.exe, wimfltr.sys, wimfltr.inf, wimgapi.dll, you have the WAIK 'logically installed'.

Peter



#66531 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 30 April 2009 - 08:47 PM in Win7PE

Warning!!!!!!!
Please do not use file share script.
It will totally damage your xp machine in a next boot.
In that script, 2.reg is absolutely missed out \WB-...\ in \WB-SOFTWARE\.

Suggestion:
Pin this as separate 'Warning' topic in this subforum!
(when it is no longer actual, cou can delete the topic)

Peter :D



#66514 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 30 April 2009 - 07:00 PM in Win7PE

I work at a University and so the blowing up of computers is not the SOP way of getting rid of them :-)

I have a couple OC3 lines at my disposal for uploading so I should be good. Where would I upload the files to for your browsing pleasure?

Brian

For those special purposes we have the domain 'shared.boot-land.net' and I'll PM you the access data.

Peter



#65370 Win7PE with Winbuilder 74 & 76

Posted by pscEx on 20 April 2009 - 04:53 PM in Win7PE

@YahooUK:

As one test before delivering the new 077 beta 2, I built your project.

Result: This has been my first Vista-World project which created a running PE with 'factory settings'. I just had to define source DVD and WAIK install path.
In the past with other projects I have had usually troubles. Maybe you remember my post 'Vista for Dummies'
:)

But please be not too proud! there are some smaller complains.

Biggest one is that you use a very old VirtualBox script. It only works with versions before 1.6.0.

Attached a script which also works with current versions up to 2.2.0 (Please do not use 2.2.0, use 2.1.?; I wrote a warning anywhere in the forum)

Some smaller:
  • Comment lines should have two hash chars rather than one. Since a while we are trying to define comment as // or ##.
  • The System,RefreshVars command is obsolete and does not do anything. You should remove it.
  • Some Echo commands with spaces in the message should include the message in quotes.
Continue your good way!

Peter

Attached File  VirtualBox.script   35.56KB   20 downloads