View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0019200 | MMW 5 | Install/Config | public | 2022-06-20 23:22 | 2022-10-13 21:40 |
| Reporter | peke | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Target Version | 5.0.4 | ||||
| Summary | 0019200: Multiple instances of MM are not allowed in most cases | ||||
| Description | Multiple instances of MM are not allowed in most cases. Create two portable installs of MM5 in two separate folders. 1. Start first portable and set it to allow multiple instances 2. Start Second (different folder) and it can't be opened. 3. Close first instance 4. Start second portable and set it to allow multiple instances 5. Close second Instance 6. Start first 7. Start second Expected behavior that Allow only one MM is only affected by starting same MM from Same MM path and not instance that is started from different path. eg. when only single instance is enabled then: - Multiple portable c:\MMtemp1\MediaMonkey.exe are not allowed - Portable c:\MMtemp1\MediaMonkey.exe and c:\MMtemp2\MediaMonkey.exe should be allowed - Non Portable c:\MMtemp1\MediaMonkey.exe and c:\MMtemp2\MediaMonkey.exe should not be allowed as they share same DB and settings and considered same app. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
I am not sure what's expected here, AFAIK and AFAIR the 'Allow just one instance of MediaMonkey' always allowed just one instance of MM no matter where the MM instance was installed. i.e. it does not matter whether they are two different portable installs or a single install. Assigned to Rusty to triage/feedback. |
|
|
I think that the current behavior is logical/expected. Resolving as no change required. |
