ProfitPress Mega CDROM2 Shareware Freeware (MSDOS)(1992)(Eng)

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

/ ProfitPress Mega CDROM2 …eeware (MSDOS)(1992)(Eng) / ProfitPress-MegaCDROM2.B6I / BBS / RA / RAMAN100.ZIP / RAMAN.DOC < prev next >

Wrap

Text File | 1992-01-02 | 42.2 KB | 1,171 lines

┌─────────┐┌──────────┬┌────────────┐┌──────────┬───────┬───┐ │ ┌───┐ ││ ┌───┐ ││ ┌─┐ ┌─┐ ││ ┌───┐ │ │ │ │ │ │ ││ │ │ ││ │ │ │ │ ││ │ │ │ │ │ │ │ └───┘ └┤ └───┘ ││ │ │ │ │ └┤ └───┘ │ │ │ │ │ ┌────┐ │ ┌────┐ ││ │ │ │ │ │ ┌────┐ │ │ │ │ │ │ │ │ │ │ ││ │ │ │ │ │ │ │ │ │ │ └──┘ └──┴──┘ └──┴┴──┘ └──┘ └───┴──┘ └──┴───┴───────┘ RAMAN - RemoteAccess Manager v1.00 Copyright (C) 1991 By David Hickey, All rights reserved TABLE OF CONTENTS Features 1 License 1 Registration 2 System Requirements 2 Installation 3 Setup 4 Feature Descriptions Toggles Menu 4 Archivers 9 Logfiles 10 Allfiles 11 Misc 12 Multi-Node Operation 14 Running RAMAN 15 Credits 17 Bug Reports 17 Beta Testers 18 Other Stuff 18 Registering RAMAN 19 RAMAN Remote Access Manager January 2, 1992 1 FEATURES * Alphabetizes FILES.BBS * Updates download counters * Adds download counters to file descriptions without them * Truncates file descriptions * Add file headers to FILES.BBS * Cleans up the location field in your user file * Creates up to 5 allfiles listings * Archives up to 5 logfiles by date * Scans files for viruses * Re-archive an unlimited number of directories * Back up your user files * Generate a report of message base usage * Pick random screens/menus LICENSE The term "RAMAN" refers to the files contained in the files contained in the RemoteAccess distribution archive released by David Hickey. The following must be read, understood, and agreed upon BEFORE you use RAMAN: * RAMAN is Shareware. It is not FreeWare or Public Domain. * This program and the accompanying documentation are copyrighted material by David Hickey. * This program is provided AS IS! I have taken a great deal of precautions insuring RAMAN will work as this documentation states, but there is always the unknown. I provide NO warranty whatsoever. * The author, David Hickey, is not liable to you or anyone for, but not limited to, any direct, indirect, incidental, or consequential damages, including, but not limited to, any lost profits, damaged hardware or software, or loss of money resulting from the inability or abilitiy of this program to perform as stated. By using this program, you agree to these terms and release the author from any liablility or litigation whatsoever. * I am in no way obligated to provide future versions of or support for RAMAN. * You are hereby granted a limited license to use RAMAN up to 14 days before registering. After 14 days you are required to register this program as described at the end of this documentation. You may use and distribute this program provided it is not modified, reverse engineered, or in any way altered. 1 RAMAN Remote Access Manager January 2, 1992 2 REGISTRATION As stated in the license agreement, you are required to register RAMAN if you use it past the 14 day trial period. RAMAN is not crippled in any way, however, if you have not registered RAMAN will pause for 10 seconds each time it executes. This pause will be eliminated once you receive your keyfile. It will also stamp a nice UNREGISTERED message on things like the Allfiles listings, File Headers, etc until you have registered. The end of this document contains registration information. If you like this program then please register. REQUIREMENTS To date, this program has been tested with the following hardware configurations: 1) Packard Bell 80286 with 1Mb RAM under MS-DOS v4.01 2) 80386 SX Clone with 2Mb RAM under MS-DOS v4.01 3) 80286 with 1Mb RAM under MS-DOS v3.3 4) IBM XT clones with 640k RAM under MS-DOS 5.0 and 3.3 5) 80386 with 8Mb RAM under MS-DOS v5.0 Memory requirements is around 295k. If RAMAN has to call an external program such as ARJ, it will attempt to swap itself out of memory and into either EMS or to a swap file. If the swap should fail, RAMAN will recover and execute the external program while still in memory. It is highly unlikely a swap would ever fail, but if it does and it has to call ARJ, it would need around 450k to execute ARJ. The swapper used was written by Kim Kokkonen of TurboPower Software. A copy of RemoteAccess v1.00 or later is required. This program is RemoteAccess specific and uses CONFIG.RA, FILES.RA, MESSAGES.RA, and your RemoteAccess logfile. For some of the functions, you will need to have a copy of PKZIP.EXE and PKUNZIP.EXE by Pkware, LHA.EXE by Yoshi, ARJ.EXE by Robert K. Jung, and SCAN.EXE by McAfee. 2 RAMAN Remote Access Manager January 2, 1992 3 RAMAN makes repeated calls to access the disk drive, and works extremely well while running under a disk caching system. This is not a requirement, but in experimentation on my system RAMAN has run MUCH faster under the 256k cache I use. INSTALLATION You MUST have the COMSPEC environment variable set to point to where Command.Com is located. To do this, put the following line in either your AUTOEXEC.BAT file or your BBS batch file: SET COMSPEC=C:\DOS\COMMAND.COM Edit this line to point to where your copy of Command.Com is located. Next, copy all the files in the distribution archive into any directory you want. RAMAN does not need to be placed in your RemoteAccess system directory, but it does need to have all it's files in the same place. SETUP A setup program called RAMANCFG.EXE is provided for the configuration. The configuration file is NOT an ASCII file. Switches for RAMANCFG.EXE: M - Force RAMANCFG into monochrome mode C - Force RAMANCFG into color mode T - Sends the contents of RAMAN.SYS to a text file called RAMANCFG.TXT P - Sends the contents of RAMAN.SYS to the printer Switches are NOT case sensistive and must be preceded by a '/' or a '-'. RAMANCFG will automatically detect the monitor type you have and default to that. Specifying the M or C switch will override what RAMANCFG has detected. There are some things that require a trailing backslash, and some that do not. RAMANCFG automatically removes/adds a trailing backslash to whatever needs it. You don't have to worry about that. 3 RAMAN Remote Access Manager January 2, 1992 4 There are several functions that deal with your FILES.RA file, and one that uses MESSAGES.RA. For an area in FILES.RA to be considered unused, the field where you enter the path for that area MUST be blank. Otherwise RAMAN will consider it "fair game." With MESSAGES.RA, an area is considered unused by RAMAN if it's Name field is blank. Again, if there is anything in that field, it is considered "fair game." FEATURE DESCRIPTIONS Following is a description of each of the features available: Toggles Menu ------------ ALPHABETIZE FILES.BBS - Does just what you think. With this option enabled each entry in each of the FILES.BBS files in FILES.RA will be alphabetized from A-Z. This procedure will strip any file headers and descriptions that take up more than one line in FILES.BBS. If you are using a program other than RAMAN to add headers in your FILES.BBS files, you will have to run that program after RAMAN is done. RAMAN adds file headers AFTER this procedure, so there is nothing to worry about if you use RAMAN to add headers. This is the only function that will strip multi-line descriptions or file headers. UPDATE DOWNLOAD COUNTERS - This function will read your RemoteAccess logfile and pick out the files that have been downloaded. RAMAN will then update the download counter for each file that was downloaded. Please note that RAMAN creates a file called RAMAN.PLC during this process. This file is used by RAMAN to keep track of which files it has already counted and whether or not the logfile it is reading is new or old. In other words, RAMAN will know whether or not you have deleted your logfile and started over again and will not count the same files twice. If you have not defined a download counter in RAMANCFG (the next function), or if a file that has been downloaded does not have a counter, RAMAN will leave it alone instead of screwing up your descriptions with meaningless numbers. ADD DOWNLOAD COUNTERS - Will add a download counter type of your choice in each of the description fields in the FILES.BBS files. The counter is only added to files that do not have a counter yet. This procedure will not affect file headers or multi-line descriptions. 4 RAMAN Remote Access Manager January 2, 1992 5 TRUNCATE DESCRIPTIONS IN FILES.BBS - Even though a file description fits on only one line in the FILES.BBS file, it may take up two when it is displayed to a user. This function will cut the file descriptions down in FILES.BBS so that the user is only shown one line. If you have multi-line descriptions, each line of that description will be cut down so that it only will display on one line when RemoteAccess displays it to the user. CLEAN UP USERS LOCATION FIELD - This makes the location field of each user's location field look better. For example: BaLTImoRE, md -----> Baltimore, Md NOrth SOUthgAte aVENUE -----> North Southgate Avenue LonDON, ENGLAND -----> London, England ARCHIVE LOGFILE(S) - This function will archive and delete up to five logfiles (or any other file for that matter) that you define (described later). CREATE ALLFILES LISTING(S) - This function will create up to five ASCII allfiles listings that you define (described later). After creating these listings, RAMAN will archive them in the same directory. Net result is an archived and text version of the allfiles listing. SCAN FILES FOR VIRUSES - This function calls SCAN.EXE by McAfee to scan files for viruses. There are three ways this function can work. The first way assumes you have one directory that all uploads go into. When RAMAN is run, only this directory will be checked out. The second way is if you have uploads going into several different directories. If this is the case, then RAMAN can scan your RA logfile to find out where uploaded files have gone into and scan the files. The third way is to create an ASCII file called SCANDIR.CTL that contains the names of any directories you want files in checked for viruses. The format of this file is: <directory> <directory> ... Example: c:\files\misc c:\files\pascal c:\files\sdsra\ 5 RAMAN Remote Access Manager January 2, 1992 6 The names of the directories do not have to have a trailing backslash, and the number of directories you may specify is unlimited. If SCANDIR.CTL is present, then RAMAN will use that. If you want RAMAN to only scan files in your upload directory, then in the MISC section of RAMANCFG (described later) you have to set the "UPLOADS GO INTO A SINGLE DIRECTORY" to "Y", and then enter the directory name in the space named "FULL PATH TO UPLOAD DIRECTORY" If you want RAMAN to use your RA logfile to find the path and filename for uploads, set "UPLOADS GO INTO A SINGLE DIRECTORY" to "N". RAMAN will also create and maintain a file called RAMAN.SCN. This file contains the path and filename of all files RAMAN has already scanned so it will not scan them again. After each run, RAMAN checks this file against reality to make sure that the files logged in RAMAN.SCN are still present on disk. If they are not, their record is removed. This feature both saves time so RAMAN does not have to scan files more than once and also makes this function ideal to run after a user logs off to check files he/she may have uploaded. PICK RANDOM MENUS/SCREENS - This function allows you to specify, in a file called MENSCR.CTL, the names of files you want to switch around. This could be useful if you want a different WELCOME.A?? or LOGO.A?? screen to be displayed each time someone logs on. The best way to explain this file is to show an example of the control file: -c:\ra\txtfiles\welcome1.ans <---- Full path/filename to Target file c:\hold\welcome1.an1 \ Up to 50 files that are c:\hold\welcome1.an2 \ possible source files to be c:\hold\welcome1.an3 >randomly copied to the c:\hold\welcome1.an4 / Target path and filename c:\hold\welcome1.an5 / specified above. -c:\ra\txtfiles\welcome1.asc c:\hold\welcome1.as1 c:\hold\welcome1.as2 - Note the '-' at the end. This tells RAMAN that there are no more entries after that '-' DO NOT FORGET TO ADD THIS! The '-' in front of the filename tells RAMAN that this is the target filename, and the files listed after that are source files. You may specify up to 50 source files for each target file. The number of target files is unlimited, but a '-' MUST appear at the end of the file, and a '-' MUST appear before each target file. 6 RAMAN Remote Access Manager January 2, 1992 7 CREATE REPORT OF MESSAGE BASE ACTIVITY - This option scans your RA logfile to generate an ANSI and ASCII file (defined later) showing the number of times someone has posted a message and the number of times someone has read a message in each sepearate message area. In unregistered mode, RA does not log message Reads to it's logfile. Therefore, if your copy of RA is not registered, then you will see nothing but zeros for the Reads of each area. If RAMAN finds a line saying the user read in Combined Mode, RAMAN will look at that users combined information record in USERSXI.BBS and update each area listed. Because offline mail doors are in wide use, RAMAN also makes provisions for recording their activity as well. At the end of the report, RAMAN will tell you how many messages have been downloaded through the offline door and how many have been uploaded through the offline door. Currently, RAMAN recognizes the log formats of: RAMail, XRS, Silver Express, and MkQwk. Future versions will support more readers as I become aware of their existance. RAMAN keeps a file called RAMAN.MSG. This file contains information about the RA logfile that RAMAN uses to make sure it doesn't count things more than once and also to determine if the RA logfile it's working on is a new one or an old one. You can display these files via a Type 5, 39, 40, 45, or 46 menu display. This is a good addition to your bulletin or message menu. REARCHIVE FILES - This function re-archives all files in a given directory into an archive format of your choice (ZIP, LZH, ARJ). RAMAN first looks for a file called REARCDIR.CTL. If this file is found, RAMAN will archive the files in the directories listed in it. Otherwise RAMAN will re-archive the files in each directory listed in FILES.RA. The format of REARCDIR.CTL is the same as for SCANDIR.CTL: <directory> <directory> ... Example: c:\files\uploads c:\files\sdsra c:\files\bbssoft c:\files\pascal 7 RAMAN Remote Access Manager January 2, 1992 8 There is no limit to the number of directories you may list, and the RAMAN does not require them to have a trailing backslash. You pick which archiver you want used from the ARCHIVERS menu described in the next section. BACK UP USER FILES - This function will make an archive, in the format of your choice (ZIP, LZH, ARJ) of your USERS*.BBS files. The filename of the archive that will be made is the letters UF plus the date, plus the archive method (.ZIP, .LZH, or .ARJ). This file will be put into the directory you specifiy in RAMANCFG under the Misc section which is descbribed later. NOTE: If you use this function, it would be very wise to have the backup path pointing to a floppy drive. Backups on a hard drive are not going to do you much good if your hard drive crashed! 8 RAMAN Remote Access Manager January 2, 1992 9 Archivers --------- PATH AND FILENAME TO PKZIP.EXE - Enter the full path and filename to where PKZIP.EXE is located. Example: C:\UTILITY\PKZIP.EXE. This is used to compress files with the PATH AND FILENAME TO PKUNZIP.EXE - Enter the full path and filename to where PKUNZIP.EXE is located. Example: C:\UTILITY\PKUNZIP.EXE. This is used to decompress files with the PATH AND FILENAME TO LHA.EXE - Enter the full path and filename to where LHA.EXE is located. Example: C:\UTILITY\LHA.EXE. This is used to compress and decompress files with the .LZH extension. PATH AND FILENAME TO ARJ.EXE - Enter the full path and filename to where ARJ.EXE is located. Example: C:\UTILITY\ARJ.EXE. This is used to compress and decompress files with the .ARJ extension. FORMAT TO REARCHIVE IN - Here is where you pick the format RAMAN will re-archive files into. Choices supported are ZIP, LZH, and ARJ. When defining the path and filename for each of the archivers, RAMAN will check that directory and make sure the file exists. If it does not exist, RAMAN will prompt you for the correct path and filename. During program execution, RAMAN will double check to make sure these files are still in place. If they are not, RAMAN checks your path statement and attempts to locate each program that way. If it can find them, it will write that information into RAMAN.SYS. If it can not find them, then you're up a creek! This check does not take long, and it will help insure against potential problems if for example you reorganize your drive and forget to make the necessary changes in RAMANCFG. 9 RAMAN Remote Access Manager January 2, 1992 10 Logfiles -------- This is the section where you define up to five logfiles you want RAMAN to archive and delete. FIRST LOGFILE TO ARCHIVE - Press the [Enter] key and you will be asked for information about the logfile: PATH AND FILENAME TO LOGFILE - Enter the full path and filename to the the logfile you want archived. Example: C:\RA\RA.LOG PATH TO PUT ARCHIVED LOGFILE - Enter the path where you want RAMAN to put the archive after it is finished. Example: C:\RA\RALOGS\ If you do not put a trailing backslash on the path, RAMAN will append one automatically. FIRST 2 LETTERS FOR ARCHIVE NAME - Enter the first two letters you want for the archive name. Example: RA The name of the archive will be a combination of the first two letters you define plus the date. For example: If you defined the first two letters as "RA" and the date is December 1, 1991 and you want the ZIP archiver to be used, the filename will be: RA120191.ZIP. FORMAT TO ARCHIVE LOGFILES - Select the method you want the logfiles to be archived in (ZIP, LZH, ARJ). Some people may not have five logfiles to archive, so there is no point in filling in the remaining spaces with dummy files. If you don't have five logfiles, then enter the menu for the ones you are not planning to use. Go to each question (Path to logfile, Path to put the logs, first two letters), press [Enter] once, then press it a second time. This will display a 'Not used' message in the first two and a '--' in the third. This tells RAMAN there is nothing there and therefore disables the spaces for the remaining logfiles. 10 RAMAN Remote Access Manager January 2, 1992 11 Allfiles -------- This section is almost identical to the way the Logfiles are handled. FIRST ALLFILES LISTING - Press the [Enter] key and you will be asked for information for the allfiles listing: PATH AND FILENAME FOR LISTING - Enter the full path and filename for this allfiles listing. Example: C:\FILES\MISC\ALLFILES.LST SECURITY LEVEL FOR THIS LIST - Enter the minimum security level a file area must have to be included in this listing. Example: 10 In this example, all file areas with a security level of 10 or below as, defined in FILES.RA, will be included in the allfiles listing. As with the logfiles, you may not need five allfiles listings. The procedure for disabling the remaining allfiles is the same as for logfiles. Go to each listing you do not want to use. At the questions (path and filename for the listing, security level for listing) press [Enter] once then press it again. This will display 'Not used' for the path and a 0 for the security level. This tells RAMAN to disregard this listing. FORMAT TO ARCHIVE ALLFILES - Choose whether you want the allfiles listings to be archived in the ZIP, LZH, or ARJ format. 11 RAMAN Remote Access Manager January 2, 1992 12 Misc ---- This section contains miscellaneous information that is required for certain functions. REMOTEACCESS SYSTEM PATH - Enter the path to where your *.RA files are kept. Example: C:\RA REMOTEACCESS LOGFILE - Enter the path and filename to your RemoteAccess logfile. Example: C:\RA\RA.LOG DOWNLOAD COUNTER TYPE - Enter the type of download counter you want RAMAN to add to descriptions in FILES.BBS. If you do not intend to use RAMAN to add download counters, but do want RAMAN to update ones you already have, enter the style that is currently in use. Example: [00] FULL PATH TO UPLOAD DIRECTORY - If you want RAMAN to only scan uploaded files for viruses and if your uploads go into a single directory, enter the path to that directory here. Example: C:\FILES\UPLOADS\ (RAMAN appends a '\' if you do not put one there). FULL PATH/FILENAME TO SCAN.EXE - Enter the full path and filename to where SCAN.EXE is located. This is the program RAMAN uses to scan files for viruses. RAMAN will check to make sure that the directory/filename you have entered actually exist. Example: C:\UTILITY\SCAN.EXE FIRST AREA NOT TO ADD COUNTERS - You may specify up to five directories that you do not want RAMAN to add download counters to. If you have directories you do not want counters added to, enter its directory number (from FILES.RA) here. If you do not have 5 directories you want left alone, put a 0 as the area number for each one you will not use. For example, if you put a zero in all five spots, RAMAN will add download counters to every directory (this is assuming you have this option turned on in the first place!) UPLOADS GO IN A SINGLE DIRECTORY - This is used in conjunction with the function to scan files for viruses. If all your uploads go into one directory, set this option to 'Y'. If your uploads can go into several different directories, set this to 'N' A 'N' will make RAMAN scan your RemoteAccess logfile to see where uploaded files have gone. For more information, see the section under 'Toggles' that describes the function to scan for viruses. 12 RAMAN Remote Access Manager January 2, 1992 13 PATH/FILENAME FOR ASCII REPORT - If you have enabled the function to create a report of your message base usage, enter the full path and filename for the ASCII version of the report. Example: C:\RA\TXTFILES\MSGUSAGE.ASC PATH/FILENAME FOR ANSI REPORT - Same as the above, but for the ANSI version of the report. Example: C:\RA\TXTFILES\MSGUSAGE.ANS PATH FOR USER FILE BACKUP - Enter the directory where you want RAMAN to place the archive containing the backed-up user files. Example: C:\RA\BACKUPS\ (A '\' will be appended if you forget to add it). As previously mentioned, this is a Registered Only feature. FORMAT TO ARCHIVE USER FILES - Select the format you would like the backed up user files to be archived in: ZIP, LZH, or ARJ. 13 RAMAN Remote Access Manager January 2, 1992 14 Multi-Node Operation -------------------- I don't currently run a multi-node board, and I know no one in the area who does. However, I am not completely ignorant of the way RemoteAccess works, so I'll give this a shot. If you run with all of RA's .RA files in a single directory (C:\RA for example) and the RA logfile is in that directory only, then set RAMAN up the same way I have already described. This *should* work. If each of your nodes has it's own .RA files, or if you want RAMAN to work with each node individually, then you will need to have one copy of RAMAN with all of it's files for each node. Make sure that you set the path to your system directory to where the .RA files are stored for that node. If you run multi-node, then you have probably had experience with setting things up for your configuration, and RAMAN should be no exception. You probably know more than I do about this area of RA operation. I cannot guarantee that what I have suggested is going to work, but to my way of thinking, it *should* do the trick. If you run multi-node and get RAMAN working great on your system, I'd appreciate it if you could netmail me and let me know how you did it so I can see if I can make it any easier with the next version of RAMAN. 14 RAMAN Remote Access Manager January 2, 1992 15 Running RAMAN ------------- Running RAMAN can be done in one of two ways. First, you can run it with no command line parameters by typing in RAMAN and hitting [Enter]. RAMAN will read the configuration file and do what you have told it to do there if you run it like this. This method is ideal for running RAMAN in your nightly maintenance, which is what RAMAN was orginally designed for. And alternate method is to run RAMAN with command line parameters to make it perform only a few functions. This is ideal for running RAMAN after a user hangs up to have it check for viruses in any files that may have been uploaded, update the message base report, etc. The following parameters are valid: H - Displays a help screen ? - Displays a help screen CLEAN - Clean up the location field of the user file TRUNC - Truncates descriptions in FILES.BBS so they will fit on one line when displayed on the screen MANGORP - Manages orphaned files/descriptions in FILES.BBS ADDHEAD - Adds file headers to FILES.BBS ABC - Alphabetize all FILES.BBS ADDCOUNT - Add download counters to all FILES.BBS UPDCOUNT - Update download counters ALLFILE - Creates allfiles listing(s) SCAN - Scans files for viruses ARCLOG - Archives and deletes your logfile(s) REARC - Re-archive files SWITCH - Switches defined menus/textfiles MSGACT - Generates a report of message base usage BACKUP - Backs up your user files A '-' or a '/' must precede each parameter, except for the 'H' or '?' which do not require a '-' or '/' in front of them. Parameters are NOT case sensitive. Example: RAMAN -Scan /allfile Note that RAMAN uses information from its configuration file such as path information even if it is being run with parameters. 15 RAMAN Remote Access Manager January 2, 1992 16 Example of partial batch file: :NIGHTLY Echo Nightly maintenance is performed here RAMAN :AFTER_USER Echo Performed after each user logs off RAMAN -Scan -Msgact -Switch -Addhead -Updcount If RAMAN can not read the overlays contained in RAMAN.EXE, it will return an errorlevel of 1. This would mean either the EXE is corrupted or it may contain a virus of some type. If you run RAMAN without parameters, the order things are performed is as follows: Clean User Location, Alphabetize the Files.Bbs, Add download counters, Update download counters, Truncate descriptions, Add headers to Files.Bbs, Create the allfiles listings, Switch menus/textfiles, Generate message base report, Scan for viruses, Re-archive files, Archive the logfiles, and Backup the user files. 16 RAMAN Remote Access Manager January 2, 1992 17 Credits ------- All product names mentioned in this document other than RAMAN are copyrighted (C) material, Trademarks (tm), or Registered Trademarks (R) of their respective holders: Arj.Exe, ARJ Robert K. Jung IBM International Business Machines Corporation Lha.Exe, LZH H. Yoshizak MS-DOS MicroSoft Corporation Pkzip.Exe, ZIP Pkware, Inc. Pkunzip.Exe, ZIP Pkware, Inc. RemoteAccess, RA Andrew Milner and Continental Software, Inc. Scan.Exe McAfee Associates Turbo Pascal Borland International, Inc. Bug Reports ----------- Any and all bug reports should be sent to me via netmail at 1:261/1108. If you do not have access to netmail, write them legibly on paper and mail them to me, or you can call my board at 1-410-263-1633 and leave a message. When reporting a bug please include the following: Your computer type Amount of RAM you are running RAMAN under What you have tried, and a complete description of the problem you are having along with any runtime error and offset memory address it gives you. Please, do not send a bug report until you have gone over your configuration very carefully and made certain you have things set up properly. 80% of all so called "bugs" can be traced back to someone not reading the docs or some kind of silly mistake in the configuration (you know the ones, the ones that make you want to hit your head against a brick wall after you find out what the problem was...). If you can not understand something in the docs or need help, you can either netmail me, call my board, or ask me to call you voice and I will help you out and get it running. I am also available through the RA_SUPPORT echo and the RA_UTIL echo. Both are on the FidoNet backbone. I would ask you to please write to me in RA_UTIL as that echo is more suited to this purpose than RA_SUPPORT is. I DO answer my mail! 17 RAMAN Remote Access Manager January 2, 1992 18 Beta testers/Thanks to... ------------------------- This is in recognition to those who voluntarily offered to test RAMAN while it was still in Beta stages. These people risked their entire system in testing unproven designs: Steve Watson, The Lymph Node! Joe Williams, B.A. Express - 1:261/1099 Jim Henthorn, The Fire Station - 1:261/1044 Sid Balcom, The Catalytic Star - 1:109/343 Bruce Shetrone, The Dollar Saver - 1:261/1128 Thanks guys, I couldn't have done it without you! Other stuff ----------- The latest version of RAMAN will always be requestable from my system, The North Star, at 1:261/1108 and from each of the Beta sites listed above. Magic name is RAMAN for the latest version. I know that a lot of people have been burned by Shareware authors. I can only say that I will not take your money and run like some seem to do. Beyond that, you will just have to trust me. Should circumstances occur and I cannot continue RAMAN development, I will probably release the source code to registered users or make arrangements with someone else to take over RAMAN development. This is NOT a promise. I plan to be around for a while, but you never know what could happen. 18 RAMAN Remote Access Manager January 2, 1992 19 Registering RAMAN ----------------- When registering, please fill out REGISTER.FRM and mail it along with your registration fee to: David Hickey 304 North Glen Avenue Annapolis, Md 21401 United States Of America The registration fee is $10. Please send only U.S. funds, no foreign personal checks unless it is drawn on a U.S. bank, and no credit cards. It just costs too much to process them. When I receive your money I will generate a key file for you. If you have a FidoNet address, I will CRASHmail it to you. If you do not have a FidoNet address, I will call your BBS and upload your key file to you in a private upload. Once you receive your key, place it in the directory with RAMAN's other files. Be sure it is named RAMAN.KEY. If you do not have a FidoNet address, be sure to create an account for me under the name of David Hickey and put the password on the place provided on the registration form contained in the file REGISTER.FRM which is in the RAMAN distribution archive. 19 EOF