Xref: utzoo comp.sys.ibm.pc.hardware:280 comp.os.msdos.misc:53 comp.os.msdos.apps:66 alt.msdos.programmer:1891
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!samsung!rex!rouge!pc!jpd
From: jpd@pc.usl.edu (Dugal James P.)
Newsgroups: comp.sys.ibm.pc.hardware,comp.os.msdos.misc,comp.os.msdos.apps,alt.msdos.programmer
Subject: Re: Help with Kermit using COM3
Keywords: Kermit, Tricky Hardware Problem
Message-ID: <11661@rouge.usl.edu>
Date: 17 Jul 90 20:47:08 GMT
References: <7937@ccncsu.ColoState.EDU>
Sender: anon@rouge.usl.edu
Followup-To: comp.sys.ibm.pc.hardware
Organization: Univ. of Southwestern La., Lafayette
Lines: 15
Originator: jpd@pc.usl.edu

In article <7937@ccncsu.ColoState.EDU> ks336514@longs.LANCE.ColoState.EDU (Keith Schwols) writes:
>machine at COM3.  When I bring up Kermit (3.01) and set port to com3, I
>get the message that the modem was not found and bios3 will be used

Kermit is checking the COM3 port addr stored at 40:4, and not finding it.
This is a common problem.  You could use debug to store COM3's addr manually,
or check the MS-Kermit docs for the short DEBUG script to create a program
to do it for you, or better yet, look in comp.binaries.ibm.pc for the
34instal posting.

-- 
-- James Dugal,	N5KNX		Internet: jpd@usl.edu
Associate Director		Ham packet: n5knx@k5arh
Computing Center		US Mail: PO Box 42770  Lafayette, LA  70504
University of Southwestern LA.	Tel. 318-231-6417	U.S.A.