jaxflmax

http://unattended.msfn.org/ i don't think there is a true 'integrate' method other than using OEM folders but that link will tell you everything you need to know to make the apps you want install automatically after windows installation finishes

Actually moving the OEM folder wasnt the only thing i did, sorry! Here's the entire procedure completed right before burning to dvd - apply method 2 to the windows xp folder (the one that contains i386), copy winnt.sif and txtsetup.sif from i386 into the 'PRO1' windows xp boot folder which should be in the root of your disc. Then copy the 'OEM' folder to the root of the disc as well. I DID NOT use DPack mass storage because of issues i had heard about and i don't really have a need for it yet, but every other current (as of 03/5/05) driver pack was used. This has been successfully tested on 8 computers now EDIT: i pretty much followed the multi-boot dvd guide to the letter when creating mine - people using different methods for organizing the boot structures may have difficulty, but just make sure you have the modified winnt.sif and txtsetup.sif files in the place where they will be called from and put the OEM folder at the root.

I used method 2, moved the "OEM" folder out of the windows xp directory and onto the root of the disc - works like a charm. The reason i'm posting is because i ran a search and found a few posts that touched on this then trailed off into unanswered oblivion. Once again that's "OEM" not "$OEM$" I used the DP's for the first time today too - they set me up with a slick sound control panel and handled everything else just fine. Thanks BTS for this great solution and so much hard work keeping the packs in development.

I still get the "txtsetup.oem caused unexpected error(18) at line 1747". My line 1747 in txtsetup.sif is "cnb2100.dll = 1,,,,,,,,3,3" I notice that people had the problem earlier but don't have it anymore, how did you fix it? When i first applied the driver packs it was a while ago and i used method 1 and had not tested my multi-boot cd, but most recently i used method 2 with the following versions BASE: 5.02.10, GRAPHICS: 5.02, LAN: 5.02, MASS STORAGE: 5.02.1, SOUND 5.02.1, WLAN: 5.02 EDIT: Doh! while rereading my post i noticed 'multi-boot' I copied the txtsetup.sif on top of the one that ACTUALLY gets used and it should work, havent tried it yet though

I use kTool because it's soooo easy and doesn't require lots of coding

@polecat: If you put a folder on your cd say "post install programs" and put ktool along with all the programs you want to install i think it will work fine they way kenedy says (havent tested this yet though) @kenedy: very nice app, this replaced all the other methods I was using any chance of adding a dialouge box or sidebar for program descriptions? Or failing that, could i have the source? EDIT: to clarify, i mean to make program descriptions available at the selection stage

A good idea is to download HIS cdshell.ini that is linked in the guide there somewhere and edit to fit your needs or use it as a template

Just enter a generic name in winnt.sif then once everything finishes install right click "my computer" and go to the "computer name" tab

What exactly happens to make you say 'it doesnt work properly' Edit: i've started work on putting MCE on my multi-boot dvd and there's a setupdlr.bin in I386. Check and see if that isn't your problem.

Why don't you just not specify a name in winnt.sif? Or better yet, once it finishes install and boots into windows just rename it or write a small program/batch file that comes in at runonce and asks you for computer name. That would be the best option as far as preserving the un-attendedness of the process The only way I could think of doing this is have cdshell copy winnt.sif (or entire boot sector? or maybe even all the install files???) to a certain spot on the drive, and edit your unnattended install to point in the right places. That sort of limits the usefullness of making a whole new OS disc in the first place though. The 2 difficulties i see are that: cdshell can't edit something that's burned on the cd, and i don't think winxp can be made to call a remote winnt.sif file.

I think win51 and the rest are marker files? So the setup knows where to look for all it's parts, it searches for win51. Edit: open up one of those files in notepad lol

In my english version they are all the same. That is really weird that you have 3 of 1 and 1 of the other, glad you got it working

Ah! Well one solution to that is to make several copies of your desired OS folder, using a different WINNT.sif (residing in I386) in each one but keeping the rest of the files the same. You can edit your cdshell.ini or whatever is used for easyboot to chain into each different version. Once you optimize your multiboot disc, it will not be any larger but you now have several different versions of the OS to chose from.

I ended up copying over my xp winnt.sif and added 2 lines on how licenses should be distributed - worked just fine. Thanks guys

Did you ever resolve this issue?