Jack Stein wrote on 25 Nov 1999 at 10:27 to Jaap Van.Veen:

 JS> Jaap Van.Veen wrote in a message to All:

 JVV> As I have recalled earlier, my system (486DX2 66) is much
 JVV> faster with FP40 installed. This has to do with the faster
 JVV> handling of the harddisk. 

 JVV> However during the regular status checks the COM1 port is
 JVV> not serviced in time causing overruns. Does somebody know
 JVV> how I can avoid overrun of COM1. 

 JVV> I am using SIO.SYS instead of COM.SYS since the beginning of
 JVV> my dealing with OS/2.

 JS> I run WARP 3 with no fixpaks (other than it is released at FP5.  I
 JS> upgraded my IBM1S506 and the DASD drivers only, and did that at the
 JS> FB17 level, and that was needed ONLY for multiple drive recognition
 JS> on a CD Changer.  Anyway, I once installed the newer drivers that
 JS> were released for large drives (>4gigs), although my stock drivers
 JS> recognized my 5 gig drive with no problem, I installed them just
 JS> for kicks.  Suddenly, I started getting modem overrun errors, on
 JS> the BBS (DOS) and on the internet (OS/2).  I tracked the problem
 JS> down to these new drivers, and I'm sure that is exactly where your
 JS> problem is coming from.  I tried 9 million things to correct the
 JS> errors, based on a bunch of recommendations in here for switches to
 JS> the IBM1S506 config.sys line, but not a damn one worked. I had to
 JS> put the older disk drivers from FP17 back in to stop the modem
 JS> errors.  I was suprised a disk driver could create modem overrun
 JS> errors, but it did, absolutly positively was the cause.

 JS> I recommend you move that driver to another name, and stick in your
 JS> old IBM1s506 driver and see if the problem doesn't disappear.  All
 JS> you need do is copy it to the correct directory and reboot.
Thanks for the info. I will try to find an old (pre FP39) IBMS506 and try to
fix the problem.
Jaap 
--- timEd/2 1.10+