The page at
http://diddy.boot-la...iles/syntax.htm isn't very clear:
- missing (rd) as valid device
- missing (hd32) (and higher bios drive numbers) as virtual CDROM/DVDROM drive
- not that clear distinction between the numbering of primary and logical partitions.
Maybe something like the following, will be more structured:
Drives/devices are numbered using the following syntax in Grub4dos:
The numbering of the hard disks starts with zero.
* (hd0) - first hard disk
* (hd1) - second hard disk
* (hd2) - third hard disk
* ....
Virtual CD drives start at (hd32):
* (hd32) - first virtual CDROM/DVDROM drive (equal to (0xA0))
* (hd33) - second virtual CDROM/DVDROM drive
* ...
* (0xFF) - last virtual CDROM/DVDROM drive (use this if (hd32) doesn't work for you)
(hd32) is a grub drive number equivalent to (0xA0). If a virtual drive is specified with a drive number greater than or equal to 0xA0, then it will be treated as a cdrom (i.e., with 2048-byte big sectors).
Floppy disks:
* (fd0) - first floppy disk
* (fd1) - second floppy disk
CD/DVD drives:
* (cd0) - first (real) CDROM/DVDROM drive
* (cd1) - second (real) CDROM/DVDROM drive
* ...
PXE drive:
* (pd) - virtual device used to designate the root director of PXE boot server
Ramdisk drive:
* (rd) - ramdisk
Partition numbering for hard disks:
- Primary partitions (numbering from 0 to 3):
* (hd#,0) - first primary partition
* (hd#,1) - second primary partition
* (hd#,2) - third primary partition
* (hd#,3) - fourth primary partition (usually an extended partition)
Examples:
* (hd0,0) - first primary partition on first hard disk
* (hd2,1) - second primary partition on third hard disk
* (hd5,3) - fourth primary partition on sixth hard disk
- Logical partitions (numbering starts from 4):
* (hd#,4) - first logical partition
* (hd#,5) - second logical partition
* (hd#,6) - third logical partition
* (hd#,7) - fourth logical partition
* (hd#,8) - fifth logical partition
* (hd#,9) - sixth logical partition
* (hd#,10) - seventh logical partition
* (hd#,11) - eight logical partition
* (hd#,12) - ninth logical partition
* (hd#,13) - tenth logical partition
* (hd#,14) - eleventh logical partition
* (hd#,15) - twelfth logical partition
* (hd#,16) - thirteenth logical partition
* (hd#,17) - fourteenth logical partition
* ...
Examples:
* (hd0,7) - fourth logical partition on first hard disk
* (hd3,10) - seventh logical partition on fourth hard disk
* (hd1,14) - eleventh logical partition on second hard disk
To get a list of all devices that grub4dos can see, press 'c' to go the command line mode and type:
root (
and press <TAB>.
Also repeat at the
ISO mapping part of the tutorial:
The "map" process is implemented using INT 13 - any disk emulation will remain accessible from an OS that uses compatible mode disk access, e.g. DOS and Windows 9x. The emulation can't however, be accessed from an OS which uses protected mode drivers (Windows NT/2000/XP/Vista, Linux, FreeBSD) once the protected mode kernel file(s) take control.
and add that Windows based boot disks can't be booted with grub4dos iso emulation, unless they are ramdisk based (link to tutorials would be nice).
This will hopefully solve the problem of newbies that try to use grub4dos iso emulation for booting windows based boot CDs (iso's), but that didn't read or didn't understand the INT 13 access problem with protected mode drivers, which is now only explained at the beginning of the map page.
Also explain that most linux based iso's won't work with grub4dos iso emulation, unless they only need a kernel and an initrd for their working.
- Linux based iso's, that only need a kernel and an initrd will work with grub4dos iso emulation because the kernel don't need to read any data from the virtual CD drive. The kernel and initrd are loaded by grub4dos from the mapped iso file (INT 13 access is still working here).
- Linux based iso's, that need other files from the mapped iso, besides the kernel and initrd, will fail to find the virtual CD drive and won't fully boot.
It would also be nice when the guide is available from:
http://diddy.boot-la...b4dos/index.htm (which seems more logical to me than
http://diddy.boot-la...os/Grub4dos.htm)
Upload also the original
README_GRUB4DOS.txt and link to it.
It will be useful for people that are searching for some more advanced examples that aren't covered in the tutorial (yet).
Also update your first post.