Siginet

Autoit3. Use the Sleep() command.

378 Yrs old! lol J/K 27 and a half

Hmmm... I hope we find a solution to this. It would be great to be able to multiboot Win64 on my disks. I will do some digging myself as well. Thanks to everyone involved!

There actually allready is a winnt.sif selection. It is the first option when you make an Unattended Pack. Personally what I do is I have a folder on my harddrive called "winntsif" under that folder I have 2 folders "Home" & "Professional" then within those folders I have a folder for each different edition. (Corporate, Retail, OEM). If your question is... is there a way to have multiple instances of the same pack which allows me to pick different unattended setups? The PowerPacker program does not do this right now... but I have a few tricks on doing that... and I may create a plugin for that. I don't want to add too many features to the main PowerPacker window itself... because then people may get confused. But... there will be many plugins made to do many things that you don't see in the main window. Also when PowerPacker has more than one thread to troubleshoot, ask questions, post comments... etc... etc... I will be able to post a lot of tutorials and tricks that can be done.

It is completley different than NLite. It doesn't do any functions that NLite does. What would make you think it is like NLite? I specifically stated earlier that the program does not do any NLite features. What specifically do you mean is like NLite? If you don't mind me asking.

Well... since I have added the capability of running .bat files at different points of the packaging process... it opens a lot of doors. Later I am going to make it capable of running custom .cmd, .exe, and .vbs scripts. Then I will work on coding .exe plugins that will do extra thing... also other users can create plugins for it as well. The possibilities are almost unlimited. I am even planning on scripting an autoinstaller that will install all exe files in a given directory at the runonceex portion of setup. This way it will make it easier for people to create application installs for their disks. I don't know about powerpacker doing everything that NLite does... NLite is probably the best tool out there for slimming an XP disk down. I don't have enough knowledge to do that. But if NLite ever has (or allready has) unattended parameters in it... it wouldn't be to hard to implement a plugin to call NLite to do things as well. If all else failed.. autoit is good at automating things that normally aren't automated... so someone could actually utalize NLite in some way no matter what. I do intend to have an option to do minor NLite types of things like deleteing the "LANG" folder and the Winntupg" folders etc... but that is about as far as I may take that. There are many possibilities... and I intend to take powerpacker as far as I can... without adding too much to the main window itself. That is why I like the idea of custom plugins. I think msfn.org has bigger plans for powerpacker in the next week or so... from what I have heard. Hopefully we will have a bigger place to discuss powerpacker so that we will have a more organized way to build on it... and I can post tutorials and tricks for everyone.

Windows XP PowerPacker v1.0 RC3 Released Tonight. Enjoy!

It will work with NLite to a certain extent... as will a lot of things. But some things that can be removed in NLite are things that you need for the driverpacks to work... or RyanVM's pack, etc... etc...

Bashrat can you add me to your msn messanger. I have you added to mine but it never sees you online. Maybe you did not recognise my email and you denyed it? [Removed] is my msn messanger account. My msn email has been removed... but it is in my profile.

I think you will like it Bashrat. It is actually great for testing out the DPs as well. This tool was actually built for the DriverPacks to begin with... and it became more. You of all people are the one I need to test it. I also hope we can MSN Message each other soon. So I can keep my tool compatable with your driverpacks if you decide to change the way they install.

Yes I got lazy and I did not add that feature yet. It will be added later. I may also add a .ini file as well. This way when you open PowerPacker it will remember your last input.

This bug has been fixed in Windows XP PowerPacker v1.0 RC3 This bug has been fixed in Windows XP PowerPacker v1.0 RC3 The maximize button is now disabled as well. And a few other minor but annoying bugs fixed. Windows XP PowerPacker RC3 should be released sometime tommorrow. Once v1.0 full is released I will begin writeing plugins.

I think bittorrent would be a good idea.

I have never seen this kind of error. My guess is it must be some sort of computer side error. The program was built and tested on WinXP SP2. I have never tested it on SP1. All I can think is check on anything that may block the program from doing things. Have you ever had viruses on your computer or spyware? That error seems like it may be caused by a damaged system. I could be wrong... but I have no idea why you would get that kind of error. Please keep me posted. When you go to package an ISO you must only point to your destination. All of the other options are not needed. But it needs to know what to package. Also... make sure you have enough space on the drive you are creating your image on. It must have enough space to create the full size of the disk before optimisation or cdimage will turn off.

That is great news! Thanks for the info Gouki!

Yes I noticed that it does not disable the gui in the background and that is a small bug that I needed to fix. I will make sure that I fix it for the next release. Also the gui is not disabled during the packing process which I need to fix. Thanks for reminding me. I didn't even think about the issue when using the help file. Both good points. Thank You very much! Thanks for this mirror I appreciate it a lot! It will definatly come in handy!

Speaking of which, I'm still waiting on a PM from you <{POST_SNAPBACK}> LOL! Checking the RVM site now Sensai!

Actually the latest release of PowerPacker just about does all of this. The new version of powerpacker allows users to run custom scripts at different areas of the Packing process. Which opens doors to Slipstreaming service packs... calling Nlite... Integrating RyanVMs packs... etc etc... so on and so fourth. I have nothing against your program at all... as we are all coders. Just wanted to point out that... that is actually what PowerPacker is intended to do. The current version has only XP options... but further releases will integrate other versions. All I have to do is add another radio button or two.

Should work just fine.

Your request is actually a good one... but there is no "stable" release yet. All releases are known to have bugs in them and that is why we keep having updates... to fix these bugs. Also in the meantime Bashrat puts in the new drivers to keep them up to date. Whenever sombody comes across a newer driver which does not work... Bashrat downgrades to an older working one. It is difficult to get the project to work 100% on every computer. Alas... what works on one computer may not work on another. So you see... it is almost imposible to make a "stable" release at this time. The DriverPacks are a work in progress... and it is progressing better than anyone imagined. It was an impossible project that Bashrat has done a lot to make possible. My suggestions above were not to offend you... but let you know of a way you can make a semi "stable" release using the newest DriverPacks. It isn't very hard... it's actually quite easy. If you need any help just ask me or any of the others.

OK everybody... I have finished codeing Windows XP PowerPacker 1.0 RC2! This one I did not have to fix any bugs... I just added some cool features, a logo to the right side of the gui, and some donation buttons (Just incase anyone is feeling thoughtful. The cool new features are by request. I have added options to run your own batch files within different periods of the packing process. Here is a quote from what I have added to the help file: These options are great for making everything unattended. You can now use windows XP SP1 as your source and have a batch file which integrates SP2 to it before it integrates the drivers etc... Also... people can release batch files that they have made as addons for PowerPacker. For now that will be fine... but in a later release I will make it so you can run any kind of file (Not just a .bat file). Then I will make extra tools that you can use with powerpacker (like integrating RyanVM's XP Updates). I would upload this fine release for everybody now... but it looks like something is wrong with my ftpserver and it doesn't allow me to upload right now. So hopefully the new version will be released sometime today. Does anybody have a little extra webspace that I can upload this to as a mirror site?

That is usually used when copying text to another file. That is so it won't look at it as an Environment Variable. It will copy it over with one set of %%.

You should have a "D" folder that you place all of your subfolders in which contain your drivers. When you are finished you need to 7zip that "D" folder. This way when the files are extracted they are extracted to the root of the systemdrive in the "D" folder. The "D" folder is the root directory of all of the DPs. So for instance if you were making a LAN pack... you may make a "L" folder inside of the "D" folder, inside of the "L" folder you have your subfolders with drivers in them. Now 7zip this up starting at the "D" folder. That will finish your own LAN DP. Then you follow the same steps for the next DP. As for your second question... I don't know how that all works yet.

The bsod you received... I'm not sure what caused it. When did you get this error? Did you use Nlite at all? Did you integrate anything into the xp files? What type of XP are you trying to install? With or without DPs? Please post as much information as you can. Thanks.

I made this tool based off of a script that Bashrat originally made. I basically made this to help troubleshoot issues with the driverpacks. If you have installed a system using the driverpacks and some drivers did not get installed please run this tool on your system after you install the missing drivers. Let us know which drivers were not installed and post a link to where you downloaded the needed drivers. I think if everyone does this it will help out significantly! I will continue to add to this tool upon request... as long as I feel it is needed. @Bashrat can you sticky this thread somewhere that you feel is suitable? BTW... is there any other info that you feel is important for you to know about their system? P.S. An update I will soon make to it is.. I think it should allow you to tell it where it will save this information. This way the tool could be run from the cd. As it is now it saves the info to a txt file created in the same directory that the exe is ran. Get_HWIDs HERE