Problem in BIOS with NumLock -- Violates Windows XP License?

[Kruskal]

I just bought an R60 and noticed that when I had ToggleKeys set in Accessibility Options, NumLock (NumLk, Fn-ScrLk, Shift-ScrlLk) did not beep as did CapsLock and ScrollLock. So I ran a scan code reader and discovered that no scan code was emitted when NumLock was pressed.

This is in contrast to my previous ThinkPad, a T43, which did beep and emit a scan code to the scan code reader. (Another difference is that Fn-ScrLk does not work -- only Shift-ScrLk, as might be surmised by NumLk being white instead of blue on the R60.)

So it appears that the BIOS just quietly implements NumLock without operating system participation. A correct implementation, I assume, is to emit the scan code and have Windows turn around and tell the BIOS to set the NumLock flag.

This not only breaks the Accessibility Option but, also, any other remapping of NumLock. PowerPro, for example, will map NumLock and Tap-NumLock to other functions on my T43.

Seems to me that if the requirement for sticking that little Windows XP sticker on the R60 were written well enough, it would specify that NumLock must emit the scan code. I'm a little skeptical that enough care was taken when writing it. Anyone know more on this?

Arguing on the other side, for a minute, I note that "USB HID to PS/2 Scan Code Translation Table", http://download.microsoft.com/download/ ... nslate.pdf , does not give a PS/2 scan code for NumLock. So maybe Windows XP keyboards are NOT required to have the key at all. Although it SHOULD be required that, if they do, it be implemented so that the Accessibility Options work.

Any thoughts -- Vincent

[Kruskal]

Turns out there is a BIOS option to fix this problem: Config/Keyboard/NumLk = Independent/Syncronized. Independent is the default and Syncronized fixes it, although you'd never quess it from the description in the BIOS.

Moderator edit: No need to quote yourself