JS> I, and someone recently in here, had problems with modum overrun
 JS> errors after installing newer IBM1S506.add drivers.  I know I
 JS> messed around a good bit trying to change paramaters in the
 JS> driver to fix it, and ended up going back to the old driver,
 JS> which works fine.  I wonder if this LAZY cache thing would fix
 JS> that?  Sounds like it might.                                     

It depends on
- your COM port.	MUST have a UART16550 (or other buffered)
			the cheap 16450 is unbufferd and my cause
			problems on transfer rates higher than 9600 cps
- your port settings    you should set the transfer rate com  modem
			to the double or higher than modem  modem
- PRIORITY_DISK_IO      must be NO to become the modem thread boosting
			over vorground threads for disk access
			(config.sys)

Then you have to play with ALL the cache parameters to find the optimum
settings for your system. The parameters depends on YOUR system usage.

The number of writers should be equal to the number of threads concurrently
writes to disk. This number is significantly lower than the number of
processes you have running! Most of your threads would never write anything
(they may read something),

If you've done all that - and the modem makes probs anyway then you have to
switch from (E)IDE to SCSII disks. Because (E)IDE is more CPU intensive than
SCSII and if the IDE drive eats CPU time the modem can't use it.

--- Sqed/32 1.15/development  352:
138/2
397/1