>Could I respectfully point out that the windoze screensavers run at >priority 4. If you raise Prime95/NTPrime's priority to 4, you will >split CPU time more or less evenly between the screensaver and the >Mersenne client. In fact there should be a bit more going our way >than the screensaver does; the screensaver does voluntarily >relinquish the CPU occasionally - otherwise a client running at >priority 1 would get nothing. A while back I set the priority for Prime95 to 5 at night and left it at 1 during the day on several PCs. In some cases in helped tremendously but in other cases it had no effect whatsoever. I don't remember if that correlated with machine type, OS or screensaver type; it was quite some time ago. I may revisit that and look for a pattern. I do remember one in particular, the "win95" screensaver running on a pentium pro with Win95 OS brought Prime95 almost to a dead stop, but changing the priorities at night slowed the screensaver so much you could barely see it move while Prime95 ran almost at optimum speed. I remember that one because it was the most successful implementation of the resetting of priorities. Others ranged from some effect to no effect. I believe the least successful were some screensavers which did not come with windows but were downloaded from elsewhere; but I am also sure there were some that came with the OS that were just as bad. Steve Harris _________________________________________________________________________ Unsubscribe & list info -- http://www.scruz.net/~luke/signup.htm Mersenne Prime FAQ -- http://www.tasam.com/~lrwiman/FAQ-mers
