[comp.protocols.misc] trouble with MS-kermit 3.0 scripting facility

glenn@welch.jhu.edu (Glenn M. Mason) (07/05/90)

I am having a problem with the scripting facility available within
version 3.0 of MS-Kermit. I am rather desperate at this point and
would greatly appreciate any help at all from anyone who has some
experience with this stuff.

I am trying to provide an inexpensive way for users to access genetics
databases here at Johns Hopkins Medical Library. I have written a DOS
application which runs "on top" of kermit to provide a colorful, window-
based communications program to provide a means of accessing our systems
with little knowledge of modem commands, kermit commands, etc. The
application is menu-driven with a dialing directory browser and other
goodies. Users select terminal emulation, port and speed settings, session
logging, etc. via menu options. There is also on-line help assistance.
It is very likely that this program could be placed into public-domain
after testing is completed and all problems are corrected.

The problem I am having has occurred after a few beta-testers for this
application had repeated failures to connect to our system. It appears to
me that the problem centers around the failure to receive the proper
modem response. In the scripts that follow I use the kermit INPUT command
to wait for an "OK" response from the modem. (I later changed the INPUT
command to wait for just "O" since I found that some modems respond this
way ... this change is not reflected in the below scripts however.) I
noticed that many of the scripts displayed just a "K" where I expected to
see "OK". I don't know for sure whether an "OK" was sent by the modem but
was incorrectly written to the transaction log file. I also noticed a few
logged transactions with several embedded "^G" characters throughout the
log file. I am very puzzled with this.

I also want to say that all modems used in the tests were Hayes-compatible
modems, either 1200 or 2400 baud. It also appears that this problem was
about twice as likely to occur at 2400-baud setting that at 1200-baud. I
am not a modem expert nor an expert using MS-kermit. I am just trying to
solve a problem with the best available tools that I can put my hands on.

If any knowledgable individual can help out with this problem, here
are the files involved with this problem. First listed are the three
kermit script files involved. Last is a listing of an example transaction
log from a beta-tester that failed to connect.


----- mskermit.ini -----
ECHO +-----------------------------------------+\13
ECHO |                                         |\13
ECHO |  Remember to press the End key to close |\13
ECHO |  the connection and hangup line (after  |\13
ECHO |    you have terminated your session.)   |\13
ECHO |                                         |\13
ECHO +-----------------------------------------+\13
ECHO Setting modem parameters ...\13
SET PORT 2
SET TAKE-ECHO ON
SET LOCAL-ECHO OFF
SET MODE-LINE OFF
SET INPUT ECHO ON
SET SPEED 1200
SET TERM VT320
SET PARITY EVEN
SET DISPLAY 7-BIT
SET KEY \4431 \KEXIT
SET KEY \315 \27\91\49\55\126
SET KEY \316 \27\91\49\56\126
SET KEY \317 \27\91\49\57\126
SET KEY \318 \27\91\50\48\126
SET KEY \319 \27\91\50\49\126
OUTPUT AT\13
INPUT 3 OK
IF FAILURE GOTO RESET
TAKE DIAL.CMD
GOTO DONE
:RESET
ECHO Do you have the correct port setting?\13
ECHO If so hangup line or reset modem and try again.\13
:DONE
ECHO Hanging up the line ...\13
OUTPUT +++
PAUSE 1
OUTPUT ATH\13
PAUSE 2
HANGUP
PAUSE 1
QUIT
-----

----- dial.cmd -----
OUTPUT AT\13
INPUT 3 OK
IF FAILURE POP
ECHO Dialing ...\13
OUTPUT ATDT9-727-6060\13
INPUT 45 CONNECT
IF FAILURE POP
ECHO Connected.\13
PAUSE 1
TAKE WELCH.CMD   
-----

There are never problems from this point, but for completeness here
is the last MS-kermit script file involved:

----- welch.cmd -----
;
;  WELCH.CMD
;
;  This is the kermit script file to log onto the welchlab host
;  computer - home of the OMIM(tm) and GDB Genetic Databases.
;
ECHO Initializing Telenet connection ...\13
PAUSE 4
OUTPUT \13\13
INPUT 5 TERMINAL=
IF FAILURE POP
OUTPUT D1\13
PAUSE 1
OUTPUT C 301 55030\13	; connect via Telenet to welchlab
ECHO Logging into Welch Library host ...\13
INPUT 10 CONNECTED
IF FAILURE POP
PAUSE 1
OUTPUT \13
INPUT 5 login:
IF FAILURE POP
CLEAR
ECHO Connected to Welch Medical Library.\13
OUTPUT \13
CONNECT
-----


----- beta-test transaction log -----
AT
OK
AT
OK
ATDT429-0956
CONNECT400

TELENET
202 111T 

TERMINAL=D1

@C 301 55030

301 55030 CONNECTED
Welch Medical Library
login: 
l
login: +++
K
ATH
K			<< OK?
AT
OK
AT
OK
ATDT429-0956
NNECT 2400		<< wait for CONNECT here ... don't get it

OK
ATH
OK
AT
+++ATH

-----

Any help or suggestions will be greatly appreciated.

Thank you,
Glenn



Internet: glenn@welch.jhu.edu
Voice: (301)955-9658
FAX: (301)955-0054