Siginet

Well... If I understand your question correctly. What you are asking is... can I use an OEM CD as my source files for every different pack. The answer is yes... as long as you put the setupp.ini file in the ExtraPackFiles\I386 directory. That way the file will be overwritten on each pack with the specific setupp.ini for each different OS. I have never tried this though... so let me know if it works. Also I am not sure the legalities of this. I would think if you own the disks there shouldn't be a problem. That is pretty normal. I think most programs do the same. Because when you type in a folder name it has no way to know if you are meening the folder or the iso. It sees the folder exists so it goes into the folder.

It does exactly that. Cdshell is the tool it uses for the boot menu.

Glad you got it working.

It should not be an issue with attributes. If it is please contact me. Because Windows XP PowerPacker is supposed to get rid of any read only attributes on all files. BTW... I don't think attributes should be a problem when creating a backup? It is weird that it makes backups of the other files and not that one.

If anyone wants to make custom Plugins for Windows XP PowerPacker currently it must be ran from a .bat file. Either the PREPACK.BAT AFTERPACK.BAT PREROOT.BAT or AFTERROOT.BAT. More info on how to use these are in the help file. Currently that is how you would run a plugin. But in v1.0 RC6 that will change. My idea is to have a "PLUGINS" folder in the same directory as Windows XP PowerPacker's executable. Inside there there will be folders for tools that will have support within WinXP PowerPacker. For instance there will be a "RVM_Integrator" folder that will be used for the new RyanVM Integrator. So far that is the only plugin that will have direct support in WinXPPP. I am also going to get rid of using CDIMAGE.EXE for compiling the iso and move towards using mkisofs.exe. (For legal reaasons.) But there will be a cdimage.exe plugin. Basically all you will have to do is download cdimage.exe and put it in a specified directory. Then WinXPPP will default to use it instead of mkisofs.exe. There will be a folder inside of the "PLUGINS" folder called "CUSTOM". That is where you would put custom made .exe .bat .cmd .vbs .msi plugins to have them ran at different points of the install. There will probably be an ini file used for asigning switches to each file. I have not begun writing RC6 yet... but this is what I am planning. If anyone has any other ideas you are welcome to suggest them. If anyone wants to make a plugin all you need to do is create your file and have it use parameters and call on other tools. Plugins will be helpful to implement other tools while making your Multiboot disk. Like automating compiling your RunOnceEx stuff... or Integrating tools like NLite, XPize, Windows Installation Helper Utility, XPlode and many other tools. This way WinXPPP can be a center to bring all of your favorite tools together while creating your multiboot disk. Because the idea is to have everything done 100% unattended. Tools that use Unattended parameters are the easiest and cleanest to make plugins for... but any tool can have a plugin created using autoit. It's just up to the members to join in and help create them.

@hyde Let me know if you like it or not. I am closing this thread now. Because I have started a new thread for the download.

I am just curious to know what people think of the program. Please only vote if you have actually tried the program out. Please post a comment regarding your vote if you have time. Thank you for any feedback. B) If you haven't tried it yet please do. Download/Rate Windows XP PowerPacker HERE ONLINE @ BetaNews.com

Well Windows XP PowerPacker has been downloaded over 11,032 times since it has been placed at Betanews.com! It has only been on their site for a little over a month. That's really cool! B)

LOL Newbie. The file shouldn't be read only. If it is then WinXP PowerPacker is not doing it's job. It is supposed to undo all readonly files. @Telenut Do you get the same error if you manually run the Run_me.cmd file from within an i386 directory?

Not sure what the Drvindex error is caused by. As for the winnt.sif file. I think I'll add the option to overwrite it. Thanks for reporting that.

Yes, I edited them and also checked them, but I will check it for a 3rd time <{POST_SNAPBACK}> You also have to hex edit setupldr.bin and you do have your boot files in a foloder at the root of your disk I assume? I suppose you could use Windows XP PowerPacker to create a windows XP load for your disk. As long as you are using cdshell for your menu. All you will manually have to do is add the entry into your boot menu. In the cdshell.ini file. Also another thing to make is to make sure you have these files copied to your disk... WIN51 WIN51IP (Only if it is a Professional disk) WIN51IP.SP2 (Only if it is a Professional disk with SP2) WIN51IC (Only if it is a Home disk) WIN51IC.SP2 (Only if it is a Home disk with SP2)

That's great to here. I'm not sure if PowerPacker is the reason it worked or not if you tried a regular disk and had the same results. But I am glad you enjoy the Tri-Pack option. It is a very good option that I have implemented.

Winnt.sif is not edited by powerpacker (yet). I plan on creating a plugin for that. The DriverPacks do edit the winnt.sif file though.

It should. But I have not had the ability to test it myself. Let me know if it works fine for you. I also plan on making a Language file so the program can be translated into different languages.

I fixed the tutorial. I posted a way that did not work correctly. Please try again if you tried previously.

LOL!

I'm glad you are still developing this project. I have been using it for a long time now and It works very well! I can't wait to see v2!

It will allow you to make 3 packs in one process. Unattended With DriverPacks Unattended Without DriverPacks Attended (Regular Install) There is a little more information in the help file.

The smilies aren't messing up the code. They are in a section of the code that does not matter anyways. I used the quote feature because i wanted to use color tags. If I used a code box I wouldn't have been able to use color tags. B) I fixed it for ya though.

Keep me posted.

deleted

This is very important if you wish to have everything unattended during the packing process. It is actually very easy when you know what to change. I will post my current RUN_ME.cmd file... but make sure you manually do the changes because later releases of the BTS DriverPack Base may change. OK. first thing you need to do is get rid of every instance of PAUSE The easiest way to do this would be... 1. Right click the RUN_ME.cmd file and "Open With NotePad" 2. Press CTRL+H (Or go to the tab EDIT and choose REPLACE) 3. In the Find What box type: PAUSE 4. In the Replace With box type: REM ### Siginet PAUSE (You must at least use REM but I add the other text so I can easily reference back to it later if I want to put the changes back to normal.) 5. Now click on the Replace All button. It should quickly make all of the changes thus far. 6. Find and replace each section below: ------------------------------------------------------------------------------------------------------------------------------- Find "GUIRunOnce" or "RunOnceEx" Options: Replace with: The choice I reccommend is in blue... but you can replace it with the red text if you wish. ------------------------------------------------------------------------------------------------------------------------------- Find "SET ROE_NUMBER" Options: SET ROE_NUMBER= SET /P ROE_NUMBER=" " IF /I '%ROE_NUMBER%'=='' GOTO REPEAT_CPLs_RunOnceEx Replace With: You may change the numbers in green if you wish. I think they have to be a 3 digit number though. ------------------------------------------------------------------------------------------------------------------------------- Find "KtD_ENABLE" or "KtD_DISABLE" Options: Replace with: The choice I reccommend is in blue... but you can replace it with the red text if you wish. ------------------------------------------------------------------------------------------------------------------------------- You can setup your RUN_ME.cmd file any way you like. The settings I chose above work best for me... and they save a lot of room on the disk. In my opinion those are the best settings. Good luck... and post here any questions pertaining to this tutorial.

OK... I am going to make this a sticky thread and I am going to post links in this thread that will point to other threads which contain some really cool Tips/Tricks/Tutorials on things you can do with Windows XP PowerPacker. This thread will get updated periodically so please check it often. -=[Tips, Tricks and Tutorials for Windows XP PowerPacker]=-How to Integrate Service Pack 2 with Windows XP PowerPacker. How to unattendedly use RyanVM's Integrator with Windows XP PowerPacker. How to unattendedly use XPize with Windows XP PowerPacker. How to edit the BTS DriverPacks RUN_ME.cmd file. (to make it unattended) How to create a Windows 2003 Pack Unattendedly. Here is some code you are welcome to put in your signatures to help promote Windows XP PowerPacker. [url=http://www.msfn.org/board/index.php?showforum=126][img=http://img386.imageshack.us/img386/5471/siginetsig1ce.png][/url] Tips I plan on posting in the near future... Tips and Examples of how to use Windows XP PowerPacker's many Unattended features. Tips and Examples of how to use the Extra Batch files. (PREPACK.BAT, AFTERPACK.BAT, PREROOT.BAT and AFTERROOT.BAT.) How to use HFSlip unattended within WinXP PP to integrate your hotfixes.

It could also be a possibility it was reading an old Powpack.ini file from RC4. I made a few changes to the ini file... so that may be the problem. I will test out the error you posted and see if anything is incorrect. I wouldn't doubt if some bugs are reported because the code was so drastically changed. BTW... to create a tri-pack you must have all setting inputed. You must have the unattended settings and the driverpack settings. Because a tri-pack needs all of this information to create the tri-pack. You will also notice that creating a Tripack is much faster than if you manually created the three packs. I will post a tutorial on how to make the DPs RUN_ME.cmd file unattended. Because that is important if you want everything unattended.

I thought I would ask if any members would like to help contribute to the Windows XP PowerPacker project by helping to create some graphics for it. Basically I would like WinXP PowerPacker to have an all round Windows XP feel to it. I need a new Boot Menu picture. Size needs to be: 640W 480H (RGB Mode) I also would like some banners made up that people can put in their signatures or on websites (To help promote it). Use your imaginations. Thanks to anyone who helps contribute. BTW here is some code you are welcome to put in your signatures if you would like to help promote Windows XP PowerPacker. [url=http://www.msfn.org/board/index.php?showforum=126][img=http://www.sig-inet.com/download/beta/IMAGES/WinXP_PP_Logo.jpg][/url]