How to move Girder 5 data (esp. Insteon) from one machine to another?

[jmonier]

The title says it all.

[quixote]

Use "Pump Event" in the Girder to Girder action folder.

[Rob H]

Actually the title doesn't really say it all - when I read it I assumed the question was about configuration data rather than events etc. which was meant?

[jmonier]

Actually the title doesn't really say it all - when I read it I assumed the question was about configuration data rather than events etc. which was meant?

Your assumption was correct, the other poster misunderstood. I should have included "configuration" in the title, sorry.

I tried moving the Configuration Files and that sort of worked as far as the Insteon names, etc. was concerned but with some bad side effects. The license manager was corrupted although I was able to recover from that fairly easily. The biggest problem was that many of my actions were replaced by a particular Insteon action. Most of the actions that were replaced had nothing to do with Insteon. The ones that I've identified so far were originally Zoomplayer TCP/IP commands.

[jmonier]

A correction to the above: The last two sentences refer to something that turns out to have nothing to do with moving the Configuration Files. Instead, it's due to the crazy way Device Manager actions are displayed when the object of those actions is not valid.

In this case the TCP/IP connection to Zoomplayer was not open (because I don't open it until I've started Zoomplayer). For that condition, the action shows as an Insteon command for some reason. Once I start Zoomplayer and open the connection the actions display correctly.

[Rob H]

Oh, that's interesting - it's probably defaulting to the first device in the list. Not sure what to do about that one.

[jmonier]

Yes, after looking at it some more, that's exactly what it's doing. I'm currently using hacked versions of your Zoomplayer and Denon files and that requires me to use the generic Device Manager action. I hope to get around to completely rewriting them to correct some of the drawbacks including providing specific actions other than the generic one.

But, to get back to my original question. Is moving the Config files the accepted (and only) way to move configuration data? Which files have to do with the License Manager such that it becomes corrupted?

[Rob H]

I'm not aware of any other method of moving your configuration from one machine to another. I'm not sure how the License Manager works but I suspect there's something that might tie a License to the machine that it was installed on. Ron would be better able to answer this question - but I'm not sure how much information he'll be willing to provide.