BOINC/SETI Problem - my own fault

[Pilgrim57]

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 300+
edited app info to reflect VLAR not kill but BOINC said could find file & tried to download it.
Ran optimised client & saw option to install not VLAR kill. Still no joy
Some GPU units downloaded but not flagged as such & so didn't run

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

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

Q. Any one using rescheduler on Win7 64bit?
Do you know what I did wrong?
Should I just not worry about VLAR kill.

 

[Pilgrim57]

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