I think I have it willing to keep running now. I looked for the #inform: in the process browser, and missed it the first time - I needed to ask for the full stack, and there it was, a good long way down the list :) It is now sending text to the transcript, so cross your fingers. Bill -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Schwab,Wilhelm K Sent: Tuesday, July 21, 2009 2:22 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Show stopper network bug on Windows It's trying to run on a win2k3 box. I say trying because it insists on telling me (modally) how many updates it processed - every time. Is there a way to gag that? Bill -----Original Message----- From: pharo-project-bounces@lists.gforge.inria.fr [mailto:pharo-project-bounces@lists.gforge.inria.fr] On Behalf Of Stéphane Ducasse Sent: Tuesday, July 21, 2009 1:36 PM To: Pharo-project@lists.gforge.inria.fr Subject: Re: [Pharo-project] Show stopper network bug on Windows Yes we do not have a windows at hand. can you let us know from which update the problem is related.
In this case the first step woud be to identify which update introduced the problem.
Suppose that a core #10200 image still works, you could do:
10200 to: 10384 do: [ :i | Utilities updateFromServerThroughUpdateNumber: i. NetNameResolver localHostAddress ]
And then see after which update number the first exception is thrown. I did not test this, but it should work.
Adrian
_______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project _______________________________________________ Pharo-project mailing list Pharo-project@lists.gforge.inria.fr http://lists.gforge.inria.fr/cgi-bin/mailman/listinfo/pharo-project