I've got debug view working again, but found that as well as using the Connect menu to "Connect Local", I also had to use the Capture menu to "Capture Win32".
Cheers
Matt

Lowlander and Rusty,

Thanks for your responses. Yes I only have one DbgView running. Yes I only invoke DbgView if I have a debug version of MM installed. Yes I know to start DbgView before MM - the instance mentioned above was an anomaly.

I have found one thing that might help - the title bar of DbgView indicated "Not Connected", which could be a basis for the problem. Looking around DbgView I found the "Computer" menu which gave me the option of "Connect Local", so I'll try implementing that with the next MM debug build that I install.

Cheers

One other hint: make sure to launch Debug view _before_ running MMW (and that there aren't any residual MMW processes running beforehand).

-Rusty

Make sure you have the debug version of MediaMonkey installed (reinstall to be sure). Also make sure you don't have multiple instances of DebugView running, as only 1 instance can capture.

Other than that, you can try a PC restart, or launching DebugView as Administrator. It is still working for me on 3036.

Hi,
Have been running DebugView with debug builds for a long time. Before starting MM I start Debug View and then initiate MM, and I can watch all of the loading stuff happen as per usual. Now, Debug View has stopped logging MM activity and I can't get it to start logging again.
As near as I can recall, at one point I did have MM running and then started Debug View. There was a fleeting dialog box about messages from Windows but that disappeared before I could act on it.
I have restarted everthing including Windows to no avail.
Any suggestions?
Matt