Question about WYSE Winterm Computers & Internet
Touchscren on wyse thin client is calibrating opposite of touch points.
Posted by Anonymous on
a 6ya expert can help you resolve that issue over the phone in a minute or two.
best thing about this new service is that you are never placed on hold and get to talk to real repairmen in the US.
the service is completely free and covers almost anything you can think of (from cars to computers, handyman, and even drones).
click here to download the app (for users in the US for now) and get all the help you need.
Posted on Jan 02, 2017
SOURCE: Wyse S30 thin Client with Ubuntu
I played with those a lot with the LTSP and finally made it work...
All in all, the problem is that the X.org cannot autoconfigure the graphic chip of this client. On ubuntu 7.10 you need to force it to use the amd driver and cannot do it from the LTSP.conf file.
In your LTSP.conf file, you have to point to a xorg.conf file specific for your s30 thin client (I called it s30xorg.conf). Then you need to build this xorg.conf file (lots of help on the net on how to do this) and place it in the right folder. (The folder is probably not the same than on my system but it should be pretty obvious or at least written in the manuals or help files where to pu it). In this xorg.conf file, you will need to specify the amd driver and some standard vesa resolutions and refresh rates (also widely availavble on the net). Then dont forget to rebuild your LTSP image with those new files in the tree.
If I remember correctly you will also need to disable the ubuntu splash screen from another config file somewhere... I am sure you will find which one.
Let me know if you can make it work... if what I said is total gebrish, go on reading everythin you can find on the net until you understand what is here.
Posted on Dec 04, 2008
SOURCE: black boxes
In the "experience" tab, uncheck the "bitmap caching" box and the problem will disappear. This is checked by default, but causes the black boxes in most situations unless you uncheck it.
Posted on Mar 03, 2009
This is caused by the terminals default display resolution (or the resolution that it was set to in its previous environment). The easiest way to get a display, would be to use a different monitor with a higher range of supported resolutions.
Fingers crossed the previous wnos.ini file would allow a G-key reset. If so, just hold down the G key when the terminal is booting, and it will reset to factory defaults. This might allow your monitor to work. (I think the default resolution is 800x600)
The problem you have is that the terminal might be locked down via the .ini file. So changing the configuration might be difficult. You could use a program like Wireshark to perform a network trace, this would tell you where the terminal is looking for it its wnos.ini file.
Then you will be able to setup a new wnos.ini on an FTP server set to the IP address(and path) the terminal is looking for, and this will allow you to set your own configuration.
Posted on Jul 07, 2009
Tips for a great answer:
May 17, 2012 | WYSE Winterm V90LE Thin Client - Thin...
Mar 20, 2011 | WYSE Winterm V30 Thin Client - Thin Client...
Dec 26, 2010 | Sony Reader Touch PRS-600
Jun 13, 2009 | Handmark Software MobileLists (950142) for...
Dec 24, 2008 | Dual Electronics CECT P168 Cellular Phone
Sep 14, 2005 | NEC MobilePro 900 Handheld
Jan 09, 2013 | WYSE Winterm V30 Thin Client - Thin Client...
94 people viewed this question
Usually answered in minutes!
Step 2: Please assign your manual to a product: