michael lefevre wrote: >...i guess it could be an >option... > Yep, thats what I want.
> >i can't see the logic in doing that though... if you have, say, 96Mb >RAM, and 32Mb is used by windows, a further 32Mb is used by mozilla, and >then you load diablo, if you then force mozilla (and of course windows) >to remain loaded, then you end up trying to run diablo in only 32Mb of >RAM, which means bits of diablo will be continually paged in and out and >the game will be unplayable. > Well, i have 256MB ram, which is quite little nowadays, anyway...Moz is currently quite memory hog ~40000K used (One browser, M&N and Compose window). If i minimize all Moz windows it takes only 1500K, and all that time i have 100 000K free physical (at least Task Manager climes so). Diablo takes some ~70 000 K after playing for a while. My point is, if I leave Moz in front while playing diablo, it immediate is usable after I exit game with no swapping (...maybe little), and game didn't swap neither. So, all i want option to forcing to keep Mozilla in memory when quick launch is active, at least critical parts of it.
