beta 4 -- wont keep dbname= setting

Post a reply

Smilies
:D :) :( :o :-? 8) :lol: :x :P :oops: :cry: :evil: :roll: :wink:
BBCode is ON
[img] is ON
[url] is ON
Smilies are ON
Topic review
   

Expand view Topic review: beta 4 -- wont keep dbname= setting

by KEP » Tue Oct 16, 2007 7:38 pm

Good response, Teknojnky. I could support that position. Especially the manual importation of old settings! I've already missed that, myself. But I'm attuned to not thinking of myself as a "normal" user of much, so I tend to discount my own wishes when my developer-self does the thinking. <g>

by Teknojnky » Tue Oct 16, 2007 4:41 pm

RE: the default installation folder

I disagree because it is those very people who will have problems and not be able to solve it on their own, necessitating a meriad of forum posts and/or support emails, thus causing a potentially larger and more time consuming situation than would occur if mm2 and mm3 could completely peacefully co-exist (and if mm3 gave the manual option to import mm2 settings/database besides install that would be swell too).

If the default mm3 install is to overwrite the mm2 files, then the users have no way to recover easily (if they did not back up the program folder on their own).

Re: beta 4 -- wont keep dbname= setting

by KEP » Tue Oct 16, 2007 4:36 pm

Teknojnky wrote:

Code: Select all

[System]
DBName=j:\program files\mediamonkey3\MyMediaMonkey3.db
and creates a new one in the documents and settings\user\local data\mediamonkey, much to my frustration.
Probably because Vista doesn't allow non-admins write access to %programfiles%, and UAC (if enabled) may even throw-up stupid dialogs on every write access even for admins. Still, a user ought to be able to override such shortsighted limitations.
Teknojnky wrote:Also, I completely disagree with this change back to the default installation folder. MM 2 and MM 3 should always be separate so that a user can properly migrate without fear of losing any existing settings etc.
Agreed, but the change doesn't prevent that. Like with most apps, it shields that option from those who may not want or otherwise be able to cope with multiple installs.

by Teknojnky » Tue Oct 16, 2007 2:16 pm

seems to be working again in 1091

thanks!

by ZPrime » Tue Oct 16, 2007 12:30 am

Odd. It isn't REMOVING my line from the mediamonkey.ini, but it does seem to be ignoring it and using a "mm.db" that it creates in Local Settings. (Actually, c:\users\[person]\appdata\local as I'm on Vista.)

It's as though the code that checks the application's directory isn't working.

I just signed up for lifetime gold since MM is working with the new iPod Classic and 3gen Nano... I got sick of screwing around with foobar2000's config that makes my head hurt. :)

Related to this -- should the DBName variable take a UNC path?

by PetrCBR » Mon Oct 15, 2007 5:19 pm

Thanks. This will be fixed in next release.

by JrVtecAccord » Mon Oct 15, 2007 2:33 pm

Err, I am having this problem as well. I have my .ini file in the program folder instead of the default because of multiple users on a single pc and the db is on a network drive.

Never had any problems with any other Alphas or Betas regarding this issue.

by Teknojnky » Mon Oct 15, 2007 8:34 am

It is a 'shared' mediamonkey.ini in the main mediamonkey3 folder.

I keep all of my stuff on an external drive, so for me I want to keep all settings and data there, and NOT in documents and settings.

by PetrCBR » Mon Oct 15, 2007 5:52 am

Where you have stored your MM.ini file ?

by Teknojnky » Sun Oct 14, 2007 9:45 pm

If I copy/rename file to

C:\Documents and Settings\User\Local Settings\Application Data\MediaMonkey\mm.db

Then it works fine, however that is simply not acceptable to me.

beta 4 -- wont keep dbname= setting

by Teknojnky » Sun Oct 14, 2007 8:53 pm

I have a 'shared' mediamonkey.ini, a specifed database file, and a whole separate folder for mm3.

I want to keep it this way.

Every time I try to start beta 4, it removes my specified db in the mediamonkey.ini

Code: Select all

[System]
DBName=j:\program files\mediamonkey3\MyMediaMonkey3.db
and creates a new one in the documents and settings\user\local data\mediamonkey, much to my frustration.

Also, I completely disagree with this change back to the default installation folder. MM 2 and MM 3 should always be separate so that a user can properly migrate without fear of losing any existing settings etc.

Top