I've never had a speed change spawn a new Host ID, but I suppose it could depending on the circumstances.

FWIW, the most frequent reason for a new ID to be spawned is if a host returns an RPC sequence number less than the one the project has stored as the last one from the current/old ID. This is usually due to corruption of the client_state file from a BSOD, careless manually editing, or just an outright boo-boo. ;-)

HTH,

Alinator

I agree, I overclock and I've never seen an ID change on account of speed. At least not yet.

---

My Amazon Wishlist
The T1 Trust, PRR T1 Class 4-4-4-4 #5550, 1 of America's First HST's

I've never had a speed change spawn a new Host ID, but I suppose it could depending on the circumstances.

FWIW, the most frequent reason for a new ID to be spawned is if a host returns an RPC sequence number less than the one the project has stored as the last one from the current/old ID. This is usually due to corruption of the client_state file from a BSOD, careless manually editing, or just an outright boo-boo. ;-)

HTH,

Alinator

How about cranking up the core speed? Will it get testy about that or work just fine as long as it happens transparant without touching the boinc install?

Krek is correct. It depends on how people upgrade. I upgraded my OS patch from XP SP1 to SP2 without having new IDs. I've updated my BOINC each time without having new IDs.

It does happen, accidentally at times. Something doesn't port over correctly, or some other issue like that can cause a new ID to be given.

If you update, and keep your current installation in tact, you should not receive a new ID.

---

Usually updating the OS will not create a new host ID. It does not matter which OS. Unfortunately if it does make a new host ID it will probably not be mergable. Unmergable hosts can be deleted once all assigned tasks are deleted from the active database.

---

BOINC WIKI

BOINCing since 2002/12/8

In threads about system merging I noticed people saying that you can't merge systems if they have different OS's (which in Linux terms means different kernel versions).

Does this also mean that when you update your kernel to a new version number that BOINC will start showing the results for that system under a new ssytem ID?

Or is it just limited to when you reinstall BOINC or a system from scratch?

What about Service Packs in Windows OS's? They usualy show up in ID strings for the OS too.