Barley wrote on Yesterday, 17:22:

Interesting! Especially for XP/7 dual boots!

I read the readme, but could not determine if this driver fixed the issues with custom resolutions, aspect ratios/gpu scaling, and detecting monitors as televisions. As a result of these issues, many use the 355.98 driver. Do you know if these issues were fixed?

Newest release addresses this should be at parody with 355.98

SupraGSX wrote on Today, 15:56:

I've validated it on a m4000 and 980ti so I know those work. Does the stock 368.81 driver work for you? What monitor do you have?

I'm testing on a 4k monitor at 60Hz max. The stock driver v368.81 works properly.

The GTX960 allows the max resolution of 3840x2160 @60Hz on the HDMI port with the driver versions 355.98, 368.81 and 368.91 after modifying nv4_mini.sys and nv4_disp.dll.
Here an image uploaded some months ago:
https://ibb.co/c7317jF

Andalu wrote on Today, 16:14:

I'm testing on a 4k monitor at 60Hz max. The stock driver v368.81 works properly. […]
Show full quote

SupraGSX wrote on Today, 15:56:

I've validated it on a m4000 and 980ti so I know those work. Does the stock 368.81 driver work for you? What monitor do you have?

I'm testing on a 4k monitor at 60Hz max. The stock driver v368.81 works properly.

The GTX960 allows the max resolution of 3840x2160 @60Hz on the HDMI port with the driver versions 355.98, 368.81 and 368.91 after modifying nv4_mini.sys and nv4_disp.dll.
Here an image uploaded some months ago:
https://ibb.co/c7317jF

Interesting are you positive the new install overwrote the older version? Since they're both 382.69 version numbers it could cause a situation where the driver already thinks it's installed is my only guess. The behavior you're describing of a blank display was present in the first driver and I could reproduce it on HBR2 cards. It was caused by the fallback for HBR3 detection not being implemented well enough (originally I built this to run a 1080ti at HBR3) Since I decided to release it publicly I'm fixing some of those bugs. In my testing the 10-3-26 version negotiates down to HBR2/HBR/RBR properly now. Unfortunately, I can only test on my monitor which is the Alienware ultrawide qd-oled. For HDMI there's a 594mhz cap which is HDMI2.0 but it should negotiate down properly as well now. I never had problems getting 3440x1440 at 100hz on either of the released drivers using HDMI on a 980ti so that's even more odd.

SupraGSX wrote on Today, 16:45:

Interesting are you positive the new install overwrote the older version? Since they're both 382.69 version numbers it could cause a situation where the driver already thinks it's installed is my only guess. The behavior you're describing of a blank display was present in the first driver and I could reproduce it on HBR2 cards. It was caused by the fallback for HBR3 detection not being implemented well enough (originally I built this to run a 1080ti at HBR3) Since I decided to release it publicly I'm fixing some of those bugs. In my testing the 10-3-26 version negotiates down to HBR2/HBR/RBR properly now. Unfortunately, I can only test on my monitor which is the Alienware ultrawide qd-oled. For HDMI there's a 594mhz cap which is HDMI2.0 but it should negotiate down properly as well now. I never had problems getting 3440x1440 at 100hz on either of the released drivers using HDMI on a 980ti so that's even more odd.

I just tested both Forceware releases on a different XP system and monitor (34" widescreen 3440x1440@144Hz) with a GT730 (GK208B) card.
In both cases the max resolution is 1920x1080 on the HDMI port. Here is an image with the first Forceware release:
https://ibb.co/v6yQFT4J

To avoid any problems, I run the tests on a fresh XP install.

Pascal cards tested had their firmware updated or not ?
Source : LINK

4K60hz and 1440p120hz are working on a 980ti + Windows XP sp3 32bit + Forceware.382.69.exe (version from yesterday). 3dMark2003 and 2006 runs fine.
https://ibb.co/KzsdGzSG

agent_x007 wrote on Today, 18:56:

Pascal cards tested had their firmware updated or not ?
Source : LINK

Thanks for the tip. My GTX960 has already the updated firmare. I checked again just to be sure.
In the next few days, I'll check to make sure the Pascal cards also have an updated firmware. My goal now is to find a way to get 3840x2160 @60Hz also on the DP port for my GTX960 with the Forceware driver .

Andalu wrote on Today, 17:51:

I just tested both Forceware releases on a different XP system and monitor (34" widescreen 3440x1440@144Hz) with a GT730 (GK208B […]
Show full quote

SupraGSX wrote on Today, 16:45:

Interesting are you positive the new install overwrote the older version? Since they're both 382.69 version numbers it could cause a situation where the driver already thinks it's installed is my only guess. The behavior you're describing of a blank display was present in the first driver and I could reproduce it on HBR2 cards. It was caused by the fallback for HBR3 detection not being implemented well enough (originally I built this to run a 1080ti at HBR3) Since I decided to release it publicly I'm fixing some of those bugs. In my testing the 10-3-26 version negotiates down to HBR2/HBR/RBR properly now. Unfortunately, I can only test on my monitor which is the Alienware ultrawide qd-oled. For HDMI there's a 594mhz cap which is HDMI2.0 but it should negotiate down properly as well now. I never had problems getting 3440x1440 at 100hz on either of the released drivers using HDMI on a 980ti so that's even more odd.

I just tested both Forceware releases on a different XP system and monitor (34" widescreen 3440x1440@144Hz) with a GT730 (GK208B) card.
In both cases the max resolution is 1920x1080 on the HDMI port. Here is an image with the first Forceware release:
https://ibb.co/v6yQFT4J

To avoid any problems, I run the tests on a fresh XP install.

Does it accept a higher custom resolution?