I have a strange problem.
I have an installer with a custom action dll (custom action type # 65).

In the past I've always compiled the .dll in ANSI and it worked fine on
English systems... it will only work on Japanese systems if I recompile it
in UNICODE, but then it will not work on German systems until I recompile it
as non-unicode. It works fine both ways on English.


Any one have any idea why this would be? Looking at the log file, it says
it's entering the custom action but nothing gets executed!

EP wrote:
> In the past I've always compiled the .dll in ANSI and it worked fine on
> English systems... it will only work on Japanese systems if I recompile it
> in UNICODE, but then it will not work on German systems until I recompile it
> as non-unicode. It works fine both ways on English.
>
>
> Any one have any idea why this would be?

My guess is that the German system is a W9x (e.g. Win98), whereas the
English system is NT+ (e.g. WinXP). Many of the Unicode APIs fail on
W9x.

Regards,
Martin

What in particular does your CA fail on?
When it try's to process a string with a c runtime function? When it
try's to display something?

actually, it ended up being that MFC71u.dll wasn't on the system.
It should have failed on the Japanese system also, except we had installed
studio on it so the dependency was already there. Now that I distribute
MFC71u.dll in the installer, the unicode version works on all systems.


"EP" <(E-Mail Removed)> wrote in message
news:eXw%(E-Mail Removed)...
> I have a strange problem.
> I have an installer with a custom action dll (custom action type # 65).
>
> In the past I've always compiled the .dll in ANSI and it worked fine on
> English systems... it will only work on Japanese systems if I recompile it
> in UNICODE, but then it will not work on German systems until I recompile
it
> as non-unicode. It works fine both ways on English.
>
>
> Any one have any idea why this would be? Looking at the log file, it says
> it's entering the custom action but nothing gets executed!
>
>