Archive Format Rar Or Zip Format
![Archive Format Rar Or Zip Better Archive Format Rar Or Zip Better](http://images.techhive.com/images/article/2013/09/7zip-100054936-orig.png)
How to Store a Rar or Zip in an Image File. An interesting little Windows hack, using 'copy' to store a ZIP or Rar archive inside of a PNG or JPEG image file. Allowing you to later extract it with WinRAR archiver. WinRAR is a Windows data compression tool that focuses on the RAR and ZIP data compression formats for all Windows users. Supports RAR, ZIP, CAB, ARJ, LZH, ACE, TAR.
Archive Format Rar Or Zip For Mac
RAR and ZIP File Differences This time I will discuss about the differences between RAR and ZIP files. RAR Archives: In many cases, creating RAR formats compress/decompress a more dense when compared with the ZIP format. Other advantages of the. Extract zip archive Files with WinRar CarlJaniei Subscribe Subscribed Unsubscribe 23 23 Loading. Add to Want to watch this again later? Sign in to add this video to a playlist. Sign in Share More Report Need to report the Sign in 68. Probably the biggest new feature in this WinRAR version is the new RAR 5.0 archive format that the program ships with. Responses to WinRAR 5.0 introduces the new RAR 5 format. What you need to know PixelWizard April 29, 2013 at 8:27 pm # So here's. Archiver for RAR & ZIP is a useful and simple to understand software solution designed specifically for devices running Windows 8.1 as an operating system, its main purpose being that of creating archives in various formats, as well as extracting files from existing.
What's the Best Way to Compress a Bunch of Files? Dear Lifehacker,Can you help me understand the different file compression formats? It seems like there are a ton out there (zip, gzip, bzip. I use? Signed,Cinnamonster.
Dear Cinnamonster,This is a good question, as it seems like every other file you download nowadays is in a different compression format, especially if you use multiple operating systems. First, we'll provide a very brief overview of how these compression formats work and the features that matter. Then, we'll note a few of the most popular formats and how they compare to one another. How Archives Work. Archive formats are most often used for two reasons: the ability to combine multiple files into one (for simple uploading or downloading), and compressing them (so they take up less space). Many formats also provide other features, like encryption, but we won't go into that today.
While most formats will archive and compress a group of files for you, a few formats are only designed to do one or the other. Tar, for example, only archives files, while gzip and bzip only compress files (and aren't able to combine multiple files into one). This is why you often see formats like tar. In general, unless you have special needs (like encryption), the three features you really want to look for in an archive format are compression ability (how much space you can save), compression time (how fast a given archive can be compressed or decompressed), and the software you'll need to use the format. How to Pick the Right Archive Format for Your Needs.
If you're archiving files for other people, I'd recommend using plain old zip. Unfortunately, most other formats (at least for Windows and Mac users) are going to require the other person download and install extra software, and no one wants to do that. If you absolutely have to, you can use something else, but the more difficult you make it for other people (especially non- tech- savvy people), the more they're going to wonder if what you're sending them is worth their while. That said, if you're archiving for your own purposes. There are way too many archive formats to go through here, so we'll list some of our favorites and their pros and cons.
Zip: It won't compress your files down a ton, but it's super fast and you don't need to install any extra software. Great for Windows and Mac users. Tar. gz: Similar to zip, tar. It's the most universally available option for Linux users, and also compresses files to a slightly smaller size than zip.
Great for Linux usess. Tar. bzip. 2: Another great option for Linux users; tar. The archive format made popular by our favorite compression tool, 7- Zip. It's pretty slow, but it compresses files like nobody's business. This is the best format to use if you need a really, really small file.
Zip is only available for Windows, but you can get a command- line tool for Mac OS X and Linux, too. This may seem counterintuitive, but it's useful if you're trying to send many large files over something like email, which limits the size of the files you send. RAR: This format is comparable to 7z. RAR compresses to smaller sizes. However, the only software that creates RAR files (Win. RAR) is shareware, and Windows- only.
You can uncompress RAR files on Mac and Linux, but not create them. RAR can also split up compressed archives into multiple parts. So which should you use? I personally use 7z unless I'm in some sort of rush, because it compresses so well. I don't like RAR because of its price or Windows- only nature, and I'm primarily a Mac and Linux user. As always, the best format is whatever best fits your need in any given situation.
If you're a Windows user and you're compressing files for other Windows machines, RAR and 7z are both good bets. Mac and Linux users will want to stick with tar. Mac users will need a program like GUI Tar to create these formats, unless they want to delve into the command line). Sincerely,Lifehacker.
P. S. This is a pretty basic summary, and a lot of this is opinion (and some people have some pretty strong opinions that may disagree with my own!). So if you have your own favorite archive format, let us know what it is and why you love it in the comments.
Zip (file format) - Wikipedia. ZIP is an archive file format that supports lossless data compression. A . ZIP file may contain one or more files or directories that may have been compressed. The . ZIP file format permits a number of compression algorithms, though DEFLATE is the most common. This format was originally created in 1. Phil Katz, and was first implemented in PKWARE, Inc.'s PKZIP utility. The . ZIP format is now supported by many software utilities other than PKZIP.
Microsoft has included built- in . ZIP support (under the name . Apple has included built- in . ZIP support in Mac OS X 1. BOMArchive. Helper, now Archive Utility) and later.
Most free operating systems have built in support for . ZIP in similar manners to Windows and Mac OS X. ZIP files generally use the file extensions . When navigating a file system via a user interface, graphical icons representing . ZIP files often appear as a document or other object prominently featuring a zipper. History. He created the format after his company had lawsuits filed against him by Systems Enhancement Associates (SEA) claiming that his archiving products were derivatives of SEA's ARC archiving system.
They wanted to imply that their product would be faster than ARC and other compression formats of the time. The earliest known version of . ZIP File Format Specification was first published as part of PKZIP 0. APPNOTE. TXT in 1.
The . ZIP file format was released into the public domain. At various times, PKWARE has added preliminary features that allow PKZIP products to extract archives using advanced features, but PKZIP products that create such archives are not made available until the next major release. Other companies or organizations support the PKWARE specifications at their own pace. The . ZIP file format specification is formally named . Specifications of some features such as BZIP2 compression, strong encryption specification and others were published by PKWARE a few years after their creation. The URL of the online specification was changed several times on the PKWARE website. A summary of key advances in various versions of the PKWARE specification: 2.
Expanded list of supported hash, compression (LZMA, PPMd+), encryption algorithms. The last 2 are applied to appropriate file types when .
Comments against this project cited the recognition that an existing published work on the . ZIP format has been in existence for over 1. PKWARE APPNOTE, recommending instead . The study period, which began in October 2. ZIP within international standards. In March, 2. 01. 1 this group presented to JTC 1 a new recommendation on how to incorporate .
ZIP within international standards. Acknowledging the broad interoperability that the . ZIP format has achieved the study group concluded in their recommendation that . This profile could be used by other international standards that use . ZIP to avoid having to write their own RER document where similar use of . ZIP may exist. At this time, no standards that use . ZIP have requested this profile.
Document Container File - Part 1. The format is a compatible profile of that defined by the Zip Application Note. A preparatory draft of the text is available as a public document.
Each file is stored separately, allowing different files in the same archive to be compressed using different methods. Because the files in a . ZIP archive are compressed individually it is possible to extract them, or add new ones, without applying compression or decompression to the entire archive. This contrasts with the format of compressed tar files, for which such random- access processing is not easily possible.
A directory is placed at the end of a . ZIP file. This identifies what files are in the . ZIP and identifies where in the . ZIP that file is located.
This allows . ZIP readers to load the list of files without reading the entire . ZIP archive. This allows for a . ZIP archive to be made into a self- extracting archive (application that decompresses its contained data), by prepending the program code to a .
ZIP archive and marking the file as executable. Storing the catalog at the end also makes possible hiding a zipped file by appending it to an innocuous file, such as a GIF image file. The . ZIP format uses a 3. CRC algorithm and includes two copies of the directory structure of the archive to provide greater protection against data loss. Structure. If the end of central directory record indicates a non- empty archive, the name of each file or directory within the archive should be specified in a central directory entry, along with other metadata about the entry, and an offset into the . ZIP file, pointing to the actual entry data.
This allows a file listing of the archive to be performed relatively quickly, as the entire archive does not have to be read to see the list of files. The entries within the .
ZIP file also include this information, for redundancy, in a local file header. Because zip files may be appended to, only files specified in the central directory at the end of the file are valid. Scanning a ZIP file for local file headers is invalid (except in the case of corrupted archives), as the central directory may declare that some files have been deleted and other files have been updated.
For example, we may start with a . ZIP file that contains files A, B and C. File B is then deleted and C updated. This may be achieved by just appending a new file C to the end of the original ZIP file and adding a new central directory that only lists file A and the new file C. When ZIP was first designed, transferring files by floppy disk was common, yet writing to disks was very time consuming. If you had a large zip file, possibly spanning multiple disks, and only needed to update a few files, rather than reading and re- writing all the files, it would be substantially faster to just read the old central directory, append the new files then append an updated central directory. The order of the file entries in the central directory need not coincide with the order of file entries in the archive.
Each entry stored in a ZIP archive is introduced by a local file header with information about the file such as the comment, file size and file name, followed by optional . Other extensions are possible via the .
Each file entry is marked by a specific signature. The end of central directory record is indicated with its specific signature, and each entry in the central directory starts with the 4- byte central file header signature. There is no BOF or EOF marker in the . ZIP specification.
Conventionally the first thing in a . ZIP file is a . ZIP entry, which can be identified easily by its local file header signature.
However, this is not necessarily the case, as this not required by the . ZIP specification - most notably, a self- extracting archive will begin with an executable file header. Tools that correctly read . ZIP archives must scan for the end of central directory record signature, and then, as appropriate, the other, indicated, central directory records. They must not scan for entries from the top of the ZIP file, because only the central directory specifies where a file chunk starts. Scanning could lead to false positives, as the format does not forbid other data to be between chunks, nor file data streams from containing such signatures. However, tools that attempt to recover data from damaged .
ZIP archives will most likely scan the archive for local file header signatures; this is made more difficult by the fact that the compressed size of a file chunk may be stored after the file chunk, making sequential processing difficult. Most of the signatures end with the short integer 0x. Viewed as an ASCII string this reads . Thus, when a . ZIP file is viewed in a text editor the first two bytes of the file are usually . Originally intended for storage of large .
ZIP files across multiple floppy disks, this feature is now used for sending . ZIP archives in parts over email, or over other transports or removable media. The FAT filesystem of DOS has a timestamp resolution of only two seconds; . ZIP file records mimic this.
As a result, the built- in timestamp resolution of files in a . ZIP archive is only two seconds, though extra fields can be used to store more precise timestamps. The . ZIP format has no notion of time zone, so timestamps are only meaningful if it is known what time zone they were created in.
In September 2. 00. PKWARE released a revision of the . ZIP specification providing for the storage of file names using UTF- 8, finally adding Unicode compatibility to . ZIP. All length fields count the length in bytes.
Local file header. Offset. Bytes. Description. It is divided into chunks, each with a 1. ID code and a 1. 6- bit length. This is immediately followed by the compressed data.
If the bit at offset 3 (0x. CRC- 3. 2 and file sizes are not known when the header is written. The fields in the local header are filled with zero, and the CRC- 3. Data descriptor. Offset. Bytes. Description. This is the number of bytes between the start of the first disk on which the file occurs, and the start of the local file header. This allows software reading the central directory to locate the position of the file inside the .
ZIP file. 4. 6n. File name. Extra field. 46+n+mk. File comment. After all the central directory entries comes the end of central directory (EOCD) record, which marks the end of the . ZIP file: End of central directory record (EOCD)Offset. Bytes. Description.
The most commonly used compression method is DEFLATE, which is described in IETF RFC 1. Compression methods mentioned, but not documented in detail in the specification include: PKWARE Data Compression Library (DCL) Implode, IBM TERSE, and IBM LZ7. Architecture (PFS). In particular, it is vulnerable to known- plaintext attacks, which are in some cases made worse by poor implementations of random- number generators. AES) methods have been documented in the . ZIP File Format Specification since version 5.
A Win. Zip- developed AES- based standard is used also by 7- Zip, Xceed, and Dot.