Jump to content

[Release] Windows XP PowerPacker 1.0 RC8 Beta4


Siginet

Recommended Posts

Ok folks...

I've just finished coding Beta4 and as promised... I've 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. :D

Please report any bugs you may find.

Download @ Siginet Software

Enjoy!

Beta-MainWindow.gif

Edited by Siginet
Link to comment
Share on other sites


Ok folks...

I've just finished coding Beta4 and as promised... I've 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. :D

Please report any bugs you may find.

Download @ Siginet Software

Enjoy!

Beta-MainWindow.gif

So am I to assume there are no bugs? :D Come on guys... I need some Beta testing. :(

Link to comment
Share on other sites

We're getting there...I just encountered this today :D.

Will test and report. Hopefully, the Extra Pack File function was fixed ;).

:blink: Actually I don't remember if I fixed it or not.

Let me know if it doesn't. But I think I fixed it a while back when I first started coding Beta4.

Link to comment
Share on other sites

Well, I can't test it now, but just started once to check out what the advanced tab was about. I found 2 glitches:

File => properties: still there, I think it's unneeded when you have the advanced tab. (now it just does nothing when you click on it)

Info => help isn't working

When I select my source path, will the powerpacker automaticly see if I have a corporate or a retail version? I don't have to activate my windows, but I don't know if it's a corporate version. We bought it via MS-KIS (my mom is a teacher)

Looks like a cool program! Keep up the good work!

(btw: I think you made the RyanVM slipstreamer too, is this integrated in Powerpacker? I can't find it. Should I just first use the slipstreamer and then the XP Powerpacker?)

Link to comment
Share on other sites

Info => help isn't working
Help doesn't work because the actual help file doesn't exist. Siginet hasn't updated it in a while (last update I guess was for 1.0 RC5 or something). It will undoubtedly be packaged into the final RC8, but for now, the actual executable file contains only the program and does not extract anything (except writing a powpack.ini settings file).
When I select my source path, will the powerpacker automaticly see if I have a corporate or a retail version? I don't have to activate my windows, but I don't know if it's a corporate version. We bought it via MS-KIS (my mom is a teacher)

Looks like a cool program! Keep up the good work!

(btw: I think you made the RyanVM slipstreamer too, is this integrated in Powerpacker? I can't find it. Should I just first use the slipstreamer and then the XP Powerpacker?)

Sorry, I know I'm not Siginet, but I can still answer your questions. PowerPacker doesn't have the ability to detect the type of source you have, but in your case, you should select 'corporate'. It doesn't really matter for the actual packaging, but the options are there so that PowerPacker activates the correct sections in the boot menu files (it also tells the program what to name the folders).

The RyanVM Integrator is maintained by RyanVM (big surprise :lol:!). It is not packaged into WXPP though, so yes, you need to download it separately. WXPP can in some way communicate with the RyanVM Integrator, but you need to wait for Siginet to explain this because I am not familiar with that portion of the program.

Hope this helps :)!

Link to comment
Share on other sites

Info => help isn't working
Help doesn't work because the actual help file doesn't exist. Siginet hasn't updated it in a while (last update I guess was for 1.0 RC5 or something). It will undoubtedly be packaged into the final RC8, but for now, the actual executable file contains only the program and does not extract anything (except writing a powpack.ini settings file).
When I select my source path, will the powerpacker automaticly see if I have a corporate or a retail version? I don't have to activate my windows, but I don't know if it's a corporate version. We bought it via MS-KIS (my mom is a teacher)

Looks like a cool program! Keep up the good work!

(btw: I think you made the RyanVM slipstreamer too, is this integrated in Powerpacker? I can't find it. Should I just first use the slipstreamer and then the XP Powerpacker?)

Sorry, I know I'm not Siginet, but I can still answer your questions. PowerPacker doesn't have the ability to detect the type of source you have, but in your case, you should select 'corporate'. It doesn't really matter for the actual packaging, but the options are there so that PowerPacker activates the correct sections in the boot menu files (it also tells the program what to name the folders).

The RyanVM Integrator is maintained by RyanVM (big surprise :lol:!). It is not packaged into WXPP though, so yes, you need to download it separately. WXPP can in some way communicate with the RyanVM Integrator, but you need to wait for Siginet to explain this because I am not familiar with that portion of the program.

Hope this helps :)!

You were almost correct about everything... except the RyanVM Integrator. ;) I am the creator of the RyanVM Integrator... and I do manage it. I made the integrator for Ryan because I enjoyed his UpdatePacks so much. A lot of the integrator was made by Ryan telling me what he wanted it to do and I coded it to do it. Then I added my ideas to it as well. ;) A lot of the addon capabilities were designed by me.

What I do is I use the RVMIntegrator first... but in the advanced tab I select Run External File, Browse to PowerPacker, then in the parameters box I put:

"X:\Path\To\A\Settings\File\powpack.ini" -PACK

This will utalize both programs. First integrating everything with the integrator then calling powerpacker unattendedly and packaging everything. Then you can use the Run External File feature in powerpacker as well to call the integrator in the same way:

Select the integrator file, Then in the parameters put this:

"X:\Path\To\A\Settings\File\integrator.ini" /INTEGRATE

This is a cool way to chain link the programs together so everything is unattended. ;)

As for PowerPacker detecting the different types of OSes... It will in a later version. The next integrator allready detects the different OSes for you... and I will be implementing that code into powerpacker as well.

Link to comment
Share on other sites

You were almost correct about everything... except the RyanVM Integrator. I am the creator of the RyanVM Integrator... and I do manage it. I made the integrator for Ryan because I enjoyed his UpdatePacks so much. A lot of the integrator was made by Ryan telling me what he wanted it to do and I coded it to do it. Then I added my ideas to it as well. A lot of the addon capabilities were designed by me.
Whoops! So sorry about my ignorance! :blushing: Guess I should have done some research first :D!
Link to comment
Share on other sites

will the powerpacker automaticly see if I have a corporate or a retail version? I don't have to activate my windows, but I don't know if it's a corporate version. We bought it via MS-KIS (my mom is a teacher)

i have no idea if it does detect the type but it shouldnt be too hard to implement

anything that doesn't require activation is a corporate version.

99% of all software provided to teachers through their work is corporate, well it is here in australia anyway.

Link to comment
Share on other sites

The next integrator... v1.3 will detect all versions of windows Pro Corp, Pro Retail, Pro OEM, Home Corp, Home Retail, Home OEM, Media Center, and so on.

Eventually I will implement the code into powerpacker as well. ;) But we are still in beta. So there is still a lot to be added. But since v1.0 RC8 has so many changes in it I decided to release a bunch of Betas so that users can still use the new features and not have to wait so long for the final RC8.

I also plan on adding an advanced feature to allow a user to use multiple winnt.sif files for a pack... which I think will be an awsome new feature. :thumbup

Link to comment
Share on other sites

hi...

finally got around to testing it today...

found a problem, it may be just me...

slipstreamed driverpacks using the latest base and latest driver packs as of today into a fresh xp source and tested. all good.

but when i use the mysettings.ini with powerpacker the driverpacks api thing comes up but it finishes up a little to quickly and there is no driverpack files (the 7z ones) copied to my multi folder.

anyone else come accross this or something similar.

Link to comment
Share on other sites

hi...

finally got around to testing it today...

found a problem, it may be just me...

slipstreamed driverpacks using the latest base and latest driver packs as of today into a fresh xp source and tested. all good.

but when i use the mysettings.ini with powerpacker the driverpacks api thing comes up but it finishes up a little to quickly and there is no driverpack files (the 7z ones) copied to my multi folder.

anyone else come accross this or something similar.

It shouldn't use the multipack feature of the DP Base. Just use the regular Disc feature.

Link to comment
Share on other sites

hi...

finally got around to testing it today...

found a problem, it may be just me...

slipstreamed driverpacks using the latest base and latest driver packs as of today into a fresh xp source and tested. all good.

but when i use the mysettings.ini with powerpacker the driverpacks api thing comes up but it finishes up a little to quickly and there is no driverpack files (the 7z ones) copied to my multi folder.

anyone else come accross this or something similar.

It shouldn't use the multipack feature of the DP Base. Just use the regular Disc feature.

multipack feature of dp base?.. i cant see an option for multiple or single

??? i dont quite understand what you are saying...

Edited by kris_h
Link to comment
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
  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...