Getting Microsoft Office Keyboard to work on Windows 7 64 bit

Microsoft_Office_Keyboard
I have tried the AutoHotkey.exe program and did all of the set up stuff that everyone talks about and made a custom as was instructed by other users and even added the scroll and Zoom functions as stated by others

Located Here

; Microsoft Office Keyboard RT9450: Making the ScrollWheel work under Windows 7. ScrollUp/Down Normal, Fast, Faster, Fastest

sc10B Up::Send {WheelDown}
sc111 Up::Send {WheelDown 3}
sc112 Up::Send {WheelDown 5}
sc11F Up::Send {WheelDown 7}
sc10B Down::Send {WheelUp}
sc111 Down::Send {WheelUp 3}
sc112 Down::Send {WheelUp 5}
sc11F Down::Send {WheelUp 7}

Return

; makes control-scroll work for zooming

^sc10B Up::Send ^{WheelDown}
^sc111 Up::Send ^{WheelDown 3}
^sc112 Up::Send ^{WheelDown 5}
^sc11F Up::Send ^{WheelDown 7}
^sc10B Down::Send ^{WheelUp}
^sc111 Down::Send ^{WheelUp 3}
^sc112 Down::Send ^{WheelUp 5}
^sc11F Down::Send ^{WheelUp 7}

Return

but, my AHK file does not magically show the H icon as I was told it would. Seemingly because tehre is nothing writing to the regestry on my computer and the AutoHotkey.exe files is just that. A stand alone program.
I later tried the Compiler on the AHK websites and even made my own little nifty executable with the hot key and scroll wheel commands already in it.
ahkcustom
Nope no good.
I even created the shortcut and added it to the start/startup folder to make the file automatically run at start up. Still a big fail.

Also found another version of the same commands with a bit added to it

Located here

#Persistent ; Keeps a script permanently running (that is, until the user closes it or ExitApp is encountered).

#SingleInstance force ; Skips the dialog box and replaces the old instance of this script automatically
#NoEnv ; Recommended. Undefined variables (%xxxx%) do not cause a search of Environment variables.

sc10B Up::Send {WheelDown}
sc111 Up::Send {WheelDown 3}
sc112 Up::Send {WheelDown 5}
sc11F Up::Send {WheelDown 7}
sc10B Down::Send {WheelUp}
sc111 Down::Send {WheelUp 3}
sc112 Down::Send {WheelUp 5}
sc11F Down::Send {WheelUp 7}
; makes control-scroll work for zooming
^sc10B Up::Send ^{WheelDown}
^sc111 Up::Send ^{WheelDown 3}
^sc112 Up::Send ^{WheelDown 5}
^sc11F Up::Send ^{WheelDown 7}
^sc10B Down::Send ^{WheelUp}
^sc111 Down::Send ^{WheelUp 3}
^sc112 Down::Send ^{WheelUp 5}
^sc11F Down::Send ^{WheelUp 7}

sc164 Down:: ; My Pictures > no action (suppress error re installing Photo Editing software which sometimes occurs when using scrollwheel)
; Alt !
!sc164 Down::
; Ctrl ^
^sc164 Down::
; Shift +
+sc164 Down::
; Alt+Ctrl !^
!^sc164 Down::
; Alt+Shift !+
!+sc164 Down::
; Ctrl+Shift ^+
^+sc164 Down::
; Alt+Ctrl+Shift !^+
!^+sc164 Down::

sc105 Down::Run Explorer ; Files button which seems mapped to Messenger.

Again, no help

It took heavy use of Google for me to get every button functioning except scroll wheel.

The latest drivers helped tremendously minus wheel support as mention, except, when I open the intellitype pro software the tab for keyboard settings is greyed out. Says “No Microsoft usb keyboard detected”.

I found a few files..(one labled ITypeDevices.xml), but they list the supported devices. I am wondering if there is an edit to that which I could make to force the software to identify the driver just well enough so I can add settings for the scroll wheel.

settings

Inside the XML file stated above, I located commands for each type of keyboard and link from that to a folder for a shortcut to a bmp file. So I assume that when the computer identifies the office keyboard, it will want to show you a little image. I am sure any image we put there will work just fine.

I am scared to make this edit because there really is no telling how many files are actually associated to this XML, that will need to be updated along with this ITypeDevices.xml file.

If anyone has anything to add to this please please respond, there are many people who need this answer

7 thoughts on “Getting Microsoft Office Keyboard to work on Windows 7 64 bit”

  1. This is probably a useless endeavor as no one at Microsoft really cares that they have orphaned the Microsoft Office Keyboard for thousands of users. It is all well and good to say “buy a new keyboard” except no other keyboard offers these features. Many years ago micro innovations made a keyboard with these features, but that is gone and not supported either. Through an accident I lost my left index finger, which makes hitting CTRL+C and CTRL+V diificult. The Microsoft Office Keyboard greatly imporved my life. I own 9 of these keyboards. I use them at work in place of the compnay supplied keyboard because it improves my productivity. Will someone please read this and do something?

  2. The best I can do is make this post, and possibly request you pass this on with facebook and twitter.

    I have a spare one of these keyboards, in near mint condition. Spilled water on it just before I plugged it in my first time. Took it apart to dry out, and it never worked after that.
    Bought it brand new for $85 back in 2002/4(?not sure) Well back when compusa was a Goliath.
    So I hang on to it because I may need the spare parts as these gradually become harder to find.

    but I did get the scroll wheel to function using hotkey program, and the regular drivers on top of those weird drivers everyone is suggesting.

    Downside is you have to restart hotkey every now and again.. big deal, right clck and select “restart” no sweat.

    But yes share this link when you can.

  3. After following the instructions from Barcode (Thank you!) found here:
    http://www.sevenforums.com/microsoft-office/25553-driver-microsoft-office-keyboard.html
    and with a bit more poking around I have this working as intended on Windows 7 Professional 64-bit.

    The keyboard IS connected to the computer using a USB to PS/2 Adapter.

    I installed the 64-bit, 7.1 version of Intellitype Pro. Found here:
    http://www.microsoft.com/en-us/download/details.aspx?id=11105

    Saved the following script in Notepad and named it KbWheel.ahk :

    #Persistent ; Keeps a script permanently running (that is, until the user closes it or ExitApp is encountered).

    #SingleInstance force ; Skips the dialog box and replaces the old instance of this script automatically
    #NoEnv ; Recommended. Undefined variables (%xxxx%) do not cause a search of Environment variables.

    sc10B Up::Send {WheelDown}
    sc111 Up::Send {WheelDown 3}
    sc112 Up::Send {WheelDown 5}
    sc11F Up::Send {WheelDown 7}
    sc10B Down::Send {WheelUp}
    sc111 Down::Send {WheelUp 3}
    sc112 Down::Send {WheelUp 5}
    sc11F Down::Send {WheelUp 7}
    ; makes control-scroll work for zooming
    ^sc10B Up::Send ^{WheelDown}
    ^sc111 Up::Send ^{WheelDown 3}
    ^sc112 Up::Send ^{WheelDown 5}
    ^sc11F Up::Send ^{WheelDown 7}
    ^sc10B Down::Send ^{WheelUp}
    ^sc111 Down::Send ^{WheelUp 3}
    ^sc112 Down::Send ^{WheelUp 5}
    ^sc11F Down::Send ^{WheelUp 7}

    sc164 Down:: ; My Pictures > no action (suppress error re installing Photo Editing software which sometimes occurs when using scrollwheel)
    ; Alt !
    !sc164 Down::
    ; Ctrl ^
    ^sc164 Down::
    ; Shift +
    +sc164 Down::
    ; Alt+Ctrl !^
    !^sc164 Down::
    ; Alt+Shift !+
    !+sc164 Down::
    ; Ctrl+Shift ^+
    ^+sc164 Down::
    ; Alt+Ctrl+Shift !^+
    !^+sc164 Down::

    I then used the Autohotkey compiler “Convert .ahk to .exe” and pointed it at the KbWheel.ahk file created before.

    I used TASK SCHEDULER to trigger the launch of the file I named KBWheel.exe at user log on, delayed by 60 seconds. [Side note: It failed repeatedly to work for me using just a normal startup entry, however manual activation after initial log on always worked. If I’m honest about it, I lost interest in finding out why, since a 60 second delay fixed the problem and I’m using the wheel as I write this comment.]

    I hope this helps someone. 8)

  4. Awesome thanks for that.
    Great detail in the follow up .

    Considering how many people I see in a week looking for this
    Your comment will be great help to many people.

  5. Ho la tastiera RT9450 sto cercando un driver per W7.
    ci sono aggiornamenti?

  6. I’m looking for a keyboard RT9450 drivers for W7.
    There are updates?

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.