Beijing Paradise BBS Backup

home *** CD-ROM | disk | FTP | other *** search

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / BBSDOOR2.ARJ / RAVIP102.ZIP / RAVIP.DOC < prev next >

Wrap

Text File | 1995-01-11 | 42.8 KB | 916 lines

──██████╗─────█████╗───██╗───██╗───██╗───██████╗─── ────██╔══██╗───██╔══██╗──██║───██║───██║───██╔══██╗──── ──────██████╔╝───███████║──██║───██║───██║───██████╔╝────── ────────██╔══██╗───██╔══██║──╚██╗ ██╔╝───██║───██╔═══╝───────── ──────────██║──██║───██║──██║───╚████╔╝────██║───██║─────────────── ─────────────╚═╝──╚═╝───╚═╝──╚═╝────╚═══╝─────╚═╝───╚═╝────────────────── RemoteAccess VIP Caller Detector - Version 1.02 - (c)Copyright 1994,1995 - Rand Nowell RaLin Enterprises Software "Putting Bits Together" (tm) Coding and Documentation by: Rand Nowell ┌─────────────────────────┐ │ Sysop Operations Manual │ └─────────────────────────┘ - Table Of Contents - Legal Stuff...........................1,2 Copyright Distribution Disclaimer Addendum System Requirements.....................2 What's it do?.........................2,3 Start-Up Commands.....................3,4 Multi-Node Systems....................4,5 Configuration...................5,6,7,8,9 Door Hangup Configuration............7,10 Double Checking Drops..................10 User Name Validation................10,11 The Message File.......................11 Message Macros......................11,12 Testing RAVIP..........................12 Registration...........................12 Alternate control files................13 /F Switch /D Switch Alternate Configuration Files..........13 Credits................................14 Support................................14 Author Contact......................14,15 RAVIP 1.02 Sysop's Operations Manual - (FreeWare) Page 1 ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ COPYRIGHT ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ RaVip, the program and documentation, are Copyrighted (C)1994,1995 work of Rand Nowell dba Ralin Enterprises. All rights are reserved. Copying, duplicating, selling or otherwise distributing this product except as noted in the Distribution Policy below is a violation of Federal Copyright Law. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ DISTRIBUTION ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ 1. Feel free to distribute the Shareware version of this program as often as you like to any interested parties. Distribution to Electronic Bulletin Boards is encouraged. 2. Please do not distribute this program without all the original related files such as documentation, readme files, registration forms etc. 3. Please distribute ONLY the original authenticated ZIP format file. 4. Please obtain our written permission before including the program with any "bundled" software packages. 5. Please do not accept payment for the program; a copying fee of $5.00 per diskette may be charged by a non-profit user-group. 6. Please do not alter the program or documentation in any way. 7. Individuals, groups, vendors or other software distribution companies which market diskettes containing shareware or test-drive evaluation programs, for profit, must obtain written permission from RaLin Enterprises prior to distribution. This will insure that you have the most current copy. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ *** DISCLAIMER *** ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ This program is supplied "as is" without warranty of any kind. The entire risk of using, and results from the use of, is assumed by you the user. You assume all costs of repair, servicing and corrections stemming from the use of this program. Rand Nowell and/or RaLin Enterprises, or any other associated company of the program author will not be held liable for any damages from the use of this program. No warranties are expressed or implied. ******************************************************************** To the original licensee of the REGISTERED version of the program, RaLin Enterprises DOES warrant that the program disk(s) on which the program is recorded, be free from defects in material and workmanship under normal use and service for a RAVIP 1.02 Sysop's Operations Manual - (FreeWare) Page 2 period of (90) ninety days from date of delivery as evidenced by your receipt. Our entire liability and your exclusive remedy shall be replacement of the defective disk not meeting the standards of this limited warranty. And in no case shall exceed the cost of reimbursement of monies paid for program registration. The Author is not obligated to produce further versions of this program. The Author also reserves the right to convert any SHAREWARE program, to that of COMMERCIAL status without prior notice. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Legal Addendum ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ Though no registration fee is required for RaVip, and you may use it and distribute it to whom you will, the program, documentation and any supporting files are copyrighted by the author. You do not OWN the program, you own the right to use it as you see fit. "Except", that your right does NOT include modifications, de-compiling, reverse engineering of the code etc. Please read FREEWARE.DOC ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ System Requirements ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ o DOS Version 3.3 or greater o RemoteAccess BBS System o Hudson or JAM message base o 150k Available memory at runtime o If you want a Netmail message, requires a Frontend Mailer ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ What's It Do? ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ RaVip will read your defined RA.LOG, and scans for the user name. This user name is compared against those listed in VIP.CTL. If the name is a match, a message is generated to the Sysop, telling you the caller logged on. Other information is also retrieved in this case, the following is checked, and noted: Did upload(s) Did download(s) Posted Local message Posted Echo message Dropped carrier Browsed files Read messages DOS external, Doors etc. EMSI connection established Log Off time The above information is rather generic, ie: it does not list RAVIP 1.02 Sysop's Operations Manual - (FreeWare) Page 3 each door run, file area browsed etc. It just gives you a general idea of what the user did during their visit. But the number of times the action was done is listed. When a VIP caller is detected, RaVip writes certain information to its logfile, RAVIP.LOG, in the same directory as RAVIP.EXE, or a directory+filename you define in RAVIP.CFG Some DOOR's allow hangup from within, this will cause RA to report Carrier lost.... RAVIP allows you to configure up to 10 strings that your Door(s) write to the log, if they do, and will ignore the dropped carrier if one is found, in the last RA session entries. This is a carry over from RADCD, its only value in RaVip is that the Dropped Carrier notations will not be made. Just a feature I left active. Instructions for configuring doors that do NOT write to the RA log are included. More is explained later. The log file is read "backwards", so even if it is HUGE, the minimum number of lines is read, stopping at the the first line entered for the callers session. Goes very quick! RAVIP would normally be called from the "After BBS" section of your batch file. The message is posted in the message area you specify in the config file. Both JAM and HUDSON bases are supported. If you run a mailer, you can optionally have RaVip send you a local Netmail message, rather than to the message base. The program also obtains the user name, the log entry date, and the time of the session, from the RA.LOG The User Name is displayed on the screen at run time, the time and date, along with the name are used when posting a message to the user. These, along with other strings may be included in the message you create by way of "Macro Characters", more on that later.... If you have used my program RADCD, RemoteAccess Dropped Carrier Detector, you will see many similarities between that program and RaVip. Much of the same code has been used, with some modifications. Also, this doc file is a modified version of the RADCD.DOC. Yeah..... I'm lazy.... <grin> ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Start Up Commands ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ RAVIP 1.02 Sysop's Operations Manual - (FreeWare) Page 4 The program requires a minimum of 120k available. 150k free memory is recommended. There are 7 startup switches/commands that may be used with RaVip. Switches must be preceded by either the minus(-) or slash(/) character, and must be separated by at least one space. -? Will display a short start up command help screen. -P Will invoke a 10 second pause at programs end, allowing you to read the screen display. ANY key press during the pause, will clear the pause and terminate the program. -L Will disable all logging of errors to RAVIP.LOG This has been included as a startup switch, rather than a config item, so you may TEST the program without creating a log file. -T Run RaVip in full use mode, but do NOT generate any message. -C Tell RaVip to use a different Config file. Full path and filename must be supplied. If none given then RaVip looks for RAVIP.CFG in the same directory as RAVIP.EXE -F Specify alternate control file to be read, instead of VIP.CTL This allows you to check specific users activities, without them being in your VIP file. The full path\filename should directly follow the "F" without any spaces. EXAMPLE: /FC:\TEMP\USER.CHK -D Essentially the same as /F, but puts RaVip in "Dual Mode". You can specify an alternate file, just as above, and RaVip will scan it right after checking the VIP.CTL file. You should NOT give the VIP.CTL name, it is ALWAYS scanned. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Multi-Node Systems ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ RaVip supports RA running in a multi-node setup, pertaining to the LOG file it scans, and also for the RAVIP.LOG. RaVip will read the CONFIG.RA file to get the log name. It first searches the current directory for CONFIG.RA, if not found it looks in the directory specified with the RA environment variable. So lets say you run a 3 line system, and for each load up of RA you set the TASK environment variable, we'll use set TASK=2 for our example. When you have the TASK variable set, you can use RA's "node" macro (*N) in the log name, ie: F:\RA\NODE*N\RA*N.LOG RAVIP 1.02 Sysop's Operations Manual - (FreeWare) Page 5 RaVip will scan the log name, and insert the current task number into the log name. Given our example TASK=2, the above would parse out to: F:\RA\NODE2\RA2.LOG - make sense?? This also applies to the RaVip logfile, in the config, you can insert the *N anywhere in the logfile name/location, and RaVip will substitute the current TASK number. The TASK variable is usually associated with those systems that run a Frontend Mailer. As RaVip does not require a mailer, and some Sysops use the NODE variable, support has been added for this also. RaVip will first look for the environment variable TASK, if not found it will try NODE, if neither is found, then the system is not running Multi-Node. If both happen to be set, the TASK variable WILL be used, NOT the NODE one. Remember, RaVip looks for a CONFIG.RA in the current directory FIRST, then looks at the environment specified directory. So if you use multiple CONFIG.RA files for different nodes, make sure you are in the proper NODE directory before RaVip is called! RaVip not only obtains your configured RA log file from CONFIG.RA, it also gets the location of your Message Base, which holds the User file. If you store your USERS.BBS and related Index files elsewhere, then we have a problem!! Doing this does not mean you should NOT configure the MsgBase location in RAVIP.CFG!! The location of the MsgBAse in CONFIG.RA is ONLY used to determine the location of the USERS.BBS file!! ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Configuration ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ The configuration file is a simple text file named RAVIP.CFG. It MUST reside in the same directory as RAVIP.EXE. A sample file has been included, you can edit it to reflect your system and preferred message base info etc., and use it. Comment lines may be included, by having the FIRST character, in column ONE be a semi-colon (;). These lines are ignored by RaVip. Currently, there are seven (17) items that can be configured for RaVip. The configuration is done with "keywords", and the format is KEYWORD=VALUE The equals sign (=) is the separator, and is used by RaVip to determine just where the VALUE starts, the VALUE being what you want used as the configuration item. There may be spaces between the KEYWORD, EQUALS, and VALUE if you need them for readability, myself, I always keep them together. Keywords may be in any or mixed case. RAVIP 1.02 Sysop's Operations Manual - (FreeWare) Page 6 Values, for the most part can be any case, but Sysop and System will be displayed AS THEY ARE LISTED. The "VALUES" for each NoDrop keyword, MUST be in the same case they will be found in the log, for them to work. KEYWORDS: MsgBase - If you want the message posted to the HUDSON message base, then this would be the full path to the Hudson Message Base, ie F:\RA\MSGBASE If you want it posted to a JAM message file, this should be the full path to the JAM message file: ie F:\JAM\GENERAL NO extension to the JAM filename, it is automatically handled. This document will not go into details about the JAM messaging system. BaseType- If the message is going to the HUDSON base, this should be "H", without the quotes. If going to JAM, it should be "J", again, no quotes. Board- Only required if posting to the HUDSON base, this should be the NUMBER of the message area, and it MUST be ZERO padded to 3 digits. Ex: Message Area #4 would be 004 Echo- If the message board you want the Sysop Notification written to, is an EchoMail area, make sure this KeyWord is defined. This will tell RaVip to handle the message properly, for possible EchoMail exporting by your tosser. Sysop- This is your Sysop Name. It does NOT need to match RA's, it is only used in conjunction with the message macros, so it can be anything you wish. BUT!!! Be advised, the name as configured here, is used in the message header TO: so if you use a a different name than is configured in your BBS/Reader etc. make sure that they will recognize this name. System- The name of your BBS. Again, it need not match that in CONFIG.RA. LogFile- You may specify, with this keyword, where RaVip will write the logged information. If not defined, the log will be written/maintained in the same directory as RaVip.EXE. The RA variable *N may be used anywhere in the log path\name, it will be substituted with the current TASK/NODE value. RAVIP 1.02 Sysop's Operations Manual - (FreeWare) Page 7 CopyCol- RaVip is hard-coded to start scanning for the user name in column #13 of the logfile. This is correct for the COMPACT log format specified in RACONFIG. If you use a different format, you should load a copy of the log into a Text Editor, and count over, from column one, to the FIRST character of the user name. This column number is what you will specify as the CopyCol value. ExpandedLog- If you are using the EXPANDED log format, you should include the line: ExpandedLog This will tell RaVip to scan for the Date and Time of a Drop differently than for the default Compact log style. It also determines how RaVip knows it has read all the current session information, as the line containing the dashes is not written to an expanded format log. You do NOT need any config keyword for Compact format, as it is the default, if ExpandedLog is not used. NoDrop- This config item is supplied with RADCD, while not really required in RAVIP, I have left it available. All it will do is keep RaVip from noting that your caller dropped carrier. No other dropped carrier action is taken at all. Specifies a string (case sensitive) that RaVip should watch for, to reverse the Carrier lost action, if the carrier was correctly dropped from within a Door Program. You may configure up to 10 strings, each one preceded by the keyword NoDrop. Each Keyword/Value on its own line. The string may be up to 25 characters in length. Any more will not be stored. The 25 character length allows you to configure sec levels to ignore Dropped Carrier for, ie: NoDrop=Security level 50 NOTE!! RaVip now fully supports InterZone Netmail. If you need to have the Sysop Notification sent to another Node/Zone etc, it may now be done accurately. Net- This tells RaVip to generate a Netmail message in the defined Mail Directory. If you do NOT want netmail, then do not activate this item. Example: Net Crash/Kill - For Netmail, when sending OUT of your system. CRASH sets Crash priority on the message. KILL sets the Kill/Sent flag. By default, if not defined, messages are NOT Crash and RAVIP 1.02 Sysop's Operations Manual - (FreeWare) Page 8 NOT Kill/Sent Do not use these if you are having the netmail message sent to YOU on YOUR system, ie: Locally. Semaphore- If you run a multi-node system and RaVip might be called from another node, while your mailer is running on another, you can give a path+filename here, and RaVip will modify the time/date (re-write) it, so your mailer will scan for new mail. This is mainly for Netmail support. For FrontDoor, this might be C:\FD\FDRESCAN.NOW FromNode- Here you give your Fidonet (or other) Netmail address. If you have specified "Net", then be sure this, and MailPath are defined correctly. Points are supported. Example: FromNode=1:161/710 NOTE: Actually, you should ALWAYS define your own Node Address here, as it is ALSO used for EchoMail. ToNode- If you are having the message generated only for use on your system, then this should be the same as that for FromNode. But if you need the message sent to another system, you can give its address here. MsgTo- When sending this message, you may want it addressed to a Co-Sysop, whether he be on your system, or at another address. If so, supply their name here. If MsgTo is not supplied with a name, the message is addressed to the Sysop name given earlier. MailPath- Where the *.MSG should be written, ie: where your mailer will look for these messages. Currently the TASK/NODE variables are NOT supported. Example: MailPath=E:\FD\MAIL Some NOTES on configuration: 1) You may NOT set Echo and Net together. If both are set, RaVip aborts with an error message. 2) You can, and should define ALL message options, ie: Message Board, Board Number, To/From Nodes etc. Which are used, is determined by the NET and ECHO keywords. Having both setups defined, makes it a simple QUICK matter to instantly change from having the message going to the messagebase, or to a Netmail .MSG. All you have to do is comment out one keyword, and un-comment the other. RAVIP 1.02 Sysop's Operations Manual - (FreeWare) Page 9 3) The generated message is ALWAYS from the Program, ie: From: RaVip 1.02 4) Comments may be inserted in the config file, any line with a semi-colon (;) in column ONE, of the line is ignored. You can use the ; to comment out a keyword also. 5) You can have multiple configurations. An alternate can be used via the -C switch. But you should configure a "STANDARD" format, and save it as RAVIP.CFG in the EXE's directory. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Door Hangup Configuration ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ NOTE on NoDrop. (READ THIS.....) Some doors that allow Hanging up, or Quitting the BBS, do NOT write to the RA.LOG, in fact probably most, do not. You can still work with these, all you need to do, is in the batch file that runs the door, after the command to run the door, insert a line that will ECHO a line of text to the RA.LOG Example: Suppose you run a door called FileVu. In your batch file, you might have, FILEVU C:\RA\DORINFO1.DEF as the command to run the program. All you need to do is insert a line such as: echo User ran FileVu >> C:\RA\RA.LOG right after the program call, when the program exits, it returns to the batch file, and this line is processed. Then in RAVIP.CFG, include a line that looks like: NoDrop=FileVu Now, when RaVip sees the Carrier lost line in RA.LOG, it sets the Dropped Carrier flag, but as soon as it finds your created value, "FileVu" it turns OFF the flag. Another use for the NoDrop, is if you want callers with a certain security level to not receive messages for dropping carrier..... RA writes a line "Security level #####," to the log file, where ##### can be any defined sec level up to the maximum allowed. So if you want to allow callers with sec level 50 to drop carrier, simply add a line such as NoDrop=Security level 50 to the RaVip.CFG You can, if you wish, insert a username here also, it should work, but has NOT been tested. Of course, an even simpler method is to use the RA Menu Command, Type 47 to generate a log entry, either just before or after the Door Command is given. It involves a little more menu work, but may be more desirable for some. Two important things to remember, the search for a value is done case SENSITIVE, it MUST match exactly what is written to the log, RAVIP 1.02 Sysop's Operations Manual - (FreeWare) Page 10 and listed in the config file. The other is, when you create your own, as in our example, you use the DOUBLE > character ">>" after the string to Echo. This is the command to DOS, to APPEND the line to the log file. If you forget, you will OVER-WRITE your RA.LOG Also, some doors do not allow a caller to hangup, but DO allow the Sysop to hangup on the user. These should also be configured, if you think you may hangup on the user in the door. Another note, when RaVip detects dropped carrier, it writes to the screen, ! User dropped carrier If it finds an "Authorized Door hangup string" it will then display ~ Authorized Door Hangup : "value", where value is the NoDrop string you supplied, and RaVip found. If it all sounds confusing, that's because it can be so!! <smile> Some experimentation on your part will get you up and running smoothly in no time. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Double Checking Drops ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ RaVip insures that the User Name in the logfile is not garbage, as can happen with bad EMSI calls or a user sending escape sequences trying to crash the system. If carrier is lost, but the user name does not contain an Alpha character starting the name, its considered an incomplete call, and no message is posted. When you run a frontend mailer, the connection can sometimes be broken during the time the mailer is loading RA. In this case there is no name for RaVip to check, usually there will only be two lines in the log, the first line RA writes, and the second, Lost carrier. So RaVip counts the important lines read from the log, and if this count is NOT greater than 3, then RaVip displays the message: "BLAM!! Never even got started..." and also logs an appropriate line to its log file. This is considered a connection that never got established. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ User Name Validation ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ Along with checking for garbage strings, and empty names, RaVip will actually "validate" the username against the user index file. Say a user does not enter a complete name the first time, but does on the second attempt. The first name will be invalid, RAVIP 1.02 Sysop's Operations Manual - (FreeWare) Page 11 and so not used. Once the name has been validated against the User index file, it is the one used. While the program is running, all names found are displayed, even the ones not found in index file, misspellings etc..... If the name does not exist, it has the message "NOT IN USER FILE" displayed after the name. The next release may do a bit towards eliminating the display of names if they are not validated. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ The Message File ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ Using your favorite Ascii Text Editor, you can create the message that will be sent to the user who has dropped carrier. It MUST be named RAVIP.MSG, and MUST reside in the same directory as RAVIP.EXE NOTE: What =you= create, is the text that is written at the beginning of the message to you. The callers activity is added to your message. See the sample RAVIP.MSG included to give you an idea of the suggested format. You can make use of several macros to insert text into the message when it is posted. A sample RAVIP.MSG has been provided. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Message Macros ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ The most important thing to remember about using the macros, is that each one MUST be preceded by the at character (@). If you wish to use a literal @ in the message text, you must precede it with another @. So the line "Call me @ 223-4455" must be written as "Call me @@ 223-4455" If you use an incorrect macro, or use the @ alone, the "macro" will be replaced with "<MACRO ERROR @??????>" where ???? is replaced with the problem character(s). If you use our RASIS program, then you should be familiar with how the message macros work, they are done in the exact same manner. There are currently eight (8) macros available for you to use: @F - Users first name only @L - Users last name only @N - Users full name RAVIP 1.02 Sysop's Operations Manual - (FreeWare) Page 12 @D - Log entry date @T - Log entry time The values for the above 5 macros are taken from the RA log file. @B - The BBS name @S - The Sysop name These 2 are taken from the RAVIP.CFG file. @C - Name of control file used for user check Supplied on the command line with the /D "Dual Mode" switch, or /F Alternate File switch, or VIP.CTL if running in normal mode. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Testing RaVip ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ You can add your name to the VIP.CTL file, or use the Alternate File switch /F, supplying a filename of the alternate file, that contains your name in it. See Startup Commands -> /F above for syntax and info. Then log on locally and perform a few normal user activities. Then run RaVip and see what happens. Another option to a local logon, is to just edit the RA.LOG, and insert your name in place of the last caller. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Registration ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ RaVip is fully functional as you have received it. If you find it a useful tool, I would request that you send me $5.00 or more though. This will show me that the program is being found useful, help defray the cost of developing utilities such as RaVip, and induce me to continue development of RaVip and other RA utilities. Please read FREEWARE.DOC If you simply cannot afford even $5.00, send me what you can, if you can send any at all. And if you're just plain destitute, at least fill out the Reg Form included, and send it to me, just so I know where the program is going etc. I think you will find RaVip worth a little donation to further development. RAVIP 1.02 Sysop's Operations Manual - (FreeWare) Page 13 ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Alternate Control Files ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ By using the /F or /D switches, and supplying a path+filename, you can have RaVip either use a file "other" than VIP.CTL, or, scan a file in "addition" to VIP.CTL The /F gives a control file to scan INSTEAD of VIP.CTL The /D gives a file to scan WITH VIP.CTL. This file is scanned AFTER VIP.CTL ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Alternate Configurations ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ You can setup additional configuration files, for the purpose of totally changing the way RaVip handles the message generation. You might have one setup to be sent to you, as local netmail. Another to you as EchoMail, and yet another to go to a co-Sysop on another system at another address. While modifying RAVIP.CFG is fairly easy, some may find it more convinient to have different setups in different files, then by supplying that filename with the proper command line switch, cause it to ne used. RAVIP -CF:\RA\VIPECHO.CFG would cause RaVip to use the VIPECHO.CFG file in the F:\RA directory, rather than the default RAVIP.CFG in the RAVIP directory. You might have several, like: VIPECHO.CFG VIPNET.CFG VIPCOSYS.CFG VIP2PNT.CFG etc. etc. RAVIP 1.02 Sysop's Operations Manual - (FreeWare) Page 14 ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Credits ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ Special Thanks to Eric Staufer of The Concession Stand, for initial testing of RaVip 1.0 - Big Help! RemoteAccess - Andrew Milner, Wantree Development. JAM(mbp) - Copyright 1993 Joaquim Homrighausen, Andrew Milner, Mats Birch, Mats Wallin. ALL RIGHTS RESERVED. RaVip uses modified message base code from Mark May, Mythical Kingdom Software. RaVip is programmed under TP 7.0, Borland International Any other products mentioned are Copyrighted by their respective authors. Some of the key folks in Beta Bashing RaVip 1.01: Donald Hinkle, Bob DaCastello, John Coleman.... Thank's Guys!! ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Support ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ Though its Free, I fully support it. Bug reports are appreciated, feature requests are usually implemented. If you send a netmail message with question/suggestion or bug, you will need to POLL for your reply. It would help, if you would TELL me if you wish a reply. If you do, it will be placed on HOLD for your call. If you do not pick it up within a week, it will be sent ROUTED. I have been replying to many questions via CRASH mail, I cannot afford to continue this practice, the program =IS= free after all, and does NOT pay for these LD return messages. <grin> Of course, I could make registration required, then I will continue crash replies.... <chuckle> ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ Author Contact ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘ I hope you find RaVip useful, and would appreciate hearing from you if you do. I can be reached at the following: Echo Areas: Fidonet - RA_UTIL, RA_SUPPORT, SHAREWAR, DOORS, PASCAL XeroNet - XN-RALIN, XN-RA Netmail - FIDO= 1:161/710, XERO= 131:5100/100;101 GASPNET= 8:86/260 RAVIP 1.02 Sysop's Operations Manual - (FreeWare) Page 15 BBS - 1-510-226-7731 Voice - 1-510-651-6177 Internet - rand.nowell@ralin.damar.com NOTE: We may soon have our own DOMAIN for the internet, "RALIN.COM" when this happens, notification will be posted in the Echos. You might also try the following: rand.nowell@ralin.intellisoft.com This address is currently where we are setting up and testing our local UUCP feed, and there are bugs to be worked out. So it may be late arriving.... Mail - Rand Nowell RaLin Enterprises 40728 Sundale Dr. Fremont, Ca. 94538-3341 =OR= 4641 Wheeler Dr. Fremont, Ca. 94538-1937 The system is located at the new Wheeler Dr. address, but I still receive mail at the Sundale Dr. address also. ┌─────────────────────────────────────────────────────────────────────────────┐ │≡≡≡ eof RAVIP.DOC ≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡≡│ └─────────────────────────────────────────────────────────────────────────────┘