home *** CD-ROM | disk | FTP | other *** search
- Newsgroups: comp.os.os2.misc
- Path: sparky!uunet!gatech!asuvax!ncar!mimbres.cs.unm.edu!intvax!bryan
- From: bryan@isrc.sandia.gov (Jon R Bryan)
- Subject: Re: COM3 and Selective Install???
- Message-ID: <1993Jan21.162335.15642@isrc.sandia.gov>
- Organization: Sandia National Labs, Org. 1600, Albq., NM
- References: <1993Jan20.132404.3878@midway.uchicago.edu>
- Date: Thu, 21 Jan 1993 16:23:35 GMT
- Lines: 26
-
- pynq@quads.uchicago.edu (Jeremy Mathers) writes:
- :
- : BTW, I had trouble with my third serial port (which the card thinks is
- : COM4, but OS/2 calls COM3) when the IRQ was set to 2 (which OS/2 thinks
- : is 9).
-
- It is comforting to hear that I'm not the only one who has trouble with
- IRQ2(9). In my case, OS/2 applications which access the port work just
- fine, but DOS applications work only once. For instance, after I boot
- up I can run ProComm+ and access COM3 on IRQ2 with no problem _the first
- time_. If I shut it down and restart I can no longer receive anything
- on that port, but transmitting still works. Obviously a problem with
- the interrupt. If I set up COM4 to use IRQ2 the problem follows the
- interrupt. The only was to get the port working again for DOS
- applications is to reboot. Since my OS/2 applications never have any
- trouble, I _assume_ that the problem is in the VCOM device.
-
- Please refrain from observations on OS/2's inability to share IRQ's,
- folks. I don't have any conflicts in this case. I've informed IBM OS/2
- support, but haven't heard anything back from them.
-
-
- --
- Jon R. Bryan (505) 844-2015 <=> bryan@isrc.sandia.gov
- Sandia National Laboratories, Intelligent System Sensors and Controls
-
-