*** ./mclasserase.c.osr6	Sat May 26 01:00:41 2007
--- ./mclasserase.c	Fri Mar 14 10:09:53 2008
***************
*** 86,92 ****
    int iTotalErase = 0;
  
    const int cycles = 3;		/* How many times we'll overwrite the media */
!   char odat[cycles];		/* Data for each overwrite procedure */
  
    /* Creating values for overwrite  */
    odat[0]=0xff;
--- 86,92 ----
    int iTotalErase = 0;
  
    const int cycles = 3;		/* How many times we'll overwrite the media */
!   char odat[3];		/* Data for each overwrite procedure */
  
    /* Creating values for overwrite  */
    odat[0]=0xff;
*** ./Makefile.in.osr6	Tue Feb 28 00:55:15 2006
--- ./Makefile.in	Fri Mar 14 10:09:53 2008
***************
*** 126,132 ****
  X_LIBS = @X_LIBS@
  X_EXTRA_LIBS = @X_EXTRA_LIBS@
  X_PRE_LIBS = @X_PRE_LIBS@
! CFLAGS = $(CPPFLAGS) $(DEFS) $(MYCFLAGS) -fno-strict-aliasing -I. @extraincludedir@ -I@srcdir@ $(USERCFLAGS) 
  CXXFLAGS  = $(CPPFLAGS) $(DEFS) $(MYCXXFLAGS) -I. @extraincludedir@ -I@srcdir@ $(USERCFLAGS) 
  LINK      = $(CC) $(LDFLAGS) $(USERLDFLAGS) @extralibdir@
  ALLLIBS   = $(USERLDLIBS) $(MACHDEPLIBS) $(SHLIB) $(LIBS)
--- 126,132 ----
  X_LIBS = @X_LIBS@
  X_EXTRA_LIBS = @X_EXTRA_LIBS@
  X_PRE_LIBS = @X_PRE_LIBS@
! CFLAGS = $(CPPFLAGS) $(DEFS) $(MYCFLAGS) -I. @extraincludedir@ -I@srcdir@ $(USERCFLAGS) 
  CXXFLAGS  = $(CPPFLAGS) $(DEFS) $(MYCXXFLAGS) -I. @extraincludedir@ -I@srcdir@ $(USERCFLAGS) 
  LINK      = $(CC) $(LDFLAGS) $(USERLDFLAGS) @extralibdir@
  ALLLIBS   = $(USERLDLIBS) $(MACHDEPLIBS) $(SHLIB) $(LIBS)
***************
*** 151,157 ****
  	$(CC) $(X_CCFLAGS) -c $?
  
  floppyd: floppyd.o
! 	$(LINK) $? -o $@ $(X_LDFLAGS)
  floppyd_installtest: $(OBJS4)
  	$(LINK) $(OBJS4) -o $@ $(ALLLIBS)
  
--- 151,157 ----
  	$(CC) $(X_CCFLAGS) -c $?
  
  floppyd: floppyd.o
! 	$(LINK) $? -o $@ $(X_LDFLAGS) /usr/lib/libsmbclient.a
  floppyd_installtest: $(OBJS4)
  	$(LINK) $(OBJS4) -o $@ $(ALLLIBS)
  
*** ./Install-OSR6.osr6	Fri Mar 14 10:09:53 2008
--- ./Install-OSR6	Fri Mar 14 10:09:53 2008
***************
*** 0 ****
--- 1,20 ----
+ #!/bin/sh
+ 
+ MOUT=mout-install
+ D=/u/tmp/mtools
+ P=$D/usr/share/doc/packages/mtools
+ DESTDIR=$D
+ export DESTDIR
+ 
+ [ -f $MOUT ] && mv $MOUT $MOUT-prev
+ [ -d $D ] && rm -rf $D
+ mkdir -p $D
+ 
+ make install DESTDIR=$D 2>&1 | tee $MOUT
+ 
+ [ -d $D/etc/default ] || mkdir -p $D/etc/default
+ cp mtools.conf $D/etc/default/mtools.conf
+ 
+ [ -d $P ] || mkdir -p $P
+ cp mtools.html $P/mtools.html
+ 
*** ./Configure-OSR6.osr6	Fri Mar 14 10:09:53 2008
--- ./Configure-OSR6	Fri Mar 14 10:09:53 2008
***************
*** 0 ****
--- 1,21 ----
+ #!/bin/sh
+ #
+ HOST=i586-sco-sysv5
+ CFLAGS="-O2"
+ INSTALL=/usr/gnu/bin/install
+ NM="nm -p"
+ M4=/usr/gnu/bin/m4
+ if [ "$1" = "-g" ]
+ then
+   CC="gcc -D_REENTRANT"
+   CXX="g++ -D_REENTRANT"
+   CFLAGS="$CFLAGS -Wall"
+ else
+   CC="cc -Kpthread -Kalloca"
+   CXX="CC -Kpthread -Kalloca"
+ fi
+ ac_cv_func_htons=yes
+ export CC CXX CFLAGS NM M4 INSTALL ac_cv_func_htons
+ rm -f mout-configure
+ ./configure --prefix=/usr --sysconfdir=/etc \
+             --host=$HOST --target=$HOST --build=$HOST 2>&1 | tee mout-configure
*** ./mtools.conf.osr6	Wed May  1 02:49:05 2002
--- ./mtools.conf	Fri Mar 14 10:13:12 2008
***************
*** 1,6 ****
  # Example mtools.conf files.  Uncomment the lines which correspond to
  # your architecture and comment out the "SAMPLE FILE" line below
! SAMPLE FILE
  
  # # Linux floppy drives
  # drive a: file="/dev/fd0" exclusive
--- 1,38 ----
  # Example mtools.conf files.  Uncomment the lines which correspond to
  # your architecture and comment out the "SAMPLE FILE" line below
! # SAMPLE FILE
! 
! # SCO OpenServer 6 and SCO UnixWare 7
! #
! # # Floppy disk drives
! #
! drive a: file="/dev/rdsk/f0t" exclusive
! drive b: file="/dev/rdsk/f1t" exclusive
! # Or, if you have a USB floppy drive on /dev/rdsk/c#b0t0d0p1
! # where 'c#' corresponds to the controller number that OSR6
! # "sdiconfig -l" sees and wish to use this as drive b: then 
! # uncomment the following line and comment out the drive b: setting above.
! # drive b: file="/dev/rdsk/c#b0t0d0p1" exclusive
! #  
! # # Hard disk partitions
! #  
! # MS-DOS partition of first hard disk.
! # The p1 assumes that the first partition in the fdisk table is the DOS
! # partition.  If this is not the case run fdisk to determine where the DOS
! # partition is, and update the p1 accordingly.  For more information, refer
! # to the sd01(7) man page.
! #
! drive c: file="/dev/rdsk/c0b0t0d0p1"
! #
! # MS-DOS partition of additional hard disks.
! # The second disk on your system might actually be different.  Please check
! # the name of your second hard disk, using "devattr disk2 cdevice", and, if
! # necessary, change the line below.  For more information, refer to the
! # devattr(1) man page.  The above comment for p1 applies here also.
! 
! drive d: file="/dev/rdsk/c0b0t0d0p2"
! drive e: file="/dev/rdsk/c0b0t0d0p3"
! drive f: file="/dev/rdsk/c0b0t0d0p4"
  
  # # Linux floppy drives
  # drive a: file="/dev/fd0" exclusive
*** ./mtools.html.osr6	Fri Mar 14 10:09:53 2008
--- ./mtools.html	Fri Mar 14 10:09:53 2008
***************
*** 0 ****
--- 1,4836 ----
+ <HTML>
+ <!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
+ <!-- Created on May, 31  2007 by texi2html 1.64 -->
+ <!-- 
+ Written by: Lionel Cons <Lionel.Cons@cern.ch> (original author)
+             Karl Berry  <karl@freefriends.org>
+             Olaf Bachmann <obachman@mathematik.uni-kl.de>
+             and many others.
+ Maintained by: Olaf Bachmann <obachman@mathematik.uni-kl.de>
+ Send bugs and suggestions to <texi2html@mathematik.uni-kl.de>
+  
+ -->
+ <HEAD>
+ <TITLE>Mtools: </TITLE>
+ 
+ <META NAME="description" CONTENT="Mtools: ">
+ <META NAME="keywords" CONTENT="Mtools: ">
+ <META NAME="resource-type" CONTENT="document">
+ <META NAME="distribution" CONTENT="global">
+ <META NAME="Generator" CONTENT="texi2html 1.64">
+ 
+ </HEAD>
+ 
+ <BODY LANG="" BGCOLOR="#FFFFFF" TEXT="#000000" LINK="#0000FF" VLINK="#800080" ALINK="#FF0000">
+ 
+ <A NAME="SEC_Top"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <H1>Mtools</H1></P><P>
+ 
+ <A NAME="SEC1"></A>
+ <H1> Introduction </H1>
+ <!--docid::SEC1::-->
+ Mtools is a public domain collection of tools to allow Unix systems to
+ manipulate MS-DOS files: read, write, and move around files on an MS-DOS
+ filesystem (typically a floppy disk).  Where reasonable, each program
+ attempts to emulate the MS-DOS equivalent command. However, unnecessary
+ restrictions and oddities of DOS are not emulated. For instance, it is
+ possible to move subdirectories from one subdirectory to another.
+ <P>
+ 
+ Mtools is sufficient to give access to MS-DOS filesystems.  For
+ instance, commands such as <CODE>mdir a:</CODE> work on the <CODE>a:</CODE> floppy
+ without any preliminary mounting or initialization (assuming the default
+ <TT>`/etc/mtools.conf'</TT> works on your machine).  With mtools, one can
+ change floppies too without unmounting and mounting.
+ </P><P>
+ 
+ <BLOCKQUOTE><TABLE BORDER=0 CELLSPACING=0> 
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC3">1. Where to get mtools</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Where to find mtools and early bug fixes</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC4">2. Common features of all mtools commands</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC18">3. How to configure mtools for your environment</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC38">4. Command list</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">The available mtools commands</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC74">5. Architecture specific compilation flags</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC75">6. Porting mtools to architectures which are not supported yet</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Porting mtools to architectures which are not
+                       yet supported</TD></TR>
+ </TABLE>
+ 
+ <br>
+ <TABLE BORDER=0 CELLSPACING=0>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC76">Command Index</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC77">Variable index</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Variable Index</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC78">Concept index</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Concept Index</TD></TR>
+ </TABLE></BLOCKQUOTE>
+ <P>
+ 
+ <!-- End chapter -->
+ <A NAME="SEC2"></A>
+ <H1> Warning, beware of the cookie monster! </H1>
+ <!--docid::SEC2::-->
+ <P>
+ 
+ If you are reading this documentation on the World Wide Web, this
+ section might interest you.  If you are reading it using info, or as a
+ printed document, or on one of our own sites
+ (http://www.tux.org/pub/knaff and http://mtools.linux.lu) you do not need
+ to worry.
+ </P><P>
+ 
+ It has come to my attention that some of the Web sites which display
+ this documentation deal so called "cookies".  These "cookies" are tags
+ sent from the server to the browser, which enable the server to keep
+ track of the sites that the user visits, and thus compromise his
+ privacy.  If you use netscape, you can enable confirmation messages for
+ any cookies sent to your browser by going into
+ Options-&#62;Network_Preferences-&#62;Protocols and checking the box for "Show
+ an Alert before Accepting a cookie". Then, when the alert box pops up,
+ click "Cancel" to refuse the cookie and protect your privacy.
+ </P><P>
+ 
+ <HR SIZE=1>
+ <A NAME="SEC1"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC2"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[ &lt;&lt; ]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[ &gt;&gt; ]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="Location"></A>
+ <HR SIZE="6">
+ <A NAME="SEC2"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC1"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC3"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[ &lt;&lt; ]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[ &gt;&gt; ]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC3"></A>
+ <H1> 1. Where to get mtools </H1>
+ <!--docid::SEC3::-->
+ <P>
+ 
+ Mtools can be found at the following places (and their mirrors):
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>http://mtools.linux.lu/mtools-3.9.11.tar.gz
+ ftp://www.tux.org/pub/knaff/mtools/mtools-3.9.11.tar.gz
+ ftp://ibiblio.unc.edu/pub/Linux/utils/disk-management/mtools-3.9.11.tar.gz
+ </pre></td></tr></table></P><P>
+ 
+ Before reporting a bug, make sure that it has not yet been fixed in the
+ Alpha patches which can be found at:
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>http://mtools.linux.lu/
+ ftp://www.tux.org/pub/knaff/mtools
+ </pre></td></tr></table></P><P>
+ 
+ These patches are named
+ <CODE>mtools-</CODE><VAR>version</VAR><CODE>-</CODE><VAR>ddmm</VAR><CODE>.taz</CODE>, where version
+ stands for the base version, <VAR>dd</VAR> for the day and <VAR>mm</VAR> for the
+ month. Due to a lack of space, I usually leave only the most recent
+ patch.
+ </P><P>
+ 
+ There is an mtools mailing list at mtools @ tux.org .  Please
+ send all bug reports to this list.  You may subscribe to the list by
+ sending a message with 'subscribe mtools @ tux.org' in its
+ body to majordomo @ tux.org . (N.B. Please remove the spaces
+ around the "@" both times. I left them there in order to fool
+ spambots.)  Announcements of new mtools versions will also be sent to
+ the list, in addition to the linux announce newsgroups.  The mailing
+ list is archived at http://www.tux.org/hypermail/mtools/latest
+ </P><P>
+ 
+ <A NAME="Common features"></A>
+ <HR SIZE="6">
+ <A NAME="SEC3"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC2"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC4"></A>
+ <H1> 2. Common features of all mtools commands </H1>
+ <!--docid::SEC4::-->
+ <P>
+ 
+ <BLOCKQUOTE><TABLE BORDER=0 CELLSPACING=0> 
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC5">2.1 Options and filenames</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">What the command line parameters of mtools
+                            mean</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC6">2.2 Drive letters</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Which drives are defined by default</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC7">2.3 Current working directory</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC8">2.4 VFAT-style long file names</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC9">2.5 Name clashes</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Name clash handling, and associated command
+                            line options</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC10">2.6 Case sensitivity of the VFAT filesystem</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Case sensitivity</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC11">2.7 high capacity formats</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">How to fit more data on your floppies</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC16">2.8 Exit codes</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC17">2.9 Bugs</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Happens to everybody</TD></TR>
+ </TABLE></BLOCKQUOTE>
+ <P>
+ 
+ <A NAME="arguments"></A>
+ <HR SIZE="6">
+ <A NAME="SEC4"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC3"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC5"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC3"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC5"></A>
+ <H2> 2.1 Options and filenames </H2>
+ <!--docid::SEC5::-->
+ MS-DOS filenames are composed of a drive letter followed by a colon, a
+ subdirectory, and a filename. Only the filename part is mandatory, the
+ drive letter and the subdirectory are optional. Filenames without a
+ drive letter refer to Unix files. Subdirectory names can use either the
+ '<CODE>/</CODE>' or '<CODE>\</CODE>' separator.  The use of the '<CODE>\</CODE>' separator
+ or wildcards requires the names to be enclosed in quotes to protect them
+ from the shell. However, wildcards in Unix filenames should not be
+ enclosed in quotes, because here we <STRONG>want</STRONG> the shell to expand
+ them.
+ <P>
+ 
+ The regular expression "pattern matching" routines follow the Unix-style
+ rules.  For example, `<CODE>*</CODE>' matches all MS-DOS files in lieu of
+ `<CODE>*.*</CODE>'.  The archive, hidden, read-only and system attribute bits
+ are ignored during pattern matching.
+ </P><P>
+ 
+ All options use the <CODE>-</CODE> (minus) as their first character, not
+ <CODE>/</CODE> as you'd expect in MS-DOS.
+ </P><P>
+ 
+ Most mtools commands allow multiple filename parameters, which
+ doesn't follow MS-DOS conventions, but which is more user-friendly.
+ </P><P>
+ 
+ Most mtools commands allow options that instruct them how to handle file
+ name clashes. See section <A HREF="mtools.html#SEC9">2.5 Name clashes</A>, for more details on these. All
+ commands accept the <CODE>-V</CODE> flags which prints the version, and most
+ accept the <CODE>-v</CODE> flag, which switches on verbose mode. In verbose
+ mode, these commands print out the name of the MS-DOS files upon which
+ they act, unless stated otherwise. See section <A HREF="mtools.html#SEC38">4. Command list</A>, for a description of
+ the options which are specific to each command.
+ </P><P>
+ 
+ <A NAME="drive letters"></A>
+ <HR SIZE="6">
+ <A NAME="SEC5"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC6"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC6"></A>
+ <H2> 2.2 Drive letters </H2>
+ <!--docid::SEC6::-->
+ <P>
+ 
+ The meaning of the drive letters depends on the target architectures.
+ However, on most target architectures, drive A is the first floppy
+ drive, drive B is the second floppy drive (if available), drive J is a
+ Jaz drive (if available), and drive Z is a Zip drive (if available).  On
+ those systems where the device name is derived from the SCSI id, the Jaz
+ drive is assumed to be at Scsi target 4, and the Zip at Scsi target 5
+ (factory default settings).  On Linux, both drives are assumed to be the
+ second drive on the Scsi bus (/dev/sdb). The default settings can be
+ changes using a configuration file (see section <A HREF="mtools.html#SEC18">3. How to configure mtools for your environment</A>).
+ </P><P>
+ 
+ The drive letter : (colon) has a special meaning. It is used to access
+ image files which are directly specified on the command line using the
+ <CODE>-i</CODE> options.
+ </P><P>
+ 
+ Example:
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre> mcopy -i my-image-file.bin ::file1 ::file2 .
+ </pre></td></tr></table></P><P>
+ 
+ This copies <CODE>file1</CODE> and <CODE>file2</CODE> from the image file
+ (<CODE>my-image-file.bin</CODE>) to the <CODE>/tmp</CODE> directory.
+ </P><P>
+ 
+ <A NAME="directory"></A>
+ <HR SIZE="6">
+ <A NAME="SEC6"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC5"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC7"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC7"></A>
+ <H2> 2.3 Current working directory </H2>
+ <!--docid::SEC7::-->
+ <P>
+ 
+ The <CODE>mcd</CODE> command (<A HREF="mtools.html#SEC49">4.6 Mcd</A>) is used to establish the device and
+ the current working directory (relative to the MS-DOS filesystem),
+ otherwise the default is assumed to be <CODE>A:/</CODE>. However, unlike
+ MS-DOS, there is only one working directory for all drives, and not one
+ per drive.
+ </P><P>
+ 
+ <A NAME="long names"></A>
+ <HR SIZE="6">
+ <A NAME="SEC7"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC6"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC8"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC8"></A>
+ <H2> 2.4 VFAT-style long file names </H2>
+ <!--docid::SEC8::-->
+ <P>
+ 
+ This version of mtools supports VFAT style long filenames. If a Unix
+ filename is too long to fit in a short DOS name, it is stored as a
+ VFAT long name, and a companion short name is generated. This short
+ name is what you see when you examine the disk with a pre-7.0 version
+ of DOS.
+  The following table shows some examples of short names:
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>Long name       MS-DOS name     Reason for the change
+ ---------       ----------      ---------------------
+ thisisatest     THISIS~1        filename too long
+ alain.knaff     ALAIN~1.KNA     extension too long
+ prn.txt         PRN~1.TXT       PRN is a device name
+ .abc            ABC~1           null filename
+ hot+cold        HOT_CO~1        illegal character
+ </pre></td></tr></table></P><P>
+ 
+  As you see, the following transformations happen to derive a short
+ name:
+ <UL>
+ <LI>
+ Illegal characters are replaced by underscores. The illegal characters
+ are <CODE>;+=[]',\"*\\&#60;&#62;/?:|</CODE>.
+ <LI>
+ Extra dots, which cannot be interpreted as a main name/extension
+ separator are removed
+ <LI>
+ A <CODE>~</CODE><VAR>n</VAR> number is generated,
+ <LI>
+ The name is shortened so as to fit in the 8+3 limitation
+ </UL>
+ <P>
+ 
+  The initial Unix-style file name (whether long or short) is also called
+ the <EM>primary</EM> name, and the derived short name is also called the
+ <EM>secondary</EM> name.
+ </P><P>
+ 
+  Example:
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre> mcopy /etc/motd a:Reallylongname
+ </pre></td></tr></table> Mtools creates a VFAT entry for Reallylongname, and uses REALLYLO as
+ a short name. Reallylongname is the primary name, and REALLYLO is the
+ secondary name.
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre> mcopy /etc/motd a:motd
+ </pre></td></tr></table> Motd fits into the DOS filename limits. Mtools doesn't need to
+ derivate another name. Motd is the primary name, and there is no
+ secondary name.
+ </P><P>
+ 
+  In a nutshell: The primary name is the long name, if one exists, or
+ the short name if there is no long name.
+ </P><P>
+ 
+  Although VFAT is much more flexible than FAT, there are still names
+ that are not acceptable, even in VFAT. There are still some illegal
+ characters left (<CODE>\"*\\&#60;&#62;/?:|</CODE>), and device names are still
+ reserved.
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>Unix name       Long name       Reason for the change
+ ---------       ----------      ---------------------
+ prn             prn-1           PRN is a device name
+ ab:c            ab_c-1          illegal character
+ </pre></td></tr></table></P><P>
+ 
+  As you see, the following transformations happen if a long name is
+ illegal:
+ <UL>
+ <LI>
+ Illegal characters are replaces by underscores,
+ <LI>
+ A <CODE>-</CODE><VAR>n</VAR> number is generated,
+ </UL>
+ <P>
+ 
+ <A NAME="name clashes"></A>
+ <HR SIZE="6">
+ <A NAME="SEC8"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC7"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC9"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC9"></A>
+ <H2> 2.5 Name clashes </H2>
+ <!--docid::SEC9::-->
+ <P>
+ 
+ When writing a file to disk, its long name or short name may collide
+ with an already existing file or directory. This may happen for all
+ commands which create new directory entries, such as <CODE>mcopy</CODE>,
+ <CODE>mmd</CODE>, <CODE>mren</CODE>, <CODE>mmove</CODE>. When a name clash happens, mtools
+ asks you what it should do. It offers several choices:
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>overwrite</CODE>
+ <DD>Overwrites the existing file. It is not possible to overwrite a
+ directory with a file.
+ <DT><CODE>rename</CODE>
+ <DD>Renames the newly created file. Mtools prompts for the new filename
+ <DT><CODE>autorename</CODE>
+ <DD>Renames the newly created file. Mtools chooses a name by itself, without
+ prompting
+ <DT><CODE>skip</CODE>
+ <DD>Gives up on this file, and moves on to the next (if any)
+ </DL>
+ <P>
+ 
+ To chose one of these actions, type its first letter at the prompt. If
+ you use a lower case letter, the action only applies for this file only,
+ if you use an upper case letter, the action applies to all files, and
+ you won't be prompted again.
+ </P><P>
+ 
+ You may also chose actions (for all files) on the command line, when
+ invoking mtools:
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>-D o</CODE>
+ <DD>Overwrites primary names by default.
+ <DT><CODE>-D O</CODE>
+ <DD>Overwrites secondary names by default.
+ <DT><CODE>-D r</CODE>
+ <DD>Renames primary name by default.
+ <DT><CODE>-D R</CODE>
+ <DD>Renames secondary name by default.
+ <DT><CODE>-D a</CODE>
+ <DD>Autorenames primary name by default.
+ <DT><CODE>-D A</CODE>
+ <DD>Autorenames secondary name by default.
+ <DT><CODE>-D s</CODE>
+ <DD>Skip primary name by default.
+ <DT><CODE>-D S</CODE>
+ <DD>Skip secondary name by default.
+ <DT><CODE>-D m</CODE>
+ <DD>Ask user what to do with primary name.
+ <DT><CODE>-D M</CODE>
+ <DD>Ask user what to do with secondary name.
+ </DL>
+ <P>
+ 
+ Note that for command line switches lower/upper differentiates between
+ primary/secondary name whereas for interactive choices, lower/upper
+ differentiates between just-this-time/always.
+ </P><P>
+ 
+ The primary name is the name as displayed in Windows 95 or Windows NT:
+ i.e. the long name if it exists, and the short name otherwise.  The
+ secondary name is the "hidden" name, i.e. the short name if a long name
+ exists.
+ </P><P>
+ 
+ By default, the user is prompted if the primary name clashes, and the
+ secondary name is autorenamed.
+ </P><P>
+ 
+ If a name clash occurs in a Unix directory, mtools only asks whether
+ to overwrite the file, or to skip it.
+ </P><P>
+ 
+ <A NAME="case sensitivity"></A>
+ <HR SIZE="6">
+ <A NAME="SEC9"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC8"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC10"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC10"></A>
+ <H2> 2.6 Case sensitivity of the VFAT filesystem </H2>
+ <!--docid::SEC10::-->
+ <P>
+ 
+ The VFAT filesystem is able to remember the case of the
+ filenames. However, filenames which differ only in case are not allowed
+ to coexist in the same directory. For example if you store a file called
+ LongFileName on a VFAT filesystem, mdir shows this file as LongFileName,
+ and not as Longfilename. However, if you then try to add LongFilename to
+ the same directory, it is refused, because case is ignored for clash
+ checks.
+ </P><P>
+ 
+ The VFAT filesystem allows to store the case of a filename in the
+ attribute byte, if all letters of the filename are the same case, and if
+ all letters of the extension are the same case too. Mtools uses this
+ information when displaying the files, and also to generate the Unix
+ filename when mcopying to a Unix directory. This may have unexpected
+ results when applied to files written using an pre-7.0 version of DOS:
+ Indeed, the old style filenames map to all upper case. This is different
+ from the behavior of the old version of mtools which used to generate
+ lower case Unix filenames.
+ </P><P>
+ 
+ <A NAME="high capacity formats"></A>
+ <HR SIZE="6">
+ <A NAME="SEC10"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC9"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC11"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC11"></A>
+ <H2> 2.7 high capacity formats </H2>
+ <!--docid::SEC11::-->
+ <P>
+ 
+ Mtools supports a number of formats which allow to store more data on
+ disk as usual. Due to different operating system abilities, these
+ formats are not supported on all OS'es. Mtools recognizes these formats
+ transparently where supported.
+ </P><P>
+ 
+ In order to format these disks, you need to use an operating system
+ specific tool. For Linux, suitable floppy tools can be found in the
+ <CODE>fdutils</CODE> package at the following locations~:
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre><CODE>ftp://www.tux.org/pub/knaff/fdutils/</CODE>.
+ <CODE>ftp://ibiblio.unc.edu/pub/Linux/utils/disk-management/fdutils-*</CODE>
+ </pre></td></tr></table></P><P>
+ 
+ See the manpages included in that package for further detail: Use
+ <CODE>superformat</CODE> to format all formats except XDF, and use
+ <CODE>xdfcopy</CODE> to format XDF.
+ </P><P>
+ 
+ <BLOCKQUOTE><TABLE BORDER=0 CELLSPACING=0> 
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC12">2.7.1 More sectors</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Putting more sectors per track on the disk</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC13">2.7.2 Bigger sectors</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Use bigger sectors to save header space</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC14">2.7.3 2m</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Use a standard first track</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC15">2.7.4 XDF</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">OS/2's eXtended density format</TD></TR>
+ </TABLE></BLOCKQUOTE>
+ <P>
+ 
+ <A NAME="more sectors"></A>
+ <HR SIZE="6">
+ <A NAME="SEC11"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC10"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC12"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC16"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC12"></A>
+ <H3> 2.7.1 More sectors </H3>
+ <!--docid::SEC12::-->
+ <P>
+ 
+ The oldest method of fitting more data on a disk is to use more sectors
+ and more cylinders. Although the standard format uses 80 cylinders and
+ 18 sectors (on a 3 1/2 high density disk), it is possible to use up to
+ 83 cylinders (on most drives) and up to 21 sectors. This method allows
+ to store up to 1743K on a 3 1/2 HD disk. However, 21 sector disks are
+ twice as slow as the standard 18 sector disks because the sectors are
+ packed so close together that we need to interleave them. This problem
+ doesn't exist for 20 sector formats.
+ </P><P>
+ 
+ These formats are supported by numerous DOS shareware utilities such as
+ <CODE>fdformat</CODE> and <CODE>vgacopy</CODE>. In his infinite hybris, Bill Gate$
+ believed that he invented this, and called it <SAMP>`DMF disks'</SAMP>, or
+ <SAMP>`Windows formatted disks'</SAMP>. But in reality, it has already existed
+ years before! Mtools supports these formats on Linux, on SunOs and on
+ the DELL Unix PC.
+ </P><P>
+ 
+ <A NAME="bigger sectors"></A>
+ <HR SIZE="6">
+ <A NAME="SEC12"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC11"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC13"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC10"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC11"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC16"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC13"></A>
+ <H3> 2.7.2 Bigger sectors </H3>
+ <!--docid::SEC13::-->
+ By using bigger sectors it is possible to go beyond the capacity which
+ can be obtained by the standard 512-byte sectors. This is because of the
+ sector header. The sector header has the same size, regardless of how
+ many data bytes are in the sector. Thus, we save some space by using
+ <EM>fewer</EM>, but bigger sectors. For example, 1 sector of 4K only takes
+ up header space once, whereas 8 sectors of 512 bytes have also 8
+ headers, for the same amount of useful data.
+ <P>
+ 
+ This method allows to store up to 1992K on a 3 1/2 HD disk.
+ </P><P>
+ 
+ Mtools supports these formats only on Linux.
+ </P><P>
+ 
+ <A NAME="2m"></A>
+ <HR SIZE="6">
+ <A NAME="SEC13"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC12"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC14"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC10"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC11"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC16"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC14"></A>
+ <H3> 2.7.3 2m </H3>
+ <!--docid::SEC14::-->
+ <P>
+ 
+ The 2m format was originally invented by Ciriaco Garcia de Celis. It
+ also uses bigger sectors than usual in order to fit more data on the
+ disk.  However, it uses the standard format (18 sectors of 512 bytes
+ each) on the first cylinder, in order to make these disks easyer to
+ handle by DOS. Indeed this method allows to have a standard sized
+ bootsector, which contains a description of how the rest of the disk
+ should be read.
+ </P><P>
+ 
+ However, the drawback of this is that the first cylinder can hold less
+ data than the others. Unfortunately, DOS can only handle disks where
+ each track contains the same amount of data. Thus 2m hides the fact that
+ the first track contains less data by using a <EM>shadow
+ FAT</EM>. (Usually, DOS stores the FAT in two identical copies, for
+ additional safety.  XDF stores only one copy, and it tells DOS that it
+ stores two. Thus the same that would be taken up by the second FAT copy
+ is saved.) This also means that your should <STRONG>never use a 2m disk
+ to store anything else than a DOS fs</STRONG>.
+ </P><P>
+ 
+ Mtools supports these format only on Linux.
+ </P><P>
+ 
+ <A NAME="XDF"></A>
+ <HR SIZE="6">
+ <A NAME="SEC14"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC13"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC15"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC10"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC11"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC16"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC15"></A>
+ <H3> 2.7.4 XDF </H3>
+ <!--docid::SEC15::-->
+ <P>
+ 
+ XDF is a high capacity format used by OS/2. It can hold 1840 K per
+ disk. That's lower than the best 2m formats, but its main advantage is
+ that it is fast: 600 milliseconds per track. That's faster than the 21
+ sector format, and almost as fast as the standard 18 sector format. In
+ order to access these disks, make sure mtools has been compiled with XDF
+ support, and set the <CODE>use_xdf</CODE> variable for the drive in the
+ configuration file. See section <A HREF="mtools.html#SEC74">5. Architecture specific compilation flags</A>, and <A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A>,
+ for details on how to do this. Fast XDF access is only available for
+ Linux kernels which are more recent than 1.1.34.
+ </P><P>
+ 
+ Mtools supports this format only on Linux.
+ </P><P>
+ 
+ <STRONG>Caution / Attention distributors</STRONG>: If mtools is compiled on a
+ Linux kernel more recent than 1.3.34, it won't run on an older
+ kernel. However, if it has been compiled on an older kernel, it still
+ runs on a newer kernel, except that XDF access is slower. It is
+ recommended that distribution authors only include mtools binaries
+ compiled on kernels older than 1.3.34 until 2.0 comes out. When 2.0 will
+ be out, mtools binaries compiled on newer kernels may (and should) be
+ distributed. Mtools binaries compiled on kernels older than 1.3.34 won't
+ run on any 2.1 kernel or later.
+ </P><P>
+ 
+ <A NAME="exit codes"></A>
+ <HR SIZE="6">
+ <A NAME="SEC15"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC14"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC16"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC10"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC11"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC16"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC16"></A>
+ <H2> 2.8 Exit codes </H2>
+ <!--docid::SEC16::-->
+ All the Mtools commands return 0 on success, 1 on utter failure, or 2
+ on partial failure.  All the Mtools commands perform a few sanity
+ checks before going ahead, to make sure that the disk is indeed an
+ MS-DOS disk (as opposed to, say an ext2 or minix disk). These checks
+ may reject partially corrupted disks, which might otherwise still be
+ readable. To avoid these checks, set the MTOOLS_SKIP_CHECK
+ environmental variable or the corresponding configuration file variable
+ (see section <A HREF="mtools.html#SEC23">3.4 Global variables</A>)
+ <A NAME="bugs"></A>
+ <HR SIZE="6">
+ <A NAME="SEC16"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC15"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC17"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC11"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC17"></A>
+ <H2> 2.9 Bugs </H2>
+ <!--docid::SEC17::-->
+ An unfortunate side effect of not guessing the proper device (when
+ multiple disk capacities are supported) is an occasional error message
+ from the device driver.  These can be safely ignored.  
+ <P>
+ 
+ The fat checking code chokes on 1.72 Mb disks mformatted with pre-2.0.7
+ mtools. Set the environmental variable MTOOLS_FAT_COMPATIBILITY (or the
+ corresponding configuration file variable, <A HREF="mtools.html#SEC23">3.4 Global variables</A>) to
+ bypass the fat checking.
+ </P><P>
+ 
+ <A NAME="Configuration"></A>
+ </P><P>
+ 
+ <HR SIZE="6">
+ <A NAME="SEC17"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC16"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC18"></A>
+ <H1> 3. How to configure mtools for your environment </H1>
+ <!--docid::SEC18::-->
+ <HR SIZE="6">
+ <A NAME="SEC18"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC17"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC19"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC4"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC19"></A>
+ <H2> 3.1 Description </H2>
+ <!--docid::SEC19::-->
+ <P>
+ 
+  This sections explains the syntax of the configurations files for
+ mtools. The configuration files
+ are called <TT>`/usr/local/etc/mtools.conf'</TT> and <TT>`~/.mtoolsrc'</TT>. If
+ the environmental variable <CODE>MTOOLSRC</CODE> is set, its contents is used
+ as the filename for a third configuration file. These configuration
+ files describe the following items:
+ </P><P>
+ 
+ <UL>
+ <LI>Global configuration flags and variables
+ <LI>Per drive flags and variables
+ <LI>Character translation tables
+ </UL>
+ <P>
+ 
+ <BLOCKQUOTE><TABLE BORDER=0 CELLSPACING=0> 
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC20">3.2 Location of the configuration files</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Where mtools looks for its configuration files</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC21">3.2.1 General configuration file syntax</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">The layout of the configuration files</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC22">3.3 Default values</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Why you don't need a config file in most cases</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC23">3.4 Global variables</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Variables that are independent of the drive</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC24">3.5 Per drive flags and variables</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Variables that are specific to a given drive</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC31">3.8 Character set translation tables</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC36">3.9 Location of configuration files and parsing order</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP"></TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC37">3.10 Backwards compatibility with old configuration file syntax</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Backwards compatibility</TD></TR>
+ </TABLE></BLOCKQUOTE>
+ <P>
+ 
+ <A NAME="config file location"></A>
+ <HR SIZE="6">
+ <A NAME="SEC19"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC20"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[ &lt;&lt; ]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[ &gt;&gt; ]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC20"></A>
+ <H2> 3.2 Location of the configuration files </H2>
+ <!--docid::SEC20::-->
+ <P>
+ 
+ <A NAME="IDX1"></A>
+ <A NAME="IDX2"></A>
+ <A NAME="IDX3"></A>
+ </P><P>
+ 
+ <TT>`/usr/local/etc/mtools.conf'</TT> is the system-wide configuration file,
+ and <TT>`~/.mtoolsrc'</TT> is the user's private configuration file.
+ </P><P>
+ 
+ On some systems, the system-wide configuration file is called
+ <TT>`/etc/default/mtools.conf'</TT> instead.
+ </P><P>
+ 
+ <A NAME="general syntax"></A>
+ <HR SIZE="6">
+ <A NAME="SEC20"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC19"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC21"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC21"></A>
+ <H3> 3.2.1 General configuration file syntax </H3>
+ <!--docid::SEC21::-->
+ <P>
+ 
+ The configuration files is made up of sections. Each section starts
+ with a keyword identifying the section followed by a colon.
+ Then follow variable assignments and flags. Variable assignments take
+ the following form:
+ <TABLE><tr><td>&nbsp;</td><td class=display><pre style="font-family: serif">name=value
+ </pre></td></tr></table>Flags are lone keywords without an equal sign and value following
+ them.  A section either ends at the end of the file or where the next
+ section begins.
+ </P><P>
+ 
+ Lines starting with a hash (<CODE>#</CODE>) are comments. Newline characters
+ are equivalent to whitespace (except where ending a comment). The
+ configuration file is case insensitive, except for item enclosed in
+ quotes (such as filenames).
+ </P><P>
+ 
+ <A NAME="default values"></A>
+ <HR SIZE="6">
+ <A NAME="SEC21"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC20"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC22"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC22"></A>
+ <H2> 3.3 Default values </H2>
+ <!--docid::SEC22::-->
+ For most platforms, mtools contains reasonable compiled-in defaults for
+ physical floppy drives.  Thus, you usually don't need to bother with the
+ configuration file, if all you want to do with mtools is to access your
+ floppy drives. On the other hand, the configuration file is needed if
+ you also want to use mtools to access your hard disk partitions and
+ dosemu image files.
+ <P>
+ 
+ <A NAME="global variables"></A>
+ <HR SIZE="6">
+ <A NAME="SEC22"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC21"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC23"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC23"></A>
+ <H2> 3.4 Global variables </H2>
+ <!--docid::SEC23::-->
+ <P>
+ 
+ Global flags may be set to 1 or to 0.
+ </P><P>
+ 
+ The following global flags are recognized:
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>MTOOLS_SKIP_CHECK</CODE>
+ <DD>If this is set to 1, mtools skips most of its sanity checks. This is
+ needed to read some Atari disks which have been made with the earlier
+ ROMs, and which would not be recognized otherwise.
+ <DT><CODE>MTOOLS_FAT_COMPATIBILITY</CODE>
+ <DD>If this is set to 1, mtools skips the fat size checks. Some disks have
+ a bigger FAT than they really need to. These are rejected if this
+ option is not set.
+ <DT><CODE>MTOOLS_LOWER_CASE</CODE>
+ <DD>If this is set to 1, mtools displays all-upper-case short filenames as
+ lowercase. This has been done to allow a behavior which is consistent
+ with older versions of mtools which didn't know about the case bits.
+ <DT><CODE>MTOOLS_NO_VFAT</CODE>
+ <DD>If this is set to 1, mtools won't generate VFAT entries for filenames
+ which are mixed-case, but otherwise legal dos filenames.  This is useful
+ when working with DOS versions which can't grok VFAT longnames, such as
+ FreeDos.
+ <DT><CODE>MTOOLS_DOTTED_DIR</CODE>
+ <DD>In a wide directory, prints the short name with a dot instead of spaces
+ separating the basename and the extension.
+ <DT><CODE>MTOOLS_NAME_NUMERIC_TAIL</CODE>
+ <DD>If this is set to one (default), generate numeric tails for all long
+ names (~1).  If set to zero, only generate numeric tails if otherwise a
+ clash would have happened.
+ <DT><CODE>MTOOLS_TWENTY_FOUR_HOUR_CLOCK</CODE>
+ <DD>If 1, uses the European notation for times (twenty four hour clock),
+ else uses the UK/US notation (am/pm)
+ </DL>
+ <P>
+ 
+ Example:
+ Inserting the following line into your configuration file instructs
+ mtools to skip the sanity checks:
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>  MTOOLS_SKIP_CHECK=1
+ </pre></td></tr></table></P><P>
+ 
+ Global variables may also be set via the environment:
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>  export MTOOLS_SKIP_CHECK=1
+ </pre></td></tr></table></P><P>
+ 
+ Global string variables may be set to any value:
+ <DL COMPACT>
+ <DT><CODE>MTOOLS_DATE_STRING</CODE>
+ <DD>The format used for printing dates of files.  By default, is dd-mm-yyyy.
+ </DL>
+ <P>
+ 
+ <A NAME="per drive variables"></A>
+ <HR SIZE="6">
+ <A NAME="SEC23"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC22"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC24"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC24"></A>
+ <H2> 3.5 Per drive flags and variables </H2>
+ <!--docid::SEC24::-->
+ <P>
+ 
+ <BLOCKQUOTE><TABLE BORDER=0 CELLSPACING=0> 
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC25">3.5.1 General information</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">What a drive description looks like</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC26">3.5.2 Disk Geometry Configuration</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Describes the physical characteristics of
+                           the media</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC27">3.5.3 Open Flags</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Flags passed to the open system call when the
+                           device is opened</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Variables which don't fit in either category</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Switch variables, which can be enabled or disabled</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC30">3.7.1 Supplying multiple descriptions for a drive</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">How to supply several descriptions for a
+                           drive, to be tried one after the other.</TD></TR>
+ </TABLE></BLOCKQUOTE>
+ <P>
+ 
+ <A NAME="general information"></A>
+ <HR SIZE="6">
+ <A NAME="SEC24"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC23"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC25"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC31"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC25"></A>
+ <H3> 3.5.1 General information </H3>
+ <!--docid::SEC25::-->
+ <P>
+ 
+ Per drive flags and values may be described in a drive section. A
+ drive section starts with
+ <CODE>drive</CODE> "<VAR>driveletter</VAR>" :
+ </P><P>
+ 
+ Then follow variable-value pairs and flags.
+ </P><P>
+ 
+ This is a sample drive description:
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>  drive a:
+     file="/dev/fd0" use_xdf=1
+ </pre></td></tr></table></P><P>
+ 
+ <A NAME="geometry description"></A>
+ <HR SIZE="6">
+ <A NAME="SEC25"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC24"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC26"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC23"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC24"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC31"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC26"></A>
+ <H3> 3.5.2 Disk Geometry Configuration </H3>
+ <!--docid::SEC26::-->
+ <P>
+ 
+ Geometry information describes the physical characteristics about the
+ disk. Its has three purposes:
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT>formatting
+ <DD>The geometry information is written into the boot sector of the newly
+ made disk. However, you may also describe the geometry information on
+ the command line. See section <A HREF="mtools.html#SEC57">4.13 Mformat</A>, for details.
+ <DT>filtering
+ <DD>On some Unices there are device nodes which only support one physical
+ geometry. For instance, you might need a different node to access a disk
+ as high density or as low density. The geometry is compared to the
+ actual geometry stored on the boot sector to make sure that this device
+ node is able to correctly read the disk. If the geometry doesn't match,
+ this drive entry fails, and the next drive entry bearing the same drive
+ letter is tried. See section <A HREF="mtools.html#SEC30">3.7.1 Supplying multiple descriptions for a drive</A>, for more details on
+ supplying several descriptions for one drive letter.
+ <P>
+ 
+ If no geometry information is supplied in the configuration file, all
+ disks are accepted. On Linux (and on Sparc) there exist device nodes
+ with configurable geometry (<TT>`/dev/fd0'</TT>, <TT>`/dev/fd1'</TT> etc),
+ and thus filtering is not needed (and ignored) for disk drives.  (Mtools
+ still does do filtering on plain files (disk images) in Linux: this is
+ mainly intended for test purposes, as I don't have access to a Unix
+ which would actually need filtering).
+ </P><P>
+ 
+ If you do not need filtering, but want still a default geometry for
+ mformatting, you may switch off filtering using the <CODE>mformat_only</CODE>
+ flag.
+ </P><P>
+ 
+ If you want filtering, you should supply the <CODE>filter</CODE> flag.  If you 
+ supply a geometry, you must supply one of both flags.
+ </P><P>
+ 
+ <DT>initial geometry
+ <DD>On devices that support it (usually floppy devices), the geometry
+ information is also used to set the initial geometry. This initial
+ geometry is applied while reading the boot sector, which contains the
+ real geometry.  If no geometry information is supplied in the
+ configuration file, or if the <CODE>mformat_only</CODE> flag is supplied, no
+ initial configuration is done.
+ <P>
+ 
+ On Linux, initial geometry is not really needed, as the configurable
+ devices are able to auto-detect the disk type accurately enough (for
+ most common formats) to read the boot sector.
+ </DL>
+ <P>
+ 
+ Wrong geometry information may lead to very bizarre errors. That's why I
+ strongly recommend that you add the <CODE>mformat_only</CODE> flag to your
+ drive description, unless you really need filtering or initial geometry.
+ </P><P>
+ 
+ The following geometry related variables are available:
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>cylinders</CODE>
+ <DD><DT><CODE>tracks</CODE>
+ <DD><A NAME="IDX4"></A>
+ <A NAME="IDX5"></A>
+ The number of cylinders. (<CODE>cylinders</CODE> is the preferred form,
+ <CODE>tracks</CODE> is considered obsolete)
+ <DT><CODE>heads</CODE>
+ <DD><A NAME="IDX6"></A>
+ The number of heads (sides).
+ <DT><CODE>sectors</CODE>
+ <DD><A NAME="IDX7"></A>
+ The number of sectors per track.
+ </DL>
+ <P>
+ 
+ Example: the following drive section describes a 1.44M drive:
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>  drive a:
+       file="/dev/fd0H1440"
+       fat_bits=12
+       cylinders=80 heads=2 sectors=18
+       mformat_only
+ </pre></td></tr></table></P><P>
+ 
+ The following shorthand geometry descriptions are available:
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>1.44m</CODE>
+ <DD>high density 3 1/2 disk. Equivalent to:
+ <CODE>fat_bits=12 cylinders=80 heads=2 sectors=18</CODE>
+ <DT><CODE>1.2m</CODE>
+ <DD>high density 5 1/4 disk. Equivalent to:
+ <CODE>fat_bits=12 cylinders=80 heads=2 sectors=15</CODE>
+ <DT><CODE>720k</CODE>
+ <DD>double density 3 1/2 disk. Equivalent to:
+ <CODE>fat_bits=12 cylinders=80 heads=2 sectors=9</CODE>
+ <DT><CODE>360k</CODE>
+ <DD>double density 5 1/4 disk. Equivalent to:
+ <CODE>fat_bits=12 cylinders=40 heads=2 sectors=9</CODE>
+ </DL>
+ <P>
+ 
+ The shorthand format descriptions may be amended. For example,
+ <CODE>360k sectors=8</CODE>
+ describes a 320k disk and is equivalent to:
+ <CODE>fat_bits=12 cylinders=40 heads=2 sectors=8</CODE>
+ </P><P>
+ 
+ <A NAME="open flags"></A>
+ <HR SIZE="6">
+ <A NAME="SEC26"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC25"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC27"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC23"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC24"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC31"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC27"></A>
+ <H3> 3.5.3 Open Flags </H3>
+ <!--docid::SEC27::-->
+ <P>
+ 
+ Moreover, the following flags are available:
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>sync</CODE>
+ <DD>All i/o operations are done synchronously
+ <DT><CODE>nodelay</CODE>
+ <DD>The device or file is opened with the O_NDELAY flag. This is needed on
+ some non-Linux architectures.
+ <DT><CODE>exclusive</CODE>
+ <DD>The device or file is opened with the O_EXCL flag. On Linux, this
+ ensures exclusive access to the floppy drive. On most other
+ architectures, and for plain files it has no effect at all.
+ </DL>
+ <P>
+ 
+ <A NAME="misc variables"></A>
+ <HR SIZE="6">
+ <A NAME="SEC27"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC26"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC28"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC23"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC24"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC31"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC28"></A>
+ <H2> 3.6 General Purpose Drive Variables </H2>
+ <!--docid::SEC28::-->
+ <P>
+ 
+ The following general purpose drive variables are available.  Depending
+ to their type, these variables can be set to a string (file, precmd) or
+ an integer (all others)
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>file</CODE>
+ <DD><A NAME="IDX8"></A>
+ <A NAME="IDX9"></A>
+ <A NAME="IDX10"></A>
+ <A NAME="IDX11"></A>
+ The name of the file or device holding the disk image. This is
+ mandatory. The file name should be enclosed in quotes.
+ <P>
+ 
+ <DT><CODE>partition</CODE>
+ <DD><A NAME="IDX12"></A>
+ <A NAME="IDX13"></A>
+ <A NAME="IDX14"></A>
+ <A NAME="IDX15"></A>
+ <A NAME="IDX16"></A>
+ <A NAME="IDX17"></A>
+ <A NAME="IDX18"></A>
+ <A NAME="IDX19"></A>
+ <A NAME="IDX20"></A>
+ Tells mtools to treat the drive as a partitioned device, and to use the
+ given partition. Only primary partitions are accessible using this
+ method, and they are numbered from 1 to 4. For logical partitions, use
+ the more general <CODE>offset</CODE> variable. The <CODE>partition</CODE> variable
+ is intended for removable media such as Syquests, ZIP drives, and
+ magneto-optical disks. Although traditional DOS sees Syquests and
+ magneto-optical disks as <SAMP>`giant floppy disks'</SAMP> which are
+ unpartitioned, OS/2 and Windows NT treat them like hard disks,
+ i.e. partioned devices. The <CODE>partition</CODE> flag is also useful DOSEMU
+ hdimages. It is not recommended for hard disks for which direct access
+ to partitions is available through mounting.
+ <P>
+ 
+ <DT><CODE>offset</CODE>
+ <DD><A NAME="IDX21"></A>
+ <A NAME="IDX22"></A>
+ Describes where in the file the MS-DOS filesystem starts. This is useful
+ for logical partitions in DOSEMU hdimages, and for ATARI ram disks. By
+ default, this is zero, meaning that the filesystem starts right at the
+ beginning of the device or file.
+ <DT><CODE>fat_bits</CODE>
+ <DD><A NAME="IDX23"></A>
+ The number of FAT bits. This may be 12 or 16. This is very rarely
+ needed, as it can almost always be deduced from information in the
+ boot sector. On the contrary, describing the number of fat bits may
+ actually be harmful if you get it wrong. You should only use it if
+ mtools gets the autodetected number of fat bits wrong, or if you want
+ to mformat a disk with a weird number of fat bits.
+ <DT><CODE>precmd</CODE>
+ <DD><A NAME="IDX24"></A>
+ <A NAME="IDX25"></A>
+ <P>
+ 
+ On some variants of Solaris, it is necessary to call 'volcheck -v'
+ before opening a floppy device, in order for the system to notice that
+ there is indeed a disk in the drive. <CODE>precmd="volcheck -v"</CODE> in the
+ drive clause establishes the desired behavior.
+ </P><P>
+ 
+ <DT><CODE>blocksize</CODE>
+ <DD><A NAME="IDX26"></A>
+ <A NAME="IDX27"></A>
+ <A NAME="IDX28"></A>
+ <P>
+ 
+ This parameter represents a default block size to be always used on this
+ device.  All I/O is done with multiples of this block size,
+ independantly of the sector size registered in the filesystem's boot
+ sector.  This is useful for character devices whose sector size is not
+ 512, such as for example CD Rom drives on Solaris.
+ </P><P>
+ 
+ </DL>
+ <P>
+ 
+ Only the <CODE>file</CODE> variable is mandatory. The other parameters may
+ be left out. In that case a default value or an autodetected value is
+ used.
+ </P><P>
+ 
+ <A NAME="misc flags"></A>
+ <HR SIZE="6">
+ <A NAME="SEC28"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC27"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC29"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC23"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC24"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC31"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC29"></A>
+ <H2> 3.7 General Purpose Drive Flags </H2>
+ <!--docid::SEC29::-->
+ <P>
+ 
+ A flag can either be set to 1 (enabled) or 0 (disabled). If the value is
+ ommitted, it is enabled.  For example, <CODE>scsi</CODE> is equivalent to
+ <CODE>scsi=1</CODE>
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>nolock</CODE>
+ <DD><A NAME="IDX29"></A>
+ <A NAME="IDX30"></A>
+ <A NAME="IDX31"></A>
+ Instruct mtools to not use locking on this drive.  This is needed on
+ systems with buggy locking semantics.  However, enabling this makes
+ operation less safe in cases where several users may access the same
+ drive at the same time.
+ <P>
+ 
+ <DT><CODE>scsi</CODE>
+ <DD><A NAME="IDX32"></A>
+ <A NAME="IDX33"></A>
+ <A NAME="IDX34"></A>
+ <A NAME="IDX35"></A>
+ <A NAME="IDX36"></A>
+ <A NAME="IDX37"></A>
+ <A NAME="IDX38"></A>
+ When set to 1, this option tells mtools to use raw SCSI I/O instead of
+ the standard read/write calls to access the device. Currently, this is
+ supported on HP/UX, Solaris and SunOs.  This is needed because on some
+ architectures, such as SunOs or Solaris, PC media can't be accessed
+ using the <CODE>read</CODE> and <CODE>write</CODE> syscalls, because the OS expects
+ them to contain a Sun specific "disk label".
+ <P>
+ 
+ As raw Scsi access always uses the whole device, you need to specify the
+ "partition" flag in addition
+ </P><P>
+ 
+ On some architectures, such as Solaris, mtools needs root privileges to
+ be able to use the <CODE>scsi</CODE> option.  Thus mtools should be installed
+ set uid root on Solaris if you want to access Zip/Jaz drives.  Thus, if
+ the <CODE>scsi</CODE> flag is given, <CODE>privileged</CODE> is automatically
+ implied, unless explicitly disabled by <CODE>privileged=0</CODE>
+ </P><P>
+ 
+ Mtools uses its root privileges to open the device, and to issue the
+ actual SCSI I/O calls.  Moreover, root privileges are only used for
+ drives described in a system-wide configuration file such as
+ <TT>`/usr/local/etc/mtools.conf'</TT>, and not for those described in
+ <TT>`~/.mtoolsrc'</TT> or <TT>`$MTOOLSRC'</TT>.  
+ </P><P>
+ 
+ <DT><CODE>privileged</CODE>
+ <DD><A NAME="IDX39"></A>
+ <A NAME="IDX40"></A>
+ When set to 1, this instructs mtools to use its set-uid and set-gid
+ privileges for opening the given drive.  This option is only valid for
+ drives described in the system-wide configuration files (such as
+ <TT>`/usr/local/etc/mtools.conf'</TT>, not <TT>`~/.mtoolsrc'</TT> or
+ <TT>`$MTOOLSRC'</TT>).  Obviously, this option is also a no op if mtools is
+ not installed setuid or setgid.  This option is implied by 'scsi=1', but
+ again only for drives defined in system-wide configuration files.
+ Privileged may also be set explicitely to 0, in order to tell mtools not
+ to use its privileges for a given drive even if <CODE>scsi=1</CODE> is set.
+ <P>
+ 
+ Mtools only needs to be installed setuid if you use the
+ <CODE>privileged</CODE> or <CODE>scsi</CODE> drive variables.  If you do not use
+ these options, mtools works perfectly well even when not installed
+ setuid root.
+ </P><P>
+ 
+ <DT><CODE>vold</CODE>
+ <DD><A NAME="IDX41"></A>
+ <A NAME="IDX42"></A>
+ <P>
+ 
+ Instructs mtools to interpret the device name as a vold identifier
+ rather than as a filename.  The vold identifier is translated into a
+ real filename using the <CODE>media_findname()</CODE> and
+ <CODE>media_oldaliases()</CODE> functions of the <CODE>volmgt</CODE> library.  This
+ flag is only available if you configured mtools with the
+ <CODE>--enable-new-vold</CODE> option before compilation.
+ </P><P>
+ 
+ <DT><CODE>swap</CODE>
+ <DD><A NAME="IDX43"></A>
+ <A NAME="IDX44"></A>
+ <P>
+ 
+ Consider the media as a word-swapped Atari disk.
+ </P><P>
+ 
+ <DT><CODE>use_xdf</CODE>
+ <DD><A NAME="IDX45"></A>
+ <A NAME="IDX46"></A>
+ If this is set to a non-zero value, mtools also tries to access this
+ disk as an XDF disk. XDF is a high capacity format used by OS/2. This
+ is off by default. See section <A HREF="mtools.html#SEC15">2.7.4 XDF</A>, for more details.
+ <DT><CODE>mformat_only</CODE>
+ <DD><A NAME="IDX47"></A>
+ Tells mtools to use the geometry for this drive only for mformatting and 
+ not for filtering.
+ <P>
+ 
+ <DT><CODE>filter</CODE>
+ <DD><A NAME="IDX48"></A>
+ Tells mtools to use the geometry for this drive both for mformatting and 
+ filtering.
+ <P>
+ 
+ <DT><CODE>remote</CODE>
+ <DD>Tells mtools to connect to floppyd (see section <A HREF="mtools.html#SEC39">4.1 Floppyd</A>).
+ </DL>
+ <P>
+ 
+ <A NAME="multiple descriptions"></A>
+ <HR SIZE="6">
+ <A NAME="SEC29"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC28"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC30"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC23"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC24"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC31"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC30"></A>
+ <H3> 3.7.1 Supplying multiple descriptions for a drive </H3>
+ <!--docid::SEC30::-->
+ <P>
+ 
+ It is possible to supply multiple descriptions for a drive. In that
+ case, the descriptions are tried in order until one is found that
+ fits. Descriptions may fail for several reasons:
+ </P><P>
+ 
+ <OL>
+ <LI>
+ because the geometry is not appropriate,
+ <LI>
+ because there is no disk in the drive,
+ <LI>
+ or because of other problems.
+ </OL>
+ <P>
+ 
+ Multiple definitions are useful when using physical devices which are
+ only able to support one single disk geometry.
+ Example:
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>  drive a: file="/dev/fd0H1440" 1.44m
+   drive a: file="/dev/fd0H720" 720k
+ </pre></td></tr></table></P><P>
+ 
+ This instructs mtools to use /dev/fd0H1440 for 1.44m (high density)
+ disks and /dev/fd0H720 for 720k (double density) disks. On Linux, this
+ feature is not really needed, as the /dev/fd0 device is able to handle
+ any geometry.
+ </P><P>
+ 
+ You may also use multiple drive descriptions to access both of your
+ physical drives through one drive letter:
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>  drive z: file="/dev/fd0"
+   drive z: file="/dev/fd1"
+ </pre></td></tr></table></P><P>
+ 
+ With this description, <CODE>mdir z:</CODE> accesses your first physical
+ drive if it contains a disk. If the first drive doesn't contain a disk,
+ mtools checks the second drive.
+ </P><P>
+ 
+ When using multiple configuration files, drive descriptions in the files
+ parsed last override descriptions for the same drive in earlier
+ files. In order to avoid this, use the <CODE>drive+</CODE> or <CODE>+drive</CODE>
+ keywords instead of <CODE>drive</CODE>. The first adds a description to the
+ end of the list (i.e. it will be tried last), and the first adds it to
+ the start of the list.
+ </P><P>
+ 
+ <A NAME="character sets"></A>
+ <HR SIZE="6">
+ <A NAME="SEC30"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC29"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC31"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC23"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC24"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC31"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC31"></A>
+ <H2> 3.8 Character set translation tables </H2>
+ <!--docid::SEC31::-->
+ <P>
+ 
+ If you live in the USA, in Western Europe or in Australia, you may
+ skip this section.
+ </P><P>
+ 
+ <BLOCKQUOTE><TABLE BORDER=0 CELLSPACING=0> 
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC32">3.8.1 Why character set translation tables are needed</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Why character set tables are needed</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC33">3.8.2 Configuration using Country</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Using the COUNTRY variable to select tables</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC34">3.8.3 Configuration using explicit translation tables</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">Supplying a new table for an unknown country</TD></TR>
+ </TABLE></BLOCKQUOTE>
+ <P>
+ 
+ <A NAME="why"></A>
+ <HR SIZE="6">
+ <A NAME="SEC31"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC30"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC32"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC24"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC36"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC32"></A>
+ <H3> 3.8.1 Why character set translation tables are needed </H3>
+ <!--docid::SEC32::-->
+ <P>
+ 
+ DOS uses a different character code mapping than Unix. 7-bit
+ characters still have the same meaning, only characters with the eight
+ bit set are affected. To make matters worse, there are several
+ translation tables available depending on the country where you
+ are. The appearance of the characters is defined using
+ code pages. These code pages aren't the same for all countries. For
+ instance, some code pages don't contain upper case accented
+ characters. On the other hand, some code pages contain characters which
+ don't exist in Unix, such as certain line-drawing characters or
+ accented consonants used by some Eastern European countries. This
+ affects two things, relating to filenames:
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT>upper case characters
+ <DD>In short names, only upper case characters are allowed. This also
+ holds for accented characters. For instance, in a code page which
+ doesn't contain accented uppercase characters, the accented lowercase
+ characters get transformed into their unaccented counterparts.
+ <DT>long file names
+ <DD>Micro$oft has finally come to their senses and uses a more standard
+ mapping for the long file names. They use Unicode, which is basically
+ a 32 bit version of ASCII. Its first 256 characters are identical to
+ Unix ASCII. Thus, the code page also affects the correspondence
+ between the codes used in long names and those used in short names
+ </DL>
+ <P>
+ 
+ Mtools considers the filenames entered on the command line as having the
+ Unix mapping, and translates the characters to get short names.  By
+ default, code page 850 is used with the Swiss uppercase/lowercase
+ mapping. I chose this code page, because its set of existing characters
+ most closely matches Unix's. Moreover, this code page covers most
+ characters in use in the USA, Australia and Western Europe. However, it
+ is still possible to chose a different mapping. There are two methods:
+ the <CODE>country</CODE> variable and explicit tables.
+ </P><P>
+ 
+ <A NAME="country"></A>
+ <HR SIZE="6">
+ <A NAME="SEC32"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC31"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC33"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC24"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC31"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC36"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC33"></A>
+ <H3> 3.8.2 Configuration using Country </H3>
+ <!--docid::SEC33::-->
+ <P>
+ 
+ The <CODE>COUNTRY</CODE> variable is recommended for people which also have
+ access to MS-DOS system files and documentation. If you don't have access
+ to these, I'd suggest you'd rather use explicit tables instead.
+ </P><P>
+ 
+ Syntax:
+ </P><P>
+ 
+ <CODE>COUNTRY="</CODE><VAR>country</VAR><CODE>[,[</CODE><VAR>codepage</VAR><CODE>],</CODE>
+ <VAR>country-file</VAR><CODE>]"</CODE>
+ </P><P>
+ 
+ This tells mtools to use a Unix-to-DOS translation table which matches
+ <VAR>codepage</VAR> and an lowercase-to-uppercase table for <VAR>country</VAR> and
+ to use the <VAR>country-file</VAR> file to get the lowercase-to-uppercase
+ table. The country code is most often the telephone prefix of the
+ country. Refer to the DOS help page on "country" for more details. The
+ <VAR>codepage</VAR> and the <VAR>country-file</VAR> parameters are
+ optional. Please don't type in the square brackets, they are only there
+ to say which parameters are optional. The <VAR>country-file</VAR> file is
+ supplied with MS-DOS, and is usually called <TT>`COUNTRY.SYS'</TT>, and
+ stored in the <TT>`C:\DOS'</TT> directory. In most cases you don't need it,
+ as the most common translation tables are compiled into mtools. So,
+ don't worry if you run a Unix-only box which lacks this file.
+ </P><P>
+ 
+ If <VAR>codepage</VAR> is not given, a per country default code page is
+ used. If the <VAR>country-file</VAR> parameter isn't given, compiled-in
+ defaults are used for the lowercase-to-uppercase table. This is useful
+ for other Unices than Linux, which may have no <TT>`COUNTRY.SYS'</TT> file
+ available online.
+ </P><P>
+ 
+ The Unix-to-DOS are not contained in the <TT>`COUNTRY.SYS'</TT> file, and
+ thus mtools always uses compiled-in defaults for those. Thus, only a
+ limited amount of code pages are supported. If your preferred code page
+ is missing, or if you know the name of the Windows 95 file which
+ contains this mapping, could you please drop me a line at
+ <CODE>alain@linux.lu</CODE>.
+ </P><P>
+ 
+ The <CODE>COUNTRY</CODE> variable can also be set using the environment.
+ </P><P>
+ 
+ <A NAME="explicit tables"></A>
+ <HR SIZE="6">
+ <A NAME="SEC33"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC32"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC34"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC24"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC31"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC36"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC34"></A>
+ <H3> 3.8.3 Configuration using explicit translation tables </H3>
+ <!--docid::SEC34::-->
+ <P>
+ 
+ Translation tables may be described in line in the configuration
+ file. Two tables are needed: first the DOS-to-Unix table, and then the
+ Lowercase-to-Uppercase table. A DOS-to-Unix table starts with the
+ <CODE>tounix</CODE>
+ keyword, followed by a colon, and 128 hexadecimal numbers.
+ A lower-to-upper table starts with the
+ <CODE>fucase</CODE>
+ keyword, followed by a colon, and 128 hexadecimal numbers.
+ </P><P>
+ 
+ The tables only show the translations for characters whose codes is
+ greater than 128, because translation for lower codes is trivial.
+ </P><P>
+ 
+ Example:
+ <A NAME="IDX49"></A>
+ <A NAME="IDX50"></A>
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre> tounix:
+    0xc7 0xfc 0xe9 0xe2 0xe4 0xe0 0xe5 0xe7 
+    0xea 0xeb 0xe8 0xef 0xee 0xec 0xc4 0xc5 
+    0xc9 0xe6 0xc6 0xf4 0xf6 0xf2 0xfb 0xf9 
+    0xff 0xd6 0xdc 0xf8 0xa3 0xd8 0xd7 0x5f 
+    0xe1 0xed 0xf3 0xfa 0xf1 0xd1 0xaa 0xba 
+    0xbf 0xae 0xac 0xbd 0xbc 0xa1 0xab 0xbb 
+    0x5f 0x5f 0x5f 0x5f 0x5f 0xc1 0xc2 0xc0 
+    0xa9 0x5f 0x5f 0x5f 0x5f 0xa2 0xa5 0xac 
+    0x5f 0x5f 0x5f 0x5f 0x5f 0x5f 0xe3 0xc3 
+    0x5f 0x5f 0x5f 0x5f 0x5f 0x5f 0x5f 0xa4 
+    0xf0 0xd0 0xc9 0xcb 0xc8 0x69 0xcd 0xce 
+    0xcf 0x5f 0x5f 0x5f 0x5f 0x7c 0x49 0x5f 
+    0xd3 0xdf 0xd4 0xd2 0xf5 0xd5 0xb5 0xfe 
+    0xde 0xda 0xd9 0xfd 0xdd 0xde 0xaf 0xb4 
+    0xad 0xb1 0x5f 0xbe 0xb6 0xa7 0xf7 0xb8 
+    0xb0 0xa8 0xb7 0xb9 0xb3 0xb2 0x5f 0x5f 
+ 
+  fucase:
+    0x80 0x9a 0x90 0xb6 0x8e 0xb7 0x8f 0x80 
+    0xd2 0xd3 0xd4 0xd8 0xd7 0xde 0x8e 0x8f 
+    0x90 0x92 0x92 0xe2 0x99 0xe3 0xea 0xeb 
+    0x59 0x99 0x9a 0x9d 0x9c 0x9d 0x9e 0x9f 
+    0xb5 0xd6 0xe0 0xe9 0xa5 0xa5 0xa6 0xa7 
+    0xa8 0xa9 0xaa 0xab 0xac 0xad 0xae 0xaf 
+    0xb0 0xb1 0xb2 0xb3 0xb4 0xb5 0xb6 0xb7 
+    0xb8 0xb9 0xba 0xbb 0xbc 0xbd 0xbe 0xbf 
+    0xc0 0xc1 0xc2 0xc3 0xc4 0xc5 0xc7 0xc7 
+    0xc8 0xc9 0xca 0xcb 0xcc 0xcd 0xce 0xcf 
+    0xd1 0xd1 0xd2 0xd3 0xd4 0x49 0xd6 0xd7 
+    0xd8 0xd9 0xda 0xdb 0xdc 0xdd 0xde 0xdf 
+    0xe0 0xe1 0xe2 0xe3 0xe5 0xe5 0xe6 0xe8 
+    0xe8 0xe9 0xea 0xeb 0xed 0xed 0xee 0xef 
+    0xf0 0xf1 0xf2 0xf3 0xf4 0xf5 0xf6 0xf7 
+    0xf8 0xf9 0xfa 0xfb 0xfc 0xfd 0xfe 0xff 
+ </pre></td></tr></table></P><P>
+ 
+ The first table maps DOS character codes to Unix character codes. For
+ example, the DOS character number 129. This is a u with to dots on top
+ of it. To translate it into Unix, we look at the character number 1 in
+ the first table (1 = 129 - 128). This is 0xfc. (Beware, numbering
+ starts at 0).
+ The second table maps lower case DOS characters to upper case DOS
+ characters. The same lower case u with dots maps to character 0x9a,
+ which is an uppercase U with dots in DOS.
+ </P><P>
+ 
+ <HR SIZE="6">
+ <A NAME="SEC34"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC33"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC35"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC24"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC31"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC36"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC35"></A>
+ <H3> 3.8.4 Unicode characters greater than 256 </H3>
+ <!--docid::SEC35::-->
+ If an existing MS-DOS name contains Unicode character greater than 256,
+ these are translated to underscores or to characters which are close
+ in visual appearance. For example, accented consonants are translated
+ into their unaccented counterparts. This translation is used for mdir
+ and for the Unix filenames generated by mcopy. Linux does support
+ Unicode too, but unfortunately too few applications support it yet to bother
+ with it in mtools. Most importantly, xterm can't display Unicode
+ yet. If there is sufficient demand, I might include support for
+ Unicode in the Unix filenames as well.
+ <P>
+ 
+ <STRONG>Caution:</STRONG>
+ When deleting files with mtools, the underscore matches all characters
+ which can't be represented in Unix. Be careful with mdel!
+ </P><P>
+ 
+ <A NAME="parsing order"></A>
+ <HR SIZE="6">
+ <A NAME="SEC35"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC34"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC36"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC24"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC31"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC36"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC36"></A>
+ <H2> 3.9 Location of configuration files and parsing order </H2>
+ <!--docid::SEC36::-->
+ <P>
+ 
+ The configuration files are parsed in the following order:
+ <OL>
+ <LI>
+ compiled-in defaults
+ <LI>
+ <TT>`/usr/local/etc/mtools.conf'</TT>
+ <LI>
+ <TT>`/etc/mtools'</TT>
+ This is for backwards compatibility only, and is only parsed if
+ <TT>`mtools.conf'</TT>
+ doesn't exist.
+ <LI>
+ <TT>`~/.mtoolsrc'</TT>.
+ <LI>
+ <TT>`$MTOOLSRC'</TT> (file pointed by the <CODE>MTOOLSRC</CODE> environmental
+ variable)
+ </OL>
+ <P>
+ 
+ Options described in the later files override those described in the
+ earlier files. Drives defined in earlier files persist if they are not
+ overridden in the later files. For instance, drives A and B may be
+ defined in <TT>`/usr/local/etc/mtools.conf'</TT> and drives C and D may be
+ defined in <TT>`~/.mtoolsrc'</TT> However, if <TT>`~/.mtoolsrc'</TT> also
+ defines drive A, this new description would override the description of
+ drive A in <TT>`/usr/local/etc/mtools.conf'</TT> instead of adding to it. If
+ you want to add a new description to a drive already described in an
+ earlier file, you need to use either the <CODE>+drive</CODE> or <CODE>drive+</CODE>
+ keyword.
+ </P><P>
+ 
+ <A NAME="old style config"></A>
+ <HR SIZE="6">
+ <A NAME="SEC36"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC35"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC37"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC31"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC37"></A>
+ <H2> 3.10 Backwards compatibility with old configuration file syntax </H2>
+ <!--docid::SEC37::-->
+ <P>
+ 
+ The syntax described herein is new for version <CODE>mtools-3.0</CODE>. The
+ old line-oriented syntax is still supported. Each line beginning with a
+ single letter is considered to be a drive description using the old
+ syntax. Old style and new style drive sections may be mixed within the
+ same configuration file, in order to make upgrading easier. Support for
+ the old syntax will be phased out eventually, and in order to discourage
+ its use, I purposefully omit its description here.
+ </P><P>
+ 
+ <A NAME="Commands"></A>
+ <HR SIZE="6">
+ <A NAME="SEC37"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC36"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC38"></A>
+ <H1> 4. Command list </H1>
+ <!--docid::SEC38::-->
+ <P>
+ 
+  This section describes the available mtools commands, and the command
+ line parameters that each of them accepts. Options which are common to
+ all mtools commands are not described here, <A HREF="mtools.html#SEC5">2.1 Options and filenames</A> for a
+ description of those.
+ </P><P>
+ 
+ <BLOCKQUOTE><TABLE BORDER=0 CELLSPACING=0> 
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC39">4.1 Floppyd</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">floppy daemon to run on your X server box</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC44">4.2 Floppyd_installtest</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">small utility to check for the presence of floppyd</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC45">4.3 Mattrib</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">change MS-DOS file attribute flags</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC46">4.4 Mbadblocks</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">tests a floppy disk, and marks the bad blocks in the FAT</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC48">4.5 Mcat</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">same as cat. Only usefull with floppyd.</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC49">4.6 Mcd</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">change MS-DOS directory</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC50">4.7 Mclasserase</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">erase memory card</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC51">4.8 Mcopy</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">copy MS-DOS files to/from Unix</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC53">4.9 Mdel</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">delete an MS-DOS file</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC54">4.10 Mdeltree</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">recursively delete an MS-DOS directory</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC55">4.11 Mdir</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">display an MS-DOS directory</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC56">4.12 Mdu</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">list space occupied by directory and its contents</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC57">4.13 Mformat</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">add an MS-DOS filesystem to a low-level formatted floppy disk</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC61">4.15 Minfo</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">get information about an MS-DOS filesystem.</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC62">4.16 Mlabel</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">make an MS-DOS volume label</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC58">4.14 Mkmanifest</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">makes a list of short name equivalents</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC63">4.17 Mmd</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">make an MS-DOS subdirectory</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC64">4.18 Mmount</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">mount an MS-DOS disk</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC66">4.20 Mpartition</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">create an MS-DOS as a partition</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC67">4.21 Mrd</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">remove an MS-DOS subdirectory</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC65">4.19 Mmove</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">move or rename an MS-DOS file or subdirectory</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC68">4.22 Mren</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">rename an existing MS-DOS file</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC69">4.23 Mshowfat</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">shows the FAT map of a file</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC70">4.24 Mtoolstest</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">tests and displays the configuration</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC71">4.25 Mtype</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">display contents of an MS-DOS file</TD></TR>
+ <TR><TD ALIGN="left" VALIGN="TOP"><A HREF="mtools.html#SEC72">4.26 Mzip</A></TD><TD>&nbsp;&nbsp;</TD><TD ALIGN="left" VALIGN="TOP">zip disk specific commands</TD></TR>
+ </TABLE></BLOCKQUOTE>
+ <P>
+ 
+ <A NAME="floppyd"></A>
+ <HR SIZE="6">
+ <A NAME="SEC38"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC37"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC39"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC18"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC39"></A>
+ <H2> 4.1 Floppyd </H2>
+ <!--docid::SEC39::-->
+ <P>
+ 
+ <CODE>Floppyd</CODE> is used as a server to grant access to the floppy drive
+ to clients running on a remote machine, just as an X server grants
+ access to the display to remote clients.  It has the following syntax:
+ </P><P>
+ 
+ <CODE>floppyd</CODE> [<CODE>-d</CODE>] [<CODE>-l</CODE>] [<CODE>-s</CODE> <VAR>port</VAR>] [<CODE>-r</CODE>
+ <VAR>user</VAR>] [<CODE>-b</CODE> <VAR>ipaddr</VAR>] [<CODE>-x</CODE> <VAR>display</VAR>] <VAR>devicenames</VAR>
+ </P><P>
+ 
+ <CODE>floppyd</CODE> is always associated with an X server.  It runs on the
+ same machine as its X server, and listens on port 5703 and above.
+ </P><P>
+ 
+ <HR SIZE="6">
+ <A NAME="SEC39"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC40"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC44"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC40"></A>
+ <H3> 4.1.1 Authentication </H3>
+ <!--docid::SEC40::-->
+ <P>
+ 
+ <CODE>floppyd</CODE> authenticates remote clients using the <CODE>Xauthority</CODE>
+ protocol. Xhost authentication is not supported. Each floppyd is
+ associated with an X server.  When a remote client attempts to connect
+ to floppyd, it sends floppyd the X authority record corresponding to
+ floppyd's X server.  Floppyd in turn then tries to open up a connection
+ to the X server in order to verify the authenticity of the xauth record.
+ If the connection to the X server succeeds, the client is granted
+ access.
+ <CODE>DISPLAY</CODE>.
+ </P><P>
+ 
+ <STRONG>Caution</STRONG>: In order to make authentication work correctly, the
+ local host should <STRONG>not</STRONG> be listed in the <CODE>xhost</CODE> list of
+ allowed hosts.
+  Indeed, hosts listed in <CODE>xhost</CODE> do not need a correct
+ <CODE>Xauthority</CODE> cookie to connect to the X server. As <CODE>floppyd</CODE>
+ runs on the same host as the X server, all its probe connection would
+ succeed even for clients who supplied a bad cookie.  This means that
+ your floppy drive would be open to the world, i.e. a huge security hole.
+  If your X server does not allow you to remove <CODE>localhost:0</CODE> and
+ <CODE>:0</CODE> from the <CODE>xhost</CODE> list, you can prevent floppyd from
+ probing those display names with the <CODE>-l</CODE> option.
+ </P><P>
+ 
+ <HR SIZE="6">
+ <A NAME="SEC40"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC39"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC41"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC41"></A>
+ <H3> 4.1.2 Command line options </H3>
+ <!--docid::SEC41::-->
+ <P>
+ 
+ <DL COMPACT>
+ <DT><CODE>d</CODE>
+ <DD>Daemon mode. Floppyd runs its own server loop.  Do not supply this if
+ you start floppyd from <CODE>inetd.conf</CODE>
+ <DT><CODE>s  <VAR>port</VAR></CODE>
+ <DD>Port number for deamon mode.  Default is 5703 + <VAR>displaynumber</VAR>.
+ This flag implies daemon mode.  For example, for display
+ <CODE>hitchhiker:5</CODE>, the port would be 5708.
+ <DT><CODE>b  <VAR>ipaddr</VAR></CODE>
+ <DD>Bind address (for multihomed hosts). This flag implies daemon mode
+ <DT><CODE>r <VAR>user</VAR></CODE>
+ <DD>Run the server under as the given user
+ <DT><CODE>x <VAR>display</VAR></CODE>
+ <DD>X display to use for authentication. By default, this is taken from the
+ <CODE>DISPLAY</CODE> variable. If neither the <CODE>x</CODE> attribute is present
+ nor <CODE>DISPLAY</CODE> is set, floppyd uses <CODE>:0.0</CODE>.
+ </DL>
+ <P>
+ 
+ <VAR>devicenames</VAR> is a list of device nodes to be opened.  Default
+ is <CODE>/dev/fd0</CODE>. Multiple devices are only supported on mtools
+ versions newer than 3.9.11.
+ </P><P>
+ 
+ <HR SIZE="6">
+ <A NAME="SEC41"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC40"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC42"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC42"></A>
+ <H3> 4.1.3 Connecting to floppyd </H3>
+ <!--docid::SEC42::-->
+ <P>
+ 
+  In order to use floppyd, add the flag <CODE>remote</CODE> to the device
+ description in your <TT>`~/.mtoolsrc'</TT> file.  If the flag <CODE>remote</CODE>
+ is given, the <CODE>file</CODE> parameter of the device description is taken
+ to be a remote address.  It's format is the following:
+ <VAR>hostname</VAR><CODE>:</CODE><VAR>displaynumber</VAR>[<CODE>/</CODE>[<VAR>baseport</VAR>][<CODE>/</CODE><VAR>drive</VAR>]]. When
+ using this entry, mtools connects to port
+ <VAR>baseport</VAR>+<VAR>displaynumber</VAR> at <VAR>hostname</VAR>. By default
+ <VAR>baseport</VAR> is 5703. The drive parameter is to distinguish among
+ multiple drives associated with a single display (only mtools versions
+ more recent than 3.9.11)
+ </P><P>
+ 
+ <HR SIZE="6">
+ <A NAME="SEC42"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC41"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC43"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC43"></A>
+ <H3> 4.1.4 Examples: </H3>
+ <!--docid::SEC43::-->
+ <P>
+ 
+  The following starts a floppy daemon giving access to <TT>`/dev/fd0'</TT>,
+ listening on the default port 5703, tied to the default X servers:
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>floppyd -d /dev/fd0
+ </pre></td></tr></table></P><P>
+ 
+  Each of the following starts a floppy daemon giving access to
+ <TT>`/dev/fd1'</TT>, tied to the :1 local X servers, and listening on port
+ 5704. We assume that the local host is named <CODE>hitchhiker</CODE>.
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>floppyd -d /dev/fd0
+ floppyd -d -x :1 -p 5704 /dev/fd0 
+ </pre></td></tr></table></P><P>
+ 
+  If you want to start floppyd by <CODE>inetd</CODE> instead of running it as a 
+ daemon, insert the following lines into <TT>`/etc/services'</TT>:
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre># floppy daemon
+ floppyd-0    5703/tcp    # floppy daemon for X server :0
+ floppyd-1    5704/tcp    # floppy daemon for X server :1
+ </pre></td></tr></table></P><P>
+ 
+  And insert the following into <TT>`/etc/inetd.conf'</TT> (assuming that you
+ have defined a user named floppy in your <TT>`/etc/passwd'</TT>):
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre># floppy daemon
+ floppyd-0 stream  tcp  wait  floppy  /usr/sbin/floppyd floppyd /dev/fd0 
+ floppyd-1 stream  tcp  wait  floppy  /usr/sbin/floppyd floppyd -x :1 /dev/fd0 
+ </pre></td></tr></table></P><P>
+ 
+  Note that you need to supply the X display names for the second
+ floppyd.  This is because the port is opened by inetd.conf, and hence
+ floppyd cannot know its number to interfere the display number.
+ </P><P>
+ 
+ On the client side, insert the following into your <TT>`~/.mtoolsrc'</TT>
+ to define a drive letter accessing floppy drive in your X terminal:
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>drive x: file="$DISPLAY" remote
+ </pre></td></tr></table></P><P>
+ 
+ If your X terminal has more than one drive, you may access the
+ additional drives as follows:
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>drive y: file="$DISPLAY//1" remote
+ drive z: file="$DISPLAY//2" remote
+ </pre></td></tr></table></P><P>
+ 
+ <A NAME="floppyd_installtest"></A>
+ <HR SIZE="6">
+ <A NAME="SEC43"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC42"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC44"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC44"></A>
+ <H2> 4.2 Floppyd_installtest </H2>
+ <!--docid::SEC44::-->
+ <P>
+ 
+ <CODE>Floppyd_installtest</CODE> is used to check for the presence of a running
+ floppyd daemon. This is usefull, if you have a small frontend script to
+ mtools, which decides whether to use floppyd or not.
+ </P><P>
+ 
+ <CODE>floppyd_installtest</CODE> [<CODE>-f</CODE>]  Connect-String
+ </P><P>
+ 
+ If the <CODE>-f</CODE> option is specified, <CODE>floppyd_installtest</CODE> does a
+ full X-Cookie authentication and complains if this does not work.
+ </P><P>
+ 
+ The connect-String has the format described in the floppyd-section:
+ <VAR>hostname</VAR><CODE>:</CODE><VAR>displaynumber</VAR>[<CODE>/</CODE><VAR>baseport</VAR>]
+ </P><P>
+ 
+ <A NAME="mattrib"></A>
+ <HR SIZE="6">
+ <A NAME="SEC44"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC43"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC45"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC39"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC45"></A>
+ <H2> 4.3 Mattrib </H2>
+ <!--docid::SEC45::-->
+ <P>
+ 
+ <CODE>Mattrib</CODE> is used to change MS-DOS file attribute flags. It has the
+ following syntax:
+ </P><P>
+ 
+ <CODE>mattrib</CODE> [<CODE>-a|+a</CODE>] [<CODE>-h|+h</CODE>] [<CODE>-r|+r</CODE>]
+ [<CODE>-s|+s</CODE>] [<CODE>-/</CODE>]  [<CODE>-p</CODE>] [<CODE>-X</CODE>] <VAR>msdosfile</VAR> [ <VAR>msdosfiles</VAR> <small>...</small> ]
+ </P><P>
+ 
+ <CODE>Mattrib</CODE> adds attribute flags to an MS-DOS file (with the
+ `<CODE>+</CODE>' operator) or remove attribute flags (with the `<CODE>-</CODE>'
+ operator).
+ </P><P>
+ 
+ <CODE>Mattrib</CODE> supports the following attribute bits:
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>a</CODE>
+ <DD>Archive bit.  Used by some backup programs to indicate a new file.
+ <DT><CODE>r</CODE>
+ <DD>Read-only bit.  Used to indicate a read-only file.  Files with this bit
+ set cannot be erased by <CODE>DEL</CODE> nor modified.
+ <DT><CODE>s</CODE>
+ <DD>System bit.  Used by MS-DOS to indicate a operating system file.
+ <DT><CODE>h</CODE>
+ <DD>Hidden bit.  Used to make files hidden from <CODE>DIR</CODE>.
+ </DL>
+ <P>
+ 
+ <CODE>Mattrib</CODE> supports the following command line flags:
+ <DL COMPACT>
+ <DT><CODE>/</CODE>
+ <DD>Recursive.  Recursively list the attributes of the files in the subdirectories.
+ <DT><CODE>X</CODE>
+ <DD>Concise. Prints the attributes whithout any whitespace padding.  If
+ neither the "/" option is given, nor the <VAR>msdosfile</VAR> contains a
+ wildcard, and there is only one Msdos file parameter on the command
+ line, only the attribute is printed, and not the filename.  This option
+ is convenient for scripts
+ <DT><CODE>p</CODE>
+ <DD>Replay mode.  Outputs a series of mformat commands that will reproduce
+ the current situation, starting from a situation as left by untarring
+ the Dos filesystem.  Commands are only output for attribute settings
+ that differ from the default (archive bit set for files, unset for
+ directories).  This option is intended to be used in addition to
+ tar. The <CODE>readonly</CODE> attribute is not taken into account, as tar can
+ set that one itself.
+ </DL>
+ <P>
+ 
+ <A NAME="mbadblocks"></A>
+ <HR SIZE="6">
+ <A NAME="SEC45"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC44"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC46"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC46"></A>
+ <H2> 4.4 Mbadblocks </H2>
+ <!--docid::SEC46::-->
+ <P>
+ 
+ The <CODE>mbadblocks</CODE> command is used to scan an MS-DOS floppy and mark
+ its unused bad blocks as bad. It uses the following syntax:
+ </P><P>
+ 
+ <CODE>mbadblocks</CODE> <VAR>drive</VAR><CODE>:</CODE>
+ <A NAME="IDX51"></A>
+ <A NAME="IDX52"></A>
+ <A NAME="IDX53"></A>
+ <A NAME="IDX54"></A>
+ </P><P>
+ 
+ <CODE>Mbadblocks</CODE> scans an MS-DOS floppy for bad blocks. All unused bad
+ blocks are marked as such in the FAT. This is intended to be used right
+ after <CODE>mformat</CODE>.  It is not intended to salvage bad disks.
+ <HR SIZE="6">
+ <A NAME="SEC46"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC45"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC47"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC48"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC47"></A>
+ <H3> 4.4.1 Bugs </H3>
+ <!--docid::SEC47::-->
+ <CODE>Mbadblocks</CODE> should (but doesn't yet :-( ) also try to salvage bad
+ blocks which are in use by reading them repeatedly, and then mark them
+ bad.
+ <P>
+ 
+ <A NAME="mcat"></A>
+ <HR SIZE="6">
+ <A NAME="SEC47"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC46"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC48"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC48"></A>
+ <H2> 4.5 Mcat </H2>
+ <!--docid::SEC48::-->
+ <P>
+ 
+ The <CODE>mcat</CODE> command is used to copy an entire disk image from or
+ to the floppy device. It uses the following syntax:
+ </P><P>
+ 
+ <CODE>mcat</CODE> [<CODE>-w</CODE>] <VAR>drive</VAR><CODE>:</CODE>
+ <A NAME="IDX55"></A>
+ <A NAME="IDX56"></A>
+ <A NAME="IDX57"></A>
+ <A NAME="IDX58"></A>
+ </P><P>
+ 
+ <CODE>Mcat</CODE> performs the same task as the unix <CODE>cat</CODE> command. It
+ is included into the mtools package, since <CODE>cat</CODE> cannot access
+ remote floppy devices offered by the mtools floppy daemon.
+ Now it is possible to create boot floppies remotely.
+ </P><P>
+ 
+ The default operation is reading. The output is written to stdout.
+ </P><P>
+ 
+ If the <CODE>-w</CODE> option is specified, mcat reads a disk-image from 
+ stdin and writes it to the given device. 
+ <STRONG>Use this carefully!</STRONG> Because of the lowlevel nature of this 
+ command, it will happily destroy any data written before on the
+ disk without warning!
+ </P><P>
+ 
+ <A NAME="mcd"></A>
+ <HR SIZE="6">
+ <A NAME="SEC48"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC47"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC49"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC46"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC49"></A>
+ <H2> 4.6 Mcd </H2>
+ <!--docid::SEC49::-->
+ <P>
+ 
+ The <CODE>mcd</CODE> command is used to change the mtools working directory
+ on the MS-DOS disk. It uses the following syntax:
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre><CODE>mcd</CODE> [<VAR>msdosdirectory</VAR>]
+ </pre></td></tr></table></P><P>
+ 
+ Without arguments, <CODE>mcd</CODE> reports the current device and working
+ directory.  Otherwise, <CODE>mcd</CODE> changes the current device and current
+ working directory relative to an MS-DOS filesystem.
+ </P><P>
+ 
+ The environmental variable <CODE>MCWD</CODE> may be used to locate the file
+ where the device and current working directory information is stored.
+ The default is <TT>`$HOME/.mcwd'</TT>.  Information in this file is ignored
+ if the file is more than 6 hours old.
+ </P><P>
+ 
+ <CODE>Mcd</CODE> returns 0 on success or 1 on failure.
+ </P><P>
+ 
+ Unlike MS-DOS versions of <CODE>CD</CODE>, <CODE>mcd</CODE> can be used to change to
+ another device. It may be wise to remove old <TT>`.mcwd'</TT> files at logout.
+ </P><P>
+ 
+ <A NAME="mclasserase"></A>
+ <HR SIZE="6">
+ <A NAME="SEC49"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC48"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC50"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC50"></A>
+ <H2> 4.7 Mclasserase </H2>
+ <!--docid::SEC50::-->
+ <P>
+ 
+ The <CODE>mclasserase</CODE> command is used to wipe memory cards by
+ overwriting it three times: first with <CODE>0xff</CODE>, then with
+ <CODE>0x00</CODE>, then with <CODE>0xff</CODE> again. The command uses the following
+ syntax:
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre><CODE>mclasserase</CODE> [<CODE>-d</CODE>] <VAR>msdosdrive</VAR>
+ </pre></td></tr></table></P><P>
+ 
+ Dos drive is optional, if none is specified, use <CODE>A:</CODE>. If more than
+ one drive are specified, all but the last are ignored.
+ </P><P>
+ 
+ <CODE>Mclasserase</CODE> accepts the following command line options:
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>d</CODE>
+ <DD>Stop after each erase cycle, for testing purposes
+ <DT><CODE>p</CODE>
+ <DD>Not yet implemented
+ </DL>
+ <P>
+ 
+ <CODE>Mclasserase</CODE> returns 0 on success or -1 on failure.
+ </P><P>
+ 
+ <A NAME="mcopy"></A>
+ <HR SIZE="6">
+ <A NAME="SEC50"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC49"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC51"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC51"></A>
+ <H2> 4.8 Mcopy </H2>
+ <!--docid::SEC51::-->
+ <P>
+ 
+ The <CODE>mcopy</CODE> command is used to copy MS-DOS files to and from
+ Unix. It uses the following syntax:
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre><CODE>mcopy</CODE> [<CODE>-bspanvmQT</CODE>] [<CODE>-D</CODE> <VAR>clash_option</VAR>] <VAR>sourcefile</VAR> <VAR>targetfile</VAR>
+ <CODE>mcopy</CODE> [<CODE>-bspanvmQT</CODE>] [<CODE>-D</CODE> <VAR>clash_option</VAR>] <VAR>sourcefile</VAR> [ <VAR>sourcefiles</VAR><small>...</small> ] <VAR>targetdirectory</VAR>
+ <CODE>mcopy</CODE> [<CODE>-tnvm</CODE>] <VAR>MSDOSsourcefile</VAR>
+ </pre></td></tr></table></P><P>
+ 
+ <CODE>Mcopy</CODE> copies the specified file to the named file, or copies
+ multiple files to the named directory.  The source and target can be
+ either MS-DOS or Unix files.
+ </P><P>
+ 
+ The use of a drive letter designation on the MS-DOS files, 'a:' for
+ example, determines the direction of the transfer.  A missing drive
+ designation implies a Unix file whose path starts in the current
+ directory.  If a source drive letter is specified with no attached file
+ name (e.g. <CODE>mcopy a: .</CODE>), all files are copied from that drive.
+ </P><P>
+ 
+ If only a single, MS-DOS source parameter is provided (e.g. "mcopy
+ a:foo.exe"), an implied destination of the current directory
+ (`<CODE>.</CODE>') is assumed.
+ </P><P>
+ 
+ A filename of `<CODE>-</CODE>' means standard input or standard output, depending
+ on its position on the command line.
+ </P><P>
+ 
+ <CODE>Mcopy</CODE> accepts the following command line options:
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>t</CODE>
+ <DD>Text file transfer.  Mcopy translates incoming carriage return/line
+ feeds to line feeds when copying from Dos to Unix, and vice-versa when
+ copying from Unix to Dos.
+ <DT><CODE>b</CODE>
+ <DD>Batch mode. Optimized for huge recursive copies, but less secure if a
+ crash happens during the copy.
+ <DT><CODE>s</CODE>
+ <DD>Recursive copy.  Also copies directories and their contents
+ <DT><CODE>p</CODE>
+ <DD>Preserves the attributes of the copied files
+ <DT><CODE>Q</CODE>
+ <DD>When mcopying multiple files, quits as soon as one copy fails (for
+ example due to lacking storage space on the target disk)
+ <DT><CODE>a</CODE>
+ <DD>Text (Ascii) file transfer.  <CODE>Mcopy</CODE> translates incoming carriage
+ return/line feeds to line feeds.
+ <DT><CODE>T</CODE>
+ <DD>Text (Ascii) file transfer with charset conversion.  Differs from
+ <CODE>-a</CODE> in the <CODE>Mcopy</CODE> also translates incoming PC-8 characters
+ to ISO-8859-1 equivalents as far as possible.  When reading DOS files,
+ untranslatable characters are replaced by '<CODE>#</CODE>'; when writing DOS files,
+ untranslatable characters are replaced by '<CODE>.</CODE>'.
+ <DT><CODE>n</CODE>
+ <DD>No confirmation when overwriting Unix files.  <CODE>Mcopy</CODE> doesn't warn
+ the user when overwriting an existing Unix file. If the target file already exists,
+ and the <CODE>-n</CODE> option is not in effect, <CODE>mcopy</CODE> asks whether to
+ overwrite the file or to rename the new file (<A HREF="mtools.html#SEC9">2.5 Name clashes</A>) for
+ details).  In order to switch off confirmation for DOS files, use <CODE>-o</CODE>.
+ <DT><CODE>m</CODE>
+ <DD>Preserve the file modification time.
+ <DT><CODE>v</CODE>
+ <DD>Verbose. Displays the name of each file as it is copied.
+ </DL>
+ <P>
+ 
+ <HR SIZE="6">
+ <A NAME="SEC51"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC50"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC52"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC53"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC52"></A>
+ <H3> 4.8.1 Bugs </H3>
+ <!--docid::SEC52::-->
+ Unlike MS-DOS, the '+' operator (append) from MS-DOS is not
+ supported. However, you may use <CODE>mtype</CODE> to produce the same effect:
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>mtype a:file1 a:file2 a:file3 &#62;unixfile
+ mtype a:file1 a:file2 a:file3 | mcopy - a:msdosfile
+ </pre></td></tr></table><P>
+ 
+ <A NAME="mdel"></A>
+ <HR SIZE="6">
+ <A NAME="SEC52"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC51"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC53"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC53"></A>
+ <H2> 4.9 Mdel </H2>
+ <!--docid::SEC53::-->
+ <P>
+ 
+ The <CODE>mdel</CODE> command is used to delete an MS-DOS file. Its syntax
+ is:
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=display><pre style="font-family: serif"><CODE>mdel</CODE> [<CODE>-v</CODE>] <VAR>msdosfile</VAR> [ <VAR>msdosfiles</VAR> <small>...</small>  ]
+ </pre></td></tr></table></P><P>
+ 
+ <CODE>Mdel</CODE> deletes files on an MS-DOS filesystem.
+ </P><P>
+ 
+ <CODE>Mdel</CODE> asks for verification prior to removing a read-only file.
+ </P><P>
+ 
+ <A NAME="mdeltree"></A>
+ <HR SIZE="6">
+ <A NAME="SEC53"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC52"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC54"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC51"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC54"></A>
+ <H2> 4.10 Mdeltree </H2>
+ <!--docid::SEC54::-->
+ <P>
+ 
+ The <CODE>mdeltree</CODE> command is used to delete an MS-DOS file. Its syntax
+ is:
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=display><pre style="font-family: serif"><CODE>mdeltree</CODE> [<CODE>-v</CODE>] <VAR>msdosdirectory</VAR> [<VAR>msdosdirectories</VAR><small>...</small>]
+ </pre></td></tr></table></P><P>
+ 
+ <CODE>Mdeltree</CODE> removes a directory and all the files and subdirectories
+ it contains from an MS-DOS filesystem. An error occurs if the directory
+ to be removed does not exist.
+ </P><P>
+ 
+ <A NAME="mdir"></A>
+ <HR SIZE="6">
+ <A NAME="SEC54"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC53"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC55"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC55"></A>
+ <H2> 4.11 Mdir </H2>
+ <!--docid::SEC55::-->
+ <P>
+ 
+ The <CODE>mdir</CODE> command is used to display an MS-DOS directory. Its
+ syntax is:
+ </P><P>
+ 
+ <CODE>mdir</CODE> [<CODE>-/</CODE>] [<CODE>-f</CODE>] [<CODE>-w</CODE>] [<CODE>-a</CODE>] [<CODE>-b</CODE>] <VAR>msdosfile</VAR> [ <VAR>msdosfiles</VAR><small>...</small>] 
+ </P><P>
+ 
+ <CODE>Mdir</CODE>
+ displays the contents of MS-DOS directories, or the entries for some
+ MS-DOS files.
+ </P><P>
+ 
+ <CODE>Mdir</CODE> supports the following command line options:
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>/</CODE>
+ <DD>Recursive output, just like Dos' <CODE>-s</CODE> option
+ <DT><CODE>w</CODE>
+ <DD>Wide output.  With this option, <CODE>mdir</CODE> prints the filenames across
+ the page without displaying the file size or creation date.
+ <DT><CODE>a</CODE>
+ <DD>Also list hidden files.
+ <DT><CODE>f</CODE>
+ <DD>Fast.  Do not try to find out free space.  On larger disks, finding out
+ the amount of free space takes up some non trivial amount of time, as
+ the whole FAT must be read in and scanned.  The <CODE>-f</CODE> flag bypasses
+ this step.  This flag is not needed on FAT32 filesystems, which store
+ the size explicitely.
+ <DT><CODE>b</CODE>
+ <DD>Concise listing. Lists each directory name or filename, one per line
+ (including the filename extension). This switch displays no heading
+ information and no summary. Only a newline separated list of pathnames
+ is displayed.
+ </DL>
+ <P>
+ 
+ An error occurs if a component of the path is not a directory.
+ </P><P>
+ 
+ <A NAME="mdu"></A>
+ <HR SIZE="6">
+ <A NAME="SEC55"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC54"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC56"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC56"></A>
+ <H2> 4.12 Mdu </H2>
+ <!--docid::SEC56::-->
+ <P>
+ 
+ <CODE>Mdu</CODE> is used to list the space occupied by a directory, its
+ subdirectories and its files. It is similar to the <CODE>du</CODE> command on
+ Unix.  The unit used are clusters.  Use the minfo command to find out
+ the cluster size.
+ </P><P>
+ 
+ <CODE>mdu</CODE> [<CODE>-a</CODE>] [ <VAR>msdosfiles</VAR> <small>...</small> ]
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>a</CODE>
+ <DD>All files.  List also the space occupied for individual files.
+ <DT><CODE>s</CODE>
+ <DD>Only list the total space, don't give details for each subdirectory.
+ </DL>
+ <P>
+ 
+ <A NAME="mformat"></A>
+ <HR SIZE="6">
+ <A NAME="SEC56"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC55"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC57"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC57"></A>
+ <H2> 4.13 Mformat </H2>
+ <!--docid::SEC57::-->
+ <P>
+ 
+ The <CODE>mformat</CODE> command is used to add an MS-DOS filesystem to a
+ low-level formatted diskette. Its syntax is:
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=display><pre style="font-family: serif"><CODE>mformat</CODE> [<CODE>-t</CODE> <VAR>cylinders</VAR>] [<CODE>-h</CODE> <VAR>heads</VAR>] [<CODE>-s</CODE> <VAR>sectors</VAR>]
+   [<CODE>-f</CODE> <VAR>size</VAR>] [<CODE>-1</CODE>] [<CODE>-4</CODE>] [<CODE>-8</CODE>]
+   [<CODE>-v</CODE> <VAR>volume_label</VAR>]
+   [<CODE>-F</CODE>] [<CODE>-S</CODE> <VAR>sizecode</VAR>] [<CODE>-X</CODE>]
+   [<CODE>-2</CODE> <VAR>sectors_on_track_0</VAR>] [<CODE>-3</CODE>]
+   [<CODE>-0</CODE> <VAR>rate_on_track_0</VAR>] [<CODE>-A</CODE> <VAR>rate_on_other_tracks</VAR>]
+   [<CODE>-M</CODE> <VAR>software_sector_size</VAR>]
+   [<CODE>-N</CODE> <VAR>serial_number</VAR>] [<CODE>-a</CODE>]
+   [<CODE>-C</CODE>] [<CODE>-H</CODE> <VAR>hidden_sectors</VAR>] [<CODE>-I</CODE> <VAR>fsVersion</VAR>]
+   [<CODE>-r</CODE> <VAR>root_sectors</VAR>] [<CODE>-L</CODE> <VAR>fat_len</VAR>] 
+   [<CODE>-B</CODE> <VAR>boot_sector</VAR>] [<CODE>-k</CODE>]
+   [<CODE>-m</CODE> <VAR>media_descriptor</VAR>]
+   <VAR>drive:</VAR>
+ </pre></td></tr></table></P><P>
+ 
+ <CODE>Mformat</CODE> adds a minimal MS-DOS filesystem (boot sector, FAT, and
+ root directory) to a diskette that has already been formatted by a Unix
+ low-level format.
+ </P><P>
+ 
+ The following options are supported: (The S, 2, 1 and M options may not
+ exist if this copy of mtools has been compiled without the USE_2M
+ option)
+ </P><P>
+ 
+ The following options are the same as for Dos's format command:
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>v</CODE>
+ <DD>Specifies the volume label. A volume label identifies the disk and can
+ be a maximum of 11 characters. If you omit the -v switch, mlabel will
+ assign no label to the disk.
+ <DT><CODE>f</CODE>
+ <DD>Specifies the size of the DOS filesystem to format. Only a certain
+ number of predefined sizes are supported by this flag; for others use
+ the -h/-t/-s flags. The following sizes are supported:
+ <DL COMPACT>
+ <DT>160
+ <DD>160K, single-sided, 8 sectors per track, 40 cylinders (for 5 1/4 DD)
+ <DT>180
+ <DD>160K, single-sided, 9 sectors per track, 40 cylinders (for 5 1/4 DD)
+ <DT>320
+ <DD>320K, double-sided, 8 sectors per track, 40 cylinders (for 5 1/4 DD)
+ <DT>360
+ <DD>360K, double-sided, 9 sectors per track, 40 cylinders (for 5 1/4 DD)
+ <DT>720
+ <DD>720K, double-sided, 9 sectors per track, 80 cylinders (for 3 1/2 DD)
+ <DT>1200
+ <DD>1200K, double-sided, 15 sectors per track, 80 cylinders (for 5 1/4 HD)
+ <DT>1440
+ <DD>1440K, double-sided, 18 sectors per track, 80 cylinders (for 3 1/2 HD)
+ <DT>2880
+ <DD>2880K, double-sided, 36 sectors per track, 80 cylinders (for 3 1/2 ED)
+ </DL>
+ <P>
+ 
+ <DT><CODE>t</CODE>
+ <DD>Specifies the number of tracks on the disk.
+ <DT><CODE>h</CODE>
+ <DD>The number of heads (sides).
+ <DT><CODE>n</CODE>
+ <DD>Specifies the number of sectors per track. If the 2m option is given,
+ number of 512-byte sector equivalents on generic tracks (i.e. not head 0
+ track 0).  If the 2m option is not given, number of physical sectors per
+ track (which may be bigger than 512 bytes).
+ <P>
+ 
+ <DT><CODE>1</CODE>
+ <DD>Formats a single side (equivalent to -h 1)
+ <P>
+ 
+ <DT><CODE>4</CODE>
+ <DD>Formats a 360K double-sided disk (equivalent to -f 360). When used
+ together with -the 1 switch, this switch formats a 180K disk
+ <P>
+ 
+ <DT><CODE>8</CODE>
+ <DD>Formats a disk with 8 sectors per track.
+ <P>
+ 
+ </DL>
+ <P>
+ 
+ MSDOS format's <CODE>q</CODE>, <CODE>u</CODE> and <CODE>b</CODE> options are not
+ supported, and <CODE>s</CODE> has a different meaning.
+ </P><P>
+ 
+ The following options are specific to mtools:
+ </P><P>
+ 
+ <DL COMPACT>
+ 
+ <DT><CODE>F</CODE>
+ <DD>Format the partition as FAT32.
+ <P>
+ 
+ <DT><CODE>S</CODE>
+ <DD>The sizecode. The size of the sector is 2 ^ (sizecode + 7).
+ <DT><CODE>X</CODE>
+ <DD>formats the disk as an XDF disk. See section <A HREF="mtools.html#SEC15">2.7.4 XDF</A>, for more details. The disk
+ has first to be low-level formatted using the xdfcopy utility included
+ in the fdutils package. XDF disks are used for instance for OS/2 install
+ disks.
+ <DT><CODE>2</CODE>
+ <DD>2m format. The parameter to this option describes the number of
+ sectors on track 0, head 0. This option is recommended for sectors
+ bigger than normal.
+ <DT><CODE>3</CODE>
+ <DD>don't use a 2m format, even if the current geometry of the disk is a 2m 
+ geometry.
+ <DT><CODE>0</CODE>
+ <DD>Data transfer rate on track 0
+ <DT><CODE>A</CODE>
+ <DD>Data transfer rate on tracks other than 0
+ <DT><CODE>M</CODE>
+ <DD>software sector size. This parameter describes the sector size in bytes used
+ by the MS-DOS filesystem. By default it is the physical sector size.
+ <DT><CODE>N</CODE>
+ <DD>Uses the requested serial number, instead of generating one
+ automatically
+ <DT><CODE>a</CODE>
+ <DD>If this option is given, an Atari style serial number is generated.
+ Ataris store their serial number in the OEM label.
+ <DT><CODE>C</CODE>
+ <DD>creates the disk image file to install the MS-DOS filesystem on
+ it. Obviously, this is useless on physical devices such as floppies
+ and hard disk partitions, but is interesting for image files.
+ <DT><CODE>H</CODE>
+ <DD>number of hidden sectors. This parameter is useful for formatting hard
+ disk partition, which are not aligned on track boundaries (i.e. first
+ head of first track doesn't belong to the partition, but contains a
+ partition table). In that case the number of hidden sectors is in
+ general the number of sectors per cylinder. This is untested.
+ <DT><CODE>I</CODE>
+ <DD>Sets the fsVersion id when formatting a FAT32 drive.  In order to find
+ this out, run minfo on an existing FAT32 drive, and mail me about it, so
+ I can include the correct value in future versions of mtools.
+ <DT><CODE>c</CODE>
+ <DD>Sets the size of a cluster (in sectors).  If this cluster size would
+ generate a FAT that too big for its number of bits, mtools automatically
+ increases the cluster size, until the FAT is small enough.
+ <DT><CODE>d</CODE>
+ <DD>Sets the number of FAT copies. Default is 2. This setting can also be
+ specified using the <CODE>MTOOLS_NFATS</CODE> environment variable.
+ <DT><CODE>r</CODE>
+ <DD>Sets the size of the root directory (in sectors).  Only applicable to 12
+ and 16 bit FATs. This setting can also be specified using the
+ <CODE>MTOOLS_DIR_LEN</CODE> environment variable.
+ <DT><CODE>L</CODE>
+ <DD>Sets the length of the FAT.
+ <DT><CODE>B</CODE>
+ <DD>Use the bootsector stored in the given file or device, instead of using
+ its own.  Only the geometry fields are updated to match the target disks
+ parameters.
+ <DT><CODE>k</CODE>
+ <DD>Keep the existing boot sector as much as possible.  Only the geometry
+ fields and other similar filesystem data are updated to match the target
+ disks parameters.
+ <P>
+ 
+ <DT><CODE>m</CODE>
+ <DD>Use a non-standard media descriptor byte for this disk. The media
+ descriptor is stored at position 21 of the boot sector, and as first
+ byte in each FAT copy. Using this option may confuse DOS or older mtools
+ version, and may make the disk unreadable. Only use if you know what you
+ are doing.
+ <P>
+ 
+ </DL>
+ <P>
+ 
+ To format a diskette at a density other than the default, you must supply
+ (at least) those command line parameters that are different from the
+ default.
+ </P><P>
+ 
+ <CODE>Mformat</CODE> returns 0 on success or 1 on failure.
+ </P><P>
+ 
+ It doesn't record bad block information to the Fat, use
+ <CODE>mbadblocks</CODE> for that.
+ </P><P>
+ 
+ <A NAME="mkmanifest"></A>
+ <HR SIZE="6">
+ <A NAME="SEC57"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC56"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC58"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC58"></A>
+ <H2> 4.14 Mkmanifest </H2>
+ <!--docid::SEC58::-->
+ <P>
+ 
+ The <CODE>mkmanifest</CODE> command is used to create a shell script (packing
+ list) to restore Unix filenames. Its syntax is:
+ </P><P>
+ 
+ <CODE>mkmanifest</CODE> [ <VAR>files</VAR> ]
+ </P><P>
+ 
+ <CODE>Mkmanifest</CODE> creates a shell script that aids in the restoration of
+ Unix filenames that got clobbered by the MS-DOS filename restrictions.
+ MS-DOS filenames are restricted to 8 character names, 3 character
+ extensions, upper case only, no device names, and no illegal characters.
+ </P><P>
+ 
+ The mkmanifest program is compatible with the methods used in
+ <CODE>pcomm, arc,</CODE> and <CODE>mtools</CODE> to change perfectly good Unix
+ filenames to fit the MS-DOS restrictions. This command is only useful if
+ the target system which will read the diskette cannot handle vfat long
+ names.
+ </P><P>
+ 
+ <HR SIZE="6">
+ <A NAME="SEC58"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC57"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC59"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC61"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC59"></A>
+ <H3> 4.14.1 Example </H3>
+ <!--docid::SEC59::-->
+ You want to copy the following Unix files to a MS-DOS diskette (using the
+ <CODE>mcopy</CODE> command).
+ <P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>  very_long_name
+   2.many.dots
+   illegal:
+   good.c
+   prn.dev
+   Capital
+ </pre></td></tr></table></P><P>
+ 
+ <CODE>Mcopy</CODE>
+ converts the names to:
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>  very_lon
+   2xmany.dot
+   illegalx
+   good.c
+   xprn.dev
+   capital
+ </pre></td></tr></table></P><P>
+ 
+ The command:
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>mkmanifest very_long_name 2.many.dots illegal: good.c prn.dev Capital &#62;manifest
+ </pre></td></tr></table>would produce the following:
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>  mv very_lon very_long_name
+   mv 2xmany.dot 2.many.dots
+   mv illegalx illegal:
+   mv xprn.dev prn.dev
+   mv capital Capital
+ </pre></td></tr></table></P><P>
+ 
+ Notice that "good.c" did not require any conversion, so it did not
+ appear in the output.
+ </P><P>
+ 
+ Suppose I've copied these files from the diskette to another Unix
+ system, and I now want the files back to their original names.  If the
+ file "manifest" (the output captured above) was sent along with those
+ files, it could be used to convert the filenames.
+ </P><P>
+ 
+ <HR SIZE="6">
+ <A NAME="SEC59"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC58"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC60"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC60"></A>
+ <H3> 4.14.2 Bugs </H3>
+ <!--docid::SEC60::-->
+ <P>
+ 
+ The short names generated by <CODE>mkmanifest</CODE> follow the old convention
+ (from mtools-2.0.7) and not the one from Windows 95 and mtools-3.0.
+ </P><P>
+ 
+ <A NAME="minfo"></A>
+ <HR SIZE="6">
+ <A NAME="SEC60"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC59"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC61"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC61"></A>
+ <H2> 4.15 Minfo </H2>
+ <!--docid::SEC61::-->
+ <P>
+ 
+ The <CODE>minfo</CODE> command prints the parameters of a Dos filesystem, such
+ as number of sectors, heads and cylinders.  It also prints an mformat
+ command line which can be used to create a similar Dos filesystem on
+ another media.  However, this doesn't work with 2m or Xdf media, and
+ with Dos 1.0 filesystems
+ <TABLE><tr><td>&nbsp;</td><td class=display><pre style="font-family: serif"><CODE>minfo</CODE> <VAR>drive</VAR>:
+ </pre></td></tr></table></P><P>
+ 
+ Mlabel supports the following option:
+ <DL COMPACT>
+ <DT><CODE>v</CODE>
+ <DD>Prints a hexdump of the bootsector, in addition to the other information
+ </DL>
+ <P>
+ 
+ <A NAME="mlabel"></A>
+ <HR SIZE="6">
+ <A NAME="SEC61"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC60"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC62"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC58"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC62"></A>
+ <H2> 4.16 Mlabel </H2>
+ <!--docid::SEC62::-->
+ <P>
+ 
+ The <CODE>mlabel</CODE> command adds a volume label to a disk. Its syntax is:
+ <TABLE><tr><td>&nbsp;</td><td class=display><pre style="font-family: serif"><CODE>mlabel</CODE> [<CODE>-vcsn</CODE>] [<CODE>-N</CODE> <VAR>serial</VAR>] <VAR>drive</VAR>:[<VAR>new_label</VAR>]
+ </pre></td></tr></table></P><P>
+ 
+ <CODE>Mlabel</CODE> displays the current volume label, if present. If
+ <VAR>new_label</VAR> is not given, and if neither the <CODE>c</CODE> nor the
+ <CODE>s</CODE> options are set, it prompts the user for a new volume label.
+ To delete an existing volume label, press return at the prompt.
+ </P><P>
+ 
+ Reasonable care is taken to create a valid MS-DOS volume label.  If an
+ invalid label is specified, <CODE>mlabel</CODE> changes the label (and
+ displays the new label if the verbose mode is set). <CODE>Mlabel</CODE>
+ returns 0 on success or 1 on failure.
+ </P><P>
+ 
+ Mlabel supports the following options:
+ <DL COMPACT>
+ <DT><CODE>c</CODE>
+ <DD>Clears an existing label, without prompting the user
+ <DT><CODE>s</CODE>
+ <DD>Shows the existing label, without prompting the user.
+ <DT><CODE>n</CODE>
+ <DD>Assigns a new (random) serial number to the disk
+ <DT><CODE>N <VAR>serial</VAR></CODE>
+ <DD>Sets the supplied serial number. The serial number should be supplied as
+ an 8 digit hexadecimal number, without spaces
+ </DL>
+ <P>
+ 
+ <A NAME="mmd"></A>
+ <HR SIZE="6">
+ <A NAME="SEC62"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC61"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC63"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC63"></A>
+ <H2> 4.17 Mmd </H2>
+ <!--docid::SEC63::-->
+ <P>
+ 
+ The <CODE>mmd</CODE> command is used to make an MS-DOS subdirectory. Its
+ syntax is:
+ </P><P>
+ 
+ <CODE>mmd</CODE> [<CODE>-D</CODE> <VAR>clash_option</VAR>] <VAR>msdosdirectory</VAR> [
+ <VAR>msdosdirectories</VAR><small>...</small> ]
+ </P><P>
+ 
+ <CODE>Mmd</CODE> makes a new directory on an MS-DOS filesystem. An error occurs
+ if the directory already exists.
+ </P><P>
+ 
+ <A NAME="mmount"></A>
+ <HR SIZE="6">
+ <A NAME="SEC63"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC62"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC64"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC64"></A>
+ <H2> 4.18 Mmount </H2>
+ <!--docid::SEC64::-->
+ <P>
+ 
+ The <CODE>mmount</CODE> command is used to mount an MS-DOS disk. It is only
+ available on Linux, as it is only useful if the OS kernel allows to
+ configure the disk geometry. Its syntax is:
+ </P><P>
+ 
+ <CODE>mmount</CODE> <VAR>msdosdrive</VAR> [<VAR>mountargs</VAR>]
+ </P><P>
+ 
+ <CODE>Mmount</CODE>
+ reads the boot sector of an MS-DOS disk, configures the drive geometry,
+ and finally mounts it passing
+ <CODE>mountargs</CODE> to <CODE>mount. </CODE>
+ If no mount arguments are specified, the name of the device is
+ used. If the disk is write protected, it is automatically mounted read
+ only.
+ </P><P>
+ 
+ <A NAME="mmove"></A>
+ <HR SIZE="6">
+ <A NAME="SEC64"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC63"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC65"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC65"></A>
+ <H2> 4.19 Mmove </H2>
+ <!--docid::SEC65::-->
+ <P>
+ 
+ The <CODE>mmove</CODE> command is used to moves or renames an existing MS-DOS
+ file or subdirectory.
+ <TABLE><tr><td>&nbsp;</td><td class=display><pre style="font-family: serif"><CODE>mmove</CODE> [<CODE>-v</CODE>] [<CODE>-D</CODE> <VAR>clash_option</VAR>] <VAR>sourcefile</VAR> <VAR>targetfile</VAR>
+ <CODE>mmove</CODE> [<CODE>-v</CODE>]  [<CODE>-D</CODE> <VAR>clash_option</VAR>] <VAR>sourcefile</VAR> [ <VAR>sourcefiles</VAR><small>...</small> ] <VAR>targetdirectory</VAR>
+ </pre></td></tr></table><CODE>Mmove</CODE> moves or renames an existing MS-DOS file or
+ subdirectory. Unlike the MS-DOS version of <CODE>MOVE</CODE>, <CODE>mmove</CODE> is
+ able to move subdirectories.  Files or directories can only be moved
+ within one filesystem. Data cannot be moved from Dos to Unix or
+ vice-versa.  If you omit the drive letter from the target file or
+ directory, the same letter as for the source is assumed.  If you omit
+ the drive letter from all parameters, drive a: is assumed by default.
+ </P><P>
+ 
+ <A NAME="mpartition"></A>
+ <HR SIZE="6">
+ <A NAME="SEC65"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC64"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC66"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC66"></A>
+ <H2> 4.20 Mpartition </H2>
+ <!--docid::SEC66::-->
+ <P>
+ 
+ The <CODE>mpartition</CODE> command is used to create MS-DOS filesystems as
+ partitions.  This is intended to be used on non-Linux systems,
+ i.e. systems where fdisk and easy access to Scsi devices are not
+ available.  This command only works on drives whose partition variable
+ is set.
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=display><pre style="font-family: serif"><CODE>mpartition</CODE> <CODE>-p</CODE> <VAR>drive</VAR>
+ <CODE>mpartition</CODE> <CODE>-r</CODE> <VAR>drive</VAR>
+ <CODE>mpartition</CODE> <CODE>-I</CODE> [<CODE>-B</CODE> <VAR>bootSector</VAR>] <VAR>drive</VAR> 
+ <CODE>mpartition</CODE> <CODE>-a</CODE> <VAR>drive</VAR>
+ <CODE>mpartition</CODE> <CODE>-d</CODE> <VAR>drive</VAR>
+ <CODE>mpartition</CODE> <CODE>-c</CODE> [<CODE>-s</CODE> <VAR>sectors</VAR>] [<CODE>-h</CODE> <VAR>heads</VAR>]
+ [<CODE>-t</CODE> <VAR>cylinders</VAR>] [<CODE>-v</CODE> [<CODE>-T</CODE> <VAR>type</VAR>] [<CODE>-b</CODE>
+ <VAR>begin</VAR>] [<CODE>-l</CODE> length] [<CODE>-f</CODE>]
+ 
+ </pre></td></tr></table></P><P>
+ 
+ Mpartition supports the following operations:
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>p</CODE>
+ <DD>Prints a command line to recreate the partition for the drive.  Nothing
+ is printed if the partition for the drive is not defined, or an
+ inconsistency has been detected.  If verbose (<CODE>-v</CODE>) is also set,
+ prints the current partition table.
+ <DT><CODE>r</CODE>
+ <DD>Removes the partition described by <VAR>drive</VAR>.
+ <DT><CODE>I</CODE>
+ <DD>Initializes the partition table, and removes all partitions.
+ <DT><CODE>c</CODE>
+ <DD>Creates the partition described by <VAR>drive</VAR>.
+ <DT><CODE>a</CODE>
+ <DD>"Activates" the partition, i.e. makes it bootable.  Only one partition
+ can be bootable at a time.
+ <DT><CODE>d</CODE>
+ <DD>"Desactivates" the partition, i.e. makes it unbootable.
+ </DL>
+ <P>
+ 
+ If no operation is given, the current settings are printed.
+ </P><P>
+ 
+ For partition creations, the following options are available:
+ <DL COMPACT>
+ <DT><CODE>s <VAR>sectors</VAR></CODE>
+ <DD>The number of sectors per track of the partition (which is also the
+ number of sectors per track for the whole drive).
+ <DT><CODE>h <VAR>heads</VAR></CODE>
+ <DD>The number of heads of the partition (which is also the number of heads
+ for the whole drive).  By default, the geometry information (number of
+ sectors and heads) is figured out from neighbouring partition table
+ entries, or guessed from the size.
+ <DT><CODE>t <VAR>cylinders</VAR></CODE>
+ <DD>The number of cylinders of the partition (not the number of cylinders of
+ the whole drive.
+ <DT><CODE>b <VAR>begin</VAR></CODE>
+ <DD>The starting offset of the partition, expressed in sectors. If begin is
+ not given, mpartition lets the partition begin at the start of the disk
+ (partition number 1), or immediately after the end of the previous
+ partition.
+ <DT><CODE>l <VAR>length</VAR></CODE>
+ <DD>The size (length) of the partition, expressed in sectors.  If end is not
+ given, mpartition figures out the size from the number of sectors, heads
+ and cylinders.  If these are not given either, it gives the partition
+ the biggest possible size, considering disk size and start of the next
+ partition.
+ </DL>
+ <P>
+ 
+ The following option is available for all operation which modify the
+ partition table:
+ <DL COMPACT>
+ <DT><CODE>f</CODE>
+ <DD>Usually, before writing back any changes to the partition, mpartition
+ performs certain consistenct checks, such as checking for overlaps and
+ proper alignment of the partitions.  If any of these checks fails, the
+ partition table is not changes.  The <CODE>-f</CODE> allows you to override
+ these safeguards.
+ </DL>
+ <P>
+ 
+ The following options are available for all operations:
+ <DL COMPACT>
+ <DT><CODE>v</CODE>
+ <DD>Together with <CODE>-p</CODE> prints the partition table as it is now (no
+ change operation), or as it is after it is modified.
+ <DT><CODE>vv</CODE>
+ <DD>If the verbosity flag is given twice, mpartition will print out a
+ hexdump of the partition table when reading it from and writing it to
+ the device.
+ </DL>
+ <P>
+ 
+ The following option is available for partition table initialization:
+ <DL COMPACT>
+ <DT><CODE>B <VAR>bootSector</VAR></CODE>
+ <DD>Reads the template master boot record from file <VAR>bootSector</VAR>.
+ </DL>
+ <P>
+ 
+ <A NAME="mrd"></A>
+ <HR SIZE="6">
+ <A NAME="SEC66"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC65"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC67"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC67"></A>
+ <H2> 4.21 Mrd </H2>
+ <!--docid::SEC67::-->
+ <P>
+ 
+ The <CODE>mrd</CODE> command is used to remove an MS-DOS subdirectory. Its
+ syntax is:
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=display><pre style="font-family: serif"><CODE>mrd</CODE> [<CODE>-v</CODE>] <VAR>msdosdirectory</VAR> [ <VAR>msdosdirectories</VAR><small>...</small> ]
+ </pre></td></tr></table></P><P>
+ 
+ <CODE>Mrd</CODE> removes a directory from an MS-DOS filesystem. An error occurs
+ if the directory does not exist or is not empty.
+ </P><P>
+ 
+ <A NAME="mren"></A>
+ <HR SIZE="6">
+ <A NAME="SEC67"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC66"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC68"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC68"></A>
+ <H2> 4.22 Mren </H2>
+ <!--docid::SEC68::-->
+ <P>
+ 
+ The <CODE>mren</CODE> command is used to rename or move an existing MS-DOS
+ file or subdirectory. Its syntax is:
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=display><pre style="font-family: serif"><CODE>mren</CODE> [<CODE>-voOsSrRA</CODE>] <VAR>sourcefile</VAR> <VAR>targetfile</VAR>
+ </pre></td></tr></table></P><P>
+ 
+ <CODE>Mren</CODE>
+ renames an existing file on an MS-DOS filesystem.
+ </P><P>
+ 
+ In verbose mode, <CODE>Mren</CODE> displays the new filename if the name
+ supplied is invalid.
+ </P><P>
+ 
+ If the first syntax is used (only one sourcefile), and if the target
+ name doesn't contain any slashes or colons, the file (or subdirectory)
+ is renamed in the same directory, instead of being moved to the current
+ <CODE>mcd</CODE> directory as would be the case with <CODE>mmove</CODE>. Unlike the
+ MS-DOS version of <CODE>REN</CODE>, <CODE>mren</CODE> can be used to rename
+ directories.
+ </P><P>
+ 
+ <A NAME="mshowfat"></A>
+ <HR SIZE="6">
+ <A NAME="SEC68"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC67"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC69"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC69"></A>
+ <H2> 4.23 Mshowfat </H2>
+ <!--docid::SEC69::-->
+ <P>
+ 
+ The <CODE>mshowfat</CODE> command is used to display the FAT entries for a
+ file.  Syntax:
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=display><pre style="font-family: serif"><CODE>$ mshowfat files</CODE>
+ </pre></td></tr></table></P><P>
+ 
+ <A NAME="mtoolstest"></A>
+ <HR SIZE="6">
+ <A NAME="SEC69"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC68"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC70"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC70"></A>
+ <H2> 4.24 Mtoolstest </H2>
+ <!--docid::SEC70::-->
+ <P>
+ 
+ The <CODE>mtoolstest</CODE> command is used to tests the mtools configuration
+ files. To invoke it, just type <CODE>mtoolstest</CODE> without any arguments.
+ <CODE>Mtoolstest</CODE> reads the mtools configuration files, and prints the
+ cumulative configuration to <CODE>stdout</CODE>. The output can be used as a
+ configuration file itself (although you might want to remove redundant
+ clauses).  You may use this program to convert old-style configuration
+ files into new style configuration files.
+ </P><P>
+ 
+ <A NAME="mtype"></A>
+ <HR SIZE="6">
+ <A NAME="SEC70"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC69"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC71"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC71"></A>
+ <H2> 4.25 Mtype </H2>
+ <!--docid::SEC71::-->
+ <P>
+ 
+ The <CODE>mtype</CODE> command is used to display contents of an MS-DOS
+ file. Its syntax is:
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=display><pre style="font-family: serif"><CODE>mtype</CODE> [<CODE>-ts</CODE>] <VAR>msdosfile</VAR> [ <VAR>msdosfiles</VAR><small>...</small> ]
+ </pre></td></tr></table></P><P>
+ 
+ <CODE>Mtype</CODE> displays the specified MS-DOS file on the screen.
+ </P><P>
+ 
+ In addition to the standard options, <CODE>Mtype</CODE> allows the following
+ command line options:
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>t</CODE>
+ <DD>Text file viewing.  <CODE>Mtype</CODE> translates incoming carriage
+ return/line feeds to line feeds.
+ <DT><CODE>s</CODE>
+ <DD><CODE>Mtype</CODE> strips the high bit from the data.
+ </DL>
+ <P>
+ 
+ The <CODE>mcd</CODE> command may be used to establish the device and the
+ current working directory (relative to MS-DOS), otherwise the default is
+ <CODE>A:/</CODE>.
+ </P><P>
+ 
+ <CODE>Mtype</CODE> returns 0 on success, 1 on utter failure, or 2 on partial
+ failure.
+ </P><P>
+ 
+ Unlike the MS-DOS version of <CODE>TYPE</CODE>, <CODE>mtype</CODE> allows multiple
+ arguments.
+ </P><P>
+ 
+ <A NAME="mzip"></A>
+ <HR SIZE="6">
+ <A NAME="SEC71"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC70"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC72"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC72"></A>
+ <H2> 4.26 Mzip </H2>
+ <!--docid::SEC72::-->
+ <P>
+ 
+ The <CODE>mzip</CODE> command is used to issue ZIP disk specific commands on
+ Linux, Solaris or HPUX. Its syntax is:
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=display><pre style="font-family: serif"><CODE>mzip</CODE> [<CODE>-epqrwx</CODE>]
+ </pre></td></tr></table></P><P>
+ 
+ <CODE>Mzip</CODE> allows the following
+ command line options:
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>e</CODE>
+ <DD>Ejects the disk.
+ <DT><CODE>f</CODE>
+ <DD>Force eject even if the disk is mounted (must be given in addition to
+ <CODE>-e</CODE>).
+ <DT><CODE>r</CODE>
+ <DD>Write protect the disk.
+ <DT><CODE>w</CODE>
+ <DD>Remove write protection.
+ <DT><CODE>p</CODE>
+ <DD>Password write protect.
+ <DT><CODE>x</CODE>
+ <DD>Password protect
+ <DT><CODE>u</CODE>
+ <DD>Temporarily unprotect the disk until it is ejected.  The disk becomes
+ writable, and reverts back to its old state when ejected.
+ <DT><CODE>q</CODE>
+ <DD>Queries the status
+ </DL>
+ <P>
+ 
+ To remove the password, set it to one of the passwordless modes
+ <CODE>-r</CODE> or <CODE>-w</CODE>: mzip will then ask you for the password, and
+ unlock the disk.  If you have forgotten the password, you can get rid of
+ it by low-level formatting the disk (using your SCSI adaptor's BIOS
+ setup).
+ </P><P>
+ 
+ The ZipTools disk shipped with the drive is also password protected.  On
+ Dos or on a Mac, this password is automatically removed once the
+ ZipTools have been installed.  From various articles posted to Usenet, I
+ learned that the password for the tools disk is
+ <CODE>APlaceForYourStuff</CODE><A NAME="DOCF1" HREF="mtools.html#FOOT1">(1)</A>.  Mzip knows about this
+ password, and tries it first, before prompting you for a password.  Thus
+ <CODE>mzip -w z:</CODE> unlocks the tools disk<A NAME="DOCF2" HREF="mtools.html#FOOT2">(2)</A>.  The tools disk is
+ formatted in a special way so as to be usable both in a PC and in a Mac.
+ On a PC, the Mac filesystem appears as a hidden file named
+ <TT>`partishn.mac'</TT>.  You may erase it to reclaim the 50 Megs of space
+ taken up by the Mac filesystem.
+ </P><P>
+ 
+ <HR SIZE="6">
+ <A NAME="SEC72"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC71"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC73"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC73"></A>
+ <H3> 4.26.1 Bugs </H3>
+ <!--docid::SEC73::-->
+ <P>
+ 
+ This command is a big kludge.  A proper implementation would take a
+ rework of significant parts of mtools, but unfortunately I don't have
+ the time for this right now. The main downside of this implementation is
+ that it is inefficient on some architectures (several successive calls
+ to mtools, which defeats mtools' caching).
+ </P><P>
+ 
+ <A NAME="Compiling mtools"></A>
+ <HR SIZE="6">
+ <A NAME="SEC73"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC72"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC74"></A>
+ <H1> 5. Architecture specific compilation flags </H1>
+ <!--docid::SEC74::-->
+ <P>
+ 
+ To compile mtools, first invoke <CODE>./configure</CODE> before
+ <CODE>make</CODE>. In addition to the standard <CODE>autoconfigure</CODE> flags,
+ there are two architecture specific flags available.
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>./configure --enable-xdf</CODE>
+ <DD><DT><CODE>./configure --disable-xdf</CODE>
+ <DD>Enables support for XDF disks. This is on by default. See section <A HREF="mtools.html#SEC15">2.7.4 XDF</A>,
+ for details.
+ <DT><CODE>./configure --enable-vold</CODE>
+ <DD><DT><CODE>./configure --disable-vold</CODE>
+ <DD>Enables support for vold on Solaris. When used in conjunction with vold,
+ mtools should use different device nodes than for direct access.
+ <P>
+ 
+ <DT><CODE>./configure --enable-new-vold</CODE>
+ <DD><DT><CODE>./configure --disable-new-vold</CODE>
+ <DD>Enables new support for vold on Solaris. This is supposed to work more
+ smoothly than the old support.
+ <P>
+ 
+ <DT><CODE>./configure --enable-floppyd</CODE>
+ <DD><DT><CODE>./configure --disable-floppyd</CODE>
+ <DD>Enables support for floppyd.  By default, floppyd support is enabled as
+ long as the necessary X includes and libraries are available.
+ </DL>
+ <P>
+ 
+ <A NAME="Porting mtools"></A>
+ <HR SIZE="6">
+ <A NAME="SEC74"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC73"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC75"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC38"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC75"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC75"></A>
+ <H1> 6. Porting mtools to architectures which are not supported yet </H1>
+ <!--docid::SEC75::-->
+ <P>
+ 
+  This chapter is only interesting for those who want to port mtools to
+ an architecture which is not yet supported. For most common systems,
+ default drives are already defined. If you want to add default drives
+ for a still unsupported system, run config.guess, to see which
+ identification autoconf uses for that system. This identification is
+ of the form cpu-vendor-os (for example sparc-sun-sunos). The cpu and
+ the os parts are passed to the compiler as preprocessor flags.
+  The OS part is passed to the compiler in three forms.
+ <OL>
+ <LI>
+ The complete os name, with dots replaced by underscores.  sco3.2v2 would
+ yield sco3_2v2
+ <LI>
+ The base os name. Sco3.2v2 would yield Sco
+ <LI>
+ The base os name plus its major version. Sco3.2v2 would yield Sco3
+ </OL>
+ <P>
+ 
+  All three versions are passed, if they are different.
+ </P><P>
+ 
+  To define the devices, use the entries for the systems that are already
+ present as templates. In general, they have the following form:
+ </P><P>
+ 
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>#if (defined (my_cpu) &#38;&#38; defined(my_os))
+ #define predefined_devices
+ struct device devices[] = {
+         { "/dev/first_drive", 'drive_letter', drive_description},
+         <small>...</small> 
+         { "/dev/last_drive", 'drive_letter', drive_description}
+ }
+ #define INIT_NOOP
+ #endif
+ </pre></td></tr></table></P><P>
+ 
+  "/dev/first_drive" is the name of the device or image file
+ representing the drive. Drive_letter is a letter ranging from a to z
+ giving access to the drive. Drive_description describes the type of the
+ drive:
+ <DL COMPACT>
+ <DT><CODE>ED312</CODE>
+ <DD>extra density (2.88M) 3 1/2 disk
+ <DT><CODE>HD312</CODE>
+ <DD>high density 3 1/2 disk
+ <DT><CODE>DD312</CODE>
+ <DD>double density 3 1/2 disk
+ <DT><CODE>HD514</CODE>
+ <DD>high density 5 1/4 disk
+ <DT><CODE>DD514</CODE>
+ <DD>double density 5 1/4 disk
+ <DT><CODE>DDsmall</CODE>
+ <DD>8 sector double density 5 1/4 disk
+ <DT><CODE>SS514</CODE>
+ <DD>single sided double density 5 1/4 disk
+ <DT><CODE>SSsmall</CODE>
+ <DD>single sided 8 sector double density 5 1/4 disk
+ <DT><CODE>GENFD</CODE>
+ <DD>generic floppy drive (12 bit FAT)
+ <DT><CODE>GENHD</CODE>
+ <DD>generic hard disk (16 bit FAT)
+ <DT><CODE>GEN</CODE>
+ <DD>generic device (all parameters match)
+ <DT><CODE>ZIPJAZ(flags)</CODE>
+ <DD>generic ZIP drive using normal access. This uses partition 4.
+ <CODE>Flags</CODE> are any special flags to be passed to open.
+ <DT><CODE>RZIPJAZ(flags)</CODE>
+ <DD>generic ZIP drive using raw SCSI access. This uses partition 4.
+ <CODE>Flags</CODE> are any special flags to be passed to open.
+ <DT><CODE>REMOTE</CODE>
+ <DD>the remote drive used for floppyd.  Unlike the other items, this macro
+ also includes the file name ($DISPLAY) and the drive letter (X)
+ </DL>
+ <P>
+ 
+  Entries may be described in more detail:
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre> fat_bits,open_flags,cylinders,heads,sectors,DEF_ARG
+ </pre></td></tr></table> or, if you need to describe an offset (filesystem doesn't start at
+ beginning of filesystem)
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre> fat_bits, open_flags, cylinders, heads, sectors, offset, DEF_ARG0
+ </pre></td></tr></table></P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>fat_bits</CODE>
+ <DD>is either 12, 16 or 0. 0 means that the device accepts both types of
+ FAT.
+ <DT><CODE>open_flags</CODE>
+ <DD>may include flags such as O_NDELAY, or O_RDONLY, which might be
+ necessary to open the device. 0 means no special flags are needed.
+ <DT><CODE>cylinders,heads,sectors</CODE>
+ <DD>describe the geometry of the disk. If cylinders is 0, the heads and sectors
+ parameters are ignored, and the drive accepts any geometry.
+ <DT><CODE>offset</CODE>
+ <DD>is used if the DOS filesystem doesn't begin at the start of the device
+ or image file. This is mostly useful for Atari Ram disks (which contain
+ their device driver at the beginning of the file) or for DOS emulator
+ images (which may represent a partitioned device.
+ </DL>
+ <P>
+ 
+  Definition of defaults in the devices file should only be done if these
+ same devices are found on a large number of hosts of this type. In that
+ case, could you also let me know about your new definitions, so that I
+ can include them into the next release.  For purely local file, I
+ recommend that you use the <CODE>/usr/local/etc/mtools.conf</CODE> and
+ <CODE>~/.mtoolsrc</CODE> configuration files.
+ </P><P>
+ 
+  However, the devices files also allows to supply geometry setting
+ routines. These are necessary if you want to access high capacity
+ disks.
+ </P><P>
+ 
+  Two routines should be supplied:
+ </P><P>
+ 
+ <OL>
+ <LI>
+ Reading the current parameters
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>static inline int get_parameters(int fd, struct generic_floppy_struct *floppy)
+ </pre></td></tr></table><P>
+ 
+  This probes the current configured geometry, and return it in
+ the structure generic_floppy_struct (which must also be declared).
+  Fd is an open file descriptor for the device, and buf is an already
+ filled in stat structure, which may be useful.
+  This routine should return 1 if the probing fails, and 0 otherwise.
+ </P><P>
+ 
+ <LI>
+ Setting new parameters
+ <TABLE><tr><td>&nbsp;</td><td class=example><pre>static inline int set_parameters(int fd, struct generic_floppy_struct *floppy)
+                                  struct stat *buf)
+ </pre></td></tr></table> This configures the geometry contained in floppy on the file descriptor
+ fd. Buf is the result of a stat call (already filled in).  This should
+ return 1 if the new geometry cannot be configured, and 0 otherwise.
+ </OL>
+ <P>
+ 
+  A certain number of preprocessor macros should also be supplied:
+ </P><P>
+ 
+ <DL COMPACT>
+ <DT><CODE>TRACKS(floppy)</CODE>
+ <DD>refers to the track field in the floppy structure
+ <DT><CODE>HEADS(floppy)</CODE>
+ <DD>refers to the heads field in the floppy structure
+ <DT><CODE>SECTORS(floppy)</CODE>
+ <DD>refers to the sectors per track field in the floppy structure
+ <DT><CODE>SECTORS_PER_DISK(floppy)</CODE>
+ <DD>refers to the sectors per disk field in the floppy structure (if
+ applicable, otherwise leave undefined)
+ <P>
+ 
+ <DT><CODE>BLOCK_MAJOR</CODE>
+ <DD>major number of the floppy device, when viewed as a block device
+ <P>
+ 
+ <DT><CODE>CHAR_MAJOR</CODE>
+ <DD>major number of the floppy device, when viewed as a character device
+ (a.k.a. "raw" device, used for fsck) (leave this undefined, if your OS
+ doesn't have raw devices)
+ </DL>
+ <P>
+ 
+  For the truly high capacity formats (XDF, 2m, etc), there is no clean
+ and documented interface yet.
+ </P><P>
+ 
+ <A NAME="Command Index"></A>
+ <HR SIZE="6">
+ <A NAME="SEC75"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC74"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC76"></A>
+ <H1> Command Index </H1>
+ <!--docid::SEC76::-->
+ <table><tr><th valign=top>Jump to: &nbsp; </th><td><A HREF="mtools.html#pg_F" style="text-decoration:none"><b>F</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#pg_M" style="text-decoration:none"><b>M</b></A>
+  &nbsp; 
+ </td></tr></table><br><P></P>
+ <TABLE border=0>
+ <TR><TD></TD><TH ALIGN=LEFT>Index Entry</TH><TH ALIGN=LEFT> Section</TH></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="pg_F"></A>F</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC39"><CODE>floppyd</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC39">4.1 Floppyd</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC44"><CODE>floppyd_installtest</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC44">4.2 Floppyd_installtest</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="pg_M"></A>M</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC45"><CODE>mattrib</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC45">4.3 Mattrib</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX51"><CODE>mbadblocks</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC46">4.4 Mbadblocks</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX55"><CODE>mcat</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC48">4.5 Mcat</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC49"><CODE>mcd</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC49">4.6 Mcd</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC7"><CODE>mcd (introduction)</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC7">2.3 Current working directory</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC50"><CODE>mclasserase</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC50">4.7 Mclasserase</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC51"><CODE>mcopy</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC51">4.8 Mcopy</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC53"><CODE>mdel</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC53">4.9 Mdel</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC54"><CODE>mdeltree</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC54">4.10 Mdeltree</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC55"><CODE>mdir</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC55">4.11 Mdir</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC56"><CODE>mdu</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC56">4.12 Mdu</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC57"><CODE>mformat</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC57">4.13 Mformat</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC26"><CODE>mformat (geometry used for)</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC26">3.5.2 Disk Geometry Configuration</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC61"><CODE>minfo</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC61">4.15 Minfo</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC58"><CODE>mkmanifest</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC58">4.14 Mkmanifest</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC62"><CODE>mlabel</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC62">4.16 Mlabel</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC63"><CODE>mmd</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC63">4.17 Mmd</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC64"><CODE>mmount</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC64">4.18 Mmount</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC65"><CODE>mmove</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC65">4.19 Mmove</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC66"><CODE>mpartition</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC66">4.20 Mpartition</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC67"><CODE>mrd</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC67">4.21 Mrd</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC68"><CODE>mren</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC68">4.22 Mren</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC69"><CODE>mshowfat</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC69">4.23 Mshowfat</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC70"><CODE>mtoolstest</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC70">4.24 Mtoolstest</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC72"><CODE>mzip</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC72">4.26 Mzip</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ </TABLE><P></P><table><tr><th valign=top>Jump to: &nbsp; </th><td><A HREF="mtools.html#pg_F" style="text-decoration:none"><b>F</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#pg_M" style="text-decoration:none"><b>M</b></A>
+  &nbsp; 
+ </td></tr></table><br><P>
+ 
+ <A NAME="Variable Index"></A>
+ <HR SIZE="6">
+ <A NAME="SEC76"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC75"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC77"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC75"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC77"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC77"></A>
+ <H1> Variable index </H1>
+ <!--docid::SEC77::-->
+ <table><tr><th valign=top>Jump to: &nbsp; </th><td><A HREF="mtools.html#vr_C" style="text-decoration:none"><b>C</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#vr_D" style="text-decoration:none"><b>D</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#vr_E" style="text-decoration:none"><b>E</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#vr_F" style="text-decoration:none"><b>F</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#vr_H" style="text-decoration:none"><b>H</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#vr_M" style="text-decoration:none"><b>M</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#vr_N" style="text-decoration:none"><b>N</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#vr_S" style="text-decoration:none"><b>S</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#vr_T" style="text-decoration:none"><b>T</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#vr_U" style="text-decoration:none"><b>U</b></A>
+  &nbsp; 
+ </td></tr></table><br><P></P>
+ <TABLE border=0>
+ <TR><TD></TD><TH ALIGN=LEFT>Index Entry</TH><TH ALIGN=LEFT> Section</TH></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="vr_C"></A>C</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX4"><CODE>cylinders</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC26">3.5.2 Disk Geometry Configuration</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="vr_D"></A>D</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC25"><CODE>drive</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC25">3.5.1 General information</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="vr_E"></A>E</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC27"><CODE>exclusive</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC27">3.5.3 Open Flags</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="vr_F"></A>F</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX23"><CODE>fat_bits</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX11"><CODE>file</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX48"><CODE>filter</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX50"><CODE>fucase</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC34">3.8.3 Configuration using explicit translation tables</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="vr_H"></A>H</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX6"><CODE>heads</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC26">3.5.2 Disk Geometry Configuration</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="vr_M"></A>M</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX47"><CODE>mformat_only</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC23"><CODE>MTOOLS_FAT_COMPATIBILITY</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC23">3.4 Global variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC23"><CODE>MTOOLS_LOWER_CASE</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC23">3.4 Global variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC23"><CODE>MTOOLS_NO_VFAT</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC23">3.4 Global variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC23"><CODE>MTOOLS_SKIP_CHECK</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC23">3.4 Global variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC19"><CODE>MTOOLSRC</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC19">3.1 Description</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="vr_N"></A>N</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC27"><CODE>nodelay</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC27">3.5.3 Open Flags</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="vr_S"></A>S</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX7"><CODE>sectors</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC26">3.5.2 Disk Geometry Configuration</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC27"><CODE>sync</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC27">3.5.3 Open Flags</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="vr_T"></A>T</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX49"><CODE>tounix</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC34">3.8.3 Configuration using explicit translation tables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX5"><CODE>tracks</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC26">3.5.2 Disk Geometry Configuration</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="vr_U"></A>U</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX46"><CODE>use_xdf</CODE></A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ </TABLE><P></P><table><tr><th valign=top>Jump to: &nbsp; </th><td><A HREF="mtools.html#vr_C" style="text-decoration:none"><b>C</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#vr_D" style="text-decoration:none"><b>D</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#vr_E" style="text-decoration:none"><b>E</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#vr_F" style="text-decoration:none"><b>F</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#vr_H" style="text-decoration:none"><b>H</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#vr_M" style="text-decoration:none"><b>M</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#vr_N" style="text-decoration:none"><b>N</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#vr_S" style="text-decoration:none"><b>S</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#vr_T" style="text-decoration:none"><b>T</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#vr_U" style="text-decoration:none"><b>U</b></A>
+  &nbsp; 
+ </td></tr></table><br><P>
+ 
+ <A NAME="Concept Index"></A>
+ <HR SIZE="6">
+ <A NAME="SEC77"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC78"> &gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC78"> &gt;&gt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <A NAME="SEC78"></A>
+ <H1> Concept index </H1>
+ <!--docid::SEC78::-->
+ <table><tr><th valign=top>Jump to: &nbsp; </th><td><A HREF="mtools.html#cp_2" style="text-decoration:none"><b>2</b></A>
+  &nbsp; 
+ <BR>
+ <A HREF="mtools.html#cp_A" style="text-decoration:none"><b>A</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_B" style="text-decoration:none"><b>B</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_C" style="text-decoration:none"><b>C</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_D" style="text-decoration:none"><b>D</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_E" style="text-decoration:none"><b>E</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_F" style="text-decoration:none"><b>F</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_G" style="text-decoration:none"><b>G</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_H" style="text-decoration:none"><b>H</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_I" style="text-decoration:none"><b>I</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_J" style="text-decoration:none"><b>J</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_L" style="text-decoration:none"><b>L</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_M" style="text-decoration:none"><b>M</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_N" style="text-decoration:none"><b>N</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_O" style="text-decoration:none"><b>O</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_P" style="text-decoration:none"><b>P</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_R" style="text-decoration:none"><b>R</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_S" style="text-decoration:none"><b>S</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_T" style="text-decoration:none"><b>T</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_V" style="text-decoration:none"><b>V</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_W" style="text-decoration:none"><b>W</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_X" style="text-decoration:none"><b>X</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_Z" style="text-decoration:none"><b>Z</b></A>
+  &nbsp; 
+ </td></tr></table><br><P></P>
+ <TABLE border=0>
+ <TR><TD></TD><TH ALIGN=LEFT>Index Entry</TH><TH ALIGN=LEFT> Section</TH></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_2"></A>2</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC14">2m</A></TD><TD valign=top><A HREF="mtools.html#SEC14">2.7.3 2m</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_A"></A>A</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC31">Accented characters</A></TD><TD valign=top><A HREF="mtools.html#SEC31">3.8 Character set translation tables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC3">ALPHA patches</A></TD><TD valign=top><A HREF="mtools.html#SEC3">1. Where to get mtools</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC72">APlaceForYourStuff</A></TD><TD valign=top><A HREF="mtools.html#SEC72">4.26 Mzip</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC45">Archive bit</A></TD><TD valign=top><A HREF="mtools.html#SEC45">4.3 Mattrib</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX43">Atari</A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX22">Atari Ram disk</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_B"></A>B</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC37">Backwards compatibility</A></TD><TD valign=top><A HREF="mtools.html#SEC37">3.10 Backwards compatibility with old configuration file syntax</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX53">Bad blocks</A></TD><TD valign=top><A HREF="mtools.html#SEC46">4.4 Mbadblocks</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC13">bigger sectors</A></TD><TD valign=top><A HREF="mtools.html#SEC13">2.7.2 Bigger sectors</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX28">blocksize</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC3">bugs</A></TD><TD valign=top><A HREF="mtools.html#SEC3">1. Where to get mtools</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_C"></A>C</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC10">Case sensitivity</A></TD><TD valign=top><A HREF="mtools.html#SEC10">2.6 Case sensitivity of the VFAT filesystem</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC45">Changing file attributes</A></TD><TD valign=top><A HREF="mtools.html#SEC45">4.3 Mattrib</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX27">character devices</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC70">Checking configuration file</A></TD><TD valign=top><A HREF="mtools.html#SEC70">4.24 Mtoolstest</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC69">Clusters of a file</A></TD><TD valign=top><A HREF="mtools.html#SEC69">4.23 Mshowfat</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC38">Command list</A></TD><TD valign=top><A HREF="mtools.html#SEC38">4. Command list</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC74">Compile time configuration</A></TD><TD valign=top><A HREF="mtools.html#SEC74">5. Architecture specific compilation flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC75">Compiled-in defaults</A></TD><TD valign=top><A HREF="mtools.html#SEC75">6. Porting mtools to architectures which are not supported yet</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC51">Concatenating MS-DOS files</A></TD><TD valign=top><A HREF="mtools.html#SEC51">4.8 Mcopy</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC22">Configuration file</A></TD><TD valign=top><A HREF="mtools.html#SEC22">3.3 Default values</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX1">Configuration file name</A></TD><TD valign=top><A HREF="mtools.html#SEC20">3.2 Location of the configuration files</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC36">Configuration file name (parsing order)</A></TD><TD valign=top><A HREF="mtools.html#SEC36">3.9 Location of configuration files and parsing order</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC36">Configuration file parsing order</A></TD><TD valign=top><A HREF="mtools.html#SEC36">3.9 Location of configuration files and parsing order</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC21">Configuration file syntax</A></TD><TD valign=top><A HREF="mtools.html#SEC21">3.2.1 General configuration file syntax</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC37">Configuration file, old syntax</A></TD><TD valign=top><A HREF="mtools.html#SEC37">3.10 Backwards compatibility with old configuration file syntax</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC19">Configuration files</A></TD><TD valign=top><A HREF="mtools.html#SEC19">3.1 Description</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC26">Configuration of disk geometry</A></TD><TD valign=top><A HREF="mtools.html#SEC26">3.5.2 Disk Geometry Configuration</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX56">Copying an entire disk image</A></TD><TD valign=top><A HREF="mtools.html#SEC48">4.5 Mcat</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC51">Copying MS-DOS files</A></TD><TD valign=top><A HREF="mtools.html#SEC51">4.8 Mcopy</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC51">CR/LF conversions</A></TD><TD valign=top><A HREF="mtools.html#SEC51">4.8 Mcopy</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC63">Creating a directory</A></TD><TD valign=top><A HREF="mtools.html#SEC63">4.17 Mmd</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC7">Current working directory</A></TD><TD valign=top><A HREF="mtools.html#SEC7">2.3 Current working directory</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC49">Current working directory (changing the)</A></TD><TD valign=top><A HREF="mtools.html#SEC49">4.6 Mcd</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_D"></A>D</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC22">Default configuration</A></TD><TD valign=top><A HREF="mtools.html#SEC22">3.3 Default values</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC7">Default directory</A></TD><TD valign=top><A HREF="mtools.html#SEC7">2.3 Current working directory</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC49">Default directory (changing the)</A></TD><TD valign=top><A HREF="mtools.html#SEC49">4.6 Mcd</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC22">Default values</A></TD><TD valign=top><A HREF="mtools.html#SEC22">3.3 Default values</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC67">Deleting a directory</A></TD><TD valign=top><A HREF="mtools.html#SEC67">4.21 Mrd</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC54">deleting an MS-DOS directory recursively</A></TD><TD valign=top><A HREF="mtools.html#SEC54">4.10 Mdeltree</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC53">deleting MS-DOS files</A></TD><TD valign=top><A HREF="mtools.html#SEC53">4.9 Mdel</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC26">Description of disk geometry</A></TD><TD valign=top><A HREF="mtools.html#SEC26">3.5.2 Disk Geometry Configuration</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC3">diffs</A></TD><TD valign=top><A HREF="mtools.html#SEC3">1. Where to get mtools</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC7">Directory</A></TD><TD valign=top><A HREF="mtools.html#SEC7">2.3 Current working directory</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC49">Directory (changing)</A></TD><TD valign=top><A HREF="mtools.html#SEC49">4.6 Mcd</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC63">Directory creation</A></TD><TD valign=top><A HREF="mtools.html#SEC63">4.17 Mmd</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC55">Directory listing</A></TD><TD valign=top><A HREF="mtools.html#SEC55">4.11 Mdir</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC67">Directory removing</A></TD><TD valign=top><A HREF="mtools.html#SEC67">4.21 Mrd</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX29">disable locking</A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC26">Disk Geometry</A></TD><TD valign=top><A HREF="mtools.html#SEC26">3.5.2 Disk Geometry Configuration</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX57">Disk image</A></TD><TD valign=top><A HREF="mtools.html#SEC48">4.5 Mcat</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC62">Disk label</A></TD><TD valign=top><A HREF="mtools.html#SEC62">4.16 Mlabel</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC12">DMF disks</A></TD><TD valign=top><A HREF="mtools.html#SEC12">2.7.1 More sectors</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX12">Dosemu hard disk image</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC24">Drive configuration</A></TD><TD valign=top><A HREF="mtools.html#SEC24">3.5 Per drive flags and variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC25">Drive configuration, example</A></TD><TD valign=top><A HREF="mtools.html#SEC25">3.5.1 General information</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC24">Drive description</A></TD><TD valign=top><A HREF="mtools.html#SEC24">3.5 Per drive flags and variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC25">Drive description, example</A></TD><TD valign=top><A HREF="mtools.html#SEC25">3.5.1 General information</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC23">Drive independent configuration variables</A></TD><TD valign=top><A HREF="mtools.html#SEC23">3.4 Global variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC56">du</A></TD><TD valign=top><A HREF="mtools.html#SEC56">4.12 Mdu</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC9">Duplicate file names</A></TD><TD valign=top><A HREF="mtools.html#SEC9">2.5 Name clashes</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_E"></A>E</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC72">Ejecting a Zip/Jaz disk</A></TD><TD valign=top><A HREF="mtools.html#SEC72">4.26 Mzip</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC23">Environmental variables</A></TD><TD valign=top><A HREF="mtools.html#SEC23">3.4 Global variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC67">Erasing a directory</A></TD><TD valign=top><A HREF="mtools.html#SEC67">4.21 Mrd</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC54">erasing an MS-DOS directory recursively</A></TD><TD valign=top><A HREF="mtools.html#SEC54">4.10 Mdeltree</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC53">erasing MS-DOS files</A></TD><TD valign=top><A HREF="mtools.html#SEC53">4.9 Mdel</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC27">exclusive access to a drive</A></TD><TD valign=top><A HREF="mtools.html#SEC27">3.5.3 Open Flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX25">Executing commands before opening the device</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_F"></A>F</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC69">Fat</A></TD><TD valign=top><A HREF="mtools.html#SEC69">4.23 Mshowfat</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC12">fdformat</A></TD><TD valign=top><A HREF="mtools.html#SEC12">2.7.1 More sectors</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX10">File name of device node</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC5">Filenames</A></TD><TD valign=top><A HREF="mtools.html#SEC5">2.1 Options and filenames</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC57">Filesystem creation</A></TD><TD valign=top><A HREF="mtools.html#SEC57">4.13 Mformat</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX58">Floppyd cat</A></TD><TD valign=top><A HREF="mtools.html#SEC48">4.5 Mcat</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC26">Format of disk</A></TD><TD valign=top><A HREF="mtools.html#SEC26">3.5.2 Disk Geometry Configuration</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC11">Formats, high capacity</A></TD><TD valign=top><A HREF="mtools.html#SEC11">2.7 high capacity formats</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC57">Formatting disks</A></TD><TD valign=top><A HREF="mtools.html#SEC57">4.13 Mformat</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC23">FreeDos</A></TD><TD valign=top><A HREF="mtools.html#SEC23">3.4 Global variables</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_G"></A>G</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC61">getting parameters of a Dos fs</A></TD><TD valign=top><A HREF="mtools.html#SEC61">4.15 Minfo</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC23">Global configuration variables</A></TD><TD valign=top><A HREF="mtools.html#SEC23">3.4 Global variables</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_H"></A>H</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC28">Hdimage</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC45">Hidden files</A></TD><TD valign=top><A HREF="mtools.html#SEC45">4.3 Mattrib</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC11">High capacity formats</A></TD><TD valign=top><A HREF="mtools.html#SEC11">2.7 high capacity formats</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC64">High capacity formats, mounting</A></TD><TD valign=top><A HREF="mtools.html#SEC64">4.18 Mmount</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC26">High density disk</A></TD><TD valign=top><A HREF="mtools.html#SEC26">3.5.2 Disk Geometry Configuration</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_I"></A>I</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX8">Image file</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC57">Initializing disks</A></TD><TD valign=top><A HREF="mtools.html#SEC57">4.13 Mformat</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC31">Internationalization</A></TD><TD valign=top><A HREF="mtools.html#SEC31">3.8 Character set translation tables</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_J"></A>J</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC72">Jaz disk (utilities)</A></TD><TD valign=top><A HREF="mtools.html#SEC72">4.26 Mzip</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC66">Jaz disks (partitioning them)</A></TD><TD valign=top><A HREF="mtools.html#SEC66">4.20 Mpartition</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX14">Jaz disks (partitions)</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX36">Jaz disks (raw Scsi access)</A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_L"></A>L</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC62">Labeling a disk</A></TD><TD valign=top><A HREF="mtools.html#SEC62">4.16 Mlabel</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC11">Linux enhancements (High Capacity Formats)</A></TD><TD valign=top><A HREF="mtools.html#SEC11">2.7 high capacity formats</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC64">Linux enhancements (mmount)</A></TD><TD valign=top><A HREF="mtools.html#SEC64">4.18 Mmount</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC38">List of available commands</A></TD><TD valign=top><A HREF="mtools.html#SEC38">4. Command list</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC55">Listing a directory</A></TD><TD valign=top><A HREF="mtools.html#SEC55">4.11 Mdir</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC56">Listing space occupied by directories and files</A></TD><TD valign=top><A HREF="mtools.html#SEC56">4.12 Mdu</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX3">Location of configuration files</A></TD><TD valign=top><A HREF="mtools.html#SEC20">3.2 Location of the configuration files</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC36">Location of configuration files (parsing order)</A></TD><TD valign=top><A HREF="mtools.html#SEC36">3.9 Location of configuration files and parsing order</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX30">locking (disabling it)</A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC8">Long file name</A></TD><TD valign=top><A HREF="mtools.html#SEC8">2.4 VFAT-style long file names</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC26">Low density disk</A></TD><TD valign=top><A HREF="mtools.html#SEC26">3.5.2 Disk Geometry Configuration</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_M"></A>M</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX16">Magneto-optical disks</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC3">mailing list</A></TD><TD valign=top><A HREF="mtools.html#SEC3">1. Where to get mtools</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC63">Making a directory</A></TD><TD valign=top><A HREF="mtools.html#SEC63">4.17 Mmd</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX52">Marking blocks as bad</A></TD><TD valign=top><A HREF="mtools.html#SEC46">4.4 Mbadblocks</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC49">Mcwd file</A></TD><TD valign=top><A HREF="mtools.html#SEC49">4.6 Mcd</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC50">Memory Card</A></TD><TD valign=top><A HREF="mtools.html#SEC50">4.7 Mclasserase</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC61">mformat parameters</A></TD><TD valign=top><A HREF="mtools.html#SEC61">4.15 Minfo</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC64">Mounting a disk</A></TD><TD valign=top><A HREF="mtools.html#SEC64">4.18 Mmount</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC65">Moving files (mmove)</A></TD><TD valign=top><A HREF="mtools.html#SEC65">4.19 Mmove</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC68">Moving files (mren)</A></TD><TD valign=top><A HREF="mtools.html#SEC68">4.22 Mren</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_N"></A>N</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC9">Name clashes</A></TD><TD valign=top><A HREF="mtools.html#SEC9">2.5 Name clashes</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX2">Name of configuration files</A></TD><TD valign=top><A HREF="mtools.html#SEC20">3.2 Location of the configuration files</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC36">Name of configuration files (parsing order)</A></TD><TD valign=top><A HREF="mtools.html#SEC36">3.9 Location of configuration files and parsing order</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX9">Name of device node</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC31">National character set</A></TD><TD valign=top><A HREF="mtools.html#SEC31">3.8 Character set translation tables</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_O"></A>O</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC56">Occupation of space by directories and files</A></TD><TD valign=top><A HREF="mtools.html#SEC56">4.12 Mdu</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC11">Odd formats</A></TD><TD valign=top><A HREF="mtools.html#SEC11">2.7 high capacity formats</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC37">Old configuration file syntax</A></TD><TD valign=top><A HREF="mtools.html#SEC37">3.10 Backwards compatibility with old configuration file syntax</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC27">open flags</A></TD><TD valign=top><A HREF="mtools.html#SEC27">3.5.3 Open Flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC5">Options</A></TD><TD valign=top><A HREF="mtools.html#SEC5">2.1 Options and filenames</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX17">OS/2 (layout of removable media)</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC15">OS/2 (XDF disks)</A></TD><TD valign=top><A HREF="mtools.html#SEC15">2.7.4 XDF</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC9">Overwriting files</A></TD><TD valign=top><A HREF="mtools.html#SEC9">2.5 Name clashes</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_P"></A>P</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC58">packing list</A></TD><TD valign=top><A HREF="mtools.html#SEC58">4.14 Mkmanifest</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC36">Parsing order</A></TD><TD valign=top><A HREF="mtools.html#SEC36">3.9 Location of configuration files and parsing order</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX20">Partitioned image file</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC66">partitions (creating)</A></TD><TD valign=top><A HREF="mtools.html#SEC66">4.20 Mpartition</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC72">password protected Zip disks</A></TD><TD valign=top><A HREF="mtools.html#SEC72">4.26 Mzip</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC3">patches</A></TD><TD valign=top><A HREF="mtools.html#SEC3">1. Where to get mtools</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC50">Physically erase</A></TD><TD valign=top><A HREF="mtools.html#SEC50">4.7 Mclasserase</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX31">plain floppy: device xxx busy</A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC75">Porting</A></TD><TD valign=top><A HREF="mtools.html#SEC75">6. Porting mtools to architectures which are not supported yet</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC8">Primary file name (long names)</A></TD><TD valign=top><A HREF="mtools.html#SEC8">2.4 VFAT-style long file names</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC9">Primary file name (name clashes)</A></TD><TD valign=top><A HREF="mtools.html#SEC9">2.5 Name clashes</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_R"></A>R</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX21">Ram disk</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX26">raw device</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX54">Read errors</A></TD><TD valign=top><A HREF="mtools.html#SEC46">4.4 Mbadblocks</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC45">Read-only files (changing the attribute)</A></TD><TD valign=top><A HREF="mtools.html#SEC45">4.3 Mattrib</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC55">Read-only files (listing them)</A></TD><TD valign=top><A HREF="mtools.html#SEC55">4.11 Mdir</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC51">Reading MS-DOS files</A></TD><TD valign=top><A HREF="mtools.html#SEC51">4.8 Mcopy</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC54">recursively removing an MS-DOS directory</A></TD><TD valign=top><A HREF="mtools.html#SEC54">4.10 Mdeltree</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC39">remote floppy access</A></TD><TD valign=top><A HREF="mtools.html#SEC39">4.1 Floppyd</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC44">remote floppy access</A></TD><TD valign=top><A HREF="mtools.html#SEC44">4.2 Floppyd_installtest</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX19">Removable media</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC67">Removing a directory</A></TD><TD valign=top><A HREF="mtools.html#SEC67">4.21 Mrd</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC54">removing an MS-DOS directory recursively</A></TD><TD valign=top><A HREF="mtools.html#SEC54">4.10 Mdeltree</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC53">removing MS-DOS files</A></TD><TD valign=top><A HREF="mtools.html#SEC53">4.9 Mdel</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC65">Renaming files (mmove)</A></TD><TD valign=top><A HREF="mtools.html#SEC65">4.19 Mmove</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC68">Renaming files (mren)</A></TD><TD valign=top><A HREF="mtools.html#SEC68">4.22 Mren</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_S"></A>S</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX38">SCSI devices</A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC8">Secondary file name (long names)</A></TD><TD valign=top><A HREF="mtools.html#SEC8">2.4 VFAT-style long file names</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC9">Secondary file name (name clashes)</A></TD><TD valign=top><A HREF="mtools.html#SEC9">2.5 Name clashes</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX40">setgid installation</A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX39">setuid installation</A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX32">setuid installation (needed for raw SCSI I/O)</A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC74">Solaris (compile time configuration of vold)</A></TD><TD valign=top><A HREF="mtools.html#SEC74">5. Architecture specific compilation flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX33">Solaris (Raw access to SCSI devices such as Zip &#38; Jaz)</A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX24">Solaris (volcheck)</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX41">Solaris (vold)</A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC56">Space occupied by directories and files</A></TD><TD valign=top><A HREF="mtools.html#SEC56">4.12 Mdu</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC11">Special formats</A></TD><TD valign=top><A HREF="mtools.html#SEC11">2.7 high capacity formats</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC63">Subdirectory creation</A></TD><TD valign=top><A HREF="mtools.html#SEC63">4.17 Mmd</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC67">Subdirectory removing</A></TD><TD valign=top><A HREF="mtools.html#SEC67">4.21 Mrd</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX34">SunOS (Raw access to SCSI devices such as Zip &#38; Jaz)</A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC27">synchronous writing</A></TD><TD valign=top><A HREF="mtools.html#SEC27">3.5.3 Open Flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC21">Syntax of the configuration file</A></TD><TD valign=top><A HREF="mtools.html#SEC21">3.2.1 General configuration file syntax</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX15">Syquest disks</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX37">Syquests (raw Scsi access)</A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC45">System files</A></TD><TD valign=top><A HREF="mtools.html#SEC45">4.3 Mattrib</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_T"></A>T</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC70">Testing configuration file for correctness</A></TD><TD valign=top><A HREF="mtools.html#SEC70">4.24 Mtoolstest</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC51">Text files</A></TD><TD valign=top><A HREF="mtools.html#SEC51">4.8 Mcopy</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC72">Tools disk (Zip and Jaz drives)</A></TD><TD valign=top><A HREF="mtools.html#SEC72">4.26 Mzip</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_V"></A>V</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC70">Verifying configuration file</A></TD><TD valign=top><A HREF="mtools.html#SEC70">4.24 Mtoolstest</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC8">VFAT-style file names</A></TD><TD valign=top><A HREF="mtools.html#SEC8">2.4 VFAT-style long file names</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC12">vgacopy</A></TD><TD valign=top><A HREF="mtools.html#SEC12">2.7.1 More sectors</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC74">Vold (compile time configuration)</A></TD><TD valign=top><A HREF="mtools.html#SEC74">5. Architecture specific compilation flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX42">Vold (mediamgr)</A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_W"></A>W</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC11">Weird formats</A></TD><TD valign=top><A HREF="mtools.html#SEC11">2.7 high capacity formats</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC12">Windows 95 (DMF disks)</A></TD><TD valign=top><A HREF="mtools.html#SEC12">2.7.1 More sectors</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC8">Windows 95-style file names</A></TD><TD valign=top><A HREF="mtools.html#SEC8">2.4 VFAT-style long file names</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX18">Windows NT (layout of removable media)</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX44">Wordswapped</A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC7">Working directory</A></TD><TD valign=top><A HREF="mtools.html#SEC7">2.3 Current working directory</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC49">Working directory</A></TD><TD valign=top><A HREF="mtools.html#SEC49">4.6 Mcd</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC72">Write protecting a Zip/Jaz disk</A></TD><TD valign=top><A HREF="mtools.html#SEC72">4.26 Mzip</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC51">Writing MS-DOS files</A></TD><TD valign=top><A HREF="mtools.html#SEC51">4.8 Mcopy</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_X"></A>X</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC39">X terminal</A></TD><TD valign=top><A HREF="mtools.html#SEC39">4.1 Floppyd</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC44">X terminal</A></TD><TD valign=top><A HREF="mtools.html#SEC44">4.2 Floppyd_installtest</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC15">XDF disks</A></TD><TD valign=top><A HREF="mtools.html#SEC15">2.7.4 XDF</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC74">XDF disks (compile time configuration)</A></TD><TD valign=top><A HREF="mtools.html#SEC74">5. Architecture specific compilation flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX45">XDF disks (how to configure)</A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ <TR><TH><A NAME="cp_Z"></A>Z</TH><TD></TD><TD></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC72">Zip disk (utilities)</A></TD><TD valign=top><A HREF="mtools.html#SEC72">4.26 Mzip</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC66">Zip disks (partitioning them)</A></TD><TD valign=top><A HREF="mtools.html#SEC66">4.20 Mpartition</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX13">Zip disks (partitions)</A></TD><TD valign=top><A HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#IDX35">Zip disks (raw Scsi access)</A></TD><TD valign=top><A HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A></TD></TR>
+ <TR><TD></TD><TD valign=top><A HREF="mtools.html#SEC72">ZipTools disk</A></TD><TD valign=top><A HREF="mtools.html#SEC72">4.26 Mzip</A></TD></TR>
+ <TR><TD COLSPAN=3> <HR></TD></TR>
+ </TABLE><P></P><table><tr><th valign=top>Jump to: &nbsp; </th><td><A HREF="mtools.html#cp_2" style="text-decoration:none"><b>2</b></A>
+  &nbsp; 
+ <BR>
+ <A HREF="mtools.html#cp_A" style="text-decoration:none"><b>A</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_B" style="text-decoration:none"><b>B</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_C" style="text-decoration:none"><b>C</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_D" style="text-decoration:none"><b>D</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_E" style="text-decoration:none"><b>E</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_F" style="text-decoration:none"><b>F</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_G" style="text-decoration:none"><b>G</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_H" style="text-decoration:none"><b>H</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_I" style="text-decoration:none"><b>I</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_J" style="text-decoration:none"><b>J</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_L" style="text-decoration:none"><b>L</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_M" style="text-decoration:none"><b>M</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_N" style="text-decoration:none"><b>N</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_O" style="text-decoration:none"><b>O</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_P" style="text-decoration:none"><b>P</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_R" style="text-decoration:none"><b>R</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_S" style="text-decoration:none"><b>S</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_T" style="text-decoration:none"><b>T</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_V" style="text-decoration:none"><b>V</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_W" style="text-decoration:none"><b>W</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_X" style="text-decoration:none"><b>X</b></A>
+  &nbsp; 
+ <A HREF="mtools.html#cp_Z" style="text-decoration:none"><b>Z</b></A>
+  &nbsp; 
+ </td></tr></table><br><P>
+ 
+ <HR SIZE="6">
+ <A NAME="SEC78"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC77"> &lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[ &gt; ]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC77"> &lt;&lt; </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top"> Up </A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[ &gt;&gt; ]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT"> &nbsp; <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <HR SIZE="6">
+ <A NAME="mtools.html"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <H1>Footnotes</H1>
+ <H3><A NAME="FOOT1" HREF="mtools.html#DOCF1">(1)</A></H3>
+ <P>To see the articles, search for
+ <CODE>APlaceForYourStuff</CODE> using Dejanews
+ <H3><A NAME="FOOT2" HREF="mtools.html#DOCF2">(2)</A></H3>
+ <P>I didn't know about
+ this yet when I bought my own Zip drive.  Thus I ended up reformatting
+ my tools disk, and hence I haven't had the opportunity to test the
+ password yet.  If anybody still has their tools disk with the original
+ password, could you try it out? Thanks in advance
+ <HR SIZE=1>
+ <A NAME="SEC_Contents"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <H1>Table of Contents</H1>
+ <UL>
+ <A NAME="TOC1" HREF="mtools.html#SEC1">Introduction</A>
+ <BR>
+ <A NAME="TOC2" HREF="mtools.html#SEC2">Warning, beware of the cookie monster!</A>
+ <BR>
+ <A NAME="TOC3" HREF="mtools.html#SEC3">1. Where to get mtools</A>
+ <BR>
+ <A NAME="TOC4" HREF="mtools.html#SEC4">2. Common features of all mtools commands</A>
+ <BR>
+ <UL>
+ <A NAME="TOC5" HREF="mtools.html#SEC5">2.1 Options and filenames</A>
+ <BR>
+ <A NAME="TOC6" HREF="mtools.html#SEC6">2.2 Drive letters</A>
+ <BR>
+ <A NAME="TOC7" HREF="mtools.html#SEC7">2.3 Current working directory</A>
+ <BR>
+ <A NAME="TOC8" HREF="mtools.html#SEC8">2.4 VFAT-style long file names</A>
+ <BR>
+ <A NAME="TOC9" HREF="mtools.html#SEC9">2.5 Name clashes</A>
+ <BR>
+ <A NAME="TOC10" HREF="mtools.html#SEC10">2.6 Case sensitivity of the VFAT filesystem</A>
+ <BR>
+ <A NAME="TOC11" HREF="mtools.html#SEC11">2.7 high capacity formats</A>
+ <BR>
+ <UL>
+ <A NAME="TOC12" HREF="mtools.html#SEC12">2.7.1 More sectors</A>
+ <BR>
+ <A NAME="TOC13" HREF="mtools.html#SEC13">2.7.2 Bigger sectors</A>
+ <BR>
+ <A NAME="TOC14" HREF="mtools.html#SEC14">2.7.3 2m</A>
+ <BR>
+ <A NAME="TOC15" HREF="mtools.html#SEC15">2.7.4 XDF</A>
+ <BR>
+ </UL>
+ <A NAME="TOC16" HREF="mtools.html#SEC16">2.8 Exit codes</A>
+ <BR>
+ <A NAME="TOC17" HREF="mtools.html#SEC17">2.9 Bugs</A>
+ <BR>
+ </UL>
+ <A NAME="TOC18" HREF="mtools.html#SEC18">3. How to configure mtools for your environment</A>
+ <BR>
+ <UL>
+ <A NAME="TOC19" HREF="mtools.html#SEC19">3.1 Description</A>
+ <BR>
+ <A NAME="TOC20" HREF="mtools.html#SEC20">3.2 Location of the configuration files</A>
+ <BR>
+ <UL>
+ <A NAME="TOC21" HREF="mtools.html#SEC21">3.2.1 General configuration file syntax</A>
+ <BR>
+ </UL>
+ <A NAME="TOC22" HREF="mtools.html#SEC22">3.3 Default values</A>
+ <BR>
+ <A NAME="TOC23" HREF="mtools.html#SEC23">3.4 Global variables</A>
+ <BR>
+ <A NAME="TOC24" HREF="mtools.html#SEC24">3.5 Per drive flags and variables</A>
+ <BR>
+ <UL>
+ <A NAME="TOC25" HREF="mtools.html#SEC25">3.5.1 General information</A>
+ <BR>
+ <A NAME="TOC26" HREF="mtools.html#SEC26">3.5.2 Disk Geometry Configuration</A>
+ <BR>
+ <A NAME="TOC27" HREF="mtools.html#SEC27">3.5.3 Open Flags</A>
+ <BR>
+ </UL>
+ <A NAME="TOC28" HREF="mtools.html#SEC28">3.6 General Purpose Drive Variables</A>
+ <BR>
+ <A NAME="TOC29" HREF="mtools.html#SEC29">3.7 General Purpose Drive Flags</A>
+ <BR>
+ <UL>
+ <A NAME="TOC30" HREF="mtools.html#SEC30">3.7.1 Supplying multiple descriptions for a drive</A>
+ <BR>
+ </UL>
+ <A NAME="TOC31" HREF="mtools.html#SEC31">3.8 Character set translation tables</A>
+ <BR>
+ <UL>
+ <A NAME="TOC32" HREF="mtools.html#SEC32">3.8.1 Why character set translation tables are needed</A>
+ <BR>
+ <A NAME="TOC33" HREF="mtools.html#SEC33">3.8.2 Configuration using Country</A>
+ <BR>
+ <A NAME="TOC34" HREF="mtools.html#SEC34">3.8.3 Configuration using explicit translation tables</A>
+ <BR>
+ <A NAME="TOC35" HREF="mtools.html#SEC35">3.8.4 Unicode characters greater than 256</A>
+ <BR>
+ </UL>
+ <A NAME="TOC36" HREF="mtools.html#SEC36">3.9 Location of configuration files and parsing order</A>
+ <BR>
+ <A NAME="TOC37" HREF="mtools.html#SEC37">3.10 Backwards compatibility with old configuration file syntax</A>
+ <BR>
+ </UL>
+ <A NAME="TOC38" HREF="mtools.html#SEC38">4. Command list</A>
+ <BR>
+ <UL>
+ <A NAME="TOC39" HREF="mtools.html#SEC39">4.1 Floppyd</A>
+ <BR>
+ <UL>
+ <A NAME="TOC40" HREF="mtools.html#SEC40">4.1.1 Authentication</A>
+ <BR>
+ <A NAME="TOC41" HREF="mtools.html#SEC41">4.1.2 Command line options</A>
+ <BR>
+ <A NAME="TOC42" HREF="mtools.html#SEC42">4.1.3 Connecting to floppyd</A>
+ <BR>
+ <A NAME="TOC43" HREF="mtools.html#SEC43">4.1.4 Examples:</A>
+ <BR>
+ </UL>
+ <A NAME="TOC44" HREF="mtools.html#SEC44">4.2 Floppyd_installtest</A>
+ <BR>
+ <A NAME="TOC45" HREF="mtools.html#SEC45">4.3 Mattrib</A>
+ <BR>
+ <A NAME="TOC46" HREF="mtools.html#SEC46">4.4 Mbadblocks</A>
+ <BR>
+ <UL>
+ <A NAME="TOC47" HREF="mtools.html#SEC47">4.4.1 Bugs</A>
+ <BR>
+ </UL>
+ <A NAME="TOC48" HREF="mtools.html#SEC48">4.5 Mcat</A>
+ <BR>
+ <A NAME="TOC49" HREF="mtools.html#SEC49">4.6 Mcd</A>
+ <BR>
+ <A NAME="TOC50" HREF="mtools.html#SEC50">4.7 Mclasserase</A>
+ <BR>
+ <A NAME="TOC51" HREF="mtools.html#SEC51">4.8 Mcopy</A>
+ <BR>
+ <UL>
+ <A NAME="TOC52" HREF="mtools.html#SEC52">4.8.1 Bugs</A>
+ <BR>
+ </UL>
+ <A NAME="TOC53" HREF="mtools.html#SEC53">4.9 Mdel</A>
+ <BR>
+ <A NAME="TOC54" HREF="mtools.html#SEC54">4.10 Mdeltree</A>
+ <BR>
+ <A NAME="TOC55" HREF="mtools.html#SEC55">4.11 Mdir</A>
+ <BR>
+ <A NAME="TOC56" HREF="mtools.html#SEC56">4.12 Mdu</A>
+ <BR>
+ <A NAME="TOC57" HREF="mtools.html#SEC57">4.13 Mformat</A>
+ <BR>
+ <A NAME="TOC58" HREF="mtools.html#SEC58">4.14 Mkmanifest</A>
+ <BR>
+ <UL>
+ <A NAME="TOC59" HREF="mtools.html#SEC59">4.14.1 Example</A>
+ <BR>
+ <A NAME="TOC60" HREF="mtools.html#SEC60">4.14.2 Bugs</A>
+ <BR>
+ </UL>
+ <A NAME="TOC61" HREF="mtools.html#SEC61">4.15 Minfo</A>
+ <BR>
+ <A NAME="TOC62" HREF="mtools.html#SEC62">4.16 Mlabel</A>
+ <BR>
+ <A NAME="TOC63" HREF="mtools.html#SEC63">4.17 Mmd</A>
+ <BR>
+ <A NAME="TOC64" HREF="mtools.html#SEC64">4.18 Mmount</A>
+ <BR>
+ <A NAME="TOC65" HREF="mtools.html#SEC65">4.19 Mmove</A>
+ <BR>
+ <A NAME="TOC66" HREF="mtools.html#SEC66">4.20 Mpartition</A>
+ <BR>
+ <A NAME="TOC67" HREF="mtools.html#SEC67">4.21 Mrd</A>
+ <BR>
+ <A NAME="TOC68" HREF="mtools.html#SEC68">4.22 Mren</A>
+ <BR>
+ <A NAME="TOC69" HREF="mtools.html#SEC69">4.23 Mshowfat</A>
+ <BR>
+ <A NAME="TOC70" HREF="mtools.html#SEC70">4.24 Mtoolstest</A>
+ <BR>
+ <A NAME="TOC71" HREF="mtools.html#SEC71">4.25 Mtype</A>
+ <BR>
+ <A NAME="TOC72" HREF="mtools.html#SEC72">4.26 Mzip</A>
+ <BR>
+ <UL>
+ <A NAME="TOC73" HREF="mtools.html#SEC73">4.26.1 Bugs</A>
+ <BR>
+ </UL>
+ </UL>
+ <A NAME="TOC74" HREF="mtools.html#SEC74">5. Architecture specific compilation flags</A>
+ <BR>
+ <A NAME="TOC75" HREF="mtools.html#SEC75">6. Porting mtools to architectures which are not supported yet</A>
+ <BR>
+ <A NAME="TOC76" HREF="mtools.html#SEC76">Command Index</A>
+ <BR>
+ <A NAME="TOC77" HREF="mtools.html#SEC77">Variable index</A>
+ <BR>
+ <A NAME="TOC78" HREF="mtools.html#SEC78">Concept index</A>
+ <BR>
+ </UL>
+ <HR SIZE=1>
+ <A NAME="SEC_OVERVIEW"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <H1>Short Table of Contents</H1>
+ <BLOCKQUOTE>
+ <A NAME="TOC1" HREF="mtools.html#SEC1">Introduction</A>
+ <BR>
+ <A NAME="TOC2" HREF="mtools.html#SEC2">Warning, beware of the cookie monster!</A>
+ <BR>
+ <A NAME="TOC3" HREF="mtools.html#SEC3">1. Where to get mtools</A>
+ <BR>
+ <A NAME="TOC4" HREF="mtools.html#SEC4">2. Common features of all mtools commands</A>
+ <BR>
+ <A NAME="TOC18" HREF="mtools.html#SEC18">3. How to configure mtools for your environment</A>
+ <BR>
+ <A NAME="TOC38" HREF="mtools.html#SEC38">4. Command list</A>
+ <BR>
+ <A NAME="TOC74" HREF="mtools.html#SEC74">5. Architecture specific compilation flags</A>
+ <BR>
+ <A NAME="TOC75" HREF="mtools.html#SEC75">6. Porting mtools to architectures which are not supported yet</A>
+ <BR>
+ <A NAME="TOC76" HREF="mtools.html#SEC76">Command Index</A>
+ <BR>
+ <A NAME="TOC77" HREF="mtools.html#SEC77">Variable index</A>
+ <BR>
+ <A NAME="TOC78" HREF="mtools.html#SEC78">Concept index</A>
+ <BR>
+ 
+ </BLOCKQUOTE>
+ <HR SIZE=1>
+ <A NAME="SEC_About"></A>
+ <TABLE CELLPADDING=1 CELLSPACING=1 BORDER=0>
+ <TR><TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Top">Top</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_Contents">Contents</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC76">Index</A>]</TD>
+ <TD VALIGN="MIDDLE" ALIGN="LEFT">[<A HREF="mtools.html#SEC_About"> ? </A>]</TD>
+ </TR></TABLE>
+ <H1>About this document</H1>
+ This document was generated by <I>Alain Knaff</I> on <I>May, 31  2007</I>
+ using <A HREF="http://www.mathematik.uni-kl.de/~obachman/Texi2html
+ "><I>texi2html</I></A>
+ <P></P>  
+ The buttons in the navigation panels have the following meaning:
+ <P></P>
+ <table border = "1">
+ <TR>
+ <TH> Button </TH>
+ <TH> Name </TH>
+ <TH> Go to </TH>
+ <TH> From 1.2.3 go to</TH>
+ </TR>
+ <TR>
+ <TD ALIGN="CENTER">
+  [ &lt; ] </TD>
+ <TD ALIGN="CENTER">
+ Back
+ </TD>
+ <TD>
+ previous section in reading order
+ </TD>
+ <TD>
+ 1.2.2
+ </TD>
+ </TR>
+ <TR>
+ <TD ALIGN="CENTER">
+  [ &gt; ] </TD>
+ <TD ALIGN="CENTER">
+ Forward
+ </TD>
+ <TD>
+ next section in reading order
+ </TD>
+ <TD>
+ 1.2.4
+ </TD>
+ </TR>
+ <TR>
+ <TD ALIGN="CENTER">
+  [ &lt;&lt; ] </TD>
+ <TD ALIGN="CENTER">
+ FastBack
+ </TD>
+ <TD>
+ previous or up-and-previous section 
+ </TD>
+ <TD>
+ 1.1
+ </TD>
+ </TR>
+ <TR>
+ <TD ALIGN="CENTER">
+  [ Up ] </TD>
+ <TD ALIGN="CENTER">
+ Up
+ </TD>
+ <TD>
+ up section
+ </TD>
+ <TD>
+ 1.2
+ </TD>
+ </TR>
+ <TR>
+ <TD ALIGN="CENTER">
+  [ &gt;&gt; ] </TD>
+ <TD ALIGN="CENTER">
+ FastForward
+ </TD>
+ <TD>
+ next or up-and-next section
+ </TD>
+ <TD>
+ 1.3
+ </TD>
+ </TR>
+ <TR>
+ <TD ALIGN="CENTER">
+  [Top] </TD>
+ <TD ALIGN="CENTER">
+ Top
+ </TD>
+ <TD>
+ cover (top) of document
+ </TD>
+ <TD>
+  &nbsp; 
+ </TD>
+ </TR>
+ <TR>
+ <TD ALIGN="CENTER">
+  [Contents] </TD>
+ <TD ALIGN="CENTER">
+ Contents
+ </TD>
+ <TD>
+ table of contents
+ </TD>
+ <TD>
+  &nbsp; 
+ </TD>
+ </TR>
+ <TR>
+ <TD ALIGN="CENTER">
+  [Index] </TD>
+ <TD ALIGN="CENTER">
+ Index
+ </TD>
+ <TD>
+ concept index
+ </TD>
+ <TD>
+  &nbsp; 
+ </TD>
+ </TR>
+ <TR>
+ <TD ALIGN="CENTER">
+  [ ? ] </TD>
+ <TD ALIGN="CENTER">
+ About
+ </TD>
+ <TD>
+ this page
+ </TD>
+ <TD>
+  &nbsp; 
+ </TD>
+ </TR>
+ </TABLE>
+ <P></P>
+ where the <STRONG> Example </STRONG> assumes that the current position 
+ is at <STRONG> Subsubsection One-Two-Three </STRONG> of a document of 
+ the following structure:
+ <UL>
+ <LI> 1. Section One  </LI>
+ <UL>
+ <LI>1.1 Subsection One-One</LI>
+ <UL>
+ <LI> ... </LI>
+ </UL>
+ <LI>1.2 Subsection One-Two</LI>
+ <UL>
+ <LI>1.2.1 Subsubsection One-Two-One
+ </LI><LI>1.2.2 Subsubsection One-Two-Two
+ </LI><LI>1.2.3 Subsubsection One-Two-Three &nbsp; &nbsp; <STRONG>
+ &lt;== Current Position </STRONG>
+ </LI><LI>1.2.4 Subsubsection One-Two-Four
+ </LI></UL>
+ <LI>1.3 Subsection One-Three</LI>
+ <UL>
+ <LI> ... </LI>
+ </UL>
+ <LI>1.4 Subsection One-Four</LI>
+ </UL>
+ </UL>
+ 
+ <HR SIZE=1>
+ <BR>  
+ <FONT SIZE="-1">
+ This document was generated
+ by <I>Alain Knaff</I> on <I>May, 31  2007</I>
+ using <A HREF="http://www.mathematik.uni-kl.de/~obachman/Texi2html
+ "><I>texi2html</I></A>
+ 
+ </BODY>
+ </HTML>
