Personal Information Library (PIL) Version 1.00 Copyright (C) 1995 By Timothy E. Peterson All Rights Reserved A Product of Merlin's Realm DISCLAIMER The author has taken every precaution to insure that no harm or damage will occur on computer systems operating this package. Nevertheless, the author shall NOT be held liable for whatever may happen on your computer system or to any computer systems which connects to your own as a result of operating this package. The user assumes full responsibility for the correct operation of this software package, whether harm or damage results from software error, hardware malfunction, or operator error. NO warranties are offered, expressly stated or implied, including without limitation or restriction any warranties of operation for a particular purpose and/or merchantability. If you do not agree with this then do NOT use this program. LICENSE AGREEMENT The Personal Information Library, herinafter referred to as the PIL, program, support files, and documentation are copyrighted products of Timothy E. Peterson. Timothy E. Peterson reserves all rights to these products. This is protected by the United States of America (USA) and International Copyright Laws. In no way shall the components of the PIL software package be reproduced or modified in any form or method without prior expressly written permission from Timothy E. Peterson. Tampering with or altering the contents or integrity of the program software package is prohibited. No fee may be charged by any agency other than Timothy E. Peterson beyond the cost of distributing unregistered copies without prior expressly written permission from Timothy E. Peterson. The modem communication portions of this software comes from the DDPlus Door Driver Package and was written by the authors of that package. The DDPlus Doordriver kit has been used for the communications, interrupt handling and some utility functions and that part of the software remains copyrighted by the authors of the DDplus Package. This program is distributed under the Shareware concept. You are allowed to operate this program for a trial period of thirty (30) days. After this trial period, you must register the program or discontinue its usage. Again if you do not agree with this then do NOT use this program. INTRODUCTION: ------------ This door program will allow all the users on your BBS to get to know one another. When a user enters this door, they can create an account. The PIL will ask them multiple questions about themselves such as what sex do they think they are, kind of books they like to read, hobbies, etc. Once the user information is entered, all users on the BBS can look at it. User accounts are saved by alias names and it is suggested that they use the same alias in the PIL as they do on the BBS. Any user can retrieve information on another user by simply entering the alias. Users can also look at all the users that have filled out the questionaires with a simple key stroke. If a user wants to change what they have entered about themseleves, the PIL will allow them to do this. The only item that can not be changed is the alias. The PIL will not allow a user to create a second account or change information in someone elses account. An editor is also provided that allows the Sysop to change information for any user. Users can also be deleted with the editor and all user alaises can be deleted. This allows the Sysop to clean up records when the only word a certain user knows is FU$% YOU. I get them on my system every now and then and I can't be the only one . REQUIREMENTS: ------------ At this point in time the only requirements are FILES=10 (or more) in your config.sys file and ANSI.SYS. SHARE must also be loaded IF you intend to use the program in a multi-node environment OR under DesqView. The program is RIP aware but NOT a RIP program at this time. A FOSSIL is NOT required to run the program, although one will be supported if it exists. Automatic time slicing support is provided to most common multi-taskers as well. Files Included -------------- Below is a listing of all files for the this program. If you are missing ANY of these files (except for the text files), the program will NOT function. Feel free to give out copies of the ENTIRE archive package of this program but please make sure all the files below are in that package: B4UASK.DOC - Troubleshooting instructions to help set up this door. BUGRPT.FRM - A form that you can use to report bugs in the PIL software. You are also encouraged to use this form to make reccomendations for improvements. FILE_ID.DIZ - A short description of the PIL. program 1.CTL and - These are sample control files that I program3.CTL use on my BBS. program3.CTL provides an illustration of how to use non-standard IRQs. These are the exact control files that I use on my BBS. I do not use a fossil with the PIL. HELP.TXT - This file provides instructions on how set up control files using the DDSetup program. If manully editing control files makes you nervous, use this program. This file also provides command line switches that can be used. HISTORY.DOC This is a text file that describes the development of the PIL. REGISTER.FRM - This file contains instructions on how to register the PIL. SAMPLE0.BAT - These are sample batch files to assist you SAMPLE3.BAT is setting up the PIL. A couple of these are used on my BBS. SYSOP.DOC - This document. A Setup guide. ACCOUNTS.DAT - All user entered information in the PIL is kept in this file. To delete all users from the PIL, delete this file and create a zero byte file called ACCOUNTS.DAT. DDSETUP.EXE - If manually editing control files makes you nervous, run this program and it will make the control files for you. DVAWARE.OBJ - Machine language routines required for DESQview operation. EDITOR.EXE - This program allows the Sysop (you) to edit any user's record. You can also delete users from the database. KEY.DAT - The PIL will not run without this file. PERSONAL.EXE - This is the executable for the PIL and must be run from your batch file. SLASYNC.OBJ - Machine language program for Asynch communications. Installation ------------ --> NOTE: programDIR is used in place of the program directory in the documentation from this point on. 1. Create a directory for the program: example: "WILDCAT\DOORS\programDIR" 2. Make sure that ALL files listed above from the program package are moved into that directory. 3. Type "DDSETUP.EXE" and hit the enter key. The first thing it will ask you is what the name of the CTL file is. Type in "GAME1.CTL" and then proceed to the other settings. After you are done, the GAME1.CTL file should be correctly configured. Two versions of a fully commented CTL file are provided for manual configuration. One is identified by the program title (example: GAME1.CTL) and this is the UN-EDITED version and the other is identified as GAME3.CTL is what a CTL file should look like AFTER it is edited. If all else fails - try the one I use on MY support BBS (GAME3.CTL), except comment out the non-standard IRQs and port three if they are not applicable. If you have fossil drivers, be sure to uncomment the 'fossil' option. If you have a modem set to a non-std IRQ be sure to use the PORT# option for that comport. A CTL file generated by DDSETUP.EXE will have NO comments and look quite different from my samples, but they WILL work just as well, never fear. Where to put this file? Put this file wherever you are running the program executable file from. If you are running multi-node, you could put a copy in each node directory and run from there. If you change directory to the program directory put the file here. See the example SAMPLE#.bat files. 4. If you are registered then you will be able to delete and edit other user files from the editor. If you are NOT registered then you will not be able to do this. In the unregistered version, you can have a maxmimum of 15 user records in the database. The unregistered version allows you to have as many as you want. The PIL was designed so that it is ready to run as soon as it is unzipped. All you have to take care of is the CTL and BAT files. That's all there is to it! If you ever need to reset or re-start the PIL, just delete the ACCOUNTS.DAT file and create a zero byte ACCOUNTS.DAT file. 5. When you are ready to register the PIL, select the registration option from the editor. It will ask you who the PIL is to be registered to. Enter this exactly like it appears on your registration form (it is case sensitive). Once this is entered, it will ask you for your registratin number. Enter this number. Once registered, you will be able to have umilimited accounts (within your computer's limitations), and be able to delete and change other users accounts. Your registration name also appear above the main menu of the PIL and editor. 6. To insure proper multi-node use, DOS SHARE must be loaded prior to the program and prior to DESQview. 7. In order to run the program program online the following parameters may be used. "/Bxxxxx" This tells program.EXE to lock its baud rate at xxxxx. In order to get the most efficiency out of a high speed error correcting modem (9600 baud or above), you may lock the baud rate to a speed higher than what the caller is actually using. By locking the baud to say 38,400, the modem can compress text data that is being sent and achieve a baud rate much higher than the actual transmission rate. This will lock the baud rate at the same value for all nodes that use this command line. If you perfer a more selective way to lock baud use 'LOCKBAUD' command in the program.CTL file. "/Cx" (where x is 1..4) This specifies a comport number. Some bbs software does not create door information files (dropfiles) that contain the comport number. If your bbs does have a comport listed in the dropfile then there is no need for this parameter. The default is comport 0, local mode. "/E" - Expanded Memory Specification If your machine has over one megabyte of memory, then you may have some available. PERSONAL.EXE can utilize EMS to improve program performance and reduce conventional memory requirements. This command will tell PERSONAL.EXE to use EMS memory to hold its overlay buffer. Otherwise disc area may be used to hold this buffer. This needs a memory manager and when enabled and is compatible with DESQview. Default is NOT to use available EMS. "/L" This tells PERSONAL.EXE to load up in LOCAL mode. This is good for testing or when a sysop just wants to "try out" the door without messing with his BBS setup. The "/L" mode will ask the user for his name and run the door in local mode. "/Nx" (where x is 1..9) This specifies a "node number". Some bbs software support multinode environments in which you must know the node number of the drop file to use. For example, RBBS-PC uses DORINFOx.DEF. If you specified "/N2" then program.EXE would use DORINFO2.DEF. "/Mx" (where x is up to 2 filename acceptable characters) Used to specify one of Multiple control files. If you have created more than one GAME#.CTL file (GAME1.CTL, GAME2.CTL, etc.) for each node or network PC then you can select the one you want by using the /M parm. Example: "/M2" will force PERSONAL.EXE to use GAME2.ctl. "/Pyyy" This specifies the path to the drop files. For example, "/PC:\WILDCAT\WCWORK\NODE1" would tell program.EXE to look for the drop file in C:\WILDCAT\WCWORK\NODE1. If this is left out the program assumes the drop file is local. "/R" To force local RIP for the sysop. Used only if the program has RipLink built in and the door supports RIP. Use AFTER the /L parameter if you are using the door in local mode. "/V" This command will tell PERSONAL.EXE not to show any display on the local screen. Only a colored screen and a message will be displayed. The cursor will not move as it will be turned off. Saves a little processing on multi-tasking systems. "/W" This flags the program that a network is present even though no multitaskers are detected. This is useful if the door is run on a network such as Novell that doesn't use multitaskers. COMMON ERRORS 003 File path not found. Check to make sure the program directory is correctly named as programDIR. 201 Files not found. Check to make sure that all required programs files are in the programDIR directory. 8. Install the door into your BBS software (see your BBS software documentation for more information). A batch file is normally used to do this. To run the program just have your batch file change to the programDIR directory and run PERSONAL.EXE - Thats all there is to it! Four different batch files sample are included to help you run the program. These are included with the program for editing and your use. Remember, when writing the batch routines for my programs you must ensure that the program is run from it's home directory AND that the program knows where to find the drop file. Satisfy these two requirements and you should have no problems running the program as long as the other setup criteria has been met. For dorinfo systems try using the following: Sample Batch File ----------------- COPY DORINFOx.DEF \RBBS\DOORS\programDIR\*.* CD \RBBS\DOORS\programDIR program x <-=- NODE number !!DO NOT USE "x"!! del dorinfox.def CD \WC30 --> Please note that you replace the "x" with the appropriate node number. Ex: Dorinfo1.def ; Dorinfo2.def ; etc... 9. Surprise! There is NO separate daily maintenance to be performed. RESTRICTIONS ON THE UNREGISTERED program ------------------------------------- Until the program is registered the following restrictions are in effect: a. A flashing banner will appear above the PIL menu, indicating that it is unregistered b. The Sysop can not change information that users have entered in the database or delete users from the database. The users themselves can still change their own information. c. The PIL will not allow any more than 15 user records to be entered. d. Registering the program disables both of the above and allows you to alter virtually all user information. e. Once you are registered, any future updates can be obtained free through my BBS and my upgrades are ALWAYS easy to implement! f. I am always improving my programs - so check my BBS for a more current version. WHAT TO DO IF THERE ARE PROBLEMS -------------------------------- Every effort is made to ensure that the program runs correctly before it leaves my BBS as Shareware. If you are experiencing problems please do the following BEFORE calling me: 1. Read ALL the SYSOP.DOC to ensure you have setup the program and have met all the program requirements. 2. Use the B4UASK.DOC as a checklist to ensure that you have not done anything wrong. Multinode use ------------- This program supports multinode use and provides automatic multi-tasker support (time slice releasing) for a wide variety of multi-taskers. Common Problems (Locked Bauds, High Speed modems, etc) ------------------------------------------------------ 1. The program does NOT require a fossil driver to run. 2. If you are running a high speed modem (9600 baud or above), then I suggest you run your bbs/mailer/doors at a locked baud rate. On high speed error correcting modems, locking the baud rate will have a noticeable increase on the speed of text that is sent. It's beyond the scope of this document to discuss configuring your BBS and mailer for a locked baud rate; you may wish to consult those docs for information on that. Here are a few things to keep in mind when setting up program with a locked baud rate: a. When using a locked baud rate, I highly recommend using a FOSSIL driver. This program will work at high speeds without one though. BNU is a good fossil driver which can even be loaded and unloaded before and after you run this program. b. If you are using a fossil, then make sure to tell the fossil that the port is locked. For BNU, to lock com1: at 38,400, you would use something like "L0=38400" on BNU's command line. c. If you lock the baud for one program, it must be locked for everything. You can't lock the baud for just this program, but not your BBS/mailer. d. You may need to use the /B switch on the program.exe Command line to specify the locked baud rate. For 19,200 this would be "/B19200" and for 38,400 this would be "/B38400". Please note there is no space between the "/B" and the baud rate. 3. What follows is some information on possible strange situations that may occur: a. Low speed users can play the program, but high speed users get garbage. - If you are not using the DORINFOx.DEF or DOOR.SYS drop file then you may wish to find a converter program to convert whatever drop file your BBS produces to the DORINFOx.DEF or DOOR.SYS format and tell program.exe to use that. Several converter programs are readily available on most BBS systems. CallDoor is a good one if you can find it. I have it on my BBS for download if you need it. b. The program hangs up when a user enters the program. - Sounds like the program is getting the wrong baud rate somehow. Try switching over to the DOOR.SYS drop file method if possible. c. Text and screens are getting cut off. - If you are running with a locked baud, then this could be caused by some sort of FLOW CONTROL problem. Try using a fossil if you aren't already. d. If you're using something other than the DOOR.SYS drop file, then I always suggest trying to use DOOR.SYS if possible. It is the most reliable method and has had the most testing. If that is not possible try DORINFOx.DEF as an alternative. e. A door locks up node 1. This can happen with fossils or the internal communications routines because it uses the default comport of 1 when NONE is found in the dropfile or program.ctl file. To correct this make sure the right port is shown in the dropfile OR program.ctl file. Also, make sure that two ports are not using the same IRQ's. If you are using a non-standard IRQ, make sure that is identified in the appropriate CTL file. f. ANSI is reflected correctly on the local screen but the user is getting garbage. Assuming the user has ANSI installed then most likely the problem is at your end. First make sure you have configured the program.ctl file to show the correct locked port rate. Second make sure the dropfile is passing the locked port rate INSTEAD of the actual conncet rate. If it is not passing the locked port rate then you may need to use a different dropfile format OR use a dropfile converter program to change the line to show the locked port rate INSTEAD of the actual connect rate. "Corrupted" data files ---------------------- It is possible that something could happen to your program data file. A power outage, program crash, or other event could damage the data files. If you get one of these messages, then the best thing to do is to delete the ACCOUNTS.DAT file and create a zero byte ACCOUNTS.DAT file. If the key file gets corrupted, simply delete KEY.DAT and create a zero byte KEY.DAT file. If the program is registered, once the zero byte KEY.DAT file is created, just run the EDITOR and re-enter the registration information. CREDITS: -------- This relatively small section is just to recognize the GOOD people who have made this door a possibility. The DDPlus Team - Thanks to Scott Baker, Steve Lorenz, Bob Dalton, Andy Stewart, Tom Morgan and other contributors for that great turbo pascal door kit. With out these guys, I would have spent most of my time writing communications routines instead of the actual program. Merlin's Realm - The users on my BBS helped me greatly Users in designing this program. There suggestions have helped make this program much better than it would have been. They also put up with many resets of the PIL until I finally got it right. It was also my users that kept requesting a door like this. Since I could not find one, they convinced me to write this program. For this, Thank you. DESQview is a registered trademark of Quarterdeck Office Systems. Doordriver kit is proprietary software by Scott Baker. Ripscript & Ripterm are registered trademarks of TeleGrafix Communications. Where to reach me ----------------- I can usually be reached at my BBS system, which should be listed in the section entitled "registration" which is below. I also habitually monitor the alt.bbs.wildcat USENET newsgroup Registration ------------ If you or your users enjoy this program, then please register it. Information on price and how to register is shown on the enclosed REGISTER.FRM. Registration will allow additional options and entitle you to life time support through my BBS. BBS Support includes unlimited free updates and upgrades (not like some door program authors who charge for major upgrades/updates!) through my BBS. To register this program just print out the registration form (REGISTER.FRM) file included with the program and send it with your check or money order to: Merlin's Realm PO Box 62624 Colorado Springs, CO. 80962 HOW TO REACH ME BY MODEM --------------------------- MERLIN'S REALM (USA) (719) 481-9881 (USR 14400 - 28800 baud) Internet merlin@merlins-realm.com Reminder: You will be mailed a LETTER with your registration code. Just allow an appropriate amount of time (a week or two) after dropping your check in the mail for it to arrive to me and the code to be sent by mail back to you. If you need it sooner log onto my BBS, leave me a message telling me you mailed the registration and when I receive your check or money order I will post a private message on the BBS giving you the key code. If you do it this way please allow at least a week from the time you mail it to the time you call and get your code. If you go the BBS route you will ALSO receive a key code by mail. REMINDER: No disks are sent, if you need the most current version you must call my BBS for it or request it on the registration form. Bug Reports/Comments/Suggestions -------------------------------- I have made every attempt to make sure the program is free of bugs, BUT the possibility always exists that one may have been missed by me or the playtesters. If you find a bug, or have a suggestion or comment to make which would make future versions better please print out the BUGRPT.FRM and mailer, fill it out, and send it to me. I read ALL of them and those people that lead me to find a bug or generate a better program will receive credit in the program documentation. PLEASE DO NOT NOTIFY ME OF PROBLEMS AND EXPECT ME TO FIX THEM IF YOU HAVE FAILED TO PROVIDE ME WITH THE BUGRPT.FRM AND OTHER INFORMATION I REQUIRE AS STATED IN THE B4UASK.DOC.