nhaus@eagle.wesleyan.edu (09/14/90)
I have run into a problem running MS-Kermit 2.31 in Windows 3.0 in 386-enhanced
mode. Kermit works fine when started from DOS or in Windows in Standard or Real
mode, but when started from Windows in 386-enhanced mode, once the CONNECT
command is given, characters are not echoed on the screen. That is, characters
echoed back from the modem or the remote host are not displayed. I have played
with all of the memory and display options in the Windows PIF editor, but to no
avail. I have also tried giving Kermit access to a full 640k, running as an
exclusive, unswappable, full-screen, etc. process, with no change.
I am using a HOOK-UP internal 1200baud modem in COM3, MS-Kermit 2.31 and
Windows 3.0 in 386-enhanced mode on a Northgate Elegance 386-25 with 4 meg and
64k cache.
Any ideas?
-Nik
NHAUS@eagle.wesleyan.eduJRD@cc.usu.edu (Joe Doupnik) (09/17/90)
Kermit in Window 3 Enhanced mode, responding to Nik Haus - First, upgrade from version 2.31 of MS-DOS Kermit to v3.0. Second, you say that the problem occurs with an internal modem arranged as COM3. I suspect that Windows is not releasing the address of COM3 to Kermit and hence no comms. If Windows does not cooperate you can try the command SET COM3 <port address> in test version 3.02 of Kermit (available in the test area of the Columbia Univ Kermit archives) to force in the correct address even if Windows has zeroed it. Yes, MS-DOS Kermit v3.0 does run in Windows 3.0, all modes. Joe D.