From: Robert Brunner (
Date: Fri Jul 08 2005 - 15:17:02 CDT

That file is startup.command, in

The extension .command normally denotes a file that is supposed to be
run using the program. Your machine must be configured
to instead open .command files with TextEdit.

To fix:

- Locate your copy of VMD
- Hold down Control and click on VMD to bring up the contextual menu.
Select Show Package Contents
- Navigate to Contents/MacOS and Control-click on startup.command
- Select Get Info
- Presumably, the Get Info window will show "Open with: TextEdit".
Change this to Terminal. If Terminal isn't listed, select Other...
and locate Terminal in /Applications/Utilities
- Usually you want .command files to open in Terminal, so you
probably should (unless you know some other reason to refrain) also
click the "Change All..." button, but this should not be necessary to
make VMD work.

Then you should be able to relaunch VMD, and it should work.

Good luck,

On Jul 8, 2005, at 11:20 AM, Miguel Valvano wrote:

> I installed Vmd 1.83 as per instructions. After copying .app file
> into my directory and launching the application, a screen from Text
> edit appears with the following:
> #!/bin/csh
> # Determine the bundle's path
> set pwd="$PWD"
> cd "$0:h/.."
> set vmdappdir="$PWD"
> cd "$pwd"
> # XXX no longer needed, we have this coded into the libraries and
> executable now
> # setenv VMDDIR "$vmdappdir/vmd"
> # setenv DYLD_FRAMEWORK_PATH "$vmdappdir/Frameworks"
> # Set mac-specific environment variables to make work correctly
> # setenv VMDMACEXEC "$vmdappdir/Resources/"
> # source "$vmdappdir/"
> # Launch vmd
> "$vmdappdir/Resources/" $*
> and nothing else happens.
> Any advice?
> Thanks

  • application/pkcs7-signature attachment: smime.p7s