----------------------------------------------------------------------------- SCSI-TESTER V2.0 © 1993 by John Yeager All Rights Reserved ----------------------------------------------------------------------------- THIS PROGRAM IS SHAREWARE. I HAVE SPENT MANY COUNTLESS HOURS IN DEVELOPING THIS SOFTWARE, SO PLEASE, IF YOU FIND THIS SOFTWARE USEFUL --- REGISTER --- AND KEEP AMIGA PROGRAMMERS DEVELOPING SOFTWARE THAT IS USEFUL AND AFFORDABLE. (See end of this doc file for registration info.) WHILE BEING SHAREWARE, THIS SOFTWARE IS FREELY DISTRIBUTABLE AS LONG AS ALL FILES IN THE ARCHIVE ARE LEFT INTACT AND ONLY A NOMINAL FEE IS CHARGED FOR ITS DISTRIBUTION. THIS SOFTWARE IS PROVIDED "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED. BY USING IT, YOU AGREE TO ACCEPT THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM. THE LOG FILE IS *NOT* CREATED IN THE *UNREGISTERED VERSION* OF SCSI-TESTER EVEN THOUGH THE PROMPTS IN THE PROGRAM MAY TELL YOU IT IS... (See the example log files in this archive for sample output.) Program Description: ~~~~~~~~~~~~~~~~~~~ SCSI TESTER was written for the purpose of exercising your hard drives, your SCSI controller, your SCSI cabling, SCSI device driver code and more to determine if there are any faults present on your SCSI bus and/or hard drives. Program Requirements: ~~~~~~~~~~~~~~~~~~~~ KickStart and WB 2.04+ are REQUIRED for this program to run. If you try to start the program on any system with LESS than version 37 of the system libraries it will inform you of that, and then just exit. Program Startup: ~~~~~~~~~~~~~~~ The program may be started via the CLI or from WorkBench. If started from the CLI you'll need to enter the SCSI device driver name that you want to use. If not supplied on the command line, the program will not start. Example usage is: SCSI-TESTER gvpscsi.device If started from Workbench via the supplied tool icon, SCSI-TESTER uses the ToolType name of DRIVERNAME=xxxxxxxx.device to start the program. The DRIVERNAME tooltype, if not supplied in the icon, WILL DEFAULT to GVP'S driver name of gvpscsi.device when the program starts. ************* **IMPORTANT** ************* The SCSI device driver name *IS* case sensitive as is the ToolType of DRIVERNAME= . DRIVERNAME= must be all upper case with the equal sign right after the E and right before the start of the actual SCSI device driver name as in: DRIVERNAME=scsi.device . The actual driver name *MUST* be case specific when supplied to either the CLI startup or the Workbench startup. I.E.: Correct ===> gvpscsi.device OR scsi.device INCorrect => GvpScsi.device OR Scsi.Device ************* **IMPORTANT** ************* To prevent a non-crashing innocuous Enforcer hit when starting SCSI-TESTER from WorkBench, a stack size of 8K, (8,192 bytes), *MUST* be set and saved in the icon. This is due to the Workbench startup code and will be modified and fixed in the next release. Program Gadgets, Requesters & Display Operations: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ There are 8 gadgets in the program window. They are: ---------------------------------- o SCSI Device Driver: o Test Intensity: o SCSI ID: o BOARD: o LUN: o START o CANCEL o THE USUAL CLOSE WINDOW GADGET... ---------------------------------- o The SCSI Device Driver gadget is a string gadget that you can use to change the device driver name without having to exit and then restart the program. Just make sure you follow the guidelines laid out in the "Program Startup" section above in regards to case specificity for the driver name. This gadget is ghosted and not usable while the test is running. o The Test Intensity gadget is a cycle gadget that sets the intensity of the head seeks between the two data reads that always occur for each sector on the hard drive. I.E: NOHEAD --> Does NOT do any head seeks between disk read compares. NORMAL --> Does 1 seek between disk read compares. HEAVY1 --> Does 3 seeks between disk read compares. HEAVY2 --> Does 15 seeks between disk read compares. As you will notice, progressing from NOHEAD thru HEAVY2 will slow the entire run down. However, as an example, HEAVY2 will more thoroughly test your hardware than NOHEAD will. This gadget is active at all times and may be cycled as you wish. o The SCSI ID cycle gadget is used to select the SCSI ID that you wish to test. The range is from 0 to 7. This gadget is only active prior to starting a run and then ghosted. o The BOARD cycle gadget is used to select from multiple SCSI controllers you might have installed in your machine. Currently, this gadget cycles from 0 to 6. (I can't believe that too many people could have more than 7 separate and distinct SCSI controllers in their Amiga, however, if this is inadequate, please let me know!) This gadget is only active prior to starting a run and then ghosted. o The LUN cycle gadget is used to select from 0 to 7 different LUN's, (Logical Unit Numbers), that may exist with your type of SCSI controller. This gadget is only active prior to starting a run and then ghosted. o The START button gadget starts the run of the program after the above other gadgets have been set. This gadget will ghost when SCSI-TESTER is actually testing a device. o The CANCEL button gadget will cancel a run in progress. This gadget starts off as ghosted before a run and then unghosts while a test is in progress. CANCELLING A PROGRAM RUN IN PROGRESS WILL NOT BE DESTRUCTIVE IN ANY WAY... THE PROGRAM IS ONLY PERFORMING READS AND SEEKS ON THE SCSI DEVICE IN QUESTION!!!! o The CLOSE gadget that is in the upper left corner of the program window acts as a normal close gadget in WB2.04+. By clicking here you will exit the program. The close gadget is only active while the program is sitting idle, (i.e. before or after a test run). o The area above the start button gadget where the program name, copyright date, and my name is displayed while the program is idle will change to drive information data once a test is started on a device. o As the test progresses, a "Percent Completed" status line will be updated and the percentage calculated as the number of blocks tested is compared with the total number of blocks on the device. o The status bar indicator also increases for every 1% of completion. o The bevel box area in the center left of the program window will display important information about the test in progress as will certain program requesters that pop up. The messages are pretty much self explanatory as is the information in the requesters. Program Operation: ~~~~~~~~~~~~~~~~~ What the program does is to do a physical test of each and every sector on your hard drive, and the SCSI bus in general, and to report any errors via program requester and program window information and a log file. SCSI-TESTER will, using scsi-direct commands, read a sector of data, then, optionally move the heads, then re-read the same sector of data and then do a compare of that data sector in memory. Any sense errors and/or sector data errors are reported as directed in the above paragraph. Data sector sizes used in the program are determined at run time by interrogating the SCSI device directly. The amount of head movement between data reads is controlled by the Gadget labeled "Test Intensity". The details of that gadget are as follows: NOHEAD --> Does NOT do any head seeks between disk read compares. NORMAL --> Does 1 seek between disk read compares. HEAVY1 --> Does 3 seeks between disk read compares. HEAVY2 --> Does 15 seeks between disk read compares. This gadget is activated for the entire run of the program and you may toggle it as you wish *DURING* any operation. This program is NON-DESTRUCTIVE and only performs reads to the particular SCSI device ID selected. However, I do NOT place a inhibit on the logical partitions on the particular SCSI device being tested. In light of this I would strongly suggest that SCSI-TESTER be run without any other disk access to that particular SCSI device. The CANCEL gadget may be hit at any time during the run with no ill effects. All you will have done is to verify the sectors up to the point you hit cancel. ************* **IMPORTANT** ************* If you are testing on a SCSI bus that has numerous problems SCSI-TESTER *MAY* hang on the bus waiting for a response to it's message ports. This may cause your whole machine to hang. *BEWARE* If this happens, just reset your machine. A log file is *REQUIRED* for the program to operate. Some very detailed information is written here and I urge you to review this ASCII file after a test run has completed. I *STRONGLY SUGGEST* that you use a device to store the log file that *IS NOT* on the SCSI bus you are testing such as your RAM: disk or Floppy drives. The ASL requester is used to prompt for the log file. 2 log file ASCII examples are included for familiariaztion. Other Program Information And Other Shareware Information: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ***************** **PERSONAL NOTE** ***************** I have owned an Amiga since 1987 and have been a long time beta tester of JRComm and currently I am beta testing Jack Radigan's soon to be released successor, TERMINUS. I have also written many other programs in Aztec C and SAS C that I am using myself. Please let me know if there are other projects you wish to see worked on and I'll do my best to see if they are worth pursuing... REGISTRATION FEES ARE AS FOLLOWS: 1) NON-COMMERCIAL INDIVIDUAL FEE: $15.00 U.S. 2) COMMERCIAL USER SITE LICENSE AND/OR COMMERCIAL USER FEE BY CPU: CONTACT ME FOR MORE INFORMATION. REGISTERED USERS WILL RECEIVE: 1) FREE TECHNICAL SUPPORT THRU THE CONTACTS I HAVE LISTED AT THE END OF THIS DOC FILE. 2) PHONE SUPPORT!!! 3) ONE (1) FREE UPDATE TO A MAJOR REVISION. MAILED DIRECTLY IF NEEDED. (I.E. V2.0 TO 3.0). 4) BUG FIXES AS NEEDED THRU ELECTRONIC DISTRIBUTION, OR FOR NOMINAL SHIPPING AND HANDLING CHARGES, THRU OTHER DELIVERY SYSTEMS. 5) MY COMMITTMENT TO YOU TO FOLLOW UP AND FIX PROBLEMS THAT MAY ARISE AND TO BE OPEN TO YOUR ENHANCEMENT SUGGESTIONS OF FUTURE VERSIONS. 6) SCSI-TESTER THAT IS OPTIMIZED FOR YOUR PARTICULAR PROCESSOR(S) TO INCREASE PROGRAM PERFORMANCE. 7) A LOG FILE THAT IS ACTIVATED. TO REGISTER SEND $15.00 IN U.S. DOLLARS IN THE FORM OF CASH, CHECK DRAWN ON US BANK OR A POSTAL MONEY ORDER. PAYEE ON CHECK OR MONEY ORDER SHOULD BE MADE OUT TO ==> THERESA YEAGER SEND TO THIS ADDRESS: THERESA YEAGER 35 SURREY WAY EXTON PA 19341-1670 CASH PAYMENTS WILL HAVE A RECEIPT MAILED WITH THEIR DISK. MONEY ORDER AND CHECK CONTRIBUTORS WILL HAVE EITHER THEIR CANCLLED CHECK OR THEIR MONEY ORDER RECEIPT AS PROOF OF PAYMENT. INQUIRIES, BUG REPORTS, COMMERCIAL LICENSING AGREEMENTS, PROGRAM SUPPORT, SUGGESTIONS, ETC, CAN BE OBTAINED BY THE FOLLOWING METHODS: ELECTRONIC MEANS VIA E-MAIL: ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| |PAUG (Philadelphia Amiga Users Group) BBS USA | | | |MODEM: +1 215-551-1485 9600 > 14.4 BAUD (USR Dual Standard) Line #1 | | +1 215-551-6113 2400 > 14.4 BAUD (USR HST) Line #2 | | +1 215-551-1120 2400 > 14.4 BAUD (SupraFaxModem v.32bis) Line #3 | | +1 215-551-1121 2400 > 14.4 BAUD (USR HST) Line #4 | | | |FIDONET Address: 1:273/912 | | | | | |Address Mail To: John Yeager | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| OR ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| |Genie Local Mail: | |Address Mail To: J.Yeager5 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| OR ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| |Internet Mail: | |Address Mail To: j.yeager5@genie.geis.com | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| OR, Lastly ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| |The U.S. Mail | | | |JOHN YEAGER | |35 SURREY WAY | |EXTON PA 19341-1670 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||| I have tested the program extensively on my system with a PP&S 68040 equipped A2000 with a GVP Series II hard card and three hard drives, (Quantum 40Q, Seagate ST296N, and a Maxtor 213SY), with version 3.15 of the gvpscsi.device. It has also been tested in 68000 mode. Tests in '040 mode were made with Enforcer V37.35 activated. It has also been tested on an A2000 with a GVP 68030 accelerator with a GVP Series II controller with no problems.