Yes, i agree with your analysis.
As the original is very old , is probably saved in a G4, so big endian.
The 3.10.2 which do not have this problem uses the JMM Squeak 4.2.5beta1U which runs on both G4 and Intel Macs.
No idea if how many projects could be valuable to rescue.
Is not a problem,

Thanks 

> On 29 Jun 2018, at 18:44, David T. Lewis <lewis at mail.msen.com> wrote:
> 
> Squeak images are saved with the native byte ordering of the machine
> from which they were saved (https://en.wikipedia.org/wiki/Endianness <https://en.wikipedia.org/wiki/Endianness>).
> I believe that this is true of image segments also.
> 
> The platforms that we use today (Linux, Windows, OS X) are all little-endian,
> but the older Mac machines were big-endian. If the project was originally
> saved from a Mac, then it was probably saved in a big-endian format.
> 
> It is possible that Squeak has lost the ability to handle big-endian
> images, and it may be that projects saved from older Macs cannot be
> loaded into Squeak today.
> 
> If that is the case (and I am only guessing), then a possible workaround
> would be to load the old projects into an old Squeak image, save the
> project again to a new file, and then load that new project file into
> a modern Squeak image.
> 
> Dave

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.squeakfoundation.org/pipermail/squeak-dev/attachments/20180629/305a4b57/attachment.html>