Siginet

Sorry I must have mis understood your issue. Your best bet would be to get rid of any spaces in the paths to anything. Anyone else having an issue? I know I ran many tests myself and fixed any bugs I could find. But it is possible I missed something. That's what I need everyone here to verify for me. I can't keep coding powerpacker if no one gives me feedback. I have no idea if people are successfully able to use it or not. All I know is it works for me.

It shouldn't use the multipack feature of the DP Base. Just use the regular Disc feature.

The next integrator... v1.3 will detect all versions of windows Pro Corp, Pro Retail, Pro OEM, Home Corp, Home Retail, Home OEM, Media Center, and so on. Eventually I will implement the code into powerpacker as well. But we are still in beta. So there is still a lot to be added. But since v1.0 RC8 has so many changes in it I decided to release a bunch of Betas so that users can still use the new features and not have to wait so long for the final RC8. I also plan on adding an advanced feature to allow a user to use multiple winnt.sif files for a pack... which I think will be an awsome new feature.

Help doesn't work because the actual help file doesn't exist. Siginet hasn't updated it in a while (last update I guess was for 1.0 RC5 or something). It will undoubtedly be packaged into the final RC8, but for now, the actual executable file contains only the program and does not extract anything (except writing a powpack.ini settings file). Sorry, I know I'm not Siginet, but I can still answer your questions. PowerPacker doesn't have the ability to detect the type of source you have, but in your case, you should select 'corporate'. It doesn't really matter for the actual packaging, but the options are there so that PowerPacker activates the correct sections in the boot menu files (it also tells the program what to name the folders).The RyanVM Integrator is maintained by RyanVM (big surprise !). It is not packaged into WXPP though, so yes, you need to download it separately. WXPP can in some way communicate with the RyanVM Integrator, but you need to wait for Siginet to explain this because I am not familiar with that portion of the program. Hope this helps ! You were almost correct about everything... except the RyanVM Integrator. I am the creator of the RyanVM Integrator... and I do manage it. I made the integrator for Ryan because I enjoyed his UpdatePacks so much. A lot of the integrator was made by Ryan telling me what he wanted it to do and I coded it to do it. Then I added my ideas to it as well. A lot of the addon capabilities were designed by me. What I do is I use the RVMIntegrator first... but in the advanced tab I select Run External File, Browse to PowerPacker, then in the parameters box I put: "X:\Path\To\A\Settings\File\powpack.ini" -PACK This will utalize both programs. First integrating everything with the integrator then calling powerpacker unattendedly and packaging everything. Then you can use the Run External File feature in powerpacker as well to call the integrator in the same way: Select the integrator file, Then in the parameters put this: "X:\Path\To\A\Settings\File\integrator.ini" /INTEGRATE This is a cool way to chain link the programs together so everything is unattended. As for PowerPacker detecting the different types of OSes... It will in a later version. The next integrator allready detects the different OSes for you... and I will be implementing that code into powerpacker as well.

Actually I don't remember if I fixed it or not. Let me know if it doesn't. But I think I fixed it a while back when I first started coding Beta4.

So am I to assume there are no bugs? Come on guys... I need some Beta testing.

Ok folks... I've just finished coding Beta4 and as promised... I've added support for the new DriverPacks Base. *Note... in order for the DP to work you must first install the new DP_Base.exe and create a mysettings.ini file through the DP Base. Once you have made your settings file you just select that settings file in the DP section of PowerPacker. Also a major change you will quickly notice is the new "Advanced" tab. A new advanced feature is the "Run file upon completion" area. This feature is allready built into the RVMIntegrator and now is available in PowerPacker as well. It is very usefult to chain link multiple packaging processes of powerpacker together... or even chain linking powerpacker and the RVMIntegrator together. It is made to help simplify the unattended disc creation. Once you have all of your settings files made for all of the programs... you just start the process and the rest is unattended. There will be more "Advanced" features added... but this new beta should hold you guys/gals for a bit before Beta5. Please report any bugs you may find. Download @ Siginet Software Enjoy!

Coding of Beta4 is comming along well. It's release will probably be tommorrow!

I'm starting to feel better. I actually did some coding for the RVMIntegrator today. So I should get a chance to start coding beta4 of the powerpacker soon. Thanks for being patient!

There have been complications with a pinched nerve in my neck that have caused me to have to postpone coding Beta4. Sorry for the delay everyone. As soon as I can get well enough to be able to sit at the computer long enough I will put something together. I have been getting cervical injections in my neck for the past month and I am currently at the second out of 3 shots. The second shot had complications where the hole did not seal properly which is causeing me extreme headaces and nausia when I sit or stand for more than a few mins. It isn't as serious as it sounds and it will be fixed hopefully tommorrow... but it hurts like hell!

OK... it's been a long time since I messed with doing this. I see now that the download for sort2cab.zip is broken. I got newsort2cab.zip... but it isn't working for me. I forget what the tabledirs.lst and xmlfiles.lst files should look like. currently I have them both looking like this: OWC10 OWC11 PRO11 Is that correct? I keep getting an error settings.ddf not found. also... I am trying to add the 3 latest updates. I have allready used this method on my source. Is it possible I am having these issues because it is previously slipstreamed using this very method?

Just as a warning. v1.0 RC8 Beta 3 and earlier do not support the new DriverPacks. I apologize. But I will do my best to release Beta4 soon.

Yes PowerPacker and the integrator will both have support for the new DP Base. Please bear with me though. I have a pinched nerve in my neck and I have been going to the doctors to hopefully get the pain releived. It makes it difficult for me to be at the computer for long periods of time. This is the biggest reason the new powerpacker is taking so long to code.

It sounds like bashy allready basically made 2k support. He can just have it detect if it is 2k or not. If it is 2k then the option to slipstream massstorage drivers into txtmode should be disabled. 2k is still a semi-useful os for some computers. It actually will run semi smooth on only 64KB of memory. So when I get customers with old computers and they aren't willing to upgrade their memory 2k is the best alternative. But I very rarley have to install 2k anymore. So I can live without the ms drivers. I have pretty much gotten the latest integrator 100% coded as well and it will now have support for XP, 2k3, 2k, XP Media Center, and x64 OSes. So I know how much of a pain it was for Bashy to include what he has done so far. The RVMIntegrator and Windows XP PowerPacker will have full support for the new DP Base as well. Thx Bashrat for the new unattended features you've implemented! A lot of the msfn programs are able to link together now to help simplify the disk creation process... and I think it is awsome! The beta is very cool! So I can't wait for the initial release. I also can't beleive how fast Bashy put it together with as little flaws as it has had.

Only conclusion I can come up with is either your winnt.sif file does not exist at D:\winnt.sif ... Or powerpacker does not like it at the root of the drive? Not sure though. If wXPPC.sif exists in your boot directory then that means it should have copied it directly from i386 dir of your destination. Is there possibly a winnt.sif file in your source i386 dir allready? Maybe WXPPP is not overwriteing it with your winnt.sif in your D:\? Please run some more tests for me and let me know your conclusions. ThX

Hmmm... that is odd. None of my tests failed. Can you post your powpack.ini (or settings) file?

I have confirmed the Extra Pack Files bug. I will fix it. ****... I never use it so it allways seems to get messed up somehow. I am also adding a new "Advanced" tab that will have advanced features in it. I am in the process now of adding an area to Run a file (with parameters) upon completion of packing files. I've said I was going to add this feature for a long time. It will allow chaining of multiple PowerPacker processes together, Utalizing the RVM Integrator (Which has the chaining options too), or any other utility that has unattended parameters. Edit: Just fixed the Extra Pack Section.

Wow! That's awsome! I will be building a website soon to help promote it and this will look nice on it. Thanks again!

Again? ****... I will look into it.

I found a bug. For some reason... when you add an XP Home Edition pack... It doesn't copy the IDENT files to the root of the DVD. But I designed a new way for PowerPacker to get the IDENT files and it works better. So expect this fix to be in the next Beta. (Beta4)

I haven't used this yet... but I am going to try it. It sounds very cool. I see that it is simple to add a timeout period... but I was thinking... Is there any way to make it use the internal speaker of the computer to make it beep periodically, (Like every second), to let you know it is ready for input? That would be very useful for a user that is installing many computers... It would let the user know the computer is ready for input.

Thx Super-Magician!

@RyanVM I think we should make it manditory to use *UPPck.in? for all updatepacks. This way apps like the driverpacks will allways be able to detect an updatepack. What do ya think? @Bashrat On the next release can you implement this small change? I beleive all current UpdatePack releases follow this rule so far.

I'm not sure exactly what you are asking but I think what you need to do is edit the presetup.cmd file so that it looks for your .7z driverpack files inside of the I386\Drivers folder. You wouldn't need to edit the .7z files themselves because they will allready extract to the same place on the HD. The "D" folder at the root of your SystemDrive. If you want to have the files extracted to a different forler that "D" all you have to do is create your .7z file with a subfolder and place the .7z files in there. But make sure you edit the presetup.cmd file accordingly.

I need your help to make the Windows XP PowerPacker project stronger! Here are some small banners that are perfect for your signatures at any forum. If you like the program and you can't afford to make a small donation it would help me just as much to at least see that my work is appreciated. Lead other people to the program and let them know how helpful it has been for you. This project has been a long and hard project. It has taken a long time and a lot of coding to get to where it is now and there are still a lot of plans for it's future. Help keep me motivated on it. Sometimes I get a little burned out on it because I wonder if people still enjoy it or not. So get me motivated again! Thanks to XPero and WolfX2 Here are the banners and the code to put in your signatures: Graphic By: XPero [url=http://www.msfn.org/board/index.php?showforum=126][img=http://img386.imageshack.us/img386/5471/siginetsig1ce.png][/url] Graphic By: WolfX2 [url=http://www.msfn.org/board/index.php?showforum=126][img=http://img227.imageshack.us/img227/8394/powerpackerblue1qv.png][/url] Graphic By: WolfX2 [url=http://www.msfn.org/board/index.php?showforum=126][img=http://img221.imageshack.us/img221/7793/powerpackergreen4vl.png][/url] Graphic By: WolfX2 [url=http://www.msfn.org/board/index.php?showforum=126][img=http://img79.imageshack.us/img79/3428/powerpackerred4ic.png][/url] Graphic By: WolfX2 [url=http://www.msfn.org/board/index.php?showforum=126][img=http://img138.imageshack.us/img138/7285/powerpackeryellow3pi.png][/url] Graphic By: WolfX2 [url=http://www.msfn.org/board/index.php?showforum=126][img=http://img84.imageshack.us/img84/8181/powerpackergreen25wv.png][/url]