DEC VT320

• Messages sorted by:[ date ][ thread ][ subject ][ author ]

--M9NhX3UHpAaciwkO
Content-Type: text/plain; charset=us-ascii

Try the following wiring to get mgetty to work. This is what I had to do
to get a PC working with mgetty.

-- 
William Burrow, VE9WIL
18 Quintillion keys on the wall, 18 Quintillion keys...
Your computer is wasting CPU cycles unless you are running rc5des:
http://rc5.distributed.net/

--M9NhX3UHpAaciwkO
Content-Type: message/rfc822
Content-Description: Forwarded message from "WARCC04.CANARY01" <WARCC04.CANARY01@SSW.ALCOA.COM>

Return-Path: WARCC04.CANARY01@SSW.ALCOA.COM
Received: from SSW.ALCOA.COM (mch1.ami.alcoa.com [147.154.1.10]) by fan1.fan.nb.ca (8.8.5/8.8.5/971013-15:10) with SMTP id CAA13270 for <aa126@fan1.fan.nb.ca>; Tue, 6 Jan 1998 02:21:14 -0400 (AST)
Received: by SSW.ALCOA.COM
  (Soft*Switch Central V4L40P1A) id 980220010098006FWARCC04;
  06 Jan 1998 01:20:01 EST
Message-Id: <WARCC04.CANARY01.980220010098006FWARCC04@SSW.ALCOA.COM>
Date: 06 Jan 1998 1901:20:01 EST 
From: "WARCC04.CANARY01" <WARCC04.CANARY01@SSW.ALCOA.COM>
Subject: Re[4]: NULL modem connection
To: aa126@fan1.fan.nb.ca
Comment: MEMO 01/05/98 23:28:00
Content-Type: text
X-UIDL: 88072698ec435bcdb224cde56404a708
Status: RO
X-Status: A
Content-Length: 2715
Lines: 75

William,

I see by your output stream you haven't the right configuration on your cable,
(although your very close)

 /-->DCD: pin 8 NC pin 8 :DCD <--\
 | Rxd: pin 3 to pin 2 :TxD  |
 | Txd: pin 2 to pin 3 :RxD  | Jumper
 | DTR: pin 20 to pin 6 :DSR <--/
 | GND: pin 7 to pin 7 :GND
 \-->DSR: pin 6 to pin 20 :DTR
  RTS: pin 4 to pin 5 :CTS
  CTS: pin 5 to pin 4 :RTS
  Ring: pin 9 NC pin 9 :Ring

--
robert write back soon!

______________________________ Reply Separator _________________________________
Subject: Re: Re[2]: NULL modem connection
Author: aa126@fan1.fan.nb.ca at ~AMSCCSSW
Date: 1/5/98 10:36 AM 19  


On Mon, Jan 05, 1998 at 01:23:01AM -0400, WARCC04.CANARY01 wrote:
> Try this in your initab entry:
>
> s1:2345:respawn:/usr/local/sbin/mgetty -rb -x 9 /dev/ttyS0

I found dropping the -b option got me a prompt on the Mac. Incidentally,
the Mac is an original SE, like one of the first made or something, so the
port speed is intentionally low because the hardware has problems with high
speeds.

The new problem is that after I enter my login name at the prompt, nothing
happens for awhile then the prompt returns. :\

> Are you going from DB9 to DB9 or what? Let me know and I will send you the
> *correct* null modem cable configuration.

I built the cable on DB25 connectors, and it works fine in terminal mode
(including hardware handshaking).

Here is the log now:

01/04 20:20:19 yS0 tio_set_flow_control( HARD )
01/04 20:20:19 yS0 getlogname (AUTO_PPP), read:will[0d]
01/04 20:20:23 yS0 input finished with '\r', setting ICRNL ONLCR
01/04 20:20:23 yS0 tio_get_rs232_lines: status: RTS CTS DSR DTR
01/04 20:20:23 yS0 WARNING: starting login while DCD is low!
01/04 20:20:23 yS0 login: use login config file /usr/local/etc/mgetty+sendfax

/login.config
01/04 20:20:23 yS0 match: user='will', key=''
01/04 20:20:23 yS0 match: user='will', key='/FIDO/'
01/04 20:20:23 yS0 match: user='will', key=''
01/04 20:20:23 yS0 match: user='will', key='/AutoPPP/'
01/04 20:20:23 yS0 match: user='will', key=''
01/04 20:20:23 yS0 match: user='will', key='*'*** hit!
01/04 20:20:23 yS0 calling login: cmd='/bin/login', argv[]='login will'
01/04 20:20:23 ##### data dev=ttyS0, pid=14143, caller=none, conn='DIRECT', name

='', cmd='/bin/login', user='will'

01/04 20:20:23 yS0 setenv: 'CALLER_ID=none'
01/04 20:20:23 yS0 setenv: 'CONNECT=DIRECT'
--
01/04 20:21:23 yS0 mgetty: official release 1.0.0


I notice that DCD is low, is this a problem? Should I tie the DCD line to
something?
--
William Burrow, VE9WIL <mailto:aa126@fan.nb.ca>
Experience is what you get when you were expecting something else.

--M9NhX3UHpAaciwkO--
.