Xref: utzoo comp.unix.sysv386:9263 comp.unix.msdos:510
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uunet!unhd.unh.edu!kepler.unh.edu!pss1
From: pss1@kepler.unh.edu (Paul S Secinaro)
Newsgroups: comp.unix.sysv386,comp.unix.msdos
Subject: Problems with SimulTask 386 and MS-Kermit 3.1
Message-ID: <1991Jun23.153720.1674@unhd.unh.edu>
Date: 23 Jun 91 15:37:20 GMT
Sender: usenet@unhd.unh.edu (USENET News System)
Organization: University of New Hampshire
Lines: 27
Nntp-Posting-Host: kepler.unh.edu

I'm using AT&T SimulTask 386 version 2.0 (which is actually VP/ix 1.something)
on an AT&T SVR3.2.1 system.  I'm having a problem with MS-Kermit 3.1

When I run Kermit, with Simultask set up to allow access to the COM2 port, I
get the error message:

?Warning: no harware for this serial port
?This port will be operated through the Bios as BIOS2

In other words, Kermit has decided it will communicate with COM2 using only
standard Bios calls.  The problem is, when I go into terminal mode, the screen
just starts filling with the character "2".  The program doesn't crash - I can
exit terminal mode and mess with the comm parameters, etc.  It's as if Kermit
thinks it's receiving a steady stream of "2"'s from the COM port.  I've tried
resetting Kermit to use the hardware ports, but it just gives the above error
message again.
 
Does anyone have any ideas?  I also use Telix 3.12, and have had no problems
at all, but I prefer MS-Kermit as it has superior terminal emulation and
a better implementation of the Kermit protocol.
Thanks,
Paul Secinaro

-- 
Paul Secinaro
pss1@kepler.unh.edu
p_secinaro@unhh.unh.edu