Unzip file error 1

How To Fix Mac Unzip Error 1- Operation Not Permitted

More often than not, there is a need to compress large files into zip format for easy and fast transfer. Zip is a popular archive file format that enables data compression without losing any part of the data, therefore it is widely used by both Mac and Windows users. However, it is not an all positive experience for Mac users when you try to expand zip file but encounter an error message that says Unable to expand filename.zip (Error 1 – Operation not permitted.), with the Mac Archive Utility dialogue shown as below:

Unable to expand zip file can be disheartening and discouraging, but we would guide you on how to fix Mac unzip error 1 in this article, let’s dive into it.

1 How to Fix Mac Archive Utility Unzip Error 1

In this section, we will take you through the different ways and processes you can apply to fix this error.

1 Unzip File in Terminal

Normally, toВ decompressВ aВ zipped fileВ on Mac, you simply need to double-click the zip file, and it will automatically unzip. But if this is not the case, try unzipping your file from Terminal. Every Mac OS has a Terminal application that uses a command promptВ to control the Mac. To successfully unzip your file using Terminal, follow these steps:

Step 1: Open and run Terminal. Do one of the following on your Mac:

Hold the Command and Space keyВ to open Spotlight, type «Terminal»В into the search box, then click Terminal.

Launch Finder, go to Applications > Utilities folder, then double click Terminal.

Step 2: Input the command Unzip filename.zip into Terminal and click on Enter.

Step 3: Your file will start unzipping.В

Step 4 (Optional): If you get a message like «No such directory Error» or «cannot find», you might eventually have to manually use the «cd” command to changeВ directory and unzip your filesВ there. For example, type “cd . /desktop” in Terminal to change the directory to Desktop.

If the above method doesn’t get the job done, then try out our next fix.

2 Try Zipeg Application

If your Zip file is too large, Mac Archive Utility may also show Error 1 operation not permitted, so our next bet to resolve the issue is using a different program to help unzip your file. Most Mac users find Zipeg as a top solution for them. As a free utility tool and an open-source program for both Windows and Mac users, Zipeg can be used to compress and extract archive files in zip, 7z, RarВ and Tar formats, etc. В ItВ can be used in resolving the Error 1 archive issue for Mac users inВ theВ belowВ steps.

Firstly, you need to download the Zipeg application.

After installing Zipeg, open the application to add your zip file, or you can alternatively drag and drop the file into the Zipeg icon.

Zipeg will display all the contents ofВ your archive file, select the content you want to extract from the list shown.

Choose a destination folder on your computer to extract to.

Finally, start extracting by clicking «Extract.» Once it is done, your files will be moved to your desired destination folder.

3 Use Stuffit Expander to Expand Zip Files

There might be a problem with your permissions when opening a zip file normally. This can be resolved by using other Unzip Software on the App Store that can help unzip your files. You can get and try Stuffit Expander from the Mac App store as it can be used for this purpose. Many users whoВ were unable to fix Mac unzip Error 1 withВ the first two methods were able to use this tool in resolving the problem. HereВ are the steps to follow:

1. Get Stuffit Expander from the Mac App Store.

2. Open the applicationВ from Spotlight,В then locate the zip file you wish to unzip and open it.

3. Choose aВ new folder you wish to extract the compressed file to.

You are done! The file will be unzipped.

2 How to Recover Deleted/Lost Zip Files on Mac due to Error

If you have deleted a zip file by accident or the file is lost due to zip file error 1, don’t worry as you still can get your files back. Your best bet is iMyFone AnyRecover for Mac, which is a home/office data recovery software.

AnyRecover for Mac is perfectly compatible with all the latest Mac operating systems including macOS 10.15 Catalina, 10.14 Mojave and 10.13 High Sierra. This software willВ completelyВ scan your hard drive, recycle bin or any other locations for deleted files, then allow you to preview before recovery. Besides,В it makes use of a unique data recovery algorithm to ensure a high recovery rate.

Key Features of iMyFone AnyRecover for Mac: В В В В

Quick and convenient recovery of any file type like videos, audios, photos, PDF documents, and more.

AnyRecover supports all storage devices like internal hard drive, memory card, USB flash drive, digital cameras, external HDD, etc.

No matter the scenario of data loss, AnyRecover can recover your files – be it emptied trash, virus attack, system crash, lost partition, etc.

100% safe to use, AnyRecover does not overwrite or distort your data during the process of recovery.

How to Recover Lost Zip FilesВ using AnyRecover

Step 1: Install and launch iMyFone AnyRecover on your Mac,В and select a locationВ where your zipped file was stored before it was lost.

Step 2:Now, click on the Start button, and AnyRecover will start a scanning process.

Step 3:Once AnyRecover finishes the scanning process, you will see a list of recoverable files. From the list, preview the zip file that you want to recover, and then click on the Recover button.

It is as simple as that. You don’t have to fidget over lost files anymore.

3 FAQ: Know More about Mac Archive Utility

Still not clear about some conceptsВ on Mac Archive Utility? Find more answers to questions frequently asked by users.

1. What is Archive Utility?

Archive Utility is a built-in small App for Apple macOS that is used to create and decompress zip files.

2. How do I Zip and Unzip files with Archive

To expand files from a zip archive, normally you don’t need to manually open the program, just double click the .zip file on your Mac, the file will be decompressed automatically by Archive Utility.

To zip files or photos, Ctrl-click or right-click all the files you want to compress, select the CompressВ option from the pop-up menu. The files will be automatically compressed in a .zip extension and will be seen in the same folder location as the original files.

3. What causes Archive Utility Error 1 on Mac?

Different factors can be responsible for Archive utility error 1. here are the most common amongst them.

Network connection: Instability of your network while extracting the zip file can cause the Error to show up. Also, if you close your browser before the file has finished downloading, it can result in this error as well.

Very Large file: Trying to compress very large files can result inВ zip file Error 1В becauseВ the necessaary resources to support the file being unzipped are not available.

No permissions: If the “Sharing & permission” section on Mac is not set to read & write or read-only, it causes the unzip Error 1.

As a macOS user, zipping your files can be easy for transferring files fast, butВ it comes with challenges.В The most common being Archive utility Error 1. There are several methodsВ to handle this error, as we have mentioned in this article. But in a case where you lose the zip file, iMyFone AnyRecoverВ for MacВ is the best recovery software to help you recover that lost fileВ from hard drive, memory card or other storage devices, there isВ always aВ peace of mind with AnyRecover.В


Ошибка при распаковке файла

Я получаю следующую ошибку при распаковке файла

Я считаю, что этот файл не поврежден или является частью многоархивированного файла, так как с помощью утилиты архивирования я смог его распаковать. Я пытался переименовать его, .zip но не получилось.

Выход type file user_file_batch1.csv.zip был

Ваш файл имеет .zip имя, но не в формате zip. Переименование файла не меняет его содержимого и, в частности, не превращает его волшебным образом в другой формат.

(В противном случае та же ошибка может произойти с неполным zip-файлом — но поскольку эта утилита архивации работала, это не так.)

Запустите, file user_file_batch1.csv.zip чтобы увидеть, что это за тип файла. Вероятно, это какой-то другой тип архива, который понимает утилита архивирования.

user_file_batch1.csv.zip: uuencoded или xxencoded текст

Запустите следующую команду:

Это создает файл, имя которого указано в user_file_batch1.csv.zip . Если вы хотите выбрать другое имя выходного файла:

Выходной файл на этом этапе может сам по себе быть архивом. (Возможно, это на самом деле почтовый индекс.) Запустите file утилиту еще раз для этого файла, чтобы увидеть, что это такое. Если вы выберете автоматическое имя файла, оно может дать подсказку.

У меня была похожая проблема при выполнении unzip archive.zip , давая мне

предупреждение archive.zip [archive.zip]: . лишние байты в начале или внутри zipfile
(все равно пытаясь обработать)
error [archive.zip]: начало центрального каталога не найдено;
Zip-файл поврежден.
(убедитесь, что вы перенесли или создали zip-файл в
соответствующем режиме BINARY и правильно скомпилировали UnZip)

Делать file archive.zip дал мне

Использование 7z e archive.zip сработало.

У меня была такая же проблема с распаковкой.

Тогда я попытался извлечь его с помощью 7z и банку без какой-либо удачи. Позже выяснилось, что это была тихая старая версия p7zip.

Я установил новый из источника, и это решило проблему. Простой:


zip files don’t unzip with standard os x archiver — (error 1 — operation not permitted) #249


With all other programs I tested they unzip just fine (Safari, Terminal unzip, Keka).
Any idea what’s the issue?

The text was updated successfully, but these errors were encountered:

I’ve encountered this issue as well, but have not managed to find a fix. The resulting zip can be opened in any extract tool except for Archive Utility. Unfortunately for me, that’s what most of my customers will be using.

Perhaps Grandt/PHPZip#4 could provide some helpful information?

Okay I investigated my case more and confirmed that the issue is actually #240. I resolved by making sure each filename is unique by appending an identifier to the filename.

@bmulholland thanks for the pointer. That helped me a lot!

I’m encountering this as well. Checked and it’s not a case of #240.

Same issue for me . and i don’t have duplicate filenames

I’m also running into this exact issue. I get the same message in system.log that @mrkamel is seeing

Hi there.. same thing here.. i have the (error 1 — operation not permitted) .. found the solution?

and dont have duplicated files.. is something related with permission of files that is on server and include in zip fila?

UPDATED: I made some chages to guarantee that does not have duplicated. but i just could work removing send_file or send_data to return the zip, i’m storing that in a folder and giving to the user a link to be downloaded after.


Unzip file error 1

list, test and extract compressed files in a ZIP archive


unzip [ ] file[.zip] [file(s) . ] [ xfile(s) . ] [ exdir ]

unzip will list, test, or extract files from a ZIP archive, commonly found on MS-DOS systems. The default behavior (with no options) is to extract into the current directory (and subdirectories below it) all files from the specified ZIP archive. A companion program, zip , creates ZIP archives; both programs are compatible with archives created by PKWARE’s PKZIP and PKUNZIP for MS-DOS, but in many cases the program options or default behaviors differ.

If the archive contains Unix or Win32 symbolic links, these will be displayed (a 0x80000 in the non-MSDOS external file attributes field with both Unix/Linux/MacOS and PTC MKS Toolkit) or restored to NTFS volumes to point to the same names (existing or not existing) as they were in the source file system. Where the source is on an NTFS volume and target does not exist, a file symbolic link will be created.

READ  Topfield tf7700hsci прошивка для триколор

zipinfo mode. If the first option on the command line is , the remaining options are taken to be zipinfo options. See the appropriate manual page for a description of these options.

[OS/2, Unix (but not PTC MKS Toolkit) DLL] print extended help for the DLL’s programming interface (API).

extract files to stdout/screen («CRT»). This option is similar to the option except that the name of each file is printed as it is extracted, the option is allowed, and ASCII-EBCDIC conversion is automatically performed if appropriate. This option is not listed in the unzip usage screen.

freshen existing files, i.e., extract only those files that already exist on disk and that are newer than the disk copies. By default unzip queries before overwriting, but the option may be used to suppress the queries. Note that under many operating systems, the TZ (timezone) environment variable must be set correctly in order for and to work properly (under Unix the variable is usually set automatically). PTC MKS Toolkit will fall back to the system timezone in the registry if TZ is not set. The reasons for this are somewhat subtle but have to do with the differences between DOS-format file times (always local time) and Unix-format times (always in GMT/UTC) and the necessity to compare the two. A typical TZ value is «PST8PDT» (US Pacific time with automatic adjustment for Daylight Savings Time or «summer time»).

list archive files (short format). The names, uncompressed file sizes and modification dates and times of the specified files are printed, along with totals for all files specified. If UnZip was compiled with OS2_EAS defined, the option also lists columns for the sizes of stored OS/2 extended attributes (EAs) and OS/2 access control lists (ACLs). In addition, the zipfile comment and individual file comments (if any) are displayed. If a file was archived from a single-case file system (for example, the old MS-DOS FAT file system) and the option was given, the filename is converted to lowercase and is prefixed with a caret (^).

list zipfile information in verbose, multi-page format.

extract files to pipe (stdout). Nothing but the file data is sent to stdout, and the files are always extracted in binary format, just as they are stored (no conversions).

test archive files. This option extracts each specified file in memory and compares the CRC (cyclic redundancy check, an enhanced checksum) of the expanded file with the original file’s stored CRC value.

[most OSes] set the timestamp on the archive(s) to that of the newest file in each one. This corresponds to zip ‘s option except that it can be used on wildcard zipfiles (e.g., «unzip -T \*.zip») and is much faster.

update existing files and create new ones if needed. This option performs the same function as the option, extracting (with query) files that are newer than those with the same name on disk, and in addition it extracts those files that do not already exist on disk. See above for information on setting the timezone properly.

list archive files (verbose format) or show diagnostic version info. This option has evolved and now behaves as both an option and a modifier. As an option it has two purposes: when a zipfile is specified with no other options, lists archive files verbosely, adding to the basic info the compression method, compressed size, compression ratio and 32-bit CRC. In contrast to most of the competing utilities, unzip removes the 12 additional header bytes of encrypted entries from the compressed size numbers. Therefore, compressed size and compression ratio figures are independent of the entry’s encryption status and show the correct compression performance. (The complete size of the encrypted compressed data stream for zipfile entries is reported by the more verbose zipinfo reports, see the separate manual.) When no zipfile is specified (that is, the complete command is simply «unzip -v»), a diagnostic screen is printed. In addition to the normal header with release date and version, unzip lists the home Info-ZIP ftp site and where to find a list of other ftp and non-ftp sites; the target operating system for which it was compiled, as well as (possibly) the hardware on which it was compiled, the compiler and version used, and the compilation date; any special compilation options that might affect the program’s operation (see also DECRYPTION below); and any options stored in environment variables that might do the same (see ENVIRONMENT below). As a modifier it works in conjunction with other options (e.g., ) to produce more verbose or debugging output; this is not yet fully implemented but will be in future releases.

display only the archive comment.

convert text files. Ordinarily all files are extracted exactly as they are stored (as «binary» files). The option causes files identified by zip as text files (those with the `t’ label in zipinfo listings, rather than `b’) to be automatically extracted as such, converting line endings, end-of-file characters and the character set itself as necessary. (For example, Unix files use line feeds (LFs) for end-of-line (EOL) and have no end-of-file (EOF) marker; Macintoshes use carriage returns (CRs) for EOLs; and most PC operating systems use CR+LF for EOLs and control-Z for EOF. In addition, IBM mainframes and the Michigan Terminal System use EBCDIC rather than the more common ASCII character set, and NT supports Unicode.) Note that zip ‘s identification of text files is by no means perfect; some «text» files may actually be binary and vice versa. unzip therefore prints «[text]» or «[binary]» as a visual check for each file it extracts when using the option. The option forces all files to be extracted as text, regardless of the supposed file type. On VMS, see also .

treat all files as binary (no text conversions). This is a shortcut for .

[when compiled with UNIXBACKUP defined (as it is with PTC MKS Toolkit)] save a backup copy of each overwritten file. The backup file is gets the name of the target file with a tilde and optionally a unique sequence number (up to 5 digits) appended. The sequence number is applied whenever another file with the original name plus tilde already exists. When used together with the «overwrite all» option , numbered backup files are never created. In this case, all backup files are named as the original file with an appended tilde, existing backup files are deleted without notice. This feature works similarly to the default behavior of emacs in many locations.

Example: the old copy of «foo» is renamed to «foo

Warning: Users should be aware that the option does not prevent loss of existing data under all circumstances. For example, when unzip is run in overwrite-all mode, an existing «foo

» file is deleted before unzip attempts to rename «foo» to «foo

». When this rename attempt fails (because of a file locks, insufficient privileges, or . ), the extraction of «foo

» gets cancelled, but the old backup file is already lost. A similar scenario takes place when the sequence number range for numbered backup files gets exhausted (99999, or 65535 for 16-bit systems). In this case, the backup file with the maximum sequence number is deleted and replaced by the new backup version without notice.

use case-insensitive matching for the selection of archive entries from the command-line list of extract selection patterns. unzip ‘s philosophy is «you get what you ask for» (this is also responsible for the / change; see the relevant options below). Because some file systems are fully case-sensitive (notably those under the Unix operating system) and because both ZIP archives and unzip itself are portable across platforms, ‘s default behavior is to match both wildcard and literal filenames case-sensitively. That is, specifying «makefile» on the command line will only match «makefile» in the archive, not «Makefile» or «MAKEFILE» (and similarly for wildcard specifications). Since this does not correspond to the behavior of many other operating/file systems (for example, OS/2 HPFS, which preserves mixed case but is not sensitive to it), the option may be used to force all filename matches to be case-insensitive. In the example above, all three files would then match «makefile» (or «make*», or similar). The option affects file specs in both the normal file list and the excluded-file list (xlist).

Please note that the option does neither affect the search for the zipfile(s) nor the matching of archive entries to existing files on the extraction path. On a case-sensitive file system, unzip will never try to overwrite a file «FOO» when extracting an entry «foo»!

skip restoration of timestamps for extracted items. Normally, unzip tries to restore all meta-information for extracted items that are supplied in the Zip archive (and do not require privileges or impose a security risk). By specifying , unzip is told to suppress restoration of timestamps for directories explicitly created from Zip archive entries. This option only applies to ports that support setting timestamps for directories (currently ATheOS, BeOS, MacOS, OS/2, Unix, VMS, Win32, PTC MKS Toolkit, for other unzip ports, has no effect). The duplicated option forces suppression of timestamp restoration for all extracted entries (files and directories). This option results in setting the timestamps for all extracted entries to the current time.

On VMS, the default setting for this option is for consistency with the behaviour of BACKUP: file timestamps are restored, timestamps of extracted directories are left at the current time. To enable restoration of directory timestamps, the negated option should be specified. On VMS, the option disables timestamp restoration for all extracted Zip archive items. (Here, a single on the command line combines with the default to do what an explicit does on other systems.)

[MacOS only] display contents of MacOS extra field during restore operation

[non-Acorn systems supporting long filenames with embedded commas, and only if compiled with ACORN_FTYPE_NFS defined (which PTC MKS Toolkit does not)] translate filetype information from ACORN RISC OS extra field blocks into a NFS filetype extension and append it to the names of the extracted files. (When the stored filename appears to already have an appended NFS filetype extension, it is replaced by the info from the extra field.

[MacOS only] ignore filenames stored in MacOS extra fields. Instead, the most compatible filename stored in the generic part of the entry’s header is used.

junk paths. The archive’s directory structure is not recreated; all files are deposited in the extraction directory (by default, the current one).

[MacOS only] ignore MacOS extra fields. All Macintosh specific info is skipped. Data-fork and resource-fork are restored as separate files.

[AtheOS, BeOS, Unix (but not PTC MKS Toolkit) only] retain SUID/SGID/Tacky file attributes. Without this flag, these attribute bits are cleared for security reasons.

convert to lowercase any filename originating on an uppercase-only operating system or file system. (This was unzip ‘s default behavior in releases prior to 5.11; the new default behavior is identical to the old behavior with the option, which is now obsolete and will be removed in a future release.) Depending on the archiver, files archived under single-case file systems (VMS, old MS-DOS FAT, etc.) may be stored as all-uppercase names; this can be ugly or inconvenient when extracting to a case-preserving file system such as OS/2 HPFS or a case-sensitive one such as under Unix. By default unzip lists and extracts such filenames exactly as they’re stored (excepting truncation, conversion of unsupported characters, etc.); this option causes the names of all files from certain systems to be converted to lowercase. The option forces conversion of every filename to lowercase, regardless of the originating file system.

pipe all output through an internal pager similar to the Unix more command. At the end of a screenful of output, unzip pauses with a «—More—» prompt; the next screenful may be viewed by pressing the Enter (Return) key or the space bar. unzip can be terminated by pressing the «q» key and, on some systems, the Enter/Return key. Unlike Unix more , there is no forward-searching or editing capability. Also, unzip doesn’t notice if long lines wrap at the edge of the screen, effectively resulting in the printing of two or more lines and the likelihood that some text will scroll off the top of the screen before being viewed. On some systems the number of available lines on the screen is not detected, in which case unzip assumes the height is 24 lines.

READ  Sql error log path

never overwrite existing files. If a file already exists, skip the extraction of that file without prompting. By default unzip queries before extracting any file that already exists; the user may choose to overwrite only the current file, overwrite all files, skip extraction of the current file, skip extraction of all existing files, or rename the current file.

[Amiga] extract file comments as Amiga filenotes. File comments are created with the option of zip , or with the option of the Amiga port of zip , which stores filenotes as comments.

overwrite existing files without prompting. This is a dangerous option, so use it with care. (It is often used with , however, and is the only way to overwrite directory EAs under OS/2.)

use password to decrypt encrypted zipfile entries (if any). THIS IS INSECURE! Many multi-user operating systems (including PTC MKS Toolkit on Windows) provide ways for any user to see the current command line of any other user; even on stand-alone systems there is always the threat of over-the-shoulder peeking. Storing the plaintext password as part of a command line in an automated script is even worse. Whenever possible, use the non-echoing, interactive prompt to enter passwords. (And where security is truly important, use strong encryption such as Pretty Good Privacy instead of the relatively weak encryption provided by standard zipfile utilities.)

perform operations quietly ( = even quieter). Ordinarily prints the names of the files it’s extracting or testing, the extraction methods, any file or zipfile comments that may be stored in the archive, and possibly a summary when finished with each archive. The options suppress the printing of some or all of these messages.

[OS/2, NT, MS-DOS, PTC MKS Toolkit] convert spaces in filenames to underscores. Since all PC operating systems allow spaces in filenames, unzip by default extracts filenames with spaces intact (e.g., «EA DATA. SF»). This can be awkward, however, since MS-DOS in particular does not gracefully support spaces in filenames. Conversion of spaces to underscores can eliminate the awkwardness in some cases.

[VMS] convert text files ( , ) into Stream_LF record format, instead of the text-file default, variable-length record format. (Stream_LF is the default record format of VMS unzip. It is applied unless conversion ( , and/or , ) is requested or a VMS-specific entry is processed.)

[UNICODE_SUPPORT only] modify or disable UTF-8 handling. When UNICODE_SUPPORT is available (as it is with PTC MKS Toolkit), the option forces unzip to escape all non-ASCII characters from UTF-8 coded filenames as «#Uxxxx» (for UCS-2 characters, or «#Lxxxxxx» for unicode codepoints needing 3 octets). This option is mainly provided for debugging purpose when the fairly new UTF-8 support is suspected to mangle up extracted filenames.

The option allows to entirely disable the recognition of UTF-8 encoded filenames. The handling of filename codings within unzip falls back to the behaviour of previous versions.

[old, obsolete usage] leave filenames uppercase if created under MS-DOS, VMS, etc. See above.

retain (VMS) file version numbers. VMS files can be stored with a version number, in the format file.ext;##. By default the «;##» version numbers are stripped, but this option allows them to be retained. (On file systems that limit filenames to particularly short lengths, the version numbers may be truncated or stripped regardless of this option.)

[only when WILD_STOP_AT_DIR compile-time option enabled (which is not enabled for PTC MKS Toolkit)] modifies the pattern matching routine so that both `?’ (single-char wildcard) and `*’ (multi-char wildcard) do not match the directory separator character `/’. (The two-character sequence «**» acts as a multi-char wildcard that includes the directory separator in its matched characters.) Examples:

This modified behaviour is equivalent to the pattern matching style used by the shells of some of UnZip ‘s supported target OSs (one example is Acorn RISC OS). This option may not be available on systems where the Zip archive’s internal directory separator character `/’ is allowed as regular character in native operating system filenames. (Currently, UnZip uses the same pattern matching rules for both wildcard zipfile specifications and zip entry selection patterns in most ports. For systems allowing `/’ as regular filename character, the option would not work as expected on a wildcard zipfile specification.)

[VMS, Unix, OS/2, NT, Tandem, PTC MKS Toolkit] restore owner/protection info (UICs and ACL entries) under VMS, or user and group info (UID/GID) under Unix, or access control lists (ACLs) under certain network-enabled versions of OS/2 (Warp Server with IBM LAN Server/Requester 3.0 to 5.0; Warp Connect with IBM Peer 1.0), or security ACLs under Windows NT. In most cases this will require special system privileges, and doubling the option ( ) under NT instructs unzip to use privileges for extraction; but under Unix, for example, a user who belongs to several groups can restore files owned by any of those groups, as long as the user IDs match his or her own. Note that ordinary file attributes are always restored—this option applies only to optional, extra ownership info available on some operating systems. [NT’s access control lists do not appear to be especially compatible with OS/2’s, so no attempt is made at cross-platform portability of access privileges. It is not clear under what conditions this would ever be useful anyway.]

PTC MKS Toolkit is capable of restoring ACLs but will ignore the Unix mode bits and owner and group information. i.e. it behaves more like a Win32 port than a Unix port for the option.

[VMS] treat archived file name endings of «.nnn» (where «nnn» is a decimal number) as if they were VMS version numbers («;nnn»). (The default is to treat them as file types.) Example:

[MS-DOS, OS/2, NT, PTC MKS Toolkit] restore the volume label if the extraction medium is removable (e.g., a diskette). Doubling the option ( ) allows fixed media (hard disks) to be labelled as well. By default, volume labels are ignored.

[all but Acorn, VM/CMS, MVS, Tandem] allows to extract archive members into locations outside of the current « extraction root folder». For security reasons, unzip normally removes «parent dir» path components («../») from the names of extracted file. This safety feature (new for version 5.50) prevents unzip from accidentally writing files to «sensitive» areas outside the active extraction folder tree head. The option lets unzip switch back to its previous, more liberal behaviour, to allow exact extraction of (older) archives that used «../» components to create multiple directory trees at the level of the current extraction folder. This option does not enable writing explicitly to the root directory («/»). To achieve this, it is necessary to set the extraction target folder to root (e.g. / ). However, when the option is specified, it is still possible to implicitly write to the root directory by specifying enough «../» path components within the zip archive. Use this option with extreme caution.

[Unix (but not PTC MKS Toolkit) only] allow control characters in names of extracted ZIP archive entries. On Unix, a file name may contain any (8-bit) character code with the two exception ‘/’ (directory delimiter) and NUL (0x00, the C string termination indicator), unless the specific file system has more restrictive conventions. Generally, this allows to embed ASCII control characters (or even sophisticated control sequences) in file names, at least on ‘native’ Unix file systems. However, it may be highly suspicious to make use of this Unix «feature». Embedded control characters in file names might have nasty side effects when displayed on screen by some listing code without sufficient filtering. And, for ordinary users, it may be difficult to handle such file names (e.g. when trying to specify it for open, copy, move, or delete operations). Therefore, unzip applies a filter by default that removes potentially dangerous control characters from the extracted file names. The option allows to override this filter in the rare case that embedded filename control characters are to be intentionally restored.

[VMS] force unconditionally conversion of file names to ODS2-compatible names. The default is to exploit the destination file system, preserving case and extended file name characters on an ODS5 destination file system; and applying the ODS2-compatibility file name filtering on an ODS2 destination file system.

unzip ‘s default behavior may be modified via options placed in an environment variable. This can be done with any option, but it is probably most useful with the , , , , , or modifiers: make unzip auto-convert text files by default, make it convert filenames from uppercase systems to lowercase, make it match names case-insensitively, make it quieter, or make it always overwrite or never overwrite files as it extracts them. For example, to make unzip act as quietly as possible, only reporting errors, one would use one of the following commands:

Unix (and PTC MKS Toolkit) Bourne shell:

Unix (and PTC MKS Toolkit) C shell:

VMS (quotes for lowercase):

Environment options are, in effect, considered to be just like any other command-line options, except that they are effectively the first options on the command line. To override an environment option, one may use the «minus operator» to remove it. For instance, to override one of the quiet-flags in the example above, use the command

The first hyphen is the normal switch character, and the second is a minus sign, acting on the option. Thus the effect here is to cancel one quantum of quietness. To cancel both quiet flags, two (or more) minuses may be used:

(the two are equivalent). This may seem awkward or confusing, but it is reasonably intuitive: just ignore the first hyphen and go from there. It is also consistent with the behavior of Unix nice .

As suggested by the examples above, the default variable names are UNZIP_OPTS for VMS (where the symbol used to install unzip as a foreign command would otherwise be confused with the environment variable), and UNZIP for all other operating systems. For compatibility with zip , UNZIPOPT is also accepted (don’t ask). If both UNZIP and UNZIPOPT are defined, however, UNZIP takes precedence. unzip ‘s diagnostic option ( with no zipfile name) can be used to check the values of all four possible unzip and zipinfo environment variables.

The timezone variable ( TZ ) should be set according to the local timezone in order for the and to operate correctly. See the description of above for details. This variable may also be necessary to get timestamps of extracted files to be set correctly. The WIN32 (8.1/2012R2/2016/2019/2022 and the PTC MKS Toolkit) port of unzip gets the timezone configuration from the registry, assuming it is correctly set in the Control Panel. The TZ variable is ignored for WIN32 but will override teh registry for PTC MKS Toolkit.

TK_ARCHIVE_CHARSET will instruct unzip how to interpret file names and commants in an archive. Settings are:

The value must be one of ASCII_ANSI , ASCII_OEM , or UTF-8 (or their equivalents) as described in the File Character Formats section of the unicode reference page.

Setting TK_ARCHIVE_CHARSET to ASCII_ANSI or ASCII_OEM is somewhat like to the LANG environment variable on UNIX in that it tailors the interpretation of the character set in use for file names and comments inside the zip archive.

When this variable is unset or it is set to a value other than those listed earlier, the default ANSI character set is used.

Encrypted archives are fully supported by Info-ZIP software, but due to United States export restrictions, de-/encryption support might be disabled in your compiled binary. However, since spring 2000, US export restrictions have been liberated, and our source archives do now include full crypt code. In case you need binary distributions with crypt support enabled, see the file «WHERE» in any Info-ZIP source or binary distribution for locations both inside and outside the US.

Some compiled versions of unzip may not support decryption (The PTC MKS Toolkit version is compiled with decryption enabled). To check a version for crypt support, either attempt to test or extract an encrypted archive, or else check unzip ‘s diagnostic screen (see the option above) for «[decryption]» as one of the special compilation options.

As noted above, the option may be used to supply a password on the command line, but at a cost in security. The preferred decryption method is simply to extract normally; if a zipfile member is encrypted, unzip will prompt for the password without echoing what is typed. unzip continues to use the same password as long as it appears to be valid, by testing a 12-byte header on each file. The correct password will always check out against the header, but there is a 1-in-256 chance that an incorrect password will as well. (This is a security feature of the PKWARE zipfile format; it helps prevent brute-force attacks that might otherwise gain a large speed advantage by testing only the header.) In the case that an incorrect password is given but it passes the header test anyway, either an incorrect CRC will be generated for the extracted data or else unzip will fail during the extraction because the «decrypted» bytes do not constitute a valid compressed data stream.

READ  Panasonic tx lr32xm5a прошивка

If the first password fails the header check on some file, unzip will prompt for another password, and so on until all files are extracted. If a password is not known, entering a null password (that is, just a carriage return or «Enter») is taken as a signal to skip all further prompting. Only unencrypted files in the archive(s) will thereafter be extracted. (In fact, that’s not quite true; older versions of zip and zipcloak allowed null passwords, so unzip checks each encrypted file to see if the null password works. This may result in «false positives» and extraction errors, as noted above.)

Archives encrypted with 8-bit passwords (for example, passwords with accented European characters) may not be portable across systems and/or other archivers. This problem stems from the use of multiple encoding methods for such characters, including Latin-1 (ISO 8859-1) and OEM code page 850. DOS PKZIP 2.04g uses the OEM code page; Windows PKZIP 2.50 uses Latin-1 (and is therefore incompatible with DOS PKZIP); Info-ZIP uses the OEM code page on DOS, OS/2 and Win3.x ports but ISO coding (Latin-1 etc.) everywhere else; and Nico Mak’s WinZip 6.x does not allow 8-bit passwords at all. UnZip 5.3 (or newer) attempts to use the default character set first (e.g., Latin-1), followed by the alternate one (e.g., OEM code page) to test passwords. On EBCDIC systems, if both of these fail, EBCDIC encoding will be tested as a last resort. (EBCDIC is not tested on non-EBCDIC systems, because there are no known archivers that encrypt using EBCDIC encoding.) ISO character encodings other than Latin-1 are not supported. The new addition of (partially) Unicode (resp. UTF-8) support in UnZip 6.0 has not yet been adapted to the encryption password handling in unzip. On systems that use UTF-8 as native character encoding, unzip simply tries decryption with the native UTF-8 encoded password; the built-in attempts to check the password in translated encoding have not yet been adapted for UTF-8 support and will consequently fail.

To use unzip to extract all members of the archive letters.zip into the current directory and subdirectories below it, creating any subdirectories as necessary:

To extract all members of letters.zip into the current directory only:

To test letters.zip, printing only a summary message indicating whether the archive is OK or not:

To test all zipfiles in the current directory, printing only the summaries:

(The backslash before the asterisk is only required if the shell expands wildcards, as in Unix; double quotes could have been used instead, as in the source examples below.) To extract to standard output all members of letters.zip whose names end in .tex, auto-converting to the local end-of-line convention and piping the output into more :

To extract the binary file paper1.dvi to standard output and pipe it to a printing program:

To extract all FORTRAN and C source files—*.f, *.c, *.h, and Makefile—into the /tmp directory:

(the double quotes are necessary only in Unix (and PTC MKS Toolkit shells) and only if globbing is turned on). To extract all FORTRAN and C source files, regardless of case (e.g., both *.c and *.C, and any makefile, Makefile, MAKEFILE or similar):

To extract any such files but convert any uppercase MS-DOS or VMS names to lowercase and convert the line-endings of all of the files to the local standard (without respect to any files that might be marked «binary»):

To extract only newer versions of the files already in the current directory, without querying (NOTE: be careful of unzipping in one timezone a zipfile created in another—ZIP archives other than those created by Zip 2.1 or later contain no timezone information, and a «newer» file from an eastern timezone may, in fact, be older):

To extract newer versions of the files already in the current directory and to create any files not already there (same caveat as previous example):

To display a diagnostic screen showing which unzip and zipinfo options are stored in environment variables, whether decryption support was compiled in, the compiler with which unzip was compiled, etc.:

In the last five examples, assume that UNZIP or UNZIP_OPTS is set to . To do a singly quiet listing:

To do a doubly quiet listing:

(Note that the «.zip» is generally not necessary.) To do a standard listing:

(Extra minuses in options don’t hurt.)

The current maintainer, being a lazy sort, finds it very useful to define a pair of aliases: tt for «unzip -tq» and ii for unzip (or zipinfo ). One may then simply type «tt zipfile» to test an archive, something that is worth making a habit of doing. With luck unzip will report «No errors detected in compressed data of zipfile.zip ,» after which one may breathe a sigh of relief.

The maintainer also finds it useful to set the UNZIP environment variable to « » and is tempted to add « » as well. His ZIPINFO variable is set to « ».

The exit status (or error level) approximates the exit codes defined by PKWARE and takes on the following values, except under VMS:

normal; no errors or warnings detected.

one or more warning errors were encountered, but processing completed successfully anyway. This includes zipfiles where one or more files was skipped due to unsupported compression method or encryption with an unknown password.

a generic error in the zipfile format was detected. Processing may have completed successfully anyway; some broken zipfiles created by other archivers have simple work-arounds.

a severe error in the zipfile format was detected. Processing probably failed immediately.

unzip was unable to allocate memory for one or more buffers during program initialization.

unzip was unable to allocate memory or unable to obtain a tty to read the decryption password(s).

unzip was unable to allocate memory during decompression to disk.

unzip was unable to allocate memory during in-memory decompression.

[currently not used]

the specified zipfiles were not found.

invalid options were specified on the command line.

no matching files were found.

the disk is (or was) full during extraction.

the end of the ZIP archive was encountered prematurely.

the user aborted unzip prematurely with control-C (or similar)

testing or extraction of one or more files failed due to unsupported compression methods or unsupported decryption.

no files were found due to bad decryption password(s). (If even one file is successfully processed, however, the exit status is 1.)

VMS interprets standard Unix (or PC) return values as other, scarier-looking things, so unzip instead maps them into VMS-style status codes. The current mapping is as follows: 1 (success) for normal exit, 0x7fff0001 for warning errors, and (0x7fff000? + 16*normal_unzip_exit_status) for all other errors, where the `?’ is 2 (error) for unzip values 2, 9-11 and 80-82, and 4 (fatal error) for the remaining ones (3-8, 50, 51). In addition, there is a compilation option to expand upon this behavior: defining RETURN_CODES results in a human-readable explanation of what the error status means.

Multi-part archives are not yet supported, except in conjunction with zip. (All parts must be concatenated together in order, and then «zip -F» (for zip 2.x) or «zip -FF» (for zip 3.x) must be performed on the concatenated archive in order to «fix» it. Also, zip 3.0 and later can combine multi-part (split) archives into a combined single-file archive using «zip -s- inarchive -O outarchive». See the zip 3 manual page for more information.) This will definitely be corrected in the next major release. Archives read from standard input are not yet supported, except with funzip (and then only the first member of the archive can be extracted).

Archives encrypted with 8-bit passwords (e.g., passwords with accented European characters) may not be portable across systems and/or other archivers. See the discussion in DECRYPTION above.

unzip ‘s («more») option tries to take into account automatic wrapping of long lines. However, the code may fail to detect the correct wrapping locations. First, TAB characters (and similar control sequences) are not taken into account, they are handled as ordinary printable characters. Second, depending on the actual system / OS port, unzip may not detect the true screen geometry but rather rely on «commonly used» default dimensions. The correct handling of tabs would require the implementation of a query for the actual tabulator setup on the output console.

Dates, times and permissions of stored directories are not restored except under Unix and PTC MKS Toolkit. (On Windows NT and successors, timestamps are now restored.)

[MS-DOS] When extracting or testing files from an archive on a defective floppy diskette, if the «Fail» option is chosen from DOS’s «Abort, Retry, Fail?» message, older versions of unzip may hang the system, requiring a reboot. This problem appears to be fixed, but control-C (or control-Break) can still be used to terminate unzip.

Under DEC Ultrix, unzip would sometimes fail on long zipfiles (bad CRC, not always reproducible). This was apparently due either to a hardware bug (cache memory) or an operating system bug (improper handling of page faults?). Since Ultrix has been abandoned in favor of Digital Unix (OSF/1), this may not be an issue anymore.

[Unix and PTC MKS Toolkit] Unix special files such as FIFO buffers (named pipes), block devices and character devices are not restored even if they are somehow represented in the zipfile, nor are hard-linked files relinked. Basically the only file types restored by unzip are regular files, directories and symbolic (soft) links.

[OS/2] Extended attributes for existing directories are only updated if the -o («overwrite all») option is given. This is a limitation of the operating system; because directories only have a creation time associated with them, unzip has no way to determine whether the stored attributes are newer or older than those on disk. In practice this may mean a two-pass approach is required: first unpack the archive normally (with or without freshening/updating existing files), then overwrite just the directory entries (e.g., «unzip -o foo */»).

[VMS] When extracting to another directory, only the [.foo] syntax is accepted for the -d option; the simple Unix foo syntax is silently ignored (as is the less common VMS foo.dir syntax).

[VMS] When the file being extracted already exists, unzip’s query only allows skipping, overwriting or renaming; there should additionally be a choice for creating a new version of the file. In fact, the «overwrite» choice does create a new version; the old version is not overwritten or deleted.

The primary Info-ZIP authors (current semi-active members of the Zip-Bugs workgroup) are: Ed Gordon (Zip, general maintenance, shared code, Zip64, Win32, Unix, Unicode); Christian Spieler (UnZip maintenance coordination, VMS, MS-DOS, Win32, shared code, general Zip and UnZip integration and optimization); Onno van der Linden (Zip); Mike White (Win32, Windows GUI, Windows DLLs); Kai Uwe Rommel (OS/2, Win32); Steven M. Schweda (VMS, Unix, support of new features); Paul Kienitz (Amiga, Win32, Unicode); Chris Herborth (BeOS, QNX, Atari); Jonathan Hudson (SMS/QDOS); Sergio Monesi (Acorn RISC OS); Harald Denker (Atari, MVS); John Bush (Solaris, Amiga); Hunter Goatley (VMS, Info-ZIP Site maintenance); Steve Salisbury (Win32); Steve Miller (Windows CE GUI), Johnny Lee (MS-DOS, Win32, Zip64); and Dave Smith (Tandem NSK).

The following people were former members of the Info-ZIP development group and provided major contributions to key parts of the current code: Greg «Cave Newt» Roelofs (UnZip, unshrink decompression); Jean-loup Gailly (deflate compression); Mark Adler (inflate decompression, fUnZip).

The author of the original unzip code upon which Info-ZIP’s was based is Samuel H. Smith; Carl Mascott did the first Unix port; and David P. Kirschbaum organized and led Info-ZIP in its early days with Keith Petersen hosting the original mailing list at WSMR-SimTel20. The full list of contributors to UnZip has grown quite large; please refer to the CONTRIBS file in the UnZip source distribution for a relatively complete version.