Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!uunet!seismo!sundc!pitstop!sun!amdcad!ames!sri-spam!rutgers!iuvax!pur-ee!uiucdcs!bradley!ninja
From: ninja@bradley.UUCP
Newsgroups: comp.sys.att
Subject: Re: UUCP on 3B1
Message-ID: <9300026@bradley>
Date: Sun, 1-Nov-87 17:51:00 EST
Article-I.D.: bradley.9300026
Posted: Sun Nov  1 17:51:00 1987
Date-Received: Sat, 7-Nov-87 04:55:00 EST
References: <1007@csustan.UUCP>
Lines: 20
Nf-ID: #R:csustan.UUCP:1007:bradley:9300026:000:886
Nf-From: bradley.UUCP!ninja    Nov  1 16:51:00 1987


> No error was returned, however the phone was not disconnected either.

I had the same problem with mine.  Very irritating when you trust uucp
to hang up your phone.  It didn't complete the call successfully, and
I gave up in disgust.   I went to use my phone about 2 hours later and
it was off-hook; thanks AT&T.  I also noticed that in general the 3B1
loves to grab a phone line entirely (you can't pick up your phone to
listen and see if it's dialing, or if it's transfering data).  

My initial solution was to have my caller script call 'phtoggle' twice after
calling uucico.  My long-term solution was to install someone else's
uucp that has been hacked locally to run on a 3B1 over our ISN.
I installed that and it was much more friendly, including very thorough 
L.sys and L-devices examples.

Frank McGee
Microcomputer Support Specialist
Bradley University
Peoria, Il.  61625