Registry
in [Windows XP]
|
From: a on 11 Jul 2010 13:22 "Nil" <rednoise(a)REMOVETHIScomcast.net> wrote in message news:Xns9DB1757987A3Enilch1(a)130.133.4.11... > On 10 Jul 2010, "a" <b(a)invalid.com> wrote in > microsoft.public.windowsxp.general: > >> If CCleaner can find "suspicious" files on a clean Windows >> install, then how is that not a placebo effect? And you know what >> they say above having an open mind... it lets your brain fall out. > > First of all, where are you seeing Ccleaner report "suspicious" files? > I've never seen it use that phrase, and the program isn't designed to > look for them. Are you sure you saw what you think you saw? > > How about you tell us what those supposedly "suspicious" files are? If > you can't do that, there's no way we can say whether Ccleaner has found > anything legitimate or not. They could be cookies or temporary files, > which are all good candidates for removal. Don't ask me all this. Ask the poster who said he did it.
From: Nil on 11 Jul 2010 14:55 On 11 Jul 2010, "a" <b(a)invalid.com> wrote in microsoft.public.windowsxp.general: > Don't ask me all this. Ask the poster who said he did it. Although I phrased it as a question, it was really in answer to your question about why you might find easily-explained, supposedly "suspicious" files on a new installation. As for what CCleaner actually found, we'll have to wait to see if he replies. I predict not.
From: Unknown on 11 Jul 2010 15:15 You're wasting your time if you think you can convince Twayne of ANYTHING. "HeyBub" <heybub(a)gmail.com> wrote in message news:Ou4e38OILHA.5136(a)TK2MSFTNGP02.phx.gbl... > Twayne wrote: >> >> Neat; a product provides you with information about the contents of >> your registry, so you call it worthless. Now there's a piece of real >> advice!! Yup, you sure proved it here, didn't you? lol, so pathetic! > > No, the program provides DATA. Only when the data are meaningful do they > become "information." > > But some people are terminally curious ("How many angels can dance on the > head of a pin") and devote untold resources to discover obscure - and > meaningless - data. I once heard that it took a team of people two years > to discover the exact middle word in the King James Bible (and it turned > out there was NOT a middle word - there were two!). >
From: Unknown on 11 Jul 2010 15:19 Absolute hogwash. There have been hundreds of posts on this newsgroup of computers being rendered inoperative by the user running a registry cleaner. Simply running a registry cleaner has caused damage. "Incognitus" <in(a)ccurate.com.invalid> wrote in message news:i1chmc$875$1(a)speranza.aioe.org... > On 07/10/2010 10:03 AM, PA Bear [MS MVP] wrote: >> >> Eddie wrote: >>> PA Bear [MS MVP] wrote: >>>> If you ever think your Registry needs to be cleaned, repaired, boosted, >>>> tuned-up, cured, tweaked, fixed, or optimized (it doesn't), read >>>> http://aumha.net/viewtopic.php?t=28099 and draw your own conclusions. >>> >>> >>> Hi [PA], >>> >>> I have followed and respected your replies to posts for years, and also >>> your affiliation toward ms products. >>> >>> I do have a question though regarding this thread, but first, an excerpt >>> from the link you posted re: O/P. >>> ------\/ >>> >>> "Microsoft has a freebie online program at >>> http://onecare.live.com/site/en-us/default.htm. Being the Godfather's >>> program it should be safe....theoretically. It didn't do me any harm. >>> I strongly recommend that you, or anyone else, avoid using the onecare >>> registry cleaner >>> >>> Here's why: >>> >>> The onecare cleaner offers no chance to backup what is removed and >>> whatever it removes is gone, forever. Should it mistakenly remove a key >>> or value needed by your operating system or software it's gone along >>> with your program or operating system. I've seen onecare's registry >>> cleaner completely hose systems." >>> ------ >>> >>> My question is: WHY did Bill/Micro allow this program to be written in >>> the first place? Why are ppl saying to Avoid it at all costs? (yet it is >>> written by M/S) >>> Lastly, and again, .. why did micro put it out there for all to see >>> Knowing Full Well that NO registry cleaner works at all.. and especially >>> considering each persons computer is different due to d/loads and >>> software and blah blah. >> <snip> >>> What do you reckon? >> >> A very sore subject! I reckon that many longtime MVPs are Microsoft's >> most vocal critics (vs. newer MVPs who are basically "MS Enthusiasts;" >> e.g., the obnoxious Win7 Launch Parties). >> >> I can't think of one Windows MVP who didn't take MS to task for >> misguidedly including a "Registry cleaner" in OneCare when beta testing >> began in 2006. (Four years later and we're still griping about it so if >> you think MVPs have much "pull" these days, think again.) >> >> The Windows Live OneCare Safety Center's >> (http://onecare.live.com/site/en-us/default.htm) "Clean up" scan is MS's >> online "Registry cleaner," and it's included when you run the Full >> Service scan. Even while the applications were in beta, this started >> causing problems (i.e., stuff was "cleaned" that shouldn't have been), >> so much so that Support had to make this page available, primarily due >> to MVP pressure): >> http://boards.msn.com/safetyboards/thread.aspx?ThreadID=4868 >> >> While OneCare itself has been discontinued (cf. >> http://onecare.live.com/standard/en-us/activation/oc_eol_guidance.htm), >> the online scans remain available and haven't been changed at all. >> >> The The Windows Live OneCare Safety Center's online scan for Vista/Win7 >> is the Full Service scan only (i.e., you can't just run the Protection >> scan) and continues to cause problems for users; cf. >> http://onecare.live.com/site/en-us/center/whatsnew.htm. >> >> Even Mark Russinovich (Technical Fellow in the MS Platform and Services >> Division) criticized the use of Registry cleaners back in 2005: >> http://blogs.technet.com/b/markrussinovich/archive/2005/10/02/registry-junk-a-windows-fact-of-life.aspx >> >> >> Again, a very sore subject! > > Well, first off re: http://onecare.live.com/site/en-us/default.htm > > The statements " The onecare cleaner offers no chance to backup what is > removed and whatever it removes is gone, forever." > > and > > "Should it mistakenly remove a key or value needed by your operating > system or software it's gone along with your program or operating system." > > are not true. > > C:\Documents and Settings\username\Local Settings\Application > Data\Microsoft\Windows Live Onecare safety scanner\Backup > > is the location in XP where WLSC_Backup Registration Entries along with > XML Documentation are stored. > > Registry cleaners themselves do no harm, it's the clueless twit using them > that causes the harm, the proof is in the two false statements quoted > above. > > I'm surprised you didn't tell Eddie of the Backup folder. >
From: Bill in Co on 11 Jul 2010 15:58
That's just because THEY didn't run it at the right time of the day. What's the matter with you? It takes skill to know what time of the day is best. :-) Unknown wrote: > Absolute hogwash. There have been hundreds of posts on this newsgroup of > computers being rendered inoperative > by the user running a registry cleaner. Simply running a registry cleaner > has caused damage. > > "Incognitus" <in(a)ccurate.com.invalid> wrote in message > news:i1chmc$875$1(a)speranza.aioe.org... >> On 07/10/2010 10:03 AM, PA Bear [MS MVP] wrote: >>> >>> Eddie wrote: >>>> PA Bear [MS MVP] wrote: >>>>> If you ever think your Registry needs to be cleaned, repaired, >>>>> boosted, >>>>> tuned-up, cured, tweaked, fixed, or optimized (it doesn't), read >>>>> http://aumha.net/viewtopic.php?t=28099 and draw your own conclusions. >>>> >>>> >>>> Hi [PA], >>>> >>>> I have followed and respected your replies to posts for years, and also >>>> your affiliation toward ms products. >>>> >>>> I do have a question though regarding this thread, but first, an >>>> excerpt >>>> from the link you posted re: O/P. >>>> ------\/ >>>> >>>> "Microsoft has a freebie online program at >>>> http://onecare.live.com/site/en-us/default.htm. Being the Godfather's >>>> program it should be safe....theoretically. It didn't do me any harm. >>>> I strongly recommend that you, or anyone else, avoid using the onecare >>>> registry cleaner >>>> >>>> Here's why: >>>> >>>> The onecare cleaner offers no chance to backup what is removed and >>>> whatever it removes is gone, forever. Should it mistakenly remove a key >>>> or value needed by your operating system or software it's gone along >>>> with your program or operating system. I've seen onecare's registry >>>> cleaner completely hose systems." >>>> ------ >>>> >>>> My question is: WHY did Bill/Micro allow this program to be written in >>>> the first place? Why are ppl saying to Avoid it at all costs? (yet it >>>> is >>>> written by M/S) >>>> Lastly, and again, .. why did micro put it out there for all to see >>>> Knowing Full Well that NO registry cleaner works at all.. and >>>> especially >>>> considering each persons computer is different due to d/loads and >>>> software and blah blah. >>> <snip> >>>> What do you reckon? >>> >>> A very sore subject! I reckon that many longtime MVPs are Microsoft's >>> most vocal critics (vs. newer MVPs who are basically "MS Enthusiasts;" >>> e.g., the obnoxious Win7 Launch Parties). >>> >>> I can't think of one Windows MVP who didn't take MS to task for >>> misguidedly including a "Registry cleaner" in OneCare when beta testing >>> began in 2006. (Four years later and we're still griping about it so if >>> you think MVPs have much "pull" these days, think again.) >>> >>> The Windows Live OneCare Safety Center's >>> (http://onecare.live.com/site/en-us/default.htm) "Clean up" scan is MS's >>> online "Registry cleaner," and it's included when you run the Full >>> Service scan. Even while the applications were in beta, this started >>> causing problems (i.e., stuff was "cleaned" that shouldn't have been), >>> so much so that Support had to make this page available, primarily due >>> to MVP pressure): >>> http://boards.msn.com/safetyboards/thread.aspx?ThreadID=4868 >>> >>> While OneCare itself has been discontinued (cf. >>> http://onecare.live.com/standard/en-us/activation/oc_eol_guidance.htm), >>> the online scans remain available and haven't been changed at all. >>> >>> The The Windows Live OneCare Safety Center's online scan for Vista/Win7 >>> is the Full Service scan only (i.e., you can't just run the Protection >>> scan) and continues to cause problems for users; cf. >>> http://onecare.live.com/site/en-us/center/whatsnew.htm. >>> >>> Even Mark Russinovich (Technical Fellow in the MS Platform and Services >>> Division) criticized the use of Registry cleaners back in 2005: >>> http://blogs.technet.com/b/markrussinovich/archive/2005/10/02/registry-junk-a-windows-fact-of-life.aspx >>> >>> >>> Again, a very sore subject! >> >> Well, first off re: http://onecare.live.com/site/en-us/default.htm >> >> The statements " The onecare cleaner offers no chance to backup what is >> removed and whatever it removes is gone, forever." >> >> and >> >> "Should it mistakenly remove a key or value needed by your operating >> system or software it's gone along with your program or operating >> system." >> >> are not true. >> >> C:\Documents and Settings\username\Local Settings\Application >> Data\Microsoft\Windows Live Onecare safety scanner\Backup >> >> is the location in XP where WLSC_Backup Registration Entries along with >> XML Documentation are stored. >> >> Registry cleaners themselves do no harm, it's the clueless twit using >> them >> that causes the harm, the proof is in the two false statements quoted >> above. >> >> I'm surprised you didn't tell Eddie of the Backup folder. |