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
FILE AUTHENTICATION
File Authentication and the File System
VX 675 R
EFERENCE GUIDE 91
File
Authentication
and the File
System
Application Memory Logically Divided Into File Groups
The memory of a VX 675 terminal is logically divided into two main areas, or
partitions:
• operating system
• applications
The application partition is further divided into sub-partitions. These sub-partitions
are called file groups or GIDs.
This system of partitions and sub-partitions makes it possible to store multiple
applications in terminal memory and prevent these applications from overlapping
or otherwise interfering with each other’s operation.
There are a total of 16 file groups (Figure 29). Group 0 is the name of the
operating system partition. Group 1 is reserved for the main application.
Groups 2–14 are available for related executable files or secondary applications.
Group 15 is open, and used for shared files such as shared libraries.
Figure 29 VX 675 Application Memory Partitions
Rules for Storing Applications in Specific File Groups
Here are some important VX 675 file system features, as they relate to storing
application files in specific file groups, and how these features affect the file
authentication process:
• Most applications consist of more than one executable. For each executable
to run on the terminal, it must be signed and authenticated.
• Although not enforced by the operating system, it is recommended that only
one application be stored per file group in the application partition. Any
number of executable files can, however, be stored in a single file group.
• Using the CONFIG.SYS *GO variable, you can specify only one application to
automatically execute following a download and terminal restart. The defined
application is usually the main application stored in Group 1 and called from
the *GO variable in the CONFIG.SYS file in GID1.
NOTE
The VX 675 operating system only enforces the rule that the main application be
always stored in GID1. You can, for example, store a shared library in any file
group. Rules for Storing Applications in Specific File Groups states reasons to
follow the guidelines previously described for storing applications and libraries in
specific file groups.