home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
The Datafile PD-CD 3
/
PDCD_3.iso
/
internet
/
scrpthlp
/
SCRIPTHLP
Wrap
Text File
|
1995-07-01
|
22KB
|
666 lines
# $Id: ScriptHelp 1.6 95/06/25 09:54:32 root Exp Locker: root $
ScriptHelp
==========
This help file applies to R.Orwin/A.P. Fitch slipdial script.
Script file Revision 1.6
Contents
--------
1.0 Introduction
2.0 Using the script
3.0 Script Requirements
3.1 Modem Driver
3.2 Setting up your modem to transmit status messages
3.3 Making sure that TTFN etc have been "seen".
4.0 Customizing the script
4.1 The contents of the configuration file, !slipdial.scripts.demconfg
4.2 To change the default dialler to Mercury.
4.2.1 To remove your Mercury PIN from a local number.
4.3 To Alter the Dialler Menu.
4.4 To Alter the List of Numbers
4.5 To Alter the Number of Retries.
4.6 To Change the Local Dialler Icon Number.
5.0 Some Frequently Asked Questions.
6.0 Conclusions and Acknowledgements.
1.0 Introduction
================
This script was originally written by Rob Orwin. I initially modified
to make it more readable, and also to learn the script language
myself. Recently it has been customised to work with TTFN/Newsbase,
and included in Dr. Alan Hassey's Internet Starter Pack for Acorn
Computers.
Changes made to version 1.5/1.6
-------------------------------
The script has been largely re-written, mainly so that all
configuration information is held in the file
!slipdial.scripts.demconfg. So that new and old configuration files
are not confused, the the configuration file is now called "demconfg"
instead of "demonconfg".
The main advantage of these changes are
1) the script should start up faster
2) changes may be made to the phone numbers dialled without editing
the script (i.e. only demconfg has to be edited).
Two additional configuration options have been added
1) it is now possible to specify a number in the configuration file
which will NOT have the mercury prefix added
2) it is now possible to specify the default "local" number as a
completely separate item. In the past, it was assumed that the
"local" number would not require a mercury prefix - this is not
always the case, so they have been made separate.
Finally, error reporting has been improved
1) if the call fails due to not receiving the login, password, or
protocol prompts, you will be told what caused the failure.
2.0 Using the script
====================
The script is placed in the !SlipDial.scripts directory. You can
either load it by dragging it and dropping it on the SlipDial icon bar
icon, or you can set SlipDial up to run the script automatically. You
should read the SlipDial documentation file !SlipDial.!Help to
understand this.
For the default setup with the starter pack, the scriptfile should be
named
!SlipDial.scripts.demon
When the script is run for the first time, it asks for setup
information and stores it in a configuration file. This version of
the script has more information stored in the configuration file, and
so may ask you for the information again, even if you have previously
stored it.
There are a number of requirements for getting the script to work in
the best way. In particular, you need to
1) make sure you are using the correct modem driver file
2) set up your modem to return certain messages
3) make sure that TTFN, NewsBase, and TCPIP have been "seen" by the filer
There are also a number of ways you can customise your setup. The
simplest ones are
1) to change the default dialler to Mercury
2) to alter the entries that appear on the menu for dialling
3) to alter the default entries when dialling a list of phone numbers
4) to alter the number of times SlipDial retries each number if the
line is busy
5) to change the local number
>From version 1.5 onwards of the script, these changes may be made by
editing the file !slipdial.scripts.demconfg (known hereinafter as the
"configuration file").
Note that to make changes to the script or the configuration, you
simply have to use a normal text editor, e.g. Edit.
With !SlipDial, there is a file called !SlipDial.scripts.DemonSpr,
which contains sprite definitions. You must make sure you have the
most up-to-date version of these sprites. If the file contains three
sprites, you are ok - if it only contains 2, you should update it to
the latest one by downloading it from demon ftp.
3.0 Script Requirements
=======================
3.1 Modem Driver
----------------
The modem drivers are stored in the directory !SlipDial.Drivers.
There are examples for a number of modems. The driver is set when
the configuration file is first stored (normally when you first run
the script). Simply answer the question wih the driver you wish to
use.
3.2 Setting up your modem to transmit status messages
-----------------------------------------------------
If you run the script, and it appears to hangup after the call has got
through but before TCPIP has started; or it doesn't recognise that the
line is busy; then you need to make sure that the modem is returning
messages indicating its (the modem's) status. These messages are text
strings, and their meaning is defined in the driver file. For
instance, with the US Robotics Sportster modem, you need to send the
setup string "X4" to enable all messages.
This means that when the modem detects the line is busy, it will
return the string "BUSY". You can tell the script to expect the
string "BUSY" to indicate engaged by putting it in the modem driver
file and assigning it to the script variable $busy. When dialling the
modem looks for the string to see if it is equal to the contents of
$busy and uses this to detect engaged lines.
The various possible strings, and their setups for a USR modem are
shown in the example driver file below
set $init "ATB0E1F1M1Q0S7=30V1X4 AT&A2&B1&C1&D2&H1&I0 AT&K3&M4&N0&R2&S0&Y1"
set $busy "BUSY"
set $conn "CONNECT"
set $nocarr "NO CARRIER"
set $nodial "NO DIAL TONE"
The $init string is sent to the modem to set it up. You will notice that
the example above has X4 enabled.
If you have a modem which returns different strings, you would have to
create your own modem driver. For instance, if your modem returned
"ENGAGED", you would have to modify the driver file to contain
set $busy "ENGAGED"
3.3 Making sure that TTFN etc have been "seen".
-----------------------------------------------
The script runs TTFN, Newsbase, and TCPIP automatically. To do this,
it needs to know where they are. It can find them if you have opened
a filer window with these programmes visible. The simplest way to
ensure that they have been seen is to put all the internet related
programmes in one directory. Then when you open the directory in
order to double-click SlipDial, you know that all the other
programmes have been seen.
4.0 Customizing the Script
==========================
4.1 The contents of the configuration file, !slipdial.scripts.demconfg
----------------------------------------------------------------------
A typical configuration file looks like this.
SP_DualPC <-- the required block driver
0 <-- port number
57600 <-- computer to modem speed
cycle <-- your host name
password <-- your password
USR <-- the modem driver
bt <-- telephone service provider
131,999999999 <-- your mercury pin
IsleOfWight <-- menu entry 1 title
01983523306 <-- menu entry 1 phone number
Reading <-- menu entry 2 title
01734284848 <-- menu entry 2 phone number
London <-- menu entry 3 title
01813384848 <-- menu entry 3 phone number
01983523306 <-- the local (default) number
01983523306 <-- a number which should NOT be prefixed
with a mercury pin
Normally this would be set up by running !DemConfg, if you use
the Demon internet starter pack. However if you need to change
something later, here is a description of what each option means.
4.1.1 Block Driver
------------------
This is the block driver name. It should be set to match with your computer, and the type of modem