Subject: Re: ToUnicodeEx function not supported on Win95
From: Andrew Dunbar (hippietrail@yahoo.com)
Date: Wed Jun 13 2001 - 22:04:16 CDT
Saint-Denis wrote:
>
> I have Win95 french edition, with locale and keybord set to french canadian.
> I also tried changing the keybord to US and it did not changed anything.
>
> The problem shows itself at the very initialization of AbiWord. It is even
> before the AP_Win32App::WinMain function in the Win32Main.cpp. I tried
> setting a break point on that function, but the problem show up before that.
>
> The symptoms are:
> A french message box with label that I translate to "Error during program
> startup", and content of the message is translated to "The ABIWORD.EXE file
> is linked to a missing export USER32.DLL:ToUnicodeEx.".
> There is also another message box labelled
> "c:\Abisource\abi\src\WIN32_1.1.7_i386_DBG\bin\AbiWord.exe". It's content
> start also with the file name followed by the text "A system attached
> peripheral does not function properly" in french.
>
> I think, the french text is an indication that the problem is detected by
> the inner working of windows.
>
> The VisualC++ compiler documentation for ToUnicodeEx says the function is
> supported on Windows NT but not on Win95 nor Win32.
>
> I hope it brings some light...
> Gilles
Thanks very much Gilles. It sheds a lot of light. It sounds to me that
this is a dynamic linking error? We could #ifdef out the call for Win
95 builds but this would mean two Windows builds. I need someone who
is more expert than I in this field of Windows. Should we "look up" the
entry to this function to call it?
I think this should be a high-priority bug now.
> > > Saint-Denis wrote:
> > >
> > > Unfortunatly the "ToUnicodeEx" function used in file
> > > ev_Win32Keyboard.cpp is not supported on Win95. The compiler and
> > > linker do not complain, but AbiWord stop at runtime because this
> > > function is missing from user32.dll.
> > >
> > > I do not know the purpose for that function insertion in the code, but
> > > it's use could be made WinNT/Win95 dependent by checking which OS is
> > > running.
> >
> > Can you give more details? That function should only be called
> > when you're using a Unicode locale - Win95 does not have Unicode
> > locales. I can only test with Windows 98 where there seems to be
> > no such problem. What locale are you using? What keyboard layout?
> > What error do you see? Is it with any keypress or just certain
> > keys?
> >
> > Andrew Dunbar.
-- http://linguaphile.sourceforge.net _________________________________________________________ Do You Yahoo!? Get your free @yahoo.com address at http://mail.yahoo.com
This archive was generated by hypermail 2b25 : Wed Jun 13 2001 - 22:01:46 CDT