[moesasji]

enuffsaid, on Jul 7 2005, 02:30 PM, said:

Good work Siginet. This sounds like a fantastic tool! Will give it a try.
<{POST_SNAPBACK}>

I second this compliment to Siginet and applaud his plans to continue development and broaden it to a tool that is able to implement a lot of the great MSFN-tricks and techniques.
And as a tip to enuffsaid; I doubt that you will run into problems trying out the PowerPacker 1.0 RC1-program, but if you do, you can rely on great support by Siginet. I have found out for myself that with his support and enthusiasme, any problems occurring with his tool will be solved quickly.

I hope a lot more MSFN-posters and MSFN-readers will give PowerPacker a try and report their results and suggestions in this forum.

[Siginet]

Thanks a lot for the compliments moesasji! I aprreciate it. I hope evryone enjoys the program as much as we do.

[moesasji]

While you are receptive for compliments, I will try a new suggestion too :-)

Could you implement an option in PowerPack to run a batch-file of choice between building the packs and compilin them into an ISO. That way I would be able to automatically apply changes that need to be made (such as adjusting the winnt.sif after Bashrat's method was applied and copying some extra info (specific to one of the packs on the DVD) into the package.
Ofcourse I could run such a batch file myself between packing and building an ISO, but I would like to be able to build the multiboot DVD completely withing PowerPacker; through the PowerPacker GUI I would also be easily reminded I have to make some adjustments (using my batch-file) before building an ISO from the packages ?

I hope you understand what I mean ?

[Siginet]

That is a good idea. I have an idea how I can easily do this for the time being... then I will create a better way of doing this for v2.0.

I will see what I can come up with soon. I am going to be buisy for the next couple of days though. If I have time tonight I may put something together.

[ccfly]

Siginet, on Jul 7 2005, 05:09 PM, said:

That is a good idea.  I have an idea how I can easily do this for the time being... then I will create a better way of doing this for v2.0.

I will see what I can come up with soon.  I am going to be buisy for the next couple of days though. If I have time tonight I may put something together.
<{POST_SNAPBACK}>

Any chances that this PowerPack works with Windows 2000 too ?

BTW, thanks for the greate work !

[Siginet]

It was made for winXP... because the DriverPacks are made for XP...

But it may work with 2000 because the DP kind of work for 2000. But all of the options are for XP... so you could just select an xp option even though you are using 2000. I am pretty sure it will work with 2000 without the DPs.

In a later version I am thinking of adding 2000 support 2003 support and x64 support.

[Siginet]

Check it out...
Windows XP PowerPacker v1.0 RC1 has been posted at www.betanews.com!

HERE

It has only been there for about a day and it has been downloaded over 1,000 times! And is rated 4.3 out of 5!!!

[Bâshrat the Sneaky]

Siginet, on Jul 9 2005, 07:23 AM, said:

Check it out...
Windows XP PowerPacker v1.0 RC1 has been posted at www.betanews.com!

HERE

It has only been there for about a day and it has been downloaded over 1,000 times!  And is rated 4.3 out of 5!!!
<{POST_SNAPBACK}>

Good job!

P.S.: how long did it take to get your files verified there? At tucows it takes MONTHS.

[Siginet]

I didn't even put it there. I have no idea how it got there. Sombody must have saw it here and put it there. I am suprised the DriverPacks are not there..??!!

[Telenut]

Nice program! (I guess)
Had some time today to test is. Some remarks:
It's not easy to understand the main screen. But it's ok for most of the people over here I guess :-)
A tutorial for changing the bootscreen would be nice to. And as said before: the tree structure is not so nice .

I've just did my fist test in VMware and had this BSOD error: Session3_initialization_failed

let's try again

[Siginet]

Telenut, on Jul 9 2005, 03:13 PM, said:

Nice program! (I guess)
Had some time today to test is. Some remarks:
It's not easy to understand the main screen. But it's ok for most of the people over here I guess :-)
A tutorial for changing the bootscreen would be nice to. And as said before: the tree structure is not so nice .

I've just did my fist test in VMware and had this BSOD error: Session3_initialization_failed

let's try again
<{POST_SNAPBACK}>

The bsod you received... I'm not sure what caused it. When did you get this error? Did you use Nlite at all? Did you integrate anything into the xp files? What type of XP are you trying to install? With or without DPs? Please post as much information as you can. Thanks.

[Telenut]

I used nLite, so I guess that's the 'problem'. With or without the DP's.
What exactly causes the problem is something I'll try to find out now.

[Siginet]

OK everybody... I have finished codeing Windows XP PowerPacker 1.0 RC2!
This one I did not have to fix any bugs... I just added some cool features, a logo to the right side of the gui, and some donation buttons (Just incase anyone is feeling thoughtful.

The cool new features are by request.

I have added options to run your own batch files within different periods of the packing process.

Here is a quote from what I have added to the help file:

Quote

Running extra scripts:
It is now possible to run 4 different batch files durring the packing process.
PREPACK.BAT: Create a batch file that you would want to run before the driverpacks are installed and just after the I386 directory is copied over to the pack. Name this file "PREPACK.BAT" and put it in your "Extra Pack Files" directory. This file will be copied over to the pack at the same level as the I386 folder so that you can run commands there.

PREROOT.BAT: Create a batch file that you would want to run before the driverpacks are installed and just after the I386 directory is copied over to the pack. Name this file "PREROOT.BAT" and put it in your "Extra Root Files" directory. This file will be copied over to the root of your destination so that you can run commands there.

AFTERPACK.BAT: Create a batch file that you would want to run as the last step of the packing process. Name this file "AFTERPACK.BAT" and put it in your "Extra Pack Files" directory. This file will be copied over to the pack at the same level as the I386 folder so that you can run commands there.

AFTERROOT.BAT: Create a batch file that you would want to run as the last step of the packing process. Name this file "AFTERROOT.BAT" and put it in your "Extra Root Files" directory. This file will be copied over to the root of your destination directory so that you can run commands there.

These options are great for making everything unattended. You can now use windows XP SP1 as your source and have a batch file which integrates SP2 to it before it integrates the drivers etc...

Also... people can release batch files that they have made as addons for PowerPacker.

For now that will be fine... but in a later release I will make it so you can run any kind of file (Not just a .bat file). Then I will make extra tools that you can use with powerpacker (like integrating RyanVM's XP Updates).

I would upload this fine release for everybody now... but it looks like something is wrong with my ftpserver and it doesn't allow me to upload right now. So hopefully the new version will be released sometime today.

Does anybody have a little extra webspace that I can upload this to as a mirror site?

This post has been edited by Siginet: 10 July 2005 - 12:56 PM

[MHz]

Hi Siginet,

Nice little program, you have created. I have started it up, for a look. I notice that someone cannot operate the program without closing the helpfile first. Perhaps you could change this? Also, when browsing for a folder, the gui remains enabled. This allows guigetmsg to continue adding to the stack.
I will let you know of other issues, when I get to do some packing.

[Martin L]

here you have a mirror: http://www.msfn.org/...er_v1.0_RC2.zip

nice program, thanks

[Siginet]

MHz, on Jul 10 2005, 11:47 PM, said:

Hi Siginet,

Nice little program, you have created. I have started it up, for a look. I notice that someone cannot operate the program without closing the helpfile first. Perhaps you could change this? Also, when browsing for a folder, the gui remains enabled. This allows guigetmsg to continue adding to the stack.
I will let you know of other issues, when I get to do some packing.
<{POST_SNAPBACK}>

Yes I noticed that it does not disable the gui in the background and that is a small bug that I needed to fix. I will make sure that I fix it for the next release. Also the gui is not disabled during the packing process which I need to fix. Thanks for reminding me. I didn't even think about the issue when using the help file. Both good points. Thank You very much!

Martin L, on Jul 10 2005, 11:58 PM, said:

here you have a mirror: http://www.msfn.org/...er_v1.0_RC2.zip

nice program, thanks
<{POST_SNAPBACK}>

Thanks for this mirror I appreciate it a lot! It will definatly come in handy!

[carputer fan]

I am testing this program and having some problem. see the attached error file.

After I selected the output directory and leave the field, program crash.

My system setup was: XP pro with SP2

I tried again with XP pro with SP1 it works without any problem.

Any help....

Attached File(s)

•  error1.jpg (85.37K)
  Number of downloads: 55

[KuDoZ]

Wonfderful program I must agree, but I'm having a problem here...

I've added two XP Corporate installations (one nLited with SP2 etc). These were all built fine and I packaged the ISO to find it was too large to burn.

Going back through the directories I removed some apps to fix that, however, I can't simply run the "Package ISO" command now can I?

From what I understand you have to have JUST added a pack (and not left the program) before you can package?

Cheers,

Scott

EDIT- Scratch that... it DOES work, but I have to set all the parameters to the last "Pack" input...

This post has been edited by KuDoZ: 12 July 2005 - 06:11 AM

[Siginet]

carputer fan, on Jul 12 2005, 05:49 AM, said:

I am testing this program and having some problem. see the attached error file.

After I selected the output directory and leave the field, program crash.

My system setup was:  XP pro with SP2

I tried again with XP pro with SP1 it works without any problem.

Any help....
<{POST_SNAPBACK}>

I have never seen this kind of error. My guess is it must be some sort of computer side error. The program was built and tested on WinXP SP2. I have never tested it on SP1. All I can think is check on anything that may block the program from doing things. Have you ever had viruses on your computer or spyware? That error seems like it may be caused by a damaged system. I could be wrong... but I have no idea why you would get that kind of error. Please keep me posted.

KuDoZ, on Jul 12 2005, 06:09 AM, said:

Wonfderful program I must agree, but I'm having a problem here...

I've added two XP Corporate installations (one nLited with SP2 etc). These were all built fine and I packaged the ISO to find it was too large to burn.

Going back through the directories I removed some apps to fix that, however, I can't simply run the "Package ISO" command now can I?

From what I understand you have to have JUST added a pack (and not left the program) before you can package?

Cheers,

Scott

EDIT- Scratch that... it DOES work, but I have to set all the parameters to the last "Pack" input...
<{POST_SNAPBACK}>

When you go to package an ISO you must only point to your destination. All of the other options are not needed. But it needs to know what to package. Also... make sure you have enough space on the drive you are creating your image on. It must have enough space to create the full size of the disk before optimisation or cdimage will turn off.

[Siginet]

MHz, on Jul 10 2005, 11:47 PM, said:

I notice that someone cannot operate the program without closing the helpfile first. Perhaps you could change this?
<{POST_SNAPBACK}>

This bug has been fixed in Windows XP PowerPacker v1.0 RC3

MHz, on Jul 10 2005, 11:47 PM, said:

Also, when browsing for a folder, the gui remains enabled. This allows guigetmsg to continue adding to the stack.
<{POST_SNAPBACK}>

This bug has been fixed in Windows XP PowerPacker v1.0 RC3

The maximize button is now disabled as well.
And a few other minor but annoying bugs fixed.
Windows XP PowerPacker RC3 should be released sometime tommorrow.

Once v1.0 full is released I will begin writeing plugins.