NVIDIA Quadro/Tesla/SDI/Notebook DRIVER RELEASE 296.35 WHQL

[StefanG3D]

This is a reference driver that can be installed on supported NVIDIA notebook GPUs. However, please note that your notebook original equipment manufacturer (OEM) provides certified drivers for your specific notebook on their website. NVIDIA recommends that you check with your notebook OEM about recommended software updates for your notebook. OEMs may not provide technical support for issues that arise from the use of this driver.

Before downloading this driver:

Please check to make sure that your notebook has a supported GPU (refer to the Products Supported tab below).

It is recommended that you backup your current system configuration. Click here for instructions.

If you own a Dell Inspiron 1420, Dell XPS M1330, Dell XPS M1530, or Dell Latitude D630/D630c it is highly recommended that you first install this Dell software update.

RELEASE HIGHLIGHTS :

New in Release 296.35:

Adds support for Notebook Workstations.

ODE Driver

The R295 drivers are the second ‘Optimal Drivers for Enterprise’, a release dedicated to relatively long term stability for ISV certification, OEMs, and Enterprise customers.

Added Support for OpenGL 4.2 on the Quadro series cards and higher.

Added Support for CUDA 4.1

Added support for the Open Computing Language (OpenCL) 1.1 in Quadro FX Series x700 and newer as well as the FX4600 and FX5600.

NVIDIA Control Panel Manage 3D Settings Page

Added Preferences tab which lets the user control the application profile notification feature.

Upon launch of a windowed 3D program, this feature causes a popup to appear notifying the user which workstation application profile was applied.

256GB Virtual Space

OpenGL and CUDA users can now take full advantage of applications that utilize 256GB of system memory

Workstation application compatibility fixes. Please read the release notes for more information on product support, feature limitations, driver fixes and known compatibility issues.

[tribaljet]

Has anyone tested this driver yet? I'm curious about the reliability this sort of drivers usually have, and if by using a modified .inf, there might be any changes to that situation.