I have a MacBook running Leopard. Qite a while ago, I installed DoubleCommand in order to be able to Forward Delete. I chose the enter key as the forward enter key. Everything has been working like a charm, until today when, fo no apparent reason that I could see, the enter key stopped functioning as assigned.
I removed DoubleCommand and checked the system for conflicting software, etc. It's all clean. So I tried installing. It gets right through to the last window to complete the installation process and says Install Failed. I did the operation again and got the same result. The message following the Install Failed message reads: "The following install step failed: run postflight script for DoubleCommand. Contact software manufacture".
Any ideas, please? And what is postflight script and where to I find it and how do I run it?
Thanks much
Emile
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
The postflight script is part of the installer package, but I haven't been able to find out why it is failing. If you run the installer, there is a menu item under the Window menu called Installer Log. If you open this and choose All Logs from the popup menu in that window, you could post the text from there and that might help solve the issue.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks for this, but I can't even come up with what you siggested, i.e. finding the Installer Log. This is a real mystery. I think that my only real avenue is to re-install the OS. None of the sugestions seem to work.
Emile
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
If you are unable to find the DoubleCommand.crashed file in any of the locations listed in that thread, you can try this:
command+space to open spotlight.
Type in terminal and run the terminal application.
At the command line, type in: mdfind DoubleCommand.crashed | grep "DoubleCommand.crashed"
That should give you the location of the file, if it exists. Once you find it, delete it and try again.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
I have a MacBook running Leopard. Qite a while ago, I installed DoubleCommand in order to be able to Forward Delete. I chose the enter key as the forward enter key. Everything has been working like a charm, until today when, fo no apparent reason that I could see, the enter key stopped functioning as assigned.
I removed DoubleCommand and checked the system for conflicting software, etc. It's all clean. So I tried installing. It gets right through to the last window to complete the installation process and says Install Failed. I did the operation again and got the same result. The message following the Install Failed message reads: "The following install step failed: run postflight script for DoubleCommand. Contact software manufacture".
Any ideas, please? And what is postflight script and where to I find it and how do I run it?
Thanks much
Emile
The postflight script is part of the installer package, but I haven't been able to find out why it is failing. If you run the installer, there is a menu item under the Window menu called Installer Log. If you open this and choose All Logs from the popup menu in that window, you could post the text from there and that might help solve the issue.
Thanks for this, but I can't even come up with what you siggested, i.e. finding the Installer Log. This is a real mystery. I think that my only real avenue is to re-install the OS. None of the sugestions seem to work.
Emile
Try the solution found in this thread:
http://sourceforge.net/forum/forum.php?thread_id=2045685&forum_id=221238
Particularly the part about /private/var/tmp.
If you are unable to find the DoubleCommand.crashed file in any of the locations listed in that thread, you can try this:
command+space to open spotlight.
Type in terminal and run the terminal application.
At the command line, type in: mdfind DoubleCommand.crashed | grep "DoubleCommand.crashed"
That should give you the location of the file, if it exists. Once you find it, delete it and try again.