So, in eco2geek's example 1, does he copy the loopback file D:\KNOPPIX\KNOPPIX from CD-Rom.Quote:
Originally Posted by j.drake
And, in the example 2, he just use KNOPPIX*.iso instead of the loopback file, right?
Thanks in advance.
Printable View
So, in eco2geek's example 1, does he copy the loopback file D:\KNOPPIX\KNOPPIX from CD-Rom.Quote:
Originally Posted by j.drake
And, in the example 2, he just use KNOPPIX*.iso instead of the loopback file, right?
Thanks in advance.
Yes, correct. And also correct that those two cheatcodes -- "fromhd", which uses the KNOPPIX loopback file, and "bootfrom", which uses the ISO -- don't mean anything to GRUB, they're parsed by the script called "linuxrc" in the miniroot.Quote:
Originally Posted by wslkelvin
Amazing job by those Japanese Knoppix guys!
So, in a nutshell, the steps to boot from NTFS either way are:
- Install GRUB
- Copy the miniroot and kernel from the Japanese Knoppix CD to somewhere on your hard drive
- Copy the ISO or the KNOPPIX file to somewhere on your hard drive
- Edit menu.lst
But it won't work in some computer, right?Quote:
Originally Posted by eco2geek
Anyway, I will try it. Thank you very much.
Wait a minute. If you have a T41 laptop, then why do you have '"hda=scsi hdb=scsi hdc=scsi hdd=scsi " in your menu.lst? Clearly, you don't have 4 SCSI HDs. And I noticed that eco2geek had that line in as well. Does this have anything to do with it? I nuked those out of mine, because I assumed that they were inapplicable to my two EIDE HDs. Could that make the difference between success and failure?Quote:
Originally Posted by ruymbeke
jd
I don't know. Did you try a cut and paste of our configs, just as a trial ?Quote:
Originally Posted by j.drake
PS: I updated my link with the "Knoppix ISO BOOT from NTFS using GRUB" package: http://s94592085.onlinehome.us/grub/grub6.zip
Gilles
I have tried, it works with "hda=scsi hdb=scsi hdc=scsi hdd=scsi ", however I haven't tried it without these parameters. My notebook is IBM ThinkPad X31 with CD-ROM, and I don't have SCSI device. Could anyone tell me what's the mean of these parameters?Quote:
Originally Posted by j.drake
I have tried it by following the instructions of this thread, and it works for the English version KNOPPIX, Japanese version KNOPPIX, and Traditional Chinese version KNOPPIX. Work both for loopback file and ISO-image.
But I still have some questions about it.
1. I use the batch file "install2win.bat" from the Japanese version CD-Rom, it install GRUB for DOS and copy the loopback file to my NTFS partition.
2. the batch file "install2win.bat" will call the other batch file "setup.bat".
3. There is a line in the "setup.bat" batch file:
%GRUBHOME%\grubinstall -d %SystemDrive% -1 %GRUBHOME%\stage1 -2 %GRUBHOME%\stage2 -m (hd%RDISK%,%PARTITION%)%GRUBDIR%\menu.lst > %GRUBHOME%\grub-installed.txt
My question is that whether it will still work if I just use the files "linux26" and "miniroot_ntfs.gz", and then use the GRUB for DOS installed by me.
What's the following line doing?
%GRUBHOME%\grubinstall -d %SystemDrive% -1 %GRUBHOME%\stage1 -2 %GRUBHOME%\stage2 -m (hd%RDISK%,%PARTITION%)%GRUBDIR%\menu.lst > %GRUBHOME%\grub-installed.txt
Both Kanotix and Knoppix Japanese Edition seem to want the "hda=scsi...(etc)" parameter when booting the CD from GRUB. I use "hda=scsi" through "hdd=scsi" because I have two hard drives and two optical drives (hda through hdd). Whether it will work without that parameter, I do not know. If you've just got two drives, just use "hda=scsi" and "hdb=scsi", although the extras won't hurt anything.Quote:
Originally Posted by wslkevin
Yes, it will.Quote:
Originally Posted by wslkevin
Knoppix Japanese Edition uses a version of GRUB for Windows originally made for a Linux distro named Topologilinux, which will run off your NTFS partition. It actually writes to your hard drive during installation and must be reinstalled if you defrag. That line you quoted is installing it using "grubinstall.exe".Quote:
Originally Posted by wslkevin
ruymbeke's version of GRUB evidently does not write to the hard drive during installation.
Whichever one you use, the format of "menu.lst" should be exactly the same.
The standard grub installer copy or dd (disk dump) the stage1 and stage2 grub binaries into the boot sectors of the floppy, partition or disk which I don't really like when running a corporate xp/ntfs computer. These modified sectors are not seen as a file by the ntfs file system and cannot be simply deleted or removed by the explorer, as an example. You need some special tool, or the xp install cd to revert back the way it was before installing grub.Quote:
Originally Posted by eco2geek
The grldr and boot.ini hook is for me much more "clean" and much easier to install and remove: modify the boot.ini text file and copy/delete some files. For the 98/me users, grub.exe can be started from dos and from a fat 16/32 partition, floppy disk, or even a usb key ...
Please note that all the files required to boot knoppix from the ISO could be located anywhere on the disk assuming that the menu.lst and boot.ini are modified accordingly, but the c:/boot/grub/menu.lst which default location is hardcoded within the grub binary. To be exact the /boot/grub/menu.lst of the first partition of the first drive.
PS: I can boot from the ISO file being in my NTFS partition without using any of these "hda/b/...=scsi". Please find below what I am using to boot from the ISO in my menu.lst:
title Knoppix 3.6 kernel 2.6 from NTFS hda1 ISO scan
kernel (hd0,0)/boot/knoppix.36/linux26 ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 nomce quiet bootfrom=/dev/hda1/boot/knoppix.36/*.iso config=scan home=scan
initrd (hd0,0)/boot/knoppix.36/miniroot_ntfs.gz
boot
Gilles
[quote="eco2geek"]Thanks, eco2geek.Quote:
Originally Posted by wslkevin
I have successfuly boot KNOPPIX up off the NTFS partition without the parameter "hda=scsi ............".
===
Could I ask a question about Topologilinux here? I have tried Topologilinux and can boot it up using CD-Rom. However, it failed when I use GRUB to boot up. There are two situations:
a. Use the grubinstall/ntfsinstall of the CD-Rom, and it stopped at "stage2" and displayed "blocklist failed". As a result, I can boot it up using GRUB.
b. I use my pre-installed GRUB for DOS to boot it, the content of men.lst is
root (hd0,0)
kernel /boot/bzImage root=/dev/loop7 ro
initrd /boot/initrd.gz
or
kernel (hd0,0)/boot/bzImage root=/dev/loop7 ro
initrd (hd0,0)/boot/initrd.gz
Then it said "Inconsistent filesystem struction" when running the "kernel ..." line.
What should I do to solve this problem?
1. I have used the batch file "install2win.bat" from the Japanese KNOPPIX CD-Rom, and it installed GRUB to my computer using "grubinstall.exe".Quote:
Originally Posted by ruymbeke
How can I remove the grub now? Is it just simply remove the folder "C:\boot"? In which command, the installer will write something to my boot sector?
2. Before installed the GRUB from Japanese KNOPPIX CD-Rom, I have installed (actually just as what you said - copied all files to C:\ and C:\boot). I can find stage1 and stage2 under the folder C:\boot? Did it also influe my boot sector?
3. Is it possible to use a image file located in a NTFS partition for "home" in the cheatcode? For example, "knoppix ..... home=/dev/hda1/KNOPPIX/home.img" (It assume /dev/hda1 is a NTFS partition in which the KNO*.ISO located)?
Let me asnwer my question first, then could you tell me whether I am right or wrong? Thanks.Quote:
Originally Posted by wslkevin
3. It definetly can set the "home" to hda1 which is a NTFS partition before the Japanese kernel has the ntfs.o built-in. After boot to knoppix, it is must to mount the partition /dev/hda1 as captive-NTFS, then the user can read/write/modify the content of "home". However, it isn't a safe way to modify NTFS partition because captive use the MS NTFS driver which isn't stable for Linux.
Am I right? Could you also please answer question 1 and 2?
Thanks very much.
Removing the C:\boot will free up some disk space, but will not remove the grub boot hook. I suppose that the grubinstall.exe writes into the boot sectors. You should probalby have look at: http://www.knoppix.net/forum/viewtopic.php?t=3311 , and/or tryQuote:
Originally Posted by wslkevin
1) Boot w/ win98 boot floppy, at the a: propmt enter: fdisk /mbr
2)Boot w/ XP or WIN2k cd into recovery mode and run: fixmbr
No. You have to start grub and run the installer to do it, or an other installer program as grubinstall.exe. BTW, I do not use stage1 and stage2 since they are already part of both the grldr and grub.exe I have been talking about in my zip and setup.Quote:
Originally Posted by wslkevin
I did not try it yet, and I would be very carefull with that. Try it on a test system, not a corporate computer. As I understand it, ntfs read only is the default after a knoppix boot and is totally safe. This linux driver cannot be easily used and is not safe to use for write access. For that reason people use the capture script and the linux read only driver to look for the MS drivers into the nt partition and then use these MS drivers to write into the ntfs partition.Quote:
Originally Posted by wslkevin
So, I may be wrong, but I think that since you may want to have write access into your home directory, you would need at boot time to: first use the linux ntfs driver and the capture script to get the MS drivers and then remount the ntfs partition in rw mode and finally mount the /home/knoppix directory from the knoppix.img being into that ntfs partition. This can be done, but ... YAKA (just do it...)
Cheers, Gilles
Being inspired by the japanese boot ramdisk, I modified the minirt24.gz to allow knoppix 3.6 to boot from ntfs with the kernel 2.4. Here is the link:
http://s94592085.onlinehome.us/grub/minirt24_ntfs.gz
I also modified the the /ramdisk memory allocation to use 3/5 (instead of 4/5) of the total memory available. This should help KDE to run when using a persistent home. Here is the link for the modified boot ramdisk for the 2.6 kernel:
http://s94592085.onlinehome.us/grub/minirt26_ntfs.gz
And my updated zip package:
http://s94592085.onlinehome.us/grub/grub7.zip
And my menu.lst entries are as follow:
title Knoppix 3.6 kernel 2.6 from NTFS hda1 ISO scan
kernel (hd0,0)/boot/knoppix.36/linux26 ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 nomce quiet bootfrom=/dev/hda1/boot/knoppix.36/*.iso config=scan home=scan
initrd (hd0,0)/boot/knoppix.36/minirt26_ntfs.gz
boot
title Knoppix 3.6 kernel 2.4 from NTFS hda1 ISO scan
kernel (hd0,0)/boot/knoppix.36/linux24 ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 nomce quiet bootfrom=/dev/hda1/boot/knoppix.36/*.iso config=scan home=scan
initrd (hd0,0)/boot/knoppix.36/minirt24_ntfs.gz
boot
Enjoy, Gilles
PS for Fabianx:
Since we finally got the ISO NTFS Boot working for knoppix 3.6 with both the 2.4 and 2.6 kernel. Would you please consider adding this feature in the next Knoppix release ? Thank you for your time and consideration.
j.drake, my deep apologizes again. The linux26 kernel I was using in my zip file was the one from the 3.4 release which explain all your errors. Could you please replace the \boot\Knoppix.36\linux26 kernel with this file:Quote:
Originally Posted by j.drake
http://s94592085.onlinehome.us/grub/linux26
I updated also the link: http://s94592085.onlinehome.us/grub/grub7.zip
Please forgive me... Gilles
AWESOME!!! :) thank you so much, this is _great_!Quote:
Originally Posted by ruymbeke
Now, a Windows .bat that does all (including editing the Windows boot loader textfile to load GRUB to load Knoppix) automagically would be nice...
Something like this should do it...Quote:
Originally Posted by probono
set path1="Root_Of_NTFS"
set path2="*.iso"
xcopy/S %path1 c:\
copy %path2 c:\boot\Knoppix.36
attrib -R c:\boot.ini
echo c:\grldr="Start Grub" >> c:\boot.ini
attrib +R c:\boot.ini
set path1=
set path2=
Cheers, Gilles
Quote:
Originally Posted by ruymbeke
FNA!!!! IT WORKS!!!
I'm writing this from an ISO 3.6/2.6 boot, straight from your menu.lst!! Now to make my changes for PH, etc.
No apologies needed. I'm just glad I didn't have to give up in frustration.
Thank you -- U DA MAN, GILLES!!!
jd
I still have the problem: When using a PH (persistent Home) having larger a size than the Ram memory of the computer, KDE doesn't start. I have an error message from KDE saying that it requires at least 88MB of Ram to run properly. Reason why I modified the /ramdisk size allocation within the linuxrc of the minitxx.gz. I now do have more Ram available since the ramdisk doesn't use it all, but KDE is still complaining about more free memory...Quote:
Originally Posted by ruymbeke
Does anyone experience the same problem ? Any solution ?
Thanks, Gilles
I modified the the /ramdisk memory allocation again: I put back the 4/5 as a default as it was before, but I added a cheatcode: "ramdisk=xxx" xxx being the size of the ramdisk in kb. So if ramdisk=32000 exists ==> a /ramdisk of 32MB will be created otherwise a /ramdisk of 4/5 of the system memory will be created. Here are the links and my menu.lst:Quote:
Originally Posted by ruymbeke
http://s94592085.onlinehome.us/grub/minirt24_ntfs.gz
http://s94592085.onlinehome.us/grub/minirt26_ntfs.gz
http://s94592085.onlinehome.us/grub/grub8.zip
title Knoppix 3.6 kernel 2.6 from NTFS hda1 ISO scan ramdisk=32MB
kernel (hd0,0)/boot/knoppix.36/linux26 ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 nomce quiet bootfrom=/dev/hda1/boot/knoppix.36/*.iso config=scan home=scan ramdisk=32768
initrd (hd0,0)/boot/knoppix.36/minirt26_ntfs.gz
boot
title Knoppix 3.6 kernel 2.4 from NTFS hda1 ISO scan ramdisk=32MB
kernel (hd0,0)/boot/knoppix.36/linux24 ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 nomce quiet bootfrom=/dev/hda1/boot/knoppix.36/*.iso config=scan home=scan ramdisk=32768
initrd (hd0,0)/boot/knoppix.36/minirt24_ntfs.gz
boot
Enjoy, Gilles
Just wanted to suggest appending the cheatcode "noprompt" in the GRUB stanzas. At shutdown or restart, Knoppix won't prompt you to remove the CD and push Enter, Given that this method doesn't use a CD, it seemed appropriate, and saves a little time and annoyance.
jd
There is just one HDD in my notebook, there are two partitions in the HDD. The KNOPPIX ISO-image is stored in the first partition.
I can boot up the KNOPPIX, and can mount /dev/hda1 successful. But can't mount /dev/hda5 (the second partition). [The command is "mount -t ntfs /dev/hda5 /mnt/hdz5"] It displays:
"/dev/hda5 has already mounted, or /mnt/hda5 is busy".
What can I do? Thank you very much.
First of all congratulations to Ruymbeke, Eco2Geek, J.Drake and the nameless Japanese for driving this project to the end we have all been wanting. I have been following this thread since its inception, eagerly awaiting its outcome.
Being away from work for a few days I have today spent some time reading the thread in total, in order to decide what I need to download and the steps I need to take to implement the grub boot, both on an NTFS machine and on a Windows 98 FAT32 machine.
I have some questions, specifically to Ruymbeke, I guess.
When grub3.zip was released it was for 3.4 Knoppix only and worked with NTFS, FAT16, FAT32.
As I understand it grub4.zip introduced stuff which in theory made it work with 3.6 Knoppix. And was only for kernal 2.6.
I am not sure what grub5.zip or grub6.zip introduced.
Grub7.zip included the capability to boot kernal 2.4, adjusted memory allocation and then the correct 3.6 version of the linux26 was added to it. I presume the new 2.4 stuff was reason for a sudden jump in file size (over 5MB to over 8MB - a bit annoying as I only have dial up when not at work!)
Grub8.zip makes memory allocation more flexible.
The question now is does grub8.zip work with NTFS, FAT16 and FAT32 and can it be used on a Windows 98 computer? If not, which version of grub.zip is required to provide the boot up on a Windows 98 computer?
Earlier in the thread it was pointed out that Makeflo needs Windows 2K/XP to make Grub floppies. Can you confirm this will NOT work with Windows 98. Making floppies does not seem to be a task specific to later Windows versions.
It seems that the zip file has to be updated for each new Knoppix version that gets released, because the miniroot and kernal files have to change. Does that mean we are reliant on the Japanese to provide these updates for future versions?
Does anyone else think it is strange that the Linux Tag German Knoppix forum, the Developers Forum and Fabian have all seem to have disappeared within the last 2 months? I'm sure Fabian would have been very useful to solving this problem if he had responded to Ruymbeke's plea for help. I know we cannot expect Klaus or Fabian to do more than the invaluable work they have already done but I do find these disappearances slightly worrying.
Thanks for any help you can provide to my queries above.
ICPUG
Are you using the home=scan or config=scan cheatcode ? Do you have something like a /dev/hda5/knoppix.img ? If so, the partition is already mounted and used by your home directory.Quote:
Originally Posted by wslkevin
Very good idea, I will try it asap... but I will gone most of next week.Quote:
Originally Posted by j.drake
Yes. Grub.exe can be launched from DOS/98/ME (without emm386.exe): either from the command prompt, from the autoexec.bat, or from the config.sys using SHELL=grub.exe. NTFS support has been added to the existing FAT16/32, ext2, ... functionality.Quote:
Originally Posted by ICPUG
I confirm that makeflo will NOT work with Windows 98. The tool dd.exe (part of the cygwin distribution) that I am using requires 2000 or XP to have a low level (block device) access to the drives. This is not available within 98/ME. I can make a grub boot floppy disk image if you want, ... Or you can make it yourself from knoppix using this:Quote:
Originally Posted by ICPUG
dd if=stage1 of=/dev/fd0 bs=512 count=1
dd if=stage2 of=/dev/fd0 bs=512 seek=1
No. It took me a while to understand the changes made in the japanese version, and I hope that I will be able to update the next release without too much trouble, if this patch is not going to be part of the next release.Quote:
Originally Posted by ICPUG
Most of the time I also have provided links to the updated files: minirt24_ntfs.tgz, minirt24_ntfs.tgz, ...Quote:
Originally Posted by ICPUG
Agreed !Quote:
Originally Posted by ICPUG
Cheers, Gilles
The content of menu.lst isQuote:
Originally Posted by ruymbeke
title KNOPPIX BV1AL (ISO)(Tranditional Chinese,normal, BV1AL, short)
root (hd0,0)
kernel /knoppix/linux26 bootfrom=/dev/hda5/KNOPPIX*.iso knoppix_name=KNOPPIX ramdisk_size=100000 init=/etc/init ro lang=tw vga=791 noprompt noapm lcd ttf2ram
initrd /knoppix/miniroot_ntfs.gz
Could you tell me how to access the partition /dev/hda5? Thanks in advance.
You are booting from /dev/hda5/KNOPPIX*.iso !Quote:
Originally Posted by wslkevin
So /mnt/hda5 is already mounted by the boot script as read only, and as far as I know, it would be very dangerous to remount this partition as rw using ntfs-capture even if you could force it. But you should be able to mount /dev/hda1.
Gilles
The method provided in this thread can make one Traditional Chinese KNOPPIX ISO-image (say, K1) booting up off NTFS, but it doesn't work for another one Traditional Chinese KNOPPIX ISO-image (say, K2).
The content of my menu.lst for "K2":
### The kernel file linux24 is from ruymbeke, it can't boot up KNOPPIX K2, and said "Inconsistent Filesystem Structure" when running the line "kernel ..."
title KNOPPIX pureKDE (ISO)(kernel 2.4.26, Tranditional Chinese,normal, pureKDE, short)
root (hd0,0)
kernel /knoppix/linux24 bootfrom=/dev/hda1/KNOPPIX*.iso knoppix_name=KNOPPIX ramdisk_size=100000 init=/etc/init ro lang=tw vga=791 noprompt noapm lcd ttf2ram
initrd /knoppix/minirt24_ntfs.gz
### The kernel linux26 is from the Japanese one, it can boot up KNOPPIX K2, but said "can't find the file /lib/modules/2.6.7/modules.dep", and some devices, i.e. NIC, doesn't work
title KNOPPIX pureKDE (ISO)(kernel 2.6.7, Tranditional Chinese,normal, pureKDE, short)
root (hd0,0)
kernel /knoppix/linux26 bootfrom=/dev/hda1/KNOPPIX*.iso knoppix_name=KNOPPIX ramdisk_size=100000 init=/etc/init ro lang=tw vga=791 noprompt noapm lcd ttf2ram
initrd /knoppix/miniroot_ntfs.gz
### The kernel file linux265 is from the CD of KNOPPIX K2, and I rename it to linux265, it can't boot up KNOPPIX K2, and said "Inconsistent Filesystem Structure" when running the line "kernel ..."
title KNOPPIX pureKDE (ISO)(kernel 2.6.5, Tranditional Chinese,normal, pureKDE, short)
root (hd0,0)
kernel /knoppix/linux265 bootfrom=/dev/hda1/KNOPPIX*.iso knoppix_name=KNOPPIX ramdisk_size=100000 init=/etc/init ro lang=tw vga=791 noprompt noapm lcd ttf2ram
initrd /knoppix/miniroot_ntfs.gz
P.S. There are two folders name 2.4.27 and 2.6.5 under /lib/modules.
Is that a problem of the kernel file? How can I solve it?
Thanks very much in advance.
Hope no one minds, but I summarized this method into the WIKI here , and linked it from the PoorMan'sInstall page. I also separated out the Basic Poor Man's instructions into a different file, so now a new user has introductory information to a PMI, with links to either a Basic or WinPartition PMI how-tos. At 11 pages so far, it's gotten to be quite a chore to sift through the successes and frustrations of this thread to get to the method.
Ruymbeke, if you have any concerns about pointing back to your site to download the files, we can always point somewhere else if you'd prefer. I linked to the grub8 version.
jd
Well, you have to be sure that the kernel, the drivers within the ramdisk, and the ISO match the same release. I suggest that you use the full name of the ISO file in the bootfrom cheatcode (to be sure that you use the correct ISO file), use the kernel extracted from that ISO file, and if the drivers of the ramdisk minirt2x_ntfs.gz are compatible with your ISO file, ... it may work.Quote:
Originally Posted by wslkevin
Great job !Quote:
Originally Posted by j.drake
No problem, you can keep it as is.Quote:
Originally Posted by j.drake
Thank you, Gilles
Yes, the kernel file is extract from the ISO file.Quote:
Originally Posted by ruymbeke
There is just one ISO file in /dev/hda1, so I think it is okey to use the short form.
What is the driver within the ramdisk? How can I verify that the drivers are compatible with my ISO file? If they are not compatible, how can I make it compatible?
I am so sorry that I have such questions, maybe they are very simple questions, but could you kindly tell to how to?
Thanks very much in advance.
Here are the links to the gzipped tar (tgz) of the content of the ramdisks I am using at boot time:Quote:
Originally Posted by wslkevin
http://s94592085.onlinehome.us/grub/minirt24_ntfs.tgz
http://s94592085.onlinehome.us/grub/minirt26_ntfs.tgz
And hopefully you will verify that the /modules files from these tgz match the ones you have in your system after having booted from your ISO file. You can do that by comparing their md5 or just by looking at the file length and date. If the drivers are different you may need to make your own boot ramdisk ... What distribution or ISO file are you using ?
Good luck, Gilles
I am using KNOPPIX34pureKDE20040720m3.iso which is downloaded from ftp://ftp3.tnc.edu.tw/KNOPPIX/health, and it's a Traditional Chinese version of KNOPPIX.Quote:
Originally Posted by ruymbeke
After I boot it up using CD-Rom, I foudn that there are two folders name 2.4.27 and 2.6.5 under /lib/modules. I am already using the files you provided.
Could you specify which two folder should I compare to each other?
I tried three config in menu.lst
###
### The kernel file linux24 and ramdisk (minirt24_ntfs.gz) are from ruymbeke, it can't boot up KNOPPIX K2, and said "Inconsistent Filesystem Structure" when running the line "kernel ..."
###
title KNOPPIX pureKDE (ISO)(kernel 2.4.26, Tranditional Chinese,normal, pureKDE, short)
root (hd0,0)
kernel /knoppix/linux24 bootfrom=/dev/hda1/KNOPPIX*.iso knoppix_name=KNOPPIX ramdisk_size=100000 init=/etc/init ro lang=tw vga=791 noprompt noapm lcd ttf2ram
initrd /knoppix/minirt24_ntfs.gz
###
### The kernel linux26 and ramdisk miniroot_ntfs.gz is from the Japanese one, it can boot up KNOPPIX K2, but said "can't find the file /lib/modules/2.6.7/modules.dep", and some devices, i.e. NIC, doesn't work
###
title KNOPPIX pureKDE (ISO)(kernel 2.6.7, Tranditional Chinese,normal, pureKDE, short)
root (hd0,0)
kernel /knoppix/linux26 bootfrom=/dev/hda1/KNOPPIX*.iso knoppix_name=KNOPPIX ramdisk_size=100000 init=/etc/init ro lang=tw vga=791 noprompt noapm lcd ttf2ram
initrd /knoppix/miniroot_ntfs.gz
###
### The kernel file linux265 is from the CD of KNOPPIX K2, and I rename it to linux265, and the ramdisk miniroot_ntfs.gz is from Japanese one , it can't boot up KNOPPIX K2, and said "Inconsistent Filesystem Structure" when running the line "kernel ..."
###
title KNOPPIX pureKDE (ISO)(kernel 2.6.5, Tranditional Chinese,normal, pureKDE, short)
root (hd0,0)
kernel /knoppix/linux265 bootfrom=/dev/hda1/KNOPPIX*.iso knoppix_name=KNOPPIX ramdisk_size=100000 init=/etc/init ro lang=tw vga=791 noprompt noapm lcd ttf2ram
initrd /knoppix/miniroot_ntfs.gz
Thank you very much in advance.
ruymbeke - thank you *VERY* much for the work you have put in on this. I am posting from a laptop I've just booted from a USB flash disk with the ISO on an NTFS partition - no CD required in the drive. This is what I wanted. I need to hone some of the boot 'cheatcodes' and create a permanent home on the second partition of the flash disk - but it looks to be mostly there.
Many, many thanks again. I echo the request to make this part of Knoppix' standard functionality.
Regards,
semreh
Done in http://s94592085.onlinehome.us/grub/grub9.zipQuote:
Originally Posted by j.drake
Just by looking at the filename, is this file a knoppix 3.4 flavor ?Quote:
Originally Posted by wslkevin
The files I provided are for knoppix 3.6 and are not compatible with 3.4.
You may try the miniroot_ntfs.gz of the japanese 3.4 release...
Cheers, Gilles
I have been using the approach outlined in this thread to boot Knoppix 3.6 from My Windows 98 PC which has a FAT 32 partition. My menu.1st, based on what Eco2Geek suggested on Page 8 is as follows:
title Knoppix 3.6 kernel 2.4 from FAT32 hda1 cloop scan
kernel (hd0,0)/boot/knoppix.36/linux24 ramdisk_size=100000 knoppix_dir=/boot/knoppix.36 knoppix_name=KNOPPIX init=/etc/init lang=uk nomce
initrd (hd0,0)/boot/knoppix.36/minirt24_ntfs.gz
title Memory test
kernel (hd0,0)/boot/knoppix.36/memtest
I have got it to work but there are two problems.
First - As Knoppix boots up it still looks to the CDROM for the cloop file before eventually giving up and then, after appearing to search every device imaginable, starts off from where I put it in \boot\knoppix.36 directory. Is there any way to stop it searching for the CD-ROM and start the boot instantly from \boot\knoppix.36?
The second problem is that I have to use a floppy formatted as a system disk with Windows 98 and a simple autoexec.bat file which says:
c:
cd \
grub
This is OK, but I would much prefer to have it boot up from the hard drive, like has been done with the NTFS system. Ruymbeke suggested 3 approaches; start grub from the command prompt, the autoexec.bat or config.sys with device=grub.exe.
From the command prompt I got the message:
Must run in real mode or ring 0 of protected mode. Cannot run in vm86 mode.
I guessed this meant that starting Windows 98 put things into the wrong mode so decided to modify my config.sys to give a menu system as follows:
[menu]
menuitem=WINDOWS, Start Windows
menuitem=KNOPPIX, Start Knoppix
menudefault=WINDOWS,30
menucolor=7,0
[KNOPPIX]
device=grub.exe
[WINDOWS]
device=c:\realmode\oakcdrom.sys /D:mscd001
dos=high,umb
buffers=40
DEVICE=C:\WINDOWS\EMM386.EXE
device=c:\windows\himem.sys /testmem:off
device=c:\windows\COMMAND\display.sys con=(ega,,1)
Country=044,850,c:\windows\COMMAND\country.sys
I figured this would boot Knoppix before Windows took hold.
When I rebooted and chose Knoppix I still got the same error message and then a break into what looked like a short memory dump. Does anybody have any idea what I am doing wrong?
ICPUG
If you use the bootfrom= cheatcode it should not search for the cdrom, but as far as i know, it will still look for all the disk/devicesQuote:
Originally Posted by ICPUG
You do not need to have a boot floppy, you can do it all from the HD. I have it working on my 98 machine. If during the 98 boot you press shift-F5 and force the boot into a prompt, just type grub.exe. You can also add a menu into the config.sys as you have done and start grub from the autoexec.bat using the %config% environment variable to recognize the linux boot selection and then run c:\your_path\grub.exe. But be sure to not have emm386.exe loaded (that would explain your error message) and not run it from a 98 dos box ! You can verify that from the prompt by typing mem/c/p. Hope this will help, GillesQuote:
Originally Posted by ICPUG
PS: it looks like that the minirtxx_ntfs.tgz are also working with knoppix 3.7...
improbably missing something obvious but...I can't get this to work! (and I want to :P)
ok, so I've wanted for a little while to get Knoppix running off of the HD, and I found this handy article: http://www.knoppix.net/docs/index.php/WinPartition. I've followed that to the letter, and when I reboot, I get the option between the two OSes, and I select the GRUB. however, all it does is flash the little _ cursor at me and does nothing.
I'm not quite sure what I'm doing wrong, as I've tried multiple times (with multiple formats! -_-;)
I'm running Win2k Pro NTFS (obviously), and I modified the boot.ini accordingly, since it was set to WinXPpro.
my boot.ini contains :
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(1)\WINNT
[operating systems]
multi(0)disk(0)rdisk(0)partition(1)\WINNT="Microso ft Windows 2000 Professional" /fastdetect
c:\grldr="Start Grub"
and my menu.lst contains:
################################################## ####
# GvR Sept 24th 2004
color black/cyan yellow/cyan
timeout=15
default=0
title Default Boot on HD 0
rootnoverify (hd0,0)
chainloader +1
boot
# Knoppix Boot from a single NTFS partition hda1:
# All the files within the directory "Root_Of_NTFS" of the grub7.zip
# have to be copied into the root of the NTFS hda1 partition c:\
# but the boot.ini file (which is just here as an example,
# the line "c:\grldr="Start Grub" has been added at the end of the boot.ini)
# Copy the also the 700MB knoppix ISO file into c:\boot\knoppix.36\ directory
title Knoppix 3.6 kernel 2.6 from NTFS hda1 ISO scan ramdisk=32MB
kernel (hd0,0)/boot/knoppix.36/linux26 ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 nomce quiet bootfrom=/dev/hda1/boot/knoppix.36/knoppix.iso config=scan home=scan ramdisk=32768
initrd (hd0,0)/boot/knoppix.36/minirt26_ntfs.gz
boot
title Knoppix 3.6 kernel 2.4 from NTFS hda1 ISO scan ramdisk=32MB
kernel (hd0,0)/boot/knoppix.36/linux24 ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 nomce quiet bootfrom=/dev/hda1/boot/knoppix.36/knoppix.iso config=scan home=scan ramdisk=32768
initrd (hd0,0)/boot/knoppix.36/minirt24_ntfs.gz
boot
title Memory test
kernel (hd0,0)/boot/knoppix.36/memtest
title Win311 from Dos from Floppy image 1.44Mb, just for fun...
kernel (hd0,0)/boot/memdisk
initrd (hd0,0)/boot/win311.img
boot
################################################## ####
title Knoppix 3.6 kernel 2.6 from NTFS hda1 ISO scan (original japanese miniroot_ntfs.gz)
kernel (hd0,0)/boot/knoppix.36/linux26 ramdisk_size=100000 init=/etc/init lang=us apm=power-off vga=791 nomce quiet bootfrom=/dev/hda1/boot/knoppix.36/knoppix.iso config=scan home=scan
initrd (hd0,0)/boot/knoppix.36/miniroot_ntfs.gz
boot
################################################## ####
thanks in advance for any help! If you need more info, plz ask
I'm gonna keep working on it some more :P
-PyroFox
You may want to try to add an other line in your boot.ini as follow:Quote:
Originally Posted by PyroFox
c:\bootgrub="Start Grub (old method)" (after c:\grldr="Start Grub")
and copy the file c:\bootgrub from the GRUB.BIN directory of grub9.zip.
Let me know, cheers, Gilles
yup, that did the trick!
I guess an old computer needs a old method to work....;)
thanks you very much for your help. excellent work too :P
-PyroFox
I have today been playing with this PMI on a friend's Windows XP machine. This is the first time I have had the chance to try the procedure on an XP machine.
I have a major problem with it!
Ruymbeke stated, and J. Drake put in the procedure, that you modify the boot.ini to add the line:
C:\bootgrub="Knoppix Submenu"
I did not see how this would start grldr but did as instructed.
The result was to come up with an error message saying Windows was missing a dll (whose name I did not note), and then start Windows.
I then followed my own lead and used the following as the last line of the boot.ini:
C:\grldr="Knoppix Submenu"
This seemed to work and display the Knoppix Submenu defined by menu.1st.
Could someone explain how C:\bootgrub is supposed to call up grldr? There is no file or directory called bootgrub??? Alternatively, if I got it right with my last line the instructions need changing.
<Seeing the reply to Pyrofox after I prepared this post, maybe you missed the bootgrub file from grub8.zip which I am using??>
I am still having problems using bootfrom be it on my friend's machine or my own Windows 98.
Please bear in mind I am trying to boot the cloop file NOT an iso.
Can it be done on Windows XP at all? If so - what is the menu.1st to use?
Can it be done on Windows 98, without a delay while it searches unsuccessfully the CD-ROM drive. If so, what is the menu.1st to use?
ICPUG