I've had lots of pesky kernel panics in the past with DoubleCommand (love it, don't get me wrong), so I'm removing DoubleCommand before I upgrade to Snow today.
i'll then try re-installing DblCmd to see what happens and report back here.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
yea the pc Style home and end key work, BUT NOT ON 64 BIT KERNEL!
It does not work when i boot my pro into 64 !There sould bee a update to support 64 Bit !
Otherwise Great Programm ! seeya
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
v1.6.8 didn't work for my under Snow Leopard. (I sent a feedback message to the developer with the details, but haven't heard anything back, so far.) What it did was a persistence for just one unwanted modification (Enter->Command) and failure to accept and effect the one change I did want (Backslash->Forward Delete). Because of the persistence for that unwanted modification, I had to uninstall DoubleCommand. Looking forward to a new version (or advice as to what I'm doing wrong with the current version) so I can avoid having to use the fn-Delete for the Forward Delete.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
It sounds like the prefpane is not able to update your settings file for some reason, possibly unrelated to Snow Leopard. The settings file for the machine is /Library/StartupItems/DoubleCommand/DoubleCommand.pref - try changing this file to have only the number 0 in it, which will cause DoubleCommand to have no effect. This could just be a permissions problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks, Michael. That must have been the problem, but as I had uninstalled DoubleCommand, I just reinstalled it and did a Restart.
I then did an "All off" and a Save: System and a Save: User--and that got me the User Preferences and System Preferences to both be "0"--clearing, if I recall correctly, a System Preferences that had been "1". I then enabled just the "Backslash (\) acts as Forward Delete" and now I have the Active Settings as "131072", the User Preferences as "131072", and the System Preferences as "0"--and my Backslash key is doing as prescribed when I'm logged in.
David
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Not compatible in 32 or 64 bit mode. None of my key bindings with double command work after upgrade to SL. Also the reason the pref pane prompts you to restart system settings is that this is how the 64 bit system settings app deals with 32 bit pref panes.
Anyway, if its working for some people on SL congrats, not working for me at all.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
BSD process name corresponding to current thread: kernel_task
I didn't notice it not working, but I didn't specifically test it either: I've only had 10.6 for a few days. I had 10.4 before. I am running on a 32-bit MacBook Pro (the original Core Duo model). I removed DoubleCommand and will wait for a confirmation that it works before installing a new version.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
@usego: I've been using 4.2 and it does work great in 64bit kernel mode, but in 32bit kernel mode it doesn't work at all.
So now I can either install 1.6.8 and use 32bit or 4.2 and 64…. Is this a bug? Or is 4.2 intended to work in 64 bit mode only?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
how do i unistall the 64 Version ? i cant install the 32 bit version under 32 bit as it say there is a newer version !
Startup items is EMPTY both on 32 or 64 Start !!!!! Prefpane is here under 32 bit also not visible !
Any HELP?
thanks !
sicnerly
usego
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-10-22
+1 For help on the 64bit issue. I've got the same problem. I installed the 64bit "beta" and then tried to uninstall it so I could run 1.6.8 in 32-bit kernel mode. Now I can't run either.
I miss DoubleCommand. Any news on official updates?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Since you ask, ok. I have Snow Leopard and I've compiled the code with the 64-bit patch, but not yet tested on the 64-bit kernel, because I haven't yet got a binary building that contains a correct 32-bit version for 10.4 ppc and i386 as well as x86_64.
However, if you are able to run with the default 32-bit kernel, but you can't get 1.6.8 working, that is a separate issue that you probably need to resolve before a new release would work for you anyway.
Typing "kextstat | grep DoubleCommand" from within the Terminal app (just copy and paste from here) is the easiest way to see if the important part of DoubleCommand is loaded or not, if you don't see a line like so:
Then it's not loaded. If that's the case, just install from the website. If it's loaded, perhaps you just can't configure it correctly for some reason, like perhaps the current prefpane won't work in Snow Leopard or something, I haven't looked at that yet.
Hope that helps.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-10-22
Thanks for the update. I can't help but think it might be worthwhile to separate out PPC and Intel builds. I've seen a lot of apps go this route since Snow Leopard. It does seem challenging to include, is it 3 or 4 chip architectures?, in one build.
I ran the terminal command and go no response. Actually my issue is slightly different. Since I installed, then uninstalled the unofficial 64bit build, I Can install DoubleCommand, and even see the System Preferences, but the issue is that (even though I've uninstalled the 64bit version) when I go to install 1.6.8 the installer won't let me. I get an exclamation point on my hard disk with the message "DoubleCommand can't be installed on this disk
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-10-22
oops. my post got prematurely posted…
The error message is "DoubleCommand can't be installed on this disk. A newer version of this software already exists on this disk".
only I've looked all over for anything resembling ANY version of doublecommand (receipts, libraries) anywhere.
So then I give up and go to re-install the 64bit version and it gets installed successfully. But then, when I go to the Preference Pane, I get this dialog error:
"DoubleCommand seems not to be running at the moment. you can save prefs but can't activate settings. Maybe you need to reinstall…"
Restarting OS X, reinstalling this version of DoubleCommand, does nothing.
So I can't run 1.6.8 because I can't install it. And I can't run the 64bit because it "seems not to be running…."
argh….
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
i was unabel to unistalll DC so i ask the Dev of the 64 Version he reply
Remove the kernel extension (/System/Library/Extensions/DoubleCommand.kext) and the preference pane (right-click in System Preferences) and reboot.
But there is no kext on my Machine ! So i open the intstall Packet and deep in there i fund a uninstaller i run this and i can Install key remap 4 macbook( Otherwise it say you have DC install!) now the new Programm work great under 64 bit !
Hope this Help how cant Unistall the DC !
Sicnerly
usego
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
For those who wish to try here is a build that *might* work with the 64-bit kernel.
The machine I have 10.6 installed on turns out to not support booting into the 64-bit kernel, so I'll have to upgrade another machine before I can test, but for those who are very keen (as you must be to be running in 64-bit mode in the first place) take a look. Be warned, I have not tested this in the 64-bit kernel, so this may crash your machine, requiring you to restart. This is a universal binary that I have tested on 10.5 Intel and 10.6 32-bit Intel, and the prefpane does load as 64-bit on 10.6.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-10-26
I'd love to try it. But I installed that wacky early 64 bit version. And now your installed claims that I already have newer version installed and won't let me install 1.6.9 beta.
I've uninstalled DC, looked through receipts, all over. Can't find how OS X knows I ever installed DC.
Do you have any ideas about how to fix this issue? Can you make an installer that doesn't check for newer versions?
Please?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hmm. Well, there is no explicit version checking done by me, so this must be an Installer.app thing. As far as I know, the Installer should only be checking in /Library/Receipts and using that for information on what is already installed.
This will remove everything to do with DoubleCommand, except for the user specific preferences if they exist. If you still can't install after running this script and restarting, then I'm not sure what the Installer is using to keep track of installations.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2009-11-07
In case anyone else installed the early 64-bit only beta, "4.2", and is having issues installing 1.6.9, I finally figured out how to do it.
1. If you have any versions of doublecommand currently installed, uninstall them by going to /Library/StartupItems/Doublecommand and running uninstall.command
2. go to /Library/Receipts/ and open InstallHistory.plist using TextEdit or any other text editor. Search for doublecommand and if you find it, you need to delete the entire dictionary entry for it.
It should look like this:
<dict>
<key>date</key>
<date>2009-11-07T20:15:18Z</date>
<key>displayName</key>
<string>DoubleCommand</string>
<key>displayVersion</key>
<string></string>
<key>packageIdentifiers</key>
<array>
<string>com.baltaks.DoubleCommand</string>
</array>
<key>processName</key>
<string>Installer</string>
</dict>
3. Go to /private/var/log/ (you can do this by, in the Finder, going up to "Go.." in the menu bar and "Go to Folder…" and typing in "/private/var/log/ ". Look for "install.log" and open that with Text Edit. Search for Doublecommand and delete any line with Doublecommand in the name.
4. Restart your mac, then install 1.6.9. worked for me.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Snow Leopard is coming out soon. Is DoubleCommand compatible with it?
I don't have Snow Leopard yet, so I don't know.
I've had lots of pesky kernel panics in the past with DoubleCommand (love it, don't get me wrong), so I'm removing DoubleCommand before I upgrade to Snow today.
i'll then try re-installing DblCmd to see what happens and report back here.
DoubleCommand is working fine for me under 10.6
I am using a patched version (to map Esc onto the Caps Lock key), but it just works.
So, I assume that this means that the forwrd delete key assignmente will continue working as on 10.5
Emile
yea the pc Style home and end key work, BUT NOT ON 64 BIT KERNEL!
It does not work when i boot my pro into 64 !There sould bee a update to support 64 Bit !
Otherwise Great Programm ! seeya
v1.6.8 didn't work for my under Snow Leopard. (I sent a feedback message to the developer with the details, but haven't heard anything back, so far.) What it did was a persistence for just one unwanted modification (Enter->Command) and failure to accept and effect the one change I did want (Backslash->Forward Delete). Because of the persistence for that unwanted modification, I had to uninstall DoubleCommand. Looking forward to a new version (or advice as to what I'm doing wrong with the current version) so I can avoid having to use the fn-Delete for the Forward Delete.
It sounds like the prefpane is not able to update your settings file for some reason, possibly unrelated to Snow Leopard. The settings file for the machine is /Library/StartupItems/DoubleCommand/DoubleCommand.pref - try changing this file to have only the number 0 in it, which will cause DoubleCommand to have no effect. This could just be a permissions problem.
Thanks, Michael. That must have been the problem, but as I had uninstalled DoubleCommand, I just reinstalled it and did a Restart.
I then did an "All off" and a Save: System and a Save: User--and that got me the User Preferences and System Preferences to both be "0"--clearing, if I recall correctly, a System Preferences that had been "1". I then enabled just the "Backslash (\) acts as Forward Delete" and now I have the Active Settings as "131072", the User Preferences as "131072", and the System Preferences as "0"--and my Backslash key is doing as prescribed when I'm logged in.
David
Forgot to include that after enabling the one selection I did (just) a Save: User.
David
Not compatible in 32 or 64 bit mode. None of my key bindings with double command work after upgrade to SL. Also the reason the pref pane prompts you to restart system settings is that this is how the 64 bit system settings app deals with 32 bit pref panes.
Anyway, if its working for some people on SL congrats, not working for me at all.
I realize my version was of DoubleCommand was old, but it caused kernel panics when rebooting the machine:
Sun Sep 13 20:01:16 2009
panic(cpu 1 caller 0x2a6ac2): Kernel trap at 0x2e575a86, type 14=page fault, registers:
…
Backtrace continues…
Kernel Extensions in backtrace (with dependencies):
com.baltaks.driver.DoubleCommand(1.6.2)@0x2e573000->0x2e577fff
dependency: com.apple.iokit.IOHIDFamily(1.6.0)@0x34662000
com.apple.iokit.IOHIDFamily(1.6.0)@0x34662000->0x3469cfff
BSD process name corresponding to current thread: kernel_task
I didn't notice it not working, but I didn't specifically test it either: I've only had 10.6 for a few days. I had 10.4 before. I am running on a 32-bit MacBook Pro (the original Core Duo model). I removed DoubleCommand and will wait for a confirmation that it works before installing a new version.
if someone what to try the 64 bit compatible version thake this file
http://rapidshare.com/files/283353439/DoubleCommand-4.2.pkg.zip.html
NO Warranty. For mee it works on 64 bit !
@usego: I've been using 4.2 and it does work great in 64bit kernel mode, but in 32bit kernel mode it doesn't work at all.
So now I can either install 1.6.8 and use 32bit or 4.2 and 64…. Is this a bug? Or is 4.2 intended to work in 64 bit mode only?
i am N O T the Dev. of the 64 bit version ! So aks the dev. it self why i dont work under 32 ! i will also ask him as it dnot work for mee on 32!
search for Ryan Walklin thas the Dev.
sincrly
usego
how do i unistall the 64 Version ? i cant install the 32 bit version under 32 bit as it say there is a newer version !
Startup items is EMPTY both on 32 or 64 Start !!!!! Prefpane is here under 32 bit also not visible !
Any HELP?
thanks !
sicnerly
usego
+1 For help on the 64bit issue. I've got the same problem. I installed the 64bit "beta" and then tried to uninstall it so I could run 1.6.8 in 32-bit kernel mode. Now I can't run either.
I miss DoubleCommand. Any news on official updates?
Since you ask, ok. I have Snow Leopard and I've compiled the code with the 64-bit patch, but not yet tested on the 64-bit kernel, because I haven't yet got a binary building that contains a correct 32-bit version for 10.4 ppc and i386 as well as x86_64.
However, if you are able to run with the default 32-bit kernel, but you can't get 1.6.8 working, that is a separate issue that you probably need to resolve before a new release would work for you anyway.
Typing "kextstat | grep DoubleCommand" from within the Terminal app (just copy and paste from here) is the easiest way to see if the important part of DoubleCommand is loaded or not, if you don't see a line like so:
138 0 0x897fc000 0x6000 0x5000 com.baltaks.driver.DoubleCommand (1.6.8) <21 6 5 4 2>
Then it's not loaded. If that's the case, just install from the website. If it's loaded, perhaps you just can't configure it correctly for some reason, like perhaps the current prefpane won't work in Snow Leopard or something, I haven't looked at that yet.
Hope that helps.
Thanks for the update. I can't help but think it might be worthwhile to separate out PPC and Intel builds. I've seen a lot of apps go this route since Snow Leopard. It does seem challenging to include, is it 3 or 4 chip architectures?, in one build.
I ran the terminal command and go no response. Actually my issue is slightly different. Since I installed, then uninstalled the unofficial 64bit build, I Can install DoubleCommand, and even see the System Preferences, but the issue is that (even though I've uninstalled the 64bit version) when I go to install 1.6.8 the installer won't let me. I get an exclamation point on my hard disk with the message "DoubleCommand can't be installed on this disk
oops. my post got prematurely posted…
The error message is "DoubleCommand can't be installed on this disk. A newer version of this software already exists on this disk".
only I've looked all over for anything resembling ANY version of doublecommand (receipts, libraries) anywhere.
So then I give up and go to re-install the 64bit version and it gets installed successfully. But then, when I go to the Preference Pane, I get this dialog error:
"DoubleCommand seems not to be running at the moment. you can save prefs but can't activate settings. Maybe you need to reinstall…"
Restarting OS X, reinstalling this version of DoubleCommand, does nothing.
So I can't run 1.6.8 because I can't install it. And I can't run the 64bit because it "seems not to be running…."
argh….
i was unabel to unistalll DC so i ask the Dev of the 64 Version he reply
Remove the kernel extension (/System/Library/Extensions/DoubleCommand.kext) and the preference pane (right-click in System Preferences) and reboot.
But there is no kext on my Machine ! So i open the intstall Packet and deep in there i fund a uninstaller i run this and i can Install key remap 4 macbook( Otherwise it say you have DC install!) now the new Programm work great under 64 bit !
Hope this Help how cant Unistall the DC !
Sicnerly
usego
For those who wish to try here is a build that *might* work with the 64-bit kernel.
The machine I have 10.6 installed on turns out to not support booting into the 64-bit kernel, so I'll have to upgrade another machine before I can test, but for those who are very keen (as you must be to be running in 64-bit mode in the first place) take a look. Be warned, I have not tested this in the 64-bit kernel, so this may crash your machine, requiring you to restart. This is a universal binary that I have tested on 10.5 Intel and 10.6 32-bit Intel, and the prefpane does load as 64-bit on 10.6.
http://doublecommand.sourceforge.net/files/DoubleCommand-1.6.9.dmg
I'd love to try it. But I installed that wacky early 64 bit version. And now your installed claims that I already have newer version installed and won't let me install 1.6.9 beta.
I've uninstalled DC, looked through receipts, all over. Can't find how OS X knows I ever installed DC.
Do you have any ideas about how to fix this issue? Can you make an installer that doesn't check for newer versions?
Please?
Hmm. Well, there is no explicit version checking done by me, so this must be an Installer.app thing. As far as I know, the Installer should only be checking in /Library/Receipts and using that for information on what is already installed.
To remove DoubleCommand, use the uninstall.command script from the StartupItems folder, or online at http://github.com/mbaltaks/doublecommand/blob/master/dist/DoubleCommand/uninstall.command
This will remove everything to do with DoubleCommand, except for the user specific preferences if they exist. If you still can't install after running this script and restarting, then I'm not sure what the Installer is using to keep track of installations.
In case anyone else installed the early 64-bit only beta, "4.2", and is having issues installing 1.6.9, I finally figured out how to do it.
1. If you have any versions of doublecommand currently installed, uninstall them by going to /Library/StartupItems/Doublecommand and running uninstall.command
2. go to /Library/Receipts/ and open InstallHistory.plist using TextEdit or any other text editor. Search for doublecommand and if you find it, you need to delete the entire dictionary entry for it.
It should look like this:
<dict>
<key>date</key>
<date>2009-11-07T20:15:18Z</date>
<key>displayName</key>
<string>DoubleCommand</string>
<key>displayVersion</key>
<string></string>
<key>packageIdentifiers</key>
<array>
<string>com.baltaks.DoubleCommand</string>
</array>
<key>processName</key>
<string>Installer</string>
</dict>
3. Go to /private/var/log/ (you can do this by, in the Finder, going up to "Go.." in the menu bar and "Go to Folder…" and typing in "/private/var/log/ ". Look for "install.log" and open that with Text Edit. Search for Doublecommand and delete any line with Doublecommand in the name.
4. Restart your mac, then install 1.6.9. worked for me.