You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
There's good support here for LZNT1 compression (created from Windows Compress contents to save space option or compact.exe /c).
In Windows 10 / Windows Server 2016, some extra compression algorithms XPRESS4K, XPRESS8K, XPRESS16K, and LZX were added (created from compact.exe /c /EXE LZX). These have higher compression ratios but do not support in-place modification.
On disk these files show up as reparse points, with the compressed data stored in a WofCompressedData ADS stream. In real Windows decompression is performed by a filesystem filter driver above ntfs. So it's arguable if it belongs in this project or not. But to correspond to the existing lznt1 support, there should be support for the other compression algorithms too.
Hi!
There's good support here for LZNT1 compression (created from Windows
Compress contents to save space
option orcompact.exe /c
).In Windows 10 / Windows Server 2016, some extra compression algorithms
XPRESS4K
,XPRESS8K
,XPRESS16K
, andLZX
were added (created fromcompact.exe /c /EXE LZX
). These have higher compression ratios but do not support in-place modification.On disk these files show up as reparse points, with the compressed data stored in a
WofCompressedData
ADS stream. In real Windows decompression is performed by a filesystem filter driver above ntfs. So it's arguable if it belongs in this project or not. But to correspond to the existing lznt1 support, there should be support for the other compression algorithms too.Some links:
The text was updated successfully, but these errors were encountered: