Dan Ingalls wrote:
If you want to keep working in an old image, and yet track the updates to 2.1, then execute the following line after fetching updates in your 2.0 image...
EToySystem eToyVersion: 'Squeak2.1' date: Date today
... and save it. Poof, you now have a system that thinks it is 2.1. Note however, that the next update you download will want the new VM, so you should definitely retrieve that asap (although almost everything will continue to run just fine on an old VM).
I just followed the instructions for making my Squeak 2.0 Win32 image 'think' it was 2.1, and then auto updated the latest changes. As we do not yet have an updated VM for 2.1 on Win32 (do we?), I used the existing VM. Bad things happened immediately. (In particular, the image hangs when entering a project, for example. A manual interrupt shows that the image is repeatedly halted with 'bad bitblt arg (fraction?) proceed to convert'). Given the nature of the released 2.1 changes, I suspect that either I have missed a step somewhere, or that we really do need the 2.1 VM before incorporating the 2.1 updates on Win32.
I might suggest that others on Win32 hold off a bit until a 2.1 VM is available, or the problem is otherwise resolved.
-- Matt Rosen, Director for Technical Services San Joaquin Delta College
Matt (and all) -
I just followed the instructions for making my Squeak 2.0 Win32 image 'think' it was 2.1, and then auto updated the latest changes. As we do not yet have an updated VM for 2.1 on Win32 (do we?), I used the existing VM. Bad things happened immediately. (In particular, the image hangs when entering a project, for example. A manual interrupt shows that the image is repeatedly halted with 'bad bitblt arg (fraction?) proceed to convert'). Given the nature of the released 2.1 changes, I suspect that either I have missed a step somewhere, or that we really do need the 2.1 VM before incorporating the 2.1 updates on Win32.
I might suggest that others on Win32 hold off a bit until a 2.1 VM is available, or the problem is otherwise resolved.
Thanks for your alert!
I apologize for suggesting that this should be simple. I thought it would only be a problem with text flow in odd containers (which could happen if you entered a couple of the PlayWithMe projects), but I didn't check it carefully.
I will look at this in detail, and try to put together a little "forward compatibility" package that would let you go forward without a new VM (unless new VMs get relased first (and they will be backward compatible)).
- Dan
existing VM. Bad things happened immediately. (In particular, the image hangs when entering a project, for example. A manual interrupt shows that the image is repeatedly halted with 'bad bitblt arg (fraction?) proceed to convert').
I downloaded the fresh 2.1 image and ran into the same problem. I haven't investigated what went wrong, but the following fix helped me to play the SameGame (which is great and addicting btw).
It seems that there's an unknown combinationRules no 33 which let's the bitblt primitive fail. A simple
combinationRule = 33 ifTrue: [^self]
just before the
self halt: 'Bad BitBlt ...'
line seems to work around that problem. I've no idea what combination rule 33 is, but the system seems to run fine without that, too.
bye -- Stefan Matthias Aust // Are you ready to discover the twilight zone?
squeak-dev@lists.squeakfoundation.org