Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Portable Version #20

Closed
RoyiAvital opened this issue Jun 25, 2016 · 10 comments
Closed

Portable Version #20

RoyiAvital opened this issue Jun 25, 2016 · 10 comments
Labels

Comments

@RoyiAvital
Copy link

Hello,

Could you offer a portable version?

Namely all configuration is saved locally and no registry keys are created.

Thank You.

@vatterspun
Copy link

offer a portable version

This program is already portable as settings are saved to the application folder, meaning it can be run from a USB drive, cloud service, or backup drive with the same settings every time.

@RoyiAvital
Copy link
Author

How can it be portable and offer Context Menu?
Aren't those driven by Registry Keys?

Portable means no Registry Tracks as well.

Thank You.

@Bioruebe
Copy link
Owner

Bioruebe commented Jul 3, 2016

UniExtract itself only creates registry keys if you enable the context menu entries. Just keep it disabled and there shouldn't be any tracks.
However, i cannot guarantee no registry keys leftover after running UniExtract, because basically UniExtract uses a different extractors for different file types. This means while a zip extraction can be fully portable, unpacking an exe file might actually leave some traces on the system. (It shouldn't happen very often, but it's possible.)

Also, if the UniExtract has no write permission to its directory (e.g. when it is installed in the program files directory), the %appdata% folder is used to store settings. If you want to run it in a portable mode, make sure it lays somewhere else.

@vatterspun
Copy link

vatterspun commented Jul 3, 2016

i cannot guarantee no registry keys leftover after running UniExtract, because basically UniExtract uses a different extractors for different file types

Precursors to UniExtract2 had similar issues; they rely on a lot of externally developed programs so zero registry writes probably isn't possible. It could be put inside a wrapper program like YaP, WinPenPack, or PortableApps that will zap all registry entries on program close but that may not be the best use of the dev's time.

How can it be portable and offer Context Menu? Aren't those driven by Registry Keys?

Yeah Context Menu options (on any program) require registry writes. But I wouldn't want a feature useful to many users to be removed in the name of being more stealth. Portablefreeware has a note on their entry about this: http://www.portablefreeware.com/index.php?id=2764

@RoyiAvital
Copy link
Author

I can leave with the policy that as long as I keep the right Menu Integration disabled no registry keys are used.

I hope someone at PortableApps will upgrade the current UniExtract to this one.

Thank You.

@vatterspun
Copy link

PortableApps has traditionally ducked programs like Universal Extractor (the project manager didn't have nice things to say about it less than a year ago), but Bioruebe has taken the concept much further and added a lot more functionality. That might change some minds.

@djohns451
Copy link

djohns451 commented Nov 7, 2016

@Bioruebe How about emulated registry keys that bypass features that don't make sense in a portable version?

@djohns451
Copy link

In my fork, specifically in the portable branch, there is beginning work on a portable version.

@vatterspun
Copy link

In my fork, specifically in the portable branch, there is beginning work on a portable version.

@djohns451 Is there any chance we could talk you into collaborating with @Bioruebe on UE2? There are already quite a few Universal Extractor forks.

@djohns451
Copy link

djohns451 commented Dec 14, 2016

You could, @vatterspun. In fact, when it reaches a suitable degree, I plan on creating a pull request of the changes, merging them into the parent fork.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

4 participants