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

MSKLC: Load Existing Keyboard

796 views
Skip to first unread message

olgt-...@comcast.net

unread,
Feb 28, 2007, 4:20:18 PM2/28/07
to
Greetings to all -

I've just got Vista installed on one of the machines. Thanks to Paul
Gorodyansky instructions at http://RusWin.net I've been able to
install the "Phonetic Russian layout". It all worked like a charm.

However when I've tried to use MSKLC 1.4 to modify it I've got an
issue. I can not load any existing keyboard inside of MSKLC. When I
use "Load Existing Keyboard" and pick any one from the list the
keyboard layout is not displayed. However If I try to "validate" the
keyborad layout loaded or see it properties it appears to point to the
right one.

I've tried searching the newgroups but could not find any posts
describing similar issues. Any suggestion is greatly appreciated.

Thanks
Pavel

Michael S. Kaplan [MSFT]

unread,
Mar 1, 2007, 5:17:44 AM3/1/07
to
I am not seeing this problem. Can you give more info on what is happening
and what your settings are?

If you click on one of the keys, do you see characters in the dialog that
pops up? If you hover over one, does the tooltip list what is in the key?


--
MichKa [Microsoft]
NLS Collation/Locale/Keyboard Technical Lead
Globalization Infrastructure, Fonts, and Tools
Blog: http://blogs.msdn.com/michkap

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

<olgt-...@comcast.net> wrote in message
news:1172697618.9...@k78g2000cwa.googlegroups.com...

olgt-...@comcast.net

unread,
Mar 1, 2007, 7:33:32 PM3/1/07
to
On Mar 1, 4:17 am, "Michael S. Kaplan [MSFT]"

<mic...@online.microsoft.com> wrote:
> I am not seeing this problem. Can you give more info on what is happening
> and what your settings are?
>
> If you click on one of the keys, do you see characters in the dialog that
> pops up? If you hover over one, does the tooltip list what is in the key?
>
> --
> MichKa [Microsoft]
> NLS Collation/Locale/Keyboard Technical Lead
> Globalization Infrastructure, Fonts, and Tools
> Blog:http://blogs.msdn.com/michkap
>
> This posting is provided "AS IS" with
> no warranties, and confers no rights.
>
> <olgt-nos...@comcast.net> wrote in message

>
> news:1172697618.9...@k78g2000cwa.googlegroups.com...
>
> > Greetings to all -
>
> > I've just got Vista installed on one of the machines. Thanks to Paul
> > Gorodyansky instructions athttp://RusWin.net I've been able to

> > install the "Phonetic Russian layout". It all worked like a charm.
>
> > However when I've tried to use MSKLC 1.4 to modify it I've got an
> > issue. I can not load any existing keyboard inside of MSKLC. When I
> > use "Load Existing Keyboard" and pick any one from the list the
> > keyboard layout is not displayed. However If I try to "validate" the
> > keyborad layout loaded or see it properties it appears to point to the
> > right one.
>
> > I've tried searching the newgroups but could not find any posts
> > describing similar issues. Any suggestion is greatly appreciated.
>
> > Thanks
> > Pavel

Ok. Here are the details. When I start msklc it comes up with an empty
keyboard layout. Here is a screen shot: http://pvlf.home.comcast.net/pictures/msklc/msklc.init.jpg.
Then I load any keyboard layout via "Load Existing Keyboard". The
screen of msklc stays the same: http://pvlf.home.comcast.net/pictures/msklc/msklc.init.jpg.
No error messages are reported. However if I try to validate the
layout I see the proper layout loaded:
http://pvlf.home.comcast.net/pictures/msklc/msklc.project.props.jpg. I
have this issue regardless of the layout I try to load: I never saw
actual keys displayed.

I'm running Vista Home Basic which came pre-installed with the laptop
from Dell. I did try to install .Net 2 but got a message that it was
already installed on my machine. I've looked at the "Turn windows
features" and noticed .Net 3.0 there. At the time only XPS Viewer was
checked. I've unchecked the whole .Net and tried to run msklc after
that. My expectation was that it would not even run since it
required .Net 2.0. However I've not seen any difference in the
behavior. Here is my current settings for "Turn windows features":
http://pvlf.home.comcast.net/pictures/msklc/windows.features.jpg.

Do you think it's related to .Net 3.0 pre-installed instead of .Net
2.0 required by msklc? Any other ideas?

This is my first experience with Vista and I'm trying hard to like
it :-)

Thanks for your help in advance.
Pavel

Michael S. Kaplan [MSFT]

unread,
Mar 3, 2007, 12:04:49 AM3/3/07
to
I have never installed the .NET Framework on a Vista machine for MSKLC 1.4 -
the built-in one is always what I have used. And .NET 3.0 is .NET 2.0 plus
some extras components. :-)

For settings, I was thinking about resolution, DPI, monitor/driver, theme,
aero status, etc....

I cannot repro here and it has never been reported before, so I would very
much like to understand what is happening here.


--
MichKa [Microsoft]
NLS Collation/Locale/Keyboard Technical Lead
Globalization Infrastructure, Fonts, and Tools
Blog: http://blogs.msdn.com/michkap

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

<olgt-...@comcast.net> wrote in message
news:1172795612....@v33g2000cwv.googlegroups.com...

olgt-...@comcast.net

unread,
Mar 3, 2007, 3:34:27 PM3/3/07
to
On Mar 2, 11:04 pm, "Michael S. Kaplan [MSFT]"

<mic...@online.microsoft.com> wrote:
> I have never installed the .NET Framework on a Vista machine for MSKLC 1.4 -
> the built-in one is always what I have used. And .NET 3.0 is .NET 2.0 plus
> some extras components. :-)
>
> For settings, I was thinking about resolution, DPI, monitor/driver, theme,
> aero status, etc....
>
> I cannot repro here and it has never been reported before, so I would very
> much like to understand what is happening here.
>
> --
> MichKa [Microsoft]
> NLS Collation/Locale/Keyboard Technical Lead
> Globalization Infrastructure, Fonts, and Tools
> Blog:http://blogs.msdn.com/michkap
>
> This posting is provided "AS IS" with
> no warranties, and confers no rights.
>
> <olgt-nos...@comcast.net> wrote in message
>
> news:1172795612....@v33g2000cwv.googlegroups.com...
>
> > On Mar 1, 4:17 am, "Michael S. Kaplan [MSFT]"
> > <mic...@online.microsoft.com> wrote:
> >> I am not seeing this problem. Can you give more info on what is happening
> >> and what your settings are?
>
> >> If you click on one of the keys, do you see characters in the dialog that
> >> pops up? If you hover over one, does the tooltip list what is in the key?
>
> >> --
> >> MichKa [Microsoft]
> >> NLS Collation/Locale/Keyboard Technical Lead
> >> Globalization Infrastructure, Fonts, and Tools
> >> Blog:http://blogs.msdn.com/michkap
>
> >> This posting is provided "AS IS" with
> >> no warranties, and confers no rights.
>
> >> <olgt-nos...@comcast.net> wrote in message
>
> >>news:1172697618.9...@k78g2000cwa.googlegroups.com...
>
> >> > Greetings to all -
>
> >> > I've just got Vista installed on one of the machines. Thanks to Paul
> >> > Gorodyansky instructions athttp://RusWin.netI've been able to

Resolution: 1680x1050, Color 32 Bpp
DPI: 120
Monitor: LCD Panel 15.4 inch UltraSharp™ Wide Screen SXGA+ Display
with TrueLife™
Driver: ATI MOBILITY™ RADEON® X1400 (no conflicts)
Theme: Windows Classic
Color schema: Windows Standard
Dell Laptop: Inspiron 6400 Dual Core
OS: Genuine Windows Vista™ Home Basic
Aero is not available in Genuine Windows Vista™ Home Basic
If you want me to get a log of all of the settings from my system and
send it to you pls let me know how I could do that (batch file,
command, etc)

Paul Gorodyansky

unread,
Mar 4, 2007, 10:25:49 PM3/4/07
to
"Michael S. Kaplan [MSFT]" wrote:
>
>
> I cannot repro here and it has never been reported before, so I would very
> much like to understand what is happening here.

For me its also worked just fine (did not touch Vista - it already
has .NET 2.0 - just ran MSKLC) - I made an instructional page at
http://ourworld.compuserve.com/homepages/paulgor/mod_e.htm#XP
only after I tried the modificationn myself :-)

So it looks like there is something wrong with Pavel's machine...

I can do modifications for him if it's a handful of them :-) -


--
Regards,
Paul Gorodyansky
"Cyrillic (Russian): instructions for Windows and Internet":
http://RusWin.net
Russian On-screen Keyboard: http://Kbd.RusWin.net

olgt-...@comcast.net

unread,
Mar 5, 2007, 5:42:58 PM3/5/07
to
On Mar 4, 9:25 pm, Paul Gorodyansky <paul...@compuserve.com> wrote:
> "Michael S. Kaplan [MSFT]" wrote:
>
>
>
> > I cannot repro here and it has never been reported before, so I would very
> > much like to understand what is happening here.
>
> For me its also worked just fine (did not touch Vista - it already
> has .NET 2.0 - just ran MSKLC) - I made an instructional page athttp://ourworld.compuserve.com/homepages/paulgor/mod_e.htm#XP

> only after I tried the modificationn myself :-)
>
> So it looks like there is something wrong withPavel'smachine...
>
> I can do modifications for him if it's a handful of them :-) -
>
> --
> Regards,
> Paul Gorodyansky
> "Cyrillic (Russian): instructions for Windows and Internet":
> http://RusWin.net
> Russian On-screen Keyboard:http://Kbd.RusWin.net

As I mentioned before I have .Net 3 (not .Net 2) installed as part of
Windows Vista™ Home Basic. Did you guys try it under Vista™ Home Basic
or Vista Pro? Maybe there is a difference there.

Is there any log that MSKLC writes the info/debug/error messages to?
Is it possible to get a build of MSKLC with debug/trace enabled?
I should not be the only one who is having this issue. But I just
might be the first one who bought Dell's laptop with Vista Home Basic
and tried to run MSKLC on it :-)

Any other ideas?

Paul Gorodyansky

unread,
Mar 5, 2007, 9:22:28 PM3/5/07
to
olgt-...@comcast.net wrote:
>
>
> As I mentioned before I have .Net 3 (not .Net 2) installed as part of
> Windows Vista Home Basic. Did you guys try it under Vista Home Basic
> or Vista Pro? Maybe there is a difference there.

I looked at the machine I used - it is Vista Ultimate (32-bit)

Michael S. Kaplan [MSFT]

unread,
Mar 6, 2007, 12:09:30 PM3/6/07
to
.NET 3.0 *is* .NET 2.0 plus some extra unrelated bits that MSKLC does not
use.

--
MichKa [Microsoft]
NLS Collation/Locale/Keyboard Technical Lead
Globalization Infrastructure, Fonts, and Tools
Blog: http://blogs.msdn.com/michkap

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


<olgt-...@comcast.net> wrote in message
news:1173134578.8...@30g2000cwc.googlegroups.com...


On Mar 4, 9:25 pm, Paul Gorodyansky <paul...@compuserve.com> wrote:
> "Michael S. Kaplan [MSFT]" wrote:
>
>
>
> > I cannot repro here and it has never been reported before, so I would
> > very
> > much like to understand what is happening here.
>
> For me its also worked just fine (did not touch Vista - it already
> has .NET 2.0 - just ran MSKLC) - I made an instructional page
> athttp://ourworld.compuserve.com/homepages/paulgor/mod_e.htm#XP
> only after I tried the modificationn myself :-)
>
> So it looks like there is something wrong withPavel'smachine...
>
> I can do modifications for him if it's a handful of them :-) -
>
> --
> Regards,
> Paul Gorodyansky
> "Cyrillic (Russian): instructions for Windows and Internet":
> http://RusWin.net
> Russian On-screen Keyboard:http://Kbd.RusWin.net

As I mentioned before I have .Net 3 (not .Net 2) installed as part of

Windows VistaT Home Basic. Did you guys try it under VistaT Home Basic

Michael Kaplan [MSFT]

unread,
Mar 6, 2007, 2:42:53 PM3/6/07
to
This has been confirmed as a bug in MSKLC in some high-DPI scenarios. The
only workaround is run at a lower DPI.

Sorry about that. :-(


--
MichKa [Microsoft]
NLS Collation/Locale/Keyboard Technical Lead
Globalization Infrastructure, Fonts, and Tools
Blog: http://blogs.msdn.com/michkap

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


<olgt-...@comcast.net> wrote in message
news:1173134578.8...@30g2000cwc.googlegroups.com...


On Mar 4, 9:25 pm, Paul Gorodyansky <paul...@compuserve.com> wrote:
> "Michael S. Kaplan [MSFT]" wrote:
>
>
>
> > I cannot repro here and it has never been reported before, so I would
> > very
> > much like to understand what is happening here.
>
> For me its also worked just fine (did not touch Vista - it already
> has .NET 2.0 - just ran MSKLC) - I made an instructional page
> athttp://ourworld.compuserve.com/homepages/paulgor/mod_e.htm#XP
> only after I tried the modificationn myself :-)
>
> So it looks like there is something wrong withPavel'smachine...
>
> I can do modifications for him if it's a handful of them :-) -
>
> --
> Regards,
> Paul Gorodyansky
> "Cyrillic (Russian): instructions for Windows and Internet":
> http://RusWin.net
> Russian On-screen Keyboard:http://Kbd.RusWin.net

As I mentioned before I have .Net 3 (not .Net 2) installed as part of

Windows VistaT Home Basic. Did you guys try it under VistaT Home Basic

Michael Kaplan [MSFT]

unread,
Mar 9, 2007, 1:48:31 PM3/9/07
to
Ok, I found another workaround....

If you run at a higher DPI than 120 (I tested with 134, for example), it
also works around the problem.

120dpi is still the default for many newer machines so this is still a
bug.... but at least there is another workaround....


--
MichKa [Microsoft]
NLS Collation/Locale/Keyboard Technical Lead
Globalization Infrastructure, Fonts, and Tools
Blog: http://blogs.msdn.com/michkap

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


"Michael Kaplan [MSFT]" <mic...@online.microsoft.com> wrote in message
news:eIKfFeCY...@TK2MSFTNGP03.phx.gbl...

olgt-...@comcast.net

unread,
Mar 9, 2007, 2:57:28 PM3/9/07
to pau...@compuserve.com
On Mar 9, 12:48 pm, "Michael Kaplan [MSFT]"

<mich...@online.microsoft.com> wrote:
> Ok, I found another workaround....
>
> If you run at a higher DPI than 120 (I tested with 134, for example), it
> also works around the problem.
>
> 120dpi is still the default for many newer machines so this is still a
> bug.... but at least there is another workaround....
>
> --
> MichKa [Microsoft]
> NLS Collation/Locale/Keyboard Technical Lead
> Globalization Infrastructure, Fonts, and Tools
> Blog:http://blogs.msdn.com/michkap
>
> This posting is provided "AS IS" with
> no warranties, and confers no rights.
>
> "Michael Kaplan [MSFT]" <mich...@online.microsoft.com> wrote in messagenews:eIKfFeCY...@TK2MSFTNGP03.phx.gbl...

>
> > This has been confirmed as a bug in MSKLC in some high-DPI scenarios. The
> > only workaround is run at a lower DPI.
>
> > Sorry about that. :-(
>
> > --
> > MichKa [Microsoft]
> > NLS Collation/Locale/Keyboard Technical Lead
> > Globalization Infrastructure, Fonts, and Tools
> > Blog:http://blogs.msdn.com/michkap
>
> > This posting is provided "AS IS" with
> > no warranties, and confers no rights.
>
> > <olgt-nos...@comcast.net> wrote in message

Thank you Michael. I'll try either standard 96 or 134 DPI values out.
Paul, you might consider adding this to your instructions at http://RusWin.net
(which are extremely helpful by the way)

Paul Gorodyansky

unread,
Mar 9, 2007, 4:37:57 PM3/9/07
to
olgt-...@comcast.net wrote:
>
>
> Thank you Michael. I'll try either standard 96 or 134 DPI values out.
> Paul, you might consider adding this to your instructions at http://RusWin.net
> (which are extremely helpful by the way)

Yes, I'll do that

0 new messages