Xref: utzoo comp.unix.xenix:7464 comp.unix.i386:335
Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!lll-winken!uunet!van-bc!sl
From: sl@van-bc.UUCP (Stuart Lynne)
Newsgroups: comp.unix.xenix,comp.unix.i386
Subject: Re: Xenix vs. Unix?
Message-ID: <262@van-bc.UUCP>
Date: 6 Sep 89 04:54:59 GMT
References: <12@dynasys.UUCP> <14@nstar.UUCP> <1989Sep3.222437.25599@ddsw1.MCS.COM> <34@nstar.UUCP> <26@fleet.UUCP> <1989Sep5.213627.13558@ddsw1.MCS.COM>
Reply-To: sl@van-bc.UUCP (Stuart Lynne)
Organization: Wimsey Associates
Lines: 34

In article <1989Sep5.213627.13558@ddsw1.MCS.COM> karl@ddsw1.MCS.COM (Karl Denninger) writes:
>In article <26@fleet.UUCP> mel@.UUCP () writes:
>>
>>SCO Xenix isn't all that great at tape drive support either.  Ever since I 
>>switched to 2.3.1 Xenix it takes TWO attempts at starting the tape drive.
>>(I'm using an Archive 150 meg/QIC02 internal on my HP Vectra 386/RS20) 
>>(I also tried an Emerald controller as well as the original Archive unit)
>
>We don't seen anything like this.  We have both 60 and 150 MB archive drives
>in the field, with both long and short controller boards.  No problems 
>reported.
>
>Karl Denninger (karl@ddsw1.MCS.COM, <well-connected>!ddsw1!karl)

I'll second Karl on this one. I've had less problems with SCO tape support
in 286 and 386 systems than in competing 386 systems.

I've used both an Archive and Everex controller just by doing mkdev tape and
using the defaults. 

It's fairly fast and seems reliable. 

If you are having problems like you describe you should probably try a
different set of hardware. I.e. does the problem disappear if you replace
the controller or drive? Does it disappear if you install the controller and
drive on a different 386 system? Different type of 386 system?

It's most likely that you have a either a bad tape system or an interaction
with it and the 386 you are using.



-- 
Stuart.Lynne@wimsey.bc.ca uunet!van-bc!sl 604-937-7532(voice) 604-939-4768(fax)