Subj : Re: Windows issues To : Finnigann From : Grymmjack Date : Sat Jun 11 2005 10:42 am > It has been my understanding that Windows apps fail to restore all of > the allocated resources upon exiting. They are thus lost to the system. > Eventually you must reboot your computer in order to recalim them. > Every version of Windows claims to fix this problem. definitely if a program is coded poorly and doesn't cleanup it's mess it can cause problems. i dont know if this is true anymore with nt/2k/xp but in the 9x days it was a huge problem. remember the memory 'leaks' or whatever they were that would crash one program, than every single other program running including the api message thing would also crash? in nt/2k/xp that's a thing of the past thank god, but there are still things going on that i can think of just looking at the way it works that could still be true. like you mention the fact that after closing you never get back what you used. i haven't run into this but i haven't kept an eye on it really. when i open photoshop, resources indicate for example, that i am using about 400mB of ram (i dedicate lots to photoshop) all told, when i close it i recover the 384mB photoshop claims to use (according to my math and the percentage of ram allocation slider in preferences). i found that running lots of apps simultaneously which exceed the limits of my physical ram chips in my machine that disk swapping naturally occurs and handles whatever situation without fail so far. i have yet to see a 'windows is running extremely low on resources' message in 2k or xp. (i've never ran nt). *shrug* the tool i recommended, RAMpage does some other stuff too. i'd really like someone who knows to look at the source (i posted the link) and see exactly for all of our benefit, what the hell the truth is :) no offense to Rob or the guy who wrote that article, but i have a hard time taking anything a "Windows magazine" says as gospel. - grymmjack .