🚀 go-pugleaf

In article: <403469628wnr@mktres.demon.co.uk>  David Lindsay 
<Davlinds@mktres.demon.co.uk> writes:
> 
> In article: <536922133wnr@wilsoni.demon.co.uk>  Ian Wilson 
> <ian@wilsoni.demon.co.uk> writes:
> > 
> >[snip]
> > ftp.demon.co.uk:
> > ibmpc/win3/apps/cybercom: 8237 Jun 26  1994 cyberc.zip
> > 
> > This has a very good reputation and I have found it the best.
> > The 'interrupt trigger level' has been set to 8 for both transmit
> > and receive and cannot be adjusted.
> > 
> > ibmpc/win3/apps/comms: 7556 Aug 17  1994 wfxcom.zip
> > 
> > Advanced settings for this driver are also available. The settings
> > for both transmit and receive FIFO thresholds are adjustable via
> > SYSTEM.INI entries in the [386 Enh] section.
> > 
> >
> I would be very interested in seeing the system.ini settings we could 
> have a copy of yours
> 
I tried wfxcomm.drv for a trial period but as it never gave me any
better results than cybercom.drv I soon reverted to that and never
kept a copy of the system.ini settings.  I am fairly sure that I 
just used the recommended defaults. From wfxcomm.txt:

 To define the number of bytes loaded into the transmit FIFO on 
 each interrupt, edit:

 ComxTXSize=y

 where

 x is the COM port number
 y is a number between 1 and 16

 The default value is 8 bytes, but 16 bytes provides a reduction 
 in interrupt overhead, with no change in fax transmission 
 reliability.  If you use a transmit FIFO setting of 1, the driver 
 cannot stream at maximum throughput.

 To define the interrupt threshold for the receive FIFO, edit:

 ComxRXSize=Y

 where

 x is the COM port number
 y is one of: 1, 4, 8, or 14

 The default value is 14 bytes, which matches the setting in the   
 original Windows 3.1 commmunications driver. Setting the receive 
 threshold to a lower value increases receive reliability. A setting 
 of 8 is recommended for most systems.

-- 
Ian Wilson
Leamington Spa, Warwickshire, England