No, msi wouldn't be enough. Don't think only about yourself! You want only msi and someone other (like me) would want exe installer. Let it be as it is. It would be even better if it would be self extracting portable version (sfx).
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Any word on when you can get the nuget packages updated to 18.05? We got the 16.04 assemblies, and it's ticking off our virus detection. Just straight deleting the 7 zip assemblies from our assemblies. We really need this for a release.
Thanks!
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
there is native _Bool type in C99, and we can use bool when including <stdbool.h> and we can easily make it compatible with C89 compilers like VC6 by #if...#else. Igor can consider switch to C99 bool.
Last edit: Linda 2018-11-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
We are expeiriencing a rather strange bug in 18.05. When browsing to unpack or create archived files, when choosing to browse via the "\." in the file manager, we are presented with an "Access is denied" error. Browsing via "Computer" works as expected. I have tried this on Windows 7, 2008 R2 & 2012 R2 and they all have the same problem (x86 & x64). Is it at all possible to remove the "\." completely from the file browser?
Last edit: Garth Lahana 2018-06-07
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Igor!
I have mbr formated disk and I would like to undelate some files from c: windows partition but I can't (process can't access to file used by other process). With newest 7-Zip version there is no directory "delated" and in 9.20 version there is no "PhysicalDrive0". How to undelate?
Last edit: mdadm 2018-06-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Thanks! It worked!
However when I try this on my older drive with win xp first system partition 7-zip when opening 0.ntfs hangs (but not crash - opening for ever) and I can't cancel. I have to terminate 7-zip process. Maybe m$ messed something with one of their updates? I installed win7 on newer drive and I remember there was some update to win7 that chaneged something about reading win xp partitions. But with other partitions on that drive it works + work on win7 hdd partitions.
Last edit: mdadm 2018-06-09
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi Igor!
I tried your command (7z l 0.ntfs -mld > a.txt) with latest 7-Zip 18.05 (x86 and x64) version, but it says: "ERROR: 0.ntfs : opening : Parameter is incorrect."
I also tried opening copied 0.ntfs partition (which is now file) in 7zFM (version 18.05 because 9.20 is hanging) and opening failed. Some info about file:
Name: 0
Size: 989
Packed Size: 406
Host OS: Unix
CRC: D6BEA98C
------------------------:
Size: 989
Packed Size: 406
Folders: 0
Files: 1
CRC: D6BEA98C
------------------------:
Path: J:\x\0.ntfs
Type: gzip
Error Type: NTFS
Errors: There are some data after the end of the payload data
Offset: 215060
Physical Size: 406
Tail Size: 31 560 151 638
Headers Size: 10
Streams: 1
How to open this file? What is good parameter to open from command line?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
7-zip can't open file as ntfs by some error, so it opens it as gzip file instead.
Maybe there is some unusual field value in ntfs volume. 7-Zip supports most ntfs files. But some cases are not supported probably:
try
7z l -tntfs 0.ntfs > 1.txt
7z l -tntfs -mld 0.ntfs > mld.txt
And create another forum thread, if you want to write more about that problem.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
When viewing information of PE file, the VS_VERSION_INFO block is mixed altogether into one very very long line which is very ugly and hard to see, but prior to 18.04 the block is normally separated into several lines. Is it a bug?
Thanks for new release :)
What is a reason for publishing both: .exe and .msi installers? Wouldn't msi be enough?
No, msi wouldn't be enough. Don't think only about yourself! You want only msi and someone other (like me) would want exe installer. Let it be as it is. It would be even better if it would be self extracting portable version (sfx).
The 32bit exe installer doesn't seem to register the shell extension on a 64bit windows 10 system. 64bit exe works fine.
Hey Igor,
Any word on when you can get the nuget packages updated to 18.05? We got the 16.04 assemblies, and it's ticking off our virus detection. Just straight deleting the 7 zip assemblies from our assemblies. We really need this for a release.
Thanks!
LzmaEnc.c:1467:69: warning: for loop has empty body [-Wempty-body]
for (len = 3; len < limit && data[len] == data2[len]; len++);
i have to put -Wno-empty-body to silence this warning.
And i add this condition :
ifndef _7ZIP_ST
LzmaEnc_Finish(p);
endif
and
ifndef _7ZIP_ST
void LzmaEnc_Finish(CLzmaEncHandle pp)
{
CLzmaEnc p = (CLzmaEnc )pp;
if (p->mtMode)
MatchFinderMt_ReleaseStream(&p->matchFinderMt);
}
endif
1) what exact compiler version for
empty-bodywarning?Can we solve it without
-Wempty-body?Try also:
for () {}2) Note that
Lzma2Enc.calso callsLzmaEnc_Finish()Last edit: Igor Pavlov 2018-06-01
1 - clang
2 - Its a problem i posted 3 years ago.
https://sourceforge.net/p/sevenzip/discussion/45797/thread/9e68012c/?limit=25&page=2#0ef0/0697/a6a9/960f/8fa7/d4c7/a013
I don't use Lzma2Enc.c but LzmaEnc.c from LzmaLib.c, the LZMA library interface as you call it.
At every release i have to fix it.
Another thing.
i cannot use LzmaLib.c functions from Swift because you define "typedef int Bool" in 7zTypes.h
and Swift already use Bool but not as int.
So i have to call a C pgm ( a wrapper) who call the LzmaLib.c func.
Swift -> Wrapper -> LzmaLib.c
By doing that LzmaLib.c is no more the LZMA library interface.
Your Bool type is only use in LzmaDec.c, LzmaEnc.c and LzmaEncMode.c.
It can easily be replaced by int.
1) so what about
for (...) {}does it work?
2) I don't know about swift / c code mix.
Is that
Boolthing the only problem there?there is native
_Booltype in C99, and we can useboolwhen including<stdbool.h>and we can easily make it compatible with C89 compilers like VC6 by #if...#else. Igor can consider switch to C99bool.Last edit: Linda 2018-11-09
Finally ... 7 months later..... this boolean bug is solved.
So I no longer need the wrapper and can now use the lzma apis directly with Swift.
the second problem raised three years ago is still not solved.
Hi.
Any news on the following security issue? The page says 7z is affected.
https://github.com/snyk/zip-slip-vulnerability
We are expeiriencing a rather strange bug in 18.05. When browsing to unpack or create archived files, when choosing to browse via the "\." in the file manager, we are presented with an "Access is denied" error. Browsing via "Computer" works as expected. I have tried this on Windows 7, 2008 R2 & 2012 R2 and they all have the same problem (x86 & x64). Is it at all possible to remove the "\." completely from the file browser?
Last edit: Garth Lahana 2018-06-07
It's not bug.
It's unusual additional feature that is not available in another programs.
You need administrator rights for that feature.
Is it at all possible to remove this from the file manager with a setting perhaps?
Even if I run FM.exe as an administrator, I still have the same error...
Try to open another volume or "PhysicalDrive0".
Hi Igor!
I have mbr formated disk and I would like to undelate some files from c: windows partition but I can't (process can't access to file used by other process). With newest 7-Zip version there is no directory "delated" and in 9.20 version there is no "PhysicalDrive0". How to undelate?
Last edit: mdadm 2018-06-09
you can open in 7-zip 9.20:
Thanks! It worked!
However when I try this on my older drive with win xp first system partition 7-zip when opening 0.ntfs hangs (but not crash - opening for ever) and I can't cancel. I have to terminate 7-zip process. Maybe m$ messed something with one of their updates? I installed win7 on newer drive and I remember there was some update to win7 that chaneged something about reading win xp partitions. But with other partitions on that drive it works + work on win7 hdd partitions.
Last edit: mdadm 2018-06-09
Try to copy 0.ntfs to another volume and then open it with different versions of 7-zip.
Also you can get deleted files with command line in latest 7-Zip with
-mldswitch:Hi Igor!
I tried your command (7z l 0.ntfs -mld > a.txt) with latest 7-Zip 18.05 (x86 and x64) version, but it says: "ERROR: 0.ntfs : opening : Parameter is incorrect."
I also tried opening copied 0.ntfs partition (which is now file) in 7zFM (version 18.05 because 9.20 is hanging) and opening failed. Some info about file:
Name: 0
Size: 989
Packed Size: 406
Host OS: Unix
CRC: D6BEA98C
------------------------:
Size: 989
Packed Size: 406
Folders: 0
Files: 1
CRC: D6BEA98C
------------------------:
Path: J:\x\0.ntfs
Type: gzip
Error Type: NTFS
Errors: There are some data after the end of the payload data
Offset: 215060
Physical Size: 406
Tail Size: 31 560 151 638
Headers Size: 10
Streams: 1
How to open this file? What is good parameter to open from command line?
7-zip can't open file as ntfs by some error, so it opens it as gzip file instead.
Maybe there is some unusual field value in ntfs volume. 7-Zip supports most ntfs files. But some cases are not supported probably:
try
And create another forum thread, if you want to write more about that problem.
Is the newest version of 7 Zip (18.05) DFARS compliant? Will it ever be?
7-Zip has no any relations with DFARS.
There is a strange change in 18.05.
When viewing information of PE file, the VS_VERSION_INFO block is mixed altogether into one very very long line which is very ugly and hard to see, but prior to 18.04 the block is normally separated into several lines. Is it a bug?