From: jeff@wisdom.bubble.org (Jeff Ross)
Newsgroups: comp.unix.sys5.r4,comp.dcom.modems
Subject: uucp woes
Summary: uucp failures
Keywords: uucp esix worldblazer sas
Date: 1 Jan 93 19:11:28 GMT
Organization: Wisdom's Pony Express


here is the saga, running (or trying to run) Esix SVR4 (4.0.4) however I am
plaiged by problems with uucico and/or SAS-1.25.  To make matters worse
there is a telebit worldblazer (LA7.01 roms problems where present with
5.01 as well)

when I call out from the Esix machine and download files from a remote
host the transfer will fail, no if ands or buts about it, all I get 
are alarms, the alarms will come at random times durring the transfer,
but always within the first 40k or so.

after borrowing an hp datascope from work, I monitored the line between
the modem and computer sent it to telebit for evaluation, their
assesment was that the worldblazer was functioning properly and that the
unix machine was not, more specifically, the unix machine was
"supposedly" dropping a packet and requesting a retransmission which the
worldblazer "supposedly" retransmitted correctly.  according to telebit
they even examined the packets that the telebit was sending to the
unix machine to verify the checksum was correct. (it was) thus they
concluded that the worldblazer is fine, but the unix machine is at
fault.

let me go into a little more detail, the baud rate is locked and 38.4k,
serial ports have 16550's and sas proclaims that fifo is enabled.  I
have tried dropping the bps rate to 19.2k (in the feeling that the unix
machine can't handle it although the drive has been moved from the
normal '386sx to a '486DX and the same failure occures).  more fuel, I
replaced the WB with a T2500, everything works perfectly!  (or at least
after running 1.5+ meg through the port.)  I have run this unix machine
plugged directly into the serial port of a SCO unix machine (svr3.2v2)
and transfered files in excess of 7meg at a clip @ 38.4k with no
problems.

I have installed the patch concerning the fubyte problem, that didn't
make a difference,  I went to using SAS over the stock async drivers
because I was unable to get the modem to work bi-directionally without
it, maybe somebody knows how to get esix drivers working properly?  Esix
didn't, (last time I spoke to them was when Jeff Ellis was still there)
then again the parallel port didn't work either until they sent me a
supposely "public domain" program called "spp" that solved the printing
problem.

does anybody have a worldblazer working properly on an esix SVR4 (4.0.4)
system?  the WB is set up properly (been in use on a SCO unix machine
ever since TB swapped out my T3000 for it) and the parameters where
verified by TB to be correct.

I am suspect of the WB due to the above information I have listed, but
then again the WB seems to be running fine under SCO.  go figure!

I'd be willing to send a copy of the protocol trace to anybody that's
interested but be forwared it was written on a HP 4952 (4951?) protocol
analyzer.

any help would be appreciated!!!


				Jeff





-- 

.Sig??? you want a stinkin' .Sig???
Jeff Ross
201-299-1819 (home)				jeff@wisdom.bubble.org
Xref: sparky comp.unix.sys5.r4:939 comp.unix.misc:4675