Article View: comp.sys.next.misc
Article #1080Re: neuron and uucp
From: Curt Welch
Date: Thu, 09 Apr 1992 02:42
Date: Thu, 09 Apr 1992 02:42
24 lines
1712 bytes
1712 bytes
In article <1992Apr8.030454.25700@u.washington.edu> wimsey@milton.u.washington.edu (Andrew Creighton) writes: > Has *anybody* been able to get uucp running with a Neuron Fax 1414 > modem? Yes. I have the 1414 and use it to get news and mail from UUNET. About one out of every 5 calls fail to connect to the UUNET trailblazers, and it seems that about half the time uunet can't connect to my Neuron, but it's good enough to keep the data flowing. The problem with the Neuron connecting to the Trailblazer seems to be caused by the Neuron thinking it's hearing a busy signal when the Trailblazer starts making it's initial tones. The first tones that the Trailblazer puts out is for the PEP protocol. It takes a few seconds before it gives up and trys the V.32 tones. It's the PEP tones that the 1414 mistakes for a busy signal. The 1414 outputs "BUSY", and then hangs up. (Actually, I don't know if it's the 1414 that decides to hang up or something the Neuron monitor does.) -------------------------------------------------------------------------- Curt Welch - KCW Consulting By 1995, there will be just two kinds curt@kcwc.com - NeXTmail please! of professionals: Those who use NeXT (703) 938-4152 FAX (703) 938-5756 and those without Jobs. --------------------------------------------------------------------------
Technical Details
Message-ID:
<1992Apr9.024234.18215@kcwc.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!kcwc.com!curtReferences:
<1992Apr8.030454.25700@u.washington.edu>Show Full Headers
Complete Article Headers
Newsgroups: comp.sys.next.misc Path: arc1-ca.pugleaf.net!sparky!uunet!kcwc.com!curt From: curt@kcwc.com (Curt Welch) Subject: Re: neuron and uucp Message-ID: <1992Apr9.024234.18215@kcwc.com> Sender: curt@kcwc.com Organization: KCW Consulting References: <1992Apr8.030454.25700@u.washington.edu> Date: Thu, 9 Apr 1992 02:42:34 GMT