-
Fast Ring: PowerArchiver 2021 20.00.53
Tech Support4 -
Someone using your name to sell their own product
Tech Support3 -
Extract to /example - BUG
Tech Support5 -
Patchbeam updates not finding new previews
Tech Support3 -
PA 20.00.47 bug extracting ZIP file.
Tech Support3 -
PowerArchiver 2021 20.00.32/44/45
Tech Support4 -
Unknown Files
Tech Support3 -
SOLVED encryption bug
Tech Support3 -
SOLVED File will not extract, takes forever to finish.
Tech Support12 -
PowerArchiver and PACL for macOS
Tech Support5 -
UNSOLVED [Bug / Feature Request] Integrate offline Virtual Drive into the PowerArchiver installer
Tech Support3 -
UNSOLVED extracting issue
Tech Support7 -
SOLVED No Updates Shown
Tech Support5 -
SOLVED PowerArchiver resend codes doesn't work
Tech Support6 -
UNSOLVED File Browser: Operations don't trigger UAC
Tech Support7 -
Fast Ring: PowerArchiver 2019 19.00.51/54/57/58/59
Tech Support24 -
SOLVED Problem: Backspace navigation in Explorer mode
Tech Support3 -
UNSOLVED Smart AI: Preferences not intuitive
Tech Support13 -
UNSOLVED PA 20.00.02 not executing .exe files from archive
Tech Support10 -
UNSOLVED Minor UI question
Tech Support7
Not handling multi-part .rar archives properly
-
v10.10.09
If you have a multi-part .rar archive which is using the ‘old style volume names’ i.e.:
my_archive.r00
my_archive.r01
my_archive.r02
my_archive.r03
my_archive.r04
my_archive.r05
my_archive.r06
my_archive.r07
my_archive.r08
my_archive.r09
my_archive.r10
my_archive.r11
my_archive.r12
my_archive.rar…and you right-click my_archive.r00 or my_archive.r01 (both file extensions are associated with PA) and choose to ‘Extract Here’ - PA just bombs out.
However, if you right-click my_archive.rar and choose to ‘Extract Here’ - PA handles that file extension fine and will extract the archive contents to the current directory.
Can you allow PA to do the same for *.r00 and *.r01 files?
-
it worked before… so we will check it out
-
v10.10.09
If you have a multi-part .rar archive which is using the ‘old style volume names’ i.e.:
my_archive.r00
my_archive.r01
my_archive.r02
my_archive.r03
my_archive.r04
my_archive.r05
my_archive.r06
my_archive.r07
my_archive.r08
my_archive.r09
my_archive.r10
my_archive.r11
my_archive.r12
my_archive.rar…and you right-click my_archive.r00 or my_archive.r01 (both file extensions are associated with PA) and choose to ‘Extract Here’ - PA just bombs out.
However, if you right-click my_archive.rar and choose to ‘Extract Here’ - PA handles that file extension fine and will extract the archive contents to the current directory.
Can you allow PA to do the same for *.r00 and *.r01 files?
hmm…v10.10.09???
-
10.10.09 is a test version of beta 2.
So it is not available via Update (at least not yet).
Check other threads if you must try it.
-
10.10.09 is a test version of beta 2.
So it is not available via Update (at least not yet).
Check other threads if you must try it.I find out links…
It alpha version…
Why so complicated author do?
-
I find out links…
It alpha version…
Why so complicated author do?alphas are not posted as betas until they become betas… so no, you wont see that version up on the site until we think it is ready.
-
Some more info to report about this:
If you have a 2-piece multi-part archive e.g.:
my_archive.r00
my_archive.rar…and you right-click my_archive.r00 and select Power Archiver 2007 > Extract Here, you’ll get an error message stating that there was a CRC error, continue?
If you do this with the my_archive.rar file it extracts the archive contents to the current directory, as expected.
If you have a larger multi-part archive and try to extract from the *.r00 or *.r01 file then PA just crashes without giving the CRC error popup.
It seems to not be loading all parts of a multi-part archive during extraction unless you begin with the *.rar file.
-
This should be fixed in latest version:
http://www.powerarchiver.com/test/release10/powarc1010.exePlease let us know…
thanks!
-
I tested extracting from both the *.r00 and *.r01 file from a couple different multi-part archives and it worked ok. Before this was reproducible every time so this seems to be fixed. I’ll advise if I notice it again and give details. Nice job on the fix btw.
