Re: Hello Everyone!!! DO Not USE
Ya know? Reading rjsmithwalmart's first post, is the first time ever, I had really ever thought of giving someone negative rep, since re-introducing this ability was discussed last year. Same goes with the reply of his, for which it doesn't help realizing that I was looking at the cleaned up version of it. That's largely the view I would have wrt this. The whole way it was written was similar to the manner in which many of those virus scares, (which seem to find their way emailed all over kingdom come) get spread. But in the case of those emails, they're in fact hoaxes. I know of those things, because I've had family email them to me, for which I've had to educate them a bit, and in the end ask that these emails not be forwarded to me anymoe...
In fewer words wrt registry cleaners, we're seeing essentially the equivallent of
http://www.symantec.com/avcenter/venc/data/watching.hoax.html
he Watching hoax is a variant of the Wobbler Hoax. The hoax is similar to the following:
Subject: FW: VIRUS
Message:
IMPORTANT, URGENT - ALL SEEING EYE VIRUS! PASS THIS ON TO ANYONE YOU HAVE AN E-MAIL ADDRESS FOR. If you receive an email titled "We Are Watching You!" DO NOT OPEN IT! It will erase everything on your hard drive. This information was announced yesterday morning from IBM, FBI and Microsoft states that this is a very dangerous and malicious virus, much worse than the "I Love You," virus and that there is NO remedy for it at this time...
There were some that claimed they'd erase the BIOS, destroy monitors and hard drives, blow up power supplies, or infect
a text file, or other such stuff. The claims were almost as ridiculous as melting down one's mobo or causing premature grey hair :laugh:
Now, admitedly someone who is ignorant and who just goes along the thing to remove anything "cause the computer said so, so it must be true, as, computers are infalible and can never make mistakes" can get themself in trouble. But no worse trouble then the unthinking use of the command line can result in as well... In this case, the problem would be more to do with operator error, and less to do with the program. The program is a tool, and yet it is only there to assist, not replace human thinking on what one is doing. If one is wondering why I might use terms such as this to describe this; it is because I have already run into this with another individual who did exactly what I'm describing with an uninstall program, and when I walked in the door was frantically waiting for me. The first words outa their mouth was help, my computer doesn't work anymore. It was the clean .dll function, and the same thinking "if the computer said it, it must be true" to which no additional thought was added.
And as it proceeded, using the option to reverse changes, or look at the log to see what files were delted wasn't possible. Reason is, the immediate thought on their part was "the program must be bad", so they uninstalled it. The thinking didn't fall along the lines of, "perhaps I shouldn't have used it the way I did, and perhaps I should have kept a better eye on what I was doing with it".
perris said:
I've never EVER seen an issue resolved or a computer "sped up" by purging the registry, and I have seen plenty of issues caused and obviously the computer slowed down when an issue does occur
Actually, I have run into one, albeit I used regedt32 to manually purge the thing myself, rather then a registry cleaning tool. Johnny is correct though, that it might be a time saver vs. manually searching the stuff myself.
Anyone remember back to the days when 3dfx was still in existence, and as they didn't have unified drivers, such as nVidia and ATI now have, each product resulted in a whole new set of gfx drivers, based on a different code base? Well, not only could switching between a nVidia and a 3dfx card (or vise versa) cause problems, as setting it to VGA mode, or uninstalling the old drivers via the win2k Device Manager (only to have the system auto-restore the old drivers), then removing the board, and all other such stuff didn't effectively clean out the old drivers, but just switching between say a Voodoo 3 3000, and a Voodoo 5 5500
With many driver files, as well as registry entries left behind, and the newer driver installed right onto the same PC, some rather odd problems resulted. I'm talking about rather weird and completely bogus benchmark results, all the way down to strange color corruption problems. I still remember the day I got Martian Unreal, which had something like a red sky and people with green faces on the thing
Not sure if I still have a pic of this. I also had some other images appear on screen that looked totally unreal, with color corruption occuring here or there... There were other odd gfx issues besides.
Unfortunately, the screen shot is no longer on my computer. But a cleanup of the old driver files (which could be done from safe mode), as well as removing references to older device drivers could clean this up without a reformat, perhaps. I ended up switching to a GF2 GTS then, after taking a look at the Voodoo 5, which proved, problematic albeit a little less problematic, then swtiching between 2 seperate 3dfx driver sets in terms of weird issues, even after supposedly "uninstalling the drivers" through the win2k Device Manager. I think that time, not wanting to reformat only a couple days after my first reformat, I did use this method to clean all 3dfx stuff off my system, and got things back to normal.
I think this potential problem with old device drivers, (albeit it's less of an issue with the same companies card now, due to the use of integrated drivers), is why nVidia released their detonator driver removal tool some years ago...