Tradewind Version 9.5 Release Notes

E70175-01

TRADEWIND®

Tradewind

2 of 20

Notice

This document contains the product update information as of the date of publication.

© 2008 MICROS-Retail. All rights reserved.

This document is confidential and may be legally privileged. The material is subject to copyright protection. Any review, retransmission, dissemination, or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited.

Trademark Acknowledgments

Xstore, Store21, Tradewind, XBR, CWStore, CWDirect, Balance, Relate, Enterprise Merchandising, Locate, eOne, Creations, and Collaborate are registered trademarks, trademarks, and service marks of MICROS-Retail.

All other company and product names may be trademarks of their respective companies.

Contact Information www.micros-retail.com

30500 Bruce Industrial Parkway

Cleveland, OH 44139 USA

Toll Free: 888.328.2826

Tel: 440.498.4414

Fax: 440.542.3043

1800 West Park Drive

Westboro, MA 01581

Tel:508.655.7500

Fax:508.647.9495

MICROS Systems, Inc.

www.MICROS.com

7031 Columbia Gateway Drive

Columbia, MD 21046-2289

Tel: 443.285.6000

Tradewind

3 of 20

Table of Contents

RELEASE OVERVIEW ................................................................................................................................. 5

DOCUMENTATION ...................................................................................................................................... 5

FEATURES ................................................................................................................................................... 5

#233369: Pinpad Development for Base - Verifone Mx Integration .......................................... 6

SECURITY IMPROVEMENTS ...................................................................................................................... 6

#161144: Database Security ..................................................................................................... 6

#168541: Update TWShell.exe for PCI compliance .................................................................. 6

#199610: Launch Tradewind without Administrator Rights ....................................................... 6

#200950: Tradewind Displays an Error Message at Startup if it is Using an Expired Encryption Key ............................................................................................................................................ 7

#201607: Employee Password Changes .................................................................................. 7

CLOSING ...................................................................................................................................................... 8

#185727: Allow the Close to Continue if Scheduled Reports Don’t Complete .......................... 8

Setup: .................................................................................................................................... 8 #200217: Remove APE Logic Key ............................................................................................ 8

DISCOUNTS/DEALS .................................................................................................................................... 8

#209626: Make Loading Deal Information Configurable ........................................................... 8

Setup: .................................................................................................................................... 8

CUSTOMER .................................................................................................................................................. 9

#204112: Capture Customer after Receipt ................................................................................ 9

Automatic Customer Prompts Not Changed .......................................................................... 9 Setup: .................................................................................................................................. 10

AUTHORIZATIONS .................................................................................................................................... 10

#211621 and #201961: Integrate Tradewind with Paymentech – Credit/Debit/Gift Card (DAS) ................................................................................................................................................ 10

Post Voids ............................................................................................................................ 10 Posting Manual Authorizations ............................................................................................ 10 Setup: .................................................................................................................................. 10

#201965: Implement Host Capture with DAS/Paymentech ..................................................... 11

Setup: .................................................................................................................................. 11 #217240: Add Support for XPay .............................................................................................. 11

Log Files .............................................................................................................................. 12

Tradewind

4 of 20

Setup: .................................................................................................................................. 12

RECEIPT CHANGES .................................................................................................................................. 13

#234497: Print Full Gift Card Number on Customer Receipt for Activations ........................... 13

DATABASE CHANGES ............................................................................................................................. 13

#203096: Support for MS SQL 2005 ....................................................................................... 13

New Control Flags: .................................................................................................................. 13

New TW_Setting Entries: ........................................................................................................ 13

New Tables Added: ................................................................................................................. 13

Table Structures Changed: ..................................................................................................... 14

REGISTRY AND INSTALLATION CHANGES .......................................................................................... 15

Registry Changes .................................................................................................................... 15

Installation Changes ................................................................................................................ 15

ISSUE RESOLUTION ................................................................................................................................. 16

CERTIFIED PLATFORMS .......................................................................................................................... 18

Tradewind

5 of 20

Release Overview

This document contains the release notes for Tradewind version 9.5. These release notes cover new features and enhancements for this version, the resolved issues that were identified in previous versions, and current issues as of the release date.

Note: The rebranding for the latest version of this documentation set is in development as part of post MICROS acquisition activities. References to former MICROS product names may exist throughout this existing documentation set.

Documentation

The following documentation for Tradewind version 9.5 will be available on or about the date indicated.

Document Title Rev # Release Date Description

Tradewind Configuration Guide

1 9/10/2007 This manual guides users through the processes and procedures required to set up and configure Tradewind.

Tradewind Database Dictionary

1 3/31/2008 This document provides a description of every database table in Tradewind, including the name, data type, and description of each field.

Tradewind Deal Pricing Guide

1 11/12/2007 This manual guides users through deal creation and configuration.

Tradewind Implementation Guide

1 4/30/2008 This manual provides step-by-step procedures for installing Tradewind and Tradewind components, including TradeCenter, TradeRoute, and optional modules.

Tradewind Manager's Manual

1 9/11/2007 This manual guides managers through the tasks that they will be required to perform on a regular basis.

Tradewind Reports Manual

1 11/08/2007 This manual describes the reports available in Tradewind and the procedure for running each report.

Tradewind Training Manual

1 12/21/2007 This manual provides step-by-step procedures describing basic user functions.

TradeCenter Manual 1 4/30/2008 This manual offers descriptions of TradeCenter processes and the procedures required to implement them.

Features

Tradewind version 9.5 includes several enhancements and new features. The sections below describe some of the more significant of these improvements.

Tradewind

6 of 20

Hardware

#233369: Pinpad Development for Base - Verifone Mx Integration Tradewind is now integrated with the Verifone Mx series of devices. This integration includes using Verifone Mx series devices for the pole display, MSR, PINPad and signature capture devices for a register. The Verifone Mx devices with which Tradewind is integrated include the Mx830, Mx850 and Mx870 devices.

This modification extends the hardware options available with Tradewind and permits more flexibility in system configuration.

Security Improvements

#161144: Database Security The ability to create user accounts with varying security levels has been added to the Tradewind database.

Users are no longer required to have administrator privileges to perform any activity in the database, including queries. By adding security levels to database logins, access permissions can be managed and restricted.

#168541: Update TWShell.exe for PCI compliance The TWShell.exe application was not PCI compliant. Changes were made to the application to improve its security to this standard.

First, the algorithm used to determine the password protecting the buttons in TWShell.exe has been changed. The algorithm used to determine this password is now configurable. This new, configurable value is created in plain text by corporate, downloaded by the store(s) and both implemented and hidden by TWShell.exe.

As part of this functionality, corporate now has a utility for creating and testing the password algorithm. Once the password has been created and tested, the utility creates files that are downloaded (along with other files) by the stores. The password change then runs as an APE at each store.

Second, the key combination CTRL-SHIFT-ESC no longer activates the Windows Task Manager. Note: The user still has the ability to access the Windows Task Manager through the Shell button in the TWShell.exe Managers Menu.

#199610: Launch Tradewind without Administrator Rights A new application has been created called DTVStartup.exe. This application is installed as part of the server and register installations. It is installed to the application path that is entered during the installation.

This new functionality will eliminate the need for the registers to be logged into the server with administrator rights. However, DTVStartup.exe will still require an administrator username and password that will need to be entered during installation:

Tradewind

7 of 20

Figure 1 - POS User Name and Password

In Figure 1, the administrator username and password will be used by DTVStartup.exe, not Tradewind.

#200950: Tradewind Displays an Error Message at Startup if it is Using an Expired Encryption Key During Tradewind startup, while doing the encryption check, if there are only expired keys in the cipher file the application will display a message to the user indicating the encryption test failed. Additionally, the error message will be written to the registers Error.txt file with an error #95 – All Keys Expired message. This file can be pulled back from the corporate office to troubleshoot the issue and provide a new cipher file.

#201607: Employee Password Changes One of the recommendations that resulted from the PABP Validation assessment was the need to protect user passwords in Tradewind. These proposed changes are directed toward strengthening the user password security for the Tradewind application.

Employee passwords will be encrypted when written to the Tradewind database. This functionality will be treated as default functionality but can be turned off if the client does not wish to encrypt employee passwords. In order to turn off employee password encryption, contact your Project Manager.

When a user logs on to Tradewind, the application will perform a lookup on the password based on the employee ID and password that were entered. If the digest values match, the user will be allowed into the system. If the digests do not match, system entry will be denied as it is today. In addition to the Employee_Password table, passwords in the Menu_Approval and POS_Control tables will also be hashed. If a customer is going to upgrade to this version, a utility will need to be run to hash all existing passwords unless they shut this feature off.

Tradewind

8 of 20

Closing

#185727: Allow the Close to Continue if Scheduled Reports Don’t Complete Tradewind is not affected by this change. Instead of running scheduled reports from Close Manager, this update calls an external application, TWDRunSR.exe to run the Scheduled Reports. After a specified number of minutes, using the value specified in the TW_Setting table, if the application is still active Close Manager will stop the job and continue with the remaining closing process. A report may not necessarily be created but the creation of nightly files is not affected.

Setup:

New entry in TW_Setting table:

VALUES ('CloseManager', 'Scheduled Reports', 'Timeout', '0')

Server installs new executable, TWDRunSR.exe, to application path specified during the install.

#200217: Remove APE Logic Key The APE_KEY field has been removed from the Automatic_Process_List table. Previously, when Close Manager processed global APEs for individual registers, the APE_KEY was generated for each APE. This key was generated using the Register_ID and the fields from Automatic_Process_List table. The encrypted value was then stored in the Table. Finally, TWRegisterupdate compared this key with the key generated by individual registers to process the APE. All of this logic was removed and APE_KEY is no longer used to process APEs.

Discounts/Deals

#209626: Make Loading Deal Information Configurable Normal deal pricing functionality remains. If the new control flag #283 - Load deals before each tran? is set to "False" and deals are loaded during the day, they will not apply until Tradewind is shut down and restarted. If this new flag is set to "True" and deals are loaded during the day, they will be loaded at the start of the next transaction and will be applied, if applicable.

Setup:

New control flag: #283 – Load deals before each tran?

If this flag is false, deals will be loaded once when Tradewind is started up and will not be loaded again.

If this flag is true, deals will not be loaded when Tradewind is started up. Instead, deals will be loaded with each new transaction.

Tradewind

9 of 20

Customer

#204112: Capture Customer after Receipt Tradewind can be configured many different ways to automatically prompt for customer information. The configuration is done mostly with control flags, but some require database settings as well.

With this modification, most of those automatic prompts will be moved until after the receipt for the transaction prints. Some of the prompts cannot be moved and must be displayed at the correct time, such as when getting delivery information for a mail check refund.

A new control flag #280 - Get Customer After Rcpt? was added to determine when Tradewind should prompt for customer. When this flag is true, Tradewind will delay most automatic prompts for the customer until after the receipt prints. However, if the transaction was aborted, the customer prompt will not be displayed. If it is false, Tradewind will function as it does currently.

Two other control flags were added as well, #281 - Get Phone Nbr After Rcpt? and #282 - Get Postal Code After Rcpt? The functionality behind these flags is described below.

The following control flags can be set up so Tradewind automatically prompts for customer information. The functionality surrounding these flags will be changed to prompt for the customer after the transaction if the new control flag is set to true.

49 – Cust prmpt before transaction?

50 – Cust prmpt after transaction?

51 – Force customer on return?

53 – Force customer on send sale?

153 – Force Customer Before Return?

163 – Force Loyalty Number on Return

197 – Force Cust Before/After Prmpts

200 – Force Cust Old/No Rcpt Return

210 – Force Cust on Large Refunds

Automatic Customer Prompts Not Changed

There are some cases where Tradewind must prompt for customer information during the transaction and cannot wait until after the receipt prints. The new control flag will not have any affect on these prompts. They are as follows:

Prompting for customer to send merchandise to on a send sale

Prompting for customer on a special order

Prompting for customer on a layaway

Prompting for customer on Employee Transactions where the employee entered doesn’t have a customer ID

Tradewind

10 of 20

If either flag #281 - Get Phone Nbr After Rcpt? or flag #282 - Get Postal Code After Rcpt? is true, the prompts will be displayed after the transaction has been written to the database and the receipt(s) are printed. This also includes any loyalty receipts, tickets, damaged documents, gift receipts, check franking and tax exempt form franking.

Setup:

New control flags:

#280 - Get Customer After Rcpt?

#281 - Get Phone Nbr After Rcpt?

#282 - Get Postal Code After Rcpt?

Authorizations

#211621 and #201961: Integrate Tradewind with Paymentech – Credit/Debit/Gift Card (DAS) Tradewind will allow gift card authorizations to be performed through DAS to Paymentech. The only changes required from current Brightcard functionality are as follows:

allow posting of manual authorizations

disallow voiding transactions that contain manually authorized gift cards

use a different existing resource string when asking if you want to manually authorize

Post Voids

Paymentech does not allow post voids of manually authorized gift cards. Therefore, when attempting a post void, Tradewind will check the new TW_Setting record to determine which gift card processor is being used. If the value is Paymentech, then Tradewind will determine if there are any manually authorized gift cards in the transaction. If there are, a message will be displayed and the transaction cannot be voided.

Posting Manual Authorizations

If the new TW_Setting record for gift card processor is set to Paymentech, Tradewind will post manual authorizations for gift cards.

Tradewind will allow posting of manual gift card authorizations during the nightly close and through the existing Post Manual Auths menu button on the Non-Financial menu. Please note that this menu button will also post manual authorizations for credit cards based on host capture which was also implemented in this release. There will not be two separate menu buttons for credit cards and gift cards.

Setup:

Paymentech Gift Card Setup

POS_Control.AUTH_PKG_ID = 7

Tradewind

11 of 20

TW_Setting

o CATEGORY = Gift Cards

o PROPERTY = Gift Card Processor

o VALUE = Paymentech

Electronic_Gift_Card_Control

o MANUAL_AUTH_VALIDATION_TYPE = 0

o DUP_MANUAL_AUTH_ALLOWED_FG = 1

Electronic_Gift_Card_Type

o SERIAL_NBR_LEN = 0

o BIN_NBR = 0

Merchant_Info: the following fields must be populated with customer-specific information provided to the retailer by Paymentech:

o Merchant_ID, UserName, Password and ClientId

#201965: Implement Host Capture with DAS/Paymentech Tradewind supports “host capture” mode when using DAS with Paymentech. That is where electronic authorizations are sent at the time of the transaction, and if successful are considered complete. No further processing or settlement is required. If the initial electronic authorization fails, the cashier can call for a manual authorization. This transaction then needs to be stored in the database and re-submitted as an electronic authorization at some point in the future (i.e., store and forward transaction).

Setup:

Control_Flag - #279 – Use Host Capture?

If True, Tradewind will have the functionality of doing Host Capture by having the store close process do the posting of manual authorizations and also allowing users to do the same thing any time during the day by selecting the menu button Post Manual Authorizations.

If False, terminal capture mode will be used as is done today.

#217240: Add Support for XPay This modification adds support for XPay to Tradewind. Additionally, customers will be able to use XPay and Relate Gift Cards together. Tradewind will authorize credit and debit cards and checks the same way it does today with other processors. If a connection to the XPay server is not available, manual authorizations on credit cards and checks will be accepted. Manual authorizations on debit cards are not permitted. A failed authorization receipt will print for failed debit card authorizations.

For debit card authorizations, Tradewind will be required to send an acknowledgement back to XPay indicating that it received the response and processed it successfully. The authorization will not be considered complete unless the acknowledgement message is received by XPay. If

Tradewind

12 of 20

the acknowledgement message does not make it to XPay, XPay will reverse the request automatically and Tradewind will treat the request as failed.

In-store settlement is not supported with XPay. Settlement is performed at the corporate office. All electronic and manually authorized credit cards and checks must be included in the settlement file.

Tradewind will communicate with XPay through XMessaging. This requires a secure HTTPS address to be defined, telling Tradewind where the XPay server is located. The Auth_Server_Address table will be used to do this. A new field named Connection_URL was added. If this field is populated, the IP_Address and IP_Port fields should be left blank.

Important: If the address does not begin with “https”, the record will be ignored and Tradewind will look at the next available record for that register. If no records are found in the table with a URL starting with “https”, then Tradewind will display the usual message that it cannot connect to an authorization server and that electronic authorizations will be disabled. Tradewind will handle backup connections to different XPay servers. The Auth_Server_Address table should be populated appropriately as it is with other processors to handle connections to multiple servers.

Note: Paymentech is the only processor that was tested with Xpay and Tradewind in version 9.5.

Log Files

Tradewind will create separate files for logging XPay authorizations. These files will reside in the Tradewind application path and will be named mmddyyTWXPay.log, where mmddyy will be the date when the XPay authorizations are performed. These log files will be stored on the registers, not the servers. Only non-dedicated servers will have log files.

In the database, a record has been added to the Hist_Limits table for XPay history logs. The default purge limit is 10 days of files. The purge date will be determined by system date, not business date. The purge will be run at system startup rather than during the close process.

Setup:

POS_Control.AUTH_PKG_ID

o Set to 14 if using XPay for credit, debit and check authorization and Relate for gift card authorization.

o Set to 12 if using XPay for credit, debit and check authorization and TradeCenter for gift card authorization.

XPay does not support credit card refunds or voids.

o Tender.AUTHORIZE_RFND_FG should be set to false for all credit card tenders.

o Tender.AUTHORIZE_VOID_FG should be set to false for all credit card tenders.

Auth_Server_Address.CONNECTION_URL must be populated with the secure HTTPS address for the XPay server.

Auth_Provider - define a new Auth_Provider_Id to be used with XPay.

o Tender.AUTH_PROVIDER_ID should match the new ID. This field must be populated for each tender using XPay.

Tradewind

13 of 20

Receipt Changes

#234497: Print Full Gift Card Number on Customer Receipt for Activations This modification provides Tradewind with the ability to print the full account number for a gift card on a customer receipt upon the activation of the gift card. This option only allows the gift card number to be printed in full on the receipt for the transaction in which the gift card is activated; all other transaction receipts mask gift card numbers.

To implement this new functionality, Tradewind has a new control flag:

#284 - Full GC For Issue On Cust Rcpt.

If this flag is TRUE, full gift card numbers are displayed on the customer receipts for the transactions in which the gift cards are activated. Gift card numbers are masked on all other receipts.

If this flag is FALSE, gift card numbers are masked on all transaction receipts.

Database Changes

#203096: Support for MS SQL 2005 This modification allows Tradewind to use Microsoft SQL Server 2005 as its database platform. This is in addition to SQL Server 2000, which remains a certified, supported database platform for Tradewind.

New Control Flags:

CTRL_CD CTRL_CAT CTRL_DESCR

280 100 Get Customer After Rcpt?

281 100 Get Phone Nbr After Rcpt?

282 100 Get Postal Code After Rcpt?

283 100 Load Deals Before Each Tran?

284 100 Full GC For Issue On Cust Rcpt.

New TW_Setting Entries:

APPLICATION CATEGORY PROPERTY VALUE

CloseManager Scheduled Reports Timeout 0

Tradewind Compression COMPRESS_PSWD_FG Null

Tradewind PinPad Slot Number 1

New Tables Added:

TRW_Roles

Tradewind

14 of 20

TRW_Logins

TRW_Role_Logins

TRW_Object_Permission_Roles

TRW_DB_Permission_Roles

Table Structures Changed:

Renamed DAS_Merchant_Info to Merchant_Info

Merchant_Info –

o Added - STORE_CITY

o Added - STORE_ZIP_CODE

o Added - ACQUIRING_INSTITUTION_ID

o Added - CLIENT_ID

o Dropped - CLIENTID

Auth_Server_Address

o Added – CONNECTION_URL

o Changed – IP_ADDRESS – varchar (20)

o Changed – IP_PORT – int

Register

o Added – RFID_FG

Settlement

o Added – PS2000_DATA

o Added – BANK_REFERENCE_NUMBER

o Added – POSTED

o Added – TRACE_NBR

Automatic_Process_List

o Dropped – APE_KEY

Employee_Password

o Changed – PSWD – varchar (40)

Menu_Approval

o Changed – APRV_PSWD – varchar (40)

POS_Control

o Changed – UNLOCK_RGST_PSWD – varchar (40)

Electronic_Gift_Card_Detail

o Added – REFERENCE_NBR

Tradewind

15 of 20

Signatures

o Added – Device_Type

Registry and Installation Changes

Registry Changes

All paths saved to the registry are saved as UNC paths, rather than the mapped drive letter.

The administrator Username and Password required for DTVStartup.exe are stored in the registry.

Password for backup/restore of the database is stored in:

o HKEY_CURRENT_USER\Software\Tradewind\

BackupPassword

Installation Changes

User can select the NCR 7167 as the receipt printer for double-byte character sets.

Removed InStore Plus Emulation as an available interface.

Added the option to choose XPay as the credit authorization processor.

Added a prompt for the POS User Name and Password required by DTVStartup.exe.

Removed PaylinX as a valid credit authorization processor.

Server and Register Installation Changes

o User is prompted for a password to backup and restore the database.

Close Manager reads this registry value, decrypts it and creates a database backup file.

Tradewind reads this registry value, decrypts it and restores the database file.

The password is required to install BackupRestore.exe.

Tradewind

16 of 20

Issue Resolution

The following list summarizes the corrective actions for previously detected issues:

Category Reference # Description

CC Auth 209625 Voids didn't always write to Pmt_Authorization

CC Auth 215298 Was not saving Visa Card Level Indicator from authorization response

CC Auth 232440 Debit acknowledgement message was not formatted correctly

Closing 204797 Offline closing problem when system error occured during close

Closing 185716 System was getting stuck at either Abortable Portion or Matching Time Card Entries

Closing 204802 Fixed fatal overflow error when closing a till from another register and the till number is greater than 33000

Closing 205806 Overflow error in CloseOtherTills

DB 203875 Fixed Restore.log archive logic

DB 234497 Repaired errors in the database backup and restore utility BackupRestore.exe

Discount 204798 If an employee discount was performed after promotionally priced items were added to a transaction, the employee discount was applied to the promo items

Discount 205807 Discount threshold did not work with coupons

Employee 207425 Tabbing through fields in Employee Maintenance did not follow a logical order

Environment 205073 Users are now prevented from entering blank responses in the Question and Answer prompts

Tradewind

17 of 20

Category Reference # Description

Gift Card 185717 Gift Card was not showing on the receipt when redeeming and the balance was zero (0)

Gift Card 185718 Corrected bad data created when a gift card was swiped for a balance inquiry

Gift Card 185719 Corrected error on expiration date with gift card as a return tender

Gift Card 201193 GCReconcile.txt file contained plain text account numbers

Gift Card 201491 Delete line error with manually authorized returned gift card

Gift Card 204334 Could not post void transactions with CRM tenders across registers

Gift Card 213922 EGC inquiry by customer name displayed hashed rather than masked account numbers

Lookup/Inq 185737 Corrected query in Tradewind to fix slow Sales Assoc. Prod report

Multi-Module 192461 Wrong shopper info/header on receipt after changing customer on employee transaction

Receipt 209689 Opening Till receipt did not include cash count lines

Receipt 219603 Could not view signatures in receipt viewer

Receipt 222508 TradeCenter Receipt Viewer was not showing the same information as the register receipts

Receiving 207424 Shipping and Receiving asked for password multiple times

Reports 176592 Discount quantity did not tally the same in the Daily Cash & Sales report and the ClassificationSls report

Reports 207426 Productivity module did not list employees in a consistent manner

Return 186992 No record in Return_Override_Comments for suspended and resumed offender return transaction

Send Sale 215810 Tax not calculated correctly on suspended and resumed send sale

Tender 183871 Adding a coupon discount to a transaction partially tendered with a branded gift card caused the gift card tender information to be lost

Tender 217163 Tender list shrank when using a touchscreen monitor

Training 209377 The text “Offline” and “Training” remained in English when it should be translated

Transaction 193501 The change amount due to a customer is kept on screen is now kept on screen until the drawer is closed and the transaction is complete

Tradewind

18 of 20

Known Issues

The following list summarizes some of known issues with Tradewind version 9.5 and is not intended to include all issues:

Category Reference # Description

CC Auth 220427 Settlement Auth_Source column shows a 5 for some transactions. This issue applies to Paymentech – terminal capture mode only and does not affect authorization or settlement. This information will be stored in a new field in a future release

Portable POS N/A The portable POS does not currently support encrypted passwords.

Receipt 220810 Issue with receipt header description Credit card / gift card settlement receipt when in terminal capture mode

Certified Platforms

The Tradewind version 9.5 release is supported on the following platforms:

Operating systems supported for v9.50 Tradewind:

o WIN2K – SP4

o WINXP – SP2

o WIN Server 2003 – SP1

o Microsoft Pocket PC 2003 or later (for Portable POS only)

Databases supported for Tradewind:

o SQL Server 2000 – SP4

o SQL Server 2005

Internet Explorer Versions

o Internet Explorer 6 – SP1

IBM OPOS Drivers

o IBM POS Suite 1.7.4

Operating systems and databases required for v9.50 Corporate Products:

o WIN2K – SP4

o WIN Server 2003 – SP1

o SQL Server 2000 – SP4

o SQL Server 2005

Receipt Printers supported for Tradewind:

o Epson TM-H6000

o Epson TM-T88IIP

Tradewind

19 of 20

o Epson TM-U200DP

o NCR 7156

o NCR 7167

o NCR 2214 (Fiscal)

Scanners

o NCR 7890

o IBM Spark

o WelchAllyn Image Team 3800

Signature Capture Devices

o Ingenico eN-Touch 1000

o Ingenico 6550

o Verifone Mx devices, including the Mx830, Mx850 and Mx870

Customer Displays

o Fujitsu Model 9535

o NCR 5972 Line Display

o Ultimate Technology PD1100

o Ingenico eN-Touch 1000

o Logic Control PD3000

o Ingenico 6550

o Verifone Mx devices, including the Mx830, Mx850 and Mx870

Pinpads

o Verifone 2000

o Ingenico eN-Touch 1000

o Ingenico eN-Crypt 2100

o Ingenico 13500

o Ingenico 6550

o Symbol 8500

o Verifone Mx devices, including the Mx830, Mx850 and Mx870

MSR

o Ingenico eN-Touch 1000

o Ingenico 6550

o Ingenico eN-Crypt 2100

o Fujitsu TeamPos MSR

o Wincor-Nixdorf Wedge MSR

Tradewind

20 of 20

o Verifone Mx devices, including the Mx830, Mx850 and Mx870

MICR

o NCR 7156

o NCR 7167

o Epson TM-H6000