home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!elroy.jpl.nasa.gov!decwrl!csus.edu!netcom.com!netcomsv!spacebbs!michael.hagerty
- From: michael.hagerty@spacebbs.com (Michael Hagerty)
- Newsgroups: comp.os.os2.misc
- Subject: Two peculiar problems...
- Message-ID: <23009.689.uupcb@spacebbs.com>
- Date: 18 Aug 92 18:01:00 GMT
- Distribution: na
- Organization: SPACE BBS - Menlo Park, CA - 10 Lines + 4gB - 415-323-4193
- Reply-To: michael.hagerty@spacebbs.com (Michael Hagerty)
- Lines: 24
-
- NT. From: tenny@euclid.uucp (Nathan Tenny)
- NT. Subject: Two peculiar problems...
- NT.
- NT. Problem #1: COM ports.
- NT.
- NT. I have an internal modem installed on COM4; programs running under "native"
- NT. DOS do fine with it, but anything running under OS/2 (even in a DOS session)
- NT. behaves *strangely*; typically, it will find nothing on COM4 the first time
- NT. it looks, and will hang the second time. Most programs (including SofTerm)
- NT. stop responding to system requests at this point, and once in a while the wh
- NT. machine will lock up and have to be hard-booted. What the hell is going on?
- NT.
- NT. (For what it's worth; I have the modem on IRQ3, and COM2 disabled to avoid
- NT. conflicts. There's a trackball on COM1, and no other serial devices.)
-
- FWIW, in the docs is some discussion about the sequential nature of ports.
- What this means is that you are apparently not permitted to have holes in
- the sequence of comm ports. To have a COM4, you must also have COM1, COM2
- and COM3. Reorder your ports, get the COM2210 driver and you should be ok.
-
- Regards, Mikey
- ---
- . JABBER v1.2 #42 . There is no dark side of the moon. Really.
-
-