> > I think that all reports with systems that overclock to a known value > > should silently be included in the data set(s). > >it shouldn't -- it's known that it might disrupt stability. if you want to >be certain what causes the lockups, reduce the set of variables. > >if you don't , you might as well count in all hardware rash related stuff >like f* up memory modules etc etc. No, because overclocking has already been ruled out as the possible cause of the problem. Though it may "cloud" the results slightly, the alternative solution would be too restrictive a sampling. A *lot* of people purchase an Abit system and overclock it. It is not only accepted practice, but also expected. It makes more sense to have 500 samples in the group, with the majority overclocked, than to have 5 samples in the group, all non-overclocked. Regards, Dennis ______________________________________________________ Get Your Private, Free Email at http://www.hotmail.com -- =- To unsubscribe, email [EMAIL PROTECTED] with the -= =- body of "unsubscribe linux-abit". -=
