-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Jordan, <<A bit of a chore, admittedly, but what I would probably do in this situation is take one of the old Kbd Map templates and modify it (since I can't "draw" worth a damn !) with the newly verified scancodes for your model. If anyone else does this, I'd suggest these could make worthy uploads to Brian's site, particularly if we got a decent representation of more recent models. A list of scancodes included would be good too. Within a general line -- e.g., Asus EEE, Acer Aspire -- these would probably be consistent.>> Not a bad idea. Shall we poll the keyboards out there amongst us? That is exactly what I did for my Cherry keyboard. Keycode.exe returned no code for some keys (such as print-screen), and returned numbers in the 300 range which made no sense to me or to Xy for some keys (for example, 325 for num-lock) but enough keys were correctly identified to allow me to modify my kbd file to suit my needs. <MD FL> -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (MingW32) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAktTdTwACgkQHrcIRRZeloFkWQCfWC8gMa1qjbkTxQGUu3yYLjd8 E2gAn3CV80abD1bCoNl8XRia3W7VBujn =WfJS -----END PGP SIGNATURE-----