The World of Computer Software

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

/ The World of Computer Software / World_Of_Computer_Software-02-386-Vol-2of3.iso / b / burn_in.zip / BURNIN.DOC < prev next >

Wrap

Text File | 1990-08-27 | 51KB | 1,062 lines

Burnin 4.2 The Premium PC Exerciser and Diagnostic Tool From: George Campbell 1472 Sixth St. Los Osos, CA SUPPORT BBS: (805) 528-3753 INTRODUCTION ============ Most of the time our PCs work flawlessly, performing the varied tasks we ask of them without a hitch. That's not always the case, however. To protect us from the possibility of hardware failure, every manufacturer of IBM-compatible computers offers a warranty. Lengths vary from 90 days to a year or more. Like most warranties, problems tend to occur two days after the warranty expires. How do you protect yourself? In the case of PCs, the answer is BurnIn. BurnIn is designed to do just one thing: give your PC and all its systems a tough workout. Here's the idea: If your PC has a hidden problem, you'd rather discover it before the warranty runs out. Running BurnIn for 24-72 hours is like using it nonstop for weeks. If there's a latent problem, it's sure to show up while BurnIn runs. If not, then your PC gets a clean bill of health and you can rest easy. Here's what I recommend: * Run BurnIn for 72 hours when you first buy your PC. That'll spot any problems before you commit your valuable data permanently. * Run BurnIn for 72 hours about a week or so before your warranty expires. That way, if there's a problem about to happen, it will happen before the expiration, allowing you to get it fixed. * Run BurnIn for 24 hours each time you add new hardware to your system, then again before the warranty on the new upgrades expire. * Run BurnIn whenever you suspect an intermittent problem is developing in your system. The BURNIN.LOG file will pinpoint the source of the problem. Special Note for System Houses and Clone Builders: ================================================== Run BurnIn on every new system before it's sold. A 48 hour run is probably adequate. BurnIn, unlike most other burn-in techniques, gives your computers a REAL workout, preventing comebacks and expensive warranty repairs. IMPORTANT!! =========== BurnIn cannot damage your computer! It uses normal DOS and BIOS routines in all its tests -- no tricks! It makes your computer work hard , but can't harm it. If BurnIn causes your system to fail, then it's just doing its job, forcing a failure which would have happened soon. SYSTEM REQUIREMENTS =================== BurnIn will run on any IBM-compatible computer with 256K of RAM. It adjusts itself to all display adapters. BurnIn senses the availability of a mouse and uses it if it's there. BurnIn requires DOS version 3.0 or later. NOTE: BurnIn DOES NOT run on Tandy 1000 HX computers or any other Tandy computer with MS-DOS in ROM! To use BurnIn with these computers, you must boot with DOS 3.0 or later from a floppy disk in drive A:. WHAT BURNIN DOES ================ When you run BurnIn, you can run tests on one system or all systems in a PC, either continuously or on a one-time or for a length of time you specify. You select the tests to run, or you can run them all sequentially. BurnIn tests include: * CPU Test -- This test computes a difficult calculation thousands of times, incrementing the calculation as it goes. The results of the calculation appear in columns on the screen. Double-precision numbers are used. If a math co- processor is installed, it is automatically used in the calculation. * Drive Test -- You specify the drives to be tested. BurnIn writes, then reads, a 32K text file on each drive specified. When the test is finished, the files are deleted automatically. * Text Monitor Test -- This test exercises the monitor and display adapter by writing a continuous string of characters. Color monitors display the basic 15 colors. Following this, a series of boxes appears on the screen. * Graphics Test -- This routine runs through a series of graphics tests, exercising both the monitor, display adapter, and system BIOS. BurnIn automatically senses the display adapter installed in the PC and adjusts itself. * Memory Test -- This test finds all free system memory and does a write/read test on it. If there is an error on this test, it's likely that the system will crash. Parity errors especially cause a hard system crash. Use a memory diagnostic utility to pinpoint the location. * Printer Test -- This routine, which is turned off by default, prints a page of random ASCII characters, then ejects that page. In most cases, you'll want to run this test alone. The printer must be attached to LPT1:. BurnIn maintains a log file which records the starting time, ending time, and elapsed time for each test. If errors occur during a test, this information is logged as well. This information is stored in the file, BURNIN.LOG. The log file may be read while in the program. On completion of tests, a box will appear, telling you whether any errors occurred. A special file, readable from within the program, offers explanations of any error messages written to the BURNIN.LOG file. INSTALLATION ============ Installing BurnIn is easy. Simply copy all the files on the BurnIn disk to a directory on your hard disk or to a blank, formatted floppy disk. BurnIn files include: BURNIN.EXE -- The BurnIn program itself. BIDOCS.COM -- This manual. You can read it from inside BurnIn or from DOS. README.COM -- Basic information on BurnIn. (Self-browsing) BURNIN.ERR -- Help file for error messages. MCOLOR.DAT* -- Configuration file...stores screen colors. ????????.RUN* -- Configuration files .. store BurnIn configuration settings. BURNIN.LOG* -- Stores information on tests run by BurnIn. * Files created by the program. RUNNING BURNIN ============== BurnIn is designed to be exceptionally easy to use. Through the use of the Interface Plus system, it offers full mouse support, drop down menus, and anticipates your next command over 90% of the time. Interface Plus is a program shell for QuickBASIC 4.5, developed by this author. If you are a QuickBASIC programmer, please see the notes on Interface Plus at the end of this document. Run BurnIn by changing to the directory containing the BurnIn files, then give the command: BURNIN <Enter> After a short setup period, you'll see the program's main menu. USING INTERFACE PLUS PROGRAMS ============================= All programs which use the Interface Plus system work the same way. They're designed to offer you multiple options and ways to work, adapting to your personal style. On the top line of the menu are several entries. These are major functions. You may select one of these by typing the first letter of the menu entry, by using the left and right cursor keys, or by clicking on an entry with your mouse. Use either mouse button. Below each main menu item is a drop-down submenu. At startup, the Files submenu is active. As you move between main menu items, the appropriate submenu drops down. Select entries in submenus by using the up and down cursor keys to highlight your selection, then press <Enter>. You can also press the number of the menu entry or click on your choice with the mouse. Menu Intelligence ----------------- In many cases BurnIn, like all Interface Plus programs, will present you with a submenu entry, pre-highlighted. By using intelligent menus, you can often bypass several keystrokes. The mouse cursor automatically appears in the correct position as well. Inputting Data -------------- When BurnIn wants data from you, a box will pop up in the middle of the screen. You'll find information there, along with a place to type in the data needed. Press <Enter> after typing data. OK and YES/NO Buttons --------------------- In many cases, BurnIn needs to get a confirmation from you, or get a YES or NO answer. In those cases, you'll see a small box, either free-floating or attached to another box. If the button says OK, press any key or click on the button to proceed. If the button says YES and NO, press Y or N or click on the appropriate word. SUMMARY ======= That's all there is to using any Interface Plus program. You'll find the process intuitive, easy and even fun. BURNIN MENUS AND COMMANDS ========================= What follows is a list of BurnIn's menus, with a description of the functions in each menu. Following this section is a tutorial for a typical BurnIn session. FILE MENU --------- 1. Shell to DOS This command lets you carry out other DOS commands without leaving BurnIn. An input box will open, allowing you to enter a DOS command. You can also press <Enter> alone to use the DOS prompt. Type EXIT, then press <Enter> to abort the command. If you shell out to the DOS prompt, give the command EXIT <Enter> to return to BurnIn. Note: If you enter a DOS command in the input box, a floating OK button will appear in the bottom right corner of your screen after command execution. Press any key or click on the box to return to BurnIn. 2. Quit Program You'll have an opportunity to confirm this command with a YES/NO button. You'll see my shareware request when you quit. Please consider registering BurnIn. CONFIGURE MENU ============== 1. Set Screen Colors This command lets you choose your favorite screen colors for BurnIn. Mouse users can simply click on their color choices, following the screen prompts. Keyboard users must type in the numbers associated with the colors. After color selection, you can choose the background appearance for the program, following the same guidelines. You can then save these colors in a file, MCOLOR.DAT, if you choose. If you save the colors, they become the default colors when you start BurnIn. 2. Load a Configuration File [] BurnIn can save the settings you make for BurnIn in special configuration files. If you use BurnIn with several computers, this can save you time. Files have the extension .RUN and are created with the next command. This command lets you choose a file from a list on the screen, either by clicking with the mouse, or by typing in the filename, if you have no mouse. If a file is currently active, its name will appear in the brackets. 3. Save Configuration This command lets you save the current status of BurnIn in a file which can be loaded with the command above. As you look at the following menus, you'll see that some settings are preceded by an asterisk (*). These settings are saved in configuration files. Use this command to help you automate BurnIn. 4. Delete a Configuration File This command lets you delete configuration files from your disk drive. As with the Load Configuration command, you select files from a list, one-at-a-time. 5. Restore Defaults If you have loaded a configuration file, then wish to return BurnIn to its normal startup settings, just give this command. OPTIONS MENU ------------ The options in this menu are basic configuration options used by BurnIn. All are saved in configuration files, if you use them. 1. *Mouse Drive On? [YES/NO] This is a toggle command. Use it to turn your mouse off or on. The current status will display in the brackets. 2. *Toggle Elapsed Time Display [ON/OFF] During BurnIn's tests, the elapsed time can appear on the screen. Normally this is set ON, but you can toggle it on and off with this command. The elapsed time is written to the BURNIN.LOG file, regardless of the state of this command. 3. *Set Path for BurnIn Data [path] This command allow you to run BurnIn from other directories, as long as the BURNIN.EXE file can be found in a directory in your PATH statement. Enter the directory where BurnIn's data files can be found here. The trailing backslash (\) is optional. The current path displays in the brackets, and is normally the path where BurnIn is started. NOTE: You can also set this path with the DOS SET command, storing the path in the environment area. BurnIn checks for the BURNIN variable in the DOS environment as soon as it starts. Use this if you commonly start BurnIn from another directory. Here's a sample: SET BURNIN=C:\BURNIN 4. *Toggle Log File Creation [ON/OFF] You may wish to cancel BurnIn's logging of tests. If so, toggle this command. The default setting is ON. TESTS MENU ========== Items under this menu are toggles for the "Run All Selected Tests" command in the "Run" menu. You can turn any of the tests on or off by giving the appropriate command. These toggles are saved in configuration files. 1. *Disk Tests [ON/OFF] This toggles disk testing on or off. Default is ON. Tests are done on the disks specified in the "Drives" menu. 2. *Text Monitor Tests [ON/OFF] Toggles the text monitor tests. Default is ON. 3. *Math and CPU Tests [ON/OFF] Toggles the math and CPU tests. Default is ON. 4. *Printer Test [ON/OFF] Toggles printer testing. Default is OFF. 5. *Graphics Tests [ON/OFF] Toggles graphics monitor testing. Default is ON. 6. *Memory Tests [ON/OFF] Toggles memory testing. Default is ON. RUN MENU ======== 1. Run All Selected Tests This command runs all the tests you marked as ON in the previous menu. Depending on the settings of menu items 7 and 8 in this menu, the tests run continuously or for a time you specify. Tests run sequentially, and can be aborted at any time if you press ANY key. NOTE: BurnIn traps most errors and continues to run the tests! You need to read the error log by using the command in the "UTILITIES" menu to discover errors. Some errors, however, are fatal. These errors will cause BurnIn to exit and a DOS error message will appear on the screen. When the tests are finished, you'll see a box with a count of errors, if any occurred during the tests. 2. Run Disk Tests This command runs only the disk tests, using the disks set to ON in the "Drives" menu. The tests run only once. 3. Run Text Monitor Tests Runs the two text monitor tests one time. 4. Run Math and CPU Tests Runs the calculation test one time. 5. Run Printer Test Runs the printer test one time. 6. Run Graphics Tests Runs the graphics test series one time. This command makes a nice demo of your graphics capabilities. If you use it for this purpose, you may want to turn the elapsed time display off in the "Options" menu. 7. Run Memory Tests Runs the memory tests one time. 8. *Continuous Run [ON/OFF] This command toggles BurnIn to run tests continuously. Default is ON. If you set it to OFF, you must provide a run time in the next command. 9. *Set Run Time [time] Hours This command lets you set a specific running time for your BurnIn test series. Enter the time in hours and decimal fractions of hours. e.g. 5, 6.5, etc. If you use this command, Continuous Run is automatically set to OFF. NOTE: Routines will not automatically end at the set time. The time is checked only at the ends of routines, so time may exceed your setting by a few minutes. UTILITIES MENU ============== 1. Format Drive A: Formats a floppy disk in drive A: The DOS FORMAT command must be available. 2. Format Drive B: As above, but for drive B: 3. Read Log File Displays the BURNIN.LOG file created during a run of tests. The file is displayed one screen at a time. Press any key to see the next screen, or <Esc> to return to BurnIn. If no errors occurred, a box will tell you so, and there's no need to read the log, unless you just want to see a record. 4. Delete Log File Deletes the BURNIN.LOG file from disk. Since BurnIn always adds to the end of the existing file, so use this command to remove old version of the log. DRIVES MENU =========== Use this menu to select drives for use in BurnIn's drive tests. Each menu entry toggles one drive on or off. As a default, only Drive C: is toggled on. All drive settings are saved in configuration files, if you use them. NOTE: Do not toggle LOGICAL drives ON! This will cause BurnIn to stop operation. What's a logical drive? It's a drive which doesn't really exist, but which DOS substitutes. An example is Drive B: on single floppy drive systems. It's there, but don't use it with BurnIn. Similarly, drives created with DRIVER.SYS cause the same problem. Toggle on only physical drives! CAUTION: BurnIn is designed to test HARDWARE. Before running it, turn off any disk caching software and disable any ASSIGN commands. They won't hurt anything, but what's the point? 1. *Drive A: [ON/OFF] I'm only going to show one of these. Give this command to either use Drive A: in testing or not. The current state appears in brackets. All drive settings are similar. HELP MENU ========= 1. Read Manual Does just what it says....lets you read this file. You can move up and down within the file by using normal cursor keys. If you want to print the file, press T, then type PRN and press <Enter>. Make sure your printer is on and has paper. You can also create an ASCII file of the manual for loading into your word processor with the same command. Instead of typing PRN, type your desired filename. 2. Shareware Information VERY IMPORTANT! You'll see this anyway, but I wanted to give you another opportunity. When you decide to register, see the REGISTRATION INFORMATION below. 3. Common Error Messages This command displays a list of error numbers you may see in the BURNIN.LOG file, along with their descriptions. NOTE: BurnIn is not a diagnostic program. It's designed to be a system exerciser. If you experience an error not described here, see your dealer or use a diagnostic program. 4. Dos Environment Info This command will remind you how to use the DOS SET command to help you use BurnIn from other directories. BURNIN TUTORIAL =============== Here are the steps for a typical BurnIn session. 1. Start BurnIn 2. Select the Options Menu Check each toggle in this menu to make sure it's set the way you want it. 3. Select the Test Menu If you're going to run a set of tests, rather than individual tests, toggle the tests you want to use to the ON setting. 4. Select the Drives Menu If you'll be running drive tests, toggle on the drives you want to test. 5. Select the Run Menu Choose the "Run All Selected Tests" command. Testing begins immediately and will run until you press a key. If you want a specific run time, use option 8 to specify the time. 6. Check the BURNIN.LOG file. When your tests are complete, the "Read Log File" command is pre-highlighted. Just click or press <Enter> to review the results of the tests. If no errors occurred, you won't need to do this step. 7. Read the "Common Error Messages" documentation. Do this only if you encountered error messages in the BURNIN.LOG file. 8. Select the Files Menu Choose entry 2 to quit the program. It's easy! Naturally, you can use any of the other commands, as you choose. REGISTRATION INFORMATION ======================== BurnIn is a Shareware Program, copyright 1990 by George Campbell. It is NOT in the public domain. If you use BurnIn, and are satisfied with it, please become a registered user. Remember, the peace of mind of knowing your system is OK is worth something. If BurnIn finds a problem while your system is under warranty, it's worth even more. Registration costs only $15, and entitles you to use the program on as many PCs as you like. Registered users receive the latest version of the program, a version which does not have any shareware registration screens. Registered users are also entitled to notification of updates to BurnIn, and can receive updated versions for a low $5 fee to cover disk mailing. Registered users also receive unlimited support, which means you get my telephone number! NOTE TO SYSTEM HOUSES AND CLONE BUILDERS ---------------------------------------- Registration is REQUIRED for commercial use of BurnIn. You need only to register ONE copy, which you can use on as many systems as you like. It's cheap insurance for bad systems, and if you register, you may ship a copy of the BURNIN.LOG file for that system with the system. If you use BurnIn commercially, I expect you to register! Send $15 registration fees to: George Campbell 1472 Sixth St. Los Osos, CA 93402 Specify 5.25 or 3.5 inch disks. ========================================================================== WELCOME TO INTERFACE PLUS! Version 2.1 The Solution For Your QuickBASIC 4.5 Problems ============================================= by George Campbell 1472 Sixth St. Los Osos, CA 93402 CIS: 71571,222 GEnie: G.CAMPBELL BBS - (805) 528-3753 INTRODUCTION ============ After writing dozens of shareware and public domain programs in QuickBASIC, I finally figured out that I was re-inventing the interface wheel for each program. As I developed my skills, my interfaces became more and more sophisticated. BUT -- I was still rewriting the things for each program. Finally, I came up with an answer. Why not create a universal interface for all my software....one which was flexible enough to handle a single menu, and complex enough to work for a complex program with dozens of choices? Out of that need comes Interface Plus, the program you're looking at today. The interface itself became an obsession: Every time I turned around, I found another thing it needed. Mouse support? Of course! Built-in routines for common needs? Certainly! Drop-down menus? What else? In any case, I finally brought the program to a point where I felt it was good enough for my programs. Now, I'm offering it as a shareware program to aid other QuickBASIC programmers. Can it work for you? WHY YOU NEED INTERFACE PLUS =========================== If you write shareware software, you already know that registration checks from users depend on your program. If it's complete and easy to use, you get checks. It's that simple. By writing your program within Interface Plus, you assure better registration response. Your program, no matter what it does, has a state-of-the-art interface. You save time, too. Since you don't have to re-invent the interface wheel each time you create a new program, you can focus on YOUR routines. Finally, since your programs will be in a flexible interface, adding new functions as you upgrade is a walk in the park. You can add new menu items just by writing three lines of code. SYSTEM REQUIREMENTS =================== Interface Plus will run on any IBM-compatible PC. It needs 256K of memory, DOS 3.0 or a later version, but will work on any monitor. The mouse is optional. Its mouse-handling routines are designed to support ALL mice, including the IBM PS/2 mouse. The program automatically determines what's available in any PC, then adjusts itself accordingly. As a programmer, working with Interface Plus, you'll need 640K, QuickBASIC 4.5 or later, and DOS 3.1 or a later version. A mouse is a good idea for testing. FEATURES ======== Interface Plus has an extensive features list, with handles you can build on to make all your programs more powerful. Here's a fairly complete list: USER FUNCTIONS Windows-like text interface Drop-Down Menus Mouse Support Automatic Configuration All menu functions can be accessed by: 1. Mouse click 2. First letter keypress 3. Cursor keys plus <Enter> Intelligent Menus (jumps to next logical choice) Screen Color Selection built-in. (point and click) Screen background choices File selection from screen list File Viewer Shell to DOS with command or just to prompt Pop-up windows and input boxes OK and YES/NO buttons for mouse or keyboard Configuration file automatically saves YOUR setup Environment variables for power users Automatic return to original directory Totally intuitive operation PROGRAMMER FUNCTIONS ==================== MENUS Full drop-down, with mouse, keyboard, or cursor-key control Up to 240 separate menu items Easy menu setup, with all menu variables in one place Automatic sizing and positioning of menus Total menu flexibility MENU INTELLIGENCE By adding two simple variables, you can make your Interface Plus applications intelligent. After executing one function, your user finds him or herself looking at the next logical menu -- already highlighted. You control this easily. MOUSE SUPPORT By keeping mouse functions simple, this program is completely independent of type of mouse. It works with ALL mice, automatically. Mouse Cursor Control -- YOU decide where you want the mouse cursor to be. Combined with intelligent menus, you can always place the cursor in the next logical spot. Detect clicks Find mouse location Turn mouse on or off with a command WINDOWS and BOXES Built-in input or information box with: Fixed location for instant user recognition. Room for three 60-character lines of text OK button or YES/NO button optional Custom Screen Windows with: Flexible sizing Total color control 5 Border types One-line call to create box on screen Multiple boxes on screen at once. OK and YES/NO buttons: Can be positioned anywhere on screen One line call to create button Accept mouse click or keystroke Optional defaults Mouse cursor is automatically on button! Program Intelligence Interface Plus checks the user's system and knows these things: Memory Size DOS Version Monitor Type Mouse status Available Drives (A: to H:) (NOTE: The drive check is currently REMmed out in this version. It occasionally leaves a temporary file behind on LOGICAL drives. You can decide for yourself whether to use the DriveTest routine) Original Directory Current Directory Environment path setting for your data files File choice - if file is selected Command line parameters MORE! Programmer-accessible routines include: Directory Display File Selection Change Directory Display ASCII file Mouse cursor position - set or read Mouse cursor on or off Programmable delay Print Screen Send Formfeed Change File Mask for directory search Shell to DOS Input box -- described above OK and YES/NO buttons -- described above Sizable and movable windows Read in Color data from file. Write and read configuration file. Keystroke filter -- tells you what key has been pressed, including all function keys, plain or shifted, and cursor keys. Easy string-type identifiers. FAST! MORE! PROGRAM LAYOUT Interface Plus is written TOTALLY in QuickBASIC 4.5. There are no hidden routines or libraries. All routines are included and may be altered to suit your needs. You get COMPLETE source code! All variables and routines have long, readable names. You won't have to remember cryptic variable and routine names when you insert your own code. Interface Plus is clean and well-designed. It uses the appropriate QB tools in the appropriate places. CALLed subroutines and GOSUBs are use throughout, depending on the need for global or local variables. NOTICE: There are three places where GOTOs are used, but they never leave a routine, so cause zero problems. Where appropriate, Interface Plus uses INTERRUPT-driven routines. Mouse control, file lists, and others are included. Since these are fundamental to the program, you don't need to know how to use interrupts to use them. There here for speed and to add support for functions not supported by QuickBASIC. The Interface Plus source code is in three sections. 1. The main menu section. All menu design tools are right up-front and easy to use. The QB SELECT CASE function is used throughout. 1. GOSUB subroutines These routines use global variables. Every precaution has been taken to clear variables when needed. Here's where you add your own stuff. 2. Called subroutines Most of these are integral to the interface itself. Calling each of these means that you must pass variables to the routine. Since variable names are clear and understandable, it's easy. Individual routines are separated by comment lines, clearly identifying them. The full documentation package even includes keywords for jumping to any routine while in the QB environment. LICENSING INFORMATION ===================== Interface Plus is shareware, and has a four-tiered licensing structure, along with several registration methods. First and foremost: YOU NEVER PAY ROYALTIES WHEN YOU USE INTERFACE PLUS! Overall Licensing Interface Plus contains code which will identify it, regardless of how you use it. In addition, a copyright notice is included as a string constant in the program. This notice will NEVER appear to your customers, but MUST remain in the source code, without changes. It will appear in the .EXE file, if a hex editor is used. No licence granted allows removal of that code or copyright notice. Regardless of the license type, users may alter any portion of the Interface Plus source code to suit their needs. Here's a rundown on licensing and registration options: Public Domain and Personal Use license: You may use Interface Plus to create personal programs and programs you place in the public domain at no charge whatsoever. I want to encourage the development of free programs. By public domain, I mean programs which are offered to the public with no registration fee whatsoever. You may, of course, want to take advantage of the $10 registration offer, which brings a clean version of the source code, and more documentation. Shareware Licence: If you use Interface Plus to create shareware software, wherein you request a registration fee from users, the licence fee is $60. That's just three $20 registrations, so it's not all that expensive. See the Registration Information below to see what you get for your $60 registration fee! Corporate In-House License: If you use Interface Plus to create applications which will be used internally WITHIN a corporation, the license fee is $125. This fee entitles you to distribute unlimited copies of a program using Interface Plus WITHIN a single corporation. Under this fee, you MAY NOT sell or otherwise distribute a program outside your corporation or to clients of your corporation. Commercial License: If you use Interface Plus to create software which you will sell outright to customers, whether corporate or individual, the license fee is $1000. It's simple: If a program using Interface Plus has a price tag and is not distributed as shareware, you must buy a Commercial License. REGISTRATION INFORMATION ======================== Here's what you get for each of the license formats: Public Domain and Personal Use License: COST: $10 INCLUDES: 1. Full source code, both for the demo version and for the cleaned-up version with no built-in menu functions. 2. 5.25" or 3.5" diskettes. 3. Basic documentation, on-disk, which includes all information needed to use functions in Interface Plus. 4. TXT2COM -- a shareware text-to-COM file utility for creating self-browsing text files. 5. Limited support on CompuServe, GEnie, or the author's BBS. No telephone support is included with this license. All other Licenses: COST: Varies INCLUDES: 1. Full source code, both for the demonstration version and the empty version. 2. 5.25" AND 3.5" Diskettes 3. Laser-printed manual in three-ring binder. Manual includes: a. Detailed source code comments b. Full variable list, with calls and functions c. Full subroutine details, with parameters and syntax. d. Menu-design tips and parameters. e. Printed copy of both source code sets for study. f. Hints and tips for making Interface Plus work for you. 4. Telephone support, along with the other support tools. 5. Notification of upgrades. Upgrades will cost $15, and will include new disks, and manual pages for quick insertion. ORDER FORM INTERFACE PLUS George Campbell 1472 Sixth Street Los Osos, CA 93402 YES! I want to order a Registered Version of Interface Plus! Please send the version checked below. I'm enclosing a check or money order. ___ Personal Use License ($15) ____ 5.25" ___ 3.5" ___ Shareware License ($60) ___ Corporate In-house License ($125) ___ Commercial License ($1000) (See section above for what's included) AMOUNT ENCLOSED: $____________ (Includes shipping) SEND TO: NAME:_______________________________________________________ STREET:_____________________________________________________ ____________________________________________________________ CITY:____________________________STATE:_____ZIP_____________ FINAL NOTE: If you're reading this, but haven't yet seen a copy of Interface Plus, be sure and download your copy of NRFACE.ZIP soon. You'll wonder why nobody did this before!