BOINC/SETI Problem - my own fault

Associate
Joined
20 May 2006
Posts
1,029
Location
London
Well I thought I knew what I was doing. [famous last words]
Installed manually the not VLARkill prog without realising I needed to edit the app info file.
Ran the rescheduler & it convert 151 files to the CPU seemed good.
I don't know if it played a part but the GPU tasks were suspended - when I resumed them they all became computer error:eek: 300+:(
edited app info to reflect VLAR not kill but BOINC said could find file:confused: & tried to download it:confused:.
Ran optimised client & saw option to install not VLAR kill. Still no joy:mad:
Some GPU units downloaded but not flagged as such & so didn't run:confused:

So deleted app info file & reinstalled the optimised client with default setting.
No GPU work & now saying my limit is 2 a day!:eek::mad::confused:

By the way using Win7 64bit which is not supported by rescheduler.
[Only backed up project folder not BOINC folder with client state xml:o]

Q. Any one using rescheduler on Win7 64bit?
Do you know what I did wrong?
Should I just not worry about VLAR kill.
 
i'm using 7 x64 on 1 rig with no problems using reschedule.

You'll have a small daily limit due to the large number of errorred results reported. This should/will come back to normal as long as you dont have to many errors. Not sure how long it'll take tho.

For future ref its probly best to set no network activity before playing with files as it is sometimes possible to recover them if they haven't been reported.

Probly worth uninstalling everything and manually deleting any remaining files and restart.
If you install the opt app (Lunatics_Win64 v0.36 combined installer) as follows it should be OK and wont need any editing of the app_info file
1) astroplus enabled.
2) the correct multi beam CPU instruction set.
3) Multibeam GPu.
Click next
4) CudaV12NoKill.
5) Cuda v2.3 DLL's.
click next
 
Last edited:
HI Toxic -I should have gone with my gut instinct & waited until the cache had got v small.
Both before this & now getting some CPU units saying 14 hours.
Still no GPU units due to the 2 a day quota.

@ReaVerUK - I pretty much followed your instructions trying to get it right, at the 2nd or 3rd attempt, but the WU's had been lost even though I had suspended network connection.
Something was corrupt & so the MB Cuda exe. was not found. Deleted it & the app info file when I reinstalled the optimised client, VLAR kill/standard version.

Have suspended work fetch & will run cache down & give it another go but with the servers shutting down for 3 days tomorrow I don't know what work fetch will be like.
Thanks for the input. Aren't computers fun:rolleyes:
 
Back
Top Bottom