Freehand MX conflict

from Stardock Forums
Hi! I've been a fan of Iconpackager for a long time and always recommended this software for the best icon customization results, but the main reason of this post is a less happier situation. Well, I'm running WindowsXP SP2 and always used IP 2.x without any conflict. But with the IP v3.00 and 3.10, a much better version, Freehand Mx fails to initialize. Probably neither Stardock or Macromedia (recently Adobe) can do anything about it wich is sad, but if any of you guys could drop me something I would apreciate it. :) The freehand update didn't solve it. Check this: http://www.macromedia.com/cfusion/webforums/forum/messageview.cfm?catid=199&threadid=1019457&enterthread=y
1,656 views 4 replies
Reply #1 from WinCustomize Forums Top
Hello!
It seams incredible how no one take the time to answer to this issue.
I'm having the same problem and can't find a solution anywhere!
If you (or anyone) have found a way to fix this would you please post it here?
Thanks
Reply #2 from WinCustomize Forums Top
Hi!
Nothing until now! I must say I've stopped finding an answer to this. Right now, when I need to use freehand (when illustrator doesn't do the trick) I log on to a different windows account wich doesn't have the iconpackager installed. As you say, it seams incredible no one had an answer. Maybe an email to stardock or adobe, I don't know...
if you find something post it here please and I'll do the same!
Thanks!
CursorFX - Customize your Windows cursor
Reply #3 from Stardock Forums Top
Tis possible your posts slipped down during flurries of activity and did not get seen. Tis also possible no one has an answer.

My first thought on 'failing to initialize' is - are you also running WindowBlinds?

If so, add Freehand to the per application in WB configuration to be excluded from skinning.
Reply #4 from WinCustomize Forums Top
It seams incredible how no one take the time to answer to this issue.


Tis possible your posts slipped down during flurries of activity and did not get seen.


Bichur's probably correct. If you would like imediate assistance, I highly suggest contacting [email protected].

This may be a problem they, as of now still know nothing about. Or maybe they do and are working on a solution. Maybe there is no solution. In either case, I'm certain SD support would give you an answer...maybe even a solution.

Remember when e-mailing to give as much info as possible.