I changed the location of the DB to the music harddrive (D:\) that is shared on the network. This works on the local PC and also another networked PC was able to make the connection without problems. I even was able to run both MM's on the same DB at the same time (I know someone reported a problem with this).

That's just great.

PS. The songs in the DB are added through the network instead of local path.

For now, this one's documented in the release notes. Our intent is to come up with a more elegant solution for this (i.e. configure this via the UI).

I guess the DBName entry needs to be added to the file as it is non-existent (Beta3)?

Well at least I added it and it works, thanks!!!!

As I replied to the e-mail, the [system] section could look like this in your case:

[System]
CacheDir=d:\music\DBcache\VirtualCD
DBName=d:\music\DBcache\MediaMonkey.mdb

Jiri

No joy. I've sent some screen shots to support@songs-db.com - if that's no longer the right mailbox let me know.

The right setting for database location in the .ini file is 'DBName', thus when you want to move your DB, it should look like:

[System]
DBName=c:\some\path\here\MediaMonkey.mdb

That should work well.

Jiri

I have changed the database location from the default in the MediaMonkey Data subfolder on the C: drive to "CacheDir=D:\Music\DBcache\" but noticed that the change wasn't honoured.

With MM closed, I moved (not copied) the database from the C: drive to it's new home and when next started MM threw up a message saying it couldn't find its database. When I selected cancel MM hung with just a corrupted splash screen showing, but it was possible to close it from the task bar ok. Copying the database files back to their default folder whilst MM was hung disn't achieve anything (no surprise there).

Win XP, 256K RAM, several drives - all music and related files on D: (I hope