Jump to content











Photo
- - - - -

grub4dos question


  • Please log in to reply
1 reply to this topic

#1 carfan

carfan

    Frequent Member

  • Advanced user
  • 196 posts
  •  
    United States

Posted 28 December 2008 - 04:34 AM

title Boot From First CDROM
cdrom --init
map --hook
chainloader (cd0)
boot

is a basic boot menu.lst entry for grub4dos booting from a cd. What I'd like to do is boot from a specific .img file on the cd. ex:
\images\test.img. I've tried this but I get an error 15 stating the file can't be found. What am I doing wrong???

title Boot From First CDROM
cdrom --init
map --mem (cd0)/Images/test.img (cd0)
map --hook
chainloader (cd0)
boot

Thanks
-c

#2 was_jaclaz

was_jaclaz

    Finder

  • Advanced user
  • 7100 posts
  • Location:Gone in the mist
  •  
    Italy

Posted 28 December 2008 - 10:45 AM

title Boot From First CDROM
cdrom --init
map --hook
chainloader (cd0)
boot

is a basic boot menu.lst entry for grub4dos booting from a cd. What I'd like to do is boot from a specific .img file on the cd. ex:
\images\test.img. I've tried this but I get an error 15 stating the file can't be found. What am I doing wrong???

title Boot From First CDROM
cdrom --init
map --mem (cd0)/Images/test.img (cd0)
map --hook
chainloader (cd0)
boot

Thanks
-c


The cdrom --init should NOT be necessary on any "modern" motherboard.

The cdrom drive should be mapped automatically to (cd).

However you cannot (obviously :cheers:) map a floppy or HD image (containing a filesystem like FAT/NTFS) to a cd device (that should contain a CDFS filesystem). ;)

Try (if floppy image):
title floppy image on cd searched

find --set-root /images/test.img

map --mem /images/test.img (fd0)

map --hook

root (fd0)

chainloader +1

title floppy image on cd 

map --mem (cd)/images/test.img (fd0)

map --hook

root (fd0)

chainloader +1

title floppy image on cd with init

cdrom --init

map --mem (cd0)/images/test.img (fd0)

map --hook

root (fd0)

chainloader +1

Depending on the contents of the image, you may want to bypass the bootsector and directly chainload the system file or load a kernel.

Please note that the "boot" is NOT needed when the entry is inside a .lst file, it is only needed when testing from command line.

Do review the Guide:
http://diddy.boot-la...os/Grub4dos.htm
http://diddy.boot-la...s/files/map.htm
http://diddy.boot-la...s/files/cli.htm

ALWAYS try using command line when testing a menu.lst entry, you will see grub4dos "feedback" and understand where and possibly why you are making a mistake (IF you are making one :cheers:)

jaclaz




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users