Question about Computers & Internet
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
The S30 terminal has the CE 5.0 operating system loaded as default. So you are limited by the operating system and not the hardware when it comes to network printing.
Here is a extract of the release notes for Windows CE 5.0:
"In Windows CE, TCP/IP supports network printing through the Server Message Block (SMB) protocol. It does not provide the Windows Line Printer Remote (LPR) Spooler. However, independent software vendors (ISVs) and original equipment manufacturers (OEMs) can add this support."
In short, you need a 3rd party software program or a (SMB) printer server setup to setup network printing on the S30 terminal..
Wyse also have add-on software to help, if you have CE 5.0 loaded then try the "Thinprint" add-on supplied as a free download by them.
I haven't tried this, so let me know if it works.
Posted on May 07, 2008
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
The Wyse S10s require a firmware update to connect to Windows Server 2008. This is due to lack of support for RDP 6.1.
The update I've found to work best is 18.104.22.168.
The only way to get this update is to contact Wyse. However, I have deployed it on numerous clients (our entire base is S10s) and had great success.
Posted on Oct 07, 2009
Tips for a great answer:
Jun 24, 2009 | WYSE 50 Terminal With Keyboard...
Mar 24, 2009 | WYSE Winterm S30 Thin Client - Thin Client...
Dec 11, 2008 | WYSE WT3235LE (902032-68) Network Terminal
Nov 12, 2008 | WYSE S10 (90210501) Network Terminal
Jun 04, 2008 | WYSE S10 (90210501) Network Terminal
May 02, 2008 | WYSE Winterm S30 Network Terminal
56 people viewed this question
Usually answered in minutes!
Step 2: Please assign your manual to a product: