Xref: utzoo comp.unix.sysv386:9300 comp.unix.msdos:514
Path: utzoo!utgpu!news-server.csri.toronto.edu!rpi!zaphod.mps.ohio-state.edu!uwm.edu!csd4.csd.uwm.edu!dbm
From: dbm@csd4.csd.uwm.edu (Dennis B Meilicke)
Newsgroups: comp.unix.sysv386,comp.unix.msdos
Subject: Re: Problems with SimulTask 386 and MS-Kermit 3.1
Message-ID: <13374@uwm.edu>
Date: 25 Jun 91 00:16:19 GMT
References: <1991Jun23.153720.1674@unhd.unh.edu>
Sender: news@uwm.edu
Followup-To: comp.unix.sysv386
Organization: University of Wisconsin - Milwaukee
Lines: 28

In article <1991Jun23.153720.1674@unhd.unh.edu> pss1@kepler.unh.edu (Paul S Secinaro) writes:
>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

Well, I'm not sure, but...

I have a similar problem running MS-Kermit 3.1 under MS-DOS.  My modem
is on COM4.  When I tell Kermit to use COM4, it tells me there is no
hardware for this port, and uses BIOS4.  When I connect, I get a
screen full of characters.

I'm not sure, but I think Kermit's port definitions are screwed up.
After a lot of trial and error, I found that I can get Kermit to work
by telling it to use COM2.  *All* of my other programs use COM4.  Very
strange.  Anyway, you might try using COM4.

Good luck...

Dennis