I have tried with an RPC and without.

Maybe they can pull up my last RPC so that I can manually put it in to fool the system. I dunno.

I am not trying anything more until my new HDD gets here and I can properly rebuild the array.

I request that again :)

Every time the question gets asked we always end up with the same answer. WCG wishes to be an unimpeachable source of valuable data. for this reason a full audit trail of all results must be maintained, so ALL data from ALL devices must be traceable. Meging devices would lose this audit trail and actually serves no useful purpose. Devices that stop producing results, or have never produced results quickly fall out of the lists, but can be displayed if ever required. So why change a system that it utterly reliable for no good reason?

Regardless, it's just as a line from one of my all time favorite games (Worms World Party) says: (in a Jamaican accent) "it's not happenin', mon!"

Time to update your answers then and base them on 9 plus years of WCG facts, traceable and auditable (At least over here all posts are still there from day one, except the policy violators ). Integration of multiple identical registrations of the same physical device is still on the active wish-list and as per the 2012 post once-upon-a-time on the board. It's a standard BOINC backend feature where the underlying UD crud being hard to adapt is the better excuse for not having this. Device registrations, particularly now with the Ripple Rent-O-Cruncher, an even bigger fake number than it already is. With 2,566,280 per last night would not be surprised if this was highlighted on Facebook, Twitter or some other place.