3 ms·
Just out of curiosity, if you don't mind, what is it called?
by colejohnson66 10y ago
Just out of curiosity, if you don't mind, what is it called?
- johnchristopher 10y agoMy money is on test????/photo???.
- johnchristopher 10y agoNot that I care for the karma but why is it being downvoted ?
- function_seven 10y agoI think because the comment is confusing. Are the question marks a text encoding error?
- paxcoder 10y agoI reckon people find it uninformative. If not, then I'd guess the exact opposite. You should know which.
- gaur 10y agoAs the sister comment says, it's because your comment doesn't make sense. What does "test????/photo????" mean?
- johnchristopher 10y agoWell, it's a guessing game to know what company the parent parent is referring to and there are two well known recovery software but I didn't want to give out the name so others could keep on guessing. So I just wildcard masked the thing.
- davb 10y agoIt's an obfuscated reference to a popular open source data recovery toolset. I think the parent was trying to avoid potentially "outing" GP against their wishes, by making a vague reference that some might get.
- jlgaddis 10y agotestdisk/photorec
- nxzero 10y agoPoint is it doesn't matter, as a creator, maker, investor, etc. -- you always have a choice, and for some the temptation to follow the money even if the path is one they would not take if given another choice of equal financial value.
- feelix 10y agoThis is the data recovery app consumer version that kicked it all off (it has the same engine as the original one): http://macdaddy.io/mac-data-recovery/ http://macdaddy.io/mac-data-recovery/ You wont find any data recovery software that does a more thorough scan than that, even though it was written in 2004 or so and has been barely modified since. I spent years writing it, in C, so it ended up highly optimized. In forensics mode it scans a drive byte-by-byte, and it assumes each byte is the start of a file of the 100 or so filetypes that it supports, and it maintains that assumption until it is proven to be false as it goes deeper into that file's data. That way it really shouldn't miss anything. It also transparently UUDecodes, unzips, and otherwise decodes data on the fly as to extract file contents under as many conditions as possible. It uses linked lists to maintain its memory of what files are where until it dumps out its buffer as output files, and it uses binary searches and threads to speed up. All in all it's about 1000 lines of code, though I really don't think that anyone would ever be able to read it except for me. I recently noticed that if you run it over your iTunes Music folder it'll extract and output the media that is contained inside your M4P ("MPEG 4 protected audio") files, and output it as unprotected MP3's. So it effectively strips all of the DRM off of all your media in seconds. Even if you didn't purchase that media (say your friend sent it to you) and couldn't play it before. That was not intentional. You can see that effect in this app: https://itunes.apple.com/app/file-extractor/id1129674765 https://itunes.apple.com/app/file-extractor/id1129674765 which is the same codebase, but it is being applied to used space (files) instead of free space.