Beijing Paradise BBS Backup

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

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

Wrap

Text File | 1992-12-25 | 41.9 KB | 1,228 lines

The Ultimate Account Management System version 1.03 August 1992 If you need support, we have an echoed conference on Salt Air carried at present by our support board, Salt Air, and TDS Intl. If you want to pick up this conf for our own reading, feel free to do so. Quick Installation For quick installation see the installation section in this document file, or enclosed file QUICK.DOC. Display User Info It is recommended that if you use the "Display User Info at Login" in PCBSetup (Options #1 - top right hand side of screen), that it be set to NO. If Display User Info is set to NO, then TUAM will display all the necessary information, and will appear seamlessly as a part of PCBoard. If Display User Info is set to YES, there are possible situations where the PCBoard display and the TUAM display will be separated by the system. This will cause an uneven flow to your screen display, making a somewhat less desirable display to the user. If you want NO display at all, set the Display User Info in the Security File to NO for that specific security level. ( see Display {Dsp}) The User Info displayed in TUAM will display all the data as shown by PCBoard, plus ratio information if used for the specific user, bytes in account, bytes in session, and reset frequency if specified. NOTE : It is not recommended that both displays be used at once. We do recommend for clean displays, and a cleaner interface to PCBoard that the Display option in the security is the ONLY one that is used. Below is an example of an actual PCBoard login with PCBoard displays disabled, and TUAM displays enabled. NOTE: TUAM displays are intelligent displays, and will display only the information that is appropriate for the specific user. Therefore not all information will display. The user below is not on ratios for example, so upload and download ratios are not displayed. What is your first name? Brian Backland Password (Dots will echo)? (............) Brian, you have new mail waiting in the following conference(s): Main Board ... Account bytes reset. Account Time reset. Last Date On : 11-13-92 Expiry Date : 09-23-93 Number Times On : 450 Page Length : 23 Expert Mode : On Security Level : 241 Total # of DLs : 101 Total # of ULs : 45 Total Bytes DLed : 12,286,459 Total Bytes ULed : 5,191,453 UL Credit Ratio : 2:1 Bytes in Account : 5,120,000 Bytes in Session : 5,120,000 Bytes Reset Freq : Daily Last Bytes Reset : 11-14-92 Time in Account : 1,440 minutes Time Reset Freq : Daily Last Time Reset : 11-14-92 (1438 min. left) Main Board Command? If this display moves across the screen to quickly then create a BYE file. This file will be displayed upon exit from the door. You can display whatever information you wish in this file, including PCB @ codes for color and names. We DO NOT clear the screen prior to exiting the system, therefore a @WAIT@ will pause the display. (Or whatever @ code you wish to use) A sample BYE file to simply pause the display may be: @WAIT@ Display Files There are several display files available to you as a SysOp, which will provide enhanced displays to your users above and beyond what we have provided. All of these files support security specific files, PCB @ language codes, and PCB graphics as well as the G (ANSI graphics) extensions and language extensions. B0 B0 File This file is displayed to your users instead of the normal text. This will provide information if you wish, letting the user know why they are locked out of the door. All of the normal PCB @ codes will function in this file, as will the PCB @ color codes. This file will also support SECURITY, GRAPHICS and LANGUAGE extensions automatically. BYE Bye File This File is not normally used, but will be displayed at the exit of the TUAM door. It will support all the PCB @ codes if you find a use for it. This file will also support SECURITY, GRAPHICS and LANGUAGE extensions automatically. NOB Byte Fail This File is displayed if the BYTE ratio fails. This file is provided and can be edited, it will support all the @ variables and @ color codes as well. This file will display when bytes are NOT distributed to a user on BYTES or BYTES/FILES ratio who fails the BYTES ratio test. We have included @WAIT@ in the demonstration file to keep the screen displayed for the userr This file will also support SECURITY, GRAPHICS and LANGUAGE extensions automatically. NOF File Fail This File is displayed if the FILE ratio fails. This file is provided and can be edited, it will support all the @ variables and @ color codes as well. This file will display when bytes are NOT distributed to a user on FILES or BYTES/FILES ratio who fails the FILES ratio test. We have included @WAIT@ in the demonstration file to keep the screen displayed for the user. This file will also support SECURITY, GRAPHICS and LANGUAGE extensions automatically. Below is listed a listing of all possible screen displays upon login. Last Date On : <<--- Last Date User was on System Expiry Date : <<--- Expiry Date of User Number Times On : <<--- Number of Times user has been on this system Page Length : <<--- Default Page Length for user Expert Mode : <<--- Expert Status Security Level : <<--- Security Level of user Total # of DLs : <<--- Total # of Downloads Total # of ULs : <<--- Total # of Uploads Total Bytes DLed : <<--- Total Bytes Downloaded Total Bytes ULed : <<--- Total Bytes Uploaded Bytes DLed Today : <<--- Bytes Downloaded Today UL Credit Ratio : <<--- UpLoad Credit Ratio (see ULP) File Ratio DL:UL : <<--- File Ratio required for this security level Actual File Ratio: <<--- Actual File Ratio of User Download:Upload Byte Ratio DL:UL : <<--- Byte Ratio required for this security level Actual Byte Ratio: <<--- Actual Byte Ratio of User Download:Upload Bytes in Account : <<--- Actual Bytes left in user account Bytes in Session : <<--- Actual Bytes in THIS session Bytes Reset Freq : <<--- Byte Account Reset Frequency Last Bytes Reset : <<--- Last Date Byte Account Reset Time in Account : <<--- Actual Time left in user account Time Reset Freq : <<--- Time Account Reset Frequency Last Time Reset : <<--- Last Date Time Account Reset Version 2 will support multi-language, and will automatically select the correct language as chosen on PCBoard. Installation For experienced sysops, TUAM is a easy door to install, with no maintenance files or configuration files necessary! Although TUAM uses a TPA, you will find this is one of the best used TPAs you may ever install. Many other TPA programs are simply not used by many or even the majority of users, making the extra bytes redundant. TUAM on the other hand, uses only 32 bytes per user, and bytes are something that virtually every user on your system will utilize. You will have to set up a TPA by using PCBSM.EXE. Note that on a multi-node system ALL nodes must be down for this operation. PCBSM will generate a backup users file in this operation, however you may wish to have another backup offline just in case. Enter PCBSM, choose menu option "Add/Remove Third Party Application" to generate a new TPA. For TPA information use TPA Name : TUAM Version : 101 Static Size : 44 Dynamic Size : 0 Keyword : BYTES the keyword must match the name of the door in your DOOR.LST file For verify that the data structure corresponds to the current version of TUAM, we have chosen a version number of 101, we will only update this when we require a TPA structure change. This will be the TPA structure version and NOT the TUAM version number. Press PGDN to generate your TPA. DO NOT use create USERS.INF file unless you want alot of work and headache ! o Please ensure that your environment variable PCBDAT is set. If not please put in your autoexec.bat SET PCBDAT=(drive\path\pcboard.dat) ie: SET PCBDAT=C:\PCB\PCBOARD.DAT If your PCBoard is NOT not configured to disallow environment variables, then PCBoard will set this automatically when entering a door. However, some sysops disable this feature in PCBoard. This variable is also need in the System Manager (TUAMSM), and may need to be set manually to enter the system mananger. Here is an example of your PCBSM screen displays. ─────────────────────────────────────────────────────────────────────────────── PCBoard System Manager Copyright (C) 1987-1991 Clark Development Company, Inc Main Menu Use w/ PCB 14.5a A Users File Maintenance B Directory Maintenance (PCBFILER) C PCBoard Configuration (PCBSETUP) --------------->> D User Info File Maintenance E Analyze System Configuration F Define Printer Port G Define Text & Graphics Editors H Customize Colors Use arrow keys to move bar, press ENTER to select, ESC to exit 03:13:44 10-25-92 F1 help caps: OFF num: ON ins: OFF ─────────────────────────────────────────────────────────────────────────────── PCBoard System Manager Copyright (C) 1987-1991 Clark Development Company, Inc User Info File Maintenance A Change Conference Allocation B List Installed Third Party Apps ------------>> C Add/Update Third Party Application D Remove Third Party Application E Create User Info File Use arrow keys to move bar, press ENTER to select, ESC to exit 03:13:48 10-25-92 F1 help caps: OFF num: ON ins: OFF ─────────────────────────────────────────────────────────────────────────────── PCBoard System Manager Add/Update Third Party Application Enter the name of the Third Party Application ? TUAM Version : 101 Static Size : 44 Dynamic Size : 0 Keyword : BYTES Press PGDN to begin or ESC to exit 03:15:15 10-25-92 F1 help caps: OFF num: ON ins: OFF ─────────────────────────────────────────────────────────────────────────────── You will now need to make some changes using PCBSetup. The first will be creating a door, this may be necessary in more than one conference, although each conference may point to the same door. Depending upon your setup, only the Main Door changes may be necessary, only you as a SysOp can determine that. It WILL however be necessary from every Conference that you wish the user to have access to it. It is highly recommended that it is at the very minimum available from the Main Conference, as well as ALL other Conferences that have auto rejoin upon login set to YES. Batch File Example of batch file : @ECHO OFF CD \DOORS\TUAM TUAM ( If you are running multiple configurations include the configuration name after TUAM. ie: TUAM NODE1 ) ** Note : Do not reload PCBoard, as this is a shell door if is configured as above. IF YOU ARE SET UP AS ABOVE AND GET ZERO BYTE PWRD FILES GENERATED, OR THE SYSTEM DOES NOT RUN, THEN TRY A NON-SHELL DOOR AS SHOWN BELOW. Multiple Configuration Files : If you wish to use multiple configuration files type the configuration file on the command line. ie: TUAM CONFIG1 will load CONFIG1.SEC and CONFIG1.CFG No name on the command line will run the defaults, this will allow for multiple configuration files. Version 2 will enhance this area, making it much cleaner and easier from the sysops standpoint. Example of batch file (NON SHELL) : @ECHO OFF CD \DOORS\TUAM TUAM BOARD ** Note : If you use NON-SHELL because of memory problems do not define door as shell in PCBSetup as shown below. ─────────────────────────────────────────────────────────────────────────────── Door Installation Using PCBSetup choose the DOOR.LST file to edit. Edit DOORS File USER DOOR Filename Password Sec Login SYS SYS Shell Path to DOOR Files 65) BYTES 0 Y N N Y C:\DOORS\TUAM\ Press F2 to edit the DOOR file ESC=Exit Alt-R=Repeat a Line Alt-I=Insert a Line Alt-D=Delete a Line 09:18:26 11-14-92 F1 help caps: OFF num: ON ins: OFF ─────────────────────────────────────────────────────────────────────────────── In the above example, we show pathing to the batch file, this would be placed in the C:\DOORS\TUAM directory. (or other directory as you have chosen) By doing this you save multiple doors for each node. TUAM is a TPA door, but DOES NOT use a USER.SYS file. Please ensure that NO USER.SYS exists when TUAM is run. NOTE: If you have other auto-login doors, you will need to modify them, or adjust BYTES to accommodate your plans for login. We have adapted our autologin door to accommodate branching for different users as necessary. If you need help in this area, please let us know on the support board, or in one of the mail networks we carry. PCBSetup Configuration : It is highly recommended that you disable the "Display User Info at Login" with PCBSetup in Options #1 screen. This will make a much more pleasing display for your users. Example of possible Screen displays to User Last Date On : <<--- Last Date User was on System Expiry Date : <<--- Expiry Date of User Number Times On : <<--- Number of Times user has been on this system Page Length : <<--- Default Page Length for user Expert Mode : <<--- Expert Status Security Level : <<--- Security Level of user Total # of DLs : <<--- Total # of Downloads Total # of ULs : <<--- Total # of Uploads Total Bytes DLed : <<--- Total Bytes Downloaded Total Bytes ULed : <<--- Total Bytes Uploaded Bytes DLed Today : <<--- Bytes Downloaded Today UL Credit Ratio : <<--- UpLoad Credit Ratio (see ULP) File Ratio DL:UL : <<--- File Ratio required for this security level Actual File Ratio: <<--- Actual File Ratio of User Download:Upload Byte Ratio DL:UL : <<--- Byte Ratio required for this security level Actual Byte Ratio: <<--- Actual Byte Ratio of User Download:Upload Bytes in Account : <<--- Actual Bytes left in user account Bytes in Session : <<--- Actual Bytes in THIS session Bytes Reset Freq : <<--- Byte Account Reset Frequency Last Bytes Reset : <<--- Last Date Byte Account Reset Time in Account : <<--- Actual Time left in user account Time Reset Freq : <<--- Time Account Reset Frequency Last Time Reset : <<--- Last Date Time Account Reset Error Level Upon Exit TUAM will return an Error Level equal to the user security level upon exit from the program. This will allow some simple batch file routines to be developed within the logon door file. You will NOT be able to run another door requiring TPA's at present, however, it will allow more flexibility and control. Below is a brief example of a batch file using errorlevels. Remember errorlevels MUST be placed with the highest level first in decending order due to the method of reading DOS does. Also, an errorlevel can be used to reroute all levels above or equal to it. Both examples are shown here. C: CD \DOORS\TUAM TUAM IF ERRORLEVEL 200 GOTO REMIND REM JUMP TO REMIND REM LEVELS 200 THROUGH 255 IF ERRORLEVEL 70 GOTO DOTHIS REM JUMP TO DOTHIS REM LEVELS 70 THROUGH 199 IF ERRORLEVEL 50 GOTO REMIND REM JUMP TO REMIND (LEVELS 50 THROUGH 69) IF ERRORLEVEL 21 GOTO END REM JUMP TO END FOR ALL LEVELS FROM 21 THROUGH 49 REM WILL PREVENT ANYBODY ABOVE 20 FROM ENTERING VALIDOR IF ERRORLEVEL 20 VALIDOR REM LEVEL 20 WILL RUN VALIDOR IF ERROELEVEL 11 GOTO END REM JUMP TO END REM WILL PREVENT ANY LEVELS ABOVE 10 FROM RUNNING INSTAREG IF ERRORLEVEL 10 INSTAREG REM LEVEL 10 WILL RUN INSTAREG GOTO END REM ALL LEVELS BELOW 10 WILL GO TO END :REMIND REM RUN A REMINDER DOOR AND EXIT REM WILL RUN FOR LEVELS 50 THROUGH 69 AND LEVELS 200 THROUGH 255 :DOTHIS REM DO WHAT EVER YOU WISH FOR LEVELS 70 THROUGH 199 :END REM EXIT FROM PROGRAM REM LEVELS 1 THROUGH 9 & LEVELS 11 THROUGH 19 REM & LEVELS 21 THROUGH 49 TUAMLOFF If you are using TIME and/or Command Level editors please read the TUAMLOFF doc file TUAMLOFF must be run from the TUAM directory. Sample $$LOGOFF.BAT C: CD\TUAM TUAMLOFF Beta Test Sites We are currently searching for some reliable beta sites for version 2 of TUAM. If you are interested, give us a call, we will consider all applicants. However, all applicants will not necessarly be selected as beta sites. TUAM v2 : We are working on the following features for TUAM v2. We will not guarantee when any or all of these features will be in TUAM v2, but we are currently in the development of TUAM v2. o Password Control o File Accounts o Message Accounts o Multiple security level configurations o Conference to join on login o Conference to join upon logoff o Password Database (for each user) o Network SysOp flag o Added flexibility on expiration of accounts o Estimated Expiration Dates o 26 Group Accounts o 10 Groups per User Account o Group Conferences o Minimum Password Length o Password Validation o Password Change forced by system based on sysop setting per security level. o Password Change override flag per individual user o Time sessions available for each security level, with multiple definations for various times of the day. InstaReg or other Registration Systems If you use InstaReg, PCBVerify or any other validation or security level changer. Please note ALL levels used by these other systems, and make a note of them all. Then set Frc flag in the Byte Editor to YES for each of these levels. This will fix any undue problems these other systems may have with TUAM. Theory of Operation: Ok how do we do this magic? Well, PCBoard reads all of its information regarding time and bytes from the PWRD file. This file MUST be modified to enable node specific information to be updated on a per user basis. Don't worry, TUAM will handle this automatically for you, HOWEVER, TUAM will rewrite a temporary PWRD file to the local node directory each time the door is run. This temporary file is the one that PCBoard will actually read. If you are using TUAM, it is recommended that to avoid confusion in updating your information that ALL future PWRD information be updated using TUAMSM rather than PCBSM. This will save you much confusion, and duplication of updates. We will update everything automatically, PCBSM will not. TUAM will also modify your PCBoard.Dat file to point to the new PWRD file location. This is all automatic, and is completed as the door runs. If you are using Command Editors then the Command Level information in PCBoard.Dat will also be updated as required. TUAM reads the original PWRD file only once, upon initializing the system. It will NEVER again read the original PWRD file. This PWRD file (the original one in C:\PCB\MAIN) can be deleted if you do not need it any longer. TUAM keeps the security information in a file called TUAM.SEC, and creates dynamic PWRD files according to the current users needs. The temporary Sysop level as defined in the PCBSet up screen. The level granted when F1 is pressed, WILL ALWAYS be granted the FULL SESSION TIME AND SESSION BYTES regardless of the current users normal status. Note on Expiration If the PCBSetup flag for "Enable Subscription Mode" is set to N, then TUAM will NOT expire users regardless of settings of the Bytes, Time or Date Expiration Flags in TUAMSM. The "Enable Subscription Mode" flag is in PCBSetup as shown below.─┐ │ Node / Event / Subscription Information │ │ Running a Network / Multitasker System : Y │ Node Number on the Network : 6 │ Network Timeout on Errors (20-99 secs) : 45 │ Node Chat Frequency (once every 5-99 secs) : 15 │ Include City Field in NODE Display Y │ Using Slave Cards (slows file access) N │ │ Is a Timed Event Active : Y │ Time to Begin Event (military time) : 00:10 │ Minutes Prior to Suspend All Activity : 0 │ Disallow Uploads Prior to an Event : N │ Minutes Prior to Disallow Uploads : 0 │ Slide Event Time if a User is Online : N │ │ Enable Subscription Mode : Y <─────────────────────────────┘ Default Subscription Length in Days : 2 Default 'Expired' Security Level : 3 Warning Days Prior to Expiration : 1 08:02:08 11-20-92 F1 help caps: OFF num: ON ins: OFF ------------------------------------------------------------------------------- 386 Specific Version We have a 386 specific version of TUAM which is called TUAM386.EXE. If you are running 386/486 machines, this code will be slightly smaller and faster. Please rename TUAM386.EXE to TUAM.EXE prior to using. PCBoard /M - Multi Port Version TUAM386.EXE automatically supports fossil drivers and is fully compatable with the PCBoard/M version. Support BBS Information Platinum Software Development has chosen Central Ontario Data Systems as its support board. The board has given us the privilege to log on regularly and answer all questions and process ordering information. All orders will be processed within 48 hours under normal conditions, other conditions may prevail, but you will be left ample notice if conditions change. Our support boards phone number is : (705) 722-8194 (HST), (705) 728-5815 (V32), (705) 835-6448 (HST) Central Ontario Data Systems has given us the unique ability to have our own bulletin board. We wish to express our thanks for this. Upon entering the system, you will only see a brief hint that you have reached Central Ontario Data Systems, and be instantly placed into Platinum Software Development Support Board. All of our files are in the Main Board. As a matter of fact, we have at this time seen no reason to add extra conferences to this board. The board is using an instant registration system (InstaReg) to allow you immediate2 access to the system and the support Conference upon first call. You will be provided with a MENU to select your registration level. BE SURE to select Platinum Software Development Support at this Menu. Upon completion of the registration, you will be placed into the Support Area of the board. The support Conferences will be 1995 and 1998. Your personal key file is available by sending in a cheque or money order to the above address. Both U.S. and Canadian cheques are processed. Sorry, we can not accept currencies other than US or Canadian dollars. Visa registration is accepted either online, or by filling in and mailing the form enclosed in the package. ( VISA.FRM ) We would like to pass along our thanks to the authors of several products who have made our life both more enjoyable, and much easier. Clark Development - PCBoard - PCB Development Kit - InstaReg (Registration Door) Please use the registration form ( REGISTER.FRM ) for cheque or money order forms. Personal cheques will have a 10 day delay on processing prior to the generation of the key file (online) or mailing one back to you. This will allow sufficient time for the cheque to be processed by the banks. Visa orders placed online will be authorized with the key file being generated within 48 hours. Other Forms of Support: We can be reached on Salt Air, TDS International Network, ILink, RIME, Intelec, NANet or FidoNet PCBoard Conferences or on our own support board. Our Fido address is 1:252/102. All of our code is posted upon release on Salt Air and on TDS International Network. Product Credit : PCBoard v14.5 - Clark Development Corp PCBToolKit - Clark Development Corp Microsoft - MS-DOS 3.30, MS-DOS 5.0 Compaq - DOS 3.31 Novell - Netware 3.31, Netware 2.2 ArtiSoft - LanTastic 4.1 Licence Agreement : The Ultimate Account Manager, its accompanying programs, documentation and associated files are Copyrighted (C) 1992 by Platinum Software Development. All rights reserved. You may not engage in, nor permit third parties to engage in any of the following : A ) Altering the software, the documentation, the key files or any other files associated with or supplied with The Ultimate Account Manager. B ) Attempting to reverse engineer, disassemble, decompile any of the software, key files or associated files in any way or by any means, either electronic, mechanical or manually. C ) Granting licences, sub-licences, leases or any rights of any kind of this software to others. D ) Selling or giving away key files without proper notification to Platinum Software Development. Platinum Software Development grants you a licence to use this software as long as you agree to meet, and continue to meet all the above conditions. Any present or future violations of any of the above conditions will result in the termination of your licence to use this software. Upon termination for any reason, you must immediately stop using this software, and destroy all copies of the key files in your possession. Platinum Software Development reserves the right to cancel your licence at any time for any violations incurred that may not be listed in this documentation. Cancellation of licence due to violation of agreement will forfeit your ability to use this product, and any or all fees paid to use this product. PROBLEMS Time or Bytes are not set correctly: There needs to be a time or byte entry in either the PWRD editor OR in the Time Editor (for time) or the Byte Editor (for bytes) Each security level NEEDS to have an entry in one of the fields specified. If you get a TIME or BYTE problem, please check carefully the TIME EDITOR, BYTE EDITOR and RATIO EDITOR and PWRD for that specific security level. ONE of the editors MUST have time and byte parameters specified. TUAMSM NOT loading: Ensure the enviroment variable PCBDAT is set. Example: SET PCBDAT=C:\PCB\PCBOARD.DAT TUAM not giving correct time: Ensure that a TIME is set up for specific security level in either PWRD Editor or TIME Editor, ONE of these needs to have TIME parameters. Our new versions of TUAM will default to 10 minutes if NO time is found in the TUAM files. TUAM is writing a ZERO BYTE PWRD file: The security level for this user IS NOT defined in TUAMSM. Ensure that ALL levels have time configurations in either the PWRD Editor OR the Time Editor. Later versions of TUAM will NOT cause a zero byte file to be written. ALT-D is NOT working - NO DEFAULT IS BEING COPIED: You have not configured the DEFAULT SCREEN. Please go into the CONFIGURATION EDITOR screen, and set up the defaults. TUAM is ONLY giving out 10 minutes of time to a specific user: TUAM has not been able to find the users security level in TIME Editor or PWRD Editor. Please recheck your configuration files. THIS WILL NOT GIVE A ZERO BYTE FILE, IF YOU HAVE A ZERO BYTE FILE PLEASE CHECK YOUR MEMORY STATUS. Pressing F1 to give temporary SysOp status does not work: Please ensure your temporary SYSOP levels have TIME and BYTES defined in them as any other user would require. NOT getting correct entries in PCBoard: Please ensure you are changing to the TUAM directory prior to running the TUAM door. Also, ensure that you did not run TUAMSM from any directory other than TUAM's own directory. If you have a file TUAM.SEC or TUAM.CFG in your PCBoard's node root directory (where your PCBoard.Dat files are) then please delete these files. TUAM.SEC and TUAM.CFG should only exist in the TUAM directory. PCBoard is displaying event warning screen all the time: Edit your PCBText record # 116. The default shows: @FIRST@, your time has been adjusted for our event. Change this record to: %C:\TUAM\EVENTWRN We have included a sample EVENTWRN file to help handle this situation. This is the ONLY situation where we can not handle the user time, as this is displayed before PCBoard will allow us control. User can NOT use any commands You have turned Commands ON in the configuration editor, and HAVE NOT set up the Command Levels for the specific users. Doors like InstaReg, Eagle Verify, PCBVerify etc do not WORK ! Users are logged off of system, and have to return the call to get access. Once back online the system works fine : Check all of the security levels used by ALL of your security level changing systems. Automated ones, the ones run during events are not necessary to change. Make a node of all of the affected levels, and return to TUAMSM (Byte Editor Screen) and set the Frc flag to Y for all of these levels. I can not get InstaReg or PCBVerify to work with TUAM in one login DOOR: Version 1.07 and beyond should coexist with InstaReg, however you will have to do a PCB145 /READSYS prior to running TUAM and after running InstaReg. Also, please delete the USER.SYS file after running PCB145 /READSYS and before running TUAM or reentering PCBoard. INDEX ----- A ----- ACCOUNTS, DAILY 5 RESET 4-5, 7, 14 TIME 5, 7, 14, 16-17, 19-20, 22-25, 28 ALT-D 13, 25, 28 ANNUAL, ACCOUNTS 17 AUTO, UPDATE 8, 19, 26 ----- B ----- B0 6 BATCH FILE 12-13, 15, 26-27 BETA, TEST SITE 17 BYE 5-6 BYTE, RATIO 4-7, 14, 24 BYTES 5-8, 13-14, 24-25, 28 BYTES, DOWNLOADED 7, 14 DOWNLOADED TODAY 7, 14 NOT SET CORRECTLY 24 SESSION 4-5, 7, 14, 17, 19 TOTAL 5, 7, 14 ----- C ----- CHANGE, NAME 5, 12 CHANGING 25-26 COMMAND, LEVEL 4-5, 7, 14-20, 22, 24-28 CONFIGURATION, EDITOR 9, 16, 18-19, 24-26 PCBSETUP 4, 9, 12-14, 20 CONFIGURATION FILES, MULTIPLE 12 ----- D ----- DAILY, ACCOUNTS 17 BYTES 5-8, 13-14, 24-25, 28 TIME 5, 7, 14, 16-17, 19-20, 22-25, 28 DOOR, INSTALLATION 3, 8, 13 NON-SHELL 12 SHELL 12-13, 28 DYNAMIC SIZE 8, 11 ----- E ----- EDITOR, SECURITY 4-7, 14-15, 17-20, 24-27 USER 4-10, 12-15, 17, 19-20, 25-28 USER ACCOUNT 7, 14, 17 ENABLE SUBSCRIPTION 20 ENVIRONMENT, VARIABLE 6, 8, 24 ERROR, LEVEL 4-5, 7, 14-20, 22, 24-28 ERROR LEVEL UPON EXIT 15 EVENTWRN 25 EXIT, ERROR LEVEL 15 EXPIRATION, NOTE ON 20 EXPIRATION DATE 17 EXPIRED SECURITY LEVEL 20 ----- F ----- FEATURES 17 FILE 3-10, 12-17, 19-20, 22-23, 25-28 FILE RATIO 4-7, 14, 24 FILES 6, 8, 12-13, 19, 22, 24-26, 28 ----- H ----- HELP 9-11, 13, 20, 25, 28 ----- I ----- INSTALLATION, DOOR 5-6, 8, 12-13, 15, 19, 22, 25-28 QUICK 3 TPA 3, 8, 13 INSTAREG 15, 18, 22, 25-28 ----- K ----- KEY FILE 22-24 KEYWORD 8, 11 ----- L ----- LAST DATE ON 5, 7, 14 LICENCE AGREEMENT 24 LOGIN 4-5, 7, 12-14, 17, 26-28 LOGIN, AUTO 6-8, 12-13, 19, 21, 26-27 ----- M ----- MANAGER 8-11, 24, 27 MANAGER, THE SYSTEM 4-5, 8, 12, 19, 22, 25, 28 Multi Port 21 MULTIPLE CONFIGURATION FILES 12 /M, PCBoard 4-5, 7-12, 19, 21-25, 27-28 ----- N ----- NAME 5, 12 NOB 6 NOF 6 NUMBER TIMES ON 5, 7, 14 ----- P ----- PASSWORDS, CHANGE 8, 10, 12, 17-18, 22, 25-26 PCBoard /M 21 PCBSETUP 4, 9, 12-14, 20 PCBSETUP CONFIGURATION 14 PCBVERIFY 18, 25-27 PLATINUM 22, 24 Port, Multi 21 PROBLEMS 12, 18, 24, 26 PRODUCT CREDIT 23 PWRD FILE 12, 19, 25 ----- Q ----- QUICK.DOC 3 ----- R ----- RATIO 4-7, 14, 24 RATIO, FILE 3-10, 12-17, 19-20, 22-23, 25-28 RESET, LAST 5, 7, 14 LAST DATE 5, 7, 14 ----- S ----- SECURITY FILE 4 SESSION BYTES 7, 14, 19 SHELL 12-13, 28 STATIC SIZE 8, 11 Subscription Mode, Enable 5, 19-20 SUPPORT 2, 6-7, 13, 21-23 ----- T ----- TEMPORARY SYSOP 19, 25 TEMPORARY SYSOP, DOES NOT WORK 25 THE SYSTEM MANAGER 8 THEORY OF OPERATION 19, 27 TIME 5, 7, 14, 16-17, 19-20, 22-25, 28 TIME, NOT SET CORRECTLY 24 SESSION 4-5, 7, 14, 17, 19 TOTAL, BYTES DOWNLOADED 7, 14 TOTAL BYTES DOWNLOADED 7, 14 TPA 8 TPA, INSTALLATION 3, 8, 13 TPA NAME 8 TUAM 4-6, 8, 11-13, 15-21, 24-28 TUAM, ONLY GIVING OUT 10 MINUTES 25 ZERO BYTE PWRD 12, 25 TUAMLOFF 16, 28 TUAMSM, NOT LOADING 24 ----- U ----- USER INFO, DISPLAY 4-7, 9, 14, 20, 25 ----- Z ----- ZERO BYTE PWRD, TUAM 4-6, 8, 11-13, 15-21, 24-28 "This program is produced by a member of the Association of Shareware Professionals (ASP). ASP wants to make sure that the shareware principle works for you. If you are unable to resolve a shareware-related problem with an ASP member by contacting the member directly, ASP may be able to help. The ASP Ombudsman can help you resolve a dispute or problem with an ASP member, but does not provide technical support for members' products. Please write to the ASP Ombudsman at 545 Grover Road, Muskegon, MI 49442 or send a CompuServe message via CompuServe Mail to ASP Ombudsman 70007,3536."