home *** CD-ROM | disk | FTP | other *** search
- Path: sparky!uunet!dtix!darwin.sura.net!news.duc.auburn.edu!ducvax.auburn.edu!hank
- From: hank@ducvax.auburn.edu
- Newsgroups: comp.os.os2.misc
- Subject: Re: Zoom Modem & COM3 blues
- Message-ID: <1992Jul21.065705.1@ducvax.auburn.edu>
- Date: 21 Jul 92 11:57:05 GMT
- References: <1992Jul21.051202.12570@pslu1.psl.wisc.edu>
- Sender: usenet@news.duc.auburn.edu (News Account)
- Organization: Auburn University, AL
- Lines: 31
- Nntp-Posting-Host: ducvax
-
- In article <1992Jul21.051202.12570@pslu1.psl.wisc.edu>, frigo@psl.wisc.edu (Sean P. Frigo UW-SRC (608)873-6651) writes:
- > I cannot get my Zoom v.32 internal modem to work as COM3. I specified
- >
- > E:\OS2\COM.SYS (3,3E8,5)
- > E:\OS2\MDOS\VCOM.SYS (3,3E8,5)
- >
- > in the CONFIG.SYS file. The card manual says the address range for COM3
- > is 3E8-3EF.
- >
- > (1) Do I need to specify COM4 as well?
- > (2) Has anyone successfully used an internal modem on an AT clone
- > designating it as COM3?
-
- Get the FAQ from T.Sipples (look for posts from Sipples--the address of the
- FAQ is in his sig).
-
- If your machine reports that com3 did not install, others (including me) have
- been able to use com3 by "touching" the port, then do a warm-boot
- (Ctrl-Alt-Del). I used com16450.sys as the com driver (this is a driver
- intended to provide com3 support to OS2 1.x). This driver works fine (at least
- for OS2 sessions--never tried it for DOS boxes). After I use this driver,
- I can replace the config.sys lines (and use the ones you've given above).
- Everything works until the next power off-on.
-
- Others have reported that the port can be "touched" from a dos box with
- something like procomm.
-
- One other thing. Make sure that you do not have any other cards using the
- IRQ you've listed for com3.
-
- --darrel hankerson hank@ducvax.auburn.edu
-