Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!zaphod.mps.ohio-state.edu!sol.ctr.columbia.edu!lll-winken!uunet!mcsun!hp4nl!tuegate.tue.nl!rc6.urc.tue.nl!rw9.urc.tue.nl!rcpt From: rcpt@rw9.urc.tue.nl (Piet Tutelaers) Newsgroups: comp.sys.amiga.tech Subject: Re: Writing Amiga Disks on Sun Sparc Station Message-ID: Date: 19 Nov 90 22:21:17 GMT References: <9011141815.AA01360@pokey.src.honeywell.com> <15877@cbmvax.commodore.com> <627@roo.UUCP> Sender: News Administration Reply-To: rcpt@urc.tue.nl Lines: 126 carpente@corinth.uucp (Michael A. Carpenter OSBU North) writes: >Any ideas? I can continue to do the extra hop (Sun, PC, Amiga), but >I'd prefer to do it straight. I use the sparc-mtools (ftp-ed from hydra.helsinki.fi from the directory pub/archives/comp.misc.sources/sparc-mtools) since a week and I am very happy with it in combination with the great `MessyDos' handler from Olaf Seibert. This last MSDOS filehandler permits me to do an Amiga zoo: zoo -add msh:NiceStuff What Ever You Want creating the MSDOS file NICESTUF.ZOO and read it into our Sparcstation (notice the messed up things): mcopy a:NICESTUF.ZOO NiceStuff.zoo and to unpack it using zoo on our UNIX box with: zoo x// NiceStuff and vice versa without any problem (so far). We use the latest version of zoo (is it 2.1?). I have installed all mtools in /usr/local/bin which is standard for us. I have also made an overall manual page from the README file belonging to the mtools (see at the end). Best copying around, Piet Tutelaers rcpt@urc.tue.nl -------------------mtools.1------------------------------------------ .\" t .TH MTOOLS 1 "version 1.6.2 - 5 Jul 89" Public .SH NAME Mtools \- tools for handling MSDOS floppies on SPARCstation1 .SH DESCRIPTION This is a collection of MSDOS tools to allow you to read and write to MSDOS formatted diskettes from a Unix based system. .PP The following MSDOS commands are emulated: .PP .TS lll. Mtool MSDOS name equivalent Description _ mcopy COPY copy MSDOS files to/from Unix mdel DEL/ERASE delete a MSDOS file mdir DIR display a MSDOS directory mkdfs FORMAT Format and build s DOS file system. mmd MD/MKDIR make a MSDOS sub directory mrd RD/RMDIR remove a MSDOS sub directory mread COPY low level read (copy) a MSDOS file to Unix mren REN/RENAME rename an existing MSDOS file mtype TYPE display contents of a MSDOS file mwrite COPY low level write (copy) a Unix file to MSDOS *) CD change working directory .TE *) by use of the environmental variable MCWD .PP The formats of IBM PC floppy disk drives are: .PP .TS ccccc. sectors tracks total disk introduced per per capacity size in MSDOS track side 8 40 160k 5.25 1.0 9 40 180k 5.25 1.1 8 40 320k 5.25 2.0 9 40 360k 5.25 2.0 15 80 1.2M 5.25 3.0 9 80 720k 3.5 3.1 18 80 1.4M 3.5 3.2 .TE .PP The disk geometry can be kept in the environment for unusual cases, init.c will pass "NCYL", "NSECT" and "NTRACK" to the disk parameter setting routine (if any). This should be documented in an "mtools" manual page giving an overview of the whole package, this file is a start. .PP The manuals are very terse... it's assumed that the reader is already familiar with MSDOS. .PP The use of the environmental variable MCWD to keep track of the current working directory is a little awkward, especially since there is no 'change directory' command. Bourne shell users will have to type two commands to initially set their working directory, ie: .IP .nf MCWD=/TMP export MCWD .PP Wildcards are only applied to filenames and not to directory names. For example '/usr/local/*.c' is appropriate, but '/usr/l*/main.c' is not. .PP I really wanted to avoid the use of a 'text' mode and a 'data' mode when transferring files, but I couldn't find a better way. It gets rather confusing and it's quite possible to mess up a file if you apply the text mode when it is not appropriate (ie: to a COM or EXE file). Likewise, if you forget to apply the text mode (to a Unix text file) then if the file is used under MSDOS, it will be missing carriage returns. However, if you aren't going to use the files on your Unix system (you just intend to hold the files and then transfer them back to MSDOS later) then you shouldn't use the text mode during either mread or mwrite. This is because, the text mode is only useful if the files are gonna be used under Unix. .PP The implementation of the Mcopy command is somewhat clumbsy since the MSDOS drive designation "A:" is used. Mcopy is really a front-end to the low level Mread and Mwrite commands. .PP There are is a shell archives called "Unixpc.shar" that contain files specific to the AT&T Unix PC 7300/3b1. .SH "SEE ALSO" mcopy (1), mdel (1), mdir (1), mkdfs (1), mmd (1), mrd (1), mread (1), mren (1), mtype (1), mwrite (1), .SH AUTHOR .nf Emmet P. Gray (...!uunet!uiucuxc!fthood!egray) .PP This manual page is a fast hack of the `Readme' file belonging to this package (Piet Tutelaers -- rcpt@urc.tue.nl)