[MM2+3] Change Drive-ID after moving Files to a new Drive

[Whiznot]

I love MM and thanks for the script.

I am running both MM3 and MM4 on a cloned drive in Windows 7. The change drive-ID script has been installed for each MM version.

When I ran the script for MM3 I was given two unlabeled "from" options and and three labeled "to" options corresponding to drive letters. I selected the top "from" option and the top "to" option (music drive C) and was successful.

The script options for MM4 present 3 unlabeled "from" options and the same 3 "to" options. I decided to delay running the script for MM4 until I can learn which "from" option to select.

My music has always been on a single drive. I don't understand multiple "from" options. Please respond if you understand what the different "from" options represent.

[mrmozambique]

Hi all. I am using MM 3.2.3 on Vista Home Premium. I created the VBS file and added the script to my scripts.ini file, but when I try to run it I get the following error:

Error #424 - Microsoft VBScript runtime error
Object required: 'MM_HDDSerial'
File: "C:\Program Files\MediaMonkey\Scripts\MM_HDDSerial.vbs", Line: 2, Column: 0

Any ideas?

[surfer]

Does this script work on the new MM4 under win7-x64?

[nynaevelan]

Does this script work on the new MM4 under win7-x64?

Yes it does, I use it every weekday to move my home db to my work db.

[Mark Colan]

Summary: I have tried using the script AND the manual method. Although the drive ID looks correct, Tracks will not play. They show up in black until I try to play them, at which time they gray out on down the list.

Details: using the script
I made a copy of my music library from the old disk, which was dying.
I made a copy of the MM.DB from the old system disk.
I reinstalled Win7 64-bit (for reasons not related to MM) and then MM 3.2.5.1306.
I edited the scripts.ini and created the new script file.
I started MM using right-click Run as Administrator. I ran the script successfully, and it said restart MM, so I did that.
The album tracks appear in black, but when I try to play one, it goes gray.

Details: the manual method
Closed MM.
I used the DIR command to find the drive-id, then converted to decimal using the javascript converter provided on the manual method Web page.
I downloaded the SQLiteBrowser and started it, navigated to the specified location for the disk id.
The disk ID I found above was exactly the same as what was shown in the database, so I conclude that script worked correctly. The script apparently did not change the disk labels, so I changed them in SQLiteBrowser.
I applied the changes and closed SQLiteBrowser, then started MM.

It still does not work.
Even though I verified that the serial number is correct, MM cannot play my music files.

Any suggestions? I have put many hours into tagging my music and I would hate to lose all that information.

[nynaevelan]

Is the music using the exact same directory structure as it was with the previous db?? When you check the dead links node, does your music show up there? If so, you can use the find missing/locate files option to have MM rescan in the missing files.

Also, are you sure it moved the music from the correct drive, how many drives are listed on the left side??

On a side note I have never tried to use the script with the directories being different on each computer, I have my music on both files set up the same on both.

[Mark Colan]

(Slap forehead)

I got burned by my own backup strategy: out-smarted myself. "Audio - Master"was the original name. The backup is always "Audio - copy". When I restored the copy, I forgot to rename copy to master.

Renamed, now it all works. THANKS!

[nynaevelan]

Glad you got it up and running.

[modtang]

The script worked for me (again) after moving my music to a bigger hard drive. Thank you for making life that little bit simpler for me.

[Champkat]

Hi all

I have a few questions for the experts. Let me begin with a few facts.
1. I am running Win XP Pro
2. I have MM 4.0.0.1439
3. I have installed the script
4. When running the script I get "Error happened during script initialization: A script engine for the specified language can not be created.
5. Language is English
6. My MMDB is located in C:\Documents and Settings\USERNAME\Application Data\MediaMonkey NOT in Local Settings\Application data\Mediamonkey.

Ok. So what have I done wrong? How can I get this to work? I have a huge library with years of info I do not want to lose. I am not a computer person and scripting is all Martian to me. In other words pretend like you are talking to a 2 yr old.

Thanks in advance

[nohitter151]

Hi all

I have a few questions for the experts. Let me begin with a few facts.
1. I am running Win XP Pro
2. I have MM 4.0.0.1439
3. I have installed the script
4. When running the script I get "Error happened during script initialization: A script engine for the specified language can not be created.
5. Language is English
6. My MMDB is located in C:\Documents and Settings\USERNAME\Application Data\MediaMonkey NOT in Local Settings\Application data\Mediamonkey.

Ok. So what have I done wrong? How can I get this to work? I have a huge library with years of info I do not want to lose. I am not a computer person and scripting is all Martian to me. In other words pretend like you are talking to a 2 yr old.

Thanks in advance

The problem is not with the script, it's with the windows scripting host that is (or maybe is not) installed on your PC. You could verify that by trying to run any other script (several are included by default with the MM installation) at Options > Scripts.

http://www.mediamonkey.com/support/inde ... icleid=116

[Champkat]

I have several other scripts installed and all are working properly.

I also tried all the solutions per the link you provided. Everything registered successfully. The Change Drive script is still giving me the same error message.

Thanks

[BenRad]

I'm having the same issue. Let's join forces to figure this out, because I'm dead in the water...
I thought it was a Win 7 64 Bit problem, but since you're on XP Pro, then I'm thinking it's not. Is it possible that it might not be a Windows scripting issue?

[nohitter151]

Have you tried to start MM as the administrator before running the script?

[BenRad]

Yes. Same result.