MaxCoderz

Basically the title says it all..
What's going on?

Which OS are you using? What software are you using? Have you installed whatever software is responsible for the COM object you're trying to sign apps with (I assume that's TI Flash Debugger).

I reinstalled the Flash Debugger just to be sure but it still doesn't work..
And I'm using LateNite to attempt to build the app (wappsign looks correctly setup, with the proper paths and all)

edit: oh and, running XP of course

Normal XP or 64-bit XP?

Hm 64bit, would that break it? I suppose it could..
edit: would it be fixed if I ran LateNite in 32bit mode?
edit2: no that didn't work..

It's a .NET app set to run on "any CPU", which wouldn't have any problems if it was a pure .NET app (it would run as 32-bit on 32-bit Windows, 64-bit on 64-bit Windows). However, it relies on a native COM object (32-bit), which can't be used when running under 64-bit Windows.

The correct solution would be to recompile all the .NET apps as requiring x86, not "any CPU". However, to fix it yourself, this post should help in the meantime.

Sorry for any inconvenience!

Edit: Bear in mind that Latenite runs Brass, so you'll need to "fix" Brass, not Latenite.

Oh I already did it the "hard" way (CFF Explorer, manually edited the flags)
But it didn't help - it's running as 32bit process but I still get the error

edit: doh didn't think of that, will fix brass now..

edit2: Ok we have a win!
thanks

I'll insert my recommendation for the Wabbit series of tools here in the meantime.

How would I set that up with latenite/brass? Just add it in the build file?

As in, use them instead of Latenite/Brass.

Can you call an external build step? Just have Brass generate a binary file, and sign it with wabbitsign using

Command Prompt wrote:wabbitsign program.bin program.8xk

Wabbitsign: http://www.revsoft.org/wabbitsign.zip