View Issue Details
| ID | Project | Category | View Status | Date Submitted | Last Update |
|---|---|---|---|---|---|
| 0002642 | MMW v4 | Install/Config | public | 2006-09-10 19:50 | 2008-03-06 19:02 |
| Reporter | rusty | Assigned To | |||
| Priority | urgent | Severity | minor | Reproducibility | always |
| Status | feedback | Resolution | open | ||
| Summary | 0002642: Serial number must be entered by each user instead of once per machine | ||||
| Description | If a user installs MM and enters a serial number, MM should be registered for all users on the machine. | ||||
| Additional Information | AVQ Requirement | ||||
| Tags | No tags attached. | ||||
| Fixed in build | |||||
| related to | 0001420 | assigned | jiri | MMW v4 | Support multi-user installs and installs with configs saved to OEM directory |
| related to | 0003399 | closed | jiri | MMW v4 | Install MM3 to Program Files\MediaMonkey3\ -- Revert |
| related to | 0004497 | closed | Ludek | AAC / Video codec plugin | f_aac_codec: Encode settings cannot be changed on non-admin account and some systems |
| related to | 0004529 | closed | Ludek | AAC / Video codec plugin | f_aac_codec: Non-admin users cannot use this AAC add-on |
|
|
We can change this, but I wonder whether other applications do this as well. I'm not sure, but it seems quite logical that the app would be registered only for a specific user. |
|
|
I'm not sure--if it's installed to a single machine, I would expect that any user on that machine should be able to use it (since only one user will be at the machine at a time). As an example, when I install MS Office software, it is registered for all users on the machine. |
|
|
It's actually related to how MM is installed. Currently (as already discussed in other issues) MM is installed per user, all settings are saved this way and so I don't think it makes sense to save registration information differently. If we want to do so, we probably should include the choices - install 'per user' or 'for all users' in the installer. |
|
|
Per discussion it would make sense to be inconsistent in this case. i.e. to save registration data on a per machine basis, but to save user config data on a per user basis. |
|
|
Note: Per machine registrations make big Problems when MM user wants to use MM on Work Computer and want to have access to GOLD Feature. Solution would be that we use HKEY_LOCAL_MACHINE instead of HKEY_CURRENT_USER we currently use in registry. That is how Office works. |
