I had a similar issue . . . It appears that some remotes programmed either in much older versions, or with the standalone ediitors have programming that is incompatible with current CCP. They would seem to upload fine, hut then throw that error. Once a nee config was written, they ipload fine, so jothing wrong with comm or setip. Seen it both way for the same model, again, depending on what last programmed it.

And yes, it sucks . . .