I just merged the second instance I got from my Win98 machine (which I got before I remembered <i>why</i> I wasn\'t running CPDN on the 98 machine). But, I accidentally merged the old one into the new one instead of the other way around.

Merging host 133223 into host 295997
Retired old computer 133223

It\'s not a big deal, but I\'d have liked to keep the older number. Is there anything that can be done about this, or do I just have to live with my \"oops\"?

Thanks!

---

I just merged the second instance I got from my Win98 machine (which I got before I remembered <i>why</i> I wasn\'t running CPDN on the 98 machine). But, I accidentally merged the old one into the new one instead of the other way around.

Merging host 133223 into host 295997
Retired old computer 133223

It\'s not a big deal, but I\'d have liked to keep the older number. Is there anything that can be done about this, or do I just have to live with my \"oops\"?

Thanks!

It would not have made any difference.

Early joiners do still have that proof of seniority because the system keeps the earliest start date but sadly also keeps the latest number. That applies whether you merge A with B or merge B with A.

I felt just the same when I lost my three-digit host number on another project. And no, there is nothing to do about it -- and even before you merged the only way to keep the nice low number was to leave it inactive forever.

Not what you wanted to hear, but at least you don\'t have to live with the feeling that you made a mistake in which way round you did the merge ;-)

I understand the reason is to make it less likely that you will try to change the hostid of a \'live\' wu. The later hostid is the more likely still to have live data.

---