122 replies to this topic

[allanf]

@wimb

I Enjoy your pe21 Otherwise I can Add an Extra Button in USB_XP_Setup.exe and use Format followed by BootSect.exe /nt52

.
... ...

BTW the Format Buttons in A43 and FreeCommander do not work at the moment.
And in DriveManager the Explore Button is NOT working.
Most likely this is due to a missing Vista Explorer.
Would it be simple to add the functionality of Vista Explorer and Format to your Project Or are we crossing here the FREE border ?

I was surprised how simple it looks when using 'LiVissta Rescup' and nanoVIS, and "The VistaPE scripts in WinBuilder make adding Explorer a piece ofcake". However, both require access to the install.wim from a Vista Installation DVD, which many people avoided. For the developers of those projects, I don't think it was as easy as it might appear to a user.

Quite a number of otherwise excellent Programs make the presumption that Windows' explorer.exe is always available. I have tried to investigate ways to somehow link the explorer buttons and functions found in some Programs to alternative file managers, but have not found an easy solution.

Also, some good alternative shells unfortunately provide by default, a means to switch back to explorer. A nice feature except when the OS happens to be Windows PE!

I will also try to Add the U_XP_SET package to the Project in a simalar way as used for adding the mkimg Tools.
Do you think this can be done this way ?

I was also looking at this. ... ...

The script lines for creating shortcuts are long and difficult to read because of the number of parameters that can be used.

In a nutshell... For GUI Programs, the script line adds a line to startnet.cmd to call a .cmd which locates the Program's .exe then passes the path and other parameters to a vb script that creates the shortcut. For cmd-line Tools, it's similar, except the called .cmd has the parameters slightly rearranged so that the .exe is cmd.exe and the parameters passed to the vb script are the path to the tool and cmd-line switches.

I look forward to the addition of your package. Having just had a brief encounter with Win7beta, I would say that XP is still here to stay!

Regards

[Filip Hasa]

hi allanf,

about jkDefrag, may be you missed it but here is GUI for jkdefrag (for amd64 as well ;o)

I got idea how to trick pkgmgr. Why: pkgmgr recognize type OS and add what is for this type OS.

example: MSU package with Windows Installer has msi.dll and msiexec.exe for Vista SP1 but not for WinPE 2.1

Idea: how about to move all files from vista SP1 image and insert files from WinPE?!

I must try it ;o)

[wimb]

I look forward to the addition of your package.

Great

Adding U_XP_SET package can be relatively simple,
since Creating a Shortcut to PStart.exe is already sufficient.
All tools of U_XP_SET are portable and are launched from PStart Menu.

In the mean time I am making a FORMAT Button in USB_XP_Setup.exe to allow Format with NTLDR-type BootSector of XP.

Thanks for your help

[allanf]

I got idea how to trick pkgmgr. Why: pkgmgr recognize type OS and add what is for this type OS.

example: MSU package with Windows Installer has msi.dll and msiexec.exe for Vista SP1 but not for WinPE 2.1

Idea: how about to move all files from vista SP1 image and insert files from WinPE?!

Ahh! That's the answer! pkgmgr is quite clever.

The Vista SP1 image - Is it an image from boot.wim or from install.wim? Or either?

But really, this is a simple project whose only source is the WAIK. How is your new project going? ... ...

I'll look at jkDefrag_portable.

Thanks

[Filip Hasa]

The Vista SP1 image - Is it an image from boot.wim or from install.wim? Or either?

i will try all one ;o)

But really, this is a simple project whose only source is the WAIK.

I know but if i can do it like this complicate way. THAN I can say which files and registry you need ;o)

How is your new project going? ... ...

I am waiting on NightMan because he is finishing new version of VistaPE. Propably I will test amd64 version and compilation for amd64 source. It is a little bit pity new version is not pure winbuilder scripts ;o(

I spend time to find how to run MSI and "Microsoft Visual C++ 2008" on amd64 ;o) Tip with msiexec /regserver doesn't work ;o(

[allanf]

All tools of U_XP_SET are portable and are launched from PStart Menu.

@wimb,

OK. Looks easy. ... ...

Here is a script which works for the download, extraction and shortcut creation with your icon. It looks good. I haven't tested the programs yet.

I modified the download link from:
http://wimb.winbuild...ad=U_XP_SET.exe
to:
http://wimb.winbuild...ds/U_XP_SET.exe
because it seems more straight-forward. I hope it doesn't matter.

Add the script to script.project (opened with a text editor, such as notepad), adding a single line to the [Apps] Section, and the new [U_XP] Section.

As a txt file due to the length of lines.



@Filip

OK I understand now. Thanks for the testing. I was thinking that the Servicing folder in the Vista or WinPE image communicates with pkgmgr and determines what can or cannot be installed. ... ... maybe other things as well?


Regards

[wimb]

@allanf
Thanks for making U_XP_SET.txt which I can Add to your script.project

The change of the download link for U_XP_SET.exe is OK.

I will test the modified script.project and let you know.

Thanks for your help

wimb

[wimb]

@allanf

Have tested script.project modified for U_XP_SET.exe Support.

Making and Booting with the ISO is fine.
Nice to have PStart direct available in your Windows PE 2 with GUI Environment.

Running of the Programs of U_XP_SET like BOOT_IMG is fine,
but as expected first one has to Add setupldr.bin of Windows Server 2003 SP1
which file I am NOT allowed to put in the package.

ERROR - Missing Server 2003 SP1 File setupldr.bin

File \makebt\srsp1\setupldr.bin NOT Found



Solution: 

Copy File <Winbuilder>\Workbench\Common\BootSDI\setupldr.bin

As File USB_XP_Setup\makebt\srsp1\setupldr.bin

But otherwise everything works OK.

For Make_USB.exe - BOOT_ISO.exe and USB_XP_Setup.exe there is no problem, but for Install of LiveXP Boot Option we need first to Add setupldr.bin to the U_XP_SET folder as discussed above.

The problem can simply be avoided by changing the focus to Windows PE 2.1 - ISO as favourite PE Boot Option.

In USB_XP_Setup.exe I will make FORMAT Button (coming soon ...),which allows to format Install Drive with NTLDR-type BootSector of XP.

And then we can use your Windows PE 2.1 ISO with GUI as the most general PE which allows to Install XP - Vista or Windows 7 from USB-stick.

[allanf]

... a delta. Actually should be alpha 1, alpha 2, alpha 3, etc. because not everything has been tested. Anyway, 'delta' it is! What's next? gamma or epsilon?

Added to the Program Selection Menu:
wimb's U_XP_SET Install from USB
Holger's PENetwork GUI Configuration
lee's ViSplore Amazing Explorer (Thanks to Medevil)
Don Ho's Notepad++ Source Editor (with Context Menu, total notepad.exe Replacement, and Explorer and Hex Editor extra Plugins)
Thomas Kolb's jkDefragStarter GUI. (@Filip - x86 and x64 - No more PA.com! ... ...)

Enabled BGInfo and damian666's Random Wallpaper in the xoblite and bbLean Shells

Slightly modified bbLean's menu

Moved a lot of Registry Settings from Build-time to Boot-time

The Selected File-Manager and Web-Browser are automatically added to emergeDesktop's Launcher

And a few other things ... ...


New Users. Install WAIK 1.1 (release for Vista SP1). Download the following .zip, and extract it to a path without spaces. Double-click Winbuilder.exe and Press 'PLAY'! ... ...

http://pe2.winbuilde...d/pe21.003d.zip

Old Users. Use Winbuilder's Download Center - pe2.winbuilder.net

EDIT: Forgot to mention that emergeDesktop Development Shell was added for x86 and x64 PEs.

Regards

[allanf]

... small correction (with a big impact) to script.project to allow installation of drivers from the nominated folder.

Regards

[wimb]

@allanf

Very nice

Thanks for all the improvements.

Very handy to Boot so FAST in about 25 sec with this pe21.iso loaded from Harddisk into RAMDISK and have all important System Management Programs available.

Regards,

wimb

[allanf]

@allanf

Very nice

Thank you, wimb.

I still haven't tested your Program. I don't really have the infrastructure

What I would like to try though is to do the whole set up from WinPE.

1. Boot WinPE with USB device inserted and XP source in I386 folder on HDD.

2. Format the USB device, and copy the XP Source to it as required.

3. Create a test Partition on the HDD.

4. Setup XP on the test Partition and make it bootable.

I think your Program can do all (or most) of that.

BTW, that bonus System Info app in U_XP_SET is a great tool too.

Regards .

[wimb]

Everything you have in mind can be done with U_XP_SET
except point 3. Create a test Partition on the HDD.
Also for Install of XP it is necessary to Set Active this Test Partition. The Test Partition must be a Primary Partition and NOT a Logical drive of the Extended Partition.

For that purpose you might make use of DISKPART
or Create the Test Partition previously by using Acronis Disk Director After Booting with LiveXP BootSDI.img made with one of the Stable Projects of amalux e.g. lx76hfcxaf or lx101408cxs
http://amalux.winbuilder.net/

In general for testing purposes I make first a Ghost image of the partition meant for Install of XP and Backup any important Data.
So that After Test Install of XP you can simply return to the original situation by Restore of your Ghost image.

[allanf]

Everything you have in mind can be done with U_XP_SET
except point 3. Create a test Partition on the HDD.
Also for Install of XP it is necessary to Set Active this Test Partition. The Test Partition must be a Primary Partition and NOT a Logical drive of the Extended Partition.

For that purpose you might make use of DISKPART

OK. Thanks ... ...

I have had some experience with WinPE 2.1's diskpart - shrinking volumes and creating new partitions. I'll give U_XP_Set a try, and report back.

In general for testing purposes I make first a Ghost image of the partition meant for Install of XP and Backup any important Data.

Very good advice! ... ...

[Filip Hasa]

hi allanf,

i found commander inspirited by TC: doublecmd.sourceforge.net run on x86, x64 and on linux as well ;o)

[allanf]

hi allanf,

i found commander inspirited by TC: doublecmd.sourceforge.net run on x86, x64 and on linux as well ;o)

Thanks Filip Hasa ... ...

I tried it in the project. It is a very snappy File Manager. Excellent... ...

Maybe, there are some TC plugins that can also be used. Any ideas?


On another subject...

I was looking at

http://www.deployvis...US/Default.aspx

where you found the BGInfo/Autorun plugin. The ADSI plugin illustrates a very nice way to add registry settings using peimg! (Too bad that plugin requires files from full Vista.)

Regards

[Filip Hasa]

Maybe, there are some TC plugins that can also be used. Any ideas?

It a little bit complicate because for x64 you need compile dll under these platform.
but I think I can find more plugins like this

where you found the BGInfo/Autorun plugin. The ADSI plugin illustrates a very nice way to add registry settings using peimg! (Too bad that plugin requires files from full Vista.)

OKey but what is the point?

[allanf]

OKey but what is the point?

Referring to, for example:

peimg /inf:C:\Plugins\ADSI\ADSI.inf c:\mount

... A single line in the script is much, much neater than:

RegHiveLoad ...

RegWrite ....

RegWrite ....

...

[or ... regedit ... ]

RegHiveUnload ...

IMO ... ...

[Filip Hasa]

i see. i think that it standard inf like for inf files for drives.

but it worked strange if you had x64 bit source.

I can try find some info how to create and so on.

Get I clue what do you want?! ;o)

[allanf]

Get I clue what do you want?! ;o)

MSI? ... ...

Or the emergeDesktop settings:


Or File-Type-Association entries:

[RgFleTypeAssoc]

##--- Parameter #1 is the File Extension ---##

Echo,"Adding %ProgramName%.#1 FileType Association"

RegWrite,"HKLM",0x1,"PE2_SOFTWARE\Classes\.#1","","%ProgramName%.#1"

RegWrite,"HKLM",0x1,"PE2_SOFTWARE\Classes\%ProgramName%.#1","","#1 File"

RegWrite,"HKLM",0x1,"PE2_SOFTWARE\Classes\%ProgramName%.#1\shell","",""

RegWrite,"HKLM",0x1,"PE2_SOFTWARE\Classes\%ProgramName%.#1\shell\open","",""

Note that the following entry is added at boot-time to locate the Program in RAM or Media:

"REG#$sAdd#$sHKLM\SOFTWARE\Classes\%ProgramName%.#1\shell\open\command ... etc ...

Just an idea because I thought there was an issue with regedit (and Winbuilder regwrite ... ...) under Vista/Win7's UAC Control. Not sure how peimg goes under UAC.

No idea really ... ...

Regards

[Sirquil]

I am having a problem with DirMove command building this project; as soon as there is a DirMove command the project halts.

Building on Vista Home Preimum SP1 with WAIK 1.1 installed using Winbuilder 076. I have uninstalled AVG 8.5, turned off the firewall --still same result.

Sirquil

[MaineCoon]

I am having a problem with DirMove command

I can confirm this behaviour using Vista Home Premium SP0 with WAIK 1.1 and WB 076.

MaineCoon

 log.7z   8.09KB   649 downloads

[allanf]

I can confirm this behaviour using Vista Home Premium SP0 with WAIK 1.1 and WB 076.

MaineCoon

 log.7z   8.09KB   649 downloads

Thanks for the feedback guys, and the log.

Basically, this is what the script does before the halt in the log:

Copies the SOFTWARE hive (and other files starting with SOFTWAR*) from the mounted image to a temporary directory.
Loads the hive from the temporary directory.
Makes an entry in the loaded hive to run startnet.cmd at startup.
Unloads the hive in the temporary directory.
Moves the amended hive from the temporary directory back to the mounted image, thereby overwriting the original hive with the amended one.

The reason for this procedure is that I had some problems amending a hive that was loaded directly from the mounted image.

There does not seem to be a problem loading, amending and unloading the hive from the temporary directory.

The halt appears to relate only to the movement of the temporary directory and perhaps the overwriting of the original files. I haven't experienced the halt on XP (my XP anyway), but I do recall some dirmove issues posted in the forum when Vista was first released. So, I assume that this is a Vista issue with file overwriting.

I am really not keen on making registry adjustments during build-time, and have taken most registtry settings into the startnet.cmd, so that they are done at boot-time. However, the one vital registry setting that must be made during build-time is the one that starts startnet.cmd setting - the one that has caused the error in the log! I assume that if the script progressed, then he other build-time registry settings would also fail.

Currently investigating the option of performing registry adjustments using the peimg command which is a lot neater. The startnet.cmd setting should be THE prime candidate.

A quick fix might be to filedelete the SOFTWARE* files in %TargetDir%\Windows\System32\config before moving them back. Or, perhaps better, might be to DirMove the entire %TargetDir%\Windows\System32\config directory to %ScriptDir% rather than FileCopy individual files to %ScriptDir%\config - then DirMove it back.

In the meantime, I have just set up a test machine with Win7 beta. So, I'll see how winbuilder goes, and check whether the issue occurs there.

Note that the winbuilder OnError command has not yet been implemented because I was hoping to retain backward compatibility with winbuilder 074. (I think that things have gone beyond that idea already!) This means that the image is still mounted when the script halts. Running the script again will dismount any wayward mounted images in the %TargetDir%, but again if the script halts, there will still be a mounted image. So it needs to be unmounted manually from the 'Start>All Programs>Microsoft Windows AIK>PE Tools Command Prompt' with:

imagex /unmount <Winbuilder Base Directory>\Target\pe21

Sorry 'bout that chiefs ... ...

[Filip Hasa]

Hi allanf,

i found link for this work.

http://msdn.microsof...y/ms790212.aspx - Creating INF Files for Multiple Platforms and Operating Systems
http://msdn.microsof...y/ms790204.aspx - Creating International INF Files
http://msdn.microsof...y/ms790223.aspx - Summary of INF Sections
http://msdn.microsof...y/ms790193.aspx - Summary of INF Directives

http://www.osronline...te-inf_4l47.htm - something like tutorial

and most important i found program for creating inf files - I have to test it.

Do you want go this way?!

[paraglider]

Its a great pity winbuilder does not show the underlying error reported from the win32 api. That way it would be much easier to debug these kind of problems.

Does DirMove,"%ScriptDir%\config","%TargetDir%\Windows\System32" work if %TargetDir%\Windows\System32\config already exists?Could also fail if %ScriptDir%\config contains locked files.