PA 2010 11.60.26 Creates invalid ZIP with large files
-
Tested it with a virtual image disk image file ( file size: 5.216.731.136 bytes ) creates archive with a size of (1.868.354.280 bytes….and with 0 files…
I will send you the reg part…
no need to send the reg, i think we managed to reproduce it… waiting for engineers to check it out.
-
are you using virtual pc or vmware or is it native XP system?
-
are you using virtual pc or vmware or is it native XP system?
Running native XP SP3 32 Bit on both systems……( but with VmWare workstation v6.5.3 build 185404 installed on both systems but with no running instance: thus no active shared folders between host en guest OS )
-
Running native XP SP3 32 Bit on both systems……( but with VmWare workstation v6.5.3 build 185404 installed on both systems but with no running instance: thus no active shared folders between host en guest OS )
Just did a test when running XP in Safe mode……same error…
-
we believe this has been fixed… will have version to test tomorrow.
thanks
-
FYI, files created were created properly, problem was with reading files, where our relativly new autodetection routine did not recognize some files as zips (in this example exactly), even if they were.
-
FYI, files created were created properly, problem was with reading files, where our relativly new autodetection routine did not recognize some files as zips (in this example exactly), even if they were.
But that doesn’t explain why the standard Windows XP UNZIP functionalitiy complains about an invalid/corrupt ZIP file( see first message )… does it ?
-
not sure that windows xp supports large zips properly, i believe it was added in Vista.
Here is the test release, please check it out and let us know:
http://www.powerarchiver.com/test/release10/powarc116028.exethanks!
-
Wow. You guys are quick. :)
-
not sure that windows xp supports large zips properly, i believe it was added in Vista.
Here is the test release, please check it out and let us know:
http://www.powerarchiver.com/test/release10/powarc116028.exethanks!
It FIXED the problem. Tested it with the BAK and VmWare image and both were now OK.
Great…BIG thanks for the quick support….and fix
:):)





