Xref: utzoo comp.windows.ms:12762 comp.sys.ibm.pc.misc:9609
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!wuarchive!usc!rpi!barryf
From: barryf@aix01.aix.rpi.edu (Barry B. Floyd)
Newsgroups: comp.windows.ms,comp.sys.ibm.pc.misc
Subject: Re: ms-kermit 3.10 in windows 3.0
Message-ID: <1--h_3g@rpi.edu>
Date: 16 May 91 16:29:47 GMT
References: <22733@yunexus.YorkU.CA>
Lines: 27
Nntp-Posting-Host: aix01srv.aix.rpi.edu

rreiner@yunexus.YorkU.CA (Richard Reiner) writes:

>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


We occasionally use Kermit 3.1 for file transfers and have encountered
the above mentioned situation when attempting to make the initial 
connection. The only "solution" if have devised entails resetting the
port:
 
   SET PORT 1

-- 
+--------------------------------------------------------------------+ 
| Barry B. Floyd                   \\\       barry_floyd@mts.rpi.edu |
| Manager Information Systems - HR    \\\          usere9w9@rpitsmts |
+-Rensselaer Polytechnic Institute--------------------troy, ny 12180-+