Fabien,
In addition, here is a Microsoft troubleshooting guide for wireless desktop:
http://support.microsoft.com/default.aspx/ph/8506
The guide may not fit your situation exactly, but perhaps it will provide
some idea on how to proceed.
Here is another troubleshooting guide:
http://support.microsoft.com/default.aspx/kb/258826
Problems such as you are having typically are caused by driver issues,
likely some incompatibility problems with the system. If updating drivers and
completing the indicated troubleshooting steps don't resolve your issues, try
contacting the official Microsoft Support. This forum is a user's group
comprised mostly of users who get together to help each other. While there
are experts that contribute information here, the official Microsoft Support
may have a different approach. Who knows.
--
freddy
"Fabien" wrote:
> Hi all,
>
> I've got a problem with my Dektop Elite keyboard and my inspiron 9300
> keyboard. This problem is not specificaly related to Vista, I also uncounter
> it under XP. I've also noticed this problem on other MS keyboards, so I
> nothing this is more a general problem.
>
> Here I go :
> 1. Plug a MS keyboard on an Inspiron 9300
> 2. Install Intellitype 6.1 (latest version available, but the problem
> existed on the older versions)
> 3. Once installed, use the Inspiron Fn keys.
>
> Here is what happened :
> For the general Fn Keys (mute, vol. up, vol down) it work flowlessy. But
> after pressing certain keys, the nightmare begin.
>
> Using the MsKey.exe tool, I've been able to see what's going on...
>
> Fn + F3 (Show battery) -> Intellitype interprete it as "redo"
> Fn + F8 (toggle screen) -> Zoom +
> Fn + F10 (Open CD Tray) -> Alt + Tab
> Fn + Down (Brightness down) -> Messenger key
>
> More problematic, after pressing the shortcut, the make event is well
> received by the MSKey.exe tool, but the break event is never called, so this
> mean the shortcut stay activ.
>
> I customized my commands.xml file so I could disable the Zoom + feature and
> disabled the messenger key, but my question is :
> Is MS aware of this problem, and is their something they could do to correct
> this incompatibility problem ?
>
>
> Regards
>
> --
> Fabien
>
>