Freehand 9.0.1 file corruption????
James
the 9.0.1 update. Since getting 9 we've been getting files that still look
like FH files on the desktop, still show the proper resources, etc., in
ResEdit, but when we try to open them in 9, they say the file is not a
Freehand file. Also tried to import the file, similar message. This doesn't
happen to all files all of the time, but it's hit several designers
randomly, sending them scrambling to find an earlier version of the file.
Often they can complete the work using the earlier version, but they're
getting to be afraid of FH 9, going back to 8 in some cases.
I saw one post that mentioned fonts, but all of our fonts have been run
through FontAgent 8 and show to be okay.
Any ideas to solve this are appreciated.
--James
Josh M. London
weeks, but I am on a P3 W98 machine. At the time, I had both FH8 and
FH9demo installed and the all the problem files were ones created with the
demo. I upgraded to FH9full AND uninstalled FH8 and have not had any
problems since and that was 4 or 5 months ago. Although I was never able to
recover those corrupt files.
I have yet to figure out what caused the problem, and frankly don't care as
long as it is "fixed". This is the same error you get when you try to open
an FH9 file in FH8 so I've suspected this might have something to do with
both versions installed on the same machine, but have no other basis for
this.
Sorry, this doesn't help your problem that much, but just wanted to let you
know I'd experienced a similar problem on the PC.
Josh London
Univ. of Washington
School of Aquatic and Fishery Sciences
"James" <jgr...@zachrinc.com> wrote in message
news:8sfiaa$oog$1...@misc.macromedia.com...
John
The same thing happened to me and I found it to be a damaged font.
Freehand 8 will let you use damaged fonts but not 9.1
As soon as I removed the font, the Freehand file worked great. This is
my excuse, and I know it may not make sense, but there it is.
I was able to recover the corrupt files.
You may want to adopt a file saving techique I use that saves work in these
cases, re: add the letter "A" somewhere in the file name of your
document name.
Each time you open the file to work on it, change the letter up one and resave.
This technique allowed me to save 90% of my work before I found the damaged
font and was able to meet my deadline.
John
"Josh M. London" wrote:
>
> Nearly the same problem happened to me on three projects over a span of 2
> weeks, but I am on a P3 W98 machine. At the time, I had both FH8 and
> FH9demo installed and the all the problem files were ones created with the
> demo. I upgraded to FH9full AND uninstalled FH8 and have not had any
> problems since and that was 4 or 5 months ago. Although I was never able to
> recover those corrupt files.
>
John
>
> The same thing happened to me and I found it to be a damaged font.
>
all copies of Freehand 8 would let you use damaged fonts,
I would like to clarify that statement for anyone who reads my last post
and gets the wrong message.
My copy of freehand 8 would run with a damaged font, not everyone elses.
My copy of freehand 9 would quit unexpectedly when using that font, not
everyone elses copy of freehand 9.
And this was just my observation of how both copies of freehand worked
on my particular
computer, and all of this is my experience but not that of MM or other
users of
freehand.
:-) hope this helps others not to be confused with my previous post.
John
old post:
Judy Arndt
<jo...@spamfree.edniegraphics.com> wrote:
> Having been politely rebuked for my global references that
> all copies of Freehand 8 would let you use damaged fonts,
> I would like to clarify that statement for anyone who reads my last post
> and gets the wrong message.
>
> My copy of freehand 8 would run with a damaged font, not everyone elses.
> My copy of freehand 9 would quit unexpectedly when using that font, not
> everyone elses copy of freehand 9.
I believe there are different kinds of font damage that affect FH
differently. Mac OS 8.6 had a bug that would damage a font's FOND resources.
(There's a fix on the Apple site for that, Font Manager Update.) Fonts
damaged in that way caused FH to crash.
I have had fonts damaged so that kerning was seriously haywire. They would
run in FH. Different problem--different affect on FH.
Judy Arndt
James
System Folder other than Chicago, Monaco, Geneva, etc., and turning off all
extensions. Freehand 9 worked, but I still couldn't open one of the "bad"
docs from our artists. My past experience with font corruption and programs
is that not having the bad font loaded allows you to open the app with a bad
font in its application...I've done this several times with Quark and other
Mac programs and it worked for me, but if it is fonts I'm not finding it.
--james
"John" <jo...@spamfree.edniegraphics.com> wrote in message
news:39ED01C2...@spamfree.edniegraphics.com...
>
> The same thing happened to me and I found it to be a damaged font.
>
James
have new machines with FH9 freshly loaded, but I think I'll check and see
about FH8 being on there. If it is, I'll try removing everything having to
do with FH8 that FH9 didn't install, rebuild the desktop and see what
happens. It would be interesting if something like this worked the same
way on both platforms. This and the corrupt font item seem to be my
best leads, though I am wondering about people working and saving
their documents to the network rather than their own computers.
"Josh M. London" <ha...@u.washington.edu> wrote in message
news:8shtov$35h$1...@misc.macromedia.com...
Mauricio Wolff
ha...@u.washington.edu (Josh M. London) wrote in
<8shtov$35h$1...@misc.macromedia.com>:
Hi; i'm desperate 'cause i'm having the same problem, and this never
happend to me before. I'm using freehand9 for a quite while now, and when i
open a very important document it keeps saying to me that "this file is not
a valid freehand file..."
Did you solve your problem? Can you help me with any solution?
Tks
+++
mau
>Nearly the same problem happened to me on three projects over a span of
>2 weeks, but I am on a P3 W98 machine. At the time, I had both FH8 and
>FH9demo installed and the all the problem files were ones created with
>the demo. I upgraded to FH9full AND uninstalled FH8 and have not had
>any problems since and that was 4 or 5 months ago. Although I was never
>able to recover those corrupt files.
>