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
Something that a few archival tools have implemented was the ability to run .exe files from an archive without manually extracting the entire archive. I am only talking about exe files which depend on other files to run.
This feature is extremely convenient in my opinion and would be a great feature for NanaZip to have.
I see a couple different ways of doing this:
Extract siblings of the file you are extracting (including folders of course) to a temp folder. This could be optimized to ignore certain filetypes that are rarely needed to run an EXE such as movie files etc.
Extract the whole bloody archive to a temp folder and remove it as soon as the process is not running. Note this would require some sort of process to run in the background after NanaZip is closed until said application is gone.
Extract just commonly needed filetypes such as .dll .dat etc.
Extract the EXE to a temp folder and surround it with placeholder files. I imagine that the API that allows Google Drive and Onedrive to put 'empty' files (which are downloaded on the fly) could also be used to 'stream' the files needed by the exe on the fly during execution.
If 4 could be implemented it would easily put NanaZip on the top as the best extraction software (again, my opinion!).
The text was updated successfully, but these errors were encountered:
Something that a few archival tools have implemented was the ability to run .exe files from an archive without manually extracting the entire archive. I am only talking about exe files which depend on other files to run.
This feature is extremely convenient in my opinion and would be a great feature for NanaZip to have.
I see a couple different ways of doing this:
If 4 could be implemented it would easily put NanaZip on the top as the best extraction software (again, my opinion!).
The text was updated successfully, but these errors were encountered: