Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Only First Caption Character Is Shown Under NT4

4 views
Skip to first unread message

Gregory Nisnevich

unread,
Nov 25, 2003, 1:18:24 AM11/25/03
to
Here's a strange one: if my MFC (statically linked) project is linked with
Unicows (following the instructions in MSDN), only under NT4 the caption
shows just the first character (I use SetWindowText in UNICODE build). If I
link without Unicows, the full caption is shown. This happens only to the main
SDI window.

Another strange thing: in Unicows build Spy++ shows (Unicode) for
the main window (the one with the wrong title), but for non-Unicows build it
shows (Unicode)(Subclassed) as it does for all other windows in the
application (for both builds).

Also, Depends shows that Unicows build is missing OLEDLG.DLL and VERSION.DLL
(I don't know if it's important, just another bit of information).

Thanks for any clues,

-Gregnory Nisnevich

Ted

unread,
Nov 25, 2003, 2:01:05 AM11/25/03
to
That's really odd, because Unicows.dll is not supposed to come into play at
all on NT based platforms. You can check this by running profile in
depends.exe, the unicows.dll should not get loaded at all. If you do
nothing else but remove unicows.lib from your linker settings, do you still
see the problem?

Ted.

"Gregory Nisnevich" <gre...@yahoo.com> wrote in message
news:862b70fe.03112...@posting.google.com...

Gregory Nisnevich

unread,
Nov 25, 2003, 3:31:29 PM11/25/03
to
I found the problem: I was using VMWare's Shared Folders, and that's what
messed thing up. If I copy the exe file to VMWare's local folder, all
looks fine. Still, it's kinda odd that non-MSLU build was not affected, and
then those strange differences in Spy++ and Depends.

Thanks,
-Gregory Nisnevich

"Ted" <t...@t--x.org> wrote in message news:<OalB2Gys...@TK2MSFTNGP10.phx.gbl>...

Michael (michka) Kaplan [MS]

unread,
Nov 26, 2003, 10:41:01 PM11/26/03
to
While the code in unicows.dll is not run when you are on NT 4 (try removing
the file if you do not believe me!), the code in the MSLU loader will always
run. It simply decides to call the NT version of the "W" functions. It is
entirely possible for functionality that attempts to hook function procs and
other weird stuff like that to cause problems in such a case, especially if
no one has ever tested their interaction before....


--
MichKa [MS]
NLS Collation/Locale/Keyboard Development
Globalization Infrastructure and Font Technologies

This posting is provided "AS IS" with
no warranties, and confers no rights.


"Gregory Nisnevich" <gre...@yahoo.com> wrote in message

news:862b70fe.0311...@posting.google.com...

0 new messages