Then the debug thing did work. The developers will look at the log to see if the problem can be found.

Debug is not working for me because the report I sent was responded to by support and he said "
[b]"We're not able to replicate the problem, but might be able to fix it if you send us a debug log."[/b]
He asked me to use DebugView - the file I got was very large from DebugView - loaded it to http://www.mediafire.com - and added the link to the ticket created (new ticket). DebugView never seams to stop - keeps logging and the resultant file is a large one - I uploaded.

The MM debug also can't go past one report it keeps generating - I have sent it many times but it still keeps popping up - very annoying!!! I sent both report to MM team.

R

How does the debug thing not work for you?

The debug thing don't work for me.

Just discovered something - I connected my old iPhone 3GS and MM did not close - worked, connected 4S and it closed. Could it have something to do with my 4S?
Please don't send me to apple!!!

Rctechy4

Lowlander wrote:Send a debug log (step 4b) to support capturing the crash: http://www.mediamonkey.com/forum/viewto ... ?f=12&t=69

Still stands.

MM Crushed
I have searched the forum and cant find an answer to this. This topic also ended with no guide on how it was resolved.

I have MM 4.1.1.1703 Gold. Been working fine. But now when I connect my iPhone 4S to MM shuts down.
When I start MM with iPhone connected - it starts and then shuts down. Very frustrating!!

Used the debug MM version and kept getting a report that kept popping up even I after I send it, cant go past that debug report - reporting another issue.

Windows Vista SP2
MM 4.1.1.1703 (latest as of today 27.04.14).

Any ideas or just point me to the forum where it has been resolved.

Aha, Lowlander, that is very interesting, that it is still loaded by MM! For 3 years I've been running MM with that dll.
No wonder it crashes a lot!
Thanks for your help today on this. I wouldn't have figured it out without that Debug version of MM.
Lori

As you only renamed the file it is still loaded by MM, worse yet it probably is an old copy of the dll and thus may cause problems. When renaming dll's one should change the extension instead like d_iphone.dll.off as that way it won't be loaded anymore by MM.

I removed the .dll file and I am happy to report that I can now use MediaMonkey with my iPhone connected.
My next step is to sync my music, but I'm going to say the problem is solved and I will leave this posted in case it can help anyone else.

In setting up for the debug log, and running MM with Debugger, I may have stumbled upon something.
A few years ago when MediaMonkey wouldn't work with my iPod Touch, I believe I changed a name of a .dll file, as recommended on a forum, and it helped. Now I am wondering if that has come back to haunt me....
When I run MM with Debugger, message says error is at module d_iPhone renaming.dll. I think maybe I had renamed my d_iPhone.dll to d_iPhone renaming.dll. I can't remember. This file is dated 2009, whereas most files in my Mediamonkey plugins folder are dated 11/12/2012 and 12/23/2011.

Is d_iPhone renaming.dll a valid file?
Should I delete it???

Many thanks...I feel I'm getting closer!

Send a debug log (step 4b) to support capturing the crash: http://www.mediamonkey.com/forum/viewto ... ?f=12&t=69

Hi,

I've been using MediaMonkey for many years to tag my music library. I would like to use it to sync music on my iPhone as well, but MM ends (crashes?) the second my iPhone is connected.

Before I had the iPhone, I had an iPod Touch, and ran into the same problem with that device.

I should add that MediaMonkey frequently "hangs" on my computer, even with no device attached, leaving me to end the task via the task manager. I'd say this happens maybe one out of every 5 times I use it.

When I connect my iPhone, the program simply ends...closes...is no longer on my screen or in task manager.

I have the latest version of MediaMonkey, iTunes, and iPhone software. I am using Windows Vista on a Sony Vaio laptop.

I will happily provide error reports and logs, if that is the way to proceed. I see there is a FAQ dated 7/2002 that explains how to report a bug - does that same procedure still apply?

Many thanks!
Lori