Jump to content

Apple Keyboard driver for Windows


  • Please log in to reply
118 replies to this topic

#61
Bergdoktor

Bergdoktor

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 4 posts
got my wireless keyboard yesterday (yaay) and got it up and running in no time. I used "my" drivers and tried my repacked 3.1 Bootcamp64.msi . everything went well, but after restarting I noticed the volume control keys (F10-F12) weren't working (everything else was). So I tried installing M4xim's Bootcamp64.msi from 3.0 which gave me an error (code 2753) and cancelled the installation.
After uninstalling my Bootcamp 3.1 installation from Windows "Program and Features" followed by a reboot I could install M4xim's BootCamp64.msi without error. After another restart the volume keys (together with the MacOS-que OSD) were working perfectly and there was a new tray icon present from bootcamp. I then proceeded to check whether my 3.1 Bootcamp64.msi did anything at all and during install for the first time I was prompted to stop (or let it stop them automatically) some programs running in the background - two services called "Apple Time Service" and "Apple OS Switch Manager" and BootCamp.exe which, as somebody pointed out already, gets started at windows startup. I let it do it's job and the installation completed afterwards followed with another prompt for reboot. After that all the keys were still working, and the tray icon was still there. To verify if any changes occurred from the 3.1 installation I checked the properties of some of the files that I knew were supposed to be "installed" in their respective folders by my selfmade .msi and they sure have a newer timestamp (01 Feb 2010 compared to 22 July 2009 before) and different file versions.
(check the following example screenshot taken of Bootcamp.exe):
Posted Image
This leads me to think my 3.1 installer works only after installing 3.0 first. Whether it actually makes a "real world" difference to update to 3.1 solely for the purpose of getting Apple Keyboards working flawlessly in Windows I can't tell.
When I tried to access the Bootcamp Control Panel (right click on the tray icon) it gave me an error ("An error occurred while trying to access the startup disk settings. You may not have privileges to change the startup disk. Make sure you have administrative privileges and try again") even though I have admin privileges on my account. so my guess is it's checking for a Mac OS partition which isn't there what triggers the (a bit misleading) error msg. So my guess was it didn't do anything useful but when I ended the Bootcamp.exe process via Task Manager I noticed the volume control keys weren't working any more (no OSD either). Manually restarting Bootcamp.exe from the install-folder (c:\program files\Boot Camp\) made them work again. To me it seems the only thing it's doing in my case is enable the volume keys (+OSD), so the older versions should probably do the job just as well. In turn it shouldn't do any harm either having them up to date. Maybe somebody else could investigate further on the changes between 3.1 and 3.0, for example somebody with Mac OS X installed on the startup partition.
Ultimately I decided to disable "Apple Time Service" and "Apple OS Switch Manager" via services.msc (don't need them because I don't have Mac OS on my native windows 7 x64 pc) and leave Bootcamp.exe in Startup checked in msconfig.
I'll continue to try a few things to see if there's another component/.exe/whatever of the bootcamp-package responsible for handling the function of the volume keys as bootcamp.exe seems to delay boot a bit and doesn't offer any additional functionality (e.g. through it's tray icon) for me.
Regarding the "updated" Keyboard drivers from Bootcamp 3.1 I had another interesting find: Windows Device Manager doesn't indicate any difference between using any of them two. Check the following screenshot which also shows that apparently KeyMagic.sys is the same :
Posted Image

Comparing KeyMagic64.inf from 3.0 to 3.1 the only difference I found were the following 3 added lines (at line 111-113) in 3.1' Keyboard64.inf in the Bluetooth keyboards section
%USBKeyboard.DevDesc%=Dri_BTH_Inst,BTHENUM\{00001124-0000-1000-8000-00805f9b34fb}_VID&000205ac_PID&0239
 %USBKeyboard.DevDesc%=Dri_BTH_Inst,BTHENUM\{00001124-0000-1000-8000-00805f9b34fb}_VID&000205ac_PID&023A
 %USBKeyboard.DevDesc%=Dri_BTH_Inst,BTHENUM\{00001124-0000-1000-8000-00805f9b34fb}_VID&000205ac_PID&023B
I'm using an Apple Wireless Keyboard (2 batteries) and in the device manager it tells me it has the PID 023a (see screenshot below on where to look for it yourself:)

Posted Image

Those lines mean added driver support in 3.1 for three additional devices - probably all of them bluetooth keyboards - but I couldn't find any info about the other two devices when googling for the PIDs specified above (0239, 023B). Maybe other people can contribute by posting their hardware-ids to see if we can get more info on this subject.
Anyway, this post is getting pretty long (and took me pretty long since I'm not a native speaker and finding the right words for my thoughts without repeating the same phrases over and over can be tiresome) so I'll leave it for now and report back when I find something new - especially related to needing bootcamp.exe running in the background for the volume keys to work.

#62
poohlo

poohlo

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 1 posts
After many hours of research , just want to post it in one place:
it attachment drivers for Apple Aluminium Wired Keyboard both for Win7 x64 and x86 enjoy!

Attached Files



#63
pangxs86

pangxs86

    InsanelyMac Protégé

  • Members
  • Pip
  • 5 posts

After many hours of research , just want to post it in one place:
it attachment drivers for Apple Aluminium Wired Keyboard both for Win7 x64 and x86 enjoy!


You mean I just install those and that's it ? How can i use the volume buttons and eject buttons ? Thanks..

#64
Bergdoktor

Bergdoktor

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 4 posts
poohlo's files (the x64 one) seem to be the same as those from the Bootcamp 3.1 Update installer I posted 1 page back attached to my first post. Timestamp is 2 weeks earlier (mid-january compared to 1st february), but besides that they look the same. I also checked for the additional 3 entries in the KeyMagic64.inf under bluetooth keyboards and they are present in poohlo's version. I didn't provide a repack of the x86-version so if you're running 32bit windows get poohlo's "installer". they contain an installer for the drivers (DPinst.exe) but the .exe is just another way of packing them in an self-extracting archive.
As I pointed out you still need the BootCamp software to get the volume keys working with OSD. Get M4xim's Bootcamp64.msi from Bootcamp 3.0 to get them working and do the update to 3.1 with my Bootcamp64 3_1.msi if you feel like it (<- don't know about the advantages yet).

#65
pangxs86

pangxs86

    InsanelyMac Protégé

  • Members
  • Pip
  • 5 posts

poohlo's files (the x64 one) seem to be the same as those from the Bootcamp 3.1 Update installer I posted 1 page back attached to my first post. Timestamp is 2 weeks earlier (mid-january compared to 1st february), but besides that they look the same. I also checked for the additional 3 entries in the KeyMagic64.inf under bluetooth keyboards and they are present in poohlo's version. I didn't provide a repack of the x86-version so if you're running 32bit windows get poohlo's "installer". they contain an installer for the drivers (DPinst.exe) but the .exe is just another way of packing them in an self-extracting archive.
As I pointed out you still need the BootCamp software to get the volume keys working with OSD. Get M4xim's Bootcamp64.msi from Bootcamp 3.0 to get them working and do the update to 3.1 with my Bootcamp64 3_1.msi if you feel like it (<- don't know about the advantages yet).


Issue is that I am using 32bit so i need Bootcamp86 instead

#66
rsmith4321

rsmith4321

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 2 posts
I'm trying to use an Apple bluetooth keyboard in Windows 7 64bit. If anyone could send me the latest boot camp drivers I would greatly appreciate it. I don't know why Apple doesn't make this freely available. Thanks.

#67
Bergdoktor

Bergdoktor

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 4 posts
rsmith4321: look 4 posts above yours for poohlo's (post #62) or 1 page back for my post (#59) with the most recent drivers attached. to get the volume keys working you also need the bootcamp64 .msi package from Bootcamp3.0, for example from M4xim's post a few pages back (#34) or my post (#59).

#68
rsmith4321

rsmith4321

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 2 posts
Sorry, I just saw that. I'm trying to remap f10 11 12 and the eject key with keytweak. It won't recognize those keys. The function key does work though.

#69
AlmostDarkWater

AlmostDarkWater

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 2 posts
thx bergdoktor for the 3.1 files, and M4xim for the "How To..." its perfectly done in win7 ultimate x64. ^^

#70
AlmostDarkWater

AlmostDarkWater

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 2 posts
Hi all, now i have a problem, after reformatting my windows, i failed to run bootcamp 3.1. do any of you know how to solve this?i cant use the feature of this keyboard. n i really cant live without the multimedia keys. its hard for me to turn volume up n down. T.T

#71
frederikwp

frederikwp

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 2 posts
I'm trying to set up a 2009 Apple Wireless Keyboard on a PC running Windows 7 x64 Pro, and none of the suggestions posted here are working for me. I can execute DPInst.exe and it will complete without errors. I can also install Bootcamp and I get the taskbar icon. However, the Apple keyboard is never listed as a device in Device Manager (either in the "Keyboard" or in the "Human Interface Devices" categories). I can manually update the "HID-compliant consumer control device" using KeyMagic64.inf, but this results in a "Device cannot start" error. Also, my registry doesn't even have the entry for KeyMagic that has been discussed here.

I don't even care about the keys because UAWKS is working fine for me. My problem is that the keyboard randomly hangs (simply being unresponsive or repeating the same key indefinitely until manually switching the keyboard off and on again). I figured that this could be related to not having the proper Apple driver installed.

Thanks in advance for any advice.

#72
frederikwp

frederikwp

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 2 posts
I uninstalled the proprietary BT stack that came with my Cirago BT dongle. Now everything works smoothly using the Windows 7 stock drivers. Go figure.

#73
anibalin

anibalin

    InsanelyMac Sage

  • Members
  • PipPipPipPipPip
  • 268 posts
hey guys.
Is there a way, under windows, to swap the
alt key to be the windows key
command key to be the alt key

I tried sharpkeys app but it wont detect the alt key son I cannot swap it.
I have the mmedia keys running too.
thanks in advance.

edit:
http://weblogs.asp.n...ht-alt-key.aspx

#74
godiebigcity

godiebigcity

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 2 posts

Here's where the complications begin:
2. To change the fn-key behavior (to default F1-F12 and not to fn+F1 - fn+F12)

If
you do that, you break the Volume up/down with OSD functionality of the BootCamp drivers you just installed (BootCamp 3.0 or 3.1)

So you have a choice here, between:
1. Use function keys with [Fn] depressed and keep Volume up/down with OSD (and all other function keys that the drivers remap)
2. Use the Function keys without [Fn] having to be held, but loose the Vol up/dn and OSD etc.

Actually I got option 2 working now under Windows 7 x64 :D
[Edit] Oh, that's actually a nested quote. So just to clarify things. What I meant is that the function keys work normally, except if I press the [Fn] key, then I got the media keys and the fancy apple icons[/Edit]
Only downside is that I am not exactly sure, what I did to get it working :D

My best guess is that there are more than 2 registry entries controlling the [Fn] behavior of the keyboard as I found 5 entries while searching for "OSXFnBehavior".

What did I do?

1) Searched for "OSXFnBehavior" in the registry and changed all the values to 0.
Just so you can compare your search results with mine, here is a list of the 5 entries I found on my machine:
HKEY_CURRENT_USER\Software\Apple Inc.\Apple Keyboard Support
HKEY_LOCAL_MACHINE\SYSTEM\ControlSet001\services\KeyMagic
 HKEY_LOCAL_MACHINE\SYSTEM\ControlSet002\services\KeyMagic
 HKEY_LOCAL_MACHINE\SYSTEM\ControlSet\services\KeyMagic
 HKEY_USERS\S-1-5-21-3482921680-60025300-2714009602-1001\Software\Apple Inc.\Apple Keyboard Support
2) Killed and restarted BootCamp.exe several times.
The path to the exe should be C:\Program Files\BootCamp\. Just in case you don't know, where to find it.

3) Followed the instructions of this blog. However, I do not know if this is in any way related to the [Fn] behavior.

4) Waited some time and let the little computer elves do their magic :P

#75
doum

doum

    InsanelyMac Protégé

  • Members
  • Pip
  • 10 posts

After many hours of research , just want to post it in one place:
it attachment drivers for Apple Aluminium Wired Keyboard both for Win7 x64 and x86 enjoy!


Hi all

I have a macbook pro @home
I buy a Apple Wireless Keyboard for my Windows 7 PC @Work

I'm used to the Apple keyboard.
I'd like to get the same layout on my PC

cmd + c for copy
cmd + v for past
cmd + tab window for selection
alt + shift + L for |
@ in the top left of the keyboard
etc....

For now I have the Bluetooth keyboard connected. Works good
What is the best solution? If I run the AppleKeyboardInstallerx86.exe nothing happens: (

#76
godiebigcity

godiebigcity

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 2 posts

I'm used to the Apple keyboard.
I'd like to get the same layout on my PC

cmd + c for copy
cmd + v for past
cmd + tab window for selection
alt + shift + L for |
@ in the top left of the keyboard
etc....

Maybe this helps:
MacComfort

#77
LBCDanno

LBCDanno

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 4 posts
Anyone else get error code 2754? I'm on Win 7 x64, using the aluminum USB keyboard. When I try and install the driver, it says that it cannot, because my current version is more recent. Any help is greatly appreciated. Attached File  2010_08_14_2053.png   36.72KB   87 downloads

#78
t3h m00kz

t3h m00kz

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 1 posts
Hey guys,

I've got a PC running Windows 7 x86 (32 bit). I've got a wired aluminum Mac board (small variant, no 10 key), and I've tried to install drivers from various sources. I found "AppleKeyboardInstaller.exe" online, and attempted to install. It got my FN key working for arrow keys and delete. However, my Volume Up/Volume Down/Mute/Pause/Play/Forward/Reverse keys do not work. I tried Poohlo's "AppleKeyboardInstallerx86.exe," but nothing appears on my screen after running the app.

Help would be appreciated.

E: Nevermind, play/pause/reverse/forward works. Volume keys do not.

#79
cuco85

cuco85

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 4 posts
Same here. i am in Win7 with my "old" Alu wired Keyboard. the driveres from poohlo seem to work except of the Volume buttons. any idea or help?

may it be that tehes keys are already used by any other shotkeys? by pulling F11 my firefox goes in fullscreen mode

#80
milko9000

milko9000

    InsanelyMac Protégé

  • Just Joined
  • Pip
  • 1 posts
When I try to install this BootCamp64.msi on my Windows Installation, I get erro 2753. I've tried uninstalling everything I did prior to that (I think I had some Bergdoktor and poohlo files already on) but it hasn't helped. At the moment the keyboard works but none of the special functions do. So frustrated! Any help welcomed.





1 user(s) are reading this topic

0 members, 1 guests, 0 anonymous users

© 2014 InsanelyMac  |   News  |   Forum  |   Downloads  |   OSx86 Wiki  |   Mac Netbook  |   PHP hosting by CatN  |   Designed by Ed Gain  |   Logo by irfan  |   Privacy Policy