The 2Gb limit has nothing to do with where the image is stored. The limit is in the image itself. The image on the SSD drive cannot be your working image because Pharo works on a *copy* of the image, not on the image itself. That is by design - otherwise you wouldn't have the possibility to rollback to a last saved image.
On 14 January 2012 14:08, Guido Stepken <[email protected]> wrote: > Why can't i take a SSD drive as Image? 2 GByte limit automatically falls? > Am 14.01.2012 13:10 schrieb "Milan Mimica" <[email protected]>: > > On 14 January 2012 12:13, Guido Stepken <[email protected]> wrote: >> >>> IS there still a "Image" neccessary in Smalltalk then? Or has this >>> former "design approach" nowerdays rather significant disadvantages? (32 >>> Bit, hanging IO during sync, GC....) >>> >> >> As I see it, image is not something that has to reside in physical RAM, >> but it is necessary in Smalltalk. >> >> >> -- >> Milan Mimica >> http://sparklet.sf.net >> > -- Milan Mimica http://sparklet.sf.net
