cyke64 / keynote-nf

Automatically exported from code.google.com/p/keynote-nf
0 stars 0 forks source link

Keynote NF doesn't open my file, "buffer error" #395

Open GoogleCodeExporter opened 9 years ago

GoogleCodeExporter commented 9 years ago
>What steps will reproduce the problem?
I don't remember doing something unusual at the time the bug was observed. But 
quite often I use copy/paste to insert images from web-pages and graphic 
software (from buffer). Because I can't choose .jpg format via "Insert" -> 
"Picture", though I can insert jpg pics via buffer ^^

>What is the expected output? What do you see instead?
While trying to open my .knt file I get the error "buffer error" and no file 
opens. (screenshot is attached)

>What version are you using? On what operating system?
KeyNote NF  v.1.7.9.1 Beta 1
Win XP Professional SP3

>Please provide any additional information below.
Initially my file was ~120Mb. Then I tried "compressed" format and then 
"encrypted" format. The last day I chose to save my keynote file in format 
"Keynote compressed file". And now KeyNote doesn't open it. 
Backup .bak file is the same, so it didn't help me.
It looks like the file is damaged, because it doesn't open in all these cases: 
after restarting OS, in another OS, after off/on the computer, after 
reinstalling keynote, in older version of keynote.

Original issue reported on code.google.com by dina.yak...@gmail.com on 10 Apr 2011 at 10:51

Attachments:

GoogleCodeExporter commented 9 years ago
I wonder if I could decompress my corrupted file and then try to restore it.. 
Is it possible?

I have found out the method of compression (?) in this issue -> 
http://code.google.com/p/keynote-nf/issues/detail?id=175
>Delphi zlib 1.2.3 implementation by Roberto Della Pasqua and previous
I have even found zlib 1.2.3. But there is only source code, no executable 
decompressor.

I will be gratefull for any ideas and even for an answer "it is impossible to 
restore that file!" ^-^

Original comment by dina.yak...@gmail.com on 15 Apr 2011 at 11:23

GoogleCodeExporter commented 9 years ago
I just received the same error. When I launched Keynote this morning, the 
last-used file that would normally load on startup failed to do so, and 
instead, a "buffer error" dialog pops up. (Exactly as dina describes above.)

The last change I'd made to that file was adding a few lines of text the night 
before; that's it. However, I did recently change file permissions on the 
portable SSD card where the Keynote EXE and data are stored, but I was still 
able to open and use Keynote normally afterward, and I can open the BAK files 
(whose permissions have also changed). Unfortunately, I stand to lose data if 
I'm not able to open the KNT file since the most recent changes weren't backed 
up.

Keynote version: 1.7.9.1 Beta 1

Platform: Windows 7 x32/x64 Enterprise. (The .knt files are stored on a SSD 
card and shared between two machines - one is x32 and the other is x64.)

Original comment by isthis1t...@gmail.com on 5 Aug 2011 at 3:01

Attachments:

GoogleCodeExporter commented 9 years ago
Can you try the new executable I have just uploaded?

http://code.google.com/p/keynote-nf/downloads/detail?name=Release_1.7.9.2%20Beta
%202.rar

(Version 1.7.9.2 [BETA])

Original comment by dpra...@gmail.com on 7 Aug 2011 at 4:55

GoogleCodeExporter commented 9 years ago
Analyzing the errorI have seen that the message "buffer error" is raised by the 
compression library (Delphi zlib 1.2.3). I have not reproduced the error with 
the actual version of KeyNote NF but I have simulated it reducing the size of 
the buffers used (they are two buffers, bufferIn and bufferOut, each of 32768 
bytes) to smaller values (50, 100, 1000 and so) and I have verified that even 
with very small values, like 50, the procedure can decompress many files, but 
when I include images (copy and paste) then 'buffer error' appears frequently. 
Testing with bigger output sizes (20/40,  50/100 or 50/200, etc) that files can 
be readen ok.
So, I have modified the procedure to dinamically adjust the outBuffer when a
Z_BUF_ERROR is received, doing a max number of retries.

This have been done in revision r141

I will mark the status as Finished. If problem arises I will reopen the issue

Original comment by dpra...@gmail.com on 8 Aug 2011 at 4:00

GoogleCodeExporter commented 9 years ago
Just reporting back that v1792 seems to have resolved the issue in my case, 
allowing me to open the file that causes a buffer error in v1791 and recover my 
data. So thank you for the fast response and resolution.

Original comment by isthis1t...@gmail.com on 10 Aug 2011 at 9:39

GoogleCodeExporter commented 9 years ago
Wow, that's so great! Thank you ^-^ It works!
Since then I have tried another outliners and managers, but I didn't end up 
using any of them.

Original comment by dina.yak...@gmail.com on 16 Aug 2011 at 7:17