Hi,
Just to reiterate this again, it doesn't really matter how much RAM you have in terms of what you can do with TG2. Having more RAM will increase the speed of certain things, but how much RAM TG2 can use is controlled by the operating system and normally that limit is 2 GB on 32 bit Windows. If you have less RAM than that the OS uses virtual memory, which basically means that it uses your hard drive as another place to store information in memory. Even if you only have 64 MB of RAM, if the there is enough space on your hard drive you can still use up to the 2 GB limit, because the OS will read and write any extra on your hard drive. It is much faster for the OS to read and write in your RAM though, which why having more RAM is a good thing. That's a simplistic overview, but it is basically how things work.
In this particular case, the size of each image TG2 is trying to load is 384 MB. You have 3 of them, for a total of 1152 MB. That may seem like it's well within the 2 GB limit, but it depends how much other memory is being used. Last time I checked TG2 allocates some fairly large blocks of memory when it starts up. One thing I've found with Windows is that it doesn't seem to like creating many large blocks of memory. I have a memory tester function in the debug version of TG2, and on Windows I find I can't allocate so many big blocks as I can on OS X, for some reason. It may be that there is memory being used which is scattered across the entire space of memory TG2 can use, and that is preventing it from being able to allocate one big block, even though if you added up all the free space it would be enough.
It's actually unnecessary to load all the image data into memory at one go. TG2 should be more intelligent and cache the image data on disk until it's needed. This will be slower than storing it all in RAM, but it would let you do more. It's a tradeoff really. We will have to look into making the image loading system more intelligent.
Regards,
Jo
