Article View: alt.linux
Article #1024CAN'T CONNECT BY SERIAL CABLE WITH WIN95
From: Toshiyuki IWATA
Date: Mon, 31 Mar 1997 00:00
Date: Mon, 31 Mar 1997 00:00
52 lines
2802 bytes
2802 bytes
I'm trying to hook my PC running Windows95 to the other PC running LINUX by a null modem cable. I have read the Serial-HOWTO, and I think I have done all I have to do. However, I have never been able to get "login: " prompt on my Win95 machine. Can anyone help me? Please advice by e-mail to me. I describe my setup as follows: CONNECTION OF TO PCs ############### by a cable connected to Win95 COM2 and LINUX COM1. I believe my cable is a null modem cable because I used to use it to connect two MS-DOS PCs by interlnk.exe and intersvr.exe to send/receive files. My Linux machine is Compaq Presario CDS924, and it used to have a DOS version of BIOS setup program that turn on/off serial ports, but when I deleted DOS and installed LINUX, I deleted that BIOS setup program partition also. Therefore I am not sure whether the COM1 is enabled or not. HOW DO I KNOW MY COM1 ON LINUX IS ENABLED?? LINUX MACHINE ############## I edited /etc/gettydefs to add: # 9600 bps Dumb Terminal entry DT9600# B9600 CS8 CLOCAL # B9600 SANE -ISTRIP CLOCAL #@S @L login: #DT9600 and, I looked at there is no /etc/default/uugetty.ttyS0 or no /etcconf.uugetty.ttyS0 Then I edited /etc/inittab to add: S0:123456:respawn:/sbin/agetty ttyS0 DT9600 vt100 and, did "init q" on my Linux. WINDOWS95 MACHINE ################ Tried Hyper Terminal that came with Windows95 with property setting: Connection: direct to Com 2, 9600bps, 8 databit, non parity, 1 stop bit, hardware flow control. VT100 emulation with ASCII character code set, local echo enabled -- Toshi IWATA iwata@mx2.nisiq.net
Technical Details
Message-ID:
<01bc3db5$0ed44ae0$LocalHost@atx>Path:
arc1-ca.pugleaf.net!unknown!not-for-mailShow Full Headers
Complete Article Headers
X-Google-Language: ENGLISH,ASCII-7-bit X-Google-Thread: 1103af,5608f2e06a126c4b,start X-Google-Attributes: gid1103af,public X-Google-Thread: 10684a,5608f2e06a126c4b,start X-Google-Attributes: gid10684a,public X-Google-Thread: 100c5f,5608f2e06a126c4b,start X-Google-Attributes: gid100c5f,public X-Google-Thread: faa64,5608f2e06a126c4b,start X-Google-Attributes: gidfaa64,public X-Google-Thread: f5910,5608f2e06a126c4b,start X-Google-Attributes: gidf5910,public X-Google-Thread: f9b51,5608f2e06a126c4b,start X-Google-Attributes: gidf9b51,public X-Google-Thread: 10669a,5608f2e06a126c4b,start X-Google-Attributes: gid10669a,public X-Google-Thread: 10a997,5608f2e06a126c4b,start X-Google-Attributes: gid10a997,public From: "Toshiyuki IWATA" <iwata@mx2.nisiq.net> Subject: CAN'T CONNECT BY SERIAL CABLE WITH WIN95 Date: 1997/03/31 Message-ID: <01bc3db5$0ed44ae0$LocalHost@atx> X-Deja-AN: 229612840 Organization: NIS Internet Service,JAPAN Newsgroups: alt.linux,alt.os.linux,alt.uu.comp.os.linux,alt.uu.comp.os.linux.questions,comp.os.linux.misc,comp.os.linux.networking,comp.os.linux.setup,fj.os.linux,japan.comp.linux,linux.act.serial