Changing manufacturer ID in TripleHead2Go EDID

[dtimm]

Now that prices for Zalman monitors have slumped I bought 3 ZM-M190s and a TripleHead2Go Digital for better 3D immersion. Everything works reasonably well with the IZ3D driver. However I still like the Nvidia Stereo driver more.

The Nvidia driver however looks for a Zalman monitor to activate interlaced S3D. But because now the DTH2G is between the graphics card and the Zalmans it only sees a Matrox "monitor". So the driver allows only anaglyph.

Does anyone have experience with changing the EDID within a DTH2G? The supplied PowerDesk SE is only able to change the 4 custom resolution slots in the DTH2G EDID. I assume I have to change the manufacturer ID, model ID and/or monitor name but dont know of a safe way to do this.

[cybereality]

I don't have any experience with the TH2G, but I've got a Zalman and did some research into how the nvidia driver works. From what I understand it locks out functionality based on the EDID like you said so you are on the right track. How you would go about spoofing the EDID without breaking anything, that I don't know. But it should be possible in theory.

[UndeadD3vi1]

You can't modify the EDID Info directly, so you'll need to intercept the EDID signals and modify the bytes (Data Format below) to your needs. Can you code BASIC or C? If so time for you to grab a Arduino ($20+ - C) or PIC ($10 - BASIC) microcontroller.

Heres the Data Format (From Wiki)

Code: Select all

Byte sequence
00–07: Header information
08–17: Complete serial number
  08–09: Manufacturer ID
  10–11: Product ID Code (little-endian)
  12–15: Serial Number (little-endian)
  16: Week of Manufacture
  17: Year of Manufacture.  Add 1990 to the value for actual year.
18: EDID Version Number
19: EDID Revision Number
20-24: Basic Display Parameters
  20: VIDEO INPUT DEFINITION
    bit 7: 0=analog, 1=digital
    if bit 7 is digital:
      bit 0: 1=DFP 1.x compatible
    if bit 7 is analog:
      bit 6-5: video level
       00=0.7, 0.3, 01=0.714, 0.286, 10=1, .4 11=0.7, 0
      bit 4: blank-to-black setup
      bit 3: separate syncs
      bit 2: composite sync
      bit 1: sync on green
      bit 0: serration vsync
  21: Maximum Horizontal Image Size (in centimeters).
  22: Maximum Vertical Image Size (in centimetres).
  23: Display Gamma.  Divide by 100, then add 1 for actual value.
  24: Power Management and Supported Feature(s):
    bit 7: standby
    bit 6: suspend
    bit 5: active-off/low power
    bit 4-3: display type.
      00=monochrome, 01=RGB colour, 10=non RGB multicolour, 11=undefined
    bit 2: standard colour space
    bit 1: preferred timing mode
    bit 0: default GTF supported
25-34: CHROMA INFO
  25: low significant bits for Red X (bit 7-6), Red Y (bit 5-4), Green X (bit 3-2), Green Y (bit 1-0).
  26: low significant bits for Blue X (bit 7-6), Blue Y (bit 5-4), White X (bit 3-2), White Y (bit 1-0).
  27–34: high significant bits for Red X, Red Y, Green X, Green Y, Blue X, Blue Y, White X, White Y.
  To decode actual value, rearrange bits as follows:
  High significant bits 7-0 for (channel), low significant bits for (channel).
    Actual value is between 0.000 and 0.999, but encoded value is between 000h and 3FFh.
35: ESTABLISHED TIMING I
  bit 7-0: 720×400@70 Hz, 720×400@88 Hz, 640×480@60 Hz, 640×480@67 Hz,
           640×480@72 Hz, 640×480@75 Hz, 800×600@56 Hz, 800×600@60 Hz
36: ESTABLISHED TIMING II
  bit 7-0: 800×600@72 Hz, 800×600@75 Hz, 832×624@75 Hz, 1024×768@87 Hz (Interlaced),
           1024×768@60 Hz, 1024×768@70 Hz, 1024×768@75 Hz, 1280×1024@75 Hz
37: Manufacturer's Reserved Timing
  00h for none
  bit 7: 1152x870 @ 75 Hz (Mac II, Apple)
38–53: Standard Timing Identification.  2 bytes for each record.
  First byte
    Horizontal resolution.  Multiply by 8, then add 248 for actual value.
  Second byte
    bit 7-6: Aspect ratio.  Actual vertical resolution depends on horizontal resolution.
      00=16:10, 01=4:3, 10=5:4, 11=16:9
    bit 5-0: Vertical frequency.  Adds 60 to get actual value.

54–71: Descriptor Block 1
  54–55: Pixel Clock (in 10 kHz) or 0
  If Pixel Clock is non null:
    56: Horizontal Active (in pixels)
    57: Horizontal Blanking (in pixels)
    58: Horizontal Active high (4 upper bits)
        Horizontal Blanking high (4 lower bits)
    59: Vertical Active (in pixels)
    60: Vertical Blanking (in vertical pixels/lines)
    61: high significant bits for Vertical Active (4 upper bits)
        high significant bits for Vertical Blanking (4 lower bits)
    62: Horizontal Sync Offset (in pixels)
    63: Horizontal Sync Pulse Width (in pixels)
    64: Vertical Sync Offset (in lines) (4 upper bits)
        Vertical Sync Pulse Width (in lines) (4 lower bits)
    65: high significant bits for Horizontal Sync Offset (bit 7-6)
        high significant bits for Horizontal Sync Pulse Width (bit 5-4)
        high significant bits for Vertical Sync Offset (bit 3-2)
        high significant bits for Vertical Sync Pulse Width (bit 1-0)
    66: Horizontal Image Size (in mm)
    67: Vertical Image Size (in mm)
    68: high significant bits for Horizontal Image Size (4 upper bits)
        high significant bits for Vertical Image Size (4 lower bits)
    69: Horizontal Border
    70: Vertical Border
    71: Interlaced or not (bit 7)
        Stereo or not (bit 6-5) ("00" means not)
        Separate Sync or not (bit 4-3)
        Vertical Sync positive or not (bit 2)
        Horizontal Sync positive or not (bit 1)
        Stereo Mode (bit 0) (unused if 6-5 are 00)
  If Pixel Clock is null:
    56: 0
    57: Block type
      FFh=Monitor Serial Number, FEh=ASCII string, FDh=Monitor Range Limits, FCh=Monitor name, 
      FBh=Colour Point Data, FAh, Standard Timing Data, F9h=Currently undefined, F8h=defined by manufacturer
    58: Unknown
    59–71: Descriptor block contents.
      If block type is FFh, FEh, or FCh, the entire area is a text string.
      If block type is FDh:
        59–63:
          Min Vertical frequency, Max Vertical frequency, 
          Min Horizontal frequency (in kHz), Max Horizontal frequency (in kHz), pixel clock (in MHz (multiply by 10 for actual value))
        64–65: Secondary GTF toggle
          If encoded value is 000A, bytes 59-63 are used.  If encoded value is 0200, bytes 67–71 are used.
        66: Start horizontal frequency (in kHz).  Multiply by 2 for actual value.
        67: C. Divide by 2 for actual value.
        68-69: M (little endian).
        70: K
        71: J. Divide by 2 for actual value.
      If block type is FBh:
        59: W Index 0.  If set to 0, bytes 60-63 are not used.  If set to 1, 61–63 are assigned to white point index #1
        64: W Index 1.  If set to 0, bytes 65-68 are not used.  If set to 2, 65–68 are assigned to white point index #2
        White point index structure:
          First byte
            bit 3-2: low significant bits for White X (bit 3-2), White Y (bit 1-0)
          Second to third byte: high significant bits for White X, White Y.
          Fourth byte: Gamma.  Divide by 100, then add 1 for actual value.
          To decode White X and White Y, see bytes 25-34.
      If block type is FAh:
        59–70: Standard Timing Identification.  2 bytes for each record.
          For structure details, see bytes 38-53.

72–89: Descriptor Block 2
90–107: Descriptor Block 3
108–125: Descriptor Block 4
126: Extension EDID Block(s).  In EDID 1.1, it is ignored, and should be set to 0.  In EDID 1.3, this is the number of
      extension blocks which follow the first.
127: Checksum.

[dtimm]

I think that's too complicated for me. I could buy a little DVI adapter that passes through all signals except for the EDID info (which is customizable) for $79.

I was thinking of a software solution, e.g. modifying a downloaded DTH2Gs firmware and flashing it to the device. I've found parts of the EDID info in the firmware but would have liked a little more assurance that flashing the modified firmware wouldn't destroy the DTH2G.

[UndeadD3vi1]

Are you positive you can modify the Manufacture EDID via a flash? I can only verify that you can modify the Resolutions Info.
Otherwise flashing a device is perfectly safe in almost every case.

[dtimm]

Just had the heart to do the flashing of the modified firmware. Everything went well and now I have one very wide "Zalman monitor".

[UndeadD3vi1]

Congrats, good to hear it went well. I may buy a TripleHead2Go eventually, I only have 2 outputs on GPU and will never go SLi but will soon have 3 Monitors...

Is it true you can go upto 6 Monitors with it? I found a photo here of UT2004 on 6 Screens using TripleHead2Go (2x Units?)

[Martel]

Hello! And greetings from Germany.

I have the same Problem with my Setup.

My Setup: Triplehead 2 Go Digital Left Samsung 226 BW / Zalman Trimon / Samsung 226 BW

I want to use the Nvidea Zalman driver but the Edid doesent allow it.

Can someone can give me a hand ( step by step ) or via Ts3 and Teamviewer Remote. To fix this Issu?

Thanx alot.

English and German possible

Found a way via .INFO somebody try this or can help ?

http://msdn.microsoft.com/en-us/windows ... e/gg487330" onclick="window.open(this.href);return false;