1202(Orig 1177): installer error on MMHelper.dll [388]

[chrisjj]

> I'm not sure what MMhelper.dll actually does.

Not convinced by http://www.mediamonkey.com/forum/viewto ... 79#p151079 ?

[chrisjj]

> Re-opened with Feedback.

" Problem showing up again."

To clarify: here it never stopped showing up.

[nohitter151]

> I'm not sure what MMhelper.dll actually does.

Not convinced by http://www.mediamonkey.com/forum/viewto ... 79#p151079 ?

Sorry, wasn't ignoring that - it is certainly viable.

[Dreadlau]

Had the same problem upon installation too with 1202.

[Dreadlau]

Problem is back upon installation with build 1208

[MarineBrat]

I had this on 1208 for the first time in many updates. I did an update in AVG Antivirus which has always unlocked MMHelper.dll in the past. This time it didn't work, which is the first time ever of the 20-30 times I've had this error in the past.

I launched Process Explorer (From SysInternals) and it said that, amazingly, it was Notepad.exe and two instances of Sndvol32.exe that had MMHelper.dll open. I closed Notepad and the two Volume Control windows I had open and all was well.

[chrisjj]

> amazingly, it was Notepad.exe ... that had MMHelper.dll open.

That fits with the theory that the .dll is involed in clipboard data. I wonder if doing CTRL-C in MM is sufficient to cause the problem.

[Dreadlau]

Problem is back in 1215

[Teknojnky]

have not had this in a long time, but I got today with 1217... when I searched for mmhelper with process explorer, it said that excel (2k) had it open, so I closed excel and was able to retry with no further problem.

[nohitter151]

Problem is back in 1215

Sorry, but this "bug" isn't resolvable. See http://www.ventismedia.com/mantis/view.php?id=388

[Dreadlau]

Ok. Thx

[chrisjj]

> but this "bug" isn't resolvable. See http://www.ventismedia.com/mantis/view.php?id=388

I see

This is necessary in order to properly receive Multimedia specific keys from keyboards (like Play/Pause key) when MM isn't the foreground application. The only way how to prevent this is to disable capturing such keys (which isn't a good fix for most users).

. This user would be more that happy with that workaround. Anyone know which option/config will do it?

[MarineBrat]

Just as an aside, this free program called Process Explorer can easily and quickly show which program has a DLL open, and close that connection.

http://technet.microsoft.com/en-us/sysi ... 96653.aspx

Even if you don't use MediaMonkey, or don't have this DLL locking issue, every Windows computer should have Process Explored installed for emergencies.

Steps:
Run ProcessExplorer
Click on "Find/Find handle or DLL (CTL-F)
Type mmhelper.dll

You'll see a list of programs that are interacting with MMHELPER.DLL. You can close those programs and it will release the DLL.

Note that all of this can be done while still sitting at the MediaMonkey install screen, where it says that it can't replace the DLL. Just hit retry.

[chrisjj]

Further info:

1) Process Explorer "Find Handle" reports:

Process PID Type Handle or DLL
DMCFileSelector.exe 2344 DLL C:\Program Files\MediaMonkey\MMHelper.dll

2) Successful workaround: in Task Manager terminate processes (I found two) DMCFileSelector.exe

[chrisjj]

> but this "bug" isn't resolvable. See http://www.ventismedia.com/mantis/view.php?id=388

I see

This is necessary in order to properly receive Multimedia specific keys from keyboards (like Play/Pause key) when MM isn't the foreground application. The only way how to prevent this is to disable capturing such keys (which isn't a good fix for most users).

. This user would be more that happy with that workaround. Anyone know which option/config will do it?

Please?? Or perhaps Jiri's disable is source-only?