drivenax.blogg.se

There's been some impedance mismatch on the communication with the person who has the OSX machine - so it is unresolved as yet.īut, if this theory holds, it would explain your situation: that WinRar and any Windows machine can open the file, but OSX cannot. So the theory is that bit 3 causes the problem. So I am using "bit 3" as a shorthand for all that.

Actually it's not as simple as just flipping one bit - the presence of the bit signals the presence of other metadata. The same zip contents produced without bit 3, allows the zip file to be opened. DotNetZip also has a way to produce a zipfile as it is streamed out, and it will also set bit-3 in the zip file if used in this way, although normally DotNetZip will produce a zipfile with bit-3 unset in it.įrom what we can tell, when bit 3 is set, the OSX zip reader (whatever it is - like I said I'm not familiar with OSX) chokes on the zip file. It was intended to support streaming generation of archives, in the way that SharpZipLib works. PKWare added bit 3 to the spec 17 years ago. At this point the most promising theory is that OSX does not like "bit 3" in the "general purpose bitfield" in the header of each zip entry.īit 3 is not new. One of the people using the library is having a problem that seems similar to what you are seeing. NET, unrelated to SharpZipLib.Ĭurrently on the user forums for DotNetZip, there's a discussion going on about zip files generated by DotNetZip that cannot be read on OSX. I've spent some time wading through the zip spec, and actually I wrote DotNetZip, which is a zip library for. I don't know for sure, because I am not very familiar with either SharpZipLib or OSX, but I still might have some useful insight for you. I wonder if it is needed to use zipStream.Write() in order to write directly to the stream?

I found the above code on the Internet, so I am not absolutely sure if the whole thing is correct. zip file created manually with the same files on Windows is extracted without any problems on Windows and Mac OS X. But as soon as I try to unzip my archive on Mac OS X, it only creates a. ZipStream.Write(buffer, 0, buffer.Length) Īll works well under Windows, when I open the file e.

ZipEntry entry = new ZipEntry(Path.GetFileName(pathname)) Using (var zipStream = new ZipOutputStream(outStream))īyte buffer = File.ReadAllBytes(pathname) Using (var outStream = new FileStream("Out2.zip", FileMode.Create)) I have an application which creates a zip file containing some JPEGs from a certain directory. Argh, today is the day of stupid problems and me being an idiot.