Driver for Microsoft Office Keyboard?

Hi BarCode,

I'm having a problem getting your script to load during boot.

I made the script (see above post) and placed a copy in the All programs > Startup folder. When I look in the hidden folders icon tray the icon is there. I select edit and the script appears to be correct, but I still have to click the original .ahk script icon located on my desktop to make the scroll button work. No bad but not ideal.

Suggestions as to what I'm doing wrong?

Thanks,
Kerry
Windows 7 Home Premium
AutoHotKey v1.0.48.05
Microsoft Office Keyboard (Model RT-9450) USB with PS/2 adapter
Mircosoft IntelliType Pro 7 (last version), > Wireless Desktop Elite Keyboard

I am having the same problem I have to rerun the script once Win 7 boots up to get the scroll wheel to work.

My MS Office keyboard left hand scroll wheel works fine (and sleep key works fine too) - but scroll wheel needs reload of the autohotkey script to enable it.

(run autohotkey is in the startup folder and scroll etc works correctly at powerup or restart).

Reload of autohotkey script is easy enough but tiresome. Any suggestions why? and/or what to do?

It there a /wakeup folder?

Hi I've also got the same problem, am using a Microsoft Keyboard Elite for Bluetooth upon which the scroll wheel doesn't work. I may be asking a stupid question, but Inotice a lot of you are talking about a USB keyboard with a scroll wheel, would the process detailed in the previous posts also work for a bluetooth keyboard? I'm running Windows 7 64 bit

Found this elegant fix for a windows 7 system running an old office keyboard which has been partially fubar due to no longer being supported - thank you microsaft
Took me less than 5 min to get it all working properly, so if you're listening - many many thanks. There's some reet clever buggers on this old net thingy.
Rob

After following the instructions from Barcode (Thank you!) found here:
Driver for Microsoft Office Keyboard?
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:
Download Microsoft IntelliType Pro 7.1 Keyboard Software for Windows - 64bit from Official Microsoft Download Center

Saved the following script (found here Getting Microsoft Office Keyboard to work on Windows 7 64 bit | TruXter Tech)
in Notepad and named it KbWheel.ahk :

Code:

#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.]

A great deal of thanks to those that contributed to making this workaround a reality!

I hope this helps someone. 8)