Extract to dir;PA can't handle;dir's created anyway

manuangi

try to extract an exe file through the context menu, when PA shows you the “extract to” option…sometimes it’s a file PA can’t handle.

also in those cases, if you chose to extract into a folder, that folder will be created.

wouldn’t it be better for it to be deleted, as the extraction process failed so you surely will delete the new dir manually?

spwolf

What happens if some files were extracted and some were not? Or if folder is already present and file doesnt work? Prefferably, we wont delete files or folders that we dont have to since that is just asking for some bug to kreep in and delete your files.

thanks,

manuangi

@spwolf:

What happens if some files were extracted and some were not? Or if folder is already present and file doesnt work? Prefferably, we wont delete files or folders that we dont have to since that is just asking for some bug to kreep in and delete your files.

thanks,

you’re sort of right, spwolf…yes, that would lead to problems if the dir was already present.

then…maybe a popup win saying “would you like to delete the dir XXX (which was just created)”?

what do you think?

ivan

I have fixed so now if folder was created by PowerArchiver and no files were extracted due broked archive (or unsupported SFX file) will be removed by PoweArchiver automatically.

manuangi

@ivan:

I have fixed so now if folder was created by PowerArchiver and no files were extracted due broked archive (or unsupported SFX file) will be removed by PoweArchiver automatically.

you rock, man! thank you so much!

spwolf

Hi,

here is the latest TEST version, 9.00.34 with fix for this bug. Please let us know if it fixes the issue and if you notice anything else at all. You can install this version over the last one and restart your computer.

Download TEST version 9.00.34:
http://www.powerarchiver.com/test/powarc90034.exe

thank you!

manuangi

let me corrupt an archive with WinHex…and I’ll check!

manuangi

@manuangi:

let me corrupt an archive with WinHex…and I’ll check!

Bug gone…but not completely!

Gone, because PA now tells me at once that the file’s corrupted, and does not create any new dir!
WELL DONE!

“not completely” because I have to click TWICE on “OK” to close PA warning messages, it seems two identic messages come out.

FYI, the “double click bug” was there in .33 as well…check it!

ivan

What double click bug - it wasn’t something mentioned in this thread?

manuangi

no, I had not mentioned it anywhere before…yet it’s related to the bug I opened this thread for.

when a corrupted file fails to extract, no folders are created, ok, problem solved.
but PA tells you TWICE that the file’s corrupted and can’t be extracted, and you have to click TWICE on “ok” to get rid of the warning message…

I think you can reproduce that behaviour quite easily…let me know!

ivan

Still cannot reproduce double dialog. Can you please tell me exact message being shown and maybe send me smallest file you are having this problem with - since double dialog does not show on any corrupted archive.

manuangi

download the following file:
http://user1.7host.com/maiuebsait/mix/corrupted.7z
uncompress and see the avi I created.

here’s the corrupted zip file I used:
http://user1.7host.com/maiuebsait/mix/CorruptedArchive_TestPurpose.zip

so…could you reproduce it now?
pls let me know!

the problem persists with v9.01.01 as well!

manuangi

@ivan: did you read my last message? what do you think?

ivan

Thanks!

I will check it.

manuangi

with the pre-release 9.01.02 PA is back to the situation I reported at the beginning of this thread:

-if you try to extract the corrupted file via “extract here”, you’ll see the extraction windows complete its task but then nothing will be extracted.

-if you choose “extract to \filename” the filename dir will be created, empty

-if you open the archive in PA it will show you the name of the file inside, and if you try to extract or open it from there, you’ll be given the “unexpected end of zip file”, and you’ll have to click twice on the message window to get rid of it.

so, I have to say 9.01.01 was better…ok, you had to click twice on the message win as well, but at least it found out the archive was corrupted, and the message would always pop up!

manuangi

with the latest 9.02.00, nothing has changed with regards to my previous post…

@dev’s: is it going to be fixed any shortly? thanks!

manuangi

@manuangi:

with the pre-release 9.01.02 PA is back to the situation I reported at the beginning of this thread:

-if you try to extract the corrupted file via “extract here”, you’ll see the extraction windows complete its task but then nothing will be extracted.

-if you choose “extract to \filename” the filename dir will be created, empty

-if you open the archive in PA it will show you the name of the file inside, and if you try to extract or open it from there, you’ll be given the “unexpected end of zip file”, and you’ll have to click twice on the message window to get rid of it.

so, I have to say 9.01.01 was better…ok, you had to click twice on the message win as well, but at least it found out the archive was corrupted, and the message would always pop up!

9.10.06: bug still there, unfortunately
W*nR** handles that properly, prompting about the archive being corrupted.

manuangi

@manuangi:

9.10.06: bug still there, unfortunately
W*nR** handles that properly, prompting about the archive being corrupted.

9.11.01: still no improvements about this bug…

manuangi

@manuangi:

9.11.01: still no improvements about this bug…

9.20.04…bug has not been solved yet

@spwolf…it’s annoying! why is it taking it so long…and you seemed to had solved it with the old 9.00.34 (read the first posts here…)

spwolf

I am sorry, we just want to make sure we give it a proper testing, which is what only 9.5 can do…

thank you and I promise 9.5 will fix it!

manuangi

@spwolf:

I am sorry, we just want to make sure we give it a proper testing, which is what only 9.5 can do…

thank you and I promise 9.5 will fix it!

ok, thank you!

manuangi

@spwolf:

I am sorry, we just want to make sure we give it a proper testing, which is what only 9.5 can do…

thank you and I promise 9.5 will fix it!

you are a man of your word!
In 9.5b4 the problem is gone, now no empty dirs are created for corrupted archives anymore!