Newsgroups: comp.os.minix
Subject: Re: macwrite, macread problem in macMinix
References: <3746678E.C391B06C@hitel.net>
Organization: Rochester Institute of Technology, Rochester, NY
From: aje9383@osfmail.isc.rit.edu (Andrew Erickson)
NNTP-Posting-Host: grace.isc.rit.edu
X-Original-NNTP-Posting-Host: grace.isc.rit.edu
Message-ID: <375be0f9.0@isc-newsserver.isc.rit.edu>
Date: 7 Jun 1999 11:10:49 -0500
X-Trace: 7 Jun 1999 11:10:49 -0500, grace.isc.rit.edu
Lines: 47
XPident: aje9383
X-Original-NNTP-Posting-Host: 129.21.3.100
XPident: Unknown
Path: star.cs.vu.nl!newsfeed.amsterdam.nl.net!sun4nl!remarQ-easT!supernews.com!remarQ.com!europa.netcrusader.net!209.130.129.214!nntp.frontiernet.net!biko.cc.rochester.edu!hydra.cs.rochester.edu!news.csug.rochester.edu!news.cs.rit.edu!isc-newsserver.isc.rit.edu!aje9383
Xref: star.cs.vu.nl comp.os.minix:35775

In article <3746678E.C391B06C@hitel.net>, chang  <lhooq@hitel.net> wrote:
>Hi.
>I wanted to transfer a file to macOS, so I tried
>
>macwrite -a aFileInRamDisk
>
>but it generated a file with same name and the size of zero.  I also
>tried
>
>macread -a aFileFromMacMinixFolder
>
>in vain..
>
>What's the exact usage of macread and macwrite?

macwrite takes input from standard input and writes it to the macos file of
the given name, in the default folder (e.g. the minix folder) if a path is
not specified.  The -a option translates LF's to CR's and should be used
only for text files.

macread does just the opposite--it reads from the specified MacOS file and
spits the result out to standard output.

macread and macwrite are actually links to macfile, which automatically sets
the -r or -w flag according to the invocated name.  As distributed,
unfortuneately, they are links to an old and buggy version of macfile, while
the actual macfile is the new, corrected version.  Therefore, if you haven't
already, you should remove them and recreate the links (as root or bin, of
course):

cd /usr/bin
rm -f macread macwrite
ln macfile macread
ln macfile macwrite

and chmod and chown and chgrp them as you see fit.  (The old version aborted
early when it encountered a byte of $FF, as I recall; transferring binary
files therefore often stopped prematurely.  It was difficult to determine
precisely why, since the source code is the new, correct, updated version.)

>Thanks in advance.

No Problemo,
Andrew Erickson, aje9383@grace.isc.rit.edu



