20 Most Recent WYSE Winterm S30 Network Terminal - Page 2 Questions & Answers

Even flash module is bad (erased) or does not make good contact with the board in J15 connector.

you can dawnload it from the manufacture websit.Just send a mail to request for password with your products no.

tapping the "G" key upon bootup

restart client

I suggest upgrading the OS on these problem terminals to the latest on the wyse website. It might be an incompatibility with the monitor and terminal (might have been fixed in later builds), in which case you will need to log it with Wyse directly, as they will need to test this.

Chances are though you either have a faulty monitor cable, a faulty unit, or faulty monitor. Perhaps even a combination of more than one of these above problems. Try to rule out each bit of hardware before blaming anything in particular.

Try a few different monitor resolutions, colour depth and refresh rates too. Cant hurt :)

You can check the settings in the bios (password will be "Fireport") I dont think there is anything in there that would trigger this.

Is there a screen-saver option in the control panel for the device? If so, see if it is set. If not, then try using the Wyse website to update the terminals OS to the latest. This will hopefully solve the problem. It might just be an incompatability with the older OS version.

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.

Reprogram EEPROM

Double-clicking the System icon in the Control Panel opens the System Info dialog box.You can use this dialog box to allocate thin client memory and reset the thin client to factory defaults.The General tab contains a check box that allows you to reset the thin client to factory defaults (the check box is active for administrators only).You can reset the thin client to factory default settings by selecting the *Reset the terminal to factory-default property settings* check box (the System Settings Change message displays and you can confirm and follow the instructions provided to reset the thin client).

Try pushing in on the scrolling ball on the mouse.
I just had the same issue and that's what I did and it quit.
Hope this helps!

On the DNS-server (Active Directory) you have to generate spesific IP-address for each thin clients MAC-address.

hold down the g key on boot

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.
Download Link:
http://www.wyse.com/supportdownload/3series/Addon_ThinPrint_B0010.exe

I haven't tried this, so let me know if it works.

The display settings are not valid with the monitor. Either you are using a new monitor or you have changed the settings. If you are using a new monitor, swap with the old monitor and configure the appropriate refresh rate for the new monitor.

If you have changed the settings you may need to either reset all default settings, or setup a parallel unit and use the same key strokes to change the display settings on the problem unit.

Cheers..

In almost all cases of my dealing with Thin Clients over a 10/100bps network all problems usually are within the Terminal Servers hosting the Thin Clients. BPCS

It probably has to do with the version of CE client that is installed on the Thin Client. I have run into this problem before. The same Wyse clients can have different versions of CE installed. If the versions are the same then contact WYSE tech support to find what the error code relate to. BPCS