dabult
Thu, 30 May 2002 09:46:35 -0700
Im running an XP1700+ aswell, and i got Win2k going. Are you sure youre not overexaggurating that time? "3 hrs-1Wu"...I rarely go sub-4hrs, 1 out of 10 goes faster than 4 at best.
Back to topic :) Maybe (and probably) you already know this, but have you made sure Seti Driver is set to 'low' client priority? I had it running for a month after i got my new comp (this one even) and a lot of progs kept on freezing, annoying as hell. Then someone told me that and 'voila', works like a charm ever since :) I dont know jack about XP tho :/ ----- Original Message ----- From: <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Thursday, May 30, 2002 4:51 AM Subject: AURGH!!!!! > > Im having a bit of a problem. > I just got an AMD Athlon XP 1700+. > It just plain whips up some ass with seti (1wu/3hrs) > I figured id install WinXP as well, with my new cpu and mobo (abit) > ofcourse i wanted stability so i formated with NTFS on my windows partition > and fat32 on my backup partition > > Heres where the problem comes in, > seti keeps locking up my system!!!!! > i close seti everything is fine > i let seti run and within a few hrs it locks up > im using Seti Driver and seti cmd 3.03 > nothing else runs on boot but what Windows tells to on install and seti > > any ideas? > == > Unsubscribe instructions: http://www.talkspace.net/mlists/setiathome.html > This list sponsored by talkspace.net: building space communities online. > Mailing list services provided by klx.communications -- www.klx.com > > == Unsubscribe instructions: http://www.talkspace.net/mlists/setiathome.html This list sponsored by talkspace.net: building space communities online. Mailing list services provided by klx.communications -- www.klx.com