Messing with recently rec'd 3.2ghz with xp pro on top and seti via setidriver. I see the platform appears to treat the 3.2ghz processor as two processors--at least presented that way.
my question stems from the following: I am running two instances of seti/setidriver/setispy, each instance in a separate directory--treating it like a dual processor machine as I have yet to figure out how to dedicate the 3.2ghz to one instance of seti.
my problem, when one instance of seti finishes it sometimes locks-up the other or causes it to start over--zeros out the state.sah.
does anyone know what I missed? please tell me how to dedicate the 3.2ghz to one instance of seti or eliminate the cross-setidriver problem.
Thanks.
Richard
my question stems from the following: I am running two instances of seti/setidriver/setispy, each instance in a separate directory--treating it like a dual processor machine as I have yet to figure out how to dedicate the 3.2ghz to one instance of seti.
my problem, when one instance of seti finishes it sometimes locks-up the other or causes it to start over--zeros out the state.sah.
does anyone know what I missed? please tell me how to dedicate the 3.2ghz to one instance of seti or eliminate the cross-setidriver problem.
Thanks.
Richard