Beijing Paradise BBS Backup

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

/ Beijing Paradise BBS Backup / PARADISE.ISO / software / BBSDOORW / DEP_53E.ZIP / DEPOSIT.DOC < prev next >

Wrap

Text File | 1993-08-21 | 37.9 KB | 903 lines

Online INSTAbank 5.3e Public Release Version A RemoteAccess 2.00.x Time and Byte Bank ──────────────────────────────────────────── (C) 1992-1993, William J. Dykstra Officially released on August 21, 1993 ************************ IMPORTANT NOTICE ************************ Due to the large number of suggestions and requests by sysops using INSTAbank, I have once again had to change some data file formats. There are different steps to take depending on which version you are upgrading from. If you are NOT upgrading (ie. this is the first time you are installing the program) then you can ignore these upgrade procedures. Sorry for doing this to you, but it was necessary. IF YOU DO NOT FOLLOW THE UPGRADE INSTRUCTIONS YOU WILL PROBABLY EXPERIENCE A LOT OF PROBLEMS! The first step in ALL cases is to unpack the archive into your bank directory. You may normally allow it to simply unpack all the files, overwriting the existing ones. In case someone changes this archive, make sure you do NOT allow your DEPOSIT.DAT, DEPOSIT.SEC, and DEPOSIT.CFG files to be overwritten! You only need to overwrite DEPOSIT.EXE, DEPMAINT.EXE, and the various documentation files. WHEN USING THE CONVERSION PROGRAMS, BE SURE THAT YOU ONLY RUN THEM ONCE! If you run a conversion utility a second time, it will mess things up... I recommend that you make a backup of your files before installing the new version. I also recommend that you delete the conversion programs (3TO4.EXE, 4TO5.EXE and CFGCONV.EXE) after you are done installing the new version. CONVERTING FROM version 5.3x to 5.3E ─────────────────────────────────── Just replace your old DEPOSIT.EXE with the new DEPOSIT.EXE. This is the only change required. No files need to be converted if you already use version 5.3x. CONVERTING FROM version 5.3 to 5.3D ─────────────────────────────────── Just replace your old DEPOSIT.EXE with the new DEPOSIT.EXE. This is the only change required. No files need to be converted if you already use version 5.3. CONVERTING FROM version 4.5 or 5.0: ────────────────────────────────── Simply run the CFGCONV.EXE program, and then run DEPMAINT and update the new security level fields. Also check your config file fields, and enter a sysop access password. CONVERTING FROM version 3.5 thru 4.3: ──────────────────────────────────── (1) Run 4TO5.EXE. (2) Next, DELETE the DEPOSIT.CFG and DEPOSIT.SEC files. You might want to print these out before you delete them. You will need to re-enter the information from within DEPMAINT.EXE. MAKE SURE YOU WRITE DOWN YOUR REGISTRATION CODE IF YOU HAVE ONE! (3) Now Run DEPMAINT.EXE and setup your configuration and security levels. That's it! CONVERTING FROM version 1.0 thru 3.3: ──────────────────────────────────── (1) Run 3TO4.EXE. (2) Run 4TO5.EXE. (3) Next, DELETE the DEPOSIT.CFG and DEPOSIT.SEC files. You might want to print these out before you delete them. You will need to re-enter the information from within DEPMAINT.EXE. MAKE SURE YOU WRITE DOWN YOUR REGISTRATION CODE IF YOU HAVE ONE! (4) Now Run DEPMAINT.EXE and setup your configuration and security levels. That's it! Online INSTAbank is a Borland Pascal 7.0 application written for RemoteAccess 2.00.x and compatible versions. This program will allow users to deposit and withdraw time and bytes. The sysop may configure the maximum daily deposits and withdrawals, as well as the maximum balances. There is also a Rob the Bank feature, which may be enabled or disabled by the sysop. This program has been extensively tested on my BBS, and has not caused any problems. There is, of course, absolutely NO WARRANTY of any kind! This program may work for you, or it may not! It will NOT WORK WILL ALL VERSIONS OF THE BNU Fossil driver. It works fine with X00, but has been known to lockup BNU systems. If you use the BNU .SYS file instead of the BNU .COM file, you will probably have better luck with the program. This program is being distributed as FREEWARE. That's right, its gonna cost you all of zero dollars to register it. You *MUST*, however, register it after 10 days of trial use. Please see the section about registration at the end of this document for more details. PLEASE READ THE DOCUMENTATION CAREFULLY. I know you hate reading the stuff... I hate writing it. But it is ESSENTIAL that you read this stuff, or you could miss some important configuration details. Please note that this version of Online INSTAbank will ONLY run on an 80286 machine or higher. If you would like an XT version please contact the author. Major Features of Online INSTAbank: ────────────────────────────────── ■ users may deposit and withdraw time and bytes ■ users may transfer time/bytes to other users ■ sysop may set the following limits: - Maximum Time/Byte Balances - Maximum Daily Time/Byte Deposit - Maximum Daily Time/Byte Withdraw - Maximum Time/Byte transfers to other users (may be disabled) - Maximum number of bank/user robbery attempts (may be disabled) ■ View bank statistical information ■ Send message to another user ■ Sysop may send messages to ALL ■ List accounts ■ Full sysop account editing/deleting locally or remotely ■ Password protected sysop menu for remote user editing ■ Capability to trade time for bytes or bytes for time - Sysop may configure byte/time costs ■ Rob the Bank feature allows a user to steal time and bytes from either the bank or another user (May be disabled) Minimum time/kb to access, as well as odds of winning, are now fully configurable. ■ Supports RA 2.00.x and compatible versions ■ Will not allow a user to take out time if it would cause a conflict with the next scheduled system event (reads system event as defined in RA, or from time left according to DOBBS.BAT if you use a mailer like Front Door) ■ specify path and filename of log file (big deal) ■ Mulitnode support ■ Full transaction logging to a "bank book" ■ Status bar with time/KB adjustment and Chat mode ■ Carrier detection and keyboard inactivity watching ■ User defined START and END ANSI/ASCII screens ■ Support for THEBANK.EXT ■ *AUTO-ACCOUNTS* (see explanation later on in the docs) ■ The BEST part of all... FREE registration! Online INSTAbank should run fine in DOS or Desqview. I have not tested it in any other environments. The program requires approx 150k-200k free RAM to run. Installing Online INSTAbank ─────────────────────────── Online INSTAbank 5.x will NOT run with RemoteAccess 1.11 or earlier. Version 5.x is strictly for RemoteAccess 2.00.g1 and later versions. The latest version for RemoteAccess 1.11 is INSTAbank version 4.8. Clarification of versions: Version 4.8 and 5.3d have the same features. There is no RA 1.11 copy of 5.3e. The 4.x versions are for RA 1.11. The 5.x versions are for RA 2.00.x. The LATEST RA 1.11 version is version 4.8. THIS IS THE FINAL RELEASE FOR RA 1.11! Now that RA 2.00 has been officially released, I will NO LONGER BE PROGRAMMING for RA 1.11. All INSTAbank development from now on will be for the RA 2.00 version of INSTAbank. To install the program, first create a directory (eg C:\RA\DEPOSIT) into which you will copy all the INSTAbank files. Now unzip the original archive file into this directory. All of the bank's files should be stored in this directory. When running the program, be sure that you run DEPOSIT.EXE from the current directory. In other words, change into your new bank files directory (such as C:\RA\DEPOSIT), and then run the program. Security Levels ─────────────── A unique feature of Online INSTAbank is the ability to setup multiple sets of limits. This allows you to have one set of limits for one user, while another user might have a totally different set of limits. You may define up to 100 different sets of limits, based on security levels. SPECIAL NOTE: The first security level MUST be 0. This will be the DEFAULT limits for all users. If a user has a security level that is not listed in your configuration, then that user's limits will be set to the default limits. Setting up the various limits if straight forward. Just enter the numbers in the appropriate fields in DEPMAINT. The maximum Transfer values are the maximum amounts that a user may transfer to another user per day. For example, if a user's maximum time transfer value is 30 minutes, they may transfer up to 30 minutes to as many different users as they wish (as long as they have the time in the bank for the transfers). They may not transfer more than the limit you set to the same user on the same day. * TIME COST: The time cost value is the number of bytes it will cost the user for each minute they purchase. A value of 40 would indicate a cost of 40kb for each minute purchased. * BYTE COST: Byte cost is a little different than time cost. The Byte cost is based on 50kb. The value you set for the Byte cost will be the number of minutes it costs for 50 kb. A value of 1 means it will cost 1 minute to purchase 50 kb. A value of 3 means it would cost 3 minutes to purchase 50 kb. Please note that you may NOT use decimal values. A value of ZERO (0) will disable the feature. You may choose to enable time or byte purchases, but disable the other. You can disable either one or the other or both by placing a zero in each appropriate field. WARNING: Be sure that your Byte Cost is high enough to offset your time cost. If your byte cost is too low, it is possible that a user could continually trade time for bytes, and then trade those bytes for more time, and actually make a profit! Example: Time Cost = 10 (buy 1 minute for 10kb) Byte Cost = 1 (buy 50kb for 1 minute) I have 1000 kb and 100 minutes. I sell my 1000kb for 100 minutes. I now have 0 kb and 200 minutes. I sell back the 100 minutes for 5000 kb. I now have 5000 kb and 100 minutes. I have made a super profit! If, however, you set it up similar to this, a user could not make a profit by trading time and bytes back and forth: Time Cost = 20 (buy 1 minute for 20kb) Byte Cost = 5 (buy 50kb for 5 minutes) I have 1000 kb and 100 minutes in my account. I sell my 1000 kb for 50 minutes. I now have 0 kb and 150 minutes. I sell back the 50 minutes for 500 kb. I now have 500kb and 100 minutes. I cannot make a profit this way. (I lost 500kb!) I find a time cost of 20 (buy 1 minute for 20 kb) and a byte cost of 5 (buy 50kb for 5 minutes) works very well. Sure, you are, in a sense, ripping off the users, but sometimes they need time or bytes and have the other, so they'll gladly trade the extra of one to get some of the other! (To make everything break even, ie no gain, no loss, set the time cost to 10 and the byte cost to 5) If you are unsure if your values will allow the user to make a profit or not, then step through the example as I did above. If you (the user) makes a profit, raise the byte cost or time cost. Robbery Limits ────────────── There are four robbery related fields that you may also setup in your Security settings. These are: - Maximum number of bank robbery attempts per day - Maximum number of user robbery attempts per day - Odds of successfully robbing the bank - Odds of successfully robbing another user The first two fields are straight forward. A user may attempt as many robberies as he or she wants, up to the limits you have set for their particular security level. The third and fourth fields are determine the odds of being successful in a robbery attempt. These are "out of 10" odds. In other words, you have an 3 in 10 chance (or 30%) of being successful if you place a 3 in this field. By placing a zero (0) in a field, you would be making it impossible for a user to successfully rob the bank or a user. By placing a 10 in a field, the user would ALWAYS be successful. If a user is unsuccessful, there is a 50% chance of being caught. If the user is not caught, they will simply be let go with a little warning. If they are caught, they will lose time and KBytes to the bank or the user they were trying to steal from. AUTO-ACCOUNTS ───────────── Auto-Accounts are simply accounts that are automatically updated, or "stocked", whenever AUTODEP.EXE is run. AUTODEP.EXE will scan the configuration file for any security levels that are setup to have "auto accounts". It will then scan the bank data file, and update all matching bank accounts, filling the time and kbyte balances to the defined amounts. What is this good for? Well, here is one sample of how this can be used: You could set this up to allow users to have a weekly download limit, instead of a daily one. Give your users a ZERO (0) KB download limit, so that they cannot download any files without taking KB from the bank. You then setup an "auto-account" in the security level setup screen. For this example, lets assume you want your users to have a 5 meg/week download limit. Setup the Maximum KByte Balance to be 5megs (5120kb where 1meg=1024kb). When the user's account is created, it will AUTOMATICALLY have a balance of 5 megs! They can then use up as many of these KBs as they wish (you set maximum daily withdrawal limits, of course), but once they run out, they must wait until the next week to get any more KB! The accounts will be automatically reset to the 5 meg balances when you run AUTODEP.EXE. For this weekly example, you would set AUTODEP.EXE to run in an event once a week. You can also setup an automatic time balance. The MAXIMUM BALANCE fields will be used to determine how much time/KB will be placed in the accounts when AUTODEP.EXE is run. You may still setup maximum daily withdrawal, deposit, and transfer limits. To setup an Auto-Account, just tag "AUTO-ACCOUNT" as "Y"es in the limits configuration screen (DEPMAINT.EXE). General Configuration ───────────────────── The "Configuration" option on the DEPMAINT menu allows you to setup the following: - Registration code - SysOp name - BBS name - SysOp security level - SysOp password - Log filename - Path to DOBBS.BAT - Days to keep transaction history - Minimum time to rob - Minimum bytes to rob Registration code: Your 12 character registration code should be entered into this field. SysOp name: Your SysOp name should be entered into this field. BBS name: Your BBS name should be entered into this field. SysOp security level: This is the security level that a user must have in order to access the "SysOp" menu. The SysOp menu allows you to adjust user's accounts, send messages to "all", etc. Anyone with this security level or higher will be able to access the sysop menu by pressing "*" on the main bank menu. SysOp password: This password will ONLY be required if someone tries to access the SysOp menu in the door. This is not required for local editing with DEPMAINT. Log filename: This is the filename (and optionally the path) of the log file. If this is left blank, no log will be written. Example: C:\RA\DEPOSIT\DEPOSIT.LOG Path to DOBBS.BAT: DOBBS.BAT is a file created by FrontDoor (and possibly some other mailers), which is used by RemoteAccess to determine how much time a user has left before the next system event. INSTAbank will read this file (if it can find it) and will use this to limit any time withdrawals. By doing this, you can be sure that a user will not be able to over-run your system event times. Example: D:\FD\ (NOTE we do NOT include the filename DOBBS.BAT!) Days to keep transaction history: INSTAbank stores a "bank book", which records all transactions made by users. When DEPMAINT is run in maintenance mode, and the data files are cleaned up, all transactions that are older than the number of days you specify here will be deleted. Minimum time to rob: This determines the minimum number of minutes a user must have before he or she may attempt to rob the bank or another user. I recommend that you at least require them to have 10 minutes, so that they will lose some time if they are caught robbing. Minimum Kbytes to rob: This is the minimum number of Kbytes that a user must have in his or her account in order to attempt a robbery. (some systems do not have files, and thus users will not have any KB in their accounts. For situations like this, just set the minimum KB required to ZERO (0)). The next step is to setup INSTAbank to run as an external door from RemoteAccess. The program should be installed as a type 7 external program in RACONFIG. The program requires that you pass the path to EXITINFO.BBS and DORINFO1.DEF to it on the command line. To do this, I recommend that you create a batch file (DEPOSIT.BAT). For single node systems, this batch file may look like this: @ECHO OFF CD \RA\DEPOSIT DEPOSIT.EXE C:\RA\ CD \RA Your 'optional data' in the RemoteAccess menu configuration for this item would be *C /C C:\RA\DEPOSIT.BAT For multinode systems your batch file should look similar to this: @ECHO OFF CD \RA\DEPOSIT DEPOSIT.EXE C:\RA\LINE%1\ CD \RA Your 'optional data' field in the RemoteAccess menu configuration for this item would be *C /C C:\RA\DEPOSIT.BAT *N The *N will pass the current line number that the user is on to your batch file. The batch file will, in turn, point to the proper line directory. If you run a multinode system then you'll know what I'm talking about here, so more explanation should not be necessary. With the above multiline example, assuming you have 2 lines on your system, if a user logged onto line 1 ran the bank, the %1 would become a '1', so the directory being pointed to would be C:\RA\LINE1\. If a user was on line 2, then it would point to C:\RA\LINE2\. Replace the LINE in LINE%1 with whatever directory names you are using for your separate RemoteAccess line directories. Thanks to Richard Bollar for pointing me in the right direction for multinode setup. If you run into memory problems you may want to use the *M feature in the RemoteAccess menu configuration field for 'optional data'. You should not need to do this however. I run the program without the *M parameter, both in DOS and Desqview environments. The program will use ANSI colour codes if ANSI is enabled in the DORINFO1.DEF file. If the user uses ANSI on the BBS, then they will have ANSI in the bank. Avatar is NOT supported. If they do not have ANSI enabled then it will run in plain ASCII mode. Options available to the users: The options that are available to users are: - Deposit Time/Bytes - Withdraw Time/Bytes - List accounts - Send message to another user (70 character max length) - Rob the Bank (or another user) *only if enabled by sysop - Transfer time/bytes to another user - Statistics - Version Information - Trade Time for Bytes/Bytes for Time - View past transactions (bank book) - Expert Menus - Quit - * Sysop (available to any user who's security level matches the Sysop Security level setting in the config file) The Rob the Bank feature will appear on the menu if the sysop has disabled this feature, but it will not be accessible. The sysop menu will only be available to users who have a security level that is equal to or greater than the level you set in the configuration file. This option will NEVER be displayed on the menu, even if the user is allowed to access the function. The key to use to access the sysop menu is the * key. Users may only view their own bank books. If a user has a security level equal to or higher than the level defined as the sysop security level, then they will be prompted for the name of the person who's bank book they want to view. In other words, if the user has access to the sysop menu, they will also be able to view anyone's bank book. Start and End ANSI/ASCII screens ──────────────────────────────── If the files START.ANS and END.ANS (or .ASC) are found in the bank directory, they will be displayed to the user just before and just after the title and copyright notice screen. In other words your ANSI/ASCII screens will be the very first and the very last things displayed by the program. Only one special character is currently supported, and that is the CONTROL-A character (). If this character is found the bank will wait until ENTER is pressed before it will continue displaying the file. START.ANS and END.ANS will be displayed to users who have the ANSI setting enabled. Otherwise START.ASC and END.ASC will be displayed. The user may press 'S' during the display of the screen to stop it. THEBANK.EXT - Using external programs to modify accounts. ─────────── ────────────────────────────────────────── Some doors create a file called THEBANK.EXT, which contains information that is used to adjust bank account balances. Online INSTAbank now supports this file. Sample THEBANK.EXT: JOHN SIMPSON:30 BILL DYKSTRA:-20 SEAN LAWSON:10 Each name is followed by a colon and a time value. If the time value is positive, that amount of time will be added to the user's account. If the time value is negative, that amount of time will be removed. If the user's name is not found in the bank files, a new account will be created. Note: Accounts will never have negative values. If THEBANK.EXT says that 15 minutes should be removed, but the user only has 10 minutes in the bank, then only 10 minutes will be removed. Any balances that exceed the user's maximum balance will be automatically erased the next time the user enters the bank. To process THEBANK.EXT you must run the EXT_UTIL.EXE program. This program will read THEBANK.EXT from the current directory, and will apply the necessary changes to the users' accounts. THEBANK.EXT will be deleted when the program is finished. DEPMAINT.EXE - Maintenance Utility ────────────────────────────────── This program contains the same options that the Sysop menu in DEPOSIT.EXE does. This is for LOCAL use only, and is very handy for changing account balances while a user is online. You cannot use the sysop menu within the INSTAbank program itself when a user is online, as it will read their info from DORINFO1.DEF and EXITINFO.BBS. Running DEPMAINT D:\PATH\ /MAINT will CLEAN THE DATA FILES. This option should be used now and then to clean out the data files. Old messages (any messages that are marked as read) will be deleted from the message file, and any users that are no longer located in USERS.BBS will be deleted. Accounts with no time and no bytes (empty accounts) will also be removed. The regular DEPOSIT.LOG file will indicate who's accounts have been deleted. This option will also clean out the transaction file, deleting records of transactions that are older than the number of days specified in DEPOSIT.CFG on line 10. D:\PATH\ must be the path to your CONFIG.RA file. You may run this program in your nightly events if you desire. Be sure to include the path to CONFIG.RA as the first parameter. Be sure to use the /MAINT parameter as the second parameter! No parameters are needed if you are only running the editor. Running DEPMAINT /MONO will run the program in monochrome mode. Using the editor ──────────────── The editor is rather easy to use. All the options available to you are shown on a menu, and you simply select the option you want to use. When editing user accounts, it is very important that you keep any dates that you change in MM-DD-YY form. A new field in the user account record is the AllowRob field. This field can be 0, 1, or 2, and will indicate if the user may be robbed or if the user has chosen not to use the rob feature. 0 = User may not be robbed (and may not rob others) 1 = User may be robbed (and may rob others) 2 = Ask user for their preference the next time they enter the bank. READMSGS.EXE - Message reader ───────────────────────────── This util will let you scroll through and read the messages in the DEPOSIT.MSG file. These are the messages that users send to eachother, and that the bank sends to users under certain conditions. You may toggle the "message read" status as well. To do this, highlight the message you want, and press ENTER. The message will be zoomed onto a window, and you can then press SPACE BAR to toggle the message read status. Remember, by setting the status of a message to READ, it WILL be deleted the next time DEPMAINT is run with the /MAINT parameter. If you want to delete a message, just set the status as READ, and it will be deleted the next time maintenance is run. Distributing Online INSTAbank ───────────────────────────── Please feel free to distribute Online INSTAbank. Please distribute only the original archive, in unmodified form. NO FEE MAY BE CHARGED for this program, other than fees necessary to cover the cost of distribution. This may be included in shareware/freeware packages, such as CD-ROM disks of shareware, etc. Registering Online INSTAbank ──────────────────────────── You must register Online INSTAbank after 20 days of evaluation use. If you continue to use the program after the 20 day trial period, please register it. Registration is *FREE*, so you have no excuse to avoid registering. Why do I require registration if its FREE? I want to know how many people are using the program, so I can determine if further development should be done. I will gladly accept suggestions and ideas for the program. If there is a feature you would like to see, let me know. Also, PLEASE let me know if you encounter any bugs of any kind! Custom versions of the program may be written on request, for a very modest fee (usually less than $25 Cndn). If it is a very small modification, and most are, then there will be no charge. I will just consider it an "implemented suggestion". It has been suggested that this is not freeware, but rather cardware or some other such system, because I require registration. I do not agree with this, however. This is entirely freeware. I don't ask you to go buy (or steal!) a postcard to send me, or anything else at that matter. All I ask is that you tell me by one means or another, that you are using the program! I think that's pretty darn free, and pretty darn fair! Future Plans: ──────────── Please send me your ideas. If you have a suggestion for the bank, and it is something that I can add without too much work, I'll do what I can to implement your suggestion. Your ideas are welcome! Send em to me! Many users of INSTAbank version 4.3-5.3e sent in suggestions, and many of them were implemented. Some of the things suggested that I added/changed were: - fix up menu alignment - get rid of the annoying double characters on local screen (bug) - START and END ANSI/ASCII Screens - Enhanced user editor (this was already planned though) - Status bar with time adjustments (I also added KB adjustments) - support for THEBANK.EXT - messages to ALL - AUTO-ACCOUNTS - Configuration file editor - Keyboard inactivity watch - The new (5.3e) method of calculating daily totals I have even made minor customizations for people...for Free! --------[Cut Here]------------------------------------------------------------- Online INSTAbank 5.3e R E G I S T R A T I O N F O R M ~~~~~~ ~~~~~~~~~ ~~~~ ~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~ *Sysop Name: _______________________________________________ *BBS Name: _______________________________________________ Address: _______________________________________________ _______________________________________________ City: ________________________ Prov/State: __________ Postal/Zip Code: __________________ Country: __________________ BBS Phone: __________________ Max Baud Rate: _____________ Fidonet Address: _________________________________________ If you have a Fido address, I can place your registration code on hold for you, or route it to you. Please check one: Place code on HOLD for pickup: [ ] Please send my code via routed netmail: [ ] If you plan to call the BBS to pickup your registration code, please fill out the following: You *ONLY* need to fill out this information if you want me to create an account ahead of time for you (and you are mailing this form in. If you are simply going to call the BBS to get your Registration code, don't worry about this logon info...) Real Name:_______________________________ (do NOT use an alias) Password to use:_________________________ ANSI? (Yes/No):__________ Where did you obtain your copy of Online INSTAbank? ________________________________________________________________ Comments/Suggestions: ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ ________________________________________________________________ --------[Cut Here - end of registration form]------------------------------------------------------------- Mail the above registration form to: Bill Dykstra 189 Bristol Road Newmarket, Ontario. Canada. L3Y 7X9 or call The BillBoard BBS (416) 898-2443 14.4k v.32bis/v.42bis 8,N,1 and leave a message to Bill Dykstra (or sysop), with this form file attached to the message. Netmail: FidoNet 1:250/932 NOTICE: As of October 4, 1993, the area code for The BillBoard BBS will change from area code 416 to area code 905. The new number for The BillBoard BBS will then be (905) 898-2443. ──────────────────────────────────────────── See SUPPORT.DOC for other registration sites. ──────────────────────────────────────────── If you would like me to send your registration code to you in the mail, please include a self addressed stamped envelope (why should I pay if you don't have to!?). If you do NOT include an envelope, then I will assume that you will be calling the BBS. Of course, you might have trouble getting Canadian stamps if you're in another country, so try to get stamp vouchers instead. If you cannot get these, and there is no way to reach you via E-mail, just send in the form. I'll get the code to you one way or another. I will create an account for you on the BBS if you fill out the appropriate information above. I will leave you a message with your registration code in it. Please allow enough time for the letter to arrive here. I will post a message with your reg. code the same day that I receive your letter. You do NOT have to mail this form to me, however. You may call the BBS, upload this form to me (File attach it to a message), and then page me. If I'm around, I'll get your code on the spot. If I am not around, you'll have to call back. I usually check mail every night at 5:45pm, as well as at other random times. If you leave a message before 5:30pm it will almost surely be answered by 6:30pm. (see above for BBS phone number) You may also simply netmail the registration form to me at Fidonet 1:250/932. *NEW* (as of February 1993) *NEW* You may now register ONLINE! Just call the BBS, logon as a new user, and select the "O"nline registration command from the newuser menu! You don't have to wait for validation or for a reply from me! Just answer the questions the program asks, and it will spit out your registration code for you right away! ───────────────────────────────────────────────────────────────── A few people have asked me WHY is this program freeware? The answer is simple. SysOps have enough to pay for already, so why make matters worse? This was a fun project... you shouldn't have to pay for me to have fun! Need to access the bank files yourself? If you are writing a door or utility, and you would like to be able to read and write user's bank account records yourself, you may contact me for the structures of the bank's data files. Preferably you should use THEBANK.EXT method of accessing accounts, but if this is not sufficient, please let me know, and I'll see what I can do. --Bill Dykstra NEW! (August, 1993) INSTAgames v1.0! INSTAgames v1.0 is an Online INSTAbank addon program. INSTAgames is a set of lottery games for users to play. There are three different lotteries that may be played: - Pick 3 (daily, weekly, and monthly) - Super JackPOT (weekly and monthly) - Raffle (weekly and monthly) INSTAgames will work with INSTAbank v4.8, v5.3d, and v5.3e. FileRequest "IGAME" from 1:250/932.