Pagefile (or Virtual memory) can be a real pain if not set up right. It
should be at least 1.5 times the actual memory. At windows installation it is
set to 1.5 times actual memory by default and this is OK. If you increase the
physical memory size, windows does not necessarily increase the Pagefile
size. Check as follows:

Windows XP: Open Control Panel - System - Advanced Tab - Performance
Settings - Advanced Tab

Windows Vista: Open Control Panel - System - Advanced System Settings -
Performance Settings - Advanced Tab

Check the size of the virtual memory and change to at least 1.5 times your
actual physical memory. That is 1500MB if you have 1000MB (1GB) memory.

Also lookup pagefile in windows help and see if any if the things mentioned
there could apply to your situation.

I am not full bottle on all the reasons but I am told that if there is
insufficient space in the Pagefile to temporarily hold all the actual memory,
windows swaps it out in dribs and drabs and it takes forever; but don't quote
me on that because it is only hear say.

Also note the other replies because it could be any reason.

--
Regards,

OssieMac


"LunaMoon" wrote:

Hi all,

I am using Excel 2003 for some project.

I am having 2GB C drive harddisk space.

After a while, the Excel begins to be extremely slow in copy and
paste...

It takes about half an hour to copy and paste just a few cells...

I've consulted people. It seems a memory problem.

But I cannot close my windows and kill the processes, because I am
running long-running (overnight) jobs...

I cannot reboot either.

Is there a way to clean the memory and let Excel 2003 clipboard
function properly without rebooting or killing my 4 long-running
processes?

Thanks!

p.s. I am sure this is an issue due to the special clipboard feature
of Excel 2003. It's very weird, is there a way to get rid of that
feature?

When the copy&paste was hung, I also checked the task manager, and
found no CPU usage for this particular operation, every single
copy&paste will cost me 30 minutes. And my colleagues are having the
same problem.

They say the only way out for them was to reboot...

How stupid is Excel 2003!