Hi Martin,<div><br></div><div>� � would you please try with both the Croquet.exe and the CroquetConsole.exe in�<a href="http://www.mirandabanda.org/files/Cog/VM/VM.r2540/cogwin.zip">http://www.mirandabanda.org/files/Cog/VM/VM.r2540/cogwin.zip</a>?. �The CroquetConsole.exe is designed to be used from the command line; stupidly Windows has this distinction between console apps and windows apps, and this distinction affects standard i/o. �If CroquetCOnsole works then the implication is that Pharo needs also to build both VMs and the user needs to select the console VM for console use and the Windows VM for detatched use.</div>
<div><br></div><div>HTH</div><div>Eliot</div><div><br><div class="gmail_quote">On Sun, Apr 8, 2012 at 4:31 PM, Martin Dias <span dir="ltr">&lt;<a href="mailto:tinchodias@gmail.com">tinchodias@gmail.com</a>&gt;</span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>Hi</div><div><br></div><div>In my windows 7, I get�an error when trying to write to &quot;FileStream stdout&quot; in both Pharo 1.4 and 1.3 (revisions�#14423�and #13320).</div>
<div><br></div><div>To reproduce,</div><div>

<br></div><div>- download:�</div><div><a href="https://ci.lille.inria.fr/pharo/job/Pharo%201.4/373/artifact/Pharo-1.4.zip" target="_blank">https://ci.lille.inria.fr/pharo/job/Pharo%201.4/373/artifact/Pharo-1.4.zip</a></div>
<div><br></div>

<div>- evaluate:�</div><div>FileStream stdout nextPutAll: &#39;a&#39;.</div><div><br></div><div>Is this a known issue? I couldn&#39;t find it in issue tracker.</div><div><br></div><div>Thanks in advance.</div><div>Mart�n</div>



</blockquote></div><br><br clear="all"><div><br></div>-- <br>best,<div>Eliot</div><br>
</div>