@echo off

rem                         FAT32 HARD DISK
rem                         ===============

rem             Hard Disk Structures: Backup and Repair
rem             =======================================


rem  Routines to Save & Restore -
rem  
rem  1. Track 0: MBR sector (BPB, IPL & Partition Table)
rem  2. Primary Partition:  Boot sector, FS Info sector, FAT 1 & 2, Root Directory
rem  3. Extended Partition: EMBR (Partition Table)
rem  4. Logical Partitions: Boot sector, FS Info sector, FAT 1 & 2, Root Directory
rem  
rem  This set of Data Recovery routines is for a FAT32 WinME system
rem  booted from a WinME Emergency Boot Disk, but should also work
rem  for a Win98SE system booted from a Win98SE Boot Disk

rem  *** Set Path ***
SET DOSpath=%path%
PATH ;
SET PATH=F:\SAVED\RECOVERY;F:\SAVED\RECOVERY\DOS\COMMAND
SET PATH=%path%;F:\SAVED\RECOVERY\DOS\UTILS;F:\SAVED\RECOVERY\DOS\HDD_FIX

rem  *** Disk Cache for MS-DOS Mode ***
rem  * To make the routines run faster *
SMARTDRV 8192 16>nul
rem  * Alternate file locations *
:: C:\WINDOWS\SMARTDRV.EXE 8192 16>nul
:: F:\SAVED\RECOVERY\CONFIG\SMARTDRV.EXE 8192 16>nul

rem  *** To backup the Rescue Utils ***
:: XXCOPY "F:\SAVED\RECOVERY\" "E:\SAVED\RECOVERY\" /H/KS/E/TTA0/TCA/TCC/TCW/ZE


::  //  ::


rem                    --------------------------
rem                    SECTION A: DISK STRUCTURES
rem                    --------------------------


rem                       DISK STRUCTURE NOTES
rem                       ====================


rem  FAT32
rem  =====
rem  
rem  The FAT32 file system is a method for storing files on the
rem  magnetic hard disk in a computer. The disk may contain a
rem  single partition, or may be divided into several partitions.
rem  
rem  A partition larger than 8GB *must* use the FAT32 file system,
rem  in order to provide enough addresses for file storeage on that
rem  partition; and a partition smaller than that *may* use it.
rem  
rem  FAT32 uses 32 bits for each entry in the File Allocation Table
rem  (i.e. 4 bytes, as there are 8 bits in a byte: 4 x 8 = 32), so
rem  providing more addresses than FAT16 (which uses only 16 bits).
rem  
rem  NB: In some disk utility programs, FAT32 is called "BigFAT"
rem      and FAT16 is called "FAT".
rem  
rem  NB: The notes in this file are for the FAT32 file system only,
rem      on a computer running Windows ME or Windows 98/98SE.
rem  
rem      Those Windows versions can <u>not</u> access an NTFS partition.
rem  
rem      This section does NOT describe a system that dual-boots
rem      (shares a partition with more than one Operating System),
rem      nor does it describe a disk that is larger than 127.53GB.


rem  CHS ADDRESSING
rem  ==============
rem  
rem  CHS = Cylinder : Head : Sector
rem  
rem  Each sector (consisting of 512 bytes) has a CHS address.
rem  
rem  A FAT32 disk starts at Cylinder 0, Head 0, Sector 1
rem  (CHS 0-0-1), and is typically structured as follows -
rem  
rem  Sector   :  There are 63 sectors per head
rem              (counted from 1 to 63)
rem  
rem  Head     :  There are 255 heads per cylinder
rem              (counted from 0 to 254)
rem  
rem  Cylinder :  The maximum number of Cylinders is 1024
rem              (counted from 0 to 1023; i.e. 1023 is
rem              the largest value in a Partition Table)
rem  
rem              NB: The maximum number will be *less* than
rem                  1023 if the disk is smaller than 8GB
rem  
rem              NB: If the disk is larger than 8GB, the
rem                  number 1024 is used: meaning use LBA
rem                  values (sectors only) instead of CHS
rem  
rem  Where the disk is larger than 8GB, Logical Block Addressing
rem  (LBA) is used for all critical disk functions instead of CHS,
rem  but some key disk structures nonetheless contain CHS values


rem  LOGICAL BLOCK ADDRESSING (LBA)
rem  ==============================
rem  
rem  An LBA sector is the same as a CHS sector: a 512 byte block
rem  of data.
rem  
rem  CHS cannot provide sufficient addresses for a disk exceeding
rem  8GB, so LBA addressing must be used instead. LBA uses sectors
rem  only, treating the disk as a single unbroken chain of them.
rem  
rem  NB: LBA is an *alternative* to C-H-S addressing, giving only
rem      a sector number (instead of the traditional three numbers:
rem      Cylinder, Head and Sector).
rem  
rem  NB: In LBA the sectors begin with sector 0, whereas CHS values
rem      begin with sector 1; thus their sector numbering is always
rem      out-of-step with each other by 1.
rem  
rem  
rem  Formula to convert a CHS value into an LBA value:
rem  
rem    (Cylinders x Heads per Cylinder x Sectors per Head)
rem    + (Heads x Sectors per Head) + (Sectors - 1)
rem  
rem  This formula, in practice, is usually:
rem  
rem    (Cylinders x 255 x 63) + (Heads x 63) + (Sectors - 1)
rem  
rem  This formula is only of use if the disk is smaller than 8GB;
rem  a larger disk will have artificial (i.e. maximum) CHS values.
rem  
rem  This formula can, nevertheless, calculate the number of sectors
rem  on a disk from the CHS information printed on the disk's casing
rem  (since the disk label does not observe the rule that Cylinder
rem  values cannot exceed 1023, because this form of labelling is a
rem  convenient way to record the disk's "geometry" - see below).
rem  
rem  
rem  Convert using PT Calc:
rem  
rem  The program PTCALC.EXE (and PT Calc for Windows) can translate
rem  CHS values to LBA, and vice versa ("PARTITION TABLE EDITOR", below).
rem  
rem  
rem  Sanity Check of Partition Table:
rem  
rem  In the MBR Partition Table, the starting sector and ending sector
rem  of each partition is described by a CHS value. These should agree
rem  with the LBA values for "start sector" and "number of sectors",
rem  even though those LBA values are enough to define the partition.
rem  
rem  NB: If the partition ends beyond the 8GB boundary, the CHS value
rem      for the ending sector will be merely the maximum permitted
rem      (typically 1024-254-63). A Cylinder value of 1024 is a special
rem      value, indicating that LBA values are in use instead of CHS.
rem  
rem  The LBA start sector is stored directly in the Partition Table.
rem  To calculate the LBA end sector: add "start sector" to "number
rem  of sectors", then subtract 1.


rem  DISK GEOMETRY
rem  =============
rem  
rem  The Disk Geometry will usually be 255 Heads per cylinder and
rem  63 Sectors per head (255 x 63 = 16,065 sectors per Cylinder);
rem  but don't just assume that, as other values are sometimes used.
rem  
rem  NB: Disk Geometry (the number of Cylinders - Heads - Sectors)
rem      can be read from the BIOS. It is also printed on a label
rem      on the Hard Disk's casing.
rem  
rem      To enter the BIOS, press the appropriate key (e.g. DEL)
rem      (or, on some systems, F1 or F2) repeatedly at startup.
rem  
rem  A sector is a real disk structure: a block of 512 bytes. But the
rem  terms 'Head' and 'Cylinder' are now mere conventionalisations;
rem  they are no longer related to the actual engineering structures.
rem  
rem  In a disk larger than 8GB all CHS values are unreal: CHS cannot
rem  address a disk larger than 8GB. But CHS values must be used in
rem  key disk structures, to ensure compatibility with the BIOS. So
rem  the CHS values used are typically the largest allowable values,
rem  i.e. 1023-254-63 or 1024-254-63 (or sometimes 512-254-63).
rem  
rem  NB: The CHS values are in what is known as "L-CHS" format,
rem      as they are CHS values that have been modified by LBA.
rem  
rem  The disk manufacturer will still typically label the disk with
rem  CHS values, but the values given are unreal. An 80GB hard disk
rem  will typically be labelled CHS 9729-254-63, but it does not have
rem  9,729 cylinders within it, nor can a CHS value greater than 1024
rem  be used in the disk's Partition Tables: that CHS value is merely
rem  a literal translation of the number of sectors on the disk.
rem  
rem  CHS values remain important because key BIOS functions are based
rem  on the Disk Geometry, by which is meant the CHS values: the
rem  number of Cylinders, Heads per cylinder, and Sectors per head.
rem  
rem  NB: The CHS value printed on the disk's casing, although unreal,
rem      is a convenient means of telling the user the Head and Sector
rem      values, which remain important (even though the figure given
rem      for the number of Cylinders is irrelevent, except for the key
rem      fact that the value *exceeds* 1,023).
rem  
rem  If you are unsure what the correct disk geometry is, try using the
rem  following values in the Partition Table, as one of these values is
rem  likely to be the correct one:
rem  
rem  (a) Sectors per Head: The most likely value is 63 (as almost all
rem      hard disks base their CHS values on this traditional number)
rem  
rem  (b) Heads per Cylinder: Try 255, 16, 32, 64, 128 and 240
rem      (in that order).
rem  
rem      NB: The number FF in Hexadecimal (base 16) represents
rem          255 in Decimal (base 10); thus 255 is the maximum
rem          decimal number that a 2-byte hex value can store.
rem  
rem          (Being the maximum value possible, 255 is the value
rem           most likely to be the correct one on a normal disk)
rem  
rem          The equivalent LBA sector number will be 1 less than
rem          the actual number (as LBA numbers start from 0 rather
rem          than 1). So the maximum LBA value in a Partition Table
rem          entry is 254 (i.e. 255 - 1 = 254).
rem  
rem      NB: Computers use Binary storage, so *any* factor of two
rem          that can be stored in a 2-byte hex value can be valid
rem          (i.e. 4, 8, 16, 32, 64, or 128).


rem  DISK SIZE
rem  =========
rem  
rem  Disk Size in Megabytes -
rem  
rem  To calculate the size of a hard disk from its C-H-S values:
rem  
rem    (Cylinders x Heads per Cylinder x Sectors per Head)
rem     / 2,048 = MegaBytes
rem  
rem  To calculate the size of a disk from its LBA value:
rem  
rem    (LBA Sectors + 1) / 2,048 = MegaBytes
rem  
rem  
rem  Notes:
rem  
rem  1. The LBA figure will be slightly greater, as the LBA calculation
rem  gives the true number of sectors on the disk. The CHS calculation
rem  only counts the number of sectors included in all the partitions;
rem  a few sectors are left unused, as partitioning rules demand that a
rem  partition MUST end on a Cylinder boundary (1 Cyl = 16,065 sectors).
rem  
rem  2. To calculate the size of a Partition from its CHKDSK.EXE value:
rem  
rem       Kilobytes / 1,024 = MegaBytes
rem  
rem       NB: Even if the hard disk has only a *single* partition,
rem           this is NOT the size of the disk. It doesn't include
rem           the System Area (Track 0, Boot Sector, FAT x2, etc).
rem  
rem  3. To convert from MegaBytes to Bytes:
rem  
rem       1 MB = 512 x 2,048 (i.e. 2,048 sectors) = 1,048,576 bytes
rem  
rem       MegaBytes x 1,048,576 = Bytes
rem       Bytes / 1,048,576 = MegaBytes
rem  
rem  
rem  Disk Size limitations -
rem  
rem  In Windows 95 and 98, because the versions of SCANDISK and DEFRAG
rem  included with the Operating System are 16-bit applications, the FAT
rem  structure is unable to exceed approximately 4.2 million clusters,
rem  imposing a partition size limit of 127.53 GB.
rem  
rem  NB: ScanDisk for Win98 is a 16-bit program. Such programs have a
rem      memory block maximum allocation size of 64 KB less than 16 MB,
rem      so cannot process a FAT32 partition if the FAT is larger than
rem      16 MB less 64 KB. As the File Allocation Table in FAT32 uses
rem      4 bytes, ScanDisk cannot process a FAT that defines more than
rem      4,177,920 clusters (including the two reserved clusters). So,
rem      including the FATs themselves, this works out at maximums of
rem      32KB per cluster and 127.53 GB per partition.
rem  
rem  NB: The versions of SCANDISK and DEFRAG in Windows ME do NOT have this
rem      limitation (and can be used with Windows 98/98SE also). As true
rem      32-bit applications, they function on a partition of up to 512 GB.
rem  
rem  Windows 9x and Windows ME do not support 48-bit LBA, so the maximum
rem  possible size of a partition is 127.53 GB (i.e. the largest partition
rem  size that's possible using 28-bit LBA).
rem  
rem  NB: The WinME driver ESDI_506.PDR (which Windows uses for 32-bit drive
rem      access) uses 28-bit LBA, so cannot access a partition larger than
rem      127.53 GB.
rem  
rem  A disk exceeding 127.53 GB can be partitioned as several partitions,
rem  each *smaller* than 127.53 GB; then Win98/ME can access each.
rem  
rem  NB: But *only* if the BIOS can recognise a disk exceeding 137 GB. If
rem      the motherboard, i.e. the motherboard's ROM-BIOS chip, does not
rem      support 48-bit LBA, it can't recognise a disk exceeding 137 GB!
rem  
rem      An IDE or SATA disk can be attached to a PCI controller card that
rem      supports 48-bit LBA. This enables a disk larger than 137 GB to be
rem      present, even where the motherboard BIOS uses 28-bit LBA.


rem  CLUSTER SIZE
rem  ============
rem  
rem  On a FAT32 partition, the default cluster size is:
rem  
rem  Partition size    Cluster size
rem  --------------    ------------
rem    0 to  8 GB           4K
rem    8 to 16 GB           8K
rem   16 to 32 GB          16K
rem   Over  32 GB          32K
rem  
rem  1 sector is 0.5K, so if a partition has a cluster size of 16K
rem  each cluster contains 32 sectors; but if cluster size is 32K,
rem  then each cluster contains 64 sectors.
rem  
rem  NB: These are the *default* values; but the user can override
rem      them in the initial partitioning and formatting of the disk.
rem      These values are thus only a guide, and will NOT be correct
rem      in all cases.
rem  
rem  The *maximum* number of Clusters in a partition:
rem  
rem  ( (No. of Sectors in Partition) - (No. of Sectors per FAT x 2) -
rem  (No. of Reserved Sectors) ) / (No. of Sectors per Cluster)
rem  
rem  If there is any remainder in the result from that formula, it just
rem  means there are a few unused sectors at the end of the partition
rem  (usually not enough to make another cluster).
rem  
rem  NB: The number of clusters can tell you the type of FAT in use, as
rem      a FAT16 partition cannot exceed 65,517 clusters. If the number
rem      of clusters is greater than 65,518 the partition is using FAT32.
rem      (Note: FAT16 has a maximum cluster size of 32K [32,768 bytes])
rem  
rem  NB: The ONLY method used by WinME to determin a partition's FAT type
rem      is the value stored in the MBR for the total number of Clusters!
rem  
rem      It does NOT use the size of the partition. Cluster size, which
rem      is user-selectable, determines the number of clusters on disk,
rem      and thus the FAT type; so partition size is an unsafe guide!
rem  
rem      It does NOT use the ID string in the partition's Boot Sector,
rem      e.g. "FAT16" or "FAT32", which has no significance whatever.
rem  
rem  NB: The number of Clusters in a partition can be ascertained by
rem      running CHKDSK.EXE which reports:
rem        (a) The total number of clusters in the partition
rem            (describing them as "allocation units"), and
rem        (b) The number of bytes in each cluster.
rem  
rem      *** Run CHKDSK.EXE ***
::       CHKDSK C: > F:\SAVED\CHKDSK_C.txt
::       CHKDSK D: > F:\SAVED\CHKDSK_D.txt
::       CHKDSK E: > F:\SAVED\CHKDSK_E.txt
rem  
rem  
rem  Minimum number of Clusters:
rem  
rem  A FAT32 partition MUST contain at least 65,527 clusters (because if it
rem  contains fewer, Windows will treat the partition as FAT16). Therefore
rem  the maximum cluster size possible is 32KB; a larger cluster size
rem  (i.e. 64KB) would make it possible to have less than 65,527 clusters.
rem  
rem  
rem  Maximum number of Clusters:
rem  
rem  FAT32 permits the maximum number of Clusters to be several million,
rem  by using 32-bit values in the File Allocation Table to store the
rem  cluster addresses. However, the maximum number of addresses is only
rem  0FFFFFFF hex (a 28-bit value), not the full 32-bit value FFFFFFFF hex.
rem  
rem  This is to enable programs that manipulate the File Allocation Table
rem  to use four bits as tags in their internal data structures; but it
rem  has NO impact on the theoretical maximum FAT32 volume size, as that is
rem  capped by the FFFFFFFF (hex) maximum sector count: which, at 512 bytes
rem  per sector, results in a theoretical maximum volume size of 2 TeraBytes.
rem  
rem  
rem  Cluster No.2 -
rem  
rem  The "Data Area" starts with cluster number 2, not cluster zero,
rem  because there are two "reserved clusters" (numbers 0 and 1).
rem  
rem  Cluster 2 is the first sector occupied by the Root Directory Table
rem  (i.e. the first sector used for the storage of data); and Norton's
rem  DiskEdit identifies it as cluster 2. [Note: Cluster numbers are ONLY
rem  assigned to the Data Area of the partition, NOT to the "system area"]
rem  
rem  NB: To calculate the LBA location of the 1st sector occupied by
rem      the Root Directory Table, see below under "ROOT DIRECTORY".
rem  
rem  The first sector containing an actual file is thus the first sector
rem  in cluster 3 (bearing in mind that LBA counts from 0, not 1):
rem  
rem  1st sector of Root Dir Table (LBA) +  No. of Sectors per Cluster
rem  
rem  NB: This is because the Root Directory Table usually occupies
rem      1 cluster (i.e. 32 sectors if the partition's cluster size
rem      is 16k, or 64 sectors if the partition uses 32k clusters).
rem  
rem  NB: Cluster 3 is typically occupied by the Directory Table
rem      for the directory RECYCLED (a hidden system directory).
rem  
rem  
rem  Examples:
rem  
rem  If cluster size is 16k, cluster 3 starts (in LBA sectors) at:
rem   (1st sector of Root Directory Table) + 32
rem  
rem  If cluster size is 32k, cluster 3 starts (in LBA sectors) at:
rem   (1st sector of Root Directory Table) + 64
rem  
rem  
rem  Clusters used by a File -
rem  
rem  Norton's DiskEdit can read from the FAT the cluster numbers used
rem  by a file, if the FAT is undamaged (see below: "FILE CLUSTERS").


rem  FAT RANGES
rem  ==========
rem  
rem  The following are the ranges for partition size, which overlap:
rem  
rem    Type    Min Partition Size             Max Partition Size
rem    -----   ------------------   -------------------------------------
rem    FAT12         1.5 KB            32 MB        (   33,472,512 bytes)
rem    FAT16          16 MB         2,047 MB (2 GB) (2,147,123,200 bytes)
rem    FAT32         ~32 MB         2,000 GB (2 TB) (   about 2^40 bytes)
rem  
rem  
rem  Practical Limits:
rem  
rem  The above partition sizes are the *theoretical* limits, but
rem  the following practical restrictions also apply -
rem  
rem  1. Although FAT16 cannot be used for a partition larger than 2GB,
rem     a disk of up to 4GB can have several FAT16 partitions on it,
rem     each not exceeding 2GB.
rem  
rem  2. Large Disk Support (FAT32) is NOT available on disks smaller
rem     than 510MB. A FAT32 partition smaller than 510MB can only exist
rem     as one of several partitions on a hard disk larger than that.
rem  
rem  3. Windows 98/ME cannot address a FAT32 partition exceeding 137GB,
rem     and Windows XP cannot create a FAT32 partition exceeding 32GB;
rem     so in practice those are upper limits for a FAT32 partition.
rem  
rem     NB: For various reasons, in practice the largest partition size
rem         that can exist on a Windows 98/ME system is 127.53 GB.
rem  
rem  
rem  Notes:
rem  
rem  16-bit FAT (i.e. FAT16) is commonly referred to simply as FAT
rem  by many disk tools (including FDISK.EXE and FORMAT.COM), and
rem  in documentation and Help files accompanying those programs.
rem  
rem  32-bit FAT (i.e. FAT32) is sometimes referred to as "BigFAT"
rem  by disk tools, and in documentation and Help files.
rem  
rem  See also: http://en.wikipedia.org/wiki/File_Allocation_Table


rem  PARTITIONS
rem  ==========
rem  
rem  The disk space is sub-divided into one or more separate Partitions
rem  (usually called "Drives").
rem  
rem  The Partition Table in the MBR sector defines:
rem   - one Primary partition (of type 0C);
rem   - one Extended partition (of type 0F) if disk space remains.
rem  
rem  The Partition Table begining the Extended partition defines:
rem   - one Logical partition (of type 0B), within the Extended partition;
rem   - one further partition (of type 05), containing a Logical partition,
rem     if the remaining disk space within the Extended partition permits.
rem  
rem  The Partition Table beginning a Type 05 partition defines:
rem   - one Logical partition (of type 0B), filling the Type 05 partition;
rem   - one further partition (of type 05), containing a Logical partition,
rem     if the remaining disk space within the Extended partition permits.
rem  
rem  NB: There can be up to 32 partitions in all, on a FAT32 disk,
rem      if the disk space within the Extended partition permits.
rem  
rem  
rem  In a WinME (or Win98/98SE) system using 32-bit FAT -
rem  
rem  1. The Primary DOS partition will normally be type 0C (i.e. the
rem     the 1st entry in the MBR's partition table will be type 0C).
rem  
rem  2. The Extended partition, in which the Logical partitions
rem     are stored, will normally be type 0F (i.e. the 2nd entry
rem     in the MBR's partition table will normally be type 0F).
rem  
rem     NB: If the Extended partition ends at cylinder 1024 or later
rem         (i.e. the hard disk exceeds 8GB), the Extended partition
rem         *must* be type 0F. If it is not, data damage will occur.
rem  
rem  3. Each Logical partition (INCLUDING the first) will normally be
rem     type 0B (i.e. the 1st entry in each E-MBR partition table, with
rem     which the Logical partition begins, will normally be type 0B).
rem  
rem     NB: Each partition table sector (other than the MBR sector
rem         at CHS 0-0-1) is called an Extended MBR (E-MBR) sector,
rem         because it's part of the Extended partition.
rem  
rem  4. Each Logical partition (EXCEPT the first), although part
rem     of the Extended partition, will *also* be in an individual
rem     partition of its own, of type 05 (i.e. the 2nd entry, if any,
rem     in each E-MBR partition table will normally be type 05).
rem  
rem  If a partition table (in the MBR or any E-MBR sector) does NOT
rem  specify the normal partition type expected, check carefully to
rem  establish why! An abnormal partition type may cause data damage.


rem  PARTITION TYPES
rem  ===============
rem  
rem  ID types in Partition Tables -
rem  
rem  FAT32 typically uses four main partition types: 05, 0B, 0C and 0F
rem  (these are numerical values, expressed in hex: i.e. hexadecimal).
rem  
rem  NB: The procedures set out in this page are ONLY safe to use with
rem      a hard disk that has those partition types AND NO OTHER.
rem  
rem  0C = FAT32 Primary DOS Partition, ending at cylinder 1024 or later
rem       Type: FAT32X (Type 0B with Interrupt-13 extensions)
rem       (i.e. FAT32 with LBA) ("Win95 FAT32 (LBA)") (Entry No.1 in MBR)
rem       (NB: The normal type of FAT32 for a Primary partition larger
rem        than 8GB; i.e. where the 1024 cylinder limit is exceeded)
rem  
rem       Note: If the disk is bootable and contains only one partition,
rem             that will be a Primary DOS Partition (i.e. type 0C).
rem  
rem  0F = FAT32 Extended Partition, ending at cylinder 1024 or later
rem       Type: Extended X (Type 05 with Interrupt-13 extensions)
rem       (i.e. FAT32 with LBA) ("Win95 Extended") (Entry No.2 in the MBR)
rem       (NB: The normal type of FAT32 for an Extended partition on a disk
rem        larger than 8GB, i.e. where the 1024 cylinder limit is exceeded)
rem  
rem       NB: This is a container of partitions (not a container of data),
rem           as indicated by its being labelled an "Extended" partition.
rem  
rem       Note: If there is more than one partition, an Extended partition
rem             (i.e. type 0F) contains all of them except the first one.
rem  
rem       Note: The 2nd partition will be a Logical partition (i.e. type 0B);
rem             as will any further partitions (e.g. the 3rd, 4th, etc).
rem  
rem       Note: If there are only two partitions on the disk, the 2nd partition
rem             will normally completely fill the Extended partition. If the disk
rem             has three or more partitions, each Logical partition will occupy
rem             PART of the Extended partition, but *without* any overlapping.
rem  
rem  0B = FAT32 Partition ("Win95 FAT32") (NB: Originated in Windows 95)
rem       (Entry No.1 in an E-MBR)
rem       (NB: All Logical partitions on a FAT32 disk are type 0B)
rem  
rem       Note: If a FAT32 disk contains more than one partition, the
rem             2nd partition (i.e. the 1st Logical partition), and any
rem             subsequent partition(s), will each be type 0B.
rem  
rem  05 = MS-DOS Extended Partition
rem       (Entry No.2 in an E-MBR)
rem       (NB: On a FAT32 disk a *second* or subsequent Logical partition
rem        is contained in - and entirely fills - a partition of type 05)
rem  
rem       NB: This is a container of partitions (not a container of data),
rem           as indicated by its being labelled an "Extended" partition.
rem  
rem       Note: If there are MORE than two partitions on the disk, the
rem             3rd partition (i.e. the 2nd Logical partition), and any
rem             subsequent one, each completely fills one type 05 partition.
rem  
rem  
rem  Hidden Partitions:
rem  
rem  1B = Hidden FAT32 0B Partition
rem  1C = Hidden FAT32 0C Partition (e.g. hidden IBM rescue partition)
rem  
rem  A hidden partition type starts with a 1, and an unhidden type
rem  starts with a 0. To hide a partition, change leading 0 to 1.
rem  For example: Type 0B is FAT32, and type 1B is Hidden FAT32.
rem  
rem  
rem  Warning for Windows 95:
rem  
rem  Types 0E and 0F can cause data loss in Win95 (but not in Win98 or
rem  WinME), if you exit from Windows to MS-DOS mode WITHOUT rebooting
rem  (although *only* if the Disk has more than one partition).
rem  
rem  This fault can be cured by installing the updated Windows 95 file
rem  DISKTSD.VXD v4.00.952 (dated 3/22/96), or any later version.
rem  
rem  
rem  Note on FAT16:
rem  
rem  If the partition type is 06 the partition is using FAT16. This also
rem  means that the partition size cannot be larger than 2GB.
rem  
rem  NB: A FAT16 disk cannot safely be repaired using any procedure set out
rem      here; there are crucial differences from FAT32 in the MBR, in the
rem      Partition Table, in the Boot Sector, in the Boot Record, in the
rem      File Allocation Table structure, and in the Root Directory table.


rem  PARTITIONING RULES
rem  ==================
rem  
rem  Partitioning rules demand that a partition MUST end on a
rem  Cylinder boundary (1 Cylinder = 255 x 63 = 16,065 sectors);
rem  i.e. every partition *must* be a multiple of 16,065 sectors.
rem  
rem  NB: This is a FUNDAMENTAL requirement. Data damage is a
rem      certainty if this rule is breached!
rem  
rem  NB: This ONLY applies to the Primary DOS partition and the
rem      Extended Partition, *not* to Logical partitions within
rem      the Extended Partition. But the 1st Logical partition
rem      will also obey this if it's the ONLY Logical partition
rem      and it occupies ALL the space in the Extended partition.
rem  
rem  Partitions are thus "cylinder aligned": they invariably start
rem  and end on a cylinder boundary (even though a Cylinder is now
rem  only a logical, rather than a physical, disk structure).
rem  
rem  NB: For tools to convert LBA values to CHS, and vice versa,
rem      see below under PTCALC.EXE and "CONVERSION CALCULATIONS"
rem  
rem  Therefore many partitions begin with the CHS address xxxx-0-1
rem  (i.e. the first sector of a cylinder), and will end with the
rem  CHS address xxxx-254-63 (i.e. the final sector of a cylinder).
rem  
rem  NB: The Partition Table will therefore be at CHS xxxx-0-1
rem      and the Boot Sector will therefore be at CHS xxxx-1-1
rem  
rem  Although Logical partitions (other than the 1st Logical partition)
rem  can begin part-way through a Cylinder, they nevertheless will NOT
rem  begin part-way through a Head; they always start at CHS xxxx-x-1.


rem  PARTITION STRUCTURE
rem  ===================
rem  
rem  It may help in understanding disk structure to think of
rem  a partition as starting with a Partition Table, followed
rem  63 sectors later (i.e. 1 Head later) by a Boot Sector.
rem  
rem  NB: Technically, though, the Partition Table *defines*
rem      the Partition (as begining with the Boot Sector),
rem      and is NOT treated as being part of the Partition.
rem  
rem      The Boot Sector defines the 63 sectors containing the
rem      Partition Table as "hidden sectors", and they are NOT
rem      counted as part of the Partition by any disk tool.
rem  
rem  
rem  Examples:
rem  
rem  In the case of the Primary DOS partition, the Partition Table
rem  is in the MBR sector, at CHS 0-0-1; and the Boot Sector is in
rem  CHS 0-1-1 (i.e. 63 sectors later).
rem  
rem  In the case of Logical Partitions, the relationship is clearer:
rem  the 1st Logical partition is defined in the MBR as *beginning*
rem  with its Partition Table sector (the MBR points to that sector).
rem  
rem  NB: Technically, the MBR is defining the Extended partition, by
rem      pointing to the first sector of it (which happens to contain
rem      the Partition Table for the 1st Logical partition).
rem  
rem      As with the Primary partition, the 63 sectors containing
rem      the Partition Table are defined as NOT being a part of the
rem      1st Logical partition and are treated as "hidden sectors".
rem  
rem  
rem  Note on Partition Reconstruction:
rem  
rem  The Boot Sector usually contains all the necessary information
rem  (see below) to undelete the partition that it belongs to.
rem  
rem  Every partition begins with a Boot Sector, immediately preceeded
rem  by 1 Head (typically 63 sectors) containing a Partition Table.
rem  
rem  Thus a partition ends immediately before a sector that contains
rem  ONLY another Partition Table (not any boot code, because Logical
rem  partitions are not bootable). The sector will be entirely BLANK
rem  (i.e. filled with zeros), except for a 12 byte Partition Table.
rem  
rem  NB: A Logical partition *can* be bootable, but only in special
rem      circumstances not usually encountered (see below).
rem  
rem  To be valid, a Partition Table usually must be on a cylinder boundary
rem  (but see above, under "PARTITIONING RULES"). (NB: If it is not,
rem  it is probably a backup copy, created by a disk recovery tool)


rem  NON-DOS PARTITION
rem  =================
rem  
rem  The first 63 sectors on the Disk (CHS 0-0-1 to 0-0-63). For
rem  historical reasons, sometimes called "Track 0".
rem  
rem  NB: Although called the "Non-DOS Partition" this is NOT truly
rem      a partition at all, as it does not contain any user data.
rem      (As disks were once so small that they usually had only a
rem       single DOS partition, the name "Non-DOS Partition" arose)
rem  
rem  It starts at sector 1 (CHS 0-0-1) (LBA 0) and ends at sector 63
rem  (CHS 0-0-63) (LBA 62); a hidden 63 sectors at the start of the
rem  disk. It contains the Partition Table for the *entire* Disk.
rem  
rem  NB: The LBA sector numbering starts at 0, whereas CHS sector
rem      numbering starts at 1; hence there is a discrepancy of 1.
rem  
rem  Sector 1 (CHS 0-0-1), the Master Boot Record (MBR), contains:
rem  the Initial Program Loader (IPL) code, BIOS Parameter Block (BPB),
rem  and the Partition Table.
rem  
rem  All other sectors are usually blank; but special backup software
rem  sometimes stores recovery data in the 62 empty sectors, so it is
rem  prudent to make a backup copy of ALL the 63 sectors of Track 0.
rem  
rem  On the ST380011A Disk:
rem  (a) Sector CHS 0-0-3 contains recovery data.
rem  (b) Sector CHS 0-0-9 contains a backup copy of the MBR sector
rem      (from CHS 0-0-1), starting with the marker "90 E9 7D".
rem  
rem  On the M02GB2 (18GB) Disk:
rem  (a) Sector CHS 0-0-62 (at 7A00 hex) contains recovery data.
rem  (b) Sector CHS 0-0-63 (at 7C00 hex) contains recovery data.
rem  
rem  The name "Non-DOS partition", used for historical reasons, is
rem  misleading. This is NOT a partition: it contains NO user data.
rem  It's actually an essential part of ALL the partitions on the
rem  disk, because it contains the Master Partition Table.
rem  
rem  
rem  Master Boot Record (MBR) -
rem  
rem  The Master Boot Record is located in the first physical sector of
rem  the disk. It contains some executable code and the Partition Table.
rem  
rem  The executable code is loaded into RAM at boot time and executed.
rem  Its role is to determine which partition is the bootable one,
rem  and then to load and execute the code in the Boot Sector of that
rem  partition (which in turn loads the Operating System, i.e. Windows).
rem  
rem  FDISK's notorious /MBR command recreates the executable code in
rem  the Master Boot Record (but on Disk 0 only).
rem  
rem  NB: That command will be HARMFUL if any drive overlay software is
rem      installed (e.g. OnTrack Disk Manager), to handle large disks,
rem      something that is required only on a disk larger than 127.53 GB.
rem      The loader code in the MBR on such a disk is not standard code;
rem      the command will destroy the special loader code, so the disk
rem      will no longer be accessible. (The Partition Table information
rem      is also *not* the same on such a disk as it would be on a disk
rem      that does not have drive overlay software.)
rem  
rem  NB: That command will also be HARMFUL if -
rem      (a) the Hard Disk has more than four partitions, or
rem      (b) the Hard Disk has dual-boot capability installed, or
rem      (c) the Hard Disk was originally partitioned using a SpeedStor
rem          utility from Storage Dimensions, with the /BOOTALL option.
rem  
rem  
rem  Structure of MBR Sector:
rem  
rem  Offset     Nature                      Size
rem  --------   -------------------------   ---------
rem   00(hex)   Executable code             446 bytes
rem  1BE(hex)   1st partition table entry    16 bytes
rem  1CE(hex)   2nd partition table entry    16 bytes
rem  1DE(hex)   3rd partition table entry    16 bytes
rem  1EE(hex)   4th partition table entry    16 bytes
rem  1FE(hex)   Executable marker (55 AA)     2 bytes
rem  
rem  
rem  Executable Code:
rem  
rem  On a FAT32 hard disk, formatted by Windows 98/98SE/ME, the first 446 bytes
rem  of the MBR Sector normally look like this (in Hex and ASCII):
rem  
::   <------------------- Hexadecimal -------------------->    <--- ASCII ---->
::          00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F    0123456789ABCDEF
::   ---------------------------------------------------------------------------
::   0000:  33 C0 8E D0 BC 00 7C FB-50 07 50 1F FC BE 1B 7C  [ 3��м |�P P �� | ]
::   0010:  BF 1B 06 50 57 B9 E5 01-F3 A4 CB BE BE 07 B1 04  [ �  PW�� �˾� �  ]
::   0020:  38 2C 7C 09 75 15 83 C6-10 E2 F5 CD 18 8B 14 8B  [ 8,| u �� ��� � � ]
::   0030:  EE 83 C6 10 49 74 16 38-2C 74 F6 BE 10 07 4E AC  [ �� It 8,t��  N� ]
::   0040:  3C 00 74 FA BB 07 00 B4-0E CD 10 EB F2 89 46 25  [ < t��  � � ��F% ]
::   0050:  96 8A 46 04 B4 06 3C 0E-74 11 B4 0B 3C 0C 74 05  [ -�F � < t � < t  ]
::   0060:  3A C4 75 2B 40 C6 46 25-06 75 24 BB AA 55 50 B4  [ :�u+@�F% u$��UP� ]
::   0070:  41 CD 13 58 72 16 81 FB-55 AA 75 10 F6 C1 01 74  [ A� Xr ��U�u �� t ]
::   0080:  0B 8A E0 88 56 24 C7 06-A1 06 EB 1E 88 66 04 BF  [  ���V$� � � �f � ]
::   0090:  0A 00 B8 01 02 8B DC 33-C9 83 FF 05 7F 03 8B 4E  [   �  ��3Ƀ�  �N ]
::   00A0:  25 03 4E 02 CD 13 72 29-BE 46 07 81 3E FE 7D 55  [ % N � r)�F �>�}U ]
::   00B0:  AA 74 5A 83 EF 05 7F DA-85 F6 75 83 BE 27 07 EB  [ �tZ�� څ�u��' � ]
::   00C0:  8A 98 91 52 99 03 46 08-13 56 0A E8 12 00 5A EB  [ ���R� F  V �  Z� ]
::   00D0:  D5 4F 74 E4 33 C0 CD 13-EB B8 00 00 00 00 00 00  [ �Ot�3�� �       ]
::   00E0:  56 33 F6 56 56 52 50 06-53 51 BE 10 00 56 8B F4  [ V3�VVRP SQ�  V�� ]
::   00F0:  50 52 B8 00 42 8A 56 24-CD 13 5A 58 8D 64 10 72  [ PR� B�V$� ZX�d r ]
::   0100:  0A 40 75 01 42 80 C7 02-E2 F7 F8 5E C3 EB 74 49  [  @u B�� ���^��tI ]
::   0110:  6E 76 61 6C 69 64 20 70-61 72 74 69 74 69 6F 6E  [ nvalid partition ]
::   0120:  20 74 61 62 6C 65 00 45-72 72 6F 72 20 6C 6F 61  [  table Error loa ]
::   0130:  64 69 6E 67 20 6F 70 65-72 61 74 69 6E 67 20 73  [ ding operating s ]
::   0140:  79 73 74 65 6D 00 4D 69-73 73 69 6E 67 20 6F 70  [ ystem Missing op ]
::   0150:  65 72 61 74 69 6E 67 20-73 79 73 74 65 6D 00 00  [ erating system   ]
::   0160:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00  [                  ]
::   0170:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00  [                  ]
::   0180:  00 00 00 8B FC 1E 57 8B-F5 CB 00 00 00 00 00 00  [    �� W���       ]
::   0190:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00  [                  ]
::   01A0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00  [                  ]
::   01B0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 ...    [                  ]
rem  
rem  Notes -
rem  1. Hexadecimal: Base 16 (0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F).
rem  2. ASCII: American Standard Code for Information Interchange
rem     (a set of 255 characters, including A to Z and 0 to 9).
rem  3. For each 2-digit hexadecimal number in the above table,
rem     you can identify its (hexadecimal) address in the sector
rem     by combining the row number (hex) in the left-hand margin
rem     with the column number (also in hex) across the top;
rem     e.g. the number in the 3rd column of the 3rd line is 7C
rem     and its address is 22 hex: 0020 (left column) + 02 (top).
rem  
rem  Examples: Copies of sector CHS 0-0-1 are set out below, saved by
rem  the program MBRSCAN.EXE from several FAT32 disks, as examples of
rem  the correct code for that sector (see "MBRSCAN RESULTS", below).
rem  
rem  
rem  CHS values in the MBR:
rem  
rem  If the disk is larger than 8GB, the only VALID numbers in the MBR
rem  are the LBA sector numbers (the numbers in the fields "sectors"
rem  and "sectors before"). The CHS values in the MBR are NOT correct
rem  as they stand: they are "L-CHS" values (see above); a conversion
rem  factor must be applied to them to calculate the *true* CHS values.
rem  
rem  
rem  Disk Serial Number:
rem  
rem  The six bytes DA to DF (bytes 219 to 224) in the MBR sector are
rem  a serial number, used by Windows to identify the different disks
rem  attached to the computer. [NB: In line 14, on a standard display]
rem  
rem  If two hard disks have the same serial number, a fault will occur
rem  during bootup (because, in effect, both have the same "address").
rem  
rem  The fault can be prevented, or repaired, by manually zeroing these
rem  six bytes (a.k.a. the "mystery bytes") on either disk. This forces
rem  Windows to allocate a new serial number to the disk, on the next
rem  bootup, thereby preventing a clash of disk addresses.
rem  
rem  NB: This serial number must NOT be confused with -
rem
rem      (a) the hardware serial number, set by the disk's manufacturer
rem          (a.k.a. the "physical serial number"), on the disk's label;
rem  
rem      (b) the serial number that Windows allocates to each Partition
rem          (the Volume Serial Number), to allow it to differentiate
rem          between the different partitions [readable with CHKDSK.EXE].
rem  
rem  
rem  This fault may cause the following errors:-
rem  
rem  1. Windows may refuse to start.
rem  
rem     Restart in DOS, and use a Disk Editor (below) to set the six
rem     bytes to 00 (zero hex), on either disk.
rem  
rem  2. Windows may WIPE the system registry.
rem  
rem     The registry can be *restored* in DOS from the backups in
rem     C:\WINDOWS\SYSBCKUP by using the following commands (and
rem     then carrying out the on-screen instructions):
rem  
::      SET PATH=%path%;C:\WINDOWS\COMMAND
::      SCANREG /RESTORE
rem  
rem  3. Windows may change the Volume Identifier on the affected disk,
rem     setting it as non-bootable. If it's subsequently installed as
rem     the Primary Master, the computer will not boot.
rem  
rem     Use PowerQuest's Partition Table Editor (below) to set the
rem     Primary DOS partition on the disk to "active" (i.e. bootable).
rem  
rem  
rem  Alternate MBR Type:
rem  
rem  In practice, the following MBR sector is sometimes encountered.
rem  
rem  This is (informally) the "90 E9 7D 01 FA" variant, as it always begins
rem  with those 5 bytes. They immediately preceed the three bytes "33 C0 8E"
rem  which typically begin a standard MBR in FAT32 (see above).
rem  
rem  The first 446 bytes of this variant (i.e. the beginning of the sector,
rem  prior to the Partition Table) are usually in the following form:
rem  
::   <------------------- Hexadecimal -------------------->    <--- ASCII ---->
::          00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F    0123456789ABCDEF
::   ---------------------------------------------------------------------------
::   0000:  90 E9 7D 01 FA 33 C0 8E-D0 8E C0 8E D8 BC 00 7C  [ ��} �3��Ў��ؼ | ]
::   0010:  8B F4 FB BF 00 06 B9 00-01 F3 A5 BB 20 06 FF E3  [ ����  �  �  �� ]
::   0020:  90 90 BE 7D 07 81 3C AA-55 75 11 E8 58 00 73 0C  [ ���} �<�Uu �X s  ]
::   0030:  E8 65 00 72 07 E8 B1 00-72 3B EB 2C BE 7D 07 C7  [ �e r � r;�,�} � ]
::   0040:  04 00 00 BA 80 00 BE BE-07 B9 04 00 F6 04 80 75  [    �� �� �  � �u ]
::   0050:  07 83 C6 10 E2 F6 EB 1D-8A 74 01 8B 4C 02 BB 00  [  �� ��� �t �L �  ]
::   0060:  7C B8 01 02 CD 13 72 0D-81 3E FE 7D 55 AA 75 05  [ |�  � r �>�}U�u  ]
::   0070:  EA 00 7C 00 00 BE 6A 07-AC 0A C0 74 FE BB 07 00  [ � |  �j � �t��   ]
::   0080:  B4 0E CD 10 EB F2 BB 00-7E C6 07 13 C6 47 01 00  [ � � �� ~�  �G   ]
::   0090:  B2 80 B8 00 E0 CD 13 C3-BF 00 7E BA F0 01 B3 A0  [ ��� �� ÿ ~�� �  ]
::   00A0:  E8 84 00 72 0C B1 01 E8-48 00 72 05 E8 19 00 73  [ � r � �H r �  s ]
::   00B0:  16 F6 C3 10 75 05 80 CB-10 EB E5 81 FA 70 01 74  [  �� u �� ���p t ]
::   00C0:  05 BA 70 01 EB D8 F9 C3-81 BD FE 01 55 AA 75 17  [  �p ���Á�� U�u  ]
::   00D0:  8B 75 02 81 FE BE 01 77-0E 03 F7 81 3C AA 55 75  [ �u ��� w  ��<�Uu ]
::   00E0:  06 F6 44 02 01 75 01 F9-C3 BF 00 7C B1 0A E8 01  [  �D  u �ÿ |� �  ]
::   00F0:  00 C3 52 57 83 C2 02 B0-01 EE 42 8A C1 EE 42 32  [  �RW�� � �B���B2 ]
::   0100:  C0 EE 42 EE 42 8A C3 EE-42 B0 20 EE E8 33 00 EC  [ ��B�B���B� ��3 � ]
::   0110:  24 FD 3C 58 75 0D 83 EA-07 B9 00 01 FA F3 6D FB  [ $�<Xu �� �  ��m� ]
::   0120:  F8 EB 01 F9 5F 5A C3 52-83 C2 07 EC A8 80 75 0F  [ �� �_Z�R�� 쨀u  ]
::   0130:  4A 8A C3 EE 42 EC 24 D0-3C 50 75 03 F8 EB 01 F9  [ J���B�$�<Pu �� � ]
::   0140:  5A C3 51 8B 0E 6C 04 83-C1 12 81 C2 FF 01 EC 8A  [ Z�Q� l �� ��� � ]
::   0150:  E0 80 E4 D8 80 FC 58 74-06 3B 0E 6C 04 75 EF 81  [ ���؀�Xt ; l u� ]
::   0160:  EA FF 01 B9 00 20 E2 FE-59 C3 0D 0A 45 72 72 6F  [ �� �  ��Y�  Erro ]
::   0170:  72 20 4C 6F 61 64 69 6E-67 20 4F 53 00 AA 55 00  [ r Loading OS �U  ]
::   0180:  00 E9 80 FE 00 00 00 00-00 00 00 00 00 00 00 00  [  ��             ]
::   0190:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00  [                  ]
::   01A0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00  [                  ]
::   01B0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 ...    [                  ]
rem  
rem  Notes -
rem  1. Excludes the final 66 bytes of the sector, which are unique to
rem     each disk (because they contain the Partition Table).
rem  2. I have come across this variant of the MBR sector so infrequently
rem     that I can't be certain whether it is always in this exact form!
rem  3. I have, in fact, come across variations in bytes 1B8 to 1BD (hex);
rem     so those, at least, are not always in the form set out above.
rem     But this *might* only be the case on an NTFS disk, not FAT32.
rem  4. The final two bytes of the sector are always "55 AA".
rem  5. As the MBR is non-standard, the Boot Sector is likely to be so too.
rem  
rem  NB: I have seen this variant with FAT32 hard disks and with NTFS disks.
rem  
rem  
rem  Partition Table:
rem  
rem  The Partition Table is located in the MBR Sector (CHS 0-0-1)
rem  at offset 1BE hex (byte 447).
rem  
rem  The Partition Table (64 bytes) contains four 16-byte entries.
rem  (NB: Any not in use will be empty, i.e. filled with zero's)
rem  
rem  The format of each 16-byte entry (see PTEDIT.EXE, below):
rem   - Boot indicator (00h = Not active; 80h = Bootable) (1 byte)
rem   - Starting Head number (0 to 254)                   (1 byte)
rem   - Starting Cylinder number (0 to 1023) (10 bits)
rem     and starting Sector number (1 to 63) (6 bits)     (2 bytes)
rem   - Partition Type (FAT32: Type 0C, 0F, 0B or 05)     (1 byte)
rem   - Ending Head number (0 to 255)                     (1 byte)
rem   - Ending Cylinder number (0 to 1023) (10 bits)
rem     and ending Sector number (1 to 63) (6 bits)       (2 bytes)
rem   - Relative sectors (see note, below)                (4 bytes)
rem   - Number of sectors in the partition                (4 bytes)
rem  
rem  This data in the Partition Table tells the Operating System where
rem  each partition starts and ends on the disk, how big that partition
rem  is, whether it's bootable, and the type of filesystem it contains.
rem  
rem  The "Ending cylinder number" is meaningless. "Starting sector"
rem  and "Number of sectors in the partition" are enough to identify
rem  the partition in FAT32: Partition type 0F uses INT 13 Extensions
rem  that use those two numbers as LBA addresses, and does *not* use
rem  the "Ending cylinder number".
rem  
rem  NB: Where a CHS value is meaningless, it does not matter if that
rem      value is incorrect!
rem  
rem  
rem  CHS values in the Partition Table:
rem  
rem  A single byte can hold a number up to 255 (FF hex). On this basis,
rem  a disk would have a limit of 255 cylinders, 255 heads & 255 sectors.
rem  For the Heads byte, this is in fact the case; but the other two
rem  bytes are manipulated to allow for larger numbers.
rem  
rem  Thus the Sector number is stored as a 6 digit binary number, and
rem  the Cylinders as a 10 digit binary number. To fit the byte structure
rem  of 8 bits to a byte, the first two digits of the Cylinder number
rem  are chopped off and put on the front of the Sector number. It gives
rem  a limit of 1023 cylinders, 255 heads, and 63 sectors (i.e. 8GB).
rem  
rem  16 Bits (numbered 0 to 15) [Cylinder = 10 bits, Sector = 6 bits]:
rem  
rem    15 14 13 12 11 10  9  8    7  6              5  4  3  2  1  0  
rem    Cylinder bits 7 to 0       Cyl bits 9 & 8    Sector bits 5 to 0  
rem  
rem  Example:  The number 957F(hex) -
rem  
rem    Hex values :  Byte #1 = 95(hex)
rem                  Byte #2 = 7F(hex)
rem  
rem    Step 1: Convert those Hex numbers to Binary.
rem  
rem    Step 2: Assign the resulting two 8-bit binary numbers to
rem            two 8-bit registers (8 bits in a byte) as follows -
rem      Bit #   15 14 13 12 11 10  9  8   7  6  5  4  3  2  1  0
rem      Binary   1  0  0  1  0  1  0  1   0  1  1  1  1  1  1  1
rem  
rem    Step 3: The Cylinder value is derived from reading the Bits
rem            in the following order (i.e. the "Cylinder bits"):
rem            7, 6, 15, 14, 13, 12, 11, 10, 9, 8
rem  
rem            In this example, doing so gives the Binary number
rem            0110010101 which is 405 in decimal (Cylinder 405)
rem  
rem    Step 4: The Sector value is derived from reading the remaining
rem            Bits in the following order (i.e. the "Sector bits"):
rem            5, 4, 3, 2, 1, 0
rem  
rem            In this example, doing so gives the Binary number
rem            111111 which is 63 in decimal (Sector 63)
rem  
rem  
rem  4-Entry Structure:
rem  
rem  The fact that the Partition Table has four entries imposed a limit
rem  of four partitions on FAT16 disks, as each partition required one
rem  of the Partition Table entries.
rem  
rem  This four-entry structure is retained on FAT32 disks for backward
rem  compatibility with FAT16-based Operating Systems and disk tools;
rem  but FAT32 can have an *unlimited* number of partitions.
rem  
rem  FAT32 uses only the first two entries in the Partition Table. The
rem  1st entry defines the current partition (start sector and length),
rem  and the 2nd entry points to the start of the next partition.
rem  
rem  FAT32 partitions are thus linked together ("chained") by a series
rem  of Partition Table sectors, starting with the MBR.
rem  
rem  NB: A partition table sector at a location other than CHS 0-0-1
rem      (i.e. located within the Extended partition) is known as an
rem      Extended MBR (EMBR).
rem  
rem  
rem  Relative Sectors:
rem  
rem  In the MBR (sector CHS 0-0-1), the column "Relative Sectors"
rem  holds the starting sector of each partition (i.e. usually
rem  the Primary and Extended partitions), in LBA format.
rem  
rem  Thus, in the MBR, "relative sectors" means the number of sectors
rem  from the 1st sector of the disk.
rem  
rem  
rem  EMBR "Relative Sectors":
rem  
rem  In an EMBR partition table, the field "relative sectors" means the
rem  number of sectors from the 1st sector of that Logical partition
rem  (except in links to the *next* Partition Table sector).
rem  
rem  In links to the next Partition Table sector, "relative sectors"
rem  means relative to the start of the *entire* Extended partition.
rem  
rem  NB: What this means in practice is that the "relative sectors"
rem      field in Entry No.1 in an EMBR Partition Table is relative to
rem      the first sector of the *current* partition; but that this
rem      field in Entry No.2 in an EMBR Partition Table is relative to
rem      the first sector of the *entire* Extended Partition.
rem  
rem  NB: The Extended Partition is defined in the MBR (sector 0-0-1),
rem      i.e. in Entry No.2 of the MBR's Partition Table. Each of the
rem      subsequent Partition Tables defines only a Logical partition.
rem  
rem  
rem  Note on PTEDIT.EXE:
rem  
rem  PowerQuest's Partition Table Editor (PTEDIT.EXE) is confusing,
rem  in that it doesn't display the Non-DOS Partition (LBA 0 to 62)
rem  (because that is *not* a real partition).
rem  
rem  The first partition it shows is the Primary DOS partition.
rem  
rem  NB: Beeblebrox.exe, an alternative Partition Editor, might be
rem      easier to understand: it's a little less confusing, as
rem      it gives additional information in its Status line.


rem  PRIMARY DOS PARTITION
rem  =====================
rem  
rem  This is the first partition on the Disk that is recognised by
rem  DOS and Windows. It starts at CHS 0-1-1 (LBA sector 63).
rem  
rem  NB: Its correct name is the Primary DOS Partition; but it's often
rem      referred to loosely as simply the "Primary Partition". Also,
rem      some DOS programs call it just "Primary DOS".
rem  
rem  It is defined in the MBR Partition Table (at CHS 0-0-1) (LBA 0),
rem  which specifies its 1st sector (always CHS 0-1-1) (LBA 63), and
rem  its length in sectors.
rem  
rem  
rem  Bootable:
rem  
rem  The Disk is bootable if the Primary DOS partition is marked as
rem  "active" in the MBR's Partition Table (at CHS 0-0-1).
rem  
rem  NB: Only the Primary DOS partition can normally be bootable. A
rem      Logical partition can't be set as "active" (i.e. bootable),
rem      unless the earlier partitions have Hidden partition types.
rem  
rem  
rem  Boot Record -
rem  
rem  The partition's Boot Record is comprised of 3 sectors (the first
rem  3 sectors of the partition):
rem  
rem   - CHS 0-1-1 (LBA 63) : Boot sector
rem   - CHS 0-1-2 (LBA 64) : FSInfo sector
rem   - CHS 0-1-3 (LBA 65) : Boot Code sector
rem  
rem  NB: Sometimes called the "Extended Boot Record", because
rem      the old FAT16 boot record had only a single sector.
rem  
rem  
rem  Boot Sector -
rem  
rem  Located in the 1st sector of the Partition (CHS 0-1-1) (LBA 63),
rem  incorporating the extended BPB (BIOS Parameter Block):
rem  
rem  Size      Comment                                         Example
rem  -------   ---------------------------------------------   --------
rem  2 bytes   Jump instruction (jump to IPL boot code)        EB58
rem  1 byte    NOP instruction                                 90
rem  8 bytes   OEM ID - Name of formatting Operating System    MSWIN4.1
rem  
rem  (start of BPB in FAT32) (53 bytes)
rem  2 bytes   Bytes per sector             [200(hex) = 512]   200h
rem  1 byte    Sectors per cluster [40(hex) = 64 (i.e.32KB)]   40h
rem            [NB: 10(hex) = 16 (8KB); 20(hex) = 32 (16KB)]
rem  2 bytes   Number of reserved sectors [NB: 20(hex) = 32]   20h
rem            (Number of sectors before the first FAT)
rem            (32 sectors = CHS 0-1-1 to CHS 0-1-32)
rem            (NB: 3 sectors are used for the Boot Record,
rem             and 3 are used for the backup Boot Record;
rem             but the remainder are unused and blank)
rem  1 byte    Number of File Allocation Tables (always 2)     2h
rem  2 bytes   No. of Root Directory entries (N/A in FAT32)    0000
rem            (NB: Unlike FAT16, there is NO limit to the
rem             number of files that can be stored in Root)
rem  2 bytes   Total number of sectors  (Not used in FAT32)    0000
rem            (Small Sectors field; where disk exceeds 32MB
rem             the Large Sectors field is used instead)
rem  1 byte    Media Descriptor (Hard Disk = F8)               F8h
rem            (NB: Normally F8 on non-removeable media)
rem  2 bytes   Number of Sectors per FAT (Not used in FAT32)   0000
rem  2 bytes   Number of Sectors per Head   [3F(hex) = 63]     3Fh
rem  2 bytes   Number of Heads per Cylinder [FF(hex) = 255]    FFh
rem  4 bytes   Number of Hidden sectors     [3F(hex) = 63]     3Fh
rem            (Number of sectors in the Non-DOS partition)
rem            (i.e. sectors CHS 0-0-1 to 0-0-63: Track 0)
rem  4 bytes   Total number of sectors in this partition
rem            (a.k.a. "Large Sectors"/"Big Total Sectors")
rem            (NB: MUST be non-zero in a FAT32 partition!)
rem  4 bytes   Number of Sectors per FAT (FAT32 disks only)
rem            (The number of sectors occupied by each FAT)
rem  2 bytes   FAT handling flag (Enables FAT mirroring,       0000h
rem            if set. If mirroring is enabled, all copies
rem            (i.e. both copies) of the FAT are updated)
rem            [NB: If set as 0, FAT mirroring is ENABLED]
rem  2 bytes   File system version (Always zero in Win9x)      0000h
rem  4 bytes   First cluster of Root Directory (usually 2)     2h
rem            (NB: This identifies the Cluster in which
rem             the Root Directory Table begins)
rem  2 bytes   File system info sector (FS Info Sector)        0001h
rem            (The number of the sector in this partition
rem             occupied by the FS Info sector) (usually 1)
rem            (Sector count starts at 0; so 1 = CHS 0-1-2)
rem  2 bytes   Backup Boot Sector (NB: Usually 6)              0006h
rem            (The number of the sector in this partition
rem             occupied by the Backup Boot Sector)
rem            (Sector count starts at 0; so 6 = CHS 0-1-7)
rem  12 bytes  Reserved (Value is always zero)                 00 (all)
rem  (end of BPB in FAT32)
rem  
rem  (start of Extended BPB) (26 bytes)
rem  1 byte    Disk ID  (Floppy = 00h, Hard Disk = 80h)        80h
rem  1 byte    Reserved for NT (This value is always zero)     00h
rem  1 byte    Extended Boot signature (Usually 29h)           29h
rem            (NB: If value is 29h, the Extended BPB contains
rem             also a Volume Serial Number & a Volume Label)
rem  4 bytes   Volume Serial Number (A random serial number,
rem            created by FORMAT.COM to differentiate Drives)
rem  11 bytes  Volume Label (Some bytes may be spaces, 20h)    DRIVE C
rem  8 bytes   File System type (a.k.a. File System ID)        FAT32
rem            (This is NOT conclusive: Windows does NOT read
rem             this value, it determines the FAT type SOLELY
rem             from the number of clusters in the partition!)
rem  (end of Extended BPB)
rem  
rem  Total = 90 bytes (Address 00h to 59h, inclusive)
rem  
rem  420 bytes  The next 420 bytes are the IPL (Initial Program Loader)
rem             boot code (which passes control to the Operating System
rem             in the active Partition), and the Partition Table.
rem  
rem  2 bytes    The final 2 bytes are the 2 signature bytes (55AA hex),
rem             which mark the end of the Boot Sector.
rem  
rem  Notes -
rem  (1) Wherever an entry comprises 2 or more bytes, as usual
rem      these are read from right-to-left (i.e. little endian).
rem  (2) A number followed by the letter h means a Hexadecimal number.
rem  
rem  Examples: Copies of sector CHS 0-1-1 follow (below), saved by the
rem  program MBRSCAN.EXE from several disks, as examples of the correct
rem  code for that sector.
rem  
rem  
rem  First 3 Bytes:
rem  
rem  The MBR transfers CPU execution to the boot sector; so the first
rem  three bytes of the boot sector must be valid executable x86-based
rem  CPU instructions. This includes a jump instruction that skips the
rem  next several non-executable bytes.
rem  
rem  Following the jump instruction is the 8-byte OEM ID (MSWIN4.1),
rem  a string of characters that identify the name and version number
rem  of the Operating System that formatted the partition.
rem  
rem  
rem  Jump Instruction (3 bytes):
rem  
rem  Instructs the computer to jump over the BPB (Bios Parameter Block)
rem  to the first byte of executable code (the first byte after the BPB
rem  and Extended BPB). The jump is 88 bytes (58 hex), to byte 5A(hex),
rem  which is the first byte of the Initial Program Loader (IPL) code.
rem  
rem  NB: The first 3 bytes (EB 58 90) are called the Jump Instruction,
rem      but only the first two bytes are the actual JMP instruction
rem      (a two-byte SHORT jump, executing a jump to the remainder of
rem      the executable code). The third byte (90 hex) is just a NOP
rem      instruction [NOP = 'No Op', i.e. do nothing].
rem  
rem  
rem  FAT Mirroring (2 bytes):
rem  
rem  Bits 0-3 : The number of the active FAT (starting from 0, not 1).
rem             (Only valid if mirroring disabled, i.e. if bit 7 = 1)
rem  Bits 4-6 : Reserved (i.e. not used).
rem  Bit  7   : A value of 0 means the FAT is mirrored into all FATs.
rem             A value of 1 means only one FAT is active (i.e. the
rem             one specified in bits 0-3).
rem  Bits 8-15: Reserved (i.e. not used).
rem  
rem  NB: There are 8 bits in a byte (usually numbered from 0 to 7)
rem  
rem  
rem  FS Info Sector (2 bytes):
rem  
rem  This MUST point to the FS Info Sector (which is invariably the
rem  second sector in the partition, i.e. CHS 0-1-2). This value is
rem  always 1 (as the LBA sector count starts at 0) (0 = CHS 0-1-1).
rem  
rem  The only other possible value in this field is 0 (zero), which
rem  appears to mean the FS Info Sector is to be ignored (i.e. that
rem  it will not be used).
rem  
rem  NB: In that situation, the O/S will recalculate the amount of
rem      free space on the disk whenever that value is needed (a
rem      slower procedure than simply looking it up), instead of
rem      storing the free space value in the FS Info Sector.
rem  
rem  
rem  Sanity Check of Boot Sector:
rem  
rem  All the following *mandatory* elements must be present:-
rem  
rem  - The jump signature must be EB or 90 or E0
rem  - The sector size (i.e. Bytes per Sector) must be 512
rem  - The cluster size (i.e. Sectors per Cluster) must be:
rem     1, 2, 4, 8, 16, 32, 64 or 128
rem  - The FAT32 version must be 0.0
rem  - There must be 2 copies of the FAT
rem  - The media type must be F8 (though it's an obsolete feature)
rem  - The signature (i.e. File System ID) should be "FAT32"
rem     (though it's meaningless)
rem  - The sector must end with the hex value AA55 (written as 55AA)
rem  
rem  NB: Although not strictly a sanity check, the ultimate test
rem      of the boot sector's validity is whether it matches the
rem      contents of the backup boot sector (usually CHS 0-1-6).
rem  
rem  
rem  FS Info Sector -
rem  
rem  File System Information Sector (FS Info Sector) (CHS 0-1-2)
rem  
rem  The second sector of the partition. There is a pointer to it
rem  in the partition's Boot Sector (at bytes 49 & 50).
rem  
rem  The ID marker RRaA at the start of the sector marks it as an
rem  Extended Boot Record. A similar ID, rrAa (the same letters,
rem  but with the case of the letters inverted) marks the start of
rem  the "Total Free Clusters" and "Next Available Cluster" data.
rem  
rem  Offset  Description                                   Size
rem  ------  --------------------------------------------  ---------
rem  00h     ID marker (Always 52 52 61 41) (ASCII: RRaA)    4 bytes
rem          (Lead signature; validates the sector)
rem  04h     Null (all 00h)                                480 bytes
rem  1E4h    ID marker (Always 72 72 41 61) (ASCII: rrAa)    4 bytes
rem          (Structure signature; validates the sector)
rem  1E8h    Number of Free Clusters                         4 bytes
rem          (Contains the last-known free cluster count)
rem          (NB: The count is unknown if FFFFFFFF or -1)
rem  1ECh    Cluster # where the O/S should start looking    4 bytes
rem          for free clusters. (If the value is FFFFFFFF
rem          the O/S should start looking from Cluster 2)
rem          (NB: Located at Bytes 493-496 [1ECh to 1EFh])
rem          [Cluster 2 is written in hex as: 02 00 00 00]
rem  1F0h    Reserved (all 00)                              12 bytes
rem  1FCh    Null (00 00)                                    2 bytes
rem  1FEh    ID marker (55AA hex)                            2 bytes
rem          (Trailing signature; validates the sector)
rem  
rem  Both ScanDisk for DOS (SCANDISK.EXE) and ScanDisk for Windows
rem  (SCANDSKW.EXE) check the amount of free space in the partition
rem  (the "free cluster count"), and correct the value stored in
rem  the FS Info Sector if it's wrong (but NOT if the Boot Sector's
rem  pointer is 0 (i.e. zero): this prevents detection of the error).
rem  
rem  NB: Norton's DiskEdit CANNOT detect an error in the "free cluster
rem      count"; the only tools that can detect and fix it are ScanDisk
rem      and Norton Disk Doctor.
rem  
rem  NB: It appears that NO critical disk operations are dependent on
rem      the accuracy of the "free cluster count", which seems to be
rem      provided for information only.
rem  
rem  WARNING:
rem  You should not run CHKDSK or SCANDISK or any other disk scanning
rem  program if the disk has crashed, or there is any logical error in
rem  the MBR or Boot Record, or the FAT or Root Directory is corrupted.
rem  It may make data information distorted, and can cause data loss.
rem  
rem  
rem  *** Routine to view the FS Info Sector ***
rem  
rem  View the current state of the FS Info sector to discover:-
rem    - The number of free clusters.
rem    - The cluster number at which the O/S will begin looking
rem      for free clusters (those marked 0 in the FAT); usually,
rem      but not always, this points to the first *free* cluster.
rem  
rem  NB: The O/S often specifies Cluster 2 as the one to start
rem      looking for free clusters from, since this leaves no
rem      chance of missing any unused clusters in the search.
rem  
rem  NB: Whenever ScanDisk corrects an error in the FSInfo Sector
rem      it resets the "start from" value to 2.
rem  
rem  ** View FSInfo Sector of Drive C (using XVI32.EXE) **
:: FINDPART GETSECT 1 0 1 2 1 DISK_C.FS noheader badf6
:: C:\Progra~1\HexEdi~1\XVI32.exe DISK_C.FS
rem  
rem  ** View FSInfo Sector of Drive D **
:: FINDPART GETSECT 2 0 1 2 1 DISK_D.FS noheader badf6
:: C:\Progra~1\HexEdi~1\XVI32.exe DISK_D.FS
rem  
rem  ** View FSInfo Sector of Drive E **
:: FINDPART GETSECT 1 1275 1 2 1 DISK_E.FS noheader badf6
:: C:\Progra~1\HexEdi~1\XVI32.exe DISK_E.FS
rem  
rem  
rem  Sanity Check of FSInfo Sector:
rem  
rem  Make sure that FSInfo Sector is sector 1 or later of the partition,
rem  counting from 0 (it's normally sector 1); and that it's within the
rem  reserved disk area; and that its sector number is not the same as
rem  that used for the Backup BootSector; and that its three signatures
rem  are correct (though only the second is documented by Microsoft).
rem  
rem  If it does not satisfy these conditions, do not use the sector;
rem  but the file system should still be usable.
rem  
rem  NB: The number of free clusters is normally checked only by disk
rem      analysis programs: it is not critical to the filesystem.
rem  
rem  
rem  Boot Code sector -
rem  
rem  The 3rd sector of the partition (CHS 0-1-3)
rem  
rem  It contains boot code (510 bytes of boot program code), beginning
rem  with the ID marker "FA 66 OF" (though this is NOT a unique marker).
rem  
rem  It ends with a two byte ID signature (55AA hex).
rem  
rem  This sector contains NO system-specific information! It contains
rem  only standard code that is identical on *all* FAT32 disks.
rem  
rem  
rem  Executable Code:
rem  
rem  On a FAT32 hard disk, formatted by Win98/98SE/ME, the Boot Code sector
rem  normally looks like this (in Hex and ASCII). 32 lines of 16 bytes each:-
rem  
rem  <------------------- Hexadecimal -------------------->    <--- ASCII ---->
rem         00 01 02 03 04 05 06 07 08 09 0A 0B 0C 0D 0E 0F    0123456789ABCDEF
rem  ---------------------------------------------------------------------------
::   0000:  FA 66 0F B6 46 10 66 8B-4E 24 66 F7 E1 66 03 46  [ �f.�F.f�N$f��f.F ]
::   0010:  1C 66 0F B7 56 0E 66 03-C2 33 C9 66 89 46 FC 66  [ .f.�V.f.�3�f�F�f ]
::   0020:  C7 46 F8 FF FF FF FF FA-66 8B 46 2C 66 83 F8 02  [ �F�....�f�F,f��. ]
::   0030:  0F 82 CF FC 66 3D F8 FF-FF 0F 0F 83 C5 FC 66 0F  [ .���f=�....���f. ]
::   0040:  A4 C2 10 FB 52 50 FA 66-C1 E0 10 66 0F AC D0 10  [ ��.�RP�f��.f.��. ]
::   0050:  66 83 E8 02 66 0F B6 5E-0D 8B F3 66 F7 E3 66 03  [ f��.f.�^.��f��f. ]
::   0060:  46 FC 66 0F A4 C2 10 FB-BB 00 07 8B FB B9 01 00  [ F�f.��.��..���.. ]
::   0070:  E8 BE FC 0F 82 AA FC 38-2D 74 1E B1 0B 56 BE D8  [ ��.���8-t.�.V�� ]
::   0080:  7D F3 A6 5E 74 19 03 F9-83 C7 15 3B FB 72 E8 4E  [ }�^t..���.;�r�N ]
::   0090:  75 D6 58 5A E8 66 00 72-AB 83 C4 04 E9 64 FC 83  [ u�XZ�f.r���.�d�� ]
::   00A0:  C4 04 8B 75 09 8B 7D 0F-8B C6 FA 66 C1 E0 10 8B  [ �.�u.�}.���f��.� ]
::   00B0:  C7 66 83 F8 02 72 3B 66-3D F8 FF FF 0F 73 33 66  [ �f��.r;f=�...s3f ]
::   00C0:  48 66 48 66 0F B6 4E 0D-66 F7 E1 66 03 46 FC 66  [ HfHf.�N.f��f.F�f ]
::   00D0:  0F A4 C2 10 FB BB 00 07-53 B9 04 00 E8 52 FC 5B  [ .��.��..S�..�R�[ ]
::   00E0:  0F 82 3D FC 81 3F 4D 5A-75 08 81 BF 00 02 42 4A  [ .�=��?MZu.��..BJ ]
::   00F0:  74 06 BE 80 7D E9 0E FC-EA 00 02 70 00 03 C0 13  [ t.��}�.��..p..�. ]
::   0100:  D2 03 C0 13 D2 E8 18 00-FA 26 66 8B 01 66 25 FF  [ �.�.��..�&f�.f%. ]
::   0110:  FF FF 0F 66 0F A4 C2 10-66 3D F8 FF FF 0F FB C3  [ ...f.��.f=�...�� ]
::   0120:  BF 00 7E FA 66 C1 E0 10-66 0F AC D0 10 66 0F B7  [ �.~�f��.f.��.f.� ]
::   0130:  4E 0B 66 33 D2 66 F7 F1-66 3B 46 F8 74 44 66 89  [ N.f3�f��f;F�tDf� ]
::   0140:  46 F8 66 03 46 1C 66 0F-B7 4E 0E 66 03 C1 66 0F  [ F�f.F.f.�N.f.�f. ]
::   0150:  B7 5E 28 83 E3 0F 74 16-3A 5E 10 0F 83 A4 FB 52  [ �^(��.t.:^..���R ]
::   0160:  66 8B C8 66 8B 46 24 66-F7 E3 66 03 C1 5A 52 66  [ f��f�F$f��f.�ZRf ]
::   0170:  0F A4 C2 10 FB 8B DF B9-01 00 E8 B4 FB 5A 0F 82  [ .��.��߹..��Z.� ]
::   0180:  9F FB FB 8B DA C3 00 00-00 00 00 00 00 00 00 00  [ ������.......... ]
::   0190:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00  [ ................ ]
::   01A0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00  [ ................ ]
::   01B0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00  [ ................ ]
::   01C0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00  [ ................ ]
::   01D0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00  [ ................ ]
::   01E0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00  [ ................ ]
::   01F0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 55 AA  [ ..............U� ]
rem  
rem  Notes -
rem  1. Hexadecimal: Base 16 (0,1,2,3,4,5,6,7,8,9,A,B,C,D,E,F).
rem  2. ASCII: American Standard Code for Information Interchange
rem     (a set of 255 characters, including A to Z and 0 to 9).
rem  3. For each 2-digit hexadecimal number in the above table,
rem     you can identify its (hexadecimal) address in the sector
rem     by combining the row number (hex) in the left-hand margin
rem     with the column number (also in hex) across the top;
rem     e.g. the number in the 3rd column of the 3rd line is F8
rem     and its address is 22 hex: 0020 (left column) + 02 (top).
rem  
rem  
rem  Backup Sectors -
rem  
rem  The 7th sector of the partition (CHS 0-1-7) (LBA 69) (at 8A00 hex)
rem  contains a BACKUP copy of CHS 0-1-1 (LBA 63) (Boot sector).
rem  
rem  The 8th sector of the partition (CHS 0-1-8) (LBA 70) (at 8C00 hex)
rem  contains a BACKUP copy of CHS 0-1-2 (LBA 64) (FS Info sector).
rem  
rem  NB: This backup of the FS Info Sector is NOT kept synchronised
rem      with the main FS Info Sector. Its "Number of Free Clusters"
rem      is set to -1 and its "Most Recently Allocated Cluster" is 2
rem      (suggesting that those were the initial settings used by the
rem      formatting program which created this partition, e.g. FDISK)
rem  
rem  The 9th sector of the partition (CHS 0-1-9) (LBA 71) (at 8E00 hex)
rem  contains a BACKUP copy of CHS 0-1-3 (LBA 65) (Boot Code sector).
rem  
rem  
rem  Reserved Sectors -
rem  
rem  As specified in the partition's Boot Sector (CHS 0-1-1) (LBA 63), the
rem  first 32 sectors of the Partition (CHS 0-1-1 to 0-1-32) are reserved.
rem  
rem  CHS 0-1-1 to 0-1-9 are in use, as above. The remainder of the
rem  32 reserved sectors (CHS 0-1-10 to 0-1-32) only contain zeros; and
rem  are immediately followed by the 1st FAT, which starts at CHS 0-1-33.
rem  
rem  
rem  File Allocation Table -
rem  
rem  The 1st FAT begins in the first sector after the number of
rem  Reserved Sectors specified in the partition's Boot Record.
rem  
rem  NB: In a FAT32 partition, the Boot Sector (CHS 0-1-1) usually
rem      specifies 32 reserved sectors (20 hex), thus the 1st FAT
rem      begins in CHS 0-1-33 (the 33rd sector of the Partition),
rem      i.e. LBA 95 (a.k.a. "Absolute Sector 95").
rem  
rem  The FAT begins with a unique marker (usually "F8 FF FF FF")
rem  (see below).
rem  
rem  If FAT mirroring is enabled (in the Boot Sector), a backup
rem  copy - or "mirror" - of the FAT is kept. This second FAT
rem  is stored immediately after the first FAT, and can be
rem  used by the Operating System if the first FAT is damaged.
rem  
rem  Example (ST380011A):
rem  
rem  FAT size for an 80GB partition = 19,075 sectors
rem  (according to PowerQuest's Partition Manager, PTEDIT.EXE)
rem  so FATs 1 and 2 = 19,075 x 2 = 38,150 sectors (19,075 KB)
rem  
rem  The 2nd FAT begins at CHS 1-49-19 (LBA 19,170) (95C400 hex)
rem  because 95 + 19,075 = 19,170 (since there are 95 sectors
rem  before the 1st FAT: CHS 0-0-1 to CHS 0-1-32 inclusive).
rem  
rem  
rem  Root Directory -
rem  
rem  The Root Directory table usually begins in the first sector after
rem  the 2nd FAT. That sector can be calculated from the CHS address
rem  of the starting sector of the 1st FAT, as follows:
rem  
rem    (Cylinders x 255 x 63) + (Heads x 63) + (Sectors x 1)
rem     + (Big Total Sectors per FAT x 2) - 1 = LBA Sector
rem  
rem  To convert that LBA sector number to a CHS value, see the
rem  note "Convert from Sectors to CHS" (below); or use the
rem  Win9x program PTcalc.exe (a CHS calculator for Windows).
rem  
rem  NB: The root directory on a FAT32 partition can legitimately
rem      be located *anywhere* in the partition! Its cluster address
rem      is stored in the Boot Sector; this can point to any cluster
rem      in the partition, it need not point to cluster 2.
rem  
rem  The Root Directory table occupies 1 Cluster (64 sectors,
rem  if cluster size is 32K). Those sectors are mostly empty;
rem  they reserve space which the table can use if necessary.
rem  But if that space is fully used, the Root Directory Table
rem  (like any file) can continue in another cluster.
rem  
rem  Note: The amount of space occupied in the table by a file's
rem        Directory entry depends upon whether the file has a
rem        Long File Name; so the number of files which will
rem        fill up 64 sectors can vary.
rem  
rem  Note: Where the cluster is full, a pointer is set indicating
rem        the next cluster used to store the table.
rem  
rem  
rem  Example (Hard Disk WD800JB, Drive C):-
rem  
rem    Data for 1st FAT -
rem  
rem      Starting sector of 1st FAT: CHS 0-1-33
rem      Size of 1st FAT in sectors: 9,992
rem  
rem    Step 1: Calculate in REAL sectors -
rem  
rem      CHS 0-1-33 = (0 x 255 x 63) + (1 x 63) + (33 x 1) = 96
rem      96 + (2 x 9,992) = 20,080
rem  
rem    Step 2: Convert REAL sectors to CHS -
rem  
rem      1 Cylinder = 255 heads x 63 sectors = 16,065 sectors
rem      (i.e. Sectors / 16,065 = Cylinders)
rem       20,080 / 16,065 = 1 cylinder (Remainder = 4,015)
rem  
rem      1 Head = 63 sectors
rem      (i.e. Remainder / 63 = Heads)
rem       4,015 / 63 = 63 heads (Remainder = 46)
rem  
rem      1 Sector = 1 sector
rem      (i.e. Remainder = Sectors)
rem       46 / 1 = 46 sectors
rem  
rem      CHS = 1-63-46
rem  
rem    Step 3: Convert REAL sectors to LBA -
rem  
rem      Real Sectors - 1 = LBA
rem       20,080 - 1 = 20,079
rem  
rem  
rem  CHS address of Root Directory Table:-
rem  
rem  Western Digital WD800JB 80GB (New bootable HDD)
rem    Primary DOS Partition (Drive C:) = CHS 1-63-46    (LBA:     20,079)
rem    1st Logical Partition (Drive E:) = CHS 1277-17-49 (LBA: 20,516,124)
rem  
rem  Western Digital WD800JB 80GB (New Drive D: HDD)
rem    Primary DOS Partition (Drive D:) = CHS 2-97-9     (LBA:     38,249)
rem  
rem  M02GB2: SeaGate ST320423A 18GB (Win98 HDD)
rem    Primary DOS Partition (Drive D:) = CHS 1-40-39    (LBA:     18,623)
rem  
rem  NB: CHS 0-0-1 = LBA 0 (i.e. Add 1 to convert LBA into actual sectors)
rem  
rem  
rem  Files -
rem  
rem  Actual files begin in the first sector <u>after</u> the cluster
rem  reserved for the Root Directory Table, i.e. in cluster 3.
rem  
rem  NB: On a WinME system, the directory table for the RECYCLE bin
rem      (a hidden system directory) usually occupies cluster 3.
rem  
rem  Address of cluster 3 =
rem  (1st sector of Root Directory Table, LBA) + (Sectors per Cluster)
rem  
rem  NB: Sectors per Cluster = Bytes in each Allocation Unit / 512
rem      (Run CHKDSK.EXE, where "allocation unit" means a Cluster)
rem      [Usually 64 sectors per cluster if partition exceeds 32GB]
rem  
rem  Example (Drive D, 80GB):
rem  LBA 38,249 + 64 = LBA 38,313 (CHS 2-98-10)


rem  EXTENDED PARTITION
rem  ==================
rem  
rem  A FAT32 disk typically has up to four partitions:
rem  1 x Primary DOS Partition
rem  1 x Extended Partition, containing up to 3 Logical Partitions
rem  
rem  On a FAT32 disk, the second entry in the MBR Partition Table
rem  (at CHS 0-0-1) defines the Extended Partition, specifying its
rem  1st sector (the LBA sector number) and its length in sectors.
rem  
rem  The first sector of the Extended Partition is called the EMBR
rem  (Extended Master Boot Record).
rem  
rem  The first sector of the Extended Partition reads just like
rem  the MBR in sector CHS 0-0-1, but has blanks instead of code
rem  in some locations. Where the Partition Table was in the MBR,
rem  the first entry defines the 1st Logical partition.
rem  
rem  NB: The 1st Logical Partition MUST fall entirely *within*
rem      the Extended Partition.
rem  
rem  NB: If the 1st Logical Partition does not completely fill
rem      the Extended Partition, further Logical partitions can
rem      exist in the remaining space.
rem  
rem  If there are any more partitions, the second entry points to
rem  the partition table of another Logical partition; the sector
rem  number in this second entry is relative to the 1st sector of
rem  the *entire* Extended Partition.
rem  
rem  Thus the Extended Partition is sub-divided into one or more
rem  Logical Partitions. In practice, there is NO limit to the
rem  number of Logical Partitions: FAT32 is *not* constrained by
rem  the fact that the Partition Table has only 4 entries, since
rem  it never uses entries 3 or 4 (chaining the Partition Tables
rem  instead, in a linked chain of EBPR sectors).
rem  
rem  As the Partition Tables form a 'chain', if that chain is broken
rem  at any point, all Logical partitions defined later in the chain
rem  (beyond the 'breakpoint') cannot be accessed.
rem  
rem  A Partition Table sector pointing to the next Partition Table
rem  sector must ALWAYS point forward, never to a previous sector!
rem  
rem  A Logical Partition is structured like the Primary Partition:-
rem   - 63 "hidden" sectors, starting with a Partition Table
rem   - 64th sector is the Boot sector
rem   - 65th sector is the FS Info sector
rem   - 66th sector is the Boot Code sector
rem   - 96th sector is the start of the 1st FAT
rem  
rem  
rem  Making a Logical Partition Bootable:
rem  
rem  In theory, Logical drives are NOT bootable. In reality, this
rem  limitation can be overcome by hiding any prior partitions;
rem  i.e. assigning them a HIDDEN partition type.
rem  
rem  For example, a Primary Partition of type 0C can be hidden by
rem  changing it to type 1C. (NB: A partition type should ONLY be
rem  changed by altering the leading 0 [zero] to a 1. It might be
rem  unsafe to alter the partition type in any other way.)
rem  
rem  
rem  Note on Partition Reconstruction:
rem  
rem  Undeleting Logical partitions without causing Partition Table
rem  errors is tricky. However, it is possible to undelete a Logical
rem  partition as a Primary partition, in order to copy the data off
rem  that partition (e.g. by hiding all the prior partitions).
rem  
rem  NB: See also Pierre's Guide to Partition Table Recovery -
rem      http://www.datarescue.com/laboratory/partition.htm


rem  DELETING PARTITIONS
rem  ===================
rem  
rem  Sometimes, due to a corrupt EMBR (Extended Master Boot Record)
rem  chain, FDISK.EXE will not delete a particular partition correctly.
rem  
rem  To delete the partition manually, change all the values in the
rem  partition's entry in the Partition Table to 0.


rem  PARTITION TABLE EDITOR
rem  ======================
rem  
rem  PTEDIT.EXE
rem  PowerQuest's Partition Table Editor for DOS, v1.0
rem  
rem  This enables the Partition Table in the MBR sector to be edited
rem  in a user-friendly GUI.
rem  
rem  *** Edit the Partition Table ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE;F:\SAVED\RECOVERY
:: MOUSE
:: PTEDIT
rem  
rem  NB: There is also a version of the program that runs under Win9x
rem      (PTEDIT32.EXE)
rem  
rem  
rem  Calculate Partition:
rem  
rem  To calculate *all* the CHS and LBA values in a Partition,
rem  see below (under "CALCULATE LBA PARTITION").


::  /--------------------------------------------------------------------/  ::


rem                       SAVE DISK INFORMATION
rem                       =====================

rem  CHKDSK.EXE
rem  ==========

rem  *** Save Cluster information ***
::   CHKDSK C: > F:\SAVED\CHKDSK_C.txt
::   CHKDSK D: > F:\SAVED\CHKDSK_D.txt
::   CHKDSK E: > F:\SAVED\CHKDSK_E.txt


rem  MBRSCAN.EXE
rem  ===========

rem  MBRSCAN v1.12
rem  
rem  Saves MBR & Boot Sector information for any IDE, SCSI or USB
rem  disk recognised by the BIOS.
rem  
rem  Saves an exact record (as ASCII) of the disk's MBR sector
rem  *including* the Partition Table, AND of each Boot Sector;
rem  and saves partition details for each partition on the disk.
rem  
rem  NB: The program's geometry function sometimes fails under
rem      Windows. If so, run the program in DOS instead.

rem  *** Save a report for Disk 1 ***
::   MBRSCAN 80 > F:\SAVED\MBRscan.D1

rem  *** Save a report for Disk 2 ***
::   MBRSCAN 81 > F:\SAVED\MBRscan.D2

rem  *** Save a report for Disk 3 ***
::   MBRSCAN 82 > F:\SAVED\MBRscan.D3

rem  *** Save a report for Disk 4 ***
::   MBRSCAN 83 > F:\SAVED\MBRscan.D4

rem  Note -
rem  There are only four IDE channels (two per cable), so only
rem  four IDE hard disks can be connected at any one time.


rem  BIOS.EXE
rem  ========

rem  BIOS.EXE v1.35
rem  
rem  Save and Restore the computer's BIOS settings.

rem  The program's functions:
rem  
rem  - Save and restore the BIOS settings
rem  - Validate actual settings to saved settings
rem  - Delete the BIOS settings (there are some strange cases...)
rem  - Display information about the BIOS, BIOS Extensions and
rem    BIOS beepcodes
rem  - Find BIOS passwords for Award, Ami, Phoenix and AST BIOS
rem  - Find BIOS universal passwords for Award BIOS
rem  - Dump the whole BIOS segment to disk
rem  - Switch the 1st and 2nd level caches on/off
rem  - Turn the PC into Standby or Suspend mode (requires APM 1.1+)
rem  - Turn off the PC (requires APM 1.2+)
rem  - Reboot the PC (cold/warm/int19)
rem  - Return DOS error codes for batch processing


rem  Syntax -
rem  
rem  Usage: BIOS [option]
rem  
rem  I = information on BIOS
rem  X = information on BIOS extensions
rem  B = information on BIOS beep codes
rem  P = find BIOS passwords (only Award, AMI, PHOENIX and AST)
rem  U = find BIOS universal password (only Award)
rem  S [FILE] = save CMOS data [to FILE] (default: c:\bios.sav)
rem  R [FILE] = restore CMOS data [from FILE] (default: c:\bios.sav)
rem  V [FILE] = validate CMOS data [to FILE] (default: c:\bios.sav)
rem  E = erase CMOS data
rem  D [FILE] = dump BIOS segment [to FILE] (default: c:\bios.dmp)
rem  A+/A- = enable/disable Advanced Power Management
rem  L1+/L1-/L2+/L2- = enable/disable 1st/2nd level cache
rem  Y = system information (requires LM7x/LM80/Winbond chipset)
rem  C/W/Z = cold boot / warm boot / reset using Int 19h
rem  M/N/O = standby / suspend / turn PC off
rem  
rem  For updates look at www.geocities.com/mbockelkamp
rem  For bug reports and improvement tips write to mbockelkamp@web.de


rem  *** Save the BIOS ***
rem  
rem  ** Save BIOS settings to a Backup file **
:: BIOS S F:\SAVED\CMOS.BIN
rem  
rem  Note:
rem  
rem  Do NOT do this in a Windows DOS box. The BIOS is divided
rem  in two parts: the first contains procedures only needed
rem  while booting, the second contains all other procedures.
rem  The first part of the BIOS segment is used as conventional
rem  memory after booting. If you try to make a BIOS dump from
rem  within Win9x, you get a dump file with some normal memory
rem  and the second part of the BIOS; the first part is missing.


rem  ** Compare the BIOS settings with a Backup file **
:: BIOS V F:\SAVED\CMOS.BIN
rem  
rem  Meaning of result codes -
rem  000 - Everything OK
rem  128 - V: Identical
rem  129 - V: Not identical
rem  130 - D: PC isn't in Real Mode
rem  253 - Error in commandline
rem  254 - Error in file operation
rem  255 - Function not supported


rem  ** Restore the BIOS settings from a Backup file **
:: BIOS R F:\SAVED\CMOS.BIN


rem  *** Save additional BIOS information ***
:: BIOS I > F:\SAVED\BiosInfo.txt
:: BIOS X > F:\SAVED\BiosExtensions.txt
:: BIOS B > F:\SAVED\BiosBeepCodes.txt


rem  *** Save BIOS Password ***
:: BIOS P > F:\SAVED\PASSWORD.txt


rem  *** Save BIOS Password State ***
:: BIOS D BIOS.DMP
rem  
rem  There are eight possible states -
rem  1. No passwords, security option: setup
rem  2. No passwords, security option: system
rem  3. Only superviser password, security option: setup
rem  4. Only superviser password, security option: system
rem  5. Only user password, security option: setup
rem  6. Only user password, security option: system
rem  7. Both passwords, security option: setup
rem  8. Both passwords, security option: system


rem  *** Manage BIOS Cache from DOS ***
rem  
rem  Enable 1st level cache:
:: BIOS L1+
rem  
rem  Disable 1st level cache:
:: BIOS L1-
rem  
rem  Enable 2nd level cache:
:: BIOS L2+
rem  
rem  Disable 2nd level cache:
:: BIOS L2-


rem  LOST BIOS PASSWORD
rem  ==================
rem  
rem  The user can be locked out of the BIOS by a forgotten password!
rem  
rem  A lost BIOS password usually has to be reset using a master password,
rem  software program, or hardware jumper (to gain access to the BIOS).
rem  
rem  
rem  A. Master Password
rem  
rem  To bypass a BIOS password, try one of these standard manufacturer's
rem  "backdoor" passwords.
rem  
rem  (a) AWARD BIOS -
rem  AWARD SW, AWARD_SW, Award SW, AWARD PW, _award, awkward, J64, j256,
rem  j262, j332, j322, 01322222, 589589, 589721, 595595, 598598, HLT,
rem  SER, SKY_FOX, aLLy, aLLY, Condo, CONCAT, TTPTHA, aPAf, HLT, KDD,
rem  ZBAAACA, ZAAADA, ZJAAADC, djonet, %����� �p������%, %������ �p������%
rem  (NB: The last two passwords in that list are in Russian!)
rem  
rem  (b) AMI BIOS -
rem  AMI, A.M.I., AMI SW, AMI_SW, BIOS, PASSWORD, HEWITT RAND, Oder
rem  
rem  (c) AMI/AWARD or other BIOS -
rem  LKWPETER, lkwpeter, BIOSTAR, biostar, BIOSSTAR, biosstar, ALFAROME,
rem  Syxz, Wodj
rem  
rem  Notes:
rem  1. These passwords are Case Sensitive!
rem  2. The key marked "_" on a US keyboard corresponds to "?" on some
rem  European keyboards, so type AWARD?SW or AMI?SW when using one.
rem  
rem  
rem  B. Software Solution - Reset the BIOS
rem  
rem  To bypass the BIOS password, run the following program at startup. It
rem  removes the password by resetting the BIOS to its default settings.
rem  
rem  *** Clear (ERASE) BIOS settings ***
:: BIOS E
rem  
rem  Alternatively, do the same manually. Use the MS-DOS tool DEBUG to
rem  reset the BIOS to its default values: type DEBUG at the command prompt
rem  in pure MS-DOS mode (NOT from an MS-DOS box in Windows); and then
rem  type the following 2 line command:
rem  
rem  For an AMI/AWARD BIOS -
rem  O 70 17
rem  O 71 17
rem  Q
rem  
rem  For a PHOENIX BIOS -
rem  O 70 FF
rem  O 71 17
rem  Q
rem  
rem  For a GENERIC BIOS -
rem  O 70 2E
rem  O 71 FF
rem  Q
rem  
rem  This invalidates the CMOS RAM, so should work on all AT motherboards;
rem  XT motherboards don't have CMOS.
rem  
rem  Notes: 1. The first character is the *letter* "O" not the number "0".
rem         2. The numbers which follow it are two bytes in hex format.
rem         3. The third line is Q (QUIT).
rem  
rem  
rem  C. Hardware Solution - Reset the Jumper
rem  
rem  On most motherboards there are not one but *two* sets of jumpers.
rem  One resets the BIOS defaults (usually the one near the battery or
rem  CMOS chip). The other resets the BIOS password (the password jumper).
rem  
rem  NB: The motherboard's manual will identify the correct jumper!
rem  
rem  NB: Most systems store the BIOS password in nvram (non-volitile ram),
rem      which does NOT lose information when the power is off. Therefore
rem      removing the CMOS battery will *not* reset the BIOS password!
rem  
rem  
rem  D. Hardware Solution - Accessing the Data
rem  
rem  To access data on a HDD, remove it from the inaccessible computer
rem  and install it temporarily as IDE Primary Slave on another computer.
rem  
rem  
rem  E. Other Solutions
rem  
rem  There are other hardware solutions: e.g. short-circuiting the chip,
rem  replacing the chip.
rem  
rem  For these, see http://www.elfqrin.com/docs/biospw.html
rem  
rem  The only other hardware option is to REPLACE the motherboard.


rem  CMOS.COM
rem  ========

rem  Save and Restore the CMOS settings.
rem  
rem  Saves and restores all 114 bytes of CMOS memory. Many older
rem  programs only save the first 50 bytes: this used not to matter
rem  but many BIOS manufacturers are now using the 'high' 64 bytes.


rem  Syntax -
rem  
rem  CMOS /SAVE filename
rem  
rem  Save CMOS to file "filename"
rem  (NB: If no filename is specified, the default is CMOS.SAV)
rem  
rem  
rem  CMOS /COMPARE filename
rem  
rem  Verifies the contents of CMOS memory against a file
rem  (NB: ERRORLEVEL 7 indicates a mismatch between CMOS and file)
rem  
rem  
rem  CMOS /RESTORE filename
rem  
rem  Load CMOS settings from file "filename" and reboot
rem  (NB: If no filename is specified, the default is CMOS.SAV)
rem  
rem  
rem  CMOS /DUMP
rem  
rem  Dumps current contents of CMOS to the screen (or to STDOUT)
rem  in hex. (NB: Useful only to hexperts)
rem  
rem  
rem  Note:
rem  
rem  Uses a different file format from other programs. You cannot
rem  share data files between CMOS.COM and SAVECMOS.EXE or ROM2.EXE
rem  as it uses a special file header to prevent the user loading
rem  (for instance) AUTOEXEC.BAT or some other non-CMOS data into
rem  CMOS memory, and to guarantee file integrity.
rem  
rem  Note: Test this utility to determine whether it can correctly
rem        save and restore your CMOS - before an emergency occurs!


rem  *** Save the CMOS settings ***
:: CMOS /SAVE    F:\SAVED\CMOS.SAV

rem  *** Compare the CMOS settings with Backup file ***
:: CMOS /COMPARE F:\SAVED\CMOS.SAV

rem  *** Restore the CMOS settings ***
:: CMOS /RESTORE F:\SAVED\CMOS.SAV


::  /--------------------------------------------------------------------/  ::


rem                           SAVE A SECTOR
rem                           =============

rem  This BATCH file is designed to work with -
rem  Svend's Utilities: FINDPART for DOS (version 4.72)
rem                     FINDPART for Windows (version 4.95 for FAT32)

rem  NB: In this version of Svend's Utilities the GETSECT function is
rem      a switch (i.e. an option) in FINDPART, not a seperate program


rem  *** Preparation ***
rem  1. Make an empty directory (E:\SAVED\DATA) to store output files
rem     and put this Batch File in that directory.
rem  2. Make an empty directory on a USB Disk at F:\SAVED\DATA
rem     to store a backup copy of the output files.

rem  Notes:
rem  The main directory holding saved sectors is E:\SAVED\DATA
rem  This file DISK.EXE is principally held in E:\SAVED\RECOVERY


rem  SYNTAX of FINDPART
rem  ==================
rem  
rem  First is the number of the Disk (numbered from 1), e.g. 1
rem  Next is the CHS number, e.g. 0 0 1
rem  Next is the number of sectors to save, e.g. 1
rem  Next specify a destination file, e.g. on Drive A: (floppy)
rem  
rem  The option NOHEADER means only the actual data will be written,
rem  not the identifying fileheader normally added by GETSECT
rem  
rem  The option BADF6 means the program will write character F6 (hex)
rem  for all bytes that can't be read (something that will only occur
rem  if the Disk is physically damaged)
rem  
rem  NB: The program WILL cope with bad sectors, writing the hex
rem      character specified in place of every byte of a bad sector,
rem      but its multiple read attempts will slow the program down
rem      (such that to read a 19,075 sector FAT took 1.5 hours)

rem  Note:
rem  When examining a binary file saved by FINDPART (e.g. viewing it
rem  with Norton's DISKEDIT), bear in mind that like any file it will
rem  consist of 32 sectors (on a FAT32 partition with 16KB clusters),
rem  therefore it does NOT contain only the content of the sector(s)
rem  saved; a Disk Editor does NOT recognise the End Of File marker,
rem  so will ALSO show the unused sectors, of those 32, containing junk


rem  Abbreviations used in FINDPART'S output:
rem  
rem  B   Based on boot sector.
rem  BU  Based on backup boot sector (meaning that the boot sector
rem      may be missing or damaged, or the partition is obsolete).
rem  00  The boot sector is filled with ASCII character 0.
rem  F6  The boot sector is filled with ASCII character 246.
rem  R   Reiser file system.
rem  3   Ext3 file system.
rem  H   HPFS (OS/2) file system.
rem  B5  A Linux boot sector with boot signature.
rem  NR  Boot sector not readable: bad sector, or outside disk area.
rem  NB  Nota Bene.
rem  R0  The boot sector relative field is relative to LBA sector 0.
rem  OK  Okay.
rem  !!  An extended partition ending at cylinder 1024 or later (type 05).
rem  *   In front of ID: Active flag set.
rem      After cylinder number: The actual entry is 1023.
rem      After Cluster KB in FAT output: Based on boot sector.
rem      After Root size/Cluster number in FAT output: Based on boot sector.
rem  #   After cylinder number: The actual entry is 1023/(heads-1)/sectors.
rem      After Cluster KB in FAT output: Not confirmed in boot sector.
rem      After Root size/Cluster number in FAT output: Not confirmed in
rem      boot sector.
rem  ?   In front of ID: Active flag not hexadecimal 00 or 80.
rem      After partition line: Ending after end of disk.



rem                             DISK 1
rem                             ======


rem  NON-DOS PARTITION  (Track Zero)
rem  =================

rem  *** Save Sector 0-0-1 (Master Boot Record & Partition Table) ***
:: FINDPART GETSECT 1 0 0 1 1 F:\0-0-1.D1 noheader badf6

rem  *** Save Sector 0-0-9 (Sector 9 of Track 0) (Backup MBR) ***
:: FINDPART GETSECT 1 0 0 9 1 F:\0-0-9.D1 noheader badf6

rem  *** Save Sector 0-0-1 to 0-0-63 (Entire Track 0) ***
:: FINDPART GETSECT 1 0 0 1 63 F:\0-0-1-63.D1 noheader badf6

rem  Note:
rem  Track 0 is usually *empty* except for CHS 0-0-1 and 0-0-9

rem  Note: The above sectors only need to be saved ONCE,
rem        as their values are permanent!


rem  PRIMARY PARTITION
rem  =================

rem  *** Save Sector 0-1-1 (Boot Sector) ***
:: FINDPART GETSECT 1 0 1 1 1 F:\0-1-1.D1 noheader badf6

rem  *** Save Sector 0-1-2 (FS Info Sector) ***
:: FINDPART GETSECT 1 0 1 2 1 F:\0-1-2.D1 noheader badf6

rem  *** Save Sector 0-1-3 (Boot Data Sector) ***
:: FINDPART GETSECT 1 0 1 3 1 F:\0-1-3.D1 noheader badf6

rem  *** Save Sector 0-1-1 to 0-1-32 (First 32 sectors) ***
:: FINDPART GETSECT 1 0 1 1 32 F:\0-1-1-32.D1 noheader badf6

rem  *** Save Sector 0-1-1 to 0-1-63 (Entire Track 1) ***
rem  ** This includes some duplication, but is essential ** 
:: FINDPART GETSECT 1 0 1 1 63 F:\0-1-1-63.D1 noheader badf6

rem  ** The above sectors only need to be saved ONCE **
rem  ** as their values are permanent (but see Note) **
rem  
rem  Note: FS Info Sector should be regularly backed up.
rem        The amount of free disk space is stored in
rem        this sector; but CHKDSK.EXE or SCANDISK.EXE
rem        can recalculate it!

rem  *** Save Sector 96 onward: FAT 1 & 2 ***
rem  ** Need to be saved daily, as FAT details change constantly **
rem  ** These will be BIG files, so do NOT save them to floppy! **
rem  ** Number of sectors to save = Big Sectors Per FAT **
rem      The value of "Big Sectors Per FAT" is displayed by
rem      the 32bit version of PowerQuest Partition Table Editor
rem      - Find this value in DOS with PTEDIT.EXE (below),
rem        PowerQuest's Partition Table Editor for DOS
rem  ** User must insert CHS value of 33rd sector of this Partition **
rem  ** and the number of sectors to be saved: "Big Sectors per FAT" **
:: FINDPART GETSECT 1 0   1 33 _____ F:\PRI_FAT1.D1 noheader badf6
rem  ** User must find CHS start sector of 2nd FAT with FINDPART (below)
rem  ** and the number of sectors to be saved: "Big Sectors per FAT" **
:: FINDPART GETSECT 1 _ ___ __ _____ F:\PRI_FAT2.D1 noheader badf6

rem  *** PowerQuest Partition Table Editor for DOS ***
rem   **    Find value of "Big Sectors Per FAT"    **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE;F:\SAVED\RECOVERY
:: MOUSE
:: PTEDIT

rem  *** Svend's FINDPART: FindFAT Option ***
rem  
rem   ** Find start sector of 2nd FAT (Disk 1, Primary Partition) **
rem   ** A quick search, for a Disk which has only one partition  **
:: FINDPART FINDFAT 1 0 1 F:\FAT_CHS1.TXT
rem  
rem   ** Find start sector of 2nd FAT (Disk 1, All Partitions) **
rem   **    Reports starting sector (CHS) and size (sectors)   **
rem   **      of all FATs on the Disk (Primary & Logical)      **
:: FINDPART FINDFAT 1 comprehensive F:\FAT_DSK1.TXT

rem  *** See also SRCFAT, below ***
rem  SRCFAT.EXE is a utility which can save and restore the FAT,
rem  *without* needing any user input as to the sector addresses

rem  *** Save the Root Directory table ***
rem  NB: The Root Directory table begins in the first sector
rem      after the 2nd FAT, and one cluster is reserved for it
rem  ** User must insert CHS value of 1st sector after the 2nd FAT **
rem  NB: Svend's FINDPART: FindFAT Option (above) reports the
rem      starting sector (CHS) and size (sectors) of the 2nd FAT
rem  NB: See note, "Convert from Sectors to CHS", below!
:: FINDPART GETSECT 1 _ __ __ 64 ROOT.D1 noheader badf6


rem  EXTENDED PARTITION
rem  ==================

rem  1st Logical Partition -

rem  *** Save Boot Sector ***
rem  ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART GETSECT 1 _____ 0 1 1 F:\L1_1st.D1 noheader badf6

rem  *** Save FS Info Sector ***
rem  ** User must insert CHS value of 2nd sector of this Partition **
:: FINDPART GETSECT 1 _____ 0 2 1 F:\L1_2nd.D1 noheader badf6

rem  *** Save Boot Data Sector ***
rem  ** User must insert CHS value of 3rd sector of this Partition **
:: FINDPART GETSECT 1 _____ 0 3 1 F:\L1_3rd.D1 noheader badf6

rem  *** Save first 32 sectors of Partition ***
rem  ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART GETSECT 1 _____ 0 1 32 F:\L1_1-32.D1 noheader badf6

rem  *** Save first 63 sectors of Partition ***
rem  ** This includes some duplication, but is essential ** 
rem  ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART GETSECT 1 _____ 0 1 63 F:\L1_1-63.D1 noheader badf6

rem  ** The above sectors only need to be saved ONCE **
rem  ** as their values are permanent (but see Note) **
rem  
rem  Note: FS Info Sector should be regularly backed up.
rem        The amount of free disk space is stored in
rem        this sector; but CHKDSK.EXE or SCANDISK.EXE
rem        can recalculate it!

rem  *** Save Sector 96 onward: FAT 1 & 2 ***
rem  ** Need to be saved daily, as FAT details change constantly **
rem  ** These will be BIG files, so do NOT save them to floppy! **
rem  ** Number of sectors to save = Big Sectors per FAT **
rem      The value of "Big Sectors per FAT" is displayed by
rem      the 32bit version of PowerQuest Partition Table Editor
rem      - Find this value in DOS with PTEDIT.EXE (below),
rem        PowerQuest's Partition Table Editor for DOS
rem  ** User must insert CHS value of 33rd sector of this Partition **
rem  ** and the number of sectors to be saved: "Big Sectors per FAT" **
:: FINDPART GETSECT 1 _____ 1 33 _____ F:\L1_FAT1.D1 noheader badf6
rem  ** User must find CHS start sector of 2nd FAT with FINDPART (below)
rem  ** and the number of sectors to be saved: "Big Sectors per FAT" **
:: FINDPART GETSECT 1 _____ _ __ _____ F:\L1_FAT2.D1 noheader badf6

rem  *** PowerQuest Partition Table Editor for DOS ***
rem   **    Find value of "Big Sectors Per FAT"    **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE;F:\SAVED\RECOVERY
:: MOUSE
:: PTEDIT

rem  *** Svend's FINDPART: FindFAT Option ***
rem  
rem   ** Find start sector of 2nd FAT (Disk 1, All Partitions) **
rem   **    Reports starting sector (CHS) and size (sectors)   **
rem   **      of all FATs on the Disk (Primary & Logical)      **
:: FINDPART FINDFAT 1 comprehensive F:\FAT_DSK1.TXT

rem  *** See also SRCFAT, below ***
rem  SRCFAT.EXE is a utility which can save and restore the FAT,
rem  *without* needing any user input as to the sector addresses

rem  *** Save the Root Directory table ***
rem  NB: The Root Directory table begins in the first sector
rem      after the 2nd FAT, and one cluster is reserved for it
rem  ** User must insert CHS value of 1st sector after the 2nd FAT **
rem  NB: Svend's FINDPART: FindFAT Option (above) reports the
rem      starting sector (CHS) and size (sectors) of the 2nd FAT
rem  NB: See note, "Convert from Sectors to CHS", below!
:: FINDPART GETSECT 1 _ __ __ 64 L1_ROOT.D1 noheader badf6


rem  2nd Logical Partition -

rem  *** Save Boot Sector ***
rem  ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART GETSECT 1 _____ 0 1 1 F:\L2_1st.D1 noheader badf6

rem  *** Save FS Info Sector ***
rem  ** User must insert CHS value of 2nd sector of this Partition **
:: FINDPART GETSECT 1 _____ 0 2 1 F:\L2_2nd.D1 noheader badf6

rem  *** Save Boot Data Sector ***
rem  ** User must insert CHS value of 3rd sector of this Partition **
:: FINDPART GETSECT 1 _____ 0 3 1 F:\L2_3rd.D1 noheader badf6

rem  *** Save first 32 sectors of Partition ***
rem  ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART GETSECT 1 _____ 0 1 32 F:\L2_1-32.D1 noheader badf6

rem  *** Save first 63 sectors of Partition ***
rem  ** This includes some duplication, but is essential ** 
rem  ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART GETSECT 1 _____ 0 1 63 F:\L2_1-63.D1 noheader badf6

rem  ** The above sectors only need to be saved ONCE **
rem  ** as their values are permanent (but see Note) **
rem  
rem  Note: FS Info Sector should be regularly backed up.
rem        The amount of free disk space is stored in
rem        this sector; but CHKDSK.EXE or SCANDISK.EXE
rem        can recalculate it!

rem  *** Save Sector 96 onward: FAT 1 & 2 ***
rem  ** Need to be saved daily, as FAT details change constantly **
rem  ** These will be BIG files, so do NOT save them to floppy! **
rem  ** Number of sectors to save = Big Sectors per FAT **
rem      The value of "Big Sectors per FAT" is displayed by
rem      the 32bit version of PowerQuest Partition Table Editor
rem      - Find this value in DOS using PTEDIT.EXE (below),
rem        PowerQuest's Partition Table Editor for DOS
rem  ** User must insert CHS value of 33rd sector of this Partition **
rem  ** and the number of sectors to be saved: "Big Sectors per FAT" **
:: FINDPART GETSECT 1 _____ 1 33 _____ F:\L2_FAT1.D1 noheader badf6
rem  ** User must find CHS start sector of 2nd FAT with FINDPART (below)
rem  ** and the number of sectors to be saved: "Big Sectors per FAT" **
:: FINDPART GETSECT 1 _____ _ __ _____ F:\L2_FAT2.D1 noheader badf6

rem  *** PowerQuest Partition Table Editor for DOS ***
rem   **    Find value of "Big Sectors Per FAT"    **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE;F:\SAVED\RECOVERY
:: MOUSE
:: PTEDIT

rem  *** Svend's FINDPART: FindFAT Option ***
rem  
rem   ** Find start sector of 2nd FAT (Disk 1, All Partitions) **
rem   **    Reports starting sector (CHS) and size (sectors)   **
rem   **      of all FATs on the Disk (Primary & Logical)      **
:: FINDPART FINDFAT 1 comprehensive F:\FAT_DSK1.TXT

rem  *** See also SRCFAT, below ***
rem  SRCFAT.EXE is a utility which can save and restore the FAT,
rem  *without* needing any user input as to the sector addresses

rem  *** Save the Root Directory table ***
rem  NB: The Root Directory table begins in the first sector
rem      after the 2nd FAT, and one cluster is reserved for it
rem  ** User must insert CHS value of 1st sector after the 2nd FAT **
rem  NB: Svend's FINDPART: FindFAT Option (above) reports the
rem      starting sector (CHS) and size (sectors) of the 2nd FAT
rem  NB: See note, "Convert from Sectors to CHS", below!
:: FINDPART GETSECT 1 _ __ __ 64 L2_ROOT.D1 noheader badf6


rem  3rd Logical Partition -

rem  *** Save Boot Sector ***
rem  ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART GETSECT 1 _____ 0 1 1 F:\L3_1st.D1 noheader badf6

rem  *** Save FS Info Sector ***
rem  ** User must insert CHS value of 2nd sector of this Partition **
:: FINDPART GETSECT 1 _____ 0 2 1 F:\L3_2nd.D1 noheader badf6

rem  *** Save Boot Data Sector ***
rem  ** User must insert CHS value of 3rd sector of this Partition **
:: FINDPART GETSECT 1 _____ 0 3 1 F:\L3_3rd.D1 noheader badf6

rem  *** Save first 32 sectors of Partition ***
rem  ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART GETSECT 1 _____ 0 1 32 F:\L3_1-32.D1 noheader badf6

rem  *** Save first 63 sectors of Partition ***
rem  ** This includes some duplication, but is essential ** 
rem  ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART GETSECT 1 _____ 0 1 63 F:\L3_1-63.D1 noheader badf6

rem  ** The above sectors only need to be saved ONCE **
rem  ** as their values are permanent (but see Note) **
rem  
rem  Note: FS Info Sector should be regularly backed up.
rem        The amount of free disk space is stored in
rem        this sector; but CHKDSK.EXE or SCANDISK.EXE
rem        can recalculate it!

rem  *** Save Sector 96 onward: FAT 1 & 2 ***
rem  ** Need to be saved daily, as FAT details change constantly **
rem  ** These will be BIG files, so do NOT save them to floppy! **
rem  ** Number of sectors to save = Big Sectors per FAT **
rem      The value of "Big Sectors per FAT" is displayed by
rem      the 32bit version of PowerQuest Partition Table Editor
rem      - Find this value in DOS with PTEDIT.EXE (below),
rem        PowerQuest's Partition Table Editor for DOS
rem  ** User must insert CHS value of 33rd sector of this Partition **
rem  ** and the number of sectors to be saved: "Big Sectors per FAT" **
:: FINDPART GETSECT 1 _____ 1 33 _____ F:\L3_FAT1.D1 noheader badf6
rem  ** User must find CHS start sector of 2nd FAT with FINDPART (below)
rem  ** and the number of sectors to be saved: "Big Sectors per FAT" **
:: FINDPART GETSECT 1 _____ _ __ _____ F:\L3_FAT2.D1 noheader badf6

rem  *** PowerQuest Partition Table Editor for DOS ***
rem   **    Find value of "Big Sectors Per FAT"    **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE;F:\SAVED\RECOVERY
:: MOUSE
:: PTEDIT

rem  *** Svend's FINDPART: FindFAT Option ***
rem  
rem   ** Find start sector of 2nd FAT (Disk 1, All Partitions) **
rem   **    Reports starting sector (CHS) and size (sectors)   **
rem   **      of all FATs on the Disk (Primary & Logical)      **
:: FINDPART FINDFAT 1 comprehensive F:\FAT_DSK1.TXT

rem  *** See also SRCFAT, below ***
rem  SRCFAT.EXE is a utility which can save and restore the FAT,
rem  *without* needing any user input as to the sector addresses

rem  *** Save the Root Directory table ***
rem  NB: The Root Directory table begins in the first sector
rem      after the 2nd FAT, and one cluster is reserved for it
rem  ** User must insert CHS value of 1st sector after the 2nd FAT **
rem  NB: Svend's FINDPART: FindFAT Option (above) reports the
rem      starting sector (CHS) and size (sectors) of the 2nd FAT
rem  NB: See note, "Convert from Sectors to CHS", below!
:: FINDPART GETSECT 1 _ __ __ 64 L3_ROOT.D1 noheader badf6



rem                             DISK 2
rem                             ======


rem  NON-DOS PARTITION  (Track Zero)
rem  =================

rem  *** Save Sector 0-0-1 (Master Boot Record & Partition Table) ***
:: FINDPART GETSECT 2 0 0 1 1 F:\0-0-1.D2 noheader badf6

rem  *** Save Sector 0-0-9 (Sector 9 of Track 0) (Backup MBR) ***
:: FINDPART GETSECT 2 0 0 9 1 F:\0-0-9.D2 noheader badf6

rem  *** Save Sector 0-0-1 to 0-0-63 (Entire Track 0) ***
:: FINDPART GETSECT 2 0 0 1 63 F:\0-0-1-63.D2 noheader badf6

rem  Note:
rem  Track 0 is usually *empty* except for CHS 0-0-1 and 0-0-9

rem  Note: The above sectors only need to be saved ONCE,
rem        as their values are permanent!


rem  PRIMARY PARTITION
rem  =================

rem  *** Save Sector 0-1-1 (Boot Sector) ***
:: FINDPART GETSECT 2 0 1 1 1 F:\0-1-1.D2 noheader badf6

rem  *** Save Sector 0-1-2 (FS Info Sector) ***
:: FINDPART GETSECT 2 0 1 2 1 F:\0-1-2.D2 noheader badf6

rem  *** Save Sector 0-1-3 (Boot Data Sector) ***
:: FINDPART GETSECT 2 0 1 3 1 F:\0-1-3.D2 noheader badf6

rem  *** Save Sector 0-1-1 to 0-1-32 (First 32 sectors) ***
:: FINDPART GETSECT 2 0 1 1 32 F:\0-1-1-32.D2 noheader badf6

rem  *** Save Sector 0-1-1 to 0-1-63 (Entire Track 1) ***
rem  ** This includes some duplication, but is essential ** 
:: FINDPART GETSECT 2 0 1 1 63 F:\0-1-1-63.D2 noheader badf6

rem  ** The above sectors only need to be saved ONCE **
rem  ** as their values are permanent (but see Note) **
rem  
rem  Note: FS Info Sector should be regularly backed up.
rem        The amount of free disk space is stored in
rem        this sector; but CHKDSK.EXE or SCANDISK.EXE
rem        can recalculate it!

rem  *** Save Sector 96 onward: FAT 1 & 2 ***
rem  ** Need to be saved daily, as FAT details change constantly **
rem  ** These will be BIG files, so do NOT save them to floppy! **
rem  ** Number of sectors to save = Big Sectors per FAT **
rem      The value of "Big Sectors per FAT" is displayed by
rem      the 32bit version of PowerQuest Partition Table Editor
rem      - Find this value in DOS with PTEDIT.EXE (below),
rem        PowerQuest's Partition Table Editor for DOS
rem  ** User must insert CHS value of 33rd sector of this Partition **
rem  ** and the number of sectors to be saved: "Big Sectors per FAT" **
:: FINDPART GETSECT 2 0   1 33 _____ F:\PRI_FAT1.D2 noheader badf6
rem  ** User must find CHS start sector of 2nd FAT with FINDPART (below)
rem  ** and the number of sectors to be saved: "Big Sectors per FAT" **
:: FINDPART GETSECT 2 0 ___ __ _____ F:\PRI_FAT2.D2 noheader badf6

rem  *** PowerQuest Partition Table Editor for DOS ***
rem   **    Find value of "Big Sectors Per FAT"    **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE;F:\SAVED\RECOVERY
:: MOUSE
:: PTEDIT

rem  *** Svend's FINDPART: FindFAT Option ***
rem  
rem   ** Find start sector of 2nd FAT (Disk 2, Primary Partition) **
rem   ** A quick search, for a Disk which has only one partition  **
:: FINDPART FINDFAT 2 0 1 F:\FAT_CHS2.TXT
rem  
rem   ** Find start sector of 2nd FAT (Disk 2, All Partitions) **
rem   **    Reports starting sector (CHS) and size (sectors)   **
rem   **      of all FATs on the Disk (Primary & Logical)      **
:: FINDPART FINDFAT 2 comprehensive F:\FAT_DSK2.TXT

rem  *** See also SRCFAT, below ***
rem  SRCFAT.EXE is a utility which can save and restore the FAT,
rem  *without* needing any user input as to the sector addresses

rem  *** Save the Root Directory table ***
rem  NB: The Root Directory table begins in the first sector
rem      after the 2nd FAT, and one cluster is reserved for it
rem  ** User must insert CHS value of 1st sector after the 2nd FAT **
rem  NB: Svend's FINDPART: FindFAT Option (above) reports the
rem      starting sector (CHS) and size (sectors) of the 2nd FAT
rem  NB: See note, "Convert from Sectors to CHS", below!
:: FINDPART GETSECT 2 _ __ __ 64 ROOT.D2 noheader badf6


rem  EXTENDED PARTITION
rem  ==================

rem  1st Logical Partition -

rem  *** Save Boot Sector ***
rem  ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART GETSECT 2 _____ 0 1 1 F:\L1_1st.D2 noheader badf6

rem  *** Save FS Info Sector ***
rem  ** User must insert CHS value of 2nd sector of this Partition **
:: FINDPART GETSECT 2 _____ 0 2 1 F:\L1_2nd.D2 noheader badf6

rem  *** Save Boot Data Sector ***
rem  ** User must insert CHS value of 3rd sector of this Partition **
:: FINDPART GETSECT 2 _____ 0 3 1 F:\L1_3rd.D2 noheader badf6

rem  *** Save first 32 sectors of Partition ***
rem  ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART GETSECT 2 _____ 0 1 32 F:\L1_1-32.D2 noheader badf6

rem  *** Save first 63 sectors of Partition ***
rem  ** This includes some duplication, but is essential ** 
rem  ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART GETSECT 2 _____ 0 1 63 F:\L1_1-63.D2 noheader badf6

rem  ** The above sectors only need to be saved ONCE **
rem  ** as their values are permanent (but see Note) **
rem  
rem  Note: FS Info Sector should be regularly backed up.
rem        The amount of free disk space is stored in
rem        this sector; but CHKDSK.EXE or SCANDISK.EXE
rem        can recalculate it!

rem  *** Save Sector 96 onward: FAT 1 & 2 ***
rem  ** Need to be saved daily, as FAT details change constantly **
rem  ** These will be BIG files, so do NOT save them to floppy! **
rem  ** Number of sectors to save = Big Sectors per FAT **
rem      The value of "Big Sectors per FAT" is displayed by
rem      the 32bit version of PowerQuest Partition Table Editor
rem      - Find this value in DOS with PTEDIT.EXE (below),
rem        PowerQuest's Partition Table Editor for DOS
rem  ** User must insert CHS value of 33rd sector of this Partition **
rem  ** and the number of sectors to be saved: "Big Sectors per FAT" **
:: FINDPART GETSECT 2 _____ 1 33 _____ F:\L1_FAT1.D2 noheader badf6
rem  ** User must find CHS start sector of 2nd FAT with FINDPART (below)
rem  ** and the number of sectors to be saved: "Big Sectors per FAT" **
:: FINDPART GETSECT 2 _____ _ __ _____ F:\L1_FAT2.D2 noheader badf6

rem  *** PowerQuest Partition Table Editor for DOS ***
rem   **    Find value of "Big Sectors Per FAT"    **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE;F:\SAVED\RECOVERY
:: MOUSE
:: PTEDIT

rem  *** Svend's FINDPART: FindFAT Option ***
rem  
rem   ** Find start sector of 2nd FAT (Disk 2, All Partitions) **
rem   **    Reports starting sector (CHS) and size (sectors)   **
rem   **      of all FATs on the Disk (Primary & Logical)      **
:: FINDPART FINDFAT 2 comprehensive F:\FAT_DSK2.TXT

rem  *** See also SRCFAT, below ***
rem  SRCFAT.EXE is a utility which can save and restore the FAT,
rem  *without* needing any user input as to the sector addresses

rem  *** Save the Root Directory table ***
rem  NB: The Root Directory table begins in the first sector
rem      after the 2nd FAT, and one cluster is reserved for it
rem  ** User must insert CHS value of 1st sector after the 2nd FAT **
rem  NB: Svend's FINDPART: FindFAT Option (above) reports the
rem      starting sector (CHS) and size (sectors) of the 2nd FAT
rem  NB: See note, "Convert from Sectors to CHS", below!
:: FINDPART GETSECT 2 _ __ __ 64 L1_ROOT.D2 noheader badf6


rem  2nd Logical Partition -

rem  *** Save Boot Sector ***
rem  ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART GETSECT 2 _____ 0 1 1 F:\L2_1st.D2 noheader badf6

rem  *** Save FS Info Sector ***
rem  ** User must insert CHS value of 2nd sector of this Partition **
:: FINDPART GETSECT 2 _____ 0 2 1 F:\L2_2nd.D2 noheader badf6

rem  *** Save Boot Data Sector ***
rem  ** User must insert CHS value of 3rd sector of this Partition **
:: FINDPART GETSECT 2 _____ 0 3 1 F:\L2_3rd.D2 noheader badf6

rem  *** Save first 32 sectors of Partition ***
rem  ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART GETSECT 2 _____ 0 1 32 F:\L2_1-32.D2 noheader badf6

rem  *** Save first 63 sectors of Partition ***
rem  ** This includes some duplication, but is essential ** 
rem  ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART GETSECT 2 _____ 0 1 63 F:\L2_1-63.D2 noheader badf6

rem  ** The above sectors only need to be saved ONCE **
rem  ** as their values are permanent (but see Note) **
rem  
rem  Note: FS Info Sector should be regularly backed up.
rem        The amount of free disk space is stored in
rem        this sector; but CHKDSK.EXE or SCANDISK.EXE
rem        can recalculate it!

rem  *** Save Sector 96 onward: FAT 1 & 2 ***
rem  ** Need to be saved daily, as FAT details change constantly **
rem  ** These will be BIG files, so do NOT save them to floppy! **
rem  ** Number of sectors to save = Big Sectors per FAT **
rem      The value of "Big Sectors per FAT" is displayed by
rem      the 32bit version of PowerQuest Partition Table Editor
rem      - Find this value in DOS with PTEDIT.EXE (below),
rem        PowerQuest's Partition Table Editor for DOS
rem  ** User must insert CHS value of 33rd sector of this Partition **
rem  ** and the number of sectors to be saved: "Big Sectors per FAT" **
:: FINDPART GETSECT 2 _____ 1 33 _____ F:\L2_FAT1.D2 noheader badf6
rem  ** User must find CHS start sector of 2nd FAT with FINDPART (below)
rem  ** and the number of sectors to be saved: "Big Sectors per FAT" **
:: FINDPART GETSECT 2 _____ _ __ _____ F:\L2_FAT2.D2 noheader badf6

rem  *** PowerQuest Partition Table Editor for DOS ***
rem   **    Find value of "Big Sectors Per FAT"    **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE;F:\SAVED\RECOVERY
:: MOUSE
:: PTEDIT

rem  *** Svend's FINDPART: FindFAT Option ***
rem  
rem   ** Find start sector of 2nd FAT (Disk 2, All Partitions) **
rem   **    Reports starting sector (CHS) and size (sectors)   **
rem   **      of all FATs on the Disk (Primary & Logical)      **
:: FINDPART FINDFAT 2 comprehensive F:\FAT_DSK2.TXT

rem  *** See also SRCFAT, below ***
rem  SRCFAT.EXE is a utility which can save and restore the FAT,
rem  *without* needing any user input as to the sector addresses

rem  *** Save the Root Directory table ***
rem  NB: The Root Directory table begins in the first sector
rem      after the 2nd FAT, and one cluster is reserved for it
rem  ** User must insert CHS value of 1st sector after the 2nd FAT **
rem  NB: Svend's FINDPART: FindFAT Option (above) reports the
rem      starting sector (CHS) and size (sectors) of the 2nd FAT
rem  NB: See note, "Convert from Sectors to CHS", below!
:: FINDPART GETSECT 2 _ __ __ 64 L2_ROOT.D2 noheader badf6


rem  3rd Logical Partition -

rem  *** Save Boot Sector ***
rem  ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART GETSECT 2 _____ 0 1 1 F:\L3_1st.D2 noheader badf6

rem  *** Save FS Info Sector ***
rem  ** User must insert CHS value of 2nd sector of this Partition **
:: FINDPART GETSECT 2 _____ 0 2 1 F:\L3_2nd.D2 noheader badf6

rem  *** Save Boot Data Sector ***
rem  ** User must insert CHS value of 3rd sector of this Partition **
:: FINDPART GETSECT 2 _____ 0 3 1 F:\L3_3rd.D2 noheader badf6

rem  *** Save first 32 sectors of Partition ***
rem  ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART GETSECT 2 _____ 0 1 32 F:\L3_1-32.D2 noheader badf6

rem  *** Save first 63 sectors of Partition ***
rem  ** This includes some duplication, but is essential ** 
rem  ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART GETSECT 2 _____ 0 1 63 F:\L3_1-63.D2 noheader badf6

rem  ** The above sectors only need to be saved ONCE **
rem  ** as their values are permanent (but see Note) **
rem  
rem  Note: FS Info Sector should be regularly backed up.
rem        The amount of free disk space is stored in
rem        this sector; but CHKDSK.EXE or SCANDISK.EXE
rem        can recalculate it!

rem  *** Save Sector 96 onward: FAT 1 & 2 ***
rem  ** Need to be saved daily, as FAT details change constantly **
rem  ** These will be BIG files, so do NOT save them to floppy! **
rem  ** Number of sectors to save = Big Sectors per FAT **
rem      The value of "Big Sectors per FAT" is displayed by
rem      the 32bit version of PowerQuest Partition Table Editor
rem      - Find this value in DOS with PTEDIT.EXE (below),
rem        PowerQuest's Partition Table Editor for DOS
rem  ** User must insert CHS value of 33rd sector of this Partition **
rem  ** and the number of sectors to be saved: "Big Sectors per FAT" **
:: FINDPART GETSECT 2 _____ 1 33 _____ F:\L3_FAT1.D2 noheader badf6
rem  ** User must find CHS start sector of 2nd FAT with FINDPART (below)
rem  ** and the number of sectors to be saved: "Big Sectors per FAT" **
:: FINDPART GETSECT 2 _____ _ __ _____ F:\L3_FAT2.D2 noheader badf6

rem  *** PowerQuest Partition Table Editor for DOS ***
rem   **    Find value of "Big Sectors Per FAT"    **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE;F:\SAVED\RECOVERY
:: MOUSE
:: PTEDIT

rem  *** Svend's FINDPART: FindFAT Option ***
rem  
rem   ** Find start sector of 2nd FAT (Disk 2, All Partitions) **
rem   **    Reports starting sector (CHS) and size (sectors)   **
rem   **      of all FATs on the Disk (Primary & Logical)      **
:: FINDPART FINDFAT 2 comprehensive F:\FAT_DSK2.TXT

rem  *** See also SRCFAT, below ***
rem  SRCFAT.EXE is a utility which can save and restore the FAT,
rem  *without* needing any user input as to the sector addresses

rem  *** Save the Root Directory table ***
rem  NB: The Root Directory table begins in the first sector
rem      after the 2nd FAT, and one cluster is reserved for it
rem  ** User must insert CHS value of 1st sector after the 2nd FAT **
rem  NB: Svend's FINDPART: FindFAT Option (above) reports the
rem      starting sector (CHS) and size (sectors) of the 2nd FAT
rem  NB: See note, "Convert from Sectors to CHS", below!
:: FINDPART GETSECT 2 _ __ __ 64 L3_ROOT.D2 noheader badf6


::  /--------------------------------------------------------------------/  ::


rem                         RESTORE A SECTOR
rem                         ================

rem  Svend's Utilities: FINDPART for DOS (version 4.72)

rem  NB: In this version of Svend's Utilities the PUTSECT function is
rem      a switch (i.e. an option) in FINDPART, not a seperate program


rem  RECOVERY PROCEDURE
rem  ==================
rem  
rem  The quickest way to recover is -
rem  1) Boot to the DOS prompt (with a bootable floppy disk)
rem  2) Rebuild the hard disk's MBR (CHS 0-0-1) (from backup)
rem  3) Rebuild the hard disk's Boot Sector (CHS 0-1-1) (from backup)
rem  4) Restore hard disk's File Allocation Table (FAT1) (from backup)
rem  
rem  NB: The floppy disk must contain the version of DOS required by
rem      the version of Windows that's on the hard disk being fixed
rem  
rem  NB: This will only repair the Primary DOS partition; but that is
rem      the partition most likely to be damaged if the disk won't boot
rem  
rem  Note: If the 2nd (backup) FAT is undamaged, set the first 4 bytes
rem        of the 1st FAT to 00000000 so Windows will detect that it's
rem        corrupt, therefore will automagically use the 2nd FAT


rem  SYNTAX of PUTSECT
rem  =================
rem  
rem  Writes a 512 byte file to a (512 byte) disk sector
rem  (NB: The PUTSECT function will *only* write a 512 byte file!)
rem  
rem  First is the number of the Disk (numbered from 1), e.g. 1
rem  (NB: Valid disk numbers are from 1 to 8)
rem  Next is the sector's CHS number: e.g. 0 0 1
rem  Next is the FILENAME of the source file
rem  Next is the number of cylinders on the disk, a 4-digit number
rem  (NB: Get this number [a DECIMAL number] with PARTINFO.EXE)
rem  (NB: Or get this number with the command FINDPART TABLES)
rem  Next is the hash number of the source file, an 8-digit number
rem  (To find this number: FINDPART PUTSECT GETHASH FILENAME.TYP)
rem  (Or HASH can be entered as 00000000 if FORCE added to command)

rem  *** Identify the number of Cylinders on the Disk ***
rem  **  Identifies CHS values for ALL disks present   **
rem  Display result on screen -
:: PARTINFO
:: FINDPART TABLES
rem  Save result to file -
:: PARTINFO > F:\PARTINFO.txt
:: FINDPART TABLES > F:\TABLES.txt

rem  Notes:
rem  The PUTSECT function can only write a 512 byte file, but -
rem  1. The program MBRutilD.exe can save and restore the entire
rem     TRACK 0 (CHS 0-0-1 to 0-0-63), but ONLY for Disk 1
rem  2. The program SRCFAT.COM can save and restore an entire FAT


rem  *** Display the Help screen ***
:: FINDPART PUTSECT /?

rem  *** Save the Help screen to a file ***
:: FINDPART PUTSECT /? > F:\PUTSECT.TXT

rem  *** Set Environment Variable ***
rem  NB: All PUTSECT operations will FAIL if this is not set!
:: SET FINDPART=EDIT
  

rem                              DISK 1
rem                              ======

rem                     [____ cylinders (decimal)]


rem  NON-DOS PARTITION (Track Zero)
rem  =================

rem  *** Write Sector 0-0-1 (MBR Sector) ***
:: FINDPART PUTSECT 1 0 0 1 F:\0-0-1.D1 ____ 00000000 FORCE

rem  *** Write Sector 0-0-9 (Backup MBR Sector) ***
rem  NB: Write this to CHS 0-0-1 instead if MBR is corrupted
:: FINDPART PUTSECT 1 0 0 9 F:\0-0-9.D1 ____ 00000000 FORCE

rem  Note:
rem  Track 0 is usually *empty* except for CHS 0-0-1 and 0-0-9

rem  MBRUtil Copyright (c) 2002 PowerQuest Corporation
rem   MBRutilD.exe [/?] [/S[H]=filename] [/R[H]=filename]
rem       /S   Save MBR (sector 1 only) to filename
rem       /SH  Save entire first head to filename
rem       /R   Restore MBR (sector 1 only) from filename
rem       /RH  Restore entire first head from filename
:: MBRUtilD.exe /RH=F:\0-0-1-63.D1


rem  PRIMARY PARTITION
rem  =================

rem  *** Write Sector 0-1-1 (Boot Sector) ***
:: FINDPART PUTSECT 1 0 1 1 F:\0-1-1.D1 ____ 00000000 FORCE

rem  *** Write Sector 0-1-2 (FS Info Sector) ***
:: FINDPART PUTSECT 1 0 1 2 F:\0-1-2.D1 ____ 00000000 FORCE

rem  *** Write Sector 0-1-3 (Boot Data Sector) ***
:: FINDPART PUTSECT 1 0 1 3 F:\0-1-3.D1 ____ 00000000 FORCE

rem  *** Write Sector 0-1-7 (Backup Boot Sector) ***
:: FINDPART PUTSECT 1 0 1 7 F:\0-1-1.D1 ____ 00000000 FORCE

rem  *** Write Sector 0-1-8 (Backup FS Info Sector) ***
:: FINDPART PUTSECT 1 0 1 8 F:\0-1-2.D1 ____ 00000000 FORCE

rem  *** Write Sector 0-1-9 (Backup Boot Data Sector) ***
:: FINDPART PUTSECT 1 0 1 9 F:\0-1-3.D1 ____ 00000000 FORCE

rem  *** Write all zero's to a sector ***
rem   ** This command replaces the filename with a special value **
rem      Most other sectors in Track 0 and in the first 33 sectors
rem      of each Partition are empty, i.e. filled with zero's, and may
rem      need to be set to zero if overwritten with garbage by a crash
:: FINDPART PUTSECT 1 _____ ___ __ !zero ____ 00000000 FORCE


rem  EXTENDED PARTITION
rem  ==================

rem  1st Logical Partition -

rem  *** Write Boot Sector ***
rem   ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART PUTSECT 1 _____ 1 1 F:\L1_1st.D1 ____ 00000000 FORCE

rem  *** Write FS Info Sector ***
rem   ** User must insert CHS value of 2nd sector of this Partition **
:: FINDPART PUTSECT 1 _____ 1 2 F:\L1_2nd.D1 ____ 00000000 FORCE

rem  *** Write Boot Data Sector ***
rem   ** User must insert CHS value of 3rd sector of this Partition **
:: FINDPART PUTSECT 1 _____ 1 3 F:\L1_3rd.D1 ____ 00000000 FORCE

rem  *** Write Backup Boot Sector ***
rem   ** User must insert CHS value of 7th sector of this Partition **
:: FINDPART PUTSECT 1 _____ 1 7 F:\L1_1st.D1 ____ 00000000 FORCE

rem  *** Write Backup FS Info Sector ***
rem   ** User must insert CHS value of 8th sector of this Partition **
:: FINDPART PUTSECT 1 _____ 1 8 F:\L1_2nd.D1 ____ 00000000 FORCE

rem  *** Write Backup Boot Data Sector ***
rem   ** User must insert CHS value of 9th sector of this Partition **
:: FINDPART PUTSECT 1 _____ 1 9 F:\L1_3rd.D1 ____ 00000000 FORCE

rem  *** Write all zero's to a sector ***
rem  ** This command replaces the filename with a special value **
:: FINDPART PUTSECT 1 _____ ___ __ !zero ____ 00000000 FORCE


rem  2nd Logical Partition -

rem  *** Write Boot Sector ***
rem   ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART PUTSECT 1 _____ 1 1 F:\L2_1st.D1 ____ 00000000 FORCE

rem  *** Write FS Info Sector ***
rem   ** User must insert CHS value of 2nd sector of this Partition **
:: FINDPART PUTSECT 1 _____ 1 2 F:\L2_2nd.D1 ____ 00000000 FORCE

rem  *** Write Boot Data Sector ***
rem   ** User must insert CHS value of 3rd sector of this Partition **
:: FINDPART PUTSECT 1 _____ 1 3 F:\L2_3rd.D1 ____ 00000000 FORCE

rem  *** Write Backup Boot Sector ***
rem   ** User must insert CHS value of 7th sector of this Partition **
:: FINDPART PUTSECT 1 _____ 1 7 F:\L2_1st.D1 ____ 00000000 FORCE

rem  *** Write Backup FS Info Sector ***
rem   ** User must insert CHS value of 8th sector of this Partition **
:: FINDPART PUTSECT 1 _____ 1 8 F:\L2_2nd.D1 ____ 00000000 FORCE

rem  *** Write Backup Boot Data Sector ***
rem   ** User must insert CHS value of 9th sector of this Partition **
:: FINDPART PUTSECT 1 _____ 1 9 F:\L2_3rd.D1 ____ 00000000 FORCE

rem  *** Write all zero's to a sector ***
rem  ** This command replaces the filename with a special value **
:: FINDPART PUTSECT 1 _____ ___ __ !zero ____ 00000000 FORCE


rem  3rd Logical Partition -

rem  *** Write Boot Sector ***
rem   ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART PUTSECT 1 _____ 1 1 F:\L3_1st.D1 ____ 00000000 FORCE

rem  *** Write FS Info Sector ***
rem   ** User must insert CHS value of 2nd sector of this Partition **
:: FINDPART PUTSECT 1 _____ 1 2 F:\L3_2nd.D1 ____ 00000000 FORCE

rem  *** Write Boot Data Sector ***
rem   ** User must insert CHS value of 3rd sector of this Partition **
:: FINDPART PUTSECT 1 _____ 1 3 F:\L3_3rd.D1 ____ 00000000 FORCE

rem  *** Write Backup Boot Sector ***
rem   ** User must insert CHS value of 7th sector of this Partition **
:: FINDPART PUTSECT 1 _____ 1 7 F:\L3_1st.D1 ____ 00000000 FORCE

rem  *** Write Backup FS Info Sector ***
rem   ** User must insert CHS value of 8th sector of this Partition **
:: FINDPART PUTSECT 1 _____ 1 8 F:\L3_2nd.D1 ____ 00000000 FORCE

rem  *** Write Backup Boot Data Sector ***
rem   ** User must insert CHS value of 9th sector of this Partition **
:: FINDPART PUTSECT 1 _____ 1 9 F:\L3_3rd.D1 ____ 00000000 FORCE

rem  *** Write all zero's to a sector ***
rem  ** This command replaces the filename with a special value **
:: FINDPART PUTSECT 1 _____ ___ __ !zero ____ 00000000 FORCE


rem                              DISK 2
rem                              ======

rem                     [____ cylinders (decimal)]


rem  NON-DOS PARTITION (Track Zero)
rem  =================

rem  *** Write Sector 0-0-1 (MBR Sector) ***
:: FINDPART PUTSECT 2 0 0 1 F:\0-0-1.D2 ____ 00000000 FORCE

rem  *** Write Sector 0-0-9 (Backup MBR Sector) ***
rem  NB: Write this to CHS 0-0-1 instead if MBR is corrupted
:: FINDPART PUTSECT 2 0 0 9 F:\0-0-9.D2 ____ 00000000 FORCE

rem  Note:
rem  Track 0 is usually *empty* except for CHS 0-0-1 and 0-0-9


rem  PRIMARY PARTITION
rem  =================

rem  *** Write Sector 0-1-1 (Boot Sector) ***
:: FINDPART PUTSECT 2 0 1 1 F:\0-1-1.D2 ____ 00000000 FORCE

rem  *** Write Sector 0-1-2 (FS Info Sector) ***
:: FINDPART PUTSECT 2 0 1 2 F:\0-1-2.D2 ____ 00000000 FORCE

rem  *** Write Sector 0-1-3 (Boot Data Sector) ***
:: FINDPART PUTSECT 2 0 1 3 F:\0-1-3.D2 ____ 00000000 FORCE

rem  *** Write Sector 0-1-7 (Backup Boot Sector) ***
:: FINDPART PUTSECT 2 0 1 7 F:\0-1-1.D2 ____ 00000000 FORCE

rem  *** Write Sector 0-1-8 (Backup FS Info Sector) ***
:: FINDPART PUTSECT 2 0 1 8 F:\0-1-2.D2 ____ 00000000 FORCE

rem  *** Write Sector 0-1-9 (Backup Boot Data Sector) ***
:: FINDPART PUTSECT 2 0 1 9 F:\0-1-3.D2 ____ 00000000 FORCE

rem  *** Write all zero's to a sector ***
rem   ** This command replaces the filename with a special value **
rem      Most other sectors in Track 0 and in the first 33 sectors
rem      of each Partition are empty, i.e. filled with zero's, and may
rem      need to be set to zero if overwritten with garbage by a crash
:: FINDPART PUTSECT 2 _____ ___ __ !zero ____ 00000000 FORCE


rem  EXTENDED PARTITION
rem  ==================

rem  1st Logical Partition -

rem  *** Write Boot Sector ***
rem   ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART PUTSECT 2 _____ 1 1 F:\L1_1st.D2 ____ 00000000 FORCE

rem  *** Write FS Info Sector ***
rem   ** User must insert CHS value of 2nd sector of this Partition **
:: FINDPART PUTSECT 2 _____ 1 2 F:\L1_2nd.D2 ____ 00000000 FORCE

rem  *** Write Boot Data Sector ***
rem   ** User must insert CHS value of 3rd sector of this Partition **
:: FINDPART PUTSECT 2 _____ 1 3 F:\L1_3rd.D2 ____ 00000000 FORCE

rem  *** Write Backup Boot Sector ***
rem   ** User must insert CHS value of 7th sector of this Partition **
:: FINDPART PUTSECT 2 _____ 1 7 F:\L1_1st.D2 ____ 00000000 FORCE

rem  *** Write Backup FS Info Sector ***
rem   ** User must insert CHS value of 8th sector of this Partition **
:: FINDPART PUTSECT 2 _____ 1 8 F:\L1_2nd.D2 ____ 00000000 FORCE

rem  *** Write Backup Boot Data Sector ***
rem   ** User must insert CHS value of 9th sector of this Partition **
:: FINDPART PUTSECT 2 _____ 1 9 F:\L1_3rd.D2 ____ 00000000 FORCE

rem  *** Write all zero's to a sector ***
rem  ** This command replaces the filename with a special value **
:: FINDPART PUTSECT 2 _____ ___ __ !zero ____ 00000000 FORCE


rem  2nd Logical Partition -

rem  *** Write Boot Sector ***
rem   ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART PUTSECT 2 _____ 1 1 F:\L2_1st.D2 ____ 00000000 FORCE

rem  *** Write FS Info Sector ***
rem   ** User must insert CHS value of 2nd sector of this Partition **
:: FINDPART PUTSECT 2 _____ 1 2 F:\L2_2nd.D2 ____ 00000000 FORCE

rem  *** Write Boot Data Sector ***
rem   ** User must insert CHS value of 3rd sector of this Partition **
:: FINDPART PUTSECT 2 _____ 1 3 F:\L2_3rd.D2 ____ 00000000 FORCE

rem  *** Write Backup Boot Sector ***
rem   ** User must insert CHS value of 7th sector of this Partition **
:: FINDPART PUTSECT 2 _____ 1 7 F:\L2_1st.D2 ____ 00000000 FORCE

rem  *** Write Backup FS Info Sector ***
rem   ** User must insert CHS value of 8th sector of this Partition **
:: FINDPART PUTSECT 2 _____ 1 8 F:\L2_2nd.D2 ____ 00000000 FORCE

rem  *** Write Backup Boot Data Sector ***
rem   ** User must insert CHS value of 9th sector of this Partition **
:: FINDPART PUTSECT 2 _____ 1 9 F:\L2_3rd.D2 ____ 00000000 FORCE

rem  *** Write all zero's to a sector ***
rem  ** This command replaces the filename with a special value **
:: FINDPART PUTSECT 2 _____ ___ __ !zero ____ 00000000 FORCE


rem  3rd Logical Partition -

rem  *** Write Boot Sector ***
rem   ** User must insert CHS value of 1st sector of this Partition **
:: FINDPART PUTSECT 2 _____ 1 1 F:\L3_1st.D2 ____ 00000000 FORCE

rem  *** Write FS Info Sector ***
rem   ** User must insert CHS value of 2nd sector of this Partition **
:: FINDPART PUTSECT 2 _____ 1 2 F:\L3_2nd.D2 ____ 00000000 FORCE

rem  *** Write Boot Data Sector ***
rem   ** User must insert CHS value of 3rd sector of this Partition **
:: FINDPART PUTSECT 2 _____ 1 3 F:\L3_3rd.D2 ____ 00000000 FORCE

rem  *** Write Backup Boot Sector ***
rem   ** User must insert CHS value of 7th sector of this Partition **
:: FINDPART PUTSECT 2 _____ 1 7 F:\L3_1st.D2 ____ 00000000 FORCE

rem  *** Write Backup FS Info Sector ***
rem   ** User must insert CHS value of 8th sector of this Partition **
:: FINDPART PUTSECT 2 _____ 1 8 F:\L3_2nd.D2 ____ 00000000 FORCE

rem  *** Write Backup Boot Data Sector ***
rem   ** User must insert CHS value of 9th sector of this Partition **
:: FINDPART PUTSECT 2 _____ 1 9 F:\L3_3rd.D2 ____ 00000000 FORCE

rem  *** Write all zero's to a sector ***
rem  ** This command replaces the filename with a special value **
:: FINDPART PUTSECT 2 _____ ___ __ !zero ____ 00000000 FORCE


rem  UTILITIES FOR WRITING MULTIPLE SECTORS
rem  ======================================
rem  
rem  SYNTAX of MBRUTILD -
rem  
rem  PowerQuest's MBR Utility for DOS
rem  Backup and restore MBR Sector & Track 0 on Disk 1
rem  
rem  The program only works on Disk 1, not on Disks 2 or 3.
rem  
rem  Saves and restores the entire Track 0 (CHS 0-0-1 to 0-0-63)
rem  (i.e. all 63 sectors at once). This is the DOS version of
rem  the MBR manager program: MBRutil.exe.
rem  
rem  It might be made to work on *any* Hard Disk, by setting the
rem  disk as Primary Master on the IDE cables. But that might be
rem  impractical because the disk to be restored will inevitably
rem  be damaged and not bootable.


rem  ** Save the MBR (Sector 0-0-1) to a file **
:: MBRutilD /S=F:\MBR_MBR.D1

rem  ** Restore the MBR (Sector 0-0-1) from a file **
:: MBRutilD /R=F:\MBR_MBR.D1


rem  ** Save the entire first Track to a file **
rem  (Save sectors 0-0-1 to 0-0-63: all 63 sectors of Track 0)
:: MBRutilD /SH=F:\MBR_TRK1.D1

rem  ** Restore the entire first Track from a file **
rem  (Restore sectors 0-0-1 to 0-0-63 from a backup file)
:: MBRutilD /RH=F:\MBR_TRK1.D1


::  /--------------------------------------------------------------------/  ::


::                           MBRSCAN RESULTS
::                           ===============

::  A damaged MBR sector can be repaired manually from these backup copies,
::  using a DISK SECTOR EDITOR (below).
::  
::  NB: The MBR sector of a HDD is unique, so CANNOT be copied to any other!
::      (See http://thestarman.pcministry.com/asm/mbr/mystery.htm#COPY)
::      [But see "Mystery Bytes" section (below), for further information]

::  Note:
::  In addition to the MBR, this program also saves a copy of the boot sector
::  from every partition on the disk; but not the other sectors making up the
::  FAT32 boot record (i.e. not the FS Info sector, nor the Boot Code sector)


::  TINY PC, Current Boot Disk
::  Western Digital 80GB WD800JB
::  2 partitions: #1 = Primary DOS (1 x 10 GB) (C:) (Bootable: WinME)
::                #2 = Logical 1   (1 x 66 GB) (E:) (Data)
::  
::  Non-DOS, Track 0 : Begins at CHS    0-0-1 (LBA 0)          (Partition Table)
::  Primary DOS (C:) : Begins at CHS    0-1-1 (LBA 63)         (Boot Sector) (PT+63)
::  Extended Partitn : Begins at CHS 1275-0-1 (LBA 20,482,875) (Partition Table)
::  1st Logical (E:) : Begins at CHS 1275-1-1 (LBA 20,482,938) (Boot Sector) (PT+63)
::  
::  MBRSCAN v1.1 Copyright (C) 1995,1999 by Nobumichi Kozawa
::  LBA mode
::  
::  1 - Master Boot Record (00000000h) : LBA 0
::  0000:  33 C0 8E D0 BC 00 7C FB-50 07 50 1F FC BE 1B 7C   [ 3��м |�P P �� | ]
::  0010:  BF 1B 06 50 57 B9 E5 01-F3 A4 CB BE BE 07 B1 04   [ �  PW�� �˾� �  ]
::  0020:  38 2C 7C 09 75 15 83 C6-10 E2 F5 CD 18 8B 14 8B   [ 8,| u �� ��� � � ]
::  0030:  EE 83 C6 10 49 74 16 38-2C 74 F6 BE 10 07 4E AC   [ �� It 8,t��  N� ]
::  0040:  3C 00 74 FA BB 07 00 B4-0E CD 10 EB F2 89 46 25   [ < t��  � � ��F% ]
::  0050:  96 8A 46 04 B4 06 3C 0E-74 11 B4 0B 3C 0C 74 05   [ -�F � < t � < t  ]
::  0060:  3A C4 75 2B 40 C6 46 25-06 75 24 BB AA 55 50 B4   [ :�u+@�F% u$��UP� ]
::  0070:  41 CD 13 58 72 16 81 FB-55 AA 75 10 F6 C1 01 74   [ A� Xr ��U�u �� t ]
::  0080:  0B 8A E0 88 56 24 C7 06-A1 06 EB 1E 88 66 04 BF   [  ���V$� � � �f � ]
::  0090:  0A 00 B8 01 02 8B DC 33-C9 83 FF 05 7F 03 8B 4E   [   �  ��3Ƀ�  �N ]
::  00A0:  25 03 4E 02 CD 13 72 29-BE 46 07 81 3E FE 7D 55   [ % N � r)�F �>�}U ]
::  00B0:  AA 74 5A 83 EF 05 7F DA-85 F6 75 83 BE 27 07 EB   [ �tZ�� څ�u��' � ]
::  00C0:  8A 98 91 52 99 03 46 08-13 56 0A E8 12 00 5A EB   [ ���R� F  V �  Z� ]
::  00D0:  D5 4F 74 E4 33 C0 CD 13-EB B8 00 00 00 00 00 00   [ �Ot�3�� �       ]
::  00E0:  56 33 F6 56 56 52 50 06-53 51 BE 10 00 56 8B F4   [ V3�VVRP SQ�  V�� ]
::  00F0:  50 52 B8 00 42 8A 56 24-CD 13 5A 58 8D 64 10 72   [ PR� B�V$� ZX�d r ]
::  0100:  0A 40 75 01 42 80 C7 02-E2 F7 F8 5E C3 EB 74 49   [  @u B�� ���^��tI ]
::  0110:  6E 76 61 6C 69 64 20 70-61 72 74 69 74 69 6F 6E   [ nvalid partition ]
::  0120:  20 74 61 62 6C 65 00 45-72 72 6F 72 20 6C 6F 61   [  table Error loa ]
::  0130:  64 69 6E 67 20 6F 70 65-72 61 74 69 6E 67 20 73   [ ding operating s ]
::  0140:  79 73 74 65 6D 00 4D 69-73 73 69 6E 67 20 6F 70   [ ystem Missing op ]
::  0150:  65 72 61 74 69 6E 67 20-73 79 73 74 65 6D 00 00   [ erating system   ]
::  0160:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0170:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0180:  00 00 00 8B FC 1E 57 8B-F5 CB 00 00 00 00 00 00   [    �� W���       ]
::  0190:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01A0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01B0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 80 01   [               �  ]
::  01C0:  01 00 0C FE 3F FA 3F 00-00 00 FC 8A 38 01 00 00   [    �?�?   ��8    ]
::  01D0:  01 FB 0F FE BF 00 3B 8B-38 01 86 59 18 08 00 00   [  � �� ;�8 �Y     ]
::  01E0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01F0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 55 AA   [               U� ]
::  
::  1 - Partition table entry = 0  << Win95 FAT32 (LBA) >>   : Disk 1, Primary Partition
::  01BE:  80 01 01 00 0C FE 3F FA-3F 00 00 00 FC 8A 38 01   [ �    �?�?   ��8  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  80        STATUS:                Active
::     +1  01 01 00  START CYL-HEAD-SECTOR: 000h-01h-01h     : Start = CHS 0-1-1
::     +4  0C        PARTITION ID:          Win95 FAT32 (LBA): Partition Type 0C
::     +5  FE 3F FA  END CYL-HEAD-SECTOR:   0FAh-FEh-3Fh     : End = CHS 250-254-63 (False)
::     +8  0000003F  START SECTOR:          63               : Start = LBA 63
::     +C  01388AFC  NUMBER OF SECTORS:     20482812         : Size (sectors) = 20,482,812
::  
::  1-0 Win95 FAT32 (LBA) Boot Record (0000003Fh)            : Boot Sector (LBA 63)
::  0000:  EB 58 90 4D 53 57 49 4E-34 2E 31 00 02 10 20 00   [ �X�MSWIN4.1      ]
::  0010:  02 00 00 00 00 F8 00 00-3F 00 FF 00 3F 00 00 00   [      �  ? � ?    ]
::  0020:  FC 8A 38 01 08 27 00 00-00 00 00 00 02 00 00 00   [ ��8  '           ]
::  0030:  00 00 06 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0040:  80 00 29 DF 0D 00 00 44-52 49 56 45 20 43 20 20   [ � )�   DRIVE C   ]
::  0050:  20 20 46 41 54 33 32 20-20 20 FA 33 C9 8E D1 BC   [   FAT32   �3ɎѼ ]
::  0060:  F8 7B 8E C1 BD 78 00 C5-76 00 1E 56 16 55 BF 22   [ �{���x �v  V U�" ]
::  0070:  05 89 7E 00 89 4E 02 B1-0B FC F3 A4 8E D9 BD 00   [  �~ �N � ��ٽ  ]
::  0080:  7C C6 45 FE 0F 8B 46 18-88 45 F9 38 4E 40 7D 25   [ |�E� �F �E�8N@}% ]
::  0090:  8B C1 99 BB 00 07 E8 97-00 72 1A 83 EB 3A 66 A1   [ ����  �- r ��:f� ]
::  00A0:  1C 7C 66 3B 07 8A 57 FC-75 06 80 CA 02 88 56 02   [  |f; �W�u �� �V  ]
::  00B0:  80 C3 10 73 ED BF 02 00-83 7E 16 00 75 45 8B 46   [ �� s��  �~  uE�F ]
::  00C0:  1C 8B 56 1E B9 03 00 49-40 75 01 42 BB 00 7E E8   [  �V �  I@u B� ~� ]
::  00D0:  5F 00 73 26 B0 F8 4F 74-1D 8B 46 32 33 D2 B9 03   [ _ s&��Ot �F23ҹ  ]
::  00E0:  00 3B C8 77 1E 8B 76 0E-3B CE 73 17 2B F1 03 46   [  ;�w �v ;�s +� F ]
::  00F0:  1C 13 56 1E EB D1 73 0B-EB 27 83 7E 2A 00 77 03   [   V ��s �'�~* w  ]
::  0100:  E9 FD 02 BE 7E 7D AC 98-03 F0 AC 84 C0 74 17 3C   [ �� �~}�� ��t < ]
::  0110:  FF 74 09 B4 0E BB 07 00-CD 10 EB EE BE 81 7D EB   [ �t � �  � �}� ]
::  0120:  E5 BE 7F 7D EB E0 98 CD-16 5E 1F 66 8F 04 CD 19   [ �}���� ^ f� �  ]
::  0130:  41 56 66 6A 00 52 50 06-53 6A 01 6A 10 8B F4 60   [ AVfj RP Sj j ��` ]
::  0140:  80 7E 02 0E 75 04 B4 42-EB 1D 91 92 33 D2 F7 76   [ �~  u �B� ��3��v ]
::  0150:  18 91 F7 76 18 42 87 CA-F7 76 1A 8A F2 8A E8 C0   [  ��v B���v ���� ]
::  0160:  CC 02 0A CC B8 01 02 8A-56 40 CD 13 61 8D 64 10   [ �  ̸  �V@� a�d  ]
::  0170:  5E 72 0A 40 75 01 42 03-5E 0B 49 75 B4 C3 03 18   [ ^r @u B ^ Iu��   ]
::  0180:  01 27 0D 0A 4E 6F 20 4F-53 20 46 6F 75 6E 64 20   [  '  No OS Found  ]
::  0190:  20 20 20 20 20 20 20 FF-0D 0A 44 69 73 6B 20 49   [        �  Disk I ]
::  01A0:  2F 4F 20 45 72 72 6F 72-FF 0D 0A 49 6E 73 65 72   [ /O Error�  Inser ]
::  01B0:  74 20 4F 53 20 73 65 74-75 70 20 64 69 73 6B 2C   [ t OS setup disk, ]
::  01C0:  20 74 68 65 6E 20 70 72-65 73 73 20 61 6E 79 20   [  then press any  ]
::  01D0:  6B 65 79 0D 0A 00 00 00-49 4F 20 20 20 20 20 20   [ key     IO       ]
::  01E0:  53 59 53 4D 53 44 4F 53-20 20 20 53 59 53 7E 01   [ SYSMSDOS   SYS~  ]
::  01F0:  00 57 49 4E 42 4F 4F 54-20 53 59 53 00 00 55 AA   [  WINBOOT SYS  U� ]
::  
::  1 - Partition table entry = 1  << Win95 Extended >>      : Disk 1, Logical Partition 1
::  01CE:  00 00 01 FB 0F FE BF 00-3B 8B 38 01 86 59 18 08   [    � �� ;�8 �Y   ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive         : Not Bootable
::     +1  00 01 FB  START CYL-HEAD-SECTOR: 0FBh-00h-01h     : Start = CHS 251-0-1 (False)
::     +4  0F        PARTITION ID:          Win95 Extended   : Partition Type 0F (Extended)
::     +5  FE BF 00  END CYL-HEAD-SECTOR:   200h-FEh-3Fh     : End = CHS 512-254-63 (False)
::     +8  01388B3B  START SECTOR:          20482875         : Start = LBA 20,482,875
::     +C  08185986  NUMBER OF SECTORS:     135813510        : Size (sectors) = 135,813,510
::  
::  1 - Partition table entry = 2  << Empty >>
::  01DE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  1 - Partition table entry = 3  << Empty >>
::  01EE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  2 - Win95 Extended (01388B3Bh) (Partition Table Entry: 1-1) : LBA 20,482,875 (Ptn Table)
::  0000:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0010:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0020:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0030:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0040:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0050:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0060:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0070:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0080:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0090:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00A0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00B0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00C0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00D0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00E0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00F0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0100:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0110:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0120:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0130:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0140:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0150:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0160:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0170:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0180:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0190:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01A0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01B0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 01   [                  ]
::  01C0:  01 FB 0B FE BF 00 3F 00-00 00 47 59 18 08 00 00   [  � �� ?   GY     ]
::  01D0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01E0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01F0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 55 AA   [               U� ]
::  
::  2 - Partition table entry = 0  << Win95 FAT32 >>
::  01BE:  00 01 01 FB 0B FE BF 00-3F 00 00 00 47 59 18 08   [    � �� ?   GY   ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive         : Not Bootable
::     +1  01 01 FB  START CYL-HEAD-SECTOR: 0FBh-01h-01h     : Start = CHS 251-1-1 (False)
::     +4  0B        PARTITION ID:          Win95 FAT32      : Partition Type 0B (Logical)
::     +5  FE BF 00  END CYL-HEAD-SECTOR:   200h-FEh-3Fh     : End = CHS 512-254-63 (False)
::     +8  0000003F  START SECTOR:          63               : Start = LBA 63 [See note]
::     +C  08185947  NUMBER OF SECTORS:     135813447        : Size (Sectors) = 135,813,447
::  
::                                                           Note - This is the offset
::                                                           from the start of the EXTENDED
::                                                           partition, *not* from the MBR!
::  
::  2-0 Win95 FAT32 Boot Record (01388B7Ah)                  : LBA 20,482,938 (Boot Sector)
::  0000:  EB 58 90 4D 53 57 49 4E-34 2E 31 00 02 40 20 00   [ �X�MSWIN4.1  @   ]
::  0010:  02 00 00 00 00 F8 00 00-3F 00 FF 00 7A 8B 38 01   [      �  ? � z�8  ]
::  0020:  47 59 18 08 C1 40 00 00-00 00 00 00 02 00 00 00   [ GY  �@           ]
::  0030:  01 00 06 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0040:  80 00 29 FC 15 58 23 44-41 54 41 20 20 20 20 20   [ � )� X#DATA      ]
::  0050:  20 20 46 41 54 33 32 20-20 20 FA 33 C9 8E D1 BC   [   FAT32   �3ɎѼ ]
::  0060:  F8 7B 8E C1 BD 78 00 C5-76 00 1E 56 16 55 BF 22   [ �{���x �v  V U�" ]
::  0070:  05 89 7E 00 89 4E 02 B1-0B FC F3 A4 8E D9 BD 00   [  �~ �N � ��ٽ  ]
::  0080:  7C C6 45 FE 0F 8B 46 18-88 45 F9 38 4E 40 7D 25   [ |�E� �F �E�8N@}% ]
::  0090:  8B C1 99 BB 00 07 E8 97-00 72 1A 83 EB 3A 66 A1   [ ����  �- r ��:f� ]
::  00A0:  1C 7C 66 3B 07 8A 57 FC-75 06 80 CA 02 88 56 02   [  |f; �W�u �� �V  ]
::  00B0:  80 C3 10 73 ED BF 02 00-83 7E 16 00 75 45 8B 46   [ �� s��  �~  uE�F ]
::  00C0:  1C 8B 56 1E B9 03 00 49-40 75 01 42 BB 00 7E E8   [  �V �  I@u B� ~� ]
::  00D0:  5F 00 73 26 B0 F8 4F 74-1D 8B 46 32 33 D2 B9 03   [ _ s&��Ot �F23ҹ  ]
::  00E0:  00 3B C8 77 1E 8B 76 0E-3B CE 73 17 2B F1 03 46   [  ;�w �v ;�s +� F ]
::  00F0:  1C 13 56 1E EB D1 73 0B-EB 27 83 7E 2A 00 77 03   [   V ��s �'�~* w  ]
::  0100:  E9 FD 02 BE 7E 7D AC 98-03 F0 AC 84 C0 74 17 3C   [ �� �~}�� ��t < ]
::  0110:  FF 74 09 B4 0E BB 07 00-CD 10 EB EE BE 81 7D EB   [ �t � �  � �}� ]
::  0120:  E5 BE 7F 7D EB E0 98 CD-16 5E 1F 66 8F 04 CD 19   [ �}���� ^ f� �  ]
::  0130:  41 56 66 6A 00 52 50 06-53 6A 01 6A 10 8B F4 60   [ AVfj RP Sj j ��` ]
::  0140:  80 7E 02 0E 75 04 B4 42-EB 1D 91 92 33 D2 F7 76   [ �~  u �B� ��3��v ]
::  0150:  18 91 F7 76 18 42 87 CA-F7 76 1A 8A F2 8A E8 C0   [  ��v B���v ���� ]
::  0160:  CC 02 0A CC B8 01 02 8A-56 40 CD 13 61 8D 64 10   [ �  ̸  �V@� a�d  ]
::  0170:  5E 72 0A 40 75 01 42 03-5E 0B 49 75 B4 C3 03 18   [ ^r @u B ^ Iu��   ]
::  0180:  01 27 0D 0A 49 6E 76 61-6C 69 64 20 73 79 73 74   [  '  Invalid syst ]
::  0190:  65 6D 20 64 69 73 6B FF-0D 0A 44 69 73 6B 20 49   [ em disk�  Disk I ]
::  01A0:  2F 4F 20 65 72 72 6F 72-FF 0D 0A 52 65 70 6C 61   [ /O error�  Repla ]
::  01B0:  63 65 20 74 68 65 20 64-69 73 6B 2C 20 61 6E 64   [ ce the disk, and ]
::  01C0:  20 74 68 65 6E 20 70 72-65 73 73 20 61 6E 79 20   [  then press any  ]
::  01D0:  6B 65 79 0D 0A 00 00 00-49 4F 20 20 20 20 20 20   [ key     IO       ]
::  01E0:  53 59 53 4D 53 44 4F 53-20 20 20 53 59 53 7E 01   [ SYSMSDOS   SYS~  ]
::  01F0:  00 57 49 4E 42 4F 4F 54-20 53 59 53 00 00 55 AA   [  WINBOOT SYS  U� ]
::  
::  2 - Partition table entry = 1  << Empty >>
::  01CE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  2 - Partition table entry = 2  << Empty >>
::  01DE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  2 - Partition table entry = 3  << Empty >>
::  01EE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  
::  [ PARTITION MAP - LBA ]
::  
::            ABSOLUTE          PART-TABLE
::         START     END      START    BLOCKS                       START: LBA  END: LBA
::        ======== ========  ======== ========                      ==========  ===========
::  1-0 : 0000003F 01388B3A  0000003F 01388AFC  Win95 FAT32 (LBA) :         63   20,482,874
::  1-1 : 01388B3B 0950E4C0  01388B3B 08185986  Win95 Extended    : 20,482,875  156,296,384
::  2-0 : 01388B7A 0950E4C0  0000003F 08185947  Win95 FAT32       : 20,482,938  156,296,384


::  TINY PC, current Drive D:
::  Western Digital 80GB - DRIVE D:
::  
::  Non-DOS, Track 0 : Begins at CHS 0-0-1 (LBA 0)
::  Primary DOS (D:) : Begins at CHS 0-1-1 (LBA 63)
::  
::  MBRSCAN v1.1 Copyright (C) 1995,1999 by Nobumichi Kozawa
::  LBA mode
::  
::  1 - Master Boot Record (00000000h)
::  0000:  33 C0 8E D0 BC 00 7C FB-50 07 50 1F FC BE 1B 7C   [ 3��м |�P P �� | ]
::  0010:  BF 1B 06 50 57 B9 E5 01-F3 A4 CB BE BE 07 B1 04   [ �  PW�� �˾� �  ]
::  0020:  38 2C 7C 09 75 15 83 C6-10 E2 F5 CD 18 8B 14 8B   [ 8,| u �� ��� � � ]
::  0030:  EE 83 C6 10 49 74 16 38-2C 74 F6 BE 10 07 4E AC   [ �� It 8,t��  N� ]
::  0040:  3C 00 74 FA BB 07 00 B4-0E CD 10 EB F2 89 46 25   [ < t��  � � ��F% ]
::  0050:  96 8A 46 04 B4 06 3C 0E-74 11 B4 0B 3C 0C 74 05   [ -�F � < t � < t  ]
::  0060:  3A C4 75 2B 40 C6 46 25-06 75 24 BB AA 55 50 B4   [ :�u+@�F% u$��UP� ]
::  0070:  41 CD 13 58 72 16 81 FB-55 AA 75 10 F6 C1 01 74   [ A� Xr ��U�u �� t ]
::  0080:  0B 8A E0 88 56 24 C7 06-A1 06 EB 1E 88 66 04 BF   [  ���V$� � � �f � ]
::  0090:  0A 00 B8 01 02 8B DC 33-C9 83 FF 05 7F 03 8B 4E   [   �  ��3Ƀ�  �N ]
::  00A0:  25 03 4E 02 CD 13 72 29-BE 46 07 81 3E FE 7D 55   [ % N � r)�F �>�}U ]
::  00B0:  AA 74 5A 83 EF 05 7F DA-85 F6 75 83 BE 27 07 EB   [ �tZ�� څ�u��' � ]
::  00C0:  8A 98 91 52 99 03 46 08-13 56 0A E8 12 00 5A EB   [ ���R� F  V �  Z� ]
::  00D0:  D5 4F 74 E4 33 C0 CD 13-EB B8 00 00 81 25 16 04   [ �Ot�3�� �  �%   ]
::  00E0:  56 33 F6 56 56 52 50 06-53 51 BE 10 00 56 8B F4   [ V3�VVRP SQ�  V�� ]
::  00F0:  50 52 B8 00 42 8A 56 24-CD 13 5A 58 8D 64 10 72   [ PR� B�V$� ZX�d r ]
::  0100:  0A 40 75 01 42 80 C7 02-E2 F7 F8 5E C3 EB 74 49   [  @u B�� ���^��tI ]
::  0110:  6E 76 61 6C 69 64 20 70-61 72 74 69 74 69 6F 6E   [ nvalid partition ]
::  0120:  20 74 61 62 6C 65 00 45-72 72 6F 72 20 6C 6F 61   [  table Error loa ]
::  0130:  64 69 6E 67 20 6F 70 65-72 61 74 69 6E 67 20 73   [ ding operating s ]
::  0140:  79 73 74 65 6D 00 4D 69-73 73 69 6E 67 20 6F 70   [ ystem Missing op ]
::  0150:  65 72 61 74 69 6E 67 20-73 79 73 74 65 6D 00 00   [ erating system   ]
::  0160:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0170:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0180:  00 00 00 8B FC 1E 57 8B-F5 CB 00 00 00 00 00 00   [    �� W���       ]
::  0190:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01A0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01B0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 80 01   [               �  ]
::  01C0:  01 00 0C FE BF 00 3F 00-00 00 82 E4 50 09 00 00   [    �� ?   ��P    ]
::  01D0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01E0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01F0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 55 AA   [               U� ]
::  
::  1 - Partition table entry = 0  << Win95 FAT32 (LBA) >>
::  01BE:  80 01 01 00 0C FE BF 00-3F 00 00 00 82 E4 50 09   [ �    �� ?   ��P  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  80        STATUS:                Active
::     +1  01 01 00  START CYL-HEAD-SECTOR: 000h-01h-01h
::     +4  0C        PARTITION ID:          Win95 FAT32 (LBA)
::     +5  FE BF 00  END CYL-HEAD-SECTOR:   200h-FEh-3Fh
::     +8  0000003F  START SECTOR:          63
::     +C  0950E482  NUMBER OF SECTORS:     156296322
::  
::  1-0 Win95 FAT32 (LBA) Boot Record (0000003Fh)
::  0000:  EB 58 90 4D 53 57 49 4E-34 2E 31 00 02 40 20 00   [ �X�MSWIN4.1  @   ]
::  0010:  02 00 00 00 00 F8 00 00-3F 00 FF 00 3F 00 00 00   [      �  ? � ?    ]
::  0020:  82 E4 50 09 85 4A 00 00-00 00 00 00 02 00 00 00   [ ��P �J           ]
::  0030:  01 00 06 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0040:  80 00 29 10 0B 5C 35 4E-4F 20 4E 41 4D 45 20 20   [ � )  \5NO NAME   ]
::  0050:  20 20 46 41 54 33 32 20-20 20 FA 33 C9 8E D1 BC   [   FAT32   �3ɎѼ ]
::  0060:  F8 7B 8E C1 BD 78 00 C5-76 00 1E 56 16 55 BF 22   [ �{���x �v  V U�" ]
::  0070:  05 89 7E 00 89 4E 02 B1-0B FC F3 A4 8E D9 BD 00   [  �~ �N � ��ٽ  ]
::  0080:  7C C6 45 FE 0F 8B 46 18-88 45 F9 38 4E 40 7D 25   [ |�E� �F �E�8N@}% ]
::  0090:  8B C1 99 BB 00 07 E8 97-00 72 1A 83 EB 3A 66 A1   [ ����  �- r ��:f� ]
::  00A0:  1C 7C 66 3B 07 8A 57 FC-75 06 80 CA 02 88 56 02   [  |f; �W�u �� �V  ]
::  00B0:  80 C3 10 73 ED BF 02 00-83 7E 16 00 75 45 8B 46   [ �� s��  �~  uE�F ]
::  00C0:  1C 8B 56 1E B9 03 00 49-40 75 01 42 BB 00 7E E8   [  �V �  I@u B� ~� ]
::  00D0:  5F 00 73 26 B0 F8 4F 74-1D 8B 46 32 33 D2 B9 03   [ _ s&��Ot �F23ҹ  ]
::  00E0:  00 3B C8 77 1E 8B 76 0E-3B CE 73 17 2B F1 03 46   [  ;�w �v ;�s +� F ]
::  00F0:  1C 13 56 1E EB D1 73 0B-EB 27 83 7E 2A 00 77 03   [   V ��s �'�~* w  ]
::  0100:  E9 FD 02 BE 7E 7D AC 98-03 F0 AC 84 C0 74 17 3C   [ �� �~}�� ��t < ]
::  0110:  FF 74 09 B4 0E BB 07 00-CD 10 EB EE BE 81 7D EB   [ �t � �  � �}� ]
::  0120:  E5 BE 7F 7D EB E0 98 CD-16 5E 1F 66 8F 04 CD 19   [ �}���� ^ f� �  ]
::  0130:  41 56 66 6A 00 52 50 06-53 6A 01 6A 10 8B F4 60   [ AVfj RP Sj j ��` ]
::  0140:  80 7E 02 0E 75 04 B4 42-EB 1D 91 92 33 D2 F7 76   [ �~  u �B� ��3��v ]
::  0150:  18 91 F7 76 18 42 87 CA-F7 76 1A 8A F2 8A E8 C0   [  ��v B���v ���� ]
::  0160:  CC 02 0A CC B8 01 02 8A-56 40 CD 13 61 8D 64 10   [ �  ̸  �V@� a�d  ]
::  0170:  5E 72 0A 40 75 01 42 03-5E 0B 49 75 B4 C3 03 18   [ ^r @u B ^ Iu��   ]
::  0180:  01 27 0D 0A 49 6E 76 61-6C 69 64 20 73 79 73 74   [  '  Invalid syst ]
::  0190:  65 6D 20 64 69 73 6B FF-0D 0A 44 69 73 6B 20 49   [ em disk�  Disk I ]
::  01A0:  2F 4F 20 65 72 72 6F 72-FF 0D 0A 52 65 70 6C 61   [ /O error�  Repla ]
::  01B0:  63 65 20 74 68 65 20 64-69 73 6B 2C 20 61 6E 64   [ ce the disk, and ]
::  01C0:  20 74 68 65 6E 20 70 72-65 73 73 20 61 6E 79 20   [  then press any  ]
::  01D0:  6B 65 79 0D 0A 00 00 00-49 4F 20 20 20 20 20 20   [ key     IO       ]
::  01E0:  53 59 53 4D 53 44 4F 53-20 20 20 53 59 53 7E 01   [ SYSMSDOS   SYS~  ]
::  01F0:  00 57 49 4E 42 4F 4F 54-20 53 59 53 00 00 55 AA   [  WINBOOT SYS  U� ]


::  TINY PC, External USB Backup
::  Western Digital 120GB - External Enclosure USB
::  4 partitions:  Primary DOS (Bootable: WinME)
::                 Logical x 3
::  
::  Non-DOS, Track 0 : Begins at CHS     0-0-1 (LBA           0) Size:         63
::  Primary DOS (G:) : Begins at CHS     0-1-1 (LBA          63) Size: 33,142,032
::  Hidden Sectors   : Begins at CHS  2063-0-1 (LBA  33,142,095) Size:         63
::  1st Logical (H:) : Begins at CHS  2063-1-1 (LBA  33,142,158) Size: 67,103,442
::  Hidden Sectors   : Begins at CHS  6240-0-1 (LBA 100,245,600) Size:         63
::  2nd Logical (I:) : Begins at CHS  6240-1-1 (LBA 100,245,663) Size: 67,103,505
::  Hidden Sectors   : Begins at CHS 10417-1-1 (LBA 167,349,168) Size:         63
::  3rd Logical (J:) : Begins at CHS 10417-2-1 (LBA 167,349,231) Size: 67,103,442
::  
::  
::  MBRSCAN v1.1 Copyright (C) 1995,1999 by Nobumichi Kozawa
::  LBA mode
::  
::  1 - Master Boot Record (00000000h)                       : LBA 0
::  0000:  33 C0 8E D0 BC 00 7C FB-50 07 50 1F FC BE 1B 7C   [ 3��м |�P P �� | ]
::  0010:  BF 1B 06 50 57 B9 E5 01-F3 A4 CB BE BE 07 B1 04   [ �  PW�� �˾� �  ]
::  0020:  38 2C 7C 09 75 15 83 C6-10 E2 F5 CD 18 8B 14 8B   [ 8,| u �� ��� � � ]
::  0030:  EE 83 C6 10 49 74 16 38-2C 74 F6 BE 10 07 4E AC   [ �� It 8,t��  N� ]
::  0040:  3C 00 74 FA BB 07 00 B4-0E CD 10 EB F2 89 46 25   [ < t��  � � ��F% ]
::  0050:  96 8A 46 04 B4 06 3C 0E-74 11 B4 0B 3C 0C 74 05   [ -�F � < t � < t  ]
::  0060:  3A C4 75 2B 40 C6 46 25-06 75 24 BB AA 55 50 B4   [ :�u+@�F% u$��UP� ]
::  0070:  41 CD 13 58 72 16 81 FB-55 AA 75 10 F6 C1 01 74   [ A� Xr ��U�u �� t ]
::  0080:  0B 8A E0 88 56 24 C7 06-A1 06 EB 1E 88 66 04 BF   [  ���V$� � � �f � ]
::  0090:  0A 00 B8 01 02 8B DC 33-C9 83 FF 05 7F 03 8B 4E   [   �  ��3Ƀ�  �N ]
::  00A0:  25 03 4E 02 CD 13 72 29-BE 46 07 81 3E FE 7D 55   [ % N � r)�F �>�}U ]
::  00B0:  AA 74 5A 83 EF 05 7F DA-85 F6 75 83 BE 27 07 EB   [ �tZ�� څ�u��' � ]
::  00C0:  8A 98 91 52 99 03 46 08-13 56 0A E8 12 00 5A EB   [ ���R� F  V �  Z� ]
::  00D0:  D5 4F 74 E4 33 C0 CD 13-EB B8 00 00 80 09 53 08   [ �Ot�3�� �  � S  ]
::  00E0:  56 33 F6 56 56 52 50 06-53 51 BE 10 00 56 8B F4   [ V3�VVRP SQ�  V�� ]
::  00F0:  50 52 B8 00 42 8A 56 24-CD 13 5A 58 8D 64 10 72   [ PR� B�V$� ZX�d r ]
::  0100:  0A 40 75 01 42 80 C7 02-E2 F7 F8 5E C3 EB 74 49   [  @u B�� ���^��tI ]
::  0110:  6E 76 61 6C 69 64 20 70-61 72 74 69 74 69 6F 6E   [ nvalid partition ]
::  0120:  20 74 61 62 6C 65 00 45-72 72 6F 72 20 6C 6F 61   [  table Error loa ]
::  0130:  64 69 6E 67 20 6F 70 65-72 61 74 69 6E 67 20 73   [ ding operating s ]
::  0140:  79 73 74 65 6D 00 4D 69-73 73 69 6E 67 20 6F 70   [ ystem Missing op ]
::  0150:  65 72 61 74 69 6E 67 20-73 79 73 74 65 6D 00 00   [ erating system   ]
::  0160:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0170:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0180:  00 00 00 8B FC 1E 57 8B-F5 CB 00 00 00 00 00 00   [    �� W���       ]
::  0190:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01A0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01B0:  00 00 00 00 00 00 00 00-66 1F 67 1F 00 00 80 01   [         f g   �  ]
::  01C0:  01 00 0C FE 3F 0E 3F 00-00 00 10 B5 F9 01 00 00   [    �? ?    ��    ]
::  01D0:  01 0F 0F FE 7F 00 4F B5-F9 01 72 82 FF 0B 00 00   [    � O�� r��    ]
::  01E0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01F0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 55 AA   [               U� ]
::  
::  1 - Partition table entry = 0  << Win95 FAT32 (LBA) >>   : Entry No.1 (Defines current)
::  01BE:  80 01 01 00 0C FE 3F 0E-3F 00 00 00 10 B5 F9 01   [ �    �? ?    ��  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  80        STATUS:                Active
::     +1  01 01 00  START CYL-HEAD-SECTOR: 000h-01h-01h
::     +4  0C        PARTITION ID:          Win95 FAT32 (LBA): Type 0C = PRIMARY DOS
::     +5  FE 3F 0E  END CYL-HEAD-SECTOR:   00Eh-FEh-3Fh
::     +8  0000003F  START SECTOR:          63               : Start (Offset from MBR) = 63
::     +C  01F9B510  NUMBER OF SECTORS:     33142032         : Size (Sectors)  = 33,142,032
::  
::  1-0 Win95 FAT32 (LBA) Boot Record (0000003Fh)            : LBA 63 (Start Sector)
::  0000:  EB 58 90 4D 53 57 49 4E-34 2E 31 00 02 10 20 00   [ �X�MSWIN4.1      ]
::  0010:  02 00 00 00 00 F8 00 00-3F 00 FF 00 3F 00 00 00   [      �  ? � ?    ]
::  0020:  10 B5 F9 01 27 3F 00 00-00 00 00 00 02 00 00 00   [  �� '?           ]
::  0030:  00 00 06 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0040:  80 00 29 17 0E 00 00 31-32 30 47 42 20 44 49 53   [ � )    120GB DIS ]
::  0050:  4B 20 46 41 54 33 32 20-20 20 FA 33 C9 8E D1 BC   [ K FAT32   �3ɎѼ ]
::  0060:  F8 7B 8E C1 BD 78 00 C5-76 00 1E 56 16 55 BF 22   [ �{���x �v  V U�" ]
::  0070:  05 89 7E 00 89 4E 02 B1-0B FC F3 A4 8E D9 BD 00   [  �~ �N � ��ٽ  ]
::  0080:  7C C6 45 FE 0F 8B 46 18-88 45 F9 38 4E 40 7D 25   [ |�E� �F �E�8N@}% ]
::  0090:  8B C1 99 BB 00 07 E8 97-00 72 1A 83 EB 3A 66 A1   [ ����  �- r ��:f� ]
::  00A0:  1C 7C 66 3B 07 8A 57 FC-75 06 80 CA 02 88 56 02   [  |f; �W�u �� �V  ]
::  00B0:  80 C3 10 73 ED BF 02 00-83 7E 16 00 75 45 8B 46   [ �� s��  �~  uE�F ]
::  00C0:  1C 8B 56 1E B9 03 00 49-40 75 01 42 BB 00 7E E8   [  �V �  I@u B� ~� ]
::  00D0:  5F 00 73 26 B0 F8 4F 74-1D 8B 46 32 33 D2 B9 03   [ _ s&��Ot �F23ҹ  ]
::  00E0:  00 3B C8 77 1E 8B 76 0E-3B CE 73 17 2B F1 03 46   [  ;�w �v ;�s +� F ]
::  00F0:  1C 13 56 1E EB D1 73 0B-EB 27 83 7E 2A 00 77 03   [   V ��s �'�~* w  ]
::  0100:  E9 FD 02 BE 7E 7D AC 98-03 F0 AC 84 C0 74 17 3C   [ �� �~}�� ��t < ]
::  0110:  FF 74 09 B4 0E BB 07 00-CD 10 EB EE BE 81 7D EB   [ �t � �  � �}� ]
::  0120:  E5 BE 7F 7D EB E0 98 CD-16 5E 1F 66 8F 04 CD 19   [ �}���� ^ f� �  ]
::  0130:  41 56 66 6A 00 52 50 06-53 6A 01 6A 10 8B F4 60   [ AVfj RP Sj j ��` ]
::  0140:  80 7E 02 0E 75 04 B4 42-EB 1D 91 92 33 D2 F7 76   [ �~  u �B� ��3��v ]
::  0150:  18 91 F7 76 18 42 87 CA-F7 76 1A 8A F2 8A E8 C0   [  ��v B���v ���� ]
::  0160:  CC 02 0A CC B8 01 02 8A-56 40 CD 13 61 8D 64 10   [ �  ̸  �V@� a�d  ]
::  0170:  5E 72 0A 40 75 01 42 03-5E 0B 49 75 B4 C3 03 18   [ ^r @u B ^ Iu��   ]
::  0180:  01 27 0D 0A 4E 6F 20 4F-53 20 46 6F 75 6E 64 20   [  '  No OS Found  ]
::  0190:  20 20 20 20 20 20 20 FF-0D 0A 44 69 73 6B 20 49   [        �  Disk I ]
::  01A0:  2F 4F 20 45 72 72 6F 72-FF 0D 0A 49 6E 73 65 72   [ /O Error�  Inser ]
::  01B0:  74 20 4F 53 20 73 65 74-75 70 20 64 69 73 6B 2C   [ t OS setup disk, ]
::  01C0:  20 74 68 65 6E 20 70 72-65 73 73 20 61 6E 79 20   [  then press any  ]
::  01D0:  6B 65 79 0D 0A 00 00 00-49 4F 20 20 20 20 20 20   [ key     IO       ]
::  01E0:  53 59 53 4D 53 44 4F 53-20 20 20 53 59 53 7E 01   [ SYSMSDOS   SYS~  ]
::  01F0:  00 57 49 4E 42 4F 4F 54-20 53 59 53 00 00 55 AA   [  WINBOOT SYS  U� ]
::  
::  1 - Partition table entry = 1  << Win95 Extended >>      : Entry No.2 (Defines next)
::  01CE:  00 00 01 0F 0F FE 7F 00-4F B5 F9 01 72 82 FF 0B   [      � O�� r��  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 01 0F  START CYL-HEAD-SECTOR: 00Fh-00h-01h
::     +4  0F        PARTITION ID:          Win95 Extended   : Type 0F = EXTENDED
::     +5  FE 7F 00  END CYL-HEAD-SECTOR:   100h-FEh-3Fh
::     +8  01F9B54F  START SECTOR:          33142095         : Offset from MBR = 33,142,095
::     +C  0BFF8272  NUMBER OF SECTORS:     201294450        : Size (Sectors) = 201,294,450
::  
::  1 - Partition table entry = 2  << Empty >>
::  01DE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  1 - Partition table entry = 3  << Empty >>
::  01EE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  2 - Win95 Extended (01F9B54Fh) (Partition Table Entry: 1-1) : LBA 33,142,095 (Start Sector)
::  0000:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0010:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0020:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0030:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0040:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0050:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0060:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0070:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0080:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0090:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00A0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00B0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00C0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00D0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00E0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00F0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0100:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0110:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0120:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0130:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0140:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0150:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0160:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0170:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0180:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0190:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01A0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01B0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 01   [                  ]
::  01C0:  01 0F 0B FE 3F 5F 3F 00-00 00 D2 EA FF 03 00 00   [    �?_?   ���    ]
::  01D0:  01 60 05 FE 3F B0 11 EB-FF 03 11 EB FF 03 00 00   [  ` �?� ��  ��    ]
::  01E0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01F0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 55 AA   [               U� ]
::  
::  2 - Partition table entry = 0  << Win95 FAT32 >>         : Entry No.1 (Defines current)
::  01BE:  00 01 01 0F 0B FE 3F 5F-3F 00 00 00 D2 EA FF 03   [      �?_?   ���  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  01 01 0F  START CYL-HEAD-SECTOR: 00Fh-01h-01h
::     +4  0B        PARTITION ID:          Win95 FAT32      : Type 0B = LOGICAL
::     +5  FE 3F 5F  END CYL-HEAD-SECTOR:   05Fh-FEh-3Fh
::     +8  0000003F  START SECTOR:          63               : Offset (in this Partn) = 63
::     +C  03FFEAD2  NUMBER OF SECTORS:     67103442         : Size (Sectors) = 67,103,442
::  
::  2-0 Win95 FAT32 Boot Record (01F9B58Eh)                  : LBA 33,142,158 (Start Sector)
::  0000:  EB 58 90 4D 53 57 49 4E-34 2E 31 00 02 20 20 00   [ �X�MSWIN4.1      ]
::  0010:  02 00 00 00 00 F8 00 00-3F 00 FF 00 8E B5 F9 01   [      �  ? � ���  ]
::  0020:  D2 EA FF 03 FB 3F 00 00-00 00 00 00 02 00 00 00   [ ��� �?           ]
::  0030:  01 00 06 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0040:  80 00 29 E3 11 22 07 31-32 30 47 42 20 44 49 53   [ � )� " 120GB DIS ]
::  0050:  4B 20 46 41 54 33 32 20-20 20 FA 33 C9 8E D1 BC   [ K FAT32   �3ɎѼ ]
::  0060:  F8 7B 8E C1 BD 78 00 C5-76 00 1E 56 16 55 BF 22   [ �{���x �v  V U�" ]
::  0070:  05 89 7E 00 89 4E 02 B1-0B FC F3 A4 8E D9 BD 00   [  �~ �N � ��ٽ  ]
::  0080:  7C C6 45 FE 0F 8B 46 18-88 45 F9 38 4E 40 7D 25   [ |�E� �F �E�8N@}% ]
::  0090:  8B C1 99 BB 00 07 E8 97-00 72 1A 83 EB 3A 66 A1   [ ����  �- r ��:f� ]
::  00A0:  1C 7C 66 3B 07 8A 57 FC-75 06 80 CA 02 88 56 02   [  |f; �W�u �� �V  ]
::  00B0:  80 C3 10 73 ED BF 02 00-83 7E 16 00 75 45 8B 46   [ �� s��  �~  uE�F ]
::  00C0:  1C 8B 56 1E B9 03 00 49-40 75 01 42 BB 00 7E E8   [  �V �  I@u B� ~� ]
::  00D0:  5F 00 73 26 B0 F8 4F 74-1D 8B 46 32 33 D2 B9 03   [ _ s&��Ot �F23ҹ  ]
::  00E0:  00 3B C8 77 1E 8B 76 0E-3B CE 73 17 2B F1 03 46   [  ;�w �v ;�s +� F ]
::  00F0:  1C 13 56 1E EB D1 73 0B-EB 27 83 7E 2A 00 77 03   [   V ��s �'�~* w  ]
::  0100:  E9 FD 02 BE 7E 7D AC 98-03 F0 AC 84 C0 74 17 3C   [ �� �~}�� ��t < ]
::  0110:  FF 74 09 B4 0E BB 07 00-CD 10 EB EE BE 81 7D EB   [ �t � �  � �}� ]
::  0120:  E5 BE 7F 7D EB E0 98 CD-16 5E 1F 66 8F 04 CD 19   [ �}���� ^ f� �  ]
::  0130:  41 56 66 6A 00 52 50 06-53 6A 01 6A 10 8B F4 60   [ AVfj RP Sj j ��` ]
::  0140:  80 7E 02 0E 75 04 B4 42-EB 1D 91 92 33 D2 F7 76   [ �~  u �B� ��3��v ]
::  0150:  18 91 F7 76 18 42 87 CA-F7 76 1A 8A F2 8A E8 C0   [  ��v B���v ���� ]
::  0160:  CC 02 0A CC B8 01 02 8A-56 40 CD 13 61 8D 64 10   [ �  ̸  �V@� a�d  ]
::  0170:  5E 72 0A 40 75 01 42 03-5E 0B 49 75 B4 C3 03 18   [ ^r @u B ^ Iu��   ]
::  0180:  01 27 0D 0A 49 6E 76 61-6C 69 64 20 73 79 73 74   [  '  Invalid syst ]
::  0190:  65 6D 20 64 69 73 6B FF-0D 0A 44 69 73 6B 20 49   [ em disk�  Disk I ]
::  01A0:  2F 4F 20 65 72 72 6F 72-FF 0D 0A 52 65 70 6C 61   [ /O error�  Repla ]
::  01B0:  63 65 20 74 68 65 20 64-69 73 6B 2C 20 61 6E 64   [ ce the disk, and ]
::  01C0:  20 74 68 65 6E 20 70 72-65 73 73 20 61 6E 79 20   [  then press any  ]
::  01D0:  6B 65 79 0D 0A 00 00 00-49 4F 20 20 20 20 20 20   [ key     IO       ]
::  01E0:  53 59 53 4D 53 44 4F 53-20 20 20 53 59 53 7E 01   [ SYSMSDOS   SYS~  ]
::  01F0:  00 57 49 4E 42 4F 4F 54-20 53 59 53 00 00 55 AA   [  WINBOOT SYS  U� ]
::  
::  2 - Partition table entry = 1  << Extended >>            : Entry No.2 (Defines next)
::  01CE:  00 00 01 60 05 FE 3F B0-11 EB FF 03 11 EB FF 03   [    ` �?� ��  ��  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 01 60  START CYL-HEAD-SECTOR: 060h-00h-01h
::     +4  05        PARTITION ID:          Extended         : Type 05 = EXTENDED (LOGICAL)
::     +5  FE 3F B0  END CYL-HEAD-SECTOR:   0B0h-FEh-3Fh
::     +8  03FFEB11  START SECTOR:          67103505         : Offset from 0F = 67,103,505
::     +C  03FFEB11  NUMBER OF SECTORS:     67103505         : Size (Sectors) = 67,103,505
::  
::  2 - Partition table entry = 2  << Empty >>
::  01DE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  2 - Partition table entry = 3  << Empty >>
::  01EE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  3 - Extended (05F9A060h) (Partition Table Entry: 2-1)    : LBA 100,245,600 (Start Sector)
::  0000:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0010:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0020:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0030:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0040:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0050:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0060:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0070:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0080:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0090:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00A0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00B0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00C0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00D0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00E0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00F0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0100:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0110:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0120:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0130:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0140:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0150:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0160:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0170:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0180:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0190:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01A0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01B0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 01   [                  ]
::  01C0:  01 60 0B FE 3F B0 3F 00-00 00 D2 EA FF 03 00 00   [  ` �?�?   ���    ]
::  01D0:  01 B1 05 FE 7F 00 22 D6-FF 07 50 AC FF 03 00 00   [  � � "�� P��    ]
::  01E0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01F0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 55 AA   [               U� ]
::  
::  3 - Partition table entry = 0  << Win95 FAT32 >>         : Entry No.1 (Defines current)
::  01BE:  00 01 01 60 0B FE 3F B0-3F 00 00 00 D2 EA FF 03   [    ` �?�?   ���  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  01 01 60  START CYL-HEAD-SECTOR: 060h-01h-01h
::     +4  0B        PARTITION ID:          Win95 FAT32      : Type 0B = LOGICAL
::     +5  FE 3F B0  END CYL-HEAD-SECTOR:   0B0h-FEh-3Fh
::     +8  0000003F  START SECTOR:          63               : Offset (in this Partn) = 63
::     +C  03FFEAD2  NUMBER OF SECTORS:     67103442         : Size (Sectors) = 67,103,442
::  
::  3-0 Win95 FAT32 Boot Record (05F9A09Fh)                  : LBA 100,245,663 (Start Sector)
::  0000:  EB 58 90 4D 53 57 49 4E-34 2E 31 00 02 20 20 00   [ �X�MSWIN4.1      ]
::  0010:  02 00 00 00 00 F8 00 00-3F 00 FF 00 9F A0 F9 05   [      �  ? � � �  ]
::  0020:  D2 EA FF 03 FB 3F 00 00-00 00 00 00 02 00 00 00   [ ��� �?           ]
::  0030:  01 00 06 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0040:  80 00 29 EE 11 36 07 31-32 30 47 42 20 44 49 53   [ � )� 6 120GB DIS ]
::  0050:  4B 20 46 41 54 33 32 20-20 20 FA 33 C9 8E D1 BC   [ K FAT32   �3ɎѼ ]
::  0060:  F8 7B 8E C1 BD 78 00 C5-76 00 1E 56 16 55 BF 22   [ �{���x �v  V U�" ]
::  0070:  05 89 7E 00 89 4E 02 B1-0B FC F3 A4 8E D9 BD 00   [  �~ �N � ��ٽ  ]
::  0080:  7C C6 45 FE 0F 8B 46 18-88 45 F9 38 4E 40 7D 25   [ |�E� �F �E�8N@}% ]
::  0090:  8B C1 99 BB 00 07 E8 97-00 72 1A 83 EB 3A 66 A1   [ ����  �- r ��:f� ]
::  00A0:  1C 7C 66 3B 07 8A 57 FC-75 06 80 CA 02 88 56 02   [  |f; �W�u �� �V  ]
::  00B0:  80 C3 10 73 ED BF 02 00-83 7E 16 00 75 45 8B 46   [ �� s��  �~  uE�F ]
::  00C0:  1C 8B 56 1E B9 03 00 49-40 75 01 42 BB 00 7E E8   [  �V �  I@u B� ~� ]
::  00D0:  5F 00 73 26 B0 F8 4F 74-1D 8B 46 32 33 D2 B9 03   [ _ s&��Ot �F23ҹ  ]
::  00E0:  00 3B C8 77 1E 8B 76 0E-3B CE 73 17 2B F1 03 46   [  ;�w �v ;�s +� F ]
::  00F0:  1C 13 56 1E EB D1 73 0B-EB 27 83 7E 2A 00 77 03   [   V ��s �'�~* w  ]
::  0100:  E9 FD 02 BE 7E 7D AC 98-03 F0 AC 84 C0 74 17 3C   [ �� �~}�� ��t < ]
::  0110:  FF 74 09 B4 0E BB 07 00-CD 10 EB EE BE 81 7D EB   [ �t � �  � �}� ]
::  0120:  E5 BE 7F 7D EB E0 98 CD-16 5E 1F 66 8F 04 CD 19   [ �}���� ^ f� �  ]
::  0130:  41 56 66 6A 00 52 50 06-53 6A 01 6A 10 8B F4 60   [ AVfj RP Sj j ��` ]
::  0140:  80 7E 02 0E 75 04 B4 42-EB 1D 91 92 33 D2 F7 76   [ �~  u �B� ��3��v ]
::  0150:  18 91 F7 76 18 42 87 CA-F7 76 1A 8A F2 8A E8 C0   [  ��v B���v ���� ]
::  0160:  CC 02 0A CC B8 01 02 8A-56 40 CD 13 61 8D 64 10   [ �  ̸  �V@� a�d  ]
::  0170:  5E 72 0A 40 75 01 42 03-5E 0B 49 75 B4 C3 03 18   [ ^r @u B ^ Iu��   ]
::  0180:  01 27 0D 0A 49 6E 76 61-6C 69 64 20 73 79 73 74   [  '  Invalid syst ]
::  0190:  65 6D 20 64 69 73 6B FF-0D 0A 44 69 73 6B 20 49   [ em disk�  Disk I ]
::  01A0:  2F 4F 20 65 72 72 6F 72-FF 0D 0A 52 65 70 6C 61   [ /O error�  Repla ]
::  01B0:  63 65 20 74 68 65 20 64-69 73 6B 2C 20 61 6E 64   [ ce the disk, and ]
::  01C0:  20 74 68 65 6E 20 70 72-65 73 73 20 61 6E 79 20   [  then press any  ]
::  01D0:  6B 65 79 0D 0A 00 00 00-49 4F 20 20 20 20 20 20   [ key     IO       ]
::  01E0:  53 59 53 4D 53 44 4F 53-20 20 20 53 59 53 7E 01   [ SYSMSDOS   SYS~  ]
::  01F0:  00 57 49 4E 42 4F 4F 54-20 53 59 53 00 00 55 AA   [  WINBOOT SYS  U� ]
::  
::  3 - Partition table entry = 1  << Extended >>            : Entry No.2 (Defines next)
::  01CE:  00 00 01 B1 05 FE 7F 00-22 D6 FF 07 50 AC FF 03   [    � � "�� P��  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 01 B1  START CYL-HEAD-SECTOR: 0B1h-00h-01h
::     +4  05        PARTITION ID:          Extended         : Type 05 = EXTENDED (LOGICAL)
::     +5  FE 7F 00  END CYL-HEAD-SECTOR:   100h-FEh-3Fh
::     +8  07FFD622  START SECTOR:          134207010        : Offset from 0F = 134,207,010
::     +C  03FFAC50  NUMBER OF SECTORS:     67087440         : Size (Sectors) =  67,087,440
::  
::  3 - Partition table entry = 2  << Empty >>
::  01DE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  3 - Partition table entry = 3  << Empty >>
::  01EE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  4 - Extended (09F98B71h) (Partition Table Entry: 3-1)
::  0000:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0010:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0020:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0030:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0040:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0050:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0060:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0070:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0080:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0090:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00A0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00B0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00C0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00D0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00E0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00F0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0100:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0110:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0120:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0130:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0140:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0150:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0160:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0170:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0180:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0190:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01A0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01B0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 01   [                  ]
::  01C0:  01 B1 0B FE 7F 00 3F 00-00 00 11 AC FF 03 00 00   [  � � ?    ��    ]
::  01D0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01E0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01F0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 55 AA   [               U� ]
::  
::  4 - Partition table entry = 0  << Win95 FAT32 >>         : Entry No.1 (Defines current)
::  01BE:  00 01 01 B1 0B FE 7F 00-3F 00 00 00 11 AC FF 03   [    � � ?    ��  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  01 01 B1  START CYL-HEAD-SECTOR: 0B1h-01h-01h
::     +4  0B        PARTITION ID:          Win95 FAT32      : Type 0B = LOGICAL
::     +5  FE 7F 00  END CYL-HEAD-SECTOR:   100h-FEh-3Fh
::     +8  0000003F  START SECTOR:          63               : Offset (from Extended) = 63
::     +C  03FFAC11  NUMBER OF SECTORS:     67087377         : Size (Sectors) = 67,087,377
::  
::  4-0 Win95 FAT32 Boot Record (09F98BB0h)                  : LBA 167,349,168 (Start Sector)
::  0000:  EB 58 90 4D 53 57 49 4E-34 2E 31 00 02 20 20 00   [ �X�MSWIN4.1      ]
::  0010:  02 00 00 00 00 F8 00 00-3F 00 FF 00 B0 8B F9 09   [      �  ? � ���  ]
::  0020:  11 AC FF 03 F7 3F 00 00-00 00 00 00 02 00 00 00   [  �� �?           ]
::  0030:  01 00 06 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0040:  80 00 29 F8 11 22 06 31-32 30 47 42 20 44 49 53   [ � )� " 120GB DIS ]
::  0050:  4B 20 46 41 54 33 32 20-20 20 FA 33 C9 8E D1 BC   [ K FAT32   �3ɎѼ ]
::  0060:  F8 7B 8E C1 BD 78 00 C5-76 00 1E 56 16 55 BF 22   [ �{���x �v  V U�" ]
::  0070:  05 89 7E 00 89 4E 02 B1-0B FC F3 A4 8E D9 BD 00   [  �~ �N � ��ٽ  ]
::  0080:  7C C6 45 FE 0F 8B 46 18-88 45 F9 38 4E 40 7D 25   [ |�E� �F �E�8N@}% ]
::  0090:  8B C1 99 BB 00 07 E8 97-00 72 1A 83 EB 3A 66 A1   [ ����  �- r ��:f� ]
::  00A0:  1C 7C 66 3B 07 8A 57 FC-75 06 80 CA 02 88 56 02   [  |f; �W�u �� �V  ]
::  00B0:  80 C3 10 73 ED BF 02 00-83 7E 16 00 75 45 8B 46   [ �� s��  �~  uE�F ]
::  00C0:  1C 8B 56 1E B9 03 00 49-40 75 01 42 BB 00 7E E8   [  �V �  I@u B� ~� ]
::  00D0:  5F 00 73 26 B0 F8 4F 74-1D 8B 46 32 33 D2 B9 03   [ _ s&��Ot �F23ҹ  ]
::  00E0:  00 3B C8 77 1E 8B 76 0E-3B CE 73 17 2B F1 03 46   [  ;�w �v ;�s +� F ]
::  00F0:  1C 13 56 1E EB D1 73 0B-EB 27 83 7E 2A 00 77 03   [   V ��s �'�~* w  ]
::  0100:  E9 FD 02 BE 7E 7D AC 98-03 F0 AC 84 C0 74 17 3C   [ �� �~}�� ��t < ]
::  0110:  FF 74 09 B4 0E BB 07 00-CD 10 EB EE BE 81 7D EB   [ �t � �  � �}� ]
::  0120:  E5 BE 7F 7D EB E0 98 CD-16 5E 1F 66 8F 04 CD 19   [ �}���� ^ f� �  ]
::  0130:  41 56 66 6A 00 52 50 06-53 6A 01 6A 10 8B F4 60   [ AVfj RP Sj j ��` ]
::  0140:  80 7E 02 0E 75 04 B4 42-EB 1D 91 92 33 D2 F7 76   [ �~  u �B� ��3��v ]
::  0150:  18 91 F7 76 18 42 87 CA-F7 76 1A 8A F2 8A E8 C0   [  ��v B���v ���� ]
::  0160:  CC 02 0A CC B8 01 02 8A-56 40 CD 13 61 8D 64 10   [ �  ̸  �V@� a�d  ]
::  0170:  5E 72 0A 40 75 01 42 03-5E 0B 49 75 B4 C3 03 18   [ ^r @u B ^ Iu��   ]
::  0180:  01 27 0D 0A 49 6E 76 61-6C 69 64 20 73 79 73 74   [  '  Invalid syst ]
::  0190:  65 6D 20 64 69 73 6B FF-0D 0A 44 69 73 6B 20 49   [ em disk�  Disk I ]
::  01A0:  2F 4F 20 65 72 72 6F 72-FF 0D 0A 52 65 70 6C 61   [ /O error�  Repla ]
::  01B0:  63 65 20 74 68 65 20 64-69 73 6B 2C 20 61 6E 64   [ ce the disk, and ]
::  01C0:  20 74 68 65 6E 20 70 72-65 73 73 20 61 6E 79 20   [  then press any  ]
::  01D0:  6B 65 79 0D 0A 00 00 00-49 4F 20 20 20 20 20 20   [ key     IO       ]
::  01E0:  53 59 53 4D 53 44 4F 53-20 20 20 53 59 53 7E 01   [ SYSMSDOS   SYS~  ]
::  01F0:  00 57 49 4E 42 4F 4F 54-20 53 59 53 00 00 55 AA   [  WINBOOT SYS  U� ]
::  
::  4 - Partition table entry = 1  << Empty >>
::  01CE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  4 - Partition table entry = 2  << Empty >>
::  01DE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  4 - Partition table entry = 3  << Empty >>
::  01EE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  
::  [ PARTITION MAP - LBA ]
::  
::            ABSOLUTE          PART-TABLE
::         START     END      START    BLOCKS
::        ======== ========  ======== ========
::  1-0 : 0000003F 01F9B54E  0000003F 01F9B510  Win95 FAT32 (LBA)
::  1-1 : 01F9B54F 0DF937C0  01F9B54F 0BFF8272  Win95 Extended
::  2-0 : 01F9B58E 05F9A05F  0000003F 03FFEAD2  Win95 FAT32
::  2-1 : 05F9A060 09F98B70  03FFEB11 03FFEB11  Extended
::  3-0 : 05F9A09F 09F98B70  0000003F 03FFEAD2  Win95 FAT32
::  3-1 : 09F98B71 0DF937C0  07FFD622 03FFAC50  Extended
::  4-0 : 09F98BB0 0DF937C0  0000003F 03FFAC11  Win95 FAT32
::  
::  Notes:
::  1. Western Digital HDD, 120GB (111GB formatted)
::  2. 4 drives (1 x 15GB, 3 x 32GB) (Total = 111GB):
::     - Primary DOS Partition (Active) (15GB)
::     - Extended: Logical Partition    (32GB)
::                 Logical Partition    (32GB)
::                 Logical Partition    (32GB)


::  TINY PC, Original HDD
::  Fujitsu 10GB
::  1 partition: Primary DOS (Bootable: WinME)
::  
::  Partition 0: (Non-DOS, Track 0) begins at CHS 0-0-1 (LBA 0)
::  Partition 1: (Primary DOS) (C:) begins at CHS 0-1-1 (LBA 63)
::  
::  MBRSCAN v1.1 Copyright (C) 1995,1999 by Nobumichi Kozawa
::  LBA mode
::  
::  1 - Master Boot Record (00000000h)
::  0000:  33 C0 8E D0 BC 00 7C FB-50 07 50 1F FC BE 1B 7C   [ 3��м |�P P �� | ]
::  0010:  BF 1B 06 50 57 B9 E5 01-F3 A4 CB BE BE 07 B1 04   [ �  PW�� �˾� �  ]
::  0020:  38 2C 7C 09 75 15 83 C6-10 E2 F5 CD 18 8B 14 8B   [ 8,| u �� ��� � � ]
::  0030:  EE 83 C6 10 49 74 16 38-2C 74 F6 BE 10 07 4E AC   [ �� It 8,t��  N� ]
::  0040:  3C 00 74 FA BB 07 00 B4-0E CD 10 EB F2 89 46 25   [ < t��  � � ��F% ]
::  0050:  96 8A 46 04 B4 06 3C 0E-74 11 B4 0B 3C 0C 74 05   [ ��F � < t � < t  ]
::  0060:  3A C4 75 2B 40 C6 46 25-06 75 24 BB AA 55 50 B4   [ :�u+@�F% u$��UP� ]
::  0070:  41 CD 13 58 72 16 81 FB-55 AA 75 10 F6 C1 01 74   [ A� Xr ��U�u �� t ]
::  0080:  0B 8A E0 88 56 24 C7 06-A1 06 EB 1E 88 66 04 BF   [  ���V$� � � �f � ]
::  0090:  0A 00 B8 01 02 8B DC 33-C9 83 FF 05 7F 03 8B 4E   [   �  ��3Ƀ�  �N ]
::  00A0:  25 03 4E 02 CD 13 72 29-BE 75 07 81 3E FE 7D 55   [ % N � r)�u �>�}U ]
::  00B0:  AA 74 5A 83 EF 05 7F DA-85 F6 75 83 BE 3F 07 EB   [ �tZ�� څ�u��? � ]
::  00C0:  8A 98 91 52 99 03 46 08-13 56 0A E8 12 00 5A EB   [ ���R� F  V �  Z� ]
::  00D0:  D5 4F 74 E4 33 C0 CD 13-EB B8 00 00 80 18 26 12   [ �Ot�3�� �  � &  ]
::  00E0:  56 33 F6 56 56 52 50 06-53 51 BE 10 00 56 8B F4   [ V3�VVRP SQ�  V�� ]
::  00F0:  50 52 B8 00 42 8A 56 24-CD 13 5A 58 8D 64 10 72   [ PR� B�V$� ZX�d r ]
::  0100:  0A 40 75 01 42 80 C7 02-E2 F7 F8 5E C3 EB 74 49   [  @u B�� ���^��tI ]
::  0110:  6E 76 61 6C 69 64 20 70-61 72 74 69 74 69 6F 6E   [ nvalid partition ]
::  0120:  20 74 61 62 6C 65 2E 20-53 65 74 75 70 20 63 61   [  table. Setup ca ]
::  0130:  6E 6E 6F 74 20 63 6F 6E-74 69 6E 75 65 2E 00 45   [ nnot continue. E ]
::  0140:  72 72 6F 72 20 6C 6F 61-64 69 6E 67 20 6F 70 65   [ rror loading ope ]
::  0150:  72 61 74 69 6E 67 20 73-79 73 74 65 6D 2E 20 53   [ rating system. S ]
::  0160:  65 74 75 70 20 63 61 6E-6E 6F 74 20 63 6F 6E 74   [ etup cannot cont ]
::  0170:  69 6E 75 65 2E 00 00 00-00 00 00 00 00 00 00 00   [ inue.            ]
::  0180:  00 00 00 8B FC 1E 57 8B-F5 CB 00 00 00 00 00 00   [    �� W���       ]
::  0190:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01A0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01B0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 80 01   [               �  ]
::  01C0:  01 00 0C FE 3F DC 3F 00-00 00 5E 30 31 01 00 00   [    �?�?   ^01    ]
::  01D0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01E0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01F0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 55 AA   [               U� ]
::  
::  1 - Partition table entry = 0  << Win95 FAT32 (LBA) >>
::  01BE:  80 01 01 00 0C FE 3F DC-3F 00 00 00 5E 30 31 01   [ �    �?�?   ^01  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  80        STATUS:                Active
::     +1  01 01 00  START CYL-HEAD-SECTOR: 000h-01h-01h
::     +4  0C        PARTITION ID:          Win95 FAT32 (LBA)
::     +5  FE 3F DC  END CYL-HEAD-SECTOR:   0DCh-FEh-3Fh
::     +8  0000003F  START SECTOR:          63
::     +C  0131305E  NUMBER OF SECTORS:     20000862
::  
::  1-0 Win95 FAT32 (LBA) Boot Record (0000003Fh)
::  0000:  EB 58 90 4D 53 57 49 4E-34 2E 31 00 02 10 20 00   [ �X�MSWIN4.1      ]
::  0010:  02 00 00 00 00 F8 00 00-3F 00 FF 00 3F 00 00 00   [      �  ? � ?    ]
::  0020:  5E 30 31 01 22 26 00 00-00 00 00 00 02 00 00 00   [ ^01 "&           ]
::  0030:  01 00 06 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0040:  80 00 29 DB 13 66 27 4D-50 46 33 31 30 32 41 54   [ � )� f'MPF3102AT ]
::  0050:  20 20 46 41 54 33 32 20-20 20 FA 33 C9 8E D1 BC   [   FAT32   �3ɎѼ ]
::  0060:  F8 7B 8E C1 BD 78 00 C5-76 00 1E 56 16 55 BF 22   [ �{���x �v  V U�" ]
::  0070:  05 89 7E 00 89 4E 02 B1-0B FC F3 A4 8E D9 BD 00   [  �~ �N � ��ٽ  ]
::  0080:  7C C6 45 FE 0F 8B 46 18-88 45 F9 38 4E 40 7D 25   [ |�E� �F �E�8N@}% ]
::  0090:  8B C1 99 BB 00 07 E8 97-00 72 1A 83 EB 3A 66 A1   [ ����  � r ��:f� ]
::  00A0:  1C 7C 66 3B 07 8A 57 FC-75 06 80 CA 02 88 56 02   [  |f; �W�u �� �V  ]
::  00B0:  80 C3 10 73 ED BF 02 00-83 7E 16 00 75 45 8B 46   [ �� s��  �~  uE�F ]
::  00C0:  1C 8B 56 1E B9 03 00 49-40 75 01 42 BB 00 7E E8   [  �V �  I@u B� ~� ]
::  00D0:  5F 00 73 26 B0 F8 4F 74-1D 8B 46 32 33 D2 B9 03   [ _ s&��Ot �F23ҹ  ]
::  00E0:  00 3B C8 77 1E 8B 76 0E-3B CE 73 17 2B F1 03 46   [  ;�w �v ;�s +� F ]
::  00F0:  1C 13 56 1E EB D1 73 0B-EB 27 83 7E 2A 00 77 03   [   V ��s �'�~* w  ]
::  0100:  E9 FD 02 BE 7E 7D AC 98-03 F0 AC 84 C0 74 17 3C   [ �� �~}�� ��t < ]
::  0110:  FF 74 09 B4 0E BB 07 00-CD 10 EB EE BE 81 7D EB   [ �t � �  � �}� ]
::  0120:  E5 BE 7F 7D EB E0 98 CD-16 5E 1F 66 8F 04 CD 19   [ �}���� ^ f� �  ]
::  0130:  41 56 66 6A 00 52 50 06-53 6A 01 6A 10 8B F4 60   [ AVfj RP Sj j ��` ]
::  0140:  80 7E 02 0E 75 04 B4 42-EB 1D 91 92 33 D2 F7 76   [ �~  u �B� ��3��v ]
::  0150:  18 91 F7 76 18 42 87 CA-F7 76 1A 8A F2 8A E8 C0   [  ��v B���v ���� ]
::  0160:  CC 02 0A CC B8 01 02 8A-56 40 CD 13 61 8D 64 10   [ �  ̸  �V@� a�d  ]
::  0170:  5E 72 0A 40 75 01 42 03-5E 0B 49 75 B4 C3 03 18   [ ^r @u B ^ Iu��   ]
::  0180:  01 27 0D 0A 49 6E 76 61-6C 69 64 20 73 79 73 74   [  '  Invalid syst ]
::  0190:  65 6D 20 64 69 73 6B FF-0D 0A 44 69 73 6B 20 49   [ em disk�  Disk I ]
::  01A0:  2F 4F 20 65 72 72 6F 72-FF 0D 0A 52 65 70 6C 61   [ /O error�  Repla ]
::  01B0:  63 65 20 74 68 65 20 64-69 73 6B 2C 20 61 6E 64   [ ce the disk, and ]
::  01C0:  20 74 68 65 6E 20 70 72-65 73 73 20 61 6E 79 20   [  then press any  ]
::  01D0:  6B 65 79 0D 0A 00 00 00-49 4F 20 20 20 20 20 20   [ key     IO       ]
::  01E0:  53 59 53 4D 53 44 4F 53-20 20 20 53 59 53 7E 01   [ SYSMSDOS   SYS~  ]
::  01F0:  00 57 49 4E 42 4F 4F 54-20 53 59 53 00 00 55 AA   [  WINBOOT SYS  U� ]
::  
::  1 - Partition table entry = 1  << Empty >>
::  01CE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  1 - Partition table entry = 2  << Empty >>
::  01DE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  1 - Partition table entry = 3  << Empty >>
::  01EE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  
::  [ PARTITION MAP - LBA ]
::  
::            ABSOLUTE          PART-TABLE
::         START     END      START    BLOCKS
::        ======== ========  ======== ========
::  1-0 : 0000003F 0131309C  0000003F 0131305E  Win95 FAT32 (LBA)


::  TIME PC, Original Drive C: (Bootable: Win 98)
::  Seagate 18GB - ST320423A (M02GB2, Win98SE HDD)
::  [NB: Currently used for data backup/storage at M.H.]
::  [NB: Not bootable on the Tiny PC, due to incompatible device drivers]
::  
::  Partition 0: (Non-DOS, Track 0) begins at CHS 0-0-1 (LBA 0)
::  Partition 1: (Primary DOS) (C:) begins at CHS 0-1-1 (LBA 63)
::  
::  MBRSCAN v1.1 Copyright (C) 1995,1999 by Nobumichi Kozawa
::  LBA mode
::  
::  1 - Master Boot Record (00000000h)
::  0000:  33 C0 8E D0 BC 00 7C FB-50 07 50 1F FC BE 1B 7C   [ 3��м |�P P �� | ]
::  0010:  BF 1B 06 50 57 B9 E5 01-F3 A4 CB BE BE 07 B1 04   [ �  PW�� �˾� �  ]
::  0020:  38 2C 7C 09 75 15 83 C6-10 E2 F5 CD 18 8B 14 8B   [ 8,| u �� ��� � � ]
::  0030:  EE 83 C6 10 49 74 16 38-2C 74 F6 BE 10 07 4E AC   [ �� It 8,t��  N� ]
::  0040:  3C 00 74 FA BB 07 00 B4-0E CD 10 EB F2 89 46 25   [ < t��  � � ��F% ]
::  0050:  96 8A 46 04 B4 06 3C 0E-74 11 B4 0B 3C 0C 74 05   [ -�F � < t � < t  ]
::  0060:  3A C4 75 2B 40 C6 46 25-06 75 24 BB AA 55 50 B4   [ :�u+@�F% u$��UP� ]
::  0070:  41 CD 13 58 72 16 81 FB-55 AA 75 10 F6 C1 01 74   [ A� Xr ��U�u �� t ]
::  0080:  0B 8A E0 88 56 24 C7 06-A1 06 EB 1E 88 66 04 BF   [  ���V$� � � �f � ]
::  0090:  0A 00 B8 01 02 8B DC 33-C9 83 FF 05 7F 03 8B 4E   [   �  ��3Ƀ�  �N ]
::  00A0:  25 03 4E 02 CD 13 72 29-BE 75 07 81 3E FE 7D 55   [ % N � r)�u �>�}U ]
::  00B0:  AA 74 5A 83 EF 05 7F DA-85 F6 75 83 BE 3F 07 EB   [ �tZ�� څ�u��? � ]
::  00C0:  8A 98 91 52 99 03 46 08-13 56 0A E8 12 00 5A EB   [ ���R� F  V �  Z� ]
::  00D0:  D5 4F 74 E4 33 C0 CD 13-EB B8 00 00 80 24 13 09   [ �Ot�3�� �  �$   ]
::  00E0:  56 33 F6 56 56 52 50 06-53 51 BE 10 00 56 8B F4   [ V3�VVRP SQ�  V�� ]
::  00F0:  50 52 B8 00 42 8A 56 24-CD 13 5A 58 8D 64 10 72   [ PR� B�V$� ZX�d r ]
::  0100:  0A 40 75 01 42 80 C7 02-E2 F7 F8 5E C3 EB 74 49   [  @u B�� ���^��tI ]
::  0110:  6E 76 61 6C 69 64 20 70-61 72 74 69 74 69 6F 6E   [ nvalid partition ]
::  0120:  20 74 61 62 6C 65 2E 20-53 65 74 75 70 20 63 61   [  table. Setup ca ]
::  0130:  6E 6E 6F 74 20 63 6F 6E-74 69 6E 75 65 2E 00 45   [ nnot continue. E ]
::  0140:  72 72 6F 72 20 6C 6F 61-64 69 6E 67 20 6F 70 65   [ rror loading ope ]
::  0150:  72 61 74 69 6E 67 20 73-79 73 74 65 6D 2E 20 53   [ rating system. S ]
::  0160:  65 74 75 70 20 63 61 6E-6E 6F 74 20 63 6F 6E 74   [ etup cannot cont ]
::  0170:  69 6E 75 65 2E 00 00 00-00 00 00 00 00 00 00 00   [ inue.            ]
::  0180:  00 00 00 8B FC 1E 57 8B-F5 CB 00 00 00 00 00 00   [    �� W���       ]
::  0190:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01A0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01B0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 80 01   [               �  ]
::  01C0:  01 00 0C FE FF FE 3F 00-00 00 3C 3F 43 02 00 00   [    ���?   <?C    ]
::  01D0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01E0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01F0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 55 AA   [               U� ]
::  
::  1 - Partition table entry = 0  << Win95 FAT32 (LBA) >>
::  01BE:  80 01 01 00 0C FE FF FE-3F 00 00 00 3C 3F 43 02   [ �    ���?   <?C  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  80        STATUS:                Active
::     +1  01 01 00  START CYL-HEAD-SECTOR: 000h-01h-01h
::     +4  0C        PARTITION ID:          Win95 FAT32 (LBA)
::     +5  FE FF FE  END CYL-HEAD-SECTOR:   3FEh-FEh-3Fh
::     +8  0000003F  START SECTOR:          63
::     +C  02433F3C  NUMBER OF SECTORS:     37961532
::  
::  1-0 Win95 FAT32 (LBA) Boot Record (0000003Fh)
::  0000:  EB 58 90 4D 53 57 49 4E-34 2E 31 00 02 20 20 00   [ �X�MSWIN4.1      ]
::  0010:  02 00 00 00 00 F8 00 00-3F 00 FF 00 3F 00 00 00   [      �  ? � ?    ]
::  0020:  3C 3F 43 02 30 24 00 00-00 00 00 00 02 00 00 00   [ <?C 0$           ]
::  0030:  01 00 06 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0040:  80 00 29 F0 11 3F 18 4D-30 32 47 42 32 20 20 20   [ � )� ? M02GB2    ]
::  0050:  20 20 46 41 54 33 32 20-20 20 FA 33 C9 8E D1 BC   [   FAT32   �3ɎѼ ]
::  0060:  F8 7B 8E C1 BD 78 00 C5-76 00 1E 56 16 55 BF 22   [ �{���x �v  V U�" ]
::  0070:  05 89 7E 00 89 4E 02 B1-0B FC F3 A4 8E D9 BD 00   [  �~ �N � ��ٽ  ]
::  0080:  7C C6 45 FE 0F 8B 46 18-88 45 F9 38 4E 40 7D 25   [ |�E� �F �E�8N@}% ]
::  0090:  8B C1 99 BB 00 07 E8 97-00 72 1A 83 EB 3A 66 A1   [ ����  �- r ��:f� ]
::  00A0:  1C 7C 66 3B 07 8A 57 FC-75 06 80 CA 02 88 56 02   [  |f; �W�u �� �V  ]
::  00B0:  80 C3 10 73 ED BF 02 00-83 7E 16 00 75 45 8B 46   [ �� s��  �~  uE�F ]
::  00C0:  1C 8B 56 1E B9 03 00 49-40 75 01 42 BB 00 7E E8   [  �V �  I@u B� ~� ]
::  00D0:  5F 00 73 26 B0 F8 4F 74-1D 8B 46 32 33 D2 B9 03   [ _ s&��Ot �F23ҹ  ]
::  00E0:  00 3B C8 77 1E 8B 76 0E-3B CE 73 17 2B F1 03 46   [  ;�w �v ;�s +� F ]
::  00F0:  1C 13 56 1E EB D1 73 0B-EB 27 83 7E 2A 00 77 03   [   V ��s �'�~* w  ]
::  0100:  E9 FD 02 BE 7E 7D AC 98-03 F0 AC 84 C0 74 17 3C   [ �� �~}�� ��t < ]
::  0110:  FF 74 09 B4 0E BB 07 00-CD 10 EB EE BE 81 7D EB   [ �t � �  � �}� ]
::  0120:  E5 BE 7F 7D EB E0 98 CD-16 5E 1F 66 8F 04 CD 19   [ �}���� ^ f� �  ]
::  0130:  41 56 66 6A 00 52 50 06-53 6A 01 6A 10 8B F4 60   [ AVfj RP Sj j ��` ]
::  0140:  80 7E 02 0E 75 04 B4 42-EB 1D 91 92 33 D2 F7 76   [ �~  u �B� ��3��v ]
::  0150:  18 91 F7 76 18 42 87 CA-F7 76 1A 8A F2 8A E8 C0   [  ��v B���v ���� ]
::  0160:  CC 02 0A CC B8 01 02 8A-56 40 CD 13 61 8D 64 10   [ �  ̸  �V@� a�d  ]
::  0170:  5E 72 0A 40 75 01 42 03-5E 0B 49 75 B4 C3 03 18   [ ^r @u B ^ Iu��   ]
::  0180:  01 27 0D 0A 49 6E 76 61-6C 69 64 20 73 79 73 74   [  '  Invalid syst ]
::  0190:  65 6D 20 64 69 73 6B FF-0D 0A 44 69 73 6B 20 49   [ em disk�  Disk I ]
::  01A0:  2F 4F 20 65 72 72 6F 72-FF 0D 0A 52 65 70 6C 61   [ /O error�  Repla ]
::  01B0:  63 65 20 74 68 65 20 64-69 73 6B 2C 20 61 6E 64   [ ce the disk, and ]
::  01C0:  20 74 68 65 6E 20 70 72-65 73 73 20 61 6E 79 20   [  then press any  ]
::  01D0:  6B 65 79 0D 0A 00 00 00-49 4F 20 20 20 20 20 20   [ key     IO       ]
::  01E0:  53 59 53 4D 53 44 4F 53-20 20 20 53 59 53 7E 01   [ SYSMSDOS   SYS~  ]
::  01F0:  00 57 49 4E 42 4F 4F 54-20 53 59 53 00 00 55 AA   [  WINBOOT SYS  U� ]
::  
::  1 - Partition table entry = 1  << Empty >>
::  01CE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  1 - Partition table entry = 2  << Empty >>
::  01DE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  1 - Partition table entry = 3  << Empty >>
::  01EE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  MBRS011 Geometry was not saved. Assuming HH = FF, SS = 3F
::  
::  [ PARTITION MAP - LBA ]
::  
::            ABSOLUTE          PART-TABLE
::         START     END      START    BLOCKS
::        ======== ========  ======== ========
::  1-0 : 0000003F 02433F7A  0000003F 02433F3C  Win95 FAT32 (LBA)


::  TINY PC, Drive C: (Faulty) (Fault dated 1 Nov '08)
::  Seagate 80GB - ST380011A (Bootable: WinME) [NB: Broken HDD]
::  
::  Partition 0: (Non-DOS, Track 0) begins at CHS 0-0-1 (LBA 0)
::  Partition 1: (Primary DOS) (C:) begins at CHS 0-1-1 (LBA 63)
::  
::  MBRSCAN v1.1 Copyright (C) 1995,1999 by Nobumichi Kozawa
::  LBA mode
::  
::  1 - Master Boot Record (00000000h)
::  0000:  90 E9 7D 01 FA 33 C0 8E-D0 8E C0 8E D8 BC 00 7C   [ ��} �3��Ў��ؼ | ]
::  0010:  8B F4 FB BF 00 06 B9 00-01 F3 A5 BB 20 06 FF E3   [ ����  �  �  �� ]
::  0020:  90 90 BE 7D 07 81 3C AA-55 75 11 E8 58 00 73 0C   [ ���} �<�Uu �X s  ]
::  0030:  E8 65 00 72 07 E8 B1 00-72 3B EB 2C BE 7D 07 C7   [ �e r � r;�,�} � ]
::  0040:  04 00 00 BA 80 00 BE BE-07 B9 04 00 F6 04 80 75   [    �� �� �  � �u ]
::  0050:  07 83 C6 10 E2 F6 EB 1D-8A 74 01 8B 4C 02 BB 00   [  �� ��� �t �L �  ]
::  0060:  7C B8 01 02 CD 13 72 0D-81 3E FE 7D 55 AA 75 05   [ |�  � r �>�}U�u  ]
::  0070:  EA 00 7C 00 00 BE 6A 07-AC 0A C0 74 FE BB 07 00   [ � |  �j � �t��   ]
::  0080:  B4 0E CD 10 EB F2 BB 00-7E C6 07 13 C6 47 01 00   [ � � �� ~�  �G   ]
::  0090:  B2 80 B8 00 E0 CD 13 C3-BF 00 7E BA F0 01 B3 A0   [ ��� �� ÿ ~�� �  ]
::  00A0:  E8 84 00 72 0C B1 01 E8-48 00 72 05 E8 19 00 73   [ � r � �H r �  s ]
::  00B0:  16 F6 C3 10 75 05 80 CB-10 EB E5 81 FA 70 01 74   [  �� u �� ���p t ]
::  00C0:  05 BA 70 01 EB D8 F9 C3-81 BD FE 01 55 AA 75 17   [  �p ���Á�� U�u  ]
::  00D0:  8B 75 02 81 FE BE 01 77-0E 03 F7 81 3C AA 55 75   [ �u ��� w  ��<�Uu ]
::  00E0:  06 F6 44 02 01 75 01 F9-C3 BF 00 7C B1 0A E8 01   [  �D  u �ÿ |� �  ]
::  00F0:  00 C3 52 57 83 C2 02 B0-01 EE 42 8A C1 EE 42 32   [  �RW�� � �B���B2 ]
::  0100:  C0 EE 42 EE 42 8A C3 EE-42 B0 20 EE E8 33 00 EC   [ ��B�B���B� ��3 � ]
::  0110:  24 FD 3C 58 75 0D 83 EA-07 B9 00 01 FA F3 6D FB   [ $�<Xu �� �  ��m� ]
::  0120:  F8 EB 01 F9 5F 5A C3 52-83 C2 07 EC A8 80 75 0F   [ �� �_Z�R�� 쨀u  ]
::  0130:  4A 8A C3 EE 42 EC 24 D0-3C 50 75 03 F8 EB 01 F9   [ J���B�$�<Pu �� � ]
::  0140:  5A C3 51 8B 0E 6C 04 83-C1 12 81 C2 FF 01 EC 8A   [ Z�Q� l �� ��� � ]
::  0150:  E0 80 E4 D8 80 FC 58 74-06 3B 0E 6C 04 75 EF 81   [ ���؀�Xt ; l u� ]
::  0160:  EA FF 01 B9 00 20 E2 FE-59 C3 0D 0A 45 72 72 6F   [ �� �  ��Y�  Erro ]
::  0170:  72 20 4C 6F 61 64 69 6E-67 20 4F 53 00 AA 55 00   [ r Loading OS �U  ]
::  0180:  00 E9 80 FE 00 00 00 00-00 00 00 00 00 00 00 00   [  ��             ]
::  0190:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01A0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01B0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 80 01   [               �  ]
::  01C0:  01 00 0C FE FF FF 3F 00-00 00 82 E4 50 09 00 00   [    ���?   ��P    ]
::  01D0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01E0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01F0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 55 AA   [               U� ]
::  
::  Note -
::  There may be a *fault* in the above MBR sector. The bytes "90 E9 7D 01 FA"
::  preceed the three bytes which ought to begin the sector (i.e. "33 C0 8E"),
::  and the rest of the sector does not look like any other MBR sector above.
::  
::  
::  1 - Partition table entry = 0  << Win95 FAT32 (LBA) >>
::  01BE:  80 01 01 00 0C FE FF FF-3F 00 00 00 82 E4 50 09   [ �    ���?   ��P  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  80        STATUS:                Active
::     +1  01 01 00  START CYL-HEAD-SECTOR: 000h-01h-01h
::     +4  0C        PARTITION ID:          Win95 FAT32 (LBA)
::     +5  FE FF FF  END CYL-HEAD-SECTOR:   3FFh-FEh-3Fh
::     +8  0000003F  START SECTOR:          63
::     +C  0950E482  NUMBER OF SECTORS:     156296322
::  
::  1-0 Win95 FAT32 (LBA) Boot Record (0000003Fh)
::  0000:  EB FE 90 4D 53 57 49 4E-34 2E 31 00 02 40 20 00   [ ���MSWIN4.1  @   ]
::  0010:  02 00 00 00 00 F8 00 00-3F 00 FF 00 3F 00 00 00   [      �  ? � ?    ]
::  0020:  82 E4 50 09 83 4A 00 00-00 00 00 00 02 00 00 00   [ ��P �J           ]
::  0030:  01 00 06 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0040:  80 00 29 C9 09 14 75 53-54 33 38 30 30 31 31 41   [ � )�  uST380011A ]
::  0050:  20 20 46 41 54 33 32 20-20 20 00 00 00 00 00 00   [   FAT32          ]
::  0060:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0070:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0080:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0090:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00A0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00B0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00C0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00D0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00E0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  00F0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0100:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0110:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0120:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0130:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0140:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0150:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0160:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0170:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0180:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0190:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01A0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01B0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01C0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01D0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01E0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  01F0:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 55 AA   [               U� ]
::  
::  Note -
::  There may be a *fault* in the above Boot sector. The bytes "EB 58 90",
::  which ought to begin the sector, are not present; and the rest of the
::  sector does not look like any other Boot sector above.
::  
::  
::  1 - Partition table entry = 1  << Empty >>
::  01CE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  1 - Partition table entry = 2  << Empty >>
::  01DE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  1 - Partition table entry = 3  << Empty >>
::  01EE:  00 00 00 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  00        STATUS:                Inactive
::     +1  00 00 00  START CYL-HEAD-SECTOR: 000h-00h-00h
::     +4  00        PARTITION ID:          Empty
::     +5  00 00 00  END CYL-HEAD-SECTOR:   000h-00h-00h
::     +8  00000000  START SECTOR:          0
::     +C  00000000  NUMBER OF SECTORS:     0
::  
::  MBRS011 Geometry was not saved. Assuming HH = FF, SS = 3F
::  
::  [ PARTITION MAP - LBA ]
::  
::            ABSOLUTE          PART-TABLE
::         START     END      START    BLOCKS
::        ======== ========  ======== ========
::  1-0 : 0000003F 0950E4C0  0000003F 0950E482  Win95 FAT32 (LBA)
::  
::  
::  *** Note on Ending CHS Values ***
::  A second use of the MBRSCAN program 4 months later showed a strangely
::  different result in the Primary DOS Partition for the *ending* CHS values;
::  and the contents of the Partition boot sector (sector 3F hex) (CHS 0-1-1)
::  are VERY different to their previous state -
::  
::  1 - Partition table entry = 0  << Win95 FAT32 (LBA) >>
::  01BE:  80 01 01 00 0C FE BF 00-3F 00 00 00 82 E4 50 09   [ �    �� ?   ��P  ]
::         ST HH CS CC ID hh cs cc START-SEC   NUMBER-SEC
::     +0  80        STATUS:                Active
::     +1  01 01 00  START CYL-HEAD-SECTOR: 000h-01h-01h
::     +4  0C        PARTITION ID:          Win95 FAT32 (LBA)
::     +5  FE BF 00  END CYL-HEAD-SECTOR:   200h-FEh-3Fh
::     +8  0000003F  START SECTOR:          63
::     +C  0950E482  NUMBER OF SECTORS:     156296322
::  
::  1-0 Win95 FAT32 (LBA) Boot Record (0000003Fh)
::  0000:  EB 58 90 4D 53 57 49 4E-34 2E 31 00 02 40 20 00   [ �X�MSWIN4.1  @   ]
::  0010:  02 00 00 00 00 F8 00 00-3F 00 FF 00 3F 00 00 00   [      �  ? � ?    ]
::  0020:  82 E4 50 09 83 4A 00 00-00 00 00 00 02 00 00 00   [ ��P �J           ]
::  0030:  00 00 06 00 00 00 00 00-00 00 00 00 00 00 00 00   [                  ]
::  0040:  80 00 29 E5 0E 00 00 53-54 33 38 30 30 31 31 41   [ � )�   ST380011A ]
::  0050:  20 20 46 41 54 33 32 20-20 20 FA 33 C9 8E D1 BC   [   FAT32   �3ɎѼ ]
::  0060:  F8 7B 8E C1 BD 78 00 C5-76 00 1E 56 16 55 BF 22   [ �{���x �v  V U�" ]
::  0070:  05 89 7E 00 89 4E 02 B1-0B FC F3 A4 8E D9 BD 00   [  �~ �N � ��ٽ  ]
::  0080:  7C C6 45 FE 0F 8B 46 18-88 45 F9 38 4E 40 7D 25   [ |�E� �F �E�8N@}% ]
::  0090:  8B C1 99 BB 00 07 E8 97-00 72 1A 83 EB 3A 66 A1   [ ����  �- r ��:f� ]
::  00A0:  1C 7C 66 3B 07 8A 57 FC-75 06 80 CA 02 88 56 02   [  |f; �W�u �� �V  ]
::  00B0:  80 C3 10 73 ED BF 02 00-83 7E 16 00 75 45 8B 46   [ �� s��  �~  uE�F ]
::  00C0:  1C 8B 56 1E B9 03 00 49-40 75 01 42 BB 00 7E E8   [  �V �  I@u B� ~� ]
::  00D0:  5F 00 73 26 B0 F8 4F 74-1D 8B 46 32 33 D2 B9 03   [ _ s&��Ot �F23ҹ  ]
::  00E0:  00 3B C8 77 1E 8B 76 0E-3B CE 73 17 2B F1 03 46   [  ;�w �v ;�s +� F ]
::  00F0:  1C 13 56 1E EB D1 73 0B-EB 27 83 7E 2A 00 77 03   [   V ��s �'�~* w  ]
::  0100:  E9 FD 02 BE 7E 7D AC 98-03 F0 AC 84 C0 74 17 3C   [ �� �~}�� ��t < ]
::  0110:  FF 74 09 B4 0E BB 07 00-CD 10 EB EE BE 81 7D EB   [ �t � �  � �}� ]
::  0120:  E5 BE 7F 7D EB E0 98 CD-16 5E 1F 66 8F 04 CD 19   [ �}���� ^ f� �  ]
::  0130:  41 56 66 6A 00 52 50 06-53 6A 01 6A 10 8B F4 60   [ AVfj RP Sj j ��` ]
::  0140:  80 7E 02 0E 75 04 B4 42-EB 1D 91 92 33 D2 F7 76   [ �~  u �B� ��3��v ]
::  0150:  18 91 F7 76 18 42 87 CA-F7 76 1A 8A F2 8A E8 C0   [  ��v B���v ���� ]
::  0160:  CC 02 0A CC B8 01 02 8A-56 40 CD 13 61 8D 64 10   [ �  ̸  �V@� a�d  ]
::  0170:  5E 72 0A 40 75 01 42 03-5E 0B 49 75 B4 C3 03 18   [ ^r @u B ^ Iu��   ]
::  0180:  01 27 0D 0A 4E 6F 20 4F-53 20 46 6F 75 6E 64 20   [  '  No OS Found  ]
::  0190:  20 20 20 20 20 20 20 FF-0D 0A 44 69 73 6B 20 49   [        �  Disk I ]
::  01A0:  2F 4F 20 45 72 72 6F 72-FF 0D 0A 49 6E 73 65 72   [ /O Error�  Inser ]
::  01B0:  74 20 4F 53 20 73 65 74-75 70 20 64 69 73 6B 2C   [ t OS setup disk, ]
::  01C0:  20 74 68 65 6E 20 70 72-65 73 73 20 61 6E 79 20   [  then press any  ]
::  01D0:  6B 65 79 0D 0A 00 00 00-49 4F 20 20 20 20 20 20   [ key     IO       ]
::  01E0:  53 59 53 4D 53 44 4F 53-20 20 20 53 59 53 7E 01   [ SYSMSDOS   SYS~  ]
::  01F0:  00 57 49 4E 42 4F 4F 54-20 53 59 53 00 00 55 AA   [  WINBOOT SYS  U� ]


rem  SATA 500GB Hard Disk
rem  ====================
rem  
rem  SATA DRV C -
rem   Partition sector = CHS 0-0-1 (LBA  0)            (MBR)
rem   Boot sector      = CHS 0-1-1 (LBA 63)
rem  
rem  SATA DRV D -
rem   Partition sector = CHS 1275-0-1 (LBA 20482875)   (EMBR 1)
rem   Boot sector      = CHS 1275-1-1 (LBA 20482938)
rem  
rem  SATA DRV E -
rem   Partition sector = CHS 11004-0-1 (LBA 176779260) (EMBR 2)
rem   Boot sector      = CHS 11004-1-1 (LBA 176779323)
rem  
rem  LOGICAL 3 (125.5 MB) -
rem   Partition sector = CHS 19458-0-1 (LBA 312592770) (EMBR 3)
rem   Boot sector      = CHS 19458-1-1 (LBA 312592833)
rem  
rem  LOGICAL 4 (7,648.1 MB) -
rem   Partition sector = CHS 19474-0-1 (LBA 312849810) (EMBR 4)
rem   Boot sector      = CHS 19474-1-1 (LBA 312849873)
rem  
rem  LOGICAL 5 (18,535.9 MB) -
rem   Partition sector = CHS 20449-0-1 (LBA 328513185) (EMBR 5)
rem   Boot sector      = CHS 20449-1-1 (LBA 328513248)
rem  
rem  LOGICAL 6 (16,182.6 MB) -
rem   Partition sector = CHS 22812-0-1 (LBA 366474780) (EMBR 6)
rem   Boot sector      = CHS 22812-1-1 (LBA 366474843)
rem  
rem  LOGICAL 7 (32,765.4 MB) -
rem   Partition sector = CHS 24875-0-1 (LBA 399616875) (EMBR 7)
rem   Boot sector      = CHS 24875-1-1 (LBA 399616938)
rem  
rem  LOGICAL 8 (32,765.4 MB) -
rem   Partition sector = CHS 29052-0-1 (LBA 466720380) (EMBR 8)
rem   Boot sector      = CHS 29052-1-1 (LBA 466720443)
rem  
rem  LOGICAL 9 (32,757.5 MB) -
rem   Partition sector = CHS 33229-0-1 (LBA 533823885) (EMBR 9)
rem   Boot sector      = CHS 33229-1-1 (LBA 533823948)
rem  
rem  LOGICAL 10 (83,509.7 MB) -
rem   Partition sector = CHS 37405-0-1 (LBA 600911325) (EMBR 10)
rem   Boot sector      = CHS 37405-1-1 (LBA 600911388)
rem  
rem  LOGICAL 11 (100,006.2 MB) -
rem   Partition sector = CHS 48051-0-1 (LBA 771939315) (EMBR 11)
rem   Boot sector      = CHS 48051-1-1 (LBA 771939378)


rem  DISK INVESTIGATOR
rem  =================
rem  
rem  Disk Investigator v1.31
rem  
rem  This program can display the following data structures in a
rem  partition, and in doing so also shows the LBA sector number:
rem  
rem    - Boot Sector (NB: Partition's Boot Sector, NOT the MBR!)
rem    - FAT 1
rem    - FAT 2
rem    - Root Directory
rem  
rem  To display the relevent data structure -
rem    1. Run the program
rem    2. Go to the VIEW menu and select DISK
rem    3. Go to the VIEW menu, and select the desired option
rem  
rem  *** Run Disk Investigator ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\HARDWARE\DI
:: DI


rem  Disk Investigator's summary of HDD structure -
rem  
rem  
rem  DISK 1, PARTITION 1
rem  Western Digital WD800JB, 80GB, Primary DOS partition
rem  
rem  Volume Label: DRIVE C
rem  Logical drive: C
rem  Physical drive: 128
rem  Total logical sectors: 20482812
rem  Cylinders: 1275
rem  Sectors per cylinder: 63
rem  Heads: 255
rem  Bytes per sector: 512
rem  File system: FAT32
rem  Sectors per Cluster: 16
rem  Number of copies of FAT: 2
rem  Sectors per FAT: 9992
rem  Start sector for FAT1: 32
rem  Start sector for FAT2: 10024
rem  Root DIR Sector: 20016
rem  Root DIR Cluster: 2
rem  2nd Cluster Start Sector: 20016
rem  Ending Cluster: 1278925
rem  Media Descriptor: 248
rem  Root Entries: 0
rem  Heads: 255
rem  Hidden sectors: 63
rem  Backup boot sector: 6
rem  Reserved sectors: 32
rem  FS Info sector: 0
rem  Sectors per track: 63
rem  File system version: 0
rem  SerialVolumeID: 00000DDF
rem  
rem  
rem  DISK 1, PARTITION 2
rem  Western Digital WD800JB, 80GB, Logical 1 partition
rem  
rem  Volume Label: DATA
rem  Logical drive: E
rem  Physical drive: 0
rem  Total logical sectors: 135813447
rem  Cylinders: 8454
rem  Sectors per cylinder: 63
rem  Heads: 255
rem  Bytes per sector: 512
rem  File system: FAT32
rem  Sectors per Cluster: 64
rem  Number of copies of FAT: 2
rem  Sectors per FAT: 16577
rem  Start sector for FAT1: 32
rem  Start sector for FAT2: 16609
rem  Root DIR Sector: 33186
rem  Root DIR Cluster: 2
rem  2nd Cluster Start Sector: 33186
rem  Ending Cluster: 2121567
rem  Media Descriptor: 248
rem  Root Entries: 0
rem  Heads: 255
rem  Hidden sectors: 35706
rem  Backup boot sector: 6
rem  Reserved sectors: 32
rem  FS Info sector: 1
rem  Sectors per track: 63
rem  File system version: 0
rem  SerialVolumeID: 235815FC
rem  
rem  
rem  DISK 2, PARTITION 1
rem  SeaGate, 18GB, Primary DOS partition
rem  
rem  Volume Label: M02GB2
rem  Logical drive: D
rem  Physical drive: 129
rem  Total logical sectors: 37961532
rem  Cylinders: 2363
rem  Sectors per cylinder: 63
rem  Heads: 255
rem  Bytes per sector: 512
rem  File system: FAT32
rem  Sectors per Cluster: 32
rem  Number of copies of FAT: 2
rem  Sectors per FAT: 9264
rem  Start sector for FAT1: 32
rem  Start sector for FAT2: 9296
rem  Root DIR Sector: 18560
rem  Root DIR Cluster: 2
rem  2nd Cluster Start Sector: 18560
rem  Ending Cluster: 1185718
rem  Media Descriptor: 248
rem  Root Entries: 0
rem  Heads: 255
rem  Hidden sectors: 63
rem  Backup boot sector: 6
rem  Reserved sectors: 32
rem  FS Info sector: 1
rem  Sectors per track: 63
rem  File system version: 0
rem  SerialVolumeID: 183F11F0
rem  
rem  
rem  DISK 3, PARTITION 1
rem  USB Pen Drive, 8GB, Primary DOS partition
rem  
rem  Volume Label: USBDISKPRO
rem  Logical drive: G
rem  Physical drive: 130
rem  Total logical sectors: 15658976
rem  Cylinders: 975
rem  Sectors per cylinder: 63
rem  Heads: 16
rem  Bytes per sector: 512
rem  File system: FAT32
rem  Sectors per Cluster: 8
rem  Number of copies of FAT: 2
rem  Sectors per FAT: 15264
rem  Start sector for FAT1: 64
rem  Start sector for FAT2: 15328
rem  Root DIR Sector: 30592
rem  Root DIR Cluster: 2
rem  2nd Cluster Start Sector: 30592
rem  Ending Cluster: 1953549
rem  Media Descriptor: 248
rem  Root Entries: 0
rem  Heads: 16
rem  Hidden sectors: 32
rem  Backup boot sector: 8
rem  Reserved sectors: 64
rem  FS Info sector: 1
rem  Sectors per track: 32
rem  File system version: 0
rem  SerialVolumeID: F713BD59


::  /--------------------------------------------------------------------/  ::


rem                      FILE ALLOCATION TABLE
rem                      =====================


rem  CONTENTS OF THE FAT
rem  ===================
rem  
rem  A cluster is a group of sectors containing user data.
rem  
rem  Examples:
rem    A  4K cluster has  8 sectors in it ( 8 x 512 =  4,096 bytes)
rem    A 16K cluster has 32 sectors in it (32 x 512 = 16,384 bytes)
rem    A 32K cluster has 64 sectors in it (64 x 512 = 32,768 bytes)
rem  
rem  The data area in a Partition starts at cluster 2. The first
rem  two entries in the FAT (4 bytes each) are therefore not needed,
rem  so are used to identify the FAT itself (i.e. 8 "admin" bytes).
rem  
rem  In the first entry, the first byte is the media descriptor (F8),
rem  & the other 3 bytes are 0F FF FF (written backwards as FF FF 0F).
rem  
rem  The second entry is the end-of-cluster-chain marker (0F FF FF FF,
rem  written backwards as FF FF FF 0F). This is the Dirty Shutdown
rem  flag: its value changes if the last shutdown was not clean,
rem  or if a disk I/O error was detected last session.
rem  
rem  Note: In *all* Disks on the Tiny PC, the second entry in
rem        the FAT is actually 07 FF FF FF (written as FF FF FF 07)!
rem  
rem        (Viewed while the disk is in use; so it is presumably
rem        the value of the "dirty shutdown" flag! If this value
rem        is set on bootup, then NOT reset to FF FF FF 0F on
rem        shutdown, it shows Windows on the next bootup that
rem        the computer was not properly shut down last time.)
rem  
rem  Each cluster has a 4-byte entry in the FAT. The entry tells you
rem  whether the cluster has data in it (if the entry is 0 there is
rem  no data in the cluster, otherwise the entry is a cluster number
rem  or a special function); and whether it's the end of the data in
rem  the file (the entry 0F FF FF FF is the final entry in the chain).
rem  
rem  NB: On disk the 4 bytes are (as always) written BACKWARDS,
rem      so for instance 0F FF FF FF reads on disk as FF FF FF 0F
rem  
rem  Value                Description
rem  -----                -----------
rem  00000000             Free cluster (No data in it)
rem  00000001             Reserved cluster, do not use
rem                       (NB: Written 01 00 00 00)
rem  00000002 - 0FFFFFEF  Number of the next cluster
rem                       (NB: Written 02 00 00 00 to EF FF FF 0F)
rem  0FFFFFF0 - 0FFFFFF6  Reserved cluster, do not use
rem                       (NB: Written F0 FF FF 0F to F6 FF FF 0F)
rem  0FFFFFF7             Bad sector in cluster or reserved cluster
rem                       (NB: Written F7 FF FF 0F)
rem  0FFFFFF8 - 0FFFFFFF  Last cluster in file (written FF FF FF 0F)
rem  
rem  NB: Any entry which (on disk) begins with F has a SPECIAL function,
rem      i.e. if it starts with F it's a Function, NOT a cluster number!
rem  
rem  The FAT stores the starting location of the file and each additional
rem  cluster used to store the file.
rem  
rem  NB: See also http://en.wikipedia.org/wiki/File_Allocation_Table


rem  FINDFAT
rem  =======
rem  
rem  Svend's Utilities: FINDPART for DOS (version 4.72)
rem  
rem  NB: In this version of Svend's Utilities the FINDFAT function is
rem      a switch (i.e. an option) in FINDPART, not a seperate program
rem  
rem  The FINDFAT function can be used for two purposes:
rem  1. To identify the starting sector of the 1st and 2nd FAT
rem     on a working Disk, so as to BACKUP the FAT.
rem  2. To locate a lost or damaged FAT on a damaged Disk.
rem  
rem  
rem  SYNTAX of FINDFAT -
rem  
rem  Usage:
rem  FINDPART FINDFAT {disk} [comprehensive | {cyl} {cyl}] {file}
rem  
rem  Specify the number of the Disk to search, e.g. 1
rem  [NB: Valid numbers are 1, 2, 3 or 4]
rem  (Alternatively, to search *all* Disks specify ALL)
rem  
rem  To search the *entire* Disk (i.e. all partitions) specify
rem  COMPREHENSIVE
rem  (Alternatively, to do a quicker search, specify cylinder
rem  number to begin the search from and to end the search at)
rem  
rem  Specify the name of the file to save the search results in
rem  (which MUST have the filetype .TXT)


rem  *** Search Primary Partition only ***
rem  
rem  ** Find FAT on Disk 1 **
rem  ** Save the report to a file **
:: FINDPART FINDFAT 1 0 1 F:\FAT_DSK1.TXT
rem  
rem  ** Find FAT on Disk 2 **
rem  ** Save the report to a file **
:: FINDPART FINDFAT 2 0 1 F:\FAT_DSK2.TXT
rem  
rem  ** Find FAT on ALL Disks **
rem  ** Save the report to a file **
:: FINDPART FINDFAT ALL 0 1 F:\FAT_ALL.TXT


rem  *** Search Primary & Extended Partitions ***
rem  
rem  ** Find FAT on Disk 1 **
rem  ** Save the report to a file **
:: FINDPART FINDFAT 1 comprehensive F:\FAT_DSK1_.TXT
rem  
rem  ** Find FAT on Disk 2 **
rem  ** Save the report to a file **
:: FINDPART FINDFAT 2 comprehensive F:\FAT_DSK2_.TXT
rem  
rem  ** Find FAT on ALL Disks **
rem  ** Save the report to a file  **
:: FINDPART FINDFAT ALL comprehensive F:\FAT_ALL_.TXT


rem  NORTON DISKEDIT
rem  ===============
rem  
rem  Norton's DiskEdit (2002) can identify all File Allocation Tables
rem  on the hard disk (and so help build up a picture of the disk's
rem  structure), by searching for the unique markers F8 FF FF 0F and
rem  F8 FF FF 07 (one of which is in the first sector of every FAT).
rem  
rem  When the program starts, in "Type" select "Physical disks"; then
rem  choose the damaged disk, then click "OK". To open the search tool:
rem  
rem    TOOLS - FIND... (or press CTRL + S)
rem  
rem  Type the text to search for (the unique marker) into the box
rem  marked "Hex", then select "Ignore Case", then click on "Find".
rem  
rem  NB: Note that this unique signature is *also* present in every
rem      backup copy of the FAT stored on the disk.
rem  
rem  *** Run Norton DiskEdit 2002: FAT32, HDD exceeding 32GB ***
rem   **       (DISKEDIT.EXE in Norton Utilities 2002)       **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE
:: MOUSE
:: SET PATH=%path%;F:\SAVED\RECOVERY\DISKEDIT\NORTON\2002
:: DISKEDIT


rem  NORTON DISKEDIT
rem  ===============
rem  
rem  Norton's DiskEdit (2002) can show the sector numbers assigned
rem  to the 1st FAT and 2nd FAT in the selected partition.
rem  
rem  When the program starts, in "Type" select "Logical disks"; then
rem  choose a partition, then click "OK". When the program has finished
rem  scanning that partition, go to:
rem  
rem    OBJECT - SECTOR (or press ALT + S)
rem  
rem  The sector number displayed is NOT the LBA sector! It's only the
rem  sector's number within the selected partition. To convert it to
rem  the LBA number, add the number of sectors before this partition,
rem  from the "Sectors Before" field in the MBR.
rem  
rem  NB: If this is the Primary DOS partition, the number of sectors
rem      to add is (always) 63.
rem  
rem  *** Run PowerQuest's Partition Table Editor ***
rem   **    (Displays the MBR partition table)   **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE;F:\SAVED\RECOVERY
:: MOUSE
:: PTEDIT
rem  
rem  *** Run Norton DiskEdit 2002: FAT32, HDD exceeding 32GB ***
rem   **       (DISKEDIT.EXE in Norton Utilities 2002)       **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE
:: MOUSE
:: SET PATH=%path%;F:\SAVED\RECOVERY\DISKEDIT\NORTON\2002
:: DISKEDIT


rem  CLUSTERS USED BY A FILE
rem  =======================
rem  
rem  Norton's DiskEdit (2002) can view the cluster information in the FAT
rem  that identifies the clusters used by a file (below: "FILE CLUSTERS")


rem  SIZE OF FAT
rem  ===========
rem  
rem  FAT32 uses 4 bytes of the FAT to record each data cluster. So
rem  1 sector in the FAT (512 bytes) records 128 clusters (512 / 4).
rem  
rem  NB: If cluster size is 8KB (i.e. 1 cluster = 16 sectors), then
rem      128 clusters = 128 x 16 = 2,048 sectors
rem  
rem  NB: If cluster size is 16KB (i.e. 1 cluster = 32 sectors), then
rem      128 clusters = 128 x 32 = 4,096 sectors
rem  
rem  NB: If cluster size is 32KB (i.e. 1 cluster = 64 sectors), then
rem      128 clusters = 128 x 64 = 8,192 sectors [HDD exceeding 32GB]
rem  
rem  In each case, this is cluster size (in KB) multiplied by 256.
rem  
rem  
rem  To calculate the *maximum* size of the FAT (in sectors):
rem  
rem  Take the number of sectors in the Partition and subtract 32
rem  (the number of Reserved Sectors); then divide that result by
rem  cluster size multiplied by 256 (i.e. 2,048 or 4,096 or 8,192)
rem  
rem  NB: Be aware that this *might* result in a FAT size slightly
rem      larger than on the actual disk, since in actuality no FAT
rem      entries are needed for the space occupied by the FAT itself
rem      (so the calculated value should be checked, by a physical
rem      examination of the disk to see where Root Directory begins)
rem  
rem  NB: The size of a FAT can be calculated from the filesize (in KB)
rem      of any backup copy of it, as the size of a FAT in sectors is
rem      equal to its file size (in KB) x 2 (since 1 sector = 0.5 KB)
rem  
rem  
rem  Calculation based on Allocation Units:
rem  
rem  To calculate the size of the FAT (in bytes), multiply the number of
rem  Allocation Units in the partition (i.e. the number of Clusters) by 4
rem  (because the FAT uses 4 bytes to record the address of each Cluster)
rem  
rem  Then add 8 bytes, as the FAT allocates 8 bytes for "admin" purposes.
rem  
rem  Divide the result by 512 to calculate the size of the FAT in sectors
rem  (because there are 512 bytes in a sector)
rem  
rem  Size of FAT (in sectors) = ( ( Number of Clusters x 4 ) + 8 ) / 512
rem  
rem  NB: Round up the result to the next whole number of sectors -
rem      INT ( Result + 0.99 )
rem  
rem  
rem  Calculate the size of the FAT in KB:
rem  
rem  (a) Divide the size of the FAT in sectors by 2
rem      (because 1 sector = 0.5 KB)
rem  
rem  (b) Divide the size of the FAT in bytes by 1,024
rem      NB: Round-up the result to the next whole KB
rem  
rem  
rem  Size of System Area:
rem  
rem  To calculate the total size of the System Area, add together:-
rem  
rem   1. The 63 "Hidden sectors" (starting with the Partition Table)
rem   2. The 32 "Reserved sectors" (starting with the Boot Sector)
rem   3. The size of the FAT, multiplied by 2 (there are 2 copies)
rem  
rem   NB: The "Data Area" begins with the cluster containing the
rem       start of the Root Directory Table (a.k.a. Cluster no.2)


rem  SRCFAT
rem  ======
rem  
rem  SRCFat v1.3(c)2001 - The W0rm
rem  Usage: SRCFat {drive:} {filename} {switch}
rem  
rem  Program to BACKUP and RESTORE the 1st or 2nd FAT
rem  
rem  SRCFat can save, restore and check the FAT on a FAT32 Disk
rem  (NB: Replaces older utilities that don't support FAT32)
rem  
rem  The program can save and restore the first or second FAT,
rem  or both; and can restore the 2nd FAT over a damaged 1st FAT
rem  (i.e. restore the second FAT to the first), or vice versa.
rem  
rem  Switches:
rem     /S - Save FAT table to file
rem     /R - Restore FAT table from file
rem     /C - Compare FAT table to file
rem     /2 - Use the second FAT copy
rem  
rem  Note:
rem  This program can *also* restore a FAT which was saved by
rem  another program, e.g. by FINDPART.EXE (provided no header
rem  or other extra data was saved along with the sector data).
rem  
rem  Notes:
rem  
rem  1. This program can compare a backup file with the on-disk FAT.
rem  
rem  2. Norton's DiskEdit has a function which can compare two backup
rem     files: split the window (View - Split Window), load both files
rem     (Object - File), then compare them (Tools - Compare Windows).
rem     The program halts at the first difference between the files.
rem     NB: It can find subsequent differences by moving the cursor to
rem         the next line, then restarting (Tools - Compare Windows).


rem  BACKUP THE FAT
rem  ==============

rem  ** Save 1st FAT **
:: SRCFAT C: F:\SAVED\SRC_FAT1.C /S
:: SRCFAT D: F:\SAVED\SRC_FAT1.D /S
:: SRCFAT E: F:\SAVED\SRC_FAT1.E /S

rem  ** Save 2nd FAT **
:: SRCFAT C: F:\SAVED\SRC_FAT2.C /S /2
:: SRCFAT D: F:\SAVED\SRC_FAT2.D /S /2
:: SRCFAT E: F:\SAVED\SRC_FAT2.E /S /2

rem  *** Alternative Backup Routine ***
rem  ** In practice, the following Backup routine is preferable **
rem  ** This saves 4 backup copies instead of only a single one **
rem  ** (so guards against overwriting with a *faulty* backup)  **
rem  [NB: SERCOPY will *not* save to Root, only to a Subdirectory]
rem  
rem  ** Save 1st FAT, Drive C: **
:: SRCFAT C: C:\SAVED\C_FAT1.BIN /S
:: SERCOPY   C:\SAVED\C_FAT1.BIN    F:\SAVED /L:4 /D:2 /Q
rem  
rem  ** Save 1st FAT, Drive D: **
:: SRCFAT D: D:\SAVED\D_FAT1.BIN /S
:: SERCOPY   D:\SAVED\D_FAT1.BIN    F:\SAVED /L:4 /D:2 /Q
rem  
rem  ** Save 1st FAT, Drive E: **
:: SRCFAT E: E:\SAVED\E_FAT1.BIN /S
:: SERCOPY   E:\SAVED\E_FAT1.BIN    F:\SAVED /L:4 /D:2 /Q

rem  
rem  ** Save 2nd FAT, Drives C:, D: & E:
:: SRCFAT C: F:\SAVED\C_FAT2.BIN /S /2
:: SRCFAT D: F:\SAVED\D_FAT2.BIN /S /2
:: SRCFAT E: F:\SAVED\E_FAT2.BIN /S /2


rem  RESTORE THE FAT
rem  ===============

rem  *** Help Screen Operations ***
rem  
rem  ** Display Help screen **
:: SRCFAT /?
rem  
rem  ** Save Help screen to file **
:: SRCFAT /? > F:\SRCFAT.txt


rem  *** Disk Operations in DOS under Win 98/ME ***
rem  
rem  ** Enable direct disk access **
:: LOCK C:
:: LOCK D:
:: LOCK E:
rem  
rem  Note:
rem  In MS-DOS v8.0 the HDD is protected (the default state) by an internal
rem  COMMAND.COM function that prevents direct disk access by any program
rem  other than DOS itself. The HDD must be locked - NOT unlocked! - to
rem  enable SRCFAT to write to the disk. [NB: DOS v8.0 comes with Win98/ME]


rem  *** Operations on 1st FAT ***

rem  ** Compare 1st FAT to Backup file of 1st FAT **
rem  Before using, insert filename of LATEST backup!
:: SRCFAT C: F:\SAVED\C_FAT1.000 /C
:: SRCFAT D: F:\SAVED\D_FAT1.000 /C
:: SRCFAT E: F:\SAVED\E_FAT1.000 /C

rem  ** Compare 1st FAT to Backup File of 2nd FAT **
:: SRCFAT C: F:\SAVED\C_FAT2.BIN /C
:: SRCFAT D: F:\SAVED\D_FAT2.BIN /C
:: SRCFAT E: F:\SAVED\E_FAT2.BIN /C

rem  ** Save a backup of damaged 1st FAT **
rem  (May give error: "Error, could not read sector")
:: SRCFAT C: F:\SAVED\BAD_FAT1.C /S
:: SRCFAT D: F:\SAVED\BAD_FAT1.D /S
:: SRCFAT E: F:\SAVED\BAD_FAT1.E /S

rem  ** Restore 1st FAT from Backup file of 1st FAT **
rem  Before using, insert filename of LATEST backup!
:: SRCFAT C: F:\SAVED\C_FAT1.000 /R
:: SRCFAT D: F:\SAVED\D_FAT1.000 /R
:: SRCFAT E: F:\SAVED\E_FAT1.000 /R

rem  ** Restore 1st FAT from Backup file of 2nd FAT **
:: SRCFAT C: F:\SAVED\C_FAT2.BIN /R
:: SRCFAT D: F:\SAVED\D_FAT2.BIN /R
:: SRCFAT E: F:\SAVED\E_FAT2.BIN /R

rem  Note:
rem  If the first 8 bytes of the 1st FAT are replaced with 00000000
rem  Win9x will automatically default to using the 2nd FAT instead
rem  (i.e. treats the 1st FAT as corrupt). This might be tried
rem  *before* attempting to replace the 1st FAT with the 2nd!


rem  *** Operations on 2nd FAT ***

rem  ** Compare 2nd FAT to Backup file of 1st FAT **
rem  Before using, insert filename of LATEST backup!
:: SRCFAT C: F:\SAVED\C_FAT1.000 /C /2
:: SRCFAT D: F:\SAVED\D_FAT1.000 /C /2
:: SRCFAT E: F:\SAVED\E_FAT1.000 /C /2

rem  ** Compare 2nd FAT to Backup File of 2nd FAT **
:: SRCFAT C: F:\SAVED\C_FAT2.BIN /C /2
:: SRCFAT D: F:\SAVED\D_FAT2.BIN /C /2
:: SRCFAT E: F:\SAVED\E_FAT2.BIN /C /2

rem  ** Save a backup of damaged 2nd FAT **
rem  (May give error: "Error, could not read sector")
:: SRCFAT C: F:\SAVED\BAD_FAT2.C /S /2
:: SRCFAT D: F:\SAVED\BAD_FAT2.D /S /2
:: SRCFAT E: F:\SAVED\BAD_FAT2.E /S /2

rem  ** Restore 2nd FAT from Backup file of 1st FAT **
rem  Before using, insert filename of LATEST backup!
:: SRCFAT C: F:\SAVED\C_FAT1.000 /R /2
:: SRCFAT D: F:\SAVED\D_FAT1.000 /R /2
:: SRCFAT E: F:\SAVED\E_FAT1.000 /R /2

rem  ** Restore 2nd FAT from Backup file of 2nd FAT **
:: SRCFAT C: F:\SAVED\C_FAT2.BIN /R /2
:: SRCFAT D: F:\SAVED\D_FAT2.BIN /R /2
:: SRCFAT E: F:\SAVED\E_FAT2.BIN /R /2

rem  Note:
rem  This procedure should normally only be necessary if
rem  BOTH copies of the FAT are corrupted on a damaged Disk
rem  *and* the backup copy of the 1st FAT is ALSO corrupted.
rem  In theory, that situation can never arise! The backup copy
rem  should be on a different Disk (i.e. at F:\SAVED).


rem  USING THE 2ND FAT
rem  =================
rem  
rem  On a FAT32 partition, FAT mirroring can be disabled, allowing
rem  a copy of the FAT (instead of the first FAT) to be active.
rem  
rem  NB: To disable FAT mirroring, edit the appropriate byte in the
rem      Boot Record of the Partition in question (see above).


::  /--------------------------------------------------------------------/  ::


rem                           ROOT DIRECTORY
rem                           ==============


rem  ROOT DIRECTORY TABLE
rem  ====================
rem  
rem  The Root Directory table usually immediately follows the 2nd FAT
rem  (i.e. begins in the first sector after the 2nd FAT).
rem  
rem  NB: Its location is specified by an entry in the Partition's
rem      Boot Sector at offset 44, i.e. in bytes 45-48.
rem  
rem  This makes the Root Directory very vulnerable: anything which
rem  damages the 2nd FAT might also wipe out the Root Directory table!
rem  This table MUST be backed up!
rem  
rem  In a FAT32 partition there is NO limit to the number of entries
rem  (i.e. files) in the Root Directory. If the cluster size is 32K,
rem  a block of 64 sectors (i.e. 1 cluster) is reserved for the Root
rem  Directory table: the first 64 sectors after the 2nd FAT. When
rem  this is full, the table can continue anywhere in the partition
rem  (just like any other file); a pointer is set to the next cluster
rem  it occupies.
rem  
rem  NB: If all the entries have only a Short Name (so no Long File Name
rem      entries are required), a maximum of 1,024 files and directories
rem      can be stored in a directory table occupying 64 sectors.
rem  
rem  
rem  Address of Root Directory Table -
rem  
rem  Western Digital WD800JB 80GB (New bootable HDD)
rem    Primary DOS Partition (Drive C:) = CHS 1-63-46    (LBA:     20,079)
rem    1st Logical Partition (Drive E:) = CHS 1277-17-49 (LBA: 20,516,124)
rem  
rem  Western Digital WD800JB 80GB (Drive D: HDD)
rem    Primary DOS Partition (Drive D:) = CHS 2-97-9     (LBA:     38,249)
rem  
rem  M02GB2: SeaGate ST320423A 18GB (Win98 HDD)
rem    Primary DOS Partition (Drive D:) = CHS 1-40-39    (LBA:     18,623)
rem  
rem  Seagate ST380011A 80GB (Broken HDD)
rem    Primary DOS Partition (Drive C:) = CHS 2-97-5
rem  
rem  NB: CHS 0-0-1 = LBA 0 (i.e. Add 1 to convert LBA into actual sectors)
rem  
rem  
rem  Finding the Root Directory Table:
rem  
rem  The Root Directory Table contains the Volume label (i.e. name)
rem  of the partition. Norton's DiskEdit can find the Table by
rem  searching for that name (if it's a unique name).
rem  
rem  The Root Directory Table on a Windows system also contains the
rem  (possibly) unique directory entry RECYCLED (unique at least in
rem  its Hex form: followed by 3 spaces and a unique file attribute).
rem  That string can be searched for, using Norton's DiskEdit.
rem  
rem  Hex characters for "RECYCLED" (8.3 filename + file attribute):
rem   52 45 43 59 43 4C 45 44 20 20 20 16
rem  
rem  *** Run Norton DiskEdit 2002: FAT32, HDD exceeding 32GB ***
rem   **       (DISKEDIT.EXE in Norton Utilities 2002)       **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE
:: MOUSE
:: SET PATH=%path%;F:\SAVED\RECOVERY\DISKEDIT\NORTON\2002
:: DISKEDIT


rem  NORTON DISKEDIT
rem  ===============
rem  
rem  Norton's DiskEdit 2002 can show the sector number assigned to
rem  the Root Directory table in the selected partition. Go to:
rem  
rem    OBJECT - SECTOR (or press ALT + S)
rem  
rem  NB: To enable this option, "Logical Disks" must be selected in
rem      DiskEdit's opening screen (in order to display the Disk's
rem      partition structure, rather than its physical structure).
rem  
rem  *** Run Norton DiskEdit 2002: FAT32, HDD exceeding 32GB ***
rem   **       (DISKEDIT.EXE in Norton Utilities 2002)       **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE
:: MOUSE
:: SET PATH=%path%;F:\SAVED\RECOVERY\DISKEDIT\NORTON\2002
:: DISKEDIT
rem  
rem  The sector number displayed is NOT the LBA sector, but only the
rem  sector's number within the selected partition. To convert it to
rem  the LBA number, add the number of sectors before this partition
rem  from the partition table (the "Sectors Before" field).
rem  
rem  NB: If this is the Primary DOS partition, the number of sectors
rem      to add is invariably 63.
rem  
rem  *** Run PowerQuest's Partition Table Editor ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE;F:\SAVED\RECOVERY
:: MOUSE
:: PTEDIT


rem  CONVERT FROM CHS TO SECTORS
rem  ===========================
rem  
rem  The utilities which can identify the location of the FAT
rem  give the result by specifying: (a) its starting sector
rem  (a CHS value), and (b) its size (in sectors).
rem  
rem  The following calculation uses that information to calculate
rem  the location of the Root Directory Table (giving the result
rem  as a CHS value, needed to make a backup copy of that Table) -
rem  
rem  Step 1: Convert the CHS value of the 1st sector of the FAT
rem  from CHS to sectors:
rem  
rem    Cylinders x 255 x 63 = ______
rem    Heads     x 63       = ______
rem    Sectors   x 1        = ______
rem                   Total = ______ sectors 
rem  
rem  Step 2: Multiply the size of the FAT (in sectors) by two,
rem  as the FAT32 file system uses two FATs (main and backup).
rem  
rem  Step 3: Add the result from Step 1 and the result from Step 2
rem  together. The total is the sector number of the start of the
rem  Root Directory Table.
rem  
rem  Step 4: Convert the total into a CHS value:
rem  
rem    (a) 1 cylinder = 255 heads x 63 sectors = 16,065 sectors
rem        So total from Step 3 / 16,065 = cylinders
rem        NB: Carry any remainder to (b) below
rem  
rem    (b) 1 Head = 63 sectors
rem        So remainder from (a) / 63 = heads
rem        NB: Carry any remainder to (c) below
rem  
rem    (c) 1 sector = 1 sector
rem        So remainder from (b) / 1 = sectors


rem  Examples -
rem  
rem  
rem  Disk 1: WD800JB 80GB (Drive C: & E:)
rem  
rem  *** Find the starting sector of *all* FATs on Disk 1 ***
:: FINDPART FINDFAT 1 comprehensive FAT_DSK1.TXT
rem  
rem  Result for Disk 1:
rem  -----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
rem      0   1 33  9992  8      2  9992     0     0     0 001203   5060
rem   1275   1 33 16577 32      2 16577     0     0     0 081104  13704
rem  
rem  
rem  Partition No.1 (Drive C:) -
rem  
rem  Step 1:
rem  Convert the CHS value of the 1st sector of the FAT to sectors
rem    CHS 0-1-33 = (0 x 255 x 63) + (1 x 63) + (33 x 1) = 96
rem  
rem  Step 2:
rem  Multiply the size of the FAT (in sectors) by 2
rem    2 x 9,992 = 19,984
rem  
rem  Step 3:
rem  Add the result of the first and second calculations
rem    96 + 19,984 = 20,080
rem  
rem  Step 4:
rem  Convert the result to CHS
rem    20,080 / 16,065 =  1 cylinder (Remainder = 4,015)
rem     4,015 /     63 = 63 heads    (Remainder = 46)
rem        46 /      1 = 46 sectors
rem  So Root Directory Table starts at address CHS 1-63-46
rem  
rem  
rem  Partition No.2 (Drive E:) -
rem  
rem  Step 1:
rem  Convert the CHS value of the 1st sector of the FAT to sectors
rem    CHS 1275-1-33 = (1275 x 255 x 63) + (1 x 63) + (33 x 1) = 20,482,971
rem  
rem  Step 2:
rem  Multiply the size of the FAT (in sectors) by 2
rem    2 x 16,577 = 33,154
rem  
rem  Step 3:
rem  Add the result of the first and second calculations
rem    20,482,971 + 33,154 = 20,516,125
rem  
rem  Step 4:
rem  Convert the result to CHS
rem    20,516,125 / 16,065 = 1,277 cylinder (Remainder = 1,120)
rem         1,120 /     63 =    17 heads    (Remainder = 49)
rem            49 /      1 =    49 sectors
rem  So Root Directory Table starts at address CHS 1277-17-49


rem  ** Save Root Directory of Disk 1, Primary Partition **
:: FINDPART GETSECT 1 1 63 46 64 ROOT_D1.PRI noheader badf6

rem  ** Save Root Directory of Disk 1, 1st Logical Partition **
:: FINDPART GETSECT 1 1277 17 49 64 ROOT_D1.L1 noheader badf6

rem  ** Save Root Directory of Disk 1, 2nd Logical Partition **
:: FINDPART GETSECT 1 ____ __ __ 64 ROOT_D1.L2 noheader badf6

rem  ** Save Root Directory of Disk 1, 3rd Logical Partition **
:: FINDPART GETSECT 1 ____ __ __ 64 ROOT_D1.L3 noheader badf6


rem  Disk 2: WD800JB 80GB (Drive D:)
rem  
rem  *** Find the starting sector of *all* FATs on Disk 2 ***
:: FINDPART FINDFAT 2 comprehensive FAT_DSK2.TXT
rem  
rem  Result for Disk 2:
rem  -----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
rem      0   1 33 19077 32      2 19077     0     0     0 070225  56668
rem  
rem  
rem  Partition No.1 (Drive D:) -
rem  
rem  Step 1:
rem  Convert the CHS value of the 1st sector of the FAT to sectors
rem    CHS 0-1-33 = (0 x 255 x 63) + (1 x 63) + (33 x 1) = 96
rem  
rem  Step 2:
rem  Multiply the size of the FAT (in sectors) by 2
rem    2 x 19,077 = 38,154
rem  
rem  Step 3:
rem  Add the result of the first and second calculations
rem    96 + 38,154 = 38,250
rem  
rem  Step 4:
rem  Convert the result to CHS
rem    38,250 / 16,065 =  2 cylinder (Remainder = 6,120)
rem     6,120 /     63 = 97 heads    (Remainder = 9)
rem         9 /      1 =  9 sectors
rem  So Root Directory Table starts at address CHS 2-97-9

rem  ** Save Root Directory of Disk 2, Primary Partition **
:: FINDPART GETSECT 2 2 97 9 64 ROOT_D2.PRI noheader badf6

rem  ** Save Root Directory of Disk 2, 1st Logical Partition **
:: FINDPART GETSECT 2 ____ __ __ 64 ROOT_D2.L1 noheader badf6

rem  ** Save Root Directory of Disk 2, 2nd Logical Partition **
:: FINDPART GETSECT 2 ____ __ __ 64 ROOT_D2.L2 noheader badf6

rem  ** Save Root Directory of Disk 2, 3rd Logical Partition **
:: FINDPART GETSECT 2 ____ __ __ 64 ROOT_D2.L3 noheader badf6


rem  CALCULATE THE STARTING SECTOR
rem  =============================
rem  
rem  RootStart = Sectors Before + Hidden Sectors + Reserved Sectors
rem              + (Number of FATs x SectorsPerFAT)
rem  
rem  Some of these values are in the MBR / EMBR sector & the Boot Record,
rem  which are most easily read using PowerQuest's Partition Table Editor.
rem  
rem  *** Run PowerQuest's Partition Table Editor ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE;F:\SAVED\RECOVERY
:: MOUSE
:: PTEDIT
rem  
rem  To calculate the RootStart sector of the Primary DOS partition,
rem  "Sectors Before" is nil, "Hidden Sectors" is usually 63 sectors
rem  (the entire Non-DOS partition), and "Reserved Sectors" normally
rem  comprises the first 32 sectors of the Primary DOS partition;
rem  so there are typically 95 sectors (LBA 0 to 94) prior to the FAT.


::  /--------------------------------------------------------------------/  ::


rem                               FILES
rem                               =====


rem  FILE NAMES
rem  ==========
rem  
rem  Under FAT32, a file typically has TWO names:
rem  
rem  1. A Short name, used by MS-DOS to access the file.
rem  
rem  2. A Long File Name (LFN), used by Windows to access
rem     the file. An LFN is optional; if one is not present,
rem     Windows uses the Short name instead.
rem  
rem  
rem  Short name -
rem  
rem  All files have a short filename, comprising 11 characters
rem  (also known as an 8.3 name). This is the ONLY name by which
rem  the file can be accessed under MS-DOS.
rem  
rem  It consists of an 8 character name, followed by a dot,
rem  followed by 3 more characters (known as the Extension).
rem  
rem  The name can have fewer than 8 characters; and the Extension
rem  can have fewer than 3 characters, or can be omitted entirely.
rem  
rem  Only letters of the alphabet (uppercase only), numbers 0 to 9,
rem  and the underscore character, can be used in a Short name.
rem  
rem  The Short name is the name displayed by the command DIR when
rem  the computer is booted to DOS.
rem  
rem  
rem  Long File Name -
rem  
rem  A file can, optionally, also have a Long File Name (or LFN),
rem  comprising up to 256 characters, by which Windows (but not DOS)
rem  can access the file.
rem  
rem  An LFN can contain any character on the keyboard, except the
rem  reserved characters (i.e. colon, question mark, quotation mark,
rem  forward slash, backslash, asterisk, angle-brackets).
rem  
rem  The LFN overcomes the many drawbacks of the Short name system
rem  inherited from MS-DOS; but not even the FAT32 version of MS-DOS,
rem  which underlies Windows 98/ME, can recognise an LFN.
rem  
rem  NB: Some third-party (i.e. non-Microsoft) tools can enable DOS
rem      to access a file using the Long File Name - see below.


rem  DIRECTORY TABLE
rem  ===============
rem  
rem  The Directory Table is not stored in a fixed location, nor does
rem  it have a fixed size. Each directory (folder) has such a table:
rem  which is just a file, but with a special (Directory) attribute.
rem  
rem  NB: Norton's DiskEdit can be used to locate the Directory Table,
rem      by searching the disk for the first 8 characters of the
rem      file's 8.3 file name.
rem  
rem  Filenames are stored in the Directory Table (not in the FAT).
rem  Each 8.3 file entry is 32 bytes long. LFNs are also stored in
rem  the Directory Table, alongside the 8.3 filename.
rem  
rem  The LFN (if any) is stored as one or more separate directory
rem  entries, immediately before the 8.3 filename. The LFN is stored
rem  first because the 8.3 filename is derived from it, not vice versa!
rem  
rem  
rem  Length of Directory Entry:
rem  
rem  If a file has no LFN, the directory table entry will be 32 bytes
rem  (i.e. that's the *minimum* length).
rem  
rem  Up to 640 bytes are occupied by the Long File Name (LFN); thus an
rem  entry can be a *maximum* of 672 bytes (32 bytes + 640 bytes).
rem  
rem  NB: Each directory entry can store up to 13 characters of an LFN,
rem      so several entries may be needed. Since an LFN can consist of
rem      up to 255 characters, the maximum size is 20 entries.
rem  
rem  
rem  Directory Table format (8.3 filename entry):
rem  
rem  Size     Description
rem  ----     -----------
rem  8 bytes  Filename
rem  3 bytes  Extension
rem  1 byte   Attribute:   0 = normal  (00h);  D = directory (10h)
rem                        A = archive (20h);  R = read-only (01h)
rem                        H = hidden  (02h);  S = system    (04h)
rem                        [NB: These hex values are NOT certain!]
rem  1 byte   Reserved (00h)
rem  1 byte   Time Created (Seconds)         }  If zero, might be
rem  2 bytes  Time Created (Hour & Minute)   }  a Directory entry
rem  2 bytes  Date Created
rem  2 bytes  Date Last Accessed
rem  2 bytes  Reserved (0Fh 00h or 0Ch 00h) (or 0Eh 00h)
rem  2 bytes  Time Modified
rem  2 bytes  Date Modified
rem  2 bytes  Cluster Number (Location of beginning of file)
rem  4 bytes  File Size (If zero, might be a Directory entry)
rem  
rem  Total = 32 bytes
rem  
rem  
rem  Attributes:
rem  
rem  Attrib  Meaning    Notes
rem  ------  -------    -----
rem    0     Unused     No attributes set
rem    A     Archive    File needs Archiving (i.e. backing-up), as it
rem                     has been modified since BACKUP.EXE was last run
rem    R     Read-only  File is Read-only
rem    S     System     File is a System file (i.e. part of Windows)
rem    H     Hidden     File is a Hidden file (i.e. part of Windows)
rem    D     Directory  The "file" is actually a Directory Table
rem    V     Volume     The attribute for a Long File Name entry
rem  
rem  Only 1 byte is allocated to store a file's Attributes, even though
rem  a file can have 4 different attributes set at once: i.e. R,A,S,H
rem  
rem  But the total value of the combined attributes is always unique;
rem  e.g. if a file is marked Archive and Read-only it has a hex value
rem  of 21 hex (i.e. 20 hex + 01 hex) [see Attribute description above]
rem  
rem  
rem  Identifying the File sectors:
rem  
rem  The file is stored in clusters of sectors. If cluster size is
rem  32K, each cluster contains 64 sectors (as sector size is 0.5K).
rem  
rem  The Directory Table contains the location of the first cluster
rem  used by the file. Each sector of a file contains a pointer to
rem  the next sector used by that file, so if the file occupies 
rem  more than 64 sectors the next cluster can be identified.
rem  
rem  That information is also stored in the File Allocation Table
rem  (FAT). If the FAT is undamaged, Norton's DiskEdit can read
rem  from it all the cluster numbers used by a file (see above).
rem  
rem  NB: The 11 character filename is in this format:
rem      - 8 characters, padded with spaces (20h) if not all are
rem        used. If the Long File Name exceeds 8 characters, the
rem        name is truncated to ~1 (or ~2, etc) for the last two.
rem      - 3 character filetype, but NO dot preceeding it.
rem  
rem  NB: A ~1 (or ~2, etc) is also used if the short name contains
rem      whitespace - even if, including the space(s), the short
rem      name does not exceed 8 characters!
rem  
rem  NB: A file will have a Long File Name (LFN) entry if the short
rem      name contains lowercase characters, even if the short name
rem      does *not* exceed 8 characters and contains *no* spaces!
rem  
rem  
rem  Sector Level Access:
rem  
rem  In operating systems which use FAT32, DOS is locked out of
rem  sector-level access to the disk, to prevent it damaging the
rem  LFN entries when performing directory operations. (NB: Use
rem  the DOS internal command UNLOCK to enable read/write access)


rem  INVALID LFN ENTRY
rem  =================
rem  
rem  ScanDisk for Windows, Norton DiskEdit, and Norton Disk Doctor
rem  (if its option to test Date and Time is set), will *wrongly*
rem  report that a disk error exists if a file's Directory Table
rem  entry includes any of the following:
rem  
rem  (a) if the Created or Last Modified date is in the future; or
rem  
rem  (b) if the Last Modified *time* ends in "00" (zero) seconds.
rem  
rem  Actually, there is NO disk error - nor any damage to the file!
rem  And the "error" can be cured by editing the Date or Time stamp
rem  in Windows, using a program such as AttributeMagic v1.0.4:
rem  
rem  - To cure a Future date, change the date to any date BEFORE
rem    the current date
rem  
rem  - To cure a "Last Modified" time which ends in zero seconds,
rem    change the seconds to any OTHER value that's an even number
rem    [Note: ScanDisk's cure is to reduce the value by 2 seconds]
rem  
rem    NB: The "Last Modified" time is stored as a 2-byte value,
rem        which is not enough space to store the actual number
rem        of seconds, so they're stored in 2-second increments.
rem        When that field holds a value of 30, Windows doubles
rem        the value (i.e. to 60), reports "seconds" as 00, and
rem        increases the "minutes" field by 1; but the disk tools
rem        are programmed to reject any value for "seconds" that
rem        exceeds 59, and so report the value of 60 as an error.


rem  LONG FILE NAMES in DOS
rem  ======================
rem  
rem  The following tools utilise Long File Names in DOS -
rem  
rem  1. Odi's LFN tools:
rem  
rem  These include: LDIR.EXE, LCOPY.EXE, LDEL.EXE, LREN.EXE, LMD.EXE
rem  NB: See below ("Recover Individual Files") for syntax and use.
rem  
rem  
rem  2. Henrik Haftmann's DOSLFN.COM:
rem  
rem  This has the advantage of being a driver, which can be loaded at
rem  boot time, that performs ALL functions in LFN format! But it's
rem  complicated to use, compared with the simplicity of Odi's tools.


rem  FILE CLUSTERS
rem  =============
rem  
rem  If a partition's File Allocation Table is damaged, to recover
rem  a file the first thing that must be done is to establish how
rem  many clusters the file occupies.
rem  
rem  To establish the cluster size, run CHKDSK.EXE to display the
rem  partition's "allocation unit size" (i.e. cluster size):
rem  
rem  *** Find the Cluster Size ***
:: CHKDSK C:
:: CHKDSK D:
:: CHKDSK E:
rem  
rem  
rem  SYNTAX -
rem  
rem  chkdsk [drive:][[path]filename] [/F] [/V]
rem  
rem  [drive:][path]  Specifies the drive and directory to check
rem  filename        Specifies the file(s) to check for fragmentation
rem  /F              Fixes errors on the disk
rem  /V              Displays the full path and name of every file on
rem                  the disk
rem  
rem  NB: Do NOT use the /F switch! That switch causes the program to
rem      try to Fix errors, but disk activity will *damage* data and
rem      reduce the changes of recovering the files in the partition!
rem  
rem  Note:
rem  
rem  For the default cluster size (which depends on the size of the
rem  partition), see above. Since a partition does NOT have to use
rem  the default size it is prudent to establish the actual value by
rem  using CHKDSK.EXE (or from byte 14 in the Boot Record: see above).
rem  
rem  
rem  Calculation -
rem  
rem  To calculate how many clusters a file occupies: divide the file size
rem  (in bytes) by the cluster size (in bytes), and round the result up
rem  (to the next whole number).
rem  
rem  NB:  8KB cluster = 1,024 x  8 =  8,192 bytes
rem      16KB cluster = 1,024 x 16 = 16,384 bytes
rem      32KB cluster = 1,024 x 32 = 32,768 bytes
rem  
rem  
rem  File Storage -
rem  
rem  If the file is larger than a single cluster, the Operating System
rem  stores the excess data in the next available cluster; and repeats
rem  this until all the data in the file is stored.
rem  
rem  
rem  Clusters used by a File -
rem  
rem  The Directory Table records the "starting cluster number", i.e. the
rem  address of the first cluster used by the file. Each cluster contains
rem  a pointer to the next cluster in the file (i.e. the cluster number),
rem  or (if it's the last one in the file) an end-of-file marker (FFFF).
rem  
rem  In addition, the File Allocation Table (FAT) contains a record of
rem  all the clusters used by the file. (This is of more practical use
rem  than the Directory Table, because a BACKUP can be made of the FAT!)
rem  
rem  NB: There are therefore TWO ways of identifying the clusters occupied
rem      by a file!
rem  
rem  NB: Programs such as Tiramisu (a.k.a. Easy Recovery), Lost & Found,
rem      and Active Partition Recovery make use of this redundancy.
rem      They scan the disk, sector by sector, to rebuild an undamaged
rem      File Allocation Table in RAM memory.
rem  
rem  
rem  Viewing the FAT -
rem  
rem  Norton's DiskEdit (see below) can display the cluster numbers stored
rem  in the FAT:
rem  
rem   1. To display the Directory Tree, go to: OBJECT - DIRECTORY
rem   2. Select the directory the file is stored in, then click "OK"
rem   3. Go to: VIEW - AS DIRECTORY (or press F4)
rem   4. Move the cursor onto the filename
rem   5. On the LINK menu, select "Cluster chain (FAT)" (or press Ctrl+T)
rem  
rem  NB: Alternatively, display the Root Directory (go to OBJECT - DRIVE)
rem      and select Directory view (go to VIEW - AS DIRECTORY). From that,
rem      double-clicking on the name of a sub-directory will change to
rem      that directory. In this way, navigate to the file in question.
rem  
rem  NB: If the Directory structure is inaccessible (due to a disk crash),
rem      to find the sector containing the directory table use DiskEdit
rem      to search for the first 8 characters of the file's 8.3 filename.
rem      (Note: The Long File Name CANNOT be used, as the characters in it
rem       are NOT stored consecutively on disk, but mixed with other data)
rem  
rem  *** Run Norton DiskEdit 2002: FAT32, HDD exceeding 32GB ***
rem   **       (DISKEDIT.EXE in Norton Utilities 2002)       **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE
:: MOUSE
:: SET PATH=%path%;F:\SAVED\RECOVERY\DISKEDIT\NORTON\2002
:: DISKEDIT
rem  
rem  
rem  The contents of the FAT, as displayed by Norton's DiskEdit, are:
rem  
rem  0 (Zero) : This represents a disk cluster that is not in use.
rem    It may, for example, have been part of an erased file.
rem  
rem    NB: The sector is NOT necessarily empty of data; zero is
rem        merely a marker, indicating the cluster is available
rem        to store new data in. Data in it will be overwritten.
rem  
rem  A decimal number, greater than 1 : This entry represents a
rem    cluster containing data belonging to a file. The number is
rem    the number of the NEXT cluster in the chain for that file.
rem  
rem  EOF ("End Of File") : This entry, too, represents a cluster
rem    containing data belonging to a file. This is the last cluster
rem    in the chain. Part of this cluster will thus be slack space
rem    (i.e. wasted space), possibly containing data from an old file.
rem  
rem  BAD : An unusable cluster. Often only one sector is actually
rem    bad (of the 32 or 64 sectors a cluster usually contains). Even
rem    a bad sector can get fixed; to try reading it, press ALT+L,F.
rem  
rem  Thus a cluster number that is NOT zero contains a file.
rem  
rem  The STATUS line (at the foot of the screen) gives the cluster
rem  number of the cluster the cursor is on. The number HIGHLIGHTED
rem  by the cursor is the number of the *next* cluster in the file!
rem  
rem  
rem  Navigating a File:
rem  
rem  In FAT view, select a cluster (i.e. click on one). If it belongs
rem  to a file (i.e. its value is neither "0" nor "BAD"):-
rem  
rem  - to view the contents of that File, press Ctrl + F (or ALT+L,F)
rem    (or go to: LINK - FILE)
rem  
rem  - to view the Directory entry for that file, press Ctrl + D
rem    (or go to: LINK - DIRECTORY)
rem  
rem  - to view the FAT entries for that file, press Ctrl + T
rem    (or go to: LINK - FAT)
rem  
rem  NB: If an entry goes RED when selected, it belongs to a file.
rem      The on-screen status line will show the file's name.
rem  
rem  Other entries highlighted in RED are other clusters in the *same*
rem  file ("allocation chain") as the selected cluster; but they might
rem  not be the only other clusters for that file.
rem  
rem  NB: To change the format of the display, go to the VIEW menu
rem       - To view sector as Hex, go to: VIEW - HEX
rem       - To view sector as Text, go to: VIEW - TEXT
rem       - To view sector as a Directory, go to: VIEW - DIRECTORY


::  /--------------------------------------------------------------------/  ::


rem                       ----------------------
rem                       SECTION B: DISK REPAIR
rem                       ----------------------


rem                 IDENTIFYING THE PARTITION STRUCTURE
rem                 ===================================


rem  Step 1: Discover the Disk's Geometry -
rem  
rem  Norton's DiskEdit can display the disk's geometry (i.e. the CHS
rem  information for the disk). Start DISKEDIT.EXE then go to:
rem  
::     Tools > Advanced
rem  
rem  *** Run Norton DiskEdit 2002: FAT32, HDD exceeding 32GB ***
rem   **       (DISKEDIT.EXE in Norton Utilities 2002)       **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE
:: MOUSE
:: SET PATH=%path%;F:\SAVED\RECOVERY\DISKEDIT\NORTON\2002
:: DISKEDIT
rem  
rem  Alternatively, the information can be viewed in the BIOS (run
rem  the routine "Auto-Detect Hard Disks"); or read the information
rem  from the label on the disk's casing.
rem  
rem  NB: To enter the BIOS, press the appropriate key (e.g. DEL)
rem      (or, on some systems, F1 or F2) repeatedly at startup.


rem  Step 2: Search for possible Partition Boot Sectors -
rem  
rem  Norton's DiskEdit can help to build up a picture of all possible
rem  boot/partition sectors on the hard disk, and hence of the disk's
rem  structure, by searching for the "55AA" marker (or the signature
rem  "FAT32") (or the signature "MSWIN4.1") present in such sectors.
rem  
rem  NB: To search, display the target HDD as a physical disk; then
rem      go to sector LBA 0; then press CTRL + S simultaneously.
rem  
rem  A partition begins with a Boot Sector, and ends immediately before
rem  another Boot Sector (provided the disk has more than one partition).
rem  Therefore locating all boot sectors on the disk will reveal a lot
rem  about the partition structure.
rem  
rem  NB: The CHS address of the boot sector of a partition is the first
rem      sector of that partition. It is preceeded by 63 hidden sectors,
rem      the first of which contains the Partition Table for that partition.
rem  
rem  The Boot Sector of a partition will normally have the CHS address
rem  xxxx-1-1 (i.e. head 1 sector 1) (except for the 2nd or subsequent
rem  Logical partitions). If the Boot Sector for the Primary DOS or the
rem  1st Logical partition does not have that address, it is NOT genuine!
rem  
rem  It is essential to visually confirm whether a possible boot sector
rem  is actually a boot sector, by using Norton's DiskEdit to view it.
rem  (NB: Compare it against sample MBR sectors in this file - see above)
rem  
rem  The most likely cause of false positives is backups:
rem  
rem  (a) The FAT32 structure includes a backup boot sector in every
rem      partition, so every boot sector on the disk will potentially
rem      show up twice (i.e. if the disk data has not been corrupted).
rem  
rem  (b) Many utilities exist that can save a copy of the MBR or
rem      the Boot Sector of a partition, as a backup file. Being
rem      ordinary files, these can be stored anywhere on the disk.
rem  
rem  Note: The partition Boot Sector contains a text-string identifying
rem        the type of partition (e.g. "FAT16" or "FAT32"). Although it
rem        is not used by the O/S in managing the partition, this is
rem        nonetheless a helpful clue to the structure of the partition.
rem  
rem  Note: The first place to look for a partition Boot Sector is in
rem        sector CHS 0-1-1 (its almost invariable location in FAT32).


rem  Step 3: Search for possible FS Info Sectors -
rem  
rem  Norton's DiskEdit can also search the hard disk for the unique
rem  signatures of an FS Info Sector ("RRaA" and "rrAa").
rem  
rem  The most likely cause of false positives is backups. Many utilities
rem  exist that can save a copy of this sector as a backup; being
rem  ordinary files, these backups can be stored anywhere on the disk.


rem  Step 4: Search for possible FATs -
rem  
rem  Norton's DiskEdit can also search the hard disk for the unique
rem  signature of a File Allocation Table (F8 FF FF 0F) (see above).
rem  
rem  NB: That signature can (in some circumstances) be F8 FF FF 07
rem      (since this is used as a "flag" to record a bad shutdown).
rem  
rem  Svend's FINDPART program can also search the disk for FATs,
rem  with the option FINDPART FINDFAT (see above).
rem  
rem  FATs come in pairs: a mirror copy (FAT2) immediately follows the FAT
rem  (FAT1). The first of the pair will normally begin within 33 sectors
rem  after the start of the partition (i.e. of its boot sector); so the
rem  presence of a FAT within 33 sectors of a boot sector indicates the
rem  boot sector is the genuine article (i.e. the start of a partition).
rem  
rem  The most likely cause of false positives is backups:
rem  
rem  (a) The FAT32 structure includes a backup FAT in every partition,
rem      so every FAT on the disk will potentially show up twice
rem      (i.e. if the disk data has not been corrupted).
rem  
rem  (b) Many utilities exist that can save a copy of the FAT as a backup.
rem      Being ordinary files, these can be stored anywhere on the disk.


rem  Step 5: Rebuild the Partition Table entry -
rem  
rem  To recover a partition, all that is needed is to recreate a correct
rem  pointer in the MBR (at CHS 0-0-1).
rem  
rem  If that pointer points to a partition table, not to a boot sector,
rem  the pointer must be an Extended Partition entry. In any event,
rem  that partition *begins* at the sector which it points to.
rem  
rem  NB: The Primary DOS partition on a FAT32 disk will invariably
rem      begin at CHS 0-1-1 (i.e. LBA sector 63), the 64th sector.
rem  
rem  The last sector at which the partition can *end* is the final
rem  sector of the Extended partition (an address which might be
rem  revealled by one of the other partition table entries in the MBR).
rem  
rem  The VERY last sector at which the partition can *end* is the last
rem  sector of the disk; but it will probably have to end before that,
rem  as partitions MUST end on a Cylinder boundary.
rem  
rem  NB: Calculate the total number of disk sectors, and from that
rem      the CHS address of the final sector of the final Cylinder.
rem      (See "Step 1: Discover the Disk's Geometry", above)
rem  
rem  A FAT32 partition MUST be a multiple of 16,065 sectors, as it
rem  *must* end in the last sector (63) of the last head (254) in a
rem  cylinder; so it MUST end with the CHS address xxxx-254-63.
rem  
rem  NB: This applies ONLY to the Primary DOS and Extended partitions,
rem      not to any Logical partition(s) - although it will apply to
rem      the 1st Logical partition if it's the only Logical partition
rem      and occupies the *entire* Extended partition.
rem  
rem  Another clue is the size of the FAT, since the number of sectors
rem  it occupies ("Big Total Sectors per FAT" in the partition's boot
rem  record) is directly related to the size of the partition (as the
rem  FAT allows 4 bytes per Cluster, and the default Cluster size is
rem  32KB [i.e. 64 sectors] if the partition exceeds 32GB).
rem  
rem  NB: For the default cluster size of smaller partitions, see above.
rem      (The default is the logical starting point, as few users will
rem       be capable of changing it)
rem  
rem  NB: The number of sectors between the first sector of FAT1 and the
rem      first sector of FAT2 discloses the size of FAT1; this can be
rem      established with Norton's DiskEdit, by searching for FATs
rem      (see above) or by viewing the disk sectors.
rem  
rem  The Ending Location for ANY partition exceeding 8GB is meaningless,
rem  since by definition its CHS address MUST be 1023-254-63 (regardless
rem  of the true size of the partition); but the numbers for the entries
rem  "Relative Sectors" and "Number of Sectors" are correct.


rem  OUTLINE OF PARTITION STRUCTURE
rem  ==============================
rem  
rem  No.   Partition    CHS Address    Notes
rem  --    ---------    -----------    -----
rem  1     Primary            0-0-1    Partition Table (MBR)
rem                           0-1-1    Boot Sector (MBR + 1 Head)
rem  
rem  2     1st Logical     xxxx-0-1    Partition Table
rem                        xxxx-1-1    Boot Sector (P.Table + 1 Head)
rem  
rem  3     2nd Logical     xxxx-x-1    Partition Table
rem                        xxxx-x-1    Boot Sector (P.Table + 1 Head)
rem  
rem  4     3rd Logical     xxxx-x-1    Partition Table
rem                        xxxx-x-1    Boot Sector (P.Table + 1 Head)
rem  
rem  NB: The Extended partition is defined in the MBR (CHS 0-0-1) and
rem      comprises all of the Logical partitions.
rem  
rem      The first sector of the Extended partition is the Partition
rem      Table sector of the 1st Logical partition.
rem  
rem      The last sector of the Extended partition is the end sector
rem      of the final Logical partition (unless there is unallocated
rem      space in the Extended partition). [NB: Partitioning utilities
rem      can only leave unallocated space AFTER all Logical partitions]
rem  
rem  NB: Since the Primary partition and the Extended partition MUST end
rem      on a Cylinder boundary, partitions (except Logical partitions)
rem      will *inevitably* begin in the FIRST sector of a Cylinder!
rem      [i.e. The value for HEAD is 0 and the value for SECTOR is 1]
rem  
rem      For backwards compatibility, this is so *even* on a HDD larger
rem      than 8 GB (i.e. one which uses LBA addressing instead of CHS).
rem  
rem      Note: Although the rule applies only to the Primary and Extended
rem      partitions, not to Logical partitions within the Extended partition,
rem      it must inevitably apply to the FIRST Logical partition.
rem  
rem  NB: You normally only need to discover the *starting* Sector
rem      for each partition to have a clear picture of the Disk,
rem      since there is rarely free space between partitions.
rem  
rem  
rem  Size of a Partition:
rem  
rem  A partition is a multiple of 16,065 sectors, inclusive of the Track
rem  containing its Partition Table (if the HDD uses standard geometry,
rem  i.e. 255 Heads per Cylinder, 63 sectors per Head).
rem  
rem  This is because 1 Cylinder = 16,065 sectors (i.e. 255 x 63 = 16,065)
rem  and because a partition is always a whole number of Cylinders.
rem  
rem  NB: This does NOT apply to Logical partitions, only to the
rem      Primary DOS partition and the Extended partition.
rem  
rem  NB: To calculate the value of "Big Total Sectors" in the MBR or EMBR,
rem      subtract 63 (the first 63 sectors containing the Partition Table)
rem      as they are counted under "Hidden Sectors" not "Big Total Sectors".


::  /--------------------------------------------------------------------/  ::


rem                          PARTITION TABLE ERRORS
rem                          ======================


rem  FDISK.EXE
rem  =========
rem  
rem  *** View the Partition information for ALL the Disks ***
:: FDISK /status
rem  
rem  
rem  Warning:
rem  
rem  If partitions are lost or damaged, do NOT enter the FDISK "create
rem  partition" screen. Just entering that screen will write sectors
rem  containing ASCII character 246 (hex F6) to large areas at the
rem  beginning of the free partition space.
rem  
rem  
rem  Warning:
rem  
rem  Do NOT attempt to recover a partition by creating a new one using
rem  standard partitioning tools, such as FDISK. To do so will cause
rem  additional damage, as FAT and other data structures will be created
rem  along with the partition table entries, deleting the previous ones.


rem  SUMMARY OF POSSIBLE ERRORS
rem  ==========================
rem  
rem  The following are possible errors which could occur in a corrupted
rem  Partition Table or EMBR (Extended Master Boot Record) chain:
rem  
rem  - Partition overlaps end of disk (see below)
rem  - Partition does not begin on Cylinder Boundary
rem  - Partition does not end on Cylinder Boundary
rem  - Partition has inconsistent length
rem  - Partition has inconsistent start sector
rem  - Partitions overlap
rem  - Partition has zero length
rem  - EMBR points to sector with no partition table
rem  - EMBR pointing backward
rem  - Circular EMBR chain
rem  - EMBR overlaps
rem  - Extended partition table entries in wrong order
rem  
rem  Notes:
rem  1. Only the Primary DOS and Extended partitions must begin and end
rem     on a cylinder boundary (i.e. must comprise an exact multiple of
rem     16,065 sectors), beginning with CHS 0-0-1.
rem  2. A partition is inconsistent if its LBA values do not match its
rem     CHS values (where both LBA and CHS values are used).
rem  3. If a partition is the wrong size, partitions might overlap,
rem     or one might be of zero length.
rem  4. An EMBR (Extended Master Boot Record) chain might be corrupt.


rem  Partition Overlaps End of Disk
rem  ==============================
rem  
rem  This problem occurs when the ending cylinder value is bigger than
rem  the total number of cylinders on the disk. In some cases, the end
rem  cylinder value can be too large by one or two cylinders.
rem  
rem  You can check the ending cylinder value using BEEBLEBROX.EXE
rem  
rem  For hard disks larger than 8GB the Partition Table stores a maximum
rem  ending cylinder value of 1024, but the disk has more than 1024 cyls.
rem  Use a CHS/LBA Calculator to convert the LBA values ("Start Sector"
rem  and "Number of Sectors") to the true CHS value: if this is greater
rem  than the value reported by Beeblebrox for the disk's Geometry, that
rem  is the problem.
rem  
rem  It may be possible to "truncate" the partition to solve the problem.
rem  To do this, you have to modify the length of the partition.
rem  
rem  NB: Using Partition Magic, start the program with the /IPE option,
rem      then resize the partition. That option causes Partition Magic
rem      to ignore partition table errors. This might cause data loss:
rem      it isn't likely, but back up all important data first.
rem  
rem  
rem  To truncate a partition using Beeblebrox:-
rem  
rem  Firstly, make a backup copy of the Partition Table.
rem  
rem  Secondly, if the new ending cylinder of the partition is greater than
rem  1024, you only have to change the "NumSectors" value. Use a CHS to LBA
rem  Calculator (below) to find the correct NumSector value (the Number of
rem  Sectors in the partition). Type this number in the NumSectors field for
rem  the partition, then save the changes. Verify that the fix was successful.
rem  If not, restore the partition table from the backup file and try to see
rem  what went wrong.
rem  
rem  If the new cylinder value is less than 1024, see whether changing
rem  the translation mode to LBA (in the BIOS) fixes the problem. If the
rem  partition definitely needs to be truncated, the process is the same
rem  as for partitions that cross cylinder 1024 except that you must
rem  also change the ending cylinder, head and sector values (to those
rem  desired). And you still need to figure out what the correct NumSectors
rem  value should be, using a CHS to LBA calculator.


::  /--------------------------------------------------------------------/  ::


rem                         DISK SECTOR EDITORS
rem                         ===================


rem  A Disk Sector Editor allows the user to manually edit the disk,
rem  to correct errors in the data which define the disk's structure.
rem  
rem  It can be used to manually repair a Partition which has been
rem  corrupted by any cause other than physical damage.
rem  
rem  NB: The notes on Disk Structures (above) can assist with this.
rem  
rem  NB: The utilities in "UTILS TO REPAIR DISK STRUCTURES" (below)
rem      automate some parts of the repair process.


rem  INTEL BYTE ORDER
rem  ================
rem  
rem  When editing disk sectors, there is one important convention to
rem  be aware of: Intel Byte order (a.k.a. "little endian").
rem  
rem  When a value exceeds 255 (decimal), more than one byte is needed
rem  to store that value. And these bytes are stored in *reverse* order!
rem  To store a decimal number greater than 255, first convert it to hex,
rem  then write the bytes to the disk in reverse order.
rem  
rem  NB: Windows 98/98SE/ME comes with a Calculator program which can
rem      convert numbers from decimal to hex (and vice versa). Go to
rem      START - RUN and type CALC in the box, then click on "OK".
rem      Then on the Calculator's VIEW menu, select "Scientific".
rem  
rem  Example: The decimal value 41393, which is A1B1 in hex, is written
rem  to disk as B1A1 (so B1A1 is what you'd actually see in a disk editor).


rem  NORTON DISK EDITOR
rem  ==================
rem  
rem  Edit the damaged HDD manually with Norton's DiskEdit
rem  (e.g. to correct a damaged MBR, Partition Table, etc).
rem  
rem  The only version of Norton's DiskEdit which will ALWAYS run in
rem  DOS is version 7.0 (1993). Later versions are too large to run
rem  in Conventional memory ("low DOS" memory) if ANY devices other
rem  than the Mouse are loaded (such as CD-ROM or USB drivers).
rem  
rem  NB: Not even the DOS internal command LOADHIGH can load
rem      later versions of the program under such conditions!
rem      [PTS Disk Editor can run: see "PTS DISK EDITOR" below]
rem  
rem  NB: Being a FAT16 program, none of v7.0's Tools functions are
rem      useable with a FAT32 disk, but the editing function works
rem      (though not for sector addresses beyond the 8GB boundary:
rem      but the MBR, Boot Sector, FAT etc are accessible with it)
rem  
rem  There is notionally 640K of Conventional memory; but it is
rem  partly used by DOS itself and by any device drivers loaded.
rem  
rem  Therefore to run later versions of DiskEdit in DOS, bootup
rem  using a bootable floppy disk that loads NO other devices!
rem  
rem  NB: The program MI.COM (below) displays a map of Conventional
rem      memory, showing the amount of free memory and the drivers
rem      loaded at bootup (together with how much memory each uses).
rem      To increase the amount of free memory, edit AUTOEXEC.BAT
rem      and CONFIG.SYS (on the floppy boot disk) to stop all other
rem      drivers from loading!
rem  
rem  
rem  *** Load a Mouse driver before running Norton's DiskEdit ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE
:: MOUSE
rem  
rem  *** Run Norton DiskEdit v7.0 (1993): FAT16 only, 8GB limit ***
rem   ** This runs under almost ANY conditions (essential tool) **
:: SET PATH=%path%;F:\SAVED\RECOVERY
:: DISKEDIT.EXE
rem  
rem  *** Run Norton DiskEdit 2001: FAT32, HDD exceeding 32GB ***
rem   **       (DISKEDIT.EXE in Norton Utilities 2001)       **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DISKEDIT\NORTON\2001
:: DISKEDIT
rem  
rem  *** Run Norton DiskEdit 2002: FAT32, HDD exceeding 32GB ***
rem   **       (DISKEDIT.EXE in Norton Utilities 2002)       **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DISKEDIT\NORTON\2002
:: DISKEDIT
rem  
rem  
rem  Note:
rem  Alternatively, to run DiskEdit 2001 or 2002, boot to Windows
rem  (using an undamaged bootable HDD as the IDE Primary Master).


rem  Solutions if DiskEdit Crashes -
rem  
rem  Norton's DiskEdit 2001 and 2002 scans the target Partition's
rem  directory structure while loading.
rem  
rem  If that Partition contains a large number of directories
rem  (e.g. if the Partition is larger than about 60GB), DiskEdit
rem  will run out of memory and crash while loading.
rem  
rem  There are two solutions for this fault:
rem  
rem  1. Abort the directory scan, by clicking the mouse, before
rem     DiskEdit has scanned all of the Partition in question.
rem  
rem     NB: The problem with this is that the unscanned part of
rem         the partition will then be *invisible* to DiskEdit.
rem  
rem  2. Use an alternative Disk Sector Editor. For instance, use
rem     the PTS Disk Editor (DE.EXE) as that program does NOT scan
rem     the partition when loading).


rem  Identifying Disk Errors -
rem  
rem  When Norton DiskEdit 2002 first opens a disk in "Logical Disks"
rem  view, it spends 5 minutes scanning that disk. When the scanning
rem  completes, if any disk errors were found it displays the details.
rem  
rem  NB: The errors found can thereafter be viewed at any time. Go to:
rem      INFO - ERROR INFO
rem  
rem  NB: Its use can be confusing, in that if NO errors are found it
rem      does NOT say so, nor does it make any entry under ERROR INFO
rem      that the disk was found to have no errors.


rem  Repairing LFN errors -
rem  
rem  Norton's DiskEdit 2002 can fix the fault, if a Long File Name (LFN)
rem  becomes dis-associated from a file's 11 character short name:
rem  
rem  1. Go to: INFO - ERROR INFO then click on one of the errors found
rem     (which will jump to the disk Cluster containing that error).
rem  2. Select Directory view (press F4 or go to: VIEW - AS DIRECTORY).
rem  3. With the cursor, select the first line of the Long File Name
rem     (LFN); then go to: TOOLS - ATTACH LFN and click "OK".
rem  4. Repeat step 3 for *every* line of the LFN.
rem  
rem  This procedure will re-attach the Long File Name to the file's
rem  short name, thus repairing the error.
rem  
rem  NB: The HDD must *not* be 'Read Only'. Go to: TOOLS - CONFIGURATION
rem      and uncheck "Read Only". (If the disk is "Read Only" the option
rem      ATTACH LFN will be unavailable, i.e. greyed-out).


rem  Copying Sectors -
rem  
rem  Norton's DiskEdit 2002 can copy up to 8 sectors at a time.
rem  
rem  Firstly, mark the section to be copied:
rem  1. Move the cursor to the start of the first sector to copy,
rem     then in the menu go to: EDIT - MARK
rem  2. Move the cursor to the end of the final sector to copy,
rem     then in the menu go to: EDIT - MARK
rem  
rem  NB: The marked section should appear highlighted!
rem  
rem  Secondly, press Ctrl + C to copy the marked section into memory.
rem  The program only allocates 4K of RAM; enough to store 8 sectors.
rem  
rem  NB: An instruction like this means press both the indicated keys
rem      simultaneously. "Ctrl" indicates the Control key (typically
rem      abbreviated to Ctrl on the keyboard).
rem  
rem  Thirdly, move the cursor to the 1st byte of the first sector to be
rem  over-written, then press Ctrl + V to paste the information in memory
rem  to the disk.


rem  File Attributes -
rem  
rem  Norton's DiskEdit 2002 can display the Attributes of a file,
rem  in Directory view (go to VIEW - AS DIRECTORY):
rem  
rem  A (Archive), R (Read Only), S (System), H (Hidden), D (Directory),
rem  and V (Volume Label).
rem  
rem  NB: An LFN entry = RSHV (i.e. a unique combination of attributes)


rem  PTS DISK EDITOR
rem  ===============
rem  
rem  An excellent alternative is PTS Disk Editor, version 1.04
rem  
rem  The program recognises a FAT32 hard disk larger than 32GB,
rem  and is small enough to load into conventional DOS memory
rem  *even* if devices other than the Mouse are loaded.
rem  
rem  NB: No version of Norton's DiskEdit can match this!
rem  
rem  If all that's needed is the ability to edit disk sectors,
rem  the PTS Disk Editor (DE.EXE) will be the best option. The
rem  drawback is that it doesn't have any of the sophisticated
rem  additional functions of Norton's DiskEdit.
rem  
rem  ** Load a Mouse driver before running PTS Disk Editor **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE
:: MOUSE
rem  
rem  *** Run the PTS Disk Editor ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\DISKEDIT\PTS
:: DE


::  /--------------------------------------------------------------------/  ::


rem                    UTILS TO REPAIR DISK STRUCTURES
rem                    ===============================

rem  These utilities can repair a Partition if it has been corrupted
rem  by any cause other than physical disk damage.
rem  
rem  NB: These are alternatives to repairing the damage manually with
rem      a Disk Sector Editor (above), since these utilities automate
rem      some parts of the repair process.


rem  TESTDISK.EXE
rem  ============
rem  
rem  TestDisk v6.10
rem  
rem  The program can recover the Partition, Boot Sector, & FAT
rem  
rem  On a FAT32 hard disk: TestDisk can run under DOS, after booting
rem  from a Win9x boot disk and loading the DPMI program CWSDPMI.EXE
rem  
rem  NB: To run the program in DOS, CWSDPMI.EXE *must* be run first
rem      (but to run it in Windows, CWSDPMI.EXE must *not* be run)
rem  
rem  *** Run TestDisk in DOS ***
:: CWSDPMI
:: TESTDISK
rem  
rem  *** Test Partition Structure of all disks in DOS ***
:: CWSDPMI
:: TESTDISK /LIST
:: TESTDISK /LIST > PRT_LIST.TXT
rem  
rem  
rem  Examples of TestDisk Scan Results -
rem  
rem  Disk 80 - 80 GB / 74 GiB - CHS 9729 255 63, sector size=512
rem  Disk 81 - 80 GB / 74 GiB - CHS 9729 255 63, sector size=512
rem  
rem  NB: Disk 80 = IDE 0 : Drive C (10GB) and Drive E (66GB)
rem      Disk 81 = IDE 1 : Drive D (76GB)
rem  
rem  Disk 80 - 80 GB / 74 GiB - CHS 9729 255 63
rem       Partition            Start        End    Size in sectors
rem   1 * FAT32 LBA          0   1  1  1274 254 63   20482812 [DRIVE C]
rem   2 E extended LBA    1275   0  1  9728 254 63  135813510
rem   5 L FAT32           1275   1  1  9728 254 63  135813447 [DRIVE E]
rem  
rem  Disk 81 - 80 GB / 74 GiB - CHS 9729 255 63
rem       Partition            Start        End    Size in sectors
rem   1 P FAT32 LBA          0   1  1  9728 254 63  156296322 [DRIVE D]
rem  No partition is bootable
rem  
rem  NB: * = Asterix indicates the active (bootable) partition
rem      P = Primary DOS partition
rem      E = Extended partition
rem      L = Logical partition
rem  
rem  
rem  Notes -
rem  
rem  If one of the disk's Partitions is accidentally deleted, e.g. by
rem  faulty software (or any cause *other* than physical disk damage),
rem  you can get it back using TESTDISK.
rem  
rem  TestDisk can also COPY any file (or entire subdirectories) from a
rem  lost partition WITHOUT having to first restore the partition or
rem  reboot. Ideal if you can't access the partition any other way!
rem  
rem  
rem  Display the Geometry (Cylinders, Heads, Sectors) -
rem  
rem  Under DOS, TestDisk gets the disk size using an extended BIOS
rem  function (ah=0x48, int 0x13), and the geometry (number of heads
rem  and sectors) using a standard BIOS function (ah=0x08, int 0x13).
rem  TestDisk uses the default sector size of 512 bytes.
rem  
rem  NB: Partitioning programs (such as FDISK.EXE) make the Primary
rem      DOS Partition and the Extended Partition end on a cylinder
rem      boundary. This is a MANDATORY requirement!
rem  
rem  
rem  Recover the Boot Sector -
rem  
rem  TestDisk can fix a corrupted FAT32 Boot Sector, using the *backup*
rem  Boot Sector. The Boot Sector is the first sector of the Partition,
rem  and a backup copy of the Boot Sector is located at the 6th sector
rem  of the Partition.
rem  
rem  TestDisk checks the Boot Sector and the backup Boot Sector:
rem  if the Boot Sector and backup Boot Sector mismatch, you can
rem  overwrite the Boot Sector (Org BS) [Original BootSector] with
rem  the backup Boot Sector (Backup BS), or vice versa.
rem  
rem  The option "Dump" can used to display the sector content in both
rem  hexadecimal (hex) and ascii (plain text).
rem  
rem  
rem  Rebuild a valid Boot Sector -
rem  
rem  If a FAT32 boot sector is corrupted, TestDisk can rebuild that
rem  boot sector: choose the option "RebuildBS" in the menu.
rem  
rem  To rebuild a FAT boot sector, TestDisk requires that:
rem   (1) filesystem size is equal to partition size, and
rem   (2) fragmentation is low.
rem   [NB: The second condition is *highly* unlikely in reality!]
rem  
rem  
rem  Recover the Partition -
rem  
rem  This option can find lost FAT32 partitions and restore them. It
rem  finds deleted partitions, then allows you to write the necessary
rem  data into the Partition Table.
rem  
rem  NB: It can COPY any file (or recurse through whole subdirectories)
rem      from within a lost partition *without* having to first restore
rem      that partition.
rem  
rem  
rem  Repair the FAT -
rem  
rem  File Allocation Tables are maps of the data region, indicating
rem  which clusters are used by files and directories. To repair FAT,
rem  (menu: "Repair FAT") TestDisk compares the two FAT copies. If FAT
rem  mismatches (sector by sector check) or contains errors, TestDisk
rem  uses the FAT copy with less errors and removes the obvious errors.
rem  
rem  This function must ONLY be used on a filesystem with *correct*
rem  values in the boot sector! It has been used with success when
rem  SCANDISK or CHKDSK refused to repair the filesystem or crashed.
rem  
rem  
rem  Make Backups of Essential Sectors -
rem  
rem  The "Dump" option can be used to dump a backup copy of essential
rem  sectors to disk (i.e. save them to another disk).
rem  
rem  
rem  Undelete FILES -
rem  
rem  1. Select "Advanced".
rem  2. Select the partition containing the lost files and choose "Undelete".
rem  3. To undelete a file, select the file to recover and press "c" to copy
rem     the file to another disk. To recover a deleted directory, select the
rem     directory and press "c" to undelete the directory *and* its contents.
rem  4. Select the destination disk.
rem  5. When you have recovered all the lost files, press "Q" to Quit.
rem  
rem  
rem  Undelete PARTITION -
rem  
rem  Step 1: Disk selection
rem  
rem  Run TestDisk. All hard drives should automatically be detected,
rem  and listed with the correct size.
rem  
rem  1. Use the up/down arrow keys to select the hard drive with the lost
rem     partition(s).
rem  2. Press "Enter" to proceed.
rem  
rem  
rem  Step 2: Partition table selection
rem  
rem  TestDisk displays the partition types.
rem  
rem  1. Select the partition type. Usually the default value will be the
rem     correct one, because TestDisk auto-detects the partition type.
rem  2. Press "Enter" to proceed.
rem  
rem  
rem  Step 3: Current partition table status
rem  
rem  1. Select "Analyse" to check the current partition structure
rem     (i.e. a sanity check: see below) & search for lost partitions.
rem  2. Press "Enter" to proceed.
rem  
rem  The current partition structure is displayed. Examine it for missing
rem  partitions and errors:
rem  - e.g. The first partition is listed twice: this indicates a
rem         corrupted partition or an invalid partition table entry.
rem  - e.g. "Invalid boot": this indicates a faulty boot sector.
rem  - e.g. Only one logical partition (labelled "Partition 2") is shown
rem         in the Extended partition, so one logical partition is missing.
rem  
rem  
rem  Step 4: Quick Search for partitions
rem  
rem  1. If there are missing partitions or errors, select the O/S
rem     (Operating System) and partitions to proceed.
rem  
rem     e.g. TestDisk finds two partitions, including a missing
rem          logical partition labelled "Partition 3".
rem  
rem  2. Highlight the partition found, then press "P" to list its files.
rem  3. If all directories and data are correctly shown, press "Enter"
rem     to proceed. To go back to the previous display, press "Q" to Quit.
rem  
rem  
rem  Step 5: Save the partition table, or search for more partitions
rem  
rem  1. If all partitions are shown and all files correctly listed:
rem     Select "Write" to save the partition structure.
rem  
rem     NB: The option "Extd Part" gives you the choice whether the
rem         Extended partition will use ALL the available disk space
rem         or only the MINIMUM required space.
rem  
rem  2. If a partition is still missing, go to Step 6:
rem     Select "Deeper Search", then press "Enter" to proceed.
rem  
rem  
rem  Step 6: If a partition is still missing, do a Deeper Search
rem  
rem  A Deeper Search will search for FAT32 backup boot sectors; and to detect
rem  more partitions it will scan each cylinder (click on the thumbnail).
rem  
rem  The results are displayed as follows -
rem  
rem  If a partition is found by its backup boot sector, on the last line
rem  of the display you'll see the message "found using backup sector!"
rem  and the size of the partition.
rem  
rem  NB: You might get a false result, if there were backup copies stored
rem      on the damaged disk of the Boot Sector for this or any other disk
rem      (i.e. backups made by a data backup or data rescue program).
rem  
rem  If a partition is displayed twice, with different sizes, both will be
rem  listed with status D (i.e. deleted) because they overlap each other:
rem  
rem  1. Highlight the first, then press "P" to list its files. If the
rem     file system of this partition is damaged (click on thumbnail
rem     to check), press "Q" for Quit to go back to the previous display.
rem  2. Highlight the second, then press "P" to list its files. If it works,
rem     you've found the correct partition! Use the left/right arrows to
rem     navigate into the directories: examine the files in them for more
rem     verification. Press "Q" (Quit) to go back to the previous display.
rem     NB: The FAT directory listing is limited to 10 clusters, so some
rem         files may not appear; but this doesn't affect recovery.
rem  3. The status options are: Primary, *bootable, Logical, and Deleted.
rem     Using the left/right arrow keys, change the status of the selected
rem     partition to L (Logical).
rem     Note: The primary partition starts at cylinder 0, head 1, sector 1;
rem           additional partitions usually start at head 0 sector 1,
rem           (e.g. C-H-S 2231-0-1).
rem     Note: If a partition is listed as * (bootable), but you don't
rem           boot from that partition, you can change it to Primary.
rem  4. Press "Enter" to proceed.
rem  
rem  
rem  Step 7: Partition table recovery
rem  
rem  Write the new partition structure to disk.
rem  
rem  1. At "Write" select 'Enter', 'y' or 'Ok', to save all partitions
rem     to the partition table.
rem  2. TestDisk displays the message "You have to restart your Computer
rem     to access your data"; so press 'Enter', then reboot the computer.


rem  *** Test the Partition Structure ***
rem  
rem  ** Display the result on screen **
:: CWSDPMI
:: TESTDISK /list
rem  
rem  ** Alternatively, save result to a file ***
:: CWSDPMI
:: TESTDISK /list > testdisk.txt
rem  
rem  ** Alternatively, save result to a file ***
:: CWSDPMI
:: TESTDISK /list /log


rem  Sanity Checks -
rem  
rem  TestDisk's analysis includes a "sanity" check of the partition
rem  structures (in the partition tables: the MBR and Extended MBR):-
rem  
rem  The MBR partition table is limited to 4 entries (one of which can
rem  be an Extended partition containing several logical partitions).
rem  
rem  Every partition table (in the MBR and in each Logical partition)
rem  must end with the two bytes 55 AA (hex).
rem  
rem  A partition entry must contain the following fields:
rem  - beginning of partition (C-H-S)
rem  - end of partition (C-H-S)
rem  - partition type
rem  - beginning of partition (LBA)
rem  - size in sectors
rem  - boot flag
rem  
rem  Only the Primary partition can have the bootable flag set.
rem  
rem  NB: This might not be so if the Primary partition is a
rem      hidden partition (i.e. if the partition type is 1C).
rem  
rem  CHS data storeage is limited to a maximum of 1,024 cylinders:
rem  0 to 1023 (the 8GB limit, 1024 x 255 x 63 = 16,450,560 sectors).
rem  A modern BIOS uses LBA mode to address disk data, not CHS; but
rem  FAT32 boot sectors still include the CHS geometry.
rem  
rem  Each CHS value must be within the valid range, so Testdisk checks
rem  that CHS sector 0 is not used (the first valid CHS sector is 1),
rem  and checks the CHS sector number is less than the number of sectors
rem  per head. It also checks: whether the LBA address values match the
rem  CHS address values; whether the partition ends after the end of the
rem  disk; and whether any partitions are overlapping each other.


rem  Further Information -
rem  
rem  See also: http://en.wikipedia.org/wiki/TestDisk


rem  SCANDISK.EXE
rem  ============
rem  
rem  It's safe to run Microsoft SCANDISK to check a hard disk for errors,
rem  but do NOT allow it to make any changes to the disk!
rem  
rem  It gives priority to file system integrity, *discarding* user data
rem  to do so, thus it CANNOT be trusted in a data recovery situation.


rem  UNFORMAT.EXE
rem  ============
rem  
rem  Norton's UNFORMAT for DOS -
rem  
rem  Recovers files and directories after an accidental format,
rem  and can rebuild disks corrupted by a virus or power failure.
rem  
rem  The program can recover all the files on a partition which has
rem  been accidentally formatted by the DOS program FORMAT.COM (if
rem  no new files have been written to the disk afterward).
rem  
rem  NB: Where files have been written to the disk after it was
rem      formatted, the program might still recover some files; but
rem      this will depend on how much data has been over-written.
rem  
rem  Norton's UNFORMAT for DOS (UNFORMAT.EXE) is one of the rescue
rem  tools included in -
rem  (a) Norton Utilities 2001
rem  (b) Norton Utilities 2002
rem  (c) Disk 1 of the Norton Emergency Disks (a set of 4 floppy disks)
rem  
rem  
rem  Syntax:
rem  
rem  UNFORMAT [drive:] [/IMAGE|/MIRROR] [/G0] [/BW|/LCD]
rem  
rem  drive       Drive letter of disk to unformat.
rem  /IMAGE      Uses Image recovery info (excludes Mirror info).
rem  /MIRROR     Uses Mirror recovery info (excludes Image info).
rem  /G0         Disable graphical mouse and all graphical characters.
rem  /BW, /LCD   Improve display on monochrome or LCD monitors.


rem  PARTITION LOGIC
rem  ===============
rem  
rem  Partition Logic is a hard disk partitioning tool.
rem  
rem  It can create, delete, format, defragment, resize and move partitions
rem  and modify their attributes. It can copy entire hard disks.
rem  
rem  Partition Logic is based on the Visopsys operating system. It boots
rem  from a CD or floppy disk, and runs as a standalone system independent
rem  of your regular operating system. It is a free alternative to such
rem  commercial programs as Partition Magic, Drive Image, and Norton.
rem  
rem  The bootable floppy disk IMG file includes a minimal distribution. It
rem  must be written to a 1.44MB floppy disk. Windows users will need a
rem  program such as RawWrite (RAWWRITEWIN.EXE) to create the disk.
rem  
rem  Under Windows 95, 98 and ME the file DISKIO.DLL (included with RawWrite)
rem  must be present in the same directory as RAWWRITEWIN.EXE.
rem  
rem  
rem  Installation note:
rem  
rem  Partition Logic is a self-contained disk image with its own operating
rem  system (Visopsys) included on the disc. It is not installed as a Windows
rem  program as such. Instead it is written to a blank floppy disk from which
rem  the computer can be booted to perform the desired partitioning, resizing,
rem  etc.
rem  
rem  
rem  Help Commands:
rem  
rem  HELP              Show summary of help entries
rem                    NB: Type 'help <command>' for specific help
rem  
rem  
rem  Data Recovery commands:
rem  
rem  BOOTMENU          Edit the boot loader menu
rem  CHKDISK           Check a filesystem for errors
rem  DISKS             Show the disk volumes in the system
rem  FDISK             Manage (i.e. partition) hard disks
rem  FORMAT            Create a new (empty) filesystem
rem  LSDEV             Display devices
rem  MEM               Show system memory usage
rem  MOUNT             Mount a filesystem
rem  SYNC              Synchronize all filesystems on disk
rem  UMOUNT            Unmount a filesystem
rem  UNAME             Print system information
rem  
rem  
rem  File Commands:
rem  
rem  CAT (or TYPE)     Print a file's contents on the screen
rem  CP (or COPY)      Copy a file
rem  FILE              Show the type of a file
rem  MORE              Display file's contents, one screenful at a time
rem  MV (or MOVE)      Move a file (ren or rename have the same effect)
rem  RM (or DEL)       Delete a file
rem  TOUCH             Update a file or create a new (empty) file
rem  
rem  
rem  Directory Commands:
rem  
rem  CD                Change the current directory
rem  FIND              Traverse directory hierarchies
rem  LS (or DIR)       Show the files in a directory
rem  MKDIR             Create one or more new directories
rem  PWD               Show the current directory
rem  RMDIR             Remove a directory
rem  
rem  
rem  Manage Processes:
rem  
rem  KILL              Kill a running process
rem  PS                Show list of current processes
rem  NM                Show symbol information for a dynamic program or library
rem  RENICE            Change the priority of a running process
rem  
rem  
rem  Miscellaneous Commands:
rem  
rem  DEFRAG            Defragment a filesystem
rem  IMGBOOT           The program launched at first system boot
rem  KEYMAP            View or change the current keyboard mapping
rem  LOGOUT (or EXIT)  End the current session
rem  REBOOT            Exit to real mode and reboot the computer
rem  SHUTDOWN          Turn off the computer
rem  VSH               Start a new command shell
rem  
rem  
rem  Commands for Graphic Mode only:
rem  
rem  COMPUTER          Navigate the resources of the computer
rem  CONFEDIT          Edit Visopsys configuration files
rem  CONSOLE           Show the console window
rem  DISPROPS          View or change the display settings
rem  FILEBROWSE        Navigate the file system
rem  PROGMAN           View and manage programs and processes
rem  SCREENSHOT        Take a screenshot
rem  VIEW              Display a file in a new window
rem  WINDOW            Open a new command window


::  /--------------------------------------------------------------------/  ::


rem                       RECOVER INDIVIDUAL FILES
rem                       ========================


rem  This procedure is for situations where the disk cannot be repaired,
rem  e.g. due to a hardware fault, and the best that can be achieved is
rem  to copy the files to an undamaged disk.
rem  
rem  This is for cases where cloning the disk will not solve the problem,
rem  because the actual structure of the file system itself is damaged.
rem  
rem  This class of utilities typically work by re-building a facsimilie,
rem  in RAM memory, of the hard disk's file structures (e.g. its File
rem  Allocation Table and Directory Tree), after scanning the disk. It
rem  can be an effective solution; but a full scan is a long process.
rem  
rem  NB: Some of the utilities included can recover files deleted from
rem      an undamaged disk (e.g. deleted by a virus, by a software bug,
rem      or by accident).


rem  TIRAMISU EASY RECOVERY
rem  ======================
rem  
rem  Easy Recovery v6.10 -
rem  
rem  This program works with ANY size of FAT32 hard disk up to 137GB
rem  (the largest hard disk possible with 28-bit BIOS).
rem  
rem  NB: Easy Recovery was known as Tiramisu in versions 1 to 5.
rem  
rem  NB: Tiramisu version 3 (a.k.a. "Tiramisu for 32-bit FAT v3")
rem      does not work on a hard disk larger than 8GB.
rem  
rem  NB: Tiramisu version 5 does not work on a hard disk larger than
rem      32GB, because it can NOT recognise a cluster size of 32k
rem      (i.e. the maximum cluster size it can recognise is 16k).
rem  
rem  Easy Recovery uses information held in the BIOS to identify the
rem  file system. If that information is faulty, or not available, it
rem  reports the File System Type as "Unknown": in that case, before
rem  the program can analyze the partition for recoverable data, the
rem  user must manually select the correct file system (i.e. FAT32).
rem  
rem  Once the file system has been correctly identified, the program
rem  is ready to begin the scan (at the 'Recovery Scan' screen).
rem  
rem  On a FAT32 disk, data is stored in clusters. The Operating System
rem  creates a table (the File Allocation Table, or FAT) to keep track
rem  of the cluster(s) in which each file is stored. It also makes a
rem  backup copy of the FAT, in case the original is damaged.
rem  
rem  By default, Easy Recovery compares the two copies of the FAT
rem  and uses the best information from each. If that default action
rem  fails to locate all the files, there is an option to select one
rem  FAT only instead (either FAT1 or FAT2).
rem  
rem  If BOTH copies of the FAT are damaged, the option "Ignore FAT"
rem  forces the program to rely solely on information in the files,
rem  without refering to either copy of the FAT.
rem  
rem  If none of the above actions recovers all the files, the option
rem  "RAW" causes all the sectors on the disk to be read sequentially,
rem  i.e. sector by sector. This will ONLY recover files which are
rem  stored contiguously on the disk, or which occupy only one sector.
rem  
rem  NB: A better option in this last event might be to try restoring a
rem      backup copy of FAT1 or FAT2 (ideally on a *clone* of the disk).


rem  LOST AND FOUND
rem  ==============
rem  
rem  Lost and Found, v1.31
rem  
rem  Lost & Found lets you recover and restore data after accidental
rem  data loss, or from corrupted media caused by a disk crash or a
rem  logical system failure. It will even recover data if the partition
rem  has been reformatted or if the FAT tables have been destroyed!
rem  
rem  As long as the disk is still spinning, Lost & Found can locate and
rem  recover almost any file, anywhere on the disk.
rem  
rem  NB: Other users have reported exceptional results! The program
rem      recovered data in situations where Norton Disk Doctor and
rem      ScanDisk.exe refused even to run.
rem  
rem  *** Run Lost and Found ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\SAVEFILE\LOSTFND
:: LF
:: LOADER LF


rem  ACTIVE PARTITION RECOVERY
rem  =========================
rem  
rem  Active Partition Recovery, v3.0
rem  
rem  
rem  SYNTAX -
rem  
rem  -lba          : Force LBA mode for access to all detected HDDs
rem  
rem  -lba=N        : Force LBA mode for access to particular HDD,
rem                  where N=[80h,81h,82h,83h]
rem  
rem  -restoreMBR=N : Restore MBR sector from a backup file,
rem                  where N=[80h,81h,82h,83h]
rem  
rem  -ignoreMBR=N  : Do not load MBR information for this drive,
rem                  where N=[80h,81h,82h,83h]
rem                  NB: Allows you to scan a damaged partition
rem  
rem  -imageN=PATH  : Create an image of the physical drive,
rem                  where N=[80h,81h,82h,83h]
rem                  and PATH={drive}:\\{PATH}\\ (i.e. destination)
rem  
rem  
rem  The IDE cables will accept up to four hard disks, two on each
rem  cable: named Primary Master, Primary Slave, Secondary Master
rem  and Secondary Slave; numbered respectively 80, 81, 82 & 83.
rem  
rem  The program cannot handle a damaged partition of type "Unknown".
rem  In that situation, start the program with the parameter
rem  "-ignoreMBR", to force program to ignore the default partitions.
rem  
rem  
rem  *** Set the PATH ***
:: SET PATH=%path%;A:\;F:\SAVED\RECOVERY\ACTPARTR
rem  
rem  *** Read the Help file ***
:: EDIT APR.TXT
rem  
rem  *** Run the Program ***
:: APR
rem  
rem  *** Run the Program: Force LBA mode ***
:: APR -lba=80
:: APR -lba=81
:: APR -lba=82
:: APR -lba=83
rem  
rem  *** Scan Disk #1 (Drive C:) ignoring its MBR ***
:: APR.EXE -ignoreMBR=80
rem  
rem  *** Scan Disk #2 (Drive D:) ignoring its MBR ***
:: APR.EXE -ignoreMBR=81
rem   
rem  
rem  NB: Press [TAB] key to switch to Long File Name view


rem  MEDIA TOOLS
rem  ===========
rem  
rem  Media Tools Professional, v5.0
rem  
rem  In access mode "IDE DRIVE" the program has direct access to any IDE
rem  drive on the system, and does not rely on the system BIOS. This
rem  means you can see the entire capacity of any IDE drive, regardless
rem  of whether the system BIOS has the ability to see the entire drive.
rem  
rem  File Recovery Tree - Rebuilds FAT32 file system automatically
rem  for hard drives and removable media. Recovers from accidental
rem  format or deletion, corrupt or missing file system, virus or worm,
rem  or files located in slack space from previous formats. Allows you
rem  to recover data to another drive.
rem  
rem  Boot Partition Repair - Rebuilds FAT boot sector and partition table
rem  automatically from an IDE or SCSI hard drive and removable media,
rem  giving you access to all files and directories.
rem  
rem  Media Editor - Mounts DOS and Windows file systems (easy step-by-step
rem  screenshots and directions). Then, once the file system is mounted,
rem  the file system can be rebuilt automatically. (Note: Use this option
rem  if "File Recovery Tree" does not produce the results you expect).
rem  
rem  NB: Media Editor also lets you view, search for, and edit anything
rem      within the file system on any media or operating system, without
rem      any knowledge of Hex, through custom designed editing templates.
rem  
rem  *** Run Media Tools ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\M_TOOLS
:: MTL


rem  GET DATA BACK FOR FAT
rem  =====================
rem  
rem  The program "GetDataBack for FAT" can succeed in recovering data
rem  where other attempts fail.
rem  
rem  GetDataBack includes a drive-imaging tool, which makes a replica
rem  of the drive on a second hard disk. The recovery portion of the
rem  program scans the image far more quickly than it could possibly
rem  work through damaged sectors on a disk, resulting in a solid
rem  solution for getting back all the missing data.


rem  SVEND'S UTILITIES: FP.SYS
rem  =========================
rem  
rem  FP.SYS (Find Partition), v1.5
rem  Copyright Svend Olaf Mikkelsen, 2001
rem  
rem  A device driver for DOS or Windows (Win95/98/ME) that adds
rem  read-only drive letters for lost partitions.
rem  
rem  
rem  SYNTAX -
rem  
rem  Put this line in config.sys:
rem   device=fp.sys [disk number]
rem  
rem  Disks are numbered from 1. Default is disk 1.
rem  
rem  If FP.SYS is not in the root of the boot drive, you must
rem  add the full path to FP.SYS.
rem  
rem  To abort loading, press ESC.
rem  
rem  If a FAT32 partition is lost, you MUST boot with a DOS version
rem  that recognises FAT32 (e.g. MS-DOS v8.0 [the WinME version]).
rem  
rem  
rem  Notes:
rem  
rem  1. To speed up disk access in pure DOS, Smartdrive (SMARTDRV.exe)
rem     can be used. However, Smartdrive does not like it if write
rem     attempts are made to read-only partitions.
rem  
rem  2. If you use FP.SYS with Windows 95/98/ME, add the following
rem     entry in the C:\WINDOWS\IOS.ini file:
rem  
rem     [SafeList]
rem     fp.sys
rem  
rem     NB: If this is not done, all partitions will be in MS-DOS
rem         compatibility mode. In some cases where a disk is not
rem         read correctly in DOS or Windows, Windows will see the
rem         disk differently in compatibility mode.
rem  
rem  
rem  RECOMMENDATIONS -
rem  
rem  Backup important data that you currently can access, to an
rem  external disk, before recovery attempts are made.
rem  
rem  Use FP.SYS when booting from floppy disk.
rem  
rem  
rem  WARNINGS -
rem  
rem  1. If partitions are overlapping, file copying can damage data.
rem     If you are in doubt, only copy to an undamaged disk.
rem  
rem  2. The target partition must NOT contain old deleted copies of
rem     the lost files.
rem  
rem  3. If you do not know the nature of the problem, do *not* write
rem     to the damaged disk at all; and do not use FDISK on it!

rem  *** Run DIR command after loading fp.sys ***
rem   ** (FP.SYS must be loaded in CONFIG.SYS) **
:: C:
:: DIR /W
rem  
:: D:
:: DIR /W


rem  SVEND'S UTILITIES: FINDDIR
rem  ==========================
rem  
rem  FINDPART for DOS, v4.72 (FINDPART FINDDIR)
rem  
rem  Searches for sub-directories; and calculates the estimated
rem  location of cluster number two, and cluster size.
rem  
rem  NB: In this version of Svend's Utilities the FINDDIR function is
rem      a switch (i.e. an option) in FINDPART, not a seperate program
rem  
rem  
rem  SYNTAX -
rem  
rem  Disks are numbered from 1.
rem  
rem  The report can be written to a file. File extension must be .txt
rem  
rem  Note: This program is *NOT* the best means of recovering files. It
rem        FAILS if the file to be copied is not contiguous on the disk!
rem        There are much BETTER recovery tools available (see above).
rem  
rem  
rem  ** Display the Help screen **
:: FINDPART FINDDIR
rem  
rem  ** Save the Help screen to a file **
:: FINDPART FINDDIR > F:\FINDDIR.TXT
rem  
rem  
rem  ** Search Disk 1 for Subdirectories **
rem  **      Saves report to a file      **
:: FINDPART FINDDIR 1 F:\FINDDIR1.txt
rem  
rem  ** Search Disk 2 for Subdirectories **
rem  **      Saves report to a file      **
:: FINDPART FINDDIR 2 F:\FINDDIR2.txt


rem  SVEND'S UTILITIES: CYLDIR
rem  =========================
rem  
rem  CYLDIR, v5.5 (CYLDIR.EXE)
rem  
rem  Lists lost directories in a FAT32 partition, and displays the
rem  file names.
rem  
rem  The correct DOS codepage must be loaded, before searching for
rem  or copying files. [NB: DOS codepage for UK (country 044) is 850]
:: SET CODEPAGE=850
rem  
rem  Copying speed is enhanced if himem.sys or smartdrv.exe are loaded
rem  (in CONFIG.SYS and AUTOEXEC.BAT respectively).
rem  
rem  Note: This program is *NOT* the best means of recovering files. It
rem        FAILS if the file to be copied is not contiguous on the disk!
rem        There are much BETTER recovery tools available (see above).
rem  
rem  
rem  SYNTAX -
rem  
rem  Cyldir {disk number} {cylinder} {head} {sector} {FAT size}
rem  {cluster size} {root} [copyfiles {Directory cluster}] [{logfile}]
rem  
rem  - FAT size in sectors (from Ranish Partition Manager: PART.exe)
rem  - Cluster size in KB  (NB: If disk exceeds 32GB, must be 32KB)
rem  - Root = Root cluster number (NB: Usually cluster 2)
rem  - Logfile's extension must be .TXT
rem  
rem  
rem  (a) LIST THE LOST FILES:
rem  
rem  ** Find the size of the FAT with FINDPART **
:: FINDPART FINDFAT ALL comprehensive F:\FAT_ALL.TXT
rem  
rem  ** Find the size of the FAT with Ranish Partition Manager **
:: SET PATH=%path%;F:\SAVED\RECOVER\P-TABLE\RANISH\16BIT-~1
:: PART.exe
rem  
rem  To list lost (or deleted) files in Partition 1 on Disk 1
rem  where the Partition uses 32K clusters (i.e. exceeds 32GB):
:: CYLDIR 1 0 1 1 ____ 32 2 F:\CDIR.TXT
rem  
rem  
rem  Example -
rem  
rem  From FINDPART FINDFAT you have this result for Disk 1:
rem  -----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
rem    260   0 33  1204  4      2  1204     0     0     0 981124    516
rem  
rem  The CYLDIR command line is the disk number, followed by the first
rem  6 numbers in the above line, followed by the file name CDIR.TXT:
rem  CYLDIR 1 260 0 33 1204 4 2 F:\CDIR.TXT
rem  
rem  
rem  (b) COPY THE LOST FILES:
rem  
rem  Run CYLDIR.EXE from a floppy disk or an undamaged partition.
rem  
rem  If the option COPYFILES is used, it copies files from a lost
rem  directory. The cluster numbers are saved in the log file.
rem  The current directory must be empty, unless it's the Root
rem  directory. NB: Copied files *cannot* be expected to be okay!
rem  
rem  To speed up file copying, load HIMEM.SYS and SMARTDRV.EXE:
rem  1: Load HIMEM.SYS in CONFIG.SYS
rem     Syntax: device=himem.sys
rem  2: Load SMARTDRV.EXE before running CYLDIR -
:: SMARTDRV.EXE 4096 16>nul
:: CYLDIR 1 0 1 1 ____ 32 2 COPYFILES ____ F:\CDIR.TXT
rem  
rem  Note: Files are copied using their SHORT file names. A file,
rem        LONGNAME.BAT, for renaming them to their Long File Names,
rem        will automatically be created. A file named CYLDIR.LOG
rem        records the names of files that are not readable or are
rem        FDISK damaged. Files bigger than 2 GB cannot be copied.
rem  
rem  
rem  Alternate usage: Cyldir {directory cluster} dir  [{copy logfile}]
rem                   Cyldir {directory cluster} tree [{copy logfile}]
rem  
rem  This is two additional ways to copy files from a lost partition.
rem  
rem  Directories are relative to the current directory.
rem  If 'tree' is specified, files in any subdirectories are copied.
rem  If the target subdirectories already exist, they must be empty.
rem  
rem  The main thing is to be certain that no copy of the lost files
rem  is on the target partition. This could occur if partitions
rem  overlap, or if old deleted copies of the lost files exist.
rem  
rem  The logfile CDIR.TXT must exist in the current directory, or
rem  in the Root of current partition. (Suggestion: Put CDIR.TXT
rem  and CYLDIR.EXE in an empty directory and work from there.)
rem  
rem  Up to ten {directory cluster}'s can be entered. If the Root
rem  directory cluster number is entered with the 'tree' option, you
rem  can add '+lost' to the command line to include lost directories,
rem  i.e. those beginning with ? in CDIR.TXT
:: CYLDIR ____ tree +lost F:\COPYLOG.TXT
rem  
rem  To stop the copy after the current directory, press ESC.
rem  
rem  If run in pure DOS, a file LONGNAME.BAT for recreating long file
rem  names is created in each directory, if there is enough free space.
rem  
rem  To write a directory listing to CDIR.LST, use:
:: CYLDIR LIST
rem  
rem  Choose directory cluster numbers in CDIR.TXT; or execute the
rem  command 'cyldir list' and find the numbers in CDIR.LST.
rem  
rem  *** Copy a single directory ***
rem  (e.g. If the cluster number is 117: cyldir 117 dir)
:: CYLDIR ___ DIR
rem  
rem  *** Copy an entire directory tree ***
rem  (e.g. If the cluster number is 117: cyldir 117 tree)
:: CYLDIR ___ TREE
rem  
rem  
rem  Example -
rem  
rem  Disk: 1   Cylinders: 9729   Heads: 255   Sectors: 63   MB: 76317
rem  
rem  -PCyl N ID -----Rel -----Num ---MB -Start CHS- --End CHS-- BS  CHS
rem      0 - 0C       63 42973812 20983    0   1  1 2674 254 63 B    OK
rem   2675 1 0B       63113322447 55333 2675   1  1 9728 254 63 R0   OK
rem      0 - 0B 42973938113322447 55333 2675   1  1 9728 254 63 B    OK
rem   6200 1 0B       63 56661192 27666 6200   1  1 9726 254 63 R0   OK
rem      0 - 0B 99603063 56661192 27666 6200   1  1 9726 254 63 B    OK
rem  
rem  -----FAT CHS -Size Cl --Root -Good -Rep. Maybe --Bad YYMMDD DataMB
rem   2675   1 33 13832 32      2 13832     0     0     0 080206  11160
rem   6200   1 33 13830 16*     2*13830     0     0     0             2
rem  
rem  Syntax:
rem  CYLDIR + Disk number + first 6 numbers from lower table + F:\CDIR.txt
rem  
rem  ** Disk 1, Partition 2 **
rem  cyldir 1 2675 1 33 13832 32 2 F:\cdir.txt
rem  
rem  ** Disk 1, Partition 4 **
rem  cyldir 1 6200 1 33 13830 16 2 F:\cdir.txt

rem  Note:
rem  To speed up file copying, load HIMEM.SYS and SMARTDRV.EXE
rem  1: Load HIMEM.SYS in CONFIG.SYS -
rem      DEVICE=HIMEM.SYS
rem  2: Load SMARTDRV.EXE before running CYLDIR -
::       SMARTDRV.EXE 4096 16>nul


rem  ODI'S LFN TOOLS
rem  ===============
rem  
rem  Odi's LFN Tools: LDIR.EXE v1.75
rem                   LCOPY.EXE v1.75
rem  
rem  This is a means of copying files off a damaged HDD (one which,
rem  although Windows will not run, is accessible in DOS) to a safe
rem  destination (i.e. an undamaged disk), in DOS, while preserving
rem  the Long File Names.
rem  
rem  
rem  *** Set PATH to include LFN tools ***
:: SET PATH=%path%;C:\WINDOWS\COMMAND\UTILS;C:\WINDOWS\COMMAND\HDD_FIX
rem  
rem  
rem  *** Directory Listing with Long File Names ***
rem   ** Pauses after each screen **
:: LDIR.EXE /P
rem  
rem  NB: A damaged disk will crash the system if the DOS command DIR
rem      is used, because the computer cannot determine the amount of
rem      free disk space. LDIR can obtain a directory listing in that
rem      situation, as it does NOT display the amount of free space!
rem  
rem  
rem  *** LCOPY.EXE: Long filename version of COPY.EXE ***
rem  ** Copy file in DOS preserving its Long File Name **
rem  
rem  SYNTAX -
rem  LCOPY "[Source]" "[Destination]"
rem  
rem  Example:
rem  LCOPY "C:\PROGRA~1\TELEVI*" "F:\DATA"
rem  
rem  1. The file LCOPY.EXE must be located in the DOS path.
rem     (Set the PATH in autoexec.bat, e.g. SET PATH=A:\;F:\)
rem  
rem  2. The destination directory must already exist, and
rem     must be a valid DOS directory name (i.e. in 8.3 format).
rem  
rem  3. It is NOT necessary to define a name for the file in the
rem     destination instruction.
rem  
rem  4. If the long file name contains spaces, the source and the
rem     destination must BOTH be enclosed in quotation marks.
rem  
rem  5. The DOS wildcard *.* is not valid. The wildcard * must be
rem     used instead.
rem  
rem  6. The wildcard * must come BEFORE the first space in the long
rem     file name for the source to be valid.
rem  
rem  7. The switch /A copies ALL files, including HIDDEN files.
rem  
rem  8. To copy only directory structure use: LCOPY . {dest} /S
rem     NB: The destination {dest} must be a valid path, e.g. F:\


rem  *** COPY all files in current directory to Floppy Disk in A: ***
rem   ** Use of LCOPY.EXE preserves the Long File Names **
rem  
rem  *** Copy ALL files in current directory ***
:: LCOPY.EXE "*" A:\ /A
rem  
rem  *** Include all SUBDIRECTORIES of current (the /S switch) ***
:: LCOPY.EXE "*" A:\ /A /S


rem  *** COPY all files in current directory to RAM disk in F: ***
rem   ** Use of LCOPY.EXE preserves the Long File Names **
rem  
rem  *** Copy ALL files in current directory ***
:: LCOPY.EXE "*" F:\ /A
rem  
rem  *** Include all SUBDIRECTORIES of current (the /S switch) ***
:: LCOPY.EXE "*" F:\ /A /S
rem  
rem  
rem  Note:
rem  
rem  To provide a RAM disk in DOS, add this to CONFIG.SYS:
rem  device=ramdrive.sys /E 28672
rem  
rem  NB: RAMDRIVE.SYS is included on WinME's Emergency Boot Disk


rem  *** COPY all files in current directory to USB disk in F: ***
rem   ** Use of LCOPY.EXE preserves the Long File Names **
rem  
rem  *** Copy ALL files in current directory ***
:: LCOPY.EXE "*" F:\ /A
rem  
rem  *** Include all SUBDIRECTORIES of current (the /S switch) ***
:: LCOPY.EXE "*" F:\ /A /S
rem  
rem  
rem  Note: USB 1.1 drivers for DOS
rem  
rem  To provide USB access in DOS, add these lines to CONFIG.SYS:
rem  device=USBASPI.SYS
rem  device=DI1000DD.SYS
rem  
rem  To connect both a USB 2.0 CD drive AND external USB 2.0 hard disk
rem  simultaneously -
rem  (a) Include the following lines, in this order, in CONFIG.SYS:
rem       device=HIMEM.SYS
rem       device=USBASPI.SYS /e
rem       device=USBCD.SYS /d:USBCD001
rem       device=DI1000DD.SYS
rem  (b) Include the following line in AUTOEXEC.BAT:
rem       MSCDEX /d:USBCD001
rem  
rem  
rem  Driver #1: USBASPI.SYS
rem  
rem  ASPI Manager for USB mass-storage v2.24
rem  Panasonic Communications Co 2000-2007
rem  
rem  Syntax:
rem  device=USBASPI.SYS [/e] [/o] [/u] [/v] [/w] [/r] [/l[#]]
rem  [/slow] [/nocbc]
rem  
rem  /e      EHCI, for enabling EHCI add-on USB 2.0 controller
rem  /o      OHCI, for enabling OHCI add-on/onboard USB 1.1 controller
rem  /u      UHCI, for enabling UHCI onboard USB 1.1 controller
rem  /v      Verbose mode, useful for troubleshooting
rem  /w      Wait, displays message to prompt attaching of USB device
rem  /r      Resident, load as memory resident if USB floppy detected
rem  /l#     Luns, specify highest number of LUN assigned: default /L0
rem  /slow   Use SLOW mode, gives longer delays on scanning USB ports
rem  /nocbc  No CardBus Controller, disable detection on CardBus slots
rem  
rem  You can specify more than one controller type (e.g. /o /e). Use
rem  this feature to specify which port types to enable: limiting
rem  the port types that are scanned for results in a faster startup.
rem  
rem  These options work on Tiny Computers PC (Intel Celeron chipset):
rem  device=USBASPI.SYS /v
rem  device=USBASPI.SYS /o /v
rem  device=USBASPI.SYS /e /v
rem  device=USBASPI.SYS /o /e /v
rem  
rem  
rem  Driver #2: DI1000DD.SYS
rem  
rem  ASPI Disk Driver v2.00
rem  (c) 2001 NOVAC Co Ltd
rem  
rem  USBASPI.SYS merely maps USB devices to an ASPI device. An
rem  additional driver, DI1000DD.SYS, is needed to map the ASPI
rem  mass storage to a DOS drive letter.
rem  
rem  NB: DI1000DD.SYS version 1 only supported FAT16; but FAT32
rem      support was added to version 2.

rem  Notes:
rem  
rem  1. If the files to be recovered are too large for a floppy,
rem     or a USB pen drive, attach a second HDD to an IDE cable
rem  
rem  2. LCOPY.EXE and other LFN utils could be held on Drive E:
rem     (a RAM disk where rescue utils are stored for carrying
rem      out data recovery on an IDE Hard Disk)
rem  
rem  3. For other methods of providing USB access in DOS, see:
rem     (a) www.computing.net/answers/dos/usb-20-drivers-for-dos/13447.html
rem     (b) www.unet.univie.ac.at/~a0503736/php/drdoswiki/index.php?n=Main.USB


rem  UNDELETE
rem  ========
rem  
rem  This is a means of recovering files accidentally deleted.
rem  
rem  
rem  A. Undelete files in DOS -
rem  
rem  1. NORTON'S UNERASE FOR DOS
rem  
rem  Recover deleted files using Norton's UNERASE for DOS (UNERASE.EXE)
rem  which is one of the rescue tools included in -
rem  (a) Norton Utilities 2001
rem  (b) Norton Utilities 2002
rem  (c) Disk 1 of the Norton Emergency Disks (a set of 4 floppy disks)
rem  
rem  Syntax:
rem  
rem  UNERASE [pathname] [/IMAGE|/MIRROR|/NOINFO] [/NOTRACK]
rem          [/PROTECTED|/NOPROTECTED] [/LIST] [/G0] [/BW|/LCD]
rem  
rem  pathname      Name of file to recover.
rem  /IMAGE        Use Image recovery info (excludes Mirror info).
rem  /MIRROR       Use Mirror recovery info (excludes Image info).
rem  /NOINFO       Exclude both Image and Mirror recover info.
rem  /NOTRACK      Exclude Delete Tracking information.
rem  /PROTECTED    Only recover files protected by SmartCan,
rem                Norton Protection, or Delete Sentry.
rem  /NOPROTECTED  Exclude files protected by SmartCan,
rem                Norton Protection, or Delete Sentry.
rem  /LIST         List the erased files available for recovery.
rem  /G0           Disable graphical mouse and all graphical characters.
rem  /BW, /LCD     Improve display on monochrome or LCD monitors.
rem  
rem  NB: SmartCan, Norton Protection and Delete Sentry provide a type of
rem      Recycle Bin for exclusively DOS-based systems; but it's one that
rem      *can't* be used on a Windows 9x system.
rem  
rem      Unless SmartCan, Norton Protection or Delete Sentry is installed,
rem      the /LIST option will show only those files that can be recovered
rem      using ordinary DOS methods.
rem  
rem  *** Run Norton Unerase for DOS ***
:: UNERASE
rem  
rem  *** List all Recoverable Files ***
:: UNERASE /LIST
rem  
rem  *** Undelete a Specific file ***
rem  NB: Insert the actual Path and Filename
:: UNERASE C:\RECOVER.ME
rem  
rem  
rem  2. TESTDISK
rem  
rem  Alternatively, recover deleted files using TestDisk:
rem  See above, under heading "TESTDISK.EXE"
rem  
rem  Alternatively, do a Google search for other DOS undelete programs:
rem  http://www.google.com/search?btnG=Google+Search&as_epq=DOS+unerase
rem  http://www.google.com/search?btnG=Google+Search&as_epq=DOS+undelete
rem  
rem  
rem  B. Undelete files in Windows -
rem  
rem  Restoration v2.5.14
rem  File undelete utility for Win98/ME/2000/XP (FAT/FAT32/NTFS partitions)
rem  
rem  Restoration is a tool to undelete files. You can scan for all files
rem  that may be recoverable, and limit the results by entering a search
rem  term or extension. The program is small and standalone; it does NOT
rem  require installation, and can run from a Floppy disk.


rem  WINDOWS UTILITIES
rem  =================
rem  
rem  Boot from Hard Disk:
rem  
rem  To use Windows tools to recover files from a damaged hard disk,
rem  attach the damaged disk as the PRIMARY SLAVE on the IDE cable
rem  and boot from an undamaged hard disk as the IDE Primary Master.
rem  
rem  
rem  Boot from CD:
rem  
rem  Load Windows from a rescue CD.
rem  
rem  An alternative to booting from a hard disk is to boot from a CD
rem  (one which has all the necessary Operating System components to
rem   be bootable), e.g. the Ultimate Boot CD burned to a CD-RW disc.
rem  
rem  NB: Creating a bootable CD to run BartPE is NOT an option, as it
rem      requires Windows XP.


rem  UNTESTED UTILS
rem  ==============
rem  
rem  A number of as-yet untried utilities to recover data are stored on
rem  the 8GB USB pendrive disk at F:\SAVED\RECOVER awaiting evaluation.


::  //  ::


rem                      -------------------------
rem                      SECTION C: ERROR MESSAGES
rem                      -------------------------


rem                        BLUE SCREEN OF DEATH
rem                        ====================


rem  BLUE SCREEN OF DEATH (BSOD)
rem  ===========================
rem  
rem  A Blue Screen error does NOT usually indicate a fatal problem.
rem  
rem  The Blue Screen of Death (also known as a STOP error) is the error
rem  screen which is displayed by the Operating System on encountering
rem  a system error during startup.
rem  
rem  Although it's called the "screen of death", the system has been
rem  halted to PREVENT damage occuring; a blue screen does *not* of
rem  itself cause any damage.
rem  
rem  It does NOT indicate a disk fault, as Windows was able to get
rem  far enough along in the startup process to encounter a startup
rem  error. The blue screen is in fact supplied by Windows.
rem  
rem  In Windows 9x, a blue screen is the main way the Operating System
rem  has of notifying the user of the presence of an incompatible
rem  device driver. Fixing this is only a minor problem.
rem  
rem  Alternatively, the blue screen might be caused by a hardware fault.
rem  If so, it can be fixed by installing a repacement for the faulty
rem  RAM, PSU or fan (all inexpensive items), as the case may be.
rem  
rem  
rem  SAFE MODE -
rem  
rem  It may be possible to start Windows, by booting into Safe Mode.
rem  
rem  To do this, restart the computer, and repeatedly press F5 or F8
rem  or CTRL (it varies, depending on the make and model of computer)
rem  at intervals of one second during the initial loading process.
rem  
rem  This starts Windows without loading any device drivers (i.e. it
rem  by-passes any faulty drivers present), so enabling you to use
rem  Windows (rather than DOS) to fix the fault which is causing the
rem  blue screen error and the inability to start normally.
rem  
rem  
rem  DIAGNOSING THE CAUSE -
rem  
rem  A blue screen can be caused by (1) incompatible device drivers,
rem  (2) poorly written device drivers, (3) bugs in the kernel of the
rem  Operating System, or (4) faulty hardware.
rem  
rem  The most common cause is faulty or incompatible device drivers
rem  (.DLL and .VXD files). At bootup, Windows tries to load all
rem  the .DLL and .VXD files in the computer; if it encounters one
rem  it can't load, the system is halted and the blue screen shown.
rem  
rem  Review any recently installed software, which may have installed
rem  incompatible driver files, e.g. files that were written for WinXP.
rem  Try *uninstalling* the software in question; or manually remove
rem  the files it added to the disk: i.e. physically delete those files
rem  from the disk, and remove all references to those files from the
rem  Windows Registry (or replace the Registry with a backup copy).
rem  
rem  
rem  Manually Removing the Files:
rem  
rem  The usual cause of the Blue Screen is simply installing the wrong
rem  device driver. Typically it will be caused by a WinXP file being
rem  installed in a Win9x system. Delete or rename that file, in DOS,
rem  using the following procedure.
rem  
rem  NB: A driver file is one with the file extension .DLL or .VXD;
rem      and just deleting or renaming the file(s) causing the problem
rem      (and then rebooting) will normally cure it.
rem  
rem  The computer can usually be restored to normal working by deleting
rem  the faulty or incompatible file(s) from the hard disk (or renaming
rem  the file(s), e.g. from .DLL to .DL_), without having to make any
rem  changes in the Registry. This should be tried first.
rem  
rem  NB: It is poor tactics to delete a file physically, in case it turns
rem      out to be the WRONG file. It is safer to merely rename it.
rem  
rem  It may mean spending a lot of time in a trial-and-error process
rem  of renaming one file at a time (in the directories C:\WINDOWS and
rem  C:\WINDOWS\SYSTEM and C:\WINDOWS\SYSTEM32\DRIVERS), to establish
rem  the identity of the faulty file(s).
rem  
rem  A directory listing, at the DOS prompt, will list the files by date
rem  (displaying a date for each file). The *newest* files are the ones
rem  to suspect first!
rem  
rem  It may be prudent to rename *all* files bearing the date that the
rem  fault arose, in all *three* directories, then restart normally.
rem  
rem  *** Directory Listing sorted by Date ***
:: DIR *.DLL /-W /P
:: DIR *.VXD /-W /P
rem  
rem  NB: Working in DOS, the date you see in a Directory listing is the
rem      "Modified" date (the date on which the file was last modified).
rem      This is NOT its "Created" date (the date it was added to the
rem      disk); so the files with the latest dates are NOT necessarily
rem      the ones added by the suspect installation program.
rem  
rem  Windows ME records a Bootup Log (as C:\BOOTLOG.TXT), on startup, if
rem  the options BootMenu=1 and DisableLog=0 are set in the C:\MSDOS.SYS
rem  file; so set those options and then restart the computer. This log
rem  might record the last step taken before the STOP error occurs. If so,
rem  the log may tell you which file the system was trying to load that
rem  caused the fault: it will be the last entry in the log.
rem  
rem  *** Routine to Edit MSDOS.SYS ***
:: C:
:: CD \WINDOWS\COMMAND
:: ATTRIB -R -H -S C:\MSDOS.SYS
:: EDIT C:\MSDOS.SYS
rem  
rem  *** Routine to View the Boot Log ***
:: C:
:: CD \WINDOWS\COMMAND
:: ATTRIB -R -H C:\BOOTLOG.TXT
:: EDIT C:\BOOTLOG.TXT
rem  
rem  Additionally, Windows ME keeps a copy of the previous bootup log,
rem  in the file C:\BOOTLOG.PRV, which, being from before the Blue Screen
rem  error, will be a complete startup log. A comparison with the latest
rem  (partial) log might show which file the boot process crashed at.
rem  
rem  *** Routine to View the Previous Boot Log ***
:: C:
:: CD \WINDOWS\COMMAND
:: ATTRIB -R -H C:\BOOTLOG.PRV
:: EDIT C:\BOOTLOG.PRV
rem  
rem  
rem  Replacing the Windows Registry:
rem  
rem  If it's necessary to make a change in the Registry, one way to
rem  do so is to restore a known good working backup of the Registry
rem  (i.e. replace the whole Registry). This can only be done in DOS.
rem  
rem  By default, Windows 98/ME keeps up to 5 backup copies of the
rem  Registry in the hidden directory C:\WINDOWS\SYSBCKUP
rem  
rem  Every day, the first time Windows loads successfully a copy of
rem  that valid Registry is saved there as a compressed .CAB file.
rem  
rem  *** View details of the backups available ***
:: DIR C:\WINDOWS\SYSBCKUP\*.CAB /P /-W /OGD
rem  
rem  *** Routine to restore the Windows Registry ***
rem  NB: Follow the on-screen instructions in SCANREG
:: SET PATH=%path%;C:\WINDOWS\COMMAND
:: SCANREG /RESTORE
rem  
rem  NB: It is NOT desirable to backup the current registry first,
rem      because that would overwrite (i.e. destroy) one of the
rem      existing backups: perhaps the very one that's needed!
rem  
rem  It is also possible to *manually* extract a Registry backup
rem  from a .CAB file, and copy it to the correct locations.
rem  
rem  *** Routine to manually extract Registry from .CAB file ***
rem  NB: Rename the .CAB file below to match the actual name
:: SET PATH=%path%;C:\WINDOWS\COMMAND
:: EXTRACT C:\WINDOWS\SYSBCKUP\RB001.CAB *.BAT /L C:\ /Y
:: EXTRACT C:\WINDOWS\SYSBCKUP\RB001.CAB *.SYS /L C:\ /Y
:: EXTRACT C:\WINDOWS\SYSBCKUP\RB001.CAB *.DAT /L C:\WINDOWS /Y
:: EXTRACT C:\WINDOWS\SYSBCKUP\RB001.CAB *.INI /L C:\WINDOWS /Y
rem  
rem  
rem  Blue Screen Error Number:
rem  
rem  The Blue Screen usually displays a message and an error number,
rem  like this:
rem  
rem    number of error (parameter strings) name of error
rem  
rem  All of this information is important in understanding the cause of
rem  the fault. Dependant on the value of "number of error", all or some
rem  of those parameters might contain information as to what went wrong.
rem  
rem  List of STOP errors:
rem  http://pcsupport.about.com/od/findbyerrormessage/tp/stop_error_list.htm
rem  
rem  
rem  Hardware Faults:
rem  
rem  Hardware faults can include faulty RAM memory, power supply issues,
rem  overheating of components (e.g. due to failure of the cooling fan
rem  on the CPU, or another fan inside the computer), hardware running
rem  beyond specification limits, or other hardware faults.
rem  
rem  If you have just made some hardware changes inside the computer,
rem  the most likely cause is an insufficiently tightened cable, an
rem  unattached cable, or some other fault related to the changes made.
rem  Perhaps you failed to correctly attach a device, or inadvertently
rem  loosened another cable while you were working. Perhaps you failed
rem  to seat the new PCI Card or RAM module firmly enough in its slot!
rem  
rem  Obviously you will only encounter hardware running beyond its
rem  specification if you have been over-clocking the CPU. If so,
rem  undo the changes you made.
rem  
rem  If the cause is NOT a faulty installation of the new hardware,
rem  the next step is to disable or remove the newly installed hardware
rem  (and any accompanying software), as doing so may be a complete cure.
rem  
rem  In the case of a fault in existing hardware, to cure the STOP error
rem  fix the hardware fault: fit a replacement RAM memory module of the
rem  same type, or a replacement Power Supply Unit (PSU) of the same type,
rem  or a replacement for the faulty fan (as the case may be). Fan failure
rem  will be obvious; if it is NOT a fan failure, suspect the RAM module
rem  and the Power Supply Unit.
rem  
rem  Note: Whenever you open the computer's case, take the appropriate
rem        anti-static precautions to avoid harming the electronics.
rem        See: http://www.annoyances.org/exec/forum/winme/1177076589
rem  
rem  
rem  USB Disk can cause Blue Screen:
rem  
rem  A blue screen can also occur *during* a Windows session; e.g. if the
rem  user ejects removable media (i.e. unplugs a USB device) while it is
rem  being read from or written to, without following the correct
rem  procedure.
rem  
rem  NB: This commonly occurs with Microsoft Office, if the program is
rem      not closed properly before unplugging a USB disk containing
rem      dependent files.
rem  
rem  
rem  Further Information:
rem  
rem  For further information about STOP errors, read the following article:
rem  http://en.wikipedia.org/wiki/Blue_Screen_of_Death
rem  
rem  Suggestions for additional troubleshooting steps:
rem  http://pcsupport.about.com/od/fixtheproblem/ht/stoperrors.htm


::  /--------------------------------------------------------------------/  ::


rem                       OTHER ERROR MESSAGES
rem                       ====================


rem  ERROR MESSAGE : "Disk / Partition Not Recognised"
rem  =============
rem  
rem  A possible cause might be the BIOS setting changing from LBA to
rem  CHS, if it was previously set to AUTO, as a result of something
rem  being altered in the first sector of the hard disk.
rem  
rem  It's safer to set the BIOS to LBA before setting-up the disk,
rem  which prevents this problem occuring. But even then, if the BIOS
rem  is reset for any reason it will default to AUTO.
rem  
rem  The change will confuse Windows; and where a switch between LBA
rem  and CHS occurs, DOS programs (such as Partition Magic) may not
rem  be able to see the Partitions.
rem  
rem  Solution: Enter the BIOS screen, and set the hard disk option
rem  to LBA (Logical Block Addressing).
rem  
rem  NB: To enter the BIOS, press the appropriate key (e.g. DEL)
rem      (or, on some systems, F1 or F2) repeatedly at startup.
rem  
rem  NB: This is usually a non-fatal error message!


rem  ERROR MESSAGE : "No boot device available" (or similar)
rem  =============
rem  
rem  The following errors all mean that none of the bootable devices,
rem  specified in the bootable sequence set in the BIOS, contains the
rem  signature bytes indicating a valid MBR in its 1st physical sector:-
rem  
rem  "No ROM Basic - System Halted"; or "No boot device available, strike
rem  F1 to retry, F2 for setup utility"; or "No boot sector on fixed disk,
rem  strike F1 to retry boot, F2 for setup utility"; or "Non-System disk
rem  or disk error, replace and strike any key when ready"; or "Disk Boot
rem  Failure, Insert System Disk and Press Enter".
rem  
rem  NB: This is usually a *non-fatal* error message!
rem  
rem  Each partition table entry includes a Boot Indicator byte: these bytes
rem  are at offset 446 (partition table entry #1 (01BE hex)), at offset 462
rem  (partition table entry #2 (01CE hex)), at offset 478 (partition table
rem  entry #3 (01DE hex)), and at offset 494 (partition table entry #4
rem  (01EE hex)). These Boot Indicators are used to determine which partition
rem  is active (i.e. bootable), by checking for the hex value 80; the other
rem  Boot Indicators should all have a value of 00 (zero). If all four entries
rem  are (for instance) 00 hex, bootup will fail.
rem  
rem  Solution: Restore a backup copy of the boot disk's MBR sector guided by
rem  the section "RESTORE A SECTOR" above.
rem  
rem  Alternative Solution: Set the Primary partition of the boot disk to
rem  "active" in the MBR, guided by the section "DISK STRUCTURE NOTES"
rem  above, using a Disk Sector Editor.
rem  
rem  Alternative Solution: Set the Primary partition of the boot disk to
rem  "active" in the MBR, guided by the section "INSTALLING A HARD DISK"
rem  below, using the FDISK.EXE program.  WARNING: Careless use of the
rem  FDISK program can cause fatal and irreversible damage to your files!
rem  
rem  The Last Resort: Partition the hard disk (thereby DESTROYING all
rem  files on it) guided by the section "INSTALLING A HARD DISK" below.
rem  This should automatically set the Primary partition to "active".


rem  ERROR MESSAGE : "Invalid partition table"
rem  =============
rem  
rem  The source of the error message is the MBR. More than one of the
rem  Partition Table entries has its Boot Indicator byte set to a value
rem  of 80 (hex); i.e. more than one partition is marked "active".
rem  
rem  Solution: Set all but one of the boot disk's partitions as "inactive"
rem  (i.e. non-bootable) guided by the section "DISK STRUCTURE NOTES" above,
rem  using a Disk Sector Editor.
rem  
rem  However, a thorough investigation of the MBR's partition table may
rem  be necessary, guided by the section "DISK STRUCTURE NOTES" above,
rem  as the actual problem may be more complex.
rem  
rem  NB: This is usually a non-fatal error message!


rem  ERROR MESSAGE : "Drive X is not formatted" (or similar)
rem  =============
rem  
rem  Windows typically reports that "Drive X is not formatted", or that
rem  "The type of the file system is RAW".
rem  
rem  This means the Boot Sector of the specified partition is damaged.
rem  
rem  Replace the Boot Sector from a backup copy, guided by the section
rem  "RESTORE A SECTOR" above; or repair it manually, guided by the
rem  section "DISK STRUCTURE NOTES" above, using a Disk Sector Editor.


rem  ERROR MESSAGE : "Error Loading Operating system"
rem  =============
rem  
rem  The source of the error message is the MBR. An error was returned
rem  from the BIOS when the boot loader attempted to read the active
rem  partition's Boot Sector into memory.
rem  
rem  Solution: In many cases this will be due to a "soft" ECC error,
rem  and can be repaired by re-writing the Boot Sector.
rem  
rem  Replace the Boot Sector from a backup copy, guided by the section
rem  "RESTORE A SECTOR" above; or re-write it manually, guided by the
rem  section "DISK STRUCTURE NOTES" above, using a Disk Sector Editor.


rem  ERROR MESSAGE : "Operating System Not Found" (or similar)
rem  =============
rem  
rem  Typically, you see the message "Operating system not found"
rem  or "Missing operating system".
rem  
rem  This error means the BIOS could not find an Operating System to
rem  transfer control to. There are two possible causes.
rem  
rem  
rem  The Type #1 error -
rem  
rem  The translation setting in BIOS has changed from LBA to CHS,
rem  causing the bootstrap loader to translate sector addresses
rem  differently (i.e. incorrectly). As a result, the location
rem  of the Boot Sector is not where it is expected to be.
rem  
rem  For disks of 528MB (504MiB) to 8.4GB (7.9GiB), reverse the
rem  translation mode (i.e. set it to LBA again).
rem  
rem  NB: To enter the BIOS, press the appropriate key (e.g. DEL)
rem      (or, on some systems, F1 or F2) repeatedly at startup.
rem  
rem  In other cases, rebuild the MBR's partition table (e.g. from
rem  backups). Note: The command FDISK /MBR (the "fixmbr" command)
rem  will rebuild a standard MBR, except the Partition Table bytes.
rem  
rem  If there then is a remaining boot problem, it can be corrected
rem  by rebuilding the Boot Sector (e.g. from a backup, guided by the
rem  section "RESTORE A SECTOR" above; or re-write it manually, guided
rem  by the section "DISK STRUCTURE NOTES", using a Disk Sector Editor).
rem  
rem  NB: In WinXP, that error on a FAT32 disk (*not* an NTFS disk)
rem      can be fixed with the "fixboot" command; e.g. FIXBOOT C:
rem  
rem  
rem  The Type #2 error -
rem  
rem  On startup, the BIOS (Basic Input Output Self-test) sends a signal
rem  to anything with a ROM chip to make sure it's there.
rem  
rem  Once that hardware check is complete, the boot process is handed over
rem  to the bootstrap loader (for Win9x the loader is IO.SYS), which finds
rem  the Master Boot Record (MBR) and tries to load the Operating System;
rem  but the latter is not found.
rem  
rem  Boot from a bootdisk: but only use a bootdisk which matches your
rem  Operating System (i.e. if you have WinME on the hard disk, you
rem  *must* use a WinME bootdisk); otherwise the fault will not be cured.
rem  
rem  Once booted to a DOS prompt -
rem  
rem  1. Use FDISK.EXE to check that the partitions are intact:
rem  
::      FDISK /STATUS
rem     
rem     NB: Do NOT use any other FDISK command in this situation!
rem         All other FDISK commands are dangerous to your files.
rem  
rem  2. Then run SCANDISK.EXE (Scandisk for DOS) to check the disk:
rem  
::      SCANDISK C: /CHECKONLY /SURFACE
rem  
rem     NB: Do NOT allow SCANDISK to make any changes to the disk!
rem  
rem  3. If all seems well, at the A: prompt type SYS C: to make the drive
rem     bootable (this copies key Operating System files to Drive C):
:: A:
:: CD \
:: SYS C:
rem  
rem  You should then be able to boot into Windows. (If not, you may have
rem  faulty hardware: see "HARDWARE FAULTS", below.)


rem  ERROR MESSAGE : Hangs at "Verifying DMI Pool Data"
rem  =============
rem  
rem  The Desktop Management Interface (DMI) is a method of managing
rem  Windows 9x computers. The main component of DMI is the Management
rem  Information Format Database or MIFD (the DMI Pool Data): this
rem  contains all the information about the computer and its components.
rem  
rem  Any changes to the motherboard BIOS settings, the hard disks, or
rem  the hard disk settings will all alter this pool data: the message
rem  "Verifying DMI Pool Data" will appear. If the system then hangs
rem  (a condition which can persist even if you *remove* the new hardware
rem  in question!) try this:
rem  
rem  1. Switch on mains power and start the computer.
rem  2. Access the BIOS screen. [Press the appropriate key (e.g. DEL)
rem     (or, on some systems, F1 or F2) repeatedly at startup]
rem  3. Disable both the Internal and External CPU Caches: these are
rem     in either the "BIOS Features" or "Advanced Settings" options
rem     of the BIOS screen.
rem  4. Save the BIOS changes, then restart the PC with a bootable
rem     floppy disk. On startup, the screen should read -
rem        Verifying DMI Pool Data
rem        Update Successful
rem     and the system should then continue loading normally.
rem  5. After the system successfully loads, re-start the PC and
rem     access the BIOS screen.
rem  6. Enable the External CPU Cache in the BIOS.
rem     Note: For optimal system performance, this feature
rem           MUST be enabled!
rem  7. Save the BIOS changes, then restart the PC with a bootable
rem     floppy disk. On startup, the screen should read -
rem        Verifying DMI Pool Data
rem        Update Successful
rem     and the system should then continue loading normally.
rem  
rem  Alternatively:
rem  
rem  1. Switch off the mains power (but do NOT unplug the PC from
rem     the wall socket). Then disconnect the power connector and
rem     the IDE cable from each hard disk.
rem  2. Switch on at the mains, then start the computer.
rem  3. Access the BIOS [Press the appropriate key (e.g. DEL)
rem     (or, on some systems, F1 or F2) repeatedly at startup]:
rem     then set each hard disk's type as "None" or "Not Installed";
rem     then load the BIOS defaults; then load the SETUP defaults.
rem  4. Save the BIOS changes, then restart using a bootable floppy.
rem  5. Shutdown the PC after the memory count is displayed.
rem  6. Reconnect the power connector and IDE cable to each hard disk.
rem  7. Restart the PC and enter the BIOS (as described above);
rem     then use the BIOS to Auto-Detect the hard disk(s).
rem     Ensure that LBA Mode is enabled for EVERY hard disk.
rem  8. Save the BIOS changes, then reboot using a bootable floppy.
rem  9. Restart the system. On startup, the screen should read -
rem        Verifying DMI Pool Data
rem        Update Successful
rem     and the system should then continue starting normally.
rem  
rem  If the above fails to solve the problem, reset the system BIOS
rem  by removing the motherboard's battery for a few seconds (or by
rem  opening the "Clear CMOS" Jumper on the motherboard for a few
rem  seconds), to clear the stored contents in the CMOS chip.
rem  
rem  As a last resort, reset the system BIOS by doing a flash-upgrade
rem  of the BIOS firmware settings (in the motherboard's EEPROM chip),
rem  by downloading a BIOS Upgrade program from the motherboard
rem  manufacturer's website and running it at the DOS prompt.
rem  
rem  Note: Whenever you open the computer's case, take the appropriate
rem        anti-static precautions to avoid harming the electronics.
rem        See: http://www.annoyances.org/exec/forum/winme/1177076589


rem  ERROR MESSAGE : "Invalid system disk"
rem  =============
rem  
rem  This message means there are no startup files on the active
rem  partition (i.e. C:). Either the startup files are corrupt,
rem  or the drive has bad sectors.
rem  
rem  
rem  A. Corrupt Startup Files -
rem  
rem  To repair corrupt startup files, start the computer using
rem  a bootable floppy disk (e.g. from http://www.bootdisk.com).
rem  
rem  NB: The floppy disk MUST contain the same version of DOS that is
rem      installed on the PC being repaired. So to repair a PC running
rem      Windows ME, the boot floppy MUST be a Windows ME boot disk
rem      (e.g. the Windows ME Emergency Boot Disk).
rem  
rem  *** Install the System Files on Drive C: ***
rem  
rem  1. Use FDISK.EXE to make sure the partitions are intact:
:: FDISK /STATUS
rem  
rem  2. Then run SCANDISK.EXE (Scandisk for DOS) to check the disk:
rem     (NB: Do NOT allow SCANDISK to make any changes to the disk)
:: SCANDISK C: /CHECKONLY /SURFACE
rem  
rem  3. If all seems well, at the A: prompt type SYS C: (to install
rem     the system files on Drive C):
:: A:
:: CD \
:: SYS C:
rem  
rem  
rem  B. Bad Sectors -
rem  
rem  Methods of recovering from bad sectors (a.k.a. "bad blocks")
rem  
rem  (1) Clone the Disk:
rem  
rem      Copy the affected disk to a new hard disk using a disk cloning
rem      program that can tolerate bad sectors, e.g. Norton's GHOST.
rem      [Note: Most cloning programs CANNOT cope with bad sectors!]
rem  
rem      Norton's GHOST for DOS v8.3 (GHOST.EXE) can clone an entire disk
rem      (but it only works with IDE disks, not SATA or SCSI or USB).
rem  
rem      NB: Whenever you open the computer's case, take the appropriate
rem          anti-static precautions to avoid harming the electronics.
rem          See: http://www.annoyances.org/exec/forum/winme/1177076589
rem  
rem      To run GHOST for DOS v8.3 with the option to ignore bad sectors,
rem      use the option -FRO
rem  
rem      Note: Norton Ghost 2003 is notorious for creating corrupt image
rem            files, due to faulty compression, although it's okay for
rem            normal (i.e. uncompressed) disk-to-disk direct cloning.
rem            (Norton's Ghost for DOS v8.3 does NOT have this fault!)
rem  
rem      It can clone a disk to a smaller one, provided the contents
rem      (i.e. data) on the source disk do not exceed the capacity of
rem      the destination disk: i.e. if the difference is just free space.
rem  
rem  
rem      Syntax -
rem  
rem      MODE=COPY
rem      Copies the contents of one disk to another (file-by-file)
rem  
rem      MODE=PCOPY
rem      Clones a partition to another partition (byte-by-byte)
rem  
rem      SRC=Source
rem      Drive number, or Drive number and Partition number
rem  
rem      DST=Destination
rem      Drive number, or Drive number and Partition number
rem  
rem      SRC and DST examples in PCOPY mode:-
rem      1:2 means the 2nd partition on the 1st disk
rem      2:1 means the 1st partition on the 2nd disk
rem  
rem  
rem      Examples -
rem  
rem      1. Copy disk 1 to disk 2:
rem         GHOST.EXE -clone,mode=copy,src=1,dst=2
rem  
rem      2. Clone the 2nd partition of disk 1 on
rem         the 1st partition of disk 2:
rem         GHOST.EXE -clone,mode=pcopy,src=1:2,dst=2:1
rem  
rem  
rem      ***  To clone a bootable Hard Disk on a new Hard Disk   ***
rem       ** Copy Partition 1 of Disk 1 to Partition 1 of Disk 2 **
::       GHOST.EXE -clone,mode=pcopy,src=1:1,dst=2:1 -FRO -PMBR
rem  
rem      Alternative, if Disks 1 and 2 each have only 1 partition:
::       GHOST.EXE -clone,mode=copy,src=1,dst=2 -FRO -PMBR
rem  
rem  
rem      Options that may be useful for troubleshooting:
rem  
rem      -FRO    : Forces Ghost to continue cloning even if the
rem                source contains bad sectors
rem  
rem      -FX     : Forces Ghost to eXit to DOS after the operation
rem                is complete
rem  
rem      -FFATID : Changes the partition ID of the DESTINATION to the
rem                recommended partition ID for that FAT32 partition
rem                [The partition ID is stored in the partition table]
rem  
rem      -PMBR   : Specifies that the Master Boot Record of the
rem                DESTINATION disk be preserved when performing
rem                a Disk-to-Disk or Image-to-Disk operation
rem  
rem  
rem      Other command line options are summarised at:
rem  
rem      http://service1.symantec.com/SUPPORT/on-technology.nsf/docid/
rem      1998082612540625
rem  
rem      http://service1.symantec.com/SUPPORT/on-technology.nsf/docid/
rem      1998082413392025
rem  
rem  
rem      *** Display Ghost's help screen ***
::       GHOST /?
::       GHOST -?
rem  
::       *** Display details of all Drives detected ***
::       GHOST -dd
rem  
rem      *** Save details of all Drives detected ***
::       GHOST -dd > drives.txt
rem  
rem  
rem      WARNING -
rem  
rem      Never start Windows with BOTH source and clone attached
rem      to the IDE cables, as that will cause a fault! The clone
rem      must NOT be attached to the same computer, except in DOS.
rem      See: http://thestarman.pcministry.com/asm/mbr/mystery.htm
rem  
rem      NB: It may be okay if one of them is attached through a USB
rem          port (i.e. as an external disk), or attached through a
rem          SATA controller (i.e. as either an internal or external
rem          SATA disk); but *not* if both are on the IDE cables!
rem  
rem      The fault can be prevented by manually zeroing the six bytes
rem      DA to DF (bytes 218 to 223) in sector CHS 0-0-1 (LBA sector 0)
rem      [the MBR sector], the "mystery bytes", before starting Windows.
rem  
rem      NB: It is believed these bytes are a serial number, that
rem          Windows uses to identify the different IDE disks; so
rem          it can't cope if two IDE disks have the same number.
rem          Zeroing these bytes forces Windows to re-allocate a
rem          new serial number to the disk, on the next bootup,
rem          thereby preventing a clash of disk addresses.
rem  
rem      Alternatively, when the cloning is completed do NOT let Ghost
rem      "reset" the computer. Rebooting to Windows will CAUSE the fault!
rem      Instead, shutdown the computer, then remove the source disk; then
rem      install the CLONE as IDE Primary Master BEFORE booting to Windows.
rem  
rem  
rem      The fault may cause the following errors:
rem  
rem      1. Windows may refuse to start.
rem  
rem         Restart in DOS, and use Norton's Disk Editor (above) to
rem         set all six of the "mystery bytes" to 00 (zero hex), in
rem         sector CHS 0-0-1 (LBA sector 0) of the destination disk.
rem  
rem      2. Windows may WIPE the system registry.
rem  
rem         The registry can be *restored* in DOS from the backups in
rem         C:\WINDOWS\SYSBCKUP by using the following commands (and
rem         then carrying out the on-screen instructions):
rem  
::          SET PATH=%path%;C:\WINDOWS\COMMAND
::          SCANREG /RESTORE
rem  
rem      3. Windows may change the Volume Identifier on the destination
rem         disk, setting it as non-bootable (as it's not the IDE Primary
rem         Master). When installed as Primary Master, it then can't boot.
rem  
rem         Use PowerQuest's Partition Table Editor (above) to set the
rem         Primary DOS partition on the disk to "active" (i.e. bootable).
rem  
rem  
rem      Note: If the hard disk does NOT have bad sectors, the cloning
rem            program DiscWizard (see below) is easier to use than Ghost.
rem            DiscWizard, from Seagate, is for setting up a new Seagate
rem            disk; but the cloning utility (called 'Copy a Partition')
rem            works with ANY make of disk: it was designed to copy
rem            whatever existing disk the user had, onto his new Seagate
rem            disk, as a byte-by-byte copy (in order that the copy would
rem            be bootable if the original was, by preserving all settings).
rem  
rem            The program Data Lifeguard Tools for DOS v11.2, from
rem            Western Digital, can also clone a hard disk (below).
rem  
rem            The program Media Tools Professional v5.0 can also clone
rem            a hard disk (below).
rem  
rem            The program HDClone v3.6 can also clone a hard disk (below).
rem  
rem  
rem  (2) HDD Regenerator:
rem  
rem      HDD Regenerator, v1.31
rem  
rem      This utility *repairs* bad sectors on a HDD. It can
rem      regenerate the magnetic surface, at least temporarily.
rem  
rem      *** Create bootable floppy containing DOS version ***
rem       **  Requires one 1.44MB floppy disk in Drive A:  **
:: SET PATH=%path%;F:\SAVED\RECOVERY\HARDWARE\REGEN
:: REGEN.EXE
rem  
rem      Clone the repaired HDD immediately, because this
rem      type of repair is only a temporary solution!
rem  
rem      NB: Whenever you open the computer's case, take the appropriate
rem          anti-static precautions to avoid harming the electronics.
rem          See: http://www.annoyances.org/exec/forum/winme/1177076589
rem  
rem  
rem  (3) The Norton DiskEdit method (in Windows):
rem  
rem      Step 1: Edit the registry to make Scandisk check bad clusters
rem  
rem              (a) START - RUN - REGEDIT
rem              (b) Go to: HKEY_CURRENT_USER\Software\Microsoft\Windows\
rem                  CurrentVersion\Applets\Check Drive
rem              (c) Double click on "Settings" in the right-hand pane
rem              (d) There are four pairs of digits: change last pair to 04
rem  
rem      Step 2: Go to START - RUN and type SCANDSKW then click on "Thorough"
rem              and *uncheck* "Automatically Fix Errors"
rem  
rem      Step 3: Wait while it slowly goes through the surface scan. When it
rem              finds bad clusters, it will test them; if it cannot find a
rem              problem with them, it will tell you so, and tell you the
rem              cluster number. Write down the number of each bad cluster,
rem              but select "Leave the cluster marked bad".
rem  
rem              NB: Microsoft says that if you select "Clear the Bad
rem              Cluster" it will remove the "bad" marker. It doesn't!
rem  
rem              NB: If there are any clusters that Scandisk sees as bad,
rem              and agrees that they are bad, it's time to back up your
rem              files and buy a new disk.
rem  
rem      Step 4: Exit to DOS, and run Norton's DISKEDIT
rem  
::       SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE
::       MOUSE
::       SET PATH=%path%;F:\SAVED\RECOVERY\DISKEDIT\NORTON\2002
::       DISKEDIT
rem  
rem      Step 5: Press the ALT and T keys simultaneously, then select
rem              "configuration...", then uncheck the Read-Only box,
rem              then click "OK"
rem  
rem      Step 6: Press the ALT and F1 keys simultaneously, to view
rem              the first FAT (there are 2 FATs)
rem  
rem      Step 7: Using the cluster numbers you wrote down, page down to
rem              find them (using the PgDn key); they'll be marked {Bad}
rem  
rem      Step 8: Select the word "Bad" by using Tab and arrow keys,
rem              then enter "0" (zero)
rem  
rem      Step 9: Press the CTRL and W keys simultaneously, to write
rem              the changes to disk, then press ESC to exit
rem  
rem      Step 10: Run CHKDSK.EXE to check that the system no longer
rem               shows any bad clusters
rem  
rem      This method of repairing bad sectors is, of course, unsafe
rem      if the sector(s) are GENUINELY bad! Do NOT use this repair
rem      if SCANDISK tells you, in Step 3, that any sector is bad!
rem  
rem      Note: Whenever you open the computer's case, take the appropriate
rem            anti-static precautions to avoid harming the electronics.
rem            See: http://www.annoyances.org/exec/forum/winme/1177076589
rem  
rem  
rem  (4) Use ScanDisk for DOS to fix the bad sectors (in DOS):
rem  
::       SET PATH=%path%;%RAMD%:\;E:\;C:\WINDOWS\COMMAND
::       SCANDISK C: /SURFACE
::       SCANDISK D: /SURFACE
rem  
rem      NB: Not practical if the bad sector is in the System Area!
rem  
rem      NB: This "solution" will result in data loss, as ScanDisk
rem          will make changes to the disk in remapping bad sectors
rem          or marking damaged sectors as bad. Try this only AFTER
rem          recovering all recoverable data using other tools.
rem  
rem  
rem  (5) Format the Hard Disk:
rem  
rem      As a last resort, start the computer using a bootable floppy disk
rem      containing FORMAT.COM and then at the A: prompt type FORMAT C:
rem      (if Drive C: is the damaged partition).
rem  
rem      NB: ALL DATA ON THE DISK WILL BE DESTROYED!! Copy all files
rem          on the damaged disk to another disk first, to save them!
rem          (Use the procedures at RECOVER INDIVIDUAL FILES, above)
rem  
rem      FORMAT.COM will display a warning when it finds bad sectors.
rem      It will try to re-map them (i.e. swap them for valid sectors
rem      from the reserve sector pool); if it cannot re-map them,
rem      it will mark them as bad so that they cannot be used.
rem  
rem      Note: See also SPINRITE v6.0, below
rem  
rem      Note: Whenever you open the computer's case, take the appropriate
rem            anti-static precautions to avoid harming the electronics.
rem            See: http://www.annoyances.org/exec/forum/winme/1177076589


rem  CMOS BATTERY DEAD
rem  =================
rem  
rem  The CMOS battery on the motherboard maintains the BIOS settings
rem  while the computer is disconnected from mains power.
rem  
rem  It's typically a lithium/manganese-dioxide battery of type CR2032
rem  that looks like a one-inch silver coin.
rem  
rem  When the battery fails: the computer loses its BIOS settings, so
rem  it will not boot. At startup it displays a blank screen with the
rem  cursor in the top left-hand corner, flashing.
rem  
rem  Solution: Fit a new battery on the motherboard, then enter the
rem  BIOS setup program and manually input the correct BIOS settings
rem  (which are hardware-dependent, so vary from one PC to another).
rem  
rem  NB: To enter the BIOS, press the appropriate key (e.g. DEL)
rem      (or, on some systems, F1 or F2) repeatedly at startup.
rem  
rem  Note: Whenever you open the computer's case, take the appropriate
rem        anti-static precautions to avoid harming the electronics.
rem        See: http://www.annoyances.org/exec/forum/winme/1177076589
rem  
rem  
rem  Backing up the BIOS -
rem  
rem  Before the battery fails, make a backup copy of the BIOS settings
rem  by entering the BIOS setup program and writing down the settings
rem  you see in the various setup menus.
rem  
rem  NB: To enter the BIOS, press the appropriate key (e.g. DEL)
rem      (or, on some systems, F1 or F2) repeatedly at startup.
rem  
rem  Note: Whenever you open the computer's case, take the appropriate
rem        anti-static precautions to avoid harming the electronics.
rem        See: http://www.annoyances.org/exec/forum/winme/1177076589


::  //  ::


rem                      ------------------------
rem                      SECTION D: DISK HARDWARE
rem                      ------------------------


rem     Whenever you open the computer's case, take the appropriate
rem      anti-static precautions to avoid harming the electronics.
rem       [http://www.annoyances.org/exec/forum/winme/1177076589]


rem                         DISK SURFACE FAULTS
rem                         ===================


rem  SPINRITE v6.0
rem  =============
rem  
rem  SpinRite tests and repairs a hard disk, byte by byte. It tests whether
rem  data can be read from and written to each sector on the disk; and then
rem  tries to recover data from any unreadable sectors.
rem  
rem  Similar to ScanDisk, but much more thorough.
rem  
rem  It has 5 levels, level 2 (for routine maintenance) being quite fast,
rem  and level 5 (for data recovery from a damaged disk) being very slow.
rem  
rem  Serial number: WS2YNDQ4VNW2M-C
rem  
rem  
rem  Note:
rem  In practice, SpinRite v6.0 could NOT recover data from a damaged FAT
rem  on a crashed hard disk, nor could it access the affected sectors!


rem  NORTON'S DISK EDITOR
rem  ====================
rem  
rem  It is possible to manually recondition ALL the affected sectors
rem  using Norton's DiskEdit. Like SpinRite, it CANNOT read 99% of
rem  affected sectors; but DiskEdit successfully reconditions them,
rem  i.e. restores them ALL to normal use, which SpinRite cannot do.
rem  
rem  NB: This solution works if the fault is a "soft" ECC error, but
rem      NOT if the fault is physical damage to the magnetic surface.
rem  
rem  The trick is to have DiskEdit access each affected sector (i.e. each
rem  inaccessible sector), one by one; and you manually write a pattern of
rem  512 bytes of new data (ANY data!) to the affected sector. This new
rem  data, once written, makes the sector accessible normally again.
rem  
rem  NB: Although "accessing" an inaccessible sector sounds impossible,
rem      DiskEdit will go to such a sector (e.g. if you scroll down the
rem      screen using the PgDn key), and try to read it; but will report
rem      that it can't be read, and will display 512 zeros (00 hex).
rem  
rem      If you then type 512 random characters (or even just 1 character)
rem      into the sector, then try to leave the sector, DiskEdit will (if
rem      the sector is not *physically* damaged!) save those new characters
rem      to that sector, which will then be accessible normally.
rem  
rem      All the data which was originally in the sector is lost, but you
rem      have restored the sector to normal use. It now contains the data
rem      you typed in (e.g. 1 character and 511 zero's) in its 512 bytes.
rem  
rem  With a damaged FAT, once every sector of the entire FAT has been
rem  repaired in this way it is then possible to copy a backup of the FAT
rem  to those sectors (successfully), and so copy files off the disk!
rem  
rem  *** Run Norton DiskEdit 2002: FAT32, HDD exceeding 32GB ***
rem   **       (DISKEDIT.EXE in Norton Utilities 2002)       **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE
:: MOUSE
:: SET PATH=%path%;F:\SAVED\RECOVERY\DISKEDIT\NORTON\2002
:: DISKEDIT


rem  NORTON'S DISK DOCTOR
rem  ====================
rem  
rem  NDD.EXE from Norton Utilities 2001 (v5.0)
rem  
rem  Diagnoses (and repairs) damaged disks.
rem  (NB: Norton Utilities 2001 recognises FAT32 and disks exceeding 32GB)
rem  
rem  
rem  SYNTAX -
rem  
rem  NDD [d:][d:]... [/C|/Q|/DT] [/R[A]:pathname] [/X:drives] [/FIXSPACES]
rem                  [/NOCOMP] [/NOHOST] [/G0] [/BW|/LCD]
rem  NDD [d:][d:]... /REBUILD [/G0] [/BW|/LCD]
rem  NDD [d:][d:]... /UNDELETE [/G0] [/BW|/LCD]
rem  NDD             /UNDO [/G0] [/BW|/LCD]
rem  
rem  /C               Complete test, including surface test.
rem  /Q               All tests except surface test.
rem  /DT              Only perform the surface test.
rem  /R[A]:pathname   Write (or Append) report to pathname.
rem  /X:drives        Exclude drives from testing.
rem  /FIXSPACES       Repair filenames with embedded spaces.
rem  /NOCOMP          Do not test compression structures.
rem  /NOHOST          Do not test host drive of compressed volumes.
rem  /REBUILD         Rebuild an entire disk that has been destroyed.
rem  /UNDELETE        Undelete a partition that was previously skipped.
rem  /UNDO            Undo repairs made in a prior session.
rem  /G0              Disable graphical mouse and all graphical characters.
rem  /BW, /LCD        Improve display on monochrome or LCD monitors.
rem  
rem  *** Run Norton Disk Doctor: ALL disks ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\NDD
:: NDD.EXE
rem  
rem  *** Complete test, including Surface scan: Specified Disk only ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\NDD
:: NDD C: /C
:: NDD D: /C
:: NDD E: /C
rem  
rem  *** Test, excluding Surface scan: Specified Disk only ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\NDD
:: NDD C: /Q
:: NDD D: /Q
:: NDD E: /Q
rem  
rem  
rem  WARNING: Do *not* allow Disk Doctor to make any changes to the disk
rem           (unless you use its UNDO function to enable you to reverse
rem           all changes), because Disk Doctor is *not* 100% reliable!
rem  
rem           It is a useful tool for diagnosing what the fault(s) are; but
rem           its repair functions make too many (unwarranted) assumptions,
rem           so treat it with caution.


rem  SEATOOLS DESKTOP
rem  ================
rem  
rem  SeaTools Desktop v3.02 (a.k.a. SeaTools Disc Diagnostic, Desktop Edition)
rem  
rem  The setup program SEATOOLD_EN.EXE creates a bootable floppy disk in
rem  Drive A. The disk loads its own operating system instead of DOS or
rem  Windows, so will always work, regardless of the Operating System in
rem  your computer.
rem  
rem  The program can repair bad sectors. It achieves results that no other
rem  program can match, and fixes faults where "SeaTools for DOS" fails.
rem  
rem  
rem  SeaTools Desktop v3 has the following drawbacks -
rem  
rem  (1) It hogs 100% of the system's resources. Therefore, moving from one
rem      on-screen button to another (e.g. from Help to Cancel), while the
rem      program is running, is VERY difficult.
rem  
rem  (2) It stops after finding 250 bad sectors. If there are more than this,
rem      it will have to be run more than once (perhaps many times); and
rem      every time it can take up to half an hour to reach the damaged area
rem      on the hard disk, if it's a large disk.
rem  
rem  (3) It automatically proceeds (having found bad sectors) to identify
rem      which file they belong to. If there are more than 250 bad sectors
rem      from a single file, this wastes much time; but there's no option
rem      to make it ASK before proceeding to identify the affected file.


rem  SCANDISK.EXE
rem  ============
rem  
rem  Run the DOS utility ScanDisk, with Surface Scan option enabled,
rem  to fix the disk faults.
rem  
rem  This is a last resort. It makes changes to the disk surface,
rem  by re-mapping or marking "bad" the bad sectors, which reduce
rem  the chance of recovering lost data from the disk!
rem  
rem  NB: Do not do this until AFTER recovering all recoverable data
rem      using other tools!
rem  
rem  *** Display ScanDisk's options ***
:: SCANDISK /?
rem  
rem  *** Run ScanDisk with Surface scan ***
:: SCANDISK /SURFACE
rem  
rem  
rem  NB: ScanDisk will default to the settings in SCANDISK.INI
rem      (if present), unless other options are explicitly set!
rem      (The INI file is at C:\WINDOWS\COMMAND\SCANDISK.INI)



rem                    HARDWARE INFORMATION DATABASE
rem                    =============================

rem  The files DRVIDX.BIN and DRVDATA.BIN in C:\WINDOWS\INF contain
rem  the Driver Information Database.
rem  
rem  At system startup, each hardware device attached to the computer
rem  reports a hardware ID to Windows, which checks to see whether
rem  that ID is recorded in those two files. If it is not, Windows
rem  rebuilds those two files. It also records the ID details in the
rem  Windows Registry, but it is those two files which contain the
rem  pointers to the location (on the hard disk) of the driver files
rem  used by each hardware device.
rem  
rem  Those two files can contain incorrect information. For example,
rem  when the software for a device is upgraded, if the new driver
rem  files are installed to a different location, or have different
rem  names to the older ones, the two files will continue to point
rem  to the old drivers. This can be cured by deleting the two files,
rem  to force Windows to rebuild them on the next bootup.
rem  
rem  *** Examine Hardware Information Database for changes ***
rem      Check whether the file dates have changed recently!
:: DIR /-W C:\WINDOWS\INF\DRVIDX.BIN
:: DIR /-W C:\WINDOWS\INF\DRVDATA.BIN
rem  
rem  *** Make backup of Hardware Information Database ***
:: REN C:\WINDOWS\INF\DRVIDX.BIN DRVIDX.BI_
:: REN C:\WINDOWS\INF\DRVDATA.BIN DRVDATA.BI_
rem  
rem  *** Rebuild the Hardware Information Database ***
:: DEL C:\WINDOWS\INF\DRVIDX.BIN
:: DEL C:\WINDOWS\INF\DRVDATA.BIN
:: REBOOT COLD


::  /--------------------------------------------------------------------/  ::


rem                      INSTALLING A HARD DISK
rem                      ======================


rem  Where the disk has hardware faults it is essential to replace it,
rem  which means installing a new hard disk.
rem  
rem  For data recovery, install an undamaged hard disk on the IDE cables
rem  to store recovered data on (e.g. to clone a damaged disk). This may
rem  involve buying, and setting up, a new hard disk for that purpose.
rem  
rem  Note: Whenever you open the computer's case, take the appropriate
rem        anti-static precautions to avoid harming the electronics.
rem        See: http://www.annoyances.org/exec/forum/winme/1177076589


rem  CONNECTING THE HARD DISK
rem  ========================
rem  
rem  You must *disconnect* all the hard disks except the new one, so
rem  that you don't accidentally partition or format the WRONG disk:
rem  doing so would DESTROY all your files on the disk in question!
rem  
rem  NB: Disconnecting all the hard disks except the new one ensures
rem      that the new disk will be identified as Drive C.
rem  
rem      If you create more than one partition, with all other disks
rem      disconnected, the second partition will be Drive D (and any
rem      further partitions will be Drive E, Drive F, Drive G, etc).
rem  
rem  
rem  An IDE (or E-IDE) hard disk has two cables attached to it:
rem  
rem    - A 40-pin data cable, or ribbon cable, called the IDE cable.
rem  
rem    - A 4-pin power cable.
rem  
rem  The new disk MUST be attached to the primary IDE cable (the one
rem  plugged into the primary IDE connector, which typically has the
rem  words "PRIMARY IDE" printed beside it on the motherboard).
rem  
rem  The secondary IDE cable will typically be connected to a CD
rem  or DVD drive. It is NOT necessary to disconnect this.
rem  
rem  The new disk MUST be attached to the IDE cable as Master. The
rem  Master connector on the cable is coloured black, and is at
rem  the END of the cable: plug this connector into the new disk.
rem  
rem  There is usually a Slave connector on the IDE cable too: the
rem  Slave is coloured grey, and is in the middle of the cable.
rem  Do NOT attach any disk to it while setting up the new disk.
rem  
rem  A power connector must also be plugged into the new disk. This
rem  is typically a 4-pin connector (called a Molex connector), and
rem  is attached at its other end to the Power Supply Unit (PSU).
rem  
rem  
rem  Hardware Jumpers -
rem  
rem  An IDE hard disk also has a jumper "block", typically comprising
rem  5 paired sets of two pins each. A tiny connector (or jumper) is
rem  used to connect two of these pins together, depending whether the
rem  disk is functioning as a single disk, as a master, or as a slave.
rem  
rem  The hard disk will have a printed label attached to it, setting
rem  out diagrams that show which two pins to attach the connector to
rem  for each setting.
rem  
rem  While setting up the disk, with no other IDE hard disks attached,
rem  the new disk will function as a SINGLE (sometimes this setting is
rem  called SINGLE OR MASTER). Quite often, this setting conveniently
rem  happens to be the one setting in which the connector is not used!


rem  PARTITIONING AND FORMATTING
rem  ===========================
rem  
rem  The following procedure will (a) partition and (b) format a
rem  hard disk. This will DESTROY all data on the disk, so is *only*
rem  suitable for initially setting-up a new (blank) disk.
rem  
rem  NB: You must NOT create any partition larger than 127.53 GB
rem      as Windows 95/98/ME will malfunction on such a partition.
rem  
rem  NB: You MUST disconnect all the hard disks except the new one, so
rem      that you don't accidentally partition or format the WRONG disk!
rem      Doing so will DESTROY all your files on the disk in question.
rem  
rem  The hard disk manufacturer will typically provide a setup program
rem  to use *instead* of DOS tools FDISK.EXE & FORMAT.COM [Steps 1 & 2
rem  below], and which includes a disk cloning utility [Step 3 below]:
rem   - Seagate provides "DiscWizard Starter Edition"
rem   - Western Digital provides "Data Lifeguard Tools v11.2 for DOS"
rem  
rem  If you CANNOT use such a setup program, proceed as follows.
rem  
rem  
rem  STEP 1:  Partition the hard disk
rem  
rem  To use a hard disk, it must first be partitioned. This is done
rem  by the DOS program FDISK.EXE (the Fixed Disk partitioning tool).
rem  
rem  For a hard disk to be accessible in Windows ME, which uses the
rem  FAT32 file system, the partitioning MUST be done using a FAT32
rem  version of FDISK (i.e. the version that comes with Windows ME).
rem  
rem  
rem  Firstly, create a bootable Windows ME floppy disk:
rem  
rem  1. Go to: START > SETTINGS > CONTROL PANEL > ADD/REMOVE PROGRAMS
rem  
rem  2. Select the STARTUP DISK tab, put a blank 3.5 inch floppy disk
rem     in Drive A, then follow the on-screen instructions.
rem  
rem  NB: This is also known as a "Windows ME Emergency Boot Disk".
rem  
rem  NB: If you intend to use the hard disk with Windows 98, or
rem      with Windows 98 Second Edition, you MUST use a bootable
rem      floppy disk from *that* version of Windows instead.
rem  
rem  
rem  To run the FDISK program, insert the bootable floppy disk into
rem  Drive A, then start the computer. (If necessary, enter the BIOS
rem  screen to set the boot-up sequence to boot first from Drive A.)
rem  
rem  At the DOS prompt, type FDISK then press the ENTER key. This
rem  will start the FDISK program.
rem  
rem  
rem  To create a single partition occupying the entire disk:
rem  
rem  At the first screen, answer YES when asked if you wish to enable
rem  large disk support; you MUST answer [Y] on that screen, in order
rem  for FDISK to create a FAT32 partition structure.
rem  
rem  At the next screen, select: "Create DOS Partition or Logical DOS
rem  Drive".
rem  
rem  At the next screen, select: "Create Primary DOS Partition".
rem  
rem  At the next screen, FDISK asks how large you want the partition
rem  to be. If you do not enter a number, it will make the partition
rem  as large as it can; so to make the partition fill the entire disk,
rem  just press ENTER to continue.
rem  
rem  NB: As well as creating the partition, FDISK will make it Active
rem      (i.e. bootable).
rem  
rem  The partitioning process will take a few minutes, but you'll see a
rem  visual display of progress on screen.
rem  
rem  And that's all you need to do to create a single partition that uses
rem  all the space on the hard disk; so once the partitioning process has
rem  finished successfully, press ESC to exit FDISK.
rem  
rem  
rem  The Rules of FDISK -
rem  
rem  The first physical disk must be the boot disk. And that disk
rem  must contain a Primary DOS partition, which must be the first
rem  partition on the disk (apart from the "Non-DOS partition").
rem  
rem  A disk must have only one Primary DOS partition (i.e. type 0C).
rem  That partition *must* be set as "active", if it is to be capable
rem  of booting (i.e. starting) the computer; but only a partition on
rem  the first physical disk is allowed to be active (i.e. set to 80).
rem  
rem  NB: In practice, FDISK will therefore not permit a disk to be
rem      set "active" (bootable) unless it is the IDE primary master
rem  
rem  In addition to one Primary partition, a disk may also have one
rem  Extended partition (i.e. type 0F).
rem  
rem  The Extended partition can comprise a single partition, or can
rem  be divided into several partitions. In either case, a partition
rem  which is contained *within* an Extended partition is called a
rem  Logical partition (i.e. type 0B).
rem  
rem  Only the FIRST physical disk must have a Primary DOS partition.
rem  Second or subsequent IDE disks can have *either* a Primary DOS
rem  partition *or* an Extended partition, i.e. as the first partition.
rem  
rem  DOS (and Windows) assign drive letters in the following order,
rem  beginning with the IDE disks, starting with drive letter C -
rem  
rem   - First, all Primary partitions (each disk has at most one)
rem   - Second, all Logical partitions (each disk can have many).
rem  
rem  NB: Thus *all* Primary DOS partitions will be assigned a drive
rem      letter before *any* Logical partitions!
rem  
rem  NB: Drive letters A and B are reserved for floppy drives.
rem  
rem  The IDE disks are treated in the following order -
rem  
rem   - IDE disk 0 (IDE Primary Master)
rem   - IDE disk 1 (IDE Primary Slave)
rem   - IDE disk 2 (IDE Secondary Master)
rem   - IDE disk 3 (IDE Secondary Slave)
rem  
rem  If there are any non-IDE hard disks present (e.g. SATA disks
rem  or external USB disks), they are assigned drive letters AFTER
rem  letters have been allocated to ALL the partitions on all the
rem  IDE disks; and typically in this order -
rem  
rem   - Disk(s) attached to PCI slot 1
rem   - Disk(s) attached to PCI slot 2
rem   - Disk(s) attached to PCI slot 3
rem  
rem  
rem  Settings -
rem  
rem  Settings used to partition Western Digital WD800JB 80GB HDD
rem  using Microsoft's FDISK.EXE (1 Mbyte = 1,048,576 bytes):
rem  
rem        Mbytes available on disk:  76,317 Mbytes [80GB]
rem  
rem        Values entered in FDISK:
rem          - Primary DOS Partition: 10,000 Mbytes
rem          - Extended Partition:    66,315 Mbytes
rem          - 1st Logical Partition: 100%
rem  
rem  Note:
rem  An alternative to Microsoft's FDISK is Ranish Partition Manager
rem  v2.40 (PART.EXE) (a 32bit version for a Hard Disk exceeding 8GB).
rem  
rem  
rem  Check the Outcome -
rem  
rem  After you have partitioned the disk, but BEFORE you format it:
rem  
rem  1. Run the FDISK /STATUS command, to check the result of the
rem     partitioning; and
rem  
rem  2. Run the FDISK program (type FDISK) to check that the Primary
rem     partition is marked as "Active" (the letter A is displayed
rem     against the active partition), if the disk is to be bootable.
rem  
rem     NB: You can't install an Operating System on the disk unless
rem         that partition is first set as "active" (i.e. bootable).
rem  
rem  
rem  Note -
rem  
rem  For background information on partitioning a hard disk as
rem  FAT16 or FAT32 see: http://www.mdgx.com/secrets.htm#FDPT
rem  (NB: Includes many partitioning tools for DOS and Win9x)
rem  
rem  
rem  STEP 2:  Format the hard disk
rem  
rem  Use the FORMAT.COM program (which is included on the bootable
rem  floppy disk) to format the partition you just created.
rem  
rem  With the computer booted to DOS: tio format the new partition,
rem  Drive C, at the A: prompt type this -
rem  
rem  FORMAT C:
rem  
rem  The formatting process takes a few minutes, but you see a visual
rem  display of progress on screen.
rem  
rem  Until the FORMAT command has executed, and completed, the C: drive
rem  does not exist. Any attempt to change directory to C: will fail, and
rem  the command DIR C: will also fail, since no drive exists until after
rem  the formatting process has created it.
rem  
rem  Sometimes it is necessary to type the format command as -
rem  
rem  FORMAT C: /S
rem  
rem  instead of FORMAT C: so try this alternative if the other doesn't work.
rem  This transfers System files, to make the disk bootable. (NB: This means
rem  you are almost certainly using the WRONG type of bootable floppy disk!)
rem  
rem  The hard disk is now partitioned as a single FAT32 partition, and is
rem  formatted as drive C:, so it is now possible to install Windows on it.
rem  
rem  Note: If the disk can't be successfully formated, the PC might have
rem        a faulty motherboard (since the disk controller chip on some
rem        boards supplements the on-disk electronics).
rem  
rem  
rem  Options -
rem  
rem  FORMAT /c : Causes FORMAT to retest bad Clusters; otherwise FORMAT
rem              will mark the Clusters as bad but will NOT retest them.
rem  
rem  FORMAT /s : Prepares a partition to make it active (bootable), by
rem              transfering System files.
rem  
rem  FORMAT /u : Does a unconditional format, which DESTROYS every byte
rem              of data on the disk by overwriting it. (Afterwards do
rem              the SYS C: command to install system files, then do a
rem              thorough SCANDISK check to fix any disk errors.)
rem  
rem  WARNING: You CANNOT unformat a disk formatted using the /U option!
rem  
rem  WARNING: The use of FORMAT /S /U makes the disk UNREADABLE.
rem           Do NOT use these two switches TOGETHER on ANY drive!
rem  
rem  
rem  STEP 3:  Install Windows 98/ME
rem  
rem  Use a cloning program (e.g. Seagate's DiscWizard Starter Edition,
rem  Western Digital's Data Lifeguard Tools for DOS, or Norton's GHOST)
rem  to make a byte-by-byte copy on the new disk of a bootable partition
rem  on another hard disk attached to the IDE cables.
rem  
rem  NB: Norton's Ghost cannot clone its "source" partition, i.e. the
rem      partition on which it's installed or from which it's running!
rem      [Run it in DOS, instead of Windows, to avoid this limitation]
rem  
rem  NB: The copying process involved in cloning a hard disk typically
rem      takes up to 20 minutes per MegaByte (i.e. 3 hours for a 10GB
rem      disk) if cloning from IDE Primary Master to IDE Primary Slave
rem  
rem      The process is much faster if cloning from IDE to a SATA disk
rem      [The fastest program, HDClone, takes only 5 minutes for 10GB]
rem  
rem  NB: Windows ME creates a backup copy of the partition information
rem      in the file C:\Suhdlog.dat (a hidden file) at the end of a
rem      successful installation. Therefore, after cloning a disk NEVER
rem      try to uninstall Windows ME from the clone! That will write the
rem      partition information in Suhdlog.dat into the clone's MBR sector
rem      - which will destroy the disk, because it is NOT the disk onto
rem      which WinME was originally installed, therefore its partition
rem      information is different from that contained in Suhdlog.dat!
rem  
rem  
rem  Alternatively, insert a Windows installation CD in the CD-ROM drive,
rem  and install Windows 9x from that CD.
rem  
rem  In this latter case, you also need a valid Microsoft serial number
rem  (called a "Product Key"). Here are two which are valid for WinME -
rem  
rem    RBDC9 - VTRC8 - D7972 - J97JY - PRVMG  (Source: Internet)
rem    RMG6R - W6HXH - P6FQM - 2WJHK - 32RBB  (Source: Tiny PC at MH)
rem  
rem  Here are some which are valid for Win98SE (Source: Internet) -
rem  
rem    T7FCQ-XTD3Q-YY6QD-TGYJQ-7BPJJ  (UK version)
rem    P767C-WKHX7-62TFV-H6XTP-JXFQM  (Version 4.10.2222, English)
rem    W7XTC-2YWFB-K6BPT-GMHMV-B6FDY  (Second Edition, English)
rem    K4HVD-Q9TJ9-6CRX9-C9G68-RQ2D3  (Second Edition, Upgrade version;
rem                                    also works for 1st Edition, Full)
rem  
rem  NB: A Google search will find a serial number on the internet,
rem      but there should be one printed on the CD's documents.
rem  
rem  NB: Type the serial number! Do NOT copy-and-paste it, or the setup
rem      program will reject it (a crude anti-piracy ploy).
rem  
rem  Windows 98/ME also requires a "Product ID". This is NOT the same
rem  thing as the "Product Key"! Here is a valid one:
rem  
rem    52782 - OEM - 0009147 - 00032          (Source: Tiny PC at MH)
rem  
rem  The installation CD can be either a *full* install of Win 98/ME,
rem  or an *upgrade* version. An upgrade version won't work, if there
rem  is no existing operating system on the hard disk, unless you
rem  insert a setup CD or floppy for an earlier version of Windows 9x
rem  when the upgrade version asks for that.
rem  
rem  
rem  The one other thing that FDISK can do is show you the current
rem  partition information (i.e. the current state of the hard disk) -
rem  
::     FDISK /STATUS
rem  
rem  
rem  For a more visual explanation of the FDISK program screens, 
rem  look at this site -
rem  
rem    http://fdisk.radified.com
rem  
rem  It explains in detail how to use the various FDISK options.
rem  
rem  
rem  PRELIMINARY STEP:  Zero-filling the hard disk
rem  
rem  Before re-using a hard disk which was NOT previously blank, it is
rem  prudent to delete all information from that disk, otherwise rogue
rem  data on the disk may cause errors. The zero-filling process
rem  eliminates any problem data, allowing normal partitioning to occur.
rem  
rem    NB: Only an entire Disk can be zero-filled, not a Partition
rem  
rem    NB: To save time, the Seagate program (below) has an option
rem        to write zeros to only the first and last million bytes
rem  
rem  First, use FDISK to delete the partition information. Run FDISK;
rem  at stage 2 it offers the option to delete the existing partitions.
rem  
rem  After doing so, use the command FDISK /STATUS to check that all the
rem  partition information has been *successfully* deleted.
rem  
rem  Next, use the command FDISK /MBR to wipe the master boot record clean
rem  (or at least the part of sector CHS 0-0-1 which it does wipe clean).
rem  
rem  Next, do a 'zero fill' of the disk: this process writes zeros to
rem  every byte on the disk. You can get the program from the website of
rem  the disk's manufacturer. For a Seagate disk, go to their website; etc.
rem  
rem  It usually isn't a seperate program. Manufacturers typically offer
rem  a disk management program with many functions, only one of which is
rem  writing zeros to the drive, so just download whatever they offer by
rem  way of disk tools: the zeroing option should be in there somewhere.
rem  You will need one 3.5 inch floppy disk for this step.
rem  
rem  NB: Seagate's DiscWizard Starter Edition includes this function,
rem      in the "Utilities" section of the program. (That program is
rem      NOT limited to Seagate disks! It works with Western Digital
rem      disks, and thus may work on other manufacturers' disks too!)
rem  
rem  If the program does not offer a zero-filling option explicitly, use
rem  any tool that offers to blank, or fill, or low-level format the disk.
rem  
rem  NB: It is in fact impossible to low level format a modern disk,
rem      but most manufacturers offer tools that do something similar,
rem      to which they like to give that description.
rem  
rem  Once the zero-filling is complete (which can take several hours for
rem  a large capacity disk), partition and format the disk (as above).


::  /--------------------------------------------------------------------/  ::


rem                           CLONING A HARD DISK
rem                           ===================


rem  CLONING A DISK
rem  ==============
rem  
rem  Cloning is a copying routine that creates a byte-by-byte copy of the
rem  source disk or source partition.
rem  
rem  The copy is identical to the original in every way.
rem  
rem  NB: Whenever you open the computer's case, take the appropriate
rem      anti-static precautions to avoid harming the electronics.
rem      See: http://www.annoyances.org/exec/forum/winme/1177076589


rem  DATA LIFEGUARD
rem  ==============
rem  
rem  Management program: Data Lifeguard Tools for DOS, v11.2
rem  
rem  This program provides functions which *replace* FDISK.EXE and
rem  FORMAT.COM and GHOST.EXE (above), for Western Digital disks.
rem  
rem  The program creates a bootable Rescue Disk on a 3.5 inch floppy
rem  disk in Drive A. [The program requires one 3.5 inch floppy disk]
rem  
rem  Create the Rescue Disk, then use it to start the computer.
rem  The Data Lifeguard program will run automatically at startup;
rem  its menus include an option to copy (i.e. clone) a hard disk,
rem  the option "DRIVE-TO-DRIVE COPY".
rem  
rem  *** Create bootable Data Lifeguard rescue disk ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\CLONING\DATALI~1
:: F:\SAVED\RECOVERY\CLONING\DATALI~1\DLGSET~1.EXE
rem  
rem  Warning: The Rescue Disk can be created in a Windows session,
rem           but must boot the system to DOS to create a clone.
rem           Do NOT try to create a clone with Windows running!
rem  
rem  
rem  Program options -
rem  
rem  1. VIEW INSTALLATION TUTORIAL
rem     Instructions on how to connect your new hard disk to the computer
rem  
rem  2. SETUP YOUR HARD DRIVE
rem     Setup a hard disk already connected to your computer
rem     [NB: This is an alternative to using FDISK.EXE and FORMAT.COM]
rem  
rem  3. DRIVE-TO-DRIVE COPY
rem     Copy a partition from one disk to another
rem     [NB: A cloning utility, making a byte-by-byte copy]
rem     [NB: This is an alternative to using GHOST.EXE or HDCLONE.EXE etc]
rem  
rem  4. HARD DRIVE INFORMATION
rem     Jumper Settings and other technical information about your hard disk
rem  
rem  
rem  Note:
rem  
rem  The drawback with Data Lifeguard Tools (both the DOS and Windows version)
rem  is that you must fully partition a disk in a single session, because it
rem  DELETES all existing partitions (thereby destroying all data on them) if
rem  instructed to partition any un-partitioned space.


rem  DISK WIZARD STARTER EDITION
rem  ===========================
rem  
rem  Disk Wizard Starter Edition (DWSE) (English version).
rem  
rem  DiscWizard is a Seagate program, for setting up a new Seagate
rem  IDE disk; but the cloning utility (called 'Copy a Partition')
rem  works with ANY make of disk: it is designed to copy whatever
rem  existing IDE disk the user has, onto his new Seagate disk, as
rem  a byte-by-byte copy (in order that the copy will be bootable
rem  if the original is, by preserving all settings).
rem  
rem  The program creates a bootable Rescue Disk on one 3.5 inch
rem  floppy disk in Drive A.
rem  
rem  Create the Rescue Disk, then use it to start the computer. The
rem  DiskWizard program will run automatically at startup; its
rem  menus include an option to copy (i.e. clone) a hard disk.
rem  
rem  *** Create DiscWizard Starter Edition v10.32 ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\CLONING\DWSE\v10_32
:: F:\SAVED\RECOVERY\CLONING\DWSE\v10_32\DWSE_EN.EXE
rem  
rem  *** Create DiskWizard Starter Edition v10.45 ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\CLONING\DWSE\v10_45
:: F:\SAVED\RECOVERY\CLONING\DWSE\v10_45\DWSE_EN.EXE
rem  
rem  Warning: The Rescue Disk can be created in a Windows session,
rem           but must boot the system to DOS to create a clone.
rem           Do NOT try to create a Clone with Windows running!


rem  NORTON GHOST
rem  ============
rem  
rem  Norton's GHOST for DOS v8.3 (GHOST.EXE) can clone an entire disk,
rem  but it only works with IDE disks: not SATA or SCSI or USB.
rem  
rem  NB: Some versions of Norton GHOST, that run under Windows, *will*
rem      clone non-IDE disks. It's only GHOST for DOS that will not.
rem  
rem  NB: To clone a non-IDE disk where Windows is inaccessible, use 
rem      HDClone Professional (see below).
rem  
rem  It can clone a disk to a smaller one, *provided* the used space
rem  (i.e. data) on the source disk does not exceed the capacity of
rem  the destination disk: i.e. if the difference is just free space.
rem  
rem  NB: Norton Ghost 2003 is notorious for creating corrupt image
rem      files, due to faulty compression, although it is safe for
rem      normal (i.e. uncompressed) disk-to-disk direct cloning.
rem      (Norton's Ghost for DOS v8.3 does NOT have this fault!)
rem  
rem  PCOPY mode *must* be used if the new disk is to be bootable.
rem  
rem  
rem  Syntax -
rem  
rem  MODE=COPY
rem  Copies the contents of one disk to another (file-by-file)
rem  
rem  MODE=PCOPY
rem  Clones a partition to another partition (byte-by-byte)
rem  
rem  SRC=Source
rem  Drive number, or Drive number and Partition number
rem  
rem  DST=Destination
rem  Drive number, or Drive number and Partition number
rem  
rem  SRC and DST examples in PCOPY mode:-
rem  1:2 means the 2nd partition on the 1st disk
rem  2:1 means the 1st partition on the 2nd disk
rem  
rem  
rem  Examples -
rem  
rem  1. Copy disk 1 to disk 2:
rem     GHOST.EXE -clone,mode=copy,src=1,dst=2
rem  
rem  2. Copy the 1st partition of disk 1 on
rem     the 1st partition of disk 2:
rem     GHOST.EXE -clone,mode=copy,src=1,dst=2
rem  
rem  3. Clone the 1st partition of disk 1 on
rem     the 1st partition of disk 2:
rem     GHOST.EXE -clone,mode=pcopy,src=1:1,dst=2:1
rem  
rem  4. Clone the 2nd partition of disk 1 on
rem     the 1st partition of disk 2:
rem     GHOST.EXE -clone,mode=pcopy,src=1:2,dst=2:1
rem  
rem  
rem  Options that may be useful for troubleshooting:
rem  
rem  -FRO    : Forces Ghost to continue cloning even if the
rem            source contains bad sectors
rem  
rem  -FX     : Forces Ghost to eXit to DOS after the operation
rem            is complete
rem  
rem  -FFATID : Changes the partition ID of the DESTINATION to the
rem            recommended partition ID for that FAT32 partition
rem            [The partition ID is stored in the partition table]
rem  
rem  -PMBR   : Specifies that the Master Boot Record of the
rem            DESTINATION disk be Preserved when performing
rem            a Disk-to-Disk or Image-to-Disk operation
rem  
rem  
rem  Other command line options are summarised at:
rem  
rem  http://service1.symantec.com/SUPPORT/on-technology.nsf/docid/
rem  1998082612540625
rem  
rem  http://service1.symantec.com/SUPPORT/on-technology.nsf/docid/
rem  1998082413392025
rem  
rem  
rem  *** Display Ghost's help screen ***
:: GHOST /?
:: GHOST -?


rem  UNDISKER.EXE
rem  ============
rem  
rem  Undisker v1.2 can clone an entire IDE Hard Disk.
rem  
rem  This is a Windows program. It cannot be used to clone the
rem  boot drive (because Windows constantly makes random writes
rem  to the boot partition); but it can clone any other partition.
rem  
rem  It can create the clone on any disk attached to the system,
rem  including a USB drive or other external disk on a USB port.
rem  
rem  Its main purpose is to create .ISO image files (compressed or
rem  uncompressed), including disk images, on a recordable CD/DVD.
rem  
rem  *** Run Undisker ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\CLONING\UNDISKER
:: F:\SAVED\RECOVERY\CLONING\UNDISKER\UNDISKER.EXE


rem  MEDIA TOOLS
rem  ===========
rem  
rem  The program Media Tools can also clone an IDE disk.


rem  ACRONIS TRUE IMAGE
rem  ==================
rem  
rem  The program Acronis True Image can also clone an IDE disk.


rem  XCOPY32.EXE
rem  ===========
rem  
rem  An alternative means of copying an existing partition (e.g. Drive C:)
rem  to a new hard disk (e.g. Drive D:) is to use XCOPY32.EXE (a program
rem  which is part of MS-DOS 8 included with Windows ME).
rem  
rem  This does NOT create a true clone of the source partition; but in an
rem  emergency it provides a reliable means of copying all the files on a
rem  partition if no other software is available (e.g. no internet access).
rem  
rem  *** Set Path ***
::   SET PATH=%path%;C:\WINDOWS\COMMAND
rem  
rem  *** Copy all files on Drive C: to Drive D: ***
::   C:
::   CD \
::   XCOPY32 *.* D:\ /S/E/R/C/H/K/Y


rem  OTHER SOFTWARE
rem  ==============
rem  
rem  Details of a number of free Cloning and Imaging programs, for
rem  making and restoring a hard disk backup, are given on-line at
rem  http://www.thefreecountry.com/utilities/backupandimage.shtml
rem  
rem  NB: Some of these are NOT suitable for use with FAT32 disks,
rem      or will NOT run on Windows 98/98SE/ME.


rem  THE "MYSTERY BYTES"
rem  ===================
rem  
rem  NEVER start Windows with both the source disk and clone attached
rem  to the IDE cables. A clone disk must NOT be attached (by the IDE
rem  interface) to the same computer as the disk of which it's a copy,
rem  as that will cause a fault!
rem  
rem  A full explanation of the "mystery bytes" fault, including symptoms,
rem  is set out above, under "OTHER ERROR MESSAGES" ("Invalid system disk").
rem  
rem  The fault can be cured by manually zeroing the six bytes DA to DF
rem  (bytes 219 to 224) in sector CHS 0-0-1 (LBA sector 0) [the MBR sector]
rem  on the CLONE disk, the "mystery bytes"; e.g. using Norton's DiskEdit.
rem  
rem  See: http://thestarman.pcministry.com/asm/mbr/mystery.htm


rem  VOLUME IDENTIFIER
rem  =================
rem  
rem  Windows may change the Volume Identifier on the clone disk to
rem  non-bootable, if the clone is installed as IDE Primary Slave
rem  for the cloning operation. So when it's then installed as the
rem  Primary Master it won't boot!
rem  
rem  To avoid this, when cloning is complete do NOT let the cloning
rem  program "reset" the computer, as booting immediately to Windows
rem  is what causes this fault! Instead, shutdown the computer, then
rem  *remove* the source disk and install the CLONE disk as the IDE
rem  Primary Master, *before* booting to Windows.


rem  CLONING SATA, SCSI OR USB DISK
rem  ==============================
rem  
rem  The only program which can clone a FAT32 disk connected by a
rem  Serial-ATA (SATA), or an SCSI, or a USB connection in Win9x is
rem  HDClone Professional v3.6 (the Professional edition of HDClone v3.6).
rem  
rem  NB: The program can also clone a disk connected on the IDE interface.
rem  
rem  The bootable floppy disk version does not load DOS or Windows. It
rem  starts the computer using its own (proprietory) Operating System.
rem  
rem  NB: The other cloning programs can all clone a Parallel-ATA (PATA)
rem      disk, i.e. an IDE disk, in DOS. But none of them can clone a
rem      disk connected by a Serial-ATA (SATA) or SCSI or USB connection
rem      in DOS, only in Windows (i.e. using a Windows 9x device driver):
rem      which results in a file-by-file copy, not a byte-by-byte clone.
rem  
rem  NB: On a Windows 9x computer (manufactured between c.1998 and 2001),
rem      the motherboard will NOT have either USB 2.0 or Serial-ATA (SATA).
rem      Those facilities can be added, by fitting a USB 2.0 and/or SATA
rem      PCI card in an empty PCI slot on the motherboard.
rem  
rem  HDClone can clone either an entire disk or a partition on the disk.
rem  
rem  
rem  Note:
rem  
rem  Detailed instructions on the use of this program are set out below
rem  (at "HARD DISK EXCEEDING 137GB: CLONING"). The procedure described
rem  there will also work for a hard disk smaller than 137GB.
rem  
rem  
rem  Warnings:
rem  
rem  1. HDClone can *only* be run safely after a COLD boot. It is
rem     NOT safe to run the program after a warm reboot; i.e. HDClone
rem     must NOT be run using the start option "Restart" or "Stand by".
rem     The computer *must* be started from a switched-off state!
rem  
rem  2. After cloning, the computer will malfunction if both the source
rem     and the clone partition have the same Volume Serial Number in
rem     their respective Boot Sectors. So it's ESSENTIAL to select the
rem     HDClone option "Patch Boot Code", to force the program to give
rem     the clone a *different* serial number (if both clone and source
rem     will ever be conected to the same computer at the same time).
rem  
rem     NB: The fault will occur however the partitions are attached,
rem         i.e. even if one is on a disk connected to the IDE cables
rem         and the other is on a disk attached to a PCI card (e.g. as
rem         a USB or SATA device), because it's caused simply by more
rem         than one partition having (in effect) the same address.
rem  
rem     NB: The fault can be cured by editing either partition manually,
rem         e.g. using DE.EXE v1.04 (the PTS disk editor). Bytes 68 to 71
rem         (4 bytes) in the partition's Boot Sector must be altered: the
rem         new number (a hexadecimal number) can be ANY number, provided
rem         it is *not* the same as the Volume Serial Number of any other
rem         partition (i.e. "drive") attached to the computer.
rem  
rem         You can enter a new hexadecimal number there yourself. But the
rem         safest action is to change each of those bytes to zero; Windows
rem         will then allocate a new number to that partition on the next
rem         reboot, automatically (thus avoiding any possible problem).
rem  
rem         The PTS disk editor can function even on a hard disk exceeding
rem         137GB. I've used it successfully on a 500GB disk, while booted
rem         to Windows (running Windows ME); so it is certainly capable of
rem         correctly accessing any hard disk of up to 512GB.
rem  
rem         For a detailed analysis of the contents of the Boot Sector
rem         on a FAT32 partition, see "Disk Structures" (above).


::  /--------------------------------------------------------------------/  ::


                           HARD DISK EXCEEDING 137GB
                           =========================


rem     Whenever you open the computer's case, take the appropriate
rem      anti-static precautions to avoid harming the electronics.
rem       [http://www.annoyances.org/exec/forum/winme/1177076589]


rem  INSTALLING A HARD DISK EXCEEDING 137GB
rem  ======================================
rem  
rem  How to install a Serial-ATA (SATA) hard disk larger than 137GB,
rem  for use as additional storage in Windows 9x (e.g. as Drive D):-
rem  
rem  
rem  Step 1: Buy a SATA Hard Disk
rem  
rem  A SATA disk not exceeding 512GB can be used as additional storeage
rem  on a Windows 9x system (e.g. a 500GB WD Caviar Blue WD5000AAKS).
rem  
rem  NB: It cannot be installed as Drive C (the bootable drive), because
rem      a pre-2001 Windows 9x motherboard *cannot* boot from a SATA disk.
rem  
rem  NB: A SATA disk is the safest choice on a Windows 9x system, because
rem      a Win9x motherboard normally has no SATA ports! Thus there is no
rem      possibility that the disk could ever be accidentally connected to
rem      the motherboard (which doesn't support disks exceeding 137GB).
rem  
rem  
rem  Step 2: Buy a PCI Card
rem  
rem  Purchase a PCI card that has a 48-bit LBA controller, which provides
rem  essential support for a hard disk larger than 137GB (for example a
rem  StarTech PCI SATA Controller Card, ASIN B001ZC561U, with its 48-bit
rem  VIA VT6421 chip).
rem  
rem  NB: The StarTech PCI SATA Controller Card is compatible with an older
rem      (e.g. 1998) model PC, as it uses PCI 2.2 and provides driver files
rem      for Windows 9x; and it provides scope for future expansion, for it
rem      includes an e-SATA port (which will accept external SATA devices).
rem  
rem  A CD containing the essential Windows 98 driver files will typically be
rem  included with the PCI card. This software is needed for the motherboard
rem  to recognise the new device (i.e. the 48-bit LBA chip on the PCI Card).
rem  
rem  NB: The CD included with the StarTech ASIN B001ZC561U PCI Card contains,
rem      in a subdirectory, the driver files VIAMRAID.mpd and VIAMVSD.VXD
rem      (which install in C:\WINDOWS\SYSTEM\IOSUBSYS) and VIAMRAID.INF
rem      (which installs in C:\WINDOWS\INF\OTHER).
rem  
rem  If the PCI card is SATA-I, but the disk is SATA-II, set the disk to run
rem  at SATA-I speed: by using a mini jumper pin to force the disk to emulate
rem  a SATA-I disk. On a WD5000AAKS disk, jumper pins 5 and 6 using a 2.54mm
rem  mini jumper pin (e.g. Psylins Computer CMP-SCREWKIT10, ASIN B000JGG8ZQ).
rem  
rem  
rem  Step 3: Buy a Drive Caddy (or Adapter Brackets) [Optional]
rem  
rem  Purchase a Serial-ATA (SATA) Drive Drawer (e.g. StarTech caddy DRW110SAT
rem  ASIN B0000E2Y7T), to fit into an empty 5.25 inch drive bay. It holds the
rem  SATA hard disk, and connects to the PCI card's internal SATA port.
rem  
rem  NB: For maximum flexibility, the StarTech DRW110SAT caddy accepts both
rem      SATA-I and SATA-II hard disks.
rem  
rem  NB: The StarTech ASIN B001ZC561U PCI card comes with a SATA data cable,
rem      for connecting the PCI card to the caddy, so it is not necessary to
rem      buy a SATA data cable separately.
rem  
rem  
rem  Step 4: Installation Procedure
rem  
rem  With the mains power switched OFF, plug the PCI card into a PCI socket,
rem  but do NOT install the caddy or the hard disk. On startup, the computer
rem  will detect the PCI card and ask for the driver CD. Insert it, then
rem  navigate to the location of the Windows 9x drivers.
rem  
rem  NB: For the StarTech ASIN B001ZC561U PCI card -
rem  
rem      (a) If your CD drive is Drive D, the driver files will be at:
rem  
rem            D:\Windows\VIAStor\driver\Raid\win9x
rem  
rem      (b) It is NOT necessary to run the included RAID program
rem          if your computer will only have a single SATA disk.
rem          (NB: The RAID functions manage multiple SATA disks)
rem  
rem      (c) In Windows 9x, it is NOT necessary to run the SETUP.EXE
rem          program in the CD's root directory.
rem  
rem  Then continue with a normal startup. Once the desktop appears, check
rem  in Device Manager (Start > Settings > Control Panel > System), under
rem  "SCSI controllers", for the entry "VIA VT6421 RAID Controller".
rem  
rem  Then shutdown the computer normally. With the mains power turned OFF,
rem  install the drive caddy (containing the hard disk): connect the caddy
rem  to a 4-pin Molex power connector, and to a (red) SATA data cable;
rem  then connect that red cable to the PCI card's internal SATA port.
rem  
rem  NB: If you are not installing a caddy, connect the Molex conector and
rem      the data cable directly to the hard disk.
rem  
rem  NB: The hard disk(s) attached to the IDE interface must NOT be jumpered
rem      to use "cable select", because that can cause a fault on bootup
rem      when using IDE disks and SATA disks in the same computer.
rem  
rem      Set the hardware jumper pin on the IDE boot disk (e.g. Drive C)
rem      to SINGLE or MASTER (as appropriate to the printed instructions on
rem      the hard disk's label) if only one IDE disk is attached. Otherwise,
rem      set the IDE boot disk to MASTER and the other IDE disk to SLAVE,
rem      and connect both to the Primary IDE cable; the MASTER *must* be
rem      attached to the end of the cable, and the SLAVE to the middle.
rem  
rem      A faulty IDE cable (40-pin ribbon connector) can cause the same
rem      fault on bootup, even if the hardware jumper pin is correctly set.
rem  
rem  Then start the computer normally. The hard disk is not yet partitioned,
rem  or formatted, so Windows cannot yet "see" it. The next step therefore 
rem  is to partition and format the new hard disk.
rem  
rem  NB: You cannot use the DOS tools FDISK.EXE or FORMAT.COM for this step,
rem      because when a computer is booted to DOS there is no means for it
rem      to access a SATA disk, since no DOS drivers for SATA exist.
rem  
rem  NB: If you bought a Western Digital hard disk, their website provides a
rem      downloadable program called "Data Lifeguard Tools for Windows". Use
rem      it to partition and format the new disk in Windows; create *several*
rem      120GB partitions, as Windows 9x CANNOT use one larger than 127.53GB.
rem  
rem  NB: "Data Lifeguard Tools for Windows" can also copy files from an
rem      existing disk to the new disk (e.g. copy the entire Drive C to
rem      the new disk). Alternatively, you can use XCOPY32.EXE (above).


rem  HARD DISK EXCEEDING 137GB: PARTITIONING
rem  =======================================
rem  
rem  The following is a more flexible, though also more complicated, method
rem  for partitioning a hard disk larger than 137GB.
rem  
rem  
rem  PARTITION MAGIC v8.05 -
rem  
rem  Open Partition Magic v8.05 in Windows.
rem  
rem  The program has an option to set existing disks (containing your data)
rem  as READ ONLY. This is an ESSENTIAL precaution, to avoid accidentally
rem  destroying one of your existing partitions! To do this, go to:
rem  
rem    General - Preferences
rem  
rem  Then create a Partition (*smaller* than 127.53GB) on the new hard disk.
rem  
rem  The program allows you to specify the exact size of the partition
rem  to be created. It also allows you to either partition all the space
rem  on the new disk immediately, or to leave some space unpartitioned
rem  (i.e. to be partitioned in a later session); this is more flexible
rem  than the options in "Data Lifeguard Tools for Windows".
rem  
rem  NB: If the new hard disk is marked as "Removeable" (in Device Manager)
rem      Partition Magic *won't* recognise it!
rem  
rem  NB: To re-use a SATA disk that has held data previously, it is prudent
rem      to remove all traces of the old (unwanted) data by writing zeros
rem      to the SATA disk before beginning any partitioning, e.g. with
rem      Western Digital's program "Data Lifeguard Diagnostics for Windows".
rem  
rem  
rem  Set Drive letter (using Device Manager), in Windows:
rem  
rem  NB: Do so ONLY when *all* partitions have been created (because
rem      if a hard disk is marked as "Removeable", in Device Manager,
rem      Partition Magic v8.05 *won't* recognise it!)
rem  
rem  NB: Set up all removable media drives (i.e. all partitions on the
rem      SATA disk) so that they're the *last* drives on the system!
rem      [This is the purpose of reserving specific drive letters for
rem       the partitions on the SATA disk: in this way the permanent
rem       disks (i.e. the IDE disks) will remain as drive C:, D: & E:
rem       even when the SATA disk is connected to the computer.]


rem  HARD DISK EXCEEDING 137GB: CLONING
rem  ==================================
rem  
rem  The following is a more flexible, though also more complicated, method
rem  for cloning (i.e. copying) an existing partition onto a new hard disk
rem  larger than 137GB.
rem  
rem  
rem  HDCLONE PROFESSIONAL v3.6 -
rem  
rem  The setup program creates a working copy of HDClone Professional v3.6
rem  on a blank floppy disk in Drive A.
rem  
rem  
rem  Using HDClone Professional v3.6 in practice -
rem  
rem  Step 1:
rem  
rem  Insert the bootable floppy disk containing HDClone into Drive A,
rem  then start/restart the computer.
rem  
rem  NB: The computer must be set, in the BIOS, to boot from Drive A
rem      (the floppy drive) before Drive C. To enter the BIOS, press
rem      the appropriate key (e.g. DEL) (or, on some systems, F1 or F2)
rem      repeatedly at startup.
rem  
rem  NB: You must create the partition structure on the new disk *before*
rem      running HDClone, as it has no ability to create partitions.
rem  
rem  
rem  Step 2:
rem  
rem  In the opening screen, select the copy method: Partition to Partition
rem  
rem  To do so, use the mouse: select "Partition" as the source, and then
rem  "Partition" as the target.
rem  
rem  NB: The hard disk is not copied in its entirety. Only the contents of
rem      one individual partition is copied.
rem  
rem      This copy is executed sector by sector, therefore (relative to the
rem      beginning of each partition) the individual sectors are moved to
rem      the same address. However, in contrast to the drive-to-drive mode,
rem      the individual sectors are not at the same absolute address in
rem      relation to the complete (target) hard disk.
rem      
rem      Such a copy is therefore not directly usable, but only after it has
rem      been copied back, or been adapted to the changed absolute position
rem      on the hard disk (as to which see "Adjust Target", below).
rem  
rem  
rem  Step 3:
rem  
rem  Select the Source partition (i.e. on an EXISTING disk).
rem  
rem  NB: Copying takes about 3 minutes per 10MB
rem      (20MB = 5 min; 80MB = 25 min)
rem  
rem  
rem  Step 4:
rem  
rem  Select the Target partition (i.e. on the NEW disk).
rem  
rem  
rem  Step 5:
rem  
rem  Select the Options (e.g. verify copy, smart copy).
rem  
rem  NB: To do a byte-by-byte copy, set "Smart copy" to OFF.
rem  
rem  NB: Selecting "Verify" (verifying the copy) will *double*
rem      the time involved, because a 2nd pass is required.
rem  
rem  
rem  Step 6:
rem  
rem  Confirm the selections, and begin the copying process.
rem  
rem  NB: For "Auto Expand" select OFF. (This option will only appear
rem      if the Target partition is *larger* than the Source.)
rem  
rem  
rem  Step 7:
rem  
rem  Adjust the Target disk; i.e. allow HDClone to make certain
rem  adjustments to the target disk (in the final screen).
rem  
rem  HDClone automatically sets parameter values that are optimal.
rem  These usually ONLY need to be confirmed; a manual change of
rem  the preset parameters is needed only in *exceptional* cases.
rem  
rem  NB: This means *accepting* ALL the suggested adjustments! It
rem      is NOT necessary to change any of the proposed settings;
rem      and in practice it's *essential* not to change any of them!
rem  
rem  NB: The following notes assume that the Target disk is a 500GB
rem      SATA disk, used in a pre-2001 Windows 9x computer, with an
rem      older BIOS that cannot boot from a SATA disk. These notes
rem      do NOT apply in any other case.
rem  
rem  
rem  (a) GEOMETRY -
rem  
rem  Geometry used        :  The geometry of the Target (i.e. clone) disk
rem                          *must* be set as LBA (Large Block Addressing).
rem  
rem                          NB: A FAT32 disk larger than 8GB *must* use
rem                              LBA (including a disk larger than 137GB)
rem  
rem  
rem  (b) MBR -
rem  
rem  Adopt partition ID   :  Use the same partition type as on the Source disk.
rem  
rem                          NB: This option is only offered for the Primary DOS
rem                              partition of the Target disk. In other cases it
rem                              is greyed-out.
rem  
rem                          NB: Type 0C (FAT32 LBA) is normal for a Primary DOS
rem                              partition on a FAT32 disk. Do NOT set any other
rem                              partition type for the Primary DOS partition of
rem                              the Target disk. See "DISK STRUCTURE NOTES" above.
rem  
rem  Adjust partition size:  Set the size of the Target partition to the
rem                          *exact* size of the Source partition.
rem  
rem                          NB: This guarantees that the clone (Target)
rem                              partition will be the same size as the Source
rem                              (will have the exact same number of Sectors);
rem                              so it will be as *close* a match as possible
rem                              to the Source partition, in every way.
rem  
rem                          NB: This will cause an option to pop-up,
rem                              offering to resize the Target to match
rem                              the size of the Source, if they differ.
rem  
rem  Adjust CHS layout    :  Use the CHS values set in 'Geometry used' for
rem                          adjusting the MBR & Boot Sector of the Target.
rem  
rem                          NB: This option is normally greyed-out
rem                              (because CHS is not used if the
rem                               Target disk is larger than 8GB)
rem  
rem  Reset disk signature :  Reset the Target disk's unique media signature.
rem  
rem                          This sets bytes DA to DF [Disk Serial Number] in
rem                          the Target's MBR (see "DISK STRUCTURE NOTES" above)
rem                          to a different ID number than the Source disk.
rem  
rem                          NB: This is an ESSENTIAL step! It would be fatal
rem                          to use the unique ID signature of the Source disk
rem                          on the Target disk: they would effectively *both*
rem                          have the same "address", causing the computer to
rem                          crash on startup.
rem  
rem  
rem  (c) BOOT SECTOR -
rem  
rem  Adjust offset        :  Adjusts the partition's start address (in the
rem                          boot sector of the Target partition).
rem  
rem                          NB: This is an ESSENTIAL adjustment! The Target
rem                              partition will NOT be accessible by Windows
rem                              if this adjustment is not made.
rem  
rem  Patch boot code      :  Avoids boot problems on older hardware.
rem  
rem                          NB: What this does is unclear; but there is NO
rem                              possibility of the Target (SATA) disk ever
rem                              being used to boot the system, as a pre-2001
rem                              m/board BIOS *cannot* boot from a SATA disk!
rem  
rem                              So it is safe to allow this: any changes
rem                              made will have NO practical consequences.
rem  
rem  Change Volume ID     :  Create a *new* ID for the Target partition.
rem                          This is ESSENTIAL if the source and target
rem                          partitions are to be used in the same PC!
rem  
rem                          A Volume (partition) serial number is randomly
rem                          generated each time you format the partition.
rem                          (NB: A simple DIR command in DOS displays the
rem                           8 character Volume Serial Number [xxxx-xxxx])
rem  
rem                          This serial number *must* be different on
rem                          every partition present in the computer, as
rem                          Windows uses these ID numbers to identify
rem                          (i.e. differentiate between) the partitions.
rem  
rem                          NB: The hard disk also has a serial number,
rem                              one that is hardcoded to the hardware,
rem                              but this is NOT a reference to that.
rem  
rem                          NB: This is NOT a reference to the Volume label
rem                              (i.e. the 11 character Partition name).


::  //  ::


rem                  ------------------------------------
rem                  SECTION E: RESTORING PRE-CRASH STATE
rem                  ------------------------------------


rem                      CHECKING DISK AFTER A REPAIR
rem                      ============================

rem  After repairing a Hard Disk, it is prudent to check it for Disk Errors
rem  (to establish whether any further errors still need to be fixed)


rem  SCANDISK
rem  ========
rem  
rem  (a) ScanDisk for DOS
rem  
rem  If Windows *cannot* load, use the DOS version of Microsoft's
rem  ScanDisk (a.k.a. ScanDisk for DOS).
rem  
rem  NB: The option /CUSTOM forces the program to use the settings
rem      in the customised file SCANDISK.INI in C:\WINDOWS\COMMAND 
rem  
rem  NB: Do NOT allow SCANDISK to make any changes to the disk!
rem  
rem  *** Set PATH ***
:: SET PATH=%path%;C:\WINDOWS\COMMAND
rem  
rem  *** Run ScanDisk for DOS ***
:: C:\WINDOWS\COMMAND\SCANDISK.EXE C: /CHECKONLY /SURFACE
:: C:\WINDOWS\COMMAND\SCANDISK.EXE D: /CHECKONLY /SURFACE
:: C:\WINDOWS\COMMAND\SCANDISK.EXE E: /CHECKONLY /SURFACE
rem  
rem  
rem  (b) ScanDisk for Windows
rem  
rem  If Windows *can* start, use the Windows version of Microsoft's
rem  ScanDisk (a.k.a. ScanDisk for Windows) instead of, or as well as,
rem  the DOS version.
rem  
rem  NB: Do NOT allow SCANDISK to make any changes to the disk!
rem  
rem  *** Set PATH ***
:: SET PATH=%path%;C:\WINDOWS
rem  
rem  *** Run ScanDisk for Windows ***
:: C:\WINDOWS\SCANDISKW.EXE C:
:: C:\WINDOWS\SCANDISKW.EXE D:
:: C:\WINDOWS\SCANDISKW.EXE E:


rem  NORTON DISKEDIT
rem  ===============
rem  
rem  When Norton's DiskEdit 2002 first accesses a partition (i.e. drive)
rem  it spends 2 or 3 minutes scanning that partition. When the scanning
rem  completes, the details of any disk errors found are displayed.
rem  
rem  NB: The errors found can thereafter be viewed by going to -
rem      INFO - ERROR INFO
rem  
rem  NB: If there are too many directories on the partition, then,
rem      depending upon the amount of installed RAM memory, allowing
rem      the scan to complete will crash DiskEdit *and* the computer.
rem      (This can be avoided by aborting the scan part-way through)
rem  
rem  NB: On scanning a partition, *no* error information is normally
rem      displayed: i.e. no message pops-up saying there are NO disk
rem      errors! ONLY if a fault is found does a message appear.
rem  
rem  *** Run Norton DiskEdit 2002: FAT32, HDD exceeding 32GB ***
rem   **       (DISKEDIT.EXE in Norton Utilities 2002)       **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE
:: MOUSE
:: SET PATH=%path%;F:\SAVED\RECOVERY\DISKEDIT\NORTON\2002
:: DISKEDIT

rem  Warning:
rem  
rem  The function "Advanced Recovery Mode" in Norton DISKEDIT 2002
rem  does *not* work properly.
rem  
rem  To access that option, select "Physical disks" then go to:
rem  Tools - Advanced Recovery Mode
rem  
rem  The function reports an incorrect value for "Sectors per Cluster".


rem  NORTON DISK DOCTOR
rem  ==================
rem  
rem  Norton's Disk Doctor 2002 can scan a partition (i.e. drive), to
rem  check it for disk errors. Five different tests are run.
rem  
rem  NB: The option /Q causes all tests to run *except* surface scan.
rem  
rem  NB: For details of all options available in this program, see
rem      below (under "NORTON'S DISK DOCTOR").
rem  
rem  *** Diagnose a Partition ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\NDD
:: NDD C: /Q
:: NDD D: /Q
:: NDD E: /Q
rem  
rem  
rem  Warning -
rem  
rem  1. StarMan recommends that NDD should NOT be used on a system
rem  with many logical drives (especially if the system dual boots
rem  Windows NT/2000/XP and Windows 98, sharing a FAT32 drive).
rem  
rem  2. If you run NDD, *never* use the option FIX unless you save
rem  all changes to an Undo file! It is *not* entirely reliable.


rem  CHK IDENTIFIER
rem  ==============
rem  
rem  One of the problems running Scandisk is that if it finds FAT chains
rem  without any corresponding files, it creates its own set of files:
rem  typically in the format file0001.chk, file0002.chk, etc.
rem  
rem  When there are only a few files it is possible to guess what they are
rem  and rename the extension accordingly, but when there are hundreds or
rem  thousands of these files the task becomes a nighmare.
rem  
rem  Flobo's CHK identifier can help, as it reads each file and determines
rem  its file type. It is able to rename the files (as e.g. File0001.xls,
rem  File0002.doc, etc) so that you can quickly open the files and use them.


rem  CHECK HARD DISK FOR ERRORS
rem  ==========================
rem  
rem  1. Boot to DOS (with WinME Emergency Boot Disk)
rem  
rem  2. Run SCANDISK for DOS:-
rem      C:\WINDOWS\COMMAND\SCANDISK.EXE C: /CHECKONLY /SURFACE
rem      C:\WINDOWS\COMMAND\SCANDISK.EXE D: /CHECKONLY /SURFACE
rem      C:\WINDOWS\COMMAND\SCANDISK.EXE E: /CHECKONLY /SURFACE
rem  
rem  3. Run Norton's DiskEdit 2002:-
rem      F:\SAVED\RECOVERY\DISKEDIT\NORTON\DISKEDIT.EXE C:
rem      F:\SAVED\RECOVERY\DISKEDIT\NORTON\DISKEDIT.EXE D:
rem      F:\SAVED\RECOVERY\DISKEDIT\NORTON\DISKEDIT.EXE E:
rem  
rem      NB: Running this program in DOS automatically causes it to
rem          scan the Drive being loaded for faults. If it finds no
rem          faults, it doesn't tell you; but if any faults are found
rem          it pops up a warning message.
rem  
rem  4. Run Norton's Disk Doctor:-
rem      SET PATH=%path%;F:\SAVED\RECOVERY\NDD
rem      NDD C: /Q
rem      NDD D: /Q
rem      NDD E: /Q
rem  
rem      Options: /C = All tests *including* Surface Scan
rem               /Q = All tests *except* Surface Scan


::  /--------------------------------------------------------------------/  ::


rem                    WINDOWS UTILS TO CLONE DIRECTORIES
rem                    ==================================


rem  XXCOPY.EXE
rem  ==========
rem  
rem  XXCOPY v2.85.7
rem  
rem  The Windows program XXCOPY.EXE can clone individual directories,
rem  as part of the process of restoring a computer to its pre-crash
rem  state.
rem  
rem  Those utilities which can clone an entire disk (e.g. GHOST.EXE)
rem  (see above) will only partially restore the pre-crash state:
rem  even the most recent backup of the damaged disk will not be
rem  *entirely* up-to-date!
rem  
rem  XXCOPY can add to the cloned disk files (or entire directories)
rem  from other backup sources, while *preserving* the file dates
rem  (Created, Modified, and Accessed).
rem  
rem  *** Clone a Directory ***
:: XXCOPY "D:\Misc\" "C:\Misc\" /H /KS /E /TTA0 /TCA /TCC /TCW /ZE
rem  
rem  
rem  Note:
rem  
rem  The only useable version of XXCOPY is v2.85.7 as it does NOT suffer
rem  from the nag screens and restrictions that afflict other versions!
rem  
rem  
rem  SYNTAX -
rem  
rem  Directory names:
rem  
rem  The space character terminates the arguments, therefore a path with
rem  embedded spaces must be contained within quotation marks to be valid.
rem  
rem  
rem  The following switches check the destination directory:
rem  
rem    /I  If copying more than one file and destination does not exist,
rem        assumes that destination must be a directory (no prompting).
rem        Note: If the destination specifier ends with a backslash,
rem        that declares a directory and implicitly sets the /I switch.
rem  
rem  
rem  The following switches use file attribute bits:
rem  
rem    /H  Copies hidden and/or system files also.
rem   /H0  Excludes hidden and/or system files (default).
rem   /Ho  Copies hidden and/or system files only.
rem    /R  Overwrites read-only files.
rem   /K0  Keeps H-bit and S-bit, sets A-bit, clears R-bit (default).
rem    /K  Keeps the source attributes including read-only (same as /KS).
rem   /KS  Keeps the source attributes including the read-only bit.
rem   /KD  Keeps the attributes of the destination (overwritten) file.
rem   /KN  Sets the destination attributes to normal (only /A).
rem  
rem  
rem  The following switches deal with subdirectories:
rem  
rem    /S  Copies directories and Subdirectories except empty ones.
rem    /E  Copies directories and subdirectories, including Empty ones.
rem    /T  Creates directory structure, but does not copy files: copies
rem        all directories including empty ones (implicitly sets /E).
rem  
rem  
rem  The following switches control timestamps:
rem  
rem    /TTA  Touches (modifies) timestamp of Last Access of source.
rem   /TTA0  Preserves timestamp of Last Access of source (default).
rem  
rem    /TCA  Copies the timestamp of Last Access from source to dest.
rem   /TCA0  Uses current time for destination's Last Access (default).
rem  
rem    /TCC  Copies the timestamp of Create Time from source to dest.
rem   /TCC0  Uses current time for destination's Create time (default).
rem  
rem    /TCW  Copies the Last Write time from source to dest (default).
rem   /TCW0  Uses current time for destination's Last Write time.
rem  
rem     NB:  In Windows 9x, this ONLY works with Files. It does
rem          *not* work with Directories. To make a *genuine*
rem          clone of the disk, use e.g. Norton's Ghost (above).
rem  
rem  
rem  Batch File Options:
rem  
rem  Source is current directory -
rem   "."
rem  
rem  Example:
rem  XXCOPY "." "C:\My Documents\"
rem  
rem  No screen output, no log file -
rem   /oD0  
rem  
rem  
rem  CLONE Switch -
rem  
rem  XXCOPY "C:" "D:" /CLONE /ED
rem  
rem  /CLONE  Duplicates a directory or an entire partition. This switch
rem          is a shortcut for: /KS/H/E/R/Q/Y/BI/ZY/ZE/oD0
rem  
rem          NB: Really, an incremental backup, not a clone. The existing
rem              files on the target will be updated, but *only* if they
rem              have changed; and any new files (i.e. those not present
rem              at all on the target) will be added.
rem  
rem              This is NOT a byte-by-byte clone of the Partition: any
rem              new directories will have the CURRENT date. In Win9x,
rem              the date/time stamps of a directory can NOT be recreated
rem              (unlike those of a file).
rem  
rem  Options:
rem  
rem   /KS   Keep attributes of Source file
rem   /H    include Hidden and system files
rem   /E    include even Empty subdirectories
rem   /R    overwrite Read-only files in the destination
rem   /Q    Quiet (no screen display, no log file)
rem   /Y    suppress the prompt before overwriting
rem   /BI   copy all files in source that are different from
rem         files in destination in either filetime or size
rem   /ZY   delete extra files or subdirectories in destination,
rem         with *no* confirmation prompt
rem   /ZE   disable all Environment variables (e.g. COPYCMD /Y)
rem   /oD0  no screen output, no log file
rem  
rem  
rem  The following switches control empty directories:
rem  
rem     /ED0  Deletes an empty directory (default action).
rem      /ED  Preserves a directory even if it becomes empty.
rem   /ED{n}  Preserves only n levels of empty directories.
rem  
rem    Note:  These ONLY work in file/directory *removal*
rem           operations (/Z, /RC, /RS, /RD, /RX or /CLONE)
rem  
rem  
rem  XXCOPY cannot copy a Disk, only a Partition. And it is necessary
rem  to first use FDISK.EXE and FORMAT.COM to create and format the
rem  target Partition (see above).
rem  
rem  
rem  BACKUP THE WINDOWS DIRECTORY -
rem  
rem  This routine backs up and restores key Operating System
rem  directories, using an Incremental Backup to enable them
rem  to be more easily kept up to date.
rem  
rem  
rem  Syntax -
rem  
rem  /BI  Backup Incrementally: Only copy files which are
rem       different, either by time or by size. It adds files
rem       which have been altered since the last backup
rem       (overwriting the previous backup of those files).
rem  
rem  The option /BI compares files using both DATE and TIME
rem  
rem  The option /Y suppresses the prompt to overwrite an
rem  existing file
rem  
rem  The option /ZY deletes extra files or subdirectories in the
rem  destination (ones not in the source), with NO confirmation prompt!
rem  
rem  
rem  Files to Exclude -
rem  
rem  Exclusion specifier syntax (consists of up to 3 parts):
rem    For file:       [ dir_spec\ ] [ *\ ] [ ftemplate ]
rem    For directory:  [ dir_spec\ ] [ *\ ] [ dtemplate ]
rem  
rem  NB: The option *\ specifies that the exclusion applies also
rem      to all subdirectories of the specified directory
rem  
rem  Create a text file named exclude.txt and copy-and-paste into it
rem  the following:
rem  
rem  // Excluded subdirectories:
rem  "C:\Windows\Desktop\*\"
rem  "C:\Windows\History\*\"
rem  "C:\Windows\Recent\*\"
rem  "C:\Windows\TEMP\*\"
rem  "C:\Windows\Temporary Internet Files\*\"
rem  
rem  // Excluded Files:
rem  "C:\Windows\wiaservc.log"
rem  "C:\Windows\WIN386.SWP"
rem  "C:\Windows\Sti_Event.log"
rem  "C:\Windows\Sti_Trace.log"
rem  "C:\Windows\Cookies\index.dat"
rem  
rem  
rem  Backup the Windows directory -
rem  
rem  The following command will create a backup of the entire Windows
rem  directory, including all sub-directories (even if empty).
rem  
rem  The copies will retain their "Created" and "Last Modified" dates.
rem  
rem  *** Backup the Windows directory ***
rem  (NB: Excludes some uncopiable or undesirable files, as above)
:: XXCOPY /BI /H /R /KS /TTA0 /TCA /TCC /TCW /V2 /Y "C:\WINDOWS\" "C:\WinBak\" /E /EXexclude.txt /ZY /ED
rem  
rem  
rem  LOG FILE -
rem  
rem  To record XXCOPY errors in a Log (and save the Log in the root
rem  directory of Drive C:), add the following to the command line:
rem  /on:c:\error.log


rem  TOTAL COMMANDER
rem  ===============
rem  
rem  Total Commander v7.04a
rem  
rem  This program will NOT run under DOS, only under Windows.
rem  It has two useful directory cloning tools.
rem  
rem  
rem  1. The DirCpy Plugin
rem  
rem     It can copy a directory, retaining the date/time stamp
rem     of the source directory, using the DirCpy plug-in from
rem     http://physio-a.univ-tours.fr/tcplugins/dircpy.htm
rem  
rem     How to install DirCpy:
rem     1. Unzip dircpy.wcx into any directory
rem        (e.g. put it in C:\Program Files\DirCpy)
rem     2. In Total Commander, go to: Configuration > Options
rem     3. Click on 'Packer'
rem     4. Click the button "Configure packer extension WCXs"
rem     5. Type any extension (you'll never use it) into the box
rem        at top right, e.g. DirCpy
rem     6. Click on 'new type', and select the file dircpy.wcx
rem        in the directory to which you unzipped it (NB: Its
rem        address will then display in the 'Associate With' box)
rem     7. Click OK
rem  
rem     How to use DirCpy:
rem     1. Start Total Commander
rem     2. In the left-hand window, select the source directory
rem        (by right-clicking on it so that it turns RED)
rem     3. In the right-hand window, select the destination directory
rem     4. Go to: Files > Pack (or press Alt & F5); then in the 'Packer'
rem        box, select the bottom radio-button, i.e. the drop-down
rem        combo box; then in that combo box select the option DirCpy
rem     5. In the 'Packer' box, click the button "Configure";
rem        then tick "Preserve Date" and "Preserve Attributes"
rem        to preserve the date & attributes of the source directory;
rem        then click on "OK".
rem     6. Tick the option "Also pack path names (only recursed)"
rem     7. Tick the option "Recursively pack subdirectories"
rem     8. *Ignore* the display line that starts "DirCpy:" and ends
rem        in a file name. That file will NOT be created at the
rem        destination; only the Path will be used at the destination
rem     9. Then click on OK. This starts the process of creating
rem        the selected directory structure at the destinaton.
rem        (NB: No files are copied, so the process takes about 1 sec)
rem  
rem     Notes:
rem     - Options changed in the "Pack files" DialogBox are saved
rem       in the Windows registry.
rem     - The "Preserve date" option is valid on Windows 9x only
rem       in versions 1.03 and later of DirCpy.
rem     - Under Windows 9x, the "Preserve date" option requires
rem       the file Wc32to16.exe (installed by the Total Commander
rem       installation routine), and you will be prompted for its
rem       location at the first use. It is in the Total Commander
rem       directory (e.g. C:\Program Files\Total Commander).
rem     - XXCOPY can NOT preserve the date of a source directory
rem       in the copy, so it is necessary to use Total Commander
rem       to create the directory tree before copying any files.
rem  
rem  
rem  2. Automates XXCOPY
rem  
rem     It automates part of the process of running XXCOPY:
rem      - No source directory needs to be defined
rem      - It stores, and recalls, the latest command line
rem  
rem     Useful XXCOPY commands:
rem  
rem     A. Standard Command Line (to copy Files only) -
::      XXCOPY /H /R /KS /TTA0 /TCA /TCC /TCW /V2 "." "F:\BACKUP\"
rem  
rem     B. Include Subdirectories -
::      XXCOPY /H /R /KS /TTA0 /TCA /TCC /TCW /V2 /S "." "F:\BACKUP\"
rem  
rem     C. Newer Files only (in Current directory only) -
::      XXCOPY /BN /H /R /KS /TTA0 /TCA /TCC /TCW /V2 /Y "." "F:\BACKUP\"
rem  
rem     D. Files only (in current directory only); prompts if OLDER file
rem     at destination; skips files at destination that are NOT older;
rem     automatically copies files that DON'T exist at destination -
::      XXCOPY /BN /H /R /KS /TTA0 /TCA /TCC /TCW /V2 "." "F:\BACKUP\"
rem  
rem     E. Same as option D, but also DELETES files in the Destination
rem     directory that don't exist in the Source directory -
::      XXCOPY /BN /H /R /KS /TTA0 /TCA /TCC /TCW /V2 /ZY "." "F:\BACKUP\"


rem  FILE MANAGER (WINFILE.EXE)
rem  ============
rem  
rem  This program will NOT run under DOS, only under Windows.
rem  
rem  Windows 98/ME comes with an alternative file manager (i.e. other
rem  than Windows Explorer), that can manage a FAT32 disk: the 16-bit
rem  File Manager.
rem  
rem  It provides 16-bit disk access if EXPLORER.EXE (which provides
rem  32-bit disk access) is unavailable. So if Windows will not start
rem  even in Safe Mode, try replacing Explorer with File Manager.
rem  
rem  NB: File Manager is a 16-bit program! All files are shown with
rem      their short (8.3 format) filenames. All files copied using
rem      it will *lose* their Long File Names.
rem  
rem  To run File Manager, edit SYSTEM.INI at the DOS prompt. In the
rem  [boot] section replace the line SHELL=EXPLORER.EXE with the line
rem  SHELL=WINFILE.EXE then save the changes and restart the computer.
rem  
rem  *** Edit SYSTEM.INI ***
:: SET PATH=%path%;A:\
:: EDIT C:\WINDOWS\SYSTEM.INI
rem  
rem  *** Run 16-bit File Manager in Windows ***
:: C:\WINDOWS\WINFILE.EXE
rem  
rem  
rem  Note:
rem  
rem  The program DOS Shell (included in all versions of MS-DOS up to
rem  MS-DOS v6.22) is very much like a DOS version of File Manager.
rem  
rem  But to use DOS Shell it might be necessary to boot the system
rem  using an MS-DOS v6 bootdisk (instead of a Windows 9x bootdisk).
rem  This would NOT be wise, as MS-DOS v6 does NOT understand FAT32.


::  //  ::


rem                  ------------------------------
rem                  SECTION F: MISCELLANEOUS TOOLS
rem                  ------------------------------


rem                             DOS UTILS
rem                             =========

rem  DOSKEY
rem  ======
rem  
rem  *** Set PATH to include DOSKEY ***
:: SET PATH=%path%;C:\WINDOWS\COMMAND
rem  
rem  *** Run DOSKEY ***
:: DOSKEY
rem  
rem  Useful DOSKEY commands:
rem  F7 : Lists command history of current session
rem  UP / DOWN ARROW : Recall previous/next commands
rem  
rem  Source:
rem  DOSKEY.COM is NOT on a standard Windows ME emergency boot disk!
rem  (NB: It is found at C:\WINDOWS\COMMAND on a WinME hard disk)


rem  MENU GUI IN DOS
rem  ===============
rem  
rem  A file manager program with a GUI gives a visual representation
rem  of the file tree, simplifying finding files and recovery utils
rem  where Windows is unavailable due to a system crash.
rem  
rem  
rem  A. DOS NAVIGATOR (DN.EXE) -
rem  
rem  This (open source) program is the most sophisticated GUI for DOS
rem  in the known universe.
rem  
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS_NAV\DN
:: DN
rem  
rem  
rem  B. DISK MANAGER (DISKMAN4.EXE)
rem  
rem  Disk Manager v4.01 (2002)
rem  
rem  *** Run Disk Manager ***
:: DISKMAN4
rem  
rem  *** Run Disk Manager in Windows (i.e. in Console Mode) ***
:: DISKMAN4 CONSOLE
rem  
rem  
rem  C. DOS file editor (EDIT.EXE) -
rem  
rem  Recognises a hard disk of any size recognised by DOS.
rem  
rem  *** Run the program ***
:: SET PATH=%path%;A:\
:: EDIT A:\AUTOEXEC.BAT
rem  
rem  To see a visual representation of the Directory tree go to:
rem   FILE - OPEN
rem  
rem  
rem  D. LAPLINK PRO (LLPRO.EXE) -
rem  
rem  *** Set PATH to include LLPRO ***
:: SET PATH=%path%;C:\WINDOWS\COMMAND\LLPRO
rem  
rem  *** Run LAPLINK PRO 16bit File Manager ***
rem  (Program does NOT support Long File Names)
:: LLPRO
rem  
rem  NB: LapLink does NOT support Disks larger than 2GB, so it is
rem      UNSAFE to copy any files with it! ONLY use it to VIEW the
rem      Files & Directories, to locate their whereabouts on Disk.


rem  MEMORY USAGE
rem  ============
rem  
rem  A. MEM.EXE -
rem  
rem  MEM.EXE for DOS is an MS-DOS program included with Windows ME
rem  in the directory C:\WINDOWS\COMMAND
rem  
rem  *** Report on Conventional & Upper Memory with MEM.EXE ***
:: SET PATH=%path%;C:\WINDOWS\COMMAND;A:\
:: MEM /A /C /P
rem  
rem  ** Summary of Memory **
:: MEM /D /P
:: MEM /D /P > Memory_1.txt
rem  
rem  ** Comprehensive report on Memory **
:: MEM /C /P
:: MEM /C /P > Memory_2.txt
rem  
rem  
rem  B. MI.COM -
rem  
rem  *** Report on Memory Information with MI.COM ***
rem   **  MI.COM is at C:\WINDOWS\COMMAND\UTILS   **
rem  
rem  Syntax:
rem  
rem  MI [parameters...]
rem  
rem    /A  - All conventional memory details listed
rem    /C  - Conventional memory only; ignore EMS and Ext.
rem    /D  - Device driver list
rem    /E  - Ignore MI*OPT=[parameters] in environment
rem    /F  - Filter (i.e. hide) unprintable characters
rem    /H  - List the EMS and XMS handles
rem    /N  - No pause at full screen
rem    /O  - Other display format
rem    /Q  - Quick summary only
rem    /V  - List the 'hooked' vectors
rem    /?  - Display this command line help

rem  *** Memory Information ***
:: MI
:: MI /N > miReport.txt

rem  *** Summary of Conventional memory ***
:: MI /C
:: MI /C /N > miSumary.txt

rem  *** Comprehensive details of Conventional memory ***
:: MI /A
:: MI /A /N > miDetail.txt


rem  EDIT THE REGISTRY
rem  =================
rem  
rem  Although the Registry Editor (REGEDIT.EXE) is a Windows program,
rem  it can also run in DOS. Registry keys can be exported (e.g. for
rem  editing), imported, deleted or read in DOS.
rem  
rem  NB: For Windows 98/98SE/ME only!
rem  
rem  
rem  SYNTAX -
rem  
rem  /L:system       Specify the location of the SYSTEM.DAT file
rem  /R:user         Specify the location of the USER.DAT file
rem  /E              Export to registry file [NB: Omit if importing]
rem  filename.reg    Name of file which the data will be exported to
rem                  or imported from
rem  "registry_key"  Name of registry key to be exported [NB: Omit if
rem                  importing], e.g. "HKEY_CLASSES\ROOT\*\shell"
rem  
rem  NB: See also http://www.robvanderwoude.com/regedit.html
rem  
rem  
rem  *** Set PATH for using Regedit.exe ***
:: SET PATH=%path%;C:\WINDOWS
rem  
rem  
rem  A. Export a registry key in DOS
rem  
rem  Export a registry key to a file:
rem  REGEDIT.EXE [ /L:system | /R:user | /T:classes] /E filename.reg regpath
rem  
:: REGEDIT.EXE /L:C:\WINDOWS\SYSTEM.DAT  /E F:\EXPORT.REG "HKEY_LOCAL_MACHINE\DummyTree"
:: REGEDIT.EXE /R:C:\WINDOWS\USER.DAT    /E F:\EXPORT.REG "HKEY_USERS\DummyTree"
:: REGEDIT.EXE /T:C:\WINDOWS\CLASSES.DAT /E F:\EXPORT.REG "HKEY_LOCAL_MACHINE\SOFTWARE\CLASSES\DummyTree"
rem  
rem  NB: Once exported the key can be edited (using any text editor
rem      to edit the .REG file, which is a plain text file), then put
rem      back into the registry using the import command (below).
rem  
rem  
rem  B. Import a registry key in DOS
rem  
rem  Import (merge) a .REG file into the registry:
rem  REGEDIT.EXE [ /L:system | /R:user | /T:classes ] filename.reg
rem  
:: REGEDIT.EXE /L:C:\WINDOWS\SYSTEM.DAT  F:\IMPORT.REG
:: REGEDIT.EXE /R:C:\WINDOWS\USER.DAT    F:\IMPORT.REG
:: REGEDIT.EXE /T:C:\WINDOWS\CLASSES.DAT F:\IMPORT.REG
rem  
rem  
rem  C. Delete a registry key in DOS
rem  
rem  Option #1:
rem  
rem  REGEDIT.EXE [ /L:system | /R:user | /T:classes ] /D regpath
rem  
:: REGEDIT.EXE /L:C:\WINDOWS\SYSTEM.DAT  /D "HKEY_LOCAL_MACHINE\DummyTree"
:: REGEDIT.EXE /R:C:\WINDOWS\USER.DAT    /D "HKEY_USERS\DummyTree"
:: REGEDIT.EXE /T:C:\WINDOWS\CLASSES.DAT /D "HKEY_LOCAL_MACHINE\SOFTWARE\CLASSES\DummyTree"
rem  
rem  
rem  Option #2:
rem  
rem  First, create a .REG file to import: containing a delete instruction,
rem  followed by an instruction to re-create an empty key.
rem  
rem  Example: Delete all hardware devices, to enable the Windows plug-n-play
rem  wizard to do a complete hardware re-install on reboot -
rem  
rem  REGEDIT4
rem  [-HKEY_LOCAL_MACHINE\Enum]
rem  [HKEY_LOCAL_MACHINE\Enum]
rem  
rem  Second, import (merge) that .REG file into the registry:
rem  [NB: Choice depends upon which file the key belongs in]
rem  
:: REGEDIT.EXE /L:C:\WINDOWS\SYSTEM.DAT  F:\DELETE.REG
:: REGEDIT.EXE /R:C:\WINDOWS\USER.DAT    F:\DELETE.REG
:: REGEDIT.EXE /T:C:\WINDOWS\CLASSES.DAT F:\DELETE.REG
rem  
rem  
rem  D. Delete one item from a registry key in DOS
rem  
rem  First, create a .REG file with (for example) these contents:
rem  
rem  REGEDIT4
rem  [HKEY_USERS\DummyTree]
rem  "ValueToBeRemoved"=-
rem  
rem  Second, import (merge) that .REG file into the registry,
rem  as at C above.
rem  
rem  
rem  E. Read a registry key in DOS
rem  
rem  *** Step 1: Export the Registry Key to a file ***
:: REGEDIT.EXE /L:C:\WINDOWS\SYSTEM.DAT  /E F:\EXPORT.REG "HKEY_LOCAL_MACHINE\DummyTree"
:: REGEDIT.EXE /R:C:\WINDOWS\USER.DAT    /E F:\EXPORT.REG "HKEY_USERS\DummyTree"
:: REGEDIT.EXE /T:C:\WINDOWS\CLASSES.DAT /E F:\EXPORT.REG "HKEY_LOCAL_MACHINE\SOFTWARE\CLASSES\DummyTree"
rem  
rem  *** Step 2: Read the file ***
:: EDIT F:\EXPORT.REG


rem  REPLACE THE REGISTRY
rem  ====================
rem  
rem  Extract the Windows Registry from a backup .CAB file, in DOS,
rem  overwriting the current Registry.
rem  
rem  NB: For Windows 98/98SE/ME only!
rem  
rem  
rem  *** Set Path ***
:: SET PATH=%path%;C:\WINDOWS\COMMAND
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\COMMAND
rem  
rem  *** Extract all Registry files to their required locations ***
rem      NB: Rename the .CAB file to match the actual filename!
:: EXTRACT C:\WINDOWS\SYSBCKUP\RB001.CAB *.BAT /L C:\ /Y
:: EXTRACT C:\WINDOWS\SYSBCKUP\RB001.CAB *.SYS /L C:\ /Y
:: EXTRACT C:\WINDOWS\SYSBCKUP\RB001.CAB *.DAT /L C:\WINDOWS /Y
:: EXTRACT C:\WINDOWS\SYSBCKUP\RB001.CAB *.INI /L C:\WINDOWS /Y


rem  SAVE FILES TO DRIVE F
rem  =====================
rem  
rem  *** Save output data to Drive F: (USB Pen Drive) ***
rem   **    NB: Check that the USB disk is Drive F:   **
rem  
rem  ** STEP 1: Make a destination directory at Drive F: **
:: MD F:\SAVED\DATA\NEW_PC
rem  
rem  ** STEP 2: Copy all output files to Drive F: **
rem     Options -
rem       /V  Verify file was written correctly
rem       /Y  Suppress prompt to overwrite if file already exists
:: COPY *.* F:\SAVED\DATA\NEW_PC /V /Y


rem  PATH
rem  ====
rem  
rem  *** Restore the original PATH settings ***
PATH ;
SET PATH=%DOSpath%


::  /--------------------------------------------------------------------/  ::


rem                 WINDOWS ME EMERGENCY BOOT DISK
rem                 ==============================

rem  This is a customised startup configuration for a Windows ME
rem  Emergency Boot Disk (EBD): the bootable start-up floppy disk
rem  created by Windows ME.
rem  
rem  To create this floppy disk, start Windows ME then go to:
rem  START - SETTINGS - CONTROL PANEL - ADD/REMOVE PROGRAMS
rem  and click on the tab "Startup Disk".

rem  Note:
rem  The additional batch (.BAT) files referred to below concerning
rem  hard disk repair or data recovery are present on a *standard*
rem  Windows ME Emergency Boot Disk.

rem  Note:
rem  Some of the device drivers referred to below must be manually
rem  copied to the start-up floppy disk. Sources for those files
rem  are cited below ("PROGRAM DOWNLOAD SOURCES").
rem  
rem  Alternatively, here is a download link to an Image File which
rem  will create this customised Windows ME Emergency Boot Disk:
rem  
rem  http://myweb.tiscali.co.uk/bridip/toolkit/WinMeEBD.img
rem  
rem  (NB: Use UNDISKER.EXE to create the floppy disk)

rem  Note:
rem  The routines below are for Disk 1 with 2 Partitions (C: and E:),
rem  Disk 2 with 1 Partition (D:), and a USB Disk (F:). The USB Disk
rem  (a non-bootable pendrive) contains certain program files which
rem  are required in the routines (because an IDE disk might fail,
rem  so all rescue programs are stored on the USB disk); but these
rem  programs could be placed on ANY working IDE disk. Sources for
rem  these files are cited below ("PROGRAM DOWNLOAD SOURCES").

rem  Note:
rem  These CONFIG.SYS and AUTOEXEC.BAT files will need to be edited
rem  in order to work, if the rescue programs are not on Drive F:


rem  CONFIG.SYS
rem  ==========

::  [menu]
::  menuitem=QUICK,    Minimal Boot (Maximum DOS Memory)
::  menuitem=UNDELETE, Undelete Files
::  menuitem=BSOD,     Restore Registry
::  menuitem=DOSNAV,   DOS Navigator GUI, with USB
::  menuitem=CD,       DOS with RAM Disk, with CD-ROM
::  menuitem=USB,      DOS with RAM Disk, with CD-ROM & USB
::  rem menuitem=NOCD, DOS with RAM Disk, without CD-ROM or USB
::  menuitem=HELP,     Advice on running WinME, with RAM Disk & CD-ROM
::  menuitem=DISKEDIT, Norton's DiskEditor (Norton Utilities 2002) for FAT32
::  menuitem=TIRAMISU, Tiramisu Easy Recovery v6, with USB support (HDD exceeding 32GB)
::  menudefault=QUICK,60
::  menucolor=7,0
::  rem  NB: Only the first 9 menu entries will be displayed!
::  
::  [QUICK]
::  rem  No device drivers loaded
::  rem  Maximises the amount of free Conventional memory in DOS
::  
::  [UNDELETE]
::  rem  USB drivers for DOS:
::  devicehigh=USBASPI.SYS /o /e /v
::  devicehigh=DI1000DD.SYS
::  
::  [BSOD]
::  
::  [DOSNAV]
::  rem  DOS Navigator v6.40 & USB
::  devicehigh=USBASPI.SYS /o /e /v
::  devicehigh=DI1000DD.SYS
::  
::  [CD]
::  devicehigh=oakcdrom.sys /D:mscd001
::  rem device=btdosm.sys
::  rem device=flashpt.sys
::  rem device=btcdrom.sys /D:mscd001
::  rem device=aspi2dos.sys
::  rem device=aspi8dos.sys
::  rem device=aspi4dos.sys
::  rem device=aspi8u2.sys
::  rem device=aspicd.sys /D:mscd001
::  rem  
::  rem  RAM Disk driver (16MB RAMdisk):
::  devicehigh=ramdrive.sys /E 16384
::  
::  [USB]
::  rem  USB drivers for DOS:
::  rem
::  rem  ASPI Manager for USB mass-storage v2.24
::  rem  Panasonic Communications Co 2000-2007
::  devicehigh=USBASPI.SYS /o /e /v
::  rem
::  rem  Syntax -
::  rem   /u     UHCI, for enabling a USB 1.0 controller (NB: Obsolete)
::  rem   /o     OHCI, for enabling a USB 1.1 controller (Motherboard & PCI Card)
::  rem   /e     EHCI, for enabling a USB 2.0 controller (PCI Card USB 2.0 ports)
::  rem   /v     Verbose mode, useful for troubleshooting
::  rem   /w     Wait, displays message to prompt attaching of USB device
::  rem   /r     Resident, load as memory resident if USB floppy detected
::  rem   /l#    LUNs, specify highest number of LUN assigned: default /L0
::  rem   /slow  Use SLOW mode, gives longer delays on scanning USB ports
::  rem   /nocbc No CardBus Controller, disable detection on CardBus slots
::  rem
::  rem  You can specify more than one controller type (e.g. /o /e). Use
::  rem  this feature to specify which port types to enable: limiting
::  rem  the port types that are scanned for results in a faster startup.
::  rem
::  rem  These options work on the TINY PC:
::  rem  device=USBASPI.SYS /v
::  rem  device=USBASPI.SYS /o /v
::  rem  device=USBASPI.SYS /e /v
::  rem  device=USBASPI.SYS /o /e /v
::  rem
::  rem  DI1000DD ASPI Disk Driver v2.00
::  rem  (c) 2001 NOVAC Co Ltd
::  devicehigh=DI1000DD.SYS
::  rem
::  rem  RAM Disk driver (28MB RAMdisk):
::  devicehigh=ramdrive.sys /E 28672
::  rem  NB: This driver CANNOT create a 32MB RAMdisk
::  rem  NB: Maximum of 64 files can be placed in RAMdisk
::  rem
::  rem  CD-ROM driver:
::  devicehigh=oakcdrom.sys /D:mscd001
::  
::  [NOCD]
::  rem  RAM Disk driver (16MB RAMdisk):
::  devicehigh=ramdrive.sys /E 16384
::  
::  [HELP]
::  device=oakcdrom.sys /D:mscd001
::  device=btdosm.sys
::  device=flashpt.sys
::  device=btcdrom.sys /D:mscd001
::  rem device=aspi2dos.sys  :: These files deleted to provide disk space
::  rem device=aspi4dos.sys  :: on this floppy for essential USB drivers
::  device=aspi8dos.sys
::  device=aspi8u2.sys
::  device=aspicd.sys /D:mscd001
::  rem  
::  rem  RAM Disk driver (16MB RAMdisk):
::  devicehigh=ramdrive.sys /E 16384
::  
::  [DISKEDIT]
::  rem  Do NOT load HIMEM.SYS, as it will *conflict* with
::  rem  the internal memory manager in this version of DOS
::  
::  [TIRAMISU]
::  rem  USB drivers for DOS:
::  devicehigh=USBASPI.SYS /o /e /v
::  devicehigh=DI1000DD.SYS
::  rem  NB: Recovered files can be copied to the USB 8GB pen drive
::  rem  
::  rem  RAM Disk driver (28MB RAMdisk):
::  devicehigh=ramdrive.sys /E 28672
::  rem  NB: This driver CANNOT create a 32MB RAMdisk
::  rem  NB: By default, Tiramisu uses the RAMdisk as the swap area
::  rem  
::  rem  *** Load Tiramisu for 32-Bit FAT v3.03 (HDD 8GB or less) ***
::  rem  NB: There are NO device drivers for this version of Tiramisu!
::  rem  
::  rem  *** Load Tiramisu Easy Recovery v6.10 (HDD exceeding 32GB) ***
::  rem  NB: There are NO device drivers for this version of Easy Recovery!
::  
::  [COMMON]
::  files=40
::  buffers=10
::  stacks=9,256
::  lastdrive=z
::  dos=high,umb
::  device=display.sys con=(ega,,1)
::  country=044,850,country.sys
::  install=mode.com con cp prepare=((850) ega.cpi)
::  install=mode.com con cp select=850
::  install=keyb.com uk,,keyboard.sys


rem  AUTOEXEC.BAT
rem  ============

::  @echo off
::  cls
::  SET DIRCMD=/W/P/O
::  
::  \hibinv.exe
::  call \checksr.bat
::  IF "%config%"=="QUICK" GOTO QUICK
::  IF "%config%"=="UNDELETE" GOTO UNDELETE
::  IF "%config%"=="BSOD" GOTO BSOD
::  IF "%config%"=="DOSNAV" GOTO DOSNAV
::  IF "%config%"=="DISKEDIT" GOTO DISKEDIT
::  
::  ::Load RAM Drive...
::  set EXPAND=YES
::  set LglDrv=27 * 26 Z 25 Y 24 X 23 W 22 V 21 U 20 T 19 S 18 R 17 Q 16 P 15
::  set LglDrv=%LglDrv% O 14 N 13 M 12 L 11 K 10 J 9 I 8 H 7 G 6 F 5 E 4 D 3 C
::  cls
::  call setramd.bat %LglDrv%
::  path=%RAMD%:\
::  set temp=%RAMD%:\
::  set tmp=%RAMD%:\
::  copy command.com %RAMD%:\ > NUL
::  set comspec=%RAMD%:\command.com
::  copy extract.exe %RAMD%:\ > NUL
::  copy readme.txt %RAMD%:\ > NUL
::  ::
::  IF "%config%"=="TIRAMISU" GOTO TIRAMISU
::  
::  :ERROR
::  IF EXIST ebd.cab GOTO EXT
::  echo Please insert Windows Millennium Edition Startup Disk 2
::  echo.
::  pause
::  GOTO ERROR
::  
::  :EXT
::  %RAMD%:\extract /y /e /l %RAMD%: ebd.cab > NUL
::  echo The diagnostic tools were successfully loaded to drive %RAMD%:
::  echo.
::  
::  IF "%config%"=="NOCD" GOTO QUIT
::  ::
::  ::Load CD-ROM driver...
::  rem Next line can be disabled to save memory
::  LH %ramd%:\MSCDEX.EXE /D:mscd001 /L:%CDROM%
::  ::If MSCDEX doesn't find a drive...
::  rem Next line can be disabled to save memory
::  IF ERRORLEVEL 1 SET CDPROB=1
::  ::
::  IF "%config%"=="USB" GOTO USB
::  IF "%config%"=="HELP" GOTO HELP
::  ::
::  GOTO QUIT
::  
::  :QUIT
::  call fixit.bat
::  rem clean up environment variables
::  set CDPROB=
::  set CDROM=
::  set LglDrv=
::  GOTO END
::  
::  :QUICK
::  SET PATH=C:\REALMODE;C:\WINDOWS\COMMAND
::  SET PATH=%path%;C:\WINDOWS\COMMAND\UTILS;C:\WINDOWS\COMMAND\HDD_FIX
::  DOSKEY
::  GOTO END
::  
::  :UNDELETE
::  echo.
::  ::Load Mouse
::  F:\SAVED\RECOVERY\CONFIG\MOUSE.EXE
::  ::Norton Unerase for Win95
::  F:\SAVED\RECOVERY\UNDELETE\UNERASE.EXE
::  GOTO END
::  
::  :BSOD
::  A:\BSOD.BAT
::  GOTO END
::  
::  :DOSNAV
::  echo.
::  ::Load Mouse
::  F:\SAVED\RECOVERY\CONFIG\MOUSE.EXE
::  ::Include USB Disk in PATH...
::  SET PATH=C:\;F:\;A:\
::  ::Launch DOS Navigator v6.40
::  F:\SAVED\RECOVERY\DOS_NAV\DN.COM
::  GOTO END
::  
::  :DISKEDIT
::  echo.
::  ::Load Mouse
::  LH F:\SAVED\RECOVERY\CONFIG\MOUSE.EXE
::  ::Launch Norton Disk Editor (662KB)
::  SET PATH=F:\SAVED\RECOVERY\DISKEDIT\NORTON\2002
::  LH   F:\SAVED\RECOVERY\DISKEDIT\NORTON\2002\DISKEDIT.EXE
::  ::Launch Norton Disk Doctor (642KB)
::  rem PATH=F:\SAVED\RECOVERY\NDD
::  rem LH   F:\SAVED\RECOVERY\NDD\NDD.EXE
::  GOTO END
::  
::  :TIRAMISU
::  echo.
::  ::Load Mouse
::  F:\SAVED\RECOVERY\CONFIG\MOUSE.EXE
::  echo.
::  SET PATH=%ramd%:\;A:\
::  ::Load Tiramisu Easy Recovery v6.10 (HDD exceeding 32GB)
::  F:
::  CD \SAVED\RECOVERY\FILESAVE\TIRAMISU\EASYRE~1.10
::  xbios /P- /Z /I /M /V=2
::  substtoz VDISK
::  echo.
::  echo Your RAM Disk is %ramd%
::  echo Copying files to RAMdisk, please wait...
::  copy EASYREC.EXE %ramd%:\
::  %ramd%:\EASYREC %ramd%:\ /y
::  copy ER.BAT %ramd%:\
::  %ramd%:
::  LOADASPI
::  RDRINT13 /V=0
::  call ER.BAT
::  GOTO END
::  
::  :USB
::  echo.
::  ::Load Mouse
::  F:\SAVED\RECOVERY\CONFIG\MOUSE.EXE
::  ::Load SmartDrive
::  F:\SAVED\RECOVERY\CONFIG\SMARTDRV.EXE 4096 16>nul
::  ::Include USB Disk in PATH...
::  SET PATH=%path%;C:\;F:\;A:\
::  GOTO END
::  
::  :HELP
::  cls
::  call HELP
::  GOTO END
::  
::  :END


::  /--------------------------------------------------------------------/  ::


rem                           CALCULATORS
rem                           ===========


rem  NORTON DISKEDIT
rem  ===============
rem  
rem  Norton's DiskEdit 2002 includes a calculator with the ability
rem  to Add, Subtract, Multiply, Divide in Decimal, Hex and Binary;
rem  plus the ability to convert between Decimal, Hex and Binary.
rem  
rem  In DiskEdit, go to: TOOLS - CALCULATOR
rem  
rem  *** Run Norton DiskEdit 2002: FAT32, HDD exceeding 32GB ***
rem   **       (DISKEDIT.EXE in Norton Utilities 2002)       **
:: SET PATH=%path%;F:\SAVED\RECOVERY\DOS\REALMODE
:: MOUSE
:: SET PATH=%path%;F:\SAVED\RECOVERY\DISKEDIT\NORTON\2002
:: DISKEDIT


rem  BATCH FILES
rem  ===========
rem  
rem  A WinME batch file (i.e. an MS-DOS 8.0 batch file) has NO arithmetic
rem  functions, as those were not added to the MS-DOS "SET" command until
rem  Windows 2000.


::  /--------------------------------------------------------------------/  ::


rem                       CALCULATE LBA PARTITION
rem                       =======================


rem  CALC.EXE
rem  ========
rem  
rem  The script below will calculate the LBA sector numbers (i.e. the
rem  disk geometry) for a FAT32 partition, on a disk larger than 8GB.
rem  
rem  The markers /* and */ operate to comment-out whatever is enclosed
rem  between them. Nothing between those markers will be executed when
rem  the script is run.
rem  
rem  The script identifies the disk location (or "field") in which a
rem  particular value belongs. For example, the field "Sectors Before"
rem  in Partition Table entry No.1 in the Master Boot Record (MBR) is
rem  written as follows:
rem  
rem    MBR: 1,"Sectors Before"
rem  
rem  Some of the Print commands [print("")] included in the script are
rem  only there to generate an empty line, to make the output easier to
rem  read.
rem  
rem  The command -q (Quit) causes the program to exit when the script
rem  has finished running, and is case sensitive.
rem  
rem  The script will run under either DOS or Windows. However, it can
rem  crash Windows in some circumstances, so is safer to run under DOS.
rem  
rem  To run it, copy-and-paste the script into a file named GEOMETRY
rem  and then enter the following commands at the DOS prompt:
rem  
rem  *** Display the output on Screen ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\CALC\CALC
:: CALC GEOMETRY -q
rem  
rem  *** Save the output to a file ***
rem  [NB: Use a filename that identifies the Partition]
:: SET PATH=%path%;F:\SAVED\RECOVERY\CALC\CALC
:: CALC GEOMETRY -q >> DRIVE_C
:: CALC GEOMETRY -q >> DRIVE_D
:: CALC GEOMETRY -q >> DRIVE_E
rem  
rem  *** View the output file ***
:: EDIT DRIVE_C
:: EDIT DRIVE_D
:: EDIT DRIVE_E


rem  Extended Partition:
rem  
rem  In an Extended partition, the value "relative sectors" in the
rem  2nd entry of an EBPR Partition Table is relative to the start
rem  of the *entire* Extended partition - NOT to the start of the
rem  current Logical partition!
rem  
rem  This means the 2nd and 3rd Logical partitions (if present) will
rem  contain relative sector values in Entry No.2 that are relative to
rem  the start (i.e. partition) sector of the *1st* Logical partition.
rem  
rem  NB: The value "relative sectors" is the number of sectors from
rem      the Partition Table sector of the *1st* Logical partition
rem      to the end sector of the *current* Logical partition.


rem  Ultimate Calculator v1.8:
rem  
rem  A similar calculation can be done using Ultimate Calculator v1.8
rem  (UCALC.EXE) (a shareware program).


rem  Repairing a Partition Table:
rem  
rem  The safest way to make changes to a disk's Partition Table is
rem  the user-friendly program "PowerQuest Partition Table Editor"
rem  (PTEDIT.EXE) (see above).
rem  
rem  The script adopts the technical expressions used in PTEDIT.EXE
rem  so as to make it easy to insert values produced by the script
rem  into a disk's Partition Table using PTEDIT.


rem  Disk with Multiple Partitions:
rem  
rem  Join together the output files for all Partitions on the disk;
rem  because, combined, they make up the entire disk.
rem  
rem  This is a much more flexible solution than attempting to create
rem  a single script to calculate the values for every possible disk
rem  configuration, as there can be an unlimited number of Partitions.
rem  
rem  *** Merge several files into a single destination file ***
rem  (NB: One file for each of the partitions on the hard disk)
::   COPY DRIVE_C+DRIVE_E DISK_1
rem  
rem  Where a disk has *more* than one Logical partition, the value in
rem  the MBR for the total size of the Extended partition ("Sectors")
rem  will be the size of ALL the Logical partitions added together
rem  (the value "Sectors" from entry 1 in <u>each</u> EMBR/EBPR).


goto END_GEOM
rem                        *** Script Begins ***


/*                    CALCULATE GEOMETRY OF FAT32 HDD                */
/*                    ===============================                */


/*  SAVE OUTPUT: Predefined Variables (Decimal)                      */

/*  Calculate to 2 decimal places only                               */
    scale = 2

/*  Set Input and Output to either Decimal or Hexadecimal            */
/*  (NB: PTEDIT.EXE uses decimal, so set this to Decimal)            */
    /* Output is Decimal (base 10)         */
       ibase = 0xA     /* Input  = base 10 */
       obase = 0xA     /* Output = base 10 */
    /* Output is Hex (base 16)             */
    /* ibase = 0xG */  /* Input  = base 16 */
    /* obase = 0xG */  /* Output = base 16 */


/*  INPUT: User-entered Variables (Disk Data)                        */

/*  *** Identification of Disk ***                                   */
    print("DISK NAME: ____________ (Drive _:)
");print("
")

/*  *** Size of Disk (Sectors) (User-entered Variable) ***           */
/*  (From MBR: 1 "Sectors Before" + 1 "Sectors" + 2 "Sectors")       */
    SizeOfDisk = 00 + 00000000 + 000000000
    /* WD 80GB, Drive C & E = 63 + 20482812 + 135813510 = 156296385  */
    /* WD 80GB, Drive D     = 63 + 156296322            = 156296385  */

/*  *** Heads per Cylinder (0-254) ***                               */
/*  (NB: A mandatory value for all FAT32 disks)                      */
    HeadsPerCylinder = 255
    /* WD 80GB, Drive C & E = 255                                    */
    /* WD 80GB, Drive D     = 255                                    */

/*  *** Sectors per Track (1-63) ***                                 */
/*  (NB: A mandatory value for all FAT32 disks)                      */
    SectorsPerHead = 63
    /* WD 80GB, Drive C & E = 63                                     */
    /* WD 80GB, Drive D     = 63                                     */


/*  INPUT: User-entered Variables (Partition Data)                   */

/*  *** Start of Partition: Boot Sector ***                          */
/*  (From Tiramisu's Easy Recovery v6)                               */
    StartSector = 00
    /* WD 80GB, Primary DOS (Drive C) (LBA) =       63               */
    /* WD 80GB, Logical #1  (Drive E) (LBA) = 20482938               */
    /* WD 80GB, Primary DOS (Drive D) (LBA) =       63               */
    /* USB 8GB, Primary DOS (Drive G) (LBA) =       32               */
    /* Note:
    In a strict sense, a Logical partition starts 63 sectors
    before the Boot Sector, at the Partition Table sector!           */

/*  *** End of Partition ***                                         */
/*  (From Tiramisu's Easy Recovery v6)                               */
    EndSector = 00000000
    /* WD 80GB, Primary DOS (Drive C) (LBA) =  20482874              */
    /* WD 80GB, Logical #1  (Drive E) (LBA) = 156296384              */
    /* WD 80GB, Primary DOS (Drive D) (LBA) = 156296384              */
    /* USB 8GB, Primary DOS (Drive G) (LBA) =  15659007              */
    /* Notes:
    This could be calculated from: StartSector + SizeOfPartition     */

/*  *** Sectors Before Partition ***                                 */
/*  (From MBR "Sectors Before" & EBPR "Sectors Before")              */
    SectorsBefore = 00 +  0
    /* WD 80GB, Primary DOS (Drive C) =       63 +  0                */
    /* WD 80GB, Logical #1  (Drive E) = 20482875 + 63                */
    /* WD 80GB, Primary DOS (Drive D) =       63 +  0                */
    /* Notes:
    Primary DOS = MBR, 1 "Sectors Before" + 0
    Logical #1  = MBR, 2 "Sectors Before" + EBPR, 1 "Sectors Before"
    (NB: Each Logical partition is preceeded by 1 Head (63 sectors)
     for system data, equivalent to Track 0 prior to Primary DOS)    */

/*  *** Size of this Partition (sectors) ***                         */
/*  (From MBR "Sectors" or EBPR "Sectors")                           */
    SizeOfPartition = 00000000
    /* WD 80GB, Primary DOS (Drive C) =  20482812                    */
    /* WD 80GB, Logical #1  (Drive E) = 135813447                    */
    /* WD 80GB, Primary DOS (Drive D) = 156296322                    */
    /* Notes:
    Primary DOS = From MBR : 1,"Sectors"
    Logical #1  = From EBPR: 1,"Sectors"                             */

/*  *** Sectors per Cluster in this Partition ***                    */
/*  (From Boot Sector: "Sectors per Cluster")                        */
    SectorsPerCluster = 00
    /* WD 80GB, Primary DOS (Drive C) = 16                           */
    /* WD 80GB, Logical #1  (Drive E) = 64                           */
    /* WD 80GB, Primary DOS (Drive D) = 64                           */

/*  *** Number of Reserved Sectors in this Partition ***             */
/*  (From Boot Sector: "Reserved Sectors")                           */
    ReservedSectors = 00
    /* WD 80GB, Primary DOS (Drive C) = 32                           */
    /* WD 80GB, Logical #1  (Drive E) = 32                           */
    /* WD 80GB, Primary DOS (Drive D) = 32                           */

/*  *** Number of Hidden Sectors in this Partition ***               */
/*  (From Boot Sector: "Hidden Sectors")                             */
    HiddenSectors = 00 + 0
    /* WD 80GB, Primary DOS (Drive C) =       63 +  0                */
    /* WD 80GB, Logical #1  (Drive E) = 20482875 + 63                */
    /* WD 80GB, Primary DOS (Drive D) =       63 +  0                */
    /* Notes:
    Primary DOS = MBR, 1 "Sectors Before"
    Logical #1  = MBR, 2 "Sectors Before" + EBPR, 1 "Sectors Before"
    (NB: Each Logical partition is preceeded by 1 Head (63 sectors)
     for system data, equivalent to Track 0 prior to Primary DOS)    */

/*  *** FS Info Sector ***                                           */
/*  (From Boot Sector: "FS Info Sector")                             */
    FSInfoSector = 1
    /* WD 80GB, Primary DOS (Drive C) = 1                            */
    /* WD 80GB, Logical #1  (Drive E) = 1                            */
    /* WD 80GB, Primary DOS (Drive D) = 1                            */

/*  *** Backup Boot Sector ***                                       */
/*  (From Boot Sector: "Backup Boot Sector")                         */
    BackupBootSector = 6
    /* WD 80GB, Primary DOS (Drive C) = 6                            */
    /* WD 80GB, Logical #1  (Drive E) = 6                            */
    /* WD 80GB, Primary DOS (Drive D) = 6                            */

/*  *** Starting sector of 2nd FAT in this Partition (LBA) ***       */
/*  (NB: Find this sector using Norton's DISKEDIT (2002):
    Object > Drive > Physical Disks > Tools > Find Object > FAT)     */
    StartingSectorFAT2 = 00000
    /* WD 80GB, Primary DOS (Drive C): FAT2 =    10087               */
    /* WD 80GB, Logical #1  (Drive E): FAT2 = 20499547               */
    /* WD 80GB, Primary DOS (Drive D): FAT2 =    19172               */


/*  OUTPUT: Perform Calculation                                      */

/*  *** Partition ***                                                */
    print("Partition -
")
/*  *** Start of Partition ***                                       */
    print("Start of Partition: LBA ")
    StartSector

/*  *** End of Partition ***                                         */
    print("End of Partition  : LBA ")
    EndSector

/*  *** Boot Sector (LBA) ***                                        */
    print("Boot Sector: LBA ")
    SectorsBefore

/*  *** FSInfo Sector (LBA) ***                                      */
    print("FSInfo Sector: LBA ")
    SectorsBefore + FSInfoSector

/*  *** Boot Code Sector (LBA) ***                                   */
    print("Boot Code Sector: LBA ")
    SectorsBefore + 2

/*  *** Backup Boot Sector (LBA) ***                                 */
    print("Backup Boot Sector: LBA ")
    SectorsBefore + BackupBootSector

/*  *** Backup FSInfo Sector (LBA) ***                               */
    print("Backup FSInfo Sector: LBA ")
    SectorsBefore + BackupBootSector + 1

/*  *** Backup Boot Code Sector (LBA) ***                            */
    print("Backup Boot Code Sector: LBA ")
    SectorsBefore + BackupBootSector + 2

/*  *** File Allocation Tables ***                                   */
    SizeOfFAT = StartingSectorFAT2 - (SectorsBefore + ReservedSectors)
    print("Size of FAT (Big Sectors Per FAT): ")
    SizeOfFAT
    print("Starting sector of first FAT : LBA ")
    SectorsBefore + ReservedSectors
    print("Starting sector of second FAT: LBA ")
    StartingSectorFAT2

/*  *** Root Directory Table ***                                     */
    print("Start of Root Directory Table: LBA ")
    StartingSectorFAT2 + SizeOfFAT

/*  *** Data Area (User files) ***                                   */
    print("Starting sector of Data Area : LBA ")
    StartingSectorFAT2 + SizeOfFAT + SectorsPerCluster

/*  *** Hidden Sectors ***                                           */
    print("Hidden Sectors in this Partition   : ")
    HiddenSectors

/*  *** Big Total Sectors ***                                        */
    print("Big Total Sectors in this Partition: ")
    SizeOfPartition


/*  *** Number of Clusters in this Partition ***                     */
    print("Number of Clusters: ")
    (SizeOfPartition-ReservedSectors-(SizeOfFAT*2))/SectorsPerCluster

/*  *** Total Disk Space in this Partition (in KB) ***               */
    print("Total Disk Space in this Partition (KB): ")
    ((SizeOfPartition-ReservedSectors-(SizeOfFAT*2)) / SectorsPerCluster) * (SectorsPerCluster/2)
print("
");

/*  *** Sanity Test of this Partition ***
    (NB: Number of Cylinders in partition; MUST be a whole number)   */
    print("Sanity test of this partition: ")
    scale = 8
    SizeOfPartition / ( SectorsPerHead * HeadsPerCylinder )
    print("*Test is failed if that result is not a whole number!    
");print("
");


/*  *** Disk size in MegaBytes ***                                   */
    print("Disk size in MegaBytes  : ")
    SizeOfDisk / 2048

/*  *** Size of Disk: ***                                            */
    print("Total Sectors on Disk   : ")
    SizeOfDisk

/*  *** Disk Space after this Partition ***                          */
    print("Sectors after Partition : ")
    SizeOfDisk - ( SectorsBefore + SizeOfPartition )
    /* Note:
    If space AFTER the partition exceeds 1 cylinder (16,065 sectors)
    there is probably *another* partition present on this disk!      */
print("
");


/*  *** Size of Disk: C-H-S ***                                      */
    print("C-H-S values for Disk : ")

    print("C - Cylinders : ")
    trunc( SizeOfDisk / ( SectorsPerHead * HeadsPerCylinder ) )
    print("                        H - Heads     : ")
    HeadsPerCylinder
    print("                        S - Sectors   : ")
    SectorsPerHead

    /* Note:
    This does not calculate the actual values, but merely assigns
    mandatory values to 'Head' and 'Sectors'. Therefore there may
    be a small area of unpartitioned space at the end of the disk.   */

:END_GEOM
rem                         *** Script Ends ***


::  /--------------------------------------------------------------------/  ::


rem                       CONVERSION CALCULATIONS
rem                       =======================


rem  FORMULAS
rem  ========
rem  
rem  Number of Sectors in Partition = LBA End Sector (CHS End converted to LBA)
rem  - LBA Start Sector (CHS Start converted to LBA) + 1
rem  
rem  End Sector = LBA Start Sector + LBA Number of Sectors - 1


rem  CONVERT C-H-S TO LBA
rem  ====================
rem  
rem  The following script uses CALC.EXE to convert a disk sector address
rem  from a C-H-S value to an LBA value.
rem  
rem  The script will run under either DOS or Windows. However, it can
rem  crash Windows in some circumstances, so is safer to run under DOS.
rem  
rem  To run it, copy-and-paste the script into a file named CONVERT
rem  and then enter the following command at the DOS prompt:
rem  
rem  *** Display the output on Screen ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\CALC\CALC
:: CALC CONVERT -q
rem  
rem  *** Save the output to a file ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\CALC\CALC
:: CALC CONVERT -q >> CHStoLBA
rem  
rem  *** View the output file ***
:: EDIT CHStoLBA


goto END_CONV
rem                        *** Script Begins ***

/*  CONVERT C-H-S TO LBA:

    *** Formula to convert any C-H-S value to LBA ***
    (Cylinder x Heads per Cylinder x Sectors per Head)
     + (Head x Sectors per Head) + (Sector - 1) = LBA                */

    print("Enter no. of Cylinders : ")
    read( Cylinder )
    print("Enter no. of Heads     : ")
    read( Head )
    print("Enter no. of Sectors   : ")
    read( Sector )

    print("LBA = ")
    (Cylinder*SectorsPerHead*HeadsPerCylinder)+(Head*SectorsPerHead)+(Sector-1)

rem                         *** Script Ends ***


rem  CONVERT LBA TO C-H-S
rem  ====================
rem  
rem  The following script uses UCALC.EXE to convert a disk sector address
rem  from an LBA value to a CHS value.
rem  
rem  The script will run under either DOS or Windows. Unlike CALC.EXE,
rem  it does NOT crash Windows.
rem  
rem  To run it, copy-and-paste the script into a file named LBAtoCHS
rem  and then enter the following command at the DOS prompt:
rem  
rem  *** Save the output to a file ***
:: SET PATH=%path%;F:\SAVED\RECOVERY\CALC\UCALC
:: UCALC /NODEF < LBATOCHS
rem  
rem  *** View the output file ***
:: EDIT LBATOCHS


goto END_CONV
rem                        *** Script Begins ***

;  CONVERT LBA to C-H-S:

;  INPUT: Configuration

;  *** Set appearance of Prompt (for Prompt & Answer) ***
   PROMPT ""
   PROMPTA "   ="

;  *** Calculate to 8 decimal places only ***
   FIX = 8

;  *** Set Printer to Off ***
   PRINT OFF


;  INPUT: User-entered Values

;  *** Enter LBA Sector Number ***
   LBA = 0                                        ; LBA Sector Number

;  *** Disk Geometry ***
   SectorsPerHead = 63                             ; Sectors per Head
   HeadsPerCylinder = 255                        ; Heads per Cylinder


;  OUTPUT: Calculation Begins

   var_1 = LBA + 1                                            ; Add 1
   var_2 = SectorsPerHead                          ; Sectors per Head
   var_3 = HeadsPerCylinder                      ; Heads per Cylinder
   var_4 = var_2 * var_3                       ; Sectors per Cylinder
   var_5 = INT( var_1 / var_4 )
   var_6 = INT( var_5 )                         ; Cylinders (Integer)
   var_7 = var_1 - ( var_6 * var_4 )                      ; Remainder
   var_8 = var_7 / var_2
   var_9 = INT( var_8 )                             ; Heads (Integer)
   var_10 = var_7 - ( var_9 * var_2 )             ; Sectors (Integer)


;  OUTPUT: Save to File

;  *** Append Output to file named CHS.TXT ***
   WRITE "CHS.txt"

;  LBA Sector Number:
   (LBA)

;  CHS Address:

;  C - Cylinders :
   (var_6)
;  H - Heads     :
   (var_9)
;  S - Sectors   :
   (var_10)

CLOSE

:END_CONV
rem                         *** Script Ends ***


::  //  ::


rem                   ----------------------------
rem                   SECTION G:  SOFTWARE SOURCES
rem                   ----------------------------


rem                     PROGRAM DOWNLOAD SOURCES
rem                     ========================


rem  Note: If you can't obtain a file you need from the links below, try -
rem        http://www.mediafire.com/?sharekey=
rem        05e8d1826d6a41af6b21be4093fab7ac913585d3c76d43e4e91dc00c2f906379


rem  ATIS.EXE
rem  Acronis True Image, v8.1 (ATIS.UHA) (DOS & Windows version)
rem  Source: Hiren's Boot CD v9.6 (Hiren_s_BootCD_9.6.rar) (Hiren's.BootCD.9.6.iso)
rem  http://www.google.com/search?btnG=Google+Search&num=20&as_epq=Hiren_s_BootCD_9.6.rar
rem  Alternative source page: http://www.shared2u.com/index.php?do=search (search for: Hiren)
rem  [NB: That site requires you to register (free), AND log-in, in order to download files]

rem  APR.EXE (a.k.a. PR.EXE)
rem  Active Partition Recovery, v3.0 (ACTPARTR.CAB)
rem  Source: Utility CD v13.00 (UTILCDv13.rar) (UTILCDv13.iso)
rem  Source page: http://www.google.com/search?as_qdr=all&q=UTILCDv13&btnG=Search

rem  BEEBLEBROX.EXE
rem  Beeblebrox Partition Table Editor for Windows, v1.0 (a.k.a. beeblebrox9xsetup.zip)
rem  Source page: http://www.mediafire.com/download.php?mtdtmxnm5by

rem  BIOS.EXE
rem  Matthias Bockelkamp's BIOS utility, v1.35.1
rem  ftp://ftp.elf.stuba.sk/pub/pc/utildiag/bios1351.zip
rem  Alternative: http://info.elf.stuba.sk/packages/pub/pc/utildiag/bios1351.zip

rem  CALC.EXE
rem  Timothy C Frenz's Infinite Precision Calculator, v2.2
rem  ftp://ftp.simtel.net/pub/simtelnet/msdos/calculte/calc_v22.zip
rem  Alternative: http://ftp.chg.ru/pub/simtelnet/msdos/calculte/calc_v22.zip

rem  CHK IDENTIFIER
rem  Flobo's CHK identifier (Demo version) (untested)
rem  http://www.floborecoverysoft.com/FloboCHKIdentifierDemo.rar
rem  Alternative (Freeware): http://www.majorgeeks.com/CHK-Mate_d4110.html

rem  CMOS.COM
rem  Charles Dye's CMOS save and restore program, v0.93
rem  ftp://ftp.sac.sk/pub/sac/utilmisc/cmos93cd.zip

rem  CYLDIR.EXE
rem  Svend's CYLDIR, v5.5
rem  http://www.partitionsupport.com/cyldir55.zip

rem  DE.EXE
rem  PTS Disk Editor for FAT32 HDD exceeding 32GB, v1.04
rem  http://mirror.href.com/thestarman/tool/dl/PTSDE104.ZIP

rem  DISKEDIT.EXE
rem  Norton's Disk Editor, v7.0 (1993) (for FAT16)
rem  Files: http://asgard.kent.edu/smallsys/Norton/diskedit.exe
rem         http://asgard.kent.edu/smallsys/Norton/diskedit.hlp
rem         http://asgard.kent.edu/smallsys/Norton/nlib100.rtl

rem  DISKEDIT.EXE
rem  Norton's Disk Editor, from Norton Utilities 2002 (for FAT32)
rem  Files: http://www.currybeast.com/ftp/Tools/Norton%20Disk%20Doctor%202002/NU/DISKEDIT.EXE
rem         http://www.currybeast.com/ftp/Tools/Norton%20Disk%20Doctor%202002/NU/DISKEDIT.HLP
rem         http://www.currybeast.com/ftp/Tools/Norton%20Disk%20Doctor%202002/NU/DISKEDIT.ICO
rem         http://www.currybeast.com/ftp/Tools/Norton%20Disk%20Doctor%202002/NU/DISKEDIT.PID

rem  DISKMAN4.EXE
rem  Disk Manager, v4.01
rem  Source: The Ultimate Boot CD at http://www.ultimatebootcd.com
rem  Download page: http://www.ultimatebootcd.com/download.html

rem  DLGSETUP11_DOS.EXE
rem  Western Digital's Data Lifeguard Tools for DOS, v11.2
rem  http://www.esnips.com/nsdoc/0925669e-2d84-4fc8-8f4c-3fadba2bf836/?action=forceDL
rem  D/L page: http://www.esnips.com/doc/0925669e-2d84-4fc8-8f4c-3fadba2bf836/dlgsetup11_dos/

rem  DOSLFN.EXE
rem  Henrik Haftmann's LFN driver for DOS, v0.34d & v0.40e
rem  v0.34d: http://adoxa.110mb.com/doslfn/doslfnm.zip
rem  v0.40e: http://sta.c64.org/dosprg/doslfn.zip
rem  Further info: http://www.glennmcc.org/download/free_software/windos.htm

rem  DWSE_EN.EXE
rem  Seagate's DiscWizard Starter Edition (English)
rem  Version 10.32.05 (requires 1 floppy disk) -
rem   ftp://ftp.km.ru/v01/Soft/Utility2/DWSE_EN.EXE
rem  Version 10.45 (requires 2 floppy disks) -
rem   http://ftp.cs.pu.edu.tw/Windows/Softking/soft/en/d/dwse_en.exe
rem  Version DiscWizard 2003 (for Windows) (10MB) -
rem  http://karman3.elte.hu/~bazse/dl/win/sys/hd/discwizard2003_en.exe

rem  FINDPART.EXE
rem  Svend's FINDPART for DOS, v4.72
rem  http://www.partitionsupport.com/fpart472.zip

rem  GHOST.EXE
rem  Norton's Ghost for DOS, v8.3 (HDD Cloning utility)
rem  http://rs43.rapidshare.com/files/60199581/ghost.exe

rem  HD Clone, v3.6 Free Edition (HDD Cloning utility for Windows 9x) (IDE only)
rem  Source: http://www.google.com/search?btnG=Google+Search&as_epq=HDClone+3.6

rem  HD Clone, v3.6 Professional (HDD Cloning utility for Windows 9x) (IDE, SATA, USB)
rem  Sources:
rem  http://www.google.com/search?btnG=Google+Search&as_epq=HDClone+3.6+Professional
rem  http://rapidshare.com/files/151236627/www.mangga2.net_HDClone.Professional.v3.6.2-DOA.rar

rem  LCOPY.EXE
rem  Odi's COPY for long file names, v1.75 (English)
rem  http://mesh.dl.sourceforge.net/sourceforge/lfntools/lfn-1.75-en.zip

rem  LDIR.EXE
rem  Odi's DIR for long file names, v1.75 (English)
rem  http://mesh.dl.sourceforge.net/sourceforge/lfntools/lfn-1.75-en.zip

rem  LF.EXE
rem  Lost and Found, v1.31 (LOSTFND.CAB)
rem  Source: Utility CD v13.00 (UTILCDv13.rar) (UTILCDv13.iso)
rem  http://www.google.com/search?as_qdr=all&q=UTILCDv13&btnG=Search
rem  http://computersnewbie.blogspot.com/2009/07/pc-first-aid-tools.html

rem  MTL.EXE
rem  Media Tools Professional, v5.0 (MEDITOOL.CAB)
rem  Source: Utility CD v13.00 (UTILCDv13.rar) (UTILCDv13.iso)
rem  http://www.google.com/search?as_qdr=all&q=UTILCDv13&btnG=Search

rem  MBRScan.EXE
rem  Nobumichi Kozawa's MBR Scan for DOS, v1.12 (English)
rem  http://my.vector.co.jp/servlet/System.FileDownload/download/http/0/103907/
rem  pack/dos/util/disk/mbrs112.zip (NB: Re-combine this URL to a single line)

rem  MBRutilD.EXE
rem  PowerQuest's MBR Utility for DOS, (c) 2002
rem  ftp://ftp.symantec.com/public/english_us_canada/tools/pq/utilities/head.zip

rem  MBRWizD.EXE (for DOS/Win9x)
rem  Version 1.52: http://mbrwizard.com/dodownload.php?f=MBRWizD.zip
rem  Version 1.53: http://archives.mysteryfcm.co.uk/system/misc/mbrwiz/mbrwiz153.zip
rem  Version 2.0b: http://archives.mysteryfcm.co.uk/system/misc/mbrwiz/beta/mbrwizd2.0.zip
rem  Source: http://mbrwizard.com/download.php

rem  MI.COM
rem  Memory Information tool (English)
rem  http://www.uwe-sieber.de/files/mi_e.zip

rem  NDD.EXE
rem  Norton Disk Doctor for DOS, from Norton Utilities 2002 (FAT32)
rem  http://ftp.biology.hcmuns.edu.vn/DOWNLOAD/Software/ANTIVIRUS/NAV%20Software/NU/NDD.EXE
rem  http://ftp.biology.hcmuns.edu.vn/DOWNLOAD/Software/ANTIVIRUS/NAV%20Software/NU/NDD.HLP
rem  Alternative links:
rem  http://www.currybeast.com/ftp/Tools/Norton%20Disk%20Doctor%202002/NU/NDD.EXE
rem  http://www.currybeast.com/ftp/Tools/Norton%20Disk%20Doctor%202002/NU/NDD.HLP

rem  NORTON UTILITIES
rem  Norton Utilities 2002
rem  http://www.currybeast.com/ftp/Tools/Norton%20Disk%20Doctor%202002/NU/

rem  PART.EXE
rem  Ranish Partition Manager, v2.40
rem  http://www.ranish.com/part/part240.zip

rem  PARTINFO.EXE
rem  Star-Tools Partition Information program, v1.04
rem  http://www.star-tools.de/english/pub/partitionstar.zip

rem  Partition Logic, v0.69
rem  http://visopsys.org/files/partlogic/partlogic-0.69-img.zip
rem  RawWrite: http://visopsys.org/files/visopsys/rawwritewin-0.7.zip
rem  Source: http://partitionlogic.org.uk

rem  Partition Magic, v8.05 (Partition.Magic.8.05.rar) (Windows 9x)
rem  http://rapidshare.com/files/163418243/Partition.Magic.8.05.rar
rem  Source: http://www.google.com/search?hl=en&btnG=Google+Search&as_epq=partition+magic+8.05

rem  PTCALC.EXE
rem  PT Calc, PowerQuest's Partition Table Calculator for Win9x (CHS to LBA)
rem  ftp://ftp.symantec.com/public/english_us_canada/tools/pq/utilities/ptcalc.zip

rem  PTEDIT.EXE
rem  PowerQuest's Partition Table Editor for DOS, v1.0
rem  ftp://ftp.symantec.com/public/english_us_canada/tools/pq/utilities/ptedit.zip

rem  PTEDIT32.EXE
rem  PowerQuest's Partition Table Editor for Windows, v1.0
rem  ftp://ftp.symantec.com/public/english_us_canada/tools/pq/utilities/PTEDIT32.zip

rem  REBOOT.COM
rem  Reboot v1.0 (for DOS), (c) 1987 Strange Software Ltd ("What Micro?" Toolkit)
rem  http://myweb.tiscali.co.uk/bridip/toolkit/reboot.zip

rem  RESTORATION.EXE
rem  Restoration, v2.5.14
rem  http://files.snapfiles.com/localdl936/REST2514.EXE
rem  Download page: http://www.snapfiles.com/get/restoration.html

rem  SEATOOLD_EN.EXE
rem  SeaTools Desktop, v3.02 (English)
rem  http://www.google.com/search?btnG=Google+Search&as_epq=seatoold_en.exe&as_qdr=all

rem  SERCOPY.COM
rem  Serial Copy, (c) 1996 Future Publishing
rem  http://myweb.tiscali.co.uk/bridip/toolkit/SERCOPY.COM

rem  SRCFAT.COM
rem  SRCFat v1.3, (c) 2001 The WOrm (Save the FAT)
rem  http://www.zelja.com/AdminHeaven/Boot/TECHW0RM.ZIP

rem  TESTDISK.EXE
rem  TestDisk for DOS, v6.10
rem  http://www.cgsecurity.org/testdisk-6.10.dos.zip
rem  TestDisk for DOS and Windows 9x/ME, v6.11
rem  http://www.cgsecurity.org/testdisk-6.11.3.dos.zip
rem  Further info: http://www.cgsecurity.org/wiki/TestDisk

rem  The Sleuth Kit
rem  Brian Carrier's Sleuth Kit for 32-bit Windows, v3.0.1
rem  http://switch.dl.sourceforge.net/sourceforge/sleuthkit/sleuthkit-win32-3.0.1.zip
rem  Further info: http://www.sleuthkit.org

rem  TOTALCMD.EXE
rem  Total Commander for Windows, v7.02a (Shareware)
rem  http://download.oldapps.com/Total_Commander/tcmdr702a.exe
rem  Total Commander for Windows, v7.04a (Shareware)
rem  http://www.druk-reklama.com/pub/tcmdr704a.exe
rem  Further info: http://www.oldapps.com/Total_Commander.php

rem  UCALC.EXE
rem  Ultimate Calculator, v1.8 (Shareware)
rem  http://mail.nfbnet.org/files/spreadsheets/UCALC18.ZIP

rem  UNDISKER.EXE
rem  Undisker, v1.2 (Trial version)
rem  ftp://ftp.sac.sk/pub/sac/utildisk/undsk12.zip
rem  Further info: http://www.undisker.com

rem  USB 1.1 drivers for DOS -
rem  USBASPI.SYS  : Panasonic's ASPI Manager for USB mass-storage v2.24
rem  Di1000DD.SYS : ASPI Disk Driver v2.00, (c) 2001 NOVAC Co Ltd
rem  http://www.stefan2000.com/darkehorse/PC/DOS/Drivers/USB/mhairu.zip
rem  Further info: www.computing.net/answers/dos/usb-20-drivers-for-dos/13447.html

rem  XVI32.EXE
rem  Christian Maas's Hex Editor
rem  http://www.chmaas.handshake.de

rem  XXCOPY.EXE
rem  XXCOPY for Windows, v2.85.7
rem  http://www.xxcopy.com/download/xxfw2857.zip


rem  LINKS -
rem  
rem  Disk Partitioning, Formatting, Backup & Recovery Tools:
rem  http://www.mdgx.com/secrets.htm#FDPT
rem  
rem  Forums for sharing Computer-related problems and requesting help:
rem  http://www.JimmyClitheroe.co.uk/links.htm#General
rem  
rem  Windows 98 operating sysytem files:
rem  http://www.google.com/search?q=Win98+rar&btnG=Search&hl=en&aq=f
rem  
rem  Windows ME operating sysytem files:
rem  http://www.google.com/search?q=WinME+rar&btnG=Search&hl=en&aq=f


:END
::   Text copyright (c) 2009 Stephen Poppitt.
::   No copyright is held by me in the computer software programs mentioned.