Matrox G200ew Driver Windows 10 64-bit
Pernille Pennebaker
Thanks for this tip. You are great!
My PowerEdge T310 arrived to me today, and of course there is same issue with Matrox G200eW. I made changes in inf files, reinstalled driver, and tomorrow I will check, if it would work (I made changes via remote session, so I cannot change resolution remotely). I hope it would do...
Best regards.
Yeah, these guys at Google did pretty good job. ;-)
Actually I was about to put there some GeForce or something, but I Was certain, that there had to be a way to force this card to work with wide screen resolution. I do not have to much to deal with Matrox cards, so your entry helped a lot. I am just wondering how it is with it's performance. Honestly, Windows 2011 GUI in 1280x1024, besides it looks really poorly displayed on wide screen, it works sloooooowly. Maybe it is the reason, why Dell locked resolutions higher than 1280x1024.
Regards,
Bartosz.
Two .inf files are located in folder, where your driver installation is unpacked. Where you run setup.exe. You must modify these files, and reinstall driver. I did so, and it worked. If you cant find this folder, just download package from Dell page.
I found the two files in the unpacked setup folders, and I added in your values. I go through the driver re-install, reboot and I still get the same 2 resolutions. 800x600, 1024x768. I've done it several times, but same results. It's driving nuts. This the drivers I'm using MATROX_G200EW-VIDEO-CONTROLL_A02_R231494.exe
Maybe you did something wrong.
Here you have these two *.inf files modified by me according to Michael's advice:
They do work, because I used them for driver installation on my machine. One thing - I suppose, that they are for 64 bit driver version (x64 in filename). If you are going to use 32 bit system, you will have to modify another files...
I really appreciate your help, but I'm not gonna spend any more time on this. I've done exactly what you did, but still no luck. I am using the 64-bit drivers and I even tried using the two inf files from your rar archive. Restart the machine same 4:3 resolutions.
Thanks for trying.
The onboard video on these servers have a dedicated 8MB of memory. 8mb!!!
My watch has more than that.
Would it hurt to give the video 512 mb of ram?
You pay thousands of dollars for a well configured flagship server and end up with video that would have been installed on an old 486 machine.
Perhaps video would look much better if you could assign more memory to it.
Thanks for the fix, it does indeed work. Only issue i had was when the VGA was removed it reverted back to the 1200 resolution. Re-installing the modified drivers brings it back. Thanks for the temp fix anyways!
didinskee,
Can you email me the setup file? Dell.com says info for that file is unavailable, check back later. My email is larse...@integratedsecuritycorp.com
Thanks if you can do it.
many thanx for your info OP. however, seems that win7 x64 systems will not play with this res hack... using the same dell driver discussed here "R231494"... completely removed all instances of the installed sys files before trying the reinstall... also tired using the two inf's from ( ) here in addition to doing manual edit, still no dice. anyone else confirm this does NOT work with win7 x64
Thanks for the info. I have a new PowerEdge T310 server and Dell is still using the Matrox G200eW. The drivers from Dell still do not include any widescreen resolutions and no support from Matrox. In fact, there's not much available on Matrox cards and custom resolutions out there. I found nothing on the Dell forums about this. It's like other people are not using widescreen monitors on their Dell servers. I tried many ways to get 1440 x 900 without 3rd party software without any success. I applied your tweak to the .inf files, reinstalled the driver and I've got 1440 x 900 as well as many others. I'm running Server 2008 R2 x64. Many Thanks!
I used the same driver as the guy before me, R231494. After expanding the executable to C:\Dell\Drivers\714DR, I modified two .inf files, s03x64.inf and S08X64.inf in that directory. I take it they are for Server 2003 and 2008 respectively. I modified them both and all went well. Reinstall the driver by running setup from the same directory. Choose overwrite Matrox drivers when prompted if there's been a previous installation.
I've had plenty of resolution problems with KVM switches and the like. Whatever you're running through has to emulate the direct connection or you may be able to shut off auto detection of the monitor depending on the OS. Vista and older can do it. Windows 7, I don't think so. Google search it.
I've got no further with this.
From all I have read auto detection can not be disabled on Win 7 like older OS.
A better KVM will pass EDID but what happens when the monitor is switched to another computer? Will this computer with no monitor connected drop back to a lower resolution once Win7 notices no monitor is connected?
Hi, i have matrox gw200e2 on x9scm-f with Windows Server 2012. I've got different drivers for this and i get through many combinations. Right now i can pass installation without any error after i have turned off Digital Driver Signing. but still no success getting 1920x1080. Resolution. I found somewhere info that Windows8/2012 don't support 16bit. Is it possible to install this driver @ 1920x1080x32?
hi
Thanks for finding out nice solution for g200ew, I am facing same resolution problem with matrox g200eR with my ibm x2500 m4 machine. Can somebody please guide me how can i get 1920*1080 resolution. I am very much tired with this dumb resolution on my widescreen monitor please help..
Great resource here - appreciate it!
I confess not reading further about the registry mod after the driver failed the install with the.inf changes. Matrox G200eR on a T320 btw. (Installed a new card instead - may go back and retry the reg update next visit though.)
Hey there.
I'm not a IT-savvy guy - so maybe my question is totally dumb but:
Do you think there is a way to run the graphics driver on Win10 installation?
All the drivers I tried don't work.
I also have the issue that I'd like to use a 1920x1080 screen on a discharged PowerEdge T110II server with Matrox G200eW that now should run as a desktop computer.
Hi all, December 2016, W7 x64 install on a T110 - can report that this solution still works great!
Except that for some reason the S03 / S08 files I downloaded from this thread were rejected by the driver installation script, so I had to unpack the driver again and go copy-pase the resolution section into each of the original files manually, THEN it worked.
Didn't work on T320 WinServer 2008 R2. After edit the driver package inf file and reinstall it, 1920x1080 resolution is appeared on the resolution list but when I select and apply it, windows crashes with a blue screen :(
Did the mod on a Supermicro X8SIL and it worked perfectly. Of course, you are not going to get 32-bit colour because that takes twice as much memory as 16-bit colour, and probably more than the chip has available. Hence the blue screen, I think.
It did take a couple of reboots, and some fiddling with the advanced properties, but it worked easily enough. If you get the message about driver not being signed, then you're on the right track. Of course with anything much after 2008R2/Win7 you're going to have to take more extreme steps to be allowed to install an unsigned driver (which your INF file now became because you altered it).
Certain anti-cheats kick the player from game because of "untrusted system file", for example EAC does so for the game Rust since a recent update. It seems to be at the game developers' discretion, as some EAC-powered games have suffered from amdihk DLL in the past.
There are good technical reasons for anti-cheats of a variety of games to desire blocking unsigned/untrusted driver files in the system32 and system driver folders. I can know, as an anticheat developer (from another game) myself.
AMD, or any driver publisher, should NEVER ship unsigned driver files. "AMDIHK64" (AMD DVR component) is, as far I know, the only of such file that lacks a digital signing certificate. It's not just not valid, but completely absent, throughout recent releases of Radeon software.
Its not just anti-cheats that are affected, there are obvious reasons why DLL files of known, major (driver) software that are placed in system folders need to be signed. A lot of software can do trust checks and eventually fail. For the anti-cheat of popular games using EAC, you have now impacted hundreds of thousands of users, and they may decide to manually remove amdihk DLL file in safemode, leading to them not benefitting from AMD DVR functionality.. just in a bid to play the game. This isn't ideal.
Again, software/driver publishers should have developers that know what proper project practise is. Shipping out 99% valid signed DLLs and a single or a few unsigned files, is bad practise. Under correct practise, no issues like the anticheat one would arise. The solution is obvious.
Please note that I was able to reproduce the problem by a clean install of Windows 10 build 1903 and immediately installing the latest Radeon Adrenalin software package; ATI drivers really place that unsigned file into your system32 folder, it's not corrupted or infected, it's not our PC's, it is AMD doing that by mistake.
c80f0f1006