Total Commander

I want to report this TC behavior when using 7z or 7zG packer for ZIP files.
I set up these packers in the settings window (see two images)

1) Image: https://imgur.com/a/5BlV4dv
2) Image: https://imgur.com/a/5BlV4dv

The operation is to decompress the files contained within a ZIP file.
In the left window with ENTER I open the file to view its content and then select all the files.
I press F5 to copy the selected files (ALL) in the right window.
I get these two errors depending on whether I use 7z or 7zG

1) Image: https://imgur.com/a/4BgER2a
2) Image: https://imgur.com/a/UfIBsyL

I don't know if the assumptions of this operation are correct.

I assumed that using 7z or 7zG packer this operation was POSSIBLE

So I reported it

Not confirmed here.

I use the following definition:
"C:\Program Files\7-Zip\7z.exe" -mcu=on

Also tested with
"C:\Program Files\7-Zip\7zg.exe" -mcu=on

No problem to pack or unpack any set of files and dirs with this definitions.

I have tested on my system (a)

"C:\Program Files\7-Zip\7z.exe" -mcu=on
"C:\Program Files\7-Zip\7zg.exe" -mcu=on

(I dont know ... -mcu=on

but I confirm the error is again.

(a) Windows 11 Pro build 22621.2070

I don't know what's wrong in your system.
What version of 7zip you are using ?
I have 23.01 x64

Let's wait if others can reproduce your problem.

Version 22.01 x64

By the way, I can't find any explanations about the restrictions on entering additional command line parameters for 7z anywhere.
In the help it is TOO simply written that "It is possible to specify parameters like -mcu=on behind the program name."
What does it mean here "LIKE"? like what and from which FULL list of which params exactly?
https://ibb.co/5nvt3pq
Are we talking about these switches? Or are there other options we can add?
Or vice versa - the restriction is applied as a ban on four 'Add(Update)/Delete/Extract' file commands only?

2AntonyD
Christian explained in another thread that you can't add parameters like "a"
as TC will automatically add the relevant basic commands.
For all the others, you have to test if 7z accepts them in zip mode.

I can confirm the bug as reported by sscireca for unpacking zip files - only I get both error messages when I use 7zg.exe: first "Unknown switch -d" and then "Not enough memory!". If I use 7z.exe I only get the message "Not enough memory!"

Tested with both 11.00rc1 32bit and 64bit and with 7zip v. 22.01 and 23.01
Tested with both files packed with TC's internal zip-packer (compression 9), and packed with 7zg.exe
Also tested with several previous TC 11 beta versions - same problem

These are my options when packing to zip archives with 7zip: https://tcmd.madsenworld.dk/7zipoptions.png

I use no switches or commands in the zip-packer/unpacker fields. My test files only have ANSI-characters, so no need for -mcu=on.


So far only tested under Window 7 and 10.

I have no problems packing files with zip-packer configured as 7zg.exe or 7z.exe

2sscireca

1) Image: https://imgur.com/a/5BlV4dv
2) Image: https://imgur.com/a/5BlV4dv

The links to the two images are the same!

2Horst.Epp
I read it - but again - the word "LIKE" is used there. Those there is no direct and clear enumeration - which flags / options are prohibited for use and the phrase that "everything that is NOT listed as prohibited 'above' is considered allowed for use in 7Z cmdline." In such a clear formulation, everything would be clear. And so, it turns out that my "experiments" with the selection of parameters can just run into some other "like -a" parameter, which will break the logic of Total. This is theoretically unacceptable.

2ghisler(Author)
Can you make a strict distinction between which commands/flags/switches... of those available on the 7z command line you are restricting use - only by full enumeration, not by the evasive phrase "LIKE..."?

2sscireca
btw - the topic's title imho contains typo:
Decompress Zip files with 7z OR 7zG packer
can you fix it?

petermad wrote: ↑2023-07-28, 21:54 UTC I can confirm the bug as reported by sscireca for unpacking zip files - only I get both error messages when I use 7zg.exe: first "Unknown switch -d" and then "Not enough memory!". If I use 7z.exe I only get the message "Not enough memory!"

Tested with both 11.00rc1 32bit and 64bit and with 7zip v. 22.01 and 23.01
Tested with both files packed with TC's internal zip-packer (compression 9), and packed with 7zg.exe
Also tested with several previous TC 11 beta versions - same problem

These are my options when packing to zip archives with 7zip: https://tcmd.madsenworld.dk/7zipoptions.png

I use no switches or commands in the zip-packer/unpacker fields. My test files only have ANSI-characters, so no need for -mcu=on.


So far only tested under Window 7 and 10.

I have no problems packing files with zip-packer configured as 7zg.exe or 7z.exe

Yes you're wright !

As said, no such errors here under Windows 11 and TC 11.00RC3
regardless which exe of 7zip I use.
Tested with various sets of large and small trees to archive into a zip archive.
Also tested with TC 11.00RC3 x86.
No glue, how others get these errors.

2Horst.Epp

Tested with various sets of large and small trees to archive into a zip archive.

The bug is not when packing the zip archive with 7z.exe or 7xg.exe - it is when UNpacking - remember do disable the option: "Always use internal unzipping (if possible)" - https://tcmd.madsenworld.dk/7zip_zip.png

petermad wrote: ↑2023-07-29, 15:25 UTC 2Horst.Epp

Tested with various sets of large and small trees to archive into a zip archive.

The bug is not when packing the zip archive with 7z.exe or 7xg.exe - it is when UNpacking - remember do disable the option: "Always use internal unzipping (if possible)" - https://tcmd.madsenworld.dk/7zip_zip.png

I have tested packing and unpacking of course
but I had not disabled "Always use internal unzipping (if possible)"
Finally, error confirmed

Horst.Epp wrote:Finally, error confirmed

Thanks