home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!cs.utexas.edu!rutgers!dziuxsolim.rutgers.edu!gandalf.rutgers.edu!jclarke
- From: jclarke@gandalf.rutgers.edu (J.Christopher Clarke)
- Newsgroups: comp.os.os2.misc
- Subject: Interesting Modem Problem.
- Summary: Works under Win-OS2, not under Desktop.
- Keywords: com3,modem,config.sys
- Message-ID: <Jul.28.16.10.00.1992.22877@gandalf.rutgers.edu>
- Date: 28 Jul 92 20:10:01 GMT
- Organization: Rutgers Univ., New Brunswick, N.J.
- Lines: 22
-
-
- I have just recieved OS2 2.0 (very quickly; in 2 days) and set it up.
- I have a real problem with my modem, through. It seems that the software that
- comes with the OS doesn't connect with the modem. I have done the fix to the
- config.sys so that it accesses the com3 port where the modem is (DEVICE=...(
- 3,03E8,5)). This allowed me to access the modem using my Crosstalk for Windows
- software under Win-OS2. It connected, slowly. But still, it would not use the
- PMTerminal that came with OS2. I have called IBM, the software maker and the
- computer maker, all who blame the others. Essentially, IBM says it the hardwar
- settings, the software maker thinks the OS (but won't say it) and Gateway hasnt
- called back.
- To the chase, if there is a conflict with the interrupt, would the
- Crosstalk software, running under OS2 in a WinOS2 box, work, while that under
- the Desktop software, it does not.
-
- Perhaps it is a hardware conflict, but I hate to open it up and move jumpers,
- etc.; I know I'll zap a chip or something.
-
- Any comments are welcome.
-
- J. Christopher Clarke
- jclarke@gandalf.rutgers.edu
-