Everything you are posting that is not portable is from a script or addon.KyleHx wrote:add'l non-portable entries, after running
[TweakMonkey]
DBName_previous=C:\!apps\MediaMonkey\Portable\MM.DB
Truly portable installation? [#12739]
Moderator: Gurus
-
nohitter151
- Posts: 23640
- Joined: Wed Aug 09, 2006 10:20 am
- Location: NJ, USA
- Contact:
Re: Truly portable installation?
MediaMonkey user since 2006
Need help? Got a suggestion? Can't find something?
Please no PMs in reply to a post. Just reply in the thread.
Need help? Got a suggestion? Can't find something?
Please no PMs in reply to a post. Just reply in the thread.
Re: Truly portable installation?
Gotcha .. I follow up, separately.
Here's something that isn't from a script or add-on: The portable installation works, just fine.
I changed MediaMonkey.ini to point to my old MM.DB with DBName= under [System], and I didn't have to specify the drive letter.
BUT, I tried copying the new MediaMonkey.INI into that same location, and using the /INIFILE command-line option.
That worked, in so far as the db and settings were found and used, but using /INIFILE caused the Windows registry to be used.
I changed nothing there, just moved the .INI and then pointed to it, and the reg-key [HKEY_CURRENT_USER\Software\MediaMonkey] got fully populated.
I've been through it about a dozen times now, deleting the reg-key in between.
The only time that having /INIFILE on the command line didn't cause this was when I ran a test pointing to a non-existant .INI.
MM found the standard .ini (in the standard location) and used it, and didn't populate the registry.
In all other cases, using the/INIFILE parameter causes the portable-MM to write to the registry.
Here's something that isn't from a script or add-on: The portable installation works, just fine.
I changed MediaMonkey.ini to point to my old MM.DB with DBName= under [System], and I didn't have to specify the drive letter.
BUT, I tried copying the new MediaMonkey.INI into that same location, and using the /INIFILE command-line option.
That worked, in so far as the db and settings were found and used, but using /INIFILE caused the Windows registry to be used.
I changed nothing there, just moved the .INI and then pointed to it, and the reg-key [HKEY_CURRENT_USER\Software\MediaMonkey] got fully populated.
I've been through it about a dozen times now, deleting the reg-key in between.
The only time that having /INIFILE on the command line didn't cause this was when I ran a test pointing to a non-existant .INI.
MM found the standard .ini (in the standard location) and used it, and didn't populate the registry.
In all other cases, using the/INIFILE parameter causes the portable-MM to write to the registry.
Re: Truly portable installation?
OK I added it in http://www.ventismedia.com/mantis/view.php?id=12739 so that we can see how to implement it.
Best regards,
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying



How to attach PICTURE/SCREENSHOTS to forum posts
Peke
MediaMonkey Team lead QA/Tech Support guru
Admin of Free MediaMonkey addon Site HappyMonkeying



How to attach PICTURE/SCREENSHOTS to forum posts