Data Area files Starting Cluster DBR disk geometry partition Jump Code OEM Name Version Sector Cluster Root Directory Entries Media Descriptor Track Heads Information Descriptor Flags Logical Drive Extended Signature Volume Name Executable Code JMP instruction boot record

Files Recovery Software
Home Contact Details Customer Support Download Demo Products  

 
 

You can also create sub-directories in the Data Area with files that appear to be contained inside them. In Fact, Subdirectories are nothing more than a special file which lists all of the files seemingly contained inside this directory and all the relevant data about each file such as, the location of each file's Starting Cluster, date, time and file size etc.

The DBR also contains some important information about the disk geometry. This information is located in the first sector of every partition,  such as:

  • Jump Code + NOP
  • OEM Name and Version
  • Bytes Per Sector
  • Sectors Per Cluster
  • Reserved Sectors
  • Number of Copies of FAT
  • Maximum Root Directory Entries (but Not Available for FAT32)
  • Number of Sectors in Partition Smaller than 32MB (Therefore Not Available for FAT32)
  • Media Descriptor (F8h for Hard Disks)
  • Sectors Per FAT (In Older FAT Systems and Not Available for FAT32)
  • Sectors Per Track
  • Number of Heads
  • Number of Hidden Sectors in Partition
  • Number of Sectors in Partition
  • Number of Sectors Per FAT
  • FAT Information Descriptor Flags
  • Version of FAT32 Drive
  • Cluster Number of the Start of the Root Directory
  • Sector Number of the File System Information Sector
  • Sector Number of the Backup Boot Sector
  • Reserved
  • Logical Drive Number of Partition
  • Extended Signature (29H)
  • Serial Number of Partition
  • Volume Name of Partition
  • FAT Name
  • Executable Code
  • Executable Marker or Magic Number (AAH 55H)

The first 3 Bytes of DBR contain a JMP instruction to skip the information and make extensions possible because the MBR loads this sector into memory and transfers execution to it. Usually these three bytes are hexadecimal numbers in format something like E9 XX XX (Hex) or EB XX 90 (Hex).

Following the initial JMP instruction OEM ID is an 8–Bit Field that is reserved by Microsoft for OEM Identification. The OEM ID describes the program that created the boot record. This is often "MSWIN4.0" for Windows 95/98/ME, "IBM 20.0" for OS/2 and "MSDOS5.0" for MS-DOS 4.0 and later.

Previous page

page 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 | 9 | 10 | 11 | 12 | 13 | 14 | 15 | 16 | 17 | 18 | 19 | 20


page 21 | 22 | 23 | 24 | 25 | 26 | 27 | 28 | 29 | 30 | 31 | 32 | 33 | 34 | 35

Next page
 
 
Data Recovery Book
 
Chapter 1 An Overview of Data Recovery
Chapter 2 Introduction of Hard Disks
Chapter 3 Logical Approach to Disks and OS
Chapter 4 Number Systems
Chapter 5 Introduction of C Programming
Chapter 6 Introduction to Computer Basics
Chapter 7 Necessary DOS Commands
Chapter 8 Disk-BIOS Functions and Interrupts Handling With C
Chapter 9 Handling Large Hard Disks
Chapter 10 Data Recovery From Corrupted Floppy
Chapter 11 Making Backups
Chapter 12 Reading and Modifying MBR with Programming
Chapter 13 Reading and Modifying DBR with Programming
Chapter 14 Programming for “Raw File” Recovery
Chapter 15 Programming for Data Wipers
Chapter 16 Developing more Utilities for Disks
Appendix Glossary of Data Recovery Terms
 
 
Pro Data Doctor

Home

Products

Contact Details

Customer Support

Download Demo

Terms and Conditions

 
Pro Data Doctor