 |
|
| to mrX |
|
|
By tigerdog - Posted on January 4, 2006 - 18:26:46 (#18755)
Current version when comment was posted: no longer available |
|
|
can't say anything about folding. haven't personnally looked into it. sorry!
|
|
| folding? |
|
|
By BeOS Mr X - Posted on January 4, 2006 - 16:54:46 (#18752)
Current version when comment was posted: no longer available |
|
|
but what is going on with the folding at home for beos. i'd rather participate in that, is it harder to make work on BeOS?
|
|
| fails under Zeta 1.0 |
|
|
By tigerdog - Posted on July 22, 2005 - 12:51:25 (#17295)
Current version when comment was posted: v0.0.3 |
|
|
SETiBe aborts under yT Zeta 1.0 (at least on my machine) with a segment violation:
loading symbols
segment violation occurred
SETiBeApp::AddDeskbarReplicant(int):
AddDeskbarReplicant__9SETiBeAppi:
+0027 9001673f: * 08788b movl 0x00000008(%eax), %edi
SETiBe:sc
frame retaddr
f8ffc494 90016432 SETiBeApp::SETiBeApp(void) + 000000b2
f8ffc4f0 9001e274 main + 00000034
f8ffc51c 90016265 _start + 00000061
f8ffc548 f8ffc583 _end + 106caed3
SETiBe:
I would be happy to help troubleshoot.
|
|
| Re: multiprocessor problem |
|
|
By emwe - Posted on January 18, 2003 - 03:02:56 (#5432)
Current version when comment was posted: v0.0.3 |
|
|
setiathome can only be run once with -graphics option.
besetiathome can be run only once too.
its not possible to run two besetiathome instances and two clients with -graphics simultaneously. ( thats not my fault :D )
when you are trying to start 2 caches in graphics mode, only one cache will be started ( client and besetiathome ). no further besetiathome instance is allowed.
what i could do is to run the next client(s) in hidden mode. that'd be better than stopping at all.
but i cannot understand why u are using graphics mode!? i've only put it in on request. its a total cpu-waste to run besetiathome. its cpu-usage is horrible! if you want fast processing of workunits take the hidden or terminal mode.
thx for your report!
emwe
|
|
| I meant to say multiprocessor problem.. |
|
|
By yonemoto - Posted on January 17, 2003 - 23:43:14 (#5427)
Current version when comment was posted: v0.0.3 |
|
|
|
| multiuser problem |
|
|
By yonemoto - Posted on January 17, 2003 - 23:42:33 (#5426)
Current version when comment was posted: v0.0.3 |
|
|
I think this might be an easy fix -- SetiBe behaves erratically because I am using a dual-processor machine and would like to view graphics.
It only launches one thread, and then the screen fails to display the stuff correctly. I believe it's possible that the graphics cache is being locked out by the first program, which prevents the second program from running.
In any case, SetiBe should only be trying to run one setiathome with the -graphics switch on. =)
Good app, though!
Isaac
|
|
| re: oops, my bad |
|
|
By emwe - Posted on January 14, 2003 - 04:23:03 (#5358)
Current version when comment was posted: v0.0.3 |
|
|
you can import the old caches fine to SETiBe 0.0.3:
all you have to do is renaming the caches to cache01, cache02 and so on, and remove the symlinks in every cache
as they are absolute symlinks( my fault ). and remove anything, except SETiBe 0.0.3 binary and the clients...
so your directory should look like this
//
cache01
cache02
cache03
...
cachexx
besetiathome (optional)
setiathome
SETiBe
//
emwe
|
|
| oops, my bad |
|
|
By clasqm - Posted on January 14, 2003 - 03:45:07 (#5357)
Current version when comment was posted: v0.0.3 |
|
|
scrap my previous comment - I was trying to be clever and copy old caches from the previous version to the new ones. Once I did things properly and started out with *nothing* in the directory but the setibe and setiathome executables, setibe behaved impeccably.
|
|
| problem |
|
|
By clasqm - Posted on January 14, 2003 - 03:30:15 (#5356)
Current version when comment was posted: v0.0.3 |
|
|
Hmmm, this new version seems to have a problem recognising itself - every time I run it, it insists on giving me the "first-time" login screen!
|
|
| Graphics mode... |
|
|
By ljr - Posted on November 10, 2002 - 11:48:28 (#4102)
Current version when comment was posted: v0.0.2 |
|
|
To activate graphics mode, make some changes :
- make a besetiathome link in cacheX folders
- replace the setiathome link by the following shell script :
#!/bin/sh
../setiathome -graphics $1 $2 $3 $4 $5 $6 $7 $8
- make it as executable (chmod +x .... or thru infos)
- starts setibe to test your new config... graphics output is managed now
- starts any besetiathome (link) from caches folder...
BTW nice seti manager !
|
|
| Finally... an easy Seti client viewer |
|
|
By Ruprect - Posted on November 10, 2002 - 00:58:39 (#4096)
Current version when comment was posted: v0.0.2 |
|
|
This is great. Thanks for your hard work! No offense to the other Seti clients/front ends, but I've had bad luck with getting them to work consistently. But SETIBe works great, and it's very slim and simple. I like!
|
|
| sorry |
|
|
By Double_S - Posted on October 19, 2002 - 13:49:35 (#3683)
Current version when comment was posted: v0.0.1 |
|
|
Sorry, Netpositive showed me an cached page where my message was still not apearing
|
|
| Nice stuff |
|
|
By Double_S - Posted on October 19, 2002 - 12:33:19 (#3680)
Current version when comment was posted: v0.0.1 |
|
|
To further improve I would like 2 options:
1) to enable graphic output from terminal engine
2) to show graphic window
I know graphic output means a performance drop. Maybe when "show graphic output" is pressed, the engine is stopt, graphic output enabled, engine restarted, graphic window showed, .... and when user tell SetiBE to stop showing graphics, .... engine is stopt again and restarted without graphic output. This way there is no performance lost while no graphics are showed ....
|
|
| Great thing |
|
|
By Double_S - Posted on October 19, 2002 - 12:32:54 (#3679)
Current version when comment was posted: v0.0.1 |
|
|
To further improve I would like 2 options:
1) to enable graphic output from terminal engine
2) to show graphic window
I know graphic output means a performance drop. Maybe when "show graphic output" is pressed, the engine is stopt, graphic output enabled, engine restarted, graphic window showed, .... and when user tell SetiBE to stop showing graphics, .... engine is stopt again and restarted without graphic output. This way there is no performance lost while no graphics are showed ....
|
|
| Great thing |
|
|
By Double_S - Posted on October 19, 2002 - 12:32:04 (#3678)
Current version when comment was posted: v0.0.1 |
|
|
To further improve I would like 2 options:
1) to enable graphic output from terminal engine
2) to show graphic window
I know graphic output means a performance drop. Maybe when "show graphic output" is pressed, the engine is stopt, graphic output enabled, engine restarted, graphic window showed, .... and when user tell SetiBE to stop showing graphics, .... engine is stopt again and restarted without graphic output. This way there is no performance lost while no graphics are showed ....
|
|
|
|
|
