Siginet

I just had another idea. Wouldn't it be possible to have this project use the svcpack method of install? Then it would be possible to use this even if it is not an unattended setup. Edit: Hmm... but then I guess the Royalty OEM Key would have to be inputed too.

I actually made my own maint program that I use on many of the company systems I maintain. It scans for viruses/spyware, performs updates, defragments the computers. It's not completley finished yet but it does the job. I want to make it email me when a computer is infected as well. Also as of now it only supports Adaware and Symantec Antivirus.

Is it possible to use a retail or oem serial number in a coporate copy? I have wondered... but I have never tried it.

If you highlight the icon it should tell you what command it is stuck on.

I've been playing around with the ideas from this thread for quite some time now and I have to say... this idea is awsome! It will save me tons of time. I have to admit... it wasn't easy to figure out how it works... but once I finally figured it out it is great. I'm sure some of you know... I am the writer of the RyanVM Integrator and Windows XP PowerPacker. Both of which have apeared in numerous worldwide magazines. I promised my fans that when I figured out how to bypass activation (legally) I would create a method that users of my programs can use to simplify the process for them. I was playing around with the scripts Bezalel made and I created an autoit executable that does basically the same thing as Bezalel's vbs but when it finds the hex code it checks the directory for that hex code... if it doesn't find it... it knocks off one of the hex characters and searches again. It keeps knocking off a hex character until it finds a file match or until it has no more characters to search for. It seems to work rather well. But I am sure Bezalel is onto something much more sophisticated. I am far from an expert at this project. All of the leg work is by the people of this thread. Any way I can help out just ask. I have a lot of source code allready written up in my other programs that would make it simple for me to create the perfect script for this project. Here is my idea... I think it would be great to have an ini file created that a script can read to differentiate which oembios.* files should be copied to windows. From what I understand Bezalel's scripts looks for what the manufacture hex code is on the machine then it copies the hex oembios files accordingly. Here is the basic concept I was thinking for the ini file: oembios.ini [Manufactures] Sony Corporation=376E13C7.rar 'Sony Corporation=376E13C7.rar Sony Corporation'=376E13C7.rar 'Dell Quanta'=87870F5A.rar 'Lan Plus=FDAA5E8B.rar Lan Plus'=FDAA5E8B.rar 'Equus Computer Systems=0D59FC53.rar Equus Computer Systems=0D59FC53.rar Equus=0D59FC53.rar Equus'=0D59FC53.rar 'MAXDATA=608BC835.rar MAXDATA'=608BC835.rar ... so on and so fourth. Basically the idea is to have the ini point to the correct pack of oembios files. Or have it point to the correct hex string. Then the files are either extracted or copied to the windows installation. This I think would give a much better organization and also allow us to easily make it all 8.3 compliant. I would also suggest the project run from outside of the $OEM$ directory. Possibly in an "OEMBIOS" directory at the root of the disk. This way it can easily be implemented in a multiboot disk environment. What do you guys think?

.net framework has never been needed for any of my tools. Think maybe you've gotten my tool mixed up with someone else.

I'll be uploading RC9 soon. I have fixed a couple of bugs and I think it deserves to be released. There won't be any major differences between RC8 and RC9 but it does fix some bugs. I may name it RC8.1.

Yes it does. Take a look at the advanced tab. A new option is there called "Create Extra Boot Folder(s)" The boot folder name can be a new boot folder or it can use an existing one. If it is a new one then powerpacker will copy all of the boot files from the pack you are using and create a new boot folder with the new winnt.sif you specify. If it is an existing folder then powerpacker will add the new winnt.sif file and add it to the boot menu. The Boot entry is what you want to add to your boot menu entry for this pack. (PowerPacker auto recognises the OS type for you now.) BOOT winnt.sif file is the new winnt.sif you want to add to this pack.

Very helpful indeed. You may want to add the rvmintegrator and windows xp powerpacker for unattended creation of your multibot disks. Saves a lot of time.

bcdw is much easier.

Autoit3 is becoming a very powerful language to code in. I develope all of my tools in it. I think anything you can do in VB can be done in autoit. Also VB and autoit seem pretty simular in code to me.

Actually I have been digging into this as well. The link discountpc has given is a good link. I haven't had much time to try it yet. Actually the oembios trick is one of the main reasons I wanted to add the Multiple winnt.sif option to the integrator. It helps in the process of making a disk with multiple manufactures files. Once I have the oembios trick down pat I will make it easier to accomplish this trick with powerpacker. Because PowerPacker is made for creating "Universal XP Media"... so this goes with the territory.

Thanks for notifying me so quickly. I have silently updated the file since they were all minor fixes. I'm also waiting for betanews to update their page as well.

Uhm... Which addons? Sorry... I added the link for ya now.

Just updated to 1.0 RC8 Final. Compiled the old manual back into it.

You can keep all of your winnt.sifs in one directory. The original winnt.sif must be named winnt.sif but all of the ones you use in the advanced tab can be named anything. I am aware that the Boot Name inputbox is kinda weird. It sometimes only allows 3 characters and sometimes it allows 5 characters. Just make sure you put in 4 characters. I will be looking into this and I will try to make it work the way I want which is to force a user to place 4 characters. The multiple winnt.sif option is great and it works very well... but I will probably be fine tuning it soon and I will be adding it into the next manual.

Thanks for this Windows 98 PowerPack! It is coming in handy for me right now.

The updatePacks are different then they used to be as well. Files are compressed on the fly while integrating into the disk... so you will notice a huge difference in the amount of time it will take to integrate. It will take longer. I have thought about creating a small tool to repackage the new updatepack into an old style updatepack that does not have to compress on the fly for those of us that do many integrations for multiboot disks.

Powerpacker doesn't copy it over for you. Yes it belongs at the root of the disk. Not next to $oem$. All of your installs should be able to use the one WPI directory at the root as long as they were all integrated with the wpi directory to begin with. Please let me know if all goes well or if you have any issues.

Try using these addons... They will remove un-needed files and save you over 100MB of space if you haven't deleted them allready. These addons are tested fully working in the integrator... but should also work with nLite. http://www.ryanvm.net/forum/viewtopic.php?...hlight=winntupg

Anybody tried the new Advanced feature to use multiple winnt.sif files yet? I'm curious to know if it works well. Soon I am gonna try to make a new manual since there have been so many new changes. I'm thinking about creating an online manual if anyone is up to helping me with it?

Actually it is even easier to add in the new shell. All you have to do is open \BOOT\Boot.ini Add this line in the [MenuOptions] section: \ERDC\setupldr.bin ; ERD Commander Copy the full contents of your erd disk to the root of your multiboot disk and rename the I386 directory to ERDC. In future versions of powerpacker I plan on making it even easier. You can also use the Extra Root Files section to automatically copy the files for you and instead of renaming I386 just use this line in your boot.ini instead: \I386\setupldr.bin ; ERD Commander

It should be possible to add the wpi directory to the root of your disk. Just make sure each of your packs have runonceex setup as well. I don't see any reason wpi won't just work directly from the root of the disk. If there are any modifications that have to be done manually that powerpacker doesn't cover I will add WPI support into powerpacker as well since I've allready added WPI support in the latest integrator program allready.

Your best bet is to completley get rid of winnt.sif. Use the svcpack method to copy your files. Just create a batch file that will run inside svcpack.inf. Take note that some envvars do not work in svcpack.inf (at least from my experiance). @5128 I like your signature.

Get: Windows XP PowerPacker v1.0 RC8 Ok folks... Changelog: RC8 Final: 1. Fixed a bug where the IDENT files were not created in the unattended pack of the Tri-Pack option. 2. Fixed other small bugs. 3. ReCompiled the old help file into the program so people can at least learn the basics until I get time to create a new help file. This help file is outdated and there have been some major changes since this help file was created... but it should help give you an understanding of what to do. Beta5: 1. Added new option in Advanced tab for allowing multiple winnt.sif files. Very cool new feature! Just select a 4 character name, a winnt.sif file and something to add to the boot screen. (PowerPacker auto recognises the type of OS you are using.) 2. Custom pack name option now allows you to add an entry into the boot screen. 3. Fixed bug where the tmp folder was left behind when using the DriverPacks. Now the driverpacks settings file is copied to the %temp% directory and deleted after it is finished. Beta4: 1. 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. Please report any bugs you may find. Rate Windows XP PowerPacker @ BetaNews.com Enjoy! Here is how to use the DriverPacks: