Programmer 7500

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

/ Programmer 7500 / MAX_PROGRAMMERS.iso / PROGRAMS / UTILS / HARDWARE / BI43.ZIP / BIDOCS.COM (.txt) next >

Wrap

Graham's TXT2COM | 1990-10-23 | 31.7 KB | 724 lines

Burnin 4.3 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. New to this version is automatic command-line operation, which allows you to run BurnIn from a batch file in a standard con- figuration. Also, the new BURNIN.SUM file provides a one-page summary of BurnIn tests, which you can include when shipping your systems as proof of the burn-in and to show error-free operation. NOTE FOR USERS OF PREVIOUS VERSIONS OF BURNIN: ============================================== New Features! Version 4.3 of BurnIn adds automatic command-line operation, automatic disabling of tests on defective disks, and a conven- ient summary file, along with error-only logging as the default. Please read these docs for full information. IMPORTANT: Configuration (*.RUN) files from previous versions will NOT work with this new version, since new variables have been added. You must set up new configuration files for version 4.3. 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, 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 each test is finished, the file is 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. * 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 any errors which occur during a test. Optionally, you can record details on each test. 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. Another file created by BurnIn is a summary of its tests and their results. The file is created whenever you use the "Run All Selected Tests" command, and can be read from within BurnIn or printed from your DOS prompt. The filename is BURNIN.SUM 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. PRINTSUM.BAT -- Prints the summary file to LPT1: 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. BURNIN.SUM* -- Stores a summary of test results. * 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. 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, or to make command-line operation more useful. 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. 5. *Toggle Error-only Logging [ON/OFF] Most often, you won't want the exact time of each test as it runs to be printed in the log file. The default for this command is ON, which only prints messages to the log file if there has been an error. To print all information about each test as it runs, toggle this setting to OFF. 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. 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. One exception to the continuous running even after an error is when there is a disk error. To prevent continuous errors, BurnIn eliminates any disk which produces an error from the testing. Testing continues on other disks, however. 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. *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. 8. *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 Test Summary When BurnIn finishes a sequence of tests, using the "Run All Tests" command, it creates a summary of the results in a file named BURNIN.SUM. This command will display that file for you. If you want to print a copy of the summary, use the PRINTSUM.BAT file to do it automatically. Exit to the DOS prompt or use BurnIn's Shell to DOS command, and give the command PRINTSUM. Be sure your printer is on line. 4. 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. In fact, unless you have turned off error-only logging, there will be no file to look at if there were no errors. 5. 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. 5. Command Line Operation Info This command displays a screen containing information on Burnin's automatic command line mode. Use it if you've forgotten how to use the command line mode to completely automate your BurnIn session. COMMAND LINE OPERATION ====================== You can also run BurnIn directly from the command line. This option was added to the program to make life easier for systems houses and clone builders. It allows a user to set up a configuration file, then use a single command or batch file to automate BurnIn. NOTE: Before using BurnIn on the command line, you should run the program in menu mode and set up your configuration file, as described above. You'll want a custom configuration and test sequence, not the BurnIn defaults. Here's the command line syntax: BURNIN [configfile] [option] Both the configfile and options are optional, but must be entered in the order shown, separated by a single space. The [configfile] is the filename (without extension) for the configuration file you've chosen. If you leave this parameter out, BurnIn uses its defaults. The [options] allow you to run all tests or just a single tests. If you do not include an option in the command line, BurnIn loads the named configuration file, then starts in menu mode. Here is a list of options (use only one): A -- Run all tests named in the config file. D -- Run the disk tests one time. T -- Run text monitor tests one time. C -- Run the Math/CPU tests one time. P -- Run the printer test one time. G -- Run the graphics tests one time. M -- Run the memory tests one time. The "A" option will be the most useful, since it runs the tests continuously. To select tests, use the menu mode to create a configuration file. NOTE: You can include a total time for testing, allowing you to run a 48-hour test sequence, for example, since that value is stored in the configuration file. 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. Read the BURNIN.SUM summary file. 7. 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. 8. Read the "Common Error Messages" documentation. Do this only if you encountered error messages in the BURNIN.LOG file. 9. 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.