In one of my previous lives (hw oriented), "fixed disk" was the complement
to "removable disk", as in those drives where a cartridge or disk pack
containing platters was user-loadable into the disk drive. This allowed
such things as one system to support accounting, inventory, etc. applications
just depending on which cartridge was loaded. Some even had a fixed
platter and a removable, so the OS might be on the fixed, and the app
and it's data were on the removable. Of course, you'd have to reboot to
swap removeables out. When Winchesters came along, everything became
"fixed"......

"Ah, the infamous error 417. This is a HTTP error.
This can possibly be fixed by telling BOINC to use HTTP 1.0 communications only. To do so, make a cc_config.xml file in your BOINC Data directory.
Put these lines into it:
<cc_config>
<options>
<http_1_0>1</http_1_0>
</options>
</cc_config>

Open BOINC Manager->Advanced view->Advanced->Read config file.
Now try to upload/download."

"Ah, the infamous error 417. This is a HTTP error.
This can possibly be fixed by telling BOINC to use HTTP 1.0 communications only. To do so, make a cc_config.xml file in your BOINC Data directory.
Put these lines into it:
<cc_config>
<options>
<http_1_0>1</http_1_0>
</options>
</cc_config>

Open BOINC Manager->Advanced view->Advanced->Read config file.
Now try to upload/download."

I once worked at a place that had 8 (numbered 0-7, of course...) disk drives and 4 permanent disk packs, with about 7 temporary packs for various projects - and swappable addresses. I ran one job (I was a system operator - this is back in mainframe times...) where steps 1-7 required one address (say 5) to be a scratch pack, and steps 8-end required address 5 to be the project pack. You'd just pop out the address plug for 5 and put it in the drive (already spinning, of course... these drives took about 1.5 minutes to come up to speed!) that had the project pack.
____________
.

I have got three validate errors all 17th March done uploaded either before or after the outage and one both of us have got validate errors. Host ID = 5250323 my new machine this is the fourth validae error from this machine and it is new well bought Jan this year.
____________

Validate errors again with 'hostid=5069275' after the weekly server maintenance.

They were ULed during the maintenance and reported after.

The same like for two weeks.

:-(

I have got three validate errors all 17th March done uploaded either before or after the outage and one both of us have got validate errors. Host ID = 5250323 my new machine this is the fourth validae error from this machine and it is new well bought Jan this year.

One of my both validate errors got the 3rd wingman, so it'll be 'deleted' soon and won't be fixed.

This validate errors (yours and mine) are server related.
If your wingman have the same result, for sure - and not because of your machine.
I made a small look at your validate errors and your wingmen have the same results.

One of your three validate errors [wuid=582108644] have a wingman also with validate error.

BTW. I saw you let run only SSE3 opt. app on your Q8300. I would guess this CPU can also SSSE3, or maybe SSE4.1 . And then you would see a little speed up in calculation.

I've been able to pull a few cuda23 WUs (32 to be exact) in among dozens of "Project has no jobs available" messages. So I think it's just a matter of letting the splitters catch up with demand. I got a couple hundred Seti Beta WUs before that server was taken down. Too bad they're not transferable.
____________
Best wishes:)

I got a couple hundred Seti Beta WUs before that server was taken down. Too bad they're not transferable.

FYI - for anyone reading that may not know the answer to this: the reason why they're not transferable is because you're not actually BETA testing the workunits, but the application and the backend server processes themselves. Most of the BETA workunits are sent out over and over again, so as to provide a repeatable environment for troubleshooting purposes.

It does no good to transfer those workunits to the live project because there's a good chance they've already been crunched scientifically.
____________