I have just set up a new desktop that came loaded with Vista. It has 2.0GB of Memory and 320GB Hard Drive. I loaded my old Adobe Photoshop Elements 2.0 from the original CD but when I try to open it I get this message:

"Could not start Adobe Photoshop because the volume Windows is using for Vitual Memory does not have enough free space, which could lead to stability problems. See Windows Help for info on increasing available virtual memory"

I´m stunned. My old laptop (with XP) had 1GB of memory 100GBHard Drive and had no trouble with A P. Can anyone explain this to me and do I have to go out and buy something to increase the Virtual Memory?

I don't think the problem is lack of virtual memory, but incompatibility with Vista, after all this is a very old program.

Ok that makes sense. I had fits trying to install an older printer and scanner.

What you can try is right click on the app and choose Run as Admin
See if this helps

Try this:

START
Control Panel
System
Advanced System Settings
Advanced tab
Performance Settings
Advanced
Change
Unclick "Automatically manage paging file size for all drives"
Click on the drive you want to change, typically 'C'
Click on "System manage size"
Click on "Set"
Get out and reboot
Adobe Elements 2.0 should start

Try this:

START
Control Panel
System
Advanced System Settings
Advanced tab
Performance Settings
Advanced
Change
Unclick "Automatically manage paging file size for all drives"
Click on the drive you want to change, typically 'C'
Click on "System manage size"
Click on "Set"
Get out and reboot
Adobe Elements 2.0 should start

I would NOT recommend this suggestion. Hardcoding the virtual memory "brick" to 2.5 times your real installed RAM is more than sufficient, resulting in no overhead waiting for the operating system to resize virtual memory/swap space.

This works on my computer (Dell Latitude D830, Vista Business, 4GB RAM) and I've had no problems. If you are not recommending it, what solution are you recommending (besides buying Elements 7)?

The OPs question has most likely been resolved by SeaHawk's recommendation.

Feel free to open another thread where we can discuss Swap Space methodology without hijacking this thread.