Scratch disk & Memory usage
Patti
!st thing would be to get another 512M of memory, if possible. Elements itself isn't that resource hungry, it is when you start to use it.
Windows XP is considered 'bloatware', it hogs memory with a lot of what people would consider useless behind the scenes stuff, and could easily chew up more than half ofyour 256 just starting up. Everthing else you have plugged in and in your system tray will eat a little more. For example, my machine runs using over 200M, doing little more than warming the room up.
When you allocate a percentage of memory to use, you are saying 'take this much and let Elements use it'.
The possibility is you haven't got that much left, so windows will use its own swap file, where anything that is not being used at that particular time will get saved (sort of) to hard disk, when you need it again, it can reload from disk, when it has made room in memory by saving something else.
For example, if you dont move your mouse, it may save your mouse program to use the memory for something else, but as soon as you move your mouse, it has to swap it back into memory again. Probably why your hrad disk light is nearly constantly on.
Elements uses a scratch disk in much the same way. Picture files can get very large without you realising it. Every layer adds about the same size to the picture as it was when it was opened, for example if you open a 250K file, it may take up 1.5M of memory, add to that 6 more layers and a few resizes, you can end up with a 60-70M file before you know it (Ive got up to 800M and wondered why my machine was getting slow)
So, back to my first lines, the more physical memory you can squeeze in, the better it will be.
It's not a technical explanation, but I hope you get the idea.
Paul
|