Siginet

You can try www.logmein.com It is free to do most everything you need to do. And it is simple to use.

If cmdow is running then my guess would be some sort of batch file is stuck at that point. 13 min mark is when most of the switchless installer addons are installed. If any of them get stuck then it would cause a problem.

It is not an error caused by PowerPacker. You have done many modifications... it would be difficult for anyone to troubleshoot it for you. I use method 2 for the driverpacks though. On a multiboot disk I highly reccommend method 2.

I don't know vb very well... but I am good with autoit. Is there some sort of sleep command?

If the 150 cat limit is ever exceeded again I will put the option back into the integrator. But I don't see that happenning any time soon. nLite is a tool for slimming things down... so it makes since that nuhi leaves that option built into nlite. I was supprised to see so many people use that feature still. But it isn't a feature that I want to have in the integrator. It is possible however to create an addon for removeing the cat files if someone wishes to create one. But like I have stated... removing cat files does more harm than good at the moment. If someone creates an addon for removing cats they could find the needed cats and make sure they aren't removed. Removing cats does not save much space at all either. The integrator automatically compresses all cat files for you as it is.

It is completley different from all of those apps. It is for making multiboot disks. Whereas the other utilities are for slipstreaming/integrating/modifying one disk. PowerPackers main purpose is to compile all of your xp disks onto one disk. So instead of carrying 5 disks (XP Pro Corp, XP Pro Retail, XP Pro, OEM, XP Home Retail and XP Home OEM) you have to only carry one disk with all of them. You'll also have options to use driverpacks for each load or even choose to have it unattended or not. In the next release you will be able to choose from multiple winnt.sif files so you can use different settings for each load.

Thanks for the feedback! I am glad you enjoy it. The next Beta of powerpacker is gonna have advanced options that will allow you to use multiple winnt.sif files (Unattened Settings Files) for each pack you create. This will be great for those of you that install multiple systems and need different settings for certain computers. I am almost finished with RC8 Beta5 and expect to have a new release out sometime this week.

I'm interested. Thx.

Stickied!

Thx!

You can try my tool cmdhide.exe It is a little larger in size... but it will do the job for ya. Read the instructions on that site. My suggestion is to try using the Window Name option for hiding your script if cmdhide.exe yourcommandfile.cmd doesn't work.

Bug fixed when batch run without path.

I'll fix it tonight. lol **** bugs!

EnvVars fixed. Batch not running when no path is given fixed. Thx!

Yes I will fix these issues as well. Are you sure the batch is not called? What are the exact ways you are testing it? Thanks for the reports! It helps a lot when people actually reply and help out. I will be back on monday and I will fix this issue.

Thanks for reporting that. I have fixed it now. I also fixed the instructions on how to use it within your batch file. I forgot to mention you needed to use cmdhide /name:"MyWindowTitle"

A couple requests: Add the pssibility to create cab files with multiple files in them. People can just drag the files/folders over to the box and drop them in to create one .cab file. Or when you add shell support people can highlight and right click to create .cab file. Also... I recommend you add 7z.exe as well. It can expand .cab .rar .zip .7z .tar ... and more all with the same command line.

I use Windows Defender and Lavasoft Adaware Personal and I don't have any problems. I use Windows Defender to protect my computer and Adaware to run manual scans now and then. And I don't have to pay a penny.

Great job XPero! I like it a lot! It will definatly come in handy! Thanks!

cmdhide.exe v1.3 This small tool is useful for hiding ugly cmd windows. It might not be quite as effective as cmdow.exe but cmdow.exe is now triggered by antivirus programs as a virus. cmdow.exe is not a virus... but since the AV makers decided to destroy cmdow.exe I came up with this alternative. It works a little diffrently than cmdow. Here is how you use it: Most people will want to place the cmdhide.exe file in the system32 directory so they don't have to specify the path to cmdhide.exe in their batch files. There are 2 ways to use it. 1. Hide one Batch File Let's say you want to hide only one batch file. The batch file you want to hide is the batch you are going to start. In this case you would want to call cmdhide.exe with the title of the batch window. So somewhere in your batch you need to make a Title for the batch window like this: Title MyBatchWindow So now your Window Title is "MyBatchWindow" Now in your batch you will want to call cmdhide.exe with the window title like this: Title MyBatchWindow cmdhide /name:MyBatchWindow *Make sure you put your window title between quotes if it has spaces in it. Now when the batch starts you will see the cmd window for a second then it will dissapear. 2. Hide batches called from other scripts This is my favorite and will probably be the most used because it never flashes the batch window at all. It is hidden from the get go. Also it is very simple to do. From within your main script if you are gonna call any batch windows you want to hide all you have to do is call cmdhide.exe with the path to the batch you want to hide. Example: cmdhide "X:\path\to\mybatch.bat"

That looks awsome Rogue! I'm a fan allready! :

The reason it didn't work is you used the select all button in the DP Base. You must not use select all. Delete the tmp directory in the powerpacker executables directory. Delete your DPs_BASE.ini and mysettings.ini files from the DP Base directory and make new ones. This time do not use "Select All". Then it will work. It has been confirmed as a bug in the latest DP Base when used in API mode. Bashrat is fixing it.

Try the latest beta of powerpacker. It is in my sig.

Another thing that could cause this is... check your mysettings.ini Look in [settings] driverpacks = "select" if it says: [settings] driverpacks = "all" Change it to: [settings] driverpacks = "select" also... [selectDriverPacks] should list the DPs you are going to slipstream. We found a small bug in the DP Base that is somehow triggered by API mode. Which is the mode used when another program utalizes the DP Base like powerpacker does. I reported it to Bashrat and he is looking into it.

I have a strong feeling that this issue is caused by cmdow.exe being deleted by your antivirus program. Recently Symantec and a few other AV programs have been claiming cmdow.exe is a virus. Which we all know is a crock of sh!t. The DriverPacks use cmdow.exe. PowerPacker utalizes the DP Base unattendedly so that it does everything with no user interaction. What is happening is the DP Base is erroring out on not finding cmdow.exe and then quits before finishing it's job. I may work on a fake cmdow.exe that will work just like the real one and see if it will work instead of the real cmdow.exe. If it works I will post it for others to use.