marmite
-
Posts
867 -
Joined
-
Last visited
Posts posted by marmite
-
-
I swear I read somewhere about a new harddrive spec that my effectively start to kill of XP machines...
Interesting article; thanks. Best get a spare in then
-
Microsoft need to sell more copies of Vista / Windows 7 so dropping support for 2k/XP would probably create an incentive for the no so computer minded to spend more cash.
I don't think selling W7 is going to be a problem. And I think (hope!) XP SP3 is going to stay in support for quite some while, given the dire take-up of Vista.
-
Does the version you now have on your website include the toolbar? Is there an option to NOT include it.
There are versions with and without the Yahoo toolbar. Check out the builds page here ... http://www.piriform.com/ccleaner/builds
All versions that package the toolbar have its installation optional; you can deselect it when installing CCleaner.
-
+1. A right-click "Copy text" would be a very simple but useful addition.
-
Speccy Showed My Operating System As Windows XP SP3 And Installation Date As 07 May 2005, 20:54. And I Want To Tell You That Windows Xp SP3 Was Released In April 2008, Then How It Will Be Installed in 2005.
I guess Speccy shows the date that XP was installed not the date the Service Pack was applied, which makes sense to me.
-
Support for XP SP2 ends on the same day.
There's no excuse for any non-corporate user not to be on SP3
-
... I wouldn't feel comfortable using an unsupported OS while online.
I think it really depends on whether any unpatched vulnerabilities exist. I think you only have to worry if new exploits come along that affect that OS. And 2000 is certainly unlikely to be the specific target of any new malware. So you may be okay ... it's just a question of keeping an eye on the situation and trying to mitigate risk where possible.
-
Apparently not exist: http://docs.piriform.com/defraggler/advanc...line-parameters
It doesn't exist as a specific command line paramater, no. But I guess where the OP is coming from is questioning whether freespace defrag is the default behaviour in a command line defrag - and the documentation doesn't answer that question.
-
Sad to see it dying off though. Compared to the clunky Windows NT 4, Windows 2000 was an absolute joy to work with. And I'd still take it over VIista any day!
-
Isn't browsing using a "private tab" fairly secure as well?
No (assuming it's akin to IE's private browsing). It doesn't prevent malicious content from being downloaded. All that it does is to stop content (e.g. cookies, history and temporary internet files) being stored on the hard drive - it's more of a privacy thing.
-
The amount of MFT freespace would usually be much less than the amount of disk freespace - so I am guessing it would be faster to delete MFT freespace than to delete all disk freespace.
Yep, but the only reason I'm aware of to delete MFT freespace is a security measure to erase MFT file metadata. Since the files themselves are still potentially in the unerased freespace, what's the gain? Surely the files themselves are the priority and MFT is just that bit extra. Erasing the latter without the former doesn't seem to achieve much.
-
A quick and interesting read, thanks. As was his own blog article (http://ccollomb.free.fr/blog/?p=69) and the one linked to on the nirsoft site (http://blog.nirsoft.net/2009/05/17/antivir...all-developers/) about anti-virus false positives and their impact on small software companies.
-
Previously I had the other version installed in AppData but removed that and installed it via google pack ...
Is that the differentiating factor? Assuming CCleaner looks for a 'known' application installation location by examining a known app-specific registry key, is this key different for a 'google pack' installation?
-
What I suspect might have happened is that, you decided to install the latest version of CCleaner and during the installation process, you might have the "Create Desktop Shortcut" option unchecked making the old shortcut basically invalid but I'm not really sure of this scenario because you only said that nothing happens when you click the desktop shortcut and how exactly this does not do anything is unknown to me.
The CCleaner exe location doesn't change between versions. If you leave the shortcut option unchecked in a subsequent update the old one won't be removed and it will still work correctly.
-
I had a mate who was into Yes at school back in the 70s ... I was more into Floyd / Genesis
But although I've still got a stack of vinyl in the attic somewhere, I haven't had a turntable since an ex got custody of my Pioneer kit about 15 years ago
-
As Nergal as shown, there are quite a few articles around this issue. In asking you to try updates separately I was trying to narrow the field down a little ... as you say though it seems to be something that applies to the update install process itself, rather than to a particular update.
His first link is one I looked at, and it does potentially look relevant, though needs to be followed with care.
So if I were you I would try the 'System Update Readiness Tool' mentioned at post 3 in the second link ... http://support.microsoft.com/kb/947821. You can just down load and run it and it may fix errors it finds or write them to a log file.
Try running it and then doing another Windows Update. If the update still fails, look for the SUR Tool logs in the location specified in the above link (you can just put '%SYSTEMROOT%\Logs\CBS\' into the Windows Explorer address bar to display the folder) and see if that gives you any more information.
-
Again, thanks for all your help. Vista x64 can be a very good OS but it does require well researched and well written software to perform at it's best.
You're welcome. Pity we didn't get to the bottom of it - I suspect there are other people out there who are happily working with Vista x64.
But as you say, you have to draw the line line somewhere, so fair play for giving it a go
-
May I ask whether you two are running Vista? If so, is it x64?
I'm not, although I've just looked at a machine that is (32-bit)!
To reiterate, you'll only see a PendingFileRenameOperations value if there's an operation queued for the next reboot. The machine I just looked at does have a value there and I see no reason for x64 to be any different. So I'm wondering if, for whatever reason, CCleaner isn't modifying (or can't modify) that key.
It would be useful if anyone else can confirm CCleaner's operation on Vista x64.
Do you have any security software running that's protecting your registry keys?
-
Hi Laura
I would think it's unlikely that CCleaner was the actual cause of this, but as Ishi says if you used the registry cleaner part then try restoring any CCleaner registry backups you may have made.
I'm assuming you're running Windows Update? Can you run this manually and select the custom option, which lets you pick which updates to install. If you can do this and install them one at a time (so you may have to run Windows Update several times) to try and find out exactly which update fails. Then post back with which update that is, and confirm that the error code is the one you mentioned above.
-
Try this link to MajorGeeks.com http://www.majorgeeks.com/CCleaner_Slim_No...lish_d4191.html for your download. Please post back on your results either way.
I'm sure from their reputation that the majorgeeks download will be perfectly kosher, but as I understand it (I may be wrong) the only two download sites that Piriform endorses are its own and FileHippo, for which links are available here ... http://www.piriform.com/ccleaner/download. The slim build you refer to can be found on the Piriform builds page here ... http://www.piriform.com/ccleaner/builds
-
That is always assuming that 'Whyreboot' works with Vista x64.
Edit :- 'Why Reboot' doesn't work with Vista x64 - I ran a check.
Ah - I couldn't see anything that said that explicitly.
All that Whyreboot does is look at a registry value; it's just that as a multi-string value it's easier to see 'read' its content displayed in Whyreboot. I'm assuming that same value still applies ... HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations. The value only appears when there's an operation to apply, so you'll still need to run CCleaner first.
(Note this is not the same as the HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\FileRenameOperations key.)
-
Does including index.dat files in cleaner.ini (is this where the entries are?) do anything more than ordinary files? If no then CC won't be able to delete them as Windows has them locked. I don't use CC control files so this is just guessing.
Agreed, though like it's speculative. But assuming they're still checked under Windows / IE then they should be scheduled for deletion at reboot anyway, I'd have thought.
-
As I said, the content and size remain the same after running CC. The content is shown using the aforesaid program 'Index.dat Analyser' which also makes a good job of clearing the contents if required.
It's the content I'm interested in - the initial creation size is constant.
So index.dat analyzer shows file content ... now I know
Try this ... http://exodusdev.com/products/whyreboot ... it shows changes scheduled at reboot. Your index.dat files should be listed there after you run CCleaner.
-
No, wait, that's a terrible idea. My vote goes toward these two being separate options for a future release.
But to reiterate, I'm still looking for a reason why you would want to delete MFT freespace but not disk freespace. What is the benefit?!
POLL:Windows 8 speculations....
in The Lounge
Posted
Until W7 came out, it amazed me that some people weren't running it.