# Eric - Here is a sample wnos.ini # # This file provides an example of an environment where all users # will log on following processing of this file. Each user will # have (potentially) a different desktop display of available # connections. Each user may have a different password for # authentication. # # The user desktop displayed following sign-on will be a combination # of connections specified here (global) and connection specified # in their individual environment specifications. Winterm 1200LE # is capable of accepting up to 16 connection definitions, total. # Those defined globally will be displayed first, followed by those # specified for the individual. If the sum of the number of # connections in the two files exceeds sixteen only the first # sixteen will be processed. # # The following directive enables the use of the sign-on dialog box. # signon=0 # # The following directive allows the Winterm 1200LE to attempt to # locate code files on the FTP server and to update the current # code on the device if the version on the server is different. # autoload=1 # # The following URL specifies a bitmap file which overlays the top # left part of the sign-on dialog box. It can be used to present a # company logo, special instructions for the day (of limited length) # or any other desired customization. The WT1200LE will attempt to # locate the file in the directory named bitmap, directly under the # directory named wnos, which contains this file. # #formurl=blazer.bmp # # The following directive causes the WT1200LE to use a different # FTP server. This overrides and replaces the fileserver in the # local network setup and/or the one obtained from DHCP option 161. # It will be used from the time this directive is processed until # the value in the local user interface is manually edited, until a # new value is obtained from a DHCP server on reboot, or until # another fileserver directive is processed. Until reset using one # of the named methods, the new value will persist across reboots # and power cycle events. The argument may be either an IP address # or a DNS name. # #FileServer=filesrv.wyse.com # # The following directive causes the WT1200LE to access a different # path on the FTP server. This overrides and replaces the path in # the local network setup and/or the one obtained from DHCP option # 162. Its characteristics are the same as the fileserver # directive. When this is actually used, the directory name wnos # will be appended to the rootpath before use. For instance, # (assuming that the DHCP server does not supply values for options # 161 and 162) immediately after the reboot following the processing # of these two directives the WT1200LE will start an FTP session # with fileserv.wyse.com and attempt to retrieve # /blazer/wyse/wnos/wnos.ini # ##RootPath=blazer/wyse # RootPath=wyse # # The following directives specify the global connections that # will be present on all user desktops or in all user Connect Lists # following sign-on. # # The following directive will, when activated, establish a # connection to a specific ICA server. Note that the directive is # continued onto multiple lines. Continuation is accomplished by # putting the following characters at the end of lines to be # continued: # # \ # # This only works if there is no space between the \ and the # character; the line will not be continued otherwise. The # function of each of the arguments is: # # connect=ica Specifies that this is a connect statement # and that the type of connection is ICA, # (currently, ICA is the only supported # connection type). This must be the first # item specified on the line. # description="x" Text to appear either under the icon on the # WT1200LE desktop or in the Connect List. # The text must be surrounded by double # quotation marks if it contains spaces or # punctuation. # icon=default The bitmap to be used for the WT1200LE # desktop display. The argument is either # default or a file name. If a file name is # specified, it must be located in the bitmap # directory under the wnos directory on the # FTP server. # host=IP The IP address or DNS name of the ICA server # to be contacted when this connection is # established. # username=me The username on the server that runs the # published application. The username # determines the privileges and default # directory used on the server. # # Since the following connection omits the password and domainname # fields, the client will attempt to perform a login using no # password and the default domain (whatever was last used on that # system). This will probably fail and present the user with # a login dialog box. This is more secure than putting passwords # into a file on an FTP server, which can be downloaded by anyone. # connect=rdp \ description="Eric 2" \ host=192.168.195.30 \ icon=default \ VncPrompt=0 \ Fullscreen=yes \ autoconnect=1 #icon=noname.ico \ #username=test1 # connect=rdp \ description= "George" \ #icon=noname.ico \ host=192.168.195.30 \ username=test2