root@raider.MFEE.TN.US (Bob Reineri) (04/30/89)
I seem to recall a while back that someone had posted a message on how to use
COM3 or COM4 as a terminal port under Xenix. I have need to add one more line,
and really can't afford a multiport board. If you have the information, and
would e-mail to me, I'd be most appreciative. On the other hand, it may be
of interest to many folks, so a posting would be fine too. Either way.
Thanks in advance for any information.
Bob
--
*RaiderNet Public Access, Murfreesboro, TN. - Middle Tenn's Unix GateWay*
*Phone: (615)896-8716/(615)896-7905 Mail: BOX 2371, Murfreesboro, TN 37133*
*DOMAIN: root@raider.MFEE.TN.US UUCP:!{ames,rutgers,decwrl}!killer!raider*souza@telesoft.UUCP (Steve Souza @telesoft) (05/03/89)
Bob, I posted the article below, but didn't get any response. Perhaps it will be of some use to you. If anybody has any suggestions they're holding out with (;-), I'd still appreciate the info. Thanks again, Steve ------------------------------------------------------------------- Hi Folks, We've recently developed a serial mouse driver for a Unisys PC running SCO Xenix. Since moving the driver from OS version 2.2(.3?) to 2.3, the message: serial: WARNING: interrupt vector collision has begun to appear. The mouse plugs into either COM1 or COM2, interrupting on vector levels 4 and 3, respectively. We remove the vector level associated with the mouse from the standard serial driver (sio), so the resulting configuration lines look as follows: sio 3 0577 104 sio 0 0 5 1 7 4 33 34 0 mse 1 0537 104 mse 0 0 27 1 5 3 0 0 0 I don't see a collision here. Is this OS confusion, or are we doing something weird? Both the mouse and the other serial port (connected to a terminal) work fine. Appreciate any suggestions! Steve Souza Optigraphics Corp., San Diego, CA ucsd!scubed!opti!souza (619)292-6060