From: Isralewitz, Barry (
Date: Wed Feb 21 2024 - 12:06:57 CST

Hello Maud,

Thanks for the bug report. I have two questions:
1) Which version of macOS are you running?
2) Did you make any changes / upgrades to this machine -- including to the VMD bundle directory -- between the most recent successful (unaltered) VMD launch and when you encountered this bug?

  Also, a bonus question: were your colleagues who also encountered this problem using the same machine as you? If not, I'd be interested in the answers to questions 1) and 2) for one or two of them.

And, this request: could you send, as an email attachment , the version of startup.command that fixed the problem for you? I'm not following the differences and line breaks, versus the shipped version, in the edited version that you pasted in your email text.


On Feb 21, 2024, at 9:24 AM, Maud Jusot <> wrote:


It seems there is a bug when starting VMD (version 1.9.4 on MACOS ARM). It was working fine a few days ago but not anymore and was the same for a few colleagues. When running the application I got the following error:

Applications/VMD\<;!!DZ3fjg!7eKV6NDHVKgBpFKmy1-rNBYefCsakbmti334M2iYaKfy_0ukhZcooTCnmpUVZsZti52RAuUssQ-VuTjDl8sG$> ; exit;
zsh: no such file or directory: Applications/VMD<;!!DZ3fjg!7eKV6NDHVKgBpFKmy1-rNBYefCsakbmti334M2iYaKfy_0ukhZcooTCnmpUVZsZti52RAuUssQ-VuTjDl8sG$>


It seems the path is not recognized correctly anymore. To solve it, I simply edit the `startup.command` as follow:
#!/bin/sh # startup.command # This is the script executed by VMDLauncher to actually start VMD. p=`dirname "$0"` /"$p/../Resources/" $* '''

Hope this can help,


Barry Isralewitz
Theoretical and Computational Biophysics Group
3143 Beckman, University of Illinois at Urbana-Champaign
Work Phone: (217) 300-1988