TITLE: Evo T20 256/256 XPe Binary Firmware (ICA, RDP, TEC, IE, Wfilter)

VERSION: 5.01 Rev B255
DESCRIPTION:
This contains the XPe firmware for the Evo Thin Client models listed below.

Add-ons included with this build:
 ICA v6.20.985
 RDP v5.1.2600.0
 TEC v1.6.0
 VNC v3,3,3,9
 IE v6.00.2600.0000

PURPOSE: Routine Release
SOFTPAQ NUMBER: SP22497
SUPERSEDES: None
EFFECTIVE DATE: February 27, 2003
CATEGORY: OS and OS Enhancements
SSM SUPPORTED: No

PRODUCT TYPE(S):
Thin Clients
 
PRODUCT MODEL(S): 
Thin Client Evo T20 256/256

OPERATING SYSTEM(S): 
OS Independent
 
LANGUAGE(S):
English 
 
PREREQUISITES: 
Rapport 3.02 with Service Pack 2 or later must be installed on your server.
 
HOW TO USE: 

1. Download the SoftPaq to a directory on your hard drive.
The file downloaded is a self-extracting executable
with a filename based on the SoftPaq Number above.

2. Execute the downloaded file and follow the on-screen
instructions.

SPECIAL INSTRUCTIONS FOR PXE UPGRADE
The PXE upgrade process is accomplished using the "Pull" and "Push" scripts
that are pre-registered in Rapport 3.02 SP2.  There are 2 methods for this
process:

METHOD 1 (PREFERRED)

(1) Using the NetXfer tool, copy and paste the binary into the NetXfer folder,
rename to "bootp.bin", and send down the image to the client. (For additional
instruction on the Netxfer tool download SP22454)

(2) With the client attached to the network, send the appropriate "Pull" script
in Rapport to the client.  This will pull the image from the client into the
inetpub\ftproot\Rapport directory under the folder of the same name.

EX - If you pulled an image using the "Pull_T20PXE_Image" script, it would
then copy the "putT20.i2d" file into the corresponding "Pull_T20PXE_Image" folder.

(3) Copy and paste the pulled image file into the corresponding "Push" folder.
Ex - Using the example above, you would copy the "putT20.i2d" file into the
"Push_T20PXE_Image" folder.

(4) Run the appropriate "Push" script to the other clients you wish to push the
image down to.

Ex. - Using the same example above, you would run the "Push_T20PXE_Image"
script to the other client(s).

METHOD 2

(1) Rename the binary (Ex. H064B218.bin) to "putT20.i2d" or "putT30.i2d" based
upon on the appropriate platform.

(2) Copy the newly named *.i2d file to the appropriate platform "Push" folder
in the software repository.

(3) Distribute the appropriate "Push" package to the target client.
CAUTION - The renamed binaries are subtly different than the i2d files that are
created by using "Pull" scripts within Rapport.  When they are sent to the
client(s), the renamed binaries will not do the following checks that are done
by the "Pulled" i2d files:

	(A) Check for correct flash size
	(B) Check for correct NOR configuration (Ex. - images pushed to 192/256
	configurations must be created for 192/256 configurations)
	(C) Check for correct platform (Ex. -  T20 -> T20 or T30 -> T30 only)
	If a renamed binary is "pushed" to a non-corresponding platform or flash
	configuration, the image could be corrupted.

EX - Rename a T20 64/64 NTE PXE binary and then push the renamed binary to a
T30 128/128 NTE PXE.  Even though neither the flash nor the platform
correspond, the image could still go down to the client and corrupt the image.
 
 
Copyright (c) 2003 Hewlett-Packard Development Company, L.P.