[Beta Release] Windows XP PowerPacker v1.0 RC8

[Siginet]

http://siginetsoftware.com/images/softpedia_clean_award_f.gif
Download: Windows XP PowerPacker v1.0 RC8 (http://fileforum.betanews.com/detail/Windows_XP_PowerPacker/1120750090/1)

Ok folks...

Changelog:
RC8 Final:
1. Fixed a bug where the IDENT files were not created in the unattended pack of the Tri-Pack option.
2. Fixed other small bugs.
3. ReCompiled the old help file into the program so people can at least learn the basics until I get time to create a new help file. This help file is outdated and there have been some major changes since this help file was created... but it should help give you an understanding of what to do.
Beta5:
1. Added new option in Advanced tab for allowing multiple winnt.sif files. Very cool new feature! Just select a 4 character name, a winnt.sif file and something to add to the boot screen. (PowerPacker auto recognises the type of OS you are using.)
2. Custom pack name option now allows you to add an entry into the boot screen.
3. Fixed bug where the tmp folder was left behind when using the DriverPacks. Now the driverpacks settings file is copied to the %temp% directory and deleted after it is finished.
Beta4:
1. Added support for the new DriverPacks Base.

*Note... in order for the DP to work you must first install the new DP_Base.exe and create a mysettings.ini file through the DP Base. Once you have made your settings file you just select that settings file in the DP section of PowerPacker.

Also a major change you will quickly notice is the new "Advanced" tab. A new advanced feature is the "Run file upon completion" area. This feature is allready built into the RVMIntegrator and now is available in PowerPacker as well. It is very usefult to chain link multiple packaging processes of powerpacker together... or even chain linking powerpacker and the RVMIntegrator together. :) It is made to help simplify the unattended disc creation. Once you have all of your settings files made for all of the programs... you just start the process and the rest is unattended. :)

There will be more "Advanced" features added... but this new beta should hold you guys/gals for a bit before Beta5.

Please report any bugs you may find.

Download and Rate Windows XP PowerPacker @ BetaNews.com (http://fileforum.betanews.com/detail/Windows_XP_PowerPacker/1120750090/1)

Enjoy!

Here is how to use the DriverPacks:

Download the DP Base.
http://driverpacks.net/DriverPacks/

Install the DriverPack Base. Then run DP_BASE.exe.
Choose all of your settings then choose to "Export Settings".

This will create a mysettings.ini file in the same directory as the DP_Base.exe file.

Use that mysettings.ini in powerpacker.

http://siginetsoftware.com/images/Beta-MainWindow.gif

[mdriessen]

Where can i find DP_Base.exe and the mysettings.ini

[Siginet]

Download the DP Base.
http://driverpacks.net/DriverPacks/

Install the DriverPack Base. Then run DP_BASE.exe.
Choose all of your settings then choose to "Export Settings".

This will create a mysettings.ini file in the same directory as the DP_Base.exe file.

Use that mysettings.ini in powerpacker.

[T D]

Good work Siginet!!!
One question, is it possible to add server 2003 support if it isn't there?

PS Why one forum @ msfn and one here?

[Siginet]

The forum at msfn was what I had to begin with. But as you can see... the forum at msfn is pretty buried. Plus I decided to have an entire forum to talk about all of my programs. ;)

As for 2003 support... it is supported... but not really. It's kind of an easter egg in the program. ;)

Basically if you look in the powpack.ini file and add this:
[Win2k3Version]
2k3Version=S

it will put it in 2k3 mode.

[Win2k3Version]
2k3Version=
should allready be in the file.

All of the options will still say XP ... but it will do the proper edits for 2k3.

I plan on making a version of powerpacker that will work for 2k3, xp, x64 editions, and 2k. But I have been working on the integrator a lot latley.

[Siginet]

Beta5 is now available! :D

[ricktendo64]

I gotta give this a try with DPs Base 6.07 RC6, Siginets DriverGrabber and Integrator.
Great Website and Tools Siginet, Its a OneStopShop :D
B-4 I used nLite to make unatended but now Ill try using this.

[vcc]

I wish it were available publicly. I hear it works great.

[madaya]

Is there any manual or Tutorial ffor this.

[Siginet]

Not yet. Sorry. But I will be putting one together soon.

[Siginet]

Just released 1.0 RC8 Final. :D It has the old manual put back into it.

[relder]

Will there be a release soon to accomodate the x64 versions of Windows (ie. XP Pro x64, 2003 x64, 2003 R2 x64...)? I would be very interested.

[relder]

Please disregard my posting as I just noticed that the answer was already given... Sorry about that.

[Slash]

Issue

using PowerPacker 1.0 RC8
DriverPacks BASE 6.10

I selected "Extra root source"
and used my WPI folder as the source. (m:\wpi)

I got a copy of WPI with its subfolders in my root (what i expected)
I also found a copy of all of the sub folders of WPI in my root

I would have expected one or the other not both?

I would like to see what i expected to see in future releases.

Thanks and nice work.

question

will you be supporting RVM_Integrator_1.4.2 or should this be run on the source first (or from advanced tab as a run upon completion.)

nice work Siginet,
Ryan and Bashrat too

[Siginet]

I wrote the RVM_Integrator program. ;) So ... yest it supports it. It's as easy as using the integrator and having powerpacker called within the advanced options. Then vice versa with powerpacker calling the integrator.

I will look into the ExtraRootFiles question. But if you point to your WPI Dir as your root files then all of the files and folders within that WPI dir are copied to the root... not just the wpi dir.

I will however be putting in support for the wpi dir so that if powerpacker finds a wpi dir in it's source it will copy it to the root of the disk automatically and not keep it in the pack.

[Slash]

thank you for answering my question. I wasnt sure the proper order. apparently there isnt one, either one first works fine. Got it.

I don't keep my WPI in my source directory because then i have to move it or copy it to edit it, and I edit it quite a bit. Usually I copy it right before I make my iso. My WPI is pretty hefty at 1.4 gig, so I'm really looking to avoid haveing several copies on my HDD. or DVD.
I think it would be nice if I could point to my source WPI folder (m:\WPI)
and have it copied to the root folder of the DVD when the ISO is created.

I may be missing an easy way to do this with existing tools.

thanks for the speedy response.

[Siginet]

Place your WPI folder inside another folder like M:\MyRoot\WPI

Then point your ExtraRootFiles to M:\MyRoot

anything in the MyRoot dir is then copied to the root of your disk. ;)

[Slash]

if i put my WPI folder inside a subfolder then i must move it to the root of the drive to edit it then back to the subfolder to copy it . that is the two steps i was trying to avoid.

Thanks for your help!

[Z.C.]

if i put my WPI folder inside a subfolder then i must move it to the root of the drive to edit it then back to the subfolder to copy it . that is the two steps i was trying to avoid.

Thanks for your help!

There is a little used legacy command in XP that can be used here:
SUBST

Put the WPI folder in the subdirectory (M:\MyRoot\WPI)
Use SUBST to make the parent directory seem like a separate drive letter

SUBST N: M:\MyRoot where N: is an available drive letter on your system.
Do your WPI edits using the substituted drive letter ( N: ).
When done, delete the mapping:

SUBST N: /D

Hope this helps

ZC

[Siginet]

Very cool trick Z.C. ;) Thanks!

[Slash]

if i put my WPI folder inside a subfolder then i must move it to the root of the drive to edit it then back to the subfolder to copy it . that is the two steps i was trying to avoid.

Thanks for your help!

There is a little used legacy command in XP that can be used here:
SUBST

Put the WPI folder in the subdirectory (M:\MyRoot\WPI)
Use SUBST to make the parent directory seem like a separate drive letter

SUBST N: M:\MyRoot where N: is an available drive letter on your system.
Do your WPI edits using the substituted drive letter ( N: ).
When done, delete the mapping:

SUBST N: /D

Hope this helps

ZC

I havent used SUBST in ten years - Great idea - thanks now all i have to do is find a drive letter im not using. :wink: