FCC ID: B32OMNI3600D Point of Sale Terminal

 

VERIX OPERATING ENVIRONMENT SOFTPAY E-PAYMENT APPLICATION VERIX DEVELOPER TOOLKIT DEVELOPMENT TOOLS VERISHIELD SECURITY ARCHITECTURE OMNI 37XX HAND-OVER-COUNTER MULTI-APPLICATION APPLIANCES OMNI 33XX MULTI-APPLICATION APPLIANCES OMNI 3600 HAND-HELD RADIO MODEM APPLIANCES VERICENTRE APPLIANCE MANAGEMENT SUITE Omni 3600 Reference Manual Part Number 22379, Revision A Omni 3600 Reference Manual 2003 VeriFone, Inc. All rights reserved. No part of the contents of this document may be reproduced or transmitted in any form without the written permission of VeriFone, Inc. The information contained in this document is subject to change without notice. Although VeriFone has attempted to ensure the accuracy of the contents of this document, this document may include errors or omissions. The examples and sample programs are for illustration only and may not be suited for your purpose. You should verify the applicability of any example or sample program before placing the software into productive use. This document, including without limitation the examples and software programs, is supplied As-Is. VeriFone, the VeriFone logo, Omni, VeriCentre, Verix, and ZonTalk are registered trademarks of VeriFone. Other brand names or trademarks associated with VeriFones products and services are trademarks of VeriFone, Inc. All other brand names and trademarks appearing in this manual are the property of their respective holders. Comments? Please e-mail all comments in this document to Tell_Us_More@VeriFone.com VeriFone, Inc. 2455 Augustine Drive Santa Clara CA 95054-3002 www.verifone.com Part Number 22379, Revision A C H AP T E R 1 Omni 3600 Terminal and Omni 3600 Base Installation CONTENTS Select a Location . 7 Omni 3600 Terminal . 7 Omni 3600 Base . 7 Environment . 7 Convenience . 8 Omni 3600 Terminal . 8 Unpack the Shipping Carton . 8 Terminal Features. 10 Power Port . 11 Smart Battery . 11 Turn On/Off the Omni 3600 Terminal . 14 Paper Installation . 14 Install/Replace MSAM Cards . 16 Install/Replace SIM Card (GSM models) . 18 Wireless Transactions. 20 Smart Card Reader Transactions . 20 Magnetic Card Reader Transactions . 20 Antenna (Some Wireless Models) . 21 Omni 3600 Base. 22 Unpack the Shipping Carton . 23 Omni 3600 Base Features . 23 Power Connection. 26 Omni 3600 Terminal Docking . 27 Spare Smart Battery Pack . 27 Omni 3600 Base Communications Ports . 28 C H AP T E R 2 Using the Terminal Keys Data Entry Modes. 32 The Keypad . 32 Function Key Descriptions . 33 Programmable Function (PF) Key Descriptions . 35 C H AP T E R 3 System Mode When to Use System Mode . 37 Local and Remote Operations . 37 Verifying Terminal Status . 38 Entering System Mode . 38 File Groups . 38 Passwords . 39 System Password . 39 File Group Passwords. 39 System Mode Menus . 40 System Mode Procedures. 41 Enter and Exit System Mode . 42 System Mode Menu 1 . 43 System Mode Menu 2 . 44 OMNI 3600 REFERENCE MANUAL 3 CONTENTS C H A P T E R 4 Performing Downloads C H A P T E R 5 File Authentication System Mode Menu 3 . 47 Edit Keyed Files . 52 System Mode Menu 4 . 52 System Mode Menu 5. 54 System Mode Menu 6 . 55 System Mode Menu 7 . 56 Downloads and Uploads. 57 Download Methods. 58 Download Tools . 58 Download Content . 59 Full and Partial Downloads. 60 Omni 3600 Download Differences . 62 Support for Multiple Applications . 62 Use of RAM and Flash Memory . 63 Redirection of Files During Application Downloads . 64 File Authentication Requirements . 69 Support for File Compression . 76 Effect of Downloads on Existing Files and Data. 76 Set Up the Download Environment . 77 Cable Connection for Direct Downloads . 78 Telephone Line Connection for Telephone Downloads . 80 Connections for Back-to-Back Downloads . 80 Direct Application Downloads. 80 Hardware Checklist. 80 Software Checklist . 80 Checklist for Effects on Files and Settings in the Receiving Terminal . 81 Direct Application Download Procedure . 81 Direct Operating System Downloads . 85 Hardware Checklist. 85 Software Checklist . 85 Checklist for Effects on Files and Settings in the Receiving Terminal . 86 Direct Operating System Download Procedure . 86 Download by Telephone. 88 Hardware Checklist. 88 Software Checklist . 88 Telephone Downloads Procedure. 89 Back-to-Back Application Downloads. 91 Hardware Checklist. 91 Software Checklist . 91 Checklist for Effects on Files and Settings in the Receiving Terminal . 92 Back-to-Back Application Download Procedure . 92 Introduction to File Authentication . 97 The VeriFone Certificate Authority . 97 Special Files Used in the File Authentication Process . 98 How File Authentication Works . 99 Planning for File Authentication . 104 Digital Certificates and the File Authentication Process . 107 File Authentication and the Omni 3600 File System . 111 4 OMNI 3600 REFERENCE MANUAL C H A P T E R 6 Troubleshooting and Service A P P E N D I X A System Messages A P P E N D I X B ASCII Table A P P E N D I X C Omni 3600 Base Unit Port Pinouts CONTENTS The FILESIGN.EXE File Signing Tool . 114 FILESIGN.EXE System Requirements. 114 Operating Modes for FILESIGN.EXE . 115 Command-Line Entries for FILESIGN.EXE . 116 Command-Line Mode Syntax Example . 117 FILESIGN.EXE Graphical Interface Mode . 117 Smart Card . 119 System Messages . 119 Use Remote Diagnostics to Identify Problems . 119 Troubleshooting . 119 Terminal Display Does Not Show Correct or Readable Information. 120 Smart Battery Will Not Charge . 120 Telephone Line Connection Does Not Work Properly . 120 Printer Does Not Work . 120 Serial Port Does Not Work . 121 Terminal Does Not Process Transactions . 121 Keypad Does Not Respond . 122 Cleaning and Care . 122 Base Contacts . 122 Smart Card Reader. 123 VeriFone Service and Support . 123 Return a Terminal, Omni 3600 Base, or Smart Battery . 123 Specifications . 125 Power Requirements . 125 Environmental. 125 Dimensions . 125 Weight. 125 Accessories and Documentation . 126 How to Order . 126 RS232 Port . 141 Telco Port . 141 Telset Port . 141 Barrel Connector Polarity . 142 G L O S S A R Y . 143 I ND E X . 149 OMNI 3600 REFERENCE MANUAL 5 CONTENTS 6 OMNI 3600 REFERENCE MANUAL CHAPTER 1 Omni 3600 Terminal and Omni 3600 Base Installation This chapter describes how to set up and install the Omni 3600 terminal and Omni 3600 base, including how to:

protect the terminal from adverse Environmental conditions, install and maintain the Smart Battery, establish communications connections through the Omni 3600 Base Communications Ports, and connect optional peripheral devices through the Omni 3600 base (see Peripheral Devices). NOTE This installation procedure is also available for end users in the Omni 3600 Installation Guide (VeriFone part number 22060), which can be downloaded at:

http://www.verifone.com/support/index.html Select a Location Omni 3600 Terminal This section provides tips on using and protecting your Omni 3600 terminal, and location recommendations for the Omni 3600 base. The Omni 3600 is a portable terminal for performing transactions remotely. Since it is a portable unit, location is not a factor however, follow the rules established in the Environment and Convenience sections. Omni 3600 Base A prime location for the Omni 3600 base is a counter or other flat surface that provides easy access to a power outlet and phone jack. Also, follow the rules established in the Environment and Convenience sections. Environment WARNING Do not leave this terminal in a non-climate-controlled vehicle. The Omni 3600 terminal is highly sensitive to temperature extremes. Subjecting the terminal to temperatures outside the stated operating range can void your warranty.

Do not use the Omni 3600 terminal or Omni 3600 base where there is moisture or high humidity, chemicals or oils, or excessive heat or dust.

Avoid locations near electrical appliances or other devices that emit excessive voltage fluctuations or electrical noise (for example, air conditioners, electric motors, neon signs, high-frequency or magnetic security devices, or computer equipment). OMNI 3600 REFERENCE MANUAL 7 OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Terminal

Never place the terminal in direct sunlight. CAUTION Do not use the Omni 3600 terminal or Omni 3600 base outdoors. They are for indoor use only, and are not waterproof or dustproof. Damage to the unit from exposure to sun, rain, or dust may void your warranty.

Keep the Omni 3600 terminal and Omni 3600 base away from anything that radiates heat, such as a stove or motor. WARNING Do not use the Omni 3600 terminal or Omni 3600 base near water, including a bathtub, wash bowl, kitchen sink or laundry tub, in a wet basement, or near a swimming pool. Avoid using these products during electrical storms. Convenience Omni 3600 Terminal Keep the Omni 3600 terminal with you to perform transactions. When plugging the Omni 3600 terminal into the power pack, ensure that the unit is placed close enough to a power outlet so that the power cable readily reaches the unit. For safety, do not string the power cable in a walkway or place across a walkway on the floor. Omni 3600 Base Locate the Omni 3600 base so that you can readily dock the Omni 3600 terminal on the cradle for recharging and downloading. Again, for safety, ensure that the power cable readily reaches the Omni 3600 base unit, so as not to trip or interfere in any way in a busy location. This section discusses the features of the Omni 3600 terminal, including

providing power to the Omni 3600 terminal, charging the smart battery, installing paper, installing MSAM cards, and completing magnetic card and smart card transactions. Omni 3600 Terminal Unpack the Shipping Carton Open the shipping carton and carefully inspect the contents for possible tampering or shipping damage (Figure 1). 8 OMNI 3600 REFERENCE MANUAL OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Terminal PAPER ROLL OMNI 3600 TERMINAL SMART BATTERY PACK POWER PACK POWER CABLE

(REGIONAL) MOD10 ADAPTOR

(OPTIONAL) Figure 1 1 Remove the following items:

Omni 3600 Terminal Shipping Carton Components

Omni 3600 terminal

Power pack and power cable (if present)

Roll of thermal printer paper

Battery pack

MOD10 adaptor (optional) 2 Remove all plastic wrap from the Omni 3600 terminal and components. 3 Remove the clear protective film from the display lens. WARNING Do not use a Omni 3600 terminal or Omni 3600 base that has been damaged or tampered with. OMNI 3600 REFERENCE MANUAL 9 OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Terminal Terminal Features Figure 2 illustrates the physical features of the Omni 3600 terminal. INTERNAL THERMAL PRINTER DISPLAY PROGRAMMABLE FUNCTION KEYS KEYPAD CANCEL/OFF KEY PRINTER DOOR RELEASE CARD SWIPE FUNCTION KEYS ALPHA KEY ENTER/ON KEY BACKSPACE KEY SMART CARD READER Figure 2 Notice the following features of the Omni 3600 terminal shown in Figure 2:

Omni 3600 Terminal Features

The display Four types of keys:

A 12-key, telephone-style keypad

Eight function keys: four function keys, labeled F1 to F4, right display; four unlabeled, programmable function (PF) keys above the keypad

Three keys (icons at left) under the keypad (left-to-right: CANCEL/OFF, BACKSPACE, ENTER/ON)

An ALPHA key center above the keypad (see ALPHA Key, page 33) The magnetic card swipe, above the display. The icon at left shows proper card orientation

Smart card reader, in the front of the unit. The icon at left shows proper card orientation The internal thermal printer and door release

A SAM (security access module) access door, underneath the battery The smart battery pack installed in back of unit (Figure 4)

(Figure 9). The Omni 3600 terminal contains three micromodule-sized SAM

(MSAM) cardholders to support multiple stored-value card programs or other merchant cards 10 OMNI 3600 REFERENCE MANUAL OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Terminal The Omni 3600 terminal is equipped with a tamper-evident label (on a screw hole on the case bottom). Power Port On the back of the Omni 3600 is one portthe power port. Use this port to connect the Omni 3600 to the power pack to recharge the battery through the unit Connect Power Pack To connect the Omni 3600 terminal to power:

1 Insert the round barrel connector (Figure 3) into the power port on the back of the terminal. 2 Insert the power cable into the power pack. 3 Plug the power pack into a wall outlet or surge protector. NOTE Install a power surge protector to protect against possible damage caused by lightning strikes and electrical surges. Figure 3 Connect Omni 3600 Terminal Power Pack WARNING Do not plug the power pack into an outdoor outlet. Smart Battery The Omni 3600 wireless terminal uses an Li-ion smart battery (see Accessories and Documentation for ordering information). The internal logic of the smart battery prevents both overcharging and undercharging (a fault condition in which the battery level goes well below the minimum acceptable charge and the battery becomes unusable). CAUTION Note that a new Li-ion batterys full performance is achieved only after two or three complete charge and discharge cycles. On initial use, allow the Omni 3600 smart battery to charge 4 hours, then fully discharge during normal operation, to ensure reliable battery operation. OMNI 3600 REFERENCE MANUAL 11 OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Terminal The following are features of the smart battery:

Two Li-ion cells

A fuel gauge module

monitors state of charge (voltage and current),

communicates with the terminal (charge parameters and alarms to indicate full discharge),

determines full charge capacity (on charge cycle and uninterrupted discharge cycle), and automatically shuts down when cell voltage is extremely low.

A safety circuit

prevents cell damage from overcharge/over-discharge, activates when the battery is left in an unused terminal for extended periods, and resets when battery voltage reaches a preset threshold during the charge cycle. NOTE Conserve battery power by turning the Omni 3600 terminal off when not in use. If the terminal is not to be used for several days, remove the battery from the terminal as it continues to discharge even when the terminal is turned off. Refer to Spare Smart Battery Pack for smart battery instructions for the Omni 3600 terminal on the Omni 3600 base. NOTE The smart battery pack must be installed and holding a minimum of a 1% charge to operate the Omni 3600 terminal. Smart Battery Installation The smart battery installs in a slot on the back of the terminal, as shown in Figure 4. The locking tab clicks when the battery is in place. The slot is keyed, so that there is only one way to insert the battery. Figure 4 Install the Smart Battery 12 OMNI 3600 REFERENCE MANUAL OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Terminal Smart Battery Removal To remove the smart battery, press the locking tab at the top of the battery and pull the smart battery from its slot. Smart Battery Charging On initial use, the smart battery must be fully charged and fully discharged through normal operation. After unpacking your Omni 3600 terminal, install the battery and connect the power pack to the unit for 4 hours. Disconnect the power pack and allow your Omni 3600 terminal to remain on until the smart battery completely discharges. Reconnect the power pack to the unit and allow the smart battery to recharge a maximum of 4 hours. It is also recommended that the smart battery receive a periodic full discharge. To ensure a full discharge, use the unit until the battery is fully drained. To determine the charge state of the battery, push the test button icon (shown in Figure 5) on the bottom of the battery. The bar LED status indicators on the battery each indicate 25% of the charge state. When the battery charge state reaches 10%, the E LED (Figure 5) blinks, indicating a low-charge state. The battery charge state displays at the bottom of the first copyright screen when the terminal is turned on. NOTE Conserve battery power by turning the Omni 3600 terminal off when not in use. If the terminal is not to be used for several days, remove the battery from the terminal as it continues to discharge even when the terminal is turned off. The smart battery has a safety circuit to protect the Li-ion cells from overcharging and over-discharging. If the battery is over-discharged, the safety circuit shuts down the battery and none of the indicator LEDs (see Figure 5) on the battery pack blink. The battery must then be recharged to restore operation. NOTE The Omni 3600 terminal automatically shuts off when the smart battery reaches the critically low charge state. If this occurs, the smart battery must recharge a minimum of 1/2 hour before it can power the terminal. It make take several recharge attempts to reset the safety circuit when charging a smart battery that has reached a critically low charge state. If the Omni 3600 terminal is already running an application (for example, SoftPay), a battery status indicator may appear on the display. BATTERY CHARGE STATE TEST BUTTON AND STATUS INDICATOR LEDS Figure 5 Smart Battery Charge Indicator LEDs and Test Button OMNI 3600 REFERENCE MANUAL 13 OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Terminal NOTE It is recommended that you keep a spare, charged smart battery available. Smart Battery Life To ensure that you get the longest possible performance from the smart battery, it must be allowed to fully discharge periodically. The smart battery can be charged and discharged hundreds of times, but will eventually wear out. When operating times are noticeably shorter than usual, it is time to buy a new battery (see Accessories and Documentation for ordering information). WARNING Do not dispose of batteries in a fire. Li-ion batteries must be recycled or disposed of properly. Do not dispose of Li-ion batteries in municipal waste sites. Turn On/Off the Omni 3600 Terminal Paper Installation When the smart battery completes its initial charge, turn on the Omni 3600 terminal by pressing the green ENTER/ON key (icon at left) for approximately 3 sec. The display screen lights and displays the initial VeriFone copyright screen. If an application is loaded in the terminal, it starts after the initial VeriFone copyright screen and displays a unique (copyright) screen. If no application is loaded in the terminal, DOWNLOAD NEEDED appears on screen after the initial VeriFone copyright screen. Turn off the Omni 3600 terminal by pressing the red CANCEL/OFF key (icon at left) continuously until the cancel tone is heard (approximately 4 sec.). First a series of beeps is heard, then the cancel tone. The unit then shuts off. The internal thermal printer uses a roll of single-ply, thermal-sensitive paper 58 millimeters (2.25 inches) wide and 25 meters (82 feet) long. A pink out-of-paper indicator line appears on the edge of the paper approximately 18 inches before the end of the roll. After this line appears, there is enough paper remaining on the roll to conclude at least one transaction. WARNING Poor-quality paper may jam the printer. Order high-quality paper from VeriFone;

refer to the ordering process listed in Accessories and Documentation. CAUTION Store thermal paper in a dry, dark, cool place. Handle thermal paper carefully;

impact, friction, high temperatures, humidity, light, and oils affect the color and storage characteristics. To install the paper roll in the internal thermal printer:

1 Lift paper roll cover tab to unlock the printer door (Figure 6). 14 OMNI 3600 REFERENCE MANUAL OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Terminal 2 Rotate the printer door up and back. Note that the door is hinged; it is not necessary to remove it from the unit. Figure 6 3 Loosen the glued leading edge of the paper from the roll. Open the Printer Cover 4 Hold the paper roll so paper feeds from the bottom (Figure 7) and pull approximately two inches of paper free of the roll. 5 Drop the paper roll into the printer tray, allowing the free paper to extend outside the printer door (Figure 7). Figure 7 6 Close the cover by gently pressing directly on the paper roll cover tab until it Load Paper clicks shut. Allow a small amount of paper to extend outside the cover, as shown in Figure 8. Figure 8 Close the Printer Cover OMNI 3600 REFERENCE MANUAL 15

 

 

OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Terminal NOTE To prevent damage to the print roller on the paper roll cover, always close the cover by gently pressing down on the paper roll cover tab. Printer Test To ensure the printer is operating correctly:

1 Turn on the terminal by pressing the green enter key (see Figure 2, page 10). 2 Enter system mode by pressing F2+F4 at the initial copyright screen, and entering the system mode password (see Passwords). 3 Toggle through the SYS MODE MENU screens, using the down arrow key until you reach SYS MODE MENU 6. 4 Press F4 to enter the Printer ID screen. 5 Press F3, Test, to start the printer self-test. The test printout, with printer information and repeating character strings, is approximately 38 cm (15 in.) long. Install/Replace MSAM Cards When you first receive your Omni 3600 terminal, you may need to install a merchant smart card or one or more micromodule-sized security account manager (MSAM) cards, or you may need to replace old cards. Often, these small cards arrive on a larger, credit card-style plastic card, from which they must be removed. The following procedure describes MSAM card installation. CAUTION Observe standard precautions for handling electrostatically sensitive devices. Electrostatic discharges can damage this equipment. An anti-static wrist strap grounded to a metal surface is recommended. 1 Remove the battery (see Smart Battery) 2 Open the MSAM door located beneath the battery (Figure 9):

a Push down and back on the raised arrow on the door. b Lift up on the raised arrow with the tip of your index finger. c Open the door until it is in the upright position, resting against the end of the terminal. 16 OMNI 3600 REFERENCE MANUAL OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Terminal Figure 9 Open the MSAM Access Door The three MSAM cardholders are now accessible. Each cardholder consists of a hinged tilt-up cover attached to a connector base (Figure 10). Figure 10 3 Access the MSAM cardholders (reference Figure 10):

MSAM Card Installation a Unlock the cardholder: Slide the lock plate to the unlocked position, in the OPEN direction (Figure 11). Figure 11 MSAM Cardholder Lock Plate Detail OMNI 3600 REFERENCE MANUAL 17 OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Terminal b Open the cardholder by pivoting the cover on its hinge away from the connector base (Figure 12). Figure 12 4 Remove any previously installed MSAM card by sliding the card from the Insert MSAM Card into Cardholder cover. 5 Install an MSAM card by aligning the card and carefully sliding it within the guides on the cover until fully inserted. NOTE The cardholder has a set of contacts and a notch on one corner to ensure the MSAM card is positioned correctly when the cover is closed. The MSAM card has a notch on one corner to ensure it is correctly positioned in the cardholder. Before inserting the MSAM card, position it as shown in Figure 12. 6 Close the cover (Figure 12). 7 Lock each MSAM cardholder by sliding its locking plate towards the LOCK arrow until the plate stops (Figure 11). CAUTION To avoid damage to the MSAM cardholders, ensure each cardholder is locked before closing the MSAM door. 8 Close the MSAM door. 9 Replace the smart battery. Install/Replace SIM Card (GSM models) The SIM (Subscriber Identity Module) card is a smart card inserted in the Omni 3600 GSM terminal that contains your GSM radio account information. Use the following procedure to replace or install a SIM card. 18 OMNI 3600 REFERENCE MANUAL OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Terminal 1 Remove screw from SIM card access door on back of Omni 3600 terminal

(Figure 13). Figure 13 2 Remove the SIM card access door (Figure 14):

Remove SIM Door Screw Figure 14 3 Open the SIM card holder and slide the SIM card supplied by your provider Slide Off SIM Card Access Door into the cardholder (Figure 15). NOTE Do not lose the SIM card dust cover or retaining screw. Figure 15 Insert SIM Card into Cardholder NOTE The SIM cardholder has a notch on one corner to ensure the SIM card is positioned correctly. The SIM card has a notch on one corner for easy orientation in the cardholder. Before inserting the SIM card, position it as shown in Figure 15, with the cards gold contacts facing down. 4 Replace the SIM card access door and screw. OMNI 3600 REFERENCE MANUAL 19 OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Terminal Wireless Transactions To conduct a wireless transaction:

Ensure the terminal is in an optimal position for transmitting.

Follow the on-screen instructions provided with your application. Smart Card Reader Transactions To conduct a smart card transaction:

1 Position the smart card with the contacts up and insert it into the smart card reader slot in a smooth, continuous motion until it seats firmly (Figure 16). Leave the smart card in the card reader until the transaction is complete. Premature removal voids the transaction. Figure 16 2 Remove the card when the display indicates the transaction is complete. Using the Primary Smart Card Reader Magnetic Card Reader Transactions To conduct a credit/debit card transaction:

1 Position the card with the magnetic stripe facing down and towards the printer. 2 Swipe it through the reader from left-to-right, as shown in Figure 17. Figure 17 Using the Magnetic Card Reader 20 OMNI 3600 REFERENCE MANUAL OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Terminal Antenna (Some Wireless Models) For some Omni 3600 terminals to establish a wireless connection, an external antenna is provided. This connection allows communication with your service provider to upload transaction data from the terminal and download system upgrades to the terminal. Radio service is activated by your service provider. NOTE Most Omni 3600 terminals have an internal antenna and this section can be ignored. Only use the antenna designed for your unit. Failure to use the proper antenna results in the inability to establish a wireless connection. CAUTION Never hold the unit by the antenna; doing so may break the connection and void your warranty. Data transfers can also be performed through the Omni 3600 base (see Omni 3600 Base Communications Ports). This section only discusses Omni 3600 terminals with external antenna. Installation The Omni 3600 should arrive from manufacture with the antenna attached. If unattached, use the following procedure to install the antenna:

1 Locate the antenna port on the side of the Omni 3600 terminal. 2 Align the respective notch inside the antenna to the key in the terminal

(Figure 18). 3 Push gently on the center of the base of the antenna until it locks in position. Figure 18 Antenna Installation Orientation To establish good wireless communication (uplink), it is important that the antenna always be vertically aligned with respect to ground and sky (Figure 19). For example, if standing and holding the terminal horizontally, position the antenna at an approximately 90 angle to the unit (that is, pointing up from the printer). This should point the antenna directly at the sky. OMNI 3600 REFERENCE MANUAL 21 OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Base If the unit is on a flat surface (for example, a table top) or docked in the Omni 3600 base, position the antenna so that it points directly at the sky. Soft detentes are felt and clicks heard when positioning the antenna. These detentes maintain antenna positions of 60, 90, and 180. Correct Antenna Position for Uplink Figure 19 If an application (for example, SoftPay) is installed in your Omni 3600 unit, a signal strength indicator may appear on the display. Replace the Antenna If your Omni 3600 terminal has difficulties completing wireless transactions, you may have to replace the antenna. Use the following procedure to replace the antenna:

1 Remove the existing antenna from the Omni 3600 terminal:

a Rotate the antenna to align with the base of the unit, pointing away from the back. b Grasp the base of the antenna, close to the body of the terminal. c Pull gently out until the antenna unsnaps from the antenna port. 2 Align the respective notch inside the new antenna to the key in the antenna port on the terminal (Figure 18). 3 Push gently on the center of the base of the newly installed antenna until it locks in position. This section discusses the features of the Omni 3600 base, including

providing power to the Omni 3600 base, docking the Omni 3600 terminal, charging the smart battery in a docked terminal, charging a spare smart battery, establishing communications, and connecting peripheral devices. The Omni 3600 base does not support PIN pad connections. Omni 3600 Base 22 OMNI 3600 REFERENCE MANUAL OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Base Unpack the Shipping Carton Refer to Figure 20 and the following procedure while unpacking the Omni 3600 base shipping carton. OPTIONAL ACCESSORIES OMNI 3600 BASE TELCO CABLE

(OPTIONAL) Figure 20 1 Remove the following items:

Omni 3600 Base Shipping Carton Contents

Omni 3600 base

Telco cable (optional) NOTE The power pack and power cable, spare battery packs, and Telco cable are available separately. See Accessories and Documentation for ordering information. 2 Remove all plastic wrap from the Omni 3600 base and other components. Omni 3600 Base Features This section discusses the features of the Omni 3600 base. SPARE BATTERY DOCK TERMINAL DOCKING CONTACTS TERMINAL DOCKING CRADLE STATUS LEDS Figure 21 Omni 3600 Base Features: Top CAUTION Avoid touching the contacts in the raised area in the center of the Omni 3600 base. Finger oils tarnish contacts, causing bad connections. If the battery charge state or terminal power LEDs do not light when the terminal is docked, or there is a high occurrence of bad or incomplete data transfers, clean the contacts. See Maintenance for more information. OMNI 3600 REFERENCE MANUAL 23 OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Base TERMINAL DOCKING CRADLE TELSET PORT TELCO PORT RS-232 PORT POWER PORT Figure 22 The Omni 3600 base Omni 3600 Base Features: Back (Telco models)

recharges the smart battery within a docked Omni 3600 terminal, charges a spare smart battery pack placed in the spare battery dock, establishes communications to a host through a 14.4 Kbps modem (Telco port), and connects to optional peripherals through the serial (RS-232) port (see Peripheral Devices). The following are the physical features of the Omni 3600 base (Figure 21 and Figure 22):

Three status LEDs (light emitting diodes) viewed left-to-right

Terminal power LED:

Steady green indicates the battery in the terminal is fully charged or the terminal is docked, but has no battery.

Flashing amber indicates the battery in the terminal is receiving a test charge and is in the precharge statethe Omni 3600 base circuitry is determining the charge state of the battery in terminal.

Steady amber indicates the battery in the terminal is recharging.

Battery charge state LED:

Steady green indicates the spare battery docked in the Omni 3600 base is fully charged or is no longer charging.

Flashing amber indicates the spare battery is receiving a test charge and is in the precharge statethe Omni 3600 base circuitry is determining the charge state of the spare battery.

Steady amber indicates the battery in the spare battery dock is recharging. 24 OMNI 3600 REFERENCE MANUAL OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Base

Omni 3600 base power LED:

Steady green indicates the Omni 3600 base is connected to the power adapter.

Not lit indicates the Omni 3600 base is not connected to the power pack, the power pack is not connected to the wall outlet, or the power is out. Table 1 illustrates different LED states. Table 1 Omni 3600 Base LED Status LED Terminal Power Spare Battery Omni 3600 Base Power Battery State Fully charged battery in Omni 3600 terminal and spare battery in Omni 3600 base Pre-charge state Charging Omni 3600 base has power

Docking cradle: For Omni 3600 terminal (Figure 21) smart battery recharging and data transfers. NOTE The Omni 3600 terminal will not automatically turn off or sleep when docked; it must be turned off manually (see Turn On/Off the Omni 3600 Terminal).

Spare battery docking station and optional spare battery: The recessed area in the top-rear of the Omni 3600 base is the dock to charge and store a smart battery. The spare battery LED does not light if no spare battery is present.

Power port: The round port on back of Omni 3600 base (icon at left) connects the Omni 3600 base to the power pack.

Communications ports: The ports on the back of the Omni 3600 base allow telephone or LAN line connectivity and peripheral device support. OMNI 3600 REFERENCE MANUAL 25 OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Base Power Connection The Omni 3600 base unit must be plugged in to a power outlet to

recharge a smart battery in a docked terminal, charge spare smart batteries, communicate with peripheral devices, and establish Telco host connections. WARNING Do not plug the power pack into an outdoor outlet. Figure 23 Power Pack Connection (Docked Terminal) NOTE It is recommended that the power pack be plugged into a power surge protector to protect against possible damage caused by lightning strikes and electrical surges. To connect the Omni 3600 base to power (Figure 23):

1 Insert the round barrel connector into the power port (icon at left) on the far right of the Omni 3600 base. 2 Insert the power cable into the power pack. 3 Plug the power cable into a wall outlet or surge protector. When the Omni 3600 base is powered, the far-right LED (icon at left) lights steady green. 26 OMNI 3600 REFERENCE MANUAL OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Base Omni 3600 Terminal Docking Place the Omni 3600 terminal in the docking cradle (Figure 23) to recharge the terminal smart battery, establish communications connections for data transfers, and communicate with peripheral devices. NOTE The Omni 3600 terminal will not turn off or enter sleep mode while docked on the Omni 3600 base. This ensures that the unit is not placed into sleep mode during data transfers. The unit must be turned off manually when docked on the Omni 3600 base. See Turn On/Off the Omni 3600 Terminal. Spare Smart Battery Pack Spare smart battery packs for the Omni 3600 terminal can be ordered from VeriFone. See Accessories and Documentation for ordering information. To charge a smart battery in the Omni 3600 base, place the smart battery into the Omni 3600 base spare smart battery dock as shown in Figure 24. The smart battery dock is keyed so that the smart battery can only be inserted in one way. Figure 24 Spare Smart Battery Docking NOTE Allow the spare battery to remain in the Omni 3600 base unit for a minimum of 2 hours, maximum of 4 hours to ensure the battery receives a full charge. Note that a new Li-ion batterys full performance is achieved only after two or three complete charge and discharge cycles. Keep a spare smart battery charging in the Omni 3600 base battery dock to ensure that a fully charged battery is always available. CAUTION Conserve battery power by turning the Omni 3600 terminal off when not in use. If the terminal is not to be used for several days, remove the battery from the terminal as it continues to discharge even when the terminal is turned off. If the Omni 3600 base unit is not plugged in, remove the smart battery from the dock to avoid the smart battery discharging in the Omni 3600 base unit. On initial use, allow the Omni 3600 smart battery to charge a maximum of 4 hours and fully discharge during normal operation to ensure reliable battery operation. See Smart Battery for charge/discharge procedures. OMNI 3600 REFERENCE MANUAL 27 OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Base WARNING Do not dispose of batteries in a fire. Li-ion batteries must be recycled or disposed of properly. Do not dispose of Li-ion batteries in municipal waste sites. Omni 3600 Base Communications Ports The communications ports are located on the back of the Omni 3600 base (see Figure 25). When the Omni 3600 terminal is docked in the Omni 3600 base, a communication port in the terminal is opened, and data can transfer from the Omni 3600 terminal back and forth through the Omni 3600 base over the modem connection to and from your service provider or merchant contact. NOTE The Omni 3600 base must be plugged into power to establish communications connections. TELSET PORT TELCO PORT RS-232 PORT POWER PORT Figure 25 Omni 3600 Base Connection Ports WARNING Do not remove the Omni 3600 terminal from the Omni 3600 base during data transfers. This terminates the connection and data loss may result. Telephone Line Ports There are two RJ11-type modular phone jacks (Figure 25) to connect the Omni 3600 base to a telephone line:

The first port is identified by a telephone-shaped Telset icon shown at left. Use this port to connect a telephone to the terminal (pass-through connection) The second port is identified by the Telco icon shown at left. Use this port to directly connect the Omni 3600 series terminal to a telephone wall jack Telephone Line Connections To make a direct connection, connect a telephone cord from the Telco port on the Omni 3600 base directly to a telephone wall jack (Figure 26). Do not string the telephone cord across a walkway or place it so as to interfere in high-traffic areas. With a direct connection, the phone line is dedicated to the terminal. 28 OMNI 3600 REFERENCE MANUAL OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Base Direct Connection Figure 26 Pass-through connection Run a telephone cord from the Telco port on the Omni 3600 base to the RJ11 jack on a standard telephone (Figure 27). Do not string the telephone cord across a walkway or place it so as to interfere in high-

traffic areas. With a pass-through connection, the phone line is busy during downloads. Figure 27 Pass-through Connection Peripheral Devices The Omni 3600 base supports a line of VeriFone peripheral devices designed to use with point-of-sale terminals. Use the RS-232 port on the back panel of the Omni 3600 base to connect these optional devices. The following sections discuss the optional devices supported by the Omni 3600. Other optional devices may be supported. For more information, please contact your VeriFone distributor. Optional Peripheral Device Port Right of the RJ11 ports is a RJ45-type modular jack (serial port), labeled RS232:

The RS232 serial port (icon shown at left) connects a VeriFone CR 600 check reader or other peripheral device to the Omni 3600 base The Omni 3600 base does not support external PIN pad devices. OMNI 3600 REFERENCE MANUAL 29 OMNI 3600 TERMINAL AND OMNI 3600 BASE INSTALLATION Omni 3600 Base Check Readers Supported The Omni 3600 base supports two VeriFone check readers: CR 600 and CR 1000i. Contact your VeriFone representative or visit the online store at www.verifone.com for information on these devices. Figure 28 provides an example of a peripheral connection. Figure 28 Example Peripheral Connections External Printers Supported Although the Omni 3600 has an internal thermal printer (see Paper Installation), it may be convenient to print larger print runs (for example, daily or weekly reports) to an external printer. The Omni 3600 base supports three VeriFone external printers: P250, P350, and P900. Contact your VeriFone representative or visit the online store at www.verifone.com for information on these devices. External printer connections are through the same port as check readers (see Figure 28). 30 OMNI 3600 REFERENCE MANUAL

 

 

Using the Terminal Keys CHAPTER 2 Before proceeding to other tasks, familiarize yourself with the operational features of the Omni 3600 terminal keypad to enter data (see Figure 29). This chapter describes how to use the keypad, including discussions on:

the12-key Telco-style keypad, the three color-coded keys below the keypad, the ALPHA key above the keypad, the four ATM-style function keys (F1, F2, F3, and F4) to the right of the display

(Figure 29), and the four programmable function (PF) keys directly above the keypad. Using these keys you can perform all data-entry tasks described in this manual. Where a specific key is mentioned, it appears within square brackets (for example, the ALPHA key). The function keys allow you to navigate though system mode menus and select specific operations. NOTE The PF and ATM-style keys can also be assigned application-specific functions in addition to those assigned to system mode operations. These functions are not discussed in this manual. Figure 29 Front Panel Key Arrangement OMNI 3600 REFERENCE MANUAL 31 USING THE TERMINAL KEYS Data Entry Modes Data Entry Modes Before you can use the keys on the front panel to enter ASCII characters, the Omni 3600 must be in a mode that accepts keyed data entry. There are two terminal operating modes, each enables you to press keys to enter data under specific circumstances:

Normal mode: This is the terminal operating mode where an application program is present in SRAM and currently running.

System mode: This is a special, password-controlled terminal operating mode for performing a variety of test and configuration procedures that cannot be performed when an application is running. NOTE If you enter system mode while a terminal application is running in normal mode, system mode preempts the application and takes control of the display and keyboard. The preempted application continues to run in the background, but does not accept user input. The only way to exit system mode is to restart the terminal. For this reason, once you enter system mode, you cannot return to the application in the same session. If you turn on an Omni 3600 terminal that does not have an application stored in SRAM, the system prompt DOWNLOAD NEEDED appears. You can enter system mode by simultaneously pressing F2 and F4, and then entering the password. Once in system mode, you can configure the terminal as required and perform the necessary download. If you turn on an Omni 3600 terminal with an application stored in SRAM, the application executes and the terminal automatically enters normal mode. The application then controls how terminal keysincluding the programmable function

(PF) keys and the ATM-style keysprocess transactions and when you can use specific keys to type characters or respond to prompts. NOTE If an application is in terminal memory, the default system password into system mode may have been changed. If so, you must press a special key combination and then type in the required system password to enter system mode. The behavior of key entries depends on the specific active system mode menu. The Keypad The keypad is a 13-key arrangement, consisting of a 12-key Telco-style keypad and the ALPHA key (Figure 29). NOTE The system mode functions described in the next section require that you enter numbers, letters, or symbols using the keypad. Using the keypad, you can enter up to 50 ASCII characters, including the letters AZ, the numerals 09, and the following 16 special characters: (*), (,), (), (), (-),

(.), (#), (%), (:), (!), (+), (@), (=), (&), (space), and (/). 32 OMNI 3600 REFERENCE MANUAL USING THE TERMINAL KEYS The Keypad Function Key Descriptions The terminals operating mode and context determine the specific action performed when you press one of the following function keys. The following descriptions are provided solely to acquaint you with some general characteristics of these function keys before presenting more detailed system mode procedure descriptions. Cancel Key Pressing the cancel key in normal modewhen the terminals application is loaded and runningusually has the same effect as pressing the Esc (escape) key on a PC. That is, it terminates the current function or operation. In system mode, use cancel to perform a variety of functions. The most common use of cancel in system mode is to exit a system mode submenu and return to the main system mode menu. The specific effect of pressing the cancel key depends on the currently active system mode menu. Backspace Key In normal mode, the backspace key is commonly used to delete a number, letter, or symbol on the terminals display screen. Press backspace one time to delete the last character typed on a line. To delete additional characters, moving from right to left, press backspace once for each character or hold down backspace to delete all characters on a line. In system mode, the specific effect of pressing backspace depends on the currently active system mode menu. ALPHA Key In normal mode, the ALPHA key enables you to enter one of the two or more characters or symbols assigned to individual keys on the 12-key Telco-style keypad. Use the ALPHA to enter up to 50 different ASCII characters through the following procedure:

1 Press the key on the 12-key keypad that shows the letter or symbol you want

(for example, use 2 to type 2, A, B, or C). The number (19 or 0) or the symbol

(* or #) you pressed now displays. 2 Press ALPHA once to display the first letter. Continuing our example, 2 ALPHA displays the letter A. 3 Continue pressing ALPHA as many times as required to display the desired character. For example, press 2 to display the number 2; press ALPHA once to display the letter A, twice to display B, or three times to display C. If you press ALPHA one more time, you cycle back to the number 2. NOTE If you firmly press and hold down one of the keys on the 12-key keypad without using ALPHA, the same character repeats until you stop pressing the key. For example, if you press 2 and hold it down, 2222222... displays OMNI 3600 REFERENCE MANUAL 33 USING THE TERMINAL KEYS The Keypad If two or more characters display on the Omni 3600 screen, pressing ALPHA changes the last character on the line to the next letter, number, or symbol in the key sequence. For example:

Current display: A5C*2 ALPHA ALPHA ALPHA ALPHA A5C*A A5C*B A5C*C A5C*2 Table 2 provides additional examples of how to use the ALPHA key to select ASCII characters from the 12-key Telco-style keypad. Table 2 Example ALPHA Key Entries Desired Character Press Keys 2 A S

Space Comma (,) Plus sign (+) 2 2 ALPHA 7 ALPHA ALPHA ALPHA

# ALPHA 0 ALPHA ALPHA

* ALPHA 0 ALPHA ALPHA ALPHA Table 3 lists all the ASCII characters you can type using the ALPHA key and the Telco keypad. Table 3 Using ALPHA and the 12-Key Keypad Key to Press Without Pressing ALPHA Press ALPHA One Time Press ALPHA Two Times Press ALPHA Three Times 1 2 3 4 5 6 7 8 9 0

Q A D G J M P T W

, 1 QZ. 2 ABC 3 DEF 4 GHI 5 JKL 6 MNO 7 PRS 8 TUV 9 WXY 0 -SP

#a a. The # key also supports four additional characters: (=), (&), (/), and (%). To enter =, press #

once, then ALPHA four times. To enter &, press # once, then ALPHA five times. To enter /, press # once, then ALPHA six times. To enter %, press # once, then ALPHA seven times. Z B E H K N R U X

[space]

. C F I L O S V Y

34 OMNI 3600 REFERENCE MANUAL USING THE TERMINAL KEYS Programmable Function (PF) Key Descriptions NOTE In system mode, use ALPHA to key in the default system password, to enter a new system password, and for entering alpha characters. Enter Key In normal mode, the enter key is generally used the same as the enter key on a PC, that is, to end a procedure, confirm a value or entry, answer Yes to a query, or select a displayed option. In system mode, press the enter key to begin a selected procedure, step forwards or backwards in a procedure, and confirm data entries. The specific effect of the enter key depends on the currently active system mode menu. Programmable Function (PF) Key Descriptions The row of four PF keys directly above the keypad (Figure 29) from left-to-right are referred to as PF1, PF2, PF3, and PF4. These keys can be assigned application-specific functions. Because such functions are often unique and can vary greatly between applications, they are not discussed in this manual. The PF keys are also use to toggle through system mode menus. These keys are functioning when arrows appear in the display screen above the associated key, indicating the keys can be used as follows:

PF1

PF2

PF3

PF4 Move to the previous menu or screen Move to the next menu or screen Scroll left Scroll right OMNI 3600 REFERENCE MANUAL 35 USING THE TERMINAL KEYS Programmable Function (PF) Key Descriptions 36 OMNI 3600 REFERENCE MANUAL System Mode When to Use System Mode Local and Remote Operations CHAPTER 3 This chapter describes a category of terminal functions called system mode operations, including discussions on:

system mode entry, initiating local and remote operations, passwords, file groups, and system mode menus. System mode is used exclusively by those responsible for configuring, deploying, and managing Omni 3600 terminal installations in the field. Use system mode functions to perform different subsets of related tasks:

Application programmers: To configure a development terminal, download versions of the Omni 3600 application program you are developing, and test and debug the application until validated and ready to download to other terminals.

Deployers of Omni 3600 terminals to end-user sites: To perform the specific tasks required to deploy a new Omni 3600 terminal in the field, including configuring the terminal, downloading application software, and testing the terminal prior to deployment.

Terminal administrators or site managers: To change passwords, perform routine tests and terminal maintenance, and configure terminals for remote diagnostics and downloads by telephone. To perform the subset of tasks that corresponds to your job, select the appropriate system mode menu(s) and execute the corresponding procedure(s). The system mode operations available on an Omni 3600 terminal can be divided into the following two categories or types:

Local operations: Address a standalone terminal and do not require communication or data transfers between the terminal and another terminal or computer. Perform local system mode operations to configure, test, and display information about the terminal.

Remote operations: Require communication between the terminal and a host computer (or another terminal) over a telephone line or a cable connection. Perform remote system mode operations to download application OMNI 3600 REFERENCE MANUAL 37 SYSTEM MODE Verifying Terminal Status software to the terminal, upload software from one terminal to another, and perform diagnostics over a telephone line. This chapter contains descriptions on how to perform local system mode operations. For information performing remote operations, such as downloads, refer to Chapter 4. Verifying Terminal Status The Omni 3600 terminal you are working with may or may not have an application program running on it. After you have set up the terminal (Chapter 1) and the terminal is turned on, use the following guidelines to verify terminal status regarding software and current operating mode:

If no application program is loaded into terminal RAM or flash, the message DOWNLOAD NEEDED appears on the display. From this point, press F2 and F4 to enter system mode and perform the required download. If an application program is loaded into terminal RAM or flash, an application-

specific application prompt appears. The application is running and the terminal is in normal mode. If all installation steps are complete, the terminal can process transactions. Entering System Mode To prevent the unauthorized use of system mode menus, the Omni 3600 terminal firmware requires a system password each time you enter system mode. The default, factory set system password is Z66831. Use the following key sequence to enter this password:

1 ALPHA ALPHA 6 6 8 3 1 []

After entering the correct password, the terminal enters system mode and displays the first system mode main menu, SYS MODE MENU 1. You can now toggle through all seven system mode main menus. NOTE It is recommended to enter system mode only on system startup or terminal restart. If you enter system mode while an application is running, system mode suspends the application and takes control of the display and keyboard. The application idles in the background, but no longer accepts user inputs. You cannot return to the application during that session, only after a restart. In addition, an application running in the background may deny access to certain system mode functions. File Groups The Omni 3600 operating system implements a file system in volatile, battery-

backed RAM and non-volatile flash memory. Files are assigned to one of 15 groups for access control. Groups are similar to directories on a computer in that different applications can be stored in separate file groups, just like different computer applications can be stored in separate directories. Groups are referred to as Group n or GIDn throughout this manual. Each group is protected by a separate password, and each has a separates CONFIG.SYS file. The following rules apply to the Omni 3600 file group system:

38 OMNI 3600 REFERENCE MANUAL SYSTEM MODE Passwords The primary application must be downloaded into Group 1.

On terminal power up and after a restart, the terminal defaults to Group 1 as the controlling group.

Group 1 applications have access to files stored in all groups. Other applications can reside in Groups 2 through 14.

Applications in a group other than Group 1 have access only to themselves and files stored in Group 15.

Group 15 is globally accessible, making it an ideal location for files shared by multiple applications, such as shared libraries.

File Groups 1 through 15 are empty until they are filled through a download to the Omni 3600 terminal. For more information on managing file groups, refer to the Verix Programmers Manual (VeriFone P/N 19733). Passwords CAUTION If you change a password and then forget it, there is no password recovery method. Without the password, you are unable to access system mode operations and may be prevented from requesting a download, performing remote diagnostics, or changing any of the information already stored in memory. The terminal can, however, continue to process transactions in normal mode. If you forget or lose the system password to your terminal, please contact your local VeriFone representative for assistance. System Password In SYS MODE MENU 3, you can select a procedure to change the default password to a unique and more secure password. Once you set a new system password, be sure to secure a copy of the new password. A valid system password may consist of one to ten alphanumeric characters. You can change the system password at any time, provided you know what the current password is. When you key in the system password to enter system mode, an asterisk (*) appears on the display for each character you type. These asterisks prevent your password from being seen by an unauthorized person. You can use the ALPHA key to change the characters or symbols you enter; this does not cause additional asterisks to appear. NOTE Some application program downloads automatically reset the system password. If your system password no longer works, check if a download has changed your password. File Group Passwords From manufacture, each file group uses the default password Z66831, entered as:

OMNI 3600 REFERENCE MANUAL 39 SYSTEM MODE System Mode Menus 1 ALPHA ALPHA 6 6 8 3 1, and press []

NOTE This default password is the same as the password for system mode entry, which is set in the CONFIG.SYS entry *SMPW. System Mode Menus The seven main system mode menus are listed in Table 4. Table 4 System Mode Menus SYS MODE MENU 1 SYS MODE MENU 2 CONTRAST F2 CLOCK F3 RESTART F4 DOWNLOAD F2 RAM FILES F3 FLASH FILES F4 SYS MODE MENU 3 SYS MODE MENU 4 CONFIG INFO F2 EDIT F3 PASSWORDS F4 REMOTE DIAGS F2 ERROR LOG F3 DEBUGGER F4 SYS MODE MENU 5 SYS MODE MENU 6 SCREEN DIAG F2 KEYBOARD DIAG F3 MAG CARD DIAG F4 IPP DIAG F2 IPP KEYLOAD F3 PRINTER DIAG F4 SYS MODE MENU 7 BATTERY STATUS F2 On successful entry of the system password, SYS MODE MENU 1 appears. To return to a previous menu, press the PF1 key (below the up arrow). To go to the next menu, press the PF2 key (below the down arrow). To return to the main system mode menu and cancel any changes, press the cancel key. Each menu has items to select; sometimes these items contain submenus or a series of prompts. When prompted to enter alphabetic or special characters, use the procedure described in Chapter 2. When performing downloads or operations that change or clear files, the password for each file group is required. The password is only required once per session per file group. 40 OMNI 3600 REFERENCE MANUAL SYSTEM MODE System Mode Menus System Mode Procedures The procedures in this section explain how to use each of the system mode menus listed in Table 4. Each procedure description starts at a main system mode menu. Each procedure takes you step-by-step through a complete system mode operation in the following sequence:

1 When a main system mode menu appears, select an operation by pressing the appropriate key. 2 Complete the operation. 3 Return to the main system mode menu. NOTE Before entering system mode and selecting the function(s) to perform, please verify that you have completely installed the Omni 3600 as described in Chapter 1, that the terminal is connected to a power source, and that the terminal is turned on. Procedure descriptions are arranged in the following tabular format:

Display Action Submenu The Display column indicates what appears on the terminal display at each step of the procedure. Please note the following conventions used in this column:

If a prompt or message appears on the screen exactly as it is described, it is shown in Arial font and in ALL CAPS. For example, DOWNLOAD NEEDED. If text is enclosed in parentheses, the actual text or message may vary depending on the terminal version you have. For example, (Application Prompt), in which the normal font is used, and text is typed in initial caps. The Action column provides a procedure description that:

Describes the current step and context of the procedure.

Indicates the entries to perform using the keypad in response to a prompt or message.

Provides additional explanations or information about the steps of that particular system mode menu. A Submenu row indicates a specific procedure evoked from a main menu screen. A description of that procedure immediately follows the Submenu row. The following keys have the same function from all submenus:

Press the enter key to save changes from a submenu and return to the menu screen.

Press the cancel key to exit any submenu without saving changes. OMNI 3600 REFERENCE MANUAL 41 SYSTEM MODE System Mode Menus Enter and Exit System Mode To enter system mode after you have turned on the Omni 3600 terminal, follow the procedure described in Table 5. NOTE On successful completion, some operations automatically exit system mode and restart the terminal. Other operations require that you exit system mode and restart the terminal. To manually exit system mode, select RESTART F4 in SYS MODE MENU 1. Table 5 Enter System Mode Display Action VERIFONE OMNI 3600a Q80000XX 4/10/01 VERIX COPYRIGHT (C) 1997-2003 VERIFONE, INC. ALL RIGHTS RESERVED Battery 95%

(Application Prompt) or DOWNLOAD NEEDED At startup, the terminal displays a copyright notice screen that shows the terminal model number, the version of the Omni 3600 system firmware stored in the terminals flash memory, the date the firmware was loaded into the terminal, the copyright notice, and battery charge remaining. This screen appears for three seconds, during which time you can enter system mode by simultaneously pressing F2 and F4. You can extend the display period of this screen by pressing any key during the initial three seconds. Each key press extends the display period an additional three seconds. If an application already resides on the terminal, an application-specific prompt displays. If no application resides on the terminal, the following message displays:

DOWNLOAD NEEDED To enter system mode from this screen, simultaneously press F2 and F4. 42 OMNI 3600 REFERENCE MANUAL SYSTEM MODE System Mode Menus Table 5 Enter System Mode (continued) Display Action SYSTEM MODE ENTRY PASSWORD

SYS MODE MENU 1 CONTRAST F2 CLOCK F3 RESTART F4 If an application prompt appeared in Step 2 and you chose to enter system mode you are prompted to type the system password. If DOWNLOAD NEEDED appeared in Step 2, use the default password Z66831. This password is entered as:

1 ALPHA ALPHA 6 6 8 3 1, and press []

Use the backspace [] key to delete the entry and correct any mistakes. If you enter an incorrect password, the terminal exits the SYSTEM MODE ENTRY screen. Verify your password and re-enter it. To quit this operation and return to the application prompt or DOWNLOAD NEEDED screen, press the cancel key. SYS MODE MENU 1 is the first menu to display. To toggle through to the other six menus, press the PF2 key or [] until you reach the desired menu. a. May have the letter G for GSM radio, P for GPRS radio, or C for CDMA radio. System Mode Menu 1 In this menu you can adjust the display contrast, set the terminal clock, and exit system mode. Table 6 System Mode Menu 1 Display Action SYS MODE MENU 1 CONTRAST F2 CLOCK F3 RESTART F4 CONTRAST F2 SYS MODE CONTRAST CONTRAST UP F2 CONTRAST DOWN F3 To adjust the display contrast, select CONTRAST F2. To set the date and time, select CLOCK F3. To restart the terminal, select RESTART F4. To toggle to system mode menu 2, press PF2 or []. Select CONTRAST UP F2 to increase display contrast or CONTRAST DOWN F3 to decrease display contrast. To return to the main menu and save your changes, press []. OMNI 3600 REFERENCE MANUAL 43 SYSTEM MODE System Mode Menus Table 6 System Mode Menu 1 (continued) Display CLOCK F3 Action Note:

The terminal clock is battery-backed to retain date and time settings when the terminal is shut off. SYS MODE CLOCK YEAR: 2003 MONTH: 02 DAY: 22 SYS MODE CLOCK HOUR: 17 MINUTE: 32 RESTART F4 This example shows February 22, 2001. To set YEAR, press F2 and type a four-digit number for the current year. To set MONTH, press F3 and type a two-digit number for the current month (between 01 12). To set DAY, press F4 and type a two-digit number for the current day (between 0131). To save your changes and return to SYS MODE MENU 1, press the PF1 key. To set the time, go to Note:

The terminal only accepts entries in the format and range specified above. Errors are not highlighted; you must ensure each entry is correct. To correct a mistake, press the fields function key (for example, F2 for YEAR) and type a new entry. This example shows 5:32 P.M. To set HOUR, press F2 and type a two-digit number between 0023 (using the twenty-four hour clock). To set MINUTE, press F3 and type a two-digit number between 0159. Note:

The terminal only accepts entries in the format and range specified above. Errors are not highlighted; therefore, you must ensure each entry is correct. To correct a mistake, press the fields function key (for example, F2 for HOUR) and type a new entry. To return to the previous menu to set the date, press the PF1 key. To save your changes and return to SYS MODE MENU 1, press enter. Select RESTART F4 to exit system mode and restart the terminal. System Mode Menu 2 In this menu, you can accomplish full or partial downloads to your terminal, clear RAM files, and clear flash files. NOTE Before performing a download to flash memory in an initialized terminal (one that contains an application), reclaim all available flash space. Unlike RAM, unused flash and duplicate flash information are not automatically reclaimed during a download. To reclaim this space perform a defrag operation from system mode

(refer to the procedure FLASH FILES F4, in Table 7). This operation makes all files in flash contiguous. You must also clear some or all flash memory if your terminal does not have enough space for the impending download. 44 OMNI 3600 REFERENCE MANUAL SYSTEM MODE System Mode Menus You cannot perform download, clear, and defragment operations if you entered system mode while an application is running. If you see the message APPLICATION ALREADY RUNNING, PLEASE RESTART, press the cancel key and restart the terminal from system mode menu 1. When you see the copyright notice screen, enter system mode within 3 seconds (before the application begins). Table 7 System Mode Menu 2 Display Action SYS MODE MENU 2 DOWNLOAD F2 RAM FILES F3 FLASH FILES F4 DOWNLOAD F2 SYS MODE FILE FILE GROUP _1 SYSTEM MODE FILE GROUP NN PASSWORD

SYS MODE DOWNLOAD FULL F3 PARTIAL F4 SYS MODE DOWNLOAD MODEM F2 COM1 F3 WIRELESS F4 SYS MODE DOWNLOAD

DOWNLOADING NOW To download an application to your terminal, select DOWNLOAD F2. To clear RAM files, select RAM FILES F3. To clear flash files, select FLASH FILES F4. To return to the previous system mode menu, press the PF1 key. To return immediately to SYS MODE MENU 1, or to quit any operation within this menu, press the cancel key. To toggle to SYS MODE MENU 3, press the PF2 key or

[]. Type the number of the file group (1 for the primary application; between 115 for other applications) to perform the download. (Refer to Chapter 4 for detailed download instructions and information.) After you type a file group number, press []. To continue, enter the required password. If you enter an incorrect password, the following message appears:

SYS MODE PASSWORD PLEASE TRY AGAIN Press []. Verify your password and re-enter it. For a full download, select FULL F3. For a partial download, select PARTIAL F4. (Refer to Chapter 4 for detailed download instructions and information.) To return to the main menu, press the PF1 key. Select a download mode: MODEM F2, COM1 F3, or WIRELESS F4. To return to the main menu without saving your selection, press the cancel key. The terminal is ready to receive a download. During the download, a line of asterisks appears that shows percentage of completion. Each asterisk equals approximately 10% of the download. You can cancel a download by pressing the cancel key during the download; doing so restarts your terminal. OMNI 3600 REFERENCE MANUAL 45 SYSTEM MODE System Mode Menus Table 7 System Mode Menu 2 (continued) Display RAM FILES F3 SYS MODE RAM CLEAR GROUP _1 F2 CLEAR ALL FILES F3 SYSTEM MODE FILE GROUP NN PASSWORD

SYS MODE CONFIRM CANCEL F3 CONFIRM F4 FLASH FILES F4 SYS MODE FLASH F2 F3 CLEAR GROUP _1 CLEAR ALL FILES DEFRAG 0 F4 Action To clear a file groups RAM files, type the file group number (115) and press F2. To correct a mistake, press [] to delete the number, and type a new entry. CONFIG.SYS protected records that begin with * or #

are retained when you clear a RAM file group. To clear the RAM of all file groups, select CLEAR ALL FILES F3. This operation also clears the CONFIG.SYS files from all groups except Group 1. Records that begin with * or # in Group 1 are retained. Note:

If you have not previously entered a groups password in this session, the terminal prompts for the groups password prior to clearing that groups RAM files. To continue, enter the required password. If you enter an incorrect password, the following message appears:

SYS MODE PASSWORD PLEASE TRY AGAIN Press []. Verify your password and re-enter it. To cancel the operation, select CANCEL F3. To continue the operation, select CONFIRM F4. After the operation is complete, you return to the main menu. To clear a file groups flash files, type the file group number (115) and press F2. To correct a mistake, press [] to delete the number, and type a new entry. To clear the flash files of all file groups, press F3. If you have not previously entered a groups password in this session, the terminal prompts you for the groups password prior to clearing that groups flash files. CAUTION! Clearing all flash files erases the application program from your terminal. A new application download is then required. To defragment flash files, press F4, then skip to SYS MODE CONFIRM of this procedure. The number displayed beside DEFRAG is the total amount of space, in bytes, to reclaim in the defrag operation. 46 OMNI 3600 REFERENCE MANUAL SYSTEM MODE System Mode Menus Table 7 System Mode Menu 2 (continued) Display Action SYSTEM MODE FILE GROUP NN PASSWORD

SYS MODE CONFIRM CANCEL F3 CONFIRM F4 SYS MODE CLEAR CLEARING FLASH PLEASE WAIT SYS MODE DEFRAG RECLAIMING FLASH PLEASE WAIT To continue, enter the required password. If you enter an incorrect password, the following message appears:

SYS MODE PASSWORD PLEASE TRY AGAIN Press []. Verify your password and re-enter it. To cancel the operation, select CANCEL F3. To continue the operation, select CONFIRM F4. After the operation is completed, you are returned to the main SYS MODE MENU 2 screen. If you selected DEFRAG in SYS MODE FLASH and select CONFIRM F4 here, you are taken to SYS MODE DEFRAG. This operation may take a few seconds. If you have cleared all flash files, the terminal displays DOWNLOAD NEEDED on restart. If after clearing selected flash files you experience difficulties with your application, you may have accidentally deleted a flash file that the CONFIG.SYS file in File Group 1 uses. This type of error usually generates the error message RUN FAILED when trying to execute the application; you must restore the required File Group 1 flash file. This message indicates the flash files are being defragmented; this operation may take a few seconds. On successful completion, the terminal automatically restarts. System Mode Menu 3 In this menu, you can view terminal configuration information, edit the CONFIG.SYS or another keyed file, and change system mode and file group passwords. NOTE Some application program downloads automatically reset the system password. OMNI 3600 REFERENCE MANUAL 47 SYSTEM MODE System Mode Menus Table 8 System Mode Menu 3 Display Action SYS MODE MENU 3 CONFIG INFO F2 EDIT F3 PASSWORDS F4 CONFIG INFO F2 SYS MODE CONF 728 481056 RAM FILES 3 INUSE AVAIL FLASH FILES 0 0 INUSE AVAIL 786424 SYS MODE CONF RAM FLASH SERNO PTID PART VERS 512 1024 K2-0001 12000000 P096-100-02 A To view terminal configuration information, select CONFIG INFO F2. To edit the CONFIG.SYS or another keyed file, or to set the country code for your terminals modem, select EDIT F3. (For more information, refer to the Edit Keyed Files section that follows this main menu description.) To change the system mode and file group passwords, select PASSWORDS F4. The file groups and system mode all use a default password that is pre-set at the factory: Z66831. It is entered as:

1 ALPHA ALPHA 6 6 8 3 1 and press []. To return to the previous system mode menu, press the PF1 key. To return immediately to SYS MODE MENU 1, or to quit any operation within this menu, press the cancel key. To toggle to the system mode menu 4, press the PF2 key or []. This screen shows the number of kilobytes in use and that available for RAM and flash. To continue, press the PF2 key. This screen shows configuration information specific to your terminal:

Total kilobytes of RAM memory

Total kilobytes of flash memory

Serial number

Permanent terminal identification number (PTID)

Terminal part number

Terminal hardware version number Your terminals screen may vary depending on your terminals model and the operating system version installed. To return to the previous menu, press the PF1 key; to continue, press the PF2 key. 48 OMNI 3600 REFERENCE MANUAL SYSTEM MODE System Mode Menus Table 8 System Mode Menu 3 (continued) Display Action SYS MODE CONF MODL CTRY KEYPAD DISPLAY MAG RDR PRINTER OMNI3600 US 0 128064 0 1 SYS MODE CONF PINPAD LIFE RSET 971117023334 0 73525 RCNT 29 MODEM CTRY?

EDIT F3 SYS MODE FILE FILE GROUP _1 SYSTEM MODE FILE GROUP NN PASSWORD

This screen shows additional configuration information specific to your terminal:

Model number

Country of manufacture

Keypad type (0 = Telco, 1 = calculator, 2 = Singapore)

Display unit type

Magnetic stripe card reader type

Whether or not a thermal printer is integrated into the terminal (where 0 = No, 1 = Yes) To return to the previous menu, select the PF1 key; to continue, select the PF2 key. To return to the main menu, press the cancel key. This screen shows additional configuration information specific to your terminal:

Whether or not a PIN pad device is integrated into the terminal (where 0 = No, 1 = Yes)

Number of seconds the terminal has run (LIFE)

Last reset date and time, in YYMMDDHHMMSS format (where YY = year, MM = month, DD = day, HH = hour, MM = minute, and SS = second)

Number of times the terminal has been reset (RCNT)

Modem country code (not applicable on this model) To return to the previous menu, select the PF1 key; to return to the main menu, press the cancel key. To search for keyed records in a particular file group, type the appropriate group number and press []. If you cannot locate a particular keyed record, it may be stored in another file group. To search for keyed records in another file group, return to the main menu by pressing the cancel key, then type the appropriate group number and press []. To correct a mistake, press [] to delete the number, and type the new entry. To continue, enter the required password. If you enter an incorrect password, the following message appears:

SYS MODE PASSWORD PLEASE TRY AGAIN Press []. Verify your password and re-enter it. OMNI 3600 REFERENCE MANUAL 49 SYSTEM MODE System Mode Menus Table 8 System Mode Menu 3 (continued) Action To edit the CONFIG.SYS file, press []. Note:

In this menu, you can create a new keyed file or edit an existing one. First, use [] to clear any previous key name from the display. Then, type the key name, press [], and skip to the SYS MODE EDIT VALUE screen below. To create or search for a keyed record, use [] to clear any previous key name from the display. Then, type the key name, press [], and skip to Step 5b of this procedure. To scroll through the search keys, press [], or use the PF1 or PF2 keys to scroll the up and down respectively, as needed. To scroll through keyed records, press either the PF3 or the PF4 key, below the Left and Right arrows respectively, as needed. To scroll through the search keys, press []. Or use the PF1 or PF2 keys to scroll the up and down respectively, as needed. To manually enter another key name, select KEY F2 and use [] to clear the previous key name from the display. Then, type the appropriate key name and press []. To scroll through the displayed key value, press either the PF3 or the PF4 key, below the Left and Right arrows respectively, as needed. To edit a key value, select VALUE F3 and proceed to the next step. To create or edit a key value, use [] to clear any previous key value from the display. Then, type the new key value and press []. To exit SYS MODE EDIT after completing your edit operations, press the cancel key twice. Display SYS MODE EDIT FILE CONFIG.SYS_ SYS MODE EDIT KEY

(KEY NAME)--------

SYS MODE EDIT

(KEY NAME) KEY

(KEY VALUE) F2 VALUE F3 SYS MODE EDIT VALUE

(Value)----------------

SYS MODE EDIT

(Key name) KEY F2

(Key value)VALUE F3 50 OMNI 3600 REFERENCE MANUAL SYSTEM MODE System Mode Menus Table 8 System Mode Menu 3 (continued) Display PASSWORDS F4 Action SYS MODE PASSWORD FILE GROUP _1 F2 SYS MODE ENTRY F3 SYSTEM MODE FILE GROUP NN PASSWORD

SYS MODE PASSWORD NEW----------------------

To change the password of File Group 1, select FILE GROUP _1 F2. Then, go to SYSTEM MODE FILE GROUP NN PASSWORD below. To change the password of another file group, type the appropriate file group number and press F2. Then, go to SYSTEM MODE FILE GROUP NN PASSWORD below. To correct a mistake, press [] to delete the number, and type the new entry. To change the system password, select SYS MODE ENTRY F3. Then, skip to SYS MODE PASSWORD NEW below. Note: Some application program downloads automatically reset the system mode password. Type the current password for the selected file group and press []. If you enter an incorrect password, the following message appears:

SYS MODE PASSWORD PLEASE TRY AGAIN Press []. Verify your password and re-enter it. Type the new password and press []. To correct a mistake, press [] to delete the number, and then type the new entry. SYS MODE PASSWORD AGAIN--------------------

The terminal requests that you verify the new password. Retype the new password and press []. SYS MODE PASSWORD PASSWORD CHANGED The new password is now in effect. To exit this screen, press []. You are returned to the main menu. OMNI 3600 REFERENCE MANUAL 51 SYSTEM MODE System Mode Menus NOTE When entering any password, an asterisk (*) appears on the display for each character you type. These asterisks prevent your password from being seen by an unauthorized person. Pressing the ALPHA key changes the characters or symbols you enter, but ALPHA does not cause additional asterisks to appear. Secure a copy of every password to ensure it is not forgotten or lost. Edit Keyed Files A keyed file is a collection of individual records, which contain ASCII data and are identified by unique search keys. You can edit the ASCII data directly from the terminal keypad using the terminals built-in keyed file editor. Each record has two parts: a key name and a key value. The search key is a variable-length string, or key name, that identifies the record. The information assigned to the search key is contained in a separate variable-length string, or key value. For example, in CONFIG.SYS, the ZonTalk key for the application serial ID number is *ZT. The value for the key is the actual application ID number. By entering *ZT using the editor, the terminal can quickly locate the application serial ID number. You can also use [] to scroll through the search keys instead of entering the characters *ZT through the keypad. NOTE For a complete list of the ASCII characters supported by the Omni 3600, as well as their decimal and hexadecimal equivalents, please refer to Appendix B. CONFIG.SYS: Protected and Non-protected Records The concept of protected and non-protected records applies only to the CONFIG.SYS files in your terminal. Protected records are those with search keys beginning with an asterisk (*) or a pound symbol (#). Prior to a download, the recommended procedure is to clear RAM files. Protected records in the File Group 1 CONFIG.SYS file are retained in a full application download and when RAM is cleared. Non-protected records are all other CONFIG.SYS files, and records of other files. These records are deleted when RAM is cleared. Editing CONFIG.SYS with an External Editor You can create and edit the CONFIG.SYS files of Omni 3600 applications through an IBM PC-compatible computer when you download files to the terminal. For more information on editing an applications CONFIG.SYS file, refer to the ZonTalk 2000 Reference Manual, the Verix Programmers Manual, or contact your local VeriFone representative. For more information about using VeriCentre Download Management Module in client-server installations, please contact your local VeriFone representative. System Mode Menu 4 In this menu you can view the error log and perform application debugging operations. 52 OMNI 3600 REFERENCE MANUAL SYSTEM MODE System Mode Menus Table 9 System Mode Menu 4 Display Action SYS MODE MENU 4 REMOTE DIAGS F2 ERROR LOG F3 DEBUGGER F4 REMOTE DIAGS: This function is reserved for future use with TMM. To return to the previous system mode menu, press the PF1 key; to return immediately to SYS MODE MENU 1, or to quit any operation within this menu, press the cancel key; to move to the next system mode menu, press the PF2 key or []. ERROR LOG F3 SYS MODE ERR LOG 0000 TYPE FRAME 00800698 008002BA F1000002 00A00000 SYS MODE ERR LOG USP TCB TIME 2491ED57 00000000 010329053144 DEBUGGER F4 The error log screens display internal diagnostic information about the most recent unrecoverable software error. If you report a terminal problem, you may be asked to provide this information. This first screen displays the following:

TYPE (Error Type) FRAME (Stack Frame) After making any notations, press the PF2 key to view additional error log information. This screen displays the following:

USP (User Stack Pointer) TCB (Task Control Block) TIME (binary-coded, decimal system, clock time of the error in the format yymmddhhmmss, where yy = year, mm = month, dd = day, hh = hour, mm = minute, and ss = second) After taking desired notes, press the PF1 key to view the previous screen or press the cancel key to return to the main menu. DEBUGGER F4: This selection starts the application programs debug monitor, if installed, on the selected file group. The Verix Operating System Programmers Manual fully documents debug operations. For more information on debugging your terminal, contact your terminal supplier. OMNI 3600 REFERENCE MANUAL 53 SYSTEM MODE System Mode Menu 5 System Mode Menu 5 In this menu you can test the display panel, keyboard, and magnetic stripe card reader. Table 10 System Mode Menu 5 Display Action SYS MODE MENU 5 SCREEN DIAG F2 KEYBOARD DIAG F3 MAG CARD DIAG F4 SCREEN DIAG F2 KEYBOARD DIAG F3 SYS MODE KBD TEST KEYCODE NN MAG CARD DIAG F4 SYS MODE TRK 1:VALID DATA TRK 2:VALID DATA TRK 3:VALID DATA To test the display panel, select SCREEN DIAG F2. To test the keyboard, select KEYBOARD DIAG F3. To test the magnetic card reader, select MAG CARD DIAG F4. To return to the previous system mode menu, press the PF1 key; to toggle through to SYS MODE MENU 6, press the PF2 key; to return immediately to SYS MODE MENU 1, or to quit any operation within this menu, press the cancel key. When you select F2, you should see a completely dark screen. Press [] to completely clear the screen. To stop the test and return to the main menu, press the cancel key. This screen displays the decimal ASCII keycode for each key you press. The value displayed corresponds to the actual key pressed. Other values assigned to keys (for example, Q, Z, and . are assigned to [1]) are software dependent. To test the keyboard, press some keys and check that they match their ASCII keycodes (for example, [1]

displays keycode 31). For more ASCII keycodes, refer to the ASCII table in Appendix B. To stop the test and return to the main menu, press either the cancel key or []. To test the magnetic-stripe card reader, swipe a magnetic-stripe card through it. A successful test displays VALID DATA for each track that read valid data. An error generates one of the following error messages for each track with an error:

NO DATA NO START NO END LRC ERR PARITY ERR REVERSE END For more information about magnetic card error messages, refer to the Verix Programmers Manual. To stop the test and return to the main menu, press the cancel key. 54 OMNI 3600 REFERENCE MANUAL SYSTEM MODE System Mode Menu 5 System Mode Menu 6 In this menu you can run integrated PIN pad (IPP) diagnostics, check the IPP key loading mode, display printer information, and run printer tests. Table 11 System Mode Menu 6 Display Action SYS MODE MENU 6 IPP DIAG F2 IPP KEY LOAD F3 PRINTER DIAG F4 IPP DIAG F2 INTERNAL PIN PAD MEMORY TEST PASSED IPP6 0PGP021 12/99 B6 SN: 00000000000000000000 BAUD: 1200 MODE: VISA RESET F3 EXIT F4 IPP KEY LOAD F3 INTERNAL PIN PAD KEY LOADING MODE BYTES SENT 0 BYTES RCVD 0 END F4 PRINTER DIAG F4 PRINTER ID VERSION STATUS F4 M 0LIT002C 20 TEST F3 PAPER FEED To test the IPP, select IPP DIAG F2. To test the IPP key load, select IPP KEY LOAD F3. To run printer diagnostics and test the printer, select PRINTER DIAG F4. To return to the previous system mode menu, press the PF1 key; to toggle through to SYS MODE MENU 7, press the PF2 key; to return immediately to SYS MODE MENU 1, or to quit any operation within this menu, press the cancel key. When you select F2, the INTERNAL PIN PAD screen appears and the diagnostic test begins. The firmware version and download date, IPP serial number, baud rate, and mode display. To reset the IPP, press F3; to exit the test and return to SYS MODE MENU 6, press F4 or the cancel key. Select this mode when using SecureKit or programming from your PC to inject keys into your terminal. The terminal must be docked to inject keys using these tools. In this mode, a pipe is opened through COM1 to the IPP to allow key loading. Press the cancel key to stop the key load session;

press F4 when finished with the key load. When you select F4, the firmware ID and version, and the printer status appear. Press F3 to run the printer test. A print sample begins that uses approximately 30.5 cm (12) of paper. This allows you to test the print quality and adjust your code for print optimization. See the Verix Programmers Manual for specifics on application development and the internal thermal printer. Press F4 to run approximately 5 cm (2) of paper through the printer without printing. To exit this screen, press the cancel key. OMNI 3600 REFERENCE MANUAL 55 SYSTEM MODE System Mode Menu 5 System Mode Menu 7 In this menu you can check the status of the smart battery. Table 12 System Mode Menu 7 Display Action SYS MODE MENU 7 Press F2 to bring up the state of the battery. BATTERY STATUS F2 BATTERY STATUS F2 BATTERY STATUS FULL CHARGE REMAINING 1556 VOLTAGE STATUS 1680 93%

8161 00C0 When you select F2, the BATTERY STATUS screen appears. The full charge state of the smart battery displays in mA hours. The remaining charge capacity and state (in mA hours) displays. The voltage capacity displays in mV. A hex value stating the status of the smart battery displays. 56 OMNI 3600 REFERENCE MANUAL CHAPTER 4 Performing Downloads This chapter contains information and procedures to allow you to perform the various types of data transfers required to:

Develop applications for the Omni 3600 terminal.

Prepare Omni 3600 terminals for deployment.

Maintain Omni 3600 terminal installations in the field.

Transfer data to/from terminals. In this chapter, information pertaining to file authentication is only discussed in the context of procedures while performing file downloads. See Chapter 5 for further file authentication discussion. The Omni 3600 terminal can perform downloads when docked with the base station. NOTE Wireless downloads can only be performed on Omni 3600 models connected to a GSM network. The base station contains ports that allow the Omni 3600 terminal to connect to a network, telephone line, or perform back-to-back downloads. See Download Methods. Downloads and Uploads In downloads, data transfers from a sending system to a receiving system. The term download also refers to a terminal receiving data. The term upload describes the process of a terminal sending data. Use any of the following three operations to program, deploy, transfer data files from, and support Omni 3600 terminals:

Host computer downloads: Applications, operating systems and associated files transfer from a host PC to a Omni 3600 terminal

Back-to-back downloads: Applications and associated files transfer from one Omni 3600 terminal to another Omni 3600 terminal

Wireless downloads: Applications, operating systems or OS updates, and data files transfer between your wireless service provider and a Omni 3600 terminal OMNI 3600 REFERENCE MANUAL 57 PERFORMING DOWNLOADS Download Methods Download Methods The following four methods are available for file and data downloads through the Omni 3600 download and upload procedures:

Direct downloads: Files and/or data transfer directly from the sending system

(a host computer) to the receiving system (an Omni 3600 terminal docked on the base station or connected using the MOD10 adapter). A special cable (PN 056051-00) connects the RS-232 serial ports of the two systems.

Downloads by telephone: Files and data transfer over a telephone line from the sending system (a host computer) to the receiving system (an Omni 3600 terminal docked on the base station). The modem of the sending host computer, and the internal modem of base station are connected by a telephone line connection. Data transfers into the Omni 3600 terminal through the docking port contacts on the base unit.

Back-to-back downloads: Files and data transfer from a docked, sending Omni 3600 terminal to a docked receiving Omni 3600 terminal. A special cable (PN 056051-00) connects the RS-232 serial ports of the two base stations.Two undocked terminals can also be connected with the MOD10 adaptor.

Wireless downloads (Omni 3600 GSM models only): Files and data transfer over your wireless system providers network. The Omni 3600 terminal does not need to be docked in the base station for this type of download. Large downloads can take a long time. It is recommend that the unit be connected to the power pack during this process. NOTE The Omni 3600 terminal can complete the first three types of downloads listed above only when docked in the base station. The base unit contains the ports to make the required wired connections (RS-232 and modem). Download Tools NOTE Three software tools are available from VeriFone for performing downloads. Because of the large size of some download files, VeriFone recommends only using download tools provided by VeriFone. CRC and other error checking is not supported on the GSM system. VeriFone download tools provide these error checking mechanisms. The following three software tools are for performing direct downloads and downloads by telephone from a host computer to an Omni 3600 terminal:

VeriCentre Download Management Module (DMM): Multi-user environment for software downloads. DMM supports Windows NT clients and has a sophisticated database to manage up to 100,000 terminals. The Omni 3600 operating system supports file decompression for archives created using DMM. 58 OMNI 3600 REFERENCE MANUAL PERFORMING DOWNLOADS Download Content

ZonTalk 2000: PC-based software tool to manage applications and data for VeriFone. In addition to being a database and communications management tool, ZonTalk 2000 automates application downloads and updates to terminal records.

DDL.EXE (Direct Download Utility): Download files and data from a development system or other host computer directly to an Omni 3600 terminal over a serial cable connection. DDL.EXE is a 32-bit, Windows 95 program included in the VDTK (Verix Developers Toolkit). NOTE No special software tool or utility is required to perform back-to-back application downloads. Only a serial cable connected between two terminals is required. This data transfer procedure, invoked from within system mode, is handled by the OS software and firmware of the sending and receiving Omni 3600 terminals. Download Content In general, you can download files and data to an Omni 3600 terminal. The types of files and data can be grouped into the following functional categories:

Operating system files: A set of related programs and data files provided by VeriFone to control the terminals basic processes and functions. Files that belong to the OS are stored in a reserved area of the terminal memory. A complete OS is downloaded to each Omni 3600 terminal during the manufacture. If necessary, download newer versions during application development, when preparing for deployment, or to terminals in the field.

Applications and related files: An application is a computer program consisting of one or more executables, including compiled and linked object files (*.out), and one or more function libraries (*.lib). Most applications also include font files (*.vft, *.fon), data files (*.dat), and other related file types. Omni 3600 applications can be developed by VeriFone, customers, or third parties on customer request. One or more applications must be downloaded to the Omni 3600 terminal before it can be deployed at a customer site and used to process transactions.

Files related to file authentication: The logical component of the VeriShield security architecture in the Omni 3600 terminal is file authentication. For an executable to run on an Omni 3600 terminal, it must be authenticated by the VeriShield file authentication module. NOTE For a details on file authentication, see Chapter 5. Two special types of files are required for the file authentication process:

digital certificates (*.crt) and signature files (*.p7s). These file types must be downloaded to the terminal together with the application files to authenticate.

Terminal configuration settings: Files or records that contain various types of data can also be downloaded to an Omni 3600 terminal, including OMNI 3600 REFERENCE MANUAL 59 PERFORMING DOWNLOADS Full and Partial Downloads Full and Partial Downloads CONFIG.SYS variables, passwords for accessing protected system mode functions, the current date and time, the modem country code setting, and so on (refer to Chapter 3). When preparing to initiate a download procedure, you must choose either a full or partial download and the COM 1 port, through the system mode menu options

(refer to Chapter 3). Depending on the type of files you are downloading and the download method you are using, there are some restrictions on if a full or partial download is permitted. The various types of full and partial download procedures are listed and described in Table 13. Table 13 Types of Full and Partial Downloads Download Type Description and Effects Partial application download Full application download An entire application, including all executables and data files, transfers from one system to another in a single operation. Files related to the file authentication process and terminal configuration settings can be included in a full application download. During this process RAM is cleared. Following a full application download, the terminal restarts and the file authentication module is invoked. If application files are authenticated, the application executes. A subset of application executables, font files, and/or data files transfer from one system to another to modify or update an existing application. Files related to file authentication and terminal configuration settings can be included in a partial application download. During this process, RAM is not cleared. Following a partial application download, the terminal does not restart and returns control to system mode or the issuing application. The file authentication module is not invoked, nor is the application allowed to execute, until the terminal is manually restarted from within system mode. Download Methods Supported

Direct downloads

Telephone downloads

Back-to-back downloads

Wireless downloadsa

Direct downloads

Telephone downloads

Wireless downloadsa Note:

Partial back-to-back downloads are not supported. 60 OMNI 3600 REFERENCE MANUAL PERFORMING DOWNLOADS Full and Partial Downloads Download Methods Supported

Direct downloads

Telephone downloads

Wirelessa Full back-to-back OS downloads are not supported

Direct downloads

Telephone downloads

Wirelessa Partial back-to-back operating system downloads are not supported. Table 13 Types of Full and Partial Downloads (continued) Download Type Description and Effects Full operating system download Partial operating system download An entire OS version transfers from a host PC to the Omni 3600 terminal. Files related to file authentication and terminal configuration settings can be included in a full OS download. During this process, RAM is cleared. Following a full OS download, the terminal restarts and the file authentication module is invoked. If the OS files are authenticated, the new OS updates (replaces) the existing OS. Application files stored in the memory area where the OS downloads (Group 1) are erased. Either an entire or a partial OS version transfers from a host PC to the Omni 3600 terminal. Files related to file authentication and terminal configuration settings can be included in a partial OS download. Following a partial OS download, the terminal does not restart and returns control to system mode or the issuing application. The file authentication module is not invoked, and the new OS is not processed until you manually restart the terminal from within system mode. If the new OS is authenticated, it then updates (replaces) the existing OS. Application files stored in the memory area the OS downloaded into (Group 1) are retained. a. Because of the large size of download files, VeriFone recommends using only VeriFone supplied download tools. CRC and other error checking is not supported on the GSM system. VeriFone download tools provide these error checking mechanisms. Here are a few more points on downloads:

The most common download procedure is a full (complete) application download.

Partial application downloads are useful when developing and testing new applications.

Full OS downloads are usually performed by VeriFone at the factory and, on occasion, by those who deploy terminals or in the field to upgrade older terminals to a newer OS version.

Partial OS downloads are performed mainly by VeriFone for development purposes and are rarely performed in the field.

Partial downloads are routinely performed by many applications. This procedure, which can be automated by an application running on a remote OMNI 3600 REFERENCE MANUAL 61 PERFORMING DOWNLOADS Omni 3600 Download Differences host computer, permits the host application to update data files and terminal configuration settings in an Omni 3600 terminal and then return control to the main application.

Full downloads restart the terminal; partial downloads return control to system mode or the issuing application. OS and application downloads can be combined. The file authentication module is not invoked until the terminal is restarted following the download procedure. Omni 3600 Download Differences To help you plan download tasks and explain how the download procedures for Omni 3600 terminals may differ from those you may be accustomed to using for other POS terminals, some information on the following related topics is included in this chapter:

Support for multiple applications

Use of RAM and flash memory

Redirection of files during application downloads

File authentication requirements Support for Multiple Applications The Omni 3600 terminal architecture supports multiple applications. This means that more than one application can reside in terminal memory, and that more than one application can run (execute) on the terminal. The application memory of the Omni 3600 terminal uses a system of file groups to store and manage multiple applications, as well as operating system files, in such a way that the data integrity of each application is ensured and that applications do not interfere with each another (see File Groups, page 38). How the File System Supports Multiple Applications The application memory partition of the Omni 3600 terminal is divided into 15 logically-defined sub-partitions called file groups or GIDs These groups are called Group 1, Group 2, and so on through GID15. Another partition of the terminal memory area, called Group 0, is reserved for the operating system and is logically separated from the application memory area. So, including Group 0, there is a total of 16 file groups. An application must be downloaded into a specific file group, along with any related files. You select the target file group for the download using system mode menu options and by entering a file group password. Usually, one application is stored in one file group. An application can, however, consist of more than one executable program file, and any number of executables

(*.out or *.lib) can be stored in a given group. In most implementations, there is a main application, one or more related programs or secondary applications, and one or more libraries. 62 OMNI 3600 REFERENCE MANUAL PERFORMING DOWNLOADS Omni 3600 Download Differences The main application must always be stored in the Group 1 sub-partition. Related programs or secondary applications can be stored in GIDs 214. GID15 is available to all other groups. The Main Application is Always Stored in GID1 The main application stored in GID1 is the controlling application for the terminal. Any function call that invokes a related program or a secondary application stored in GIDs 214 must be initiated by the GID1 application. An application stored in a file group other than GID1 is limited in that it can only access executables and files stored in its own file group and in GID15. Physical and Logical Access to File Groups The Omni 3600 operating system controls physical access to GIDs 115 using password-protected system mode functions. To download data into a specific file group, you must first enter system mode and choose the target group by making the appropriate menu selections. Then, you must enter the correct password for that file group. Each file group has its own CONFIG.SYS file. The CONFIG.SYS settings of the target group you select are always used as the system parameters for the download operation you are performing. The system of file groups also imposes some logical restrictions on which files can download into which file groups:

If GID1 is selected as the target group in system mode, you can download files into GID1 and redirect files into any of the other file groups, as required, in the same download operation. If another file group is selected as the target file group, you can download files only into that group and redirect files only to GID15. For example, if you select GID5 as the target group for the download, files can only download into GID5 and be redirected to GID15. Use of RAM and Flash Memory The Omni 3600 application memory partition has two separate file systems:

RAM (battery-backed volatile memory, also called SRAM), drive name I:

Flash (non-volatile memory), drive name F:

The fact that there are two different file systems has the following important implications for data transfer procedures:

Depending on the requirements of a specific application, some files must download into RAM and others into flash.

There are also rules that restrict which types of files you can download and store in which file system (RAM or flash). OMNI 3600 REFERENCE MANUAL 63 PERFORMING DOWNLOADS Omni 3600 Download Differences With application files, the application designer or programmer usually decides which file types to download into which file system. Other file types, such as operating system files, digital certificates, and signature files, must download into RAM. In a typical download procedure, all files are loaded into the RAM file system of the target group selected in system mode. Specific files included in the download package must be redirected, as necessary, to the flash file system of the target group or to the RAM or flash file system of another file group. To redirect files during a download procedure, see the following sections. Defragment Flash For Application Downloads Before you perform an application download, you may need to defragment terminal flash memory. For information on performing this system mode operation, see Table 7, page 45. To ensure the best result when performing back-to-back downloads, you may need to defragment the flash memory on the receiving terminals. A system mode procedure is also available for clearing the RAM or flash memory, either entirely or for a specific file group, to prepare an Omni 3600 for a clean download. NOTE The flash defragment operation is not necessary for an Omni 3600 terminal just out of the box. In this case, the terminal flash file system is still in its factory-new condition. Redirection of Files During Application Downloads You can download application files into RAM or flash memory. By default, files that you download to a specific file group are stored in the RAM of that group. To store a file in flash of that file group, you must provide instructions to redirect the file to flash as part of the procedure. There are two methods you can use to redirect files during an application download, depending on the download tool you are using:

If you are using Download Manager or ZonTalk 2000, you must manually create and include special zero-length files called SETDRIVE.x and SETGROUP.n on the download computer, and add these files to the batch download list to direct files to a specific file system (drive) or file group. If you are using DDL.EXE to perform direct downloads, you can use a special command-line option that automatically redirects files to the drive and file group you specify. Both of these methods are further described in the following sections. 64 OMNI 3600 REFERENCE MANUAL PERFORMING DOWNLOADS Omni 3600 Download Differences Manually Redirecting Files to Flash Memory To manually redirect files to flash memory for Download Manager or ZonTalk 2000 application downloads, you must create one or more files on the download computer with the special file name, SETDRIVE.x, where, x is the name of the drive (memory area) to download files to:

Drive name I: is RAM: This is the system mode default for downloads.

Drive name F: is flash. To create a zero-length SETDRIVE file on the download computer, use the DOS command, REM, as in the following example:

REM >SETDRIVE.F To redirect a file from RAM of the target group to flash of the same file group, insert the zero-length SETDRIVE.F file into the batch of application files to download. All files that follow the SETDRIVE.F file in the download list automatically load into flash memory (F:) of the target group. If you do not insert a SETDRIVE.F special file in the download list, all files download by default into the RAM (drive I:) of the target file group. You can also insert a zero-length file with the name SETDRIVE.I into the download list at any point to indicate that the following files download into RAM. For example, the following batch download list loads the executable code file FOO.OUT into the RAM of the selected file group (default Group 1). Because the signature file, FOO.P7S is included, FOO.OUT is also authenticated when the terminal restarts after the download. The *GO variable in this example indicates that the FOO.OUT application executes on restart, after successful authentication. The two data files that follow the zero-length SETDRIVE.F file, FOO.DAT and FOO.VFT, are redirected into flash of GID1. Because it follows the inserted zero-length SETDRIVE.I file, GOO.DAT downloads into Group 1 RAM. FOO.OUT FOO.P7S

*GO=FOO.OUT SETDRIVE.F FOO.DAT FOO.VFT SETDRIVE.I GOO.DAT OMNI 3600 REFERENCE MANUAL 65 PERFORMING DOWNLOADS Omni 3600 Download Differences You can also insert zero-length SETGROUP.n files into a batch download list to redirect files from the target file group to other file groups. Together, the zero-

length SETDRIVE.x and SETGROUP.n files allow you flexibility to store files as required in RAM or flash file systems and in specific file groups in a single batch download operation. NOTE You can only use zero-length SETDRIVE.x files for batch application downloads, either direct or telephone, and only using the Download Manager or ZonTalk 2000 download tools (and not DDL.EXE). You cannot use this special file convention for operating system downloads or for back-to-back application downloads. Redirecting Files to Other File Groups GID1 is the default system mode setting for performing downloads. Using the system mode menu options, you can select another file group (GID 215) as the target group for the application download. If you select another group, files download directly into the RAM of that file group. To redirect files from the selected target file group to another file group as part of the download operation, insert a zero-length SETGROUP.n file in the batch download list (the same as SETDRIVE.x). The syntax of this convention is SETGROUP.n, where n = 115, for GIDs 115. To create a zero-length SETGROUP file on the download computer, use the DOS command REM as in the following example:

REM >SETGROUP.2 If you do not insert SETGROUP.n special files into the download list, all files download into the target group selected in system mode. If no number is added to the SETGROUP filename, SETGROUP.1 (GID1) is assumed. Restrictions on File Redirection The Omni 3600 file system restricts how you can redirect files to other file groups. Here are the important points to remember:

The main application must always be downloaded into GID1.

Because of the way file groups are managed in the Omni 3600 file system, only two schemes are available for redirecting files during a batch application download:

If, using system mode menu options, you select Group 1 (default) as the target group for the download, files can be redirected to any other file group, including GID15.

If, using system mode menu options, you select a file group other than Group 1 (GIDs 214) as the target group for the download, files can be redirected only into the selected file group or into GID15. 66 OMNI 3600 REFERENCE MANUAL PERFORMING DOWNLOADS Omni 3600 Download Differences In the following example, GID1 is selected as the target group for the download. The download list loads FOO.OUT into Group 1 RAM, GOO.OUT into GID2, and the shared library, COMN.LIB, into GID15. When the terminal restarts after the download, the file authentication module is invoked for all three files, based on the certificate data that authorizes them to be stored in their respective file groups. If FOO.OUT is authenticated, the GID1 application, FOO.OUT, executes, as specified by the *GO variable, when the terminal restarts following successful file authentication. The function library stored in GID15 can be shared by both applications, as both Group 1 and Group 2 applications can access Group 15:

FOO.OUT FOO.P7S

*GO=FOO.OUT SETGROUP.2 GOO.OUT GOO.P7S SETGROUP.15 COMN.LIB COMN.P7S NOTE You can only use zero-length SETGROUP.x files for batch application downloads, either direct or telephone, and only using the Download Manager or ZonTalk 2000 download tools (not DDL.EXE). You cannot use this special file convention for operating system downloads or back-to-back application downloads. Using DDL.EXE to Automatically Redirect Files The version of DDL.EXE included in the Omni 3600 SDK allows you to change the default drive and file group for a direct download by preceding the filename(s) on the DDL command line with a special filename. The syntax is as follows:

SETDRIVE.<drive letter>

where, drive letter is I: (RAM, default) or F: (flash), and/or SETGROUP.<group number>

where, group number is 115. For example, the following command-line entry:

DDL SETDRIVE.F cardco.lib SETDRIVE.I SETGROUP.15 card.dat downloads the executable file cardco.lib into the flash of the selected target group and the data file card.dat into Group 15 RAM. (Because drive or group settings apply to all files that follow in the list, it is necessary to use SETDRIVE.x to reset the drive from F: back to I:.) If you are using this DDL.EXE method, zero-length SETDRIVE.x and SETGROUP.n files do not need to exist as files on the download computer. OMNI 3600 REFERENCE MANUAL 67 PERFORMING DOWNLOADS Omni 3600 Download Differences File Redirection in Operating System Downloads When performing an operating system download, you must download the OS files into Group 1 RAM and not into flash memory or into another file group. OS files download into Group 1 RAM because is not possible to download these files directly into Group 0. OS files are redirected to Group 0 depending on if you perform a full or partial download (see Table 13, page 60):

For full OS downloads, the redirection of OS files into Group 0 is performed automatically, after the terminal restart, as part of the download procedure. For partial OS downloads, OS files are redirected from the RAM of Group 1 into Group 0 on manual terminal restart by selecting the appropriate system mode menu option. 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 terminals 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. 68 OMNI 3600 REFERENCE MANUAL PERFORMING DOWNLOADS Omni 3600 Download Differences 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 3600 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.

A signature file must be downloaded together with each executable that makes up an application. An executable can be a compiled and linked object file (*.out) or a shared function library (*.lib). In most cases, an application consists of multiple executables and requires a number of corresponding signature files.

In a typical batch application download, all files, including executables, signature files, and any required certificates, download together in the same operation.

After the download is complete and the terminal restarts, the file authentication module is invoked if a new signature file (or certificate) is detected. If the application (executable) is authenticated, it is allowed to run on the terminal. Otherwise, it does not execute.

If one executable file is required by an application that consists of multiple executables fails to authenticate, the main application may crash when it attempts to access the non-authenticated executable.

Application files other than executables (for example, font and data files) may also require logical security under file authentication. In these cases, each protected non-executable file also requires a corresponding signature file.

Digital certificates (*.crt) and signature files (*.p7s) required to authenticate both application files and operating system files must always be downloaded into RAM of the target file group.

Certificate files are deleted from application memory after they are authenticated. If a certificate is not authenticated, it is retained in the terminal memory.

If the *FA variable in the CONFIG.SYS file of the target group is set to 1, signature files are redirected to the same location where the application file it OMNI 3600 REFERENCE MANUAL 69 PERFORMING DOWNLOADS Omni 3600 Download Differences authenticates is stored. If *FA is 0, signature files are deleted from RAM when the file authentication process is complete. The File Authentication Process During an Application Download In the following example of a typical file authentication process, it is assumed that we:

are downloading an application to prepare an Omni 3600 deployment terminal for deployment. That is, a sponsor certificate and a signer certificate download in batch mode to GID1 RAM of the receiving terminal, together with the application to authenticate. generated a signature file for each executable that comprises the application on the download computer using FILESIGN.EXE, with the signer certificate, signer private key, and signer password as required inputs. These signature files are also downloaded to the receiving terminal. In a typical batch application download, file authentication proceeds as follows:

1 All certificate files (*.crt), signature files (*.p7s), and application files (*.out,

*.lib, *.fon, *.vft, *.dat, and so on) download to the Omni 3600 deployment terminal in batch mode. 2 When the terminal restarts after the download, the file authentication module searches the RAM-based file system for the following two file types:

Authenticated certificate files (*.crt) to add to the permanent certificate tree

Signature files (*.p7s) that authenticate corresponding target application files Certificate files and signature files can download into the RAM of any file group. For this reason, the file authentication module searches through the entire file system (all file groups) for new files with these filename extensions each time the terminal restarts. 3 The file authentication module builds a list of all newly detected certificates and signature files. If no new certificates or signature files are located, the module just returns. If one or more new files of this kind are detected, the file authentication module starts processing them based on the list. 4 Certificates are always processed first (before signature files). The processing routine is called one time for each certificate in the list. If a certificate is authentic, it is noted, and the next certificate processed. This process continues in random order until all certificates are authenticated. When a certificate file in the processing list is authenticated, the Authenticated message displays below the corresponding filename. If it fails to be authenticated, the Failed message displays for five seconds and the terminal beeps three times (see Figure 30). The routine then resumes processing and continues until all certificates are successfully processed. 70 OMNI 3600 REFERENCE MANUAL PERFORMING DOWNLOADS Omni 3600 Download Differences The processing routine gives you both visible and audible indications if a specific certificate successfully authenticates. The file authentication module does not halt the process if a certificate fails to authenticate, but continues to the next step: authenticating signature files. If one or more certificates fail to authenticate, the ensuing file authentication process based on signature files probably also fails, with the result that an application is not authenticated and is not allowed to execute on the terminal. When a certificate file is authenticated, the data it contains is added to the certificate tree and the certificate file is deleted from the RAM. When all required certificates are authenticated and stored in the certificate tree, the file authentication process for signature files can proceed. Figure 30 5 Signature files are processed next (after certificate files). The file Display Prompts During the File Authentication Process authentication module calls the signature checking routine one time for each new signature file it detects. Each *.p7s file is checked as it is detected; a list is not built and multiple processing passes are not required.

If a signature file is authenticated, the AUTHENTIC message displays and the target files ATTR_NOT_AUTH bit is set to 1. If the authentication process fails, the FAILED message displays for five seconds and the terminal beeps three times (see Figure 30). The routine then continues processing the next signature file until all newly detected signature files are checked. If a signature file fails to authenticate and its target file is an executable code file, such as *.out or *.lib, the executable is not allowed to run on the terminal on terminal restart. OMNI 3600 REFERENCE MANUAL 71 PERFORMING DOWNLOADS Omni 3600 Download Differences For data files, font files, and any other files that require authentication to meet the applications design specification, the application must ensure that these files successfully authenticate. While a signature file is being processed, it remains stored in the RAM file system of the target file group. The target application file may be redirected immediately on download to RAM or flash. When the signature file successfully authenticates its target file, it is automatically moved to same the file system and file group as the target file it authenticates (that is, if *FA = 1). The processing routine gives you visible and audible indications of if a specific signature file successfully authenticates. The file authentication module does not halt the process if a signature file fails to authenticate, but continues to the next step: storing the downloaded files in their final locations in the terminal file system. 6 Certificate files and signature files are retained in the RAM file system until the file authentication process is complete. These special files are then either deleted or automatically redirected to another file system or file group, as previously described. When an application file is authenticated, the operating system sets the files read-only attribute to protect it from being modified while stored in terminal memory. This is also true for a signature file retained in terminal memory. When a signature file is assigned the read-only attribute, it is no longer detected as a new signature file by the file authentication module on terminal restart. 7 When all certificates and signature files are processed and special files deleted or redirected as required, the terminal restarts and the *GO application executes. File Group Permissions Now, consider how file authentication controls who (which business entity) can store application files in which file groups in the Omni 3600 file system. By inserting zero-length SETDRIVE.x and SETGROUP.n files into a download list, you can specify which drive (x = I: RAM or F: flash) and which group (n = 1 15) to store an application file. In addition to this file redirection protocol, the file authentication module controls which files are allowed, under the authority of the signer certificate used to sign them, to be stored in which file groups in the Omni 3600 file system. For example, if the terminal owner specifies that a loyalty application in be stored GID2, the information is encoded in the sponsor and signer certificates issued by the VeriFone CA for that terminal. 72 OMNI 3600 REFERENCE MANUAL PERFORMING DOWNLOADS Omni 3600 Download Differences Chapter 5 discussed how signer certificates are required inputs to FILESIGN.EXE when preparing a deployment terminal. Each signature file generated under that signer certificate contains a logical link that allows the application to authenticate and run on the terminal only if the signature files and corresponding target files are downloaded into the target GID. Although you can store files in any file group simply by selecting the target group in system mode, the files you download are not authenticated for the target group you selected unless they are properly signed under the authority of the sponsor and signer certificates issued for that terminal. Download an Operating System Update Provided by VeriFone Because the operating system software for the Omni 3600 is developed and controlled by VeriFone for its customers, VeriFone provides the necessary certificates and signature files to ensure the authenticity and integrity of the operating system update as part of the download package. NOTE Operating system files can only be transferred to an Omni 3600 terminal using a PC-to-terminal download procedure, either direct or by telephone. OS files cannot be downloaded to an Omni 3600 terminal in a back-to-back operation. The file authentication procedure for OS downloads is much the same as application downloads, with the following exceptions:

VeriFone provides all files required for the OS download, including The operating system files (such as Q.out, 1.out, and 2.out),

An encrypted list of the new files, called VFI.PED, and

A signature file generated by the VeriFone CA under the authority of a higher-level OS partition sponsor certificate, called VFI.P7S. The file authentication logic on the receiving terminal uses this signature file to confirm the origin and authenticity of the encrypted list of files, VFI.PED.

You must download the entire OS package into Group 1 RAM. If you select a target group other than Group 1, the operation fails.

Before you initiate an OS download, either full or partial, ensure enough memory space is available in Group 1 RAM to temporarily store the OS files and that any application files can also be stored in Group 1.

If you have selected a full OS download in system mode, the terminal restarts automatically and the new OS is processed and replaces the existing OS. In this download operation, all application files stored in Group 1 are automatically erased. If you select a partial OS download, the operating system returns control to system mode after the download completes. To process the new OS, you must manually restart the terminal by selecting the appropriate system mode OMNI 3600 REFERENCE MANUAL 73 PERFORMING DOWNLOADS Omni 3600 Download Differences menu option. In a partial OS download operation, application files stored in Group 1 are not erased.

When you initiate the OS download, the OS file authentication progress displays on the screen as new certificates are authenticated and added to the terminals certificate tree, and as signature files for corresponding OS files are detected and authenticated, as shown in Figure 30, page 71.

While the new OS is being processed, there is no visible indication on the terminal display of progress. When the new OS is processed (this usually takes a few minutes), the terminal restarts automatically and the OS download procedure is complete. CAUTION If the power supply to the receiving terminal is accidentally cycled during an operating system download procedure, the terminal may permanently lock up. In that case, return the terminal to VeriFone for service. File Authentication for Back-to-Back Application Downloads When performing a back-to-back application download between two docked Omni 3600 terminals, the file authentication process on the receiving terminal is similar to an application download from a host computer to a standalone Omni 3600 terminal. There are, however, some important differences to take into account:

Only a full application download is supported for back-to-back data transfers. You cannot perform partial back-to-back application downloads.

Before you can initiate the back-to-back download, you must enter system mode in both terminals, select Group 1 as the target group for both terminals, and enter all required passwords.

All signature files required to authenticate the download application(s) must reside in memory of the sending terminal. They must not be deleted through the *FA variable being cleared to 0 on previous downloads.

Any sponsor and signer certificates downloaded to and authenticated on the sending terminal are stored in the certificate tree of that terminal. When you perform a back-to-back download, certificate files are reconstructed from the data present in the sending units certificate tree.

All certificates transfer to Group 1 RAM on the receiving terminal, except for the highest-level platform root certificate, which can never be transferred to another terminal.

When certificates are detected by the file authentication module of the receiving terminal, they are processed exactly the same as in a direct download: All certificates are checked one by one and, on authentication, are added to the certificate tree of the receiving terminal. Then, all signature files are checked. 74 OMNI 3600 REFERENCE MANUAL PERFORMING DOWNLOADS Omni 3600 Download Differences

Downloaded certificates (receiving terminal) must synchronize with the certificate data present in the certificate tree. Synchronized means the following:

The certificate tree of the receiving terminal can be no more than one revision out-of-sync with the certificate tree on the sending terminal or the files on the receiving terminal do not successfully authenticate. In this case, the term revision refers to any generic change to the current sponsor and signer certificates stored in the certificate tree of a deployment terminal.

When the back-to-back download completes and all certificates and signature files authenticate, the receiving terminal restarts. If the name of the *GO application is specified in the Group 1 CONFIG.SYS file of the receiving terminal, the application executes and the application prompt or logo displays on the terminal. Timing Considerations Due to the Authentication Process The file authentication process takes some time. The total amount of time required depends on a number of factors, including:

the number and size of application files, the number of certificates and signature files, and if you are using the file compression feature of Download Manager to perform the download. Here are a few additional considerations that may affect the total elapsed time required to complete the download operation:

Because additional processing steps are required, an operating system download takes longer to complete than an application download (several minutes as opposed to a few seconds).

The download order of a batch of certificate files may affect total processing time. Digital certificates are validated in a looping process where the validation process cycles as many times as necessary to establish the proper relationship and position of a given certificate in the certificate tree that exists in the terminal. To optimize the authentication process, you can download certificates in a higher-level-certificates-first order. This way, they process faster than a random order download. Optimize Available Memory Space for Successful Downloads One certificate file or signature file requires approximately 400 bytes of memory space. The application designer must account for the extra memory required to download and store these special files. OMNI 3600 REFERENCE MANUAL 75 PERFORMING DOWNLOADS Effect of Downloads on Existing Files and Data When planning your download procedure, carefully consider the total amount of memory space required to store certificates and signature files and the application files. In some cases, a considerable number of 400-byte signature files reside in terminal memory at any given time. Here are some general guidelines to follow:

Know the size of available memory (RAM and flash) of the receiving terminal;

in back-to-back downloads, memory on both the sending and receiving terminal.

Know in advance how application files are redirected to RAM or flash and to file groups other than the target group.

Defragment flash memory before performing a download to optimize the available space in the flash file system.

Before you perform a download, use system mode menu selections to clear the entire RAM and/or flash or the RAM or flash of a specific file group, as necessary to ensure proper use of available memory in the target group. Support for File Compression For information regarding file compression, refer to refer to the Verix Operating System Programmers Manual (VeriFone part number 19733). Effect of Downloads on Existing Files and Data When you download application files and data to an Omni 3600 terminal, an important consideration is the effect of download procedure on existing application files, files used in the file authentication process, and terminal configuration settings stored in CONFIG.SYS files in the receiving terminal. Here are some important points to remember:

If a file already exists in the target file group, the existing file is replaced with the new file of the same name. (Files in separate file groups can have identical names.)

Always download executable files (and any other files to logically protect under VeriShield file authentication) together with the certificates and signature files required to authenticate them.

In full or partial application downloads, all CONFIG.SYS records on the receiving terminal, both protected and non-protected (beginning with * or #), are retained. New CONFIG.SYS variables included in the download package, including the *GO variable, selectively replace existing variables with the same key name in the CONFIG.SYS file of the target group.

All current passwords are retained on the receiving terminal during an application or operating system download (direct, by telephone, and back-to-

back). This includes the system mode password and file group passwords. If required, you can replace existing file group passwords with new values as part of the data transfer operation. NOTE Always modify the system mode password in a separate, securely-controlled operation. 76 OMNI 3600 REFERENCE MANUAL PERFORMING DOWNLOADS Set Up the Download Environment

For back-to-back application downloads, clear the RAM and flash of the receiving terminal before initiating the download. All application files stored on the receiving terminal, including CONFIG.SYS settings, are replaced by those of the sending terminal. System mode and file group passwords are retained on the receiving terminal. For full operating system downloads, Group 1 RAM is cleared as part of the operation and any application files stored in GID1 are erased. In this case, previously downloaded and authenticated applications must be downloaded again in a subsequent operation, together with the certificates and signature files required to authenticate them. Set Up the Download Environment The first step in performing a download to an Omni 3600 terminal is to establish the physical communication link between the sending and receiving system required to support the desired download method:

Direct serial cable connection for direct application and OS downloads. The link is between the COM1 port of a download computer (PC) and the COM1 port on the base station of the docked receiving Omni 3600 terminal, or through the MOD10 adapter (PN 22536-01) directly to a receiving Omni 3600 terminal. Two cables are available from VeriFone to support direct downloads: one for computers with DB25-type serial connectors (PN 26263-02) and another for DB9-type connectors (PN 26264-01). Both of these cables have a 10-pin RJ45 modular plug on one end for the terminal-side connection. The MOD10 adapter allows direct cable connections to an undocked Omni 3600 terminal. Figure 31 shows how to install the MOD10 adapter. Figure 31

Connecting the MOD10 Adapter Telephone line connection for application or OS downloads by telephone. The link is from the modem connection of a host computer to the integrated modem direct in the base station of the docked receiving Omni 3600 terminal. For this type of download operation, a standard telephone line cord with modular Telco connectors is required. OMNI 3600 REFERENCE MANUAL 77 PERFORMING DOWNLOADS Set Up the Download Environment Cable Connection for Direct Downloads

Direct serial cable connection for back-to-back application downloads. The link is between the RS-232 port of the base stations between the docked sending and docked receiving Omni 3600 terminals, or between two Omni 3600 terminals directly connected by cable through two MOD10 adapters. A special cable is required for back-to-back downloads (PN 056051-00). This cable has two 10-pin RJ45 modular plugs on each end to establish the base station-to-base station connection. There are two cables and one adapter for direct downloads:

DB25 serial connector (PN 26263-02)

DB9 connector (PN 26264-01)

MOD10 adapter (PN 22536-01) The following steps describe how to establish the cable link between the sending host computer and the receiving Omni 3600 terminal (see Figure 32):

1 Connect the DIN-type connector on one end of the cable to the COM1 (or COM2) serial I/O port on the download computer. 2 Connect the RJ45 connector on the other end of the download cable to the RS-232 port on the back panel of the base station of the docked Omni 3600 terminal, or to the MOD10 adapter installed in an undocked Omni 3600 terminal (see Figure 33). 78 OMNI 3600 REFERENCE MANUAL PERFORMING DOWNLOADS Set Up the Download Environment HOST COMPUTER FOR DOWNLOADS OR DEBUGGING COM1 OR COM2 SERIAL PORT DOCKED OMNI 3600 TERMINAL OMNI 3600 BASE STATION RS-232 SERIAL PORT Figure 32 Serial Cable Connection for Direct Downloads HOST COMPUTER FOR DOWNLOADS OR DEBUGGING COM1 OR COM2 SERIAL PORT MOD10 ADAPTER RJ45 PORT OMNI 3600 FROM BOTTOM Figure 33 Serial Cable Connection using the MOD10 Adapter OMNI 3600 REFERENCE MANUAL 79 PERFORMING DOWNLOADS Direct Application Downloads Telephone Line Connection for Telephone Downloads To set up the telephone line connection for application or OS downloads between a host computer and a docked Omni 3600 terminal:

1 Confirm proper configuration of the dial-up telephone line and modem connection on the host computer and 2 Confirm the parameters for the download by telephone are set in the download tool. 3 Confirm that the base station of the docked receiving Omni 3600 terminal has a direct telephone line connection. 4 Ensure that the correct keyed variables used to control downloads by telephone are stored in the CONFIG.SYS file of the target file group on the docked receiving terminal. Connections for Back-to-Back Downloads To prepare for a back-to-back application download for docked terminals:

1 Insert the RJ45 modular connector on one end of the download cable

(PN 056051-00) into the RS-232 port of the base station of the docked sending terminal. 2 Insert the RJ45 connector on the other end of the cable into the RS-232 port on the back panel of the base station of the docked receiving terminal. To prepare for a back-to-back application download for terminals using MOD10 adapters:

1 Insert the RJ45 modular connector on either end of the download cable into the port of each MOD10 adapter installed in the two terminals. This section provides procedures for direct downloads.

The cable to connect the download computer serial port (COM1 or COM2) to the RS-232 serial port (COM1) of the base station of the docked Omni 3600 terminal, or The MOD10 adapter and cable to connect the download computer serial port

(COM1 or COM2) directly to the Omni 3600 terminal Direct Application Downloads Hardware Checklist Software Checklist

Download Manager, ZonTalk 2000, or DDL.EXE running on the host computer.

The application file to download (full or partial) resides on host computer. The correct keyed record variables exist in the CONFIG.SYS file(s) of the file group(s) to store the application files. 80 OMNI 3600 REFERENCE MANUAL PERFORMING DOWNLOADS Direct Application Downloads

Certificate files (*.crt) required for file authentication on the docked receiving terminal are stored in memory or they reside on the host computer and download together with the application files.

All required signature files (*.p7s) generated using FILESIGN.EXE, reside on the host computer. One signature file downloads for each executable (*.out or

*.lib) to run on the terminal.

The filenames in the batch download list on the host computer indicate which application files to redirect to flash and file groups other than the target group. To avoid accidental overwrites, ensure that file names and CONFIG.SYS variables to download are correct in relation to those stored in memory of the docked receiving terminal. The required system mode and file group passwords are available to make the system mode menu selections required to prepare the docked receiving terminal to receive the application download.

Sufficient memory space exists in RAM of the target group so that it can accept the entire download package, including certificates, signature files, and all data files.

Use the system mode menu options to clear the entire RAM or flash or specific file groups on the receiving terminal (as necessary). Perform a flash defragment (coalesce) operation to optimize the flash file system (as necessary). (The application itself can issue a function call to defragment the flash on restart after the download.) For more information on system mode operations, refer to Chapter 3. NOTE Download, clear, and defragment operations cannot proceed in system mode if an application is executing. If you see the message DEVICE BUSY, PLEASE RESTART STAND ALONE, press the cancel key and restart the terminal from SYS MODE MENU 1. When you see the VeriFone copyright screen, enter system mode within 3 seconds (before the application starts). Checklist for Effects on Files and Settings in the Receiving Terminal

Protected records in the CONFIG.SYS file(s) of the receiving terminal keyed records that begin with * or # are not erased.

The bootloader, OS, and other firmware on the receiving terminal are not modified as a result of the application download. The certificate tree that exists on the receiving terminal is not modified unless one or more new certificate files are downloading to the terminal. When new certificates are authenticated on the receiving terminal, the data they contain is stored in the certificate tree and the certificate files are deleted from the RAM of the target group. Direct Application Download Procedure The procedure in Table 15 describes how to perform a direct application download from a host download computer into the Group 1 application memory area of a docked Omni 3600 deployment terminal. OMNI 3600 REFERENCE MANUAL 81 PERFORMING DOWNLOADS Direct Application Downloads Steps described in the Action column are performed directly on the docked Omni 3600 terminal. Notes provided in this column indicate and explain actions you must perform on the host computer. NOTE The five steps listed in Table 15 are required for all download and upload procedures. In each of the following procedural tables, step numbering starts at 1 to indicate the unique steps of the specific download method. In subsequent procedures, only the method-specific steps are documented; the five steps in Table 14 are assumed to be completed. Table 14 Common Steps to Start a Download Step Display Action 1 VERIFONE OMNI Q80000XX 01/10/01 K2 *K2*

COPYRIGHT (C) 1997-2003 VERIFONE, INC. ALL RIGHTS RESERVED 2 3

(Application Prompt) or DOWNLOAD NEEDED SYSTEM MODE ENTRY PASSWORD

When the terminal restarts, a copyright screen displays that shows the version of Omni 3600 system firmware stored in the terminals flash EPROM, the date the firmware was loaded into the terminal, and the copyright. This screen displays for three seconds, during which time you can enter system mode by simultaneously pressing F2 and F4. To extend the display period of this screen, press any key during the initial three seconds. Each key press extends the display period an additional three seconds. If an application already exists on the receiving terminal, the application starts and the application prompt displays. Otherwise, the DOWNLOAD NEEDED message displays. To enter system mode, simultaneously press F2 and F4. Enter the system mode password. If an application already resides on the terminal, a unique system mode password may already exist. In this case, type that password and press enter to confirm your entry. If DOWNLOAD NEEDED displayed in step 2, enter the default password, Z66831. To type this password on the keypad, enter: 1 ALPHA ALPHA 6 6 8 3 1, and then press enter. If you enter an incorrect password, the message, PLEASE TRY AGAIN displays. Reenter the password. To correct a typing mistake, press [] to delete the entry, and retype your entry. To end the password entry session and return to the display shown in Step 2, press the cancel key. 82 OMNI 3600 REFERENCE MANUAL PERFORMING DOWNLOADS Direct Application Downloads Table 14 Common Steps to Start a Download (continued) Step Display Action 4 5 SYS MODE MENU 1 CONTRAST F2 CLOCK F3 RESTART F4 SYS MODE MENU 2 DOWNLOAD F2 RAM FILES F3 FLASH FILES F4 When the system mode password is accepted, the terminal enters system mode and SYS MODE MENU 1 displays. To display additional system mode menus, press the PF2 key located on the terminal just below the on-screen down arrow. You can also press the enter key to toggle to the next menu. To perform any type of download operation, press the enter key one time when SYS MODE MENU 1 displays to move to SYS MODE MENU 2. When SYS MODE MENU 2 displays, press F2 to select the DOWNLOAD menu option. To return to SYS MODE MENU 1, press the PF1 key located on the terminal keypad just below the on-screen up arrow. To return to SYS MODE MENU 1 and cancel the download procedure from within SYS MODE MENU 2, press the cancel key. Table 15 Direct Application Download Procedure Step Display Action 1 2 3 4 5 SYS MODE FILE FILE GROUP _1 SYSTEM MODE FILE GROUP _1 PASSWORD

SYS MODE DOWNLOAD FULL F3 PARTIAL F4 SYS MODE DOWNLOAD MODEM F2 COM1 F3 COM2 F4 SYS MODE DOWNLOAD

DOWNLOADING NOW Enter the target file group for the download. File Group _1 (Group 1) displays as the default selection. To select Group 1 as the target file group, press enter; to select a file group other than Group 1, type the one or two-digit number of the desired file group (215) for the download. Enter the password of the selected file group. For example, if Group 1 is the target group, the GROUP_1 PASSWORD message as shown at left displays. To continue, enter the required file group password and press enter to confirm your entry. Select if the download operation is FULL or PARTIAL. To perform a full application download, press F3; to perform a partial download, press F4. To return to SYS MODE MENU 2, press the PF1 key. Select the terminal port to use for the data transfer from the host computer to the docked receiving terminal. (To display additional menu options, press the PF2 key.) For a direct application download, always select the COM1 menu option by pressing F3. When you press F3, the docked terminal is ready to receive the application download from the host computer. To initiate the download, execute the proper command(s) in the download tool running on the host computer. The data transfer operation starts, and the status messages shown at left display on the terminal screen. The progress of the download is indicated by a series of ten asterisks (each asterisk indicates 10% of the download is complete). When the last asterisk displays, the direct download is complete. You can stop the download operation at any time by pressing the cancel key. The terminal restarts automatically. OMNI 3600 REFERENCE MANUAL 83 PERFORMING DOWNLOADS Direct Application Downloads Table 15 Direct Application Download Procedure (continued) Step Display Action 6 7 8

**VERIFYING FILES**

CHECK CERTIFICATE

(FILENAME.CRT)

**AUTHENTIC**

or else

--- FAILED ---

**VERIFYING FILES**

COMPARE SIGNATURE FILENAME.P7S FILENAME.OUT

**AUTHENTIC**

or else

--- FAILED ---

(Application Prompt) or DOWNLOAD NEEDED When the download is complete, the terminal restarts automatically. The file authentication module on the receiving terminal begins to check for new certificate files (*.crt) and signature files (*.p7s) included in the download. These special files then process, one at a time; certificates are processed first, then signature files. When the file authentication module is invoked, the status display informs you of the progress of the file authentication process. If file authentication succeeds for a specific certificate, the AUTHENTIC message displays directly below the certificate filename. If file authentication fails for a specific certificate, the FAILED message displays for five seconds below the filename and the terminal beeps three times, allowing you to note which certificate failed to authenticate. The authentication process then continues to the next certificate until all new certificates are authenticated. The file authentication module proceeds to authenticate any new signature files downloaded with the OS files. When the signature file authentication routine starts, the status display shown at left informs you of the progress of the authentication process. If file authentication succeeds for a specific signature file, the AUTHENTIC message displays directly below the filename of the signature file. If file authentication fails for a specific signature file, the FAILED message displays 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 authenticated, the corresponding application prompt or logo displays on restart. The terminal can now process transactions. The message DOWNLOAD NEEDED appears if:

Note:

The *GO variable is not set.

The application did not authenticate (invalid or missing *.p7s file).

The application uses shared libraries that are missing or were not

*GO does not specify an application is present. authenticated (invalid or missing *.p7s files). Note:

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. You must then repeat the direct download procedure using the correct certificates and/or signature files. 84 OMNI 3600 REFERENCE MANUAL Direct Operating System Downloads Hardware Checklist This section presents procedures for direct downloads. PERFORMING DOWNLOADS Direct Operating System Downloads

The cable to connect the download computer serial port (COM1 or COM2) to the base station of the docked Omni 3600 RS232 serial port (COM1) (refer to Cable Connection for Direct Downloads), or The MOD10 adapter and cable to connect the download computer serial port

(COM1 or COM2) directly to the Omni 3600 terminal. Software Checklist

Download Manager, ZonTalk 2000, or DDL.EXE running on the host computer. The complete OS version to download resides on host computer.

Determine full or partial download of the OS. In a full OS download, the terminal restarts automatically and the new OS is processed, replacing the existing OS. In a partial OS download, the terminal returns to system mode and the new OS does not process until you manually initiate a terminal restart from system mode. The correct keyed record variables for the download exist in the CONFIG.SYS files of Group 1. (OS files must always download into GID1 RAM). The required variables can also be written into the CONFIG.SYS file as part of the download operation. The following files, provided by VeriFone CA for full OS downloads, must reside on the host computer:

A signature file, called VFI.P7S, for the OS update. This signature file is The new OS version or OS update (Q*.out, 1*.out, 2*.out). generated by VeriFone CA using the high-level OS certificates for the Omni 3600 platform.

A file called VFI.PED. This file is an encrypted list of the new OS files.

One or more digital certificates (*.crt) download with the OS update. All new OS files, including VFI.P7S, VFI.PED, all certificate files, and any other files in the download package provided by VeriFone CA, must download together into Group 1 RAM. The required system mode and file group passwords are available to make the system mode menu selections required to prepare the receiving terminal to receive the OS download.

Sufficient memory space exists in the Group 1 RAM to accept the OS download package including certificates, signature files, and all data files. OMNI 3600 REFERENCE MANUAL 85 PERFORMING DOWNLOADS Direct Operating System Downloads

Use system mode menu options to clear the entire RAM or the RAM of Group 1 on the receiving terminal (as necessary). NOTE Download, clear, and defragment operations cannot proceed in system mode if an application is executing. If you see the message DEVICE BUSY, PLEASE RESTART STAND ALONE, press the cancel key and restart the terminal from SYS MODE MENU 1. When you see the copyright screen, enter system mode within three seconds

(before the application begins). Checklist for Effects on Files and Settings in the Receiving Terminal

A full OS download replaces the existing OS and erases all application files from the Group 1 RAM.

A partial OS download returns control of the terminal to system mode and does not erase application files from Group 1 RAM.

Protected records in the CONFIG.SYS file(s) of the receiving terminal keyed records that begin with * or # are not erased.

An OS download does not overwrite terminal configuration settings, including the current date and time, passwords, and modem country code. If required, you can download new terminal configuration settings together with the OS files.

The certificate tree that exists on the receiving terminal is not modified unless one or more new certificate files required to authenticate the new OS are being downloaded to the terminal. When new certificates are authenticated on the receiving terminal, the data they contain is stored in the certificate tree and the certificate files are deleted from the Group 1 RAM. The certificates and signature files required to authenticate the new OS are processed by the file authentication module of the receiving terminal the same as application files.

When the terminal restarts and the new OS files are processed, they are moved out of the Group 1 RAM into the Group 0 area of the Omni 3600 file system. Direct Operating System Download Procedure The procedure in Table 16 describes how to perform a direct operating system download from a host computer into the Group 1 RAM of a docked Omni 3600 terminal. Steps are performed directly on the Omni 3600 terminal. Notes provided in the Action column indicate actions to perform on the download computer side of the data transfer. NOTE In Table 16 and in the following procedures, only method-specific steps are included. For a description of the first five steps required to enter system mode and display SYS MODE MENU 2, please refer to Table 14. 86 OMNI 3600 REFERENCE MANUAL PERFORMING DOWNLOADS Direct Operating System Downloads Table 16 Direct Operating System Download Procedure Step Display Action 1 2 3 4 5 6 SYS MODE FILE FILE GROUP _1 SYSTEM MODE FILE GROUP _1 PASSWORD

SYS MODE DOWNLOAD FULL F3 PARTIAL F4 SYS MODE DOWNLOAD MODEM F2 COM1 F3 COM2 F4 SYS MODE DOWNLOAD

DOWNLOADING NOW

**VERIFYING FILES**

CHECK CERTIFICATE

(FILENAME.CRT)

**AUTHENTIC**

or else

--- FAILED ---

Enter the target file group for the download. File Group _1 (Group 1) is the default. Operating system files must always download into Group 1. This is the default group number in system mode. To select Group 1 as the target file group, press enter. Enter the password of the selected file group (Group 1) and press enter to confirm your entry. Select the OS download operation: FULL or PARTIAL. To perform a full OS download, press F3; to perform a partial OS download, press F4. To return to the previous system mode menu, press PF1. Select the terminal port to use for the data transfer from the host computer to the docked receiving terminal. (To display additional menu options, press PF2.) For a direct OS download, always select the COM1 menu option by pressing F3. When you press F3, the terminal is ready to receive the OS download from the host computer. Initiate the download by executing the proper command(s) in the download tool running on the host computer (when the receiving terminal is prepared to receive the direct OS download). The data transfer operation starts and status messages display on the terminal screen. The progress of the download is indicated by a series of ten asterisks (each asterisk indicates 10% of the download has completed). When the last asterisk displays, the direct download is complete. To stop the download operation, press the cancel key. The terminal restarts automatically. When the OS download is complete, the terminal restarts automatically. The file authentication module on the receiving terminal then checks for new certificate (*.crt) and signature (*.p7s) files included in the download. It processes these special files one at a time; certificates are processed first, then signature files. When the file authentication module is invoked, the progress of the file authentication process displays. If file authentication succeeds for a specific certificate, the AUTHENTIC message displays directly below the certificate filename. If file authentication fails for a specific certificate, the FAILED message displays for five seconds below the filename and the terminal beeps three times, allowing you to note which certificate failed to authenticate. The authentication process then continues to the next certificate until all new certificates are checked. OMNI 3600 REFERENCE MANUAL 87 PERFORMING DOWNLOADS Download by Telephone Table 16 Direct Operating System Download Procedure (continued) Step Display Action 7

**VERIFYING FILES**

COMPARE SIGNATURE FILENAME.P7S FILENAME.OUT

**AUTHENTIC**

or else

--- FAILED ---

8

(Application Prompt) or DOWNLOAD NEEDED The file authentication module proceeds to authenticate new signature files downloaded with the OS files. When the signature file authentication routine begins, the progress of the authentication process displays. If file authentication succeeds for a specific signature file, the AUTHENTIC message displays directly below the filename of the signature file. If file authentication fails for a specific signature file, the FAILED message displays 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 proceeds to the next signature file until all signature files are validated. When file authentication is complete, the terminal either restarts automatically and begins processing the new OS

(full download) or it returns control to system mode (partial download). If you are performing a partial download, the terminal does not restart until manually initiated by pressing F4 in SYS MODE MENU 1. If an application resides on the terminal following the OS download, it executes and starts running on restart. Note:

Because a full OS download clears the RAM, all terminal applications and related certificate and signature files must download to the terminal when performing this type of download. If you performed a full OS download, the DOWNLOAD NEEDED prompt displays. At this point, you can perform a direct application download on the receiving terminal. If you performed a partial OS download and manually restarted the terminal, the application residing in the terminal (if any) executes. The application prompt displays on terminal restart, after OS processing, and the application starts running. Download by Telephone The procedure to perform an application or OS download by telephone is similar to that of direct application (see Table 15) and direct operating system downloads

(see Table 16). Hardware Checklist

Set up the dial-up telephone line and modem connection on the host computer.

Set up the direct telephone line connection on the docked receiving Omni 3600 terminal, as described in Telephone Line Connections, page 28. Software Checklist

Download Manager or ZonTalk 2000 installed and running on the host computer. (DDL.EXE can only be used for direct downloads.)

The information required to control the download by telephone is stored in the CONFIG.SYS file of the target group selected on the receiving terminal. Required settings for Download Manager and ZonTalk 2000 may include the following:

Dial-up numbers used to established the telephone line connection 88 OMNI 3600 REFERENCE MANUAL PERFORMING DOWNLOADS Download by Telephone Terminal ID

Baud rate settings for the data transfer

Application ID

Operating system name or serial number NOTE For detailed information about the setup requirements and download procedures for Download Manager and ZonTalk 2000, please refer to the user documentation supplied by VeriFone with these software products. Telephone Downloads Procedure Press F2 (step 4 in Table 17) to select the MODEM port on the receiving terminal when the port selection options display (SYS MODE MENU 2). When you press F2, the internal modem in the base station of the receiving Omni 3600 terminal dials the host computer to request the download. When the host computer accepts the call, the download procedure is initiated by the host. Table 17 Download by Telephone Procedure Step Display Action 1 2 3 4 5 SYS MODE FILE FILE GROUP _1 SYSTEM MODE FILE GROUP _1 PASSWORD

SYS MODE DOWNLOAD FULL F3 PARTIAL F4 SYS MODE DOWNLOAD MODEM F2 COM1 F3 COM2 F4 SYS MODE DOWNLOAD

DOWNLOADING NOW Enter the target file group for the download. File Group _1 (Group 1) is the default. Operating system files must always download into Group 1. This is the default group number in system mode. To select Group 1 as the target file group, press enter. Enter the password of the selected file group (Group 1) and press enter to confirm your entry. Select the OS download operation: FULL or PARTIAL. To perform a full OS download, press F3; to perform a partial OS download, press F4. To return to the previous system mode menu, press PF1. Select the terminal port to use for the data transfer from the host computer to the docked receiving terminal. (To display additional menu options, press PF2.) For a download by telephone, you must select the MODEM F2 menu option. When you press F2, the docked terminal can receive the download from the host computer over the Telco port telephone line connection. Initiate the download by executing the proper command(s) in the download tool running on the host computer. The data transfer operation then starts, and status messages display on the terminal screen. The progress of the download is indicated by a series of ten asterisks (each asterisk represents 10% of the completed download). When the last asterisk displays, the direct download is complete. You can stop the download operation by pressing the cancel key. The terminal restarts automatically. OMNI 3600 REFERENCE MANUAL 89 PERFORMING DOWNLOADS Download by Telephone Table 17 Download by Telephone Procedure (continued) Step Display Action 6

**VERIFYING FILES**

CHECK CERTIFICATE

(FILENAME.CRT)

**AUTHENTIC**

or else

--- FAILED ---

7

**VERIFYING FILES**

COMPARE SIGNATURE FILENAME.P7S FILENAME.OUT

**AUTHENTIC**

or else

--- FAILED ---

8

(Application Prompt) or DOWNLOAD NEEDED When the OS download is complete, the terminal restarts automatically. The file authentication module on the receiving terminal then checks for new certificate (*.crt) and signature (*.p7s) files included in the download. It processes these special files one at a time; certificates are processed first, then signature files. When the file authentication module is invoked, the progress of the file authentication process displays. If file authentication succeeds for a specific certificate, the AUTHENTIC message displays directly below the certificate filename. If file authentication fails for a specific certificate, the FAILED message displays for five seconds below the filename and the terminal beeps three times, allowing you to note which certificate failed to authenticate. The authentication process then continues to the next certificate until all new certificates are checked. The file authentication module proceeds to authenticate new signature files downloaded with the OS files. When the signature file authentication routine begins, the progress of the authentication process displays. If file authentication succeeds for a specific signature file, the AUTHENTIC message displays directly below the filename of the signature file. If file authentication fails for a specific signature file, the FAILED message displays 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 proceeds to the next signature file until all signature files are validated. When file authentication is complete, the terminal either restarts automatically and begins processing the new OS

(full download) or it returns control to system mode (partial download). If you are performing a partial download, the terminal does not restart until manually initiated by pressing F4 in SYS MODE MENU 1. If an application resides on the terminal following the OS download, it executes and starts running on restart. Note:

Because a full OS download clears the RAM, all terminal applications and related certificate and signature files must download to the terminal when performing this type of download. If you performed a full OS download, the DOWNLOAD NEEDED prompt displays. At this point, you can perform a direct application download on the receiving terminal. If you performed a partial OS download and manually restarted the terminal, the application residing in the terminal (if any) executes. The application prompt displays on terminal restart, after OS processing, and the application starts running. 90 OMNI 3600 REFERENCE MANUAL Back-to-Back Application Downloads Hardware Checklist PERFORMING DOWNLOADS Back-to-Back Application Downloads This section presents procedures for back-to-back terminal downloads.

The correct serial cable connects the RS-232 ports of the base stations of the docked sending and receiving Omni 3600 terminals (refer to Connections for Back-to-Back Downloads), or The MOD10 adapter and cable to connect the download computer serial port

(COM1 or COM2) directly between the two Omni 3600 terminals.

Verify the RAM size on the receiving terminal is large enough to receive files uploaded from the sending terminal. If the RAM on the sending terminal is 512 KB, the RAM on the receiving terminal must be at least 512 KB. Software Checklist

The firmware version of the sending and receiving terminals must be identical or very similar.

One or more complete, authenticated, application programs are stored in GIDs 1-15, RAM or flash, of the sending terminal. In this type of operation, all files stored in application memory of the sending terminal download to the receiving terminal.

Before you initiate the download procedure, remember to select Group 1 as the target file group on both the sending and receiving terminals. The required system mode and file group passwords must also be available to make the required system mode menu selections on both terminals.

The current CONFIG.SYS variables, date and time, and other terminal configuration settings on the sending terminal are those downloaded to the receiving terminal. Ensure your desired settings.

All signature files required to authenticate the application files being downloaded to the receiving terminal are present in the RAM or flash file system of the sending terminal.

The certificate tree of the sending and receiving terminal must be synchronized. That is, there can be no more than one revision difference between the certificate data currently stored in the memory of the sending and receiving terminals. If application files are downloaded to the receiving terminal in previous operations, use system mode menu options to clear the RAM and flash file systems of the receiving terminal before you initiate the back-to-back download procedure. This ensures a clean download. OMNI 3600 REFERENCE MANUAL 91 PERFORMING DOWNLOADS Back-to-Back Application Downloads NOTE Download, clear, and defragment operations cannot proceed in system mode if an application has already started. If you see the message DEVICE BUSY, PLEASE RESTART STAND ALONE, press the Cancel (

from system mode Menu 1. When you see the copyright notice screen, enter system mode within three seconds (before the application begins).

) key and then restart the terminal Checklist for Effects on Files and Settings in the Receiving Terminal

A back-to-back application download overwrites existing applications, libraries, or any other files stored in RAM of the receiving terminal.

All CONFIG.SYS records and settings on the receiving terminalprotected and non-protectedare replaced with those of the sending terminal. Ensure that these are correct on the sending terminal before initiating the download.

Passwords on the receiving terminal are retained.

Certificates and signature files downloaded to the receiving terminal together with application files must be processed by the file authentication module on the receiving terminal on terminal restart after the back-to-back download.

The OS software on the receiving terminal is not affected by a back-to-back application download. (OS files cannot be downloaded in a back-to-back operation.)

An application upload does not overwrite the existing certificate tree on the receiving terminal. Any downloaded certificate files are authenticated and then added to the tree. Back-to-Back Application Download Procedure The back-to-back application download process consists of two main phases:

1 Preparing a Gold Omni 3600 terminal (transfers application files to the Target Omni 3600 terminal). 2 Downloading application files from the Gold terminal to a properly configured Target terminal. Prepare Gold Terminal (PC-to-Terminal) 1 Configure a PC for an application download operation to the Gold terminal:

Set the *FA variable (if present in the application) to 1.

Ensure all certificates, *p7s files, applications, and other required files are present.

Ensure the download is exactly what you want your Target terminals to receive. 2 Configure the Gold terminal to receive an application download from a PC:

From SYS MODE MENU 2, set Group 1 and the COM1 port to receive the download. 3 Connect a cable between the RS-232 serial ports of the PC and the base station of the docked Gold terminal, or to a MOD10-equipped Gold terminal. 92 OMNI 3600 REFERENCE MANUAL PERFORMING DOWNLOADS Back-to-Back Application Downloads 4 Initiate the file transfer on the PC. 5 From SYS MODE MENU 2 on the Gold terminal, select either a full or a partial download. The PC transfers files to the Gold terminal. Download Application Files to Target Terminal 1 Configure a Gold terminal for an application download operation to a deployment terminal:

If the *FA variable (if present in the application) is set to 1, you can reset it to 0. For more information on the *FA variable, refer to the Verix Programmers Manual (PN 19733).

Ensure the download is exactly what you want your Target terminals to receive.

Ensure that previously authenticated files are not changed prior to the file transfer operation. 2 Configure the docked Target terminal to receive an application download from the Gold terminal:

From SYS MODE MENU 2, set Group 1 and the COM1 port to receive the file transfer. 3 Connect a cable between the RS-232 serial ports of the base stations of the docked Gold and Target terminals, or between the MOD10-equipped Gold and Target terminals. 4 From any system mode menu on the Gold terminal, press [*] and enter the GID1 password to initiate the file transfer. 5 From SYS MODE MENU 2 on the deployment terminal, select either a full or a partial download. The Gold terminal begins to transfer files to the Target terminal. Figure 34 illustrates these two phases and how they relate to each other. OMNI 3600 REFERENCE MANUAL 93 PERFORMING DOWNLOADS Back-to-Back Application Downloads Back-To-Back Download Process Figure 34 The procedure in Table 18 steps you through a back-to-back application download from a docked sending Omni 3600 terminal (Gold) to a docked receiving Omni 3600 terminal (Target). Back-to-back downloads require that one terminal, the Gold terminal, be loaded with the required applications. The receiving terminal is the Target terminal. The procedure in Table 18 assumes the following:

The Target terminal has no applications loaded. 94 OMNI 3600 REFERENCE MANUAL PERFORMING DOWNLOADS Back-to-Back Application Downloads

There is enough memory in the Target terminal to complete the download. NOTE The Target terminal does not display an error message if there is not enough memory to complete the download. However, the Gold terminal displays DOWNLOAD INCOMPLETE before returning to SYS MODE MENU 2. Table 18

You are performing a full download. Back-to-Back Application Download Procedure Step Gold Terminal Target Terminal 1 2 3 4 5 6 7 8 Connect a MOD10 cable (P/N 05651-XX) between the RS-232 ports of the base stations. Dock each terminal and allow each terminal to boot up. After boot up, the Target terminal displays DOWNLOAD NEEDED. Press F2+F4 to enter system mode. Enter system mode password (factory default is 1 ALPHA ALPHA 6 6 8 3 1a) and press the enter key. Press the key (PF2) to access the SYS MODE MENU 2 screen. Press the * (asterisk) key and press the Enter []

key. You are prompted to reenter the system mode password. UPLOADING NOW displays. Press F2, DOWNLOAD, to enter download mode. Press enter key at the next SYS MODE DOWNLOAD screen to select FILE GROUP_1 (default displayed) as the target file group. Press F3, FULL, at the next SYS MODE DOWNLOAD screen. Full downloads are required in back-to-back downloads. Select F3 (COM1) at next SYS MODE DOWNLOAD screen. DOWNLOADING NOW displays. Both terminals display a status indicator, where each dash represents a 10% increment of the download. Ensure that the Gold terminal displays UPLOAD COMPLETE before returning to SYS MODE MENU 2. This is when the Gold terminal might display an error message if problems occurred during the download process. The Target terminal begins to validate all files loaded. Allow the Target terminal to complete file authentication and reboot the terminal. The Gold terminal is ready to perform another download. An application-specific menu displays after the Target terminal completes the reboot. a. Z66831; 1 ALPHA ALPHA = the character, Z. OMNI 3600 REFERENCE MANUAL 95 PERFORMING DOWNLOADS Back-to-Back Application Downloads 96 OMNI 3600 REFERENCE MANUAL CHAPTER 5 File Authentication This chapter:

Introduction to File Authentication

introduces the file authentication module of the VeriShield security architecture, and the organizational infrastructure that supports this feature. explains how the file authentication process may affect the tasks normally performed by application programmers, terminal deployers, site administrators, or by entities authorized to download files to an Omni 3600 terminal. describes how to use the file signing utility, FILESIGN.EXE, to generate the signature files that are required to perform downloads and authenticate files on the Omni 3600 terminal. In Chapter 4, the topic of file authentication is also discussed in the context of specific file download procedures. The Omni 3600 terminal has a new type of security architecture, developed by VeriFone. This architecture, called VeriShield, has both physical and logical components. The logical security component of the VeriShield architecture, which is part of the terminals operating system software, is called the file authentication module, or simply, file authentication. File authentication is a secured process for authenticating files using digital signatures, cryptographic keys, and digital certificates. This process makes it possible for the sponsor of an Omni 3600 terminal to logically secure access to the terminal by controlling who is authorized to download application files to that terminal. It proves and verifies the

files origin senders identity integrity of the files information The VeriFone Certificate Authority To manage the tools and processes related to the file authentication module of the VeriShield security architecture, VeriFone has established a centralized VeriFone Certificate Authority, or VeriFone CA. This agency is responsible for managing keys and certificates. The VeriFone CA uses an integrated set of software tools to generate and distribute digital certificates and private cryptographic keys to customers who purchase Omni 3600 terminals. OMNI 3600 REFERENCE MANUAL 97 FILE AUTHENTICATION Introduction to File Authentication Special Files Used in the File Authentication Process The following specially formatted files support the file authentication process:

A digital certificate is a digital, public document used to verify the signature of a file.

A digital signature is a piece of information based on both the file and the signers private cryptographic key. The file sender digitally signs the file using a private key. The file receiver uses a digital certificate to verify the senders digital signature.

Signer private keys (*.key files) are securely conveyed to clients on smart cards. The secret passwords required by clients to generate signature files, using signer private keys, are sent as PINs over a separate channel such as registered mail or encrypted e-mail. Some files, such as private key files, are encrypted and password-protected for data security. Others, such as digital certificates and signature files, do not need to be kept secure to safeguard the overall security of VeriShield. Within the FILESIGN.EXE tool, you can recognize the special file types that support the file authentication process by their filename extensions:

File Type Signature Private key Digital certificate Extension

*.p7s

*.key

*.crt All digital certificates are generated and managed by the VeriFone CA, and are distributed on request to Omni 3600 clients either internally within VeriFone or externally to sponsors. All certificates that are issued by the VeriFone CA for the Omni 3600 platform, and for any VeriFone platform with the VeriShield security architecture, are hierarchically related. That is, a lower-level certificate can only be authenticated under the authority of a higher-level certificate. The security of the highest-level certificate, called the platform root certificate, is tightly controlled by VeriFone. The required cryptographically-related private keys that support the file authentication process are also generated and distributed by the VeriFone CA. Certificates Contain Keys That Authenticate Signature Files

Sponsor certificate: Certifies a clients sponsorship of the terminal. It does not, however, convey the right to sign and authenticate files. To add flexibility to the business relationships that are logically secured under the file authentication process, a second type of certificate is usually required to sign files. A sponsor certificate is authenticated under a higher-level system certificate, called the application partition certificate. 98 OMNI 3600 REFERENCE MANUAL FILE AUTHENTICATION Introduction to File Authentication NOTE Only one sponsor certificate is permitted per terminal.

Signer certificate: Certifies the right to sign and authenticate files for terminals belonging to the sponsor. A signer certificate is authenticated under the authority of a higher-level client certificate (the sponsor certificate). The required sponsor and signer certificates must either have been previously downloaded and authenticated on the terminal, or they must be downloaded together with the new signature files and target files for them to authenticate. Signer Private Keys Are Issued to Secure the File Signing Process Signer private keys are loaded onto a smart card. This smart card is securely delivered to the business entity that the terminal sponsor has authorized to sign, download, and authenticate applications to run on the sponsors terminal. The VeriFone CA can also issue additional sets of sponsor and signer certificates, and signer private keys to support multiple sponsors and multiple signers for a specific platform. To establish the logical security of applications to download to an Omni 3600 terminal, the designated signer uses the signer private key issued them by the VeriFone CA as a required input to the file signing tool, FILESIGN.EXE. Every signature file contains information about the signer private key used to sign it. When a signature file generated using a signer private key downloads to the Omni 3600 terminal, if it is successfully authenticated depends on whether the signer private key used to sign the target file matches the signer certificate stored in the terminals certificate tree. File authentication consists of three basic processes:

1 Development: The file signing software tool FILESIGN.EXE creates a signature file for each application file to authenticate. 2 Pre-deployment: An optimal certificate structure is determined, and the necessary certificates and keys created. 3 Deployment: The development and pre-deployment processes, once complete, are used in combination to prepare a terminal for deployment. Development Process In this process:

1 The application developer creates an application file. 2 The developer assigns a name to the application file. OMNI 3600 REFERENCE MANUAL 99 How File Authentication Works FILE AUTHENTICATION Introduction to File Authentication 3 The application file becomes a required input for the FILESIGN.EXE tool

(included in the SDK). 4 The default certificate (K2SIGN.CRT) and default key (K2SIGN.KEY) included in the SDK are inputs for the FILESIGN.EXE tool. 5 Using the application file, default certificate, and default key, FILESIGN.EXE creates a signature file (*.p7s). 6 The signature file and the original application file are loaded into a development terminal, where the following actions occur:

a The terminals operating system searches for signature files. b When a signature file is found, the operating system then searches for a matching application file. c When a matching application file is found, the operating system compares the signature files signature against the values stored in the application files calculated signature. d If these values match, the two files are authenticated, and the ATTR_NOT_AUTH bit is set to 0. 7 The application file is tested and debugged. 8 After the application file is fully debugged, it becomes an input for the deployment process. Figure 35 illustrates the development process. 100 OMNI 3600 REFERENCE MANUAL

 

 

FILE AUTHENTICATION Introduction to File Authentication Figure 35 The Development Process Pre-Deployment Process In this process:

1 A sponsor goes to the VeriFone CA Web site and requests certificates for deployment terminals. 2 Based on information provided by the sponsor through the VeriFone CA Web site, the VeriFone CA determines the required certificate structure. 3 VeriFone CA generates the following items for the sponsor:

a Smart card containing a set of certificates and keys. b Smart card PIN. 4 VeriFone CA sends the smart card and smart card PIN to the sponsor. 5 The sponsor uses the smart card and smart card PIN as inputs for the deployment process. OMNI 3600 REFERENCE MANUAL 101 FILE AUTHENTICATION Introduction to File Authentication Refer to Figure 36 illustrates the pre-deployment process. Figure 36 The Pre-Deployment Process Deployment Process In this process:

1 The sponsor provides the application file (from the development process) and the smart card and smart card PIN (from the pre-deployment process) as inputs to VeriShield. 2 VeriShield extracts the signer key, signer certificate, and sponsor certificate from the smart card. 3 VeriShield uses the extracted data, along with the application file, to create a signature file (*.p7s). 4 VeriShield creates files suitable for downloading from the extracted smart card data. 5 The signature file, the application file, and the extracted signer and sponsor certificates are downloaded into a deployment terminal, where the following actions occur:

a The terminals operating system searches for signature files. b If a signature file is found, the operating system then searches for a matching application file. 102 OMNI 3600 REFERENCE MANUAL FILE AUTHENTICATION Introduction to File Authentication c If a matching application file is found, the operating system compares the signature files signature against the values stored in the application files calculated signature. d If the values match, the two files are authenticated and the ATTR_NOT_AUTH bit is set to 0. 6 Each successfully authenticated executable application file is allowed to run on the terminal (otherwise, the executable remains stored in the terminal memory but is not allowed to run). Figure 37 illustrates the deployment process. OMNI 3600 REFERENCE MANUAL 103 FILE AUTHENTICATION Introduction to File Authentication Figure 37 The Deployment Process Planning for File Authentication File authentication is an integral part of every Omni 3600 terminal. To safeguard the terminals logical security, the file authentication module requires that any executable code file must be successfully authenticated before the operating system allows it to execute on the terminal. 104 OMNI 3600 REFERENCE MANUAL FILE AUTHENTICATION Introduction to File Authentication Authentication Requirements for Specific File Types For the purposes of file authentication, executable code files include two file types that can be recognized by their filename extensions:

File Type Extension Compiled and linked application files Global function libraries

*.out

*.lib Depending on the logical security requirements of specific applications, other types of files used by an application (that is, non-executable files) also need to be authenticated:

Data files (*.dat) that contain sensitive customer information or other data that needs to be secure

Font files (*.vft or *.fon) that may need to be secure to prevent unauthorized text or messages from being displayed on the terminal screen

Any other type of file used by an application and that the application designer wishes to logically secure using file authentication requirements Decide Which Files to Authenticate in a Specific Application The first step in the file authentication process is to determine which files must be authenticated for an application to meet its design specifications for logical security under the VeriShield security architecture. In most cases, application designers make these decisions based on specifications provided by the terminal sponsor. Which files to authenticate can be completely transparent to the person or business entity responsible for signing, downloading, and authenticating an application prior to deployment. How (and When) Signature Files Authenticate Their Target Files Signature files are usually downloaded together with their target application files in the same data transfer operation. This recommended practice lets you specify and confirm the logical security status of the Omni 3600 terminal each time you perform an application download. When the file authentication module detects a new signature file after a terminal restart, it locates and attempts to authenticate the target file that corresponds to the new signature file. It is not mandatory to always download a signature file at the same time as its target application file. For example, you can download the corresponding signature file in a separate operation. A non-authenticated application can reside in the terminal memory, but is not authenticated or allowed to run on the terminal until the signature files for the application executable files are processed by the file authentication module after a subsequent download procedure and terminal restart. OMNI 3600 REFERENCE MANUAL 105 FILE AUTHENTICATION Introduction to File Authentication Determine Successful Authentication To ensure the Omni 3600 terminals logical security, never assume that a target file was authenticated simply because it downloaded to the Omni 3600 terminal together with its signature file. There are several ways to ensure a target file successfully authenticated after a download:

Confirm all downloaded executable files run. If an executable code file is not successfully authenticated, the operating system does not allow it to execute and run, either following the initial download or on subsequent terminal restarts. The effect of this rule depends on whether or not all executable files successfully authenticated:

If the executable file that failed to authenticate is the main application

(*.out) specified in the CONFIG.SYS *GO variable, the main application is not allowed to run.

If the executable that failed to authenticate is a secondary executable

(*.out) or shared library (*.lib) used by the main application, the CONFIG.SYS *GO application executes and runs until it issues a function call to that library. When the main application attempts to access a non-

authenticated executable, the main application may crash.

Visually (and audibly) confirm file authentication during the process. When the file authentication module is invoked at terminal restart and detects a new signature file, it displays status information on screen indicating success or failure of the authentication of each target file based on its corresponding signature file. (A similar status display also appears on screen when you download digital certificates.) You can watch the screen display following the download to see if a specific target file fails to be authenticated. If this happens, FAILED displays on screen for five seconds below the filenames of the target and signature files, and the terminal beeps as an alert. An application program can issue a function call to read the ATTR_NOT_AUTH bits current value for all relevant files to verify that were successfully authenticated. If the ATTR_NOT_AUTH bits binary value is 1, the file did not authenticate; if 0, the file did authenticate. For non-executable files, it is the applications responsibility to confirm that all of the files it uses successfully authenticated on download completion, and when the application executes the first time following a restart. NOTE Because the application is responsible for verifying data files and prompt files, it is recommended that each application check the ATTR_NOT_AUTH bit of all relevant files on restart. 106 OMNI 3600 REFERENCE MANUAL FILE AUTHENTICATION Introduction to File Authentication NOTE Each successfully authenticated file is also write-protected. That is, the files read-

only attribute is set. If the read-only file is removed or if the file is modified in any way while stored in the terminal, the ATTR_NOT_AUTH bit is automatically set to 1. If the modified file is an executable, it is no longer allowed to run. Digital Certificates and the File Authentication Process The file authentication module always processes certificates before it processes signature files. Digital certificates (*.crt files) generated by the VeriFone CA have two important functions in the file authentication process:

They define the rules for file location and usage (for example, the valid file group, replaceable *.crt files, parent *.crt files, whether child *.crt files can exist, and so on). They convey the public cryptographic keys generated for terminal sponsors and signers that are the required inputs to the file signing tool, FILESIGN.EXE, to verify file signatures. Hierarchical Relationships Between Certificates All digital certificates are hierarchically related to one another. Under the rules of the certificate hierarchy managed by the VeriFone CA, a lower-level certificate must always be authenticated under the authority of a higher-level certificate. This rule ensures the overall security of VeriShield. To manage hierarchical relationships between certificates, certificate data is stored in terminal memory in a special structure called a certificate tree. New certificates are authenticated based on data stored in the current certificate tree. The data from up to 21 individual related certificates (including root, OS, and other VeriFone-owned certificates) can be stored concurrently in a certificate tree. This means that a new certificate can only be authenticated under a higher-level certificate already resident in the terminals certificate tree. This requirement can be met in two ways:

The higher-level certificate may have already been downloaded to the terminal in a previous or separate operation. The higher-level certificate can be downloaded together with the new certificate as part of the same data transfer operation. A development set of higher-level certificates is downloaded into each Omni 3600 terminal at manufacture. When you take a new Omni 3600 terminal out of its shipping carton, certificate data is already stored in the terminals certificate tree. In this just-out-of-the-box condition, the Omni 3600 terminal is called a development terminal. Typically, a sponsor requests an additional set of digital certificates from the VeriFone CA to establish sponsor and signer privileges. This additional set of certificates are then downloaded to the Omni 3600 terminal when the terminal is being prepared for deployment. When this procedure is complete, the Omni 3600 terminal is called a deployment terminal. OMNI 3600 REFERENCE MANUAL 107 FILE AUTHENTICATION Introduction to File Authentication Add New Certificates When you add a new certificate file to an Omni 3600 terminal, the file authentication module detects it by filename extension (*.crt). On restart, the terminal then attempts to authenticate the certificate under the authority of the resident higher-level certificate stored in the terminals certificate tree or one being downloaded with the new certificate. In a batch download containing multiple certificates, each lower-level certificate must be authenticated under an already-authenticated, higher-level certificate. Whether or not the data a new certificate contains is added to the terminals certificate tree depends on if it is successfully authenticated. The following points explain how certificates are processed:

If a new certificate is successfully authenticated, the information it contains is automatically stored in the terminals certificate tree. The corresponding certificate file (*.crt) is then deleted from that file groups RAM. If the relationship between the new certificate and an existing higher-level certificate cannot be verified, the authentication procedure for the new certificate fails. In this case, the certificate information is not added to the certificate tree and the failed certificate file (usually ~400 bytes) is retained in application memory. Development Terminals A development terminal is an Omni 3600 terminal still maintaining the original factory set of certificates in its certificate tree. This set of certificates includes several higher-level system certificates and a special client certificate called a default signer certificate (see Figure 38). In the development terminal, the level of logical security provided by the file authentication module is minimal, even though applications must still be signed and authenticated before they can run on the terminal. In most application development and test environments, tight security is not required, and the flexibility offered by the Omni 3600 development terminal is more important. NOTE With the factory set of certificates stored in the terminal memory, anyone who has the Omni 3600 SDK and included file signing tool, FILESIGN.EXE, can generate valid signature files for downloading and authenticating files on the Omni 3600 platform. Deployment Terminals While the application development process is being completed and while the new application is being tested on a development terminal, a sponsor can order specific sponsor and signer certificates from the VeriFone CA to use to logically secure sponsor and signer privileges when the Omni 3600 terminal is prepared for deployment. 108 OMNI 3600 REFERENCE MANUAL FILE AUTHENTICATION Introduction to File Authentication Customer-specific sponsor and signer certificates are usually downloaded to an Omni 3600 terminal as part of the standard application download procedure performed by a deployment service. In this operation, the new sponsor and signer certificates replace the development sponsor certificate that is part of the factory set of certificates, as shown in Figure 38. When the sponsor and signer certificates are downloaded and successfully authenticated, the terminal is ready to deploy. Ultimately, it is the sponsors decision how to implement the logical security provided by file authentication on a field-deployed terminal. Additional certificates can be obtained from the VeriFone CA any time, to implement new sponsor and signer relationships in deployment terminals. Figure 38 Certificate Trees in Development and Deployment Terminals Permanency of the Certificate Tree The data contained in a digital certificate is stored in the terminals certificate tree when the certificate is authenticated, and the certificate file itself is erased from RAM. The certificate tree file is stored in a reserved area of non-volatile memory and is therefore relatively permanent. New certificate data can be added to the existing certificate tree (up to a maximum of 21 certificates). OMNI 3600 REFERENCE MANUAL 109 FILE AUTHENTICATION Introduction to File Authentication Required Inputs to the File Signing Process The required inputs to the file signing process are somewhat different for development terminals than deployment terminals. The significant differences shown in Table 19. Table 19 Differences Between Required Inputs Development Terminals Deployment Terminals Manufacturing inputs to the file signing process are included, together with the file signing tool, FILESIGN.EXE, in the Omni 3600 SDK. These inputs make it possible for anyone who has the Omni 3600 SDK to sign and authenticate files. The following two factory inputs are required for the file signing process, in addition to the application files you want to sign and authenticate:

Default signer certificate, with the filename K2SIGN.CRT

Default signer private key, with the filename K2SIGN.KEY The required inputs to FILESIGN.EXE must be obtained from the VeriFone CA to logically secure the sponsor and signer privileges for the terminal. The following three unique inputs, which are issued at customer request by the VeriFone CA, are required for the file signing process, as well as the application files you want to sign and authenticate:

Customer signer certificate: This unique certificate is a required input for FILESIGN.EXE and must be downloaded to the terminal along with the signature files and target application files to authenticate, unless already downloaded to the terminal in a previous operation.

Customer signer private key: The VeriFone CA issues this unique, encrypted private key file (*.key) to an authorized signer at the sponsors request. The signer private key is a required input to FILESIGN.EXE, but does not have to be downloaded to the terminal.

Customer signer PIN: The VeriFone CA issues this unique password to an authorized signer at the sponsors request. The customer signer password is a required input to FILESIGN.EXE, but it does not have to be downloaded to the terminal. Note:

A default signer password is not a required entry when using FILESIGN.EXE to sign files for an Omni 3600 development terminal. Note:

The customer sponsor certificate, which authenticates the customer signer certificate, is usually downloaded to the terminal with the customer signer certificate, but it is not a required FILESIGN.EXE input when signing files to be downloaded to, and authenticated on, a deployment terminal. Replace a Sponsor Certificate A sponsor may need to clear the current sponsor certificate from a terminal so that a new sponsor can load certificates and applications. To do this, the original sponsor must order a clear smart card from the VeriFone CA. The clear smart card is specific to the requesting sponsor. It restores a deployment terminal to the development state (refer to Figure 39) by:

Deleting the current sponsor and signer certificates from the terminals application partition.

Restoring the default certificate to the terminals application partition. 110 OMNI 3600 REFERENCE MANUAL FILE AUTHENTICATION Introduction to File Authentication NOTE The process for replacing a signer certificate is the same as for replacing a sponsor certificate. File Authentication and the Omni 3600 File System Figure 39 Certificate Replacement Process Application Memory Logically Divided Into File Groups The memory of an Omni 3600 terminal is logically divided into two main areas, or partitions: One partition is for the operating system and the other partition is reserved for 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 others operation. There are a total of 16 file groups (Figure 40). Group 0 is the name of the operating system partition. Group 1 is reserved for the main application. Groups 214 are available for related executable files or secondary applications. Group 15 is open, and used for shared files. OMNI 3600 REFERENCE MANUAL 111 FILE AUTHENTICATION Introduction to File Authentication Figure 40 Omni 3600 Application Memory Partitions NOTE The Omni 3600 operating system only enforces the rule that the main application always be 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. Rules for Storing Applications in Specific File Groups Here are some important Omni 3600 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.

The main application stored in GID1 can access files, secondary applications, or function libraries stored in any other file group. The application downloaded into GID1 is always the primary application for the terminal. This application is owned by the primary terminal sponsor

(sponsor A) in cases where there are multiple sponsors. The Group 1 application controls any and all secondary applications stored in terminal memory. That is, a secondary application can only be invoked by a RUN command issued by the Group 1 application.

An application stored in Groups 215 can only access files stored in its own file group and in Group 15. For example, an application authorized by the sponsor to be authenticated in Group 4 can only access files and libraries stored in Group 4 and Group 15.

If multiple applications (main and secondary) are to run on the same terminal, each .OUT and/or shared library file must have its own matching signature file. 112 OMNI 3600 REFERENCE MANUAL FILE AUTHENTICATION Introduction to File Authentication Because each application is responsible for verifying its own data and prompt files, the other application files should have their own matching signature files. The master .OUT file should validate that these additional signature files are authenticate before the signature files are used.

If two or more applications are to run on the same terminal, the signature files for the respective applications must be downloaded, together with the corresponding target files, into the specific file group(s) for which the applications are authorized. If an application is downloaded into a group for which is it not authorized, file authentication for that application fails. If, for example, Application B is downloaded into GID4, where it is authorized to run, but the signature files for all Application B executable files are downloaded into GID7, file authentication for Application B fails and it is not allowed to run.

Each certificate contains an attribute to verify if an application is valid for a particular group. Authenticate Files Stored in the RAM or Flash of a File Group All *.p7s files are loaded into RAM and contain flags that indicate if the file to verify is stored in flash or RAM. A signature file must know if its matching application file is stored in flash or RAM. If a signature file cannot locate its matching application file, the application file is not authenticated. If the signature file authenticates its target file, and if the *FA variable is present in the CONFIG.SYS file of the target file group and is set to 1, the signature file is retained in memory and is automatically moved, if necessary, into the same file system as the target file it authenticates. That is, if the target file is stored in the flash, the signature file is also stored in the flash; if the target file is stored in RAM, the signature file is also stored in RAM. If the signature file authenticates its target file and the *FA variable is present in the CONFIG.SYS file of the target file group and is set to 0, the signature file is erased when its target file is authenticated. If you intend to perform back-to-back downloads, as described in Chapter 4, all signature files must be retained in the Omni 3600 terminals application memory, together with the target application files they authenticate. NOTE To control if signature files are retained or deleted when they are processed by the file authentication module, you must use the protected CONFIG.SYS variable *FA as documented in the Verix Operating System Programmers Manual. OMNI 3600 REFERENCE MANUAL 113 FILE AUTHENTICATION The FILESIGN.EXE File Signing Tool Restrictions on Downloading Different File Types A typical application download includes a variety of different file types. There are the following restrictions on how you can download different kinds of files to the Omni 3600 terminal and how files are stored in the file system:

File Type Restriction Certificate (*.crt) Must be downloaded into the RAM of the target file group (GID1 GI15) selected in system mode. Signature (*.p7s) Must be downloaded into the RAM of the target file group (GID1 GID15) that you select in system mode. Operating system Must be downloaded into Group 1 RAM. When the OS files and related certificates and signature files are authenticated, they are automatically moved from Group 1 RAM into the Group 0 sub-

partition, reserved for the operating system. The normal size of a signature file is approximately 400 bytes. Depending on the applications size and on how memory space is allocated, the area available for storing multiple signature files must be carefully managed. The memory space required by a certificate file is also approximately 400 bytes, but certificate files are temporary. When a certificate is authenticated, the data it contains is copied to the certificate tree, and the certificate file is erased from the target file groups RAM. The FILESIGN.EXE File Signing Tool To generate the signature files required for file authentication, you must sign all executable files and other files to be logically protected, using the FILESIGN.EXE software tool. This section discusses use of this tool, which is included in the Omni 3600 SDK. The file signing tool, FILESIGN.EXE, generates a formatted file called a signature file, recognized by the filename extension *.p7s. You can run FILESIGN.EXE on a host computer (PC) in DOS command-line mode, or invoke the program under Windows NT or Windows 95 and then use the FileSign dialog box to make the required entries. NOTE The file signing process for operating system files is done for Omni 3600 customers by the VeriFone CA. For operating system updates, VeriFone provides customers with a complete download package that includes all certificates and signature files required for authentication. FILESIGN.EXE System Requirements The FILESIGN.EXE tool requires one of the following computing environments:

Windows NT, Version 4.0, SP5

Windows 95, with Internet Explorer Version 5.0 The SP5 and Internet Explorer Version 5.0 software can be downloaded from the Microsoft Web site located at www.microsoft.com. 114 OMNI 3600 REFERENCE MANUAL Operating Modes for FILESIGN.EXE FILE AUTHENTICATION The FILESIGN.EXE File Signing Tool FILESIGN.EXE can run on the host computer in two user modes:

Command-line mode (Windows PC DOS shell): Command-line mode is useful for application developers who perform batch file downloads and is convenient when using file download tools provided by VeriFone such as VeriCentre Download Management Module (DMM), ZonTalk 2000, and the direct download utility, DDL.EXE. In command-line mode, you can sign a batch of files in a single operation.

Graphical interface mode (Windows NT or Windows 95): Use the FileSign dialog box (Figure 41) to select the file to sign and assign a name and destination location for the generated signature file on the host computer. When you run the FILESIGN.EXE tool under Windows, you can sign only one file at a time. You can also specify to store the target file in the target file groups RAM

(default location) or in the flash file system. If required, you can navigate through the file system on your PC to select the signer certificate file (*.crt) and signer private key file (*.key) to use as inputs to the file signing process. Figure 41 FileSign Dialog Box for FILESIGN.EXE Under Windows NOTE If the entry of a signer password is a required input, a secondary dialog box displays to enter and confirm the password. Please also note that a signer password is required for a deployment terminal, but not for a development terminal. OMNI 3600 REFERENCE MANUAL 115 FILE AUTHENTICATION The FILESIGN.EXE File Signing Tool Command-Line Entries for FILESIGN.EXE Table 20 lists and describes the switches that make up the command-line mode syntax for FILESIGN.EXE. Table 20 Command-Line Mode Switches for FILESIGN.EXEa Switch

-C, -c Description Requirements Signer certificate file name (*.crt).

-K, -k Signer private key filename (*.key).

-P, -p

-F, -f

-S, -s

-L, -l Signer password for decrypting the signer private key. Name of the application file to sign (*.out,

*.lib, or other file type). Name of the signature file (*.p7s) for FILESIGN.EXE to generate for the target application file. Specifies to store the target application file to sign and authenticate in the flash (drive F:) file system. If you do not use this switch to specify flash as the target file destination, it is stored by default in the RAM file system (drive I:). Required input for development terminals and deployment terminals. For development terminals, you can use the default signer certificate, K2SIGN.CRT. For deployment terminals, you must use the signer certificate issued by the VeriFone CA. Required input for development terminals and deployment terminals. For development terminals, you can use the default signer private key, K2SIGN.KEY. For deployment terminals, you must use the signer private key provided by the VeriFone CA. Required input only for deployment terminals. The VeriFone CA issues and securely conveys this password to an authorized signer. Required for development terminals and for deployment terminals. Required for development terminals and for deployment terminals. Optional entry. This switch assigns an F: prefix to the name of the

*.out or *.lib file to download, and also stores this information in the signature file as part of the special filetype attribute. NOTE: Signature files must be downloaded into the target file groups RAM. If the target file is authenticated, the corresponding *.p7s file is moved to the same memory area as the target file it authenticates. For example, if the target file is stored in flash (F:), its *.p7s file is moved into the flash file system. If, however, you set the *FA variable in the file groups CONFIG.SYS file to 0, all signature files are deleted from RAM when file authentication is complete. a. The switches described in Table 20 are not case-sensitive and can be entered on the command line in any order. 116 OMNI 3600 REFERENCE MANUAL Command-Line Mode Syntax Example In the FILESIGN.EXE command-line entry example below, please note that the syntax used applies to an Omni 3600 development terminal with the factory set of certificates, and not to a deployment terminal. The differences are as follows:

FILE AUTHENTICATION The FILESIGN.EXE File Signing Tool

The default signer certificate and default signer key file names that are provided by VeriFone as part of the Omni 3600 SDK are entered on the command line instead of customer-specific customer signer certificate and customer signer private key file names, and The switch for signer password (-P password) is not used, because a customer signer password is only required to sign and authenticate files for Omni 3600 deployment terminals being prepared for deployment. Please note also how the command-line mode switches described in Table 20 are used in this example:

filesign -L -f file.out -s file.p7s -c k2sign.crt -k k2sign.key

The -L switch indicates to store the application file in the flash file system instead of the target groups (default) RAM file system. (The target group for the download must be selected from system mode when the download is performed.) The -f switch indicates that the application file file.out must be signed by the FILESIGN.EXE tool. Executable files, such as *.out and *.lib files, must always be signed if they are to run on the terminal following a download. Depending on the applications logical security requirements, other types of files, such as data files and font files, may also need to be signed and are authenticated on download. The -s switch is followed by the name of the signature file to generate, file.p7s. The -c switch is followed by the name of the default signer certificate to use for file authentication with the development terminal, k2sign.crt. The -k switch is followed by the name of the default signer private key file, k2sign.key. A signer private key is a required input to the file signing process for development terminals and for deployment terminals. When you execute FILESIGN.EXE in the Windows environment, the FileSign dialog box displays (see Figure 41). The FileSign dialog box has four entry fields, each of which is followed by a Next

[...] selection button, as well as one check box, and the OK and Cancel buttons:

Press ALT-C or click on the [...] button to the right of the Certificate field to locate and select the certificate file (*.crt) you want to use to sign the file.

Press ALT-K or click on the [...] button to the right of the Key field to locate and select the signer private key file (*.key). OMNI 3600 REFERENCE MANUAL 117 FILESIGN.EXE Graphical Interface Mode FILE AUTHENTICATION The FILESIGN.EXE File Signing Tool

Press ALT-F or click on the [...] button to the right of the File to be signed field to locate and select the application file (*.out, *.lib, or other) to sign. If necessary, you can also modify the filename. If you want to store the file in flash memory on download to the terminal, check the Stored in FLASH checkbox. This adds the F: prefix to the target file name.

Press ALT-S or click on the [...] button to the right of the Signature file field to enter a filename for the signature file to be generated. The filename extension must always be *.p7s. You can also choose another directory to store the generated signature file.

When all entries are complete, press ALT-O or click the OK button to execute FILESIGN.EXE and generate the signature file. Or, press ALT_A or click Cancel to exit the FILESIGN.EXE utility. When the necessary signature files are generated to authenticate the application or applications on the Omni 3600 terminal, you are ready to perform the application download procedure. For more information about file authentication within the context of specific download procedures, please refer to Chapter 4. 118 OMNI 3600 REFERENCE MANUAL Troubleshooting and Service This chapter discusses:

CHAPTER 6 typical problems encountered and their resolution, cleaning and maintenance,

where to go for more information. product specifications, and VeriFone follows stringent quality control standards in the manufacture of Omni 3600 terminals. Each unit that leaves the factory receives numerous tests to ensure quality and reliable operation. However, should you encounter a problem in operation, read this section for possible causes and solutions. Perform only those adjustments or repairs specified in this guide. For all other services, contact your local VeriFone distributor or service provider. Service conducted by parties other than authorized VeriFone representatives may void the product warranty. The Omni 3600 terminal comes equipped with tamper-evident labels. Do not, under any circumstance, attempt to disassemble the terminal. NOTE NOTE Smart Card The smart card implementation is a proprietary hardware solution that has no serviceable parts. System Messages Appendix A lists all system messages, including informational and error messages, and prompts, that may appear on the Omni 3600 display panel. For an explanation of a message that indicates some terminal malfunction occurred, please refer to the descriptions in Appendix A. Use Remote Diagnostics to Identify Problems Certain problems with a specific Omni 3600 terminal can be identified by a computer running a diagnostic test program. The diagnostic computer can be connected directly to a docked terminal by a cable or through a telephone line connection. Troubleshooting The troubleshooting guidelines provided in this section identify various problems and suggest appropriate corrective action(s). If you have problems operating your Omni 3600 terminal, please read through these troubleshooting examples. If the problem persists or if it is not described below, contact your local VeriFone representative for assistance. OMNI 3600 REFERENCE MANUAL 119 TROUBLESHOOTING AND SERVICE Troubleshooting Terminal Display Does Not Show Correct or Readable Information 1 Dock the Omni 3600 terminal in a base station. 2 Check all cable connections and verify that the telephone line is properly connected. 3 Recharge or replace the battery. 4 Check display contrast by performing a local diagnostic test of the terminal display in system mode (refer to System Mode Menu 5 in Chapter 3). 5 If the problem persists, contact your local VeriFone representative for assistance. Smart Battery Will Not Charge The smart battery must initially receive a full charge to set the batterys charge capacity memory. Allow the Omni 3600 terminal to remain connected to the power pack for a minimum of 2 hours, maximum of 4 hours to ensure the battery receives a full charge. Since the smart battery has a memory of its initial charge, this is the maximum charge it will take. If the initial charge was not long enough or insufficient, battery use hours are shortened. NOTE Conserve battery power by turning the Omni 3600 terminal off when not in use. If the terminal is not to be used for several days, remove the battery from the terminal as it continues to discharge even when the terminal is turned off. Telephone Line Connection Does Not Work Properly 1 Check the telephone line cord and all telephone connections. 2 If you are using a pass-through (Telset) connection, check that the telephone handset is seated properly in its cradle. Also, check the line using another telephone base unit. If the other telephone works, have the defective telephone repaired or replaced. 3 If you are using a direct (Telco) connection, check the Telco cable by plugging it into a working telephone and listening for a dial tone. If this test does not work, replace the Telco cable. If it is determined that the telephone line is dead, contact your local telephone company to check the status of the line. 4 If the problem persists, contact your local VeriFone representative for assistance. Printer Does Not Work 1 Check battery status. The printer will not print if there is an insufficient charge remaining in the battery to complete the print operation. 2 Check if the printer is out of paper. Open the paper roll cover and install a new roll of printer paper. 3 Perform a test of the integrated thermal printer as described in Printer Test in Chapter 1. 4 If the problem persists, contact your local VeriFone representative for assistance. 120 OMNI 3600 REFERENCE MANUAL TROUBLESHOOTING AND SERVICE Troubleshooting Serial Port Does Not Work 1 The serial port on the back panel of the base station is identified by the RS232 icon. Check that the device connected to the serial port has power and is functioning properly. If possible, perform a self-test on the device in question. 2 The cable connecting the optional device to the base station serial port may be defective. Try a different serial cable. 3 If the problem persists, contact your local VeriFone representative for assistance. Terminal Does Not Process Transactions There are several possible reasons why the terminal may not be operating properly or processing transactions. To check the most likely causes, follow the steps below. Step 1: Check the magnetic card reader 1 Test the magnetic card reader as described in System Mode Menu 5 in Chapter 3. 2 Perform a test transaction using several different magnetic stripe cards to ensure the problem is not a defective card. 3 Make sure you are swiping cards properly. With the Omni 3600 card reader, the black, magnetic stripe on the card should face down, away from the keypad. 4 Process a transaction manually using the keypad instead of the card reader. If the manual transaction works, the problem may be a defective card reader. Contact your VeriFone distributor or service provider. 5 If the manual transaction does not work, proceed to Step 3. Step 2: Check the smart card reader 1 Perform a test transaction using several different smart cards to ensure the problem is not a defective card. 2 Make sure you are inserting the cards properly. With the Omni 3600 smart card reader, the chip on the card should face down and inward. 3 Ensure the MSAM cards are properly inserted and the cardholders are properly secured as described in Install/Replace MSAM Cards in Chapter 1. 4 Process a transaction manually using the keypad instead of the card reader. If the manual transaction works, the problem may be a defective card reader. Contact your VeriFone distributor or service provider. 5 If the manual transaction does not work, proceed to Step 3. OMNI 3600 REFERENCE MANUAL 121 TROUBLESHOOTING AND SERVICE Cleaning and Care Step 3: Check the telephone line 1 Connect to a working telephone and check for a dial tone. If there is no dial tone, replace the Telco cable. 2 If the problem appears to be with the telephone line, check with the party you are trying to call to see if their system is operational. If they are not experiencing difficulties with their line, contact the telephone company and have your line checked. 3 If the telephone line works, contact your local VeriFone representative for assistance. Keypad Does Not Respond 1 Check the display panel. If it displays the wrong character or nothing at all when you press a key, follow the steps outlined in Terminal Display Does Not Show Correct or Readable Information. 2 If pressing a function key does not perform the expected action, refer to the user documentation for that application to be sure you are entering data correctly. 3 Perform a local diagnostic test of the keyboard in system mode (refer to System Mode Menu 5 in Chapter 3). 4 If the problem persists, contact your local VeriFone representative for assistance. Cleaning and Care This section discusses keeping the Omni 3600 terminal and Omni 3600 base clean. For normal dirt, use a clean cloth slightly dampened with water and a drop or two mild soap. For stubborn stains, use alcohol or an alcohol-based cleaner. CAUTION Never use thinner, acetone, trichloroethylene, or ketone-based solvents these chemicals can deteriorate plastic or rubber parts. Do not spray cleaners or other solutions directly onto the keypad or display. Base Contacts It is important that the exposed contacts in the docking cradle of the base stay clean and unbent. Gently swab the contacts with alcohol or contact cleaner to remove dirt. CAUTION Avoid touching the contacts in the raised area in the center of the base. Finger oils tarnish contacts, causing bad connections. If the battery charge state or terminal power LEDs do not light when the terminal is docked or there is a high occurrence of bad or incomplete data transfers, clean the contacts. 122 OMNI 3600 REFERENCE MANUAL TROUBLESHOOTING AND SERVICE VeriFone Service and Support Smart Card Reader CAUTION Do not attempt to clean the smart card reader. Doing so may void your warranty. For smart card reader service, contact your VeriFone distributor or service provider. VeriFone Service and Support For Omni 3600 terminal or base problems, contact your local VeriFone representative or service provider. Visit www.verifone.com to locate a representative near you. For Omni 3600 product service and repair information:

(USA) VeriFone Service and Support Group, 1-800-837-4366, Monday Friday, 8 A.M.8 P.M. eastern time

(International) Contact your local VeriFone representative For Omni 3600 supplies:

VeriFone Online Store at www.store.verifone.com.

(USA) VeriFone Customer Development Center, 1-800-837-4366, Monday Friday, 7 A.M.8 P.M. mountain time

(International) Contact your local VeriFone representative Return a Terminal, Omni 3600 Base, or Smart Battery Before returning an Omni 3600 terminal, base, or smart battery to VeriFone, you must obtain a Merchandise Return Authorization (MRA) number. The following procedure describes how to return one or more terminals or base for repair or replacement (U.S. customers only):

NOTE International customers, please contact your local VeriFone representative for assistance with your service, return, or replacement. 1 Gather the following information from the printed labels (Figure 42) on the bottom of each Omni 3600 terminal and base station you are returning:

Product ID, including the model and part number. For example, OMNI 3600 and P096-XXX-XX

Serial number (S/N XXX-XXX-XXX) 2 Contact VeriFone:

Within the U.S., call VeriFone toll-free at 800-VeriFone (837-4366)

Internationally, contact your local VeriFone representative. To locate a representative near you, visit www.verifone.com 3 Select the MRA option from the automated message. The MRA department is open MondayFriday, 8 A.M.8 P.M., eastern time. OMNI 3600 REFERENCE MANUAL 123 TROUBLESHOOTING AND SERVICE VeriFone Service and Support 4 Give the MRA representative the information gathered in Step 1. If the list of serial numbers is long, you can fax the list, along with the information gathered in Step 1, to the MRA department. Include a telephone number where you can be reached and your fax number. Please print clearly to the attention of the VeriFone MRA Dept. and send your fax to 502-329-5947 (U.S.). You will be issued an MRA number and the fax will be returned to you. NOTE One MRA number must be issued for each terminal or base station you return to VeriFone, even if you are returning several of the same model. 5 Describe the problem and provide the shipping address to return the repaired or replacement unit. 6 Keep a record of the following items:

Assigned MRA number(s)

VeriFone serial number assigned to the Omni 3600 terminal or base station you are returning for service or repair

Shipping documentation, such as airbill numbers used to trace the shipment

Model(s) returned (model and part numbers are located on the bottom of each terminal or base station) 124 OMNI 3600 REFERENCE MANUAL Figure 42 Information Labels on Bottom of Terminal TROUBLESHOOTING AND SERVICE Specifications Specifications Power Requirements Environmental DC power (all Omni 3600 terminals and base stations): DC: 19VDC; 3.16A DC power pack (all Omni 3600 terminals and base stations):

Input: 100240 V ~ (100240VAC); 5060 Hz; 1.5A

Output: 19VDC; 3.16A Barrel connector polarity (all Omni 3600 terminals and base stations):

Omni 3600 terminal:

Operating temperature: 0 to 40 C (32 to 104 F)

Storage temperature: 18 to + 66 C (0 to 150 F)

Relative humidity: 15% to 90%; no condensation Base station:

Operating temperature: 0 to 55 C (32 to 131 F)

Storage temperature: 40 to + 70 C (-40 to 158 F)

Relative humidity: 15% to 90%; no condensation Dimensions

Height: 69 mm (2.72 inches)

Width: 95 mm (3.74 inches)

Length: 220 mm (8.64 inches) Weight

Terminal weight: 568 g (1.25 lb)

with battery installed: 681 g (1.5 lb)

with battery and paper roll installed: 710 g (1.56 lb)

Shipping weight: 1264 g (2.78 lb): The shipping weight for the Omni 3600 terminal includes: shipping carton, one terminal, power pack and cable, one smart battery, paper roll, and one Quick Installation Guide.

Base station weight: 378 g (0.83 lb)

Shipping weight: 498 g (1.098 lb): The shipping weight for the Omni 3600 base station includes: shipping carton, one base station, one Telco cable, and one Quick Installation Guide. OMNI 3600 REFERENCE MANUAL 125 TROUBLESHOOTING AND SERVICE Accessories and Documentation Accessories and Documentation Accessories and documentation available for the Omni 3600 are listed in this section. When ordering, please refer to the part number on the left. How to Order

VeriFone Online Store at www.store.verifone.com

USA: VeriFone Customer Development Center, 1-800-837-4366, Monday Friday, 7 A.M.8 P.M., PST

International: Contact your local VeriFone representative Download Cables and Adapters 05651-xx 26263-xx 26264-xx 22536-01 MOD10-MOD10 (base station-to-base station) 02xxx MOD10-PC DB25F (base station-to-PC) 02xxx MOD10-PC DB9F (base station-to-PC) MOD10 adapter (terminal-to-terminal/PC/telephone) Cables for Optional Peripherals 07041-xx MOD10-MDIN9 (CR 600/CR 1000i check readers) Base Station P096-201-00 Base station Telco Cable 00124-17 Antenna 2.1-m (7) telephone line cord, black color, with modular RJ11-type connectors Contact your VeriFone distributor to determine the exact antenna for your Omni 3600 terminal. 22066-XX Replacement antenna. Smart Battery 22044-02 12V battery pack Power Pack Contact your local VeriFone distributor to determine which power pack fits your needs. 22161-01 21973-01 DC power pack (universal) Power cable (U.S.) 126 OMNI 3600 REFERENCE MANUAL TROUBLESHOOTING AND SERVICE Accessories and Documentation Thermal Printer Paper CRM0043 Standard-grade thermal printer paper, 57-mm (2.25) width, 7.62-m

(25) length; single roll VeriFone Cleaning Kit 02746-01 Cleaning kit Documentation 22377 22378 22060 19733 Omni 3600 Quick Installation Guide Omni 3600 Base Station Quick Installation Guide Omni 3600 Installation Guide Verix Operating System Programmers Manual OMNI 3600 REFERENCE MANUAL 127 TROUBLESHOOTING AND SERVICE Accessories and Documentation 128 OMNI 3600 REFERENCE MANUAL System Messages APPENDIX A This appendix describes error and information messages that may appear when the Omni 3600 terminal is in system mode. For ease of use, these messages are grouped alphabetically. These messages include those:

displayed digital certificate and signature file download to the terminal processed by the file authentication module displayed when using the file compression module of the VeriCentre DMM terminal management and download tool ALREADY DEBUGGING This message displays when DEBUGGER F4 in SYS MODE MENU 4 is selected and the debugging monitor program, DBMON.OUT, is already running on the terminal. APPLICATION ALREADY RUNNING PLEASE RESTART This message displays when an attempt was made to invoke a system mode function not allowed to execute while an application is running on the terminal. The requested function is not invoked, and the application continues to run in the background. Some system mode functions, such as setting the date and time, can be performed in this mode even with the application running in background, and this message does not display. For other system mode functions, such as downloads and RAM or flash clear operations, you must restart the terminal and re-enter system mode before the application starts (within three seconds). To restart the terminal and enter system mode:

1 Press the cancel key until the SYS MODE MENU 1 displays. 2 Select RESTART F4. 3 Enter system mode within three seconds of seeing the VeriFone copyright screenbefore the application beginsby simultaneously pressing F2 and F4. DEVICE BUSY PLEASE RESTART STAND ALONE OMNI 3600 REFERENCE MANUAL 129 SYSTEM MESSAGES This message displays when a system mode function queried an internal device that is busy. This message can also occur if you entered system mode with an application running. For example, if the application opened the magnetic stripe card reader and you try to invoke the card reader diagnostic through MAG CARD READER F4 in SYS MODE MENU 5, the attempt fails and this message appears. Restart the terminal and enter system mode before the application starts. DOWNLOAD NEEDED The operating system is unable to start the application specified in the *GO variable for the following reasons:

No application resident in the terminal.

The *GO variable is not set in the Group 1 CONFIG.SYS file. The application file specified in the *GO variable does not exist in Group 1.

(The *GO variable cannot specify an application file stored in a file group other than Group 1.)

The application or a shared library used by the application either does not exist or is not authenticated. All executables must be authenticated to run on the terminal. There is not enough memory available to run the application requested in the

*GO variable. FLASH CHKSUM ERROR A corrupt file is detected in the flash file system during terminal start up, after power-on, or during restart. This message may indicate a hardware problem or the error condition may be resolved through another download of the file. LOAD DBMON.OUT The DEBUGGER F4 option in SYS MODE MENU 4 was selected. The debugging monitor program, DBMON.OUT, is included in the SDK, but is not stored in the terminal memory of a factory unit. To use the debugging tool, you must sign, download, and authenticate the DBMON.OUT application. LOAD TERMINAL MANAGEMENT AGENT This message displays if you select REMOTE DIAGS F2 in SYS MODE MENU 4 and the

(optional) Terminal Management Agent (TMA) software is not resident in the Omni 3600 terminal. The TMA software is required to perform remote diagnostics. For more information about support for remote diagnostics, contact your VeriFone service provider. 130 OMNI 3600 REFERENCE MANUAL SYSTEM MESSAGES MODL O3600M CTRY GEN KEYPAD DISPLAY MAG RDR PRINTER 0 128064 3 1 This message displays when you select CONFIG INFO F2 in SYS MODE MENU 3 and press the PF2 key (below the down arrow) two times. This third display, in a series of four, provides the following information about the current terminal configuration:

MODL: The model number assigned to the terminal on manufacture. CTRY: The name or abbreviation (up to 42 characters) of the country of manufacture. KEYPAD: A code (05) to indicate keypad type. DISPLAY: A code (000000, 000001, or xxxyyy) to indicate display unit type. MAG RDR: A code (04) to indicate magnetic stripe card reader type. PRINTER: A code (0 or 1) to indicate that a thermal printer is integrated. PINPAD LIFE RSET RCNT MODEM CTRY 1 730810 020829000536 198

This message displays when you select CONFIG INFO F2 in SYS MODE MENU 3 and press the PF2 key (below the down arrow) three times. This fourth display, in a series of four, provides the following information about the current terminal configuration:

PINPAD: A code (0 or 1) to indicate that a PIN pad is integrated. LIFE: The number of seconds the terminal has run since first powered on. RSET: The date and time when the terminal was last reset, in yymmddhhmmss format. RCNT: The total number of times the terminal has been reset. MODEM CTRY: The current two-digit modem country code setting. For additional information about modem country codes, see the Verix Operating System Programmers Manual. PLEASE TRY AGAIN This message displays if you enter an incorrect system mode password or an incorrect file group password. Repeat the password entry and press the enter key. OMNI 3600 REFERENCE MANUAL 131 SYSTEM MESSAGES RAM FLASH SERNO PTID PART VERS 1024 2048 024-546-755 12443328 P096-100-02 6 This message displays when you select CONFIG INFO F2 in SYS MODE MENU 3 and press the PF2 key (below the down arrow) to display the next screen. This second display, in a series of four, provides the following information about the current terminal configuration:

RAM: The RAM (SRAM) size in kilobytes (KB). FLASH: The flash memory size in KB. SERNO: The serial number assigned to the terminal on manufacture. PTID: The permanent terminal ID assigned to the terminal on manufacture. If no PTID is assigned, the default value is 12000000. PART: The part number assigned to the terminal on manufacture. VERS: The hardware version number assigned to the terminal on manufacture. RAM CHKSUM ERROR A corrupt file is detected in the RAM file system at terminal start up, after power-

on, or during restart. This message may indicate a hardware problem or the error condition may be resolved through another download of the file. RAM FILES INUSE AVAIL FLASH FILES INUSE AVAIL 5 31686 960630 1 3232 1766232 This message displays when you select CONFIG INFO F2 in SYS MODE MENU 3. This first display, in a series of four, provides the following information about the current terminal configuration:

INUSE: The number of bytes of memory space currently being used in the RAM file system (RAM FILES) or the flash file system (FLASH FILES). AVAIL: The number of bytes of memory space currently available in the RAM file system (RAM FILES) or the flash file system (FLASH FILES). RECEIVING NOW 132 OMNI 3600 REFERENCE MANUAL SYSTEM MESSAGES In back-to-back downloads, the Target (receiving) terminal displays this message on data transfer initiation when pressing the asterisk key (*). To stop the upload, press the cancel key on either terminal (Gold or Target). SYS MODE CLEAR CLEARING FLASH PLEASE WAIT This message displays when you select FLASH FILES F4 in SYS MODE MENU 2 and select CLEAR GROUP_nn F2 or CLEAR ALL FILES F3 to clear files from the flash memory of a specific file group (Group 115) or from the entire flash memory. This message remains until the files either within the file group or all files in flash are deleted. If you select CLEAR ALL FILES F3, only application file(s) stored in the flash-based file systemnot the files stored in RAMare erased. SYS MODE CLEAR CLEARING RAM PLEASE WAIT This message displays when you select RAM FILES F3 in SYS MODE MENU 2 and select CLEAR GROUP_nn F2 or CLEAR ALL FILES F3 to clear files from the RAM of a specific file group (Group 115) or from the entire RAM. This message remains until the files either within the file group or all files in RAM are deleted. If you select CLEAR ALL FILES F3, only the application file(s) stored in RAMnot the files stored in flashare erased. If you erase the main application stored in the RAM file system, the terminal displays DOWNLOAD NEEDED after the VeriFone copyright screen on terminal restart. Note that clearing the RAM does not erase the keyed variable settings stored in protected CONFIG.SYS recordsthat is, in records that start with an asterisk (*). SYS MODE DEFRAG RECLAIMING FLASH PLEASE WAIT This message displays when you select FLASH FILES F4, followed by DEFRAG F4 in SYS MODE MENU 2 to perform defragmentation (coalesce) of the flash memory file system. PLEASE WAIT remains displayed during the defragmentation process. On successful completion, the terminal automatically restarts. SYS MODE DOWNLOAD DOWNLOADING NOW An application is being downloaded to a receiving Omni 3600 terminal from a host PC, either directly over a serial cable or by telephone. This message also displays on the Target terminal in a back-to-back download. OMNI 3600 REFERENCE MANUAL 133 SYSTEM MESSAGES The terminal displays a series of asterisks (*) to indicate the progress of the download (each asterisk represents 10% of the file is downloaded). When ten asterisks appear, the data transfer is complete. SYS MODE EDIT

*KEY KEY F2 VALUE F3 This message displays when you select EDIT F3 in SYS MODE MENU 3 to invoke the keyed file editor to edit files (such as, CONFIG.SYS), as follows:

FILE: Make the appropriate menu selections to select or create a file to edit KEY: Search for a specific keyed record VALUE: Add a new value for a selected keyed record SYS MODE ERR LOG TYPE FRAME USP TCB TIME This information appears when you select ERROR LOG F3 in SYS MODE MENU 4. The following information helps developers interpret the cause of the most recent unrecoverable software error that occurred on the terminal:

TYPE: The error type code. For a description of error types (codes 211), refer to Chapter 3. FRAME: The value of the stack frame. USP: The value of the user stack pointer. TCB: The value of the task control block. TIME: The binary-coded decimal clock time when the last error occurred in yymmddhhmmss format. If you report a system error to VeriFone, you may be asked to provide the information displayed in this screen. For detailed information about the error log function and the terms listed above, please refer to the Verix Operating System Programmers Manual. SYS MODE KBD TEST KEYCODE nn 134 OMNI 3600 REFERENCE MANUAL SYSTEM MESSAGES This message displays when you initiate a local diagnostic test of the terminal keyboard through KEYBOARD DIAG F3 in SYS MODE MENU 5. When invoked, the decimal ASCII keycode of each key you press (test) appears to the right of KEYCODE. For example, pressing the 1 key on the terminal keypad displays the corresponding ASCII keycode, 31. SYS MODE PASSWORD FILE GROUP nn GROUP nn PASSWORD This message displays when you initiate the procedure for modifying existing system mode passwords through PASSWORDS F4 in SYS MODE MENU 3. Additional menu options display to let you change the password of a file group (F2) or the system mode password (F3). SYS MODE PASSWORD NEW AGAIN PASSWORD CHANGED This message displays when you select PASSWORDS F4 in SYS MODE MENU 3 to modify the existing system mode password.

NEW: Make the appropriate menu selections to enter the new password. AGAIN: Repeat the entry to confirm the new password. PASSWORD CHANGED: Displays when the new password is accepted. SYS MODE UPLOAD UPLOADING NOW In a back-to-back download, the Gold (sending) terminal displays this message when you initiate an upload from the receiving terminal. To stop the upload, press the cancel key on either terminal. TRK1:

TRK2:

TRK3:

When you invoke a local system mode diagnostic test of the magnetic stripe card reader, status information appears for data track (TRK1, TRK2, and TRK3) on a magnetic stripe card. To perform this test, select MAG CARD DIAG F4 in SYS MODE MENU 5 and swipe a magnetic stripe card through the card reader:

NO DATA or VALID DATA: A successful test of the magnetic-stripe card reader displays for each track. Actual data stored on data tracks does not display.

An error condition generates one of the following error messages for each track with an error:

OMNI 3600 REFERENCE MANUAL 135 SYSTEM MESSAGES

NO DATA NO START NO END LRC ERR PARITY ERR REVERSE END Press the cancel key to end the local diagnostic test of the card reader.

** UNZIP Error n xxxxxx yyyyyy If you are using the file compression module in DMM, information similar to what is shown above appears when an error occurs during file extraction from a downloaded ZIP archive. Note the error number and error codes (xxxxx and yyyyy) and try to download the archive again. UNZIP stuff.zip myprog.out mydata.txt 6x8.fon 10x14.fon

... If you are using the file compression module in DMM, information similar to what is shown above appears when a compressed file archive downloaded to the terminal decompresses (unzipped), and the files extracted from the archive.

** VERIFYING FILES **

Check Certificate

(or System Certificate) filename.crt

** Authentic **

(or ---Failed---) This message displays when the file authentication module detects a new digital certificate, together with the filename of the certificate to authenticate, during a download to the Omni 3600 terminal. If the authentication is successful, Authentic displays; otherwise, Failed displays for five seconds and the terminal beeps three times to draw attention to the filename of the certificate that could not be authenticated. This message remains on screen until all new certificates are checked, one by one. In special cases where system certificates are being installed, System Certificate displays instead of Check Certificate. 136 OMNI 3600 REFERENCE MANUAL SYSTEM MESSAGES

** VERIFYING FILES **

Compare Signature myfile.p7s myfile.out

** Authentic **

(or ---Failed---) The file authentication module detected a new signature file, together with the application file for which the signature file was generated, during a download to the Omni 3600 terminal. If the authentication is successful, Authentic displays;

otherwise, Failed appears for five seconds and the terminal beeps three times to draw attention to the filename of the certificate that could not be authenticated. This message remains on screen until all new signature files are checked. New digital certificates are always checked first, followed by new signature files, in an uninterrupted process. OMNI 3600 REFERENCE MANUAL 137 SYSTEM MESSAGES 138 OMNI 3600 REFERENCE MANUAL ASCII Table APPENDIX B An ASCII table for the Omni 37xx display is in Figure 43. The table is formatted for quick reference, as follows:

The letters and numbers in the column to the left of the table and in the row above the table are, when combined, the hexadecimal value of an ASCII character located in the corresponding row and column coordinate. The numbers shown in white on a black background within the table itself are the decimal value of the ASCII character in that table cell. The large character located in the middle of each cell is the ASCII character. For example, to determine the hexadecimal value of the plus (+) sign:

1 Locate the plus sign ASCII character in the table (decimal 43). 2 From this position, follow the row to the left and view the hexadecimal value in the column outside the table. This value (2) is the first character of the ASCII characters hexadecimal value. 3 Now, from the plus sign, follow the column to the top of the table and view the hexadecimal value in the row above the table. This value (B) is the second part of the hexadecimal value. LEARNING PRODUCTS TEMPLATE VERSION 2.1 USERS GUIDE 139 ASCII TABLE Figure 43 ASCII Table for the Learning Products Template Version 2.1 Display 140 LEARNING PRODUCTS TEMPLATE VERSION 2.1 USERS GUIDE APPENDIX C Omni 3600 Base Unit Port Pinouts The tables in this appendix list pinouts for the Omni 3600 base unit connectors. RS232 Port Connector Pin Function Description 1 10 LOOKING INTO CONNECTOR 1 2 3 4 5 6 7 8 9 10 TXCLK NC CD DTR GND

/RXD

/TXD CTS RTS RXCLK Transmit clock signal No connection Carrier detect Data terminal ready Power ground Receive data Transmit data Clear to send Request to send Receive clock signal Telco Port Connector Pin Function Description 1 6 LOOKING INTO MOD 6P4C 1 2 3 4 5 6 NC NC Tip Ring NC NC No connection No connection Telephone line Telephone line No connection No connection Telset Port Connector Pin Function Description 1 6 LOOKING INTO MOD 6P4C 1 2 3 4 5 6 NC NC Tip Ring NC NC No connection No connection Telephone line Telephone line No connection No connection OMNI 3600 REFERENCE MANUAL 141 OMNI 3600 BASE UNIT PORT PINOUTS Barrel Connector Polarity 142 OMNI 3600 REFERENCE MANUAL GLOSSARY Access code A code number dialed to gain ac-

cess to a telephone line, such as dialing the number 9 to reach an outside line. chandise in retail stores. To support specific applica-

tions, an optional bar code reader can be attached to the Omni 3600 to read and process bar codes. Application ID An alphanumeric code that identi-

fies an application program downloaded to a termi-

nal from a download computer. For ZonTalk 2000 application downloads, the application ID is stored in the CONFIG.SYS record which begins with the *ZA key. An Omni 3600 application ID can be up to 21 characters long. For VeriCentre Download Manage-

ment Module, the application ID, as well as other CONFIG.SYS variables, may differ from those used for ZonTalk 2000. Application program The ordered set of pro-

grammed instructions by which a computer performs an intended task or series of tasks. Application prompt The information shown on the terminals display panel when power is applied to the terminal, assuming that an application program has already been downloaded into the terminals memory and authenticated by the Omni 3300 file au-

thentication module. The application prompt often contains a graphical logo, and date and time, but it can consist of anything the programmer chooses for that purpose. ASCII Abbreviation for American Standard Code for Information Interchange. A 7-bit code (with no parity bit) that provides a total of 128 bit patterns. ASCII codes are widely used for information interchange in data processing and communication systems. Back-to-back application download The pro-

cess of copying the contents of one terminals appli-

cation memory to another terminals application memory. A terminal-to-terminal application upload require that the sending and receiving terminal be connected to each other by a serial cable. The same operation as a terminal-to-terminal application up-

load. Bar code Optical binary code imprinted on mer-

Bar code reader A pencil- or wand-shaped optical scanner used to read bar codes. To read the code, you drag the tip of the bar code reader across the length of the bar code, in a left-to-right or right-to-left direction. Base station This unit allows the Omni 3600 ter-

minal to obtain land-line connections and perform back-to-back downloads. Baud The number of times per second that a sys-

tem, especially a data transmission channel, chang-

es state. The state of a system may represent a bit, digit, or symbol. For a POS terminal, the baud rate indicates the number of bits per second that are transmitted or received by the terminals serial ports and modem. Bit Short for binary digit. Either of the two digits 0 and 1 in the binary number system. Also, a unit of in-

formation equal to one binary decision. The bit is the smallest unit of storage and hence of information in any binary system within a computer. Block A collection of data units such as words, characters, or records (generally more than a single word) that are stored in adjacent physical positions in memory or on a peripheral storage device. A block can therefore be treated as a single unit for reading, writing, and other data communication operations. Boot loader Also called a bootloader or bootstrap loader. A short program, stored in flash EPROM, that allows the terminal to continue operating during an operating system download procedure, until the new operating system is downloaded into terminal mem-

ory. Buffer A temporary memory for data, normally used to accommodate the difference in the rate at which two devices can handle data during a transfer. OMNI 3600 REFERENCE MANUAL 143 GLOSSARY Byte A term developed to indicate a measurable number of consecutive binary digits that are usually operated on as a unit. For the Omni 3600, a byte consists of eight bits. See also Bit. Calendar/clock chip A microchip inside the Omni 3600 terminal which keeps track of the current date and time. Card reader Also called magnetic stripe card read-

er. The slot on the right side of the Omni 3600 termi-

nal that automatically reads data stored in the magnetic stripe on the back of a specially-encoded card when you swipe the card through the slot. Carrier Usually, an analog signal that is selected to match the characteristics of a particular transmission system. The carrier signal on a phone line is modu-

lated with frequency or amplitude variations to allow a terminal to transmit or receive data using a mo-

dem. A carrier signal transmits data from a host com-

puter to an Omni 3600 terminal over an analog telephone line. Certificate Also called a digital certificate. A digital document or file that attests to the binding of a public key to an individual or entity, and that allows verifica-

tion that a specific public key does in fact belong to a specific individual. Character An element of a given character set. Al-

so, the smallest unit of information in a record. A let-

ter, numeral, or other symbol to express information. CONFIG.SYS file A special keyed file that is stored in terminal memory and which contains sys-

tem and application configuration parameters. Each record in a CONFIG.SYS file is identified by an al-

phanumeric search key. In the Omni 3600 file sys-

tem, there is one password-protected CONFIG.SYS file per file group (Groups 115). You can modify CONFIG.SYS records using the keyed file editor. See Keyed file editor. CPU Abbreviation for central processing unit. The principal operating part of a computer system that controls the interpretation and execution of instruc-

tions stored in memory. Data Information prepared, often in a particular for-

mat, for a specific purpose. Data is to be distin-

guished from applications or program instructions. In the Omni 3600 terminal, application files and data files can be stored in RAM or flash memory. Data entry The process of using a keyboard, card reader, or other device to input data directly into a system. Data packet A group of bits of fixed maximum size and well-defined format that is switched and trans-

mitted as a composite whole through a packet switching network. Any message that exceeds the maximum size is partitioned and carried as several packets. Data packets are formed by the controller in the sending data terminal and the data is extracted and reassembled by the controller at the receiving end. Dedicated line A leased or private telephone line that is used for a particular communications pur-

pose, such as to connect an Omni 3600 base station to a host computer. See Leased line. Default A value, parameter, option, or attribute that is assigned by the program or system when another has not been assigned by the user. Delete To remove a record, field, or item of data. Diagnostics Techniques employed for detection and isolation of malfunctions and errors in programs, systems, and devices. In a diagnostic test, a pro-

gram or routine is run to detect failures or potential failures. These tests and routines help detect and isolate problems in a terminal or peripheral device. Dial-up line A standard public telephone line. The switching equipment on a dial-up line requires that a party dial the other party before a connection can be made. Direct download The process of transferring files and/or data from a download computer to a terminal over a serial cable connection and in a local, as op-

posed to a remote, system environment. Display The screen on the Omni 3600 terminal that shows numerals, letters, and punctuation symbols in selected fonts, graphics in various formats, informa-

tion entered from the keypad, as well as system prompts and messages. 144 OMNI 3600 REFERENCE MANUAL GLOSSARY Docking/Docked The act of placing a Omni 3600 terminal in the docking cradle of a base station. The following can occur when the Omni 3600 terminal is docked:

A telephone line connection can be established to transfer data and files and effect downloads

The smart battery can be recharged (the battery can also be recharged through the terminal)

You can perform back-to-back downloads by connecting to another base station with a docked terminal Download To transfer files or data from a host computer or sending terminal over a communication link to a receiving terminal. DTMF Dual-tone multi-frequency. The ordinary dial tone on a telephone line. File authentication A process through which one proves and verifies the origin of a file, the identity of the sender, and the integrity of the information it con-

tains. Firmware System software, including the operating system, boot loader, default display font, and system messages, stored in terminal flash memory. Fixed prompt A system prompt or message stored as part of system firmware in terminal memory. Fixed prompts appear on the terminal display to alert the user to specific system occurrences or malfunc-

tions, and to prompt the user to enter specific infor-

mation or select options. Flash memory An area of non-volatile memory where files can be stored. The Omni 3600 also has a RAM-based file system. Files can be stored in RAM (drive I:) or in flash (drive F:) memory area of any file group (Groups 115). Host computer Also called a download computer. The primary or controlling computer in a multiple computer operation. Also, a computerusually a PC running Windows NT or Windows 95 or 98used to prepare programs for download to POS terminals. Host computers are also used to process transac-

tions that originate from a distributed network of POS terminals. Input The process of entering data into a process-

ing system or a peripheral device such as a terminal, or the data that is entered. Interface A common boundary between two sys-

tems, devices, or programs. Also, to interact. Keyed file character set A limited set of 95 ASCII characters, from 00h to 5Fh (or 0 to 95 deci-

mal), that is used by the Omni 3600 keyed file editor. Although an application program can download all 95 characters in this set, you can only enter 50 of these characters from the terminal keypad: 09, A Z, and 14 special characters. Keyed file editor A keyed file editor lets you cre-

ate new records or modify existing records stored in a keyed file such as CONFIG.SYS. See CON-

FIG.SYS file. Keyed file record ASCII data, or variables, stored in the terminals CONFIG.SYS file(s). A keyed file record consist of two parts: a search key that identi-

fies the record, and the data or variable stored in the record. See CONFIG.SYS file. Keypad A small keyboard or section of a keyboard containing a smaller number of keys, generally those used in simple calculators. The 16-key core keypad of the Omni 3600 terminal is used to enter data and perform operations. Leased line A private telephone line leased from the phone company. See Dedicated line. Line cord A telephone-type cord with modular plugs on each end to connect the base station to a dial-up telephone line. Local functions Operations performed at the ter-

minal only and not in interaction with a host comput-

er. For the Omni 3600, local functions such as internal diagnostics are performed in system mode. See Chapter 3. Manual transaction A transaction involving the manual entry of account information from the termi-

nal keypad instead of automatic entry of the informa-

tion from a reading device, such as a magnetic stripe card reader. OMNI 3600 REFERENCE MANUAL 145 GLOSSARY Memory A device or medium that can retain infor-

mation for subsequent retrieval. The term is most frequently used to refer to the internal storage of a computer (or a terminal) that can be directly ad-

dressed by operating instructions. In the Omni 3600, files can be stored in battery-backed RAM or in non-

volatile flash memory. Messages Words and symbols appearing on the display screen which inform the user of the terminal of the result of a process, or if an error has occurred. The term prompt is used when the displayed mes-

sage is requesting the user to enter information or to select an option. Modem Modulator/demodulator. A device that con-

verts a digital bit stream into an analog signal to transmit over an analog communication channel

(modulation), and converts incoming analog signals back into digital signals (demodulation). The internal modem in the Omni 3600 base station lets the termi-

nal communicate with a host computer over a dial-up telephone line. Non-volatile memory A memory or storage medi-

um that retains data in the absence of power so that the data is available when power is restored. For the Omni 3600, application files and data files can be stored in battery-backed RAM or non-volatile flash memory, according to the requirements of the appli-

cation. Normal Mode The operating mode for normal transaction processing. The main application (down-

loaded and authenticated) starts and displays an ap-

plication prompt, indicating that the terminal is in normal mode. In this mode, the terminal is ready to process transactions. See also System Mode. Packet A group of bits of fixed maximum size and well-defined format that is switched and transmitted as a composite whole through a packet switching network. Any message that exceeds the maximum size is partitioned and carried as several packets. Packet-switched networks Networks of com-

puters or computing devices in which communica-

tion resources are allocated dynamically on a variety of levels to multiple communicating entities. Messag-

es between entities are partitioned into segments, or packets, with a fixed maximum size. Parameter A variable that is usually assigned a constant value for a specific subroutine, procedure, or function. Parameters stored in terminal memory or in the CONFIG.SYS file(s), enable a host or down-

load computer to identify to terminal configuration. Password A group of characters that identify a user to the system so that they can gain access to the system or part of that system. Passwords are used to ensure the security of computer systems by regulating the amount of access freedom. The pass-

word used to enter system mode is called the system mode password. In the Omni 3600 file system, each file group (Groups 115) also has its own password. PC Abbreviation for personal computer. Usually, PC refers to an IBM-compatible personal computer. Peripheral device In a computer system, any equipment that provides the processing unit with out-

side communication. Typical peripheral devices for a POS terminal include PIN pads, bar code wands, and check readers. Port An opening or connection that provides electri-

cal or physical access to a system or circuit. Also, a connection point with associated control circuitry that allows I/O devices to be connected to the internal bus of a microprocessor. POS terminal A terminal used at the point of sale, which is usually at a merchant site where a customer pays for goods or services received. Information concerning the sale can be entered into the terminal and transmitted to a remote host computer for verifi-

cation and processing. Power pack A unit for transforming and converting electrical power from one AC voltage level to another AC voltage level, or from AC to DC, for electronic de-

vices. Prompt A short message, sent from a process to a user, indicating that the process expects the user to present fresh data. For example, a prompt appears on the terminal display asking the user to enter spe-

cific information. See Messages. Protocol An agreement that governs the proce-

dures used to exchange information between coop-

erating entities. For example, protocols govern the format and timing of messages exchanged between devices in a communication system, such as be-

tween a terminal and a host computer. 146 OMNI 3600 REFERENCE MANUAL GLOSSARY PTID Permanent terminal ID. An optional identifier that can be permanently assigned to a VeriFone ter-

minal at the factory, upon customer request. The PTID has two parts: a 2-digit manufacturer ID (12 for VeriFone) and a unique 8-digit terminal ID. If no PTID is assigned, the default PTID value is 1200000000. Pulse dialing A method of telephone dialing that specifies a phone number by the number of electrical pulses sent. RAM Random-access memory. The type of memo-

ry in which storage locations are addressable and can therefore be accessed in any order. In the Omni 3600 terminal, the RAM (or SRAM) is com-

monly used to store applications and temporary data generated during a transaction. The RAM is battery-backed, meaning that if power is turned off, data stored in this area of volatile memory is not lost. Application files and data can also be stored in the non-volatile flash memory system. By default, files downloaded to the terminal are stored in the RAM of the target file group(s). The RAM file sys-

tem is called drive I:. See Flash memory. Remote host computer A host computer con-

nected to a Omni 3600 base station over a dial-up telephone line to download files or data, or to pro-

cess transactions. The opposite of remote is local. RS232 Also RS-232C. A widely used standard in-

terface that covers the electrical connection between data communication equipment, such as a modem, and data terminal equipment, such as a microcom-

puter or computer terminal. The RS232 interface standard was developed by the EIA (Electronic In-

dustries Association) and is essentially equivalent to the CCITTs V.24 interface. Scroll To move all or part of the information dis-

played on a screen up or down, left or right, to allow new information to appear. For the Omni 3600, text that does not fit entirely within the display area can be scrolled to the left or right using the pound (#) and asterisk (*) keys. Search key Also called key. In the Omni 3600, a short character string used by an application to iden-

tify a keyed file record stored in CONFIG.SYS file(s). For example, *ZA or *OT. A keyed file record consist of two parts: a search key to identify the record, and the variable data stored in the record. See also Keyed file record and CONFIG.SYS file. Serial port A connection point through which digi-

tal information is transferred one digital bit at a time. Same as serial interface. The Omni 3600 base sta-

tion has one serial port, labeled RS232. The main serial port on a download computer is usually as-

signed the device ID, COM1. Signature file A digital file with the filename exten-

sion *.p7s generated in an industry-standard format by the file signing tool, FILESIGN.EXE. The output of the file signing tool is a signature file in an industry-

standard format. SRAM See RAM. Subroutine A software routine that can be part of another routine. When a main routine calls a subrou-

tine, program control is transferred to the subroutine. When the subroutine is completed, control reverts to the instruction in the main routine immediately fol-

lowing the subroutine call. Swipe The action of sliding a magnetic stripe card through a terminal card reader. The Omni 3600 card reader has a bi-directional swipe direction. The user must hold the card so that the magnetic stripe is fac-

es down and towards the printer. System Mode For the Omni 3600, system mode temporarily disables normal mode operations, allow-

ing you to perform local functions such as down-

loads, diagnostics, and other operations that cannot be performed while the application program is run-

ning. At startup, the terminal displays a copyright notice screen that shows the version of Omni 3600 system firmware stored in terminal flash memory, the date it was loaded into the terminal, and the copyright no-

tice. This screen appears for three seconds. To enter system mode, simultaneously press the F2 and F4 keys during this three-second period. Pressing any other key(s) during that period resets the copyright notice screen to display an additional three seconds. See also Local functions and Normal Mode. OMNI 3600 REFERENCE MANUAL 147 GLOSSARY System mode password A unique set of charac-

ters entered by the user to access the system mode local functions of the terminal. A default password is supplied with each terminal. For the Omni 3600 ter-

minal, the default system password set at manufac-

ture is: Z66831. To prevent unauthorized access, change the default password to a confidential password on terminal de-

ployment. Store the new password in a safe place, as it is impossible to restore the terminal default password without sending the unit to VeriFone for service. Telephone download The process of transferring an application program and/or data from a remote host or download computer to a terminal over a tele-

phone line. Telephone jack Also, telephone line wall jack. In-

sert a modular connector into a telephone jack or re-

ceptacle. Also, modular-type sockets for connecting telephone line cords. The Omni 3600 base station has two RJ45-type telephone jacks on the back pan-

el: The TELSET jack is used for pass-through con-

nections; the TELCO jack is used for a direct connection to a telephone line wall jack. Telephone line The standard telephone wiring connecting your phone or terminal to a local or pri-

vate telephone company. Terminal Any device capable of sending and re-

ceiving data over a data link, such as a telephone line or a RS-232 cable. Some terminals, such as the Omni 3600, can print receipts and display informa-

tion and graphics on a screen. Terminal ID An alphanumeric code that identifies a terminal to a download computer. In this way, the download computer can determine what data or ap-

plication programs to download to that terminal. For ZonTalk 2000 downloads, the Omni 3600 terminal ID is stored in the *ZT record in the CONFIG.SYS file. This variable should not exceed 10 characters in length. Not the same as PTID Terminal-to-terminal application upload The process of copying the application memory contents of one terminal to the application memory of another terminal. A terminal-to-terminal application upload requires that the base stations of the sending and re-

ceiving terminals be connected to each other by a serial cable. See also Back-to-back application download. Tone dialing Also called touch-tone dialing. A method of telephone dialing that uses different pitched tones to specify a phone number. See also DTMF. Track 1, 2, or 3 data Information stored on tracks 1, 2, or 3 of a debit or credit card magnetic stripe, which can be read by a magnetic card reader device, such as the one that is integrated in the Omni 3600 terminal. Transaction An exchange of data resulting in a transfer of goods, services, value, and/or information between two parties. Variable A string of characters that denotes some value stored within the computer and that can be changed during execution. A variable may be inter-

nal to a program, in which case it is held in memory, or external if the program must perform an input op-

eration to read its value. See Parameter. Volatile memory A type of memory where the contents are destroyed if the power supply to the memory is interrupted. When volatile memory, such as SRAM, is used for crucial applications, it is often back up by battery-supplied power. Compare with Non-volatile memory. Wireless The Omni 3600 terminal a continuous, virtual link through a radio connection to upload transaction data files to and download applications and OS updates from your merchant business pro-

cessor. This connection is stand-alone, not requiring unit docking. See Docking/Docked. 148 OMNI 3600 REFERENCE MANUAL A accessories 126 cables 126 documentation 127 ordering 126 power packs 126 telco cable 126 thermal printer paper 127 VeriFone cleaning kit 127 ALPHA key 33 antenna 21 installation 21 orientation 21 replacement 22 application debugging 52 application partition certificate 98 ASCII table 139 B backspace key 33 back-to-back downloads 57, 58 file authentication 74 redirect files during 68 battery extend battery life 14 battery status 56 C cables ordering 126 cancel key 33 cancel tone 14 certificate tree 107 certificates add new certificates 109 application partition certificate 98 certificate tree 107 default signer certificate 108 development certificates 107 download sponsor and signer certificates 109 hierarchical relationships 98, 107 platform root certificate 98 signer certificate 99 sponsor certificate 98 certificates and signature files 69 INDEX check readers 30 clear all flash files 46 clear RAM 46 clock 44 CONFIG.SYS file 60 and file groups 63 CONFIG.SYS files 52 credit/debit card transactions 20 D data entry modes normal mode 32 system mode 32 date and time 44 determine last reset 49 DDL.EXE 59 debugging 53 debugging applications 52 default signer certificate 108 defragment flash 46 defragment flash memory 44 development certificates 107 diagnostics 54, 119 digital certificates 107 direct connection 28 display ASCII table 139 troubleshooting 120 display contrast 43 display panel test 54 documentation 126 ordering 127 downloads applications and related files 59 back-to-back 57 application downloads hardware checklist 91 software checklist 91 cable connection 80 set up environment 78 using MOD10 adapters 80 back-to-back application 58 by telephone 58, 88 hardware checklist 88 software checklist 88 OMNI 3600 REFERENCE MANUAL 149 INDEX E certificates 109 definition 57, 145 differences 62 direct 58, 80, 81 cable connections 78, 79 checklist 81 hardware checklist 80 operating system downloads 85 hardware checklist 85 software checklist 85 software checklist 80 with MOD10 adapter 79 direct download utility (DDL) 59 download types 60 effect on existing files and data 76 file authentication and back-to-back application downloads 74 file authentication and downloading a new oper-

ating system 73 file authentication and downloading applica-

tions to specific file groups 72 file authentication and optimizing available memory space 75 file authentication and timing considerations 75 file authentication procedure for 70 file authentication process 59 file authentication requirements 69 certificates and signature files 69 file compression 76 file groups 45 file system 62 full and partial downloads 60 full application 60 full operating system 61 full OS 85 host PC 57 MOD10 adapter 58, 77 operating system files 59 OS files and file authentication 73 partial 85 partial application 60 partial operating system 61 redirecting files during 64 redirecting files to flash memory 65 redirecting files to other file groups 66 redirection of files during downloads 64 back-to-back downloads 68 how operating system files are redirected 68 using DDL.EXE to automatically redirect files 67 restrictions on redirecting files to other file groups 66 150 OMNI 3600 REFERENCE MANUAL rules for the file system 63 select port 45 select type 45 set up the download environment 77 set up the download environment for application or OS downloads by telephone 77 setting up the download environment 77 store the main application in File Group 1 63 support for multiple applications 62 physical and logical access to file groups 63 telephone 80 terminal configuration settings 59 tools 58 types of download operations 57 use of RAM and flash memory 63 defragmenting the flash 64 implications for data transfers 63 wireless 57, 58 E enter key 35 error log 52, 53 F file authentication 69

*GO variable executes application following authentication 106 and downloads 70 authenticating files in specific file groups 112 back-to-back downloads 74 certificate file size 114 certificates 98, 107 add new certificates 109 application partition certificate 98 certificate tree 107 default signer certificate 108 development certificates 107 download sponsor and signer certificates 109 hierarchical relationships 98, 107 platform root certificate 98 signer certificate 99 sponsor certificate 98 confirm successful authentication 106 deployment process 102 development process 99 digital signature 98 downloading OS files and 73 failed authentication 106 file signing 114 file signing operating system files 114 files used 98 FILESIGN.EXE 114 command-line mode 115 graphical interface mode 115 switches for command-line entries 116 syntax 117 system requirements 114 guidelines for downloading specific file types 114 keys 98 private cryptographic key 98 public cryptographic key 107 non-executable application files 105 pre-deployment process 101 relationship to file groups 111 signature file size 114 VeriFone Certificate Authority 97 VeriShield security architecture 97 file group password 39 file groups 38, 62 file authentication and 111 keyed records 49 password 39, 45, 51 passwords 46 store main application in Group 1 63 file system 62 files CONFIG.SYS 52 keyed 52 placing in terminal directories 64 FILESIGN.EXE 114 flash 45 clear all files 46 defragment 46 display memory used 48 flash memory 63 defragment 44 downloads to 44 full application download 60 full download 45 full OS download 85 function keys 31, 33 G GIDs 62, 63 I install terminal power pack 11 installation antenna 21 direct connection 28 MSAM cards 16 INDEX G optional device(s) 29 paper roll 14 pass-through connection 29 peripherals 30 power connection (base unit) 26 printer test 16 terminal location 7 unpack the shipping carton 8 using the smart card reader 20 integrated PIN pad 49 diagnostic 55 key loading mode 55 K key value 50, 52 keyboard test 54 keyed files 52 keyed records 49 keypad troubleshooting 122 keypad description 32 keys 31, 33 ALPHA 33 backspace 33 cancel 33 cancel/off 14 enter 35 enter/on 14 public cryptographic key 107 L location recommendations 7 M magnetic card reader 20 magnetic card reader test 54 maintenance returning a terminal 123 memory space optimization 75 MOD10 adapter 58, 77 installation 77 modem country code 49 MSAM cards 16 cardholders 17 installation 16 multiple applications support for 62 OMNI 3600 REFERENCE MANUAL 151 INDEX N N non-protected records 52 O operating system downloads 61 optimize memory space 75 optional devices, connecting 29 P paper roll installing 14 partial application downloads 60 partial download 45 partial OS download 85 pass-through connection 29 password 38, 39 passwords 39 file group 46, 51 manufacturers default 48 peripherals 29 cables 126 check readers 30 installation 30 printers 30 PF keys 31, 35 PIN pad 49 platform root certificate 98 Port pinouts 141 ports downloads and 45 peripheral devices 29 power 11 Telco 28 telephone line 28 Telset 28 power pack 126 ordering 126 terminal connection 11 power port 11, 26 printer display information on 55 install paper 14 out-of-paper indicator 14 paper roll 14 paper storage 14 power-on test 16 test in system mode 16 troubleshooting 120 printer paper ordering 127 152 OMNI 3600 REFERENCE MANUAL private cryptographic key 98 programmable function keys 35 protected records 52 public cryptographic key 107 R RAM 45, 63 clear 46 display memory used 48 remote diagnostics 119 reset date and time 49 restart the terminal 44 S SecureKit 55 service returning a terminal 123 signature file 114 signer certificate 99 SIM card installation 18 smart battery 14 smart battery status 56 smart card transactions 20 smart card reader 20 sponsor certificate 98 system messages 119 system mode 37 CONFIG.SYS 52 debugging applications in 53 diagnostics in 54 display memory used 48 display panel test 54 download port selection 45 download type 45 entering 42 error log display 53 file group password 46 file groups 38, 45 integrated PIN pad 49 IPP test 55 keyboard test 54 local and remote operations 37 mag card reader test 54 menu 1 43 menu 2 44 menu 3 47 menu 4 52 menu 5 54 menu 6 55 INDEX T magnetic card reader 54 time 44 timing considerations and downloads 75 troubleshooting display 120 keypad 122 printer 120 remote diagnostics 119 serial port connection 121 system messages 119 transactions 121 U upload 57 V variables 60 VeriCentre Download Management Module (DMM) 52, 58 VeriFone Certificate Authority 97 VeriShield 97 W wireless downloads 58 wireless transactions 20 Z ZonTalk 2000 52, 59 menu 7 56 menus 40 password 51 procedures 41 RAM 46 restart the terminal 44 terminal downloads 45 tests 54 system mode operations protected and non-protected records 52 system password 39 T telco cable, ordering 126 Telco port 28 telephone connections direct 28 telephone downloads 80, 88 telephone line connections pass-through 29 telephone line cord, see telco cable. 126 Telset port 28 terminal accessories 126 ASCII table for display 139 clock 44 configuration information 48 data entry modes 32 documentation 126 downloads 45 file editor 52 keys 31 life of 49 number of resets 49 password 38, 39 repair 123 replacement 123 restart 44 service and support 123 specifications 125 troubleshooting 120 turn off 14 turn on 14 verify status 38 terminal features 10 optional peripheral ports 29 Telco port 28 Telset port 28 tests display panel 54 integrated PIN pad 55 keyboard 54 OMNI 3600 REFERENCE MANUAL 153 VeriFone, Inc. 2455 Augustine Drive Santa Clara CA 95054-3002 Tel: 800-VeriFone (837-4366) www.verifone.com Omni 3600 Reference Manual Part Number 22379, Revision A VERIX OPERATING ENVIRONMENT SOFTPAY E-PAYMENT APPLICATION VERIX DEVELOPER TOOLKIT DEVELOPMENT TOOLS VERISHIELD SECURITY ARCHITECTURE OMNI 37XX HAND-OVER-COUNTER MULTI-APPLICATION APPLIANCES OMNI 33XX MULTI-APPLICATION APPLIANCES OMNI 3600 HAND-HELD RADIO MODEM APPLIANCES VERICENTRE APPLIANCE MANAGEMENT SUITE

 

 

VeriFone, Inc. 2455 Augustine Drive Santa Clara CA 95054-3002 Tel: 800-VeriFone (837-4366) www.verifone.com Separate Power Sources Some peripherals require a separate power source. Before connecting a check reader or similar device, turn off power to the terminal. Peripherals Before connecting any peripheral device, turn off power to the terminal. Turn on power only after you are finished connecting the peripheral device(s). For complete information about peripheral installation and use, please refer to the user documentation supplied with those devices. Disconnecting Power Disconnecting power during a transaction may cause transaction data files that are not yet stored in terminal memory to be lost. Surge Protectors To protect your terminal against possible damage caused by lightning strikes and electrical surges, you may want to install a power surge protector. Location Electrical Considerations CAUTION: Due to risk of electrical shock or terminal damage, do not use the terminal near water, including a bathtub, wash bowl, kitchen sink or laundry tub, in a wet basement, or near a swimming pool. Also, avoid using this product during electrical storms. Avoid locations near electrical appliances or other devices that cause excessive voltage fluctuations or emit electrical noise (for example, air conditioners, neon signs, high-frequency or magnetic security devices, or electric motors). Equipment Damage Carefully inspect the shipping carton and its contents for any damage. If the terminal or any product component appears damaged or tampered with, immediately notify the shipping company and your VeriFone distributor or service provider. CAUTION: Do not use a terminal that has been damaged or tampered with. Repairs Unless otherwise instructed in this document, do not, under any circumstances, attempt any service, adjustments, or repairs on this equipment. Instead, contact your local VeriFone distributor or service provider for assistance. Failure to comply may invalidate the product warranty. Omni 3600 Certifications and Regulations FCC Compliance Manufacturer: VeriFone, Inc. Model: Omni 3600 FCC Part 15 Class B This device complies with Part 15 of the FCC Rules. Operation is subject to the following two conditions: (1) this device may not cause harmful interference, and (2) this device must accept any interference received, including interference that may cause undesired operation. SAR Labeling Mobitex USA To comply with the FCC RF exposure requirements, bystanders and parts of the users body other then the extremities must be at least 15.0mm away from the device. CDMA USA SAR compliance for body worn operating configurations is limited to the specific belt clips / holsters / accessories that have no metallic component in the assembly. The highest reported SAR values for Omni 3600C under the FCC ID B32OMNI3600C are:

PMS modes (Part 22) Body-worn 0.0056mW/g. The highest reported SAR values for Omni 3600D under the FCC ID B32OMNI3600D are: PMS modes (Part 22) Body-worn 0.309mW/g, PCS mode (Part 24) - Body-worn: 0.232mW/g. Brazil

"""O terminal Omni 3600 atende aos limites da Taxa de Absoro Especfica referente exposio a campos elcticos, magnticos e electromagnticos de radiofreqncias adoptados pela Anatel."""

GSM/GPRS USA SAR compliance for body worn operating configurations is limited to the specific belt clips / holsters / accessories that have no metallic component in the assembly. The highest reported SAR values under this FCC ID are: PMS modes (Part 22) Body-worn 0.245mW/g, PCS mode (Part 24) - Body-worn: 0.218mW/g. Australia Required Warning Statement Please switch off and do not operate the equipment when in an area with a potentially explosive atmosphere, such as refueling points, fuel depots or storage areas, chemical plants, and blasting operations. Electrical Location Environmental Considerations LI-ion Battery ModuleRechargeable Battery Unit Caution Do not plug the power pack into an outdoor outlet or operate the terminal outdoors. It is not waterproof or dustproof, and is for indoor use only. Any damage to the unit from exposure to rain or dust may void your warranty. Do not use the terminal where there is high heat, dust, humidity, moisture, or caustic chemicals or oils. Keep the terminal away from direct sunlight and anything that radiates heat, such as a stove or a motor. Cleaners and Solvents Do not:

disassemble, crush, puncture, or incinerate in fire. short circuit contacts. expose to temperatures exceeding 140 F (60C). Power Packs Never use thinner, trichloroethylene, or ketone-based solvents to clean the terminal they may deteriorate plastic or rubber parts. Do not spray cleaners or other solutions directly onto the keypad or display. For best results, use a VeriFone Cleaning Kit or a clean cloth dampened with water and mild soap. To remove stubborn stains, use alcohol or an alcohol-based cleaner. Location Ease of Use Select a location for your terminal that contributes to its ease of use:

A location convenient for both merchant and cardholder.

A flat support surface, such as a countertop or table.

A location near a power outlet and a telephone/modem line connection. WARNING! Changes or modifications to this unit not expressly approved by the party responsible for compliance could void the users authority to operate this equipment. Omni 3600 Certifications and Regulations VeriFone Part Number: 22475 Revision E 2003 VeriFone, Inc. All rights reserved. Before you connect the terminal power pack to an electrical outlet, check that the on/off power switch on the terminal is off. If the terminal does not have an on/off switch, check that the power cable connector is removed from the terminals power port. or When connecting the terminal to a power pack, always connect the three-pronged plug of the power pack to an electrical wall outlet first. Then connect the power cable to the terminals power port. AC Adapter The AC adapter is designed to ensure your personal safety and to be compatible with this equipment. Please follow these guidelines:

Do not use the adapter in a high moisture environment. Never touch the adapter when your hands or feet are wet.

Allow adequate ventilation around the adapter. Avoid locations with restricted airflow.

Connect the adapter to a proper power source. The voltage and grounding requirements are found on the product case and/or packaging.

Do not use the adapter if the cord becomes damaged.

Do not attempt to service the adapter. There are no serviceable parts inside. Replace the unit if it is damaged or exposed to excess moisture. continued

Omni 3600 GPRS Declaration of Conformity Omni 3600 GSM Declaration of Conformity