View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0001797 | MMW v4 | Install/Config | public | 2005-02-08 04:48 | 2015-09-30 16:23 |
Reporter | rusty | Assigned To | |||
Priority | immediate | Severity | feature | Reproducibility | always |
Status | closed | Resolution | fixed | ||
Target Version | 4.1.6 | Fixed in Version | 4.1.9 | ||
Summary | 0001797: Add empty winamp.exe and winamp.ini files to /MediaMonkey directory (Norton security issues) | ||||
Description | This was suggested by Lowlander as a means of getting Winamp installers to work correctly with MediaMonkey. I tested it out and it works! All we have to do is modify the installer to copy a blank file called winamp.exe to the mm directory. | ||||
Additional Information | Confirmed that this fixed Ticket http://www.mediamonkey.com/support/staff/index.php?_m=tickets&_a=viewticket&ticketid=109 | ||||
Tags | No tags attached. | ||||
Fixed in build | 1763 | ||||
|
Note: I've been using MM in this manner for months without a problem. |
|
I'm quite reluctant to do so. It could cause users to wonder why such a file is present in MediaMonkey installation. Question is, how many users actually need this hack... |
|
Support questions about how to install plugins are fairly common, and a large % of the plug-ins check for such a file. I would suggest adding it to the alphas and if it triggers any problems, then we can remove it. |
|
I don't think it will create problems (well, maybe some antiviruses could complain about zero size executable). Maybe we could at least make it a very small executable that would start MediaMonkey.exe in the same folder. |
|
Sure--that's fine (though I'm not sure if it's really necessary). |
|
There were two reasons: - There won't be an .exe that would be zero size (possible problems?). - After clicking it, MM will be started instead of showing an error message. |
|
Peke, please create a very small executable that will only execute MediaMonkey.exe in the same folder. Store the project in Helpers folder, create a building batch for it at Mp3Datab\Builds folder, file LibBuild_Winamp.bat (see other batched there for an example) and call it from LibBuildAll.bat. (The batch should copy WinAmp.exe to SetupFiles folder. |
|
Done In Build 1492. |
|
Included in build 1004. |
|
Verified 1005. |
|
Reopenning as i noticed that some installations also need fake winamp.ini in MediaMonkey Folder. I wanted to know would it be good that we add this here or as simple empty txt file? Reference Forum post: http://www.mediamonkey.com/forum/viewtopic.php?t=26064&highlight=dfx |
|
Fixed in build 1141. |
|
Verified that an empty file is installed. |
|
User has noticed that winamp.exe is quarantined by Norton, see details here: http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=60132&start=15#p401000 Do we still need winamp.exe be bundled with MM installer? |
|
Unless there is winamp.exe in installation folder than winamp designed plugins in 99% of cases will not allow plugins to install so yes we need to have it with installation. Problem with blank file is that some of installations request winamp start after installation in order to complete it successfully. |
|
OK, what are you suggesting Rusty? Leaving winamp.exe in MM installer and contact Norton about the winamp.exe issue? |
|
I suggest that Peke tests this out and verifies whether it's still an issue. In the past, norton has usually fixed the false positive at their end. Trial version available here: http://us.norton.com/downloads-trial-norton-antivirus If the problem persists I'll contact them again. |
|
No issues on my end using trial version after 7 day of usage, guess they fixed false positive. |
|
Closed False positive on Norton Side |
|
This issue is raised again: http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=82231&start=15#p414497 The user wrote that he uses winamp.exe from an older version of MM. Looking into it the true is that alhought WinAmp.exe from subsequent builds has same size, they are slightly different compared bit by bit. Maybe due to compilation ? So it makes sense to fix this and make the winamp.exe file permanent (bit by bit) and not run re-compilation each time a new build is creating. In addition the one from 1758 is really larger We should make WinAmp.exe file permanent |
|
Fixed in 4.1.9.1763 i.e. made WinAmp.exe permanent (used that one from build 4.1.8.1751) |
|
Verified 1763 |