Interesting. I did a fresh install when going to Vista x64 vs. doing an in-place upgrade. Might that have made a difference? And perhaps being in a 64-bit mode makes the processor look different than when in 32-bit mode (just as 32 bit protected mode appears differently than the old 16 bit mode)?
The host ID actually has nothing to do with the processor; it's your MAC address, at least for MAPublisher. So Vista or XP, 32-bit or 64-bit, none of that should change your MAC address or, therefore, your host ID.
That said, it does seem to happen from time to time! There are oddball cases but they're usually related to the addition of a new piece of hardware that for whatever reason occludes the original MAC address. One of our support guys once plugged in his digital camera and suddenly found that his host ID was being reported as 00000000! Fortunately, unplugging the camera restored the ID; in most cases where we hear people report this it ends up being some piece of temporary hardware that can confuse the host ID function of the 3rd part security library we use.
Changing the ID permanently really requires a hardware change. Adding a second network card, or replacing a motherboard (most motherboards nowadays have built in networking) are the most common causes, but there are probably others. There are software methods of changing your MAC address, but that's never a wise idea; MAC addresses are supposed to be globally unique, and if you change yours you might end up colliding with someone else and causing network issues. And anyways, all that would do is make you have to contact a number of vendors for new licenses
That would probably include Adobe, by the way, because I believe they use the same library we do!
Assuming you added or took away nothing during your upgrade, I'm not sure what could cause the host ID to change. The only thing I can think of is maybe something like a native network card on your motherboard was disabled under XP but Vista activated it when it installed? Something like that might cause it to change, but it would really require a MAC address from a different source than you were getting it from under XP.
I've also noticed that MAPublisher won't execute inside a Remote Desktop Connection, a situation where the hardware ID hasn't changed (I've checked), though if you launch it from inside a VNC session it works just fine. Is that normal/expected behavior?
I actually went and tried this and found that the reason is quite simple: the security library detects & automatically fails any attempt at licensing under what's called "Windows Terminal Services" -- which includes RDC. Since VNC uses a very different method of connection (I believe it literally just sends mouse clicks & keystrokes one way and graphics output the other), the library doesn't detect & quash it like it does with RDC. So I guess that's expected behaviour, though I'm not sure it's really come up (other than us using VNC, so we knew that worked).
Should we take this discussion off line? I don't want to hijack this thread.
Any more than I already have.
Well, we do have the OP's blessing