Very Computer

Why can't I use uugetty with a null-modem (RTS/CTS & 115200 at the
terminal). My cable has all 7 lines connected.

My configuration:

---- /etc/rc.d/rc.serial
setserial -abv /dev/cua0 uart 16550A port 0x3f8 irq 4 baud_base 115200
spd_vhi

---- /etc/defaults/uugetty.ttyS0
INITLINE=cua0
TIMEOUT=60
INIT="" ATZ\r OK\r\n
WAITFOR=RING
CONNECT="" ATA\r CONNECT\s\A
DELAY=1

---- /etc/inittab
s0:45:respawn:/sbin/uugetty ttyS0 F38400 vt100

The above won't work. I'll get the following message every 5 mintues:
INIT: ID "s0" respawning too fast: disabled for 5 minutes

But the following will work just fine.
s0:45:respawn:/sbin/agetty 38400 ttyS0 vt100

I would like to try it out thru null-modem first, before I hook in the
modem. And I find it very strange... I'm using getty_ps-2.0.7h the rest
is from the Slackware 3.0 ELF distribution.

Joakim ?gren

I get the desired effect--a login prompt on the terminal--if I issue the
following command as root:

        /sbin/agetty -L ttyS0 38400 vt100 & .

Make sure your terminal is expecting a 38400bps transmission rate.

Ted Sternberg
San Jose, California, USA

I suppose the problem is that you are awaiting 'OK' and 'RING' responses
from your modem - but they do not arrive. aren't you able to use simply
'agetty' ?

hope this helps ? - hg

: Why can't I use uugetty with a null-modem (RTS/CTS & 115200 at the
: terminal). My cable has all 7 lines connected.

: My configuration:

: ---- /etc/rc.d/rc.serial
: setserial -abv /dev/cua0 uart 16550A port 0x3f8 irq 4 baud_base 115200
: spd_vhi

You have a terminal capable to 115200?

: ---- /etc/defaults/uugetty.ttyS0
: INITLINE=cua0
: TIMEOUT=60
: INIT="" ATZ\r OK\r\n
: WAITFOR=RING
: CONNECT="" ATA\r CONNECT\s\A
: DELAY=1

This wouldn't work unless your terminal can respond to that 'ATZ\r' with
'OK'. And when the terminal has something to say to your computer, it must
transmit 'RING' first. Also 'ATA\r' must be handled correctly.

: ---- /etc/inittab
: s0:45:respawn:/sbin/uugetty ttyS0 F38400 vt100

: The above won't work. I'll get the following message every 5 mintues:
: INIT: ID "s0" respawning too fast: disabled for 5 minutes

: But the following will work just fine.
: s0:45:respawn:/sbin/agetty 38400 ttyS0 vt100

Even better would be:
s0:45:respawn:/sbin/agetty -h -L 38400 ttyS0 vt100
if you really have a nullmodem -cable. If you put your modem to ttyS0, leave
out that -L and have a '-t60' instead.

: I would like to try it out thru null-modem first, before I hook in the
: modem. And I find it very strange... I'm using getty_ps-2.0.7h the rest
: is from the Slackware 3.0 ELF distribution.

: Joakim ?gren

Good luck.
--
                        Kalevi J Hautaniemi
----------------------------------------------------------------------------
Marjatankatu 12       |tel: +358-31-364-7446          |fax: +358-31-364-2476

FINLAND               |http://www.sci.fi/~khmi/       |On air:  OH3FG, KO4BC
----------------------------------------------------------------------------

: Why can't I use uugetty with a null-modem (RTS/CTS & 115200 at the
: terminal). My cable has all 7 lines connected.

: My configuration:

: ---- /etc/rc.d/rc.serial
: setserial -abv /dev/cua0 uart 16550A port 0x3f8 irq 4 baud_base 115200
: spd_vhi

: ---- /etc/defaults/uugetty.ttyS0
: INITLINE=cua0
: TIMEOUT=60
: INIT="" ATZ\r OK\r\n
: WAITFOR=RING
: CONNECT="" ATA\r CONNECT\s\A
: DELAY=1

: ---- /etc/inittab
: s0:45:respawn:/sbin/uugetty ttyS0 F38400 vt100

: The above won't work. I'll get the following message every 5 mintues:
: INIT: ID "s0" respawning too fast: disabled for 5 minutes

: But the following will work just fine.
: s0:45:respawn:/sbin/agetty 38400 ttyS0 vt100

: I would like to try it out thru null-modem first, before I hook in the
: modem. And I find it very strange... I'm using getty_ps-2.0.7h the rest
: is from the Slackware 3.0 ELF distribution.

If all you want to do is run a modem forget about all this and use the
modem. I had similar troubles with null-modem cable and uugetty. I tried
agetty and everything worked fine so I left it at that....I needed to
use the null-modem cable for an application though.

--Paul T.

--
.
: