>We are unable to test the Diamond Viper V550 under Windows95 but having
>followed the threads of this problem suggest the following:-
>The Diamond Viper V550 driver is based on the nVidia generic drivers.
>The generic drivers seem to have the problem experenced by some Windows95
>users. Therefore it is possible that some Diamond drivers may have this bug.
>It seems that the Diamond NT drivers are OK.
>Checking the dates, the NT driver is October, the nVidia generic drivers
>are December. Is it possible the Windows95 drivers are based on later
>generic drivers than the NT version and the problem has been introduced.
>
Thanks, that helps a lot.
Sadly I don't like my chances of running my Creative Labs card off the
Diamond drivers :-}
I wonder if we can nail this to a particular driver version
I'm currently running NT under CL driver based on nVidias 0.48 driver
and I've also tried nVidias own 0.48 driver both exhibit the problem.
I think that for most cards the last 3 digits of the version number will be
the
nVidia reference driver that it is based on.
Does your working NT driver have such a version number?
James.
--
James Macgill
Centre for Computational Geography
School of Geography - Leeds University
Spell Checker (c) Creative spelling inc. (AKA my dyslexic brain)
=====================================================================
To subscribe/unsubscribe, send mail to [EMAIL PROTECTED]
Java 3D Home Page: http://java.sun.com/products/java-media/3D/
