As I've said, what's happening to you it's not normal, and it's not how the system is designed.
Just to be more precise: we haven't designed *anything* in the serial number activation or hardware detection routines, etc, this is done entirely by the Esellerate library that, since it used by several hundreds of other shareware products, it supposed to work quite reliably. We only do the communication between Esellerate and FS X or 9.
What you are seeing can be maybe due to one of these factors, like:
- Esellerate can't write the activation in the registry, probably becasue of wrong permission settings somewere, so it keep asking because it can't store them. Wrong permissions might be a result of running with a limited permission account instead of an account with administrative rights.
- The fact that you keep turning on and off the network, with *some* cards and *some* buggy network drivers, might result in the hardware ID that keeps changing, as if you were really changing the hardware. Since a network card is an hardware change, although a minor one, it will not consume an activation, but it will try to get a confirmation online. To diagnose if this is the problem, you should contact us in private at the support address written on the Contact page, so we can check your activation history on the server side, and see if this is the case.
Both LSZH and KORD worked perfectly well on my networked computer before
So, it's clearly a problem of what you have changed in your config, so you can go back to "before"...
