› Forums › Operating Systems › Windows Server 2008 R2 › Hardware Compatibility › Apple Magic Mouse
- This topic has 18 replies, 6 voices, and was last updated 14 years, 10 months ago by Anonymous.
- AuthorPosts
-
- 29th November 2009 at 09:52 #43939
Yes yes I know its not a great mouse but all my other hardware is Apple and I want to get this working. I have it working under Bluetooth but only have left and right click and nothing else. I have a driver that installs in Windows 7 but doesn’t allow install under Server 2008 R2. I’ve tried compatibility mode but no go, any ideas how I fool it that I am on Windows 7?
Cheers!
- 29th November 2009 at 15:55 #50197
If you can, extract the actual driver files, or copy them from the temporary directory, and install the driver manually.
- 29th November 2009 at 15:55 #60016Anonymous
If you can, extract the actual driver files, or copy them from the temporary directory, and install the driver manually.
- 2nd December 2009 at 12:32 #50200
Thanks, have tried that but it says the driver is not 64 bit compatible oddly but its definitely the 64 bit versions.
- 2nd December 2009 at 12:32 #60019Anonymous
Thanks, have tried that but it says the driver is not 64 bit compatible oddly but its definitely the 64 bit versions.
- 2nd December 2009 at 15:34 #50201
Hmm, odd. Did you have a look at the INF file(s)? There may be a small line you can remove or change to stop it checking compatibility.
- 2nd December 2009 at 15:34 #60020Anonymous
Hmm, odd. Did you have a look at the INF file(s)? There may be a small line you can remove or change to stop it checking compatibility.
- 2nd December 2009 at 22:24 #50202
Here’s the inf – any ideas? Appreciate any help with this.
- 2nd December 2009 at 22:24 #60021Anonymous
Here’s the inf – any ideas? Appreciate any help with this.
- 2nd December 2009 at 23:09 #50203
I’m no expert, but I think this line is preventing the install on a Server OS:
[Version]
Signature="$WINDOWS NT$"Perhaps you could change that to “$SERVER NT$” instead of “$WINDOWS NT$”, but I do not know if that will help.
- 2nd December 2009 at 23:09 #60022Anonymous
I’m no expert, but I think this line is preventing the install on a Server OS:
[Version]
Signature="$WINDOWS NT$"Perhaps you could change that to “$SERVER NT$” instead of “$WINDOWS NT$”, but I do not know if that will help.
- 3rd December 2009 at 03:08 #50204
OK, The driver you have is just for windows under bootcamp, not most versions of windows.
However, some clever folks made a working driver for normal versions of windows, available here: http://uneasysilence.com/archive/2009/11/14588/
- 3rd December 2009 at 03:08 #60023Anonymous
OK, The driver you have is just for windows under bootcamp, not most versions of windows.
However, some clever folks made a working driver for normal versions of windows, available here: http://uneasysilence.com/archive/2009/11/14588/
- 3rd December 2009 at 04:07 #50198
Yep, thats the one I am trying to use… Installs fine in Windows 7 but not 2008 R2.
- 3rd December 2009 at 04:07 #60017Anonymous
Yep, thats the one I am trying to use… Installs fine in Windows 7 but not 2008 R2.
- 3rd December 2009 at 04:23 #50199
Hmm.
In device manager/add new hardware wizard, can you choose look for files, and browse to the extracted folder? Bypassing the need to use the setup executable.
Also, what happened when you tried with compatibility mode?
Otherwise, I would suggest manually copying the files and adding the registry entries as described in the INF.
- 3rd December 2009 at 04:23 #60018Anonymous
Hmm.
In device manager/add new hardware wizard, can you choose look for files, and browse to the extracted folder? Bypassing the need to use the setup executable.
Also, what happened when you tried with compatibility mode?
Otherwise, I would suggest manually copying the files and adding the registry entries as described in the INF.
- 3rd December 2009 at 04:33 #50205
Tried everything apart from your last point, perhaps I will look at the registry entries.
- 3rd December 2009 at 04:33 #60024Anonymous
Tried everything apart from your last point, perhaps I will look at the registry entries.
- AuthorPosts
- You must be logged in to reply to this topic.