Quoting Alain Rastoul <[email protected]>:
Le 13/05/2015 16:08, J. Vuletich (mail lists) a écrit :
Today I did a new commit to the Cuis repo. The Cuis image is now in Cog
format (6505) instead of Closures format (6504). I hope this allows you
to run Cuis in your system.
I also addressed some of the issues you raised. I optimized the refresh,
and avoided the "bolder text" effect.
Now,
Time millisecondsToRun: [ 1000 timesRepeat: [ Transcript show: 'x'
] ].
takes 2 ms, even while updating the Display. (Hundreds of times faster).
Thanks Juan
It's nice to see how reactive you are :)
Thanks. Also thanks for trying and reporting your experience. This
lets me solve any issues!
I downloaded the Cuis-4.2-2322 image but still have the same error
message : This interpreter (vers. 6505) cannot read image file
(vers. 1007290890).
The cuis image number looks strange.
Is this image supposed to be in 6505 format ?
Mhhh. Maybe it is a problem with downloading the file. I guess you
cloned https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev , right?
Maybe Git thinks it needs to mess with the files? Please try getting
the zip file
https://github.com/Cuis-Smalltalk/Cuis-Smalltalk-Dev/archive/master.zip and
unzipping it.
Alternatively, try getting the image file from
https://dl.dropboxusercontent.com/u/13285702/Cuis4.2-2322.image
What version of squeak vm do you use ?
I'm using a Squeak 4.5 vm who runs perfectly on this system (linux
ubuntu 14.04).
I tried with other older vms but always got this error (only the
6505 number changed IIRC)
--
Regards,
Alain
Cuis4.2-2322.image was saved with a relatively recent Windows Cog VM
from Eliot's site. All previous Cuis images were saved with
Squeak4.10.2-2612.exe from squeakvm.org. Always on Windows 7.
I run them under Debian Jessie with Eliot's coglinux all the time
without problems.
The number you get 1007290890 is 16r3C0A0A0A... Those bytes are not
there in the header in the image file I have. The first bytes of the
image file should be 69 19 00 00 (in hex). This is 6505 in decimal.
That's why I suspect of a problem with the image file itself, and
maybe a problem with git. Those 0A bytes are LF characters... Maybe
git is trying to be "smart" and converting or adding LF characters to
what it thinks is text?
Regards,
Juan Vuletich
