8.0
Table Of Contents
- Introduction
- Getting Started
- PartitionMagic Basics
- PartitionMagic Main Window
- Rescue Disk Main Window
- Process Overview
- Selecting a Hard Disk and Partition
- Selecting an Operation
- Undoing an Operation
- Viewing Pending Operations
- Applying Changes to Your System
- Supported File Systems
- Changing PartitionMagic Preferences
- Using International Keyboards
- Defragmenting a Hard Drive
- Getting Help
- Managing Partitions
- Integrity Checks
- Browsing Partitions
- Resizing and Moving Partitions
- Creating Partitions
- Deleting Partitions
- Undeleting Partitions
- Changing Partition Labels
- Formatting Partitions
- Copying Partitions
- Checking Partitions for Errors
- Merging Partitions
- Splitting Partitions
- Getting Information About Partitions
- Scanning a Disk for Errors
- Defragmenting Drives
- Completing Advanced Disk Operations
- Converting Partitions
- Procedure for Converting Partitions
- Converting FAT Partitions to FAT32
- Converting FAT Partitions to NTFS
- Converting FAT32 Partitions to FAT
- Converting FAT32 Partitions to NTFS
- Converting FAT/FAT32 Partitions to 4K Aligned
- Converting NTFS Partitions to FAT or FAT32
- Converting Partitions to Logical or Primary
- Using Wizards
- Using PartitionMagic Utilities
- BootMagic
- Getting Started
- Configuring BootMagic
- Setting BootMagic Passwords
- Adding an Operating System to the BootMagic Menu
- Removing an Item from the BootMagic Menu
- Modifying a Menu Item’s Properties
- Setting a Default Operating System
- Booting from a Second Hard Disk
- Setting the Startup Delay
- Disabling BootMagic
- Using the BootMagic Menu
- Using BootMagic to Install Operating Systems
- Troubleshooting
- Using PartitionMagic With Other Programs
- Troubleshooting
- General Troubleshooting
- Freeing Memory to Run PartitionMagic under DOS
- Assigning a CD-ROM Drive Letter
- Using PartitionMagic With a SCSI Hard Disk
- PqRP Partitions
- Merging Partitions with Different NTFS Version Numbers
- Resolving Check Errors
- Resolving Partition Table Errors
- Partition Tables and Viruses
- Partition Will Not Boot After Resizing
- Generating Diagnostic Reports with PartitionInfo
- Error Messages and Solutions
- Miscellaneous Errors (3-38)
- Disk Access Errors (40-56)
- Miscellaneous Errors
- Partition Table Errors (100-199)
- #100 Partition table is bad
- #104 No sectors in partition
- #105 Partition starts on wrong boundary
- #106 Partition doesn’t start with sector one
- #107 Partition begins after end of disk
- #108 Partition doesn’t end at end of cylinder
- #109 Partition ends after end of disk
- #110 Partition table number of sectors is inconsistent
- #111 Logical partition starts outside of Extended
- #112 Logical partition ends outside Extended
- #113 Partitions overlap
- #116 Partition table Begin and Start inconsistent
- #117 Partition’s drive letter cannot be identified
- #120 The logical drive chain is incompatible
- #121 The first sector of the drive cannot be read
- #122 A bad sector was found in the current or new partition area
- #140 Overlapping partitions found. No partitions can be undeleted.
- Check Errors (500-599)
- Batch Errors (600-633)
- User Interaction Errors (950-999)
- #950 Unable to detect any disk drives
- #951 An invalid value was entered
- #952 Value entered is the same as the current value
- #963 Selected operation is currently invalid
- #968 Incorrect Volume Label entered, Deletion not performed
- #969 Incorrect Volume Label entered, Unable to proceed.
- #970 Invalid Bad Sector Check value specified
- #971 The label entered was too long
- #972 Invalid characters in the label
- #973 Volume Label cannot have leading spaces
- #974 Root size specified was not in the valid range
- #975 The cluster size specified was invalid for this partition
- #976 Cannot create the file system specified in the current space
- #977 Partition selected is invalid
- #978 Unable to set to proper partition after last operation. Script halted.
- #986 Unable to get information for the specified partition
- #993 Partition contains open files. Use the operating system check utility.
- NTFS Check Errors (1500-1699)
- #1501 Wrong version of NTFS
- #1503 Bad NTFS cluster size
- #1512 Restart record mismatch
- #1513 Bad attribute position in file record
- #1516 Partition improperly dismounted
- #1527 Bad update sequence number
- #1529 Information mismatch in directory entry
- #1538 Can’t find contiguous space to move
- #1539 File size mismatch
- #1544 External attribute list in external attribute
- #1545 File attributes out of order
- #1546 Attribute neither resident nor nonresident
- #1547 Wrong run limits
- #1548 File table has fewer than 16 entries
- #1549 File table has more than 4 billion entries
- #1604 File’s parent does not contain the file
- #1609 Lost cluster(s)
- #1630 Inconsistent sizes in attribute header
- #1644 Bad system file sequence number
- #1647 Error in root directory index
- #1681 Data is compressed or sparse
- #1687 An object index is present
- FAT Check Errors (2000-2099)
- #2001 FAT copies are not identical
- #2002 There are invalid entries in the FAT
- #2003 File size does not match FAT allocation for file
- #2005 One or more lost clusters are present
- #2012 Formatted FAT file system too big for partition
- #2013 A component of FAT geometry is bad
- #2024 The OS/2 Extended Attribute file is corrupt
- #2027 Too many root entries in the FAT32 partition to convert it to FAT16
- #4002 No valid NetWare volumes signature in volume definition table
- BootMagic Errors (8000-8999)
- Operating System Errors (over 10,000)
- Exit Code 12
- General Troubleshooting
- Service and Support Solutions
- Index
Norton PartitionMagic 123
controller has been changed, (5) the BIOS has been upgraded, (6) the BIOS LBA
setting has been changed, or (7) there is a partition table virus present on the hard
disk.
In most instances, you should resolve the problem as explained in “Resolving
Partition Table Errors” on page 114. You can also use a virus scanning program
to remove any partition table virus. Data loss is possible if the number of heads or
sectors per track has changed since you first created your partitions.
#117 Partition’s drive letter cannot be identified
Under OS/2, PartitionMagic must be able to find the drive letter for each partition
before modifications can be made. There are various reasons why OS/2 might not
be able to find a drive letter for each partition. For example, a driver on your
system may change the drive letters from their defaults, or your partitions may
not have serial numbers.
You may also see this error when running PartitionMagic under Windows.
The solution is to run PartitionMagic from DOS or from MS-DOS mode (in
Windows 95 or Windows 98). When PartitionMagic runs from DOS or from
MS-DOS mode, it does not need to be able to find the drive letter for each
partition. Thus, if the problem indicated by this error message is the only
problem, PartitionMagic can run successfully.
#120 The logical drive chain is incompatible
This error occurs under some operating systems when logical partitions are not
chained together in the expected order. DOS, OS/2, Windows 95, Windows 98,
and Windows NT require that logical partitions be chained together in ascending
order. Some other operating systems do not require this. For example, some
versions of the Linux FDISK utility chain logical partitions together in the order
they are created. This error message identifies a very dangerous situation; using
the DOS FDISK in this situation can cause loss of one or more partitions.
For solutions to this problem, see the instructions in “Resolving Partition Table
Errors” on page 114. If you decide to back up your data and recreate your
partitions, you may have to use the same partitioning program that you used to
create the partitions in order to delete them. Norton recommends recreating the
partitions with DOS FDISK or PartitionMagic.
#121 The first sector of the drive cannot be read
The first sector of the hard disk (cylinder 0, head 0, sector 1) contains the master
boot record (MBR) and the primary partition table. PartitionMagic cannot make
changes to this hard disk because an error occurred when it read the first sector.
See error #50 for information on resolving this error.