Help - Search - Members - Calendar
Full Version: A working Linux on AIO Multiboot
MSFN Forums > Unattended Windows Discussion & Support > Multi-Boot CD/DVDs

   


Google Internet Forums Unattended CD/DVD Guide
Markymoo
I've managed to get Linux Knoppix booting off AIO. Knoppix is a bootable linux to
run off a cd. This is what i did.

Update 27 May 04
Moving the isolinux folder to your AIO boot folder causes loading of the knoppix boot screen while loading an other os. So this is now corrected. Thanks to FBi_

Instructions

Goto http://www.knoppix.org/ to get it.

Edit your iso(try winrar or ultraiso) and extract the knoppix folder to your AIO folder and then extract the isolinux folder to AIO also.

Example

C:\AIO\knoppix
C:\AIO\isolinux

No hexing of files to do...shock..gasp

All you now left to do in your menu script to run linux is the command

bcdw /isolinux/isolinux.bin

Always use bcdw not memdisk

I didnt mention the -j1 switch in cdimage but this is what i use everytime.

the necessary switches are:-

-l label "ALLWINDOWS"
-t 08/23/2001,09:00:00
-h hidden files & dirs
-j1 both joliet and iso-9660 compatible filenames together.
-b "loader.bin"
-o optimize storage
-m ignore maximum image size

I love to use cdimageGUI saves alot of time and can experiment with different options. If im experimenting with one os to get it to work i just make an AIO folder with just that os. This saves enourmous time burning the image to test instead of trying to make an iso 4gig big and finding out it dosent work. I just have boot folder files and a dat and whatever else is needed for that os so when i have got it running perfect i add it to the dvd aio folder with the rest.

Enjoy
Phil
It seems to work, but does not in my AIO : When Knoppix works, all Windows installations don't, for example XP installation fails before copying the files on the HD.
It seems to be because Knoppix requires Joliet and Win installations require strict ISO...(?)
If anybody has the final answer... Please TRY all your installers and tell us. If it works, perhaps you could provide here your CDIMAGE.EXE params and/or your AIODVD directory structure.
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?
cyberdiamond
I can tell you that you must use the boot image (floppys) that are created with the same kernel your trying to boot.

So you cant use old floppy boot disks with a new version. no.gif

Also the reason they don't allow you to make a floppy boot on the new version is the image is too large to fit on a floppy disc.

You could recompile the kernel and make a foppy image use that for your aio (it still won't fit on a floppy but that doesn't matter on a cd smile.gif )
ArmyDoc
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 sad.gif How to proceed?

ArmyDoc
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:

CODE
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… realmad.gif

How do I solve this?

Any help appreciated
Markymoo
Ok first up make sure you have plenty of space on your hard drive because cdimage demands alot if the image is big. If you get hangs or cdimage quitting this is usually from not enough space.


@ArmyDoc yes cdimage will let you create an iso/joliet iso

@Phil you need to add the -j1 switch. It does work!

Here is my command line this should help

cdimage.exe -l"ALLWINDOWS" -t08/23/2001,09:00:00 -h -j1 -b"C:\AIO\BOOT\loader.bin" -o -m "C:\AIO" "C:\AIO.iso"

Failing that download cdimageGUI HERE
ArmyDoc
@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
Markymoo
Ah well you said nothing about BartPe.

Guess what my AIO has BartPE too.

I run BartPE put every program plugin going. No problem at all

Rename the BartPe I386 folder to BART
Make a BART.DAT boot file
Hexedit BART.DAT change I386 to BART
Edit setupldr.bin in BART folder and change I386 to BART
copy winbom.ini to root
Run BART.DAT from a script

Never got the error you described as long as i use -j1

You could try a utility such as this to see which programs are using long filenames. And sacrifice the offending program.

Also check your drive for errors.

Extra long filename is supported with the ISO9660:1999 and UDF filesystems.
ArmyDoc
Check on every account... but I've named it BPE1, check attached screenshot. It's called from cdshell.ini:

CODE
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 newwink.gif ).

ArmyDoc
Markymoo
Nothing wrong with that

Try removing total commander that has long filename problems.
ArmyDoc
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 no.gif . Knoppix does by the way smile.gif . 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 woot.gif , I guess I'm sticking to Windows and BartPE.

****...
Tuxer
I'm not a star in this, but doesn't he mention in the first post :

bcdw /boot/isolinux/isolinux.bin

Always use bcdw not memdisk

.... you are using memdisk..... maybe this is the problem?
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)
Markymoo
all you have to do is copy bcdw.csm into your cdshell modules folder.
Tuxer
Ok now I lost it completely!

I've got a simpel AIO..
Added Knoppix.... and it's getting weird....

Option 1 (winxp) boots fine
Option 2 (wn98) first gives me the knoppix bootscreen, and then boots 98.
Option 3 (knoppix) gives me knoppix
Option X (more options) gives me knoppix!!!!!!!!!!!!!!!
Option Q (quit) gives me knoppix!!!!!!
Option R (reboot) gives me knoppix!!!!!!! ARGGGGGGGGGGGGGGHHHHH

Get my drift!! ??

WHY????

Pls help
I started the whole thing over and stuff.. nothing helps...

Any suggestions?



# Printing the Interface
menu:
set textColor= color[grey on black]
set boldColor= color[cyan on black]
cls
print c "\n\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ<\c0B$time $date\cXX>ÄÄ \n\n"
print c "\cXXMulti-Boot DVD NEDERLANDS 0.5\n\n"
print l "\cXXPress \c0CF1 \cXXfor Help"; print r "\c0Ctux@inventerprise.nl \n"
print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n\n"
print "1) Windows XP Professional SP1 Nederlands \n"
print "2) Windows 98 SE Nederlands \n"
print "3) Knoppix \n"
print "\n"
print "X) More Options... \n\n"
print "Q) Quit to Command Prompt \n"
print "R) Reboot \n"
print "ESC) Boot 1st Harddisk \n"
print c "\n"

MainKey:
getkey 20 boot 0x80
if $lastKey == key[1]; then chain /PRO1.DAT
if $lastKey == key[2]; then memdisk /98SE.IMA
if $lastKey == key[3]; bcdw /boot/isolinux/isolinux.bin
if $lastKey == key[q]; then end
if $lastKey == key[r]; then reboot
if $lastKey == key[x]; then goto MoreOptions
if $lastKey == key[F1]; then goto Help
if $lastKey == key[esc]; then boot 0x80

MoreOptions:
cls
print r "\n\cXXPress \c0BF1 \cXXfor Help \n"
print c "\n\cXXMore Options \n"
print c "\cXXÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ \n"
print "1) ERD Commander \n"
print "2) Partition Magic 8.0 \n"
print "3) Laat Serials zien \n"
print c "\n\n"
print "Druk op een toets om terug te keren naar het Hoofdmenu... \n"

MoreOptions_Key:
getkey 20 goto menu
if $lastKey == key[1]; then chain /ERD1.DAT
if $lastKey == key[2]; then memdisk /PM8.IMA
if $lastKey == key[3]; then goto SerialNumbers
goto menu
Markymoo
I will tell you whats wrong with it the line below.

if $lastKey == key[3]; bcdw /boot/isolinux/isolinux.bin

Its treated as two seperate commands, it will always boot linux whatever you press from this line onwards unconditionally. You have missed a then statement.

It should be

if $lastKey == key[3]; then bcdw /boot/isolinux/isolinux.bin

Now it will work fine.

This line if $lastKey == key[2]; then memdisk /98SE.IMA is fine as long as you have 98SE.IMA in the root dir which i'm sure you have. I suggest you download a 98SE.IMA again from here
Tuxer
Thx a million, i'm giving it a go right now :-)
FBi_
Hi!

Thanks for this great guide to get Knoppix running.

I had the problem that at some (not all) start options the knoppix bootscreen appeared and then started the correct app.

That's the prob, that Tuxer had also.

QUOTE
Option 2 (wn98) first gives me the knoppix bootscreen, and then boots 98.
If the folder isolinux is pointed in the boot folder, the image appeared. If you put the isolinux folder in any other folder, the image doesn't appear.

I only want you to know that.

cu
FBi

-------------------------------------------------
getting errors on booting knoppix now sad.gif

QUOTE
ISOLINUX 2.04 (Debian,  2003-06-06) Copyright © 1994-2003 H. Peter Anvin
Could not find kernel image: linux
boot:


Is there another possibility to supress the knoppix bootscreen at some starts of programs?

--------------------------------------------------
now it works smile.gif

i put the isolinux folder in root of the dvd.
Markymoo
Yes FBi_ moving the isoinux folder to root cures the loading of knoppix boot screen while booting another os. I thought i tried this already and it failed. I was messing around with isolinux.bin at the time. I was trying to hexedit isolinux.bin so i could have isolinux in the knoppix folder but isolinux.bin checks itself for modification and results in checksum error. Trying too hard i guess.

I update the mini-guide to reflect this.

Well Done FBi_! You did good biggrin.gif
Tuxer
Hi there again :-)

Sorry but moving the isolinux folder to the root doesn't work for me :-(

Any other suggestions?... besides from getting that annoying bootscreen it works perfectly....
FBi_
Yes, there's another problem.

Anything started via memdisk brings the knoppix boot screen if the isolinux folder is in /boot or root sad.gif

the maker of memdisk could make a update to ignore this folder newwink.gif
Tuxer
So putting it in a different folder should solve it....?

I'll try it ! Thx!
Tuxer
Putting it in a different folder works!

Thx!
Markymoo
is that why u getting problems coz u r using memdisk??
FBi_
yes, when i start the .ima files via memdisk i get the knoppix screen. when bcdw is used, there is no knoppix screen.

e.g. ghost doesn't work with bcdw, cause the disks are write protected?!?!? "it can't write to disk" was the error message.

UBCD uses memdisk also. When I start any program of the UBCD on my AIO DVD, then the knoppix screen appears.

that is really bad *G*


Tuxer wrote:
QUOTE
Putting it in a different folder works!

Thx!


in what folder exactly have you put it? and how do you start it?

if $lastKey == key[4]; then bcdw /images/isolinux/isolinux.bin
doesn't work for me sad.gif
ArmyDoc
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:
CODE
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... realmad.gif realmad.gif
FBi_
When i put the isolinux in any other folder than /boot or / i get the following error message confused.gif

what do i have to put in there to boot knoppix?

the isolinux folder is located in /LINUX/


-------------------------------------------------------------------

I found another guide to boot the latest knoppix.

http://www.sadyc.net/anyCDintoUBCD.html

The only problem is that the floppyimage is 2,88 mb and the files are about 4 mb.

so take his image as seed image in EasyBoot and create a 4320 kbyte image. then copy the file ldlinux.sys from the 2,88mb diskimage in the 4,3mb diskimage, rename the isolinux.cfg to syslinux.cfg and put all files from the isolinux folder (except boot.cat and isolinux.bin) in the 4,3mb diskimage.

if ($lastKey == key[k]); then bcdw /images/diskimage.img


There's no Knoppix bootscreen anymore when using memdisk or diskemu for other apps woot.gif

I hope this is the final solution for this problem.
Markymoo
Thats why i mentioned dont put in anywhere else other than boot and root.
Tuxer
-But Markymoo you have the same problem with the bootscreen or what?

-FBi gonna try your thing in the morning smile.gif
thx...!
Markymoo
no i dont using bcdw in root
Tuxer
****, well i tried using the 4 meg image, but this doesn't work... still got the bootscreen.....

Almost giving up......
FBi_
Hi!

i have attached the 4320.img with the ldlinux.sys inside. just rename your isolinux.cfg to syslinux.cfg and add the files of your isolinux dir (except boot.cat and isolinux.bin) with winimage.

you have to delete the isolinux folder of course. now the knoppix bootscreen has no change to come up.

it works great.

@Markymoo

QUOTE
no i dont using bcdw in root


what do you mean? you don't use bcdw at all? or you haven't the isolinux folder in root?

cu
FBi
Markymoo
i dont get the flash of knoppix screen while using bcdw,isolinux in root but i have had it while isolinux in boot folder. A bin connected graphic file is getting loaded somewhere i look into it just short of time lately.
FBi_
QUOTE (Markymoo @ Jun 6 2004, 07:00 PM)
i dont get the flash of knoppix screen while using bcdw,isolinux in root but i have had it while isolinux in boot folder. A bin connected graphic file is getting loaded somewhere i look into it just short of time lately.

you mean you have the isolinux.bin etc in root?
Markymoo
right i have isolinux.bin in isolinux folder
atlas95
At the root of knoppix cd, there are on folder boot and oe folder KNOPPIX.
I must extract the folder KNOPPIx at the root of my dvd? right?
or I must extract all files of knoppix cd in one folder name KNOPPIX at the root of dvd? ...
Godzilla
@ all
Can anybody summarizes the solution?

@FBi_
Oder kannst du das nochmal auf deutsch erklären?? newwink.gif

I use the cdmenu.cmd from http://gosh.msfnhosting.com/part1.htm .

One example to run an image (if it is different to cdshell):
onkey 4 run UBCD.DAT
If I need bcdw, you must explain, how I use it.

Thanks
desquinn
OK I just went through this and have a few less hairs than I began with. But Mostly my own fault smile.gif

you need to use the j1 switch by the looks of it.
You extract the Knoppix folder from the iso and put it at the root of your AIO dvd.
you extract the boot/isolinux folder and put that under boot on the AIO root.
you download the bcdw module from cdshell page and extract that to the AIO/boot folder
add the bcdw /boot/isolinux/isolinux.bin to the cdshell.ini file and you should be good to go

HTH some people
prathapml
QUOTE (desquinn @ Aug 18 2004, 05:03 AM)
OK I just went through this and have a few less hairs than I began with.
LOL - you do seem to have a good sense of humour, don't you? laugh.gif

I was looking for something like that - so yes, it helps thank you!
FBi_
Hi Folks!

I tried "my" way again with the Knoppix Version v3.6 (KNOPPIX_V3.6-2004-08-16-DE.iso) and it works.

Just follow these steps:

-Copy the folder (cdrom:\boot\)ISOLINUX folder from cd to your harddisk

-Rename the isolinux.cfg to syslinux.cfg and DELETE boot.cat & isolinux.bin

-Download the attached file and unzip it, start winimage, load/open the file

-Put all files from ISOLINUX folder on your harddisk into the image file

There should be 12 files in your image: boot.msg, f2, f3, german.kbd, ldlinux.sys, linux24, linux26, logo.16, memtest, minirt24.gz, minirt26.gz, syslinux.cfg

-If that's correct SAVE the image


You have to put this image in your AIODVD folder. I have a folder called images and put there all my images (also the 4320.img) i need, and i start them via cdshell with the following line

CODE
if ($lastKey == key[k]); then bcdw /images/4320.img


If there are any problems, read the above 2-3 times newwink.gif

When there are still problems, let me know and i'll try to help you.

@Godzilla
Ich denke, das ist einfach ausgedrückt. Ich habe grade keinen Bock das zu übersetzen newwink.gif

Dieses cdmenu.cmd habe ich noch nicht getestet.


cU
FBi
thracx
After a few hours, I finally got Knoppix v3.7 running flawlessly off of my AIO-DVD (which includes UBCD4Win v2.41, which uses Bart's PEBuilder v3.1.3). For me, it came down to one simple problem: The 'Knoppix' folder in the root of my AIO-DVD was marked as 'hidden'.

I hide the 'PRO1', 'UBCD', 'CDSH', etc, folders to make the DVD 'look' nicer (only my Setup and Software folders and a few files are normally visable). Hiding the 'Knoppix' folder causes Knoppix to give the error message:

CODE
Can't find KNOPPIX filesystem, sorry.
Dropping you to a (very limited) shell.
Press reset button to quit.


I hope this helps some of you.


For those of you new to this thread looking for a quickfix, this is what I did:
1. Download KNOPPIX_V3.7-2004-12-08-EN.iso from http://www.knoppix.net/.
2. Open this file file in WinRAR.
3. Extract the 'boot/isolinux' and the 'KNOPPIX' folders to the root directory of your AIO-DVD.
4. Add the following line to cdshell.ini:
CODE
if $lastKey == key[3]; then bcdw boot /isolinux/isolinux.bin

5. You may mark the 'boot' folder as hidden if you like.
6. Do NOT mark the 'KNOPPIX' folder as hidden.
FBi_
your way works, of course. but there's the problem with the knoppix bootscreen. when you boot other tools like e.g. Partition Magic it will flash the Knoppix bootscreen and then boot to Partition Magic. it's only a cosmetic problem, but with my mentioned way it works without this flashing knoppix bootscreen. i've tested it with KNOPPIX_V3.8.1-2005-04-08-DE.iso

it's correct that the knoppix folder must not be marked as hidden.

cu
FBi
hooovahh
That's great, I got my DSL to work on my Ultimate DVD, but does any one know about the new Suse Live DVD? or Lindows Live? I'm trying to get these to also work and their structure is much different.

Also does any one know how to make xp and 2000 and 2003 install from a spot other than I386? I've found several PDFs and I can't get them to work. It will eventually install but I have to tell it like 30 times during the install to look in the right directory other than I386.
Slimmi
could anyone please please please sum this up for me? cause i'm having some problems, i'm trying to add a Helix boot cd on to my dvd but that doesn't have all thouse boot files you guys are talking about, and unfortunaly i'm not good with linux. I'm trying to get this to work, and i've been looking through the whole page msfn.org page as well as i could, only to find nothing that can actually help me here, the system is still knoppix but only a build 2.6.10 and i can't find any way for it to boot, please help?
byte.chaser
Sorry i know this is a bit of an old thread but it relates to my issue..

trying to get knoppix v-4 to run off my AIO dvd. Has latest UBCD (dos) on it and win xp so far. All is working except knoppix. I dont know if i am using a different version of bcdw but when i run
CODE
bcdw /isolinux/isolinux.bin
I get an error saying invalid BCDW command.
I have it set up in cdshell menu like this

CODE
if ($lastKey == key[f1]); then bcdw /ISOLINUX/isolinux.bin
I dont know if that matters or not though.

I used cdimage like this to make the iso, then used virtual pc to test.
CODE
E:\>start cdimage.exe -lAIODVD -h -j1 -b\AIO-DVD\BOOT\loader.bin -o -m -yd -k \AIO-DVD E:\AIODVD.iso


Sounds like a syntax error or something.. anyone have any suggestions?


EDIT: Very sorry everyone, I did do a search in the forum, nothing came up... however IF I had spelt BCDW correctly I would have found a post stating bcdw v 2 has different syntax...

CODE
if ($lastKey == key[f1]); then bcdw boot /ISOLINUX/isolinux.bin


again sorry for the silly post :/
JohnSteven
Hi byte.chaser,

Here's the syntax I'm using;

CODE
if $lastKey == key[5]; then memdisk /4320.IMA


Go to post #41 and download his image file and give it a go.
Daemonforce
I am using this guide to make a linux multiboot. Right now I'm working on DSL and I would like to make the KNOPPIX File System specifically reserved. How can I change /KNOPPIX/KNOPPIX to DSLINUX/KNOPPIX or better yet KNOPPIX/DSLINUX without screwing this up?

The command I use is:
if $lastKey == key[a]; then memdisk /DSLINUX.IMA

I plan on also putting in:
ChaOS(if I ever get a look at it)
FreeNAS
IP Cop
PHLAK
RIP
Slax

Some of these aren't even based on Knoppix. Can you tell me how you created 4320.img and what it is exactly? I would really like to wrap this up in the next few days. unsure.gif




Google Internet Forums Unattended CD/DVD Guide

This is a "lo-fi" version of our main content. To view the full version with more information, formatting and images, please click here.