Currently have 256mb, should I jump to 768mb?

[LoStZ]

Well like mentioned, I currently have 256mb. I'm planning to get 2 more 256 sticks. I'm going to be using 2000 as soon as I receive my RAM (if I do get it). Since I'm still on ME right now and have been too lazy to install 2k and reinstall/config all the appz all over. But since I'm planning on getting 2 more sticks, what the heck I'll just install 2000.

I'll run multiple sessions of certain programs, use Photoshop, watch movies, and few other proggies also. Should I stick with 256 or would I be much better off with 768? Since as said, 2000 will utilize all the RAM you throw at it. Just that I'm wonderin if 768 will have much or less noticeable increase. Any input is appreciated, thanks.

 

[dee]

Photoshop eats ram. If you work with big scans its a case of the more the better (I've got 320 and it still pages all the time).

 

[Shooters]

If you're a Photoshop user then I would recommend jumping to 512MB. Anything beyond that and I don't think you'll really notice that much difference. Of course if you have money to blow then go for the 768MB.

 

[LoStZ]

How bout if I'm just a normal PS user? I don't work with that big of scans or anything extensive. Probably it'll be mostly several appz running in the background and downloads, listening to music, etc, while working with Photoshop. So I should just get 512, since 768 over 512 won't benefit as much?

 

[NelsonMuntz]

I'd probably just jump to 512 Mb since there are better places I could put the rest of the money.

 

[Shooters]

Go with the 512MB.

 

[HansXP]

Yeah, I would agree. 512 MB seems to be the "sweet spot" for Win2K. Then again, if you're going to be scanning a LOT of stuff into PhotoShop and working with it, then bumping it all the way to 768 MB can never hurt. Got the money? Go for it!

 

[IcemanJer]

heck, RAM prices are still pretty cheap, might as well go for it.

 

[Mday]

the win9x kernel has a 512MB memory management bug.

 

[LoStZ]

<< the win9x kernel has a 512MB memory management bug. >>



Theres a few things you can fiddle with to fix that
And plus, I'm gonna be using 2000