nanite2000 wrote:

Lowlander wrote:It has been reported: http://www.ventismedia.com/mantis/view.php?id=9423

Awesome. Thanks!

Has it been solved now ?

Lowlander wrote:It has been reported: http://www.ventismedia.com/mantis/view.php?id=9423

Awesome. Thanks!

It has been reported: http://www.ventismedia.com/mantis/view.php?id=9423

Lowlander wrote:Was it a clean install?

Hi,

Yes - it as a clean install. MediaMonkey had never been installed on that particular machine before.

Do we agree that this is a bug? If so, I'll report it.

I just checked my ini file and I too had the virtual cd and preview directories set as c:\
This was easily rectified by changing the directories to use relative paths within Options\Library\Virtual CD & Preview
However I also noticed that the temp dir was also set for an absolute path and after changing it to relative it reverts back to absolute on MM close
Not sure what ramifications this would have on a truly portable set-up (which mine isn't)
PS This was a clean portable install but quite a few versions ago

Was it a clean install?

Hi,

I installed MediaMonkey v4.0.3.1476 to an external hard drive.

The portable install seems to rely entirely on the portable drive being allocated the same drive letter on every machine to which it is connected. This breaks the first rule of portable drives - you cannot ever rely on it being allocated the same drive letter every time you plug it in.

For example - I originally installed it on a drive that was allocated the letter 'F:'.

I unplugged it and plugged it into another PC where it was allocated the drive letter 'E:'. Here is the list of error messages I received when I tried to start up MediaMonkey from the portable drive:

"Access violation at address 004ADF53 in module 'MediaMonkey.exe'. Read of address 0000006C."
"The directory F:\Music\MMPortable\Portable\VirtualCD\ cannot be created"
"The directory F:\Music\MMPortable\Portable\Previews\ cannot be created"

If I force Windows to allocate the drive letter 'F:', then it works fine.

MediaMonkey should be checking relative paths, not absolute paths.

Thoughts?