home *** CD-ROM | disk | FTP | other *** search
- ROBOCOMM
-
- ROBOCOMM.SCR is a script for ROBOCOMM users to call FINET NETHUB
- Follow the instructions at the top and delete them before running it.
-
-
- TELIX
- FINET.SLT is a script for TELIX. This file give more information should
- you wish to add to that script, and about using pcrelay.
-
-
- MAIL SCRIPT INFORMATION FOR TELIX AND GENERIC
-
- Here is sample batch file to use the script:
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- rem this is a sample batch file which could be used, renaming directory
- rem names and the like, to run the telix script. PCRELAY would be
- rem replaced with whatever name you're using.... and drive letters also.
- rem this is only one of many ways to do it. I do it several ways...
- rem you may wish to call PCRELAY directory FINET
-
-
- @echo off
- j:
- cd j:\PCRELAY
- rem this backs up the lastread.net file which PCRELAY sometimes corrupts
- rem if you don't have a backup tape or disk, this will save need to
- rem reconfigure all the conferences over again
- copy lastread.net lastread.bac
- copy lastread.bac j:\pcrelay\save\lastread.2
- rem this exports new messages from your bbs to pcrelay transfers....
- EXPORT.EXE
- c:
- cd C:\pcrtelix
- rem this is your net-specific Telix directory
- rem this is where you might save the relay packet EXPORT created
- rem although the provided Telix scripts backs this up
- copy node_id.rly j:\pcrelay\save\out.rly
- rem this is where telix is run with script.
- telix SFINET02
- copy IN.RLY g:\pcrelay
- rem my script backs this up, but this is how from batch file
- j:
- cd j:\PCRELAY
- rem import messages from new IN.RLY to message bases
- IMPORT.EXE
- e:
- cd\rbbs
- rem this is normal bbs directory ready to revoke bbs via batch file
- rem you can remove the remark lines if you follow batch files easily
-
-
- --------------------------------------------------------------------
-
- GENERAL SCRIPT INFORMATION:
- --------------------------
- FINET.SLT is the provided script for TELIX, though you can use Qmodem,
- Robocomm, etc. This script gives you a choice of using external dsz
- zmodem (a better way), or the internal Telix zmodem. The default is the
- RBBS turbo logon, which stacks firstname;lastname;password, etc....
- on one fast logon line. However, if you wish to change passwords, you
- will need to re-edit the script and recompile. The other way, listed in
- the script answers each RBBS prompt one at a time. This is a versatile
- method and uses the password in the Telix dialing directory. This makes
- changing the password easy without recompiling the script. However, the
- login time is a bit longer.
-
- You need to modify the Telix dialing directory entry number and node_id
- name anyway, you have your choice. Both scripts will back up the
- node_id.rly and IN.RLY packets. In fact, several generations, one from
- each mail run, of IN.RLY files are kept for safety. Timers are running
- for make sure that you are not kept on line should something go wrong;
- independent timers check login time, upload and download times, and for
- carrier.
-
- FINET NETHUB only provides the connection; while we try to help with
- scripts, that is the relaying sysop's responsibility. Feel free to
- modify any of these to customize them for your application. Another node
- here uses robocomm with good result.
-
-
- sequence for script is basically:
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
- (from batch file you've run pcrelay "EXPORT")
-
- 1 Dial and log in
- 1a you might wish to send an <enter> keystroke in case the opening
- screen is unusally long and sends a "continue" more prompt.
- 2 at "RST name?" prompt send turbo login sequence (including ";"):
- firstname;lastname;password;!;d;fihub;/G^M
- (where ^M is the <enter> or cr/lf character. this lets you login fast
- using one line and command and log off after done!)
- 3 at the "fe64" or "*" zmodem prompt upload your node_id.rly packet
- 4 wait for download packet preparation or download zmodem prompt:
- a "*" again or "dd38" and receive zmodem IN.RLY packet
- 5 Door drops DTR and logs you off, you execute local "hangup"
- 6 back up in.rly packet in comm dir and lastread.net file in pcrelay!
- 7 resume pcrelay batch file and issue "IMPORT" command.
-
- ------------------------------------------------------------------------
-
- Notes on TELIX script to dial into Freedom Infonet RBBS
- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-
- If your setup (rare) does not delete in.rly before calling out, you can
- do this from the batch file or the script. You can execute DOS commands
- from within the script thus:
-
- The line to add early in the main script before dialing out! is
- observe case:
-
- dos("if exist c:\telix\IN.RLY del c:\telix\IN.RLY",0);
-
- however, PCRELAY when successful, always deletes IN.RLY after export.
- This would be in case for some reason PCRELAY failed....
-
- YOU CAN ALSO ADD SIMILAR LINES TO RENAME IN.RLY TO A BACKUP FILE IN.1
-
-
- dos("if exist c:\telix\IN.RLY rename IN.RLY in.1",0);
-
- Script source code needs to be compiled, since SALT is a language.
- With Telix' CS.EXE in your path or directory, type
-
- CS scriptname
-
- If the script name is finet02.slt, the program will create finet2.slc:
-
- CS FINET
-
- The ".SLT extension is implicit, and FINET02.SLC will be created.
-
- ----------------------------------------------------------------------
- Some advanced script options follow....
-
-
- Specifying handshakes and other DSZ parameters in finet scripts
- (a bit more complex but smoother option for the script.....)
- ______________________________________________
-
-
- The default script specifies DSZ as letter "D" in external protocol
- options in TELIX configuration menu. If you wish to name the path and
- name explicitly, create a "Protocol" string variable as below:
-
- str Protocol[60] = "C:\TELIX\DSZ.COM" ; // Complete path to DSZ
-
- You can also specifiy complete dsz parameters and handshakes as well as
- the directory paths by explicitly spelling out the "send" or "receive"
- command. Do this by creating the followsing two variables:
-
- str Send_Command[64] = " port 1 ha slow sz -m C:\TELIX\nodeid.RLY";
- str Recv_Command[64] = " port 1 ha slow rz -m C:\TELIX\IN.RLY";
-
- The following two variables specify external dsz rather than internal:
-
- int SendStatus = 1; // Used for send R/C from DSZ
- int RecvStatus = 1; // Used for receive R/C from DSZ
-
- The following would replace these two code snippets from finet01/02.slt
-
- SendStatus = run( Protocol , Send_Command , 0 ) ;
- // send('Z', "nodeid.RLY"); //this would be internal Telix zmodem
-
- would replace the marked line and node_path variable:
-
- status_wind("Sending Packet",10);
- --------> if (protocol == "D" ) send('D',node_path);
- else if (protocol == "Z") send('Z',node_path);
- return;
-
- and this:
-
- delay(2);
- RecvStatus = run( Protocol , Recv_command , 0 );
- //receive('Z', "IN.RLY"); this would be internal Telix zmodem
-
- Would replace the marked line and node_path variable for receive
-
- {
- status_wind("Receiving Packet",10);
- --------> if (protocol == "D" ) receive('D',"");
- else if (protocol == "Z") receive('Z',"");
- return;
- }
-
-
- You can hard-code the parameters as well for send or receive, e.g.:
-
- run( "c:\telix\dsz.com", "port 1 ha on sz c:\telix\node_id.rly", 0);
-
- and use in conjunction with "IF" statements, or break up the file names
- and file paths into separate variables and combine the strings......
-
- Hope this helps for the advanced SALT script programmers out there to
- make this script even more powerful!
-
-
-
-
- <end of file>
-