-=> Quoting Eugen Woiwod to Richard Town <=-
 RT> Win3.1/3.11 and WfWG 3.11 will not adequately support 115k2
 RT> First two are rated at 57k6.
 EW> This is not quite true Richard. Im using a Zoom V.34I+ 33.6 with
 EW> WFWG at 115k2 with Trumpet Winsock for the Internet, and I sometimes
 EW> run Terminate under WFWG with no problem's either using 115k2
Thanx for the update.  Still havn't had the tech notes on WfWG3.11
but have upped the port, sys.ini and win.ini settings to 115200 now
and also havn't had a comoverrun either
 EW> Anyway's, here's the setting's for my Com2 port in SYSTEM.INI that I
 EW> use. 
 EW> COMBoostTime=20
 EW> Com2AutoAssign=0
 EW> COM2FIFO=1
 EW> COM2Buffer=1024
Yup.
 EW> COM2RxTRIGGER=8
Still using the ComnTXSIZE=8
                ComnRXSIZE=8
from Win3.11's system.ini.  When WfWG's install program ran, it
did not change these to a TRIGGER command, but I see this in
Win'95 system.ini posts tho
 EW> One would definetly get com overrun's using the plain old
 EW> Window's 3.1 comm driver, or even a replacement one for Windows 3.1
 EW> but with WFWG, the above setting's from system.ini and win.ini,
 EW> I have never gotten any com overrun error's in Winsock.
Believe that Winsock interacts directly with a .dll  Mostly for
Fidonet programs, they operate in a DOS box and therefor interact
directly with the .vxd   Exception being FIPS, the Win'95 mailer
(which doesn't work in Win32s BTW)
rgdZ
Richard
--- FMail/386 1.02
---------------