Forum > GPU crunching
CPU <-> GPU rebranding
Geek@Play:
Marius...........Question please.......... ::)
If I start program with the commmand ReSchedule.exe /Autorun 50 and the configuration file contains Position=75, which file ratio will be used? 50 or 75?
Thanks for the program, it works great!
;D
[edit] Never mind, i figured it out. If OnlyVLarVHar=1 then those are moved to the CPU and no others are moved.
;D
Marius:
--- Quote from: savac on 21 Jun 2009, 11:57:32 am ---I'm running 64 bit xp and I know you've tested this out for 32 bit, but every time I click the "run" button i get an "Error:Range check error". If i do not have boinc running the tool works fine. It appears from the log file that it's having trouble stopping the boinc service in x64. Is there any way to fix/change this, or do you have any recommendations?
--- End quote ---
Thanks for reporting. I have indeed only tested on win32 and i have no experience with win64 (other then a couple of failing windows 7 installations). But i do have a winxp/64 installation under virtualbox so i will have a look later this week as soon as i have the time.
In te mean time that range error bothers me a lot, so i recompiled without rangechecking and included a crashlog mechanism (nothing else has changed in this new version). Could you or Calypso check if this solves youre problems? And if not could you please post the Reschedule.elf file which is created.
For the record, Vista and windows 7 should theoretically block or ignore any commands to start or stop any service, so i do think you need to run under admin rights.
Thanks,
Marius
[attachment deleted by admin]
eschamali:
Got: Error:Error stopping BOINC service with 1.7 - Windows 7 64bit
Tried with "Run as admin", same result
Attaching elf file
[attachment deleted by admin]
Calypso:
Hi Marius.
I tested version 1.7
Of course no "Range check error". I get "Error:Error stopping BOINC service" in both cases (running with or without admin rights).
I attached log and elf file. I ran the tool three times. At first without admin rights, then two times with admin rights.
When stopping Boinc manually, the tool works fine.
[attachment deleted by admin]
Marius:
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?
Navigation
[0] Message Index
[#] Next page
[*] Previous page
Go to full version