<br><br><div class="gmail_quote">On Sat, Jul 16, 2011 at 8:07 PM, Philippe Marschall <span dir="ltr"><<a href="mailto:kustos@gmx.net">kustos@gmx.net</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Hi<br>
<br>
I have had the following experience. I'm running Pharo 1.3 on a Linux<br>
box where the time is set on start up using ntp. The hardware clock is<br>
set to the local time (because I'm dual booting). When there is no<br>
network connection during booting the system the clock is two hours<br>
"ahead" until I get network connection and set the time using ntp. When<br>
a Pharo image is running during this the UI freezes and doesn't react<br>
anymore. Does anybody else observe this? Is this a known limitation?<br>
<br></blockquote><div><br>Yes. It seems the known limitation of Cog VM that uses clock and something related to heartbeat and etc...When you change time you confuse Cog generating a freeze.<br>At least I remember that something like that could happens.<br>
Try with a non-Cog VM. <br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
Sorry if this message got sent twice. I had some trouble with the<br>
mailing list.<br>
<br>
Cheers<br>
<font color="#888888">Philippe<br>
<br>
<br>
</font></blockquote></div><br><br clear="all"><br>-- <br>Mariano<br><a href="http://marianopeck.wordpress.com" target="_blank">http://marianopeck.wordpress.com</a><br><br>