St. wrote:
>     No, it just clears some heavy memory for you as far as I understand it. 

Virtual memory, much? Maybe Windows' VM algorithm sucks, but I wouldn't 
think it sucks that bad. And you'd need to have a crapload of services 
running before the bookkeeping overhead started to take up noticable 
memory, methinks. On my machine, all the services put together are 100 
meg, which is about 4 times the size of explorer with no windows open. 
Assuming that "mem usage" actually means "in physical memory" and I 
don't have to subtract out the "vm size" to find the working set size. 
Not exactly "heavy memory" either way, methinks. :-)

You should try it and tell us how many FPS it saves you, for real.

-- 
Darren New / San Diego, CA, USA (PST)

Post a reply to this message