Sorry, I hit "send" by accident. What I meant to say is that the
interpreter VM may get you past the crash that you experienced, or it
might just crash differently. If you have the patience you can give it a
try and see if it helps.

Either way, I'm pretty sure that the problem is in the update stream as
opposed to the VM.

Dave

> Hi Jeff,
>
> Nice to see you on the list, and sorry for not responding earlier.
>
> I am fairly sure that we had some things screwed up in the update stream
> (since resolved) and you are experiencing the effects of that. I have a
> feeling that most of us working with trunk images we are keeping up to
> date with the stream, and we may have neglected to go back and fix up
> whatever update maps needed to be patched in order to work around the
> problem.
>
> I don't know if this will make any difference, but the latest version of
> the traditional interpreter VM for Windows is at
>
> http://www.squeakvm.org/win32/
> http://www.squeakvm.org/win32/release/Squeak4.10.2-2612.win32-i386.zip
>
>
>> Hi Folks,
>>
>> Just wanted to PING the list again to see if anyone had any feedback.
>> Am I just seeing a crash that no one else is seeing and it is
>> something with my setup, is there a safe VM version that people are
>> using to update from the trunk image, and is anyone else able to grab
>> the image that Marcel posted and do a successful update on the trunk?
>>
>> I am just playing around with the image Marcel posted and it is just
>> fine for getting work done, but my OCD tendencies flare up a bit
>> knowing that I am not working with fully updated code.
>>
>> Any help or at least just letting me know that this is a problem on my
>> end rather than the trunk would be greatly appreciated.
>>
>> Thanks,
>> Jeff
>>
>
>
>