D
Dave Liddell
I'm having the same problem with IE6 (all patches
installed as of today) on XP SP1.
I have four accounts set up: two are administrator
accounts, and two are restricted user accounts. Only the
account from which I installed all patches seems to work
correctly. The others have the keyboard problem you
mentioned, including the restricted account that I just
set up from scratch.
Some additional information I can add... the problem
appeared sometime within the last two months. I suspect
one of the patches, since we've always used IE6. I
searched through the registry to see if perhaps a patch
updated something for the current user but not for all
users, but found nothing of interest.
The one patch which was installed roughly around the time
the problem started, and which installed files having to
do with the browser is KB823559. I haven't tried rolling
it back since it's a security patch. (I'm hoping for a
better alternative!)
Also, I tried a number of different languages. Only
languages for which the character set is on a unicode
page higher than 00 has problems. This leads me to
believe that the top byte of a unicode word is being
chopped off: for example, instead of displaying a
Russian "a", which is character U+0430, it comes out as
a "0", or U+0030. Languages which use an IME, such as
Japanese, don't seem to have this problem.
- Dave
installed as of today) on XP SP1.
I have four accounts set up: two are administrator
accounts, and two are restricted user accounts. Only the
account from which I installed all patches seems to work
correctly. The others have the keyboard problem you
mentioned, including the restricted account that I just
set up from scratch.
Some additional information I can add... the problem
appeared sometime within the last two months. I suspect
one of the patches, since we've always used IE6. I
searched through the registry to see if perhaps a patch
updated something for the current user but not for all
users, but found nothing of interest.
The one patch which was installed roughly around the time
the problem started, and which installed files having to
do with the browser is KB823559. I haven't tried rolling
it back since it's a security patch. (I'm hoping for a
better alternative!)
Also, I tried a number of different languages. Only
languages for which the character set is on a unicode
page higher than 00 has problems. This leads me to
believe that the top byte of a unicode word is being
chopped off: for example, instead of displaying a
Russian "a", which is character U+0430, it comes out as
a "0", or U+0030. Languages which use an IME, such as
Japanese, don't seem to have this problem.
- Dave
