Sunrise Door and Home Software Friday November 24, 2017  





REMIND ME! WINServer Documentation

Download PDF Version

Version 2.1
Author/Contact Al Lawrence/Sunrise Door Software
Overview The REMIND ME! Door allows your callers to enter REMINDERS to themselves. They can be reminded daily, on a specific date, a day of the week, on a particular date of the month or every OTHER day. Reminders are displayed to the caller when they choose the correct option from the REMIND ME Main Menu AND/OR they will be sent to the caller automatically as a PRIVATE Message in
the BBS message base. A NEW option allows the Reminders to be sent via EMAIL

SYSOP can leave reminders to ALL, specific Security levels or to SPECIFIC USERS!!!! They will also be sent to the callers via a PRIVATE BBS message!
Non-Registered
 Restrictions
- Maximum number of Reminders is 5 TOTAL
- Game time limit disabled
- Allow Player to Send and Read Messages from the Door Message Center
- REMEVENT not activated
- Deleted/Expired REMINDERS cannot be purged
Installation (1) Create a directory to hold all files
(2) Unzip the archive into the above directory
(3) MOVE the WCX file to your WC5 directory and delete it from the directory created in step (1)
(4) Create a menu entry to run the wcBASIC Door and you MUST pass the FULL drive:\path of the directory as a command line parameter when defining the Door on the menu. An example follows:

Program Name: REMINDME
Parameter:      c:\wc5\doors\REMINDME

(5) Modify the supplied CFG file. A description follows:

CONFIGURATION FILE

# = Requires registration to change to a different value.


NOTE: There are NO Blank Lines in the Config File!!
SUNRISE-80 BBS Your BBS Name
Al Lawrence Sysop's First AND Last name
00000000 Registration Number
Y Y = Log all callers to USAGEx
N = Do not log callers
# 0 Time Allowed in Door per day. (0 = BBS Time remaining)
2 1 = DO NOT Display ADOPT-A-DOOR Message
2 = Display ADOPT-A-DOOR message
# Y Y = Allow player to send PRIVATE messages from the Door Message Center
N = Do NOT allow PRIVATE messages
# 0 Place PRIVATE messages in this BBS Conf #
# Y Y = Allow player to send PUBLIC messages addressed to ALL from Message Center
N = Do NOT allow PUBLIC messages
# 1 Place PUBLIC messages in this BBS conf. #
# Y Y = Allow Player to Check for Mail from the Door Message Center
N = Do NOT allow Check for Mail
Y Allow player to send EMAIL to Door Author
xxxx@yyyyyyy.zzz Door Author's EMAIL Address
NONE Additional security level that will be allowed to leave Reminders as if Sysop was online.
NONE GOODBYE File Name
N Y=Allow Reminders to be sent via EMAIL
N=Do NOT allow Reminders to be sent via EMAIL
0 Message conference that EMAIL Reminders will be sent to
G Door Rating. Default is G.
Maximum Characters: 5

Maintenance REMEVENT.WCX is a utility program that is run in an EVENT process. This program will search the database and send out ALL eligible REMINDERS to the appropriate users in the form of PRIVATE Messages and if present, will send PUBLIC Reminders from the REMINDME.PUB file.

Example command: wcrun -r REMEVENT FullPathtoDoorDirectory

***NOTE****: You MUST have a LOCAL node available for the event process to work properly
Send Public Reminders This option will give you the opportunity to send ONE-TIME PUBLIC Reminders to ALL your callers. The message will be placed in a PUBLIC conference of your choice, addressed to ALL with the From name being taken from the MakeWild SysopName. You might want to use this option to send holiday greetings for NEW YEARS, Chanukah, Christmas, Thanksgiving, or just about any other event you can think of.

To use this option you create a TEXT (ASCII) file named REMINDME.PUB. This file can contain ANY number of entries, but each entry MUST be on a separate line. The format of the entries is as follows:

aaa~bbb~ccc~ddd~eee

Where aaa = Reminder type (Currently only O is a valid entry)

Where bbb = Date the reminder is to be sent. It MUST be in the MM-DD-YYYY format.

Where ccc = The TEXT to be placed on the message SUBJECT line

Where ddd = The name of the text file that will contain the ACTUAL message you are sending. You can use @-codes and the length of the message is unlimited (remember you want the callers to read it, so keep the length reasonable). The file MUST reside in the Door directory and it WILL be DELETED after the Reminder is posted.

Where eee = Conference number to use for the PUBLIC Reminder

Public Reminders are processed during the nightly event and will also be processed if you use the Sysop option on the Main Menu of REMINDME.
Usage Log As an option, we provide you with the ability to log every player to a text file. IF you enter Y in the CFG file to log callers, the Door will place the caller's name as well as the ON and OFF times each time a caller selects the Door. A separate file will be created for each Node and the name of the file will be USAGEx, where x is the Node number.

You may delete these files at any time and the Door will recreate them the next time a caller enters the Door. If you do NOT want to continue logging callers, change the CFG file entry to N.
Adopt-A-Door The concept, ADOPT-A-DOOR, allows a caller to register (ADOPT) a door. It would be the same as sending in a donation, only this way it is earmarked for registering a particular door. In a way, the user feels he/she is "getting something in return". As a Door author I have decided to build this concept into each of my Door programs. The concept replaces the usual message "tell the Sysop to register this Door" we find in most
doors.

If the Door is unregistered then a message appears on the opening screen to that effect. After finishing or suspending a game, a message screen is displayed about the ADOPT-A-DOOR concept. The message also tells the caller to contact the Sysop to find out if there is any further details to the ADOPT-A-DOOR concept. Some Sysops give extra D/L time, online time, etc to callers that ADOPT-A-DOOR.

If the Door has been registered, either by the Sysop or other callers, the names of those contributors will be displayed in the closing screen.

NOTE: If you want to display the names of the callers that contributed to registering the Door, you must create an ASCII file called ADOPT.SYS. You create it with an ASCII text editor. Enter the names of the contributors (one on each line, maximum of 5 entries, each a maximum of 30 characters long). This file must be saved, in ASCII format, and placed in the Door directory.
Legalities THIS SOFTWARE AND ACCOMPANYING MATERIALS ARE DISTRIBUTED "AS IS" WITHOUT WARRANTY, EXPRESS, IMPLIED OR STATUTORY, INCLUDING BUT NOT LIMITED TO ANY IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. IN NO EVENT SHALL ANYONE INVOLVED WITH THE CREATION AND PRODUCTION OF THIS PRODUCT BE LIABLE FOR INDIRECT, SPECIAL, OR CONSEQUENTIAL DAMAGES, ARISING OUT OF ANY USE THEREOF OR BREACH OF ANY WARRANTY.
Distribution You may make this file available for downloading from your BBS or you may upload it to any BBS or WEB site of your choice, provided that you do not make any changes to the contents of the archive (ZIP/EXE file). The archive and its individual contents may not be used by any service that charges any money whatsoever, without the written permission of the author.
Registration Registration and the subsequent insertion of the registration number into your configuration file, allows for the display of your BBS name on the opening and closing screen as well as the reduction of a delay built into the opening screen display along with the ability to change certain values in the configuration file.

Once a door is registered, any changes to registration information (Sysop name or BBS Name) will require the doors to be re-registered at the registration fee in effect at that time.

Be sure to use the proper upper/lower case when filling in your name and BBS name, as they MUST match the way you entered them in the configuration file.
Misc. The latest version this product, along with and other fine DOOR and HOME EDITION products are always available for download from this web site.


Moving Eye Line

Moving Eye Line


Last modified: August 11, 2013        Valid XHTML 1.0 Transitional