Note that this service isn't needed to run d_WMDM plug-in, it just runs correctly out of the box. What happens in your case is probably some kind of conflict that's caused by installation of the Windows Mobile services. We'll try to find out more, but I don't know whether we can do anything about it.

Jiri

Sure, but i did not think i had to install Windows Mobile Device Center 6.1 and run those 2 services to use the wmdm-plugin :-?

[quote="surfer"]But then i would not be able to use this plugin, would i?[/quote]Then the services aren't unused.[quote="surfer"]and having to run 2 more unused services.[/quote]

[quote="Lowlander"]Then changing d_WMDM.dll to d_WMDM.dll.off should allow you to not run those services.[/quote]
But then i would not be able to use this plugin, would i?

Then changing d_WMDM.dll to d_WMDM.dll.off should allow you to not run those services.

[quote="pleglise"]So ? Did that work for you ?[/quote]Yes, it seems so. After activating the 2 services of "windows mobile connections" MM i have not had this sort of "hanging" as described above any more...as yet.
The drawback is to have had to install "Windows Mobile Device Center 6.1" and having to run 2 more unused services.
thanks a lot once more for the valuable hint!

So ?
Did that work for you ?

I'm pretty sure it's related. in d_WMDM.dll, WMDM stands for Windows Media Device Manager. And one of the purpose of the service WcesCom is to handle Media connectivity.

PY

thanks a lot for your hint. i've actually had this service stopped as well and have just activated it to see if it helps.

@developers: do you think the isue could in fact be in some way related to that?

I had the same problem with different version of MM... (3 or 4, whatever).
I finally end up with the solution after lot's of hours of hard work...

The problem, (for me) was [u]solved [/u]with the correct setting of the WcesComm service (used for Windows Mobile 2003 connectivity). I recently disabled this service because I don't use it... Big mistake. I know now that it's usefull for d_wmdm.dll to work correctly.

So if you have the same trouble (MM won't stop correctly and debug log looping on "WMDM: Waiting for queued actions to terminate", then just go into the service manager, set the service "Windows Mobile 2003 connectivity" or WcesComm (I don't know how it's called in english) to "Automatic" and start it. It should work ok.

Cheers.
PY
PS : excuse my poor English, it's not my natural langage.

Debug logs in DBGView don't require crashes.

Ok I'll try to generate it but the problem is that the program doesn't crash it simply doesn't close...
When I click on the X (or i choose file->close) it only reduces in taskbar and doesn't close so i have to terminate it by taskmanager.

Debug log send to support would be helpful: http://www.mediamonkey.com/forum/viewtopic.php?f=7&t=69

Problem NOT solved
I can't close mediamonkey 4, the task and the icon on the taskbar are still active and i must kill the process in task manager.
But doing this the prog doesn't save any customization so it's useless.
I'm a gold user and i love MM but i think i'll switch soon to another program :(

Windows 7 pro 64bit, dual screen configuration if can help

bye

This could be related to Windows Media redistributables, which were available online in the past. However, you shouldn't need them for Win 7 anyway, so I'm not sure...

Jiri

I'm not sure any more if it was the same in mm3, but i think so.

What could i try to do to resolve the issue in windows? Would you have any hint?
I do not risk anything, i have backups of my system-partition in an image.