LCD SEC3255=1600x1200 shows only 1400x1050

January 28, 2005

Teraphy, you're my MAN!! :)

I also went for the whole EDID data in my override line. It appears that Carriage Returns are not digested well by the installer. Is that right Teraphy? After removing them the 67.66 install went perfectly. I opted to modify Bill's INF for 67.65 based on the original Dell INF and add Pieter's 67.65 optimizations from the 30.53p INF. I popped in my corrected override line for the SEC3255 and it finally squeaked!

;>>>  Fix for the SEC3255 Samsung UXGA ASV panel problem!
HKR,, OverrideEdidFlags0, %REG_BINARY%,
3A,C4,00,03,00,00,FF,FF,04,00,00,00,00,
7F,00,ff,ff,ff,ff,ff,ff,00,4c,a3,55,32,00,00,
00,00,00,0c,01,03,80,1e,17,78,0a,ad,71,
96,57,52,89,27,23,50,54,00,00,00,01,01,
01,01,01,01,01,01,01,01,01,01,01,01,01,
01,48,3f,40,f0,61,b0,32,40,40,80,6e,11,
30,e4,10,00,00,19,00,00,00,0f,00,00,00,
00,00,00,00,00,00,19,af,02,32,00,00,00,
00,fe,00,32,52,32,39,30,32,31,35,30,55,
32,0a,20,00,00,00,fe,00,e2,b4,93,77,4e,
2e,0f,00,02,0a,20,20,20,00,79,00,00,00,
00,00,00,00,00,00,00,00,00,00,00,00,00,
00,00,00,00,00,00,00,00,00,00,00,00,00,
00,00,00,00,00,00,00,00,00,00,00,00,00,
00,00,00,00,00,00,00,00,00,00,00,00,00,
00,00,00,00,00,00,00,00,00,00,00,00,00,
00,00,00,00,00,00,00,00,00,00,00,00,00,
00,00,00,00,00,00,00,00,00,00,00,00,00,
00,00,00,00,00,00,00,00,00,00,00,00,00,
00,00,00,00,00,00,00,00,00,00,00,00,00,
00,00,00,00,00,00,00,00

We should definitely pass on the great news to the other poor Samsung panel owners.

Especially in the Dell Video forums for Inspiron & Latitude where most are still stuck at 42.58.

I'm really amazed that the nVision gurus were able to crack this nut so effortlessly. :) Great team here Teraphy & Pieter!

@Bob the Dino: I don't know how old your Samsung display is, but mine was manufactured in 2002 according to the Phoenix program I posted further up.

January 28, 2005

All Kudos to Teraphy for this fix, I just pointed you here Doug at the right time.

All good timing on everybodies part.

How about a post on the Dell forums for the masses to see.

I don't normally like to post in forums about our forums (courtesy) but in this case I think it's appropriate seeing Dell is a OEM forum, and they have no idea of how to fix it.

Once again well done guys, quite a coup

January 28, 2005

Glad it worked :)

Darmdorf, you don't need all of those zeroes trailing the 79.

Enjoy the new versions :)

January 28, 2005

According to the program, mine was made in 2003. I just got it replaced (luckily under warranty still :) ), so its probably also rebuilt. Your EDID also worked for me as far as I can tell, so I guess it doesn't make that much of a difference which one is used.

January 29, 2005

I'm one happy camper now as they say, and so very grateful to all of you:

Bob the Dino for starting this thread and being a great interactive partner and asking the right questions and providing the right information,

Teraphy for being our host here, not scoffing at our silly questions, and most of all for being a true expert worth his weight in gold,

and of course Pieter for being a good friend and my "light in the dark".

Yesterday was indeed a great day for Dell users everywhere, and puts us right up there in Nvidia heaven with the Toshiba patrons.

Darmdorf, you don't need all of those zeroes trailing the 79.

Thanks again for the expertise. That means any non-stated parameter values always default to 0? OK, very handy in this case.

So, who wants to go to the trouble to post to the Dell forums? I think Teraphy is pretty much predestined to do it right. I'll see if I can't post something appropriate in the German forum I used to frequent. If I have this right, all one needs for the repair is to place the 'override' line somewhere in front of the mode parameter in the INF?

@Bob the Dino: My Samsung was also a warranty replacement for a warranty replacement back in March of 2003. The first one wasn't the ASV model and I asked Dell support for the correct one. Maybe I should have gone with the Sharp?

January 29, 2005

Darmdorf, welches German Forum ist das?

January 30, 2005

I was referring to the Notebook-Forum.DE.NR where I used to be an admin for the Dell area. Just looked, thank goodness they haven't killed my account since I've been away for quite some time now -- priorities changed. I was the one to ask Pieter to include them here in the Links. It's become a real powerhouse in the notebook sector [with almost 2800 registered members], and Pieter's site was also popular there too. They cover a very broad range of notebook brands and are a very diversified and nice crowd. I can recommend them highly. :)

I hope Teraphy comes back with an answer soon, so that I don't run the risk of telling the local Germans something false. :)

Have a nice sunday in Berlin. The Bergstrasse is warming up a tick.

January 31, 2005

The binary key for the registry requires all of those 0's but the EDID and the key for the INF do not require that many 0's. I placed the final one at the top removing the last byte -- 79, as this is the driver calculated CRC value.

As you have been away from the German Notebook forums I equally haven't been visiting the Dell forums for similar reasons. :)

April 16, 2005

Hi guys,

I'm having the same nightmare with my PC, I want to install 67.55 but I'm not sure which inf file I paste that code into, and where exactly, as I thought I'd done it right but had the lovely rainbowy 1400x1050 appear at me again.

Can you give some clear instructions for a poor tweaking n00b?

Where exactly do I paste that code, and in which .inf file in the 67.55 directory?

:)

April 16, 2005

Paste it into Pieter's mod INF for 67.65 or his performance INF for 67.65.

You probably mean the 67.65 driver?

If you really do have a 67.55 driver we would love to have it......

You should delete all INFs in the directory and then put in one of Pieter's INFs, then go and change this section to look like this:

[nv_SoftwareDeviceSettings]
HKR,, InstalledDisplayDrivers,    %REG_MULTI_SZ%, nv4_disp

HKR,, Acceleration.Level, %REG_DWORD%, 0

HKR,, MultiFunctionSupported, %REG_DWORD%, 1

HKR,, NvCplEnableHardwarePage,    %REG_DWORD%, 1

HKR,, OverlayMode2, %REG_DWORD%, 0xF00050

HKR,, OverlayMode3, %REG_DWORD%, 0x10400001

HKR,, OverlayMode4, %REG_DWORD%, 0x3

HKR,, RotateFlag, %REG_DWORD%, 4

HKR,, UseBestResolution,    %REG_DWORD%, 1

HKR,, VgaCompatible,    %REG_DWORD%, 0

HKR,, OverrideEdidFlags0, %REG_BINARY%,

3A,C4,00,03,00,00,FF,FF,04,00,00,00,00,7F,00,ff,ff,ff,ff,ff,ff,00,4c,a3,55,32,00

00,

00,00,00,0d,01,03,80,1e,17,78,0a,ad,75,96,57,52,89,27,23,50,54,00,00,00,01,01,

01,01,01,01,01,01,01,01,01,01,01,01,01,01,48,3f,40,30,62,b0,32,40,40,80,6e,11,

30,e4,10,00,00,19,00,00,00,0f,00,00,00,00,00,00,00,00,00,19,af,02,32,00,00,00,

00,fe,00,4d,31,36,33,35,02,31,35,30,55,32,0a,20,00,00,00,fe,00,e6,d6,c0,a9,8a,

67,43,00,02,0a,20,20,20,00,38

HKR,, NV_Modes, %REG_MULTI_SZ%, "{*}S 320x200 320x240 400x300 480x360 512x384 640x400=1FFF;SHV 640x480 720x480

768x576 800x600 1024x768

1152x864 1280x720 1280x768 1280x800 1280x854 1280x960 1280x1024 1360x768 1366x768

1400x1050 1440x900 1600x900 1600x1000 1600x1024 1600x1200 1680x1050 1920x1200 1920x1440

2048x1536x8,16,32=1FFF"

HKR,, DCBOverride0, %REG_BINARY%,   04,25,00,22,18,20,10,01,00,02,b8,88,00,00,00,02,01,01,b8,88,00,00,02,02,11,02,

00,00,00,00,02,01,11,02,00,00,00,00,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,f

f,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,

f,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,3f,3e,00,00,

37,36,00,00,51,50,00,00,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff

,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

HKR,, DCBOverride1, %REG_BINARY%,   04,25,00,23,09,20,10,01,00,02,b8,88,00,00,00,02,01,01,b8,88,00,00,02,02,11,02,0

0,00,00,00,02,01,11,02,00,00,00,00,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,

f,ff,ff,ff,ff,ff,ff,f

f,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,

f,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,

ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,3f,3e,00,00,

37,36,00,00,51,50,00,00,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

ff,ff,ff,ff,ff,ff,ff,ff,ff

,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff,ff

[Mobile_Tweaks]

I made the section headers bold, those are what you look for, the override tweak is also bolded, that is what you add in.

I hope I explained it correctly....

Bill

April 16, 2005

:)

... without the breaks. It must be one continouos line. :)

April 16, 2005

I copied the tweak directly from your edit in the first post, I also tidied up the nv_modes section so my post would not span like 2 sreens horizontally.

For the guy that is putting that in, copy it from the first post and add it in the INF with no breaks, don't copy what I put, that is just for reference.

Edit: Glad you got it working, as usuall I get no respect. (see ®®®'s post below)

lol j/k ®®®.

April 16, 2005

Hi guys,

:P

IT'S WORKED!

:)

I am delighted! I've wasted almost two days trying to get new drivers, finally I have up-to-date, powerful drivers as opposed to the old crap I've been suffering with since... probably since ever, actually.

I've just run it through BF1942 and it works much better, I reckon Doom 3 might be playable now. One odd thing - the water is now much more greenish than it was. But, there's not much water in Desert Combat...

Thank you all very much, for your perseverence and patience!

:)

April 16, 2005

All respect goes out to Teraphy, tentoine and Darmdorf and Bill!

Spread the word :)

June 29, 2005

"72.01 with Pieter's mod INF version 30.71"

Mine works with those abovementioned + the line mentioned in the 1st post without a break added. A great many thanks you guys. You guys rock!!! :P :) :( :)

August 13, 2005

hi guys,

i'am also a very glad user of this threat :)

but to make your life a bit more difficult, i have

a tricky question for you: : :) :

this fix is only useable under win2k / xp, does anyone

have an idea, how to apply this trick for win98 or winMe

drivers?

there is the same problem with the display size.

many thanks in advance

der steini

June 7, 2006

Chris, you rock. I recently put in a Quadro 700 GoGL into my 'ol 8100 (remember those days :) ) and I had the same problem, where I could only see distorted screens and a res up till only 1400 by 1050. This fix did the trick. Everything runs fine now. Funny thing is that this screen is a UltraSharp Sharp LCD.

Thanks again all :P

hi guys,
i'am also a very glad user of this threat :)

but to make your life a bit more difficult, i have

a tricky question for you: : :( :

this fix is only useable under win2k / xp, does anyone

have an idea, how to apply this trick for win98 or winMe

drivers?

there is the same problem with the display size.

many thanks in advance

der steini

Have you tried adding the same lines in the INF for the 9x/ME INF?

August 9, 2006

Lol....How about no.

July 22, 2007

I have the problem samsung screen. Is there a simple install to fix out yet? I'm not a programmer and don't understand all of these edits and such.

Thank you all for your hard work,

Brih

July 24, 2007

Find the INF file (later used for installing via Have-Disk method described in http://forums.laptopvideo2go.com/index.php?showtopic=33 ) and open it with a text editor.

Read the first post in this thread and find the line where it says:

Add this line to an INF. It needs to be one long line placed before NV_Modes after [nv_SoftwareDeviceSettings]. Add the code to the INF, save and install driver.

October 13, 2007

Hello, forgive me for bringing up this old thread, but I think they were really onto something with this EDID override stuff. Is there a method for fixing broken EDIDs that applies to any monitor? Unfortunately LCD manufacturers haven't gotten any smarter and still screw up their EDIDs from time to time.

I have a Westinghouse LVM-37w3se 37" 1080p monitor/HDTV with VGA, DVI, HDMI, component, s-video, composite, etc, etc.

There is a known problem with the EDID on the "SE" revision of this monitor. Basically Westinghouse screwed up and gave it the same EDID from a 720p monitor (W4207), so it doesn't have an entry for 1080p, and the highest user selectable mode is 1080i (interlaced). I think the W4207 could accept a 1080i signal and downscale it to 720p, but could not accept a 1080p signal. So here I have a 1080p monitor that can accept 1080p signals, but tells any device that reads the EDID the maximum mode it can accept is 1080i.

There are two very large threads about this monitor at [H]ardForums and AVSForums that go into this issue but there is no real resolution to the broken EDID problem as of yet.

http://www.hardforum.com/showthread.php?t=1088497

http://www.avsforum.com/avs-vb/showthread.php?t=655280

I've got my Dell Inspiron XPS Gen 2 with NVIDIA 7800 GTX connected up to it via DVI and there is only ONE way to get 1080p working and it only works with the "classic" NVIDIA control panel, phased out by newer driver revisions. In the classic CP, you can force 1080p with the following steps:

1 - Open Classic Control Panel

2 - Click "Screen Resolutions & Refresh Rates"

3 - Check "Show standard HDTV formats" (accept license agreement)

4 - Click nView Display Settings

5 - Right click the "Westinghouse W4207" icon

6 - Check "Treat Digital Display as HDTV" (if not already checked)

7 - Repeat step 5, click "Select TV Format"->"1080p HDTV"

8 - On the window that opens ("HDTV overscan compensation") check "Native" and "Remember my preference for the selected format"

Click OK twice and voila, your 1080p monitor should finally be running in 1080p!

I've tried using Powerstrip custom resolutions to force 1080p to no avail, tried using NVIDIA's own Custom Resolutions, but it always reverts back to 1080i, stubbornly. Only method that works is the one I detailed above.

SO, with the background out of the way, on to the point:

How can I override the faulty EDID with the proper modes/timings so that 1080p is available by default (since the above method doesn't work with the new control panel).

Would I need to extract the faulty EDID from my monitor, and if so which program(s) can do that? I think I have tried one before, a DOS based one, and it failed.

Would I need to have someone with the correct EDID from a later revision send me their EDID so that I could use that data to override the faulty one?

What data exactly would need to be replaced in the override string?

Is there a simpler method such as the NV_R&T method (and how does that work?)

In my nv4_disp.inf I see a line such as:

HKR,, NV_R&T,[tab][/tab][tab][/tab][tab][/tab][tab][/tab]  %REG_SZ_APPEND%,"R&T0002=1920,1080,*,60,*,BNQ766A,OEM,13850,2080,48,32,1111,3,5,+-"

I believe this is a monitor-specific timing/mode for a BenQ FP231W 23" 1920x1200 monitor. Am I on the right track in that I could add a line similar to this with the timings for 1080p from my Westinghouse?

What is the format for this line? I understand a few of them, e.g.

HKR,, NV_R&T,[tab][/tab][tab][/tab][tab][/tab][tab][/tab]  %REG_SZ_APPEND%,"R&T000<n>=<active horz lines>,<active vert lines>,*,<refreshrate>,*,<deviceID>,OEM,<?>,<horz total lines>,<horz front porch?>,<horz back porch?>,<vert total lines>,<vert front porch?>,<vert back porch?>,<polarity>"

Probably got some of the "porches" mixed up, and what is that first number (13850)? I suspected pixel clock at first but it seems too small to be in KHz and too large to be in MHz. And for the deviceID, where can that exact string be located? My monitor is recognized as either a "Westinghouse W4207" or just "W4207" in the NVIDIA drivers.

I used PowerStrip to read the current timings in 1080p mode (after using the 'classic' control panel method), if this helps anyone formulate a NV_R&T string for my monitor:

PowerStrip timing parameters:
1920x1080=1920,88,44,148,1080,4,5,36,148500,768

Generic timing details for 1920x1080:
HFP=88 HSW=44 HBP=148 kHz=68 VFP=4 VSW=5 VBP=36 Hz=60

VESA detailed timing:
PClk=148.50 H.Active=1920 H.Blank=280 H.Offset=72 HSW=44 V.Active=1080 V.Blank=45 V.Offset=4 VSW=5

Linux modeline parameters:
"1920x1080" 148.500 1920 2008 2052 2200 1080 1084 1089 1125 +hsync +vsync

Sorry for the lengthy post, just trying to be thorough.

Thanks in advance for your insight.

October 15, 2007

I'll save you the trouble of reinventing the wheel and fill in the blanks. Restriction & Timing, used to remove modes that are available that shouldn't be or tweaking the timing of a given mode. This will not add a mode that is not available!

x resolution(s), y resolution(s), bpp, refresh rate, device id, monitor id, 1 or more timing standards, pixel clock (ex: 115MHz = 11500 *10kH),  horz total, horz front porch, horz pulse width, vert total, vert front porch, vert pulse width, h/v polarity

October 15, 2007

I'll save you the trouble of reinventing the wheel and fill in the blanks. Restriction & Timing, used to remove modes that are available that shouldn't be or tweaking the timing of a given mode. This will not add a mode that is not available!
x resolution(s), y resolution(s), bpp, refresh rate, device id, monitor id, 1 or more timing standards, pixel clock (ex: 115MHz = 11500 *10kH),  horz total, horz front porch, horz pulse width, vert total, vert front porch, vert pulse width, h/v polarity

Thanks I did figure most of that out (forgot to update this thread).

The line I ended up using goes like this:

HKR,, NV_R&T, %REG_MULTI_SZ%, "R&T0000=1920,1080,*,60,*,WDE4207,OEM,14850,2200,72,44,1125,4,5,++"

Problem is the entire frame is shifted to the left by about 5 pixels, and changing the horz front porch in the R&T line doesn't seem to affect that. Is this because the R&T line doesn't have an entry for rear porch (can it?)? Or perhaps its a timings standard thing (what other standards are enterable?).

I use PowerStrip to adjust both front and rear horizontal porch to fix this, but it doesn't stick upon a resolution change. Hoping when I get someone to send me the fixed EDID data I can just do a full EDID override.

Edited October 15, 2007 by blah238

October 25, 2007

Hello, I notice that your override EDID strings have 14 more bytes(?) than the 128 byte EDID I am generating with the Phoenix editor, seemingly appended to the beginning. What do these 14 extra bytes signify, and how are they generated?

October 25, 2007

OK, I figured out what the 14 bytes are for from reading Teraphy's user page.

Sadly, although the override EDID flags show up in the registry after installing the driver (163.75 Vista 32-bit), they seem to have no effect. I still can not get a resolution of 1360x768 on my Sharp Aquos LC-32GA5U, even with Powerstrip.

Does anyone know whether the EDID override is supposed to work on Windows Vista, or is good for XP only?

FWIW, here is my string:

HKR,, OverrideEdidFlags0, %REG_BINARY%, DE,10,92,02,00,00,FF,FF,04,00,00,00,00,80,00,FF,FF,FF,FF,FF,FF,00,4D,10,B1,0F,01

,01,01,01,00,0F,01,03,80,00,00,78,0A,1B,BE,A2,55,34,B3,26,14,4A,52,BF,EE,00,31,5

9

,45,59,61,59,81,99,81,80,81,C0,8B,C0,01,01,01,1D,00,80,51,D0,1A,20,28,88,13,00,0

0

,00,00,00,00,1C,F6,20,50,A0,51,00,1B,30,30,90,13,00,00,00,00,00,00,1C,00,00,00,F

D

,00,31,56,18,46,0B,00,0A,20,20,20,20,20,20,00,00,00,FC,00,53,48,41,52,50,20,4C,4

3

,44,0A,20,20,20,00,14

LCD SEC3255=1600x1200 shows only 1400x1050

Recommended Posts

Darmdorf

Link to comment

Share on other sites

Top Posters In This Topic

Popular Days

Top Posters In This Topic

Popular Days

mobilenvidia

Link to comment

Share on other sites

Teraphy

Link to comment

Share on other sites

Bob the Dino

Link to comment

Share on other sites

Darmdorf

Link to comment

Share on other sites

®®®

Link to comment

Share on other sites

Darmdorf

Link to comment

Share on other sites

Teraphy

Link to comment

Share on other sites

Guest Guest

Link to comment

Share on other sites

Bill

Link to comment

Share on other sites

®®®

Link to comment

Share on other sites

Bill

Link to comment

Share on other sites

Guest metalangel

Link to comment

Share on other sites

®®®

Link to comment

Share on other sites

Guest FLDQUY157

Link to comment

Share on other sites

Guest der_steini

Link to comment

Share on other sites

Kamika007z

Link to comment

Share on other sites

The_Lead_Factor

Link to comment

Share on other sites

Brih

Link to comment

Share on other sites

®®®

Link to comment

Share on other sites

Guest Blahman

Link to comment

Share on other sites

Teraphy

Link to comment

Share on other sites

blah238

Link to comment

Share on other sites

Guest lazyn00b

Link to comment

Share on other sites

Guest lazyn00b

Link to comment