Siginet

BartPE is legal to use though, as long as you use your own copy of Windows XP/2003

I'm not sure if I understand you. This program does not need to be installed. The only cd's you would need to swap would be different versions of the OS. Can you try to explain in more detail?

I think what he is asking is... cdimage.exe helps us make optimized ISOs so that we can make multiboot disks with many simular OSes because it puts multiple refferences to files which are alike in the TOC so that the files only reside on the CD once even though it looks as if they are there multiple times. It is a good question... one that I am curious to know as well. Because making a multiboot disk like this hogs up a lot of HD space.

Check this site and make sure you do this. http://staff.stir.ac.uk/thomas.speirs/Bart-PE_RIS.htm

It depends on the plugin you are using to scan. I know there is a plugin for adaware that uses another plugin called runscanner which allows the registry to be pulled off of the system so that you scan it instead of the PE disks registry. Sometimes within PE you can get rid of spyware that won't delete within the OS because of permissions. So sometimes it is better done inside of the PE environment. But it is still good to do a scan inside of the OS aftwards... just incase something was missed. I find that some things tend to be buggy in the PE environment sometimes. So it is always good to be careful. But I belive that the PE environment is definatly a good way to scan. Especially if the computer is inaccessibale due to spyware/viruses that stop it from booting all the way. There are also many other tools which are useful in the BArtPE Arsenal.

With compname.exe you can have the computer named anything + the motherboards serial # or MAC ... It ensures that every computer has a different name. (Most of the time)

The recovery console does not do the same type of repair that they are talking about. But that wasn't a bad idea.

Just thought I would mention that I just realeased PowerPacker v1.03 I have made a help file to help new users learn how to use the program.

I just added PowerPacker v1.03 to the first post. There were no changes to the program except for the new "Help" button which opens up a quick help file I made to make it a little easier to understand the program. I still need beta testers.

You could have applications on a usb drive. Then have your runonceex.cmd or guirunonce run a batch file that will look for a specific file that you would have on your thumb drive so you can create an env variable to point to the usb drive for installing apps. Or you can make your install open the cd tray and ask for a second disk.

OK... Update has been added to the download. We are now at Windows XP PowerPacker Beta v.1.02 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.

I actually allready posted this in another section of the forums... but I think it should be posted here as well. It is an autoit gui I wrote to help people create a MultiBoot cd/dvd with multiple copies of Windows XP. It also has the ability to install BTS Driverpacks (Which you can read more about in the Drivers section of the forum.) I am going to work on adding options for slipstreaming and adding RyanVM's WinXP updates into it as well. As of now it is still in beta... but it is comming together well. I need some experts (and newbies) to help me test it out, give me some ideas and point out any bugs. Eventually I would like to add as much as I possibly can to it and maybe get it to do a lot of the things that people come to msfn.org to learn. So who's with me??!? Here is the original post... Windows XP PowerPacker Or you can find it in my signature.

I will put a halt on uploading my most recent update until I fix the Attributes problem. I should be uploading a new version tonight.

I'll double check that note. But I am pretty sure that the program does not keep any file attributes when it copies them to the destination. Edit: Looks like you may be right! Thanks a lot! Now I will make the program put all attributes to normal on the files after they are copied. Good call.

Works like a charm. Thanks a lot!

Every error that could pop up halts the program. It isn't possible for the program to do what you are stateing. It must be a problem on your end if that is happening. Can anyone else produce these multiple errors that can not be read?

Yeah that was the bug I fixed in the next version. I made the window too long... in the new version the format is a lot different. No need to apologize. I'm glad you posted. I wish more people would help me test it for bugs. Let me know if it works out for you or not.

Could you specify the error you get? The error should say a filename or something in it. That would help to point you in the right direction. It sounds like you have it working... but one of the drivers aren't loading right. If you aren't installing the Mass Storage drivers this doesn't happen often. The times when I have encountered a problem the most, (without mass storage drivers) is on some Dell computers. I get the portsys error. This error is caused by a sound driver. You can read more about it in the DriverPack Sound section. Allthough I haven't been getting that error latley I have seen a few others claiming to have had a problem with it. Don't give up... you are almost there.

@Bashrat I tried to PM you but it seems your PM Box is full. I just wanted to ask if the cmdlines.exe file I made worked out ok for you? I just noticed that if it is called from a batch file within a different directory it doesn't work correctly. Did you find a way to use the cmdlines.exe file? I did rewrite the cmdlines.exe file to work correctly... just let me know if you still need it. Is there any way we could chat?

I will be putting another update online sometime tommorrow. It fixes the problem of being too long on 800x600 resolution. Actually the window is layed out a lot differently. I also added some code to have it check to make sure you point to the correct directories on certain browse buttons. This will probably fix the errors others were getting. The way the program was made was a little confuseing on wether you point to a directory or a directory containing a certain directory and I think that may have been what caused the errors. Once I put together a help file it should make things more clear.

For best results right now try making a disk without the mass storage driverpack. Some Storage drivers do have problems. (Not many anymore but their still are some.) Then install the sata drivers seperate. I know it isn't exactly what you wanted... but everything isn't 100% perfect yet. Hopefully soon they will be.

If the hex editing part did not finish there must be something not copying over to your destination quick enough. So far I haven't run into this... but I have not had the chance at testing it on many computers yet. Is the boot Directory copying over correctly? The boot directory would be a folder named XPPC or something simular (Depending on what type of pack you are createing.) on the root of your destination. Not in the "ROOT" directory.

When and how do your regtweaks get installed? What method are you using to install the DPs? and are you using GuiRunOnce or RunOnceEx?

When did you get these error messages? It is supposed to pop up an error if you did not do something correctly. If it wasn't an error from something you've done then I need to fix it. Because when I use it I don't get any errors. I need to know what error you got.

It is meant for use when someone allready has their own RunOnceEx.cmd file or any other file being ran inside of cmdlines.txt. It just assures that BTS_DPs_ROE.cmd is the first batch ran so that any other batch that is ran that sets the title will overwrite the BTS_DPs_ROE.cmd's title. It's not a bug that is gonna ruin your install it is just meant to keep your previous title in the RunOnceEx install point instead of the title that BTS_DPs_ROE.cmd sets. No it is meant to be simpler... but testing and fixing bugs comes with the teritory. I haven't seen anything stateing that these are bug free as of yet.