Xref: utzoo comp.unix.xenix:7512 comp.unix.i386:388
Path: utzoo!utgpu!jarvis.csri.toronto.edu!mailrus!shadooby!oxtrap!teemc!ka3ovk!ki4pv!cdin-1!icdi10!fr
From: fr@icdi10.UUCP (Fred Rump from home)
Newsgroups: comp.unix.xenix,comp.unix.i386
Subject: Re: Xenix vs. Unix?
Message-ID: <413@icdi10.UUCP>
Date: 7 Sep 89 14:02:00 GMT
References: <12@dynasys.UUCP> <14@nstar.UUCP> <1989Sep3.222437.25599@ddsw1.MCS.COM> <34@nstar.UUCP> <26@fleet.UUCP> <8293@spool.cs.wisc.edu> <315@bilver.UUCP>
Reply-To: fr@icdi10.UUCP (Fred Rump from home)
Organization: normally @ Compudata Inc. Phila PA
Lines: 26

In article <315@bilver.UUCP> bill@bilver.UUCP (Bill Vermillion) writes:
>In article <8293@spool.cs.wisc.edu> thurm@shorty.cs.wisc.edu (Matthew Thurmaier) writes:
->
->I have had success with the Maynard units.  They install right, first time
->every time.  And run right.  The only thing I have found is that sometimes it
->didn't like to take the tar command the first time.  So I just made a scripts
->that issued "mtape reset" as the first line, sleep a few seconds, and then
->generate the tar command.  Users fire it off by logging in as "tape".
->Perhaps you could explain to me/the-net what their problems are.  I am using
->them under 2.2.3 on '286 machines, and 2.2.3 on IBM 80's.

How can they run "right" when you have to issue work-arounds to make the work 
at all?

Another netter just reported how he has to issue two tar commands to get his 
tape to work. He complained about how this is somehow SCO's fault. The net 
responded by reporting all is well with SCO's tape drivers, but faulting Irwin 
and Maynard for being flaky. You only confirmed that.

fr

-- 
This is my house.   My castle will get started right after I finish with news. 
26 Warren St.             uucp:          ...{bpa dsinc uunet}!cdin-1!icdi10!fr
Beverly, NJ 08010       domain:  fred@cdin-1.uu.net or icdi10!fr@cdin-1.uu.net
609-386-6846          "Freude... Alle Menschen werden Brueder..."  -  Schiller