On Sat, 01 Jan 2005 20:21:47 -0800, Tim Rowledge <tim at sumeru.stanford.edu>  
wrote:

> "Yar Hwee Boon" <hboon at motionobj.com> wrote:
>
>> I posted a similar error before. Not sure if it is related, but I had  
>> been
>> using the 3.6 VM with a 3.7 image. When I switched to the 3.7 VM
>> (windows), the problem seem to go away.
> It is absolutely related. It's nothing to do with particular VMs as
> such, nor cpu architecture (well....) but all to do with the OS and
> it's approach to allocating memory.

Just to clarify - do you mean that the switch to a 3.7 VM should not be  
the reason that the problem goes away?

-- 
Regards
HweeBoon
MotionObj