Quote:
So I'm not sure that original music database got hosed. If I get time next week I will try 3.0 again and use the steps mlord outlined for manually building a new database. But that will not overwrite the old 2.x one?


The problem wasn't that a database was hosed. It's that 2.0 and 3.0 use different databases. So when you upgraded to 3.0 for the first time, it didn't see a database, so it built it every time you booted. By doing the instructions above, it will make sure to not only make the new 3.0 database, but also save it to disk for future use.

By reverting back to 2.01, all you did was return to the same 2.0 database that had been there all long and works.

As far as developer builds vs consumer builds, just load the developer build. Even if you currently have no plans to use the features it offers, you might need them for working through one of the FAQ procedures or other troubleshooting situations. Better to just have it there from the start (since it doesn't harm anything, nor slow anything down) then to need to load it up everytime something might need to be troubleshot.