Firmware t rd8503 03 Download Android firmware APK for android Gingerbread 2.3.3 - 2.3.7 2010 year, android Ice Cream Sandwich 4.0.3 - 4.0.4 2011 year, android Jelly Bean 4.1.x 2012 year, android Jelly Bean 4.2.x 2012 year, android Jelly Bean 4.3 2013 year, android KitKat 4.4 2013 year, android Lollipop 5.0 2014 year, android Lollipop 5.1 2015 year, android Marshmallow 6.0 2015 year, android. T.RD8503.03 Universal LCD LED TV Controller Driver Board +7 Key button+1ch 6bit 40Pins LVDS Cable+Speaker+EU Power Adapter. To confirm that this part fits your vehicle, please enter your vehicle's details below. Step 2: Find and write in the corresponding firmware.

I have 3 Windows Vista computers that I am connecting up to Sony Bravia KDL40S2000 LCD tvs using a VGA connection. The computers are Dells with and intel Q965/Q963 Express Chipset.

I am trying to run the screens at there default resolution of 1366 x 768, but this is not an option. The only resolution close to this that works is 1280 x 768, however this leaves black bars on each side of the image. I have downloaded the latest driver but this didn't make a difference. I have tried finding a display driver for the monitor (it shows up as generic display) but have been unable to find an available one. I also attempted to use PowerStrip to set a custom resolution, but this did nothing (I've read somewhere that PowerStrip doesn't work with Intel).I found an article where they discussed editing the NonEDIDModeAddSwSettings in the driver inf file, however I did not understand what all of these diffenet settings mean. Is this the best way to make this work?Any help would be greatly appreciated. Found this for your monitor on the MythTV Website:Sony KDL-40S2000I am able to get the picture exactly as it is with XP under Ubuntu with these settings.

HorizSync 30-66VertRefresh 30-61Modeline '1360x768' 85.500 1360 1432 1544 1792 768 771 777 795That Modeline translates to DTD:66,21,50,B0,51,00,1B,30,48,70,36,00,00,00,00,00,00,1CUnfortunately, the Modeline I found didn't specify sync, so there are three alternates in case that one doesn't work:66,21,50,B0,51,00,1B,30,48,70,36,00,00,00,00,00,00,1E66,21,50,B0,51,00,1B,30,48,70,36,00,00,00,00,00,00,1A66,21,50,B0,51,00,1B,30,48,70,36,00,00,00,00,00,00,18Download the latest Intel drivers in.ZIP form and extract them to a directory. In that directory or a subdirectory, find (depending on your version)Vista 32: igdlh.infVista 64: igdlh64.infOpen it.

Hey Archibael I tried this hack to the latest Intel drivers (may-31) for WinXP MCE and it just made my screen not work at all. Reinstalled latest driver from VGA mode to restore.My problem is this. When I run MonInfo the LCD (Vizio 37') says the max resolution is 1920x540. But the tech support guys at Vizio said that the correct resolution is 1366x768 @ 60HzOf course neither of these resolutions show up in the Display settins for Intel Graphics.Not sure who to believe. I am unsure as to what the correct DTD line values are can you help?Thanks-Charles.

Xda-developers Nexus 7 Nexus 7 Android Development KERNEL 4.2.2 CM10.1m4xx3d0utkexec,ath9k,rtl8187,USBhost5/2/13 by m4xx3d0ut XDA Developers was founded by developers, for developers. It is now a valuable resource for people who want to make the most of their mobile devices, from customizing the look and feel to adding new functionality. M4xx3d0ut kernel nexus 7 update.

I trid the above changes in this thread as but they did not work. Here is my Monitor Info for the Mac Mini running Windows XP MCE, DVI output into HDMI input of Vizio 37' LCD.Any help would be great!!-CharlesMonitorWindows description. Plug and Play MonitorManufacturer description. VIZIO L37 HDManufacturer.

VIZPlug and Play ID. VIZ1300Serial number.

HLEABAG086975EDID data source. I2C bus (real-time)Manufacture date.

2006, ISO week 8EDID revision. 1.3Display type and signal. DigitalSync input support. N/aScreen size. 820 x 460 mm (39')Power management.

N/aColor characteristicsDisplay gamma. 2.20Red chromaticity.

Rx 0.640 - Ry 0.330Green chromaticity. Gx 0.290 - Gy 0.600Blue chromaticity. Bx 0.150 - By 0.060White point (default). Wx 0.280 - Wy 0.290Timing characteristicsVESA GTF support. Not supportedHorizontal scan range.

31-70kHzVertical scan range. 50-85HzVideo bandwidth. 110MHzExtension blocks.

1Timing recommendation #1. 1920x540 at 60HzModeline.

'1920x540' 74.250 1920 2008 2052 2200 540 542 547 562 +hsync +vsyncTiming recommendation #2. 1920x1080 at 30HzModeline. '1920x1080' 74.250 1920 2008 2052 2200 1080 1084 1094 1124 interlace +hsync +vsyncTiming recommendation #3. 1920x540 at 60HzModeline. '1920x540' 74.250 1920 2008 2052 2200 540 542 547 562 +hsync +vsyncTiming recommendation #4. 1920x1080 at 30HzModeline.

'1920x1080' 74.250 1920 2008 2052 2200 1080 1084 1094 1124 interlace +hsync +vsyncTiming recommendation #5. 640x480 at 60HzModeline. '640x480' 25.180 640 656 752 800 480 490 492 525 -hsync -vsyncTiming recommendation #6. 1280x720 at 60HzModeline.

'1280x720' 74.250 1280 1390 1430 1650 720 725 730 750 +hsync +vsyncTiming recommendation #7. 720x480 at 60HzModeline. '720x480' 27.000 720 736 798 858 480 489 495 525 -hsync -vsyncTiming recommendation #8. 720x576 at 50HzModeline. Ah, using the HDMI input.

It's usually problematic with today's technology to get native rez over HDMI. The dirty little truth of the matter is, the HDMI inputs on most HDTVs (there are a few exceptions) only accept the so-called 'CE resolutions' (CE = consumer electronics), aka 1920x1080, 1280x720, 720x480, etc. This is due to a limitation of the HDMI reciever chips the TV manufacturers are buying, and thus regardless of what native rez you have, you will only ever get joy from driving a CE resolution- even if native rez works just fine over VGA or DVI (different, more flexible circuitry). There are some limitations to Intel's drivers (god knows that's why the whole 'Programmable Resolutions.'

Thread exists in the first place), but in this case Nvidia or ATI drivers are going to give you the same result. In fact, if you hook up using the VGA port, you might get an entirely different EDID result, including 1366x768!Your best bet is in using the resolutions provided (either 1080i or 720p), with DTDs:01 1D 80 18 71 1C 16 20 58 2C 25 00 34 CC 31 00 00 9E; 1080i01 1D 00 72 51 D0 1E 20 6E 28 55 00 34 CC 31 00 00 1E; 720pbecause that's what the scaling chips in your monitor are built to accept and turn into 1366x768.It's possible your monitor is the exception, but my research implies that your monitor is problematic and may not even have a valid EDID over VGA. I recommend 720p. I am currently using 1920x1080 from the downloaded driver and that does work however is cut off a bit enough that I cannot see the WIndows bar at the bottom of the screen and I lose a bit all the way around.I tried the Intel 1280x720 but that doesn't work.Do I need a special DTD for the 720p or a proper fitting 1080i??

I don't understand Should I copy these 2 lines into my INF file and set Number of DTDs to 2?? I'm lost.Also Am I really getting a better quaility of picture with the HDMI then if I were to just use VGA?-Charles.

Well I decided to hookup with the VGA and See. You were right the proper resolution is detected with the VGA port youcan see from this report from MonitorInfo how it has completely different results:MonitorWindows description. Plug and Play MonitorManufacturer description. VIZIO L37 HDManufacturer. VIZPlug and Play ID. VIZ1300Serial number. HLEABAG086975EDID data source.

I2C bus (real-time)Manufacture date. 2006, ISO week 8EDID revision.

1.3Display type and signal. Analog 0.714,0.286 (1.0V p-p)Sync input support. Separate, Composite, Sync on greenScreen size. 820 x 460 mm (39')Power management.

Standby, Suspend, Active off/sleepColor characteristicsDisplay gamma. 2.20Red chromaticity. Rx 0.640 - Ry 0.330Green chromaticity. Gx 0.290 - Gy 0.600Blue chromaticity.

Bx 0.150 - By 0.060White point (default). Wx 0.280 - Wy 0.290Timing characteristicsVESA GTF support. Not supportedHorizontal scan range.

31-70kHzVertical scan range. 50-85HzVideo bandwidth. 110MHzExtension blocks.

N/aTiming recommendation #1. 1366x768 at 60HzModeline. I would use the two DTDs I provided (comma delimited, with,37,01 tagged onto the end) to replace the ones in the.INF file, and yes, you should change the Number of DTDs to as many as you've replaced in the.INF. Basically, follow the directions from Wiki, using the DTDs I just gave you.HDMI can give you a better picture if your VGA cable is noisy or lossy, which it will be to some (possibly insignificant) extent.

HDMI is most useful to merge sound and graphics into one cable and to allow you to display AACS-protected material, but it is not required for anything besides that.For the overscan you're seeing, I recommend messing with the parameter in the.INF file called something like 'HDMI Overscan Percentage'. Currently it's set to zero, but you might want to tweak it up and down to see if it helps.

Timing recommendation #1. 1366x768 at 60HzModeline. '1366x768' 85.500 1366 1494 1624 1798 768 770 776 795 +hsync -vsyncRaw EDID base00: 00 FF FF FF FF FF FF 00 59 3A 00 13 01: 08 10 01 03 3F 52 2E 78 EA E6 9D A3 54 4A 99 2620: 0F 47 4A 0F CA 00 01 01 01 01 01 01 01: 01 01 01 01 01 01 00 00 00 FD 00 32 55 1F 46 0B40: 01 00 BC 90 21 00 00 1A 66 21 56 B0 51 00 1B 3050: 80 82 26 00 34 CC 31 00 00 1A 00 00 00 FF 00 4860: 4C 45 41 42 41 47 30 38 36 39 37 35 00 00 00 FC70: 00 56 49 5A 49 4F 20 4C 33 37 20 48 44 0A 00 BCIs there no way to get this on the HDMI port? And why doesn't 1280x720 work in HDMI. This monitor is strange. The 1920x1080 works with just a little cropping on the HDMI but on the VGA it crops off almost half the screen in the same setting.-CharlesYou could try using the 1366x768 DTD you got from VGA66 21 56 B0 51 00 1B 3080 82 26 00 34 CC 31 0000 1Ain the.INF file; it may show up then for HDMI, but even if it does there's no guarantee the monitor will accept it.Like I said, the circuitry is completely different on the VGA inputs than it is on the HDMI, which is why they're behaving differently for you.

Anim-FXis a very compact Flash tool based on a wide range of Flash templates.The unique thing about Anim-FX Flash intro and banner builderis that the positioning of the text and the number of text lines is flexible.- Speed Flash Animation on top of the photo of the car.the free demo version and check these great animated Flash intros and Flashbanners templates yourself. Just get this inexpensivetool to do it for you. Intro flash free. U p to 5lines of animated text effectsUnlimited number of characters72great Flashintros forUS$27Easyto use and to make changesSoundeffectsUser-friendlyinterfaceAllupgrades are FREE o2 FREE updatesannually.Fora full list of features, see the page.Anim-FXFlash Intro and Flash banner builder costs just US$27, whichmakes it one of the cheapest Flash animations and Flash text effect creatorsaround!OtherFlash Intro and Banner buildersCheck out this cool created with Amara Flash Intro and Banner BuilderFlashIntro and Banner SamplesTheAbove Flash animations are made entirely with Anim-FX. Make sure that you also read carefully throughthe section before you try it.WHAT'SNEWDon'twaste your time and effort trying to create graphics / gif files for animatedDHTML or animated Javascript banners or intros, when you know you don'thave the skills, time, money or patience for it.

OK I tried the new 3 lines and yes the 1366x768 will now appear in the drop down menu for the Intel Display however is doesn't work. Too funny it looks as f you were correct about the HDMI since when pluggin into the VGA 1366x768 is detected on startup and configured perfectly.On the HDMI It will do 1920x1080 still but there is cropping all the way around.

I didn't see anything on Overscan but there was a variable called HDMIUnderScan so I changed that from 0 to 7.5 just to see what it did. And nothing happened.

Weird that the EDID is different for one port to the other. Not sure that the HDMI port really pays attention to the driver. Or at least the underscan variable. Does it matter that I am coming out the DVI to HDMI of the screen??-Charles.

If you're coming out the DVI port and using a DVI-to-HDMI cable I'm not sure the AddUnderscanPercentageHDMI will work, since the card thinks you're on DVI. Even if it does work, using a decimal value like 7.5 would be bad since it should be in hexadecimal. It's automatically defaulting to 7.5% underscan with the setting at 0; try tweaking it upward to see if you get results.Can you run MonInfo when hooked up to HDMI? Even if the underscan percentage variable doesn't work for you, you could create your own timings with PowerStrip or manually (I'd help) which would shrink the number of pixels being sent to something like 1900x1000, thus fitting onscreen better. Yes the Montior info in HDMI (DVI) is the first one I sent above here, it read the Screen and suggested the 1080i or 720p. Which is what we based the Modlines on I thought. That's why I thought that one of the 3 DTD would work.

2 were based on the MonInfo with HDMI and the 1366x768 was based on the MonInfo with the VGA.Powerstrip seems to load up showing custom resolutions available now (before the recent update it was greyed out) but It doesn't seem to write to the graphics chip properly just yet.How would I change my pixel count to fit the screen? Just reduce the number of pixels?

Would that really work?-Charles. Yep.First of all, understand that we would be doing what Powerstrip refers to as a 'resolution within a resolution': we'd be sending what the TV thinks is a 1920x1080 picture, but we would only be lighting up some smaller number.Take the DTD you're working on. The critical numbers are:01,1D,80,18,71,1C,16,20,58,2C,25,00,34,CC,31,00,00,9E80, 18, 71 - 780, 118 in hex = 1920, 280 in decimal. This is the horizontal resolution (number of active pixels) and the blanking interval (rest of the pixels- black).

You want their total to remain the same, so if you drop the number of active pixels from 1920 to 1900, you need to raise the blanking interval from 280 to 300. Convert back to hex:1900 - 76C, 300 - 12CPut the bytes in the proper order:6C,2C,71And you've nowshrunk thehorizontal resolution by 20.

It should work similar with the bluevalues in thevertical direction: again, make sureif youlower the active pixelsby one, you need to increase the blanking interval by the same amount. In the above DTD example, if you want to drop the number of vertical lines by 8, you'd subtract1C - 8 = 14and add16 + 8 = 1ESo the vertical numbers would be14,1E,20It's possible- even probable- that now your image is off-center. At that point, you start messing with the green values, but let's not go there yet.This would be easier with Powerstrip, but since you can't seem to get it working, try horizontal first, then add vertical in. Wait no you're right it does appear in the drop down menu after all but as a separte resolution. 1900x1064I thought is was a res inside the 1080 resolution so I was selecting the 1080 one.However when I select the 1900 one we just added it just blanks out the screen and doesn't work like the 1366 one did.Strange I wonder what exactly this HDMI input is for if it does not display 1080i or 720p correctly.

It seems to only accept the resolutions givin but none of them actually fit the screen.-Charles. Try changing the vertical resolution back to normal and see if it still blanks when you select it.

1900x1080, in other words. I might have gotten something wrong when I specified it, and that could make it send a resolution your monitor can't display.I'm not sure why it's not displaying 720p for you, since we're giving it the DTD it claims it wants in the EDID. For 1080i, it's probably just the scaling chip in the TV assuming it's being sent video with icky stuff around the edges (as in last century's TV)- that's not uncommon at all!- so it's overscanningby some internally set percentage before converting it to 1366x768. We're attempting to compensate for this by essentially underscanning the signal we send to it so that when it does the zoom/scaling it goes to the edge of your screen instead of beyond it. An even better idea.

Stretch your toolbar to make it twice as big as usual (enough so when you use the 1080i resolution you can still click stuff on it).Download Powerstrip from.Install and execute it.Switch to one of the 1080i modes in DVI/HDMI- preferably the one I provided from your EDID, but whatever you can get. Right click on the Powerstrip icon on your toolbar, choose Display Profiles Configure. Click theAdvanced Timing Options button, then click on the Copy Timings to clipboard button (next to Cancel). Paste these into Notepad or whatever text editor you like. Label them '1080i original'.Now, down by Add New Resolution there's an icon with a triangle and a ruler which is labelled Design a resolution in a resolution when you scroll over it. You'll get a black screen with a white outline which you should extend to the edges of your screen, where you want the visible edges to go.

When it looks like how you want it, click OK. You'll be back on the Custom Resolutions screen. On this screen, too, you'll have a Copy to clipboard icon. Paste it in the same file, labelled '1080i underscan'.Get out of Powerstrip and switch back to whatever is a comfortable resolution for you to watch, then post your results from the file here. We should be able to use the same 1080i timings that you know work, along with the information Powerstrip provided, to construct working custom timings for 1080i for you to paste into the.INF file. It's a roundabout way of doing things, but it should accomplish what you want: running your monitor without such a silly amount of overscan. Archibael,Great thanks for the offer of help.The information from Moninfoseems of little use, it's a Sony LCD TV 32' so perhaps it's not reporting the DTD information.

I thnk I'm using the correct software (Monitor Asset Manager). It's the only montor I have attached so there is no problem there.The machine is a media PC dual booting windows XP Home and Fedora.

Perhapsthere are some Linux utilities?MonitorHardware information. N/aWindows description.

Default MonitorDisplay adapterAdapter description. Mobile Intel 945 Express Chipset FamilyAdapter device ID. 0x27A28086Display settings. 1280x768, 32bppUser/computer informationRegistered user name.Registered organization.Network user name.Network computer name.Windows version.

Windows XPWindows build. 5.01.2600 Service Pack 2Installation date. Bigred07,So far I'm not finding a Modeline for your TV, but I'll keep looking.

I see you're running a laptop- is the laptop screen deactivated when you're running MonInfo? There should be a pulldown box at the top which allows you to select the monitor you want to look at.Another trick someone pointed out to me recently is to open the Intel Display Console (should be a bluesquarein your toolbar, unless you've shut it off, click on the Information button, and then look for 'Monitor' or 'Display' (I'm forgetting because I'm not on my G965 system at the moment). Though it doesn't list the EDID there, if you click 'Save Information' at the bottom of the box it will save a file which will contain the EDID. See if that works.

Thanks for your assistance, archibael.I have just recently bought the Sony Bravia V2500 model and when I try out the above DTD, the V2500 says that the input signal is 1280x768, not the 1360 I was hoping for.:-( (The laptop, however, switches to 1360 or similar when I activate the above screen resolution DTD entry)This is the EDID information I get from Monitor Asset Manager when running from my Fujitsu Siemens Si1520 (GMA 945) laptop. I'm new to this EDID fibbling business so I ask you to kindly assist me:-)Here we go (VGA connector used, not HDMI)EDIT: Now that I read what's in the report, this seems very very unlikely. Among other things, it lists the screen size as approx 13 inches. That's 19 inches too few.:) I can't figure out why Monitor Asset Manager gives this information?MonitorWindows description. QDS MonitorManufacturer. QDSPlug and Play ID. QDS0045Serial number.

N/aEDID data source. I2C bus (real-time)Manufacture date. 2005EDID revision. 1.3Display type and signal. DigitalSync input support.

N/aScreen size. 260 x 160 mm (13')Power management.

N/aColor characteristicsDisplay gamma. 2,20Red chromaticity. Rx 0,590 - Ry 0,343Green chromaticity. Gx 0,295 - Gy 0,558Blue chromaticity. Bx 0,162 - By 0,149White point (default). Wx 0,313 - Wy 0,328Timing characteristicsVESA GTF support.

Not supportedHorizontal scan range. N/aVertical scan range. N/aVideo bandwidth. N/aExtension blocks. N/aTiming recommendation #1. 1280x800 at 60HzModeline.

'1280x800' 68,900 1280 1301 1333 1408 800 804 808 816 -hsync -vsyncStandard timings supportedn/aRaw EDID base00: 00 FF FF FF FF FF FF 00 44 93 45 00 00: 00 0F 01 03 80 1A 10 78 0A 3B 90 97 57 4B 8E 2920: 26 50 54 00 00 00 01 01 01 01 01 01 01: 01 01 01 01 01 01 EA 1A 00 80 50 20 10: 44 00 05 A3 10 00 00 18 00 00 00 0F 00: 72 01 0A 02 32 1E A0 04 32 01 00 00 00 FE 00 5160: 55 41 4E 54 41 44 49 53 50 4C 41 59 00 00 00 FE70: 00 51 44 31 32 54 4C 30 32 31 0A 20 20 20 00 41Display adapterAdapter description. Auxiliary portAdapter device ID. 0x27A68086Display settings. Hey Guys I too have the problem with overscan and trying to get my HTPC to display in 1366x768.Here is my setup - A-bit iL90MV Intel 945GM on board graphics.HDMI out to HDMI in on my Samsung LE32R73BD.Again I am having the same problem as everyone else and cannot get rid of the cropping.Here is my moninfo on HDMI in and out:MonitorWindows description. Generic PnP MonitorManufacturer description. SamsungPlug and Play ID.

SAM0200Serial number. N/aEDID data source. Registry (stored)Manufacture date. 2005, ISO week 42EDID revision. 1.3Display type and signal.

DigitalSync input support. N/aScreen size.

160 x 90 mm (8')Power management. N/aColor characteristicsDisplay gamma. 2.40Red chromaticity.

Rx 0.632 - Ry 0.357Green chromaticity. Gx 0.289 - Gy 0.596Blue chromaticity. Bx 0.143 - By 0.085White point (default). Wx 0.280 - Wy 0.290Timing characteristicsVESA GTF support. Not supportedHorizontal scan range. 15-46kHzVertical scan range. 50-61HzVideo bandwidth.

80MHzExtension blocks. 1Timing recommendation #1. 1280x720 at 60HzModeline. '1280x720' 74.250 1280 1390 1430 1650 720 725 730 750 +hsync +vsyncTiming recommendation #2. 1280x720 at 50HzModeline. You're probably running into the classic HDMI monitor limitation.

Many HDMI inputs are limited to taking only 'CE' (aka 'consumer electronics' resolutions), even though their native resolution is different. CE resolutions are 720x480p, 1920x1080i/p, 1280x720p, etc. What you'd get out of a set top box, in other words. The TV then scales those inputs to native (1360x768).I believe you have the Bravia V-series, correct? According to this, it's not capable of 1:1 pixel mapping over HDMI:Sorry to be the bearer of bad tidings. You can send 1920x1080 and then I can help you in modifying the DTD so it doesn't overscan so much, but short of that your best bet is VGA if you want 1:1 pixel mapping.

Get the latest version of. It's abilities with Intel graphics are not comprehensive, but it will let you do a 'resolution within a resolution', which is what you want here.Basically, when your TV gets 1280x720, it expands ('scales') that imageto fit the actual 1366x768 physical pixels in your screen. When it does this, it scales it a little extra large so that any weird artifacts along the edge of a TV broadcast will be cut off (this is a holdover from analog TV days, and really has no place in a modern digital screen, but I digress).Select 1280x720 resolution and start up Powerstrip. In Powerstrip, go to Display Profiles Configure, choose Advanced Timing Options, then Custom Resolutions. In the lower right hand corner of the Custom Resolutions screen is a Design icon for 'Design a resolution-in-a-resolution'. Click this, extend the box to the limits of your screen, then click OK.Now click 'Copy to Clipboard' and paste the result here.

Ican help you convert the Modeline that you paste here to a DTD value you can use to get an uncropped image. Hi Everyone,This is my first post but I have been following this thread for about a week. I'm having similar problems as some of you. I recently bought a Shuttle SG33G5 which features the Intel G33 chipset and HDMI port. I'm connecting to my Rear Projection LCD HDTV which is a Panasonic PT-52LCX66 via HDMI. The problem I have is 'optical overscan' as described.

The TV's native resolution is. The driver and TV are in sync and I see the picture displayed, but the problem is the visible area is smaller than the native resolution.I have had success in the past on this TV with nVidia drivers which have a feature in ForceWare that will automatically adjust the visible area to fit the screen.

The reason I bought this system is because on, they advertise 'Intel TV Wizard' which claims to correct for overscan/underscan. I expected this to be similar to the nVidia solution only to find it doesn't do anything besides let me choose from 480p, 720p, 1080i. There is no option to adjust overscan and it's basically worthless.I have been emailing Intel Tech Support and this was their latest response:Hello,Thank you for contacting Intel Technical Support.At this point, we can only recommend that you contact the motherboard manufacturer for additional information and technical support.

This issue has not been replicated nor have other customers reported it.Please do not hesitate to contact us again if you need further assistance.Sincerely,Intel Technical SupportNeedless to say I am very disappointed. I would strongly suggest to everyone tocontact Intel Tech Support and make them aware this is a common issue. We need to hold them responsible for fixing features they advertise for their products that we paid good money for,in particularthis 'Intel TV Wizard'.archibael, I have been following your posts on several forums and have attempted your solution of manually adjusting the DTD so that the active pixels are reduced to 1192x672 (by also increasing the blank pixels so that the total count is constant).

So far, I have not had success with this over HDMI, but it does work for VGA. On HDMI the screen is blank, asone other poster observed.If anyone has any other ideas, please share them. In parallel, let's all make sure Intel hears about this.Thanks.