Techsurvivors

Archives => 2007 => Topic started by: Raven on April 08, 2007, 09:39:20 PM

Title: My Freehand file is not valid??!!
Post by: Raven on April 08, 2007, 09:39:20 PM
I worked on a Freehand file this morning. Came back to it this afternoon and it will not open. Tells me that "the file is not a valid Freehand document"!

Tried restarting FH. Rebooted. Repaired permissions.  I doubled clicked the document, and tried opening from the Freehand Menu Bar. Neither way worked.
Nothing helps. I hate to have to rebuild the document from scratch. Never had this before.

Can I salvage my document?

FH v11. OS10.3.9.
Dual G4/1.25GHz
Title: My Freehand file is not valid??!!
Post by: krissel on April 10, 2007, 12:05:31 AM
First try dropping on the Freehand icon. Then drag the file across your dock or other icons of graphic programs and see if any highlight and if so drop it on them one at a time to see if any can open it. You may want to make a duplicate of the file first.

Haven't used Freehand in years but I do remember one constant problem people had with opening files and the application itself was with fonts. Only thing I can suggest is going into Font Book and see if you can find any corrupt fonts. Tiger version of font book can do this I think but Panther version doesn't. There are also third party apps that can check.

Other thing is to check the suffix on the name of the file to be sure it is actually labeled properly.

http://whatis.techtarget.com/file-extensio...42,sid9,00.html

http://www.macdisk.com/macsigen.php3

Here's another idea:  change the Type to "EPSF" and drop it directly on the Photoshop icon. Might work but will rasterize your vector stuff so do it with a duplicate.  Thinking.gif
Title: My Freehand file is not valid??!!
Post by: tacit on April 11, 2007, 03:50:05 AM
If none of the suggestions above work, it's quite possible your FreeHand file was corrupted and likely can not be salvaged.
Title: My Freehand file is not valid??!!
Post by: Raven on April 11, 2007, 10:19:34 AM
Nothing worked to bring it back. Had to redo the damn thing. Thanks for your suggestions.
:-)