Article View: comp.sys.ibm.pc.misc
Article #1270Re: Modem Problems with Windows 3.1
From: fred j mccall 575-3539
Date: Tue, 18 Aug 1992 20:50
Date: Tue, 18 Aug 1992 20:50
46 lines
2806 bytes
2806 bytes
In <1992Aug14.151938.10653@nntp.hut.fi> tsand@vipunen.hut.fi (Tapio Sand) writes: >In article <q2aDPB1w164w@buscard.fidonet.org> sharky@buscard.fidonet.org (Gary Sciacca) writes: >>Anyone know why I would modem problems with windows and >>not in DOS. I have 2 com ports and 1 internal modem at >>com 3. The mouse is working fine as com 2 in windows >>but I'm having flacky probs with and windows application >>that uses a modem. Hangs system, with faults, download >>problems. If I use the internal modem with Procomm >>under DOS 5.0 only, everthing works fine. Do I have some >Ah, the classic question every windows user with a fast (>2400) >modem asks, sooner or later. The problem is that when a character >comes in the serial port, it signals with an IRQ that the computer >should copy the received character into memory. This has to happen >immediately because the UART (8250 or 16450) has room for one character >only. With windows running, there is so much activity going on that >the CPU can't serve the serial port fast enough. This of course >results in losing incoming charaters. This is NOT his problem. In addition, the UART on the internal modem probably isn't changeable anyway. His problem is with an IRQ collision between COM1 and the modem at COM3. >Solution: replace your serial port UART with a 16550. This has a 16 byte >buffer, so that the serial port can hold 16 characters before starting >to lose data. This has solved all my friend's problems similar to yours. This doesn't do anything for you unless you are running a 9600 baud or faster modem and a multitasking OS. >How to find out what UART you have? There must be several programs >that can report this. The one I know of is Port Finder v2.7 >You can get it via FTP from SIMTEL20 from msdos' sysutl directory >named pf270.zip. >European users: nic.funet.fi /pub/msdos/utilities/sysutl/pf270.zip If he has Windows 3.1, he can just use MSD.EXE, which comes with it. However, this is irrelevent to his problem. -- "Insisting on perfect safety is for people who don't have the balls to live in the real world." -- Mary Shafer, NASA Ames Dryden ------------------------------------------------------------------------------ Fred.McCall@dseg.ti.com - I don't speak for others and they don't speak for me.
Technical Details
Message-ID:
<1992Aug18.205041.23284@mksol.dseg.ti.com>Path:
arc1-ca.pugleaf.net!sparky!uunet!pmafire!news.dell.com!swrinde!cs.utexas.edu!csc.ti.com!tilde.csc.ti.com!mksol!mccallReferences:
<q2aDPB1w164w@buscard.fidonet.org> <1992Aug14.151938.10653@nntp.hut.fi>Show Full Headers
Complete Article Headers
Path: arc1-ca.pugleaf.net!sparky!uunet!pmafire!news.dell.com!swrinde!cs.utexas.edu!csc.ti.com!tilde.csc.ti.com!mksol!mccall From: mccall@mksol.dseg.ti.com (fred j mccall 575-3539) Newsgroups: comp.sys.ibm.pc.misc Subject: Re: Modem Problems with Windows 3.1 Message-ID: <1992Aug18.205041.23284@mksol.dseg.ti.com> Date: 18 Aug 92 20:50:41 GMT References: <q2aDPB1w164w@buscard.fidonet.org> <1992Aug14.151938.10653@nntp.hut.fi> Organization: Texas Instruments Inc Lines: 46