Stream Read Error

[GoogleCodeExporter]

I am getting the following error when trying to open my .kne file:

"stream read error"

I was using the program the night before, and saved my file successfully.
When opening the program in the morning, the error above came up and would
not open the file. 

The file was located on a usb drive. I checked the file and it seems to be
corrupted. I cannot move or copy the file anywhere else. I checked the
properties of the file, and it said it was 999kb in size, which makes me
wonder if there was a problem with the code or compatibility with files
over a certain size?

I tried a lot of things, including trying to open it in other similar
programs that import keynote files, but nothing has worked. I upgraded my
keynotes program to the recent version (from this website), but still nothing. 

Any help would be absolutely incredible because I had a lot of information
added since my last backup! 

If anyone knows of a program to open a .kne file (most only accept .knt),
let me know as well!

Thanks

Original issue reported on code.google.com by itbelink@gmail.com on 17 Dec 2009 at 4:44

[GoogleCodeExporter]

Hi itbelink,

if you say you can't move or copy the file on or from your USB stick you mean 
that 
you see the file in explorer but you can't manage the file within explorer 
(supposed 
you are using Windows)?

If this is true then your chances are not good because your stick might have 
failed 
maybe even just in one bit during your last write off. The fact that the file 
was 
saved successfully does not mean anything as windws is not verifying what it 
writes. 
It finds about write errors only during read operations (that's when the shit 
has 
already happened and it's too late) or if it comes to hard errors like a dead 
disk. 
This is something even Windows takes note of. The size of your file is not an 
issue 
here. 1 MB is not much for KeyNote.

If your encrypted file has been hit by just one failed bit this is enough to 
render 
it completely unrecoverable.

The alternative ways to get acess to a file normaly make only sense if it is 
not 
encrypted and if it has  not been damaged too hard: 
1. make an image of the drive before you go on.
2. run a data recovery tool of your choice and try to copy the visible file via 
that 
tool. The file access works in a different way then through explorer.
3. you might also run a chkdsk against the affected drive to find if there are 
any 
errors detected.
But all this will not get your file back if it was encrypted and placed on the 
wrong 
spot.

Original comment by stati...@gmx.net on 18 Dec 2009 at 5:38

[GoogleCodeExporter]

Thank you for the explanation. That sounds right and makes sense. 
Unfortunately, I
decided to run the chkdsk yesterday after reading some other information from 
other
forums. Chkdsk fixed the corruption to the point I could copy it to another 
drive,
but unfortunately it must have ruined the encryption or something because now
keynotes completely doesn't recognize it.  I've tried copying it over and 
opening it
on another computer, but nothing has worked. Yeah, I goofed. 

At this point I'm kind of giving up and counting my losses, unless there are any
other suggestions that might work. I wish I would have waited and just went 
with the
suggestions above. Hopefully my mistake will help others with some insight 
though.

Original comment by itbelink@gmail.com on 18 Dec 2009 at 5:59

[GoogleCodeExporter]

Hello itbelink
I know it has been a long time since your issue report.. Anyway I would like to
confirm what staticp indicated to you, and recomend you to use the backup 
options
that KeyNote offers. Of course, it is also always convenient to make regularly a
backup to a different place.
That is something common to the use of any program but specially when then 
document
is encrypted or compressed.

I hope you could recover most of your work
Regards

Original comment by dpra...@gmail.com on 30 May 2010 at 3:54

• Changed state: Invalid

[GoogleCodeExporter]

Hi dpradov,

Yes I had made backups, but unfortunately my other drive I backed up to failed 
on me
(hardware failure).  One of those freak accidents where both the original AND 
the
backup fail. Extremely extremely rare, but happens. I just had some really 
really bad
luck that day!    I luckily was backing up every 2 weeks, so I still had a 
previous
backup around 3-4 weeks prior. So I lost everything I had done in 3-4 weeks, 
which
was actually quite a bit, which is why I was hoping for a recovery. 

This is just one of those things that happens with technology, so can't do much 
about
it.   Feel free to close this thread, I don't think there's anything left to 
do. 

Thanks for trying!

Original comment by itbelink@gmail.com on 4 Jun 2010 at 3:22

[GoogleCodeExporter]

Hello, really you had bad luck, but on the other hand it isn't so strange.. 
(Murphy's
law)

Original comment by dpra...@gmail.com on 4 Jun 2010 at 10:11