Jump to content

Welcome to MSFN Forum
Register now to gain access to all of our features. Once registered and logged in, you will be able to create topics, post replies to existing threads, give reputation to your fellow members, get your own private messenger, post status updates, manage your profile and so much more. This message will be removed once you have signed in.
Login to Account Create an Account



Photo

Windows XP PowerPacker v1.0 RC8 Beta3

- - - - -

  • Please log in to reply
45 replies to this topic

#1
Siginet

Siginet

    Windows XP PowerPacker Creator

  • Member
  • PipPipPipPipPip
  • 739 posts
  • Joined 22-January 05
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, 01 May 2006 - 10:27 PM.

Posted Image
For those of you interested in my next software venture you can check it out here:
www.ITTechware.com



How to remove advertisement from MSFN

#2
Super-Magician

Super-Magician

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 970 posts
  • Joined 15-January 06
Thanks for releasing a beta! I'll test it and let you know how it goes...

-- Super-Magician :)

Posted Image
--------------------
Posted Image


#3
Super-Magician

Super-Magician

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 970 posts
  • Joined 15-January 06
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, 10 April 2006 - 06:54 PM.

Posted Image
--------------------
Posted Image


#4
Siginet

Siginet

    Windows XP PowerPacker Creator

  • Member
  • PipPipPipPipPip
  • 739 posts
  • Joined 22-January 05

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!

Posted Image
For those of you interested in my next software venture you can check it out here:
www.ITTechware.com


#5
hbinded

hbinded

    what? whaat?

  • Member
  • Pip
  • 66 posts
  • Joined 22-December 04
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?

#6
Super-Magician

Super-Magician

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 970 posts
  • Joined 15-January 06
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?

Posted Image
--------------------
Posted Image


#7
Siginet

Siginet

    Windows XP PowerPacker Creator

  • Member
  • PipPipPipPipPip
  • 739 posts
  • Joined 22-January 05
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.

Posted Image
For those of you interested in my next software venture you can check it out here:
www.ITTechware.com


#8
Ghostrider

Ghostrider

    Member

  • Member
  • PipPip
  • 177 posts
  • Joined 29-January 04
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)

#9
Siginet

Siginet

    Windows XP PowerPacker Creator

  • Member
  • PipPipPipPipPip
  • 739 posts
  • Joined 22-January 05
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.

Posted Image
For those of you interested in my next software venture you can check it out here:
www.ITTechware.com


#10
Super-Magician

Super-Magician

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 970 posts
  • Joined 15-January 06
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 :).

Posted Image
--------------------
Posted Image


#11
Ghostrider

Ghostrider

    Member

  • Member
  • PipPip
  • 177 posts
  • Joined 29-January 04

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

#12
hbinded

hbinded

    what? whaat?

  • Member
  • Pip
  • 66 posts
  • Joined 22-December 04
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=

Attached Files



#13
Siginet

Siginet

    Windows XP PowerPacker Creator

  • Member
  • PipPipPipPipPip
  • 739 posts
  • Joined 22-January 05
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, 12 April 2006 - 11:18 AM.

Posted Image
For those of you interested in my next software venture you can check it out here:
www.ITTechware.com


#14
hbinded

hbinded

    what? whaat?

  • Member
  • Pip
  • 66 posts
  • Joined 22-December 04
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!

#15
Siginet

Siginet

    Windows XP PowerPacker Creator

  • Member
  • PipPipPipPipPip
  • 739 posts
  • Joined 22-January 05

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.

Posted Image
For those of you interested in my next software venture you can check it out here:
www.ITTechware.com


#16
Super-Magician

Super-Magician

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 970 posts
  • Joined 15-January 06
OK, great :)! I haven't had time to test the current beta, however.

Posted Image
--------------------
Posted Image


#17
Super-Magician

Super-Magician

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 970 posts
  • Joined 15-January 06
Any luck on getting ready the next beta, or any thought on when you'll release it?

Thanks :).

Posted Image
--------------------
Posted Image


#18
Telenut

Telenut

    Member

  • Member
  • PipPip
  • 147 posts
  • Joined 24-February 05
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?

#19
Siginet

Siginet

    Windows XP PowerPacker Creator

  • Member
  • PipPipPipPipPip
  • 739 posts
  • Joined 22-January 05
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.

Posted Image
For those of you interested in my next software venture you can check it out here:
www.ITTechware.com


#20
Super-Magician

Super-Magician

    Friend of MSFN

  • Member
  • PipPipPipPipPip
  • 970 posts
  • Joined 15-January 06
Well, thanks for responding, siginet! I'm looking forward to Beta 2. No rush, of course ;).

Posted Image
--------------------
Posted Image


#21
choman

choman
  • Member
  • 2 posts
  • Joined 20-December 04
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
Posted Image

#22
Siginet

Siginet

    Windows XP PowerPacker Creator

  • Member
  • PipPipPipPipPip
  • 739 posts
  • Joined 22-January 05

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.

Posted Image
For those of you interested in my next software venture you can check it out here:
www.ITTechware.com


#23
Siginet

Siginet

    Windows XP PowerPacker Creator

  • Member
  • PipPipPipPipPip
  • 739 posts
  • Joined 22-January 05
I uploaded Beta3. Beta2 .... What Beta2?

Posted Image
For those of you interested in my next software venture you can check it out here:
www.ITTechware.com


#24
Telenut

Telenut

    Member

  • Member
  • PipPip
  • 147 posts
  • Joined 24-February 05
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

#25
Siginet

Siginet

    Windows XP PowerPacker Creator

  • Member
  • PipPipPipPipPip
  • 739 posts
  • Joined 22-January 05

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.

Posted Image
For those of you interested in my next software venture you can check it out here:
www.ITTechware.com





0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users