IPC802/uugetty problem on 6386 V3.2

[John Canning]

In article <14900 at bfmny0.UU.NET> tneff at bfmny0.UU.NET (Tom Neff) writes:
>
>... Almost everything works great, except that if I dial up
>and log in and eventually hang up, then the NEXT time I dial in, the
>modem will CONNECT but uugetty won't issue a login: prompt.  This
>remains true no matter how many additional times I log in, or what I do
>on the line after CONNECT -- hit returns, breaks, keys etc.  The only
>thing that repairs it is when UUCICO runs hourly and does its thing!
>Afterwards, I can usually log in again -- once.
>

The problem seems to be in the code to uugetty.  It fails to reset
CLOCAL or some other flag, so that it is not able to see your
incoming call.

The trick is when the modem answers, have someone run an stty on
the port (in your case ttyh01).  This is all it takes to wake up
the uugetty.  Calling out on the modem will also reset the uugetty,
which is why things work when uucp does its hourly thing.

This may sound crazy, but it works.  The problem is that you have
to have someone at your computer to initiate the stty.

Maybe a simpler work around for you would be to make uucp call out
every 10 minutes, rather than once an hour.  You could also get an
internal modem, or an external modem which emulates the AT&T command
set instead of the Hayes command set.

The upsetting thing about all this is that the IPC-802 manual says
that Hayes modems are supported, and that the 3.0 drivers handle
all supported modems properly.  The Hotline tells us that the Hayes
modems are no longer supported, and that it is a bug in the Hayes
modems, and not AT&T's software, that causes things to lock up...

John Canning					...uunet!uvm-gen!banzai!john
The People's Computer Company			...attmail!banzai!john
Williston, Vermont				john at banzai.pcc.com
802-864-0747