View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0001233 | MMW v4 | Install/Config | public | 2004-04-09 17:57 | 2007-03-28 22:13 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | major | Reproducibility | always |
| Status | resolved | Resolution | no change required | ||
| Summary | 0001233: Validate plugin compatibility with Vista | ||||
| Description | MediaMonkey users that don't have administrative rights often are unable to save plugin configurations depending on how permissions are set up for the \Program Files\MediaMonkey folder. This can be very frustrating, especially since there are no error messages indicating the fact that the .ini file isn't saved. This can be fixed by moving to an alternative plugin format, but in the 3.0 timeframe, we need to validate whether some plugins can be used with Vista, and determine an appropriate action plan. | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
|
|
This is likely to become an issue with Vista, given that it enforces the use of non-admin accounts. --> We need to decide how to deal with this for 3.0. |
|
|
Problem is that we can't fix it - if a WinAmp plug-in wants to store something in MM folder, we can't prevent it. Our plug-ins or scripts don't have this problem, they use either our ini file (stored in App folders) or registry. |
|
|
Testing reveals that: -directsound output plugin writes to MediaMonkey.ini in the /MediaMonkey folder -musepack.ini, in_ape.ini, plugin.in (defx)i, milkdrop_config.ini write to the /MediaMonkey/Plugins folder I'm leaving this bug open to validate whether the musepack input plugin, ape input plugin, and defx input plugin are compatible with Vista. I'm opening 2 other bugs in relation to the output plugin and milkdrop. |
|
|
Setting to 'resolved' to trigger testing. |
