You are entitled to your opinion
I agree, we are all entitled to our own opinions. But like the opinion that Maggots spontaneously appeared in rotting meat was proven to not be cogent with reality so too is an opinion that this- or any other "memory conservation" tool works merely the result of placebo and confirmation bias.
after an hour or so my ram drops to about 269megs available and when I kick in the program I am up to 420megs free with no adverse effects
I got tired of running low on ram
Running low on RAM means nothing. Running low on Free RAM also means nothing How much free memory you have only has a impact on performance if it causes a lot of swapping, which will only occur if you are frequently using data that isn't paged in physical memory. Since these programs work by essentially forcing every program to page out data out of physical memory with the goal of making the amount of free memory bigger (which affects performance negatively).
and am to poor to buy more so my solution is fixed.
I ran Windows XP with 96MB of memory for over 3 years, so while I currently have 8GB it's not like I've never dealt with Limited memory. The solution is not found in snake oil software but rather in diligent computing habits. For example, Firefox was out of the question, and for some software packages the later versions were as well; Many options had to be disabled (things like Luna themes, for example) in the interest of saving as much memory as possible, not using more than one application at a time, etc.
Most important was that when using a machine that had limited RAM, I had to limit myself to software that
took that into account. Firefox does not meet that requirement, nor would chrome or pretty much any common desktop application in use today. The problem is not that you or I had too little memory (since 96MB was considered gobs at one point) but that the software we typically use is designed to consume memory like a SUV guzzles gasoline- with little regard for the environment and with far more style than utility.
PS I dont think it is cool to disassemble a program when the licence says not to,you may take that as you wish.
There is no license attached to the program, therefore the only license attached to it is the implicit license of fair use and default literary copyright. Even if it was, Dissassembly is covered Under the Canadian Copyright Act 30.6.
Ah more people bashing my program :-)
I wasn't bashing it. I was saying that all memory "optimizer" perform an unnecessary task and are distributed people that either do this and are intentionally deluding people or don't and are spreading their own delusion around. Facts are what I, personally, work with, and unfortunately ethereal concepts and opinions do not sway that.
And in case your wondering it is made in VB6 because I like the size of the run times 1.3 mb vs the insane size of .net, It is my programming of choice nothing more.
It could probably have been created in VBScript, at least the core "cleaner" portion.
Again someone going off about the page file
This hardly refutes anything I said. This is analogous to if somebody tried to say that Cookies didn't contain flour, and I said "Cookies contain flour" and the response was "yet again someone going off about the page file". (It also reminds me of the Reagan vs. Carter debate where the former said "There you go again" as a response to an otherwise articulate argument.)
Has anyone read this yet?
http://www.pcwintech.com/about-cleanmem
I just did.
CleanMem doesn't work magic on your system. The best thing you could do is get more memory for your system! The goal of CleanMem is to help keep windows from needing to rely heavily on the page file. Which is located on your hard drive.
And yet, what the program
actually does flies directly in the face of this. You cannot simply cull a processes memory usage; the broadcast messages are deprecated (WM_COMPACTING, for example) and typically have no effect at all. Unless you are actually going through every process and somehow figuring out where programs are no longer using data (which is an intractable problem) and then deallocating those blocks of memory (which would require process injection). All I could gather was mostly from the WMI query strings acquirable from SysInternals "String" tool, (which is what leads me to the conclusion that much of the base functionality could be done with VBScript or JScript through WMI); though the Monitor thingamajig
I only responded because shagger1 is a good user of my forums, so I thought I would just chime in, I wont be getting into any fights over my program. You don't like it then don't use it.
This sort of reads like a care salesman who's best customer is being told that the rust on the bottom of the used care they are trying to sell does not actually make the car go faster, saying "if you don't like driving cars with rust on them, don't". That probably isn't the intent here,(I would certainly hope it isn't) but this isn't about personal preference; either these programs help performance, do nothing, or impede it. Any one program cannot do more than one of these things. This sort of goes into my next paragraph too.
If you haven't even tried it or put it under any test then please don't comment on it till you do, but once you put it under tests and having something to complain about then I am all ears.
I did, But I didn't want to image post at the time. More importantly they weren't really that methodical. I'll try to come up with some sort of test that attempts to be more or less impartial, and, most importantly, is reproducible, since it's otherwise useless. This will make a good blog post, since I could test other programs of the same cabre. I'll probably test this one first, since it has relevance particularly to this thread, but I'm curious how a program I used to use when I thought it actually mattered, RAMpage, fares as well.
I'm trying to think of what specifically needs to be covered here. First, and most obvious, is memory statistics, which can be captured with Process Explorer. In order to "heavy" up the machine, I imagine it might be ideal to run a few programs and do something in them that pulls in some of their latent pages from disk (eg code in their executable). As explained above this is what usually increases memory use over time. The method to do this will need to be well documented, any relevant macros provided, etcetera. Once the machine is "loaded" we will test the speed of things at that point; I guess that could be more macros, perhaps some sort of browser test and maybe running a benchmark using Fraps or something of that sort. Possibly even run some programs that find the anagrams in a dictionary since I'm currently in the process of blogging about that implementation in a bunch of languages and cross-over posts are never a bad thing.
After that, we run the optimizer program being tested. Then we grab the memory statistics immediately afterward, and do the same speed tests. Keep track of the results and then reveal.
Hopefully this doesn't turn into that ill-fated idea where I was going to test Registry cleaners but then sort of forgot about it for a year and a half.
