W2k with 768mb ram and getting virtual memory errors

[Davegod75]

I'm running w2k pro at the momment and I have 768mb ram so i figured i could set my page file really small. I chose 20mb. However, I'm getting errors that say "your low on virtual memory so windows is increasing it"

When it does this sometimes i'm only surfing and using like 100mb ram of my 768mb. So obiviously i shouldn't be getting these errors.

Is there anyway to force w2k to use my ram and not look at the paging file at all?

ps the only reason i didn't set it to 0 to begin with is that wk2 requires at least 2mb and some applications won't run if they detect your paging file to be too small.

thanks

 

[HexVector]

No, Windows 2000/XP likes to have a pagefile at all times. Disabling is not recommended. Just set it to something like 200MBs and it will be fine.

It doesn't work like 9x/ME where you could actually disable it and resort to using RAM exclusively.

 

[SanDiegoPaul]

I'm running w2k pro at the momment and I have 768mb ram so i figured i could set my page file really small. I chose 20mb. However, I'm getting errors that say "your low on virtual memory so windows is increasing it"

---

It's a huuuge! jump from what W2K defaults to, which is 1.5 times the RAM amount. I have 512MB of RAM and also run a static swap file ... but I have it set to 500MB

-- Just my two cents

 

[Nothinman]

Is disk space really that tight for you? Set it to like 200M and leave it.

 

[Davegod75]

it's not disk space i'm complaining about. I just don't was wk2 storing stuff on disk or whatever when it could be using ram.

 

[Saltin]

Then set your pagefile to a less than 1:1 ratio.
Don't try to disable it, whatever you do, and don't set it to a tiny number like 20mb.
People will tell you it's ok to disable your page file. I've worked on this problem for quite some time in a lab at work as a side project (out of interest). It is unstable and performance gains are negligable.