Reply 16860 of 18696, by the_ultra_code
DosFreak wrote on 2020-10-05, 18:38:
355.98 work for me on XP 32bit (with inf modified). Earliest I could find after that is 358.50 which has the monitor detected as […]the_ultra_code wrote on 2020-10-05, 04:52:
FYI, 352.86, or just any drivers before 353.X+, are the last drivers that properly show what monitor you are using and thus allo […]DosFreak wrote on 2020-10-04, 22:36:
980ti and Windows XP on a 27" 2560x1440 @ 85hz or LG 38" 3840x1600 @30hz monitor with scaling.
Took quite a bit of troubleshooting but finally identified the last good driver with scaling on XP w/ DVI or displayport.
FYI, 352.86, or just any drivers before 353.X+, are the last drivers that properly show what monitor you are using and thus allow you to use the "Adjust Desktop Size and Position" for that given type of monitor. Sadly, these drivers came out before the 980 ti AFAIK, so while adding a 980 ti's ID to the .inf file will allow you to install the driver, and from what I can tell it works perfectly find, in the Nvidia Control Panel and anything that looks at the NCP for specs and not directly querying the card for that information (like GPU-Z does), it will just say "Graphics Device" instead of "980 ti." Hopefully it's only a cosmetic issue.
You mention scaling, but I'm guessing you aren't referring to what I'm talking about, no?
355.98 work for me on XP 32bit (with inf modified). Earliest I could find after that is 358.50 which has the monitor detected as a TV issue. With the 355.98 drivers using DVI or displayport then the nvidia scaling, monitor scaling or no scaling options are available and work, any version past that has the issue. Next goal is to talk to the dev who made nvidia pixel clock patcher about what needs to be modified in these drivers to allow refresh rates past 85hz at 2560x1440 or 30hz at 3840x1660. On Windows 10 on the same box refresh rates go much higher.
For drivers past that I haven't had any luck with using overridedEDID, monitor drivers, mix and matching drivers.
http://www.codeground.net/howto/override-moni … using-registry/
Mabye if the driver can be modified to ignore CEA or the EDID changed on the monitor then mabye newer drivers can be used, I say that but when I connected a very old monitor from 2012 I still had the same issue so it likely can only be fixed in the driver, we just need someone who can debug these drivers.
I'll check this out later. It'd be nice if 355.98 work.