Siginet

Well... it is finally here! Windows XP PowerPacker v1.0 RC5 This is the biggest update ever! PowerPacker will help a user create a Multiboot Windows XP disk with or without DriverPacks. It will do almost everything for you, even hex edit the files needed to be hexed, create the boot directory, boot menu, etc. It makes creating multiboot XP disks a breeze. This program was made with the BTS DriverPacks in mind. Basically it does just about everything you need to do to add a windows XP load to your MultiBoot Disk. It will gather the needed files from your source XP CD and put them into a directory you specify. It will grab the DriverPack Files and install them. It will create a boot directory for your load and even hex edit the files that need to be HEXED to allow you to boot to it. It will put the needed info into the boot list so you can select your XP load. It makes testing the DriverPacks very easy!!! ================================================== History: ================================================== v1.0 RC5 - 08-17-05 I have extensively re-written most of the code to make it function much better. 1. RC4 had hesitation issues when browsing and selecting things. That is fixed in RC5. 2. I have added a checkbox which allows the user to exclude WIN9XUPG folders from being copied to the destination (To help save a lot of space of your final product if you do not plan on using the winnt32.exe upgrade option... which nobody should use anyways). 3. Also another check box for the user to exclude the LANG folder from being copied to the destination (Which also saves a lot of room and is not needed if you are only going to be using a localized version of WinXP). 4. Also as promised... I made major use of the new powpack.ini file! You now can call PowerPacker_v1.0RC5.exe from a script file using certain parameters and you can actually create your whole entire multiboot disk 100% unattended!!! Completley from the first pack to the last pack... and even have it compile your iso into the destination and name you specify! No more sitting at the computer for hours waiting for every pack to finish so you can start the next pack. Once you have created your script file... and your set of ini files all you will need to do is run your script and leave. Come back later and everything is done! I think I deserve a round of applause for that! You all will never know what I had to do to get this program capable of doing that. (Check the updated help file for more information.) 5. Updated the help file with instructions on how to use the unattended parameters. 6. Added a "Tri-Pack" Checkbox... which will allow a user to quickly create three packs from one source. (Unattended with Driverpacks, Unattended without DriverPacks, and a regular attended pack.) 7. Added a Checkbox called "Custom Pack Name" which will allow a user to choose a four character name to be used as the destination directories and boot files. (**NOTE** when you use this option you have to manually edit the BOOT\cdshell.ini file to add your custom pack to the boot menu.) 8. Many other changes were made... but there are too many to list and remember. Please post bugs and requests in this thread... and be nice... this is my first Public App! ScreenShots: powerpacker-gui.jpg (Screenshot Updated August 17th 2005) Download/Rate Windows XP PowerPacker HERE ONLINE @ BetaNews.com Or download it from these mirrors: HERE ONLINE Thanks to my server for this mirror. Mirror 2 ONLINE Thanks to Telenut for this mirror! Mirror 3 ONLINE Thanks to Moesasji for this mirror! Mirror 4 ONLINE Thanks to UnO for this mirror! P.S. Please check out Windows XP PowerPacker's spot at BetaNews.com Give it a rating and place a comment if you get a chance. Thanks everybody! Looks like Windows XP PowerPacker is becoming very popular! Check out google to see what I am talking about. Search: Windows XP PowerPacker on GOOGLE.com I even found a site that claims to have a keygenerator and Crack for WinXP PowerPacker! (Duh... it's freeware and doesn't need a keygen or crack.) Please Don't get the crack it must be a virus!!!

A huge thank you to Martin L and Xper for creating a new Forum at MSFN.ORG for Windows XP PowerPacker!!! I will be back soon to post some tips/tutorials and hopefully RC5!

BartPE support will be added in v2.0 Windows PowerPacker... or a plugin may be created to add BartPE. But yes I do have plans for that. The Tri-Pack option does not take up much more space as long as you are creating an optimized ISO. You can use the built in Package ISO feature for that. Also... the tri-pack option actually only puts 2 sets of files in the ROOT folder. The Unattended with DriverPacks is a full pack, The Unattended without DriverPacks is a full pack, and the Regular pack is only the Boot files pointing to the unattended without driverpack ROOT files. (Which is a way to save space) Also with the "WIN9XUPG and LANG folders being excluded you also save a lot of space. I currently have a cd with a Tri-Pack of WinXP Pro Corp, Tri-Pack of WinXP Pro Retail and a Tri-Pack of WinXP Pro OEM... all on 1 cd. Which gives me 9 choices to choose from. Currently WinXP PowerPacker uses CDIMAGE.exe to compile the optimised iso... but probably the next version will get rid of CDIMAGE.EXE and use mkisofs.exe. But a user will easily be able to use cdimage.exe instead of mkisofs.exe if he/she wishes. I will be posting a simple tutorial on how to do that. Manually yes. You can also place your custom cdshell files in the "Extra Root" folder and copy them over the originals. Also... if you make a Windows XP looking boot picture I would like to use it in WinXP PowerPacker. I want to give it more of an XP look. The boot picture it has now is basically the one I made for my own company.

OK... now I have added a "Tri-Pack" checkbox. What this button does is... After you have selected all of your options to make a full pack, (including Unattended with DriverPacks), you can place a checkmark in the "Tri-Pack" checkbox. Now when you click on "Pack These Files Into The Destination" you will not only create a pack that is Unattended with driverpacks... but it will automatically create a pack that is Unattended without DriverPacks and a pack that is User Attended Without DriverPacks. So in one sweep you will create a whole set... which I am calling a Tri-Pack. Another feature I have added is... Lets say you don't want your pack named "XPPC", you want it named "X234" you can now add a custom name to any pack & it still will make all of the correct changes to every file. (This feature does not work with the Tri-Pack option though.) Just for a sneak peak at how to use the unattended features that are in the new RC5 release... ============================================================================== To create a "Pack" or "Tri-Pack" unattendedly all you will need to do is call XP Powerpacker from a script file with 2 parameters. 1. The first parameter is the path and file you wish to use as the ini file. (With quotes if your path contains spaces.) 2. The second parameter needs to be "-pack" (with or without the quotes) Example: Creating a Pack or Tri-Pack Unattended PowerPacker_v1.0_RC5.exe "D:\mypath\tomy\inifile\XP_Corp.ini" -pack ============================================================================== Now if you have finished creating packs and are ready to compile the iso... you can use this set of 4 parameters to Unattendedly "Package ISO"... 1. The first parameter should be "-package" (With or without the quotes) 2. The second parameter is the lable you want on your disk. (With quotes if your name contains spaces.) (Also I think the max abount of characters you can use is 16) 3. The third parameter is the path and file you wish to use as the ini file. (With quotes if your path contains spaces.) 4. The fourth parameter would be the path and filename of the iso you wish to create. Example: Packaging ISO Unattended PowerPacker_v1.0_RC5.exe -package "My PowerPack" "D:\mypath\tomy\inifile\XP_Corp.ini" "D:\ISOs\PowerPackDVD\PowerPackDVD_08-17-05.iso" ============================================================================== Another thing you can do is call XPPowerPacker with 1 parameter to open it using a different ini file than the default powpack.ini file. If the ini file you tell it to open with does not exist WinXP PowerPacker will create a brand new ini file with the name and path you specified. This comes in handy when you are getting your batch file ready. Just create a batch file that will open WinXP Powerpacker 1 by one and create all of your ini files that you will use in you "Packing batch file:. Example: Open Windows XP PowerPacker with a different ini file or create a new ini file. PowerPacker_v1.0_RC5.exe "D:\mypath\tomy\inifile\XPPC.ini"

I have XPize installed on my computer now. It looks very nice! I even installed the cmd mod to test out Windows XP PowerPacker and it seems to work just fine. Thanks!

@Bashrat I think I can host the base for you until your site goes back online.

Windows XP PowerPacker RC5 is very close to being finished. I have extensively re-written most of the code to make it function much better. 1. RC4 had hesitation issues when browsing and selecting things. That is fixed in RC5. 2. I have added a checkbox which allows the user to exclude WIN9XUPG folders from being copied to the destination (To help save a lot of space of your final product if you do not plan on using the winnt32.exe upgrade option... which nobody should use anyways). 3. Also another check box for the user to exclude the LANG folder from being copied to the destination (Which also saves a lot of room and is not needed if you are only going to be using a localized version of WinXP). 4. Also as promised... I made major use of the new powpack.ini file! You now can call WinXP PowerPacker.exe from a script file using certain parameters and you can actually create your whole entire multiboot disk 100% unattended!!! Completley from the first pack to the last pack... and even have it compile your iso into the destination and name you specify! No more sitting at the computer for hours waiting for every pack to finish so you can start the next pack. Once you have created your script file... and your set of ini files all you will need to do is run your script and leave. Come back later and everything is done! I think I deserve a round of applause for that! You all will never know what I had to do to get this program capable of doing that. Everything I listed above is finished and working 100%... but I am not finished yet. I have a few more ideas packed in this little brain of mine. So stay tuned!!!

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 <{POST_SNAPBACK}> Glad you found your issue. Try this. Before running NLite go into your dosnet.inf file and search for "system32\smss.exe" Write down all of the lines you find. Run NLite on it then check the dosnet.inf file again. Are there any differences? If so record your findings and post them at my forum so I can help you further analize it.

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! Windows XP PowerPacker Forum!

Deletes one or more files. DEL [/P] [/F] [/S] [/Q] [/A[[:]attributes]] names ERASE [/P] [/F] [/S] [/Q] [/A[[:]attributes]] names names Specifies a list of one or more files or directories. Wildcards may be used to delete multiple files. If a directory is specified, all files within the directory will be deleted. /P Prompts for confirmation before deleting each file. /F Force deleting of read-only files. /S Delete specified files from all subdirectories. /Q Quiet mode, do not ask if ok to delete on global wildcard /A Selects files to delete based on attributes attributes R Read-only files S System files H Hidden files A Files ready for archiving - Prefix meaning not If Command Extensions are enabled DEL and ERASE change as follows: The display semantics of the /S switch are reversed in that it shows you only the files that are deleted, not the ones it could not find. Or it looks like you want to delete the entire folders. Try the RD command. Removes (deletes) a directory. RMDIR [/S] [/Q] [drive:]path RD [/S] [/Q] [drive:]path /S Removes all directories and files in the specified directory in addition to the directory itself. Used to remove a directory tree. /Q Quiet mode, do not ask if ok to remove a directory tree with /S Echo Deleting Setup Program Files RD /S /Q "%systemdrive%\Install\FreeAV" "%systemdrive%\Documents and Settings\All Users\Desktop" RD /S /Q "%systemdrive%\Install\REGISTRY" "%systemdrive%\Documents and Settings\All Users\Desktop" RD /S /Q "%systemdrive%\Install\VCDgear" "%systemdrive%\Documents and Settings\All Users\Desktop" RD /S /Q "%systemdrive%\Install\Riochet" "%systemdrive%\Documents and Settings\All Users\Desktop" RD /S /Q "%systemdrive%\Install\dB PowerAMP" "%systemdrive%\Documents and Settings\All Users\Desktop" P.S. You can find most cmd switches by typing the command and using the switch /?

But I would think the way the DPbase works it should work just fine on any of the OSes (win2000, win2003, & winxp). The only difference I would think would be different DPs. Maybe some win2000 or win2003 users would like to start testing the theory out and posting their experiances?

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.

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 ! <{POST_SNAPBACK}> 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.

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! 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! I started the packing before I left to work at a clients office and when I came back it was completly finished. 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.

Crazy.

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! I think I'm gonna download it! 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

Haha or errr...

My bad! I accidentally compiled the exe using the Autoit Beta code. I just recompiled it the normal way and it is working now. Please redownload it in a few mins.

What the hell??? I am looking into it now. Sorry guys.

Windows XP PowerPacker v1.0 RC4 is now online! Enjoy! Please be careful of the link you use to download... they have not all been updated yet. It has not been updated at BetaNews.com yet either. It is online at my server though.

Windows XP PowerPacker v1 RC3 was pretty close to being flawless but... Windows XP PowerPacker v1.0 RC4 should be finished today. I just have to finish up a few last peices to it. The biggest change in RC4 is that I've added a powpack.ini file that will remember your previous settings. So if you close powerpacker and reopen it... it will still have all of your settings. This also opens another idea that I will add to RC5. In RC5 I am going to try to code it so you can call PowerPacker from a batch or script file with a couple parameters. You will be able to specify a .ini file to be used for settings and it will use those settings to create your pack unattendedly. I will also add parameters to compile the iso unattendedly. This way people will be able to create a batch or script file that will create all of the packs and compile the iso all unattended! I think RC5 should be the last Release Candidate. Sorry for so many RC's... I did not expect to add so many new features to it. Just wanted to let you know RC4 should be online later today. I also fixed the mis-spelled "Generating" word, Made all progress windows not stay on top, iso compilation will now pop up a window stating it has finished. If the iso was not created or if the iso is 0 kb in size it will tell you something went wrong. P.S. It would be nice to get some donations from those who enjoy powerpacker.

Looks like a typo I'll fix it. As for the error you are getting D:\A\XPPO\SETUPLDR.BIN D:\A\ROOT\XPPO\I386\SETUPLDR.BIN that is normal. It is just telling you those files are very simular... but they are a little different. Which is true. If your iso is not there... then you may not have had enough space on your hard drive to create it. You need to have as much space on your hard drive as you are using in your destination directory. In the next version of powerpacker there is more error checking implemented.

That shouldn't be the issue at all. PowerPacker does not use winnt32.exe when creating the boot directory. It parses the dosnet.inf file itself.

I was thinking the same thing lol. Thanx Nazgul!

Try using my app Windows XP Powerpacker. It will do exactly what you need. Edit... well almost what you want. Jito is right some of what you want to do is not possible. Sorry.