From: John Stone (
Date: Thu May 17 2007 - 12:21:26 CDT

  Which version of VMD are you using? It sounds like you've
found a bug in the VMD parm or parm7 plugin. Can you send me
a gzipped copy of of the files that causes this to occur?
Its possible that some of your file transfers are corrupting the
parm files, and others are not, but even so, the plugin should
gracefully handle these situations and not crash VMD which it
seems is what is happening presently. If I can reproduce your
problem it should be pretty easy to solve.

  John Stone

On Thu, May 17, 2007 at 12:47:04PM -0400, Stern, Julie wrote:
> When I try to load a prmtop or a pdb which I have winscp3'd over from certain machines
> but not others I get the error in its own window:
> The instruction at "0x000412e95" reference memory at "0x00000000". The memory could
> not be"written." Click OK to terminate program.
> This only happens upon transfer from some machines and not others. The prmtop is
> functional and usable as it generates the MD results. I just need to be able to look at them.
> Any ideas on what do I do?
> Thanks.

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