For the record, here is the organization of those files: 1) the .image file > the object memory in binary form. You read it from disk and the VM continues executing the bytecode where it left off (basically picking up the instruction and stack pointers to do so). It is kind of like the hibernate file in Windows.
2) the .changes and .sources files > text files with sources and in the changes, what you typed got appended. It is always possible to take a fresh Pharo image and replay stuff from the .changes file to get back to the same state (useful if one image becomes corrupted). Phil 2013/3/11 Mohammad Al Houssami (Alumni) <[email protected]> > Isnt this the way to open the image file? I'm using the pharo virtual > machine to open it… > Im not sure I understand how I can be loading it as a text file. **** > > ** ** > > **** > > ** ** > > ** ** > > Thanks again **** > > Mohammad**** > > -----Original Message----- > From: [email protected] [mailto: > [email protected]] On Behalf Of Hilaire Fernandes > Sent: Monday, March 11, 2013 2:10 PM > To: [email protected] > Subject: Re: [Pharo-users] Pharo .image loading issues. > > ** ** > > Heu, it looks like you try to load the bytcode pharo .image as a text file > in Pahro. It does not make sense.**** > > Only the Pharo VM can interpret this image, so it should be open with the > Pharo VM.**** > > ** ** > > ** ** > > ** ** > > Hilaire**** > > ** ** > > ** ** > > Le 11/03/2013 12:21, Mohammad Al Houssami (Alumni) a écrit :**** > > > Hey Hilaire,**** > > > **** > > > **** > > > **** > > > What I was doing is going to the image file and opening it using pharo.* > *** > > > That exactly Is by right click--> open with --> pharo.**** > > > Draging the image into pharo also it says the following : File **** > > > 'HTML5.PARSER.image' is 20849204 bytes long.**** > > > **** > > > You may use the 'get' command to read the entire file.**** > > ** ** > > ** ** > > ** ** > > --**** > > Dr. Geo http://drgeo.eu**** > > ** ** > > ** ** > > ** ** > > ** ** > > -----**** > > No virus found in this message.**** > > Checked by AVG - www.avg.com**** > > Version: 2013.0.2904 / Virus Database: 2641/6163 - Release Date: 03/10/13* > *** >
