From: John Stone (
Date: Sat Mar 24 2007 - 17:06:09 CDT

  The script you included below is still missing the command I suggested
that you add. I'd also suggest putting a "puts" command prior to
the foreach to make sure you don't have any other errors in your script,
and that it is indeed loading the *.tcl files in the directory you
have specified. The very fact that your commands are still undefined
indicates to me that one of these steps isn't working, but you haven't
yet debugged why not. Add this command to the beginning of your vmd.rc
file on Windows, to make sure it's running at all:
  puts "Running custom VMD startup scripts..."

If you don't see that message when VMD starts up, then your vmd.rc
file isn't being loaded and that would explain why your extra
commands aren't being found. Please check this and let me know
what the results are, as well as whether or not you're seeing
the messages from the other puts that I suggested adding to your
foreach loop.

  John Stone

On Sat, Mar 24, 2007 at 02:39:43PM -0700, Zheng Hu wrote:
> Hi John,
> Thanks for your reply. I have put the following script you suggested in the vmd.rc file. But when I input the command I defined in the VMD Tk console, it still tells me "invalid command name". It seems that the script cannot be loaded automatically. There should not be errors in the script file since it works well in linux version VMD. Besides modify vmd.rc file, do I need to do something else in order to automatically load a script file to windows version VMD?
> # command extensions
> foreach ext [glob -nocomplain C:/vmdextensions/*.tcl] {
> source $ext
> }
> unset ext
> Thanks,
> Zheng
> ---------------------------------
> Don't pick lemons.
> See all the new 2007 cars at Yahoo! Autos.

NIH Resource for Macromolecular Modeling and Bioinformatics
Beckman Institute for Advanced Science and Technology
University of Illinois, 405 N. Mathews Ave, Urbana, IL 61801
Email:                 Phone: 217-244-3349
  WWW:      Fax: 217-244-6078