Yes, you can have mutliple MM versions installed at once.

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.

Hello Zephyr,

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?

re this install command, is there an option to uninstall a comserver (if you want to install another copy)?

can portable and "full" installs exists in relative harmony?

have to lookup the options on changing inis and swapping dbs...

Hi all, many thanks for reminding me of the command to elevate a portable install to enable OS integration... that makes sense.

Unfortunately my new SSD died so it's in Paris hopefully getting replaced and not just repaired, so back to reconfiguring hotkeys etc :( really need some start backing up wherever possible.

thanks again, will update and confirm this resolves when I next do a portable install...

Can these operations be completed on existing installs that haven't been moved? have a few .ini / .db portable installs I'd like to review

Sorry for going off topic

Hello zephyr and Blackcat12 and e.e., this works for me on [b]Win XP SP3[/b]:
[list]1.) Start your portable version with these command line parameters: "/elevate /regcomserver" Read the full answer of Peke first in this thread [url]http://www.mediamonkey.com/forum/viewtopic.php?f=2&t=73213#p372160[/url] 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.[/list]

[i]@Ludek, Lowlander:[/i] I can not find a MediaMonkeyCOM.exe on my System?

HTH

Mikey

Portable version doesn't register automatically anything, see this KB article for details:
http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=153

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.

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.

[quote="zephyr"]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.

[img]http://i.imgur.com/bF9SHWV.png[/img]
(I attempted to monitor an install, and it crashed, so I re-ran another portable install, hence the [i]change[/i] 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).

Any insights most appreciated. Thanks![/quote]

It works for me, but I: http://www.mediamonkey.com/support/index.php?_m=knowledgebase&_a=viewarticle&kbarticleid=153

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.

[img]http://i.imgur.com/bF9SHWV.png[/img]
(I attempted to monitor an install, and it crashed, so I re-ran another portable install, hence the [i]change[/i] 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).

Any insights most appreciated. Thanks!

This is about the issue mentioned by a few users, [url=http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=73864&p=377762#p377762]here[/url] and [url=http://www.mediamonkey.com/forum/viewtopic.php?f=1&t=68165&p=377763#p377763]here[/url]

I don't know when this problem started, but the associate with Mediamonkey option is not working.

If I double-click a file (wav, for example) I have to associate it with a player. I browse for portable MM4, and tell it to always open that file with MM. the association is then made.

I have to do this for each file type.

If I use MM Options (associate with all audio, for example, or if re-associate on startup is ticked) the association is overwritten as follows

[img]http://i.imgur.com/z8KiBAS.png[/img]

Hi, and no unfortunately you are not alone in experiencing these issues.

I thought my issues were due to the portable installl (to c:\apps\mediamonkey, not program files).

Full details [url=http://www.mediamonkey.com/forum/viewtopic.php?f=6&t=73864&p=377762#p377762]here[/url].

If I double click a file and open with MM, it appears to resolve, whilst the MM audio file type association option doesn't seem to work.

Would rather not do an application reinstall, as I've heavily configured my UI, skins, hotkeys, and scripts.

Guess I'll have to try and associate on a file by file basis.

[b]UPDATE:[/b]

I repeated the process, and it appears that mp3's are now correctly associated with MM.
Do I have to do this for each file type (open, and associate)?

I tried using MM options (associate with audio), and I think the associations are being made, but incorrectly.

If I check 'default programs'

[img]http://i.imgur.com/CGQUDew.png[/img]

Instead of seeing 'Media Monkey', I see this
[img]http://i.imgur.com/9CV6Ohv.png[/img]

I've associated audio with VLC for now, until I can find the cause (and cure) of these problems)

hi, I'm also having this issue with my portable install, on windows 7 ultimate 64 bit.

I installed MM to c:\apps\Mediamonkey4

There is no entry for MM in add/removed programs (although there are uninstall entries for some scripts)

MM's file associations aren't sticking.

Example: double-click to open MP3
[img]http://i.imgur.com/VmeFKKZ.png[/img]

associate with MM (listed as a program perhaps only because I've completed this procedure... repeatedly)
[img]http://i.imgur.com/Yx39HLg.png[/img]

Notice file association updates the icon of the files (mp3s)
[img]http://i.imgur.com/YThvuMS.png[/img]

And then immediately returns to previous state of 'unknown'
[img]http://i.imgur.com/JgKxwT1.png[/img]

This is within a second of MM opening and playing the file.

Now, I'm pretty sure this never used to happen.

Can anyone help?!

thanks

:oops: You are right, I just forgot that. I assume, if I want the BETA to be the handler for mp3 and so on, I'd better install the normal MM as portable version then.

Sorry!

You may have done some improper installing at some point. A Portable Install should use the ini in the Portable folder in the install folder instead of the default ini.