Oops.  Nvidia fixed this bug in one of the 35x versions.
I am almost certain it will have been fixed in 367.44.
(Just now, I don't have access to the relevant machine.)

Sorry not to have let you known---it took Nvidia about
6 months to respond.

Reply via email to