Path: utzoo!utgpu!water!watmath!clyde!att!osu-cis!tut.cis.ohio-state.edu!cwjcc!gatech!ncar!boulder!sunybcs!bingvaxu!leah!uwmcsd1!marque!uunet!mcvax!enea!kth!draken!tut!tolsun!reini
From: reini@tolsun.oulu.fi (Jukka Reinikainen)
Newsgroups: comp.unix.xenix
Subject: Re: COM3 with Xenix 2.2.3
Message-ID: <414@tolsun.oulu.fi>
Date: 18 Oct 88 14:24:23 GMT
References: <1113@lakesys.UUCP> <3700004@eecs.nwu.edu>
Reply-To: reini@tolsun.UUCP (Jukka Reinikainen)
Organization: University of Oulu, Finland
Lines: 19

In article <3700004@eecs.nwu.edu> skrenta@eecs.nwu.edu (Richard Skrenta) writes:
# I've got an older version of Xenix, but perhaps this will work on your system.
# Try running /etc/serinit.  This is a shell script that configures various
# serial devices.  On my system it puts up a menu asking what kind of device
# you'd like to add (1 port, 4 port, 8 port card) and where it should go
# (com1, com2, etc).

Does the kernel interrupt configuration support those interrupt lines
which are used by many internal modems when dip-switched to COM3 and
COM4?  If I remember right, the only interrupt lines supported for
COMs are those for COM1 and COM2 and if you want to use COM3 or COM4,
you have to reconfigure your kernel interrups somehow.  I'm not sure
about this, but if /etc/serinit (mkdev serial) doesn't help, this
may be the problem.
--
|-in real life: Jukka Reinikainen-+--------------------------------+----------|
| voice login: NOLOGIN            | uucp: ...!mcvax!tut!oulu!reini | foo-bar  |
| visual login: Hiidentie 2 C 44  | internet: reini@tolsun.oulu.fi | buffer   |
|-------------- 90550 OULU FINLAND+--------------------------------+----------|