Total Commander

2ghisler(Author)

Therefore I will use lelik007's suggestion to automatically unpack files when the dictionary size is at least 2GB smaller than the installed RAM.

If we want to take for the beginning point the installed RAM maybe it's should be - 3 Gb dictionary or for some systems the swap will be used.
Read below, please.

2MaxX
I don't use Total7zip and IDK how it does it.
In Winrar and 7-zip you can increase a limit up to all the size of your RAM - 1 Gb (31 Gb) I've just unpacked 14 Gb file with 7-zip though it's been only 12 Gb free. And of course Winrar does the same. My current laptop has 16 GB RAM + 4 GB of SSD swap.
You can use 7zG.exe with -smemx30g switch (you've got it anyway if you use Total7zip) or unrarw64.exe with -mdx30 switch to unpack it.

But can't do this for "14Gb.rar" with unRarDll now.

If it's about TC - because the limit isn't changed jet, this will be in the future builds.

Actually, if a person has a PC with 32 Gb memory installed only a file with a dictionary of 18 Gb can be created. Because the algo is asymmetric and it's meant 18 Gb for unpacking and requires 29 Gb to pack. And it requires 44 Gb to create a file with a dictionary of 30 Gb.

lelik007 wrote: 2024-10-20, 21:49 UTCI don't use Total7zip and IDK how it does it.

Very useful plugin. Works perfectly with regular 7z*.exe and 7z*.dll any version you want. Now I use the last one.

lelik007 wrote: 2024-10-20, 21:49 UTC4 GB of SSD swap.

Thanks, but no. I don't want this legacy problem maker on my OS. The last time I used swap was almost 20 years ago on ancient 32-bit XP SP2 and 192 MB of RAM (one 256 MB minus 64 MB for iGPU).

lelik007 wrote: 2024-10-20, 21:49 UTCIf it's about TC - because the limit isn't changed jet, this will be in the future builds.

Ok, I can wait for that.

lelik007 wrote: 2024-10-20, 21:49 UTCIt's asymmetric

I know.

2MaxX
As I said maybe it's should be: installed memory - 3 Gb = allowed dictionary. But Winrar and 7-zip allow - 1 Gb. I just said that both SW can use swap, I can free the memory to 14 Gb for my laptop and 30 Gb for my desktop.

2MaxX
I've just now seen a laptop with 16 Gb memory installed and iGPU - it's 13,4 Gb free from the start (Windows 10 22H2 Professional) but it also uses the default setting for a swap file - 2893 Mb. So 7-zip installed there unpacked 14Gb.rar with no issues. And 7-zip uses the code of unrar.exe. Thus this might be an issue for the PCs with iGPUs and a swap disabled to unpack a dictionary like : installed memory - 2 Gb.

2lelik007
Just read my situation as a PC with only 30 gigs of RAM "installed" (available after iGPU usage). I am not talking about any memory usage percentage or checking "minus 1 vs minus 2" gigs from available memory. I only say that now I can test dictionaries only smaller than my available RAM. Nothing strange here.

2ghisler(Author)
TBH Christian, IDK what is the better Idea for TC or to use the same limits as the original SW and maybe use some swap or to limit unpacking with the slightly lesser dictionaries and to use no swap. Anyway a person is always able to unpack a file with a dictionary created by the same PC.

2MaxX
I read it, yes, this just means you are able to unpack the files with the lesser dictionaries, 28-29 Gb for example.

I will show a warning where the user can click on "Retry" to try anyway.

2ghisler(Author)
Thank you, I've checked now and unpacked 14Gb.rar on my laptop with 16 Gb memory installed and actually 13 Gb free, TC said "Not enough memory" - I agreed, I don't mind using some swap. I consider this as implemented.

For 30Gb.rar the problem is that I'm away from home where my PC with 32 Gb RAM is so I can't check it now. And I 'll be at least for 10 days.
Maybe the others users could do it faster.

2ghisler(Author)
I've checked 30Gb.rar on a PC with 32 Gb memory installed and 29,3 Gb free I ignored the warning and it worked, maybe we'll receive some more feedback after the release but for now it's done. I can't checked a file with the maximum possible dictionary - 64 Gb, anyway.