I installed and played around with DoubleCommand, and used it to swap the COMMAND and OPTION keys. I've since uninstalled (using Appzapper). But--now, every time I reboot my Mac, it reverts to the swapped-key configuration. Even if I use the (Mac) pref panes to set things back to normal, when I reboot again -- the keys are swapped.
Any ideas?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I don't know how Appzapper works, but you might want to look in /Library/StartupItems/DoubleCommand. There is also an uninstall.command file that comes with DoubleCommand to remove it from your system.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks very much for the response. Appzapper does a pretty thorough job -- there's nothing related to DoubleCommand left at all in my startup items folder.
Two questions:
(1) Is it possible that DoubleCommand reset some Leopard default, before being deleted? (I thought that, rather, it would "do its thing" each time it ran as a startup item -- and, now that it's gone, it would have no effect.)
(2) Since there's no trace left of DoubleCommand (that I can find), should I reinstall DC and then uninstall it with its own uninstaller?
Thanks!
Alan
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There's no default that was set, DoubleCommand does in fact need to run to have any effect. However, Mac OS X does cache kexts and it is possible that the kext cache still has it.
Try running the following as an admin user in the Terminal:
sudo rm /System/Library/Extensions.kextcache
Then restart. At this point I don't see how there could possibly be anything of DoubleCommand left on your machine.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I installed and played around with DoubleCommand, and used it to swap the COMMAND and OPTION keys. I've since uninstalled (using Appzapper). But--now, every time I reboot my Mac, it reverts to the swapped-key configuration. Even if I use the (Mac) pref panes to set things back to normal, when I reboot again -- the keys are swapped.
Any ideas?
I don't know how Appzapper works, but you might want to look in /Library/StartupItems/DoubleCommand. There is also an uninstall.command file that comes with DoubleCommand to remove it from your system.
Thanks very much for the response. Appzapper does a pretty thorough job -- there's nothing related to DoubleCommand left at all in my startup items folder.
Two questions:
(1) Is it possible that DoubleCommand reset some Leopard default, before being deleted? (I thought that, rather, it would "do its thing" each time it ran as a startup item -- and, now that it's gone, it would have no effect.)
(2) Since there's no trace left of DoubleCommand (that I can find), should I reinstall DC and then uninstall it with its own uninstaller?
Thanks!
Alan
There's no default that was set, DoubleCommand does in fact need to run to have any effect. However, Mac OS X does cache kexts and it is possible that the kext cache still has it.
Try running the following as an admin user in the Terminal:
sudo rm /System/Library/Extensions.kextcache
Then restart. At this point I don't see how there could possibly be anything of DoubleCommand left on your machine.
Thanks so much for the response, Michael.
(I tried running that command in terminal, but I get the prompt "no such file or directory." It's still a mystery <smile>.)