Two things:
(1) Even being in Australia and having to deal with the stupidly high costs for computer parts, I'd IMMEDIATELY go out and by virtually any used video card you can get your hands on. Literally anything made within the past 3 years as a dedicated card will be a big boost to your performance over an Intel 530. Go down to the local computer shop, and buy the cheapest 1GB VRAM video card you find - ask them if they've swapped out any from people upgrading, and buy that card. You should have no problem with finding one under $50 AUD (heck, I see some available NEW from on-line retailers shipping to Australia for less than that). That will immediately solve your problems.
(2) on modern OSes, including all flavors of Windows since Win2003, virtual memory works this way:
virtual memory = physical ram + swap file
All allocation is done into virtual memory, with no knowledge of where that memory page will actually reside. the OS itself then decides where to put the memory page based on two criteria:
- Is the page actually allocated for use, and not just "reserved" for future allocation?
- When was the last time the page was accessed?
In the case of memory pages actually accessed, the OS will put the most recently used ones in RAM, and, if there is no room left over, store the remainder on the swap file. In the case of "reserved" pages - ones the application says to allocate, but not use for the immediate future - these are put on the swap file. Reserved pages are really just markers that say "Hi, I'm going to be using this sometime in the future. You can't have this space." Reserved pages are increasingly rare; they were typical for huge memory hog apps like Photoshop in the 32-bit era, but in the 64-bit era, they're virtually useless, and thus, apps don't do it.
Should there be more RAM than the sum total of all allocated pages in use, the OS will use the remaining RAM as a file cache. This file cache will be evicted immediately upon any memory pressure (i.e. memory being allocated in excess of the existing total).
The long and short of this is this: for modern systems under ordinary desktop use, you should NEVER need a swap file. If the OS is having to swap, you're taking a enormous (i.e. 10,000x) performance hit. Your RAM should *always* be sufficient to run all the apps you need; if it isn't, BUY MORE RAM. You should have a swap file for two reasons: (a) if you want to do a crash dump, you have to have sufficient swap space to store the entire contents of RAM, or (
you still have certain apps that reserve but don't allocate a significant amount of RAM. JavaVMs are a prime example of this right now.
In case (a), you need a swap = RAM. In case (
, you need swap sufficient enough to hold the reservation amount. Which probably is no more than a few GBs.
TL;DR: you shouldn't need a swap file at all on a modern desktop system. At most, 1-2GB is sufficient, regardless of system RAM (because, who actually looks at crash dumps?) If you detect swapping, BUY MORE RAM. It's that simple.