http://setiathome.berkeley.edu/show_host_detail.php?hostid=2235134
http://setiathome.berkeley.edu/show_host_detail.php?hostid=2219084

Same system, nothing in it has been changed (bar the CPU speed when overclocking) - could that have caused it ?
When i try to merge them, they are not "seen" as being the same computer.

Any ideas ?

Cheers :)

---

http://setiathome.berkeley.edu/show_host_detail.php?hostid=2235134
http://setiathome.berkeley.edu/show_host_detail.php?hostid=2219084

Same system, nothing in it has been changed (bar the CPU speed when overclocking) - could that have caused it ?
When i try to merge them, they are not "seen" as being the same computer.

Any ideas ?

Cheers :)

That's another one that can't be merged because of the rpc times. 2235134 was created on 5 March, but 2219084 was still contacting the scheduler on 9 March. Because of the fact that both hosts were in existence and in contact with the scheduler on overlapping times, it will never consider them to be 2 instances of the same host and allow them to be merged. As far as the server is concerned, if the newest one had really wiped out the oldest one, the oldest one would never have been able to contact the server again - since it did, the server says they can't be the same machine.

---

Makes perfect sense, thanks for the reply!
Im still confused to why this has happened though. If it was something as simple as clock speed, I would have expected a lot of instances of the same machine by now.
Guess its just something ill have to live with :D

Cheers buddy ! :)

---

Worst case will be you have to wait until all the results for the old ID are cleared out, then you should be able to merge it to the new ID.

HTH,

Alinator

Probably a stupid question, but is your host name and computer name the same as before? If not it will see it as a different pc.

---