Hi I am running:
squeak ./my-image
and get: This interpreter (vers. 6502) cannot read image file (vers. 544830578).
My image was likely opened on Windows , the above message is from Linux I think all my VMs are fairly recent , within about 2 years (I can provide them later, right now I do have access to the Windows VM that saved the image).
Was there a recent (I mean perhaps last 2-3 years) VM change that would create incompatibility of images as to which VM versions can be used to open them? Or perhaps, can this be a siggn the image is corrupted?
Thanks Milan
On Sat, Jul 12, 2008 at 09:43:28AM +0000, Milan Zimmermann wrote:
Hi I am running:
squeak ./my-image
and get: This interpreter (vers. 6502) cannot read image file (vers. 544830578).
My image was likely opened on Windows , the above message is from Linux I think all my VMs are fairly recent , within about 2 years (I can provide them later, right now I do have access to the Windows VM that saved the image).
Was there a recent (I mean perhaps last 2-3 years) VM change that would create incompatibility of images as to which VM versions can be used to open them? Or perhaps, can this be a siggn the image is corrupted?
Milan,
Yes, it is a sign that the image is corrupted. The "version" that the interpreter is talking about is intended to refer to 64 bit images as opposed to normal 32 bit images, but in this case you have almost certainly got a bad image file. You have been moving images between different operating systems, so the most likely cause is that a zip utility or ftp file copy has mistakenly treated the binary image file as if it were text, and thus "helped" you by trying to convert line ending characters.
Dave
Thanks David,
I agree it is likely corruption. It has not been compressed, but transfered via USB stick, I think it was unmounted safely but anyway, I'll take it on Monday to work to the Windows Squeak where it was created and confirm it does not load. If it does .. well we'll see
Thanks Milan
On 2008 July 12, David T. Lewis wrote:
On Sat, Jul 12, 2008 at 09:43:28AM +0000, Milan Zimmermann wrote:
Hi I am running:
squeak ./my-image
and get: This interpreter (vers. 6502) cannot read image file (vers. 544830578).
My image was likely opened on Windows , the above message is from Linux I think all my VMs are fairly recent , within about 2 years (I can provide them later, right now I do have access to the Windows VM that saved the image).
Was there a recent (I mean perhaps last 2-3 years) VM change that would create incompatibility of images as to which VM versions can be used to open them? Or perhaps, can this be a siggn the image is corrupted?
Milan,
Yes, it is a sign that the image is corrupted. The "version" that the interpreter is talking about is intended to refer to 64 bit images as opposed to normal 32 bit images, but in this case you have almost certainly got a bad image file. You have been moving images between different operating systems, so the most likely cause is that a zip utility or ftp file copy has mistakenly treated the binary image file as if it were text, and thus "helped" you by trying to convert line ending characters.
Dave
Beginners mailing list Beginners@lists.squeakfoundation.org http://lists.squeakfoundation.org/mailman/listinfo/beginners
beginners@lists.squeakfoundation.org
-
David T. Lewis -
Milan Zimmermann