New
#11
This file might be a key to figuring out how many bits things got pushed to the left or right. It contains the name of itself, as well as the names of other files and/or the folder "NOTEBOOKS"(?) which it was in. So... If anyone ever gets any guesses as to how many bits the titles and path directory of near by documents would roughly be from the file, perhaps that could be helpful. It certainly should not contain what it has in it. https://mega.nz/file/15diTbqA#2LkEM-...9oEuPsm-UE4qN4
That said, I've discovered audio albums are in perfect working order, photographs, PDFs, ODT (Open Document Format), seemingly all good. In the link I posted that was mentioning the bits being pushed left and right, they mentioned that .txt files are more vulnerable to data loss; however, 1 photo and a couple .rtf documents do seem out of order or damaged beyond usability. So... is the data really lost on the text documents if the vast majority of all other formats is just fine?
Sure a few images are dead, but that might have been because of the brief copying of data over them before I cancelled the file moving onto the drive. The oddity is, that almost everything is okay, it's mostly the .txt and a few .rtfs which are seemingly dead. Again, it's not that the TXTs are unrecoverable, because many are also recovered just fine. Why are many okay, and some are not? If it's really a problem with TXT being more vulnerable and harder to recover, wouldn't they all be corrupt?
I noticed, that opening some of the documents in Libre Office prompted a "Choose Character set" option. I tried with Unicode, Unicode 7, Unicode 8, and a few of the "Western" or English based character sets and all I got was the same well spaced paragraphs with different unreadable characters.
Remember one of those files posted, and a few others I've found, had contents which said the file's program(?) could not be used in DOS. The Linux recovery software I was using was on a DOS environment (I believe -- not sure). So... Was the Linux (DOS based?) recovery software simply unable to read them because it didn't have the linguistic support? Can they be recovered correctly and in intact form if we use a non-DOS recovery process, or something which support the format(character set) of the text files.
All of the text files were created with these settings:![]()
That is "Format (Line ending):
Windows (CR LF)"
and "Encoding:
UTF-8"
and set to "Apply UTF-8 to opened ANSI files" which I guess means they'd be saved in UTF-8.
Based on my Sherlock Holms detective-clue-spotting skills, the Linux (DOS Based) recovery software could not read the Windows CR LF format. Am I wrong? I don't know, that's beyond my skill set.
Do I need a recovery software that can detect "Windows CR LF"? Perhaps I should try EaseUse again, or Disk Drill, or MiniTool, or any of the others with unhelpful help sections. Maybe if I offer to pay them they will be able to inform me about these technical details before purchase. ...Which of these companies uses expert tech-support instead of sales-people support?
- - - Updated - - -
This is one... The gibberish. I recognize this note because I was playing with it a week ago. The small note within, is the same size as the English note which was supposed to be there.
Can anyone translate this note? https://mega.nz/file/Zo1mgRZQ#Gd781M...6GxdpmHnbcysOU
Never mind if your English translation is not related to the the file name; the English text within is expected to be different as that's how it was originally saved.
"Help me Onlyone Kinobe
You're my only hope."
- - - Updated - - -
Trying out some character set detection... It's not going well.