Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!husc6!hao!ames!lll-lcc!mordor!sri-spam!sri-unix!ctnews!pyramid!prls!philabs!lamont!dale
From: dale@lamont.LDGO.Columbia.edu (dale chayes)
Newsgroups: comp.dcom.modems,comp.mail.uucp
Subject: Telebit TrailBlazers and UUCP
Message-ID: <222@lamont.LDGO.Columbia.edu>
Date: Tue, 17-Nov-87 17:50:12 EST
Article-I.D.: lamont.222
Posted: Tue Nov 17 17:50:12 1987
Date-Received: Sat, 21-Nov-87 03:56:45 EST
Organization: Lamont-Doherty Geological Observatory N.Y.
Lines: 30
Keywords: uucp traliblazers timeouts
Summary: HELP please
Xref: mnetor comp.dcom.modems:1202 comp.mail.uucp:971

We are using Telebit TrailBlazers with Berkley 4.3 uucp to link our
lab network with our geophysical research vessel (Robert D. Conrad.)
The TrailBlazers have version 3.0 EPROMS. We set up a reasonable
test period in the lab, and then over a local (very noisey) phone 
line and got good results (which I reported a couple of weeks ago.)

We are now running between the lab and the ship (at sea) through 
an INMARSAT satelite link and having intermittent problems.  In general,
we see "pkcget: alarm n" and eventually the link fails.  We are sucessfully
transfering files, but the data rate is highly variable, and it is
not reliable enough to let it run automagicly.

My present hypothesis is that the extra delay induced by the sat. link
is causing time outs....but I haven't been able to sleuth out what to 
change.

I have spent hours looking at the code, (and seconds reading the profuse
comments (:-)) and would really like to talk to someone who is familiar with
uucp. 

	Dale Chayes
usmail:	Lamont-Doherty Geological Observatory of Columbia University
	Route 9W 
	Palisades, N.Y.,   19064
voice:	(914) 359-2900 extension 434
fax:	(914) 359-6817 (all kinds)
usnet:	...philabs!lamont!dale
------
-- 
are we having fun yet?....