I, like you, have 2 logins. The way I handle this is that BOINC (which I now use) and UD client (which I used to use) are installed on one user profile only. I use windows "Fast user switching", which enables me to log on as the 2nd user while the first user is still logged on and running programs. Boinc still does everything, even sends results and gets more work. The other user is totally unaware and unaffected by this. You will need plenty of memory for this option, but you can switch back and forth between users quickly.

I am not sure about BOINC, but you CANNOT run more than one instance of the UD client on one machine - it uses shared machine resources above the user profile level. So the 2nd user may not make his own installation of UD, and things will get messed up if you try.

If youn cannot use fast user switching, it is possible to run UD client as a windows SERVICE, that runs for all users - this is well explained in many other threads - do a search for "Run UD client as a service". With this option, your PC will crunch the same work, irrespective of who is logged on.

Another option is to run the UD client on your login and run BOINC on your brothers login. They would process totally separate work, and you can choose whether you want to use the same WCG name for both, in which case you get all the points allocated from both clients, or create another separate WCG identity for your brother.

Happy crunching

There are a few problems with Fast User Switching. If the wrong user logs on first, then UD will not run. If you solve this by putting the shortcut in All Users, then you will get an error when logging on as the second user. You can't win.

Far better to install BOINC as a service. Unlike UD, BOINC fully supports running as a service, with all the proper setting built into the installer. We don't need to use the UD service hack anymore - it is unofficial, and hard to remove.

Running as a service means that you will crunch no matter who is logged on (even when nobody is logged on) and Fast User Switching is irrelevant.

Yes, I have seen the problems using fast user switching - in my case the user that has BOINC installed always logs on first.

It is good to know that BOINC can run as a service - I assume that you still get access to the same BOINC GUI and can view project graphics etc?

Appologies to Dharwish if this constitutes Hijacking a thread - but it seems we are in a similar position. We both have 2 users of our pc. I dont know about Dharwish, but I am on very good terms with the other user of my PC, and so I only have one WCG identity! What if we fell out and each wanted our own WCG account? Is there an option to install BOINC on both windows user profiles and then crunch separate work for separate WCG accounts when each is logged on (without using Fast user Switching)?

Well Dirk Gently, I am in good terms with the other user too.The problem is i will have to wait until my curent work unit has finished crunching up.When it does finish im gonna migrate to BOINC and start crunching as a service.Hopefully my migration would be incident free.

I understand it will happen, but I suspect it's low priority.

Graphics stuff is difficult at the best of times, and I have heard that the BOINC graphics features are particularly complex. So, don't hold your breath. There are a lot more urgent things to be done first.