Hi all,<br>Thanks for your answers... I will try every one (I really need to get back those objects)...<br>I think Ale is right and I made a mistake not been modular in my application... but now is to late :( <br>After recover all (if it is possible), I will try some modularization... which way do you recomend? ImageSegments seems the right one, but I really don't know how to use it...
<br><br>Thanks again,<br>Esteban<br><br><div class="gmail_quote">On Nov 28, 2007 10:48 AM, Alejandro F. Reimondo <<a href="mailto:aleReimondo@smalltalking.net">aleReimondo@smalltalking.net</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Esteban,<br><br>If you has not compressed the changes file, the code can be recovered from<br>there with a change set browser.<br>In case it is not your situation and you need to dump some<br>objects/information actually inside the image...
<br>Do you know how to build a VM ? (compile a patched VM to run your image)<br>If you know how to doit, you can patch a primitive you are sure it is called<br>by your image before crashing and try to activate another process running an
<br>evaluation of the code you want to evaluate to dump your code & objects (or<br>repair the image, the last changes -after last recorded saveImage- can help<br>you to know what has you broken there).<br>I wish you good luck!
<br><br>The situation you have now IMHO is good to learn that working saving the<br>image is not a convenient way to work (you have reached one of the<br>situations that reveals this fact). It is reccomended to work investing
<br>efforts in modularization. From now you can evaluate the risks of investing<br>efforts only in saving your image.<br>The construction of modular systems requieres little efforts as demostrated<br>for more than a decade and let you be sure that parts of your system can be
<br>assembled without risks (consider each time that a module is assembled in an<br>image a test of conformance of the assembly energy requiered to put your<br>parts in another system).<br>If you work with your objects in (only) one image, you can construct a
<br>system and learn a lot about the domain from doing that, but doing that way<br>will not face you to the costs of putting your parts in the context of other<br>image(s).<br>The efforts put in modular composition of subsystems is related with this
<br>facts (energy requiered to assemble a system from its "parts") and not with<br>sharing goodies with other people. If you consider modularity you will also<br>evade the risks of loosing time, work and make your framework more
<br>appropiate to be bound to other image(s).<br><br>cheers,<br>Ale.<br><div class="Ih2E3d"><br><br>> 2007/11/27, Esteban Lorenzano <<a href="mailto:estebanlm@gmail.com">estebanlm@gmail.com</a>>:<br>>> Hi all,
<br>>> I have an image that is not working anymore, and I can not take control<br>>> from<br>>> that (the image starts, but i can't press any key, not even cmd+.)<br>>> Is there a way to load the image (as an ImageSegment or something like
<br>>> that)<br>>> so I can recover the objects I need?<br>>><br>>> Thanks in advance,<br>>> Esteban<br>>> --<br>>> "Querer es suscitar las paradojas"<br>>> Camus. El míto de Sísifo.
<br>>><br>>><br>>><br>><br>><br>> --<br>> Damien Cassou<br>><br><br><br></div>--------------------------------------------------------------------------------<br><br><br>><br>><br><br>
<br></blockquote></div><br><br clear="all"><br>-- <br>"Querer es suscitar las paradojas"<br>Camus. El míto de Sísifo.