beg wrote:Hi Rednroll,
thx for reply, but I am afraid it does not help in my case. I can not use an external HDD since my music is stored on a high end RAID system within the file server. I do not want to replace that high end system by any external hd conected to the fileserver via USB..
Still I need that music and that mm.db also on a hd and/or on a laptop for mobile usage like DJing in different venues.
regards,
B
Sorry, I'm not familiar with the obstacles associated with using networked hard drives.
Here's some general information that I have learned and maybe you can use this info to solve your problem.
1.
MediaMonkey.ini File:
The MediaMonkey.ini file keeps track of all your
preference settings and it also has the ability to define the location of where to look for the MM.DB file. So things like your screen layout, your last views before you shut down MM, and any settings in the Options>Preferences menu get saved in the MediaMonkey.ini file.
To define the location of the MM.DB (database file) Here is the format of the line you need to
ADD to the MediaMonkey.ini file to tell MM where to look for the database file.
Example:
DBName=T:\MediaMonkey\All Users\Application Data\MediaMonkey\MM.DB
Format:
DBName=Drive Letter:\Drive Path\FileName.DB
If you want MM to look at a network drive for the database file, then I imagine you need to enter the network path. I'm not sure what you have to do, or if it's possible if the network drive needs a login/password to access it.
The thing to be careful about is that the MediaMonkey.exe seems to be programmed to look at multiple locations on your Hard drives for the MediaMonkey.ini file. I'm not sure where it looks 1st, then 2nd...etc. So be sure to make sure ALL other instances are deleted off of your PC to ensure it is running the correct MediaMonkey.ini file when you 1st start up MediaMonkey.exe. It helps to do an Windows "advanced" file search on "MediaMonkey.ini" and make sure to "Show hidden files". I found out the hard way that MM, will create "hidden" instances of the MediaMonkey.ini file. It seems to me the "Last" place MM looks for the MediaMonkey.ini is in it's own install directory. So that's where I keep my MediaMonkey.ini file. So it will always run that INI file as long as no other MediaMonkey.ini are located in other directories on the Windows install HDD, like the specific user folders they some times bury themselves in.(ie "\All Users", "\MyDocuments"..etc.)
So that's what I mentioned earlier is that you could actually have 2 MM install folders on the same HDD and put a separate MediaMonkey.ini file in each separate install folder, so you could have each MediaMonkey.exe access different database files on the same PC....same HDD...etc. by
defining the location of the MM.DB file in the separate MediaMonkey.ini files. Where MM looks for the MM.DB (database) file is not called out by default in the INI file, so you have to ADD a line to the INI file.
2.
MM.DB (The Database File.)
This file stores the location of your music files, your "Library"and ANY changes to your music files you do "within" MM. So if you ADD music files this information gets updated in the DB. So if you add music files on one PC to your library, they will show up in the "library" node in MM, but if you open a different DB file on another PC these files will not automatically show up even though they may physically be on a particular HDD because that "library" information has not been updated with that particular information. So if you EVER have to "move" music files to different HDD's it's always best to move them by using the MM Explorer view and not "Windows" explorer, since the MM DB file will not keep track of the changes you make outside of MM. Now with that said....there is a "preference" setting within MM where you can set it to automatically "scan" certain defined folders. So when you 1st run MM, MM will "rescan" those defined folders and then update the DB file with any changes they may have occurred.
The MM.DB file also contains the playlists that show up in the Playlist node. One thing that I like to do is to create a playlist with nothing in it called "Test_Playlist" on one PC. Then to ensure MM is truly looking at that same MM.DB database file, I make sure that particular Playlist shows up on the other PC I'm running MM on. Same Playlist view=Same Database.
3. The Windows Registry.
As far as I can tell, the only thing that MM looks for on a particular PC in regards to the Windows Registry is the MM registration info. So if you enter your MM "GOLD" key, that information will be saved into that particular PC's Windows Registry. So as long as you enter that info in once on a particular PC, MM will start up in the "Gold" version....no matter which MediaMonkey.exe you run on that particular PC. If that information isn't written to the Windows Registry, then MM will start in the non gold version mode.