<div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br><br>I have a wide-screen HDTV with only component in. I'm using a<br>VGA-component converter. Not knowing my "native resolution" but knowing
<br>the set accepts 1080i, I used the Modeline Generator at<br><a href="http://xtiming.sourceforge.net/cgi-bin/xtiming.pl">http://xtiming.sourceforge.net/cgi-bin/xtiming.pl</a> and started with<br>1920x1080. This created a modeline with the horrible overscan you
<br>mention. After a little fiddling around, I found that 1760x990<br>resolution worked for me. Here is my modeline:<br><br># My 1920x1080i mode<br> Mode "1920x1080i"<br> DotClock 74.25<br>
HTimings 1760 1928 1984 2204<br> VTimings 990 1034 1040 1113<br> Flags "-HSync" "-VSync" "Interlace"<br> EndMode<br><br>There's also a tool with Xorg (I can't remember the name) that will
<br>allow you to adjust your screen for perfect fit and then give you the<br>exact modeline. Use that for fine tuning.<br><br>HTH,<br><br>Drew</blockquote><div><br>Thank you for the reply. I thought in the past when I tried changing the resolution with powerstrip to anything much off of 1080i, I TV lost signal despite following the directions to keep the frequencies where they needed to be. I am outputting directly to component out on my video card but I am not sure that would matter. I will try your settings. If that doesn't work, I'll see if I can get that resolution to work on my TV with the
xltiming.pl approach. Thanks for the advice!<br></div><br></div>