Siginet

I would reccommend you use method 2 on a multiboot disk. Then you can move the OEM (Not the $OEM$) folder it creates to the root of your disk. Delete any OEM folders created by Method 2 in any of the other folders (You won't need them anymore.) I think Method 2 works much better, saves more room, and actually is faster in my opinion. You can also try using Windows XP PowerPacker, (In my signature) It will help you create a multiboot disk using method 2.

I think you only have to reintegrate when it comes to Mass Storage DP or when new Control Panels are being placed in a graphics or sound DP. And probably if a new chipset DP is released. As for the WLAN... I am pretty sure you can just add it to your OEM dir.

Good to see you back Bashrat! Great donation Muiz!

I found the problem. Thanks for pointing it out to me. Basically what is wrong is... in my code It is supposed to check to see if you selected Tri-Pack or if you've unselected it. It looks in the powpack.ini file for this information. But... if you have never used the program before that information is not in the powpack.ini file by default. So the program does not know what to do. I will look into the code a bit more tonight and fix it. In the mean time all you need to do is place a checkmark in the Tri-Pack box and then uncheck it. Then the program should work. Or you can put a checkmark in the Custom Name Pack box... type a custom name. Then uncheck the box. Thanks again for pointing out this error!

Hmmm... that's a weird problem. It should not sit idle it should begin copying your source files to the destination. Does it do anything at all after you click on the "Pack these files to the destination" Button? Can you post your destination and source paths and any other information you can think of that can help me further troubleshoot your issue? What OS are you running and how much space do you have left on your HD(s)?

1. What the need for the fake setup.exe is (what needs to be altered from the standard file)? It executes just before the gui portion of setup. It is the point where all of the DriverPacks are extracted. Then it starts the real setup.exe. 2. Where to obtain a newer version of this file, if at all possible or necessary? In the latest DriverPack Base I assume. 3. Whether this file is executed at the end of the first part of the text mode RIS setup (i.e. at the point after the MS drivers have loaded where is says "Setup is starting Windows...")? - I ask because currently on certain hardware platforms (Intel 915GUX, Pro 100/VE, Pentium 541 EM64T capable) the RIS install blue screens directly after this point quoting "unable to initialise network boot". I know it is not a NIC driver issue because other, older platforms (845/865 chipset) with the same NIC hardware and drivers work flawlessly. Same answer as 1. I am not an expert at ris though.

Thanks for pointing that out! I will runs some tests on that. But how would someone browse to a directory that is non existent to save the iso? I definatly see there being an issue if it is done using the unattended switches. But there shouldn't be a problem if it is done manually. In any case... i will make sure I add code to create the directory before creating the iso.

Sorry my host is down right now so all of the pictures in the thread are not working. They should be fixed sometime tommorrow.

Corporate / VLK is usually sold to big corporations. They can install unlimited copies on many different computers within the corporation. There is also no activation. Retail is a store bought copy that is sold in a box with the manual and other accesseries. It does need to be activated. OEM is just like Retail but it does not come in a box with the manual and is supposed to be purchased with a peice of hardware. For instance you could buy an OEM copy of windows with a new HardDrive or preloaded on a computer. OEM disks do require activation. If they have been preloaded sometimes you do not need to activate it because it has been allready activated by the manufacture. There is also an Upgrade disk that is the same as a Retail/OEM disk except that it is sold cheaper for someone who owns a previous version of Windows. You can install it on top of Win2000 for instance... or you can clean install it... but it will ask you for a valid copy of windows to install. It too needs activation. The only version that does not need any activation is Corporate/VLK (Volume License Key).

Hmmm... latley I have had people say they are having trouble making an iso. I don't know why some people are having an issue. If you can please give me more specific details of your structure so I can better help troubleshoot the issue and fix the problem if there is one. What is the path of your destination directory? (Where your files reside that you wish to use to create your iso). What is the path and name of the iso file you are wanting to create? How much space do you have on all of your available Hard drives? Which drives are you utalizing with the ISO creation process? Have you edited any of the files? Are you using the default BOOT directory or have you implemented your own? Please give me any info that can help me narrow down the problem.

Use cdimage.exe or mkisofs.exe with the corect parameters. You then can make a batch file that will allow you to compile your optimized isos.

It is retail XP Pro sp2. I have (seen not aquired ) a copy of the exact same one. On the Windows AIO DVD. According to the pid I would think it would be OEM... but I geuss it doesn't follow those guidlines for some reason.

Yep for instance... You have start /wait "%CDROM%\wincomp\netframework\netfx.msi "/qn REBOOT=Suppress" start /wait "%CDROM%\wincomp\vb runtime\vbrun60sp6.exe /Q:A /R:N" start /wait "%CDROM%\wincomp\directx9c\dxsetup.exe /silent" start /wait "%CDROM%\wincomp\flashplayer\Shockwave_Installer_Full.exe /s" Should be... start /wait "%CDROM%\wincomp\netframework\netfx.msi" /qn REBOOT=Suppress start /wait "%CDROM%\wincomp\vb runtime\vbrun60sp6.exe" /Q:A /R:N start /wait "%CDROM%\wincomp\directx9c\dxsetup.exe" /silent start /wait "%CDROM%\wincomp\flashplayer\Shockwave_Installer_Full.exe" /s The way you were doing it you were basically saying there were no switches. Everything between the quotes represents a path. The reson for the quotes is so that you can use a path which has spaces. The quote tell it that the spaces are part of the path. If you enclose your switches within those quotes it looks at them as if they were part of the path.

15,440 Downloads on September 10th at beta news. 4,408 more downloads since August 24th (The day I posted this thread). But where are the replys from most of the people who use it?

This might be a good place to start... Windows XP PowerPacker Tips And Tricks

You should have more than 1 DP file. You need the base and the driverpacks. There is a help file with windows xp powerpacker. And you may want to look at the tutorial for the dps as well. I am working on a way to make it a little simpler... but for now basically all you have to do is what is in the help file.

I fixed a few more bugs that slipped into this release. Please redownload if you previously downloaded. Make sure you download RC6.2! Sorry everybody... I have no idea how these bugs apeared in this release like that.

I am going to keep track of the complete history of Windows XP PowerPacker in this one thread. History: ================================================== v1.0 RC6.2 - 09-07-05 1. Fixed issue with Extra Root Files and Extra Pack Files not keeping the settings correctly in the ini file. (Not sure how this bug slipped into this version.) 2. Because of the settings not being saved to the ini file correctly the Extra Pack Files and Extra Root files were not being copied over to the destination. 3. The Tri-Pack and the Custom Name Pack checkboxes were not functioning correctly when first opening the gui. v1.0 RC6.1 - 09-06-05 1. Fixed Screwup I made with the Main Window. It was only a minor bug... but it's fixed now. v1.0 RC6 - 09-06-05 1. New File Menu that you can find at the top left of the main window. I got rid of the Help and About buttons and put them in the File Menu. Now all of the Options (CheckBoxes) will be found in File>Properties (Except the Custom Pack Name and Tri-Pack checkboxes). 2. I got rid of the ugly picture that was on the right side that made you have to tilt your head and squint your eyes to read it! LOL! I made a new picture and placed it at the top. 3. I have also added an UnDocumented option that you can add to your ini file. This custom option will allow you to tell the Windows XP PowerPacker to do the nesissary things to create a Windows 2003 Pack. But I am gonna leave this at that. I am not going to put any checkbox/option or anything in the gui itself to do this because this is Windows XP PowerPacker and it is not meant to pack Windows 2003 ... Yet. But I am going to begin coding Windows PowerPacker (Instead of Windows XP PowerPacker) soon after Windows XP PowerPacker goes v1.0 Final. Just think of this as a sneak peak into Windows PowerPacker. To use this new Custom Option all you need to do is add this to your ini file: [Win2k3Version] 2k3Version= The 2k3Version must = L, D, S, A or B. Any of these letters will do the exact same thing (For now)... but they represent the Windows 2003 IDENT files... Example: 2k3Version=S 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. v1.0 RC4.1 - 08-08-05 1. I accidentally compiled the PowerPacker RC4 file the wrong way. I recompiled it the normal way and there is no problem now. Sorry guys. v1.0 RC4 - 08-07-05 1. Implemented a powpack.ini file to record your settings. This way everytime you open Windows XP PowerPacker it will remember how you had it setup the last time you used it. 2. Progress windows were changed to not always be on top. This way you can still use your computer normally without having Windows XP PowerPacker's windows being in your way as much as before. 3. Fixed some spelling errors. 4. Fixed the problem with WIN51IP and WIN51IC files getting copied over when they weren't needed. If you are creating a Windows XP Professional pack the WIN51IP files will get copied over, and the WIN51IC files will get copied over when you are creating a Windows XP Home pack. 5. More error checking implemented in the "Compile ISO" process. Now a window will pop up stating that you have successfully created your iso. If your iso was not created or ends up being 0 KB in size it will tell you it failed. v1.0 RC3 - 07-13-05 1. Fixed - When help file is opened I can not use the Main GUI window untill I close the help file. 2. Whenever certain windows are opened by powerpacker the main window will now be disabled so that users can not click on things when they are not supposed to. v1.0 RC2 - 07-10-05 1. Put a logo on the right side of the gui. 2. Placed Donation buttons in the program so users may donate to support the work on Windows XP PowerPacker. (The wife made me do it! LOL! ) 3. Integrated the capability to run custom written .bat scripts at different points of the packing process. v1.0 RC1 - 07-05-05 This release will be Release Candidate 1. Which means this may be the FULL version... if no bugs are reported. 1. I coded my own Dosnet.inf parser... so now I am no longer using BootFolder.exe. This version should work much better. Now there is so far no problems with createing the Boot Folder because my parser does not car if anything allready exists in the folder or if the file allready exists. It will overwrite if it has to. There should also be no need of MS Framework .net being installed... because that was needed by bootfolder.exe. My parser is completley based off the idea of bootfolder.exe by Nazgul... but my version is made to work better with powerpacker and it's needs. (Nazguls new version seems to be able to overwrite existing files now. So if you want to create a boot folder only... his tool is the best for the job!) P.S. A huge THANK YOU to moesasji for his patience and beta testing. Without his help I don't think I could have fixed all of these errors so soon. v1.06 - 06-28-05 1. Fixed a few minor bugs. (None that were harmful... just annoying.) 2. Coded the temp directory a little differently. 3. Added the newest version of BootFolder.exe v1.05 - 05-24-05 1. Integrated Nazgul's BootFolder.exe file to handle createing the boot directory. This method is much faster and creates a lot less steps. Now you do not need to go through the windows setup process to make the boot folder. Much thanks to Nazgul! v1.04 - 05-22-05 1. Fixed problem with Boot directory not copying to the destination sometimes. It should work every time now. v1.03 - 05-21-05 1. Added Embedded Help File. 2. Added Help File Button. v1.02 - 05-18-05 Fixed all known bugs. 1. I fixed the window size. It should now fit any resolution that somebody would use. 2. Made PowerPacker Set Attributes on all files to normal. 3. Added features to help make sure users do not point to incorrect directories. v1.01 - 05-14-05 1. Fixed problem with creating optimised ISO. 2. Added extra files section. 3. Added progressbars.

Make sure you have your OUTPUT: PowerPack Destination pointing to your files. They should have a folder called BOOT in it... and in there should be a file called loader.bin ... If it isn't there ISO creation will fail. Also if you haven't got enough HD space it will fail. As for the size of the files... That is because stuff at the root of your disk is not copied by default. They are files you will probably not miss. And if you selected to Exclude WIN9XUPG or LANG folders that also saves a lot of space. Hope I answered your questions. I am not sure if I understood you exactly.

What program is doing this? It is a false positive. I am getting sick of this. TrojanHunter does this too. I use Symantec and it never gives me a problem. I think some antivirus programs just don't work very well and they delete anything that is compiled in a certain way.

Another tutorial added. How to create a Windows 2003 Pack Unattendedly.

I have added an option that you can add to your ini file. This custom option will allow you to tell the Windows XP PowerPacker to do the nesissary things to create a Windows 2003 Server Pack. I am not going to put any checkbox/option or anything in the gui itself to do this because this is Windows XP PowerPacker and it is not meant to pack Windows 2003 ... Yet. But I am going to begin coding Windows PowerPacker (Instead of Windows XP PowerPacker) soon after Windows XP PowerPacker goes v1.0 Final. Just think of this as a sneak peak into Windows PowerPacker. To use this new Custom Option all you need to do is add this to your ini file: [Win2k3Version] 2k3Version= The 2k3Version must = L, D, S, A or B. Any of these letters will do the exact same thing (For now)... but they represent the Windows 2003 IDENT files... WIN51IL = Small Business server 2003 WIN51ID = Data Center Server 2003 WIN51IA = Enterprise Server 2003 WIN51IS = Standard Server 2003 WIN51IB = Web Server 2003 Example: 2k3Version=S Anyone who has played around with making a windows 2003 server SP1 multiboot disk knows it is a pain in the butt untill you know what you are doing. This little entrie in Windows XP PowerPacker makes that job simple. I have tested it with a Custom Pack Name (Which I recommend). You will have to edit BOOT\cdshell.ini manually to show your custom 2003 pack as a menu item. Also you can use the Tri-Pack option... but the DriverPacks may not work 100% And you will be stuck with the names for XP for the folder creation. For Windows XP Version and Edition... You just select anything.

Windows XP PowerPacker v1.0 RC6.2 Well... it is finally here! Windows XP PowerPacker v1.0 RC6.2 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!!! ================================================== Fixed in this release: Example: 2k3Version=S Version History: HERE ================================================== Please post bugs and requests in this thread... and be nice... this is my first Public App! ScreenShots: Main Window Properties Window Default Boot Screen 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

Hmmm... maybe Bashrat let this domain go? Or it could be hackers. WTF!!??! What is the point of hacking a site like that? Pretty lame I think.

I got rid of the ugly picture that was on the right side that made you have to tilt your head and squint your eyes to read it! LOL! I made a new picture and placed it at the top.