How do I do that? I have two linux systems that
have identical cpu and identical os and run the
same projects. How do I know which one is which
in the host list? Help me complete the following table:

system	hostID	bamID

---------------------------------

quad	5402406	128421

linux3  	????????   125633

linux5	????????	127917

275	5405999	140082

xeonV	5406168	147948

xeonXP	5790023	179056

win7	5803561	179358

The "host id" is the value that is shown in the title when
I select a host in the detailed stats.

plz ignore - i figured it right after posting.
s o r r y

Found this in a signature on some forum:-)

Thanks - I will have to remember that along with "the only truely stupid question is the one not asked or posted"

There are about 50+ systems on my detailed stats "users host page", many obsolete, and no id or systems names are listed on the boincstats form for that users host page. In comparing two active systems earlier, I knew that one system was badly underperforming but didnt know which one of the two linux systems it was since it was not identified uniqely. It is not possible to lookup the system name from the boincstats users host list directly. All one can do is make a mental note of the host id (not same as project's host id and unfortunately different from the bam id). Then one can go to the host list, click on the stats icon associated with the bam id, and see if the host id matches the one you made the mental note of. This is awkward and it would be nice if a system name or a link to the host system was provided as another column in that detailed stats host list.

What I found was, (I posted this problem at the boinc manager forum) one system quit processing any work within seconds of the mouse not moving. As long was I was typeing on the keyboard or moving the mouse, the system processed the 4 cpu thread aqua wu, but stopped processing within about 5 seconds after I stopped typeing or moving the mouse. I had not noticed this problem till a couple of days later when the system was no longer producing credit. Rebooting solved the problem.