Better document how to do chain loading.

diff --git a/README.menu b/README.menu
index 8c358a6..b6f457a 100644 (file)
--- a/README.menu
+++ b/README.menu
@@ -47,11 +47,18 @@ MENU LABEL label
        you to have a label that isn't suitable for the command line,
        for example:
 
+       # Soft Cap Linux
        LABEL softcap
                MENU LABEL Soft Cap Linux 9.6.36
                KERNEL softcap-9.6.36.bzi
                APPEND whatever
 
+       # A very dense operating system
+       LABEL brick
+               MENU LABEL Windows CE/ME/NT
+               KERNEL chain.c32
+               APPEND hd0 2
+
 MENU HIDE
 
        (Only valid after a LABEL statement.)

diff --git a/extlinux.doc b/extlinux.doc
index 502cfc0..4a6c3a9 100644 (file)
--- a/extlinux.doc
+++ b/extlinux.doc
@@ -65,3 +65,21 @@ kernel image to still be in the log.  This is a general problem for
 boot loaders on journalling filesystems; it is not specific to
 extlinux.  The "sync" command does not flush the log on the ext3
 filesystem.
+
+
+The SYSLINUX series boot loaders support chain loading other operating
+systems via a separate module, chain.c32 (located in
+com32/modules/chain.c32).  To use it, specify a LABEL in the
+configuration file with KERNEL chain.c32 and
+APPEND [hd|fd]<number> [<partition>]
+
+For example:
+
+# Windows CE/ME/NT, a very dense operating system.
+# Second partition (2) on the first hard disk (hd0);
+# Linux would *typically* call this /dev/hda2 or /dev/sda2.
+LABEL cement
+       KERNEL chain.c32
+       APPEND hd0 2
+
+See also README.menu.