I'm trying to merge duplicate computer names but when I click the merge button there is no other computer in the list for me to select. User ID is 88142

---

If the computers are not the same in terms of OS, CPU type, ... you will not able to merge them.

---

I made changes to three of my systems last week. One did not require merging, but two did. I was able to successfully merge one system, but not the other. Here are the three scenarios.

Computer 177211 was upgraded from a 2.4Ghz P4 to a 3.2GHz Dual Core P4. While Windows XP and some software required reregistration, I did nothing to the BOINC client. The Rosetta site reflects the new and correct hardware/OS configuration that is now in 177211.

Computer 203481 was running Windows XP Home, and I installed Windows XP Pro. The installation wiped the hard drive, and I installed the latest version of BOINC. This created computer 486792, and I was able to merge the results of 203481 into 486792. The merge results reflect the proper and current OS on this hardware.

Computer 297677 is running Red Hat Linux on a dual core P4 whose hostname is redhat. Last week I ran the "update" to apply the latest patches. The Kernel version changed from 2.6.9-42.0.10.ELsmp to 2.6.9-55.ELsmp. During the update, I also had to use the Logical Volument Management tool to extend my root and /var file systems. After patching, my /usr/local file system disappeared, and that is where the BOINC client was installed. This time I installed the latest version of BOINC under the /home filesystem and it created computer 486792. When I attempt to merge computer 486792, no computers appear in the merge list. However, if I attempt to merge computer 297677, it displays the same hostname or hardware in its various incarnations, but not the current configuration for 486792. The merge list for 297677 includes a system named fedora that was running on a Pentium III. Fedora was later replaced with redhat on the same P3. Redhat was later upgraded from a P3 to a Dual Core P4, and configuration also appears in the merge list. However, I cannot merge 297677 into 486792.

It appears that the selection criteria is not exact, allowing a different OS, processors and hostnames. The problem is that the merge does not consistently discriminate for all systems.

---

I made changes to three of my systems last week. One did not require merging, but two did. I was able to successfully merge one system, but not the other. Here are the three scenarios.

It appears the major problem is the cpu type. The new BOINC version not only lists your cpu type but also its features. After installing the new version, note I did not upgrade the old version, I had three computers suddenly of which the two old ones with only the cpu type could not merge the newest one. I found a hackaround using the old version and only have one pc now thankfully. I will try to explain what happened in your three scenarios.

Computer 177211 was upgraded from a 2.4Ghz P4 to a 3.2GHz Dual Core P4. While Windows XP and some software required reregistration, I did nothing to the BOINC client. The Rosetta site reflects the new and correct hardware/OS configuration that is now in 177211.

The BOINC client still had your old computer ids and only updated the details. This should not cause a new computer to be generated.

Computer 203481 was running Windows XP Home, and I installed Windows XP Pro. The installation wiped the hard drive, and I installed the latest version of BOINC. This created computer 486792, and I was able to merge the results of 203481 into 486792. The merge results reflect the proper and current OS on this hardware.

Since the BOINC data was wiped it had to create new computer ids. You did not change the hardware so you were able to merge the old data into the new computer.

Computer 297677 is running Red Hat Linux on a dual core P4 whose hostname is redhat. Last week I ran the "update" to apply the latest patches. The Kernel version changed from 2.6.9-42.0.10.ELsmp to 2.6.9-55.ELsmp. During the update, I also had to use the Logical Volument Management tool to extend my root and /var file systems. After patching, my /usr/local file system disappeared, and that is where the BOINC client was installed. This time I installed the latest version of BOINC under the /home filesystem and it created computer 486792. When I attempt to merge computer 486792, no computers appear in the merge list. However, if I attempt to merge computer 297677, it displays the same hostname or hardware in its various incarnations, but not the current configuration for 486792. The merge list for 297677 includes a system named fedora that was running on a Pentium III. Fedora was later replaced with redhat on the same P3. Redhat was later upgraded from a P3 to a Dual Core P4, and configuration also appears in the merge list. However, I cannot merge 297677 into 486792.

Were you perhaps running the old BOINC version before? If so when you installed the new one it created new computer ids and because it reports the cpus differently the selection criteria sees them as different computers. If you look you will see that 297677 is reported as "GenuineIntel Intel(R) Pentium(R) D CPU 2.66GHz" and 486792 is reported as" GenuineIntel Intel(R) Pentium(R) D CPU 2.66GHz [x86 Family 15 Model 4 Stepping 7] [fpu tsc sse sse2 mmx]". This is two completely different systems as far as the merging is concerned.

If you really want to merge the old 297677 system you can create a dummy install of the old BOINC version, run it, and merge the computer into the new computer it creates. You then have two options:
1. Note the "host_cpid" (cross project id) and "hostid" (the one reported) tag values in the "client_state.xml" file of the dummy version and place them into your main version over the values there after backing up the file. Do this while BOINC is not running and then start the main version and let it update the project and in the proses change the cpu type without creating a new computer. Then after exting BOINC restore the backed up file and restart BOINC as normal.
2. Install the new BOINC version while BOINC is not running over the dummy install, start the new dummy version and have it update the project. Then exit the dummy version and start the main version as normal.
After one of these you should be able to merge the new computer created by the dummy install into the computer created by your main version.

If you don't want this to happen again you should note the two ids from the installed version before making any big changes. Those two values seem to identify your computer.

---

BBLounge - Broadband and Technology forum