1183 - Fails to load, stuck at splash screen

bob61 · Post by **bob61** » Fri Jun 06, 2008 11:47 am

1) Make sure that you're using the most recent build - Done, load of latest version has caused me the problem.

2) Be specific in your description of the problem and clearly describe the steps needed to reproduce the problem Installed latest version, launched MM3 and stuck at splash screen

3) Provide detailed information about your environment. e.g.
WinXP SP2, P3 256MB, 1 CDR, 1 DVD reader, 1 HD (C:/), MediaMonkey 3.0.0.1014, MAD plug-in enabled Nothing exotic, WinXP SP2, have had no problem previously with MM3

4) Send us a debug log to help us pinpoint the problem (you need to be using a debug build to do so e.g. MediaMonkey_xxxx_debug.exe): Done - MM3 actually created 4 different debug logs, all were sent[/b]

bob61 · Post by **bob61** » Fri Jun 06, 2008 3:43 pm

Problem was tracked to script, MagicNode 1.7.6. When I removed this script MM3 loads properly.

Guest · Post by **Guest** » Sat Jun 07, 2008 2:01 pm

I got the same hang problem today after a new install on a new computer (XP). Downgraded to the current release version and everything started up correctly. Might try an ugrade to the beta again when I've finished organising my files.
G.

bob61 · Post by **bob61** » Sun Jun 08, 2008 9:46 pm

Problem with MagicNodes (thanks to the ZvezdanD) is due to corrupt MM.DB database file. Now, MM3 isn't having any problem but according to ZvezdanD

"Your database file is corrupted - I get the error message "database disk image is mallformed" with many MN nodes. Maybe this database currently have a problem only with Magic Nodes, but latter will be much worse even with MM itself. You could try File/Maintain Library/Compact database, but I doubt you would have any luck with this - I already tried it with your database without success (I got the mentioned error message). You could try to restore the database file if you have some older backup. But if you don't have it, you are really out of luck - you should rescan your library and start to build database from the same begin.

The MagicNodes uses MM's ini file to store the "node" last checked and loads that when MM3 starts up. The "node" was encountering a problem due to the corrupt database.

What's left now is to go back through my .db back-ups and determine which is not corrupt, but not sure how to do that since there are no errors reported by MM3 with any problem using the database.