*** Quoting Richard Town to Stuart Wright dated 03-15-97 ***
>  SW> SYSTEM.INI file:
>  SW> COMM.DRV=COMM.DRV
> 
> Win3.1 and Win3.11's comm.drv is inadequate
> Change to either WFXCOMM.DRV (free with supplied Delrina WinFax)
> or Cybercom
> 
> Win3.1/3.11 and WfWG 3.11 will not adequately support 115k2
> First two are rated at 57k6. (havn't seen any comms docs for
> WfWG3.11)  Still need to adjust the WIN.INI
> 
You make those statements like they are incontrovertable fact and the TRUTH 
is that they AIN'T.
Simple FACT.  Been there and DONE that with the standard COMM.DRV for BOTH!
It isn't simply communicating that is a problem but rather the multitasking 
that one tends to do in Windows cause it is supposed to be a multitasking 
environment.  THAT is what mucks things up and requires BETTER 16550 support.
IF ALL one were doing is running their comm app, there wouldn't be a problem.
Even the lowly XT can do 115200bps DTE rates.  
Really, it CAN.  Don't even DREAM of ANY sort of multitasking though. 
And that usually means do NOT use a write cache.
But suffice to say that the limitations you note as regards Windows COMM.DRV 
are really NONEXISTANT.  They can and do work at the speeds you contend they 
don't.  Even more.  The W4WG driver IS entirely adaquate to the task.  The 
replacement drivers offer more control etc, but the W4WG drivers DO WORK.
The Windows drivers work, but apparently NOT with DOS apps.  And EVEN with 
Windows apps, one is USUALLY better off to do as you suggest, BUT that is NOT 
to say that one can't get by otherwise since I and others HAVE DONE exactly 
that. 
---
---------------