Jump to content

[Release] Windows XP PowerPacker


Recommended Posts


LOL! I found a website that claims to have the full finished version of Windows XP PowerPacker v1.0! It even claims to have a Keygen and Crack to go with it! :thumbup

I think I'm gonna download it! :D

Or... uhhhh... hold on a sec... I am the person creating Windows XP PowerPacker..!!?? LOL!

XP PowerPacker is not even finished for one thing. Second... it is freeware. No need to crack it or have a keygen. ;) So please beware of any sites claiming to have something like this. It must be a virus.

But for fun...

Check out how popular WinXP PowerPacker has become...

Search: Windows XP PowerPacker @ Google.com

Link to post
Share on other sites

Powerpacker 1.0rc4 is (again) a great program. I do have a question concerning it however....

One of my pc's uses a Highpoint 370 Raid controller (integrated on the mobo) and so far I have not been able to use the driverpacks massstorage succesfully on it.

For my ultimate MultiBoot DVD I am looking for a way tha powerpack packs these two packs:

The basis of this pack is XPSP2, Nlited with RyanVM and the official (and confirmed working) Highpoint 370 integrated through Nlite. As far as the Bashrat Driverpacks are concerned, I compiled a UWXPCD_ROOT dir WITHOUT the masstorage driverpack.
The settings in powerpacker I use are:

Input = g:\uaxp\uaxpenglitedhpt
Output = G:\PPOutput
Unattended Install
Winnt.sif directory = g:\uaxp\uaxpadd
$OEMdirectory = g:\uaxp\uapxextras\$OEM$
Driverpacks = integrated (except masstorage driverpack)
Windows XP Version = Windows XP Professional
Windows XP Edition = Corporate
Extra Pack Files = NO
Extra Root files = YES

And the second pack looks like this:

The basis of this pack is XPSP2, Nlited with RyanVM. In this pack I do not integrate the official Highpoint Driverpack, and do use the Bashrat's driverpacks INCLUDING the masstorage driverpack (I've compiled an UWXPCD_ROOT directory incorporating the massstorage driverpack).
The settings in powerpacker I use are:

Input = g:\uaxp\uaxpenglitedhpt
Output = G:\PPOutput
Unattended Install
Winnt.sif directory = g:\uaxp\uaxpadd
$OEMdirectory = g:\uaxp\uapxextras\$OEM$
Driverpacks = ALL integrated (including massstorage driverpack)
Windows XP Version = Windows XP Professional
Windows XP Edition = Corporate
Extra Pack Files = NO
Extra Root files = YES

It seems that PowerPacker, since both versions have the options to use the driverpacks, make an unattended CD (DVD) and are based on WinXP Pro Corp, tries to install both the packs in the same directory on the output-folder.... Both packs get copied into the XPPC folder and therefore I have only one image to boot from, instead of the desired two.... Since the two only differ as to the uses base and the usage of masstorage Bashrat Driverpacks (but I explained above why these differences are important to me), Powerpacker treats them as the same packs and copy the second one over the first one in making the packs.

Any ideas on how to avoid this and get a working setup ?

Link to post
Share on other sites

Powerpacker 1.0rc4 is (again) a great program. I do have a question concerning it however....

One of my pc's uses a Highpoint 370 Raid controller (integrated on the mobo) and so far I have not been able to use the driverpacks massstorage succesfully on it.

For my ultimate MultiBoot DVD I am looking for a way tha powerpack packs these two packs:

The basis of this pack is XPSP2, Nlited with RyanVM and the official (and confirmed working) Highpoint 370 integrated through Nlite. As far as the Bashrat Driverpacks are concerned, I compiled a UWXPCD_ROOT dir WITHOUT the masstorage driverpack.
The settings in powerpacker I use are:

Input = g:\uaxp\uaxpenglitedhpt
Output = G:\PPOutput
Unattended Install
Winnt.sif directory = g:\uaxp\uaxpadd
$OEMdirectory = g:\uaxp\uapxextras\$OEM$
Driverpacks = integrated (except masstorage driverpack)
Windows XP Version = Windows XP Professional
Windows XP Edition = Corporate
Extra Pack Files = NO
Extra Root files = YES

And the second pack looks like this:

The basis of this pack is XPSP2, Nlited with RyanVM. In this pack I do not integrate the official Highpoint Driverpack, and do use the Bashrat's driverpacks INCLUDING the masstorage driverpack (I've compiled an UWXPCD_ROOT directory incorporating the massstorage driverpack).
The settings in powerpacker I use are:

Input = g:\uaxp\uaxpenglitedhpt
Output = G:\PPOutput
Unattended Install
Winnt.sif directory = g:\uaxp\uaxpadd
$OEMdirectory = g:\uaxp\uapxextras\$OEM$
Driverpacks = ALL integrated (including massstorage driverpack)
Windows XP Version = Windows XP Professional
Windows XP Edition = Corporate
Extra Pack Files = NO
Extra Root files = YES

It seems that PowerPacker, since both versions have the options to use the driverpacks, make an unattended CD (DVD) and are based on WinXP Pro Corp, tries to install both the packs in the same directory on the output-folder.... Both packs get copied into the XPPC folder and therefore I have only one image to boot from, instead of the desired two.... Since the two only differ as to the uses base and the usage of masstorage Bashrat Driverpacks (but I explained above why these differences are important to me), Powerpacker treats them as the same packs and copy the second one over the first one in making the packs.

Any ideas on how to avoid this and get a working setup ?

Link to post
Share on other sites

Hmm... you may have found a huge bug. I am looking into it now.

I actually should be releasing WXP PowerPacker 1.0 RC5 very soon. I almost finished re-coding it allready. The code has been very optimised... so it should actually run better as well. Also I have allready got the unattended paprameters working as well for creating the packs from a batch file. Now I am going to make unattended parameters for packaging the iso as well. It works very well though! :D I actually created a Multiboot DVD with

Windows XP Professional (Corp, Retail & Oem) (With DPs Unattended, Without DPs Unattended and a Regular pack)

Windows XP Home (Retail & Oem) (With DPs Unattended, Without DPs Unattended and a Regular pack)

Every pack seems to be complete. I had all of this compiled 100% unattended. All I had to do was run my batch file that called PowerPacker with some parameters. It seems to have worked flawlessly! :w00t:

I started the packing before I left to work at a clients office and when I came back it was completly finished. :thumbup

So everybody stay tuned... The best of Windows XP PowerPacker has only just begun! ;)

Edit:

@moesasji - I ran a test to see if I got the same error as you specified... but I do not. Are you sure you did not accidently have the DPs selected? Try again and see if you still get the error. Look inside your powpack.ini file and make sure that the

[DriverPacks]

OnOff=O

As long as that =O it will make the boot name XOPC. If it says OnOff=P When you've turned off the DPs... then there is a problem.

Edited by Siginet
Link to post
Share on other sites
@moesasji - I ran a test to see if I got the same error as you specified... but I do not.  Are you sure you did not accidently have the DPs selected?  Try again and see if you still get the error.  Look inside your powpack.ini file and make sure that the

[DriverPacks]

OnOff=O

As long as that =O it will make the boot name XOPC.  If it says OnOff=P When you've turned off the DPs... then there is a problem.

Siginet,

The problem is that I need two packs with dp ON and from the same XP-source. In one pack I use all the driverpacks except the masstorage, in the other I use all driverpacks including masstorage.

So if OnOff=P in powpack.ini bot times, then it is correct, but both times the directory created in the output directory is XPPC.

This is not a bug of PowerPacker, but by design. It is logically also, because not many people will need to make two almost identical packs. I need to, because the masstorage driverpack is not working on one of my pc's, but on the other one it is working.

Maybe you can integrate a check in PowerPacker 1.0RC6 to check whether the output-directory already exists. If it does, Powerpacker could create a ne directory based on the standard name + 1 (say: XPPC1). This way, I would be able to integrate the desired images into one MultiBoot DVD.

As for the development of PowerPacker concerns; I think you're doing great work. Keep it up, I'm already looking forward to the undoubtedly superb 1.0 Release !

Link to post
Share on other sites
@moesasji - I ran a test to see if I got the same error as you specified... but I do not.  Are you sure you did not accidently have the DPs selected?  Try again and see if you still get the error.  Look inside your powpack.ini file and make sure that the

[DriverPacks]

OnOff=O

As long as that =O it will make the boot name XOPC.  If it says OnOff=P When you've turned off the DPs... then there is a problem.

Siginet,

The problem is that I need two packs with dp ON and from the same XP-source. In one pack I use all the driverpacks except the masstorage, in the other I use all driverpacks including masstorage.

So if OnOff=P in powpack.ini bot times, then it is correct, but both times the directory created in the output directory is XPPC.

This is not a bug of PowerPacker, but by design. It is logically also, because not many people will need to make two almost identical packs. I need to, because the masstorage driverpack is not working on one of my pc's, but on the other one it is working.

Maybe you can integrate a check in PowerPacker 1.0RC6 to check whether the output-directory already exists. If it does, Powerpacker could create a ne directory based on the standard name + 1 (say: XPPC1). This way, I would be able to integrate the desired images into one MultiBoot DVD.

As for the development of PowerPacker concerns; I think you're doing great work. Keep it up, I'm already looking forward to the undoubtedly superb 1.0 Release !

Ok I understand what you want to do. I do the same thing pretty much. I do plan on adding something to the ini file that will allow you to customize the name used for the pack and creating some sort of plugin for the short cut (That I explain at the bottom. But here is what you need to do.

Well... since you are making one with mass storage and one without... there is no shortcut. You have to create a completly seperate pack.

1. What you can do is Point to a new destination and create the complete pack. Then you will have to hex edit a couple files and rename files / folders. There should be a file called XPPC.DAT that is on the root of the destination. That file can be named any 4 Letters or digits you want. Open this file with a hex editor and find the string "XPPC" replace it with the same name that you gave the .dat file. For instance if you named it "XP2C.DAT" then you will replace "XPPC" with "XP2C".

2. Next rename the XPPC folder that lies at the root of your destination (ALSO THE ONE INSIDE THE ROOT FOLDER!) to the same name "XP2C".

3. Inside that XP2C folder (The one at the root of the disk not the one in the ROOT folder) find setupldr.bin. Open this file with a hex editor. Find all 4 instances of "XPPC" and change them to "XP2C".

4. Now find txtsetup.sif in the same directory and open with notepad. Search for "XPPC" and replace with "XP2C".

5. Copy all of this pack (EXCEPT THE BOOT FOLDER!) to your original destination.

6. Inside your original destination go inside of the "BOOT" folder and find a file called cdshell.ini. Edit this file to suit your boot menu with the new pack.

That should be it.

If you weren't installing the mass storage dp. It would have been much easier. For instance if you wanted 2 XPPC packs that were completley Identical except for the winnt.sif file. All you would need to do is.

1. Copy the contents inside the "XPPC" folder on the root of your destination To a seperate 4 character folder on the root of the destination.

2. Edit the setupldr.bin file inside the new folder by searching for all 4 instances of "XPPC" and change them to the name you gave the folder.

3. Overwrite the winnt.sif file in this folder with the new winnt.sif file.

4. Copy the XPPC.DAT file on the root of the destination to another DAT file on the root of the destination and name it the same as that folder you made.

5. Edit cdshell.ini to fit your needs.

That's it. I think I covered everything. Let me know if you still need help.

Edited by Siginet
Link to post
Share on other sites
Looking forward for the Win2000 & Win2003 version soon

Not sure how soon it will be. It is gonna be a lot of coding. But it is definatly on my to do list after Windows XP PowerPacker v1.0 final gets released.

Link to post
Share on other sites

I've created a new forum for Windows XP PowerPacker so that I will have more room for support questions and posting tips and tricks.

Please check it out and become a member. You do not have to signup to be able to post... but I hope you would. :) Hope to see you there! :thumbup

Windows XP PowerPacker Forum!

Link to post
Share on other sites
finaly found it: If you remove 'manual install and update' with nLite, you get a BSOD.

deleting the win* folder in I386 is not a problem.

Good news ;) I wonder why it creates an error?

hi all, i've found what was the problem tha caused the BSOD:

\DVD\XOPC\SYSTEM32\SMSS.EXE is missing when using powerpack with my nLited windows. just this. if i manually copy it everything works fine.

i hope this could help anyone

thanks

sonica

Edited by sonica
Link to post
Share on other sites
Guest
This topic is now closed to further replies.
  • Recently Browsing   0 members

    No registered users viewing this page.

×
×
  • Create New...