This content has been marked as final. Show 4 replies
if I remember correctly, the way that a Director .exe is built does not like the kind of modifications that the Authenticode certificate makes... the same happens when you use those apps that will trim the size of .exe's by getting rid of all the overhead... I'm not sure how to get around it, but vaguely remember seeing a similar thread on the Direct-L listserve... I'll check it out for you.
You could try signing the projector skeleton prior to publishing your
executable - I don't know if it will work, but it's worth a try.
Find the file named "projec32.skl" in the root Director folder and sign
that (you may need to rename it to .exe to brand it and then back to
.skl before republishing)
Thanx for your quick answers!
I'm very glad that I'm not alone with this problem;-) Ok, I tried to sign the "projec32.skl" prior publishing and at first glance it seem to work beacause I could see the Digital Sign-Tab at the Property-dialogue of the file. But as I double-clicked the file under Vista i was told that this certificate isn't valid;-( I made a second try not renaming the projec32.skl into .exe but this didn't had any effect either!
It's very embarassing that Adobe had a TechNote for that ( http://kb.adobe.com/selfservice/viewContent.do?externalId=tn_19501&sliceId=2 but it seems that they only copy & pasted from the official Microsoft press release;-(((
@Chunick: Did you find this similar thread on the Direct-L listserver???