ArmyDoc

And then you should hexedit the cdshell files top reflect this. Right? See flyakite's Longhorn section on which files to edit

@dhernande, for info on the possible switches for cdimage, just open a command prompt an type cdimage without switches, statements etc. You'll get a list of all possible switches. Most commonly used are -l -h -n -m -o -b and -d. If you're lazy or a lousy typist you can use the gui version of cdimage, aptly named *drumroll* ... cdimagegui. A google serach should let you find it, else click here.

The spcific switch for cdimage being -o, in case anybody was wondering

In principle, yes. But only the folders that relate to your model of mobo and your OS (if you're using this disc on your own pc only). Keep the folder structure intact. You'll have to point to each folder which has an .inf in your winnt.sif OemPnpDriversPath line. ArmyDoc

I followed the guide to the letter and didn't have any problems with installing Win98SE, as long as the autoexec.bat poiints to the right folder! I do know that an update of this section is forthcoming, though. Stay tuned. ArmyDoc

@All look at the top right of the screen. See the little magnifying glass? Alternatively, scroll down af few lines on the main page, you'll find a large post that deals with this. It's this one. ArmyDoc

@ Alanoll: HUH?!? I understood every single word of your post - but the whole didn't make sense. Please elaborate... perhaps with an example? Meaning three different winnt.sif's? Or one with multiple entries? You've lost me there... You're not kidding... ArmyDoc

As Maverick would say: no worries mate I hope my two posts were clear - if not, let me know and I'll try to explain. Sometimes my toughts run ahead of my two-finger-typing skills and things that I think are clear tend to be convoluted... Good luck and let us know if it worked. ArmyDoc

I think something went wrong when you hexedited your files, probably your bootsector .dat file.

@Maverick After giving this some more thought I've come to the conclusion that it all depends on which unattended installation method you use: batch file command line driven or RunOnceEx. In the first case you can specify which batch file to run, and if you create three different batch files you can point winnt.sif to a specific one - but you would still need three .dats and three bootfolders with three winnt.sif files. When using RunOnceEx you will need to do it as posted before because then you cannot point to specific batch files - Windows Setup will search automatically for a file called cmdlines.txt of which there can obviously only be one in each folder - therefor there must be multiple $OEM$ folders when using RunOnceEx It does make for a nice experiment, though, doesn't it? ArmyDoc

The download link on the XPCtest website (from the first opst) doesn't work - I get error: file not found on server xpctest.exe (using getright) Without getright I get a 404

There are some posts that address this question - look for acronis and msdos in the topics. A general guide on how to do this can be found here. It deals primarily with Acronis apps but can be adapted to fit others. For MSDOS: more info here.

Kremlin, my first reply may have a been too hasty... Something posted is another forum has been nagging me all day now, and it does reflect on your problem. After first reading your post I assumed it was a simple unattend/multiboot question - it's not. In fact, in it's core it has nothing to do with multiboot, so, technically it's a question posted in the wrong forum - it's all about unattended install. My guess is you'll find what you're looking for is you search the Unattend forum, here. Since I'm at it anyway - here's what I'm thinking: you have two choiches - number one is to create a single setup routine with an option menu at the end of it which will let you choose what apps to install - like this thread. Granted, it's not exactly unattended, but is is flexible and will let you actually achieve what your asking without too much trouble. Second option: completly unattended options - for this you will have to go multiboot, as what I'm thinking you should do is to copy the entire WinXP Pro CD to your multiboot DVD three times, so that you'll end up with with the follwoing (bear with me...) D:\AIO-DVD\Setup\XP\Pro1 D:\AIO-DVD\Setup\XP\Pro2 D:\AIO-DVD\Setup\XP\Pro3 Now, you'll also have to create three boot sectors, Pro1.dat, Pro2.dat and, *gasp* Pro3.dat, and also three separate bootfolders - again, PRO1, PRO2, and PRO3 (although, see below). Edit the files so Pro1.dat refers to PRO1 refers to \Setup\XP\Pro1. Do the same for Pro2.dat and Pro3.dat. After that all (ahem) you'll have to do is to create the appropriate $OEM$ folder structure for each of the different setups and create/copy all the necessary files - for that I will refer you back to AaronXP's guide. Last step is to create three boot option in your menu, calling Pro1, -2, or -3.dat Is this actually clear? I'm doing this of the top of my head right now, so anybody please correct me if I'm wrong, especially about needing three separate bootfolders - I'm thinking that, just as with the /inram bootoption as described in the update multiboot guide, the same results can be reached with copying and renaming setupldr.bin and txtsetup.sif (within the PRO1 folder) twice (so, you'll end up with, lets say - setupldr.bin, setupldr.net and setupldr.dvd; txtsetup.sif, txtsetup.net and txtsetup.dvd) Then, edit so that pro1.dat points to setupldr.bin and txtsetup.sif, which point to \Setup\XP\Pro1; pro2.dat points to setupldr.net and txtsetup.net, which point to \XP\Pro2; and pro3.dat points to setupldr.dvd and txtsetup.dvd, which point to \XP\Pro3. Me thinks option one is easier, but a lot less satisfying to try out and get working right

Dude! You blindly copied and pasted my text, typo's and sidenotes included, don't know whether to or . I'm planning on doing some cleaning up on my own guide in the very near future - I'll send you an English version of UBCD.htm when I'm at it. By the way: it can be had here.

The fact that I'm even replying should tell you something - but that's a discussion for another forum, me thinks... Boss-man and wife-woman aren't always too happy tho, so I can relate .

Crossing my fingers!

Ok, just to double check: These are the original PM rescue discs, I gather? If not, make sure there are! You set/check the bootsector each time you save your PM8.IMA? I know I'm nitpicking, but it's easy to forget this. Something like this had me stumped for two whole days before it retraced every step in the creation process. If all else fails - what version of WinImage are you running? I have 6.10.6100, never had a problem. EDIT: Just now looked at your screenshots - there's definitely something wrong with either the bootsector or the system files on the IMA - bootsectors are the best bet, I think. ArmyDoc

Hmmm, I'm assuming WinxS is a typo? Take a look at my screenshot - 2 remarks: 1. discard the BartPE folder at the bottom - it's my PEBuilder folder. 2. discard the two files with the .ram extension, they're used for loading /inram. As you can see, I don't have the identifiers in the BPE1 folder, and this setup works flawlessly... You did copy all the files, including the hidden ones, did you? Alanoll is working at flyakites guide to include a BartPE section (any word yet on a due date, Alanoll?), check that to see if you've missed anything, or check this if you can read French. bart.zip

Ah, well, I didn't actually say anything about *creating* plugins, now did I? I'm not smart enough for that , and besides, other people can do that far better than I ever could For a long list of plugins go here. A complete Forum repository can be found here, specifics on a partition magic plugin here. A plugin for Ghost is included in PEBuilder, but read this. I've posted a cabfile with the necessary files, download here.

I've found the most satisfying option to add PM, Ghost etc to the DVD is to integrate them into BartPE using third 'party' plugins. The one big advantgae of this method is that you can use more than one app in the same session - otherwise you'll have to restart the machine after each use of the tool in question.

Alanoll, just sent you a PM which outlines the differences and overlap with flyakites guide. Take a look. ArmyDoc

Alanoll, I propose I PM you with a brief synopsis of what is in my guide, and we can discuss about the parts you would like me to translate? If you have another idea, let me know.. Regarding th -n option, I havent encountered any problems with the -n options when used solo. I do know that you cannot have both -n and -j1 options in your command, If you have you get errors like CD\DVD not bootable of cdimage not running at all. I don't know if it has anything to do with the order in which the options are used which kind of error you get, but this is what has been frustrating the hell out of me when trying to add knoppix to a DVD already containing BartPE.

Weird problem... Off the top of my head: how many CD-DVD drives do you have? If just the one then you may want to try and run BartPE from memory (with the /inram option) to avoid problems with disc swapping? Also, have you checked that all the necessary plugin files are on the multiboot CD\DVD? What command do you use to launch/run BartPE? ArmyDoc

Doesn't anybody search anymore? Jeez, I'm starting to sound like Maverick and Alanoll Kremlin: go here and spend some time there, then go here and look under extra's. Mavericks is right tho, nothing a short search wouldn't have turned up... ArmyDoc

Maverick: to see my cdshell goto the downloads page of the guide - you'll find a download for cdshell.zip. This zipfile contains both my cdshell.ini for an textmenu and cdshellgraphic.ini for (three guesses... ) a graphic menu. Disect, edit, reassemble, assimilate ... Armydoc