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

Notes regarding WinMerge_0.2011.211.170_x64_setup.cpl #22

Open
Gitoffthelawn opened this issue Dec 19, 2021 · 0 comments
Open

Notes regarding WinMerge_0.2011.211.170_x64_setup.cpl #22

Gitoffthelawn opened this issue Dec 19, 2021 · 0 comments

Comments

@Gitoffthelawn
Copy link
Contributor

Thank you for WinMerge2011.

I few comments and questions regarding WinMerge_0.2011.211.170_x64_setup.cpl:

  1. When renaming the file to WinMerge_0.2011.211.170_x64_setup.zip, and performing an extraction, 7-Zip will issue a warning that the file is not in zip format, but is in 7z format. This, of course, makes perfect sense if it was compressed in 7z format. Was it?
  2. When renaming the file to WinMerge_0.2011.211.170_x64_setup.7z, and performing an extraction, 7-Zip will issue a warning that the extraction is being performed from an offset. Why is this?
  3. Just FYI, ShellExtensionU.dll is currently being detected as malware by the heuristic analyzers of some popular AV tools. For unclear reasons (likely different settings), those same tools do not report problems in the VirusTotal sandbox (but other AV engines do report problems). If one is not using WinMerge2011's shell extension functionality, can WinMerge2011 be successfully used as a portable app if the user simply omits copying ShellExtensionU.dll and ShellExtensionX64.dll from the cpl file?
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant