Restart opens with default db instead of specified portable db [#18429]

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: Restart opens with default db instead of specified portable db [#18429]

Re: Restart opens with default db instead of specified portable db [#18429]

by Blackcat12 » Sun Nov 28, 2021 9:29 am

Re: Restart opens with default db instead of specified portable db [#18429]

by Peke » Sat Nov 27, 2021 3:51 pm

Hi,
I am unable to reproduce on newer builds INI files parsed in /INIFILE taht contained custom DB Location loads taht DB instead of default one.

Re: Restart opens with default db instead of specified portable db [#18429]

by Blackcat12 » Sat Nov 27, 2021 9:20 am

I will get a debug file later this week and open a new incident. This should be fairly easy to reproduce as Peke was able to earlier. You just need to make sure that your default DB is very different than your custom DB so that the distinction is obvious when MM5 restarts. For me, the default DB is empty and my full library is in my custom.

Re: Restart opens with default db instead of specified portable db [#18429]

by PetrCBR » Fri Nov 26, 2021 1:55 pm

That's what i meant ... for me correct ini file is used after skin change (defined by INIFILE parameter). Can you make me a debuglog so i can see why INIFILE parameter wasn't used after skin change ?

Re: Restart opens with default db instead of specified portable db [#18429]

by Blackcat12 » Fri Nov 26, 2021 12:29 pm

I think you are misunderstanding the issue. There is no issue with preserving the /inifile.

1. Open MM5 with a /inifile directive to a custom DB
2. Change something in MM5 that will prompt for a restart after the change, such as an addon update or change the skin.
3. When MM5 restarts, it is opening with the default DB instead of opening with reference to the original custom db that was initially opened.

I just did it again by changing the skin. I have to close MM5 and reopen again using the original shortcut or command line with reference to the inifile.

Re: Restart opens with default db instead of specified portable db [#18429]

by PetrCBR » Fri Nov 26, 2021 12:18 pm

Just tried on 2523 and /INIFILE parameter is preserved correctly ... can you make me a debuglog, please ?

Re: Restart opens with default db instead of specified portable db [#18429]

by Blackcat12 » Fri Nov 26, 2021 9:07 am

Hi Team,
This issue has regressed and is present again in build 2523.

Re: Restart does not open with default db instead of specified portable db

by Peke » Fri Oct 15, 2021 10:54 am

Restart opens with default db instead of specified portable db [#18429]

by Blackcat12 » Fri Oct 15, 2021 9:51 am

I have specific DB's mentioned in my ini files (Local /External /Mobile) and open MM5 with the /INI directive. When I change something like the Skin or an Addon, MM5 requests to restart. When MM5 restarts, it is opening with the default db rather than the one that was in use when the restart was triggered. I have to close MM5 again and restart a second time by using my shortcut with the ini directive.

Top