I was already using SteerMouse, but wanted to try out the RazerPro 1.6.x drivers for my Razer Diamondback on my OS X Leopard system, only to find out that I should have just stayed with the tried-and-true SteerMouse. The Razer website provides the following instructions for removing the RazerPro drivers from one’s machine:

There are 2 methods to uninstall the drivers. Note that the below does not remove the SystemLoginItem entry in the system preference.

1. Run the uninstall.sh file that is included in the driver package.
2. Launch the Terminal Application. Copy and paste the below commands one at a time.
   
sudo rm -r /System/Library/Extensions/RazerPRODriver.kext
sudo rm -r "/Library/Application Support/Razer/RazerPRODaemon.app"
sudo rm -r /Library/PreferencePanes/RazerPRO.prefPane
rm -f ~/Library/Preferences/com.razer.PRO.plist
sudo rm -r /Library/Receipts/Razer\ PRO.pkg

While that cleaned up the important stuff, and allowed me to use SteerMouse again, I noticed that the RazerPRODaemon was still running…

2055 ?? 0:00.05 /Library/PrivilegedHelperTools/RazerPRODaemon.app/Contents/MacOS/RazerPRODaemon

Killing the process won’t work (the daemon will launch again). I needed to remove a lingering .plist file:

sudo rm -r /Library/LaunchAgents/com.razer.PRO.RazerPRODaemon.plist

After killing the daemon, I removed the whole app:

sudo rm -r /Library/PrivilegedHelperTools/RazerPRODaemon.app

That did the trick.

Comments (imported from the old blog):

Aug 19, 2008

Stephen said…
Thanks for the tip. That seemed to fix my problem :)

Dec 27, 2008

darron said…
Thanks for the tip too - what a pain the Razer software is.

Feb 06, 2009

Brian said…
I have been wrestling with this thing for a bit. The directions you gave didn’t quite work for me because the daemon relaunched even after I removed .plist file(?!) With that running, it won’t let you delete the app. But I could open the content of the RazerPRODaemon.app and found the actual daemon. That I could delete, then I killed the running daemon again, which didn’t restart this time, and removed the rest of the R~.app.

Would not have solved it without you pointing me in the right direction, thanks for the help!