If you are unsure of whether or not you need to update your Drivers (unless you are seeing a specific error such as second monitor not detected), you can run a Drivers scan using a driver update tool (you will need to pay to register this tool but usually the Drivers scan is free). This will allow you to assess your Driver needs without any commitment. Alternatively, you can use the device manager to check if there are problems with any of your hardware devices.
windows xp 1080p monitor driver
Download: https://shurll.com/2vF5zn
* Disconnect the monitor USB upstream cable and any monitor audio cabling from the computer* Be sure that only one video cable is connected from the monitor to the computer. Either Display Port, Mini-Display Port, or HDMI* Uninstall any U2414H software (drivers, DDM Dell Displays Manager) you may have installed* Restart the computer. Does the error message appear?
What do you think my chances are that a paid support incident would result in my getting this Found New Hardware Wizard issue resolved?* Low. They would most likely want to you to format/erase the data from the hard disk drive, install the operating system, and drivers, and then connect the monitor without loading any monitor software.
Since this monitor only has HDMI and Displayport inputs, I have found that can be quite a limitation for Windows XP. I first tried with a GTX 760, figuring it to be a good choice to play any XP game at high framerates and detail settings, while having the bonus of that Displayport. I immediately ran into some issues, finding that anything above 3440x1440@60hz was out of the question. Even 60hz was sometimes dodgy it seemed. Knowing that Displayport 1.2 should be plenty for 3440x1440, I looked about and guessed that the Kepler cards had pixel clock limitations. I tried to scale it back, but the drivers were very picky about any resolutions in-between, accepting say 1080p but refusing to have anything to do with 1600x1200. This was new, because my main machine(with a 1080ti) has no problem at all with in-between resolutions, you can pick whatever you want up to the max resolutions.
If I get around to tackling the EDID again for trying to use newer graphics drivers than 355.98 (or HDMI ports) the below is interesting, I found the below while trying to figure out why in NTVDM in XP with my 980ti and my 2560x1440 (displayport) why all resolutions in NTVDM are scaled to 2560x1440 which is the native res of the monitor. Disabling the scaling options has no effect nor does NVSC Need to see what happens in real DOS but will likely be the same since in fullscreen you are talking directly to the card but mabye NVSC will work in DOS with this monitor and card. The scaling is fine just weird that you can't do anything with it.
the display switches from monitor mode to Interlaced HDTV mode where the font is fuzzy and the colors are fuzzy and cannot be used as a monitor. As I wrote in the previous post - on even newer drivers, e.g. 185.85, scaling options are not available and on the latest 307.83 there is no such option.
NVIDIA drivers work so that if they detect this extension, the scaling option does not work properly with the aspect ratio because they detect the display as a TV and not monitor and misinterpret the data from the CEA extension. In LG displays after pressing OK it is like this:
when the display works as a monitor it shows e.g. 1920x1080 @ 60Hz when the display works as HDTV it shows e.g. 16: 9 1080i 60Hz. To solve the problem, it is enough to disable the use of the CEA extension in Windows via the registry. You can probably edit EDID in the displays as well, deleting the second 128 bytes, some even allow this via HDMI cable, but it's safer to use the Windows registry. Tested on: WinXP Pro x86 SP2 NVIDIA 77.72 PCIe GeForce 6200 TurboCache (TM) graphics card display - native resolution FullHD 1920x1080, LG 22MT44DP DVI connection-HDMINajlepiej extract the driver 77.72_win2kxp_international_whql.exe and cancel the installation of the box, edit the file nv4_disp.inf , which will introduce this setting during the installation of the driver. We're going to need 4 bytes from our monitor's EDID at offset 8-11. This can be read in various ways, e.g. with the Monitor Asset Manager program , which should automatically read the EDID content of the active display after starting - see Display IDs , [Real-time ...] and Raw Data below : NVIDIA cards - Centered resolutions lower than native we open the .inf file in Windows Notepad in the [nv_SoftwareDeviceSettings] section, add the following entry: Code:
The registry entry causes the graphics driver to read only the first 128 bytes of EDID from the registry instead of from the monitor.I found helpful information here, where in both cases the problem was related to Windows Vista, NVIDIA card and LG display:image at resolution 1900x1200 is cropped and off-center DVI to HDMI LCD distortion problem using EDID tweak As you can see, the trick works on WinXP as well.
You probably meant DVI to DP.. because i have couple cheap working (for 1920x1200) DP (from graphics) to DVI (monitor), because there is important what is source and target, because they are not usually working vice versa. Im quite new in anything bigger than 1920x1200, i never was fried of high DPI, but 1920x1200 is dead.. and with lesser resolution was a bit forced to 2560x1440, i hope that i will life with it for lots of years as with three 1920x1200 mons. I have only monitors, but its just other feature of Nvidia drivers and anything connected through HDMI is considered as TV.
There are alot of combinations to keep in mind DP versions, HDMI versions, passive, active, drivers, OS, video cards, monitors, cable quality etc so try it keep it simple if you can. I use DP to DP @ 2560x1440 @ 85hz in XP and use the refresh rate lock tool for games that try to use higher than the max refresh rate otherwise I'll get a black screen (or I can switch to a SD/HD res which has a hard limit of 60hz). If I couldn't use DP then I'd have to settle for 1920x1080 or 1920x1200 @60hz with DVI. If you don't care about scaling then HDMI or DVI->HDMI can work and possibly you can try an old Nvidia driver version for working scaling with HDMI if your video card is supported on that old driver version, for the above I tested with a 980ti.
For the above I haven't done any testing since, I'm pretty sure it's a driver/OS issue since it all works fine in a newer OS on the same box. Never did get around to testing XDDM vs WDDM Nvidia drivers on Vista to test that theory. You can use XDDM drivers up to Windows 7 if you have time to test. I also never contacted that guy who made the Nvidia pixel clock patcher to patch Nvidia drivers to see how hard it would be to have an XP version. I think I also was going to look into seeing how high the basic vga or bearwindows drivers could go for testing but didn't bother with those since I wanted 3D but testing there could prove that it's a driver issue.
Attempting to summarize:1. Use a videocard and driver that doesn't have the scaling (Displayport/DVI/HDMI) and/or monitor out of sync (Displayport) and/or dynamic range via HDMI issues is the number 1 solution2. If you don't want to do #1 and are using an LCD monitor then use one that doesn't not exceed the limits of the buggy or unsupported driver. Your driver may be limited to HBR1 speeds. So no > 100hz (rough estimate 85hz is my limit) Displayport\HDMI\DVI @ > 2560. Ideally there should be an option on the monitor itself to set max refresh rate, I've never had one that could but maybe this is the solution.3. Using DVI or VGA from the video card is the easiest solution if you have those ports.3. If you don't want to do #1 and #2 but are using a monitor with high refresh rates and/or resolution then your monitor may show colored dots on a black background no matter what the refresh rate is set to on the desktop. Use an SD/HD resolution to limit max to 60hz (issue there is sometimes scaling options will disappear using this) or use refreshlock (use this!) to 85hz works for me BUT your monitor itself may not support the resolution you are switching to as well. For instance on my XB271HU it goes out of sync when running the dxdiag d3d 7/8 tests which run at 656x496@60hz but the d3d9 tests at 800x600@60hz work fine. I can create the 656x496 res in the control panel but I still can't switch to that res. The dxdiag d3d 7/8 tests run fine on my 1920x1200 monitor. I setup a displayport switch today so all I have to do is press a button to switch between both monitors.
Something I noticed today during testing indicates that the issue is not the port on the back of the card but the detection of the type of port used by the Nvidia driver:For instance:I can do HDMI->HDMI to DVI on monitor adapter on a monitor which shows up as DVI in the Nvidia Control Panel as well as shows up as a monitor with scaling.If I then using the same adapter do DVI to HDMI adapter->HDMI on monitor which shows up as HDMI in the Nvidia Control Panel as an HDTV with no scaling.If so then makes you wonder what the criteria the Nvidia driver uses and if there is a way to fool it that I've missed with the EDID emulator. Would be nice if there was a text file in the Nvidia driver with HDTV and monitor requirements, heh. Guess we need OSSC for modern ports. (Yeah I know it's an upscaler)Of course DVI->DVI works fine.Displayport to Displayport on this Dell monitor shows up as an HDTV but on my XB271HU it shows up as a monitor and works with scaling although max refresh at2560x1440 is 85hz and you'll need to use refreshlock otherwise games will try to use higher than 85hz causing black screens.
I did do some testing today with EDID emulators and even one that can emulate DVI but the overscan issue, 1080p limitation (you can't even do 1920x1200!) and HDTV issues persisted.I've ordered an active DVI to displayport cable that supposedly maxes out at 60hz (hopefully that is true) so will play around with that. If that works then would be able to plug DVI into any modern monitor and hopefully the nvidia driver decides the monitor is a monitor. Then I'll use displayport for Windows 11 and Linux on the same box and DVI to displayport for XP and below. If the adapter doesn't pan out then either DVI->DVI and hope the monitor never dies (2012 and still going strong!) or DP->DP w/ refreshlock. 2ff7e9595c
Comments