CORRECT.EXE Usage Notes

This program (including instructions for its use) is provided "as is" 
without warranty of any kind.  The entire risk arising out of the use or 
performance of this program and documentation remains with you.

CORRECT.EXE will correct most instances of partition corruption that are 
caused by a problem with Windows NT 3.51 and the 3.51 version of Disk 
Administrator.  CORRECT.EXE will not repair corruption not caused by Disk 
Administrator.

To determine whether your drives have been affected by the Disk 
Administrator problem, first run CORRECT.EXE once for each physical hard 
disk seen by Windows NT.  "CORRECT /d#", where "#" is the zero-based 
number of the hard disk you wish to check.  For example, on a system with 
two physical drives, you would run:

CORRECT /d0
CORRECT /d1

If CORRECT.EXE does indicate that your disk has been affected, you should 
take any steps necessary to back up important data before attempting to 
fix the error.  Keep in mind that user or filesystem data on the disk may 
already have been damaged, so existing backups are preferable whenever 
available.

To have CORRECT.EXE attempt to repair partition damage for two physical 
drives, run:

CORRECT /d0 /f
CORRECT /d1 /f

NOTE:  You may need to shut down and restart your system after running 
CORRECT.EXE with the "/f" switch in order for the operating system to 
recognize the fixed drives.

More Information:

In some limited cases, running Disk Administrator from the released version 
of Windows NT 3.51 could result in partition table corruption.  This 
corruption could render portions of a hard disk inaccessible.  

In particular, disks with more than two logical drives in an extended 
partition are susceptible to the problem.  Disk Administrator would only 
corrupt such drives if and when it had to write a "fault tolerance 
signature" to the drive.  This signature is used to uniquely identify disks 
for purposes of software RAID, and is ordinarily written to the disk the 
first time Disk Administrator is run. Ordinarily, writing this signature is 
not a problem.  However, a problem in the Windows NT 3.51 kernel has caused 
the operation to malfunction in the specific situations mentioned above 
when the 3.51 version of Disk Administrator was run.  

The kernel problem mentioned above is strictly limited to operations 
involving disk partitioning and in no way affects other operating system 
functions.  Furthermore, the 3.5 version of Disk Administrator is not 
affected by the problem and can be run safely on a 3.51 system provided 
that you are not using third party partitioning software.  If the kernel 
fix was not included with this program and you suspect you need the fix, 
contact Microsoft Product Support.  (The fix will be included in "Service 
Pack 2 for Windows NT 3.51."  Note: the kernel fix will only serve to 
prevent corruption from taking place in the first place if it is applied 
before Disk Administrator is run on a system.)

Due to the nature of the corruption that takes place, user and/or file 
system data can also be damaged by the problem.  Therefore, if you suspect 
that one or more of your disks has been corrupted by the 3.51 Disk 
Administrator problem, you should consider repartitioning and reformatting 
your drives and then reinstalling or restoring your data from previous 
backups rather than using data recovered by CORRECT.EXE.

In situations where a current backup is unavailable or where you are unable 
to repartition the drive because Disk Administrator will not run correctly, 
CORRECT.EXE may be helpful.  CORRECT.EXE scans the corrupt partition table 
and attempts to restore it to the state it was in before the corruption 
took place.  

CORRECT.EXE will correct most instances of partition corruption that are 
caused by the Disk Administrator problem described here, but there are some 
rare and particularly problematic cases that CORRECT.EXE will not be able 
to handle.  

If CORRECT.EXE does not restore all your logical drives to a consistent 
state, the only recourse at the present time is to delete any remaining 
logical drives.  If you encounter a situation where CORRECT.EXE does not 
repair one or more logical drives, you can use a "/x" switch in addition 
to the "/f" already mentioned.  This switch instructs CORRECT.EXE to 
DELETE logical drives that it is not able to recover and is intended to be 
used only if and when all else fails.