Amiga Format CD 2/amigaformatcd02.iso/comms/netsoftware/amitcpdial10.lha/AmiTCP_dialup/AmiTCP_dialup10.doc

Text File | 1994-01-13 | 5.5 KB | 125 lines

AmiTCP_Dialup version 1.0
Date 1/12/94

    This series of AmigaDOS and ARexx scripts are designed to automate much
of the call in procedure for AmiTCP.  It can be used for SLIP & CSLIP and
supports dynamicly assigned addressing for the Annex III Terminal Server
from Xylogics.  This package probably will support PPP, it is not yet
available for the Amiga, to my knowledge.
    This is based on a script from P. Josh Rovero, which was modified from
Dave Bolen's Rexx script for OS/2.  This original script is in the main
directory, called "SLIPUP.REXX" and is included for historical information
only.  It maybe deleted as you desire.

    These scripts can be found on AmiNET & "ftp.hawaii.edu" and can be
distributed as needed.  They may also show up on the InterNet new's groups
comp.sys.amiga.datacomm and comp.sys.amiga.sources as people request (who
may not have FTP access).

    Installation is simple.  Copy the "bin" scripts to "AmiTCP:bin". Copy
the "db/pearl/netdb-myhost" template file to "AmiTCP:bin/pearl".  Copy the
"Ami" and "Ami.Info" files to anyplace that is suitable if you desire the
Icon automation.  By the way, I installed AmiTCP in the following directory
"Devs:Networks/AmiTCP-2.2" so that it is close to what it is, a networking
package.
    You may safely ignore the "AmiTCP:db/netdb-myhost" file, as it is
created at run time from the "AmiTCP:db/pearl/netdb-myhost" template file.
I included it as an example of the behaviour of these scripts.
    The ARexx part of these scripts, writes configuration data to ENV
variables HOSTNAME, Sana2/slip0.config (or whatever your's is called) and
the ENVARC master copies.  This means a AmiTCP dialup session can survive
a re-boot.  However, you should keep a copy of your old setup just in case
you need to go back to it until these dial up scripts do what you need
them to do.  Don't forget to use your "AmiTCP:db/netdb-myhost" file as the
base for the "AmiTCP:db/pearl/netdb-myhost" template file.

    Next, you must have ARexx properly installed and working.

    I make use of the following AmigaOS libraries and the have to be
installed.  I found them on AmiNET, so you should beable to also.

         RexxSupport.Library  version 34.9 (or greater?)
         RexxArpLib.Library   version 3.0  (or greater?)
         RexxSerDev.Library   version 5.01 (or greater?)


    I also have install the "APIPE:" device that AmiTCP wants for the
"fingerd" daemon.  You can remove the 3 lines in
"AmiTCP:bin/startnet_pearl.rexx" that deals with this if you want.  But I
have written the script to attempt mounting the "APIPE:" device, if it is
available, or continue on anyway, even if it is already mounted.

    The "TCP:" device is not mounted as I do use it.  A line in the
"AmiTCP:bin/startnet_pearl.rexx" file details this, but I have commented
it out.

    These scripts  will have to be modified for each user.  The following
things need to be changed at the very least.  Others as needed.

AmiTCP:bin/startnet_pearl.rexx

    Phone number
    (C)SLIP command
    User name prompt
    User name for login
    Password prompt
    Password for user
    IP address format
    Serial port name, bit rate, and other stuff.  Note this is in 2
locations.  First in the beginning for the "RexxSerDev.Library" openning
and second for "ENV:Sana2/slip.config" file.
    Name of SLIP/CSLIP (or PPP if available) configuration file.  This is
in 2 places, as I copy the "ENV:Sana2/slip0.config" file to "ENVARC:Sana2"
so that it can survive re-boots.
    Parameters for the "ENV:Sana2/slip0.config" file need to be set
according to your device driver.



AmiTCP:bin/hangup.rexx

    Serial port name, bit rate and other stuff.


AmiTCP:db/pearl/netdb-myhost

    DOMAIN should be modified for yours
    NAMESERVER same here


    Now you are ready to try it.  Likely you will have to debug it, and I
have left in and installed many of my own monitoring messages.  Note, the
serial device should be unused, but as I recall the "RexxSerDev.Library"
opens it in shared mode.  However, this does NOT help me because my AmiTCP
CSLIP device driver requires exclusive access and will come up offline.
    Try clicking on the Icon to start it.  This Icon section wants to
change directory to "SYS:t", but you can change it to anything you want. I
also did not want a close gadget, because as long as AmiTCP is running, I
want a SHELL active.  I even left the Icon out on WorkBench.


    Included in this package is a nifty feature that I call re-boot
survivability.  Assuming "AmiTCP:bin" is in your path, then you can re-boot
your Amiga while the MODEM still has a carrier.  Needless to say, you lose
any connections you have made, and even some subtle things can work against
you.  I once re-booted while I had a "rlogin" session which was running a
mail program.  After reboot, I could not use the mail program until I used
"kill xxx" on that Unix process.
    To use this feature, open up a shell and type "startnet_pearl.cont".
Thats it.  Machine name, HOST and SLIP addresses, ENV variables and the
like should be setup already.
    Needless to say, my Amiga is pretty stable, and any re-booting that I
do, is likely to be my fault, not the programs I use or the hardware.
Sometimes my MODEM will lock up (or is it the HOST?), maybe due to power
problems and re-booting does not help.  I have to hangup and call again.


    Corrections or modifications can be sent to me at the address below.
Complements are always welcome, flames to should be redirected to /dev/null
or NIL: as you desire.


                             K. Raquel Sanborn
                             [e-mail]