Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

"... Zip archive data, at least v2.0 to extract" from file command.

5,768 views
Skip to first unread message

ANT...@zimage.com

unread,
Nov 16, 2007, 4:58:21 PM11/16/07
to
Greetings! I am having problems with a huge zip file, but Linux/Debian's
unzip command can't read it:

$ ls -all *.zip
-rwx------ 1 ant ant 4795524388 2007-11-16 13:14 potbs_st2_client.zip

$ unzip -v potbs_st2_client.zip
Archive: potbs_st2_client.zip
warning [potbs_st2_client.zip]: 500556947 extra bytes at beginning or
within zipfile
(attempting to process anyway)
error [potbs_st2_client.zip]: start of central directory not found;
zipfile corrupt.
(please check that you have transferred or created the zipfile in the
appropriate BINARY mode and that you have compiled UnZip properly)

$ file *.zip
potbs_st2_client.zip: Zip archive data, at least v2.0 to extract


What zip v2 command file (no GUI since this is done via SSH) can I use
to view, extract, and these files? I assume it is using the newer zip
compression format like in WinZip.

Thank you in advance. :)
--
"We are anthill men upon an anthill world." --Ray Bradbury
/\___/\
/ /\ /\ \ Phillip (Ant) @ http://antfarm.ma.cx (Personal Web Site)
| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net
\ _ / Please remove ANT if replying by e-mail.
( )

Bill Marcum

unread,
Nov 17, 2007, 2:38:01 AM11/17/07
to
["Followup-To:" header set to comp.os.linux.misc.]

On 2007-11-16, ANT...@zimage.com <ANT...@zimage.com> wrote:
> Greetings! I am having problems with a huge zip file, but Linux/Debian's
> unzip command can't read it:
>
> $ ls -all *.zip
> -rwx------ 1 ant ant 4795524388 2007-11-16 13:14 potbs_st2_client.zip
>
> $ unzip -v potbs_st2_client.zip
> Archive: potbs_st2_client.zip
> warning [potbs_st2_client.zip]: 500556947 extra bytes at beginning or
> within zipfile
> (attempting to process anyway)
> error [potbs_st2_client.zip]: start of central directory not found;
> zipfile corrupt.
> (please check that you have transferred or created the zipfile in the
> appropriate BINARY mode and that you have compiled UnZip properly)
>
> $ file *.zip
> potbs_st2_client.zip: Zip archive data, at least v2.0 to extract
>
>
> What zip v2 command file (no GUI since this is done via SSH) can I use
> to view, extract, and these files? I assume it is using the newer zip
> compression format like in WinZip.
>
> Thank you in advance. :)

If unzip thinks the file is corrupt, it won't extract.
Perhaps "wine winzip filename" or a newer version of info-zip? Or if you
have any control over the creation of the file, force it to use
older compression (info-zip or gzip for Windows should work.)
Ubuntu 7.10 has unzip version
UnZip 5.52 of 28 February 2005, by Ubuntu. Original by Info-ZIP.
but I don't know if that will extract your file.

jayjwa

unread,
Nov 17, 2007, 5:44:41 PM11/17/07
to
Bill Marcum <marcu...@bellsouth.net> writes:


> On 2007-11-16, ANT...@zimage.com <ANT...@zimage.com> wrote:
>> Greetings! I am having problems with a huge zip file, but Linux/Debian's
>> unzip command can't read it:
>>
>> $ ls -all *.zip
>> -rwx------ 1 ant ant 4795524388 2007-11-16 13:14 potbs_st2_client.zip
>>
>> $ unzip -v potbs_st2_client.zip
>> Archive: potbs_st2_client.zip
>> warning [potbs_st2_client.zip]: 500556947 extra bytes at beginning or
>> within zipfile
>> (attempting to process anyway)
>> error [potbs_st2_client.zip]: start of central directory not found;
>> zipfile corrupt.
>> (please check that you have transferred or created the zipfile in the
>> appropriate BINARY mode and that you have compiled UnZip properly)
>>
>> $ file *.zip
>> potbs_st2_client.zip: Zip archive data, at least v2.0 to extract
>>
>>
>> What zip v2 command file (no GUI since this is done via SSH) can I use
>> to view, extract, and these files? I assume it is using the newer zip
>> compression format like in WinZip.
>>
>> Thank you in advance. :)
>
> If unzip thinks the file is corrupt, it won't extract.
> Perhaps "wine winzip filename" or a newer version of info-zip?


Yes, you are correct. I've seen these beasts too. I got in with a
WinZip "trial" version, running under Wine. My version was a pay
version, but the trial was enough to do the 1 or 2 files I needed it
for (actually, you can reset the trial period counter in the registry,
but...). Hopefully someone will update InfoZip.

I know that's not a no-GUI answer, but I thought I'd mention this
since we are bound to see more of these in the linux world as Windows
users pass around zip files made in a format our tools can no longer
work with.


--
[** America, the police state **]
Whoooose! What's that noise? Why, it's US citizen's
rights, going down the toilet with Bush flushing.
http://www.wired.com/politics/security/news/2007/08/wiretap
http://www.hermes-press.com/police_state.htm

Ant

unread,
Nov 17, 2007, 11:12:25 PM11/17/07
to
On 11/17/2007 2:44 PM PT, jayjwa typed:

>>> Greetings! I am having problems with a huge zip file, but Linux/Debian's
>>> unzip command can't read it:
>>>
>>> $ ls -all *.zip
>>> -rwx------ 1 ant ant 4795524388 2007-11-16 13:14 potbs_st2_client.zip
>>>
>>> $ unzip -v potbs_st2_client.zip
>>> Archive: potbs_st2_client.zip
>>> warning [potbs_st2_client.zip]: 500556947 extra bytes at beginning or
>>> within zipfile
>>> (attempting to process anyway)
>>> error [potbs_st2_client.zip]: start of central directory not found;
>>> zipfile corrupt.
>>> (please check that you have transferred or created the zipfile in the
>>> appropriate BINARY mode and that you have compiled UnZip properly)
>>>
>>> $ file *.zip
>>> potbs_st2_client.zip: Zip archive data, at least v2.0 to extract
>>>
>>> What zip v2 command file (no GUI since this is done via SSH) can I use
>>> to view, extract, and these files? I assume it is using the newer zip
>>> compression format like in WinZip.
>>>
>>> Thank you in advance. :)
>> If unzip thinks the file is corrupt, it won't extract.
>> Perhaps "wine winzip filename" or a newer version of info-zip?

I noticed old registered WinZip v8.1 had the same problem. It said
something about the file being over 4 GB (which is true). I tried the
latest WinRAR worked though! So the zip file is fine, but unzip command
and older WinZip versions can't handle it. I also tried it in Windows XP
Pro. SP2's with its built in zip component (same problem).


> Yes, you are correct. I've seen these beasts too. I got in with a
> WinZip "trial" version, running under Wine. My version was a pay
> version, but the trial was enough to do the 1 or 2 files I needed it
> for (actually, you can reset the trial period counter in the registry,
> but...). Hopefully someone will update InfoZip.
>
> I know that's not a no-GUI answer, but I thought I'd mention this
> since we are bound to see more of these in the linux world as Windows
> users pass around zip files made in a format our tools can no longer
> work with.

Yeah, this stinks. Someone needs to update zip/unzip commands! :(
--
"For an ant to have wings would be his (her) undoing." --Iranian
/\___/\
/ /\ /\ \ Phillip/Ant @ http://antfarm.ma.cx (Personal Web Site)


| |o o| | Ant's Quality Foraged Links (AQFL): http://aqfl.net

\ _ / Remove ANT from e-mail address: phi...@earthlink.netANT
( ) or ANT...@zimage.com
Ant is currently not listening to any songs on his home computer.

John Thompson

unread,
Nov 18, 2007, 7:34:35 PM11/18/07
to
On 2007-11-17, Bill Marcum <marcu...@bellsouth.net> wrote:

> If unzip thinks the file is corrupt, it won't extract.
> Perhaps "wine winzip filename" or a newer version of info-zip?

Perhaps try "zip -F zipfile.zip"

-F Fix the zip archive. This option can be used if
some portions of the archive are missing. It is not
guaranteed to work, so you MUST make a backup of
the original archive first.

When doubled as in -FF the compressed sizes given
inside the damaged archive are not trusted and zip
scans for special signatures to identify the limits
between the archive members. The single -F is more
reliable if the archive is not too much damaged,
for example if it has only been truncated, so try
this option first.

Neither option will recover archives that have been
incorrectly transferred in ascii mode instead of
binary. After the repair, the -t option of unzip
may show that some files have a bad CRC. Such files
cannot be recovered; you can remove them from the
archive using the -d option of zip.


--

John (jo...@os2.dhs.org)

0 new messages