Forum > GPU crunching

CPU <-> GPU rebranding

<< < (43/75) > >>

Athalian:
Cpu suddenly got work and now the exe file appeared. So it works now odd enough :/ ill send the thing anyways

Marius:

--- Quote from: Athalian on 25 Jul 2009, 06:39:10 am ---Cpu suddenly got work and now the exe file appeared. So it works now odd enough :/ ill send the thing anyways

--- End quote ---

Thanks, no change needed anymore ;) The original clientstate is correct (no corruption) but it just didn't contain any information about the 603 cpu application.

Must say, this is the first time i've seen a client_state without a cpu application!

msattler:
Downloaded the 1.9 rebranding tool, and for the most part, it works great.
I have one problem though, which prevents me from running it in automatic mode.

I have run it a number of times manually, and sometimes after the rebranding is finished, it does not correctly restart Boinc.  I get a message saying that Boinc is not connected to a client, "you have entered an incorrect password, please try again"......

Manually exiting Boinc and restarting it sets things right again.

Other times it works correctly.  I have not run it enough times yet to notice if the bad restart only occurs when work has actually been rebranded vs when it has not found any VLAR to rebrand.

Anybody else notice this problem?

I should mention that this is on an i7 XP x64 rig, and Boinc is NOT running as a service.

Marius:

--- Quote from: msattler ---I have run it a number of times manually, and sometimes after the rebranding is finished, it does not correctly restart Boinc.  I get a message saying that Boinc is not connected to a client, "you have entered an incorrect password, please try again"......
--- End quote ---

This occasionally happends, but unfortunately its not something i can prevent. From where i stand it looks like a bug in the boincmgr because of credential problems but i'm not absolutely sure about it.

My vista/64 test installation ran without problems, but that doesn't help you much. In the background i use 'boinccmd.exe --quit' to stop boinc, boincmgr detects this and "grayes" out the project. After the reschedule i simply use 'boinc.exe -detach' to restart it, but this credential problem in boincmgr is a blocking factor. You could try these commands manually, its boincmgr whats causing the trouble for sure.

No idea if it can/could be fixed on my side. Any ideas out there?

Jason G:
On XP I still use the 'old style' automatic mode.  That is with an entry in Windows scheduled tasks, pointing to a batch (.cmd)  file that has boinc control in it to control the service:

REM Reschedule.cmd, for automated rebranding
net stop boinc
reschedule.exe /Autorun 75
net start boinc

By linking to a shortcut to that you can set it to run minimised also, so that command window only appears briefly on the taskbar, otherwise invisible.  No problems stop/starting boinc that way here, probably since the reschedule process has enough meat in it without additional delays.

That, of course is for service installation, which won't be suitable with Vista+ with the GPU app, so changing the 'net stop & start' line to use boinccmd should work.  If some delay is needed you can use 'ping someaddress.com > nul' to make a delay before restarting.

Navigation

[0] Message Index

[#] Next page

[*] Previous page