home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.wwiv.com
/
ftp.wwiv.com.zip
/
ftp.wwiv.com
/
pub
/
BBS
/
RAFDLC17.ZIP
/
FD2RALC.DOC
< prev
next >
Wrap
Text File
|
1995-05-31
|
5KB
|
122 lines
FrontDoor Lastcall to RemoteAccess Lastcall
FD2RALC.EXE - Version 1.07
==========================================================================
Startup Commands:
Parameters must be proceeded by either a Minus(-) or a slash(/) and must
be seperated by at least one space.
Switches are: P - 10 second pause at program end
B - Specify connect speed to be written
D - Debug, certian path/filenames will be written to
the FD2RALC.ERR file, for verification.
V - View the caller dat file !CALL.DAT
? - Display the Help screen
Examples:
FD2RALC /P will invoke the 10 sec pause at program end.
FD2RALC -b14400 will cause 14400 to be used as the connect speed for
the mail call entry.
NOTE!! There must be NO space between the "b" and the
baud speed.
FD2RALC -p /b28000 will invoke the pause, and set the baud speed to
28000
FD2RALC -v Will display the !CALL.DAT, listing the nodes who have
called, and how many times.
==========================================================================
This program is a take off of RA2FDLC, which stores the last BBS
caller in the FD lastcall file.
It is being distributed as FreeWare.
But please read the included FREEWARE.DOC!!
No warranties are expressed or implied. You use it at your own risk.
FD2RALC.EXE is (c)Copyright 1994,95 Rand Nowell - RaLin Enterprises
FD2RALC reads the FD information about the last INBOUND mail call to your
system, and inserts this in the RA LASTCALL.BBS, so your users can see just
how busy your system "really" is.
Place FD2RALC in a path directory, or, when you call it, supply the
full path/name of the file.
The file !CALL.DAT is created, and FD2RALC expects to find it, in the
same directory as FD2RALC.
You should place a call to FD2RALC in your mailer batch file, so it is
called whenever you receive mail pkts. If you have FD set to exit on netmail
receipt also, FD2RALC will be called as if you received a pkt.
If you call a system, and receive mail from them, this will be considered
an outbound call by FD2RALC, and the sending node will NOT be added to
the LASTCALL.BBS
If you are running Multi-Line RA, and maintaining seperate LASTCALL.BBS
files, you will want to be in the NODE directory when you call FD2RALC.
Unless you have the *N variable in the RA System Directory field, which
is replaced with the current TASK number. The NODE variable is also
supported, if a TASK enviornment variable is not found, a NODE one will be
checked for. If neither is found, then the system is considered to be
running single line.
Please see notes in CHANGES.107 about the NODE and TASK variable.
FD2RALC inserts the calling system Name, Handle, Node and call time start/end
into RA's LASTCALL.BBS The LogOn time is retrived from FD, the LogOff time is
the time the program runs. The baud defaults to 9600, unless you have
supplied a BaudRate on the command line.
The node defaults to 1, unless a current TASK or NODE variable has been set.
Times called, is read from the !CALL.DAT file, and inserted.
FD2RALC will modify the RA LASTCALL.BBS, *if* there is an
"incomming" mail call to insert.
The location of the LASTCALL.BBS is obtained from CONFIG.RA -> System
Directory. This directory name can have the RA NODE variable, *N, in it
if wished, and will be replaced by the current NODE value.
The program maintains a small data file, FD2RALC.DAT to help in eliminating
duplicate entries.
FD2RALC also maintains a semaphore file named FD2RALC.SEM
When the program runs it does this:
1. Creates it if missing, =OR= Updates the date/time of the file.
2. Compares date/day of semaphore and lastcall file.
3. If the lastcall file is from the previous day, it is
deleted/re-created, then the new call is placed in it.
Important & Debug information, as well as errors are written to
FD2RALC.LOG, which is created/maintained in the EXE directory.
All support files, data, semaphore, are expected to be in the same directory
as the exe file. Do not place them elsewhere.
Rand Nowell
RaLin Enterprises
40728 Sundale Dr.
Fremont, Ca. 94538-3341 USA
=OR=
4641 Wheeler Dr.
Fremont, Ca. 94538-1937 USA
The RaLin Software BBS
Voice : 510-651-6177
BBS : 510-226-7731
Fido : 1:215/710
Internet : rand.nowell@ralin.damar.com
CREDITS:
FrontDoor - JoHo, Absolute Solutions
RemoteAccess - Andrew Milner, Wantree Development
Compiled under TP 7.0 - Borland International