Fuzzlepeck_ wrote:
I do sometimes get a message on start up that the SYSTEM 32 file is corrupted, and to reboot from disc. But after turning off & on again it works, so I don't know if that *would* have something to do with it. I didn't get that today though.
Your system is likely corrupted/broken (broken files...). You can't really expect Gimp to work nicely in these conditions. Gimp is the first to demonstrate the problem because it stresses the system a bit more than other applications.
Asseime the aboce is fixed, if the troule persists: if gmem.c can't allocate memory, it's because Windows won't give it the memory to allocate, so:
- check in the process manager for any sign of memory exhaustion (available Free memory very small). How much memory is Gimp using?
- check that you have virtual memory enabled, and enough disk space to support it
- see if the problem is specific to a given image (or does it occur at startup?)