marmite
-
Posts
867 -
Joined
-
Last visited
Posts posted by marmite
-
-
Once booted up into the Ubuntu operating system, go to "Places" in the top menu bar and delete any file or folder at will.
Use with care because you can delete without Windows rules and permissions.
You wouldn't want to delete something like your Windows XP operating system.
If you think this could be some type of malware, virus or rootkit you should visit the Spyware Hell section of the forum.
Agree with the above. I hadn't thought of that and I'll add it to my ideas list
. Doesn't have to be Ubuntu ... could be (for example) any recovery disk that gives you independent access to your file system.The only thing that concerns me about the general principle is that files get locked (or have their access permissions changed) for a reason. I've never yet been unable to delete a file without good reason ... like that it's an essential operating system file. In a healthy (non-infected) system there's pretty-well always a service or an exe or a driver you can disable at start-up (as usual, used with care Sysinternals autoruns is excellent for this). If you resort to a boot cd any old time you get a locked file, without considering or being aware of what you're deleting, there is a possibility of messing up your installation ... so I fully echo the comment in Jamin4u's post about taking care!
But ... this method wouldn't seem be a problem in this instance.
-
-
I'll happily live with reduced UAC and fight malware in other ways thank you very much.
-
After restart, all restore points were gone. I think CCleaner does the job correctly, besides it gives this error message.
If it is WMI, I think it's Windows that's giving you the error, not ccleaner.
-
I haven't used command-line much so this is a learning curve for me.
No worries
Can you give me an example for MoveFile?Do I need navigate to folders or show a path?
1) To move a file.
2) To delete a file.
Okay. To make sure your exe is picked up easily, stick PendMoves and MoveFile in your system32 directory for now. This means that no matter what folder your command window opens at, the OS will be able to find the MoveFile exe easily.
To do a move, create a file something like c:\movetest.txt in explorer.
Then do: MoveFile c:\movetest.txt c:\moved.txt
(If your folder/file has spaces in it you'll need quotes around the name ... eg MoveFile "c:\my movetest.txt" c:\moved.txt)
Run both PendMoves and WhyReboot and you should now see this listed for a move.
To do a delete, create a file something like c:\delete.txt in explorer.
Then do: MoveFile c:\delete.txt ""
Run both PendMoves and WhyReboot and you should also now see this listed for deletion.
Reboot and see what happens! Rather than c:\movetest.txt and c:\delete.txt, you should now just have c:\moved.txt
Obviously if either of these were locked, it would enable them to be (re)moved at reboot.
My example files were conveniently located in c:\ ... longer paths are a pain to type in. One really useful tool for getting the path to a file is PathCopyEx (http://www.mlin.net/other.shtml), which adds a Windows explorer context menu 'Copy Path to Clipboard' for copying the selected file or folder path. One of the most useful context menu entries ever.
-
Thanks. I'm getting auto-update problems; saved me having to hunt for the download link.
-
When you do have some free time check out this page. Just found it in a search. Theres more info there than I previously knew about.
Thanks ... I found that one last night too ... couldn't find any mention of logoff / shutdown scripts though!!!
-
Makes sense now that I understand I need to run the command-line app through a command window.
Yeah ... there's kind of a clue in the name
Hope it's working now anyway.
-
I was addressing the point that CC can write to the registry key and execute at shutdown ...
I realise that; but that's exactly what I was querying for reasons stated above. I am fairly sure that certain GP features won't work on an XP Home machine, but I think I'm coming round to your way of thinking that for (e.g.) logoff scripts it will work. Unfortunately I don't have access to my XP Pro machine at the moment so I can't see the format of the registry entries to try it out on this XP Home machine.
-
The command-line window just flashes open & closed.
Must not be Vista compatible given the release date of "Published: November 1, 2006".
Thanks again
You have to open a command window (just type cmd in the run box) and then run it from inside there. You also need to be in the right folder for your exe location (or put in the system directory since that path is always available). Type 'PendMoves at the command prompt.
The date shouldn't be an issue, assuming Vista still uses the same registry locations.
-
The Group Policy Editor is just a UI. You should have a service named: Group Policy Client
Its avail in XP, Vista and 7. Depending on the OS edition you may or may not have gpedit.msc
I cant speak for 2k and NT as I never used either of those enough to remember.
Sure, the console is a UI, but there are other components and directory structures involved. There are plenty of conflicting articles about whether GP will run successfully on XP Home, for example. I've tried installing the 'recommended' components to 'convert' an XP Home machine and have only achieved limited GP functionality. It may be that those particular registry entries (shutdown/logoff) would function ... but for GP as a whole I still believe it's more complex than just adding appropriate registry keys.
Out of the box ... I suspect NT would have had GP, W2K does, XP Pro does, XP Home doesn't.
-
How do you use PendMoves v1.1 and MoveFile v1.0.
Are they Vista compatible?
They're both just simple command-line apps ... the usage is given at the end of the linked page posted earlier.
PendMoves is effectively just a command-line version of WhyReboot.
MoveFile always needs two parameters ... the first is the file to be moved/deleted and the second is either the new file name if the file is to be moved, or "" if the file is to be deleted.
As far as I know they should work on Vista ... easy enough to try PendMoves and see if that runs okay
-
Deleting the folder at reboot is probably the way to go.
MoveFile just uses the standard Windows 'PendingFileRename' registry keys ... you could enter the details manually in the registry if you really want to. It's the same mechanism Windows itself uses to move or rename files. So it's not so much a program running at startup, as supplying filenames to the out-of-the-box Windows start-up functionality. Not sure if it works at folder level too though.
I've never used killbox, but as you say it might well incorporate the same mechanism.
This is a good little app for seeing what moves are pending without having to dig around in the registry ... http://exodusdev.com/products/whyreboot (although it was written for a slightly different purpose).
Oh and incidentally it's also the same mechanism that ccleaner uses to remove temp internet index.dat files.
-
GP shutdown scripts are stored in the registry under: HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Group Policy\Scripts\Shutdown
They may well be, but as I said I'm not sure it's that simple. If the OS version isn't supporting GP, is the OS going to pick the key up? I could always try it I suppose
-
-
Nice idea ... +1 to the notion of a separate new application. In my view I don't think it would be appropriate to add something like that to ccleaner.
There are quite a few free duplicate file finders out there, but I definitely think there's room for something a bit more fully-featured
-
A brief google on 1717s suggests it might be related to WMI. Have you tried it after a reboot so your WMI service is in a stable state? If it is WMI there may well be a corresponding entry in your Windows Event Log.
-
Instead of letting the user fiddle around in some nested, hidden Group Policy editors or Registry branches
CCleaner should offer a simple checkbox which let it run at shutdown time.
It already offers shutdown after a fashion ... as in "run then shutdown". I.e. it triggers a shutdown on completion rather than responds to shutdown events. Don't forget that ccleaner requires a user context, so it has to be done before logoff (as per your original post). It's no use having it in the shutdown script because the context has gone.
Also, not all OS versions (e.g. XP Home) support GP and I don't think (though I've not tried) it's as straightforward as just manipulating the reg keys in those cases.
-
Sysinternals' MoveFile can be used to schedule the file to be moved/deleted at reboot before anything gets a handle on it.
-
FileASSASSIN is ineffectual. It simply yields the error message: ? ? refers to a location that is unavailable ? info may have been moved to a different location.?
Unlocker claims to delete the object, but it doesn't.
Judging by all of the error messages from your last two posts it sounds as though it's no longer there!
What is now telling you that it is still there? Have you refreshed any apps where it is(was) visible?
-
... so i don't think ccleaner will erase any registry item that is necessary. it almost erases nothing anyway. so i don't see a danger in that.
Tell that to people who believe they have had problems because of the reg cleaner's behaviour!
acting on the basis of "fear" is a primitive way of acting. only fashist ideologies expect people to first fear then act on the basis of that fear.Fascism - wow, a bit heavy for a ccleaner forum. And in this case a completely inappropriate analogy.
I agree with fireryone that ccleaner has to cater for people who are new to computing. The registry is not something to be feared, but it is definitely something to be respected. It's usually people who have a blas? attitude to things like this that end up being bitten on the backside.
Yep such warnings annoy me too. However you can't start on the basis that everyone knows what they're doing. But as you and other posters have suggested, what you can do is to have a check-box in the Advanced tab so that experienced users can turn warnings off. That should keep everyone happy. And if the existing box doesn't do that (I don't know - I don't clean the registry with ccleaner) then I believe that it should be changed so that it does, or a new check-box should be added just to turn off registry warnings.
-
Hi LegoBas
First some objectivity. From the tinyhacker article ... "Did you realize that the DNS cache on your computer is tracking everything you do". The function of the resolver cache is not to 'track activity', it is to make the resolution of domain names (not individual web pages) on your PC quicker by caching website domains you have visited recently. This is a good article to read through ... http://support.microsoft.com/kb/318803
As explained in the Microsoft article, you can turn DNS caching off via the Services console if you want to. The article also shows you how to display and clear the entries that you have in your cache at the moment.
Ccleaner doesn't currently clear this; I have said before that I think this would be a reasonable option to include; particularly in comparison to some of the more esoteric suggestions that are made for ccleaner
-
... I was never aware of the fact that this kind of thing existed.
While the thread is bumped up I'll happily plug Sysinternals
And there's a lot more ... http://technet.microsoft.com/en-gb/sysinternals/default.aspx
Some of this stuff is command-line only, so a degree of comfort is required with using some of those utilities ... but there's something for everyone
The whole suite really is a 'must have'. Autoruns and Process Monitor (different to Process Explorer) are two really useful tools for seeing what's going on. -
Hi thoste
e.g. "C:\Program Files\CCleaner\CCleaner.exe" /AUTO
See here for more information on ccleaner command-line usage.
Yes you should be able to use GP to do this.
. Doesn't have to be Ubuntu ... could be (for example) any recovery disk that gives you independent access to your file system.
CC doesn't remove cookie
in CCleaner
Posted
Absolutely, which is why I then said ...
The point I was making is about the general principle of using this method for 'any locked file file' ... original post now tweaked for clarity