SETI@Home

[Fleabus]

I'll join.
Results so far...

SETI:1)28 hr 56 min 51.0 sec
2)27 hr 36 min 13.5 sec
3)30 hr 45 min 13.6 sec
4)33 hr 04 min 17.1 sec
5)28 hr 33 min 27.0 sec
6)26 hr 57 min 40.6 sec
7)25 hr 39 min 36.2 sec
8)26 hr 36 min 39.5 sec
9)25 hr 55 min 55.5 sec
10)27 hr 24 min 07.0 sec



------------------
P2-450;256MB PC100;Asus P2B;16MB G200 Mystique 5.13,2.3; 12MB CL Voodo

[agallag]

Try 43677.71 years...

[agallag]

Whoa, lots of posts have disappeared.

To update, the WinNT command line version runs fine on Win98SE, but not on Win95. Don't know about original Win98. It's about 3-4 times (!) faster. I used to complete work units in 30-40 hours with the GUI version, now I'm completing them in about 10-12 hours. You can also let it run in the background, and it won't affect the performance of anything else. It will only use idle cycles, and totally gets out of the way when something else is running. I was even playing some Re-volt (demo) at 800x600x32 full fps on my G200 while it was churning away in the background!

Does anyone know how to stop the command line version? Can you just terminate it, or is there a way to gracefully shut it down? I haven't actually tried to stop it yet, so if it's just hitting escape, sorry to bother you

That's all for now.

Andrew (agallagh42 on SETI)

[This message has been edited by agallag (edited 08-05-99).]

[Wombat]

I used to do SETI, but they don't want any more help. People are already crunching numbers faster than they can harvest new raw data for the SETI@Home project. Intel has written KNI code for it, and there has already been an offer of 3DNow! code which would double the speed of the client, but SETI has turned these offers down. No data = no more donations for them from big companies. Although, 700yrs of computing time is pretty impressive.

If we want to donate our idle cycles, I say go for distributed.net

-Wombat


------------------
503+ rev 1.2a, 128MB PC100 RAM, K6-2/350@400,RH6 & Win98,G200 Millenium (SGRAM), no plans to buy a G400

[Trav]

I'm In!

[Jorden]

Congrats Buuri,

you got me

Jorden.

[M Buuri]

Thanks

I was determined
There's a long way to the next tho..

B

[scotty]

ok, i'm in... add 50 units to the tally.

also, i didn't look too closely at the other posts so someone else might have explained this already... select seti@home as your winblows screensaver, and in the settings for it there make sure 'go to blank screen' is checked, and i put in 0 minutes. if you don't check this box, the cpu is wasting cycles refreshing the video. it cut my hours/unit almost in half.

now where is that et feller anyway???

[M Buuri]

But while at it you might want to use the command prompt version which is faster.

B

[scotty]

can you give us the seti@home site that has that version? i see a text only version for unix, nt, os/2, mac etc, but not for dos.

thx eh
8¬)

[Colin Morey]

the winNT-cmdline version works under win98.

[scotty]

cool, thx!

[agallag]

Yup, NT command line works in Win98 but not 95. It takes about 1/3 the time per work unit than the GUI version, and has almost no effect on the performance of your system when running in the background. I guess it's better at using idle cycles only.

Andrew

[Guyver]

Can someone post a link to our group? I'm getting timeouts trying to locate Matrox Users from home. D@MNED slow V.90 connections!!!

[mynx]

I found the command line version only slightly faster than the GUI. As long as they are both running in the background.