• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Linux, NT4 or Win2k?

Slaughter

Senior member
Ok so I have this dual Pentium Pro 200@233 with 128megs. My question to you is, which OS will run SETI@home faster? Linux, NT4, or Win2k? I'm runing linux on it now and its not pumping WUs like I thought it would, which is what that Time calculator told me. I was expecting sub-24 hour WUs, but I'm going like 28-32 hour WUs. Would any of these alternatives run it faster?
 
Not an expert of SETI, but I belive linux cmd-line client is slower than the w32 client which is run under wine?
 
Originally posted by: Slaughter
WINE is not an option, frankly, becuase I don't run a GUI on anything. Text based all the way! Now which? 😀

Ok, well that eliminates NT/2K so where's the question? If time is your primary concern, then I would suck it up and run WINE. If not, then run 2K and you're back on the GUI boat.


 
If you are asking what is the fastest ways to run Seti@home:

1) Win CLI running on WINE in Linux
2) Win CLI in Win2K
3) Win CLI in NT4
4 Linux CLI in Linux

The difference in speed between the Win CLI on WINE in Linux and Win 2K with Win CLI isn't very huge so for my choice I had plenty of Win2K licenses so I went with Win CLI in Win 2K.
 
18-20 hour wu's running Win2k, dual PPro 200/1meg @ 233mhz 320 meg of ram on a SuperMicro P6DNF m/b. 26-30 hours per wu running Linux i686 cli.
 
Wine can run without X, though some people have had more success than others.

Here's a link to a google search I did. Check out the first few responses.

It CAN be done, though with a mixed rate of success.

Good luck! 😛
 
Back
Top