Database and ini locations

[DM-UK]

Is there any particular reason that the Database and ini files are now in Local Settings rather than My Documents?

Local Settings does not get written back to the server with roaming profiles, so all changes are lost at logout. Is is possible to use the old locations still while remembering that when a users logs in local settings WILL BE EMPTY.

Sure %Username%\Application Data would be a good idea, %Username%\Local Settings\Application Data is not such a good place for data that is permanantly kept.

[nynaevelan]

You can change the default location of the db and ini files, see here.

Nyn

[DM-UK]

The ini file cannot be used because the Location Local Settings\Media Monkey DOES NOT EXIST when a user logs in with a roaming profile.

[DM-UK]

Hmm, or is it doing a one time only change to the odbc location? In which case I'll have a go

[DM-UK]

No it doesn't work. It always looks for the ini in local settings, so it worked once, but not after the local settings\mediamonkey.ini file was lost on logout.

[nohitter151]

No it doesn't work. It always looks for the ini in local settings, so it worked once, but not after the local settings\mediamonkey.ini file was lost on logout.

Move MediaMonkey.ini to the Program Files\MediaMonkey\ folder

[DM-UK]

No it doesn't work. It always looks for the ini in local settings, so it worked once, but not after the local settings\mediamonkey.ini file was lost on logout.

Move MediaMonkey.ini to the Program Files\MediaMonkey\ folder

Well that works as a temporary fix for the primary user, but it's no good if more than one user uses the machine, which is highly likely with roaming profiles. It's just annoying because it works perfectly with 2.5. There really should be a search for the ini the non local setting appdata first.

[nynaevelan]

If you move the db and ini files to the mediamonkey folder, why is this not ideal for all users??

Nyn

[DM-UK]

If you move the db and ini files to the mediamonkey folder, why is this not ideal for all users??

Nyn

They are private databases for each user. The old settings allowed users with a roaming profile to have their settings stored in a redirected folder, My Documents. User logs into any machine on the network and has their MM settings. Now this is not possible because of the reliance of reading the ini from a location that cannot be used for multiple different users.

2.5

User1: \\server\share\My Documents\My Music\MediaMonkey\user1s.mdb
User2: \\server\share\My Documents\My Music\MediaMonkey\user2s.mdb

User can login to any machine and always have their db.

3.0

User1: %UserProfile%\Local Settings\MediaMonkey\User1.mdb. Folder is deleted on logout with roaming profiles

Fix with %ProgramFiles%\MediaMonkey\MediaMonkey.ini
User1: \\server\share\My Documents\My Music\MediaMonkey\user1s.db
User2: Cannot change ini in %ProgramFiles% so unable to use MM

User can no longer move machine and no other users can use MM on the machine that the "fix" is in place.

This can simply be fixed by reading from %UserProfile%\Application Data first and not %UserProfile%\Local Settings\Application Data

[nynaevelan]

Ahh, now I understand. I am not that familiar with roaming but there is a Roaming directory in the username\appdata\ folder. Is this the same thing??

Nyn

[DM-UK]

Ahh, now I understand. I am not that familiar with roaming but there is a Roaming directory in the username\appdata\ folder. Is this the same thing??

Nyn

Not quite

With a roaming profile:

Appdata is copied to/from the server when the user logs in/out.

Local Settings\Appdata can also contain application data, but it used for larger files that do not need to be kept between machines. Local Settings is one of the excluded folders when copying a roaming profile, so it's contents will never be copied to/from the server.

Not having a large db file copied at login is a good idea, but not if the only way to configure it's location is in a folder excluded from ever being written to the server! Program files is normally locked to users to, but as this is a small home network the temporary fix will get the primary user working for now.

So at minimum you really need to look for a config file in userprofile\appdata before checking the local settings\appdata. Local settings, which is at best machine specific and at worst deleted whenever the user logs out.

[nynaevelan]

So then for you, you can move the ini and db files to the My Documents folder as they were in v2.5. Would this work to meet your needs? There was a discussion, I think in the Beta forum quite some while ago about why the files were moved. I'm sure if you search you will find many topics on the matter. Sorry I could not be of more help to you.

Out of curiosity do you have alot of roaming, is this a home network and if so why is the user roaming rather than using his/her own machine?

Nyn

[DM-UK]

So then for you, you can move the ini and db files to the My Documents folder as they were in v2.5. Would this work to meet your needs? There was a discussion, I think in the Beta forum quite some while ago about why the files were moved. I'm sure if you search you will find many topics on the matter. Sorry I could not be of more help to you.

Out of curiosity do you have alot of roaming, is this a home network and if so why is the user roaming rather than using his/her own machine?

Nyn

I can only use the ini in Program Files to point to a single users DB file in their user area, but this will be wrong if another users logs in. It also only works for that machine. I'm using roaming profiles so settings are consistant when users switch to laptops etc. From a network compatability point of view it's quite a step back as for 2.5 to work I had to do nothing, and now I have to fudge it to get single users partially working on selected machines.

I should think the files were moved to meet vista logo requirements, but for keeping settings between machines is exactly the reason why there is a distinction between appdata and local settings\appdata folder.

[Bex]

You have a point here, I added this to Mantis:
http://www.ventismedia.com/mantis/view.php?id=5040