REPOST...
I have a product I paid for (and have been using for many years) that suddenly stopped working. All I have is a rumor that it's because the computer name was changed. If that's the cause, it's undocumented, and a bizarre dependency -- certainly it's not a security measure, because any computer can be given any name at any time. And I have NO RESPONSE from the company. My music database is inaccessible, and I have no clue what to do about it. Reinstall? Restore a license? Why would these be necessary?
EARLIER MESSAGE:
>> Did you change your computer name?
MAYBE... I recall it was changed some time ago (to be more consistent with other computers on the LAN), but perhaps not restarted until last night. After being always-on for a long time, I powered off for six days while on a trip. I restarted it last night and did the MC 12.0.233 upgrade this morning. The computer's clock is auto-set and is correct, as it always is.
It's an XP WinMediaCenter machine that's been running MC 12.0.x for months (my last restore was to put MC on this PC, transferred from my old PC).
I install every new version of MC, usually the same day it's made available. Today I did exactly as I always do.
I'm not running any exotic or new software.
If changing the name of the computer wiped out my MC license, that's scary because it's the only software I've encountered that cares what the PC's name is. I work with hundreds of computers (not running MC, of course) every day and have never encountered any problem with changing names other than sometimes messing up Windows network neighborhood bookmarks.
Is this behavior in MC documented? What about the computer's name matters: exact spelling, capitalization, nickname? Is there any recovery short of restoring the license? I searched and can't find any mention of the computer's name as a factor in MC installation or behavior. Did I miss it somewhere?
If MC really does require that the computer's name be unchanged after MC is installed, that seems like a really poor system. The computer's name is in the user's control, so how does this protect MC? Wouldn't it be a lot better if MC uses something more stable to lock on to, such as MAC or CPU serial number or something? After all, if the license is locked to the computer name, something readily changeable by the user, it's a very weak lock. And if the license is NOT locked to the name, then why cause the user a problem for no reason?
I'm hoping to hear an official explanation before I use up a restore to recover from what might be MC's undocumented (mis)behavior.