doc.me

通讯程序源码

CHG_DIR directory
.br
Change the current working directory to the given directory.
.sp
.ti -0.5i
HANG_UP
.br
Hang up the phone, but remain in Pcomm.
.sp
.ti -0.5i
PRINTER [ ON | OFF ]
.br
Control the logging of data to the printer.
.sp
.ti -0.5i
MODEM_BREAK
.br
Send a modem break to the remote system.  This is typically used to
tell the remote to switch to a different baud rate.
.sp
.ti -0.5i
SEND protocol filename
.br
Send a file to the remote.  The valid protocols are XMODEM, XMODEM_1K,
MODEM7, YMODEM, YMODEM_G, ASCII, EXT_1, EXT_2, and EXT_3.
.sp
.ti -0.5i
RECEIVE protocol filename
.br
Receive a file from the remote.  The valid protocols are XMODEM,
XMODEM_1K, MODEM7, YMODEM, YMODEM_G, ASCII, EXT_1, EXT_2, and EXT_3.
.sp
.ti -0.5i
SCREEN_DUMP
.br
Dump the current contents of the screen to the DUMPFILE.  If the file
already exists, the new contents are appended to the file.
.sp
.ti -0.5i
DATA_LOG [ ON | OFF ]
.br
Control logging of the terminal session to the LOGFILE.  If the file
already exists, the new contents are appended to the file.
.in
.sh 2 "Waitfor command"
.(x
  \*($n Waitfor command
.)x
.lp
The waitfor command has the following syntax:
.sp
.in +0.5i
waitfor \-n string
.in
.lp
where \*(lqn\*(rq is the number of seconds to wait and \*(lqstring\*(rq
is the string to wait for.
.lp
Waitfor returns a 0 if the string was found, a 1 if it didn't find the
string within the allotted time, and a \-1 if there was an error.
Waitfor returns immediately if the string is found.
.lp
The waitfor command would typically be used in a script to indicate that
the desired prompt has appeared.  For example:
.sp
.in +0.5i
.CS
.(b L
waitfor \-5 "ogin:"
if [ "$?" \-eq 0 ]
then
.in +0.5i
echo "egray"
.in
fi
.)b
.Cs
.in
.lp
would wait up to 5 seconds for the string \*(lqogin:\*(rq.  If the
return code is 0 (the strings did appear), send the string
\*(lqegray\*(rq (my user ID).
.lp
.ft I
NOTE:\ \ Upper and lower case letters are considered different.  If you
are not sure if the prompt is \*(lqLogin:\*(rq or \*(lqlogin:\*(rq, then
skip the first letter in the string and use \*(lqogin:\*(rq.
.ft 
.sh 2 "Matches command"
.(x
  \*($n Matches command
.)x
.lp
The matches command has the following syntax:
.in +0.5i
.sp
matches string1 string2
.in
.lp
Matches returns a 0 if string2 is contained in string1, and returns a 1
if it does not.  Unlike waitfor, the matches command does not read the
TTY port.
.lp
The matches command could be used to test string values such as:
.sp
.in +0.5i
.CS
.(b L
read junk
matches $junk "login failed"
if [ "$?" \-eq 0 ]
then
.in +0.5i
exit
.in
fi
.)b
.Cs
.in
.sh 2 "Examples"
.(x
  \*($n Examples
.)x
.lp
It is not my intention to teach the reader the fundamentals of Unix
shell programming.  There are several good books on the subject
available in stores.
.lp
Remember to add execute permission to the file and remove the read
permission to all others.
.lp
.(b L
The simplest auto-login script may contain the following:
.sp
.in +0.5i
.CS
# send a <CR>
echo ""
# wait 5 seconds for the login prompt
waitfor \-5 ogin:
# send my user ID
echo "egray"
# wait 5 seconds for the password prompt
waitfor \-5 assword:
# send my password
echo "abcdefg"
# return to Pcomm
exit 0
.Cs
.)b
.in
.lp
.(b L
A more complex script is required if the user must send a modem break to
synchronize the baud rate of the remote.  For example:
.sp
.in +0.5i
.CS
echo ""
try=0
# loop until done
while true
do
.in +0.5i
# wait 5 seconds for the login prompt
waitfor \-5 ogin:
# test the exit code of the waitfor command
if [ "$?" \-eq 0 ]
then
.in +0.5i
# send my user ID and exit the loop
echo "egray"
break
.in
fi
.sp
# increment the number of attempts
try=\`expr $try + 1\`
# test to see if we should give up
if [ "$try" \-eq 5 ]
then
.in +0.5i
exit 1
.in
fi
.sp
# send a modem break and loop again
pcomm_cmd modem_break
echo ""
.in 0.5i
done
# wait 5 seconds for the password prompt
waitfor \-5 assword:
# test the return code from waitfor
if [ "$?" \-eq 0 ]
then
.in +0.5i
# send my password
echo "abcdefg"
.in
else
.in +0.5i
exit 1
.in
fi
# return to Pcomm
exit 0
.Cs
.)b
.in 0
.lp
.(b L
The following is an example of a shell script that will dial a system,
log a user on, transfer a file called junk using xmodem, log out, and
exit Pcomm.
.sp
.in +0.5i
.CS
# are we already connected?
answer=`pcomm_cmd if connected`
if [ "$answer" -eq 0 ]
then
.in +0.5i
# dial entry number 23 in my dialing directory
pcomm_cmd dial 23
.in -0.5i
fi
# wait for the login prompt
waitfor ogin:
# send my user id
echo egray
# wait for the password prompt
waitfor assword:
# send my password
echo abcdefg
# wait for a Unix prompt
waitfor $
# start up an xmodem file transfer
echo sx junk
# wait for the sx command to say its ready
waitfor now
sleep 1
# do a file transfer
pcomm_cmd receive xmodem junk
# wait for the prompt
waitfor $
# log me out
echo "^D"
sleep 1
# exit pcomm
pcomm_cmd exit
.Cs
.)b
.in 0
.bp
.if e \{
.ep
.bp\}
.uh "Appendix A \- Typical Modem Configuration"
.(x
 
.)x _
.(x
Appendix A \- Typical Modem Configuration
.)x
.lp
I can't begin to describe how to configure every modem to work with
Pcomm.  There are, however, several guidelines that will apply to
virtually any modem.
.ba +0.5i
.lp
1) Pcomm doesn't care about the DCD (Data Carrier Detect) settings of
the modem.
.lp
2) It would be nice (but not essential) if the loss of the DTR (Data
Terminal Ready) caused the modem to hang up.
.lp
3) Pcomm doesn't care if commands are echoed back by the modem (it might
save a few milliseconds if echoing was turned off).
.lp
4) Some sort of result codes are required.  Numeric result codes are
ok...  but since they are displayed on the screen, word result codes
will make more sense.
.lp
5) If the modem can return different result codes for each baud rate at
which it answers, then by all means, use them.  Match the odd-ball
codes (such as CONNECT FAST for Telebit PEP) to the closet matching speed.
.lp
6) Anything that is returned by the modem, but not listed in the modem
setup, is ignored.
.lp
7) Systems running older versions of uugetty (the bi-directional version
of getty that comes with HDB uucp) may require extra commands in the
initialization string to assure that uugetty switches to its dial out
mode.  Normally, \*(lqAT!~AT!~\*(rq causes enough dialogue to force
uugetty to release the line.
.ba
.lp
For example, a 2400 baud Hayes compatible modem might be configured with
the following command:
.sp
.in +0.5i
.nf
AT\ S7=60\ S11=70\ E0\ Q0\ V1\ X4\ &D2
.fi
.in +0.5i
.(b L
.TS
l l.
AT	Hayes attention command
S7=60	Wait 60 seconds for an answer
S11=70	70 ms touch tone dialing
E0	Don't echo commands (not essential)
Q0	Turn result codes on
V1	Return word result codes
X4	Use as many result codes as you've got
&D2	Hang up when DTR is lost (nice to have)
.TE
.)b
.in 0
.bp
.if e \{
.ep
.bp\}
.uh "Appendix B \- AT&T Unix PC 7300/3b1 Dial Codes"
.(x
 
.)x _
.(x
Appendix B \- AT&T Unix PC 7300/3b1 Dial Codes
.)x
.lp
The dialing codes used by the OBM (On Board Modem) are not
straight-forward.  The modem setup, as included in the Unixpc.shar file,
looks like this:
.br
.CS
.(b L
.(c
-------------------------- Modem Setup --------------------------
.sp
           1) Modem name (1 of 2) ... OBM
           2) Modem init string .....
           3) Dialing command ....... %
           4) Dialing cmd suffix .... @
           5) Hang up string ........
           6) Auto baud detect ...... N
           7) 300 baud connect ...... CONNECT
           8) 1200 baud connect ..... CONNECT
           9) 2400 baud connect .....
          10) 4800 baud connect .....
          11) 9600 baud connect .....
          12) 19200 baud connect ....
          13) 38400 baud connect ....
          14) No connect string 1 ...
          15) No connect string 2 ...
          16) No connect string 3 ...
          17) No connect string 4 ...
-----------------------------------------------------------------
OPTION ==> _                                Press <ESC> to return
.)c
.)b
.Cs
.lp
The relevant fields of the modem setup are:
.ba +0.5i
.lp
1) Modem name.  This must be \*(lqOBM\*(rq.
.lp
.ft I
NOTE:\ \ Pcomm uses the modem name as a flag to determine which dialing
method to use.  The string \*(lqOBM\*(rq is a \*(lqreserved word\*(rq
that Pcomm uses to switch to the AT&T Unix PC 7300/3b1 dialing method.
.ft
.lp
3) Dialing command.  This should be \*(lq%\*(rq for touch tone dialing
or \*(lq^\*(rq for pulse dialing.
.lp
4) Dialing cmd suffix.  This must be the \*(lq@\*(rq character.
.lp
6) Auto baud detect.  The OBM cannot use the auto baud detect feature.
.lp
7\-8) Connect strings.  Although the OBM doesn't actually return any
result codes, these fake fields are required.
.ba
.lp
Additional OBM dialing codes from the phone(7) manual:
.br
.in +0.5i
.(b L
.TS
l l.
\*(lq~\*(rq	wait for next dial tone
\*(lq,\*(rq	pause 2 seconds
\*(lq:\*(rq	pause 10 seconds
\*(lq&\*(rq	perform a hookflash
\*(lq%\*(rq	begin tone dialing
\*(lq^\*(rq	begin pulse dialing
.TE
.)b
.in
.lp
These codes can be inserted into the phone number string, for example:
.br
.in +0.5i
.(b L
.TS
l l.
555-1234~56	dial 555-1234, wait for tone, dial 56
9,555-1234	dial 9, wait 2 seconds, dial 555-1234
%555^1234	dial 555 using tone, 1234 using pulse
.TE
.)b
.in
.lp
.ft I
NOTE:\ \ The dialing codes for the OBM are not subject to character
synonym translations, therefore the \*(lq%\*(rq, \*(lq^\*(rq, and
\*(lq~\*(rq characters do NOT have to be preceded by the \*(lq\e\*(rq
character to remove their special meaning.
.ft
.bp
.if e \{
.ep
.bp\}
.uh "Appendix C \- Using High Speed Modems"
.(x
 
.)x _
.(x
Appendix C \- Using High Speed Modems
.)x
.ba
.lp
The features and complexities of the newer high speed intelligent modems
available today warrants a more detailed discussion.
.lp
1) Locked interface speed
.ba +0.5i
.lp
Newer modems have the ability to maintain a locked interface speed
with the computer without regard to the connected baud rate.  For
example, it is a good idea to lock the interface speed at
19200 baud (or 38400) when the modem is \*(lqtalking\*(rq at 14400 baud.
.lp
The \*(lqlocked speed\*(rq field of the TTY database was created to
solve this problem.  If this value is non-zero, Pcomm will only use this
baud rate when talking to the modem.  The true connected baud rate
(14400 for example) will continue to be displayed in the status line.
.ba
.lp
2) Multiple setups
.ba +0.5i
.lp
Users of newer modems may require a different \*(lqinit string\*(rq or
\*(lqdial string\*(rq depending on the target machine being called.  For
example, when trying to connect to older V.32 modems, the V.42 and V.42bis
features may have to be disabled.  In this case, the dial string would
contain the command to disable the unwanted features.
.lp
This problem is solved by creating additional modem entries in the modem
database.  For example, you could have an entry called \*(lqTELEBIT\*(rq
for normal connections, one called \*(lqTELEBIT_V.32\*(rq for connecting
to older V.32 modems, and another called \*(lqTELEBIT_PEP\*(rq for 
connections to other PEP modems.
.lp
Pcomm uses the connect strings to determine if the modem can handle the
requested baud rate.  If there are multiple modems that satisfy that baud
rate, then the first modem entry is used.  You can influence the choice of
suitable modems by placing the name of the modem in the Auxiliary field of
the dialing directory.  In this way, you can have a default modem and a 
specific modem for each dialing directory that my require one.
.lp
.ft I
NOTE:\ \ The default modem configuration (in a multiple setup situation)
must appear first in the modem database.
.ft
.lp
Your choices are virtually unlimited...  you can have a separate modem
setup to control modem features such as error control, compression,
protocol spoofing, etc.
.ba
.lp
3) Telebit WorldBlazer settings
.ba +0.5i
.lp
The following configuration is what I personally use for my Telebit
WorldBlazer on bi-directional lines (ones with uugetty).  Your mileage
may vary.
.in +0.5i
.(b L
.TS
l l.
~&F 	Restores fa