Siginet

OK... I have moved The Tri-Pack checkbox and the Custom Pack Name checkbox back onto the main window. But I am leaving the Exclude UnNeeded Folders section in the Properties menu. 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 necissary 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 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 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. You just select anything for the XP Version/Edition.

Man this sux! I will email them again.

That's good to hear. Thanks for letting me know!

Very nice idea. This would wok out well for Windows XP Powerpacker as well if it was implemented into the next version of the DPs.

Do you have your BOOT folder at the root of the destination? It looks for a BOOT\loader.bin file.

OK. I will look at making a more toned down boot screen as the default. I think you guys are right. Hopefully someone will also make some screens as well. Like I said it is very simple to use your own instead of the default one. As for the check marks... I agree as well. I was wondering myself what I should do... should I keep them on the main gui as well or just put them in a menu. Well... I think since now I have more room on the gui I can still keep the checkboxes on the gui somewhere as well. I'll look at putting them somewhere in the main window.

In the BOOT\GRAPHICS folder there is a file called "splash.csi". That is the file that contains the boot screen. If you want to add your own you can create a bmp file following the directions on cdshell.org and compile it into a splash.csi file. Then in your Extra Root Files directory create a folder called BOOT and a folder within it called GRAPHICS. Inside the graphics folder put your custom splash.csi file. It will overwrite the default one that comes with powerpacker. You can follow these same steps to create your own cdshell.ini file etc.

I didn't like having the little Option checkmarks scattered all over the Main window so I went ahead and created a new File Menu that you can find at the top left of the main window. I got rid of the Help and About buttons as well and put them in the File Menu as well. Now all of the Options (CheckBoxes) will be found in File>Properties (Except the Custom Pack Name and Tri-Pack checkboxes). 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. I also made a new Boot Screen picture as well. 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 necissary 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 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 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. You just select anything for the XP Version/Edition. Release of v1.0 RC6 should be very soon now... So Stay Tuned!

You may have a hard time setting up the source with NLite. It's all trial and error. You may be able to get away with removing just those simple things. Everything you posted above can be done unattended except for the NLite portion if I am not mistaken. I don't think NLite has any unattended parameters yet. The order I would do it would be I would first create a PREPACK.BAT file with some code to slipstream SP2, Then I would add the script above for Ryans Integrator, I would then add parameters to have it slipstream XPize. I would put my hacked files in a directory that I would specify as my Extra Pack Files within Windows XP PowerPacker. Once I had my PREPACK.BAT file created I would just click on the button "Pack These Files Into The Destination". Everything would be done unattended for me. Except afterwards I would open NLite and remove components I didn't want. Nlite is usually best as the last step.

The wait is normal. It is caused by the DPs extracting like you stated. As for your driver issue I am not sure what the problem is. I am sure someone will have a good answer for you.

I am sure you could. Depending on what you take out of the Source files. But the reason to do it the way I posted above is for unattended purposes.

New tutorial added. How to unattendedly use RyanVM's Integrator with Windows XP PowerPacker

How to unattendedly use RyanVM's Integrator with Windows XP PowerPacker. If you want to Integrate RyanVM's update packs 100% unattended all you need to do is create a batch file called PREPACK.BAT and place it inside of the directory containing your "Extra Pack Files". (For more information on PREPACK.BAT or Extra Pack Files please reffer to the help file.) Inside of the PREPACK.BAT file you will need to put something like this: To break it down I color coded each section.1. The first section (In Black) represents the path and file to execute. In this case it is the RVM_Integrator_v1.0RC8.exe If the path contains any spaces in it you must put quotation marks at the beginning of the path and at the end of the file name. 2. The second section (In Green) represents the unattend switch. This must be /u or /U (You can put quotes around it as well... but you don't need to.) 3. The third section (In Blue) Represents the path to the directory containing the I386 directory. In Windows XP PowerPacker that will be the directory where the PREPACK.BAT file will get executed. So you will want this to be "%CD%". %CD% means Current directory in the batch file. So no matter where the batch is run from it will look at the directory where it is executed as the directory containing the I386 directory. 4. The fourth section (In Purple) represents the path and filename of the RVM_Update*.cab file you wish to use. (Again make sure you use Quotes if your path contains any spaces.) 5. The fifth and final section (In Red) represents the path and RVM_Addon*.cab file(s) you will be using. If you wish to use more than one Addon then make sure all of the addons reside in the same directory. If you are using 2 addon packs the fifth section would look simular to this... Make sure you look at the above example very carefully. Each Addon.cab file has a | (Pole) in front of it to seperate each Addon.cab. Also the path does not have a \ (Backslash) at the end of it.The easiest way to make sure you are getting your syntax correct would be to open the exe file itself, browse to the files and select them. In the inputbox just copy the text and paste it into your batch file. *Note* The best thing to do would be to create new source files with the RyanVM Integrator and just use those source files through WinXP PP. But for those of you that do not care how long it will take to use the RVM Integrator on every pack you create you can use the tutorial above. Hope this helps somebody.

Weird that you are having an issue. No one else has claimed to have had this issue. Please check you PM I sent you. I need some more info from you so I can better troubleshoot your problem.

Can you post some more info about your stuff. You shouldn't have an issue. Is there a chance that the iso you are trying to create allready exists and the file is in use? What is the path you are putting your iso in? The more info you give me the easier it will be for me to figure out your problem. Usually this isue is caused by not enough room on the HD... but you stated you have 100GB free space. <{POST_SNAPBACK}> Try rebooting your computer and try again.

Can you post some more info about your stuff. You shouldn't have an issue. Is there a chance that the iso you are trying to create allready exists and the file is in use? What is the path you are putting your iso in? The more info you give me the easier it will be for me to figure out your problem. Usually this isue is caused by not enough room on the HD... but you stated you have 100GB free space.

I didn't say it was perfect yet. I said almost there. Actually he is only getting very little reports of problems now. Which goes to show that the majority of everything is working. The biggest issues I see that are reported are the NVidia storage problems... which I stated above. He has also fixed some of it. So he is getting closer. He is trying his best... and I just wanted to point out that everything he has been doing I do appreciate.

Wow Bashrat! It looks like you've almost got a flawless set now! Just a few more fixes with the mass storage I guess. I haven't had many problems at all. Except with the realtek sound drivers every once in a while... but that isn't to hard to bypass. And it happens very rarlely. I am gonna donate somethin' to ya. You definatly deserve it! Anybody else with me? I feel bad I have been using your DPs for a while now and neverdonated anything yet. I got a little extra cash to shoot your way. Nothing much... but I know every little bit helps.

Glad you enjoy it. It will only get better... I'm just getting started!

I agree dell is the best (for customer support reasons). But my vote went to HP (should have been a choice for HP/Compaq since they are the same company). The reason I voted for HP is the fact that dell has a contract with Intel... so as of now you can't purchase any AMD computers from dell. Mainly the Athlon 64 which kicks intels a**!

Nice tip. So how would I answer all of the questions? I will play around with it. I deleted the post of the cmd file You are right... there was no need.

I sent them an email to fix this false reading.

That is definatly a false positive. Some applications have false readings... especially on programs that are fresh and new... like Windows XP PowerPacker. What program is that, that gave that reading? I use Symantec Antivirus and I have no problems.

Yes I do want to implement something like that. I am pretty busy coding Windows XP PowerPacker itself right now... but anyone is welcome to write a plugin for WinXP PowerPacker to do something like what you have requested. Once I get the program fully released I should have more time to create plugins.

I am going to work on adding BartPE to v2.0 but I have no access to WINPE. Maybe someone can make a plugin for WinPE. As for now you will need to manually create your WinPE pack... then save all of the files to the "Extra Root Files" directory for later installs.