WinRAR - What's new in the latest version Version 5.11 1. WinRAR can unpack TAR archives containing folders with pax extended headers. Previous versions failed to unpack them. 2. "Keep broken files" extraction option is supported for 7-Zip archives. 3. Bugs fixed: a) WinRAR 5.10 did not set "hidden", "read-only" and "system" file attributes when unpacking ZIP archives; b) WinRAR 5.10 failed to update self-extracting RAR archives containing nested ZIP archives stored without compression; c) ZIP archive created with "Do not store paths" option included unnecessary empty name records for folders; d) archived files could have 1 hour modification time error in Windows XP; e) deleting a file in RAR5 solid archive containing files stored with -ver switch caused such files to lose version information; f) black rectangles were displayed instead of toolbar buttons in 16- and 24- bit screen color modes and Windows custom text size larger than 100%. Version 5.10 1. Added extraction support for ZIP and ZIPX archives using BZIP2, LZMA and PPMd compression. 2. Added extraction support for 7z split archives (.7z.001, .7z.002, ...). 3. Added support for AES-NI CPU instructions allowing to improve RAR encryption and decryption performance. 4. Default theme images are scaled up with better quality in high DPI display mode. 5. Environment variables, such as %temp%, can be used in "Files to add" field of archiving dialog. 6. Switch -ai can be used when creating RAR archive, so predefined values, typical for file and folder, are stored instead of actual attributes. Previously this switch could be used only when extracting. Version 5.01 1. RAR 5.0 archives can include an optional quick open information controlled with -qo[-|+] switch or "Quick open information" options group in archiving dialog. It allows to open the archive contents in WinRAR faster. This version provides better update performance for archives containing both quick open information and service records, such as NTFS file security. Also default parameters of quick open information are optimized to achieve faster open time for such archives. 2. Bugs fixed: a) "Find" command could fail when searching text string in .7z archives; b) when opening RAR 5.0 archive with encrypted file names stored in another such archive, WinRAR could issue an erroneous message that password is incorrect. It happened only if passwords to inner and outer archives were different. It did not affect extraction, all files could be unpacked regardless of this message; c) option "Use for all archives" in password dialog did not suppress additional password requests for RAR 5.0 archives with encrypted file names; d) WinRAR address bar did not process correctly environment variable based paths, such as %temp%; e) storing NTFS file security and alternate data streams did not work for file pathnames longer than 260 characters; f) "Test" command could erroneously report damaged data in valid recovery record if only a part of files in RAR 5.0 archive was tested. It did not happen if entire archive contents was tested; g) "Test" command erroneously reported errors when verifying RAR 4.x Unix symbolic links; h) WinRAR "View" command did not work for files inside of BZIP2 archives; i) if "High precision modification time" option in archiving dialog was turned off, WinRAR did not store the modification time at all instead of storing a lower precision time; j) destination paths containing .\ or ..\ component did not work when extracting non-RAR archives in WinRAR command line mode; k) WinRAR failed to unpack multivolume CAB archives. Version 5.00 1. New RAR 5.0 archiving format. You can use "RAR 5.0" option in archiving dialog or -ma command line switch to create RAR 5.0 archives. Older software including older WinRAR versions is not able to decompress RAR 5.0 archives, so if you plan to send an archive to other people, it is necessary to take the compatibility issue into consideration. You can select "RAR" instead of "RAR5" option in archiving dialog to create RAR 4.x archives compatible with previous WinRAR versions. 2. Changes in RAR 5.0 compression algorithm: a) maximum compression dictionary size is increased up to 1 GB in 64 bit WinRAR. 32 bit WinRAR version can use up to 256 MB dictionary when creating an archive. Both 32 bit and 64 bit versions can unpack archives with any dictionary size, including 1 GB; b) default dictionary size for RAR 5.0 is 32 MB, typically resulting in higher compression ratio and lower speed than RAR 4.x 4 MB. You can use "Dictionary size" archiving dialog option or -md<size> switch to change this value; c) -md<size> switch syntax is modified to support larger dictionary sizes. Append 'k', 'm' and 'g' modifiers to specify the size in kilo-, mega- and gigabytes, like -md64m for 64 MB dictionary. If modifiers are not present, megabytes are assumed, so -md64m is equal to -md64; d) RAR 5.0 format includes Intel IA-32 executable and delta compression algorithms, but RAR 4.x text, audio, true color and Itanium algorithms are not supported. These excluded algorithms are not efficient for modern data types and hardware configurations; e) RAR 5.0 decompression can utilize several CPU cores. Though not to same extent as in compression algorithm, it improves the decompression speed on large files with poorly compressible data or when using BLAKE2 checksums. 3. Changes in RAR 5.0 archive format: a) file times are stored as Coordinated Universal Time (UTC) instead of former local time, making file exchange among several time zones more straightforward; b) file names and archive comments use UTF-8 encoding. 4. RAR 5.0 recovery record is based on Reed-Solomon error correction codes. If recovery record size is large enough, 5% and more, the new error correction scheme provides much higher resistance to multiple damages comparing to RAR 4.x recovery record. Smaller record, such as 1 - 2%, or less random damage type would result in less difference between 4.x and 5.0. For single continuous damage 4.x and 5.0 efficiency is about the same. Additionally to usual data erasures, the new recovery record is able to detect deletions and insertions of much larger size than in previous RAR versions. Maximum insertion size is several megabytes. Maximum deletion size depends on the damage type and in some cases can be as large as the recovery record size. Still, the best recovery performance and efficiency is achieved if no deletions and insertions are present, so all data including damaged sectors preserve their original positions. Thus, if you use some special software to copy an archive from damaged media, it is better to choose the mode, when damaged sectors are filled by zeroes or any other data instead of cutting them out completely from resulting file. RAR 5.0 recovery record is more resistant to damage of recovery record itself and can utilize a partially corrupt recovery record data. Note, though, that "Repair" command does not fix broken blocks in recovery record. Only file data are corrected. After successful archive repair, you may need to create a new recovery record for saved files. New recovery record is not based on 512 byte sectors anymore and incorporates more complicated data structures. So it is impossible to specify its size in sectors. For RAR 5.0 archives the parameter of -rr[N] switch and rr[N] command is always treated as a percent of archive size regardless of presence of % character. Typically N% recovery record can repair up to N% of continuously damaged data and increases the archive size by only slightly more than N%. Ability to fix multiple damages is proportional to N. We used "Screaming Fast Galois Field Arithmetic Using Intel SIMD Instructions" paper by James S. Plank, Kevin M. Greenan and Ethan L. Miller to improve Reed-Solomon coding performance. Also we are grateful to Artem Drobanov and Bulat Ziganshin for samples and ideas allowed to make Reed-Solomon coding more efficient. 5. "Test" command verifies validity of RAR 5.0 recovery record. Recovery record is tested after processing all archived files. If corrupt archive contains the recovery record, it might be possible to repair it even if recovery record validity test is failed. "Repair" command attempts to utilize even a partially damaged recovery record. So treat the negative recovery record test result as a reason to re-create the archive if original files are still available, but not as a reason to avoid "Repair" command. 6. Changes in RAR 5.0 encryption algorithm: a) encryption alg...
AnOnYmOuSFORCE