🚀 go-pugleaf

However, I would like to salvage what I can on the data end.
My problem is this.  THe modem works perfectly well when I connect
to various services in terminal emulation mode.  I even can use XMODEM
and YMODEM without difficulty, (at least when receiving files).
UUCP is another story.  After much 
hair pulling I managed to get the chat scripts right --- I can dial
into my UUCP account (at netcom) with no difficulty.  But at that
point things *always* freeze.  The link refuses to sync.  (At least
I think that's what's happening.  Here is the debug output:
>\020Shere=netcomsvgot: that
>send "lamont"
>wanted ""
>got: that
>send "Q0"
>wanted ""
>got: that
>send "x6"
>root netcom (4/7-13:21-154) SUCCEEDED (call to netcom )
>imsg looking for SYNC<\0
>Connection closed.

Is this really a Neuron problem?  Is it an obscure cable problem that
would be fixed if a bought a modem cable from NeXTConnection?  (I
have an 040 turbo color slab and told that to Neuron, though there
is no physical identification on the cable that it is for the 040.)
Or am I just screwing up my management of UUCP someplace.  

They say it can blow at any seam, but my problem is that it has blown,
and there are more seams on this puppy than on the Hindenburg, and I
am pretty upset and desparate to get my UUCP link running while on 
sabbatical and I would be every so grateful for any help, assistance,
or just plain moral encouragement.

Thanks,
Andrew Creighton
wimsey@u.washington.edu  *or*
wimsey@netcom.com

P.S.  Neuron doesn't return my phone calls, either.