Xref: utzoo comp.windows.ms:12761 comp.sys.ibm.pc.misc:9608
Path: utzoo!utgpu!news-server.csri.toronto.edu!helios.physics.utoronto.ca!ists!yunexus!rreiner
From: rreiner@yunexus.YorkU.CA (Richard Reiner)
Newsgroups: comp.windows.ms,comp.sys.ibm.pc.misc
Subject: ms-kermit 3.10 in windows 3.0
Message-ID: <22733@yunexus.YorkU.CA>
Date: 16 May 91 15:51:34 GMT
Organization: York U. Computing Services
Lines: 11

Having grown discontented with the available Windows comm programs,
I've been setting up ms-kermit 3.10 to run under windows 3.0 in 386Enh
mode.  This works well, even in a small window, (although the PIF
distributed with ms-kermit is for Windows 2 (!), and therefore needed
revision), except that now and then Kermit decides to drive the comm
port through BIOS, resulting in terrible performance.  I know that
Kermit does this when it finds no comm hardware of the usual type in
the right place, so win3 must sometimes be hiding the comm port from
Kermit.  Does anyone have a solution?

//richard