Jump to content
CCleaner Community Forums

Augeas

Moderators
  • Content Count

    4,205
  • Joined

Community Reputation

0 Neutral

About Augeas

  • Rank
    Moderator

Contact Methods

  • Website URL
    http://
  • ICQ
    0

Profile Information

  • Gender
    Not Telling
  • Location
    Where Stuff is made, UK

Recent Profile Visitors

2,801 profile views
  1. Yes, but 96 posts in English, and then this? Are we supposed to get the clown reference? Is it a way of sneaking in offensive language? Was ist der Sinn?
  2. All you can do is sort the file size column by clicking on the column header, and then start from the top.
  3. Or 'Not as far as I know', which is more relative than absolute.
  4. You don't give up, do you? It must be the tolerant attitude we have here.
  5. It means, in the most basic terms, that what you are trying to play is not a video file. What has been recovered will be faithfully what is on the storage device. What is on the storage device is therefore not a playable video file (you can replace video with any type of file). Why is this so? It could be because the file has been overwritten, it's FAT32, it's greater than 4gb, it's an SSD, or it's some kind of coding that needs decoding (I have no idea how Kodak holds its files), or something else I don't know about. Can these files be recovered? There's not enough info (there's not any info) to say yes or no, but one could say probably not.
  6. The file count whilst running includes live as well as deleted files. If you are not seeing any deleted files in the l/h pane then possibly there is some selection criteria entered which does not match any file found. It sounds as if you were running a deep scan which I don't think finds RAW files.
  7. I am not confused. Thank you for your compliments, who knows whether CC commits to disk? I would say that it does. Misinterpreting on purpose? The phrase 'SSds were built with many writes to the MFT in mind' certainly implies some constructional abilities. It's actually nonsense, as it's NAND flash that holds the MFT (and all other files) and is either robust or not. On reflection I think you may mean robust in a software sense, and that is entirely down to the file system, in this case NTFS. The SSD knows nothing of the MFT and just doesn't come into it. I'm not going to get drawn into this discussion, and your strawman arguments about fake chips. SSDs last a long time, and that's that. True, you didn't. But this thread is entitled Using CCleaner on SSDs, and it's in a CC forum on a Piriform Bulletin Board, so one might be forgiven for thinking such. You may not believe what I say, but it is frustrating repeating myself. I would suggest that you re-read this thread and perhaps also re-read some of the relevant passages in the previous link (it can be heavy going to tackle all at once). SSDs are far more complex, and different, than many users realise.
  8. It would be better for both brevity and comprehension if if HDDs were left out of this thread, as the title refers to SSDs. I said that CC will fill the disk, not write and delete files one by one. However, as described in detail in the link, zero-byte pages are maped to a default zero-byte page, the SSD doesn't write millions of zero-filled pages. Writing random data certainly will fill the addressable pages on the disk, and deleting them will return to the default zero-filled page mapping, just as you were if you hadn't bothered to do all that in the first place. The MFT is a file just like all the others. It has no special longevity attributes and is unknown by the SSD controller. If Drive Wiper is used then the MFT is wiped as you require. It is not made larger, or for that matter made smaller, in this process. It is not possible to access deleted pages nor the overprovisioning pages on an SSD using non-specialist software running under Windows (and I don't know of any specialist s/w either). If the chips are read in a lab the data is almost certainly encrypted or striped across blocks, and there is no link from one page of a file to another. No financial business or organization that might have sensitive data would use a free utility with no authentication or verification for disk sanitisation, and CC, despite what some of its marketing might claim, isn't intended for that purpose. The SSD life section is a little tongue in cheek. Of course some electronic devices will fail immediately, some will last seemingly forever. An approximation of the life of NAND flash can be made, and it is a very long time. .I have a 512 mb flash drive dating back to 2006 that has been thrashed unmercifully, and it's still good, if semi-retired now.
  9. It is effectively random, as the existing data has been randomised before writing, and the overwriting pattern of zeroes is also randomised, so there is no concept of overwriting a one with a zero etc as many think (at least not in the last 30 years).
  10. To answer your question CC will, if you absoultely force it to, fill the disk with zero-filled files, and then delete them. However CC will warn against this, and indeed it is utterly pointless, achieves nothing, and will hammer the MFT and other system files. It does not even 'fill' the device. It is not, as you imply, 'the ONLY way to "erase" anything from solid state memories'. There is no way, using O/S software. TRIM will do it all for you. There's a lot here that is shall we say contentious, but I'm not going to get into a lengthy exposition. If you want you could read through http://kcall.co.uk/ssd/index.html which goes into considerable detail, even though it is still being updated. You could swap ssd for ntfs in the url for even more bed time reading.
  11. On the SSD the clusters will be mapped to a zero-filled page on delete with TRIM, so you will be recovering zeroes. There's not enough info on the attached USB drive to make a guess.
  12. It's been suggested a few times before, and although there is a likelyhood that some file will be modified or unavailable on a restart, that also applies to a certain extent when running Recuva anyway. I doubt if will be implemented, given how many times Recuva has been updated recently (around zero). I can't see any real reason why you should not work on your system drive whilst running Recuva. It will slow things down a bit but I'm sure you can live with that.
  13. Well, I can't open my files is pretty unspecific, and we're not clairvoyant. At a guess I would say that the files do not contain a correctly formatted header. Recuva copies clusters bit by bit with no alterations, so what's recovered is what's on the source disk. The reasons why the header is not what is expected could well be found in the somewhat slighted file (which saves typing it out every time we get this question). But I'm no expert.
  14. Read through this, the answer might be in there. http://kcall.co.uk/recovering files.html
  15. In advanced mode open Options/Actions and check boxes 1, 2, 3 and 5. Do not apply any filter to the search.
×
×
  • Create New...