cool. I finally d/led it after a year of putting it off. pretty sweet. although my overclocked cpu went to 41C (it is aircooled right now). wahho 'im 6% done my data unit
-----------------
"648kb is all the space anyone will ever need!"
What's that? Did you just delete s@h off your system or did you just start running it after a year. Me no understand you.
If you did just start running it we could use you on the team. We are just about to make the top 200 for clubs.
<A HREF="http://www.seti.tomshardware.com" target="_new">Join The Tom's Hardware SETI@Home Team</A>
35 hr 49 min..... How come it took you so long to complete this wu? What type of system are you using? Are you using the screensaver or cmd line version?
<A HREF="http://www.seti.tomshardware.com" target="_new">Join The Tom's Hardware SETI@Home Team</A>
Ahhh,
The screensaver would do it. If you are yousing the gui version set it to go blank and disable the screensaver.
Or you could start using the command line version and start kicking some a-s. It's not as pretty but it is a lot faster.
<A HREF="http://www.seti.tomshardware.com" target="_new">Join The Tom's Hardware SETI@Home Team</A>
You can get the cmd line version <A HREF="http://ftp://ftp.cdrom.com/pub/setiathome/setiathome-3.03.i386-winnt-cmdline.exe" target="_new">Here</A>
The cmd line version has no graphics so it dosn't tell you what your % completed is or anything. A good tool to use with it is <A HREF="http://pages.tca.net/roelof/setispy/" target="_new">setispy</A>
After you download the cmd line version put it in a folder and excecute. Also put setispy in the same folder. The rest is pretty straight forward. You might want to put a shortcut to the cmd line in your startup folder.
Let me know how it works out. That should get you pumping out wu every couple of hours.
<A HREF="http://www.seti.tomshardware.com" target="_new">Join The Tom's Hardware SETI@Home Team</A>
Glad to hear that.
Do you have a constant connection to the internet for your pc? If not there is also a caching program, so that there is less idle time while waiting to connect to the internet.
<A HREF="http://www.seti.tomshardware.com" target="_new">Join The Tom's Hardware SETI@Home Team</A>
Actually, the command line version isn't any faster than the gui if you keep the gui version in the systray only (ie, no graphics at all). I run a linux cli and a winME gui on my dual booted machine, and the times are pretty much the same (providing of course for differences in the work units themselves).
This V3.03 takes a lot longer than the previous versions though. I was running at around 4.5 to 5.5 hrs per wu, now i'm up to 7.5 or so.
I would have to disagree. My experiance has been a average of a couple of hours difference. And that was with the screen saver off, set to blank screen (just in case) and always running. compared to the cmd line.
So I wonder how long until this gets moved to the Distributed Computing forum.......
<A HREF="http://www.seti.tomshardware.com" target="_new">Join The Tom's Hardware SETI@Home Team</A><P ID="edit"><FONT SIZE=-1><EM>Edited by scarecrow on 04/08/01 01:26 PM.</EM></FONT></P>
That's because you had the graphics running. If you re-read my post, I said that it takes the same time provided the graphics aren't generated. (ie, the gui version is minimized to the systray and the screensaver is disabled). You said that you're getting times of about 10hrs on your 1GHz Athlon C on the cli. I'm getting 7.5 to 8.5 hrs on my Tbird 900@1050 on both my WinME gui and Linux cli versions.
Heh, that's half the time that you were generating graphics then. Trust me, there is no difference between the two versions.
The units start off and end really quickly for me. The highest I've seen is about 350 MFlops and 2.9 cpu cycles/Flop at the beginning of a unit, and I've seen estimates for a 3 hour time. But it slows down in the middle for some reason.
You are about to answer a thread that has been inactive for more than 6 months. If you still wish to proceed, please ensure that your posting is original and does not duplicate or overlap any prior responses to this thread.