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).
Info => help isn't working
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).
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?)
The RyanVM Integrator is maintained by RyanVM (big surprise !). 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:
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:
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.