home *** CD-ROM | disk | FTP | other *** search
-
- ┌───┐┌─────┐┌─────┐ ┌────────┐┌───────┐┌───────┐
- │░▒▓││░▒▓┌─┘│░▒▓┌─┘ │░▒▓ ┌┐░▒││░▒▓█▓░▒││░▒▓┌┐░▒│
- │▒▓█││▒▓█│ │▒▓█└┐ │▒▓█┌┘│▒▓││▒▓┌────┘│▒▓█└┘▒▓┘
- │▓██││▓██│ │▓██┌┘ │▓██│ │▓█││▓█│ ┬──┐│▓██┌┐▓█│
- │███││███└─┐│███└─┐ │███│ │██││██└─┘██││███││██│
- └───┘└─────┘└─────┘ └───┘ └──┘└───────┘└───┘└──┘
-
- IceManager, Nightly Maintenance Utility
- For RemoteAccess v2.xx BBS packages
-
- ─────────────────────────────────────────────────────────────────────────────
- IceMGR v1.00 - CopyRight Jeremy Landvoigt, 1996 - IceMGR v1.00
- ─────────────────────────────────────────────────────────────────────────────
-
- ┌───────────────────────────────────────────────────────────────────────────┐
- │░░░▒▒▒▓▓▓ A Really Quick Note ▓▓▓▒▒▒░░░│
- └───────────────────────────────────────────────────────────────────────────┘
-
- Well guys, after a year of this thing being run on no more than 3 test
- systems, I've decided that I should release it. Since it IS a first
- version, there may be problems that weren't caught during the beta cycle.
- If you encounter any problems, please report them. Additionally if you
- have any suggestions for new features, I'd be interested in hearing
- them.
-
- ┌───────────────────────────────────────────────────────────────────────────┐
- │░░░▒▒▒▓▓▓ CopyRight Notices & Program Disclaimer ▓▓▓▒▒▒░░░│
- └───────────────────────────────────────────────────────────────────────────┘
-
- The utility IceMGR, along with all its support files and documents,
- are Copyright (C) 1996 Jeremy Landvoigt. Distributing a version
- AFTER it has been registered is prohibited; distribution & execution of
- the original, unaltered version is permitted, indeed encouraged, as long
- as all support-files and documentation that accompany the program are
- included WITHOUT ALTERATION OF ANY SORT. None of the files included
- in the IceMGR archive may be modified in any way or distributed in any
- package without the express permission of Ice Technologies. Any type of
- cracking of either evaluation or registered versions of IceMGR
- including (but not limited to) hex-editing, reverse engineering,
- decompiling are strictly prohibited.
-
- The author can be quickly reached for information through the RA_UTIL
- international FidoNET Conference, or at InterNET e-mail address:
-
- jlandvoigt@interhop.net
-
- Or, If you wish to trust comments/complaints/suggestions to the Post
- Office, you can send them to:
-
- P.O. Box 93044
- 1111 Davis Drive
- Newmarket, Ontario
- Canada L3Y 8K3
-
- The following programs mentioned in this documentation are Copyright of
- their respective authors. They are listed in no particular order:
-
- IceMGR - CopyRight Jeremy Landvoigt
- RemoteAccess - CopyRight Wantree Development & Andrew Milner
-
- THE USUAL LEGALITIES
-
- I (Jeremy Landvoigt) make no warranty of any kind, expressed or implied,
- including without limitation any warranties of merchantability
- and/or fitness for a particular purpose. I shall not be held liable
- for any damages, whether direct, indirect, special or consequential
- arising from the failure of this program to operate in the manner desired
- by the user. I shall not be held liable for any damage to data or
- property which may be caused directly or indirectly by the use of this
- program.
-
- In no event will I be held liable for any damages, including (but
- not limited to) any lost profits, lost savings, or other incidental
- or consequential damages arising out of the use -- or the inability
- to use -- this program, or for any claim by any other party. The only
- thing that IceMGR is guaranteed to do is to take up space on your
- hard drive.
-
- Making use of this software is acknowledgement that you have read,
- understand, and fully agree to the license and disclaimer agreement.
-
- ┌───────────────────────────────────────────────────────────────────────────┐
- │░░░▒▒▒▓▓▓ Registration ▓▓▓▒▒▒░░░│
- └───────────────────────────────────────────────────────────────────────────┘
-
- The Development of IceMGR v1.00 took many long hours, and a lot of time
- and effort not to mention money. This program is not FreeWare. If this
- program satisfies your expectations of a User Access Manager, if not MORE,
- then you are expected to register it after an evaluation period of 30 days
- or sooner. By doing this you can be sure of continued development of the
- software. Thanks for your support.
-
- This Program may be freely distributed but DO NOT under any circumstances
- change any of the executables or alter any files that come in the original
- distribution archive.
-
- I urge you to register as soon as you can! The more registrations that
- I have will show the interest of people in the program, and I will release
- a newer version with many more features. If you should choose to register
- IceMGR all "Unregistered" messages and almost inaudible beeps within the
- program will also be removed. Please note that the status of features
- (whether they are available or not to unregistered users) may be changed
- without further warning in later versions of the software; but this does
- not mean that they will be changed.
-
- If you wish to register, please fill out the registration form :
-
- North America
- -------------
-
- Register.Can - Registration Form For Canadian Users
- Register.Usa - For the U.S.A, and for all other Registrations
-
- Europe
- ------
-
- Register.Ger - Registration Form For Germany
- Register.Uk - Registration Form For Uk/Eire
-
- Far East
- --------
-
- Register.Aus - Registration Form for Australasia
-
- Please at this time send ALL registrations to the address listed in the
- correct registration form. Thank you for your support.
-
- Any Registration forms that have invalid or missing information may be
- considered void and not be processed, depending on the extent of the
- errors.
-
- Due to recent events, I have changed my policy on personal cheques that
- are sent in to pay for registration. I will continue to honour them,
- however as of this release, there will be a 3 week hold placed on the
- cheque to ENSURE that it does NOT go N.S.F. Although most people are
- honest about this, lately too many people have sent in N.S.F. cheques, and
- when contacted about them, show little or no concern about them or the
- financial difficulties they may have caused.
-
- Additionally, a service charge of $15 will be levied against any N.S.F.
- cheques. Until both the full payment, and the service charge is recieved
- in the form of a MONEY ORDER, the registration will not be processed.
-
- In conclusion to the above information, to ensure a speedy turnaround time
- it is recommended you send your registration in the form of a money order
- (or direct deposit for Canadian residents) If you do choose to send in a
- personal cheque, it means that you have read, understood and agree to these
- conditions.
-
- ┌───────────────────────────────────────────────────────────────────────────┐
- │░░░▒▒▒▓▓▓ Archive Contents ▓▓▓▒▒▒░░░│
- └───────────────────────────────────────────────────────────────────────────┘
-
- The IceMGR archive should contain the following files :
-
- ICEMGR.EXE - The Main Program
- MGRCFG.EXE - Use to configure the program
- ICEMGR.DOC - Program Documentation
- REGISTER.CAN - Canadian Registration Form
- REGISTER.USA - American Registration Form
- REGISTER.GER - German Registration Form
- REGISTER.AUS - Australian Registration Form
- REGISTER.UK - United Kingdom Registration Form
- SAMPLES.RAR - Sample Textfile messages/bulletins
- FILE_ID.DIZ - General Program Description
-
- If one or any combination of these files are missing, or files have been
- ADDED, then you are using a possibly modified or altered copy of IceMGR.
- It would be advised that you delete this copy, and get a clean copy of
- IceMGR from one of the BBS's listed at the end of the documentation.
- Newest Version of IceMGR can be F'REQed from Ice Technologies BBS under
- the magic name 'ICEMGR' (Without the quotes).
-
- ┌───────────────────────────────────────────────────────────────────────────┐
- │░░░▒▒▒▓▓▓ Program Information ▓▓▓▒▒▒░░░│
- └───────────────────────────────────────────────────────────────────────────┘
-
- Ice-Manager is a new Ice Technologies utility, and the very first utility
- that isn't run as a door, but in your nightly maintenance. It's purpose
- is an automatic bulletin generator/msg poster/access upgrader. :)
-
- It can create welcome, happy birthday, password failure, thankyou
- (uploads/msg post), daily birthday listings. It can also upgrade user
- security depending on their number of uploads and number of messages
- posted; and more!
-
- ┌───────────────────────────────────────────────────────────────────────────┐
- │░░░▒▒▒▓▓▓ Program Configuration - Using MGRCfg ▓▓▓▒▒▒░░░│
- └───────────────────────────────────────────────────────────────────────────┘
-
- Setting up IceMGR is quite easy. This section of the documentation will
- attempt to take you step by step on how to use the configuration utility
- MgrCfg.Exe to set up IceMGR. Most of the options are self explanatory.
-
- File
- ------
-
- █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█
- ▌ Save & Exit ▐
- ▌ Save Without Exit ▐
- ▌ Exit Without Save ▐
- ▌ Program Info ▐
- ▌ Carrier Offenders ▐
- ▌ Twit List ▐
- █▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█
-
- · Save & Exit - This will save your current configuration to the
- IceMgr.Cfg file and will exit the program.
-
- · Save Without Exit - This will save your current configuration to the
- IceMgr.Cfg file and will allow you to continue modifying your setup.
-
- · Exit Without Save - This will abort the save procedure (just in case you
- somehow really messed up!) and will exit the program.
-
- · Program Info - This will give you a little bit of information on the
- current version of IceMGR that you happen to be using.
-
- · Carrier Offenders - Use this to list and edit users to drop carrier,
- and how many times they have done so.
-
- · Twit List - Use this to edit the list of twit users whose access will
- not be upgraded even if they have reached the required number of kbyte
- uploads or message posts.
-
- VALUES
- --------
-
- █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█
- ▌ Uploads (k) ▐
- ▌ Msgs Posted ▐
- ▌ NewUser Security ▐
- ▌ Board Number ▐
- ▌ System Node No. ▐
- ▌ Hangup Times ▐
- ▌ Hangup Security ▐
- █▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█
-
- · Uploads (k) - Use this to set the upgrade access according to uploads
- in kilobytes. You can set a virtually limitless number of access
- upgrade levels. Press INS to add additional records.
-
- Each record contains:
-
- Target - This is the the level of uploads in K the user must reach
- before their security is upgraded.
-
- OldSec - This is the security level that the user must have now in order
- to be upgraded.
-
- NewSec - This will be the users new security level if they have reached
- the target chosen by the SysOp.
-
- · Msgs Posted - Use this to set the upgrade access according to number
- of messages posted. You can set a virtually limitless number of access
- upgrade levels. Press INS to add additional records.
-
- Each record contains:
-
- Target - This is the the number of messages the user must post
- before their security is upgraded.
-
- OldSec - This is the security level that the user must have now in order
- to be upgraded.
-
- NewSec - This will be the users new security level if they have reached
- the target chosen by the SysOp.
-
- · NewUser Security - This is the access that newusers have when they log
- on the BBS. This is used when IceMGR creates welcome messages for new
- users.
-
- · Board Number - This is the board number where all messages to users will
- be posted. This MUST be set if you are using The HUDSON message base
- system.
-
- · System Node No. - This is the number of nodes you have on your system.
- This is required for multinode setup so that IceMGR can scan each node's
- system log to check for newusers, and password failures.
-
- · Hangup Times - How many times can a user hangup on the system before
- they are penalized by an access drop.
-
- · Hangup Security - What security should the user be dropped to if they
- drop carrier excessively (defined in Hangup Times).
-
- TOGGLES
- ---------
-
- █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█
- ▌ Welcome Message NO ▐
- ▌ Access/Uploads (k) NO ▐
- ▌ Access/Msg Posts NO ▐
- ▌ Birthday Message NO ▐
- ▌ Generate Bday ANSi NO ▐
- ▌ Password Watchdog NO ▐
- ▌ Hangup Tracking NO ▐
- ▌ Top 10 Hangup List NO ▐
- ▌ Enable Backups NO ▐
- ▌ Use JamBASE NO ▐
- █▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█
-
- · Welcome Message (YES/NO) - Should IceMGR generate Newuser Welcome
- messages?
-
- · Access/Uploads (k) (YES/NO) - Should IceMGR upgrade access depending on
- user uploads in K, as defined by the Sysop and then in turn post a thank
- -you message to the user?
-
- · Access/Msg Posts (YES/NO) - Should IceMGR upgrade access depending on
- user message posts, as defined by the Sysop and then in turn post a
- thank-you message to the user?
-
- · Birthday Message (YES/NO) - Should IceMGR post a Happy Birthday message
- to the user?
-
- · Generate Bday ANSi (YES/NO) - Should IceMGR create a daily birthdays
- Bulletin?
-
- · Password Watchdog (YES/NO) - Should IceMGR post a message to the user
- if there are excessive password failures on their account?
-
- · Hangup Tracking (YES/NO) - Should IceMGR keep track of user carrier
- loss and drop user security accordingly after excessive carrier losses?
-
- · Top 10 Hangup List (YES/NO) - Should IceMGR generate a "Top 10 Carrier
- Offenders" Bulletin?
-
- · Enable Backups (YES/NO) - Should IceMGR backup all files defined in
- BACKUP.CTL. The format of BACKUP.CTL is as follows:
-
- HEADER [PATH\FILESPEC]
-
- eg
-
- SYSTEM C:\BBS\RA\*.RA*
- USER C:\BBS\MSG\USER*.*
- ANSI C:\BBS\TXTFILES\*.ANS
-
- On each line, specify a header name for the file, and the
- directory/filespec that should be backed up. When IceMGR executes in
- the nightly maintenance, it will backup the specifed files into the
- backup directory, as defined in MGRCFG. The backup archive will be
- named after the header, with the extension corresponding to the day of
- the week.
-
- eg SYSTEM.TUE
-
-
- · Use JamBASE (YES/NO) - Should IceMGR post messages to the JamBASE? If
- NO, then all messages will be written to the board in the HMB.
-
- NAMES
- -------
-
- █▀▀▀▀▀▀▀▀▀▀▀▀▀█
- ▌ BBS Name ▐
- ▌ SysOp Name ▐
- ▌ Sender Name ▐
- █▄▄▄▄▄▄▄▄▄▄▄▄▄█
-
- · BBS Name - Enter the name of the BBS in this field.
-
- · SysOp Name - Enter the name of the System Operator in this field.
-
- · Sender Name - Enter the name IceMGR will use as the "sender" of the
- messages.
-
- PATHS
- -------
-
- █▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀▀█
- ▌ RA.LOG Path(s) ▐
- ▌ RemoteAccess Path ▐
- ▌ MsgBase Path ▐
- ▌ Birthday File ▐
- ▌ Backup Directory ▐
- ▌ Compression Util ▐
- █▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄▄█
-
- · RA.LOG Path(s) - Enter full path and filename of your RA.LOG. Use *N to
- represent nodenumber for multinode systems.
-
- Eg: C:\BBS\RA\NODE*N\RA.LOG
-
- · RemoteAccess Path - Enter full path to your Ra system files.
-
- · MsgBase Path - Enter full path to your HMB, or full path and filename
- to JamBASE.
-
- · Birthday File - Enter full path and filename of the daily birthdays
- bulletin.
-
- · Backup Directory - Full path to directory where IceMGR will store
- user and system file backups.
-
- · Compression Util - This is the compression utility that will be used
- during the backup procedure. PKZIP or ARJ highly recommended, as IceMGR
- is known to work perfectly with these two. LHA tends to prompt the
- sysop for input, which is not "good" during maintenance.
-
- ┌───────────────────────────────────────────────────────────────────────────┐
- │░░░▒▒▒▓▓▓ Setting up IceMGR with RemoteAccess ▓▓▓▒▒▒░░░│
- └───────────────────────────────────────────────────────────────────────────┘
-
- Although IceMGR was specifically designed to work with RemoteAccess, the
- actual integration of IceMGR has nothing to do with your RemoteAccess
- configuration.
-
- After completing the setup of IceMGR with MGRCFG, you'll need to add
- IceMGR to your BBS batchfile. Some systems make use of one main batchfile
- for recycling the BBS, whereas others use multiple files. To help you
- locate the proper file, you'll need to edit the batchfile which runs your
- mailer program (if you're using a mailer) or the file that runs RA.EXE.
-
- Generating Bulletins
- --------------------
-
- It's recommended that IceMGR is loaded just before the main EXE (whether
- it be RA or the mailer). Here is a sample:
-
- :START
- CD \BBS\ICEMGR
- ICEMGR.EXE -C
- CD \BBS\IMAIL
- IM.EXE
-
- In this sample, IceMGR is being run with the -C parameter, which will
- generate the today's callers list. After which, InterMail is loaded. This
- way an updated list is generated every time a user logs off of the BBS.
- Please refer to the "Command Line Parameters" section for a complete list
- of parameters.
-
- Nightly Maintenance
- -------------------
-
- Before setting up IceMGR for nightly maintenance, it is VERY IMPORTANT
- that RemoteAccess has been configured to use EXPANDED log format. For this
- first version IceMGR can only properly interpret expanded logs.
-
- If IceMGR is being run in the nightly maintenance, it doesn't require any
- special parameters. Simply add it into the section of your batchfile which
- controls maintenance. Sample:
-
- :BBSMAINT
- CD \BBS\ICEBANK
- ICEBANK /M
- CD\BBS\DOORS\TRADE
- EXTERN
- CD\BBS\ICEMGR
- ICEMGR.EXE
-
- After a few other maintenance utils are executed, IceMGR is run. At which
- time it will post any messages which are enabled in MGRCFG. Please NOTE:
- You need to CHDIR into the IceMGR directory before execution. Once
- IceMGR has scanned your RemoteAccess log, it is VERY important that the
- logged is either renamed, re-located, or moved or IceMGR will duplicate
- actions from the night before as it will re-scan the same sections of
- the log.
-
- ┌───────────────────────────────────────────────────────────────────────────┐
- │░░░▒▒▒▓▓▓ Files That Are Used By IceMGR ▓▓▓▒▒▒░░░│
- └───────────────────────────────────────────────────────────────────────────┘
-
- IceMGR will call upon a number of files during runtime. They are listed
- below along with a brief description.
-
- CONFIG.RA - This file is read by MGRCFG and IceMGR when you first install
- IceMGR. It will only be read if MGRCfg can find the RA
- environment variable. It is compatible with the RA 2.0x
- Config.Ra file only. It will not read the Ra 1.1x format.
-
- ICEMGR.CFG - This is IceMGR's configuration file. It is absolutely
- necessary in order for IceMGR.Exe to function.
-
- USERS.BBS - This file is accessed to update user security levels and
- generate bulletins.
-
- ICEMGR.U-L - This is the file that IceMGR stores upload access upgrade
- levels in.
-
- IceMGR.MSG - This is the file that IceMGR stores message post access
- upgrade levels in.
-
- BDAY.TXT - This file is a readonly file that IceMGR uses as the
- 'framework' for the daily birthday bulletin. You can create
- this file in a standard ANSi editor such as TheDraw. Include
- substrings to be converted into userlists etc. Codes listed
- below.
-
- TOPHANG.TXT - This file is a readonly file that IceMGR uses as the
- 'framework' for the Top 10 Hangup Offender Bulletin. You
- can create this file in a standard ANSi editor such as
- TheDraw. Include substrings to be converted into userlists
- etc. Codes listed below.
-
- HANGMGR.DAT - This is the file that IceMGR stores Carrier Offenders,
- and the number of times the carrier has been dropped by
- each offender.
-
- NEWUSER.DAT - This is the file that IceMGR stores already processed
- newusers in.
-
- EXEMPT.DAT - This is a textfile that you can create. IceMGR will read
- from this file if it detects that a carrier has been lost.
- Some programs allow users to terminate the connection. If
- IceMGR finds that any programs listed in this file have
- been run just previous to the carrier loss, it will exempt
- the user from penalization. Please specify FILENAME or
- BATCHFILENAME that calls the program, one per line.
-
- CARRIER.# - Textfile that contains carrier drop warning (before limit
- is reached). (# - language)
-
- SECDROP.# - Textfile that contains security level drop due to excessive
- carrier drop message. (# - language)
-
- BDAY.# - Textfile that contains the Happy Birthday message. #
- represents the language of the user.
-
- FILESK.# - Textfile that contains the Thankyou Message for uploading
- the specified number of Kbytes. (# - language)
-
- MSGS.# - Textfile that contains the Thankyou Message for writing the
- specified number of messages. (# - language)
-
- PASSWORD.# - Textfile that contains the password failure warning.
- (# - language)
-
- WELCOME.# - Textfile that contains newuser greeting. (# - language)
-
- RATOP.A?? - ANSi/ASCii file containing top header information for
- today's caller listing.
-
- RAMIDDLE.A?? - ANSi/ASCii file containing middle list format for
- today's caller listing.
-
- RABOTTOM.A?? - ANSi/ASCii file containing bottom header information for
- today's caller listing.
-
- FDTOP.A?? - ANSi/ASCii file containing top header information for
- inbound session listing.
-
- FDMIDDLE.A?? - ANSi/ASCii file containing middle list format for
- inbound session listing.
-
- FDBOTTOM.A?? - ANSi/ASCii file containing bottom header information for
- inbound session listing.
-
- BACKUP.CTL - Textfile containing list of file directories/filespecs to
- be backed up.
-
- ┌───────────────────────────────────────────────────────────────────────────┐
- │░░░▒▒▒▓▓▓ IceMGR's Commandline Parameters ▓▓▓▒▒▒░░░│
- └───────────────────────────────────────────────────────────────────────────┘
-
- Following is a current list of all IceMGR commandline parameters.
-
- -C - Generate today's callers bulletins. If running IceMGR with this
- parameter, it should be run immediately after a user logs off the
- BBS, or immediately before your Mailer (FD/IM) is executed.
-
- -I - Generate inbound session bulletins. If running IceMGR with this
- parameter, it should be run immediately after inbound mail toss,
- or immediately before your Mailer (FD/IM) is executed.
-
- ┌────────────────────────────────────────────────────────────────────────────┐
- │░░░▒▒▒▓▓▓ Message Substrings ▓▓▓▒▒▒░░░│
- └────────────────────────────────────────────────────────────────────────────┘
-
- In all bulletins that get posted to users (excluding daily b-day bulletin),
- you can use the following message substrings that will get converted into
- other data.
-
- %DATE% - The date at time of message processing.
-
- %AGE% - The user's age. (BDAY.#)
-
- %MSGS% - The Target number of messages for the users current security
- level. (MSGS.#)
-
- %KBYTES% - The Target number of Kbytes for the user current security
- level. (FILESK.#)
-
- %CD% - Number of times user has dropped carrier
-
- %SYSOPNAME% - The Sysop's Full Name.
-
- %BBSNAME% - The BBS name.
-
- %FROMNAME% - The name defined as the "FromName" in MGRCFG.
-
- %USERNAME% - The full user name.
-
- %FIRSTNAME% - The users first name.
-
- %SYSOPFIRST% - The Sysop's First name.
-
- %FROMFIRST% - The "FromName"'s First name.
-
- %SUBJECT:[S] - The message subject [S] - MUST BE ON A LINE BY ITSELF!
-
- %PWDLIST% - The list of failed passwords - MUST BE ON A LINE BY
- ITSELF! (PASSWORD.#)
-
- Imbedded Colors
- -----------------
-
- With IceMGR, it is possible to use color codes into your bulletin text.
- This is very easily done. Wherever you would like to have a color change in
- your message, type one of the following codes:
-
- |00 - Black
- |01 - Blue
- |02 - Green
- |03 - Cyan
- |04 - Red
- |05 - Magenta
- |06 - Brown
- |07 - LightGray
- |08 - DarkGray
- |09 - LightBlue
- |10 - LightGreen
- |11 - LightCyan
- |12 - LightRed
- |13 - LightMagenta
- |14 - Yellow
- |15 - White
-
- So, If you had a line such as:
-
- "|15This is a |09test."
-
- The first three words "This is a" would be in White, and the rest, "Test."
- would be in LightBlue once the message text has been saved to the MSGBASE.
-
-
- The following codes can be used only in the BDAY.TXT / TOPHANG.TXT file:
-
- %B - BBSname
- %D - The current date as of bulletin generation
- %F - The "Fromname" as defined in MGRCFG.
- %S - The Sysopname as defined in MGRCFG.
-
- The following codes can be used only in the BDAY.TXT file:
-
- %T - Today's Birthday list. } The names will be centred on the
- %W - Tomorrow's Birthday list. } screen, one name per line.
-
- The folowing code can be used only in the TOPHANG.TXT file:
-
- %H - Top 10 Hangup Offenders list.
-
- You can also use the standard ^F ^K (etc..) codes in these bulletins that
- RA provides, as IceMGR will in no way disrupt them.
-
- In the today's caller listing, or inbound session listing, the following
- ^K codes are available. Note that these codes MUST be padded with \, |, or /
- characters. Each of these characters will change the justification.
-
- If you pad with \, the text will be left justified. | will centre the text,
- and / will right justify the text.
-
- Eg.
-
- ^KJ||||||||||||||||||
-
- In this example, The BBSName will be displayed in the bulletin. It has been
- padded with 18 | characters. By doing this,
-
- 1) If the BBS Name is greater than 20 characters, it will be trimmed off.
-
- 2) If the BBS name is less than 20 characters, the additional | characters
- will be replaced by spaces.
-
- 3) Since | was used, the information will be centred.
-
- This is necessary in order to keep the format of the bulletins aligned,
- so that information being displayed row by row will be in the same position
- as the information on the line above it.
-
- RT - RATOP.ANS FT - FDTOP.ANS UT - ULTOP.ANS
- RM - RAMIDDLE.ANS FM - FDMIDDLE.ANS UM - ULMIDDLE.ANS
- RB - RABOTTOM.ANS FB - FDBOTTOM.ANS UB - ULBOTTOM.ANS
-
- Code: Description: Files:
- ───────────────────────────────────────────────────────────────────────────
-
- ^KA Number in list/total number RM RB FM FB UM UB
- ^KB User Name RM UM
- ^KC User Handle/Alias RM UM
- ^KD User Location RM UM
- ^KE Time Of Call RM FM
- ^KF User Logoff Time RM
- ^KG User Connect Rate RM
- ^KH User Calling Times RM UM
- ^KI Node Number RM
- ^KJ User Last Calling Date UM
- ^KK BBS Name All
- ^KL SysOp Name All
- ^KM System Name FM
- ^KN System Location FM
- ^KO System Address FM
-
- ^KQ Time Online FM
- ^KR Bytes Recieved FM
- ^KS Bytes Sent FM
- ^KT Cost FM
-
- ┌────────────────────────────────────────────────────────────────────────────┐
- │░░░▒▒▒▓▓▓ Other Ice Technologies Utilities ▓▓▓▒▒▒░░░│
- └────────────────────────────────────────────────────────────────────────────┘
-
- Here is a list of all the Ice Technologies utilities that were available at
- the time of release of this archive. If you enjoy using this Ice utility,
- you may want to check some of these out! :)
-
- · IceChat -
-
- IceChat is a split screen chat utility for RemoteAccess/ProBoard BBS
- packages. It can be used with many other BBS types as long as they
- support Dorinfo1.Def/Door.Sys type Doors.
-
- · IceEdit -
-
- IceEdit is a fullscreen ANSi message editor that was originally designed
- for use with RemoteAccess. Although it has been tested with
- RA v2.xx, PB v2.xx, and TeleGard v3.0 it should be compatible with any
- other BBS that uses the QuickBBS style dropfiles that contain the
- message writing information. These files are MSGTMP & MSGINF. You should
- check your BBS documentation to see if your software supports this
- system. IceEdit also calls on the Dorinfo1.Def file to read in necessary
- information about the user profile.
-
- · IceNote -
-
- IceNote is the third Ice Technologies door to become available. It is a
- message to all users type door with many neat features. It has been
- tested with both RemoteAccess v2.xx, and the latest release of Renegade,
- and should work with any other Dorinfo1.Def compatible BBS Packages.
-
- · IceBank -
-
- IceBank is the fourth utility to become available. It is a fully
- functional, fully configurable timebank system for RA v2.xx/PB v2.xx.
- It has many cool features, including InterBBS transactions.
-
- · IceUser -
-
- This is the fifth utility to become available. It is a fully
- functional online user editor for RemoteAccess v2.xx. Very secure.
-
- · IceCBV -
-
- The very newest Ice Technologies door available! Took awhile to finally
- get it released, but you won't be disappointed. Full featured callback
- verification system for RemoteAccess and ProBoard. Many unique features!
- Look forward to even more features in the next version!
-
-
- ┌───────────────────────────────────────────────────────────────────────────┐
- │░░░▒▒▒▓▓▓ Program Support - BBS Locations ▓▓▓▒▒▒░░░│
- └───────────────────────────────────────────────────────────────────────────┘
-
- All Ice Technologies utilities are available from our homepage at:
- http://www.ionsys.com/~mckkev/icesoft.html
-
- IceMGR can be File Requested from any of the following BBS's under the
- magic name of ICEMGR.
-
- Legend
- ──────
-
- S - Support Site B - Beta Site R - Registration Site D - Distrib. Site
-
- Ice Technologies Concession Stand Minerva Online Ltd.
- Ontario, Canada Florida, USA London, England
- (905) 895-7775 (561) 569-6568 +44-(0)181-402-3350
- FidoNET 1:259/912 FidoNET 1:374/6568 FidoNET 2:254/33
- Max. Baud: 28800 Max. Baud: 33600 Max. Baud: 28800
- Flags: S B R D Flags: S B D Flags: S R D
-
- The Modem Link Slash BBS The Fisherman's Cove
- Heidelburg, Germany Venray, The Netherlands Maryland, USA
- +49-6221-390239 +31-478-550103 (410) 561-9937
- FidoNET 2:2468/6022 Fidonet 2:512/5 FidoNET 1:261/1041
- Max. Baud: 19200 Max. Baud 33600 Max. Baud 38400
- Flags: S R D Flags: S D Flags: S R D
-
- Lateline BBS The Oriental Express
- Penshurst, Australia Torii Station, Japan
- +61-2-579-6564 +81-6117-44-4584
- 3:712/841 FidoNET 6:733/76
- Max. Baud: 28800 Max. Baud 28800
- Flags: S R D Flags: S D
-
- <EOF>
-