MX File gets corrupt!

[shiro-hagen webforumsuser@macromedia.com]

Hi guys,

Our studio (5 macs) running 10.2.5 and OSX Server version 10.2.3 is experiencing sporadic corruption problems with MX as well.

I've not been able to duplicate how files are corrupted (retracing steps etc) - it almost seems like pot luck.

I've been working on a file, saved it, closed it and immediately tried to reopen it only to get the "not a valid freehand document" dialog. Then I've tried it on a backup of the file and the same process is fine.

Don't know how much help that is to you, just thought I'd add our experience to the thread.

Regards,
Andi

[shiro-hagen webforumsuser@macromedia.com]

The saga continues...

I've just lost another file. So in desperation I downloaded HexEdit and compared the header of the file that is corrupt to a fresh, no problems file.

The corrupted file doesn't contain the words "Freehand 11" in the top few lines of hex, whereas the fresh file (and 5 others I checked) did.

Perhaps it is an issue of MX corrupting the header/checksum of a file? Anyone got any ideas?

[Rich Hudgins]

So...have you tried editing the header to match the good file?

Rich

"shiro-hagen" [email]webforumsuser@macromedia.com[/email] wrote:

> The saga continues...
>
> I've just lost another file. So in desperation I downloaded HexEdit and compared the header of the file that is corrupt to a fresh, no problems file.
>
> The corrupted file doesn't contain the words "Freehand 11" in the top few lines of hex, whereas the fresh file (and 5 others I checked) did.
>
> Perhaps it is an issue of MX corrupting the header/checksum of a file? Anyone got any ideas?
>
>
>

[Andy Colquhoun]

I've noticed on 3 or 4 occasions that different files would crash out FHMX
on opening. Every time I have tracked it down to 'pasted inside' objects, if
you manage to halt the on screen drawing (command period) before it gets to
drawing the rogue paste inside you can switch to 'keyline' and FHMX will
happily draw the offending object, where you can then take it apart or
delete it.
The weird thing is I have took these steps and 'repaired' the file but I can
then paste the same object or group inside another identical shape and the
crash wont re-occur.

Very random bizarreness but at least I don¹t lose my work anymore.

Andy.

P.S. I also have found FHMX to be more stable since upgrading to OS X
10.2.6.

[shiro-hagen webforumsuser@macromedia.com]

Yeah I did try editing the file header by copying the data from a fresh file, but it made no difference. I'm no hex expert so I might be copying file data as well as header, or I might be missing a checksum somewhere...