(In reply to Michel D�nzer from comment #14) > That's unfortunate, but doesn't change that it's probably not a driver bug > and that you should get in touch with Dan Williams about it. Thanks just e-mailed him.