+--------------------------------------+ | Partition Saving | | | | http://www.partition-saving.com | | Copyright (c) 1999-2007 D. Guibouret | +--------------------------------------+ Errors list This file gives the list of errors that can be generated by Partition Saving. Errors can be divided into two types: - non fatal errors. - fatal errors. Firsts are errors generated by program but that did not stop its execution. Seconds are errors that are due to an encouterred problem that prevent program to follow its execution (else it can result in some loss of datas). 1- Non fatal errors ------------------- - This file does not exist: <message> When restoring, you give the name on a non-existing file. Following message gives more details on the problem. - This file already exist and cannot be overwritten. When saving, you try to save into a read-only or not available file. If it is not the case and you create file on an USB drive, it can be because it does not support writing file check, so you have to disable it with using -nvf option. If you try to create file on a mounted NTFS partition, you can not do that, you have first to create files from Windows before using them from DOS. - This file already exist and is on a drive for which you are not allowed overwriting a not empty file. When saving a partition on itself you try to overwrite a not empty existing file to create the backup file. This operation can lead to some errors after restoring, so it is not allowed. So you have to either create a new file or choose an empty file if creating file is not available. This message can only appear on FAT and ext2/ext3 partitions (on NTFS, overwriting a not empty existing file is available without any problem). - Given file is incorrect: <message> When restoring, you select a file that seems to be erroneous. Perhaps it is not a file created with savepart. Messages can be following: * Accessing file error File cannot be opened. * Header not found Header cannot be found. It is not a file created with savepart or it is erroneous. * Bad header version Header version is not known. This file can have been created with a more recent version of savepart. * Bad file size Size of file does not correspond to size saved into header. * Bad header CRC A CRC is used to check header. Calculated CRC is not equal to saved one. * Bad compression format Compression algorithm is not known. * Bad file number Given file is not the one waited when restoring must be done with several files. Perhaps you have inverted two files. * Bad disk format When restoring from several files, disk format of given file does not correspond to disk format of previous file. * Bad partition format When restoring from several files, partition format of given file does not correspond to partition format of previous file. * Bad filesystem type Filesystem type into file header is not recognised, or when restoring from several files, filesystem type of new file is not the same than for the previous file. * Unknown filesystem option An specific filesystem option (as saving an partition on itself) is not recognised by this version of program. Perhaps do you use a different version than the one used to perform saving. * Bad filesystem option A specific filesystem option of new file is not the same than for the previous file. * Bad support type Support type into file header is not recognised, or when restoring from several files, support type of new file is not the same than for the previous file. - There was not enough free space on chosen disk There was not enough free space on chosen disk or free disk space cannot be know. Choose another drive where to create file. - All groups/FATs were not written correctly This error appears if you restore occupied sectors of a partition. An error has occurred when restoring. This error is not fatal, because it does not stop program, but you will have to use a program like scandisk to check partition content. Try possibly to do restoring on another partition. - All data seem not to have been written on element (<n> bytes remaining) This error appears if you restore occupied sectors of a partition. An error has occurred when restoring. This error is not fatal, because it does not stop program, but you will have to use a program like scandisk to check partition content. Try possibly to do restoring/copying on another partition or check that file is valid. - All sectors were not written or more sectors were written than expected. When restoring/copying, it seems that all sectors were not written or too much sectors were written. This error is not fatal as it does not stop program execution, but you have to run some utilities like scandisk to perform a check of the partition. Try possibly to do restoring/copying on another partition or check that file is valid. - Number of sectors restored/copied/saved differs from number of sectors declared for element (<n1> against <n2>) This error is not fatal, because it does not stop program, but you will have to use a program like scandisk to check partition content. Try possibly to do restoring on another partition or check that file is valid. - Boot sector copy has not been found. When saving NTFS partition, boot sector copy cannot be found, so it would not be restored. As long as your hard disk has no bad sector this has no consequence. - Boot sector copy cannot be written. When restoring NTFS partition, boot sector copy cannot be written. Some versions of NTFS put this copy of boot sector on the middle of the partition and so, if when restoring partition, this sector is already occupied, copy of boot sector cannot be written. Restoring this partition on a partition with a different size (notably on a partition with the same size as saved one) can solve this problem. This has no consequence as long as your hard disk does not has bad sectors. - Filesystem information sector containing invalid data is not modified. Copy of filesystem information sector containing invalid data is not modified. Given sector contains some wrong data. It theorically needs to be updated, but in this case it is not done as this perhaps is not expected sector. Using scandisk will certainly correct this. This can appear only when restoring FAT32 partition on a partition with a different format. - A compressed file cannot be used to simulate an element. Using driver to simulate an element needs the saved file not to be compressed. Use copy file option to inflate file and then use this copy with the driver. - Driver is set with a sector size different from element saved into this file. Driver can only simulate element that has sector size equal to the one given when it was initialised. Change driver loading line such as sector size is equal to the one of the element into the saved file. - Registry file "<filename>" has not been found or is not correct: <message>. Partition or directory you gave seems not to have a Windows 2000 or XP installation. Check that you do not have made an error. It can also be due to a bad support of NTFS filesystem. - Registry key \HKEY_LOCAL_MACHINE\SYSTEM\MountedDevices has not been found or does not have any value Program can not find the registry key that defines list of drive letter and their definition or it does not have any value. - No registry value has been found that match searched name and type. Program can not find any value into registry that matches a partition definition. - Registry value for given drive letter has not been found or is not correct. Drive letter you gave does not exist into registry or does not correspond to a partition definition. This can be also du to the fact that registry is not a Windows 2000 or XP registry. - File listing bad clusters cannot be updated: <message>. This message can be displayed when restoring a NTFS partition on a partition with a different definition than the source one. Following error message gives you more details, but in most case it is not very bad error and you can run chkdsk on this partition with option to force filesystem check to correct it. - Update of filesystem of <drive> has generated an error: <message>. Update of filesystem information on a partition you mount has generated an error and filesystem is certainly into some inconsistency state. It is better to run some check program as scandisk on it to correct this. If you created some file on this drive, it is better to check them because they can be wrong. - This partition is already mounted as <drive>:. Mount value <drive> is already used for another partition. Partition that should be mounted as <drive>: is already mounted as <drive>:. Filesystem to mount <drive>: is not recognised. Partition to mount <drive>: does not exist. Disk to mount <drive>: does not exist. Chosen partition cannot be mounted (saved or restored one or it was modified through DOS). Partition to mount on <drive> has been modified with DOS. Use it instead. These error messages are displayed when trying to mount a partition. They say why a partition cannot be mounted. ...
lolos81