by davidb » Sun Feb 06, 2022 3:17 pm
I have MM4 as a Portable installation on SSD. I opened after a very long time and it prompted for upgrade to MM5, which I did, as a Portable installation beside my MM4. It was a fail. Ultimately, I ended up removing it. But here are issues and needed refinements I found. This is all for a Portable installation, Windows10 - Home.
1. When installing, under Browse to select folder, there's no guidance as to whether the old MediaMonkey folder should be selected, or the Directory containing the old MediaMonkey folder, if I wanted to retain MM4. BTW, it should be the latter, so as to keep the two installations pure.
2. The MM4 database, MM.DB, was not visible to MM5, so I copied mm.db from MediaMonkey4, and pasted it into the Portable Folder as mm.db, as Wiki-Instructs, and renamed the mm.db5 file to mm.db5.bak.
3. I opened MM5 and it pulled the music list in. Yet when I went to play (anything), it went into a super-rapid scroll through the database, returning error message boxes with each song title, saying it wasn't playable, hen auto-scrolled to the next.
4. At some point, I gave up trying to work it out and decided to start over. But I could not find an Uninstall program, nor simply delete the files or folder. When the Delete command hit any executable (*.exe), it returned an error asking for Administrator privilege, even when I ran File Explorer under "Run as Administrator."
5. I tried overwriting the installation with a new installation. But it failed when the new install installation hit any .exe file. It tried to rename th e.exe files rather than delete or overwrite them, and couldn't, for the same "Administrator" privilege problem.
6. Under Windows10 - Home, no "Security" tab exists to claim the Administrator permission. Also, I couldn't claim ownership.
7. To resolve, I had to go Command prompt and enable the Administrator Account through, "net user administrator /active:yes". This gave me the capability finally, to remove the entire MM5 installation. Then to close the security vulnerability this Command Prompt action might have created, I returned the system to back to its default of, "net user administrator /active:no".
I don't know what happened on my MM5 installation, but at minimum, I didn't see the instruction, support and guidance necessary for me to trust MM5 is ready for prime time.
I have MM4 as a Portable installation on SSD. I opened after a very long time and it prompted for upgrade to MM5, which I did, as a Portable installation beside my MM4. It was a fail. Ultimately, I ended up removing it. But here are issues and needed refinements I found. This is all for a Portable installation, Windows10 - Home.
1. When installing, under Browse to select folder, there's no guidance as to whether the old MediaMonkey folder should be selected, or the Directory containing the old MediaMonkey folder, if I wanted to retain MM4. BTW, it should be the latter, so as to keep the two installations pure.
2. The MM4 database, MM.DB, was not visible to MM5, so I copied mm.db from MediaMonkey4, and pasted it into the Portable Folder as mm.db, as Wiki-Instructs, and renamed the mm.db5 file to mm.db5.bak.
3. I opened MM5 and it pulled the music list in. Yet when I went to play (anything), it went into a super-rapid scroll through the database, returning error message boxes with each song title, saying it wasn't playable, hen auto-scrolled to the next.
4. At some point, I gave up trying to work it out and decided to start over. But I could not find an Uninstall program, nor simply delete the files or folder. When the Delete command hit any executable (*.exe), it returned an error asking for Administrator privilege, even when I ran File Explorer under "Run as Administrator."
5. I tried overwriting the installation with a new installation. But it failed when the new install installation hit any .exe file. It tried to rename th e.exe files rather than delete or overwrite them, and couldn't, for the same "Administrator" privilege problem.
6. Under Windows10 - Home, no "Security" tab exists to claim the Administrator permission. Also, I couldn't claim ownership.
7. To resolve, I had to go Command prompt and enable the Administrator Account through, "net user administrator /active:yes". This gave me the capability finally, to remove the entire MM5 installation. Then to close the security vulnerability this Command Prompt action might have created, I returned the system to back to its default of, "net user administrator /active:no".
I don't know what happened on my MM5 installation, but at minimum, I didn't see the instruction, support and guidance necessary for me to trust MM5 is ready for prime time.