VeriFone VX 680 Reference Manual page 134

P D
ERFORMING OWNLOADS
Download from a USB Flash Drive
134
VX 680 R
EFERENCE
Table 19 USB Flash Drive Download Procedure
Step Display
9 **VERIFYING FILES**
CHECK CERTIFICATE
FILENAME.CRT
*AUTHENTIC*
**VERIFYING FILES**
COMPARE SIGNATURE
FILENAME.P7S
FILENAME.OUT
*FAILED*
10 <application prompt>
DOWNLOAD NEEDED
<error message>
G
UIDE
Action
On startup, the file authentication module
authenticates any new signature files
downloaded with the OS files.
When the signature file authentication routine
starts, the status display informs you of the
progress of the authentication process.
If file authentication succeeds for a specific
signature file, the
*AUTHENTIC*
displayed directly below the filename of the
signature file. If file authentication fails for a
specific signature file, the
is displayed for five seconds below the
filename and the terminal beeps three times,
allowing you to note which signature file failed
to authenticate. The authentication process
then proceeds to the next signature file until all
signature files are validated.
When all new signature files are
authenticated, the terminal restarts, and the
application specified in the *GO variable or the
default application in Group 1 executes and
starts running on the terminal.
If the downloaded application successfully
authenticates, the corresponding application
prompt or logo is displayed upon restart.
The terminal can now process transactions.
The message
Note: DOWNLOAD NEEDED
appears if:
The *GO variable is not set.
•
*GO does not specify that an application is
•
present.
The application did not authenticate (invalid
•
or missing *.p7s file).
The application uses shared libraries that
•
are missing or were not authenticated
(invalid or missing *.p7s files).
If one or more executables in the application
fail to successfully authenticate, the
application may not run. If the application
attempts to access an unauthenticated
executable or library, it may crash. Repeat the
Direct Application Download Procedure
the correct certificates and/or signature files.
message is
message
*FAILED*
using