MediaMonkey forum

Simply stating "this happens to me" without any additional information, log, etc. is not helpful. We already know that it happens (do you think we don't believe this is happening, that people are just making this up?), what we need now is more information. I don't see how reminding that we need a log is in the vein of being a "condescending ass". It's more along the lines of "hey, this thread is almost 30 posts long, and people might not be reading every single post, let's make sure people realize we need more info".

I'm sorry that you think Lowlander and I unfit as moderators. But I do wish that you (or anyone who has a problem with one or both of us) would bring these issues to us directly or another moderator.

Onweerwolf wrote:so i'm not sure what a debug log would do

And I tried to do was answer why the log is important based on that statement

Lowlander wrote:if it captures the error

and for that I get insulted

nohitter151 wrote:Simply stating "this happens to me" without any additional information, log, etc. is not helpful. We already know that it happens (do you think we don't believe this is happening, that people are just making this up?), what we need now is more information. I don't see how reminding that we need a log is in the vein of being a "condescending ass". It's more along the lines of "hey, this thread is almost 30 posts long, and people might not be reading every single post, let's make sure people realize we need more info".

And here we go again. I am not pretending that confirming I have this issue is helpful at all. I am just confirming that I have it. It's fine to ask for a debug log once, it's insulting and being an ass to do it three times in a row like Lowlander did. You both continually behave as if you are working at a callcenter that gets calls from all the morons that have no clue as to what they are doing.

I'm sorry that you think Lowlander and I unfit as moderators. But I do wish that you (or anyone who has a problem with one or both of us) would bring these issues to us directly or another moderator.

Yeah, I did once pm one of you with a complaint. No response at all. I'm not wasting my time on that one.

Onweerwolf wrote:
Yeah, I did once pm one of you with a complaint. No response at all. I'm not wasting my time on that one.

Then bring it to Peke (the other moderator) or Rusty, the board admin.

Onweerwolf wrote:You both continually behave as if you are working at a callcenter that gets calls from all the morons that have no clue as to what they are doing.

I will agree with you that Lowlander and I are not perfect. But take a look at the number of posts each of us has, and just try to imagine how much time we spend in these forums. Sometimes it does feel that way, because we see the same posts over and over and over again.

Debug log was just sent for this problem.

It looks like the error appears when MM is trying to load the custom skin, at least that's the last line in the debug log.

The name of the skin i'm using is GrauGrün by DreadM. Not sure if that could be significant, in any case that's the one and I was using it as well the first time this error appeared.

I have to add that i'm noticing another problem which I think I had as well last time this bug occurred.

I have not yet rebooted. I decided to run my backup program first. The software I use for that is called ViceVersa. Part of the backup is mirroring files from the external hard-drive that contains my MM portable install file. When trying to copy files the software gives an error: "cannot open *.* all or part of the path is invalid." These files can be located when using windows explorer and they also work fine. For instance soundfiles are perfectly playable. Rebooting the external drive makes no difference.

I'm pretty sure that after rebooting my computer ViceVersa will not give this error anymore and be able to copy the files again, which i'm going to try in a minute.

I'm not sure if these things are connected but they might be.



edit: just rebooted my system and as expected; both MM & ViceVersa work flawlessly again.

It looks like GrauGrün wasn't updated to a MediaMonkey 4 skin.

Onweerwolf wrote:the software gives an error: "cannot open *.*

Does MediaMonkey run of the portable drive?

It does yes.

Then I wouldn't be surprised if that causes serious issues. If ViceVersa has trouble reading files of it, MediaMonkey may too have this problem.

Right, I would think so too, but then I'm not sure what is causing it. The drive looks to be in perfect condition. It's also not a matter of just a few corrupt files or something either. ViceVersa couldn't backup any of the files at all and after rebooting the system all is perfectly fine again.

The question may be if ViceVersa is causing this (too many i/o??), is MediaMonkey causing this, something else like Security software or worse the drive itself.

ViceVersa very likely isn't causing it since it wasn't running.

I do not run security software. The drive seems to be fine. My guess is that it has something to do with the os (winxp) having been forced in uptime for too long.

Hi all,
99% of Cases with this error is related to Alpha blending not being correctly set by by outdated Graphic Card Driver.
Can you please Upload GPU info using GPU-Z (Upper right corner)

See example of my screenshot where it is clearly shown that I use driver from March 2012 (12.3):

I have been having the same problem for months. Thought my database was corrupted, until I removed the splash and saw the "unable to create image" message, which led me here.

I could not get a debug file as first reboot solved the problem. Video card is a radeon 5770 with latest drivers. Only thing I can contribute to is to confirm that this problem is well alive with latest MM4, be it as an upgrade or a clean install : I completely wiped off MM3, db, scripts, settings and even registry entries before removing the splash and getting there as a result.

Guess this won't help a lot; thought I'd just bump the thread and maybe trigger some more attention to what looks like a pretty big turn down on MM4. I'll make sure to capture a log whenever I revert to MM3 and give MM4 another try.

XP SP3, core i7 on x58 mobo, no firewall or anti virus.

Roger.

Plain WinXP without any Third Party Themes (uxtheme.dll patching)?
Is this happening in XP only, any way to test on some Win Vista/7 PCs?