Authenticode problem

[trkrhelp]

One of the reasons for the V8 upgrade was to get the authenticode for my setup program, so I ran a small setup program for a update to test it and it worked fine. So then I did the build on my real program, which is a large build, 800mb on the high compression setting, and it doesn't work on that program. I'm trying to understand why it's not working with that build.
During the build it did kick up the password box twice, said succeeded after each time, but when I click properties for the setup.exe and check the digital signature is not there.

Any suggestions?

[jassing]

did you review the build logs?
Have you used chktrust on your exe? or tried to sign it again, manually?
What if you build it to a different filename/folder?

[trkrhelp]

I did try the different folder but that didn't work. Maybe I'll try the folder where the keys and signcode.exe live.

Have not tried chktrust, did try signing it manually but that didn't work either, but again that might be a path error, I'll test it in the home folder for the signcode and keys.

Thanks for the suggestions.

[jassing]

If signing it manually didn't work either; then it's not a SUF issue; it's a signtool issue.... (Sorry, I know that doesn't help)

I don't have any larger than CD projects here -- There may be a limitation on sign & size.

Doing a quick search with my friend Google (should be yours too) I found this, which seems to say you're "not alone".

[trkrhelp]

Thanks, I think that the note I read in your link about XP not showing properties correctly for files over 400 megs may be the issue. When I ran the cktrust - it doesn't squawk about the file so it is signed, XP just isn't showing that it's signed. I'll double check that tomorrow on a Vista machine.

Thanks for the tip.

[jassing]

I've seen OS's not report correctly when viewed in properties; but chktrust always reported "right"

The only thing I like about vista is it reports instantly if the file is signed..

[trkrhelp]

That was the problem - once in Vista is shows the digital signature

Thanks for getting me on the right track