home *** CD-ROM | disk | FTP | other *** search
Text File | 1993-07-01 | 40.1 KB | 1,123 lines |
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- R E M O T E A C C E S S
-
-
- L O G R E P O R T I N G P R O G R A M
-
-
- Sep. 1990 - 1993
-
-
- REMOTLOG
-
- ////// ///// / / /////// /////// / /////// ///////
- / / / / / // / / / / / / /
- ////// /// / / / / / / / / / / ///
- / / / / / / / / / / / / /
- / / ///// / / /////// / /////// /////// ///////
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- REMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOG
- REMOTLOG V 2.00 9D 1
-
-
-
-
-
-
- The Program - REMOTLOG
-
-
- I developed Remotlog a little after the announcement of RA was
- made and I endeavored to switch from QuickBBS. There was
- something missing, I could no longer use all my QBBS utilities.
- After exhaustive efforts of trying to get the implementation of
- my old program by its author, I decided that it was time to do
- some coding.
-
- Here we have the finished product. A full fledged RA log reporting
- program, and now Bulletins and statistics generator.
-
- (RA) Remote Access is the registered product of Continental Software.
-
- At present this program will function with RA version 2.xx. Do
- not attempt to use this program with any other software except RA
- because it uses the file MESSAGES.RA, FILES.RA, CONFIG.RA,
- USERS.BBS, and TIMELOG.BBS. If it cannot find these files the
- program will abort in error.
-
- The screens provided by this program are as the author thought
- you the sysops would like to see them. If you feel the
- information is too much or that there is not enough, or would
- even like to see some of the information moved from one location
- to another part of the page or a totaly different screen. Please
- do not hesitate to let the author know.
-
- TERMS OF USAGE
-
- BY USING THIS SOFTWARE YOU AGREE TO THE FOLLOWING
-
- 1. REMOTLOG is distributed under the shareware concept. This means
- that you are free to distribute this program to anyone you like,
- as long as you don't charge for it, modify the program in any
- way, or add files to the original distribution archive.
-
- 2. No guarantees are made that this software will work with your
- system and/or configuration. Additionally, no guarantees are
- provided that the data read from and/or written to your
- RemoteAccess files will be accurate. The user assumes full
- responsibility for making backup copies of all important data
- files. No guarantees are made that this software may not damage
- any files that it may or may not be exposed to.
-
- 3. If this software is released in a Beta test format, this means that
- the software is not fully tested, and debugged. Use of this
- software in Beta format is at your own risk.
-
-
-
-
-
-
-
-
-
-
- REMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOG
- REMOTLOG V 2.00 9D 2
-
-
-
-
-
-
- LICENSE AGREEMENT
-
- OKC., computers has taken every precaution to ensure that no harm
- or damage will occur on systems running the REMOTLOG log
- processor and statistics generator. However, we cannot be held
- responsible for any damages or other losses suffered as a result
- of running the REMOTLOG software on your system. The user
- assumes full responsibility for the proper use of this program,
- whether damage occurs as a fault of operator error or software
- error. NO WARRANTIES ARE IMPLIED OR EXPRESSLY STATED.
-
- The REMOTLOG program is fully copyrighted, and is not, nor will
- it be in the Public Domain. This program is not FREEWARE. It is
- distributed under the SHAREWARE concept. Users are allowed to
- try this program for 30 days, you may use the program to the
- capacity allowed for a non registered version. If the software
- does not meet your needs, and/or you do not plan on registering
- it after the 30 day trial period, you are to cease usage of the
- program and remove the installed copy from your system.
- Continued use after the 30 day trial period will require that you
- pay the full registration fee.
-
- REGISTERED USERS LICENSE
-
- Registered users of REMOTLOG are granted an unlimited license to
- use the product registered, provided the following:
-
- Registration fees are NOT refundable. That is the purpose of the
- evaluation period.
-
- Registration codes and Key files are not transferable to other
- parties.
-
- Unofficial software patches must not be applied, and all
- copyright notices in the documentation and supporting files are
- not to be altered.
-
- BACKUP copies may be kept of all registered versions of this
- software for archive purposes only.
-
- Use of a registered copy is limited to one machine at a time.
- Usage on more than one machine requires registration for each
- machine in use.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- REMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOG
- REMOTLOG V 2.00 9D 3
-
-
-
-
-
-
- INSTALLATION
-
- REMOTLOG comes in a distribution archive that should tell you it was
- recieved or downloaded from OPA-LOCKA Tower BBS. The contents of the
- archive should be.
-
- REMOTLOG.EXE - The Executable file
- REMOTLOG.DOC - This file (Documentation)
- REMOTLOG.KEY - The key file required to run the program
- REMOTLOG.CFG - Configuration File
- REMOTLOG.### - ### = ASC/ANS/AVT sample statistics report file.
- RLOG_USG.### - " " sample bulletin
- RLOG_TME.### - " " sample bulletin
- BETA.DOC - Changes made before releases.
- UPLOAD.TXT - Sample text file
- NEWUSER.TXT - Sample text file
- DROPCMSS.TXT - Sample text file
-
- 1. COPY all the files to the same directory and Read the documentation
- completely.
- 2. EDIT the configuration file *.CFG and make the necessary changes.
- 3. RUN REMOTLOG from the directory that it was placed in.
-
- SYSTEM REQUIREMENTS
-
- IBM PC, or compatible.
- Enough drive space
- display of your choosing.
- 300KB of memory is recommended. The more the merrier. May
- function with less.
-
- COMMAND LINE OPTIONS
-
- REMOTLOG [TEST] [/C] [/N##] [FILENAME.EXT]
-
- [TEST] - REMOTLOG will generate only the Bulletin Screens and info.
- [/C] - Will cause REMOTLOG to dump the config info to Log File.
- [/N##] - Use the option to give remotlog a node number.
- See: LogFile, LineInUse etc. If specified you may use
- the *N anywhere in the configuration file and Remotlog
- will substitute the ## given for the *N. You may use
- it in directory name or even filenames. When used do
- not specify a lineInUse variable or either the two
- numbers match or you use the *N for the LINEINUSE as
- well. This option may allow you to use only one
- configuration file for your multi line system. Just
- call REMOTLOG and tell it which line to process.
- [FILENAME.EXT]
- - Specify the config file name on the command line.
- Any file name is valid.
-
-
-
-
-
-
-
-
- REMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOG
- REMOTLOG V 2.00 9D 4
-
-
-
-
-
-
- Configuration of REMOTLOG
-
- REGISTRATION INFORMATION
-
- In this section you will find the BOARDNAME, SYSOPNAME, and REGISTKEY
- options. These options are only one part of the registration system
- to REMOTLOG. It also requires a key file to be present and properly
- coded for a registered copy of the program to work as such. The key
- file called REMOTLOG.KEY is required even if you are not a registered
- user. When you are registered. You will be sent a new key file in
- addition to the information supplied below so that you may have a
- registered copy of REMOTLOG.
-
- 1. BOARDNAME Opa-Locka Tower
-
- Boardname will be as you want it to appear on the screens
- when registration is displayed. Maximum number of
- characters that you may use are approximately 20 for the
- board name, you can use more but only 20 will be displayed.
- It is used to identify the name of the registered system.
-
- 2. SYSOPNAME Orland Carter
-
- This should be quite apparent. However this is keyword lets
- remotlog know who is the sysop that it is registered to. It
- is advisable to use the same name that you have on the
- system. REMOTLOG at times may use this name to post a
- message to the sysop and not the one located in the
- CONFIG.RA file. Maximum length of the sysop name is about
- 20 characters, you can have more however only 20 will be
- displayed.
-
- 3. REGISTKEY 00000000000000000000
-
- Registkey is where you place the key number that you will be
- given to indicate that you have properly registered a copy of
- this program. It has no preassigned length. Or numbers.
- Whether you are registered or not you will be required to make
- use of the BOARDNAME and SYSOPNAME options. If you change
- registkey it will not make a difference to your unregistered
- status.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- REMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOG
- REMOTLOG V 2.00 9D 5
-
-
-
-
-
-
- CONFIGURATION - FILES SECTION
-
- 4. LOGFILE
- This entry is required. It lets REMOTLOG know the name of
- the BBS log file that it needs to process. You are also
- able to give it a path to identify where the file is
- located. This option will default to simply SYSTEM.LOG in
- the current directory if no configuration file is specified.
- LOGFILE SYSTEM.LOG or LOGFILE C:\LINE*N\LINE*N.LOG
-
- 5. LINEINUSE
- This entry is not required if running single a line system,
- However if you are running a Multi-Line system and would
- like to delete or zip each nodes log file then this is
- needed. LINEINUSE ##. Where ## is the line being processed
- by this configuration file. ## range is 1..99
- This option is not required if the [/N##] option is
- specified on the command line.
- LineInUse 1 or LineInUse *N
-
- 6. FDLOGFILE
- This option is required if you want REMOTLOG to process the
- file transfers, file requests, and other miscellaneous
- information. The DEFAULT is NOFDLOGFILE, this option tells
- REMOTLOG that you have no Front End Mailer logfile
- compatible with the Frontdoor logging method. The other
- option is FDLOGFILE [Path + Filename] of the Front End
- Mailers log file, remember it must be compatible with
- FrontDoor's log style.
- FDLogFile C:\Fd\Fd.Log or FDLogFile C:\FD\FD*N\FD*N.LOG
-
- 7. OUTPUTFILE
- This option is a required option. It lets REMOTLOG know
- what [path + filename] the statistical output of the program
- should be placed in. REMOTLOG will generate both the *.ANS
- & *.ASC versions. This file name currently only applies to
- the statistical information files that remotlog produces,
- and not to the Bulletin information files. DEFAULT filename
- is REMOTLOG. The bulletins will also use this directory to
- store its output files default filename RLOG_???.Asc/Ans.
- OUTPUTFILE C:\Ra\Txt\Remotlog
-
- 8. NOMULTILINE
- This option is required. It tells the program whether or not you
- wish the optional page of Multiline usage to be displayed. This
- multiline usage is a breakdown of the number of calls per line in
- a system with more than one node. This option will either report
- it or not report it. In either case the statistics will still be
- stored if the option is not selected. If at some future point in
- time you wish to view this section just simply activate it by
- specifying MULTILINE and it will let you know your multiline
- usage up to that point. DEFAULT : NOMULTILINE
- NoMultiLine
-
-
-
-
-
- REMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOG
- REMOTLOG V 2.00 9D 6
-
-
-
-
-
-
- 9. COMPACT
- This option is required. It tells the program what type of log
- file you are using. Wether FD/COMPACT [Front Door type] or
- OPUS/EXPANDED. DEFAULT FD / COMPACT. This particular selection
- applies ONLY to the BBS logfile. It is assumed that the Front
- End Mailer of choice for this program logs in a Front Door
- compatible format. There are actually four options for this
- section FD, COMPACT both meaning the same thing and also OPUS,
- EXPANDED both meaning the same as well. This is to smooth the
- change that was made in RA 1.1x with the type of logfile
- selection. Some sysops were getting confused.
-
- COMPACT
-
- [LOGFILE - DELETING/SHRINKING/ARCHIVING - SUBSECTION]
-
- This portion of the logfile determines how REMOTLOG will handle the
- size reduction of your logfiles. The choices are relatively simple.
- DELETE the files after checking them. SHRINK the files by ## of days
- after checking them. And also ZIP the logfiles into an archive after
- checking them.
-
- 10. DELETELOG
- This option is not required. It activates or Deactivates
- the BBS logfile deleting option. The DEFAULT is that the
- logfile will be deleted every 10 days. The two options are
- DELETELOG ## (Where ## is the number of days that the
- logfile should be kept,) and NODELETELOG this will tell the
- system to not delete the logfile at all. This option is
- also REQUIRED with the ZIPFILE option. It determines how
- often the program will archive the logfile. Archive daily
- or after ## number of days have elapsed.
-
- DELETELOG 7
-
- 11. DELETEFDLOG
- This option is not required. It activates or Deactivates
- the Front End Mailer logfile deleting option ie (Front
- Door)). The DEFAULT is the fd logfile will be deleted with
- the RA log. The two options are DELETEFDLOG and
- NODELETEFDLOG. When Zipping the File use DELETEFDLOG. This
- option does not have a ## requirement by itself. It relies
- on the ## number in the DELETELOG option for the BBS
- logfile.
-
- DELETEFDLOG
-
-
-
-
-
-
-
-
-
-
-
-
- REMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOG
- REMOTLOG V 2.00 9D 7
-
-
-
-
-
-
- 12. SHRINKFILE, ZIPFILE, or NOZIPFILE
- This option is not required and will not function if the
- DELETELOG option is not selected. It will determine whether
- or not the Log file will actually be deleted, zipped, or
- shrunk depending on a given date for storage.
-
- The archiving method used by default is PKZIP, any
- version located in your path. The file will be moved
- while archived. The archive name will be in the format
- RLMMDDYY.ZIP/ARC/ARJ/LZH/etc.
-
- The option SHRINKFILE will take the ## of days
- specified in the DELETELOG ## option and maintain on
- those entries in the logfile for those number of days.
- Meaning if today was the 21 APR 93 and DELETELOG 11 was
- specified. The first log entry that would be left in
- your log file would be from 10 APR 93 and onward.
-
- The NOZIPFILE option says that you don't want to
- archive the file and you don't want to shrink the
- logfile and you don't want to archive the log file.
- REMOTLOG will simply check the file make its notations
- and leave it as is.
-
- DEFAULT - NOZIPFILE, other otions are ZIPFILE and SHRINKFILE
-
- SHRINKFILE
-
- 13. ARCHIVER
-
- This option is also optional and defaults to PKZIP -m. It
- controls which program is used to archive the log files.
- The program should be able to remove the logfile after
- archiving it. Default is ARCHIVER PKZIP -m
- Option ARCHIVER
-
- ARCHIVER PKZIP -m
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- REMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOG
- REMOTLOG V 2.00 9D 8
-
-
-
-
-
-
- CONFIGURATION - COLORS SECTION
-
- 14. BACK
-
- This option is required. It tells the program which color
- to place the background of the ansi screen in. DEFAULT : 40
- [Black]
- Back 40
-
- 15. NUMBERS
-
- This option is required. It tells the program what color
- the numbers displayed are. DEFAULT : 1;33
- [Yellow]
- Numbers 1;33
-
- 16. HIGHLIGHT
-
- This option is required. It tells the program what color to
- use when highlighting the Beginning and Ending dates of the
- Log period. DEFAULT : 1;46;37
- [Bold White on Cyan]
- HighLight 1;46;37
-
- 17. NORMAL
-
- This option is required. It tells the program which color
- to use to restore the screen to "normal". DEFAULT : 0
- [No Attributes]
- Normal 0
-
- 18. OUTLINE
-
- This option is required. It tells the program which color
- to use for Outlining the Box and Dividing lines of the
- output file. DEFAULT 1;34
- [Bold Blue]
- Outline 1;34
-
- 19. TEXT
-
- This option is required. It tells the program which color
- to use for all the text that is printed. DEFAULT 0;32
- [Green]
- Text 0;32
-
- NOTE **** A color chart is supplied in Appendix A.
-
-
-
-
-
-
-
-
-
-
-
- REMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOG
- REMOTLOG V 2.00 9D 9
-
-
-
-
-
-
- 20. EXTERNALCHAT
-
- This option is not a required option it will default to FX-
- CHAT.EXE if nothing is specified. It lets REMOTLOG know
- what the Dos Shell entry of your External chat program is.
- This must be in the same case as the BBS will write it to
- the log file. DEFAULT : FX-CHAT.EXE
-
- EXTERNALCHAT FastChat.EXE
-
- 21. Search Items
-
- This option is not required and at the descretion of the
- sysop. Using This will cause another page to be displayed
- in addition to the current 2 or 3 pages that are already
- displayed. This option is where the sysop can have remotlog
- search the logfile for something specific and keep track of
- its occurrences.
-
- I.e. *01My_Name Carter - This will cause remotlog to
- search the log file for all occurences of "Carter" it will
- accumulate and store the amount of time it finds it in
- variable 01. When it displays it it will display "My_Name
- >>> ####" where # is amount of times the item was found
- possible Variables are 00-29. The 0 is significant. The
- "*" is required there can be no spaces except to separate
- the Display item from the search item. When displayed the
- "_" underscore will be replaced by a space. On the search
- side underscores are NOT USED.
-
- Format "*<Variable 00-29><Entry to Make in *.Ans/*.Asc file>
- <Search For>"
-
- *00Graffitti_Wall Grafn3.EXE
- *01JetFighter_Game Combat 1
-
- 22. NOSHOW
-
- These options are not required. But they do provide you
- with a great amount of security. For areas you do not want
- all your users to see. IE. Adult areas or Sysop areas.
- (Message Areas) DEFAULT - NONE. 200 MAXIMUM ENTRIES.
-
- NoShow 8
- NoShow 10
-
- 23. NOFILE
-
- These options are not required. But they do provide you
- with a great amount of security. For areas you do not want
- all your users to see. IE. Adult areas or Sysop areas.
- (File Areas) DEFAULT - NONE. 200 MAXIMUM ENTRIES.
-
- NoFile 8
- NoFile 10
-
-
-
- REMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOG
- REMOTLOG V 2.00 9D 10
-
-
-
-
-
-
- 24. REPLACESEA / REPLACEDSP
-
- This option is not required. It is used to Change the
- default Sealink protocol displayed in the 1st output page to
- a protocol of your choosing. REPLACESEA - Is the Search
- String for the new protocol. REPLACEDSP - Is the Actual Item
- to be displayed in the Output page.
-
- ReplaceSea SEALink
- ReplaceDsp SEALink
-
- 25. NOLOCAL
-
- This option is also not required. It determines whether or
- not the local logons will be shown on the report output.
- The DEFAULT for this option is show local logons. Leave
- this option out for the default to take effect.
-
- NoLocal
-
- 26. FILECOUNTER
-
- This option is also not required. It activates or
- deactivates the Files.BBS downloaded files counter. The
- count will be stored and added to the Files.BBS in the
- directory the file was taken from. DEFAULT for this option
- is FILECOUNTER, To deactivate use NOFILECOUNT
-
- ******* FILECOUNTER Option has been removed due to Enhancements in RA
-
- 27. CHATRECORD
-
- This option is also not required. It activates a chat
- record. This will log all chats found in the log file to a
- file called REMOTLOG.CHT in the current directory. The
- DEFAULT is CHATRECORD, all chats will be logged. The other
- option to disable the chat is NOCHATRECORD A file is created
- named REMOTLOG.CHT
-
- CHATRECORD
-
- 28. MESSAGEBOARD
-
- This tells remotlog which message area to post the
- statistics files generated to. A value of 0 here would
- cause remotlog to not post the files to the message area.
- But will still accumulate information in Them. This option
- is REQUIRED.
-
- MessageBoard 3
-
-
-
-
-
-
-
-
- REMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOG
- REMOTLOG V 2.00 9D 11
-
-
-
-
-
-
- 29. DOWNLOADS
-
- This option is not required and defaults to Off. It will
- determine if Remotlog will log a copy of all BBS downloads
- out to a file. This file will be called REMOTLOG.DWN it
- will be appended to if not posted to the message base. To
- activate this option the Keyword is DOWNLOADS
-
- Downloads
-
- 30. WHATDOORS
-
- This option is not required and defaults to off. It
- determines whether or not REMOTLOG will log a copy of all
- users that access any of the doors that you use on your
- system. It logs them all to a file called REMOTLOG.DRS. It
- will also append if the file is not erased. The file as
- with all others created will be posted to the message base
- to the sysop if the messageboard option is specified. The
- word to activate this option is WHATDOORS
-
- WhatDoors
-
- 31. QUESTIONAIRE
-
- This option is not required and defaults to off. It
- determines whether or not REMOTLOG will log a copy of all
- users that access any of the questionaires that you have for
- your users. It logs them all to a file called REMOTLOG.QST.
- It will also append if the file is not erased. The file will
- be posted to the message base. Option is QUESTIONAIRE
-
- QUESTIONAIRE
-
- 32. SPLITFILES
-
- This option is not required and defaults to off. It
- determines whether or not REMOTLOG will create separate
- files for each report Screen. The files will be
- REMOTLO#.ASC/ANS. Where # is 1 - 5 depending on the Page
- the report. OPTION SPLITFILES. If this option is specified
- and bulletins are generated they will have a filename of
- RLOG_B##.ASC/ANS. ## = 1-10
-
- SPLITFILES
-
- 33. NOSORT
-
- This option is not required and defaults to off. It
- determines whether or not the Files.BBS listings will be
- sorted. The sort now respects non-filename characters at
- anypoint in the file and will no longer sort them to the
- top. OPTION: NOSORT
-
- ******** NOSORT Option removed due to enhancements in RA
-
-
-
- REMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOG
- REMOTLOG V 2.00 9D 12
-
-
-
-
-
-
- 34. DROPCARRIER
-
- This option is not required and defaults to off. It
- determines whether or not REMOTLOG will generate a message
- to those users that have dropped carrier on your system.
- Filename is required and must contain at least one
- character. OPTION: DROPCARRIER <FILENAME> or NODDROPCARRIER.
- The file can be whatever you want TXT/ANS/ETC, it must
- contain at least 1 character.
-
- DROPCARRIER DROPMESS.TXT
-
- 35. UPLOADMSG
-
- This option is not required and defaults to off. It
- determines whether or not REMOTLOG will generate a message
- to those users who have uploaded to the system. Filename is
- required to Post a message and it must at least contain 1
- character. Option: UPLOADMSG <filename> , NOUPLOADMSG. The
- file can be whatever you want TXT/ANS/ETC, it must contain
- at least 1 character.
-
- UPLOADMSG Upload.TXT
-
- 36. NEWUSERMSG
-
- This option is not required and defaults to off. It
- determines whether or not REMOTLOG will generate a message
- to those users who have just logged on to the system. New
- Users. Filename is required to post a message and it must
- at least contain 1 character. Option: NEWUSERMSG
- <filename>,NONEWUSERMSG. The file can be whatever you want
- TXT/ANS/ETC, it must contain at least 1 character.
-
- NEWUSERMSG NewUser.TXT
-
- 37. CDROM
-
- This option is not required and defaults to off. It will
- let REMOTLOG know that you have a CDROM Drive and which one
- it is. Given the differences between manufacturers of CDROM
- drives for computers and how they place files on them. This
- option allows for easy and more simplistic handling of
- those. OPTION: CDROM <Drive Number> <Drive Letter>\ Where
- drive number is 0-9 to indicate the physical number of the
- CDROM drive. Drive Letter is of course whatever the CDROM
- drive letter is. the "\" is required on the drive specs.
-
- CDROM 0 L:\
- CDROM 1 M:\
- CDROM 2 O:\
-
- ***** POSSIBLE REMOVAL IN FUTURE VERSIONS (RA2.00) *******
-
-
-
-
-
- REMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOG
- REMOTLOG V 2.00 9D 13
-
-
-
-
-
-
- 38. CUMULATIVE
-
- This option is also optional and defaults to off. It will
- give you a complete listing of all users that have dropped
- Carrier on your system and how many times to date that they
- have done so. This will be posted to the Sysop by REMOTLOG.
- OPTION : CUMULATIVE
-
- CUMULATIVE
-
- 39. MINIMUMTIME
- This option is also optional and defaults to 0. It controls
- how many times the user must have dropped carrier before
- they will be listed in cumulative Dropped/Lost Carrier
- listing. Default is MINIMUMTIME 0. Option MINIMUMTIME ###
-
- MINIMUMTIME 5
-
- 40. MINDROPCARR
- This option is also optional and defaults to 0. It controls
- how many times the user must have dropped carrier before
- they will be sent a Dropped Carrier message. Default is
- MINDROPCARR 0 OPTION MINDROPCARR ###
-
- MINDROPCARR 0
-
- 41. NODROP
- This default to NO DROP. It is used to check what log entry
- is made just before the system logfile records a lost
- carrier. If REMOTLOG is sending dropped carrier messages to
- users after they use some doors and logoff from the door.
- Then simply place either the DOS SHELL information here or,
- in cases where you have the shell logging information to
- your logfile place the last logged line of the shell here.
- OPTION Nodrop Rats.exe
-
- NODROP Rats.exe /n
- NoDrop BWExpress.exe
-
- 42. MAXDISP
- This controls the newly added bulletins. Maximum number of
- items that will be displayed is 50 this option allows you to
- vary between 1 and 50. Defaults to 50
-
- MAXDISP 25
-
- 43. BULLETINS / NOBULLETINS
- This option determines whether the bulletin information will
- be created or not. You only need to have it active once in
- a multiline setup. Preferable on the last line being
- processed. Default to on.
-
- NOBULLETINS
-
-
-
-
-
- REMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOG
- REMOTLOG V 2.00 9D 14
-
-
-
-
-
-
- APPENDIX A.
-
- Supplied ANSI Code sequences
-
- Number Represents
- ------ ----------
- 0 All attributes off (Normal Display)
-
- 1 High Intensity (Bold)
-
- 5 Sets Blink on
-
- 7 Reverse Video on
-
- 8 Concealed on (makes display invisible)
-
- 30 Foreground Black
-
- 31 Red
-
- 32 Green
-
- 33 Yellow
-
- 34 Blue on Color Monitor
- Underline on MonoChrome
-
- 35 Magenta
-
- 36 Cyan
-
- 37 White
-
- 40 BackGround Black
-
- 41 Red
-
- 42 Green
-
- 43 Yellow
-
- 44 Blue
-
- 45 Magenta
-
- 46 Cyan
-
- 47 White
-
-
-
-
-
-
-
-
-
-
- REMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOG
- REMOTLOG V 2.00 9D 15
-
-
-
-
-
-
- APPENDIX B.
-
- Hints about operation of this program
-
- There are several different things that you can do to get certain
- results from this program.
-
- For example if you want to change the begining date of the
- report without erasing the remotlog.dat file. All you have
- to do is to edit the .DAT file find the string that has the
- date in it and make it a null string. When the program
- starts up it will notice the date is missing and get the
- date from the current system.log file.
-
- When reading the log file the program will not attempt to
- reposition pointers if the last item in the log is the
- REMOTLOG tag. Of course the current session will be
- appended to the end of the logfile.
-
- By deleting the notations/entries that REMOTLOG makes in the
- log file you can force it to re-process portions of or the
- entire log file.
-
- The *##^^^^^^^^^ ___ option will accept hard spaces in the
- search for portion. It is not restricted.
-
- Any bug reports, comments, or requested addition, deletions etc. may
- be sent to Node 1:135/72. or the addresses listed in the registration
- section. I can also be reached in the RA_UTIL echo. Before you send
- me a bug report if you are not registered, and if you are. Insure
- that you RTM and read the configuration file comments before screaming
- bug report. If you send me netmail bug reports, and are not
- registered do not wait for a netmail reply. It cost me money to send
- a net message back to you and you couldn't find it to register. All
- bug reports must contain a copy of Errors.log and a summarized copy of
- your configuration file. Meaning leave out all the lines with a ";"
- in them. Explain the bug in full detail. If not I will simply ignore
- it or send you a message indicating that I will take no action until
- you can meet the bug reporting requirements.
-
- Credits
-
- The author, Orland K. Carter, would like to thank anyone who served as a
- beta testers of this program that put up with the constant updates to the
- one program and major overhaul of their configuration and data files.
-
-
-
-
-
-
-
-
-
-
-
-
-
- REMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOG
- REMOTLOG V 2.00 9D 16
-
-
-
-
-
-
- APPENDIX C
-
- Registrations
-
- The cost to register REMOTLOG is $20.
- Registrations will be sent to.
- __________________________________________________________________________
- |Registration of REMOTLOG, Form 2.00, B.D 00-97-13-003|
- |------------------------------------------------------------------------|
- | |
- |SysopName |
- |Name of Sysop __________________________________________________________|
- | |
- |Street Address__________________________________________________________|
- | |
- |City/St/Zip __________________________________________________________|
- | |
- |BoardName |
- |Name of BBS __________________________________________________________|
- | |
- |Number of BBS __________________________________________________________|
- | |
- |Node # __________________________________________________________|
- | |
- |Make all payments address to |
- | Orland Carter |
- | Dept.R00-97-13-003 |
- | P.O. Box 540898 |
- | Opa-Locka, FL 33054 |
- |________________________________________________________________________|
-
- Thank you for your support.
-
- Orland
-
- Node 1:135/72 @FIDONET
- 55:55/2 @CAPNET
- 55:5004/0
- 55:420/0
- 55:420/8349
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- REMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOGREMOTLOG
- REMOTLOG V 2.00 9D 17
-
-
-
-