home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!usc!rpi!uwm.edu!ogicse!das-news.harvard.edu!husc-news.harvard.edu!husc10!gershon
- From: gershon@husc10.harvard.edu (Ethan Gershon)
- Newsgroups: comp.os.os2.misc
- Subject: Re: problems with modem/com port
- Message-ID: <gershon.715750122@husc10>
- Date: 6 Sep 92 03:28:42 GMT
- Article-I.D.: husc10.gershon.715750122
- References: <92249.213943JXL103@psuvm.psu.edu>
- Lines: 33
- Nntp-Posting-Host: husc10.harvard.edu
-
- JXL103@psuvm.psu.edu writes:
-
- >...still somewhat new to OS/2....I currently have an Intel Satixfaxtion Modem
- >/400, Pmcomm 1.10....I have my modem set to Com 3, (3e8, irq 5), and I can't
- >get the pmcomm to work...I'm running the beta comm drivers (from COMMGA.zip).
- >On my Boot manager setup, my modem works fine in DOS.....any suggestions?
-
- I had similar problems getting my com3, 3E8, irq5 to work. Someone sent
- me the following solution, which worked perfectly. (note that I have
- no idea *why* this works or what it does.)
-
- >CD to the OS2 subdirectory.
- >COPY COM.SYS to COM.OLD
- >PATCH COM.SYS
- >Select offset 7F2, where you should see 74 4A.
- >Replace the two bytes with 90 90 (NOP's).
- >Save the revised COM.SYS
- >Reboot.
-
- >I don't remember where I got this tip, but it works.
-
- >Avoid the revised COM drivers. They are unreliable.
-
- >Another thing you can do is use a DOS application to talk to COM3 and
- >then reboot. That seems to initialize the UART so that on subsequent
- >reboots the port will be recognized.
-
- >--
- >Jon R. Bryan (505) 844-2015 <=> bryan@isrc.sandia.gov
- >Sandia National Laboratories, Intelligent System Sensors and Controls
-
- --Ethan Gershon
- gershon@husc.harvard.edu
-