TIP: Click on subject to list as thread! ANSI
echo: commo
to: FRED BRUCKER
from: CARL MORRIS
date: 1996-01-04 21:52:00
subject: Re: COMMO

FB> Tips from users on running {COMMO} in Windows 3.1x:
Tips for running any communications program in Windows 95: (after doing you 
suggestions)
Add a COMxBuffer=y line in the 386Enh section of system.ini, for each COM 
ort
X use a buffer setting Y of 1024 or more.  On my slow 4meg system, I have to 
use 10240 or more, and this applies for all DOS communications applications.
In the Device Manager, make sure all 16550 ports have the Fifo settings at 3 
notche and 4 notches respectively.  Windows 3.11 and 95 virtualize the com 
port and use those FIFO settings instead of the one COMMO loads into the Fifo 
Control Register.  Make sure the baud rate in the properties tab is higher or 
the same as what you use, as some people say if its set at 9600, windows will 
limit COMMO from setting the port speed any higher.
I have found this on my system to be true. The first DOS box opened after 
Windows 95 boots, will not do any good in communications.  A 16550 port will 
hardly notice, but a 16450 will not even work.  After booting, I suggest that 
if you have problems with the first window, close it and open another one 
and try again...
These tips were callected from the Windows 95 echo.  I wrote a FOSSIL 5 
erial
Communications driver and have tested these tips to help 1000%!
Carl
--- Renegade v10-05 Exp
---------------
* Origin: Hooper Connections -Home of SuperDir- 402-654-2102 (1:285/302)

SOURCE: echomail via exec-pc

Email questions or comments to sysop@ipingthereforeiam.com
All parts of this website painstakingly hand-crafted in the U.S.A.!
IPTIA BBS/MUD/Terminal/Game Server List, © 2025 IPTIA Consulting™.