🚀 go-pugleaf

In article <1--h_3g@rpi.edu>, barryf@aix01.aix.rpi.edu (Barry B. Floyd) writes:
> 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-+
--------------------------
	Barry is correct: Windows can sometimes refuse to reveal COMn.
The Windows 3.0 .PIF material has been published on this list a couple
of times (by me) and appears again in the help file for MSK 3.10 on the
Columbia Univ archives. Please grab all the files, including the Patch
file MSR310.PCH.
	Joe D.