User's Manual
Table Of Contents
- VX 675
- Contents
- Preface
- Terminal Overview
- Terminal Setup
- Selecting Terminal Location
- Unpacking the Shipping Carton
- Examining Terminal Features
- Examining Connection Ports
- Installing the Paper Roll
- Installing the SIM Card
- Installing the SD Card
- Using the Battery
- Battery Behavior (No Power Pack)
- Connecting the Terminal Power Pack
- Charging the Battery
- Using the VX 675 Base Stations
- Powering Up the Base
- Docking the Terminal on the Base
- Undocking the Terminal from the Base
- Conducting Wireless Transactions
- Conducting Smart Card Transactions
- Using the Magnetic Card Reader
- Connecting to USB Host
- VX 675 ECR (Fiscal Module) Support
- VX 675 3G and GPS Support
- Using the Terminal Keys
- Verix Terminal Manager
- File Authentication
- Performing Downloads
- Downloads and Uploads
- Download Methods
- Download Tools
- Download Content
- Full and Partial Downloads
- Support for Multiple Applications
- Use of I: drive and F: drive
- File Authentication Requirements
- Required Certificates and Signature Files
- The File Authentication Process During an Application Download
- File Group Permissions
- Download an Operating System Update Provided by VeriFone
- File Authentication for Back-to-Back Application Downloads
- Timing Considerations Due to the Authentication Process
- Support for File Compression
- Effect of Downloads on Existing Files and Data
- Direct Operating System Downloads
- Back-to-Back Application Downloads
- Specifications
- Maintenance
- VeriFone Service and Support
- System Messages
- Troubleshooting Guidelines
- Port Pinouts
- ASCII Table
- VX 675 Battery Information
- Glossary
- Application ID
- Application program
- Application prompt
- ASCII
- Back-to-back application download
- Baud
- Bit
- Block
- Boot loader
- Buffer
- Byte
- Calendar/clock chip
- Card reader
- Carrier
- Certificate
- Character
- CONFIG.SYS file
- CPU
- Data
- Data entry
- Data packet
- Default
- Delete
- Diagnostics
- Direct download
- Display
- Download
- File authentication
- Firmware
- Fixed prompt
- Flash memory
- Host computer
- Input
- Interface
- Keyed file character set
- Keyed file editor
- Keyed file record
- Keypad
- Local functions
- Manual transaction
- Memory
- Messages
- Non-volatile memory
- Normal Mode
- Packet
- Packet-switched networks
- Parameter
- Password
- PC
- Peripheral terminal
- Port
- POS terminal
- Power pack
- Prompt
- Protocol
- PTID
- RAM
- Remote host computer
- Scroll
- Search key
- Serial port
- Signature file
- mDRAM
- Subroutine
- Swipe
- Verix Terminal Manager
- Verix Terminal Manager password
- Terminal
- Terminal ID
- Terminal-to-terminal application upload
- Track 1, 2, or 3 data
- Transaction
- Variable
- Volatile memory
- Index
- Contact VeriFone
PERFORMING DOWNLOADS
Effect of Downloads on Existing Files and Data
VX 675 R
EFERENCE GUIDE 125
9
**VERIFYING FILES**
CHECK CERTIFICATE
(FILENAME.CRT)
**AUTHENTIC**
or
--- FAILED ---
The file authentication module continues to authenticate
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” message is displayed directly below the
filename of the signature file. If file authentication fails for a
specific signature file, the “
FAILED” message 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.
10
(Application Prompt)
or
DOWNLOAD NEEDED
If the downloaded application successfully authenticates,
the corresponding application prompt or logo is displayed
upon restart.
The terminal can now process transactions.
Note: The message 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
Operating System Download Procedure using the correct
certificates and/or signature files.
Table 14 Direct Application Download Procedure (continued)
Step Display Action