I just installed Freehand 11.0.2, the graphic axe I've been
using for at least five years through various upgrades, after
having removed all traces of a previous installation of ALL the
programs in my MX 2004 suite to start over with a pure,
Macromedia-free set up (sigh). While the Macromedia disk used for
the install tested fine on another XP SP2 computer, on mine the
very first run of the program opens with problems: the particularly
ugly shades o' gray Welcome to Freehand" blurb on screen one (on my
two screen system) and a blank Freehand window on screen two (not
under the blurb on screen one where it should be) - and the blank
window has NO new blank file opened inside, and no tool bars or
palettes either.
*****.
Opening a new file from the menu doesn't do anything but present a new file - still no palettes or panels, despite both being turned on for viewing in the menus (and they all work from right-click). I've tried ALL of the fixes provided by Adobe in Tech note 13186 as suggested by Judy Arndt earlier, to no avail. Even reconfigured my system to one-screen-only as a test. Nope.
Because the program appears to perform correctly on other systems I thought the problem must be with my system. But I have no other pallete or tool bar issues with other apps in my "designer's toolbox" and specifically none with the other programs in the MX 2004 suite and anyway, Freehand isn't even painting it's own automatic new install/first-run opening screens correctly, a step so early in the first-run process that it's hard to believe anything significant already resident on my computer is mucking it up.
I have to think there's a snippet of code somewhere that Freehand (and apparently Freehand alone) references first thing when it starts up, and that snippet's corrupt. Needless to say, I haven't a clue about how to attack that. Would really appreciate help from any propeller head out there... and thanks in advance. I'll even tackle Registry changes without a backup first (gasp!) if I have to.
Jim
*****.
Opening a new file from the menu doesn't do anything but present a new file - still no palettes or panels, despite both being turned on for viewing in the menus (and they all work from right-click). I've tried ALL of the fixes provided by Adobe in Tech note 13186 as suggested by Judy Arndt earlier, to no avail. Even reconfigured my system to one-screen-only as a test. Nope.
Because the program appears to perform correctly on other systems I thought the problem must be with my system. But I have no other pallete or tool bar issues with other apps in my "designer's toolbox" and specifically none with the other programs in the MX 2004 suite and anyway, Freehand isn't even painting it's own automatic new install/first-run opening screens correctly, a step so early in the first-run process that it's hard to believe anything significant already resident on my computer is mucking it up.
I have to think there's a snippet of code somewhere that Freehand (and apparently Freehand alone) references first thing when it starts up, and that snippet's corrupt. Needless to say, I haven't a clue about how to attack that. Would really appreciate help from any propeller head out there... and thanks in advance. I'll even tackle Registry changes without a backup first (gasp!) if I have to.
Jim