• 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.

Win2K Or WinXP For SETI@Home?

Has anyone run a straight comparison of these two for crunching WU's? I have a ThinkPad coming in a day or two with Win2K on it, and I am wondering if I should upgrade to WinXP or not.
 
Don't know on the speeds, don't have an XP box to compare.

But, what processor are you getting in that Thinkpad?

If it is a PIII, it may be a tualitin core with 512K cache and you are looking at 5hr30min average WU times in Win2KPro with nothing else going on. 😀
 
It is a PIII Mobile with the Power Saving Technology. A bit more than the ThinkPad's with the basic PIII's, so it may well have a Tualatin core.
 
A *HUGE* bump because I'm interested in the answer to the original question.

I'm wondering if an upgrade from 2K to XP would be worth it for SETI.
 
I kept having problems running seti on XP (PC kept rebooting after a few minutes after a win32k.sys BSOD). Went to W2K Adv Server and it was running fine. Got a new heatsink/fan and even am o/c now and it's still running fine.

<shrug>
 
I switched from W2K Pro to XP Pro and there was a neglible difference when looking at 20 or so WU's under XP--not more than a couple of minutes and that may be due to angle differences. The only problem I have encountered are occasional (5%?) crashes of Seti Spy when rebooting, but a manual restart of Seti Spy always works fine. Setting Seti Spy to run in W2K compliant mode and disabling visual themes helped with the crashes.
 
Back
Top