
                  +----------------------------------------+
                  |                                        |
                  |            Partition saving            |
                  |                                        |
                  |    http://www.partition-saving.com     |
                  |  Copyright (c) 1999-2006 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: <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 could not 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 could 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 could 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 could 
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 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 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 could not 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 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. 

  - 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 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: 
    <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 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. 

  - 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 could 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 could not 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 could not be mounted. 

  - An error occured when resetting bad sectors: <message>

Resetting information on bad sectors into filesystem could not be done 
correctly. Message gives more details on the problem. Running "scandisk" on 
the corresponding drive could correct this problem. 


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 opening/creating file <name>: <message>. 
    Error creating file <name>: <message>. 
    Error on seeking into file <name>: <message>. 
    Error on reading file <name>: <message>. 
    Error on writing file <name>: <message>. 
    Error on closing file <name>: <message>.

An error appears when creating, opening, seeking, reading or writing a file. A
message could explain the reason. There could be several reasons (as disk 
full, bad sector, read-only file, ...). 

  - 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 " at beginning of line in place of removing it such 
as you could easily undo modifications). Another solution is to add 
"DEVICE=<directory>EMM386.EXE RAM" line at beginning of your CONFIG.SYS 
(<directory> is path to EMM386.EXE file). Program needs at least 300 Kb of 
free DOS memory. 

  - Error when calling interruption with DPMI interface 
    Error when calling procedure with DPMI interface

DPMI server could not call an interruption or a procedure. Try to load into 
memory a DPMI server that will replace the one used (CWSDPMI integrated into 
program). 

  - Not enough memory

Memory could not be allocated. If you are saving with deflating data, try to 
not use compression to save memory space. If you have more than 32 Mb of 
memory and EMM386 is activated, you could win space by disabling it (look at 
remark part into chapter about saving only occupied sectors for NTFS partition
into manual (chapter 18.i)). 

  - No element agrees with source

No element has been found which could correspond to format of saved element. 
For two elements to correspond, they have to respect some constraints 
described into manual at chapter 18. 

  - No element agrees with given choices

It was not possible to find an element that correspond to given choices or 
options. Check your option file or try without option file to see what are 
choices that are proposed to you. 

  - There was not enough option to choose an element

Options that you gave are not enough to choose an element. You have either to 
be more precise into options given or to not give some to see choice that is 
proposed to you. 

  - This program could not be executed under Windows

This program could not be executed on multitasking environment. You must boot 
your computer with DOS (not a DOS window under Windows). For this purpose, 
please read FAQ (Q 10). 

  - Value "<s1>" is not allowed for option <s2> (<s3>) 
    Value "<s1>" is not allowed for option <s2> (<d1>..<d2>)

Value you give for option <s2> is not correct. It must be one of the value 
given into <s3> or a number into <d1>..<d2> range. 

  - Language option is not given (-l en|fr|fr_2)

You give language option (-l) without following it by chosen language. 

  - Options file name is not given (-f <options file name>)

You give options file name option (-f) without a file name after. 

  - File name given into option file is not valid (line <n>)

Parameter given into options file for file name is not valid. Perhaps was the 
file name not given or it contains a space character. 

  - Disk number must be given if you want to give partition number

Options file must contain a "disk=" option if you want to give "main_part=" 
option. 

  - Main partition number must be given if you want to give extended partition
    number

Options file must contain a "main_part=" option if you want to give 
"ext_part=" option. 

  - Option "<s>" is unknown

Given option is not recognised. 

  - Option "<s>" is unknown (at line <n> of options file)

Given option <s> into options file at line <n> is not recognised. 

  - Option "<s>" must be defined only once

Given option is given more than once, when it could be given only once. 

  - Options file <s> could not be opened

Options file could not be opened. Is its name valid? 

  - An error occurred when reading options file at line <n>

Line <n> of options file could not be analysed. 

  - Support options (disk, floppy and device) could not be used together

Option file could define only one support. 

  - Format of <s> option ("<s>") is wrong, it should be: <drive number>:<disk 
    number>/<main part. number>,<extended part. number> with ",<extended part.
    number>" that must not be given for a main partition.

Option "mount=" that you gave into option file does not follow expected 
syntax. Expected format is the one described into error message. 

  - A sector containing parameters for filesystem could not be read 
    A sector containing parameters for filesystem could not be written

This error appears only when saving/restoring occupied sectors of a partition.
One of the sectors defining filesystem could not be read/written. As these 
sectors are needed for a good access to filesystem, saving/restoring is 
stopped to avoid errors. If this problem occurs when saving, you could choose 
to save all sectors. If this problem occurs when restoring, you could choose 
to restore it on another partition. In all cases, use a program like scandisk 
to possibly correct this problem. 

  - FAT sectors reading returns an error: <message>

This error appears only when saving/restoring occupied sectors of a FAT 
partition. 
Problem detail is given into following message. If problem is that FATs 
differ, you could use scandisk to correct it, then try again the saving (with 
saving occupied only sectors again). In case it is another message, problem is
more important and if running scandisk does not solve it you will have to save
the whole partition. 

  - FAT sectors writing returns an error: <message>

Writing modified FAT sectors back to disk generates an error. More details are
given into following message. It is better to run scandisk to try to solve the
problem. 

  - There were not enough sectors on partition to write all data

This error appears only when restoring occupied sectors of a partition. 
Despite the check of the minimum size to restore a partition, this partition 
is too small. This partition has not been modified if you restore a FAT 
partition, and only the first 1024 bytes of the partition have been modified 
if you restore an ext2 partition (they do not contain any data (having some 
boot code ?), so partition could be considered as not modified). Try to 
restore it on a bigger partition. 

  - An error occurred when updating bitmap: <message>. 
    An error occurred when updating filesystem: <message>.

In the case of NTFS partitions, filesystem could not be correctly built. 
Depending on the following error message, try to do restore/copy on a 
partition with a different size (smaller or bigger). Running chkdsk on this 
partition with option to force filesystem check could also solve problem. 
Doing restoring/copying on a partition with the same definition as the source 
one could not generate this problem. 

  - An error occurred when reading bitmap: <message>.

In NTFS partition, bitmap describes which sectors are occupied or not. 
Depending on following error message, running chkdsk with option to force 
filesystem check could solve the problem, else you will have to save the whole
partition. 

  - Trying to read a sector outside of the partition: accessing sectors 
    <n1>-<n2> when partition is on sectors <n3>-<n4>. 
    Trying to write a sector outside of the partition: accessing sectors 
    <n1>-<n2> when partition is on sectors <n3>-<n4>.

This error comes from an error of program or of systemfile. For not damaging 
datas outside of the partition, sector is not accessed and program stops. If 
you save only occupied sectors of the partition (saving or source partition 
when saving), try to check it (using scandisk by example). If some errors are 
found, correct them and try to save again. In another cases please contact me.

  - Driver could not be set as driver has not been found.

Options "-m" and "-u" could be used only if driver has been loaded. 

  - You could not create files on NTFS drive as you are not running Windows 
    NT/2000/XP.

Option "-n" to create file on a NTFS drive could only be used from an 
operating system that is able to manage this type of filesystem. 

  - Error when copying data into XMS memory. 
    Error when copying data into EMS memory.

An error occurred when using XMS or EMS memory. Try to use another XMS/EMS 
driver. 

  - You do not have enough EMS or XMS memory: <n> Kb free memory are needed.

For using driver, you need more EMS or XMS memory. Please read chapter 13 of 
manual to get more details on this error. 

  - Number of sectors to simulate an element differs from number of sectors 
    written into element (<n1> against <n2>).

Between what was declared into element and what was found, number of sectors 
is not the same. In this case driver is not initialised. Possibly, you could 
check if the file is correct. 

  - More than 255 files could not be used when initialising driver.

Driver is not able to simulate elements that are splitted in more than 255 
files. Use copying option to try to group several files together. 

  - Filename could not be more than <n> characters long when using driver.

Driver is not able to use file whose name (path + name) is more than <n> 
character long. Move these files into another directory to reduce name length.

  - Environment variable "<name>" is unknown.

Option file uses an environment variable that has not been found. You have to 
either define this environment variable or modify option file. 

  - Program could not treat this type of element for this operation.

When updating registry or BOOTSECT.DOS file, these operations could be 
performed only on some element type (Windows installation could only be 
searched on a partition or DOS device, entry to modify into registry could 
only correspond to a partition, BOOTSECT.DOS file could only be on a 
partition, a floppy disk or a DOS device). 

  - Error reading disk number into MBR.

This could be generated in case of faulty or wrong MBR. 

  - Registry modification was not done correctly: <message>.

This could be due to a bad support of NTFS filesystem, or a bad sector when 
reading or writing on disk. 

  - BOOTSECT.DOS file not found on this element or has a wrong size. 
    BOOTSECT.DOS file has an incorrect signature.

Support you choose seems not to have a BOOTSECT.DOS file on root directory, or
it has a wrong size or content. 

  - An error was raised when creating driver: <message>.

When restoring a partition for which only occupied sectors were saved, program
is not able to access to content of this partition with using its filesystem. 
This could be because of a bad saving file, so you have to check it. 

  - Driver for the element to restore is used elsewhere, doing restoration on 
    this element will lead to data lost. 
    Element you want to restore has some opened file.

When restoring, you mount a partition to be able to access to a saving file, 
then you use this partition as the restoration destination. This could not 
work, so you have first to copy file elsewhere then perform restoration. 

  - Element you want to save has some opened file.

You try to save a partition when you use some files on it. Either filesystem 
on this partition allows being saved on itself, in which case you have to use 
this option, or it does not allow this and so you could not do that. 

------
All trademarks and registered trademarks are property of their respective 
holders. 
