- This topic is empty.
February 9, 2010 at 3:44 pm #5669
I have an issue with my newly acquired Dell P2010H lcd screens. They have a native resolution of 1600×900 and report so in the DDC table. However, the V10L will offer a resolution of 1600×1200 if I tell it to display 1600×900 from the ddc table, (and also if I tell it to use the best resolution from the DDC table). This results in the monitor not being able to display the thin client’s output.
A custom resolution of 1600×900 cannot be set in the V10L’s display settings. I can set a custom resolution lower than 1600×900, but this results in pixes doubling, and honestly I would not like to be setting the screen resolution for every terminal in the building manually.
Does anyone know of a way to fix this problem?
RienFebruary 10, 2010 at 11:07 am #17665
the V10L does not support this resolution. If you really need this you would have to contact Wyse to get this implemented.
CGFebruary 10, 2010 at 4:22 pm #17673
Hmmm that’s not good, what would be the chances of that happening on a scale from never to probably? (I have like 10 terminals with 2 of these displays each :()February 10, 2010 at 5:07 pm #17675
Open up a case with Wyse. In the past that had worked for me quite well. Maybe rise the number of installed terminals from 10 to 250 or something when you talk to them 😉
CGMarch 5, 2010 at 9:29 pm #17862croach77Member
- Total Post: 8
If you have a maintenance contract, update the firmware to version 6.5.0_30 since they added support for 1600 x 900.
I had the same problem and almost had a heart attack because we just ordered 30 lcds that were natively 1600 x 900.
ChrisMarch 11, 2010 at 4:58 pm #17898
Hmm, not under maintenance contract yet. It wasn’t offered by the distributor where I got the units from…
Is there another way to get the recent firmware? (Or can support contracts with wyse be entered after the sale of a unit?)March 11, 2010 at 8:35 pm #17900
You can buy an upgrade. And then directly maintenance to avoid further complications with getting up-to-date firmware.
CGMarch 12, 2010 at 3:15 pm #17919
I got the 6.5.0__30 firmware from Wyse. Do you use V10L dual dvi units? Because it seems the 1600×900 resolution only works on the second head, not on the first. (The first head still selects to output 1600×1200, or a weird very small resolution, just like it did in older firmwares)?
RienMarch 15, 2010 at 5:52 pm #17929croach77Member
- Total Post: 8
Sorry, I do not use the dual monitor option. I’d like to help you out and test your problem, but I don’t have the Wyse dual head adapter. Did you use a generic adapter or the one purchased through Wyse?
ChrisMarch 15, 2010 at 6:10 pm #17930
The V10L units are for sale with a second DVI-port (see http://www.wyse.com/products/hardware/thinclients/V10LDualDVI/index.asp ). These are the units I have.
Firmware 6.5.0__31 shows the same behaviour. One port now neatly displays 1600×900, but the other shows 640×480 and is therefore not usable. Any further ideas?
Greetings from the Netherlands,
RienMarch 15, 2010 at 7:51 pm #17934
Have you contacted Wyse support on this issue?
CGMarch 15, 2010 at 9:30 pm #17938
Yes, their first response was to try firmware 6.5.0__31. I replied that it didn’t resolve the issue and they haven’t replied on that yet.
I’ll let you guys know when there’s progress.
RienDecember 12, 2013 at 8:51 am #24455ITPeteMember
- Total Post: 1
I might post this to the wrong thread, but I think it is related.
We’re using Wyse V10L clients and have recently bought some 20″ widescreen monitors (1600×900) to replace classic 15″ 1024×1280 ones. They do pick up the correct resolution and work OK until they enter standby/sleep state. Once they do, they won’t come back active. So then users have to force shut down the client, this is causing disconnected sessions, time loss…and all that trouble that comes with it.
Anyone had a problem like this before? Any solutions?
Is it possible at least to disable this feature of the clients?
PeterDecember 13, 2013 at 12:33 pm #24457
Typically the only reason for the unit to go to standby is the screensaver.
So adding Screensaver=0 should help here.
- You must be logged in to reply to this topic.