ArmyDoc

As of now, a Dutch guide on creating multiboot DVD can be found here. Like I stated in another post, it is a collection of information form flyakite's guide, this forum, Terriers French guide, and other assorted sites on the WWW. Attention: Dutch ONLY! So you won't find much of your liking als je niet kunt lezen wat hier staat Regards, ArmyDoc

I use CD Shell prosonally, but a lot of posts also deal with BCDW - and very often both methods are being used inside the same topic, possibly adding to the general confusion. I've gone the way of CD SHell because flyakite uses it in his guide, and only later learned of the exsistence of BCDW. By then, I had become proficient enough with CD Shell and could achieve the results I wanted to, and didn't have the time, patience nor the inclination to start using another method. I'm wondering if I'm missing something out? So I propose to use use this topic to discuss the merits, weakpoints etc. of both methods to help others make an educated choice.

OK, easier still but I suppose the steps are the same? Create some gifs and call them using showgif module? I use CD Shell personally, that's why I outlined the steps above... ArmyDoc

Sure! Which parts and where do you want them?

Well, I suppose I could, but most of it is off flyakites guide. Possibly just the parts that I added from other sources? If the demand is high enough I'll give it a go... ArmyDoc

Just type "Press any key" in the search box, it'll give you a fait few hitys. Try this one.

@ ET love your text menu but the cdshell.ini is a pain in the a** to read, no formatting whatsoever. Do you happen to to have a cleaner version that you can post? That is, if you arestill around... ArmyDoc

Or, if you want to know how to create a graphical menu here's what you do: Create a 640x480x24 bits bitmap fot each menuscreen you want to call, then convert them to csi files - just like you would to change the splashscreen. After that place them in the same folder as cshell.ini (unlike the splash.csi!) and edit your cdshell.ini like so (according to your posted image): boot: cls show image mainmenu.csi getkey 30 boot 0x80 if $lastkey == [f1]; then chain /pro1.dat if $lastkey == [f2]; then chain /wpe.dat . . . if $lastkey == [esc]; then boot 0x80 or use goto to call another screen. By the way, those three dots are purely to indicate more lines, (which I couldn't be bothered to type ) they serve no other purpose. Granted, it looks nice but don't start creating the graphics until you are completely satisfied with the layout of your DVD - the graphical menu is a b**** to maintain, unlike the textual menu. ArmyDoc

Maverick: take a look, but it's Dutch only I'm afraid. For anyone else who's interested: v1.0 is up tonight!

Alanoll, yeah, well, I've been at this for a while now and these are some of the snags, tips and whatnot that I've run into, not just on this forum. Mostly though it's because I've created a guide in Dutch (see previous post) and I get very nitpicky (?!?) when I go into teacher-mode By the way - I forgot one request: a working Knoppix! This one's driving me crazy... ArmyDoc

Suggestions / additions: 1. What to do with the installation files folders - $WIN_NT$.~LS. I've always just deleted them and haven't experienced any problems, but I do remember somebody posting something about this. 2. Add the cdromsp4.tst indentifier to the section about win2K SP4 (Funny thing - the file IS included in the DVD lay-out section, as a ERD Commander source file!) 3. Adding BartPE to the DVD: - Run PEBuilder - no specific need to create the iso - just the files in the output folder are needed, - copy from the PEB output folder the Programs folder to DVD project's root, do the same for i386 and rename that one to BPE1. Copy the files from the root of the output folder to the root of the DVD project. Like so: D:\AIO-DVD\BPE1 D:\AIO-DVD\Programs - edit setupldr.bin - replace i386 with BPE1 (as in the others) - no need to edit txtsetup.sif ( standard setting for setupsourcepath is already correct) - bootsector: in the root of the DVD project there is a file called bootsect.bin (it was copied over in step 1). Rename this to BPE1.DAT (for consistency) and hexedit replacing I386 with BPE1 (as in the others). - create menu entry: if $lastkey == ; then chain /BPE1.DAT 4. Space saving tip (I found it on Terriers French site): if you want to have multiple entries for ERD Commander and/or BartPE, one normal and one /inram, an alternative to flyakites method is the following: - goto BPE1 folder and create copies of both txtsetup.sif and setupldr.bin. Name them txtsetup.ram and setupldr.ram, respectively. - also make a copy of BPE1.DAT in the root of the DVD and name this BPE2.DAT - Hexedit BPE2.DAT and replace the textstring setupldr.bin with setupldr.ram. It's near where you would replace I386 with PRO1, 2PRO, BPE1, etc. Save. - Hexedit setupldr.ram and replace all occurences of the textstring txtsetup.sif with txtsetup.ram. Save. - Open txtsetup.sif with Notepad serach for OSLoadOptions and add /ínram: OsLoadOptions ="/fastdetect /minint /inram". Save. - add menu entry: if $lastkey == ; then chain /BPE2.DAT 5. In the section about support tools and WinImage, suggestion to check the boot sector is set correctly through Image > Boot sector properties... My personal experience is to set it to Win95 unless the image is meant for a DOS specific program, then use MSDOS6.22 6. Add to the boot menu section the possibility of creating graphic CD Shell menus by using show image xxxx.csi, e.g.: boot: menu: menu_Key: cls show image mainmenu.csi getkey 60 boot 0x80 if $lastKey == key[1]; then goto Windows if $lastKey == key[2]; then goto Utility if $lastkey == key[3]; then goto Info if $lastKey == key[q]; then goto end if $lastKey == key[r]; then reboot if $lastKey == key[h]; then goto Help if $lastKey == key[b]; then boot 0x80 7. There is a new version of IsoBuster. Haven't played with it much yet, though. 8. Screenshots sections has a bad link. 9. Link to translations of the guide? I know of two: in French and Dutch.

Hi again! After giving Knoppix a rest and concentrating on the rest of the DVD I decided I wanted to give it another chance - guess what? I'm running into the exact same problems as before... To recap: 1. Using using cdimage or cdimagegui or mkisofs it still remains impossible (for me) to create a joint Joiet/ISO DVD. I must have tried all possible combinations of options and switches I could think of... 2. When creating a DVD that uses only ISO (no -j1) I get a perfect DVD but Knoppix refuses to load because the filesystem cannot be found 3. The problem -AFAIK, PLEASE correct me if I'm wrong- in creating a Joliet/ISO DVD is the fact that it cannot cope with files or directories over 110 characters in length - as stated before, I have a grand total of one (1) such directory on the entire DVD, and it's created by PEBuilder Now I know some of you have been able to do exactly waht I am still trying to do - but how? Is it the language version of Windows XP which is responsible for the creation by PEBuilder of the one overly long directory? I'm guessing now because the one offending directory has only one file in it - mfc42nld.dll and I assume that the nld is a reference to Netherlands. What does this file do? Is it necessary (I'm thinking yes, because PEBuilder will create this file even if no plugins are selected). A websearch didn't give me any answers... Someone please help me out of my misery - CAN IT BE DONE? Is there a workaround for my problem, are any more of you experiencing this problem? I've found Terrier's site and it has this to say: il pourrait arriver que certains plugins de Bart PE ne fonctionnent plus (car 1 ou 2 fichiers du répertoire D:\ROOT\i386\WinSxS\Manifests\ ne peuvent pas êtres copiés correctement). Je n'ai personnellement pas eu de problème.Translation: some of you may have a problem with adding both BartPE and Knoppix, but I didn't. I'm much too nosy not to want to try, but I'm getting more and more frustrated by the hour...

Cobravox, looked at your site (is ity yours? I'm only assuming) but as far as I can tell it's not so much about multiboot as it is about creating an unattended Windows XP CD. No problem though, I combine both methods (Unattend and multiboot) for my own kickass DVD, and I was looking for a Dutch site for that as well. Can I link to yours in my guide? I'm not sure my wife likes me very much right now, I'm spending so much time on this whole project, and she would KILL me if I were to start on another one right away. Quick plug time: the Dutch guide is now about 80% finished, so let call it v0.8 for now. It should be completed by midnight tonight local time (= GMT+1). I'm keeping my fingers crossed... EDIT: OK, it's now almost 1 AM, and the site is 95% up and running - missing so far are the download section and the page concerning creating and testing ISOs. Those will hopefully be up by this weekend. Anyone up for proofreading? let me know through either email or PM. ArmyDoc @ AJvK.nl -=- AJvK.nl/multiboot

I know, it's what got me started on this whole project - and last month they did a piece on Unattended install too (which was an almost word-for-word translation of AaronXP guide/site)... By the way: I'm in the process of creating a Multiboot guide in Dutch - it's a 'hybrid' from flyakite, info from this forum and terrier's guide (which is in French, but has some great tips which flyakite doesn't have). EDIT: As of now, the first complete version is up, lets call it v1.0 - www.ajvankesteren.nl/multiboot All input appreciated! ArmyDoc

I've only just perfected -ahem- my boot menu using CD Shell, which, as far as I know, only supports chain and memdisk. bcdw is, to my knowledge only usable by BCDW, not CD Shell (at least not without plugin)

Ok I've narrowed it down to 1 specific folder in BartPE (see screenshot in pervious post), that ones 112 chars long and falls outside the range that a joint Joliet / ISO-9660 disc can cope with. I've tried renaming the folder by deleting 3 chars, and also to use CDIMAGE with the -k switch but, as you can guess, then BartPE won't load anymore . Knoppix does by the way . You win one, you lose one... So it seems it really is either BartPE or Knoppix for me, and since my knowledge of Linux is only marginally better than that of nuclear physics , I guess I'm sticking to Windows and BartPE. ****...

Check on every account... but I've named it BPE1, check attached screenshot. It's called from cdshell.ini: boot: menu: menu_Key: cls show image mainmenu.csi getkey if $lastKey == key[1]; then goto Windows if $lastKey == key[2]; then goto Utility if $lastkey == key[3]; then goto Info if $lastKey == key[q]; then goto end if $lastKey == key[r]; then reboot if $lastKey == key[h]; then goto Help if $lastKey == key[b]; then boot 0x80 Windows: Windows_Key: cls show image windows.csi getkey 120 goto menu if $lastKey == key[1]; then chain /PRO1.DAT if $lastKey == key[2]; then chain /HOM1.DAT if $lastKey == key[3]; then chain /2PRO.DAT if $lastKey == key[4]; then memdisk /98SE.IMG #ALs deze img niet goed werkt dan terug naar 98se.ima en pre-formatten if $lastKey == key[x]; then chain /PRO2.DAT if $lastKey == key[q]; then goto end if $lastKey == key[r]; then reboot if $lastKey == key[h]; then goto Help if $lastKey == key[b]; then boot 0x80 goto menu Utility: Utility_Key: cls show image utility.csi getkey 120 goto menu if $lastKey == key[1]; then chain /BPE1.DAT if $lastKey == key[2]; then chain /BPE2.DAT if $lastKey == key[3]; then chain /UBCD.DAT if $lastKey == key[4]; then memdisk /PM95.IMA [B]#if $lastkey == key[5]; then memdisk /KNOPPIX/knoppix.img[/B] if $lastKey == key[6]; then memdisk /622C.IMG #Keys nog aanpassen als Knoppix eenmaal werkt... if $lastKey == key[q]; then goto end if $lastKey == key[r]; then reboot if $lastKey == key[h]; then goto Help if $lastKey == key[b]; then boot 0x80 goto menu Info: Info_Key: cls show image info.csi getkey 120 goto menu if $lastKey == key[1]; then goto Serie if $lastkey == key[2]; then goto Mail if $lastKey == key[3]; then goto Copy if $lastKey == key[q]; then goto end if $lastKey == key[r]; then reboot if $lastKey == key[h]; then goto Help if $lastKey == key[b]; then boot 0x80 goto menu Mail: Mail_Key: cls show image mail.csi getkey goto menu Copy: Copy_Key: cls show image copy.csi getkey goto menu Serie: Serie_Key: cls show image serie.csi getkey goto menu Help: Help_Key: cls show image help.csi getkey goto menu end Also, I've checked using the provided app, and the only files/folders over 100 chars long are the folders in BartPE, and only one is over 110 chars. I'm about ready to give up on Knoppix unless someone has a kickass replacement for BartPE (and I don't have $200 to spend on ERD Commander, so don't bother mentoning that one ). ArmyDoc AIO_folders.zip

@Markymoo: I know that both cdimage and mfisofs SHOULD let me create Joliet/ISO-9660 DVDs, BUT in my DVD structure I've included BartPE which uses long filenames (>110 chars). I believe that's the problem with cdimage (and what cdimageGUI so politely tells me about before quitting), and I assume that this is the same problem for mkisofs. If anybody can tell em a way of creating BartPE with shorter filenames, or has other solutions, I'm open to suggestions ArmyDoc

OK, so CDIMAGE.exe won't let me create a Joliet/ISO-9660 DVD iso file. After some searching I found this site and I have been trying to do the above only now using mkisofs. I've made the following .cmd file: DEL D:\*-JOLIET.ISO start mkisofs -iso-level 4 -l -J -joliet-long -r -R -b \AIO-DVD\BOOT\loader.bin -allow-multidot -no-emul-boot -volid "MULTIOSDVD" -A MKISOFS -sysid "Win32" -boot-load-size 4 -o "D:\multi-joliet.iso" "D:\AIO-DVD" ;start /pause cdimage.exe -lMultiOSDVD -t08/23/2001,09:00:00 -b\AIO-DVD\BOOT\loader.bin -j1 -h -o -m \AIO-DVD D:\AIO-JOLIET.iso end The syntax is modified somewhat from the example on the page (it -d -D switches, and no -r -R) because of two error messages. The first one about Rock Ridge file system and how they strongly advice me to incorporate it, so I have. The other problem is that I always get the same message on running my .cmd: WARNING: creating file system that does not conform to ISO-9660. mkisofs then hangs… How do I solve this? Any help appreciated

Right, so it's either back to Knoppix 3.2 with boot.img or Knoppix 3.4 with isolinux.bin Either way, when trying to create the cdimage using the -j1 switch cdimage.exe refuses to run, even after removing the conflicting -n switch (run cdimage.exe from command line without options to see the helpsection). But even if it would work there are a ton of files on my DVD that have long filenames How to proceed? ArmyDoc

Had the same error. What fixed for me was partitioning and formatting the C: drive before installation (al least, that's what worked in MSVM), after that Install of Win 98SE went smooth as a babies behind. ArmyDoc

A short search would have given you the switch to use: it's -j1 However, I've tried to edit the createiso.cmd file from flyakite's guide/site and add the -j1 switch but then the cmd file refuses to run. Anybody know why this is? Also, the latest version of Knoppix doesn't include the makefloppy command, and I'm unsure how to proceed. Things I've tried: using the boot.img from an older version of Knoopix and loading from that in CDShell. The problem is that memdisk will run, but installation is halted at a boot: prompt. From there it refuses all input except "knoppix" (all other inputs return an error message to the effect that the specified kernel could not be found). With "knoppix" entered I get a few lines of a loadin sequence and then the screen goes blank and the PC hangs. Anybody have any idea how to correct this? EDIT Using MS Virtual Machine I've come on step further - I get the following error So it seems to be the filesystem after all, which brings me back to my original problem - how to make createiso work with the -j1 switch?

I couldn't code if my life depended on it

If you don't mind creating some gifs: take a look at this, for use with CDShell. According to the author : Also, the following ini shows how to use them for various screens (though the author [credits / original post found here] is using csi here, for those you'll have to create 640x480x24 bit bmps and convert them): boot: menu: menu_Key: cls show image MENU.CSI getkey if $lastKey == key[1]; then goto 2003 if $lastKey == key[2]; then goto XP if $lastkey == key[3]; then goto 2000 if $lastkey == key[4]; then chain /ERD1.DAT if $lastkey == key[5]; then chain /ERD2.DAT if $lastkey == key[6]; then chain /UBCD.DAT if $lastKey == key[F1]; then memdisk /MISC/DOS.IMG if $lastKey == key[F2]; then memdisk /MISC/W98.IMG if $lastKey == key[F3]; then memdisk /MISC/W98NTFS.IMG if $lastKey == key[F4]; then memdisk /MISC/PM8.IMG if $lastkey == key[F5]; then memdisk /MISC/GHOST.IMG if $lastkey == key[F6]; then memdisk /MISC/DOCM.IMG if $lastkey == key[F7]; then memdisk /MISC/DS.IMG if $lastkey == key[F8]; then memdisk /MISC/DF.IMG if $lastkey == key[F9]; then memdisk /MISC/PWM.IMG if $lastkey == key[F10]; then memdisk /MISC/DL.IMG if $lastkey == key[F11]; then memdisk /MISC/DW.IMG if $lastKey == key[F12]; then goto serial if $lastKey == key[r]; then reboot if $lastKey == key[a]; then goto aide if $lastKey == key[esc]; then boot 0x80 serial: serial_Key: cls show image SERIAL.CSI getkey goto menu XP: XP_Key: cls show image XPMENU.CSI getkey 120 goto menu if $lastKey == key[1]; then chain /WPRO.DAT if $lastKey == key[2]; then chain /PRO1.DAT if $lastKey == key[3]; then chain /PROU.DAT if $lastKey == key[4]; then chain /WHDE.DAT if $lastKey == key[5]; then chain /MCTR.DAT if $lastkey == key[6]; then goto tweakXP if $lastKey == key[F1]; then goto Help goto menu tweakXP: tweakXP_Key: cls show image TWEAKMEN.CSI getkey 120 goto menu if $lastKey == key[1]; then goto orilla if $lastKey == key[2]; then goto teknisio if $lastKey == key[3]; then goto milk if $lastKey == key[4]; then goto reluna if $lastkey == key[5]; then goto rebutz2v if $lastkey == key[6]; then goto guipod if $lastKey == key[F1]; then goto Help goto menu (midsection deleted... since code is for demonstration purposes only) aide: aide_Key: cls show image AIDE.CSI getkey goto menu end Example (not based on above ini ):

Hi all, does anybody know if it's possible to assign a password to a specific entry in cdshell.ini - i.e. I have one specific key set up to OEM preinstall WinXP and a bunch of drivers/apps, and I want to protect it from prying hands. If not through cdshell.ini, perhaps through the corresponding DAT? ArmyDoc