ckermit.bwr

linux终端仿真程序

appropriate SET DUPLEX command (FULL or HALF), and then CONNECT again.
For a consistently misbehaving connection, you can automate this process in
a macro or TAKE file.

TELNET sessions are treated just like serial communications sessions as far as
"terminal bytesize" and "command bytesize" are concerned.  If you need to view
and/or enter 8-bit characters during a TELNET session, you must tell C-Kermit
to SET TERMINAL BYTESIZE 8, SET COMMAND BYTESIZE 8, and SET PARITY NONE.

If you SET TERMINAL DEBUG ON or SET DEBUG SESSION (same thing), TELNET
protocol negotiations will be displayed on your screen.  But most of the
interesting negotiations happen at the time the SET HOST or TELNET command
is given, before CONNECT mode is entered, so you won't see them on your
screen.  However, you can still capture them in the debug log ("log debug").

C-Kermit version 6.0 has a new set of SET TCP commands, to control TCP-level
parameters, such as "keepalive" protocol (that allows C-Kermit to detect
more quickly and reliably when a connection is broken).  In case you should
see a message like:

  Could not get SO_KEEPALIVE: Protocol not available

it means that the underlying TCP/IP stack does not support this feature.
Don't worry, no harm is done.  You can make this message go away by adding:

  SET TCP KEEPALIVE OFF

Similarly for the other SET TCP commands.


(5) THE SERVICES DIRECTORY

Until edit 190, the login macros (such as UNIXLOGIN, VMSLOGIN, etc), which are
used in the services directory, had their respective system prompts
hard-coded, so if the prompt on the system you were logging in to differed
from the one in the macro, the macro would time out and report failure (even
though it actually did log you in).  These macros have been changed in edit
190 to allow you to override the default prompt.  As explained on pp.297-301
of "Using C-Kermit", the format of a services directory entry is:

  entry-name  login-macro-name  user-id  connection-macro-name + arguments

For example:

  chemistry   vmslogin   ivan   call hayes com1 2400 7654321

If you want to specify the system prompt to look for after logging in, you
can do it by grouping it after the login macro name in braces, like this:

  chemistry   {vmslogin CHEM:}  ivan   call hayes com1 2400 7654321

For reference, here are the standard login macros and the default prompts:

  UNIXLOGIN     \13\10$\32  (i.e. CR, LF, dollar sign, space)
  VMSLOGIN      \13\10$\32  (ditto)
  CISLOGIN      CompuServe Information Service
  DOWLOGIN      ENTER QUERY
  VMLINELOGIN   (Not applicable)
  VMFULLOGIN    (Not applicable)


(6) MODEMS AND DIALING

(Also see MODEMS.DOC and DIALING.DOC)

The list of modem types supported by C-Kermit is obtained by typing:

  set modem type ?

at the C-Kermit> prompt.  Note that the ITU-T (V.25bis) modem type is only
for asynchronous mode, not synchronous (HDLC) mode -- there is no support
in C-Kermit for synchronous communication (except for SET NET X.25, which
is available in SunOS and Solaris with SunLink X.25, and in Stratus VOS,
but that still has nothing to do with V.25bis modems).

If you have a high-speed, error-correcting, data-compressing modem, you should
generally use the following settings:

  set speed 57600 ; Or 38400, the highest supported by both Kermit & the modem
  set modem speed-matching off  ; Use speed buffering.
  set modem error-correction on ; Enable error-correction and compression.
  set modem data-compression on

An important change in C-Kermit 6.0 is that when you give a SET MODEM TYPE
command to tell Kermit what kind of modem you have, Kermit also sets a number
of other modem-related parameters automatically from its internal modem
database.  Thus, the order in which you give modem-related commands is
significant, whereas in prior releases they could be given in any order.

The new default for flow control is "auto", meaning "do the right thing".
So (for example) if your version of C-Kermit supports SET FLOW RTS/CTS and
your modem also supports RTS/CTS, then Kermit will automatically set its
flow control to RTS/CTS *and* set modem's flow control to RTS/CTS too before
attempting to use the modem.

ADDING NEW MODEM TYPES TO C-KERMIT (see MODEMS.DOC)


(7) DIALING HINTS AND TIPS

(Also see DIALING.DOC)

Remember: In many C-Kermit implementations (depending on the underlying
operating system -- mostly Windows, OS/2, and System-V-based UNIX versions),
you can't CONNECT to a modem and type the modem's dialing command (like
"ATDT7654321") manually, unless you first tell C-Kermit to:

  SET CARRIER-WATCH OFF

This is because (in these implementations), the CONNECT command requires the
modem's Carrier Detect (CD) signal to be on, but the CD signal doesn't come on
until after dialing is complete.  This requirement is what allows C-Kermit to
pop back to its prompt automatically when the connection is hung up.  See the
description of SET CARRIER in "Using C-Kermit".

Similarly, if your dialed connection drops when CARRIER-WATCH is set to AUTO
or ON, you can't CONNECT back to the (now disconnected) screen to see what
might have happened unless you first SET CARRIER-WATCH OFF.

Don't SET FLOW RTS/CTS if your modem is turned off, or if it is not presenting
the CTS signal.  Otherwise, the serial device driver might get stuck waiting
for this signal to appear.

Here are a few points to clarify the purpose of SET MODEM SPEED-MATCHING:

 0. The name was changed from SET DIAL SPEED-MATCHING to SET MODEM
    SPEED-MATCHING in edit 192, as part of the overhaul of the dialing
    features.

 1. This command does not do anything at all to the modem.  Rather, it is used
    to inform C-Kermit about the modem's configuration: whether the modem's
    interface speed is "fixed", or it changes its interface speed when a
    connection is made.  In the latter case, C-Kermit changes its own speed in
    response to the speed given in the modem's CONNECT message.  By default,
    SPEED-MATCHING is ON, so Kermit does indeed attempt to change its speed.
    If your modem is set to have a fixed interface speed, you must SET MODEM
    SPEED-MATCHING OFF.

 2. When MODEM SPEED-MATCHING is ON:

    (a) Your modem must be configured to report its *interface* speed in the
        CONNECT message, rather than the connection (modulation) speed.

    (b) Your computer (and C-Kermit) must support all connection speeds that
        might be reported by your modem.  SET SPEED ? will give you a list of
        the speeds that your version of C-Kermit knows about.

 3. If conditions (a) and (b) cannot be satisfied, then you must:

    (a) Configure your modem to lock its interface speed

    (b) Tell C-Kermit to SET MODEM SPEED-MATCHING OFF

To illustrate, suppose you have a V.32bis modem.  When it connects to a
remote V.32bis modem, it might issue a message like:

  CONNECT 14400

But 14400 bps is not a speed that is supported by certain operating systems
and so C-Kermit might fail to adjust its speed according to this report.
Therefore, you must lock the modem's interface speed at a higher speed (such
as 19200, 38400, or 57600) that is supported by C-Kermit, set C-Kermit to the
same speed, and tell C-Kermit to SET MODEM SPEED-MATCHING OFF.

If you have a high-speed, error-correcting, data-compressing, speed-buffering
modem, you should always SET MODEM SPEED-MATCHING OFF, and you should fix the
modem's interface speed as high as possible, preferably four times higher than
its maximum connection (modulation) speed to allow compression to work at full
advantage.  In this type of setup, you must also have an effective means of
flow control enabled between C-Kermit and the modem, preferably hardware
(RTS/CTS) flow control.

C-Kermit knows about a large number of modems, depending on how it was built
(type "set modem type ?" and "show features" for further info).  This
knowledge is imbedded in the SET MODEM and DIAL commands.  If you are having
trouble dialing your modem, SET DIAL DISPLAY ON to watch the dialing
interactions between C-Kermit and your modem.  Consult pages 65-66 of "Using
C-Kermit" for modem-dialing troubleshooting instructions.

If it takes your call longer to be completed than the timeout interval that
C-Kermit calculates, you can use the SET DIAL TIMEOUT command to override
C-Kermit's value.  But beware: the modem has its own timeout for completing
the call.  If it is a Hayes-like modem, C-Kermit adjusts the modem's value
too by setting register S7.  But the maximum value for S7 might be smaller
than the time you need!  In that case, C-Kermit sets S7 to 0, 255, or other
(modem-specific) value to signify "no timeout".

WARNING: Certain modems might have a maximum dial timeout shorter than what
Kermit expects it to be.  If Kermit attempts to set register S7 to a value
higher than your modem's maximum, the modem will say "ERROR" and you will get
a "Failure to initialize modem" error.  In that case, use SET DIAL TIMEOUT to
override C-Kermit's calculation of the timeout value with the highest value
that is legal for your modem, e.g. 60.

The SET MODEM KERMIT-SPOOF command works only for Telebit and US Robotics
modem types; it is OFF by default.  You may wish to experiment with large
packets (1K or greater) and various window sizes with spoofing disabled in the
modem.  In most situations the transfer rates achieved by Kermit with sliding
windows and long packets are better than with protocol spoofing turned on.
Also, attribute (A) packets are not passed by Telebit modems with spoofing
enabled so if they are desired spoofing must be turned off.

Some modems have a feature called adaptive dialing.  When they are told to
dial a number using Tone dialing, they check to make sure that dialtone has
gone away after dialing the first digit.  If it has not, the modem assumes the
phone line does not accept Tone dialing and so switches to Pulse.  When
dialing out from a PBX, there is almost always a secondary dialtone.
Typically you take the phone off-hook, get the PBX dialtone, dial "9" to get
an outside line, and then get the phone company's dialtone.  In a situation
like this, you need to tell the modem to expect the secondary dialtone.  On
Hayes and compatible modems, this is done by putting a "W" in the dial string
at the appropriate place.  For example, to dial 9 for an outside line, and
then 7654321, use ATDT9W7654321.  In Kermit 95, this is accomplished with:

  SET PBX-OUTSIDE-PREFIX 9W

(replace "9" with whatever your PBX's outside-line prefix is).

DEC modems...  Reportedly, these don't work right when connected to a DEC
terminal server -- result codes are never reported (on the other hand, this
might be a modem configuration problem).  Dialing "by hand", "blind" still
works.  Also, reportedly "For people who do have DEC modems directly connected
to DEC computers the DF03, DF100-series, and DF200-series modem dialers should
work.  The only thing that is not straightforward is that the DF124-CA,
DF124-CM modems must use the the DF200-series since they speak Digital Modem
Command Language (DMCL) and AT commands.  The Digital Scholar Plus is a DF242
so it uses the DF200-series."

If C-Kermit's dialing methods are insufficient for your purposes, you can
write a C-Kermit script program to do the dialing.

DIALING AND FLOW CONTROL

Most modern modems support RTS/CTS (if they support any hardware flow control
at all), but some computers use different RS-232 circuits for the same
purposes, e.g. DTR and CD, or DTR and CTS.  In such cases, you might be able
to make your computer work with your modem by appropriately cross-wiring the
circuits in the cable connector, for example the computer's DTR to the modem's
RTS, and modem's CD to the computer's CTS.  HOWEVER, C-Kermit does not know
you have done this.  So if you have (say) SET FLOW DTR/CD, C-Kermit will make
no attempt to tell the modem to use RTS/CTS.  You probably did this yourself
when you configured the modem.

A "TIES" (Time-Independent Escape Sequence) modem does not require any guard
time around its escape sequence.  The following text: