Kode Kesalahan Pada Partion Magic

PartitionMagic 8.0 error messages and solutions

Situation:

This document lists common error messages you may encounter while using Norton PartitionMagic 8.0 or PartitionMagic 8.0, and solutions to many common errors.

Solution:

Notes:

This information is also available on pages 117-137 of the Norton PartitionMagic 8.0 User's Guide.

In many cases, individual error messages have more detailed information available in documents specific to the error number. For the best results, search the Symantec knowledge base using the error number as the search string. For example, if you are looking for information on Error 56, use the search string "Error 56."

PartitionMagic error messages and possible solutions are listed below by number. The messages are also grouped in number ranges by error category.

Miscellaneous Errors (3–38)

#3 Not enough memory

This error can occur when you are resizing, moving, or copying an extremely large partition (60 GB) or when manipulating smaller partitions in DOS with EMM386 loaded. EMM386 limits the amount of memory the program can access. To solve the problem, modify your Config.sys file by commenting the EMM386 line. For more information about memory requirements, see PartitionMagic 8.0 system requirements.

The DOS PartitionMagic executable requires a minimum of 585 KB of memory in the first 640 KB of the computer's address space (conventional memory) and 8 MB of total memory. For possible solutions if you have insufficient conventional memory, see Freeing memory to run PartitionMagic under DOS.

You may be able to resolve this problem by rebooting to an A: prompt, typing LOCK_C:, and running PartitionMagic from the rescue disks.

#8 Could not allocate/deallocate DOS real mode memory

The DOS PartitionMagic executable running under DOS, Windows 3.x, Windows 95, and Windows 98 requires some memory in the first 1 MB of the computer's address space (PartitionMagic uses a DOS extender). If not enough memory is available, PartitionMagic cannot access the hard disk. For possible solutions, see Freeing memory to run PartitionMagic under DOS.

#27 Cannot lock drive

Under multitasking operating systems such as Windows 95, PartitionMagic must lock a partition before it can safely modify it. If the hard disk contains files that are in use by another process, PartitionMagic cannot lock the partition.

#29 Cannot lock a locked drive

Verify that the partitions you are attempting to modify are not on a locked hard disk.

#34 The Beta version is no longer safe to use

Norton occasionally releases beta versions and evaluation versions of PartitionMagic. Both versions are not as safe as release versions; therefore, Norton builds an expiration date into each version. After a predetermined test period, the beta or evaluation version no longer functions.

Disk Access Errors (40–56)

Errors in the 40–56 number range indicate that accessing your disk is not possible, and often result from hardware problems. Some problems may have simple solutions; for others, the only solution may be replacing the hard disk. When possible, PartitionMagic detects major errors before any changes have been made so you can back up your data before replacing the hard disk.

#45 CRC error in data

When PartitionMagic or any other program reads information off of a hard disk, it checks the CRC (cyclic redundancy check) information contained in each sector. If it performs a CRC test and the result is different from the value stored on that sector, there is a CRC error. This usually means one of two things.

The file being read has become corrupted by some other means.

A sector used in the file's storage has become bad and corrupted that part of the stored file.

The solution is to do a surface test to make sure any bad sectors are marked as bad, then reinstall the software involved to ensure that files on the system are not corrupted. You may also want to try running PartitionMagic with an /IRE switch.

#48 Sector not found

This error can be reported when a given sector cannot be read or written to. There are many possible causes.

If you are encountering this error, make sure that your BIOS supports the operating system and hard disk on the system. Also run a thorough ScanDisk on the drive to prevent data from being written to bad sectors.

#49 Write fault

#50 Read fault

(The following information applies to errors 49 and 50.)

PartitionMagic is unable to write to/read from a specific sector on the hard disk. Possible causes include:

If your PC beeps or displays a black box in the middle of the screen, virus protection is enabled in your computer's BIOS. Disable virus or boot sector protection in the BIOS.

A virus protection application (which may be a TSR or DLL program) is in use. Disable the application before using PartitionMagic.

There is a bad sector on the hard disk (this is usually the case only with older hard disks). Run ScanDisk on the hard disk to perform a surface scan to verify the existence of bad sectors. If your drive has bad sectors, we recommend you replace it.

You have set up disk mirroring with PC-Tools. Disable the disk mirroring option.

Miscellaneous Errors (70-99)

#70 Windows was deleted

If you are using Windows 3.x, you must create PartitionMagic rescue disks and run PartitionMagic for DOS.

#89 EZ-Drive has been detected on the drive but EZ-Drive is not running

#90 EZ-Drive has been detected on the drive but EZ-Drive is corrupt

#91 Disk Manager has been detected on the drive but is not running

These errors are "first head" errors. They can be resolved with assistance from Norton technical support. Before calling technical support, please type the

following at a DOS prompt:

wrprog /bak > x:head1.dat

where x: is one of the drives on your machine.

The Wrprog.exe file can be found in the Utility\DOS folder under your Norton product folder. If you are running under Windows NT and do not have DOS available, you can use the DOS rescue diskettes that you created for your Norton software.

#98 Hibernate Windows 2000/XP

#99 Hibernate Windows Me

Hibernation saves the system RAM to a file, then uses Advanced Power Management to shut the system down. When the machine is subsequently booted, the hibernation file is read into RAM, and execution begins where it left off.

A hibernated system assumes when it is booted that the system is in the same state as when hibernation occurred. Any changes made to the system's hardware (including disks and disk partitions) may cause unexpected results.

To avoid this error, shut down your machine normally and then restart.

Partition Table Errors (100–199)

Errors in the 100–199 number range are partition table errors. For general information about resolving these errors, see Resolving partition table errors and Partition tables and viruses.

#100 Partition table is bad

The master boot record (MBR) can contain, at most, one extended partition, and each extended partition boot record (EPBR) can contain, at most, one link to another EPBR. This error occurs when a partition table violates the foregoing rule. It can also occur if you have more than one active partition. Since any modifications PartitionMagic makes may decrease the amount of data that is recoverable from the hard disk, PartitionMagic does not recognize any of the hard disk's partitions. If you must create new, error-free partition tables to resolve your problem, see Resolving partition table errors for instructions.

#104 No sectors in partition

No partition should contain zero sectors. Delete the partition before using PartitionMagic.

#105 Partition starts on wrong boundary

#106 Partition doesn't start with sector one

The hard-disk partition table contains erroneous values. PartitionMagic expects partitions to begin and end on the correct cylinder boundaries. If they do not, the disk may be partially corrupted. In this circumstance, if PartitionMagic were to make any modifications it might cause the loss of data. Therefore, PartitionMagic refuses to recognize any of the hard disk's partitions. To resolve this problem, see the instructions in Resolving partition table errors.

#107 Partition begins after end of disk

This error can occur if a partition erroneously extends beyond the physical end of the hard disk. This may happen if the hard disk has been used on a different computer or with a different hard-disk controller or if BIOS settings have been changed. Be advised that the physical geometry of the hard disk may differ from the logical geometry assigned to the hard disk by the operating system.

#108 Partition doesn't end at end of cylinder

#109 Partition ends after end of disk

#110 Partition table number of sectors is inconsistent

The hard-disk partition table contains two inconsistent descriptions of the number of sectors on the hard disk. This error is serious if both DOS and another operating system use the hard disk. Because DOS uses one description and other operating systems may use the other, data loss is likely once the partition is almost full. To resolve this problem, see the instructions in Resolving partition table errors.

#111 Logical partition starts outside of Extended

#112 Logical partition ends outside Extended

An extended partition boot record (EPBR) is a sector on the hard disk that contains a partition table. The EPBR partition table is special because it generally only has two valid entries: one for the logical partition and one that is a pointer to the next EPBR. The standard is for the logical partition's entry to be the first entry in the table and the second entry is the pointer to the next EPBR. The third and fourth entries are not used. For some utilities, such as IBM's Boot Manager, the order of these entries is important because the utility expects the first entry to be the logical and the second entry to be the pointer to the next EPBR. If PartitionMagic detects that the EPBR entries are out of order, you will be prompted to fix the error. If you choose to fix the error, PartitionMagic will reorder the EPBR entries for you automatically.

#113 Partitions overlap

The hard disk partition table contains erroneous values. If data partitions overlap, writing to one may destroy data in another.

This error is sometimes the result of an OS/2 FDISK bug. If free space exists within the extended partition, OS/2's FDISK program allows a primary partition to be created that overlaps the extended partition. A logical partition is subsequently created in the space occupied by the overlapping primary partition. If a primary partition overlaps the end of the extended partition but does not overlap any logical partitions within the extended partition, the problem can be remedied by patching the partition table. Only qualified individuals should attempt this repair! An incorrect patch could destroy all data on the hard disk! In most instances, you should resolve the problem as explained in Resolving partition table errors.

#116 Partition table Begin and Start inconsistent

The hard disk partition table contains two inconsistent descriptions of the partition's starting sector. This error can occur if the operating system reports a hard-disk geometry that is different than the geometry in use when the partition table was written. Possible causes include: (1) different operating systems report different hard-disk geometries, (2) you boot from a diskette that loads a different driver than is loaded when you boot from the hard disk, (3) upgrading the operating system causes a different driver to be used, (4) the hard disk or 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. 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. 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.

#122 A bad sector was found in the current or new partition area

The partition cannot be moved safely because there is a bad sector in the new or current partition area. When you see this error message, the move operation is aborted before any corruption can occur. Try moving the partition to a different place. Run ScanDisk or CHKDSK /F with a surface scan before continuing. If your hard disk has bad sectors, we recommend that you replace the hard disk.

#140 Overlapping partitions found. No partitions can be undeleted.

Two or more deleted file systems were found in the unallocated space. However, each file system claims space that another file system also claims. There are no other partitions that can be undeleted.

Check Errors (500–599)

Check errors occur when PartitionMagic checks the integrity of a partition. For general information about resolving these errors, see Resolving check errors.

#500 Subdirectory is corrupted

This error message reveals the name of the corrupted subdirectory. Back up the contents of that directory and its subdirectories. You can then delete the corrupted subdirectory.

#501 Cross-linked files were found

Multiple files claim the same clusters. PartitionMagic can fix this error when it occurs on an NTFS partition. For more information, see Checking partitions for errors using PartitionMagic™ 8.0. PartitionMagic lets you fix this error by: (1) copying the shared clusters to each affected file, (2) deleting all affected files, or (3) keeping one file and deleting the other affected files.

#506 Not enough free space on partition to shrink

Some free space (which is dependent on the hard disk's current contents) is required to resize a partition smaller. Delete unneeded and duplicate files in the partition and then attempt the operation again.

#508 As specified, the operation does not change the partition

You have entered a value that is the same as or (when rounded to the required cylinder boundary) rounds to the same as the partition's present value. Enter a larger change.

#509 A bad sector was detected in the current or new FS area

In order to perform the resize operation that you requested, PartitionMagic attempted to expand the file system area. However, the program found a bad sector in the new area. Try moving the partition before you resize it. No corruption occurs when you encounter this error.

#510 The version of the file system is not supported

An updated version of PartitionMagic is required to operate on this new version of the file system. Visit www.symantec.com for information about updated versions of PartitionMagic.

Batch Errors (600–633)

#600 Batch file could not be opened

#601 Error trying to write batch file

#602 Batch file not found

PartitionMagic lets you specify a series of changes you want to make to your partitions, and then executes all the changes when you click Apply. At this point, PartitionMagic writes out a command list file (called a "batch file") to disk in preparation for execution, and then reads the file upon execution (immediately if a lock can be secured on all impacted partitions, or in a special "reboot" mode after rebooting your computer if not all locks can be secured). In the Windows 95, Windows 98, and Windows NT Workstation versions of PartitionMagic, the batch file is located in your Windows\System directory. In the DOS versions, it is located in the directory from which PartitionMagic is running. The batch file name is Pq_sm40.pqb.

If the batch file cannot be created, cannot be written, or cannot be located when PartitionMagic attempts to execute the command file, the above error messages appear. If you are running PartitionMagic from rescue disks, ensure they are not write-protected. If you cannot determine the source of the problem, contact Norton technical support.

#603 Unknown batch operation

The batch file contained an operation unknown to PartitionMagic. Contact Norton technical support.

#625 Batch structure has changed

Generally error 625 occurs only when the system needs to go into boot-mode to execute your commands. A 625 error occurs when your disk geometry is seen differently in your native Windows version of PartitionMagic than it is in the boot-mode version. For security reasons, PartitionMagic cannot apply your changes without risking data loss.

One common configuration that will cause a 625 error is a system that has a hard disk (such as a SCSI or removable drive) that is visible in Windows but that cannot be seen in the boot-mode environment.

Some possible solutions include:

Make sure the operation executes in native Windows mode (without resorting to boot-mode execution). PartitionMagic will only go into boot-mode if it cannot lock a partition (that is, if there are any open files on the partition). Try to confine all operations to drives PartitionMagic can lock before clicking the Apply Changes button.

Change the configuration of the offending disk (most likely the SCSI or removable drive) by changing the BIOS setup for that disk. Doing so will ensure that the native and boot-mode environments detect identical hard disk configurations. If this does not work, you can try temporarily disabling the offending disk.

This error usually indicates that some other application has modified your disk configuration while you were running PartitionMagic. Make sure no other applications are loaded while PartitionMagic is running.

User Interaction Errors (950–999)

#950 Unable to detect any disk drives

No partitionable hard disks were found on your computer. Diskette drives and many removable media drives do not support partitioning. PartitionMagic cannot perform operations on disks in such drives.

#951 An invalid value was entered

The value entered is outside the range or (when rounded to the required cylinder boundary) rounds to a value that is outside the range for the operation specified. Check the displayed range and reenter the value.

#952 Value entered is the same as the current value

See error #508.

#963 Selected operation is currently invalid

Not all PartitionMagic operations can be performed on all partitions. For example, you cannot create a partition if there is not enough unallocated space on

the hard disk. Options that are not available either do not appear on the menus or they appear dimmed. Refer to the relevant information in this user guide or the online Help for restrictions that explain why an operation is not available.

#968 Incorrect Volume Label entered, Deletion not performed

To delete a partition, PartitionMagic requires you to enter that partition's volume label. If the volume label you enter does not match the volume label of the partition you want to delete, this error appears.

#969 Incorrect Volume Label entered, Unable to proceed.

To format an existing partition, PartitionMagic requires you to enter that partition's volume label. If the volume label you enter does not match the volume label of the partition you are attempting to format, this error appears.

#970 Invalid Bad Sector Check value specified

This error occurs only in the enterprise version of PartitionMagic from a running script. If the script command SET DEFAULT BAD SECTOR TEST STATE is not followed by either ON or OFF, this error appears.

#971 The label entered was too long

When you enter a volume label, the process that checks the validity of the label displays this message if the label is too long. The label must be no longer than 11 characters.

#972 Invalid characters in the label

When you enter a volume label, the process that checks the validity of the label displays this message if the label has characters that are invalid. Invalid characters include the following: [ * ? : < > | + = ; \ / " , ].

#973 Volume Label cannot have leading spaces

When you enter a volume label, the process that checks the validity of the label displays this message if you enter a label in which a space or spaces are the leading characters.

#974 Root size specified was not in the valid range

This error occurs only in the enterprise version of PartitionMagic from a running script. If you use the Create, Format, or Resize Root operations, and the number of root entries specified is not within the acceptable range for that partition, this error appears. Generally, the valid range is from 64 to 1,024.

#975 The cluster size specified was invalid for this partition

This error message displays only in the enterprise version of PartitionMagic from a running script. Many commands have a cluster size option. If a script command specifies an invalid cluster size (for the type and size of the partition), this error appears.

#976 Cannot create the file system specified in the current space

This error message displays only in the enterprise version from a running script. When you use the Create or Format commands, you must also choose a file system type. If the file system or partition type you specified cannot be created in the space available, this error appears.

#977 Partition selected is invalid

This error message displays only in the enterprise version of PartitionMagic from a running script. If the partition selected from the Select Partition command is not a valid partition, this error appears.

#978 Unable to set to proper partition after last operation. Script halted.

This error message appears only in the enterprise version of PartitionMagic from a running script. After each operation, PartitionMagic ensures that the right partition is still selected. If PartitionMagic is not able to select the proper partition, it ends script processing and displays this error.

#986 Unable to get information for the specified partition

PartitionMagic reports this error most commonly when MS-DOS-based terminate-and-stay-resident programs (TSRs) are running in the background. These TSRs will be located in the Config.sys or Autoexec.bat files.

One such TSR is the SUBST command. The SUBST can be used to associate a path with a drive letter. This creates a "virtual drive" that can be accessed as an additional local drive. The SUBST command is classified as a "dirty" or "deadly" TSR, and cannot be loading at the same time that PartitionMagic is loading.

To solve the problem, you must remark out the Config.sys or Autoexec.bat line that is loading the SUBST command. This command can be reinstated after running PartitionMagic.

There are other "dirty" or "deadly" TSRs that may cause a problem. If you are experiencing this error and are not using the SUBST command, find and remark out any of the following commands: Join, Append, or Assign.

This error can also be reported if your C: drive is compressed. If the C: drive is compressed, you will need to either uncompress the drive, or run PartitionMagic from the rescue diskettes.

This error can also be caused by multiple partition table errors. If any of the above solutions do not apply, run PartitionInfo and send the report to Norton technical support. Refer to Generating diagnostic reports with PartitionInfo for information about PartitionInfo and PARTINFO.

#993 Partition contains open files. Use the operating system check utility.

To fix this error, disable any anti-virus programs on your system and run a thorough ScanDisk. You cannot use the Check for Errors operation on a partition with open files.

NTFS Check Errors (1500–1699)

Errors 1500–1699 are NTFS-specific check errors, which can occur when PartitionMagic checks the integrity of a partition. PartitionMagic can fix certain errors when you perform the Check for Errors operation. For more information, see Checking partitions for errors using PartitionMagic 8.0 and Resolving check errors.

In this section, "attribute" does not mean read-only, hidden, system, etc. Rather, "attribute" means one of a file's data streams.

#1501 Wrong version of NTFS

The partition was created using a version of the NTFS file format that PartitionMagic cannot work with.

#1503 Bad NTFS cluster size

The NTFS cluster size must be 512, 1,024, 2,048, 4,096, 8,192, 16,384, 32,768, or 65,536 bytes.

#1512 Restart record mismatch

The two restart entries in the journal file are different. This may happen if Windows NT Workstation is not properly shut down. To fix this problem, restart Windows NT Workstation, and then and shut it down using the Shut Down command.

#1513 Bad attribute position in file record

This error can often be resolved by running CHKDSK /F on the affected disk. For instructions on running CHKDSK, see How to run Microsoft CHKDSK from the command line.

If running CHKDSK /F does not help, please send the following items to Norton Technical Support:

A debug report. See Running a Debug Report.

A PARTINFO report. See Generating diagnostic reports with PartitionInfo.

The information outlined in Information needed for a Trouble Report.

If possible, an image of the machine or the actual hard disk, so Norton developers can examine the source of the issue more closely.

#1516 Partition improperly dismounted

The partition dirty flag is set in a restart record in the journal file. This error may have been caused by a power failure or system crash while the Windows NT operating system was writing the partition.

This problem can often be resolved by running CHKDSK /F on the affected drive. For instructions on running CHKDSK, see How to run Microsoft CHKDSK from the command line.

If running CHKDSK /F does not help, please send the following items to Norton Technical Support:

A debug report. See Running a Debug Report.

A PARTINFO report. See Generating diagnostic reports with PartitionInfo.

The information outlined in Information needed for a Trouble Report.

If possible, an image of the machine or the actual hard disk so Norton developers can examine the source of the issue more closely.

#1527 Bad update sequence number

A buffer contains mismatched update sequence numbers. This error may have been caused by a power failure or system crash while the Windows NT operating system was writing to the partition. Reboot Windows NT Workstation and execute CHKDSK /F to repair the damage.

#1529 Information mismatch in directory entry

A file attribute stored in a file record is different from the attribute stored in its directory entry. If this error is in a system file (file 0–10), Windows NT CHKDSK does not fix it, but Windows NT rebuilds the root directory on the partition the next time the operating system is started.

#1538 Can't find contiguous space to move

The partition does not contain enough contiguous free space to hold the new copy of a file that must be contiguous. You normally encounter this error when you use the Resize option to resize a partition smaller.

#1539 File size mismatch

The size of a system file (file 0–15) recorded in its file record does not match either the size recorded in its directory entry in the root directory or the size of its data stream.

#1544 External attribute list in external attribute

An external file record has an external attribute list.

#1545 File attributes out of order

The attributes in a file must appear in order of increasing numeric type.

#1546 Attribute neither resident nor nonresident

The attribute resident flag has a value other than resident or nonresident.

#1547 Wrong run limits

A run has more clusters than the difference between its highest and lowest cluster.

#1548 File table has fewer than 16 entries

The file table must have at least 16 entries.

#1549 File table has more than 4 billion entries

The file table must have fewer than 4 billion entries.

#1604 File's parent does not contain the file

The file's parent directory does not contain a reference to the file, or a file's size, date, or time information does not match the file's parent directory information.

This error can be fixed when you perform the Check operation. For more information, see Checking partitions for errors using PartitionMagic 8.0. When you fix this error, PartitionMagic updates the file's parent directory information.

#1609 Lost cluster(s)

The volume bitmap shows clusters as being used which are not used (no file claims them). This error can be fixed when you perform the Check operation. For more information, see Checking partitions for errors using PartitionMagic 8.0. PartitionMagic lets you fix this error by either deleting the lost clusters or by saving them in a file in the root directory. The file name is Filennnn.pqe, where nnnn is a number between 0000 and 9999.

#1630 Inconsistent sizes in attribute header

File size information is incorrect. This error can be fixed when you perform the Check operation. For more information, Checking partitions for errors using PartitionMagic 8.0. When you fix this error, PartitionMagic computes the correct file size information.

#1644 Bad system file sequence number

A system file has a bad sequence number. System files must have a sequence number from 1 to 15. A partition with this problem may pass Windows NT CHKDSK, but Windows NT does not mount the partition the next time the operating system is started.

#1647 Error in root directory index

There is an error in the root directory's index. Running Windows NT CHKDSK does not fix this problem, but Windows NT automatically rebuilds the root directory on the partition the next time it is started.

#1681 Data is compressed or sparse

There are compressed or sparse files on an NTFS file system that is being converted to FAT. Since FAT does not support sparse files and the compression technique used by Windows NT/2000/XP on the FAT file system is different than that used with NTFS, the compressed and sparse files would be unreadable if the conversion were performed.

When this error occurs on a Windows XP system, you can often fix the problem by disabling the Windows System Restore feature. To do this, right-click My Computer, select Properties, click the System Restore tab, and place a mark in the checkbox next to Turn off System Restore on all drives.

If the error occurs on a Windows NT or Windows 2000 system, or if turning off System Restore in XP does not solve the problem, perform the following:

In Windows, open a command prompt window.

Change to the root directory of the affected drive.

Type the following at the command prompt:

compact /u /s /a /i /f *.*

This command uncompresses all the files in the partition you run it on. Consequently, you should have ample free space in the partition to accommodate the larger file sizes. Also, depending on how many files are compressed, this process can be quite time consuming. If you need to abort the process at any point, press Ctrl+C inside the command prompt window.

After the uncompression process is complete, perform a search for the file EGA.CPI.

When you find the file, right-click on it, select Properties, click Advanced, and verify that the file is uncompressed.

You should now be able to perform the file system conversion without getting Error 1681. If you still receive the error, try locating and uncompressing the particular file that is referenced in the Error 1681 message by its FRS number (the first number that is not enclosed in parentheses). To do this:

Download the file BTIni.zip, then unzip the file.

Copy the Btini.exe file from the directory where you unzipped the BTIni.zip file to a floppy diskette.

Boot to the PartitionMagic rescue disk 1.

When prompted for disk 2, insert the floppy diskette containing Btini.exe, and press Enter.

Press Ctrl+C to halt the rescue disk batch process.

At the command prompt, type the following:

btini /show

This command displays the partition ID for the NTFS partition.

Type the following:

btini /frs <partition ID for the NTFS partition>:<FRSnumber displayed in the Error 1681 message>

This command returns the file name associated with the FRS number referenced in the Error 1681 message.

Reboot the computer to Windows, and search for the file reported by BTINI.

Uncompress or unencrypt the file.

You can also copy the file to another location and then delete it from its original location. After PartitionMagic has completed the conversion operation, you may then copy the file back to its original location.

For more information on using the BTINI utility, please see BTini and PQfile syntax and uses.

If Error 1681 is still reported after you have tried all the preceding steps, then reboot Windows, search for compressed files manually using Windows Explorer, and uncompress the files you find. For instructions on how to do this, see Uncompressing files in Windows NT, 2000, and XP.

#1687 An object index is present

A file with an object index created by Windows 2000 was found. For example, users may have been assigned disk space quotas. When converting a partition to FAT or FAT32, this information will not be saved, since FAT and FAT32 file systems do not support object indexes. (The FRS number for the compressed file found is shown.)

FAT Check Errors (2000–2099)

Check errors occur when PartitionMagic checks the integrity of a partition. For general information about resolving these errors, see Resolving check errors.

#2001 FAT copies are not identical

Run ScanDisk to fix this error.

This problem may also be caused by a virus. Run a virus checker and remove the virus if possible.

#2002 There are invalid entries in the FAT

This error can generally be fixed by running a thorough ScanDisk on the partitions reporting the error.

#2003 File size does not match FAT allocation for file

Run ScanDisk or CHKDSK to fix this error.

#2005 One or more lost clusters are present

Run ScanDisk or CHKDSK to fix this error.

#2012 Formatted FAT file system too big for partition

This error can occur when:

The number of sectors in the partition is larger than 65,536, and the bsHugeSects field of the boot sector ("Big total number of sectors" in Norton's DISKEDIT utility) shows that there are more sectors in the partition than the partition table shows.

The number of sectors in the partition is less than 65,536, and the bsSects field of the boot sector ("Total sectors on disk" in Norton's DISKEDIT utility) shows that there are more sectors in the partition than the partition table shows.

This situation can result in data loss when the FAT file system tries to use space outside the partition that does not exist or that belongs to another partition. Since file data may exist outside the partition boundary, you cannot fix the problem by simply patching the boot sector.

To correct the error, back up all data on the partition, delete the partition, recreate the partition, and restore the data. Alternately, it has been reported that you can use Norton Disk Doctor to fix this problem.

#2013 A component of FAT geometry is bad

This error can occur when:

The number of clusters on the hard disk is greater than the FAT limits allow. This can result from bad values in the boot sector for the number of sectors, FATs, root entries, reserved sectors, and sectors per cluster.

The number of sectors in the FAT is not large enough to hold the number of clusters present on the hard disk.

A qualified consultant may be able to fix the hard disk by performing simple patches. Alternately, you can back up the data on the partition, delete the partition, recreate the partition, and restore the files.

#2024 The OS/2 Extended Attribute file is corrupt

This error only occurs if you are running OS/2 and a program mistakenly writes to or overwrites the OS/2 Extended Attribute file. If this error occurs, you should back up your data, delete the partition, recreate the partition, and restore your data.

#2027 Too many root entries in the FAT32 partition to convert it to FAT16

Long file names may be causing this problem, since they use multiple entries per file. To fix this error, move some of the root directory entries into a subdirectory and defragment the disk.

#4002 No valid NetWare volumes signature in volume definition table

See error #3.

BootMagic Errors (8000-8999)

These errors are "first head" errors. They can be resolved with assistance from Norton technical support. Before calling technical support, please type the following at a command prompt:

wrprog /bak > x:head1.dat

where x: is one of the drives on your machine.

Operating System Errors (over 10,000)

Any number over 10,000 indicates an operating system error. To determine the number of the operating system error, subtract 10,000. (For example, 10,032 - 10,000 = 32) Consult your operating system documentation for information about resolving the error.

Exit Code 12

PartitionMagic needs free sectors in track 0 to install the virtual floppy file that applies operations in boot mode. If PartitionMagic cannot find free sectors in track 0, it returns this exit code. If you encounter this error, perform the following steps.

To resolve the problem

Download the Head.zip file, and unzip it to a folder on your hard disk.

Open a command prompt, and then change to the folder in which you unzipped the Head.zip file.

Type the following:

mbrutil /sh=head0.dat

This creates a backup of the first head (head 0) of your hard drive, which you can restore if something goes wrong when you run the Wipetrk.exe program.

To restore the first head, type the following:

mbrutil /rh=head0.dat

At the command prompt, type the following:

Wipetrk

This clears everything on your hard drive between bytes 512 and 32255 (the location of the data that is causing exit code 12).

If this does not resolve your issue, then run PartitionMagic from rescue diskettes.