T1500 WINDOWS-BASED TERMINAL NETWORK INSTALLATION GUIDE
T1500 WINDOWS-BASED TERMINAL NETWORK INSTALLATION GUIDE December 1999
ii Notice The information in this document is subject to change without notice. COMPAQ COMPUTER CORPORATION SHALL NOT BE LIABLE FOR TECHNICAL OR EDITORIAL ERRORS OR OMISSIONS CONTAINED HEREIN; NOR FOR INCIDENTAL OR CONSEQUENTIAL DAMAGES RESULTING FROM THE FURNISHING, PERFORMANCE, OR USE OF THIS MATERIAL. This document contains information protected by copyright. No part of this document may be photocopied or reproduced in any form without prior written consent from Compaq Computer Corporation.
iii Federal Communications Commission Notice This equipment has been tested and found to comply with the limits for a Class B digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference in a residential installation. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instructions, may cause harmful interference to radio communications.
iv European Union Notice Products with the CE Marking comply with both the EMC Directive (89/336/EEC) and the Low Voltage Directive (73/23/EEC) issued by the Commission of the European Community.
v Control No. 075C License Agreement YOU SHOULD CAREFULLY READ THE FOLLOWING TERMS AND CONDITIONS BEFORE USING THIS SOFTWARE (TOGETHER WITH ANY SUPPLIED DOCUMENTATION, HEREAFTER “SOFTWARE”), WHICH IS COPYRIGHTED BY LICENSOR. USING THIS SOFTWARE INDICATES YOUR ACCEPTANCE OF THE FOLLOWING TERMS AND CONDITIONS. Grant You may use the Software in conjunction with Your hardware (Terminal).
vi Limit of liability UNDER NO CIRCUMSTANCES SHALL LICENSOR BE LIABLE FOR LOSS OF DATA, COST OF COVER, OR ANY INCIDENTAL OR CONSEQUENTIAL DAMAGES, HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY. THESE LIMITATIONS SHALL APPLY EVEN IF LICENSOR OR ITS RESELLER HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES, AND NOTWITHSTANDING ANY FAILURE OF ESSENTIAL PURPOSE OF ANY LIMITED REMEDY PROVIDED HEREIN.
Contents Overview Introduction xi How to Use This Guide xi References xi DHCP/BOOTP xii Time Server xii SNMP xii Other RFCs xii 1 Installation Overview and Planning Overview of Installation Procedure 2 Planning Your Installation 3 Step 1. Complete Worksheets 3 Step 2. Configure Terminal Start-Up Resources 3 Step 3. Configure Optional Terminal Start-Up Resources Step 4. Configure Server Application Resources 4 Step 5. Select Location of Browser 4 Step 6.
viii Option 43 Vendor-Specific ID 13 NETSVC 13 NOSWAP 14 REFLASH 14 MF_DIR 14 MF_CFG 15 XFS 15 XDMCP 15 BUDDY_BOOT 15 Packet Size 16 Option Overload 16 Option 18 vs. Option 43 vs.
ix 6 Installing CD Software onto the Server(s) CD Contents 39 Running the Installation Program 39 Text-Mode Installation 43 GUI-Mode Installation 44 Installing on Non-Supported Servers 45 A T1500 Windows-Based Terminal Quick-Start Instructions Quick-Start Procedure 48 “G-Key Reset” Procedure 50 B Installation Planning Worksheets Terminal Start-Up Resources Worksheet 53 Optional Terminal Start-up Resources Worksheet 54 Server Application Resources Worksheet 55 Browser Launch Location Resources Worksheet
x
Overview Introduction This guide explains how to install software from the installation CD onto your server and how to configure the resources resident on the server to support Compaq T1500 Windows-Based Terminals for this software release. How to Use This Guide For full access to all the terminal resources, you will need to plan and configure your server setup as explained in Chapter 1 of this guide.
xii DHCP/BOOTP RFC 1534 - Interoperation between DHCP and BOOTP RFC 2131 - Dynamic Host Configuration Protocol RFC 2132 - DHCP Options and BOOTP Vendor Extensions Time Server RFC 868 - Time Protocol SNMP RFC 1155 - Structure and Identification of Management Information for TCP/IP-based Internets RFC 1157 - A Simple Network Management Protocol (SNMP) RFC 1212 - Concise MIB Definitions RFC 1213 - Management Information Base for Network Management of TCP/IP-based internets: MIB-II Other RFCs RFC 1350 -The T
1 Installation Overview and Planning This document describes how to install the T1500 software on the following computer servers: • SCO OpenServer 5.0.5 • SCO UnixWare 7 • Linux (both Slackware and Red Hat) • Windows NT Server • HP/UX For technical support refer to the Compaq Technical Support telephone numbers for your area.
2 Chapter 1 Server resources can be provided from platforms other than the above-listed ones, but Compaq has not certified other environments and can not be responsible for any problems related to incorrectly configured servers. If you are going to operate in a different server environment, read this entire document very carefully to determine if there are any issues that you might need to resolve. Overview of Installation Procedure There are two major parts to the installation: 1.
Installation Overview and Planning 3 Planning Your Installation The software installation procedure is broken down into 6 basic steps, including the planning described in this chapter. The following brief descriptions of the basic steps do not by themselves provide enough information for you to fill in the planning worksheets presented in Appendix B of this document; you should also read the chapters pertaining to the individual worksheets for full information.
4 Chapter 1 Step 3. Configure Optional Terminal Start-Up Resources A set of resources independent of the individual applications on the terminal is strongly recommended for ease of use of the system as a whole.
2 Configuring Terminal Start-Up Resources Several network resources are either required or recommended for starting up the terminal initially in a network-boot environment. The resources in this category use the following 6 network protocols: BOOTP NFS DHCP DNS TFTP Time Server A brief description of the resources and any special configuration requirements for each protocol are provided in this chapter. Some resources (such as NFS) may also be described in other chapters of this document.
6 Chapter 2 When booting in a network environment, BOOTP provides the terminal with the following required information: the terminal’s IP address; the IP address of the TFTP boot server; the pathname of the operating system file to be loaded using the TFTP server; the NFS directory to use for the terminal’s root file system (including NFS server IP address and pathname on that server); and a subnet mask (typically 255.255.255.0 for Class C IP addresses and 255.255.0.0 for Class B IP addresses).
Configuring Terminal Start-Up Resources 7 Figure 2-1 Bootptab File Example .c_terminal:ht=1:ds=132.237.1.42:gw=132.237.20.1:sm=255.255.255.0:\ :dn=xx.com:sa=132.237.20.2:hd=/tftpboot:bf=vmlinux:\ :T17=”132.237.20.2:/nwt/root”: term1:ha=00800c123456:ip=132.237.20.5:tc=.c_terminal term2:ha=00800c123457:ip=132.237.20.4:tc=.
8 Chapter 2 For all non-Windows server platforms, bootp can be run either at boot or from inetd. It is recommend that bootp be run from inetd, although with many terminals and a stable environment (i.e., an unchanging list of terminals), it may be faster to run via automatic start-up at server boot. Consult the manual pages for the bootp program on your server platform. Linux uses bootpd, UnixWare uses in.bootpd, Openserver uses bootpd, and HP/UX uses bootpd.
Configuring Terminal Start-Up Resources 9 In a local-boot environment, DHCP can provide a set of configuration parameters, which reduces the need to configure the terminal’s Select | System | Setup | Connectivity | Internet | DHCP dialog box. The default (out of the box) configuration assumes DHCP provides all network configuration information. As such, the fields mentioned above for BOOTP all apply, except that the TFTP server (sa), TFTP boot file (bf), and Root directory (T17) are not used.
10 Chapter 2 Table 2-1 DHCP Options Option Number Option Description 1 Subnet Mask 3 Router 6 Domain Name Server 12 Host Name 15 Domain Name 17 Root Path 18 Extension Path 28 Broadcast Address 43 Vendor-Specific Information 48 X-Windows Font Server 49 XDMCP Addresses 51 Lease Time 52 Option Overload 53 DHCP Message Type 54 DHCP Server IP Address 55 Parameter Request List 57 Maximum DHCP Message Size 58 T1 (renew) Time 59 T2 (rebind) Time 60 Vendor Class Identifier
Configuring Terminal Start-Up Resources 11 Option 48 assumes TCP and port 7100 for font server access. If other ports are to be used, you must use the vendor-specific option described below. Also, option 49 assumes Query mode. If Direct is wanted, use the vendor-specific option.
12 Chapter 2 Table 2-2 Additional Vendor-Specific Options Option 43 Number Description Type/Length/Value for Option 43 1 Vendor-specific ID. Integer 4, 0x76583A1C NETSVC 2 Network service machine and directory. String, variable, same format as option 18 string. NOSWAP 3 If this option is provided, swapping is turned off. Integer 1, any value. REFLASH 4 If this option is provided, the reflash utility is invoked in a network-boot environment. Integer 1, any value.
Configuring Terminal Start-Up Resources 13 In a network-boot environment, the client and vendor identifiers are not modifiable by the user. The terminal provides the ability to change the Client ID, Vendor ID, and Hostname fields consistent with the RFCs. The default Vendor ID is Compaq-T1500. The default client ID is the MAC address with a key (consistent with the RFC specifications). The default hostname is the letter “t” followed by the last 6 digits of the MAC address.
14 Chapter 2 DNS resolvable machine name, share is the share name, and path is an optional path within that share. For name resolution, an entry in the terminal's host file Setup | Connectivity | Internet | DNS | Hosts) Hosts qualifies. For NFS, the directory (Setup MUST be exported with read/write/execute permissions and with root mapping to root, not to nobody. For SMB, the server's guest account needs to be activated and guest users need to be able to connect to that share for full control.
Configuring Terminal Start-Up Resources 15 Setup | Connectivity | Internet | resolution, an entry in the terminal's host file (Setup DNS | Hosts) Hosts qualifies. For NFS, the directory MUST be exported with read/write/ execute permissions and with root mapping to root, not to nobody. For SMB, the server's guest account needs to be activated and guest users need to be able to connect to that share for full control.
16 Chapter 2 Packet Size The terminal is capable of sending and receiving the Maximum DHCP Message size option, allowing packets to contain up to 1500 bytes, including the DHCP header in this size. Since some DHCP servers will only respond to packets that are of the smallest size, the packets sent by the terminal are guaranteed to fit in a minimum size. If the DHCP server does not honor option 57, or honors one smaller than the one the terminal accepts, the terminal will operate successfully.
Configuring Terminal Start-Up Resources 17 Option 18 vs. Option 43 vs. Options 128+ All three methods (Option 18, Option 43, Option 128+) provide identical capabilities, just in different manners. It is recommended that only one method be used, but you are not restricted to this.
18 Chapter 2 Table 2-3 Labels and Data for Text Format Option, Option , Continued Option Number Label Notes 40 NISDOMAINNAME Not currently used. 41 NISSERVER Not currently used. 42 NTPSERVER Not currently used. 43 Not allowed. 48 XFONTSERVER First element; subsequent elements append a number contiguous to the label. 49 XDMCP First element; subsequent elements append a number contiguous to the label. 51 Not allowed. 52 Not allowed. 53 Not allowed.
Configuring Terminal Start-Up Resources 19 Files ending in a .txt name are treated as text files. Any other filename is treated as an RFC-compliant file. Use of this option requires a TFTP server. Since path names are included in the file, the TFTP server must accept UNIX-style file separators, not DOS-style separators. Likewise, the default transfer mode must be binary, and the file (either format) must be capable of being read by the terminal without modifications (i.e.
20 Chapter 2 TFTP TFTP is required in a network-boot environment. The TFTP server loads the terminal’s operating system off the server into memory on the terminal. This operating system then controls all other actions performed from the terminal. This resource is used once each time a network-boot terminal is powered-up. If a local-boot environment uses DHCP, and DHCP supplies option 18, the server named in option 18 must support TFTP.
Configuring Terminal Start-Up Resources 21 The following four requirements are mandatory and must be met in the NFS configuration: Note IMPORTANT! IMPORTANT If these requirements are not met, the terminals will not work in a network-boot environment. 1. The client root account map must be able to access the server root account (on Linux, this is called no_root_squash, and on SCO Openserver 5.05, set the NFS option to -anon=0).
22 Chapter 2 DNS DNS is a protocol designed for converting the relatively easy-to-remember descriptive machine/terminal names into IP addresses, which is their actual representation on the Internet/intranet. Although DNS is not required for the terminals to be functional, it is strongly recommended to use DNS. For example www.name.com is a lot easier to remember than a string of numbers (nnn.n.nnn.nnn).
3 Configuring Optional Terminal Start-Up Resources Several server resources can enhance terminal operation but are not among the minimum required for the terminal to function. The resources in this category use the following network protocols: NFS SMB HTTP FTP SNMP and may use the following serial line protocols: PPP SLIP CSLIP This chapter provides a brief description of where the above-listed protocols are used and discusses any special configuration requirements.
24 Chapter 3 Because of limited local storage capacity in the terminal, the fonts resident on the terminal are the minimum set for use with all applications. If a locally booted terminal uses the network services director, additional fonts are automatically made available. All the network services are already provided for the users who perform a network boot; no additional measures need to be taken to ensure that this group of users enjoys these benefits.
Configuring Optional Terminal Start-Up Resources 25 For a network printer to be used (via SMB), all the requirements above must be met. Also, for a server with an NTFS file system, the security must be altered to allow guests to have full access to all files and directories in the network services tree. Perform the following steps: 1. Use Windows NT Explorer to locate the folder in which network services is installed (:\netservices is the default). 2.
26 Chapter 3 HTTP (Help) HTTP is the protocol used by the World Wide Web. The server-based user help for the terminal is distributed as a tree of HTTP links and is on the installation CD. Terminal help can be installed on a WWW server, but because of network traffic or your configuration, it may be more desirable to configure a local HTTP server and install the help tree there.
Configuring Optional Terminal Start-Up Resources 27 CSLIP CSLIP stands for Compressed Serial Line Internet Protocol and is a variant of SLIP that uses VJ header compression. The host and server name requirements mentioned under SLIP also apply to CSLIP. FTP FTP is one of the protocols that will be used to upgrade from the current software release to future releases. When implemented, configuration of an FTP server will be recommended, but the exact details currently are not available.
28 Chapter 3
4 Configuring Server Application Resources Several server resources apply to the individual applications that run on the terminal. These resources are not needed for basic functioning of the terminal, but individual applications require them. The resources in this category use the following network protocols: HTTP POP3/IMAP4 ICA RSH This chapter provides a brief description of where each protocol is used and any special configuration requirements.
30 Chapter 4 POP3/IMAP4 POP3 and IMAP4 are the Post Office Protocols used by the e-mail function embedded in Netscape Communicator on the terminal. If you are using the e-mail function to send and read e-mail, you may need to configure a POP3 or IMAP4 server to manage the e-mail. The e-mail user can also communicate with an individual’s ISP account (if configured for POP3) to view that user’s e-mail. Every user may need an individual account on the POP3/IMAP4 server.
Configuring Server Application Resources 31 Note RSH support is not available from Windows NT servers. Even if X clients are installed on NT, RSH support must be available from other server(s) for the X Manager to be able to launch them. The X Manager is the terminal’s interface to RSH; on the server the following must typically must be configured for RSH support: Note For exact details refer to the manuals on your server.
32 Chapter 4 where terminal is the terminal name and user is the user name from the terminal (root is automatically used if security is disabled; guest is automatically used if security is enabled and auto login as guest is selected). In addition, the terminal optionally supports both Kerberos authentication and DES data encryption for RSH commands, although the X protocol packets for an X application will not go through the DES data encryption layer.
Configuring Server Application Resources 33 Any command executed through this mechanism will be run as that special user, although the SHELL environment variable is replaced with the first entry in the rshsecure.cfg file and the DISPLAY environment variable is set to point back to the terminal, allowing shell scripts that launch sets of X applications to work.
34 Chapter 4
5 Selecting Browser Location The browser application is designed to run either locally or from a server. Normally it resides and is run locally. Based upon the number of users running an application, the processing power of the server, the types of operations being performed by the users with the application, and the type of network connection between the terminal and the server, it may be more advantageous to run the application from a server rather than locally.
36 Chapter 5 • Your company has standardized on a browser other than Netscape Communicator. Reasons to execute the browser locally: • Less network bandwidth is available. • You require faster start-up of the browser application. • Many users are on the network. • Your terminal is connected to the network via a serial or phone line. If you choose to execute Communicator locally, there are several configuration options you may choose, each of which will enable different components of Communicator.
37 Selecting Browser Location Table 5-1 lists the various configurations of the terminal and the external controls that were imposed on Communicator for each configuration. Table 5-1 Netscape Communicator Constraints Configuration Save/Save As Java Main/News Composer Local Home/No Swap No Yes No No Swap No Yes No No Net Home/No Swap No Yes Yes Yes Swap No Yes Yes Yes No Swap Yes Yes Yes Yes Swap Yes Yes Yes Yes Local Boot: Network Boot: Consequences: 1.
38 Chapter 5
6 Installing CD Software onto the Server(s) This chapter describes the procedure for installing the software provided on the T1500 Windows-Based Terminal installation CD. The software is installed onto the server(s) you selected when filling out the worksheets for Chapter 1.
40 Chapter 6 Caution There is currently no check for sufficient disk space and no undo procedure. Total disk space required to install all software on the CD is 650 MB. On UNIX, the script determines if GUI mode will be used based upon the DISPLAY environment variable; if it is set, the script uses the GUI, if it is not, it will run in text mode.
Installing CD Software onto the Server(s) 41 Mount the CD-ROM drive using the following command: Platform Command SCO UnixWare mount -r -F cdfs /dev/cdrom/c0b0t510/cdrom SCO OpenServer mount /dev/cd0/cdrom Slackware Linux mount /dev/cdrom/cdrom Red Hat Linux mount /mnt/cdrom /cdrom HP/UX • To mount at the beginning: Make sure /usr/sbin is in the program search path. Do a ps to make sure the pfs software is not already running.
42 Chapter 6 Change the active directory to the CD-ROM drive (cd /cdrom). Note Windows uses “ \ ” as directory separator, and UNIX uses “ / ”. Prior to start of the TCL/TK runtime, use the appropriate separator. Run the install procedure (./install). Note that ./install explicitly runs the install program in the current directory. This is because there may be other install programs in your search path and because the current directory is not normally part of root’s search path.
Installing CD Software onto the Server(s) 43 The installation script will not install any software onto your system until after all responses are entered. The last prompt will tell you when the installation is ready to proceed. Up until then, you can abort the installation safely by using the interrupt character (or by typing “q” for the yes/no prompts) for text mode or pressing the Cancel button for GUI mode. Text mode will abort immediately; GUI mode will ask for confirmation.
44 Chapter 6 Directories are made as required, so a /T1500/root directory extraction will also create /T1500. If the directory and/or file exist at the time the second section of the installation is reached (querying for where to install), and if the user chooses to overwrite the data (applies to install only, not to update), the files and/or directories are removed prior to installing. This removes inappropriate files and directories (such as from an aborted installation).
Installing CD Software onto the Server(s) 45 There are five sections to the GUI-mode installation. Each has a distinct background screen. The first section is purely informative to you, the user. The second section contains a series of checklists, asking for which items you wish to install on that server. The third section asks for locations based upon the items selected in the second section. The fourth section confirms whether you wish to proceed and update your disk or abort your installation.
46 Chapter 6 The upgrade directory contains the scripts necessary for upgrading local-boot terminals from one release to another. The admin directory contains an ever-growing set of scripts that administrators can use or refer to for managing their terminals via NFS.
A T1500 Windows-Based Terminal Quick-Start Instructions The T1500 Windows-Based Terminal is shipped from the factory configured for local boot. Instructions are included in this appendix to convert to network boot if you require this mode of operation. If you require additional network services for a local-boot (default) terminal, you must use the server setup procedure. This procedure starts with Chapter 1 of this document.
48 Appendix A Quick-Start Procedure These instructions are for network administrators and end users already familiar with networks and terminals. They provide the minimum information needed to get the terminal into a basic operating mode that permits access to the full help system, services, and upgrade software residing on designated servers on the network. 1. Set the terminal on the desktop. 2. Connect the terminal communication interfaces.
T1500 Windows-Based Terminal Quick-Start Instructions 49 7. To further configure the network setup, use the Select | System | Setup window’s Connectivity dialog boxes. Most of the information can be supplied by your network administrator: • For ethernet networking, make entries in the Internet dialog boxes. • For serial networking (network connection through a server), make entries in the Serial Ports and Serial Internet dialog boxes.
50 Appendix A “ G-Key Reset” Procedure You may reset the terminal software settings by using the G-Key Reset procedure: • Turn on power and upon hearing the first beep immediately press the G key. The beep occurs coincident with expansion of the splash screen to full window size. The Login dialog box displays only if security is enabled, in which case enter a valid administrator or user login name and password.
B Installation Planning Worksheets The following worksheets should be filled in during the planning phase (Chapter 1) and used during the installation phase (Chapters 2 through 6) of your resource configuration process. The chapter corresponding to each worksheet provides specific information about the entries in the worksheet, and should be consulted as the worksheet is filled in. Note It is suggested that you make and use photocopies of the worksheets and retain the originals for possible later use.
52 Appendix B In an existing network environment where workstations are on people’s desktops, many server resources may already be configured. In new installations you will have to determine which server resources you must configure for use with the network terminals, based upon your needs and environment (and filled in worksheets).
Yes No No Yes No No TFTP B O O TP DHCP NF S (root) DNS Ti m e Ser v er Recommended Recommended Required Required* Required* Required Is t h e r es o u r c e r eq u i r ed f o r r ec o m m en d ed f o r n et w o r k boot? Recommended Recommended No Recommended No No Is t h i s r es o u r c e r eq u i r ed o r r ec o m m en d ed f o r l o c al b o o t ? * Either BOOTP or DHCP is required, but not both.
Is s o f t w ar e o n t h e CD r el at ed to this r es o u r c e? Yes Yes Yes No No No No No No Yes Ser v er Res o u r c e NF S (network services) SNMP HT T P (remote help) PPP SL IP CS L I P FTP (upgrades) HTTP (upgrades) SMB (network services) A d m i n To o l No No No No No No No Recommended No Recommended Is t h e r es o u r c e r eq u i r ed f o r r ec o m m en d ed f o r n et w o r k boot? Recommended No No No No No No Recommended No Recommended Is t h i s r es o u r
Is s o f t w ar e o n t h e CD r el at ed to this r es o u r c e? No No No No Yes Ser v er Res o u r c e HTTP (b r o w s er ) POP3 SMTP ICA RS H Ser v er Nam e (Wr i t e d o w n t h e s er v er n am e/IP ad d r es s f o r eac h r es o u r c e) Installation Worksheet for Step 4 (Chapter 4) Ser v er A p p l i c at i o n Res o u r c es Wo r k s h eet Installation Planning Worksheets 55
Is s o f t w ar e o n t h e CD r el at ed to this r es o u r c e? No No Ser v er Res o u r c e ICA (remote browser) RS H (remote browser) Ser v er Nam e (Wr i t e d o w n t h e s er v er n am e/IP ad d r es s f o r eac h r es o u r c e) Installation Worksheet for Step 5 (Chapter 5) B r o w s er L au n c h L o c at i o n Res o u r c es Wo r k s h eet 56 Appendix B
Is s o f t w ar e o n t h e CD r el at ed to this r es o u r c e? Yes Yes Yes Yes Ser v er Res o u r c e Rep ai r Im ag es Up g r ad e Im ag es Up g r ad e Sc r i p t s A d m i n i s t r at i v e Sc r i p t s No Recommended Recommended No Is t h e r es o u r c e r eq u i r ed f o r r ec o m m en d ed f o r n et w o r k boot? Recommended No No Recommended Is t h i s r es o u r c e r eq u i r ed o r r ec o m m en d ed f o r l o c al b o o t ? Installation Worksheet for Step 6 Part 1 (Chapter 6
1 MB 250 MB 200 MB 40 MB 1 MB 60 MB 32 MB 1 MB 1 MB 1 MB 10 MB TFTP NFS (r o o t ) NFS o r SMB (n et w o r k s er v i c es ) HTTP (h el p ) SNMP Rep ai r Im ag es Up g r a d e Im ag es ) Up g r ad e Sc r i p t s A d m i n i s t r at i v e Sc r i p t s RSH Sec u r e Sh el l A d m i n To o l /mwt/admin.tcl/ /mwt/rshsecure/ /mwt/admin.sh/ /mwt/upgrade.sh/ /mwt/upgrade.fw/ /mwt/local/ /mwt/snmp/mib.
Installation Planning Worksheets 59
T1500 Windows-Based Terminal Network Installation Guide Created using FrameMaker® and Acrobat® The on-line book is provided in PDF and presented on the terminal product CD.
