Specifications

PERFORMING DOWNLOADS
Omni 37xx Download Differences
90 OMNI 37XX REFERENCE MANUAL
A downloaded OS is processed and authenticated while stored in Group 1 RAM.
As the files are authenticated under the authority of the certificates and signature
files included in the OS download package, they move automatically into Group 0.
This process, which usually takes a few minutes, is completely transparent during
the download procedure.
File Redirection in Back-to-Back Application Downloads
In a back-to-back application download,
all application files stored on the sending
terminal — in both file systems and in all file groups — transfer to the receiving
terminal in a single operation.
For this type of download, you
must select Group 1 as the target group on the
sending and receiving terminal. When you initiate the download on the receiving
terminal, all application files, as well as all special files required for file
authentication and terminal configuration settings on the sending terminal,
download to the receiving terminal.
In this type of data transfer operation, some file redirection does occur
automatically as a result of the file authentication procedure that occurs on the
receiving terminal. This redirection process is transparent during the download.
Briefly, all files initially download into RAM, and are then redirected based on the
directory and subdirectory names of the sending terminal’s file system. Signature
files must always be authenticated in RAM. If the target file the signature file
authenticates is stored in flash, the signature file is moved to flash only after the
target file is successfully authenticated.
To successfully perform a back-to-back download, all signature files that are
required to authenticate application executables must reside in the memory of the
sending terminal. If the *FA variable is present in the Group 1 CONFIG.SYS file of
the sending terminal, it must be set to 1 to retain all previously downloaded
signature files.
If a signature file is missing on the sending terminal, the target application file that
it authenticates is not authenticated on the receiving terminal and, if the target file
is an executable, it is not allowed to run on the receiving terminal.
File Authentication
Requirements
Chapter 5 provided a general introduction to the file authentication process. Now
we become more task-oriented and see how the file authentication process
affects how to perform the various download procedures.
Required Certificates and Signature Files
Here are some important points to remember about how certificates and signature
files relate to application download procedures:
• Before an executable file can be downloaded to and be allowed to run on an
Omni 37xx terminal, the file must be digitally signed on the download
computer using the file signing tool, FILESIGN.EXE. The result of this
procedure is a signature file recognized by its *.p7s file name extension.