by hermes3por3 » Fri Sep 07, 2012 8:10 am
Hi,
I am experiencing the same startup errors (one for each installed script): OLE error 8007000E. I am running MediaMonkey 4.0.6.1501 using Wine in Linux Mint Maya with KDE Desktop.
As explained in
http://www.dbforums.com/microsoft-sql-server/261723-microsoft-ole-db-provider-odbc-drivers-error-8007000e.html, it seems to be related to the way ODBC database connection objects are created (and apparently not properly destroyed, which would create a memory leak that is responsible for those errors) within ASP scripts, which kind of makes sense.
Since the same MediaMonkey version on my Windows 7 and with the same scripts does not raise (or ever raised) those errors on startup, a first guess is that those scripts rely on some automatic garbage collection mechanism that VBS script engine provides in Windows, but maybe not in Wine.
I don't know if this is something related in any way to MediaMonkey itself, to each particular script, the way those scripts are handled within Wine, or how errors are raised, etc. In my case, those errors were presumably raised by Cue Reader and Involved People Node. Removing those extensions also prevented the errors at startup.
As a sidenote, under Wine in Linux I can use MediaMonkey quite well. I have to disable skins and use native windows widgets though. Skinning MM makes the interface considerably slower. Notably there are problems when resizing windows, as if window resize events are triggered differently (kind of sloppier) than under native windows, and all sorts of box sizing and placement problems occur during window resizing. Again, this might not be related to MediaMonkey at all. Using unskinned MM the interface behaves normally.
Hi,
I am experiencing the same startup errors (one for each installed script): OLE error 8007000E. I am running MediaMonkey 4.0.6.1501 using Wine in Linux Mint Maya with KDE Desktop.
As explained in [url]http://www.dbforums.com/microsoft-sql-server/261723-microsoft-ole-db-provider-odbc-drivers-error-8007000e.html[/url], it seems to be related to the way ODBC database connection objects are created (and apparently not properly destroyed, which would create a memory leak that is responsible for those errors) within ASP scripts, which kind of makes sense.
Since the same MediaMonkey version on my Windows 7 and with the same scripts does not raise (or ever raised) those errors on startup, a first guess is that those scripts rely on some automatic garbage collection mechanism that VBS script engine provides in Windows, but maybe not in Wine.
I don't know if this is something related in any way to MediaMonkey itself, to each particular script, the way those scripts are handled within Wine, or how errors are raised, etc. In my case, those errors were presumably raised by Cue Reader and Involved People Node. Removing those extensions also prevented the errors at startup.
As a sidenote, under Wine in Linux I can use MediaMonkey quite well. I have to disable skins and use native windows widgets though. Skinning MM makes the interface considerably slower. Notably there are problems when resizing windows, as if window resize events are triggered differently (kind of sloppier) than under native windows, and all sorts of box sizing and placement problems occur during window resizing. Again, this might not be related to MediaMonkey at all. Using unskinned MM the interface behaves normally.
