In a message dated 09-05-99, Steve Mccrystal said to Gene Tucker:


SM>;
SM>In a msg of , Gene Tucker writes to Kris
SM>Steenhaut: ;
SM>Gene,

 GT> Well for that part just because the connect says so doesn't mena
 GT> it is so. comm drivers do lie.

SM>As has already been pointed out, com drivers don't enter 
SM>into the protocol/speed negotiation at all.  It just isn't 
SM>possible.

 GT>  I cannot comment on these drivers in truth as I have never tried
 GT> them. I don't have Quatech hardware at all.

SM>If there is an advantage to the Quatech drivers (if I could 
SM>get them to work, I'd find out) over the stock Warp 4 
SM>drivers, then that advantage would be available even 
SM>*without* Quatech hardware.  I assume that support for 
SM>"legacy" onboard COM ports was necessary so one could use 
SM>the two now-standard motherboard com ports in addition to 
SM>one of Quatech's multi-port cards.  Thus, for some people, 
SM>there *may be* some utility.

SM>In any case,I'm not saying folks should not try/use/etc. 
SM>the Quatech drivers. All I'm saying is that it will not 
SM>perform miracles as has been suggested.

Which Steve is very rational. I realize your stand on this issue. It was just
that your post was the easiest for me to enter the discussion on. I am sorry
if
I left you with the impression that I thought that you com port drivers
readings
was all that there was to it. Heck you can't even trust the read out in the
Netscape download popup box.:) But it has been that way since the old BBS's
spanned the land. A stop watch and some math is the only w;ay to get an
accurate
picture. and then adjuat for the variations on every single comnect. For get
it
I am happy to have something run without dropoffs.:)
___
 X MR/2 2.26 #30 X Your Zip file is open.

--- Maximus/2 2.02