[comp.sys.amiga] UUCP 1.06D uucico

bobl@pro-graphics.cts.com (System Administrator) (09/19/90)

Anyone having trouble with uucico in UUCP 1.06d?  I can't seem to get my side
to send anything out when trying to uucico -ssystem.  My L.sys is just as in
the docs and I've even tried sending something without even waiting for and
expect string.  I've heard there is an updated uucico.  Can someone please
UUENCODE it and mail to my internet address below?  Thanks.

Any other insights would be helpful.  I am using a Hayes Ultra 96 V.32/V.42bis
modem with AmigaUUCP 1.06d out of the standard unit0 serial port.  It dials
and connects without mishap and then sits there doing nothing.  After about 30
seconds it hangs-up and resets the modem and prints an entry in
UUCP:spool/LOGFILE of "Failed call to crash" or some such thing.  uucico could
use a little more descriptive logfile entry in my opinion.  Just to let you
know, I don't see anything in my cli when uucico connects.  Shouldn't I see
what is coming back to me from the modem or at least a connect message?

I get a good connection and carrier detect and I see the other UUCP system
sending the login screen but my system just seems to be sitting there doing
nothing. (I can see this on the CD light and the RD lights on the modem).

Any help would be appreciated.

-- Bob
______ Pro-Graphics BBS  `It's better than a sharp stick in the eye!' ________

    UUCP: crash!pro-graphics!bobl         |         Pro-Graphics: 908/469-0049
ARPA/DDN: pro-graphics!bobl@nosc.mil      |       America Online: Graphics3d
Internet: bobl@pro-graphics.cts.com       |           CompuServe: RIP
_________                                                          ___________
          Raven Enterprises  25 Raven Avenue  Piscataway, NJ 08854 

jax@well.sf.ca.us (Jack J. Woehr) (09/22/90)

bobl@pro-graphics.cts.com (System Administrator) writes:

>Anyone having trouble with uucico in UUCP 1.06d?  I can't seem to get my side
>to send anything out when trying to uucico -ssystem.  My L.sys is just as in
>the docs

	Yeah, that L.sys is tricky, you really have to anticipate
EXACTLY what is going to happen at login. Dick around with \c and \d
some, experiment.

	Also, check your spelling. I spent a week trying to connect
to du!nyx with an L.sys that spelled it "nxy" :-)

 <jax@well.{UUCP,sf.ca.us} ><  Member, >        /// ///\\\    \\\  ///
 <well!jax@lll-winken.arpa >< X3J14 TC >       /// ///  \\\    \\\/// 
 <JAX on GEnie             >< for ANS  > \\\  /// ///====\\\   ///\\\ 
 <SYSOP RCFB (303) 278-0364><  Forth   >  \\\/// ///      \\\ ///  \\\