Application Gui OK on XP Pro but not WES

Question

I run a 3rd party application  - it's a device manager extension, when in device manager and right click then Properties, this vendor provided app runs which provides additional configuration and management for the underlying device - as well as the standard tabs that appear in a device manager properties dialog.

Problem is, runs just fine in XP, in WES some of the tabs are missing GUI elements, like strings / labels. I assume a missing component in my WES build, but when I check the dependencies of the app they are all present in the build.  It seems the only part of the GUI affected are those tabs specific to the device, not the tabs that appear in most every device manager properties dialog.

Running out of idea to debug, any suggestions?

Answer 1

Try adding the Fonts and Code Page Compatibility macro components. These two macro components should pull in the necessary support to adjust the strings.

-Sean

---

www.annabooks.com / www.seanliming.com / Book Author - Pro Guide to WES 7, XP Embedded Advanced, Pro Guide to POS for .NET

Answer 2

That is general issue on WES/XPE. Please check your registry on  follow of path.

Make your XPE/WES path the same with XP pro. Try it....  

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontMapper]
"ARIAL"=dword:00000000
"COURIER"=dword:00008800
"COURIER NEW"=dword:00008000
"FIXEDSYS"=dword:00009000
"MS SANS SERIF"=dword:00001000
"MS SERIF"=dword:00005000
"SMALL FONTS"=dword:00000800
"SYMBOL"=dword:00004002
"SYMBOL1"=dword:0000a002
"TIMES NEW ROMAN"=dword:00004000
"WINGDINGS"=dword:00000002
"WINGDINGS2"=dword:00008002
"細明體"=dword:00008088
"新細明體"=dword:00000088
"@細明體"=dword:0000a088
"@新細明體"=dword:00002088
"DEFAULT"=dword:00000088

Johnny

---

Johnny Blog: http://johnny0627.blogspot.tw/

Answer 3

I tried adding the fonts and Code Page Compatibility macro components but that did not help. I found a similar question posted and somebody experimentally found deleting an entry in the Font Compatibility section worked (see below). I tried it and it did solve the problem on 2 tabs of this particular application, a 3rd tab (with apparently the same font) still shows the problem. Must admit I don't know all the ramifications of removing this registry entry yet.

So still looking at this issue... the past response from Johnny I don't completely understand. I did compare those registry setting to XP PRO, very close by default but not exactly the same. Aside from those Asian looking entries (which I did not have in my WES build) the only difference was the DEFAULT value - which I set from 0 to 0x88 but that had no affect.

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\FontSubstitutes\MS Sans Serif,0