Siginet

Actually the RVMIntergator needs some gfx as well. I'm not sure what sizes... but I can allways adjust things in the gui to fit. Any of my programs I'd request to have "Siginet Software" somewhere in the gui if possible. Thanks again!

Wow! Thanks! I like them all. Sorry I didn't reply sooner... I just noticed your reply here. I will put them all to use somehow.

I just spoke to Bashrat. He has changed the site a little. If you go directly to www.driverpacks.net and browse through there it works fine. But if you follow the link in his DriverPack Base Thread it is wrong. So if anyone else has a prob that's what it is. He says he will try to fix it tommorrow.

I was about to download the latest DP stuff... but for some reason I can't get to the download pages? It just sends me back to the main menu. Have I been Banned Bashy?

hmmm... I can't seem to figure out how they were able to run the file. Whenever I try to do it nothing happens. I don't think this file actually runs anything. Maybe another file checks this inf for that info to run the file?

lol... yeah adding PE doesn't leave much room for programs in PE. Especially on a CD.

Completely different program. I never understood why some sites said this was an alternative to nLite. This is for creating Multiboot Media. So you can have different versions of XP on one CD or DVD. Instead of Carrying 5 or more CD's/DVD's around with you... you can pack them all onto 1 disk. Also it utalizes the DriverPacks as well... so you can add all needed drivers. This way you have the ultimate "Universal Windows XP Disk" that is compatably for just about any computer. Wether you need to install XP Home OEM, XP Pro Retail, XP Home Retail, XP Pro OEM, XP Pro Corp... and the list can go on. With Nvidia Video Drivers, Realtek Sound Drivers... blah blah blah.... and so on. Also this program can be used as your center for creating your disk. It can utalize any program that has unattended switches. Like the RVMIntegrator (Scripted by yours truley), XPize, NLite (Once nuhi adds his unattended stuff... and so on. This project is mainly for XP... but the full project will work for all NT OSes and PEs.

Now there is a BOOT.ini file that basically you use to point to another ini file or you add reference to the boot file in it. For instance here is the new BOOT.INI: [MenuItems] : C:\; Boot from drive C: : \Boot\PRO.INI; Install Windows XP PRO \Boot\HOME.INI; Install Windows XP HOME ;END : :reboot; Reboot :PowerOff; Power Off [MenuOptions] BGColors = 00, 80, 80, 80 BGSymbol = 32 TopText = BottomText = MenuPosition = 02, 05, 76, 16 MenuColors = f9, 9f, 1f, f0, 0f, fd, f9 MenuBorderStyle = 5 MenuShadowStyle = 2 MenuTitle = Boot Options MenuDefault = 0 MenuTimerLabel = Time remaining: MenuTimer = 5 You can either point to another INI file like this: [MenuItems] : C:\; Boot from drive C: : \Boot\PRO.INI; Install Windows XP PRO \Boot\HOME.INI; Install Windows XP HOME \Boot\BART.INI; Initiate Preinstallation Environment ;END : :reboot; Reboot :PowerOff; Power Off [MenuOptions] BGColors = 00, 80, 80, 80 BGSymbol = 32 TopText = BottomText = MenuPosition = 02, 05, 76, 16 MenuColors = f9, 9f, 1f, f0, 0f, fd, f9 MenuBorderStyle = 5 MenuShadowStyle = 2 MenuTitle = Boot Options MenuDefault = 0 MenuTimerLabel = Time remaining: MenuTimer = 5 Then in your new BART.INI you would have this: [MenuItems] \BPE1\SETUPLDR.BIN; BART Preinstallation Environment \XPE1\SETUPLDR.BIN; XPE Preinstallation Environment : :Return; Main Screen [MenuOptions] BGColors = 00, 80, 80, 80 BGSymbol = 32 TopText = BottomText = MenuPosition = 02, 05, 76, 7 MenuColors = f9, 9f, 1f, f0, 0f, fd, f9 MenuBorderStyle = 5 MenuShadowStyle = 2 MenuTitle = Initiate Preinstallation Environment MenuDefault = 0 MenuTimerLabel = Time remaining: And I want to customize the [MenuOptions] for PowerPacker as well. I was thinking a green theme for the HOME.ini file and a blue theme for the PRO.ini file.

Actually you are 100% correct. I replace winnt.sif with the name of the folder like: wXPPC.sif. Pretty cool trick. It opens many other doors that will be simple to implement to powerpacker. Like the option to use multiple winnt.sif files for the same pack. BTW... has anyone noticed that the filesize of PowerPacker is about a third of the size of RC7.1. Actually in the new beta it should be even easier. All you should have to do is add reference to the setupldr.bin file in the new boot menu ini files. I haven't tested yet... but that's all I think has to be done. I confirmed it today. All you have to do is give reference to the setupldr.bin file. But when PowerPacker has support for PE I want it to be able to add multiple copies of PE on a disk and they share the same Programs folder.

Actually in the new beta it should be even easier. All you should have to do is add reference to the setupldr.bin file in the new boot menu ini files. I haven't tested yet... but that's all I think has to be done.

I uploaded Beta3. Beta2 .... What Beta2?

That issue would not be caused by powerpacker in any way. I'll try to release beta 2 today.

Everyone should bow down to the master Bart! He is the man!!! Great to have ya here Bart. Your PEBuilder is magnificent!

Sorry guys... I've been kinda busy latley. I think I am ready for beta 2... but I want to run a few more tests. I'll try to get the beta out this weekend. It will be kind of the same as Beta1 but with all of the known bugs fixed. Hopefully I will have some time to add some more stuff to it soon.

I like it as well... so if someone finds the code and posts it here I will try my best to implement it.

I fixed a few bugs last night... so I should be releaseing another beta soon.

Actually it might be better to just change: %INE% I386\RVMUPPCK.IN_ ( To: %INE% I386\*UPPCK.IN? ( That way it will look for any RVM style UpdatePack.

That seems to be a driverpack issue. Try to use the driverpacks without powerpacker and see if you get the same problem. If you do try to remove any read only attribs from your i386 directory then try again. Powerpacker should be removing the read only attribs though. BTW try deleting the powpack.ini file. I accidentally implemented the powpack.ini that I use in this beta.

I'm not fixing it. I am moving toward enhancing it. As of now... with this beta the enhancements are mainly just speed and looks. Any changes that I have made are for future stuff that the final release will be capable of. Belive me... I know what you mean about if it aint broke don't fix it. I have a bunch of batch files and ini files that I use between the integrator and powerpacker and my batches are pefect... but with the new changes in the integrator my old batches and ini files are useless. So even I hate the changes so far. But when you see where the changes are going you will appreciate them. The new powerpacker will have a lot more customizable capability. Just trust me. If you like the old powerpacker... you will love the new one when it is complete. I am gearing toward making powerpacker and the integrator to actually work together better than ever. One usefull enhancment so far is that you can save/load your settings files.

Beta1 of RC8 can be downloaded here: http://www.msfn.org/board/index.php?showtopic=72041

Yes in the final cdimage.exe will not be used. But can be used as a plugin. I will look into the Extra Pack error you specified. It wouldn't suprise me if it has a bug. That is basically the only option I did not test. I will also place a clean powpack.ini in there as well... that was an accident.

Sorry I forgot to mention that a couple of changes were made that makes an old settings file not work correctly. It is best to use a new settings file... or make sure you re-select all of the options. Especially the Extra Pack/Root files sections. So ... are you still getting an issue with the boot directory creation? Is the progressbar working correctly? Do you think I should make the progressbar a little thicker? I made it thin just to be different... but I'm not sure if it looks ok or not. Coding it to show progress for cdimage.exe was a real pain but it seems to work well so far. There's still a lot of coding to be done before the final release... but I couldn't wait to show off what I've done with it so far. Thanks for giving me some feedback! I appreciate any feedback. It actually gives me an insentive to code more when people actually show an interest. Seems like ever since I came out with a version that worked very well people didn't give much feedback anymore. Almost makes me want to put bugs in it on purpose! LOL! J/K!

OK... I decided to release a beta of v1.0 RC8. So here is Beta1. The beta releases are mainly meant for those of you who are somewhat familuar with previous releases. The help file it contains is old and has not been updated. There have been many changes to the coding and xp powerpacker is now much faster and it is about half of the size. XP Powerpacker also has a new progressbar to show you progress. There are many new changes that I will explain later... but for now I just ask that members try using it and letting me know how well it works for them. Also the unattended parameters have changed a little bit. I am going to be changing the unattended parameters completley before the final release. The changes so far are simple: Parameter1 = The path to your settings file. Parameter2 = The type of unattended process to perform. (Either: -PACK or -PACKAGE) Parameter3 = The disk lable you wish to add to the iso. (Only to be used with -PACKAGE) Parameter4 = The path and name for the iso file. (Only to be used with -PACKAGE) Download Beta3

The .dat files will no longer be needed because BCDW will allow us to boot to the setupldr.bin file instead. Which allows us to have multiple setupldr.bin's for each boot folder. XPPCldr.bin, XOPCldr.bin, ROPCldr.bin... etc... Each new *ldr.bin file will be hex edited to be told to use a different winnt.sif file as well. wXPPC.sif, wXOPC.sif... and so on. I am not sure when there will be a new release as of yet. Sorry... but I have had a lot of things happen recently in my life that has slowed down my time to code again. I may release a beta version of what I have so far. But it is only to be considered beta. It seems to work very well and very fast... but there is still a lot to be added. With the new idea of how the winnt.sif file is used I need to change the way you select your winnt.sif file as well. Instead of selecting the folder containing the winnt.sif we will need to select the winnt.sif file itself. Which will cause me to have to change a lot of code throughout the scripts. There are going to be so many changes that I have decided to not make this version fully backwards compatable with the older versions. Which means you will need to make new settings files and even the unattended parameters will change to make them simpler to use. So yes I would advise recreating your disks when the new version is released. Sorry... but it will better the project. So these changes will be needed.

Actually I think you can use a winnt.sif file that you made for your unattended without driverpacks. OemPreinstall = "no" Then when the driverpacks are installed to the other selection with driverpacks the driverpack script files will automatically add the OemPreinstall = "yes" selection to the winnt.sif. But I am also adding the capability to create your own multiple boot options for specific boot folders utalizeing different winnt.sif files. So now it will be possible to have many different ways to install the system.