July 21, 2009
6:35 p.m.
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