Category : System Diagnostics for your computer
Archive   : MDT10.ZIP
Filename : MDT.DOC

Output of file : MDT.DOC contained in archive : MDT10.ZIP
//// Monroy Diskette Test ////
//////////// and ////////////
////////// Analyzer /////////

Release: v1.0

(c) 1990 Julius_Ware
JM Enterprises

º Program Description º

The Monroy Disk Test is a utility to help you pinpoint
errors on your floppy diskettes. It does a track by track, cluster by
cluster verification of your diskette. It will detect any un-readable
clusters, report them to you by way of location (on screen). It will
detect errors ranging from bad clusters, controller errors, to drive
not ready errors (open floppy door). The test is NON-destructive,
and will not cause harm to your data.

The release of this version is strictly to detect and pinpoint errors
on your diskettes, it will NOT mark off clusters as bad and un-usable.
The next version will detect if a file is located in a bad cluster,
and prompt the user to mark them off as bad, or relocate them within
other parts of the diskette. So for now, it is strictly a diagnosis
tool for floppies that are acting up with errors.

The program has a simple analysis algorithm which uses the mode
averaging technique to "decide" on if an error is actually as
originally reported by the operating system. So whenever it finds
an error, it will re-scan the diskette sector again 10 times, and
report the error most frequently found.

º Usage, Parameters º

This program requires a command line parameter, which
is the specification of which drive to test for errors. For example,
if you wanted to test your floppy drive A:, you would call the program
like this:


Likewise, if you wanted to test your floppy drive B:, you would call
the program like like such:


If you call the program with no parameters, it will abort, warning you
that you did not supply the correct parameters. It will only accept
a drive designation, which is non-case sensitive.

º Notes about MDT º

* MDT also detects errors in the controller, which is handy
when deciding which piece of hardware might be faulty
(i.e., drive vs. controller, etc...).

* This program automatically detects drive type, diskette type,
and DOES require the diskette to be formatted with DOS before
it is tested for errors. It will only work with these formats:

360 k 5 1/4"
1.2 meg 5 1/4"

720 k 3 1/2"
1.44 meg 3 1/2"

* This program was written using Turbo Pascal v4.0.

* It uses the MS-DOS interrupts (21h), using the Turbo Pascal
interrupt library function (INTR), and is widely compatible.
Direct memory addressing is used, but should not pose a problem.

º Future Releases º

The next version of this program will have the ability to
detect if a damaged cluster is occupied by a file, and mark the cluster
as bad. It will provide a user-interactive menu to allow files to be
overwritten as bad or left alone. The program will also try to relocate
data stored in a bad cluster to a good cluster.
Future releases will also be able to test and mark off
bad clusters on HARD disks of all types. It requires a bit more
data retrieval as well as error analysis, thus the reason they are not
available in this release.

º Begging º

If there is anybody out there that finds this program
of use, please consider sending the author $10.00 for his efforts.
If you send in the dough, you get a copy of the source code as well
as the latest compiled version.

Here's the address:

Northern Lights
P.O. Box 7238
Menlo Park, California

Or, call my BBS to tell me the money is on the way.
The number is 415-324-2601 and supports 300/1200/2400/9600 bps.
Thanks for reading.
-=[ Julio Monroy ]=-

  3 Responses to “Category : System Diagnostics for your computer
Archive   : MDT10.ZIP
Filename : MDT.DOC

  1. Very nice! Thank you for this wonderful archive. I wonder why I found it only now. Long live the BBS file archives!

  2. This is so awesome! 😀 I’d be cool if you could download an entire archive of this at once, though.

  3. But one thing that puzzles me is the “mtswslnkmcjklsdlsbdmMICROSOFT” string. There is an article about it here. It is definitely worth a read: