Man page 1 : mzip

mzip - change protection mode and eject disk on Zip/Jaz drive
     .tr (is' .tr (if` .tr (pd"

This manpage has been automatically generated from mtools's texinfo documentation, and may not be entirely accurate or complete. See the end of this man page for details.

The \fR\f(CWmzip\fR command is used to issue ZIP disk specific commands on Linux, Solaris or HPUX. Its syntax is:

\fR\f(CWmzip\fR [\fR\f(CW-epqrwx\fR]

\fR\f(CWMzip\fR allows the following command line options:

• \fR\f(CWe\fR 
      Ejects the disk.
• \fR\f(CWf\fR 
      Force eject even if the disk is mounted (must be given in addition to \fR\f(CW-e\fR).
• \fR\f(CWr\fR 
      Write protect the disk.
• \fR\f(CWw\fR 
      Remove write protection.
• \fR\f(CWp\fR 
      Password write protect.
• \fR\f(CWx\fR 
      Password protect
• \fR\f(CWu\fR 
      Temporarily unprotect the disk until it is ejected. The disk becomes writable, and reverts back to its old state when ejected.
• \fR\f(CWq\fR 
      Queries the status

To remove the password, set it to one of the passwordless modes \fR\f(CW-r\fR or \fR\f(CW-w\fR: 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).

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 \fR\f(CWAPlaceForYourStuff\fR\fR. Mzip knows about this password, and tries it first, before prompting you for a password. Thus \fR\f(CWmzip -w z:\fR unlocks the tools disk. 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 \fR\f(CW(ifpartishn.mac(is\fR. You may erase it to reclaim the 50 Megs of space taken up by the Mac filesystem.

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).

Mtools' texinfo doc

This manpage has been automatically generated from mtools's texinfo documentation. However, this process is only approximative, and some items, such as crossreferences, footnotes and indices are lost in this translation process. Indeed, these items have no appropriate representation in the manpage format. Moreover, not all information has been translated into the manpage version. Thus I strongly advise you to use the original texinfo doc. See the end of this manpage for instructions how to view the texinfo doc.

• *   
      To generate a printable copy from the texinfo doc, run the following commands:

   ./configure; make dvi; dvips mtools.dvi

\fR

• *   
      To generate a html copy, run:

   ./configure; make html

\fRA premade html can be found at \fR\f(CW(ifhttp://www.gnu.org/software/mtools/manual/mtools.html(is\fR

• *   
      To generate an info copy (browsable using emacs' info mode), run:

   ./configure; make info

\fR

The texinfo doc looks most pretty when printed or as html. Indeed, in the info version certain examples are difficult to read due to the quoting conventions used in info.