Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!um-math!sharkey!shadooby!accuvax.nwu.edu!tank!ncar!ames!pasteur!helios.ee.lbl.gov!nosc!cod!hall
From: hall@cod.NOSC.MIL (Robert R. Hall)
Newsgroups: comp.os.minix
Subject: Re: Reading Minix diskettes on MSDOS
Summary: Minix also can do the unwrap job
Message-ID: <1474@cod.NOSC.MIL>
Date: 6 Apr 89 14:33:34 GMT
Organization: Naval Ocean Systems Center, San Diego
Lines: 30

In article <3691@mit-amt>, pshen@atrp.media.mit.edu (Paul Shen) writes:
> In article <11680005@hpsmtc1.HP.COM> swh@hpsmtc1.HP.COM (Steve Harrold) writes:
> >Re: MIN2DOS unwrapping problem
> >
> >The MIN2DOS package I recently uploaded was "shar"ed using a Unix system,
> >and I was assuming that recipients of it would also be running on a Unix
> >system.  If this is not the case, I apologize.  Here's some more detailed
> > .......
> Acturally, 'shar' and 'uudecode' have been ported to MSDOS. In general,
> they are pd. They can be found in BBS's.
> 
I kermit the news article into Minix and did the
     sh min2dos

It produced a usuable file, the problems I had was the unpack
procedure place a blank as the leading character to the file name
which I corrected with a
     mv ?min2dos.arc min2dos.arc

Also the word and line count did not match the given numbers
but the total bytes size did so I ignored them.  After doing
doswrite to move the file to my DOS partition PKXARC accepted
the file and extracted all file without any error messages

I also tried the Minix command
    uudecode min2dos

which went faster and as far as I can tell proceduced the
same archive file and without the leading blank in the file
name.