Archived from groups: microsoft.public.win98.gen_discussion (
More info?)
What performance are you talking about: booting, shutting down, browsing
folders in Explorer, or what?
I am in total agreement with Gary--registry cleaners should be used as a
last resort, not regular maintenance. MVP Alan Edwards and I quit using
them years ago and concentrated on keeping our registries clean instead of
wasting time scanning the undo file for items that did not appear to be
valid entries to remove.
--
Regards
Ron Badour, MS MVP for W98
Tips:
http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo
"flusters" <flusters@go4.it> wrote in message
news:esmvEXkrFHA.2540@TK2MSFTNGP09.phx.gbl...
> Gary thank you. As usual, your helpful advice and sound commonsense is
> very
> welcome and I will take notice.
>
> In mitigation, if you note my opening preamble, this is a case of what
> else
> can I do before reformatting and rebuilding again. The performance of the
> notebook was excellent but it is now like glue.
>
> This is why I posed the question about the varying results from the
> different programs. I would rather every thing was running smoothly but it
> is not!!
>
> Flusters
> "Gary S. Terhune" <grystnews@mvps.org> wrote in message
> news:uYuencjrFHA.4044@TK2MSFTNGP09.phx.gbl...
>> "flusters" <flusters@go4.it> wrote in message
>> news:Od3q1uirFHA.260@TK2MSFTNGP11.phx.gbl...
>> > Thanks AlmostBob, Gary and Buffalo for the advice so far - its been
>> > very
>> > helpful.
>> >
>> > My rule of thumb on suggested Registry changes has always been, if it
>> > refers
>> > to a current application then do absolutely nothing unless it has been
>> > fully
>> > investigated first. If it refers to an old application and is either
> (a)
>> > File or Path Did Not Exist (b) Invalid Applic Path (c) Obsolete Entry,
>> > then
>> > I delete.
>>
>> So long as you're sure they really belong to the obsolete app. But, there
>> are almost certainly a number of Registry entries created by this or that
>> *curent* application that appear to be from one or another obsolete app,
>> placed there by the current app for purposes of compatibility--just in
> case.
>> Major apps suites are prone to this--MS Office, WordPerfect Office,
>> almost
>> any Adobe product. They all write a ton of seemingly garbage entries to
> the
>> Registry, and in truth *some* of it *is* garbage--but not all. A lot of
> the
>> stuff they write that Registry cleaners flag as useless really isn't. So,
>> no, the rule of thumb you delineate above is not foolproof.
>>
>> When it comes to Registry cleaning, my rule over the last few years is,
> "If
>> it ain't broke, don't fix it." The one exception is when I'm doing major
>> maintenance--cleaning up a mess. In that case, I must be ready, able, and
>> willing to reinstall one or more apps, patches, or whatever, immediately
>> afterwards. Even then, if I am at all doubtful about the provenance and
>> purpose of an entry, I leave it alone. In short, I consider Registry
>> cleaning, etc., to be a last-ditch effort to tidy things up, and if I
>> fail
>> to succeed, the next step is a complete rebuild from scratch. I *don't*
>> think that any regular maintenace program should include "Registry
>> cleaning."
>>
>> > Should I add 'Extension not used' to my rules above?
>>
>> IMO, no, for reasons parallel to the above. Yes, it's typical that some
> file
>> associations get created by accident and can be deleted, but unless
> they're
>> *wrong* associations, instead of just unneeded associations, I tend to
> leave
>> them alone for reasons resembling the ones I discussed above.
>>
>> > For Buffalo - yes, I do have the 'back-up before deletion' box checked.
>> > Unsure when I downloaded my RegSeeker version but I was surprised that
> (a)
>> > it appeared to be quite a comprehensive program but (b) there is no
>> > help/instruction/tutorial file. That worries me because I do like to
> read
>> > and check things out thoroughly. Anyway, you seem to be quite happy
>> > with
>> > this program - taking care obviously. There is a read me file but
>> > should
> I
>> > be looking in a different place?
>>
>> I know the above was "for Buffalo", but do you mind if I comment? Backing
> up
>> Registry entries before you delete them is of course common sense. But
>> let
>> me ask you--how do you determine when the source of some odd behavior
>> that
>> you might encounter in the future is due to your having removed an entry
>> that didn't appear to be right today? How do you mentally connect some
> "new"
>> problem with some Registry entry you deleted two months ago? It does no
> good
>> to back something up and then delete it if you can't later identify the
> need
>> for, and the specific details of, some item that it turns out shouldn't
> have
>> been deleted.
>>
>> --
>> Gary S. Terhune
>> MS-MVP Shell/User
>>
>>
>>
>
>