by TheAncient » Sun Jul 03, 2016 10:34 am
I'm glad it worked for you. Unfortunately that does not help me.
I am at the point where I am ready to build some sort of batch file to copy one of 3 ini files (one to point to "M", one for \\Server, and one for "D") over top of the existing mediamonkey.ini file. Oh yeah: I also uninstalled and re-installed MediaMonkey but I am still having the same problems.
I also ran into other problems which may or may not be related:
1. If my .ini file contains comments (lines prefixed by a semi-colon) Mediamonkey removes those lines as it re-writes the .ini file when it closes. I find that VERY annoying as I use comments to explain why I chose certain settings and to note alternatives such as different database locations.
2. Teamviewer appears to have a problem with MediaMonkey (or vice versa): If I start MediaMonkey first and then Teamviewer, everything works as expected. If I run Teamviewer first and then try to start Mediamonkey, Mediamonkey will not start. The error message is not informative at all and merely states "Mediamonkey has stopped working". This is only an issue when running the FULL version of Teamviewer. Everything works fine when using the HOST version of Teamviewer (run Teamviewer as a sevice)
I will open separate problems for these two issues - I am just mentioning them here in case they have any bearing on this problem.
I'm glad it worked for you. Unfortunately that does not help me.
I am at the point where I am ready to build some sort of batch file to copy one of 3 ini files (one to point to "M", one for \\Server, and one for "D") over top of the existing mediamonkey.ini file. Oh yeah: I also uninstalled and re-installed MediaMonkey but I am still having the same problems.
I also ran into other problems which may or may not be related:
1. If my .ini file contains comments (lines prefixed by a semi-colon) Mediamonkey removes those lines as it re-writes the .ini file when it closes. I find that VERY annoying as I use comments to explain why I chose certain settings and to note alternatives such as different database locations.
2. Teamviewer appears to have a problem with MediaMonkey (or vice versa): If I start MediaMonkey first and then Teamviewer, everything works as expected. If I run Teamviewer first and then try to start Mediamonkey, Mediamonkey will not start. The error message is not informative at all and merely states "Mediamonkey has stopped working". This is only an issue when running the FULL version of Teamviewer. Everything works fine when using the HOST version of Teamviewer (run Teamviewer as a sevice)
I will open separate problems for these two issues - I am just mentioning them here in case they have any bearing on this problem.