Ned,

We have never aimed at being able to run newer images on older VMs
flawlessly. This is simply because certain improvements require a later VM
than others. The other way around is different - you should certainly be
able to run an old image on a new VM (and that is true for the VM that I
just put out). Even right now you can see that (as I wrote in a message
before) a 3.0 image really wants a 3.0 VM. It'll work on an older VM but not
without flaws. The same has been true for pretty much any prior Squeak
version that included some improvement to the VM. Bottom line is: Run the
latest VM and everything should be okay. Do not run a newer image on an
older VM if possible.

Cheers,
  - Andreas

> -----Original Message-----
> From: Ned Konz [mailto:ned at bike-nomad.com]
> Sent: Sunday, February 04, 2001 7:19 PM
> To: squeak at cs.uiuc.edu
> Cc: recipient list not shown
> Subject: Re: [Win32] Preliminary 3.0 VM available
> 
> 
> On Sunday 04 February 2001 19:01, Raab, Andreas wrote:
> 
> > Currently, there is one known problem with the sound if 
> you're not using
> > the DSound version which is related to a Squeak side 
> problem. The attached
> > CS fixes the problem (it'll come in the update stream later).
> 
> Looking in the change set, it appears that you have to have 
> the code in the 
> image matching the VM; does this means that you can't use the 
> image unchanged 
> in VM's that don't support the ready semaphore? I can see 
> this causing 
> problems when people try to use older VM's with newer images...
> 
> UseReadySemaphore _ true.  "set to false if ready semaphore 
> not supported by 
> VM"
> 
> Is there any way to detect this VM capability from the image?
> 
> -- 
> Ned Konz
> currently: Stanwood, WA
> email:     ned at bike-nomad.com
> homepage:  http://bike-nomad.com
>