home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!decwrl!csus.edu!netcom.com!netcomsv!spacebbs!michael.hagerty
- From: michael.hagerty@spacebbs.com (Michael Hagerty)
- Newsgroups: comp.os.os2.misc
- Subject: OS/2 considerations in mo
- Message-ID: <23885.689.uupcb@spacebbs.com>
- Date: 30 Aug 92 16:45: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: 32
-
- LH. From: hartzman@kilroy.Jpl.Nasa.Gov (Les Hartzman)
- LH. Subject: OS/2 considerations in modem selection?
-
- LH. Are there any special OS/2 considerations I should keep in mind when looking
- LH. for a modem (9600, 14.4k)?
-
- Internal or external. If internal, make certain that it has a built-in
- 16550. If external, make certain that the port you will be using has a
- 16550.
-
- Now for the tough stuff... If it is internal, what port will you be
- configuring it as? If other than COM1 or COM2, you will probably need
- to get a later set of comm drivers than those shipped with the GA. I
- am using the set labeled COM2210 or COMGA3.
-
- One critical piece of information... Unlike DOS, you cannot share an
- IRQ between two apps. This means that you must assign an UNUSED IRQ to
- COM3 or COM4 in order to use the port. Nor can you have holes in the
- comm sequence (i.e., COM1, COM2, COM4 is a no-no).
-
- Other than the above, you should be in hot fat... Now, is the comm
- program a native OS/2 product, a DOS program or (heaven forbid) a Win
- app? If it is a DOS app, and they run real fine under OS/2, remember
- to pay attention to the settings to get the full performance out of the
- modem. Take a look at the file DOSGAMES available on some BBS's for a
- few suggestions. Setting the comm program up as a game is overkill,
- but you will lose not a single bit that way.
-
- Regards, Mikey
- ---
- . JABBER v1.2 #42 . Telemate, the dessert topping/floor wax of comm pgms.
-
-