MemTest 1.0 (MAY/20/2001) © 2001 desdiSoft, Fernando Martínez . . . . . /\ /\ * C ||/\|| ./\ ( ) /\ . . . ||. ) °° ( || _||_/ __ \_||_ . . |o o TT o o| . ____|______||______|_____ ~~ d e s d i S o f t DISCLAIMER ~~~~~~~~~~ This software is subject to the MAILWARE concept. Please, see the COPYRIGHT document for more information. If you like it and use it regularly please send a mail or e-mail to: smail: Fernando Martínez C/ Juan Ramón Jiménez 4, 3ºD 34001 - Palencia SPAIN email: fernanmv@navegalia.com Please tell me any comments and/or sugestions. REQUIREMENTS ~~~~~~~~~~~~ Any Amiga running Workbench 3.0 or better should run this software. Simple! :) PURPOSE ~~~~~~~ The object of this program is to test the CHIP/FAST RAM of your Amiga to look for any possible failure. INSTALLATION ~~~~~~~~~~~~ Just copy the hole MemTest directory anywhere you want to use it. The program comes in two versions: 'MemTest-00' for 68000 processors and 'MemTest-20' for 68020 or better processors. Rename the one you what to use as 'MemTest'. You can also find two sizes icons in the 'Icons' directory if you whant to change it. USAGE / OPTIONS ~~~~~~~~~~~~~~~ The program can be started from either Workbench/CLI. In both ways you can use the same parameters/tooltypes following the format: <option>=<value> mem=chip|fast|both - Choose the type of memory you want to test: fast, chip or both. mode=vervose|quiet - Select 'vervose' to display output information. In 'quiet' mode only errors will be shown. fill=<value> Byte value to fill the memory with. dump=<from>-<to> - Dumps to the output the selected range of memory (before filling if you use it). From CLI you can use also '?' to display a short help. THANKS ~~~~~~ To my friend Travis Vaughn for helping me with my english. To Amiga Inc. for making the best computer system. HISTORY ~~~~~~~ Version 1.0ß (MAY/11/2001) First internal version. Beta version for testing period fully functional. Version 1.0 (MAY/25/2001) First public version. Internal improvements. Fixed output runing from Workbench. Fixed two internal errors, fortunately non dangerous. The test is now fully reliable.
Alek_NGI