They are testing new searches, if you have any issues with those, better post in the News part of this forum, there are threads to each of the new searches. The edge_1 and free_1 had error rates of about 5-10% according to the posts over there, so no reason to abort all of them, that does really not help them to find the issue.

From what I can tell, it looks like the newly generating 'ps_separation_14_2s_null_3_v3' workunits are crunching and validating, so I think we're in the clear from here on out.

You probably have your project preferences set to receive cpu tasks including N-Body Simulation, but your app_info.xml does not contain any CPU applications. Once you go on anonymous platform, only the applications in it will be used. If you want to run GPU only, change your project preferences to get rid of the messages.

Ahhh yes you are correct more than 4 gig would not be helpful under XP!

One thing I did, I install Win7 on my pc's more than once due to using used parts all the time, I got an 8 gig usb stick and after making it bootable copied the Win7 dvd onto it. It makes Win7 load up almost twice as fast as using the dvd, it also means I don't have to put a dvd drive in each machine early on.

I would first upgrade your memory to at least 8 gig but probably 16 gig if it were my pc. There have been studies done that say a pci-e slot is not the slow-down people think it is, so that may not be your problem.

you can zero out your debts by putting this into your cc_config.xml file:
<zero_debts>1</zero_debts>. It is recommended that you only use it once then remove it, but I know some people who just left it in there.

The new Boinc version 7 is NOT clear on the words they are using in the cache area, the early versions anyway. If you are coming directly from version 6 to version 7 you should reverse the numbers you had in version 6. The newer version 7 releases are clearer about what each set of numbers does. But basically the 1st set of numbers now says "minimum work buffer", while the 2nd set says "max additional work buffer", this is in version 7.0.23. Essentially in version 6 you reverse those two with the smaller being in the 1st section and the bigger being in the 2nd part. BUT in version 7 that says to maintain only a VERY small minimum work buffer, which is not what most of us want. I just reversed the numbers and my cache has not changed from the one version to the next.

I have a "full" queue from SETI with 7.0.18, I have my preferences set globally at

Maintain enough tasks to keep busy for at least(max 10 days). 5 days
... and up to an additional 0.5 days 

With development BOINC 7.0.xx versions, Connect about every x.xx days has now effectively become Minimum work buffer. In fact in the later 7.0.xx versions it has been renamed. If you leave it at 0 days which was previously recommended for an always on connection it will not download any new tasks until your cache is empty. The value needs to be set above 0 if you want to download work before the cache is empty.

This new method of controlling work download may cause tasks to run in high priority mode on projects that have a short deadline. The higher the value you use for Connect about every x.xx days/Minimum work buffer, the more likely it is that tasks may go into high priority mode. It depends on the deadline, for example with projects with a short deadline of 2 days, tasks may run high priority with a value above 0.7-0.8 days. This can cause trouble if they run out of order while leaving other tasks "waiting to run". In later BOINC versions (after 7.0.14, I think) high priority tasks run in "earliest deadline first" order which overcomes this problem on most projects. WCG can still upset the applecart though if a computer becomes a trusted host and gets sent repair tasks with a shorter deadline than normal tasks. These repair tasks may start to run in high priority mode as soon as they are downloaded.

<cc_config>
<options>
<exclude_gpu>
<url>http://setiathome.berkeley.edu/</url>
<device_num>0</device_num>
</exclude_gpu>
<exclude_gpu>
<url>http://milkyway.cs.rpi.edu/milkyway/</url>
<device_num>1</device_num>
</exclude_gpu>
</options>
</cc_config>

3/31/2012 9:57:56 PM | | ATI GPU 0: AMD Radeon HD 6900 series (Cayman) (CAL version 1.4.1664, 2048MB, 2031MB available, 6144 GFLOPS peak)
3/31/2012 9:57:56 PM | | ATI GPU 1: ATI Radeon HD 5800 series (Cypress) (CAL version 1.4.1664, 2048MB, 2023MB available, 5440 GFLOPS peak)
3/31/2012 9:57:56 PM | | OpenCL: ATI GPU 0: Cayman (driver version CAL 1.4.1664, device version OpenCL 1.1 AMD-APP (851.4), 1024MB, 2031MB available)
3/31/2012 9:57:56 PM | | OpenCL: ATI GPU 1: Cypress (driver version CAL 1.4.1664, device version OpenCL 1.1 AMD-APP (851.4), 1024MB, 2023MB available)
3/31/2012 9:57:56 PM | | ATI GPU 0 is OpenCL-capable
3/31/2012 9:57:56 PM | Milkyway@Home | Found app_info.xml; using anonymous platform
3/31/2012 9:57:56 PM | SETI@home | Found app_info.xml; using anonymous platform
3/31/2012 9:57:56 PM | SETI@home | Config: excluded GPU. Type: all. App: all. Device: 0
3/31/2012 9:57:56 PM | Milkyway@Home | Config: excluded GPU. Type: all. App: all. Device: 1