CorelDRAW file will not open
Andrew McDonnell
the following problem with a CorelDRAW 4 file (in .CDR format).
While working on this file I received a message stating something
like "Unexpected condition encountered, please refer to CorelDRAW
Help.” The only choice was to click OK. I continued to work without
incident for about an hour, saved and closed the file, but was unable
later to open the .CDR file, or its .BAK backup later. (The two files
are of identical size, and regrettably probably are identically damaged
or corrupted.)
The file thumbnail is visible, and is up-to-date, displaying objects
that were created on the day of the last save and corruption. The file
size is consistent with its normal earlier versions. On the evidence,
all the data would seem to be intact, but inaccessible.
The drawing was rather complicated, and large (2.4 MB), and I
speculate that it may have too many objects, or too many nodes;
or that an “illegal” object was inadvertantly created and saved,
and that a corruption developed, which the aforementioned message
flagged, and which now keeps the file from opening.
Subsequent research suggests that the problem most likely is due to
the generation of objects with only one node: many users report that
this can cause file corruption. This may have resulted from my using
the standard Corel procedure of creating pie wedges from ellipses, which
in their initial state have only one node. The “unexpected condition”
message came up while these wedges were being manipulated.
I know that later versions of CorelDRAW have “media manager”
capabilities, including the use of .CMX files, which might be
able to re-open this file or extract its data, and I wonder if
experienced users are familiar with this sort of “unexpected
condition” error and corruption scenario.
Can anyone suggest a way to open this file?
Can anyone suggest a data recovery procedure to repair the file,
even partially, and to extract objects from the file?
Lastly, can anyone inform me of the proper steps to avoid such a
condition in the future, or the proper procedure to follow in the
event such a message comes up, to avoid such lockouts from a file?
Any help that could be provided would be sincerely appreciated.
Sincerely,
Andrew McDonnell
amcd...@concentric.net
Jerry Sanderson [C_Tech]
Jerry
C_Tech Volunteer