HelloTychicus,
Why not? When we were running the OpenCL version of HCC earlier this year, many people ran multiple GPUs. Unfortunately, we finished the HCC data in half a year so right now we have no GPU projects that you can run, nor do we have any under development.

Someday . . .
Lawrence

There are other BOINC projects where you can put your 7990 thru it's paces!

If you have to create a cc_config file in notepad make sure you rename the file cc_config.xml when you're finished.

That was already said in the original post about the cc_config.xml ;)

What appears to be a slight confusion is since when this 'read config file' could be done... think at least since the early 6.x versions. Probably there's been a mix-up with the new app_config.xml. That can now be read-in via the same menu option and is confirmed in the message log:

73 08-10-2013 10:13 Re-reading cc_config.xml
74 08-10-2013 10:13 Not using a proxy
86 08-10-2013 10:13 log flags: file_xfer, sched_ops, task, checkpoint_debug
87 World Community Grid 08-10-2013 10:13 Found app_config.xml

As you see, both files [plural as the text is now in latest 7.2 clients] are read.

There's a big BUT with this. By far not all additions/changes to the cc_config.xml take immediate effect with the read-in [only tested a few tags for the app_config.xml]. Often a client restart is still required which means in some cases that planning is advised. You want to do that when you've checked where any CEP2 task is... when the last checkpoint was, or you could lose hours progress [of course if you run CEP2 on all cores simultaneous, there's little room for planning... just bite the bullet, or switch running science selection for a while if it hurts too much].

And yes, be sure the file remains to be named exactly the same. Some text editors will by default suffix .txt to a file, and then your changes/additions will of course not be found.

edit: BTW, think the "read config files" also includes the remote_hosts.cfg, at least when I do this all the IPs are being listed in the log from which RPC commands are accepted (the removed log entries #75-85... not going to tell you what my LAN IPs are ;>). On that token, it seems the IP specification could be replaced by the MAC codes in a future release. This would facilitate to allow full DHCP without having to worry about which IP is linked to which device. If that gets Event logged, you don't want to publish those lines either... they represent a potential attack vector for drive-by hackers.