Hi Kevin,

I don't think I was too clear with my last post. I have included the account_worldcommunitygrid.org.xml with my package so the client PC has connected to WCG, downloaded work units, etc (ie everything works fine). I was just wondering about how to stop the duplications of the devices appearing in my stats (This is not exactly a major problem I know, but I'm a neat and tidy freak!!!)

The code in the authenticator tags has remained the same, which is the only thing that I thought might change.

The other xml files that are created when boinc.exe is first run and first connects, also have long code like numbers in them, do you think it could be one of them ?

David

I'm going to guess that we're talking about slightly different things here.

I'm refering to te duplicate devices that appear in the 'My Grid > Device Manager' section of the WCG website.

I think you're refering to duplicate devices on the clients processing the work units.

Just to recap. I have created a new BOINC msi installation which just installs the BOINC service on my client PCs. This new package includes the account_worldcommunitygrid.org.xml file, plus the basic BOINC files required for the service. I had to tweak the msi a couple of time so that the gui_rpc_auth.cfg and remote_hosts.cfg files were also included so that I can monitor the client PCs from my server.

This resulted in me installing and uninstalling BOINC 3 times on my test PC. (uninstalling completed deletes the BOINC directory, as it should)

The net result is that I have 3 identically named BOINC devices listed in the Device Manager on the WCG website.

What I'm trying to do is to include some additional files in my custom msi installation that will tell BOINC that is doesn't need to re-register the PC and to just go and get the work units. I'm guessing that I will have to install BOINC on each of the PCs in my network once, grab a file or two from each PC and include them in the msi. (Obviously the msi would be tailered so that the right file(s) get installed on the right PC)

My guess is that the other XML files created on the first run of BOINC are the key, however I'm trying to workout which ones to use.

As I said, this is not a major issue, but just something that I would like to sort out.

Hope this is a bit clearer

David

P.S. If you're wondering why I'm bothering with the repackaging of the original BOINC msi, I have found over the years that it is much easier to patch programs when a new version is released. (ie drop the new files into my custom msi and create a msp which can then be directly applied to all of my PCs in one go - takes about 10 minites and doesn't have to be done outside of work hours - Allows more time in the pub )

I do assure you I'm in the former camp - hence my forum name.

In fact, that's what I've been doing with my UD devices, however it appears that you can't change the name of BOINC ones. (And hence the question to you guys!)

Not strictly true about 4 results required. Each Boinc project choses their own requirement.
Seti sends out 4 and requires 3 back to agree for validation.
Predictor sends out 4 also.
Rosetta only sends out 1 and validates immediately.
Climate sends out one.

So WCG could if it wished just send out the one as with the normal UD client, you can chose what you want and not be constrained by anyone else.

If you do a complete uninstall of BOINC, including deleting project folder, when you do new install on same machine you will get a new ID for that processor. Same holds true if you change OS (different Linux or Win 2000, XP home or XP pro) or if you detatch from the project from BOINC manager. On BOINC only projects, you can merge these clients IF everything is identical, as you now have. If you change OS, you will eventually be able to delete the old client without losing any credit from the old client

Doing what you have done on the testing, you should also need the client_state.xml file.