Registry cleaner ?

[Unknown]

What an out and out lie! Each and every time a poster posted the damage
caused by a registry
cleaner to their system you completely ignored and wouldn't respond.

 

[Twayne]

In

As usual and in your true form when ever these useless programs are
exposed for what they are you are here to defend your beloved cleaners
and to insult all who disagree with you. However, when people post
seeking help with real problems caused by these cleaners you are
nowhere to been seen. Most of us here have noticed that when it
comes to posts about registry cleaners you have a case of selected
blindness, and when you do reply to posts you usually leave your
brains and manners parked somewhere else.

John

Wrong. I only address those who make untrue statements without anything to
back themselves up and which I know from education, research and experience
to be completely wrong. e.g. you say "will" cause irrepairale damage, not
"could" cause some kind of minor damage, and so forth. Even a preface of "in
my opinion" in your posts would quiet me down. But that's not your posture
and you know it. Your'e also wrong and you know it.
As for your last sentence, projection won't do you much good; you have to
become an actual thinking person as opposed to a mindless follower without
anything to back up or verify what you claim.

HTH,

Twayne

 

[Twayne]

In

None of which tells us ANYTHING about why you think we should not use
registry cleaners, and what harm you think they do.

And they never will, Steve. I used to gently prod for something, anything,
that would lead them to their decisions and opinions. If there were any
truth to their contentions, there would be a LOT of information all over the
web sites about the subject of how useless they are. But it's only a small
clique here wanting to force their opinions on the newbies and weaker
personalities they might suck in.
Nowadays I just take every opportunity to expose their lies and
misinformation; it's more fun anyway, since they have absolutely nothing but
a few anecdotal messages to back up their claims.

Cheers,

Twayne`

 

[Unknown]

Twayne the registry cleaner program seller is back!

Been away for 5 days.

 

[John John - MVP]

I'd love to see you trying to get a machine working right again after
say Office quits working, won't start, won't uninstall and won't
reinstall. Do you even have a hint how many regisry entries you'll find
for MS Office?

That is quite a joke... it probably quit working because you ran your
useless registry cleaner as Office is one of the applications that is
most often broken by worthless registry cleaners! Where were you when
this was posted:

http://groups.google.com/group/micr.../thread/6b333372c870ea74/43b0f73c7b89f3ba?q=#

As usual when these problems are exposed you conveniently disappear.
And if you're such an Office expert you should know by now that
Microsoft has a removal tool just for Office. Next time don't use your
cleaners and you won't break Office, and, if you do break Office,
instead of causing more damages with your cleaners go to the Office site
and get the removal tool!

John

 

[John John - MVP]

In

Wrong.

No, we have all noticed it. When people post with problems brought
about by registry cleaners you *never* offer any help, you simply
disappear. It's so blatant, you are there defending your cleaners 5
minutes earlier but as soon as someone has problems you go blind and see
nothing. Who are you really trying to kid?

John

 

[Unknown]

I have never once, in at least 5 years, seen you respond to someone who
posted the damage done to
his/her machine by a registry cleaner. You conveniently ignore them. Then,
you severely criticize some who
says registry cleaners are 'snakeoil'. Why are you so two faced? Do you work
for the 'snakeoil' developers?

 

[Peter Foldes]

Twayne

LOL. You are a real gem Twayne

It is so strange that you disappear and do not show up when a poster posts that he
messed up his system after using a Registry Tool. Happens with you time and time
again that you avoid to answer in those posts because you know that you will be
wrong which you are all the time when it comes to Registry Tools and it's effect on
Operating Systems..
The only thing that you can do in posts concerning Registry Cleaners is to blast
everyone that disagrees with your belief that Reg Cleaning tools do magic for
someone's OS

 

[Twayne]

In

What harm they do??? THINK, how would you write or create a registry
cleaner? How would you the
programmer know unequivocally whether an item is an orphan or not?

It's simple. And, if it turns out a program needs an on-the-fly that's
referenced, well, that's what the UNDO is for if you didn't recognize it
first time around. Chances of that are very small in contrast. The last one
of those I came across simply threw up a message and asked for the original
media in order to re-register the components. I fixed it with a simple UNDO
though since it named the exact entry. Ain't it great what software can know
about itself? I've seen a couple that pretend to be on-the-fly too but
actually just spilt their data off onto the hard drive into its own temp
directory.
But YOU think! Why do you suppose the manuals spell it out rather clearly
about being careful of entries that may only exist at certain times for
temporarily created uses? Or don't you read?

What happens if the cleaner
inadvertently deletes something that is absolutely needed.

Well, that's NOT going to be a case of stopping the machine from booting or
running except for the one application that's now telling you it wants such
and such and can't find it. UNDO takes care of it pretty quickly if and when
that should occur. And, such an occurrence is seldom going to happen on the
machines of anyone participating here. I do notice the cleaners say to watch
out for such things, though; right on the screen if you bother to look at
it. It separates things it doesn't "know" for me. If in doubt, leave it
alone. But like I said, that almost never happens.

This is

usually the case. AND, if you didn't know
if an entry is valid or not what do you do with it?.

Me? Depends on my mood. But usually, I simply look it up at one of the many
sites available to see what it is. If you just follow the heirarchy back a
bit, it's going to tell you what application it belongs to. In fact, my
registry cleaner does that for me. If it's my machine and there is no reason
to suspect it's causing a problem, I'll still delete it, just to see what
happens. But if it's a client's machine I'll only delete it long enough to
be sure it's not the cause of the problems I'm looking at, then I'll put the
entry back. Or sometimes I'll reload the whole registry to make comparisons
between various suspicions if it gets to that point. You only need 3 rules:

-- Back up the Registry and System State before doing any work.
-- One change at a time or set of related changes, and test before
proceeding to see if it effected the problem.
-- THINK! Actually read the screen output. All of it.

Oh, and as for orphaned entries; I'll often kill those, too, just for GPs
since I'm already there. They take time to load/unload from RAM so they are
timewasters since they're going to/from the disc and buffers.

Now I guess all I have to do is decide whether to go back and respond to all
the misinformation in all those old posts of yours<g>. Thanks for the head
start.

HTH,

Twayne

 

[Twayne]

In

No, we have all noticed it. When people post with problems brought
about by registry cleaners you *never* offer any help, you simply
disappear. It's so blatant, you are there defending your cleaners 5
minutes earlier but as soon as someone has problems you go blind and
see nothing. Who are you really trying to kid?

John

Aha, that's an exact description of YOUR MO! You'll find I either: Offer an
answer to at minimum tell the poster that you are all wet and not to be
taken seriously.


HTH,

Twayne

 

[Twayne]

In

I have never once, in at least 5 years, seen you respond to someone
who posted the damage done to
his/her machine by a registry cleaner.

Well, you'd better go look again. Or put your glasses on. I don't offer
answers to someone if I don't know the answer. But I DO address your
misinformation. K? And, I'm clear about what I'm doing.
You've missed a lot of posts in 5 years.

... You conveniently ignore them.

But you don't, if you have a chance to spew your misinformation, huh?

Then, you severely criticize some who
says registry cleaners are 'snakeoil'. Why are you so two faced? Do
you work for the 'snakeoil' developers?

I criticize liars, misinformationists and those who lump the entier world
together with one color. I would join your vendetta if even one of you have
any verifiable, legitimate information from an unbiased source to disprove
the functionality of every registry cleaner ever made. It's an extremely
stupid premise to start with and intentionally ignorant besides.

And if you think those are severe criticisms, may I suggest you need a
thicker snake skin?


HTH,

Twayne

 

[Twayne]

I was going to give you a pass, but ... go measure the added time it takes
to load a registry with 4 Meg of orphans. It's considerably longer than 1
second, and also depends on knowing the cpu speed, front buss speed,
pagefile status, latencies and buffers statuses. That time is present during
the load and the unload as it spools everything back to disc, not to mention
the movements that must continually happen in RAM as data is pushed around
to make room for or remove other data. You simply cannot say 1.S without
those numbers because your'e talking about a very fast machine when you do.

"When the registry ... " is pure unadulterated crap if one is using a
branded, reputable cleaner.

Maybe the points below will help the OP:


In

- What is currently wrong or failing with the registry?

I may have just noticed an increase of about 40, maybe 60, seconds in boot
time. You should know what that indidates.

- What convinced you that the registry needs to be "cleaned" up?

Depends; The OP didn't say he had a problem; he asked for advice, such as
ccleaner, or Norton tools, or whatever. You provided no such thing and thus
had no business responding.

- What constitutes the "cleaning" actions?

lol, if you don't know, I'm not about to tell you!

- What do you expect to gain from the cleanup?

Either repair of an issue, or possibly simply a process of elimination if
it's possible the registry were at fault. But again, the OP asked for
programs, not your drivel advice.

- What are you going to do if the registry changes hose over
your computer since a restore may not be possible?

That's fantasy. Only malware or kiddie-code could screw up a machine to the
point where it couldn't boot. It's nearly impossible, unless there is
malware or serious code corruption, to stop a machine from boothing using a
reputable program.

- What is your recovery strategy from the registry changes?

Restore Points. Save the System State. Etc.

*_Why the uneducated or lazy should never use registry cleaners_*

If YOU are not adept at *manually* editing the registry, don't use a
tool that you don't understand regarding its proposed changes.

So, don't YOU use a word processor or any office program, because they all
impact the registry with thousands of entries upon install, and if you8
don't know their internal workings completely, don't use it! Or any other
program, for that matter! Just totally ignore the reason any program
exists; to save time and effort.

Regardless of relinquishing the task to software, YOU are the final
authority in allowing it to make the changes. Any registry cleaner
that does not request for YOU to give permission to make its proposed
changes along with listing each proposed change should be discarded.

I don't believe there is any such thing in any but the most pathetic of
examples of malware and kiddie-code.

....

Say there was an unusually high amount of orphaned entries in your
registry, like 4MB. By deleting the orphaned entries, you would
speed up how long it takes Windows to load the registry's files when
it starts up - by all of maybe 1 second.

Wrong. Measure it, or calculate it. With the given information. You cannot
do it.

Oooh, aaah. All that risk

of modifying the registry to save maybe a second, or less, during the
Windows startup.

Wrong again.

....

Cleaning the registry will NOT improve performance in reading from the
memory copy of the registry.

Why is it you dummies think there is no reason to use a registry cleaner
other than to delete orphaned entries? Even discounting your impossible math
above, you suddenly switch to reading RAM all of a sudden. Huh?

The reduced size of the registry's .dat

files might reduce the load time of Windows by all of a second and
probably much less.

Again, something you cannot possibly know based on the info you have.

And you want to risk the stability of your OS

for inconsequential changes to its registry?

No, the OP asked for WHICH program, which you ignored.

The same boobs that get

suckered into these registry cleanup "tools" are the same ones that
get suckered into the memory defragment "tools".

OOF! Now you've clearly shown your ignorance. How the hell do you get from
asking for advice on a registry cleaner to mem defrag? Just another chance
to be condescending, I know. You're a real idiot here.

A registry cleaner should only be used if you by yourself can
correctly cleanup the registry. The cleaner is just a tool to
automate the same process but you should know every change that it
intends to make and understand each of those changes. After all, and
regardless of the stagnant expertise that is hard coded into the
utility, *YOU* are the final authority in what registry changes are
performed whether you do it manually or with a utility. If YOU do
not understand the proposed change (which requires the product
actually divulge the proposed change before committing that change),
how will you know whether or not to allow that change?

Good question and one that's often overlooked because of a refusal to RTFM
by way too many people. Not reading the screen is even worse; most tell you
right on the screen these days; at least all 3 of mine do.
But, you do not have to be a registry expert; what you do need is the
ability to recognize names of your own programs and how to look up whatever
it may be showing you to see whether it's part of one of our own programs or
not.
But again, you've jumped to orphaned entries in your own mind. YOUr
entire post and non-response here are MORONIC. YOU need to seriously get
YOUrself some interpersonal skills on how to work with people and actually
accomplish something good on the groups. As far as I can see YOU're nothing
but a moron.


HTH,

Twayne

 

[Twayne]

In

VanguardLH said it correctly. If you are inept at editing the registry
manually don't use a program to do
it for you. His post was well said and educational.
But, Sandy58, this has absolutely nothing to do with fixing corrupt
files, do a spell-check, do a full search,
take/make a snapshot, etc. Perhaps, you have no idea what a registry
is?

Actually, it does. He very likely does all those things without knowing
exactly how they're performed or executed.


HTH,

Twayne

 

[Twayne]

Ahh, the original intentionally ignorant misinformationist! Just looking
for a chance to make your moronic spiel, eh? You've been exposed so many
times I don't think it's even necessary to go through it all again. You're
wrong now, always have been, and always will be. Your advice here is
complete "snake-oil" by definition.

HTH,

Twayne






In

 

[Twayne]

In

....

So how should you clean the registry, then?

Personally I wouldn't use that program for registry cleaning, mainly because
I know nothing about it and never heard of it. I'd opt for ccleaner over
that or better yet a few of the pay-for cleaners that are around.
You're wise to ask for advice here, and I just wish there were responses
from more than a small group of morons here. Those idiots have a lot of
people afraid to even mention a registry cleaner. They're pure idiots,
believe me.

What they should be saying Steve, is that the registry is seldom the root of
computer problems and doesn't need frequent cleaning. It's really a case of
a stubborn problem that can't seem to be fixed otherwise and often is a
last-ditch or process of elimination effort at a fix, simply because it's
not likely to be caused by the registry. There are reasons to immediately
suspect the registry, but it's too much to go into and not write a book<g>.
Experience counts there.
If you decide to use a registry cleaner, be certain to first back up your
registry and preferably the System State so it's easy to get back should you
make a mistake. Any good program comes with UNDO functions too, but it's
best to be safe. It's no different than backing up all your data whenever
you decide to mess around with the OS. Always keep a backup handy.

Luck,

Twayne

 

[Twayne]

In

And the correct answer to that question is: "You shouldn't." There's
no sound technical reason for doing so, but abundant technical reasons
for *not* doing so.

He asked HOW, dummy! Also:

You typo'd: There ARE sound technical reasons for doing so, and abundant
technical reasons that the problem most likely lies elsewhere also. But as
usual, your are completely wrong and missed the chance for a good response.

HTH,

Twayne

 

[Twayne]

In

Hundreds, or even thousands, of defunct registry entries should not
even be noticed as far as performance is concerned. If you get rid of
a problematic program, Norton for example, then you would want to use
the removal tool for that issue. Many programs have removal tools or
instructions to get rid of all aspects the program.

Registry cleaners sound like a good idea like needless e-mail
scanning, but it is like playing Russian Roulette. Someday, you may
well regret it.

Frist, he won't. Second, even if your threat were true, how do you know he
doesn't have the drives imaged? Or otherwise backed up?

Your ability to give out misinformation is beat only by your ability to make
ASSumptions.

HTH,

Twayne

 

[Twayne]

In

(Still waiting for an example, David.)



/Very/ good question. Let's see all the people who enjoy
hoarding old registry entries answer that one. Let's specify
"reinstall" and "overwrite" to mean that a newer version of the
same program is being installed, or a /similar/ program which
handles the same types of files.

(If you are reinstalling the /identical/ version of the same
program you had before, the worst that may happen is that you
may end up with old settings you don't want any more or that you
may end up with new settings you didn't want, depending on how
bad the install routine is written. Either way you will have to
do some work.)

Nah, just export the whole registry from regedit, then import the whole
registry.
NO DON'T! At least not unless it's a sandbox machine<g>.

HTH,

Twayne

 

[thanatoid]

In thanatoid <[email protected]> typed:


I'll buy that; it's one step further than I go, but it
doesn't hurt anything as long as you know what you're
doing, which you do or you wouldn't be online< G >. Well,
I also only use one cleaner too, but I do have three I keep
available just in case.
You did well, brain-farted sentence and all! :^}

Sometimes I sign my posts thanafart ;-) ...

--
There are only two classifications of disk drives: Broken drives
and those that will break later.
- Chuck Armstrong (This one I think, http://www.cleanreg.com/,
not the ball player. But who knows. I can't remember where I got
the quote. But it's true.)

 

[thanatoid]

http://www.411-spyware.com/remove-registrycleanerpro

That's a description of why it's "bad".

The /program/ is here:

http://www.ixitools.com/products/

And for malware, it sure has a lot of five star ratings from
software sites - of course, they could be fake. I sure am not
impressed by the fact they also have a "driver updater" and
"driver backuper". Driver utilities are such bullshit.

As always, the bottom line is the user... I scan my security
programs with ESET NOD32 just like I scan any and every other
thing that wasn't on my computer before the last online session.

--
There are only two classifications of disk drives: Broken drives
and those that will break later.
- Chuck Armstrong (This one I think, http://www.cleanreg.com/,
not the ball player. But who knows. I can't remember where I got
the quote. But it's true.)