+----------------------------------------+ | | | Partition saving | | | | http://www.partition-saving.com | | Copyright (c) 1999-2004 D. Guibouret | +----------------------------------------+ Errors list This file gives the list of errors that could be generated by Partition Saving. Errors could 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 could does some loss of datas). 1- Non fatal errors ------------------- - This file does not exist When restoring, you give the name on a non-existing file. - This file could not be created This file already exist and could not be overwritten (read-only) or you do not have access to it. When saving, you try to save into a read-only file. - 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 could be following: * Accessing file error File could not be opened. * Header not found Header could not be found. It is not a file created with savepart or it is erroneous. * Bad header version Header version is not known. This file could 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 file system type File system type into file header is not recognised, or when restoring from several files, file system type 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 could not be know. Choose another drive where to create file. - Free disk size could not be known Program is not able to get free disk size. 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 could not 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 could not be written. When restoring NTFS partition, boot sector copy could not 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 could not be written. Restoring this partition on a partition with a different size (notably on a partition with the same size as saved one) could solve this problem. This has no consequence as long as your hard disk does not has bad sectors. - Boot sector copy containing invalid data is not modified. FSInfo sector containing invalid data is not modified. Copy of FSInfo 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 could appear only when restoring FAT32 partition on a partition with a different format. - A compressed file could not 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. - The filesystem type contained into file could not be used to simulate an element. Driver could only be used with FAT element or with element where all sectors were saved. In this last case, element type is not checked, but if it is not a FAT element, DOS would not be able to access it. - Driver is set with a sector size different from element saved into this file. Driver could 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. 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 could also 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 could be also du to the fact that registry is not a Windows 2000 or XP registry. - File listing bad clusters could not be updated (<message>). This message could 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. 2- Fatal errors --------------- - Error when initialising deflating/inflating algorithm There was something wrong when initialising deflating/inflating algorithm. You can try again without deflating data (in case of save). - Error when deflating/inflating data There was something wrong when running deflating/inflating algorithm. If it is when deflating (when saving), you could try again without deflating data. If it is when inflating (when restoring), perhaps is the file erroneous. - Error creating file: <message> Error opening file: <message> An error appears when creating or opening a saving file. A message could explain the reason. - Seeking file error Reading file error Writing file error An error appears when seeking, reading or writing file. Perhaps is it erroneous. - Calculated CRC is not equal to saved CRC When restoring, saved CRC into file is not equal to calculated CRC. Perhaps is the file erroneous. - Bad flag marking last file Into header is an element to mark last file. Current state of restoration does not correspond to read header. Perhaps is the file erroneous. - Size of read data is not equal to saved size Into header an element save data size into file. Current restoration state does not correspond to read header. Perhaps is the file erroneous. - Error when allocating memory with DPMI interface DPMI server could not allocate memory. You need to free some DOS memory (below the first 640 Kb (conventionnal memory when you use MEM.EXE)) with removing drivers and program that you do not need into yours CONFIG.SYS and AUTOEXEC.BAT (add a "REM...
Kot_Maciek