Option to keep mm.db and ini files on seperate folder/disk

Get answers about using MediaMonkey 4 for Windows.

Moderator: Gurus

Guebil
Posts: 6
Joined: Mon Jan 28, 2019 5:25 am

Option to keep mm.db and ini files on seperate folder/disk

Post by Guebil »

Would it be possible to have an option to keep the database and ini files in a different place, i.e parameterised ?
I like to keep all data and parameter files in a seperate disk (on a raid array) so that it is easy to restore. I regularly have issues with windows and it would be good to have that option ... that way I could just re-install MM and point it to the seperate fofder and everything would be in place.

Thanks
Lowlander
Posts: 56628
Joined: Sat Sep 06, 2003 5:53 pm
Location: MediaMonkey 5

Re: Option to keep mm.db and ini files on seperate folder/disk

Post by Lowlander »

Database: https://www.mediamonkey.com/support/ind ... e-location

ini: https://www.mediamonkey.com/support/ind ... ediamonkey

or install MediaMonkey as Portable Install on the separate disc.
Guebil
Posts: 6
Joined: Mon Jan 28, 2019 5:25 am

Re: Option to keep mm.db and ini files on seperate folder/disk

Post by Guebil »

Thanks for the quick reply, I will do that.

However, to help me make the best decision for my situation, can I ask what's the difference between a normal and a portable install? i.e. is there any advantages/drawbacks for each options (other that the obvious portability aspect :) )?

Thanks
Lowlander
Posts: 56628
Joined: Sat Sep 06, 2003 5:53 pm
Location: MediaMonkey 5

Re: Option to keep mm.db and ini files on seperate folder/disk

Post by Lowlander »

The Portable Install doesn't integrate with Windows, thus some of the OS Integration, taskbar player and MM service won't be available. Otherwise it is identical and easier to move the whole installation.
Guebil
Posts: 6
Joined: Mon Jan 28, 2019 5:25 am

Re: Option to keep mm.db and ini files on seperate folder/disk

Post by Guebil »

I still think it would be tidier to have an option in the app but I'm happy with the solution, it was simple enough to implement.
Thanks for the quick support, you can close the issue.
Post Reply