2mgui for Linux project v0.1.0
A project by Santiago Garca Mantin (manty@geocities.com)
Facultad de Informtica, Universidad de La Corua (Spain)
based on the 2mgui technology by Ciriaco Garca de Celis (ciri@gui.uva.es)
(C) 1997 distribute freely

This is the first public release of the project, only the guitools or gtools
are available at this time, this tools have been designed to be similar to the
mtools but they can only handle 2mgui disks in read only mode, no writing
available at this time, and they do it quite slowly, two turns by track in HD
disks and 3 turns by track in DD ones, instead of the one turn by track wich
gives you 2mgui for DOS.

2mgui is a format that lets you get almost the physical capacity of a disk, it
lets you get more than two million bytes free out of a 3.5 HD disk, this is the
maximum you'll ever be able to achieve in one of this disks with the standard
technology (a NEC 765 compatible controller and a 3.5 HD drive), it is achieved
by putting only one sector per track (this is done with a 16Kb sector or 32Kb
in ED disks and resetting the controller before overwriting the beginning of the
sector). 2mgui is also the name of the driver that will let you read, write and
format this disks under DOS, both the format and the driver are designed and
developed by Ciriaco Garca de Celis and the latest version should always be
found on ftp://ftp.gui.uva.es/pub/dos/2m or http://www.gui.uva.es/~ciri

What guitools provide you with is a set of commands to read the disks in an
mtools style, this is:

  gtype      <source files>
  gdir   [-] <source files>
  gcopy  [-] <source files> [target]
  gimage     <source drive> <target file>

where...

  gtools  shows info on the other available commands
  gcopy   copies files from a 2mgui disk   (recursive if - is specified)
  gdir    does a dos style dir of the disk (recursive if - is specified)
  gimage  obtains an image of the hole disk
  gtype   types files from a 2mgui disk onto the std output

The expansion in the file names is done as follows:

  if no name has been specified or the name is '.' then '*.*' is used
  if only '.ext' has been specified then '*.ext' is used
  if only 'filename' (no extension) has been passed then it uses 'filename.*'
  '*' and '?' behave like in standard unix shells

FAT names are always converted to lowercase on copy.

I'm gonna try to put this on the major linux sites (i.e. sunsite.unc.edu), but
latest realease will always be available via ftp at ceu.fi.udc.es in directory
/pub/os/linux/misc and via http at www.geocities.com/SiliconValley/Lakes/1486

I think this is all, I hope to continue developing this project, there is still
a lot of job to be done. Any comments will be wellcome.

Santiago Garca Mantin (manty@geocities.com).
