2)  FDISK /STATUS ?

    Prints a screen just like using option 4 of fdisk "Partition
    information", but includes extended partition information.
    Nice if you want to get an overview without fear of pressing
    the wrong keys.
                              Armin Hanisch

    Doesn't work in Ver 3.30.

                              Mitch Ames

    FDISK /MBR

    MS-DOS 5.0 FDISK has an undocumented parameter, /MBR, that causes it
    to write the master boot record to the hard disk without altering the
    partition table information. While this feature is not documented, it
    can be told to customers on a need-to-know basis.

    What is the MBR?
 
    At the end of the ROM BIOS bootstrap routine, the BIOS will read and
    execute the first physical sector of the first floppy or hard drive on
    the system. This first sector of the hard disk is called the master
    boot record, or sometimes the partition table or master boot block. At
    the beginning of this sector of the hard disk is a small program. At
    the end of this sector is where the partition information, or
    partition table, is stored. This program uses the partition
    information to determine which partition is bootable (usually the
    first primary DOS partition) and attempts to boot from it.

    This program is what is written to the disk by FDISK /MBR and is
    usually called the master boot record.  During normal operation,
    FDISK only writes this program to the disk if there is no master
    boot record.

    Why is the MBR changed during Setup?

    During installation of Microsoft MS-DOS 5 Upgrade, Setup will replace
    the master boot record on the hard disk with code to display the
    message:

       The MS-DOS 5.0 Setup was not completed.
       Insert the UNINSTALL #1 diskette in drive A.
       Press the ENTER key to continue.

    This message should be erased and the master boot code rewritten
    before Setup is completed. If a problem occurs during Setup and you
    return to the previous MS-DOS, UNINSTAL should also remove this
    message. However, should Setup or UNINSTAL fail to remove this
    message, or should the master boot record become corrupted, a new
    master boot record can be written to the disk using the following
    command:

        C:\>fdisk /mbr

    Warning:  Writing the master boot record to the hard disk in this
    manner can make certain hard disks unusable.  IE: those partitioned
    with SpeedStor, or Microhouse's DrivePro program.  It can also cause
    problems for some dual-boot programs, or for disks with more than 4
    partitions.  Specific information is below.

    WARNINGS:

    This option should not be used if:

       - the disk was partitioned using Storage Dimensions' SpeedStor
         utility with its /Bootall option
       - the disk was partitioned using MicroHouse's DrivePro program AND
         the drive was NOT setup using a standard CMOS value.
       - more than 4 partitions exist
       - certain dual-boot programs are in use

    Storage Dimensions' SpeedStor utility using the /Bootall option
    redefines the drive's physical parameters (cylinder, head, sector).
    /BOOTALL stores information on how the drive has been changed in an
    area of the master boot record that MS-DOS does not use. FDISK /MBR
    will erase that information, making the disk unusable.

    MicroHouse's DrivePro program functions similarly to SpeedStor above, 
    and has the same boot record vulnerability.  MicroHouse identifies their
    boot program at boot-up by a small MICROHOUSE logo near the left side of
    the screen about two-thirds down, at power on.  If you see this logo, 
    do NOT use FDISK /MBR, or the drive will become unusable.

    Some older OEM versions of MS-DOS and some third-party partitioning
    utilities can create more than 4 partitions.  Additional partition
    information is commonly stored information on partitions in an area
    that FDISK /MBR will overwrite.

    Some dual-boot programs have a special MBR that asks the user which
    operating system they want on bootup.  FDISK /MBR erases this program.
    Dual-boot systems that boot whichever partition is marked Active are
    not affected by FDISK /MBR.

                              Edited: MicroSoft Publication
                              forwarded by Don Dean
                              editing suggestions made by
                              Matt Mc_Carthy (info re:
                              MicroHouse's DrivePro)