Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

michaelverdin

macrumors member
Original poster
Feb 12, 2007
37
0
Hi,

Since I have upgraded to Bootcamp 1.3 my volume and eject keys (the top four keys at the right hand side of the apple keyboard) don't work, any suggestions?



Thanks,


Mike
 

quicksilver77

macrumors 6502
Nov 30, 2005
277
13
Nova Scotia, Canada
I am having the same type of problem with my MBP using 1.3 I have no

-keyboard brightness
-volume
-brightness

I read that it is a problem with kbdmgr.exe not starting up. Any ideas?
 

a1291762

macrumors member
Aug 19, 2003
37
0
Australia
Boot Camp 1.3 keyboard fix

The Boot Camp 1.3 drivers appear to have a broken kbdmgr.exe (either that or it just doesn't work on early MacBook Pros). You can get a working kdgmgr.exe from KeyboardSetup.exe in the Boot Camp 1.2 drivers. It installs fine over the top of the 1.3 drivers and restores the brightness and volume keys.

-- posted using Safari in Windows XP on a MacBook Pro with Boot Camp 1.3 and working volume keys!

Ouch! Safari for Windows chops off text here and on my blogger blog. Beware when using Safari to enter information anywhere!
 

a1291762

macrumors member
Aug 19, 2003
37
0
Australia
Does that work with XP64 on a MacPro? I haven't been able to get the eject button working...

I don't know if Apple's BootCamp 1.2 drivers support 64-bit XP or not. In this case though I don't think there's any drivers getting installed, just an executable (and 32-bit executables should work just fine on 64-bit Windows).

You'll know if the install worked because you'll have the 'bootcamp' icon (looks like the 'a' key of a keyboard) in your system tray.
 

Osarkon

macrumors 68020
Aug 30, 2006
2,161
4
Wales
Only problem I get with the Bootcamp 1.2 drivers is that I don't get the proper double quotation marks, i get ¨ .

This seems to have been fixed in 1.3, however I then sacrifice the volume and eject buttons. :(
 

a1291762

macrumors member
Aug 19, 2003
37
0
Australia
Only problem I get with the Bootcamp 1.2 drivers is that I don't get the proper double quotation marks, i get ¨ .

This seems to have been fixed in 1.3, however I then sacrifice the volume and eject buttons. :(

Do you mean Bootcamp 1.2 vs Bootcamp 1.3 or do you mean Bootcamp 1.3 + KeyboardSetup.exe from Bootcamp 1.2? I haven't noticed a problem with the " key but then... perhaps I haven't used it yet.
 

Tangerine

macrumors regular
Jan 5, 2007
182
0
Bootcamp 1.3 improve the Eject and Volume Key. Before with vesion 1.2, I have problem with Eject and Volume keys in Windows, it's very buggy and sometime doesn't respond. With version 1.3 it suppose to work better, it work exactly like in OS X now, when using Eject or Volume key on Apple Keyboard, there will be an icon indicating the process. I suggest upgrade instead of downgrade. If you have problem, try burn a clean Driver CD with Bootcamp 1.3. Boot into Windows and make sure you unplug all devices except keyboard and mouse, also make sure you don't have anything open. Insert CD and install, let it finish, don't interfere with it and let it done. Mine work great.
 

ziutek

macrumors member
Aug 4, 2004
80
0
CA
The volume/brightness keys also didn't function on my vista partition but I got everything to work by putting an alias of kbdmgr.exe in the startup folder (which is located in the start menu).
 

a1291762

macrumors member
Aug 19, 2003
37
0
Australia
"It works for me" is not helpful

Guys, the "it works for me" responses are not helpful. If it didn't work for everyone Apple would have released a fix by now so obviously this is only affecting a small number of people.

I have installed the Bootcamp 1.3 drivers more than once yet the problem persists. I have no external peripherals connected yet the problem persists. The kbdmgr.exe process in Bootcamp 1.3 simply does not work on my machine. It runs but the system tray icon does not show up and the keys do not work. I don't know if this is a hardware issue (I have a rev1 MBP) or a software issue (My Windows XP install has been around since Bootcamp 1.0) and frankly I don't care. The Bootcamp 1.2 version of kbdmgr.exe works so it's a solution for anyone that has this problem.

If you don't have a problem, don't install it. Just don't tell us that we're not doing it right.
 

Sbrocket

macrumors 65816
Jun 3, 2007
1,250
0
/dev/null
I encountered the kbdmgr.exe launching problem when upgrading from Bootcamp 1.2 to 1.3, which it appears is what you did. If you manually launch kbdmgr.exe it will work again normally (though this is a hassle) since it just seems to be a problem with the initial startup. Installing Bootcamp 1.3 on a fresh Windows installation (i.e. without previously installing 1.2) seems to not cause the same problems. You may want to try completely removing Boot Camp via "Add/Remove Programs" in Windows, do a restart, and then try reinstalling the 1.3 drivers. It may not work, but since it seems to be a problem with the installer when upgrading from 1.2 to 1.3 this could bypass whatever bug there is. No promises.

Required warning: Remember always this is still beta software; I know you said "1.3 Beta", but a lot of people say it and don't fully realize the implications of what it means. I'm not blaming you, but remember that "beta" means still in development.
 

a1291762

macrumors member
Aug 19, 2003
37
0
Australia
If you manually launch kbdmgr.exe it will work again normally

Nope.

Installing Bootcamp 1.3 on a fresh Windows installation (i.e. without previously installing 1.2) seems to not cause the same problems.

Installing Windows and all the apps again is a pain. It's something I'd consider only if there was no alternative (and there are two). Heck, a worse problem happened to me when installing some Mac OS X update and I didn't reinstall: http://a1291762.blogspot.com/2007/02/nasty-system-error.html

You may want to try completely removing Boot Camp via "Add/Remove Programs" in Windows, do a restart, and then try reinstalling the 1.3 drivers.

Been there, done that, didn't work. The problem is that kbgmgr.exe doesn't work, not that it doesn't run when I boot.
 

Osarkon

macrumors 68020
Aug 30, 2006
2,161
4
Wales
Do you mean Bootcamp 1.2 vs Bootcamp 1.3 or do you mean Bootcamp 1.3 + KeyboardSetup.exe from Bootcamp 1.2? I haven't noticed a problem with the " key but then... perhaps I haven't used it yet.

Bootcamp 1.2 vs 1.3, I can't get the keyboard manager to run when I have the 1.3 drivers installed.

Something worth noting though maybe is that I'm not actually using the keyboard on my macbook, but on my Vista desktop when I need to use it for certain things.
 

a1291762

macrumors member
Aug 19, 2003
37
0
Australia
Bootcamp 1.2 vs 1.3, I can't get the keyboard manager to run when I have the 1.3 drivers installed.

Same problem as me. I had success by running KeyboardSetup.exe from Bootcamp 1.2 (there's a link on an earlier post) which installs a version of kbdmgr.exe that works.

In other words, I have Bootcamp 1.3 installed but I'm using kbdmgr.exe from Bootcamp 1.2 and everything works fine.
 

Sbrocket

macrumors 65816
Jun 3, 2007
1,250
0
/dev/null
Been there, done that, didn't work. The problem is that kbgmgr.exe doesn't work, not that it doesn't run when I boot.

Well then its just a weird anomaly. The Boot Camp Drivers v1.3 are working fine for me currently in XP Pro SP2, which means its an issue with your specific installation of Windows. Did you do anything out of the ordinary? Modify your installation with nLite or something similar?
 

a1291762

macrumors member
Aug 19, 2003
37
0
Australia
Well then its just a weird anomaly. The Boot Camp Drivers v1.3 are working fine for me currently in XP Pro SP2, which means its an issue with your specific installation of Windows.

It's not a weird anomaly, it's a bug in kbdmgr.exe or something it uses. Evidence? Installing 1.2 makes kbdmgr.exe work every time while installing 1.3 makes kbgmgr.exe fail every time. The kbdmgr.exe from 1.2 works with Bootcamp 1.3 which is a solution for the people that have this problem.
 

Osarkon

macrumors 68020
Aug 30, 2006
2,161
4
Wales
Same problem as me. I had success by running KeyboardSetup.exe from Bootcamp 1.2 (there's a link on an earlier post) which installs a version of kbdmgr.exe that works.

In other words, I have Bootcamp 1.3 installed but I'm using kbdmgr.exe from Bootcamp 1.2 and everything works fine.

I tried that and it seems to just be using the 1.2 drivers again because my double quote ( " ) key doesn't work again. :rolleyes:
 

Sbrocket

macrumors 65816
Jun 3, 2007
1,250
0
/dev/null
It's not a weird anomaly, it's a bug in kbdmgr.exe or something it uses. Evidence? Installing 1.2 makes kbdmgr.exe work every time while installing 1.3 makes kbgmgr.exe fail every time. The kbdmgr.exe from 1.2 works with Bootcamp 1.3 which is a solution for the people that have this problem.

Right, and my installation of the 1.3 drivers is magical and simply decided to work for no particular reason. I suppose the drivers simply like my personality and not yours, right? Try to avoid phrases like "every time" because more often than not, you end up spouting out nonsense.
 

StudioGuy

macrumors regular
Nov 4, 2003
121
0
I've read about the issues with 1.3 on the keyboard and also BT, and experienced them all myself. Here's what finally worked for me (after using a generic USB keyboard - the Apple USB keyboards wouldn't not work, and it was picky which USB port on the Mac Pro I used).

Anyway, I saw that BT 1.3 driver would not load properly. After much adieu, I finally thought to try the "roll back driver" option in the driver tab from Device Manager. That brought it back to a 1.0.0 Apple driver, and suddenly everything started getting recognized again! Yeah!

So, brave (bleeding edge) me decided to reinstall the Mac Drivers 1.3 again (I had removed them still before to no recovery). This time it updated fine and I have the Apple BT keyboard & mouse working with very cool sound + eject keys working too! So, the v1.3 keyboard driver is working fine now for me with the new cool features

Give that a try - use Device Manager to see what drivers have an (!) and roll back, then try the drivers again perhaps and get lucky.

Note that there are 4 PCI (!) which are always there - you can safely ignore them for some reason (see old post).

HTH someone!
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.