Forum > GPU crunching

CPU <-> GPU rebranding

<< < (18/75) > >>

eschamali:

--- Quote from: Marius on 21 Jun 2009, 05:54:03 pm ---Ok, at least the weird range error is gone and i got the general picture about stopping the service. So thanks to you guys i'm 2 steps further.

Storyline: for some reason windows accept/ignores the commandline "net stop boinc" and just returns with code 0 (succes). The next action in the code is a simple check to see if boinc is really down (by locking the stdoutdae.txt file, one of the files boinc alway's opens). Because it cannot get this lock i assume boinc is still running and raise the error 'Unable to stop BOINC service'.

So the trick question is why does windows/64 allow "net stop boinc" but does not stop boinc. Is there any other valid windows 64 command to do this?


--- End quote ---

Seems like BOINC is not running in service mode as default any longer. Due to some problems with CUDA. So I get this error code when trying to stop BOINC:

C:\Users\Dag Morten>net stop boinc
The service name is invalid.


Richard Haselgrove:
BOINC defaults to 'not service' on Vista and Win 7 because CUDA won't run as a service on those platforms.

Anybody running this tool will be wanting to run CUDA, so you can definitively assume that on Vista and Win 7, BOINC will NOT be running as a service.

Until nVidia works out how to do a CUDA service on Win 7.....

Geek@Play:
Ran Schedule 1.6 with a 50/50 split set in.  Seems it took the 4 work units already in progress on the CPU's and rebranded them to CUDA and when Boinc restarted new work units were started.  Leaving the newly created CUDA in paused mode.  Didn't expect that!  Would have been better to leave work already started alone.

savac:
I see im a bit late to respond, but here is the requested file.  Hope it helps.  1.7 does return a boinc service error "Error:Error stopping BOINC service"  so i'm running into the same thing with winxp 64.

[attachment deleted by admin]

Marius:

--- Quote from: Richard Haselgrove on 21 Jun 2009, 07:52:34 pm ---BOINC defaults to 'not service' on Vista and Win 7 because CUDA won't run as a service on those platforms.

Anybody running this tool will be wanting to run CUDA, so you can definitively assume that on Vista and Win 7, BOINC will NOT be running as a service.

Until nVidia works out how to do a CUDA service on Win 7.....

--- End quote ---
Any idea what commands to use to shutdown and start boinc for the win64 platform? For example "boinccmd --quit", but how to restart it?. Or are there other  alternatives?

Greetings,
Marius

Navigation

[0] Message Index

[#] Next page

[*] Previous page

Go to full version