Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!swrinde!ucsd!nosc!cod!hall
From: hall@cod.NOSC.MIL (Robert R. Hall)
Newsgroups: comp.os.minix
Subject: Re: Estdio Version 2.0 - Part 1 of 8
Message-ID: <2029@cod.NOSC.MIL>
Date: 1 Aug 90 20:06:53 GMT
References: <26256@nigel.udel.EDU> <2786@bruce.cs.monash.OZ.AU>
Organization: Naval Ocean Systems Center, San Diego
Lines: 15

In article <2786@bruce.cs.monash.OZ.AU>, cechew@bruce.cs.monash.OZ.AU (Earl Chew) writes:
> In <26256@nigel.udel.EDU> RX80266%INDYLLY.BITNET@uicvm.uic.edu writes:
> 
> >I receive nonreadable characters, why?
> 
> In case you haven't already noticed, the distribution has been shar'ed,
> compressed and uuencoded.

Even so uuencode should not leave any control type characters in the
file.  Since there is no table header preamble section in your posting
I suspect that they were uuencode on a Sun instead of using the Minix
command uue.  Since the orginal poster has a BITNET address his copy
is a likely candidate to suffer character transpositions by BITNET.
Given the preamble header table, the Minix command uud can then restore
any character transpositions that may have occured in transmiting.