Sign in to follow this  
Followers 0
Siginet

Windows XP PowerPacker v1.0 RC8 Beta3

46 posts in this topic

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

Edited by Siginet
0

Share this post


Link to post
Share on other sites

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

-- Super-Magician :)

0

Share this post


Link to post
Share on other sites

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.

Edited by Super-Magician
0

Share this post


Link to post
Share on other sites
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!

0

Share this post


Link to post
Share on other sites

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

UWXP_ROOT

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?

0

Share this post


Link to post
Share on other sites

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?

0

Share this post


Link to post
Share on other sites

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. :blushing: I will also place a clean powpack.ini in there as well... that was an accident.

0

Share this post


Link to post
Share on other sites

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. :thumbup

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

0

Share this post


Link to post
Share on other sites

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.

0

Share this post


Link to post
Share on other sites

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 :).

0

Share this post


Link to post
Share on other sites
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.

I should have clarified that I meant my setup wasn't broke... so i don't want to fix it yet... :P

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. :yes:

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

0

Share this post


Link to post
Share on other sites

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.

[InputOutput]
XPSource=K:\XPHR
XPDestination=H:\LOOT\OUTP

[Exclusions]
WIN9XUPG=Y
LANG=Y

[Extra Files]
ExtraPack=N
ExtraPackDest=
ExtraRoot=N
ExtraRootDest=G:\BACKUP_D\PowerPack_Files\PowPack CD Files Pro

[Custom Options]
Tri-Pack=Y
PackNameOn=N
PackName=XMPC

[Unattended]
Unattend=X
Winnt.sif=K:\XPHR
$OEM$=

[DriverPacks]
DriverPack=P
DPSource=H:\LOOT\UWXPCD_ROOT

[WinXPVersion]
XPVersion=H

[WinXPEdition]
XPEdition=R

[Win2k3Version]
2k3Version=

post-39095-1144856087_thumb.png

0

Share this post


Link to post
Share on other sites

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.

Edited by Siginet
0

Share this post


Link to post
Share on other sites

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!

0

Share this post


Link to post
Share on other sites
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.

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now
Sign in to follow this  
Followers 0

  • Recently Browsing   0 members

    No registered users viewing this page.