I even ticked the add context menu items, to see if they'd work as anticipated (adding the option per associated file type).

Looking at the results, it was a success.

(I attempted to monitor an install, and it crashed, so I re-ran another portable install, hence the change of keys, registry modified, with updated path.)

So, can I ask, does everyone with a portable installation experience this issue? Perhaps only on windows7 ultimate (64-bit) perhaps it's cause I'm running a debug install (I like the idea of being able to view logs of activities, and believe that a debug install is the only way to achieve this)..

If this is a consequence of installing MM as a portable, where the program is 'associated' with types, but the OS fails to achieve 'normal behaviour' (because it's associating the files with an UNKNOWN/portable application), can someone please confirm?!

I tried monitoring the registry change to .mp3's (when manually registering them with mm, by choosing the application by browsing... the ONLY way to successfully associate file with MM) but no change was tracked. comparing the 'working file assoication' (mp3/flac, both I've manually registered, and it STICKS, because 're-associate on startup ISN'T checked).

Same issue for me Zephyr. I am running Windows 7 64bit and latest beta build (gold) installed as portable. I have set the file associations though the MM UI, set them through Explorer "Open With", and also through control panel default programs. I have yet to get the file associations to stick to MM with any method. The extensions revert to being unassociated with any app.

Please update if a fix is found for this.

zephyr wrote:OK, I monitored an install of portable MM, using InstallWatch.

I even ticked the add context menu items, to see if they'd work as anticipated (adding the option per associated file type).

Looking at the results, it was a success.

(I attempted to monitor an install, and it crashed, so I re-ran another portable install, hence the change of keys, registry modified, with updated path.)

So, can I ask, does everyone with a portable installation experience this issue? Perhaps only on windows7 ultimate (64-bit) perhaps it's cause I'm running a debug install (I like the idea of being able to view logs of activities, and believe that a debug install is the only way to achieve this)..

If this is a consequence of installing MM as a portable, where the program is 'associated' with types, but the OS fails to achieve 'normal behaviour' (because it's associating the files with an UNKNOWN/portable application), can someone please confirm?!

I tried monitoring the registry change to .mp3's (when manually registering them with mm, by choosing the application by browsing... the ONLY way to successfully associate file with MM) but no change was tracked. comparing the 'working file assoication' (mp3/flac, both I've manually registered, and it STICKS, because 're-associate on startup ISN'T checked).

Especially:
1) To enable OS Integration settings to function in portable mode, register the MediaMonkey elevation COM object, which is used to give MediaMonkey admin rights in cases where changes must be made to the registry (e.g. for file associations):
MediaMonkeyCOM.exe /regserver

So for auto-registration you need to either call 'MediaMonkeyCOM.exe /regserver' or install standard version of MediaMonkey that does this automatically during the install process.

Hello zephyr and Blackcat12 and e.e., this works for me on Win XP SP3:

1.) Start your portable version with these command line parameters: "/elevate /regcomserver" Read the full answer of Peke first in this thread http://www.mediamonkey.com/forum/viewto ... 13#p372160 You will see your file symbols flashing, that's all!
2.) Start your portable version without those command line parameters and set the desired file associations as you normally did.

I don't know, if there are any bad implications, if you elevate your portable installation of MM. In my case if, I have to choose between portable and normal installation, as I have to go through the whole procedure again if I want to re-associate files with another installation. Maybe somebody else can shine a light on this?

e.g. you can install portable to C:/MediaMonkey/ and then regular to C:/Program Files/MediaMonkey/ and files will be associated with the regular version.
You can install regular version again to C:/Program Files/MediaMonkey2/ and this last one will be associated with files.