Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
1K views12 pages

WTware ThinClient

The document describes the configuration file for WTware terminals. It lists various parameters that can be set, including server and session settings, login credentials, keyboard layout, and graphic options. Terminal debugging and selecting peripheral devices are also discussed.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
1K views12 pages

WTware ThinClient

The document describes the configuration file for WTware terminals. It lists various parameters that can be set, including server and session settings, login credentials, keyboard layout, and graphic options. Terminal debugging and selecting peripheral devices are also discussed.
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 12

15/10/2014

WTware terminal configuration file. Terminal features, parameters and their descriptions - Windows Terminal Ware.

Search
What is WTware

Read

Download

Buy

Forum

WTware terminal configuration file. Terminal features, parameters and their descriptions.

List of parameters
Terminal debugging
syslog
Selecting server and session parameters
win2kIP, win2kIP2...win2kIP7
Session parameters
user, password, domain
shell, directory
keyboard
numlock
graphic
Using terminal periphery
floppy, cdrom, usb1..usb10, proc
printer
sound, sound_level, sound_control
com1, com2, com3, com4
smartcard
Others
clienthostname
include
turnoffmenu
autoshutdown
managed
infobox
redraw_delay
rdpcompression
connect_timeout
Terminal console parameters
usbkeyboard
mouse, mouse_wheel, mouse_accel_mult
video
resolution
bpp
refresh
noddc

Terminal debugging
There's no programs without errors. If you think, that WTware terminal works incorrectly or you've found an error create report for WTware techsupport. With your help we can make WTware better. In order to create report:
1. Start WTware event viewer on any Windows-computer. Run "Start - Programs - WTware - Event viewer" (file
wtcenter.exe from WTware zip-distribution utils directory).
2. Set syslog parameter value in terminal cofiguration file (or in wizard.wtc file, if the error occured in "Terminal
configuration wizard"). Parameter value should be IP-address of the computer where wtcenter.exe is working:
syslog = 10.100.50.2
3. Reboot terminal and try to reproduce the error. Terminal sends event log to wtcenter.exe and wtcenter.exe shows
it on the screen. When you reproduce the error, press "Save to file".
4. Send this event log file and description of the error to WTware techsupport.
Using of syslog parameter slows down terminal work. So we don't recommend to use it without need.

Selecting server and session parameters


win2kIP parameters group specifies terminal server address. These parameters also allow to select session settings. Possible
values:
1. Connection to specified terminal server. Specify terminal server IP-address (or DNS-name if dhcp-server returns dnsserver address):
win2kIP = 10.100.50.2
2. [Only in WTware PRO] Search for the first available server. Terminal sequentially pings all the servers listed and
connects to the first respondent. Server list is specified by these parameters:
win2kIP = 10.100.50.2
win2kIP2 = 10.100.50.3
win2kIP3 = 10.100.50.4
win2kIP4 = 10.100.50.5
win2kIP5 = 10.100.50.6
win2kIP6 = 10.100.50.7
win2kIP7 = 10.100.50.8

http://www.wtware.com/docs44/config.html

1/12

15/10/2014

WTware terminal configuration file. Terminal features, parameters and their descriptions - Windows Terminal Ware.
3. Connection to WTware cluster of terminal servers. For more details about cluster see this article:
1. Autosearch of all the servers from common cluster:
win2kIP = name:common
2. Connect to acc cluster by scanning all the servers listed in file acc.iplist (acc.iplist text file should be in the
same directory as all configuration files on tftp-server. This file should contain list of ip-addresses, one by line):
win2kIP = name:acc, list:acc.iplist
4. [Only in WTware PRO] Selection from menu. Address can be both definite server (ip-address or DNS-name) and cluster.
Its syntax is similar to 1, 2, 3 items. After address can be keyword opt: and configuration file name. This configuration
file settings are used when user selects corresponding menu item. So different terminal settings can be specified for
different servers. For more details about configuration file inclusion see include option. Unlike include parameter,
settings from files, included by opt: keyword, underlie settings in main configuration file. After comma should be
comment, that user sees in menu. It's obligatory to specify comments.
win2kIP = name:acc, list:acc.iplist, opt:acc.cfg, Accounts department
win2kIP2 = name:finance, Finance department
win2kIP3 = 10.100.50.4, opt:inet.cfg, Internet server
win2kIP4 = 10.100.50.7, Workplace

Session parameters
By default user should specify login, password and domain (if terminal server is included into domain) in "Windows login"
window when terminal starts. Set these values in configuration file to simplify user life. Possible values:
1. Definite values. Specified parameters are set automatically in login window. You can specify any of these
parameters - user, password and domain:
user = vasyapupkin
domain = MYDOMAIN
password = coolpassword
2. Selection from menu. User can select login parameters from menu. Possible values for login parameters:
DOMAIN\user[display_name]:password
DOMAIN\user:password
user[display_name]:password
user:password
DOMAIN\user[display_name]
DOMAIN\user
user
display_name is the name to display in menu. When display_name is not specified user name is displayed in menu.
These blocks are separated by semicolons. For example, this line creates menu with 5 items (users vasja and peter
from DOMAIN2, basil's password is 'joke', john's password is '1'):
user = DOMAIN2\basil[Basil Washington]:joke;DOMAIN2\peter;john:1;july;Guest;--new-Keyword --new-- tells terminal to leave username empty. You can create as many items as can be placed on the
screen. Terminal automatically shows them in columns.
If server doesn't accept password - check off checkbox "Always prompt for password" in Control Panel - Administrative
Tools - Terminal Services Configuration - RDP-Tcp - Logon Settings.
[Only in WTware PRO] Usually terminal server starts explorer when user connects. So user sees usual Windows desktop.
If you need any other program to start instead of desktop, use shell parameter. Thus Citrix Metaframe Seamless
Windows mode can be easily emulated. Of course shell parameter won't prevent advanced user from running any other
program from "Windows Task manager". Use Windows group policy or special software for such restrictions. Examples of
shell usage:
shell = c:\windows\system32\cmd.exe
starts command prompt console;
shell = C:\Program Files\Microsoft Office\Office10\winword.exe "c:\temp\document 1.doc"
runs Microsoft Word and opens document (it should be one line in configuration file).
[Only in WTware PRO] When using shell parameter you may need to set current working directory. Then use directory
parameter. For example, if shell parameter starts command prompt console, then this line opens command prompt and
sets current directory to c:\windows\temp instead of user home directory:
directory = c:\windows\temp

keyboard parameter determines default keyboard layout in "Windows login" window. Default value is english layout, also
you can set german:
keyboard = de
Or any other from the list below: af (Afrikaans), sq (Albanian), ar (Arabic), ar-sa (Arabic (Saudi Arabia)), ar-iq (Arabic
(Iraq)), ar-eg (Arabic (Egypt)), ar-ly (Arabic (Libya)), ar-dz (Arabic (Algeria)), ar-ma (Arabic (Morocco)), ar-tn (Arabic
(Tunisia)), ar-om (Arabic (Oman)), ar-ye (Arabic (Yemen)), ar-sy (Arabic (Syria)), ar-jo (Arabic (Jordan)), ar-lb (Arabic
(Lebanon)), ar-kw (Arabic (Kuwait)), ar-ae (Arabic (U.A.E.)), ar-bh (Arabic (Bahrain)), ar-qa (Arabic (Qatar)), eu
(Basque), bg (Bulgarian), be (Belarusian), ca (Catalan), zh (Chinese), zh-tw (Chinese (Taiwan)), zh-cn (Chinese (China)),
zh-hk (Chinese (Hong Kong SAR)), zh-sg (Chinese (Singapore)), hr (Croatian), cs (Czech), da (Danish), nl (Dutch

http://www.wtware.com/docs44/config.html

2/12

15/10/2014

WTware terminal configuration file. Terminal features, parameters and their descriptions - Windows Terminal Ware.
(Netherlands)), nl-be (Dutch (Belgium)), en (English), en-us (English (United States)), en-gb (English (United Kingdom)),
en-au (English (Australia)), en-ca (English (Canada)), en-nz (English (New Zealand)), en-ie (English (Ireland)), en-za
(English (South Africa)), en-jm (English (Jamaica)), en-bz (English (Belize)), en-tt (English (Trinidad)), et (Estonian), fo
(Faeroese), fa (Farsi), fi (Finnish), fr (French (France)), fr-be (French (Belgium)), fr-ca (French (Canada)), fr-ch
(French (Switzerland)), fr-lu (French (Luxembourg)), gd (Gaelic), de (German (Germany)), de-ch (German
(Switzerland)), de-at (German (Austria)), de-lu (German (Luxembourg)), de-li (German (Liechtenstein)), el (Greek), he
(Hebrew), hi (Hindi), hu (Hungarian), is (Icelandic), in (Indonesian), it Italian ((Italy)), it-ch (Italian (Switzerland)),
ja (Japanese), ko (Korean), lv (Latvian), lt (Lithuanian), mk (FYRO Macedonian), ms (Malay (Malaysia)), mt (Maltese), no
(Norwegian (Bokmal)), no (Norwegian (Nynorsk)), pl (Polish), pt-br (Portuguese (Brazil)), pt (Portuguese (Portugal)), rm
(Rhaeto-Romanic), ro (Romanian), ro-mo (Romanian (Moldova)), ru (Russian), ru-mo (Russian (Moldova)), sr (Serbian
(Cyrillic)), sr (Serbian (Latin)), sk (Slovak), sl (Slovenian), sb (Sorbian), es (Spanish (Traditional Sort)), es-mx (Spanish
(Mexico)), es (Spanish (International Sort)), es-gt (Spanish (Guatemala)), es-cr (Spanish (Costa Rica)), es-pa (Spanish
(Panama)), es-do (Spanish (Dominican Republic)), es-ve (Spanish (Venezuela)), es-co (Spanish (Colombia)), es-pe
(Spanish (Peru)), es-ar (Spanish (Argentina)), es-ec (Spanish (Ecuador)), es-cl (Spanish (Chile)), es-uy (Spanish
(Uruguay)), es-py (Spanish (Paraguay)), es-bo (Spanish (Bolivia)), es-sv (Spanish (El Salvador)), es-hn (Spanish
(Honduras)), es-ni (Spanish (Nicaragua)), es-pr (Spanish (Puerto Rico)), sx (Sutu), sv (Swedish), sv-fi (Swedish
(Finland)), th (Thai), ts (Tsonga), tn (Tswana), tr (Turkish), uk (Ukrainian), ur (Urdu), vi (Vietnamese), xh (Xhosa), ji
(Yiddish), zu (Zulu)
Also you can specify US International keyboard layout. It processes grave in a different way:
keyboard = en-us-int
keyboard = pt-br-int

By default NumLock indicator is on when terminal connects to terminal server. To turn off NumLock set in configuration
file:
numlock = off

[Only in WTware PRO] By default additional graphic options turned off to increase operating speed and lower network
load. To turn them on use graphic parameter. Parameter value is a line containing some of these symbols:
a
b
c
d
f

desktop wallpaper
show window contents while moving
visual effects for menus and windows
themes
font smoothing (ClearType)

Set parameter value as a sequence of symbols corresponding to the options you want to turn on. For example, to add all
options:
graphic = abcd
To show desktop wallpaper:
graphic = a
Windows 2003 Server shows desktop wallpaper only if you set to "Disabled": Start > Run > gpedit.msc >
Computer configuration > Administrative templates > Windows components > Terminal services > Enforce
removal of remote desktop wallpaper.

Using terminal periphery


[Only in WTware PRO] You can access terminal floppy-disk, USB-disks and CDROM. To enable device redirection set
corresponding parameter to on or samba. This value determines disk redirection way.
Value on means, that RDP protocol is used for redirection. We recommend to use this value. Windows 2000 Server
doesn't support this way of redirection. Use samba value. In current terminal session disk is available at:
\\tsclient\{floppy|cdrom|usbN}. Sometimes (not always, reasons not established) disk automatically appears in
"My computer".
If you've set proper parameter in configuration file, but can't see any disk icon - please, make sure that terminal
server settings allow client disk redirection. Try to access Windows-computer disks using standart Microsoft
terminal services client (Start > Programs > Accessories > Communications > Remote desktop connection).
While using terminal disks user should connect and disconnect disks manually. After inserting disk, floppy or USBdisk user should place mouse to bottom right screen corner. Then window with buttons appears. Press "connect"
button to make terminal read disk contents. It's necessary to press "disconnect" BEFORE disk ejecting, otherwise
disk data can be damaged. This is the only safe way of working with terminal disks.
Value samba makes terminal run "Microsoft networks" support service. It means, that any user is able to access
disk from any computer in network. Disk is available at: \\terminal_IP_address\{floppy|cdrom|usbN}.
By default all disk redirections are disabled. Don't allow users to access terminal disks without extreme necessity. Firstly,
it threatens your computer infrastructure security. Having the opportunity to read\write information to disks, user can
bring virus or steal important information. Secondly, redirection uses terminal resources, most of all memory, that could
be used for cache.
To access terminal floppy-disk set:
floppy = on

http://www.wtware.com/docs44/config.html

3/12

15/10/2014

WTware terminal configuration file. Terminal features, parameters and their descriptions - Windows Terminal Ware.
or
floppy = samba
To access terminal CDROM set:
cdrom = on
or
cdrom = samba
If you use no more than one flash-card at once, set only usb1 = on or usb1 = samba. All other parameters are needed for
card-readers, that work with various cards, or to work with several cards at once:
usb1 = on or usb1 =
usb2 = on or usb2 =
usb3 = on or usb3 =
usb4 = on or usb4 =
usb5 = on or usb5 =
usb6 = on or usb6 =
usb7 = on or usb7 =
usb8 = on or usb8 =
usb9 = on or usb9 =
usb10 = on or usb10

samba
samba
samba
samba
samba
samba
samba
samba
samba
= samba

When samba is used terminals are included into WTWARE workgroup. If needed you can place them into your group, then
terminals will appear in "My network places". Terminals can be placed into workgroup, but can't into domain! Workgroup
name is specified in workgroup parameter:
workgroup = mygroup
For computer stock-taking we created Linux-specific file system /proc. Computer hardware information is stored into
different files of this system. The only parameter value is:
proc = on

If printer parameter is specified correctly, printer can be attached to terminal, and all computers in the network,
including terminal server, can use it.
Possible parameter values:
printer = on
one-way data communication with printer (only from server to printer), lpt parallel port driver configured to work
with 378 port, irq 7.
printer = lpt
one-way data communication with printer, lpt parameters autodetection.
printer = usb
one-way data communication with printer, USB printer.
printer = com1
one-way data communication with connected to com1 port printer, 9600 bps speed, 8 bit capacity, no parity check, one
stop-bit (9600-8-N-1, common com-port hardware configuration). Expanded parameter syntax:
printer = com1(38400)
specifies 38400 bps speed.
Terminal with attached printer should have fixed IP-address. For more details about how to make Microsoft DHCP to give
fixed terminals addresses see this article. About printer drivers installation on the server read at this article./p>
How to print from DOS on terminal read here
WTware terminal emulates HP JetDirect hardware print-server (hardware print-server is a small box, that connects
computer network and printer). With WTware terminal:

work all printers able to work with hardware print-server HP JetDirect (as well as with any other print-server, all
hardware print-servers are HP JetDirect copies),
work all printers which drivers are included into Window distributive,
work all printers able to print from DOS without additional drivers,
don't work so called Win-printers. Some of win-printers: HP 700c, 820c, 1000c, 3300c, 3400c, DJ 820cxi, LJ 3100;
Canon LBP-250/810/1110/1120/1210/2410; Epson LP1300,EPL 5800/2050+/6200L, C900; Lexmark X5150;Dell
A920/940/960, J740; Minolta 1350W/1250W/2300W.

Up to 4 printers can work on the terminal. printer2 uses port 9101, printer3 uses port 9102 and printer4 uses port
9103. If you connect more than one printers of the same type (lpt and lpt, or usb and usb), then check experimentally
physical naming order by printing test pages. To print test page in WTware press Del during terminal loading, when
"Press Del to enter SETUP" is shown. Press "Terminal configuration" menu item.
printer = lpt
printer2 = lpt
printer3 = usb

http://www.wtware.com/docs44/config.html

4/12

15/10/2014

WTware terminal configuration file. Terminal features, parameters and their descriptions - Windows Terminal Ware.
printer4 = com1(38400)
If server_only is specified after printer type, terminal ignores all other parameters and simply works as print-server,
without graphic interface and connection to terminal server. For example, printer = lpt,server_only.
[Only in WTware PRO] Windows 2003 Server or Windows XP can redirect sound from server to terminal sound card. Keep
in mind, that playing Winamp takes up to 500KBps, i.e. up to half of 10Mbit network bandwidth. Unfortunately, 1-3
seconds delays while playing sound are unavoidable.
Windows 2000 Server doesn't support sound redirection.
In order to redirect sound to terminal set:
sound = on
Next line leaves sound on server, i.e. makes server sound card to reproduce sound:
sound = remote
By default sound redirection is turned off. If you set proper parameter in configuration file, but an error occures while
playing sound or sound is not reproduced - please, make sure, that terminal server settings allow client sound
redirection. Try to redirect sound to Windows-computer using standart Microsoft terminal services client (Start >
Programs > Accessories > Communications > Remote desktop connection).
Windows 2003 Server redirects sound only if you set to "Enabled": Start > Run > gpedit.msc > Computer configuration >
Administrative templates > Windows components > Terminal services > Client/Server data redirection > Allow audio
redirection.
Terminal sound level:
sound_level = 50
Possible values - from 0 (sound turned off) to 100 (maximum level).
Drivers for some sound cards can't manage hardware sound level. In such cases you can use software sound level
control:
sound_control = sw
Some drivers for some sound cards set sound speed incorrectly. For example old AMD Geode GX1 (Cyrix Kahlua). As a
result sound is much faster then it should be. To correct it we added parameter sound_rate. Specify one of the next
values in configuration file:
sound_rate = 32000
sound_rate = 44100
sound_rate = 48000

[Only in WTware PRO] Serial port redirection is far from perfection in Windows 2003 Server. For example, available
redirection doesn't allow to connect to Internet via COM-port modem on terminal. But for some tasks it will do.
Windows 2000 Server doesn't support serial port redirection.
Better test your device on Windows-computer using standart Microsoft terminal services client before attaching it to
WTware terminal COM-port.
In order to redirect serial port COM1 to terminal set:
com1 = on
To redirect COM2:
com2 = on
To redirect COM3:
com3 = on
To redirect COM4:
com4 = on
Not to cause confusion with physical server ports we recommend to rename physical ports. It's not obligatory, but
otherwise there will be two COM1 ports in terminal session. If applications have to deal with these two variants, it can
cause errors. To configure ports: rightclick on "My Computer" > Manage > Device manager > Ports (COM & LPT) >
Communications port (COM1) > Properties > Port settings > Advanced > COM-port number. For example, set COM11.
Similarly rename COM2 to COM12. Reboot server.
To make sure, that everything is right: connect to terminal server, start command line prompt and execute change port
command. Correct result is (redirected COM1 port):
COM1 = \Device\RdpDrPort\;COM1:1\tsclient\COM1
COM11 = \Device\Serial0
COM12 = \Device\Serial1
It means, that there's three serial ports available in session. COM11 and COM12 ports are physical server ports. COM1 is
physical terminal COM1 port. In this session any application, that works with COM1 device, in fact works with terminal
COM1 port.
USB bar code scanners, check printers and other devices with com and usb interfaces also should be connected using
com parameter. Then on the terminal server such device is available as COM-port device. Such devices have USB-COM
converter, and terminal makes reconversion. Like Windows-driver terminal creates virtual com-port. To redirect such
device with USB interface specify:

http://www.wtware.com/docs44/config.html

5/12

15/10/2014

WTware terminal configuration file. Terminal features, parameters and their descriptions - Windows Terminal Ware.
com1 = usb-serial
Partly incompatible ports we saw on SiS 651 motherboards and PCI-controller cards. Incompatibility is that connection
to port fails in Windows session, and in log appear messages "Broken port? Try comX=on,broken.". For simple devices
like bar-code scanners such port functionality is enough. Specify in configuration file:
com1 = on, broken
For those who understand. broken means DTR_OFF, RTS_OFF. These flags specify constant values for the lines.
Corresponding Windows commands are ignored when these flags specified. Syntax:
com1 = on, DTR_OFF, RTS_ON
com1 = on, DTR_ON
com1 = on, RTS_OFF

[Only in WTware PRO] Smart-cards redirection is supported only in Windows 2003 Server.
It's impossible to redirect smart-cards in Windows 2000 Server.
In current version only eToken PRO 32K cards supported. To redirect smartcards to terminal specify:
smartcard = on

Others
Terminal name, that is shown in "Terminal Services Manager" and is used for licensing access to Microsoft terminal
services, is determined by clienthostname parameter:
clienthostname = terminal1
Better to use different names for different terminals. Also terminal name can be received from DHCP-server (in this case
it can be used as a name for configuration file, for more details see this article). But clienthostname parameter value
underlies received from DHCP-server name. clienthostname default value is wtwXXXXXXXXXXXX, where XXXXXXXXXXXX terminal MAC-address.
include option helps to move all duplicated parameters into one (two, three...) common files:
include common.wtc
Terminal requests TFTP-server for specified file (that should be in configs directory, containing all configuration files)
and includes all parameters in this file. Included file format should be similar to main configuration file format. Any
parameter can be moved to included files. The amount of includes in main configuration file is optional. Include can't be
used in included files. Main configuration file parameters always underlie parameters in included files.
After disconnecting from terminal server terminal automatically connects to server again. Sometimes users don't
understand: when are they to shut down computer if there's always Windows on the screen? When you set parameter
value to:
turnoffmenu = on
then if parameters win2kIP and user create start menu, terminal adds new menu item "Turn off computer". Otherwise
after disconnect on the screen appears screen saver with the text "Turn off computer or press Enter to continue."
If parameter value is always:
turnoffmenu = always
then after disconnect terminal shows screen saver with the text "Turn off computer or press Enter to continue." AND adds
item "Turn off computer" to server and user selection menus, if they are created by win2kIP and user parameters. Press
Esc, Sleep, Power when you see screen saver "Turn off computer..." to turn off terminal.
To make terminal turn off automatically after log off specify:
turnoffmenu = poweroff
This parameters is used to make terminal shut down when it is not connected to server during specified time. Then menu
for server or user choise or screen saver or information window can appear on the terminal screen. Timeout is specified
in minutes:
autoshutdown = 5
You can turn off or restart terminals remotely. It can be useful, for example, when you changed configuration files and
need to apply these changes immediately. Such line in configuration file allows to manage terminal from any other
computer:
managed = on
And this line allows to manage terminal only from computer with address 192.168.10.15:
managed = 192.168.10.15
Terminals are managed by command line tool rsh.exe included into Windows Server distribution. To restart terminal
192.168.10.50 immediately run:
rsh.exe 192.168.10.50 reboot

http://www.wtware.com/docs44/config.html

6/12

15/10/2014

WTware terminal configuration file. Terminal features, parameters and their descriptions - Windows Terminal Ware.
If you changed configuration file and want terminal to re-read it, terminal should be restarted. You can tell terminal to
restart as soon as possible, i.e. when user will exit current session:
rsh.exe 192.168.10.50 update
To turn off terminal run:
rsh.exe 192.168.10.50 shutdown
When moving mouse to right-bottom screen corner - WTware window appears. It contains technical information: WTware
version, terminal server IP, terminal MAC-address. Also when floppy, cdrom, usbN parameters are specified in
configuration file connect\disconnect buttons for disks are placed in this window. When this window makes you nervous,
terminal can show it only if you press one of the control buttons and move mouse to right-bottom corner. Specify one
these lines:
infobox = lctrl
infobox = rctrl
infobox = lalt
infobox = ralt
infobox = lshift
infobox = rshift
lctrl means "left Ctrl button", rshift means "right shift button".
redraw_delay parameter determines maximal screen refresh interval. It is specified in milliseconds. Possible values from 50 to 3000, default value is 300.
redraw_delay = 50
When server sends data to screen too fast and terminal can't cope with such data amount - terminal stops screen
refreshing and draws image only to frame buffer, in RAM. To see this effect run some console application, for example,
execute command 'type longtextfile' from command prompt. For there's no output to slow video memory terminal can
calculate each frame faster and thus cope with redraw amount faster. But people don't like when image freezes and
screen stops refreshing. Small parameter values make image more alive. High values cause refresh delays but help to
increase the speed of large data amounts redraw.
rdpcompression parameter enables RDP packets compression:
rdpcompression = on
Use this option only for lower-bit-rate channels. Compression decreases terminal performance in local networks. Disabled
by default.
connect_timeout parameter.
connect_timeout = 15
This line means that terminal will try to connect to server for 15 seconds. Only after that it reports that server is
unavailable. May be usefull for slow and unreliable channels.

Terminal console parameters


Terminal configuration wizard helps to determine and check parameters from this group. It's easier to use wizard than
to select values manually.
If USB-keyboard is used and terminal RAM is less 64Mb set:
usbkeyboard = on
On the terminals with no less than 64Mb RAM USB-keybard is autodetected.
If mouse port is not PS/2, set mouse parameter. Possible values:
mouse = usb
mouse = com1
mouse = com2
mouse = com3
mouse = com4
On the terminals with no less than 64Mb RAM USB-mouse is autodetected.
If mouse without wheel you must specify:
mouse_wheel = off
mouse_accel_mult parameter changes mouse pointer speed. Default value is 5, possible values - from 0.01 to 8. To make
a very low mouse speed set:
mouse_accel_mult = 0.05
video parameter determines video card driver. All possible values are listed below. We insist on using terminal
configuration wizard to select video card driver.
svgalib 1.4.3 drivers, suffix (S).

http://www.wtware.com/docs44/config.html

7/12

15/10/2014

WTware terminal configuration file. Terminal features, parameters and their descriptions - Windows Terminal Ware.
Tseng ET4000 chip:
video = ET4000(S)
Tseng ET6000 chip:
video = ET6000(S)
Cirrus Logic GD542x chips:
video = Cirrus(S)
Cirrus Logic 546x (laguna) chips:
video = LAGUNA(S)
Trident TVGA8900/9000 chips:
video = TVGA(S)
Oak Technologies 037/067/077 chips:
video = Oak(S)
S3 Trio chips:
video = S3(S)
S3 savagechip:
video = SAVAGE(S)
ARK Logic chip:
video = ARK(S)
old ATI VGA chips:
video = ATI(S)
ATI Mach32 chip:
video = Mach32(S)
ALI2301 chip:
video = ALI(S)
Alliance Technology AT 24 / 25 / 3D chips:
video = APM(S)
nVidia Riva 128 / TNT / GeForce chips:
video = NV3(S)
WD90C31 chip:
video = PARADISE(S)
ATI Rage Pro, mach64 chip:
video = RAGE(S)
ATI Rage 128 chip:
video = R128(S)
Banshee/V3 chip:
video = BANSHEE(S)
SiS 5597 / 6326 / 620 / 530 chips:
video = SIS(S)
Intel i740 chip:
video = I740(S)
Matrox G200/G400/G450 chips:
video = G400(S)
universal VESA driver, works with almost all cards. IS NOT ABLE TO CHANGE REFRESH FREQUENCY, use it
only if there's no native driver for your card.
video = VESA(S)

svgalib 1.9.20 drivers, suffix (T).


Tseng ET4000 chip:
video = ET4000(T)
Tseng ET6000 chip:

http://www.wtware.com/docs44/config.html

8/12

15/10/2014

WTware terminal configuration file. Terminal features, parameters and their descriptions - Windows Terminal Ware.
video = ET6000(T)
Cirrus Logic GD542x / 543x / 544x chips:
video = Cirrus(T)
Cirrus Logic 546x (laguna) chips:
video = LAGUNA(T)
Trident TVGA8900/9000 chips:
video = TVGA(T)
S3 chips:
video = S3(T)
S3 Savage, Virge chip, some Trio64:
video = SAVAGE(T)
ARK Logic chip:
video = ARK(T)
ALI2301 chip:
video = ALI(T)
Alliance Technology AT 24 / 25 / 3D chips:
video = APM(T)
nVidia Riva 128 / TNT / GeForce chips:
video = NV3(T)
WD90C31 chip:
video = PARADISE(T)
ATI Rage Pro, mach64 chip:
video = RAGE(T)
ATI Rage 128 and Radeon chip:
video = R128(T)
Banshee/V3 chip:
video = BANSHEE(T)
SiS 5597 / 6326 / 620 / 530 chips:
video = SIS(T)
Intel i740 chip:
video = I740(T)
Matrox Mystique / G100 / G200 / G400 / G450 chips:
video = G400(T)
Matrox Millennium, Millennium II:
video = MILLENNIUM(T)
Intel i810 / 815 chips
video = I810(T)
Trident PCI / AGP chips:
video = TRIDENT(T)
Chips & Technologies chips:
video = C&T(T)
VIA/S3 Unichrome chips:
video = UNICHROME(T)
universal VESA driver, works with almost all cards. IS NOT ABLE TO CHANGE REFRESH FREQUENCY, use it
only if there's no native driver for your card:
video = VESA(T)

Linux Kernel Framebuffer drivers, suffix (F).


nVidia Riva/Geforce chips:
video = rivafb(F)

http://www.wtware.com/docs44/config.html

9/12

15/10/2014

WTware terminal configuration file. Terminal features, parameters and their descriptions - Windows Terminal Ware.
Intel i810, i815 chips:
video = i810fb(F)
Intel 830M/845G/852GM/855GM/865G chips:
video = intelfb(F)
Cirrus Logic GD542x/543x/544x/5480 chips:
video = clgenfb(F)
Matrox Millennium, Millennium II, Mystique, Mystique 220, Productiva G100, Mystique G200, Millennium G200,
G400, G450 and G550 chips:
video = matroxfb_base(F)
ATI Mach64 chips:
video = atyfb(F)
ATI Radeon chips:
video = radeonfb(F)
ATI Rage128 chips:
video = aty128fb(F)
SiS 300, 315 and 330 chips:
video = sisfb(F)
Trident CyberXXXX/Image/CyberBlade chips, including VIA EPIA motherboards on PLE133 chip:
video = tridentfb(F)
VIA/S3 UniChrome (CLE266, KM400, KN400, KM800, KN800, PM800, PN800, CN400) chips, VIA EPIA
motherboards on CLE266 chip:
video = viafb(F)
Cyrix MediaGX, Natsemi Geode chips (intergrated into some thinclients):
video = nsc(F)
S3 Savage:
video = savagefb(F)
tdfx voodoo 3/4/5:
video = tdfxfb(F)

XFree86 4.5.0 drivers, suffix (X).


Alliance Promotion AT3D, AT25, AT24 chips:
video = apm(X)
ARK Logic ARK1000PV, ARK2000PV, ARK2000MT chips:
video = ark(X)
ATI chips:
video = ati(X)
Chips and Technologies 65520, 65525, 65530, 65535, 65540, 65545, 65546, 65548, 65550, 65554, 65555,
68554, 69000, 64200, 64300 chips:
video = chips(X)
Cirrus Logic Alpine (5430, 5434, 5436, 5446, 5480, 7548) and Laguna (5462, 5464, 5465) chips:
video = cirrus(X)
Cyrix MediaGX, Natsemi Geode chips (integrated into some thinclients):
video = cyrix(X)
Permedia and GLINT chips:
video = glint(X)
Intel i740 chip:
video = i740(X)
Intel i810, i810-dc100, i810e, i815, i830M, i845G, i852GM, i855GM, i865G, i915, i925 chips:
video = i810(X)
Matrox MGA2064W (Millennium I), MGA1064SG (Mystique), MGA2164W (Millennium II) (PCI, AGP), G100,
G200, G400, G450, G550 chips:

http://www.wtware.com/docs44/config.html

10/12

15/10/2014

WTware terminal configuration file. Terminal features, parameters and their descriptions - Windows Terminal Ware.
video = mga(X)
NVIDIA Riva 128, 128ZX, TNT, TNT2 (Ultra, Vanta, M64), GeForce (DDR, 256), Quadro, GeForce2 (GTS, Ultra,
MX), GeForce3, Quadro2 chips:
video = nv(X)
S3 964 (revisions 0 and 1), 968, Trio32, Trio64, Trio64, Trio64V+, Trio64UV+, Aurora64V+, Trio64V2,
PLATO/PX chips:
video = s3(X)
S3 ViRGE, ViRGE/VX, ViRGE/DX, ViRGE/GX, ViRGE/GX2, ViRGE/MX, ViRGE/MX+, Trio3D, Trio3D/2X chips:
video = s3virge(X)
S3 Savage3D, Savage3D/MV, Savage4, Savage2000, SuperSavage chips:
video = savage(X)
SiS5597/5598, SiS530/620, SiS6326/AGP/DVD, SiS300/305, SiS540, SiS630/730, SiS315/H/PRO SiS550
SiS650/651/650M/740, SiS330 (Xabre) chips:
video = sis(X)
Voodoo Banshee, Voodoo3, Voodoo4, Voodoo5 chips:
video = tdfx(X)
Trident TVGA8900B, TVGA8900C, TVGA8900CL, TVGA9000, TVGA9000i, TVGA9100B, TVGA9200CXr,
TVGA8900D, TGUI9440AGi, TGUI9660, TGUI9680, ProVidia 9682, ProVidia 9685, 3DImage975, 3DImage985,
Blade3D, Cyber9320, Cyber9382, Cyber9385, Cyber9388, Cyber9397, Cyber9397/DVD, Cyber9520,
Cyber9525/DVD CyberBlade/Ai1,CyberBlade/i7, CyberBlade/i1, CyberBlade/DSTN/Ai1, CyberBlade/DSTN/i7,
CyberBlade/DSTN/i1, CyberBlade/e4, CyberBladeXP, BladeXP chips, VIA EPIA motherboards on PLE133 chip
video = trident(X)
Tseng Labs ET4000AX, ET4000/W32, ET4000/W32i, ET4000/W32p, ET6000, ET6100 chip:
video = tseng(X)
VIA CLE266 (CLE3122, CLE3022) chip. Used in new VIA EPIA models:
video = via(X)
terminal test under VMWare Workstation:
video = vmware(X)
universal VESA driver, works with almost all cards. IS NOT ABLE TO CHANGE REFRESH FREQUENCY, use it
only if there's no native driver for your card:
video = vesa(X)

resolution parameter determines screen resolution. Below is the list of common resolutions. Possibly, some of them are
not supported by your video card or driver. Use terminal configuration wizard to see available resolutions. [Resolutions
higher than 800x600 are supported only in WTware PRO]
resolution
resolution
resolution
resolution
resolution
resolution
resolution
resolution
resolution
resolution
resolution
resolution
resolution
resolution
resolution
resolution
resolution

=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=
=

640x480
800x600
1024x768
1280x1024
1152x864
1600x1200
960x720
1920x1440
720x540
848x480
1072x600
1280x720
1360x768
1800x1012
1920x1080
2048x1152
2048x1536

bpp parameter determines colour depth. Keep in mind, that Windows 2000 Server supports only 8-bit colour. Windows
2003 Server supports all possible colour depths, but not every driver is able to support all values. Use terminal
configuration wizard to see available colour depths.
bpp
bpp
bpp
bpp
bpp

=
=
=
=
=

8
15
16
24
32

refresh parameter determines screen frequency refresh, in Hz. Some LCDs work only with 60 or 75 Hz. Use terminal
configuration wizard to see all possible frequency refresh values.
refresh = 60
Only for video=...(X). This option can be used for LCD-monitors, when no other way helps to resize image to full screen:

http://www.wtware.com/docs44/config.html

11/12

15/10/2014

WTware terminal configuration file. Terminal features, parameters and their descriptions - Windows Terminal Ware.
noddc = on

If you have any comments or remarks to this article, please, let us know!
<< Documentation

2002-2014 WTware

http://www.wtware.com/docs44/config.html

12/12

You might also like