fb> TS} The symptom is this: when I connect with another
fb>   } modem, or sometimes even before - when I just
fb>   } poll the modem's registers - the display slows
fb>   } down to a crawl (o n e   c h a r a c t e r    a
fb>   } t   a   t i m e) and displays garbage.
fb> Which version of {COMMO} were you using?  If it was 6.42d,
fb> how did
fb> you have "esp" set?  If it was 6.42b or 6.42c, then try "d"
fb> or "e"
fb> and make sure "esp=no".
That *seems* to have fixed it, using beta 6.42d (beta 6.42e) wasn't on 
ordata.com, as of five minutes ago, or at least wasn't located where I could 
get to it.
Thanks for the heads up, Fred.
(Now I just have to swap all the modems back to the machines they were 
originally in, before I decided the problem was hardware related. .)
Again, for purposes of documenting things, the two machines where I had the 
problem were 386sx-20's, running dos 5.0.  Here's the config.sys and 
autoexec.bat.  If you need me to, I'll try to figure out where the conflict 
is, although I strongly suspect the print redirection:
DEVICE=C:\DOS\SETVER.EXE
DEVICE=C:\WINDOWS\HIMEM.SYS
DOS=HIGH
FILES=30
STACKS=9,256
files=60
(Don't ask me...it's not my machine.)
ECHO OFF
@ECHO OFF
SET GMK5=C:\GMK
PATH C:\DOS;c:\util;C:\WP51\;C:\LEMENU;C:\GMK
mode lpt1:=com1:
mode com1:9600,n,8,1,p
SET TEMP=C:\DOS
PROMPT $P$G
C:
CD \LEMENU
LE MENU
--- GEcho 1.11+
---------------