VMD-L Mailing List

From: Dan Lussier (dtlussier_at_gmail.com)
Date: Sun Apr 05 2009 - 09:40:26 CDT

I am attempting to use the 1.8.6 version.

When I attempt to open the disk image I get the following.

"The disk image you are opening may be damaged and could damage your
system. Are you sure you want to open this disk image?"

If I go ahead and mount the disk image after attempting to repair it
through Disk Utility and then pull the VMD app bundle to my
Applications directory it appears to be working today (app starts and
can run simple examples).

Yesterday when I sent my original email to the list this wasn't the
case and the app wouldn't run. I don't know how to explain this,
which definitely raises the chances that my configuration is at fault.

That being said - I wanted to flag up the warning coming from the disk
image mounting process in case other OS X VMD users are seeing the
same thing.

Dan

On 5-Apr-09, at 3:05 PM, Axel Kohlmeyer wrote:

> On Sun, 2009-04-05 at 09:02 +0100, Dan Lussier wrote:
>> I just wanted to flag up a potential problem with the OS X intel
>> binary of the most up to date version of VMD.
>
> dan,
>
> please be a little bit more precise. are you talking about the
> release version 1.8.6 or one of the alpha test versions?
>
>
>> I have tried downloading it a couple of times without success.
>> When I
>
> well, if you do the identical (=correct) steps, a computer should
> produce identical results. so repeating the same thing without
> modifications _should_ produce the same result. ;)
>
>> try to mount the disk image I get an error warning that there is a
>> problem and then once the disk image is mounted the app simply
>> doesn't
>
> well, _what_ is the problem that is being reported.
>
>> run. If I try mounting and re-mounting the same disk image a second
>
> the installation instructions say that you have to drag and
> drop the application to an appropriate location. did you do that?
>
>>
>> time I get an error ("Incorrect codec" ) and can't even get it to
>> mount.
>
> hmm... that looks more like there is something misconfigured in your
> machine rather than
>
>> I only have a single Mac here so I can't try it on another machine
>> but
>> my hardware specs are fairly typical (if it is significant to the
>> problem):
>
> it is very unlikely that it is a hardware problem, but rather
> something
> on the software side. whether this is pertaining to VMD or your setup,
> that is very hard to determine.
>
> cheers,
> axel.
>
>> MacBook Pro
>> 2 GB RAM
>> 2.4 GHz Core 2 Duo
>> OS X 10.5.6 fully updated
>>
>> Thanks,
>>
>> Dan
>
> --
> =
> ======================================================================
> Axel Kohlmeyer akohlmey_at_cmm.chem.upenn.edu http://
> www.cmm.upenn.edu
> Center for Molecular Modeling -- University of Pennsylvania
> Department of Chemistry, 231 S.34th Street, Philadelphia, PA
> 19104-6323
> tel: 1-215-898-1582, fax: 1-215-573-6233, office-tel: 1-215-898-5425
> =
> ======================================================================
> If you make something idiot-proof, the universe creates a better
> idiot.
>