francisco wrote: > > Easy to answer, because this happen in rc2 with both, tuxracer 0.6.11mdk (from > rc2) and tuxracer 0.6.10mdk (from 9.0) runing under rc2 and doesn't happen > with any of both tuxracer releases under 9.0. > > You can run tuxracer under 9.0 without any problem; the rpms of Nvidia are > those of the mandrake powerpack. > > So it must be a nvidia new release problem, mustn't it > > El Mi�rcoles, 5 de Marzo de 2003 20:38, Adam Williamson escribi�: > > On Wed, 2003-03-05 at 19:22, francisco wrote: > > > This is exactly the same driver I have used. Tuxracer plays well except > > > some of the races, for example the one I have mentioned. Chromium is > > > runing without problems and even more, the whole commercial Tuxracer is > > > runing fine. > > > > In which case, why did you confidently conclude the bug was in the > > NVIDIA driver?! Seems far more likely to be a bug in tuxracer... > > -- > Francisco Alcaraz Ariza > Departamento de Biolog�a Vegetal > Universidad de Murcia > E-30100 Murcia > Espa�a (Spain)
You are certain it isn't something else, like one of the many library changes? There wer many things broken by the glibc change, and many packages had to be rebuilt to work properly. Perhaps this is another case of that problem. The fact that an executable runs on 9.0 doesn't mean that it won't have a problem on 9.1. As I said, I have run some very demanding programs with the Nvidia drivers on cooker, and not had any problems. I still think the Nvidia drivers are pretty solid. I think you need to look elsewhere for the problem. Paul
