BADCLU is a disk utility that grovels through an MS-DOS disk's data
area, marking bad clusters based on the number of retries it has to do
to read the sector.

usage:

    badclu -d drive -p partition [-r retries][-n|w][-m]

    -d      drive is the physical hard disk number (0 or 1)
    -p      partition is the logical partition number (0 or 1)
    -r      retries is the number of retries to attempt before marking
            a cluster as bad (default is 0)
    -n      do NOT write the updated File Allocation Table (overrides -w)
    -w      write FAT each time an entry is changed
    -m      allow marking most recent cluster by keypress during disk read

    this program is placed in the public domain

This program has severe limitations:

    (1) it does very little error checking about the disk info itself.
        running it on a non-backed up hard disk is probably stupid.
        it won't modify FAT entries which are in use, so it's ok in that
        respect, but if you have a weird disk layout, i do NOT take
        responsibility. BADCLU should be run on a disk that can be 
        sacrificed.

    (2) the handling of extended DOS partitions is extremely limited.
        specifically, if a logical drive you specify is an extended
        partition, you'll end up running the program on the first
        logical drive in that partition. You can't go any further than
        that.

WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING! WARNING!

This program can alter your hard disk. If you CANNOT read C, you probably
don't want to deal with it. This program should be compiled with Turbo
C using the HUGE memory model. This is so pointers cannot have any
weird bugs (if you're running this program, you have problems, so it
does not matter if you waste the extra CPU cycles or not).

If I ***EVER*** find this program on a BBS without this file or without *ALL*
the original source code, I ***WILL*** find the person responsible and have
that person's head on a stick. This is a useful utility, but I have placed
it in the public domain because I feel it will help people, and anyone using
this program's features to destroy someone else's data will be caught,
skinned alive slowly, and fed to my cat (the last two are concurrent processes).

BBS sysops should feel free to add remarks in the space provided.
If you add something, fine. Please do NOT delete.

****************************** SYSOP COMMENTS ******************************

******************************  END  COMMENTS ******************************

program by J. Alan Eldridge, 11 Maiden Lane #4C, New York, NY 10038

<end of file>
