Xref: utzoo comp.sources.wanted:10402 comp.unix.xenix:9793
Path: utzoo!utgpu!jarvis.csri.toronto.edu!cs.utexas.edu!uwm.edu!uakari.primate.wisc.edu!uflorida!mephisto!mcnc!rti!sas!sastdr
From: sastdr@sas.UUCP (Thomas David Rivers)
Newsgroups: comp.sources.wanted,comp.unix.xenix
Subject: Old versions of XENIX 286 and uucp probs?
Message-ID: <1516@sas.UUCP>
Date: 1 Feb 90 15:09:16 GMT
References: <ADNAN.90Jan29160624@sgtech.UUCP>
Reply-To: sastdr@sas.UUCP (Thomas David Rivers)
Distribution: comp
Organization: SAS Institute Inc, Cary NC
Lines: 32


I have an older version of SCO XENIX V for the '286 (version 2.2.0
I think, but I know it's before 2.2.1, I can't remember now and I'm
at work) which I bought second hand from my previous boss.

I have been acquiring uucp connections and have begun to notice
some problems...

	   With HDB Sys V machines, and some BSD machines; after transfering
	   the first file, the XENIX machine gets hung in state 10; 
	   will the other machines send headers until they finally time
	   out.  This leaves an odd situation of a successful transfer
	   of the control file, without the data.  On the next call,
	   uucico will find the C.<machine>nnnn file, but won't find
	   the control file (since it was previously transferred) leaving
	   a message in the LOGFILE like "CAN'T READ DATA".  However,
	   it will successfully transfer one file, timing out again on
	   the next, etc...

So, I have two questions...

	1) Is this a known problem (any ideas?)

	     and

	2) Does SCO have a trade-in/trade-up policy.  The warranty
	   card was not sent in on the package, so I still have that.


	  Thanx in advance,

	- Dave Rivers -