VictorVG

I think we're mistaken in expecting identical behavior across different operating systems, dismissing the differences in their security models as insignificant. The UNIX-family OS security model specifies logical YES/NO values ​​for any action, while the WINNT model states, "Only those explicitly stated as ALLOWED are permitted; everything else is denied by default." Therefore, when migrating an access rights model from one model to another, we need to take into account the differences in their approaches...

Just use -u swtch i(Auto rename all u Rename all extracted files that already exist in the output directory) in to 7Z/7zFM commad prompt (GUI don't have extract options) : 7z x -u <arc>.<ext></ext></arc>

Понял. Уже нету.

Похоже в FarAudioPlayer_3.48.27.5055_x64.7z попал лишний файл - atools.exe

Archives and installers downloaded from the project's website do not require any passwords. It appears you downloaded a fake version of 7zip.com, which imitates the design of 7-zip.org but distributes malware (source is https://www.opennet.ru/opennews/art.shtml?num=64799 (Russian, suite code page is KOI-8R)). Furthermore, attackers were found to have created a website called 7zip.com, which mimicked the official 7-zip.org website, but offered a modified installer, 7zipInstall.exe, containing malicious...

That's right - multi-volume 7-zip archives are split - the source file is divided into fragments L-bytes long, 7-Zip reads them sequentially, and the OS does not know the length of the segments and does not know how to work with them. Use a command like: copy /b arc000 + /b arc001 + ... + /b arcNNN /b arc.7z to merge them into one file, and then the OS will be able to read it.

**gwergewg ** You are wrong - the FreeImage library is a dynamically plug-in module, in this case a DLL, and like any DLL it is launched in the process of the calling module, usually it is a GUI or console program and in this archive it is in the \FreeImage\Dist\x32\ and \FreeImage\Dist\x64\ directories. Yes, it cannot be used directly because, like any DLL, it has a special call format (API), but if we have an application that can work with it and uses an older version of the library, and if the...

**gwergewg ** You are wrong - the FreeImage library is a dynamically plug-in module, in this case a DLL, and like any DLL it is launched in the process of the calling module, usually it is a GUI or console program and in this archive it is in the \FreeImage\Dist\x32\ and \FreeImage\Dist\x64\ directories. Yes, it cannot be used directly because, like any DLL, it has a special call format (API), but if we have an application that can work with it and uses an older version of the library, and if the...