Same problems here..
I used powerstrip with every 700tsv setting i can find.
Only difference is that my screen says it's 852x480 or 640x480 (depends on the version of the settings).
Hey,
I have a 7' screen as mentioned in the title with a Intel little valley board which supports 800x480. When I place the board at this resolution regardless of the color depth, the Xenarc always recognizes it as 800x600, causing obvious undesired results. All other supported resolutions function as they should.
Thanks to this forum I have successfully designed, implemented and troubleshooted every problem I have had so far, this problem finally problem however I have not been able to find an answer too.
Anyone else experience this problem? Thanks!
Same problems here..
I used powerstrip with every 700tsv setting i can find.
Only difference is that my screen says it's 852x480 or 640x480 (depends on the version of the settings).
I also had some issue with my 2008 tsv screen but it was mostly related with the touch screen drivers....I went with an older driver and that fixed the problem.
I don't have that resolution problem, but I realized that it could be a PIA to configure sometimes.
If you guys find a solution!! LET US KNOW
Thanks!, Do you happen to know the version of the driver you were successful with? Also I would never think the two (driver and resolution problem) could be related to each other, how did you stumble upon it?
what's the advantage of running at 800x480 vs 800x600. Most FEs and skins can handle either one fine without the image appearing stretched..
The only reason I wanted to try 800x480 was to see the true clarity of this monitor. And curiosity, otherwise I am happy with 800x600.
lol.. me too.. clearer, and probably a hair brighter.
Stav
I ran into this problem when I bought the "new version" of the 700IDT. Long story short, they changed the chipset so "native mode" is actually not supported. I told them they should change their specs since they claim that the displays will support 640x480 thru 1600x1200 but that is technically no longer true :-/
No driver or timing adjustments will fix this. This is a hardware issue...
figured.. tried everything..
Bookmarks