AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |
Back to Blog
Archive utility5/7/2023 The proper decompression behavior would be to continue to uncompress the stream until it returns that it's at its end, like unzip and other tools (and older Archive Utility) do it. Instead, it appears to stop uncompressing once it believes it has reached the "uncompressed size", even though the compressed zip stream keeps feeding data and hasn't reached its end, yet. Please don't punish all us by ignoring that old mistake by deciding to not working around it any more.Īctually, it appears that the decompression utility does not even first create the full 4GB file before shortening it afterwards. So please fix this issue in Archive Utility (or in ditto or whatever it uses beneath) instead of demanding that everyone "does it right", and thereby failing to uncompress backups people may have made with Apple's own tools in the past. How to enable Archive apps on Windows 11. In fact, it was, until this regression.įact is that this zip file was created on macOS High Sierra, using Finder's "Compress" command, so it's Apple's own tool that created this file, and since it also used to uncompress correctly, you can't blame anyone but Apple on this :) Sure, the zip64 format is _supposed_ to be used for such cases, but there are many zip files out there that aren't using that format, and they should still extract just fine, which is possible. The bug is that the new Archive Utility ignores that possibility and shortens the extracted file (which initially indeed extracts to the full 4GB in length, it appears) to the 32bit value it finds in the directory (which is 5). This is a fairly serious regression because it leads to zip files not uncompressing that uncompressed well before.Īnd it shouldn't matter that the zip file contains a file whose size is >32 bit, because all other common zip tools before and current can correctly uncompress it regardless. When uncompressing the same file on older macOS versions (I've tried High Sierra) or with command line tools such as "unzip", the result is correct. It should create a file of about 4 GB in size (4'294'967'301 bytes, which is 2^32+5), but it creates one of only 5 bytes. Replace filename.zip with the actual name of the zip file. Enter the command (s) in the steps below into your command line prompt (triple click the line, copy it, and paste it into your prompt). You can access it by typing 'Terminal' into Spotlight. zip file (gzipped version: ) that fails to uncompress correctly when opened by Archive Utility (e.g. It's likely that filename.zip is either not actually a.
0 Comments
Read More
Leave a Reply. |