Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!sdd.hp.com!elroy.jpl.nasa.gov!decwrl!mcnc!wolves!deepthot!Jay From: Jay@deepthot.UUCP (Jay Denebeim) Newsgroups: comp.sys.amiga.datacomm Subject: Re: UUCP 1.08DR2 Message-ID: Date: 2 Feb 91 02:46:03 GMT References: <7263@crash.cts.com> <189b9b99.ARN0475@brewing.cts.com> Organization: The Software Distillery Lines: 31 In article <189b9b99.ARN0475@brewing.cts.com> doc@brewing.cts.com (Mitch Evans) writes: >In article <7263@crash.cts.com>, Bob Lindabury, SysAdmin writes: > >> Is anyone else having problems with this new version of UUCP? I had terrible >> >> UUCP: crash!pro-graphics!bobl | Pro-Graphics: 908/469-0049 >> Internet: bobl@pro-graphics.cts.com | America Online: Graphics3d >> FastInet: bobl@bobsbox.rent.com | Compuserve: RIP > > my UUCP 1.08d has the same problem. I haven't seen it connect yet! >= PATH: ...!crash!brewing!doc US MAIL: Mitchell M. Evans = Me too, however I have a theory. A friend of mine was trying to dial me up with 1.08, he wasn't able to connect to the 1.08 on my system. I noticed that the system dialed through and got to UUCICO on my end. Turned on debugging, and I noticed that UUCP initial handshake was ^P and some other jazz. I figured that it was sending it too soon. Anyway, I don't know if that was what it was, but adding "" \d to the end of the send/response sequence in the L.sys file fixed the problem for us. He's dialing up and getting fed with no problem now. -- |_o_o|\\ |. o.| || The Jay Denebeim | . | || Software | o | || Distillery | |// Address: mcnc!wolves!deepthot!jay ====== BBS:(919)-460-7430 VOICE:(919)-460-6934