OK... I decided to release a beta of v1.0 RC8.
So here is Beta1.

The beta releases are mainly meant for those of you who are somewhat familuar with previous releases. The help file it contains is old and has not been updated.
There have been many changes to the coding and xp powerpacker is now much faster and it is about half of the size.
XP Powerpacker also has a new progressbar to show you progress.
There are many new changes that I will explain later... but for now I just ask that members try using it and letting me know how well it works for them.

Also the unattended parameters have changed a little bit. I am going to be changing the unattended parameters completley before the final release. The changes so far are simple:

Parameter1 = The path to your settings file.
Parameter2 = The type of unattended process to perform. (Either: -PACK or -PACKAGE)
Parameter3 = The disk lable you wish to add to the iso. (Only to be used with -PACKAGE)
Parameter4 = The path and name for the iso file. (Only to be used with -PACKAGE)

Download Beta3

Thanks for releasing a beta! I'll test it and let you know how it goes...

-- Super-Magician

I'm testing the beta release now. It hangs forever on generating a boot directory (XOPC). I'm attaching my powpack.ini file in case you want to look at it.

Also, the "Browse" button for the Extra Pack Files stays active after you press the "Pack" button.

Edit: Actually, this was my own doing. I deleted the powpack.ini to start over with new settings but something got messed up. There is one remaining problem, however. The Extra Pack Files I selected did not copy over.

Sorry I forgot to mention that a couple of changes were made that makes an old settings file not work correctly. It is best to use a new settings file... or make sure you re-select all of the options. Especially the Extra Pack/Root files sections.

So ... are you still getting an issue with the boot directory creation? Is the progressbar working correctly? Do you think I should make the progressbar a little thicker? I made it thin just to be different... but I'm not sure if it looks ok or not. Coding it to show progress for cdimage.exe was a real pain but it seems to work well so far. There's still a lot of coding to be done before the final release... but I couldn't wait to show off what I've done with it so far.

Thanks for giving me some feedback! I appreciate any feedback. It actually gives me an insentive to code more when people actually show an interest. Seems like ever since I came out with a version that worked very well people didn't give much feedback anymore. Almost makes me want to put bugs in it on purpose! LOL! J/K!

I've so far tried intergrating my xp home cd using the power pack to make a tri-pack, but I get this error with the BTS driver packs, I will try and make the again, I've been using the same one since ages!

A few pointers though:
The progress bar looks good and different.
and a ssuggestion: Maybe, intead of exiting when a parameter is missing, could you make it to just warn the user and that's it?

Also, I think there should be a "Cancel" button somewhere when the program is working. Right now, you can only exit.

When I was talking about the powpack.ini file, I was saying that I deleted the one that automatically popped up when I launched the program, as it had all of your settings in it and I wanted to start fresh. I did not use an old settings file.

I did recheck all of my settings, but as I said, my Extra Pack Files weren't being copied correctly. I think everything else worked though.

The progress bar looks fine. I'd like to see the files completed section again (i.e. 5123/6457) instead of just 85% or something.

Aren't you switching to mkisofs?

Yes in the final cdimage.exe will not be used. But can be used as a plugin. I will look into the Extra Pack error you specified. It wouldn't suprise me if it has a bug. That is basically the only option I did not test. I will also place a clean powpack.ini in there as well... that was an accident.

I would love to try this but i have my batch scripts configured so that i can "integrate" and then "powerpack" a DVD with addon data then an OEM home/pro cd iso and then a retail home/pro cd iso then a Corp Cd iso. I start it when i leave work and burn the finished results when i come in the following day.

The saying goes... "if it ain't broke, don't fix it...!!!!!"

I'm not fixing it. I am moving toward enhancing it. As of now... with this beta the enhancements are mainly just speed and looks. Any changes that I have made are for future stuff that the final release will be capable of. Belive me... I know what you mean about if it aint broke don't fix it. I have a bunch of batch files and ini files that I use between the integrator and powerpacker and my batches are pefect... but with the new changes in the integrator my old batches and ini files are useless. So even I hate the changes so far. But when you see where the changes are going you will appreciate them. The new powerpacker will have a lot more customizable capability. Just trust me. If you like the old powerpacker... you will love the new one when it is complete. I am gearing toward making powerpacker and the integrator to actually work together better than ever. One usefull enhancment so far is that you can save/load your settings files.

Thanks, Siginet.

By the way, I know you said this version is *supposed to be* faster, but when I ran it, it wasn't much speedier.

Another thing - I actually liked the pop-up windows when the PowerPacker was hex-editing the boot files because it was an indication that the program was working effectively. But...that's just me .

I should have clarified that I meant my setup wasn't broke... so i don't want to fix it yet...
I know you want to improve it and i'm sure you will. Actually, my batch script includes deleting a source folder and creating a new blank folder, loading each vanilla OS ISO via Daemon tools command line then copying winntbbu.dl_ for each different OS just after the integrate stage. When powerpacker is initiated the batch also deletes the destination and recreates a blank folder, powerpacks and then copies my version cdshell and splash files and lastly creates the ISO

Can you make integrator and powerpacker do that without batch files...? that would be neat.

I can zip the batch scripts if you like so you can see whats happening...

Hey Siginet, I keep on getting this error, even after using a source that isn't "n-lited". What I'm I doing wrong? here is my settings.ini, just in case.

That seems to be a driverpack issue. Try to use the driverpacks without powerpacker and see if you get the same problem. If you do try to remove any read only attribs from your i386 directory then try again. Powerpacker should be removing the read only attribs though.

BTW try deleting the powpack.ini file. I accidentally implemented the powpack.ini that I use in this beta.

It works now, perfectly, althought the copy process is a lil bit slow. Maybe it's my on PC's side. Otherwise, it works OK. Nice work!

I fixed a few bugs last night... so I should be releaseing another beta soon.

OK, great ! I haven't had time to test the current beta, however.

Any luck on getting ready the next beta, or any thought on when you'll release it?

Thanks .

When next beta is out, I would like to test is too.
For the moment, I'm doing some experiments with ubcd, ubcd4win, bartPE, bcdw etc...
Would be nice to combine them all :-)
btw, I more prefer the cd shell scripts in ubcd. They are easier to maintain.
Have you already done some tests with bartPE? ore someone else?

Sorry guys... I've been kinda busy latley. I think I am ready for beta 2... but I want to run a few more tests. I'll try to get the beta out this weekend. It will be kind of the same as Beta1 but with all of the known bugs fixed. Hopefully I will have some time to add some more stuff to it soon.

Well, thanks for responding, siginet! I'm looking forward to Beta 2. No rush, of course .

I also am looking forward to the release of Beta 2. I have ran into a few issues with the tri-pack, both duing the intall phase (not integration). I would like to see Beta 2 before I rample on just in case they are resolved. But real quick, they both appear during the runonce phase.

So after the first login. The first, just annoying but a missing nlite.inf file (not using nlite, but I am using the RVM_Integrator) and the really annoying is with bashrat's DP. I get a "bad signing logo" on quite a few drivers. I think for of these are due to the tri-pack split. I am still trying a few things, but any ideas?

Either way, cannot wait for Beta 2

That issue would not be caused by powerpacker in any way. I'll try to release beta 2 today.

I uploaded Beta3. Beta2 .... What Beta2?

Cool. If I have some time tonight, I will do some testing.
I also found out that it is not hard at all to add support voor BartPE. Just add the BartPE files to the root of the CD. copy the bootsect.bin file and rename it to PRO1.DAT.
In the cdshell.ini you have to edit some lines too. Since I use a complete other cdshell (the one you find on UBCD) I can't exactly tell what to change. But it should be easy.
Something like:
print " [F1] The Ultimate Boot CD 4 Windows "
if ($lastKey == key[f1]); then chain /PRO1.DAT

Actually in the new beta it should be even easier. All you should have to do is add reference to the setupldr.bin file in the new boot menu ini files. I haven't tested yet... but that's all I think has to be done.

Hey, how do you make setupldr.bin to select which file it's going to use? do you just replace all instances of winnt.sif in setupldr.bin or what kind of "magic" are you employing here ..lol ...lol

btw, I'm currently testing beta 3. will get back and give a report.

Actually you are 100% correct. I replace winnt.sif with the name of the folder like: wXPPC.sif.
Pretty cool trick. It opens many other doors that will be simple to implement to powerpacker. Like the option to use multiple winnt.sif files for the same pack.

BTW... has anyone noticed that the filesize of PowerPacker is about a third of the size of RC7.1.


I confirmed it today. All you have to do is give reference to the setupldr.bin file.

But when PowerPacker has support for PE I want it to be able to add multiple copies of PE on a disk and they share the same Programs folder.

And how exactly do I have to do that?
Now I use the cdchell.ini from ubcd www.ultimatebootcd.com/ and I only had to ad some lines like
if ($lastKey == key[f1]); then chain /XOPC.DAT
Now those xxxx.DAT files are gone.
Do I just have to edit it like:
if ($lastKey == key[f12]); then \XOPC\XOPC.BIN

Now there is a BOOT.ini file that basically you use to point to another ini file or you add reference to the boot file in it.

For instance here is the new BOOT.INI:


You can either point to another INI file like this:


Then in your new BART.INI you would have this:


And I want to customize the [MenuOptions] for PowerPacker as well. I was thinking a green theme for the HOME.ini file and a blue theme for the PRO.ini file.

Thx for the info. But I wanted to use the cdshell.ini
Now I found out how to start one of the powerpacker installations. Just use: bcdw boot \XOPC\ROPC.BIN
I could edit the boot.ini from powerpacker, but that would be more work for me :-)
I'm still trying to combine everything on one CD.
Keep up the good work!

I can confirm that it works :-)
With BartPE included!
Now my only problem is: It is to big for one CD

lol... yeah adding PE doesn't leave much room for programs in PE. Especially on a CD.

I found a bug. For some reason... when you add an XP Home Edition pack... It doesn't copy the IDENT files to the root of the DVD.

But I designed a new way for PowerPacker to get the IDENT files and it works better. So expect this fix to be in the next Beta. (Beta4)

Another thing, Siginet. When I configure the PowerPacker for Extra Pack Files, the files don't get added to the pack dir (e.g. ROOT\ROPC\*).

Again? ****... I will look into it.

I have confirmed the Extra Pack Files bug. I will fix it. ****... I never use it so it allways seems to get messed up somehow.

I am also adding a new "Advanced" tab that will have advanced features in it. I am in the process now of adding an area to Run a file (with parameters) upon completion of packing files. I've said I was going to add this feature for a long time. It will allow chaining of multiple PowerPacker processes together, Utalizing the RVM Integrator (Which has the chaining options too), or any other utility that has unattended parameters.

Edit: Just fixed the Extra Pack Section.

That's great! Thanks...

Can't wait for the next release...

Is the beta3 that is online now the fixed one? I would like to test again this weekend.

No, Siginet never posted a Beta 2. We need to wait for Beta 4.

hello. i think i've found a bug in v1.0 RC8 Beta3


my winnt.sif file is not loaded.

after loadining it in powerpacker and creating the files, if i look in folder %MYUCD%\ROOT\XPPC\I386 the winnt.sif file doesn't includemy specific settings and also %MYUCD%\XPPC\wXPPC.sif doesn't include them

is this behaviour correct?

i tried both in tripac and in simple version but none of them worked

Hmmm... that is odd. None of my tests failed. Can you post your powpack.ini (or settings) file?

here it is

Only conclusion I can come up with is either your winnt.sif file does not exist at D:\winnt.sif ... Or powerpacker does not like it at the root of the drive? Not sure though. If wXPPC.sif exists in your boot directory then that means it should have copied it directly from i386 dir of your destination.

Is there possibly a winnt.sif file in your source i386 dir allready? Maybe WXPPP is not overwriteing it with your winnt.sif in your D:\?

Please run some more tests for me and let me know your conclusions.

ThX

What about PowerPacker to support new DriverPacks 605 CP? Would like to get tripack.

There's an API but it's still in the testing phase (in fact it's just the multiboot support that's in testing phase). It will come very soon, though!

Yes PowerPacker and the integrator will both have support for the new DP Base.

Please bear with me though. I have a pinched nerve in my neck and I have been going to the doctors to hopefully get the pain releived. It makes it difficult for me to be at the computer for long periods of time. This is the biggest reason the new powerpacker is taking so long to code.