Aloha Knowledge Base Articles

TableService

AKBID1001 Configuring the CALIBRATE Variable on Aloha Terminals

AKBID1002 Aloha Receipt and Kitchen Printer Settings and Pin-out

AKBID1003 Aloha Network Cable Pin-outs

AKBID1004 Serial Pin Assignments

AKBID1005 Microsoft Windows Automatic Log In

AKBID1006 Configuring Windows User and Share Permissions for Alo

AKBID1007 Default Aloha Windows Desktop Icons

AKBID1009 Windows 95 FOH Terminal Setup

AKBID1010 Aloha Application Software System Environment Variable

AKBID1011 Windows 9x VNETBIOS.VXD Patch

AKBID1012 Aloha Application Software Utility Description and Usa

AKBID1013 Windows 98 FOH Terminal Setup

AKBID1014 Full Hard Drive Recovery

AKBID1015 EOD Process and Errors

AKBID1016 Grind Process and Errors

AKBID1017 Required Category

AKBID1018 Network Lana Numbers

AKBID1019 Manually Registering and Un-registering Aloha Applicat

AKBID1021 Windows 95 File Server Setup

AKBID1022 Windows 98 File Server Setup

AKBID1023 Windows 95 File Server/Terminal Setup

AKBID1024 Windows 98 File Server/Terminal Setup

AKBID1025 ADP Payroll Export File

AKBID1026 Using Windows-based Printers with Aloha

AKBID1027 Microsoft Windows NT/Windows 2000 Automatic Backup

AKBID1028 Winhook

AKBID1029 Credit Card Pre-Authorization

AKBID1030 Grind Database Contents

AKBID1031 Floating Logo

AKBID1032 IBM 4695 POS Terminal

AKBID1033 PAR POS 4 POS Terminal

AKBID1035 Windows NT FOH Terminal Setup

AKBID1036 Windows NT File Server Setup

AKBID1037 Windows NT File Server/Terminal Setup

AKBID1038 Report Command Line Parameters

AKBID1039 ProHost32

AKBID1040 Run Control and Maintenance from Remote Workstation

AKBID1041 Multiple Terminal Berg Tap Setup

AKBID1042 Aloha Application Software Database Files

AKBID1043 Expediter Printer

AKBID1044 Tray Chit Printer

AKBID1045 Saved Credit Card Information

AKBID1047 Microsoft Windows Task Scheduler Service

AKBID1048 Aloha Hardware and OS Specifications

AKBID1049 Installing DCOM in Windows

AKBID1051 Aloha Application Software Flag and Marker Files

AKBID1052 Caller ID

AKBID1053 TableService Order Entry Job Code Options

AKBID1054 Revenue Centers

AKBID1055 TableService Guest Check Printing Options

AKBID1056 Upgrading the Aloha Application Software

AKBID1057 Comp and Promo Taxes

AKBID1058 Pizza Modifiers

AKBID1059 Custom Checkouts

AKBID1060 CDX Files vs. TDX Files

AKBID1062 Property Management Systems

AKBID1063 TCP/IP

AKBID1064 Tip Out Feature

AKBID1065 Aloha Synctime and Windows Time Zone Configuration

AKBID1066 Demo Aloha with the Aloha Remote Display System

AKBID1067 DBUP.EXE and DBCONFIG.EXE

AKBID1068 Barcodes and Scanners

AKBID1069 Cash Card Device Troubleshooting

AKBID1070 Cash Drawer Checkout

AKBID1071 Coconut Code Export Files

AKBID1072 Electronic Coin Dispensers

AKBID1073 Using Aloha Without Enabling Administrator Permissions

AKBID1074 OPOS

AKBID1075 NetBIOS and the Aloha Application Software

AKBID1076 Item Output File

AKBID1077 Tender ID Validation

AKBID1078 Receipt Logos

AKBID1079 PayUSA Export Files

AKBID1080 ReMACS Export Files

AKBID1081 Summary Process and Files

AKBID1082 Separate QS and TS Installations on a Single Demo Comp

AKBID1083 Checkout Buckets Report

AKBID1085 Basic Gift Certificates

AKBID1086 Get Check versus Transfer Check

AKBID1087 Clarifye Export File

AKBID1089 Order Attributes

AKBID1090 Drink Dispensers

AKBID1091 Windows 2000 Settings Location Quick Guide

AKBID1092 Windows 2000 FOH Terminal Setup

AKBID1093 Windows 2000 File Server Setup

AKBID1094 Windows 2000 File Server/Terminal Setup

AKBID1097 Aloha Application Software Font Name and Size Variable

AKBID1098 Order Taker Job Code Option

AKBID1099 Network Troubleshooting

AKBID1100 Multi-Part Checks

AKBID1101 Windows Me FOH Terminal Setup

AKBID1102 Windows Me File Server Setup

AKBID1103 Windows Me File Server/Terminal Setup

AKBID1105 Guest Check Information Files

AKBID1106 Paychex Export Files

AKBID1107 Aloha Application Software Fault Tolerance Functionali

AKBID1108 Using the Crystal Report Interface with .DBF Files

AKBID1109 ICVERIFY

AKBID1110 Installing Microsoft SQL 7.0

AKBID1111 Employee ID Card Format

AKBID1112 HASP Key Troubleshooting

AKBID1113 Remote Aloha Manager

AKBID1114 Tax and Surcharge Calculations

AKBID1115 Configuring QSR Automations RDS Ethernet Video

AKBID1116 File Server/Terminal Limitations

AKBID1117 Using Anti-virus Software on FOH Terminals

AKBID1118 Supersite IBERCFG.BAT

AKBID1119 FOH Adjustable Resolution Settings

AKBID1121 Reroute Print All Chits to Local Printers

AKBID1122 Select Electronics Video

AKBID1124 Multiple Concepts on a Single File Server

AKBID1125 Supersite Time Synchronization

AKBID1126 Supersite-Specific System Environment Variables

AKBID1128 Moving Aloha Data to a New File Server

AKBID1129 Using the Crystal Report Interface with an RDB

AKBID1131 Using .DBF Files to Create a New RDB Over an Existing

AKBID1132 Installing a New .DBF Database Over an Existing Databa

AKBID1133 Supersite Dated Folders

AKBID1134 Debouts

AKBID1137 IBM Kitchen System

AKBID1138 APG Cash Drawer Model 212A

AKBID1139 Serial Port Error Return Codes

AKBID1145 T= and C= Errors

AKBID1146 HDSPACE.EXE Low Disk Space Warning Utility

AKBID1147 Bartender Tab Name Options

AKBID1148 Backup Procedures

AKBID1149 Aloha Overtime Calculations

AKBID1150 Using LMHOSTS with a Supersite

AKBID1153 Types of Transaction Logs in Dated Folders

AKBID1154 Aloha Application Software Transaction Log

AKBID1155 Using 4.2x Dated Folders in 5.0x

AKBID1156 Using Windows Printers Between Stores in Supersites

AKBID1157 Aloha Application Software Printer Logs

AKBID1158 Configuring Windows XP Embedded for Order Entry Termin

AKBID1159 Restoring the TRANS.LOG to DATA After the EOD Process

AKBID1160 Manually Upgrading Configuration Files in Aloha Manage

AKBID1161 EMPMAGCARDMASK in the ALOHA.INI

AKBID1162 Microsoft Windows Service versus a Standard Applicatio

AKBID1163 FOH HASP Key Expiration

AKBID1164 Repairing a Corrupt NRTOTALS File

AKBID1165 FOH Screen Resolution Settings

AKBID1166 Aloha Manager BOH Security Files

AKBID1169 Assigning .WAV Files to FOH Login Functions and Events

AKBID1170 Multiple Versions of Aloha on a Single Demo Computer

AKBID1171 FOHHook.bat

AKBID1172 Configuring the IBM SurePOS 300 and SurePOS 500

AKBID1173 Demo Aloha without a HASP Key

AKBID1175 Aloha Terminal Restart Options

AKBID1176 Windows XP FOH Terminal Setup

AKBID1177 Windows XP File Server Setup

AKBID1178 Windows XP File Server/Terminal Setup

AKBID1179 Aloha BIN Folder File Contents

AKBID1181 Using Interface Server as an Aloha Printer Server

AKBID1182 COM Interface Configuration

AKBID1183 Recommended Hard Drive Partitions, File Systems, and S

AKBID1184 Consolidated Kitchen Chit Ingredient Tags

AKBID1185 Using TSBUTTON.CFG to Launch Applications from TableSe

AKBID1186 FOH Manual and Magnetic Stripe Passwords

AKBID1187 Enable or Disable RDB Grind User Interfaces

AKBID1188 Using Previous Version Dated Folders in 5.2x

AKBID1192 Troubleshooting EDC Spooling

AKBID1193 Purging Dated Folders in Aloha Manager

AKBID1194 Check Comp Form

AKBID1195 Deleting the DOWNTIME.INI

AKBID1196 DBFUTIL.EXE

AKBID1197 Assigning Logins to Aloha Services

AKBID1198 Magnetic Stripe Card Information

AKBID1199 Configuring a SuperSite FOH Terminal

AKBID1200 Chit Information Files

AKBID1201 Multi-resolution Bitmap Folders

AKBID1202 Installing Microsoft SQL Server 2000

AKBID1203 Configuring Aloha as a Thin Client on Windows Terminal

AKBID1204 Default Aloha System Environment Variable Placement

AKBID1206 Printing Foreign Characters

AKBID1207 Configuring and Using CHKINFO.EXE

AKBID1208 Configuring Fiscal Manager and Fiscal Printers in Aloh

AKBID1209 Configuring the Aloha Application Software VizorVest I

AKBID1210 Converting an Existing .DBF Site to a Relational Datab

AKBID1211 Common Microsoft Error Return Codes

AKBID1212 Aloha Application Software Version Numbering Scheme

AKBID1215 Configuring Veridicom Thumbprint Scanners

AKBID1216 Enabling and Configuring FOH Enhanced Graphical Interf

AKBID1217 Configuring QSR Automations KDS

AKBID1218 Using MSDE with the Aloha Application Software

AKBID1219 Updating Binary Files on an Existing Aloha Installatio

AKBID1220 Assigning the HASP LPT Port in the Aloha Application S

AKBID1221 Store Lockout File

AKBID1222 Configuring Aloha Applications as the Windows Shell

AKBID1223 Windows Server 2003 FOH Terminal Setup

AKBID1224 Windows Server 2003 File Server Setup

AKBID1225 Windows Server 2003 File Server/Terminal Setup

AKBID1226 Front-of-House Item Pricing Hierarchy

AKBID1227 Aloha Application Software Relational Database Tables

AKBID1228 Demo both QS and TS with a Single Instance of Aloha Ma

AKBID1229 Logic Controls Logic Net Kitchen Display System (Seria

AKBID1230 Adding Tips to Gift Card Payments

AKBID1231 Masking Credit Card Numbers

AKBID1232 Formatting Seat Numbers on Kitchen and Bar Chits

AKBID1233 Select Electronics OAsys Kitchen Display System

AKBID1234 Configuring Aloha to Conform with the Visa CISP Guidel

AKBID1235 Downgrading a SuperSite Store Following a Major Upgrad

AKBID3001 Exact and Next Tenders

AKBID3002 Windows 95 Auto Scandisk

AKBID3004 File Formerly Known as BOHSEC

AKBID3005 Foreign Tenders

AKBID3006 Include Comps or Promos in Net Sales

AKBID3008 OK File

AKBID3009 CTLSVR.EXE Registry Variables

AKBID3010 EDCSVR.EXE Registry Variables

AKBID3011 OLK Files

AKBID3012 LCK Files

AKBID3013 Sub-Folders Inside System Folders

AKBID3014 Cashier Guest Counts

AKBID3015 Softkey Upgrades

AKBID3016 Manual HASP Driver Installation and Removal

AKBID3017 Adjust Control and Maintenance Window Sizes

AKBID3018 Adjust Control and Maintenance Window Positions

AKBID3019 Control not Responding on Task Bar

AKBID3020 Adjust Control and Maintenance Timeouts

AKBID3021 FOH Looping Batch File

AKBID3022 Windows NT/Windows 2000 HASP Key BSOD

AKBID3023 Clock-Out Time is Less than Clock-In Time

AKBID3024 Erase Sales Data for Go Live

AKBID3025 Javelin LC Customer Display Settings

AKBID3026 Inclusive Tax Formula

AKBID3027 Double-Click Ability with FOH Running

AKBID3030 Supported Crystal Report Writer Versions

AKBID3033 Slow 16 MB 4.2 Terminals

AKBID3035 Gift Certificate Get_Entry_Name Error

AKBID3036 Survey ID Codes

AKBID3038 LANDRYS Flag

AKBID3039 Masking the Credit Card Numbers on the Guest Check

AKBID3041 Masking the Credit Card Number on the Voucher

AKBID3042 Default Magnetic Stripe Reader Sentinels

AKBID3043 Aloha Manager Navigation Bar Settings

AKBID3044 CLOSETIME ALOHA.INI Setting

AKBID3045 EVENTTIME ALOHA.INI Setting

AKBID3046 CONNMGR.EXE

AKBID3047 NCR 7454 Windows Protection Error

AKBID3048 Illegal Operation Over the Floating Logo

AKBID3049 FOH Sticks 'Initializing POS' on FOH/BOH Computer

AKBID3051 COM Port Error -1

AKBID3052 COM Port Error -3

AKBID3054 Remote pcANYWHERE Report Printing

AKBID3055 Shifted FOH Screen

AKBID3056 Unable to Locate Security Descriptor

AKBID3057 Employee Locked on Another Terminal

AKBID3058 Tip Refund

AKBID3059 Faded Cool Interfaces

AKBID3060 Job Code Revenue Center

AKBID3061 Aloha Manager SSP Timeout

AKBID3062 FOH Server Sales Report Abbreviations

AKBID3063 Ultimate Technology Corporation Customer Display Set

AKBID3065 Windows 9x Fails to Initialize Microsoft Windows Net

AKBID3068 Bump to Video Group

AKBID3069 Negative Price Modifiers

AKBID3070 Irregular Mouse Movement when CTLSVR.EXE is Running

AKBID3071 Incomplete Labor Reports

AKBID3072 Repairing a Corrupt TRANS.LOG

AKBID3073 Aloha Technologies MSR Card Engraved Number

AKBID3074 Non-Redeemed Payments

AKBID3076 Maximum Number of Items

AKBID3077 Multiple Chits Print

AKBID3078 Delivery Interface not Responding to FOH

AKBID3079 NOMODCODES in the ALOHA.INI

AKBID3080 BOH Sort Preferences

AKBID3082 Scale Serial Port, Cable, and Miscellaneous Configur

AKBID3083 Tip Share

AKBID3084 DBFDIFF.EXE

AKBID3085 BOH Sales Report Calculated Cash Formula

AKBID3086 Cloned Terminal Application Shortcuts

AKBID3087 4.2x and 4.4x Full-Screen 800x600 FOH Settings

AKBID3088 Separate Tip and Gratuity Tracking

AKBID3089 Maintenance Only Creates TAB.CDX File

AKBID3090 Using IBEREXE.DLL to Disable the Super-Secret-Passwo

AKBID3091 EXITING File

AKBID3092 MSYNC File

AKBID3093 PULLDONE File

AKBID3094 FOH Restarts When Reading System Parameters

AKBID3095 Network Name Unexpectedly Deregistered

AKBID3096 Synchronization of Data Fails

AKBID3097 Failed to Read Error Code

AKBID3098 Corrupt Printer Log Error

AKBID3100 FOH Flash Report Labor Information is Blank

AKBID3101 Edit Punches Application does not Display Properly

AKBID3103 BOH CTL3D32.DLL Error

AKBID3104 Shutdown Terminal

AKBID3105 Barcodes for Basic House Accounts

AKBID3106 Separating Chits on a Single Printer

AKBID3107 Windows Screensavers Causing Slow Terminals and Erro

AKBID3108 Setting RDB Grind Screen Positions

AKBID3109 Re-synchronizing DBF Files From an RDB

AKBID3110 The REMOTE Variable

AKBID3111 How to Shut Down the FOH Using a Keyboard

AKBID3112 HALT File

AKBID3113 Serial Cash Drawer Compulsory Method

AKBID3114 PRINTERBAUD in the ALOHA.INI

AKBID3115 Enable or Disable Receipts when Manager Adjusts the

AKBID3116 SERIALDRAWERCOUNT in the ALOHA.INI

AKBID3117 FOH 'Invalid Employee Number' Error

AKBID3118 FOH 'Not Authorized for Video' Error

AKBID3119 BOH Cool Interface Selection Only Displays 'Default'

AKBID3120 Two Cash Drawers Connected to a Single Printer

AKBID3121 Setting the Credit Card Refund Limit

AKBID3122 Show Subtotal on Customer Display

AKBID3123 Print FOH Flash Report

AKBID3128 Defining the BackOffice Messages Folder Location

AKBID3129 TEKVisions Keyboard Error

AKBID3130 RunGrind File in the Data Folder

AKBID3132 .CNT Files in the DATA Folder

AKBID3133 TableService PLU Button BMP

AKBID3134 Tippable Sales Calculation

AKBID3135 Gift Certificates Not in Aloha Manager Payments Menu

AKBID3136 UNFORGIVING in the ALOHA.INI

AKBID3137 TableService Tender and Item Bitmaps

AKBID3139 Disabling Clock-in and Clock-out Chits

AKBID3140 Hold Button is Replaced with a Reprint Check Button

AKBID3141 Default Aloha Manager Window Size and Position

AKBID3142 Changing the Default Aloha Manager HTML Page

AKBID3143 Users cannot Modify Items

AKBID3144 Using an Ampersand on a QuickService Button Label

AKBID3145 IPX/SPX Protocol

AKBID3146 Payment Reconciliation Calculation

AKBID3147 Using Modifiers with Item Availability

AKBID3148 Aloha Manager Failed Security Error

AKBID3149 Auto Start BOH Terminal and Errors

AKBID3150 Editing Microsoft Windows Me Environment Variables

AKBID3151 TableService Open Item Options

AKBID3152 Items in Categories Have Zero Item Numbers

AKBID3153 Force Manager Approval for Employee Clock-in

AKBID3154 Epson Printer Enunciators

AKBID3155 EVENTS.CFG Corruption

AKBID3156 WMF Pen Reader Pin-outs

AKBID3157 AutoMenu not Initializing

AKBID3159 Clock-Out Chit Sales Calculation

AKBID3161 Product Mix Report Specific Items Only

AKBID3162 Chits do not Display Entire Tab Name

AKBID3163 Ordinal not Found in Dynamic Link Library

AKBID3165 Javelin Viper Customer Display Settings

AKBID3167 IBER.EXE/IBERQS.EXE Demonstration Restrictions

AKBID3168 Progressive Systems CVM Pin-outs

AKBID3169 KEY.TXT HASP Security Key Identification File

AKBID3170 Report Layout or Display Anomalies

AKBID3171 Cannot load string' Errors in FOH Debouts

AKBID3172 Event-level Tax Reroutes

AKBID3173 RIP1ITEM=0 in the ALOHA.INI

AKBID3174 Disable Drink Chits for Bartenders

AKBID3175 Aloha does not Detect Open Javelin OPOS Cash Drawer

AKBID3176 SuperSite Terminals Restart, but do not Refresh

AKBID3177 Seat Numbers are not Printing on Chit

AKBID3179 Tax Rounding Direction

AKBID3180 Membership Interface Causes Grind PutIntField Overfl

AKBID3181 Aloha Manager Only Displays a White Background

AKBID3185 Lookup_stat ID Errors

AKBID3186 Cool Interface by Terminal

AKBID3187 Selecting an Open TCP Port for AlohaSpy and Fiscal M

AKBID3188 Logging Screen Touches for Debugging

AKBID3189 ODBC Version Error

AKBID3190 House Account Report Font

AKBID3191 NCR OPOS Memory Leak Causing Terminal Lockups

AKBID3193 Printing One Item on Two Chits Using a Single Printe

AKBID3194 Configuring Customer Cards for Use with Frequent Buy

AKBID3195 Resetting Non-resetting Totals to Zero

AKBID3196 Event-level Menu Assignment Hierarchy

AKBID3197 Enabling Retroactive Non-resetting Totals

AKBID3198 EDC Processors Currently Supported by Aloha

AKBID3205 FOH Hangs on Starting EDC

AKBID3206 Balancing Reports Using /BALANCE

AKBID3209 USEHUGECURRENCY in the ALOHA.INI

AKBID3211 Enable FOH Keyboard Input

AKBID3212 Thumbprint Scanner and HASP Key Conflicts

AKBID3214 Default Report Output to Text or Printer

AKBID3215 DOWNTIME.INI Updates

AKBID3216 Enabling the TableService PLU Button

AKBID3217 License File Not Found' Error

AKBID3219 Changing a SuperSite Store's Date-of-Business

AKBID3220 Hourly Sales and Labor Report Revenue Accumulation

AKBID3221 Real-time Virus Protection Can Effect Aloha Performa

AKBID3222 Windows 95 Illegal Operation with AlohaSpy

AKBID3223 NOREBOOTAFTERSYNCH in the ALOHA.INI

AKBID3225 NEWEOD in the ALOHA.INI

AKBID3226 FSRECOVERYEOD in the ALOHA.INI

AKBID3227 FOH Login Screen Memory Availability and Usage Figur

AKBID3228 Setting a Custom Resolution in Panel Editor

AKBID3229 Enabling the Substitute Modifier Button

AKBID3230 Ameranth Terminal Connection Failure Error

AKBID3231 Multi-site EOD Run Date Error

AKBID3232 Remote Printers Continuously Print Chits

AKBID3233 Adding Memory Status Updates to FOH Debouts

AKBID3234 House Account Log Record Types

AKBID3235 Excluding Voids from Gross Sales on Checkouts

AKBID3236 Aloha Manager is Missing Drop-down Menus or Menu Opt

AKBID3237 MASTERTERMINALID in the ALOHA.INI

AKBID3238 System Date Set to Prior Year Reports Log Corruption

AKBID3239 Dated Folders Missing from Reprint or Audit Report L

AKBID3240 NETBIOSERRORTHRESHOLD in the ALOHA.INI

AKBID3241 Merging Transaction Logs

AKBID3242 Hard Check Printer Only Prints One Line Per Check

AKBID3243 Suppressing Errors for Temporary Terminals

AKBID3244 FOH Check Numbering Scheme

AKBID3245 CTLSVR.EXE Says Another Terminal with the Same Numbe

AKBID3247 Shifts are not Listed on Labor Reports

AKBID3248 IBM SurePOS 500-xx2 Serial Port Pin-outs and Printer

AKBID3249 QSR Ethernet Creates Very Large Transaction and Vide

AKBID3250 Offline Gift Card Authorizations do not Print Balanc

AKBID3251 Brother Report Printer Prints Reports Inverted and R

AKBID3252 Cash Drawer Opens Each Time the Printer Prints

AKBID3253 Caf� Service Errors

AKBID3255 Reversing Comp Calculation Order

AKBID3257 FOH Cannot Start with Disconnected Veridicom Scanner

AKBID3258 Problems Installing MDAC 2.6 in Windows 2000

AKBID3259 Windows does not Read MSR without a Keyboard Attache

AKBID3261 SETUPPOS.EXE Opens a Visual Basic Editor

AKBID3262 'BarDlgFunc: no table!' Error in TableService FOH

AKBID3263 Equinox ESP 8 10/100 Serial Hub Printer Cable Pin-ou

AKBID3264 Zero-byte .OLK Files Cause Windows Illegal Operation

AKBID3266 Configuring Network-based Receipt Printers with Aloh

AKBID3269 Equinox SST-8P Serial I/O Adaptor Printer Cable Pin-

AKBID3271 Too Many Delivery Orders Causes FOH to Exit

AKBID3272 Configuring POSIFLEX PD-2500 Customer Display

AKBID3273 NCR OPOS MSR Stops Working After First Swipe

AKBID3275 Configuring the Flytech POS600 MSR for Use with Aloh

AKBID3276 Configuring the Flytech POS600 Customer Display

AKBID3277 Configuring the CRS IT-8000 2X20 Rear Customer Displ

AKBID3278 NEVERPRINTFOHWAGES in the ALOHA.INI

AKBID3282 Configuring the J2 800 CX MSR for Use with Aloha

AKBID3283 Configuring the ID TECH MiniMag Compact MSR for Aloh

AKBID3284 NOVOIDFINALIZEDGCPAYMENTS Variable in the ALOHA.INI

AKBID3285 Using LOCALREAD to Decrease Wireless Network Traffic

AKBID3286 Removing the 'Clear' Button from the Order Entry Scr

AKBID3287 The Aloha Application Software FF.INI

AKBID3288 PMS Interfaces Currently Supported by Aloha

AKBID3289 Using /DEV to Suppress Customer Data Errors During T

AKBID3290 PRINTSHORTCLOCKOUT in the ALOHA.INI

AKBID3291 Javelin Cash Drawer Ports Cause Fatal Errors

AKBID3293 TOFOH.TXN Files

AKBID3294 User 1500n Errors in the Debouts

AKBID3295 USESHORTCHECKNUMBERFORGC Variable in the ALOHA.INI

AKBID3296 Log Corruption Message on a File Server/Terminal

AKBID3297 Senor Tech Co., Ltd. R856008AST Customer Display

AKBID3298 FOH Loses Magnetic Stripe Passwords Following EOD

AKBID3299 FOH Receipt and Chit Printers do not Automatically R

AKBID3300 Aloha FOH Reads Multiple Event Configuration Files

AKBID3301 Enable the FOH to Process BOH EDC Transactions

AKBID3302 Comp and Promo Discount Distribution

AKBID3303 Enable PMS Tip or Tender Adjustments on Closed Check

AKBID3304 Configuring the CRS IT-1000-TM1K-2K 2-track MSR

AKBID3305 Configuring the J2 800 CX Customer Display for Use w

AKBID3306 Price Text Overwrites Graphics on AccuVIEW 150 Displ

AKBID3309 Touch Screens Register Touch to the Previously Touch

AKBID3310 Historical P-Mix Reports using Current Configuration

AKBID3311 Windows 95 Terminals do not Detect Windows 2000+ Fil

AKBID3313 Forcing End-of-Day from Outside of Aloha

AKBID3316 Printing Multiple Copies of Chits on a Terminal's Lo

AKBID3317 Radiant RJ12 serial port Pin-outs and Cables

AKBID3318 Configuring the Radiant Systems P15xx MSR for Aloha

AKBID3319 Enabling FOH EDC Transactions for Less Than $1.00

AKBID3320 EGI Causes Windows Error on DigiCom Terminals

AKBID3321 DEFAULTREVENUECENTER in the ALOHA.INI

AKBID3322 RDB Report Date Ranges

AKBID3323 Non-SERVERCAPABLE Terminals do not Sync Config Files

AKBID3324 FASTECHGIFTCERT=Obsolete in the ALOHA.INI

AKBID3326 Radiant P701 Customer Display OPOS Configuration

AKBID3327 Radiant 16-inch Printer Driven Cash Drawer Cable Pin

AKBID3328 'Got Message Type 287 from BOH' Message in Debouts

AKBID3329 Configuring the Radiant Systems P1210 Integrated MSR

AKBID3330 Configuring the Radiant P1210 Integrated Customer Di

AKBID3331 Configuring the Radiant Systems P400 MSR for Aloha

Go to Top

QuickService

AKBID1001 Configuring the CALIBRATE Variable on Aloha Terminals

AKBID1002 Aloha Receipt and Kitchen Printer Settings and Pin-out

AKBID1003 Aloha Network Cable Pin-outs

AKBID1004 Serial Pin Assignments

AKBID1005 Microsoft Windows Automatic Log In

AKBID1006 Configuring Windows User and Share Permissions for Alo

AKBID1007 Default Aloha Windows Desktop Icons

AKBID1009 Windows 95 FOH Terminal Setup

AKBID1010 Aloha Application Software System Environment Variable

AKBID1011 Windows 9x VNETBIOS.VXD Patch

AKBID1012 Aloha Application Software Utility Description and Usa

AKBID1013 Windows 98 FOH Terminal Setup

AKBID1014 Full Hard Drive Recovery

AKBID1015 EOD Process and Errors

AKBID1016 Grind Process and Errors

AKBID1018 Network Lana Numbers

AKBID1019 Manually Registering and Un-registering Aloha Applicat

AKBID1021 Windows 95 File Server Setup

AKBID1022 Windows 98 File Server Setup

AKBID1023 Windows 95 File Server/Terminal Setup

AKBID1024 Windows 98 File Server/Terminal Setup

AKBID1025 ADP Payroll Export File

AKBID1026 Using Windows-based Printers with Aloha

AKBID1027 Microsoft Windows NT/Windows 2000 Automatic Backup

AKBID1028 Winhook

AKBID1030 Grind Database Contents

AKBID1031 Floating Logo

AKBID1032 IBM 4695 POS Terminal

AKBID1033 PAR POS 4 POS Terminal

AKBID1035 Windows NT FOH Terminal Setup

AKBID1036 Windows NT File Server Setup

AKBID1037 Windows NT File Server/Terminal Setup

AKBID1038 Report Command Line Parameters

AKBID1040 Run Control and Maintenance from Remote Workstation

AKBID1041 Multiple Terminal Berg Tap Setup

AKBID1042 Aloha Application Software Database Files

AKBID1047 Microsoft Windows Task Scheduler Service

AKBID1048 Aloha Hardware and OS Specifications

AKBID1049 Installing DCOM in Windows

AKBID1051 Aloha Application Software Flag and Marker Files

AKBID1052 Caller ID

AKBID1053 TableService Order Entry Job Code Options

AKBID1054 Revenue Centers

AKBID1056 Upgrading the Aloha Application Software

AKBID1057 Comp and Promo Taxes

AKBID1058 Pizza Modifiers

AKBID1059 Custom Checkouts

AKBID1060 CDX Files vs. TDX Files

AKBID1062 Property Management Systems

AKBID1063 TCP/IP

AKBID1065 Aloha Synctime and Windows Time Zone Configuration

AKBID1066 Demo Aloha with the Aloha Remote Display System

AKBID1067 DBUP.EXE and DBCONFIG.EXE

AKBID1068 Barcodes and Scanners

AKBID1069 Cash Card Device Troubleshooting

AKBID1070 Cash Drawer Checkout

AKBID1071 Coconut Code Export Files

AKBID1072 Electronic Coin Dispensers

AKBID1073 Using Aloha Without Enabling Administrator Permissions

AKBID1074 OPOS

AKBID1075 NetBIOS and the Aloha Application Software

AKBID1076 Item Output File

AKBID1077 Tender ID Validation

AKBID1078 Receipt Logos

AKBID1079 PayUSA Export Files

AKBID1080 ReMACS Export Files

AKBID1081 Summary Process and Files

AKBID1082 Separate QS and TS Installations on a Single Demo Comp

AKBID1090 Drink Dispensers

AKBID1091 Windows 2000 Settings Location Quick Guide

AKBID1092 Windows 2000 FOH Terminal Setup

AKBID1093 Windows 2000 File Server Setup

AKBID1094 Windows 2000 File Server/Terminal Setup

AKBID1096 Smart Items

AKBID1097 Aloha Application Software Font Name and Size Variable

AKBID1099 Network Troubleshooting

AKBID1101 Windows Me FOH Terminal Setup

AKBID1102 Windows Me File Server Setup

AKBID1103 Windows Me File Server/Terminal Setup

AKBID1105 Guest Check Information Files

AKBID1106 Paychex Export Files

AKBID1107 Aloha Application Software Fault Tolerance Functionali

AKBID1108 Using the Crystal Report Interface with .DBF Files

AKBID1109 ICVERIFY

AKBID1110 Installing Microsoft SQL 7.0

AKBID1111 Employee ID Card Format

AKBID1112 HASP Key Troubleshooting

AKBID1113 Remote Aloha Manager

AKBID1114 Tax and Surcharge Calculations

AKBID1115 Configuring QSR Automations RDS Ethernet Video

AKBID1116 File Server/Terminal Limitations

AKBID1117 Using Anti-virus Software on FOH Terminals

AKBID1118 Supersite IBERCFG.BAT

AKBID1122 Select Electronics Video

AKBID1124 Multiple Concepts on a Single File Server

AKBID1125 Supersite Time Synchronization

AKBID1126 Supersite-Specific System Environment Variables

AKBID1128 Moving Aloha Data to a New File Server

AKBID1129 Using the Crystal Report Interface with an RDB

AKBID1131 Using .DBF Files to Create a New RDB Over an Existing

AKBID1132 Installing a New .DBF Database Over an Existing Databa

AKBID1133 Supersite Dated Folders

AKBID1134 Debouts

AKBID1137 IBM Kitchen System

AKBID1138 APG Cash Drawer Model 212A

AKBID1139 Serial Port Error Return Codes

AKBID1145 T= and C= Errors

AKBID1146 HDSPACE.EXE Low Disk Space Warning Utility

AKBID1148 Backup Procedures

AKBID1149 Aloha Overtime Calculations

AKBID1150 Using LMHOSTS with a Supersite

AKBID1153 Types of Transaction Logs in Dated Folders

AKBID1154 Aloha Application Software Transaction Log

AKBID1155 Using 4.2x Dated Folders in 5.0x

AKBID1156 Using Windows Printers Between Stores in Supersites

AKBID1157 Aloha Application Software Printer Logs

AKBID1158 Configuring Windows XP Embedded for Order Entry Termin

AKBID1159 Restoring the TRANS.LOG to DATA After the EOD Process

AKBID1160 Manually Upgrading Configuration Files in Aloha Manage

AKBID1161 EMPMAGCARDMASK in the ALOHA.INI

AKBID1162 Microsoft Windows Service versus a Standard Applicatio

AKBID1163 FOH HASP Key Expiration

AKBID1164 Repairing a Corrupt NRTOTALS File

AKBID1165 FOH Screen Resolution Settings

AKBID1166 Aloha Manager BOH Security Files

AKBID1169 Assigning .WAV Files to FOH Login Functions and Events

AKBID1170 Multiple Versions of Aloha on a Single Demo Computer

AKBID1171 FOHHook.bat

AKBID1172 Configuring the IBM SurePOS 300 and SurePOS 500

AKBID1173 Demo Aloha without a HASP Key

AKBID1175 Aloha Terminal Restart Options

AKBID1176 Windows XP FOH Terminal Setup

AKBID1177 Windows XP File Server Setup

AKBID1178 Windows XP File Server/Terminal Setup

AKBID1179 Aloha BIN Folder File Contents

AKBID1181 Using Interface Server as an Aloha Printer Server

AKBID1182 COM Interface Configuration

AKBID1183 Recommended Hard Drive Partitions, File Systems, and S

AKBID1184 Consolidated Kitchen Chit Ingredient Tags

AKBID1186 FOH Manual and Magnetic Stripe Passwords

AKBID1187 Enable or Disable RDB Grind User Interfaces

AKBID1188 Using Previous Version Dated Folders in 5.2x

AKBID1192 Troubleshooting EDC Spooling

AKBID1193 Purging Dated Folders in Aloha Manager

AKBID1195 Deleting the DOWNTIME.INI

AKBID1196 DBFUTIL.EXE

AKBID1197 Assigning Logins to Aloha Services

AKBID1198 Magnetic Stripe Card Information

AKBID1199 Configuring a SuperSite FOH Terminal

AKBID1200 Chit Information Files

AKBID1201 Multi-resolution Bitmap Folders

AKBID1202 Installing Microsoft SQL Server 2000

AKBID1203 Configuring Aloha as a Thin Client on Windows Terminal

AKBID1204 Default Aloha System Environment Variable Placement

AKBID1205 Configuring Subway WISR and Control Reports

AKBID1206 Printing Foreign Characters

AKBID1207 Configuring and Using CHKINFO.EXE

AKBID1208 Configuring Fiscal Manager and Fiscal Printers in Aloh

AKBID1210 Converting an Existing .DBF Site to a Relational Datab

AKBID1211 Common Microsoft Error Return Codes

AKBID1212 Aloha Application Software Version Numbering Scheme

AKBID1214 Using COMPVER.TXT to Verify Names Applied to Comps

AKBID1215 Configuring Veridicom Thumbprint Scanners

AKBID1216 Enabling and Configuring FOH Enhanced Graphical Interf

AKBID1217 Configuring QSR Automations KDS

AKBID1218 Using MSDE with the Aloha Application Software

AKBID1219 Updating Binary Files on an Existing Aloha Installatio

AKBID1220 Assigning the HASP LPT Port in the Aloha Application S

AKBID1221 Store Lockout File

AKBID1222 Configuring Aloha Applications as the Windows Shell

AKBID1223 Windows Server 2003 FOH Terminal Setup

AKBID1224 Windows Server 2003 File Server Setup

AKBID1225 Windows Server 2003 File Server/Terminal Setup

AKBID1226 Front-of-House Item Pricing Hierarchy

AKBID1227 Aloha Application Software Relational Database Tables

AKBID1228 Demo both QS and TS with a Single Instance of Aloha Ma

AKBID1229 Logic Controls Logic Net Kitchen Display System (Seria

AKBID1230 Adding Tips to Gift Card Payments

AKBID1231 Masking Credit Card Numbers

AKBID1233 Select Electronics OAsys Kitchen Display System

AKBID1234 Configuring Aloha to Conform with the Visa CISP Guidel

AKBID1235 Downgrading a SuperSite Store Following a Major Upgrad

AKBID3001 Exact and Next Tenders

AKBID3002 Windows 95 Auto Scandisk

AKBID3003 Editing the Check and Queue Sizes

AKBID3004 File Formerly Known as BOHSEC

AKBID3005 Foreign Tenders

AKBID3006 Include Comps or Promos in Net Sales

AKBID3008 OK File

AKBID3009 CTLSVR.EXE Registry Variables

AKBID3010 EDCSVR.EXE Registry Variables

AKBID3011 OLK Files

AKBID3012 LCK Files

AKBID3013 Sub-Folders Inside System Folders

AKBID3015 Softkey Upgrades

AKBID3016 Manual HASP Driver Installation and Removal

AKBID3017 Adjust Control and Maintenance Window Sizes

AKBID3018 Adjust Control and Maintenance Window Positions

AKBID3019 Control not Responding on Task Bar

AKBID3020 Adjust Control and Maintenance Timeouts

AKBID3021 FOH Looping Batch File

AKBID3022 Windows NT/Windows 2000 HASP Key BSOD

AKBID3023 Clock-Out Time is Less than Clock-In Time

AKBID3024 Erase Sales Data for Go Live

AKBID3025 Javelin LC Customer Display Settings

AKBID3026 Inclusive Tax Formula

AKBID3030 Supported Crystal Report Writer Versions

AKBID3031 Delete Previous Like Item

AKBID3032 Consolidate QuickService Open Check Items

AKBID3033 Slow 16 MB 4.2 Terminals

AKBID3034 Disable QuickService Compulsory Cash Drawers

AKBID3035 Gift Certificate Get_Entry_Name Error

AKBID3039 Masking the Credit Card Numbers on the Guest Check

AKBID3041 Masking the Credit Card Number on the Voucher

AKBID3042 Default Magnetic Stripe Reader Sentinels

AKBID3043 Aloha Manager Navigation Bar Settings

AKBID3047 NCR 7454 Windows Protection Error

AKBID3048 Illegal Operation Over the Floating Logo

AKBID3049 FOH Sticks 'Initializing POS' on FOH/BOH Computer

AKBID3051 COM Port Error -1

AKBID3052 COM Port Error -3

AKBID3054 Remote pcANYWHERE Report Printing

AKBID3055 Shifted FOH Screen

AKBID3056 Unable to Locate Security Descriptor

AKBID3057 Employee Locked on Another Terminal

AKBID3058 Tip Refund

AKBID3060 Job Code Revenue Center

AKBID3061 Aloha Manager SSP Timeout

AKBID3062 FOH Server Sales Report Abbreviations

AKBID3063 Ultimate Technology Corporation Customer Display Set

AKBID3064 Wait for Credit Card Authorization

AKBID3065 Windows 9x Fails to Initialize Microsoft Windows Net

AKBID3067 QS Append to Current Quantity

AKBID3068 Bump to Video Group

AKBID3069 Negative Price Modifiers

AKBID3070 Irregular Mouse Movement when CTLSVR.EXE is Running

AKBID3071 Incomplete Labor Reports

AKBID3072 Repairing a Corrupt TRANS.LOG

AKBID3073 Aloha Technologies MSR Card Engraved Number

AKBID3074 Non-Redeemed Payments

AKBID3075 NOTOTALLINEONCHECK in the ALOHA.INI

AKBID3076 Maximum Number of Items

AKBID3077 Multiple Chits Print

AKBID3078 Delivery Interface not Responding to FOH

AKBID3079 NOMODCODES in the ALOHA.INI

AKBID3080 BOH Sort Preferences

AKBID3081 Closing QS Refunds

AKBID3082 Scale Serial Port, Cable, and Miscellaneous Configur

AKBID3084 DBFDIFF.EXE

AKBID3085 BOH Sales Report Calculated Cash Formula

AKBID3086 Cloned Terminal Application Shortcuts

AKBID3087 4.2x and 4.4x Full-Screen 800x600 FOH Settings

AKBID3089 Maintenance Only Creates TAB.CDX File

AKBID3090 Using IBEREXE.DLL to Disable the Super-Secret-Passwo

AKBID3091 EXITING File

AKBID3092 MSYNC File

AKBID3093 PULLDONE File

AKBID3094 FOH Restarts When Reading System Parameters

AKBID3095 Network Name Unexpectedly Deregistered

AKBID3096 Synchronization of Data Fails

AKBID3097 Failed to Read Error Code

AKBID3098 Corrupt Printer Log Error

AKBID3099 QS Manager Access Functions from Any Screen

AKBID3100 FOH Flash Report Labor Information is Blank

AKBID3101 Edit Punches Application does not Display Properly

AKBID3103 BOH CTL3D32.DLL Error

AKBID3104 Shutdown Terminal

AKBID3105 Barcodes for Basic House Accounts

AKBID3106 Separating Chits on a Single Printer

AKBID3107 Windows Screensavers Causing Slow Terminals and Erro

AKBID3108 Setting RDB Grind Screen Positions

AKBID3109 Re-synchronizing DBF Files From an RDB

AKBID3110 The REMOTE Variable

AKBID3111 How to Shut Down the FOH Using a Keyboard

AKBID3112 HALT File

AKBID3113 Serial Cash Drawer Compulsory Method

AKBID3114 PRINTERBAUD in the ALOHA.INI

AKBID3115 Enable or Disable Receipts when Manager Adjusts the

AKBID3116 SERIALDRAWERCOUNT in the ALOHA.INI

AKBID3117 FOH 'Invalid Employee Number' Error

AKBID3118 FOH 'Not Authorized for Video' Error

AKBID3120 Two Cash Drawers Connected to a Single Printer

AKBID3121 Setting the Credit Card Refund Limit

AKBID3122 Show Subtotal on Customer Display

AKBID3123 Print FOH Flash Report

AKBID3128 Defining the BackOffice Messages Folder Location

AKBID3129 TEKVisions Keyboard Error

AKBID3130 RunGrind File in the Data Folder

AKBID3131 QuickService Panel Background Bitmap

AKBID3135 Gift Certificates Not in Aloha Manager Payments Menu

AKBID3136 UNFORGIVING in the ALOHA.INI

AKBID3139 Disabling Clock-in and Clock-out Chits

AKBID3141 Default Aloha Manager Window Size and Position

AKBID3142 Changing the Default Aloha Manager HTML Page

AKBID3143 Users cannot Modify Items

AKBID3144 Using an Ampersand on a QuickService Button Label

AKBID3145 IPX/SPX Protocol

AKBID3146 Payment Reconciliation Calculation

AKBID3148 Aloha Manager Failed Security Error

AKBID3149 Auto Start BOH Terminal and Errors

AKBID3150 Editing Microsoft Windows Me Environment Variables

AKBID3152 Items in Categories Have Zero Item Numbers

AKBID3153 Force Manager Approval for Employee Clock-in

AKBID3154 Epson Printer Enunciators

AKBID3155 EVENTS.CFG Corruption

AKBID3156 WMF Pen Reader Pin-outs

AKBID3159 Clock-Out Chit Sales Calculation

AKBID3161 Product Mix Report Specific Items Only

AKBID3162 Chits do not Display Entire Tab Name

AKBID3163 Ordinal not Found in Dynamic Link Library

AKBID3165 Javelin Viper Customer Display Settings

AKBID3167 IBER.EXE/IBERQS.EXE Demonstration Restrictions

AKBID3168 Progressive Systems CVM Pin-outs

AKBID3169 KEY.TXT HASP Security Key Identification File

AKBID3170 Report Layout or Display Anomalies

AKBID3171 Cannot load string' Errors in FOH Debouts

AKBID3172 Event-level Tax Reroutes

AKBID3173 RIP1ITEM=0 in the ALOHA.INI

AKBID3175 Aloha does not Detect Open Javelin OPOS Cash Drawer

AKBID3176 SuperSite Terminals Restart, but do not Refresh

AKBID3178 Quick Combo Select Item Panel Size and Color

AKBID3179 Tax Rounding Direction

AKBID3181 Aloha Manager Only Displays a White Background

AKBID3183 QS Video Displays 'Order is not finalized' Error

AKBID3185 Lookup_stat ID Errors

AKBID3187 Selecting an Open TCP Port for AlohaSpy and Fiscal M

AKBID3188 Logging Screen Touches for Debugging

AKBID3189 ODBC Version Error

AKBID3190 House Account Report Font

AKBID3191 NCR OPOS Memory Leak Causing Terminal Lockups

AKBID3193 Printing One Item on Two Chits Using a Single Printe

AKBID3194 Configuring Customer Cards for Use with Frequent Buy

AKBID3195 Resetting Non-resetting Totals to Zero

AKBID3197 Enabling Retroactive Non-resetting Totals

AKBID3198 EDC Processors Currently Supported by Aloha

AKBID3205 FOH Hangs on Starting EDC

AKBID3206 Balancing Reports Using /BALANCE

AKBID3209 USEHUGECURRENCY in the ALOHA.INI

AKBID3212 Thumbprint Scanner and HASP Key Conflicts

AKBID3214 Default Report Output to Text or Printer

AKBID3215 DOWNTIME.INI Updates

AKBID3217 License File Not Found' Error

AKBID3219 Changing a SuperSite Store's Date-of-Business

AKBID3220 Hourly Sales and Labor Report Revenue Accumulation

AKBID3221 Real-time Virus Protection Can Effect Aloha Performa

AKBID3222 Windows 95 Illegal Operation with AlohaSpy

AKBID3223 NOREBOOTAFTERSYNCH in the ALOHA.INI

AKBID3224 NOORDERLOCKING in the ALOHA.INI

AKBID3225 NEWEOD in the ALOHA.INI

AKBID3226 FSRECOVERYEOD in the ALOHA.INI

AKBID3227 FOH Login Screen Memory Availability and Usage Figur

AKBID3228 Setting a Custom Resolution in Panel Editor

AKBID3229 Enabling the Substitute Modifier Button

AKBID3231 Multi-site EOD Run Date Error

AKBID3232 Remote Printers Continuously Print Chits

AKBID3233 Adding Memory Status Updates to FOH Debouts

AKBID3234 House Account Log Record Types

AKBID3235 Excluding Voids from Gross Sales on Checkouts

AKBID3236 Aloha Manager is Missing Drop-down Menus or Menu Opt

AKBID3237 MASTERTERMINALID in the ALOHA.INI

AKBID3238 System Date Set to Prior Year Reports Log Corruption

AKBID3239 Dated Folders Missing from Reprint or Audit Report L

AKBID3240 NETBIOSERRORTHRESHOLD in the ALOHA.INI

AKBID3241 Merging Transaction Logs

AKBID3242 Hard Check Printer Only Prints One Line Per Check

AKBID3243 Suppressing Errors for Temporary Terminals

AKBID3244 FOH Check Numbering Scheme

AKBID3245 CTLSVR.EXE Says Another Terminal with the Same Numbe

AKBID3246 QuickService Modifiers to not Auto Flow to Next Modi

AKBID3247 Shifts are not Listed on Labor Reports

AKBID3248 IBM SurePOS 500-xx2 Serial Port Pin-outs and Printer

AKBID3249 QSR Ethernet Creates Very Large Transaction and Vide

AKBID3250 Offline Gift Card Authorizations do not Print Balanc

AKBID3251 Brother Report Printer Prints Reports Inverted and R

AKBID3252 Cash Drawer Opens Each Time the Printer Prints

AKBID3255 Reversing Comp Calculation Order

AKBID3256 Accounting for a Traveling Cash Till on a Single Che

AKBID3257 FOH Cannot Start with Disconnected Veridicom Scanner

AKBID3258 Problems Installing MDAC 2.6 in Windows 2000

AKBID3259 Windows does not Read MSR without a Keyboard Attache

AKBID3260 QuickService Counter Service Errors

AKBID3261 SETUPPOS.EXE Opens a Visual Basic Editor

AKBID3263 Equinox ESP 8 10/100 Serial Hub Printer Cable Pin-ou

AKBID3264 Zero-byte .OLK Files Cause Windows Illegal Operation

AKBID3266 Configuring Network-based Receipt Printers with Aloh

AKBID3269 Equinox SST-8P Serial I/O Adaptor Printer Cable Pin-

AKBID3271 Too Many Delivery Orders Causes FOH to Exit

AKBID3272 Configuring POSIFLEX PD-2500 Customer Display

AKBID3273 NCR OPOS MSR Stops Working After First Swipe

AKBID3275 Configuring the Flytech POS600 MSR for Use with Aloh

AKBID3277 Configuring the CRS IT-8000 2X20 Rear Customer Displ

AKBID3278 NEVERPRINTFOHWAGES in the ALOHA.INI

AKBID3279 Configuring a T.O.D.D. System Controller in Aloha

AKBID3282 Configuring the J2 800 CX MSR for Use with Aloha

AKBID3283 Configuring the ID TECH MiniMag Compact MSR for Aloh

AKBID3285 Using LOCALREAD to Decrease Wireless Network Traffic

AKBID3287 The Aloha Application Software FF.INI

AKBID3288 PMS Interfaces Currently Supported by Aloha

AKBID3289 Using /DEV to Suppress Customer Data Errors During T

AKBID3291 Javelin Cash Drawer Ports Cause Fatal Errors

AKBID3292 Configuring a VeriFone PIN Pad on 'Port 4' on an IBM

AKBID3293 TOFOH.TXN Files

AKBID3294 User 1500n Errors in the Debouts

AKBID3296 Log Corruption Message on a File Server/Terminal

AKBID3297 Senor Tech Co., Ltd. R856008AST Customer Display

AKBID3298 FOH Loses Magnetic Stripe Passwords Following EOD

AKBID3299 FOH Receipt and Chit Printers do not Automatically R

AKBID3300 Aloha FOH Reads Multiple Event Configuration Files

AKBID3301 Enable the FOH to Process BOH EDC Transactions

AKBID3302 Comp and Promo Discount Distribution

AKBID3303 Enable PMS Tip or Tender Adjustments on Closed Check

AKBID3304 Configuring the CRS IT-1000-TM1K-2K 2-track MSR

AKBID3305 Configuring the J2 800 CX Customer Display for Use w

AKBID3306 Price Text Overwrites Graphics on AccuVIEW 150 Displ

AKBID3309 Touch Screens Register Touch to the Previously Touch

AKBID3310 Historical P-Mix Reports using Current Configuration

AKBID3311 Windows 95 Terminals do not Detect Windows 2000+ Fil

AKBID3312 Configuring VeriFone PIN Pads for Use with Aloha

AKBID3313 Forcing End-of-Day from Outside of Aloha

AKBID3314 QuickService with RDS Consumes System Resources

AKBID3316 Printing Multiple Copies of Chits on a Terminal's Lo

AKBID3317 Radiant RJ12 serial port Pin-outs and Cables

AKBID3318 Configuring the Radiant Systems P15xx MSR for Aloha

AKBID3319 Enabling FOH EDC Transactions for Less Than $1.00

AKBID3320 EGI Causes Windows Error on DigiCom Terminals

AKBID3321 DEFAULTREVENUECENTER in the ALOHA.INI

AKBID3322 RDB Report Date Ranges

AKBID3323 Non-SERVERCAPABLE Terminals do not Sync Config Files

AKBID3324 FASTECHGIFTCERT=Obsolete in the ALOHA.INI

AKBID3326 Radiant P701 Customer Display OPOS Configuration

AKBID3327 Radiant 16-inch Printer Driven Cash Drawer Cable Pin

AKBID3328 'Got Message Type 287 from BOH' Message in Debouts

AKBID3329 Configuring the Radiant Systems P1210 Integrated MSR

AKBID3330 Configuring the Radiant P1210 Integrated Customer Di

AKBID3331 Configuring the Radiant Systems P400 MSR for Aloha

Go to Top

EDC

AKBID1006 Configuring Windows User and Share Permissions for Alo

AKBID1007 Default Aloha Windows Desktop Icons

AKBID1010 Aloha Application Software System Environment Variable

AKBID1019 Manually Registering and Un-registering Aloha Applicat

AKBID1020 EDC Process

AKBID1046 Postponing Daily Batch Settlement

AKBID1048 Aloha Hardware and OS Specifications

AKBID1049 Installing DCOM in Windows

AKBID1050 Remote EDC

AKBID1051 Aloha Application Software Flag and Marker Files

AKBID1056 Upgrading the Aloha Application Software

AKBID1062 Property Management Systems

AKBID1082 Separate QS and TS Installations on a Single Demo Comp

AKBID1095 Stand-Alone EDC File Server

AKBID1107 Aloha Application Software Fault Tolerance Functionali

AKBID1109 ICVERIFY

AKBID1118 Supersite IBERCFG.BAT

AKBID1123 Multiple Concept EDC on a Single File Server

AKBID1128 Moving Aloha Data to a New File Server

AKBID1134 Debouts

AKBID1148 Backup Procedures

AKBID1162 Microsoft Windows Service versus a Standard Applicatio

AKBID1166 Aloha Manager BOH Security Files

AKBID1167 Temporarily Disabling EDC for Modem Availability

AKBID1170 Multiple Versions of Aloha on a Single Demo Computer

AKBID1173 Demo Aloha without a HASP Key

AKBID1174 Stand Alone EDC File Server for Multiple Concepts

AKBID1179 Aloha BIN Folder File Contents

AKBID1183 Recommended Hard Drive Partitions, File Systems, and S

AKBID1189 EDC Modem Initialization Strings

AKBID1190 Host-based Credit Card Processors

AKBID1191 Common EDC Processor Errors

AKBID1192 Troubleshooting EDC Spooling

AKBID1197 Assigning Logins to Aloha Services

AKBID1198 Magnetic Stripe Card Information

AKBID1204 Default Aloha System Environment Variable Placement

AKBID1212 Aloha Application Software Version Numbering Scheme

AKBID1213 Using EDC Linger Time to Decrease Authorization Time

AKBID1222 Configuring Aloha Applications as the Windows Shell

AKBID1231 Masking Credit Card Numbers

AKBID1234 Configuring Aloha to Conform with the Visa CISP Guidel

AKBID3022 Windows NT/Windows 2000 HASP Key BSOD

AKBID3024 Erase Sales Data for Go Live

AKBID3039 Masking the Credit Card Numbers on the Guest Check

AKBID3041 Masking the Credit Card Number on the Voucher

AKBID3053 Terminal-Specific EDC Processors

AKBID3054 Remote pcANYWHERE Report Printing

AKBID3056 Unable to Locate Security Descriptor

AKBID3066 Supersite PMS Settlement

AKBID3090 Using IBEREXE.DLL to Disable the Super-Secret-Passwo

AKBID3121 Setting the Credit Card Refund Limit

AKBID3138 Default EDC.EXE Window Size and Position

AKBID3150 Editing Microsoft Windows Me Environment Variables

AKBID3163 Ordinal not Found in Dynamic Link Library

AKBID3170 Report Layout or Display Anomalies

AKBID3192 4.4x EDC Security Server Error

AKBID3198 EDC Processors Currently Supported by Aloha

AKBID3199 Credit Card Lengths and Prefixes

AKBID3200 Increasing Credit Card Authorization Speed

AKBID3201 Temporarily Moving EDC TXN Files

AKBID3202 EDC Configuration not Saving Properly

AKBID3203 Duplicate Credit Card Transactions

AKBID3204 US Robotics 56K Modem Hang-up Issue

AKBID3205 FOH Hangs on Starting EDC

AKBID3208 EDC Reports Less Than Total Settlement

AKBID3221 Real-time Virus Protection Can Effect Aloha Performa

AKBID3254 Supported Gift Card Transaction Types and Codes

AKBID3267 'Processor Not Configured' Error with Private Label

AKBID3270 Configuring EDC TCP Timeout and Retries

AKBID3274 EDC 'CEdcDlg::OnInitDialog' Error

AKBID3280 Port Used by EDCSVR.EXE for SSL Credit Card Authoriz

AKBID3281 Internet Credit Card Authorization via a Proxy Serve

AKBID3288 PMS Interfaces Currently Supported by Aloha

AKBID3301 Enable the FOH to Process BOH EDC Transactions

AKBID3307 Settling Gift Card Transactions in EDC

AKBID3308 Credit Card Adjustments Fail Because of Duplicate Tr

AKBID3315 Configuring CES/First Data IPN Terminal ID Numbers

AKBID3325 First Data IPN Requires DW.DLL

Go to Top

BackOffice

AKBID1006 Configuring Windows User and Share Permissions for Alo

AKBID1007 Default Aloha Windows Desktop Icons

AKBID1008 BackOffice Interfaces & RPC Service

AKBID1010 Aloha Application Software System Environment Variable

AKBID1034 Using a WAN and Corporate Gift Certificates

AKBID1048 Aloha Hardware and OS Specifications

AKBID1049 Installing DCOM in Windows

AKBID1051 Aloha Application Software Flag and Marker Files

AKBID1056 Upgrading the Aloha Application Software

AKBID1062 Property Management Systems

AKBID1073 Using Aloha Without Enabling Administrator Permissions

AKBID1107 Aloha Application Software Fault Tolerance Functionali

AKBID1120 Delivery Street Address File (ZONE.TXT)

AKBID1127 Printing BackOffice Gift Certificates When Sold

AKBID1130 Remote Aloha Labor Scheduler

AKBID1134 Debouts

AKBID1135 Using E-Messenger and Corporate Gift Certificates

AKBID1136 Exporting BackOffice Customer Data

AKBID1140 Remote BackOffice Gift Certificate Workstation

AKBID1141 Remote BackOffice Accounts Receivable Workstation

AKBID1142 Remote BackOffice Delivery/Frequent Buyer Workstation

AKBID1143 E-Messenger PACKAGE.DAT Files

AKBID1144 Importing Aloha Daily Sales Data into BackOffice Inven

AKBID1148 Backup Procedures

AKBID1151 Remote BackOffice Inventory Control Workstation

AKBID1152 Remote BackOffice Advanced Reservations Workstation

AKBID1166 Aloha Manager BOH Security Files

AKBID1168 Configuring Gift Cards for Use with Gift Certificate M

AKBID1173 Demo Aloha without a HASP Key

AKBID1180 Moving BackOffice Data

AKBID1183 Recommended Hard Drive Partitions, File Systems, and S

AKBID1198 Magnetic Stripe Card Information

AKBID1220 Assigning the HASP LPT Port in the Aloha Application S

AKBID1222 Configuring Aloha Applications as the Windows Shell

AKBID1236 Moving a CIM SQL Database to a New File Server

AKBID3028 Labor Scheduler Login

AKBID3029 Labor Scheduler Pay Periods do not Appear

AKBID3035 Gift Certificate Get_Entry_Name Error

AKBID3037 BackOffice Green Keys

AKBID3054 Remote pcANYWHERE Report Printing

AKBID3078 Delivery Interface not Responding to FOH

AKBID3102 BackOffice Interface Startup Shortcut Location

AKBID3124 Delivery/Frequent Buyer POS Discount ID

AKBID3125 Inventory Control Event Viewer is Empty

AKBID3126 Inventory Control Event Viewer Warns of Uncosted Ite

AKBID3127 Current period ends' is Blank in Inventory Control

AKBID3135 Gift Certificates Not in Aloha Manager Payments Menu

AKBID3150 Editing Microsoft Windows Me Environment Variables

AKBID3158 Use Any Area Code in Delivery/Frequent Buyer

AKBID3160 Exporting BackOffice General Ledger Activity

AKBID3163 Ordinal not Found in Dynamic Link Library

AKBID3164 BackOffice Shortcut 'Start in' Settings

AKBID3166 Meal Accountability System On-screen Keyboard

AKBID3182 Enable 'Set Customer Balance to Zero' Option in A/R

AKBID3184 Running ALS in Demo Mode with a HASP Key

AKBID3194 Configuring Customer Cards for Use with Frequent Buy

AKBID3207 No 'Labor Scheduler' Drop-down Menu in Aloha Manager

AKBID3210 BackOffice 'Invalid Activation Key' Message

AKBID3213 Customer Lookup Screen Only Displays for an Instant

AKBID3218 Issued Certificate Report Status Codes

AKBID3221 Real-time Virus Protection Can Effect Aloha Performa

AKBID3265 Incorrect ALS Installation Path Causes 'Anomalies'

AKBID3268 Purging ALS Data in Order to Increase Available Disk

AKBID3332 Unit Definition Error When Opening Gift Certificate

Go to Top

Answer Wizards

AKBID10001 EDC is not Automatically Processing Spooled Files

AKBID10002 Terminals do not Detect the File Server

AKBID10003 Terminals do not Detect Each Other or Constantly Reboo

AKBID10004 File Server Recovery does not Work

AKBID10005 File Server does not Recognize the HASP Security Key

AKBID10008 Terminals Display 'Waiting for System Configuration to

AKBID10009 Terminals Display 'Waiting for Multi Server Sync to Co

AKBID10010 Terminals Display 'Waiting to Grind YYYYMMDD'

AKBID10011 Soft Key Upgrade is not Working

AKBID10012 EDC.EXE Only Displays File and Report Drop-Down Menus

AKBID10013 Expired HASP Key

AKBID10014 Events do not Fire Automatically

AKBID10015 FOH Sticks on 'Terminal Up' or Blank Message

AKBID10016 BOH Passwords are Deleted After EOD

AKBID10017 Employee Locked on Another Terminal

AKBID10018 Failed to Register Station Name, 0x34' Error

AKBID10019 FOH Terminals Ask for Windows User Name and Password

AKBID10020 BackOffice Interface Does not Respond to FOH

AKBID10021 Invalid DATA Path Causes Aloha Manager Security Setup

Go to Top
Configuring the CALIBRATE Variable on Aloha Terminals

Configuring the CALIBRATE Variable on Aloha Terminals

============================================================================

AKBID1001

Created: 8 December 1999

Updated: 2 March 2004

Reviewed: 2 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: Aloha Terminal Touch Screen Calibration Settings

============================================================================

Summary

The ALOHA^� application software enables users to calibrate the touch screen terminals from within the Front-of-House (FOH).� The CALIBRATE environment variable supplies the Aloha application software with the correct calibration utility.� The utility varies with the operating system (OS) and touch screen software you are using.

If you have a touch screen that is not listed in this document or the manufacturer has altered the name or location of the calibration application, please email [email protected] with the OS, touch screen type, and calibration variable (if known).

Information

The CALIBRATE variable sets the path to the touch screen calibration utility.� The OS determines the location in which the CALIBRATE variable is set.� Refer to document AKBID1204 for the default Aloha application software environment variable placement.

Locate the correct calibration utility provided by the touch screen vendor and any command line options that it requires.� Below are some examples of variables for different operating systems and touch screen software.� These can vary depending on the path and folder in which your touch screen software is installed.

Dynapro with Windows 9x

SET CALIBRATE=C:\TOUCH\W95\TOUCHCFG.EXE

EloTouch with Windows 9x

SET CALIBRATE=C:\WINDOWS\SYSTEM\ELOCAL32.EXE

MicroTouch

SET CALIBRATE=C:\PROGRA~1\MICROT~1\TOUCHW~1\MTSCAL.EXE /C

Refer to the MicroTouch TouchWare for Windows User's Guide for more information.

Radiant Systems P400 and P1550

�� SET CALIBRATE=TCALIB.EXE

Radiant Systems P1210

�� SET CALIBRATE=C:\PROGRA~1\ETURBO~1\ETURBO~1\ETURBO.EXE

Extended Information

When the FOH initializes the calibration routine, it uses the following command line:

x /HWND y

'x' represents the command line assigned to the CALIBRATE variable.� '/HWND' are built in command line variables that are often ignored by the calibration application.� 'y' is a number generated by Windows that acts as a 'handle' for the application, and it is generally ignored by the calibration application.�

To view these variables first-hand, assign NOTEPAD.EXE to the CALIBRATE variable, and attempt to calibrate the touch screen from the FOH.� This creates an error message that displays the command line parameters.

Although most calibration applications ignore these variables, they may affect some others.� In this case, create a batch file called CALIB.BAT.� Add the correct calibration command line to CALIB.BAT, and assign CALIB.BAT to the CALIBRATE variable.�

Caveats

No information.

============================================================================

See also:

Aloha TableService or QuickService User Manual

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1001 elodev found touchscreen

Aloha Receipt and Kitchen Printer Settings and Pin-outs

Aloha Receipt and Kitchen Printer Settings and Pin-outs

============================================================================

AKBID1002

Created: 9 December 1999

Updated: 16 April 2004

Reviewed: 16 April 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: DIP Switch and Cable Settings for the Aloha Application Software Printers

============================================================================

Summary

The majority of printer problems associated with the ALOHA^� application software consists of two things: dual in-line package (DIP) switches and cable pin-outs.� This document lists general configuration settings, DIP switch settings for approved printers, and the cable pin-outs used with the Aloha application software.

Some switches might vary depending on the auto-cutter option on the printer.� This might cause mechanical errors if set incorrectly.� Consult the printer's user manual for more information.

Some printers in this document might not be officially approved for use with the Aloha application software.� Refer to document AKBID1048 for a list of approved hardware.

Some printers might not be compatible with all versions of the Aloha application software.� Contact Aloha Technologies to verify version compatibility.

Unless otherwise stated, the printer settings and cable pin-outs listed in this document only apply to printers driven by native Aloha application software drivers, not OLE for Retail Point-of-Sale (OPOS) drivers or Windows-based drivers.� Refer to document AKID1074 for more information on OPOS drivers or AKBID1026 for more information on Windows-based drivers.

Information

LPT Port Settings

You need to set your parallel ports to Standard or EPP in the BIOS if you are using parallel printers.� If parallel printers continue to print slowly, consider using the printer's OPOS drivers (refer to document AKBID1074).

If you are using a parallel receipt or chit printer, then you must ensure that the LPT port is not set to ECP mode in either the system BIOS or in the Windows hardware configuration.� Configuring the LPT port to ECP mode can result in system lock-ups.

FIFO Buffers

Microsoft^� Windows^� 95, Windows 98, Windows Millennium Edition (Me), Windows 2000, and Windows XP offer the option to enable First-In-First-Out (FIFO) buffers on the terminal's COM ports.� These buffers tend to interfere with printers using Xon/Xoff flow control.� Aloha Technologies disables these buffers on all COM ports on all terminals by default, regardless of the printer type.� (In the event of a printer or COM port failure, a replacement printer using Xon/Xoff flow control might be temporarily connected to the port in the future.)

To access the FIFO buffer settings, open Windows Device Manager via the System Control Panel applet.� Click the plus sign (+) next to Ports to expand it.� Select each port one at a time, and select Properties/Port Settings/Advanced.� Clear the Use FIFO buffer.� Perform this on each COM port.� The LPT port does not have this option.

Printer Buffers

In some cases, a printer might not function properly using the printer's smaller buffer size, but the printer will function properly if you increase the buffer size to the higher setting.� In this case, Aloha Technologies has found that although the printer functions properly most of the time, it is still prone to sporadic problems that are not easily diagnosed because of their randomness.� In other words, the problems still exist, but they are just masked a little better.

Since the Aloha application software should not encounter errors printing to printers using the smaller buffer size (it is actually preferred over the larger buffer), you should rectify the problem when encountering printer problems with the smaller buffer size rather than patching them with a larger buffer size.� Consistent problems with the smaller buffer size are much easier to troubleshoot than sporadic problems with the larger buffer size.

In most cases, the problems are caused by printer cables, FIFO buffers, or incorrect data flow settings.

OPOS Printers

The information in this document does not apply to OPOS printers since the Aloha application software does not directly communicate with OPOS printers.� Instead, the Aloha application software communicates with the OPOS drivers (supplied by the printer manufacturer), and the OPOS drivers communicate with the printer.� For this reason, the printer manufacturer should provide you with the cable pin-outs and DIP switches for use with their OPOS drivers.� In general, they use the printer's default DIP switch configuration and the cable pin-outs described in document AKBID1074, but this is not a hard rule.

Refer to document AKBID1074 for more information on OPOS.

CBM 354x Serial

You must have a Star ROM in CBM 354x printers.� The descriptive ID on the bottom of the printer identifies a printer with the Star ROM.� If the ID includes a 'S', the printer has a Star ROM.� If the ID includes a 'R', it does not have a Star ROM.

Define the printer as a Star 300 in the Aloha application software.�

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

SW9

SW10

Set 1

Off

On

On

On

On

On

On

On

On

On

Set 2

On

Off

Off

On

On

On

Off

On

-

-

CBM CBM-710/720/730, and CBM-750 Serial (40 column version)

Define the printer as a Citizen CBM-750 in the Aloha application software.�

(SW1 on Set 1 sets the auto-cutter)

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

On

Off

Off

Off

Off

Off

Off

Off

Set 2

Off

Off

On

Off

On

On

On

Off

Serial DB9 to CBM-7xx DB25

DB9

1

2

3

5

6

9

DB25

12

2

3

7

20

11

Serial DB25 to CBM-7xx DB25

DB25

1

2

3

6

7

8

22

DB25

1

3

2

20

7

12

11

CBM CBM-1000 Serial

CBM-1000 printers require firmware version MPV1.01 or higher.

Define the printer as an Epson TM-80 in the Aloha application software.

(SW1 on Set 1 sets the auto-cutter)

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

On

Off

Off

Off

Off

Off

On

Off

Set 2

Off

Off

Off

Off

Off

Off

Off

Off

Set 3

Off

On

On

On

On

Off

Off

Off

Set 4

Off

On

Off

Off

-

-

-

-

CBM CBM-1000 Type II Serial

Define the printer as an Epson TM-80 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

SW9

SW10

Set 1

On

Off

Off

Off

Off

On

On

Off

-

-

Set 2

Off

Off

Off

Off

Off

Off

Off

Off

Off

Off

Set 3

Off

On

On

On

On

Off

Off

Off

-

-

CBM iDP3240 Serial

Define the printer as an Epson TM-80 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

On

Off

Off

Off

Off

On

On

Off

Set 2

Off

Off

Off

Off

Off

Off

Off

Off

Set 3

Off

On

On

On

-

-

-

-

Set 4

Off

On

Off

Off

-

-

-

-

Eltron/Zebra Technologies LP2742

The Eltron^� or Zebra Technologies LP2742 uses a straight-through serial cable.

Epson TM-H6000 Serial

Define the printer as an Epson H6000 in the Aloha application software.

Although the Aloha application software supports both the slip printer and receipt printer in TableService, QuickService only supports the receipt printer.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

Off

On

Off

On

On

Off

On

Set 2

Off

Off

Off

Off

Off

Off

Off

Off

Epson TM-T80 Serial

Define the printer as an Epson TM-80 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

SW9

SW10

Set 1

Off

On

On

On

On

On

Off

Off

Off

Off

Epson TM-T85 Serial

Define the printer as an Epson TM-80 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

On

On

Off

On

On

On

Off

Set 2

Off

Off

Off

Off

Off

Off

Off

Off

Epson TM-T88 Parallel

Define the printer as an Epson TM-80 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

On

On

Off

On

On

On

Off

Set 2

Off

Off

Off

Off

Off

Off

Off

Off

Epson TM-T88 Serial

Define the printer as an Epson TM-80 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

On

On

Off

On

On

On

Off

Set 2

Off

Off

Off

Off

Off

Off

Off

Off

Epson TM-U200 Serial

In Aloha versions 5.025 and lower, define the printer as an Epson 300 in the Aloha application software.� In Aloha versions 5.026 and higher, define the printer as an Epson U200 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

On

On

Off

On

On

Off

Off

Set 2

Off

On¹

Off

On

-

-

-

-

¹Set this switch to the Off position if the printer lacks an auto-cutter.

Epson TM-U200 Parallel

In Aloha versions 5.025 and lower, define the printer as an Epson 300 in the Aloha application software.� In Aloha versions 5.026 and higher, define the printer as an Epson U200 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

On

Off

Off

Off

Off

Off

Off

Set 2

Off

On¹

Off

On

-

-

-

-

¹Set this switch to the Off position if the printer lacks an auto-cutter.

Epson TM-U220 Serial

Define the printer as an Epson U200 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

On¹

On

Off

On

On

Off

Off

Set 2

Off

On²

Off

Off

Off

Off

Off

Off

¹Set this switch to the Off position if you experience problems with misaligned text or missing characters

²Set this switch to the Off position if the printer lacks an auto-cutter.

Epson TM-295 Serial

Define the printer as an Epson TM-295 in the Aloha application software.

The Aloha application software does not support 'line find' on slip printers in versions 5.0x and lower.� For example, when you insert a hard check into the printer, the Aloha application software does not search for the next unused line, but instead, the Aloha application software starts printing as if printing to a blank slip.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

SW9

SW10

Set 1

On

On

Off

Off

On

On

Off

Off

Off

Off

Epson TM-U300 Serial

Define the printer as an Epson 300 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

SW9

SW10

Set 1

Off

Off

On

Off

On

On

Off

Off

Off

On

IBM SureMark 4610 Serial

Define the printer as an OPOS printer in the Aloha application software.� This configuration requires Aloha version 5.026 or higher and installation of IBM OPOS drivers.� Refer to documents AKBID1074 and AKBID1172 for more information.

Refer to document AKBID3248 for more information on cable pin-outs if you are using with printer with an IBM SurePOS 500-xx2.

SW1

SW2

SW3

SW4

Set 1

Off

Off

Off

Off

Ithaca (TransAct) iTherm 280 Serial

Define the printer as an Epson 80 in the Aloha application software.� Adjust the printer configuration to 9600/8/E/1/XON-XOFF, Epson TM-T88 emulation mode.

Ithaca (TransAct) Model 82 Plus Serial

Define the printer as an Epson TM-80 in the Aloha application software.� Adjust the configuration to 9600/8/E/1/XON-XOFF, TM-T88 Emulation Mode.� Use the default configuration mode with the default parity changed to even parity.� If you are installing Ithaca Series 80 printers, we recommend you order the Ithaca Series 80 Programmer's Guide from Ithaca as outlined in the printer's Operator's Guide.� It contains instructions on adjusting the printer's configuration settings.

Ithaca (TransAct) Model 82 Plus Parallel

Define the printer as a Epson TM-80 in the Aloha application software.� Use the default configuration mode.� If you are installing Ithaca Series 80 printers, we recommend you order the Ithaca Series 80 Programmer's Guide from Ithaca as outlined in the printer's Operator's Guide.� It contains instructions on adjusting the printer's configuration settings.

Ithaca (TransAct) Series 1000 Serial

Define the printer as an Epson U200 in the Aloha application software or use OPOS drivers.� If you are configuring the printer as an Epson TM-U200 in the Aloha application software, adjust the configuration to 9600/8/E/1/XON-XOFF, Epson Emulation Mode.� If you are configuring the printer as an OPOS printer in the Aloha application software, use the manufacturer's recommended settings.

Ithaca (TransAct) POSjet 1000 Serial

Define the printer as an Epson U200 in the Aloha application software.� Adjust the printer configuration to 9600/8/E/1/XON-XOFF, Epson Emulation Mode.

Nanoptix C21-BNSAB/C21-BNSBB Spill Proof Thermal Printer

Define the printer as an Epson TM-80 in the Aloha application software.

Configure the printer to 9600/8/E/1/XON-XOFF.� You must use firmware Aloha V2.42H-61AU8BHe or higher.

Use a straight-thru cable pin-out.

NCR 7193 Serial

Define the printer as an Epson TM-80 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

Set 1

Off

On

Off

Off

On

Off

NCR 7194 Serial

Define the printer as an Epson TM-80 in the Aloha application software and use the printer's default settings.

Olivetti OST12 Serial

Define the printer as an Epson U200 in the Aloha application software.� Adjust the configuration to 9600/8/E/1/XON-XOFF, ESC/POS Mode, and set the 'Chars / inchs' to 'A=15 B=20 cpi' in order to avoid some larger text wrapping to a second line.

Partner Tech Corp RP-200

Define the printer as an Epson TM-80 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

SW9

SW10

Set 1

Off

Off

Off

Off

On

On

Off

On

Off

On

Set 2

Off

Off

Off

Off

-

-

-

-

-

-

Samsung SRP-270

Define the printer as an Epson 300 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

Off

On

Off

Off

Off

Off

Off

Set 2

Off

Off

On

Off

On

On

Off

Off

Samsung SRP-270C

Define the printer as an Epson U200 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

Off

On

Off

On

On

Off

Off

Set 2

Off

Off

On

Off

Off

Off

Off

Off

Samsung SRP-350

Define the printer as an Epson TM-80 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

Off

On

Off

On

On

On

Off

Set 2

Off

Off

Off

Off

Off

Off

Off

Off

Samsung SRP-500C Serial and Parallel

Define the printer as an Epson U200 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

Off

On

Off

Off

Off

Off

Off

Set 2

Off

Off

Off

Off

On

On

Off

Off

Star 8340 Serial

Define the printer as a Star 8340 in the Aloha application software.

If printed receipt characters appear distorted because the last two characters appear on the next line, set the printer type to Star 300 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

On

On

On

On

On

On

Off

Off

Set 2

On

On

On

On

-

-

-

-

Star 300/312 Serial

Define the printer as a Star 300 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

On

On

On

On

On

On

On

On

Set 2

On

On

On

On

On

On

On

On

Set 3

On

On

On

On

On

On

Off

Off

Set 4

On

On

On

On

On

On

On

On

Star 300/312 Parallel

Define the printer as a Star 300 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

On

On

On

On

On

On

On

On

Set 2

On

On

On

On

On

On

On

On

Star SP512MD

Define the printer as a Star 300 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

SW9

SW10

Set 1

On

On

On

On

On

On

On

Off

Off

On

Star SP2000 Serial

Define the printer as a Star 300 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

On

Off

On

Off¹

On

On

On

On

Set 2

On

On

On

Off

Off

On

Off

Off

¹Set this switch to the On position if the printer lacks an auto-cutter.

Star TSP200 Serial

Define the printer as a Star TSP-200 Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

On

On

On

Off

Off

Off

On

On

Set 2

On

On

Off

Off

-

-

-

-

Star TSP400 Serial

Define the printer as a Star TSP-400 or Star TSP-400 with Cutter in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

On

On

On

On

Off

Off

On

On

Pin-outs for Standard Printer Cables

Serial DB9 to Printer DB25

DB9

2

3

5

8

DB25

2

3

7

20

Serial DB9 to Printer DB9

DB9

2

3

5

8

DB9

3

2

5

4

Serial DB25 to Printer DB25

DB25

2

3

5

7

DB25

3

2

20

7

Serial DB25 to Printer DB9

DB25

2

3

5

7

DB9

2

3

4

5

RJ45 to RS232 Adapter Pin-outs for Standard Printer Cables

Serial DB9 to Printer DB25

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB9

1

2

3

4

5

6

7

8

DB25

Unused

2

3

Unused

7

Unused

Unused

20

Serial DB9 to Printer DB9

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB9

1

2

3

4

5

6

7

8

DB9

Unused

3

2

Unused

5

Unused

Unused

4

Serial DB25 to Printer DB25

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB25

1

2

3

4

5

6

7

8

DB25

Unused

3

2

Unused

20

Unused

7

Unused

Serial DB25 to Printer DB9

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB25

1

2

3

4

5

6

7

8

DB9

Unused

2

3

Unused

4

Unused

5

Unused

Extended Information

Any printer that emulates one of the listed printers will work in the Aloha application software.� All serial printers connected to the Aloha application software use the listed cable pin-out.

If you have a printer that emulates an approved printer, then set the DIP switches to the listed preferences.� For Epson emulation, set the printer to Epson emulation, 9600 baud, even parity, 8 data bits, 1 stop bit, and Xon/Xoff flow control.� For Star emulation, set the printer to Star emulation, 9600 baud, even parity, 8 data bits, 1 stop bit, and DTR/DSR flow control.

Caveats

Some switches might vary depending on the auto-cutter option on the printer.� This might cause mechanical errors if set incorrectly.� Consult the printer's user manual for more information.

Some printers in this document might not be officially approved for use with the Aloha application software.� Refer to document AKBID1048 for a list of approved hardware.

Some printers might not be compatible with all versions of the Aloha application software.� Contact Aloha Technologies to verify version compatibility.

Unless otherwise stated, the printer settings and cable pin-outs listed in this document only apply to printers driven by native Aloha application software drivers, not OLE for Retail Point-of-Sale (OPOS) drivers or Windows-based drivers.� Refer to document AKID1074 for more information on OPOS drivers or AKBID1026 for more information on Windows-based drivers.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1003 Aloha Network Cable Pin-outs

AKBID1004 Serial Pin Assignments

AKBID1026 Using Windows-based Printers with Aloha

AKBID1048 Aloha Application Software Hardware and OS Specifications

AKBID1074 OPOS

AKBID1156 Using Windows Printers Between Stores in SuperSites

AKBID1172 IBM SurePOS 500

AKBID3154 Epson Printer Enunciators

AKBID3248 IBM SurePOS 500-xx2 Serial Port Pin-outs and Printer Cables

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1000 1002 200 220 2000 232 2742 270A 270C 270D 295 300 312 3240 3541 3542 3551 3552 400 6000 80 85 88 citizen db-9 db-25 mark partnertech pinout pinouts rj-45 rs-232 sp500 srp270 srp500 sure tmt tmu tsp u200 u220 x-off x-on

Terminals do not Detect Each Other or Constantly Reboot

Terminals do not Detect Each Other or Constantly Reboot

============================================================================

AKBID10003

Created: 15 November 2000

Updated: 28 April 2003

Reviewed: 20 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

This document is designed to provide a temporary list of resolutions for a specific issue related to the ALOHA^� application software.� The contents of this document will be added to the Aloha Knowledge Base (AKB) Answer Wizards when they are operational, and this document will be deleted.

If the Front-of-House (FOH) terminals do not detect each other or constantly reboot when two or more terminals are started, perform the following:

1.        Verify if each terminal's network name is set in a way consistent with the TERMSTR+TERM nomenclature and there are no spaces in the name.

2.        Verify if the terminal number in the network name matches the terminal's number assigned by the TERM variable.

3.        Verify if read/write network connection exists between each of the FOH terminal's BOOTDRV share.

4.        Verify if the lana number for the network protocol assigned to the Aloha application software is properly configured (refer to document AKBID1018) on each FOH terminal.

5.        If the Aloha application software is communicating using TCP/IP, verify if the IP addresses on the FOH terminals are properly configured (refer to document AKBID1063).

6.        Verify if the TERMSTR, ROBUST (versions 4.4x and lower), NUMTERMS, TERM, and IBERROOT variables have the correct values on each FOH terminal.� If you are using versions 5.030 and lower, the TERMSTR variable is case-sensitive.�

7.        On computers using Microsoft^� Windows^� 95, Windows 98, or Windows Millennium Edition (Me), ensure the VNETBIOS.VXD patch is in place and setup properly (refer to document AKBID1011).

8.        There is an EXITING file in the file server's TMP folder (or the TMP folder of the terminal acting as the file server).

9.        If there site uses a router to communicate, ensure UDP ports 137, 138, and 139 are enabled to allow NetBIOS commands to pass through the router or switch.

Review the Debugging-Output-Files (debouts) on the terminals for further causes.� Refer to document AKBID1134 for more information on debouts.

============================================================================

See also:

AKBID1011 Windows 95, Windows 98, and Windows Me NCB Limit

AKBID1018 Network Lana Numbers

AKBID1063 TCP/IP

AKBID1099 Network Troubleshooting

AKBID1134 Debouts

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 10003 can cannot find recognize

File Server Recovery does not Work

File Server Recovery does not Work

============================================================================

AKBID10004

Created: 15 November 2000

Updated: 29 October 2002

Reviewed: 24 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

============================================================================

This document is designed to provide a temporary list of resolutions for a specific issue related to the ALOHA^� application software.� The contents of this document will be added to the Aloha Knowledge Base (AKB) Answer Wizards when they are operational, and this document will be deleted.

If the file server recovery process is not working properly, perform the following:

Never perform a file server recovery by deleting the DOWNTIME.INI (refer to AKBID1195).

1.        Verify if read/write network connection exists between the file server and the Front-of-House (FOH) terminal's BOOTDRV share.�

2.        Verify if read/write network connection exists between the FOH terminals and the file server's BOOTDRV share.�

3.        Verify if the lana number for the network protocol assigned to the Aloha application software is properly configured (refer to document AKBID1018) on the file server.�

4.        Verify if the lana number for the network protocol assigned to the Aloha application software is properly configured (refer to document AKBID1018) on the FOH terminals.�

5.        If the Aloha application software is communicating using TCP/IP, verify if the IP addresses on the file server and FOH terminals are properly configured (refer to document AKBID1063).�

6.        Verify if the SERVER, TERMSTR, IBERDIR, IBERROOT, and ROBUST variables have the correct values on the file server.� If you are using versions 5.030 and lower, the TERMSTR variable is case-sensitive.�

7.        Verify if the SERVER, TERMSTR, and IBERROOT variables have the correct values on the FOH terminals.� If you are using versions 5.030 and lower, the TERMSTR variable is case-sensitive.�

8.        Check if the REMOTE variable is included in the Control Server command line in the Microsoft^� Windows^� registry (refer to documents AKBID3009) on the file server.�

9.        Verify that the NONET variable is not included in the CTLSVR.EXE (Control Server) command line in the Windows registry (refer to document AKBID3009).�

10.     Verify that the shortcuts to CTL.EXE (Control) or ALOHAMGR.EXE (Aloha Manager) on the file server do not include the REMOTE variable.�

11.     Verify that the shortcuts to CTL.EXE (Control) or ALOHAMGR.EXE (Aloha Manager) on the file server do not include the NONET variable.

12.     On computers using Windows 95, Windows 98, or Windows Millennium Edition (Me), ensure the VNETBIOS.VXD patch is in place and properly configured (refer to document AKBID1011).

Review the Debugging-Output-Files (debouts) on the terminals for further causes.� Refer to document AKBID1134 for more information on debouts.

============================================================================

See also:

AKBID1011 Windows 9x VNETBIOS.VXD Patch

AKBID1134 Debouts

AKBID1195 Deleting the DOWNTIME.INI

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 10004

File Server does not Recognize the HASP Security Key

File Server does not Recognize the HASP Security Key

============================================================================

AKBID10005

Created: 30 October 2000

Updated: 12 September 2003

Reviewed: 8 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

This document is designed to provide a temporary list of resolutions for a specific issue related to the ALOHA^� application software.� The contents of this document will be added to the Aloha Knowledge Base (AKB) Answer Wizards when they are operational, and this document will be deleted.

Perform the following if the file server is not recognizing the Aladdin^� Hardware-Against-Software-Piracy (HASP^�) key and displaying a message stating 'Security key not found':

�

1.        Ensure the HASP key is attached to the parallel (LPT) port or a Universal Serial Bus (USB) port.�

2.        If you are attaching a key to the LPT port, then the HASP key requires a LPT port that supports bi-directional data transfer.� Enhanced-Parallel-Port (EPP), Enhanced-Capabilities-Port (ECP), Bi-directional, and PS/2 LPT port interfaces are bi-directional.� Most Standard-Parallel-Port (SPP) interfaces are also bi-directional.� Ensure the LPT port interface is bi-directional.

3.        Ensure the LPT or USB port is functioning properly.

4.        If this message was generated by the grind application, verify that the soft-key upgrade security key activation codes have been properly configured.

5.        Reinstall the HASP key drivers, as described in document AKBID1112.

6.        Download HASPDIAG.ZIP from the Aloha Technologies FTP site, and extract it to a temporary folder.� Run HASPDIAG.EXE, and select the HASP Test tab.� This shows whether the utility recognizes a HASP key on the LPT or USB port.

7.        If a printer is attached to the security key, detach the printer and verify if the problem persists.

8.        If you are using a LPT port thumbprint scanner along with the HASP security key, refer to document AKBID3212.

9.        If you are using Windows XP, then you must install HASP security key drivers 4.50 or higher.� They are available from http://www.hasp.com.

10.     If you are using version 5.2.7.x or higher with a HASP key attached to the LPT port, then use HASPLPTPORT.EXE to verify the port assigned to the HASP key.� Refer to document AKBID1220 for more information.

Refer to document AKBID1112 for more information.

============================================================================

See also:

AKBID1112 HASP Key Troubleshooting

AKBID1163 FOH HASP Key Expiration

AKBID1220 Assigning the HASP LPT Port in the Aloha Application Software

AKBID3212 Thumbprint Scanner and HASP Key Conflicts

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 10005

style='mso-spacerun:yes'>� 2003

Terminals Display 'Waiting for system configuration to complete'

Terminals Display 'Waiting for system configuration to complete'

============================================================================

AKBID10008

Created: 30 October 2000

Updated: 12 November 2001

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

This document is designed to provide a temporary list of resolutions for a specific issue related to the ALOHA^� application software.� The contents of this document will be added to the Aloha Knowledge Base (AKB) Answer Wizards when they are operational, and this document will be deleted.

Perform the following if the Front-of-House (FOH) terminals do not properly synchronize the DATA and/or BMP folder(s) with the file server or the FOH terminals display a message stating 'Waiting for system configuration to complete':

Ensure each FOH terminal has BIN, BMP (versions 5.0x and lower), DATA, NEWBIN, RECIPE, and TMP folders inside the Aloha application software folder.� The Aloha application software versions 5.2x and higher compensate for subfolders within the BMP folder in order to enable multi-resolution bitmaps (refer to document AKBID1201).

Ensure an OK file (refer to document AKBID3008) exists in the DATA folder on the file server.

Ensure the BOOTDRV share on each FOH terminal and the file server enables access to the Aloha application software folders between the file server and terminals.

Review the Debugging-Output-Files (debouts) on the terminals for further causes, such as a zero-byte or read-only file.� Refer to document AKBID1134 for more information on debouts.

============================================================================

See also:

AKBID1134 Debouts

AKBID1201 Multi-resolution Bitmap Placement

AKBID3008 OK File

AKBID3013 Sub-folders Inside System Folders

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 10008 copy copying fail failing fails subdirectories subdirectory synchronizing

Terminals Display 'Waiting for Multi Server Sync to Complete'

Terminals Display 'Waiting for Multi Server Sync to Complete'

============================================================================

AKBID10009

Created: 30 October 2000

Updated: 12 November 2002

Reviewed: 2 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

This document is designed to provide a temporary list of resolutions for a specific issue related to the ALOHA^� application software.� The contents of this document will be added to the Aloha Knowledge Base (AKB) Answer Wizards when they are operational, and this document will be deleted.

If the Front-of-House (FOH) terminals display a message stating 'Waiting for Multi Sync to Complete', perform the following:

1.        Verify if the TERMSTR environment variable is set and is correct on the file server and each terminal.

2.        Verify if the SERVER environment variable is set and is correct on the file server and each terminal.

3.        Verify if the IBERROOT environment variable is set and is correct on the file server and each terminal.

4.        Review the Debugging-Output-Files (debouts) on the terminals for further causes.� Refer to document AKBID1134 for more information on debouts.

Refer to document AKBID3092 for more information on the MSYNC file.

============================================================================

See also:

AKBID1134 Debouts

AKBID3092 MSYNC File

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 10009

Configuring the CALIBRATE Variable on Aloha Terminals

Configuring the CALIBRATE Variable on Aloha Terminals

============================================================================

AKBID1001

Created: 8 December 1999

Updated: 2 March 2004

Reviewed: 2 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: Aloha Terminal Touch Screen Calibration Settings

============================================================================

Summary

The ALOHA^� application software enables users to calibrate the touch screen terminals from within the Front-of-House (FOH).� The CALIBRATE environment variable supplies the Aloha application software with the correct calibration utility.� The utility varies with the operating system (OS) and touch screen software you are using.

If you have a touch screen that is not listed in this document or the manufacturer has altered the name or location of the calibration application, please email [email protected] with the OS, touch screen type, and calibration variable (if known).

Information

The CALIBRATE variable sets the path to the touch screen calibration utility.� The OS determines the location in which the CALIBRATE variable is set.� Refer to document AKBID1204 for the default Aloha application software environment variable placement.

Locate the correct calibration utility provided by the touch screen vendor and any command line options that it requires.� Below are some examples of variables for different operating systems and touch screen software.� These can vary depending on the path and folder in which your touch screen software is installed.

Dynapro with Windows 9x

SET CALIBRATE=C:\TOUCH\W95\TOUCHCFG.EXE

EloTouch with Windows 9x

SET CALIBRATE=C:\WINDOWS\SYSTEM\ELOCAL32.EXE

MicroTouch

SET CALIBRATE=C:\PROGRA~1\MICROT~1\TOUCHW~1\MTSCAL.EXE /C

Refer to the MicroTouch TouchWare for Windows User's Guide for more information.

Radiant Systems P400 and P1550

�� SET CALIBRATE=TCALIB.EXE

Radiant Systems P1210

�� SET CALIBRATE=C:\PROGRA~1\ETURBO~1\ETURBO~1\ETURBO.EXE

Extended Information

When the FOH initializes the calibration routine, it uses the following command line:

x /HWND y

'x' represents the command line assigned to the CALIBRATE variable.� '/HWND' are built in command line variables that are often ignored by the calibration application.� 'y' is a number generated by Windows that acts as a 'handle' for the application, and it is generally ignored by the calibration application.�

To view these variables first-hand, assign NOTEPAD.EXE to the CALIBRATE variable, and attempt to calibrate the touch screen from the FOH.� This creates an error message that displays the command line parameters.

Although most calibration applications ignore these variables, they may affect some others.� In this case, create a batch file called CALIB.BAT.� Add the correct calibration command line to CALIB.BAT, and assign CALIB.BAT to the CALIBRATE variable.�

Caveats

No information.

============================================================================

See also:

Aloha TableService or QuickService User Manual

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1001 elodev found touchscreen

Terminals Display 'Waiting to Grind YYYYMMDD'

Terminals Display 'Waiting to Grind YYYYMMDD'

============================================================================

AKBID10010

Created: 30 October 2000

Updated: 16 April 2003

Reviewed: 20 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

This document is designed to provide a temporary list of resolutions for a specific issue related to the ALOHA^� application software.� The contents of this document will be added to the Aloha Knowledge Base (AKB) Answer Wizards when they are operational, and this document will be deleted.

If the grind process does not automatically initialize, verify the following:

1.        CTLSVR.EXE (Control Server) is not active (closed or exited) on the file server.�

2.        The 'Auto Grind and Summarize' flag is cleared in Control (for versions 4.4 and lower).

3.        DISABLEAUTOFILEPROCESSING is set to TRUE in the ALOHA.INI located in the Aloha application software DATA folder (for versions 5.0x and higher).� You need to ensure that this variable is set to FALSE.

4.        The Summary file creation is interfering with automatic grinding of the new dated folder's data (refer to document AKBID1081).� Disable the summary files if you do not need them.

5.        A Winhook file is defined in the configuration files, but the batch file does not exist in the BIN folder (refer to document AKBID1028).�

6.        The hard drive has run out of available space (refer to document AKBID1014).�

7.        The shortcut for Control or Aloha Manager includes the REMOTE variable (refer to document AKBID3110).�

8.        The command line variables for Control Server include the REMOTE variable (refer to document AKBID3110).�

9.        The TRANS.LOG (transaction log) or a database file (.DBF or RDB) is corrupted.�

10.     A NOGRIND file exists in the store's folder (RDB systems only).� Refer to document AKBID1051.

11.     'Disable Auto-Grind and Summarize' is enabled in Maintenance/Options/BOH Controls or Aloha Manager/Maintenance/Store Settings/System/Aloha Settings.

12.     Control or Control Server is hung up waiting for a Winhook batch file from the previous Date-of-Business (DOB) to complete.

13.     If you have Control Server configured to log in with a specific user rather than the built-in Windows System account, ensure that the login has administrative privileges.

For more information on the Grind process and the solutions listed in this document, refer to document AKBID1016.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1014 Full Hard Drive Recovery

AKBID1016 Grind Process and Errors

AKBID1028 Winhook

AKBID1051 Aloha Application Software Flag and Marker Files

AKBID1081 Summary Process and Files

AKBID3110 The REMOTE Variable

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 10010 auto autogrind

Soft Key Upgrade is not Working

Soft Key Upgrade is not Working

============================================================================

AKBID10011

Created: 15 November 2000

Updated: 16 April 2003

Reviewed: 11 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.246 � 5.3.x

============================================================================

This document is designed to provide a temporary list of resolutions for a specific issue related to the ALOHA^� application software.� The contents of this document will be added to the Aloha Knowledge Base (AKB) Answer Wizards when they are operational, and this document will be deleted.

If soft-security-key (softkey) upgrades do not work properly, perform the following:

Verify that you are using CTLSVR.EXE (Control Server) is 4.246f or higher.

Verify that you correctly entered the HASP^� security key activation codes.

The upgraded HASP security key activation codes are not for a different key.

Control Server is running.

Verify that you have correctly set the LOCALDIR system environment variable in the Front-of-House.

The ALOHA.INI (with the new HASP security key activation codes) has propagated to the terminals.

Aloha Technologies upgraded the HASP security key activation codes to the correct options.

You have installed the HASP security key driver.

If the FOH is displaying an error stating 'Wrong Security Key', ensure that you have restarted Control Server since updating the new HASP security key activation codes.� If you have not done so, then the BOH is broadcasting one set of codes while the FOH is reading a different set of codes from the ALOHA.INI.

�

Review the Debugging-Output-Files (debouts) on the terminals for further causes.� Refer to document AKBID1134 for more information on debouts.

============================================================================

See also:

AKBID1112 HASP Key Troubleshooting

AKBID1134 Debouts

AKBID1163 FOH HASP Key Expiration

AKBID3016 HASP Driver

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 10011

EDC.EXE Only Displays File and Report Drop-Down Menus

EDC.EXE Only Displays File and Report Drop-Down Menus

============================================================================

AKBID10012

Created: 15 December 2000

Updated: 8 January 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 4.2x - 5.3.x

============================================================================

This document is designed to provide a temporary list of resolutions for a specific issue related to the ALOHA^� application software.� The contents of this document will be added to the Aloha Knowledge Base (AKB) Answer Wizards when they are operational, and this document will be deleted.

Perform the following if EDC.EXE (EDC) only displays the File and Report drop-down menus:

1.        Ensure the correct HASP^� security key activation codes exists in \Data\Aloha.ini.

2.        Ensure the HASP security key activation code is authorized for EDC.

3.        Restart EDCSvr.exe (EDC Server).

Review the Debugging-Output-Files (debouts) on the terminals for further causes.� Refer to document AKBID1134 for more information on debouts.

============================================================================

See also:

AKBID1134 Debouts

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 10012 available show

Expired HASP Key

Expired HASP Key

============================================================================

AKBID10013

Created: 7 December 2000

Updated: 17 September 2003

Reviewed: 10 December 2003

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

This document is designed to provide a temporary list of resolutions for a specific issue related to the ALOHA^� application software.� The contents of this document will be added to the Aloha Knowledge Base (AKB) Answer Wizards when they are operational, and this document will be deleted.

If the Aloha application software Front-of-House (FOH) functions for more than 21-days without communicating with a HASP^� key either locally or via CTLSVR.EXE (Control Server), the FOH displays the following message when a user tries to login:

'System redundancy has been exceeded! Restore your fileserver to continue or contact your service provider for assistance.'

To remove this message if the system is functioning normally in regards to the file server being online and functional, perform the following:

1.        Verify if the HASP security key is attached to the file server, as defined by the SERVER system environment variable on the file server.

2.        Verify if the HASP security key is attached to the file server, as defined by the SERVER system environment variable on each terminal.

3.        Verify the computer defined as the file server by the SERVER system environment variable is actually functioning as the file server.

4.        Verify that Control Server is enabled on the file server.

5.        Verify if the lana number for the network protocol assigned to the Aloha application software is properly configured (refer to document AKBID1018) on the file server.�

6.        Verify if the lana number for the network protocol assigned to the Aloha application software is properly configured (refer to document AKBID1018) on the master terminal.

7.        Verify the user currently logged in to the file server has read/write access to the Microsoft^� Windows^� registry.

8.        Verify the user currently logged in to each terminal has read/write access to the Windows registry.

9.        Check if the REMOTE variable is included in the Control Server command line in the Windows registry (refer to document AKBID3009).�

10.     If the site is not running both the FOH and the Back-of-House (BOH) on the same computer, verify that the NONET variable is not included in the Control Server command line in the Windows registry (refer to document AKBID3009).�

11.     Verify that the shortcuts to CTL.EXE (Control) or ALOHAMGR.EXE (Aloha Manager) on the file server do not include the REMOTE variable.�

If the file server is not functioning properly and fault tolerance capabilities are enabled to compensate for it (the file server is 'down'), attach the HASP key to the terminal acting as the temporary file server and restart the terminal.� Ensure that you install the HASP drivers on the FOH terminal (refer to document AKBID3016).

If you have a terminal that is never connected to file server over the network, you can upgrade your HASP security key to support this if you are using Aloha version 5.2.8.83 or higher.�� Contact your Aloha Technologies Sales representative for more information on a remote terminal upgrade for your HASP security key.� Ensure that you install the HASP drivers on the remote terminal (refer to document AKBID3016).

Review the Debugging-Output-Files (debouts) on the terminals for further causes.� Refer to document AKBID1134 for more information on debouts.

============================================================================

See also:

AKBID1018 Network Lana Numbers

AKBID1112 HASP Key Troubleshooting

AKBID1134 Debouts

AKBID1163 FOH HASP Key Expiration

AKBID3009 CTLSVR.EXE Registry Variables

AKBID3016 HASP Driver Removal and Installation

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 10013

style='mso-spacerun:yes'>� 2003

Events do not Fire Automatically

Events do not Fire Automatically

============================================================================

AKBID10014

Created: 2 January 2001

Updated: 3 June 2003

Reviewed: 12 September 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

This document is designed to provide a temporary list of resolutions for a specific issue related to the ALOHA^� application software.� The contents of this document will be added to the Aloha Knowledge Base (AKB) Answer Wizards when they are operational, and this document will be deleted.

If Aloha application software events do not automatically fire in the Front-of-House (FOH), perform the following:

Iber.exe and IberQS.exe execute FOH events.� Ctlsvr.exe (Control Server) does not manage FOH events.

1.        Verify if the Date-of-Business (DOB) setting is not out of synchronization with the system date by more than one day.

2.        Check for corruption in the EVENTS.CFG file (refer to document AKBID1134).

3.        Verify the events configuration to ensure another event is not overriding the event in question.� The event hierarchy is 'Special overrides Monthly overrides Weekly overrides Daily'.

4.        View the contents of the EVENTS.CFG in the DATA folder to verify the contents.

5.        Verify that you do not have multiple event configuration files that are overwriting each other (refer to document AKBID3300).

6.        If you are rerouting menus, refer to document AKBID3196 to ensure you are following the correct event type hierarchy.

7.        Enable event-debugging output to the Debugging-Output-Files (debouts) in Aloha Manager/Maintenance/Store Settings/System/Aloha Settings, and review the debouts on the terminals for further causes.� Refer to document AKBID1134 for more information on debouts.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1134 Debouts

AKBID3155 EVENTS.CFG Corruption

AKBID3196 Event-level Menu Assignment Hierarchy

AKBID3300 Aloha FOH Reads Multiple Event Configuration Files

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 10014

style='mso-spacerun:yes'>� 2003

FOH Sticks on 'Terminal Up' or Blank Message

FOH Sticks on 'Terminal Up' or Blank Message

============================================================================

AKBID10015

Created: 30 March 2001

Updated: 2 April 2001

Reviewed: 12 December 2003

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

============================================================================

This document is designed to provide a temporary list of resolutions for a specific issue related to the ALOHA^� application software.� The contents of this document will be added to the Aloha Knowledge Base (AKB) Answer Wizards when they are operational, and this document will be deleted.

Perform the following if the Aloha application software Front-of-House hangs on a 'Terminal Up' or blank error in the lower left corner:

1.        Windows networking is not properly configured with a valid network adapter and/or protocol.� One of the following must be configured, active, and assigned to lana zero:

A.      The TCP/IP protocol assigned to a static IP address

B.       The TCP/IP protocol assigned to an IP address via DHCP

C.       The NetBEUI protocol

2.        If the user is trying to run both the FOH and the Back-of-House (BOH) together on the same Microsoft^� Windows^� 95, Windows 98, or Windows Millennium Edition (Me) PC, add the NONET (/NONET) variable to the CTLSVR.EXE (Control Server) command line variables in the registry (refer to document AKBID3009).

Refer to document AKBID1099 for more information.

Review the Debugging-Output-Files (debouts) on the terminals for further causes.� Refer to document AKBID1134 for more information on debouts.

============================================================================

See also:

AKBID1134 Debouts

AKBID3009 CTLSVR.EXE Registry Variables

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 10015 hang stick sticks stuck

style='mso-spacerun:yes'>� 2003

BOH Passwords are Deleted After EOD

BOH Passwords are Deleted After EOD

============================================================================

AKBID10016

Created: 30 March 2001

Updated: 30 March 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

This document is designed to provide a temporary list of resolutions for a specific issue related to the ALOHA^� application software.� The contents of this document will be added to the Aloha Knowledge Base (AKB) Answer Wizards when they are operational, and this document will be deleted.

If Back-of-House (BOH) passwords are continually deleted after each End-of-Day (EOD) process, verify that a BOHSEC files does not exist along with a 'File Formerly Known as BOHSEC' file in the DATA folder.� If it does, delete all instances of the BOHSEC file and restart file server.

Review the Debugging-Output-Files (debouts) on the terminals for further causes.� Refer to document AKBID1134 for more information on debouts.

============================================================================

See also:

AKBID1134 Debouts

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 10016 delete erase erased

Employee Locked on Another Terminal

Employee Locked on Another Terminal

============================================================================

AKBID10017

Created: 30 March 2001

Updated: 30 March 2001

Reviewed: 16 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

This document is designed to provide a temporary list of resolutions for a specific issue related to the ALOHA^� application software.� The contents of this document will be added to the Aloha Knowledge Base (AKB) Answer Wizards when they are operational, and this document will be deleted.

Errors stating that an employee is locked on another Front-of-House (FOH) terminal are typically caused by one of the following:

1.        The employee is logged in to another terminal.

2.        A manager is editing the employee or the employee's open checks on another FOH terminal.

3.        The ALOHA^� application software file server is out of disk space, and the .LCK files (refer to document AKBID3012) are not being deleted.

4.        Faulty power or network issues.

In the case low disk space, refer to document AKBID1014 to recover disk space.� Once you have recovered the disk space, stop the FOH, delete *.LCK from the DATA folder, and restart the FOH.

Review the Debugging-Output-Files (debouts) on the terminals for further causes.� Refer to document AKBID1134 for more information on debouts.

============================================================================

See also:

AKBID1014 Full Hard Drive Recovery

AKBID1134 Debouts

AKBID3012 LCK Files

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 10017

Failed to Register Station Name, 0x34' Error

'Failed to Register Station Name, 0x34' Error

============================================================================

AKBID10018

Created: 2 April 2001

Updated: 25 February 2004

Reviewed: 25 February 2004

Microsoft^� Windows^� Versions: Windows NT^�, Windows 2000, Windows XP, Windows Server 2003

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

============================================================================

This document is designed to provide a temporary list of resolutions for a specific issue related to the ALOHA^� application software.� The contents of this document will be added to the Aloha Knowledge Base (AKB) Answer Wizards when they are operational, and this document will be deleted.

Perform the following if the Aloha application software Front-of-House (FOH) or Back-of-House (BOH) displays an error stating 'Failed to register station name, 0x34':

Ensure that the network binding used by the Aloha application software is assigned to lana number zero.� Refer to document AKBID1018 for more information.

If you are using the TCP/IP protocol, ensure that you have a valid IP addresses assigned to the network binding used by the Aloha application software.

If you are using Windows 2000, Windows XP, or Windows Server 2003, verify that you have disabled DHCP Media Sense.

Refer to document AKBID1099 for more information.

Review the Debugging-Output-Files (debouts) on the terminals for further causes.� Refer to document AKBID1134 for more information on debouts.

============================================================================

See also:

AKBID1134 Debouts

AKBID1018 Network Lana Numbers

AKBID1099 Network Troubleshooting

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 10018 hang stick sticks stuck

FOH Terminals Ask for Windows User Name and Password

FOH Terminals Ask for Windows User Name and Password

============================================================================

AKBID10019

Created: 9 April 2001

Updated: 7 April 2003

Reviewed: 19 December 2003

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

This document is designed to provide a temporary list of resolutions for a specific issue related to the ALOHA^� application software.� The contents of this document will be added to the Aloha Knowledge Base (AKB) Answer Wizards when they are operational, and this document will be deleted.

If Microsoft^� Windows^� on the Front-of-House (FOH) terminals requests a user name and password following a system refresh of the End-of-Day (EOD) process, perform the following:

If the terminal is using Windows NT^�, Windows 2000, or Windows XP, refer to document AKBID1005 to enable auto login.

If the terminal is using Windows 95, Windows 98 or Windows Millennium Edition (Me), set the Primary Network Logon in the Windows network properties to Windows Logon and clear the password (DEL C:\WINDOWS\*.PWL and restart Windows).

If the terminal is using Windows 95, Windows 98 or Windows Millennium Edition (Me), disable user profiles if they are enabled.� To disable user profiles, double-click the Passwords icon in the Control Panel, select the User Profiles tab, select 'All users of this PC use the same preferences and desktop' and click OK.� Clear the passwords (DEL C:\WINDOWS\*.PWL) and restart Windows.

If the terminal is using Windows 95, Windows 98 or Windows Me and you are required to configure it with either a login password, user profiles or set the Primary Network Logon to 'Client for Microsoft Networks', use the Microsoft Windows TweakUI utility to automatically enter the user name and password.� Download TweakUI from the Aloha Technologies FTP site as TWEAKUI.ZIP.

============================================================================

See also:

AKBID1005 Microsoft Windows Automatic Log In

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 10019 automatic in log logon on

style='mso-spacerun:yes'>� 2003

Aloha Receipt and Kitchen Printer Settings and Pin-outs

Aloha Receipt and Kitchen Printer Settings and Pin-outs

============================================================================

AKBID1002

Created: 9 December 1999

Updated: 16 April 2004

Reviewed: 16 April 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: DIP Switch and Cable Settings for the Aloha Application Software Printers

============================================================================

Summary

The majority of printer problems associated with the ALOHA^� application software consists of two things: dual in-line package (DIP) switches and cable pin-outs.� This document lists general configuration settings, DIP switch settings for approved printers, and the cable pin-outs used with the Aloha application software.

Some switches might vary depending on the auto-cutter option on the printer.� This might cause mechanical errors if set incorrectly.� Consult the printer's user manual for more information.

Some printers in this document might not be officially approved for use with the Aloha application software.� Refer to document AKBID1048 for a list of approved hardware.

Some printers might not be compatible with all versions of the Aloha application software.� Contact Aloha Technologies to verify version compatibility.

Unless otherwise stated, the printer settings and cable pin-outs listed in this document only apply to printers driven by native Aloha application software drivers, not OLE for Retail Point-of-Sale (OPOS) drivers or Windows-based drivers.� Refer to document AKID1074 for more information on OPOS drivers or AKBID1026 for more information on Windows-based drivers.

Information

LPT Port Settings

You need to set your parallel ports to Standard or EPP in the BIOS if you are using parallel printers.� If parallel printers continue to print slowly, consider using the printer's OPOS drivers (refer to document AKBID1074).

If you are using a parallel receipt or chit printer, then you must ensure that the LPT port is not set to ECP mode in either the system BIOS or in the Windows hardware configuration.� Configuring the LPT port to ECP mode can result in system lock-ups.

FIFO Buffers

Microsoft^� Windows^� 95, Windows 98, Windows Millennium Edition (Me), Windows 2000, and Windows XP offer the option to enable First-In-First-Out (FIFO) buffers on the terminal's COM ports.� These buffers tend to interfere with printers using Xon/Xoff flow control.� Aloha Technologies disables these buffers on all COM ports on all terminals by default, regardless of the printer type.� (In the event of a printer or COM port failure, a replacement printer using Xon/Xoff flow control might be temporarily connected to the port in the future.)

To access the FIFO buffer settings, open Windows Device Manager via the System Control Panel applet.� Click the plus sign (+) next to Ports to expand it.� Select each port one at a time, and select Properties/Port Settings/Advanced.� Clear the Use FIFO buffer.� Perform this on each COM port.� The LPT port does not have this option.

Printer Buffers

In some cases, a printer might not function properly using the printer's smaller buffer size, but the printer will function properly if you increase the buffer size to the higher setting.� In this case, Aloha Technologies has found that although the printer functions properly most of the time, it is still prone to sporadic problems that are not easily diagnosed because of their randomness.� In other words, the problems still exist, but they are just masked a little better.

Since the Aloha application software should not encounter errors printing to printers using the smaller buffer size (it is actually preferred over the larger buffer), you should rectify the problem when encountering printer problems with the smaller buffer size rather than patching them with a larger buffer size.� Consistent problems with the smaller buffer size are much easier to troubleshoot than sporadic problems with the larger buffer size.

In most cases, the problems are caused by printer cables, FIFO buffers, or incorrect data flow settings.

OPOS Printers

The information in this document does not apply to OPOS printers since the Aloha application software does not directly communicate with OPOS printers.� Instead, the Aloha application software communicates with the OPOS drivers (supplied by the printer manufacturer), and the OPOS drivers communicate with the printer.� For this reason, the printer manufacturer should provide you with the cable pin-outs and DIP switches for use with their OPOS drivers.� In general, they use the printer's default DIP switch configuration and the cable pin-outs described in document AKBID1074, but this is not a hard rule.

Refer to document AKBID1074 for more information on OPOS.

CBM 354x Serial

You must have a Star ROM in CBM 354x printers.� The descriptive ID on the bottom of the printer identifies a printer with the Star ROM.� If the ID includes a 'S', the printer has a Star ROM.� If the ID includes a 'R', it does not have a Star ROM.

Define the printer as a Star 300 in the Aloha application software.�

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

SW9

SW10

Set 1

Off

On

On

On

On

On

On

On

On

On

Set 2

On

Off

Off

On

On

On

Off

On

-

-

CBM CBM-710/720/730, and CBM-750 Serial (40 column version)

Define the printer as a Citizen CBM-750 in the Aloha application software.�

(SW1 on Set 1 sets the auto-cutter)

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

On

Off

Off

Off

Off

Off

Off

Off

Set 2

Off

Off

On

Off

On

On

On

Off

Serial DB9 to CBM-7xx DB25

DB9

1

2

3

5

6

9

DB25

12

2

3

7

20

11

Serial DB25 to CBM-7xx DB25

DB25

1

2

3

6

7

8

22

DB25

1

3

2

20

7

12

11

CBM CBM-1000 Serial

CBM-1000 printers require firmware version MPV1.01 or higher.

Define the printer as an Epson TM-80 in the Aloha application software.

(SW1 on Set 1 sets the auto-cutter)

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

On

Off

Off

Off

Off

Off

On

Off

Set 2

Off

Off

Off

Off

Off

Off

Off

Off

Set 3

Off

On

On

On

On

Off

Off

Off

Set 4

Off

On

Off

Off

-

-

-

-

CBM CBM-1000 Type II Serial

Define the printer as an Epson TM-80 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

SW9

SW10

Set 1

On

Off

Off

Off

Off

On

On

Off

-

-

Set 2

Off

Off

Off

Off

Off

Off

Off

Off

Off

Off

Set 3

Off

On

On

On

On

Off

Off

Off

-

-

CBM iDP3240 Serial

Define the printer as an Epson TM-80 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

On

Off

Off

Off

Off

On

On

Off

Set 2

Off

Off

Off

Off

Off

Off

Off

Off

Set 3

Off

On

On

On

-

-

-

-

Set 4

Off

On

Off

Off

-

-

-

-

Eltron/Zebra Technologies LP2742

The Eltron^� or Zebra Technologies LP2742 uses a straight-through serial cable.

Epson TM-H6000 Serial

Define the printer as an Epson H6000 in the Aloha application software.

Although the Aloha application software supports both the slip printer and receipt printer in TableService, QuickService only supports the receipt printer.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

Off

On

Off

On

On

Off

On

Set 2

Off

Off

Off

Off

Off

Off

Off

Off

Epson TM-T80 Serial

Define the printer as an Epson TM-80 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

SW9

SW10

Set 1

Off

On

On

On

On

On

Off

Off

Off

Off

Epson TM-T85 Serial

Define the printer as an Epson TM-80 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

On

On

Off

On

On

On

Off

Set 2

Off

Off

Off

Off

Off

Off

Off

Off

Epson TM-T88 Parallel

Define the printer as an Epson TM-80 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

On

On

Off

On

On

On

Off

Set 2

Off

Off

Off

Off

Off

Off

Off

Off

Epson TM-T88 Serial

Define the printer as an Epson TM-80 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

On

On

Off

On

On

On

Off

Set 2

Off

Off

Off

Off

Off

Off

Off

Off

Epson TM-U200 Serial

In Aloha versions 5.025 and lower, define the printer as an Epson 300 in the Aloha application software.� In Aloha versions 5.026 and higher, define the printer as an Epson U200 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

On

On

Off

On

On

Off

Off

Set 2

Off

On¹

Off

On

-

-

-

-

¹Set this switch to the Off position if the printer lacks an auto-cutter.

Epson TM-U200 Parallel

In Aloha versions 5.025 and lower, define the printer as an Epson 300 in the Aloha application software.� In Aloha versions 5.026 and higher, define the printer as an Epson U200 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

On

Off

Off

Off

Off

Off

Off

Set 2

Off

On¹

Off

On

-

-

-

-

¹Set this switch to the Off position if the printer lacks an auto-cutter.

Epson TM-U220 Serial

Define the printer as an Epson U200 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

On¹

On

Off

On

On

Off

Off

Set 2

Off

On²

Off

Off

Off

Off

Off

Off

¹Set this switch to the Off position if you experience problems with misaligned text or missing characters

²Set this switch to the Off position if the printer lacks an auto-cutter.

Epson TM-295 Serial

Define the printer as an Epson TM-295 in the Aloha application software.

The Aloha application software does not support 'line find' on slip printers in versions 5.0x and lower.� For example, when you insert a hard check into the printer, the Aloha application software does not search for the next unused line, but instead, the Aloha application software starts printing as if printing to a blank slip.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

SW9

SW10

Set 1

On

On

Off

Off

On

On

Off

Off

Off

Off

Epson TM-U300 Serial

Define the printer as an Epson 300 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

SW9

SW10

Set 1

Off

Off

On

Off

On

On

Off

Off

Off

On

IBM SureMark 4610 Serial

Define the printer as an OPOS printer in the Aloha application software.� This configuration requires Aloha version 5.026 or higher and installation of IBM OPOS drivers.� Refer to documents AKBID1074 and AKBID1172 for more information.

Refer to document AKBID3248 for more information on cable pin-outs if you are using with printer with an IBM SurePOS 500-xx2.

SW1

SW2

SW3

SW4

Set 1

Off

Off

Off

Off

Ithaca (TransAct) iTherm 280 Serial

Define the printer as an Epson 80 in the Aloha application software.� Adjust the printer configuration to 9600/8/E/1/XON-XOFF, Epson TM-T88 emulation mode.

Ithaca (TransAct) Model 82 Plus Serial

Define the printer as an Epson TM-80 in the Aloha application software.� Adjust the configuration to 9600/8/E/1/XON-XOFF, TM-T88 Emulation Mode.� Use the default configuration mode with the default parity changed to even parity.� If you are installing Ithaca Series 80 printers, we recommend you order the Ithaca Series 80 Programmer's Guide from Ithaca as outlined in the printer's Operator's Guide.� It contains instructions on adjusting the printer's configuration settings.

Ithaca (TransAct) Model 82 Plus Parallel

Define the printer as a Epson TM-80 in the Aloha application software.� Use the default configuration mode.� If you are installing Ithaca Series 80 printers, we recommend you order the Ithaca Series 80 Programmer's Guide from Ithaca as outlined in the printer's Operator's Guide.� It contains instructions on adjusting the printer's configuration settings.

Ithaca (TransAct) Series 1000 Serial

Define the printer as an Epson U200 in the Aloha application software or use OPOS drivers.� If you are configuring the printer as an Epson TM-U200 in the Aloha application software, adjust the configuration to 9600/8/E/1/XON-XOFF, Epson Emulation Mode.� If you are configuring the printer as an OPOS printer in the Aloha application software, use the manufacturer's recommended settings.

Ithaca (TransAct) POSjet 1000 Serial

Define the printer as an Epson U200 in the Aloha application software.� Adjust the printer configuration to 9600/8/E/1/XON-XOFF, Epson Emulation Mode.

Nanoptix C21-BNSAB/C21-BNSBB Spill Proof Thermal Printer

Define the printer as an Epson TM-80 in the Aloha application software.

Configure the printer to 9600/8/E/1/XON-XOFF.� You must use firmware Aloha V2.42H-61AU8BHe or higher.

Use a straight-thru cable pin-out.

NCR 7193 Serial

Define the printer as an Epson TM-80 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

Set 1

Off

On

Off

Off

On

Off

NCR 7194 Serial

Define the printer as an Epson TM-80 in the Aloha application software and use the printer's default settings.

Olivetti OST12 Serial

Define the printer as an Epson U200 in the Aloha application software.� Adjust the configuration to 9600/8/E/1/XON-XOFF, ESC/POS Mode, and set the 'Chars / inchs' to 'A=15 B=20 cpi' in order to avoid some larger text wrapping to a second line.

Partner Tech Corp RP-200

Define the printer as an Epson TM-80 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

SW9

SW10

Set 1

Off

Off

Off

Off

On

On

Off

On

Off

On

Set 2

Off

Off

Off

Off

-

-

-

-

-

-

Samsung SRP-270

Define the printer as an Epson 300 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

Off

On

Off

Off

Off

Off

Off

Set 2

Off

Off

On

Off

On

On

Off

Off

Samsung SRP-270C

Define the printer as an Epson U200 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

Off

On

Off

On

On

Off

Off

Set 2

Off

Off

On

Off

Off

Off

Off

Off

Samsung SRP-350

Define the printer as an Epson TM-80 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

Off

On

Off

On

On

On

Off

Set 2

Off

Off

Off

Off

Off

Off

Off

Off

Samsung SRP-500C Serial and Parallel

Define the printer as an Epson U200 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

Off

Off

On

Off

Off

Off

Off

Off

Set 2

Off

Off

Off

Off

On

On

Off

Off

Star 8340 Serial

Define the printer as a Star 8340 in the Aloha application software.

If printed receipt characters appear distorted because the last two characters appear on the next line, set the printer type to Star 300 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

On

On

On

On

On

On

Off

Off

Set 2

On

On

On

On

-

-

-

-

Star 300/312 Serial

Define the printer as a Star 300 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

On

On

On

On

On

On

On

On

Set 2

On

On

On

On

On

On

On

On

Set 3

On

On

On

On

On

On

Off

Off

Set 4

On

On

On

On

On

On

On

On

Star 300/312 Parallel

Define the printer as a Star 300 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

On

On

On

On

On

On

On

On

Set 2

On

On

On

On

On

On

On

On

Star SP512MD

Define the printer as a Star 300 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

SW9

SW10

Set 1

On

On

On

On

On

On

On

Off

Off

On

Star SP2000 Serial

Define the printer as a Star 300 in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

On

Off

On

Off¹

On

On

On

On

Set 2

On

On

On

Off

Off

On

Off

Off

¹Set this switch to the On position if the printer lacks an auto-cutter.

Star TSP200 Serial

Define the printer as a Star TSP-200 Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

On

On

On

Off

Off

Off

On

On

Set 2

On

On

Off

Off

-

-

-

-

Star TSP400 Serial

Define the printer as a Star TSP-400 or Star TSP-400 with Cutter in the Aloha application software.

SW1

SW2

SW3

SW4

SW5

SW6

SW7

SW8

Set 1

On

On

On

On

Off

Off

On

On

Pin-outs for Standard Printer Cables

Serial DB9 to Printer DB25

DB9

2

3

5

8

DB25

2

3

7

20

Serial DB9 to Printer DB9

DB9

2

3

5

8

DB9

3

2

5

4

Serial DB25 to Printer DB25

DB25

2

3

5

7

DB25

3

2

20

7

Serial DB25 to Printer DB9

DB25

2

3

5

7

DB9

2

3

4

5

RJ45 to RS232 Adapter Pin-outs for Standard Printer Cables

Serial DB9 to Printer DB25

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB9

1

2

3

4

5

6

7

8

DB25

Unused

2

3

Unused

7

Unused

Unused

20

Serial DB9 to Printer DB9

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB9

1

2

3

4

5

6

7

8

DB9

Unused

3

2

Unused

5

Unused

Unused

4

Serial DB25 to Printer DB25

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB25

1

2

3

4

5

6

7

8

DB25

Unused

3

2

Unused

20

Unused

7

Unused

Serial DB25 to Printer DB9

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB25

1

2

3

4

5

6

7

8

DB9

Unused

2

3

Unused

4

Unused

5

Unused

Extended Information

Any printer that emulates one of the listed printers will work in the Aloha application software.� All serial printers connected to the Aloha application software use the listed cable pin-out.

If you have a printer that emulates an approved printer, then set the DIP switches to the listed preferences.� For Epson emulation, set the printer to Epson emulation, 9600 baud, even parity, 8 data bits, 1 stop bit, and Xon/Xoff flow control.� For Star emulation, set the printer to Star emulation, 9600 baud, even parity, 8 data bits, 1 stop bit, and DTR/DSR flow control.

Caveats

Some switches might vary depending on the auto-cutter option on the printer.� This might cause mechanical errors if set incorrectly.� Consult the printer's user manual for more information.

Some printers in this document might not be officially approved for use with the Aloha application software.� Refer to document AKBID1048 for a list of approved hardware.

Some printers might not be compatible with all versions of the Aloha application software.� Contact Aloha Technologies to verify version compatibility.

Unless otherwise stated, the printer settings and cable pin-outs listed in this document only apply to printers driven by native Aloha application software drivers, not OLE for Retail Point-of-Sale (OPOS) drivers or Windows-based drivers.� Refer to document AKID1074 for more information on OPOS drivers or AKBID1026 for more information on Windows-based drivers.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1003 Aloha Network Cable Pin-outs

AKBID1004 Serial Pin Assignments

AKBID1026 Using Windows-based Printers with Aloha

AKBID1048 Aloha Application Software Hardware and OS Specifications

AKBID1074 OPOS

AKBID1156 Using Windows Printers Between Stores in SuperSites

AKBID1172 IBM SurePOS 500

AKBID3154 Epson Printer Enunciators

AKBID3248 IBM SurePOS 500-xx2 Serial Port Pin-outs and Printer Cables

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1000 1002 200 220 2000 232 2742 270A 270C 270D 295 300 312 3240 3541 3542 3551 3552 400 6000 80 85 88 citizen db-9 db-25 mark partnertech pinout pinouts rj-45 rs-232 sp500 srp270 srp500 sure tmt tmu tsp u200 u220 x-off x-on

BackOffice Interface Does not Respond to FOH

BackOffice Interface Does not Respond to FOH

============================================================================

AKBID10020

Created: 20 April 2001

Updated: 4 February 2004

Reviewed: 4 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, BackOffice

Aloha POS Versions: 3.65x � 5.3.x

============================================================================

This document is designed to provide a temporary list of resolutions for a specific issue related to the ALOHA^� application software.� The contents of this document will be added to the Aloha Knowledge Base (AKB) Answer Wizards when they are operational, and this document will be deleted.

If the Aloha application software Front-of-House (FOH) displays an error stating 'NO RESPONSE.� DELIVERY INTERFACE PROBABLY NEEDS TO BE STARTED' when you are assigning a customer to a check, ensure the following are true:

1.        The Aloha Interface is started on the file server.

2.        The interface Message File Path is set to the \DELIVERY\MESSAGES\ (note the additional back-slash at the end) folder inside the Aloha application software folder.

3.        The \DELIVERY\MESSAGES folder exists inside the Aloha application software folder.

4.        The SERVER environment variable is correctly set in the FOH (refer to document AKBID1010).

5.        The FOH terminals can access the file server over the network.

6.        The BACKOFFICEDIR environment variable is not set or is not set incorrectly (refer to document AKBID3128).

Review the Debugging-Output-Files (debouts) on the terminals for further causes.� Refer to document AKBID1134 for more information on debouts.

============================================================================

See also:

AKBID1010 Aloha Application Software System Environment Variables

AKBID1134 Debouts

AKBID3128 SuperSite BackOffice Messages Folder

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 10020

Invalid DATA Path Causes Aloha Manager Security Setup Failure

Invalid DATA Path Causes Aloha Manager Security Setup Failure

============================================================================

AKBID10021

Created: 3 May 2001

Updated: 3 May 2001

Reviewed: 18 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

This document is designed to provide a temporary list of resolutions for a specific issue related to the ALOHA^� application software.� The contents of this document will be added to the Aloha Knowledge Base (AKB) Answer Wizards when they are operational, and this document will be deleted.

If ALOHAMGR.EXE (Aloha Manager) displays an error stating 'Security setup failed.� Aloha Manager cannot log users in without a valid path to an Aloha data directory', perform the following:

1.        Verify if the IBERDIR variable in the system environment variables is correct.

2.        Verify if an IBERDIR variable exists on the Aloha Manager shortcut command line (not required) and if it is correct.

3.        Update the NEWDATA and DATA configuration data using DBCONFIG.EXE.� Refer to document AKBID1160 for upgrade instructions.

Review the Debugging-Output-Files (debouts) on the terminals for further causes.� Refer to document AKBID1134 for more information on debouts.

============================================================================

See also:

AKBID1134 Debouts

AKBID1160 Manually Upgrading Configuration Files in Aloha Manager

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 10021

Aloha Network Cable Pin-outs

Aloha Network Cable Pin-outs

============================================================================

AKBID1003

Created: 12 December 1999

Updated: 6 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: Aloha Network Cable Pin-outs (regular and terminal-to-terminal)

============================================================================

Summary

This document outlines the network cable pin-outs used by Aloha Technologies with the ALOHA^� application software for both a regular cable (through a hub or with a printer) and terminal-to-terminal (without a hub).

Information

Aloha Technologies recommends you add proper labeling to terminal-to-terminal cables so they are not mistaken for regular network cables.

Regular

Pin #

Term 1

Hub

1

White/Orange

White/Orange

2

Orange

Orange

3

White/Green

White/Green

4

Blue

Blue

5

White/Blue

White/Blue

6

Green

Green

7

White/Brown

White/Brown

8

Brown

Brown

Terminal to Terminal

Pin #

Term 1

Term 2

1

White/Orange

White/Green

2

Orange

Green

3

White/Green

White/Orange

4

Blue

Blue

5

White/Blue

White/Blue

6

Green

Orange

7

White/Brown

White/Brown

8

Brown

Brown

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

AKBID1002 Aloha Receipt & Kitchen Printer Settings

AKBID1004 Serial Pin Assignments

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1003 pinout pinouts

Serial Pin Assignments

Serial Pin Assignments

============================================================================

AKBID1004

Created: 12 December 1999

Updated: 6 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: RS232 Serial Pin Assignments

============================================================================

Summary

This document outlines the pin assignments for common 9-pin (DB9) and 25-pin (DB25) computer serial ports on ALOHA^� application software terminals.

Information

9-Pin Serial Ports

Pin

Function

1

Carrier Detect (CD)

2

Receive Data (RXD)

3

Transmit Data (TXD)

4

Data Terminal Ready (DTR)

5

Signal Ground (GND)

6

Data Set Ready (DSR)

7

Request To Send (RTS)

8

Clear To Send (CTS)

9

Ring Indicator (RI)

25-Pin Serial Ports

Pin

Function

2

Transmit Data (TXD)

3

Receive Data (RXD)

4

Request To Send (RTS)

5

Clear To Send (CTS)

6

Data Set Ready (DSR)

7

Signal Ground (GND)

8

Carrier Detect (CD)

20

Data Terminal Ready (DTR)

22

Ring Indicator (RI)

Extended Information

Straight Through RJ45-to-DB9

RJ45 Wire

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB9 Pin

1

2

3

4

5

6

7

8

Straight Through RJ45-to-DB25

RJ45 Wire

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB25 Pin

8

3

2

20

7

6

4

5

Caveats

No information.

============================================================================

See also:

AKBID1002 Aloha Receipt and Kitchen Printer Settings

AKBID1003 Aloha Network Cable Pin-outs

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1004 db-9 db-25 pinout pinouts rj-45 thru

Microsoft Windows Automatic Log In

Microsoft Windows Automatic Log In

============================================================================

AKBID1005

Created: 15 December 1999

Updated: 17 December 2003

Reviewed: 17 December 2003

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x.x

Subject: Enabling Windows Automatic Log In

============================================================================

Summary

Microsoft^� Windows^� Automatic Log In benefits ALOHA^� application software users by providing quicker start-up time, enabling Windows to start without user interaction (thus, ensuring that all software in the Windows StartUp folder is promptly initiated), and does not require knowledge of the Windows password.� This is beneficial on Front-of-House (FOH) terminals during refreshes (or any other time you restart them) and on Back-of-House (BOH) file servers you must restart the system.

Consider any possible security issues before enabling automatic log in.

Not all of the information in this document conforms to the security requirements explained by the Visa U.S.A. Cardholder Information Security Program (CISP).� Aloha Technologies strongly recommends that you review the CISP in detail in order to verify that you meet all of the security requirements.� Refer to document AKBID1234 for more information.

Information

The incorrect use of the Windows Registry Editor can lead to serious, system-wide problems that might require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in single quotes.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

Before you configure automatic log in, you need to configure a default user.� Refer to document AKBID1006 for more information.

Windows 95, Windows 98 and Windows Me

If you are using Windows 95, Windows 98, or Windows Millennium Edition (Me), enable automatic log in using one of two methods:

Erase any passwords assigned to the default user so they have a blank password and set the Primary Network Logon in the network properties to Windows Logon.� If you want to erase all user login password, delete *.PWL from the Windows folder.� Disable user profiles if they are enabled.� To disable user profiles, double-click the Passwords icon in the Control Panel, select the User Profiles tab, select 'All users of this PC use the same preferences and desktop' and click OK.� Clear the passwords (DEL C:\WINDOWS\*.PWL) and restart Windows.� Refer to Microsoft Knowledge Base Article ID: Q156826 for more information.

If the terminal is using Windows 95, Windows 98 or Windows Me and you are required to configure it with either a login password, user profiles or set the Primary Network Logon to 'Client for Microsoft Networks', use the Microsoft Windows TweakUI utility to automatically enter the user name and password.� Download TweakUI from the Aloha Technologies FTP site as TWEAKUI.ZIP.

Windows NT, Windows 2000, Windows XP, and Windows Server 2003

If you are using Windows NT^�, Windows 2000, Windows XP, or Windows Server 2003, you can configure automatic log in using the Microsoft Windows TweakUI utility to automatically enter the user name and password.� Download TweakUI from the Aloha Technologies FTP site as TWEAKUI.ZIP.

An alternative to using TweakUI is to perform the following in order to manually edit the Windows registry and enable automatic log in:

The automatic log in feature may not function properly with a blank password.

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Current Version\Winlogon.

3.        Verify the AutoAdminLogon key exists in the folder.� If it does, double-click it and change the Value Data to '1'.� If it does not exist, select Edit/New/String Value and name the key 'AutoAdminLogon'.� Then double-click the entry and change the Value Data text box to '1'.

4.        Verify if the DefaultUserName key exists in the folder.� If it does, double-click it and change the Value Data to 'n' where n is the user name (case sensitive) that is used to log in to Windows.� If it does not exist, select Edit/New/String Value and name it 'DefaultUserName'.� Double-click the entry and change the Value Data to the user name (case sensitive) that is used to log in to Windows.

5.        Verify if the DefaultPassword key exists in the folder.� If it does, double-click it and change the Value Data to 'n' where n is the password (case sensitive) that is used to log in to Windows.� If it does not exist, select Edit/New/String Value and name the key 'DefaultPassword'.� Double-click the entry and change the Value Data to the password (case sensitive) that is used to log in to Windows.

6.        If you are using Windows XP or Windows 2000, verify the ForceAutoLogon key exists in the folder.� If it does, double-click it and change the Value Data to '1'.� If it does not exist, select Edit/New/String Value and name the key 'ForceAutoLogon'.� Then double-click the entry and change the Value Data text box to '1'.

7.        Select Registry/Exit to exit the Windows Registry Editor.

8.        Restart Windows.

If you are logged in to Windows and want to temporarily log in with another name, hold down the Shift key when you log out of Windows or, if you are starting Windows, press and hold down the Shift key when you see the Windows splash screen while starting Windows.

Perform the following to permanently disable automatic log in:

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Current Version\Winlogon.

3.        Locate the AutoAdminLogon key in the folder.� Double-click it and change the Value Data text box to '0'.

4.        To remove any possible security breeches, locate the DefaultPassword key in the folder.� Double-click it and clear the Value Data text box.

5.        Select Registry/Exit to exit the Windows Registry Editor.

6.        Restart Windows.

Extended Information

No information.

Caveats

Consider any possible security issues before enabling automatic log in.

The automatic log in feature may not function properly with a blank password.

============================================================================

See also:

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1234 Configuring Aloha to Conform with the Visa CISP Guidelines

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1005 auto autologin autologon login

style='mso-spacerun:yes'>� 2003

Configuring Windows User and Share Permissions for Aloha

Configuring Windows User and Share Permissions for Aloha

============================================================================

AKBID1006

Created: 16 December 1999

Updated: 17 December 2003

Reviewed: 17 December 2003

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 3.0x � 5.3.x

Subject: Configuring Windows Users and Shares for the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software requires you to configure Microsoft^� Windows^� shares and users on the Aloha file server, any ancillary file servers (EDC, BackOffice, Terminal Server, and so on), and each Front-of-House (FOH) order entry terminal to enable read and write access to one another's BOOTDRV share.� This document explains user privilege and share requirements required by the Aloha application software.

Not all of the information in this document conforms to the security requirements explained by the Visa U.S.A. Cardholder Information Security Program (CISP).� Aloha Technologies strongly recommends that you review the CISP in detail in order to verify that you meet all of the security requirements.� Refer to document AKBID1234 for more information.

Information

BOOTDRV Share Configuration

The Aloha application software requires a network share labeled BOOTDRV on each file server and each FOH terminal.� The BOOTDRV share must enable read and write access to each file server and each FOH terminal, so any one node in the Aloha installation has read and write privileges to the BOOTDRV share on any other node.� In the case of a SuperSite, the terminals within a store must have read and write permission to all of the terminals within the same store and all of the SuperSite�s file servers, but they do not require access to the BOOTDRV share on terminals in a different store.

You must apply the BOOTDRV share to the root folder or drive in which the Aloha folder resides.� For example, if the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.

If you are installing the Aloha application software using an Aloha installation application, then the installation will create the BOOTDRV share, but you might have to manually adjust the share permissions in order to grant the necessary access to your logins.

Local User Permissions

While you must assign local administrative privileges to logins used by the CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) services, administrative privileges are not required by the local system logins.� Aloha Technologies prefers to use logins with administrative privileges in order to provide easier technical support, but you can configure the system login with standard user privileges, provided you apply the additional rights explained in document AKBID1073.

Refer to document AKBID1073 for additional configuration requirements if you are not granting administrator privileges to local system logins.

Configuration Strategies

The strategy you employ to enable user-access to the BOOTDRV share depends on your security requirements and operating systems.� If security is not an issue because the site is not connected to a Wide-Area-Network (WAN), then you can share BOOTDRV to all users and enable to the Windows guest account to simplify the user configurations.� On the other hand, if security is an issue for the site, then you should consider using specific user names and passwords to limit access.� Regardless of the method you choose, the Aloha application software requires the file servers (which include the CTLSVR.EXE and EDCSVR.EXE service logins), and each FOH terminal to have read and write access to one another's BOOTDRV share.

The Aloha application software requires the file servers (which include the CTLSVR.EXE and EDCSVR.EXE service logins), and each FOH terminal to have read and write access to one another's BOOTDRV share.

For example, if you have a system with Windows NT^�, Windows 2000, Windows XP, or Windows Server 2003 on the file server and Windows 95, Windows 98, or Windows Millennium Edition (Me) on the FOH terminals and you only require minimal security, then you can just enable the Windows guest account on the file server, grant BOOTDRV access to everyone, and just log into the FOH terminals using a user name with no password.

If you are using the guest account for network access to the file server or terminals, ensure that the file server or any terminals using Windows 2000/XP/2003 is not configured to deny network access to the guest account.� To configure this, access the Local Security Policies in the Administrative Tools, select Local Policies/User Rights Assignment, double-click 'Deny access to this computer from the network' in, and remove the guest account.

If you are using a Windows NT/2000/XP/2003 throughout the entire system (on the file servers and all of the FOH terminals), consider using a common user name and password throughout the entire system.� Use this password for the automatic login for each file server, each terminal, and the Control Server and EDC Server service logins.� Ensure that you explicitly grant this user read and write access to the BOOTDRV share on each computer (do not depend on the 'Everyone' group included in the list by Windows).

If security is a major issue, then you can consider using a separate name and password on the file servers and each FOH terminal.� Ensure that you explicitly grant each user read and write access to the BOOTDRV share on each computer.� Also make ensure that the Control Server and EDC Server logins have read and write access to all of the FOH terminals (refer to document AKBID1197 for more information).� If you are using Windows 95/98/Me on the FOH terminals, you will have to configure a domain and enable user-level sharing on the FOH terminals in order to provide the most security.

The Aloha application software requires the file servers (which include the CTLSVR.EXE and EDCSVR.EXE service logins), and each FOH terminal to have read and write access to one another's BOOTDRV share.

Extended Information

No information.

Caveats

Not all of the information in this document conforms to the security requirements explained by the Visa U.S.A. Cardholder Information Security Program (CISP).� Aloha Technologies strongly recommends that you review the CISP in detail in order to verify that you meet all of the security requirements.� Refer to document AKBID1234 for more information.

Refer to document AKBID1073 for additional configuration requirements if you are not granting administrator privileges to local system logins.

If you are using the guest account for network access to the file server or terminals, ensure that the file server or any terminals using Windows 2000/XP/2003 is not configured to deny network access to the guest account.� To configure this, access the Local Security Policies in the Administrative Tools, select Local Policies/User Rights Assignment, double-click 'Deny access to this computer from the network' in, and remove the guest account.

The Aloha application software requires the file servers (which include the CTLSVR.EXE and EDCSVR.EXE service logins), and each FOH terminal to have read and write access to one another's BOOTDRV share.

============================================================================

See also:

AKBID1005 Microsoft Windows Automatic Login

AKBID1073 Using Aloha Without Enabling Administrator Permissions

AKBID1197 Assigning Logins to Aloha Services

AKBID1234 Configuring Aloha to Conform with the Visa CISP Guidelines

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1006 logon logons

style='mso-spacerun:yes'>� 2003

Default Aloha Windows Desktop Icons

Default Aloha Windows Desktop Icons

============================================================================

AKBID1007

Created: 16 December 1999

Updated: 3 December 2001

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

Subject: Aloha's Default Windows Desktop Icons on Customer Systems

============================================================================

Summary

When Aloha Technologies stages ALOHA^� application software file servers and terminals for a client, they always install certain application shortcuts on the desktop to assist the Aloha Customer Service Center (CSC) in supporting the client, and to simplify the client's access to these applications.� Extra desktop shortcuts are removed to help alleviate the use of unneeded applications, reduce confusion, and create a cleaner appearance.

Information

When creating new shortcuts, Aloha Technologies assigns them proper names instead of the default name given by the Microsoft^� Windows^� operating system.� For example, when you create a shortcut for ALOHAMGR.EXE (Aloha Manager), the new shortcut is renamed to 'Aloha Manager' instead of the default name of 'Shortcut to Alohamgr.exe'.� This creates a user-friendly desktop for the novice user.

You should add desktop shortcuts in Windows NT^�, Windows 2000, or Windows XP to the All Users desktop.� This ensures that the shortcuts exist regardless of the user who is logged on.� The easiest way to access the All Users desktop is to right-click the Windows Start button and select Explore All Users.

Windows 95, Windows 98, or Windows Me File Server

In order to access these settings on an existing icon, right-click the icon on the desktop, and select Properties.� Select the Shortcut tab.� To create new icons, right-click the desktop, select New, and select Shortcut.

Desktop Name

Target

Start in

Notes

My Computer

N/A

N/A

Windows default

Network Neighborhood

N/A

N/A

Windows default

Recycle Bin

N/A

N/A

Windows default

Explorer

EXPLORER.EXE

default

Command Prompt

COMMAND.COM

C:\ALOHA

Adjust the 'Start in' setting to reflect the Aloha folder.

Aloha POS

C:\ALOHA\IBER.BAT

default

Use only if this computer is a server/terminal.� Adjust the 'Target' setting to reflect the Aloha folder.

Aloha Manager

C:\ALOHA\BIN\ALOHAMGR.EXE

default

Adjust the 'Target' setting to reflect the Aloha folder.

Aloha Credit Cards

C:\ALOHA\BIN\EDC.EXE

default

If used, adjust the 'Target' setting to reflect the Aloha folder.

Aloha Labor Scheduler

C:\ALOHA\BACKOFFICE\SCHEDULE\ESP.EXE

default

Use if Labor Scheduler is installed.� Adjust the 'Target' setting to reflect the BackOffice folder.

Symantec^� pcANYWHERE^�

MODEM.BHF in pcANYWHERE's DATA folder.

Default

Use only if pcANYWHERE is installed.

Windows 95, Windows 98, or Windows Me Terminal

In order to access these settings on an existing icon, right-click the icon on the desktop, and select Properties.� Select the Shortcut tab.� To create new icons, right-click the desktop, select New, and select Shortcut.

Desktop Name

Target

Start in

Notes

My Computer

N/A

N/A

Windows default

Network Neighborhood

N/A

N/A

Windows default

Recycle Bin

N/A

N/A

Windows default

Aloha POS

C:\ALOHA\BIN\IBER.EXE

default

Adjust the 'Target' setting to reflect the Aloha folder.

Windows NT, Windows 2000 or Windows XP File Server

In order to access these settings on an existing icon, right-click the icon on the desktop, and select Properties.� Select the Shortcut tab.� To create new icons, right-click the desktop, select New, and select Shortcut.

Desktop Name

Target

Start in

Notes

My Computer

N/A

N/A

Windows default

Network Neighborhood

N/A

N/A

Windows default

Recycle Bin

N/A

N/A

Windows default

Explorer

EXPLORER.EXE

default

Command Prompt

CMD.EXE

C:\ALOHA

Adjust the 'Start in' setting to reflect the Aloha folder.

Aloha POS

C:\ALOHA\IBER.BAT

default

Use only if this computer is a server/terminal.� Adjust the 'Target' setting to reflect the Aloha folder.

Aloha Manager

C:\ALOHA\BIN\ALOHAMGR.EXE

default

Adjust the 'Target' setting to reflect the Aloha folder.

Aloha Credit Cards

C:\ALOHA\BIN\EDC.EXE

default

If used, adjust the 'Target' setting to reflect the Aloha folder.

Aloha Labor Scheduler

C:\ALOHA\BACKOFFICE\SCHEDULE\ESP.EXE

default

Use this only if Labor Scheduler is installed.� Adjust the 'Target' setting to reflect the BackOffice folder.

Services

N/A

N/A

Drag the Services icon from the Windows Control Panel to the desktop to create this shortcut.

pcANYWHERE

MODEM.BHF in the pcANYWHERE DATA folder.

Default

Use only if pcANYWHERE is installed.

Windows NT, Windows 2000 or Windows XP Terminal

IN order to access these settings on an existing icon, right-click the icon on the desktop, and select Properties.� Select the Shortcut tab.� To create new icons, right-click the desktop, select New, and select Shortcut.

Desktop Name

Target

Start in

Notes

My Computer

N/A

N/A

Windows default

Network Neighborhood

N/A

N/A

Windows default

Recycle Bin

N/A

N/A

Windows default

Aloha POS

C:\ALOHA\IBERCFG.BAT

default

Adjust the 'Target' setting to reflect the Aloha folder.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1007

Aloha BackOffice Interfaces and RPC Service

Aloha BackOffice Interfaces and RPC Service

============================================================================

AKBID1008

Created: 21 January 2000

Updated: 2 January 2001

Reviewed: 4 February 2004

Microsoft Windows Versions: Windows NT, Windows 2000, Windows XP, Windows Server 2003

Aloha Products: BackOffice

Aloha POS Versions: 3.6x � 5.3.x

Subject: Aloha BackOffice Interfaces and Windows NT RPC Service

============================================================================

Summary

The ALOHA^� Application Software BackOffice interfaces indirectly use the Microsoft^� Windows NT^�, Windows^� 2000, Windows XP, and Windows Server 2003 Remote Procedure Call (RPC) service.� Under certain circumstances, an error can occur during the Windows NT, Windows 2000, or Windows XP start up procedure regarding the BackOffice interface's association with the RPC service.��

Information

The RPC Service error is most likely to occur on Windows NT/2000/XP/2003 file servers using the Auto Log In (refer to document AKBID1005) feature and Aloha BackOffice.� When Windows starts, the Aloha BackOffice interface in the Windows StartUp folder becomes activated before Windows has finished activating the RPC service.� The error states 'The RPC server is unavailable.'

Under normal circumstances, start the interface as the Aloha Installation CD configured it.� Only use the following fix if the symptoms described in this document occur.

To alleviate the error message, create a batch file in the same folder as the interface executables.� For example, if you are experiencing this problem with the Gift Certificate Manager interface, create a batch file called GCINTERF.BAT in the \BACKOFFICE\GC folder and add the following lines:

WAIT 30

D:

CD\ALOHA\BACKOFFICE

START D:\ALOHA\BACKOFFICE\GC\GCOLI08F.EXE

EXIT

Replace \GC\GCOLI08F.EXE in the batch file with the correct interface.

The batch file performs the following:

-          The first line uses the WAIT.EXE utility (refer to document AKBID1012) to create a 30-second pause.� This enables the RPC service to start.�

-          The working folder must be the BackOffice folder, so the batch file navigates to it.

-          The START command starts the interface and enables the batch file to continue to the next line after the interface starts, which ends the batch file and closes the command prompt.�

Create a shortcut to the batch file in the Windows Start Up group replacing the existing interface shortcut.

Extended Information

You can set the batch file's icon to the interface's original icon in order to create a cleaner, more professional installation.� To change the icon, open the properties of the shortcut, right-click on the shortcut, select Properties/Shortcut/Change Icon/Browse, path out the actual interface executable, and select OK.� Select the appropriate bitmap from the bitmaps that display.

Caveats

Under normal circumstances, start the interface as the Aloha Installation CD configured it.� Only use the following fix if the symptoms described in this document occur.

============================================================================

See also:

AKBID1005 Microsoft Windows Automatic Log In

AKBID1012 Aloha Application Software Utility Description and Usage

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1008 a/r accounts buyer delivery frequent receivable

Windows 95 FOH Terminal Setup

Windows 95 FOH Terminal Setup

============================================================================

AKBID1009

Created: 17 December 1999

Updated: 15 May 2003

Reviewed: 2 March 2004

Microsoft Windows Versions: Windows 95

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

Subject: Windows 95 FOH Terminal Setup

============================================================================

Summary

The ALOHA^� application software requires several specialized settings (as well as several preferred settings) in the Microsoft^� Windows^� 95 operating system (OS) to properly run IBER.EXE and IBERQS.EXE in the Front-of-House (FOH).� If you are using the terminal to run both Aloha Front-of-House (FOH) and Back-of-House (BOH) together, refer to document AKBID1023.

Information

This document is written for users familiar with Windows 95.� This document describes procedures for Windows 95 OSR2 (version B) and Windows 95 OSR2.5 (version C).� If you are not using one of these two versions of Windows 95, you need to upgrade your operating system.

Since some computers come with Windows 95 preloaded while others do not, this document is based on editing the settings of Windows 95.� Users who are installing Windows 95 from scratch or upgrading another OS to Windows 95 can still use this document either by employing these instructions after the Windows 95 installation or by making many of these changes during the Windows 95 installation.

File System

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

The most important settings in the Aloha application software involve the network settings.� To access these settings, select Start/Settings/Control Panel/Network or right-click the Network Neighborhood icon on your desktop and select Properties.

The Configuration tab contains a Components area and Primary Network Logon type.� The components area should have Client for Microsoft Networks as the only network client installed.� You may have others, but these should only be added if absolutely needed.� The correct drivers for your network interface card (NIC) should also be listed.�

The Aloha application software can use either TCP/IP or NetBEUI as its network protocol.� Select either one, but both the file server and the terminals must use the same protocol.� To assign the protocol for the Aloha application software to use (refer to document AKBID1018), double-click the desired protocol, select the Advanced tab, and select 'Set this protocol to be the default protocol'.� If you select TCP/IP, Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure that terminals always have an address assigned to them.� The Aloha application software will not function without an IP address assigned to the terminal.� You may have multiple protocols installed as long as the proper protocol for the Aloha application software has been marked as such.�

To add file and print sharing for the Aloha application software, click the File and Print Sharing button and select both options.� Print Sharing may be left disabled if you are not using Windows based printer shares for the FOH.�

The Primary Logon Type is typically set to Windows Logon.� This log in enables Windows 95 to skip the prompt for the user name and password if the password is blank.� Setting this as Client for Microsoft Networks prompts for the user name and password regardless if the password is blank.� If Client for Microsoft Networks must be used as the Primary network logon, use the Microsoft Windows 95 TweakUI utility to automatically enter the user name and password.� TweakUI can be downloaded from the Aloha Technologies FTP site as TWEAKUI.ZIP.� Aloha Technologies installs this utility regardless of the Primary Logon Type setting.

Set the terminal's network name under the Identification tab.� Aloha Technologies uses TERM1, TERM2, and so on by default.� Different names may be used, but they must follow Aloha application software specifications.� The terminal name must be a common name used on all terminals (the TERMSTR, refer to document AKBID1010) followed by a number designating the terminal's ID number.� Examples include ALOHA1, ALOHA2, TSFOH_1, and TSFOH_2.� In this case, the TERMSTR would be 'ALOHA' or 'TSFOH_'.� Different TERMSTR names can not be used within the same Aloha system.� Spaces can not be used, but underscores can.� Leading zeros can not be used unless they are part of the TERMSTR, but it is not recommended.

Set the Workgroup name the same on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the Workgroup name, but this name can be of your choice as long as it is consistent throughout the Aloha application software.�

The Computer Description is solely to your discretion.

Ensure that 'Share-level access control' is selected under the Access Control tab.� Only experienced Domain administrators should consider using 'User-level access control'.

Aloha Share Name

The Aloha application software requires a network share name of BOOTDRV.� This is the required name.� This share needs to be applied to the root folder or drive in which the Aloha folder resides.� To set the share, right-click the drive or folder and choose Sharing.� Set the Share Name to BOOTDRV, the Access Type to Full, and leave the password fields blank.

If the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.� Some clients prefer to place the Aloha application software in a special folder in order to limit the shared files, and, therefore, enhance security.� Sharing the entire drive in which the Aloha application software resides also shares other files that reside on the drive, such as Windows.

Display Settings

To access the Display settings, select Start/Settings/Control Panel/Display or right-click the Windows desktop and select Properties.� Select the Settings tab.� Set the Color palette to 256 Colors or higher.� Aloha Technologies typically uses 16-bit color.�

Refer to document AKBID1165 for screen resolution settings.

Do not enable a Windows screen saver.

Time Zone & Daylight Savings

For the file server and all terminals to display the correct time and adjust to Daylight Savings changes properly, the Time and Date settings must be properly configured in Windows.� Select Start/Settings/Control Panel/Date/Time or double-click the time displayed on the task bar.� Ensure the date and time are correct.� Ensure the date and time are correct on the Date & Time tab.� Ensure the correct time zone is chosen on the Time Zone tab.� This time zone needs to be the same on all terminals and the file server.� If the area observes Daylight Savings, then the 'Automatically adjust clock for daylight savings changes' option must be selected on all terminals and the file server.� This can be turned on or off, but it needs to be consistent throughout the Aloha application software.

FIFO Buffers

Windows 95 enables First-In-First-Out (FIFO) buffers for each COM port.� These buffers tend to interfere with printers using Xon/Xoff flow control, so Aloha Technologies disables these buffers on all COM ports on all terminals, regardless of the printer type.� (In the event of a printer or COM port failure, a printer using Xon/Xoff flow control may be temporally connected to the port in the future.)

To access the FIFO buffer settings, select Start/Settings/Control Panel/System or right click My Computer and select Properties.� Select the Device Manager tab, and click the plus sign (+) next to Ports to expand it.� Select each port one at a time, and select Properties/Port Settings/Advanced.� Clear 'Use FIFO buffer'.� Repeat for each COM port.� The LPT port does not have this option.

Scandisk Autoscan & Settings

By default, if Windows is shut down improperly, it runs Scandisk the next time the system is started.� The problem resides in the prompt to do so.� A prompt displays a scolding for improperly shutting down Windows and to press any key to continue and run Scandisk.� Since there is not a keyboard that is typically attached to a FOH terminal, the user would have to wait for the two-minute timeout before Windows will continue.� The MSDOS.SYS file must be adjusted for Windows to automatically run Scandisk when needed without prompting for user interaction.�

Open Explorer and navigate to C:\.� Right-click the MSDOS.SYS file (if the file is not displayed, adjust your Explorer settings using the directions in the Explorer Settings portion of this document) and choose Properties.� Clear the 'Read-only' option and close the Properties window.� Double-click the MSDOS.SYS file and choose to open it with Notepad.� Under the [OPTIONS] section, add a new line which reads AUTOSCAN=2.� Close Notepad and save your changes.� Re-enable the Read-only attribute for the MSDOS.SYS file.� (Some terminals come from the manufacturer with the AUTOSCAN option already enabled.)

Once Scandisk is set to run properly, if it finds any problems on the drive, it prompts for answers.� Again, there is not a keyboard that is typically attached to a FOH terminal to answer the questions, which increases the time the Aloha application software may be disrupted.� To alleviate this problem, Aloha Technologies offers a SCANDISK.INI that keeps Windows from prompting for 95% of the questions.� This SCANDISK.INI can be downloaded from the Aloha Technologies FTP site as SCANDISK.ZIP.� Place this file in the Windows COMMAND folder overwriting the one that currently exists.

Login Name

Refer to document AKBID1006 for more information on user login information.

To clear the current user names and passwords, delete *.PWL from the Windows folder to remove all users.� Select Start/Shutdown.� Select 'Close all programs and log in as a different user' and click Yes.� Windows logs the current user out and prompts for a user name and password.� Enter the desired user and password and log in to Windows.

VNetBIOS

Windows 95 might experience network problems with restaurants using five or more terminals.� To ensure that terminals do not experience these problems, Microsoft issued a new VNETBIOS.VXD that you can download from the Aloha Technologies FTP site as VNETBIOS.ZIP.� Aloha Technologies installs this .VXD file on all terminals, regardless of the system's size.� Refer to document AKBID1011 for more information.

Once you have the new .VXD, place it in the Windows SYSTEM folder overwriting the current version.� Edit the SYSTEM.INI in the Windows folder, and add a new line in the [386Enh] section that states NUMHCBS=x.� Replace x with a number four times the number of terminals in the system, but not less than 80 nor exceeding 200.� The default for this number is 100.� For example, a 25 terminal system would use NUMHCBS=100.� Do not exceed 100 unless you have more than 25 terminals.

To ensure that Windows does not overwrite the updated VNETBIOS.VXD following network configuration changes, place a copy of the updated VNETBIOS.VXD in the same folder as the Windows CAB files.

AUTOEXEC.BAT

Aloha Technologies uses a default AUTOEXEC.BAT (before the Aloha application software is installed) which contains only two lines:

SET PATH=%PATH%

DOSKEY

The first line creates a PATH variable that Windows 95 does not install by default.� If the path statement does not reside in AUTOEXEC.BAT, some software packages create a new path line that does not include the Windows default path.� With this line, the software will most likely append to the line and preserve the Windows path.

The second line installs DosKey.� DosKey is an application used in a command prompt that recalls previous lines typed via the arrow up and down keys.� For users accustomed to a command prompt environment, it is a welcome feature.

Install Aloha Software

Once Windows 95 is set up according to the standards outlined in this document and you can view the network, use the terminal installation diskette to install the Aloha application software.

To create this diskette, insert the installation CD in the file server's CD-ROM, and run SETUPPOS.EXE /ADVANCED.� Select Make Diskettes/Create Terminal Installation Diskette from the Main Menu

Once the diskette is created, insert it into the terminal's floppy drive, and run SETUP.EXE.� The setup program walks you through the rest of the installation.

If the terminal does not have a floppy drive, run the Terminal Installation application directly from the CD-ROM on the file server.� Map a drive to the CD-ROM on the file server.� Do not choose the Reconnect at Logon option when mapping the drive.� Run the file \TERMINST\SETUP.EXE from the Aloha POS CD.� The setup program walks you through the rest of the installation.

Extended Information

No information.

Caveats

There have been instances where Dial-Up Networking was installed on Windows 95 and caused conflicts with networking abilities in the Aloha application software.� The reason is currently unknown.

============================================================================

See also:

AKBID1001 Configuring the CALIBRATE Variable on Aloha Terminals

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1009 Microsoft Windows 95 FOH Terminal Setup

AKBID1010 Aloha Application Software System Environment Variables

AKBID1011 Windows 9x VNETBIOS.VXD Patch

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1018 Network Lana Numbers

AKBID1023 Microsoft Windows 95 Filer Server/Terminal Setup

AKBID1028 Winhook

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1165 FOH Screen Resolution Settings

AKBID1175 Aloha Terminal Restart Options

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1009 stage staging

Aloha Application Software System Environment Variables

Aloha Application Software System Environment Variables

============================================================================

AKBID1010

Created: 17 January 2000

Updated: 15 October 2003

Reviewed: 5 February 2004

Windows Versions: All

Aloha Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 3.0x � 5.3.x

Subject: Aloha Application Software System Environment Variables

============================================================================

Summary

The ALOHA^� application software Front-of-House (FOH) and Back-of-House (BOH) applications use command line parameters and system environment variables to change the way the Aloha application software functions.�

Most applications support multiple parameters and variables.

Information

Quick Reference

Application

Variables

ALOHAMGR.EXE

ALOHAMANAGEREXITONLOGOUT, ALOHAMGRPAGE, ALOHAPEXRES, ALOHAPEYRES, DATA, IBERDIR, NOMUTEX, RECORDDUPDBFRECORDS, REMOTE, SQLMODE

ALOHASPY.EXE

CTLPROCESS, DEBUG, IBERDIR, MAXDEBOUTDAYS, MAXDEBOUTSIZE, NONET, REGSERVER, SERVICE, UNREGSERVER

CESSVR.EXE

REGSERVER, SERVICE, UNREGSERVER

CTL.EXE

CRYSTAL, DEBUG, DEBUGCOPYTOSTORE, DEBUGCRWREPORTPARMS, DEBUGGRINDMANAGER, DEBUGGRINDSTORE, DEBUGGRINDTHREAD, DELETEVID, EXIT, IBERDIR, MULTIDEBUG, NOMUTEX, NONET, NOROBUST, REMOTE, ROBUST, SERVER, SQLMODE, TERMSTR

CTLSVR.EXE

ACCOUNTNAME, CLUBIMPORTFILE, DEBUG, DEBUGGRINDMANAGER, IBERDIR, MAXDEBOUTDAYS, MAXDEBOUTSIZE, MULTIDEBUG, NOMUTEX, NONET, NOROBUST, PASSWORD, REGSERVER, REMOTE, ROBUST, SERVER, SERVICE, SNAME, SPWD, SQLMODE, TERMSTR, UNREGSERVER

DBFDIFF.EXE

HKEY

DBUP2.EXE

ASSIGNSECURITYLEVEL, ATTENDED, CDX, CDXCHECK, CENTRALSITE, CONFIGONLY, CREATEDB, CREATEDBF, DBFINPUT, DBFONLY, DBFOUTPUT, DBONLY, DEBUG, ENTERPRISE, FORCESECURITY, FORCEUPGRADE, IBERDIR, NODBFCOPY, VERBOSE

DBUP3.EXE

ALLTABLES, ASSIGNSECURITYLEVEL, ATTENDED, CDX, CDXCHECK, CENTRALSITE, CONFIGONLY, CREATEDB, CREATEDBF, DBFINPUT, DBFONLY, DBFOUTPUT, DBONLY, DEBUG, ENTERPRISE, FORCESECURITY, FORCEUPGRADE, IBERDIR, NODBFCOPY, VERBOSE

DRSQL.EXE

IBERDIR

EDC.EXE

EDCSVR, IBERDIR, REPORTMODE, SECSVR, SECSVRPATH

EDCSVR.EXE

ACCOUNTNAME, DATADIR, DEBUGEXT, DEBUGSCAN, EDCDIR, EDCPATH, IBERDIR, IBERROOT, MULTIPLEMERCHANTIDS, NOMUTEX, PASSWORD, PMSDIR, PMSPATH, REGSERVER, S, SCANRESTRICT, SERVICE, SNAME, SPWD, TERMSTR, UNREGSERVER

EDOLDTM.EXE

IBERDIR, N, P, SQLMODE

ESP.EXE

ADDEMP, DATA, DELEMP, EDITEMP, IBERDIR

FASTECH.DLL

BACKOFFICEDIR, IBERDIR

GRIND.EXE

BALANCE, CLUBIMPORT, DATA, DATE, DEBUG, DEBUGCONVERTLOG, DEBUGCONVERTTRANSLOG, DEBUGMERGETRANSLOGS, DEBUGSQLBUILD, FORCECONVERTLOG, HOUSE, IBERDIR, INTERVAL, MERGETRANSLOGS, NODELETELOG, NOMUTEX, NOWINDOW, PAYCHEX, REGRIND, ROBUST, SQLMODE, STOREDIR, STORENUM, TIMING, USESLEEPING

GRINDQ.EXE

BALANCE, CLUBIMPORT, DATA, DATE, DEBUG, DEBUGCONVERTLOG, DEBUGMERGETRANSLOGS, DEBUGSQLBUILD, FORCECONVERTLOG,� HOUSE, IBERDIR, INTERVAL, MERGETRANSLOGS, NODELETELOG, NOMUTEX, NOWINDOW, PAYCHEX, REGRIND, ROBUST, SQLMODE, STOREDIR, STORENUM, TIMING, USESLEEPING

IBER.EXE

ALOHABIGFONTNAME, ALOHABIGFONTSIZE, ALOHAHUGEFONTNAME, ALOHAHUGEFONTSIZE, ALOHALEFT, ALOHAMEDIUMFONTNAME, ALOHAMEDIUMFONTSIZE, ALOHASMALLFONTNAME, ALOHASMALLFONTSIZE, ALOHASYSTEMFONTNAME, ALOHASYSTEMFONTSIZE, ALOHATINYFONTNAME, ALOHATINYFONTSIZE, ALOHATOP, ALOHAXRES, ALOHAYRES, AUTOCREATE, AUTOEXIT, AUTOUPGRADE, CALIBRATE, CONTRAST, DATA, DEBUG, DEBUG_COM, DEBUG_DISPLAY_BOARD, DELETEVID, DEBUGMSR, DEBUGSCALES, DEBUGTOUCH, DEV, DOUBLECLICK, EDCPATH, EGI, IBERDIR, IBERROOT, IBM4695MSR, LIQUORPLUDIGITS, LOCALDIR, LOCALREAD, MASTERCAPABLE, MASTERFILEDEBUG, MASTERFILEFREQ, MMSHEME, MULTILIQUORTAPTERM, MULTISERVER, NCR_MSR_FIX, NOFATALMSGBOX, NOROBUST, NUMTERMS, PROHOSTDIR, REBOOTNT, REGSERVER, ROBUST, SERVER, SERVERCAPABLE, STOPLOGO, STOREID, SUPPRESSTIPLINE, TERM, TERMSTR, UNREGSERVER, USEFULLMEMBERMAGCARD, USEONLY5DIGITS

IBERQS.EXE

ALOHABIGFONTNAME, ALOHABIGFONTSIZE, ALOHAHUGEFONTNAME, ALOHAHUGEFONTSIZE, ALOHALEFT, ALOHAMEDIUMFONTNAME, ALOHAMEDIUMFONTSIZE, ALOHASMALLFONTNAME, ALOHASMALLFONTSIZE, ALOHASYSTEMFONTNAME, ALOHASYSTEMFONTSIZE, ALOHATINYFONTNAME, ALOHATINYFONTSIZE, ALOHATOP, ALOHAXRES, ALOHAYRES, AUTOCREATE, AUTOEXIT, AUTOUPGRADE, CALIBRATE, CONTRAST, DATA, DATE, DEBUG, DEBUG_COM, DEBUG_DISPLAY_BOARD, DEBUGMSR, DEBUGSCALES, DEBUGTOUCH, DELETEVID, DEV, DOUBLECLICK, EDCPATH, EGI, IBERDIR, IBERROOT, IBM4695MSR, LIQUORPLUDIGITS, LOCALDIR, LOCALREAD, MASTERCAPABLE, MMSCHEME, MULTILIQUORTAPTERM, MULTISERVER, NCR_MSR_FIX, NOFATALMSGBOX, NONET, NOTIPS, NUMTERMS, REBOOTNT, ROBUST, SERVER, SERVERCAPABLE, STOPLOGO, STOREID, SUPPRESSTIPLINE, TERM, TERMSTR, VERIFONEONIBMPORT

LABSCHED.EXE

DATA, IBERDIR

MNT.EXE

DATA, DATE, IBERDIR, SQLMODE

PAYRECON.EXE

DATADIR, IBERDIR

REPRINT.EXE

ALL, ALTALOHAINI, CKO, DATA, DATE, DEBUG, DEBUGCONVERTLOG, IBERDIR, RPTAUDIT, RPTXFERS, SQLMODE, STORENUM

RPT.EXE

CTLREMOTE, DATE, IBERDIR, NODEPOSIT, NUM, PRD, R, SQLMODE, TYPE

TEAMSERV.EXE

IBERDIR, NOMUTEX

USERTOOL.DLL

DATA, DATE, IBERDIR

VIDEO.EXE

AUTOEXIT, DATA, DATE, NONET, NOROBUST, ROBUST, SERVER, VIDEO, VIDEOHEIGHT, VIDEOWIDTH, VIDEOX, VIDEOY

VIDEOMX.DLL

DEBUGIBM, DEBUGPV, DEBUGQSR, DEBUGSV, IBERDIR, IBMBAUD, IBMMODE, IBMPORT, IBMVIDEOS, PVPORT, QSRBAUD, QSRMODE, QSRPORT, QSRVIDEO, QSRVIDEOS, SVBAUD, SVIDEOS, SVMODE, SVPORT

Variables

Variable

ACCOUNTNAME

Applications

CTLSVR.EXE, EDCSVR.EXE

Description

Specifies the user name with which the server will log in as if you are using 5.230 or higher with the Windows NT, Windows 2000 or Windows XP operating systems.� Used in conjunction with the PASSWORD environment variable.� Refer to document AKBID1019.

System Variable Example

N/A

Command Line Example

CTLSVR.EXE /SERVICE /ACCOUNTNAME .\<user name>

Variable

ADDEMP

Applications

ESP.EXE

Description

Adds an employee to the schedule.

System Variable Example

N/A

Command Line Example

ESP.EXE /ADDEMP <employee ID> <employee first name> <employee last name>

Variable

ALL

Applications

REPRINT.EXE

Description

Reprints all guest checks.

System Variable Example

N/A

Command Line Example

REPRINT.EXE /ALL

Variable

ALLTABLES

Applications

DBUP3.EXE

Description

Instructs DBUP.EXE to update all of the RDB tables, not just tables that have changed.� Refer to document AKBID1067 for more information.

System Variable Example

N/A

Command Line Example

DBUP3.EXE /ALLTABLES

Variable

ALOHABIGFONTNAME

Applications

IBER.EXE, IBERQS.EXE

Description

Defines the 'Big' font for use in the FOH.� Refer to document AKBID1097.

System Variable Example

SET ALOHABIGFONTNAME=<font name>

Command Line Example

N/A

Variable

ALOHABIGFONTSIZE

Applications

IBER.EXE, IBERQS.EXE

Description

Defines the 'Big' font size to use in the FOH.� Refer to document AKBID1097.

System Variable Example

SET ALOHABIGFONTSIZE=<size, e.g.� 10>

Command Line Example

N/A

Variable

ALOHAHUGEFONTNAME

Applications

IBER.EXE, IBERQS.EXE

Description

Defines the 'Huge' font for use in the FOH.� Refer to document AKBID1097.

System Variable Example

SET ALOHAHUGEFONTNAME=<font name>

Command Line Example

N/A

Variable

ALOHAHUGEFONTSIZE

Applications

IBER.EXE, IBERQS.EXE

Description

Defines the 'Huge' font size to use in the FOH.� Refer to document AKBID1097.

System Variable Example

SET ALOHAHUGEFONTSIZE=<size, e.g.� 10>

Command Line Example

N/A

Variable

ALOHALEFT

Applications

IBER.EXE, IBERQS.EXE

Description

Specifies the left coordinate for the FOH (in pixels).

System Variable Example

N/A

Command Line Example

IBERQS.EXE /ALOHALEFT <pixel number>

Variable

ALOHAMANAGEREXITONLOGOUT

Applications

ALOHAMGR.EXE

Description

Forces Aloha Manager to exit upon logout rather than just logging the user out.

System Variable Example

SET ALOHAMANAGEREXITONLOGOUT=TRUE

Command Line Example

N/A

Variable

ALOHAMEDIUMFONTNAME

Applications

IBER.EXE, IBERQS.EXE

Description

Defines the 'Medium' font for use in the FOH.� Refer to document AKBID1097.

System Variable Example

SET ALOHAMEDIUMFONTNAME=<font name>

Command Line Example

N/A

Variable

ALOHAMEDIUMFONTSIZE

Applications

IBER.EXE, IBERQS.EXE

Description

Defines the 'Medium' font size to use in the FOH.� Refer to document AKBID1097.

System Variable Example

SET ALOHAMEDIUMFONTSIZE=<size, e.g.� 10>

Command Line Example

N/A

Variable

ALOHAMGRPAGE

Applications

ALOHAMGR.EXE

Description

Sets the initial page for the Aloha Manager display.� The initial page usually resides on the local hard drive.

System Variable Example

SET ALOHAMGRPAGE=<web address or local HTML file>

Command Line Example

N/A

Variable

ALOHAPEXRES

Applications

ALOHAMGR.EXE

Description

Used with ALOHAPEYRES, defines the screen width in a custom resolution size for Panel Editor.� The custom resolution is displayed as [custom] in Panel Editor's list of resolutions.� Refer to document AKBID3228 for more information.

System Variable Example

SET ALOHAPEXRES=<size, e.g.� 240>

Command Line Example

N/A

Variable

ALOHAPEYRES

Applications

ALOHAMGR.EXE

Description

Used with ALOHAPEXRES, defines the screen height in a custom resolution size for Panel Editor.� The custom resolution is displayed as [custom] in Panel Editor's list of resolutions.� Refer to document AKBID3228 for more information.

System Variable Example

SET ALOHAPEYRES=<size, e.g.� 320>

Command Line Example

N/A

Variable

ALOHASMALLFONTNAME

Applications

IBER.EXE, IBERQS.EXE

Description

Defines the 'Small' font for use in the FOH.� Refer to document AKBID1097.

System Variable Example

SET ALOHASMALLFONTNAME=<font name>

Command Line Example

N/A

Variable

ALOHASMALLFONTSIZE

Applications

IBER.EXE, IBERQS.EXE

Description

Defines the 'Small' font size to use in the FOH.� Refer to document AKBID1097.

System Variable Example

SET ALOHASMALLFONTSIZE=<size, e.g.� 10>

Command Line Example

N/A

Variable

ALOHASYSTEMFONTNAME

Applications

IBER.EXE, IBERQS.EXE

Description

Defines the 'System' font for use in the FOH.� Refer to document AKBID1097.

System Variable Example

SET ALOHASYSTEMFONTNAME=<font name>

Command Line Example

N/A

Variable

ALOHASYSTEMFONTSIZE

Applications

IBER.EXE, IBERQS.EXE

Description

Defines the 'System' font size to use in the FOH.� Refer to document AKBID1097.

System Variable Example

SET ALOHASYSTEMFONTSIZE=<size, e.g.� 10>

Command Line Example

N/A

Variable

ALOHATINYFONTNAME

Applications

IBER.EXE, IBERQS.EXE

Description

Defines the 'Tiny' font for use in the FOH.� Refer to document AKBID1097.

System Variable Example

SET ALOHATINYFONTNAME=<font name>

Command Line Example

N/A

Variable

ALOHATINYFONTSIZE

Applications

IBER.EXE, IBERQS.EXE

Description

Defines the 'Tiny' font size to use in the FOH.� Refer to document AKBID1097.

System Variable Example

SET ALOHATINYFONTSIZE=<size, e.g.� 10>

Command Line Example

N/A

Variable

ALOHATOP

Applications

IBER.EXE, IBERQS.EXE

Description

Specifies the top coordinate for the FOH (in pixels).

System Variable Example

N/A

Command Line Example

IBERQS.EXE /ALOHATOP <pixel number>

Variable

ALOHAXRES

Applications

IBER.EXE, IBERQS.EXE

Description

Specifies the 'x' screen resolution for the FOH (in pixels).� In versions 5.021 and lower, the default resolution is 640x480.� In versions 5.022 and higher, the resolution defaults to the current Windows resolution.

System Variable Example

SET ALOHAXRES=<pixels>

Command Line Example

N/A

Variable

ALOHAYRES

Applications

IBER.EXE,IBERQS.EXE

Description

Specifies the 'y' screen resolution for the FOH (in pixels).� In versions 5.022 and higher, the resolution defaults to the current Windows resolution.

System Variable Example

SET ALOHAYRES=<pixels>

Command Line Example

N/A

Variable

ALTALOHAINI

Applications

REPRINT.EXE

Description

Specifies of an alternate ALOHA.INI path.� Used only with SuperSites.

System Variable Example

N/A

Command Line Example

REPRINT.EXE /ALTALOHAINI <path>

Variable

ASSIGNSECURITYLEVEL

Applications

DBUP2.EXE, DBUP3.EXE

Description

Assigns security levels to employees based on previous data.� Refer to document AKBID1067.

System Variable Example

N/A

Command Line Example

DBUP2.EXE /ASSIGNSECURITYLEVEL

Variable

ATTENDED

Applications

DBUP2.EXE, DBUP3.EXE

Description

Sends messages to the screen via a Message box.� Refer to document AKBID1067.

System Variable Example

N/A

Command Line Example

DBUP2.EXE /ATTENDED

Variable

AUTOCREATE

Applications

IBER.EXE, IBERQS.EXE

Description

Automatically creates DBF files.

System Variable Example

N/A

Command Line Example

IBERQS.EXE /AUTOCREATE

Variable

AUTOEXIT

Applications

IBER.EXE, IBERQS.EXE, VIDEO.EXE

Description

AUTOEXIT instructs the Aloha application software FOH to restart the terminal upon the exit of the Aloha application software if the operating system is Microsoft^�Windows^� 95, Windows 98, or Windows Millennium Edition (Me).� AUTOEXIT instructs the Aloha application software FOH to log out the user (which will automatically log back in if Windows NT, Windows 2000 or Windows XP automatic log in feature is used) upon the exit of the Aloha application software if the operating system is Windows NT, Windows 2000 or Windows XP.� See the REBOOTNT variable.� In some older versions of the Aloha application software, this variable is considered true regardless of the assigned value.� In these versions, you must completely remove the variable in order to disable it.� Refer to document AKBID1005.

System Variable Example

SET AUTOEXIT=TRUE.

Command Line Example

N/A

Variable

AUTOUPGRADE

Applications

IBER.EXE, IBERQS.EXE

Description

Automatically upgrades DBF files.

System Variable Example

N/A

Command Line Example

IBERQS.EXE /AUTOUPGRADE

Variable

BACKOFFICEDIR

Applications

FASTECH.DLL

Description

Defines the BackOffice path.

System Variable Example

SET BACKOFFICEDIR=<path>

Command Line Example

N/A

Variable

BALANCE

Applications

GRIND.EXE, GRINDQ.EXE

Description

Creates BALANCE.TXT in the target folder with detailed financial information to enable easier solutions to report balancing questions.� Refer to document AKBID3206.

System Variable Example

N/A

Command Line Example

GRIND.EXE /DATE <yyyymmdd> /BALANCE

Variable

CALIBRATE

Applications

IBER.EXE, IBERQS.EXE

Description

CALIBRATE defines the path and touch screen calibration executable for touch screen calibration from the Aloha application software FOH.� Refer to document AKBID1001.

System Variable Example

SET CALIBRATE=<path>

Command Line Example

N/A

Variable

CDX

Applications

DBUP2.EXE, DBUP3.EXE

Description

Rebuilds CDX files (always).� Refer to document AKBID1067.

System Variable Example

N/A

Command Line Example

DBUP2.EXE /CDX

Variable

CDXCHECK

Applications

DBUP2.EXE, DBUP3.EXE

Description

Rebuilds CDX files, if needed.� Refer to document AKBID1067.

System Variable Example

N/A

Command Line Example

DBUP2.EXE /CDXCHECK

Variable

CENTRALSITE

Applications

DBUP2.EXE, DBUP3.EXE

Description

Upgrades a Enterprise central site.� Refer to document AKBID1067.

System Variable Example

N/A

Command Line Example

DBUP2.EXE /CENTRALSITE

Variable

CKO

Applications

REPRINT.EXE

Description

Open the Assign Checkouts dialog at the start of reprint.

System Variable Example

N/A

Command Line Example

REPRINT.EXE /CKO

Variable

CLUBIMPORT

Applications

GRIND.EXE, GRINDQ.EXE

Description

Imports the Membership Interface member file to the NEWDATA folder.

System Variable Example

N/A

Command Line Example

GRIND.EXE /CLUBIMPORT

Variable

CLUBIMPORTFILE

Applications

CTLSVR.EXE

Description

Defines the name and location of the Membership Interface import file.

System Variable Example

SET CLUBIMPORTFILE=<path and file name>

Command Line Example

N/A

Variable

CONFIGONLY

Applications

DBUP2.EXE, DBUP3.EXE

Description

Upgrades the configuration files only.� Refer to document AKBID1067.

System Variable Example

N/A

Command Line Example

DBUP2.EXE /CONFIGONLY

Variable

CONTRAST

Applications

IBER.EXE, IBERQS.EXE

Description

Used only with IBM 4695 POS terminals, CONTRAST enables the adjustment of the touch screen monitor�s contrast level.� Refer to document AKBID1032.

System Variable Example

SET CONTRAST=<level>

Command Line Example

N/A

Variable

CREATEDB

Applications

DBUP2.EXE, DBUP3.EXE

Description

Creates new RDB files from existing DBF files.� Refer to document AKBID1067.

System Variable Example

N/A

Command Line Example

DBUP2.EXE /CREATEDB

Variable

CREATEDBF

Applications

DBUP2.EXE, DBUP3.EXE

Description

Creates new DBF files from existing RDB files.� Refer to document AKBID1067.

System Variable Example

N/A

Command Line Example

DBUP2.EXE /CREATEDBF

Variable

CRYSTAL

Applications

CTL.EXE

Description

Run the Crystal Report interface remotely.� Refer to document AKBID1040 and AKBID1108.

System Variable Example

SET CRYSTAL=TRUE

Command Line Example

CTL.EXE /CRYSTAL

Variable

CTLPROCESS

Applications

ALOHASPY.EXE

Description

Determines if ALOHASPY.EXE controls CTLSVR.EXE.� Use a non-zero for 'yes', and 0 for 'no'.

System Variable Example

N/A

Command Line Example

ALOHASPY.EXE /CTLPROCESS <0 or 1>

Variable

CTLREMOTE

Applications

RPT.EXE

Description

Indicates that CTL.EXE starts the Grind process instead of RPT.EXE doing it directly.� Using REMOTE with CTL.EXE performs the same function.� Refer to document AKBID1040.

System Variable Example

N/A

Command Line Example

RPT.EXE /CTLREMOTE

Variable

DATA

Applications

ALOHAMGR.EXE, ESP.EXE, IBER.EXE, IBERQS.EXE, GRIND.EXE, GRINDQ.EXE, LABSCHED.EXE, MNT.EXE, REPRINT.EXE, USERTOOL.DLL, VIDEO.EXE

Description

Specifies the DATA folder inside the current IBERDIR.� For most applications, this has the exact same effect as the DATE parameter.� This does not enable a different IBERDIR, unless the IBERDIR variable is used in conjunction.

System Variable Example

N/A

Command Line Example

GRIND.EXE /DATA <folder>

Variable

DATADIR

Applications

EDCSVR.EXE, PAYRECON.EXE

Description

Sets the name of the Data folder.

System Variable Example

SET DATADIR=<folder name>

Command Line Example

N/A

Variable

DATE

Applications

GRIND.EXE, GRINDQ.EXE, RPT.EXE, IBERQS.EXE, MNT.EXE, REPRINT.EXE, USERTOOL.DLL, VIDEO.EXE

Description

Defines the dated folder to use.� Use DATA as the date for the current day�s data.� For most applications, this parameter is equivalent to the DATA parameter.

System Variable Example

N/A

Command Line Example

C:\ALOHA\BIN\GRIND.EXE /DATE <folder>

Variable

DBFINPUT

Applications

DBUP2.EXE, DBUP3.EXE

Description

Specifies the name of the input DBF folder.� Refer to document AKBID1067.

System Variable Example

N/A

Command Line Example

DBUP2.EXE /DBFINPUT <path>

Variable

DBFONLY

Applications

DBUP2.EXE, DBUP3.EXE

Description

Restricts upgrade to DBF files only.� Refer to document AKBID1067.

System Variable Example

N/A

Command Line Example

DBUP2.EXE /DBFONLY

Variable

DBFOUTPUT

Applications

DBUP2.EXE, DBUP3.EXE

Description

Specifies the name of the output DBF folder.� Refer to document AKBID1067.

System Variable Example

N/A

Command Line Example

DBUP2.EXE /DBFOUTPUT <path>

Variable

DBONLY

Applications

DBUP2.EXE, DBUP3.EXE

Description

Upgrades RDB only.� Refer to document AKBID1067.

System Variable Example

N/A

Command Line Example

DBUP2.EXE /DBONLY

Variable

DEBUG

Applications

ALOHASPY.EXE, CTL.EXE, CTLSVR.EXE, GRIND.EXE, GRINDQ.EXE, IBER.EXE, IBERQS.EXE, REPRINT.EXE, DBUP2.EXE, DBUP3.EXE, DBUP3.EXE

Description

Generates extra debugging information in the Debout files.

System Variable Example

N/A

Command Line Example

ALOHASPY.EXE /DEBUG

Variable

DEBUG_COM

Applications

IBER.EXE, IBERQS.EXE

Description

Generates extra debugging information in the debout files for COM object messages.

System Variable Example

N/A

Command Line Example

IBER.EXE /DEBUG_COM

Variable

DEBUG_DISPLAY_BOARD

Applications

IBER.EXE, IBERQS.EXE

Description

Generates extra debugging information in the debout files for display boards to C:\DISPLAY_BOARD_OUTPUT.TXT.

System Variable Example

SET DEBUG_DISPLAY_BOARD=TRUE

Command Line Example

N/A

Variable

DEBUGCONVERTLOG

Applications

GRIND.EXE, GRINDQ.EXE, REPRINT.EXE

Description

Generates additional debug information in the debout files when converting a TRANS.LOG (transaction log), and it is used with the CONVERTTRANSLOG function.� Has the same effect as the DEBUGCONVERTTRANSLOG variable.� Refer to document AKBID1016.

System Variable Example

N/A

Command Line Example

GRIND.EXE /DEBUGCONVERTLOG /CONVERTTRANS.LOG

Variable

DEBUGCONVERTTRANSLOG

Applications

GRIND.EXE

Description

Generates additional debug information in the debout files when converting a transaction log.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.� Refer to document AKBID1016.

System Variable Example

SET DEBUGCONVERTTRANSLOG=TRUE

Command Line Example

N/A

Variable

DEBUGCOPYTOSTORE

Applications

CTL.EXE

Description

Generates additional debugging information in the debouts when copying files to a Store folder.� Used with SQLMODE only.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.

System Variable Example

SET DEBUGCOPYTOSTORE=TRUE

Command Line Example

N/A

Variable

DEBUGCRWREPORTPARMS

Applications

CTL.EXE

Description

Generates additional Crystal Report Interface parameter debugging information in the debouts.� Refer to document AKBID1108.

System Variable Example

N/A

Command Line Example

CTL.EXE /DEBUGCRWREPORTPARMS

Variable

DEBUGEXT

Applications

EDCSVR.EXE

Description

Sets the extension of the debugging file.� Do not include the dot.� Refer to document AKBID1020.

System Variable Example

N/A

Command Line Example

EDCSVR.EXE /DEBUGEXT <extension>

Variable

DEBUGGRINDMANAGER

Applications

CTL.EXE, CTLSVR.EXE

Description

Generates additional Grind Manager debugging information in the debout files.� Existence of the variable is all that matters.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.� Refer to document AKBID1016.

System Variable Example

SET DEBUGGRINDMANAGER=TRUE

Command Line Example

N/A

Variable

DEBUGGRINDSTORE

Applications

CTL.EXE

Description

Provides additional Store grinding debugging information in the debout files.� Used only with SuperSites.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.� Refer to document AKBID1016.

System Variable Example

SET DEBUGGRINDSTORE=TRUE

Command Line Example

N/A

Variable

DEBUGGRINDTHREAD

Applications

CTL.EXE

Description

Provides additional grind thread initiation debugging information in the debout files.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.� Refer to document AKBID1016.

System Variable Example

SET DEBUGGRINDTHREAD=TRUE

Command Line Example

N/A

Variable

DEBUGIBM

Applications

VIDEOMX.DLL

Description

Generates additional IBM video debugging information in the debout files.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.

System Variable Example

SET DEBUGIBM=TRUE

Command Line Example

N/A

Variable

DEBUGMERGETRANSLOGS

Applications

GRIND.EXE, GRINDQ.EXE

Description

Generates additional debugging information in the debout files when merging transaction logs.� Refer to document AKBID1016.

System Variable Example

SET DEBUGMERGETRANSLOGS=TRUE

Command Line Example

GRIND.EXE /DEBUGMERGETRANSLOGS

Variable

DEBUGMSR

Applications

IBER.EXE, IBERQS.EXE

Description

Enables additional MSR debugging information in the debouts.

System Variable Example

SET DEBUGMSR=TRUE

Command Line Example

N/A

Variable

DEBUGPV

Applications

VIDEOMX.DLL

Description

Generates additional Progressive Systems video debugging information in the debout files.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.

System Variable Example

SET DEBUGPV=TRUE

Command Line Example

N/A

Variable

DEBUGQSR

Applications

VIDEOMX.DLL

Description

Generates additional QSR video debugging information in the debout files.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.

System Variable Example

SET DEBUGQSR=TRUE

Command Line Example

N/A

Variable

DEBUGSCALES

Applications

IBER.EXE, IBERQS.EXE

Description

Provides additional debugging information for scale communication.

System Variable Example

SET DEBUGSCALES=TRUE

Command Line Example

N/A

Variable

DEBUGSCAN

Applications

EDCSVR.EXE

Description

Generates additional EDC terminal-scanning debugging information in the debout files.

System Variable Example

N/A

Command Line Example

EDCSVR.EXE /DEBUGSCAN

Variable

DEBUGSQLBUILD

Applications

GRIND.EXE, GRINDQ.EXE

Description

Generates additional SQL debugging information in the debout files.

This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.

System Variable Example

SET DEBUGSQLBUILD=TRUE

Command Line Example

GRIND.EXE /DEBUGSQLBUILD

Variable

DEBUGSV

Applications

VIDEOMX.DLL

Description

Generates additional Select video debugging information in the debout files.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.

System Variable Example

SET DEBUGSV=TRUE

Command Line Example

N/A

Variable

DEBUGTOUCH

Applications

IBER.EXE, IBERQS.EXE

Description

Generates a list of screen buttons and functions used in the terminal debout.� Refer to document AKBID3188 for more information.

System Variable Example

SET DEBUGTOUCH=TRUE

Command Line Example

N/A

Variable

DELEMP

Applications

ESP.EXE

Description

Deletes an employee from the schedule.

System Variable Example

N/A

Command Line Example

ESP.EXE /DELEMP 'employee ID'

Variable

DELETEVID

Applications

CTL.EXE, IBER.EXE, IBERQS.EXE

Description

DELETEVID deletes the VIDEO.LOG any time the Aloha application software FOH is refreshed.� It is used to decrease the time the Aloha application software needs to read a large VIDEO.LOG when starting.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.

System Variable Example

SET DELETEVID=TRUE

Command Line Example

N/A

Variable

DEV

Applications

IBER.EXE, IBERQS.EXE

Description

Used on a command line, /DEV suppresses many of the common data errors experienced when testing customer data by disabling many of the hardware peripherals.� Refer to document AKBID3289 for more information.

System Variable Example

N/A

Command Line Example

IBER.EXE /DEV

Variable

DOUBLECLICK

Applications

IBER.EXE, IBERQS.EXE

Description

DOUBLECLICK enables Windows to detect double-click ability while the Aloha application software FOH is running.� If this variable is not desired, completely remove it.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.

System Variable Example

DOUBLECLICK=TRUE

Command Line Example

N/A

Variable

EDCDIR

Applications

EDCSVR.EXE

Description

Sets the EDC folder name.� Refer to document AKBID1020.

System Variable Example

SET EDCDIR=<folder name>

Command Line Example

EDCSVR.EXE /EDCDIR <folder>

Variable

EDCSVR

Applications

EDC.EXE

Description

Specifies path to a remote EDCSVR.EXE.� Refer to document 1020.

System Variable Example

N/A

Command Line Example

EDC.EXE /EDCSVR <path>

Variable

EDCPATH

Applications

EDCSVR.EXE, IBER.EXE, IBERQS.EXE

Description

Sets the path to the EDC folder when multiple instances of EDC are running on the same file server.� Refer to document AKBID1020.

System Variable Example

SET EDCPATH=<path>

Command Line Example

IBER.EXE /EDCPATH <path>

Variable

EDITEMP

Applications

ESP.EXE

Description

Opens the scheduler to the edit screen for the specific employee.

System Variable Example

N/A

Command Line Example

ESP.EXE /EDITEMP 'employee ID'ESP

Variable

EGI

Applications

IBER.EXE, IBERQS.EXE

Description

Explicitly enables or disables the EGI, overriding the 64 megabytes of memory/16-bit color requirements.� Use this to enable the EGI in Aloha versions 5.2.5.x.� Refer to document AKBID1216.

System Variable Example

SET EGI=TRUE

Command Line Example

N/A

Variable

ENTERPRISE

Applications

DBUP2.EXE, DBUP3.EXE

Description

Upgrades an Enterprise site database.� Refer to document AKBID1067.

System Variable Example

N/A

Command Line Example

DBUP2.EXE /ENTERPRISE

Variable

EXIT

Applications

CTL.EXE

Description

Enables users to exit CTL.EXE.

System Variable Example

N/A

Command Line Example

CTL.EXE /EXIT

Variable

FORCECONVERTLOG

Applications

GRIND.EXE, GRINDQ.EXE

Description

Forces Grind to upgrade a transaction log in the DATA folder to the current version of the Aloha application software.

System Variable Example

N/A

Command Line Example

GRIND.EXE /FORCECONVERTLOG

Variable

FORCESECURITY

Applications

DBUP2.EXE, DBUP3.EXE

Description

Force security conversion in spite of any errors encountered.� Refer to document AKBID1016.

System Variable Example

N/A

Command Line Example

DBUP2.EXE /FORCESECURITY

Variable

FORCEUPGRADE

Applications

DBUP2.EXE, DBUP3.EXE

Description

Force the upgrade, ignoring the version check.� Refer to document AKBID1016.

System Variable Example

N/A

Command Line Example

DBUP2.EXE /FORCEUPGRADE

Variable

HOUSE

Applications

GRIND.EXE, GRINDQ.EXE

Description

Specifies a date range when rebuilding the House Account file.� This (re)posts transactions for the specified date range and will double-post transactions if they already exist.

System Variable Example

N/A

Command Line Example

GRIND.EXE /DATE DATA /HOUSE <yyyymmdd> <yyyymmdd>

Variable

IBERDIR

Applications

ALOHAMGR.EXE, ALOHASPY.EXE, CTL.EXE, CTLSVR.EXE, EDC.EXE, EDCSVR.EXE, ESP.EXE, GRIND.EXE, GRINDQ.EXE, IBER.EXE (NONROBUST mode only), IBERQS.EXE, MNT.EXE, DRSQL.EXE, EDOLDTM.EXE, FASTECH.DLL (System Variable only), LABSCHED.EXE, PAYRECON.EXE (System Variable only), REPRINT.EXE, RPT.EXE, TEAMSERV.EXE, DBUP2.EXE, DBUP3.EXE, USERTOOL.DLL (System Variable only), VIDEO.EXE

Description

IBERDIR defines the to the Aloha application software root folder name and location.� This is only required for BOH applications.� FOH application resolve the IBERDIR variable dynamically.

System Variable Example

SET IBERDIR=<path>

Command Line Example

C:\ALOHA\BIN\CTL.EXE /IBERDIR <path>

Variable

IBERROOT

Applications

IBER.EXE, IBERQS.EXE, EDCSVR.EXE

Description

Defines the Aloha application software folder name.� Used with ROBUST.

System Variable Example

SET IBERROOT=<folder>

Command Line Example

N/A

Variable

IBM4695MSR

Applications

IBER.EXE, IBERQS.EXE

Description

IBM4695MSR instructs the Aloha application software FOH to use the IBM 4695 integrated Magnetic Stripe Reader (MSR).� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.� Refer to document AKBID1032

System Variable Example

SET IBM4695MSR=TRUE

Command Line Example

N/A

Variable

IBMBAUD

Applications

VIDEOMX.DLL

Description

Sets the baud rate for the IBM video port.

System Variable Example

SET IBMBAUD=<baud rate>

Command Line Example

N/A

Variable

IBMMODE

Applications

VIDEOMX.DLL

Description

Sets the IBM video characters per line and number of lines on the monitor.� Mode 1 is 40x25, and Mode 3 is 80x25.

System Variable Example

SET IBMMODE=<1 or 3>

Command Line Example

N/A

Variable

IBMPORT

Applications

VIDEOMX.DLL

Description

Sets the serial port the IBM video is attached to.

System Variable Example

SET IBMPORT=<port>

Command Line Example

N/A

Variable

IBMVIDEOS

Applications

VIDEOMX.DLL

Description

Enumerates the number IBM video device(s) that are chained off the serial port.

System Variable Example

SET IBMVIDEOS=<1>,<2>,<3>

Command Line Example

N/A

Variable

INTERVAL

Applications

GRIND.EXE, GRINDQ.EXE

Description

Sets the time interval (in seconds) between recurrent grinds when used with RDB�s.

System Variable Example

N/A

Command Line Example

GRIND /INTERVAL <seconds>

Variable

KEY

Applications

DBFDIFF.EXE

Description

Designates the key field.

System Variable Example

N/A

Command Line Example

DBFDIFF /KEY <field>

Variable

LIQUORPLUDIGITS

Applications

IBER.EXE, IBERQS.EXE

Description

Used in conjunction with the Berg liquor dispensing system, LIQUORPLUDIGITS defines the number of digits used in a liquor item�s PLU number.� Refer to document AKBID1041.

System Variable Example

SET LIQUORPLUDIGITS=4

Command Line Example

N/A

Variable

LOCALACCOUNT

Applications

CTLSVR.EXE, EDCSVR.EXE

Description

Instructs the application to the use Windows local system account as the application's login if you are using 5.230 or higher with the Windows NT, Windows 2000 or Windows XP operating systems.� Used in place of the SNAME and SPWD environment variables.� Refer to document AKBID1019.

System Variable Example

N/A

Command Line Example

CTLSVR.EXE /SERVICE /LOCALACCOUNT

Variable

LOCALDIR

Applications

IBER.EXE, IBERQS.EXE

Description

LOCALDIR defines the location and name of the local Aloha application software folder.� Used with ROBUST.

System Variable Example

SET LOCALDIR=<path>

Command Line Example

IBER.EXE /LOCALDIR=<path>

Variable

LOCALREAD

Applications

IBER.EXE, IBERQS.EXE

Description

FOH reads from the LOCALDIR instead of the file server.� This decreases network traffic on large systems.� Do not enable the LOCALREAD variable on FOH terminals that are not master or server-capable, unless the terminal also acts as the Aloha application software's file server.� If a terminal is not master or server-capable, it does not synchronize the local DATA folder with the file server, so the information in the local DATA folder is not current.

System Variable Example

SET LOCALREAD=TRUE

Command Line Example

N/A

Variable

MASTERCAPABLE

Applications

IBER.EXE, IBERQS.EXE

Description

MASTERCAPABLE designates whether the local terminal can act as a master terminal if needed.� Used with ROBUST.

System Variable Example

SET MASTERCAPABLE=TRUE

Command Line Example

N/A

Variable

MASTERFILEDEBUG

Applications

IBER.EXE

Description

Generates additional MASTER file debugging information in the debout files.

Used only with SuperSites.

System Variable Example

SET MASTERFILEDEBUG=TRUE

Command Line Example

N/A

Variable

MASTERFILEFREQ

Applications

IBER.EXE

Description

Sets the frequency, in milliseconds, that the MASTER file is scanned.� This time interval has a minimum resolution of 55 milliseconds.� Used only with SuperSites.

System Variable Example

SET MASTERFILEFREQ=<number of milliseconds>

Command Line Example

N/A

Variable

MAXDEBOUTSIZE

Applications

ALOHASPY.EXE, CTLSVR.EXE

Description

Sets the maximum debout file size before CTLSVR.EXE renames the file and starts a new file.� Defaults to 8000000 (eight megabytes).� Size is in bytes.

System Variable Example

SET MAXDEBOUTSIZE=<number of bytes>

Command Line Example

N/A

Variable

MAXDEBOUTDAYS

Applications

ALOHASPY.EXE, CTLSVR.EXE

Description

Sets the number of days to keep a DEBBAK file before purging it.� Defaults to 30 (days).

System Variable Example

SET MAXDEBOUTDAYS=<number of days>

Command Line Example

N/A

Variable

MERGETRANSLOGS

Applications

GRIND.EXE, GRINDQ.EXE

Description

Merges the two transaction logs.� Refer to document AKBID1016.

System Variable Example

N/A

Command Line Example

GRIND.EXE /MERGETRANSLOGS <log 1> <log 2>

Variable

MMSCHEME

Applications

IBER.EXE, IBERQS.EXE

Description

Defines an alternate Cool Interface these.� Refer to document AKBID3186.

System Variable Example

SET MMSCHEME=BLUESTONE800

Command Line Example

N/A

Variable

MULTIDEBUG

Applications

CTL.EXE, CTLSVR.EXE

Description

Generates additional debugging information in the debout files.

Used only with SuperSites.

System Variable Example

N/A

Command Line Example

CTL.EXE /MULTIDEBUG

Variable

MULTILIQUORTAPTERM

Applications

IBER.EXE, IBERQS.EXE

Description

Used in conjunction with the Berg liquor dispensing system, MULTITERMINALTAPTERM defines the Aloha application software terminal ID as defined in the Berg software when multiple terminals are connected to a single drink dispenser.� Refer to document AKBID1041.

System Variable Example

SET MULTITERMINALTAPTERM=<terminal number>

Command Line Example

N/A

Variable

MULTISERVER

Applications

IBER.EXE, IBERQS.EXE

Description

Sets the Multi-Server network ID.� Used only with SuperSites.

System Variable Example

SET MULTISERVER=<compuer name>

Command Line Example

N/A

Variable

N

Applications

EDOLDTM.EXE

Description

Specifies the username.� Used with P.

System Variable Example

N/A

Command Line Example

EDOLDTM.EXE /N <username>

Variable

NCR_MSR_FIX

Applications

IBER.EXE, IBERQS.EXE

Description

Enables MSRs using some versions of the NCR OPOS drivers to function after a single swipe.� Refer to document AKBID3273.

System Variable Example

SET NCR_MSR_FIX=TRUE

Command Line Example

N/A

Variable

NODBFCOPY

Applications

DBUP2.EXE, DBUP3.EXE

Description

Forces the update of all DBF files instead of copying unchanged DBF files.� Refer to document AKBID1067.

System Variable Example

N/A

Command Line Example

DBUP2.EXE /NODBFCOPY

Variable

NODELETELOG

Applications

GRIND.EXE, GRINDQ.EXE

Description

In versions 5.230 and higher, Grind deletes any intermediate versions of the transaction log when it upgrades the transaction log.� If you enable this, Grind does not delete the intermediate versions of the log.

System Variable Example

N/A

Command Line Example

GRIND.EXE /NODELETELOG

Variable

NODEPOSIT

Applications

RPT.EXE

Description

Eliminates requests for and printing of deposits the Sales Report.

System Variable Example

N/A

Command Line Example

RPT.EXE /NODEPOSIT

Variable

NOFATALMSGBOX

Applications

IBER.EXE, IBERQS.EXE

Description

Suppresses FOH fatal message error prompts.� Instead of displaying the error, the FOH immediately shuts down.

System Variable Example

SET NOFATALMSGBOX=TRUE

Command Line Example

N/A

Variable

NOMUTEX

Applications

ALOHAMGR.EXE, CTL.EXE, CTLSVR.EXE, EDCSVR.EXE, GRIND.EXE, GRINDQ.EXE, TEAMSERV.EXE

Description

NOMUTEX enables multiple copies of the application to be active simultaneously.� Should only be used in environments where two concepts are using the same file server.� NOMUTEX stands for No-Mutual-Exclusivity.

System Variable Example

N/A

Command Line Example

C:\ALOHA\BIN\CTL.EXE /NOMUTEX

Variable

NONET

Applications

ALOHASPY.EXE, CTL.EXE, CTLSVR.EXE, IBERQS.EXE, VIDEO.EXE

Description

Forces non-network mode.� A file named NONET is the LOCALDIR or IBERDIR performs the same function.

System Variable Example

N/A

Command Line Example

CTL.EXE /NONETtC

Variable

NOROBUST

Applications

CTL.EXE, CTLSVR.EXE, IBER.EXE, VIDEO.EXE

Description

Disables robust mode.

System Variable Example

N/A

Command Line Example

CTL.EXE /NOROBUST

Variable

NOWINDOW

Applications

GRIND.EXE, GRINDQ.EXE

Description

Do not show the Grind window.

System Variable Example

N/A

Command Line Example

GRIND.EXE /NOWINDOW

Variable

NUM

Applications

RPT.EXE

Description

Sets the Labor Report number (1, 2 or 3).� Refer to document AKBID1038.

System Variable Example

N/A

Command Line Example

RPT.EXE /RA /NUM <report number>

Variable

NUMTERMS

Applications

IBER.EXE, IBERQS.EXE

Description

NUMTERMS defines the number of physical terminals attached to the Aloha application software.� Used with ROBUST.

System Variable Example

SET NUMTERMS=<number of terminals>

Command Line Example

N/A

Variable

NOTIPS

Applications

IBERQS.EXE

Description

Disables tips on a per-terminal basis.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.

System Variable Example

SET NOTIPS=TRUE

Command Line Example

N/A

Variable

P

Applications

EDOLDTM.EXE

Description

Specifies the password.� Used with N.

System Variable Example

N/A

Command Line Example

EDOLDTM.EXE /P <password>

Variable

PASSWORD

Applications

CTLSVR.EXE, EDCSVR.EXE

Description

Specifies the password with which the server will log in as if you are using 5.230 or higher with the Windows NT, Windows 2000 or Windows XP operating systems.� Used in conjunction with the ACCOUNTNAME environment variable.� Refer to document AKBID1019.

System Variable Example

N/A

Command Line Example

CTLSVR.EXE /SERVICE /PASSWORD <password>

Variable

PAYCHEX

Applications

GRIND.EXE, GRINDQ.EXE

Description

Creates the PAYCHEX export file for the previous pay period.

System Variable Example

N/A

Command Line Example

GRIND.EXE /PAYCHEX

Variable

PMSDIR

Applications

EDCSVR.EXE

Description

Defines the PMS folder name inside the IBERDIR.

System Variable Example

SET PMSDIR=<folder name>

Command Line Example

EDCSVR.EXE /PMSDIR <folder name>

Variable

PMSPATH

Applications

EDCSVR.EXE

Description

Defines the PMS folder path

System Variable Example

SET PMSPATH=<path>

Command Line Example

EDCSVR.EXE /PMSPATH <path>

Variable

PRD

Applications

RPT.EXE

Description

Defines the period (D for Daily, W for Weekly, and M for Monthly) for use with the Scheduled vs.� Actual Labor Report.� Refer to document AKBID1038.

System Variable Example

N/A

Command Line Example

RPT.EXE /RL /PRD <period>

Variable

PROHOSTDIR

Applications

IBER.EXE

Description

Defines the path to write ProHost32 message files.� Refer to document AKBID1039.

System Variable Example

SET PROHOSTDIR=<path>

Command Line Example

N/A

Variable

PVPORT

Applications

VIDEOMX.DLL

Description

Sets the serial port the Progressive Systems video is attached to.

System Variable Example

SET PVPORT=<port>

Command Line Example

N/A

Variable

QSRBAUD

Applications

VIDEOMX.DLL

Description

Sets the baud rate for the QSR video port.

System Variable Example

SET QSRBAUD=<baud rate>

Command Line Example

N/A

Variable

QSRMODE

Applications

VIDEOMX.DLL

Description

Sets the QSR video characters per line and number of lines on the monitor.� Mode 1 is 40x25, and Mode 3 is 80x25.

System Variable Example

SET QSRMODE=<1 or 3>

Command Line Example

N/A

Variable

QSRPORT

Applications

VIDEOMX.DLL

Description

Sets the serial port the QSR video is attached to.

System Variable Example

SET QSRPORT=<port>

Command Line Example

N/A

Variable

QSRVIDEO

Applications

VIDEOMX.DLL

Description

Selects the QSR video type, NATIVE or KDS.

System Variable Example

SET QSRVIDEO=<type>

Command Line Example

N/A

Variable

QSRVIDEOS

Applications

VIDEOMX.DLL

Description

Enumerates the number of QSR video device(s) that are chained off the serial port.

System Variable Example

SET QSRVIDEOS=<1>,<2>,<3>

Command Line Example

N/A

Variable

R

Applications

RPT.EXE

Description

R defines the report type.� Refer to document AKBID1038.

System Variable Example

N/A

Command Line Example

C:\ALOHA\BIN\RPT.EXE /R<report>

Variable

REBOOTNT

Applications

IBER.EXE, IBERQS.EXE

Description

Used in conjunction with AUTOEXIT and Windows NT, Windows 2000 or Windows XP, REBOOTNT instructs the Aloha application software FOH to reboot the local terminal when refreshed rather than only logging the user out.� Refer to document AKBID1005.

System Variable Example

SET REBOOTNT=TRUE

Command Line Example

N/A

Variable

RECORDDUPDBFRECORDS

Applications

ALOHAMGR.EXE

Description

Detects and reports (on-screen and in debout) when attempting to add duplicate records (determined by duplicate key field values).

System Variable Example

SET RECORDDUPDBFRECORDS=TRUE

Command Line Example

ALOHAMGR.EXE /RECORDDUPDBFRECORDS

Variable

REGRIND

Applications

GRIND.EXE, GRINDQ.EXE

Description

Forces re-Grind in SQLMODE.

System Variable Example

N/A

Command Line Example

GRIND.EXE /REGRIND

Variable

REGSERVER

Applications

ALOHASPY.EXE, CESSVR.EXE, CTLSVR.EXE, EDCSVR.EXE

Description

Registers the application to not run as a service.� Refer to document AKBID1019.

System Variable Example

N/A

Command Line Example

CESSVR.EXE /REGSERVER

Variable

REMOTE

Applications

ALOHAMGR.EXE, CTL.EXE, CTLSVR.EXE

Description

REMOTE enables CTL.EXE to function on a separate computer than the file server without looking for the Aloha software key.� Refer to document AKBID1040.

System Variable Example

REMOTECTL=TRUE

Command Line Example

C:\ALOHA\BIN\CTL.EXE /REMOTE

Variable

REPORTMODE

Applications

EDC.EXE

Description

Enables 'Reports Only' mode.� All other menu items are not displayed.� Refer to document AKBID1050.

System Variable Example

N/A

Command Line Example

EDC.EXE /REPORTMODE

Variable

ROBUST

Applications

CTL.EXE, CTLSVR.EXE, GRIND.EXE, GRINDQ.EXE, IBER.EXE, IBERQS.EXE, VIDEO.EXE

Description

Enables fault tolerance capabilities.� Refer to document AKBID1107.

System Variable Example

SET ROBUST=TRUE

Command Line Example

IBER.EXE /ROBUST

Variable

RPTAUDIT

Applications

REPRINT.EXE

Description

Initiates an Audit Report.

System Variable Example

N/A

Command Line Example

REPRINT.EXE /RPTAUDIT

Variable

RPTXFERS

Applications

REPRINT.EXE

Description

Initiates a Transfer Report.

System Variable Example

N/A

Command Line Example

REPRINT.EXE /RPTXFERS

Variable

S

Applications

EDCSVR.EXE

Description

Enables silent-mode

System Variable Example

N/A

Command Line Example

EDCSVR.EXE /S

Variable

SCANRESTRICT

Applications

EDCSVR.EXE

Description

Restricts EDC file scanning to specific terminal

System Variable Example

N/A

Command Line Example

EDCSVR.EXE /SCANRESTRICT <terminal name>

Variable

SECSVR

Applications

EDC.EXE

Description

Specifies the User Security server, usually the POS file server.� Refer to document AKBID1050.

System Variable Example

N/A

Command Line Example

EDC.EXE /SECSVR <computer name>

Variable

SECSVRPATH

Applications

EDC.EXE

Description

Sets the IBERDIR on the User Security server.� This variables uses the path as if set from the file server itself.� For example, if the IBERDIR on the POS file server is D:\ALOHA, this setting is D:\ALOHA, even if used remotely.� Remote use requires SECSVR.� Refer to document AKBID1050.

System Variable Example

N/A

Command Line Example

EDC.EXE /SECSVRPATH <iberdir>

Variable

SERVER

Applications

CTL.EXE, CTLSVR.EXE, IBER.EXE, IBERQS.EXE, VIDEO.EXE

Description

SERVER defines the Aloha application software file server network name.� Used with ROBUST.

System Variable Example

SET SERVER=<computer name>

Command Line Example

N/A

Variable

SERVERCAPABLE

Applications

IBER.EXE, IBERQS.EXE

Description

SERVERCAPABLE defines whether the local terminal can act as file server if needed.

System Variable Example

SET SERVERCAPABLE=TRUE

Command Line Example

N/A

Variable

SERVICE

Applications

ALOHASPY.EXE, CESSVR.EXE, CTLSVR.EXE, EDCSVR.EXE

Description

Registers the application to run as a service.� Refer to document AKBID1019.

System Variable Example

N/A

Command Line Example

CTLSVR.EXE /SERVICE

Variable

SNAME

Applications

CTLSVR.EXE, EDCSVR.EXE

Description

Specifies the encrypted user name listed in the registration batch file created by the Aloha setup application.� This is the user name with which the server will log in as if you are using 5.230 or higher with the Windows NT, Windows 2000 or Windows XP operating systems.� Used in conjunction with the SPWD environment variable.� Refer to document AKBID1019.

System Variable Example

N/A

Command Line Example

CTLSVR.EXE /SERVICE /SNAME <user name>

Variable

SPWD

Applications

CTLSVR.EXE, EDCSVR.EXE

Description

Specifies the encrypted password listed in the registration batch file created by the Aloha setup application.� This is the password with which the server will log in as if you are using 5.230 or higher with the Windows NT, Windows 2000 or Windows XP operating systems.� Used in conjunction with the SNAME environment variable.� Refer to document AKBID1019.

System Variable Example

N/A

Command Line Example

CTLSVR.EXE /SERVICE /SPWD <password>

Variable

SQLMODE

Applications

ALOHAMGR.EXE, CTL.EXE, CTLSVR.EXE, GRIND.EXE, GRINDQ.EXE, MNT.EXE, EDOLDTM.EXE, REPRINT.EXE, RPT.EXE

Description

SQLMODE instructs the Aloha application software to use an RDB database.

System Variable Example

SET SQLMODE=TRUE

Command Line Example

MNT.EXE /SQLMODE

Variable

STOPLOGO

Applications

IBER.EXE, IBERQS.EXE

Description

Disables the floating logo so it is stationary in the middle of the screen.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.

System Variable Example

SET STOPLOGO=TRUE

Command Line Example

N/A

Variable

STOREDIR

Applications

GRIND.EXE, GRINDQ.EXE

Description

Sets the Store folder in SQLMODE.

System Variable Example

N/A

Command Line Example

GRIND.EXE /STOREDIR <path>UNCPathUNnnnggd

Variable

STOREID

Applications

IBER.EXE, IBERQS.EXE

Description

Defines Store number.� Used with SQLMODE.

System Variable Example

SET STOREID=<ID number>

Command Line Example

N/A

Variable

STORENUM

Applications

GRIND.EXE, GRINDQ.EXE, REPRINT.EXE

Description

Defines Store number.� Used with SQLMODE.

System Variable Example

N/A

Command Line Example

GRIND.EXE /STORENUM <ID number>

Variable

SUPPRESSTIPLINE

Applications

IBER.EXE, IBERQS.EXE

Description

Disables the tip line on receipts (not credit card vouchers).

System Variable Example

SET SUPPRESSTIPLINE=TRUE

Command Line Example

N/A

Variable

SVBAUD

Applications

VIDEOMX.DLL

Description

Sets the baud rate for the Select video port.

System Variable Example

SET SVBAUD=<baud rate>

Command Line Example

N/A

Variable

SVIDEOS

Applications

VIDEOMX.DLL

Description

Enumerates the number of Select video device(s) that are chained off the serial port.

System Variable Example

SET SVIDEOS=<1>,<2>,<3>

Command Line Example

N/A

Variable

SVMODE

Applications

VIDEOMX.DLL

Description

Sets the Select video characters per line and number of lines on the monitor.� Mode 1 is 40x25, and Mode 3 is 80x25.

System Variable Example

SET SVMODE=<1 or 3>

Command Line Example

N/A

Variable

SVPORT

Applications

VIDEOMX.DLL

Description

Sets the serial port the Select video is attached to.

System Variable Example

SET SVPORT=<port>

Command Line Example

N/A

Variable

TERM

Applications

IBER.EXE, IBERQS.EXE

Description

TERM defines the Aloha application software order entry terminal ID number as designated in the BOH.

System Variable Example

SET TERM=<terminal number>

Command Line Example

IBER.EXE TERM <terminal number>

Variable

TERMSTR

Applications

CTL.EXE, CTLSVR.EXE, IBER.EXE, IBERQS.EXE, EDCSVR.EXE

Description

TERMSTR defines the setting used to override the default naming convention for terminals that must be used on all Aloha application software terminals.� For example, if TERMSTR is set to TERM, then terminals must be named TERM1, TERM2, etc.

System Variable Example

SET TERMSTR=<name>

Command Line Example

N/A

Variable

TIMING

Applications

GRIND.EXE, GRINDQ.EXE

Description

Generates extra debugging information in the debout files for Grind timing.

System Variable Example

N/A

Command Line Example

GRIND.EXE /TIMING

Variable

TYPE

Applications

RPT.EXE

Description

Defines the period (E for Employee, C for Job Code, and G for Job Group) for use with the Scheduled vs.� Actual Labor Report.� Refer to document AKBID1038.

System Variable Example

N/A

Command Line Example

RPT.EXE /RL /TYPE <type>

Variable

UNREGSERVER

Applications

ALOHASPY.EXE, CESSVR.EXE, CTLSVR.EXE, EDCSVR.EXE

Description

Unregisters the application or removes if from service status.� Refer to document AKBID1019.

System Variable Example

N/A

Command Line Example

CESSVR.EXE /UNREGSERVER

Variable

USEFULLMEMBERMAGCARD

Applications

IBER.EXE

Description

This instructs IBER.EXE to parse the entire alphanumerical ID on a member ID card used with the Membership Interface.� If this is not enabled, then IBER.EXE only parses the numerical characters in the ID.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.

System Variable Example

SET USEFULLMEMBERMAGCARD =TRUE

Command Line Example

N/A

Variable

USEONLY5DIGITS

Applications

IBER.EXE

Description

This instructs IBER.EXE to parse only the first five digits of the number on a member ID card used with the Membership Interface.� Alphabetical characters are ignored.� If the trimmed digits are not zeros, then you receive an 'Invalid Number' error.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.

System Variable Example

SET USEONLY5DIGITS=TRUE

Command Line Example

N/A

Variable

USESLEEPING

Applications

GRIND.EXE, GRINDQ.EXE

Description

Grind waits for a signal from CTLSVR.EXE to activate instead of activating on timer basis.� Used only with SQLMODE.

System Variable Example

N/A

Command Line Example

GRIND.EXE /USESLEEPING

Variable

VERBOSE

Applications

DBUP2.EXE, DBUP3.EXE

Description

Messages are displayed in the command prompt window.� Refer to document AKBID1067.

System Variable Example

N/A

Command Line Example

DBUP2.EXE /VERBOSE

Variable

VERIFONEONIBMPORT

Applications

IBERQS.EXE

Description

Enables you to connect a VeriFone PIN pad to 'Port 4' on an IBM 4695 POS terminal.� Refer to document AKBID3292.

System Variable Example

SET VERIFONEONIBMPORT=TRUE

Command Line Example

N/A

Variable

VIDEO

Applications

VIDEO.EXE

Description

Identifies the video device ID.

System Variable Example

SET VIDEO=<device ID>

Command Line Example

VIDEO.EXE /VIDEO <device ID>

Variable

VIDEOHEIGHT

Applications

VIDEO.EXE

Description

The height (in pixels) of the window to display the video information.

System Variable Example

N/A

Command Line Example

VIDEO.EXE /VIDEOHEIGHT <pixels>

Variable

VIDEOWIDTH

Applications

VIDEO.EXE

Description

The width (in pixels) of the window to display the video information.

System Variable Example

N/A

Command Line Example

VIDEO.EXE /VIDEOWIDTH <pixels>

Variable

VIDEOX

Applications

VIDEO.EXE

Description

Specifies the left coordinate for VIDEO.EXE (in pixels).

System Variable Example

N/A

Command Line Example

VIDEO.EXE /VIDEOX <pixel number>

Variable

VIDEOY

Applications

VIDEO.EXE

Description

Specifies the top coordinate for VIDEO.EXE (in pixels).

System Variable Example

N/A

Command Line Example

VIDEO.EXE /VIDEOY <pixel number>

Extended Information

No Information.

Caveats

No Information.

============================================================================

See also:

AKBID1001 Configuring the CALIBRATE Variable on Aloha Terminals

AKBID1005 Microsoft Windows Automatic Log In

AKBID1016 Grind Process and Errors

AKBID1019 Manually Registering and Un-registering Aloha Applications

AKBID1020 EDC Process

AKBID1032 IBM4695 POS Terminal

AKBID1038 Report Command Line Parameters

AKBID1039 ProHost32

AKBID1040 Remote Control and Maintenance

AKBID1041 Multiple Terminal Berg Tap Setup

AKBID1050 Remote EDC

AKBID1067 DBUP.EXE

AKBID1097 Aloha Application Software Font Name and Size Variables

AKBID1107 Aloha Application Software Fault Tolerance Functionality

AKBID1108 Using the Aloha application software Crystal Report Interface

AKBID1165 FOH Screen Resolution Settings

AKBID1204 Default Aloha System Environment Variable Placement

AKBID1216 Enabling and Configuring FOH Enhanced Graphical Interface

AKBID3186 Cool Interface by Terminal

AKBID3188 Logging Screen Touches for Debugging

AKBID3206 Balancing Reports Using /BALANCE

AKBID3228 Setting a Custom Resolution in Panel Editor

AKBID3273 NCR OPOS MSR Stops Working After First Swipe

AKBID3289 Using /DEV to Suppress Customer Data Errors During Testing

AKBID3292 Configuring a VeriFone PIN Pad on 'Port 4' on an IBM 4695

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1010 mx

Windows 9x VNETBIOS.VXD Patch

Windows 9x VNETBIOS.VXD Patch

============================================================================

AKBID1011

Created: 21 January 2000

Updated: 19 February 2003

Reviewed: 8 March 2004

Microsoft Windows Versions: Windows 95, Windows 98, Windows Me

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.8x � 5.3.x

Subject: Windows 9x VNETBIOS.VXD Patch

============================================================================

Summary

ALOHA^� application software installations with five or more Front-of-House (FOH) terminals using either the Microsoft^� Windows^� 95, Windows 98, or Windows Millennium Edition (Me) operating system (OS) might experience network problems that are attributed to the VNETBIOS.VXD virtual device running out of internal storage for network control blocks (NCB), but you can correct this with a patch available from Aloha Technologies.

This document applies to all network protocols supported by NetBIOS, which includes NetBEUI, TCP/IP, and IPX/SPX.

Information

Symptoms

There are four major symptoms of the VNETBIOS.VXD problem:

The master terminal's Debugging-Output-File (debout) contains '0x22' errors.

Any of the FOH terminals debouts contain 'Network error: Sent bundle id xxx != expected id yyy' errors.

The master terminal's debout contains '0xFF' errors.

Any other mysterious communication problems between terminals.

Resolution

Perform the following to enable the VNETBIOS.VXD patch:

Copy the VNETBIOS.VXD file from the \MISC\WIN95 folder on the Aloha Application Software Software Installation CD to the Windows SYSTEM folder on each Windows 95, Windows 98, or Windows Me FOH terminal.

Do not use any other version of VNETBIOS.VXD, including newer versions.� The correct version is dated 7/10/1998 (or 7/9/1998 on some 5.2x Aloha Installation CDs) and is 27 kilobytes in size.

Add NUMHCBS=xxx to the [386Enh] section of the SYSTEM.INI file found in the Windows folder on each terminal, where xxx should be equal to or higher than 80.� In general, Aloha Technologies uses 100 when staging terminals, and this is a satisfactory number in all but rare cases.� You should not need to go higher than four times the number of terminals, and you should not exceed 200.

Future Network Configuration Updates

If changes are made to the network configuration following the placement of the VNETBIOS.VXD patch in the Windows SYSTEM folder, Windows may attempt to overwrite the file with the original version that came with Windows.� In some cases, Windows asks the user for permission to overwrite the file, but in other cases, Windows overwrites the file without requesting permission from the user.

By placing an updated VNETBIOS.VXD file in the same folder as the Windows installation (.CAB) files, Windows no longer attempts to overwrite the patch residing in the Windows SYSTEM folder since the existing VNETBIOS.VXD file matches the version of the file residing in the Windows installation files.

Extended Information

When Aloha Technologies stages terminals, this patch is added to all Windows 95, Windows 98, and Windows Me terminals regardless of the system's size.� This helps promote consistency and ensure the problem will not surface on our client's systems.

Caveats

Do not use any other version of VNETBIOS.VXD, including newer versions.� The correct version is dated 7/10/1998 and is 27 kilobytes in size.

============================================================================

See also:

Microsoft Knowledge Base Article ID: Q169540

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1011 numhcbs vnetbios

Aloha Application Software Utility Description and Usage

Aloha Application Software Utility Description and Usage

============================================================================

AKBID1012

Created: 17 January 2000

Updated: 18 December 2003

Reviewed: 18 December 2003

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

Subject: Aloha Utility Description and Usage

============================================================================

Summary

Aloha Technologies has created several utilities to help support the ALOHA^� application software.� This document lists and explains the usage of each utility.

Information

These utilities reside on the Aloha Technologies FTP site as compressed (.ZIP) files.� You can download and distribute them for Aloha support needs.

ALOHA_SYMBOL_MSR_ARM.ZIP

ALOHA_SYMBOL_MSR_ARM.EXE is designed for use with a Symbol Technologies Microsoft^� Windows^� CE-based handheld device that uses a StrongARM processor.� This utility, specifically tested with a Symbol Technologies PPT2846 handheld and a Symbol Technologies MSR3006 Magnetic-Stripe-Reader (MSR), converts MSR input from RS232 to keyboard input.� This enables communication with the Aloha application software Front-of-House (FOH) if you are using Windows Terminal Server (refer to document AKBID1203).

To enable this, just place ALOHA_SYMBOL_MSR_ARM.EXE in the Windows StartUp folder on the handheld device and configure the terminal's MSR as a keyboard MSR in the Aloha application software.

Usage: ALOHA_SYMBOL_MSR_ARM.EXE

Options: None

CARD.EXE

CARD.EXE captures all keyboard-based MSR and scanner input, including actual hexadecimal and decimal representations of the characters, which is useful for checking non-printing characters.

Usage: CARD.EXE [options]

Options:

> CARD.TXT�� Writes the data to CARD.TXT for future reference.

CHECKNO2.EXE

The Aloha application software sometimes refers to a check using the check number as used in the transaction log (TRANS.LOG) rather than the check number displayed on most reports and on the check itself.� CHECKNO2.EXE provides a method of converting the check number from the version used in the TRANS.LOG to the version displayed on the check, and vice versa.� CHECKNO2.EXE works with Aloha versions 4.0x and higher.

Usage: CHECK2.EXE <check number from the TRANS.LOG or the guest check>

Options:

/?�� Displays help information.

CLEARMAG.EXE

CLEARMAG.EXE enabled you to clear the magnetic stripe passwords for all employees.� After making a backup of the current EMP.DBF, close ALOHAMGR.EXE (Aloha Manager), copy the EMP.DBF from the NEWDATA folder to a temporary folder where CLEARMAG.EXE resides, and run CLEARMAG.EXE.� The target EMP.DBF must reside in the same folder as CLEARMAG.EXE.� Once the process is complete, replace the EMP.DBF in the NEWDATA folder with the new version containing the cleared passwords, and refresh the data.

This utility will clear the magnetic stripe passwords for all employees listed in the EMP.DBF.

Usage: CLEARMAG.EXE [options]

Options:

/?�� Displays help information.

CLOSEAPP.EXE

CLOSEAPP.EXE closes a window or Windows file from a command line or batch file.

Usage: CLOSEAPP.EXE [options] <window caption string>

Options:

/CLOSE�� Enables a graceful exit similar to using File/Exit.

/QUIT�� Forces ungraceful exit similar to using <Ctrl><Alt><Del> to end a task.

/?�� Displays help information.

<window caption string> is the exact caption found in the upper left corner of a window.� You can use the first several characters instead of the entire caption, but you should use enough letters to differentiate the target from other open applications.� For example, 'CLOSEAPP.EXE /CLOSE Aloha ED' will close Aloha EDC 4.235, Aloha EDC 4.246 and so on.

COMBITM.EXE

COMBITM.EXE combines two Aloha application software item files (ITM.DBF) in to a single DBF file labeled COMBINED.DBF.� You can use this utility on other Aloha application software database files that contain an ID field.

DBFUTIL.EXE performs the same functions as COMBITM.EXE, plus many others.� Refer to document AKBID1196 for more information.

Usage: COMBITM.EXE <file1>.DBF <file2>.DBF

Options:

/?�� Displays help information.

DATEDAY.EXE

DATEDAY.EXE enables you to run an application or process in Winhook only on specific days of the month.

DATEDAY.EXE creates a file in the %IBERDIR%\TMP folder labeled by the day of the month in regards to the system date (not the Aloha application software DOB).

File examples: DATEDAY.1, DATEDAY.9, DATEDAY.11, DATEDAY.21, and DATEDAY.31

Usage: DATEDAY.EXE

Options:

/?�� Displays help information.

DAYWEEK.EXE

DAYWEEK.EXE enables you to run an application or process in Winhook only on specific days of the week.

DAYWEEK.EXE creates a file in the %IBERDIR%\TMP folder labeled by the day of the week in regards to the system date (not the Aloha application software DOB).

File examples: SUN.DAY, MON.DAY, TUES.DAY, WEDNES.DAY, THURS.DAY, FRI.DAY, and SATUR.DAY

Usage: DAYWEEK.EXE

Options:

/?�� Displays help information.

DBF2TEXT.EXE

DBF2TEXT.EXE enables you to convert a .DBF-based database file to a comma-separated-value (CSV) text file.� You can also accomplish this using DBFUTIL.EXE (refer to document AKBID1196).

Usage: DBF2TEXT.EXE <input>.DBF <output>.TXT

Options:

/?�� Displays help information.

DBFUTIL.EXE

DBFUTIL.EXE is a multi-purpose utility Refer to document AKBID1196 for more information on DBFUTIL.EXE.

EDCRENAM.EXE

EDCRENAM.EXE enables you to rename a group of non-sequentially numbered EDC TXN files to sequentially numbered EDC TXN files.�

For example if you have TXN00003, TXN00005, and TXN00010, run EDCRENAM.EXE in the same folder as the TXN files and EDCRENAM.EXE renames the files to TXN00001, TXN00002, TXN00003.

EDCRENAM.EXE only renames EDC TXN files.� It does not ensure that EDC properly reads and processes the information held in the TXN files.

Usage: EDCRENAM.EXE

Options: None

FILEINCREMENTER.EXE

FILEINCREMENTER.EXE enables you to create flag files based on an incrementing number, starting with a base number and continuing to a maximum number.� You can utilize these flag files in batch files (for example, with the IF EXIST command).

The first time you run FILEINCREMENTER.EXE, it creates a file in the local folder based on the minimum number.� Further instances of FILEINCREMENTER.EXE will increment the number by one until it reaches the maximum number, at which it will revert back to the minimum number.� If you delete the flag file, FILEINCREMENTER.EXE will start again with the minimum number.

Usage: FILEINCREMENTER.EXE <prefix> <min> <max>

<prefix> is the name string applied to the generated files.� For example, a prefix of TERM will yield files labeled TERM1, TERM2, and so on.

<min> is the starting point for incrementing numbers.

<max> is the highest available increment.� Further increments beyond this number restart with the minimum number.

Options:

/?�� Displays help information.

FIXLOG.EXE

FIXLOG.EXE repairs a corrupt Aloha TRANS.LOG.� The repaired transaction log is labeled FIXED.LOG.� Always stop or shut down the FOH before using FIXLOG.EXE.

There are multiple versions of FIXLOG.EXE.� Each version is compatible with specific versions of the Aloha application software.

FIXLOG.EXE repairs Aloha versions 3.6xx - 3.949

FIXLOG2.EXE repairs Aloha versions 3.950 - 4.111

FIXLOG3.EXE repairs Aloha versions 4.112 - 4.230

FIXLOG4.EXE repairs Aloha versions 4.231 - 4.4xx

FIXLOG4327.EXE repairs Aloha versions 5.0xx

FIXLOG5200.EXE repairs Aloha versions 5.2xx � 5.2.4.x

FIXLOG5.2.5.72.EXE repairs Aloha versions 5.2.5.x � 5.3.x

Usage: FIXLOG.EXE <filename>

Options:

/?�� Displays help information.

FIXLOG.EXE can create an output file that includes any TRANS.LOG errors that are found as well as diagnostic information.� Create this file by adding '> FIXLOG.TXT' to the end of the command line.� For example:

FIXLOG.EXE TRANS.LOG > FIXLOG.TXT

The information included in this output file may help resolve TRANS.LOG issues not reparable with FIXLOG.EXE such as database configuration.

HASPLPTPORT.EXE

The HASPLPTPORT.EXE utility that is available in the \MISC\HASP folder on the Aloha Installation CD, and it is used to view, configure, or remove the parallel (LPT) port number used by the HASP^� security key in the Windows registry.� Refer to document AKBID1220 for more information.

Usage: HASPLPTPORT.EXE [options]

Options:

/G�� Displays the current LPT port number defined in the Windows registry.

0, 1, or 2�� Defines the LPT port to which the HASP security key is attached.� '0' instructs the Aloha application software to search all of the LPT ports, '1' instructs the Aloha application software to use only LPT1, and '2' instructs the Aloha application software to use only LPT2.

/R�� Removes the LPT port definition from the Windows registry.

If you assign the HASP security key to LPT1 in the Windows registry using HASPLPTPORT.EXE but physically attach the HASP security key to LPT2 (or vice versa), then the Aloha application software will not locate the key and display a message stating 'Security key not found'.

HDSPACE.EXE

HDSPACE.EXE creates a LOWSPACE file in the working folder if the unused hard drive space is below the amount defined in the command line for HDSPACE.EXE.� You must use HDSPACE.EXE from a command line inside Windows.� Use HDSPACED.EXE (also in this document) for a MS-DOS^� prompt outside of Windows, such as the AUTOEXEC.BAT.

Usage: HDSPACE.EXE <drive> <warning point>

<drive> is the local or mapped hard drive to verify the unused hard drive space.

<warning point> is the minimum amount of unused space available before HDSPACE.EXE creates the LOWSPACE file.

Options:

/?�� Displays help information.

Refer to document AKBID1146 for more information.

HDSPACED.EXE

HDSPACED.EXE creates a LOWSPACE file in the working folder if the unused hard drive space is below the amount defined in the command line for HDSPACED.EXE.� Use HDSPACED.EXE for a MS-DOS prompt outside of Windows, such as the AUTOEXEC.BAT.� You must use HDSPACE.EXE (also in this document) from a command line inside Windows.�

Since HDSPACED.EXE is designed for use in a MS-DOS environment, it conforms to the two gigabyte MS-DOS hard drive size limit.� The displayed hard drive size does not exceed two gigabytes, but HDSPACED.EXE still functions properly on a hard drive over two gigabytes as long as the hard drive space warning point is less than two gigabytes.

Usage: HDSPACED.EXE <drive> <warning point>

<drive> is the local or mapped hard drive to verify the unused hard drive space.

<warning point> is the minimum amount of unused space available before HDSPACED.EXE creates the LOWSPACE file.

Options:

/?�� Displays help information.

Refer to document AKBID1146 for more information.

INDEX.EXE

Creates indexes of Aloha .DBF files.� It is particularly useful when creating and viewing reports with Crystal Reports.�

Usage: INDEX.EXE <filename> <indexkey> <indexname>

INDEX.EXE does not require file extensions in the command line.� For example, use 'INDEX.EXE ITM ID ITM' instead of 'INDEX ITM.DBF ID ITM.NTX'.

Options:

/?�� Displays help information.

ISCRIPT.EXE

ISCRIPT.EXE enables you to create a running script of touch screen, mouse, and keyboard activity that can be repeated a set number of times or an unlimited number of times.� ISCRIPT.EXE uses command line options and a graphical-user-interface (GUI).

Usage: ISCRIPT.EXE /G /E /R <value> /S <file name>

Options:

/G�� Ghost mode.� Hides the GUI while a script is replayed.

/E�� Automatically exits ISCRIPT.EXE if /R is used.

/R�� Number of times to automatically repeat (1 � 9999 times).

/S�� Script file name.�

/?�� Displays help information.

Script files are text based files and generally use a .TXT file extension (for example, SCRIPT.TXT, ISCRIPT9.TXT).�

If /S is used without a file name, ISCRIPT.EXE defaults to SCRIPT.TXT in the Windows TEMP folder.�

If the script file does not exist, a new file is created.� Contents are added to the file when the START button is pressed.� Pressing the START button always clears the .TXT file and creates a new one.

If the script file already exists, it is loaded into ISCRIPT.EXE for use by pressing PLAY or REPLAY.

GUI Buttons:

START�� Starts recording a script.

STOP�� Ends the recording mode.

PLAY�� Plays the recorded script once.

REPLAY�� Prompts for the number of replays and repeats the recorded script.

KEYRENUM.EXE

KEYRENUM.EXE enables you to automate the process of changing the HASP security key activation codes in the ALOHA.INI in dated folders to match the HASP security key activation codes contained in the %IBERDIR%\DATA\ALOHA.INI.

You must run KEYRENUM.EXE from the Aloha application software BIN folder.

Debugging information is outputted to the DEBOUT.KEY file in the Aloha application software TMP folder.

Usage: KEYRENUM.EXE /IBERDIR <IBERDIR path> /SS /TERM <terminal number>

Options:

/?�� Displays help information.

/IBERDIR�� Defines the path to the Aloha application software folder.� This is not required if the IBERDIR path is already declared in the Windows system environment variables.

/SS�� Used in SuperSites, updates all of the dated folders on all of the FOH terminals.

/TERM�� Used in SuperSites, updated only the dated folders on a specific FOH terminal.

KILLSVR.EXE

KILLSVR.EXE is available in the Aloha application software BIN folder at any site where version 5.0x or higher is installed.� It is not available on the Aloha Technologies FTP site.

KILLSVR.EXE is designed to enable you to stop Aloha application software services on a file server running Windows 95, Windows 98, or Windows Millennium Edition (Me), which do not contain a native ability to perform this task without restarting the computer.

KILLSVR.EXE is not designed for use with Windows NT^�, Windows 2000, or Windows XP, since you can start and top services via the Services GUI or the NET START or NET STOP command lines in those operating systems.��

Usage: KILLSVR.EXE �H �L �R <file name> �K <process name>

Options:

-H�� Displays help information

-L�� Lists current processes that are running

-R �� Tells if the specified file is running as a process

-K�� Stops (kills) a the specified process

NETINFO.EXE

NETINFO.EXE assists in finding an open TCP socket port for use with AlohaSpy and Fiscal Manager.� Refer to document AKBID3187 for more information.

Usage: NETINFO.EXE

Options:

None

POSPRINT.EXE

POSPRINT.EXE enables you to print a text file to any Aloha application software printer.� Since this utility uses the Component Object Module (COM) interface to print files, it requires Aloha application software version 5.230 or higher and you have to enable the COM interface in Aloha Manager/Maintenance/Store Settings/Interfaces/Use FOH COM Interface.

Usage: POSPRINT.EXE <printer ID> <text file>

<printer ID> is the printer ID, as defined in the Aloha application software.

<text file> is the path and name of the text file.

Options:

/?�� Displays help information.

REBOOT30.EXE

REBOOT30.EXE forces a Windows to restart after a 30-second wait.� This utility can be used for scheduled restarts or, if placed in the Windows StartUp folder, can be used for stress-testing computers with multiple restarts.

Usage: REBOOT30.EXE

Options:

None

SETUPSYS.EXE

Some system files (in the Windows SYSTEM32 folder) used by the Aloha application software are shared with other Windows components, so users may not be able to manually overwrite them while using Windows NT, Windows 2000, or Windows XP.�

SETUPSYS.EXE overcomes this by restarting the system, and replacing the files before they are used by other components.� The system files are replaced only if current versions of the files do not already exist or the replacement versions are newer than current versions.

SETUPSYS.EXE only updates files to the Windows SYSTEM32 folder.

Perform the following to use SETUPSYS.EXE:

1.        Place all of the new system files in an empty folder on the same partition as the Windows folder.

2.        Open SETUPSYS.EXE.

3.        Specify the folder where the new system files reside.� If you use the 'Browse' function, you are required to select a file inside of the folder where the new system files reside.� SETUPSYS.EXE updates all of the files in the folder, regardless if you select a specific file or not.

4.        Click Update.

5.        Restart the system.

SETUPSYS.EXE writes debugging information to C:\DEBOUT.SET.

Usage: SETUPSYS.EXE

Options:

None

SHOWCLRn.EXE

SHOWCLR.EXE outputs the cleared items or No Sale transactions in an Aloha application software TRANS.LOG.� Cleared items are unordered items that were cleared before they were ordered, so they do not count as a void.�

This utility does not reflect time zone differences if you are in an international time zone or a time zone that does not recognize daylight savings time.� In this case, it displays Pacific Time.

There are multiple versions of SHOWCLR.EXE.� Each version is compatible with specific versions of Aloha.

SHOWCLR50.EXE views Aloha versions 5.0x.

SHOWCLR52.EXE views Aloha versions 5.2x (the Audit report in Aloha versions 5.2x and higher also has an option to display a list of cleared items).

The default output is Date<tab>Hour<tab>Minute<tab>Employee<tab>Item<tab>Price.

Usage: SHOWCLR.EXE [/NOSALE] [/SUMMARY] <TRANS.LOG> > SHOWCLR.TXT

Options:

/?�� Displays help information.

/NOSALE�� Displays No Sale transactions rather than cleared items.

/SUMMARY�� If used with /NOSALE, it outputs a No Sale summary by manager in the format of Manager<tab>Count; otherwise it outputs a cleared item summary by employee in the format of Employee<tab>Count<tab>Total.

SPLITSTL.EXE

SPLITSTL.EXE splits an EDC .STL file back into its original .TXN files.� Be sure to remove the .TXN file (usually the last .TXN) that corresponds with the original settlement once this utility is used on an .STL file.

Usage: SPLITSTL.EXE <settlement-filename>

Options:

/?�� Displays help information.

SSDELBTN.EXE

SuperSite BTN.DBF files may grow very large since they contain QuickService button information for a large number of panels.� Since SuperSite dated folders are stored on the terminals, multiple copies of the large BTN.DBF files needlessly use the limited disk space.

GRINDQ.EXE and REPRINTQ.EXE require the BTN.DBF files resides in the dated folder, but they do not use the file's contents.� For this reason, the file can not be deleted.� Instead, SSDELBTN.EXE replaces it with a blank copy of the file.

Since GRINDQ.EXE and REPRINTQ.EXE versions 5.0x and higher no longer read the BTN.DBF file and IBERQS.EXE (and IBER.EXE) versions 5.2x and higher enable you to run FOHHOOK.BAT (refer to document AKIBID1171) to delete the BTN.DBF from the dated folder, this utility has limited value in current versions of the Aloha application software.

SSDELBTN.EXE checks for the previous day's dated folder on the local terminal.� If it exists, the BTN.DBF is deleted from the dated subdirectory and replaced with a smaller blank copy in the BIN folder.

SSDELBTN.EXE uses the system date, not the Aloha application software DOB.

Add SSDELBTN.EXE and the blank BTN.DBF (included in the downloadable file) to the BIN folder on the file server to implement this throughout the SuperSite.� Add a line to the IBERCFG.BAT to run the SSDELBTN.EXE from the BIN folder.

This application runs each time the terminal restarts and does not delete the BTN.DBF in the dated folder unless a blank copy resides in the BIN folder.

SSDELBTN.EXE uses the LOCALDIR variable.� Declare it in the IBERCFG.BAT before this application is called.

Usage: SSDELBTN.EXE

Options:

/?�� Displays help information.

Refer to document AKBID1118 for more information.

SSDELCDX.EXE

SSDELCDX.EXE deletes .CDX files from dated folder on SuperSite terminals.� Aloha application software versions 4.2x and higher include the option to not copy the index files to dated folders, so this utility has limited value in current versions of the Aloha application software.

SSDELCDX.EXE checks for the previous day's dated folder on the local terminal.� If it exists, the .CDX files are deleted from the dated subdirectory.

SSDELCDX.EXE uses the system date, not the Aloha application software DOB.

Add SSDELCDX.EXE to the BIN folder on the file server to implement this application throughout the SuperSite.� Add a line to the IBERCFG.BAT to run the SSDELBTN.EXE from the BIN folder.

This application runs each time the terminal restarts.

SSDELCDX.EXE uses the LOCALDIR variable.� Declare it in the IBERCFG.BAT before this application is called.

Usage: SSDELCDX.EXE

Options:

/?�� Displays help information.

Refer to document AKBID1118 for more information.

TAILER.EXE

Displays log files (debout) as they update in real time.� As the log file is updated, the changes are displayed in TAILER.EXE.� This utility is great for watching a terminal's debout from the file server, especially in a SuperSite.

Usage: TAILER.EXE <file>

Options:

None.

TAX.EXE

TAX.EXE exports a tax breakpoint table (TAX.TXT) for a specified tax amount.� Use a decimal amount for the tax rate instead of a percentage (e.g.� .0675, not 6.75).� Three fields are displayed: Through, Tax, and Delta.� 'Through' defines the sales amount to which the tax breakpoint applies.� 'Tax' defines the tax amount applied to the sales amount.� 'Delta' is the breakpoint defined in the Aloha application software.

Refer to the Aloha QuickService or TableService User Manual for more information regarding Repeating and Non-repeating Tax Breakpoints.

Usage: TAX.EXE <tax rate> > TAX.TXT

Options: None

UARTTYPE.COM

UARTTYPE.COM displays the type of UART the serial ports use.� This utility should be used in a DOS environment (such as a boot diskette) for accurate results.

Usage: UARTTYPE.COM

VIEWHOUS.EXE, VHOUSE2.EXE, and VHOUSE3.EXE

VIEWHOUS.EXE and VHOUSE2.EXE enable you to view the Aloha house account files by decoding and exporting the data to a text file.� VIEWHOUSE.EXE is used with the HOUSE file found in versions 4.0 and lower.� VHOUSE2.EXE is used with the HOUSE32 file found in versions 4.2 and 4.4.� VHOUSE3.EXE is used with the HOUSE32 or HOUSE50 file found in versions 5.0 and higher.

Usage: VIEWHOUS.EXE [options] <filename> > VIEWHOUS.TXT

Options:

/ACCT <#>�� Restrict to a particular house account number

/FULL�� Extract full information

/?�� Displays help information.

Usage: VHOUSE2.EXE [options] <filename> > VHOUSE2.TXT

Options:

/ACCT <#>�� Restrict to a particular house account number

/FULL�� Extract full information

/?�� Displays help information.

VIEWPRT.EXE

VIEWPRT.EXE enables you to view the Aloha printer logs (PRT*.LOG) by decoding and exporting the data to a text file.

There are multiple versions of VIEWPRT.EXE.� Each version is compatible with specific versions of Aloha.

VIEWPRT2.EXE views Aloha versions 3.950 - 4.111.

VIEWPRT3.EXE views Aloha versions 4.112 - 4.230, 4.300 - 4.304

VIEWPRT4.EXE views Aloha versions 4.231 - 4.2xx

VIEWPRT52.EXE views Aloha versions 5.0xx - 5.2xx

Usage: VIEWPRT.EXE <filename> > VIEWPRT.TXT

Options:

/?�� Displays help information.

VNR.EXE and VNR2.EXE

VNR.EXE and VNR2.EXE enable you to view the Aloha non-reset total files by decoding and exporting the data to a text file.� VNR.EXE is used with the NONRESET file found in versions 4.0 and lower.� VNR2.EXE is used with the NRTOTALS file found in versions 4.2 and higher.

Usage: VNR.EXE <filename> > VNR.TXT

Options:

/?�� Displays help information.

Usage: VNR2.EXE <filename> > VNR.TXT

Options:

/?�� Displays help information.

WAIT.EXE

WAIT.EXE creates a timed pause in a batch file.�

Usage: WAIT.EXE <seconds>

Options: None

WAITCE.EXE

WAITCE.EXE is designed for a Windows CE environment, and it enables a user to program a timed pause and automatically launch an application following the pause.� For example, some Windows CE-based handheld terminals using some wireless Network-Interface-Cards (NICs) may require addition time to initialize the network cards.� This means that an application in the Windows StartUp folder that requires the NIC may error out since the NIC has not yet initialized.

Instead of placing the network application in the Windows StartUp folder, you can instead place WAITCE.EXE in the StartUp folder and configure it to wait a desired number of seconds and then start a specific application.

You configure WAITCE.EXE using WAITCE.CFG.� Create a new text file on a standard Windows PC and label it WAITCE.CFG.� Specify the number of seconds to wait on the first line of the CFG file and specify the application to initialize on the second line of the CFG file.� For example, if you want WAITCE.EXE to pause for five seconds and then initialize \MY DOCUMENTS\TERM3.LNK, then the contents of your WAITCE.CFG file will be the following:

5

\MY DOCUMENTS\TERM3.LNK

Once you have created the WAITCE.CFG file, place it in the root folder of the Windows CE device.

Aloha Technologies currently has versions of WAITCE.EXE for MIPS and StrongARM types of CPUs.� Both versions are available in WAITCE.ZIP on the Aloha Technologies FTP site.

Usage: WAITCE.EXE

Options: None

Extended Information

FOHMGR.EXE

FOHMGR.EXE is a utility used by developers for the COM interface in order to manage the FOH.� It is only available with the COM Software-Developers-Kit (SDK).� Contact the Aloha Customer Service Center (CSC) at (817) 25-ALOHA (252-5642) for more information on the COM SDK.

WINDIFF.EXE

WINDIFF.EXE, available from Microsoft, is a useful utility for comparing two files for minor differences.� If you are in a position where one configuration or .INI file functions properly, but a seemingly identical file does not, install WINDIFF.EXE in order to compare the two files.

Caveats

Failure to place the utilities in the system's path can effectively nullify them.� Support personnel might not know the location of the utilities and assume they are not installed.� This will lengthen the support time while they are retrieved and installed.� Placing the utilities in the system's path ensures they are available from a command line within any folder on the system.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1118 SuperSite IBERCFG.BAT

AKBID1146 HDSPACE Low Disk Space Warning Utility

AKBID1171 FOHHOOK.BAT

AKBID1196 DBFUTIL.EXE

AKBID1220 Assigning the HASP LPT Port in the Aloha Application Software

AKBID1203 Configuring Aloha as a Thin Client on Windows Terminal Server

AKBID3187 Selecting an Open TCP Port for AlohaSpy

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1012 aloha_symbol_msr_arm alohasymbolmsr-arm alohasymbolmsr-arm.exe arm card checkno2 closeapp combitm dateday dayweek dbf2text dbfutil edcrenam fileincrementer fixlog fixlog2 fixlog3 fixlog4 fixlog4327 fixlog5 fixlog5.exe fixlog5200 fohmgr hasplptport hdspace hdspaced index iscript keyrenum killsvr netinfo posprint reboot30 renumber setupsys showclr showclr50 showclr52 splitstl ssdelbtn ssdelcdx tailer tax uarttype util utils viewhouse vhouse vhouse2 vhouse3 viewprt viewprt2 viewprt3 viewprt4 viewprt5 vnr vnr2 wait

style='mso-spacerun:yes'>� 2003

�

Windows 98 FOH Terminal Setup

Windows 98 FOH Terminal Setup

============================================================================

AKBID1013

Created: 17 December 1999

Updated: 15 May 2003

Reviewed: 2 March 2004

Microsoft Windows Versions: Windows 98

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

Subject: Windows 98 FOH Terminal Setup

============================================================================

Summary

The ALOHA^� application software requires several specialized settings (as well as several preferred settings) in the Microsoft^� Windows^� 98 operating system (OS) to properly run IBER.EXE and IBERQS.EXE in the Front-of-House (FOH).� If you are using the terminal to run both Aloha Front-of-House (FOH) and Back-of-House (BOH) together, refer to document AKBID1024.

Information

Since some computers come with Windows 98 preloaded while others do not, this document is based on editing the settings of Windows 98.� Users who are installing Windows 98 from scratch or upgrading another OS to Windows 98 can still use this document either by employing these instructions after the Windows 98 installation or by making many of these changes during the Windows 98 installation.

File System

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

The most important settings in the Aloha application software involve the network settings.� To access these settings, select Start/Settings/Control Panel/Network or right-click the Network Neighborhood icon on your desktop and selecting Properties.

The Configuration tab contains a Components area and Primary Network Logon type.� The components area should have Client for Microsoft Networks as the only network client installed.� You may have others, but these should only be added if absolutely needed.� The correct drivers for your network interface card (NIC) should also be listed.�

The Aloha application software can use either TCP/IP or NetBEUI as its network protocol.� Select either one, but both the file server and the terminals must use the same protocol.� To assign the protocol for the Aloha application software to use (refer to document AKBID1018), double-click the desired protocol, select the Advanced tab, and select 'Set this protocol to be the default protocol'.� If you select TCP/IP, Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure that terminals always have an address assigned to them.� The Aloha application software will not function without an IP address assigned to the terminal.� You may have multiple protocols installed as long as the proper protocol for the Aloha application software has been marked as such.�

To add file and print sharing for the Aloha application software, click the File and Print Sharing button and select both options.� Print Sharing may be left disabled if you are not using Windows based printer shares for the FOH.�

The Primary Logon Type is typically set to Windows Logon.� This log in enables Windows 98 to skip the prompt for the user name and password if the password is blank.� Setting this as Client for Microsoft Networks prompts for the user name and password regardless if the password is blank.� If Client for Microsoft Networks must be used as the Primary network logon, use the Microsoft Windows 98 TweakUI utility to automatically enter the user name and password.� TweakUI can be downloaded from the Aloha Technologies FTP site as TWEAKUI.ZIP.� Aloha Technologies installs this utility regardless of the Primary Logon Type setting.

Set the terminal's network name under the Identification tab.� Aloha Technologies uses TERM1, TERM2, and so on by default.� Different names may be used, but they must follow Aloha application software specifications.� The terminal name must be a common name used on all terminals (the TERMSTR, refer to document AKBID1010) followed by a number designating the terminal's ID number.� Examples include ALOHA1, ALOHA2, TSFOH_1, and TSFOH_2.� In this case, the TERMSTR would be 'ALOHA' or 'TSFOH_'.� Different TERMSTR names can not be used within the same Aloha system.� Spaces can not be used, but underscores can.� Leading zeros can not be used unless they are part of the TERMSTR, but it is not recommended.

Set the Workgroup name the same on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the Workgroup name, but this name can be of your choice as long as it is consistent throughout the Aloha application software.�

The Computer Description is solely to your discretion.

Ensure that 'Share-level access control' is selected under the Access Control tab.� Only experienced Domain administrators should consider using 'User-level access control'.

Aloha Share Name

The Aloha application software requires a network share name of BOOTDRV.� This is the required name.� This share needs to be applied to the root folder or drive in which the Aloha folder resides.� To set the share, right-click the drive or folder and choose Sharing.� Set the Share Name to BOOTDRV, the Access Type to Full, and leave the password fields blank.

If the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.� Some clients prefer to place the Aloha application software in a special folder in order to limit the shared files, and, therefore, enhance security.� Sharing the entire drive in which the Aloha application software resides also shares other files that reside on the drive, such as Windows.

Display Settings

To access the Display settings, select Start/Settings/Control Panel/Display or right-click the Windows desktop and select Properties.� Select the Settings tab.� Set the Color palette to 256 Colors or higher.� Aloha Technologies typically uses 16-bit color.�

Refer to document AKBID1165 for screen resolution settings.

Do not enable a Windows screen saver.

Time Zone & Daylight Savings

For the file server and all terminals to display the correct time and adjust to Daylight Savings changes properly, the Time and Date settings must be properly configured in Windows.� Select Start/Settings/Control Panel/Date/Time or double-click the time displayed on the task bar.� Ensure the date and time are correct.� Ensure the date and time are correct on the Date & Time tab.� Ensure the correct time zone is chosen on the Time Zone tab.� This time zone needs to be the same on all terminals and the file server.� If the area observes Daylight Savings, then the 'Automatically adjust clock for daylight savings changes' option must be selected on all terminals and the file server.� This can be turned on or off, but it needs to be consistent throughout the Aloha application software.

FIFO Buffers

Windows 98 enables First-In-First-Out (FIFO) buffers for each COM port.� These buffers tend to interfere with printers using Xon/Xoff flow control, so Aloha Technologies disables these buffers on all COM ports on all terminals, regardless of the printer type.� (In the event of a printer or COM port failure, a printer using Xon/Xoff flow control may be temporally connected to the port in the future.)

To access the FIFO buffer settings, select Start/Settings/Control Panel/System or right click My Computer and select Properties.� Select the Device Manager tab, and click the plus sign (+) next to Ports to expand it.� Select each port one at a time, and select Properties/Port Settings/Advanced.� Clear 'Use FIFO buffer'.� Repeat for each COM port.� The LPT port does not have this option.

Scandisk Autoscan & Settings

By default, if Windows is shut down improperly, it runs Scandisk the next time the system is started.� If it finds any problems on the drive, it prompts for answers.� Since there is not a keyboard that is typically attached to a FOH terminal to answer the questions, which increases the time the Aloha application software may be disrupted.� To alleviate this problem, Aloha Technologies offers a SCANDISK.INI that keeps Windows from prompting for 95% of the questions.� This SCANDISK.INI can be downloaded from the Aloha Technologies FTP site as SCANDISK.ZIP.� Place this file in the Windows COMMAND folder overwriting the one that currently exists.

Login Name

Refer to document AKBID1006 for more information on user login information.

To clear the current user names and passwords, delete *.PWL from the Windows folder to remove all users.� Select Start/Shutdown.� Select 'Close all programs and log in as a different user' and click Yes.� Windows logs the current user out and prompts for a user name and password.� Enter the desired user and password and log in to Windows.

VNetBIOS

Windows 98 might experience network problems with restaurants using five or more terminals.� To ensure that terminals do not experience these problems, Microsoft issued a new VNETBIOS.VXD that you can download from the Aloha Technologies FTP site as VNETBIOS.ZIP.� Aloha Technologies installs this .VXD file on all terminals, regardless of the system's size.� Refer to document AKBID1011 for more information.

Once you have the new .VXD, place it in the Windows SYSTEM folder overwriting the current version.� Edit the SYSTEM.INI in the Windows folder, and add a new line in the [386Enh] section that states NUMHCBS=x.� Replace x with a number four times the number of terminals in the system, but not less than 80 nor exceeding 200.� The default for this number is 100.� For example, a 25 terminal system would use NUMHCBS=100.� Do not exceed 100 unless you have more than 25 terminals.

To ensure that Windows does not overwrite the updated VNETBIOS.VXD following network configuration changes, place a copy of the updated VNETBIOS.VXD in the same folder as the Windows CAB files.

AUTOEXEC.BAT

Aloha Technologies uses a default AUTOEXEC.BAT (before the Aloha application software is installed) which contains only two lines:

SET PATH=%PATH%

DOSKEY

The first line creates a PATH variable that Windows 98 does not install by default.� If the path statement does not reside in AUTOEXEC.BAT, some software packages create a new path line that does not include the Windows default path.� With this line, the software will most likely append to the line and preserve the Windows path.

The second line installs DosKey.� DosKey is an application used in a command prompt that recalls previous lines typed via the arrow up and down keys.� For users accustomed to a command prompt environment, it is a welcome feature.

Install Aloha Software

Once Windows 98 is set up according to the standards outlined in this document and you can view the network, use the terminal installation diskette to install the Aloha application software.

To create this diskette, insert the installation CD in the file server's CD-ROM, and run SETUPPOS.EXE /ADVANCED.� Select Make Diskettes/Create Terminal Installation Diskette from the Main Menu

Once the diskette is created, insert it into the terminal's floppy drive, and run SETUP.EXE.� The setup program walks you through the rest of the installation.

If the terminal does not have a floppy drive, run the Terminal Installation application directly from the CD-ROM on the file server.� Map a drive to the CD-ROM on the file server.� Do not choose the Reconnect at Logon option when mapping the drive.� Run the file \TERMINST\SETUP.EXE from the Aloha POS CD.� The setup program walks you through the rest of the installation.

Windows 2000 File Server

If you are using a Windows 2000 file server with Windows 98 FOH terminals, you may need to adjust the login account used by CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) on the file server.� Refer to AKBID1197 for more information.

Extended Information

No information.

Caveats

There have been instances where Dial-Up Networking was installed on Windows 98 and caused conflicts with networking abilities in the Aloha application software.� The reason is currently unknown.

============================================================================

See also:

AKBID1001 Configuring the CALIBRATE Variable on Aloha Terminals

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1010 Aloha Application Software System Environment Variables

AKBID1011 Windows 9x VNETBIOS.VXD Patch

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1018 Network Lana Numbers

AKBID1024 Microsoft Windows 98 Filer Server/Terminal Setup

AKBID1028 Winhook

AKBID1165 FOH Screen Resolution Settings

AKBID1175 Aloha Terminal Restart Options

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1197 Assigning Logins to Aloha Services

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1013 stage staging

Full Hard Drive Recovery

Full Hard Drive Recovery

============================================================================

AKBID1014

Created: 10 January 2000

Updated: 5 June 2001

Reviewed: 27 January 2004

Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: Full Hard Drive Recovery

============================================================================

Summary

This document describes the proper emergency recovery procedure when encountering a full hard drive while a site is in operation.� Using the proper options in the ALOHA^� application software will ensure this never happens.

Information

The typical indication that the file server's hard drive has exhausted its disk space is the creation of a STOP file in the TMP folder.� This causes all Front-of-House (FOH) terminals to exit and display a 'Waiting for permission to resume' message.� This occurs automatically, and the Aloha application software cannot restart until you provide additional disk space.� The debugging (debout) files will display 'Failed to write to TRANS.LOG' or 'Failed to write to printer log' on one of the last lines.� Use Microsoft^� Windows^� Explorer or a command prompt to check for available disk space.�

To recover from a full hard drive emergency, perform the following steps:

1.        Use Windows Explorer or a command prompt and locate the oldest dated folder in the Aloha application software folder.

2.        Delete all .CDX and .TDX files.� These are index files for the database, and they are not needed unless the user relies on Crystal Reports.

3.        Locate the next dated folder and delete the .CDX and .TDX files.

4.        Continue this process through the dated folders until you have recovered several megabytes of disk space.

5.        When the necessary disk space is recovered, restart the FOH via the Control/System/Start FOH if you are using versions 4.4x or lower, or Aloha Manager/Utilities/Start FOH if you are using versions 5.0x or higher.� (Deleting the STOP file in the TMP folder also performs this step.)

Extended Information

Consider utilizing Winhook (refer to document AKBID1028 Winhook) to help maximize disk efficiency by deleting .CDX and .TDX files and archiving dated folders.� Winhook, when used together with the Automatic Directory Purge feature (refer to AKBID1193), can dramatically decrease the chances of a hard drive filling up.� The Purge feature is located in Maintenance/Options/File Maintenance & Backups if you are using version 4.4x or earlier.� This feature is located in Aloha Manager/Maintenance/Store Settings/System/Disk Maintenance if you are using version 5.0x or better.� A possible solution would be as follows:

1.        Create a separate hard drive partition for archived dated folders.� The size can vary.� Since archives are compressed, you need approximately 500 kilobytes per day.� This means a 500-megabyte partition will last approximately 1,000 days (refer to document AKBID1183).

2.        Use Winhook to compress and archive the dated folder each night.

3.        Set the Purge feature to a number of days based on the average dated folder size and the disk space available.

4.        Set the user security levels to allow the Purge feature for all desired users.

Versions 5.0x and higher include the option of omitting .CDX files in the dated folders.� This option is located in Aloha Manager/Maintenance/Store Settings/System/End of Day.�

Caveats

No information.

============================================================================

See also:

AKBID1015 EOD Process & Errors

AKBID1028 Winhook

AKBID1146 HDSPACE.EXE Low Disk Space Utility

AKBID1183 Recommended Hard Drive Partitions, File Systems and Setup

AKBID1193 Purging Dated Folders in Aloha Manager

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1014 create diskspace harddrive low

�

EOD Process and Errors

EOD Process and Errors

============================================================================

AKBID1015

Created: 18 January 2000

Updated: 3 December 2003

Reviewed: 15 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: The Aloha Application Software End-of-Day (EOD) Process and Errors

============================================================================

Summary

The ALOHA^� application software End-of-Day (EOD) process that closes out the sales for a given Date-of-Business (DOB), archives the DOB, and starts the new DOB with a fresh TRANS.LOG (transaction log).� Should EOD fail, knowledge of where to look for the cause, the steps to correct it, and an overall understanding of the process is crucial in supporting the Aloha application software.

Information

The EOD Process

IBER.EXE or IBERQS.EXE starts and controls the Aloha application software EOD process.� The EOD process is often confused with the Grind process (refer to document AKBID1016) that follows it.� This is a major misconception since different Aloha modules control each process.� Whereas the EOD process closes out the sales for a given DOB, archives the day's business and starts the new DOB with a fresh transaction log, the Grind process simply converts the day's transaction log into viewable database files for reporting.� These are two separate processes and you should not confuse them.

After the EOD process occurs, the Grind process begins.� When the Grind process is complete, the Winhook (refer to document AKBID1028) process begins.� Each process relies on the previous process to complete properly.� If one fails, the process that follows will not activate.� It is important to determine the process that failed in order to properly diagnose problems.

The EOD process is triggered by either an End-of-Day Event configured in Aloha Maintenance (versions 4.4x and lower) or Aloha Manager (versions 5.0x and higher), or manually from the Front-of-House (FOH) or the Back-of-House (BOH).� Refer to the Aloha QuickService or TableService User Manual for more information on events and manually activating the EOD process.

The complete EOD process performs the following tasks:

1.        The master terminal, which controls the EOD process, creates an EOD marker file in the DATA folder to inform the other terminals of the EOD commencement.

2.        A dated folder for the day's business is created in the root Aloha application software folder on the file server.� The folder is labeled using the DOB (YYYYMMDD).

3.        All required files are copied from the DATA folder on the file server to the dated folder.

4.        All unneeded files are removed from the file server's DATA and TMP folders.

5.        The configuration files are copied from the NEWDATA folder to the DATA folder on the file server.

6.        A DONE30 marker file is created in the dated folder to signal a successful completion of the EOD process.

7.        The EOD marker file is removed from the DATA folder.

8.        All FOH terminals restart.

Troubleshooting the EOD Process

The first step in troubleshooting the EOD process is to determine whether the problem is an actual EOD process problem or if another process is responsible for the errors.� If the EOD process is experiencing errors, the FOH terminals display the message 'Waiting for EOD to complete' for an extended period of time.� The normal EOD process should not take more than five minutes to complete.�

If the EOD process did not even start, the problem is not with the EOD process itself.� You need to verify your EOD event and DOB settings.� Events will not fire properly if the DOB is more than one day off of the system date.� The EOD process also does not start if a dated folder already exists for the DOB.

If the FOH displays a message stating 'Waiting to Grind YYYMMDD', then the problem is with the Grind process and you need to refer to document AKBID1016.� Some versions of Aloha display an error stating 'READDBF(): Could Not Read Dated Subdirectory YYYYMMDD Because it is Not Marked as Ground - Exiting' rather than 'Waiting to Grind YYYYMMDD'.

If the Winhook batch file is not firing or running properly, then the problem is with the Winhook process and you need to refer to document AKBID1028.

Once the problem is determined to be the EOD process, verify if the EOD process has created a dated folder for the DOB in the Aloha folder.� If so, check if a DONE30 marker file exists in the dated folder.� If the DONE30 marker file exists, then the EOD process has fully completed and is not the root of the problem.

The next step is to view the EOD debugging output file (debout), which is located in the TMP folder on the master terminal and labeled DEBOUT.EOD.

If the FOH terminals display an EOD error, cancel the EOD from the BOH.� Canceling EOD effectively deletes the EOD marker file and fools the computer into thinking it is late on the EOD process.� The FOH should immediately begins the process again, but before canceling EOD, verify the following:

-          Establish how far the EOD process went before it failed by reading DEBOUT.EOD.� Check whether a dated folder was created and, if so, if any files were copied to it.

-          Verify the location of the transaction log. �If the transaction log is in the DATA folder, cancel the EOD process immediately.� If the transaction log is in the dated folder, as a precaution, copy it back to the DATA folder and cancel the EOD process.� The Cancel End-of-Day function in Control or Aloha Manager copies the transaction log from the dated folder back to the DATA folder and makes necessary backups in the TMP folder, but practice safe computing by backing up the transaction log.

If the EOD failed because the file server's hard drive ran out of available space, free up the required space (refer to document AKBID1014).� After freeing up the recommended space, use the Cancel End-of-Day function from Control or Aloha Manager to restart the EOD process.�

If the site is using Centralized Database Management (CDM), the EODCTLWAITTIME and EODFOHWAITTIME variables in the ALOHA.INI may be enabled.� These values (in minutes in version 5.0x and in seconds in versions 5.2x and higher) set timed delays in the EOD process that are required by the CDM process.� The delays may result in the appearance of the EOD process not initializing.� If you are using CDM, do not edit these files, but instead wait for the process they govern to complete.� When the process is complete, the EOD process will continue.� If you are not using CDM, set each of these values to a negative value to disable the timeouts and decrease the time that the EOD process takes to complete.

The FOHHOOKTIMEOUT variable in the ALOHA.INI can also increase the time the EOD process takes to complete.� Refer to document AKBID1171 for more information on this variable.

If you are experience problems where the EOD process fails to copy files, you should disable write caching for the hard drive in which the Aloha application software resides on the file server.� This is usually configured in the hard drive's properties in Windows.

24-hour Operation

If the 24-hour Operation option is enabled in the Aloha application software, the EOD process differs in regards to handling open checks and clocked-in employees.� When the EOD process occurs with the 24-hour Operation option enabled, all open checks are temporarily closed and all clocked-in employees are checked-out and clocked out.� Before the EOD process completes, and new transaction log is started in the DATA folder, previously clocked-in employees are clocked-in again and the previously open checks are reopened.� In general, all checks closed prior to the EOD process are attributed to the previous DOB.� All checks open at the time of the EOD process are attributed to the new DOB.

Employee checkouts show sales for the entire shift, even if it encompasses two days of business.

Although the sales from checks still open at the time of the EOD process are attributed to the new DOB instead of the previous DOB, the BOH check reprint application still list these checks for both dated.� If you are verifying report calculations using reprinted checks, some checks my not apply to the DOB in question.

FOH sales reports for the new DOB includes sales from checks still open at the time of the EOD.

The time stamp displayed on checks listed in the FOH View Open Checks function are true to the time the check was originally opened.� The time does not reset following the EOD.

If employees are clocked-in at the time of the EOD process, each day is considered a different shift, as if they had manually clocked-out and clocked-in for a new shift.� It is possible for an employee to only work two shift but appear as four shifts in the ALOHA application software.� For example, if the employee works from 9:00 PM to 5:00 AM and the EOD process occurs at 12:00 AM, the shifts appear as the following:

Shift

System Date

Date of Business

Clock-in Time

Clock-out Time

1

01/02/2001

01/02/2001

12:01 AM

5:00 AM

2

01/02/2001

01/02/2001

9:00 PM

12:00 AM

3

01/03/2001

01/03/2001

12:01 AM

5:00 AM

4

01/03/2001

01/03/2001

9:00 PM

12:00 AM

If guest checks are unknowingly left open, they can carry over to an infinite number of days unless the carried over transactions are routinely verified by a manager.� The same possibility also applies to an employee who fails to clock-out.� These scenarios can have an adverse effect on balancing sales and labor for a DOB.

Back-of-House Passwords

In versions 5.0x and higher, if the BOHSEC file exists along with the 'File Formerly Known as BOHSEC' file (refer to document AKBID3004), the EOD process deletes the BOH passwords.

Date of Business

If Maintenance (versions 4.4x and lower) is left open through one or more EOD processes, it may overwrite the current DOB with an incorrect DOB when it is closed.�

Extended Information

DEBOUT.EOD displays checkpoints to define the progress of the EOD process.� The following is an explanation of each checkpoint:

Checkpoint

Process

A

Copy TRANS.LOG from DATA to the dated folder.

A1

Delete GND*.*, ADJTIME*.*, and *.CKP from DATA.

A2

Copy EMP.* from NEWDATA to DATA to compensate for real-time updates to the employee data

B

Copy *.DBF from DATA to the dated folder.

C

Copy *.CDX from DATA to the dated folder.

D

Copy ALOHA.INI from DATA to the dated folder.

E

Copy EVENT*.CFG from DATA to the dated folder.

E2

Copy SMART.CFG from DATA to the dated folder.� SMART.CFG was never fully implemented and is not currently used.

E3

Copy CKO.CFG from DATA to the dated folder.

E4

Copy DEPOSIT.TXT from DATA to the dated folder.

E5

Copy WEATHER.TXT from DATA to the dated folder.

E6

Copy PRICE.CFG from DATA to the dated folder.� PRICE.CFG is not used in versions 4.4x and higher.

E7

Copy HOUSE*.* from DATA to the dated folder.

E8

Copy NRTOTAL*.* from DATA to the dated folder.

E8A

Copy FF.INI from DATA to the dated folder (QuickService only).

E9

Copy BOHSEC from DATA to the dated folder.

E10

Copy *.CSH from DATA to the dated folder.

E10A

Copy CHITTAG.CFG from DATA to the dated folder.

G

Delete MIRROR.LOG from TMP.

H

Delete PRT*.LOG from DATA.

PRT or HH

Delete VID*.LOG from DATA.

I

Delete *.LCK from DATA.

I2

Delete GND*.* from DATA.

I3

Delete CKO.CFG from DATA.

I4

Delete DEPOSIT.TXT from DATA.

I5

Delete WEATHER.TXT from DATA.

J or JERRETT

Delete *.ANS from PMS.

K

Perform a 'NEWDATA' copy test.

L

Copy *.DBF from NEWDATA to DATA.

M

Copy *.CDX from NEWDATA to DATA.

N

Copy *.CFG from NEWDATA to DATA.

O

Copy *.INI from NEWDATA to DATA.

P

Create the DONE30 marker file in the dated folder.

SuperSite systems do not automatically perform the refresh task (updating DATA with the NEWDATA files) during the EOD process unless specified with a 'Non-immediate Refresh'.�

The SuperSite EOD process performs as described previously in this document, but the file server mentioned previously is the store's Master/Server, not the Super Server.� EOD also automatically created a GNDDBF30.XXX marker file in the dated folder.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1014 Full Hard Drive

AKBID1016 Grind Process and Errors

AKBID1028 Winhook

AKBID1171 FOHHOOK.BAT

AKBID3004 File Formally Known as BOHSEC

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1015

Grind Process and Errors

Grind Process and Errors

============================================================================

AKBID1016

Created: 20 January 2000

Updated: 10 November 2003

Reviewed: 23 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: Aloha Application Software Grind Process and Errors

============================================================================

Summary

The ALOHA^� application software uses GRIND.EXE or GRINDQ.EXE in a process that reads the TRANS.LOG (transaction log) for a given Date-of-business and creates a series of grind (GND*.DBF) files that contain all relevant information for the day's business.� This grind process insulates other Aloha system components such as RPT.EXE (reports) from the need to understand the binary transaction log and enables third party software easy access to data generated by the Aloha application software.

Information

The Grind Process

The grind process reads the binary Aloha transaction log and creates grind database files labeled GND*.DBF.� If you are using a Relational Database (RDB), the tables are labeled HSTGND* in the RDB.� Refer to document AKBID1030 for more information on grind file contents.

The grind process, initiated by CTL.EXE (Control) in Aloha versions 4.0x and lower or CTLSVR.EXE (Control Server) in versions 4.2x and higher, is typically enabled for one of the following reasons.

-          You want to print or view a report for the current day's business.� In this case, the grind files are created in the Aloha application software DATA folder.� If you are using an RDB, the grind tables are created in the RDB database.

-          The End-of-Day (EOD) process (refer to document AKBID1015), once complete, creates a DONE30 file in the new dated folder to signal Control or Control Server to initialize the grind process for the dated folder.� In this case, the grind files are created in the dated folder.� If you are using an RDB, the tables are created in the RDB database.

-          You are regrinding a dated folder.

-          If you are using a RDB, then grind process is constantly active or standing by.� Refer to the Relational Databases and Aloha POS User Manual for more information.

When the grind process completes, it creates a file labeled GNDDBF30.XXX in the dated folder.� This file signifies the grind process has successfully completed.

Failure to Automatically Grind

If the grind process does not automatically initialize, verify the following:

Control or Control Server is not active on the file server.� Control or Control Server must be active on the file server for the grind process to start following the EOD process because it regularly scans the dated folders created by the EOD process for new folders to grind.� If Control or Control Server is not active, the folders are not scanned and the grind process does not automatically start.� The following� precautions help prevent this:

a)       If Control Server is not registered as a Microsoft^� Windows^� service (in versions 4.2x and higher), place a shortcut to Control or ALOHAMGR.EXE (Aloha Manager) in the Windows StartUp folder and configure Windows to automatically log in (refer to document AKBID1005).� This ensures that the operating system (OS) logs in and processes the StartUp folder in case of a power failure or unexpected shutdown.

b)       If Control Server is not registered as a Windows service, disable the user's option to exit Control or Aloha Manager.

c)       Register Control Service as a Windows service.

The 'Auto Grind and Summarize' flag is cleared in Control (versions 4.4x and lower).� The 'Auto Grind and Summarize' setting in Control enables or disables the grind process from automatically activating when needed.� This setting, located in Control/System/Auto Grind and Summarize, is very easy to inadvertently clear.� The ability to clear this setting is controlled by the user's abilities as defined in the Aloha Back of House (BOH) security configuration.� Refer to the Aloha QuickService or TableService User Manual for more information.� All users, regardless of standing, should be disabled from clearing this flag.

In versions 5.0x and higher, ensure that Aloha Manager/Maintenance/Store Settings/System/Aloha Settings/Disable Auto-Grind is not enabled.� If it is, disable it, refresh the system, and restart Control Server.� In versions 4.4.x and lower, ensure that Maintenance/System/'Auto Grind and Summarize' is disabled.

The Summary file creation is interfering with automatic grinding of the new dated folder's data.� This usually becomes an issue when Summary files are enabled after multiple dated folders already exist and the Summary process cannot catch up to the current date before another new dated folder is created.� If you do not need the Summary files, disable them by setting the RUNSUM variable in the ALOHA.INI to FALSE.� Refer to document AKBID1105 for more information on the Summary process.

A Winhook file is defined in the configuration files, but the batch file does not exist in the BIN folder.� The Grind process may not automatically start following the EOD process if a Winhook batch file is defined in the BOH, but the batch file does not actually exist in the BIN folder.� Clear the Winhook file definition to rectify this problem.� Refer to document AKBID1028 for more information on Winhook.

The hard drive has run out of available space (refer to document AKBID1014).

The shortcut for Control or Aloha Manager includes the REMOTE variable or the command line variables for Control Server include the REMOTE variable.� Among other functions, the REMOTE variable (refer to document AKBID3110) instructs Control or Control Server to not automatically search for new dated folder to grind.� Verify the REMOTE command line variable does not exists in the command line for any shortcuts to Control (versions 4.4x and lower), any shortcuts to Aloha Manager (versions 5.0x and higher) or in the Windows registry command line for Control Server (refer to document AKBID3009).

The transaction log or a database file (DBF or RDB) is corrupted.� If the transaction log appears to be the corrupted, use the fixlog utility (refer to document AKBID1012) to repair the log.� If a corrupt .DBF file (in non-RDB systems only) appears to be the root of the problem, try using the same .DBF file from a previous day's folder.� Backup the possibly .DBF file and copy the same .DBF file from the previous day's folder and retry the grind process.� Ensure the .DBF file in the NEWDATA and DATA folders is not also corrupt.� If the system is using an RDB and the RDB is corrupt, consult your database engine's user manual for help repairing a corrupt database.

A NOGRIND file exists in the Store's folder (RDB systems only).� The most common reason for the grind process to fail in an RDB system is the existence of a NOGRIND file in the store's folder (STR00001).� The grind process does not initialize if a NOGRIND file exists.� The NOGRIND file may exist because of human intervention or Control or Control Server may have created it because of problems in the grind process.� Either way, remove the flag and see if the grind process performs properly.� If the grind process errors out three times, it will recreate the NOGRIND file.� The Debugging-Output-Files (debouts) created by the grind process should provide an adequate explanation of the problem.� Refer to document AKBID1134 for more information on debouts.

'Disable Auto-Grind and Summarize' is enabled in Maintenance/Options/BOH Controls or Aloha Manager/Maintenance/Store Settings/System/Aloha Settings.� You should always leave this option disabled.

Control or Control Server is hung up waiting for a Winhook batch file to complete.� Although Control and Control Server do not monitor the success of the commands included in the Winhook batch file, they do wait for the batch file to complete.� Control and Control Server do not continue with other tasks (such as grinding dated folders or initializing the Winhook batch file for other dated folders) until the current Winhook batch file completes.� If the batch file from the previous Date-of-Business (DOB) pauses or hangs indefinitely, then Control or Control Server will not initialize other tasks.� If you have registered Control Server using a specific user login rather than the built-in Windows system account, then the batch file does not interact with the desktop, and you cannot verify the Winhook batch file's completion or see any errors (including errors while printing reports).� In this case, you can view the current processes in Windows Task Manager and close the CMD.EXE process if it is active (ensure that the CMD.EXE process does not represent another task besides Winhook).

If you have Control Server configured to log in with a specific user rather than the built-in Windows System account, ensure that the login has administrative privileges.

If, for whatever reason, the site is ready to open for business but the FOH terminals are still waiting for the previous day to grind, you can 'trick' the Aloha application software into thinking it has successfully completed the grind process for the dated folder by manually creating the GNDDBF30.XXX file using the DOS ECHO command.� The following line is an example of this:

ECHO 1 > %IBERDIR%\20000112\GNDDBF30.XXX

This is a temporary fix for use in an emergency and does not replace the actual grind process.� After you have fixed the problem, delete the GNDDBF30.XXX and WINHOOK files from the dated folder.

SuperSites not Grinding Dated Folders

If a SuperSite successfully grinds a store's data folder during the current day but does not grind the dated folder following the EOD process, then verify that the TERMSTR is configured properly in store maintenance.� The grind debouts will show how the TERMSTR that is currently configured.

Debugging Variables

Variable

DEBUG

Description

Generates extra debugging information in the Debout files.

System Variable Example

N/A

Command Line Example

GRIND.EXE /DEBUG

Variable

DEBUGCONVERTLOG

Description

Generates additional debug information in the debout files when converting a transaction log, and it is used with the CONVERTTRANSLOG function.� Has the same effect as the DEBUGCONVERTTRANSLOG variable.�

System Variable Example

N/A

Command Line Example

GRIND.EXE /DEBUGCONVERTLOG /CONVERTTRANS.LOG

Variable

DEBUGCONVERTTRANSLOG

Description

Generates additional debug information in the debout files when converting a transaction log.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.�

System Variable Example

SET DEBUGCONVERTTRANSLOG=TRUE

Command Line Example

N/A

Variable

DEBUGGRINDMANAGER

Description

Generates additional Grind Manager debugging information in the debout files.� Existence of the variable is all that matters.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.�

System Variable Example

SET DEBUGGRINDMANAGER=TRUE

Command Line Example

N/A

Variable

DEBUGGRINDSTORE

Description

Provides additional Store grinding debugging information in the debout files.� Used only with SuperSites.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.�

System Variable Example

SET DEBUGGRINDSTORE=TRUE

Command Line Example

N/A

Variable

DEBUGGRINDTHREAD

Description

Provides additional grind thread initiation debugging information in the debout files.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.�

System Variable Example

SET DEBUGGRINDTHREAD=TRUE

Command Line Example

N/A

Variable

DEBUGMERGETRANSLOGS

Applications

GRIND.EXE, GRINDQ.EXE

Description

Generates additional debugging information in the debout files when merging transaction logs.�

Command Line Example

GRIND.EXE /DEBUGMERGETRANSLOGS

Regrinding Dated Folders

If you need to regrind a dated folder, you can use either use the Regrind Subdirectories utility in Aloha Manager or you can manually grind each dated folder from a command line.

If you are using the Regrind Subdirectories utility, all database and transaction log conversions are performed automatically without any user input.� Open Aloha Manager, select Utilities/Regrind Dated Subdirectories, select the dates to regrind, set Active to 'On', set Num Grinds to '1' and click Done.� Refer to the Aloha QuickService or TableService User Manual for more information on the Regrind Subdirectories utility.

The Aloha application software stores the Regrind Subdirectories utility configuration data in the \SQL\SQL.INI and the list of dated folders to regrind in REGRIND.DBF.

In versions, 5.2.7.165 through 5.2.7.x, and 5.2.8.57 and higher, the Regrind Subdirectories utility creates a NOREGRIND flag in the dated folder if it is unable to regrind it.� The enables the Regrind Subdirectories utility to move on to the next dated folder in the list.� When this occurs, the dated folder is noted as 'Noregrind' in the Regrind Subdirectories utility, and you can reselect the dated folder in order to attempt to regrind it again.

If you are regrinding the dated folders in a site using an RDB, you can place a REGRIND flag in the Store folder in order to override the NOGRIND file (if it exists).� If you are performing an upgrade, this enables you to upgrade and regrind dated folders, even if you do not yet want to upgrade and grind current data.

Manually Grinding Dated Folders

To manually grind a dated folder from a command line, open a command line and navigate to the BIN folder.� The command line is GRIND.EXE followed by /DATE, and the name of the dated folder to grind.� For example, use the following command line:

GRIND.EXE /DATE 20000112

Use DATA as the date to manually grind the current day's transactions.� You can also use this command line in batch files.� Refer to document AKBID1010 for more information on command line variables.

Extended Information

Remote copies of the non-RDB BOH use the RUNGRIND folder to start the Grind process for the current day's data.� Refer to document AKBID3130.� This does not apply to systems with a RDB database.

Caveats

No information.

============================================================================

See also:

Relational Databases and Aloha POS

Aloha QuickService or TableService User Manual

AKBID1005 Microsoft Windows Automatic Log In

AKBID1010 Aloha Application Software System Environment Variables

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1014 Full Hard Drive Recovery

AKBID1015 EOD Process and Errors

AKBID1028 Winhook

AKBID1030 Aloha Grind Database Contents

AKBID1081 Summary Process and Errors

AKBID1134 Debouts

AKBID1162 Microsoft Windows Service versus Non-Service

AKBID3009 CTLSVR.EXE registry Variables

AKBID3110 The REMOTE Variable

AKBID3130 RUNGRIND File in the DATA Folder

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1016 auto-grind autogrind

Required Category

Required Category

============================================================================

AKBID1017

Created: 27 January 2000

Updated: 10 February 2003

Reviewed: 27 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.4x � 5.3.x

Subject: The Aloha Application Software Required Category Feature

============================================================================

Summary

The ALOHA^� application software 'Required Menu Category' setting forces an order entry employee to order one or more items from a specific set of items before they can print or close a check.� It is designed to remind servers to place items on the check that they would normally prepare or get themselves as opposed to items that are sent to a remote printer for production (the most common being non-alcoholic beverages).

Information

If the you have enabled 'Required Menu Category', the server cannot print or close a check until one of a specific set of items is present on the check.� It the site has enabled Pivot Seating or 'Guest Count by Entr�e', the server must have as many of the required items as there are guests on the check.� Refer to the Aloha TableService User Manual for more information on 'Pivot Seating' and 'Guest Count by Entr�e'.� If you are using manual guest counts, only one item from the required menu category must be present on the check in Aloha versions 5.2.5.x and lower.� If you are using manual guest counts in versions 5.2.7.x and higher, you must have an item from the required menu category for each guest.

The first step to enable the 'Required Menu Category' setting is to create a non-sales category for the option to use and place the desired items in the new category.� Refer to the Aloha TableService User Manual for more information on creating and editing non-sales categories.

If the site is using Aloha versions 4.4x or lower, assign the new category in Maintenance/Menu/Global Menu Settings.

If you are using Aloha versions 5.0x or higher, assign the new category in Aloha Manager/Maintenance/ Store Settings/Order Entry/More Options.

Extended Information

No information.

Caveats

Aloha versions prior to 3.6x have two limitations to this option:

1.        You can print the guest check without a required item, but you cannot close the guest check.

2.        No matter what the guest count setting, only one required item is needed to print or close the check regardless of the number of guests.

The following issues for all Aloha versions:

1.       If the qualifying item is ordered and later voided, the Aloha application software will still enable you to print and close the check.� Remember that this feature is designed to remind the servers to add those items to the check, not necessarily to enforce or police the policy.

2.       If you are using the 'Print Check (on) Order' setting (refer to the Aloha TableService User Manual for more information), the Aloha application software will print the initial check when ordered.� Subsequent checks without an additional order will not print.� The server will not be able to close the check until the necessary required item(s) are on the check per the rules described above.

3.       Make sure you have placed all reasonable items in the required category to compensate for all reasonable scenarios.� For example, all alcoholic beverages should be included in the required category since a food order might be accompanied by only a beer, wine, and so on.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1017

�

Network Lana Numbers

Network Lana Numbers

============================================================================

AKBID1018

Created: 13 January 2000

Updated: 10 April 2003

Reviewed: 3 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: Network Lana Numbers

============================================================================

Summary

The correct configuration of the Microsoft^� Windows^� LAN Adapter (Lana) numbers is essential to the ALOHA^� application software.� This document explains how to verify and change lana numbers in Windows.� These instructions are the same regardless if the computer is used as a Front-of-House (FOH) terminal, a Back-of-House (BOH) server, or both.

Information

Lana numbers are NetBIOS interface identification numbers assigned to the binding of each network adapter coupled with each network protocol.� For each network adapter on a system, there is a different lana number for each protocol.� The following example shows the possible bindings and lana numbers for a computer with a network interface card (NIC) and a modem using TCP/IP and NetBEUI protocols:

Lana Number

Network Interface

Network Protocol

0

NIC

TCP/IP

1

Modem

TCP/IP

2

NIC

NetBEUI

3

Modem

NetBEUI

All network activity for the Aloha application software is routed through lana number 0.� You must assign the NIC and protocol used by the Aloha application software to lana number 0.� You can install multiple protocols and network adapters on a computer running the Aloha application software, but you must properly configure the lana numbers in order for the Aloha application software to function properly.� The Aloha application software can use any NetBIOS protocol (NetBEUI, TCP/IP, IPX/SPX), but one must select one, and set it to lana number 0 throughout the entire Aloha application software (file server and terminals).

Symptoms of an incorrect lana number configuration include:

1.        FOH terminals display the message 'Master is Down' when the Master terminal is up and functioning.

2.        The inability of FOH terminals to recognize the Master terminal or the file server.

3.        The inability of the Aloha Synctime option to properly synchronize the time on the BOH file server with the time on the FOH terminals.

4.        Windows displays 'Fail to register station name 0x23' or 'Fail to register station name 0x34' network errors.

Windows 95, Windows 98, or Windows Me

If you are using Windows 95, Windows 98, or Windows Millennium Edition (Me), access the computer's network properties by selecting Start/Settings/Control Panel/Network or right-click Network Neighborhood from the desktop, and select Properties.

The protocol marked as the default Windows protocol is assigned lana number 0.� Select the protocol intended for use with the Aloha application software, and select Properties.� Select the Advanced tab, and select 'Set this protocol to be the default protocol'.

If multiple network adapters are present on the terminal, multiple instances of the same protocol may reside in the network properties.� Select the protocol and adapter intended for use with the Aloha application software as the default protocol.

Windows NT

If you are using Windows NT^�, access the computer's network properties by selecting Start/Settings/Control Panel/Network, or right-click Network Neighborhood from the desktop, and select Properties.� Select the Services tab, and double-click the NetBIOS Interface service to open it.

This displays a list of the current lana number assigments.� Each lana number is associated with a network route or binding.� Each binding contains a protocol (Nbf for NetBEUI and NetBT for TCP/IP) plus a network adapter.� NetBEUI on a NE2000 NIC has a binding similar to 'Nbf -> NE2000'.� TCP/IP on a NE2000 NIC has a binding similar to 'NetBT -> NE2000'.� You must set the binding intended for use by the Aloha application software to lana number 0.

Perform the following if the incorrect binding is assigned to lana number 0:

1.        Select the binding currently assigned to lana number 0, and click Edit.� Change the number to the next available unused lana number.

2.        Note the current lana number of the binding intended for use with the Aloha application software.

3.        Select the binding intended for the Aloha application software, and click Edit.� Set the lana number to 0.

4.        Select the original binding that was lana number 0, click Edit, and change it to the lana number previously occupied by the Aloha application software binding.

5.        Click OK.

You should now have the same lana numbers listed as when you started, but the assignments are changed to suit the Aloha application software.

Windows 2000, Windows XP, Windows XPe, and Windows Server 2003

If you are using Windows 2000, Windows XP, Windows XP Embedded (XPe), or Windows Server 2003, you must use the LANACFG.EXE utility to view and adjust lana numbers.� The version of LANACFG.EXE that you use depends on the version of Windows that you are using.� The Aloha Technologies FTP site has two versions: LANACFG.ZIP and LANACFG_XP_NO-SP.ZIP.� Use the following chart to determine the version of LANACFG.EXE that you should use:

LANACFG.ZIP

LANACFG_XP_NO-SP.ZIP

Windows 2000 (all versions)

Yes

No

Windows XP

No

Yes

Windows XP SP1

Yes

No

Windows XPe

No

Yes

Windows XPe SP1

Yes

No

Windows Server 2003

Yes

No

Place LANACFG.EXE in the Windows folder.

To view the current lana numbers, open a command prompt and navigate to the Windows folder.� Type the following command line:

LANACFG.EXE SHOWLANAPATHS

This displays a list of current lana number assignments.� Each lana number is associated with a binding.� Each binding will contain a protocol (Nbf for NetBEUI and NetBT for TCP/IP) plus a network adapter.

Find the binding for the Aloha application software to use.� If the incorrect binding is assigned to lana number 0, change the number to the next available unused lana number using the following command line:

LANACFG.EXE SETLANANUMBER 0 x

Replace x with the new lana number.

Change the binding that the Aloha application software will be using to 0 using the following command line:

LANACFG.EXE SETLANANUMBER y 0

Replace y with the current lana number applied to the binding for the Aloha application software to use.

Type the following command line to verify the correct binding is assigned to lana 0:

LANACFG.EXE SHOWLANAPATHS

If the lana numbers are properly assigned, type the following command line to verify and write the new lana information to the registry.

LANACFG.EXE REWRITELANAINFO

Restart the computer.

Extended Information

Windows 2000, Windows XP, Windows XPe, Windows Server 2003, and Windows Me can display 'Fail to register station name 0x23' network errors if DHCP Media Sense is not disabled on a PC that is not connected to an active network.� Refer to operating system's configuration document for more information.

Caveats

No information.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1018 lanacfg lanaconfig

�

Manually Registering and Un-registering Aloha Applications

Manually Registering and Un-registering Aloha Applications

============================================================================

AKBID1019

Created: 26 January 2000

Updated: 25 August 2003

Reviewed: 4 March 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 4.2x � 5.3.x

Subject: How to Manually Register and Un-register the Aloha Software Applications

============================================================================

Summary

The ALOHA^� application software Back-of-House (BOH) CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) applications are capable of running as a Microsoft^� Windows^� service, but you must register them as such.� Besides Control Server and EDC Server, several other Aloha software application files also require registration.� All of these applications are automatically registered when you install or upgrade the Aloha application software using the Aloha Installation CD, but some situations may require you to manually un-register and register applications.

Information

If you are using Windows 95 on the file server, you must install and configure DCOM before performing the procedures in this document.� DCOM is included with all other approved operating systems, so you do not need to install it on them.� Refer to document AKBID1049 for more information on installing DCOM.

If manually installing a new version of the Aloha application software on a file server already using it, you must unregister the previous version before installing and registering the new version.� Always restart the system after uninstalling previous versions of the Aloha application software.

If you install the Aloha application software versions 5.2x and higher using the installation CD, the setup application leaves copies of the batch files that it uses to un-register and register BOH applications in the root folder of the drive or partition in which the Aloha application software was installed.� You can use these batch files to manually un-register and register BOH applications, or you can also use the information in this document to build your own customer batch files for versions 4.2x and higher.

Refer to document AKBID1162 for more information on the benefits of running the Aloha application software components as a service.

Un-register Control Server Versions 4.2x through 4.4x

To un-register Control Server, open a command prompt and navigate to the BIN folder.� Type the following commands:

CTLSVR.EXE /UNREGSERVER

REGSVR32.EXE /U CTLSVRPS.DLL

REGSVR32.EXE /U CALCEDIT.OCX (Version 4.4x only)

REGSVR32.EXE /U QWERTY.OCX (Version 4.4x only)

Register Control Server Versions 4.2x through 4.4x as a Service

To register Control Server as a service, open a command prompt and navigate to the BIN folder.� Type the following commands:

CTLSVR.EXE /SERVICE

REGSVR32.EXE CTLSVRPS.DLL

REGSVR32.EXE CALCEDIT.OCX (Version 4.4x only)

REGSVR32.EXE QWERTY.OCX (Version 4.4x only)

Register Control Server Versions 4.2x through 4.4x not as a Service

To register Control Server to not run as a service, open a command prompt and navigate to the BIN folder.� Type the following commands:

CTLSVR.EXE /REGSERVER

REGSVR32.EXE CTLSVRPS.DLL

REGSVR32.EXE CALCEDIT.OCX (Version 4.4x only)

REGSVR32.EXE QWERTY.OCX (Version 4.4x only)

Un-register EDC Server Versions 4.2x through 4.4x

To un-register EDC Server, open a command prompt and navigate to the BIN folder.� Type the following commands:

EDCSVR.EXE /UNREGSERVER

REGSVR32.EXE /U EDCSVRPS .DLL

Register EDC Server Versions 4.2x through 4.4x as a Service

To register EDC Server as a service, open a command prompt and navigate to the BIN folder.� Type the following commands:

EDCSVR.EXE /SERVICE

REGSVR32.EXE EDCSVRPS.DLL

Register EDC Server Versions 4.2x through 4.4x not as a Service

To register EDC Server to not run as a service, open a command prompt and navigate to the BIN folder.� Type the following commands:

EDCSVR.EXE /REGSERVER

REGSVR32.EXE EDCSVRPS.DLL

Un-register Aloha Manager and Control Server Versions 5.0x through 5.2x

To un-register Aloha Manager and Control Server, open a command prompt and navigate to the BIN folder.� Type the following commands:

ALOHAMGR.EXE /UNREGSERVER

CTLSVR.EXE /UNREGSERVER

REGSVR32.EXE /U AMGRPS.DLL

REGSVR32.EXE /U AMGRSHIM.DLL (Version 5.0x only)

REGSVR32.EXE /U CTL4X.DLL

REGSVR32.EXE /U EDTPUNCH.DLL

REGSVR32.EXE /U MNT4X.DLL

REGSVR32.EXE /U USERTOOL.DLL

REGSVR32.EXE /U ASECPS.DLL

REGSVR32.EXE /U ARSEC.DLL

REGSVR32.EXE /U ARSECPS.DLL

ALOHASEC.EXE /UNREGSERVER

REGSVR32.EXE /U ALOHALAB.DLL

REGSVR32.EXE /U CTLSVRPS.DLL

REGSVR32.EXE /U CALCEDIT.OCX

REGSVR32.EXE /U QWERTY.OCX

REGSVR32.EXE /U CRYSTL32.OCX (Versions 5.2x and higher)

Register Aloha Manager and Control Server Versions 5.0x through 5.2x as a Service

To register Aloha Manager with Control Server running as a service, open a command prompt and navigate to the BIN folder.� Type the following commands:

ALOHAMGR.EXE /REGSERVER

ALOHASEC.EXE /REGSERVER

CTLSVR.EXE /SERVICE

REGSVR32.EXE AMGRPS.DLL

REGSVR32.EXE AMGRSHIM.DLL (Version 5.0x only)

REGSVR32.EXE ASECPS.DLL

REGSVR32.EXE ARSEC.DLL

REGSVR32.EXE ARSECPS.DLL

REGSVR32.EXE MNT4X.DLL

REGSVR32.EXE EDTPUNCH.DLL

REGSVR32.EXE CTL4X.DLL

REGSVR32.EXE USERTOOL.DLL

REGSVR32.EXE CTLSVRPS.DLL

REGSVR32.EXE ALOHALAB.DLL

REGSVR32.EXE CALCEDIT.OCX

REGSVR32.EXE QWERTY.OCX

REGSVR32.EXE CRYSTL32.OCX (Version 5.2x and higher)

If you are using Control Server versions 5.230 and higher and you are using the Microsoft Windows NT^�, Windows 2000, or Windows XP operating system, Control Server prompts you for the user configuration.� This is the user with which Control Server will log in.� You can instruct Control Server to use the Windows local system account (the default configuration in versions 5.229 and lower), or you can configure a specific user name and password.� You must configure a specific login in instances where the operating system on the Front-of-House (FOH) terminals does not enable network access by the Windows local system account or if you are using Windows 2000 on the file server (refer to document AKBID1197).�

Configuring Control Server to login using the local system account on a file server using Windows 2000 can result in memory leaks.� You must use a specific user name and password.� Refer to document AKBID1197 for more information.

You can use the /LOCALACCOUNT command line variable to instruct Control Server to register using the Windows local system account without prompting the user.� For example:

CTLSVR.EXE /SERVICE /LOCALACCOUNT

You can use the /ACCOUNTNAME and /PASSWORD command line variables to instruct Control Server to register using a specific user name and password.� For example:

CTLSVR.EXE /SERVICE /ACCOUNTNAME .\<user name> /PASSWORD <password>

If you are using a domain account, you can specify the domain name using the following command line:

CTLSVR.EXE /SERVICE /ACCOUNTNAME <domain name>\<user name> /PASSWORD <password>

The batch file automatically created by the Aloha application software setup application (as explained previously in this document) uses the /SNAME and /SPWD command line variables instead of the /ACCOUNTNAME and /PASSWORD variables to designate that the user name and password in the batch file are encrypted.� For example:

CTLSVR.EXE /SERVICE /SNAME <encrypted user name> /SPWD <encrypted password>

Register Aloha Manager Control Server Versions 5.0x through 5.2x not as a Service

To register Aloha Manager with Control Server not running as a service, open a command prompt and navigate to the BIN folder.� Type the following commands:

ALOHAMGR.EXE /REGSERVER

ALOHASEC.EXE /REGSERVER

CTLSVR.EXE /REGSERVER

REGSVR32.EXE AMGRPS.DLL

REGSVR32.EXE AMGRSHIM.DLL (Version 5.0x only)

REGSVR32.EXE ASECPS.DLL

REGSVR32.EXE ARSEC.DLL

REGSVR32.EXE ARSECPS.DLL

REGSVR32.EXE MNT4X.DLL

REGSVR32.EXE EDTPUNCH.DLL

REGSVR32.EXE CTL4X.DLL

REGSVR32.EXE USERTOOL.DLL

REGSVR32.EXE CTLSVRPS.DLL

REGSVR32.EXE ALOHALAB.DLL

REGSVR32.EXE CALCEDIT.OCX

REGSVR32.EXE QWERTY.OCX

REGSVR32.EXE CRYSTL32.OCX (Version 5.2x and higher)

Un-register EDC Server Versions 5.0x through 5.2x

To un-register EDC Server, open a command prompt and navigate to the BIN folder.� Type the following commands:

EDCSVR.EXE /UNREGSERVER

REGSVR32.EXE /U EDCSVRPS.DLL

REGSVR32.EXE /U EDCSEC.DLL

Register EDC Server Versions 5.0x through 5.2x as a Service

To register EDC Server to run as a service, open a command prompt and navigate to the BIN folder.� Type the following commands:

EDCSVR.EXE /SERVICE

REGSVR32.EXE EDCSVRPS.DLL

REGSVR32.EXE EDCSEC.DLL

If you are using EDC Server versions 5.230 and higher and you are using the Windows NT, Windows 2000, or Windows XP operating system, EDC Server prompts you for the user configuration.� This is the user with which EDC Server will log in. �You can instruct EDC Server to use the Windows local system account (the default configuration in versions 5.229 and lower), or you can configure a specific user name and password.� You must configure a specific login in instances where the operating system on the FOH terminals does not enable network access by the Windows local system account or if you are using Windows 2000 on the file server (refer to document AKBID1197).

Configuring EDC Server to login using the local system account on a file server using Windows 2000 can result in memory leaks.� You must use a specific user name and password.� Refer to document AKBID1197 for more information.

You can use the /LOCALACCOUNT command line variable to instruct EDC Server to register using the Windows local system account without prompting the user.� For example:

EDCSVR.EXE /SERVICE /LOCALACCOUNT

You can use the /ACCOUNTNAME and /PASSWORD command line variables to instruct EDC Server to register using a specific user name and password.� For example:

EDCSVR.EXE /SERVICE /ACCOUNTNAME .\<user name> /PASSWORD <password>

If you are using a domain account, you can specify the domain name using the following command line:

EDCSVR.EXE /SERVICE /ACCOUNTNAME <domain name>\<user name> /PASSWORD <password>

The batch file automatically created by the Aloha application software setup application (as explained previously in this document) uses the /SNAME and /SPWD command line variables instead of the /ACCOUNTNAME and /PASSWORD variables to designate that the user name and password in the batch file are encrypted.� For example:

EDCSVR.EXE /SERVICE /SNAME <encrypted user name> /SPWD <encrypted password>

Register EDC Server Versions 5.0x through 5.2x not as a Service

To register EDC Server to not run as a service, open a command prompt and navigate to the BIN folder.� Type the following commands:

EDCSVR.EXE /REGSERVER

REGSVR32.EXE EDCSVRPS.DLL

REGSVR32.EXE EDCSEC.DLL

Silent Registration Options

All registered Aloha software applications and REGSVR32.EXE support silent registration which disables the confirmation prompts (and error prompts) following file registration.� The following switches are used for silent operation:

Silent operation disables error prompts, but you will not be informed of errors that may inhibit the application or .DLL registration process.

CTLSVR.EXE and REGSVR32.EXE use '/S' to enable silent operation.� For example:

CTLSVR.EXE /REGSERVER /NONET /S

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S CTLSVRPS.DLL

EDVSVR.EXE uses '/S ' to enable silent operation.� EDCSVR.EXE does not recognize the '/S ' variable unless there is a space after the 'S' (use '/S ', not '/S'.) For example:

EDCSVR.EXE /REGSERVER /NONET /S

ALOHAMGR.EXE and ALOHASEC.EXE use 'QUIET' to enable silent operation.� For example:

ALOHAMGR.EXE /REGSERVERQUIET

ALOHASEC.EXE /REGSERVERQUIET

ALOHAMGR.EXE /SERVICEQUIET

ALOHASEC.EXE /SERVICEQUIET

Extended Information

ATL.DLL

Aloha Manager requires you to register ATL.DLL.� This file has already been registered and does not need to be registered again if the Aloha application software was originally installed using the versions 5.0x or higher Aloha Installation CD.

The ATL.DLL file differs between Windows 95, Windows 98, and Windows Millennium Edition (Me) operating systems, and the Windows NT, Windows 2000, and Windows XP operating systems.� You can find ATL.DLL for Windows 95, Windows 98, and Windows Me in the W95DLL.ZIP file in the ALOHATS folder on the installation CD.� You can find ATL.DLL for Windows NT, Windows 2000, and Windows XP can be found in the WNTDLL.ZIP file in the ALOHATS folder on the installation CD.

Do not overwrite newer versions of ATL.DLL.

If you need to manually register the file, you must copy ATL.DLL to the Windows System folder.� If you are using Windows NT, Windows 2000, or Windows XP, place it in the Windows SYSTEM32 folder.� If you are using Windows 95, Windows 98, or Windows Me, place it in the Windows SYSTEM folder.� If the file already exists in the folder, replace it only if the existing file is older.

Navigate to the Windows System folder containing the file, and use the following command line to register the file:

REGSVR32.EXE ATL.DLL

Caveats

If the Aloha application software variables are not defined properly on the system, they need to be added to the command lines described in this document.� Refer to document AKBID1010 for more information on the Aloha application software variables.

Silent operation disables error prompts, but you will not be informed of errors that may inhibit the application or .DLL registration process.

Configuring Control Server to login using the local system account on a file server using Windows 2000 can result in memory leaks.� You must use a specific user name and password.� Refer to document AKBID1197 for more information.

Configuring EDC Server to login using the local system account on a file server using Windows 2000 can result in memory leaks.� You must use a specific user name and password.� Refer to document AKBID1197 for more information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

Aloha Credit Card User Manual

AKBID1010 Aloha Application Software System Environment Variables

AKBID1049 Installing DCOM for Windows

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1197 Assigning Logins to Aloha Services

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1019

�

EDC Process

EDC Process

============================================================================

AKBID1020

Created: 16 February 2000

Updated: 4 February 2004

Reviewed: 4 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 3.5x � 5.3.x

Subject: The Aloha Application Software EDC Process

============================================================================

Summary

The ALOHA^� application software Electronic Draft Capture (EDC) application uses a process of request and answer files to communicate between the Front-of-House (FOH) Point-of-Sale (POS) terminals and the Back-of-House (BOH) file server.� This document explains this and other EDC processes to help you better support the Aloha application software.

Information

The EDC Authorization Process

Request and Answer files are the basis of FOH interaction with EDC.� When a user performs an action on the FOH, such as applying, adjusting, or voiding an EDC payment, the master terminal creates a nnnnnnnn.REQ file in the EDC folder on the fileserver.�

The EDC program is normally scanning for new .REQ files at least once per second.� If a .REQ file is found, EDC immediately renames it to a .HLD file, indicating that processing has begun.�

After EDC processes the request file, the response is written out to a .ANS file, and the .HLD file is deleted (for increased debugging ability in versions 5.2.4.0 and higher, the response is first written to a .WRK file, and the .WRK file is renamed to a .ANS file).� The .ANS file is basically identical to the .REQ file, but the APPROVED field indicates whether the action succeeded, and the AUTH or ERROR fields provide additional information.

In addition to writing the response out to an .ANS file, EDC also writes the response out to a TXNmmmmm file in the processor folder for the processor that is handling the batch for the transaction.� The TXN files are sequentially numbered, and have identical contents as the .ANS files.� The TXN files in a processor folder make up the current batch for that processor.

The FOH detects the .ANS file, reads it in to parse the response, and deletes the .ANS file.

EDC also generates TXN and .ANS files if a user adjusts EDC transactions in the BOH.� If you have enabled this process in the FOH, the FOH picks up the .ANS files and updates the FOH with the changes (refer to document AKBID3301).

If the EDC application becomes disabled while processing an action, then the .HLD file is left in the EDC folder.� When EDC restarts, it always scans to see if there are any .HLD files.� If it finds any .HLD files, it errors all of them out because it does not know if they went through to the processor or not.� This is what the 'HLD File not processed' error indicates.

EDC uses the following error numbers in the Debugging-Output-Files (debouts) when processing .REQ, .HLD, and .AND files:

Error

Description

1

Could not open file exclusively

2

Could not rename file to *.HLD

3

Could not open file exclusively a second time

4

Failed to open .ANS file

5

Got bad return code from WriteTxnParms

6

Failed to delete .HLD file

The EDC Settlement Process

The following steps occur during settlement:

1.        EDC creates a SETTLING file in the folder of the processor being settled.

2.        EDC dials out to the processor, and sends detailed information about all of the transactions in the batch.� The processor may approve or reject the batch.

3.        EDC deletes the SETTLING file.

4.        The TXN file is created for the settlement transaction.

5.        If settlement failed, nothing else happens.

6.        If settlement succeeds, EDC attempts to archive the current batch by creating a settlement file that contains a header with some batch information and the text of all of the TXN files in the batch.� The name of the settlement file is normally yyyymmdd.STL, where yyyymmdd is the current system date (not the Date-of-Business).� If a settlement file already exists with that name, the settlement file is named yyyymmdd.A, yyyymmdd.B, and so on.

7.        If the settlement file is successfully created, the TXN files are deleted.

8.        A SETTLED marker file is created.

9.        If the archive batch process fails, it is a serious problem.� EDC will display the following message five times: 'Settlement succeeded, but error nn occurred.� CONTACT TECHNICAL SUPPORT and WRITE DOWN the settlement authorization (Error message x of 5).'� The reason this is so serious is that the batch was settled, but was not cleared out for some reason.� This raises the risk of settling the same batch twice and double-billing customers.� The Force Settlement function may be required in this case.

The Force Settlement function is rarely used.� It archives and clears out the current batch, but it does not perform any actual settlement with the processor.� It is intended only in case that the batch has already been settled, but Aloha does not know about it.� This can happen when settlement is interrupted, as described above, or when the processor manually settles a batch on their end to solve a problem.

You can split the .STL file back into the original TXN files using the SPLITSTL.EXE utility.� Refer to document AKBID1012 for more information.

EDC Files

The EDC files typically reside in the EDC folder located in the Aloha application software folder (IBERDIR) on the file server.� You can override this default folder with the EDCPATH environment variable, but EDCPATH is only required for SuperSites.� Each defined processor has its own folder named after the processor inside the EDC folder.

The following table shows the descriptions of the files typically found in the EDC directories:

File

Description

EDC\EDC.INI

EDC Configuration File

EDC\*.REQ

Request files from FOH

EDC\*.HLD

FOH requests currently being processed

EDC\*.ANS

Completed requests

EDC\CHANGED

Marker file indicating to the FOH that at least one file has changed

EDC\<Processor>\TXN*.

TXN files making up the current batch for the processor

EDC\<Processor>\SETTLING

Marker file indicating that Settlement is currently in progress for the processor

EDC\<Processor>\SETTLED

Marker file indicating that Settlement has been completed for the processor.

EDC\<Processor>\yyyymmdd.STL

Settlement file containing all of the TXN files for a settled batch

There is no relationship between the transaction number (as referenced in EDC and EDC errors) and the like numbered TXN file.� For example, an error message referring to transaction 39 does not link to TXN00039.� The only way of determining the transaction number is to use the batch transaction number shown in the Select Transaction dialog when you adjust or void transactions from the BOH.

�

The following table shows the contents of a TXN file:

Manually editing or otherwise manipulating TXN files is highly discouraged.� However, it is useful to understand how they work when dealing with problems.

Field

Description

TYPE

Type of action: AUTHORIZE, PREAUTHORIZE, ADJUST, VOID, CREDIT, FORCE, SETTLE, FORCESETTLE

DOB

Date of Business

DATE

System date

TIME

System time

TERMINAL

Originating FOH terminal, or BOH

MANAGER

If manager approval was required, who did it

EMPLOYEE

FOH Employee performing the action

TABLE

Name of table or quick service order

CHECK

Check number

PAYMENT

Unique payment id

AUTHAMT

Amount to authorize

BATCHAMT

Amount to settle

BATCHTIP

Tip amount to settle

PROCESSOR

Which credit card processor handles this TXN

CARDTYPE

Type of card (VISA, MC, etc.)

CARD

Card number

EXP

Expiration (MMYY)

TRACK1

Track 1 magnetic card information, if available

TRACK2

Track 2 magnetic card information, if available

REF

Reference ID that identifies the batch transaction this action is updating.� A transaction consists of all the TXN files which have the same REF id.

APPROVED

YES if the action succeeded, NO if failed for any reason

AUTH

Authorization code for successful authorizations

ERROR

Error text for failed actions

INFO

Additional internal transaction information needed for settlement

REASON

For void actions, the explanation for the void

NOCAPTURE

Indicates that the authorization succeeded but the transaction can not be settled.� An example would be trying to use an American Express card with CES when CES does not have the restaurant configured to settle American Express transactions.

PROCNO

Processor number of settlement processor.

FILENO

Number of the TXN file

STANDALONE

YES if the action occurred while the FOH was in Spooling (fake authorization) mode.� The transactions are designated with an asterisk (*) on the batch report.

PINDEX

Used for SuperSites only.� Processor index.� Distinguishes which batch the transaction goes into when you have multiple simultaneous batches for a processor.� The processor index is applied from the 'EDC Info' field defined in Terminal Maintenance.

TERMID

Used for SuperSites only. �Terminal ID.� This does not necessarily correspond to the Aloha terminal number.� This is a specific terminal ID to be sent to the processor so that they can report on credit card activity by terminal.� The terminal ID is applied from the 'EDC Info' field defined in Terminal Maintenance.

MICR

Used for Check Authorization only.� Magnetic Ink Character Recognition code along bottom of check.� Check Authorization is not yet supported.

DLL

Used for Check Authorization only.� Drivers License information.� Check Authorization is not yet supported.

CHECKNO

Used for Check Authorization only.� Check Number.� Check Authorization is not yet supported.

STATE

Used for Check Authorization only.� State.� Check Authorization is not yet supported.

ZIP

Used for Check Authorization only.� Zip Code.� Check Authorization is not yet supported.

Enable FOH EDC Debugging Information

In Aloha versions 5.2.7.133 and higher, you can enable additional debugging in the FOH by assigned the DEBUGEDC variable in the ALOHA.INI to a value of 1 (for example, DEBUGEDC=1).� This information includes .REQ file creation and deletion.

Rejected Transaction Files

In versions 4.4x and higher, the Aloha application software enables the ability to write rejected transactions to a file and continue settling a batch that would otherwise be rejected in whole.� Since this not supported by all processors, it is processor specific, and as of this writing, the only processors that support feature are VISANET, CES, FDC, and BUYPASS.�

You can enable or disable this feature in the processor configuration in EDC.EXE (EDC).� The option will be grayed out if the processor does not support this feature.

If a transaction is rejected and this feature is enabled, the rejected transaction will be written to a .REJ file and the settlement process will continue.� You can edit the rejected transactions using 'Edit Rejected Transactions' in the EDC Functions drop-down menu.

Miscellaneous Environment Variables

Variable

DEBUGEXT

Applications

EDCSVR.EXE

Description

Sets the extension of the debugging file.� Do not include the dot.

System Variable Example

N/A

Command Line Example

EDCSVR.EXE /DEBUGEXT <extension>

Variable

DEBUGSCAN

Applications

EDCSVR.EXE

Description

Generates additional EDC terminal-scanning debugging information in the debout files.

System Variable Example

N/A

Command Line Example

EDCSVR.EXE /DEBUGSCAN

Variable

EDCDIR

Applications

EDCSVR.EXE

Description

Sets the EDC folder name.

System Variable Example

SET EDCDIR=<folder name>

Command Line Example

EDCSVR.EXE /EDCDIR <folder>

Variable

EDCSVR

Applications

EDC.EXE

Description

Specifies path to a remote EDCSVR.EXE.�

System Variable Example

N/A

Command Line Example

EDC.EXE /EDCSVR <path>

Variable

EDCPATH

Applications

EDCSVR.EXE, IBER.EXE, IBERQS.EXE

Description

Sets the path to the EDC folder when multiple instances of EDC are running on the same file server.�

System Variable Example

SET EDCPATH=<path>

Command Line Example

IBER.EXE /EDCPATH <path>

Extended Information

Use Winhook to backup the EDC.INI and the EDC .STL files by zipping them up to another location.� Refer to document AKBID1028 for more information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

Aloha Credit Card User Manual

AKBID1010 Aloha Application Software System Environment Variables

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1019 Manually Registering and Un-registering Aloha Applications

AKBID1028 Winhook

AKBID1029 Credit Card Pre-Authorization

AKBID1046 Postponing Daily Batch Settlement

AKBID1050 Remote Aloha EDC

AKBID1062 Property Management Systems

AKBID1095 Stand Alone EDC Server

AKBID1104 Automatic Credit Card Settlement

AKBID1134 Debouts

AKBID1189 EDC Modem Initialization Strings

AKBID1190 Host-based Credit Card Processors

AKBID1191 Common EDC Processor Errors

AKBID1192 Troubleshooting EDC Spooling

AKBID3010 EDCSVR.EXE Registry Variables

AKBID3198 EDC Processors Currently Supported by Aloha

AKBID3199 Credit Card Lengths and Prefixes

AKBID3200 Increasing Credit Card Authorization Speed

AKBID3201 Temporarily Moving EDC TXN Files

AKBID3202 EDC Configuration not Saving Properly

AKBID3203 Duplicate Credit Card Transactions

AKBID3204 US Robotics 56K Modem Hang-up Issue

AKBID3205 FOH Hangs on Starting EDC

AKBID3301 Enable the FOH to Process BOH EDC Transactions

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1020

Windows 95 File Server Setup

Microsoft Windows 95 File Server Setup

============================================================================

AKBID1021

Created: 22 December 1999

Updated: 21 February 2003

Reviewed: 1 March 2004

Microsoft Windows Versions: Windows 95

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

Subject: Microsoft Windows 95 File Server Setup

============================================================================

Summary

The ALOHA^� application software requires several specialized settings (as well as several preferred settings) in the Microsoft^� Windows^� 95 operating system (OS) to properly run on the file server.� If you are using the file server to run both Aloha Front-of-House (FOH) and Back-of-House (BOH) together, refer to document AKBID1023.

Information

This document is written for users familiar with Microsoft Windows 95.� This document describes procedures for Windows 95 OSR2 (version B) and Windows 95 OSR2.5 (version C).� If you are not using one of these two versions of Windows 95, you need to upgrade your operating system (OS).

Since some computers come with Windows 95 preloaded while others do not, this document is based on editing the settings of Windows 95.� Users who are installing Windows 95 from scratch or upgrading another OS to Windows 95 can still use this document either by employing these instructions after the Windows 95 installation or by making many of these changes during the Windows 95 installation.

Drive Sizes and Partitions

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

The most important settings in the Aloha application software involve the network settings.� To access these settings, select Start/Settings/Control Panel/Network or right-click the Network Neighborhood icon on your desktop and select Properties.

The Configuration tab contains a Components area and Primary Network Logon type.� The components area should have Client for Microsoft Networks as the only network client installed.� You may have others, but these should only be added if absolutely needed.� The correct drivers for your network interface card (NIC) should also be listed.�

The Aloha application software uses either TCP/IP or NetBEUI as its network protocol.� Select either one, but both the file server and the terminals must use the same protocol.� To assign the protocol for the Aloha application software to use (refer to document AKBID1018), double-click the desired protocol, select the Advanced tab, and select 'Set this protocol to be the default protocol'.� If you select TCP/IP, Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure that terminals always have an address assigned to them.� The Aloha application software will not function without an IP address assigned to the terminal.� You may have multiple protocols installed as long as the proper protocol for the Aloha application software has been marked as such.�

To add file and print sharing for the Aloha application software, click the File and Print Sharing button and select both options.� Print Sharing may be left disabled if you are not using Windows based printer shares for the FOH or remote Control/Maintenance servers.�

The Primary Logon Type is typically set to Windows Logon.� This log in enables Windows 95 to skip the prompt for the user name and password if the password is blank.� Setting this as Client for Microsoft Networks prompts for the user name and password regardless if the password is blank.� If Client for Microsoft Networks must be used as the Primary network logon, use the Microsoft Windows 95 TweakUI utility to automatically enter the user name and password.� TweakUI can be downloaded from the Aloha Technologies FTP site as TWEAKUI.ZIP.� Aloha Technologies installs this utility regardless of the Primary Logon Type setting.

The Identification tab contains the network name and workgroup name.� Aloha Technologies uses ALOHABOH by default.� A different name can be used if desired.� Set the Workgroup name the same on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the Workgroup name, but this name can be of your choice as long as it is consistent throughout the Aloha application software.� The Computer Description is solely to your discretion.

Ensure that 'Share-level access control' is selected under the Access Control tab.� Only experienced Domain administrators should consider using 'User-level access control'.

The Aloha Application Software Share Name

The Aloha application software requires a network share name of BOOTDRV.� This is the required name.� This share needs to be applied to the root folder or drive in which the Aloha folder resides.� To set the share, right-click on the drive or folder and choose Sharing.� Set the Share Name to BOOTDRV, the Access Type to Full, and leave the password fields blank.

If the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.� Some clients prefer to place the Aloha application software in a special folder in order to limit the shared files, and, therefore, enhance security.� Sharing the entire drive in which the Aloha application software resides also shares other files that reside on the drive, such as Windows.

Display Settings

To access the Display settings, select Start/Settings/Control Panel/Display or right-click the Windows desktop and select Properties.� Select the Settings tab.� Set the Color palette to 256 Colors or higher.� Aloha Technologies typically uses 16-bit color.� The Aloha application software can be run on both a 640x480 pixel display and an 800x600 pixel display, however, Aloha Technologies prefers 800x600 (or better) resolution.

Aloha Technologies typically does not use a screen saver on the file server since some screen savers (the Open GL based screen savers in particular) can sap processor speed.

Time Zone & Daylight Savings

For the file server and all terminals to display the correct time and adjust to Daylight Savings changes properly, the Time and Date settings must be properly configured in Windows.� Select Start/Settings/Control Panel/Date/Time or double-click the time displayed on the task bar.� Ensure the date and time are correct.� Ensure the date and time are correct on the Date & Time tab.� Ensure the correct time zone is chosen on the Time Zone tab.� This time zone needs to be the same on all terminals and the file server.� If the area observes Daylight Savings, then the 'Automatically adjust clock for daylight savings changes' option must be selected on all terminals and the file server.� This can be turned on or off, but it needs to be consistent throughout the Aloha application software.

Scandisk Autoscan & Settings

By default, if Windows is shut down improperly, it runs Scandisk the next time the system is started.� The problem resides in the prompt to do so.� A prompt displays a scolding for improperly shutting down Windows and to press any key to continue and run Scandisk.� This can cause a delay when a file server is restarting, which increases the time the Aloha application software is disrupted.� The MSDOS.SYS file must be adjusted for Windows to automatically run Scandisk when needed without prompting for user interaction.�

Open Explorer and navigate to C:\.� Right-click the MSDOS.SYS file (if the file is not displayed, adjust your Explorer settings using the directions in the Explorer Settings portion of this document) and choose Properties.� Clear the 'Read-only' option and close the Properties window.� Double-click the MSDOS.SYS file and choose to open it with Notepad.� Under the [OPTIONS] section, add a new line which reads AUTOSCAN=2.� Close Notepad and save your changes.� Re-enable the Read-only attribute for the MSDOS.SYS file.� (Some terminals come from the manufacturer with the AUTOSCAN option already enabled.)

Once Scandisk is set to run properly, if it finds any problems on the drive, it prompts for answers.� Again, this can cause a delay when a file server is restarting, which increases the time the Aloha application software may be disrupted.� To alleviate this problem, Aloha Technologies offers a SCANDISK.INI that keeps Windows from prompting for 95% of the questions.� This SCANDISK.INI can be downloaded from the Aloha Technologies FTP site as SCANDISK.ZIP.� Place this file in the Windows COMMAND folder overwriting the one that currently exists.

Login Name

Refer to document AKBID1006 for more information on user login information.

To clear the current user names and passwords, delete *.PWL from the Windows folder to remove all users.� Select Start/Shutdown.� Select 'Close all programs and log in as a different user' and click Yes.� Windows logs the current user out and prompts for a user name and password.� Enter the desired user and password and log in to Windows.

VNetBIOS

Windows 95 might experience network problems with restaurants using five or more terminals.� To ensure that terminals do not experience these problems, Microsoft issued a new VNETBIOS.VXD that you can download from the Aloha Technologies FTP site as VNETBIOS.ZIP.� Aloha Technologies installs this .VXD file on all terminals, regardless of the system's size.� Refer to document AKBID1011 for more information.

Once you have the new .VXD, place it in the Windows SYSTEM folder overwriting the current version.� Edit the SYSTEM.INI in the Windows folder, and add a new line in the [386Enh] section that states NUMHCBS=x.� Replace x with a number four times the number of terminals in the system, but not less than 80 nor exceeding 200.� The default for this number is 100.� For example, a 25 terminal system would use NUMHCBS=100.� Do not exceed 100 unless you have more than 25 terminals.

To ensure that Windows does not overwrite the updated VNETBIOS.VXD following network configuration changes, place a copy of the updated VNETBIOS.VXD in the same folder as the Windows CAB files.

AUTOEXEC.BAT

Aloha Technologies uses a default AUTOEXEC.BAT (before the Aloha application software is installed) which contains only two lines:

SET PATH=%PATH%

DOSKEY

The first line creates a PATH variable that Windows 95 does not install by default.� If the path statement does not reside in AUTOEXEC.BAT, some software packages create a new path line that does not include the Windows default path.� With this line, the software will most likely append to the line and preserve the Windows path.

The second line installs DosKey.� DosKey is an application used in a command prompt that recalls previous lines typed via the arrow up and down keys.� For users accustomed to a command prompt environment, it is a welcome feature.

Install Aloha Software

Once Windows 95 is set up according to the standards outlined in this document and you can view the network, use the Aloha Application Software Installation CD to install the Aloha application software.

Run SETUPPOS.EXE /ADVANCED from the Aloha POS CD.� The setup program walks you through the rest of the installation.

Refer to document AKBID1162 for more information on running CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) as Windows services.

Extended Information

For extra security, Windows offers a Policy Editor (POLEDIT.EXE) for Windows 95 that can lock the user out of most Windows 95 features.� Microsoft provides information on this through their Knowledge Base and can be accessed at http://support.microsoft.com.� Too much security can increase the support time required to address a problem, and, therefore, increase the down time.

Caveats

There have been instances where Dial-Up Networking was installed on Windows 95 and caused conflicts with networking abilities in the Aloha application software.� The reason is currently unknown.

When a file server is running Windows 95, Windows 98, or Windows Millennium Edition (Me), Aloha Technologies does not choose to run CTLSVR.EXE and EDCSVR.EXE as services.� Running them as services in a Windows 95, Windows 98, or Windows Me environment, although possible and stable, creates problems when Control Server or EDC Server have to be restarted and/or replaced.� It is not as easy a task to stop and start a service in Windows 95, Windows 98, and Windows Me as it is in Windows NT.� Refer to document AKBID1162 for more information on running Control Server and EDC Server as Windows services.

============================================================================

See also:

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1009 Microsoft Windows 95 FOH Terminal Setup

AKBID1010 Aloha Application Software System Environment Variables

AKBID1011 Windows 9x VNETBIOS.VXD Patch

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1018 Network Lana Numbers

AKBID1023 Microsoft Windows 95 File Server/Terminal Setup

AKBID1028 Winhook

AKBID1148 Backup Procedures

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1021 stage staging

Windows 98 File Server Setup

Windows 98 File Server Setup

============================================================================

AKBID1022

Created: 6 January 2000

Updated: 21 February 2003

Reviewed: 1 March 2004

Microsoft Windows Versions: Windows 98

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

Subject: Windows 98 File Server Setup

============================================================================

Summary

The ALOHA^� application software requires several specialized settings (as well as several preferred settings) in the Microsoft^� Windows^� 98 operating system (OS) to properly run on the file server.� If you are using the file server to run both Aloha Front-of-House (FOH) and Back-of-House (BOH) together, refer to document AKBID1024.

Information

This document is written for users familiar with Microsoft Windows 98.

Since some computers come with Windows 98 preloaded while others do not, this document is based on editing the settings of Windows 98.� Users who are installing Windows 98 from scratch or upgrading another OS to Windows 98 can still use this document either by employing these instructions after the Windows 98 installation or by making many of these changes during the Windows 98 installation.

Drive Sizes & Partitions

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

The most important settings in the Aloha application software involve the network settings.� To access these settings, select Start/Settings/Control Panel/Network or right-click the Network Neighborhood icon on your desktop and select Properties.

The Configuration tab contains a Components area and Primary Network Logon type.� The components area should have Client for Microsoft Networks as the only network client installed.� You may have others, but these should only be added if absolutely needed.� The correct drivers for your network interface card (NIC) should also be listed.�

The Aloha application software uses either TCP/IP or NetBEUI as its network protocol.� Select either one, but both the file server and the terminals must use the same protocol.� To assign the protocol for the Aloha application software to use (refer to document AKBID1018), double-click the desired protocol, select the Advanced tab, and select 'Set this protocol to be the default protocol'.� If you select TCP/IP, Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure that terminals always have an address assigned to them.� The Aloha application software will not function without an IP address assigned to the terminal.� You may have multiple protocols installed as long as the proper protocol for the Aloha application software has been marked as such.�

To add file and print sharing for the Aloha application software, click the File and Print Sharing button and select both options.� Print Sharing may be left disabled if you are not using Windows based printer shares for the FOH or remote Control/Maintenance servers.�

The Primary Logon Type is typically set to Windows Logon.� This log in enables Windows 98 to skip the prompt for the user name and password if the password is blank.� Setting this as Client for Microsoft Networks prompts for the user name and password regardless if the password is blank.� If Client for Microsoft Networks must be used as the Primary network logon, use the Microsoft Windows 98 TweakUI utility to automatically enter the user name and password.� TweakUI can be downloaded from the Aloha Technologies� FTP site as TWEAKUI.EXE.� Aloha Technologies installs this utility regardless of the Primary Logon Type setting.

The Identification tab contains the network name and workgroup name.� Aloha Technologies uses ALOHABOH by default.� A different name can be used if desired.� Set the Workgroup name the same on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the Workgroup name, but this name can be of your choice as long as it is consistent throughout the Aloha application software.� The Computer Description is solely to your discretion.

Ensure that 'Share-level access control' is selected under the Access Control tab.� Only experienced Domain administrators should consider using 'User-level access control'.

Aloha Share Name

The Aloha application software requires a network share name of BOOTDRV.� This is the required name.� This share needs to be applied to the root folder or drive in which the Aloha folder resides.� To set the share, right-click the drive or folder and choose Sharing.� Set the Share Name to BOOTDRV, the Access Type to Full, and leave the password fields blank.

If the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.� Some clients prefer to place the Aloha application software in a special folder in order to limit the shared files and, therefore, enhance security.� Sharing the entire drive in which the Aloha application software resides also shares other files that reside on the drive such as Windows.

Display Settings

To access the Display settings, select Start/Settings/Control Panel/Display or right-click the Windows desktop and select Properties.� Select the Settings tab.� Set the Color palette to 256 Colors or higher.� Aloha Technologies typically uses 16-bit color.� The Aloha application software can be run on both a 640x480 pixel display and an 800x600 pixel display, however, Aloha Technologies prefers 800x600 (or better) resolution.

Aloha Technologies typically does not use a screen saver on the file server since some screen savers (the Open GL based screen savers in particular) can sap processor speed.

Time Zone & Daylight Savings

For the file server and all terminals to display the correct time and adjust to Daylight Savings changes properly, the Time and Date settings must be properly configured in Windows.� Select Start/Settings/Control Panel/Date/Time or double-click the time displayed on the task bar.� Ensure the date and time are correct.� Ensure the date and time are correct on the Date & Time tab.� Ensure the correct time zone is chosen on the Time Zone tab.� This time zone needs to be the same on all terminals and the file server.� If the area observes Daylight Savings, then the 'Automatically adjust clock for daylight savings changes' option must be selected on all terminals and the file server.� This can be turned on or off, but it needs to be consistent throughout the Aloha application software.

Scandisk Autoscan & Settings

By default, if Windows is shut down improperly, it runs Scandisk the next time the system is started.� If it finds any problems on the drive, it prompts for answers.� Again, this can cause a delay when a file server is restarting, which increases the time the Aloha application software may be disrupted.� To alleviate this problem, Aloha Technologies offers a SCANDISK.INI that keeps Windows from prompting for 95% of the questions.� This SCANDISK.INI can be downloaded from the Aloha Technologies� FTP site as SCANDISK.ZIP.� Place this file in the Windows COMMAND folder overwriting the one that currently exists.

Login Name

Refer to document AKBID1006 for more information on user login information.

To clear the current user names and passwords, delete *.PWL from the Windows folder to remove all users.� Select Start/Shutdown.� Select 'Close all programs and log in as a different user' and click Yes.� Windows logs the current user out and prompts for a user name and password.� Enter the desired user and password and log in to Windows.

VNetBIOS

Windows 98 might experience network problems with restaurants using five or more terminals.� To ensure that terminals do not experience these problems, Microsoft issued a new VNETBIOS.VXD that you can download from the Aloha Technologies FTP site as VNETBIOS.ZIP.� Aloha Technologies installs this .VXD file on all terminals, regardless of the system's size.� Refer to document AKBID1011 for more information.

Once you have the new .VXD, place it in the Windows SYSTEM folder overwriting the current version.� Edit the SYSTEM.INI in the Windows folder, and add a new line in the [386Enh] section that states NUMHCBS=x.� Replace x with a number four times the number of terminals in the system, but not less than 80 nor exceeding 200.� The default for this number is 100.� For example, a 25 terminal system would use NUMHCBS=100.� Do not exceed 100 unless you have more than 25 terminals.

To ensure that Windows does not overwrite the updated VNETBIOS.VXD following network configuration changes, place a copy of the updated VNETBIOS.VXD in the same folder as the Windows CAB files.

AUTOEXEC.BAT

Aloha Technologies uses a default AUTOEXEC.BAT (before the Aloha application software is installed) which contains only two lines:

SET PATH=%PATH%

DOSKEY

The first line creates a PATH variable that Windows 98 does not install by default.� If the path statement does not reside in AUTOEXEC.BAT, some software packages create a new path line that does not include the Windows default path.� With this line, the software will most likely append to the line and preserve the Windows path.

The second line installs DosKey.� DosKey is an application used in a command prompt that recalls previous lines typed via the arrow up and down keys.� For users accustomed to a command prompt environment, it is a welcome feature.

Install Aloha Software

Once Windows 98 is set up according to the standards outlined in this document and you can view the network, use the Aloha Application Software Installation CD to install the Aloha application software.

Run SETUPPOS.EXE /ADVANCED from the Aloha POS CD.� The setup program walks you through the rest of the installation.

Refer to document AKBID1162 for more information on running CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) as Windows services.

Extended Information

For extra security, Windows offers a Policy Editor (POLEDIT.EXE) for Windows 98 that can lock the user out of most Windows 98 features.� Microsoft provides information on this through their Knowledge Base and can be accessed at http://support.microsoft.com.� Too much security can increase the support time required to address a problem, therefore, increasing the down time.

Caveats

There have been instances where Dial-Up Networking was installed on Windows 98 and caused conflicts with networking abilities in the Aloha application software.� The reason is currently unknown.

When a file server is running Windows 95, Windows 98, or Windows Millennium Edition (Me), Aloha Technologies does not choose to run CTLSVR.EXE and EDCSVR.EXE as services.� Running them as services in a Windows 95, Windows 98, or Windows Me environment, although possible and stable, creates problems when Control Server or EDC Server have to be restarted and/or replaced.� It is not as easy a task to stop and start a service in Windows 95, Windows 98, and Windows Me as it is in Windows NT.� Refer to document AKBID1162 for more information on running Control Server and EDC Server as Windows services.

============================================================================

See also:

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1010 Aloha Application Software System Environment Variables

AKBID1011 Windows 9x VNETBIOS.VXD Patch

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1013 Microsoft Windows 98 FOH Terminal Setup

AKBID1018 Network Lana Numbers

AKBID1024 Microsoft Windows 98 File Server/Terminal Setup

AKBID1028 Winhook

AKBID1148 Backup Procedures

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1022 stage staging

Windows 95 File Server/Terminal Setup

Microsoft Windows 95 File Server/Terminal Setup

============================================================================

AKBID1023

Created: 30 March 2000

Updated: 21 February 2003

Reviewed: 1 March 2004

Microsoft Windows Versions: Windows 95

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x - 5.3.x

Subject: Microsoft Windows 95 File Server and Terminal on the Same Computer Setup

============================================================================

Summary

The ALOHA^� application software requires several specialized settings (as well as several preferred settings) in the Microsoft^� Windows^� 95 operating system (OS) to properly run on the run both Aloha Front-of-House (FOH) and Back-of-House (BOH) together on the same computer.� If you are using the computer as a file server only, refer to document AKBID1021.� If you are using the computer as a terminal only, refer to document AKBID1009.

Refer to document AKBID1116 for more information on the limitations of running both the FOH and BOH together on the same PC.

Information

This document is written for users familiar with Microsoft Windows 95.� This document describes procedures for Windows 95 OSR2 (version B) and Windows 95 OSR2.5 (version C).� If you are not using one of these two versions of Windows 95, you need to upgrade your operating system (OS).

Since some computers come with Windows 95 preloaded while others do not, this document is based on editing the settings of Windows 95.� Users who are installing Windows 95 from scratch or upgrading another OS to Windows 95 can still use this document either by employing these instructions after the Windows 95 installation or by making many of these changes during the Windows 95 installation.

Drive Partitions and Sizes

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

The most important settings in the Aloha application software involve the network settings.� To access these settings, select Start/Settings/Control Panel/Network or right-click the Network Neighborhood icon on your desktop and select Properties.

The Configuration tab contains a Components area and Primary Network Logon type.� The components area should have Client for Microsoft Networks as the only network client installed.� You may have others, but these should only be added if absolutely needed.� The correct drivers for your network interface card (NIC) should also be listed.�

The Aloha application software can use either TCP/IP or NetBEUI as its network protocol.� Select either one, but both the file server/terminal and the other terminals must use the same protocol.� To assign the protocol for the Aloha application software to use (refer to document AKBID1018), double-click the desired protocol, select the Advanced tab, and select 'Set this protocol to be the default protocol'.� If you select TCP/IP, Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure that terminals always have an address assigned to them.� The Aloha application software will not function without an IP address assigned to the terminal.� You may have multiple protocols installed as long as the proper protocol for the Aloha application software has been marked as such.�

To add file and print sharing for the Aloha application software, click the File and Print Sharing button and select both options.� Print Sharing may be left disabled if you are not using Windows based printer shares for the FOH.�

The Primary Logon Type is typically set to Windows Logon.� This log in enables Windows 95 to skip the prompt for the user name and password if the password is blank.� Setting this as Client for Microsoft Networks prompts for the user name and password regardless if the password is blank.� If Client for Microsoft Networks must be used as the Primary network logon, use the Microsoft Windows 95 TweakUI utility to automatically enter the user name and password.� TweakUI can be downloaded from the Aloha Technologies FTP site as TWEAKUI.ZIP.� Aloha Technologies installs this utility regardless of the Primary Logon Type setting.

Set the terminal's network name under the Identification tab.� Aloha Technologies uses TERM1 (file server/terminal), TERM2, and so on by default.� Different names may be used, but they must follow Aloha application software specifications.� The terminal name must be a common name used on all terminals (the TERMSTR, refer to document AKBID1010) followed by a number designating the terminal's ID number.� Examples include ALOHA1, ALOHA2, TSFOH_1, and TSFOH_2.� In this case, the TERMSTR would be 'ALOHA' or 'TSFOH_'.� Different TERMSTR names can not be used within the same Aloha system.� Spaces can not be used, but underscores can.� Leading zeros can not be used unless they are part of the TERMSTR, but it is not recommended.

Set the Workgroup name the same on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the Workgroup name, but this name can be of your choice as long as it is consistent throughout the Aloha application software.�

The Computer Description is solely to your discretion.

Ensure that 'Share-level access control' is selected under the Access Control tab.� Only experienced Domain administrators should consider using 'User-level access control'.

The Aloha Application Software Share Name

The Aloha application software requires a network share name of BOOTDRV.� This is the required name.� This share needs to be applied to the root folder or drive in which the Aloha folder resides.� To set the share, right-click on the drive or folder and choose Sharing.� Set the Share Name to BOOTDRV, the Access Type to Full, and leave the password fields blank.

If the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.� Some clients prefer to place the Aloha application software in a special folder in order to limit the shared files, and, therefore, enhance security.� Sharing the entire drive in which the Aloha application software resides also shares other files that reside on the drive, such as Windows.

Display Settings

To access the Display settings, select Start/Settings/Control Panel/Display or right-click the Windows desktop and select Properties.� Select the Settings tab.� Set the Color palette to 256 Colors or higher.� Aloha Technologies typically uses 16-bit color.�

Refer to document AKBID1165 for screen resolution settings.

Do not enable a Windows screen saver.

Time Zone & Daylight Savings

For the file server and all terminals to display the correct time and adjust to Daylight Savings changes properly, the Time and Date settings must be properly configured in Windows.� Select Start/Settings/Control Panel/Date/Time or double-click the time displayed on the task bar.� Ensure the date and time are correct.� Ensure the date and time are correct on the Date & Time tab.� Ensure the correct time zone is chosen on the Time Zone tab.� This time zone needs to be the same on all terminals and the file server.� If the area observes Daylight Savings, then the 'Automatically adjust clock for daylight savings changes' option must be selected on all terminals and the file server.� This can be turned on or off, but it needs to be consistent throughout the Aloha application software.

FIFO Buffers

Windows 95 enables First-In-First-Out (FIFO) buffers for each COM port.� These buffers tend to interfere with printers using Xon/Xoff flow control, so Aloha Technologies disables these buffers on all COM ports on all terminals, regardless of the printer type.� (In the event of a printer or COM port failure, a printer using Xon/Xoff flow control may be temporally connected to the port in the future.)

To access the FIFO buffer settings, select Start/Settings/Control Panel/System or right click My Computer and select Properties.� Select the Device Manager tab, and click the plus sign (+) next to Ports to expand it.� Select each port one at a time, and select Properties/Port Settings/Advanced.� Clear 'Use FIFO buffer'.� Repeat for each COM port.� The LPT port does not have this option.

Scandisk Autoscan & Settings

By default, if Windows is shut down improperly, it runs Scandisk the next time the system is started.� The problem resides in the prompt to do so.� A prompt displays a scolding for improperly shutting down Windows and to press any key to continue and run Scandisk.� This can cause a delay when a file server/terminal is restarting, which increases the time the Aloha application software is disrupted.� The MSDOS.SYS file must be adjusted for Windows to automatically run Scandisk when needed without prompting for user interaction.�

Open Explorer and navigate to C:\.� Right-click the MSDOS.SYS file (if the file is not displayed, adjust your Explorer settings using the directions in the Explorer Settings portion of this document) and choose Properties.� Clear the 'Read-only' option and close the Properties window.� Double-click the MSDOS.SYS file and choose to open it with Notepad.� Under the [OPTIONS] section, add a new line which reads AUTOSCAN=2.� Close Notepad and save your changes.� Re-enable the Read-only attribute for the MSDOS.SYS file.� (Some terminals come from the manufacturer with the AUTOSCAN option already enabled.)

Once Scandisk is set to run properly, if it finds any problems on the drive, it prompts for answers.� Again, this can cause a delay when a file server/terminal is restarting, which increases the time the Aloha application software may be disrupted.� To alleviate this problem, Aloha Technologies offers a SCANDISK.INI that keeps Windows from prompting for 95% of the questions.� This SCANDISK.INI can be downloaded from the Aloha Technologies� FTP site as SCANDISK.ZIP.� Place this file in the Windows COMMAND folder overwriting the one that currently exists.

Login Name

Refer to document AKBID1006 for more information on user login information.

To clear the current user names and passwords, delete *.PWL from the Windows folder to remove all users.� Select Start/Shutdown.� Select 'Close all programs and log in as a different user' and click Yes.� Windows logs the current user out and prompts for a user name and password.� Enter the desired user and password and log in to Windows.

VNetBIOS

Windows 95 might experience network problems with restaurants using five or more terminals.� To ensure that terminals do not experience these problems, Microsoft issued a new VNETBIOS.VXD that you can download from the Aloha Technologies FTP site as VNETBIOS.ZIP.� Aloha Technologies installs this .VXD file on all terminals, regardless of the system's size.� Refer to document AKBID1011 for more information.

Once you have the new .VXD, place it in the Windows SYSTEM folder overwriting the current version.� Edit the SYSTEM.INI in the Windows folder, and add a new line in the [386Enh] section that states NUMHCBS=x.� Replace x with a number four times the number of terminals in the system, but not less than 80 nor exceeding 200.� The default for this number is 100.� For example, a 25 terminal system would use NUMHCBS=100.� Do not exceed 100 unless you have more than 25 terminals.

To ensure that Windows does not overwrite the updated VNETBIOS.VXD following network configuration changes, place a copy of the updated VNETBIOS.VXD in the same folder as the Windows CAB files.

AUTOEXEC.BAT

Aloha Technologies uses a default AUTOEXEC.BAT (before the Aloha application software is installed) which contains only two lines:

SET PATH=%PATH%

DOSKEY

The first line creates a PATH variable that Windows 95 does not install by default.� If the path statement does not reside in AUTOEXEC.BAT, some software packages create a new path line that does not include the Windows default path.� With this line, the software will most likely append to the line and preserve the Windows path.

The second line installs DosKey.� DosKey is an application used in a command prompt that recalls previous lines typed via the arrow up and down keys.� For users accustomed to a command prompt environment, it is a welcome feature.

Install Aloha Software

Once Windows 95 is set up according to the standards outlined in this document and you can view the network, use the Aloha Application Software Installation CD to install the Aloha application software.

Run SETUPPOS.EXE /ADVANCED from the Aloha POS CD.� The setup program walks you through the rest of the installation.� You must select 'Run Front of House and Back of House on same PC' on the Aloha Configuration window.

Refer to document AKBID1162 for more information on running CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) as Windows services.

Restarting the FOH

Refer to document AKBID1116 for more information regarding restarting the FOH in this type of environment.�

Extended Information

For extra security, Windows offers a Policy Editor (POLEDIT.EXE) for Windows 95 that can lock the user out of most Windows 95 features.� Microsoft provides information on this through their Knowledge Base and can be accessed at http://support.microsoft.com.� Too much security can increase the support time required to address a problem, and, therefore, increase the down time.

Caveats

There have been instances where Dial-Up Networking was installed on Windows 95 and caused conflicts with networking abilities in the Aloha application software.� The reason is currently unknown.

When a file server is running Windows 95, Windows 98, or Windows Millennium Edition (Me), Aloha Technologies does not choose to run CTLSVR.EXE and EDCSVR.EXE as services.� Running them as services in a Windows 95, Windows 98, or Windows Me environment, although possible and stable, creates problems when Control Server or EDC Server have to be restarted and/or replaced.� It is not as easy a task to stop and start a service in Windows 95, Windows 98, and Windows Me as it is in Windows NT.� Refer to document AKBID1162 for more information on running Control Server and EDC Server as Windows services.

============================================================================

See also:

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1009 Microsoft Windows 95 FOH Terminal Setup

AKBID1010 Aloha Application Software System Environment Variables

AKBID1011 Windows 9x VNETBIOS.VXD Patch

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1018 Network Lana Numbers

AKBID1021 Microsoft Windows 95 File Server Setup

AKBID1028 Winhook

AKBID1116 File Server/Terminal Limitations

AKBID1148 Backup Procedures

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1165 FOH Screen Resolution Settings

AKBID1175 Aloha Terminal Restart Options

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1023 boh/foh bohfoh foh/boh fohboh stage staging terminal/server

Windows 98 File Server/Terminal Setup

Windows 98 File Server/Terminal Setup

============================================================================

AKBID1024

Created: 30 March 2000

Updated: 21 February 2003

Reviewed: 2 March 2004

Microsoft Windows Versions: Windows 98

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Windows 98 File Server and Terminal on the Same Computer Setup

============================================================================

Summary

The ALOHA^� application software requires several specialized settings (as well as several preferred settings) in the Microsoft^� Windows^� 98 operating system (OS) to properly run on the run both Aloha Front-of-House (FOH) and Back-of-House (BOH) together on the same computer.� If you are using the computer as a file server only, refer to document AKBID1022.� If you are using the computer as a terminal only, refer to document AKBID1013.

Refer to document AKBID1116 for more information on the limitations of running both the FOH and BOH together on the same PC.

Information

This document is written for users familiar with Microsoft Windows 98.

Since some computers come with Windows 98 preloaded while others do not, this document is based on editing the settings of Windows 98.� Users who are installing Windows 98 from scratch or upgrading another OS to Windows 98 can still use this document either by employing these instructions after the Windows 98 installation or by making many of these changes during the Windows 98 installation.

Drives and Partitions

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

The most important settings in the Aloha application software involve the network settings.� To access these settings, select Start/Settings/Control Panel/Network or right-click the Network Neighborhood icon on your desktop and select Properties.

The Configuration tab contains a Components area and Primary Network Logon type.� The components area should have Client for Microsoft Networks as the only network client installed.� You may have others, but these should only be added if absolutely needed.� The correct drivers for your network interface card (NIC) should also be listed.�

The Aloha application software can use either TCP/IP or NetBEUI as its network protocol.� Select either one, but both the file server/terminal and the other terminals must use the same protocol.� To assign the protocol for the Aloha application software to use (refer to document AKBID1018), double-click the desired protocol, select the Advanced tab, and select 'Set this protocol to be the default protocol'.� If you select TCP/IP, Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure that terminals always have an address assigned to them.� The Aloha application software will not function without an IP address assigned to the terminal.� You may have multiple protocols installed as long as the proper protocol for the Aloha application software has been marked as such.�

To add file and print sharing for the Aloha application software, click the File and Print Sharing button and select both options.� Print Sharing may be left disabled if you are not using Windows based printer shares for the FOH.�

The Primary Logon Type is typically set to Windows Logon.� This log in enables Windows 98 to skip the prompt for the user name and password if the password is blank.� Setting this as Client for Microsoft Networks prompts for the user name and password regardless if the password is blank.� If Client for Microsoft Networks must be used as the Primary network logon, use the Microsoft Windows 98 TweakUI utility to automatically enter the user name and password.� TweakUI can be downloaded from the Aloha Technologies FTP site as TWEAKUI.ZIP.� Aloha Technologies installs this utility regardless of the Primary Logon Type setting.

Set the terminal's network name under the Identification tab.� Aloha Technologies uses TERM1 (file server/terminal), TERM2, and so on by default.� Different names may be used, but they must follow Aloha application software specifications.� The terminal name must be a common name used on all terminals (the TERMSTR, refer to document AKBID1010) followed by a number designating the terminal's ID number.� Examples include ALOHA1, ALOHA2, TSFOH_1, and TSFOH_2.� In this case, the TERMSTR would be 'ALOHA' or 'TSFOH_'.� Different TERMSTR names can not be used within the same Aloha system.� Spaces can not be used, but underscores can.� Leading zeros can not be used unless they are part of the TERMSTR, but it is not recommended.

Set the Workgroup name the same on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the Workgroup name, but this name can be of your choice as long as it is consistent throughout the Aloha application software.�

The Computer Description is solely to your discretion.

Ensure that 'Share-level access control' is selected under the Access Control tab.� Only experienced Domain administrators should consider using 'User-level access control'.

Aloha Share Name

The Aloha application software requires a network share name of BOOTDRV.� This is the required name.� This share needs to be applied to the root folder or drive in which the Aloha folder resides.� To set the share, right-click the drive or folder and choose Sharing.� Set the Share Name to BOOTDRV, the Access Type to Full, and leave the password fields blank.

If the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.� Some clients prefer to place the Aloha application software in a special folder in order to limit the shared files and, therefore, enhance security.� Sharing the entire drive in which the Aloha application software resides also shares other files that reside on the drive such as Windows.

Display Settings

To access the Display settings, select Start/Settings/Control Panel/Display or right-click the Windows desktop and select Properties.� Select the Settings tab.� Set the Color palette to 256 Colors or higher.� Aloha Technologies typically uses 16-bit color.�

Refer to document AKBID1165 for screen resolution settings.

Do not enable a Windows screen saver.

Time Zone & Daylight Savings

For the file server and all terminals to display the correct time and adjust to Daylight Savings changes properly, the Time and Date settings must be properly configured in Windows.� Select Start/Settings/Control Panel/Date/Time or double-click the time displayed on the task bar.� Ensure the date and time are correct.� Ensure the date and time are correct on the Date & Time tab.� Ensure the correct time zone is chosen on the Time Zone tab.� This time zone needs to be the same on all terminals and the file server.� If the area observes Daylight Savings, then the 'Automatically adjust clock for daylight savings changes' option must be selected on all terminals and the file server.� This can be turned on or off, but it needs to be consistent throughout the Aloha application software.

FIFO Buffers

Windows 98 enables First-In-First-Out (FIFO) buffers for each COM port.� These buffers tend to interfere with printers using Xon/Xoff flow control, so Aloha Technologies disables these buffers on all COM ports on all terminals, regardless of the printer type.� (In the event of a printer or COM port failure, a printer using Xon/Xoff flow control may be temporally connected to the port in the future.)

To access the FIFO buffer settings, select Start/Settings/Control Panel/System or right click My Computer and select Properties.� Select the Device Manager tab, and click the plus sign (+) next to Ports to expand it.� Select each port one at a time, and select Properties/Port Settings/Advanced.� Clear 'Use FIFO buffer'.� Repeat for each COM port.� The LPT port does not have this option.

Scandisk Autoscan & Settings

By default, if Windows is shut down improperly, it runs Scandisk the next time the system is started.� If it finds any problems on the drive, it prompts for answers.� Again, this can cause a delay when a file server/terminal is restarting, which increases the time the Aloha application software may be disrupted.� To alleviate this problem, Aloha Technologies offers a SCANDISK.INI that keeps Windows from prompting for 95% of the questions.� This SCANDISK.INI can be downloaded from the Aloha Technologies� FTP site as SCANDISK.ZIP.� Place this file in the Windows COMMAND folder overwriting the one that currently exists.

Login Name

Refer to document AKBID1006 for more information on user login information.

To clear the current user names and passwords, delete *.PWL from the Windows folder to remove all users.� Select Start/Shutdown.� Select 'Close all programs and log in as a different user' and click Yes.� Windows logs the current user out and prompts for a user name and password.� Enter the desired user and password and log in to Windows.

VNetBIOS

Windows 98 might experience network problems with restaurants using five or more terminals.� To ensure that terminals do not experience these problems, Microsoft issued a new VNETBIOS.VXD that you can download from the Aloha Technologies FTP site as VNETBIOS.ZIP.� Aloha Technologies installs this .VXD file on all terminals, regardless of the system's size.� Refer to document AKBID1011 for more information.

Once you have the new .VXD, place it in the Windows SYSTEM folder overwriting the current version.� Edit the SYSTEM.INI in the Windows folder, and add a new line in the [386Enh] section that states NUMHCBS=x.� Replace x with a number four times the number of terminals in the system, but not less than 80 nor exceeding 200.� The default for this number is 100.� For example, a 25 terminal system would use NUMHCBS=100.� Do not exceed 100 unless you have more than 25 terminals.

To ensure that Windows does not overwrite the updated VNETBIOS.VXD following network configuration changes, place a copy of the updated VNETBIOS.VXD in the same folder as the Windows CAB files.

AUTOEXEC.BAT

Aloha Technologies uses a default AUTOEXEC.BAT (before the Aloha application software is installed) which contains only two lines:

SET PATH=%PATH%

DOSKEY

The first line creates a PATH variable that Windows 98 does not install by default.� If the path statement does not reside in AUTOEXEC.BAT, some software packages create a new path line that does not include the Windows default path.� With this line, the software will most likely append to the line and preserve the Windows path.

The second line installs DosKey.� DosKey is an application used in a command prompt that recalls previous lines typed via the arrow up and down keys.� For users accustomed to a command prompt environment, it is a welcome feature.

Install Aloha Software

Once Windows 98 is set up according to the standards outlined in this document and you can view the network, use the Aloha Application Software Installation CD to install the Aloha application software.

Run SETUPPOS.EXE /ADVANCED from the Aloha POS CD.� The setup program walks you through the rest of the installation.� You must select 'Run Front of House and Back of House on same PC' on the Aloha Configuration window.

Refer to document AKBID1162 for more information on running CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) as Windows services.

Restarting the FOH

Refer to document AKBID1116 for more information regarding restarting the FOH in this type of environment.

Extended Information

For extra security, Windows offers a Policy Editor (POLEDIT.EXE) for Windows 98 that can lock the user out of most Windows 98 features.� Microsoft provides information on this through their Knowledge Base and can be accessed at http://support.microsoft.com.� Too much security can increase the support time required to address a problem, therefore, increasing the down time.

Caveats

There have been instances where Dial-Up Networking was installed on Windows 98 and caused conflicts with networking abilities in the Aloha application software.� The reason is currently unknown.

When a file server is running Windows 95, Windows 98, or Windows Millennium Edition (Me), Aloha Technologies does not choose to run CTLSVR.EXE and EDCSVR.EXE as services.� Running them as services in a Windows 95, Windows 98, or Windows Me environment, although possible and stable, creates problems when Control Server or EDC Server have to be restarted and/or replaced.� It is not as easy a task to stop and start a service in Windows 95, Windows 98, and Windows Me as it is in Windows NT.� Refer to document AKBID1162 for more information on running Control Server and EDC Server as Windows services.

============================================================================

See also:

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1010 Aloha Application Software System Environment Variables

AKBID1011 Windows 9x VNETBIOS.VXD Patch

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1013 Microsoft Windows 98 FOH Terminal Setup

AKBID1018 Network Lana Numbers

AKBID1022 Microsoft Windows 98 File Server Setup

AKBID1028 Winhook

AKBID1116 File Server/Terminal Limitations

AKBID1148 Backup Procedures

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1165 FOH Screen Resolution Settings

AKBID1175 Aloha Terminal Restart Options

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1024 boh/foh bohfoh foh/boh fohboh stage staging terminal/server

ADP Payroll Export File

ADP Payroll Export File

============================================================================

AKBID1025

Created: 5 February 2000

Updated: 9 December 2002

Reviewed: 9 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.4x � 5.3.x

Subject: Aloha Application Software ADP Payroll Export File Functionality

============================================================================

Summary

The ALOHA^� application software can export labor hours to a file that can be imported by the Automatic Data Processing, Inc (ADP) software.� This document explains how to configure the Aloha application software to export information to ADP.

Information

Setup

Log on to the Aloha application software Back-of-House (BOH).� If the site is using Aloha versions 4.4x or lower, open Maintenance, and select Labor/Electronic Payroll Processing.� If the site is running Aloha versions 5.0x or higher, open Aloha Manager and select Maintenance/Store Settings/Labor/Electronic Payroll Settings.� Add the following information:

Use ADP - Select this to enable ADP support.

ADP Company Number - Enter the 3-digit company code supplied by ADP.

ADP Version Number - Enter the version number of your ADP software.

Store Number - Enter the store number (if applicable) supplied by your ADP representative.

Omit Credit Card Tips - Select this to not include credit card tips in the ADP export file.

Omit Control Totals - Select this for early versions of the ADP software that do not support these fields.

Don't output primary rate or Job Code - Select this if you do not want the employee's primary pay rate or Job Code included in the export file.� The Aloha application software considers the primary pay rate and Job Code to be the first ones listed in the employee record.

Output sales as whole dollars � Select this to export tippable sales for employees as whole dollars (without cents).

Add the ADP export codes to each Job Code and Employee in the Aloha application software.

Enable the External Paydata Information option in the ADP software.� See you ADP representative for assistance.

Export

The ADP export file is created in the Aloha application software BOH.� If the site is using Aloha versions 4.4x or lower, open Control, and select Functions/Create ADP Pay File.� If the site is running Aloha versions 5.0x or higher, open Aloha Manager, and select Functions/Export/Create ADP Pay File.� Highlight the day or range of days to export and click OK.� A message informing you to run the ADP validation program will signal the file was successfully created.

The Aloha application software creates the export file Aloha application software PCPERS.� The file is named EXTPAYxx.yyy where x is the Store ID and y is the company ID.� You need to copy the file to the folder that ADP uses to run its PCPERS program.

Automation

You can automate the process of creating the export file and moving it to the correct ADP folder using Winhook (refer to document AKBID1028).� Contact your ADP representative for the correct ADP folder to use.

To create the export file, add the following command line to your Winhook batch file:

%IBERDIR%\BIN\RPT.EXE /DATE %1 /RD

This will create the export file in the PCPERS folder.� To move the file to ADP, add the following line to the Winhook batch file:

COPY %IBERDIR%\PCPERS\EXTPAY*.* C:\ADP\PCPERS

Replace 'C:\ADP\PCPERS' with the correct destination.

Extended Information

The Aloha application software uses an ADP export file format that is referred to by ADP as the 'DOS format'.� If you are using a Windows-based version of ADP, you must configure it to import data using the 'DOS format'.�

The ADP export file is a flat text file containing multiple 80 byte text records.� Records can extend over multiple lines and are identified by an alphabetic character in the first byte of the record.� The end of each logical record (the end of the data) is indicated by a lowercase z.� The record is then blank filled to 80 bytes, a carriage return (CR), and a line feed, making a total of 82 characters per record.� Each record is made up of multiple fields.� A predefined three-digit field identification number precedes most fields.

There are three types of records that make up one ADP extract file; a header record identified by a 'A' as the first byte of the record, a data record identified by a 'B', and a batch total record identified by a 'C'.

A field is made up of a 3-position field ID and data.� The number of positions for the data portion is field ID specific.� There is no field delimiter.� To reach the next field, the current field has to be scanned for the number of data positions based on the field length.� If not noted otherwise, all field data must be right justified and all alphabetic characters in the file must be uppercase, except for the lowercase z at the end of each logical record.

Header Record

1.        There must be one header record per batch.� Note that the Aloha application software currently outputs one batch per file.

2.        The first field ID is 001 followed by the company code.

3.        The second field ID is 002 followed by the batch ID.� If the ADP Store # is not defined, the default value is 01.

4.        The third field ID is 003 followed by the store number.� This field will only output if ADPSSN=TRUE in the ALOHA.INI in Aloha versions 5.2.5.89 and higher.

5.        The ADP version number is placed in position 80 of the record.

Data Record

The following fields make up the ADP export file data record.� Note that not all fields are required on all records.� If there is no data the field will not be output.� The length is the length of the data portion of the field. �

Field ID

Name

Length

Requirements/Notes

003

Employee Number

6

This is always required.� This is the Employee Export ID entered in Employees.� If none is entered, it will default to the Aloha application software employee ID.

004

Pay Code

1

This is always 1.

005

Employee Social Security Number

15

This field will only output if ADPSSN=TRUE in the ALOHA.INI in Aloha versions 5.2.5.89 and higher.

008

ADP Job Code

6

This field will not output if the 'Don't output primary rate or Job Code' option is enabled and the pay record is for the employee's primary Job Code.� Otherwise, the Job Code's Export Code is output.

010

Shift Code

1

This field will not output if this is the employee's primary Job Code.� If the employee is not working in their primary job, the value of this field is 8 or 9 depending on their change in tip status, if any.� The Shift Code table uses their primary and current tip status to determine this value.� A Job Code can be directly tipped, indirectly tipped, or not tipped.� The field will not be output if there is no change in tip status.� The Order Entry, Bartender, and Indirectly Tipped job code fields are used to determine the job code's tip status.�

011

Pay Rate��

8

This field will not output if the 'Don't output primary rate or Job Code' option is enabled and the pay record is for the employee's primary Job Code

012

Regular Hours

8

013

Overtime Hours��

8

020

Declared Tips

7

The first five digits of the field will be '020 T' and followed by a seven digit tip amount.

021

Cash Tips

7

This field may not apply to all customers.� The first five digits of the field will be '021 G' and followed by a seven digit Cash tip amount.

028

Sales

7

If ADP version is 4, then the first six digits of the field are '028192' plus a seven digit sales total.� Otherwise, the first seven digits of the field are '028192 ' (there's a blank space after the 2) plus a seven digit sales amount.� This field does not include sales in non-tippable order modes.

029

Credit Card Tips��

7

If the ADPUSE195 entry in the ALOHA.INI file is FALSE, the credit card tips will be output (if any).� The first seven digits of the field will be '029195 ' followed by a seven-digit tip amount.��

Shift Code

Value

Primary/

Directly Tipped

Primary/

Indirectly Tipped

Current/

Directly Tipped

Current/

Indirectly Tipped

9

T

-

F

F

9

F

F

T

-

9

-

T

F

F

8

T

-

-

T

8

-

T

T

-

8

F

F

-

T

Batch Total Record

The batch total record contains three fields:

Field ID

Name

Length

Requirements/Notes

030

Total Regular Hours

12

The data portion of the field is followed by a blank.

031

Total Overtime Hours

12

The data portion of the field is followed by a blank.

036

Total Declared Tips

12

The data portion of the field is followed by a blank.

Caveats

No information.

============================================================================

See also:

AKBID1028 Winhook

AKBID1038 Report Command Line Parameters

AKBID1047 Microsoft Windows Schedule Service

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1025

style='mso-spacerun:yes'>� 2003

�

Using Windows-based Printers with Aloha

Using Windows-based Printers with Aloha

============================================================================

AKBID1026

Created: 24 March 2000

Updated: 27 June 2003

Reviewed: 30 January 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Using Windows Printers in the Aloha Application Software Front-of-House

============================================================================

Summary

The ALOHA^� application software supports Microsoft^� Windows^� driven printers to print guest checks, kitchen and bar chits, and Front-of-House (FOH) reports.� You can use Windows printer drivers in lieu of native Aloha application software printer drivers, but you should only use then when required since they introduce additional troubleshooting steps (printer shares and Windows print manager) and may not support all of the features that are supported by OPOS or native drivers.

This document only applies to users configuring receipt printers using Windows-based drivers.� If you are using the native Aloha application software printer drivers, refer to document AKBID1002.

Information

Operating System

Using Windows printers places an increased burden on the computer driving the printers because the computer becomes a printer server, and several other computers are connecting to the shared printers and requesting print jobs.� This can overburden the Windows 95, Windows 98, and Windows Millennium Edition (Me) operating systems if you have more than one Windows printer attached to the computer, so you should consider using Windows NT^�, Windows 2000, Windows XP, or Windows Server 2003 on computers driving multiple Windows printers.

Configuration

Configure the printer in Windows on the terminal to which the printer is physically attached using the port settings and pin-outs at the bottom of this document and the Windows printer drivers provided by the printer manufacturer.� Print a test page.� If Windows does not successfully print a test page, then the Aloha application software will not successfully print either.

To configure the printer in Aloha versions 4.4x and lower, open Maintenance, and select System/Printers.

To configure the printer in Aloha versions 5.0x and higher, open Aloha Manager, and select Maintenance/Hardware/Printers.

Set the printer type to a Windows printer.� If you are using Aloha versions 5.230 or higher, you can additionally configure the Windows Printer Type.� If you are using a printer that is compatible with one of the listed printer types (they are the same printer types that the Aloha application software natively supports), then setting this enables all of the format options associated with the native printer drivers such as bold or red printing and also disables unnecessary cutting when printing FOH reports.

If the printer is physically connected to a terminal using Windows 95, Windows 98, or Windows Millennium Edition (Me) select the Printer ID, select the terminal ID, set the printer type to Windows Printer, and set the 'Windows Printer Name' to reflect the printer name in Start/Settings/Printers (for example, EPSON).

If the printer is physically connected to a terminal using Windows NT, Windows 2000, Windows XP, or Windows Server 2003, select the Printer ID, select the terminal ID, set the printer type to Windows Printer, and set the 'Windows Printer Name' to reflect the printer's Universal Naming Convention (UNC) name (for example, \\TERM1\EPSON).

If the printer is not physically connected to an order-entry terminal, such as a dedicated printer server, you must configure the printer in Windows as a local printer on printer server, and then configure the printer in Windows on an order-entry terminal as a network printer (pointing to the printer on the printer server).� When you configure the printer in the Aloha application software, point to the printer defined on the order-entry terminal, not directly to the printer defined on the printer server.

Click Settings on the Printer maintenance screen in the Aloha application software BOH to access the page layout settings.

When selecting the Right, Left, Top, or Bottom margins, consider the built-in 5-millimeter (mm) indent.� For example, specifying a 25-mm left margin creates an actual space of 30-mm before the text starts.

The 'Space Between Columns' margin is exact.� Specifying 8-mm creates an actual space of 8-mm between the columns.

You must select a font in the Aloha application software that is preloaded in the printer, otherwise the printer function very slowly.� Perform the following to determine the printer's pre-loaded fonts:

1.        Set the receipt printer as the default printer in Windows.

2.        Open Windows Wordpad and select the font drop-down list from the toolbar.

3.        Fonts that have a small printer icon next to them are pre-loaded in the printer. �Experiment with different fonts to determine the best one for your needs.

In the case of Epson printers, select the '15 cpi' font for the Aloha application software to use, and set the point size to 10.

Refresh the system.

Refer to the Aloha application software User Manual for more information.

FIFO Buffers

Windows 95, Windows 98, Windows Me, Windows 2000, Windows XP, and Windows Server 2003 offer the option to enable First-In-First-Out (FIFO) buffers on the terminal�s COM ports.� These buffers tend to interfere with printers using Xon/Xoff flow control.� Aloha Technologies disables these buffers on all COM ports on all terminals by default, regardless of the printer type.�� (In the event of a printer or COM port failure, a replacement printer using Xon/Xoff flow control may be temporarily connected to the port in the future.)

To access the FIFO buffer settings, select Start/Settings/Control Panel/System or right-click the My Computer icon on your desktop and select Properties.� Select the Device Manager tab.� Clicking on the plus sign (+) next to Ports to expand it.� Highlight each port one at a time and select Properties/Port Settings/Advanced.�� Clear the Use FIFO buffer.�� Perform this on each COM port.�� The LPT port will not have this option.

Port Settings and Pin-outs

The printer and COM port settings are the user's discretion, but the printer and COM port must use identical settings.

Failure to match the printer and port settings produces unreadable text.� If printer continues to print unreadable text, increase the printer's buffer size.

The following pin-outs apply to serial printers using Windows drivers instead of native Aloha application software printer drivers.� If you are using native Aloha application software printer drivers, refer to document AKBID1002 for the proper pin-outs.

Serial DB9 to Printer DB25

DB9

2

3

4

5

6

8

DB25

2

3

6

7

20

4

Serial DB9 to Printer DB9

DB9

2

3

4

5

6

8

DB9

3

2

6

5

4

7

Serial DB25 to Printer DB9

DB25

2

3

5

6

7

20

DB9

2

3

7

4

5

6

Serial DB25 to Printer DB25

DB25

2

3

5

6

7

20

DB25

3

2

4

20

7

6

RJ45 to RS232 Adapter Pin-outs

Serial DB9 to Printer DB25

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB9

1

2

3

4

5

6

7

8

DB25

Unused

2

3

6

7

20

Unused

4

Serial DB9 to Printer DB9

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB9

1

2

3

4

5

6

7

8

DB9

Unused

3

2

6

5

4

Unused

7

Serial DB25 to Printer DB9

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB25

1

2

3

4

5

6

7

20

DB9

Unused

2

3

Unused

7

4

5

6

Serial DB25 to Printer DB25

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB25

1

2

3

4

5

6

7

20

DB25

Unused

3

2

Unused

4

20

7

6

Extended Information

Assign the printer names and the printer share to reflect the printer's use or location.� For example, instead of 'Epson TM-T88 Partial Cut', rename it to 'TERM1RCPT'.

Caveats

This document only applies to users configuring receipt printers using Windows-based drivers.� If you are using the native Aloha application software printer drivers, refer to document AKBID1002.

If the printer is not physically connected to an order-entry terminal, such as a dedicated printer server, you must configure the printer in Windows as a local printer on printer server, and then configure the printer in Windows on an order-entry terminal as a network printer (pointing to the printer on the printer server).� When you configure the printer in the Aloha application software, point to the printer defined on the order-entry terminal, not directly to the printer defined on the printer server.

If you are using Windows 98 with TWEAKUI.EXE for automatic login, sharing the printer may disable the automatic login.

Failure to match the printer and port settings produces unreadable text.

The following pin-outs apply to serial printers using Windows drivers instead of native Aloha application software printer drivers.� If you are using native Aloha application software printer drivers, refer to document AKBID1002 for the proper pin-outs.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1002 Aloha Receipt and Kitchen Printer Settings

AKBID1156 Using Windows Printers Between Stores in SuperSites

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1026 based db-9 db-25 network pinout pinouts

�

Microsoft Windows NT/Windows 2000 Automatic Backup

Microsoft Windows NT/Windows 2000 Automatic Backup

============================================================================

AKBID1027

Created: 2 February 2000

Updated: 11 October 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: Windows NT, Windows 2000

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: Using Microsoft Windows NT and Windows 2000 to Automatically Backup Data

============================================================================

Summary

You can schedule the native backup software that is provided with Microsoft^� Windows NT^� and Windows^� 2000 to automatically back up the computer's data using the ALOHA^� application software Winhook feature.

Refer to document AKBID1148 for backup procedures.

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

Information

It is important to safeguard a site's data by backing up the data on to separate media.� Proper backups decrease the down time and data loss if the file server's loses its hard drive.�

The ideal backup process for the Aloha application software would require minimal user intervention, and you can perform the following to accomplish this:

1.        Use Winhook to initiate the backup at a convenient time when nobody is at the restaurant.� This enables the backup to start without user intervention.

2.        Use backup hardware that can contain the contents of the entire hard drive on a single tape.� This requires less user intervention since you will not need to swap the tape during the backup.

3.        Use seven different tapes to decrease the chance of an unusable tape.� You need to label each tape needs with a different day of the week, for example 'Monday', 'Tuesday', and so on.� The user only needs to insert the correct tape for the day.� This decreases the wear on the tapes and allows for a successful recovery.� If the most recent tape is found defective during the recovery procedure, there are six other tapes with similar backup data.

There are a few precautionary measures to consider:

1.        Backup tapes wear out.� The site should replace the tapes as directed by the manufacturer to ensure data integrity.� Using a different tape each day of the week will curtail wear, but it will not alleviate it.

2.        NTBackup can interfere with the operation of the Aloha application software.� It is not advisable to use NTBackup during business hours.�

3.        You should store the backup tapes in a secure area to prohibit theft.� You should also keep one tape off premises at all times to protect the data in case of a fire or other natural disaster.

Windows NT

You need to add a command line to the Winhook batch file in order to start NTBackup.� Refer to document AKBID1028 for more information on Winhook.� The syntax for NTBACKUP.EXE is:

NTBACKUP.EXE operation path [/a] [/v] [/r] [/d �text�] [/b] /hc:{on|off}] [/t {option}] [/l �filename�] [/e] [/tape:{n}]

Command

Function

Operation

BACKUP or EJECT.� Instructs NTBackup to perform a backup or eject the tape.

Path

Defines the files to backup.

/a

Appends the backup files to any files already on the tape at the start of the process.� Any files on the tape will be overwritten without this option.

/v

Verifies the files on the tape to ensure data integrity.

/r

Restricts the tape's access to the owner or Administrator.

/d �text�

Labels the backup contents.

/b

Includes the local registry in the backup.

/hc: {on | off}

Specifies hardware compression.� Consult your hardware documentation.

/t {option}

Specifies the type of backup; normal, copy, incremental, differential, or daily.� A normal backup is performed if this option is not specified.

/l �filename�

The name and location of the backup log, if one is desired.

/e

Used with /l; only logs exceptions.

/tape: {n}

Designates the tape number (0-9) to be used.

The following is an example of the command lines used in Winhook to back up a hard drive with three partitions:

rem --------------- Backup ---------------------

rem *** Delete old backup log ***

ECHO Y | DEL C:\BACKUP.TXT

rem *** Fire NTBackup for C: overwriting the tape ***

NTBACKUP BACKUP C: /D �Entire C:� /B /L �C:\BACKUP.TXT�

rem *** Fire NTBackup for D: appending the tape ***

NTBACKUP BACKUP D: /A /D �Entire D:� /L �C:\BACKUP.TXT�

rem *** Fire NTBackup for E: appending the tape ***

NTBACKUP BACKUP E: /A /D �Entire E:� /L �C:\BACKUP.TXT�

rem -------------------------------------------------

Windows 2000

A command line to start NTBackup needs to be added to the Winhook batch file.� Refer to document AKBID1028 for more information on Winhook.� The syntax for NTBACKUP.EXE is:

NTBACKUP.EXE backup [systemstate] "BKS file name" /j {"job name"} [/p {"pool name"}] [/g {"guid name"}] [/t {"tape name"}] [/n {"media name"}] [/f {"file name"}] [/d {"text"}] [/ds {"server name"}] [/is {"server name"}] [/a] [/v:{yes|no}] [/r:{yes|no}] [/l:{f|s|n}] [/m {backup type}] [/rs:{yes|no}] [/hc:{on|off}]

Command

Function

systemstate

Specifies that you want to back up the System State data (includes registry and system files information).� When you back up the System State data, all of the System State data is backed up, therefore, the /S switch does not apply.� Also, the backup type will be forced to NORMAL or COPY.

BKS file name

Specifies the name of the backup selection file (.BKS file) to be used for this backup operation.� A backup selection file contains information on the files and folders you have selected for backup.� You have to create the file using the graphical user interface (GUI) version of Backup.

/j {"job name"}

Specifies the job name to be used in the log file.� The job name usually describes the files and folders you are backing up in the current backup job as well as the date and time you backed up the files.

/p {"pool name"}

Specifies the media pool from which you want to use media.� This is usually the Backup media pool.� If you select this, you must not use the following switches: /A /G /F /T.

/g {"guid name"}

Overwrites or appends to this tape.� Do not use this switch in conjunction with /P.

/t {"tape name"}

Overwrites or appends to this tape.� Do not use this switch in conjunction with /P.

/n {"media name"}

Specifies the new tape name.� You must not use /A with this switch.

/f {"file name"}

Logical disk path and file name.� You must not use the following switches with this switch: /P /G /T.

/d �text�

Labels the backup contents.

/ds {"server name"}

Backs up the directory service file for the specified Microsoft Exchange Server.

/is {"server name"}

Backs up the Information Store file for the specified Microsoft Exchange Server.

/a

Appends the backup files to any files already on the tape at the start of the process.� Any files on the tape will be overwritten without this option.� Either /G or /T must be used in conjunction with this switch.� Do not use this switch in conjunction with /P.

/v:{yes|no}

Verifies the files on the tape to ensure data integrity

/r:{yes|no}

Restricts the tape's access to the owner or Administrator.

/l:{f|s|n}

Specifies the type of log file: f=full, s=summary, n=none (no log file is created).

/m {backup type}

Specifies the type of backup: normal, copy, incremental, differential, or daily.� A normal backup is performed if this option is not specified.

/rs:{yes|no}

Backs up the Removable Storage database.

/hc:{on|off}

Specifies hardware compression.� Consult your hardware documentation.

The following is an example of the command lines used in Winhook to back up a hard drive with three partitions:

rem --------------- Backup ---------------------

rem *** Fire NTBackup for C: overwriting the tape ***

NTBACKUP.EXE BACKUP SYSTEMSTATE /N "Full Backup Tape" /F "C:\� /D "Entire C:" /M NORMAL

rem *** Fire NTBackup for D: appending the tape ***

NTBACKUP.EXE BACKUP SYSTEMSTATE /T "Full Backup Tape" /F "D:\� /D "Entire D:" /A /M NORMAL

rem *** Fire NTBackup for E: appending the tape ***

NTBACKUP.EXE BACKUP SYSTEMSTATE /T "Full Backup Tape" /F "E:\� /D "Entire E:" /A /M NORMAL

rem -------------------------------------------------

Extended Information

NTBackup can be started using the Windows NT Schedule Service or the Windows 2000 Scheduled Tasks instead of using Winhook.� Refer to document AKBID1047 for more information on the Windows NT Schedule Service.

Caveats

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

Backup tapes wear out.� The site should replace tapes as directed by the manufacturer to ensure data integrity.� Using a different tape each day of the week will curtail wear, but it will not alleviate it.

NTBackup can interfere with the operation of the Aloha application software.� It is not advisable to use NTBackup during business hours.�

The back up tapes should be stored in a secure area to prohibit theft.� It is also advisable to keep one tape off the premises at all times to protect the data in case of a fire or natural disaster.

============================================================================

See also:

AKBID1028 Winhook

AKBID1047 Windows NT Schedule Service

AKBID1148 Backup Procedures

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1027

Winhook

Winhook

============================================================================

AKBID1028

Created: 9 February 2000

Updated: 27 June 2003

Reviewed: 30 January 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.301 � 5.3.x

Subject: Using the Aloha Application Software Winhook Feature

============================================================================

Summary

The ALOHA^� application software uses the Winhook feature to perform tasks executed from a batch file after the End of Day (EOD) and Grind processes have completed each night.� You can use the Winhook batch file to backup data, print reports and manipulate files.� Refer to document AKBID1171 for more information on running a batch file on the Front-of-House (FOH) Master terminal following the EOD process.

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

Information

Create your Winhook batch file, and place it in the Aloha application software BIN folder.� The batch file must reside in the BIN folder.� The file name is arbitrary, but POSTEOD.BAT and WINHOOK.BAT are commonly used.

To enable the Winhook feature, define the batch file for Winhook to use in the Back-of-House (BOH).� If you are using versions 4.4x and lower, define the name of your batch file in Maintenance/Options/Miscellaneous 2.� If you are using versions 5.0x and higher, define the name of your batch file in Aloha Manager/Maintenance/Store Settings/System/End of Day.

The Winhook batch file is initiated when CTL.EXE or CTLSVR.EXE (depending on the version of the Aloha application software) detects dated folder with a GNDDBF30.XXX file (created by the Grind Process; refer to document AKBID1016) in it, but not a WINHOOK file in it.� When this occurs, CTL.EXE (Control) or CTLSVR.EXE (Control Server) initiates the Winhook batch file.� Although Control and Control Server do not monitor the success of the commands included in the Winhook batch file, they do wait for the batch file to complete.� Once the batch file's window has closed, it is considered successful regardless of any errors resulting from the batch file's contents and Control or Control Server create a WINHOOK marker file in the dated folder.

There is no way to limit Winhook to starting only on select days, but you can use the DATEDAY.EXE and DAYWEEK.EXE utilities to limit selected commands within the batch file to start on select days.� Refer to document AKBID1012 for more information.

Winhook uses the %1 parameter to declare the Date-of-Business (DOB) in the batch file.� The %1 parameter is standard syntax for referring to command-line variables from within a batch file.� Always use %1 in place of the dated folder's name in the batch file, for Control or Control Server pass the dated folder's label as the first command line parameter.� For example, to delete the .CDX files in a dated folder, use the following command line:

DEL %IBERDIR%\%1\*.CDX

Copying Files to Windows NT, Windows 2000, Windows XP, or Windows Server 2003

If you are using Winhook to copy files between from a file server using Microsoft^� Windows NT^�, Windows^� 2000, Windows XP, or Windows Server 2003 to another remote computer using Windows NT, Windows 2000, or Windows XP or if you are using Winhook to copy files from a file server using Windows 2000, Windows XP, or Windows Server 2003 to another remote computer using Windows 98, then you will possibly have to change the login used by Control Server from the built-in Windows system account to a user account with access to the remote computer's shares.� Refer to document AKBID1197 for more information.

Manually Start the Winhook Process

To manually start the Winhook process for a dated folder, remove the WINHOOK file from the folder or run it from a command line, which uses the batch file name and the dated folder name.� For example:

POSTEOD.BAT 20001009

Winhook Does not Automatically Initialize

If Control or Control Server do not automatically initialize Winhook batch files, it is possible that Control or Control Server is hung up waiting for a previous Winhook batch file to complete.� Although Control and Control Server do not monitor the success of the commands included in the Winhook batch file, they do wait for the batch file to complete.� Control and Control Server do not continue with other tasks (such as grinding dated folders or initializing the Winhook batch file for other dated folders) until the current Winhook batch file completes.� If the batch file pauses or hangs indefinitely, then Control or Control Server will not initialize other tasks.� If you have registered Control Server using a specific user login rather than the built-in Windows system account, then the batch file does not interact with the desktop, and you cannot verify the Winhook batch file's completion or see any errors (including errors while printing reports).� In this case, you can view the current processes in Windows Task Manager and close the CMD.EXE process if it is active (ensure that the CMD.EXE process does not represent another task besides Winhook).

Consider using the Windows START command for time-consuming functions in the Winhook batch file in order to initiate new instances of the command prompt.� This enables the Winhook batch file to complete sooner, and not get hung up waiting for a task to complete.

Extended Information

Using WAIT.EXE When Copying Files to FOH Terminals

You can use the WAIT.EXE utility to create a timed pause in a batch file (refer to document AKBID1012 for more information on WAIT.EXE).� This utility is useful when the Winhook batch file accesses FOH terminals.� After the EOD and Grind processes have completed, the Winhook process is often started by the BOH before the FOH terminals have finished restarting.� Insert a two-minute pause in the batch file to wait for the FOH terminals to complete.

Sample Winhook File

rem --------------- Default Aloha PostEOD.bat ------

rem

rem

rem

rem

rem --------------- Set Up Parameters ---------------

rem *** Define your EDC processor's folder ***

SET EDCFOLD=CES

rem *** Define your archive drive and folder ***

SET ARCHDIR=D:\ALOHAZIP

rem -------------------------------------------------

rem

rem

rem

rem

rem --------------- Disk Cleanup --------------------

rem *** Delete unneeded CDX files in dated subdirs ***

DEL %IBERDIR%\%1\*.CDX

rem -------------------------------------------------

rem

rem

rem

rem

rem --------------- Data Archiving ------------------

rem *** Archive dated subdirs to archive drive ***

PKZIP %ARCHDIR%\%1.ZIP %IBERDIR%\%1\*.*

rem *** archive EDC STL files to archive drive ***

PKZIP %ARCHDIR%\EDCSTL.ZIP %IBERDIR%\EDC\%EDCFOLD%\*.STL

rem *** Archive EDC INI file to archive drive ***

PKZIP %ARCHDIR%\EDCINI.ZIP %IBERDIR%\EDC\EDC.INI

rem -------------------------------------------------

rem

rem

rem

rem

rem --------------- Data Backup ---------------------

rem *** Delete old backup log ***

REM ECHO Y | DEL C:\BACKUP.TXT

rem *** Fire NTBackup for C: overwriting the tape ***

NTBACKUP BACKUP C: /D "ENTIRE C:" /B /L "C:\BACKUP.TXT"

rem *** Fire NTBackup for D: appending the tape ***

NTBACKUP BACKUP D: /A /D "ENTIRE D:" /L "C:\BACKUP.TXT"

rem *** Fire NTBackup for E: appending the tape ***

NTBACKUP BACKUP D: /A /D "ENTIRE E:" /L "C:\BACKUP.TXT"

rem -------------------------------------------------

rem

rem

rem

rem

Caveats

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

============================================================================

See also:

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1015 EOD Process and Errors

AKBID1016 Grind Process and Errors

AKBID1027 Microsoft Windows NT/Windows 2000 Automatic Backup

AKBID1038 Report Command Line Parameters

AKBID1104 Automatic Credit Card Settlement

AKBID1148 Backup Procedures

AKBID1171 FOHHOOK.BAT

AKBID1197 Assigning Logins to Aloha Services

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1028

Credit Card Pre-Authorization

Credit Card Pre-Authorization

============================================================================

AKBID1029

Created: 6 March 2000

Updated: 16 October 2000

Reviewed: 27 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.5x � 5.3.x

Subject: Using Credit Card Pre-Authorization with the Aloha Application Software

============================================================================

Summary

You can use the ALOHA^� application software credit card pre-authorization functionality to save and verify customer the credit card information when a check is opened.� You can then use the pre-authorization to close the check, which enables a restaurant keep the credit card number and validate the available credit without the liability of holding the physical credit card.

Information

Tender Setup

You must enable 'Allow Pre-Auth with EDC' for each credit card tender available for pre-authorization.� Tenders that do not have this enabled will not pre-authorize.

At least one tender must be enabled for pre-authorization to functionality to appear in the Front-of-House (FOH).

In versions 4.4x and lower, open Maintenance, select Payments/Tenders, and open the Auth Req'd window.� Enable the 'Allow Pre Auth With EDC' option.�

In versions 5.0x and higher, open Aloha Manager, select Maintenance/Payments/Tenders, and select the Authorization tab.� Enable the 'Allow Pre Auth With EDC' option.

EDC Settings

You must enable pre-authorization in the Electronic Draft Capture (EDC) settings.

In versions 4.4x and lower, open Maintenance, select MX, and then select EDC.

In versions 5.0x and higher, open Aloha Manager, select Maintenance/Store Settings, and select the Credit Cards group.� Select the Authorization tab.

Define the pre-authorization Amount, Increment, and Warning Point. The amount is the initial pre-authorization dollar amount. The increment is the default dollar amount the pre-authorization will increment when increasing the pre-authorization dollar amount. The warning point is the dollar amount the check's sales must be within (compared to the pre-authorized amount) before a warning is given to increase the pre-authorization.

You can configure eight additional pre-authorization increment amounts in the spaces provided.� In versions 4.4x and lower, these are defined in the 'Preauth Amounts' section.� In versions 5.0x and higher, these are defined in the Amount Selections.� These provide the server with a choice of amounts if the pre-authorization is manually increased.� The default increment amount is used if these additional amounts are not defined.

You can use automatic pre-authorization increments if you enable the 'Auto Pre-Auth' (in versions 4.4x and lower) or the 'Perform Pre-Authorizations Automatically' (in versions 5.0x and higher) option.� Automatic pre-authorization incrementing uses the default increment amount.

Front-of-House Functionality

You can initialize credit card pre-authorization process in two ways:

1.        The server chooses the Pre Auth button from the Tenders screen.

2.        The server swipes a valid credit card (with pre-authorization enabled as described in Tenders Setup) from the Order Entry or Tenders screen.

If the employee's job code is defined as a bartender (as described in document AKBID1053), the tab name will reflect the customer's name defined on the credit card if the tab has not already been named.

If the employee's job code has 'Sees Tabs' enabled, but not does not have bartender enabled, the employee can swipe the credit card on the New Tab Name screen.� This names the tab to reflect the customer's name on the credit card.� The employee must swipe the credit card again from the Order Entry screen to start the pre-authorization process.�

When the pre-authorization Warning Point is reached, the top of the guest check will turn red when you view the check from the Order Entry or Tenders screen.

If you are not using automatic pre-authorization incrementing, you can increase the pre-authorization using the 'Increase Auth' button on the Tenders screen.� If the optional increment amounts are defined, you receive a choice of increment amounts; otherwise the Aloha application software uses the default increment amount.

Use the 'Print Auth' button to present a credit card voucher to the customer.

If the check is paid using the pre-authorized credit card, you must close the check using the 'Close Out Auth' button on the Tenders screen.� Reentering the credit card information or using the Saved Credit feature (refer to document AKBID1045) creates a second authorization, and needlessly ties up the customer's credit.

Disabling FOH Pre-Authorization Buttons

To disable the pre-authorization buttons on the FOH tender screen, disable all pre-authorization settings and set all pre-authorization amount settings to zero in the Back-of-House (BOH).� Also disable 'Allow Pre-Auth with EDC' on all tenders in the BOH.

Extended Information

No information.�

Caveats

If the check is paid using the pre-authorized credit card, you must close the check using the 'Close Out Auth' button on the Tenders screen.� Reentering the credit card information or using the Saved Credit feature (refer to document AKBID1045) creates a second authorization, and needlessly ties up the customer's credit.

============================================================================

See also:

Aloha TableService User Manual

AKBID1020 EDC Process

AKBID1045 Saved Credit Card Information

AKBID1053 TableService Order Entry Job Code Options

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1029

Grind Database Contents

Grind Database Contents

============================================================================

AKBID1030

Created: 26 January 2000

Updated: 2 October 2003

Reviewed: 28 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: Aloha Application Software Grind Database Contents

============================================================================

Summary

The ALOHA^� application software uses the Grind Process (refer to document AKBID1016) to extract data from each Date-of-Business (DOB) binary transaction log and create DBF or relational database (RDB) files.� These files are referred to as 'Grind files' and the Aloha application software (and third party software) uses them to report the DOB's transactions.� This document explains the Grind file contents to help users interface with third party software and create customized reports.

Information

Some files and fields may not be present in all versions of the Aloha application software software.

The following information is specific to the DBF-format Grind Files.� The RDB files use a similar format, but they are tables in the RDB database.

Some fields in the Grind files refer to data found in the Aloha DBF or RDB files.� DBF files are indexed by ID.

Refer to document AKBID1016 for the location of the Grind files.

ADJTIME.DBF and ADJTIMEX.DBF Labor Hours File

Shift data is stored in the ADJTIME.DBF, but ADJTIMEX.DBF exists in the dated folder if a shift from this day was edited, added or deleted.� ADJTIMEX.DBF is copied to ADJTIME.DBF during the next End-of-Day (EOD) process.

�

Field

Description

EMPLOYEE

Employee ID

SHIFT_ID

Employee shift number for the day.� For example, the first time the clock-in for the day is shift one, the second time they clock-in for the same day is shift two, and so on.

INVALID

TRUE if this shift has been discarded

SSN

Social Security Number

DATE

DOB

JOBCODE

Job code ID

INHOUR

Clock-in hour

INMINUTE

Clock-in minute

OUTHOUR

Clock-out hour

OUTMINUTE

Clock-out minute

MINUTES

Total minutes (including overtime)

HOURS

Total hours (including overtime)

RATE

Pay rate

PAY

Total pay for shift (including overtime)

OVERMIN

Overtime minutes

OVERHRS

Overtime hours

OVERRATE

Overtime rate

OVERPAY

Overtime pay

DRIVERFEES

Earned delivery fees

CCTIPS

Credit card tips (less any reductions)

DECTIPS

Declared tips

SALES

Tippable gross sales closed by server

SALESIN

Tippable gross sales closed by server, rung by someone else

SALESOUT

Tippable gross sales rung by server, closed by someone else

NOTIPSALES

Non-tippable gross sales closed by server

MANAGER

Employee ID who created, edited, or deleted this shift

PAIDBRK

Paid break minutes

PAIDBRKHRS

Paid break hours

PAIDBRKPAY

Paid break wages

UNPAIDBRK

Unpaid break minutes

UNPDBRKHRS

Unpaid break hours

UNPBRKPAY

Unpaid break time

TIPPED

TRUE if shift was tipped

SEEN

TRUE if changes have been reported to employee

REGOVMIN

Regular overtime minutes

REGOVHRS

Regular overtime hours

REGOVPAY

Regular overtime pay

DAYOVMIN

Daily overtime minutes

DAYOVHRS

Daily overtime hours

DAYOVPAY

Daily overtime pay

PUNCH_ID

Edited punch unique id

UNIT

Unit ID (from the ALOHA.INI)

OCCASION

Event ID (SuperSite)

STARTMILES

Driver starting miles

ENDMILES

Driver ending miles

DLVRUNS

Delivery runs

DLVORDERS

Delivery orders

DLVSALES

Delivery sales

CCTIPSALES

Tippable credit card sales

VIZOR

Total employee contribution to VizorVest program

REASON

Edit punch reason ID

TOTCCSLS

Total credit card Sales (after shift edit)

TNOCSHSLS

Total non-cash sales (after shift edit)

TNOCSHTIP

Total non-cash tips (after shift edit)

TIPREFUND

Tip Refund (after shift edit)

TIPSHCON

Tip share contribution (after shift edit)

AUTGRTTOT

Total automatic gratuity (after shift edit)

GROSSTXIN

Gross cash in (after shift edit)

GROSSTXOUT

Gross cash out (after shift edit)

GROSSSLS

Gross sales (after shift edit)

NOOFCHECK

Number of checks (after shift edit)

NOOFGUEST

Number of guests (after shift edit)

TOTCOMP

Total comps for employee (after shift edit)

TOTPROMO

Total promo amount for employee (after shift edit)

SPECTNDR

Special tender Amount

MGRNUMBER

Employee ID who created, edited, or deleted this shift

GNDAUDIT.DBF

This file contains audit information and only appears if the LANDRYS flag is enabled.� Refer to document AKBID3038 for more information on the LANDRYS flag.��

Field

Description

AUDITTYPE

Sales type (see the GNDAUDIT.DBF Type Constants table)

DOB

DOB

HOUR

Transaction hour

MINUTE

Transaction minute

EMPLOYEE

Employee ID

CHECK

Check number

ITEM

Item ID that was transferred or deleted

QUANTITY

Quantity of the item

AMOUNT

Item amount

PREVCHECK

Previous check

PREVEMP

Previous employee

ORIGCHECK

Original check

ORIGEMP

Original employee

MANAGER

Manager ID

REASON

Reason

DATA1

Type constant information (see the GNDAUDIT.DBF Type Constants table)

GNDAUDIT.DBF Type Constants

Used with GNDAUDIT.DBF.

Type

Description

1

Transfer Item

2

Print Check

3

Transfer Check

4

Reopen Check

5

Adjust Payment, DATA1 contains the tender ID

6

Delete Promotion from check.� ITEM contains the promotion ID and AMOUNT contains the comped amount.

7

Reprint closed check

8

Delete check out

9

Split check, DATA1 contains the number of checks that were generated

10

Server Checkout

GNDBREAK.DBF Break File

This file contains all breaks that for a business day.

Field

Description

BREAKID

Unique break ID

EMPLOYEE

Employee ID

SHIFT

Employee shift number for the day.� For example, the first time the clock-in for the day is shift one, the second time they clock-in for the same day is shift two, and so on.

SSN

Social Security Number

DATE

DOB

JOBCODE

Job code

INHOUR

Start hour

INMINUTE

Start minute

OUTHOUR

End hour

OUTMINUTE

End minute

MINUTES

Total minutes

HOURS

Total hours

PAID

Paid or unpaid break

INVALID

TRUE if this shift has been discarded

PERIOD ID

Period ID

MGR

Employee ID who created, edited or deleted this break

UNIT

Unit ID (from the ALOHA.INI)

OCCASION

Event ID (SuperSite)

REASON

Edit punch (break) reason ID

MGRNUMBER

Edit punch manager ID

GCHKINFO.DBF Check Information

Additional guest check information (refer to document AKBID1207)

Field

Description

UNIT

Store ID

DOB

DOB

EMPLOYEE

Employee ID

QUEUEID

Queue ID

TABLEID

Unique table ID

CHECKID

Unique check ID in versions 5.2.7.82 and lower; check number in versions 5.2.7.83 and higher.

ATTNAME

Prompt text

ATTTEXT

Text entered by user

FKTABLEID

Table number ('0' if it a tab name is used)

TABNAME

Tab name (if this was a table number, uses 'Table nn', where nn is the table number)

GNDDEPST.DBF

This file contains the daily deposit information previously contained in DEPOSIT.TXT.

Field

Description

DATE

Deposit date

AMOUNT

Deposit amount

DESCRIPTION

Deposit description (supplied by user at the time of the deposit entry)

ID

Unique deposit ID

EMPID

Employee ID

TIME

Time and date when deposit was recorded

STOREID

Store ID (SuperSite)

REGIONID

Region ID (SuperSite)

OCCAISNID

Occasion ID (SuperSite)

GNDDRWR.DBF or GNDOPD.DBF Open Cash Drawer

Open cash drawer instances.

Field

Description

DOB

DOB

EMPLOYEE

Employee ID

DRAWER

Drawer ID

STATE

Drawer state (1 for open, 2 for close)

ACCTIME

Drawer accessed time

HOUR

Hour in which the drawer was opened

MINUTE

Minute in which the drawer was opened

SECOND

Second in which the drawer was opened

GNDEDC.DBF

This file contains EDC transaction information and only appears if the LANDRYS flag is enabled.� Refer to document AKBID3038 for more information on the LANDRYS flag.

Field

Description

EDCTYPE

1 for Authorization, 2 for Adjustment, 3 for Void

DOB

DOB

HOUR

Transaction hour

MINUTE

Transaction minute

EMPLOYEE

Employee ID

MANAGER

Manager ID (if available)

CHECK

Check number

FOHTRANS

FOH-originated transaction

AMOUNT

Transaction amount

TIP

Tip amount

MANUAL

Manual ID input (versus MSR input)

FORCED

Forced transaction

GNDITEM.DBF Item Grind File

This file contains one record for every item sold.

Field

Description

TYPE

The type of record ('0' for a normal sale, '1' for a refund)

EMPLOYEE

Employee ID who sold the item, but not necessarily the employee who closed the check.

CHECK

Check number

ITEM

Item ID

PARENT

Item ID number of the parent item if this item acted as a modifier

CATEGORY

Sales category ID

MODE

Order mode ID

PERIOD

Period ID

HOUR

Transaction hour

MINUTE

Transaction minute

TAXID

Tax ID

REVID

Revenue center ID assigned to the check

TERMID

Terminal ID

MENU

Menu ID

ORIGIN

Submenu ID or modifier menu ID

PRICE

Price

MODCODE

Modifier type if the item was a modifier (see MODCODE Types table)

DOB

DOB

UNIT��

Unit ID (from the ALOHA.INI)

SEAT

If pivot seating is used, the seat number the item was ordered from

ENTRY ID

A unique entry ID generated by the Front-of-House (FOH)

OCCASION

Event ID (SuperSite)

QUANTITY

Item quantity (usually one except when using quantity pricing)

TAXID2

Secondary tax ID

DISCPRICE

Reduced price at which item was sold

REVID2

Revenue center from which item was ordered

CONCEPT

Concept from which item was ordered, if any

INCLTAX

Inclusive tax

MODCODE Types

Used with GNDITEM.DBF.

Type

Description

0

Modifier code not used

1

WITH modifier code (currently unused)

2

NO modifier code

3

EXTRA modifier code

4

SIDE modifier code

5

MESSAGE modifier code (currently unused)

6

SUBSTITUTE modifier code (currently unused)

7

FOR modifier code (currently unused)

8

DELETED modifier code (currently unused)

9

SUBSTITUTE EXTRA modifier code (currently unused)

10

SUBSTITUTE SIDE modifier code

11

INACTIVE modifier code (currently unused)

12

PRINTED DELETED modifier code (currently unused)

13

CANCELED modifier code (currently unused)

14

LIGHT modifier code

15

HEAVY modifier code

16

ONLY modifier code

17

HALF modifier code

18

QUARTER modifier code

19

ADD modifier code

GNDLBSUM.DBF

This file contains a daily labor summary.

Field

Description

DOB

DOB

STOREID

Store ID (SuperSite)

REGIONID

Region ID (SuperSite)

OCCAISNID

Occasion ID (SuperSite)

JOBID

Job code ID

STARTHOUR

Hour that this period starts

STARTMIN

Minute that this period starts

STOPHOUR

Hour that this period ends

STOPMIN

Minute that this period ends

MINUTES

Total minutes for the period

COST

Labor cost

GNDLINE.DBF Line Item Detail Grind File

This file contains line item detail records for applied Comps and Promos.

Field

Description

ID

Promo or comp ID

ITEMID

Item ID

PRICE

Price (when check was closed)

OPRICE

Price (when item was ordered)

AMT

Amount of discount

TYPE

Type of discount (see GNDLINE type constants)

CATID

Sales category ID

TYPEID

Promo or comp ID

CHECKID

Check ID

UNIT

Unit ID (from the ALOHA.INI)

DOB

DOB

ENTRYID

A unique entry ID generated by the FOH

OCCASION

Event ID (SuperSite)

CONCEPTID

Concept ID

GNDLINE.DBF Type Constants

Used with GNDLINE.DBF.

Type

Description

1

Payment (This type is currently unused)

2

Promo

3

Comp

4

Comp category (This type is currently unused)

5

Promo category (This type is currently unused)

6

Gift certificate promo

7

Gift certificate comp

8

Comp category (This type is currently unused)

9

Promo category (This type is currently unused)

10

Deferred tip (This type is currently unused)

GNDOWAGE.DBF Other Wages File

This file contains Other Wages paid for a business day.

Field

Description

ID

Unique ID

DOB

DOB

OWNERID

Owning store ID

USERNUMBER

User-assigned ID

EMPID

Employee ID

STOREID

Store ID (SuperSite)

HOURS

Paid hours

MINUTES

Paid minutes

AMOUNT

Amount

WAGETYPEID

Wage type ID

JOBCODEID

Job code ID

STOREACC

Store access flags

PARENTACC

Parent store access flags

CREATETM

Time record was created

CREATEDT

Date record was created

MODIFYTM

Time record was modified

MODIFYDT

Date record was modified

MANAGER

Employee ID modifying the record

MODTYPE

Type of modification

REVIEWED

Denotes if record was reviewed

GNDPERF.DBF Performance Measure

This file records Performance Measure information.

Field

Description

EMPLOYEE

Employee ID who sold the item, but not necessarily the employee who closed the check.

JOBCODE

Job code ID

SHIFT

Employee shift number for the day.� For example, the first time the clock-in for the day is shift one, the second time they clock-in for the same day is shift two, and so on.

COUNT

Count

AMOUNT

Amount

PERFTEXT

Calculated Performance Measure output

DATE

DOB

PERFID

Performance Measure ID

UNIT

Unit ID (from the ALOHA.INI)

CKOUTNUM

Checkout number

OCCASION

Occasion ID (SuperSite)

REVENUEID

Revenue center ID

GNDQKCNT.DBF Quick Count Accumulated Totals

QuickService only, this file record Quick Count totals.

Field

Description

ID

Composite or tracking item ID

TYPE

Item type (see GNDQKCNT.DBF type constants)

ITEM_ID

Item ID (TYPE 6 only)

DESC

Description

OPENCOUNT

Opening count (at time of Grind process)

ADDCOUNT

Opening count (at time of Grind process)

USAGECOUNT

Usage count (at time of Grind process)

WASTECOUNT

Waste count (at time of Grind process)

VOIDCOUNT

Void count (at time of Grind process)

SOLDCOUNT

Sold count (at time of Grind process)

CLOSECOUNT

Closing count (at time of Grind process)

UNIT

Unit ID (from the ALOHA.INI)

DOB

DOB

OCCASION

Event ID (SuperSite)

GNDQKCNT.DBF Type Constants

Used with GNDQKCNT.DBF.

Type

Description

6

Tracking Item

7

Composite Item

GNDREVN.DBF Revenue Center Grind File

This file contains miscellaneous information formatted to expedite Revenue Center reporting.

Field

Description

EMPLOYEE

Employee ID who closed the check, but not necessarily the employee who sold the item.

CHECK

Check ID

PERIOD

Period ID

REVID

Revenue center ID

TYPE

Type of information (see GNDREVN.DBF type constants)

TYPEID

ID associated with TYPE, if any

AMOUNT

Amount

OPENHOUR

Hour check was opened

OPENMIN

Minute check was opened

ORDERHOUR

Hour first item was ordered on the check

ORDERMIN

Minute first item was ordered on the check

CLOSEHOUR

Hour check was closed

CLOSEMIN

Minute check was closed

UNIT

Unit ID (from the ALOHA.INI)

DOB

Date of business

OCCASION

Event ID (SuperSite)

REVID2

Currently unused

GNDREVN.DBF Type Constants

Used with GNDREVN.DBF.

Type

Description

1

Sales

2

Exclusive taxes

3

Inclusive and vendor taxables

4

Guests

5

Checks

Used with GNDREVN.DBF, the following type constants are created if the REVENUEDETAIL in the ALOHA.INI is set to TRUE.� Note that the addition of these records will take significantly more disk space.

Type

Description

20

Total exclusive tax on a tax exempt check, by tax ID

21

Total payments, by tender ID

22

Total comps, by comp ID

23

Total promos, by promo ID

25

Total voided sales, by server

28

Surcharges collected from guest

29

Order mode charges

30

Total comps, by sales category ID

31

Total promos, by sales category ID

GNDSALE.DBF Sales Grind File

This file contains sales information.

Field

Description

EMPLOYEE

Employee ID who closed the check, but not necessarily the employee who sold the items.�

CHECK

Check number

PERIOD

Period ID

TYPE

Sales type (see the GNDSALE.DBF Type Constants table)

TYPEID

ID associated with TYPE, if any

AMOUNT

Amount

OPENHOUR

Hour the check was opened

OPENMIN

Minute the check was opened

ORDERHOUR

Hour when the first item on this check was ordered

ORDERMIN

Minute when the first item on this check was ordered

CLOSEHOUR

Hour the check was closed

CLOSEMIN

Minute the check was closed

SHIFT

Employee shift number for the day (0 if not applicable).� For example, the first time the clock-in for the day is shift one, the second time they clock-in for the same day is shift two, and so on.

COUNT

Depends on record TYPE (see the GNDSALE.DBF Type Constants table).� For TYPE 25, 51 and 54, the COUNT field is also the Tax ID.

REVENUE

Revenue Center ID

TIPEMP

The tippable employee (employee who opened the check)

UNIT

Unit ID (from the ALOHA.INI)

DOB

DOB

TYPEID2

Item category for a sold BackOffice gift certificate if the TYPE is 23 (See the GNDSALE.DBF type constants table).� The Tax ID for TYPE 25, 51 and 54.

OCCASION

Event ID (SuperSite)

REVID2

Unused

GNDSALE.DBF Type Constants

Used with GNDSALE.DBF.

Type

Description

1

Total (including inclusive taxes) of all items sold by sales category.� Does not include exclusive taxes or voids.

2

Exclusive taxes, by Tax ID

3

Tax-exempt exclusive taxes, by Tax ID

4

Payments, by tender ID.� In QS, TYPEID2 is checkout number.

5

Comps, by comp ID

6

Promotions, by promotion ID

7

Comp tax not collected, by tax ID

8

Promotion tax not collected, by tax ID

9

Taxable sales for inclusive and vendor taxes, by tax ID

10

Total guests

11

Total checks

12

Amount of tip share paid

13

Total voided sales, by employee ID

14

Tip reduction, by employee ID

15

Petty cash, by manager employee ID and account ID.� TYPEID2 is a running count of the number of cash in/out records that is used to identify each record.� In QS, CLOSEHOUR is the checkout number within the shift.

16

Non-collected surcharges

17

Collected surcharges

18

Order mode charges

19

Comps, by sales category ID

20

Promotions, by sales category ID

21

Server performance measure, by performance measure ID

22

Declared cash from checkout.� In QS, TYPEID2 is the checkout number.� ORDERHOUR is the checkout hour, ORDERMINUTE is the checkout minute and CLOSEHOUR is the terminal ID where the employee checked-out.

23

Gift certificates sold, by gift certificate ID

24

Tax, by sales category ID.� COUNT is the tax ID.

25

Taxable sales for inclusive taxes, by sales category ID.

The inclusive tax formula is TAX= (AMOUNT * RATE) / (1 + RATE) .� COUNT is the tax ID.

26

Non-redeemed payments (over-payment without return change).� In QS, TYPEID2 is the checkout number.

31

Net sales, by order mode ID

32

Total calculated inclusive taxes

33

Calculated inclusive taxes, by check number

34

Auto gratuity, by check number

35

Refunds, by tender ID

36

Total tax refunded

37

Taxable refunds (currently unused)

38

Tax exempt refunds (currently unused)

39

Tax refunds, by sales category ID (currently unused)

40

Taxable refunds, by sales category ID (currently unused)

41

Tax-exempt taxable sales

42

Over/short, by employee ID (if available).� In QS, TYPEID2 is the checkout number.

43

Number of checks, by order mode ID

44

Perpetual check counter information.� TYPEID2 is the terminal ID.

45

Rounding adjustment total

46

Order attributes

47

Number of 'no sale' transactions (QuickService only)

48

Foreign currency payments, by tender ID.� In QS, TYPEID2 is the checkout number.

49

Guests, by order mode ID

50

Credit card refunds (currently unused)

51

Exclusive-tax taxable sales, by sales category ID

52

Straight sales � inclusive tax � comps (if NETHASCOMPS=TRUE) � promotions (if NETHASCOMPS=TRUE), by sales category ID.

53

Straight sales + Exclusive tax, by sales category

54

Inclusive tax, by sales category ID

55

Cash cards sold

56

Voided gift certificates, by gift certificate ID

57

Declared tenders from Payment Reconciliation.� In QS, TYPEID2 is the checkout number.� ORDERHOUR is the checkout hour, ORDERMINUTE is the checkout minute and CLOSEHOUR is the terminal ID where the employee checked-out.� TYPEID is the tender ID.

58

Uncollected surcharges, by sales category ID

59

Collected surcharges, by sales category ID

60

Order mode charges, by sales category ID and revenue center

61

Revenue item sales

62

Additional charges (Aloha Manager\Maintenance\Store Settings\Financials\Add Charges)

63

Goods and services tax (GST)

64

$0.00 check count (only populated if Aloha Manager/Maintenance/Store Settings/Financials/Reports/'Exclude Comped Checks and Guests' is enabled)

65

Total comps applied to gift certificates, by comp ID

66

Total promos applied to gift certificates, by promo ID

67

Total comps applied to gift certificates, by sales category ID

68

Total promos applied to gift certificates, by sales category ID

69

Unused

70

Unused

71

Voids by category ID

72

Voided revenue items

73

VizorVest^SM contributions by employee ID

74

Portion of the VizorVest contributions that adds to Cash Owed

75

Cleared (unordered) items by amount

76

Cleared (unordered) items by category ID

77

Cleared revenue items

78

Charge tip added to the check.� This type only appears if the LANDRYS flag is enabled.� Refer to document AKBID3038 for more information on the LANDRYS flag.

79

Number of tokens dispensed.� Used with the Chuck E. Cheese's T.O.D.D. System Controller (token dispenser).

GNDSLSUM.DBF

This file contains a daily sales summary.

Field

Description

DOB

DOB

STOREID

Store ID (SuperSite)

REGIONID

Region ID (SuperSite)

OCCAISNID

Occasion ID (SuperSite)

KEYVOLUME

1 is Sales, 2 is Customers, 3 is Items, 4 is Checks

REVID

Revenue center ID

CATID

Sales category ID

STARTHOUR

Hour that this period starts

STARTMIN

Minute that this period starts

STOPHOUR

Hour that this period ends

STOPMIN

Minute that this period ends

AMOUNT

Total for the period

GNDTIME.DBF

This file contains daily labor information.

Field

Description

EMPLOYEE

Employee ID

SSN

Social Security Number

DATE

DOB

JOBCODE

Job code ID

INHOUR

Clock-in hour

INMINUTE

Clock-in minute

OUTHOUR

Clock-out hour

OUTMINUTE

Clock-out minute

MINUTES

Total minutes

RATE

Pay rate

PAY

Total pay

OVERMIN

Overtime minutes

OVERRATE

Overtime rate

OVERPAY

Overtime pay

CCTIPS

Credit card tips

DECTIPS

Declared tips

SALES

Tippable gross sales closed by server

SALESIN

Tippable gross sales closed by server, rung by and tippable to someone else

SALESOUT

Tippable gross sales rung by and tippable to server, closed by someone else

NOTIPSALES

Non-tippable gross sales closed by server

PERIOD

Period ID

UNIT

Unit ID (from the ALOHA.INI)

GNDTNDR.DBF Tender Grind File

This file contains a record for all applied payments.

Field

Description

EMPLOYEE

Employee ID who closed the check, but not necessarily the employee who sold the item.

CHECK

Check ID

DATE

DOB

TYPE

Type of payment (see GNDTNDR type constants)

TYPEID

Tender ID

IDENT

Identifier, if tender or promotion (see GNDTNDR type constants)

AUTH

Authorization, if tender (see GNDTNDR type constants)

EXP

Expiration, if tender (see GNDTNDR type constants)

NAME

Guest name, if available

UNIT

Comp unit, if comp (see GNDTNDR type constants)

AMOUNT

Amount

TIP

Tip

NR

Non-redeemed payment (overpayment without change provided)

TRACK

YES or NO

HOUSEID

House account ID, if house account (see GNDTNDR type constants)

TIPPABLE

Tippable employee ID

MANAGER

Employee ID who authorized the transaction

HOUR

Transaction hour

MINUTE

Transaction minute

ID

A unique entry ID generated by the FOH

AUTOGRAT

Amount of automatic gratuity

STRUNIT

Unit ID (from the ALOHA.INI)

REVENUE

Revenue center ID

OCCASION

Event ID (SuperSite)

GNDTNDR.DBF Type Constants

Used with GNDTNDR.DBF.

Type

Description

1

Tender

2

Promotion

3

Comp

10

Deferred tip if job code does not deduct tips

GNDTURN.DBF Table Turnover Grind File

This file contains detailed information for each opened and closed table, enabling reports to track the lifetime of the table.� By analyzing these times, a manager can determine where guests are spending their time and focus on improving service in those areas.� By speeding up table turnover, the restaurant can serve more guests and generate more revenue.

Field

Description

EMPLOYEE

Employee ID who closed the check, but not necessarily the employee who sold the item.

DRIVER

Employee ID (who delivered the order)

JOBCODE

Job code ID

TABLE

Table number

TABLEID

A unique table ID generated by the FOH

NAME

Table name (table number or Tab name)

PERIOD

Sales period

REVID

Revenue center

MINUTES

Total minutes the table was open

SALES

Total sales closed on the table

CHECKS

Number of checks closed on the table

GUESTS

Number of guests at the table

WAITHOUR

Hour when party began waiting for table (if using a seating system)

WAITMIN

Minute when party began waiting for table (if using a seating system)

WAITSEC

Second when party began waiting for table (if using a seating system)

SEATHOUR

Hour when party was seated (if using a seating system)

SEATMIN

Minute when party was seated (if using a seating system)

SEATSEC

Second when party was seated (if using a seating system)

OPENHOUR

Hour when table was opened in the POS

OPENMIN

Minute when table was opened in the POS

OPENSEC

Second when table was opened in the POS

CLOSEHOUR

Hour when table was closed in the POS

CLOSEMIN

Minute when table was closed in the POS

CLOSESEC

Second when table was closed in the POS

FIRSTORDHR

Hour when first item ordered for the table

FIRSTORDMN

Minute when first item ordered for the table

FIRSTORDSC

Second when first item ordered for the table

LASTORDHR

Hour when last item ordered for the table

LASTORDMN

Minute when last item ordered for the table

LASTORDSC

Second when last item ordered for the table

FIRSTPAYHR

Hour when first payment applied for the table

FIRSTPAYMN

Minute when first payment applied for the table

FIRSTPAYSC

Second when first payment applied for the table

LASTPAYHR

Hour when last payment applied for the table

LASTPAYMN

Minute when last payment applied for the table

LASTPAYSC

Second when last payment applied for the table

BUSHOUR

Hour when table was bused (if using a seating system)

BUSMIN

Minute when table was bused (if using a seating system)

BUSSEC

Second when table was bused (if using a seating system)

FIRSTBMPHR

Hour when first order bumped

FIRSTBMPMN

Minute when first order bumped

FIRSTBMPSC

Second when first order bumped

LASTBMPHR

Hour when last order bumped

LASTBMPMN

Minute when last order bumped

LASTBMPSC

Second when last order bumped

READYHOUR

Time for order to be bumped (hour)

READYMIN

Time for order to be bumped (minute)

READYSEC

Time for order to be bumped (second)

ASSIGNHOUR

Time order was assigned (hour)

ASSIGNMIN

Time order was assigned (minute)

ASSIGNSEC

Time order was assigned (second)

DRVOUTHOUR

Driver out time (hour)

DRVOUTMIN

Driver out time (minute)

DRVOUTSEC

Driver out time (second)

DRVINHOUR

Driver in time (hour)

DRVINMIN

Driver in time (minute)

DRVINSEC

Driver in time (second)

UNIT

Unit ID

DOB

Date of business

PROMISED

Number of minutes an order was promised

CATEGORYID

Sales category ID for first item ordered on this check

MODEID

Order mode ID for first item ordered on this check

FSTVIDID

Video ID for the first item on this check sent to a video

LSTVIDID

Video ID for the last item on this check sent to a video

STOREID

Store ID (SuperSite)

GNDVOID.DBF Void Grind File

This file contains a record for every item voided.

Field

Description

EMPLOYEE

Employee ID (who owned the check)

MANAGER

Employee ID (who performed the void)

CHECK

Check ID

TABLENAME

Table name (table number or tab name)

ITEM

Item ID

PRICE

Price

DATE

DOB

HOUR

Transaction hour

MINUTE

Transaction minute

REASON

Void reason ID

INVENTORY

Did this void affect inventory?

UNIT

Unit ID (from the ALOHA.INI)

ENTRYID

A unique entry ID generated by the FOH

OCCASION

Event ID (SuperSite)

REVID

Revenue center ID

WAGEEDIT.DBF

No information is available at the time of this writing.

Field

Description

ID

Unique ID

DOB

DOB

OWNERID

Owning store ID

USERNUMBER

User-assigned ID

EMPID

Employee ID receiving other wages

STOREID

Store ID (SuperSite)

HOURS

Number of hours paid

MINUTES

Number of minutes paid

AMOUNT

Amount paid

WAGETYPEID

Wage type ID

JOBCODEID

Job code ID for wage

CREATETM

Time record was created

CREATEDT

Date record was created

MODIFYTM

Time record was modified

MODIFYDT

Date record was modified

MANAGER

Employee ID modifying the record

MODTYPE

Type of modification

STOREACC

Store access flags

PARENTACC

Parent store access flags

REVEWED

Denotes whether this record was reviewed

Extended Information

Aloha Enterprise.com Egrind Files

Aloha Enterprise.com creates the following grind files during the Egrind process, but these files are not covered in this document: GLDP.DBF, GLRCDP.DBF, GLRC.DBF, GLLC.DBF.� These file contain labor information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

Quick Count User Manual

AKBID1016 Grind Process and Errors

AKBID1042 Aloha Application Software Database Files

AKBID1081 Summary Process and Files

AKBID1085 Basic Gift Certificates

AKBID1108 Using the Crystal Report Interface with .DBF Files

AKBID1129 Using the Crystal Report Interface with an RDB

AKBID1207 Configuring and Using CHKINFO.EXE

AKBID3038 LANDRYS Flag

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1030 export.doc export50 export50.doc export52 export52.doc

Floating Logo

Floating Logo

============================================================================

AKBID1031

Created: 7 February 2000

Updated: 4 September 2003

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: The Aloha Application Software Floating Logo Creation and Options

============================================================================

Summary

You can customize the ALOHA^� application software Front-of-House (FOH) floating logo to each client's needs.� For example, you can use a single logo, or you can configure multiple logos that alternate with each sweep of the screen. This document explains how to configure the floating logo in the Aloha application software.

Information

The floating logo is a Windows bitmap (.BMP) file created from a restaurant's logo, and it resides in the BMP folder.� The logo floats across the screen of the FOH terminals when they are not in use, and they also appear as the background of some Aloha application software Back-of-House (BOH) products.� The logo's movement appears to be bouncing since it increases its speed when moving down and decreases its speed when moving up.

Logo Creation

To create the logo, scan it from a document (letterhead, envelope, coaster or otherwise) or use an existing copy already in an electronic format.� Convert the file to a .BMP format.� Label the file using the information in the Logo Usage section of this document.

The logo's size is relative to the client's preferences, but it typically ranges from two to three inches in width and height.� You can use a larger size, but it may not 'float' in the way in which it was designed.� The colors should not exceed the FOH terminal's available color palette.

Each logo should have a 1/3^rd inch solid black border around each side in order to prevent streaks from appearing as the logo floats across the screen.

Logo Usage

You can use the logo's file name in order to configure the logo's usage.

You can label your logo LOGO.BMP.� This creates a single logo that bounces across the FOH screen, and it is also used as the background of some BOH applications.� This is the preferred method if you are only using a single floating logo.

If you want to use multiple floating logos, you can create several logos labeled sequentially as LOGO1.BMP, LOGO2.BMP, and so on.� The FOH logo alternates between the different numbered logos each time it reaches the screen edge.� Any BOH applications that use the logo as a background will use a built-in default Aloha application software logo (the BOH applications ignore the numbered logos).� You cannot use a LOGO.BMP file with configuration; otherwise the FOH ignores the numbered logos.

If you do not create a logo bitmap, then the FOH will use a built-in default Aloha application software logo.

STOPLOGO System Environment Variable

If you are using Aloha application software versions 5.211 or higher, you can enable the STOPLOGO system environment variable (SET STOPLOGO=TRUE) to disable the logo's floating motion.� If this is enabled, the logo is centered on the screen and does not move.� This benefits wireless and thin-client users who do not have the bandwidth or system resources to support the logo's floating motion.

Extended Information

Some clients prefer the streaks or 'tracers' created by a logo without a black border around its edges.� If you do not add the solid black border around the logo, the logo might leave streaks as if floats across the screen.� Some clients prefer this look.

Caveats

If a site switches to multiple numbered logos after initially using a LOGO.BMP, you must manually delete the LOGO.BMP file from the BMP folder on the file server and each terminal.� Only deleting the file from the file server does not also remove the file from the terminals when the files are synchronized.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1031 bounce bouncing

�

IBM 4695 POS Terminal

IBM 4695 POS Terminal

============================================================================

AKBID1032

Created: 4 January 2000

Updated: 25 April 2003

Reviewed: 19 February 2004

Microsoft^� Windows^� Versions: Windows 95, Windows NT^�

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

Subject: IBM 4695 Setup for the Aloha Application Software

============================================================================

Summary

The IBM^� 4695 POS terminal requires specific settings for use with the ALOHA^� application software.� The settings include the touch screen, network interface card (NIC), integrated magnetic stripe reader (MSR), cash drawers, and customer (or rear) display.� The Aloha application software to interfaces with the IBM Point of Sale Subsystem (POSS) drivers to communicate with the peripherals.

If you use IBM OPOS drivers instead of the IBM POSS drivers to interface the IBM 4695 peripherals to the Aloha application software, do not use this document.� Instead, set the terminal up as a clone and use OPOS as the device type for the peripherals.� Refer to document AKBID1074 for more information.

Information

The basic operating system (OS) setup mimics Aloha's standard setup recommendations regardless of the OS type.� You should review the proper OS setup document before proceeding any further with this document.

This document is written under the assumption that you have followed Aloha's suggested OS setup as described in the OS setup document.

You can download IBM hardware drivers from IBM's POS Support page located at http://www2.clearlake.ibm.com/store/support/index.html.� IBM's 4695 terminals come in both 4694-2xx and 4695-3xx versions.� Ensure you download the correct drivers for your terminal version. �The POSS drivers apply to both versions.

IBM POSS Drivers

Aloha interfaces with the IBM POSS drivers to initialize the touch screen, cash drawer ports, integrated MSR, and customer display.

A copy of version 1.4.0 (with a separate bug fix) resides in the \Misc\IBM4695\POSSW140 folder on the Aloha Installation CD for versions 4.2x and lower.� A copy of version 1.4.3 resides in the \Misc\IBM4695\POSSW143 folder on the Aloha Installation CD for versions 4.4x and higher.� Aloha Technologies recommends using version 1.4.3.

Windows 95 and Windows 98 use a path variable that includes the Windows folder and the Windows Command folder.� The PATH variable is true even if there is either no system path already defined in the system's variables.� If you install the IBM POSS drivers on a system without a previous path variable defined, they can create a new PATH variable that will not account for the default path mentioned above.� Thus, Windows may not have access to the files it needs and will not start.� To alleviate this problem, ensure the variable SET PATH=%PATH% resides in the Autoexec.bat before installing the POSS driver software.

If you are using the POSS drivers on the Aloha Installation CD, run the IBM POSS Setup.exe to install the software.� Select the default options when prompted by the setup application.�

If you are using version POSS 1.4.0 (rather than 1.4.3), ensure that you copy the bug fix files from the Aloha Installation CD to the \POS\Bin folder on the terminal's hard drive after you have installed the POSS drivers.� Replace the existing versions and restart the system.

Environment Variables

If you are using the 4695's integrated MSR, add the IBM4695MSR=TRUE system environment variable to the terminal.

If you are not attaching IBM's integrated MSR to the terminal, do not set the MSR variable described above.

Regardless of peripheral use, create a file labeled IBMRes in Aloha application software Bin folder on the terminal using a command line similar to the following to create this file:

Echo 1 > %LOCALDIR%\Bin\IBMRes

IBM touch screens do not lose calibration, and therefore, you cannot calibrate them.� You do not need to use the Aloha application software CALIBRATE variable with 4695 terminals.

Adjust the 4695 touch screen's contrast using the CONTRAST system environment variable.� The default value is 30, but you can increase or decrease the value (usually between 28 and 32) for more or less contrast.� If you are using a monochrome screen, initially set this value to 20 and then adjust it from there.� This variable does not take effect until the FOH is started.

IBM's touch screen drivers may take up to 15 seconds (or longer) to properly initialize after Windows starts.� In most circumstances, they are typically initialized by the time the Aloha application software is loaded.

NIC Settings

If you are using a 4695-3xx terminal that uses the AMD PCNET Ethernet Adapter, change the following resource settings in the NIC's properties:

-          Set Bus Type to PCI

-          Set Full Duplex to OFF

Failure to configure these settings can result in slow network performance and system failures.

Hardware Connections

The 4695 comes with two COM ports labeled A and B.� Port A corresponds to COM 1 and port B corresponds to COM 2.

The cash drawer(s) utilize port 3A and/or 3B.� The correct cable, supplied by IBM, will have a number 3 printed on the cable to designate its use.

The customer display utilizes port 4.� The correct cable, supplied by IBM, will have a number 4 printed on the cable to designate its use.

The MSR plugs into the right side of the touch screen.� Plug covers may have to be removed prior to installing the MSR.

Aloha POS Settings

In the Aloha application software terminal maintenance, set the Terminal Type to IBM 4695.� To select the IBM 4695 customer display port in the Aloha application software, select IBM4695 ANOP A as the Pole Display Type.

To assign the IBM 4695 cash drawer ports to the Aloha application software, select either IBM4695 A or IBM4695 B as the Cash Drawer Type in cash drawer maintenance.

The IBM4695MSR variable described previously in this document is the only setting required to enable the 4695's integrated MSR within the system.

Should the Aloha application software Front-of-House (FOH) pause for an extended time while initializing peripherals, check the terminal's debout file to determine the problem.� It is typically caused by an IBM cash drawer, IBM MSR, or IBM customer display defined in the Aloha application software that is either not attached, incorrectly attached, or is defective.� The Aloha application software will timeout after three minutes and eventually start without the use of the peripheral in question.

AUTOEXIT

Using the Aloha application software on the 4695 requires the AUTOEXIT system environment variable.� If you are using Windows NT, configure the REBOOTNT system environment variable in conjunction with AUTOEXIT.� Refer to document AKBID1175 for more information on restart options.

The Aloha application software may not initialize the POSS drivers properly unless the terminal is restarted after the FOH exits.

LPT Port Settings

If you are connecting a parallel receipt or chit printer to the 4695, then you must ensure that the LPT port is not set to ECP mode in either the system BIOS or in the Windows hardware configuration.� Configuring the LPT port to ECP mode can result in system lock-ups.

In some cases, the LPT port might default to sharing an interrupt (IRQ) with the Device Channel once you manually configure the port to a different mode in the system BIOS.� In this case, you will have to manually configure the Device Channel to a different IRQ in the system BIOS, such as IRQ 11 (leaving the LPT port as the sole user of IRQ seven), in order for everything to function properly.

Extended Information

No information.

Caveats

If you use IBM OPOS drivers instead of the IBM POSS drivers to interface the IBM 4695 peripherals to the Aloha application software, do not use this document.� Instead, set the terminal up as a clone, and use OPOS as the device type for the peripherals.� Refer to document AKBID1074 for more information.

The IBM 4695 comes in two major versions: Model 4695-2xx and Model 4695-3xx.� This number is found on the back of the terminal under the rear cover.� Ensure you are aware of the version when applying the instructions described in this document.

If you are not attaching IBM's integrated MSR to the terminal, do not set the MSR variable as described in this document.

�

Should the Aloha application software FOH pause for an extended time while initializing peripherals, check the terminal's debout file to determine the problem.� It is typically caused by an IBM cash drawer, IBM MSR, or IBM customer display defined in the Aloha application software that is either not attached, incorrectly attached, or is defective.� The Aloha application software will timeout after three minutes and eventually start without the use of the peripheral in question.

If you do not make the changes to the 4695-3xx NIC described in this document, it can cause abnormal behavior, as well as system failure.

The Aloha application software may not initialize the POSS drivers properly unless the terminal is restarted after the FOH exits.

�============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1074 OPOS

AKBID1175 Aloha Terminal Restart Options

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1032 possuite stage staging

PAR POS 4 POS Terminal

PAR POS 4 POS Terminal

============================================================================

AKBID1033

Created: 1 March 2000

Updated: 31 January 2001

Reviewed: 4 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: PAR POS 4 Setup for the Aloha Application Software

============================================================================

Summary

The PAR^� POS 4 POS terminal requires specific settings for use with the ALOHA^� application software.� The settings include the integrated magnetic stripe reader (MSR), cash drawers, and customer (or rear) display.� This document explains how to configure these settings.

Information

The basic operating system (OS) setup mimics the Aloha Technologies standard setup recommendations, regardless of the OS type.� Aloha Technologies suggests reviewing the appropriate Aloha Knowledge Base (AKB) document for your OS before preceding any further with this document.

This document is written under the assumption that you have followed the Aloha Technologies suggested OS setup as described in the appropriate AKB document.

Device and OPOS Drivers

Aloha Technologies interfaces with OLE for Retail Point-of-Sale (OPOS) drivers (refer to document AKBID1074) to initialize the cash drawer ports, integrated MSR, and customer display.� You must install the PAR Win32 Device Drivers before installing the PAR OPOS drivers.� Contact PAR to obtain these drivers.

�

You must install the PAR Win32 Device Drivers before installing the PAR OPOS drivers.

Test the appropriate OPOS drivers by selecting Start/Programs/Par OPOS, and selecting Par OPOS Test.

Windows Settings

You must adjust the Plug and Play BIOS setting in order for Windows to restart properly.

Select Start/Settings/Control Panel, and double-click System.� Select the Device Manager tab and expand the System Devices tree.� Double-click Plug and Play BIOS, select the Settings tab, and select 'Disable NVRAM/ESCD Updates'.

Aloha POS Settings

Set the MSR, cash drawers and customer display type to OPOS when configuring the devices in the Aloha application software.

Refer to document AKBID1074 for more information on OPOS drivers.

Extended Information

No information.

Caveats

You must install the PAR Win32 Device Drivers before installing the PAR OPOS drivers.

============================================================================

See also:

AKBID1010 Aloha Application Software System Environment Variables

AKBID1074 OPOS

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1033 partech pos4 stage staging

Using a WAN and Corporate Gift Certificates

Using a WAN and Corporate Gift Certificates

============================================================================

AKBID1034

Created: 13 December 2000

Updated: 18 March 2002

Reviewed: 24 February 2004

Microsoft Windows Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

Subject: Using a Wide Area Network and Corporate Gift Certificates

============================================================================

Summary

The ALOHA^� application software can use a Wide-Area-Network (WAN) to transfer and consolidate Aloha Gift Certificate Manager sales and inventory information between stores and a corporate office.� This document explains using a WAN to send gift certificate information from a store to a corporate office and back.

A valid read/write network connection must be established between the corporate office and each store (and vice versa) before the procedures and applications in this document will function properly.

Information

The 'Corporate Gift Certificate' process uses five steps (divided into three stages):

Stage One:

Each store purges any 'purgable' gift certificate information.

Each store exports gift certificate information to a folder at the corporate office.

Stage Two:

The corporate office imports and processes the gift certificate information from the stores.

The corporate office exports the updated gift certificate information to be retrieved by each store.

Stage Three:

Each store imports the new gift certificate information from the corporate office.

It is important to stagger the times of each stage and step in the process as well as the times that each store interacts with the corporate office's file server.� The latter is not required, but it ensures the corporate office file server is not over-burdened or exceeds the number of simultaneous connections allowed Microsoft^� Windows^�.

For example, a corporate office and three stores may use the following timetable:

Location

Time

Task

Store One

3:00 AM

Purge and export gift certificate information to the corporate office.

Store Two

3:10 AM

Purge and export gift certificate information to the corporate office.

Store Three

3:20 AM

Purge and export gift certificate information to the corporate office.

Corporate Office

3:30 AM

Import gift certificate information from the stores.

Corporate Office

3:50 AM

Export gift certificate information to the stores.

Store One

4:00 AM

Import gift certificate information from the corporate office.

Store Two

4:10 AM

Import gift certificate information from the corporate office.

Store Three

4:20 AM

Import gift certificate information from the corporate office.

Install Gift Certificate Manager at the Corporate Office

Install Gift Certificate Manager from the Aloha Installation CD, and configure the BackOffice License Manager with the correct user information.�

This document is based on Gift Certificate Manager version 3.03 SP4 or higher.� After installing Gift Certificate Manager, ensure version compliance with this document.

You must select the 'Corporate Office' option when installing Gift Certificate Manager.

Set the Export and Import Gift Certificates Location at the Corporate Office

Designate folders to import and export gift certificate information.� For example, create C:\TO_CORP and C:\TO_STORE folders on the file server.�

After creating the folders, open the Aloha BackOffice Main Menu and select Gift Certificate Manager.� Select 'Gift Certificate Import' from the operations menu, and select Options/Program Setup.� Add C:\TO_CORP to the 'Directory Name' text box.�

Open the Aloha BackOffice Main Menu and select Gift Certificate Manager.� Select 'Gift Certificate Export' from the operations menu, and select Options/Program Setup.� Select 'Manual File Exchange' as the transport method and add C:\TO_STORE to the 'File Export Path' text box.

A separate folder for each store is automatically created inside of the gift certificate export folder the first time the export application is initialized (for example, C:\TO_STORE\00123).

If the 'Gift Certificate Import' and 'Gift Certificate Export' option do not appear in the Operations menu, reinstall the Gift Certificate Manager application and select 'Corporate Office'.

Create GCIMP.BAT at the Corporate Office to Import Gift Certificate Info from the Store

After each store has sent the gift certificate information, the corporate office must use a .BAT file to process the information.

If you are using Windows 95, Windows 98, or Windows Me, configure Task Scheduler to launch the .BAT file.� If you are using Windows NT^�, Windows 2000 or Windows XP, configure Windows Schedule Service (refer to document AKBID1047) to launch the .BAT file.� Configure the launch time as described at the beginning of this document.

Create GCIMP.BAT in the Windows folder, and add the following information to GCIMP.BAT:

Navigate to the BackOffice folder.� In this example, the BackOffice folder is in the D:\ALOHA\BACKOFFICE folder.

D:

CD\ALOHA\BACKOFFICE

Initialize GCIMPORT.EXE to import the updated information.

GC\GCIMPORT.EXE /AUTO

Finished.

EXIT

Create GCEXP.BAT at the Corporate Office to Export the Gift Certificate Info to the Store

After the corporate office imports and processes the gift certificate information from the store, the new information is exported for the stores to retrieve and process.

�

If you are using Windows 95, Windows 98, or Windows Me, configure Task Scheduler to launch the .BAT file.� If you are using Windows NT, Windows 2000 or Windows XP, configure Windows Schedule Service (refer to document AKBID1047) to launch the .BAT file.� Configure the launch time as described at the beginning of this document.

Create GCEXP.BAT in the Windows folder, and add the following information to GCEXP.BAT:

Navigate to the BackOffice folder.� In this example, the BackOffice folder is in the D:\ALOHA\BACKOFFICE folder.

D:

CD\ALOHA\BACKOFFICE

Initialize GCIMPORT.EXE to import the updated information.

GC\GCEXPORT.EXE /AUTO

Finished.

EXIT

Install Aloha Gift Certificate Manager at the Store

Install Gift Certificate Manager from the Aloha Installation CD, and configure the BackOffice License Manager with the correct user information.�

This document is based on Gift Certificate Manager version 3.03 SP4 or higher.� After installing Gift Certificate Manager, ensure version compliance with this document.

You must select the 'Corporate Store' option when installing Gift Certificate Manager.

If you do not install the demonstration database or a database from the corporate office with the store already configured in it, you will receive an error at the store stating 'Unable to Initialize GC Server' or 'Unable to Initialize the Gift Certificate services.� Can't continue' when starting the Aloha interface.

Set the Export and Import Gift Certificates Location at the Store

Designate the gift certificate export and import folders already on the corporate office file server as the store's export and import folders using Universal-Naming-Convention (UNC) paths by opening the Aloha BackOffice Main Menu and select Gift Certificate Manager.� Select 'Gift Certificate Import' from the operations menu, and select Options/Program Setup.� Add the UNC path to the store's folder inside of the TO_STORE folder on the corporate office to the 'Directory Name' text box (for example, \\ALOHABOH\BOOTDRV\TO_STORE\00123).

Select 'Gift Certificate Export' from the operations menu, and select Options/Program Setup.� Select 'Manual File Exchange' as the transport method and add the UNC path to the TO_CORP folder on the corporate office to the 'Directory Name' text box (for example, \\ALOHABOH\BOOTDRV\TO_CORP).

If the 'Gift Certificate Import' and 'Gift Certificate Export' option do not appear in the Operations menu, reinstall the Gift Certificate Manager application and select 'Corporate Store'.

Configure AutoRun at the Store to Purge and export Gift Certificates at the Store

To configure AutoRun to purge, process, and send the gift certificate information to the corporate office each night, select AutoRun from the Operations menu in the Gift Certificate Manager, and add the following programs:

Since the paths listed below are based on the %IBERDIR%\BACKOFFICE folder as the root folder instead of the actual root drive folder, the Browse button is not compatible and should not be used.

Field

Information

Title

Gift Certificate Purge

Command Line

GC\GCPURGE.EXE AUTO

Working Directory

%IBERDIR%\BACKOFFICE

Wait For Programs To Finish�

Yes

Field

Information

Title

Gift Certificate Export

Command Line

GC\GCEXPORT.EXE AUTO

Working Directory

%IBERDIR%\BACKOFFICE

Wait For Programs To Finish�

Yes

Perform the following to set the time for AutoRun to start (configure the launch time as described at the beginning of this document):

1.        Open the Aloha Interface.

2.        Select File/Setup/General.

3.        Set the time in the 'At Business Date Roll Time Of' text box.

4.        Select 'Execute AutoRun Program'.

5.        Click 'OK'.�

Since AutoRun requires the BackOffice Interface to be active, AutoRun may not be compatible with some restaurants, so if you are using Windows 95, Windows 98, or Windows Me, configure Task Scheduler to launch a .BAT file in place of using AutoRun.� If you are using Windows NT, Windows 2000 or Windows XP, configure Windows Schedule Service (refer to document AKBID1047) to launch a .BAT file in place of AutoRun.� Configure the launch time as described at the beginning of this document and create GCPURGEX.BAT in the Windows folder, and add the following information to GCPURGEX.BAT:

Navigate to the BackOffice folder.� In this example, the BackOffice folder is in the D:\ALOHA\BACKOFFICE folder.

D:

CD\ALOHA\BACKOFFICE

Initialize GCEXPORT.EXE to export the gift certificates.

START /WAIT GC\GCPURGE.EXE AUTO

Initialize GCPURGE.EXE to purge the gift certificates.

START /WAIT GC\GCEXPORT.EXE AUTO

Finished.

EXIT

Create GCIMP.BAT at the Store to Retrieve Gift Certificate Info from the Corporate Office

After the corporate office had processed the gift certificate information, the store must use a .BAT file to retrieve the updated information and process it.

If you are using Windows 95, Windows 98, or Windows Me, configure Task Scheduler to launch the .BAT file.� If you are using Windows NT, Windows 2000 or Windows XP, configure Windows Schedule Service (refer to document AKBID1047) to launch the .BAT file.� Configure the launch time as described at the beginning of this document.

Create GCIMP.BAT in the Windows folder, and add the following information to GCIMP.BAT:

Navigate to the BackOffice folder.� In this example, the BackOffice folder is in the D:\ALOHA\BACKOFFICE folder.

D:

CD\ALOHA\BACKOFFICE

Initialize GCIMPORT.EXE to import the updated information.

GC\GCIMPORT.EXE /AUTO

Finished.

EXIT

Extended Information

No information.

Caveats

A valid read/write network connection must be established between the corporate office and each store (and vice versa) before the procedures and applications in this document will function properly.

You must select the 'Corporate Office' option when installing Gift Certificate Manager at the corporate office.

If the 'Gift Certificate Import' and 'Gift Certificate Export' option do not appear in the Operations menu at the corporate office, reinstall the Gift Certificate Manager application and select 'Corporate Office'.

You must select the 'Corporate Store' option when installing Gift Certificate Manager at the store.

If you do not install (at the store) the demonstration database or a database from the corporate office with the store already configured in it, you will receive an error at the store stating 'Unable to Initialize GC Server' or 'Unable to Initialize the Gift Certificate services.� Can't continue' when starting the Aloha interface.

If the 'Gift Certificate Import' and 'Gift Certificate Export' option do not appear in the Operations menu at the store, reinstall the Gift Certificate Manager application and select 'Corporate Store'.

Since the AutoRun paths are based on the %IBERDIR%\BACKOFFICE folder as the root folder instead of the actual root drive folder, the Browse button is not compatible and should not be used.

============================================================================

See also:

Aloha Enterprise Messenger User Manual

Aloha Gift Certificate Manager User Manual

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1047 Microsoft Windows Schedule Service

AKBID1061 Using E-Messenger to Send Aloha Data to a Corporate Office

AKBID1135 Using E-Messenger and Corporate Gift Certificates

AKBID1143 E-Messenger PACKAGE.DAT Files

AKBID1168 Configuring Gift Cards for Use with Gift Certificate Manager

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1034 broadband dsl

�

Windows NT FOH Terminal Setup

Windows NT FOH Terminal Setup

============================================================================

AKBID1035

Created: 17 March 2000

Updated: 17 March 2003

Reviewed: 1 March 2004

Microsoft Windows Versions: Windows NT

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

Subject: Windows NT FOH Terminal Setup

============================================================================

Summary

The ALOHA^� application software requires several specialized settings (as well as several preferred settings) in the Microsoft^� Windows NT^� operating system (OS) to properly run on a terminal.� If you are using the terminal to run both Aloha Front-of-House (FOH) and Back-of-House (BOH) together, refer to document AKBID1037.

Information

This document is written for users familiar with Microsoft Windows NT.

Since some computers come with Windows NT preloaded while others do not, this document is based on editing the settings of Windows NT.� Users who are installing Windows NT from scratch or upgrading another OS to Windows NT can still use this document either by employing these instructions after the Windows NT installation or by making many of these changes during the Windows NT installation.

In regards to the Aloha application software functionality, the only difference between Windows NT Server and Windows NT Workstation is the number of user connections allowed.� Windows NT Workstation enables up to 10 connections, and you cannot increase this number.� Microsoft Windows NT Server limits the number of users to the number of licenses purchased.� Breaking the connection limit may disrupt the Aloha application software.� Refer to AKBID1048 for more information the recommended number of FOH terminals for each operating system.

File System

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

The Windows NT Server setup prompts for a choice between using the computer as a Primary Domain Controller, Backup Domain Controller, and Stand Alone Server.� Choose Stand Alone Server.� If the incorrect option is chosen, Windows must be reinstalled to remedy the problem.

The most important settings in the Aloha application software involve the network settings.� To access these settings, select Start/Settings/Control Panel/Network or right-click the Network Neighborhood icon on your desktop and select Properties.

Both Windows NT Workstation and Windows NT Server prompt for either a Domain name or Workgroup name.� Choose a Workgroup name.� Only experienced network administrators should consider using a Domain name.

Set the Workgroup and network name under the Identification tab.� set the Workgroup name the same on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the Workgroup name, but this name can be of your choice as long as it is consistent throughout the Aloha application software.

Set the terminal�s network name.� Aloha Technologies uses TERM1, TERM2, and so on by default.� Different names may be used, but they must follow Aloha application software specifications.� The terminal name must be a common name used on all terminals (the TERMSTR, refer to document AKBID1010) followed by a number designating the terminal�s ID number.� Examples include ALOHA1, ALOHA2, TSFOH_1, and TSFOH_2.� In this case, the TERMSTR would be 'ALOHA' or 'TSFOH_'.� Different TERMSTR names can not be used within the same Aloha system.� Spaces can not be used, but underscores can.� Leading zeros can not be used unless they are part of the TERMSTR, but it is not recommended.

The Aloha application software can use either TCP/IP or NetBEUI as its network protocol.� Select either one, but both the file server and the terminals must use the same protocol.� Access the protocols under the Protocols tab.�

Assign lana number 000 to the protocol used by the Aloha application software.� Refer to document AKBID1018 for more information.

If you select TCP/IP, Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure that terminals always have an address assigned to them.� The Aloha application software will not function without an IP address assigned to the terminal.� You may have multiple protocols installed as long as the proper protocol for the Aloha application software has been marked as such.

Aloha Share Name

The Aloha application software requires a network share name of BOOTDRV.� This is the required name.� This share needs to be applied to the root folder or drive in which the Aloha folder resides.� To set this share, right-click the drive or folder and choose Sharing.� Set the Share Name to BOOTDRV.

If the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.� Some clients prefer to place the Aloha application software in a special folder in order to limit the shared files, and, therefore, enhance security.� Sharing the entire drive in which the Aloha application software resides also shares other files that reside on the drive, such as Windows.

Display Settings

To access the Display settings, select Start/Settings/Control Panel/Display or right-click the Windows desktop and select Properties.� Select the Settings tab.� Set the Color palette to 256 Colors or higher.� Aloha Technologies typically uses 16-bit color.�

Refer to document AKBID1165 for screen resolution settings.

Do not enable a Windows screen saver.

Time Zone & Daylight Savings

For the file server and all terminals to display the correct time and adjust to Daylight Savings changes properly, the Time and Date settings must be properly configured in Windows.� Select Start/Settings/Control Panel/Date/Time or double-click the time displayed on the task bar.� Ensure the date and time are correct.� Ensure the date and time are correct on the Date & Time tab.� Ensure the correct time zone is chosen on the Time Zone tab.� This time zone needs to be the same on all terminals and the file server.� If the area observes Daylight Savings, then the 'Automatically adjust clock for daylight savings changes' option must be selected on all terminals and the file server.� This can be turned on or off, but it needs to be consistent throughout the Aloha application software.

Login Name

Refer to document AKBID1006 for more information on configuring Windows logins for the Aloha application software.

Install Aloha Software

Once Windows NT is set up according to the standards outlined in this document and you can view the network, use the terminal installation diskette to install the Aloha application software.

To create this diskette, insert the installation CD in the file server�s CD-ROM, and run SETUPPOS.EXE /ADVANCED.� Select Make Diskettes/Create Terminal Installation Diskette from the Main Menu

Once the diskette is created, insert it into the terminal�s floppy drive, and run SETUPTRM.EXE.� The setup program walks you through the rest of the installation.

If the terminal does not have a floppy drive, run the Terminal Installation application directly from the CD-ROM on the file server.� Map a drive to the CD-ROM on the file server.� Do not choose the Reconnect at Logon option when mapping the drive.� Run the file \TERMINST\SETUPTRM.EXE from the Aloha POS CD.� The setup program walks you through the rest of the installation.

Service Pack

Install Windows NT Service Pack 4 or higher after all software has been installed and Windows NT is configured properly.�

Reinstall the Service Pack anytime significant changes are made to Windows NT.

Save System Configuration

To save the system configuration, select Start/Run, and enter the command line RDISK /S.� Click OK.� Windows NT starts the Rescue Disk routine, saves the current configuration, and prompts to create or update the system�s Rescue Disk.�

Perform this routine anytime significant changes are made to Windows NT.

Set Control Server and EDC Server Login on the File Server

You may need to adjust the login account used by CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) on the file server to ensure proper operation with terminals running Windows NT.� Refer to AKBID1197 for more information.

Extended Information

No Information.

Caveats

The Windows NT Server setup prompts for a choice between using the computer as a Primary Domain Controller, Backup Domain Controller, and Stand Alone Server.� Choose Stand Alone Server.� If the incorrect option is chosen, Windows must be reinstalled to remedy the problem.

Both Windows NT Workstation and Windows NT Server prompt for either a Domain name or Workgroup name.� Choose a Workgroup name.� Only experienced network administrators should consider using a Domain name.

============================================================================

See also:

AKBID1005 Microsoft Windows Automatic Log In

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1010 Aloha Application Software System Environment Variables

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1018 Network Lana Numbers

AKBID1036 Windows NT File Server Setup

AKBID1037 Windows NT Server/Terminal Setup

AKBID1048 Aloha Application Software Hardware and OS Specifications

AKBID1165 FOH Screen Resolution Settings

AKBID1175 Aloha Terminal Restart Options

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1197 Assigning Logins to Aloha Services

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1035 stage staging

Windows NT File Server Setup

Windows NT File Server Setup

============================================================================

AKBID1036

Created: 6 January 2000

Updated: 17 March 2003

Reviewed: 2 March 2004

Microsoft Windows Versions: Windows NT

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

Subject: Windows NT File Server Setup

============================================================================

Summary

The ALOHA^� application software requires several specialized settings (as well as several preferred settings) in the Microsoft^� Windows NT^� operating system (OS) to properly run on the file server.� If you are using the file server to run both Aloha Front-of-House (FOH) and Back-of-House (BOH) together, refer to document AKBID1037.

Information

This document is written for users familiar with Microsoft�s Windows NT.

Since some computers come with Windows NT preloaded while others do not, this document is based on editing the settings of Windows NT.� Users who are installing Windows NT from scratch or upgrading another OS to Windows NT can still use this document either by employing these instructions after the Windows NT installation or by making many of these changes during the Windows NT installation.

In regards to the Aloha application software functionality, the only difference between Windows NT Server and Windows NT Workstation is the number of user connections allowed.� Windows NT Workstation enables up to 10 connections, and you cannot increase this number.� Microsoft Windows NT Server limits the number of users to the number of licenses purchased.� Breaking the connection limit may disrupt the Aloha application software.� Refer to AKBID1048 for more information the recommended number of FOH terminals for each operating system.

Drive Sizes and Partitions

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

The Windows NT Server setup prompts for a choice between using the computer as a Primary Domain Controller, Backup Domain Controller, and Stand Alone Server.� Choose Stand Alone Server.� Only experienced network administrators should consider using one of the other two.� If the incorrect option is chosen, Windows must be reinstalled to remedy the problem.

The most important settings in the Aloha application software involve the network settings.� To access these settings, select Start/Settings/Control Panel/Network or right-click the Network Neighborhood icon on your desktop and select Properties.

Both Windows NT Workstation and Windows NT Server prompt for either a Domain name or Workgroup name.� Choose a Workgroup name.� Only experienced network administrators should consider using a Domain name.

Set the Workgroup and network name under the Identification tab.� set the Workgroup name the same on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the Workgroup name, but this name can be of your choice as long as it is consistent throughout the Aloha application software.

Aloha Technologies uses the network name ALOHABOH by default.� A different name can be used if desired.

The Aloha application software can use either TCP/IP or NetBEUI as its network protocol.� Select either one, but both the file server and the terminals must use the same protocol.� Assign the lana number 000 to the protocol used by the Aloha application software.� Refer to document AKBID1018 for more information.

If you select TCP/IP, Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure that terminals always have an address assigned to them.� The Aloha application software will not function without an IP address assigned to the terminal.� You may have multiple protocols installed as long as the proper protocol for the Aloha application software has been marked as such.

Aloha Share Name

The Aloha application software requires a network share name of BOOTDRV.� This is the required name.� This share needs to be applied to the root folder or drive in which the Aloha folder resides.� To set the share, right-click the drive or folder and choose Sharing.� Set the Share Name to BOOTDRV.

If the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.� Some clients prefer to place the Aloha application software in a special folder in order to limit the shared files, and, therefore, enhance security.� Sharing the entire drive in which the Aloha application software resides also shares other files that reside on the drive, such as Windows.

Display Settings

To access the Display settings, select Start/Settings/Control Panel/Display or right-click the Windows desktop and select Properties.� Select the Settings tab.� Set the Color palette to 256 Colors or higher.� Aloha Technologies typically uses 16-bit color.� The Aloha application software can be run on both a 640x480 pixel display and an 800x600 pixel display, however, Aloha Technologies prefers 800x600 (or better) resolution.

Aloha Technologies typically does not use a screen saver on the file server since some screen savers (the Open GL based screen savers in particular) can sap processor speed.

Time Zone & Daylight Savings

For the file server and all terminals to display the correct time and adjust to Daylight Savings changes properly, the Time and Date settings must be properly configured in Windows.� Select Start/Settings/Control Panel/Date/Time or double-click the time displayed on the task bar.� Ensure the date and time are correct.� Ensure the date and time are correct on the Date & Time tab.� Ensure the correct time zone is chosen on the Time Zone tab.� This time zone needs to be the same on all terminals and the file server.� If the area observes Daylight Savings, then the 'Automatically adjust clock for daylight savings changes' option must be selected on all terminals and the file server.� This can be turned on or off, but it needs to be consistent throughout the Aloha application software.

Login Name

Refer to document AKBID1006 for more information on configuring Windows logins for the Aloha application software.

Install Aloha Software

Once Windows NT is set up to the standards outlined in this document and you can view the network, the Aloha Application Software Installation CD to install the Aloha application software.

Run SETUPPOS.EXE /ADVANCED from the Aloha POS CD.� The setup program walks you through the rest of the installation.

Refer to document AKBID1162 for more information on running Control Server and EDC Server as Windows services.

Service Pack

Install Windows NT Service Pack 4 or higher after all software has been installed and Windows NT is configured properly.�

Reinstall the Service Pack anytime significant changes are made to Windows NT.

Save System Configuration

To save the system configuration, select Start/Run, and enter the command line RDISK /S.� Click OK.� Windows NT starts the Rescue Disk routine, saves the current configuration, and prompt to create or update the system�s Rescue Disk.�

Perform this routine anytime significant changes are made to Windows NT.

Set Control Server and EDC Server Login

If you are running Windows NT or Windows 2000 on your FOH terminals, you may need to adjust the login account used by CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) on the file server to ensure proper operation.� Refer to AKBID1197 for more information.

Extended Information

No Information.

Caveats

The Windows NT Server setup prompts for a choice between using the computer as a Primary Domain Controller, Backup Domain Controller, and Stand Alone Server.� Choose Stand Alone Server.� Only experienced network administrators should consider using one of the other two.� If the incorrect option is chosen, Windows must be reinstalled to remedy the problem.

Both Windows NT Workstation and Windows NT Server prompt for either a Domain name or Workgroup name.� Choose a Workgroup name.� Only experienced network administrators should consider using a Domain name.

============================================================================

See also:

AKBID1005 Microsoft Windows Automatic Log In

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1010 Aloha Application Software System Environment Variables

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1018 Network Lana Numbers

AKBID1027 Windows NT Auto Backup

AKBID1028 Winhook

AKBID1035 Windows NT FOH Terminal Setup

AKBID1037 Windows NT Server/Terminal Setup

AKBID1047 Microsoft Windows NT Schedule Service

AKBID1048 Aloha Application Software Hardware and OS Specifications

AKBID1148 Backup Procedures

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1197 Assigning Logins to Aloha Services

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1036 stage staging

Windows NT File Server/Terminal Setup

Windows NT File Server/Terminal Setup

============================================================================

AKBID1037

Created: 17 April 2000

Updated: 16 April 2003

Reviewed: 2 March 2004

Microsoft Windows Versions: Windows NT

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Microsoft Windows NT File Server and Terminal on the Same Computer Setup

============================================================================

Summary

The ALOHA^� application software requires several specialized settings (as well as several preferred settings) in the Microsoft^� Windows NT^� operating system (OS) to properly run on the run both Aloha Front-of-House (FOH) and Back-of-House (BOH) together on the same computer.� If you are using the computer as a file server only, refer to document AKBID1036.� If you are using the computer as a terminal only, refer to document AKBID1035.

Refer to document AKBID1116 for more information on the limitations of running both the FOH and BOH together on the same PC.

Information

This document is written for users familiar with Microsoft�s Windows NT.

Since some computers come with Windows NT preloaded while others do not, this document is based on editing the settings of Windows NT.� Users who are installing Windows NT from scratch or upgrading another OS to Windows NT can still use this document either by employing these instructions after the Windows NT installation or by making many of these changes during the Windows NT installation.

If you are converting an existing file server to a file server/terminal, refer to the Extended Information section of this document.

In regards to the Aloha application software functionality, the only difference between Windows NT Server and Windows NT Workstation is the number of user connections allowed.� Windows NT Workstation enables up to 10 connections, and you cannot increase this number.� Microsoft Windows NT Server limits the number of users to the number of licenses purchased.� Breaking the connection limit may disrupt the Aloha application software.� Refer to AKBID1048 for more information the recommended number of FOH terminals for each operating system.

Drive Sizes and Partitions

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

The Windows NT Server setup prompts for a choice between using the computer as a Primary Domain Controller, Backup Domain Controller, and Stand Alone Server.� Choose Stand Alone Server.� Only experienced network administrators should consider using one of the other two.� If the incorrect option is chosen, Windows must be reinstalled to remedy the problem.

The most important settings in the Aloha application software involve the network settings.� To access these settings, select Start/Settings/Control Panel/Network or right-click the Network Neighborhood icon on your desktop and select Properties.

Both Windows NT Workstation and Windows NT Server prompt for either a Domain name or Workgroup name.� Choose a Workgroup name.� Only experienced network administrators should consider using a Domain name.

Set the Workgroup and network name under the Identification tab.� set the Workgroup name the same on all terminals and the file server/terminal.� Aloha Technologies generally uses IBERTECH as the Workgroup name, but this name can be of your choice as long as it is consistent throughout the Aloha application software.

Set the terminal�s network name.� Aloha Technologies uses TERM1, TERM2, and so on by default.� Different names may be used, but they must follow Aloha application software specifications.� The terminal name must be a common name used on all terminals (the TERMSTR, refer to document AKBID1010) followed by a number designating the terminal�s ID number.� Examples include ALOHA1, ALOHA2, TSFOH_1, and TSFOH_2.� In this case, the TERMSTR would be 'ALOHA' or 'TSFOH_'.� Different TERMSTR names can not be used within the same Aloha system.� Spaces can not be used, but underscores can.� Leading zeros can not be used unless they are part of the TERMSTR, but it is not recommended.� The file server/terminal is usually terminal 1.

The Aloha application software can use either TCP/IP or NetBEUI as its network protocol.� Select either one, but both the file server/terminal and the terminals must use the same protocol.� Assign the lana number 000 to the protocol used by the Aloha application software.� Refer to document AKBID1018 for more information.

If you select TCP/IP, Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure that terminals always have an address assigned to them.� The Aloha application software will not function without an IP address assigned to the terminal.� You may have multiple protocols installed as long as the proper protocol for the Aloha application software has been marked as such.

Aloha Share Name

The Aloha application software requires a network share name of BOOTDRV.� This is the required name.� This share needs to be applied to the root folder or drive in which the Aloha folder resides.� To set the share, right-click the drive or folder and choose Sharing.� Set the Share Name to BOOTDRV.

If the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.� Some clients prefer to place the Aloha application software in a special folder in order to limit the shared files, and, therefore, enhance security.� Sharing the entire drive in which the Aloha application software resides also shares other files that reside on the drive, such as Windows.

Display Settings

To access the Display settings, select Start/Settings/Control Panel/Display or right-click the Windows desktop and select Properties.� Select the Settings tab.� Set the Color palette to 256 Colors or higher.� Aloha Technologies typically uses 16-bit color.�

Refer to document AKBID1165 for screen resolution settings.

Do not enable a Windows screen saver.

Time Zone & Daylight Savings

For the file server/terminal and all terminals to display the correct time and adjust to Daylight Savings changes properly, the Time and Date settings must be properly configured in Windows.� Select Start/Settings/Control Panel/Date/Time or double-click the time displayed on the task bar.� Ensure the date and time are correct.� Ensure the date and time are correct on the Date & Time tab.� Ensure the correct time zone is chosen on the Time Zone tab.� This time zone needs to be the same on all terminals and the file server/terminal.� If the area observes Daylight Savings, then the 'Automatically adjust clock for daylight savings changes' option must be selected on all terminals and the file server/terminal.� This can be turned on or off, but it needs to be consistent throughout the Aloha application software.

Login Name

Refer to document AKBID1006 for more information on configuring Windows logins for the Aloha application software.

Install Aloha Software

Once Windows NT is set up according to the standards outlined in this document and you can view the network, use the Aloha Application Software Installation CD to install the Aloha application software.

Run SETUPPOS.EXE /ADVANCED from the Aloha POS CD.� The setup program walks you through the rest of the installation.� You must select 'Run Front of House and Back of House on same PC' on the Aloha Configuration window.

Refer to document AKBID1162 for more information on running Control Server and EDC Server as Windows services.

Aloha Application Software Versions 4.2x � 5.0x

Perform the following to remove the NONET variable from the Control Server variables in the Windows Registry:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_CLASSES_ROOT\AppId\{81DD90A1-CF22-11D1-A84F-0080AD1C6910}.

3.        Then double-click AlohaCtlSrvParameters and remove the NONET variable from Value Data.

4.        Select Registry/Exit to exit the Windows Registry Editor.

Restarting the FOH

Refer to document AKBID1116 for more information regarding restarting the FOH in this type of environment.

Service Pack

Install Windows NT Service Pack 4 or higher after all software has been installed and Windows NT is configured properly.�

Reinstall the Service Pack anytime significant changes are made to Windows NT.

Save System Configuration

To save the system configuration, select Start/Run, and enter the command line RDISK /S.� Click OK.� Windows NT starts the Rescue Disk routine, saves the current configuration, and prompt to create or update the system�s Rescue Disk.�

Perform this routine anytime significant changes are made to Windows NT.

Extended Information

Converting an Existing File Server to a File Server/Terminal

The steps for converting an existing file server to a file server/terminal depend on the usage.

If you are not going to make the file server/terminal master or server-capable (such as a COM interface server or a remote print server), then you can just add the MASTERCAPABLE, SERVERCAPABLE, LOCALDIR, TERM, CALIBRATE, and IBERROOT variables to the system environment variables and assign the proper values to them; and optionally configure a looping batch file to restart the FOH (refer to document AKBID1116).

If at any time you will make the file server/terminal master and/or server-capable, then you must add the MASTERCAPABLE, SERVERCAPABLE, LOCALDIR, TERM, CALIBRATE, and IBERROOT variables to the system environment variables and assign the proper values to them; rename the file server/terminal to match the TERMSTR+TERM nomenclature (Aloha Technologies suggests making it terminal one); and optionally configure a looping batch file to restart the FOH (refer to document AKBID1116).

Caveats

The Windows NT Server setup prompts for a choice between using the computer as a Primary Domain Controller, Backup Domain Controller, and Stand Alone Server.� Choose Stand Alone Server.� Only experienced network administrators should consider using one of the other two.� If the incorrect option is chosen, Windows must be reinstalled to remedy the problem.

Both Windows NT Workstation and Windows NT Server prompt for either a Domain name or Workgroup name.� Choose a Workgroup name.� Only experienced network administrators should consider using a Domain name.

============================================================================

See also:

AKBID1005 Microsoft Windows Automatic Log In

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1010 Aloha Application Software System Environment Variables

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1018 Network Lana Numbers

AKBID1027 Windows NT Auto Backup

AKBID1028 Winhook

AKBID1035 Windows NT FOH Terminal Setup

AKBID1036 Windows NT File Server Setup

AKBID1047 Microsoft Windows NT Schedule Service

AKBID1048 Aloha Application Software Hardware and OS Specifications

AKBID1116 File Server/Terminal Limitations

AKBID1148 Backup Procedures

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1165 FOH Screen Resolution Settings

AKBID1175 Aloha Terminal Restart Options

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1037 boh/foh bohfoh foh/boh fohboh stage staging terminal/server

Report Command Line Parameters

Report Command Line Parameters

============================================================================

AKBID1038

Created: 9 February 2000

Updated: 10 October 2003

Reviewed: 3 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: Report Command Line Parameters

============================================================================

Summary

You can print ALOHA^� application software reports from a command line, which enables you to automatically print reports for a Date-of-Business (DOB) each night using Winhook (refer to document AKBID1028).� This document explains the report command line parameters and usage information associated with RPT.EXE.

Information

Command Line

RPT.EXE uses the following syntax and parameters:

1.        /IBERDIR declares the location of the Aloha application software folder.� This does not need to be declared if the variable already resides in the system environment.

2.        /DATE specifies the DOB to report.� It is based on the dated folder's label.� Winhook uses the %1 variable to specify the date.� The %1 parameter is standard syntax for referring to command-line variables from within a batch file.� Refer to document AKBID1028 for more information on the %1 parameter.

3.        /Rz to specifies the report to print.� Replace z with a parameter listed later in this document.

4.        In versions 5.2x and higher, use LOAD "y" to specify a setting file for the Labor Report, Sales Report, and Product Mix Report, where y if the report settings file name.

5.        In versions 5.2x and higher, use /Xz in place of /Rz to export the report to a file rather than print the report.� Replace z with a parameter listed later in this document.� The report is exported using the format and location information already existing in the report's export settings.� The export will not function properly unless you have previously saved these settings in Aloha Manager, which creates an .EXP file for this report.

The following command line prints a Sales (Cash) Report for 1/7/2000 in versions 5.0x and lower:

%IBERDIR%\BIN\RPT.EXE /DATE 20000107 /RC

The following command line prints a Sales (Cash) Report for 1/7/2000 in versions 5.2x and higher using the 'default' settings:

%IBERDIR%\BIN\RPT.EXE /DATE 20000107 /RC LOAD "DEFAULT.SLS.SET"

The following command line exports a Sales (Cash) Report for 1/7/2000 in versions 5.2x and higher using the 'default' settings:

%IBERDIR%\BIN\RPT.EXE /DATE 20000107 /XC LOAD "DEFAULT.SLS.EXP"

/DAYS n creates a report for a span of consecutive days defined by n.� The n variable defines the number of previous days to include in the report, including the date specified by the DATE variable.� For example, to print a report for 5/1/2001 through 5/7/2001, you would use the following command line:

%IBERDIR%\BIN\RPT.EXE /DATE 20010507 /RC /DAYS 7

As of this writing, the /DAYS variable is not currently functioning properly.

Report Parameters

Parameter

Function

A

Labor Report.� In versions 5.0x and lower, use /NUM n to declare the Labor Report number (1-3).

AD

Daily Cashout Summary

B

Employee Break Report

C

Sales Report

CW

Weekly Sales Report

D

ADP Payroll Export File

DD

Delivery Driver Report

DP

Delivery Production Report

E

Entertainer Income Report

F

ReMacs Menu Item Sales Export File

G

Gift Certificate Tracking Report

H

Hourly Sales and Labor Report

HW

Weekly Hourly Sales and Labor Report

I

Menu Item Forecast Report

J

Tip Income Report

K

Comparative Server Sales Report

L

Scheduled Vs Actual Labor Report.� Use /TYPE =x to declare the group to report (E for employee, C for job code, G for job group).� Use /PRD y to declare the time period (D for day, W for week, and M for month).

M

Edited Punches Report

N

Surcharge Report

O

Overtime Warning Report

OD

Open Drawer Report

P

Product Mix Report

PQ

Weekly Quick Count Report

PW

Weekly Product Mix Report

Q

Employee Performance Measures Report

R

RealWorld Payroll Export File

S

Landry's Sales Report

T

Top Item Movement Report

TS

Team Service Tip Split Report

U

Edit Deposits Report

V

Void Report

W

Server Sales Report (There is not a way to select the employees to list in this report from a command line, so printing this report from a command line produces a blank report.)

Y

Payment Detail Report

Z

Sales By Revenue Center Report

1

Coconut Code Payroll Export File

11

Overtime Forecast Report

2

Coconut Code Sales Mix Export File

3

Coconut Code Daily Sales Export File

4

Back-of-House User Security

5

Back-of-House Security Levels

6

Detailed Access Levels

7

Front-of-House Cash Owed Report

8

Speed of Service Report

9

Tiered Tax Report

Windows NT, Windows 2000, and Windows XP

Windows NT^�, Windows 2000, and Windows XP users may experience error messages regarding the 'default printer' when trying to print reports via Winhook.� In this case, you must edit the Windows registry to ensure the default printer is properly defined before Winhook can print reports.�

The incorrect use of the Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

All Registry entries are case sensitive.

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Devices.

3.        Verify if a string for the default printer exists with a value of winspool,LPT1:.� Note the printer name assigned to the string's name.

4.        Path out HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\PrinterPorts.

5.        Verify if a string for the default printer exists with a value of winspool,LPT1:,14,45 (or something similar, such as winspool,LPT1:,15,45).� Note the value assigned to the printer string.

6.        Path out HKEY_CURRENT_USER\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows.

7.        Verify if the Device string exists with a value of <printer name>,winspool,LPT1:.

8.        HKEY_USER\DEFAULT\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Devices.

9.        Create a new string based on the printer's name and assign a value of winspool,LPT1:.

10.     HKEY_USER\DEFAULT\SOFTWARE\Microsoft\Windows NT\CurrentVersion\PrinterPorts.

11.     Create a new string name based on the printer's name and assign the same value as assigned in step 5.� For example, winspool,LPT1:,14,45.

12.     Path out HKEY_USER\DEFAULT\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Windows.

13.     Verify if the Device string exists with a value of <printer name>,winspool,LPT1:.

14.     Select Registry/Exit to exit the Windows Registry Editor.

15.     Restart Windows.

Extended Information

Deposit Prompt

Some reports prompt you for a deposit if you have not already entered one for the DOB. �

In versions 5.0x and lower, you can suppress this prompt by creating a null DEPOSIT.TXT.� The deposit information is stored in the DEPOSIT.TXT located in the dated folder, and creating a new DEPOSIT.TXT before printing the report from Winhook alleviates the problem.� Use the following command to create this file:

ECHO 0 >> %IBERDIR%\%1\DEPOSIT.TXT

The use of >> rather than > will create a new file if DEPOSIT.TXT does not exist, but will append to the file (instead of overwriting it) in case it already exists.

In versions 5.2x and higher, the deposit information is stored in the GNDDEPST.DBF located in the dated folder, and copying a GNDDEPST.DBF with a zero-amount deposit into the dated folder prior to printing the report from Winhook suppresses the prompt.� For example, edit the deposits for a day that does not have any recorded deposits, and add a zero-amount deposit.� Copy the GNDDEPST.* from the dated folder with the newly created zero-amount deposit to a storage area, such as a \ALOHA\NULL_DEP folder.� Add the following command to your batch file prior to the commands that initialize the reports in order to copy the GNDDEPST.DBF to the dated folder:

The following command line wraps to a second line, but it is a single line in the batch file.

IF NOT EXIST %IBERDIR%\%1\GNDDEPST.* COPY %IBERDIR%\NULL_DEP\GNDDEPST.* %IBERDIR%\%1\GNDDEPST.*

Report Setting Templates

You can enable Winhook-specific copies of RPT.SET to ensure the same settings are used each time the report Winhook prints a report.� For example, in version 5.0x and lower, you might want a Product Mix report with only the desserts sold, but somebody previously printed a Product Mix for all items without changing the report settings back to their original configuration when they were finished.� Use the following steps to create and enable Winhook-specific report templates:

�

(Although this method is no longer needed for the Sales Report, Labor Report or Product Mix Report in versions 5.2x and higher, you can still use this for other reports that do not use individual report settings files.)

Edit the report settings to the desired settings.

The report settings are saved in the RPT.SET file in the DATA folder.� Copy this file to RPT.ONE.

If you are printing multiple versions of the same report (for example, two different Product Mix Reports), edit the report settings to the second configuration and copy RPT.SET to RPT.TWO.

Add command lines similar to the following to your Winhook batch file:

�

rem Delete RPT.SAV if it already exists.

DEL %IBERDIR%\DATA\RPT.SAV

rem Save a copy of the current RPT.SET.

REN %IBERDIR%\DATA\RPT.SET %IBERDIR%\DATA\RPT.SAV

rem Enable the preferred settings.

REN %IBERDIR%\DATA\RPT.ONE %IBERDIR%\DATA\RPT.SET

rem Print a Sales Report and Product Mix Report.

%IBERDIR%\BIN\RPT.EXE /DATE %1 /RC

%IBERDIR%\BIN\RPT.EXE /DATE %1 /RP

rem Rename the set file to its original name.

REN %IBERDIR%\DATA\RPT.SET %IBERDIR%\DATA\RPT.ONE

rem Enable the second preferred settings.

REN %IBERDIR%\DATA\RPT.TWO %IBERDIR%\DATA\RPT.SET

rem Print a second Product Mix Report.

%IBERDIR%\BIN\RPT.EXE /DATE %1 /RP

rem Rename the set file to its original name.

REN %IBERDIR%\DATA\RPT.SET %IBERDIR%\DATA\RPT.TWO

rem Bring back the original set file.

REN %IBERDIR%\DATA\RPT.SAV %IBERDIR%\DATA\RPT.SET

WAIT.EXE

Use the WAIT.EXE utility to create a timed pause in a batch file (refer to document AKBID1012 for more information on WAIT.EXE).� Some printers do not have the buffer capabilities to process multiple reports sent in quick succession.� Use WAIT.EXE to create a 30-second pause between each report, which gives the printer time to process the previous report.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1028 Winhook

AKBID3161 Product Mix Report Specific Items Only

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1038 auto rpt switch switches

�

ProHost32

ProHost32

============================================================================

AKBID1039

Created: 6 April 2000

Updated: 15 May 2002

Reviewed: 26 February 2004

Microsoft^� Windows^� Versions: Windows NT^�, Windows 2000

Aloha Products: TableService

Aloha POS Versions: 3.6x � 5.3.x

Subject: Interfacing the Aloha Application Software to ProHost32

============================================================================

Summary

The ALOHA^� application software interfaces with the ProHost32^� table service management software using a series of message files.� His document explains the steps to enable the interface in the Aloha application software, basic interface setup in the ProHost32 software, and the interface functionality.

Information

The Aloha application software interface with ProHost32 is a one-way interface, in that the Aloha application software creates message files that are read by ProHost32, but the Aloha application software does not recognize message files created by ProHost32.

ProHost32 can share a file server with the Aloha application software, or it can use a separate file server.� Although ProHost32 can exist along with the Aloha application software Front-of-House (FOH) software, it is not recommended, since the user must use a keyboard to alternate between the two applications.

ProHost32 utilizes the TCP/IP network protocol using Microsoft Windows Networking, just the Aloha application software does.� ProHost32 does not utilize the NetBEUI network protocol.

Enable the Interface in the Aloha Application Software

The Aloha application software requires a single setting to enable the ProHost32 interface.� Perform the following based on the Aloha application software version:

In versions 4.4x and lower, open Maintenance, and select Interfaces from the System drop-down menu.� Set the TMS type to ProHost.

In versions 5.0x and higher, open Aloha Manager, and select Store Settings from the Maintenance drop-down menu.� Select the System Group, and click the Interfaces tab.� Set the TMS type to ProHost.

Refresh the system.

Enable the Interface in ProHost32

Install and configure the ProHost32 software.� Set the Shared Path, which is the location of the message files from the Aloha application software.� In most cases, path should point to the Aloha application software Tmp folder on the Aloha application software file server, since this is the default location where the Aloha application software writes message files.� If ProHost32 uses a different file server than the Aloha application software, you must use a Universal-Naming-Convention (UNC) name (for example, \\Alohaboh\Bootdrv\Aloha\Tmp).

Since stores in a SuperSite installation dynamically select a file server, the Aloha application software cannot reliably use the default message file location (the Aloha application software Tmp folder on the Aloha application software file server).� In this case, you must enable the PROHOSTDIR environment variable on each terminal in a store.� This variable defines a static location for the message files, such as the ProHost32 file server.� For example, to instruct Aloha application software terminals to write all files to the \\ProHost32\C\Messages folder, use SET PROHOSTDIR=\\ProHost32\C\Messages on each FOH terminal.� Set the same location as the Shared Path in the ProHost32 configuration.� This configuration can be used in non-SuperSites as well.

If a network message file location selected with the PROHOSTDIR variable is not available to the FOH terminals when they attempt to write a message file, the Aloha application software may freeze for up to 30 seconds or more while it tries to write a message file.�

Interface Functionality

When the interface is enabled, the Aloha application software FOH login screen displays two extra buttons: Clean Table, and Bus Request.� There are no other visual indications of the interface in the FOH.

The following table explains the interface functions ('Results in ProHost32' may vary with ProHost32 options):

Aloha Application Software Function

Message File Type

Result in ProHost32

Bus Request Button

DIRTY

Displays a dirty table icon over the table.

Clear Table Button

CLEARED

Displays a clean table.

Open new table

OPENED

Displays a red circle around the table.

Order items

ORDERED

Resets the order timer, if enabled.

Apply payment

PAID

Displays a green circle around the table.

Print check

PRINTED

Displays a light blue circle around the table.

Close check

CLOSED

Displays a green and red circle around the table.

Message Files

The interface creates two types of message files: Termn.pos and Termn.tms, where n is the terminal number, without leading zeros.

Termn.pos holds messages created by the Aloha application software for ProHost32 to read.� ProHost32 deletes the file after it has been read.� The messages are on a single line since carriage returns are not used.� The Aloha application software appends to this file if it already exists.

Termn.tms holds messages created by ProHost32 for application softwares to read.� The messages are on a single line since carriage returns are not used.� ProHost32 appends to this file if it already exists.� The Aloha application software ignores this file, and it may continue to grow unchecked, so you should develop a method for deleting this file on a regular basis, possibly using a batch file automatically fired by the Windows Schedule Service (refer to AKBID1047) or Windows Task Scheduler.

Troubleshooting

If ProHost32 does not respond to messages from the Aloha application software, check the following:

1.        Is the interface enabled in the Aloha application software?

2.        Is the interface enabled in ProHost32?

3.        Does the ProHost32 Shared Path point to the correct folder on the Aloha application software file server?

4.        If ProHost32 is on a separate file server, do the file server and user have network access to the messages folder?

5.        Are the message files created in the correct folder?

6.        Does ProHost32 read and delete the messages from the Aloha application software?

Extended Information

No information.

Caveats

If a network message file location selected with the PROHOSTDIR variable is not available to the FOH terminals when they attempt to write a message file, the Aloha application software may freeze for up to 30 seconds or more while it tries to write a message file.

============================================================================

See also:

Aloha TableService User Manual

ProHost32 User Manual

AKBID1047 Microsoft Windows Schedule Service

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1039 host pro

�

Run Control and Maintenance from Remote Workstation

Run Control and Maintenance from Remote Workstation

============================================================================

AKBID1040

Created: 31 January 2000

Updated: 23 August 2002

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 4.4x

Subject: Creating and Using Remote Copies of Control and Maintenance

============================================================================

Summary

You can configure the ALOHA^� application software Back-of-House (BOH) to access the file server from a remote computer.� This enables multiple users access the BOH for reports and database management.� This document explains how to configure remote copies of Control and Maintenance.

Refer to document AKBID1113 for remote Aloha Manager.

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

Information

Non-relational Database

To install a remote copy of Control on a non-relational database (RDB) system, perform the following steps.

1.        Ensure the Aloha BOOTDRV share allows the remote user access to the file server.

2.        If the remote computer is using the Microsoft^� Windows NT^� or Windows^� 95 operating system (OS), copy the correct CTL3D32.DLL to the local computer.� Obtain the correct version from W95DLL.ZIP or WNTDLL.ZIP from the ALOHATS folder on the Aloha POS Installation CD.� Place it in the Windows SYSTEM32 folder if the remote computer is using Windows NT, or the Windows SYSTEM folder if the remote machine is using Windows 95.� Windows 98, Windows Millennium Edition (Me), and Windows 2000 comes from Microsoft with the correct CTL3D32.DLL file.

3.        Create a shortcut to Control on the desktop:

A.      Right-click any unused portion of the remote computer desktop and select New/Shortcut.

B.       Enter the following command in the 'Command Line' text box being sure to insert the correct server name and Aloha application software folder:

�

\\ALOHABOH\BOOTDRV\ALOHA\BIN\CTL.EXE /IBERDIR \\ALOHABOH\BOOTDRV\ALOHA /REMOTE

C.       Click Next and enter 'Aloha Control' as the shortcut name.

D.      Click Finish.

The remote user can now access Control to view and print reports.�

4.        If the remote user needs to perform maintenance to the database, create a shortcut to Maintenance on the desktop:

A.      Right-click any unused portion of the remote computer desktop and select New/Shortcut.

B.       Enter the following command in the 'Command Line' text box being sure to insert the correct server name and Aloha application software folder:

�

\\ALOHABOH\BOOTDRV\ALOHA\BIN\MNT.EXE /IBERDIR \\ALOHABOH\BOOTDRV\ALOHA

C.       Click Next and enter 'Aloha Maintenance' as the shortcut name.

D.�� Click Finish.

Relational Database (SQL)

To install a remote copy of Control on an RDB system, perform the following steps:

1.        Ensure the Aloha BOOTDRV share allows the remote user access to the Aloha file server.

2.        If the remote computer is using Microsoft Windows NT or Windows 95, copy the correct CTL3D32.DLL to the local computer.� Obtain the correct version from W95DLL.ZIP or WNTDLL.ZIP from the ALOHATS folder on the Aloha POS Installation CD.� Place it in the Windows SYSTEM32 folder if the remote computer is using Windows NT or the Windows SYSTEM folder if the remote machine is using Windows 95.� Windows 98, Windows Me, and Windows 2000 come from Microsoft with the correct CTL3D32.DLL file.

3.        Open the Windows Control Panel by selecting Start/Settings/Control Panel.�

A.      If the remote computer uses the Windows 95, Windows 98, or Windows Me OS, select the 32-bit ODBC icon.� If the remote computer uses the Windows NT or Windows 2000 OS, select the ODBC icon.� If the icon is not present, install ODBC from the ODBC folder on the Aloha Application Software Installation CD.

B.       Click Add from the ODBC Data Sources window.

C.       Select SQL Server from the Installed ODBC Drivers list in the Add Data Source window and click Finish.� The ODBC SQL Server Setup window displays.� If SQL Server is not present in the Add Data Source window, reinstall ODBC from the ODBC folder on the Aloha POS Installation CD and select the option for SQL drivers.

D.      Click Options and clear the 'Generate Store Procedure for Prepared Statement' option.�

E.       Enter AlohaRDB (case sensitive) as the 'Data Source Name'.�

F.       Use 'Aloha SQL' for the Description.�

G.       Enter the file server�s network name (e.g.� ALOHABOH) for the Server.�

H.      Enter ibersql (case sensitive) for the database name.�

I.         Leave the other options to their default settings and click OK.

J.        Close the ODBC window and the Control Panel.

4.        Create a shortcut to Control on the desktop:

A.      Right-click on any unused portion of the remote computer desktop and select New/Shortcut.

B.       Enter the following command in the 'Command Line' text box being sure to insert the correct server name and Aloha application software folder:

�

\\ALOHABOH\BOOTDRV\ALOHA\BIN\CTL.EXE /IBERDIR \\ALOHABOH\BOOTDRV\ALOHA /REMOTE /SQLMODE

C.       Click Next and enter 'Aloha Control' as the shortcut name.

D.      Click Finish.

The remote user can now access Control to view and print reports.�

5.        If the remote user needs to perform maintenance to the database, create a shortcut to Maintenance on the desktop:

A.      Right-click any unused portion of the remote computer desktop and select New/Shortcut.

B.       Enter the following command in the 'Command Line' text box being sure to insert the correct server name and Aloha application software folder:

�

\\ALOHABOH\BOOTDRV\ALOHA\BIN\MNT.EXE /IBERDIR \\ALOHABOH\BOOTDRV\ALOHA /SQLMODE

C.       Click Next and enter 'Aloha Maintenance' as the shortcut name.

D.      Click Finish.

Extended Information

The Windows Remote Access Service (RAS) or Dial-up Networking can be used to access the file server from a location that is not part of the local area network (LAN).� Accessing the BOH with this option can be very slow since typical phone lines and modems do not support the bandwidth of the LAN that is normally used on the Aloha application software.� This option should be thoroughly tested before given to a customer to use.

Remote copies of the non-RDB BOH use the RUNGRIND folder to start the Grind process for the current day's data.� Refer to document AKBID3130.� This does not apply to systems with a RDB database.

Caveats

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

Remote copies of Maintenance may enable multiple users to access the same database file at the same time.� This can cause database corruption or data loss.� It is very important to instruct the users to develop rules of use that prevent this from occurring.�

============================================================================

See also:

AKBID1010 Aloha Application Software System Environment Variables

AKBID3130 RUNGRIND File in the DATA Folder

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1040

�

Multiple Terminal Berg Tap Setup

Multiple Terminal Berg Tap Setup

============================================================================

AKBID1041

Created: 10 February 2000

Updated: 28 August 2002

Reviewed: 8 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.4x � 5.3.x

Subject: Using Multiple POS Terminals with a Single Berg Beer Tap

============================================================================

Summary

The ALOHA^� application software enables up to eight terminals to be connected to a single Berg Company^� Beer Tap unit; therefore a single beer tap can be used to order drinks on multiple terminals. This document explains how to configure multiple terminals on a single the Berg beer tap.

Information

You can assign each button on the Berg tap to a specific item number for ordering on a specific terminal.� For example, button one on a tap can order a beer on terminal one, button two on the same tap can order a beer on terminal two, and so on.� The message is sent via Berg's Fan-Out box to all of the connected Aloha application software terminals.� The terminal with the matching terminal ID accepts the message and reacts, while the remaining terminals ignore the message.�

You enable this ability by configuring the item number programmed into the Berg unit to include both the terminal's ID and the item's ID number.� Assign each button on a beer tap to a number based on the terminal in which the order is to appear coupled with the item ID number to which it coincides.� For example, for button number four to pour a beer assigned to item number 123, and order it on terminal number one (as defined with the MULTILIQUORTAPTERM variable discussed below), assign the string 1123 to the tap's button number four.� To order it on terminal number two, assign the string 2123.

Aloha Application Software Setup

Define a drink dispenser for each terminal interacting with the Berg system.� If you are using versions 4.4x or lower, do this in Maintenance/MX/Accessories/Drink Dispensers.� If you are using versions 5.0x or higher, do this in Aloha Manager/Maintenance/Hardware/Drink Dispensers.� Select the next available ID in the order that already exists.� Select a name (based on the terminal to which it is assigned), the terminal, the COM port Berg will use, and set the type to Berg Liquor.

If you are connecting multiple terminals to one Berg unit, you must define each connected terminal.� For example, if you have six terminals connected to one Berg unit, define all six terminals as described above.

Environment Changes

You must define two environment variables on each terminal.� The first is LIQUORPLUDIGITS.� This variable defines the number of digits in the item number the Berg unit will send to the Aloha application software.� For example, if the beer has an item ID number of 1234 (do not include the leading zeros), set this variable to 4 by adding the line SET LIQUORPLUDIGITS=4 to the system environment variables on each terminal.� This setting does not include the terminal number sent by Berg.� If this variable is not set, the default value is 3.� If you assign a value lower than 1 or higher than 4, it defaults back to 3.

The second variable is MULTILIQUORTAPTERM.� This defines the terminal's number in relation to the terminal number assigned in the Berg software.� It has no relation to the terminal number assigned to the terminal in the Aloha application software.� For example, if you have four terminals connected to the Berg unit, you will assign each terminal a number 1 through 4.� Any Berg pour though a button assigned in the Berg software to terminal 1 orders the item on the Aloha terminal assigned by this variable as terminal 1.� An example of this variable is SET MULTILIQUORTAPTERM=1.� Set this variable in the system environment variables on each terminal

The following is an example of the variables:

SET LIQUORPLUDIGITS=4

SET MULTILIQUORTAPTERM=1

Hardware Setup

Configure the Berg Beer Tap system as explained in documentation provided by Berg.

Extended Information

The cables used by the Berg unit to connect the Berg Fan-Out Box to the Aloha application software terminals are 6 wire (3 pair) cables terminated with six-wire RJ11 ends.� The run is straight through, so there is no wire crossing needed.� If using POS terminals with RJ45 type serial ports, plug these cables directly into the serial port.� If you are using DB9 style serial ports, use an RJ45 to DB9 adapter.� This adapter should be wired straight through.� Refer to documents AKBID1002, AKBID1003, and AKBID1004 for more information.

Caveats

If you are ordering items assigned to a four-digit item number in the Aloha application software, the Berg hardware limits you to six terminals.� For example, if the item is assigned the number 1234, you cannot assign the item to appear on terminal seven via programming the Berg unit for 71234.� If you are connecting more than six terminals to one Berg unit, you need to assign the items to three digit numbers since this will enables up to eight terminals.

============================================================================

See also:

Aloha Accessories User Manual

AKBID1002 Aloha Receipt and Kitchen Printer Settings

AKBID1003 Aloha Network Cable Pin-outs

AKBID1004 Serial Pin Assignments

AKBID1090 Drink Dispensers

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1041

Aloha Application Software Database Files

Aloha Application Software Database Files

============================================================================

AKBID1042

Created: 8 February 2000

Updated: 25 July 2003

Reviewed: 11 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

Subject: Aloha Application Software Database Files

============================================================================

Summary

This document lists the .dbf files used with the ALOHA^� application software, their description, whether they are used with QuickService or TableService, and the numerical reference found in some errors.� Refer to document AKBID1030 for information on Grind (GND) files, and AKBID1081 for more information on Summary (SUM) files.

Information

The Cat.dbf, Cit.dbf, and Pro.dbf files have multiple versions for Store, Regional, and Corporate levels.� This is disabled in versions 5.0x and higher.

Some database files might exist in both QuickService and TableService, even though only one of the two products actually uses the files.� Files in this document are attributed to the product only if they are actually used by the product.

��

Name

Description

QS

TS

Error Reference Number

Acc.dbf

Access Levels

X

X

1100

AdjTime.dbf

Adjusted Labor Hours

X

X

1140

AdjTimex.dbf

Prior Day Labor Edits Performed Today

X

X

N/A

Aloha.ini

Configuration

X

X

1128

Amnu.dbf

Auto Menu

-

X

1159

Amnud.dbf

Auto Menu Details

-

X

1160

Avail.dbf

ALS Employee Availability

X

X

N/A

Bhrs.dbf

ALS Business Hours

X

X

N/A

Btn.dbf

Panel Buttons

X

X

1147

CashCard.dbf

Cash Cards

X

X

1180

Cat.dbf

Categories

X

X

1101

Cat1.dbf

Store-Level Categories

-

-

1101

Cat2.dbf

Regional-Level Categories

-

-

1101

Cat3.dbf

Corporate-Level Categories

-

-

1101

Cevnt.dbf

CDM Event Groups

-

X

N/A

Cevntsub.dbf

CDM Event Group Subscriptions

X

X

N/A

Cit.dbf

Category Items

X

X

1102

Cit1.dbf

Store-Level Category Items

-

-

1102

Cit2.dbf

Regional-Level Category Items

-

-

1102

Cit3.dbf

Corporate-Level Category Items

-

-

1102

Cmg.dbf

Clock-In Messages

X

X

1103

Cmp.dbf

Comps

X

X

1104

Cncpt.dbf

Concepts

X

X

1196

Ctk.dbf

Quick Count Composite Tracking Items

X

-

1162

Dnk.dbf

Drink Dispensers

X

X

1165

Dsplybrd.dbf

Display Boards

X

X

1182

Dwr.dbf

Cash Drawers

X

X

1105

Emp.dbf

Employees

X

X

1106

Empi9.dbf

Employee I9 Information

X

X

N/A

Emppol.dbf

ALS Employee Policies

X

X

N/A

EmpType.dbf

ALS Employee Types

X

X

N/A

Exc.dbf

Exception Modifier Groups

X

X

1107

FixPrice.dbf

Fixed Item Pricing

-

X

1176

FlexTax.dbf

Flex Taxes

X

X

1185

Gci.dbf

Guest Check Information

X

X

1108

GcLog.dbf

Basic Gift Certificate Tracking

X

X

1142

Gif.dbf

Basic Gift Certificates

X

X

1109

Gpredem.dbf

TGI Friday's Gold Points Redeemed

-

X

N/A

Hse.dbf

House Accounts

X

X

1110

Itm.dbf

Items

X

X

1111

Itmgrp.dbf

Item Size Groups

X

-

1185

Itmgrpl.dbf

Item Size Group List

X

-

1186

Job.dbf

Job Codes

X

X

1112

Jrv.dbf

Job by Revenue Center

X

X

N/A

Lab.dbf

Labor Groups

X

X

1113

Label.dbf

Labels

X

X

1181

LabLimit.dbf

ALS Labor Period Limits

X

X

N/A

Laborprj.dbf

ALS Labor Projections

X

X

N/A

Labpdtm.dbf

ALS Labor Period Times

X

X

N/A

Labprd.dbf

ALS Labor Periods

X

X

N/A

Memb.dbf

Memberships

-

X

N/A

MembHold.dbf

Membership Hold Reasons

X

X

N/A

Mnu.dbf

Menus

-

X

1114

Mod.dbf

Modifier Groups

X

X

1115

Msg.dbf

Main Screen Messages

X

X

1134

Multcurr.dbf

Foreign Currencies

X

X

1177

NoSaler.dbf

No Sale Reasons

X

X

1184

Occ.dbf

Occasions

X

X

1171

Oct.dbf

Occasion Categories

X

X

1172

Odr.dbf

Order Modes

X

X

1116

OthWage.dbf

Other Wages

X

X

1197

Pc.dbf

Price Changes

X

X

1167

Pcid.dbf

Price Change Item Detail

X

X

1168

Pcpd.dbf

Price Change Promotion Detail

X

X

1190

Pcpld.dbf

Price Change Price Level Detail

X

X

1169

Pet.dbf

Petty Cash Accounts

X

X

1135

Pkgpro.dbf

Chuck E. Cheese's Package Promos

X

-

N/A

Pkgprocp.dbf

Chuck E. Cheese's Package Promo Components

X

-

N/A

Pkgprogc.dbf

Chuck E. Cheese's Package Promo Group Components

X

-

N/A

Pkgprogp.dbf

Chuck E. Cheese's Package Promo Group Pricing

X

-

N/A

Pnchrsn.dbf

Edit Punch Reasons

X

X

N/A

Pnl.dbf

Panels

X

X

1148

Poll.dbf

Customer Polls

X

X

N/A

PollEvent.dbf

Customer Poll Events

X

X

N/A

Pollsubs.dbf

Customer Poll Subscribers

X

X

N/A

Prd.dbf

Day Parts

X

X

1117

Prf.dbf

Performance Measures

X

X

1118

Prg.dbf

Printer Groups

X

X

1119

Prjc.dbf

Preparation Projections

X

X

1179

Prjt.dbf

Preparation Projection Tracking

X

X

1178

Prl.dbf

Price Levels

X

X

1157

Prntd.dbf

Thumb (Finger) Print Data

X

X

N/A

Pro.dbf

Promotions

X

X

1120

Pro1.dbf

Store-Level Promotions

-

-

1120

Pro2.dbf

Regional-Level Promotions

-

-

1120

Pro3.dbf

Corporate-Level Promotions

-

-

1120

Pron.dbf

N/A

-

-

N/A

Prt.dbf

Printers

X

X

1121

QtyPrice.dbf

Quantity Pricing

X

X

1175

Que.dbf

Order Queues

X

X

1149

Rcp.dbf

Quick Count Composite Item Recipes

X

X

1163

Reg.dbf

Regions

X

X

1170

ReGrind.dbf

Regrind Dated Folders Information

X

X

N/A

ReqRule.dbf

ALS Requirement Rules

X

X

N/A

Required.ini

Required fields configuration

X

X

N/A

Rev.dbf

Revenue Centers

X

X

1122

Rsn.dbf

Void Reasons

X

X

1123

Rtl.dbf

Routing Levels

X

-

1154

Salesproj.dbf

ALS Sales Projections

X

X

N/A

Salesum.dbf

ALS Sales Summary

X

X

N/A

Scale.dbf

Scales

X

X

1173

Sch.dbf

Schedule

X

X

1124

Schdshft.dbf

ALS Schedule Shift Data

X

X

N/A

Scr.dbf

Screens

X

X

1153

Seclvl.dbf

Security Levels

X

X

N/A

Seclvldt.dbf

Security Level Details

X

X

N/A

Shift.dbf

ALS Shifts

X

X

N/A

ShiftTag.dbf

ALS Shift Tags

X

X

N/A

Smcrd.dbf

Smart Cards

X

X

1164

Smg.dbf

Server Information Messages

X

X

1126

Specreq.dbf

ALS Special Requests

X

X

N/A

Sqlrpt.dbf

SQL Reports

X

X

N/A

Sqlrptpm.dbf

SQL Report Parameters

X

X

N/A

Sto.dbf

Stores

X

X

1166

StrEdit.dbf

CDM Store Edits

X

X

N/A

Strgrp.dbf

CDM Store Groups

X

X

N/A

Strgrpm.dbf

CDM Store Group Members

X

X

N/A

Sub.dbf

Submenus

-

X

1127

Sur.dbf

Surcharges

X

X

1136

Survey.dbf

Surveys

X

X

1191

Tab.dbf

Tables

-

X

1129

Tabdef.dbf

CDM Table Definitions

X

X

N/A

Tare.dbf

Tare Weights

X

X

1174

Task.dbf

ALS Tasks

X

X

N/A

TaskType.dbf

ALS Task Types

X

X

N/A

Tax.dbf

Taxes

X

X

1130

Tdr.dbf

Payment Tenders

X

X

1131

Teamserv.dbf

Team Service Tip Distribution

-

X

N/A

Trdtx.dbf

Tiered Taxes

X

X

N/A

Trk.dbf

Quick Count Tracking Items

X

-

1161

Trm.dbf

Terminals

X

X

1132

Val.dbf

Valid Tender Identifiers

X

X

1133

Vdv.dbf

Remote Display Devices

X

X

1192

Ver.dbf

Database Version Number

X

X

N/A

Vgp.dbf

Remote Display Groups

X

X

1143

Vid.dbf

Remote Displays

X

X

1138

Vkp.dbf

Remote Display Keypads

X

X

1193

Vol.dbf

Volume Levels

X

-

1156

Vqu.dbf

Remote Display Queues

X

X

1194

Workpol.dbf

Work Policies

X

X

1301

Zap.dbf

Termination Reasons

X

X

1137

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1030 Grind Database Contents

AKBID1081 Summary Process and Errors

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1042

�

Expediter Printing

Expediter Printing

============================================================================

AKBID1043

Created: 25 February 2000

Updated: 19 February 2003

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: Expediter Printing Options

============================================================================

Summary

The ALOHA^� application software supports Expediter (Expo) printers in order to assist the kitchen staff in coordinating orders.� This document explains the use of an expo printer, the types of expo printing supported by the Aloha application software, and how to configure them.

Information

The expo printer is a remote chit printer used in the kitchen's production area to provide a synopsis of the entire order and aid the coordination of the kitchen.� The Expediter person usually mans it.

The expediter has multiple roles in preparation of orders sent to the respective tables.� Those roles include quality control (temperature, appearance, and so on), assuring the items are 'plated' correctly (vegetables, sauces, garnishes, and so on), assuring that plates are organized and 'trayed' correctly for an efficient delivery to the table, and assisting in the overall coordination of the kitchen.

�

The expo printer is a tool to display for the expediter a snapshot of the entire order, communicate information, and verification the items are properly prepared for delivery

There are two common types of expo printing supported by the Aloha application software:

Multiple Printer Mode � The entire order prints at the expo printer if an item or items are routed to multiple kitchen printers.

�

Inclusive Printer Mode � all items sent to a kitchen printer also print to an expo printer.

Some options are not available in all versions of the Aloha application software.

Multiple-Printer Mode

In this environment, the entire order prints at the expo printer only if an item or items are routed to multiple kitchen printers.� If all items are routed to a single printer, an expo chit does not print.

Define an expo printer in the Aloha application software by performing one of the following steps based on the version number:

1.        In versions 4.4x and lower, open Maintenance.� Select Options/Print/Chit Print, and set the expo printer in the Expediter drop-down menu.

2.        In versions 5.0x through 5.2.6.x, open Aloha Manager.� Select Maintenance/Store Settings/Printing/Chit Style, and set the expo printer in the Expediter drop-down menu.

3.        In versions 5.2.7.x and higher, open Aloha Manager.� Select Maintenance/Store Settings/Printing-Chits/Chit Style, and set the expo printer in the Expediter drop-down menu.

Enable the 'In Kitchen' option for all kitchen printers (including the expo printer) by performing one of the following steps based on the version number:

1.        In versions 4.4x and lower, open Maintenance.� Select System/Printers, and select 'In Kitchen' for each kitchen printer.

2.        In versions 5.0x and higher, open Aloha Manager.� Select Maintenance/Hardware/Printers/Options, and select 'In Kitchen' for each kitchen printer.

Inclusive Printer Mode

In this environment, all items sent to a kitchen printer also print to an expo printer.� This is done one of two ways depending on the Aloha application software version.

In versions prior to 4.218 and lower, add the expo printer to all kitchen Printer Groups.� Any item routed to a kitchen printer group will also print a chit on the expo printer as well as the specified kitchen printers.

In versions 4.219 and higher, enable expo printing by performing on of the following steps based on the version number:

1.        In versions 4.4x and lower, open Maintenance.� Select Options/Print/Chit Print, and set the printer in the Expediter field.� Check the 'Expedite for 1 printer' option.

2.        In versions 5.0x through 5.2.6.x, open Aloha Manager.� Select Maintenance/Store Settings/Printing/Chit Style, and set the printer in the Expediter field.� Check the 'Expedite for 1 printer' option.

3.        In versions 5.2.7.x and higher, open Aloha Manager.� Select Maintenance/Store Settings/Printing-Chits/Chit Style, and set the printer in the Expediter field.� Check the 'Expedite for 1 printer' option.

You must define the kitchen printers (including the expo printer) by checking the 'In Kitchen' option.� Perform one of the following steps based on the version number:

1.        In version 4.4x and lower, open Maintenance.� Select System/Printers, and check the 'In Kitchen' option for each kitchen printer.

2.        In version 5.0x and higher, open Aloha Manager.� Select Maintenance/Hardware/Printers/Options, and check the 'In Kitchen' option for each kitchen printer.

Extended Information

Order Mode Expo Reroute

You can reroute the expo printer by the order mode.� This option applies to expo printing based on the Expeditor Printing feature, not expo printing performed by adding an expo printer to each printer group.� The new expo printer must have the 'In Kitchen' option checked.� Perform one of the following two steps based on the version number:

1.        In versions 4.4x and lower, open Maintenance.� Select Menu, and select Order Modes.� Set the expo printer for the order mode to use.

2.        In versions 5.0x and higher, open Aloha Manager.� Select Maintenance/System/Order Modes/Order Mode Info, and set the expo printer for the order mode to use.

Print Delivery Information on Expo Chit

To print delivery or customer information on the expo chit, add the line (if it does not already exist) PRINTDELIVERYONEXPEDITER=TRUE to the ALOHA.INI file in the NEWDATA folder, and refresh the system.� The information is the same delivery or customer information that prints on the guest check.

Print Barcode on Expo Chit

To print a barcode on the expo chit, add the line (if it does not already exist) PRINTBARCODEONEXPEDITER=TRUE to the ALOHA.INI file in the NEWDATA folder, and refresh the system.� The must define a thermal printer as the printer type in the Aloha application software in order to print barcodes on expo chits.� You can also use the OPOS printer type provided that the printer is a thermal printer.

Caveats

No Information.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1043 expoditer

�

Tray Chit Printer

Tray Chit Printer

============================================================================

AKBID1044

Created: 1 March 2000

Updated: 9 January 2003

Reviewed: 28 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.5x � 5.3.x

Subject: Using the Aloha Application Software Tray Chit Printer Option

============================================================================

Summary

The 'Tray Chit Printer' setting in the ALOHA^� application software requires a Pivot Seating environment.� (Refer to the Aloha TableService User Manual for more information on Pivot Seating.)� The tray chit is designed to increase customer service by providing the kitchen a list of the order's contents, and the seat number to which each item belongs.� This information enables the site to deliver complete orders to the table without having to 'auction off' the food.� This document explains how to enable and configure tray chits in the Aloha application software.

Information

To enable a tray chit printer, perform the following:

In versions 4.4x and lower, open Maintenance.� Select Options/Print/Chit Print, and select 'Tray Chit Printing'.� Set the printer in the 'Printer' text box.

In versions 5.0x through 5.2.6.x, open Aloha Manager.� Select Maintenance/Store Settings/Printing, and select the Chit Style subtab.� Select 'Tray Chit Printing'.� Set the printer in the 'Printer' text box.

In versions 5.2.7.x and higher, open Aloha Manager.� Select Maintenance/Store Settings/Printing-Chits, and select the Other Chits subtab.� Select 'Print Tray Chits'.� Set the printer in the 'Tray Chit Printer' text box.

Exclusion Category

Any item routed to a remote or kitchen printer prints at the tray chit printer.� This includes bar drinks.�

Items on a check that are not routed to a remote or kitchen printer print at the tray chit printer if any other item ordered at the same time is routed to a remote or kitchen printer.�

Items are excluded from printing on the tray chit printer with an exclusion category.� Create a non-sales category to contain these items.� Label the non-sales category 'No T-Chit', and add the excluded items to the category.� To define the exclusion category, perform one the following:

In versions 4.4x and lower, open Maintenance.� Select Options/Print/Chit Print, and select 'Exclude Category'.� Set the exclusion category in the 'Category' text box.

In versions 5.0x through 5.2.6.x, open Aloha Manager.� Select Maintenance/Store Settings/Printing, and select the Chit Style subtab.� Select 'Exclude Category'.� Set the exclusion category in the Category text box.

In versions 5.2.7.x and higher, open Aloha Manager.� Select Maintenance/Store Settings/Printing-Chits, and select the Other Chits subtab.� Select 'Exclude specific category'.� Set the exclusion category in the Exclude Category text box.

Extended Information

No information.

Caveats

Any item routed to a remote or kitchen printer prints at the tray chit printer.� This includes bar drinks.�

Items on a check that are not routed to a remote or kitchen printer print at the tray chit printer if any other item ordered at the same time is routed to a remote or kitchen printer.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1044

Saved Credit Card Information

Saved Credit Card Information

============================================================================

AKBID1045

Created: 25 February 2000

Updated: 5 October 2001

Reviewed: 17 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.8x � 5.3.x

Subject: Saved Credit Card Information for Bartenders

============================================================================

Summary

The ALOHA^� application software enables bartenders to swipe a customer's credit card to name a new tab, and save the credit card information.� The bartender can use the saved credit card information later when closing the check.� This enables a restaurant to keep the credit card number for bar tabs without the liability of holding the physical card or pre-authorizing the credit card.� Refer to document AKBID1029 for more information on credit card pre-authorization.

Information

The 'Saved Card' feature is only available for job codes with the 'Bartender' setting enabled.� Refer to document AKBID1053 for more information on job codes.

The credit card information is saved if the credit card is swiped while on the Order Entry screen or Working with Tabs screen.� If any items have been applied to the check, they are ordered when the credit card is swiped unless Auto Ordering is disabled.� See the Aloha POS TableService Manual for more information on disabling Auto Ordering.

The saved credit card information is applied as a payment when the Saved Card button is chosen on the Tenders screen.

The Saved Card feature does not work directly with the Credit Card Pre-Authorization feature.� If a check is closed to the saved credit card, the Electronic Draft Capture (EDC) transaction is separate from the pre-authorization transaction.

You do not have to enable EDC functionality in order to use the Saved Card feature.

You can only apply credit cards configured in the system as active tenders with the Saved Card feature.

If you are using Aloha application software versions 5.032 and lower, saved credit cards do not follow a transferred check.� If you transfer a check, then you will lose the saved credit card information.� This does not occur in versions 5.033 and higher.

Extended Information

No information.

Caveats

The Saved Card feature does not work directly with the Credit Card Pre-Authorization feature.� If a check it closed to the saved credit card, the Electronic Draft Capture (EDC) transaction is separate from the pre-authorization transaction.

If you are using Aloha application software versions 5.032 and lower, saved credit cards do not follow a transferred check.� If you transfer a check, then you will lose the saved credit card information.� This does not occur in versions 5.033 and higher.

============================================================================

See also:

Aloha TableService User Manual

AKBID1029 Credit Card Pre-Authorization

AKBID1053 Table Service Order Entry Job Code Options

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1045 held hold

style='mso-spacerun:yes'>� 2003

�

Postponing Daily Batch Settlement

Postponing Daily Batch Settlement

============================================================================

AKBID1046

Created: 24 January 2000

Updated: 4 January 2002

Reviewed: 4 February 2004

Microsoft Windows Versions: All

Aloha Products: EDC

Aloha POS Versions: 4.2x � 5.3.x

Subject: Postponing Aloha EDC Daily Batch Settlement

============================================================================

Summary

The ALOHA^� Application Software Electronic Data Capture (EDC) module is designed for settling a business day's credit card transactions before the beginning of the next business day, but a batch file can be used to enable storage and later settlement of credit card transactions from multiple business days.� This document explains how to set up a batch file that transfers the Aloha EDC transaction (TXN) files for a business day to a temporary storage folder for settlement after the next date of business has started.� This will enable the site time to finish any required booking keeping procedures without rushing to settle the credit card batch before the next business day.� For example, a site's bookkeeper will not have time to review and log the previous day's credit card transactions before the site opens early the next morning.� This process will store up to seven different business day's credit card transactions and still enable individual settlement.

Information

Usage

The batch postponement process is accomplished by defining seven like processors in Aloha EDC.� Each processor will use the same account and modem information.� Each night, a batch file will close Aloha EDC and move the EDC TXN files to the next folder in line.� For example, the current EDC TXN files in processor number one will be moved to processor number two.� Processor two's TXN files will be moved to processor number three.� This will continue through processor number seven.�

If this process encounters errors, they will be displayed using a text file and Windows Notepad.� These errors include the seventh processor already containing TXN files or the existence of TXN files after they should have been deleted.

Prepare the System

This document is only valid for users running Aloha EDC with a terminal-based processor (compared to a host-based processor such as Nova) in one of the following environments:

1.       An Aloha EDC/file server using the Microsoft^� Windows NT^�, Windows 2000, Windows XP, or Windows Server 2003 operating system (OS) and Aloha EDC 4.2 or greater is running as a Windows^� service.

2.       An Aloha EDC/file server using the Microsoft Windows NT, Windows 2000, Windows XP, or Windows Server 2003 OS and Aloha EDC 4.2 or greater is not running as a Windows service.

3.       An Aloha EDC/file server using the Microsoft Windows 95, Windows 98 or Windows Millennium Edition (Me) OS and Aloha EDC 4.2 or greater is not running as a Windows service.

To separately store and settle credit card batch files for multiple business days, multiple processors must be created in EDC.� They are created just as the original processor was created and use the same account and modem information.� See the Aloha Credit Card User Manual for more information on creating credit card processors.� A total of seven processors will be needed and they should be numbered consecutively, e.g.� VISANET, VISANET1, VISANET2, and so on.

Download CLOSEAPP.EXE from the Aloha Technologies FTP site. �Refer to document AKBID1012 for more information on Aloha application software utilities and usage.

Create the Batch File

Create a batch file called EDCINCR.BAT in the BIN folder.� Add the following lines.

rem *** Aloha EDC Batch Incrementing File.� ***

rem *** Shut down EDC GUI.� ***

rem *** Adjust the next line to reflect EDC's window title.� ***

CLOSEAPP.EXE /QUIT Aloha EDC

rem *** Shut down EDC service.� ***

rem *** Remove the next line if not using EDC as a service.� ***

NET STOP EDCSVR

rem *** Check for files in VISANET7 and error is necessary.� ***

IF EXISTS %IBERDIR%\EDC\VISANET7\TXN*.* GOTO ERRFULL

rem *** Increment TXN files.� ***

COPY %IBERDIR%\EDC\VISANET6\TXN*.* %IBERDIR%\EDC\VISANET7\*.*

ECHO Y | DEL %IBERDIR%\EDC\VISANET6\TXN*.*

IF EXISTS %IBERDIR\EDC\VISANET6\TXN*.* GOTO ERRDEL

COPY %IBERDIR%\EDC\VISANET5\TXN*.* %IBERDIR%\EDC\VISANET6\*.*

ECHO Y | DEL %IBERDIR%\EDC\VISANET5\TXN*.*

IF EXISTS %IBERDIR\EDC\VISANET5\TXN*.* GOTO ERRDEL

COPY %IBERDIR%\EDC\VISANET4\TXN*.* %IBERDIR%\EDC\VISANET5\*.*

ECHO Y | DEL %IBERDIR%\EDC\VISANET4\TXN*.*

IF EXISTS %IBERDIR\EDC\VISANET4\TXN*.* GOTO ERRDEL

COPY %IBERDIR%\EDC\VISANET3\TXN*.* %IBERDIR%\EDC\VISANET4\*.*

ECHO Y | DEL %IBERDIR%\EDC\VISANET3\TXN*.*

IF EXISTS %IBERDIR\EDC\VISANET3\TXN*.* GOTO ERRDEL

COPY %IBERDIR%\EDC\VISANET2\TXN*.* %IBERDIR%\EDC\VISANET3\*.*

ECHO Y | DEL %IBERDIR%\EDC\VISANET2\TXN*.*

IF EXISTS %IBERDIR\EDC\VISANET2\TXN*.* GOTO ERRDEL

COPY %IBERDIR%\EDC\VISANET\TXN*.* %IBERDIR%\EDC\VISANET2\*.*

rem *** Check for TXN files in VISANET.� ***

IF EXISTS %IBERDIR%\EDC\VISANET\TXN*.* GOTO ERRNO1

rem *** Start EDC service.� ***

rem *** Remove next line if not running EDC as service.� ***

NET START EDCSVR

rem *** Start EDC GUI.� ***

%IBERDIR%\BIN\EDC.EXE

rem *** Everything finished correctly! ***

GOTO END

:ERRFULL

rem *** Create and display ALL VISANET FOLDERS FULL message.� ***

ECHO The Auto EDC Increment batch file > %IBERDIR%\TMP\EDCBAT.TXT

ECHO did not run properly! >> %IBERDIR%\TMP\EDCBAT.TXT

ECHO All seven of the defined >> %IBERDIR%\TMP\EDCBAT.TXT

ECHO processor folders are full.� >> %IBERDIR%\TMP\EDCBAT.TXT

ECHO Please address this immediately! >> %IBERDIR%\TMP\EDCBAT.TXT

NOTEPAD.EXE %IBERDIR%\TMP\EDCBAT.TXT

GOTO END

:ERRDEL

rem *** Create and display ERROR DELETING TXN's message.� ***

ECHO The Auto EDC Increment batch file > %IBERDIR%\TMP\EDCBAT.TXT

ECHO did not run properly! >> %IBERDIR%\TMP\EDCBAT.TXT

ECHO Some TXN files were not >> %IBERDIR%\TMP\EDCBAT.TXT

ECHO moved correctly.� >> %IBERDIR%\TMP\EDCBAT.TXT

ECHO Please address this immediately! >> %IBERDIR%\TMP\EDCBAT.TXT

NOTEPAD.EXE %IBERDIR%\TMP\EDCBAT.TXT

GOTO END

:ERRNO1

rem *** Create and display MAJOR ERROR message.� ***

ECHO The Auto EDC Increment batch file > %IBERDIR%\TMP\EDCBAT.TXT

ECHO encountered a major error! >> %IBERDIR%\TMP\EDCBAT.TXT

ECHO Processor folder #1 still >> %IBERDIR%\TMP\EDCBAT.TXT

ECHO contains TXN files after >> %IBERDIR%\TMP\EDCBAT.TXT

ECHO they should have been removed.� >> %IBERDIR%\TMP\EDCBAT.TXT

ECHO Please address this immediately! >> %IBERDIR%\TMP\EDCBAT.TXT

NOTEPAD.EXE %IBERDIR%\TMP\EDCBAT.TXT

GOTO END

:END

rem *** Done! ***

Edit the Batch File

Remove the NET STOP EDCSVR and NET START EDCSVR lines unless you have configured EDDCSVR.EXE as a service and you are using Windows NT, Windows 2000, or Windows XP.

Edit the CLOSEAPP.EXE line to define the correct Aloha EDC window name.� Refer to document AKBID1012.

�

If you are not using Visanet as your credit card processor, replace all mentions of VISANET in the batch file with the correct processor name.� Use a text file editor with a Find and Replace feature to ensure all mentions are corrected.

Start the Batch File

This batch file should be fired when the location is not open for business.� The Windows Schedule service (refer to document AKBID1047), the Windows Task Scheduler or Winhook (refer to document AKBID1028) can fire the batch file.

Batch Settlement

The batches can be settled any time within 7 days, but if this is done while the site is open, the settlement process may tie up the modem for several minutes and not enable authorizations on the same modem.�

Extended Information

No information.

Caveats

The TXN files contain important information.� Before testing your batch file, please backup your TXN files.

The CLOSEAPP.EXE line in the batch file should be re-tested any time the Aloha EDC software is updated.� Significant problems can occur if CLOSEAPP.EXE fails to shut down Aloha EDC.

============================================================================

See also:

Aloha Credit Card User Manual

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1028 Winhook

AKBID1047 Microsoft Windows Schedule Service

AKBID1104 Automatic Credit Card Settlement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1046 delay second two

Copyright Aloha Technologies, Ltd.�

Microsoft Windows Schedule Service

Microsoft Windows Schedule Service

============================================================================

AKBID1047

Created: 3 February 2000

Updated: 19 December 2001

Reviewed: No longer reviewed

Microsoft Windows Versions: Windows NT, Windows 2000, Windows XP

Aloha Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 3.0x � 5.3.x

Subject: Using the Microsoft Windows NT, Windows 2000, and Windows XP Schedule Service

============================================================================

Summary

The Microsoft^� Windows NT^�, Windows^� 2000, and Windows XP Schedule service enables users to schedule custom processes to take place at desired times and dates.

Information

Create a CMD File

The Schedule service uses command files (.CMD) to initiate the desired task.� Command files are batch files (.BAT) with a different file extension.� Create a command file that performs the desired task and save it in the Windows folder.

Enable the Schedule Service

The Schedule service is not enabled by default.� To enable it, select Start/Settings/Control Panel and select Services.� Locate the Schedule service and double-click it.� Select 'Automatic' and click OK.� Click 'Start' to activate the service immediately.� The service will automatically start each time Windows is started.

Schedule a Task

The Schedule service uses the AT command to access and set up the Schedule service.� The syntax to add a new task is:

AT [\\computername] time [/INTERACTIVE] [/EVERY:date[,�] | /NEXT:date[,�] ] 'command'

The syntax to remove a task is:

AT [\\computername] [ [id] [/DELETE] | /DELETE [/YES] ]

\\computername: Specifies a remote computer in which to run the task.� The local computer is assumed if this is not specified.

id: Specifies the task�s assigned ID.

/DELETE: Deletes the specified task ID.� If an ID is not defined, all tasks are removed.

/YES: Passes a positive confirmation to all prompts when deleting a task.

time: Designates the time to run the task.�

/INTERACTIVE: Enables the task to interact with the desktop of the logged on user.

/EVERY:date[,�]:Specifies the day or month in which to run the task.� The current date of each month is used if this is not specified.

/NEXT:date[,�]: Specifies the next occurrence of the day or month in which to run the task.� The current day of the month is used if this is not specified.

'command': Specifies the name of the command file to run.

To view the current scheduled tasks, type AT from a command line and press <Enter>.

To access command line help text, type AT /? from a command line and press <Enter>.

Examples of AT Command Lines

The following command line runs the FULLBKUP.CMD file at 11:00 p.m. every Monday, Wednesday, and Friday:

AT 23:00 /every:M,W,F FULLBKUP.CMD

The following command line runs the MYARCHIV.CMD file at 4:00 a.m. every day:

AT 4:00 /every:M,T,W,Th,F,S,Su MYARCHIV.CMD

Extended Information

Microsoft supplies a graphical user interface (GUI) for use with the Schedule service.� This application, WINAT.EXE, creates a Windows interface for creating, scheduling, and removing tasks. �The application can be downloaded from the Aloha Technologies FTP site as WINAT.ZIP.� Place WINAT.EXE in the Windows folder and double-click it to open it.

If the Schedule service is used to perform a system backup, use the /INTERACTIVE parameter to display any errors on the desktop.� This will inform the restaurant manager of any problems that the Schedule service encounters with the backup routine.

Caveats

No information.

============================================================================

See also:

AKBID1027 Microsoft Windows NT/Windows 2000 Automatic Backup

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1047

Aloha Hardware and OS Specifications

Aloha Hardware and OS Specifications

============================================================================

AKBID1048

Created: 19 April 2000

Updated: 16 April 2004

Reviewed: 16 April 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

Summary

The ALOHA^� application software is a hardware independent application, but it does require you to use approved hardware, maintain minimum hardware requirements, and use approved operating systems (OS).

'Aloha Certified Hardware' means that the specific model/version of hardware was certified with a specific operating system and a specific version of Aloha application software.� Although Aloha Technologies tries to ensure hardware compatibility with past and future versions of Aloha application software (unless otherwise specified), certification does not guarantee correct functionality in every version of Aloha software.� Aloha Technologies strongly recommends testing all hardware, intended operating systems, and Aloha application software in your specific operating environment and configuration prior to using it in a live environment.

Information

The following hardware has been approved by Aloha Technologies for use with the Aloha application software.

Barcode Scanners

Refer to document AKBID1068.

Make

Model

Notes

Metrologic^�

Serial

NCR

7890

POSIFLEX Business Machines, Inc.

CD-2820

The CD-2820 was certified using a keyboard- interface.

SCANTEAM^�

N/A

Symbol^� Technologies

2000

Caller ID Adaptors

Refer to document AKBID1052

Make

Model

Notes

BEK-TEL, Inc.

PC/4

Supported in versions 5.2x and higher

Rochelle^�

Multi-Line Adapter (MLA), model number 2045

Cash Card Devices

Refer to document AKBID1069

Make

Model

Notes

Debitek

N/A

InterCard^�

N/A

Xico

N/A

Only supported in Aloha application software version 4.0x.

Cash Drawers

Make

Model

Notes

APG Cash Drawer^�

212A

Serial-fired (refer to document AKBID1138)

CBM America/Japan CBM

6E

Printer-fired

MMF

N/A

Printer and Serial-Fired

M-S

SS-103

Printer-fired

OPOS

N/A

Refer to document AKBID1074.

Partner Tech Corp.

CDR-5E415

POSIFLEX Business Machines, Inc.

CR-4100C

The CR-4100C was certified using OPOS drivers via the cash drawer port on a POSIFLEX TP-6000 POS terminal.

Radiant Systems

CD00046 16-inch Printer Driven Cash Drawer

Senor Tech Co., Ltd.

CDB-424253MS

Printer-fired

Coin Changers

Refer to document AKBID1072

Make

Model

Notes

Telequip

TRANSACT

Customer (Pole, Rear) Displays

Make

Model

Notes

CRS, Inc.

IT-8000 2x20 Rear Customer Display

Refer to document AKBID3277

Flytech

Flytech POS600 Customer Display

Refer to document AKBID3276 for more information on configuring the POS600 display.

J2

J2 800 CX Customer Display

Refer to document AKBID3305 for configuration information.

NCR

7402 (RealPOS 70) Line Display, NCR 7462 (7460-2020, RealPOS 62) Line Display

Certified using OPOS drivers.

Partner Tech Corp.

CD-7220

The CD-7220 was certified with OPOS drivers.

POSIFLEX Business Machines, Inc.

PD-302, PD-2500

The PD-302 and PD-2500 were certified using OPOS drivers.� Refer to document AKBID3272 for more information on configuring the PD-2500.

Radiant Systems

P701, P703, P1210 Integrated Customer Display

P701 and P703 were certified using OPOS drivers.� Refer to document AKBID3330 for more information on configuring the P1210 Integrated Customer Display.

Senor Tech Co., Ltd.

R856008AST

Refer to document AKBID3297.

Sharp

UP-120DP

Certified using OPOS drivers.

Ultimate Technology Corporation

PD220XL, PD1100XL, PD2200XL

Refer to document AKBID3063.

OPOS

N/A

Refer to document AKBID1074.

Display Boards

Make

Model

Notes

Texas Digital Systems, Inc.

AccuORDER 360 (LED), AccuVIEW (LCD)

Drink Dispensers

Refer to documents AKBID1041 and AKBID1090.

Make

Model

Notes

Berg Company^�

N/A

Multi-terminal beer taps supported.

Easybar^� Beverage Management Systems

N/A

File Servers

The Aloha application software supports most Microsoft^� Windows^�-based PC's that meet or exceed the minimum requirements listed in the Minimum File Server Requirements section of this document.

Make

Model

Notes

IBM

8480-22x

Radiant Systems

S4021

Magnetic Stripe Readers

Make

Model

Notes

CRS, Inc.

IT-8000 180 Degree 2-track MSR, IT-1000-TM1K-2K 2-track MSR

Flytech

Flytech POS600 MSR

POS600 MSR certified using a keyboard interface. Refer to document AKBID3275 for more information.

ID TECH

MiniMag Compact Magnetic Stripe Reader (keyboard wedge)

Refer to document AKBID3283 for configuration information.

J2

800 CX MSR

Refer to document AKBID3282 for configuration information.

Mag-Tek

Keyboard Wedge

NCR

NCR 7402 (RealPOS 70) Wedge MSR, NCR 7462 (7460-2020, RealPOS 62) Wedge MSR

Certified using OPOS drivers.

Partner Tech Corp.

MR-4330, MSR-1450LM12B

The MR-4330 and MSR-1450LM12B were certified using a keyboard interface.�

PioneerPOS

PioneerPOS PXi MSR

PioneerPOS PXi MSR certified using a keyboard interface.

POSIFLEX Business Machines, Inc.

SD-100, SD-100 USB

The SD-100 and SD-100 USB were certified with a keyboard interface.� SD-100 and SD-100 USB certification do not include the thumbprint scanner or smart card device.

Radiant Systems

P400 MSR, P1210 MSR, P1550 MSR

Senor Tech Co., Ltd.

CR-856A-123

Certified using a keyboard interface.

Sharp

UP-E12MR2

Certified using OPOS drivers.

Uniform Industrial Corporation

N/A

OPOS

N/A

Refer to document AKBID1074.

Modems

Make

Model

Notes

Boca Research

2400

Credit card use only.

GVC

14.4

Credit card use only.

Motorola

Modem Surfer 28.8

Credit card use only.

Practical Peripherals

14.4, 28.8

Credit card and remote support.

3Com/U.S. Robotics, Inc.

Sportster 28.8-56K, Courier 56K

Credit card and remote support, except for the Sportster 56K, which is remote support only.

Network Hubs

The Aloha application software supports most standard Ethernet 10/100-base-T hubs.

Network Interface Cards

The Aloha application software supports most standard Ethernet 10/100-base-T network-interface-cards (NICs).

Pen Readers

Make

Model

Notes

WMF

N/A

Pen (writing) based login devices in Europe. Refer to document AKBID3156.

Point-of-Sale Terminals

Make

Model

Notes

Casio^�

QT-7000

Customer display not certified.

Comtrex Systems Corporation

iTP-1143H

Customer display and cash drawer port not certified.

CRS, Inc.

IT-1000, IT-2000, IT-8000

IT-1000 certification includes MSR.� IT-8000 certification includes MSR and customer display.

DigiCom International, Inc.

iPOS430, Sonic-I B63

Earth LCD

Panel PC (PPC-Rev A)

Flytech

POS500, POS600

POS600 certification includes P0730601 customer display and P1-505-55-0NN MSR.

IBM

4695 2xx, 4695 3xx, SurePOS 300, SurePOS 500

Models with Cyrix processor not certified. Refer to AKBID1032 (4695) and AKBID1172 (SurePOS). SurePOS requires Aloha version 5.026 or higher.

Jaguar

N/A

Certified with Ultimate Technology Corporation customer display.

Javelin Systems Inc.

LC, LCP, LP, Viper, Wedge

J2

800 CX

800 CX certification also includes the customer display and MSR.

Liberty

CPU Units, Sahara PC

Merrimac

Fusion

Mintronix

Dynova 5000, Touch 5000

Certified with Ultimate Technology Corporation customer display.

NCR

7402 (RealPOS 70), 7453-2012, 7454, 7460, NCR 7462 (7460-2020, RealPOS 62)

Panasonic^�

9000 Workstation

Calibration requires a keyboard.

PAR^�

POS4

OPOS KVS not certified. Refer to document AKBID1033.

Partner Tech Corp.

PT-3000, PT-4000i/4100i, PT-9000

PT-4000i/4100i includes CD-7220 customer display (OPOS) and MR-4330 MSR.� PT-9000 includes MSR-1450LM12B MSR and CD-7220 customer display (OPOS).

PioneerPOS

PioneerPOS PXi

PioneerPOS PXi includes keyboard-based MSR.

POSIFLEX Business Machines, Inc.

TP-6000, Jiva EL TP-5800

TP-6000 and Jiva EL TP-5800 certification includes SD-100 MSR (keyboard), PD-302 and PD-2500 customer displays (OPOS), CR-4100C cash drawer (OPOS), and CD-2820 barcode scanner.� TP-6000 and Jiva EL TP-5800 certification does not include the thumbprint scanner or smart card device.

Radiant Systems

P400, P1210, P1550, S4021

P400 certification includes P400 MSR and P701 customer display.� P1210 certification includes P1210 MSR and P1210 customer display.� P1550 certification includes P1550 MSR and P703 customer display.

Senor Tech Co., Ltd.

ROBOT POS PLUS

Sharp

UP-5900

UP-5900 certification includes the UP-E12MR2 MSR (OPOS) and UP-120DP customer display (OPOS).

Ultimate Technology Corporation (UTC)

Q1501, Q1503, UltimaTouch F5x00

Uptime

Wedge POS

Wincor Nixdorf

BEETLE /iPOS

Printers

Refer to document AKBID1002

Make

Model

Notes

Axiohm

A794

Serial

CBM America/Japan CBM

CBM-710-40/720-40/730-40/750-40 (version 4.4 and higher), CBM-1000 Type II, iDP3240

CBM-1000 Type II and iDP3240 are serial only.� CBM-1000 Type II and iDP3240 require OPOS 1.6.001 or higher, or you can use Epson emulation.

Epson

TM-295, TM-H6000, TM-T80/85/88, TM-U300, TM-U200, TM-U220, TM-U950

Parallel and serial. TM-U950 slip printing and check MICR reading are not supported.� TM-H6000 and TM-295 'line find' is not supported in versions 5.0x and lower.� TM-H6000 slip printer is not supported in QuickService.� TM-U220 is only supported with a serial interface.

IBM

SureMark 4610

Requires Aloha version 5.026 or higher and IBM OPOS version 1.5.0 or higher.� If you are using IBM OPOS 1.4.4, the patch included in 1.5.0 is available from Aloha Technologies.

Ithaca (TransAct)

82 Plus, iTherm 280, POSjet 1000, Series 1000

82 Plus is certified in both serial and parallel.� iTherm 280, POSjet 1000, and Series 1000 only certified with serial interface.

Nanoptix, Inc.

C21-BNSAB/C21-BNSBB �Spill Proof Thermal Printer

NCR

7193, 7194, 7197

The 7193 is certified for RS232 and RS485.� The 7197 is certified in Aloha versions 5.2.5.x and higher.� We only support the 7197 using OPOS drivers.

Olivetti

OST12

Serial

Partner Tech Corp.

RP-200

Serial

POSIFLEX Business Machines, Inc.

POSIFLEX PP7000S103

Certified with OPOS drivers

Samsung

SRP-270C, SRP-350, SRP-500C

SRP-270C was tested only with a serial interface using Epson TM-U200 emulation.� SRP-350 was tested only with a serial interface using Epson TM-T80 emulation.� SRP500C was certified with both serial and parallel interfaces using Epson TM-U200 emulation.

Star Micronics

DP8340, SP300, SP312, SP342, SP512MD, SP2000, TSP400, TSP600, TSP700, TSP800

Serial, SP300, TSP600, TSP700, TSP800 both parallel and serial.� We only support the TSP600, TSP700 and TSP800 using OPOS and Windows-based drivers.� The TSP400 is a label printer.

OPOS

N/A

Refer to document AKBID1074.

Zebra Technologies/Eltron^�

TLP2642

Label printer.

Remote Display Systems

Make

Model

Notes

IBM^�

IBM Kitchen System

Refer to document AKBID1137.

Logic Controls, Inc.

Logic Net^� Kitchen Display System

Serial only.� Refer to document AKBID1229.

Progressive Systems

CVM3

Refer to document AKBID3168.

QSR^� Automations

RDS-2000, epic, KDS

Refer to document AKBID1115 and document AKBID1217.

Select Electronics

SV1000, SV2000, Oasys

Refer to document AKBID1122.

Scales

Make

Model

Notes

NCI

6702, 6710, 6720

METTLER TOLEDO

8217

Serial Expansion Devices

Make

Model

Notes

Equinox

ESP-8 10/100 Serial Hub, SST-8P UNIV

ESP-8 10/100 is an 8-port RS232 ethernet serial device server.� SST-8P UNIV is an 8-port RS232 PCI board.� Refer to documents AKBID3263 and AKBID3269.

Inside Out Networks

Edgeport/4

Edgeport/4 is a USB to 4-port RS232 device.

Quatech, Inc.

QSCLP-100, QSE-100D, QSU-100

QSCLP-100 is a 4-port RS232 PCI board.� QSE-100D is a 4-port RS232 ethernet serial device server.� QSU-100 is a USB to 4-port RS232 device.

Systech

RCS-3284

RCS-3284 is a 4-port RS232 ethernet serial device server.

Thumbprint Scanners

Make

Model

Notes

Veridicom

5^th Sense Parallel, 5^th Sense USB

Refer to document AKBID1215 to avoid HASP^� security key conflicts.

Touch Screen Monitors

Make

Model

Notes

Caltron Industries, Inc.

12� flat panel

Earth LCD

XLM-78ST

Elo TouchSystems

N/A

3M Touch Systems/MicroTouch^�

M150 FPD Touch Monitor (Serial), M150 FPD Touch Monitor (USB)

Liberty

N/A

KEYTEC, Inc.^�

Magic Touch^� add-on touch screen kit.

Preh

12� Touch Commander

TEKVisions

N/A

UPS and Power Conditioners

Uninterruptible Power Supplies (UPS) do not always condition power as well as protect against power loss.

Make

Model

Notes

EnergyUPS

EUPS250 Power Conditioned Online Uninterruptible Power Supply, EUPS400 Power Conditioned Online Uninterruptible Power Supply

Smart Power Systems

Econo Pro+ TBF^� EP625 Uninterruptible Power Supply, Smart TBF15PC Digital Power Conditioner, BAK500AVRTBF Uninterruptible Power Supply

Video Security Systems

Make

Model

Notes

Transaction Verification Systems, Inc. (TVS)

TVC-1066A, TVC-1068A, TVC-1090

Also known as AlohaSpy.

Wireless Networking

Make

Model

Notes

BreezeCOM^�

AP-10 (Access Point), SA-10 (Station Adapter), SA-PCR (PCMCIA Station Adapter).

Range may be limited by environmental variables.

File Server Hardware Requirements

Hardware requirements must meet or exceed the operating system's recommended requirements.� Add additional memory and increase the processor speed to compensate for heavy use, third-party software, and usage unrelated to the Aloha application software.

Resource

Non-SuperSite

SuperSite

Comments

Database Software

None (.DBF files)

Microsoft SQL Server 2000

Hard Drive

EIDE, 20 gigabyte

Ultra3 SCSI or Serial ATA, 40 gigabytes, RAID 5

The Aloha application software uses less than 100 megabytes when initially installed but requires approximately three megabytes per historical day.

Memory

128 megabytes

1 Gigabyte

Network Card

10-base-T

10/100-base-T

Parallel or USB Port

Yes

Yes

Required for HASP security key

Processor

500 MHz

2 GHz

Video Adapter

16 bit colors

16 bit colors

Order-entry Terminal Requirements

This does not include peripherals such as receipt printers, magnetic stripe readers, customer displays, and so on.

Hardware requirements must meet or exceed the operating system's recommended requirements.� Add additional memory and increase the processor speed to compensate for heavy use, third-party software, and usage unrelated to the Aloha application software.

Resource

Non-SuperSite

SuperSite

Comments

Hard Drive

IDE, 2 gigabytes

IDE, 4 gigabytes

The Aloha application software uses less than 50 megabytes, but SuperSites require approximately two megabytes per historical day.

Memory

64 megabytes

64 megabytes

Network Card

10-base-T

10-base-T

Processor

350 MHz

350 MHz

Video Adapter

16 bit color

16 bit color

Recommended Stand-alone EDC, PMS or BackOffice File Server Hardware Requirements

The use of stand-alone EDC, PMS and BackOffice file servers are generally limited to SuperSites to lessen the burden on the SuperSite file server and increase fault tolerance, but you can use them at any site.

Hardware requirements must meet or exceed the operating system's recommended requirements.� Add additional memory and increase the processor speed to compensate for heavy use, third-party software, and usage unrelated to the Aloha application software.

Resource

Recommended

Comments

Hard Drive

EIDE, 10 gigabyte

Memory

128 megabytes

Network Card

10/100-base-T

Processor

Pentium-class 500 MHz

File Server Operating Systems

Not all operating systems are certified with all components of the Aloha application software.� Please contact the Aloha Customer-Service-Center (CSC) at (817) 25-ALOHA (252-5642) for more information on specific compatibility.

If you are using Windows NT, Windows 2000, Windows XP, or Windows Server 2003 in a standard site, the Aloha application software file server requires a Windows Client-Access-License (CAL) for EDC.EXE (EDC) and each Front-of-House (FOH) terminal.� Remote instances of ALOHAMGR.EXE (Aloha Manager) also consume a CAL.� Additional third-party software might also consume a CAL.

If you are using Windows NT, Windows 2000, Windows XP, or Windows Server 2003 in a SuperSite, the Aloha application software SuperSite file server requires a Windows CAL for EDC and each SuperSite store.� Even if EDC is on a stand-alone file server, the SuperSite file server still requires a CAL for EDC since the EDC file server will connect to the SuperSite file server on a regular basis to update the local configuration files.� Remote instances of Aloha Manager also consume a CAL.� Additional third-party software might also consume a CAL.

At the time of this writing, Aloha Technologies has not certified Windows Server 2003 for use on SuperSite file servers.

Windows 95, Windows 98, and Windows Millennium Edition (Me) do not use CALs, so only the system resources limit the number of terminals.

The following recommendations apply to a standard site (not a SuperSite), they are based on a system without any remote instances of Aloha Manager or third-party software, and they leave one CAL available as a safeguard to account for Windows ambiguous treatment of CALs:

At the time of this writing, Aloha Technologies has not certified Windows Me.

Windows Me and Windows 2000 require Aloha application software versions 5.017 or higher.� Windows XP requires Aloha application software versions 5.211 or higher.� Windows Server 2003 requires Aloha application software versions 5.2.7.105 and higher.

Operating System

Recommended maximum number of FOH terminals if not using EDC

Recommended maximum number of FOH terminals if using EDC

Windows 95

2 (limited by system resources)

2 (limited by system resources)

Windows 98

2 (limited by system resources)

2 (limited by system resources)

Windows Me

2 (limited by system resources)

2 (limited by system resources)

Windows NT 4.0 Workstation (requires Service Pack 4 or higher)

9 (limited by hard-coded operating system licensing)

8 (limited by hard-coded operating system licensing)

Windows NT 4.0 Server (requires Service Pack 4 or higher)

Limited by the number of CALs purchased

Limited by the number of CALs purchased

Windows 2000 Professional (requires Service Pack 2 or higher)

9 (limited by hard-coded operating system licensing)

8 (limited by hard-coded operating system licensing)

Windows 2000 Server (requires Service Pack 2 or higher)

Limited by the number of CALs purchased

Limited by the number of CALs purchased

Windows XP Home Edition

4 (limited by hard-coded operating system licensing)

3 (limited by hard-coded operating system licensing)

Windows XP Professional

9 (limited by hard-coded operating system licensing)

8 (limited by hard-coded operating system licensing)

Windows Server 2003

Limited by the number of CALs purchased

Limited by the number of CALs purchased

Order-entry Terminal Operating Systems

Not all operating systems are certified with all components of the Aloha application software.� Please contact the Aloha Customer-Service-Center (CSC) at (817) 25-ALOHA (252-5642) for more information on specific compatibility.

If you are using Windows NT, Windows 2000, Windows XP, or Windows Server 2003 in a standard site, the Aloha application software requires a separate CAL for each FOH terminal, plus an additional CAL is required if you are using a stand-alone EDC file server rather than using the Aloha application software file server to process EDC or PMS transactions.�

If you are using Windows NT, Windows 2000, Windows XP, or Windows Server 2003 in a SuperSite, the Aloha application software requires a CAL for each terminal within the same store, an additional CAL is required for the SuperSite file server to connect to the terminal, a stand-alone EDC file server requires an additional CAL, as does any terminal from a separate store that is printing to a local Windows-based printer.� Additional third-party software can also consume a CAL.

Windows 95, Windows 98, and Windows Millennium Edition (Me) do not use CALs, so only the system resources limit the number of terminals.� Although Windows 95, Windows 98, and Windows Me theoretically have the resources to handle 50 FOH terminals, you should consider other factors before selling a flat site (rather than a SuperSite) of this size, such as manageability and refreshing the system.� Sites with more than 30 terminals should consider using Aloha's SuperSite architecture to increase the manageability and reliability.

The following recommendations are based on a system without any additional third-party software, not using a stand-alone EDC file server, and they leave one CAL available as a safeguard to account for Windows ambiguous treatment of CALs:

At the time of this writing Aloha Technologies has not certified Windows Me.

Windows Me and Windows 2000 require Aloha application software versions 5.017 or higher.� Windows XP requires Aloha application software versions 5.211 or higher.� Windows Server 2003 requires Aloha application software versions 5.2.7.105 and higher.

Operating System

Recommended maximum number of FOH terminals in a standard site

Windows 95

50 (limited by system resources)

Windows 98

50 (limited by system resources)

Windows Me

50 (limited by system resources)

Windows NT 4.0 Workstation (requires Service Pack 4 or higher)

9 (limited by hard-coded operating system licensing)

Windows NT 4.0 Server (requires Service Pack 4 or higher)

Limited by the number of CALs purchased

Windows 2000 Professional (requires Service Pack 2 or higher)

9 (limited by hard-coded operating system licensing)

Windows 2000 Server (requires Service Pack 2 or higher)

Limited by the number of CALs purchased

Windows XP Home Edition

4 (limited by hard-coded operating system licensing)

Windows XP Professional/Windows XP Embedded (XPe)

9 (limited by hard-coded operating system licensing)

Windows Server 2003

Limited by the number of CALs purchased

Extended Information

No information.

Caveats

'Aloha Certified Hardware' means that the specific model/version of hardware was certified with a specific operating system and a specific version of Aloha application software.� Although Aloha Technologies tries to ensure hardware compatibility with past and future versions of Aloha application software (unless otherwise specified), certification does not guarantee correct functionality in every version of Aloha software.� Aloha Technologies strongly recommends testing all hardware, intended operating systems, and Aloha application software in your specific operating environment and configuration prior to using it in a live environment.

File server and order-entry terminal hardware requirements must meet or exceed the operating system's recommended requirements.� Add additional memory and increase the processor speed to compensate for heavy use, third-party software and usage unrelated to the Aloha application software.

Not all operating systems are certified with all components of the Aloha application software.� Please contact the Aloha Customer-Service-Center (CSC) at (817) 25-ALOHA (252-5642) for more information on specific compatibility.

Windows Me and Windows 2000 require Aloha application software versions 5.017 or higher.� Windows XP requires Aloha application software versions 5.211 or higher.� Windows Server 2003 requires Aloha application software versions 5.2.7.105 and higher.

============================================================================

See also:

Aloha POS User Manual

AKBID1002 Aloha Receipt and Kitchen Printer Settings

AKBID1032 IBM 4695 POS Terminal

AKBID1033 PAR POS 4 POS Terminal

AKBID1041 Multi-Terminal Berg Tap Setup

AKBID1052 Caller ID

AKBID1068 Barcodes and Scanners

AKBID1069 Cash Card Device Troubleshooting

AKBID1072 Electronic Coin Dispensers

AKBID1074 OPOS

AKBID1090 Drink Dispensers

AKBID1115 QSR Automations Ethernet Video

AKBID1122 Select Electronics Video

AKBID1137 IBM Kitchen System

AKBID1138 APG Cash Drawer Model 212A

AKBID1172 Configuring the IBM SurePOS 300 and SurePOS 500

AKBID1215 Configuring Veridicom Thumbprint Scanners

AKBID1217 Configuring QSR Automations KDS

AKBID1229 Logic Controls Logic Net Kitchen Display System (Serial)

AKBID3063 Ultimate Technology Corporation Customer Display Settings

AKBID3156 WMF Pen Reader Pin-outs

AKBID3168 Progressive Systems CVM Pin-outs

AKBID3263 Equinox ESP 10/100 Serial Hub Printer Cable Pin-outs

AKBID3269 Equinox SST-8P Serial I/O Adaptor Printer Cable Pin-outs

AKBID3272 Configuring POSIFLEX PD-2500 Customer Display

AKBID3275 Configuring the Flytech POS600 MSR for Use with Aloha

AKBID3276 Configuring the Flytech POS600 Customer Display

AKBID3277 Configuring the CRS IT-8000 2X20 Rear Customer Display

AKBID3282 Configuring the J2 800 CX MSR for Use with Aloha

AKBID3283 Configuring the ID TECH MiniMag Compact MSR for Aloha

AKBID3297 Senor Tech Co., Ltd. R856008AST Customer Display

AKBID3305 Configuring the J2 800 CX Customer Display for Use with Aloha

AKBID3329 Configuring the Radiant Systems P1210 Integrated MSR

AKBID3330 Configuring the Radiant P1210 Integrated Customer Display

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1048 1550 f5000 f5500 certification equipment finger fingerprint line partnertech restriction rs-232 scale senortech spy tech thumb

Install DCOM in Windows

Install DCOM in Windows

============================================================================

AKBID1049

Created: 13 March 2000

Updated: 15 April 2002

Reviewed: 30 January 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 4.2x � 5.3.x

Subject: Installing DCOM in Windows

============================================================================

Summary

The ALOHA^� application software requires installation of the Distributed Component Object Model (DCOM) for some Back-of-House (BOH) components to function properly in versions 4.2s and higher.� DCOM is not supplied with Microsoft^�Windows^� 95, so the Aloha application software setup application (SETUPPOS.EXE) installs and configures DCOM when the Windows 95 operating system (OS) is present on the file server.� DCOM is automatically included in Windows 98and Windows Millennium Edition (Me), but it might require manual configuration.� DCOM is automatically included in Windows NT, Windows 2000, Windows XP, and Windows Server 2003.� DCOM is also required to run some Aloha software applications as clients on remote computers.

Information

Windows 95 Automatic Installation and Configuration

If the Aloha application software versions 4.2x or higher have never been installed on the file server, SETUPPOS.EXE automatically installs and configures DCOM during the Aloha application software installation.� There are no other requirements.

If versions 4.2x (or higher) has been previously installed on the file server using SETUPPOS.EXE and you need to force SETUPPOS.EXE to reinstall DCOM, perform the following:

The incorrect use of the Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_CLASSES_ROOT\CLSID\{bdc67890-4fc0-11d0-a805-00aa006d2ea4}\InstalledVersion.

3.        Delete the InstalledVersion key.�

4.        Select Registry/Exit to exit the Windows Registry Editor.

5.        Run SETUPPOS.EXE /ADVANCED from the Aloha Application Software Installation CD.

Windows 95 Manual Installation and Configuration

Remote use of some BOH applications requires the manual addition of DCOM to the remote computer since SETUPPOS.EXE is not used.� You can also manually installation DCOM on the file server if using SETUPPOS.EXE is not an option.�

Manual DCOM installation requires two executables: DCOM95.EXE and DCM95CFG.EXE.� Both executables are included on the Aloha Installation CD in the \MISC\DCOM95 folder as DCOM95.EXE and DCM95CFG.EXE.

Perform the following to install and configure DCOM:

1.        Run DCOM95.EXE, and restart Windows when the installation is complete.

2.        Run DCM95CFG.EXE, and restart Windows when the installation is complete.

3.        Run DCOMCFNG.EXE from the Windows SYSTEM folder, select 'Enable Distributed COM on this computer' under the Default Properties tab, and select 'Enable Remote Connection' under the Default Security tab.

4.        Click OK and restart Windows.

Windows 98 and Windows Me Manual Configuration

Perform the following to manually configure DCOM in Windows 98 or Windows Me:

1.        Run DCOMCNFG.EXE from the Windows SYSTEM folder.� Select 'Enable Distributed COM on this computer' under the Default Properties tab, and select 'Enable Remote Connection' under the Default Security tab.

2.        Click OK and restart Windows.

If DCOMCNFG.EXE is not installed on the PC, install DCOMCNFG.EXE by running DCM95CFG.EXE from the Aloha Installation CD.

Extended Information

DCOM uses the following permission types:

-          Access permissions control user access to an application after it has been started.� Any user who does not have administrative rights and will be remotely accessing the application must have access permission.

-          Launch permissions control user access to launch or start an application.� Any user who does not have administrative rights and will be remotely starting the application must have launch permission.

-          Change permissions control user access to modify the application's DCOM configuration.� Any user who does not have administrative rights and will be modifying the application's DCOM configuration must have change permission.� Change permission should be limited to users who will be supporting the application.

Caveats

The incorrect use of the Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1049

Remote Aloha EDC

Remote Aloha EDC

============================================================================

AKBID1050

Created: 1 February 2000

Updated: 28 January 2002

Reviewed: 4 February 2004

Microsoft Windows Versions: All

Aloha Products: EDC

Aloha POS Versions: 4.2x � 5.3.x

Subject: Creating and Using Remote Copies of EDC

============================================================================

Summary

The ALOHA^� application software Electronic Draft Capture (EDC) application can be setup to access the EDC file server from a remote computer.� This is helpful in restaurants where multiple people need to access EDC from different offices.

Information

Network

Establish a TCP/IP-based network connection between the remote EDC client and EDC file server.� Other network protocols may be used in conjunction with TCP/IP, but TCP/IP must be included.� Refer to document AKBID1063 for more information on TCP/IP.

Establish network file access between the remote EDC client and the BOOTDRV share on the EDC file server.

Remote EDC must use a TCP/IP connection.

Install DCOM

Distributed Component Object Model (DCOM) must be installed and configured on the EDC file server and the remote EDC client.�

EDC file servers using Microsoft^� Windows^� 98 and Windows Millennium Edition (Me) may require the manual configuration of DCOM, even with the Aloha application software already installed on it.

Refer to document AKBID1049 for more information about installing and configuring DCOM.

Register EDCSVRPS.DLL

If the remote EDC client is using the Windows NT^�, Windows 2000, Windows XP, or Windows Server 2003 operating system (OS), open a command prompt on the remote EDC client and navigate to the Windows SYSTEM32 folder.� Type the following command line to register the copy of EDCSVRPS.DLL from the EDC file server on the remote EDC client (a successful confirmation should follow the registration):

REGSVR32.EXE \\ALOHABOH\BOOTDRV\ALOHA\BIN\EDCSVRPS.DLL

If the remote EDC client is using the Windows 95, Windows 98, or the Windows Me OS, open a command prompt on the remote EDC client and navigate to the Windows SYSTEM folder.� Type the following command line to register the copy of EDCSVRPS.DLL from the EDC file server on the remote EDC client (a successful confirmation should follow the registration):

REGSVR32.EXE \\ALOHABOH\BOOTDRV\ALOHA\BIN\EDCSVRPS.DLL

The EDCSVRPS.DLL needs to be re-registered on the remote EDC client each time the Aloha Application Software is upgraded to a newer version.

Copy Windows NT, Windows 2000, Windows XP, Windows Server 2003 System Files (4.4x and higher)

This step is required if the remote computer is using the Windows NT, Windows 2000, Windows XP, or Windows Server 2003 operating system.

EDC requires system files in the Windows SYSTEM32 folder on the remote computer, but since current copies of the files may be in use by Windows, you cannot copy the new versions to the SYSTEM32 folder.

To alleviate this problem, download SETUPSYS.EXE from the Aloha Technologies FTP site as SETUPSYS.ZIP (refer to document AKBID1012) or use the copy of SETUPSYS.EXE from the \MISC\SETUPSYS folder on the Aloha Installation CD.

Extract the system files from WNTDLL.ZIP and WNTDLL2.ZIP in the ALOHATS folder on the Aloha Installation CD and place them in a temporary folder on the same drive partition as the Windows folder.� Open SETUPSYS.EXE, define the location of the temporary folder where the system files reside, and install the files.� Restart the computer.

Copy Windows 95, Windows 98, or Windows Me System Files (4.4x and higher)

This step is required if the remote computer is using the Windows 95, Windows 98, or Windows Me operating system.

EDC requires system files in the Windows SYSTEM folder on the remote computer.

Extract the system files from W95DLL.ZIP and W95DLL2.ZIP in the ALOHATS folder on the Aloha Installation CD, and place them in the Windows SYSTEM folder.� Restart the computer.

Some files may be in use by Windows, so you may have to restart the computer to a MS-DOS^� prompt to replace the files.

Do not overwrite newer versions of the files.

Register ATL.DLL (4.2x only)

If the remote EDC client is using the Windows NT, Windows 2000, Windows XP, or Windows Server 2003 OS, copy ATL.DLL from WNTDLL.ZIP in the ALOHATS or ALOHAQS folder in the Aloha Installation CD to the Windows SYSTEM32 folder.� Open a command prompt, and navigate to the Windows SYSTEM32 folder.� Type the following command line to register ATL.DLL (a successful confirmation should follow the registration):

REGSVR32.EXE ATL.DLL

If the remote EDC client is using the Windows 95, Windows 98, or Windows Me OS, copy ATL.DLL from W95DLL.ZIP in the ALOHATS or ALOHAQS folder in the Aloha Installation CD to the Windows SYSTEM folder.� Open a command prompt, and navigate to the Windows SYSTEM folder.� Type the following command line to register ATL.DLL (a successful confirmation should follow the registration):

REGSVR32.EXE ATL.DLL

Do not overwrite a newer version of ATL.DLL if it already exists.

Register ATL.DLL (4.4x and higher)

If the remote EDC client is using the Windows NT, Windows 2000, Windows XP, or Windows Server 2003 OS, open a command prompt, and navigate to the Windows SYSTEM32 folder.� Type the following command line to register ATL.DLL (a successful confirmation should follow the registration):

REGSVR32.EXE ATL.DLL

If the remote EDC client is using the Windows 95, Windows 98, or Windows Me OS, open a command prompt, and navigate to the Windows SYSTEM folder.� Type the following command line to register ATL.DLL (a successful confirmation should follow the registration):

REGSVR32.EXE ATL.DLL

Register Aloha Security Files (4.4x and higher)

Open a command prompt on the remote EDC client and type the following command line to register the copy of ALOHASEC.EXE from the EDC file server on the remote EDC client (a successful confirmation should follow the registration):

\\ALOHABOH\BOOTDRV\ALOHA\BIN\ALOHASEC.EXE /REGSERVER

If the remote EDC client is using the Windows NT, Windows 2000, Windows XP, or Windows Server 2003 OS, open a command prompt on the remote EDC client and navigate to the Windows SYSTEM32 folder.� Type the following command line to register the copy of ASECPS.DLL from the EDC file server on the remote EDC client (a successful confirmation should follow the registration):

REGSVR32.EXE \\ALOHABOH\BOOTDRV\ALOHA\BIN\ASECPS.DLL

If the remote EDC client is using the Windows 95, Windows 98, or the Windows Me OS, open a command prompt on the remote EDC client and navigate to the Windows SYSTEM folder.� Type the following command line to register the copy of ASECPS.DLL from the EDC file server on the remote EDC client (a successful confirmation should follow the registration):

REGSVR32.EXE \\ALOHABOH\BOOTDRV\ALOHA\BIN\ASECPS.DLL

If the remote EDC client is using the Windows NT, Windows 2000, Windows XP, or Windows Server 2003 OS, open a command prompt on the remote EDC client and navigate to the Windows SYSTEM32 folder.� Type the following command line to register the copy of ARSEC.DLL from the EDC file server on the remote EDC client (a successful confirmation should follow the registration):

REGSVR32.EXE \\ALOHABOH\BOOTDRV\ALOHA\BIN\ARSEC.DLL

If the remote EDC client is using the Windows 95, Windows 98, or the Windows Me OS, open a command prompt on the remote EDC client and navigate to the Windows SYSTEM folder.� Type the following command line to register the copy of ARSEC.DLL from the EDC file server on the remote EDC client (a successful confirmation should follow the registration):

REGSVR32.EXE \\ALOHABOH\BOOTDRV\ALOHA\BIN\ARSEC.DLL

If the remote EDC client is using the Windows NT, Windows 2000, Windows XP, or Windows Server 2003 OS, open a command prompt on the remote EDC client and navigate to the Windows SYSTEM32 folder.� Type the following command line to register the copy of ARSECPS.DLL from the EDC file server on the remote EDC client (a successful confirmation should follow the registration):

REGSVR32.EXE \\ALOHABOH\BOOTDRV\ALOHA\BIN\ARSECPS.DLL

If the remote EDC client is using the Windows 95, Windows 98, or the Windows Me OS, open a command prompt on the remote EDC client and navigate to the Windows SYSTEM folder.� Type the following command line to register the copy of ARSECPS.DLL from the EDC file server on the remote EDC client (a successful confirmation should follow the registration):

REGSVR32.EXE \\ALOHABOH\BOOTDRV\ALOHA\BIN\ARSECPS.DLL

The ALOHASEC.EXE, ASECPS.DLL, ARSEC.DLL and ARSECPS.DLL need to be re-registered on the remote EDC client each time the Aloha Application Software is upgraded to a newer version.

Install EDCSVR.EXE (4.2x Only)

This is only required for versions 4.2x.� Users of later versions must skip this section.

Install the EDCSVR.EXE (EDC Server) by typing the following from a command line (replace the correct location of EDC Server on the EDC file server):

\\ALOHABOH\BOOTDRV\ALOHA\BIN\EDCSVR.EXE /REGSERVER

Configure DCOM for Remote Use (4.2x Only)

This is only required for versions 4.2x.� Users of later versions must skip this section.

If the remote EDC client is using the Windows NT, Windows 2000, Windows XP, or Windows Server 2003 OS, run DCOMCNFG from the Windows SYSTEM32 folder.� If the remote EDC client is using the Windows 95, Windows 98, or the Windows Me OS, run DCOMCNFG.EXE from the Windows SYSTEM folder.�

Select EDC Class from the Applications list, and select Properties.� Select the Location tab, clear 'Run application on this computer,' and select 'Run application on the following computer.' Define the name of the EDC file server in the space provided (for example, ALOHABOH).

If EDC Class is not listed in the Applications, EDC Server has not been successfully registered.� Refer to the Install EDC Server section of the document.

Select the Default Security tab, and check 'Enable remote connection.'

Shortcut to EDC.EXE

If you are using versions 4.2x, create a new shortcut on the desktop of the remote EDC client using the following command line (replace the correct location of EDC.EXE on the EDC file server and the IBERDIR):

\\ALOHABOH\BOOTDRV\ALOHA\BIN\EDC.EXE /IBERDIR \\ALOHABOH\BOOTDRV\ALOHA

If you are using versions 4.4x or higher, create a new shortcut on the desktop of the remote EDC client using the following command line (replace the correct location of EDC.EXE on the EDC file server and the IBERDIR):

\\ALOHABOH\BOOTDRV\ALOHA\BIN\EDC.EXE /EDCSVR \\ALOHABOH /SECSVR \\ALOHABOH /SECSVRPATH \\ALOHABOH\BOOTDRV\ALOHA /IBERDIR \\ALOHABOH\BOOTDRV\ALOHA

Refer to document AKBID1010 for more information on environment variables.

REPORTMODE

The REPORTMODE variable limits the user to reports only.� Add /REPORTMODE to the EDC command line to enable this.

REPORTMODE overrides user login settings in versions 5.0x and higher.

Upgrading EDC

If you are upgrading from versions 4.2x to versions 4.4x or higher, unregister EDC Server with the following command line before configuring remote EDC 4.4x and higher:

\\ALOHABOH\BOOTDRV\ALOHA\BIN\EDCSVR.EXE /UNREGSERVER

When performing any upgrade, regardless of the version, replace and re-register all .EXE and .DLL files.

Extended Information

SuperSites or locations using multiple copies of EDC need to include the EDCPATH variable in the EDC.EXE shortcut command line.� Refer to document AKBID1010 and AKBID1020 for more information.

The EDC.INI may exceed 64,000 bytes (64K) in size in very rare occasions where the number of defined credit card processors exceeds 100.�� Remote copies of EDC.EXE using the Windows 95, Windows 98, or Windows Me will not recognize an INI file over 64K and truncate the information in excess of the 64K.

Caveats

Remote EDC must use a TCP/IP connection.

EDC file servers using Microsoft Windows 98, or Windows Me may require the manual configuration of DCOM, even with the Aloha application software already installed on it.

Do not overwrite newer versions of the ATL.DLL if they already exist

When performing any upgrade, regardless of the version, replace and re-register all .EXE and .DLL files.

The EDC.INI may exceed 64,000 (64K) bytes in size in very rare occasions where the number of defined credit card processors exceeds 100.�� Remote copies of EDC.EXE using the Windows 95, Windows 98, or Windows Me will not recognize an INI file over 64K and truncate the information in excess of the 64K.

============================================================================

See also:

AKBID1010 Aloha Application Software System Environment Variables

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1020 EDC Process

AKBID1049 Installing DCOM in Windows

AKBID1063 TCP/IP

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional Query Words: 1050

Aloha Application Software Flag and Marker Files

Aloha Application Software Flag and Marker Files

============================================================================

AKBID1051

Created: 26 April 2000

Updated: 11 August 2003

Reviewed: 5 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 4.0x � 5.3.x

Subject: Aloha Application Software Flag Files

============================================================================

Summary

The ALOHA^� application software often uses 'flag' files to configure the behavior of the application software.� While many of these files are created and removed by the software during daily operations, some files are created manually.� This document explains these files, their options, and where to create (or delete) them.

Information

Unless otherwise noted, the contents of the flag file are unimportant.� Create them using the following command line from the folder the file is to reside in:

ECHO 1 > x

Replace x with the name of the file.

CHAMPS or CHAMPPS

Location

%IBERDIR%

Purpose

Instructs IBER.EXE to write 'CHAMPPS extensions enabled' to the terminal's debout, changes 'extra' modifier text from 'XT' to Extra', and changes 'side' modifier text from 'SD' to 'On Side'.

Created by

Manually

Common Error

None

CHANGED

Location

%IBERDIR%\EDC

Purpose

Signals Back-of-House (BOH) changes to EDC transactions so the Front-of-House (FOH) updates itself wit the changes (refer to document AKBID1020)

Created by

EDCSVR.EXE or EDC.EXE

Common Error

None

CHICO

Location

%IBERDIR%

Purpose

Instructs GRIND.EXE to create ECSALE.DBF, ECTIME.DBF (only on the last day of the week), ECITEM.DBF and ECLABOR.TXT (ASCII) in the DATA or dated folder.

Created by

Manually

Common Error

None

DEMOPMS

Location

%IBERDIR%

Purpose

Demonstrates the PMS functions with fake authorizations (refer to document AKBID1062)

Created by

User

Common Error

None

DONE30

Location

%IBERDIR%\yyyymmdd

Purpose

Designates successful completion of the End-of-Day (EOD) process (refer to document AKBID1015)

Created by

IBER.EXE or IBERQS.EXE

Common Message

Waiting for End-of-Day to Complete

EOD

Location

%IBERDIR%\DATA

Purpose

Designates the EOD process has started (refer to document AKBID1015)

Created by

IBER.EXE or IBERQS.EXE

Common Message

Processing End-of-Day

EODGRIND

Location

%IBERDIR%\yyyymmdd

Purpose

Used with Relational Databases (RDB), designates the successful completion of the Grind process after the EOD process (refer to document AKBID1016)

Created by

GRIND.EXE or GRINDQ.EXE

Common Message

Waiting for yyyymmdd to Grind

EXITING

Location

%IBERDIR%\TMP

Purpose

Signals other terminals that the local terminal is shutting down or is not currently running IBER.EXE or IBERQS.EXE (refer to document AKBID3091)

Created by

IBER.EXE or IBERQS.EXE

Common Message

Waiting for Exiting File to Disappear

FASTFOOD

Location

%IBERDIR%

Purpose

Instructs Maintenance, Aloha Manager, Control, and Aloha Video to use QuickService functionality

Created by

SETUPPOS.EXE or manually

Common Message

None

FUDD

Location

%IBERDIR%

Purpose

Instructs IBER.EXE to write 'FUDD extensions enabled' to the terminal's debout, disables the Open Drawer and Hold buttons on the order entry screen, changes the 'New Order' button text to 'Guest Name', changes the 'Add to Tab' button text to 'Add to Guest', and automatically displays the tenders screen after a tab is named.

Created by

Manually

Common Message

None

GNDDBF30.XXX

Location

%IBERDIR%\yyyymmdd

Purpose

Designates the successful completion of the Grind process after the EOD process (refer to document AKBID1016)

Created by

GRIND.EXE or GRINDQ.EXE

Common Message

Waiting for yyyymmdd to Grind

HALT

Location

C:\

Purpose

No longer used, it signaled CONNMGR.EXE to restart the terminal (refer to document AKBID3112)

Created by

IBER.EXE or IBERQS.EXE

Common Message

None

HIDEGRIND

Location

%IBERDIR%\STRnnnn

Purpose

Used with a RDB and in conjunction with the GRINDHIDEWINDOW ALOHAl.INI variable, disables the Grind applications user interface (refer to document AKBID1187)

Created by

Manually

Common Message

None

IBMRES

Location

%IBERDIR%\BIN

Purpose

Used with the IBM 4695 POS terminal (refer to document AKBID1032)

Created by

Manually

Common Message

Failed to Initialize IBM Error 336

IBEREXE.DLL

Location

%IBERDIR%\BIN

Purpose

Disables the BOH Super-Secret-Password (SSP) (refer to document AKBID3090)

Created by

Manually

Common Message

None

LANDRYS

Location

C:\

Purpose

Changes the functionality of the SSP and the BOH Sales Report, and in versions 5.2.5.x and higher, creates Landry's-specific export files (refer to document AKBID3038)

Created by

Manually

Common Message

None

MSYNC

Location

%IBERDIR%\DATA

Purpose

Signals to the FOH terminals that the Master terminal is synchronizing with the file server� (refer to document AKBID3092)

Created by

IBER.EXE or IBERQS.EXE

Common Message

Unable to delete %IBERDIR%\DATA\MSYNC

NOGRIND

Location

%IBERDIR%\STRnnnn

Purpose

Disables the regrind process for a specific dated folder

Created by

GRIND.EXE or GRINDQ.EXE

Common Message

None

NOREGRIND

Location

%IBERDIR%\yyyymmdd

Purpose

In versions, 5.2.7.165 through 5.2.7.x, and 5.2.8.57 and higher, the Regrind Subdirectories utility creates a NOREGRIND flag in the dated folder if it is unable to regrind it.� The enables the Regrind Subdirectories utility to move on to the next dated folder in the list.� When this occurs, the dated folder is noted as 'Noregrind' in the Regrind Subdirectories utility, and you can reselect the dated folder in order to attempt to regrind it again.

Created by

Control, Aloha Manager, GRIND.EXE, GRINDQ.EXE, or Manually

Common Message

None

OK

Location

%IBERDIR%\DATA

Purpose

Signals to the FOH terminals that the data on the file server is ready for use (refer to document AKBID3008)

Created by

SETUPPOS.EXE or manually

Common Message

Waiting for System Configuration to Complete

PULLDONE

Location

%IBERDIR%\STRnnnn

Purpose

Used with SuperSites, designates the FOH has finished synchronizing with the file server (refer to document AKBID3093)

Created by

IBER.EXE or IBERQS.EXE

Common Message

None

QSTSBOTH

Location

%IBERDIR%

Purpose

Used with SuperSites, instructs Maintenance or Aloha Manager to display both TableService and QuickService configuration options

Created by

Manually

Common Message

None

REFRESH

Location

%IBERDIR%\STRnnnn

Purpose

Used with SuperSites, instructs the FOH to refresh their data with the file server

Created by

Aloha Control or Aloha Manager

Common Message

None

REGRIND

Location

%IBERDIR%\STRnnnn; %IBERDIR%\yyyymmdd

Purpose

The REGRIND flag has two separate and exclusive functions.� If placed in the store folder on a file server using an RDB, it enables the Regrind utility to initiate the grind process on dated folders, even if a NOGRIND flag exists in the store's folder.

�

In a separate function, once the grind process has completed regrinding a dated folder, then it creates a REGRIND text file that contains the version of GRIND.EXE or GRINDQ.EXE that was used to regrind the dated folder.

Created by

Manually; GRIND.EXE or GRINDQ.EXE

Common Message

None

RUNGRIND

Location

%IBERDIR%\DATA\RUNGRIND

Purpose

On a non-RDB system, it instructs the CTLSVR.EXE to Grind the current day's data

Created by

Aloha Control or Aloha Manager

Common Message

None

SETTLED

Location

%IBERDIR%\EDC\<processor>

Purpose

Indicates the last settlement process completed successfully (refer to document AKBID1020)

Created by

EDC.EXE or EDCSVR.EXE

Common Message

Your last settlement was interrupted�

SETTLING

Location

%IBERDIR%\EDC\<processor>

Purpose

Indicates the settlement process is active (refer to document AKBID1020)

Created by

EDC.EXE or EDCSVR.EXE

Common Message

None

SHOWGRIND

Location

%IBERDIR%\STRnnnn

Purpose

Used with a RDB and in conjunction with the GRINDHIDEWINDOW ALOHAl.INI variable, enables the Grind applications user interface (refer to document AKBID1187)

Created by

Manually

Common Message

None

SPOOLING

Location

%IBERDIR%\EDC

Purpose

Indicates the FOH is processing credit cards in Spooling Mode (refer to document AKBID1020)

Created by

IBER.EXE or IBERQS.EXE

Common Message

None

STOP

Location

%IBERDIR%\TMP

Purpose

Stops the FOH and reboots the FOH terminals

Created by

Control or Aloha Manager

Common Message

Waiting for Permission to Resume

WINHOOK

Location

%IBERDIR%\yyyymmdd

Purpose

Designates that the Winhook batch file has been initialized for this dated folder (refer to document AKBID1028)

Created by

CTLSVR.EXE

Common Message

None

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1015 EOD Process and Errors

AKBID1016 Grind Process and Errors

AKBID1020 EDC Process

AKBID1028 Winhook

AKBID1032 IBM 4695 POS Terminal

AKBID1062 Property Management Systems

AKBID1187 Enable or Disable RDB Grind User Interfaces

AKBID3038 LANDRYS Flag

AKBID3090 Using IBEREXE.DLL to Disable the Super-Secret-Password

AKBID3091 EXITING File

AKBID3092 MYSYNC File

AKBID3093 PULLDONE File

AKBID3112 HALT File

AKBID3130 RUNGRIND File in the DATA Folder

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1051 fuddruckers tsqsboth super user superuser

�

Caller ID

Caller ID

============================================================================

AKBID1052

Created: 14 February 2000

Updated: 29 August 2002

Reviewed: 3 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.65x � 5.3.x

Subject: Using Caller ID with the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software interfaces with phone lines featuring caller ID using third-party caller ID devices.� This enables the Aloha application software Delivery/Frequent Buyer application to display the caller's name and/or phone number before you answer the call.� This document explains the basic configuration of caller ID devices in the Aloha application software.� Refer to the hardware vender's user manual for device-specific configuration.

Refer to document AKBID1048 for a complete list of caller ID devices supported by the Aloha application software.

Information

Some electronic phone systems do not support caller ID.� The phone lines connected to the caller ID device should bypass these phone systems.

Aloha Software Configuration

You must configure the number of caller ID lines connected to the caller ID device in the Aloha application software.� If you are using version versions 4.4x or lower, open Maintenance and select MX/Delivery.� If you are using versions 5.0x or higher, open Aloha Manager, select Maintenance/Store Settings/Delivery.

You also need to configure caller ID device in the Aloha BackOffice software.� Open the BackOffice Main Menu, and select Caller ID Control Panel from the Operations menu.� Set the 'Caller ID Device' to the type of device you are using, and select the COM port to which the device is attached.

The Caller ID Control Panel offers a caller ID testing feature.� To access this feature, click Test.� A blank screen displays that will record phone line activity.� With the testing feature started, place calls to the caller ID phone lines to see if it records the proper information.� Refer to the Delivery/Frequent Buy User Manual for more information.

You should disable the Delivery/Frequent Buyer POS Interface when using the caller ID testing feature, but the interface must be enabled during normal use.

Rochelle MLA

If you are using a Rochelle^� Multi-Line Adapter (MLA), model number 2045, attach the Rochelle MLA to an open serial (RS232) port on the Aloha application software file server using a standard serial cable.� Rochelle does not supply a serial cable with their MLA since the desired length is inconsistent from location to location.

Attach the incoming caller ID phone lines to the Rochelle MLA.� The Rochelle MLA supports up to six phone lines.

Disable the First-In-First-Out (FIFO) buffers on the COM port used by the caller ID device.

Failure to disable the FIFO buffers on the COM port used by the caller ID device can lead to inaccurate or repeated data from the caller ID device.

Extended Information

No information.

Caveats

Some electronic phone systems do not support caller ID.� The phone lines connected to the caller ID device should bypass these phone systems.

Failure to disable the FIFO buffers on the COM port used by the caller ID device can lead to inaccurate or repeated data from the caller ID device.

============================================================================

See also:

Delivery/Frequent Buyer User Manual

AKBID1048 Aloha Application Software Hardware and OS Specifications

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1052 callerid

�

TableService Order Entry Job Code Options

TableService Order Entry Job Code Options

============================================================================

AKBID1053

Created: 10 February 2000

Updated: 26 July 2002

Reviewed: 30 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: Table Service Order Entry Job Code Options and Description

============================================================================

Summary

An employee's interaction with menus, events, and other ALOHA^� application software functionality is determined by their job code settings, specifically the Shift Required, Order Entry, Bartender, and Cashier job codes settings.� This document explains each of these settings and how they affect the job code's behavior in the Aloha application software.

Information

Usage

Shift Required requires the employee to clock-in and clock-out, but it does not enable any order entry functionality.� On its own, Shift Required only enables access to Employee Functions and Manager Functions.� You must enable this setting, along with the Order Entry setting, to enable true order entry functionality.

Order Entry provides the employee access to menus and order entry capability if it is used with Shift Required; otherwise, only the Manager Function screens are available.� This setting provides the employee with 'server' capabilities in regards to menu assignment, events, customer polling functionality and other job code settings.� Order Entry must be enabled, along with Shift Required, to enable true order entry functionality.

The Bartender setting is used along with Shift Required and Order Entry.� This setting provides the employee with 'bartender' capabilities in regards to menu assignment, events, customer polling functionality and other job code settings.� Bartenders use tab names instead of table numbers and have access to Fast Cash functionality.

The Cashier setting is used with Shift Required and Order Entry.� This setting provides the employee with 'cashier' capabilities in regards to menu assignment, Events, customer polling functionality and other job code settings.� This does not grant any cashiering-specific functionality.

Rules

All order entry personnel must have Shift Required and Order Entry enabled.� Bartenders and cashiers do not receive order entry functionality unless these are enabled.

The Cashier setting in itself does not provide the ability to access the Get Check function.� Get Check access is assigned separately in the access levels.�

If a job code has both Bartender and Cashier enabled, the employee will see the Cashier menu as assigned in Default Menu Settings or events.� The Cashier setting is not required for bartenders that function as a cashier to the servers.� Bartender restriction options applied in the Aloha application software apply to this job code.

Examples

Server � Select Shift Required and Order Entry.� You can assign menus to this employee via the Default Server Menu, the Set Server Menu event, or the Set Menu Group event.�

Bartender � Select Shift Required, Order Entry, and Bartender.� You can assign menus to this employee via the Default Bartender Menu, the Set Bar Menu event, or the Set Menu Group event.

Cashier � Select Shift Required, Order Entry, and Cashier.� You can assign menus to this employee via the Default Cashier Menu, the Set Cashier Menu event, or the Set Menu Group event.

Cashier w/ Fast Cash � Select Shift Required, Order Entry, Bartender, and Cashier.� You can assign menus to this employee via the Default Cashier Menu, the Set Cashier Menu event, or the Set Menu Group event.

Cocktail � Select Shift Required, Order Entry, and Sees Tabs.� You can assign menus to this employee via the Default Server Menu, the Set Server Menu event, or the Set Menu Group event.

Extended Information

The reference to cocktail servers in Customer Polling refers to job codes with Shift Required, Order Entry, and Sees Tabs enabled.

Caveats

Employees with multiple job codes are required to clock-in regardless of the Shift Required setting.� The employee also has full order entry capability (if Order Entry is enabled) regardless of the Shift Required setting.

If default menus are not declared in the Back-of-House (BOH) for servers, bartenders or cashiers, the respective job code uses the lowest numbered menu in the menu database (refer to document AKBID1042).

============================================================================

See also:

Aloha TableService User Manual

AKBID1042 Aloha Application Software Database Files

AKBID1064 Tip Out Feature

AKBID1098 Order Taker Job Code Option

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1053

�

Revenue Centers

Revenue Centers

============================================================================

AKBID1054

Created: 14 February 2000

Updated: 5 March 2004

Reviewed: 5 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: Revenue Center Application and Hierarchy

============================================================================

Summary

Each guest check opened in the ALOHA^� application software is assigned to a revenue center.� A revenue center is a physical part of the restaurant such as the bar, dining room, patio, and so on.� Revenue centers are assigned in multiple locations and follow a hierarchy for their assignment.

Information

The revenue center is assigned to a check (whether assigned by the table number or terminal) when the first item is ordered.� This revenue center stays with the check regardless of transfers or if items are applied from another terminal.�

For example, if a check is opened in the bar for a party waiting on their table, the check is assigned to the bar's revenue center.� If the check is transferred to the dining room after the party is seated, the dining room orders still apply to the bar's revenue center.�

The revenue center changes only if the check is merged with another check belonging to another revenue center.� All of the items are applied to the new revenue center.� In the previous example, if the server in the dining room merges the check from the bar with a check from the dining room that already has the party's food on it, the bar orders and the dining room orders are applied to the dining room's revenue center.

Aloha application software versions 5.2x and higher enable you to select the method for reporting the revenue center in the Product Mix Report.� You can report by the revenue center assigned to the check when it was opened or the revenue center from which the item was ordered.

TableService

Revenue centers are assigned to order modes, tables, terminals, and job codes.� The hierarchy for sales attribution is order mode overrides table overrides terminal.� Job codes revenue centers are not included in the hierarchy.� In Aloha versions 5.2.7.182 through 5.2.7.x, 5.2.8.73 through 5.2.8.x, and 5.3.1.42 and higher, the payment is always attributed to the terminal's revenue center.

The revenue center attached to the order mode is applied to a guest check if a revenue center is assigned to the order mode.� If a revenue center is not assigned to the order mode, the revenue center attached to the table is applied to a guest check if a table number is used.� If a revenue center is not assigned to the order mode and a tab is used, the revenue center attached to the terminal is assigned to the guest check.

The revenue center for the job code only applies to the Hourly Sales and Labor Report's 'Split Hourly Sales and Labor by Revenue Center' setting.� It has no bearing on the guest check's revenue center assignment.

QuickService

Revenue centers are assigned to terminals and job codes.� The revenue center attached to the terminal is assigned to each guest check.

The revenue center attached to the job code only applies to the Hourly Sales and Labor Report's 'Split Hourly Sales and Labor by Revenue Center' setting.� It has no bearing on the guest check's revenue center assignment.

Extended Information

If a restaurant wants the revenue center to be assignment based on the terminal and never assigned from a table, perform one of the following:

1.        If the restaurant has the Property Management Systems (PMS) interface enabled, open Aloha Manager and select Maintenance/Store Settings/Hotel and select 'Report Revenue Center sales from where check originated'.� Refresh the system.

2.        If the restaurant does not have the Property Management Systems (PMS) interface enabled, edit ALOHA.INI in the NEWDATA folder, and set PMSUSETERMREVCENTER to TRUE (PMSUSETERMREVCENTER=TRUE).� Refresh the system.

If the restaurant wants only select tables to override the terminal's revenue center, only assign revenue centers to the select tables.� Tables without revenue centers assigned to them do not override the revenue center assigned to terminals.

Many restaurants have a bar area serviced by bartenders and cocktail staff, and a dining room serviced by a wait staff.� The bar staff uses tab names and the wait staff uses table numbers.� In this case, it would be prudent to assign all terminals to the Bar revenue center.� This enables the entire staff to use any terminal in the restaurant and still have their sales assigned to the correct revenue center.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1054

�

TableService Guest Check Printing Options

TableService Guest Check Printing Options

============================================================================

AKBID1055

Created: 11 February 2000

Updated: 8 May 2000

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: TableService Guest Check Printing Options

============================================================================

Summary

The ALOHA^� application software offers several options for printing guest checks.�� Many of these options effect other printing options in the software and can become confusing.�� This document explains each printing option in TableService and the effects each has on other options.

Information

Some printing options may not be available with all versions of the Aloha application software.

Location

Option

Description

Tenders

Print Check on Close

Prints a check when the check is closed from the Payment screen or using Fast Cash.�� The number of checks defined in the Printers section effects the number of checks printed with this option.�� The printing option defined in the Revenue Center section overrides this option.

This setting, as applied to the default open cash tender, overrides this setting for all other cash tenders.

Comps

Print Check

Prints a check when a check is closed from the Payment screen or Fast Cash.� If this is enabled, a check prints even if the option is disabled on any Tenders applied to the check.� The number of checks defined in the Printers section effects the number of checks printed with this option.�� The printing option defined in the Revenue Center section overrides this one.

Promos

Print Check

Prints a check when a check is closed from the Payment screen or using Fast Cash.� If this is enabled, a check prints even if the option is disabled on any Tenders applied to the check.� The number of checks defined in the Printers section effects the number of checks printed with this option.�� The printing option defined in the Revenue Center section overrides this one.

Revenue Centers

Print Check

The 'Default' setting prints checks as chosen in other settings.� The 'Never' setting will not print a check.�� The 'Always' setting prints a check regardless of other settings.�� The latter two settings override the settings in Tenders, Comps, and Promos.

Queues

Auto Print

The number of checks defined in the Printers section effects the number of checks printed with this option.�� The printing option defined in the Revenue Center section overrides this one.

Printers

# Guest Checks

Defines the number of guest checks that print when the check is closed from the Payment screen or using Fast Cash.� The printing option defined in the Revenue Center section overrides this if set to Never.

Printing

Auto print when food is ordered

Prints a guest check after an order mode is applied to the item.� The number of checks defined in the Printers section does not affect the number of checks printed with this option.�� The printing option defined in the Revenue Center section does not override this one.

Printing

Don't auto print when manager adjusts checks

Disables the automatic printing of a guest check if a manager adjusts a check from the Manager Function screen.� This is not applied if the check is adjusted using the Manager Just In Time (JIT) feature.� The number of checks defined in the Printers section does not affect the number of checks printed with this option.�� The printing option defined in the Revenue Center section does not override this one.

Printing

Don�t auto print when bartender closes checks

Disables the automatic printing of a guest check when the bartender closes a check from the Payment screen or using Fast Cash.� The number of checks defined in the Printers section effects the number of checks printed with this option.�� If this option is not enabled, the printing options defined in the Revenue Center and Tenders sections override this one.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1055

Upgrading the Aloha Application Software

Upgrading the Aloha Application Software

============================================================================

AKBID1056

Created: 15 February 2000

Updated: 12 February 2003

Reviewed: 17 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 3.6x � 5.3.x

Subject: Upgrading the Aloha Application Software

============================================================================

Summary

You can upgrade the ALOHA^� application software using the installation application from the Aloha Installation CD with the new application files or by manually adding the new files to the BIN folder.� Upgrading with the Aloha Installation CD is the preferred upgrade method and you should use this method in place of a manually upgrading the application files whenever possible.� The upgrade process should occur after the system has completed the End-of-Day (EOD) process and before new transactions are added to the new Date-of-Business (DOB).� Transactions include sales, labor, and Front-of-House (FOH) configuration changes such as rerouting printers for videos.

You should use the Aloha Installation CD to upgrade the Aloha application software whenever possible.

Information

It is critical that you start the software upgrade process after successfully completing the EOD process, but before regular business is started for the subsequent day.

Using the Aloha Installation CD

1.        Shut down and turn off all FOH terminals.

2.        Close any remote instances of the Back-of-House (BOH) applications.

3.        Close all open applications on the BOH file server.

4.        Create backup copies of the Bin, Data, and NewData folders in the root Aloha application software folder.� Do not place the backup copies of these folders within their respective folders (for example, \Data\Data42 or \Bin\Bin42.)

5.        Delete all log files (*.log) from the Data folder.� Deleting the log files removes any current day sales or carry-over data from the previous day (24-hour systems).

6.        Insert the Aloha Installation CD into the file server.� If the operating system (OS) is configured to automatically start the software on the CD, the Aloha application software installation software will start.� If the OS is not setup to start the software automatically, start SetupPOS.exe from the root folder of the CD (for example, D:\SetupPOS.exe).

7.        In most cases, the installation software automatically displays the Upgrade screen and you can click Upgrade to begin the process.� Otherwise, you will otherwise have to select the system type (TableService or QuickService) and click the Next button at each configuration screen after verifying the displayed configuration settings.�

8.        When the upgrade process completes (which may include one or more reboots), open Maintenance or Aloha Manager and perform a cursory check of the data.

9.        Refresh the Aloha application software.

10.     Update any BackOffice applications.

11.     Turn the FOH terminals on.� If the FOH terminal were initially setup properly, they should automatically perform the update themselves without any user intervention.

Some versions may require you to upgrade the FOH terminals using the terminal installation diskette in order to reinstall the Aloha application software.� If the terminals do not upgrade automatically or do not function properly following the upgrade, use SetupTrm.exe to upgrade the FOH terminals.

Once the Aloha application software is upgraded and running properly, keep the backup copies of the Bin, Data, and NewData folders for several days to verify the correct operation of the upgraded software before deleting them.

Manually Upgrading Aloha

You should only perform manual upgrades on minor point upgrades (for example, 5.2.4.24 to 5.2.4.40), never on revision upgrades (for example, 5.2.4.24 to 5.2.5.10) or full version upgrades (5.2.x.x to 5.3.x.x).� Always register any new versions of application or .dll files that are replacing previously registered application or .dll files.

Shut down and turn off all FOH terminals.

Close any remote instances of the Back-of-House (BOH) applications.

Close all open applications on the BOH file server.

Unregister the Aloha software applications running as services (refer to document AKBID1019).

Create backup copies of the Bin, Data, and NewData folders in the root Aloha application software folder.� Do not place the backup copies of these folders within their respective folders (for example, \Data\Data42 or \Bin\Bin42.)

Delete all log files (*.log) from the Data folder.� Deleting the log files removes any current day sales or carry-over data from the previous day (24-hour systems).

Copy and/or decompress the new files into the Bin folder.

Reboot the file server.

Register the new services and .dll files (refer to document AKBID1019).

If you are upgrading to versions 5.0x and higher, refer to the Manual .DBF Database Upgrade or Manual RDB Database Upgrade section of this document to manually upgrade the database.

Open Maintenance/Aloha Manager and perform a cursory check of the data.

12.     Refresh the Aloha application software.

13.     Update any BackOffice applications.

14.     Turn the FOH terminals on.� If the FOH terminal were initially setup properly, they should automatically perform the update themselves without any user intervention.

Some versions may require you to upgrade the FOH terminals using the terminal installation diskette in order to reinstall the Aloha application software.� If the terminals do not upgrade automatically or do not function properly following the upgrade, use SetupTrm.exe to upgrade the FOH terminals.

Once the Aloha application software is upgraded and running properly, keep the backup copies of the Bin, Data, and NewData folders for several days to verify the correct operation of the upgraded software before deleting them.

Manual .DBF Database Upgrade

The following steps are only required if you did not upgrade the software using an Aloha Installation CD and you are using a .dbf-based system.

Perform the following to manually upgrade the data on a .dbf-based system:

1.        Start DBConfig.exe from the Bin folder.�

2.        Select only the following to update the .dbf files in the NewData folder:

-          Dbf Files Only

-          Attended

-          Debug

-          Force Upgrade

3.        Verify the IBERDIR description, and point the Input and Output text boxes to the NewData folder.

4.        Click Run.

If you are using versions 5.239 and lower, perform the following to update the index (.cdx) files in the NewData folder (this step is not required in versions 5.2.4.0 and higher since the 'Dbf Files Only' option in the previous step will have already updated the .cdx files):

1.        Start DBConfig.exe from the Bin folder.�

2.        Select only the following to update the .cdx files in the NewData folder:

-          Attended

-          Debug

-          Upgrade Dbf Index Files

3.        Verify the IBERDIR description, and point the Input and Output text boxes to the NewData folder.�

4.        Click Run.

Open Aloha Manager and refresh the system.

Manual RDB Database Upgrade

The following steps are only required if you did not upgrade the software using an Aloha Installation CD and you are using a RDB-based system.

Perform the following to manually upgrade the data on Relational Database (RDB) based system:

1.        Start DBConfig.exe from the Bin folder.�

2.        Select only the following to update the RDB:

-          Relational Database Only

-          Attended

-          Debug

-          Force Upgrade

3.        Verify the IBERDIR description, and point the Input and Output text boxes to the NewData folder.

4.        Click Run.

Perform the following to update the .dbf files used by the FOH:

1.        Start DBConfig.exe from the Bin folder.�

2.        Select only the following to update the .dbf files in the NewData folder:

-          Create Dbf Files

-          Attended

-          Debug

3.        Verify the IBERDIR description, and point the Input and Output text boxes to the NewData folder.

4.        Click Run.

Open Aloha Manager and refresh the system.

Upgrading the RDB Engine While Upgrading the Aloha application software

If you are upgrading the RDB engine when you upgrade the Aloha application software, you should update the Aloha application software prior to upgrading the RDB to ensure compatibility.� For example, if you are upgrading from Microsoft SQL 7.0 to SQL 2000 and from Aloha version 5.0 to Aloha version 5.2, and you upgrade the RDB engine before upgrading the Aloha application software, then Aloha version 5.0 will not be able to read or write to SQL 2000 since it is not supported in that version.� On the other hand, if you first update the Aloha application software to version 5.2, then version 5.2 is compatible with both SQL 7.0 and SQL 2000.

After you upgrade the Aloha application software and upgrade the RDB engine (which should include using the RDB engine to upgrade the Aloha application software RDB to match the current RDB engine), you must manually edit the RDBType variable in the SQL.INI to reflect the RDB engine.� Contact the Aloha Customer Service Center (CSC) for the value that represents the new RDB engine.

Using a Batch File to Manually Upgrade Versions 5.0x and Higher

You should use the Aloha Installation CD to upgrade the Aloha application software whenever possible.

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

If you are using a batch file to manually upgrade the Aloha application software versions 5.0x and higher, the batch file must perform the following functions after you have closed all open applications on the BOH file server and closed any remote instances of the BOH applications:

-          Create a Stop file in the Aloha application software Tmp folder on the file server.

-          Move the Trans.log (transaction log) from the Aloha application software Data folder.

-          Delete the printer and video logs from the Data folder.

-          Unregister all Aloha software applications and .dll files.

-          Backup the current Aloha application software Bin folder.

-          Backup the current Data folder.

-          Copy the new files to the Bin folder.

-          Register all Aloha software applications and .dll files.� Refer to document AKBID1162 for more information on services versus non-services.

-          Use DBUp.exe to upgrade the database files.� Refer to document AKBID1067 for the correct DBUp.exe version to use.

-          Delete the Stop file in the Tmp folder.

The following is an example of a batch file used for manually upgrading the Aloha application software:

The information in this batch file is for versions 5.0x through 5.3.x.x.� If you are using a higher version, refer to documents AKBID1019 and AKBID1067 for to verify the application registration information and DBUp.exe usage for the version.

Create a Stop file in the Tmp folder and use Wait.exe to create a timed pause that ensures the FOH terminals have exited Iber.exe/IberQS.exe.� Refer to document AKBID1012 for more information regarding Wait.exe:

Echo 1 > %IBERDIR%\Tmp\Stop

Wait.exe 30

Move the transaction log to a temporary folder and delete the printer and video logs:

MOVE %IBERDIR%\Data\Trans.log %IBERDIR%\Tmp\TransUpg.log

Echo Y | Del %IBERDIR%\Data\*.log

If you are using Microsoft^� Windows^� 95, Windows 98, or Windows Millennium Edition (Me), disable CtlSvr.exe (Control Server) and, if applicable, EDCSvr.exe (EDC Server), using KillSvr.exe:

%IBERDIR%\Bin\KillSvr.exe -K CtlSvr.exe

%IBERDIR%\Bin\KillSvr.exe -K EDCSvr.exe

If you are using Windows NT^�, Windows 2000 or Windows XP, disable CtlSvr.exe (Control Server) and, if applicable, EDCSvr.exe (EDC Server), using the Net Stop command:

Net Stop CtlSvr.exe

Net Stop EDCSvr.exe

You should also want to use the CloseApp.exe utility to ensure all open Aloha software applications are closed.� Refer to document AKBID1012 for more information regarding CloseApp.exe.

Unregister Aloha software applications (refer to document AKBID1019 for 'silent' registration options to disable the confirmation prompts):

%IBERDIR%\Bin\AlohaMgr.exe /UnRegServer

%IBERDIR%\Bin\ALOHASEC.exe /UnRegServer

%IBERDIR%\Bin\CtlSvr.exe /UnRegServer

Unregister Aloha application software .dll files using RegSvr32.exe: (Replace 'C:\Windows\System' with the correct path to RegSvr32.exe.� For example, use 'C:\WinNT\System32\RegSvr32.exe'.)

C:\Windows\System\RegSvr32.exe /U %IBERDIR%\Bin\AlohaLab.dll

C:\Windows\System\RegSvr32.exe /U %IBERDIR%\Bin\AmgrPS.dll

C:\Windows\System\RegSvr32.exe /U %IBERDIR%\Bin\AmgrShim.dll (Versions 5.0x only)

C:\Windows\System\RegSvr32.exe /U %IBERDIR%\Bin\ASecPS.dll

C:\Windows\System\RegSvr32.exe /U %IBERDIR%\Bin\Ctl4x.dll

C:\Windows\System\RegSvr32.exe /U %IBERDIR%\Bin\CtlSvrPS.dll

C:\Windows\System\RegSvr32.exe /U %IBERDIR%\Bin\EdtPunch.dll

C:\Windows\System\RegSvr32.exe /U %IBERDIR%\Bin\Mnt4x.dll

C:\Windows\System\RegSvr32.exe /U %IBERDIR%\Bin\UserTool.dll

C:\Windows\System\RegSvr32.exe /U %IBERDIR%\Bin\Crystl32.ocx (Versions 5.2x and higher)

If applicable, unregister EDC Server:

%IBERDIR%\Bin\EDCSvr.exe /UnRegServer

If applicable, unregister EDC .dll files using RegSvr32.exe:

C:\Windows\System\RegSvr32.exe /U %IBERDIR%\Bin\EDCSvrPS.dll

Create folders to backup the Data and Bin folders to, and backup the Data and Bin folders:

MD %IBERDIR%\DataBku

Copy %IBERDIR%\Data\*.* %IBERDIR%\DataBku\*.*

MD %IBERDIR%\BinBku

Copy %IBERDIR%\Bin\*.* %IBERDIR%\BinBku\*.*

Update the Bin folder with the upgraded application and .dll files:

Copy %IBERDIR%\NewBin\*.* %IBERDIR%\Bin\*.*

Register Aloha software applications using Service in place of RegServer with Control Server to register it as a Windows service (refer to document AKBID1162):

%IBERDIR%\Bin\AlohaMgr.exe /RegServer

%IBERDIR%\Bin\ALOHASEC.exe /RegServer

%IBERDIR%\Bin\CtlSvr.exe /RegServer

Register Aloha application software .dll files using RegSvr32.exe:

C:\Windows\System\RegSvr32.exe %IBERDIR%\Bin\AlohaLab.dll

C:\Windows\System\RegSvr32.exe %IBERDIR%\Bin\AmgrPS.dll

C:\Windows\System\RegSvr32.exe %IBERDIR%\Bin\AmgrShim.dll (Versions 5.0x only)

C:\Windows\System\RegSvr32.exe %IBERDIR%\Bin\ASecPS.dll

C:\Windows\System\RegSvr32.exe %IBERDIR%\Bin\Ctl4x.dll

C:\Windows\System\RegSvr32.exe %IBERDIR%\Bin\CtlSvrPS.dll

C:\Windows\System\RegSvr32.exe %IBERDIR%\Bin\EdtPunch.dll

C:\Windows\System\RegSvr32.exe %IBERDIR%\Bin\Mnt4x.dll

C:\Windows\System\RegSvr32.exe %IBERDIR%\Bin\UserTool.dll

C:\Windows\System\RegSvr32.exe %IBERDIR%\Bin\Crystl32.ocx (Versions 5.2x and higher)

If applicable, register EDC Server using Service in place of RegServer to register it as a Windows service (refer to document AKBID1162):

%IBERDIR%\Bin\EDCSvr.exe /RegServer

If applicable, register EDC .dll files using RegSvr32.exe:

C:\Windows\System\RegSvr32.exe %IBERDIR%\Bin\EDCSvrPS.dll

If you are using a .dbf-based system, use the appropriate version of DBUp.exe (refer to document AKBID1067) to upgrade the data and index files in NewData and Data:

The following steps are only required if you are using a .dbf-based system.

START /WAIT %IBERDIR%\Bin\DBUp3.exe /DBFOnly /Debug /ForceUpgrade /DBFInput %IBERDIR%\NewData /DBFOutput %IBERDIR%\NewData

START /WAIT %IBERDIR%\Bin\DBUp3.exe /Cdx /Debug /DBFInput %IBERDIR%\NewData /DBFOutput %IBERDIR%\NewData

START /WAIT %IBERDIR%\Bin\DBUp3.exe /DBFOnly /Debug /ForceUpgrade /DBFInput %IBERDIR%\Data /DBFOUTPUT %IBERDIR%\Data

START /WAIT %IBERDIR%\Bin\DBUp3.exe /Cdx /Debug /DBFInput %IBERDIR%\Data /DBFOutput %IBERDIR%\Data

If you are using a RDB-based system, use the appropriate version of DBUp.exe (refer to document AKBID1067) to upgrade the data and index files in NewData and Data:

The following steps are only required if you are using an RDB-based system.

START /WAIT %IBERDIR%\Bin\DBUp3.exe /DBOnly /Debug /ForceUpgrade

START /WAIT %IBERDIR%\Bin\DBUp3.exe /CreateDBF /Debug /DBFOutput %IBERDIR%\NewData

START /WAIT %IBERDIR%\Bin\DBUp3.exe /CreateDBF /Debug /DBFOutput %IBERDIR%\Data

Delete the Stop file to restart the FOH:

Del %IBERDIR%\Tmp\Stop

Extended Information

FOH Application Shortcuts

An actual copy of the Iber.exe/IberQS.exe file in the Windows StartUp folder of one or more FOH terminals is one of the most common causes of FOH problems following an upgrade.� The FOH terminals must have a shortcut to Iber.exe/IberQS.exe in the start up folder rather than the actual executable.� The shortcut should point to the Iber.exe/IberQS.exe file in the local Bin folder.� Failure to set this up properly can result in the FOH continuously updating the application files and general protection faults.

Upgrading a Multi-Concept System

When you perform an upgrade to the Aloha application software, you cannot use the 'One-Button-Upgrade' feature on the Aloha Installation CD.� You must use the installation CD to reinstall each concept as if it where a new installation.� SetupPOS.exe will not overwrite existing data, so it will effectively perform an upgrade.� Once you have upgraded each concept, ensure that you remove or edit any new shortcuts or environment variables created by SetupPOS.exe.

Caveats

It is critical that you start the software upgrade process after successfully completing the EOD process, but before regular business is started for the subsequent day.

You should use the Aloha Installation CD to upgrade the Aloha application software whenever possible.

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

The information in the example batch file is for versions 5.0x through 5.3.x.x.� If you are using a higher version, refer to documents AKBID1019 and AKBID1067 for to verify the application registration information and DBUp.exe usage for the version.

============================================================================

See also:

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1019 Manually Registering and Un-registering Aloha Applications

AKBID1067 DBUP.exe and DBCONFIG.exe

AKBID1155 Using 4.2x Dated Folder with 5.0x

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1188 Using Previous Version Dated Folders in 5.2x

AKBID1219 Updating Binary Files on an Existing Aloha Installation CD

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1056

Comp and Promo Taxes

Comp and Promo Taxes

============================================================================

AKBID1057

Created: 20 February 2000

Updated: 12 October 2000

Reviewed: 11 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

Subject: Configuring Comp and Promo Taxes

============================================================================

Summary

ALOHA^� application software Comps and Promotions (Promos) use unique tax options that enable multiple tax options to comply with local tax laws.� This document explains the possible primary tax options used with Comps and Promos.� This document does not cover secondary taxes and vendor taxes.

Information

Five fields define the primary tax setup for each comp or promo: Tax Comp Amount, Tax Food Cost, Food Cost, Tax ID, and Guest Pays Tax.� Perform the following to access these fields in the Aloha application software:

In versions 4.4x and lower, open Maintenance, and select either Comps or Promos from the Payment drop-down menu.

In versions 5.0x and higher, open Aloha Manager, and select either Payments/Comps or Payments/Promos from the Maintenance drop-down menu.

Tax Comp Amount � (comps only) Indicates the comp amount is taxed in accordance with the tax assigned to the item, regardless if it is the restaurant or the customer paying the tax.

Tax Applied Before Promotion � (promos only) Indicates the promo amount is taxed in accordance with the tax assigned to the item, regardless if it is the restaurant or the customer paying the tax.

Guest Pays Tax �Indicates that the tax will be charged to the guest, instead of the restaurant.

Tax Food Cost � Indicates the tax is applied on food cost percentage, not the item price.� Use this where tax liability is assessed on the cost of the item only.

Food Cost � Used with Tax Food Cost, indicates the estimated food cost percentage used for the tax calculation.� (30 = 30%)

Tax ID � Indicates an alternate Tax ID applied to the discount amount.

The following table describes a combination of options available and the resulting data:

(The table is based on a $100.00 check with a $50.00 discount and a 7% tax rate.)

Field

Option 1

Option 2

Option 3

Option 4

Option 5

Tax Discount Amount

-

X

X

X

X

Tax Food Cost

-

-

-

X

X

Food Cost

25%

25%

25%

25%

25%

Guest Pays Tax

-

-

X

-

X

Subtotal

$50.00

$50.00

$50.00

$50.00

$50.00

Guest Tax

$3.50

$3.50

$7.00

$3.50

$4.38

Guest Total

$53.50

$53.50

$57.00

$53.50

$54.38

Uncollected Tax

$0.00

$3.50

$0.00

$0.88

$0.00

'Uncollected Tax' is tax that is not collected from the patron, but the restaurant is responsible to pay.� This amount is printed in the Audit section of the Server Checkout if applicable.

If 'Tax Comp Amount' or 'Tax Applied Before Promotion' is not enabled, the other options discussed in this document are not applied.

Extended Information

No information.

Caveats

If 'Tax Comp Amount' or 'Tax Applied Before Promotion' is not enabled, the other options discussed in this document are not applied.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1057

style='mso-spacerun:yes'>� 2003

�

Pizza Modifiers

Pizza Modifiers

============================================================================

AKBID1058

Created: 12 April 2000

Updated: 21 July 2000

Reviewed: 18 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.0x � 5.3.x

Subject: Configuring the Aloha Application Software Functionality

============================================================================

Summary

The ALOHA^� application software has specific modifiers for restaurants that sell pizzas.� This document explains the method for configuring the pizza options and modifiers in the Aloha application software.

Information

Setup

Refer to the Aloha QuickService or TableService User Manual for more information on creating or editing items, modifier groups, sales categories, submenus, panels, menus and screens.

Perform the following to set up pizza modifiers (pricing is discussed in the Pricing section):

Create items to define the guest check and kitchen chit labels for right-half and left-half toppings.� For example, use '* Right Half� *' and '* Left Half *'.

Create items for each pizza size (for example, Small, Medium, and Large), and add them to a pizza size modifier group.

Create items for each pizza crust (for example, Thin, Thick, and Pan), and add them to a pizza crust modifier group.

Create items for each pizza topping (for example, Beef, Ham, and Onions), and add them to a pizza toppings modifier group.� Screen flow options are not required; the pizza modifier functionality sets this for you.

Create items for each type of pizza (for example, Regular, Meat Lovers, and Veggie Lovers), and add the pizza size modifier group as modifier one, the pizza crust modifier group to modifier 2, and the pizza toppings modifier group to modifier 3.

The size, crust, and toppings modifier groups must be in the correct order and assigned to modifiers one, two, and three.

Create a 'Pizza' Sales or Non-sales category, and add the pizzas created in Step 5 to it.� The items in this category, when placed on a submenu or panel, invoke the pizza modifiers screen.

Add the pizza items created in Step 5 to submenus (in TableService) or panels (In QuickService), and assign the submenus to menus or panels to screens.

In version 4.4 and lower, open Maintenance, and select Miscellaneous 2 from the Options drop-down menu.� In version 5.0 and higher, open Aloha Manager and select Maintenance/Store Settings/Order Entry/Pizza.

In the Pizza drop-down list, select the pizza category created in Step 6.�

In the Left Half and Right Half drop-down lists, select the left-half and right-half items created in Step 1.

Refresh the system.

With the exception of prices, the pizza functionality should work if tested in the Front-of-House (FOH).

Pricing

Pizza pricing, in general, follows the same conventions as normal item pricing, including modifier weights, minimum, maximum, and free.� Modifier weights only count for half of their normal weight if the modifier is only applied to half of the pizza.� Split toppings, that is, toppings for only half of the pizza, are automatically priced at 50% of their original price.� See the Aloha Application Software User Manual for more information.

Versions 5.0x and higher offer four new pricing options in regards to split toppings:

Percentage Pricing: Split-topping prices are figured by the defined percentage in relation to their normal price.

Average Pricing: Split-topping prices are figured by adding together the regular prices of each topping on each side, and then dividing the sum by the number of toppings.

Higher Priced Item Charged: Split-toppings prices are figured by the half with the highest total price based on regular prices.

Whole Price for Topping: Each topping is regular priced, regardless if used on a single half of the pizza or the whole pizza.

To access these pricing options, open Aloha Manager, and select Maintenance/Store Settings.� Select the Order Entry Group, and select the Pizza tab.

Maximum Numbers

The Aloha application software displays a maximum of 55 sizes, 55 crusts, and 54 toppings per pizza item.

Extended Information

Sites that do not offer a choice of size or crust can use blank modifier menus for modifier one or modifier two.

Caveats

The size, crust, and toppings Modifier Groups must be in the correct order and assigned to Modifiers one, two, and three.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1058

style='mso-spacerun:yes'>� 2003

Custom Checkouts

Custom Checkouts

============================================================================

AKBID1059

Created: 18 February 2000

Updated: 11 September 2003

Reviewed: 15 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.236 � 5.3.x

Subject: Configuring Custom Employee Checkouts

============================================================================

Summary

The ALOHA^� application software provides a user defined checkout report that you can use in addition to or to replace the standard checkout report.� You define the custom settings in the Checkout.cfg file and configure the usage in the Back-of-House (BOH).

Information

CHECKOUT.CFG Values

The following table lists the values available for configuring the Checkout.cfg.� Note that nnnn refers to the ID number assigned to the item in the Aloha application software.� Leading zeros are not required when referring to the ID number, but they can be used if desired.�

These values are added to the checkout using <VAL(width:formula)>, where width is the total number of spaces reserved for the value and formula is the numeric value or equation from the values listed below.� The formula is always a number containing two decimals, such as 1.00 instead of 1.

Value

Description

#GUESTS

Total count of all guests

#CHECKS

Total count of all checks

#S

Total count of all Sales categories

$S

Total dollar amount of all Sales categories

#Snnnn

Total count of Sales category nnnn

$Snnnn

Total dollar amount of Sales category nnnn

$X

Total dollar amount of all taxes

$Xnnnn

Total dollar amount of tax nnnn

$XI

Total dollar amount of inclusive taxes

$XE

Total dollar amount of exclusive taxes

$SUR

Total dollar amount of all surcharges

$SURnnnn

Total dollar amount of surcharge nnnn

#T

Total count of all tenders

$T

Total dollar amount of all tenders

#Tnnnn

Total count of tender nnnn

$Tnnnn

Total dollar amount of tender nnnn

$TNRnnnn

Total dollar amount of tender nnnn not redeemed (overpayment without change to guest)

$TFCnnnn

Total dollar amount of foreign currency tender nnnn in based on the foreign currency, not the base currency

$TIPS

Total dollar amount of all tips on non-cash tenders

$TIPSnnnn

Total dollar amount of tips for tender nnnn

#C

Total count of all comps

$C

Total dollar amount of all comps

#Cnnnn

Total count of comp nnnn

$Cnnnn

Total dollar amount of comp nnnn

#P

Total count of all promos

$P

Total dollar amount of all promos

#Pnnnn

Total count of promo nnnn

$Pnnnn

Total dollar amount of promo nnnn

#V

Total count of all voids

$V

Total dollar amount of all voids

#R

Total count of all refunds

$R

Total dollar amount of all refunds

#GC

Total count of all gift certificates sold

$GC

Total dollar amount of all gift certificates sold

#GCnnnn

Total count of all gift certificate nnnn sold

$GCnnnn

Total dollar amount of gift certificate nnnn sold

#GCC

Total count of all gift certificate comps

$GCC

Total dollar amount of all gift certificate comps

#GCCnnnn

Total count of gift certificate nnnn comps

$GCnnnn

Total dollar amount of gift certificate nnnn comps

#GCP

Total count of all gift certificate promos

$GCP

Total dollar amount of all gift certificate promos

#GCPnnnn

Total count of gift certificate nnnn promos

$GCPnnnn

Total dollar amount of gift certificate nnnn promos

#OMCnnnn

Total count of order mode charges for order mode nnnn

$OMCnnnn

Total dollar amount of order mode charges for order mode nnnn

#ACCTnnnn

Total count of transactions for cash account nnnn

$ACCTnnnn

Total dollar amount of transactions for cash account nnnn

#TAXEXEMPT

Total count of tax exempt transactions

$TAXEXEMPT

Total dollar amount of tax exempt transactions

#NOSALES

Total count of No Sale (open drawer) operations performed

(QuickService only)

#ENTREES

Total count of entrees sold

$CASH

Total dollar amount of calculated cash:

+ sales

+ taxes

+ gift certificates sold

- tenders

- comps

- promos

+ not redeemed

+ tip reduction

+ mode charges

$DECLCASH

Total dollar amount of declared cash (TableService only)

$TIPSHAREPAID

Total dollar amount of tipshare paid

$TIPREDUX

Total dollar amount of tip reduction

$AUTOGRAT

Total dollar amount of autogratuity

$AUTOGRATnnnn

Total dollar amount of autogratuity of tender type nnnn

$ROUNDING

Total dollar amount of rounding adjusted total, if using 'round check to

Nickel' option

#SPLITCHECKS

Total count of split checks for this server for this checkout.

DOB

Date of business

EMPLOYEEID

Employee's ID number

FIRSTNAME

Employee's first name

JOBCODEID

Employee's job code ID for the checkout

JOBCODENAME

Employee's job code name for the checkout

LASTNAME

Employee's last name

NICKNAME

Employee's nick name

PRINTTIME

The time the checkout was printed

SHIFTNUMBER

Employee's shift number for the day

SYSTEMDATE

System date

RESTUNITNUMBER

Restaurant's unit number

RESTUNITNAME

Restaurant's name

RESTADDRESSONE

First line of the restaurants' address

RESTADDRESSTWO

Second line of the restaurants' address

RESTPHONENUMBERONE

Restaurants' first phone number

RESTPHONENUMBERTWO

Restaurants' second phone number

STORENUMBER

SuperSite store ID

STORENAME

SuperSite store name

$VIZOR

Total employee contribution to VizorVest^SM investment program

$VIZOROWED

Portion of VizorVest contribution that adds to cash owed

#SVC

Total count of service charges

$SVC

Total amount of service charges

#GST

Total count of GST taxes

$GST

Total amount of GST taxes

#DELIVERY

Total count of delivery orders

$DELCOMM

Amount of delivery commissions

STARTMILEAGE

Starting mileage

ENDMILEAGE

Ending mileage

$ACCTD

Total amount of all petty accounts

$ACCTDnnnn

Total amount of petty account nnnn

CHECKOUT.CFG Rules

The Checkout.cfg uses the following rules:

1.        ( ) + - * / Standard algebraic operators are supported; * and / have a higher precedence than + and -.

2.        When multiplying by a percentage, use a leading zero (for example, use 0.05 instead of .05).

3.        The Checkout.cfg must contain a [DEFAULT] header.� Values listed under this header are listed on all employee checkouts that are not defined elsewhere in a job code section.

4.        Job code specific configurations are preceded by the [JOBCODE:i,j..] header where job codes are separated by commas.� For example, [JOBCODE:1,3,4,7] applies this section of the Checkout.cfg to Job Codes 1, 3, 4, and 7.� If an employee's job code is listed within a JOBCODE label, the data following that label is used to print a customized checkout report for the cob code.� The [DEFAULT] section does not print.� If a JOBCODE label does not include an employee's job code, the DEFAULT section of Checkout.cfg is used to print a customized checkout report for that job code.

5.        The Checkout.cfg may contain as many sections as necessary.

6.        <FILL(c)> inserts a break line composed of the character c.�� Use a single character such as -, _, or =.� For example, <FILL(=)>adds a line of 'equal signs' across the width of the checkout.

7.        All text on the checkout is left justified by default.� Use <CENTER> and <RIGHT> to change the alignment.

Creating the CHECKOUT.CFG

Editing the Checkout.cfg file located in the Data folder using Microsoft Notepad or any other text editor configures the custom checkout information.� Create a new file it does not already exist.

The following is an example of a Checkout.cfg file:

[Default]

<FILL(=)>

<VAL(1:DOB)>

<FILL(=)>

<VAL(1:LASTNAME)>, <VAL(1:NICKNAME)>

<VAL(1:JOBCODENAME)> (<VAL(1:JOBCODEID)>)

<FILL(=)>

<Center> Guests and Checks

Number of Guests: <RIGHT> <VAL(4:#GUESTS)>

Number of Checks: <RIGHT> <VAL(4:#CHECKS)>

Guests per Check: <RIGHT> <VAL(4:#GUESTS/#CHECKS)>

<FILL(=)>

<CENTER> Sales

Total Sales: <RIGHT> <VAL(8:$S)>

Food: <RIGHT> <VAL(7:$S0001)>

Liquor: <RIGHT> <VAL(7:$S0002)>

Beer: <RIGHT> <VAL(7:$S0003)>

Wine: <RIGHT> <VAL(7:$S0004)>

Retail: <RIGHT> <VAL(7:$S0005)>

Memberships: <RIGHT> <VAL(7:$S0006)>

<FILL(=)>

[JOBCODE:4,5]

<FILL(=)>

<VAL(1:DOB)>

<FILL(=)>

<VAL(1:LASTNAME)>, <VAL(1:NICKNAME)>

<VAL(1:JOBCODENAME)> (<VAL(1:JOBCODEID)>)

<FILL(=)>

<Center> Guests and Checks

Number of Guests: <RIGHT> <VAL(4:#GUESTS)>

Number of Checks: <RIGHT> <VAL(4:#CHECKS)>

Guests per Check: <RIGHT> <VAL(4:#GUESTS/#CHECKS)>

<FILL(=)>

<CENTER> Sales

Total Sales: <RIGHT> <VAL(8:$S)>

Food: <RIGHT> <VAL(7:$S0001)>

Liquor: <RIGHT> <VAL(7:$S0002)>

Beer: <RIGHT> <VAL(7:$S0003)>

Wine: <RIGHT> <VAL(7:$S0004)>

Retail: <RIGHT> <VAL(7:$S0005)>

Memberships: <RIGHT> <VAL(7:$S0006)>

<FILL(=)>

<CENTER> Performance

Dessert (Sales): <RIGHT> <VAL(7:$S0014)>

Dessert (Count): <RIGHT> <VAL(3:#S0014)>

Desserts per Guests: <RIGHT> <VAL(3:#S0014/#GUESTS)>

<FILL(=)>

[JOBCODE:2]

<FILL(=)>

<VAL(1:DOB)>

<FILL(=)>

<VAL(1:LASTNAME)>, <VAL(1:NICKNAME)>

<VAL(1:JOBCODENAME)> (<VAL(1:JOBCODEID)>)

<FILL(=)>

<Center> Guests and Checks

Number of Guests: <RIGHT> <VAL(4:#GUESTS)>

Number of Checks: <RIGHT> <VAL(4:#CHECKS)>

Guests per Check: <RIGHT> <VAL(4:#GUESTS/#CHECKS)>

<FILL(=)>

<CENTER> Sales

Total Sales: <RIGHT> <VAL(8:$S)>

Food: <RIGHT> <VAL(7:$S0001)>

Liquor: <RIGHT> <VAL(7:$S0002)>

Beer: <RIGHT> <VAL(7:$S0003)>

Wine: <RIGHT> <VAL(7:$S0004)>

Retail: <RIGHT> <VAL(7:$S0005)>

Memberships: <RIGHT> <VAL(7:$S0006)>

<FILL(=)>

<CENTER> Performance

Alcohol (Sales): <RIGHT> <VAL(7:$S0002+$S0003+$S0004)>

Alcohol (Count): <RIGHT> <VAL(3:#S0002+#S0003+#S0004)>

Liquor (Count): <RIGHT> <VAL(7:#S0002)>

Beer (Count): <RIGHT> <VAL(7:#S0003)>

Wine (Count): <RIGHT> <VAL(7:#S0004)>

Alcohol per Guests (Count): <RIGHT> <VAL(3:((#S0002)+(#S0003)+(#S0004))/(#GUESTS)>

<FILL(=)>

Enabling the Custom Checkout

Custom checkouts are enabled by the existence of values in the Checkout.cfg file.� If enabled, the standard checkout also includes the customized portion.�

You can also perform the following to limit the checkout to only the customized portion (this is a global option that effects all employees):

In versions 4.4x or lower, open Maintenance and select Options/Miscellaneous 1.�� Select the 'Only Print Custom Checkout' option.

In versions 5.0x or higher, open Aloha Manager and select Maintenance/Store Settings/Printing/Employee Checkout Cfg, and select 'Only Print Custom Checkout'.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1059

CDX File vs. TDX Files

CDX File vs. TDX Files

============================================================================

AKBID1060

Created: 18 February 2000

Updated: 9 July 2002

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

Subject: CDX Files vs. Index Files

============================================================================

Summary

ALOHA^� application software uses the .DBF type file format for storing some or all configuration and historical data.� DBF files are easy to manually manipulate, but if you do not update the index (.CDX) files when making manual changes to .DBF files, database related problems could occur.� New functionally using .TDX files introduced in version 5.0x is designed to alleviate these problems.

Information

In Aloha application software versions 4.4x and lower, .CDX files are created when you start Maintenance and only if the .CDX files do not already exist.� If a .CDX file already exists, Maintenance makes no attempt to validate the contents.� Therefore, erroneous .CDX files may also be passed on to the Front-Of-House (FOH) during a refresh or during the End-of-Day (EOD) process.

Aloha application software versions 5.0x and higher ensure the validity of the .CDX files by saving the .DBF file's last write time and the length in a corresponding .TDX file, and comparing them during a refresh, during the EOD process, and when you start Aloha Manager.

Comparing the last write time and the length of the .DBF file to the time and length saved in the corresponding .TDX file does the validity check.� If they differ, it is assumed the .DBF file was modified manually and the .CDX file could be obsolete.�� The .CDX file will be rebuilt.� If the .TDX or the .CDX file is missing, the .CDX and .TDX files will be rebuilt.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

AKBID1015 EOD Process and Errors

AKBID1067 DBUP.EXE and DBCONFIG.EXE

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1060

style='mso-spacerun:yes'>� 2003

Using E-Messenger to Send Aloha Data to a Corporate Office

Using E-Messenger to Send Aloha Data to a Corporate Office

============================================================================

AKBID1061

Created: 30 May 2000

Updated: 22 January 2003

Reviewed: 4 February 2004

Microsoft Windows Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

Subject: Using Enterprise Messenger to Send Aloha Data to a Corporate Office

============================================================================

Summary

The ALOHA^� application software uses Enterprise Messenger (E-Messenger) to send data to a restaurant chain's corporate office via email using Microsoft^� Windows^� Messaging Application Programming Interface (MAPI) compliant clients.� MAPI compliant clients include Microsoft Windows Messaging, Microsoft Outlook^� 97 or greater (configured as a 'Corporate or Workgroup' installation), and Microsoft Exchange Client 5.0 or greater.� Outlook Express is not MAPI compliant.� This document explains using E-Messenger to send an Aloha application software dated folder from a store to a corporate office.�

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

If you are using E-Messenger to send gift certificate information between a store and corporate office, refer to document AKBID1135.� If you are using a Wide-Area-Network (WAN) to send gift certificate information between a store and corporate office, refer to document AKBID1034.

Information

Transferring data from a store to a corporate office requires the MAPI client and E-Messenger installed and configured at each store and the corporate office.� You must install the MAPI client before installing E-Messenger.

Configure the MAPI Client at the Store

Setup an Internet email account with a local Internet access provider, and configure the MAPI client.� If you are using Microsoft Exchange as your MAPI client, double-clicking the Inbox icon on the Microsoft Windows desktop generally starts an installation wizard that guides you through the installation process.�

In order to automate the sending process, the MAPI client must be configured to send and receive mail without requiring any external intervention other than the initial operation to start the send-and-receive-email process.� For example, if the user opens Microsoft Exchange and selects Tools/Deliver Now, Microsoft Exchange must complete the send-and-receive-email process without further intervention.

Consult Microsoft documentation for more information on configuring MAPI clients.

Install E-Messenger at the Store

Install E-Messenger from the Aloha Installation CD, and configure the BackOffice License Manager with the correct user information.

This document is based on E-Messenger version 1.03 SP3.� After installing E-Messenger, ensure version compliance with this document.

After the installation is complete, open E-Messenger, select File/Setup, and enter the password.� Add the store ID to the 'Store ID' text box, and add the corporate office email address to send sales data in the 'Send Packages To' text box.� Verify the email profile information to ensure it is correct.

Refer to the Aloha Enterprise Messenger User Manual for more information on configuring E-Messenger.

Windows NT^� and Windows 2000 assign different MAPI client profiles to each user that logs in.� Ensure you are executing E-Messenger in the context of the correct user.

Configure the SU.EXE Utility at the Store

Users of Windows NT and Windows 2000 must use the SU.EXE for E-Messenger to send and receive email from a command line, such as a Winhook batch file.

As stated previously in this document, Windows NT and Windows 2000 assign different MAPI client profiles to each user.� Tasks executed from a command line (like the Winhook batch file) use the built-in Windows system account, which does not have a profile defined for the MAPI client, and therefore, will not function properly.

Use the SU.EXE utility, developed by Microsoft, as a work-around for this, and it must be installed on all Windows NT and Windows 2000 file servers using E-Messenger.

Perform the following to install the SU.EXE utility:

1.        Download SU.ZIP from the Aloha Technologies FTP site.

2.        Copy SU.EXE and SUSS.EXE to the Windows folder.

3.        Open a command prompt and navigate to the Windows folder.

4.        Run 'SUSS.EXE �INSTALL'.

This installs SU.EXE on the file server.� The correct user account and password is defined later in the Winhook batch file.

Add UNITNUM Variable

The Winhook batch file requires the UNITNUM system environment variable to define the unit number (as defined previously as the store ID in E-Messenger).� Adding it to the system environment variables, rather than the Winhook batch file itself, enables the same Winhook batch to be used at each store.� For example:

SET UNITNUM=1234

Configure the Winhook Batch File at the Store

E-Messenger uses the Winhook batch file (refer to document AKBID1028) to initiate the data transfer.� E-Messenger can also use Windows Schedule Service (refer to document AKBID1047) or BackOffice AutoRun to initiate the file transfer, but only Winhook has the inherent ability to define a dated folder's label (date).

Edit or create the Winhook batch file and add the following information:

The first step in the process.

:STEP01

This step first verifies if the Grind process (refer to document AKBID1016) has completed.� If it has not completed, the batch file skips to STEP02.

IF NOT EXIST %IBERDIR%\%1\GNDDBF30.XXX GOTO STEP02

Compress the sales data in the dated folder to a file labeled EMDATA.ZIP using PKZIP.EXE.� Ensure PKZIP.EXE is in the system's path.

PKZIP %IBERDIR%\%1\EMDATA.ZIP %IBERDIR%\%1\*.*

This command line creates PACKAGE.DAT that defines for E-Messenger what files (EMDATA.ZIP) to send and how to process them on the receiving end (the corporate office).� Besides using the IBERDIR, UNITNUM, and %1 variables, the command line also refers to $CPDIR$, which is a macro used by E-Messenger at the corporate office.� The $CPDIR$ macro is discussed later in this document.� This command line performs the following:

1.        'ECHO � >>' appends all of the instructions listed between the 'ECHO' and '>>' statements to PACKAGE.DAT.

2.        '%IBERDIR%\%1\EMDATA.ZIP' specifies the file, EMDATA.ZIP, to send to the corporate office.

3.        '$CPDIR$\%UNITNUM%\%1' is used by E-Messenger at the corporate office to select the target folder based on the information contained in the $CPDIR$ macro, the UNITNUM variable, and name of the dated folder.

4.        'PKUNZIP �O $CPDIR$\%UNITNUM%\%1\EMDATA.ZIP $CPDIR$\%UNITNUM%\%1' applies PKUNZIP.EXE at the corporate office to extract EMDATA.ZIP into the working folder.� '-O' instructs PKUNZIP.EXE to overwrite any existing files of the same name.� Ensure PKUNZIP.EXE is in the system's path at the corporate office.

5.        'DELETE' instructs E-Messenger to delete PACKAGE.DAT from the hard drive after sending it to the corporate office.

6.        '>> C:\EMAIL\PACKAGE.DAT' defines the location to place PACKAGE.DAT on the store's file server.

ECHO %IBERDIR%\%1\EMDATA.ZIP,$CPDIR$\%UNITNUM%\%1,PKUNZIP �O $CPDIR$\%UNITNUM%\%1\EMDATA.ZIP $CPDIR$\%UNITNUM%\%1,DELETE >> C:\EMAIL\PACKAGE.DAT

The second step in the process shows how stores can also send files not kept in the dated folder, such as labor export files.� In this example, instructions to send and process %IBERDIR%\%1.TXT are also added to PACKAGE.DAT.

:STEP02

This command line verifies if the file exists.� If it does not exist, the batch file skips to STEP03.

IF NOT EXIST %IBERDIR%\%1.TXT GOTO STEP03

This command line adds the instructions to PACKAGE.DAT.

ECHO %IBERDIR%\%1.TXT,$CPDIR$\%UNITNUM%\PAYROLL,,SAVE >> C:\EMAIL\PACKAGE.DAT

The third step in the process.

:STEP03

This command line verifies if the file exists.� If it does not exist, the batch file skips to STEP04.

IF NOT EXIST C:\EMAIL\PACKAGE.DAT GOTO STEP04

If the E-Messenger software is already active, the batch file will not be able to automatically send the package to the corporate office.� To ensure that E-Messenger is not already active, use the CLOSEAPP.EXE utility (refer to document AKBID1012) in the batch file to close E-Messenger before trying to process the package.� You may also want to use this after the files are sent to shut down E-Messenger.

CLOSEAPP.EXE /CLOSE ENTERPRISE

Initialize E-Messenger to send any queued files as specified in PACKAGE.DAT (Windows 95, Windows 98, and Windows Millennium Edition only).

"%IBERDIR%\BACKOFFICE\ENTERPRISE MESSAGING\EMESSENGER.EXE" /AUTO

Set the SU.EXE command line that initializes E-Messenger to send any queued files as specified in PACKAGE.DAT (Windows NT and Windows 2000 only).

SET SU_COMMANDLINE="%IBERDIR%\BACKOFFICE\ENTERPRISE MESSAGING\EMESSENGER.EXE" /AUTO

Run SU.EXE to initialize E-Messenger to send any queued files as specified in PACKAGE.DAT.� In this example, the user name is 'aloha' and the password is 'hello'.� Edit this command line, and insert the user name and password that matches the profile previously set up in E-Messenger (Windows NT and Windows 2000 only).

This command line creates a potential security risk since it exposes the user name and password.� If this is not acceptable, consult SU.TXT (included in SU.ZIP) for more password options.

ECHO hello| SU.EXE aloha

The fourth step in the process.

:STEP04

Finished.

EXIT

Configure the MAPI Client at the Corporate Office

Setup an Internet email account with a local Internet access provider, and configure the MAPI client.� If you are using Microsoft Exchange as your MAPI client, double-clicking the Inbox icon on the Microsoft Windows desktop generally starts an installation wizard that guides you through the installation process.�

In order to automate the sending process, the MAPI client must be configured to send and receive mail without requiring any external intervention other than the initial operation to start the send-and-receive-email process.� For example, if the user opens Microsoft Exchange and selects Tools/Deliver Now, Microsoft Exchange must complete the send-and-receive-email process without further intervention.

Consult Microsoft documentation for more information on configuring MAPI clients.

Install E-Messenger at the Corporate Office

Install E-Messenger from the Aloha Installation CD, and configure the BackOffice License Manager with the correct user information.

This document is based on E-Messenger version 1.03 SP3.� After installing E-Messenger, ensure version compliance with this document.

Refer to the Aloha Enterprise Messenger User Manual for more information on configuring E-Messenger.

Configure $CPDIR$

CPDIR is a macro created in E-Messenger.� The macro specifies the folder on the corporate office computer to process the sent files.� The dollar signs ($) on each side of the label define it as a macro in command lines.

For example, the corporate may have a folder on C: labeled 'STORES'.� Inside the 'STORES' folder is a sub-folder for each store labeled with the store number (for example, C:\STORES\1234).

In this case, perform the following to create a macro at the corporate office to define the target folder:

1.        Open E-Messenger.

2.        Select File/Macro Definitions.

3.        Click 'Add Macro'.

4.        Name the macro 'CPDIR' and give the macro a path of 'C:\STORES'.

5.        Click 'OK'.

When a package is sent from the store, E-Messenger at the corporate office replaces '$CPDIR$' with 'C:\STORES' when processing the package.� The store's subfolder label is defined in PACKAGE.DAT when it is created at the store (UNITNUM)

'CPDIR' is not a required label for the macro.� Users can specify different names as long as the packages from the stores also refer to the different name.

Configure the SU.EXE Utility at the Corporate Office

Users of Windows NT and Windows 2000 must use the SU.EXE for E-Messenger to send and receive email from a command line, such as a .BAT or a .CMD file.

As stated previously in this document, Windows NT and Windows 2000 assign different MAPI client profiles to each user.� Tasks executed from a command line (like the Winhook batch file) use the built-in Windows system account, which does not have a profile defined for The MAPI client, and therefore, will not function properly without the SU.EXE utility.

Perform the following to install the SU.EXE utility:

1.        Download SU.ZIP from the Aloha Technologies FTP site.

2.        Copy SU.EXE and SUSS.EXE to the Windows folder.

3.        Open a command prompt and navigate to the Windows folder.

4.        Run 'SUSS.EXE �INSTALL'.

This installs SU.EXE on the file server.� The correct user account and password is defined in the Winhook batch file.

Configure Windows Schedule Service at the Corporate Office

Create a .CMD (the same as a .BAT file, but with a different extension) for Windows Schedule Service to use, and refer to document AKBID1047 to set Windows Schedule Service to automatically activate the .CMD file.

Edit or create the .CMD file and add the following information:

If the E-Messenger software is already active, the batch file will not be able to automatically receive and process the sent files to the corporate office.� To ensure that E-Messenger is not already active, use the CLOSEAPP.EXE utility (refer to document AKBID1012) in the batch file to close E-Messenger before trying to receive and process the sent files.

CLOSEAPP.EXE /CLOSE ENTERPRISE

Initialize E-Messenger to receive and process the send file (Windows 95, Windows 98, and Windows Millennium Edition only).

"<path to EMESSENGER.EXE>\EMESSENGER.EXE" /AUTO

Set the SU.EXE command line that initializes E-Messenger to receive and process the sent files (Windows NT and Windows 2000 only).

SET SU_COMMANDLINE="<path to EMESSENGER.EXE>\EMESSENGER.EXE" /AUTO

Run SU.EXE to initialize E-Messenger to receive and process the sent files.� In this example, the user name is 'aloha' and the password is 'hello'.� Edit this command line to use the user name and password that matches the profile previously set up in E-Messenger (Windows NT and Windows 2000 only).

This command line creates a potential security risk since it exposes the user name and password.� If this is not acceptable, consult SU.TXT (included in SU.ZIP) for more password options.

ECHO hello| SU.EXE aloha

Finished.

EXIT

E-Messenger Debugging Files

E-Messenger provides a debugging log file to assist users in troubleshooting problems processing packages.� Open E-Messenger, and select File/View Process Log to view the debugging file.

Extended Information

No information.

Caveats

Transferring data from a store to a corporate office requires The MAPI client and E-Messenger installed and configured at each store and the corporate office.� You must install The MAPI client before installing E-Messenger.

This document is based on E-Messenger version 1.03 SP3.� After installing E-Messenger, ensure version compliance with this document.

Windows NT and Windows 2000 assign different MAPI client profiles to each user that logs in.� Ensure you are executing E-Messenger in the context of the correct user.

�

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

The Windows NT and Windows 2000 SU.EXE command line in the store's Winhook batch file creates a potential security risk since it exposes the user name and password.� If this is not acceptable, consult SU.TXT (from SU.ZIP) for more password options.

============================================================================

See also:

Aloha Enterprise Messenger User Manual

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1016 Grind Process and Errors

AKBID1028 Winhook

AKBID1034 Using a WAN and Corporate Gift Certificates

AKBID1047 Microsoft Windows Schedule Service

AKBID1135 Using E-Messenger and Corporate Gift Certificates

AKBID1143 E-Messenger PACKAGE.DAT Files

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1061

�

Property Management Systems

Property Management Systems

============================================================================

AKBID1062

Created: 18 February 2000

Updated: 29 August 2002

Reviewed: 11 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 3.8x � 5.3.x

Subject: The Aloha Application Software PMS Process and Troubleshooting

============================================================================

Summary

The ALOHA^� application software Electronic Draft Capture (EDC) application uses a process of request and answer files to interface with the Front-of-House (FOH) Point-of-Sale (POS) terminals and the Back-of-House (BOH) file server.� The EDC application, in turn, uses a serial or modem connection to interface with Property Management Systems (PMS).� This document explains the PMS authorization process in order to help you better understand and troubleshoot problems with communicating with a PMS.

Information

The PMS Authorization Process

Request and answer files are the basis of FOH interaction with EDC.� EDC automatically knows to process PMS request and answer files if the HASP^� security key has PMS enabled.� When a user performs an action on the FOH, such as applying, adjusting or voiding a PMS payment, the master terminal creates a nnnnnnnn.req file in the PMS folder on the fileserver.�

The EDC program scans the PMS folder for .req files at least once per second.� If a .req file is found, EDC immediately renames it to a .hld file, indicating that processing has begun.�

After EDC processes the request file, the response is written to an .ans file and the .hld file is deleted.� The .ans file is basically identical to the .req file, but the APPROVED field indicates whether the action succeeded and the ERROR field provides additional information.

In addition to writing the response to an .ans file, EDC writes the response to a Txnmmmmm file in the PMS folder.� The Txn files are sequentially numbered and have identical contents as .ans files.� Txn files in a processor directory make up the current PMS batch.

The FOH detects the .ans file, parses the information and deletes the .ans file.

PMS Files

The PMS folder typically resides in the Aloha application software folder (IBERDIR) on the file server.� This default folder is overridden with the PMSPATH environment variable (if used).�

The following table shows the descriptions of the files typically found in the PMS folder:

File

Description

\PMS\PMS.ini

PMS configuration file

\PMS\*.req

Request files from FOH

\PMS\*.hld

FOH requests currently being processed

\PMS\*.ans

Completed requests

\PMS\Txn*.

Txn files making up the current batch for the processor

There is no relationship between the transaction number (as referenced in EDC application and PMS errors) and the like numbered Txn file.� For example, an error message referring to transaction 39 does not link to Txn00039.� The only way of determining the transaction number is to use the batch transaction number shown in the Select Transaction dialog when you adjust or void transactions from the BOH.

�

The following table shows the contents of a .TXN file:

Manually editing or otherwise manipulating TXN files is highly discouraged.� However, it is useful to understand how they work when dealing with problems.

Field

Description

TYPE

Message type

DOB

Date-of-Business (DOB)

DATE

System date

TIME

System time (HH:MM:SS)

TERMINAL

Originating FOH Revenue Center, or BOH

MANAGER

If manager approval was required, who did it

EMPLOYEE

FOH Employee performing the action

TABLE

Name of table or quick service order

CHECK

Check number

PAYMENT

Amount of payment

CARD

Room or customer identification number

EXP

Expiration Date (always 0000)

APPROVED

YES or NO

ERROR

Error text for failed actions

FILENO

Number of the TXN file

MSG1

Message request information.

MSG2

Message request information.

MSG3

Message request information.

MSG4

Message request information.

MSG5

Message request information.

MSG6

Message request information.

MSG7

Message request information.

MSG8

Message request information.

SELECTINFO

Selection field information

SELECTNUM

Selection field ID

PERIOD

Day part

TRANSNUM

Transaction number

GUESTCOUNT

Number of guests

SLSTOTAL1

Sales Category one sales

SLSTOTAL2

Sales Category two sales

SLSTOTAL3

Sales Category three sales

SLSTOTAL4

Sales Category four sales

DISCTOTAL

Discounts against the transaction sales amount.

SERVCHRG1

Manual service charges, tips, or other add-on amounts manually added to the transaction amount.

SERVCHRG2

Automatic service charges, gratuities, or other add-on amounts automatically added to the transaction amount.

TAX1

Tax

TAX2

Unused

TAX3

Unused

TAX4

Unused

PRVPAYMENT

The previous amounts paid against the transaction total exclusive to the amount being posted

CHECKNUM

Check number

CHECKTOTAL

Total sales for the check

PAYMENTID

Unique payment ID

PMSID

PMS Tender ID

TENDERID

Tender ID

End-of-Day Process

The End-of-Day (EOD) process (refer to document AKBID1015) creates a DONE30 file in the PMS folder.� This file prompts EDC to erase all Txn files in order to start a new day.� If the site is a SuperSite, refer to document AKBID3066 for more information on SuperSite PMS settlement.

Once the EOD process clears the Txn files, you cannot use the Aloha application software to edit transactions from the previous day.

Txn files are not saved in a settlement (.stl) file as EDC credit card transactions are.

Environment Variables

EDC supports two environment and command-line variables in regards to PMS.� Refer to document AKBID1010 for more information.

Variable

PMSDIR

Applications

EDCSvr.exe

Description

Defines the PMS folder name inside the IBERDIR.

System Variable Example

SET PMSDIR=<folder name>

Command Line Example

EDCSVR.EXE /PMSDIR <folder name>

Variable

PMSPATH

Applications

EDCSvr.exe

Description

Defines the PMS folder path

System Variable Example

SET PMSPATH=<path>

Command Line Example

EDCSVR.EXE /PMSPATH <path>

Timeouts

To access the following timeouts, open EDC, select Stop POS Processing to disable file processing, and select Parms from the PMS drop-down menu.� Unless instructed otherwise by the Aloha Customer Service Center (CSC), set the PMS timeouts to the following settings:

Type

Default

Timeout

Enquiry

15

Response

15

Message

15

Retries

1

A separate PMS Timeout for the FOH terminals should be set to 45 seconds.� To edit the timeout, perform one of the following based on the version of the Aloha application software:

In versions 4.4x and lower, open Maintenance and select MX/PMS.

In versions 5.0x and higher, open Aloha Manager, and select Maintenance/Store Settings/Hotel.

You should not set the FOH timeout as less than the total BOH timeouts multiplied by the number of retries.� If the FOH timeout is less than the BOH timeouts, the FOH might timeout before the BOH receives the response from the PMS system.� This can cause double posting if the transaction is re-posted from the FOH.

Serial Cable

The PMS interface uses a null-modem serial cable between the Aloha application software file server and the PMS file server.� For best results, use a quality category-5 10-base-T or 100-Base-T cable and use a straight-through wire run.� Let the serial adapters on each end perform the pin conversions, as described in the Serial Cable Pin-Outs section.

The serial cable cannot exceed 150 feet and should not approach any electrical interference.

The serial cable connecting the Aloha application software file server to the PMS file server is just as important as the network cables used throughout the Aloha application software.� Apply the same precautions and rules as you would a network cable.

Serial Cable Pin-outs

The Hilton PMS systems (HPMS and HPMS2) use a different type of serial cable than other PMS systems.� Consult the PMS vendor for the correct cable information.

POS File Server DB9 to PMS DB25

DB9

2

3

5

8

DB25

2

3

7

20

POS File Server DB9 to PMS DB9

DB9

2

3

5

8

DB9

3

2

5

4

POS File Server DB25 to PMS DB25

DB25

2

3

5

7

DB25

3

2

20

7

POS File Server DB25 to PMS DB9

DB25

2

3

5

7

DB9

2

3

4

5

RJ45 to RS232 Adapter Pin-outs

POS File Server DB9 to PMS DB25

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB9

1

2

3

4

5

6

7

8

DB25

-

2

3

-

7

-

-

20

POS File Server DB9 to PMS DB9

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB9

1

2

3

4

5

6

7

8

DB9

-

3

2

-

5

-

-

4

POS File Server DB25 to PMS DB25

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB25

1

2

3

4

5

6

7

8

DB25

-

3

2

-

20

-

7

-

POS File Server DB25 to PMS DB9

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB25

1

2

3

4

5

6

7

8

DB9

-

2

3

-

4

-

5

-

Serial Port Settings

Set the serial ports on the Aloha application software file server and the PMS file server to 9600 baud, no parity, 8 data bits, and 1 stop bit.� The flow control setting does not matter to the Aloha application software.

The Aloha application software is certified with each PMS vendor with these settings.� Different settings can cause errors or double posting.

Troubleshooting

To enable the output of extra debugging information to the Debout.edc file in the TMP folder, open EDC, disable POS processing, select Parms from the PMS drop-down menu and set Debug to 1.

If EDC or the FOH appears 'locked-up', it may be waiting for a response from the PMS system.� Wait for it to time-out before taking any further action.

If there does not appear to be communication between the Aloha POS file server and the PMS file server, check the cable, cable length, connectors and serial port settings (on both sides).� Check Debout.edc for more information.

If the PMS system does not appear to respond to the Aloha application software, ensure the PMS interface is enabled on the PMS system.� Users often disable the interface at night during their EOD routine.

An 'Invalid Posting Code' indicates that Revenue Centers or automatic gratuities are not configured properly in the Aloha application software and/or the PMS system.

An 'Incorrect Room Number' error returned from the PMS system may occur if the PMS system requires additional information with the room number, such a 'R' or 'R/'.� For example, you would use 'R5034' or 'R/5034' instead of '5034'.� Some systems require the room number, a slash and the first two digits of the occupant�s last name (for example, 5034/AB).� Consult the PMS system vendor for more information on the exact room information required.�

If double posts occur, check the BOH and FOH timeouts, and make sure the serial port settings are correct.

Micros Interface 4-Digit Employee Limit

The Micros PMS interface (and therefore, RDP, Springer Miller, HIS, CSS, Fidelio, Fastech and Marriott) only allows for employee numbers up to four digits.� The Aloha application software PMS interface compensates for this in versions 4.410 and higher by only transmitting the last four digits of employee numbers over the four-digit limit.

Extended Information

To record cash payments in the PMS system, configure a 'Cash' tender just as you would a PMS tender, but select the Cash flag.� Set the PMS Room Number to reflect the PMS account for cash income.

To record comps or promotions in the PMS system, set up a 'Comp' or 'Promo' tender just as you would a PMS tender.� Set the PMS Room Number to reflect the PMS account for the comp or promotion.

Caveats

Manually editing or otherwise manipulating Txn files is highly discouraged.�

Set the serial ports on the Aloha application software file server and the PMS file server to 9600 baud, no parity, 8 data bits, and 1 stop bit (the flow control setting does not matter to the Aloha application software).� The Aloha application software is certified with each PMS vendor with these settings.� Different settings can cause errors or double posting.

The serial cable connecting the Aloha application software file server to the PMS file server is just as important as the network cables used throughout the Aloha application software.� Apply the same precautions and rules as you would a network cable.

============================================================================

See also:

Aloha QuickService or TableService User Manual

Aloha Hotel User Manual

AKBID1004 Serial Pin Assignments

AKBID1010 Aloha Application Software System Environment Variables

AKBID1015 EOD Process and Errors

AKBID1020 EDC Process

AKBID1198 Magnetic Stripe Card Information

AKBID3066 SuperSite PMS Settlement

AKBID3303 Enable PMS Tip or Tender Adjustments on Closed Checks

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1062 pinout pinouts

style='mso-spacerun:yes'>� 2003

TCP/IP

TCP/IP

============================================================================

AKBID1063

Created: 20 February 2000

Updated: 27 April 2001

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

Subject: Using TCP/IP with the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software can use the Transmissions Control Protocol/Internet Protocol (TCP/IP or IP) protocol or the NetBEUI protocol for network communication.� This document explains basic TCP/IP usage to assist you in configuring it for use with the Aloha application software.

Information

NetBEUI vs. TCP/IP

The primary benefit of TCP/IP protocol over the NetBEUI protocol is network routing.� You can route and filter TCP/IP network packets enable quicker file transfer, less traffic, and more scalability over a large network.� This enables less interference with other network functionality if the network is not limited to POS use.� Since Aloha application software terminal uses NetBIOS messaging, they must reside on the same subnet.

NetBEUI produces more network traffic than TCP/IP, but it is generally faster over small networks.� Since the difference in speed may be noticeable only when transferring large files, this difference is not perceptible during the normal POS operation.� The NetBEUI protocol is considered an old standard while TCP/IP is the current standard.

IP Addresses

Each member of a network that communicates with IP needs a unique identifier, the IP Address.� There are specific rules governing the assignment of IP addresses, the basics of which are covered here.

The IP Address is organized into four numbers and separated by periods, or 'dots' (e.g.� 200.100.100.100).� Each number can be a value between 0 and 255, but selecting the correct values is critical to having your network work properly.

The IP address actually contains two identifiers: one for the network and one for the specific machine within the network.� The Network ID portion of an IP address will be the same for every machine (host) in a Subnet (explained later).� Looking from left to right, the Network ID is the first part of the address.� For example, if a network has an ID of 200.100.100, two hosts in the same Subnet may have the addresses 200.100.100.101 and 200.100.100.102.

The Network ID will occupy the first one, two or three numbers, depending on the network Class.� Networks are divided into three classes: A, B, and C.� A Class A Network ID uses the first number.� Class B network use the first two numbers, and Class C networks use the first three numbers.� For example:

Class

Network ID Range

Host ID Range

A

1.x.x.x � 254.x.x.x

x.1.1.1 -x.254.254.254

B

1.1.x.x � 254.254.x.x

x.x.1.1 - x.x.254.254

C

1.1.1.x - 254.254.254.x

x.x.x.1 - x.x.x.254

The Internet Network Information Center (InterNIC, www.internic.net) follows specific rules in assigning IP addresses for use on the Internet.� If the network is not connected to the Internet or is blocked from the Internet by a firewall (as most Aloha application software networks are), these numbers are arbitrary and only need a value between 0 and 255.

POS networks are usually Class C.� This means that the first three numbers must be the same value.

The third number (xxx) is a random number specific to the application software.� Different numbers are used between systems since multiple application softwares may be staged on the same network.� For example, one system may use 101 and another may use 102.�

The fourth number (yyy) is defined by the host's use.� Terminal one uses a 1, terminal two uses a 2, and so on.� The file server is assigned 100.� The following is an example of IP address used for a application software:

Host Use

IP Address

File Server

10.100.101.100

Terminal 1

10.100.101.1

Terminal 2

10.100.101.2

Terminal 3

10.100.101.3

Terminal 4

10.100.101.4

Subnets and Subnet Masks

Subnets and Subnet Masks may be applied with IP addressing to screen network traffic from defined IP addresses, but since Aloha application software terminal uses NetBIOS messaging, they must reside on the same subnet.� For this reason, they will not be a in depth discussion in this document.

A Subnet defines the point where the Network ID ends and the Host ID begins.� It is typically found on a Class C network to divide it into smaller groups.� A Subnet of 255.255.255.0 is usually used with the application software.

Dynamic IP Addressing

Dynamic Host Configuration Protocol (DHCP) can be used to assign IP addresses and Subnets.� This enables easier administration since IP assignment is controlled from a central point.� Windows NT 4.0 Server can be configured to provide the DHCP Service.

The size of the network does not warrant the use of DHCP with a typical application software.� If DHCP is used with the Aloha application software, IP Leasing (without expiration) should be enabled to ensure fault tolerance capabilities.

Installing IP

To add TCP/IP to Microsoft^� Windows^� 95, Windows 98, or Windows Millennium Edition (Me), open the Network properties by selecting Start/Settings/Control Panel/Network or right-clicking the Network Neighborhood icon on the desktop and selecting Properties.� If TCP/IP is not a listed component, add it by selecting Add/Protocol/Microsoft and select TCP/IP.� Once TCP/IP is an installed component, select TCP/IP and choose Properties.� Specify the IP address and Subnet under the IP Address tab and choose OK.� Refer to document AKBID1018 for assistance with making TCP/IP the default protocol for the Aloha application software to use.

To add TCP/IP to Microsoft Windows NT^�, open the Network properties by selecting Start/Settings/Control Panel/Network or right-clicking the Network Neighborhood icon on the desktop and selecting Properties.� If TCP/IP is not a listed protocol under the Protocols tab, add it by selecting Add and TCP/IP.� Once TCP/IP has been added, select TCP/IP and choose Properties.� Specify the IP address and Subnet under the IP Address tab and choose OK.� Refer to document AKBID1018 for assistance with making TCP/IP the default protocol for the Aloha application software to use.

To add TCP/IP to Microsoft Windows 2000 or Windows XP, open the Network properties by selecting Start/Settings/Control Panel, and select Network and Dial-up Connections or right-clicking the Network Neighborhood icon on the desktop and selecting Properties.� Right-click on the Local Area Network icon and select Properties.� If TCP/IP is not a listed protocol, add it by selecting Install/Protocol, highlight TCP/IP, and select Add.� Specify the IP address and Subnet by highlighting TCP/IP and selecting Properties.� Refer to document AKBID1018 for assistance with making TCP/IP the default protocol for the Aloha application software to use.

If you are using Windows 2000 or Windows XP, you must enable NetBIOS over TCP/IP by selecting Start/Settings/Control Panel, and selecting Network and Dial-up Connections or right-clicking the Network Neighborhood icon on the desktop and selecting Properties.� Right-click on the Local Area Network icon and select Properties.� Highlight TCP/IP, select Properties/Advanced.� Select Enable NetBIOS Over TCP/IP in the WINS tab.

Extended Information

Multiple Protocols

You can install multiple protocols on the Aloha application software file server and terminals as long as they follow the rules outlined in AKBID1018.

Multiple protocols can slow down the network, but most application software networks do not have enough network traffic for multiple protocols to have any real effect the network.

IP Address Classification

The following are the classifications for different ranges of Network ID's or domains as determined by the InterNIC for use on the Internet.� The address-ranges given would apply to just the first number of the IP Address.

Class

Network ID Range

Host ID Range

A

1.x.x.x - 126.x.x.x

x.1.1.1 -x.254.254.254

B

128.1.x.x - 191.254.x.x

x.x.1.1 - x.x.254.254

C

192.1.1.x - 254.254.254.x

x.x.x.1 - x.x.x.254

The numbers 0 (zero) and 255 in the last (fourth) octet are reserved and cannot be used for a host address.� Additionally, the numbers 127 and 224-254 in the first octet are reserved by InterNIC and should not be used.

Caveats

No information.

============================================================================

See also:

AKBID1018 Network Lana Numbers

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1063 tcp tcpip

�

Tip Out Feature

Tip Out Feature

============================================================================

AKBID1064

Created: 20 April 2000

Updated: 6 June 2001

Reviewed: 5 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Using the Aloha Application Software Tip Out Feature

============================================================================

Summary

The ALOHA^� application software uses the Tip Out feature to track tips (collected by cashiers) that are distributed by cashiers to order entry employees.� This document explains how to configure and use the tip out feature.� In order to enable the tip share functionality, you must create a petty cash account for tip outs to use, assign the petty cash account to the tip out function, and enable the cashier job codes to pay tip outs.

Information

Petty Cash Accounts

Perform the following to create a petty cash account for the tip out feature to use:

In versions 4.4x and lower, open Maintenance, and select System/Petty Accounts.

In versions 5.0x and higher, open Aloha Manager, and select Maintenance/System/Petty Accounts.

Set the name to 'Tip Out', do not assign a tender type, clear 'Affects Deposit', and select Cash Out Account.

Do not use ID number 01 for the tip out petty account.� ID number 01 is the default ID for the cash drawer bank account.

Store Settings

Define the petty cash account for use with the Tip Out feature.

In versions 4.4x and lower, open Maintenance, and select Options/Miscellaneous 1.� Select the Tip Out Account.

In versions 5.0x and higher, open Aloha Manager, and select Maintenance/Store Settings.� Select the Gratuities and Taxes tab from the Financial Group.� Select the Tip Out Account.

Job Codes

Setup the cashier job codes that will distribute tips using tip outs.� Job codes that distribute tips via tip outs must have the Cashier and Allow Tip Out options enabled.

In versions 4.4x and lower, open Maintenance, and select Labor/Job Codes.� Select Cashier on the first page, and Allow Tip Out on Page 2.

In versions 5.0x and higher, open Aloha Manager, and select Maintenance/Labor/Job Codes drop-down menu.� Select Cashier and Allow Tip Outs from the TableService tab.

FOH Functions

Cashiers with both Cashier and Allow Tip Outs enabled in their job code can use the Tip Out button in the Financials section of the Front-of-House (FOH) Manager Functions to distribute tips.

When they select the Tip Out button, they must select the employee to tip out, and a confirmation with the sales and tip information appears.� Select Yes, and the FOH prints a tip out chit.� Only employees with checks containing tips that have been closed by the cashier appear in the list of employees to tip out.

Tip Outs are tracked on the employee checkouts.�

Extended Information

No information.

Caveats

Do not use ID number 1 for the Tip Out Petty Cash Account.� It is the default ID for the cash drawer bank account.

The cashier's job code must have both Cashier and Allow Tips Outs enabled to perform tip outs in the FOH.

============================================================================

See also:

Aloha TableService User Manual

AKBID1053 TableService Order Entry Job Code Options

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1064 tip-out tipout

Aloha Synctime and Windows Time Zone Configuration

Aloha Synctime and Windows Time Zone Configuration

============================================================================

AKBID1065

Created: 22 February 2000

Updated: 5 October 2001

Reviewed: 13 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.301 � 5.3.x

Subject: Using the Aloha Application Software Synctime Feature and Configuring Windows Time Zones

============================================================================

Summary

The ALOHA^� application software uses the Synctime function to synchronize the system time and date between the Back-of-House (BOH) file server and the Front-of-House (FOH) terminals.� This document explains how to enable Synctime and configure the Windows time and date settings for proper Synctime functionality.

Information

When you enable Synctime, CTLSVR.EXE (Control Server) automatically updates the time and date settings on the master terminal to match the file server's system time and date every two hours.� The master terminal, in turn, updates all of the other FOH terminals with the correct time and date.

Restarting Control Server immediately updates the time and date on the master terminal.

If you manually adjust the times on the FOH terminals, start with the master terminal.� Otherwise, the master terminal will immediately update the non-master terminal's time with the existing incorrect time.

Enabling Synctime

In TableService versions 4.4x and lower, enable Synctime in Maintenance by selecting Options/Miscellaneous 2, and selecting 'Run Synctime'.

In QuickService versions 4.4x and lower, edit ALOHA.INI in the NEWDATA folder, and add the line SYNCTIME=TRUE, if it does not already exist.

In versions 5.0x and higher, enable Synctime in Aloha Manager by selecting Maintenance/Store Settings/System/Date/Time, and select 'Synchronize POS Time With Back Office Time'.

Windows Time Settings (Version 4.0x and Lower)

If you are using Aloha versions 4.0x and lower, enable 'Automatically adjust clock for daylight savings changes' in the Windows time and date configuration on the file server if the client is in a time zone that recognizes Daylight Savings Time (DST).

You must configure the FOH terminals to have the same time zone defined as the file server.� The 'Automatically adjust clock for daylight savings changes' option in the Windows time and date configuration does not matter; Synctime will function properly either way.� Clearing this option will prevent the New Clock Settings dialogue box from appearing when the time changes between DST on terminals using Microsoft^� Windows^� 95, Windows 98 and Windows Millennium Edition (Me).

Synctime may not work properly for users of 4.0x in time zones that do not recognize DST.

Windows and Aloha Time Settings (Version 4.2x and Higher)

In Aloha versions 4.2x and higher, select 'Automatically adjust clock for daylight savings changes' on the file server if the client is in a time zone that recognizes DST.

You must configure the FOH terminals to have the same time zone defined as the file server.� Enable 'Automatically adjust clock for daylight savings changes' in the Windows time and date configuration if you are in a time zone that recognizes DST.

If you are using Aloha versions 4.244 and higher in time zones that do not recognize DST, then you must add the line TIMEZONE=NO DST (with a space between NO and DST) to the ALOHA.INI if it does not already exist; otherwise, you should leave this set to the default US DST.� Disable The 'Automatically adjust clock for daylight savings changes' option in the Windows time and date configuration.

International

International clients that recognize DST, but do not follow the U.S. rules for DST, must use Aloha versions 4.244 and higher.� You must add the line TIMEZONE=INTL to the ALOHA.INI, if it does not already exist.� This creates a TIMEZONE.INI file in the Aloha application software DATA folder.� If you change the time zone on the file server, then you must delete the TIMEZONE.INI and restart Control Server in order to create a new TIMEZONE.INI.

If you change the time zone on the file server, but not on the FOH terminals, the FOH terminals may restart several times while updating their time zone.

Enable 'Automatically adjust clock for daylight savings changes' in the Windows time and date configuration on the file server if the client is in a time zone that recognizes DST.

You must configure the FOH terminals to the same time zone defined as the file server.� Select 'Automatically adjust clock for daylight savings changes' in the Windows time and date configuration if you are in a time zone that recognizes DST.

Extended Information

Synctime does not function on systems with both the FOH and BOH on the same computer.� This is not an issue as long as the FOH/BOH computer is the master terminal because the other terminals will synchronize their time with the master, which is also the file server.

Caveats

If you manually adjust the times on the FOH terminals, start with the master terminal.� Otherwise, the Master terminal will immediately update the non-master terminal's time with the existing incorrect time.

The FOH terminals may take up to 60 seconds to recognize the new time when the DST changes.

============================================================================

See also:

Aloha Application Software User Manual

AKBID1125 SuperSite Time Synchronization

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1065 dls match

Demo Aloha with the Aloha Remote Display System

Demo Aloha with the Aloha Remote Display System

============================================================================

AKBID1066

Created: 23 February 2000

Updated: 29 January 2002

Reviewed: 19 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

Subject: Demonstrating the Aloha POS FOH and the Aloha Remote Display System on a Single Computer

============================================================================

Summary

You can use the ALOHA^� application software Front-of-House (FOH) and Back-of-House (BOH) simultaneously with the Aloha Remote Display System (RDS) on the same computer for demonstration purposes.� The two applications may be relocated on the screen or resized to enable easy toggling between them.�

Information

Setup the Application Software

Install the Aloha application software using the Aloha Installation CD, and select the 'Run Front of House and Back of House on same PC' option.� Install the desired database and adjust the POS settings as needed.

After the FOH and BOH are functioning properly, configure the Aloha RDS.

Setup the Aloha RDS

Create a new shortcut for Video.exe.�� The command line will look similar to the following:

%LOCALDIR%\Bin\Video.exe VIDEO 1 /NONET /NOROBUST

The /NONET and /NOROBUST command line variables are only required if you are using Microsoft^� Windows^� 95, Windows 98, or Windows Millennium Edition (Me).� Do not use the NONET and NOROBUST command line variables if you are using Windows NT^�, Windows 2000, Windows XP, or Windows Server 2003.� The /NONET and /NOROBUST disable networking and fault tolerance that can interfere with the FOH.�

'VIDEO 1' defines the RDS device number.

Disabling networking (NONET) and fault tolerance (NOROBUST) will cause bumped order to reappear if the RDS is restarted.

Edit the RDS options in the BOH and select 'Use Touch Screen' to bump orders.

After the FOH, BOH, and RDS are functioning properly, you can adjust the application screen locations and sizes.

Adjust Screen Location and Sizes

Screen size and position variables are available in TableService versions 4.2 and higher, and QuickService versions 5.024 and higher.

You can limit the FOH application size using the ALOHAXRES and ALOHAYRES variables.� For example, even if your screen uses a resolution of 1024x768, you can limit the FOH to a resolution of 640x480.� The enables you to leave other portions of the screen open for the RDS application.

You can adjust the position of the FOH application by using the ALOHALEFT and ALOHATOP variables.� This is measured in pixels.�� For example, the FOH uses a 640x480 resolution and appears in the middle of a screen with 1024x768 resolution using the following command line:

%LOCALDIR%\Bin\Iber.exe /ALOHALEFT 192 /ALOHATOP 144 /ALOHAXRES 640 /ALOHAYRES 480

If you are using Aloha versions 5.0x and lower, you can adjust the RDS window position using the VIDEOX and VIDEOY variables, and adjust the RDS window size using the VIDEOWIDTH and VIDEOHEIGHT variables.� For example, if the FOH application is in the default upper left-hand corner, RDS could share a 1024x768 screen with the following command line:

%LOCALDIR%\Bin\Video.exe VIDEO 1 /VIDEOWIDTH 384 /VIDEOHEIGHT 288 /VIDEOX 640 /VIDEOY 480

If you are using Aloha versions 5.2x and higher, then you can adjust the RDS window size and position using the RDS device configuration in Aloha Manager.

The number of rows and columns displayed on the RDS should be decreased to compensate for the smaller size.

Extended Information

If you are not using a HASP^� security key, refer to document AKBID1173.

Caveats

Disabling networking (NONET) and fault tolerance (NOROBUST) will cause bumped order to reappear if the RDS is restarted.

Screen size and position variables are available in TableService versions 4.2 and higher, and QuickService versions 5.024 and higher.

============================================================================

See also:

Aloha Video User Manual

AKBID1010 Aloha Application Software System Environment Variables

AKBID1165 FOH Screen Resolution Settings

AKBID1173 Demo Aloha without a HASP Key

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1066 demonstrate kds kitchen kvs

DBUP.EXE & DBCONFIG.EXE

DBUP.EXE & DBCONFIG.EXE

============================================================================

AKBID1067

Created: 23 February 2000

Updated: 22 May 2002

Reviewed: 5 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

Subject: Using the DBUP.EXE and DBCONFIG.EXE Utilities

============================================================================

Summary

DBUP.EXE and DBCONFIG.EXE provide the ALOHA^� application software with the capability to upgrade .DBF file and Relational Database (RDB) data.� DBUP.EXE and DBCONFIG.EXE are used to upgrade database files when older files are introduced to a newer version of software or during a software upgrade.� Different versions of DBUP.EXE exist for different versions of the Aloha application software software.� DBCONFIG.EXE is a Graphical-User-Interface (GUI) for DBUP.EXE.

Information

Aloha Manger does automatically updates the database files as Maintenance previous did, but instead relies in DBUP.EXE.� You can use DBUP.EXE and DBCONFGI.EXE to manually update a database.� You can also use DBUP.EXE and DBCONFIG.EXE to update or create RDB tables from DBF files, update or create DBF files from the RDB tables, and update or create CDX files.

DBUP.EXE and DBCONFIG.EXE are found in the Aloha application software BIN folder.

DBUP.EXE and DBCONFIG.EXE do not access or change the transaction log (TRAN.LOG) in any way.

Version Compatibility

The following table lists the released versions of DBUP.EXE and their application.

Utility Version

Database Generation

Aloha Application Software Version

DBUP2.EXE

2

5.0x

DBUP3.EXE

3

5.2x � 5.2.x.x

Command Line Options

DBUP.EXE is controlled by command line parameters.� Use DBUPn.EXE /? to display the parameters.� The parameters can be listed in any order and they are case insensitive.�

The following table lists the command line parameters:

Parameter

Usage

/ALLTABLES

In versions 5.229 and lower, DBUP.EXE updated all of the tables in a RDB, even if the table's schema was not changed.� In versions 5.230 and higher, the default behavior is to only update tables that have changed.� /ALLTABLES is available in versions 5.230 and higher to force DBUP.EXE to update all tables.� This does not affect .DBF-based databases.

/ASSIGNSECURITYLEVEL

Assign Security Levels to Employees.� Must be in 'Attended' Mode.

/ATTENDED

Create Error/Status Messages in a message box.� If this is not used, errors are listed in the debout file if DEBUG is used.

/CDX

Forces rebuilding DBF index (CDX) files.� If specified, this is the only operation performed.� File location is determined by DBFOUTPUT.� In versions 5.2.4.0 and higher, this function is automatically performed with /DBFONLY.

/CDXCHECK

Rebuild DBF index (CDX) files only if required.� If specified, this is the only operation performed.� File location is DBFOUTPUT.

/CENTRALSITE

Specifies data for an Enterprise central site.� Used for building test data sets only.

/CONFIGONLY

Used only with Relational Databases, upgrades current configuration files only, not the historical (GND and HST) tables.

/CREATEDB

Creates and populates a new RDB defined by SQL.INI.� Population is from DBF files defined by DBFOUTPUT.

/CREATEDBF

Creates and populates new DBF files from the current RDB defined by SQL.INI.� Output DBF file location is defined by DBFOUTPUT.� No RDB upgrade is attempted.� Index (CDX) files are automatically recreated.

/DBFINPUT

Current DBF file location.� Defaults to %IBERDIR%\NEWDATA.

/DBFONLY

Upgrade DBF files only.

/DBFOUTPUT

Upgraded DBF file output location.� Defaults to %IBERDIR%\NEWDATA.

/DBONLY

Upgrade Relational Database only.

/DEBUG

Send all messages to DEBOUT.TXT in the TMP folder.� If the TMP folder does not exist, DEBOUT.TXT is placed in C:\.

/ENTERPRISE

Data is for an Enterprise site.� Used for building test data sets only.

/FORCESECURITY

Forces security conversion if errors are encountered during CREATEDB or DBONLY.� This is enabled by default in versions 5.230 and higher.

/FORCEUPGRADE

Forces an upgrade even though it is not required.

/IBERDIR

Location of the Aloha application software folder.� Defaults to C:\ALOHA.

/NODBFCOPY

Does copy DBF files that have not changed.� Enables ID and User number update.

/NOFORCEUPGRADE

Available in versions 5.230 and higher, this disables the /FORCESECURITY option since it is enabled by default in versions 5.230 and higher.

/VERBOSE

Print error and status messages on the screen.� Use with non-attended mode operation.

Using DBUP.EXE

All Aloha software applications check the database version and generation, and they will stop according to the rules below.�

1.        Aloha Manager checks the current data version and prompts the user to automatically upgrade the database if the database configuration version is less than the software version.� It also stops if the database configuration version is greater that the software version.� Aloha Manager does not check the historical database version (e.g.� HST tables or dated folders).

2.        Grind and EDTPUNCH.DLL stop if the historical database version is less or greater than the software version.� The current data version is not checked.

3.        All other components will stop if either database (current or historical) is newer than the corresponding software version.

DBUP.EXE is typically used in one of two instances: upgrading the Aloha application software or repairing corrupted CDX files.

If an upgrade is performed using the Aloha Application Software Installation CD, DBUP.EXE will run automatically if needed.� If a manually upgrading (e.g.� copying a new version to the BIN folder), DBUP.EXE must be manually started.� The following are typical command lines for this procedure:

DBUPn.EXE /DBFONLY /DEBUG /ATTENDED

DBUPn.EXE /CDX /DEBUG /ATTENDED

The latter command line may be used to update the CDX files if they are corrupted.

The FORCEUPGRADE variable is required when upgrading within a version (for example, 5.000 to 5.010).

DBCONFIG.EXE

DBCONFIG.EXE is started one of two ways:

1.        Open Aloha Manager, and select Database Upgrade from the Utilities drop-down menu.

2.        Open Windows Explorer, and double-click DBCONFIG.EXE in the BIN folder.

Extended Information

Return Codes

In addition to providing on screen messaging in /ATTENDED mode, DBUP.EXE returns DOS ERRORLEVEL return-codes to the OS that can be interrogated to determine the success of DBUP.EXE.�

Code

Description

0

Normal return.

1

MFC failed to initialize.

2

Could not read command parameters.

3

Could not read system INI file.

4

Could not read SQL INI file.

5

Invalid RDB type.

6

Could not read DBF version file.

11

Update � Could not open RDB.

12

Update � Conversion is not required.

13

Update � Data source does not exist.

14

Update � Could not build table list.

15

Update � Could not build all foreign keys

16

Update � Could not set or remove 'Select Into'.

17

Update � Could not create all tables.

18

Update � Database population exceptions (errors).

19

Update � File copy error.

21

Create � Could not load IBERSQL.DLL.

22

Create � RDB database already exists.

23

Create � Could not create data source

24

Create � Database creation error.

25

Create � Database open error.

26

Create � Could not create all RDB tables.

27

Create � Could not build all RDB foreign keys.

28

Create � Could not create RDB folder.

29

Create � Database population exceptions (errors).

30

Create � Database deleted by user.

31

Create � Database delete error (database could not be deleted).

33

Upgrade DBF index files error.

34

Error creating DBF files.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1010 Aloha Application Software System Environment Variables

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1067 dbup dbup2 dbup3

�

Scanners and Barcodes

Scanners and Barcodes

============================================================================

AKBID1068

Created: 2 March 2000

Updated: 20 January 2004

Reviewed: 20 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

Subject: Setting up Barcode Scanners for use with the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software uses barcode scanners to scan items, recall checks, and apply promotions.� This document explains barcodes, barcode scanner settings, and the general use of barcode scanners in the Aloha application software.

Information

The Aloha application software supports three types of barcodes: SKU, American scale variable weight, and International barcodes.

SKU barcodes do not consist of weight or price information.� When you scan a SKU barcode, the Aloha application software searches the SKU fields of each item for a match.� You can use SKU barcodes to order items or for promotions.

You can only use 11-digit American scale barcodes for ordering items.� Items priced using an American scale barcode do not require a price defined in the Aloha application software.� The American scale barcodes use the following format:

Usage

Digits

Always '2'

1

Item Number

2, 3, 4, 5, 6 (uses leading zeros)

Check Digit

7

Price

8, 9, 10, 11 (uses leading zeros; there is an implied decimal between digits 9 and 10)

International barcodes, if enabled, do not allow for regular SKU or American scale barcodes.� You can only used them for ordering items.� The 12-digit International barcode uses the following format:

Usage

Digits

Always '2 8'

1, 2

Item Number

3, 4, 5, 6

Check Digit

7

Weight

8, 9, 10, 11, 12 (there is an implied decimal between digits 9 and 10)

International barcodes require item prices in the Aloha application software.

Serial Barcode Scanners

Although you can program most serial-based barcode scanners for use with the Aloha application software, refer to document AKBID1048 for a list of approved hardware.

Always set the barcode scanner options to the default settings before programming a scanner.

Set the serial port and scanner to transmit at 9600 bits per second, 8 data bits, no parity, 1 stop bit, and Xon / Xoff flow control.

Barcode scanner settings and options vary between brands and models, but set the barcode scanner to the following settings if they are available:

Option

Setting

Interface

RS232

Label Identifiers

Off

Prefix

None

Suffix

Carriage Return (CR)

UPC-A Check Digit

Disabled or suppressed

UPC-E Check Digit

Disabled or suppressed

Define the barcode scanner type and port from Terminal Maintenance in the Aloha application software Back-of-House (BOH), and refresh the system.

Once the scanner is defined, various options in later sections of this document define the barcode scanner�s use.

Metrologic MS951

The Metrologic^� MS951 serial barcode scanner uses the following options:

Option

Setting

Interface

RS232

Baud Rate

9600

Data Bits

8

Parity

None

Stop Bit

1

Flow Control

Xon / Xoff

Short Range Activation

On

UPC-A Check Digit

Off

NCR7890

The NCR 7890 serial barcode scanner uses the following options:

Option

Setting

Interface

RS232

Baud Rate

9600

Data Bits

8

Parity

None

Stop Bit

1

Flow Control

RTS / CTS

Label Identifiers

Off

Check Digit

None

Prefix Byte

None

Carriage Return

None

SCANTEAM

The SCANTEAM^� serial barcode scanner uses the following options:

Option

Setting

Interface

RS232

Baud Rate

9600

Data Bits

8

Parity

Even

Stop Bit

1

Flow Control

Xon / Xoff

Symbol Technologies LS1004

The Symbol^� Technologies LS1004 serial barcode scanner uses the following options:

Option

Setting

Interface

RS232

Baud Rate

9600

Data Bits

8

Parity

None

Stop Bit

1

Flow Control

Xon / Xoff

Suffix Carriage Return

On

UPC-A Check Digit

Off

UPC-E Check Digit

Off

Symbol Technologies LS9100

The Symbol^� Technologies LS9100 serial barcode scanner uses the following options:

Option

Setting

Interface

RS232C

Parity

None

Suffix Carriage Return

On

UPC-A Check Digit

Off

UPC-E Check Digit

Off

Keyboard Scanners

The Aloha application software supports keyboard scanners that use '~' as the lead sentinel, and '^' as the end sentinel.� To test the sentinels on a keyboard scanner, scan an item from a command prompt.� The command prompt should display a '~', the barcode number, and a '^'.

You should also disable transmission of the UPC-A and UPC-E check digits.

You can use a keyboard to mimic keyboard scanner by typing '~', the barcode numbers for information, and typing '^'.

You do not need to define the scanner in the Aloha application software since keyboard input into the Front-of-House (FOH) is enabled by default.

POSIFLEX Business Machines CD-2820

The POSIFLEX Business Machines, Inc. CD-2820 keyboard barcode scanner uses the default configuration plus the configuration changes:

Option

Setting

Pre-amble

~

Post-amble

^

UPC-A Check Digit

Off

UPC-E Check Digit

Off

Use the following steps from the user manual to program the scanner for use with the Aloha application software (the following page numbers were correct at the time of this writing):

-          START (front cover of user manual)

-          SET (front cover of user manual)

-          Define Pre-amble=?? (page 22 of user manual)

-          ~ (page 66 of user manual)

-          EXIT (page 66 of user manual)

-          Define Post-amble=?? (page 22 of user manual)

-          ^ (page 63 of user manual)

-          EXIT (page 66 of user manual)

-          UPC-A Check Digit � Not Transmitted (page 28 of user manual)

-          EXIT (page 66 of user manual)

-          UPC-E Check Digit � Not Transmitted (page 29 of user manual)

-          EXIT (page 66 of user manual)

-          END (front cover of user manual)

DB9 to RJ45 Conversions

Most barcode scanners have a DB9 serial connector attachment, but some Point-of-Sale (POS) terminals use RJ45 serial ports.�

Use the following table to attach a DB9-to-RJ45 adapter to a POS terminal with RJ45 serial ports:

Blue

Orange

Black

Red

Green

Yellow

Brown

White

Pin

1

2

3

4

5

6

7

8

Scanning Items

To scan item SKU numbers, define the SKU numbers in the Aloha application software, and scan an item from the order entry screen.�

The following settings may be used when scanning items:

�

Setting

Location in Maintenance

Location in Aloha Manager

Item SKU Numbers

Menu/Items

Maintenance/Menu/Items/Miscellaneous

EAN International Barcodes

Options/International

Maintenance/Store Settings/International/International

Item Price

Menu/Items

Maintenance/Menu/Items/Price

Add PLU/SKU Key to Submenus

Options/Miscellaneous 1/Auto PLU Key

Maintenance/Store Settings/User Interface/Order Screen

Item if� SKU Number is not found

ALOHA.INI - OPENITEMBADSKU

Maintenance/Store Settings/Order Entry/Options

Scanning Checks

Enabling cashiers to scan check barcodes decreases the transaction time, especially if the 'Auto Get Check/Close' option in enabled.�

The barcodes printed on guest checks are a proprietary format.�

The must define a thermal printer as the printer type in the Aloha application software in order to print barcodes on guest checks.� You can also use the OPOS printer type provided that the printer is a thermal printer.

You can use the following settings for scanning checks:

Setting

Location in Maintenance

Location in Aloha Manager

Print Barcode on Check

Options/Print/Guest Checks

Maintenance/Store Settings/Printing/Check Content 2

Auto Get Check/Close

Labor/Job Codes/Page 2

Maintenance/Labor/Job Codes/Job Code

Consolidate Scanned Checks

ALOHA.INI - AUTOCONSOLIDATESCANNEDCHECKS

Maintenance/Store Settings/Order Entry/Tabs and Tables

Scanning Tenders

QuickService only supports scanning tenders in versions 5.3.x.x and higher.

To scan Promotion barcodes, define the SKU numbers in the Aloha application software, and scan a barcode from the tender screen.

The following settings may be used when scanning promotions:

Setting

Location in Maintenance

Location in Aloha Manager

Barcode Range

Payments/Promotions

Maintenance/Payments/Promotions/ Promotions

Troubleshooting

Use the terminal's debugging file (debout) to verify the SKU/PLU number the Aloha application software reads from the barcode scanner.� Some barcode scanners might append a zero or add check-digits (if they are not disabled).

Add the line PRINTBARCODEDEBUG=TRUE to the ALOHA.INI (if it does not already exist) to increase the dubbing information.

Use HyperTerminal to verify communication between the computer and the barcode scanner.� If HyperTerminal does not display the SKU/PLU number, the Aloha application software will not recognize it either.� Conversely, this does not guarantee the Aloha application software will recognize the SKU/PLU number even though HyperTerminal does.

Extended Information

The barcodes printed on guest checks are a proprietary format.�

The must define a thermal printer as the printer type in the Aloha application software in order to print barcodes on guest checks.� You can also use the OPOS printer type provided that the printer is a thermal printer.

Caveats

Always set the barcode scanner options to the default settings before programming a scanner.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1048 Aloha Application Software Hardware and OS Specifications

AKBID1086 Get Check versus Transfer Check

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1068 bar code

Cash Card Device Troubleshooting

Cash Card Device Troubleshooting

============================================================================

AKBID1069

Created: 3 May 2000

Updated: 8 February 2002

Reviewed: 24 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Troubleshooting Cash Card Devices

============================================================================

Summary

This document is designed to assist users supporting cash card devices connected to the ALOHA^� application software.� For more information on cash card device installation and settings, refer to the Aloha Accessories User Manual.

Information

The Aloha application software supports two types of cash card devices: Debitek and InterCard^�.� A third device, Xico, was supported in Aloha application software version 4.0x, but it is no longer supported in 32-bit versions of the Aloha application software (4.2x and higher).

Debout Errors

The Aloha application software Front-of-House (FOH) debouts use the following cash card errors:

Error

Description

0

No error.

1

The serial port is in use by another device.

2

The software attempted to read the device, but it is not open.

3

The software attempted to change the value of the card, but the card has not yet been read.

4

The software cannot find REVAL1.DLL.

5

There is not enough value on the card to satisfy the request.

Cables

Terminal DB9 to Debitek DB25:

Terminal DB9

1

2

3

4

5

6

7

8

9

Debitek DB25

8

3

2

20

7

6

4

5

22

Terminal DB25 to Debitek DB25:

Terminal DB25

8

3

2

20

7

6

4

5

22

Debitek DB25

8

3

2

20

7

6

4

5

22

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

Aloha Accessories User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1069

�

Cash Drawer Checkout

Cash Drawer Checkout

============================================================================

AKBID1070

Created: 8 March 2000

Updated: 12 March 2002

Reviewed: 9 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 4.0x � 5.3.x

Subject: Using the TableService Cash Drawer Checkout

============================================================================

Summary

The ALOHA^� application software features a Cash Drawer Checkout function (resembling an employee checkout) that prints the cash drawer's income and clears the drawer information for the next employee.

Information

Setup

The cash drawer checkout function does not require any Back-of-House (BOH) configuration.� You access the checkout report from the Front-of-House (FOH).� Any employee with Cash Drawer access (as defined in access levels) can perform a cash drawer checkout report.� Refer to the Aloha TableService User Manual for more information on access levels.

Creating Checkouts

The cash drawer checkout is created the first time an employee that is assigned to the cash drawer closes a check, even if they close the check on a different terminal than the terminal to which the cash drawer is connected.

You can de-assign employees from the cash drawer and assign new employees to the cash drawer without clearing the checkout information.

If you reassign an employee to a different cash drawer, a new checkout starts for the new cash drawer if one does not already exist.

The cash drawer's checkout is updated every time an employee that is assigned to the cash drawer closes a check.

To run a checkout report, log in to the FOH using an employee with cash drawer access, select Functions/Financial, and select Cash Drawers.� Highlight an employee assigned to the drawer, and select Checkout.� Even though you are only selecting a single employee, the checkout includes sales from all of the employees assigned to the cash drawer.

Performing a Cash Drawer Checkout does not remove the employee's assignment to the cash drawer.

Clearing Checkouts

If you are using Aloha versions 5.0x and lower, printing the cash drawer checkout report clears the cash drawer checkout.� Further application of the cash drawer checkout report reprints the previous checkout until the employee performs an employee checkout or an employee assigned to the cash drawer closes another sale.

If you are using Aloha versions 5.2x and higher, the FOH prompts you with an option to clear the cash drawer checkout when you run a checkout report.

In any version, once you clear the checkout, employees still assigned to the original drawer accrue a new cash drawer checkout.

Transferring a Checkout

Employees may move from drawer to drawer using the same checkout information if you use the Transfer button.

If multiple employees are assigned to the original cash drawer (besides the transferred employee), both the original cash drawer and the new cash drawer will contain the checkout information from the original drawer.

To transfer an employee, log in to the FOH using an employee with cash drawer access, select Functions/Financial, and select Cash Drawers.� Highlight the employee assigned to the drawer, and select Transfer.� Select the new cash drawer.

If an active checkout is not already attached the selected cash drawer, the checkout report from the original drawer is transferred to the new drawer.� If the selected drawer already has an active checkout, the FOH prompts the user whether or not to transfer the employee without transferring the checkout information.

Extended Information

The Cash Drawer Checkout can utilize the custom checkout features described in AKBID1059.

Caveats

Performing a cash drawer checkout does not remove the employee's assignment to the cash drawer

If multiple employees are assigned to the original drawer besides the employee to transfer, both the original drawer and the new drawer will contain the checkout information from the original drawer.

============================================================================

See also:

Aloha TableService User Manual

AKBID1059 Custom Checkouts

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1070 check-out zero

Coconut Code Export Files

Coconut Code Export Files

============================================================================

AKBID1071

Created: 7 March 2000

Updated: 21 April 2003

Reviewed: 13 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

Subject: Creating Coconut Code Export File with the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software can export labor and sales data to files that are imported by the Coconut Code software.� This document provides an explanation of the export files and automating the export.

Information

The Coconut Code export files are created in the Aloha application software Back-of-House (BOH).� If you are using versions 4.4x or lower, open Control, select Functions and select the appropriate Coconut Code export function.� If you are using versions 5.0x or higher, open Aloha Manager, select Function/Export and select the appropriate Coconut Code export function.� Highlight the day or range of days to export and click OK.�

The Aloha application software creates the export in the Aloha application software folder (for example, C:\ALOHA\CC*.TXT).� The following files are exported with each Aloha application software export function:

Export File

Export Function

Description

CCTIME.TXT

Payroll

Labor hours.

CCPMIX.TXT

Sales Mix

Items sold.

CCSLS.TXT

Daily Sales

Restaurant sales.

CCHOUSE.TXT

Daily Sales

House Account information.� This applies to the Basic House Account functionality, not the BackOffice Accounts Receivable payments.

CCNDPTY.TXT

Daily Sales

Petty Cash transactions that do not effect the deposit (as defined in the Aloha application software).

CCPETTY.TXT

Daily Sales

Petty Cash transactions that effect the deposit (as defined in the Aloha application software).

CCGCREDM.TXT

Daily Sales

Gift Certificates redeemed.� This applies to both the Basic Gift Certificate functionality, and the BackOffice Gift Certificate functionality.

CCGCSOLD.TXT

Daily Sales

Gift Certificates sold.� This applies to both the Basic Gift Certificate functionality, and the BackOffice Gift Certificate functionality.

Automation

You can automate the process of creating export files and moving them to the correct Coconut Code folder using Winhook (refer to document AKBID1028 and AKBID1038).� Contact your Coconut Code representative for the correct Coconut Code folder to use.

To create the Payroll export file, add the following command line to your Winhook batch file:

%IBERDIR%\BIN\RPT.EXE /DATE %1 /R1

To create the Sales Mix export file, add the following command line to your Winhook batch file:

%IBERDIR%\BIN\RPT.EXE /DATE %1 /R2

To create the Daily Sales export files, add the following command line to your Winhook batch file:

%IBERDIR%\BIN\RPT.EXE /DATE %1 /R3

To move the files to the Coconut Code folder, add the following line to the Winhook batch file, replacing x with the location Coconut Code imports from:

COPY %IBERDIR%\CC*.TXT C:\x

The Daily Sales export function will prompt the user to enter a deposit amount if the deposit was not previously entered.� Refer to document AKBID1028 for information on creating zero amount deposits in with Winhook.

Extended Information

All Coconut Code export files are ASCII Comma Separated Value (CSV) fields.

CCSLS.TXT

Description

Data Type

Description

Text

Amount

Numeric

Count

Numeric

CCGCSOLD.TXT

Description

Data Type

Certificate Number

Text

Certificate Amount

Numeric

CCGCREDM.TXT

Description

Data Type

Certificate Number

Text

Certificate Amount

Numeric

CCPETTY.TXT

Description

Data Type

Account Name

Text

Total Amount

Numeric

Number Transactions

Numeric

CCNDPTY.TXT

Description

Data Type

Account Name

Text

Total Amount

Numeric

Number Transactions

Numeric

CCHOUSE.TXT

Description

Data Type

Account Name/Number

Text

Check ID

Numeric

Date

Text

Amount

Numeric

CCPMIX.TXT

Description

Data Type

Item ID

Numeric

Number Sold

Numeric

Total Sales

Numeric

Price

Numeric

CCTIME.TXT

Description

Data Type

Employee ID or Employee Export ID

Numeric

Job Code ID or Job Code Export ID

Numeric

In Date

Text

In Time

Text

Out Date

Text

Out Time

Text

Break Minutes

Numeric

Tips

Numeric

Gross Sales

Numeric

Pay Rate

Numeric

Caveats

No information.

============================================================================

See also:

AKBID1028 Winhook

AKBID1038 Report Command Line Parameters

AKBID1047 Microsoft Windows NT/Windows 2000 Schedule Service

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1071

Electronic Coin Dispensers

Electronic Coin Dispensers

============================================================================

AKBID1072

Created: 10 March 2000

Updated: 31 July 2000

Reviewed: 4 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, Table Service

Aloha POS Versions: 3.402 � 5.3.x

Subject: Using Electronic Coin Dispensers with the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software supports two types of coin dispensers: the Telequip TRANSACT, and the NCR 2010.� This document explains the communication configuration for each device.

Information

Perform the following to define a coin dispenser in the Aloha application software:

In versions 4.4x and lower, open Maintenance, and select Terminals from the System drop-down menu.� Select the terminal that the coin dispenser is connected to, and define the type and COM port in the Coin Changer section.� Refresh the system.

In versions 5.0x and higher, open Aloha Manager, and select Hardware/Terminals from the Maintenance drop-down menu.� Select the terminal that the coin dispenser is connected to, and define the type and COM port in the Coin Changer section.� Refresh the system.

Telequip TRANSACT

Use the following DIP switch settings:

Switch

Setting

1

Off

2

On

3

Off

4

Off

Use the following pin-outs on the female DB9 connector:

Pin

Wire

1

Unused

2

Brown

3

Orange

4

Jumper with pin 6

5

Green

6

Jumper with pin 4

7

Jumper with pin 8

8

Jumper with pin 7

9

Unused

Set the serial port on the terminal to the following settings:

Option

Setting

Bits per second

9600

Data bits

7

Parity

Even

Stop bits

1

Flow control

Xon / Xoff

NCR 2010

The NCR 2010 comes with the correct pin-outs, and it uses the following serial port settings:

Option

Setting

Bits per second

1200

Data bits

8

Parity

No

Stop bits

2

Flow control

Xon / Xoff

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha Application Software User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1072 change db-9 pinout pinouts

Using Aloha Without Enabling Administrator Permissions

Using Aloha Without Enabling Administrator Permissions

============================================================================

AKBID1073

Created: 18 April 2002

Updated: 15 September 2003

Reviewed: 1 March 2004

Microsoft Windows Versions: Windows NT, Windows 2000, Windows XP

Aloha Products: QuickService, TableService, BackOffice

Aloha POS Versions: 5.036 � 5.0x, 5.210 � 5.3.x

Subject: Using Aloha Without Enabling Administrator Permissions for the Local User

============================================================================

Summary

The ALOHA^� application software requires you enable limited or full access to specific registry keys if you are using Microsoft^� Windows NT^�, Windows^� 2000, Windows XP, or Windows Server 2003 on the file server or FOH terminals and are not assigning administrative rights to the local user.

Information

Install the Aloha application software Back-of-House (BOH) or Front-of-House (FOH) using the appropriate Aloha Knowledge Base document prior to performing the steps listed in this document.

The incorrect use of the Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.

Back-of-House (Windows NT only)

To enable the BOH to function on a Windows NT-based file server when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the file server, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_CLASSES_ROOT\AppID\ 583B6E82-64F1-11D1-8EF3-0040054AB0A4 key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Full Control and click OK to close the Registry Key Permissions window.

Highlight the HKEY_CLASSES_ROOT\AppID\ 81DD90A1-CF22-11D1-A84F-0080AD1C6910 key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Full Control and click OK to close the Registry Key Permissions window.

Highlight the HKEY_CLASSES_ROOT\AppID\ 5BAA0737-985E-11d3-8AF0-0090270D3229 key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Full Control and click OK to close the Registry Key Permissions window.

Highlight the HKEY_CLASSES_ROOT\AppID\ 0CAA634F-33F4-11D3-95B8-00104BC81D62 key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Full Control and click OK to close the Registry Key Permissions window.

Highlight the HKEY_CLASSES_ROOT\AppID\ 5503AB9C-9B77-11D3-9151-00105A005BB7 key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Full Control and click OK to close the Registry Key Permissions window.

Highlight the HKEY_CLASSES_ROOT\AppID\ 90E3D096-E8AB-11D3-80DB-00C04F06E1D7 key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Full Control and click OK to close the Registry Key Permissions window.

Highlight the HKEY_CLASSES_ROOT\AppID\ D756033B-FB53-11D3-80F7-00C04F06E1D7 key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Full Control and click OK to close the Registry Key Permissions window.

Highlight the HKEY_CLASSES_ROOT\AppID\ 94C39746-80F7-11D3-913C-00105A005BB7 key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Full Control and click OK to close the Registry Key Permissions window.

Highlight the HKEY_CURRENT_USER\SOFTWARE\Aloha Technologies key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Special Access to open the Special Access window and enable the following access:

Query Value

Set Value

Create Subkey

Enumerate Subkeys

Notify

Delete

Read Control

Click OK to close the Special Access window and click OK to close the Registry Key Permissions window.

Highlight the HKEY_LOCAL_MACHINE\SOFTWARE key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Special Access to open the Special Access window and enable the following access:

Query Value

Set Value

Create Subkey

Enumerate Subkeys

Notify

Delete

Read Control

Click OK to close the Special Access window and click OK to close the Registry Key Permissions window.

Select Registry/Exit to close the Windows Registry Editor.

Back-of-House (Windows 2000, Windows XP, or Windows Server 2003)

To enable the BOH to function on a Windows 2000, Windows XP, or Windows Server 2003-based file server when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the file server, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_CLASSES_ROOT\AppID\583B6E82-64F1-11D1-8EF3-0040054AB0A4 key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, change the access type to Full Control and click OK to close the Permissions window.

Highlight the HKEY_CLASSES_ROOT\AppID\ 81DD90A1-CF22-11D1-A84F-0080AD1C6910 key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, change the access type to Full Control and click OK to close the Permissions window.

Highlight the HKEY_CLASSES_ROOT\AppID\ 5BAA0737-985E-11d3-8AF0-0090270D3229 key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, change the access type to Full Control and click OK to close the Permissions window.

Highlight the HKEY_CLASSES_ROOT\AppID\ 0CAA634F-33F4-11D3-95B8-00104BC81D62 key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, change the access type to Full Control and click OK to close the Permissions window.

Highlight the HKEY_CLASSES_ROOT\AppID\ 5503AB9C-9B77-11D3-9151-00105A005BB7 key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, change the access type to Full Control and click OK to close the Permissions window.

Highlight the HKEY_CLASSES_ROOT\AppID\ 90E3D096-E8AB-11D3-80DB-00C04F06E1D7 key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, change the access type to Full Control and click OK to close the Permissions window.

Highlight the HKEY_CLASSES_ROOT\AppID\ D756033B-FB53-11D3-80F7-00C04F06E1D7 key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, change the access type to Full Control and click OK to close the Permissions window.

Highlight the HKEY_CLASSES_ROOT\AppID\ 94C39746-80F7-11D3-913C-00105A005BB7 key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, change the access type to Full Control and click OK to close the Permissions window.

Highlight the HKEY_CURRENT_USER\SOFTWARE\Aloha Technologies key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, click Advanced, select Users (or whichever group represents the local user) from the Permissions Entries list, click View/Edit and enable the following access:

Query Value

Set Value

Create Subkey

Enumerate Subkeys

Notify

Delete

Read Control

Click OK to close the Permissions window, click OK to close the Access Control Settings window and click OK to close the Permissions window.

Highlight the HKEY_LOCAL_MACHINE\SOFTWARE key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, click Advanced, select Users (or whichever group represents the local user) from the Permissions Entries list, click View/Edit and enable the following access:

Query Value

Set Value

Create Subkey

Enumerate Subkeys

Notify

Delete

Read Control

Click OK to close the Permissions window, click OK to close the Access Control Settings window and click OK to close the Permissions window.

Select Registry/Exit to close the Windows Registry Editor.

Front-of-House (Windows NT Only)

To enable the FOH to function on a Windows NT-based terminal when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the local terminal, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_CLASSES_ROOT\AppID\29BFF798-661E-11d3-95D5-00104BC81D62 key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Full Control and click OK to close the Registry Key Permissions window.

Highlight the HKEY_LOCAL_MACHINE\SOFTWARE key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Special Access to open the Special Access window and enable the following access:

Query Value

Set Value

Create Subkey

Enumerate Subkeys

Notify

Delete

Read Control

Click OK to close the Special Access window and click OK to close the Registry Key Permissions window.

Select Registry/Exit to close the Windows Registry Editor.

Front-of-House (Windows 2000, Windows XP, or Windows Server 2003)

To enable the FOH to function on a Windows 2000, Windows XP, or Windows Server 2003-based terminal when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the local terminal, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_CLASSES_ROOT\AppID\29BFF798-661E-11d3-95D5-00104BC81D62 key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, change the access type to Full Control and click OK to close the Permissions window.

Highlight the HKEY_LOCAL_MACHINE\SOFTWARE key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, click Advanced, select Users (or whichever group represents the local user) from the Permissions Entries list, click View/Edit and enable the following access:

a.        Query Value

b.       Set Value

c.        Create Subkey

d.       Enumerate Subkeys

e.        Notify

f.         Delete

g.       Read Control

Click OK to close the Permissions window, click OK to close the Access Control Settings window and click OK to close the Permissions window.

Select Registry/Exit to close the Windows Registry Editor.

Aloha Inventory Control (Windows NT Only)

To enable Aloha Inventory Control to function on a Windows NT-based file server when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the local terminal, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_LOCAL_MACHINE\Software\Fastech Software key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Full Control and click OK to close the Registry Key Permissions window.

Highlight the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths\EventView.exe key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Full Control and click OK to close the Registry Key Permissions window.

Click OK to close the Registry Key Permissions window.

Select Registry/Exit to close the Windows Registry Editor.

Aloha Inventory Control (Windows 2000, Windows XP, or Windows Server 2003)

To enable Aloha Inventory Control to function on a Windows 2000, Windows XP, or Windows Server 2003-based file server when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the local terminal, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_LOCAL_MACHINE\Software\Fastech Software key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, change the access type to Full Control and click OK to close the Permissions window.

Highlight the HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\App Paths\EventView.exe key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, change the access type to Full Control and click OK to close the Permissions window.

Click OK to close the Permissions window.

Select Registry/Exit to close the Windows Registry Editor.

Aloha Delivery/Frequent Buyer (Windows NT Only)

To enable Aloha Delivery/Frequent Buyer to function on a Windows NT-based file server when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the local terminal, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_LOCAL_MACHINE\Software\Fastech Software key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Full Control and click OK to close the Registry Key Permissions window.

Click OK to close the Permissions window.

Select Registry/Exit to close the Windows Registry Editor.

Aloha Delivery/Frequent Buyer (Windows 2000, Windows XP, or Windows Server 2003)

To enable Aloha Delivery/Frequent Buyer to function on a Windows 2000, Windows XP, or Windows Server 2003-based file server when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the local terminal, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_LOCAL_MACHINE\Software\Fastech Software key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, change the access type to Full Control and click OK to close the Permissions window.

Click OK to close the Permissions window.

Select Registry/Exit to close the Windows Registry Editor.

Aloha E-Messenger (Windows NT Only)

To enable Aloha E-Messenger to function on a Windows NT-based file server when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the local terminal, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_LOCAL_MACHINE\Software\Fastech Software key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Full Control and click OK to close the Registry Key Permissions window.

Highlight the HKEY_LOCAL_MACHINE\Software\Microsoft\Exchange\Exchange Provider key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Full Control and click OK to close the Registry Key Permissions window.

Click OK to close the Permissions window.

Select Registry/Exit to close the Windows Registry Editor.

Aloha E-Messenger (Windows 2000, Windows XP, or Windows Server 2003)

To enable Aloha E-Messenger to function on a Windows 2000, Windows XP, or Windows Server 2003-based file server when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the local terminal, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_LOCAL_MACHINE\Software\Fastech Software key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, change the access type to Full Control and click OK to close the Permissions window.

Highlight the HKEY_LOCAL_MACHINE\Software\Microsoft\Exchange\Exchange Provider key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, change the access type to Full Control and click OK to close the Permissions window.

Click OK to close the Permissions window.

Select Registry/Exit to close the Windows Registry Editor.

Aloha BackOffice Automation Scripts (Windows NT Only)

To enable Aloha BackOffice Automation Scripts to function on a Windows NT-based file server when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the local terminal, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_LOCAL_MACHINE\Software\Fastech Software key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Full Control and click OK to close the Registry Key Permissions window.

Click OK to close the Permissions window.

Select Registry/Exit to close the Windows Registry Editor.

Aloha BackOffice Automation Scripts (Windows 2000, Windows XP, or Windows Server 2003)

To enable Aloha BackOffice Automation Scripts to function on a Windows 2000, Windows XP, or Windows Server 2003-based file server when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the local terminal, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_LOCAL_MACHINE\Software\Fastech Software key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, change the access type to Full Control and click OK to close the Permissions window.

Click OK to close the Permissions window.

Select Registry/Exit to close the Windows Registry Editor.

Aloha Accounts Receivable (Windows NT Only)

To enable Aloha Accounts Receivable to function on a Windows NT-based file server when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the local terminal, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_LOCAL_MACHINE\Software\Fastech Software key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Full Control and click OK to close the Registry Key Permissions window.

Click OK to close the Permissions window.

Select Registry/Exit to close the Windows Registry Editor.

Aloha Accounts Receivable (Windows 2000, Windows XP, or Windows Server 2003)

To enable Aloha Accounts Receivable to function on a Windows 2000, Windows XP, or Windows Server 2003-based file server when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the local terminal, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_LOCAL_MACHINE\Software\Fastech Software key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, change the access type to Full Control and click OK to close the Permissions window.

Click OK to close the Permissions window..

Select Registry/Exit to close the Windows Registry Editor.

Aloha CIM/MAS (Windows NT Only)

To enable Customer Information Management/Meal Accountability System (CIM/MAS) to function on a Windows NT-based file server when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the local terminal, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_LOCAL_MACHINE\Software\Fastech Software key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Full Control and click OK to close the Registry Key Permissions window.

Click OK to close the Permissions window.

Select Registry/Exit to close the Windows Registry Editor.

Aloha CIM/MAS (Windows 2000, Windows XP, or Windows Server 2003)

To enable Customer Information Management/Meal Accountability System (CIM/MAS) to function on a Windows 2000, Windows XP, or Windows Server 2003-based file server when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the local terminal, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_LOCAL_MACHINE\Software\Fastech Software key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, change the access type to Full Control and click OK to close the Permissions window.

Click OK to close the Permissions window.

Select Registry/Exit to close the Windows Registry Editor.

Aloha Corporate Inventory Reporting (Windows NT Only)

To enable Aloha Corporate Inventory Reporting to function on a Windows NT-based file server when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the local terminal, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_LOCAL_MACHINE\Software\Fastech Software key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Full Control and click OK to close the Registry Key Permissions window.

Click OK to close the Permissions window.

Select Registry/Exit to close the Windows Registry Editor.

Aloha Corporate Inventory Reporting (Windows 2000, Windows XP, or Windows Server 2003)

To enable Aloha Corporate Inventory Reporting to function on a Windows 2000, Windows XP, or Windows Server 2003-based file server when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the local terminal, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_LOCAL_MACHINE\Software\Fastech Software key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, change the access type to Full Control and click OK to close the Permissions window.

Click OK to close the Permissions window.

Select Registry/Exit to close the Windows Registry Editor.

Aloha Gift Certificate Manager (Windows NT Only)

To enable Aloha Gift Certificate Manager to function on a Windows NT-based file server when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the local terminal, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_LOCAL_MACHINE\Software\Fastech Software key.

Select Security/Permissions.

Select Everyone from the name list, change the access type to Full Control and click OK to close the Registry Key Permissions window.

Click OK to close the Permissions window.

Select Registry/Exit to close the Windows Registry Editor.

Aloha Gift Certificate Manager (Windows 2000, Windows XP, or Windows Server 2003)

To enable Aloha Gift Certificate Manager to function on a Windows 2000, Windows XP, or Windows Server 2003-based file server when the local user does not have administrative access, perform the following in the registry to enable access to specific keys:

To open the Windows Registry Editor on the local terminal, select Start/Run, type REGEDT32, and click OK.

Highlight the HKEY_LOCAL_MACHINE\Software\Fastech Software key.

Select Security/Permissions if you are using Windows 2000 or select Edit/Permissions if you are using Windows XP.

Select Users (or whichever group represents the local user) from the name list, change the access type to Full Control and click OK to close the Permissions window.

Click OK to close the Permissions window.

Select Registry/Exit to close the Windows Registry Editor.

Extended Information

Since the Aloha application software attempts to synchronize the time on the FOH terminals with the BOH file server, you must ensure that the Windows user has permission to change the local time.� This permission is not granted by default to local users without administrative access.

Caveats

The incorrect use of the Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.

============================================================================

See also:

AKBID1006 Configuring Windows User and Share Permissions for Aloha

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1073 log login logon

�

OPOS

OPOS

============================================================================

AKBID1074

Created: 1 March 2000

Updated: 16 September 2003

Reviewed: 10 December 2003

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.222 � 5.3.x

Subject: Using OPOS Hardware Driver with the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software is compatible with OLE for Retail Point-of-Sale (OPOS) device drivers for cash drawers, line (customer or rear) displays, magnetic stripe readers (MSR), and printers.� This document explains how to configure OPOS devices in the Aloha application software.

Information

OPOS is an industry standard created by a consortium of NCR, Microsoft^�, Epson, and PSI/ICL that enables a common hardware interface in a Win32 environment.� In theory, all hardware that has OPOS drivers will function properly with Point-of-Sale (POS) software designed to interface with OPOS drivers.� This enables POS software developers to create a single interface to multiple types, brands, and models of hardware.

The hardware manufacturer provides the OPOS driver software, and you must install it on the local computer (terminal) before the Aloha application software can interact with it.� The Aloha application software writes to the OPOS software, which, in turn, sends the information to the hardware.

Aloha Technologies does not provide OPOS software.� You must obtain the software from the hardware manufacturer.

OPOS Software Configuration

Install the OPOS software according to the manufacturer's instructions.

Most manufacturers offer utilities for testing the OPOS software with the hardware.�

If the hardware does not work with the OPOS testing utility, the hardware will not work with the Aloha application software.

Configuring the Aloha Application Software

When configuring a cash drawer, line display, MSR, or printer in the Aloha application software Back-of-House (BOH), select OPOS as the hardware type within the Aloha application software device configuration screen.

If you select OPOS as the hardware type, the OPOS Name field becomes active.� The device's OPOS name is found in the operating system's (OS) registry, and the OPOS name is case sensitive.

The incorrect use of the Microsoft Windows^� Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system. Use this tool at your own risk.�

To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

Path out HKEY_LOCAL_MACHINE\SOFTWARE\OLEforRetail\ServiceOPOS.� Open the folder coinciding with the type of hardware (for example, CashDrawer, LineDisplay, MSR, and so on).� Inside each hardware-type folder is a separate folder for each specific device within the category.� The name of the folder is the name to use in the Aloha application software.� NCRMSR.1 and NCRCashDrawer.1 are examples of an OPOS name.

Select Registry/Exit to exit the Windows Registry Editor.

If the OLEforRetail folder does not exist in the registry, then you did not properly configure the OPOS software.

If you are configuring an OPOS printer-fired cash drawer, set the cash drawer to OPOS in the Aloha application software, and configure the cash drawer in the OPOS software to the same COM port as the printer.

Known Hardware Restrictions and Miscellaneous Information

Hardware

Notes

CBM CBM-1000 Type II

Requires OPOS 1.6.001 or higher.

CBM iDP3240

Requires OPOS 1.6.001 or higher.

Epson TM-U200

TM-U210 drivers must be used to print in red.

Epson TM-U325

Only the receipt printing works, not the slip printing.

Epson TM-U375

Only the receipt printing works, not the slip printing.

Epson TM-L60II

Cannot print labels.

Epson TM-U925

Only the receipt printing works, not the slip printing.

Epson TM-U950

Only the receipt printing works, not the slip printing.

Epson TM-H5000/TM-H5000II

Only the receipt printing works, not the slip printing.

Epson TM-295

Works with Aloha versions 5.2.4.x and higher.

Epson TM-U300

Does not return the printer status through OPOS.

Epson TM-U590

Does not work at all with the Aloha application software.

Epson TM-T80

Does not return the printer status through OPOS.

IBM SureMark 4610

Requires Aloha version 5.026 or higher and IBM OPOS version 1.5.0 or higher.� If you are using IBM OPOS 1.4.4, the patch included in 1.5.0 is available from Aloha Technologies.

Misc.� Cash Drawers

You may need to adjust the cash drawer status polarity to enable proper functionality for some cash drawers and OPOS software.� If the polarity is not set properly, the OPOS software (and the Aloha application software) will list the cash drawer as closed when it is open and vice versa.

Magnetic Stripe Readers

If you are using an OPOS MSR with Aloha application software versions 5.208 and lower, the Aloha application software only reads magnetic stripes with information on both track one and track two, or with information only on track two (enable Track Two Only in Aloha Manager).� Aloha application software versions 5.036 and lower� and versions 5.022 through 5.208 do not read magnetic stripes with information only on track one.� Versions 5.037 through 5.0x and 5.209 and higher read track one only, track two only and both track one and track two by default (do not enable Track Two Only in Aloha Manager).

POSIFLEX Business Machines, Inc. PP7000S103

You must use OPOS 3.13PP.3.8 or higher and firmware 5.6 or higher.

Star Micronics SP542MC

In order to make the printer function following a Windows restart, you must set memory switch six in the printer's ROM to a value of 1000 (hex).� Contact Star Micronics support for instructions and more information.� If you do not configure this memory switch, then you might have to cycle the printer's power each time you restart Windows in order for the printer to function.

Extended Information

OPOS Error Return Codes

The following is a list of OPOS error return code descriptions:

Error Code

Error

Description

100

OPOS_SUCCESS

Successful OPOS operation

101

OPOS_E_CLOSED

Attempting to access a closed device

102

OPOS_E_CLAIMED

Device is claimed by another process

103

OPOS_E_NOTCLAIMED

Device has not been claimed by this process

104

OPOS_E_NOSERVICE

Cannot communicate with device (usually a configuration issue)

105

OPOS_E_DISABLED

Device is disabled

106

OPOS_E_ILLEGAL

Attempted an unsupported operation

107

OPOS_E_NOHARDWARE

Device is not connected or powered on

108

OPOS_E_OFFLINE

Device is offline

109

OPOS_E_NOEXIST

File name or value does not exist

110

OPOS_E_EXISTS

File name or value already exists

111

OPOS_E_FAILURE

Although the device is functioning properly, it can not perform the requested procedure

112

OPOS_E_TIMEOUT

Timed out waiting for response or sending a response

113

OPOS_E_BUSY

Device is busy

OPOS Printer Cables

Most OPOS printers use the following cable pin-outs:

Orange

Black

Red

Green

Yellow

Brown

White

Terminal DB9

2

3

4

5

6

7

8

Printer DB25

2

3

6

7

20

5

4

Orange

Black

Red

Green

Yellow

Brown

White

Terminal DB9

2

3

4

5

6

7

8

Printer DB9

3

2

6

5

4

8

7

Orange

Black

Red

Green

Yellow

Brown

White

Terminal DB25

3

2

20

7

6

4

5

Printer DB25

2

3

6

7

20

5

4

Orange

Black

Red

Green

Yellow

Brown

White

Terminal DB25

3

2

20

7

6

4

5

Printer DB9

3

2

6

5

4

8

7

Caveats

Aloha Technologies does not provide OPOS software.� You must obtain the software from the hardware manufacturer.

If the hardware does not work with the OPOS testing utility, the hardware will not work with the Aloha application software.

The OPOS name is case sensitive.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1074 pinouts

style='mso-spacerun:yes'>� 2003

NetBIOS and the Aloha Application Software

NetBIOS and the Aloha Application Software

============================================================================

AKBID1075

Created: 26 April 2000

Updated: 12 October 2000

Reviewed: 9 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Interaction Between NetBIOS and the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software uses the Network Basic Input/Output System (NetBIOS) protocol for network communications.� This document explains the NetBIOS protocol and how the Aloha application software interacts with it.

Information

IBM^� developed the NetBIOS protocol as an open network protocol for computers, and published a NetBIOS programming interface to enable developers to use the NetBIOS protocol.

The Aloha application software was originally developed in 1992 using the NetBIOS interface, since it was the only network programming interface supported by Microsoft^� Windows^� at the time.� The NetBIOS programming interface originally only worked with the NetBIOS Extended User Interface (NetBEUI) protocol, but soon Microsoft added support for NetBIOS over TCP/IP (NetBT) and NetBIOS over IPX/SPX.� The Aloha application software uses any of the three protocols, but requires the NetBIOS interface in all cases.

Lana Numbers

When a NetBIOS application (such as the Aloha application software) wishes to communicate on a network, it must specify which physical network adapter to use, as well as which protocol to use.� NetBIOS defines LAN adapter (lana) numbers as a means of specifying this information.� A lana number identifies a binding.� For example, lana 0 may specify a NetBEUI protocol bound to adapter 0.� Lana 1 might specify TCP/IP bound to adapter 0, and so on.

By default, most NetBIOS applications (including the Aloha application software) communicate using lana 0.� By specifying which binding is associated with lana 0, a technician can control which adapter card the Aloha application software communicates on, as well as which protocol.

Network Control Blocks

Network Control Blocks (NCBs) are the way applications issue NetBIOS commands.� An application builds a NCB and submits it to NetBIOS drivers.� An NCB specifies the following:

1.        The command to perform

2.        The lana number for the command

3.        The name of the sender and/or recipient

4.        A buffer that either contains the data to be sent, or will contain the data received

The NCB is 'in use' until a command completes.� Some commands take a relatively long time to complete; some never complete, such as a command listening for a terminal that is not on a network.

Under Microsoft Windows95, Windows98, and Windows Millennium Edition (Me) NCBs are a limited system resource.� Only a certain number of NCBs are in use at the same time.� This has some setup implications described below.

NetBIOS Names

NetBIOS identifies nodes using 16-character names.� More than one name can be in use on the same node at the same time.� Any application that wishes to communicate must first register a name that will identify it as a sender and recipient of data.� When the application exits, it also must 'deregister' the names it was using.

There are two types of NetBIOS names: station names and group names:

Station Name: A station name identifies a specific entity on a network.� If an application tries to register a station name that is already in use by someone else on the network, the application will fail to register the name.�

Group Name: A group name identifies one or more entities on a network.� It is okay for an application to register a group name that is already in use on a network.

When a NetBIOS name is registered, NetBIOS issues it a name number (ranging from 0-255) that is used to identify the name for subsequent NetBIOS commands.

The Front-of-House (FOH) registers two NetBIOS names when initializing a network.� The first name is a group name called IBERLINK.� The group name is used for all datagrams sent and received.� The second name is the station name that is TERMx where x is a character string based on a terminal number.� 'A' corresponds to 0, 'B' to 1, and so on.� For example, the station name for terminal 21 would be �TERMCB�.

If more than one Aloha system is running on the same network, name conflict poses a problem.� If both systems use the same naming convention, each system could inadvertantly receive messages from the other system, causing all sorts of confusion.

As a solution to this, the Aloha application software supports an environment variable named 'TERMSTR' that normally defaults to TERM.� If TERMSTR is set to any other value, the group name is set to 'TermStrLINK' and the station name is set to 'TermStrx,'� where x is defined as before.� In this manner, the terminals for a store can specify a unique TERMSTR value common to that store, and can avoid confusion with terminals in other stores

Datagrams

One type of network communication is unacknowledged, connectionless datagram service.� A datagram is a single network packet that is broadcast by a node.� Datagrams are not guaranteed to arrive at their destination, or even to arrive in the same order they are sent.� They may be discarded or lost at any time, without notification to the sender.� A datagram can be sent to an individual node, or to a group of nodes, by specifying either a station name or a group name as the destination.�

Datagrams are 'lean and mean', in that they are fast and have very little network overhead.� They provide a means of sending data to multiple recipients at one time.� But datagrams have limited usefulness, because they cannot be larger than the maximum packet size (512 bytes).� In addition, since datagram delivery is not 100% reliable, applications cannot assume a datagram has been received.� In reality, datagram reliability is more than 99.9 percent in a typical local area network (LAN).

In order for one application to send a datagram to another application, the following typically occurs:

1.        Both applications register the same group name.

2.        Both applications issue one or more 'Receive Datagram' commands for the group name, which basically states they are interested in receiving copies of datagrams addressed to that name.�

3.        The sending application issues a 'Send Datagram' command each time it wishes to transmit a datagram.

4.        The receiving application receives a notification as datagrams arrive.� As each incoming datagram is processed, the Receive Datagram command is reissued to prepare for the next datagram.

5.        Upon Shut Down, each application cancels the outstanding Receive Datagram command, then deregisters the group name.

Applications typically issue multiple Receive Datagram commands to ensure that there are enough receive buffers to keep up with expected traffic.� For example, if there is only one Receive Datagram command and a datagram arrives, the application will be notified and will process the datagram as quickly as possible.� If a second datagram arrives before the first is processed, the second datagram will be lost, because the Receive Datagram command has not yet been reissued and there is no place to buffer the second datagram.

As of version 4.2x, the FOH sends and receives datagrams only for redundancy purposes.� Previous versions used datagrams to broadcast status information, such as which terminals and printers were up.

Whenever a redundant terminal starts, it begins broadcasting datagrams that identify who it is and who it believes the master terminal is.� It also listens for datagrams from other terminals.� Eventually the redundant terminal will either receive a datagram from the master terminal, or an election process will elect a terminal to be the master, and startup continues.� The Aloha FOH issues two '* NumTerms Receive Datagram' commands, up to a maximum of 20.

The other Aloha application that broadcasts datagrams is the Control Server application.� Control Server broadcasts datagrams from the Back-of-House (BOH) containing the system date and time, and security key information.

Connections

Another type of network communication is reliable, connection-oriented service.� A connection is a point-to-point, two-way information channel.� Packets are guaranteed to arrive in the same order they are sent, and the sender is guaranteed to receive notification of successful or failed arrival.

To keep a receiver from being bombarded with more packets than it can handle, the sender and recipient agree on how many unacknowledged packets the sender is allowed to transmit.� The receiver acknowledges packets as a group, which is more efficient than one-at-a-time acknowledgement.� If the sender does not receive acknowledgement after an agreed period of time, it will resend the packets.� If no acknowledgement occurs after a specified time-out, the operation fails and the sender is notified.

Connections involve more overhead than datagrams, because they manage the two-way flow of packets between nodes.� Connections are also more complicated to use, because two nodes must negotiate to establish a connection.� In addition, to send data to multiple nodes requires a separate connection to each node.� For example, to send 1 megabyte (MB) of data to five nodes will actually transmit 5 MB on a network.� But sending 1 MB of datagrams to five nodes would only transmit 1 MB of data on a network.� This is the price paid for reliability.

1.        To establish a connection, the following must occur:

2.        Each station must register a unique station name.

3.        One station must issue a 'Listen' command that passively awaits contact from another station.

4.        The other station must issue a 'Call' command that identifies the station name to which it wishes to connect.

5.        If a Call is issued for a station that is Listening, the connection is established.� Each application is issued a 'session number' identifying the connection.

Once a connection is established, the following steps occur for a message to be transmitted:

1.        Each station issues a Receive command.

2.        The sending application issues a 'Send' command each time it wishes to transmit a message.

3.        The receiving application receives a notification as messages arrive.� As each incoming message is processed, the Receive command is reissued to prepare for the next message.

Unlike the case with datagrams, a single Receive command is enough for a connection.� The connection itself prevents the receiver from being overrun with data faster than it can process it.

How the Aloha application software Uses Connections

Aloha terminals communicate with master terminals using connections.� Each non-master terminal connects to a Master.� So if there are n terminals up, there are n � 1 connections.

To establish connections, one terminal must listen and the other must call.� The Master terminal issues n � 1 Listen commands.� Each non-master terminal issues a single Call command to the Master terminal.

Once a connection is established, the Aloha application software transaction messages are sent to and from the Master terminal by the other terminals.� The Master terminal writes the transactions to the transaction log as they are received.� This is the fundamental role of the Master terminal, and explains why the Aloha application software must have a Master terminal to function effectively.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1099 Network Troubleshooting

AKBID3145 IPX/SPX Protocol

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1075

�

Item Output File

Item Output File

============================================================================

AKBID1076

Created: 10 March 2000

Updated: 27 July 2000

Reviewed: 10 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Using the Item Output File Function in the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software Item Output File function creates, in real-time, a text file containing all menu items as they are ordered.� You can use this file with third-party stock control software, or as a limited electronic journal.�

Information

To enable the Item Output File, add the following line (if it does not already exist) to the ALOHA.INI file in the NEWDATA folder, and refresh the system:

ITEMOUTPUT=TRUE

Output files are created in the HISTORY folder.� The file name is based on the date, and it uses a .ITM extension (for example, 20000315.ITM).

Items are added to the output file as they are ordered or voided.

The file contains the necessary information for a basic product mix report, but it should not be used as such.� The Product Mix Report in the Aloha application software provides more information.

File Format

Each column is separated by a comma, and each line has a semi-colon (;) at the end.� Each line includes the following columns:

Column

Description

Action

'1' for Sale, '2' for Void.� An Action type '1' with a negative price is a Refund.

Item

The item's ID number.

Price

The amount of the Sale, Refund, or Void.

Employee

The employee's ID number.

Revenue Center

The Revenue Center ID applied to the transaction.

Time Stamp

The time of the transaction, in HH:MM:SS format.

Extended Information

No information.

Caveats

The file contains the necessary information for a basic product mix report, but it should not be used as such.� The Product Mix Report in the Aloha application software provides more information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1076 export interface sales

style='mso-spacerun:yes'>� 2003

�

Tender ID Validation

Tender ID Validation

============================================================================

AKBID1077

Created: 2 November 2000

Updated: 14 November 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

Subject: Using VAL.DBF to Enable Tender Identification Validation

============================================================================

Summary

The ALOHA^� application software uses VAL.DBF to verify tender identification numbers against a list of valid or invalid numbers.� You must enable tender validation for each tender in the Aloha application software Back-of-House (BOH) and manually enter valid or invalid ID numbers in VAL.DBF.

Information

Back-of-House Options

Besides enabling the ID prompt and setting the minimum and maximum number of characters, tender validation uses the following options in each tender's identification properties in BOH tender maintenance:

Numeric � Enables only numeric ID data.� Clear this box to enable alphanumeric ID characters.

Validate � Validates the ID entered in the order entry screen against a user-defined list of IDs in VAL.DBF.

Valid � Indicates whether the user-defined IDs in VAL.DBF are valid IDs or invalid IDs.

Tenders with 'House Account' enabled will not reference the information in VAL.DBF.

Editing VAL.DBF

Edit VAL.DBF with a compatible database-editing application and append the valid or invalid IDs.� VAL.DBF uses the following fields:

Field

Type

Length

Description

TENDERID

Numeric

10

The tender ID (from TDR.DBF) associated with this entry

IDENT

Character

20

The valid/invalid ID number

OWNERID

Numeric

5

Used by Centralized Database Management (CDM)

If a valid or invalid ID applies to multiple tenders, separate entries must be made for each tender.

The IDENT field supports alphanumeric characters.

The IDENT field only supports entire ID numbers.� ID strings are not supported.� For example, entering '1234' only validates or invalidates '1234', not '012345', '11234' and so on.

Extended Information

No information.

Caveats

Tenders with 'House Account' selected will not reference the information in VAL.DBF.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1077 val verify

�

Receipt Logos

Receipt Logos

============================================================================

AKBID1078

Created: 19 April 2000

Updated: 9 December 2002

Reviewed: 6 October 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.65x � 5.3.x

Subject: Printing Receipt Logos with the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software offers two ways to print receipt logos: downloaded from the Aloha application software, and logos stored in the receipt printer's memory.� This document explains how to configure both methods in the Aloha application software.

Information

POS Downloaded Logos

The Aloha application software can download a logo to thermal receipt printers, but this option substantially increases the time to print a receipt.

Create a receipt logo in bitmap (.BMP) form.� Do not use multiple colors since the printer only uses black and white hues.� Keep the bitmap file as small as possible since the Aloha application software must download (at 9600 BPS) the logo each time it prints a receipt.

To enable the receipt logo, edit the ALOHA.INI file in the NEWDATA folder, and add the following lines if the do not already exist:

Variable

Description

PRINTERBITMAP=y

Replace y with the name of the receipt logo, for example, RECEIPT.BMP.� The file must reside in the BMP folder.

PRINTERBITMAPSIZE=n

Set n to 0, 1, 2, or 3.� '0' stretches the logo horizontally and vertically.� '1' stretches the logo vertically.� '2' stretches the logo horizontally.� '3' displays the logo normally.� The maximum logo width is 192 pixels if '0' or '2' is specified.� The maximum logo width is 320 pixels if '1' or '3' is specified.� There is not limit to the vertical size.

PRINTERBITMAPJUSTIFY=x

Set x to LEFT, CENTER, or RIGHT.

Printer Memory Logos

Aloha application software versions 5.0x and higher support printer-memory logos with Epson^� TM-T88II printers.

Add the logos to the printer's memory using the TM Flash Logo setup utility from Epson.� The communications settings for the serial port in Windows, the printer, and the utility must match in order for the utility to see the printer.

To assign the logo to print, open Aloha Manager, and select Hardware/Printers from the Maintenance drop-down menu.� Set the logo number from the Pre-Loaded Logo drop-down menu.

Extended Information

Some printers have the ability to print logos independently from commands issued by the application software using the firmware built into the printer.� For example, the printer always prints a logo with any print job that it performs, regardless if it is a receipt, a remote printer chit, or a report.� Since this occurs entirely within the printer's firmware and does not require any interaction with the application software, the Aloha application software considers this feature neither supported nor unsupported.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1002 Aloha Receipt and Kitchen Printer Settings

AKBID1026 Using Windows-based Printers with Aloha

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1078

�

PayUSA Export Files

PayUSA Export Files

============================================================================

AKBID1079

Created: 7 March 2000

Updated: 29 September 2000

Reviewed: 3 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Creating PayUSA Export Files with the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software can export labor data to a file that you can import into the PayUSA software.� The files are automatically created at the end of the PayUSA-defined pay period during the End-of-Day (EOD) process, or you can manually generate the export files from the Aloha application software Back-of-House (BOH).

Information

Perform the following to enable and configure PayUSA in the Aloha application software:

If you are using versions 4.4x or lower, open Maintenance, and select Labor/Electronic Payroll Processing.��

If you are using versions 5.0x or higher, open Aloha Manager, select Maintenance/Store Settings/Labor/Electronic Payroll Settings.��

Configure the following information in the Electronic Payroll settings:

Use PayUSA � Select this to enable PayUSA support.

Pay Period Days � The number of days in a PayUSA pay period (7 or 14).

Company Code � Company code assigned to the store by PayUSA.

Perform the following to add the PayUSA export codes to each employee in the Aloha application software:

If you are using versions 4.4x or lower, open Maintenance, and select Labor/Employees.� Add the export code to the 'Export ID #' field for each employee.

If you are using versions 5.0x or higher, open Aloha Manager, select Maintenance/Labor/Employees.� Add the export code to the 'Export ID #' field for each employee.

The initial PayUSA setup requires manual configuration of two variables in the ALOHA.INI.� Edit the Aloha.ini in the NewData folder and add the following variables if they do not already exist (replace the date as described below):

PAYUSAENDDATE=mm dd yyyy

PAYUSAAUTORANDATE=mm dd yyyy

PAYUSAENDDATE refers to the last day of the previous PayUSA pay period.� Set this date to 7 or 14 days (depending on the Pay Period Days defined above) prior to the next pay period ending date.

PAYUSAAUTORANDATE refers to the last date the PayUSA export files were automatically created.� Set this date to the same day as the PAYUSAENDDATE.

The PAYUSAENDDATE and PAYUSAAUTORANDATE variables will be automatically adjusted in the future.� Manual configuration is only required during the initial setup.

Export Files

The Aloha application software checks the pay period status during the grind process following each EOD in order to automatically create the PayUSA export files.�

The automatic creation process adds the Pay Period Days to the PAYUSAENDDATE variable.� If the sum equals the DOB, the sum is compared to the PAYUSAAUTORANDATE.�

If these dates are the same, nothing more is done.�

If the PAYUSAAUTORANDATE is prior to the sum (Pay Period Days + PAYUSAENDDATE), the grind process creates the PayUSA export files and the the PAYUSAAUTORANDATE and PAYUSAENDDATE variables are updated.

Manual execution of the PayUSA export process extracts the payroll data from the last complete pay period prior to the current DOB.� It does not however, update PAYUSAAUTORANDATE.� Manual execution of the extract process overwrites existing extract data files, if any.�

To manually create the export files in versions 4.4x and lower, open Control and select Functions/Create PayUSA Payroll File.�

To manually create the export files in versions 5.0x and higher, open Aloha Manager and select Functions/Export/Create PayUSA Payroll File.

Two export files are created in the PAYUSA folder located within the Aloha application software folder: PCDBcccc.023 and PCDBcccc.036 (cccc reflects the Unit Number)

PCDBcccc.023 contains employee time information.� PCDBcccc.036 contains employee sales and tip information.

The extract process accumulates labor data for each day in the selected pay period by employee by job code and by type (regular or overtime).� All rates are total pay (not reported) divided by total hours.� Tippable sales and tips (declared wages) are accumulated by employee.

Extended Information

The following files contain cumulative totals for all days in the defined pay period.

Data input is from AdjTime.dnf or AdjTimex.dbf (if present) in the appropriate dated subdirectories of the defined PayUSA pay period.� Refer to document AKBID1030 and AKBID1042 for more information on Aloha application software DBF files.

PCDBcccc.023

Position

Type

Length

Description

1 � 6

Numeric

6

Employee Export ID.� Right justified, zero filled.

7 � 7

Numeric

1

Code: 2 = Regular, 3 = Overtime, 4 = Double-time.� Only 2 and 3 are currently used.

8 � 12

Numeric

5

Hours (2 implied decimals, right justify, zero filled).

13 � 13

Alpha

1

'G' if G/L account number or 'J' if job cost number.� Only 'G' is currently used.

14 � 27

A/N

14

G/L account number: 6 = Job Code, 2 = Company Code, 6 = Store #.

28 � 33

Numeric

6

Rate (2 implied decimals, right justify, zero filled).

34 � 35

LF or CR

1 or 2

Line Feed or Carriage Return

PCDBcccc.036

Position

Type

Length

Description

1 � 6

Numeric

6

Employee Export ID.� Right justified, zero filled.

7 � 10

A/N

4

Deduction/Earning Code, either SALE or TIPS.

11 � 16

Numeric

6

Hours, all zeros.

17 � 23

Numeric

7

Rate, all zeros.

24 � 31

Numeric

8

Depending on Deduction/Earning Code above, either tippable sales or declared wages (2 implied decimals, right justify, zero filled).

32 � 33

Space

1

33 � 33

LF or CR

1

Line Feed or Carriage Return

Caveats

No information.

============================================================================

See also:

AKBID1015 EOD Process and Errors

AKBID1016 Grind Process and Errors

AKBID1030 Aloha Grind Database Contents

AKBID1042 Aloha Application Software Database Files

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1079

ReMACS Export Files

ReMACS Export Files

============================================================================

AKBID1080

Created: 10 March 2000

Updated: 7 November 2002

Reviewed: 27 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

Subject: Creating ReMACS Export Files in the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software can export labor and sales data to files that are imported by the ReMACS software.� This document explains how to configure the Aloha application software to export ReMACS information.

Information

Perform the following to create ReMACS export files:

In versions 4.4x or lower, open Control, and select the appropriate ReMACS export function from the Functions drop-down menu.� Highlight the day or range of days to export, and click OK.�

In versions 5.0x or higher, open Aloha Manager, and select Function/Export, and select the appropriate ReMACS export function.� Highlight the day or range of days to export, and click OK.�

Two ReMACS export files are created in the Aloha application software folder: MENUSALE.FLT, and PAYROLL.FLT.� The 'Create ReMACS Menu File' function creates the MENUSALE.FLT export file.� This file holds sales information.� The 'Create ReMACS Realworld Pay File' function creates the PAYROLL.FLT export file.� This file holds labor information.

Two additional settings for the ReMACS Menu file are available by selecting the Settings button on the export date selection screen:

Use Profit Center Code � If this is not checked, the exported Profit Center Code is set to the Location Number set in the Aloha application software.� If this is checked, the Profit Center Code is the first two digits of the item�s Sales Category plus the first three digits of the Location Number set in the Aloha application software.

Report Sales by Period � Exports the day parts.

Job Code Export Codes

All Job Codes must have an export code for ReMACS.� Perform the following to add the ReMACS export codes to each Job Code in the Aloha application software:

If you are using versions 4.4x or lower, open Maintenance, select Labor/Job Codes/Page 2, and add the export code to the 'Export ID #' field for each Job Code.

If you are using versions 5.0x or higher, open Aloha Manager, select Maintenance/Labor/Job Codes, and add the export code to the 'Export Code' field for each Job Code.

Employee Export Codes

Employees can have optional export code for ReMACS.� Perform the following to add the optional ReMACS export codes to each employee in the Aloha application software:

If you are using versions 4.4x or lower, open Maintenance, select Labor/Employees from the Labor drop-down menu, and add the export code to the 'Export ID #' field for each employee.

If you are using versions 5.0x or higher, open Aloha Manager, select Maintenance/Labor/Employees, and add the export code to the 'Export ID #' field for each employee.

Automation

You can automate the process of creating export files and moving them to the correct ReMACS folder using the Winhook process (refer to document AKBID1028 and AKBID1038).� Contact your ReMACS representative for the correct ReMACS folder to use.

To create the ReMACS Realworld Payroll export file, add the following command line to your Winhook batch file:

%IBERDIR%\BIN\RPT.EXE /DATE %1 /RR

To create the ReMACS Menu Item Sales export file, add the following command line to your Winhook batch file:

%IBERDIR%\BIN\RPT.EXE /DATE %1 /RF

To move the files to the ReMACS folder, add the following line to the Winhook batch file, replacing x with the location ReMACS imports from:

COPY %IBERDIR%\*.FLT C:\x

Extended Information

Both export files are in ASCII format.

MENUSALE.FLT

Field

Size

Date (YY)

2

Date (MM)

2

Date (DD)

2

Profit Center Code

5

Period (Optional)

5

Location (always blank)

3

Item

5

Sub Menu (always 00)

2

Price (7.2 format)

9

Quantity Sold

8

PAYROLL.FLT

Field

Size

Record Type (always LM)

2

Employee Number (uses Export ID if available)

10

Start Date (YYMMDD)

6

End Date (YYMMDD)

6

Job Code (uses Export ID if available)

5

Salary Flag (always N)

1

Regular Hours (includes a +)

6

Regular Rate (includes a +)

6

Overtime Hours (includes a +)

6

Overtime Rate (includes a +)

6

Special Hours (always 000000+)

6

Special Rate (always 000000+)

6

Holiday Hours (always 000000+)

6

Sick Hours (always 000000+)

6

Vacation Hours (always 000000+)

6

Advanced Vacation Weeks (always 0)

1

Accrued Vacation Hours (always 000000+)

6

Accrued Sick Hours (always 000000+)

6

Weeks worked/Paid (always 0000+)

4

Work Units (always 00000+)

5

Direct Tips (includes a +)

8

Sales (includes a +)

8

Indirect Tips (always 00000000+)

8

Meals (always 00000000+)

8

Temp D/E 1 Code (always blank)

3

Temp D/E 1 Amount (always 00000000+)

8

Temp D/E 2 Code (always blank)

3

Temp D/E 2 Amount (always 00000000+)

8

Temp D/E 3 Code (always blank)

3

Temp D/E 3 Amount (always 00000000+)

8

Caveats

No information.

============================================================================

See also:

AKBID1028 Winhook

AKBID1038 Report Command Line Parameters

AKBID1047 Microsoft Windows Schedule Service

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1080 remax

�

Summary Process and Files

Summary Process and Files

============================================================================

AKBID1081

Created: 15 March 2000

Updated: 16 April 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 3.8x, 4.260 � 5.3.x

Subject: The Summary Process and Files

============================================================================

Summary

The ALOHA^� application software Summary process creates .DBF files from information in the dated folders created during the End-of-Day (EOD) process (refer to document AKBID1015).� Summary files are advantageous to Crystal Report users because a summary file spans an entire month or year, whereas Grind files (refer to document AKBID1016) only span a single day.� This document explains the summary file process and their contents.

The summary process should not be enabled unless there is a specific need.

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

Information

The summary process is enabled in the ALOHA.INI.� Edit the ALOHA.INI in the NEWDATA folder, and add the line RUNSUM=TRUE if it does not already exist.

Ensure a complete understanding of the Re-summarizing Files section in this document before enabling the summary process.

The summary process automatically creates summary files after the grind process creates the GNDDBF30.XXX flag in each dated folder, but before the Winhook process (refer to document AKBID1028) starts.� The summary process creates a marker file in the dated folder as it updates each DBF files.� Flags files for each DBF are created in the dated folder in nnnnnnn.XXY (year) and nnnnnnn.XXM (month) format, where nnnnnnn is the label of the completed summary DBF file.

The 'Auto Grind and Summarize' flag in Control (versions 4.4 and lower) enables or disables the Grind and Summary processes from automatically activating when needed.�� This flag, located in Control/System/Auto Grind and Summarize, is very easy to inadvertently clear.� Clearing this flag is controlled by the user's abilities, as defined in the Back-of-House (BOH) security setup.�� See the Aloha QuickService or TableService User Manual for more information.�� All users, regardless of standing, should be disabled from clearing this flag.

Summary DBF Files

Summary DBF files are stored in the SUM folder.� A folder for each month and year resides in the SUM folder.� Each month's folder is labeled in a MOyyyymm format, where yyyy is the year, and mm is the month.� For example, the March 2000 folder is labeled MO200003.� Each year's folder is labeled in a YEARyyyy format, where yyyy is the year.� For example, the year 2000 folder is labeled YEAR2000.

Each month and year folder houses seven DBF files:

File

Description

SUMITEM.DBF

Item sales (or product mix)

SUMREVN.DBF

Revenue Center sales

SUMSALE.DBF

Sales amounts

SUMTIME.DBF

Labor clock-in and clock-out times

SUMTNDR.DBF

Tender amounts

SUMTURN.DBF

Table turns, or number of checks

SUMVOID.DBF

Voided items

Re-summarizing Files

The summary process design does not lend itself to re-summarizing.� Deleting the *.XXM or *.XXY flag files from the dated folders forces re-summarization.�� However, this will result in double-summarizing the data, since the Summary process is additive only.��

Any time the Summary process runs, it adds into the specified monthly or yearly totals.�� Except for the marker files, the Summary process has no way knowing whether or how much it has already added for a given date.� Thus, deleting marker files is hazardous.

If accurate monthly summary files are required in a situation that requires re-grinding and re-summarizing data that has been previously summarized, delete the summary DBF files for the entire month, and then delete *.XXM from the dated folders for the entire month.��

If accurate yearly summary files are required in a situation that requires re-grinding and re-summarizing data that has been previously summarized, delete the summary DBF files for the entire year, and then delete *.XXY from the dated folders for the entire year.

Re-summarizing entire months or years can be avoided by creating backup copies of summary DBF files on a routine basis, such as every week or each time dated folders are purged.

Re-summarizing files should be avoided whenever possible.

Manual File Creation

The Summary process is additive only.� Re-summarizing existing data may create invalid figures if performed improperly.� See the Re-summarizing section of this document for more information.

The RUNSUM variable described in previously can be TRUE or FALSE for manual summary file creation.

Summary files are manually created using the following command line syntax:

%IBERDIR%\BIN\SUM.EXE /DATE x /TYPE y /SUMDIR z

/DATE x � The name of the dated folder.� For example, /DATE 20000331.

/TYPE y � The type of summary file (see table).� For example, /TYPE 10734.

/SUMDIR z � The year or month folder to place the files.� For example, /SUMDIR %IBERDIR%\SUM\MO20000331 or /SUMDIR %IBERDIR%\SUM\YEAR2000.

Summary Types:

Type

File

10734

SUMITEM.DBF

10736

SUMREVN.DBF

10738

SUMSALE.DBF

10249

SUMTIME.DBF

10742

SUMTNDR.DBF

10744

SUMTURN.DBF

10746

SUMVOID.DBF

The following commands are an example of manual summary file creation (month and year) for the date of 31 March 2000:

%IBERDIR%\BIN\SUM.EXE /DATE 20000331 /TYPE 10734 /SUMDIR C:\ALOHA\SUM\MO200003

%IBERDIR%\BIN\SUM.EXE /DATE 20000331 /TYPE 10736 /SUMDIR C:\ALOHA\SUM\MO200003

%IBERDIR%\BIN\SUM.EXE /DATE 20000331 /TYPE 10738 /SUMDIR C:\ALOHA\SUM\MO200003

%IBERDIR%\BIN\SUM.EXE /DATE 20000331 /TYPE 10249 /SUMDIR C:\ALOHA\SUM\MO200003

%IBERDIR%\BIN\SUM.EXE /DATE 20000331 /TYPE 10742 /SUMDIR C:\ALOHA\SUM\MO200003

%IBERDIR%\BIN\SUM.EXE /DATE 20000331 /TYPE 10744 /SUMDIR C:\ALOHA\SUM\MO200003

%IBERDIR%\BIN\SUM.EXE /DATE 20000331 /TYPE 10746 /SUMDIR C:\ALOHA\SUM\MO200003

%IBERDIR%\BIN\SUM.EXE /DATE 20000331 /TYPE 10734 /SUMDIR C:\ALOHA\SUM\YEAR2000

%IBERDIR%\BIN\SUM.EXE /DATE 20000331 /TYPE 10736 /SUMDIR C:\ALOHA\SUM\YEAR2000

%IBERDIR%\BIN\SUM.EXE /DATE 20000331 /TYPE 10738 /SUMDIR C:\ALOHA\SUM\YEAR2000

%IBERDIR%\BIN\SUM.EXE /DATE 20000331 /TYPE 10249 /SUMDIR C:\ALOHA\SUM\YEAR2000

%IBERDIR%\BIN\SUM.EXE /DATE 20000331 /TYPE 10742 /SUMDIR C:\ALOHA\SUM\YEAR2000

%IBERDIR%\BIN\SUM.EXE /DATE 20000331 /TYPE 10744 /SUMDIR C:\ALOHA\SUM\YEAR2000

%IBERDIR%\BIN\SUM.EXE /DATE 20000331 /TYPE 10746 /SUMDIR C:\ALOHA\SUM\YEAR2000

Extended Information

SUMITEM.DBF

Field

Description

EMPLOYEE

Employee ID who sold the item

ITEM

Item ID

CATEGORY

Sales Category ID

PERIOD

Period ID

REVID

Revenue Center ID

TAXID

Tax ID

PRICE

Item price

QUANTITY

Quantity sold

SUMSALE.DBF

Field

Description

EMPLOYEE

Employee ID who sold the item

PERIOD

Period ID

TYPE

Type of sale (see table)

TYPEID

ID associated with TYPE, if any

AMOUNT

Amount for the TYPE

SUMSALE.DBF Types

Type

Description

1

Total (including inclusive taxes) of all items sold by sales category.� Does not include exclusive taxes or voids)

2

Exclusive taxes, by Tax ID

3

Tax-exempt exclusive taxes, by Tax ID

4

Payments, by tender ID

5

Comps, by comp ID

6

Promotions, by promotion ID

7

Comp tax not collected, by tax ID

8

Promotion tax not collected, by tax ID

9

Taxable sales for inclusive and vendor taxes, by tax ID

10

Total guests

11

Total checks

12

Amount of tip share paid

13

Total voided sales, by employee ID

14

Tip reduction, by employee ID

15

Petty cash, by manager employee ID and account ID

16

Non-collected surcharges

17

Collected surcharges

18

Order mode charges

19

Comps, by sales category ID

20

Promotions, by sales category ID

21

Server performance measure, by performance measure ID

22

Declared cash from checkouts and payment reconciliation

23

Gift certificates sold, by gift certificate ID

24

Tax, by sales category ID

25

Taxable sales for inclusive taxes, by sales category ID

inclusive tax formula: TAX= (AMOUNT * RATE) / (1 + RATE)

26

Non-redeemed payments (over-payment without return change)

31

Net sales, by order mode ID

32

Total calculated inclusive taxes

33

Calculated inclusive taxes, by check number

34

Auto gratuity, by check number

35

Refunds, by Sales Category ID

36

Total tax refunded

37

Taxable refunds

38

Tax exempt refunds

39

Tax refunds, by sales category ID

40

Taxable refunds, by sales category ID

41

Tax-exempt taxable sales

42

Over/short, by employee ID (if available)

43

Number of checks, by order mode ID

44

Perpetual check counter information

45

Rounding adjustment total

46

Order attributes

47

Number of 'no sale' transactions (QuickService only)

48

Foreign currency payments, by tender ID

49

Guests, by order mode ID

50

Credit card refunds

51

Exclusive tax taxable sales, by sales category ID

52

Straight sales � inclusive tax � comps (if NETHASCOMPS=TRUE) � promotions (if NETHASCOMPS=TRUE), by sales category ID.

53

Straight sales + Exclusive tax, by sales category

54

Inclusive tax, by sales category ID

55

Cash cards sold

56

Voided gift certificates, by gift certificate ID

57

Declared non-cash tenders from payment reconciliation

58

Uncollected surcharges, by sales category ID

59

Collected surcharges, by sales� category ID

60

Order mode charges, by sales category ID

61

Revenue center ID for type 60 order mode charges

62

Additional charges (Aloha Manager\Maintenance\Store Settings\Financials\Add Charges)

63

Goods and services tax (GST)

64

$0.00 checks

65

Total comps applied to gift certificates, by comp ID

66

Total promos applied to gift certificates, by promo ID

67

Total comps applied to gift certificates, by sales category ID

68

Total promos applied to gift certificates, by sales category ID

SUMTNDR.DBF

Field

Description

TYPE

Type of payment (see table)

TYPEID

ID associated with TYPE

AMOUNT

Amount for the TYPE

TIP

Tip

NR

Non-redeemed payments (over-payment without return change)

QUANTITY

Quantity for TYPE

SUMTNDR.DBF Types

Type

Description

1

Tender

2

Promotion

3

Comp

SUMVOID.DBF

Field

Description

EMPLOYEE

Employee ID

MANAGER

Manager ID who performed the void

CHECK

Check ID

TABLENAME

Table Name

ITEM

Voided item ID

PRICE

Voided item price

DATE

Date-of-Business

HOUR

Hour

MINUTE

Minute

REASON

Void reason ID

INVENTORY

Does void effect inventory

SUMREVN.DBF

Field

Description

EMPLOYEE

Employee ID

PERIOD

Period ID

REVID

Revenue Center ID

TYPE

Type of sale (see table)

TYPEID

ID associated with TYPE, if any

AMOUNT

Amount for the TYPE

SUMREVN.DBF Types

Type

Description

1

Sales

2

Exclusive Taxes

3

Inclusive and Vendor Taxes

4

Guests

5

Checks

SUMTURN.DBF

Field

Description

EMPLOYEE

Employee ID

JOBCODE

Job Code ID

TABLE

Table number

PERIOD

Period ID

REVID

Revenue Center ID

SALES

Total sales closed for the table

CHECKS

Number of checks closed for the table

GUESTS

Number of guests at the table

MINUTES

Minutes table was open

QUANTITY

Total number of table turns

SUMTIME.DBF

Field

Description

EMPLOYEE

Employee ID

SSN

Employee Government-issued ID number

DATE

Date-of-Business

JOBCODE

Job Code ID

INHOUR

Clock-in hour

INMINUTE

Clock-in minute

OUTHOUR

Clock-out hour

OUTMINUTE

Clock-out minute

MINUTES

Total labor minutes

RATE

Pay rate

PAY

Total pay

OVERMIN

Overtime minutes

OVERRATE

Overtime pay rate

OVERPAY

Total overtime pay

CCTIPS

Non-cash tips

DECTIPS

Declared tips

SALES

Gross sales

SALESIN

Gross sales closed by this employee, but entered by another employee.

SALESOUT

Gross sales entered by this employee, but closed by another employee.

NOTIPSALES

Non-tippable sales

Caveats

The Summary process should not be enabled unless there is a specific need.

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

Ensure a complete understanding of the Re-summarizing Files section in this document before enabling the Summary process.

Any time the Summary process runs, it adds into the specified monthly or yearly totals.�� Except for the marker files, the Summary process has no way knowing whether or how much it has already added for a given date.� Thus, deleting marker files is hazardous.

Re-summarizing files should be avoided whenever possible.

The Summary process is additive only.� Re-summarizing existing data may create invalid figures if performed improperly.� See the Re-summarizing section of this document for more information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1015 EOD Process and Errors

AKBID1016 Grind Process and Errors

AKBID1028 Winhook

AKBID1030 Grind Database and Contents

AKBID1108 Using the Crystal Reports Interface with .DBF Files

AKBID1129 Using the Crystal Reports Interface with an RDB

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1081

�

Separate QS and TS Installations on a Single Demo Computer

Separate QS and TS Installations on a Single Demo Computer

============================================================================

AKBID1082

Created: 16 March 2000

Updated: 4 August 2003

Reviewed: 18 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 4.2x � 5.3.x

Subject: Configuring QuickService and TableService on a Single Computer for Demonstration Purposes

============================================================================

Summary

This document explains how to configure separate instances of the ALOHA^� application software QuickService and TableService products on a single computer for demonstration purposes.� The results of the information in this document are two separate instances of ALOHAMGR.EXE (Aloha Manager): one for QuickService and the other for TableService.� Each instance is separate from the other and uses a separate Aloha folder.� If you want to use a single instance of Aloha Manager (and a single Aloha folder) to run both QuickService and TableService on a single computer for demonstration purposes, then refer to document AKBID1228 for more information.

The information in this document is not intended for use in a live restaurant.� It is intended for demonstration purposes only.

Information

Network Settings

Ensure the computer's network identification is set properly before attempting to install the Aloha application software.� The Aloha application software installation application (SETUPPOS.EXE /ADVANCED) on the Aloha Installation CD requires the proper network identification nomenclature.� The name must consist of a name (referred to as TERMSTR) followed terminal number (referred to as TERM).� ALOHA1, QSTS1, and DEMO1 are examples of possible network names.� In the case of ALOHA1, 'ALOHA' is the TERMSTR, and '1' is the TERM number.

Ensure the computer's network configuration is set properly before attempting to install the Aloha application software.� Once installed, the Aloha application software requires that Windows networking is enabled.� If Windows networking is not configured with a valid network interface device, such as a Network-Interface-Card (NIC) or a modem, along with a functional protocol, Windows networking may not be enabled.� If you are using TCP/IP as the default protocol, TCP/IP must be assigned an IP address either statically or via DHCP.� Refer to document AKBID1099 for more information on single-terminal networking.

Install QuickService and TableService

Run SETUPPOS.EXE /ADVANCED from the Aloha Installation CD to separately install QuickService and TableService in separate folders (for example, C:\ALOHAQS and C:\ALOHA).

It does not matter if you select 'Run Front of House and Back of House on same PC', 'Run CTLSVR as a service', or 'Run EDCSVR as a service' when installing each version since these settings are overridden later in this document.�

Since each version requires different environment variables to indicate the correct IBERDIR, LOCALDIR, and IBERROOT, you must initialize each version of each application using a separate batch file.� The batch files also register the necessary versions of CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server).

QuickService Batch Files

Each QuickService component requires a batch file to enable the correct environment variables.

For versions 4.2x or 4.4 and lower, create a batch file labeled QSCTL.BAT in the C:\ALOHAQS\BIN folder.� Use this batch file to start Control.� Add the following lines to the batch file:

Adjust the Aloha application software environment variables and the location of REGSVR32.EXE as needed.

SET TERMSTR=DEMO

SET NUMTERMS=1

SET SERVER=DEMO1

SET IBERROOT=ALOHAQS

SET IBERDIR=C:\%IBERROOT%

SET ROBUST=TRUE

%IBERDIR%\BIN\CTLSVR.EXE /UNREGSERVER /S

%IBERDIR%\BIN\CTLSVR.EXE /REGSERVER /NONET /S

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S %IBERDIR%\BIN\CTLSVRPS.DLL

%IBERDIR%\BIN\CTL.EXE

The '/S' variable directs CTLSVR.EXE and REGSVR32.EXE not to display conformation dialogues.

In versions 5.0x and higher, create a batch file labeled QSMGR.BAT in the C:\ALOHAQS\BIN folder.� Use this batch file to start Aloha Manager.� Add the following lines to the batch file:

Adjust the Aloha application software environment variables and the location of REGSVR32.EXE as needed.

SET TERMSTR=DEMO

SET NUMTERMS=1

SET SERVER=DEMO1

SET IBERROOT=ALOHAQS

SET IBERDIR=C:\%IBERROOT%

SET ROBUST=TRUE

%IBERDIR%\BIN\CTLSVR.EXE /UNREGSERVER /S

%IBERDIR%\BIN\CTLSVR.EXE /REGSERVER /NONET /S

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S %IBERDIR%\BIN\CTLSVRPS.DLL

%IBERDIR%\BIN\ALOHAMGR.EXE

Create a batch file labeled QSIBER.BAT in the C:\ALOHAQS\BIN folder.� Use this batch file to start IBERQS.EXE.� Add the following lines to the batch file:

Adjust the Aloha application software environment variables as needed.

SET TERMSTR=DEMO

SET NUMTERMS=1

SET SERVER=DEMO1

SET IBERROOT=ALOHAQS

SET ROBUST=TRUE

SET MASTERCAPABLE=TRUE

SET SERVERCAPABLE=TRUE

SET LOCALDIR=C:\%IBERROOT%

SET CALIBRATE=%LOCALDIR%\BIN\CALIB.EXE

SET TERM=1

IF EXIST %LOCALDIR%\TMP\EXITING DEL %LOCALDIR%\TMP\EXITING

%LOCALDIR%\BIN\IBERQS.EXE

TableService Batch Files

Each TableService component requires a batch file to enable the correct environment variables.

For versions 4.2x or 4.4 and lower, create a batch file labeled TSCTL.BAT in the C:\ALOHA\BIN folder.� Use this batch file to start Control.� Add the following lines to the batch file:

Adjust the Aloha application software environment variables and the location of REGSVR32.EXE as needed.

SET TERMSTR=DEMO

SET NUMTERMS=1

SET SERVER=DEMO1

SET IBERROOT=ALOHA

SET IBERDIR=C:\%IBERROOT%

SET ROBUST=TRUE

%IBERDIR%\BIN\CTLSVR.EXE /UNREGSERVER /S

%IBERDIR%\BIN\CTLSVR.EXE /REGSERVER /NONET /S

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S %IBERDIR%\BIN\CTLSVRPS.DLL

%IBERDIR%\BIN\CTL.EXE

The '/S' variable directs CTLSVR.EXE and REGSVR32.EXE not to display conformation dialogues.

In versions 5.0x and higher, create a batch file labeled TSMGR.BAT in the C:\ALOHA\BIN folder.� Use this batch file to start Aloha Manager.� Add the following lines to the batch file:

Adjust the Aloha application software environment variables and the location of REGSVR32.EXE as needed.

SET TERMSTR=DEMO

SET NUMTERMS=1

SET SERVER=DEMO1

SET IBERROOT=ALOHA

SET IBERDIR=C:\%IBERROOT%

SET ROBUST=TRUE

%IBERDIR%\BIN\CTLSVR.EXE /UNREGSERVER /S

%IBERDIR%\BIN\CTLSVR.EXE /REGSERVER /NONET /S

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S %IBERDIR%\BIN\CTLSVRPS.DLL

%IBERDIR%\BIN\ALOHAMGR.EXE

Create a batch file labeled TSIBER.BAT in the C:\ALOHA\BIN folder.� Use this batch file to start IBER.EXE.� Add the following lines to the batch file:

Adjust the Aloha application software environment variables as needed.

SET TERMSTR=DEMO

SET NUMTERMS=1

SET SERVER=DEMO1

SET IBERROOT=ALOHA

SET ROBUST=TRUE

SET MASTERCAPABLE=TRUE

SET SERVERCAPABLE=TRUE

SET LOCALDIR=C:\%IBERROOT%

SET CALIBRATE=%LOCALDIR%\BIN\CALIB.EXE

SET TERM=1

IF EXIST %LOCALDIR%\TMP\EXITING DEL %LOCALDIR%\TMP\EXITING

%LOCALDIR%\BIN\IBER.EXE

Extended Information

If you are not using a HASP^� key, refer to document AKBID1173.

Caveats

The information in this document is not intended for use in a live restaurant.� It is intended for demonstration purposes only.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1010 Aloha Application Software System Environment Variables

AKBID1099 Network Troubleshooting

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1170 Multiple Version of Aloha on a Single Demo Computer

AKBID1173 Demo Aloha without a HASP Key

AKBID1228 Demo both QS and TS with a Single Instance of Aloha Manager

AKBID3169 KEY.TXT HASP Security Key Identification Files

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1082 demonstrate

�

Reporting Checkout Buckets

Reporting Checkout Buckets

============================================================================

AKBID1083

Created: 21 March 2000

Updated: 20 August 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.206 � 5.3.x

Subject: Using the Aloha Application Software Checkout Report

============================================================================

Summary

The ALOHA^� application software uses the Checkout Report as a convenient way to summarize employee sales information in a single report using Checkout Buckets.� This document explains how to create checkout buckets and report them.

Information

Checkout Buckets

Create checkout buckets to assign employees to for the checkout report.� Checkout buckets are groups of employees, such as AM, PM, Bar, Dining Room, or Patio.

�

In versions 4.4x and lower, open Maintenance, and select Checkout Buckets from the Labor drop-down menu.

In versions 5.0x and higher, open Aloha Manager, and select Maintenance/Store Settings/Labor/Checkout Buckets.�

You can create up to ten checkout buckets.

Refresh the system.

Checkout Report

Perform the following to run a checkout report:

In versions 4.4x and lower, open Control, and select Functions/Assign Checkouts.� Select a date, assign employees to checkout buckets, and click Print or View.

In versions 5.0x and higher, open Aloha Manager, and select Functions/Assign Checkouts.� Select a date, assign employees to checkout buckets, and click Print or View.

All employees clocked-in under an Order Entry job code (refer to document AKBID1053) can be included in the checkout report, even if they have not checked-out.�

Extended Information

Checkout bucket assignments are stored in the CKO.CFG.� There is a different CKO.CFG in dated folders for each day that you have created checkout bucket assignment configuration, including the current day.� The CKO.CFG for the current day (in the Aloha application software DATA folder) is moved to the dated folder during the End-of-Day (EOD) process.� In order to make checkout bucket assignments easier, you can use the Winhook process (refer to document AKBID1028) to copy the CKO.CFG from the dated folder to the Aloha application software DATA folder.� This will provide a default checkout bucket assignment configuration for the new day.

Caveats

No information.

============================================================================

See also:

Aloha TableService User Manual

AKBID1028 Winhook

AKBID1053 TableService Order Entry Job Code Options

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1083

�

Smart Tax

Smart Tax

============================================================================

AKBID1084

Created: 8 March 2000

Updated: 4 October 2001

Reviewed: 15 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.8x � 5.3.x

Subject: Using Smart Taxes in the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software Smart Tax functionality offers the ability to automatically convert inclusive taxes to exclusive taxes in special situations. In most cases, inclusive taxes, and thus, smart taxes, are only used in the bar area.� For this reason, this document only focuses on using inclusive and smart taxes in the bar area.

The information in this document does not preclude any local, state, or federal tax laws.� Consult local tax laws before implementing instructions given in this document.

Information

Many restaurants use inclusive taxes on liquor items sold in the bar area, but leave food exclusively taxed.� Both food and liquor items in the restaurant area are exclusively taxed.

Inclusive taxes include the sales tax in an item's selling price, and increase the bartender's speed by eliminating pennies, and in some cases, change altogether.� The downside is the restaurant does not make as much profit on items inclusively taxed.�

Smart Taxes are designed increase profitability by to converting inclusive taxes to exclusive taxes if any exclusively taxed items reside on the check.� For example, a patron orders two inclusively taxed beers at a bar priced at $1.50 each.� The total is $3.00, and the transaction is completed quickly since there is no change involved.� Another patron orders two inclusively taxed beers at $1.50 each, plus an exclusively taxed hamburger at $3.00.� The total is $6.18 (with a 6% tax rate).

Since the hamburger is exclusively taxed, smart tax coverts the two beers to exclusive taxes, so the total price in the previous example becomes $6.36.

Create Inclusive and Exclusive Taxes

Create inclusive and exclusive versions of each liquor, beer, or wine tax to coexist with the food and retail taxes.� Refer to the Aloha Application Software TableService User Manual for more information on creating taxes.�

Assign Taxes to Items

Assign exclusive taxes to all taxable items.� Do not assign inclusive taxes to items since inclusive taxes will be assigned using Menu level Tax Reroutes.� Refer to the Aloha Application Software TableService User Manual for more information on assigning taxes to items.�

Reroute Taxes

Create Menu level Tax Reroutes on the bar menus to replace exclusive taxes with inclusive taxes on all bar drinks.� Perform the following steps to create menu tax reroutes:

In versions 4.4x and lower, open Maintenance, and select Menus/Menu.

In versions 5.0x and higher, open Aloha Manager, and select Maintenance/Menu/Menus.

Select each bar menu and reroute each exclusive liquor tax to the similar inclusive tax in the Tax Substitution fields.

Any employee using a bar menu will get inclusive taxes on bar drinks.

Enable Smart Taxes

Enable smart tax functionality, and assign smart taxes to each inclusive tax.� To enable Smart Tax functionality, perform the following:

In versions 4.4x and lower, open Maintenance, and select Options/Miscellaneous 2.� Enable the 'Use Smart Taxes' option.

In versions 5.0x and higher, open Aloha Manager, and select Maintenance/Store Settings/Financials/Taxes & Surcharge.� Enable the 'Use Smart Taxes' option.

Assign the applicable exclusive tax in the smart tax box for each inclusive tax by performing the following steps:

In versions 4.4x and lower, open Maintenance, and select Menu/Taxes.

In versions 5.0x and higher, open Aloha Manager, and select Maintenance/Menu/Taxes.

Assign the similar exclusive tax in the Smart Tax box for each inclusive tax.

Smart Surcharges

The Aloha application software supports Smart Surcharges in versions 5.2x and higher.� If enabled in Aloha Manager/Store Settings/Financials/Taxes & Surcharges, surcharges are considered inclusive until a non-zero-priced item with an exclusive primary tax is added to the check.

Extended Information

No information.

Caveats

The information in this document does not preclude any local, state, or federal tax laws.� Consult local tax laws before implementing instructions given in this document.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1084

style='mso-spacerun:yes'>� 2003

Basic Gift Certificates

Basic Gift Certificates

============================================================================

AKBID1085

Created: 15 March 2000

Updated: 29 January 2003

Reviewed: 24 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 5.0x � 5.3.x

Subject: Using Basic Gift Certificates in TableService

============================================================================

Summary

The ALOHA^� application software TableService product offers basic gift certificate functionality.� This document explains the creation of new gift certificates, selling gift certificates, gift certificate redemption, and gift certificate tracking.

This document does not cover Aloha Gift Certificate Manager, Aloha eCard, or third-party gift cards.

Information

The Revenue Item feature added to versions 5.2x and higher provides an alternative to using basic gift certificates in QuickService, where basic gift certificate functionality is not available.

Create Gift Certificates

To create gift certificates, open Aloha Manager, and select Maintenance/Payments/Gift Certificates.� If this menu does not exist, select Maintenance/Store Settings/Gift Card-Certificate Sales and enable Aloha Gift Certificates.

When you create a new basic gift certificate, you must use an ID number between 30,200 and 30,299.�

Valid ranges are optional, and each range must have the same number of digits (for example, 100-199, 1000-1999, and so on).� Alphanumeric ranges are valid as long as the last character is numeric (for example, DINING100-DINING199, BAR10-BAR99).�

You must disable the valid ranges if you do not utilize them.� To disable valid ranges, select Maintenance/Store Settings.� Select the Restrictions subtab in the Security group, and select 'No Gift Certificate Numbers'.

Refer to the Aloha TableService User Manual for more information regarding gift certificate creation and options.

Create Gift Certificate Payments

To create gift certificate tenders, open Aloha Manager, and select Maintenance/Payments/Tenders.

Select 'Gift Certificate' for each gift certificate tender.� To select 'Gift Certificates', select Maintenance/Payments/Tenders.� Select the Back Office subtab, and select 'Gift Certificate'.

The Aloha application software does not validate gift certificates (to gift certificates sold) upon redemption.� Validation is restricted to the basic tender validation options available for all tenders, and validation is not required.

To access basic validation settings, select Maintenance/Payments/Tenders.� Edit the gift certificate tender and complete the information on the Identification subtab.

�

Refer to the Aloha TableService User Manual for more information regarding gift certificate tender and validation options.

Sell Gift Certificates

Gift certificates are sold from submenus just as regular items are; however, pricing is defined on the gift certificate level, not the submenu level.

If enabled valid ranges, gift certificate numbers are validated with the assigned range, and they are compared to the gift certificates previously sold.� You cannot sell the same number more than once.

Redeem Gift Certificates

Gift certificate range numbers are not validated against the ranges of previously sold gift certificate, and the same ID number may be used multiple times.

If 'Provide Change' is enabled on the tender, change from overpayment is applied to cash on reports.

If 'Provide Change' is not enabled on the tender, change from overpayment is listed as 'Not Redeemed' or N/R on reports.�

Extended Information

Gift certificate sales and redemption are recorded in the GCLOG.DBF, found in the HISTORY folder.� The Grind process (refer to document AKBID1016) updates the GCLOG.DBF information each time the Grind files are processed.

GCLOG.DBF

Field

Type

Length

Description

DATE

Date

8

Date sold

GC_TYPE_ID

Numeric

10

Gift Certificate ID (Action 1 only)

EMP_NUMBER

Numeric

10

Employee ID

HOUR

Numeric

2

Hour sold

MINUTE

Numeric

2

Minute sold

GIFT_NUM

Character

15

Gift certificate number (if any)

AMOUNT

Numeric

15

Dollar amount

CHECKID

Numeric

10

Check ID

ACTION

Numeric

2

1 if sold, 2 if redeemed

UNIT

Numeric

6

Unit number (Action 1 only)

CERTID

Numeric

10

Unique Gift Certificate ID number (Action 1 only)

OCCASION

Numeric

10

Unique Occasion ID number (Action 1 only)

Caveats

No information.

============================================================================

See also:

Aloha TableService User Manual

AKBID1016 Grind Process and Errors

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1085

style='mso-spacerun:yes'>� 2004

Get Check versus Transfer Check

Get Check versus Transfer Check

============================================================================

AKBID1086

Created: 2 March 2000

Updated: 25 September 2003

Reviewed: 17 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.5x - 5.3.x

Subject: The Differences Between the Get Check Function and the Transfer Check Function

============================================================================

Summary

The ALOHA^� application software offers two ways to transfer checks between Front-of-House (FOH) employees: the Get Check function and the Transfer Check function.� Although each transfers a check from one employee to another, each handles sales attribution in different ways, and each is intended for different uses.

Information

Get Check

The Get Check function, which is enabled in the job code configuration, leaves all sales attributed to the original owner of the check.� It is intended for two uses: a cashiering environment and quick check additions by persons other than the check's owner.

When a cashier uses the Get Check function to retrieve and close a check, the sales remain with the check's original owner, but the financial responsibility transfers to the cashier.� If the cashier adds further sales to the check before closing it, the added sales are attributed to the original check owner, not the cashier.

In order to ensure financial responsibility, the check's sales appear on the checkout for whomever closes the check, but the sales reports (such as the Back-of-House Server Sales Report) will attribute the sales to the check's original owner.

You can also use the Get Check function in cases where a manager or other server may want to quickly grab the check, add an item, and return the check.

By default, the check is manually returned to the owner by touching the Return Check button on the Tenders screen.� The check's original owner must manually accept the returned check.

The 'Auto Return Get Checks' option in the job code setup alleviates extra steps when returning a check.� If this option is enabled, the check is automatically returned to the original owner when you press the Done button or the 'Go to Working with Tables/Tabs Screen' button.� The original owner automatically accepts the check.

The Team Get Check functions in Aloha application software versions 5.2x and higher use the same sales attribution as the standard Get Check function.

Transfer Checks

The Transfer Check function transfers all sales to the new owner of the check.� It is used when a new server is taking full responsibility for the check.

You can disable check transferring abilities for order entry employees, but transfer abilities from the Manager Functions screen are governed by Access Levels.

To disable transferring abilities in versions 4.4x and lower, open Maintenance, select Options/FOH Security Options, and select Disable Transfers.� Refresh the system.

To disable transferring abilities in versions 5.0x and higher, open Aloha Manager, and select Maintenance/Store Settings/Security, and select Disable Transfers.� Refresh the system.

The transferred check is manually accepted by the recipient unless the 'Cashier Auto-Accepts Checks' option is enabled.� The Cashier must have the correct job code options defined in AKBID1053.

An employee with unaccepted-transferred checks or an employee with a check they have not accepted cannot perform a checkout.� The Force Transfer FOH Manager Function transfers responsibility from the check's original owner to the manager forcing the transfer so the employee may check-out if needed.� The recipient must manually accept the check as normal unless the 'Manager Force Transfer' option is enabled.

If 'Manager Force Transfer' is enabled, employees with an access level granting 'Transfer Tables' can also force transfers.

To enable 'Manager Force Transfer' in versions 4.4x and lower, open Maintenance, and select Options/Miscellaneous 1.� Select 'Manager Force Transfer'.

To enable 'Manager Force Transfer' in versions 5.0x and higher, open Aloha Manager, and select Maintenance/Store Settings/Order Entry/Transfers, and select 'Manager Force Transfer'.

You can also apply the following options to transferred checks:

Ask for Transfer Name - Prompts for a check-name when transferring the check.

Require Transfer Name - Requires a check-name when transferring the check.

Transfer Merges Seats - Used in a Pivot Seating environment, this combines the seats with the existing seats when checks are merged, otherwise new seats are created.� Refer to the Aloha Application Software TableService User Manual for more information on pivot seating.

Self Transfer

You can transfer checks to yourself for merging purposes.� Since this option can create a potential employee theft risk, you can disable it in the job code configuration.

Extended Information

Refer to document AKBID1068 for more information on using scanners and barcodes with the Get Check function in a cashiering environment.

Caveats

No information.

============================================================================

See also:

Aloha TableService User Manual

AKBID1053 Table Service Order Entry Job Code Options

AKBID1068 Barcodes and Scanners

AKBID1088 Send All Checks to Local Bartender/Cashier

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1086

style='mso-spacerun:yes'>� 2003

�

Clarifye Export File

Clarifye Export File

============================================================================

AKBID1087

Created: 10 March 2000

Updated: 29 September 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.8x � 5.3.x

Subject: Using the Aloha Application Software Clarifye Export File

============================================================================

Summary

The ALOHA^� application software interfaces to Claret Software�s Clarifye^� wine and beverage management software through an export file created by the Grind process (refer to document AKBID1016) at the end of each business day.

Information

The Aloha application software Grind process creates the Clarifye export file in the Aloha application software CLARIFYE folder.� The file is labeled using the Date-of-Business (DOB), and is in a CLmmddyy.TXT format.

Voided items do not appear in the export file, and items with Comp or Promotions (Promos) applied to them appear with their discounted price.

Versions 4.2x and Lower Setup

In versions 4.2x and lower, you can install the Clarifye software during the Aloha application software installation process.� If you have already installed the Aloha application software, you can install the Clarifye software using SETUP.EXE in the CLARIFYE folder on the Aloha Installation CD.

To enable the Clarifye export file, open Maintenance, and select Miscellaneous 2 from the Options drop-down menu.� Select Export Clarifye to enable the export file, and designate the wine Sales Category as the Clarifye Category.

Refresh the system.

Versions 4.4x and Higher Setup

The Clarifye software is not included on the Aloha Installation CD for versions 4.4x and higher.� Contact Claret Software (www.claretsoftware.com) to purchase the Clarifye software.

Enable the Clarifye export file in the ALOHA.INI.� Edit the ALOHA.INI file in the NEWDATA folder, and add the following lines if they do not already exist:

CLARIFYEEXPORT=TRUE

CLARIFYECATID=n

Replace n with the wine Sales Category (no leading zeros) to export sales from.

Refresh the system.

Manual File Creation

You can manually create the Clarifye export file by regrinding the dated folders.� Refer to document AKBID1016 for more information on regrinding dated folders.

The Clarifye export option must have been enabled during the actual DOB to manually create export files.

Extended Information

Clarifye export file contents:

Field

Maximum Size

Item ID

5

Item Name

25

Quantity

5

Single Item Price

7

Check Number

10

Server Name

15

Revenue Center

14

Terminal Name

15

Terminal ID

3

Number of Guests

Unused

Time

HH:MM

Caveats

The Clarifye export option must have been enabled during the actual DOB to manually create export files.

============================================================================

See also:

Aloha TableService User Manual

AKBID1016 Grind Process and Errors

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1087

�

Send Check to Local Bartender/Cashier

Send Check to Local Bartender/Cashier

============================================================================

AKBID1088

Created: 2 March 2000

Updated: 27 July 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.206 � 5.3.x

Subject: Send Check to Local Bartender/Cashier Job Code Flags

============================================================================

Summary

The ALOHA^� application software job code options for 'Send All Checks to the Local Bartender on Close' and 'Send All Checks to the Local Cashier on Close' are not related, and create entirely different Front-of-House (FOH) behavior.� This document explains the behavior of each feature.

Information

Perform the following to assign the 'Send All Checks to the Local Bartender/Cashier on Close' option to a job code:

In versions 4.4x and lower, open Maintenance, and select Labor/Job Codes/Page 2.

In versions 5.0x and higher, open Aloha Manager, and select Maintenance/Labor/Job Codes/TableService.

Select either 'Send All Checks to the Local Bartender on Close' or Send All Checks to the Local Cashier on Close', and refresh the system.

Send All Checks to Local Bartender on Close

This option forces the system to transfer the check to the bartender when the order-entry employee selects the Close button on the Order Entry screen.� The following rules apply to this function:

1.        The check is transferred to the bartender with the lowest ID number that is currently clocked-in, regardless of bartender cash drawer assignment.

2.        If there are no bartenders clocked-in to the system, the order-entry employee receives an error when they select the Close button.

3.        The order-entry employee can order items, but they cannot close checks without a bartender clocked-in to the system.

4.        The order-entry employee can only open one check at a time.

5.        This option uses normal transfer functionality, which means the sales are transferred along with the check.� Refer to document AKBID1086 for more information.

Send All Checks to Local Cashier on Close

This option does not have any actual transfer capabilities, but it does require a user assigned to the local cash drawer for order-entry employees to close checks.� The following rules apply to this function:

1.        Order-entry employees cannot close a check unless an employee is assigned to a cash drawer on the local terminal.

2.        If there is not an employee assigned to a cash drawer on the local terminal, the order-entry employee receives an error when they select the Close button on the Tenders screen.

3.        The order-entry employee can order items and assign a tender, but they cannot close checks without a employee assigned to the local cash drawer clocked-in.

4.        If two or more employees are assigned to the local cash drawer, the order-entry employees cannot close checks.

5.        The person assigned to the local cash drawer does not have to be a cashier.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha TableService User Manual

AKBID1086 Get Check vs. Transfer Check

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1088

�

Order Attributes

Order Attributes

============================================================================

AKBID1089

Created: 8 March 2000

Updated: 7 December 2000

Reviewed: 18 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 4.215 � 5.3.x

Subject: Using Order Attributes in the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software uses Order Attributes (also known as order codes or sales types) to further specify use of a revenue center.� For example, you might use the dining room revenue center as ala carte service during lunch and buffet service for dinner.� You can use order attributes to break down the dining room revenue center to show ala carte income versus buffet income.

Information

You must manually create a text file to define your order attributes, and then enable them in the Back-of-House (BOH).

Define Order Attributes

Create a new, blank text file in the Data folder labeled Ordattr.txt.� Add each attribute to the text file with a two-digit sequential identification number, a space, and the name of the attribute.� An example of the file contents is shown below:

01 Ala Carte

02 Banquet

03 Special Event

04 Buffet

Enable Order attributes

In versions 4.4x and lower, open Maintenance, and select Options/Miscellaneous 3.

In versions 5.0x and higher, open Aloha Manager.� Select Maintenance/Store Settings/Order Entry Group/Options.

Enable Order Attribute � Implements Order Attribute functionality.

Require Order Attribute � This option applies to job codes with Sees Tabs enabled, but do not have Bartender enabled.� The Front-of-House (FOH) will prompt you for the order attribute when you open a new tab, unless you have defined the Default Selected ID.

Default Selected ID � Highlights the defined order attribute on the selection list.� You can select a different order attribute from the list if the default ID is not applicable.�

Name � Labels the order attribute button, order attribute screen, and guest check label in the FOH.

Front-of-House Usage

Job codes without Sees Tabs or Bartender enabled can assign the order attribute on the Tenders screen.� The order attribute assignment is not forced, and is not assigned unless you manually choose one or you assigned a Default Selected ID in the order attribute configuration options.�

Job codes with Bartender enabled can assign the order attribute on the Tenders screen.� The order attribute assignment is not forced, and is not assigned unless you manually choose one or you assigned a Default Selected ID in the order attribute configuration options.� Fast Cash functionality does not assign an order attribute.

Job codes with Sees Tabs enabled, but do not have Bartender enabled, are forced to select an order attribute if you enabled the Require Order Attribute option and you assigned a Default Selected ID in the order attribute configuration options.� Otherwise, you can assign or change the order attribute on the Tenders screen.

Reports

Order attributes are reported on the BOH Sales Report, but not the FOH reports.

Order attributes are included in the report by selecting 'Sort by Sales Type' for the Number of Guests, Number of Checks, and Sales by Category sections.

Extended Information

Grind Files

The order attribute information is stored in GNDSALE.DBF as a type 46 transaction.� The order attribute ID is stored in the Count field.

Caveats

No information.

============================================================================

See also:

AKBID1053 Table Service Order Entry Job Code Options

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1089

�

Drink Dispensers

Drink Dispensers

============================================================================

AKBID1090

Created: 25 February 2000

Updated: 8 May 2000

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.0x � 5.3.x

Subject: Using Drink Dispensers with the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software supports drink dispensers manufactured by the Berg Company^� and EasyBar Beverage Control.� This document explains the basic configuration required by the Aloha application software.

Information

Define the Drink Dispensers in the Aloha Application Software

Specify the type and location of the drink dispenser in the Aloha application software by performing the following:

In versions 4.4x and lower, open Maintenance, and select MX/Accessories/Drink Dispensers.� Create a new ID number, and specify the name, terminal, port, and type.

In versions 5.0x and higher, open Aloha Manager, and select Maintenance/Hardware/Drink Dispensers.� Create a new ID number, and specify the name, terminal, port, and type.

Hardware Setup

Although it is possible to connect multiple dispensers to multiple serial ports, dispensers are regularly connected together and use a single serial port.� To the Aloha application software, there is effectively one dispenser connected to the POS terminal.

A single Berg Company dispenser can apply drinks to multiple terminals.� Refer to document AKBID1041 for more information.

Type

Baud Rate

Parity

Data Bits

Stop Bits

Cable

Berg Company

2400

Even

7

1

Null modem cable.

EasyBar Beverage Control

9600

None

8

1

Straight-through cable

Items and Pricing

Use the following rules to create and price items in the Aloha application software that interface with the drink dispenser:

1.        Each item that you configure in the drink dispenser software must have a matching item in the Aloha application software with the same item ID number or PLU number.

2.        Do not use modifiers on items that interface to the drink dispenser.��

3.        Use different item and PLU numbers for size variances (for example, small, medium, and large).

4.        You can use Price Levels in the Aloha application software for drink dispenser items, but they are not required.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

Aloha Accessories User Manual

AKBID1041 Multiple Terminal Berg Tap Setup

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1090 automatic bar easy

Windows 2000 Settings Location Quick Guide

Windows 2000 Settings Location Quick Guide

============================================================================

AKBID1091

Created: 25 February 2000

Updated: 16 October 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: Windows 2000

Aloha Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 5.0x � 5.3.x

Subject: The Location of Windows 2000 Settings Used with the Aloha Application Software

============================================================================

Summary

Microsoft^� has relocated many often-used functions and settings in Windows^� 2000.� Many of these settings are routinely accessed when supporting the ALOHA^� application software.� This document describes the new location of these settings.

Information

Some network settings and network functionality may not be available if the Network Interface Adapter (NIC) is not physically connected to a network.

Some setting locations differ between Windows 2000 Server and Windows 2000 Professional.

Disk Management

Windows 2000 Server: Select Start/Programs/Administrative Tools, and select Computer Management.� Expand the Storage tree, and select Disk Management.

Windows 2000 Professional: Select Start/ Settings/Control Panel, and double-click Administrative Tools.� Double-click Computer Management.� Expand the Storage tree, and select Disk Management.

Environment Variables

Select Start/Settings/Control Panel, and double-click System.� Select the Advanced tab, and select Environment Variables.

Modem Configuration

Select Start/Settings/Control Panel, and double-click Phone and Modem Options.� Select the Modems tab.

Network Card Properties

Select Start/Settings/Control Panel, and double-click Network and Dial-up Connections.� Right-click Local Area Connection, and select Properties.

Network Lana Numbers

Users of Windows 2000 must use the LANACFG.EXE utility to view and adjust lana numbers.� Download LANACFG.EXE from the Aloha Technologies FTP site as LANACFG.ZIP.

Place LANACFG.EXE in the Windows folder.

To view the current lana numbers, open a command prompt and navigate to the Windows folder.� Type the following command line:

LANACFG.EXE SHOWLANAPATHS

A list of the current lana numbers is displayed.�� Each lana number is associated with a Network Route.�� Each Network Route will contain a protocol (Nbf for NetBEUI and NetBT for TCP/IP) plus a network adapter.

Find the network route for the Aloha application software to use.� If the incorrect Network Route is assigned to lana number 0, change the number to the next available unused lana number using the following command line:

LANACFG.EXE SETLANANUMBER 0 x

Replace x with the new lana number.

Change the Network Route that the Aloha application software will be using to 0 using the following command line:

LANACFG.EXE SETLANANUMBER y 0

Replace y with the current lana number applied to the Network Route for the Aloha application software to use.

Type the following command line to verify the correct Network Route is assigned to lana 0:

LANACFG.EXE /SHOWLANAPATHS

If the lana numbers are properly assigned, type the following command line to verify and write the new lana information to the registry.

LANACFG.EXE REWRITELANAINFO

Restart the computer.

Network Name and Workgroup

Select Start/Settings/Control Panel, and double-click System.� Select the Network Identification tab.

Network Protocols and IP Address

Select Start/Settings/Control Panel, and double-click Network and Dial-up Connections.� Right-click Local Area Connection, and select Properties.� To access the TCP/IP address, highlight TCP/IP, and select Properties.

NetBIOS must be enabled over TCP/IP to use TCP/IP with the Aloha application software.� This is enabled by selecting Start/Settings/Control Panel, and double-click Network and Dial-up Connections.� Right-click Local Area Connection, and select Properties.� Highlight TCP/IP, and select Properties.� Select the Advanced button, and select the WINS tab.� Select 'Enable NetBIOS over TCP/IP'.

Remote Access Service

Aloha Technologies advises the use of Remote Access Service (RAS) to serve as the primary means of remote support or as a backup to Symantec^� pcANYWHERE^�.

Create a dial-up connection by selecting Start/Settings/Control Panel.� Double-click 'Network and Dial-Up Connections', double-click 'Make New Connection', and select Next.� Select 'Accept incoming connections', and select Next.� Select the remote support modem, and select Next.� Select 'Do not allow virtual private connections', and select Next.� Select Users, set the Callback properties for each user to 'Allow the caller to set the callback number', and select Next.� Select the desired RAS protocols, and select Next.� Select Finish.

Services

Windows 2000 Server: Select Start/Programs/Administrative Tools, and select Computer Management.� Expand the Services and Applications tree, and select Services.

Windows 2000 Professional: Select Start/ Settings/Control Panel, and double-click Administrative Tools.� Double-click Computer Management.� Expand the Services and Applications tree, and select Services.

Startup/Shutdown Options

Select Start/Settings/Control Panel, and double-click System.� Select the Advanced tab, and select Startup and Recovery.

User Management

Windows 2000 Server: Select Start/Programs/Administrative Tools, and select Computer Management.� Expand the System Tools tree, and expand the Local Users and Groups tree.� Select Users.

Windows 2000 Professional: Select Start/ Settings/Control Panel, and double-click Administrative Tools.� Double-click Computer Management.� Expand the System Tools tree, and expand the Local Users and Groups tree.� Select Users.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

AKBID1092 Microsoft Windows 2000 FOH Terminal Setup

AKBID1093 Microsoft Windows 2000 File Server Setup

AKBID1094 Microsoft Windows 2000 File Server/Terminal Setup

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1091 reference

Windows 2000 FOH Terminal Setup

Windows 2000 FOH Terminal Setup

============================================================================

AKBID1092

Created: 20 March 2000

Updated: 17 March 2003

Reviewed: 1 March 2004

Microsoft Windows Versions: Windows 2000

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.017 � 5.3.x

Subject: Windows 2000 FOH Terminal Setup

============================================================================

Summary

The ALOHA^� application software requires several specialized settings (as well as several preferred settings) in the Microsoft^� Windows^� 2000 operating system (OS) to properly run on a terminal.� If you are using the terminal to run both Aloha Front-of-House (FOH) and Back-of-House (BOH) together, refer to document AKBID1094.

The Aloha application software requires the installation of Windows 2000 Service Pack 2 or higher.

Information

This document is written for users familiar with Microsoft Windows 2000.

Since some computers come with Windows 2000 preloaded while others do not, this document is based on editing the settings of Windows 2000.� Users who are installing Windows 2000 from scratch or upgrading another OS to Windows 2000 can still use this document either by employing these instructions after the Windows 2000 installation or by making many of these changes during the Windows 2000 installation.

In regards to the Aloha application software functionality, the only difference between Windows 2000 Server and Windows 2000 Professional is the number of user connections allowed.� Windows 2000 Professional enables up to 10 connections, and you cannot increase this number.� Microsoft Windows 2000 Server limits the number of users to the number of licenses purchased.� Breaking the connection limit may disrupt the Aloha application software.� Refer to AKBID1048 for more information the recommended number of FOH terminals for each operating system.

File System

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

The most important settings in the Aloha application software involve the network settings.

Both Windows 2000 Professional and Windows 2000 Server prompt for either a Domain name or Workgroup name.� Choose a Workgroup name.� Only experienced network administrators should consider using a Domain name.

Set the Workgroup name the same on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the Workgroup name, but this name can be of your choice as long as it is consistent throughout the Aloha application software.� To access the Workgroup name, select Start/Settings/Control Panel, and double-click System.� Select the Network Identification tab.�

Set the terminal�s network name.� Aloha Technologies uses TERM1, TERM2, and so on by default.� Different names may be used, but they must follow Aloha application software specifications.� The terminal name must be a common name used on all terminals (the TERMSTR, refer to document AKBID1010) followed by a number designating the terminal�s ID number.� Examples include ALOHA1, ALOHA2, TSFOH_1, and TSFOH_2.� In this case, the TERMSTR would be 'ALOHA' or 'TSFOH_'.� Different TERMSTR names can not be used within the same Aloha system.� Spaces can not be used, but underscores can.� Leading zeros can not be used unless they are part of the TERMSTR, but it is not recommended.

The Aloha application software uses either TCP/IP or NetBEUI as its network protocol.� Select either one, but both the file server and the terminals must use the same protocol.� To access protocols, select Start/Settings/Control Panel, and double-click 'Network and Dial-Up Connections'.� Right-click 'Local Area Network Connection', and select Properties.

Assign lana number 000 to the protocol used by the Aloha application software.� Refer to document AKBID1018 for more information.

If you select TCP/IP, Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure that terminals always have an address assigned to them.� The Aloha application software will not function without an IP address assigned to the terminal.� You may have multiple protocols installed as long as the proper protocol for the Aloha application software has been marked as such.

NetBIOS must be enabled over TCP/IP to use TCP/IP with the Aloha application software.� To do this, select Start/Settings/Control Panel, and double-click 'Network and Dial-up Connections'.� Right-click 'Local Area Connection', and select Properties.� Select TCP/IP, and select Properties.� Click the Advanced button, and select the WINS tab.� Select 'Enable NetBIOS over TCP/IP'.

TCP/IP Media Sense

Windows 2000 uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.�

Perform the following to disable Media Sense in the Windows Registry:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters.

3.        Verify the DisableDHCPMediaSense value exists in the folder.� If it does, double-click it and change Value Data to '1'.� If it does not exist, choose Edit/New/DWORD Value and name the key ' DisableDHCPMediaSense '.� Then double-click the entry and change Value Data to '1'.

4.        Select Registry/Exit to exit the Windows Registry Editor.

5.        Restart Windows.�

Media Sense provides the ability to connect to networks with different DHCP options in one Windows session without the need to release and renew the IP configuration by using IPCONFIG.EXE.� If you disable Media Sense, no new IP configuration information is obtained when you connect to a new network unless you restart the computer, or you release and renew the IP configuration by using IPCONFIG.EXE.

Refer to Microsoft Knowledge Base document Q239924 for more information on Media Sense.

Aloha Share Name

The Aloha application software requires a network share name of BOOTDRV.� This is the required name.� This share needs to be applied to the root folder or drive in which the Aloha folder resides.� To set the share, right-click the drive or folder and choose Sharing.� Set the Share Name to BOOTDRV.

If the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.� Some clients prefer to place the Aloha application software in a special folder in order to limit the shared files, and, therefore, enhance security.� Sharing the entire drive in which the Aloha application software resides also shares other files that reside on the drive, such as Windows.

Display Settings

To access the Display settings, select Start/Settings/Control Panel/Display or right-click the Windows desktop and select Properties.� Select the Settings tab.� Set the Color palette to 256 Colors or higher.� Aloha Technologies typically uses 16-bit color.�

Refer to document AKBID1165 for screen resolution settings.

Do not enable a Windows screen saver.

Time Zone & Daylight Savings

For the file server and all terminals to display the correct time and adjust to Daylight Savings changes properly, the Time and Date settings must be properly configured in Windows.� Select Start/Settings/Control Panel/Date/Time or double-click the time displayed on the task bar.� Ensure the date and time are correct.� Ensure the date and time are correct on the Date & Time tab.� Ensure the correct time zone is chosen on the Time Zone tab.� This time zone needs to be the same on all terminals and the file server.� If the area observes Daylight Savings, then the 'Automatically adjust clock for daylight savings changes' option must be selected on all terminals and the file server.� This can be turned on or off, but it needs to be consistent throughout the Aloha application software.

FIFO Buffers

Windows 2000 enables First-In-First-Out (FIFO) buffers for each COM port.� These buffers tend to interfere with printers using Xon/Xoff flow control, so Aloha Technologies disables these buffers on all COM ports on all terminals, regardless of the printer type.� (In the event of a printer or COM port failure, a printer using Xon/Xoff flow control may be temporally connected to the port in the future.)

To access the FIFO buffer settings, select Start/Settings/Control Panel/System or right click My Computer and select Properties.� Select Hardware/Device Manager, and click the plus sign (+) next to Ports to expand it.� Select each port one at a time, and select Properties/Port Settings/Advanced. �Clear 'Use FIFO buffer'.� Repeat for each COM port.� The LPT port does not have this option.

Login Name

Refer to document AKBID1006 for more information on configuring Windows logins for the Aloha application software.

Install Aloha Software

Once Windows 2000 is set up according to the standards outlined in this document and you can view the network, use the terminal installation diskette to install the Aloha application software.

To create this diskette, insert the installation CD in the file server�s CD-ROM, and run SETUPPOS.EXE /ADVANCED.� Select Make Diskettes/Create Terminal Installation Diskette from the Main Menu

Once the diskette is created, insert it into the terminal�s floppy drive, and run SETUPTRM.EXE.� The setup program walks you through the rest of the installation.

If the terminal does not have a floppy drive, run the Terminal Installation application directly from the CD-ROM on the file server.� Map a drive to the CD-ROM on the file server.� Do not choose the Reconnect at Logon option when mapping the drive.� Run the file \TERMINST\SETUPTRM.EXE from the Aloha POS CD.� The setup program walks you through the rest of the installation.

Service Pack

Install Windows 2000 Service Pack 2 or higher after all software has been installed and Windows 2000 is configured properly.�

Reinstall the Service Pack anytime significant changes are made to Windows 2000.

Set Control Server and EDC Server Login on the File Server

You may need to adjust the login account used by CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) on the file server to ensure proper operation with terminals running Windows 2000.� Refer to AKBID1197 for more information.

Enable a Hotplugged Keyboard

By default, Windows 2000 does not enable you to hotplug a keyboard if Windows has already started without a keyboard attached.� You can change this behavior and enable hotplugging a keyboard by installing Windows 2000 Service Pack 3 or higher, and performing the following to edit the Windows registry:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

Path out HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\i8042prt\Parameters.

Verify the Headless value exists in the folder.� If it does, double-click it and change Value Data to '1'.� If it does not exist, choose Edit/New/DWORD Value and name the key 'Headless'.� Then double-click the entry and change Value Data to '1'.

Select Registry/Exit to exit the Windows Registry Editor.

Restart Windows.

Extended Information

Windows Explorer starts in the My Documents folder by default.� Add ' /n,/e' to the EXPLORER.EXE command line and shortcuts in order for Explorer to default to C:\.� For example:

%systemroot%\explorer.exe /n,/e

Caveats

The Aloha application software requires the installation of Windows 2000 Service Pack 2 or higher.

Both Windows 2000 Professional and Windows 2000 Server prompt for either a Domain name or Workgroup name.� Choose a Workgroup name.� Only experienced network administrators should consider using a Domain name.

Windows 2000 uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.� To eliminate this, disable Media Sense.

============================================================================

See also:

AKBID1005 Microsoft Windows Automatic Log In

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1010 Aloha Application Software System Environment Variables

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1018 Network Lana Numbers

AKBID1048 Aloha Application Software Hardware and OS Specifications

AKBID1093 Windows 2000 File Server Setup

AKBID1094 Windows 2000 Server/Terminal Setup

AKBID1165 FOH Screen Resolution Settings

AKBID1175 Aloha Terminal Restart Options

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1197 Assigning Logins to Aloha Services

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1092 stage staging

Windows 2000 File Server Setup

Windows 2000 File Server Setup

============================================================================

AKBID1093

Created: 20 March 2000

Updated: 11 April 2003

Reviewed: 2 March 2004

Microsoft Windows Versions: Windows 2000

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.017 � 5.3.x

Subject: Windows 2000 File Server Setup

============================================================================

Summary

The ALOHA^� application software requires several specialized settings (as well as several preferred settings) in the Microsoft^� Windows^� 2000 operating system (OS) to properly run on the file server.� If you are using the file server to run both Aloha Front-of-House (FOH) and Back-of-House (BOH) together, refer to document AKBID1094.

The Aloha application software requires the installation of Windows 2000 Service Pack 2 or higher.

Information

This document is written for users familiar with Microsoft Windows 2000.

Since some computers come with Windows 2000 preloaded while others do not, this document is based on editing the settings of Windows 2000.� Users who are installing Windows 2000 from scratch or upgrading another OS to Windows 2000 can still use this document either by employing these instructions after the Windows 2000 installation or by making many of these changes during the Windows 2000 installation.

In regards to the Aloha application software functionality, the only difference between Windows 2000 Server and Windows 2000 Professional is the number of user connections allowed.� Windows 2000 Professional enables up to 10 connections, and you cannot increase this number.� Microsoft Windows 2000 Server limits the number of users to the number of licenses purchased.� Breaking the connection limit may disrupt the Aloha application software.� Refer to AKBID1048 for more information the recommended number of FOH terminals for each operating system.

Drive Sizes and Partitions

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

The most important settings in the Aloha application software involve the network settings.

Both Windows 2000 Professional and Windows 2000 Server prompt for either a Domain name or Workgroup name.� Choose a Workgroup name.� Only experienced network administrators should consider using a Domain name.

Set the Workgroup name the same on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the Workgroup name, but this name can be of your choice as long as it is consistent throughout the Aloha application software.� To access the Workgroup name, select Start/Settings/Control Panel, and double-click System.� Select the Network Identification tab.�

Aloha Technologies uses the network name ALOHABOH by default.� A different name can be used if desired.� To access the network name, select Start/Settings/Control Panel.� Double-click System, and select the Network Identification tab.

The Aloha application software uses either TCP/IP or NetBEUI as its network protocol.� Select either one, but both the file server and the terminals must use the same protocol.� To access protocols, select Start/Settings/Control Panel, and double-click 'Network and Dial-Up Connections'.� Right-click 'Local Area Network Connection', and select Properties.

Assign lana number 000 to the protocol used by the Aloha application software.� Refer to document AKBID1018 for more information.

If you select TCP/IP, Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure that terminals always have an address assigned to them.� The Aloha application software will not function without an IP address assigned to the terminal.� You may have multiple protocols installed as long as the proper protocol for the Aloha application software has been marked as such.

NetBIOS must be enabled over TCP/IP to use TCP/IP with the Aloha application software.� To do this, select Start/Settings/Control Panel, and double-click 'Network and Dial-up Connections'.� Right-click 'Local Area Connection', and select Properties.� Select TCP/IP, and select Properties.� Click the Advanced button, and select the WINS tab.� Select 'Enable NetBIOS over TCP/IP'.

TCP/IP Media Sense

Windows 2000 uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.�

Perform the following to disable Media Sense in the Windows Registry:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters.

3.        Verify the DisableDHCPMediaSense value exists in the folder.� If it does, double-click it and change Value Data to '1'.� If it does not exist, choose Edit/New/DWORD Value and name the key ' DisableDHCPMediaSense '.� Then double-click the entry and change Value Data to '1'.

4.        Select Registry/Exit to exit the Windows Registry Editor.

5.        Restart Windows.�

Media Sense provides the ability to connect to networks with different DHCP options in one Windows session without the need to release and renew the IP configuration by using IPCONFIG.EXE.� If you disable Media Sense, no new IP configuration information is obtained when you connect to a new network unless you restart the computer, or you release and renew the IP configuration by using IPCONFIG.EXE.

Refer to Microsoft Knowledge Base document Q239924 for more information on Media Sense.

Aloha Share Name

The Aloha application software requires a network share name of BOOTDRV.� This is the required name.� This share needs to be applied to the root folder or drive in which the Aloha folder resides.� To set the share, right-click on the drive or folder and choose Sharing.� Set the Share Name to BOOTDRV.

If the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.� Some clients prefer to place the Aloha application software in a special folder in order to limit the shared files, and, therefore, enhance security.� Sharing the entire drive in which the Aloha application software resides also shares other files that reside on the drive, such as Windows.

Display Settings

To access the Display settings, select Start/Settings/Control Panel/Display or right-click the Windows desktop and select Properties.� Select the Settings tab.� Set the Color palette to 256 Colors or higher.� Aloha Technologies typically uses 16-bit color.� The Aloha application software can be run on both a 640x480 pixel display and an 800x600 pixel display, however, Aloha Technologies prefers 800x600 (or better) resolution.

Aloha Technologies typically does not use a screen saver on the file server since some screen savers (the Open GL based screen savers in particular) can sap processor speed.

Time Zone & Daylight Savings

For the file server and all terminals to display the correct time and adjust to Daylight Savings changes properly, the Time and Date settings must be properly configured in Windows.� Select Start/Settings/Control Panel/Date/Time or double-click the time displayed on the task bar.� Ensure the date and time are correct.� Ensure the date and time are correct on the Date & Time tab.� Ensure the correct time zone is chosen on the Time Zone tab.� This time zone needs to be the same on all terminals and the file server.� If the area observes Daylight Savings, then the 'Automatically adjust clock for daylight savings changes' option must be selected on all terminals and the file server.� This can be turned on or off, but it needs to be consistent throughout the Aloha application software.

Login Name

Refer to document AKBID1006 for more information on configuring Windows logins for the Aloha application software.

Processor Performance

By default, Windows 2000 is configured to assign foreground applications priority processing.� This can cause erroneous behavior in background applications, such as Control Server and EDC Server.� Aloha Technologies suggests setting the processor priority to background applications.

To configure the processor priority, open the System properties and select Advanced/Performance Options, and set the application response to Background Services.

Install Aloha Software

Once Windows 2000 is set up to the standards outlined in this document and you can view the network, use the Aloha Application Software Installation CD to install the Aloha application software.

Run SETUPPOS.EXE /ADVANCED from the Aloha POS CD.� The setup program walks you through the rest of the installation.

Refer to document AKBID1162 for more information on running Control Server and EDC Server as Windows services.

Service Pack

Install Windows 2000 Service Pack 2 or higher after all software has been installed and Windows 2000 is configured properly.�

Reinstall the Service Pack anytime significant changes are made to Windows 2000.

Set Control Server and EDC Server Login

If you are running Windows 98, Windows NT^� or Windows 2000 on your FOH terminals, you may need to adjust the login account used by CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) on the file server to ensure proper operation.� Refer to AKBID1197 for more information.

Extended Information

EOD File Copy Errors

If you are experience problems where the End-of-Day (EOD) process fails to copy files, you should perform the following in order to disable write caching for the hard drive in which the Aloha application software resides on the file server:

Open Windows Explorer, right-click on the hard drive in which the Aloha application software is installed, and select Properties.

Select the Hardware tab.

Select the physical drive, and select Properties.

Select the Disk Properties tab.

Clear the 'Write cache enabled' option, and press OK.

Caveats

The Aloha application software requires the installation of Windows 2000 Service Pack 2 or higher.

Both Windows 2000 Professional and Windows 2000 Server prompt for either a Domain name or Workgroup name.� Choose a Workgroup name.� Only experienced network administrators should consider using a Domain name.

Windows 2000 uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.� To eliminate this, disable Media Sense.

============================================================================

See also:

AKBID1005 Microsoft Windows Automatic Log In

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1010 Aloha Application Software System Environment Variables

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1018 Network Lana Numbers

AKBID1027 Windows NT/Windows 2000 Auto Backup

AKBID1028 Winhook

AKBID1048 Aloha Application Software Hardware and OS Specifications

AKBID1092 Windows 2000 FOH Terminal Setup

AKBID1094 Windows 2000 Server/Terminal Setup

AKBID1148 Backup Procedures

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1197 Assigning Logins to Aloha Services

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1093 stage staging

Windows 2000 File Server/Terminal Setup

Windows 2000 File Server/Terminal Setup

============================================================================

AKBID1094

Created: 20 March 2000

Updated: 16 April 2003

Reviewed: 1 March 2004

Microsoft Windows Versions: Windows 2000

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.017 � 5.3.x

Subject: Microsoft Windows 2000 File Server and Terminal on the Same Computer Setup

============================================================================

Summary

The ALOHA^� application software requires several specialized settings (as well as several preferred settings) in the Microsoft^� Windows^� 2000 operating system (OS) to properly run on the run both Aloha Front-of-House (FOH) and Back-of-House (BOH) together on the same computer.� If you are using the computer as a file server only, refer to document AKBID1093.� If you are using the computer as a terminal only, refer to document AKBID1092.

Refer to document AKBID1116 for more information on the limitations of running both the FOH and BOH together on the same PC.

The Aloha application software requires the installation of Windows 2000 Service Pack 2 or higher.

Information

This document is written for users familiar with Microsoft Windows 2000.

Since some computers come with Windows 2000 preloaded while others do not, this document is based on editing the settings of Windows 2000.� Users who are installing Windows 2000 from scratch or upgrading another OS to Windows 2000 can still use this document either by employing these instructions after the Windows 2000 installation or by making many of these changes during the Windows 2000 installation.

If you are converting an existing file server to a file server/terminal, refer to the Extended Information section of this document.

In regards to the Aloha application software functionality, the only difference between Windows 2000 Server and Windows 2000 Professional is the number of user connections allowed.� Windows 2000 Professional enables up to 10 connections, and you cannot increase this number.� Microsoft Windows 2000 Server limits the number of users to the number of licenses purchased.� Breaking the connection limit may disrupt the Aloha application software.� Refer to AKBID1048 for more information the recommended number of FOH terminals for each operating system.

Drive Sizes and Partitions

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

The most important settings in the Aloha application software involve the network settings.

Both Windows 2000 Professional and Windows 2000 Server prompt for either a Domain name or Workgroup name.� Choose a Workgroup name.� Only experienced network administrators should consider using a Domain name.

Set the Workgroup name the same on all terminals and the file server/terminal.� Aloha Technologies generally uses IBERTECH as the Workgroup name, but this name can be of your choice as long as it is consistent throughout the Aloha application software.� To access the Workgroup name, select Start/Settings/Control Panel, and double-click System.� Select the Network Identification tab.�

Set the file server/terminal�s network name.� Aloha Technologies uses TERM1, TERM2, and so on by default.� Different names may be used, but they must follow Aloha application software specifications.� The terminal name must be a common name used on all terminals (the TERMSTR, refer to document AKBID1010) followed by a number designating the terminal�s ID number.� Examples include ALOHA1, ALOHA2, TSFOH_1, and TSFOH_2.� In this case, the TERMSTR would be 'ALOHA' or 'TSFOH_'.� Different TERMSTR names can not be used within the same Aloha system.� Spaces can not be used, but underscores can.� Leading zeros can not be used unless they are part of the TERMSTR, but it is not recommended.� The file server/terminal is usually terminal 1.

The Aloha application software uses either TCP/IP or NetBEUI as its network protocol.� Select either one, but both the file server/terminal and the terminals must use the same protocol.� To access protocols, select Start/Settings/Control Panel, and double-click 'Network and Dial-Up Connections'.� Right-click 'Local Area Network Connection', and select Properties.

Assign lana number 000 to the protocol used by the Aloha application software.� Refer to document AKBID1018 for more information.

If you select TCP/IP, Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure that terminals always have an address assigned to them.� The Aloha application software will not function without an IP address assigned to the terminal.� You may have multiple protocols installed as long as the proper protocol for the Aloha application software has been marked as such.

NetBIOS must be enabled over TCP/IP to use TCP/IP with the Aloha application software.� To do this, select Start/Settings/Control Panel, and double-click 'Network and Dial-up Connections'.� Right-click 'Local Area Connection', and select Properties.� Select TCP/IP, and select Properties.� Click the Advanced button, and select the WINS tab.� Select 'Enable NetBIOS over TCP/IP'.

TCP/IP Media Sense

Windows 2000 uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.�

Perform the following to disable Media Sense in the Windows Registry:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk. �

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters.

3.        Verify the DisableDHCPMediaSense value exists in the folder.� If it does, double-click it and change Value Data to '1'.� If it does not exist, choose Edit/New/DWORD Value and name the key ' DisableDHCPMediaSense '.� Then double-click the entry and change Value Data to '1'.

4.        Select Registry/Exit to exit the Windows Registry Editor.

5.        Restart Windows.�

Media Sense provides the ability to connect to networks with different DHCP options in one Windows session without the need to release and renew the IP configuration by using IPCONFIG.EXE.� If you disable Media Sense, no new IP configuration information is obtained when you connect to a new network unless you restart the computer, or you release and renew the IP configuration by using IPCONFIG.EXE.�

Refer to Microsoft Knowledge Base document Q239924 for more information on Media Sense.

Aloha Share Name

The Aloha application software requires a network share name of BOOTDRV.� This is the required name.� This share needs to be applied to the root folder or drive in which the Aloha folder resides.� To set the share, right-click on the drive or folder and choose Sharing.� Set the Share Name to BOOTDRV.

If the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV. �For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.� Some clients prefer to place the Aloha application software in a special folder in order to limit the shared files, and, therefore, enhance security.� Sharing the entire drive in which the Aloha application software resides also shares other files that reside on the drive, such as Windows.

Display Settings

To access the Display settings, select Start/Settings/Control Panel/Display or right-click the Windows desktop and select Properties.� Select the Settings tab.� Set the Color palette to 256 Colors or higher.� Aloha Technologies typically uses 16-bit color.�

Refer to document AKBID1165 for screen resolution settings.

Do not enable a Windows screen saver.

Time Zone & Daylight Savings

For the file server/terminal and all terminals to display the correct time and adjust to Daylight Savings changes properly, the Time and Date settings must be properly configured in Windows.� Select Start/Settings/Control Panel/Date/Time or double-click the time displayed on the task bar.� Ensure the date and time are correct.� Ensure the date and time are correct on the Date & Time tab.� Ensure the correct time zone is chosen on the Time Zone tab.� This time zone needs to be the same on all terminals and the file server/terminal.� If the area observes Daylight Savings, then the 'Automatically adjust clock for daylight savings changes' option must be selected on all terminals and the file server/terminal.� This can be turned on or off, but it needs to be consistent throughout the Aloha application software.

FIFO Buffers

Windows 2000 enables First-In-First-Out (FIFO) buffers for each COM port.� These buffers tend to interfere with printers using Xon/Xoff flow control, so Aloha Technologies disables these buffers on all COM ports on all terminals, regardless of the printer type.� (In the event of a printer or COM port failure, a printer using Xon/Xoff flow control may be temporally connected to the port in the future.)

To access the FIFO buffer settings, select Start/Settings/Control Panel/System or right click My Computer and select Properties.� Select Hardware/Device Manager, and click the plus sign (+) next to Ports to expand it.� Select each port one at a time, and select Properties/Port Settings/Advanced.� Clear 'Use FIFO buffer'.� Repeat for each COM port.� The LPT port does not have this option.

Login Name

Refer to document AKBID1006 for more information on configuring Windows logins for the Aloha application software.

Processor Performance

By default, Windows 2000 is configured to assign foreground applications priority processing.� This can cause erroneous behavior in background applications, such as Control Server and EDC Server.� Aloha Technologies suggests setting the processor priority to background applications, but this can affect the FOH, which is also running on the file server.� If you experience problems with Control Server or EDC Server that you can attribute to processor time, consider changing the processor priority.

To configure the processor priority, open the System properties and select Advanced/Performance Options, and set the application response to Background Services.

Install Aloha Software

Once Windows 2000 is set up according to the standards outlined in this document and you can view the network, use the Aloha Application Software Installation CD to install the Aloha application software.

Run SETUPPOS.EXE /ADVANCED from the Aloha POS CD.� The setup program walks you through the rest of the installation. �You must select 'Run Front of House and Back of House on same PC' on the Aloha Configuration window.

Refer to document AKBID1162 for more information on running Control Server and EDC Server as Windows services.

Aloha Application Software Versions 4.2x � 5.0x

Perform the following to remove the NONET variable from the Control Server variables in the Windows Registry:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_CLASSES_ROOT\AppId\{81DD90A1-CF22-11D1-A84F-0080AD1C6910}.

3.        Then double-click AlohaCtlSrvParameters and remove the NONET variable from Value Data.

4.        Select Registry/Exit to exit the Windows Registry Editor

Restarting the FOH

Refer to document AKBID1116 for more information regarding restarting the FOH in this type of environment.�

Service Pack

Install Windows 2000 Service Pack 2 or higher after all software has been installed and Windows 2000 is configured properly.�

Reinstall the Service Pack anytime significant changes are made to Windows 2000.

Extended Information

Converting an Existing File Server to a File Server/Terminal

The steps for converting an existing file server to a file server/terminal depend on the usage.

If you are not going to make the file server/terminal master or server-capable (such as a COM interface server or a remote print server), then you can just add the MASTERCAPABLE, SERVERCAPABLE, LOCALDIR, TERM, CALIBRATE, and IBERROOT variables to the system environment variables and assign the proper values to them; and optionally configure a looping batch file to restart the FOH (refer to document AKBID1116).

If at any time you will make the file server/terminal master and/or server-capable, then you must add the MASTERCAPABLE, SERVERCAPABLE, LOCALDIR, TERM, CALIBRATE, and IBERROOT variables to the system environment variables and assign the proper values to them; rename the file server/terminal to match the TERMSTR+TERM nomenclature (Aloha Technologies suggests making it terminal one); and optionally configure a looping batch file to restart the FOH (refer to document AKBID1116).

EOD File Copy Errors

If you are experience problems where the End-of-Day (EOD) process fails to copy files, you should perform the following in order to disable write caching for the hard drive in which the Aloha application software resides on the file server:

Open Windows Explorer, right-click on the hard drive in which the Aloha application software is installed, and select Properties.

Select the Hardware tab.

Select the physical drive, and select Properties.

Select the Disk Properties tab.

Clear the 'Write cache enabled' option, and press OK.

Caveats

The Aloha application software requires the installation of Windows 2000 Service Pack 2 or higher.

Both Windows 2000 Professional and Windows 2000 Server prompt for either a Domain name or Workgroup name.� Choose a Workgroup name.� Only experienced network administrators should consider using a Domain name.

Windows 2000 uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.� To eliminate this, disable Media Sense.

============================================================================

See also:

AKBID1005 Microsoft Windows Automatic Log In

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1010 Aloha Application Software System Environment Variables

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1018 Network Lana Numbers

AKBID1027 Windows NT/Windows 2000 Auto Backup

AKBID1028 Winhook

AKBID1048 Aloha Application Software Hardware and OS Specifications

AKBID1092 Windows 2000 FOH Terminal Setup

AKBID1093 Windows 2000 File Server Setup

AKBID1116 File Server/Terminal Limitations

AKBID1148 Backup Procedures

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1165 FOH Screen Resolution Settings

AKBID1175 Aloha Terminal Restart Options

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1094 boh/foh bohfoh foh/boh fohboh stage staging terminal/server

Stand-Alone EDC File Server

Stand-Alone EDC File Server

============================================================================

AKBID1095

Created: 22 March 2000

Updated: 17 February 2004

Reviewed: 17 February 2004

Microsoft^� Windows^� Versions: Windows NT^�, Windows 2000, Windows XP, Windows Server 2003

Aloha Products: EDC

Aloha POS Versions: 5.0x � 5.3.x

Subject: Configuring an Aloha Application Software Stand-Alone EDC File Server

============================================================================

Summary

You can configure the ALOHA^� application software Electronic Draft Capture (EDC) application on a separate computer from the Aloha application software file server.� This is helpful at locations (mainly SuperSites) where the Aloha application software file server can become overburdened running both the Aloha application software Back-of-House (BOH) and EDC.� It also increases the Aloha application software fault tolerance capabilities by eliminating a single point of failure for both the POS file server and the EDC file server.�

This document is intended for use with a SuperSite or with a single TableService or QuickService site.� If you are configuring a shared POS and EDC file server for use with multiple stores or concepts such as two restaurants next to each other, refer to document AKBID1123.� If you are configuring a single dedicated EDC file server for use with multiple stores or concepts such as two restaurants next to each other sharing a single dedicated EDC file server, refer to document AKBID1174.

Information

Network

Establish a TCP/IP or NetBEUI network connection between the EDC file server and POS file server.� The EDC file server must use the same network protocol as the rest of the Aloha application software, and the Front-of-House (FOH) terminals must have access to the EDC file server.

Configure DCOM

Install and configure Distributed Component Object Model (DCOM) on the EDC server.� Refer to document AKBID1049 for more information about configuring DCOM.

Configure Internet Explorer 4.0 SP2 (5.2x and higher)

If you are using the Aloha application software version 5.2x or higher, configure Microsoft Internet Explorer 4.0 Service Pack 2 or higher using the source files on the Aloha Installation CD.� Do not overwrite newer versions of Internet Explorer.

Create Aloha Folder and BOOTDRV Share

Create an Aloha application software folder on the EDC file server with the same name as the Aloha application software folder on the POS file server, and create the BOOTDRV share based on the folder location.� Although the EDC file server requires a share name so the FOH terminals may access it, it not required you use the BOOTDRV label.� Using the BOOTDRV label, though, creates constancy with the other Aloha application software computers on the network.

If the Aloha application software folder resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the 'POS' folder as BOOTDRV.� Some clients prefer to place the Aloha application software in a special folder in order to limit the shared files and thus, enhance security.� Sharing the entire drive in which the Aloha application software resides also shares other files that reside on the drive such as Windows.

Create Sub-Folders and Copy Files

Create BIN, DATA, EDC, NEWDATA, and TMP folders inside the Aloha application software folder on the EDC file server.

Copy the following files from the BIN folder on the POS file server to the BIN folder on the EDC file server: ALOHASEC.EXE, ARSEC.DLL, ARSECPS.DLL, ASECPS.DLL, CB532.DLL, EDC.EXE, EDCSEC.DLL, EDCSVR.EXE, EDCSVRPS.DLL, IBERSTR.DLL (5.2x and higher) and SHW32.DLL.

Copy the following files from the NEWDATA folder on the POS file server to the NEWDATA folder on the EDC file server: ALOHA.INI, EMP*.*, SECLVL*.*, STO.*, TRM.*, and VER.*.

Copy the following files from the DATA folder on the POS file server to the DATA folder on the EDC file server: ALOHA.INI, EMP*.*, SECLVL*.*, STO.*, TRM.*, and VER.*.

Copy System Files

EDC requires system files in the Windows SYSTEM32 folder, but since current copies of the files may be in use by Windows, you can not copy the new ones to the SYSTEM32 folder.

To alleviate this problem, download SETUPSYS.EXE from the Aloha Technologies FTP site as SETUPSYS.ZIP (refer to document AKBID1012) or use the copy of SETUPSYS.EXE from the \MISC\SETUPSYS folder on the Aloha Installation CD.

Extract the system files from WNTDLL.ZIP and WNTDLL2.ZIP in the ALOHATS folder on the Aloha Installation CD, and place them in a temporary folder on the same drive partition as the Windows folder.� Open SETUPSYS.EXE, define the location of the temporary folder where the system files reside, and install the files.� Restart the computer.

Environment Variables

Add the following to the system environment variables on the EDC file server and restart the system:

Variable

Assignment

EDCPATH

The path to the local EDC folder (for example, D:\ALOHA\EDC)

IBERDIR

The local Aloha application software folder path (for example, C:\ALOHA)

IBERROOT

The local Aloha application software folder label (for example, ALOHA)

POSPATH

The path to the Aloha application software folder on the POS file server (for example, \\ALOHABOH\BOOTDRV\ALOHA)

TERMSTR

This is only required if you are not in a SuperSite environment.� The root name used in the terminal naming convention (for example, TERM)

Also add the local Aloha application software BIN folder to the existing system path.

Restart the computer.

Register ATL.DLL

Open a command prompt, and navigate to the Windows SYSTEM32 folder.� Type the following command line to register ATL.DLL (a successful confirmation should follow the registration):

ATL.DLL must be registered before other applications and .DLL files are registered.

REGSVR32.EXE ATL.DLL

Install EDC Server and Security Server

To install EDCSVR.EXE (EDC Server) and ALOHASEC.EXE, type the following from a command line:

%IBERDIR%\BIN\EDCSVR.EXE /SERVICE

%IBERDIR%\BIN\ALOHASEC.EXE /REGSERVER

If you are using EDC Server versions 5.230 and higher, EDC Server prompts you for the user configuration.� This is the user with which EDC Server will log in.� You can instruct EDC Server to use the Windows local system account (the default configuration in versions 5.229 and lower) or you can configure a specific user name and password.� You must configure a specific login in instances where the operating system on the FOH terminals does not enable network access by the Windows local system account.�

You can use the /LOCALACCOUNT command line variable to instruct EDC Server to register using the Windows local system account without prompting the user.� For example:

%IBERDIR%\BIN\EDCSVR.EXE /SERVICE /LOCALACCOUNT

You can use the /ACCOUNTNAME and /PASSWORD command line variables to instruct EDC Server to register using a specific user name and password.� For example:

EDCSVR.EXE /SERVICE /ACCOUNTNAME .\<user name> /PASSWORD <password>

If you are using a domain account, you can specify the domain name using the following command line:

EDCSVR.EXE /SERVICE /ACCOUNTNAME <domain name>\<user name> /PASSWORD <password>

Register DLL Files

Open a command prompt, and navigate to the BIN folder.� Type the following command lines to register Aloha application software .DLL files (a successful confirmation should follow the registration):

REGSVR32.EXE ARSEC.DLL

REGSVR32.EXE ARSECPS.DLL

REGSVR32.EXE ASECPS.DLL

REGSVR32.EXE EDCSEC.DLL

REGSVR32.EXE EDCSVRPS.DLL

Restart the computer.

Updating EDC POS Configuration Files

The EDC file server uses configuration files from the POS file server.� To ensure these files are up to date, Aloha Technologies suggests creating the following EDC.CMD file to shut down EDC, update the files, and restart EDC:

IF EXIST %POSPATH%\DATA\ALOHA.INI GOTO RESTART

GOTO END

:RESTART

START /WAIT CLOSEAPP.EXE /QUIT ALOHA EDC

START /WAIT NET STOP EDCSVR

COPY %POSPATH%\NEWDATA\ALOHA.INI %IBERDIR%\NEWDATA

COPY %POSPATH%\NEWDATA\EMP*.* %IBERDIR%\NEWDATA

COPY %POSPATH%\NEWDATA\SECLVL*.* %IBERDIR%\NEWDATA

COPY %POSPATH%\NEWDATA\STO.* %IBERDIR%\NEWDATA

COPY %POSPATH%\NEWDATA\TRM.* %IBERDIR%\NEWDATA

COPY %POSPATH%\NEWDATA\VER.* %IBERDIR%\NEWDATA

COPY %POSPATH%\DATA\ALOHA.INI %IBERDIR%\DATA

COPY %POSPATH%\DATA\EMP*.* %IBERDIR%\DATA

COPY %POSPATH%\DATA\SECLVL*.* %IBERDIR%\DATA

COPY %POSPATH%\DATA\STO.* %IBERDIR%\DATA

COPY %POSPATH%\DATA\TRM.* %IBERDIR%\DATA

COPY %POSPATH%\DATA\VER.* %IBERDIR%\DATA

START /WAIT NET START EDCSVR

%IBERDIR%\BIN\EDC.EXE

:END

EXIT

Note the use of the POSPATH environment variable (discussed previously) and CLOSEAPP.EXE.� Download the CLOSEAPP.EXE utility from the Aloha Technologies FTP site, and refer to document AKBID1012 for more information.�

Use the Windows Schedule Service (refer to document AKBID1047) to initialize the file each night.� Windows 2000 users can instead employ Window Task Scheduler to initialize the file each night.

Users may also consider adding a shortcut to EDC.CMD to the Windows Desktop of the Aloha start menu folder so users can manually update the data.

EDC Shortcuts

Create an 'Aloha Credit Cards' (EDC.EXE) shortcut on the desktop, start menu, and anywhere else it is needed.� A shortcut to EDC is not required in the Windows StartUp folder since EDC is registered as a Windows service.

A shortcut to EDC.CMD is not required since it is activated by the Windows Schedule Service.

FOH Terminal Settings

Add or adjust the EDCPATH variable on the POS terminals to provide the path to the EDC folder on the EDC file server.� For example, SET EDCPATH=\\EDCSERVER\BOOTDRV\ALOHA\EDC.

Upgrading EDC.EXE

Upgrades to the Aloha application software on the EDC file server requires replacement and registration of all application files and .DLL files listed previously in this document.�

Multiple EDC File Servers in a SuperSite

If you have configured multiple EDC file servers to run simultaneously in a SuperSite (for example, file server one covers stores 1-10 and file server two covers stores 11-20), then you must use a TRM.DBF specific only to the file server's target terminals on each EDC file server in order to ensure that each EDC file server exclusively serves its specific stores.� If you use a site-wide TRM.DBF, then each EDC file server will attempt to process spooled transactions from all stores (including the stores serviced by other EDC file servers), not just their assigned stores.

For example, if a SuperSite has one EDC file server servicing stores 1-10 and a second EDC file server serving stores 11-20, then each EDC file server must use a copy of TRM.DBF that only contains the terminals in which it serves.�

Extended Information

A SuperSite PMS file server is set up the same as an SuperSite EDC file server, the only difference being the PMS settlement, as explained in document AKBID3066.

SuperSites can share a single EDC/PMS file server, but separate servers are advantageous when a problem with EDC or PMS occurs.� When separate file servers are used, a problem with one does not cripple both processes.

Caveats

This document is intended for use with a SuperSite or with a single TableService or QuickService site.� If you are configuring a shared POS and EDC file server for use with multiple stores or concepts such as two restaurants next to each other, refer to document AKBID1123.� If you are configuring a single dedicated EDC file server for use with multiple stores or concepts such as two restaurants next to each other sharing a single dedicated EDC file server, refer to document AKBID1174.

ATL.DLL must be registered before other applications and .DLL files are registered.

============================================================================

See also:

AKBID1010 Aloha Application Software System Environment Variables

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1020 EDC Process

AKBID1047 Microsoft Windows Schedule Service

AKBID1049 Installing DCOM in Windows

AKBID1063 TCP/IP

AKBID1123 Multiple Concept EDC on a Single File Server

AKBID1174 Stand Alone EDC File Server for Multiple Concepts

AKBID3066 SuperSite PMS Settlement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1095

Smart Items

Smart Items

============================================================================

AKBID1096

Created: 3 May 2000

Updated: 31 July 2000

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService

Aloha POS Versions: 3.8x � 5.3.x

Subject: How to Use QuickService Smart Items

============================================================================

Summary

Smart Items, in the ALOHA^� QuickService application software, enable an easy way for you to add multiple-sized items to the menu.� Rather than 10 drinks types using 30 buttons to accommodate three different sizes of each drink, smart items reduce the button count to 13: three size buttons, and 10 drink types.� Users select the size button followed by the drink type, and the correct drink size is added to the guest check.� This document explains how to configure smart items in the Aloha application software.

Information

Smart items use two functions: Smart Select and Smart Items.� Each of these functions is assigned to buttons in Panel Editor.

Smart Select

Smart select buttons are item sizes (for example, Small, Medium, and Large).� You must assign a Smart Group and Smart Element is assigned to each button.

The smart group refers to a group of items.� For example, the same screen might have smart select and smart item buttons for both drinks and french fries.� Assign the drinks to smart group 1 and french fries to smart group 2.

The smart element defines which item (defined in smart items) is applied to the guest check.�

Separate smart group numbers are not required for each set of smart items.� For example, you can use one set of size buttons for both drinks and french fries.

Smart Item

Smart item buttons define the items associated with the smart select buttons.� Each button contains a list of related items (for example, Small Drink, Medium Drink, and Large Drink), a group assignment for each item, and an element assignment for each item.

The Default Item is the item added to the guest check when a smart select button is not used in conjunction with the smart item button.

The Group relates to the smart group defined in the Smart Select section of this document.

The Element relates to the smart element defined in the Smart Selection section of this document.� When a smart select button with a smart element of 1 is chosen along with a smart item button, the item assigned to element 1 appears on the guest check.� When a smart select button with a smart element of 2 is chosen along with a smart item button, the item assigned to element 2 appears on the guest check.

Overview

A restaurant with 5 drinks that come in three sizes may use the following buttons and settings:

Type

Smart Select

Label

Small

Smart Group

1

Smart Element

1

Type

Smart Select

Label

Medium

Smart Group

1

Smart Element

2

Type

Smart Select

Label

Large

Smart Group

1

Smart Element

3

Type

Smart Item

Label

Cola

Default Item

Medium Cola

Item 1

Small Cola

Item 1 Group

1

Item 1 Element

1

Item 2

Medium Cola

Item 2 Group

1

Item 2 Element

2

Item 3

Large Cola

Item 3 Group

1

Item 3 Element

3

Type

Smart Item

Label

Diet Cola

Default Item

Medium Diet Cola

Item 1

Small Diet Cola

Item 1 Group

1

Item 1 Element

1

Item 2

Medium Diet Cola

Item 2 Group

1

Item 2 Element

2

Item 3

Large Diet Cola

Item 3 Group

1

Item 3 Element

3

Type

Smart Item

Label

Orange Cola

Default Item

Medium Orange Cola

Item 1

Small Orange Cola

Item 1 Group

1

Item 1 Element

1

Item 2

Medium Orange Cola

Item 2 Group

1

Item 2 Element

2

Item 3

Large Orange Cola

Item 3 Group

1

Item 3 Element

3

Type

Smart Item

Label

Root Beer

Default Item

Medium Root Beer

Item 1

Small Root Beer

Item 1 Group

1

Item 1 Element

1

Item 2

Medium Root Beer

Item 2 Group

1

Item 2 Element

2

Item 3

Large Root Beer

Item 3 Group

1

Item 3 Element

3

Type

Smart Item

Label

Ice Tea

Default Item

Medium Ice Tea

Item 1

Small Ice Tea

Item 1 Group

1

Item 1 Element

1

Item 2

Medium Ice Tea

Item 2 Group

1

Item 2 Element

2

Item 3

Large Ice Tea

Item 3 Group

1

Item 3 Element

3

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1096

�

Aloha Application Software Font Name and Size Variables

Aloha Application Software Font Name and Size Variables

============================================================================

AKBID1097

Created: 3 May 2000

Updated: 29 January 2002

Reviewed: 6 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Changing Aloha Application Software Font Names and Sizes

============================================================================

Summary

The ALOHA^� application software uses Microsoft^� Windows^� font names and sizes in the user interface.� You can use system environment variables to change the font names and sizes from their default settings.� This document explains the system environment variables used by the Aloha application software to change the screen text's size and font.

Information

TableService-only Font Name and Size Variables

The Aloha application software uses the following variables to override the default font and font size settings:

The defined font must reside on the local terminal.

System Environment Variable

Description

Example (Default Values)

ALOHABIGFONTNAME

Big font name

SET ALOHABIGFONTNAME=ARIAL

ALOHABIGFONTSIZE

Big font size

SET ALOHABIGFONTSIZE=16

ALOHAHUGEFONTNAME

Huge font name

SET ALOHAHUGEFONTNAME=ARIAL

ALOHAHUGEFONTSIZE

Huge font size

SET ALOHAHUGEFONTSIZE=80

ALOHAMEDIUMFONTNAME

Medium font name

SET ALOHAMEDIUMGFONTNAME=ARIAL

ALOHAMEDIUMFONTSIZE

Medium font size

SET ALOHAMEDIUMFONTSIZE=12

ALOHASMALLFONTNAME

Small font name

SET ALOHASMALLFONTNAME=ARIAL

ALOHASMALLFONTSIZE

Small font size

SET ALOHASMALLFONTSIZE=8

ALOHASYSTEMFONTNAME

System font name

SET ALOHASYSTEMFONTNAME=ARIAL

ALOHASYSTEMFONTSIZE

System font size

SET ALOHASYSTEMFONTSIZE=12

ALOHATINYFONTNAME

Tiny font name

SET ALOHATINYFONTNAME=ARIAL

ALOHATINYFONTSIZE

Tiny font size

SET ALOHATINYFONTSIZE=6

The font name and font size variables are mutually inclusive, even if the value does not differ from the default.� For example, if you want to change the ALOHABIGFONTSIZE, you must also set the ALOHABIGFONTNAME variable, even if you are assigning the default ARIAL value.

TableService used the following font type assignments:

Screen

Text

Font

Floating Logo

Copyright information

Medium

Error Messages

Error messages

Medium

Login

Keypad numbers 0 � 9

Big

Login

Keypad 'Clear'

Medium

Login

Keypad 'Exit'

N/A

Login

Date-of-Business (DOB), system date, system resources

Small

Login

Time, master status, terminal name

Medium

Login

User messages, login prompt, ID number

Medium

Working with Tables

Employee name

Medium

Working with Tables

Exit

Big

Working with Tables

Open tables, transfer tables

Medium

Working with Tables

Icon text

Small

Working with Tables

Button text

Small

Manager Functions

Exit

Big

Manager Functions

Button text

Medium

Manager Function Selections

Button Text

Medium

Manager Function Selections

Exit

N/A

Table Number Input

Keypad 'Clear' and 'OK'

Medium

Table Number Input

Keypad 'Cancel'

Medium

Table Number Input

Keypad numbers 0 - 9

Big

Table Number Input

Table number and guests prompts

Medium

Table Number Input

'Enter Table Number'

N/A

Order Entry

'**Recipe'

Small

Order Entry

Function button text

System

Order Entry

Item button text

System

Order Entry

Item counter text

Small

Order Entry

Check selection button text

N/A

Order Entry

Menu name

System

Order Entry

Guest Check

Medium

Modifier

Guest check information

Medium

Modifier

Modifier button text

System

Modifier

Selection text

System

Modifier

Modify text

Big

Modifier

'OK', 'Cancel'

Medium

Modifier

Function button text

System

Tenders

Guest check information

Medium

Tenders

Function button text

N/A

Tenders

Check selection button

N/A

Tenders

Tender button text

N/A

Tenders

Exit button

N/A

N/A

Optional cash drawer messages

Huge

TableService QuickService Font Name Variables

TableService versions 5.230 and higher and QuickService versions 5.212 support the ALOHABASEFONT variable.� This variable defines the font name used by all Front-of-House (FOH) text and you can set it in the ALOHA.INI (ALOHABASEFONT=TIMES NEW ROMAN), as a system environment variable (SET ALOHABASEFONT=TIMES NEW ROMAN) or on the command line for IBER.EXE or IBERQS.EXE (/ALOHABASEFONT "TIMES NEW ROMAN").� The command line variable overwrites the system environment variable and the system environment variable overwrites the ALOHA.INI variable.

If you are using TableService, the system environment variables described in the TableService-only Font Name and Size Variables section of this document overwrite the ALOHABASEFONT variable.

Extended Information

No information.

Caveats

The defined font must reside on the local terminal.

The font name and font size variables are mutually inclusive, even if the value does not differ from the default.� For example, if you want to change the ALOHABIGFONTSIZE, you must also set the ALOHABIGFONTNAME variable, even if you are assigning the default ARIAL value.

============================================================================

See also:

Aloha TableService User Manual

AKBID1119 FOH Adjustable Resolution Settings

AKBID1165 FOH Screen Resolution Settings

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1097 adjust

�

Order Taker Job Code Option

Order Taker Job Code Option

============================================================================

AKBID1098

Created: 6 March 2000

Updated: 3 July 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.6x � 5.3.x

Subject: The Order Taker TableService Job Code Option

============================================================================

Summary

The ALOHA^� application software uses the Order Taker job code option for operations that require the guest to order a portion of their meal at the beginning of a line, and give a chit to the cashier at the end of the line.� The cashier retrieves the check (using Get Check) based on the information printed on the Order Taker chit, orders any additional items, and closes the check.� Order Taker chits only print for employees with the Order Taker job code option

Do not confuse the Order Taker job code option with the Delivery Order Taker job code option in Aloha Manager.

Information

The order taker chit includes five lines of customizable text, the check number, check total, table number, and time/date information.

Order Taker functionality requires two steps:

1.        Define Order Taker job codes.

2.        Enable Order Taker chits to print.�

Job Codes

Define job codes that print an order taker chit by enabling the order taker job code option.� Job codes without the order taker option enabled do not print an order taker chit.

In versions 4.4x and lower, open Maintenance/Labor/Job Codes.� Select the appropriate job code, and select the order taker option.

In versions 5.0x and higher, open Aloha Manager, and select Maintenance/Labor/Job Codes.� Select the appropriate job code, and select the Table Service tab.� Select the order taker option.

Printing

Enable order taker chits to print for the selected job codes by enabling it in the printing options.

In versions 4.4x and lower, open Maintenance, and select Options/Print/Other, and click Print Order Taker Chits to enable it.

In versions 5.0x and higher, open Aloha Manager, select Maintenance/Store Settings, and select the Printing group.� Select the Other Chits tab, and select Print Order-Taker Chits.

The Order Taker chit only prints the first time items are ordered on a check.� Subsequent orders from the same check do not produce an Order Taker chit.

Extended Information

No information.

Caveats

The Order Taker chit only prints the first time items are ordered on a check.� Subsequent orders from the same check do not produce an Order Taker chit.

============================================================================

See also:

Aloha TableService User Manual

AKBID1053 TableService Order Entry Job Code Options

AKBID1100 Multi-Part Checks

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1098

Network Troubleshooting

Network Troubleshooting

============================================================================

AKBID1099

Created: 26 April 2000

Updated: 28 April 2003

Reviewed: 26 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

Subject: Troubleshooting Aloha Application Software Network Problems

============================================================================

Summary

Proper network functionality is one of three major factors in the stability of the ALOHA^� application software, the other two being clean power and quality hardware.� Any one of these three can render the Aloha application software unreliable.� This document addresses network troubleshooting when the network causes problems associated with the Aloha application software.� Refer to document AKBID1048 for more information on hardware, and the Aloha Application Software A C Power Requirements Manual for more information on power requirements.

Refer to document AKBID1075 for more information on how the Aloha application software interacts with NetBIOS.

Information

The most important step in troubleshooting network problems is prevention.� The first step in preventing network problems is using quality hardware, cables, connectors, and proper wiring runs.

A floating logo on the Front-of-House (FOH) terminal that regularly pauses is a telltale sign of trouble with the network or power.� Each time the logo pauses, the terminal has lost the network connection with the file server or Master terminal.

Check the Network Hardware

1.        Besides the checking the condition of the cables and connectors, check for cables that run near sources of interference, such as fluorescent lights, electrical motors, and other power sources.��

2.        Do all cables fit snuggly into the connections?� Disconnect each cable and reconnect it.

3.        Does the hub's power source fit snuggly into the wall power receptacle and into the back of the hub?

4.        If it is only a single terminal causing problems, try moving the terminal.� Does the problem follow the terminal or patch cable?� Try a different port on the hub, or a different hub.

5.        Re-terminate network connections.� Loose or inferior connections cause intermittent problems.

Check the Basic Network Functionality

1.        Can each terminal copy a file to the file server's BOOTDRV share and delete the file?� Can the file server copy a file to each terminal's BOOTDRV share and delete the file?

2.        Using a network that is known to be trouble-free, copy a large file between computers.� Using the time as a benchmark, copy the same file between computers on the problematic network, and see if the transfer rate is the same.�

3.        If TCP/IP is used as the network protocol, are the TCP/IP addresses compatible with one another?� Refer to document AKBID1063.

4.        If TCP/IP is used as the network protocol, is NetBIOS enabled over to transmit over TCP/IP?� Refer to document AKBID1063.

5.        Are the lana numbers for the protocol and Network-Interface-Card (NIC) used by the Aloha application software all set to zero?� Refer to document AKBID1018.

6.        Are the workgroup and network names correct on each terminal?� Do any of the network names contain spaces?

Single-Terminal Networking

The Aloha application software requires you to enable Microsoft^� Windows^� Networking, even if the system only uses a single terminal as both a file server and a terminal.� The Aloha application software displays one of the following errors if you have not properly installed Windows Networking:

1.        Failed to register station name, error 0x3F

2.        Failed to register station name, error 0x34

3.        The FOH sticks on a 'Terminal Up' message in the lower left corner

4.        The FOH sticks on a blank message in the lower left corner

If the terminal has a NIC installed, ensure that it is functional and that a valid network protocol is assigned to lana zero (refer to document AKBID1018).� A valid network protocol includes one of the following:

1.        The TCP/IP protocol assigned to a static IP address

2.        The TCP/IP protocol assigned to an IP address via DHCP

3.        The NetBEUI protocol

4.        The IPX/SPX protocol

If you have configured TCP/IP to use a DHCP-assigned IP address, the terminal must actually have an IP address assigned by DHCP, otherwise Windows will not enable the protocol.

In cases where the terminal does not have a NIC installed, Windows will recognize a modem as a network interface adapter.� If the terminal does not have a physical modem installed, a 'phantom' modem and Dial-Up Networking can be installed to act as a network interface adapter.

Check the Aloha Application Software Variables

1.        Are the Aloha application software variables configured properly on each terminal?� Use the SET command from a command prompt to verify the settings.� Refer to document AKBID1010.

2.        Do any applications have command line variables that override the system variables (for example, NONET on Control or Control Server)?

3.        Are the shortcuts to FOH and Back-of-House (BOH) Aloha applications actual shortcuts and not (older) copies of the application itself?

Read the Debugging Files

Read the debugging files for more information.� The information in this document and document AKBID1075 explains much of the network status information contained in the debugging files.

NetBIOS Return Codes

The Aloha application software often uses NetBIOS Return Codes in the debugging files.� Use the following chart to decipher NetBIOS errors listed in the debugging files:

Code

Name

Description

0x00

NRC_GOODRET

Good return

0x01 or 0x1

NRC_BUFLEN

Illegal buffer length

0x02 or 0x2

NB_ERROR_BUFFERS_FULL

Buffers full, no receive issued

0x03 or 0x3

NRC_ILLCMD

Illegal command

0x05 or 0x5

NRC_CMDTMO

Command timed out

0x06 or 0x6

NRC_INCOMP

Message incomplete, issue another command

0x07 or 0x7

NRC_BADDR

Illegal buffer address

0x08 or 0x8

NRC_SNUMOUT

Session number out of range

0x09 or 0x9

NRC_NORES

No resource available

0x0a or 0xa

NRC_SCLOSED

Session closed

0x0b or 0xb

NRC_CMDCAN

Command canceled

0x0d or 0xd

NRC_DUPNAME

Duplicate name

0x0e or 0xe

NRC_NAMTFUL

Name table full

0x0f or 0xf

NRC_ACTSES

No deletions, name has active sessions

0x10

NB_ERR_INVALID

Name not found or no valid name

0x11

NRC_LOCTFUL

Local session table full

0x12

NRC_REMTFUL

Remote session table full

0x13

NRC_ILLNN

Illegal name number

0x14

NRC_NOCALL

No callname

0x15

NB_ERR_BAD_NAME

Cannot put * in NCB_NAME

0x16

NB_ERR_NAME_IN_USE

Name in use on remote adapter

0x17

NB_ERR_NAME_DELETED

Called name cannot == name or name #

0x18

NB_ERR_SESSION_CRASHED

Session ended abnormally

0x19

NB_ERR_NAME_CONFLICT

Name conflict detected

0x21

NB_ERR_BUSY

Interface busy, IRET before retrying

0x22

NB_ERR_SLOW_DOWN

Too many commands outstanding, retry later

0x23

NB_ERR_BAD_ADAPTER

NCB_bridge field not 00 or 01

0x24

NB_ERR_CANCEL_PENDING

Command completed while cancel occurring

0x25

NB_ERR_RESERVED_NAME

Reserved name specified

0x26

NB_ERR_CANT_CANCEL

Command not valid to cancel

0x33

NB_ERR_MULT

Multiple requests for same session

0x34

NB_ERR_ ENVNOTDEF

Environment undefined.� RESET required or network not configured

0x36

NB_ERR_MAXAPPS

Max number of applications exceeded

0x38

NB_ERR_NORESOURCES

Requested resources are not available

0x40

NB_ERR_SYSTEM

System error

0x41

NB_ERR_ROM

ROM checksum failure

0x42

NB_ERR_RAM

RAM test failure

0x43

NB_ERR_DLF

Digital loopback failure

0x44

NB_ERR_ALF

Analog loopback failure

0x45

NB_ERR_IFAIL

Interface failure

0x50

NB_ERR_ADAPTER

Network adapter malfunction

0x50 - 0xf6

NB_ERR_ADAPTER

Other adapter failures

0xff

NB_COMMAND_PENDING

Asynchronous command is not yet finished

Using a Router

The Aloha application software will not function properly with a network router unless the router is setup to enable NetBIOS traffic.� Enabling UDP ports 137, 138, and 139 does this.

A router is a more complex device than a hub or a switch, and it is designed for linking together sub-networks into a larger network, whereas the Aloha application software is optimized to run on one leg of a network.� Since a router performs more processing and theoretically has a lower bandwidth than a hub, it is possible that a router may slow down or have an adverse effect on the Aloha application software.

Since SuperSite stores do not communicate with each other, they do not experience the possible negative effects of a router.

Common Network Problems and Errors

The terminals and file server can see each other on the network, but the Aloha application software does not recognize them: Check the lana numbers, TCP/IP addresses, the TERMSTR variables, and spaces in the network names.� 0x23 and 0x34 errors usually refer to incorrect lana number configuration.

The debugging files contain 0x22 and 0xff NetBIOS errors: administer the VNETBIOS.VXD patch.� Refer to document AKBID1011.

The debugging files contain 0x0a NetBIOS errors: This indicates the terminal has ended the connection in preparation for a shutdown.� This is normal.

The debugging files contain 0x18 NetBIOS errors: This indicates the session has 'crashed'.� It usually occurs when the terminal is turned off without properly shutting it down, the computer has locked up, or the network is disrupted.� If this happens irregularly, check for appliances or other power sources that may cause this.

Windows Millennium Edition (Me), Windows 2000 and Windows XP may display 'Fail to register station name 0x23' network errors if DHCP Media Sense is not disabled on a PC that is not connected to an active network.� Refer to operating system's configuration document for more information.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

Aloha Data and A C Power Requirements Manual

AKBID1010 Aloha Application Software System Environment Variables

AKBID1011 Windows 9x VNETBIOS.VXD Patch

AKBID1018 Network Lana Numbers

AKBID1048 Aloha Application Software Hardware and OS Specifications

AKBID1063 TCP/IP

AKBID1075 NetBIOS and the Aloha Application Software

AKBID3065 Windows 9x Fails to Initialize Microsoft Windows Networking

AKBID3145 IPX/SPX Protocol

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1099 code

Multi-Part Checks

Multi-Part Checks

============================================================================

AKBID1100

Created: 6 March 2000

Updated: 19 February 2003

Reviewed: 5 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.6x � 5.3.x

Subject: TableService Multi-Part Check Options

============================================================================

Summary

The ALOHA^� application software offers two options for printing multiple-part checks: Two-Part Checks, and Check Stub.� Two-part checks print a second portion of the guest check that includes five custom lines of text, the check number, check total, table number, and date/time information.� Check stub prints a second portion of the guest check that includes a single line of custom text, a list of items on the check, the check number, date/time information, and a barcode representing the check number.

Information

Two-Part Checks

To enable two-part checks in versions 4.4x and lower, open Maintenance, select Options/Print/Other, and select Print Two Part Checks.

In versions 5.0x and higher, open Aloha Manager, select Maintenance/Store Settings/Printing/Multi-Part Checks, and select Print Two-Part Checks.

Five lines of customizable text are available to print on the second part of the check.

Check Stubs

Check stubs include a barcode, and require a thermal type receipt printer.

The must define a thermal printer as the printer type in the Aloha application software in order to print barcodes on check stubs.� You can also use the OPOS printer type provided that the printer is a thermal printer.

To enable check stubs in versions 4.4x and lower, open Maintenance, select Options/Print/Other, and select Print Stub When Order.

In versions 5.0x and higher, open Aloha Manager, select Maintenance/Store Settings/Printing/Multi-Part Checks, and select Print Check Stub.

One line of customizable text is available to print on the check stub.

Extended Information

No information.

Caveats

The must define a thermal printer as the printer type in the Aloha application software in order to print barcodes on check stubs.� You can also use the OPOS printer type provided that the printer is a thermal printer.

============================================================================

See also:

Aloha Table Service User Manual

AKBID1098 Order Taker Job Code Option

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1100 cafeteria cashier

Windows Me FOH Terminal Setup

Windows Me FOH Terminal Setup

============================================================================

AKBID1101

Created: 29 September 2000

Updated: 21 February 2003

Reviewed: 1 March 2004

Microsoft Windows Versions: Windows Me

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.017 � 5.3.x

Subject: Windows Me FOH Terminal Setup

============================================================================

Summary

The ALOHA^� application software requires several specialized settings (as well as several preferred settings) in the Microsoft^� Windows^� Millennium Edition (Me) operating system (OS) to properly run IBER.EXE and IBERQS.EXE in the Front-of-House (FOH).� If you are using the terminal to run both Aloha Front-of-House (FOH) and Back-of-House (BOH) together, refer to document AKBID1103.

Information

Since some computers come with Windows Me preloaded while others do not, this document is based on editing the settings of Windows Me.� Users who are installing Windows Me from scratch or upgrading another OS to Windows Me can still use this document either by employing these instructions after the Windows Me installation or by making many of these changes during the Windows Me installation.

File System

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

The most important settings in the Aloha application software involve the network settings.� To access these settings, select Start/Settings/Control Panel/Network or right-click the Network Neighborhood icon on your desktop and selecting Properties.

If the Network option is not listed in the Control Panel, click 'view all Control Panel options' on the left-hand side of the screen.

The Configuration tab contains a Components area and Primary Network Logon type.� The components area should have Client for Microsoft Networks as the only network client installed.� You may have others, but these should only be added if absolutely needed.� The correct drivers for your network interface card (NIC) should also be listed.�

The Aloha application software can use either TCP/IP or NetBEUI as its network protocol.� Select either one, but both the file server and the terminals must use the same protocol.� To assign the protocol for the Aloha application software to use (refer to document AKBID1018), double-click the desired protocol, select the Advanced tab, and select 'Set this protocol to be the default protocol'.� If you select TCP/IP, Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure that terminals always have an address assigned to them.� The Aloha application software will not function without an IP address assigned to the terminal.� You may have multiple protocols installed as long as the proper protocol for the Aloha application software has been marked as such.�

To add file and print sharing for the Aloha application software, click the File and Print Sharing button and select both options.� Print Sharing may be left disabled if you are not using Windows based printer shares for the FOH.�

The Primary Logon Type is typically set to Windows Logon.� This logon enables Windows Me to skip the prompt for the user name and password if the password is blank.� Setting this as Client for Microsoft Networks prompts for the user name and password regardless if the password is blank.� If Client for Microsoft Networks must be used as the Primary network logon, use the Microsoft Windows Me TweakUI utility to automatically enter the user name and password.� TweakUI can be downloaded from the Aloha Technologies FTP site as TWEAKUI.ZIP.� Aloha Technologies installs this utility regardless of the Primary Logon Type setting.

Set the terminal's network name under the Identification tab.� Aloha Technologies uses TERM1, TERM2, and so on by default.� Different names may be used, but they must follow Aloha application software specifications.� The terminal name must be a common name used on all terminals (the TERMSTR, refer to document AKBID1010) followed by a number designating the terminal's ID number.� Examples include ALOHA1, ALOHA2, TSFOH_1, and TSFOH_2.� In this case, the TERMSTR would be 'ALOHA' or 'TSFOH_'.� Different TERMSTR names can not be used within the same Aloha system.� Spaces can not be used, but underscores can.� Leading zeros can not be used unless they are part of the TERMSTR, but it is not recommended.

Set the Workgroup name the same on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the Workgroup name, but this name can be of your choice as long as it is consistent throughout the Aloha application software.�

The Computer Description is solely to your discretion.

Ensure that 'Share-level access control' is selected under the Access Control tab.� Only experienced Domain administrators should consider using 'User-level access control'.

TCP/IP Media Sense

Windows Me uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.�

Perform the following to disable Media Sense:

1.        To access these settings, select Start/Settings/Control Panel/Network or right-click the Network Neighborhood icon on your desktop and select Properties.

2.        Click the copy of TCP/IP that is bound to the network adapter you want to configure.

3.        Click the IP Address tab, click to clear the 'Detect connection to network media' check box, and then click OK.

4.        Click OK, and then restart your computer.

Media Sense provides the ability to connect to networks with different DHCP options in one Windows session without the need to release and renew the IP configuration by using WINIPCFG.EXE.� If you disable Media Sense, no new IP configuration information is obtained when you connect to a new network unless you restart the computer, or you release and renew the IP configuration by using WINIPCFG.EXE.

Refer to Microsoft Knowledge Base document Q239924 for more information on Media Sense.

Aloha Share Name

The Aloha application software requires a network share name of BOOTDRV.� This is the required name.� This share needs to be applied to the root folder or drive in which the Aloha folder resides.� To set the share, right-click the drive or folder and choose Sharing.� Set the Share Name to BOOTDRV, the Access Type to Full, and leave the password fields blank.

If the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.� Some clients prefer to place the Aloha application software in a special folder in order to limit the shared files, and, therefore, enhance security.� Sharing the entire drive in which the Aloha application software resides also shares other files that reside on the drive, such as Windows.

Display Settings

To access the Display settings, select Start/Settings/Control Panel/Display or right-click the Windows desktop and select Properties.� Select the Settings tab.� Set the Color palette to 256 Colors or higher.� Aloha Technologies typically uses 16-bit color.�

Refer to document AKBID1165 for screen resolution settings.

Do not enable a Windows screen saver.

Time Zone & Daylight Savings

For the file server and all terminals to display the correct time and adjust to Daylight Savings changes properly, the Time and Date settings must be properly configured in Windows.� Select Start/Settings/Control Panel/Date/Time or double-click the time displayed on the task bar.� Ensure the date and time are correct.� Ensure the date and time are correct on the Date & Time tab.� Ensure the correct time zone is chosen on the Time Zone tab.� This time zone needs to be the same on all terminals and the file server.� If the area observes Daylight Savings, then the 'Automatically adjust clock for daylight savings changes' option must be selected on all terminals and the file server.� This can be turned on or off, but it needs to be consistent throughout the Aloha application software.

FIFO Buffers

Windows Me enables First-In-First-Out (FIFO) buffers for each COM port.� These buffers tend to interfere with printers using Xon/Xoff flow control, so Aloha Technologies disables these buffers on all COM ports on all terminals, regardless of the printer type.� (In the event of a printer or COM port failure, a printer using Xon/Xoff flow control may be temporally connected to the port in the future.)

To access the FIFO buffer settings, select Start/Settings/Control Panel/System or right click My Computer and select Properties.� Select the Device Manager tab, and click the plus sign (+) next to Ports to expand it.� Select each port one at a time, and select Properties/Port Settings/Advanced.� Clear 'Use FIFO buffer'.� Repeat for each COM port.� The LPT port does not have this option.

Scandisk Autoscan & Settings

By default, if Windows is shut down improperly, it runs Scandisk the next time the system is started.� If it finds any problems on the drive, it prompts for answers.� Since there is not a keyboard that is typically attached to a FOH terminal to answer the questions, which increases the time the Aloha application software may be disrupted.� To alleviate this problem, Aloha Technologies offers a SCANDISK.INI that keeps Windows from prompting for 95% of the questions.� This SCANDISK.INI can be downloaded from the Aloha Technologies FTP site as SCANDISK.ZIP.� Place this file in the Windows COMMAND folder overwriting the one that currently exists.

Login Name

Refer to document AKBID1006 for more information on user login information.

To clear the current user names and passwords, delete *.PWL from the Windows folder to remove all users.� Select Start/Shutdown.� Select 'Close all programs and log in as a different user' and click Yes.� Windows logs the current user out and prompts for a user name and password.� Enter the desired user and password and log in to Windows.

VNetBIOS

Windows Me might experience network problems with restaurants using five or more terminals.� To ensure that terminals do not experience these problems, Microsoft issued a new VNETBIOS.VXD that you can download from the Aloha Technologies FTP site as VNETBIOS.ZIP.� Aloha Technologies installs this .VXD file on all terminals, regardless of the system's size.� Refer to document AKBID1011 for more information.

Once you have the new .VXD, place it in the Windows SYSTEM folder overwriting the current version.� Edit the SYSTEM.INI in the Windows folder, and add a new line in the [386Enh] section that states NUMHCBS=x.� Replace x with a number four times the number of terminals in the system, but not less than 80 nor exceeding 200.� The default for this number is 100.� For example, a 25 terminal system would use NUMHCBS=100.� Do not exceed 100 unless you have more than 25 terminals.

To ensure that Windows does not overwrite the updated VNETBIOS.VXD following network configuration changes, place a copy of the updated VNETBIOS.VXD in the same folder as the Windows CAB files.

Install Aloha Software

Once Windows Me is set up according to the standards outlined in this document and you can view the network, use the terminal installation diskette to install the Aloha application software.

To create this diskette, insert the installation CD in the file server's CD-ROM, and run SETUPPOS.EXE /ADVANCED.� Select Make Diskettes/Create Terminal Installation Diskette from the Main Menu

Once the diskette is created, insert it into the terminal's floppy drive, and run SETUP.EXE.� The setup program walks you through the rest of the installation.

If the terminal does not have a floppy drive, run the Terminal Installation application directly from the CD-ROM on the file server.� Map a drive to the CD-ROM on the file server.� Do not choose the Reconnect at Logon option when mapping the drive.� Run the file \TERMINST\SETUP.EXE from the Aloha POS CD.� The setup program walks you through the rest of the installation.

Extended Information

Windows Explorer starts in the My Documents folder by default.� Add ' /n,/e' to the EXPLORER.EXE command line and shortcuts in order for Explorer to default to C:\.� For example:

%systemroot%\explorer.exe /n,/e

Caveats

No information.

============================================================================

See also:

AKBID1001 Configuring the CALIBRATE Variable on Aloha Terminals

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1010 Aloha Application Software System Environment Variables

AKBID1011 Windows 9x VNETBIOS.VXD Patch

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1018 Network Lana Numbers

AKBID1028 Winhook

AKBID1103 Microsoft Windows Me Filer Server/Terminal Setup

AKBID1165 FOH Screen Resolution Settings

AKBID1175 Aloha Terminal Restart Options

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1204 Default Aloha System Environment Variable Placement

AKBID3150 Editing Microsoft Windows Me Environment Variables

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1101 stage staging

Windows Me File Server Setup

Windows Me File Server Setup

============================================================================

AKBID1102

Created: 28 September 2000

Updated: 8 August 2002

Reviewed: 1 March 2004

Microsoft Windows Versions: Windows Me

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.017 � 5.3.x

Subject: Windows Me File Server Setup

============================================================================

Summary

The ALOHA^� application software requires several specialized settings (as well as several preferred settings) in the Microsoft^� Windows^� Millennium Edition (Me) operating system (OS) to properly run on the file server.� If you are using the file server to run both Aloha Front-of-House (FOH) and Back-of-House (BOH) together, refer to document AKBID1103.

Information

This document is written for users familiar with Microsoft Windows Me.

Since some computers come with Windows Me preloaded while others do not, this document is based on editing the settings of Windows Me.� Users who are installing Windows Me from scratch or upgrading another OS to Windows Me can still use this document either by employing these instructions after the Windows Me installation or by making many of these changes during the Windows Me installation.

Drive Sizes & Partitions

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

The most important settings in the Aloha application software involve the network settings.� To access these settings, select Start/Settings/Control Panel/Network or right-click the Network Neighborhood icon on your desktop and select Properties.

If the Network option is not listed in the Control Panel, click 'view all Control Panel options' on the left-hand side of the screen.

The Configuration tab contains a Components area and Primary Network Logon type.� The components area should have Client for Microsoft Networks as the only network client installed.� You may have others, but these should only be added if absolutely needed.� The correct drivers for your network interface card (NIC) should also be listed.�

The Aloha application software uses either TCP/IP or NetBEUI as its network protocol.� Select either one, but both the file server and the terminals must use the same protocol.� To assign the protocol for the Aloha application software to use (refer to document AKBID1018), double-click the desired protocol, select the Advanced tab, and select 'Set this protocol to be the default protocol'.� If you select TCP/IP, Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure that terminals always have an address assigned to them.� The Aloha application software will not function without an IP address assigned to the terminal.� You may have multiple protocols installed as long as the proper protocol for the Aloha application software has been marked as such.�

To add file and print sharing for the Aloha application software, click the File and Print Sharing button and select both options.� Print Sharing may be left disabled if you are not using Windows based printer shares for the FOH or remote Control/Maintenance servers.�

The Primary Logon Type is typically set to Windows Logon.� This logon enables Windows Me to skip the prompt for the user name and password if the password is blank.� Setting this as Client for Microsoft Networks prompts for the user name and password regardless if the password is blank.� If Client for Microsoft Networks must be used as the Primary network logon, use the Microsoft Windows Me TweakUI utility to automatically enter the user name and password.� TweakUI can be downloaded from the Aloha Technologies FTP site as TWEAKUI.ZIP.� Aloha Technologies installs this utility regardless of the Primary Logon Type setting.

The Identification tab contains the network name and workgroup name.� Aloha Technologies uses ALOHABOH by default.� A different name can be used if desired.� Set the Workgroup name the same on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the Workgroup name, but this name can be of your choice as long as it is consistent throughout the Aloha application software.� The Computer Description is solely to your discretion.

Ensure that 'Share-level access control' is selected under the Access Control tab.� Only experienced Domain administrators should consider using 'User-level access control'.

TCP/IP Media Sense

Windows Me uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.�

Perform the following to disable Media Sense:

1.        To access these settings, select Start/Settings/Control Panel/Network or right-click the Network Neighborhood icon on your desktop and select Properties.

2.        Click the copy of TCP/IP that is bound to the network adapter you want to configure.

3.        Click the IP Address tab, click to clear the 'Detect connection to network media' check box, and then click OK.

4.        Click OK, and then restart your computer.

Media Sense provides the ability to connect to networks with different DHCP options in one Windows session without the need to release and renew the IP configuration by using WINIPCFG.EXE.� If you disable Media Sense, no new IP configuration information is obtained when you connect to a new network unless you restart the computer, or you release and renew the IP configuration by using WINIPCFG.EXE.

Refer to Microsoft Knowledge Base document Q239924 for more information on Media Sense.

Aloha Share Name

The Aloha application software requires a network share name of BOOTDRV.� This is the required name.� This share needs to be applied to the root folder or drive in which the Aloha folder resides.� To set the share, right-click the drive or folder and choose Sharing.� Set the Share Name to BOOTDRV, the Access Type to Full, and leave the password fields blank.

If the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.� Some clients prefer to place the Aloha application software in a special folder in order to limit the shared files and, therefore, enhance security.� Sharing the entire drive in which the Aloha application software resides also shares other files that reside on the drive such as Windows.

Display Settings

To access the Display settings, select Start/Settings/Control Panel/Display or right-click the Windows desktop and select Properties.� Select the Settings tab.� Set the Color palette to 256 Colors or higher.� Aloha Technologies typically uses 16-bit color.� The Aloha application software can be run on both a 640x480 pixel display and an 800x600 pixel display, however, Aloha Technologies prefers 800x600 (or better) resolution.

Aloha Technologies typically does not use a screen saver on the file server since some screen savers (the Open GL based screen savers in particular) can sap processor speed.

Time Zone & Daylight Savings

For the file server and all terminals to display the correct time and adjust to Daylight Savings changes properly, the Time and Date settings must be properly configured in Windows.� Select Start/Settings/Control Panel/Date/Time or double-click the time displayed on the task bar.� Ensure the date and time are correct.� Ensure the date and time are correct on the Date & Time tab.� Ensure the correct time zone is chosen on the Time Zone tab.� This time zone needs to be the same on all terminals and the file server.� If the area observes Daylight Savings, then the 'Automatically adjust clock for daylight savings changes' option must be selected on all terminals and the file server.� This can be turned on or off, but it needs to be consistent throughout the Aloha application software.

Scandisk Autoscan & Settings

By default, if Windows is shut down improperly, it runs Scandisk the next time the system is started.� If it finds any problems on the drive, it prompts for answers.� Again, this can cause a delay when a file server is restarting, which increases the time the Aloha application software may be disrupted.� To alleviate this problem, Aloha Technologies offers a SCANDISK.INI that keeps Windows from prompting for 95% of the questions.� This SCANDISK.INI can be downloaded from the Aloha Technologies FTP site as SCANDISK.ZIP.� Place this file in the Windows COMMAND folder overwriting the one that currently exists.

Login Name

Refer to document AKBID1006 for more information on user login information.

To clear the current user names and passwords, delete *.PWL from the Windows folder to remove all users.� Select Start/Shutdown.� Select 'Close all programs and log in as a different user' and click Yes.� Windows logs the current user out and prompts for a user name and password.� Enter the desired user and password and log in to Windows.

VNetBIOS

Windows Me may experience network problems with restaurants using five or more terminals.� To ensure that terminals do not experience these problems, Microsoft issued a new VNETBIOS.DLL that can be downloaded from the Aloha Technologies FTP site as VNETBIOS.ZIP.� Aloha Technologies installs this DLL on all terminals regardless of the system's size.� Refer to document AKBID1011 for more information.

Once you have the new DLL, place it in the Windows SYSTEM folder overwriting the one that currently exists.� Edit the SYSTEM.INI in the Windows folder and add a new line in the [386Enh] section that reads NUMHCBS=x.� Replace x with a number four times the number of terminals in the system, but not less than 80 and not exceeding 200.� The default for this number is 100.� For example, a 25 terminal system would use NUMHCBS=100.

To ensure that Windows does not overwrite the updated VNETBIOS.VXD following network configuration changes, place a copy of the updated VNETBIOS.VXD in the same folder as the Windows CAB files.

Install Aloha Software

Once Windows Me is set up according to the standards outlined in this document and you can view the network, use the Aloha Application Software Installation CD to install the Aloha application software.

Run SETUPPOS.EXE /ADVANCED from the Aloha POS CD.� The setup program walks you through the rest of the installation.

Refer to document AKBID1162 for more information on running CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) as Windows services.

Desktop Icons

The Windows desktop icons are generally a matter of preference.� In order to create a cleaner installation, Aloha Technologies ships file servers with only the My Computer, Network Neighborhood, Recycle Bin, Aloha Control, Aloha Maintenance, and (if installed) Symantec^� pcANYWHERE^� icons residing on the desktop.� For more information, refer to document AKBID1007.

Extended Information

Windows Explorer starts in the My Documents folder by default.� Add ' /n,/e' to the EXPLORER.EXE command line and shortcuts in order for Explorer to default to C:\.� For example:

%systemroot%\explorer.exe /n,/e

Caveats

When a file server is running Windows Me, Aloha Technologies does not choose to run CTLSVR.EXE and EDCSVR.EXE as services.� Running them as services in a Windows Me environment, although possible and stable, creates problems when Control Server or EDC Server have to be restarted and/or replaced.� It is not as easy a task to stop and start a service in Windows Me as it is in Windows NT.� Refer to document AKBID1162 for more information on running Control Server and EDC Server as Windows services.

============================================================================

See also:

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1010 Aloha Application Software System Environment Variables

AKBID1011 Windows 9x VNETBIOS.VXD Patch

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1018 Network Lana Numbers

AKBID1028 Winhook

AKBID1101 Microsoft Windows Me FOH Terminal Setup

AKBID1103 Microsoft Windows Me File Server/Terminal Setup

AKBID1148 Backup Procedures

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1204 Default Aloha System Environment Variable Placement

AKBID3150 Editing Microsoft Windows Me Environment Variables

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1102 stage staging

Windows Me File Server/Terminal Setup

Windows Me File Server/Terminal Setup

============================================================================

AKBID1103

Created: 29 September 2000

Updated: 24 September 2002

Reviewed: 2 March 2004

Microsoft Windows Versions: Windows Me

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.017 � 5.3.x

Subject: Windows Me File Server and Terminal on the Same Computer Setup

============================================================================

Summary

The ALOHA^� application software requires several specialized settings (as well as several preferred settings) in the Microsoft^� Windows^� Millennium Edition (Me) operating system (OS) to properly run on the run both Aloha Front-of-House (FOH) and Back-of-House (BOH) together on the same computer.� If you are using the computer as a file server only, refer to document AKBID1102.� If you are using the computer as a terminal only, refer to document AKBID1101.

Refer to document AKBID1116 for more information on the limitations of running both the FOH and BOH together on the same PC.

Information

This document is written for users familiar with Microsoft Windows Me.

Since some computers come with Windows Me preloaded while others do not, this document is based on editing the settings of Windows Me.� Users who are installing Windows Me from scratch or upgrading another OS to Windows Me can still use this document either by employing these instructions after the Windows Me installation or by making many of these changes during the Windows Me installation.

Drive Sizes & Partitions

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

The most important settings in the Aloha application software involve the network settings.� To access these settings, select Start/Settings/Control Panel/Network or right-click the Network Neighborhood icon on your desktop and select Properties.

If the Network option is not listed in the Control Panel, click 'view all Control Panel options' on the left-hand side of the screen.

The Configuration tab contains a Components area and Primary Network Logon type.� The components area should have Client for Microsoft Networks as the only network client installed.� You may have others, but these should only be added if absolutely needed.� The correct drivers for your network interface card (NIC) should also be listed.�

The Aloha application software can use either TCP/IP or NetBEUI as its network protocol.� Select either one, but both the file server/terminal and the other terminals must use the same protocol.� To assign the protocol for the Aloha application software to use (refer to document AKBID1018), double-click the desired protocol, select the Advanced tab, and select 'Set this protocol to be the default protocol'.� If you select TCP/IP, Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure that terminals always have an address assigned to them.� The Aloha application software will not function without an IP address assigned to the terminal.� You may have multiple protocols installed as long as the proper protocol for the Aloha application software has been marked as such.�

To add file and print sharing for the Aloha application software, click the File and Print Sharing button and select both options.� Print Sharing may be left disabled if you are not using Windows based printer shares for the FOH.�

The Primary Logon Type is typically set to Windows Logon.� This logon enables Windows 95 to skip the prompt for the user name and password if the password is blank.� Setting this as Client for Microsoft Networks prompts for the user name and password regardless if the password is blank.� If Client for Microsoft Networks must be used as the Primary network logon, use the Microsoft Windows 95 TweakUI utility to automatically enter the user name and password.� TweakUI can be downloaded from the Aloha Technologies FTP site as TWEAKUI.ZIP.� Aloha Technologies installs this utility regardless of the Primary Logon Type setting.

Set the terminal's network name under the Identification tab.� Aloha Technologies uses TERM1 (file server/terminal), TERM2, and so on by default.� Different names may be used, but they must follow Aloha application software specifications.� The terminal name must be a common name used on all terminals (the TERMSTR, refer to document AKBID1010) followed by a number designating the terminal's ID number.� Examples include ALOHA1, ALOHA2, TSFOH_1, and TSFOH_2.� In this case, the TERMSTR would be 'ALOHA' or 'TSFOH_'.� Different TERMSTR names can not be used within the same Aloha system.� Spaces can not be used, but underscores can.� Leading zeros can not be used unless they are part of the TERMSTR, but it is not recommended.

Set the Workgroup name the same on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the Workgroup name, but this name can be of your choice as long as it is consistent throughout the Aloha application software.�

The Computer Description is solely to your discretion.

Ensure that 'Share-level access control' is selected under the Access Control tab.� Only experienced Domain administrators should consider using 'User-level access control'.

TCP/IP Media Sense

Windows Me uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.�

Perform the following to disable Media Sense:

1.        To access these settings, select Start/Settings/Control Panel/Network or right-click the Network Neighborhood icon on your desktop and select Properties.

2.        Click the copy of TCP/IP that is bound to the network adapter you want to configure.

3.        Click the IP Address tab, click to clear the 'Detect connection to network media' check box, and then click OK.

4.        Click OK, and then restart your computer.

Media Sense provides the ability to connect to networks with different DHCP options in one Windows session without the need to release and renew the IP configuration by using WINIPCFG.EXE.� If you disable Media Sense, no new IP configuration information is obtained when you connect to a new network unless you restart the computer, or you release and renew the IP configuration by using WINIPCFG.EXE.�

Refer to Microsoft Knowledge Base document Q239924 for more information on Media Sense.

Aloha Share Name

The Aloha application software requires a network share name of BOOTDRV.� This is the required name.� This share needs to be applied to the root folder or drive in which the Aloha folder resides.� To set the share, right-click the drive or folder and choose Sharing.� Set the Share Name to BOOTDRV, the Access Type to Full, and leave the password fields blank.

If the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.� Some clients prefer to place the Aloha application software in a special folder in order to limit the shared files and, therefore, enhance security.� Sharing the entire drive in which the Aloha application software resides also shares other files that reside on the drive such as Windows.

Display Settings

To access the Display settings, select Start/Settings/Control Panel/Display or right-click the Windows desktop and select Properties.� Select the Settings tab.� Set the Color palette to 256 Colors or higher.� Aloha Technologies typically uses 16-bit color.�

Refer to document AKBID1165 for screen resolution settings.

Do not enable a Windows screen saver.

Time Zone & Daylight Savings

For the file server and all terminals to display the correct time and adjust to Daylight Savings changes properly, the Time and Date settings must be properly configured in Windows.� Select Start/Settings/Control Panel/Date/Time or double-click the time displayed on the task bar.� Ensure the date and time are correct.� Ensure the date and time are correct on the Date & Time tab.� Ensure the correct time zone is chosen on the Time Zone tab.� This time zone needs to be the same on all terminals and the file server.� If the area observes Daylight Savings, then the 'Automatically adjust clock for daylight savings changes' option must be selected on all terminals and the file server.� This can be turned on or off, but it needs to be consistent throughout the Aloha application software.

FIFO Buffers

Windows Me enables First-In-First-Out (FIFO) buffers for each COM port.� These buffers tend to interfere with printers using Xon/Xoff flow control, so Aloha Technologies disables these buffers on all COM ports on all terminals, regardless of the printer type.� (In the event of a printer or COM port failure, a printer using Xon/Xoff flow control may be temporally connected to the port in the future.)

To access the FIFO buffer settings, select Start/Settings/Control Panel/System or right click My Computer and select Properties.� Select the Device Manager tab, and click the plus sign (+) next to Ports to expand it.� Select each port one at a time, and select Properties/Port Settings/Advanced.� Clear 'Use FIFO buffer'.� Repeat for each COM port.� The LPT port does not have this option.

Scandisk Autoscan & Settings

By default, if Windows is shut down improperly, it runs Scandisk the next time the system is started.� If it finds any problems on the drive, it prompts for answers.� Again, this can cause a delay when a file server/terminal is restarting, which increases the time the Aloha application software may be disrupted.� To alleviate this problem, Aloha Technologies offers a SCANDISK.INI that keeps Windows from prompting for 95% of the questions.� This SCANDISK.INI can be downloaded from the Aloha Technologies FTP site as SCANDISK.ZIP.� Place this file in the Windows COMMAND folder overwriting the one that currently exists.

Login Name

Refer to document AKBID1006 for more information on user login information.

To clear the current user names and passwords, delete *.PWL from the Windows folder to remove all users.� Select Start/Shutdown.� Select 'Close all programs and log in as a different user' and click Yes.� Windows logs the current user out and prompts for a user name and password.� Enter the desired user and password and log in to Windows.

VNetBIOS

Windows Me may experience network problems with restaurants using five or more terminals.� To ensure that terminals do not experience these problems, Microsoft issued a new VNETBIOS.DLL that can be downloaded from the Aloha Technologies FTP site as VNETBIOS.ZIP.� Aloha Technologies installs this DLL on all terminals regardless of the system's size.� Refer to document AKBID1011 for more information.

Once you have the new DLL, place it in the Windows SYSTEM folder overwriting the one that currently exists.� Edit the SYSTEM.INI in the Windows folder and add a new line in the [386Enh] section that reads NUMHCBS=x.� Replace x with a number four times the number of terminals in the system, but not less than 80 and not exceeding 200.� The default for this number is 100.� For example, a 25 terminal system would use NUMHCBS=100.�

To ensure that Windows does not overwrite the updated VNETBIOS.VXD following network configuration changes, place a copy of the updated VNETBIOS.VXD in the same folder as the Windows CAB files.

Install Aloha Software

Once Windows 95 is set up according to the standards outlined in this document and you can view the network, use the Aloha Application Software Installation CD to install the Aloha application software.

Run SETUPPOS.EXE /ADVANCED from the Aloha POS CD.� The setup program walks you through the rest of the installation.� You must select 'Run Front of House and Back of House on same PC' on the Aloha Configuration window.

Refer to document AKBID1162 for more information on running CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) as Windows services.

Restarting the FOH

Refer to document AKBID1116 for more information regarding restarting the FOH in this type of environment.

Extended Information

Windows Explorer starts in the My Documents folder by default.� Add ' /n,/e' to the EXPLORER.EXE command line and shortcuts in order for Explorer to default to C:\.� For example:

%systemroot%\explorer.exe /n,/e

Caveats

When a file server is running Windows 95, Windows 98, or Windows Me, Aloha Technologies does not choose to run CTLSVR.EXE and EDCSVR.EXE as services.� Running them as services in a Windows 95, Windows 98, or Windows Me environment, although possible and stable, creates problems when Control Server or EDC Server have to be restarted and/or replaced.� It is not as easy a task to stop and start a service in Windows 95, Windows 98, and Windows Me as it is in Windows NT.� Refer to document AKBID1162 for more information on running Control Server and EDC Server as Windows services.

============================================================================

See also:

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1010 Aloha Application Software System Environment Variables

AKBID1011 Windows 9x VNETBIOS.VXD Patch

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1018 Network Lana Numbers

AKBID1028 Winhook

AKBID1101 Microsoft Windows Me FOH Terminal Setup

AKBID1102 Microsoft Windows Me File Server Setup

AKBID1116 File Server/Terminal Limitations

AKBID1148 Backup Procedures

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1165 FOH Screen Resolution Settings

AKBID1175 Aloha Terminal Restart Options

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1103 boh/foh bohfoh foh/boh fohboh stage staging terminal/server

Automatic Credit Card Settlement

Automatic Credit Card Settlement

============================================================================

AKBID1104

Created: 9 March 2000

Updated: 11 August 2003

Reviewed: 24 February 2004

Microsoft Windows Versions: All

Aloha Products: EDC

Aloha POS Versions: 3.5x � 5.3.x

Subject: Automatic Aloha Application Software Credit Card Settlement

============================================================================

Summary

The ALOHA^� application software Electronic Draft Capture (EDC) interface does not have built-in automatic settling capabilities, but there is a method to automatically settle credit cards.� This document explains how to configure automatic settlement.

Using automatic credit card settlement does not preclude monitoring settlement on a daily basis.� Settlements can fail for many reasons, and successful settlement should not be an assumption.

The use of this feature will result in your batch settling each day at a certain time, regardless of whether they have reviewed or adjusted the batch.� If any subsequently necessary adjustments have to be made, they will be in the next day's batch and will show as separate transactions on the customer's credit card bill.

Information

EDC uses request (REQ) and answer (ANS) files to initiate functions.� Refer to document AKBID1020 for more information on request and answer files.� When you select Settle Batch from the Functions drop-down menu, a request file is created to initiate the settlement.�� A manually created the request file initiates settlement also, and that is how the automatic settlement works.

Request File

Create a text file named 10000001.REQ that is stored in a permanent location outside of the EDC folder.

Edit the text file, and add the following lines:

BEGIN

TYPE <5 spaces> SETTLE

PROCESSOR <5 spaces> x

PROCNO <5 spaces> y

PINDEX <5 spaces> 1

END

�

Replace x with the name of the credit card processor (for example, VISNAET, AMEX, NABANCO, and so on).� Use capital letters in the processor name.� If you need to check the syntax, refer to an existing TXN file for the same processor.

Replace y with the credit card processor number from the following table:

Processor

PROCNO

CES

1

Visanet

2

American Express

3

NPC

4

NDC

5

Nabanco

6

FDC

7

Nova

8

Maverick

9

FCCNET

10

Paytech

11

Directnet

12

$$ in the Bank

13

Buypass

14

AlohaNet

15

LynkSystems

16

If you are using multiple processors, you must create a different request file (each with the correct processor number) for each unique processor.� You can label the request files 10000002.REQ, 10000003.REQ, and so on (the request file label does not have to reflect the processor number).

PINDEX refers to the Processor Index if multiple instances of the same processor are used (refer to document AKBID3053).� The default is '1'.� You must create a different request file (each with the correct index declaration) for each processor.� You can label the request files 10000002.REQ, 10000003.REQ, and so on (the request file label does not have to reflect the processor index number).

Process

To initiate a settlement, copy the request file to the EDC folder.� Do not move the file since the request file is used every time an automatic settlement is initiated.� EDC reads the file, converts it to a hold (HLD) file, and initiates the settlement.�

Automate this process using the Aloha application software Winhook feature (refer to document AKBID1028) or the Microsoft^� Windows^� Schedule Service (refer to document AKBID1047).� Either method utilizes a batch file.� The batch file should look similar to the following:

rem *** Automatic EDC Settlement ***

rem *** Copy the REQ file to EDC ***

COPY %IBERDIR%\REQFILE\10000001.REQ %IBERDIR%\EDC\10000001.REQ

rem *** Done ***

Extended Information

Force Settlement

If you are using Force Settlement, then replace the request type in the request file with 'FORCE' rather than 'SETTLE'.� For example:

BEGIN

TYPE <5 spaces> FORCE

PROCESSOR <5 spaces> x

PROCNO <5 spaces> y

PINDEX <5 spaces> 1

END

�

The Force Settlement function is rarely used.� It archives and clears out the current batch, but it does not perform any actual settlement with the processor.� It is intended only in case that the batch has already been settled, but Aloha does not know about it.� This can happen when settlement is interrupted, as described above, or when the processor manually settles a batch on their end to solve a problem.

Caveats

Using automatic credit card settlement does not preclude monitoring settlement on a daily basis.� Settlements can fail for many reasons, and successful settlement should not be an assumption.

The use of this feature will result in your batch settling each day at a certain time, regardless of whether they have reviewed or adjusted the batch.� If any subsequently necessary adjustments have to be made, they will be in the next day's batch and will show as separate transactions on the customer's credit card bill.

The Force Settlement function is rarely used.� It archives and clears out the current batch, but it does not perform any actual settlement with the processor.� It is intended only in case that the batch has already been settled, but Aloha does not know about it.� This can happen when settlement is interrupted, as described above, or when the processor manually settles a batch on their end to solve a problem.

============================================================================

See also:

AKBID1020 EDC Process

AKBID1028 Winhook

AKBID1046 Postponing Daily Batch Settlement

AKBID1047 Microsoft Windows Schedule Service

AKBID3053 Terminal-Specific EDC Processors

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1104 auto automate

�

Guest Check Information Files

Guest Check Information Files

============================================================================

AKBID1105

Created: 1 May 2000

Updated: 8 October 2001

Reviewed: 13 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x - 5.3.x

Subject: Creating Guest Check Information Files

============================================================================

Summary

The ALOHA^� application software creates text files with guest check information for you to use in creating and printing custom guest checks.� You must either create an application or batch file to process, delete and prints the guest check information files or use ACPRINT.EXE, available from Aloha Technologies, to process and print the guest check information files.� The custom guest check functionality is especially convenient for clients that require special guest checks for banquets.

Neither ACPRINT.EXE nor the Aloha application software offer any fault tolerance features for check information files.

Refer to document AKBID1200 for information on chit information files.

Information

The following variables enable and control guest check file output:

Variable

Location

Description

CHECKFILEPATH

System Environment

Enables guest check information files on the local terminal and defines the local location of the guest check information files.� For example, SET CHECKFILEPATH=C:\ALOHA\CHECKS

CHECKFILEDELIMITER

ALOHA.INI

Defines the field separator used in the guest check output files.� For example, CHECKFILEDELIMITER=,

FISCALPRINTEXE

ALOHA.INI

Name and location of the local terminal's application or batch file used to process guest check output files.� For example, FISCALPRINTEXE=C:\ALOHA\CHECKS\ACPRINT.EXE

SKIPALOHAPRINT

ALOHA.INI

Disables normal check printing behavior.� This does not effect checkouts or clock-in/out information.� For example, SKIPALOHAPRINT=TRUE

The CHECKFILEPATH environment variable enables guest check information files and defines the location in which to write the guest check information files.� You must set this variable independently on each terminal, and you must manually create the target folder if it does not already exist.

Each time the Aloha application software prints a check, the application software creates the check file in the CHECKFILEPATH and initializes the application or batch file defined in the FISCALPRINTEXE variable to process the file.

Since FISCALPRINTEXE and SKIPALOHAPRINT are defined in the ALOHA.INI, they are global.� This means that each local terminal will attempt to initialize the FISCALPRINTEXE in the same (local) location, and SKIPALOHAPRINT is either enabled or disabled throughout the entire system.

Guest Check Files

The guest check information files are text files labeled nnnnn.CHK, where nnnnn is the guest check number as it appears on the guest check.

The Aloha application software does not delete the processed check files (nnnnn.CHK).� The check processing application or a batch file must delete the processed check files.� The check processing application provided by Aloha Technologies, ACPRINT.EXE (discussed later in this document), automatically deletes the check files after they are processed.

The guest check files use the following format:

Keyword

Value

CLOSED

TRUE if the check is closed; FALSE if not

EMPLOYEE

Employee name, first name, last name, nickname

CASHIER

Cashier name, first name, last name, nickname (TS only)

DOB

Date of business (YYYYMMDD)

DATE

System date (YYYYMMDD)

TIME

System time (HH:MM:SS)

HEADER

Heading message line to print at the top of the check.�� May have multiple lines.

FOOTER

Footer message line to print at the bottom of the check.�� May have multiple lines.

COUNTER

Perpetual counter ID for the check, if any.

ORDERNAME

Name of the TableService table or QuickService order.

GUESTS

Number of guests.

REPRINTS

Total number of times this check has already been printed, if any.

ORDERMODE

Order mode text, if any.� (QuickService only)

REVENUECENTER

Revenue Center text, if any.

MENUNAME

Menu name, if any.� (TableService only)

ORDERATTR

The Order Attribute, if any

DAYPART

The day part, if any

ITEM

Item name, original price, printed price, quantity

QCOMBOITEM

Quick combo item name, price, quantity

PROMO

Promo name, amount, quantity

COMP

Comp name, amount

PAYMENT

Payment name, amount, tip, identifier/card number, expiration

SUBTOTAL

Subtotal of all items on check

SUBTOTAL2

Not currently supported

TOTAL1ITEM

Not currently supported

GRATUITY

The �Percentage� gratuity amount.� (TableService only)

GRATDOLLARAMT

The �Fixed Dollar� gratuity amount (TableService only)

GRATUITYTAX

Total tax charged on the auto gratuity, if any.� (TableService only)

GRATUITYTOTAL

The total + gratuities + gratuity tax

TAX

Total exclusive tax amount.

TAX2

Secondary tax ID, amount.

VOIDITEM

Voided item name, price.

SURCHARGE

Surcharge id, amount.� If surcharge is combined, then the ID is 0

MODECHARGE

Order mode ID, amount.

ROUNDADJUST

Adjustment from using �round to nickel�, if applicable

CASH

Cash payment amount.

OVERPAYMENT

Amount overpaid, not to be given as change.

CHANGE

Change due to customer.

BALANCEDUE

Balance due from customer.

SPECIALMSG

Special item modifier message to print on check.

INCLUSIVETAX

Amount of inclusive tax

MEMBER

Member ID, Member Type (TableService only)

CATTTOTAL

Category Name, Amount

QTYLINE2

Text, follows ITEM for Quantity Priced Items

Installing ACPRINT.EXE and ACPCONFIG.EXE

You can develop your own application to process the check files, or you can use ACPRINT.EXE located the \MISC\ACPRINT folder on the Aloha Application Software Installation CD.

ACPRINT.EXE limits users to letter, legal, or A4 style printers and paper.

Perform the following to install ACPRINT.EXE and ACPCONFIG.EXE on each terminal that prints custom guest checks:

Add the FISCALPRINTEXE and (if desired) SKIPALOHAPRINT variables to ALOHA.INI in the NEWDATA folder on the file server and refresh the system.

Set the CHECKFILEPATH variable on each local terminal that is to print custom guest checks, and restart the terminal.

Create a folder on the terminal for the check files.� This folder must coincide with the location assigned to CHECKFILEPATH.

Create a folder on the terminal for ACPRINT.EXE and ACPCONFIG.EXE, and copy them to the folder.� This folder must coincide with the location assigned to FISCALPRINTEXE.�

Configure the check style using ACPCONFIG.EXE.

In cases where custom guest checks are printed from selected terminals instead of the entire system (such as only on a banquet terminal), perform the following on terminals that do not print custom guest checks:

Disable the CHECKFILEPATH variable (if it exists) on terminals not printing custom guest checks.� The Aloha application software does not produce guest check information files if the CHECKFILEPATH variable does not exist.�

Instead of using ACPRINT.EXE, copy DONOTHING.EXE from the \MISC\ACPRINT folder on the Aloha Installation CD to the folder on the local terminal defined by FISCALPRINTEXE.

Rename DONOTHING.EXE to ACPRINT.EXE.� This enables the Aloha application software to launch an application called ACPRINT.EXE (that does nothing) instead of displaying an error.

Do not store ACPRINT.EXE and ACPCONFIG.EXE in the BIN or BMP folder since the Aloha application software will overwrite the ACPCONFIG.EXE configuration file (ACHECK.INI) as part of the normal file propagation behavior.

Configuring a Check in ACPCONFIG.EXE

To create a guest check design in ACPCONFIG.EXE, drag and drop the check contents to arrange them to your preference.� To enable new content, right-click the field and select 'Enabled'.� The right-click menu also contains options for font size and alignment.

Select Tools/Company Logo to select a different logo than the default.� Drag the 'Logo' text, not the actual logo, to move the logo to a different portion of the check.

ACPRINT.EXE uses the Windows default printer and does not use the printer configuration set in the Aloha application software configuration files.

Extended Information

No information.

Caveats

Neither ACPRINT.EXE nor the Aloha application software offer any fault tolerance features for check information files.

The Aloha application software does not delete the processed check files.� The check processing application or a batch file must delete the processed check files.� The check processing application provided by Aloha Technologies, ACPRINT.EXE, automatically deletes the check files after they are processed.

ACPRINT.EXE limits you to letter, legal, or A4 style printers and paper.

Do not store ACPRINT.EXE and ACPCG.EXE in the BIN or BMP folder since the Aloha application software will overwrite the ACPCONFIG.EXE configuration file (ACHECK.INI) as part of the normal file propagation behavior.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1200 Chit Information Files

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1105 acprint configurable dump

Paychex Export Files

Paychex Export Files

============================================================================

AKBID1106

Created: 27 April 2000

Updated: 2 June 2003

Reviewed: 15 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.269 � 5.3.x

Subject: Creating Paychex Payroll Export Files

============================================================================

Summary

The ALOHA^� application software supports the Paychex^� Paylink^� payroll software by creating an export file containing labor and payroll information that is imported by Paychex.� This document explains how to configure the Paychex interface in the Aloha application software and the contents of the export files.

At the time of this writing, the export files generated by the Aloha application software are not compatible with the Paychex Preview^� software.

Information

The Aloha application software creates an export file in the PAYCHEX folder during the grind process (that follows the End-of-Day process) on the last day of the pay period.� The file is labeled bbbccccs.xxx, where bbb is the Branch number, cccc is the Client number, and s is the Site Code.� Since the grind process creates the export file, debugging information is written to the grind application's Debugging-Output-File (debout).� Refer to document AKBID1134 for more information on debouts.

If the labor information is changed following the grind process, the user can manually create the export file for the last pay period in the Back-of-House (BOH).

Aloha Settings

Perform the following to enable Paychex in the Aloha application software:

1.        In versions 4.4x and lower, open Maintenance, and select Labor/Electronic Payroll Processing.

2.        In versions 5.0x and higher, open Aloha Manager, and select Maintenance/Store Settings/Labor/Electronic Payroll Processing.

3.        Enable Paychex, and define the Branch number, Client number, Pay Period, and Site Code.

4.        In versions 4.4x and lower, select Labor/Employees.

5.        In versions 5.0x and higher, select Maintenance/Labor/Employees.

6.        Assign each employee an Export ID number for Paychex, and in versions 5.0x and higher, assign the Paychex Pay Period Days.

7.        In versions 4.4x and lower, edit the ALOHA.INI in the NEWDATA folder and edit the PAYCHEXDAYS variable to reflect the desired numbers of days in the Paychex pay period (for example, PAYCHEXDAYS=7 or PAYCHEXDAYS=14).

8.        Edit the ALOHA.INI in the NEWDATA folder and edit the PAYCHEXENDDATE variable to reflect the last day of the previous complete Paychex pay period (for example, PAYCHEXENDDATE=02 15 2001).

9.        Refresh the system.

Employees without Export ID number are not included in the export file.

Manual Export File Creation

Perform the following to create the export file from the previous pay period:

1.        In versions 4.4x and lower, open Control, and select Functions/Create Paychex Pay File.

2.        In versions 5.0x and higher, open Aloha Manager, and select Functions/Export/Create Paychex Export File.

Extended Information

The Paychex export file is a comma-delimited text file using the following fields:��

Field

Import Size

Notes

Employee Number

1-9999

Uses the Export ID

Department Number

N/A

Unused, and left blank

Regular Hours

-999.99 � 999.99

Overtime Hours

-999.99 � 999.99

Pay Rate

0 � 999.999

The average pay rate for all hours for each Job Code

Credit Card Tips

-9999.99 � 9999.99

Declared Cash Tips

-9999.99 � 9999.99

Gross Wages

-999999.99 � 999999.99

Includes overtime

Caveats

Employees without Export ID number are not included in the export file.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1134 Debouts

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1106 chex pay

�

Aloha Application Software Fault Tolerance Functionality

Aloha Application Software Fault Tolerance Functionality

============================================================================

AKBID1107

Created: 20 April 2000

Updated: 12 November 2003

Reviewed: 25 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 3.6x � 5.3.x

Subject: The Aloha Application Software Fault Tolerance Functionality

============================================================================

Summary

The ALOHA^� application software offers fault tolerance features (also knows as Robust or Redundancy) for the Back-of-House (BOH) file server, the Front-of-House (FOH) terminals, and the Electronic Draft Capture (EDC) application.

Information

The following information describes the fault tolerance architecture, settings, and behavior of each component in the Aloha application software.

The Aloha application software fault tolerance features are not designed to compensate for inferior hardware, network components, wiring, or power.� It is designed to function in special circumstances when an abnormal failure occurs.� Inferior components are impossible to compensate for in the software.

File Server

In the event the Aloha application software file server malfunctions, a FOH terminal can assume the role of a temporary file server for the system.� File server fault tolerance is optional in TableService versions 3.6x through 4.2x and is always enabled (and cannot be disabled) in TableService versions 5.0x and higher.� File server fault tolerance is always enabled (and cannot be disabled) in all versions of QuickService.

If the FOH terminals lose network connectivity with the file server, the terminals 'freeze' for up to 60 seconds, after which a message stating 'The file server is down' appears.� The Master terminal displays a 'Make File Server' button.� To make this terminal the file server, touch this button, and a keypad appears along with two numbers at the bottom of the screen.� Add the two numbers together, enter the sum on the keypad, and touch OK.� The sum acts as a password.� For example, if the numbers 123 and 456 appear at the bottom of the screen, the password is 579.�

While the FOH terminal is acting as the file server, it will still run the End-of-Day (EOD) process, provided you are manually initiating it or previously configured it to automatically initiate via an event.� The dated folders are stored in the Aloha folder on the terminal acting as the file server, and you must manually move the dated folders to the BOH file server once you have successfully recovered it.� You can grind the dated folders once you have successfully moved them to the BOH file server.

If the FOH terminals lose connectivity with the file server, the FOH terminals do not automatically initiate the EOD process until the file server is restored or a terminal is assigned the role of file server.� In this case, the user may have to manually initiate the EOD process.� Refer to document AKBID1015 for more information.

The terminal remains as the file server indefinitely (including after the End-of-Day process) until the BOH file server is manually recovered.

Recover the BOH file server at any time to reinstate it as the Aloha application software file server.� Perform one of the following, based on the version number, to recover the file server:

Never perform a file server recovery by deleting the DOWNTIME.INI (refer to AKBID1195).

In versions 4.4x and lower, open Control, and select System/Fileserver Recovery.

In versions 5.0x and later, open Aloha Manager, and select Utilities/Fileserver Recovery.

Typically, the file server recovery process is virtually unnoticed from the FOH.

If the FOH terminals freeze because of lost connectivity with the file server, do not turn off or restart the terminals.� Although it is not harmful, it delays recovery.

If a FOH terminal has acted as a file server through one or more instances of the EOD process, users must manually transfer the dated folders from the temporary file server to the BOH file server.

The BOH uses the following variables in regards to fault tolerance:

Variable

IBERROOT

Description

Defines the Aloha application software folder name.�� Used with ROBUST.

System Variable Example

SET IBERROOT=<folder>

Command Line Example

N/A

Variable

ROBUST

Description

Enables fault tolerance capabilities.� (Versions 3.6x � 4.4x only.)

System Variable Example

SET ROBUST=TRUE

Command Line Example

IBER.EXE /ROBUST

Variable

SERVER

Description

SERVER defines the Aloha application software file server network name.�� Used with ROBUST.

System Variable Example

SET SERVER=<computer name>

Command Line Example

N/A

Variable

TERMSTR

Description

TERMSTR defines the setting used to override the default naming convention for terminals that must be used on all Aloha application software terminals.�� For example, if TERMSTR is set to TERM, then terminals must be named TERM1, TERM2, etc.

System Variable Example

SET TERMSTR=<name>

Command Line Example

N/A

Order Entry Terminal and Master Terminal

The FOH supports two forms of fault tolerance: the Master terminal and full network failure.� Master terminal and full network failure fault tolerance is optional in TableService versions 3.6x through 4.2x and is always enabled (and cannot be disabled) in TableService versions 5.0x and higher.� Master terminal and full network failure fault tolerance is always enabled (and cannot be disabled) in all versions of QuickService.

If the FOH terminals lose network connectivity with the Master terminal, the terminals 'freeze' for up to 60 seconds, after which a message stating 'The Master terminal is down, trying to recover' appears.� After 15 additional seconds, another terminal is elected as the Master terminal and system operation continues as usual.� The terminal remains as the Master terminal until the system is restarted because of a system refresh or the EOD process.

If the FOH terminals freeze because of lost connectivity with the Master terminal, do not turn off or restart the terminals.� Although it is not harmful, it delays recovery.

If a full network failure occurs, usually because of a malfunctioning hub, each terminal can become the Master terminal and the file server.� As the network is restored, the terminals synchronize their data, and finally elect a single Master terminal and file server.� Full recovery occurs when the Aloha application software file server is recovered from the BOH.

In the event of a full network failure or two or more terminals are using different file servers, it is important that employees are restricted to one terminal.� All employees do not have to use the same terminal, but each employee must only use a single terminal until the system is restored.� Failure to do so may result in inconsistent transactions.� For example, an employee might clock-in or clock-out at different times on two terminals.

The FOH uses the following variables in regards to fault tolerance:

Variable

IBERROOT

Description

Defines the Aloha application software folder name.�� Used with ROBUST.

System Variable Example

SET IBERROOT=<folder>

Command Line Example

N/A

Variable

LOCALDIR

Description

LOCALDIR defines the location and name of the local Aloha application software folder.�� Used with ROBUST.

System Variable Example

SET LOCALDIR=<path>

Command Line Example

IBER.EXE /LOCALDIR=<path>

Variable

MASTERCAPABLE

Description

MASTERCAPABLE designates whether the local terminal can act as a master terminal if needed.�� Used with ROBUST.

System Variable Example

SET MASTERCAPABLE=TRUE

Command Line Example

N/A

Variable

NUMTERMS

Description

NUMTERMS defines the number of physical terminals attached to the Aloha application software.�� Used with ROBUST.

System Variable Example

SET NUMTERMS=<number of terminals>

Command Line Example

N/A

Variable

ROBUST

Description

Enables fault tolerance capabilities.� (Versions 3.6x � 4.4x only.)

System Variable Example

SET ROBUST=TRUE

Command Line Example

IBER.EXE /ROBUST

Variable

SERVER

Description

SERVER defines the Aloha application software file server network name.�� Used with ROBUST.

System Variable Example

SET SERVER=<computer name>

Command Line Example

N/A

Variable

SERVERCAPABLE

Description

SERVERCAPABLE defines whether the local terminal can act as file server if needed.

System Variable Example

SET SERVERCAPABLE=TRUE

Command Line Example

N/A

Variable

TERMSTR

Description

TERMSTR defines the setting used to override the default naming convention for terminals that must be used on all Aloha application software terminals.�� For example, if TERMSTR is set to TERM, then terminals must be named TERM1, TERM2, etc.

System Variable Example

SET TERMSTR=<name>

Command Line Example

N/A

FOH Kitchen and Bar Chits

In version 5.0x and higher, kitchen chits will print on the terminal's default printer (as assigned in printer maintenance in the BOH) if all of the following are true:

1.        The local terminal is the Master terminal.

2.        There are two or more terminals defined in the system.

3.        None of the other terminals are on the network.

4.        The feature is not disabled.

To disable the feature in versions 5.0x through 5.2.6.x, open Aloha Manager, and select Maintenance/Store Settings/Printing.� Select the Chit Content subtab, and select 'Disable standalone chit printing'.

To disable the feature in versions 5.2.7.x and higher, open Aloha Manager, and select Maintenance/Store Settings/Printing-Chits.� Select the Chit Content subtab, and select 'Disable standalone chit printing'.

EDC and PMS

The EDC application spools credit card transactions and generates 'fake' credit card authorizations in the event the EDC file server (usually the Aloha application software file server) is malfunctioning.

In versions 4.0x through 4.250, credit card spooling only occurs if the EDC file server is not accessible on the network.

In version 4.251 and higher, credit card spooling also occurs if FOH requests files are not answered in a specified amount of time, or if EDCSVR.EXE (EDC Server) is not started.

Refer to the Aloha application software Credit Card User Manual or document AKBID1020 for more information on configuring EDC spooling.

At the time of this writing, the Property Management System (PMS) interface does not have fault tolerance capabilities.

Kitchen Video System

At the time of this writing, the Aloha application software does not include any internal kitchen video system (KVS) fault tolerance capabilities.

BackOffice

At the time of this writing, the Aloha application software BackOffice products do not have fault tolerance capabilities.

HASP Key

The Aloha application software requires the attachment of the Aladdin^� Hardware-Against-Software-Piracy (HASP^�) key to the temporary file server if the BOH file server is off-line for more than 21 days.

Extended Information

No information.

Caveats

The Aloha application software fault tolerance features are not designed to compensate for inferior hardware, network components and wiring, or power.� It is designed to function in special circumstances when a failure occurs.� Inferior components are impossible to compensate for from the software.

If the FOH terminals lose connectivity with the file server, the FOH terminals do not automatically initiate the EOD process until the file server is restored or a terminal is assigned the role of file server.� In this case, the user may have to manually initiate the EOD process.� Refer to document AKBID1015 for more information.

Never perform a file server recovery by deleting the DOWNTIME.INI (refer to AKBID1195).

If the FOH terminals freeze because of lost connectivity with the file server, do not turn off or restart the terminals.� Although it is not harmful, it delays recovery.

If a FOH terminal has acted as a file server through one or more instances of the EOD process, users must manually transfer the dated folders from the temporary file server to the BOH file server.

If the FOH terminals freeze because of lost connectivity with the Master terminal, do not turn off or restart the terminals.� Although it is not harmful, it delays recovery.

In the event of a full network failure or two or more terminals are using different file servers, it is important that employees are restricted to one terminal.� All employees do not have to use the same terminal, but each employee must only use a single terminal until the system is restored.� Failure to do so may result in inconsistent transactions.� For example, an employee might clock-in or clock-out at different times on two terminals.

============================================================================

See also:

Aloha QuickService or TableService User Manual

Aloha application software Credit Card User Manual

AKBID1010 Aloha Application Software System Environment Variables

AKBID1015 EOD Process and Errors

AKBID1020 EDC Process

AKBID1112 HASP Key Troubleshooting

AKBID1195 Deleting the DOWNTIME.INI

AKBID3215 DOWNTIME.INI Updates

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1107

�

Using the Crystal Reports Interface with .DBF Files

Using the Crystal Reports Interface with .DBF Files

============================================================================

AKBID1108

Created: 25 May 2000

Updated: 26 July 2002

Reviewed: 30 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

Subject: Using the Aloha Application Software Crystal Reports Interface with .DBF Files

============================================================================

Summary

The ALOHA^� application software uses an interface to Seagate Crystal Reports^� to provide customers with customized reporting beyond the Aloha application software's native reports.� The Crystal Reports interface enables customers to view reports created in the Crystal Reports software, but it does not offer any report creation capabilities of its own.

If you are using a Relational Database (RDB), refer to document AKBID1129.

Information

To access the Crystal Report interface, open Aloha Manager, and select Reports/Crystal Reports.

To add a new report, click 'Add', enter a description in the text box, and click 'Browse' to select the report file.� The report (.RPT) file must reside in the CRW folder.� Select the type of data to use, and click 'OK'.

To view a report, select the report from the list, select the historical files to use (if applicable), and click 'View' or 'Print'.

Refer to document AKBID3030 for the versions of Crystal Reports supported by the Aloha application software.�

Data Sources

The Aloha application software has three data sources for use with Crystal Reports:

1.        Configuration Files � Configuration files are the database files in the NEWDATA folder.� Use these database files for reports that list the current Aloha application software configuration, such as employees or menu prices.

2.        Dated Folders � Use the dated folders to report detailed historical data.� When the user accesses a report, they select the dated folder to use.�

Crystal Reports can not report information from multiple dated folders.� This is a limitation of the Aloha application software interface with Crystal Reports.

3.        Summary Files � Use Summary files to report summary information from a range of dates.� Summary files differ from dated folders in that they do not contain detailed information.� Refer to document AKBID1081 for more information.

Creating Crystal Reports

The information in this document supplements the Crystal Reports User Manual by explaining Aloha-related information.

When creating Crystal Reports, use .DBF files from the same version of the Aloha application software that the site uses to ensure data integrity.� Always select 'Verify on Every Print' from the Database drop-down menu on each report to ensure compatibility.

Extended Information

No information.

Caveats

Crystal Reports cannot report information from multiple dated folders.� This is a limitation of the Aloha application software interface with Crystal Reports.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1030 Grind Database Contents

AKBID1042 Aloha Application Software Database Files

AKBID1081 Summary Process and Files

AKBID1129 Using the Crystal Reports Interface with an RDB

AKBID3030 Supported Crystal Report Writer Versions

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1108

�

ICVERIFY

ICVERIFY

============================================================================

AKBID1109

Created: 3 May 2000

Updated: 31 July 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 4.233 � 5.3.x

Subject: Using ICVERIFY with the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software supports an interface with ICVERIFY.� ICVERIFY is a third-party vendor specializing in payment authorization software. This document explains how to configure the Aloha application software to use ICVERIFY.

Information

Aloha Application Software Set Up

The Aloha Application Software HASP^� security key must have ICVERIFY enabled in order to use ICVERIFY with the Aloha application software.

To access the credit card settings and enable ICVERIFY, perform the following:

In versions 4.4x and lower, open Maintenance, and select MX/EDC.

In versions 5.0x and higher, open Aloha Manager, and select Maintenance/Store Settings/Credit Card.

Select 'Enable EDC', but do not select 'Use Aloha EDC'.

Define the number of number of ICVERIFY terminals that you are licensed for.� This amount indicates the number of credit cards ICVERIFY simultaneously processes.� For example, if the number of terminals is set to 3 and three credit cards are applied at the same time, the Aloha application software sends all three credit cards to ICVERIFY at the same time, and ICVERIFY processes them in a single call.� If the amount of terminals is 1, each credit card is processed separately.

If you are using the Microsoft^� Windows^� version of ICVERIFY, edit ALOHA.INI in the NEWDATA folder, and add the following line if it does not already exist:

ICVERY_WIN=TRUE

Configure ICVERIFY credit card tenders in the Aloha application software Back-of-House (BOH) the same way that you would normally configure credit card tenders, as described in the Aloha EDC User Manual.� Enable identification and authorization for all credit card tenders.

Refresh the system.

The Aloha application software does not support credit card spooling for fault tolerance with ICVERIFY.

ICVERIFY Setup

Install ICVERIFY, according to the manufacturer's instructions, in the %IBERDIR%\IC folder.

Set the ICVERIFY Merchant Information to the %IBERDIR%\IC\DATA folder.� This is the folder that the Aloha application software writes and reads request and answer files.

Disable the ICVERIFY receipt and voucher settings, since the Aloha application software performs its own receipt and voucher printing.

Ensure the ICVERIFY Type of Business is set to F (Food), otherwise ICVERIFY does not accept requests from the Aloha application software.

� ��

Set the ICVERIFY Multi-user Wait Time to 1 second.� This is how often ICVERIFY checks for new request files from the Aloha application software.

Authorization Process

ICVERIFY runs in the background on the file server.� The following is the process in which ICVERIFY processes Aloha application software requests:

1.        The Aloha application software Master terminal sends request files (ICVERnnn.REQ, where nnn is the request number) to the %IBERDIR%\IC\DATA folder.�

2.        ICVERIFY processes the request and creates an answer file (ICVERnnn.ANS, where nnn is the answer number) in the %IBERDIR%IC\DATA folder.

3.        The Aloha application software Master terminal processes the answer file and acts on the results.

To settle or print batches from the Aloha application software Back-of-House, perform one of the following (based on the version number):

1.        In versions 4.4x and lower, open Control, and select Functions/Credit Cards/Settle Current Batch or Print Settlement.

2.        In versions 5.0x and higher, open Aloha Manager, and select Functions/IC Verify/Settle Current Batch or Print Settlement.

Going Live

To remove training data from ICVERIFY before going live, stop ICVERIFY, delete all of the files from the %IBERDIR%\IC\DATA folder, and restart ICVERIFY.

Troubleshooting

If ICVERIFY does not work properly, check the following:

1.        Is EDC enabled in the Aloha application software?

2.        Does the %IBERDIR%\IC\DATA folder exist on the file server?

3.        Is the ICVERUFY software running?

4.        Is the ICVERIFY software set to look in the %IBERDIR%\IC\DATA folder?

5.        It the tender type set up to require authorization and authorize using EDC?

6.        Are request and/or answer files generated in the %IBERDIR%\IC\DATA folder?

7.        Is the ICVERIFY Type of Business set to F (Food)?

8.        If using the Windows version of ICVERIFY, is ICVERY_WIN properly set in the ALOHA.INI?

9.        Check the Front-of-House (FOH) debouts.

Extended Information

No information.

Caveats

The Aloha Application Software HASP^� security key must have ICVERIFY enabled in order to use ICVERIFY with the Aloha application software.

The Aloha application software does not support credit card spooling for fault tolerance with ICVERIFY.

============================================================================

See also:

Aloha QuickService or TableService User Manual

Aloha EDC User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1109 ic verify

�

Installing Microsoft SQL 7.0

Installing Microsoft SQL 7.0

============================================================================

AKBID1110

Created: 18 May 2000

Updated: 2 January 2003

Reviewed: 16 December 2003

Microsoft Windows Versions: Windows NT, Windows 2000, Windows XP, Windows Server 2003

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

Subject: Installing Microsoft SQL Server for use with the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software versions 5.0x and higher support Microsoft^� SQL Server 7.0 relational-databases (RDB).� This document explains how to configure SQL Server for use with the Aloha application software, and how to install the Aloha application software in order to use a RDB.

Information

For easiest installation and configuration, setup an Aloha application software file server with SQL Server in the following order:

1.        Install and configure Microsoft^� Windows NT^�, Windows^�2000, Windows XP, or Windows Server 2003.

2.        Install and configure SQL Server.

3.        Install and configure the Aloha application software.

If you are converting an existing .DBF-based system to an SQL system, following the steps listed in this document, and reinstall Aloha from the Aloha Installation CD just as if it were a new installation.� The Aloha application software will use the existing data and configuration to create the RDB.� You will have to regrind any existing dated folders in order to add them to the RDB, though.

Operating System Configuration

Install the Windows operating system (OS) as described in the appropriate Aloha Knowledge Base (AKB) document.

The preferred hard drive-partitioning scheme for an Aloha application software file server with an RDB is different than a non-RDB Aloha application software file server.� Rather than configuring hard drive space for dated folders, space for the RDB becomes paramount.� Refer to document AKBID1183 for more information on hard drive partitions and file systems.

SQL Licenses

SQL Server requires a user license for each user or application simultaneously accessing the SQL database.� In the case of the Aloha application software, each active copy of GRIND.EXE or GRINDQ.EXE requires a license (SuperSites need a license for each store since there is an active Grind for each store), as does RPT.EXE, the local user, and each remote user.

If the number of users exceeds the number of SQL Server user licenses, the Aloha application software may not be able to access the RDB.

Installing SQL

Insert the SQL Server 7.0 installation CD.� If the installation application does not automatically start, manually start AUTORUN.EXE from the root folder of the Microsoft SQL Server 7.0 installation CD.

Install any perquisites suggested by the installation application before installing SQL Server before proceeding with the following SQL Server 7.0 instructions:

1.        Click 'Install SQL Server 7.0 Components'.

2.        Click 'Install Database Server' from the Install SQL Server 7.0 Components window.�

3.        Select 'Local Install' from the 'Select Install Method' window, and click 'Next'.

4.        Select 'Typical', and select the program and data file locations from the Setup Type window.� Install the program files on the partition intended for non-Aloha applications (C:), and install the database files on the partition intended for the RDB database files (E:).� Click 'Next'.

5.        Select 'Use the same account for each service.� Auto start SQL Server service' and select 'Use the Local System account' from the Services Accounts window.� Click 'Next'.

6.        When the installation is complete, restart the computer.

Configuring SQL

After the computer has restarted, perform the following to configure SQL Server:

1.        Click Start/Programs/Microsoft SQL Server 7.0/Enterprise Manager to open the SQL Server Enterprise Manager.

2.        On the left side of the screen, expand Microsoft SQL Servers/SQL Server Group/<the file server's network name>/Databases.

3.        Delete the 'Northwind' and 'Pubs' databases to conserve space.

4.        On the left side of the screen, expand Microsoft SQL Servers/SQL Server Group/<the file server's network name>/Security/Logins, and double-click 'Users'.

5.        Clear the 'sa' user password, and click 'OK'.

6.        On the left side of the screen, expand Microsoft SQL Servers/SQL Server Group/<the file server's network name>, right click on the file server, and select Properties.

7.        Select the Security tab and ensure that the Authentication type is configured as 'SQL Server and Windows NT'.

8.        Close SQL Server Enterprise Manager.

The Aloha application software requires a blank password for the 'sa' user during installation.� For security purposes, a password can be configured for the 'sa' user after the Aloha application software is installed.

The Aloha application software installation will not complete without a blank password for the 'sa' user, or if administrative abilities are removed from the 'sa' user.

Installing Aloha

Install the Aloha application software using the Aloha Installation CD.

Select 'MS SQL Server' on the Database Configuration window, and set the 'Computer Name' and 'Path To Database'.� The database path is typically the \MSSQL7\DATA folder on the partition intended for RDB, and should have already been created by the SQL Server installation application.� Click 'Next', finish the installation, and restart the computer.

If the Aloha application software is already installed on the file server without selecting the SQL options, reinstall the Aloha application software from the Aloha Installation CD using the SQL options.

If the Aloha application software cannot create the new RDB, open the file server properties in SQL Enterprise Manager and ensure that you configured the Security Authentication as 'SQL Server and Windows NT' rather than 'Windows NT Only'.

Configuring Aloha

The Aloha application software is automatically configured during the installation process, but you can change the amount of data stored in the RDB and the number of days before purging it.

To access the Aloha application software data storage options, open Aloha Manager, and select Maintenance/SQL Settings.� The Sales Group 1, Sales Group 2, and Payments/Labor subtabs contain options for summary data stored in the RDB.� The Grind subtab contains options for detailed data stored in the RDB.

The RDB becomes very large over time, and users should consider adjusting these settings to best suite them.� In general, the summary data is intended for long-term storage, and the detailed (or Grind) data is intended for short-term storage.

Changing the 'sa' Password

The Aloha application software requires a user name of 'sa' with a blank password to access the RDB during the initial installation process.� Once the Aloha application software is installed, user's can change the user name and password the Aloha application software uses to access the RDB.

In general, users should leave the user name and password set to 'sa' with a blank password to avoid confusion and configuration issues.� Aloha Technologies advises users to only change the user name or password when necessary.� New users must have administrative access to the databases.

Once the new user or 'sa' password is configured in SQL Server, edit the SQL.INI on the %IBERDIR%\SQL folder, and change the DBUserName and DBPassword variables to reflect the correct information.

Since the password is viewable in the SQL.INI, some users set the password to 'true', so the SQL.INI reads 'DBPassword=true'.� This is intended to appear as a setting to enable or disable the password instead of displaying the actual password.

Database Maintenance

The ability to enable auto-expansion of databases is a principal enhancement to SQL Server 7.0.� This option enables SQL Server to increase the size of the RDB as needed rather than disable the addition of new information when the RDB is full.

With auto-expansion enabled, the RDB may eventually consume the allotted hard drive space without the user knowing it.� It is imperative the user devises an RDB archiving and purging scheme to combat this problem.

Perform the following to enable auto-expansion:

1.        Click Start/Programs/Microsoft SQL Server 7.0/ Enterprise Manager to open the SQL Server Enterprise Manager.

2.        On the left side of the screen, expand Microsoft SQL Servers/SQL Server Group/<the file server's network name>/Databases.

3.        Double-click ibersql.

4.        Click 'database properties' in the General tab.

5.        Select the General tab from the ibersql Properties window.

6.        Select 'Automatically grow file' and set it to 10%.

7.        Set the maximum file size in regards to the disk space you have allocated to the RDB.

8.        Select OK.

User Maintenance

Perform the following to configure ibersql as the default database for the sa user:

1.        Click Start/Programs/Microsoft SQL Server 7.0/Enterprise Manager to open the SQL Server Enterprise Manager.

2.        On the left side of the screen, expand Microsoft SQL Servers/SQL Server Group/<the file server's network name>/Security/Logins, and double-click 'Users'.

3.        Adjust the properties of the sa user to use ibersql as the default database.

4.        Close SQL Server Enterprise Manager.

Extended Information

Remote SQL

You can also run SQL Server on a separate computer than the Aloha application software file server.� This is useful for clients that want to keep the Aloha application software SQL database consolidated with existing SQL databases on a separate SQL server.� This enables you to run Aloha Manager (and thus, Grind) on one file server and store data on a different file server.

To enable the Aloha application software to utilize a remote SQL server, install the Aloha application software on the Aloha file server as explained in the Installing Aloha section of this document, but set a different 'Computer Name' and 'Path to Database' than previously explained.� Set the SQL server's network name as the 'Computer Name' (for example, SQLSERVER) and set the SQL server's local path to the database as the 'Path to Database' (for example, E:\MSSQL\DATA).� The path must be the SQL server's local path as if you were actually on the SQL server.

You are not required to install the Aloha application software on the SQL server.

If you are using a remote SQL server on a SuperSite where you will experience a high flow of data between the Aloha file server and the SQL file server, you should consider using dedicated network adaptors for communication between the two file servers.� This will decrease the strain placed on the rest of the network, increase the bandwidth between the two file servers, and provide additional fault tolerance by bypassing the other points of failure throughout the rest of the network.

Caveats

If the number of users exceeds the number of SQL Server user licenses, the Aloha application software may not be able to access the RDB.

The Aloha application software installation will not complete without a blank password for the 'sa' user or if administrative abilities are removed from the 'sa' user.

If the Aloha application software cannot create the new RDB, open the file server properties in SQL Enterprise Manager and ensure that you configured the Security Authentication as 'SQL Server and Windows NT' rather than 'Windows NT Only'.

In general, users should leave the user name and password set to 'sa' with a blank password to avoid confusion and configuration issues.� Aloha Technologies advises users to only change the user name or password when necessary.� New users must have administrative access to the databases.

With auto-expansion enabled, the RDB may eventually consume the allotted hard drive space without the user knowing it.� It is imperative the user devises an RDB archiving and purging scheme to combat this problem.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1131 Installing a New RDB Over and Existing RDB

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID3108 Setting RDB Grind Positions

AKBID3109 Re-synchronizing DBF Files From an RDB

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1110 sql7

style='mso-spacerun:yes'>� 2003

�

Employee ID Card Format

Employee ID Card Format

============================================================================

AKBID1111

Created: 22 May 2000

Updated: 5 September 2001

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

Subject: Employee ID Card Format

============================================================================

Summary

The information in this document has been replaced by information in document AKBID1198.

Information

Extended Information

Caveats

============================================================================

See also:

AKBID1198 Magnetic Stripe Card Information

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1111

HASP Key Troubleshooting

HASP Key Troubleshooting

============================================================================

AKBID1112

Created: 10 April 2000

Updated: 29 January 2004

Reviewed: 29 January 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

Subject: Troubleshooting Aloha Application Software Security Key Errors

============================================================================

Summary

The ALOHA^� application software uses the Aladdin^� Hardware-Against-Software-Piracy (HASP^�) security key for protection against software piracy.� This document explains how to troubleshoot common problems encountered with the HASP security key.

Information

The HASP security key is a white two-inch by one-inch dongle that attaches to the parallel (LPT) or Universal-Serial-Bus (USB) port on the file server or the master terminal, depending on your Aloha application software configuration.

In robust mode (refer to document AKBID1107), CTL.EXE (versions 3.6x � 4.0x), CTLSVR.EXE (versions 4.2x � 5.0x), GRIND.EXE/GRINDQ.EXE, and IBER.EXE/IBERQS.EXE (version 5.0x and higher) verify the HASP security key's existence.� You must attach the key to the file server.

In non-robust mode, IBER.EXE (versions 3.5x � 4.4x) verifies the HASP security key's existence.� You must attach the key to the master terminal.

HASP Software Installation

The Aloha application software installs the HASP security key driver automatically during the set up process, unless you select the 'Demo' option.

The HASP security key uses the following files in the Microsoft^� Windows^� SYSTEM folder on Windows 95, Windows 98, and Windows Millennium Edition (Me) systems: HASP95.VXD, HASP95DL.VXD, and HARDLOCK.VXD.

The HASP security key uses the following files in the Windows SYSTEM32\DRIVERS folder of Windows NT^�, Windows 2000, Windows XP, and Windows Server 2003 systems: HASPNT.SYS, and HARDLOCK.SYS.� The HASP also key uses the following files in the Windows SYSTEM32 folder: HASPVDD.DLL, HASPDOS.SYS, and HLVDD.DLL.

To manually remove the HASP security key driver, type the following from a command line and restart the computer:

%IBERDIR%\BIN\HINSTALL �R

If HINSTALL.EXE does not already reside in the BIN folder, you can extract it from \ALOHATS\HINSTALL.ZIP on Aloha Installation CDs for versions 5.2.x.x and lower, or copy it from the \MISC\HASP folder on Aloha Installation CDs for versions 5.3.x.x and higher.

If the system is running Windows NT/2000/XP/2003, manually delete the HASPNT.SYS file (if it exists) in the Windows SYSTEM32 folder after manually uninstalling the HASP security key driver, but before reinstalling the HASP security key driver.

To manually install the HASP security key driver, type the following from a command line and restart the computer:

%IBERDIR%\BIN\HINSTALL �I

If you receive an error stating 'Operation failed, some processes accessing the driver are open', ensure that you have disabled all Aloha software applications, including BackOffice applications.� If this error occurs when the computer is restarting following the HASP driver installation, ensure that there are no Aloha software applications that are starting at the same time (for example, BackOffice interfaces).

Troubleshooting 'Security key not found'

The first step in troubleshooting a HASP security key error is understanding the error.� 'Security key not found' and 'Wrong security key' require two entirely different troubleshooting routes.

'Security key not found' means the Aloha application software cannot find the HASP security key, so the HASP security key activation codes entered into the Aloha application software are not the issue.� Verify the following to diagnose the cause of a 'Security key not found' error:

Ensure the HASP key is attached to the LPT port or a Universal Serial Bus (USB) port.�

If you are attaching a key to the LPT port, then the HASP key requires a LPT port that supports bi-directional data transfer.� Enhanced-Parallel-Port (EPP), Enhanced-Capabilities-Port (ECP), Bi-directional, and PS/2 LPT port interfaces are bi-directional.� Most Standard-Parallel-Port (SPP) interfaces are also bi-directional.� Ensure the LPT port interface is bi-directional.

Ensure the LPT or USB port is functioning properly.

If this message was generated by the grind application, verify that the soft-key upgrade security key activation codes have been properly configured.

Reinstall the HASP key drivers, as described in document AKBID1112.

Download HASPDIAG.ZIP from the Aloha Technologies FTP site, and extract it to a temporary folder.� Run HASPDIAG.EXE, and select the HASP Test tab.� This shows whether the utility recognizes a HASP key on the LPT or USB port.

If a printer is attached to the security key, detach the printer and verify if the problem persists.

If you are using a LPT port thumbprint scanner along with the HASP security key, refer to document AKBID3212.

If you are using Windows XP, then you must install HASP security key drivers 4.50 or higher.� They are available from http://www.hasp.com.

If you are using Windows Server 2003, then you must install HASP security key drivers 4.95 or higher.� They are available from http://www.hasp.com.

If you are using version 5.2.7.x or higher with a HASP key attached to the LPT port, then use HASPLPTPORT.EXE to verify the port assigned to the HASP key.� Refer to document AKBID1220 for more information.

Troubleshooting 'Wrong security key'

'Wrong security key number' means the Aloha application software finds the HASP security key, but the HASP security key activation codes defined in the Aloha application software software do not match the HASP security key.� Verify the following to diagnose the cause of a 'Wrong security key' error:

1.        Ensure that the HASP security key activation codes entered in the Aloha application software are correct.� Read the HASP security key activation codes directly from the \DATA\ALOHA.INI to compare them with the correct codes.� If you are using Aloha 5.0x or higher, open Aloha Manager, select Help/About Aloha Manager and verify the HASP key ID number.

2.        Ensure that the system has been refreshed since the correct HASP security key activation codes have been added in the Back-of-House (BOH).� All Aloha POS applications that read the HASP security key refer to the HASP security key activation codes listed in the ALOHA.INI file in the DATA folder.

3.        Verify that the IBERDIR (BOH) variable or the LOCALDIR (FOH) variable is set correctly.� Refer to document AKBID1010.

4.        The HASP security key activation codes supplied by Aloha Technologies could refer to a different HASP security key.� Verify the HASP security key ID number with Aloha Technologies.

5.        There may be multiple instances of the HASP security key activation codes (not remarked out) defined in the ALOHA.INI file.� Search for multiple instances of the text 'SEC1', 'SEC2', 'SEC3', 'SEC4', 'SEC5', and 'SEC6' in the ALOHA.INI file.� There should not be more than one active listing of each variable.

6.        Ensure that the [IBERTECH] line at the top of the ALOHA.INI file is not remarked out or missing (partially or wholly).

7.        Aloha application software version 5.007 or higher must be installed if the HASP security key is authorized for more than 255 terminals or if it is authorized for interface terminals.

8.        If a printer is attached to the security key, detach the printer and verify if the problem persists.

9.        If the Grind process is displaying this error, open the Grind's debout, search for the 'Wrong security key' message and note the error numbers directly above the message.� The first number represents the softkey upgrade serial number and the second number represents the HASP key serial number.� Verify that these serial numbers match your HASP security key.

10.     If the Front-of-House (FOH) is displaying this error, open the FOH debout, search for the 'Wrong security key' message and note the error numbers directly above the message.� The first number represents the HASP key serial number and the second number represents the softkey upgrade serial number.� Verify that these serial number match your HASP security key.

11.     If the FOH is displaying this error, ensure that you have restarted CTLSVR.EXE (Control Server) since updating the new HASP security key activation codes.� If you have not done so, then the BOH is broadcasting one set of codes while the FOH is reading a different set of codes from the ALOHA.INI.

Multiprocessor BSOD

Older versions of the HASP security key driver may cause the 'Blue Screen of Death' (BSOD) when used with Windows NT or Windows 2000.� This only occurs on systems with multiple processors, and when the Aloha application software is starting two or more applications that access the HASP security key at the same time.

To fix this, uninstall the current HASP security key driver, and install the HASP security key driver version 3.81 or higher.

White Key versus Green Key

The following rules apply to the usage of the white HASP security keys versus the green Fastech-issued security keys and the Aloha BackOffice suite of applications:

-          Existing sites with green security keys will continue to use the green key.� This includes upgrades of existing BackOffice products and new product additions.

-          The BackOffice products on the Aloha Installation CD only support the white security keys.

-          The BackOffice products on non-Aloha installation CDs support both the white security key and the green security key on the same CD.� Setup always prompts the user for which version of the security key they are using.

If BackOffice License Manager can't find the security key, you can click the '?' button where the serial number is supposed to be and it will tell you what kind of key it is configured to look for.

QuickService Counter Service Errors

If you receive an error in the Aloha application software FOH stating 'Only authorized for Counter Service', then HASP security key was mistakenly created for Counter Service.� The Counter Service option is available in the key generation software at Aloha Technologies, but since the Counter Service option is obsolete, it does not appear on the key information sheet, so there is no way to confirm if this option was selected for the HASP security key in question.� The only way to confirm that this is the root problem is to obtain a new HASP security key without the Counter Service option enabled.� Refer to document AKBID3260 for more information.

Extended Information

On very rare occasions, the Aloha application software may not recognize the HASP security key unless a printer or other device is connected to the HASP security key, thus terminating the signal.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1010 Aloha Application Software System Environment Variables

AKBID1040 Remote Control and Maintenance

AKBID1107 Aloha Application Software Fault Tolerance Functionality

AKBID1163 FOH HASP security key Expiration

AKBID1220 Assigning the HASP LPT Port in the Aloha Application Software

AKBID3016 HASP Driver Removal and Installation

AKBID3022 Windows NT/Windows 2000 HASP security key BSOD

AKBID3169 KEY.TXT HASP Security Key Identification Files

AKBID3212 Thumbprint Scanner and HASP Key Conflicts

AKBID3260 QuickService Counter Service Errors

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1112 bsd

�

Remote Aloha Manager

Remote Aloha Manager

============================================================================

AKBID1113

Created: 17 July 2000

Updated: 22 April 2004

Reviewed: 22 April 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

Subject: Configuring Remote Copies of Aloha Manager

============================================================================

Summary

You can configure the ALOHA^� application software Back-of-House (BOH) to access the file server from a remote computer.� This enables multiple users access the BOH for reports and database management.� This document explains how to configure remote copies of Aloha Manager.

If you are using Aloha application software versions 4.4x and lower, refer to document AKBID10403 for remote Aloha Control or Maintenance.

Because of limitations in using Microsoft^� Windows^� 95 in conjunction with Distributed Component Object Model (DCOM), Aloha Technologies does not recommend using Windows 95 on remote Aloha Manager workstations.

Information

Remote Aloha Manager requires the full installation of Aloha Manager from the Aloha installation CD on the remote workstation.� Users must perform a full installation because Aloha Manager requires several Microsoft applications (such as Internet Explorer, Data Access, and DCOM) as well as the registration of numerous .EXE and .DLL files.� Once the full installation is complete, most of the files in the Aloha folder can be removed to not needlessly consume hard drive space on the remote workstation.� Only the BIN folder and its contents stay on the remote hard drive.

Network

Establish a TCP/IP-based network connection between the remote computer and the file server.� Other network protocols may be used in conjunction with TCP/IP, but TCP/IP must be included.� Refer to document AKBID1063 for more information on TCP/IP.

Establish network file access between the remote computer and the BOOTDRV share on the file server.

Remote Aloha Manager must use a TCP/IP connection.

Non-relational Database

To install a remote copy of Aloha Manager on a non-relational database (RDB) system, perform the following steps:

1.        Ensure the network and Aloha BOOTDRV share on the file server enable the remote user full access to the file server.

2.        Install the Aloha application software on the remote workstation.� Do not enter any key numbers or select any optional components.� With the exception of the Aloha application software folder location and disabling the EDC options, leave the setup parameters at their default settings since they will be erased later and have no bearing on the final result.� You can leave the Aloha application software folder location at the default location or move it to a different location on the remote workstation hard drive.� Restart the computer when the installation is complete.

3.        On the remote workstation, open a command prompt, navigate to the BIN folder, and use the following command line to unregister CTLSVR.EXE (Control Server):

CTLSVR.EXE /UNREGSERVER

4.        Remove the BOOTDRV share from the remote workstation that was created by the installation process.

5.        Delete the entire contents of the Aloha application software folder on the remote workstation, leaving only the Aloha application software folder, the BIN folder, and the BIN folder's contents.

6.        Remove the Aloha application software environment variables from either the IBERCFG.BAT or the system environment variables (depending on the operating system).

7.        Create a shortcut to Aloha Manager on the desktop:

A.      Right-click any unused portion of the remote computer desktop and select New/Shortcut.

B.       Enter the following command in the 'Command Line' text box being sure to insert the correct server name and Aloha application software folder:

�

\\ALOHABOH\BOOTDRV\ALOHA\BIN\ALOHAMGR.EXE /IBERDIR \\ALOHABOH\BOOTDRV\ALOHA /REMOTE

C.       Click Next and enter 'Aloha Aloha Manager' as the shortcut name.

D.      Click Finish.

Relational Database

To install a remote copy of Aloha Manager on a system using a relational database (RDB), perform the following steps:

1.        Ensure the network and Aloha BOOTDRV share on the file server enable the remote user full access to the file server.

2.        Install the Aloha application software on the remote workstation.� Do not enter any key numbers or select any optional components, unless you are using a Microsoft Access database.� If you are using an Access database, set the database type to MS Access.� If you are using any other type of RDB, leave the database type configured to the default .DBF database setting.� With the exception of the Aloha application software folder location, disabling the EDC options, and configuring the Access database selection, leave the setup parameters at their default settings since they will be erased later and have no bearing on the final result.� You can leave the Aloha application software folder location at the default location or move it to a different location on the remote workstation hard drive.� Restart the computer when the installation is complete.

3.       On the remote workstation, open a command prompt, navigate to the Aloha application software BIN folder, and enter the following commands to unregister Aloha software applications and .DLL files (edit the path to REGSVR32.EXE as needed).� If you are using Aloha application software versions 5.2x or higher, you can utilize the UNREGISTER_IBER_n.BAT (where n is the version number) created by the Aloha application software installation process to unregister these application and .DLL files.� The batch file is located in the root folder of the drive in which the Aloha application software was installed.

ALOHAMGR.EXE /UNREGSERVER

CTLSVR.EXE /UNREGSERVER

ALOHASEC.EXE /UNREGSERVER

REGSVR32.EXE /U AMGRPS.DLL

REGSVR32.EXE /U AMGRSHIM.DLL (Version 5.0x only)

REGSVR32.EXE /U CTL4X.DLL

REGSVR32.EXE /U EDTPUNCH.DLL

REGSVR32.EXE /U MNT4X.DLL

REGSVR32.EXE /U USERTOOL.DLL

REGSVR32.EXE /U ASECPS.DLL

REGSVR32.EXE /U ARSEC.DLL

REGSVR32.EXE /U ARSECPS.DLL

REGSVR32.EXE /U ALOHALAB.DLL

REGSVR32.EXE /U CTLSVRPS.DLL

REGSVR32.EXE /U CRYSTL32.OCX (Versions 5.2x and higher)

4.        Remove the BOOTDRV share from the remote workstation that was created by the installation process.

5.        Delete the entire contents of the Aloha application software folder on the remote workstation, leaving only the Aloha application software folder, the BIN folder, and the BIN folder's contents.

6.        Edit the Aloha application software environment variables in either the IBERCFG.BAT or the system environment variables (depending on the operating system).� Change the IBERDIR variable to point to the Aloha application software folder on the file server (for example, SET IBERDIR=\\ALOHABOH\BOOTDRV\ALOHA) and enable SQLMODE (for example, SET SQLMODE=TRUE).� Remove all other Aloha application software variables.

7.        If the remote workstation is using the Windows NT^� or Windows 2000 operating system (OS), copy NTWDBLIB.DLL from the Windows SYSTEM32 folder on the SQL server to the Windows SYSTEM32 folder on the remote workstation.

8.        If the remote workstation is using the Windows 95, Windows 98, or Windows Millennium System (Me) OS, copy NTWDBLIB.DLL from the Windows SYSTEM32 folder on the SQL server to the Windows SYSTEM folder on the remote workstation.

9.        Restart the remote workstation.

10.     To add a new ODBC source, open the Windows Control Panel by selecting Start/Settings/Control Panel, and double-click ODBS or 32-bit ODBC.�

A.      Select the System DSN tab.

B.       Click Add from the System Data Sources window.�

C.       Select SQL Server from the Installed ODBC Drivers list in the Add Data Source window and click Finish to display the new data source configuration menu.� (If SQL Server is not present in the System Data Source window, reinstall ODBC from the ODBC folder on the Aloha POS Installation CD and select the option for SQL drivers.)

D.      Enter ALOHARDB (all capitals) as the Name.�

E.       Use 'Aloha RDB' for the Description.�

F.       Enter the SQL server's network name for the Server (for example, ALOHABOH).�

G.       Click Next.

H.      Select the SQL Server Authentication radio button, set the correct SQL login ID and password (for example, 'sa' with no password), and click Next.

I.         Select 'Change the default database to', select ibersql from the drop-down list, and click Next.

J.        Click Finish and test the data source.

K.      Close the ODBC window and the Control Panel.

11.     On the remote workstation, open a command prompt, navigate to the Aloha application software BIN folder, and enter the following commands to register Aloha software applications and .DLL files.� If you are using Aloha application software versions 5.2x or higher, you can utilize the REGISTER_IBER_n.BAT (where n is the version number) created by the Aloha application software installation process to register these application and .DLL files.� The batch file is located in the root folder of the drive or partition in which the Aloha application software was installed.� Ensure that the batch file is not set to registering the applications as services (refer to document AKBID1019).

REGSVR32.EXE AMGRPS.DLL

REGSVR32.EXE AMGRSHIM.DLL (Version 5.0x only)

REGSVR32.EXE CTL4X.DLL

REGSVR32.EXE EDTPUNCH.DLL

REGSVR32.EXE MNT4X.DLL

REGSVR32.EXE USERTOOL.DLL

REGSVR32.EXE ASECPS.DLL

REGSVR32.EXE ARSEC.DLL

REGSVR32.EXE ARSECPS.DLL

REGSVR32.EXE ALOHALAB.DLL

REGSVR32.EXE CTLSVRPS.DLL

REGSVR32.EXE CRYSTL32.OCX (Versions 5.2x and higher)

ALOHAMGR.EXE /REGSERVER

CTLSVR.EXE /REGSERVER

ALOHASEC.EXE /REGSERVER

Some applications might display a connection failure message when you register them.� If this occurs, acknowledge the message by pressing OK.� At the SQL Server Login prompt, clear 'Use Trusted Connection', and enter the correct SQL login and password (for example, the user 'sa' with a blank password).

12.     Create a shortcut to Aloha Manager on the desktop:

A.      Right-click any unused portion of the remote computer desktop and select New/Shortcut.

B.       Enter the following command in the 'Command Line' text box being sure to insert the correct server name and Aloha application software folder:

�

\\ALOHABOH\BOOTDRV\ALOHA\BIN\ALOHAMGR.EXE /REMOTE

C.       Click Next and enter 'Aloha Aloha Manager' as the shortcut name.

D.      Click Finish.

Extended Information

Some versions of Aloha Manager may display Control Server errors when Aloha Manager is started on the remote workstation.� Click OK or Cancel (depending on the error) to continue starting Aloha Manager.

Different versions of Windows may use different versions of the Microsoft Data Access Components (MDAC) that may not be compatible with each other.� If you experience problems with remote workstations accessing the RDB, download the latest version of MDAC from http://www.microsoft.com/data/download.htm and install them on the file server and remote workstations.

Remote copies of the non-RDB BOH use the RUNGRIND folder to start the Grind process for the current day's data.� Refer to document AKBID3130.� This does not apply to systems with a RDB database.

Caveats

Because of limitations in using Windows 95 in conjunction with Distributed Component Object Model (DCOM), Aloha Technologies does not recommend using Windows 95 on remote Aloha Manager workstations.

Remote Aloha Manager must use a TCP/IP connection.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1010 Aloha Application Software System Environment Variables

AKBID1019 Manually Registering and Un-registering Aloha Applications

AKBID3130 RUNGRIND File in the DATA Folder

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1113

�

Tax and Surcharge Calculations

Tax and Surcharge Calculations

============================================================================

AKBID1114

Created: 7 April 2000

Updated: 30 April 2001

Reviewed: 4 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

Subject: Aloha Application Software Tax and Surcharge Calculations

============================================================================

Summary

The ALOHA^� application software supports multiple types of taxes and surcharges.� This document provides the calculation for each type of tax and surcharge.

Information

Exclusive Primary Tax

The Aloha application software figures Exclusive taxes using the calculation (NET * RATE).

Inclusive Primary Tax

The Aloha application software figures Inclusive taxes using the calculation ((NET * RATE) / (1 + RATE)).

Secondary Tax

The Aloha application software figures Secondary taxes using the calculation (NET * RATE).

Secondary taxes do not include Primary or Vendor taxes in the calculation.

Vendor Tax

The Aloha application software figures Vendor taxes using the calculation (NET * RATE).

Vendor taxes are figured only in the Back-of-House (BOH) reports.� They are included in the Inclusive Tax section of the BOH reports, but they are not calculated the same way as Primary Inclusive taxes.� Instead, Vendor taxes multiply the Net Sales by the Vendor tax amount, just as an Exclusive tax does.� The Net Sales are decreased by the amount of the Vendor tax, thus the vendor is taxed, not the customer.�

Surcharges

Surcharges, in their original form, are designed to create an extra charge based on quantity.� For example, a restaurant sells an alcoholic drink with one-ounce of tequila for $5.95 and a one-ounce shot of tequila for $3.95.� Since the Surcharge is based on quantity, the Surcharge is the same for tequila in both instances, even though the price of each drink differs.

The Aloha application software also allows for Surcharges based on the price.� This is useful for restaurants that must charge additional fees, such as a Mall Fee or any other fee that cannot be calculated as, included in, or labeled as a tax.

The Aloha application software figures Surcharges using the calculation (QUANTITY * RATE) or (NET * RATE) depending on the setup options.

Surcharges do not include Primary or Vendor taxes in the calculation.

Additional Charges

Additional Charges in version 5.2x and higher are not included in non-GST tax calculations.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1057 Comp and Promo Taxes

AKBID1084 Smart Tax

AKBID3026 Inclusive Tax Formula

AKBID3172 Event-level Tax Reroutes

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1114

�

Configuring QSR Automations RDS Ethernet Video

Configuring QSR Automations RDS Ethernet Video

============================================================================

AKBID1115

Created: 7 April 2000

Updated: 28 October 2003

Reviewed: 13 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.412 � 5.3.x

Subject: Using QSR Automations RDS Ethernet Video with the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software supports the QSR^� Automations RDS-2000 Video Kitchen-Video-System (KVS).� This enables restaurants to use network lines and the existing network hub to run the KVS system instead of serial ports and serial cables.� This document explains how to configure RDS-2000 for use with the Aloha application software.

If you are configuring QSR Automations KDS product, refer to document AKBID1217.

Information

This document is written to supplement the Aloha Video User Manual and the RDS-2000 User Manual, not to replace them.

The Aloha application software communicates with the RDS-2000 differently than other KVS systems in that the Aloha application software does not communicate directly with the KVS hardware, but instead, the Aloha application software communicates with the RDS-2000 software (service).� The RDS-2000 software, in turn, communicates with the KVS hardware.� For this reason, you must install and configure the RDS-2000 software on each POS terminal driving a video monitor.

Setup

Configure the RDS-2000 software as a Stand Alone host in QSR.� The Aloha application software does not support primary and secondary hosts.� You can configure a second Stand Alone host to serve as a backup, but you can only enable one at a time (via the QSRVIDEOS system environment variable) in the Aloha application software.� Refer to the Backup Host section of this document for more information.

If the host is using the Microsoft^� Windows^� 95 Operating System (OS), download the Winsock2 installation files (W95WS2.ZIP) from the Aloha Technologies FTP site, and install them on the terminal.

�

If the host is using the Microsoft Windows NT^� Operating System (OS), install Windows NT Service Pack 5 or later to install the required Winsock2 drivers.

After you have installed the RDS-2000 software, replace the RDSAPI.DLL in the Aloha Application Software BIN folder on the file server with the RDSAPI.DLL from the Windows SYSTEM folder (Windows 95, Windows 98, or Windows Me) or the Windows SYSTEM32 folder (Windows NT, Windows 2000, or Windows XP) on the host.� This propagates the correct RDSAPI.DLL file to the BIN folder all of the terminals, including the hosts.

Although you must install the RDS-2000 software on the host, it does not need to be started in order for the videos to work.� Only start the RDS-2000 software to change the configuration.

Refer to the RDS-2000 User Manual for more information.

Touch Screen Event Configuration

If you are using a touch screen to bump orders QSR versions 5.0 or higher, you must configure the touch screen actions that translate into system events.� Set this to �Touch downs should generate system events� in the QSR software configuration, otherwise the Aloha application software will not register the touch.� Refer to the RDS-2000 User Manual for more information.

Network

The RDS-2000 software communicates with the TCP/IP protocol.� The IP addresses for the host and the video controllers are assigned in the RDS-2000 software.� The IP addresses assigned in the RDS-2000 software must be on the same subnet as IP addresses assigned the file server and terminals.

Refer to the RDS-2000 User Manual for more information.

Environment Variables

Configure the following system environment variables on any terminal that is driving videos:

Variable

QSRMODE

Applications

VIDEOMX.DLL

Description

Sets the QSR video characters per line and number of lines on the monitor.� Mode 1 is 40x25, and Mode 3 is 80x25.� If not set, Mode 3 is the default.

System Variable Example

SET QSRMODE=<1 or 3>

Command Line Example

N/A

Variable

QSRVIDEO

Applications

VIDEOMX.DLL

Description

Selects the QSR video type.� Always set to NATIVE for RDS-2000.

System Variable Example

SET QSRVIDEO=NATIVE

Command Line Example

N/A

Variable

QSRVIDEOS

Applications

VIDEOMX.DLL

Description

Enumerates the number of QSR video device(s) that are driven by the host.� Ensure that you do not configure multiple hosts (using QSRVIDEOS environment variable) to drive the same video device.

System Variable Example

SET QSRVIDEOS=<1>,<2>,<3>

Command Line Example

N/A

Refer to the Aloha Video User Manual for more information.

Backup Host

The Aloha application software does not support the Primary and Secondary Host functionality in the QSR software, but you can configure a second Stand Alone Host to act as a backup QSR host.

If you create a second host, then you must not enable the QSRVIDEOS system environment variable on the second host.� If multiple hosts are configured (using QSRVIDEOS environment variable) to drive the same video device, then each terminal is sending duplicate order messages and bumps to each video device and log file.� This also creates additional burden on the network, which can slow down the FOH terminal�s and video device�s performance.� The easiest method to prevent this is to remark (REM) out the QSRVIDEOS variable on the second host, and only enable this variable as needed.

Ensure that you do not configure multiple hosts (using QSRVIDEOS environment variable) to drive the same video device.

ARP Cache Troubleshooting

Windows uses the Address-Resolution-Protocol (ARP) cache (or table) to resolve TCP/IP address with Media-Access-Control (MAC) addresses.� Each time you bring a new QSR controller online, Windows resolves the controller�s TCP/IP address and MAC address.� Since QSR controllers are shipped with the same address, turning them all on at once can confuse Windows since multiple devices will claim the same TCP/IP address, but have different MAC addresses.� The QSR software, in turn, will not be able to communicate with some of the devices.

The best method to prevent this problem is by bringing each device online one at a time, assign the correct address, and then bring the next device online.� If you think the ARP cache may contain incorrect entries, you can use the Windows ARP.EXE application to delete incorrect ARP entries.� Open a command prompt and type the following to view the ARP.EXE syntax, options, and usage:

ARP.EXE -?

General Troubleshooting

Do not plug-in or unplug any RDS-2000 peripherals while the power is on.

Verify the proper QSR IP addresses are used and if they are compatible with the rest of the application software IP addresses.� Refer to the Network section of this document.

If the video screen becomes distorted, press the Refresh button on the bump bar.

Generate additional QSR video debugging information in the debout files by adding the following line to the system environment on the Host computer and restart the computer:

SET DEBUGQSR=TRUE

This variable is considered true regardless of the assigned value.�� If this variable is not desired, completely remove it.

If the firmware on each video controller is not the same version, you may experience erratic problems.

Refer to the Aloha Video User Manual and the RDS-2000 User Manual for more information.

Extended Information

No information.

Caveats

You must install the correct RDSAPI.DLL and Winsock2 files for the RDS-2000 KVS system to function properly with the Aloha application software.

Do not plug-in or unplug any RDS-2000 peripherals while the power is on.

Ensure that you do not configure multiple hosts (using QSRVIDEOS environment variable) to drive the same video device.

============================================================================

See also:

Aloha Video User Manual

RDS-2000 User Manual

AKBID1217 Configuring QSR Automations KDS

AKBID3068 Bump to Video Group

AKBID3249 QSR Ethernet Creates Very Large Transaction and Video Logs

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1115 rds2000

�

File Server/Terminal Limitations

File Server/Terminal Limitations

============================================================================

AKBID1116

Created: 18 April 2000

Updated: 25 August 2003

Reviewed: 4 March 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Aloha Application Software Limitations on File Server/Terminals

============================================================================

Summary

The ALOHA^� application software Back-of-House (BOH) and Front-of-House (FOH) can function together on a single computer that acts as both the file server and an order entry terminal, but there are limitations to this configuration.� This document explains these limitations and the work-arounds associated with them.

Information

There are two major limitations when running the FOH and BOH on the same computer: restarting the FOH after a refresh or after the End-of-Day process (refer to document AKBID1015), and the location of the dated folders created after the EOD process.

Restarting the FOH

The FOH restarts after a refresh or after the EOD process.� After a refresh is initiated in the BOH, the BOH creates a STOP file in the TMP folder on the file server.� The STOP file instructs the FOH to restart.� If the STOP file still exists after the FOH restarts, the FOH will not finish initializing until the STOP file no longer exists.

When a computer is only running the FOH, the AUTOEXIT variable (refer to document AKBID1010) instructs the FOH to restart the operating system (OS).� The OS subsequently starts the FOH from the Microsoft^� Windows^� StartUp folder.

A computer running the FOH and BOH together cannot use the AUTOEXIT variable, because the FOH might exit and restart Windows following a refresh before the Aloha application software completes the refresh process and deletes the STOP file.� This will result in the FOH not restarting without use intervention.

Instead, run the FOH from a looping batch file utilizing the WAIT.EXE utility (refer to document AKBID1012).� This way, a batch file restarts the FOH without restarting Windows, and it properly compensates for the time required for the refresh to complete.�

Label the batch file FOHSTART.BAT, place it in the root Aloha application software folder (for example, D:\ALOHA\FOHSTART.BAT), and include following lines in the batch file:

@ECHO OFF

:START

CLS

ECHO *** Do not close this batch file. ***

ECHO *** It is required to auto restart Aloha. ***

IF EXIST %LOCALDIR%\TMP\EXITING DEL %LOCALDIR%\TMP\EXITING

START /WAIT %LOCALDIR%\BIN\IBER.EXE

CLS

ECHO *** Waiting 10 seconds for refresh. ***

WAIT.EXE 10

GOTO START

This batch file performs the following functions:

1.        Disables unneeded text from appearing on the screen.

2.        Clears the screen.

3.        Displays a warning to not close the batch file, since it is essential for restarting the FOH.

4.        Deletes the EXITING file, if it exists.

5.        Starts the FOH using the START /WAIT command.� The START /WAIT command instructs the batch file to wait for the FOH to exit before proceeding to the next line in the batch file.� '/WAIT' is in no way connected with the WAIT.EXE utility described later in this document.� /WAIT is a standard Microsoft command-line variable, and WAIT.EXE is a utility supplied by Aloha Technologies.

6.        After the FOH exits, the batch file clears the screen.

7.        The batch file uses the WAIT.EXE utility (refer to document AKBID1012 for more information) to create ten-second pause while the BOH finishes the refresh procedure, and starts the batch file over again.

The batch file is always active on the FOH/BOH computer, and it continually restarts the FOH anytime it exits.� Use shortcuts to the batch file (instead of shortcuts directly to IBER.EXE or IBERQS.EXE) in the Windows StartUp folder, desktop, Start Menu, or wherever else you place a shortcut to start the FOH.

EXITING File

The %IBERDIR%\TMP\EXITING file signals other FOH terminals that the local terminal is shutting down or is not currently running IBER.EXE or IBERQS.EXE.� The file warns other terminals not to create a network connection since the terminal is restarting.� IBER.EXE and IBERQS.EXE create a local copy of this file upon exiting and delete the local EXITING file when they start.�

If you are not using a looping batch file as explained in the 'Restarting the FOH' section of this document, then you can end up with a stray EXITING file on the file server and the other FOH terminals will not start.� To resolve this, use a batch file to start the FOH that initializes the FOH and then deletes the EXITING file after the FOH shuts down, rather than just running IBER.EXE or IBERQS.EXE directly.� For example:

START /WAIT %LOCALDIR%\BIN\IBER.EXE

ECHO Y | DEL %LOCALDIR\TMP\EXITING

EXIT

Dated Folders

If you select 'Run Front of House and Back of House on same PC' when you install the Aloha application software on a PC running Windows 95, Windows 98, or Windows Millennium Edition (Me), then SETUPPOS.EXE assigns the NONET variable to CTLSVR.EXE (Control Server).� This means the application software is always in redundant mode (refer to document AKBID1107).� This means that if the FOH is not started on the FOH/BOH computer, it does not broadcast file server capabilities; so another FOH terminal may assume file server functionality.� This does not inhibit the FOH functionality of the application software, but it can cause confusion when the EOD process creates dated folders.

The EOD process creates the dated folder on whichever computer is the current file server.� If a different computer has assumed the role of file server instead of the designated FOH/BOH computer, then the EOD process creates the dated folder on a FOH terminal.� Although you can manually move the dated folder from the FOH terminal to the FOH/BOH computer, it might cause confusion.

At the time of this writing, there is not a sufficient fix or work-around for this problem if you are using a FOH/BOH computer with the Windows 95, Windows 98, or Windows Me.

If you are using Windows NT^�, Windows 2000, Windows XP, or Windows Server 2003, then SETUPPOS.EXE does not assign the NONET variable to Control Server in versions 5.2x and higher.� Network functionality inherent to Windows NT, Windows 2000, and Windows XP enables Control Server to run without the NONET variable, thus alleviating the problem of another terminal assuming file server capabilities, unless specifically instructed by the user.

If you are installing Aloha versions 5.0x or lower and you are using Windows NT, Windows 2000, Windows XP, or Windows Server 2003, then you can perform the following to manually remove the NONET variable from the Control Server variables in the Windows Registry on the FOH/BOH computer in order to enable the application software to run in non-redundant mode:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_CLASSES_ROOT\AppId\{81DD90A1-CF22-11D1-A84F-0080AD1C6910}.

3.        Then double-click AlohaCtlSrvParameters and remove the NONET variable from Value Data.

4.        Select Registry/Exit to exit the Windows Registry Editor

5.        Restart the computer.

Disabling the FOH on the File Server

If your FOH/BOH computer is using Windows NT, Windows 2000, Windows XP, or Windows Server 2003, and you disable or shut down the Aloha application software FOH on the FOH/BOH computer, the remaining FOH terminals will no longer recognize the FOH/BOH computer as the Aloha application software file server until you restart them. You can set the MASTERCAPABLE and SERVERCAPABLE system environment variables to FALSE in versions 5.026 and higher in order to prevent this from occurring, but this also disables the FOH from functioning on the FOH/BOH computer should the network become disabled.

If you set MASTERCAPABLE and SERVERCAPABLE to FALSE and you also require the ability to use the FOH/BOH computer in stand-alone mode following a network failure, you can create a secondary method to start the FOH via a batch file that enables the MASTERCAPABLE and SERVERCAPABLE variables.� For example, create a batch file in the Aloha application software BIN folder labeled FOHXNET.BAT with the following information:

SET MASTERCAPABLE=TRUE

SET SERVERCAPABLE=TRUE

START %LOCALDIR%\BIN\IBER.EXE

Create a shortcut to the batch file on the Windows desktop (or wherever you deem appropriate), but make sure the user can differentiate this shortcut from the normal shortcut used to start the FOH.� In the event they encounter network problems that require each terminal to enter stand-alone mode, they can start the FOH on the FOH/BOH computer using this batch file.

FSRECOVERYEOD in the ALOHA.INI

If you have FSRECOVERYEOD assigned a value of TRUE in the ALOHA.INI, a file server recovery results in deletion of the TRANS.LOG (transaction log).� You must set this variable to FALSE on a FOH/BOH computer.

Extended Information

No information.

Caveats

Use a looping batch file to start the FOH on a FOH/BOH computer.� Do not start the FOH application directly.

When using a FOH/BOH computer with the Windows 95, Windows 98, or Windows Me operating system, another terminal can assume file server capabilities and create dated folders during the EOD process on another terminal besides the designated FOH/BOH computer.� This does not occur with Windows NT, Windows 2000, or Windows XP.

============================================================================

See also:

AKBID1010 Aloha Application Software System Environment Variables

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1015 EOD Process and Errors

AKBID1023 Windows 95 File Server/Terminal Setup

AKBID1024 Windows 98 File Server/Terminal Setup

AKBID1037 Windows NT File Server/Terminal Setup

AKBID1094 Windows 2000 File Server/Terminal Setup

AKBID1107 Aloha Application Software Fault Tolerance Functionality

AKBID3226 FSRECOVERYEOD in the ALOHA.INI

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1116 boh/foh bohfoh foh/boh fohboh stage staging stage staging stage staging terminal/server

�

Using Anti-virus Software on FOH Terminals

Using Anti-virus Software on FOH Terminals

============================================================================

AKBID1117

Created: 19 April 2002

Updated: 9 May 2002

Reviewed: 23 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

Subject: Configuring Anti-virus Software for use on Front-of-House Terminals

============================================================================

Summary

The ALOHA^� application software Front-of-House (FOH) functions properly with an anti-virus software package installed and active as long as you follow some general guidelines, but with some anti-virus software packages, the FOH requires explicit configurations.� This document explains the general configuration options required for all anti-virus software packages and also any specific configuration requirements for anti-virus software packages that Aloha Technologies has tested.

Information

In general, FOH terminals running anti-virus software along with the Aloha application software require additional memory and processor speed in order for the terminals to function smoothly.� The amount of extra memory and processor speed required depends on several factors, such as the anti-virus software developer's recommendations, the hardware provider's recommendations, the number of POS terminals, and the amount of stress placed on the system.

If you experience slow-downs or even Microsoft^� Windows^� errors that you can attribute to the anti-virus software, then you should consider performing the following:

-          Increase the amount of memory on the FOH terminals.

-          Meter the amount of memory and CPU processing on FOH terminals to determine if there is a memory or CPU speed deficiency.

-          Disable unneeded anti-virus options.� For example, configure the anti-virus software to only scan certain file types, such as BAT, BIN, COM, DLL, EXE and SYS, rather than all file types.�

-          Many anti-virus software packages have multiple layers of protection, so review the software user's manual to determine if you can disable any other unnecessary forms of protection.

Norton AntiVirus

Aloha Technologies has performed stress tests using Symantec^� Norton AntiVirus^� 2000 and we have determined the following configuration settings are required for use with the Aloha application software:

-          Do not enable real-time protection for all file types, but instead, only the following file types: BAT, BIN, COM, DLL, EXE and SYS.

-          Configure Norton AntiVirus to only scan files when on creation or if they are modified in the Advanced settings.

-          Disable Bloodhound^� virus detection in the Heuristics settings.

Aloha Technologies also recommends using a minimum of 32-megabytes of memory for FOH terminals using TableService if you are not using Floor Plan.� If you are using TableService with Floor Plan or if you are using QuickService, you are required a minimum of 64-megabytes of memory with anti-virus software.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1117 anti virus

�

SuperSite IBERCFG.BAT

SuperSite IBERCFG.BAT

============================================================================

AKBID1118

Created: 27 April 2000

Updated: 30 June 2003

Reviewed: 3 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 4.2x � 5.3.x

Subject: Aloha Application Software SuperSite IBERCFG.BAT File

============================================================================

Summary

ALOHA^� application software SuperSites use an IBERCFG.BAT for the Front-of-House (FOH) terminals that differs significantly from the IBERCFG.BAT used at a non-SuperSite.� The SuperSite IBERCFG.BAT file is designed for easier maintenance on a system with a large number of terminals.

Information

One basic requirement of a SuperSite is consistency and this concept carries over to the IBERCF.BAT.� Unlike a regular site that has less than 10 terminals, the SuperSite might have hundreds of terminals.� Knowing the exact contents of the IBERCFG.BAT without having to verify them on each terminal enables easier support.� You can accomplish this by using the same IBERCFG.BAT file for each terminal, and placing it in the SuperSite file server's BIN folder.� Storing the IBERCFG.BAT in the SuperSite file server's BIN folder enables you to edit the IBERCFG.BAT on the SuperSite file server, and let the Aloha application software propagate the file to each terminal with the rest of the BIN file contents the next time the FOH terminal restart.

Changes to the IBERCFG.BAT require the terminals to restart a second time, just as new binary files do.

Another batch file (either the AUTOEXEC.BAT or a terminal IBERCFG.BAT, refer to document AKBID1199 for more information on the AUTOEXEC.BAT or terminal IBERCFG.BAT) initially declares the system path and the TERM system environment variable, updates the BIN folder with the contents of the NEWBIN folder, and calls the SuperSite IBERCFG.BAT file discussed in this document.� The SuperSite IBERCFG.BAT does the bulk of the work by using a layout that enables the user to add both global and terminal specific settings.

The SuperSite IBERCFG.BAT performs the following:

Declares global environment variables.

Uses the TERM environment variable passed from the AUTOEXEC.BAT or terminal IBERCFG.BAT to set terminal-specific environment variables.� Refer to document AKBID1199 for more information on the AUTOEXEC.BAT or first-level IBERCFG.BAT.

Starts any optional applications or utilities.

Once you have properly configured your SuperSite IBERCFG.BAT, you can configure terminals as explained in document AKBID1199.

The following is an example of a SuperSite IBERCFG.BAT:

Do not enable the LOCALREAD variable on terminals that are not master and server-capable.� If a terminal is not master or server-capable, it does not synchronize the local DATA folder with the file server, so the information in the local DATA folder is not current.

You must assign the SERVER variable a value of UNUSED and assign a value to the MULTISERVER variable in order to enable SuperSite functionality in the FOH.

SET AUTOEXIT=TRUE

SET IBERROOT=ALOHA

SET LOCALDIR=C:\%IBERROOT%

SET LOCALREAD=TRUE

SET MASTERCAPABLE=TRUE

SET MASTERFILEFREQ=2160

SET MULTISERVER=\\ALOHAPOS\BOOTDRV\ALOHA

SET ROBUST=TRUE

SET SERVER=UNUSED

SET SERVERCAPABLE=TRUE

GOTO %TERM%

:1

:2

SET EDCPATH=\\ALOHAEDC\BOOTDRV\ALOHA\EDC

SET PMSPATH=\\ALOHAPMS\BOOTDRV\ALOHA\PMS

SET NUMTERMS=2

SET STOREID=1

SET TERMSTR=ARENA

GOTO END

:3

:4

:5

:6

SET EDCPATH=\\ALOHAEDC\BOOTDRV\ALOHA\EDC

SET PMSPATH=\\ALOHAPMS\BOOTDRV\ALOHA\PMS

SET NUMTERMS=4

SET STOREID=2

SET TERMSTR=DINING

GOTO END

:7

SET EDCPATH=\\ALOHAEDC\BOOTDRV\ALOHA\EDC

SET PMSPATH=\\ALOHAPMS\BOOTDRV\ALOHA\PMS

SET NUMTERMS=1

SET STOREID=3

SET TERMSTR=BAR

GOTO END

:END

IF EXIST %LOCALDIR%\TMP\EXITING DEL %LOCALDIR%\TMP\EXITING

Windows Me, Windows NT, Windows 2000, and Windows XP

If you are using the Windows Millennium Edition (Me), Windows NT, Windows 2000, or Windows XP operating systems, you have to configure the end of the SuperSite IBERCFG.BAT to start IBER.EXE or IBERQS.EXE.� For example, using the previous example, the last section would appear as the following:

:END

IF EXIST %LOCALDIR%\TMP\EXITING DEL %LOCALDIR%\TMP\EXITING

START %LOCALDIR%\BIN\IBER.EXE

Since you are using the same SuperSite IBERCFG.BAT for all of your terminals, you have to configure the SuperSite IBERCFG.BAT to compensate for SuperSites using both QuickService and TableService terminals.� The previous example would only work for a site with only QuickService terminals or only TableService terminals, so you must create a variable that defines if the store is QuickService versus Table Service and assign the variable to each store.�

For example, create a variable labeled QUICK and assign it a value of TRUE or FLASE in each store's section.� For example:

:1

:2

SET EDCPATH=\\ALOHAEDC\BOOTDRV\ALOHA\EDC

SET PMSPATH=\\ALOHAPMS\BOOTDRV\ALOHA\PMS

SET NUMTERMS=2

SET QUICK=TRUE

SET STOREID=1

SET TERMSTR=ARENA

GOTO END

:3

:4

:5

:6

SET EDCPATH=\\ALOHAEDC\BOOTDRV\ALOHA\EDC

SET PMSPATH=\\ALOHAPMS\BOOTDRV\ALOHA\PMS

SET NUMTERMS=4

SET QUICK=FALSE

SET STOREID=2

SET TERMSTR=DINING

GOTO END

At the end of the batch file, use this variable to determine whether to start IBER.EXE or IBERQS.EXE.� For example:

:END

IF EXIST %LOCALDIR%\TMP\EXITING DEL %LOCALDIR%\TMP\EXITING

IF %QUICK%==TRUE START %LOCALDIR%\BIN\IBERQS.EXE

IF %QUICK%==FALSE START %LOCALDIR%\BIN\IBER.EXE

The example above could also work with SuperSites using a mix of both Windows 95 or Windows 98 terminals and Windows Me, Windows NT, Windows 2000, and Windows XP terminals.� Since Windows 95 and Windows 98 terminals start IBER.EXE or IBERQS.EXE from a direct shortcut in the Windows StartUp folder, then setting the QUICK variable to 'NULL' will bypass the last two lines and the FOH will start via the Windows StartUp folder.

Extended Information

No information.

Caveats

Changes to the IBERCFG.BAT require the terminals to restart a second time, just as new binary files do.

Do not enable the LOCALREAD variable on terminals that are not master and server-capable.� If a terminal is not master or server-capable, it does not synchronize the local DATA folder with the file server, so the information in the local DATA folder is not current.

You must assign the SERVER variable a value of UNUSED and assign a value to the MULTISERVER variable in order to enable SuperSite functionality in the FOH.

============================================================================

See also:

Aloha SuperSite User Manual

AKBID1125 SuperSite Time Synchronization

AKBID1126 SuperSite-Specific System Environment Variables

AKBID1150 Using LMHOSTS with a SuperSite

AKBID1199 Configuring a SuperSite FOH Terminal

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1118

�

FOH Adjustable Resolution Settings

FOH Adjustable Resolution Settings

============================================================================

AKBID1119

Created: 3 May 2000

Updated: 14 November 2003

Reviewed: 27 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.144 � 5.3.x

Subject: Using the Aloha Application Software Adjustable Screen Resolution Settings

============================================================================

Summary

You can use the ALOHAXRES and ALOHAYRES environment variables to override the default FOH ALOHA^� application software Front-of-House (FOH) screen resolution.� In versions 5.021 and lower, the default resolution is 640x480.� In versions 5.022 and higher, the default resolution is based on the Microsoft^� Windows^� resolution settings.

Refer to document AKBID1165 for more information on FOH screen resolutions.

Information

The ALOHAXRES and ALOHAYRES variables are only required in the rare case that you need to override the default FOH resolution settings.� You do not need to configure these variables for most installations.

Changing the FOH Resolution

The FOH uses the following system environment variables to define screen resolutions different than the default resolution:

Variable

ALOHAXRES

Applications

IBER.EXE, IBERQS.EXE

Description

Specifies the 'x' screen resolution for the FOH (in pixels).

System Variable Example

SET ALOHAXRES=1024

Command Line Example

N/A

Variable

ALOHAYRES

Applications

IBER.EXE, IBERQS.EXE

Description

Specifies the 'y' screen resolution for the FOH (in pixels).

System Variable Example

SET ALOHAYRES=768

Command Line Example

N/A

Do not use the Windows large fonts settings with the ALOHAXRES and ALOHAYRES variables.� The ALOHAXRES and ALOHAYRES variables use the default Windows small fonts setting.

The FOH button and tender bitmaps are automatically stretched (or shrunk) according to the resolutions, and they do not require manual resizing.

Extended Information

No information.

Caveats

Do not use the Windows large fonts settings with the ALOHAXRES and ALOHAYRES variables.� The ALOHAXRES and ALOHAYRES variables use the default Windows small fonts setting.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1097 Aloha Application Software Font Name and Size Variables

AKBID1165 FOH Screen Resolution Settings

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1119 600 800 800x600 768 1024 1024x768 entire full fullscreen re-size resize

�

Delivery Street Address File (ZONE.TXT)

Delivery Street Address File (ZONE.TXT)

============================================================================

AKBID1120

Created: 5 May 2000

Updated: 12 March 2002

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 5.0x � 5.3.x

Subject: Delivery Street Address File (ZONE.TXT)

============================================================================

Summary

The ALOHA^� application software BackOffice Delivery/Frequent Buyer application uses the ZONE.TXT file to limit the restaurant's delivery area and assist users when entering new customer address information.� This document explains how to configure ZONE.TXT for use with the Aloha application software.

Information

ZONE.TXT is a tab delimited text file (meaning each column is separated by a tab) that resides in the Aloha application software DATA folder, and uses the following columns (not labeled in the file):

1.        Street Name � The street name.

2.        Start Address Number � The starting number in the address range.

3.        End Address Number � The ending number in the address range.

4.        Zone Code � Used in conjunction with the Zone field in the customer information.

The following is an example of a ZONE.TXT file:

1ST ST�� 5200� 5299� NH9

2ND ST�� 0�� 5399� NH9

2ND ST�� 5500� 7000� NH10

3RD ST�� 5200� 5299� NH8

4TH ST�� 5100� 5699� NH8

5TH ST�� 5500� 5699� NH8

Users can manually create the ZONE.TXT file, or import information from an external database using Microsoft Excel^� or Microsoft Access^�.� Whichever method you use to create ZONE.TXT, ensure that you place a carriage return at the end of the file.�

Failure to add the carriage return to the end of ZONE.TXT will result in illegal operation errors in the Front-of-House (FOH).

Using ZONE.TXT

When ZONE.TXT exists, the Aloha application software uses the file to verify that the customer's address is within the delivery zone.� When a user enters a street name, the Aloha application software uses information in the ZONE.TXT file to automatically complete the street name.

If the street or address is not listed in ZONE.TXT, the user receives an error stating 'This street name in not within our delivery area'.

If the ZONE.TXT file exists, users cannot enter new customer address information that is not defined in the ZONE.TXT file.

Extended Information

No information.

Caveats

Failure to add the carriage return to the end of ZONE.TXT will result in illegal operation errors in the Front-of-House (FOH).

If the ZONE.TXT file exists, users cannot enter new customer address information that is not defined in the ZONE.TXT file.

============================================================================

See also:

Aloha QuickService or TableService User Manual

Aloha Delivery/Frequent Buyer User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1120

�

Reroute All Chits to Local Printers

Reroute All Chits to Local Printers

============================================================================

AKBID1121

Created: 9 May 2000

Updated: 18 June 2001

Reviewed: 27 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.8x � 5.3.x

Subject: Rerouting All Kitchen and Bar Chits to Local Receipt Printers

============================================================================

Summary

Some restaurants may want to separately print the kitchen and bar chits to local receipt printer (for example, wines <cut> entr�es <cut> sides <cut> desserts <cut>), and the order-entry employee manually delivers the chits to the kitchen or bar.� Although the ALOHA^� application software does not have specific functionality for this, you can still configure your printers, printer groups, and events in order to perform this task.

Information

This document is based on a 4-terminal restaurant that requires separate chits for wine, bar, appetizers, entrees and desserts.

In order for the Aloha application software to print separate chits for each category, you must reroute printers using the 'Reroute Printer' event.� Rerouting only the printer groups places all items on a single chit.

To do this, you must set up the four physical printers and printer groups, and add a virtual printer and printer group for each terminal and each category.� This produces four physical printers and printer groups, and 20 virtual printers and printer groups.

All items are routed to the virtual terminal one printer group for the category.� A 'Reroute Print by Terminal' event reroutes the terminal one virtual printer group to the correct terminal's virtual printer group.� After that, a 'Reroute Printer' event reroutes the virtual printer to the local receipt printer.

In versions 5.007 through 5.026, you might have to disable stand-alone chit printing (part of the Aloha application software fault tolerance capabilities) in order for the functionality described in this document to function properly.� To disable stand-alone chit printing, edit the ALOHA.INI in the Aloha application software NEWDATA folder, set the DISABLESTANDALONECHITPRINT variable to TRUE (for example, DISABLESTANDALONECHITPRINT=TRUE) and refresh the system.

Printers

Create the following printers in the Back-of-House (BOH):

Printer ID

Printer Name

Terminal

1

Terminal 1 Receipt

1

2

Terminal 2 Receipt

2

3

Terminal 3 Receipt

3

4

Terminal 4 Receipt

4

11

Terminal 1 App

Unassigned

12

Terminal 2 App

Unassigned

13

Terminal 3 App

Unassigned

14

Terminal 4 App

Unassigned

21

Terminal 1 Bar

Unassigned

22

Terminal 2 Bar

Unassigned

23

Terminal 3 Bar

Unassigned

24

Terminal 4 Bar

Unassigned

31

Terminal 1 Dessert

Unassigned

32

Terminal 2 Dessert

Unassigned

33

Terminal 3 Dessert

Unassigned

34

Terminal 4 Dessert

Unassigned

41

Terminal 1 Entree

Unassigned

42

Terminal 2 Entree

Unassigned

43

Terminal 3 Entree

Unassigned

44

Terminal 4 Entree

Unassigned

51

Terminal 1 Wine

Unassigned

52

Terminal 2 Wine

Unassigned

53

Terminal 3 Wine

Unassigned

54

Terminal 4 Wine

Unassigned

Printer Groups

Create the following printer groups in the BOH and add the specified printer to each group:

Group ID

Group Name

Printers

1

Terminal 1 Receipt

1

2

Terminal 2 Receipt

2

3

Terminal 3 Receipt

3

4

Terminal 4 Receipt

4

11

Terminal 1 App

11

12

Terminal 2 App

12

13

Terminal 3 App

13

14

Terminal 4 App

14

21

Terminal 1 Bar

21

22

Terminal 2 Bar

22

23

Terminal 3 Bar

23

24

Terminal 4 Bar

24

31

Terminal 1 Dessert

31

32

Terminal 2 Dessert

32

33

Terminal 3 Dessert

33

34

Terminal 4 Dessert

34

41

Terminal 1 Entree

41

42

Terminal 2 Entree

42

43

Terminal 3 Entree

43

44

Terminal 4 Entree

44

51

Terminal 1 Wine

51

52

Terminal 2 Wine

52

53

Terminal 3 Wine

53

54

Terminal 4 Wine

54

Assign Item Routing

Assign all items to the terminal 1 printer group for the specific category.� For example, route all wines to 'Terminal 1 Wine', all desserts to 'Terminal 1 Dessert', and so on.

Reroute Printer by Terminal Events

Create the following 'Reroute Print by Terminal' events in the BOH to fire daily at 00:00:

Terminal

From Group

To Group

2

11

12

3

11

13

4

11

14

2

21

22

3

21

23

4

21

24

2

31

32

3

31

33

4

31

34

2

41

42

3

41

43

4

41

44

2

51

42

3

51

43

4

51

44

Reroute Printer Events

Create the following 'Reroute Printer' events in the BOH to fire daily at 00:00:

From Printer

To Printer

1

1

2

2

3

3

4

4

21

1

22

2

23

3

24

4

31

1

32

2

33

3

34

4

41

1

42

2

43

3

44

4

51

1

52

2

53

3

54

4

Menu-level Reroutes

Menu-level reroutes are still available.� For example, to disable bar chits for the bar menu, add a menu-level reroute from 'Terminal 1 Bar' to 'none'.

Extended Information

No information.

Caveats

In versions 5.007 through 5.026, you might have to disable stand-alone chit printing (part of the Aloha application software fault tolerance capabilities) in order for the functionality described in this document to function properly.� To disable stand-alone chit printing, edit the ALOHA.INI in the Aloha application software NEWDATA folder, set the DISABLESTANDALONECHITPRINT variable to TRUE (for example, DISABLESTANDALONECHITPRINT=TRUE) and refresh the system.

Printing chits with held items may produce unpredictable printing results.

============================================================================

See also:

Aloha TableService User Manual

AKBID3106 Separating Chits on a Single Printer

AKBID3193 Printing One Item on Two Chits Using a Single Printer

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1121 sullivan's sullivans

�

Select Electronics Video

Select Electronics Video

============================================================================

AKBID1122

Created: 11 May 2000

Updated: 15 December 2003

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.0x � 5.3.x

Subject: Using Select Electronics Video with the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software supports the Select Electronics kitchen-video-system (KVS).� You must adjust dual in-line Package (DIP) switches and jumpers in the Select Electronics KVS components to properly interface them with the Aloha application software.

Refer to document AKBID1233 if you are using the Select OAsys Kitchen Display System.

Information

For more info on setting up the Select Electronics KVS system, refer to the Aloha Video User Manual or the Select Electronics user manual available at http://www.selectelectronics.com.

When adjusting the Select Electronics KVS system settings, you must restart the Select Electronics components along with the Aloha application software.

SV2000 Controller

SW1 assigns the SV2000 controller a unique video ID number, baud rate, and keypad type.� The ID matches the video ID assigned in the Aloha application software Back-of-House (BOH).� Use the following table to set the SV2000 controller to the correct ID, baud rate, and keypad:

ID

DIP 1

DIP 2

DIP 3

DIP 4

DIP 5

DIP 6

DIP 7

DIP 8

ID 1

Off

Off

Off

Off

Off

Off

Off

Off

ID 2

On

Off

Off

Off

Off

Off

Off

Off

ID 3

Off

On

Off

Off

Off

Off

Off

Off

ID 4

On

On

Off

Off

Off

Off

Off

Off

ID 5

Off

Off

On

Off

Off

Off

Off

Off

Further ID numbers are listed in the Select Electronics user manual.

Use the following table to set the SW2 DIP switches:

DIP 1

DIP 2

DIP 3

DIP 4

Off

Off

On

Off

Use the following table to set the SW3 DIP switches:

DIP 1

DIP 2

DIP 3

DIP 4

DIP 5

DIP 6

DIP 7

DIP 8

On

On

On

On

On

On

On

Off

Use the following table to set the jumpers:

Jumper Number

Jumper Pins

JP1

Factory

JP2

None

JP3

1 � 2

JP4

1 � 2

JP5

1 � 2

JP6

1 � 2

JP7

1 � 2

JP8

None

SK4400 Bump Bar

JP3 assigns the SK4400 bump bar a unique video ID number, baud rate, and beeper control.� The ID matches the video ID assigned in the Aloha application software BOH.� Use the following table to set the SV2000 controller to the correct ID, baud rate, and beeper control:

ID

DIP 1

DIP 2

DIP 3

DIP 4

DIP 5

DIP 6

DIP 7

DIP 8

ID 1

Off

Off

Off

Off

Off

On

Off

On

ID 2

On

Off

Off

Off

Off

On

Off

On

ID 3

Off

On

Off

Off

Off

On

Off

On

ID 4

On

On

Off

Off

Off

On

Off

On

ID 5

Off

Off

On

Off

Off

On

Off

On

Further ID numbers are listed in the Select Electronics user manual.

Use the following table to set the JP1 jumpers:

Pin Set

Jumper

Pin Set 1

C � B

Pin Set 2

C � B

Pin Set 3

C � B

Pin Set 4

None

Pin Set 5

C � B

Pin Set 6

None

Pin Set 6

C � B

Pin Set 8

C � B

SCM221 Serial Conversion Module

Jump pins 1 and 2 on JP1 to set it to full duplex, or FDX.

Windows Settings

Adjust the Microsoft Windows settings for the COM port driving the KVS to 38,400 baud rate and no flow control.

Environment Settings

The Aloha application software uses the SVIDEOS, SVMODE, and SVPORT environment variables to communicate with the Select Electronics KVS system.�

SVIDEOS enumerates the number of Select Electronics KVS device chained off the serial port.� For example, if video numbers one, two, and three are connected to the port, the SVIDEOS variable is the following:

SET SVIDEOS=1,2,3

If video numbers one, three, and five are connected to the port, the SVIDEOS variable is the following:

SET SVIDEOS=1,3,5

SVMODE sets the video characters per line and number of lines on the monitor.� Mode 1 is 40x25, and Mode 3 is 80x25.� This is not typically used.

SVPORT sets the serial port to which the Select Electronics KVS system is attached.� For example, if the KVS system uses port number two, the variable is the following:

SET SVPORT=2

Extended Information

No information.

Caveats

When adjusting the Select Electronics KVS system settings, users must restart the Select Electronics components along with the Aloha application software.

============================================================================

See also:

Aloha Video User Manual

AKBID1233 Select Electronics OAsys Kitchen Display System

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1122

style='mso-spacerun:yes'>� 2003

�

Multiple Concept EDC on a Single File Server

Multiple Concept EDC on a Single File Server

============================================================================

AKBID1123

Created: 15 May 2000

Updated: 30 January 2002

Reviewed: 5 February 2004

Microsoft Windows Versions: Windows NT, Windows 2000, Windows XP, Windows Server 2003

Aloha Products: EDC

Aloha POS Versions: 5.020 - 5.3.x

Subject: Multiple Concept EDC on a Single File Server

============================================================================

Summary

An ALOHA^� application software file server running separate copies of QuickService and TableService (or two copies of QuickService or TableService) can use a single copy of the Electronic Draft Capture (EDC) application to process credit cards for both concepts.� This document explains the proper EDC configuration for this type of environment.� Refer to document AKBID1124 for more information on configuring multiple concepts on the same file server.�

This document is intended for an environment where EDC is on the same file server as each concept's application software.� If EDC resides on a separate and dedicated EDC server, refer to document AKBID1174.� If you are setting up a separate and dedicated EDC file server for use with a SuperSite or with a single TableService or QuickService site, refer to document AKBID1095.

Information

Create and Populate an ALOHAEDC Folder

Create an ALOHAEDC folder in the file server's BOOTDRV share (for example, D:\ALOHAEDC), and create BIN, DATA, EDC, NEWDATA, and TMP folders inside the new folder.

Copy the following files from either one of the concept's BIN folder to the \ALOHAEDC\BIN folder: CB532.DLL, EDC.EXE, EDCSEC.DLL, EDCSVR.EXE, EDCSVRPS.DLL, IBERSTR.DLL (5.2x and higher) and SHW32.DLL.

Environment Variables

If Aloha Manager was configured as described in document AKBID1124, then the Back-of-House (BOH) applications use a batch file to declare the required environment variables.� This leaves the Microsoft^� Windows NT^�, Windows^� 2000, Windows XP, and Windows Server 2003 system environment variables available for use by EDC.

Add IBERDIR, IBERROOT and EDCPATH variables to the Windows system environment variables that reference ALOHAEDC folder and restart the computer.

Unregister Previously Registered EDC Files

Unregister any previously registered EDC application and .DLL files using the following command lines (a successful confirmation should follow each command):

Edit the path to REGSVR32.EXE as needed.

%IBERDIR%\BIN\EDCSVR.EXE /UNREGSERVER

C:\WINNT\SYSTEM32\REGSVR32.EXE /U %IBERDIR%\BIN\EDCSEC.DLL

C:\WINNT\SYSTEM32\REGSVR32.EXE /U %IBERDIR%\BIN\EDCSVRPS.DLL

Register EDC Server

Open a command prompt and register EDCSVR.EXE as a service using the following command line (a successful confirmation should follow the registration):

%IBERDIR%\BIN\EDCSVR.EXE /SERVICE

If you are using EDC Server versions 5.230 and higher, EDC Server prompts you for the user configuration.� This is the user with which EDC Server will log in.� You can instruct EDC Server to use the Windows local system account (the default configuration in versions 5.229 and lower) or you can configure a specific user name and password.� You must configure a specific login in instances where the operating system on the FOH terminals does not enable network access by the Windows local system account.�

You can use the /LOCALACCOUNT command line variable to instruct EDC Server to register using the Windows local system account without prompting the user.� For example:

%IBERDIR%\BIN\EDCSVR.EXE /SERVICE /LOCALACCOUNT

You can use the /ACCOUNTNAME and /PASSWORD command line variables to instruct EDC Server to register using a specific user name and password.� For example:

EDCSVR.EXE /SERVICE /ACCOUNTNAME .\<user name> /PASSWORD <password>

If you are using a domain account, you can specify the domain name using the following command line:

EDCSVR.EXE /SERVICE /ACCOUNTNAME <domain name>\<user name> /PASSWORD <password>

Register DLL Files

Open a command prompt and use the following command lines to register EDC .DLL files (a successful confirmation should follow the registration):

Edit the path to REGSVR32.EXE as needed.

C:\WINNT\SYSTEM32\REGSVR32.EXE %IBERDIR%\BIN\EDCSEC.DLL

C:\WINNT\SYSTEM32\REGSVR32.EXE %IBERDIR%\BIN\EDCSVRPS.DLL

Restart the computer.

Edit TRM.DBF and STO.DBF Files

Under normal circumstances, EDC only uses TRM.DBF and the TERMSTR and IBERROOT system environment variables to resolve the terminal network names required to poll the Front-of-House (FOH) terminals for spooled credit card files.� If two concepts share the same file server, each concept's terminals must use different TERMSTR (and possibly IBERROOT) system environment variables, thus single variables can not be relied on to resolve the terminal network names.�

Like SuperSites, a location with multiple concepts on the same file server must use STO.DBF in conjunction with TRM.DBF instead of the TERMSTR and IBERROOT system environment variables to resolve the terminal network names.� Manual changes to the TRM.DBF and STO.DBF are required to create separate TERMSTR and IBERROOT variables for each concept.

Edit TRM.DBF in each concept's NEWDATA folder and set the store ID in the STORE field for each Concept One terminal to '1' and each Concept Two terminal to '2'.� Refresh both concepts to update TRM.DBF in the DATA folder.� As explained later in this document, EDC will use a single TRM.DBF created by combining each concept's TRM.DBF using COMBITM.EXE.

Copy STO.DBF from either one of the concept's NEWDATA folder to the \ALOHAEDC\NEWDATA folder.� Edit \ALOHAEDC\NEWDATA\STO.DBF and add the following information:

Field

Description

Concept One

Concept 2

ID

Store ID Number

1

2

OWNERID

Used with CDM

0

0

USERNUMBER

Used with CDM

1

1

NAME

Store Name

QS

TS

NETNAME

Store's TERMSTR

QSTERM

TSTERM

IBERDIR

Store's IBERROOT

ALOHAQS

ALOHA

REGION

Supersite Region

1

1

STOREACC

Used with CDM

0

0

PARENTACC

Used with CDM

0

0

Copy the updated STO.DBF in the \ALOHAEDC\NEWDATA folder to the \ALOHAEDC\DATA folder.

Create Combined TRM.DBF

Use COMBITM.EXE (refer to document AKBID1012 for more information) to combine the \NEWDATA\TRM.DBF files from each concept into a single TRM.DBF.

Copy the combined TRM.DBF to both the \ALOHAEDC\NEWDATA and \ALOHAEDC\DATA folders.

Copy Configuration Files

Copy the following files from either concept's NEWDATA folder to the \ALOHAEDC\NEWDATA and DATA folders: ALOHA.INI, EMP*.*, SECLVL*.* and VER.*.

Updating EDC POS Configuration Files

To ensure the configuration files used by EDC are updated on a regular basis, create the following EDCUPD.BAT file in the \ALOHAEDC\BIN folder to shut down EDC, update the files, and restart EDC on a daily basis:

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

Close EDC.EXE using CLOSEAPP.EXE (refer to document AKBID1012 for more information) and stop EDCSVR.EXE:

START /WAIT CLOSEAPP.EXE /QUIT ALOHA EDC

START /WAIT NET STOP EDCSVR

Copy the required configuration files to \ALOHAEDC\NEWDATA and DATA folders (the files can be copied from either concept):

COPY D:\ALOHAQS\NEWDATA\ALOHA.INI %IBERDIR%\NEWDATA

COPY D:\ALOHAQS\NEWDATA\EMP*.* %IBERDIR%\NEWDATA

COPY D:\ALOHAQS\NEWDATA\SECLVL*.* %IBERDIR%\NEWDATA

COPY D:\ALOHAQS\NEWDATA\VER.* %IBERDIR%\NEWDATA

COPY %IBERDIR%\NEWDATA\*.* %IBERDIR%\DATA\*.*

Restart EDCSVR.EXE and EDC.EXE:

START /WAIT NET START EDCSVR

START %IBERDIR%\BIN\EDC.EXE

EXIT

Save the file in either the Windows folder if you are using the Windows Schedule Service (refer to document AKBID1047) to initialize the file each night, or save the file in one of the concept's BIN folder if you are using Winhook (refer to document AKBID1028) to initialize the file each night.� Setup either the Windows Schedule Service or Winhook to initialize the file each night to update the configuration files.� Windows 2000, Windows XP, and Windows Server 2003 users can instead employ Window Task Scheduler to initialize the file each night in place of the Windows Schedule Service.

You should also consider adding a shortcut to EDCUPD.BAT to the Windows desktop users can manually update the data if needed.

EDC Shortcuts

Create an 'Aloha Credit Cards' (EDC.EXE) shortcut on the desktop, start menu, and anywhere else it is needed.� A shortcut to EDC is not required in the Windows StartUp folder since EDC is registered as a Windows service.

FOH Terminal Settings

Add or adjust the EDCPATH variable on the POS terminals to provide the path to the EDC folder on the file server (for example, SET EDCPATH=\\ALOHABOH\BOOTDRV\ALOHAEDC\EDC).

Upgrading EDC.EXE

Upgrades to the Aloha application software on the EDC file server requires replacement and registration of all application files and .DLL files listed previously in this document.�

Extended Information

Refer to document AKBID3053 for information on assigning each concept (or each terminal) to separate EDC processor accounts.

Multiple-concept PMS is set up the same as EDC, the only difference being the PMS settlement (as explained in document AKBID3066) and use of the PMSPATH variable on the FOH terminals.

Caveats

This document is intended for an environment where EDC is on the same file server as each concept's application software.� If EDC resides on a separate and dedicated EDC server, refer to document AKBID1174.� If you are setting up a separate and dedicated EDC file server for use with a SuperSite or with a single TableService or QuickService site, refer to document AKBID1095.

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

============================================================================

See also:

AKBID1124 Multiple Concepts on a Single File Server

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1020 EDC Process

AKBID1028 Winhook

AKBID1047 Microsoft Windows Schedule Service

AKBID1095 Stand-Alone EDC File Server

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1174 Stand Alone EDC File Server for Multiple Concepts

AKBID3053 Terminal-specific EDC Processors

AKBID3066 SuperSite PMS Settlement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1123 multi multiconcept qs/ts qsts tsqs ts/qs same

Multiple Concepts on a Single File Server

Multiple Concepts on a Single File Server

============================================================================

AKBID1124

Created: 17 July 2000

Updated: 29 January 2004

Reviewed: 29 January 2004

Microsoft Windows Versions: Windows NT, Windows 2000, Windows XP, Windows Server 2003

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.020 � 5.3.x

Subject: Multiple Concept Aloha Manager Applications on a Single File Server

============================================================================

Summary

You can configure the ALOHA^� application software in a way that enables both a QuickService concept and a TableService concept to use a single file server without resorting to SuperSite functionality.� Although this document focuses on installing a single QuickService store and a single TableService store, you can also apply these instructions to a single file server running either two QuickService stores or two TableService stores.

Radiant Systems does not recommend installing more than two separate concepts on a single file server.

You cannot use the configuration in this document with a Relational-Database (RDB).

Information

Before proceeding with this document, prepare Microsoft^� Windows^� on the file server as explained in document AKBID1036 (Windows NT^�), document AKBID1093 (Windows 2000), document AKBID1177 (Windows XP), or document AKBID1224 (Windows Server 2003).

Install TableService

Install TableService on the file server using the Aloha Installation CD.� Do not select the option to run CTLSVR.EXE (Control Server) as a service, and do not install EDC at all.� Refer to document AKBID1123 for EDC installation instructions following the completion of this document.

Restart the computer when instructed by the setup application.

Install QuickService

Using the Aloha Installation CD, install QuickService on the file server in a different folder than TableService.� For example, install TableService in the D:\ALOHA folder and QuickService in the D:\ALOHAQS folder.� Do not select the option to run CTLSVR.EXE as a service, and do not install EDC at all.

Restart the computer when instructed by the setup application.

Remove the IBERDIR Variable from Control Server

Control Server is assigned an IBERDIR variable in the Windows registry may interfere with the new environment variables set by batch files later in this document.� Perform the following to remove the IBERDIR variable from Control Server in the Windows registry:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_CLASSES_ROOT\AppId\{81DD90A1-CF22-11D1-A84F-0080AD1C6910}.

3.        Double-click AlohaCtlSrvParameters and remove ' /IBERDIR D:\ALOHA' from the Value Data.

4.        Select Registry/Exit to exit the Windows Registry Editor.

Delete System Environment Variables and Setup Batch Files

Some of the system environment variables created by the Aloha Installation CD may interfere with the new environment variables set by batch files later in this document.� Delete the following from the Windows system environment variables so they do not interfere with the new assignments: IBERDIR, IBERROOT, NUMTERMS, and TERMSTR.� Leave the ROBUST and SERVER variables in place since they are common to both QuickService and TableService.

Create batch files labeled AMGRQS.BAT and AMGRTS.BAT in the BIN folder for each concept to set the necessary environment variables and start Aloha Manager.� The batch files should look similar to the following, but with the correct variable values:

SET IBERROOT=ALOHA

SET IBERDIR=D:\%IBERROOT%

SET NUMTERMS=1

SET TERMSTR=TSTERM

START %IBERDIR%\BIN\ALOHAMGR.EXE /NOMUTEX /CTLSVRNOCOM

The NOMUTEX switch disables mutual exclusivity, which enables you to open multiple copies of Aloha Manager on the same computer.

CTLSVRNOCOM instructs Aloha Manager to initiate Control Server using a Create_Process command rather the normal COM command.� This is required since COM uses the information in the registry, and you cannot have information for both Aloha installations (concepts) in the registry because they would interfere with one another.� In this environment, Aloha Manager communicates with Control Server using flag files in the TMP folder rather than through COM.

Create shortcuts to both batch files to replace the shortcuts to ALOHAMGR.EXE in the start menu and on the desktop.� Since Control Server is not running as a service, also put shortcuts in the Windows StartUp folder.

Since Control Server is not running as a service, Aloha Technologies strongly recommends the use of Windows auto-logon.� Refer to document AKBID1005 for more information.

FOH Terminal Names and ID Numbers

The Front-of-House (FOH) terminals are configured as normal, but each concept must use unique TERMSTR names, ID numbers, and LOCALDIR names.� For example, the following chart shows settings for a location with four TableService terminals and five QuickService terminals:

Concept

TERMSTR

TERM

Network Name

LOCALDIR

TS

TSTERM

1

TSTERM1

ALOHA

TS

TSTERM

2

TSTERM2

ALOHA

TS

TSTERM

3

TSTERM3

ALOHA

TS

TSTERM

4

TSTERM4

ALOHA

QS

QSTERM

5

QSTERM5

ALOHAQS

QS

QSTERM

6

QSTERM6

ALOHAQS

QS

QSTERM

7

QSTERM7

ALOHAQS

QS

QSTERM

8

QSTERM8

ALOHAQS

QS

QSTERM

9

QSTERM9

ALOHAQS

In the example, the NUMTERMS setting for TableService is four, and the NUMTERMS setting for QuickService is five.

Unique network workgroup names or IP subnets are not required for each store and should not be employed.

Extended Information

Upgrades

When you perform an upgrade to the Aloha application software, you cannot use the 'One-Button-Upgrade' feature on the Aloha Installation CD.� You must use the installation CD to reinstall each concept as if it where a new installation.� SETUPPOS.EXE will not overwrite existing data, so it will effectively perform an upgrade.� Once you have upgraded each concept, ensure that you remove or edit any new shortcuts or environment variables created by SETUPPOS.EXE.

Sharing a Remote Chit Printer

If multiple stores share a single remote chit printer, you must configure the remote printer similar to the information in document AKBID1156.

Caveats

Radiant Systems does not recommend installing more than two separate concepts on a single file server.

You cannot use the configuration in this document with a Relational-Database (RDB).

Since Control Server is not running as a service, Aloha Technologies strongly recommends the use of Windows auto-logon.� Refer to document AKBID1005 for more information.

FOH terminals for each concept (QuickService or TableService) must use unique TERMSTR names, terminal ID numbers, and LOCADIR names.� Unique network workgroup names and IP address are not required.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1005 Microsoft Windows Automatic Logon

AKBID1036 Microsoft Windows NT File Server Setup

AKBID1093 Microsoft Windows 2000 File Server Setup

AKBID1123 Multiple Concept EDC on a Single File Server

AKBID1156 Using Windows Printer Between Stores in a SuperSite

AKBID1177 Microsoft Windows XP File Server Setup

AKBID1224 Windows Server 2003 File Server Setup

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1124 multi multiconcept qs/ts qsts tsqs ts/qs same

�

SuperSite Time Synchronization

SuperSite Time Synchronization

============================================================================

AKBID1125

Created: 15 May 2000

Updated: 21 April 2003

Reviewed: 13 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.0x � 5.3.x

Subject: Synchronizing SuperSite Terminal Times

============================================================================

Summary

ALOHA^� application software SuperSites do not use Synctime functionality (refer to document AKBID1065), but instead, use the Microsoft^� Windows^� NET TIME command, which synchronizes the local time with a specific computer's time.

The information in this document is also useful for Non-SuperSites that do not with to use Synctime.

Information

The NET TIME command requires matching time configuration on the terminal and file server.� Prior to enabling the NET TIME command, ensure that all terminals and the file server are set to the same time zone, and daylight savings is enabled throughout the entire system, or daylight savings disabled throughout the entire system.

Create a batch file labeled SETTIME.BAT in the BIN folder on the SuperSite file server with the following information in it (use the correct file server name):

NET TIME \\ALOHABOH /SET /YES

After refreshing the system in order to propagate SETTIME.BAT out to the Front-of-House (FOH) terminals, create a shortcut to the batch file in each terminal's Windows StartUp folder.� This ensures that the time is updated each time Windows starts.� Also ensure that 'Close on exit' is enabled in the shortcut.�

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

AKBID1065 Aloha Synctime and Windows Time Zone Configuration

AKBID1118 SuperSite IBERCFG.BAT

AKBID1126 SuperSite-Specific System Environment Variables

AKBID1199 Configuring a SuperSite FOH Terminal

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1125 nettime.bat

�

SuperSite-Specific System Environment Variables

SuperSite-Specific System Environment Variables

============================================================================

AKBID1126

Created: 15 May 2000

Updated: 11 October 2002

Reviewed: 12 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: SuperSite-Specific Environment Variables

============================================================================

Summary

ALOHA^� application software SuperSites use three environment variables that are not used in regular sites: MASTERFILEFREQ, MULTISERVER, and STOREID.� An understanding of each of these is required to properly support a SuperSite.

Information

MASTERFILEFREQ

The MASTERFILEFREQ variable edits the frequency in which the store's Master terminal updates the MASTER file in the store folder (%IBERDIR%\STRnnnn) on the file server.�

The MASTER file contains the name of the current Master terminal in the store, and is used by the Grind process.

If the MASTER file is incorrect, the Grind process may not function properly, or the store may not properly perform an immediate refresh if an immediate refresh is invoked.

Set MASTERFILEFREQ to 2160 (or SET MASTERFILEFREQ=2160), which is 2,160 clicks.� There are approximately 18 clicks in a second, so the MASTER file is updated every 2 minutes.

MULTISERVER

Rather than using the SERVER variable, SuperSites use the MULTISERVER variable to identify the SuperSite's file server, sometimes referred to as a 'Super-Server' or 'Multi-Server'.

Although each SuperSite store has its own local file server, the selection and assignment is performed automatically, thus the SERVER variable is set by IBER.EXE or IBERQS.EXE.

The MULTISERVER variable maps the file server, the Aloha share, and the Aloha folder.� For example, SET MULTISERVER=\\ALOHABOH\BOOTDRV\ALOHA.

You must assign the SERVER variable a value of UNUSED in order to enable SuperSite functionality in the FOH.� For example, SET SERVER=UNUSED.

STOREID

This refers to the Store ID the terminal is assigned to in the Aloha application software Back-of-House (BOH).� For example, SET STOREID=2.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha SuperSite Technical Manual

AKBID1118 SuperSite IBERCFG.BAT

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1126 site super superserver

�

Printing BackOffice Gift Certificates When Sold

Printing BackOffice Gift Certificates When Sold

============================================================================

AKBID1127

Created: 31 May 2000

Updated: 1 June 2000

Reviewed: 29 January 2004

Microsoft Windows Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 5.0x � 5.2.x

Subject: Printing BackOffice Gift Certificates When They are Sold in the POS

============================================================================

Summary

You can automatically print ALOHA^� application software BackOffice Gift Certificates to a designated printer when the gift certificate is sold or when the check is closed.� You can use an office-type printer or a Front-of-House (FOH) receipt-type printer to print the gift certificates.� This document explains how to configure gift certificates to print when you sell them.

Information

You can print gift certificates on office printers (such as inkjet or laser printers) or use FOH receipt printers.� Aloha Technologies suggests using an office printer instead of a FOH receipt printer because they (typically) print faster than receipt printers, and they offer more gift certificate design options.� Overall, office printers provide a better gift certificate presentation than receipt printers do.

For help on designing gift certificates or using the BackOffice Gift Certificate application, refer to the Aloha BackOffice Gift Certificate User Manual.

Office Printer

The office printer used to print gift certificates must reside on the network (either as a local printer, a network printer, or shared from another computer on the network) along with the Aloha application software, and you must configure it as a Microsoft^� Windows^� printer on the file server.

Refer to Microsoft documentation for help adding and configuring a Windows printer.

Perform the following to designate the Gift Certificate printer:

Set up the printer in Windows on the file server.

Open the Aloha Interface on the file server, and select File/Setup.

Select the POS Terminal Options tab.

Select the printer from the Certificate Printer drop-down menu.� If the printer is not listed, then it is not setup in Windows, and you cannot use it until you configure it as a Windows printer.

Select OK.

Restart the interface.

Receipt Printer

You must setup the FOH receipt printer used to print gift certificates as a Windows-based printer, and you must defined as a Windows printer on both the file server and in the Aloha application software (refer to document AKBID1026).�

Refer to Microsoft documentation for help adding and configuring a Windows printer.

If the printer is set to a standard serial or parallel printer in the Aloha application software, the Aloha Interface will not have access to the receipt printer while the Aloha application software is functioning.� The receipt printer must be set up as a Windows printer in the Aloha application software receipt printer maintenance to print both receipts and gift certificates.

Perform the following to designate the Gift Certificate printer:

Set up the receipt printer in Aloha Manager as described in document AKBID1026, and share the printer to allow print access to the file server.

Set up the printer in Windows (as a network printer) on the file server.

Open the Aloha Interface on the file server, and select File/Setup.

Select the POS Terminal Options tab.

Select the printer from the Certificate Printer drop-down menu.� If the printer is not listed, then it is not setup in Windows, and you cannot use it until you configure it as a Windows printer.

Select OK.

Restart the interface.

Print on Order or on Close

The Aloha application software can print the gift certificate when it is ordered (sold) or when the check is closed.

Gift certificates are printed when they are ordered by default, and there are no other settings for this.� To print gift certificates when the check is closed, perform the following:

Open Aloha Manager, and select Maintenance/Store Settings/Gift Certificate.�

Select 'Print Sold Gift Certificates on Close Check'.

Save your changes and refresh the system.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

Aloha BackOffice Gift Certificate User Manual

AKBID1002 Aloha Receipt and Kitchen Printer Settings

AKBID1026 Using Windows-based Printers with Aloha

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1127

�

Moving Aloha Data to a New File Server

Moving Aloha Data to a New File Server

============================================================================

AKBID1128

Created: 17 May 2000

Updated: 10 November 2003

Reviewed: 23 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Moving Data From an Old File Server to a New File Server

============================================================================

Summary

This document explains the proper procedure to move ALOHA^� application software database, and historical files from an old file server to a new file server.

Information

Set up the new file server as instructed in the corresponding AKB document, and install the Aloha application software from the Aloha Installation CD.� Once the new file server has Microsoft^� Windows^� and the Aloha application software installed and configured, copy the data from the old file server.

This process should occur after the system has completed the End-of-Day (EOD) process and before new transactions are added to the new Date-of-Business (DOB).�� Transactions include sales, labor, and Front-of-House (FOH) configuration changes such as rerouting printers for videos.

Aloha Data

After the Aloha application software is installed on the new file server, turn off the Front-of-House (FOH) terminals, close all Aloha software applications on both file servers, and copy the following files from the old file server to the like location on the new file server:

Files

Location

Notes

All files

%IBERDIR%\yyyymmdd

Dated folders

All files

%IBERDIR%\BIN

Aloha applications.� These files are restored if the Aloha application software is reinstalled, unless the BIN folder contains any site-specific files.� You can also restore these from the FOH terminals.

All files

%IBERDIR%\BMP

Aloha BMP files.� You can also restore these from the FOH terminals.

All files

%IBERDIR%\CORPDATA

Centralized Data Management (CDM) information.

All files

%IBERDIR%\CRW

Seagate Crystal Reports^�.� These files are restored if the Aloha application software is reinstalled, unless the CRW folder contains any site-specific reports.

All files

%IBERDIR%\NEWDATA and DATA

Aloha configuration files.� You can also restore these from the FOH terminals.

EDC.INI

%IBERDIR%\EDC

EDC configuration file.

*.STL

%IBERDIR%\EDC\<processor folder>

EDC settlement files.

GCLOG.*

%IBERDIR%\HISTORY

Basic gift certificate sales history.� This is only required if the site is using basic gift certificates (instead of BackOffice Gift Certificates).

All files and subfolders

%IBERDIR%\HTML

Aloha Manager HTML files.� These files are restored if the Aloha application software is reinstalled, unless the HTML folder contains any site-specific files.

PMS.INI

%IBERDIR%\PMS

Property Management System (PMS) configuration file.� This is only required if the site is using the PMS interface.

All files and subfolders

%IBERDIR%\PROFILES

Back-of-House (BOH) user profiles.

All files

%IBERDIR%\RECIPE

FOH recipes.� This is only required if the site is using FOH recipes.

All files

%IBERDIR%\RPTEXPORT

Report export settings.

All files

%IBERDIR%\RPTSET

Report content settings.

IBERSQL.MDB

%IBERDIR%\SQL (or other location where it is stored)

Microsoft Access database.� This is only required if the site is using an Access database.

All files and subfolders

%IBERDIR%\SUM

Summary files.� This is only required if the site is using summary files.

All files

%IBERDIR%\VIZOR

VizorVest^SM configuration

The old file server should be kept on the network for several days until the site is confident all pertinent information has been moved to the new file server.� Perform the following to ensure the FOH terminals do not try to access the old file server:

1.        Change the network name.

2.        Disable all Aloha software applications and services.

3.        Rename the BOOTDRV share.

Relational Database

If you are using a Relational Database (RDB), you must also move the database to the new file server using the export and import functions from the database engine.

BackOffice Data

Refer to document AKBID1180.

Extended Information

No information.

Caveats

This process should occur after the system has completed the EOD process and before new transactions are added to the new DOB.�� Transactions include sales, labor, and FOH configuration changes such as rerouting printers for videos.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1180 Moving BackOffice Data

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1128 reinstall

�

Using the Crystal Reports Interface with an RDB

Using the Crystal Reports Interface with an RDB

============================================================================

AKBID1129

Created: 5 June 2000

Updated: 26 July 2002

Reviewed: 3 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.017 � 5.3.x

Subject: Using the Aloha Application Software Crystal Reports Interface with an Relational Database

============================================================================

Summary

The ALOHA^� application software uses an interface to Seagate Crystal Reports^� to provide customers with customized reporting beyond the Aloha application software's native reports.� The Crystal Reports interface enables customers to view reports created in the Crystal Reports software, but it does not offer any report creation capabilities of its own.

If you are not using a Relational Database (RDB), refer to document AKBID1108.

Information

To access the Crystal Report interface, open Aloha Manager, and select Reports/RDB Crystal Reports.

To add a new report, click 'Add', enter a description in the text box, and click 'Browse' to select the report file.� The report (.RPT) file must reside in the CRW folder.� Select the 'DB Type', add the required report parameters, and click 'OK'.

Refer to document AKBID3030 for the versions of Crystal Reports supported by the Aloha application software.

Report Parameters

Report parameters enable the user to select variables to filter the data, such as the start and end date, a store name, and so on.�

When adding a parameter, users must define four variables:

1.        Sequence � This is the order in which the user is prompted for parameters.

2.        Parameter � Select the parameter type from the drop-down list.� The parameter name must match the parameter name used in the report's design.

3.        Parameter Field Name � This is the name of the parameter as it appears on reports.

4.        Parameter Field Prompt � This is the description of the parameter's prompt that the user sees.

All date prompts use a 'MM/DD/YYYY' format.

Users must manually configure the RDB Crystal Reports (in the CRW folder) that are supplied with the Aloha application software.� Refer to document README2.TXT in the CRW folder for usage and parameter information.

Creating Crystal Reports

The information in this document supplements the Crystal Reports User Manual by explaining Aloha-related information.

When creating Crystal Reports, use an RDB from the same version of the Aloha application software that the site uses to ensure data integrity.� Always select 'Verify on Every Print' from the Database drop-down menu on each report to ensure compatibility.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1030 Grind Database Contents

AKBID1042 Aloha Application Software Database Files

AKBID1081 Summary Process and Files

AKBID1108 Using the Crystal Reports Interface with .DBF Files

AKBID3030 Supported Crystal Report Writer Versions

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1129

�

Remote Aloha Labor Scheduler

Remote Aloha Labor Scheduler

============================================================================

AKBID1130

Created: 19 May 2000

Updated: 5 December 2003

Reviewed: 5 December 2003

Microsoft Windows Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 5.0x � 5.3.x

Subject: Configuring a Remote Copy of Aloha Labor Scheduler

============================================================================

Summary

You can configure the Aloha Labor Scheduler (ALS) application to access a Microsoft^� Windows NT^�, Windows^� 2000, or Windows XP ALOHA^� application software file server from a remote client.� This document explains the configuration requirements for remote ALS.

Although the ALS file server must use the Windows NT, Windows 2000 or Windows XP operating system (OS), the remote ALS client can use the Windows 95, Windows 98, Windows Millennium Edition (Me), Windows NT, Windows 2000, or Windows XP OS.

Information

You must use Aloha versions 5.0x or higher on the file server, and you must have installed the ALS application on the ALS file server using the installation CD for Aloha application software versions 5.0x or higher.

Network

Establish a TCP/IP-based network connection between the remote ALS client and ALS file server.� You can use other network protocols in conjunction with TCP/IP, but you must include TCP/IP.� Refer to document AKBID1063 for more information on TCP/IP.

Remote ALS requires a TCP/IP connection with the ALS file server.

Establish network file access between the remote ALS client and the BOOTDRV share on the ALS file server.� If you did not install ALS in the BOOTDRV share on the file server, ensure the client also has access to the ALS files outside of the BOOTDRV share.

Install Internet Explorer on the ALS File Server

Install Microsoft Internet Explorer 4.01 or higher on the ALS file server.

Set the Data File Location on the ALS File Server

The current ALS data file location setting on the ALS file server uses a drive letter to indicate the� BACKOFFICE\SCHEDULE folder's location on a local hard drive.� Since the remote ALS client requires a Universal-Naming-Convention (UNC) address to access the data on the ALS file server and since the ALS file server can also use the UNC address to access local data, set the data location on the ALS file server to a UNC-based location.� For example, if the current path is D:\ALOHA\BACKOFFICE\SCHEDULE\DATA, the new location may be \\ALOHABOH\BOOTDRV\ALOHA\BACKOFFICE\SCHEDULE\DATA.

Perform the following to edit the ALS data location on the ALS file server:

1.        Open ALS on the ALS server.

2.        Select Edit/Options and select the Miscellaneous tab.

3.        Edit the path in the Data Location text box to reflect the UNC name and click OK.

4.        Restart ALS.

Install DCOM on the ALS File Server

Install and configure Distributed Component Object Model (DCOM) on the ALS file server.�

Refer to document AKBID1049 for more information about installing and configuring DCOM.

Install CESSVR.EXE on the ALS File Server

Install the CESSVR.EXE on the ALS file server by typing the following from a command line (use the correct location of CESSVR.EXE on the ALS file server):

%IBERDIR%\BACKOFFICE\SCHEDULE\CESSVR.EXE /SERVICE

Depending on the version number, you might receive a registration conformation.

Restart the computer.

Configure DCOM on the ALS File Server for Remote Use

Run DCOMCNFG from the Windows SYSTEM32 folder.� Select CES Class or CESSvr from the Applications list, and select Properties.

If CES Class or CESSvr is not listed in the Applications, then you have not successfully registered CESSVR.EXE.� Refer to the 'Install CESSVR.EXE on the ALS File Server' section of the document.

Select the Location tab and select 'Run application on this computer'.� Select the Security tab and use the following information to adjust the application user and group rights to enable remote use:

Remote ALS will not be able to verify the HASP^� security key if remote security permissions are not properly granted.

-          Access permissions control user access to an application after it has been started.� Any user who does not have administrative rights and will be remotely accessing ALS must have access permission.

-          Launch permissions control user access to launch or start an application.� Any user who does not have administrative rights and will be remotely starting ALS must have launch permission.

-          Change permissions control user access to modify the application's DCOM configuration.� Any user who does not have administrative rights and will be modifying the application's DCOM configuration must have change permission.� Change permission should be limited to users who will be supporting the application.

Restart the computer.

Although you can edit access levels using the DCOM Default Security tab, editing access levels using the application's Security tab is safer and more flexible.

Install Internet Explorer on the Remote ALS Client

Install Microsoft Internet Explorer 4.01 or higher on the remote ALS client.

Copy CESSRVC.DLL File to the Remote ALS Client

If the remote ALS client is using the Windows NT, Windows 2000, or Windows XP operating system, copy CESSRVC.DLL from the BACKOFFICE\SCHEDULE folder on the ALS file server to the Windows SYSTEM32 folder on the ALS client.

If the remote ALS client is using the Windows 95, Windows 98, or Windows Me OS, copy CESSRVC.DLL from the BACKOFFICE\SCHEDULE folder on the ALS file server to the Windows SYSTEM folder on the ALS client.

You need to update CESSRVC.DLL on the remote ALS client each time you upgrade the Aloha Application Software.

Install DCOM on the Remote ALS Client

Install and configure Distributed Component Object Model (DCOM) on the remote ALS client.�

Refer to document AKBID1049 for more information about installing and configuring DCOM.

Install and Register System Files on the Remote ALS Client

You must add or update system files in the Windows SYSTEM (Windows 95, Windows 98, or Windows Me) folder or the SYSTEM32 (Windows NT, Windows 2000, or Windows XP) folder on the remote ALS client.� Extract the system files from SYSTEM.ZIP in the ALOHALBR folder on the Aloha Installation CD, and place them in the Windows SYSTEM or SYSTEM32 folder.�

Do not overwrite newer versions of existing files.

Since current copies of the files might be in use by Windows, you cannot overwrite existing files in the Windows SYSTEM or SYSTEM32 folder.� If required, overwrite the files in Windows 95, Windows 98, or Windows Me by restarting to a command prompt and replacing the files.� To overwrite the files in Windows NT, Windows 2000, or Windows XP, download and use SETUPSYS.EXE from the Aloha Technologies FTP site as SETUPSYS.ZIP (refer to document AKBID1012) or use the copy of SETUPSYS.EXE from the \MISC\SETUPSYS folder on the Aloha Installation CD.

Once you have updated the files, open a command prompt, navigate to the Windows SYSTEM or SYSTEM32 folder, and register the system files using the following command lines:

REGSVR32.EXE OLEAUT32.DLL

REGSVR32.EXE OLEPRO32.DLL

REGSVR32.EXE VCF132.OCX

REGSVR32.EXE VSVIEW3.OCX

Install CESSVR.EXE on the Remote ALS Client

Install the CESSVR.EXE on the remote ALS client by typing the following from a command line (use the correct location of CESSVR.EXE on the ALS file server):

\\ALOHABOH\BOOTDRV\ALOHA\BACKOFFICE\SCHEDULE\CESSVR.EXE /REGSERVER

Depending on the version number, you may or may not receive a registration conformation.

Configure DCOM on the Remote ALS Client for Remote Use

If the remote ALS client is using the Windows NT, Windows 2000, or Windows XP OS, run DCOMCNFG from the Windows SYSTEM32 folder.� If the remote ALS client is using the Windows 95, Windows 98, or Windows Me OS, run DCOMCNFG.EXE from the Windows SYSTEM folder.�

Select CES Class or CESSvr from the Applications list, and select Properties.� Select the Location tab, clear 'Run application on this computer,' and select 'Run application on the following computer.' Define the name of the ALS file server in the space provided (for example, ALOHABOH).

If CES Class or CESSvr is not listed in the Applications, then you have not successfully registered CESSVR.EXE.� Refer to the 'Install CESSVR.EXE on the ALS File Server' section of the document.

Restart the computer.

Shortcut to ALS on the Remote ALS Client

Create a new shortcut on the desktop of the remote ALS client using the following command line (use the correct location of ESP.EXE on the ALS file server and the IBERDIR):

\\ALOHABOH\BOOTDRV\ALOHA\BACKOFFICE\SCHEDULE\ESP.EXE /IBERDIR \\ALOHABOH\BOOTDRV\ALOHA

Regardless if the SCHEDULE folder is in the ALOHA folder or not, IBERDIR must point to the Aloha application software folder on the Aloha application software file server.

Edit the new shortcut and set the 'Start In' location to \\ALOHABOH\BOOTDRV\ALOHA\BACKOFFICE\SCHEDULE.

Refer to document AKBID1010 for more information on environment variables.

Extended Information

No information.

Caveats

Although the ALS file server must use the Windows NT, Windows 2000 or Windows XP operating system (OS), the remote ALS client can use the Windows 95, Windows 98, Windows Millennium Edition (Me), Windows NT, Windows 2000 or the Windows XP OS.

You must use Aloha versions 5.0x or higher on the file server, and you must have installed the ALS application on the ALS file server using the installation CD for Aloha application software versions 5.0x or higher.

Remote ALS requires a TCP/IP connection.

You need to update CESSRVC.DLL on the remote ALS client each time you upgrade the Aloha Application Software.

Regardless if the SCHEDULE folder is in the ALOHA folder or not, IBERDIR must point to the ALOHA folder on the Aloha application software file server.

============================================================================

See also:

Aloha Labor Scheduler User Manual

AKBID1010 Aloha Application Software System Environment Variables

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1049 Installing DCOM in Windows

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1130

style='mso-spacerun:yes'>� 2003

�

Using .DBF Files to Create a New RDB Over an Existing RDB

Using .DBF Files to Create a New RDB Over an Existing RDB

============================================================================

AKBID1131

Created: 19 May 2000

Updated: 10 January 2003

Reviewed: 30 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

Subject: Using .DBF File to Create a New RDB Over an Existing RDB

============================================================================

Summary

This document explains how to install new .DBF database files on a file server with an existing relational database (RDB), and the creation of a new relational database (RDB) from the .DBF files.

If you are installing a new .DBF database over an existing database and are not using an RDB, refer to document AKBID1132.

Information

The information below deletes the current RDB file, including all previous sales.

Installing a new database on a system with sales data from previous days (dated folders) may result in inaccurate reports for data created with the previous database.

Stop or shut down all Aloha software applications and services and perform the following steps in the order that they appear.

Delete Current RDB

The information below deletes the current RDB file, including all current and historical sale data.

Delete the 'IberSQL' database using the database software (for example, Microsoft SQL Server Enterprise Manager).�

If you are using Microsoft Database Engine (MSDE), you can install a third-party database management application in order to delete the database.� Otherwise, you have to uninstall MSDE, delete the IberSQL database on the file level, and reinstall the Aloha application software using the Aloha Installation CD (ensure that you enable MSDE and select the option to use custom data).

Copy the New .DBF Files to NEWDATA

Perform the following to copy the .DBF files from the new menu to the NEWDATA folder and update them:

1.        Copy the new database to the NEWDATA folder, overwriting the existing database files.

2.        Start DBCONFIG.EXE from the BIN folder.

3.        Select only the following to update the .DBF files in the NEWDATA folder:

-          DBF Files Only

-          Attended

-          Debug

-          Force Upgrade

4.        Verify the IBERDIR description, and point the Input and Output text boxes to the NEWDATA folder.�

5.        Click Run.

Update the .CDX Files in NEWDATA

If you are using versions 5.239 and lower, perform the following to update the index (.CDX) files in the NEWDATA folder (this step is not required in versions 5.2.4.0 and higher since the 'DBF Files Only' option in the previous step will have already updated the .CDX files):

1.        Start DBCONFIG.EXE from the BIN folder.

2.        Select only the following to update the .CDX files in the NEWDATA folder:

-          Attended

-          Debug

-          Upgrade DBF Index Files

3.        Verify the IBERDIR description, and point the Input and Output text boxes to the NEWDATA folder.�

4.        Click Run.

Create the RDB

Perform the following to create a new RDB based on the .DBF files in the NEWDATA folder:

1.        Start DBCONFIG.EXE from the BIN folder.

2.        Select only the following to update the create the RDB:

-          Create RDB

-          Attended

-          Debug

-          Relational Database Only

3.        Verify the IBERDIR description, and point the Input and Output text boxes to the NEWDATA folder.�

4.        Click Run.

This process may display an error stating a warning about database inconsistencies and a list of the problems encountered.� You can choose to proceed with the inconsistencies or fix them and start the process over.�

Recreate the .DBF Files From the RDB

To ensure the .DBF files in the NEWDATA folder match the RDB data, perform the following to recreate the .DBF and .CDX files in the NEWDATA folder:

1.        Start DBCONFIG.EXE from the BIN folder.

2.        Select only the following to recreate the .DBF files from the RDB:

-          Create DBF Files

-          Attended

-          Debug

3.        Verify the IBERDIR description, and point the Input and Output text boxes to the NEWDATA folder.�

4.        Click Run.

Some versions of DBCONFIG.EXE do not display the 'Create DBF Files' option.� In this case, open a command prompt and use the following command line to perform this function:

%IBERDIR%\BIN\DBUP2.EXE /ATTENDED /DEBUG /DBFOUTPUT %IBERDIR%\NEWDATA /CREATEDBF

Update the .DBF Files in the DATA Folder

Perform the following to update the .DBF files in the DATA folder using the .DBF files in the NEWDATA folder:

1.        Start DBCONFIG.EXE from the BIN folder.

2.        Select only the following to update the .DBF files in the DATA folder:

-          DBF Files Only

-          Attended

-          Debug

3.        Verify the IBERDIR description, and point the Input text box to the NEWDATA folder and the Output text box to the DATA folder.�

4.        Click Run.

Update the .CDX files in the DATA Folder

If you are using versions 5.239 and lower, perform the following to update the index (.CDX) files in the DATA folder (this step is not required in versions 5.2.4.0 and higher since the 'DBF Files Only' option in the previous step will have already updated the .CDX files):

1.        Start DBCONFIG.EXE from the BIN folder.

2.        Select only the following to update the .CDX files in the DATA folder:

-          Attended

-          Debug

-          Upgrade DBF Index Files

3.        Verify the IBERDIR description, and point the Input and Output text boxes to the DATA folder.

4.        Click Run.

Restart the Aloha Application Software

Restart the Aloha application software Aloha software applications and services.

Extended Information

You can automate this process (with the exception of deleting the RDB) using a batch file similar to the following with the appropriate version of DBUP.EXE (refer to document AKBID1067):

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

ECHO Y | COPY C:\DATABASE\*.* %IBERDIR%\NEWDATA

START /WAIT %IBERDIR%\BIN\DBUP3.EXE /DBFONLY /DEBUG /FORCEUPGRADE /DBFINPUT %IBERDIR%\NEWDATA /DBFOUTPUT %IBERDIR%\NEWDATA

START /WAIT %IBERDIR%\BIN\DBUP3.EXE /CDX /DEBUG /DBFINPUT %IBERDIR%\NEWDATA /DBFOUTPUT %IBERDIR%\NEWDATA

START /WAIT %IBERDIR%\BIN\DBUP3.EXE /CREATEDB /DBONLY /DEBUG /DBFINPUT %IBERDIR%\NEWDATA /DBFOUTPUT %IBERDIR%\NEWDATA

START /WAIT %IBERDIR%\BIN\DBUP3.EXE /CREATEDBF /DEBUG /DBFINPUT %IBERDIR%\NEWDATA /DBFOUTPUT %IBERDIR%\NEWDATA

START /WAIT %IBERDIR%\BIN\DBUP3.EXE /DBFONLY /DEBUG /FORCEUPGRADE /DBFINPUT %IBERDIR%\NEWDATA /DBFOUTPUT %IBERDIR%\DATA

START /WAIT %IBERDIR%\BIN\DBUP3.EXE /CDX /DEBUG /DBFINPUT %IBERDIR%\DATA /DBFOUTPUT %IBERDIR%\DATA

Caveats

Some information and commands in this document can result in deletion the current RDB file, including all previous sales.

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

============================================================================

See also:

Aloha QuickService or TableService User Manual

Database and Aloha POS Manual

AKBID1067 DBUP.EXE and DBCONFIG.EXE

AKBID1110 Installing Microsoft SQL Server 7.0

AKBID1129 Installing Microsoft Access 2000

AKBID1132 Installing a New .DBF Database Over an Existing Database

AKBID1202 Installing Microsoft SQL Server 2000

AKBID3109 Re-synchronizing DBF Files From an RDB

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1131 supersite

�

Installing a New .DBF Database Over an Existing Database

Installing a New .DBF Database Over an Existing Database

============================================================================

AKBID1132

Created: 25 May 2000

Updated: 10 January 2003

Reviewed: 30 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

Subject: Installing a New .DBF Database Over an Existing Database

============================================================================

Summary

This document explains how to install new .DBF database files on a file server with an existing .DBF database.

If you are installing a new .DBF database on a system with a relational database (RDB), refer to document AKBID1131.

Information

Installing a new database on a system with sales data from previous days (dated folders) may result in inaccurate reports for data created with the previous database.

Stop or shut down all Aloha software applications and services and perform the following steps in the order that they appear.

Copy the New .DBF Files to NEWDATA

Perform the following to copy the .DBF files from the new menu to the NEWDATA folder and update them:

1.        Copy the new database to the NEWDATA folder, overwriting the existing database files.

2.        Start DBCONFIG.EXE from the BIN folder.

3.        Select only the following to update the .DBF files in the NEWDATA folder:

-          DBF Files Only

-          Attended

-          Debug

-          Force Upgrade

4.        Verify the IBERDIR description, and point the Input and Output text boxes to the NEWDATA folder.�

5.        Click Run.

Update the .CDX Files in NEWDATA

If you are using versions 5.239 and lower, perform the following to update the index (.CDX) files in the NEWDATA folder (this step is not required in versions 5.2.4.0 and higher since the 'DBF Files Only' option in the previous step will have already updated the .CDX files):

1.        Start DBCONFIG.EXE from the BIN folder.

2.        Select only the following to update the .CDX files in the NEWDATA folder:

-          Attended

-          Debug

-          Upgrade DBF Index Files

3.        Verify the IBERDIR description, and point the Input and Output text boxes to the NEWDATA folder.�

4.        Click Run.

Update the .DBF Files in the DATA Folder

Perform the following to update the .DBF files in the DATA folder using the .DBF files in the NEWDATA folder:

1.        Start DBCONFIG.EXE from the BIN folder.

2.        Select only the following to update the .DBF files in the DATA folder:

-          DBF Files Only

-          Attended

-          Debug

-          Force Upgrade

3.        Verify the IBERDIR description, and point the Input text box to the NEWDATA folder and the Output text box to the DATA folder.�

4.        Click Run.

Update the .CDX files in the DATA Folder

If you are using versions 5.239 and lower, perform the following to update the index (.CDX) files in the DATA folder (this step is not required in versions 5.2.4.0 and higher since the 'DBF Files Only' option in the previous step will have already updated the .CDX files):

1.        Start DBCONFIG.EXE from the BIN folder.

2.        Select only the following to update the .CDX files in the DATA folder:

-          Attended

-          Debug

-          Upgrade DBF Index Files

3.        Verify the IBERDIR description, and point the Input and Output text boxes to the DATA folder.

4.        Click Run.

Restart the Aloha Application Software

Restart the Aloha application software Aloha software applications and services.

Extended Information

You can automate this process using a batch file similar to the following with the appropriate version of DBUP.EXE (refer to document AKBID1067):

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

ECHO Y | COPY C:\DATABASE\*.* %IBERDIR%\NEWDATA

START /WAIT %IBERDIR%\BIN\DBUP3.EXE /DBFONLY /DEBUG /FORCEUPGRADE /DBFINPUT %IBERDIR%\NEWDATA /DBFOUTPUT %IBERDIR%\NEWDATA

START /WAIT %IBERDIR%\BIN\DBUP3.EXE /CDX /DEBUG /DBFINPUT %IBERDIR%\NEWDATA /DBFOUTPUT %IBERDIR%\NEWDATA

START /WAIT %IBERDIR%\BIN\DBUP3.EXE /DBFONLY /DEBUG /FORCEUPGRADE /DBFINPUT %IBERDIR%\NEWDATA /DBFOUTPUT %IBERDIR%\DATA

START /WAIT %IBERDIR%\BIN\DBUP3.EXE /CDX /DEBUG /DBFINPUT %IBERDIR%\DATA /DBFOUTPUT %IBERDIR%\DATA

Caveats

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1067 DBUP.EXE and DBCONFIG.EXE

AKBID1131 Using .DBF Files to Create a New RDB Over an Existing RDB

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1132 menu

�

SuperSite Dated Folders

SuperSite Dated Folders

============================================================================

AKBID1133

Created: 26 May 2000

Updated: 2 January 2002

Reviewed: 5 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

Subject: Maintaining SuperSite Dated Folders

============================================================================

Summary

ALOHA^� application software SuperSites store dated folders on the Front-of-House (FOH) terminals rather than the Back-of-House (BOH) SuperSite file server.� Users must understand this behavior to properly support a SuperSite.

Information

Each store in a SuperSite has a FOH terminal that acts as a file server for the store.� The End-of-Day (EOD) process (refer to document AKBID1015) creates a dated folder on the store's file server instead of the SuperSite file server.� Since the store's file server may roam to other FOH terminals within the same store, dated folders may exist on multiple terminals in a store.

Regardless of the terminal they are on, dated folders use the same file and folder structure as a regular site.� The dated folder resides in the Aloha POS folder, and it is labeled in regards to the Date-of-Business (DOB) using the yyyymmdd format.

As with regular sites, SuperSites use the DONE30 file to signal the completion of the EOD process.

Dated Folder Usage

Although the Grind process (refer to document AKBID1016) transfers sales information from the dated folders to the relational database (RDB) on the SuperSite file server, the dated folders are still required to reprint checks and checkouts or to print audit reports.

Hard Drive Space and Archiving

Unlike most BOH file servers, FOH SuperSite terminals that function as store file servers do not typically have large amounts of hard drive space.� This means dated folders can consume a hard drive's available space quicker than they do on a typical BOH file server's hard drive.� Furthermore, since the terminal is not occupied by a user with a keyboard and mouse like a BOH file server typically is, low hard drive space is rarely noticed until it effects the Aloha application software.

It is very important that SuperSites administrate the dated folders and develop a purging and archiving scheme to combat hard drive space problems.� Just like a normal BOH file server, users should employ several dated folders to determine the average daily hard drive space usage and organize a scheme based on this information.

Since dated folders are required to reprint checks and checkouts or to print audit reports, you should leave dated folder on the FOH terminals as long as hard drive space allows.� When you remove them, archive them elsewhere in case you must restore them to perform reporting or to regrind them in case of a catastrophe.

You can configure automatic purging of dated folders in Aloha Manager/SQL Settings/Settings.� This functionality permanently deletes any dated folders found on FOH terminals that exceeded the set number of days.� You can configure the FOHHOOK.BAT (refer to document AKBID1171) to automatically archive or copy the dated folders to the SuperSite file server.

Extended Information

If you have a large SuperSite using QuickService, your button database file (BTN.DBF) can become quite large in size.� Configuring FOHHOOK.BAT (refer to document AKBID1171) to delete the BTN.DBF from the store's dated folder each night can help preserve disk space.

Caveats

No information.

============================================================================

See also:

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1015 EOD Process and Errors

AKBID1016 Grind Process and Errors

AKBID1171 FOHHOOK.BAT

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1133 subdir subdirs

�

Debouts

Debouts

============================================================================

AKBID1134

Created: 31 May 2000

Updated: 8 August 2003

Reviewed: 20 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 5.0x � 5.3.x

Subject: An Overview of Aloha Application Software Debugging Files

============================================================================

Summary

The ALOHA^� application software uses debugging-output-files (debouts) to assist in troubleshooting problems related to the system.� Virtually every Aloha process writes information to debugging files, and technicians are required to understand the location and content of these files to support the Aloha application software.� This document explains what debouts are available, and their purging capabilities.

Information

BOH Debout Names and Locations

The following debouts created by Back-of-House (BOH) applications, and they are stored in the file server's TMP folder:

Name

Description

DB_ERROR.Gnn

Supplements the Grind debouts when using an RDB.

DEBOUT.DFF

DBFDIFF.EXE debugging information (refer to document AKBID3084)

DEBOUT.EDC

EDC and PMS debugging information.

DEBOUT.Gnn

Grind process debugging information (The BOH uses the store number in the file name.� It defaults to 01, but SuperSites have separate Grind debouts for each store.)

DEBOUT.KEY

KEYRENUM.EXE debugging information (refer to document AKBID1012)

DEBOUT.PR

PAYRECON.EXE (Payment Reconciliation) debugging information.

DEBOUT.Rnn

Regrind process debugging information (The BOH uses the store number in the file name.� It defaults to 01, but SuperSites have separate Regrind debouts for each store.)

DEBOUT.SVR

CTLSVR.EXE (Control Server) debugging information

DEBOUT.TXT

Debugging information for Aloha Manager, associated .DLL, and all other BOH applications not specified in other debout files

SQL_ERR.TXT

While not labeled as a debout file, it contain information regarding an SQL database.

In some cases, BOH debouts may appear in the TMP folder on a Front-of-House (FOH) terminal.� Ignore these files since they may be out of date.� Always use the BOH debout files from the file server.

FOH Debout Names and Locations

Each FOH terminal writes debugging information to a debout file in the local TMP folder that is specific to the terminal.� The FOH debouts are labeled using the terminal's ID number.� For example, terminal one writes to DEBOUT.01, terminal two writes to DEBOUT.02, and so on.

In some cases, FOH debouts may appear in the TMP folder on the file server, or a FOH terminal may contain a debout from other terminal.� Ignore these files since they may be out of date.� Always use the FOH debout file from the terminal it is specific to.

The Master terminal creates a DEBOUT.EOD file with debugging information from the End-of-Day (EOD) process.� The DEBOUT.EOD file is overwritten each time the EOD process starts.� The information in DEBOUT.EOD is also stored in the Master terminals debout (DEBOUT.nnn).� Refer to document AKBID1015.

Aloha Spy writes debugging information to DEBOUT.SPY in the local terminal's TMP folder.

FISCALMGR.EXE (Fiscal Manager) writes debugging information to DEBOUT.FPM in the local terminal's TMP folder.

Payment Reconciliation writes debugging information to DEBOUT.PR in the local terminal's TMP folder.

Setup Application Debouts

SETUPPOS.EXE and SETUPTRM.EXE write debugging information to C:\DEBOUT.SET.

Purging Debouts

IBER.EXE and IBERQS.EXE purge debouts by renaming them during the EOD process every Tuesday night (using the Date-of-Business, or DOB).� All debouts are renamed from DEBOUT.* to DEBBAK.* after any previous DEBBAK.* files are deleted.� This applies to the debouts on FOH terminals and, if you are using the file server to run both the FOH and BOH on the same computer, the debouts on the file server.� For example, DEBOUT.TXT is renamed to DEBBAK.TXT, and DEBOUT.01 is renamed to DEBBAK.01.

If you are not running the FOH on your file server, then CTLSVR.EXE (Control Server) controls BOH debout purging.� (The FOH debouts are still purged on the FOH terminals by IBER.EXE and IBERQS.EXE, as explained previously in this document.) Control Server uses the MAXDEBOUTSIZE and MAXDEBOUTDAYS system environment variables to control BOH debout purging.

MAXDEBOUTSIZE renames the debouts to DEBBAK files when they reach a set size.� If you do not set the MAXDEBOUTSIZE variable in the system environment variables, it defaults to 8000000 (eight megabytes).� When a debout's size exceeds the limit, Control Server renames the debout to DEBBAK2.*.� For example, DEBOUT.TXT is renamed to DEBBAK2.TXT, and DEBOUT.G01 is renamed to DEBBAK2.G01.� If DEBBAK2.* already exists, then the files are renamed DEBBAK3.* and so on.

MAXDEBOUTDAYS deletes any DEBBAK files (created because of the MAXDEBOUTSIZE variable) that are older than a set number of days.� If you do not set the MAXDEBOUTDAYS variable in the system environment variables, then it defaults to 30 (days).�

Searching Debouts for Trouble

The information in the debouts appears overwhelming at first glance, but the following tips may help:

-          When searching the debouts for errors, look for words like 'error', 'warning', 'fail', or 'fatal'.� This helps you concentrate on information regarding the problem.

-          If the site is experiencing network problems, use the NetBIOS error codes explained in document AKBID1099 to decipher the information supplied in the debouts.� Understanding how the Aloha application software uses NetBIOS (as described in document AKBID1075) greatly enhances the user's understanding of debouts.

-          If the site is experiencing problems during the EOD process, refer to document AKBID1015 to decipher the checkpoints listed in the debouts.

-          Debouts often use identification numbers when referring to a database.� Use document AKBID1042 to match the identification numbers to the database.

-          Using the DEBUG flag (refer to document AKBID1010) to create extended information in the debouts.�

Extended Information

Bracketed Numbers

Some debouts include a string of numbers contained within brackets (for example, [123456789]) at the beginning of each line. The strings refer to the thread ID, which is used to distinguish which thread of a multi-threaded application is writing the information to the debout.

Caveats

In some cases, BOH debouts may appear in the TMP folder on a FOH terminal.� Ignore these files since they may be out of date.� Always use the BOH debout files from the file server.

In some cases, FOH debouts may appear in the TMP folder on the file server, or a FOH terminal may contain a debout from other terminal.� Ignore these files since they may be out of date.� Always use the FOH debout file from the terminal it is specific to.

============================================================================

See also:

AKBID1010 Aloha Application Software System Environment Variables

AKBID1011 Windows 9x VNETBIOS.VXD Patch

AKBID1015 EOD Process and Errors

AKBID1016 Grind Process and Errors

AKBID1020 EDC Process

AKBID1042 Aloha Application Software Database Files

AKBID1075 NetBIOS and the Aloha Application Software

AKBID1099 Network Troubleshooting

AKBID1139 Serial Port Error Return Codes

AKBID3051 COM Port Error -1

AKBID3052 COM Port Error -3

AKBID3084 DBFDIFF.EXE

AKBID3095 Network Name Unexpectedly De-Registered

AKBID3096 Synchronization of Data Fails

AKBID3097 Filed to Read Error Code

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1134 debout.set

�

Using E-Messenger and Corporate Gift Certificates

Using E-Messenger and Corporate Gift Certificates

============================================================================

AKBID1135

Created: 30 May 2000

Updated: 22 January 2003

Reviewed: 24 February 2004

Microsoft Windows Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

Subject: Using Enterprise Messenger and Corporate Gift Certificates

============================================================================

Summary

The ALOHA^� application software uses Enterprise Messenger (E-Messenger) to transfer and consolidate Aloha Gift Certificate Manager sales and inventory information between stores and a corporate office.� The process uses Microsoft^� Windows^� Messaging Application Programming Interface (MAPI) compliant clients.� MAPI compliant clients include Microsoft Windows Messaging, Microsoft Outlook^� 97 or higher (configured as a 'Corporate or Workgroup' installation), and Microsoft Exchange Client 5.0 or higher.� Outlook Express is not MAPI compliant.� This document explains using E-Messenger to send gift certificate information from a store to a corporate office and back.

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

If you are using a Wide-Area-Network (WAN) to send gift certificates between a store and corporate office, refer to document AKBID1034.� If you are using E-Messenger to send Aloha application software sales information (dated folders) between a store and corporate office, refer to document AKBID1061.

Information

The 'Corporate Gift Certificate' process uses 10 steps (divided into three stages):

Stage One:

1.        Each store exports gift certificate information to the C:\GCEXPORT folder.

2.        Each store purges any 'purgable' gift certificate information.

3.        Each store creates a gift certificate information files to send to the corporate office.

4.        Each store sends the files to the corporate office using E-Messenger.

Stage Two:

5.        The corporate office receives and processes the packages from the stores.

6.        The corporate office imports and processes the gift certificate information from the stores.

7.        The corporate office exports the updated gift certificate information to send back to each store.

8.        The corporate office sends the updated gift certificate information back to each store.

Stage Three:

9.        Each store receives and processes the package from the corporate office.

10.     Each store imports the new gift certificate information from the corporate office.

It is important to stagger the times of each stage in the process.� For example, set stage one to start at 3:00 a.m., stage two at 4:00 a.m., and stage three at 5:00 a.m.� This leaves an hour buffer between each stage for processing time.

Transferring gift certificate data from a store to a corporate office requires the MAPI client and E-Messenger installed and configured at each store and the corporate office.� You must install the MAPI client before installing E-Messenger.

Configure the MAPI Client at the Corporate Office

Setup an Internet email account with a local Internet access provider, and configure the MAPI client.� If you are using Microsoft Exchange as your MAPI client, double-clicking the Inbox icon on the Microsoft Windows desktop generally starts an installation wizard that guides you through the installation process.�

In order to automate the sending process, the MAPI client must be configured to send and receive mail without requiring any external intervention other than the initial operation to start the send-and-receive-email process.� For example, if the user opens Microsoft Exchange and selects Tools/Deliver Now, Microsoft Exchange must complete the send-and-receive-email process without further intervention.

Consult Microsoft documentation for more information on configuring MAPI clients.

Install E-Messenger at the Corporate Office

Install E-Messenger from the Aloha Installation CD, and configure the BackOffice License Manager with the correct user information.

This document is based on E-Messenger version 1.03 SP3.� After installing E-Messenger, ensure version compliance with this document.

Refer to the Aloha Enterprise Messenger User Manual for more information on configuring E-Messenger.

Windows NT^� and Windows 2000 assign different MAPI client profiles to each user that logs in.� Ensure you are executing E-Messenger in the context of the correct user.

Install Aloha Gift Certificate Manager at the Corporate Office

Install Gift Certificate Manager from the Aloha Installation CD, and configure the BackOffice License Manager with the correct user information.�

This document is based on Gift Certificate Manager version 3.03 SP4 or higher.� After installing Gift Certificate Manager, ensure version compliance with this document.

You must select the 'Corporate Office' option when installing Gift Certificate Manager.

Set the Export and Import Gift Certificates Location at the Corporate Office

Designate folders to import and export gift certificate information.� For example, create C:\GCIMPORT and C:\GCEXPORT folders on the file server.�

Open the Aloha BackOffice Main Menu and select Gift Certificate Manager.� Select 'Gift Certificate Import' from the operations menu, and select Options/Program Setup.� Add C:\GCIMPORT to the 'Directory Name' text box.�

Open the Aloha BackOffice Main Menu and select Gift Certificate Manager.� Select 'Gift Certificate Export' from the operations menu, and select Options/Program Setup.� Select 'Enterprise Messaging' as the transport method, add C:\GCEXPORT to the 'Local Export Path' text box, and set 'Remote Import Path' to $GCIMPORT$.

If the 'Gift Certificate Import' and 'Gift Certificate Export' option do not appear in the Operations menu, reinstall the Gift Certificate Manager application and select 'Corporate Office'.

Configure $GCIMPORT$ at the Corporate Office

GCIMPORT is a macro created in E-Messenger.� The macro specifies the folder on the corporate office computer to process the received files.� The dollar signs ($) on each side of the label define it as a macro in command lines.

Perform the following to create a macro at the corporate office to define the target folder:

1.        Open E-Messenger.

2.        Select File/Macro Definitions.

3.        Click 'Add Macro'.

4.        Name the macro 'GCIMPORT' and give the macro a path of C:\GCIMPORT.

5.        Click 'OK'.

When packages are sent from the stores, E-Messenger at the corporate office replaces '$GCIMPORT$' with 'C:\GCIMPORT' when processing the package.

'GCIMPORT' is not a required label for the macro.� Users can specify different names as long as the packages from the stores also refer to the different name.

Configure the SU.EXE Utility at the Corporate Office

Users of Windows NT and Windows 2000 must use the SU.EXE for E-Messenger to send and receive email from a command line, such as a .BAT or a .CMD file.

As stated previously in this document, Windows NT and Windows 2000 assign different MAPI client profiles to each user.� Tasks executed from a command line (like .CMD batch file) use the built-in Windows system account, which does not have a profile defined for the MAPI client, and therefore, will not function properly.

Perform the following to install the SU.EXE utility:

1.        Download SU.ZIP from the Aloha Technologies FTP site.

2.        Copy SU.EXE and SUSS.EXE to the Windows folder.

3.        Open a command prompt and navigate to the Windows folder.

4.        Run 'SUSS.EXE �INSTALL'.

This installs SU.EXE on the file server.� The correct user account and password is defined in the Winhook batch file.

Setup Store Email Addresses at the Corporate Office

E-Messenger at the corporate office requires a list of the store email addresses to send the updated gift certificate information.� Perform the following to add the email addresses:

1.        Open E-Messenger.

2.        Select File/Setup, and click 'Edit'.

3.        Enter the password, and click 'OK'.

4.        Select 'Corporate' in the Local Settings.

5.        Add the email addresses for each store (separated by semicolons) in the 'Send Packages To' text box.

6.        Click 'OK'.

You must edit this email list as new stores are added or removed.

Refer to the Aloha Enterprise Messenger User Manual for more information on configuring E-Messenger

Create EMSG.CMD to Retrieve and Process Store Packages at the Corporate Office

After each store has sent the gift certificate packages, the corporate office must use a .CMD file to retrieve the emails, process the information in them, and send the updated gift certificate information to the stores.�

If you are using Windows 95, Windows 98, or Windows Me, configure Task Scheduler to launch the .CMD file.� If you are using Windows NT or Windows 2000, configure Windows Schedule Service (refer to document AKBID1047) to launch the .CMD file.

Create EMSG.CMD in the Windows folder, and add the following information to EMSG.CMD:

If the E-Messenger software is already active, the batch file will not be able to automatically send the files to the corporate office.� To ensure that E-Messenger is not already active, use the CLOSEAPP.EXE utility (refer to document AKBID1012) in the batch file to close E-Messenger before trying to send the files.� You may also want to use this after the package has been sent to shut down E-Messenger.

�� CLOSEAPP.EXE /CLOSE ENTERPRISE

Navigate to the BackOffice folder.� In this example, the BackOffice folder is in the D:\ALOHA\BACKOFFICE folder.

D:

CD\ALOHA\BACKOFFICE

Initialize E-Messenger to retrieve and process the information from the stores (Windows 95, Windows 98, or Windows Me only).

"D:\ALOHA\BACKOFFICE\EMESSENGER.EXE" /AUTO

Set the SU.EXE command line that initializes E-Messenger to retrieve and process the files from the stores (Windows NT and Windows 2000 only).

SET SU_COMMANDLINE="D:\ALOHA\BACKOFFICE\EMESSENGER.EXE" /AUTO

Run SU.EXE to initialize E-Messenger.� In this example, the user name is 'aloha' and the password is 'hello'.� Edit this command line to use the user name and password that matches the profile previously set up in E-Messenger (Windows NT and Windows 2000 only).

This command line creates a potential security risk since it exposes the user name and password.� If this is not acceptable, consult SU.TXT (from SU.ZIP) for more password options.

ECHO hello| SU.EXE aloha

Import the gift certificate information from the stores.

START /WAIT D:\ALOHA\BACKOFFICE\GC\GCIMPORT.EXE /AUTO

Export the new gift certificate information.

START /WAIT D:\ALOHA\BACKOFFICE\GC\GCEXPORT.EXE /AUTO

Verify if the gift certificate export file exists in C:\GCEXPORT.� If it does not, skip to EXIT.

IF NOT EXIST C:\GCEXPORT\*.GCX GOTO :EXIT

If the E-Messenger software is already active, the batch file will not be able to automatically send the files to the corporate office.� To ensure that E-Messenger is not already active, use the CLOSEAPP.EXE utility (refer to document AKBID1012) in the batch file to close E-Messenger before trying to send the files.� You may also want to use this after the package has been sent to shut down E-Messenger.

�� CLOSEAPP.EXE /CLOSE ENTERPRISE

Initialize E-Messenger to process and send the files to the stores (Windows 95, Windows 98, and Windows Me only).

"D:\ALOHA\BACKOFFICE\EMESSENGER.EXE" /AUTO

Set the SU.EXE command line that initializes E-Messenger to process and send the files to the stores (Windows NT and Windows 2000 only).

SET SU_COMMANDLINE="D:\ALOHA\BACKOFFICE\EMESSENGER.EXE" /AUTO

Run SU.EXE to initialize E-Messenger.� In this example, the user name is 'aloha' and the password is 'hello'.� Edit this command line to use the user name and password that matches the profile previously set up in E-Messenger (Windows NT and Windows 2000 only).

This command line creates a potential security risk since it exposes the user name and password.� If this is not acceptable, consult SU.TXT (from SU.ZIP) for more password options.

ECHO hello| SU.EXE aloha

Finished.

EXIT

Configure the MAPI Client at the Store

Setup an Internet email account with a local Internet access provider, and configure the MAPI client.� If you are using Microsoft Exchange as your MAPI client, double-clicking the Inbox icon on the Microsoft Windows desktop generally starts an installation wizard that guides you through the installation process.�

In order to automate the sending process, the MAPI client must be configured to send and receive mail without requiring any external intervention other than the initial operation to start the send-and-receive-email process.� For example, if the user opens Microsoft Exchange and selects Tools/Deliver Now, Microsoft Exchange must complete the send-and-receive-email process without further intervention.

Consult Microsoft documentation for more information on configuring MAPI clients.

Install E-Messenger at the Store

Install E-Messenger from the Aloha Installation CD, and configure the BackOffice License Manager with the correct user information.

This document is based on E-Messenger version 1.03 SP3.� After installing E-Messenger, ensure version compliance with this document.

After the installation is complete, open E-Messenger and select File/Setup, and enter the password.� Add the store ID to the 'Store ID' text box, and add the corporate office email address to send sales data to in the 'Send Packages To' text box.� Verify the email profile information to ensure it is correct.

Refer to the Aloha Enterprise Messenger User Manual for more information on configuring E-Messenger.

Windows NT and Windows 2000 assign different MAPI client profiles to each user that logs in.� Ensure you are executing E-Messenger in the context of the correct user.

Configure the SU.EXE Utility at the Store

Users of Windows NT and Windows 2000 must use the SU.EXE for E-Messenger to send and receive email from a command line, such as a .CMD batch file used by Windows Schedule Service.

As stated previously in this document, Windows NT and Windows 2000 assign different MAPI client profiles to each user.� Tasks executed from a command line (like .CMD batch file) use the built-in Windows system account, which does not have a profile defined for the MAPI client, and therefore, will not function properly.

Use the SU.EXE utility, developed by Microsoft, as a work-around for this, and it must be installed on all Windows NT and Windows 2000 file servers using E-Messenger.

Perform the following to install the SU.EXE utility:

1.        Download SU.ZIP from the Aloha Technologies FTP site.

2.        Copy SU.EXE and SUSS.EXE to the Windows folder.

3.        Open a command prompt and navigate to the Windows folder.

4.        Run 'SUSS.EXE �INSTALL'.

This installs SU.EXE on the file server.� The correct user account and password is defined later in the Winhook batch file.

Install Aloha Gift Certificate Manager at the Store

Install Gift Certificate Manager from the Aloha Installation CD, and configure the BackOffice License Manager with the correct user information.�

This document is based on Gift Certificate Manager version 3.03 SP4 or higher.� After installing Gift Certificate Manager, ensure version compliance with this document.

You must select the 'Corporate Store' option when installing Gift Certificate Manager.

If you do not install the demonstration database or a database from the corporate office with the store already configured in it, you will receive an error at the store stating 'Unable to Initialize GC Server' or 'Unable to Initialize the Gift Certificate services.� Can't continue' when starting the Aloha interface.

Set the Export and Import Gift Certificates Location at the Store

Designate folders to import and export gift certificate information.� For example, create C:\GCIMPORT and C:\GCEXPORT folders on the file server.�

Open the Aloha BackOffice Main Menu and select Gift Certificate Manager.� Select 'Gift Certificate Import' from the operations menu, and select Options/Program Setup.� Add C:\GCIMPORT to the 'Directory Name' text box.�

Open the Aloha BackOffice Main Menu and select Gift Certificate Manager.� Select 'Gift Certificate Export' from the operations menu, and select Options/Program Setup.� Select 'Enterprise Messaging' as the transport method, add C:\GCEXPORT to the 'Local Export Path' text box, and set 'Remote Import Path' to $GCIMPORT$.�

If the 'Gift Certificate Import' and 'Gift Certificate Export' option do not appear in the Operations menu, reinstall the Gift Certificate Manager application and select 'Corporate Store'.

Configure $GCIMPORT$ at the Store

GCIMPORT is a macro created in E-Messenger.� The macro specifies the folder on the store file server to process the received files.� The dollar signs ($) on each side of the label define it as a macro in command lines.

Perform the following to create a macro at the corporate office to define the target folder:

Open E-Messenger.

Select File/Macro Definitions.

Click 'Add Macro'.

Name the macro 'GCIMPORT' and give the macro a path of C:\GCIMPORT.

Click 'OK'.

When packages are sent from the corporate office, E-Messenger at the stores replaces '$GCIMPORT$' with 'C:\GCIMPORT' when processing the package.

'GCIMPORT' is not a required label for the macro.� Users can specify different names as long as the packages from the stores also refer to the different name.

Configure AutoRun at the Store

To configure BackOffice to process and send the gift certificate information to the corporate office each night, select AutoRun from the Operations menu in the Gift Certificate Manager, and add the following programs:

Since the paths listed below are based on the %IBERDIR%\BACKOFFICE folder as the root folder instead of the actual root drive folder, the Browse button is not compatible and should not be used.

Field

Information

Title

Gift Certificate Export

Command Line

GC\GCEXPORT.EXE AUTO

Working Directory

%IBERDIR%\BACKOFFICE

Wait For Programs To Finish�

Yes

Field

Information

Title

Gift Certificate Purge

Command Line

GC\GCPURGE.EXE AUTO

Working Directory

%IBERDIR%\BACKOFFICE

Wait For Programs To Finish�

Yes

Field

Information

Title

Run CLOSEAPP.EXE.� If the E-Messenger software is already active, the batch file will not be able to automatically send the files to the corporate office.� To ensure that E-Messenger is not already active, use the CLOSEAPP.EXE utility (refer to document AKBID1012) in the batch file to close E-Messenger before trying to send the files.� You may also want to use this after the package has been sent to shut down E-Messenger.

Command Line

"<location of CLOSEAPP.EXE>\CLOSEAPP.EXE /CLOSE ENTERPRISE"

Working Directory

<location of CLOSEAPP.EXE>

Wait For Programs To Finish�

Yes

Field

Information

Title

Launch E-Messenger

Command Line

"ENTERPRISE MESSAGING\EMESSENGER.EXE" AUTO

Working Directory

%IBERDIR%\BACKOFFICE

Wait For Programs To Finish�

Yes

AutoRun must launch these applications in the correct order to function properly.

1.        Gift Certificate Export

2.        Gift Certificate Purge

3.        Run Email Package Creation File

4.        Run CLOSEAPP.EXE Utility

5.        Launch E-Messenger

Perform the following to set the time for AutoRun to start:

1.        Open the Aloha Interface.

2.        Select File/Setup/General.

3.        Set the time in the 'At Business Date Roll Time Of' text box.

4.        Select 'Execute AutoRun Program'.

5.        Click 'OK'.�

Since AutoRun requires the BackOffice Interface to be active, AutoRun may not be compatible with some restaurants, so if you are using Windows 95, Windows 98, or Windows Me, configure Task Scheduler to launch a .BAT file in place of using AutoRun.� If you are using Windows NT or Windows 2000, configure Windows Schedule Service (refer to document AKBID1047) to launch a .BAT file in place of AutoRun.� Configure the launch time as described at the beginning of this document and create GCPURGEX.BAT in the Windows folder, and add the following information to GCPURGEX.BAT:

Navigate to the BackOffice folder.� In this example, the BackOffice folder is in the D:\ALOHA\BACKOFFICE folder.

D:

CD\ALOHA\BACKOFFICE

Initialize GCEXPORT.EXE to export the gift certificates.

START /WAIT GC\GCPURGE.EXE AUTO

Initialize GCPURGE.EXE to purge the gift certificates.

START /WAIT GC\GCEXPORT.EXE AUTO

Run CLOSEAPP.EXE.� If the E-Messenger software is already active, the batch file will not be able to automatically send the files to the corporate office.� To ensure that E-Messenger is not already active, use the CLOSEAPP.EXE utility (refer to document AKBID1012) in the batch file to close E-Messenger before trying to send the files.� You may also want to use this after the package has been sent to shut down E-Messenger.

START /WAIT <location of CLOSEAPP.EXE>\CLOSEAPP.EXE /CLOSE ENTERPRISE

Launch E-Messenger.

START /WAIT "ENTERPRISE MESSAGING\EMESSENGER.EXE" AUTO

Finished.

EXIT

Create EMSG.CMD and Configure Windows Schedule Service at the Store

After the corporate office has processed the gift certificate information sent from the stores, each store must initialize E-Messenger from a .CMD file to retrieve the updated data from the corporate office and process it.

If you are using Windows 95, Windows 98, or Windows Millennium Edition (Me), configure Task Scheduler to launch the .CMD file.� If you are using Windows NT or Windows 2000, configure Windows Schedule Service (refer to document AKBID1047) to launch the .CMD file.

Create EMSG.CMD in the Windows folder, and add the following information to EMSG.CMD:

If the E-Messenger software is already active, the batch file will not be able to automatically send the files to the corporate office.� To ensure that E-Messenger is not already active, use the CLOSEAPP.EXE utility (refer to document AKBID1012) in the batch file to close E-Messenger before trying to send the files.� You may also want to use this after the package has been sent to shut down E-Messenger.

�� CLOSEAPP.EXE /CLOSE ENTERPRISE

Navigate to the BackOffice folder.� In this example, the BackOffice folder is in the D:\ALOHA\BACKOFFICE folder.

D:

CD\ALOHA\BACKOFFICE

This command line initializes E-Messenger to send the files and any other queued files (Windows 95, Windows 98, and Windows Me only).

IBERDIR%\BACKOFFICE\ENTERPRISE MESSAGING\EMESSENGER.EXE" /AUTO

Set the SU.EXE command line that initializes E-Messenger to send the files and any other queued files (Windows NT and Windows 2000 only).

SET SU_COMMANDLINE="%IBERDIR%\BACKOFFICE\ENTERPRISE MESSAGING\EMESSENGER.EXE" /AUTO

Run SU.EXE to initialize E-Messenger to send the files.� In this example, the user name is 'aloha' and the password is 'hello'.� Edit this command line, and insert the user name and password that matches the profile previously set up in E-Messenger (Windows NT and Windows 2000 only).

This command line creates a potential security risk since it exposes the user name and password.� If this is not acceptable, consult SU.TXT (included in SU.ZIP) for more password options.

ECHO hello| START /WAIT SU.EXE aloha

Import the new gift certificate information.

%IBERDIR%\BACKOFFICE\GC\GCIMPORT.EXE AUTO

Finished.

EXIT

E-Messenger Debugging Files

E-Messenger provides a debugging log file to assist users in troubleshooting problems processing packages.� Open E-Messenger, and select File/View Process Log to view the debugging file.

Extended Information

No information.

Caveats

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

Transferring gift certificate data from a store to a corporate office requires the MAPI client and E-Messenger installed and configured at each store and the corporate office.� You must install The MAPI client before installing E-Messenger.

This document is based on E-Messenger version 1.03 SP3.� After installing E-Messenger, ensure version compliance with this document.

You must select the 'Corporate Store' option when installing Gift Certificate Manager at a store.

When installing Gift Certificate Manager at the store, you must install the demonstration database or a database from the corporate office with the store already configured in it.� Otherwise, you will receive an error at the store stating 'Unable to Initialize GC Server' or 'Unable to Initialize the Gift Certificate services.� Can't continue' when starting the Aloha interface.

Since the paths listed below are based on the %IBERDIR%\BACKOFFICE folder as the root folder instead of the actual root drive folder, the Browse button is not compatible and should not be used.

The AutoRun applications at the stores must be set in the proper order to function properly.

You must select the 'Corporate Office' option when installing Gift Certificate Manager at the corporate office.

============================================================================

See also:

Aloha Enterprise Messenger User Manual

Aloha Gift Certificate Manager User Manual

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1034 Using a WAN and Corporate Gift Certificates

AKBID1047 Microsoft Windows Schedule Service

AKBID1061 Using E-Messenger to Send Aloha Data to a Corporate Office

AKBID1143 E-Messenger PACKAGE.DAT Files

AKBID1168 Configuring Gift Cards for Use with Gift Certificate Manager

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1135

�

Exporting BackOffice Customer Data to a .TXT File

Exporting BackOffice Customer Data to a .TXT File

============================================================================

AKBID1136

Created: 31 May 2000

Updated: 8 June 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

Subject: Using Microsoft Access to Export BackOffice Customer Data to a Text File

============================================================================

Summary

The ALOHA^� application software Delivery/Frequent Diner BackOffice product stores customer information in a Microsoft Access database.� Restaurants can use Access to export the customer database into a text file for use with other products.� This document explains how to export BackOffice customer data to a text file.

Information

Perform the following to export the BackOffice customer database into a text file:

1.        Open Access and start a blank database.

2.        Label the database to your preference, and click 'Create'.

3.        Select File/Get External Links/Link Tables to open the 'Link' window.

4.        Path-out the location of the DSDATA.MDB database file, and click 'Link' to open the 'Link Tables' window.� (DSDATA.MDB most likely resides in the \BACKOFFICE\DS folder.)

5.        Select the 'Customers' table, and click 'OK'.� This links the Customers table from the DSDATA.MDB database to the new database created in steps 1 and 2.

6.        Select the Query tab to create a query to export the data to a .TXT or .CSV file.� This opens the 'New Query' window.

7.        Select 'Simple Query Wizard', click 'OK', and follow the wizard through the steps.

8.        When the query results display, select File/Save As/Export.� Select 'To an External File or Database' from the 'Save As�' window.

9.        Select 'Text Files (*.txt; *.csv; *.tab; *.asc)' from the 'Save as type' drop-down menu in the 'Save Query' window.

10.     The 'Export Text Wizard' guides you through the rest of the process.� Select the options that best suite your needs.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha Delivery and Frequent Buyer User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1136

�

IBM Kitchen System

IBM Kitchen System

============================================================================

AKBID1137

Created: 1 June 2000

Updated: 15 August 2003

Reviewed: 25 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Using the IBM Kitchen with the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software supports the IBM^� Kitchen System.� The IBM Kitchen System requires you to assign address numbers to each video controller and set the proper Microsoft^� Windows^� environment variables in order to interface it with the Aloha application software.

Information

Set the Video Device Type in the Aloha application software to IBM.� For additional information on configuring videos in the Aloha application software, refer to the Aloha Video User Manual.

For more information configuring the IBM Kitchen System hardware or wiring, refer to the IBM Kitchen System: Installation, Operation and Service Manual available at http://www2.clearlake.ibm.com/store/support/html/pubs.html#Kitchen.

When adjusting the IBM Kitchen System settings, you must restart the IBM Kitchen System components along with the Aloha application software.

Setting Address Numbers

You must configure each I/O unit to use a separate address between 00 and 15.� The address matches the identification number you assigned to the video monitor in the Aloha application software Back-of-House (BOH).

After connecting all of the hardware, perform the following on each I/O unit to assign an address:

1.        Press the reset button on the I/O box (or unplug the I/O box and plug it back in).

2.        As soon as the diagnostic menu appears, immediately press '1' on the bump bar.

3.        Select 'Address Setup' from the diagnostic menu.

4.        Set the address.

5.        Exit the diagnostic menu.

Environment Settings

The Aloha application software uses the IBMVIDEOS, IBMMODE, and IBMPORT environment variables to communicate with the IBM Kitchen System.�

IBMVIDEOS enumerates the number of IBM Kitchen System devices chained off the serial port.� For example, if video numbers one, two, and three are connected to the port, the IBMVIDEOS variable is the following:

SET IBMVIDEOS=1,2,3

If video numbers one, three, and five are connected to the port, the IBMVIDEOS variable is the following:

SET IBMVIDEOS=1,3,5

IBMMODE sets the video characters per line and number of lines on the monitor.� Mode 1 is 40x25, and Mode 3 is 80x25.� This is not typically used.

IBMPORT sets the serial port the IBM Kitchen System is attached to.� For example, if the system uses port number two, the variable is the following:

SET IBMPORT=2

Extended Information

No information.

Caveats

When adjusting the IBM Kitchen System settings, you must restart the IBM Kitchen System components along with the Aloha application software.

============================================================================

See also:

Aloha Video User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1137 kvs

�

APG Cash Drawer Model 212A

APG Cash Drawer Model 212A

============================================================================

AKBID1138

Created: 1 June 2000

Updated: 1 June 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: APG Cash Drawer Model 212A Settings for the Aloha Application Software

============================================================================

Summary

The APG Cash Drawer^� model 212A requires configuration of jumpers and dual inline package (DIP) switches to function with the ALOHA^� application software.

Information

Cash Drawer Status

The 212A uses jumpers to enable sending the cash drawer open or closed status to the Aloha application software.

Always jumper pins 6, 8, and 20 on jumper J1.

Jumper J2 enables or disables the open or closed signal.� Jumper pins 4 and 5 to disable the signal.

Perform one of the following two options to enable the open or closed signal (the Aloha application software can be configured to work either way):

1.        Jumper pin SW to pin 5 on jumper J2 to send the signal on serial pin 5 (Clear to Send or CTS).

2.        Jumper pin 22 to pin SW and pin 5 to pin 4 on jumper J2 to send the signal on serial pin 22 (Ring Indicator or RI).

Set the compulsory method in cash drawer maintenance to match the serial pin you selected to send the signal.� Refer to document AKBID3113 for more information.

ASCII Characters

The Aloha POS sends the '0' ASCII character to the 212A to signal the drawer to open.�

To set the correct ASCII character, set DIP switch banks A and B to the following:

Switch

1

2

3

4

5

6

7

8

Bank A

On

On

On

On

Off

Off

On

On

Bank B

Off

Off

On

Off

Off

On

Off

On

Data Flow

To enable the correct data flow settings for the Aloha application software, set DIP switch bank C to the following:

Switch

1

2

3

4

5

6

7

8

Use

Baud Rate (300)

Baud Rate (300)

Baud Rate (300)

Parity Type (N/A)

Parity Check (None)

Data Bits (8)

Numb.� ASCII Char.� (1)

DCE or DTE (DTE)

Setting

Off

On

On

On

On

Off

On

Off

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID3113 Serial Cash Drawer Compulsory Method

AKBID3116 SERIALDRAWERCOUNT in ALOHA.INI

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1138 212

�

Serial Port Error Return Codes

Serial Port Error Return Codes

============================================================================

AKBID1139

Created: 20 June 2000

Updated: 2 August 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Aloha Application Software Serial Port Error Return Codes

============================================================================

Summary

The ALOHA^� application software displays serial or communications (COM) port error codes in a numerical format.� This document describes each numerical error code to provide technicians with a better understanding of the problem.

Information

When the Aloha application software displays the following message when and error is encountered when communicating to a COM port:

Device Name: Failed to open com port nn, status xx

'Device Name' is the same of the device, such as a printer.� 'nn' is the serial port number.� 'xx' is the error type described in the following table:

Error

Description

0

Successful communication

1

General error, usually encountered when two devices are assigned to the same serial port

2

Invalid COM port

3

Port is in use by another device, usually not a device configured in the Aloha application software

5

Out of memory

6

Port is not setup

7

One or more arguments are invalid (programming error)

25

Illegal baud rate

26

Illegal parity

27

Illegal word length

28

Illegal stop bits

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

AKBID3051 COM Port Error -1

AKBID3052 COM Port Error �3

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1139 alohaspy printer spy

�

Remote BackOffice Gift Certificate Workstation

Remote BackOffice Gift Certificate Workstation

============================================================================

AKBID1140

Created: 10 July 2000

Updated: 25 October 2001

Reviewed: 16 February 2004

Microsoft Windows Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

Subject: Configuring Remote BackOffice Gift Certificate Workstations

============================================================================

Summary

You can configure remote ALOHA^� application software BackOffice Gift Certificate workstations (version 2.01 and higher) to remotely access, edit, and report the application's data.� The BackOffice network security option enables remote use without requiring a separate security key for each remote workstation.

Information

Remote BackOffice applications require TCP/IP (refer to document AKBID1063) to communicate between the file server and the remote workstation.� You must configure TCP/IP as lana zero (refer to document AKBID1018)

Licenses

You must license the BackOffice application for enough users to not effect the operation of the POS interface with the BackOffice application.� Each workstation concurrently connected to the BackOffice application must have a license.� Although each component within the BackOffice application does not require a separate license, each workstation concurrently and actively using the BackOffice application does require a license.

For example, the POS interface and the BackOffice Main Menu on the file server only require a single license, even if they are running at the same time.� Since the POS interface must always be functional to ensure communication with the Front-of-House (FOH) terminals, the file server requires a license that should not be shared.� Extra licenses are required for remote workstations.�

Each remote workstation does not require a separate license if they are connected at separate times.� For example, three licenses allow the file server and any two remote workstations to connect to the BackOffice application.� A different remote workstation may connect at a later time after one of the previous two workstations disconnects.

It is very important not to let the remote workstations interfere with the POS interfaces ability to function properly.

Install Gift Certificate on the File Server

Install the Gift Certificate software on the file server using the Aloha Installation CD and configure BackOffice License Manager.�

Do not select 'Use Network Security' in BackOffice License Manager.

Install Gift Certificate on the Remote Workstation

Before installing the Gift Certificate software on the remote workstation, ensure the remote workstation has access to a shared resource on the file server that contains the Gift Certificate database.� This is usually the BOOTDRV share if the file server's BackOffice folder resides in the Aloha application software folder.

Install the Gift Certificate software on the remote workstation using the Aloha Installation CD.� Configure BackOffice License Manager by selecting 'Use Network Security' in BackOffice License Manager and enter the file server name in the 'Remote Server Name' text box.�

If a shortcut to the POS interface is automatically added to the Microsoft^� Windows^� StartUp folder on the remote workstation, remove it from the start up group so it does not interfere with the POS interface on the file server.� Refer to document AKBID3102 for more information.

Configure Databases on the Remote Computer

The remote workstation must have access to the following databases and files in the \BACKOFFICE\GC folder on the file server: GC.INI, GCDATA.MDB, and GCDATAB.MDB.� Edit FASTECH5.INI in the BackOffice folder and edit the GC path variable in the [ModuleData] section to point to the \BACKOFFICE\GC folder on the file server (the existing line says 'GC=GC').� For example, if the BackOffice folder resides within the Aloha application software folder on the file server, the variable may appear as the following:

GC=\\ALOHABOH\BOOTDRV\BACKOF~1\GC

Note the use of the '8.3' version of the BackOffice folder's name.

If the GC.INI exists in the \BACKOFFICE\GC folder on the remote workstation, then the BackOffice Gift Certificate application will read the local copy rather than the version on the file server.� Delete the local copy of the \BACKOFFICE\GC\GC.INI to force the BackOffice Gift Certificate application to read the version on the file server.

Start the BackOffice Gift Certificate Menu using the shortcut in the Windows start menu created by the BackOffice installation program.

Troubleshooting

Three common problems using remote BackOffice workstations are the TCP/IP settings, share access, and licenses.

The file server and remote workstations must communicate with TCP/IP, and TCP/IP must be assigned to lana zero on the file server and remote workstations.� Refer to document AKBID1063 for more information on TCP/IP and document AKBID1018 for more information on network lana numbers.

If the remote workstation can not access the databases on the file server, it will display the following error:

'MSDOS Command Share.exe is not loaded or functioning correctly.�� Application requires Share be loaded and executed correctly'

Verify if the share on the file server enables the user full access to the files and if the GC variable in the [ModuleData] section of FASTECH5.INI is set correctly.� The share must allow the remote workstation full read and write access to the database files.

The BackOffice application must have enough licenses to allow the required remote connections plus the local connection (the POS interface).� If there are no open licenses available, the remote workstation will not be able to start the application.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha BackOffice Gift Certificate User Manual

AKBID1018 Network Lana Numbers

AKBID1063 TCP/IP

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1140

�

Remote BackOffice Accounts Receivable Workstation

Remote BackOffice Accounts Receivable Workstation

============================================================================

AKBID1141

Created: 10 July 2000

Updated: 25 October 2001

Reviewed: 16 February 2004

Microsoft Windows Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

Subject: Configuring Remote BackOffice Accounts Receivable Workstations

============================================================================

Summary

You can configure the ALOHA^� application software BackOffice Accounts Receivable application (version 2.06 and higher) on remote workstations in order to access, edit, and report the application's data.� The BackOffice network security option enables remote use without requiring a separate security key for each remote workstation.

Information

Remote BackOffice applications require TCP/IP (refer to document AKBID1063) to communicate between the file server and the remote workstation.� You must configure TCP/IP as lana zero (refer to document AKBID1018)

Licenses

You must license the BackOffice application for enough users to not effect the operation of the POS interface with the BackOffice application.� Each workstation concurrently connected to the BackOffice application must have a license.� Although each component within the BackOffice application does not require a separate license, each workstation concurrently and actively using the BackOffice application does require a license.

For example, the POS interface and the BackOffice Main Menu on the file server only require a single license, even if they are running at the same time.� Since you must keep the POS interface functional to ensure communication with the Front-of-House (FOH) terminals, the file server requires a license that should not be shared.� Extra licenses are required for remote workstations.�

Each remote workstation does not require a separate license if they are connected at separate times.� For example, three licenses allow the file server and any two remote workstations to connect to the BackOffice application.� A different remote workstation may connect at a later time after one of the previous two workstations disconnects.

It is very important not to let the remote workstations interfere with the POS interfaces ability to function properly.

Install Accounts Receivable on the File Server

Install the Accounts Receivable software on the file server using the Aloha Installation CD and configure BackOffice License Manager.�

Do not select 'Use Network Security' in BackOffice License Manager.

Install Accounts Receivable on the Remote Workstation

Before installing the Accounts Receivable software on the remote workstation, ensure the remote workstation has access to a shared resource on the file server that contains the Accounts Receivable database.� This is usually the BOOTDRV share if the file server's BackOffice folder resides in the Aloha application software folder.

Install the Accounts Receivable software on the remote workstation using the Aloha Installation CD.� Configure BackOffice License Manager by selecting 'Use Network Security' in BackOffice License Manager and enter the file server name in the 'Remote Server Name' text box.�

If a shortcut to the POS interface is automatically added to the Microsoft^� Windows^� StartUp folder on the remote workstation, remove it from the start up group so it does not interfere with the POS interface on the file server.� Refer to document AKBID3102 for more information.

Configure Databases on the Remote Computer

The remote workstation must have access to the following databases and files in the \BackOffice\DS folder on the file server: AR.ini and DSData.mdb.� Edit Fastech5.ini in the BackOffice folder and edit the AR and DS path variables in the [ModuleData] section to point to the \BackOffice\DS folder on the file server (the existing lines say 'AR=DS' and 'DS=DS').� For example, if the BackOffice folder resides within the Aloha application software folder on the file server, the variables may appear as the following:

AR=\\AlohaBOH\BootDrv\BackOf~1\DS

DS=\\AlohaBOH\BootDrv\BackOf~1\DS

Note the use of the '8.3' version of the BackOffice folder's name.

If the AR.INI exists in the \BackOffice\DS folder on the remote workstation, then the BackOffice Accounts Receivable application will read the local copy rather than the version on the file server.� Delete the local copy of the \BackOffice\DS\AR.ini to force the BackOffice Accounts Receivable application to read the version on the file server.

Start the BackOffice Accounts Receivable Menu using the shortcut in the Windows start menu created by the BackOffice installation program.

Troubleshooting

Three common problems using remote BackOffice workstations are the TCP/IP settings, share access, and licenses.

The file server and remote workstations must communicate with TCP/IP, and you must assign TCP/IP to lana zero on the file server and remote workstations.� Refer to document AKBID1063 for more information on TCP/IP and document AKBID1018 for more information on network lana numbers.

If the remote workstation cannot access the databases on the file server, it will display the following error:

'MSDOS Command Share.exe is not loaded or functioning correctly.�� Application requires Share be loaded and executed correctly'

Verify if the share on the file server allows the user full access to the files and if the AR and DS variables in the [ModuleData] section of Fastech5.ini are set correctly.� The share must allow the remote workstation full read and write access to the database files.

The BackOffice application must have enough licenses to allow the required remote connections plus the local connection (the POS interface).� If there are no open licenses available, the remote workstation will not be able to start the application.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha BackOffice Accounts Receivable User Manual

AKBID1018 Network Lana Numbers

AKBID1063 TCP/IP

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1141 a/r ar

�

Remote BackOffice Delivery/Frequent Buyer Workstation

Remote BackOffice Delivery/Frequent Buyer Workstation

============================================================================

AKBID1142

Created: 16 June 2000

Updated: 25 October 2001

Reviewed: 16 February 2004

Microsoft Windows Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

Subject: Configuring Remote BackOffice Delivery/Frequent Buyer Workstations

============================================================================

Summary

Users of the ALOHA^� application software BackOffice Delivery/Frequent Buyer application (version 5.20 and higher) can configure remote workstations to access, edit, and report the application's data.� The BackOffice network security option enables remote use without requiring a separate security key for each remote workstation.

Information

Remote BackOffice applications require TCP/IP (refer to document AKBID1063) to communicate between the file server and the remote workstation.� You must configure TCP/IP as lana zero (refer to document AKBID1018)

Licenses

You must license the BackOffice application for enough users to not effect the operation of the POS interface with the BackOffice application.� Each workstation concurrently connected to the BackOffice application must have a license.� Although each component within the BackOffice application does not require a separate license, each workstation concurrently and actively using the BackOffice application does require a license.

For example, the POS interface and the BackOffice Main Menu on the file server only require a single license, even if they are running at the same time.� Since the POS interface must always be functional to ensure communication with the Front-of-House (FOH) terminals, the file server requires a license that should not be shared.� Extra licenses are required for remote workstations.�

Each remote workstation does not require a separate license if they are connected at separate times.� For example, three licenses allow the file server and any two remote workstations to connect to the BackOffice application.� A different remote workstation may connect at a later time after one of the previous two workstations disconnects.

It is very important not to let the remote workstations interfere with the POS interfaces ability to function properly.

Install Frequent Buyer on the File Server

Install the Frequent Buyer software on the file server using the Aloha Installation CD and configure BackOffice License Manager.�

Do not select 'Use Network Security' in BackOffice License Manager.

Install Frequent Buyer on the Remote Workstation

Before installing the Frequent Buyer software on the remote workstation, ensure the remote workstation has access to a shared resource on the file server that contains the Frequent Buyer database.� This is usually the BOOTDRV share if the file server's BackOffice folder resides in the Aloha application software folder.

Install the Frequent Buyer software on the remote workstation using the Aloha Installation CD.� Configure BackOffice License Manager by selecting 'Use Network Security' in BackOffice License Manager and enter the file server name in the 'Remote Server Name' text box.�

If a shortcut to the POS interface is automatically added to the Microsoft^� Windows^� StartUp folder on the remote workstation, remove it from the start up group so it does not interfere with the POS interface on the file server.� Refer to document AKBID3102 for more information.

Configure Databases on the Remote Computer (BackOffice 5.24 and lower)

The remote workstation must have access to the following databases and files in the \BACKOFFICE\DS folder on the file server: DBENGINE.INI, DS.INI, DSDATA.MDB, and DSDATAB.MDB.� If you are using Delivery/Frequent Buyer versions 5.24 or lower, create the DS5DATAPATH system environment variable on each remote workstation to define the location of the \BACKOFFICE\DS folder on the file server.� For example, if the BackOffice folder resides within the Aloha application software folder on the file server, the variable may appear as the following:

SET DS5DATAPATH=\\ALOHABOH\BOOTDRV\BACKOF~1\DS

Note the use of the '8.3' version of the BackOffice folder's name.

Start the BackOffice Frequent Buyer Menu using the shortcut in the Windows start menu created by the BackOffice installation program.

Configure Databases on the Remote Computer (BackOffice 5.25 and higher)

The remote workstation must have access to the following databases and files in the \BACKOFFICE\DS folder on the file server: DBENGINE.INI, DS.INI, DSDATA.MDB, and DSDATAB.MDB.� If you are using Delivery/Frequent Buyer versions 5.25 or higher, edit FASTECH5.INI in the BackOffice folder and edit the DS path variable in the [ModuleData] section to point to the \BACKOFFICE\DS folder on the file server (the existing line says 'DS=DS').� For example, if the BackOffice folder resides within the Aloha application software folder on the file server, the variable may appear as the following:

DS=\\ALOHABOH\BOOTDRV\BACKOF~1\DS

Note the use of the '8.3' version of the BackOffice folder's name.

If the DS.INI exists in the \BACKOFFICE\DS folder on the remote workstation, then the BackOffice Delivery/Frequent Buyer application will read the local copy rather than the version on the file server.� Delete the local copy of the \BACKOFFICE\DS\DS.INI to force the BackOffice Delivery/Frequent Buyer application to read the version on the file server.

Start the BackOffice Frequent Buyer Menu using the shortcut in the Windows start menu created by the BackOffice installation program.

Troubleshooting

Three common problems using remote BackOffice workstations are the TCP/IP settings, share access, and licenses.

The file server and remote workstations must communicate with TCP/IP, and TCP/IP must be assigned to lana zero on the file server and remote workstations.� Refer to document AKBID1063 for more information on TCP/IP and document AKBID1018 for more information on network lana numbers.

If the remote workstation can not access the databases on the file server, it will display the following error:

'MSDOS Command Share.exe is not loaded or functioning correctly.�� Application requires Share be loaded and executed correctly'

Verify if the share on the file server enables the user full access to the files and if the DS5DATAPATH variable is set correctly.� The share must allow the remote workstation full read and write access to the database files.

The BackOffice application must have enough licenses to allow the required remote connections plus the local connection (the POS interface).� If there are no open licenses available, the remote workstation will not be able to start the application.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha BackOffice Delivery/Frequent Buyer User Manual

AKBID1018 Network Lana Numbers

AKBID1063 TCP/IP

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1142 fb

�

E-Messenger PACKAGE.DAT Files

E-Messenger PACKAGE.DAT Files

============================================================================

AKBID1143

Created: 21 June 2000

Updated: 27 June 2000

Reviewed: 5 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

Subject: Enterprise Messenger PACKAGE.DAT Fields

============================================================================

Summary

The ALOHA^� application software BackOffice Enterprise Messenger (E-Messenger) software uses PACKAGE.DAT files to assign email file attachments and define how E-Messenger on the receiving end is to process the attached files included in the message.

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

Information

Each line in PACKAGE.DAT refers to a file (email attachment) that is sent from one location to another using E-Messenger.� PACKAGE.DAT files may have multiple lines for multiple files (one per file).� Each line is comprised of the following six fields:

Field

Usage

Description

1

Required

Full path and file to send.

2

Required

Target location (folder name) to save the file on the target system.� Do not include the file name, for it uses the file's original name.

3

Optional

Full name of the command to execute on target system after file is saved to the target

location.� This can include command line arguments.

4

Required

The text 'SAVE' or 'DELETE'.� This indicates whether the file should be left in

the target folder after the command specified in field three has completed execution.

5

Optional

The email address of the target system.� If this is specified, it overrides the default

email address defined in E-Messenger.

6

Optional

The text 'SAVE' or 'DELETE'.� This indicates whether the file should be deleted from the source system after it has been sent to the target.� If it is left blank, the default behavior is 'SAVE'.

A comma separates each field.� If optional fields are not used in the command line, the commas separating the fields are still required.� For example:

C:\CONFIG.SYS,C:\TEMP,,SAVE,,

Automatically Executing E-Messenger

The following command line automatically executes E-Messenger to send or receive and process the files queued in PACKAGE.DAT:

"<location of BackOffice folder>\ENTERPRISE MESSAGING\EMESSENGER.EXE" /AUTO

If E-Messenger is already active, this command line will not function properly.� Use CLOSEAPP.EXE (refer to document AKBID1012) to close E-Messenger before executing this command line.

PACKAGE.DAT Command Line Examples

Use the following command line to create a PACKAGE.DAT file that sends the CONFIG.SYS file on the local system to a target system and places it in the C:\TEMP folder on the target system:

IF EXIST C:\CONFIG.SYS ECHO C:\CONFIG.SYS,C:\TEMP,,SAVE,, >> C:\EMAIL\PACKAGE.DAT

Use the following command line to verify if GNDITEM.DBF exists in the dated folder on the local system, send GNDITEM.DBF to the target system, and place GNDITEM.DBF in the D:\STORES\STORE01\20000621 folder on the target system:

IF EXIST D:\ALOHA\20000621\GNDITEM.DBF ECHO D:\ALOHA\20000621\GNDITEM.DBF,D:\STORES\STORE01\20000621,,SAVE,, >> C:\EMAIL\PACKAGE.DAT

If the previous example is used in the Winhook batch file (refer to document AKBID1028), use '%1' in place of the dated folder's name.�

IF EXIST D:\ALOHA\%1\GNDITEM.DBF ECHO D:\ALOHA\%1\GNDITEM.DBF,D:\ALOHA\STORE01\%1,,SAVE,, >> C:\EMAIL\PACKAGE.DAT

The previous command line can also use a macro (GNDDIR) and a UNITNUM environment variable to create a command line for use with Winhook in multiple stores.

GNDDIR is a macro created in E-Messenger.� The macro specifies the folder on the target computer to receive the sent files.� The dollar signs ($) on each side of the label define it as a macro in command lines.

For example, the target computer may have a folder on D: labeled 'STORES'.� Inside the 'STORES' folder is a sub-folder for each store labeled with the store number (for example, D:\STORES\STORE01).

In this case, perform the following to create a macro on the target computer to define the target folder:

Open E-Messenger.

Select File/Macro Definitions.

Click 'Add Macro'.

Name the macro 'GNDDIR' and give the macro a path of 'D:\STORES'.

Click 'OK'.

When a package is sent from the store, E-Messenger on the target computer replaces '$GNDDIR$' with 'D:\STORES' when processing the package.�

'GNDDIR' is not a required label for the macro.� Users can specify different names as long as the packages from the stores also refer to the different name.

The store's subfolder label is defined in PACKAGE.DAT when it is created at the store with the UNITNUM variable.� Create a system environment variable at the store assigning UNITNUM to a value of� 'STORE01'.

The following is an example of a command line that uses the GNDDIR macro and the UNITNUM variable:

IF EXIST D:\ALOHA\%1\GNDITEM.DBF ECHO D:\ALOHA\%1\GNDITEM.DBF,$GNDDIR$\%UNITNUM%\%1,,SAVE,, >> C:\EMAIL\PACKAGE.DAT

Extended Information

No information.

Caveats

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

============================================================================

See also:

Aloha BackOffice Enterprise Messenger User Manual

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1028 Winhook

AKBID1061 Using E-Messenger to Send Data to a Corporate Office

AKBID1135 Using E-Messenger and Corporate Gift Certificates

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1143

�

Importing Aloha Daily Sales Data into BackOffice Inventory

Importing Aloha Daily Sales Data into BackOffice Inventory

============================================================================

AKBID1144

Created: 22 June 2000

Updated: 29 September 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

Subject: Using Data Manager to Import Aloha Daily Sales Data into BackOffice Inventory Control

============================================================================

Summary

ALOHA^� application software BackOffice Inventory Control uses Data Manager to import the daily sales information from the application software.� After the Grind process completes (refer to document AKBID1016) following the End-of-Day (EOD) process (refer to document AKBID1015), you can open Data Manager and import the sales data for the Date-of-Business (DOB).

Information

Create a Data Manager Job

Open Inventory Control, and perform the following to create a new Data Manager job to import the daily sales data:

1.        Select Window/Data Manager/Edit Jobs or click the 'Data Manager' toolbar button (the button displaying a lightening bolt) and select Edit Jobs.

2.        Click the 'New Job' toolbar button (the button displaying a blank sheet of paper on the top toolbar) and create a label for the new job (for example, 'Aloha Daily Sales Import').

3.        Click the 'Save' toolbar button (the button displaying a diskette on the top toolbar) to save the new job.

4.        Create a new task by clicking the 'New Task' toolbar button (the button displaying a blank sheet of paper on the bottom toolbar) and create a label for the new task (for example, 'Aloha Daily Sales Import').

5.        Click the 'Load task from file' toolbar button (the button displaying an open folder on the bottom toolbar) to load an existing task from a file.

6.        Navigate to the \BACKOFFICE\DATA MANAGER TEMPLATES\ALOHA folder, select 'Aloha Sales Item Import.dtm', and click Open.

7.        Click the 'Save' toolbar button (the button displaying a diskette on the bottom toolbar) to save the new task.

8.        Click the Close button.

Import the Daily Sales Files

Open Inventory Control and perform the following to import the daily sales data:

1.        Select Window/Data Manager/Run Jobs or click the 'Data Manager' toolbar button (the button displaying a lightening bolt) and select Run Jobs.

2.        Select the job created in the first portion of this document.

3.        Finish importing the sales and creating a 'sales day' as instructed in the Aloha BackOffice User Manual.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha BackOffice Inventory Control User Manual

AKBID1015 EOD Process and Errors

AKBID1016 Grind Process and Errors

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1144

�

T= and C= Errors

T= and C= Errors

============================================================================

AKBID1145

Created: 28 December 2000

Updated: 28 December 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

Subject: T= and C= Errors on FOH Terminals or Debouts

============================================================================

Summary

In some cases where the ALOHA^� application software experiences TRANS.LOG (transaction log) corruption, you will receive 'T= C=' errors on the Front-of-House (FOH) terminals or in the FOH debugging-output-files (debouts).� These errors are referring to specific tables (T=) and checks (C=) in the transaction log.

The table and check IDs used in the TRANSACTION LOG are not the format displayed on the Font-of-House (FOH) terminals or on guest checks.

Information

Transaction log corruption is caused by communication problems between FOH terminals because of hardware issues (for example, network adapters, cabling, and terminations), substandard power, and by not utilizing the Microsoft^� Windows^� Vnetbios.vxd patch (refer to document AKBID1011).

This often results in the following:

1.        Checks and tables 'disappearing'

2.        Check and tables are available on one FOH terminal but not on another FOH terminal

3.        T= and C= errors occurring if a specific table or check is selected from the Working with Tables or Working with Tabs screen

4.        The debouts display T= and C= errors

If checks or tables are not accessible because of T= and C= errors, they will be closed to cash by the End-of-Day process (refer to document AKBID1015).

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha A/C Power and Communication Requirements

AKBID1011 Windows 9x Vnetbios.vxd Patch

AKBID1015 EOD Process and Errors

AKBID1099 Network Troubleshooting

AKBID1134 Debouts

AKBID1154 Aloha Application Software Transaction Log

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1145 disappear equals

�

HDSPACE.EXE Low Disk Space Warning Utility

HDSPACE.EXE Low Disk Space Warning Utility

============================================================================

AKBID1146

Created: 27 June 2000

Updated: 12 October 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: Using the HDSPACE.EXE and HDSPACED.EXE Low Disk Space Warning Utility

============================================================================

Summary

HDSPACE.EXE and HDSPACED.EXE enable a means to verify the available disk space on ALOHA^� application software file servers and terminals.� When you use HDSPACE.EXE and HDSPACED.EXE in conjunction with batch files (.BAT or .CMD), you can configure systems to notify an administrator via an on-screen message or (in some cases) a pager if a hard drive that has reached the low hard drive space warning point.

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

Information

On its own, HDSPACE.EXE and HDSPACED.EXE perform a minor function in the overall warning process.� Batch files perform the majority of the process to enable the most configuration options.� Besides explaining the use of HDPSACE.EXE and HDSPACED.EXE, this document also outlines several methods for using batch files to alert an administrator when a hard drive has reached the warning point.

HDSPACE.EXE

HDSPACE.EXE creates a LOWSPACE file in the working folder if the available hard drive space is below the amount defined in the command line for HDSPACE.EXE.� You must use HDSPACE.EXE from a command line inside Microsoft^� Windows^�.� Use HDSPACED.EXE for a MS-DOS^� prompt outside of Windows, such as the AUTOEXEC.BAT.

Usage: HDSPACE.EXE <drive> <warning point>

<drive> is the local or mapped hard drive to verify the unused hard drive space.

<warning point> is the minimum amount of unused space available before HDSPACE.EXE creates the LOWSPACE file.

Options:

/?�� Displays help information.

HDSPACED.EXE

HDSPACED.EXE creates a LOWSPACE file in the working folder if the available hard drive space is below the amount defined in the command line for HDSPACED.EXE.� Use HDSPACED.EXE for a MS-DOS prompt outside of Windows, such as the AUTOEXEC.BAT.� You must use HDSPACE.EXE from a command line inside Windows.�

Since HDSPACED.EXE is designed for use in a MS-DOS environment, it conforms to the two gigabyte MS-DOS hard drive size limit.� The displayed hard drive size does not exceed two gigabytes, but HDSPACED.EXE still functions properly on a hard drive over two gigabytes as long as the hard drive space warning point is less than two gigabytes.

Usage: HDSPACED.EXE <drive> <warning point>

<drive> is the local or mapped hard drive to verify the unused hard drive space.

<warning point> is the minimum amount of unused space available before HDSPACED.EXE creates the LOWSPACE file.

Options:

/?�� Displays help information.

File Server Method 1

This method checks the file server's hard drive space using a batch file on the file server that creates a message in Microsoft^� Windows^� Notepad that warns the user of the hard drive space shortage.

This method relies on a batch file that navigates to the Aloha application software TMP folder, deletes any previous copies of the LOWSPACE file, applies HDSPACE.EXE, and creates a warning message in Notepad if the hard drive space is low.� The working folder (in this case, the TMP folder) is up to the user, but you must navigate to a folder where you plan to place the LOWSPACE file.

Create a batch file with the following information:

D:

CD\ALOHA\TMP

IF EXIST LOWSPACE DEL LOWSPACE

HDSPACE.EXE D: 10000000

IF EXIST LOWSPACE GOTO ALERT

GOTO END

:ALERT

ECHO *** Alert *** > D:\ALOHA\TMP\ALERT.TXT

ECHO *** Alert *** >> D:\ALOHA\TMP\ALERT.TXT

ECHO Drive D: has reached the hard drive space warning point.� >> D:\ALOHA\TMP\ALERT.TXT

ECHO Contact your hard drive administrator to create more hard drive space.� >> D:\ALOHA\TMP\ALERT.TXT

ECHO *** Alert *** >> D:\ALOHA\TMP\ALERT.TXT

ECHO *** Alert *** >> D:\ALOHA\TMP\ALERT.TXT

NOTEPAD.EXE D:\ALOHA\TMP\ALERT.TXT

GOTO END

:END

EXIT

Depending on your operating system and preferences, you can periodically start the batch file using Windows Schedule Service (refer to document AKBID1047), Windows Task Scheduler, or start it manually.

File Server Method 2

This method checks the file server's hard drive space using a batch file on the file server to alert the administrator via pager of the hard drive space shortage.

This method relies on a batch file that navigates to the Aloha application software TMP folder, deletes any previous copies of the LOWSPACE file, applies HDSPACE.EXE, and pages an administrator if the hard drive space is low.� The working folder (in this case, the TMP folder) is up to the user, but you must navigate to a folder where you plan to place the LOWSPACE file.

Refer to the Modem Issues section of this document for information on the shortcomings of this method.

Create a batch file with the following information:

D:

CD\ALOHA\TMP

IF EXIST LOWSPACE DEL LOWSPACE

HDSPACE.EXE D: 10000000

IF EXIST LOWSPACE GOTO ALERT

GOTO END

:ALERT

ECHO ATDT18005551212,,,,911*100# > COM2

WAIT.EXE 30

ECHO ADH0 > COM2

GOTO END

:END

EXIT

The command line 'ECHO ATDT18005551212,,,,911*100# > COM2' performs the following:

1.        'ECHO' and '> COM2' send the information to the serial port with the modem attached.

2.        'ATDT18005551212' instructs the modem to dial the phone number 1-800-555-1212.� This is the pager's phone number.

3.        ',,,,' creates a pause to wait for the other end of the line to answer.

4.        '911*100#' is the message sent to the pager.� The asterisk (*) sends a dash to the pager, and the pound sign (#) ends the message.� User's can create their own code to send, but in this case, this may represent an emergency (911) with terminal 100.

The command line ' WAIT.EXE 30' uses the WAIT.EXE utility (refer to document AKBID1012) to create a 30-second pause.� This gives the previous command line time to finish before the phone line is disconnected in the next command line.

The command line 'ECHO ADH0 > COM2' sends a 'hang-up' message to the serial port with the modem attached.

Depending on your operating system and preferences, you can periodically start the batch file using Windows Schedule Service (refer to document AKBID1047), Windows Task Scheduler, or start it manually.

File Server Method 3

This method checks the file server's hard drive space using a batch file on a remote computer that creates a message in Microsoft^� Windows^� Notepad that warns the user of the hard drive space shortage.

This method relies on two batch files.� One on the file server to create the LOWSPACE file, and one on the remote computer to search for the LOWSPACE file and display a warning.

The first batch file resides on the file server.� It navigates to the Aloha application software TMP folder, deletes any previous copies of the LOWSPACE file, and applies HDSPACE.EXE.� The working folder (in this case, the TMP folder) is up to the user, but you must navigate to a folder where you plan to place the LOWSPACE file.

Create a batch file with the following information:

D:

CD\ALOHA\TMP

IF EXIST LOWSPACE DEL LOWSPACE

HDSPACE.EXE D: 10000000

Depending on your operating system and preferences, you can periodically start the batch file using Windows Schedule Service (refer to document AKBID1047) or Windows Task Scheduler.

The second batch file resides on the remote computer.� It checks for the LOWSPACE file on the file server, and if found, creates a warning message in Notepad.� The working folder (in this case, the C:\TEMP folder) is up to the user.

Create a batch file with the following information:

IF EXIST \\ALOHBOH\BOOTDRV\ALOHA\TMP\LOWSPACE GOTO ALERT

GOTO END

:ALERT

ECHO *** Alert *** > C:\TEMP\ALERT.TXT

ECHO *** Alert *** >> C:\TEMP\ALERT.TXT

ECHO The file server has reached the hard drive space warning point.� >> C:\TEMP\ALERT.TXT

ECHO Contact your hard drive administrator to create more hard drive space.� >> C:\TEMP\ALERT.TXT

ECHO *** Alert *** >> C:\TEMP\ALERT.TXT

ECHO *** Alert *** >> C:\TEMP\ALERT.TXT

NOTEPAD.EXE C:\TEMP\ALERT.TXT

GOTO END

:END

EXIT

Depending on your operating system and preferences, you can periodically start the batch file using Windows Schedule Service (refer to document AKBID1047), Windows Task Scheduler, or start it manually.

File Server Method 4

This method checks the file server's hard drive space using a batch file on a remote computer to alert the administrator via pager of the hard drive space shortage.

This method relies on two batch files.� One on the file server to create the LOWSPACE file, and one on the remote computer to search for the LOWSPACE file and page an administrator with a warning.

The first batch file resides on the file server.� It navigates to the Aloha application software TMP folder, deletes any previous copies of the LOWSPACE file, and applies HDSPACE.EXE.� The working folder (in this case, the TMP folder) is up to the user, but you must navigate to a folder where you plan to place the LOWSPACE file.

Refer to the Modem Issues section of this document for information on the shortcomings of this method.

Create a batch file with the following information:

D:

CD\ALOHA\TMP

IF EXIST LOWSPACE DEL LOWSPACE

HDSPACE.EXE D: 10000000

Depending on your operating system and preferences, you can periodically start the batch file using Windows Schedule Service (refer to document AKBID1047) or Windows Task Scheduler.

The second batch file resides on the remote computer.� It checks for the LOWSPACE file on the file server, and if found, pages an administrator with a warning.� The working folder (in this case, the C:\TEMP folder) is up to the user

Create a batch file with the following information:

IF EXIST \\ALOHBOH\BOOTDRV\ALOHA\TMP\LOWSPACE GOTO ALERT

GOTO END

:ALERT

ECHO ATDT18005551212,,,,911*100# > COM2

WAIT.EXE 30

ECHO ADH0 > COM2

GOTO END

:END

EXIT

The command line 'ECHO ATDT18005551212,,,,911*100# > COM2' performs the following:

1.        'ECHO' and '> COM2' send the information to the serial port with the modem attached.

2.        'ATDT18005551212' instructs the modem to dial the phone number 1-800-555-1212.� This is the pager's phone number.

3.        ',,,,' creates a pause to wait for the other end of the line to answer.

4.        '911*100#' is the message sent to the pager.� The asterisk (*) sends a dash to the pager, and the pound sign (#) ends the message.� User's can create their own code to send, but in this case, this may represent an emergency (911) with terminal 100.

The command line ' WAIT.EXE 30' uses the WAIT.EXE utility (refer to document AKBID1012) to create a 30-second pause.� This gives the previous command line time to finish before the phone line is disconnected in the next command line.

The command line 'ECHO ADH0 > COM2' sends a 'hang-up' message to the serial port with the modem attached.

Depending on your operating system and preferences, you can periodically start the batch file using Windows Schedule Service (refer to document AKBID1047), Windows Task Scheduler, or start it manually.

POS Terminals Method 1

This method checks the terminal's hard drive space using a batch file on a remote computer creates a message in WindowsNotepad that warns the user of the hard drive space shortage.

This method relies on two batch files.� One on the file server to create the LOWSPACE file, and one on the remote computer to search for the LOWSPACE file and display a warning.

The first batch file resides on the terminal.� It navigates to the Aloha application software TMP folder, deletes any previous copies of the LOWSPACE file, and applies HDSPACE.EXE.� The working folder (in this case, the TMP folder) is up to the user, but you must navigate to a folder where you plan to place the LOWSPACE file.

Create a batch file with the following information:

C:

CD\ALOHA\TMP

IF EXIST LOWSPACE DEL LOWSPACE

HDSPACE.EXE C: 10000000

Depending on your operating system and preferences, you can periodically start the batch file using Windows Schedule Service (refer to document AKBID1047), Windows Task Scheduler, or the AUTOEXEC.BAT.� If you are starting HDSPACE.EXE from the AUTOEXEC.BAT, use HDSPACED.EXE.

The second batch file resides on the remote computer.� It checks for the LOWSPACE file on the terminal, and if found, creates a warning message in Notepad.� The working folder (in this case, the C:\TEMP folder) is up to the user

Create a batch file with the following information:

:START

GOTO TERM1

:TERM1

IF EXIST \\TERM1\BOOTDRV\ALOHA\TMP\LOWSPACE GOTO ALERT1

GOTO TERM2

:TERM2

IF EXIST \\TERM2\BOOTDRV\ALOHA\TMP\LOWSPACE GOTO ALERT2

GOTO TERM3

:TERM3

IF EXIST \\TERM3\BOOTDRV\ALOHA\TMP\LOWSPACE GOTO ALERT3

GOTO TERM4

:TERM4

IF EXIST \\TERM4\BOOTDRV\ALOHA\TMP\LOWSPACE GOTO ALERT4

GOTO END

:ALERT1

ECHO *** Alert *** > C:\TEMP\ALERT1.TXT

ECHO *** Alert *** >> C:\TEMP\ALERT1.TXT

ECHO Terminal 1 has reached the hard drive space warning point.� >> C:\TEMP\ALERT1.TXT

ECHO Contact your hard drive administrator to create more hard drive space.� >> C:\TEMP\ALERT1.TXT

ECHO *** Alert *** >> C:\TEMP\ALERT1.TXT

ECHO *** Alert *** >> C:\TEMP\ALERT1.TXT

NOTEPAD.EXE C:\TEMP\ALERT1.TXT

GOTO TERM2

:ALERT2

ECHO *** Alert *** > C:\TEMP\ALERT2.TXT

ECHO *** Alert *** >> C:\TEMP\ALERT2.TXT

ECHO Terminal 2 has reached the hard drive space warning point.� >> C:\TEMP\ALERT2.TXT

ECHO Contact your hard drive administrator to create more hard drive space.� >> C:\TEMP\ALERT2.TXT

ECHO *** Alert *** >> C:\TEMP\ALERT2.TXT

ECHO *** Alert *** >> C:\TEMP\ALERT2.TXT

NOTEPAD.EXE C:\TEMP\ALERT2.TXT

GOTO TERM3

:ALERT3

ECHO *** Alert *** > C:\TEMP\ALERT3.TXT

ECHO *** Alert *** >> C:\TEMP\ALERT3.TXT

ECHO Terminal 3 has reached the hard drive space warning point.� >> C:\TEMP\ALERT3.TXT

ECHO Contact your hard drive administrator to create more hard drive space.� >> C:\TEMP\ALERT3.TXT

ECHO *** Alert *** >> C:\TEMP\ALERT3.TXT

ECHO *** Alert *** >> C:\TEMP\ALERT3.TXT

NOTEPAD.EXE C:\TEMP\ALERT3.TXT

GOTO TERM4

:ALERT4

ECHO *** Alert *** > C:\TEMP\ALERT4.TXT

ECHO *** Alert *** >> C:\TEMP\ALERT4.TXT

ECHO Terminal 4 has reached the hard drive space warning point.� >> C:\TEMP\ALERT4.TXT

ECHO Contact your hard drive administrator to create more hard drive space.� >> C:\TEMP\ALERT4.TXT

ECHO *** Alert *** >> C:\TEMP\ALERT4.TXT

ECHO *** Alert *** >> C:\TEMP\ALERT4.TXT

NOTEPAD.EXE C:\TEMP\ALERT4.TXT

GOTO END

:END

EXIT

Depending on your operating system and preferences, you can periodically start the batch file using Windows Schedule Service (refer to document AKBID1047), Windows Task Scheduler, or start it manually.

POS Terminals Method 2

This method checks the terminal's hard drive space using a batch file on a remote computer to alert the administrator via pager of the hard drive space shortage.

This method relies on two batch files.� One on the file server to create the LOWSPACE file, and one on the remote computer to search for the LOWSPACE file and page an administrator with a warning.

The first batch file resides on the terminal.� It navigates to the Aloha application software TMP folder, deletes any previous copies of the LOWSPACE file, applies HDSPACE.EXE.� The working folder (in this case, the TMP folder) is up to the user, but you must navigate to a folder where you plan to place the LOWSPACE file.

Refer to the Modem Issues section of this document for information on the shortcomings of this method.

Create a batch file with the following information:

C:

CD\ALOHA\TMP

IF EXIST LOWSPACE DEL LOWSPACE

HDSPACE.EXE C: 10000000

Depending on your operating system and preferences, you can periodically start the batch file using Windows Schedule Service (refer to document AKBID1047), Windows Task Scheduler, or the AUTOEXEC.BAT.� If you are starting HDSPACE.EXE from the AUTOEXEC.BAT, use HDSPACED.EXE.

The second batch file resides on the remote computer.� It checks for the LOWSPACE file on the terminal, and if found, pages an administrator with a warning message.� The working folder (in this case, the C:\TEMP folder) is up to the user

Create a batch file with the following information:

:START

GOTO TERM1

:TERM1

IF EXIST \\TERM1\BOOTDRV\ALOHA\TMP\LOWSPACE GOTO ALERT1

GOTO TERM2

:TERM2

IF EXIST \\TERM2\BOOTDRV\ALOHA\TMP\LOWSPACE GOTO ALERT2

GOTO TERM3

:TERM3

IF EXIST \\TERM3\BOOTDRV\ALOHA\TMP\LOWSPACE GOTO ALERT3

GOTO TERM4

:TERM4

IF EXIST \\TERM4\BOOTDRV\ALOHA\TMP\LOWSPACE GOTO ALERT4

GOTO END

:ALERT1

ECHO ATDT18005551212,,,,911*1# > COM2

WAIT.EXE 30

ECHO ADH0 > COM2

GOTO TERM2

:ALERT2

ECHO ATDT18005551212,,,,911*2# > COM2

WAIT.EXE 30

ECHO ADH0 > COM2

GOTO TERM3

:ALERT3

ECHO ATDT18005551212,,,,911*3# > COM2

WAIT.EXE 30

ECHO ADH0 > COM2

GOTO TERM4

:ALERT4

ECHO ATDT18005551212,,,,911*4# > COM2

WAIT.EXE 30

ECHO ADH0 > COM2

GOTO END

:END

EXIT

The command line 'ECHO ATDT18005551212,,,,911*1# > COM2' performs the following:

1.        'ECHO' and '> COM2' send the information to the serial port with the modem attached.

2.        'ATDT18005551212' instructs the modem to dial the phone number 1-800-555-1212.� This is the pager's phone number.

3.        ',,,,' creates a pause to wait for the other end of the line to answer.

4.        '911*1#' is the message sent to the pager.� The asterisk (*) sends a dash to the pager, and the pound sign (#) ends the message.� User's can create their own code to send, but in this case, this may represent an emergency (911) with terminal 1.

The command line ' WAIT.EXE 30' uses the WAIT.EXE utility (refer to document AKBID1012) to create a 30-second pause.� This gives the previous command line time to finish before the phone line is disconnected in the next command line.

The command line 'ECHO ADH0 > COM2' sends a 'hang-up' message to the serial port with the modem attached.

Depending on your operating system and preferences, you can periodically start the batch file using Windows Schedule Service (refer to document AKBID1047), Windows Task Scheduler, or start it manually.

Modem Issues

Using a modem to page an administrator from a command line may encounter two problems: it may effect the functionality of remote support software or Aloha Electronic Draft Capture (EDC), and initializing a modem from a command line does not work with all modems and all operating systems (OS).

When selecting a modem and COM port to page an administrator from, ensure it does not effect the functionality of Symantec^� pcANYWHERE^� or EDC.� Use a dedicated modem or a remote computer if needed.

Not all modems and operating systems enable you to initialize the modem from a command prompt, although most Hayes-compatible modems should work.� For example, in testing the functionality listed in this document, a 3Com^� U.S.� Robotics^� 33.6 modem and an U.S.� Robotics Courier^� 56K would not work from a command line in Windows NT^�, but would work from a command line in Windows 98 Second Edition (SE).

In cases where the file server is using the Windows NT OS, you may consider using a remote computer to dial the modem.� In cases where a remote computer is not cost effective, consider using one of the Front-of-House (FOH) POS terminals using Windows 98 SE to dial the modem.

Extended Information

Besides using a notepad message or a pager, you can also administer warnings using E-Messenger (to open a notepad warning on an administrator's computer via email, refer to document AKBID1143), or Windows Sound Recorder to play a sound using the following command line:

SNDREC32.EXE /PLAY /CLOSE ALERT.WAV

Caveats

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

HDSPACE.EXE must be used from a command line inside Windows.� Use HDSPACED.EXE for a MS-DOS prompt outside of Windows, such as the AUTOEXEC.BAT.

Before using a modem to page an administrator, refer to the Modem Issues section of this document for information on the shortcomings of this method.

============================================================================

See also:

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1047 Microsoft Windows Schedule Service

AKBID1143 E-Messenger PACKAGE.DAT Files

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1146 diskspace harddrive

�

Bartender Tab Name Options

Bartender Tab Name Options

============================================================================

AKBID1147

Created: 28 September 2000

Updated: 20 July 2001

Reviewed: 27 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 5.0x � 5.3.x

Subject: Bartender Tab Name Options

============================================================================

Summary

The default behavior of the ALOHA^� application software in regards to naming bar tabs is to require the bartender to input a tab name whenever the bartender selects the Working with Tabs button or the New Order button from the Order Entry screen.� This document explains options for naming tabs, and how you can use each in conjunction with one another.� To access these options, open Aloha Manager and select Maintenance/Store Settings/Order Entry, and select the Tabs & Tables subtab.

Information

These options only effect job codes with the Bartender option enabled.

Auto Save Tab When NEW TAB is Pressed

The 'Auto Save Tab When NEW TAB is Pressed' option automatically names tabs 'Fast Close' if you press 'New Order' on the order entry screen.� You cannot manually name tabs, and if you have multiple tabs saved, they are all named 'Fast Close'.

Enabling the Aloha application software to name all tabs 'Fast Close' can lead to confusion, so you should consider enabling 'Auto Name Saved Bar Tabs' with this option.� If you use this option in conjunction with the 'Auto Name Saved Tabs' option, tabs are named according to your initials and a consecutive number rather than the 'Fast Close' name.

If you use this option in conjunction with the 'Auto New Order' option, tabs are automatically named 'Fast Close' when new items are ordered.

Auto New Order

If 'Auto New Order' is enabled and you order items on a tab, then you are prompted to name the current tab, and the Front-of-House (FOH) automatically opens a new blank tab.� If you have already named the tab, then the FOH opens a new tab blank tab without promoting you to name the current tab.�

If you use this option in conjunction with the 'Auto Save Tab When NEW TAB is Pressed' option, tabs are automatically named 'Fast Close' when you order new items.

If you use this option in conjunction with the 'Auto Name Saved Tabs' option, tabs are named according to your initials and a consecutive number only if you close the check without manually selecting an order mode.

Auto Name Saved Tabs

If you enabled 'Auto Name Saved Tabs', then your initials and a consecutive number determine tab names.� For example, Joe Smith's first tab is named 'JS 1', his second tab is named 'JS 2', and so on.�

If you press 'New Order' on the order entry screen, then you must manually assign a name to the tab.� The original tab name (based on your initials) is only saved if you do not press the 'New Order' button.�

The following occur if you use this option in conjunction with the 'Auto Save Tab When NEW TAB is Pressed' option:

1.        Tabs are named according to your initials and a consecutive number rather than the 'Fast Close' name.

2.        You cannot manually name tabs if you press 'New Order'.

If you use this option in conjunction with the 'Auto New Order' option, tabs are named according to your initials and a consecutive number if you close the check without manually selecting an order mode.

Extended Information

Job codes with the Bartender option enabled use tab names instead of table numbers regardless the Sees Tabs job code option.� The Sees Tabs option only effects job codes without the Bartender option enabled.

Caveats

These options only effect job codes with the Bartender option enabled.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1147

�

Backup Procedures

Backup Procedures

============================================================================

AKBID1148

Created: 27 June 2000

Updated: 10 November 2003

Reviewed: 23 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 3.5x � 5.3.x

Subject: Backup Procedures for the Aloha Application Software

============================================================================

Summary

To preserve the ALOHA^� Application Software configuration and historical data in case of a system failure, you must perform regular backups of the Aloha software applications and files.� Since the Aloha application software uses the Microsoft^� Windows^� operating system (OS), there are a number of options for performing backups.� This document explains many of the options and the files to backup, but it is up to you to decide on a backup method that works best for the customer.

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

Information

The most important data to backup on a hard drive is historical Aloha application software information.� The Aloha software applications and binary files are all recoverable from the Aloha Installation CD, and the current data and bitmap files are recoverable from the Front-of-House (FOH) terminals, but the historical information (dated folders), Electronic Draft Capture (EDC) configuration files, EDC settlement files, BackOffice databases, and BackOffice configuration files are only stored in a single place.� It is very important to backup this information on a regular basis.

Backup Software

Backup software is open to the user's preference.� In most cases, the backup software supplied with Windows provides the required functionality, although the native backup software in Windows 95, Windows 98, and Windows Millennium Edition (Me) does not have the command line options available in the native Windows NT^�, Windows 2000, Windows XP, and Windows Server 2003 backup software (refer to document AKBID1027 for more information on Windows NT and Windows 2000 command line options).

Backup Types

In most cases, you will use full backups because they are easier to administer, but there are three types of backups: full backup, incremental backup, and differential backup.

A full backup includes all of the selected files.� The advantage of a full backup is the ease of use during both the backup process and the restoration process.� The disadvantages are time consumption and redundant backups.�

An incremental backup includes all selected files that have changed since the last backup, regardless of the type of backup.� This method offers the better use of media since only changed files are backed up and takes less time, but restoration might take multiple tapes (or other media).�

A differential backup includes all selected files that have changed since the last full backup.� This method uses less time and the restoration only requires two tapes, the last full backup tape and the last differential backup tape.� As the number of changed files increases since the last full backup, differential backups consume more time or more time.

Starting the Backup

Depending on the backup software and operating system, you can use several methods to initialize the backup software, including the Winhook batch file, Windows Schedule Service, Windows Task Schedule, a manual batch file, or scheduling software included in third-party backup software.

What to Backup

Some files in the following table are restorable from other locations such as the Aloha Installation CD or the FOH terminals, but you should include them in the backup routine when possible.� Non-Aloha application software files are not included in this list (such as Microsoft Office documents), but you should include them in the backup.

If you are using a structured-query-language (SQL) database, refer to the SQL Database section of this document.

In cases where the data is recoverable from the FOH terminals, it is important not to let default data installed by the Aloha installation CD overwrite the information on the FOH terminals when the file server is recovered after installing the Aloha application software software.

Files

Location

Notes

All files

%IBERDIR%\yyyymmdd

Dated folders

All files

%IBERDIR%\BIN

Aloha applications.� These files are restored if the Aloha application software is reinstalled, unless the BIN folder contains any site-specific files.

All files

%IBERDIR%\BMP

Aloha BMP files.� These files can be restored from the FOH terminals also.

All files

%IBERDIR%\CORPDATA

Centralized Data Management (CDM) information.

All files

%IBERDIR%\CRW

Seagate Crystal Reports^�.� These files are restored if the Aloha application software is reinstalled, unless the CRW folder contains any site-specific reports.

All files

%IBERDIR%\NEWDATA and DATA

Aloha configuration files.� These files can be restored from the FOH terminals also.

EDC.INI

%IBERDIR%\EDC

EDC configuration file.

*.STL

%IBERDIR%\EDC\<processor folder>

EDC settlement files.

GCLOG.*

%IBERDIR%\HISTORY

Basic gift certificate sales history.� This is only required if the site is using basic gift certificates (instead of BackOffice Gift Certificates).

All files and subfolders

%IBERDIR%\HTML

Aloha Manager HTML files.� These files are restored if the Aloha application software is reinstalled, unless the HTML folder contains any site-specific files.

PMS.INI

%IBERDIR%\PMS

Property Management System (PMS) configuration file.� This is only required if the site is using the PMS interface.

All files and subfolders

%IBERDIR%\PROFILES

Back-of-House (BOH) user profiles.

All files

%IBERDIR%\PROJ

Aloha Labor Scheduler (ALS) labor and sales projection files in versions 5.2.6.x and higher.� This is only required if the site is using ALS.

All files

%IBERDIR%\RECIPE

FOH recipes.� This is only required if the site is using FOH recipes.

All files

%IBERDIR%\RPTEXPORT

Report export settings.

All files

%IBERDIR%\RPTSET

Report content settings.

All files

%IBERDIR%\SCHEDULE

ALS schedule and configuration files in versions 5.2.6.x and higher.� This is only required if the site is using ALS.

IBERSQL.MDB

%IBERDIR%\SQL (or other location where it is stored)

Microsoft Access database.� This is only required if the site is using an Access database.

All files and subfolders

%IBERDIR%\SUM

Summary files.� This is only required if the site is using summary files.

All files

%IBERDIR%\VIZOR

VizorVest^SM configuration

All files

\BACKOFFICE\SCHEDULE\DATA

ALS database and configuration files in versions 5.2.5.x and lower.� This is only required if the site is using ALS.

FASTECH.LIC

\BACKOFFICE\LICENSE

BackOffice license information.

DSDATA.MDB and AR.INI

\BACKOFFICE\DS

BackOffice Accounts Receivable (A/R) database and configuration files.� This is only required if the site is using BackOffice A/R.

AD.INI and ADDATA.MDB

\BACKOFFICE\AD

BackOffice Advanced Reservations database and configuration files.� This is only required if the site is using BackOffice Advanced Reservations.

AUTORUN.INI

\BACKOFFICE

BackOffice AutoRun.� Also copy any folders or files used by AutoRun statements.� This is only required if the site is using BackOffice AutoRun.

FDATADW.MDB

\BACKOFFICE\DATABASE

BackOffice Corporate Reporting database.

All files

\BACKOFFICE\ENTERPRISE MESSAGING

BackOffice Enterprise Messenger (E-Messenger) configuration files.� This is only required if the site is using BackOffice E-Messenger.

*.PST

Varies

BackOffice Enterprise Messenger (E-Messenger) email archive.� This is only required if the site is using BackOffice E-Messenger.

DSDATA.MDB and DS.INI

\BACKOFFICE\DS

BackOffice Frequent Buyer database and configuration files.� This is only required if the site is using BackOffice Frequent Buyer.

GC.INI and GCDATA.MDB

\BACKOFFICE\GC

BackOffice Gift Certificate database and configuration files.� This is only required if the site is using BackOffice Gift Certificates.

~LFDATAS.MDB, B_FDATAS.MDB, FDATAS.MDB and FDATAS.INI

\BACKOFFICE\DATABASE

BackOffice Inventory database and configuration files.� This is only required if the site is using BackOffice Inventory.

Backup Methods

Backup methods might differ between sites, but in general, a daily backup method is recommended.� In order to limit user intervention and thus, have the highest success probability, select backup hardware and media that can hold the entire backup content on a single piece of media.� Automate the backup to start the backup each night after the site closes.

For example, use a tape drive and tapes that hold the backup contents on a single tape.� Use seven tapes and label the tapes for each day of the week.� Start the backup with Winhook each night and instruct the user to insert the correct tape each day.� In this case, the only user intervention is switching the tape each day.� Should they neglect to switch the tape, the backup process still occurs.

Tapes (and most other media) have a limited life and must be replaced according to the manufacturer's recommendations.� Users do not always replace the tapes, so although there is no substitute for buying new tapes, the use of seven tapes (one for each day of the week) provides some buffer for this.� If the tapes are not used daily, they do not wear out as fast, and if a tape corrupts data because of wear, there are six other tapes that may contain restorable (but slightly older) information.

Users may also consider taking a tape off-site in case of a fire or other catastrophe that may destroy both the hard drive and the tapes.

SQL Databases

Backing-up an SQL relational-database (RDB) differs from previous backup methods discussed in this document in that you must backup the RDB using the SQL software, Microsoft SQL Server 6.5 or SQL Server 7.0.� You cannot use NTBACKUP.EXE from a command line to back it up, but the backup software native to SQL Server performs scheduled backups.� The SQL database backup does not replace backing up the files listed previously in this document.

In either case, you must backup the IBERSQL database.

Perform the following to setup and schedule backups of the database in SQL Server 6.5:

1.        Click Start/Programs/Microsoft SQL Server 6.5/SQL Enterprise Manager to open the SQL Server Enterprise Manager.

2.        Select Tools/Database Backup and Restore.

3.        Add a new backup device and select the options that best suite your needs.

4.        To schedule a backup, click Schedule.

5.        Schedule the backup to occur on a regular basis, preferably each day.

6.        Save your changes and close SQL Server Enterprise Manager.

Perform the following to setup and schedule backups of the database in SQL Server 7.0 and SQL Server 2000:

1.        Click Start/Programs/Microsoft SQL Server/Enterprise Manager to open the SQL Server Enterprise Manager.

2.        On the left side of the screen, expand Microsoft SQL Servers/SQL Server Group/<the file server's network name>/Management.

3.        Right-click Backup and select Backup a Database.

4.        Add a new backup device and select the options that best suite your needs.

5.        To schedule a backup, select Schedule and click '�'.

6.        Schedule the backup to occur on a regular basis, preferably each day.

7.        Save your changes and close SQL Server Enterprise Manager.

Archiving Data

Since most backup methods require a degree of user input, Aloha Technologies uses 'data archiving' as a secondary means to backup the most important data.� This does not replace the primary backup procedure, but instead, acts as a secondary backup to ensure the availability of data in an emergency.� Archiving also enables an easy way to restore purged dated folders in the event they are needed.

Archiving uses third-party compression software such as WinZip^� or PKZIP^� to compress data on to a separate hard drive or a dedicated partition on the local hard drive.� For example, you might consider creating separate partitions as explained in document AKBID1183.� Use the Winhook batch file (refer to document AKBID1028) to enable the archiving process on a regular basis.� Although other options are available to start the archiving process, such as the Windows Schedule Service (refer to document AKBID1047) or Windows Task Scheduler, only Winhook includes the dated folder's label in the command line for reference in the batch file.� The archiving commands in the Winhook batch file look similar to the following:

PKZIP.EXE E:\ALOHAZIP\%1.ZIP %IBERDIR%\%1\*.*

PKZIP.EXE E:\ALOHAZIP\EDC\EDCINI.ZIP %IBERDIR%\EDC\EDC.INI

PKZIP.EXE E:\ALOHAZIP\EDC\%1.ZIP %IBERDIR%\EDC\<processor folder>\%1.*

If the site is using Aloha application software BackOffice products, add them to the batch file as well.

Archiving not only ensures data recovery, but it also enables you to maintain the space on the Aloha application software partition.� If the dated folders are safely archived, users can delete older dated folders from the Aloha application software partition without the worry of lost data.� With archiving and the dated folder purge feature in the Aloha application software (refer to document AKBID1193), the Aloha application software partition should never run out of hard drive space.� In case the user requires the purged dated folders for reporting, it is easy to temporarily restore them from the archives and report the information.

Extended Information

No information.

Caveats

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

In cases where the data is recoverable from the FOH terminals, it is important not to let default data installed by the Aloha installation CD overwrite the information on the FOH terminals when the file server is recovered after installing the Aloha application software software.

============================================================================

See also:

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1027 Windows NT/Windows 2000 Automatic Backup

AKBID1028 Winhook

AKBID1047 Microsoft Windows Schedule Service

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1193 Purging Dated Folders in Aloha Manager

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1148

�

Aloha Overtime Calculations

Aloha Overtime Calculations

============================================================================

AKBID1149

Created: 28 June 2000

Updated: 3 June 2003

Reviewed: 16 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

Subject: Aloha Application Software Overtime Calculations

============================================================================

Summary

The ALOHA^� application software supports three methods of overtime: Weekly Overtime, Daily Overtime, and Extended Daily Overtime.� This document explains how the Aloha application software calculates overtime (regardless of the overtime method), but this document does not explain how to configure each method of overtime.� For more information on configuring each method of overtime, refer to the Aloha QuickService or TableService User Manual.

The examples in this document use $2.13 per hour for the minimum tipped wage and $5.15 per hour for the standard minimum wage.� These figures are not intended to represent the actual minimum wages in your area or locale.� Consult your local, state, and federal government guidelines for the true minimum wages in your area or locale.

Information

Overtime Multiplier

The term 'overtime multiplier' in this document refers to the overtime rate minus one.� For example, if the overtime rate is 1.5, the overtime multiplier is .5.� If the overtime rate is 2.0, the overtime multiplier is 1.0.� This is required since the Aloha application software figures the overtime pay separately from the total hours multiplied by the regular pay.�

When you configure your overtime rate in the Aloha application software, enter the true rate.� For example, if your overtime rate is 1.5, then enter 1.5, not the .5 overtime multiplier rate.� When the Aloha application software calculates the overtime multiplier, it assumes the user has entered the true overtime rate.

For example, an employee makes $2.13 per hour, works 45 hours (where 5 hours is overtime and the overtime rate is 1.5), and the minimum wage is set to $5.15 per hour.� The Aloha application software does not use (40 * $2.13) + (5 * ($2.13 * 1.5)) because the overtime rate must be figured using either the hourly wage or the minimum wage, whichever is higher, per the 'Tip Credit' guidelines set by the United States Department of Labor.� Instead, the Aloha application software uses (45 * $2.13) + (5 * ($5.15 * .5)).

In order to understand Aloha application software overtime calculations, you must understand that the latter method is used and that the Aloha application software uses the minimum wage for overtime calculations if the hourly rate is less than the minimum wage.

In another example, an employee makes $6.50 per hour, works 45 hours (where 5 hours is overtime and the overtime rate is 1.5), and the minimum wage is set to $5.15 per hour (as defined in Maintenance/Store Settings/Labor/Employee Settings).� In this case, the Aloha application software uses (45 * $6.50) + (5 * ($6.50 * .5)) since the hourly wage is higher than the minimum wage.

Overtime Pay Rate Calculation Options

You can choose to calculate overtime pay rates using an average pay rate (described later) or use the current shift rate.� To select a method, open Aloha Manager, select Maintenance/Store Settings/Labor/ Clock In/Out subtab.

Regardless of the method, the overtime rate is compared to the minimum wage defined in Maintenance/Store Settings/Labor/Employee Settings.� If the true overtime rate is less than the minimum wage, the minimum wage is used to calculate the overtime rate instead of the true overtime rate.

Average Pay Rate

Since employees might use multiple job codes with multiple pay rates throughout the pay period, overtime calculations (extended, daily, or weekly) can use an average pay rate calculated by the total hours divided by the total pay.� This is referred to as the 'average pay rate' in this document.� For example, if an employee works 10 regular hours at $3.25 per hour and 5 regular hours at $4.50 per hour, the average pay rate is ((10 * $3.25) + (5 * $4.50))/15 or $3.67 per hour.� This average pay rate is used in the overtime calculations described previously in this document, unless it is less than the minimum wage, in which the minimum wage would be used.

Average pay rates are calculated with each shift and include the pay from the current shift.

Additional Rules

Hours are always calculated with a single overtime rate, never with multiple overtime rates.� The hierarchy for rate selection is extended overtime, daily overtime, and weekly overtime.� In other words, if an hour qualifies for both daily overtime and weekly overtime, daily overtime is applied to the hour.

Unpaid breaks are subtracted from the time used in overtime calculations.� Paid breaks are included in the time used in overtime calculations.

All overtime hours, whether weekly, daily, or extended daily, are figured using the same algorithm.

The overtime pay rate listed in Aloha application software reports is the total overtime pay divided by the total overtime hours.

Calculations for Tipped Employees

To figure the total overtime dollar amount paid above the regular wages for the total number of hours, the Aloha application software uses overtime hours * (average pay rate * overtime multiplier).� For example, an employee works 45 hours in a week (five hours overtime with an overtime rate of 1.5) under multiple job codes with multiple pay rates.� The employee earns $191.25 in total pay, including overtime.� The average pay rate is $191.25/45 or $4.25 per hour.� In this case, the minimum wage ($5.15 per hour) is higher than $4.25 per hour, so the calculation for the total overtime dollar amount paid beyond the regular pay for 45 hours is 5 * ($5.15 * .5) or $12.85.� This enforces the 'Tip Credit' guidelines set by the United States Department of Labor

To find the overtime pay rate in the above example, the Aloha application software uses the regular pay rate plus the overtime pay rate.� In the above example, the average regular pay rate for all 45 hours without overtime is total pay � total overtime (beyond the regular wages paid for the total hours) / the total hours worked.� In this case, it is (191.25 � 12.85) / 45 or $3.96 per hour.� In the above example, the average overtime pay rate is average pay rate * overtime multiplier.� In this case, it is $4.25 * .5, or $2.125.� So the overtime pay rate is $3.96 + $2.125 or $6.085 per hour.

Calculations for Non-Tipped Employees

To figure the total overtime dollar amount paid above the regular wages for the total number of hours, the Aloha application software uses overtime hours * (average pay rate * overtime multiplier).� For example, an employee works 45 hours in a week (five hours overtime with an overtime rate of 1.5) under multiple job codes with multiple pay rates.� The employee earns $321.65 in total pay, including overtime.� The average pay rate is $321.65/45 or $7.14 per hour.� In this case, the minimum wage ($5.15 per hour) is not higher than $7.14 per hour, so the calculation for the total overtime dollar amount paid beyond the regular pay for 45 hours is 5 * ($7.14 * .5) or $17.85.

To find the overtime pay rate in the above example, the Aloha application software uses the regular pay rate plus the overtime pay rate.� In the above example, the average regular pay rate for all 45 hours without overtime is total pay � total overtime (beyond the regular wages paid for the total hours) / the total hours worked.� In this case, it is (321.65 � 17.85) / 45 or $6.75 per hour.� In the above example, the average overtime pay rate is average pay rate * overtime multiplier.� In this case, it is $7.14 * .5, or $3.57.� So the overtime pay rate is $6.75 + $3.57 or $10.32 per hour.

Extended Information

Aloha Technologies uses the standards set by the United States Department of Labor to develop the above methods for overtime calculation.� Please refer to the Department of Labor web page at http://www.dol.gov for more information.

Caveats

The examples in this document use $2.13 per hour for the minimum tipped wage and $5.15 per hour for the standard minimum wage.� These figures are not intended to represent the actual minimum wages in your area or locale.� Consult your local, state, and federal government guidelines for the true minimum wages in your area or locale.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1149 ot over time

�

Using LMHOSTS with a SuperSite

Using LMHOSTS with a SuperSite

============================================================================

AKBID1150

Created: 10 July 2000

Updated: 19 July 2002

Reviewed: 6 October 2003

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Using LMHOSTS for SuperSite Name Resolution

============================================================================

Summary

ALOHA^� application software SuperSites that reside on a segmented network require network name resolution capabilities beyond that provided by NetBIOS in order for Front-of-House (FOH) terminals and Back-of-House (BOH) file servers to achieve network access to each other across the different subnets.� One name resolution method is the LAN Manager Hosts (LMHOSTS) file.� This document explains the advantages of LMHOSTS, how to create the LMHOSTS file, and how to import the LMHOSTS file into Microsoft^� Windows^�.

Information

TCP/IP requires name resolution to interact with other computers using network names in place of TCP/IP addresses.� Name resolution matches a TCP/IP address to a network name.� In a non-SuperSite, all FOH terminals reside on the same TCP/IP subnet, so standard NetBIOS name resolution fulfils the name resolution requirements.� Since many SuperSites use segmented networks, or subnets, and NetBIOS only resolves names in the local subnet, another method of name resolution is required.� The preferred name resolution method with SuperSites is LMHOSTS.

LMHOSTS resolves network names using a text file on the local computer that lists the TCP/IP address and network name of the file servers and terminals.� LMHOSTS is advantageous over other name resolution methods in that it does not require a separate host or server to resolve and distribute network names.� For example, Domain Naming Service (DNS) requires a DNS host on the network, but if it does not exists because of hardware or network failure, the file servers and terminals will not have access to name resolution.� Since the LMHOSTS list is stored locally, a host is not necessary.� LMHOSTS is virtually infallible if you have configured it properly.

Once you create an LMHOSTS file on the SuperSite file server, you can distribute new and updated versions of the LMHOSTS file to the FOH terminals using the Aloha application software's native BIN propagation and the SuperSite's IBERCFG.BAT (refer to document AKBID1118).� You must manually distribute the LMHOSTS file to the other BOH file servers, such as Electronic Data Capture (EDC) or Property Management System (PMS) file servers

Creating an LMHOSTS File

Although the terminals only require name resolution to resolve the BOH file server names, the file servers still require name resolution for all of the FOH terminals.� Instead of using separate LMHOSTS files for the file servers and the terminals, use a single LMHOSTS file for the entire SuperSite.� This way you only have to maintain a single LMHOSTS file.

In order to automatically distribute the LMHOSTS file out to each terminal, create the LMHOSTS file in the Aloha application software BIN folder so you can take advantage of the Aloha application software's automatic propagation of the BIN folder contents.� Thus, when you update the LMHOSTS file, the Aloha application software automatically updates the file in the BIN folder on each terminal as it does with the rest of the BIN folder's contents.

Create a new file in the BIN folder on the file server and label it 'LMHOSTS', without a file extension (for example, D:\ALOHA\BIN\LMHOSTS).

�

Create a line in the file for each file server and each terminal that includes the TCP/IP address and network name of each computer (separated by a space or tab).� The file contents look similar to the following:

10.100.100.100 ALOHABOH #PRE

10.100.100.101 ALOHAEDC #PRE

10.100.100.102 ALOHAPMS #PRE

10.100.101.1 BAR1

10.100.101.2 BAR2

10.100.102.1 PATIO3

10.100.102.2 PATIO4

10.100.102.3 PATIO5

10.100.103.1 DINING6

10.100.103.2 DINING7

Note the use of ' #PRE' (must be uppercase and include a space before the pound symbol) after each file server's name.� In the hierarchy of name resolution, LMHOSTS resolution is the last method attempted by Windows.� In some cases, the Aloha application software might not allow enough time for Windows to process the LMHOSTS file and resolve the network name.� In this case, the Aloha application software can timeout and assume the target computer does not exist on the network.� Since the file server's names have not been resolved, the terminal cannot access the file servers to update the MASTER file, check for the existence of a REFRESH flag, or process EDC or PMS requests.� '#PRE' instructs Windows to immediately load the specified line of the LMHOSTS file into memory (NetBIOS cache).� Windows attempts to resolve these addresses first, thus the file server's names have been resolved in time for the Aloha application software to access the file servers.� '#PRE' is not required for terminals since the store's terminals reside on the same subnet and do not require LMHOSTS for name resolution.

Distributing the LMHOSTS file from the BIN Folder

Failure to properly import the LMHOSTS file into the file servers or terminals can result in improper operation of the Aloha application software.

You need to copy the LMHOSTS file from the BIN folder to the proper location in order for Windows to automatically read it.� By default, Windows 95, Windows 98, and Windows Millennium Edition (Me) look for the LMHOSTS file in the Windows folder (for example, C:\WINDOWS\LMHOSTS).� Windows NT^�, Windows 2000, and Windows XP look for the LMHOSTS file in the in Windows \SYSTEM32\DRIVERS\ETC folder (for example, C:\WINNT\SYSTEM32\DRIVERS\ETC\LMHOSTS).

For FOH terminals, you can copy the LMHOSTS file to the proper location using the SuperSite's IBERCFG.BAT.� If the FOH terminals are using Windows 95, Windows 98, or Windows Me, add the following line to the end of the IBERCFG.BAT to copy the LMHOSTS file to the Windows folder:

COPY %LOCALDIR%\BIN\LMHOSTS C:\WINDOWS\LMHOSTS

Windows 95, Windows 98 read the LMHOSTS file when Windows initializes.� Since the IBERCFG.BAT is processed prior to this, additional restarts are not required for Windows to read the new LMHOSTS file.� Since Windows Me processes the LMHOSTS file after Windows has initialized, it will not read the new LMHOSTS file until Windows restarts, whether that occurs manually or during the next system refresh or End-of-Day (EOD).

If the FOH terminals are using Windows NT, Windows 2000, or Windows XP, ensure that 'Enable LMHOSTS lookup' is enabled in the TCP/IP WINS properties and add the following lines to the end of the IBERCFG.BAT in order to copy the LMHOSTS file to the Windows \SYSTEM32\DRIVERS\ETC folder:

COPY %LOCALDIR%\BIN\LMHOSTS C:\WINNT\SYSTEM32\DRIVERS\ETC\LMHOSTS

NBTSTAT -R

Since Windows NT, Windows 2000, and Windows XP process the LMHOSTS file after Windows has initialized, it will not read the new LMHOSTS file unless you use the 'NBTSTAT �R' (the 'R' must be uppercase) command to tell it to do so.

To update the LMHOSTS file on your file servers, manually copy the LMHOSTS file from the BIN folder to the Windows \SYSTEM32\DRIVERS\ETC folder and manually run the 'NBTSTAT �R' command.

Extended Information

In some cases, the HOSTS file has interfered with the LMHOSTS file and has hampered proper name resolution.� If this occurs, either clear the contents of the HOSTS file or edit the IBERCFG.BAT to copy the LMHOSTS file in the BIN folder to both the LMHOSTS and HOSTS files.� For example:

COPY %LOCALDIR%\BIN\LMHOSTS C:\WINDOWS\LMHOSTS

COPY %LOCALDIR%\BIN\LMHOSTS C:\WINDOWS\HOSTS

Caveats

Failure to properly import the LMHOSTS file into the file servers or terminals can result in improper operation of the Aloha application software.

============================================================================

See also:

AKBID1118 SuperSite IBERCFG.BAT

AKBID1199 Configuring a SuperSite FOH Terminal

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1150

�

Remote BackOffice Inventory Control Workstation

Remote BackOffice Inventory Control Workstation

============================================================================

AKBID1151

Created: 10 July 2000

Updated: 28 January 2002

Reviewed: 17 February 2004

Microsoft Windows Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

Subject: Configuring Remote BackOffice Inventory Control Workstations

============================================================================

Summary

You can configure the ALOHA^� application software BackOffice Inventory Control application (versions 1.01 and higher) on remote workstations in order to access, edit, and report the application's data.� The BackOffice network security option enables remote use without requiring a separate security key for each remote workstation.

Information

Remote BackOffice applications require TCP/IP (refer to document AKBID1063) to communicate between the file server and the remote workstation.� You must configure TCP/IP as lana zero (refer to document AKBID1018)

Licenses

You must license the BackOffice application for enough users to not effect the operation of the POS interface with the BackOffice application.� Each workstation concurrently connected to the BackOffice application must have a license.� Although each component within the BackOffice application does not require a separate license, each workstation concurrently and actively using the BackOffice application does require a license.

For example, the POS interface and the BackOffice Main Menu on the file server only require a single license, even if they are running at the same time.� Since you must keep the POS interface functional to ensure communication with the Front-of-House (FOH) terminals, the file server requires a license that should not be shared.� Extra licenses are required for remote workstations.�

Each remote workstation does not require a separate license if they are connected at separate times.� For example, three licenses allow the file server and any two remote workstations to connect to the BackOffice application.� A different remote workstation may connect at a later time after one of the previous two workstations disconnects.

It is very important not to let the remote workstations interfere with the POS interfaces ability to function properly.

Install Inventory Control on the File Server

Install the Inventory Control software on the file server using the Aloha Installation CD and configure BackOffice License Manager.�

Do not select 'Use Network Security' in BackOffice License Manager.

Install Inventory Control on the Remote Workstation

Before installing the Inventory Control software on the remote workstation, ensure the remote workstation has access to a shared resource on the file server that contains the Inventory Control database.� This is usually the BOOTDRV share if the file server's BackOffice folder resides in the Aloha application software folder.

Install the Inventory Control software on the remote workstation using the Aloha Installation CD.� Configure BackOffice License Manager by selecting 'Use Network Security' in BackOffice License Manager, and enter the file server name in the 'Remote Server Name' text box.�

Configure Databases on the Remote Computer

The remote workstation must have access to the following databases and files in the \BackOffice\Database folder on the file server: FDatas.ini, FDatas.mdb, and FDatacb.mdb.� Use the BackOffice Database Utilities to link the 'Server Databases' (not the 'Client Databases') to the file server.� For example, set the Server Database Location on the remote workstation to \\Alohaboh\Bootdrv\BackOffice\

Database.

Start the BackOffice Inventory Control Menu using the shortcut in the Microsoft^� Windows^� start menu created by the BackOffice installation program.

Troubleshooting

Three common problems using remote BackOffice workstations are the TCP/IP settings, share access, and licenses.

The file server and remote workstations must communicate with TCP/IP, and you must assign TCP/IP to lana zero on the file server and remote workstations.� Refer to document AKBID1063 for more information on TCP/IP and document AKBID1018 for more information on network lana numbers.

If the remote workstation cannot access the databases on the file server, it will display the following error:

'MSDOS Command Share.exe is not loaded or functioning correctly.�� Application requires Share be loaded and executed correctly'

Verify if the share on the file server enables the user full access to the files and if the Server Database variable in BackOffice Database Utilities is set correctly.� The share must allow the remote workstation full read and write access to the database files.

The BackOffice application must have enough licenses to allow the required remote connections plus the local connection (the POS interface).� If there are no open licenses available, the remote workstation will not be able to start the application.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha BackOffice Inventory User Manual

AKBID1018 Network Lana Numbers

AKBID1063 TCP/IP

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1151

�

Remote BackOffice Advanced Reservations Workstation

Remote BackOffice Advanced Reservations Workstation

============================================================================

AKBID1152

Created: 16 June 2000

Updated: 24 October 2001

Reviewed: 16 February 2004

Microsoft Windows Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

Subject: Configuring Remote BackOffice Advanced Reservations Workstations

============================================================================

Summary

Users of the ALOHA^� application software BackOffice Advanced Reservations application (version 1.10 and higher) can configure remote workstations to access, edit, and report the application's data.� The BackOffice network security option enables remote use without requiring a separate security key for each remote workstation.

Information

Remote BackOffice applications require TCP/IP (refer to document AKBID1063) to communicate between the file server and the remote workstation.� You must configure TCP/IP as lana zero (refer to document AKBID1018)

Licenses

You must license the BackOffice application for enough users to not effect the operation of the POS interface with the BackOffice application.� Each workstation concurrently connected to the BackOffice application must have a license.� Although each component within the BackOffice application does not require a separate license, each workstation concurrently and actively using the BackOffice application does require a license.

For example, the POS interface and the BackOffice Main Menu on the file server only require a single license, even if they are running at the same time.� Since the POS interface must always be functional to ensure communication with the Front-of-House (FOH) terminals, the file server requires a license that should not be shared.� Extra licenses are required for remote workstations.�

Each remote workstation does not require a separate license if they are connected at separate times.� For example, three licenses allow the file server and any two remote workstations to connect to the BackOffice application.� A different remote workstation may connect at a later time after one of the previous two workstations disconnects.

It is very important not to let the remote workstations interfere with the POS interfaces ability to function properly.

Install Advanced Reservations on the File Server

Install the Advanced Reservations software on the file server using the Aloha Installation CD and configure BackOffice License Manager.�

Do not select 'Use Network Security' in BackOffice License Manager.

Install Advanced Reservations on the Remote Workstation

Before installing the Advanced Reservations software on the remote workstation, ensure the remote workstation has access to a shared resource on the file server that contains the Advanced Reservations database.� This is usually the BOOTDRV share if the file server's BackOffice folder resides in the Aloha application software folder.

Install the Advanced Reservations software on the remote workstation using the Aloha Installation CD.� Configure BackOffice License Manager by selecting 'Use Network Security' in BackOffice License Manager and enter the file server name in the 'Remote Server Name' text box.�

Configure Databases on the Remote Computer

The remote workstation must have access to the following databases and files in the \BACKOFFICE\AD folder on the file server: DBENGINE.INI, AD.INI, ADDATA.MDB, and ADDATAB.MDB.� Create the ADDATAPATH system environment variable on each remote workstation to define the location of the \BACKOFFICE\DS folder on the file server.� For example, if the BackOffice folder resides within the Aloha application software folder on the file server, the variable may appear as the following:

SET ADDATAPATH=\\ALOHABOH\BOOTDRV\BACKOF~1\AD

Note the use of the '8.3' version of the BackOffice folder's name.

Start the BackOffice Advanced Reservations Menu using the shortcut in the Microsoft^� Windows^� start menu created by the BackOffice installation program.

Troubleshooting

Three common problems using remote BackOffice workstations are the TCP/IP settings, share access, and licenses.

The file server and remote workstations must communicate with TCP/IP, and TCP/IP must be assigned to lana zero on the file server and remote workstations.� Refer to document AKBID1063 for more information on TCP/IP and document AKBID1018 for more information on network lana numbers.

If the remote workstation can not access the databases on the file server, it will display the following error:

'MSDOS Command Share.exe is not loaded or functioning correctly.�� Application requires Share be loaded and executed correctly'

Verify if the share on the file server enables the user full access to the files and if the ADDATAPATH variable is set correctly.� The share must enable the remote workstation full read and write access to the database files.

The BackOffice application must have enough licenses to allow the required remote connections plus the local connection (the POS interface).� If there are no open licenses available, the remote workstation will not be able to start the application.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha BackOffice Advanced Reservations Buyer User Manual

AKBID1018 Network Lana Numbers

AKBID1063 TCP/IP

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1152

�

Types of Transaction Logs in Dated Folders

Types of Transaction Logs in Dated Folders

============================================================================

AKBID1153

Created: 11 July 2000

Updated: 29 August 2002

Reviewed: 10 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Types of Transaction Logs in Dated Folders

============================================================================

Summary

Besides the TRANS.LOG (refer to document AKBID1154), ALOHA^� application software dated folders might also have other versions of the transaction log.� These other logs are labeled TRANSCnn.LOG, TRANSVnn.LOG, TRNSnnnn.LOG, and ORIG.LOG.� This document explains the reason for each of these files, and when you can remove them to conserve space.

Information

TRANSCnn.LOG

TRANSCnn.LOG (where nn is the version number) appears when the 24-hour operations are enabled in the Aloha application software.� The log contains 'carry-over' transactions from the End-of-Day (EOD) process (refer to document AKBID1015), and the log is created in the dated folder during the Grind process (refer to document AKBID1016).

TRANSCnn.LOG files are not required by the Aloha application software, but serve a purpose in troubleshooting.� If Aloha application software reports function properly, you can delete the TRANSCnn.LOG files.� If you upgrade the Aloha application software, keep the TRANSCnn.LOG files until all post-upgrade testing has proved successful.

The TRANSCnn.LOG is no longer created in versions 5.0x and higher.�

TRANSVnn.LOG and TRNSnnnn.LOG

TRANSVnn.LOG and TRNSnnnn.LOG (where nn or nnnn is the version number) are the original versions of converted transaction logs that are created by the Grind process if the version of GRIND.EXE or GRINDQ.EXE is different than the version of IBER.EXE or IBERQS.EXE.

TRANSVnn.LOG files are created by versions 4.4x and lower, and TRNSnnnn.LOG files are created by versions 5.0x through 5.239.

TRANSVnn.LOG and TRNSnnnn.LOG files are not required by the Aloha application software, but serve a purpose in troubleshooting.� If Aloha application software reports function properly, you can delete the TRANSVnn.LOG and TRNSnnnn.LOG files.� If you upgrade the Aloha application software, keep the TRANSVnn.LOG and TRNSnnnn.LOG files until all post-upgrade testing has proved successful.

ORIG.LOG

In versions 5.2.4.x and higher, ORIG.LOG is the original version of a transaction log that has been converted to a newer version by GRIND.EXE or GRINDQ.EXE.� TRANS.LOG is the converted version of the log.

In order to conserve disk space, Aloha application software versions 5.2.4.x and higher no longer create TRNSnnnn.LOG files.

ORIG.LOG files are not required by the Aloha application software, but serve a purpose in troubleshooting.� If Aloha application software reports function properly, you can delete the ORIG.LOG files.� If you upgrade the Aloha application software, keep the ORIG.LOG files until all post-upgrade testing has proved successful.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1015 EOD Process and Errors

AKBID1016 Grind Process and Errors

AKBID1154 Aloha Application Software Transaction Log

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1153 subdirectory transv trns

�

Aloha Application Software Transaction Log

Aloha Application Software Transaction Log

============================================================================

AKBID1154

Created: 17 July 2000

Updated: 16 February 2004

Reviewed: 16 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: The Aloha Application Software Transaction Log

============================================================================

Summary

The Trans.log (transaction log) is an important part of the ALOHA^� application software because it records business day's sales and other Front-of-House (FOH) transactions.� It is important to understand the transaction log's role in order to properly support the Aloha application software.

Information

The transaction log is a log file that stores the sales and other FOH transactions for each Date-of-Business (DOB).� The current day's sales and transactions are recorded in the transaction log located in the Data folder.� The sales and transactions from previous days are stored in the transaction log located in the day's dated folder.

Since the transaction log contains the source information from which all sales information and reports are directly or indirectly taken, it is very important that the transaction log for each day is not lost, deleted, or corrupted.� The only way to reproduce a transaction log is to recreate the DOB by re-entering the day's transactions from the FOH terminals.

Although the FOH terminals primarily use the transaction log on the BOH file server, the transaction log is synchronized to the Data folder on each FOH terminal every three to ten seconds.� In case the file server or network fails requiring one or more terminals to become a temporary file server, the current transaction log is available to continue business.� When the file server is recovered, the transaction log from the terminal (acting as the file server) is copied to the BOH file server.� This means that during normal business operation, the sizes of the transaction log on the file server and the transaction log on the FOH terminals may not exactly match unless there were no new transactions since the last synchronization.

Grind Files

Since the transaction log is in a proprietary binary format (for security reasons), you cannot view or edit it.� To make the information available for reporting, the Aloha application software uses the Grind process (refer to document AKBID1016) to convert the log into standard .dbf files and, if enabled, a relational database (RDB).� You can use the grind files to create your own reports based on the data gathered from the transaction log.

With the exception of check and checkout reprints and the Audit report (both of which use the Reprint.exe or Reprintq.exe), all Aloha application software Back-of-House (BOH) reports use the grind files to gather information.� Reprint.exe and Reprintq.exe gather information directly from the transaction log.

Mirror Logs and Backup Logs

Ctlsvr.exe (Control Server) maintains a mirrored copy of the current transaction log in the Data folder on the file server, named Mirror.log.� Control Server performs the following every 20 seconds to update the Mirror.log (except when in SuperSite mode):

-          If an Eod or Stop file exists, nothing is done since the End-of-Day (EOD) process is currently active.

-          If the Mirror.log length is greater than the transaction log length, then there has been an unexpected occurrence.� Control Server copies the current Mirror.log to the file server's Tmp folder, renames it Mirnnnn.log (where nnnn is a consecutive number starting with 0000), and deletes the current Mirror.log in the Data folder.

-          If the current transaction log length is greater than the Mirror.log length, then Control Server copies the difference from the transaction log to the Mirror.log.

In the case of a lost or corrupted transaction log, a mirror log may be available for replacement, although since it is a mirror of the transaction log, it may contain the same corruption.

The FOH deletes the Mirror.log during the EOD process before it is copied to the dated folder.

If a FOH terminal detects log corruption, it creates a backup log named Backnnnn.log, where nnnn is a consecutive number starting with 0000.

When considering whether to restore a backup log, you must check three things:

Read the FOH and BOH debouts to find out why the backup log was created.� The debouts always indicate the reason the backup was made.

Check the date and time of the backup log for reasonability.

Check the size of the backup log for reasonability.

If you are restoring a backup log, stop or shutdown the FOH, backup the original log in the DATA folder on the server, replace the original log, and start the FOH.� If needed, the original log can be restored again the same way.

Transaction Log Corruption

Transaction log corruption is caused be several factors, including a faulty network, power, or hardware.� In case of transaction log corruption, use the Fixlog.exe utility.� Fixlog.exe comes in several versions to compensate for differing log formats between the different versions of the Aloha application software.� Refer to document AKBID1012 for more information about using Fixlog.exe.

Another common cause of transaction log corruption is file system corruption on the hard disk, especially cross-linked files.� Always run Chkdsk.exe /f when transaction log corruption occurs.

Incorrect date settings (specifically, the year) can also lead the Aloha application software to incorrectly assume there is transaction log corruption at position zero.� If the year of the log is less than or equal to 1993 or is greater than the current year on the terminal, the Aloha application software concludes that something is wrong with the log (it should not be getting 'logs from the future').

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1016 Grind Process and Errors

AKBID1157 Aloha Application Software Printer Logs

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1154 trans.log corrupt at position 0

�

Using 4.2x Dated Folders in 5.0x

Using 4.2x Dated Folders in 5.0x

============================================================================

AKBID1155

Created: 26 July 2000

Updated: 4 May 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x

Subject: Using Version 4.2x Dated Folders in Versions 5.0x

============================================================================

Summary

After you have upgraded the ALOHA^� application software from version 4.2x to version 5.0x, you can view Back-of-House reports as you have previously, but reprinting guests checks, reprinting employee checkouts, viewing audit reports or regrinding dated folders requires converting the database and TRANS.LOG (transaction log) to the current version.

You do not need to regrind or update 4.2x dated folders to view reports in 5.0x.

Information

Reprinting Guest Checks and Employee Checkouts

REPRINT.EXE and REPRINTQ.EXE, which are used to reprint guest checks or employee checkouts, read data directly from the transaction log instead of the grind files.� In order to read the transaction log in a dated folder created by version 4.2x, REPRINT.EXE or REPRINTQ.EXE update the data files and transaction log in the dated folders to the current version.

The upgrade process is automated and only requires you to click 'Yes' when prompted for permission to upgrade.� After the database upgrade is completed by DBUP2.EXE (refer to document AKBID1067), the grind process (refer to document AKBID1016) automatically converts the transaction log to the current version.

After the conversion is complete, you can reprint guests checks or employee checkouts as you normally would.

Once the dated folder is upgraded, users will not experience the upgrade process again for the dated folder until a newer version of the Aloha application software is installed.

Audit Report

The Audit report is part of REPRINT.EXE and REPRINTQ.EXE, and it performs the same way as described above for reprinting guest checks or employee checkouts.

Regrinding Dated Folders

If you need to regrind a dated folder, you can use either use the Regrind Subdirectories utility in Aloha Manager or you can manually grind each dated folder from a command line.

If you are using the Regrind Subdirectories utility, all database and transaction log conversions are performed automatically without any user input. �Mark the selected dates to regrind, set Active to 'On', set Num Grinds to '1', and click Done.� Refer to the Aloha QuickService or TableService User Manual for more information on the Regrind Subdirectories utility.

If you are manually regrinding dated folders by initializing the grind process from a command line or by deleting the GNDDBF30.XXX file from the dated folder, you must first update the database using DBCONFIG.EXE.� To start DBCONFIG.EXE, open Aloha Manager and select Utilities/Database Upgrade, or double-click DBCONFIG.EXE in the BIN folder.� Set the Input and Output folders to the dated folder's location, select the following, and click run:

1.        DBF Files Only (if not using an RDB)

2.        Attended

3.        Debug

4.        Force Upgrade

Once the database is upgraded, initialize the grind process from a command line or delete the GNDDBF30.XXX file from the dated folder.� Refer to document AKBID1016 for more information.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1016 Grind Process and Errors

AKBID1067 DBUP.EXE and DBCONFIG.EXE

AKBID1153 Types of Transaction Logs in Dated Folders

AKBID1160 Manually Upgrading Configuration Files in Aloha Manager

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1155 subdirectories subdirectory

�

Using Windows Printers Between Stores in SuperSites

Using Windows Printers Between Stores in SuperSites

============================================================================

AKBID1156

Created: 13 July 2000

Updated: 18 June 2001

Reviewed: 29 January 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Using Windows-based Receipt and Chit Printers Between Stores in SuperSites

============================================================================

Summary

ALOHA^� application software SuperSites must use Microsoft^� Windows^�-based printers to share a printer between two or more stores.� This is useful when two or more stores use a common kitchen or bar printer.� This document explains the setup required for printing receipts or chits between stores using Windows-based printers.

This document supplements document AKBID1026.� Refer to document AKBID1026 for more information regarding printer setup, Aloha application software settings, and troubleshooting.

Information

SuperSite Front-of-House (FOH) terminals can only use printers defined in the Aloha application software configuration as attached to a terminal in the local store.� For this reason, you must define the Windows-based printer in the Aloha application software as physically attached to a terminal in each store, regardless of the printer's true location.� Since the printer's true location, as defined on the Windows-level as a local or network printer, is masked from the Aloha application software, it is easy to 'fool' the Aloha application software into thinking the printer is a local printer.

In Aloha versions 5.007 through 5.026, you may have to disable stand-alone chit printing (part of the Aloha application software fault tolerance capabilities) in order for the functionality described in this document to function properly.� To disable stand-alone chit printing, edit the ALOHA.INI in the Aloha application software NEWDATA folder, set the DISABLESTANDALONECHITPRINT variable to TRUE (for example, DISABLESTANDALONECHITPRINT=TRUE) and refresh the system.

Setup the Physical Printer in Windows

Attach the printer to a FOH terminal (or a dedicated print server), and define it as a local printer in Windows.� Share the printer so it is accessible to the FOH terminals in all of the stores accessing the printer.�

Refer to document AKBID1026 for more information.

Setup the Printer in Each Store

Select a FOH terminal in each store that will be using the printer, and set the printer up in Windows as a network printer.� Refer to document AKBID1026 for more information.

In the Aloha application software Back-of-House (BOH), define the network printer in each store (as setup above) as if it was physically attached to the selected terminal in each store.� Although the printer is actually a network printer, Windows masks this from the Aloha application software, so it can be considered a local printer in the Aloha application software.

Edit the printer settings in the BOH as described in document AKBID1026.

Setup Printer Reroutes

Since each store will use a different printer (as far as the Aloha application software is concerned) to access the same physical printer, you must setup printer reroute events for each store to reroute from a generic printer group to a real printer group.

For example, if each store prints chits for bar drinks to a shared service bar printer, perform the following:

1.        Create a printer group labeled 'Mock Bar' without any printers in it.�

2.        Create a printer group for each store labeled 'Bar n' where n is the store ID.� Place the store's local bar printer in each store's bar printer group.

3.        Create a 'Reroute Printer Group' event for each store that reroutes the 'Mock Bar' printer group to the 'Bar n' printer group, where n is the store ID.

4.        Refresh the system.

Extended Information

No information.

Caveats

In Aloha versions 5.007 through 5.026, you may have to disable stand-alone chit printing (part of the Aloha application software fault tolerance capabilities) in order for the functionality described in this document to function properly.� To disable stand-alone chit printing, edit the ALOHA.INI in the Aloha application software NEWDATA folder, set the DISABLESTANDALONECHITPRINT variable to TRUE (for example, DISABLESTANDALONECHITPRINT=TRUE) and refresh the system.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1026 Using Windows-based Printers with Aloha

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1156 across multiple

�

Aloha Application Software Printer Logs

Aloha Application Software Printer Logs

============================================================================

AKBID1157

Created: 18 July 2000

Updated: 21 December 2000

Reviewed: 10 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: The Aloha Application Software Printer Logs

============================================================================

Summary

The ALOHA^� application software uses printer logs to track data sent to receipt and chit printers.� If a printer malfunctions, the Aloha application software uses the information in printer logs to determine if the receipt or chit information has printed properly.� It is important to understand the printer log's role in order to properly support the Aloha application software.

Information

The Aloha application software uses printer logs to verify a receipt or chit has been printed.� Every time a new printer request is processed, the log not only tracks the information printed, but a confirmation from the printer that the information was printed correctly.� This avoids 'losing' receipts or chits even if the terminal reboots unexpectedly.

Printer logs reside in the data folder of the file server (and thus, are propagated to each SERVERCAPABLE terminal's DATA folder).� Refer to document AKBID1107 for more information on SERVERCAPABLE.� The logs are labeled using the PRTnnn.LOG format, where nnn is the printer ID assigned in Maintenance (Aloha versions 3.0x � 4.4x) or Aloha Manager (Aloha versions 5.0x and higher).

The Aloha application software stores printer requests in logs separate from the TRANS.LOG (refer to document AKB1154) because the information contained in the printer logs can be discarded instead of archived in the dated folders during the End-of-Day process (refer to document AKBID1015).� Also, to avoid unnecessary processing, the only terminal that reads a given printer's log is the terminal that is responsible for the printer.

Printer Log Corruption

Printer log corruption is caused be several factors, including a faulty network, power, or hardware.� In case of printer log corruption, users should delete the corrupted log from the DATA folder on the file server and restart the Front-of-House (FOH) terminals.� Although the FIXLOG.EXE utility (refer to document AKBID1012) can be used to fix corrupted printer logs, it is not required since the printer logs do not usually contain significant data.�

Another common cause of printer log corruption is file system corruption on the hard disk, especially cross-linked files.�� Always run ScanDisk or another disk verification utility when printer log corruption occurs.

Viewing Printer Logs

You can view printer logs using the VIEWPRT.EXE utility.� Refer to document AKBID1012 for more information on using the VIEWPRT.EXE utility.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1015 EOD Process and Errors

AKBID1016 Grind Process and Errors

AKBID1107 Aloha Application Software Fault Tolerance Functionality

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1157 corrupt prt

Configuring Windows XP Embedded for Order Entry Terminals

Configuring Windows XP Embedded for Order Entry Terminals

============================================================================

AKBID1158

Created: 8 August 2002

Updated: 8 December 2003

Reviewed: 8 December 2003

Microsoft Windows Versions: XPe

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.211 � 5.3.x

Subject: Configuring Windows XP Embedded for use on FOH Order Entry Terminals

============================================================================

Summary

The ALOHA^� application software Front-of-House (FOH) functions on order-entry terminals using the Microsoft^� Windows^� XP Embedded (XPe) operating system (OS).� This document explains the Windows XPe configuration requirements that are specific to the Aloha application software FOH in order for you to build a Windows XPe runtime image for use with the Aloha application software.

This document is intended to supplement Windows XPe user manuals and usage documentation provided my Microsoft, not replace it.� You must already possess knowledge of using Windows XPe Target Designer and its components prior to using the information in this document.� This document only covers the Aloha-specific portions of creating a Windows XPe client image for use on an Aloha application software FOH order-entry terminal.

All Windows XPe problems reported to the Aloha Customer Service Center (CSC) must be reproducible in standard Windows XP Professional prior to the CSC assisting you with or troubleshooting problems and errors.

Information

Some of the information in this document is primarily intended for users who are creating new Windows XPe runtime images.� If you are using a computer that is pre-installed with a full version of Windows XPe that includes all Windows components, then you can skip past the portions of this document that cover construction of Windows XPe runtime images.� In general, if you are installing the Aloha application software on a computer that is pre-installed with a full version of Windows XPe, then, then you can use the information listed in document AKBID1176 to configure Windows XPe as you would configure a standard version of Windows XP Professional.

The following lists the basic steps for creating a Windows XPe image:

Install Windows XPe Target Designer the file server you will use for creating and storing your XPe images.

Create a System Components File for the target system.

Create a basic XPe image.

Configure your XPe image for use as an Aloha FOH order-entry terminal.

Prepare your target media for the image.

Transfer your image from the Target Designer file server to the target media.

Boot your image for the first time and let it process the First Boot Agent.

Perform additional Windows configuration in order to prepare the applied image for use as an Aloha FOH order-entry terminal.

Install the Aloha FOH application software.

Windows XPe 10 Connection Limit

Windows XPe enables up to 10 concurrent incoming connections, and you cannot increase this amount.� If the site has more than nine FOH terminals, you must consider using Windows 2000 Server on select terminals in order to make them master and/or server-capable.� None of the other terminals can be master and/or server-capable.� Breaking the user limit can disrupt the Aloha application software.� If the site has less than 10 terminals, then you can use Windows XPe on each terminal, and you can configure each terminal as master and/or server-capable.

Install Windows XPe Target Designer

Install and configure Windows XPe Target Designer on the computer that you will use to configure and build Windows XPe runtime images.

Create Hardware and System Components Requirements File

Prior to creating your runtime image in Target Designer, you need to import the hardware and system components from your target system using the TAP.EXE (Target Analyzer Probe), which is provided with the Target Designer utilities.� TAP.EXE creates a .PMQ file, which you can import into Target Designer.

Prior to using TAP.EXE, you must first install and configure either Windows 2000 or Windows XP on your target system.� Once you have installed Windows 2000 or Windows XP, you can run TAP.EXE on the target system to create the .PMQ file.

Prior to using TAP.EXE to create a .PMQ file, verify if your hardware provider has created a .PMQ or .SLD file that they can supply you with.

Create Base Image

To create a new image, start with a blank image in Target Designer, and import your .PMQ file.� In

After importing your .PMQ file, add the 'TCP/IP Networking with File Sharing and Client for MS Networks', 'Standard PC' or 'Advanced Configuration and Power Interface (ACPI) PC', and 'Explorer Shell' components, and perform a dependency check.� The dependency check adds additional network and system components required by the Aloha application software.� This is all that is absolutely required by the Aloha application software.

Aloha Technologies does not recommend including only the required components in an image.� Doing so severely inhibits the ability to configure Windows for the Aloha application software and provide support for the Aloha application software.

The following is a list of components that are either required by the Aloha application software or preferred by Aloha Technologies for configuring Windows for use with the Aloha application software or supporting the Aloha application software:

Component

Settings

Notes

Standard PC or Advanced Configuration and Power Interface (ACPI) PC

Refer to the Workgroup and Computer Name' section of this document for more information.

Required image component.

TCP/IP Networking with File Sharing and Client for MS Networks

Required image component.

Explorer Shell

Required image component.

Task Manager

Enables access to Task Manager

User Account

Refer to the 'Configure User Accounts and Auto Login' section of this document for more information.

Adds users to image.� Add a new instance of this component for each user.

Automatic Logon

Refer to the 'Configure User Accounts and Auto Login' section of this document for more information.

Enables automatic login.

User Interface Core

Show Context Menu on Task bar

Enables you to right-click on the task bar, and select an option from the menu.

User Interface Core

Show Context Menu on Shell folders

Enables you to right-click on folders in Windows Explorer, and select an option from the menu.

User Interface Core

Show All Programs on Start Menu

Enables you to click and view the All Programs option on the Start Menu.

User Interface Core

Show Control Panel on Start Menu

Enables access to the Control Panel from the Start Menu.

User Interface Core

Show My Computer on Start Menu

Enables access to My Computer from the Start Menu.

User Interface Core

Show My Network Places on Start Menu

Enables access to My Network Places from the Start Menu.

User Interface Core

Show Network Connections on Start Menu

Enables access to Network Connections from the Start Menu.

Add Hardware Control Panel

Enables access to the Add Hardware icon from the Control Panel.

Add/Remove Programs Control Panel

Enables access to the Add/Remove Programs icon from the Control Panel.

Date/Time Control Panel

Enables access to the date and time configuration from the Control Panel.

Display Control Panel

Enables access to the display configuration from the Control Panel.

System Control Panel

Enables access to the system configuration from the Control Panel.

Computer Name User Interface

Enables access to the computer name and workgroup configuration from the System Control Panel.

Users Control Panel

Enables access to basic user configuration from the Control Panel.

Windows Accessories

Enables Notepad, Wordpad, and Paint Brush.

Registry Editor

Adds registry-editing tools (REGEDIT.EXE).

CMD � Windows Command Processor

Enables command line input via CMD.EXE.

Disk Management MMC Snap-in

Enables disk management from the Computer Management console.

TCP/IP Utilities

Enables pinging network resources from a command line.

Device Manager

Enables access to Deice Manager from the System Control Panel.

Msxml 3.1

Required for Device Manager to function

Administration Support Tools

Enables the Computer Management console.� Refer to the 'Configuring Access to the Computer Management Console' section of this document for more information.� This component and its dependencies add 50 megabytes to the image size.

OpenGL Support

Required if you are using the Enhanced-Graphical-Interface (EGI) in the FOH.

Adding all of the above components and their dependencies produces an image size of approximately 190 megabytes.

The computer hardware configuration or additional software outside of the Aloha application software FOH might require additional components.

Workgroup and Computer Name

Configure the same workgroup name on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the workgroup name, but this name is arbitrary as long as it is consistent throughout the Aloha application software.�

You can configure Windows XPe as a member of a workgroup or a domain.� Select a workgroup name.� Only experienced network administrators should consider enabling a domain name.� Configuring a domain name might require additional components.

Configure the terminal's network name.� Aloha Technologies uses TERM1, TERM2, and so on by default.� You can use different names, but they must follow Aloha application software specifications.� The terminal's name must use a name that is common to all terminals (the TERMSTR, refer to document AKBID1010) followed by a number designating the terminal's ID number.� Examples include ALOHA1, ALOHA2, TSFOH_1, and TSFOH_2.� In this case, the TERMSTR would be 'ALOHA' or 'TSFOH_'.� You cannot use different TERMSTR names within the Aloha application software.� You cannot use spaces, but you can use underscores.� You can use leading zeros if they are part of the TERMSTR, but Aloha Technologies does not recommend doing so.

To configure the workgroup name and computer name in Target Designer, select either the Standard PC or the Advanced Configuration and Power Interface (ACPI) PC component (depending on which one you included in your image), and select Settings/System Settings/System Identification.

TCP/IP Media Sense

Windows XPe uses Media Sense with TCP/IP to determine whether the network card is in a linked state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.�

You can manually disable Media Sense on the terminal using Windows Registry Editor after applying the image to the target system, or you can configure a new component for Target Designer that disables Media Sense.

To manually disable Media Sense on the terminal using Windows Registry Editor, perform the following:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters.

3.        Verify the DisableDHCPMediaSense value exists in the folder.� If it does, double-click it and change Value Data to '1'.� If it does not exist, choose Edit/New/DWORD Value and name the key' DisableDHCPMediaSense'.� Then double-click the entry and change Value Data to '1'.

4.        Select Registry/Exit to exit the Windows Registry Editor.

5.        Restart Windows.�

To disable Media Sense by using a component in Target Designer, configure a new component in Component Designer that creates a new DWORD value in the Windows registry labeled DisableDHCPMediaSense, assigns it a value of '1', and places the new value in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters.

Media Sense provides the ability to connect to networks with different DHCP options in one Windows session without the need to release and renew the IP configuration by using IPCONFIG.EXE.� If you disable Media Sense, no new IP configuration information is obtained when you connect to a new network unless you restart the computer, or you release and renew the IP configuration by using IPCONFIG.EXE.

Refer to Microsoft Knowledge Base document Q239924 for more information on Media Sense.

Configure User Accounts and Automatic Login

Add new users to the runtime image using the User Account component in Target Designer.� Add a separate instance of the User Account component for each new user.� Refer to document AKBID1006 for more information on Aloha application software users requirements.

After you add the User Account component, open the advanced properties to configure the user name, password, and privileges.� Use cmiUserName to configure the user name, cmiUserPassword to configure the password, and cmiUserGroup to configure the privileges (use 1 for Administrator, 2 for Power User, 3 for User, or 4 for Guest).

At the time of this writing, there is not a method for disabling password expiration in Target Designer.� You must configure the password expiration properties after the image is deployed.

At the time of this writing, there is not a method for enabling the Guest account or configuring its password Target Designer.� You must configure the Guest account properties after the image is deployed or create a new account and assign it guest privileges.

After you configure your users, add automatic login to the runtime image using the Automatic Logon component in Target Designer.� After you add the Automatic Logon component, select Settings/Automatic Logon Settings, and configure the user name, password, and domain/workgroup.

The Automatic Logon component does not add the ForceAutoLogon variable to the Windows Registry (refer to document AKBID1005), so you must create a new component for Target Designer to perform this task or you must manually edit the Windows Registry on the terminal to add the variable after applying the image to the target system.

Configuring Access to the Computer Management Console

In order to access the Computer Management Console in Windows XPe, you must add the Administration Support Tools component.

Once you have added the Computer Management Console to your image, you cannot access it by right-clicking My Computer and selecting Manage or by the Administrative Tools in the Control Panel.� You have to manually run COMPMGMT.MSC from Start/Run or create a shortcut to COMPMGMT.MSC, and place the shortcut in the Start Menu, on the desktop, or in Administrative Tools.

You can also create a new component for Target Designer that automatically adds a shortcut to COMPMGMT.MSC in your image.

Display Settings

If you configure your display adaptor in Target Designer (click the device's component and select Settings), it lists all possible resolution and color options, even if your display adaptor does not support some of the combinations.� If you select a resolution and color combination that is not supported by your display adaptor, Windows XPe First-Boot-Agent (FBA) reverts to 640x480 resolution.� Ensure that your display adaptor supports the resolution and color combination that you configure.

Set the Color palette to 256 Colors or higher.� Aloha Technologies recommends using 16-bit color.� Refer to document AKBID1165 for screen resolution settings.

Do not enable a Windows screen saver.

Target Media Preparation

Prepare the hard drive (or the storage medium you have, such as a memory or RAM-based storage device) using Microsoft FDISK.EXE and FORMAT.EXE (can use FAT16 or FAT32 file systems), connecting the hard drive to an existing PC and preparing the partitions using Windows disk manager (can use FAT16, FAT32, or NTFS file systems), or use third party partitioning and formatting software (file system restrictions depend on the software).�

Your partition sizes will vary with the components that you install (refer to the Create Base Image section of this document).� Refer to document AKBID1183 for more information on configuring partitions for use with the Aloha application software and their required sizes.

If you have formatted your boot partition with FAT16 or FAT32, use BOOTPREP.EXE (provided with the Target Designer utilities) to make the partition bootable.� In most cases, you can just run BOOTPREP.EXE, but you can view the command line options by typing BOOTPREP.EXE /?.

If you formatted your partition with NTFS, then it is inherently bootable, so you do not need to use BOOTPREP.EXE.

Transfer the Image to the Target Media

Once you have created an image, you must transfer it to the target media.� One popular method is using Windows Preinstallation Environment (WinPE).� You can boot from the Windows XPe Installation CD 1 in order to boot a target PC into WinPE.� Once you have started WinPE, you can use standard network and command-line-shell commands in order to copy the image to the target (for example, NET USE and XCOPY)

Time Zone & Daylight Savings

At the time of this writing, there is not a method for configuring time and date setting in Target Designer.� You must configure the time and date properties after the image is deployed.

In order for the file server and all terminals to display the correct time and adjust to daylight savings changes properly, you must properly configure the Windows time and date settings.� Ensure that each terminal is configured to the same time zone, and if the area observes daylight savings, then ensure it is enabled on all terminals and the file server.� This can disable daylight savings, but it needs to be consistent throughout the Aloha application software.� You cannot enable daylight savings on one terminal and not on another, or enable it on the file server and not the terminals.

FIFO Buffers

Windows XPe enables First-In-First-Out (FIFO) buffers for each COM port.� These buffers tend to interfere with printers using Xon/Xoff flow control, so Aloha Technologies disables these buffers on all COM ports on all terminals, regardless of the printer type.� (In the event of a printer or COM port failure, a printer using Xon/Xoff flow control may be temporally connected to the port in the future.)

At the time of this writing, there is not a way to access the FIFO buffer configuration from Device Manager, so you need to edit the Windows Registry in order to disable them.

To manually disable the FIFO buffers on the terminal using Windows Registry Editor, perform the following:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Serial.

3.        Verify the ForceFifoEnable value exists in the folder.� If it does, double-click it and change Value Data to '0'.� If it does not exist, choose Edit/New/DWORD Value and name the key' DisableDHCPMediaSense'.� Then double-click the entry and change Value Data to '0'.

4.        Select Registry/Exit to exit the Windows Registry Editor.

5.        Restart Windows.�

To disable the FIFO buffers by using a component in Target Designer, configure a new component in Component Designer that creates a new DWORD value in the Windows registry labeled ForceFifoEnable, assigns it a value of '0', and places the new value in HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Serial.

Set the Lana Number to Zero

After you have installed and started Windows XPe on the target system, ensure the network binding intended for use by the Aloha application software is set to lana zero.� Refer to document AKBID1018 for more information.

Install the Aloha Application Software

Once you have deployed Windows XPe on the target system and configured all of the components, use the terminal installation diskette to install the Aloha application software.

To create this diskette, insert the Aloha Installation CD in the file server's CD-ROM, and run SETUPPOS.EXE /ADVANCED.� Select Make Diskettes/Create Terminal Installation Diskette from the Main Menu.� After you have created the diskette, insert it into the terminal's floppy drive, and run SETUPTRM.EXE.� The setup program walks you through the rest of the installation.

If the terminal does not have a floppy drive, run the Terminal Installation application directly from the Aloha Installation CD in the CD-ROM on the file server.� Map a drive to the CD-ROM on the file server from the terminal.� Do not select Reconnect at Logon when mapping the drive.� Run the \TERMINST\SETUPTRM.EXE application from the Aloha Installation CD.� The setup program walks you through the rest of the installation.

You can also copy the TERMINST folder from the Aloha Installation CD directly to the FOH terminal's local drive, and run SETUPTRM.EXE locally.

At the time of this writing, Windows XPe does not support sharing a root drive; it only supports sharing folders.� This limitation requires you to create a root folder in which the Aloha application software folder will reside (for example, POS or BOOTDRV).� SETUPTRM.EXE will subsequently install the Aloha application software in this folder (for example, C:\POS\ALOHA or C:\BOOTDRV\ALOHAQS), and share this folder as BOOTDRV rather than the root drive.

If you receive Dde Client errors when running SETUPTRM.EXE, then install the Explorer shell component.� Other shell components (for example, Task Manager shell) might not have all of the functionality required by SETUPTRM.EXE.

Set Control Server and EDC Server Login on the File Server

You might need to adjust the login account used by CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) on the file server to ensure proper operation with terminals running Windows XPe.� Refer to AKBID1197 for more information.

Extended Information

Page File

Windows XPe does not enable the system page file by default since it consumes disk space.� If you need to enable and configure it, select the Standard PC component or the Advanced Configuration and Power Interface (ACPI) PC component (depending on which one you included in your image), and select Settings/System Settings/System Pagefile.�

If you continue to experience memory errors, edit the page file settings to enable Windows to administrate its size.� You must do this in the Windows system properties after you have deployed the image.

Adding addition memory decreases and/or replaces the need for a page file.

Sources of Help for Windows XPe

There are a number of places to obtain help for Windows XPe, provided you are willing to search for the answers.

One of the best locations is the microsoft.public.windowsxp.embedded newsgroup.� There are several Microsoft technicians along with experienced Windows XPe users that assist with questions.�

Prior to posting a new question on the microsoft.public.windowsxp.embedded newsgroup, you can quickly search archived posts via Google Groups.� Open http://www.google.com, click the Groups link, and enter your search text.� Include 'group:*windowsxp.embedded*' (without the quotes) in your search text in order to limit the results to microsoft.public.windowsxp.embedded newsgroup.

You can also find information on the Microsoft Windows Embedded web page located at http://www.microsoft.com/windows/embedded/xp/default.asp.

Additional support documents are available from the Microsoft Developer Network (MSDN^�) web page located at http://www.msdn.microsoft.com, and the Microsoft Product Support Services web page located at http://support.microsoft.com.

The following article is a great introduction to Windows XPe: http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnembedded/html/embedded09262002.asp.

Setting the IP Address from a Command Line

If you are using a static IP address, you can assign the IP address in Windows XPe using the NETSH.EXE command-line shell (network command shell) after applying the client image and booting the client rather than using network configuration applet.� You must add the Network Command Shell and Network Command Shell Interface Context components to your image in order to use the network command shell.

Once you have started Windows XPe on the client, run NETSH.EXE, and type the following command line in the network command shell (adjust the IP address and subnet mask as needed):

interface ip set address name="Local Area Connection" static addr=10.100.156.1 mask=255.255.255.0

Type 'Bye' to close the network command shell, and restart the Windows XPe client.

You can also add the previous command line to a batch file, changing only the IP address for use on each client.� This results in less typing and less mistakes.� To execute the batch file, open the network command shell, and type 'EXEC <path and batch file name>'.

If you receive an error stating 'Invalid interface Local Area Connection specified', then verify the name of the local connection by typing the following command line in the network command shell:

�� interface ip show addr

This will display the network interface name, which you can use on the command line to set your IP address (to replace "Local Area Connection").� If the name is an alphanumeric label within braces (for example, {E1F31F79-7303-404D-1A9543B6D2}), then you need to run explorer once (as either an application or as the Windows shell), and restart the network command shell.� This should reset the network interface name to Local Area Connection.

Windows Installer Service

Some applications (such as the IBM^� OPOS drivers) require Windows Installer in order to install the software.� In this case, add the Windows Installer Service component and its dependencies to the runtime image.

Windows-based Printers

If you are using Windows-based printers with the Aloha application software, you must add the Local Printer Support component and its dependencies to the runtime image.� You should also enable 'Show Printers and Faxes on Start Menu' in the User Interface Core component.

CD-ROM

If your Windows XPe target computer has a CD-ROM drive, you need to add the CDFS component and its dependencies in order to read CDs.

Floppy Drive

If your Windows XPe target computer has a floppy drive, you need to add the FAT component and its dependencies in order to read floppies.

Caveats

This document is intended to supplement Windows XPe user manuals and usage documentation provided my Microsoft, not replace it.� You must already possess knowledge of using Target Designer and its components prior to using the information in this document.� This document only covers Aloha-specific portions of creating a Windows XPe client image for use on an Aloha application software FOH order-entry terminal.

All Windows XPe problems reported to the Aloha Customer Service Center (CSC) must be reproducible in standard Windows XP Professional prior to the CSC assisting you with or troubleshooting problems and errors.

Aloha Technologies does not recommend including only the required components in an image.� Doing so severely inhibits the ability to configure Windows for the Aloha application software and provide support for the Aloha application software.

The computer hardware configuration or additional software outside of the Aloha application software FOH might require additional components.

At the time of this writing, there is not a method for disabling password expiration in Target Designer.� You must configure the password expiration properties after the image is deployed.

At the time of this writing, there is not a method for enabling the Guest account or configuring its password Target Designer.� You must configure the Guest account properties after the image is deployed or create a new account and assign it guest privileges.

The Automatic Logon component does not add the ForceAutoLogon variable to the Windows Registry (refer to document AKBID1005), so you must create a new component for Target Designer to perform this task or you must manually edit the Windows Registry on the terminal to add the variable after applying the image to the target system.

At the time of this writing, there is not a method for configuring time and date setting in Target Designer.� You must configure the time and date properties after the image is deployed.

At the time of this writing, Windows XPe does not support sharing a root drive; it only supports sharing folders.� This limitation requires you to create a root folder in which the Aloha application software folder will reside (for example, POS or BOOTDRV).� SETUPTRM.EXE will subsequently install the Aloha application software in this folder (for example, C:\POS\ALOHA or C:\BOOTDRV\ALOHAQS), and share this folder as BOOTDRV rather than the root drive.

============================================================================

See also:

AKBID1005 Microsoft Windows Auto Log In

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1010 Aloha Application Software System Environment Variables

AKBID1018 Network Lana Numbers

AKBID1165 FOH Screen Resolution Settings

AKBID1175 Aloha Terminal Restart Options

AKBID1176 Windows XP FOH Terminal Setup

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1197 Assigning Logins to Aloha Services

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1158 exp win pe

style='mso-spacerun:yes'>� 2003

Restoring the TRANS.LOG to DATA After the EOD Process

Restoring the TRANS.LOG to DATA After the EOD Process

============================================================================

AKBID1159

Created: 18 July 2000

Updated: 9 October 2000

Reviewed: 20 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

Subject: Restoring a TRANS.LOG to the DATA Folder After the EOD Process

============================================================================

Summary

After the ALOHA^� application software completes the End-of-Day (EOD) process (refer to document AKBID1015), with the exception of the labor information, users cannot edit the business day's sales information.� In rare cases, users may need to void an item or otherwise edit sales from a previous day by restoring the TRANS.LOG (transaction log) from the former Date-of-Business (DOB) to the DATA folder.

Information

There are three methods for invoking the EOD process:

1.        Firing the EOD process from an Event.

2.        Forcing the EOD process from the Front-of-House (FOH).

3.        Forcing the EOD process from the Back-of-House (BOH).

If you use an event to fire the EOD process or force the EOD process from the FOH, you can restore the transaction log without assistance from Aloha Technologies.� If you forced the EOD process from the BOH, you must send the transaction log to Aloha Technologies in order to remove the EOD transaction.� Otherwise the EOD process immediately starts again if the FOH attempts to use the transaction log.

The method used to invoke the EOD process prescribes the steps required to restore and edit the transaction log.

EOD Process Fired from Event

Perform the following if the EOD process was fired by an event:

1.        Stop or shut down the FOH terminals.

2.        Open Maintenance or Aloha Manager, and delete the EOD event.

3.        Refresh the system, and shut down Maintenance or Aloha Manager.

4.        Rename the dated folder containing the transaction log to restore.

5.        If there is an existing transaction log in the DATA folder with transactions you wish to keep, move the transaction log to a temporary location.

6.        Copy the transaction log from the renamed dated folder to the DATA folder.

7.        Change the DOB in the ALOHA.INI in both the NEWDATA and DATA folders to the date of the transaction log.

8.        Start the FOH and make the necessary changes.

9.        Open Maintenance or Aloha Manager, re-enable the EOD event, and refresh the system.

10.     After the FOH restarts, the EOD process should occur, followed by the Grind process (refer to document AKBID1016) and the Winhook process (refer to document AKBID1028).

If the restored information was more than a single day old, the FOH will start the EOD process a second time, until the DOB matches the system date.� In this case, you must manually adjust the DOB.

If the current DOB is displayed following the EOD process, the system is ready for normal use.� If you had an existing transaction log from the current day you want to use, stop or shut down all FOH terminals, replace the transaction log in the DATA folder on the file server with the new log, and restart the FOH terminals.

EOD Process Forced from FOH

Perform the following if the EOD process was forced from the FOH:

1.        Stop or shut down the FOH terminals.

2.        Shut down Maintenance or Aloha Manager.

3.        Rename the dated folder containing the transaction log to restore.

4.        If there is an existing transaction log in the DATA folder with transactions you wish to keep, move the transaction log to a temporary location.

5.        Copy the transaction log from the renamed dated folder to the DATA folder.

6.        Change the DOB in the ALOHA.INI in both the NEWDATA and DATA folders to the date of the transaction log.

7.        Start the FOH, make the necessary changes, and start the EOD process.

8.        The EOD process should occur, followed by the Grind process (refer to document AKBID1016) and the Winhook process (refer to document AKBID1028).

If the restored information was more than a single day old, you must manually adjust the DOB following the EOD process.

If the current DOB is displayed following the EOD process, the system is ready for normal use.� If you had an existing transaction log from the current day you want to use, stop or shut down all FOH terminals, replace the transaction log in the DATA folder on the file server with the new log, and restart the FOH terminals.

EOD Process Forced from BOH

Perform the following if the EOD process was forced from the BOH:

1.        Send the transaction log to Aloha Technologies for adjustment so the EOD process does not automatically start when the FOH reads the transaction log.

2.        After Aloha Technologies returns the adjusted transaction log, stop or shut down the FOH terminals.

3.        Shut down Maintenance or Aloha Manager.

4.        Rename the dated folder containing the transaction log to restore.

5.        If there is an existing transaction log in the DATA folder with transactions you wish to keep, move the transaction log to a temporary location.

6.        Copy the transaction log sent from Aloha Technologies to the DATA folder.

7.        Change the DOB in the ALOHA.INI in both the NEWDATA and DATA folders to the date of the transaction log.

8.        Start the FOH and make the necessary changes.

9.        Force the EOD process from the BOH.

10.     The EOD process should occur, followed by the Grind process (refer to document AKBID1016) and the Winhook process (refer to document AKBID1028).

If the restored information was more than a single day old, you must manually adjust the DOB following the EOD process.

If the current DOB is displayed following the EOD process, the system is ready for normal use.� If you had an existing transaction log from the current day you want to use, stop or shut down all FOH terminals, replace the transaction log in the DATA folder on the file server with the new log, and restart the FOH terminals.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1015 EOD Process and Errors

AKBID1016 Grind Process and Errors

AKBID1028 Winhook

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1159

�

Manually Upgrading Configuration Files in Aloha Manager

Manually Upgrading Configuration Files in Aloha Manager

============================================================================

AKBID1160

Created: 26 July 2000

Updated: 10 January 2003

Reviewed: 30 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

Subject: Manually Upgrading Configuration Files in Aloha Manager

============================================================================

Summary

This document explains how to upgrade the .DBF database for an existing .DBF database.�

If you are installing a new .DBF database on a system with a relational database (RDB), refer to document AKBID1131.

If you are installing a new .DBF database on a system with an existing database, refer to document AKBID1132.

Information

Stop or shut down all Aloha software applications and services and perform the following steps in the order that they appear.

Update the .DBF Files in NEWDATA

Perform the following to update the .DBF files in the NEWDATA folder:

1.        Start DBCONFIG.EXE from the BIN folder.

2.        Select only the following to update the .DBF files in the NEWDATA folder:

-          DBF Files Only

-          Attended

-          Debug

-          Force Upgrade

3.        Verify the IBERDIR description, and point the Input and Output text boxes to the NEWDATA folder.�

4.        Click Run.

Update the .CDX Files in NEWDATA

If you are using versions 5.239 and lower, perform the following to update the index (.CDX) files in the NEWDATA folder (this step is not required in versions 5.2.4.0 and higher since the 'DBF Files Only' option in the previous step will have already updated the .CDX files):

1.        Start DBCONFIG.EXE from the BIN folder.

2.        Select only the following to update the .CDX files in the NEWDATA folder:

-          Attended

-          Debug

-          Upgrade DBF Index Files

3.        Verify the IBERDIR description, and point the Input and Output text boxes to the NEWDATA folder.�

4.        Click Run.

Update the .DBF Files in the DATA Folder

Perform the following to update the .DBF files in the DATA folder using the .DBF files in the NEWDATA folder:

1.        Start DBCONFIG.EXE from the BIN folder.

2.        Select only the following to update the .DBF files in the DATA folder:

-          DBF Files Only

-          Attended

-          Debug

-          Force Upgrade

3.        Verify the IBERDIR description, and point the Input text box to the NEWDATA folder and the Output text box to the DATA folder.�

4.        Click Run.

Update the .CDX files in the DATA Folder

If you are using versions 5.239 and lower, perform the following to update the index (.CDX) files in the DATA folder (this step is not required in versions 5.2.4.0 and higher since the 'DBF Files Only' option in the previous step will have already updated the .CDX files):

1.        Start DBCONFIG.EXE from the BIN folder.

2.        Select only the following to update the .CDX files in the DATA folder:

-          Attended

-          Debug

-          Upgrade DBF Index Files

3.        Verify the IBERDIR description, and point the Input and Output text boxes to the DATA folder.

4.        Click Run.

Restart the Aloha Application Software

Restart the Aloha application software Aloha software applications and services.

Extended Information

You can automate this process using a batch file similar to the following with the appropriate version of DBUP.EXE (refer to document AKBID1067):

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

START /WAIT %IBERDIR%\BIN\DBUP3.EXE /DBFONLY /DEBUG /FORCEUPGRADE /DBFINPUT %IBERDIR%\NEWDATA /DBFOUTPUT %IBERDIR%\NEWDATA

START /WAIT %IBERDIR%\BIN\DBUP3.EXE /CDX /DEBUG /DBFINPUT %IBERDIR%\NEWDATA /DBFOUTPUT %IBERDIR%\NEWDATA

START /WAIT %IBERDIR%\BIN\DBUP3.EXE /DBFONLY /DEBUG /FORCEUPGRADE /DBFINPUT %IBERDIR%\DATA /DBFOUTPUT %IBERDIR%\DATA

START /WAIT %IBERDIR%\BIN\DBUP3.EXE /CDX /DEBUG /DBFINPUT %IBERDIR%\DATA /DBFOUTPUT %IBERDIR%\DATA

Caveats

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1067 DBUP.EXE and DBCONFIG.EXE

AKBID1131 Using .DBF Files to Create a New RDB Over an Existing RDB

AKBID1132 Installing a New .DBF Database Over an Existing Database

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1160

�

EMPMAGCARDMASK in the ALOHA.INI

EMPMAGCARDMASK in the ALOHA.INI

============================================================================

AKBID1161

Created: 5 October 2000

Updated: 9 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.013 � 5.3.x

Subject: Configuring EMPMAGCARDMASK in the ALOHA.INI

===========================================================================

Summary

The ALOHA^� application software uses the EMPMAGCARDMASK variable in ALOHA.INI to mask portions of track one on magnetic stripe cards employees log in with.� This document explains how to configure the EMPMAGCARDMASK variable in the Aloha application software.

Information

To enable the magnetic card mask, edit ALOHA.INI in the NEWDATA folder, and add the variable EMPMAGCARDMASK, if it does not already exist.� Assign a value to the mask using an 'x' to represent characters to skip and an 'o' to represent characters to read.�

For example, track one on a magnetic strip card consists of '123456789', but you only want the Aloha application software to read '4567'.� You would set the value of EMPMAGCARDMASK in ALOHA.INI to 'xxxooooxx', or EMPMAGCARDMASK=xxxooooxx.�

The following rules apply to the EMPMAGCARDMASK variable:

1.        EMPMAGCARDMASK only applies to track one on the magnetic strip card.�

2.        All employee magnetic strip cards must have the same number of numerical characters in the track one field.

3.        EMPMAGCARDMASK must represent all of the numerical characters in the track one field.

4.        Alphabetical characters are ignored.

For example, if an employee has '4567' assigned as a magnetic stripe card password and EMPMAGCARDMASK set to 'xxxooooxx', the following strings in track one receive the following results:

Track 1 Contents

Result

123456789

Works

1234567890

Does not work

12345678

Does not work

AB3456789

Does not work

ABC123456789

Works

AB123456789CD

Works

A1B2C3D4E5F6G7H8I9

Works

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

AKBID1198 Magnetic Stripe Card Information

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1161 display hide mag magcard magcards show swipe

�

Microsoft Windows Service versus a Standard Application

Microsoft Windows Service versus a Standard Application

============================================================================

AKBID1162

Created: 11 September 2000

Updated: 10 April 2003

Reviewed: 27 January 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 4.2x � 5.3.x

Subject: Installing CTLSVR.EXE and EDCSVR.EXE as a Windows Service versus a Standard Application

============================================================================

Summary

You can register the ALOHA^� application software's CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) applications as Microsoft^� Windows^� services or as standard applications.� The decision to register Control Server or EDC Server as a service or as a standard application depends on the operating system (OS), the type of environment, security, and the customer's requirements.

Information

When using the Windows NT^�, Windows 2000, Windows XP, and Windows Server 2003 operating systems, Aloha Technologies generally opts to register Control Server and EDC Server as services when installing the Aloha application software on a file server.� When using the Windows 95, Windows 98, or Windows Millennium Edition (Me) operating systems, Aloha Technologies generally opts not to register Control Server and EDC Server as services when installing the Aloha application software on a file server.� Since this is not a concrete rule, users must consider the information in this document to decide whether to install Control Server and EDC Server as services or not.

Control Server and EDC Server

Control Server broadcasts file server capability, monitors the dated folders and DATA folder to initiate the Grind process (refer to document AKBID1016) after the End-of-Day (EOD) process completes (refer to document AKBID1015) or a user requests a report for the current Date-of-Business (DOB), and performs various other functions required by the Aloha application software.� If Control Server is not active, these processes do not occur.�

EDC Server processes credit card requests from Front-of-House (FOH) terminals, the file server (using EDC.EXE), or remote instances of EDC.EXE.� Refer to document AKBID1020.�

Service versus Standard Application

If an application is started as a service, it is active when Windows starts, regardless if anybody has logged into the system or if the system has been logged out of.� Conversely, Windows does not start standard applications (non-services) until a user logs in to the system, and Windows closes the application if the user logs out of the system.�

If you register Control Server as a service, Control Server is active regardless if CTL.EXE (Control) or ALOHAMGR.EXE (Aloha Manager) is active or not.� This enables you to close Control or Aloha Manager without disabling required functionality.� If you did not register Control Server as a service, it is disabled if you close Control or Aloha Manager, or if they are inactive.

If you register EDC Server as a service, EDC Server is active regardless if EDC.EXE (EDC) is active not.� This enables you to close EDC without disabling required functionality.� If you did not register EDC Server as a service, it is disabled if you close EDC, or if it is inactive.

Operating Systems

Although each OS supports services, Windows NT, Windows 2000, Windows XP, and Windows Server 2003 lend themselves to interfacing with services better than Windows 95, Windows 98, and Windows Me.

Windows NT, Windows 2000, Windows XP, and Windows Server 2003 enable you to start and stop services through either a graphical user interface (GUI) or a command line.� If you need to disable Control Server or EDC Server, such as to replace either application or stop the functionality, you only need to do so via the GUI or a command line.�

Windows 95, Windows 98, and Windows Me do not enable users to disable the services using a GUI or a command line.� If you need to disable Control Server or EDC Server, such as to replace either application or stop the functionality, you must either use KILLSVR.EXE to close the application, or unregister the service and restart the computer.� Restarting the file server causes a disruption in the FOH POS operation.

Regardless of the OS, if you do not register Control Server as a service, exiting Control or Aloha Manager disables Control Server.� If you do not register EDC Server as a service, exiting EDC disables EDC Server.

Security

Keeping an idle system in a logged-out state increases security, but in most cases, the extra security is not required at a typical restaurant.� Additionally, auto log in is often employed (refer to document AKBID1005), which in itself decreases security.

If the restaurant requires the file server to idle in a logged-out state, you must register Control Server and EDC Server as a service; otherwise, you can register them as a standard application.

Environment

In some environments, you to not have a have a choice of registering Control Server and EDC Server as a service or standard application.� For example, if you are installing both QuickService and TableService as separate applications on the file server, you must register Control Server as a standard application.

Extended Information

The following are the Windows NT, Windows 2000, Windows XP, and Windows Server 2003 command lines to start Control Server or EDC Server:

NET START CTLSVR

NET START EDCSVR

The following are the Windows NT, Windows 2000, Windows XP, and Windows Server 2003 command lines to stop Control Server or EDC Server:

NET STOP CTLSVR

NET STOP EDCSVR

Caveats

No information.

============================================================================

See also:

Aloha Installation Guide

Aloha QuickService or TableService User Manual

Aloha Credit Card User Manual

AKBID1005 Microsoft Windows Automatic Log In

AKBID1015 EOD Process and Errors

AKBID1016 Grind Process and Errors

AKBID1020 EDC Process

AKBID1197 Assigning Logins to Aloha Services

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1162 regserver

FOH HASP Key Expiration

FOH HASP Key Expiration

============================================================================

AKBID1163

Created: 8 September 2000

Updated: 17 September 2003

Reviewed: 10 December 2003

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

Subject: Front-of-House HASP Key Expiration

============================================================================

Summary

The ALOHA^� application software uses the Aladdin^� Hardware-Against-Software-Piracy (HASP^�) key for protection against software piracy.� Since the HASP key is connected to the file server, the Front-of-House (FOH) communicates with the file server to verify existence of the HASP key.� In the case of file server failure, the FOH functions for 21 days without a HASP key before special measures must be taken to continue usage.

Information

The Aloha application software uses the following rules in regards to requiring a HASP key in redundant mode:

'Redundant' mode refers to the state in which the Aloha application software recognizes a different computer as the file server than the SERVER variable indicates.� Refer to document AKBID1010.

1.        You must have a HASP key attached to the computer acting as the file server the first time you start the Aloha application software.

2.        The Back-of-House (BOH) cannot function at all without a HASP key.

3.        The FOH can function without a HASP key for up to 21 days since last communicating with the HASP key.

4.        After 21 days, the FOH must communicate with the HASP key via CTLSVR.EXE (Control Server) on a stand-alone file server or on the local parallel or Universal-Serial-Bus (USB) port on the FOH terminal acting as the file server.

5.        If the system uses a stand-alone file server, Control Server cannot use the NONET variable.� Refer to document AKBID1010.

Although the FOH user does not require administrative access, the Aloha application software requires the user to have read/write access to the Windows registry in order for this feature to function properly.

If the FOH functions for more than 21-days without communicating with a HASP key, you will see a message stating the following:

'System redundancy has been exceeded! Restore your fileserver to continue or contact your service provider for assistance.'

In this case, you have two options:

1.        Re-enable the file server with the HASP key on it, thus removing the system from its redundant state.

2.        Place the HASP key on the terminal temporarily acting as the file server.� Ensure that you install the HASP drivers on the FOH terminal (refer to document AKBID3016).

If you use the latter method, then you can remove the key after the FOH communicates with the key, and the FOH will not require the key again for 21 days.

Troubleshooting

To remove this message if the system is functioning normally in regards to the file server being online and functional, perform the following:

1.        Verify if the HASP security key is attached to the file server, as defined by the SERVER system environment variable on the file server.

2.        Verify if the HASP security key is attached to the file server, as defined by the SERVER system environment variable on each terminal.

3.        Verify the computer defined as the file server by the SERVER system environment variable is actually functioning as the file server.

4.        Verify that Control Server is enabled on the file server.

5.        Verify if the lana number for the network protocol assigned to the Aloha application software is properly configured (refer to document AKBID1018) on the file server.�

6.        Verify if the lana number for the network protocol assigned to the Aloha application software is properly configured (refer to document AKBID1018) on the master terminal.

7.        Verify the user currently logged in to the file server has read/write access to the Microsoft^� Windows^� registry.

8.        Verify the user currently logged in to each terminal has read/write access to the Windows registry.

9.        Check if the REMOTE variable is included in the Control Server command line in the Windows registry (refer to document AKBID3009).�

10.     If the site is not running both the FOH and the Back-of-House (BOH) on the same computer, verify that the NONET variable is not included in the Control Server command line in the Windows registry (refer to document AKBID3009).�

11.     Verify that the shortcuts to CTL.EXE (Control) or ALOHAMGR.EXE (Aloha Manager) on the file server do not include the REMOTE variable.�

If the file server is not functioning properly and fault tolerance capabilities are enabled to compensate for it (the file server is 'down'), attach the HASP key to the terminal acting as the temporary file server and restart the terminal.

Review the Debugging-Output-Files (debouts) on the terminals for further causes.� Refer to document AKBID1134 for more information on debouts.

Extended Information

Stand-Alone Terminals

If you have a terminal that is never connected to file server over the network, you can upgrade your HASP security key to support this if you are using Aloha version 5.2.8.83 or higher.�� Contact your Aloha Technologies Sales representative for more information on a remote terminal upgrade for your HASP security key.

Ensure that you install the HASP drivers on the remote terminal (refer to document AKBID3016).

Caveats

Although the FOH user does not require administrative access, the Aloha application software requires the user to have read/write access to the Windows registry in order for this feature to function properly.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1010 Aloha Application Software System Environment Variables

AKBID1112 HASP Key Troubleshooting

AKBID1134 Debouts

AKBID3016 HASP Driver Removal and Installation

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1163 expire

style='mso-spacerun:yes'>� 2003

�

Repairing Corrupt NRTotals File

Repairing Corrupt NRTotals File

============================================================================

AKBID1164

Created: 9 August 2000

Updated: 9 August 2000

Reviewed: 5 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Repairing a Corrupt NRTotals File

============================================================================

Summary

The ALOHA^� application software uses the NRTotals file to store non-resetting income totals.� Although the active NRTotals file is stored in the Data folder, a backup copy is placed in the dated folder each night during the End-of-Day (EOD) process (refer to document AKBID1015).� In case the NRTotals file in the Data folder becomes corrupted, you can build a new one using a backup copy of NRTotals and the Grind process (refer to document AKBID1016).

Information

Perform the following to restore a corrupt NRTotals file:

1.        Move the current NRTotals file from the Data folder to a temporary folder.

2.        Copy the NRTotals file from a dated folder prior to the start of the corruption to the Data folder.

3.        Update the NRTotals file to the current day by manually grinding each dated folder, starting with the dated folder the replacement NRTotals file was copied from in step two.� Grind the dated folders in order from oldest to the most recent.� Refer to document AKBID1016 for manual grinding instructions.

4.        If reports indicate the corruption is repaired, delete original NRTotals file that was moved to a temporary folder.

Extended Information

You can export the information contained in the NRTotals file using VNR2.exe. �Refer to document AKBID1012 for more information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1015 EOD Process and Errors

AKBID1016 Grind Process and Errors

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1164 non nonreset report reset

FOH Screen Resolution Settings

FOH Screen Resolution Settings

============================================================================

AKBID1165

Created: 2 October

Updated: 19 September 2002

Reviewed: 10 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.0x � 5.3.x

Subject: Front-of-House Screen Resolution Settings and Options

============================================================================

Summary

The Front-of-House (FOH) screen resolution and settings required by the ALOHA^� application software vary with the screen size, the Aloha application software version, and the use of Cool Interfaces.� This document explains the options available for each version of the Aloha application software.

Information

Versions 4.0x and Lower

QuickService and TableService versions 4.0x and lower only support 640x480 resolution.

Versions 4.2x � 4.4x

QuickService versions 4.2x and 4.4x support 640x480 resolution with the Microsoft Windows font size set to small fonts, or 800x600 resolution with the Windows font size set to large fonts.

TableService versions 4.2x and 4.4x support the following resolutions:

-          640x480 resolution with the Microsoft Windows font size set to small fonts.

-          800x600 resolution with the Windows font size set to large fonts.

-          Any resolution using the ALOHAXRES and ALOHAYRES variables (refer to document AKBID1119) with the Microsoft Windows font size set to small fonts.

TableService Cool Interfaces only support 640x480 resolution with the Microsoft Windows font size set to small fonts.

Version 5.001 � 5.021

QuickService versions 5.001 through 5.021 support 640x480 resolution with the Microsoft Windows font size set to small fonts, and 800x600 resolution with the Windows font size set to large fonts.

TableService versions 5.001 through 5.021 support the following resolutions:

-          640x480 resolution with the Microsoft Windows font size set to small fonts.

-          800x600 resolution with the Windows font size set to large fonts.

-          Any resolution using the ALOHAXRES and ALOHAYRES variables (refer to document AKBID1119) with the Microsoft Windows font size set to small fonts.

TableService version 5.0 Revision A supports the following Cool Interfaces with 640x480, 800x600, and 1024x768 resolutions with the Microsoft Windows font size set to small fonts:

Interface

640x480

800x600

1024x768

Notes

Blue Stone

Yes

Yes

Yes

Requires the ALOHAXRES and ALOHAYRES environment variables and small fonts if the resolution differs from 640x480.

Fabric

Yes

No

No

Marble

Yes

No

No

Wave

Yes

No

No

Version 5.022 - 5.3.x

QuickService and TableService versions 5.022 through 5.3.x automatically adjust their resolution to match the Windows resolution settings.� Set the Windows font size to small fonts.� Use the ALOHAXRES and ALOHAYRES variables (refer to document AKBID1119) to override the automatic resolution adjustment if needed.

TableService versions 5.2x and higher supports the following Cool Interfaces with 640x480, 800x600, and 1024x768 resolutions with the Microsoft Windows font size set to small fonts:

Interface

640x480

800x600

1024x768

Notes

Blue Stone

Yes

Yes

Yes

Fabric

Yes

No

No

Marble

Yes

No

No

Wave

Yes

No

No

For more information on the Enhanced Graphical Interface (EGI) available in versions 5.2.5.x and higher, refer to document AKBID1216.

Extended Information

In TableService (versions 4.2x and higher) and QuickService (versions 5.2 and higher), use the ALOHATOP and ALOHALEFT environment variables (refer to document AKBID1119) to adjust the screen position of Iber.exe or Iberqs.exe.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1097 Aloha Application Software Font Name and Size Variables

AKBID1119 FOH Adjustable Resolution Settings

AKBID1216 Enabling and Configuring FOH Enhanced Graphical Interface

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1165 480 600 640 768 800 1024 full fullscreen

style='mso-spacerun:yes'>� 2003

�

Aloha Manager BOH Security Files

Aloha Manager BOH Security Files

============================================================================

AKBID1166

Created: 10 October 2000

Updated: 11 October 2000

Reviewed: 30 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 5.0x � 5.3.x

Subject: Using Aloha Manager BOH Security Files to Create a Common BOH Security Template

============================================================================

Summary

The ALOHA^� application software uses three .DBF files or Relational Database (RDB) tables to create and assign Back-of-House (BOH) security levels and passwords to employees: Security Levels, Security Level Detail, and Employees.� This document explains the contents of each file and how to configure them as a custom template for new stores.� By using the same BOH security template for each new store, users are assured common login names and passwords.

Information

BOH security settings are stored in three files or tables:

.DBF File

RDB Table

Description

SECLVL.DBF

SecurityLevel

Security level names and identification numbers

SECLVLDT.DBF

SecurityLevelDetail

Security level functionality assignments

EMP.DBF

Employee

Employee security level ID assignments, BOH password (encrypted), and login time restrictions

Each .DBF file also has a .CDX and .TDX file associated with it.� Refer to document AKBID1060 for more information.

You can create a BOH security template by placing these files in new systems.� This enables common security levels and BOH logins for use across multiple restaurants.

Besides the security data, the Aloha application software also stores user preferences and navigation bar information in the PROFILES folder.

Creating Templates

Regardless if the restaurant is using .DBF files or an RDB, the base files must be stored and transferred in .DBF format.

To create new template files, start with a blank database, open Aloha Manager, and perform the following:

1.        Select Maintenance/Labor/BackOffice Security Levels, and create the common security levels.

2.        Assign access settings to the new security levels.

3.        Select Maintenance/Labor/Employees, and create the common employees.

4.        Assign security levels and login time restrictions to the new employees.

5.        Log out and separately log in each employee to assign him or her a BOH password.�

6.        Copy the SECLVL.DBF, SECLVLDT.DBF, and EMP.DBF files from the NEWDATA folder to a storage location outside of the NEWDATA or DATA folders.

7.        Copy the PROFILES folder to a storage location outside of the current PROFILES folder.

Applying Template Files to a .DBF System

Perform the following to apply the template files to a .DBF-based system:

Performing the following overwrites all employees, security levels, user preferences, and navigation bar settings already existing on the system.

1.        Disable Aloha Manager.

2.        Copy the SECLVL.DBF, SECLVLDT.DBF, and EMP.DBF files to the NEWDATA and DATA folders, overwriting the existing files.

3.        Copy the PROFILES folder to the IBERDIR, overwriting existing files.

4.        Refer to document AKBID1160 to upgrade the files to ensure they match the Aloha software version and create the .CDX and .TDX files.�

Always perform an upgrade of the .DBF files to ensure they match the Aloha software version.

Applying Template Files to an RDB System

Perform the following to apply the template files to a .DBF-based system:

Performing the following will overwrite all employees, security levels, current sales data, historical sales data, user preferences, and navigation bar settings already existing on the system.

1.        Disable Aloha Manager.

2.        Copy the SECLVL.DBF, SECLVLDT.DBF, and EMP.DBF files to the NEWDATA and DATA folders, overwriting the existing files.

3.        Copy the PROFILES folder to the IBERDIR, overwriting existing files.

4.        Refer to document AKBID1131 to upgrade the files, create the .CDX and .TDX files, and create new RDB tables.

Importing BOHSEC from Version 4.4x and Lower into Versions 5.0x or Higher

Since Alohas version 4.4x and lower uses the BOHSEC file to store BOH security information (refer to document AKBID3004), users can only convert and transfer the security levels, but not employee assignments, login names, or passwords.� Furthermore, replacing the EMP.DBF on an existing system will overwrite the current employees listed in the file.�

Performing the following overwrites the current SECLVL.DBF and SECLVLDT.DBF files if they already exist.

Use DBCONFIG.EXE (refer to document AKBID1067) with the 'Force Security' option to convert the BOHSEC file.

Extended Information

No information.

Caveats

Regardless if the restaurant is using .DBF files or an RDB, the base files must be stored and transferred in .DBF format.

Copying the security template .DBF files to the NEWDATA and DATA folders overwrites all employees, security levels, user preferences, and navigation bar settings already existing on a system.

When adding the security template .DBF files, always perform an upgrade of the .DBF files to ensure they match the Aloha software version.

Recreating the RDB tables erases all current and historical sales data.

Using DBCONFIG.EXE with the 'Force Security' option overwrites the current SECLVL.DBF and SECLVLDT.DBF files if they already exist.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1042 Aloha Application Software Database Files

AKBID1060 .CDX Files versus .TDX Files

AKBID1067 DBUP.EXE and DBCONFIG.EXE

AKBID1131 Using .DBF File to Create a New RDB Over an Existing RDB

AKBID1160 Manually Upgrading Aloha Configuration Files in Aloha Manager

AKBID3004 The File Formally Known as BOHSEC

AKBID3043 Aloha Manager Navigation Bar Settings

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1166

�

Temporarily Disabling EDC for Modem Availability

Temporarily Disabling EDC for Modem Availability

============================================================================

AKBID1167

Created: 12 October 2000

Updated: 8 May 2002

Reviewed: 5 February 2004

Microsoft Windows Versions: All

Aloha Products: EDC

Aloha POS Versions: 4.2x � 5.3.x

Subject: Temporarily Disabling EDC to Use the Modem with Other Applications

============================================================================

Summary

If you need to perform polling or other processes that require the ALOHA^� application software Electronic Data Capture (EDC) application's modem while the restaurant is closed and not actively using EDC, you must first disable EDC, perform the processes that require the modem and then re-enable EDC.� This document explains methods for automatically disabling and re-enabling EDC using batch files and either Winhook, the Microsoft^� Windows^� Schedule Service (refer to document AKBID1047), or the Windows Task Scheduler.

Information

The method of disabling EDCSVR.EXE (EDC Server) depends on the operating system and if EDC Server is registered as a Windows service or not.� Refer to document AKBID1162 for more information on Windows services.

EDC Server is not Registered as a Service

To automatically disable EDC when it is not registered as a Windows service, create a batch file with the following information and use Winhook, the Windows Schedule Service or Task Manager to initialize the batch file:

CLOSEAPP.EXE /QUIT ALOHA EDC

Refer to document AKBID1012 for more information on the CLOSEAPP.EXE utility.

After perform the processes that require the EDC modem has completed, re-enable EDC by creating a batch file with the following information and use Winhook, the Windows Schedule Service or Task Manager to initialize the batch file:

%IBERDIR%\BIN\EDC.EXE

EDC Server is Registered as a Service

If EDC Server is registered as a service, the file server must be using the Windows NT, Windows 2000, Windows XP, or Windows Server 2003 operating system to perform the instructions in this document.� The information in this document does not apply to users of Windows 95, Windows 98, or Windows Me who have registered EDC Server as a service.

To automatically disable EDC when it is registered as a Windows service, create a batch file with the following information and use Winhook, the Windows Schedule Service or Task Manager to initialize the batch file:

START /WAIT CLOSEAPP.EXE /QUIT ALOHA EDC

NET STOP EDCSVR

Refer to document AKBID1012 for more information on the CLOSEAPP.EXE utility.

After perform the processes that require the EDC modem has completed, re-enable EDC by creating a batch file with the following information and use Winhook, the Windows Schedule Service or Task Manager to initialize the batch file:

START /WAIT NET START EDCSVR

%IBERDIR%\BIN\EDC.EXE

Extended Information

No information.

Caveats

If EDC Server is registered as a service, the file server must be using the Windows NT, Windows 2000, Windows XP, or Windows Server 2003 operating system to perform the instructions in this document.� The information in this document does not apply to users of Windows 95, Windows 98, or Windows Me who have registered EDC Server as a service.

============================================================================

See also:

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1028 Winhook

AKBID1047 Microsoft Windows Schedule Service

AKBID1162 Microsoft Windows Services versus a Standard Application

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1167 alohaenterprise alohaenterprise.com enterprise enterprise.com

�

Configuring Gift Cards for Use with Gift Certificate Manager

Configuring Gift Cards for Use with Gift Certificate Manager

============================================================================

AKBID1168

Created: 13 October 2000

Updated: 11 August 2003

Reviewed: 23 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 5.016 � 5.3.x

Subject: Configuring Gift Cards for Use with Aloha Gift Certificate Manager

============================================================================

Summary

ALOHA^� Gift Certificate Manager support gift certificates in the form of magnetic stripe cards, or gift cards.� Gift cards are setup and treated similar to traditional gift certificates, but the Aloha application software enables specific options to govern how gift cards are sold and redeemed.� This document explains how to configure gift cards for use with Gift Certificate Manager.

Information

Gift Card Magnetic Stripe Information

If you are using magnetic stripe cards as gift certificates (or gift cards), you are required to program the gift card identification number on either track one or track two, but not both tracks.� Programming both tracks can yield a 'double read'.� In order to ensure full compatibility, you should only use numeric prefix, serial, and suffix numbers for gift cards.

Do not use alphanumeric prefix and suffix characters with gift cards.

The Aloha application software parses the gift card identification number by reading everything between the beginning and ending sentinels, so only the gift card identification number can reside on the gift card.� The Aloha application software does not support leading zeros on gift card prefix, serial, and suffix numbers.� Do not include any spaces between the prefix, serial, or suffix numbers.

Programming leading zeros in the gift card prefix, serial, or suffix numbers will lead to incorrect behavior by the Aloha application software.

Do not include any spaces between the prefix, serial, or suffix numbers.

The Aloha application software versions 5.021 and lower only support keyboard-wedge Magnetic-Stripe-Readers (MSRs) for selling gift cards, although you can redeem cards using keyboard-wedge, IBM POSS and OPOS MSRs.� The Aloha application software versions 5.022 and higher support all MSR types for both selling and redeeming gift cards.

Aloha Technologies suggests printing the gift card number (magnetic stripe information) on the face of the gift card in case the magnetic stripe becomes unreadable.

Gift Card Number Restrictions and Examples

Gift card serial numbers have a maximum length of 10 digits and a maximum value of 1299999999.� Gift card prefixes and suffixes have a maximum length of five digits.

Programming leading zeros in the gift card prefix, serial, or suffix numbers will lead to incorrect behavior by the Aloha application software.

If you are using multiple gift card series, you should maintain a common length for all three components (prefix, serial, and suffix) throughout each series.� For example, use 3-digit prefix numbers, 6-digit serial numbers, and 2-digit suffix numbers for each series.

Examples of acceptable prefix numbers include 100 through 199.� Examples of unacceptable prefix numbers include 001 through 099 (note the leading zeros).� You can use prefix numbers of different lengths, such as 123 and 1234, but this is not recommended since it will be hard to distinguish the prefix from the serial number between various series.

Examples of acceptable serial numbers include 10001, 10002�60000 (note the same length and lack of leading zeros).� Examples of unacceptable serial numbers include 00001, 00002�60000 (note the leading zeros).� You can use serial numbers of different lengths, such as 1, 2, 3, 10, 100, 1000, 6000, but this is not recommended.

Examples of acceptable suffix numbers include 100 through 199.� Examples of unacceptable suffix numbers include 001 through 099 (note the leading zeros).� You can use suffix numbers of different lengths, such as 123 and 1234, but this is not recommended since it will be hard to distinguish the prefix from the serial number between various series.

BOH Setup

Add the gift cards to the Back-Of-House (BOH) just as you would traditional gift certificates, but consider the following when creating gift cards in Gift Certificate Designer:

-          Do not enable automatic gift certificate numbering under the Numbers subtab.� The Front-of-House (FOH) must prompt users for gift card number in order to record and track the gift card number.

-          Enable 'Use Inventory Feature' under the Issue subtab.� This also requires you to inventory the gift certificates in Inventory and Issue.� Corporate gift certificate users must inventory the gift certificates on the corporate-level.

-          If you enable 'Allow Partial Redemptions' under the Redemption subtab, do not enable 'Issue New Gift Certificate' unless you want to issue a new gift card with a partial redemption.

-          Set Certificate Format to 'None' under the Format subtab.

-          If you do not want the FOH to prompt for a price when selling the gift card, set a value in the Fixed Certificate Value text box under the Format subtab.

In the Aloha application software tender setup, enable 'Use Magnetic Card ONLY' if you want to disable manual gift card number entry.�

Refer to the Aloha QuickService or TableService User Manual and the BackOffice Gift Certificates User Manual for more information.

FOH Usage

When you sell a gift card in the FOH, swipe the gift card when prompted for a gift certificate number.� Depending on the pricing options, you may or may not be prompted for the price.

Some non-keyboard-based (OPOS) magnetic stripe readers (MSR) may not record the gift certificate number properly when the gift card is sold in versions prior to 5.022.

When redeeming a gift card, swipe the gift card when prompted for the gift certificate number, and the FOH will authorize the gift card and deduct the sale amount.

Extended Information

No information.

Caveats

Do not use alphanumeric prefix and suffix characters with gift cards.

Do not include any spaces between the prefix, serial, or suffix numbers.

Programming leading zeros in the gift card prefix, serial, or suffix numbers will lead to incorrect behavior by the Aloha application software.

Some non-keyboard-based magnetic stripe readers (MSR) may not record the gift certificate number properly when the gift card is sold.

============================================================================

See also:

Aloha QuickService or TableService User Manual

Aloha Gift Certificate Manager User Manual

AKBID1135 Using E-Messenger and Corporate Gift Certificates

AKBID1198 Magnetic Stripe Card Information

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1168 gc mag magcard magcards swipe

�

Assigning .wav Files to FOH Login Functions and Events

Assigning .wav Files to FOH Login Functions and Events

============================================================================

AKBID1169

Created: 2 November 2000

Updated: 3 November 2000

Reviewed: 16 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

Subject: Assigning .wav Files to Front-of-House Login Functions and Events

============================================================================

Summary

The ALOHA^� application software enables you to assign .wav audio files to certain login functions and events.� This feature is primarily intended for demonstrations and trade shows, but you can also use it in a live environment.

Information

The following functions support .wav files:

Function

Hook ID

Login screen

50001

Login successful number 1

50002

Login successful number 2

50003

Login successful number 3

50004

Login successful number 4

50005

Incorrect employee number

50006

Incorrect password

50007

Employee locked on another terminal (TableService only)

50008

Perform the following to enable .wav files:

1.        Edit Aloha.ini in the file server's NewData folder, and set the MULTIMEDIA variable to TRUE (for example, MULTIMEDIA=TRUE).�

2.        Create a MM subfolder inside the Aloha application software folder on each terminal (for example, C:\Aloha\MM).

3.        Copy the designated .wav files to the folder and label them using the format Mnnnnn.wav, where nnnnn is the Hook ID listed previously in this document (for example, M50001.wav).

4.        Refresh the system.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1169 sound sounds

�

Multiple Versions of Aloha on a Single Demo Computer

Multiple Versions of Aloha on a Single Demo Computer

============================================================================

AKBID1170

Created: 8 November 2000

Updated: 20 March 2003

Reviewed: 20 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 4.2x � 5.3.x

Subject: Configuring Multiple Versions of Aloha on a Single Computer for Demonstration Purposes

============================================================================

Summary

This document explains how to setup multiple versions of the ALOHA^� application software on a single computer for demonstration purposes.

The information in this document is not intended for use in a live restaurant.� It is intended for demonstration purposes only.

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

Information

Network Settings

Ensure the computer's network identification is set properly before attempting to install the Aloha application software.� The Aloha application software installation application (SETUPPOS.EXE or ADVANCED.EXE) on the Aloha Installation CD requires the proper network identification nomenclature.� The name must consist of a name (referred to as TERMSTR) followed terminal number (referred to as TERM).� ALOHA1, QSTS1, and DEMO1 are examples of possible network names.� In the case of ALOHA1, 'ALOHA' is the TERMSTR, and '1' is the TERM number.

Ensure the computer's network configuration is set properly before attempting to install the Aloha application software.� Once installed, the Aloha application software requires that Microsoft^� Windows^� networking is enabled.� If Windows networking is not configured with a valid network interface device, such as a Network-Interface-Card (NIC) or a modem, along with a functional protocol, Windows networking may not be enabled.� If you are using TCP/IP as the default protocol, TCP/IP must be assigned an IP address either statically or via DHCP.� Refer to document AKBID1099 for more information on single-terminal networking.

Install Each Version

Install each version one at a time and in order of the oldest version to the newest version.� Use each version's SETUPPOS.EXE or ADVANCED.EXE to install each version in separate IBERDIR folders (for example, ALOHA42, ALOHA44, ALOHA50, and so on).�

It does not matter if you select 'Run Front of House and Back of House on same PC', 'Run CTLSVR as a service', or 'Run EDCSVR as a service' when installing each version since these settings are overridden later in this document.�

Since each version requires different environment variables to indicate the correct IBERDIR, LOCALDIR, and IBERROOT, you must initialize each version of each application using a separate batch file.� The batch files also register the necessary versions of CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server).

Configure Control Batch Files

Assuming Aloha version 4.2x Control resides in the C:\ALOHA42 folder, a batch file similar to the following starts Control versions 4.2x or 4.4x:

Adjust the Aloha application software environment variables and the location of REGSVR32.EXE as needed.

SET TERMSTR=DEMO

SET NUMTERMS=1

SET SERVER=DEMO1

SET IBERROOT=ALOHA42

SET IBERDIR=C:\%IBERROOT%

SET ROBUST=TRUE

%IBERDIR%\BIN\KILLSVR.EXE -K CTLSVR.EXE

%IBERDIR%\BIN\CTLSVR.EXE /UNREGSERVER /S

C:\WINDOWS\SYSTEM\REGSVR32.EXE /U /S %IBERDIR%\BIN\CTLSVRPS.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /U /S %IBERDIR%\BIN\CALCEDIT.OCX (Version 4.4x only)

C:\WINDOWS\SYSTEM\REGSVR32.EXE /U /S %IBERDIR%\BIN\QWERTY.OCX (Version 4.4x only)

%IBERDIR%\BIN\CTLSVR.EXE /REGSERVER /NONET /S

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S %IBERDIR%\BIN\CTLSVRPS.DLL

%IBERDIR%\BIN\CTL.EXE

KILLSVR.EXE ensures CTLSVR.EXE is not enabled when this batch file is processed, but KILLSVR.EXE is designed only for Windows 95, Windows 98 and Windows Millennium Edition (Me).� If you are using Windows NT^�, Windows 2000 or Windows XP, replace the KILLSVR.EXE line with the following line:

NET STOP CTLSVR.EXE

The '/S' variable directs CTLSVR.EXE and REGSVR32.EXE to use 'silent' operation and not to display conformation dialogues.

Silent operation disables error prompts.� The user will not be informed of errors that may inhibit the application or .DLL registration process.

Configure Maintenance Batch Files

Assuming Aloha version 4.2x Maintenance resides in the C:\ALOHA42 folder, a batch file similar to the following starts Maintenance version 4.2x or 4.4x:

Adjust the IBERDIR environment variable as needed.

SET IBERDIR=C:\ALOHA42

%IBERDIR%\BIN\MNT.EXE

Configure Aloha Manager Batch Files

Assuming Aloha version 5.0x Aloha Manager resides in the C:\ALOHA50 folder, a batch file similar to the following starts Aloha Manager version 5.0x and higher:

Adjust the Aloha application software environment variables and the location of REGSVR32.EXE as needed.

SET TERMSTR=DEMO

SET NUMTERMS=1

SET SERVER=DEMO1

SET IBERROOT=ALOHA50

SET IBERDIR=C:\%IBERROOT%

SET ROBUST=TRUE

%IBERDIR%\BIN\KILLSVR.EXE -K CTLSVR.EXE

%IBERDIR%\BIN\ALOHAMGR.EXE /UNREGSERVERQUIET

IBERDIR%\BIN\ALOHASEC.EXE /UNREGSERVERQUIET

%IBERDIR%\BIN\CTLSVR.EXE /UNREGSERVER /S

C:\WINDOWS\SYSTEM\REGSVR32.EXE /U /S %IBERDIR%\BIN\ALOHALAB.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /U /S %IBERDIR%\BIN\AMGRPS.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /U /S %IBERDIR%\BIN\AMGRSHIM.DLL (Version 5.0x only)

C:\WINDOWS\SYSTEM\REGSVR32.EXE /U /S %IBERDIR%\BIN\ASECPS.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /U /S %IBERDIR%\BIN\CTL4X.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /U /S %IBERDIR%\BIN\CTLSVRPS.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /U /S %IBERDIR%\BIN\EDTPUNCH.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /U /S %IBERDIR%\BIN\MNT4X.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /U /S %IBERDIR%\BIN\USERTOOL.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /U /S %IBERDIR%\BIN\CRYSTL32.OCX

C:\WINDOWS\SYSTEM\REGSVR32.EXE /U /S CRYSTL32.OCX (Version 5.2x and higher)

%IBERDIR%\BIN\ALOHAMGR.EXE /REGSERVERQUIET

%IBERDIR%\BIN\ALOHASEC.EXE /REGSERVERQUIET

%IBERDIR%\BIN\CTLSVR.EXE /REGSERVER /NONET /S

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S %IBERDIR%\BIN\ALOHALAB.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S %IBERDIR%\BIN\AMGRPS.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S %IBERDIR%\BIN\AMGRSHIM.DLL� (Version 5.0x only)

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S %IBERDIR%\BIN\ASECPS.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S %IBERDIR%\BIN\CTL4X.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S %IBERDIR%\BIN\CTLSVRPS.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S %IBERDIR%\BIN\EDTPUNCH.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S %IBERDIR%\BIN\MNT4X.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S %IBERDIR%\BIN\USERTOOL.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S %IBERDIR%\BIN\CRYSTL32.OCX

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S CRYSTL32.OCX (Version 5.2x and higher)

%IBERDIR%\BIN\ALOHAMGR.EXE

KILLSVR.EXE ensures CTLSVR.EXE is not enabled when this batch file is processed, but KILLSVR.EXE is designed only for Windows 95, Windows 98 and Windows Me.� If you are using Windows NT, Windows 2000 or Windows XP, replace the KILLSVR.EXE line with the following line:

NET STOP CTLSVR.EXE

The '/S' variable directs CTLSVR.EXE and REGSVR32.EXE not to display conformation dialogues.

The addition of 'QUIET' to the REGSERVER and UNREGSERVER variables direct ALOHAMGR.EXE and ALOHASEC.EXE not to display conformation dialogues.

Configure IBER.EXE/IBERQS.EXE Batch Files

Assuming Aloha version 4.2x IBER.EXE/IBERQS.EXE resides in the C:\ALOHA42 folder, a batch file similar to the following starts IBER.EXE/IBERQS.EXE version 4.2x and higher:

Adjust the Aloha application software environment variables as needed.

SET TERMSTR=DEMO

SET NUMTERMS=1

SET SERVER=DEMO1

SET IBERROOT=ALOHA42

SET ROBUST=TRUE

SET MASTERCAPABLE=TRUE

SET SERVERCAPABLE=TRUE

SET LOCALDIR=C:\%IBERROOT%

SET CALIBRATE=%LOCALDIR%\BIN\CALIB.EXE

SET TERM=1

IF EXIST %LOCALDIR%\TMP\EXITING DEL %LOCALDIR%\TMP\EXITING

%LOCALDIR%\BIN\IBER.EXE

Configure EDC Version 4.4 and Lower Batch Files

Assuming Aloha version 4.2x EDC resides in the C:\ALOHA42 folder, a batch file similar to the following starts EDC version 4.4x and lower:

Adjust the Aloha application software environment variables and the location of REGSVR32.EXE as needed.

SET TERMSTR=DEMO

SET NUMTERMS=1

SET SERVER=DEMO1

SET IBERROOT=ALOHA42

SET IBERDIR=C:\%IBERROOT%

%IBERDIR%\BIN\KILLSVR.EXE -K EDCSVR.EXE

%IBERDIR%\BIN\EDCSVR.EXE /UNREGSERVER /S

C:\WINDOWS\SYSTEM\REGSVR32.EXE /U /S %IBERDIR%\BIN\EDCSVRPS.DLL

%IBERDIR%\BIN\EDCSVR.EXE /REGSERVER /S

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S %IBERDIR%\BIN\EDCSVRPS.DLL

%IBERDIR%\BIN\EDC.EXE

KILLSVR.EXE ensures EDCSVR.EXE is not enabled when this batch file is processed, but KILLSVR.EXE is designed only for Windows 95, Windows 98 and Windows Me.� If you are using Windows NT, Windows 2000 or Windows XP, replace the KILLSVR.EXE line with the following line:

NET STOP EDCSVR.EXE

The '/S' variable directs EDCSVR.EXE and REGSVR32.EXE not to display conformation dialogues.� EDCSVR.EXE does not recognize the '/S ' variable unless there is a space after the 'S' (use '/S ', not '/S'.)

Configure EDC Version 5.0 and Higher Batch Files

Assuming Aloha version 5.0x EDC resides in the C:\ALOHA50 folder, a batch file similar to the following starts EDC version 5.0x and higher:

Adjust the Aloha application software environment variables and the location of REGSVR32.EXE as needed.

SET TERMSTR=DEMO

SET NUMTERMS=1

SET SERVER=DEMO1

SET IBERROOT=ALOHA50

SET IBERDIR=C:\%IBERROOT%

%IBERDIR%\BIN\KILLSVR.EXE -K EDCSVR.EXE

%IBERDIR%\BIN\ALOHASEC.EXE /UNREGSERVERQUIET

%IBERDIR%\BIN\EDCSVR.EXE /UNREGSERVER /S

C:\WINDOWS\SYSTEM\REGSVR32.EXE /U /S %IBERDIR%\BIN\ASECPS.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /U /S %IBERDIR%\BIN\EDCSEC.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /U /S %IBERDIR%\BIN\EDCSVRPS.DLL

%IBERDIR%\BIN\ALOHASEC.EXE /REGSERVERQUIET

%IBERDIR%\BIN\EDCSVR.EXE /REGSERVER /S

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S %IBERDIR%\BIN\ASECPS.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S %IBERDIR%\BIN\EDCSEC.DLL

C:\WINDOWS\SYSTEM\REGSVR32.EXE /S %IBERDIR%\BIN\EDCSVRPS.DLL

%IBERDIR%\BIN\EDC.EXE

KILLSVR.EXE ensures EDCSVR.EXE is not enabled when this batch file is processed, but KILLSVR.EXE is designed only for Windows 95, Windows 98 and Windows Me.� If you are using Windows NT, Windows 2000 or Windows XP, replace the KILLSVR.EXE line with the following line:

NET STOP EDCSVR.EXE

The '/S' variable directs EDCSVR.EXE and REGSVR32.EXE not to display conformation dialogues.� EDCSVR.EXE does not recognize the '/S ' variable unless there is a space after the 'S' (use '/S ', not '/S'.)

The addition of 'QUIET' to the REGSERVER and UNREGSERVER variables direct ALOHASEC.EXE not to display conformation dialogues.

Extended Information

Refer to document AKBID3169 for more information on the KEY.TXT HASP^� security key identification file.�

The information in this document also applies to setting up a computer with multiple versions of both QuickService and TableService.

Windows 95, Windows 98, and Windows Millennium Edition (Me) users might have to increase the environment memory for each batch file if they experience 'Out of environment space' errors when applying the batch file.� If you experience this problem, the environment variables in the batch files will not be properly applied and the Aloha software applications might not function properly.� Perform the following to increase the environment memory:

1.        Right-click the batch file and select Properties.

2.        Click the Memory tab.

3.        Click the 'Initial environment' drop-down menu and select 1024.

4.        Click OK.

You can also add the following line to the CONFIG.SYS in order to increase the memory globally:

SHELL=C:\COMMAND.COM C:\ /E:1024 /P

If you are not using a HASP key, refer to document AKBID1173.

Caveats

The information in this document is not intended for use in a live restaurant.� It is intended for demonstration purposes only.

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

Silent operation disables error prompts.� The user will not be informed of errors that may inhibit the application or .DLL registration process.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1010 Aloha Application Software System Environment Variables

AKBID1082 Separate QS and TS Installations on a Single Demo Computer

AKBID1099 Network Troubleshooting

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1170 Multiple Versions of Aloha on a Single Demo Computer

AKBID1173 Demo Aloha without a HASP Key

AKBID1228 Demo both QS and TS with a Single Instance of Aloha Manager

AKBID3169 KEY.TXT HASP Security Key Identification File

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1170 demonstrate

�

FOHHook.bat

FOHHook.bat

============================================================================

AKBID1171

Created: 29 December 2000

Updated: 25 July 2002

Reviewed: 6 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x - 5.3.x

Subject: Configuring FOHHook.bat to Automatically Initialize on FOH Terminals During the EOD Process

============================================================================

Summary

The ALOHA^� application software enables you to configure a custom batch file (FOHHook.bat) that automatically initializes in the Front-of-House (FOH) on the Master terminal immediately following the End-of-Day (EOD) process, but before the FOH terminals restart.� Although you can configure FOHHook.bat to perform any number of tasks, this functionality is directed at SuperSites for functions such as copying or archiving dated folders to the SuperSite file server (refer to document AKBID1133).

Information

To enable the FOHHook.bat functionality, create a file labeled FOHHook.bat in the Aloha application software Bin folder, configure the batch file to perform the desired tasks and set the FOHHOOKTIMEOUT variable in the Aloha.ini.� The FOHHOOKTIMEOUT variable instructs the master terminal how long to wait (in seconds) after executing FOHHook.bat so the batch file has time to complete before the terminals are rebooted.� Since the Master terminal leaves the EOD flag in the Data folder for as long as the FOHHOOKTIMOUT variable in Aloha.ini is set for, none of the other terminals reboot either.� The FOHHOOKTIMEOUT variable should be set to 50 or greater (FOHHOOKTIMEOUT=50), but needs to be adjusted according to your batch file's needs.� Set the FOHHOOKTIMEOUT variable to 0 to disable the FOHHook.bat.

If you do not properly configure the FOHHOOKTIMEOUT variable, the FOH terminals may restart before the batch file's tasks are completed.

There is no way to limit the FOHHook.bat to starting only on select days, but the DATEDAY.EXE and DAYWEEK.EXE utilities can be used to limit selected commands within the batch file to start on select days.� Refer to document AKBID1012 for more information.

The Aloha application software does not check for a successful completion of the batch file since the FOHHook.bat batch file is not an integral part of the Aloha application software.� Once the batch file has been found and launched, it is considered successful regardless of any errors occurring from the batch file's contents.

Winhook uses the %1 parameter to declare the Date-of-Business (DOB) in the batch file.� The %1 parameter is standard syntax for referring to command-line variables from within a batch file.� Always use %1 in place of the dated folder's name in the batch file, for Iber.exe or Iberqs.exe pass the dated folder's label as the first command line parameter.� For example, to delete the .cdx files on the local terminal, use the following command line:

Del %LOCALDIR%\%1\*.cdx

Extended Information

Using FOHHook.bat to Archive Dated Folders in a SuperSite

If you are using FOHHook.bat to compress dated folders to an archive location on the SuperSite file server, then you must compensate for multiple dated folders for the same date within the same store.� For example, a malfunction during the EOD process can cause a second terminal to initiate the EOD process, which can result in multiple copies of a dated folder within a store.

In order to compensate for this, you should create a batch file similar to the following that uses the STOREID and TERM variables to store the archived dated folders in separate folders for each terminal (ensure that you manually create the folders on the target drive):

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

Pkzip.exe \\Alohaboh\Archive\Store%STOREID%\Term%TERM%\%1.zip %LOCALDIR%\%1\*.*

Caveats

If you do not properly configure the FOHHOOKTIMEOUT variable, the FOH terminals may restart before the batch file's tasks are completed.

Some command lines in this document wrap to a second line, but they are a single line in the batch file.� A blank line separates each individual command line in this document.

============================================================================

See also:

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1028 Winhook

AKBID1133 SuperSite Dated Folders

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1171 fohhook hook

�

Configuring the IBM SurePOS 300 and SurePOS 500

Configuring the IBM SurePOS 300 and SurePOS 500

============================================================================

AKBID1172

Created: 11 December 2000

Updated: 1 October 2002

Reviewed: 27 January 2004

Microsoft^� Windows^� Versions: Windows 98, Windows NT^�, Windows 2000, Windows XP

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.026 � 5.3.x

Subject: Configuring the IBM SurePOS 300 and SurePOS 500 POS terminal for Aloha ============================================================================

Summary

The ALOHA^� application software communicates with the IBM^� SurePOS 300 and SurePOS 500 customer displays, magnetic-stripe-readers (MSR), cash drawers, and SureMark 4610 receipt printers using OLE for Retail Point-of-Sale (OPOS) device drivers.� This document explains how to configure these devices for use with the Aloha application software.

Information

General Configuration

If you are using the MSR, ensure the communication switch on the MSR is set to Serial, not Keyboard.� The Aloha application software is not compatible with the SurePOS MSR in keyboard mode.

The IBM OPOS drivers are included in the IBM POS Suite, available at http://www2.clearlake.ibm.com/store/support/index.html.� Drivers for the network-interface-card (NIC), touch screen, video adapter, sound card (if applicable), operating system (OS) patches, and other devices (and publications) are also available at the web site.�

When you install the POS Suite or OPOS drivers on the SurePOS, only enable the 'OPOS RS-232 POS Devices' category and all of the selections inside of it (with the exception of the SureOne drivers), and disable the 'Point of Sale Subsystem' and/or 'OPOS RS-485/USB POS Devices' categories and all of the selections inside of them.�

Once you have installed the OPOS drivers, open the OPOS configuration application, and assign each device an OPOS name using the 'Customize' button.� With the exception of assigning a name to all OPOS devices and changing the COM port for OPOS printers, you should not have to adjust any other settings.

If you are connecting an IBM cash drawer to a SureMark 4610 printer, you must configure the OPOS cash drawer in the printer configuration section in the OPOS application.� After you have named your printer, you can enable Cash Drawer Name and enter the cash drawer name.� You do not need to configure the cash drawer cash drawer section of the OPOS drivers.

Set the terminal type to 'Clone' in the Aloha application software and configure each OPOS device as described in document AKBID1074.

SureMark 4610 Printer Patch

The SureMark 4610 receipt printer requires IBM OPOS versions 1.5.0 and higher, but if you are using IBM OPOS version 1.4.4, you can obtain a patch from Aloha Technologies.

Windows 2000 Beeping

If you are using Windows 2000 on the SurePOS and experience occasional beeping when the Aloha application software is displaying the floating logo, perform the following:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_CURRENT_USER\Control Panel\Sound.

3.        Verify the Beep value exists in the folder.� If it does, double-click it and change Value Data to 'no'.� If it does not exist, choose Edit/New/String Value and name it 'Beep'.� Then double-click the entry and change Value Data to 'no'.

4.        Select Registry/Exit to exit the Windows Registry Editor.

5.        Restart Windows.�

Extended Information

No information.

Caveats

If you are using the MSR, ensure the communication switch on the MSR is set to Serial, not Keyboard.� The Aloha application software is not compatible with the SurePOS MSR in keyboard mode.

============================================================================

See also:

AKBID1074 OPOS

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1172 mark sp sp300 sp500 stage staging sure

�

Demo Aloha without a HASP Key

Demo Aloha without a HASP Key

============================================================================

AKBID1173

Created: 11 December 2000

Updated: 23 September 2002

Reviewed: 19 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 4.2x � 5.3.x

Subject: Demonstrating the Aloha Application Software without HASP Key

============================================================================

Summary

The ability to demonstrate the ALOHA^� application software without an Aladdin^� Hardware-Against-Software-Piracy (HASP^�) key varies in restrictions and setup between software versions and applications.� This document explains how to set up each version and application for demonstration use without a HASP key.

Information

Front-of-House

In versions 4.2x through 4.4x, the Front-of-House (FOH) has complete functionality without the HASP key attached.

In versions 5.0x and higher, the FOH can function without a HASP key attached for 21 days since the last time it communicated with a security key.� As explained in document AKBID1163, the FOH must communicate with the HASP key over the network via CTLSVR.EXE (on a separate file server) or with a HASP key attached to a local port.

If you attach the key to a local port, then you cannot set local SERVER variable to the local computer name.� For example, if your computer name is DEMOALOHA, you cannot set the SERVER variable to DEMOALOHA.� This ensures that the Aloha application software believes the file server is not functioning properly, and the fault tolerance capabilities are enabled to compensate for it.

With either method, the file server (as defined by the SERVER variable) must not be available on the network.� The ability to function without a HASP key expires 21 days from the last interaction with the HASP key.

You can also demonstrate the FOH software using the 'demo' version of IBER.EXE or IBERQS.EXE.� This does not require a HASP key, but the functionality is limited.� Refer to document AKBID3167 for more information.

Back-of-House

Regardless of the version, the Aloha application software Back-of-House (BOH) will not broadcast file server capability or perform the grind process without security key attached.

In versions 4.2x through 4.4x, add /REMOTE to the command line for CTL.EXE (Control).

In versions 5.0x and higher, add /REMOTE to the command line for ALOHAMGR.EXE (Aloha Manager).� Some versions of Aloha Manager might display Control Server errors when you start Aloha Manager.� If this occurs, click OK or Cancel (depending on the error) to continue starting Aloha Manager.

EDC

All versions of EDC function without a HASP key attached, although versions 5.2x and higher require you to have defined valid HASP security key activation codes in the ALOHA.INI in order to have access to all menus and features.

BackOffice

Most Aloha application software BackOffice products can function without a security key, but the following limitations are applied:

Product

Limitation

Accounts Receivable

Twenty accounts

Aloha Labor Scheduler

Changes are not saved

Delivery/Frequent Buyer

Twenty customers

Gift Certificate Manager

Limited to fifty gift certificates in the database

Inventory Control

Twenty batches of information

Extended Information

No information.

Caveats

Regardless of the version, the Aloha application software Back-of-House (BOH) will not broadcast file server capability or perform the grind process without security key attached.

============================================================================

See also:

AKBID1066 Demo Aloha with the Aloha Remote Display System

AKBID1082 Separate QS and TS Installations on a Single Demo Computer

AKBID1163 FOH HASP Key Expiration

AKBID1170 Multiple Versions of Aloha on a Single Demo Computer

AKBID1228 Demo both QS and TS with a Single Instance of Aloha Manager

AKBID3167 IBER.EXE/IBERQS.EXE Demonstration Restrictions

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1173 demo running

�

Stand Alone EDC File Server for Multiple Concepts

Stand Alone EDC File Server for Multiple Concepts

============================================================================

AKBID1174

Created: 9 January 2001

Updated: 30 July 2002

Reviewed: 6 February 2004

Microsoft^� Windows^� Versions: Windows NT^�, Windows 2000, Windows XP

Aloha Products: EDC

Aloha POS Versions: 5.0x � 5.3.x

Subject: Configuring a Stand-Alone EDC File Server for Multiple Aloha Application Software Concepts

============================================================================

Summary

You can configure a single copy of the Electronic Draft Capture (EDC) on a separate and dedicated EDC file server for ALOHA^� application software configurations where separate copies of QuickService and TableService (or two copies of QuickService or TableService) share a single file server or multiple file servers exist for multiple concepts (for example, two separate concepts next door to each other).� This document explains the proper EDC configuration for this type of environment.� Refer to document AKBID1124 for more information on POS configuration for multiple concepts on the same file server.�

This document is intended for an environment where EDC is a separate file server as each concept's application software.� If EDC resides on the same file server as the application software, refer to document AKBID1123.� If you are setting up a separate and dedicated EDC file server for use with a SuperSite or with a single TableService or QuickService site, refer to document AKBID1095.

Information

FOH Terminal Names and ID Numbers

You must configure the Front-of-House (FOH) terminals in a way that each concept uses unique TERMSTR names, and ID numbers.� If the concepts are using the same POS file server, each concept must use unique LOCALDIR names as well.� For example, the following chart shows settings for a location with four TableService terminals and five QuickService terminals:

Concept

TERMSTR

TERM

Network Name

LOCALDIR

TS

TSTERM

1

TSTERM1

ALOHA

TS

TSTERM

2

TSTERM2

ALOHA

TS

TSTERM

3

TSTERM3

ALOHA

TS

TSTERM

4

TSTERM4

ALOHA

QS

QSTERM

5

QSTERM5

ALOHAQS

QS

QSTERM

6

QSTERM6

ALOHAQS

QS

QSTERM

7

QSTERM7

ALOHAQS

QS

QSTERM

8

QSTERM8

ALOHAQS

QS

QSTERM

9

QSTERM9

ALOHAQS

In the example, the NUMTERMS setting for TableService is four, and the NUMTERMS setting for QuickService is five.

Unique network workgroup names or IP subnets are not required for each store and should not be employed.

Network

Establish a TCP/IP or NetBEUI network connection between the EDC file server and POS file server.� The EDC file server must use the same network protocol as the rest of the Aloha application software, and the FOH terminals must have access to the EDC file server.

Configure DCOM

Install and configure Distributed Component Object Model (DCOM) on the EDC server.� Refer to document AKBID1049 for more information about configuring DCOM.

Configure Internet Explorer 4.0 Sp2 (5.2x and higher)

If you are using the Aloha application software version 5.2x or higher, configure Microsoft Internet Explorer 4.0 Service Pack 2 or higher using the source files on the Aloha Installation CD.� Do not overwrite newer versions of Internet Explorer.

Create Aloha Folder and BOOTDRV Share

Create an Aloha application software folder on the EDC file server with the same name as the Aloha application software folder on the POS file server, and create the BOOTDRV share based on the folder location.� Although the EDC file server requires a share name so the FOH terminals may access it, it not required you use the BOOTDRV label.� Using the BOOTDRV label, though, creates constancy with the other Aloha application software computers on the network.

If the Aloha application software folder resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the 'POS' folder as BOOTDRV.� Some clients prefer to place the Aloha application software in a special folder in order to limit the shared files and thus, enhance security.� Sharing the entire drive in which the Aloha application software resides also shares other files that reside on the drive such as Windows.

Create Sub-Folders and Copy Files

Create BIN, DATA, EDC, NEWDATA, and TMP folders inside the Aloha application software folder on the EDC file server.

Copy the following files from the BIN folder on the POS file server to the BIN folder on the EDC file server: ALOHASEC.EXE, ARSEC.DLL, ARSECPS.DLL, ASECPS.DLL, CB532.DLL, EDC.EXE, EDCSEC.DLL, EDCSVR.EXE, EDCSVRPS.DLL, IBERSTR.DLL (5.2x and higher) and SHW32.DLL.

Copy the following files from the NEWDATA folder on the POS file server to the NEWDATA folder on the EDC file server: ALOHA.INI, EMP*.*, SECLVL*.*, and VER.*.

Copy the following files from the DATA folder on the POS file server to the DATA folder on the EDC file server: ALOHA.INI, EMP*.*, SECLVL*.*, and VER.*.

Copy System Files

EDC requires system files in the Windows SYSTEM32 folder, but since current copies of the files may be in use by Windows, you can not copy the new ones to the SYSTEM32 folder.

To alleviate this problem, download SETUPSYS.EXE from the Aloha Technologies FTP site as SETUPSYS.ZIP (refer to document AKBID1012) or use the copy of SETUPSYS.EXE from the \MISC\SETUPSYS folder on the Aloha Installation CD.

Extract the system files from WNTDLL.ZIP and WNTDLL2.ZIP in the ALOHATS folder on the Aloha Installation CD, and place them in a temporary folder on the same drive partition as the Windows folder.� Open SETUPSYS.EXE, define the location of the temporary folder where the system files reside, and install the files.� Restart the computer.

Environment Variables

Add the following to the system environment variables on the EDC file server and restart the system:

Variable

Assignment

EDCPATH

The path to the local EDC folder (for example, D:\ALOHA\EDC)

IBERDIR

The local Aloha application software folder path (for example, C:\ALOHA)

IBERROOT

The local Aloha application software folder label (for example, ALOHA)

POSPATH

The path to the Aloha application software folder on the POS file server (for example, \\ALOHABOH\BOOTDRV\ALOHA)

Also add the local Aloha application software BIN folder to the existing system path.

Restart the computer.

Register ATL.DLL

Open a command prompt, and navigate to the Windows SYSTEM32 folder.� Type the following command line to register ATL.DLL (a successful confirmation should follow the registration):

ATL.DLL must be registered before other applications and .DLL files are registered.

REGSVR32.EXE ATL.DLL

Install EDC Server and Security Server

To install EDCSVR.EXE (EDC Server) and ALOHASEC.EXE, type the following from a command line:

%IBERDIR%\BIN\EDCSVR.EXE /SERVICE

%IBERDIR%\BIN\ALOHASEC.EXE /REGSERVER

If you are using EDC Server versions 5.230 and higher, EDC Server prompts you for the user configuration.� This is the user with which EDC Server will log in.� You can instruct EDC Server to use the Windows local system account (the default configuration in versions 5.229 and lower) or you can configure a specific user name and password.� You must configure a specific login in instances where the operating system on the FOH terminals does not enable network access by the Windows local system account.�

You can use the /LOCALACCOUNT command line variable to instruct EDC Server to register using the Windows local system account without prompting the user.� For example:

%IBERDIR%\BIN\EDCSVR.EXE /SERVICE /LOCALACCOUNT

You can use the /ACCOUNTNAME and /PASSWORD command line variables to instruct EDC Server to register using a specific user name and password.� For example:

EDCSVR.EXE /SERVICE /ACCOUNTNAME .\<user name> /PASSWORD <password>

If you are using a domain account, you can specify the domain name using the following command line:

EDCSVR.EXE /SERVICE /ACCOUNTNAME <domain name>\<user name> /PASSWORD <password>

Register DLL Files

Open a command prompt, and navigate to the BIN folder.� Type the following command lines to register Aloha application software .DLL files (a successful confirmation should follow the registration):

Edit the path to REGSVR32.EXE as needed.

C:\WINNT\SYSTEM32\REGSVR32.EXE ARSEC.DLL

C:\WINNT\SYSTEM32\REGSVR32.EXE ARSECPS.DLL

C:\WINNT\SYSTEM32\REGSVR32.EXE ASECPS.DLL

C:\WINNT\SYSTEM32\REGSVR32.EXE EDCSEC.DLL

C:\WINNT\SYSTEM32\REGSVR32.EXE EDCSVRPS.DLL

Restart the computer.

Edit TRM.DBF and STO.DBF Files

Under normal circumstances, EDC only uses TRM.DBF and the TERMSTR and IBERROOT system environment variables to resolve the terminal network names required to poll the FOH terminals for spooled credit card files.� If two or more concepts share the same file server, each concept's terminals must use different TERMSTR (and possibly IBERROOT) system environment variables, thus single variables can not be relied on to resolve the terminal network names.�

Like SuperSites, a location with multiple concepts on the same file server must use STO.DBF in conjunction with TRM.DBF instead of the TERMSTR and IBERROOT system environment variables to resolve the terminal network names.� Manual changes to the TRM.DBF and STO.DBF are required to create separate TERMSTR and IBERROOT variables for each concept.

Edit TRM.DBF in each concept's NEWDATA folder on the POS file server and set the store ID in the STORE field for each Concept One terminal to '1', each Concept Two terminal to '2', and so on.� Refresh each concept to update TRM.DBF in the DATA folder.� As explained later in this document, EDC will use a single TRM.DBF created by combining each concept's TRM.DBF using COMBITM.EXE.

Copy STO.DBF from one of the concept's NEWDATA folder to the \ALOHA\NEWDATA folder on the EDC file server.� Edit \ALOHA\NEWDATA\STO.DBF on the EDC file server and add the following information:

Field

Description

Concept One

Concept 2

ID

Store ID Number

1

2

OWNERID

Used with CDM

0

0

USERNUMBER

Used with CDM

0

0

NAME

Store Name

QS

TS

NETNAME

Store's TERMSTR

QSTERM

TSTERM

IBERDIR

Store's IBERROOT

ALOHAQS

ALOHA

REGION

Supersite Region

0

0

STOREACC

Used with CDM

0

0

PARENTACC

Used with CDM

0

0

Copy the updated STO.DBF in the EDC file server's \ALOHA\NEWDATA folder to the EDC file server's \ALOHA\DATA folder.

Create Combined TRM.DBF

Use COMBITM.EXE (refer to document AKBID1012 for more information) to combine the \NEWDATA\TRM.DBF files from each concept into a single TRM.DBF.

Copy the combined TRM.DBF to both the \ALOHA\NEWDATA and \ALOHA\DATA folders on the EDC file server.

Updating EDC POS Configuration Files

The EDC file server uses configuration files from the POS file server.� If you are using multiple POS file servers, only update the files from one file server.� To ensure these files are up to date, Aloha Technologies suggests creating the following EDC.CMD file to shut down EDC, update the files, and restart EDC:

IF EXIST %POSPATH%\DATA\ALOHA.INI GOTO RESTART

GOTO END

:RESTART

START /WAIT CLOSEAPP.EXE /QUIT ALOHA EDC

START /WAIT NET STOP EDCSVR

COPY %POSPATH%\NEWDATA\ALOHA.INI %IBERDIR%\NEWDATA

COPY %POSPATH%\NEWDATA\EMP*.* %IBERDIR%\NEWDATA

COPY %POSPATH%\NEWDATA\SECLVL*.* %IBERDIR%\NEWDATA

COPY %POSPATH%\NEWDATA\VER.* %IBERDIR%\NEWDATA

COPY %POSPATH%\DATA\ALOHA.INI %IBERDIR%\DATA

COPY %POSPATH%\DATA\EMP*.* %IBERDIR%\DATA

COPY %POSPATH%\DATA\SECLVL*.* %IBERDIR%\DATA

COPY %POSPATH%\DATA\VER.* %IBERDIR%\DATA

START /WAIT NET START EDCSVR

%IBERDIR%\BIN\EDC.EXE

:END

EXIT

Note the use of the POSPATH environment variable (discussed previously) and CLOSEAPP.EXE.� Download the CLOSEAPP.EXE utility from the Aloha Technologies FTP site, and refer to document AKBID1012 for more information.�

Use the Windows Schedule Service (refer to document AKBID1047) to initialize the file each night.� Windows 2000 users can instead employ Window Task Scheduler to initialize the file each night.

Users may also consider adding a shortcut to EDC.CMD to the Windows Desktop of the Aloha start menu folder so users can manually update the data.

EDC Shortcuts

Create an 'Aloha Credit Cards' (EDC.EXE) shortcut on the desktop, start menu, and anywhere else it is needed.� A shortcut to EDC is not required in the Windows StartUp folder since EDC is registered as a Windows service.

A shortcut to EDC.CMD is not required since it is activated by the Windows Schedule Service.

FOH Terminal Settings

Add or adjust the EDCPATH variable on the POS terminals to provide the path to the EDC folder on the EDC file server.� For example, SET EDCPATH=\\EDCSERVER\BOOTDRV\ALOHA\EDC.

Upgrading EDC.EXE

Upgrades to the Aloha application software on the EDC file server requires replacement and registration of all application files and .DLL files listed previously in this document.�

Extended Information

A SuperSite PMS file server is set up the same as an SuperSite EDC file server, the only difference being the PMS settlement, as explained in document AKBID3066.

SuperSites can share a single EDC/PMS file server, but separate servers are advantageous when a problem with EDC or PMS occurs.� When separate file servers are used, a problem with one does not cripple both processes.

Caveats

This document is intended for an environment where EDC is a separate file server as each concept's application software.� If EDC resides on the same file server as the application software, refer to document AKBID1123.� If you are setting up a separate and dedicated EDC file server for use with a SuperSite or with a single TableService or QuickService site, refer to document AKBID1095.

ATL.DLL must be registered before other applications and .DLL files are registered.

============================================================================

See also:

AKBID1010 Aloha Application Software System Environment Variables

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1020 EDC Process

AKBID1047 Microsoft Windows Schedule Service

AKBID1049 Installing DCOM in Windows

AKBID1063 TCP/IP

AKBID1095 Stand Alone EDC File Server

AKBID1123 Multiple Concept EDC on a Single File Server

AKBID3066 SuperSite PMS Settlement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1174 multi multiconcept qs/ts qsts tsqs ts/qs same

Aloha Terminal Restart Options

Aloha Terminal Restart Options

============================================================================

AKBID1175

Created: 1 March 2001

Updated: 10 April 2003

Reviewed: 28 January 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Aloha Terminal Restart Options

============================================================================

Summary

The ALOHA^� application software typically restarts the Front-of-House (FOH) terminals following the End-of-Day (EOD) process or when you perform a FOH refresh.� How the FOH terminals react to the restart commands issued by the Aloha application software and the possible routines used to restart the Aloha application software varies between Microsoft^� Windows^� versions and user preferences.� This document explains the restart process and the options accompanying it.

Information

Windows 95, Windows 98, and Windows Me

The Aloha application software uses the AUTOEXIT system environment variable to determine whether to restart Windows 95, Windows 98, or Windows Millennium Edition (Me).� The AUTOEXIT variable is set in the AUTOEXEC.BAT or IBERCFG.BAT.� As explained in document AKBID1116, the AUTOEXIT variable is not usually enabled on terminals that run both the Aloha application software FOH and Back-of-House (BOH), otherwise refreshes may not function properly.� The AUTOEXIT variable is typically enabled on dedicated FOH terminals, but it is not required.

In some older versions of the Aloha application software, the AUTOEXIT variable is considered true if it is assigned any value.� For example, if AUTOEXIT is set to FALSE (SET AUTOEXIT=FALSE), it is still considered true since it is assigned a value.� In these versions, you must remove the variable entirely in order to disable the AUTOEXIT variable.

If the AUTOEXIT variable is enabled when the FOH is instructed to restart (because of the EOD process or a FOH refresh), the Aloha application software instructs Windows to restart the computer.� If a shortcut that restarts the Aloha application software resides in the Start Up group, the Aloha application software will automatically start when Windows reinitializes following the restart.

Hardware conflicts, incorrect device drivers, or BIOS settings may inhibit Windows from restarting properly.

If the AUTOEXIT variable is not enabled when the FOH is instructed to restart (because of the EOD process or a FOH refresh), the Aloha application software exits to the Windows desktop, but it does not instruct Windows to restart the computer.� In this case, the Aloha application software must be restarted manually or using a looping batch file as explained in document AKBID3021.

In order to decrease the FOH terminals' downtime during a refresh, users can opt to disable the AUTOEXIT variable and use a looping batch file as explained in document AKBID3021.� This is method discouraged since restarting the terminals on a daily basis (via the EOD process or a FOH refresh) ensures the terminals' memory and resources are cleared on a regular basis.� There is no way to only disable AUTOEXIT for FOH refreshes and not for the EOD process (or vice versa).

Windows NT, Windows 2000, Windows XP, and Windows Server 2003

The Aloha application software uses both the AUTOEXIT and REBOOTNT system environment variables to determine whether and how to restart Windows NT^�, Windows 2000, Windows XP, or Windows Server 2003.�

The AUTOEXIT variable is set in the system environment variables or IBERCFG.BAT.� As explained in document AKBID1116, the AUTOEXIT variable is not usually enabled on terminals that run both the Aloha application software FOH and Back-of-House (BOH), otherwise refreshes may not function properly.� The AUTOEXIT variable is typically enabled on dedicated FOH terminals, but it is not required.

In some older versions of the Aloha application software, the AUTOEXIT variable is considered true if it is assigned any value.� For example, if AUTOEXIT is set to FALSE (SET AUTOEXIT=FALSE), it is still considered true since it is assigned a value.� In these versions, you must remove the variable entirely in order to disable the AUTOEXIT variable.

If the AUTOEXIT variable is enabled when the FOH is instructed to restart (because of the EOD process or a FOH refresh), the Aloha application software instructs Windows to log the user off of the terminal.� If auto-login is enabled (refer to document AKBID1005) and a shortcut that restarts the Aloha application software resides in the Start Up group, Windows automatically logs back in and the Aloha application software will automatically start when Windows reinitializes following the restart.

If the REBOOTNT variable is enabled in conjunction with the AUTOEXIT variable when the FOH is instructed to restart (because of the EOD process or a FOH refresh), the Aloha application software instructs Windows to restart the computer instead of just logging out.� If a shortcut that restarts the Aloha application software resides in the Start Up group, the Aloha application software will automatically start when Windows reinitializes following the restart.� The REBOOTNT variable does not function without the AUTOEXIT variable enabled.

Hardware conflicts, incorrect device drivers, or BIOS settings may inhibit Windows from restarting properly.

If the AUTOEXIT variable is not enabled when the FOH is instructed to restart (because of the EOD process or a FOH refresh), the Aloha application software exits to the Windows desktop, but it does not instruct Windows to log the user out of the computer.� In this case, the Aloha application software must be restarted manually or using a looping batch file as explained in document AKBID3021.

In order to decrease the FOH terminals' downtime during a refresh, users can opt to disable the AUTOEXIT variable and use a looping batch file as explained in document AKBID3021.� This is method discouraged since logging out or restarting the terminals on a daily basis (via the EOD process or a FOH refresh) ensures the terminals' memory and resources are cleared on a regular basis.� There is no way to only disable AUTOEXIT or REBOOTNT for FOH refreshes and not for the EOD process (or vice versa).

Extended Information

No information.

Caveats

In some older versions of the Aloha application software, the AUTOEXIT variable is considered true if it is assigned any value.� For example, if AUTOEXIT is set to FALSE (SET AUTOEXIT=FALSE), it is still considered true since it is assigned a value.� In these versions, you must remove the variable entirely in order to disable the AUTOEXIT variable.

Hardware conflicts, incorrect device drivers, or BIOS settings may inhibit Windows from restarting properly.

============================================================================

See also:

AKBID1005 Microsoft Windows Automatic Log In

AKBID1116 File Server/Terminal Limitations

AKBID3021 FOH Looping Bach File

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1175 boh/foh bohfoh boot foh/boh fohboh reboot terminal/server warm

�

Windows XP FOH Terminal Setup

Windows XP FOH Terminal Setup

============================================================================

AKBID1176

Created: 14 November 2001

Updated: 2 December 2003

Reviewed: 15 March 2004

Microsoft Windows Versions: Windows XP

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.211x � 5.3.x

Subject: Windows XP FOH Terminal Setup

============================================================================

Summary

The ALOHA^� application software requires several specialized settings (as well as several preferred settings) in the Microsoft^� Windows^� XP operating system (OS) to properly run on a terminal.� Failure to properly configure Windows XP will result in erroneous Aloha application software behavior.� If you are using the terminal to run both Front-of-House (FOH) and Back-of-House (BOH) together, refer to document AKBID1178.

Information

Although some computers come with Windows XP preloaded while others do not, this document is based on editing the settings of and existing Windows XP installation.� Users who are installing Windows XP from scratch or upgrading another OS to Windows XP can still use this document either by employing these instructions after the Windows XP installation or by making some of these changes during the Windows XP installation.

In regards to the Aloha application software functionality, the only difference between Windows XP Home Edition and Windows XP Professional is the number of concurrent incoming user connections allowed by the OS.� Windows XP Home Edition enables up to five connections and Windows XP Professional enables up to 10 connections.� You cannot increase the number of connections.� Breaking the connection limit may disrupt the Aloha application software.� Refer to AKBID1048 for more information the recommended number of FOH terminals for each operating system.

File System

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

Set the workgroup name the same on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the workgroup name, but this name is arbitrary as long as it is consistent throughout the Aloha application software.�

You can configure Windows XP as a member of a workgroup or a domain.� Select a workgroup name.� Only experienced network administrators should consider enabling a domain name.

Set the terminal's network name.� Aloha Technologies uses TERM1, TERM2, and so on by default.� You can use different names, but they must follow Aloha application software specifications.� The terminal's name must be a common name used on all terminals (the TERMSTR, refer to document AKBID1010) followed by a number designating the terminal's ID number.� Examples include ALOHA1, ALOHA2, TSFOH_1, and TSFOH_2.� In this case, the TERMSTR would be 'ALOHA' or 'TSFOH_'.� Different TERMSTR names cannot be used within the same Aloha system.� Spaces cannot be used, but underscores can.� Leading zeros can be used if they are part of the TERMSTR, but it is not recommended.

Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure that terminals always have an address assigned to them.� The Aloha application software will not function without an IP address assigned to the terminal.� You may have multiple protocols installed as long as the proper protocol for the Aloha application software has been marked as such by the lana number assignment.� Assign lana number zero to the network binding (protocol and adaptor) used by the Aloha application software.� Refer to document AKBID1018 for more information on assigning lana numbers.�

NetBIOS must be enabled over TCP/IP to use TCP/IP with the Aloha application software.� To do this, access the TCP/IP properties for the Local Area Connection, click the Advanced button, and select the WINS tab.� Select 'Enable NetBIOS over TCP/IP'.

TCP/IP Media Sense

Windows XP uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.�

Perform the following to disable Media Sense in the Windows Registry:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters.

3.        Verify the DisableDHCPMediaSense value exists in the folder.� If it does, double-click it and change Value Data to '1'.� If it does not exist, choose Edit/New/DWORD Value and name the key' DisableDHCPMediaSense'.� Then double-click the entry and change Value Data to '1'.

4.        Select Registry/Exit to exit the Windows Registry Editor.

5.        Restart Windows.�

Media Sense provides the ability to connect to networks with different DHCP options in one Windows session without the need to release and renew the IP configuration by using IPCONFIG.EXE.� If you disable Media Sense, no new IP configuration information is obtained when you connect to a new network unless you restart the computer, or you release and renew the IP configuration by using IPCONFIG.EXE.

Refer to Microsoft Knowledge Base document Q239924 for more information on Media Sense.

File Sharing

The Aloha application software requires a network share labeled BOOTDRV that enables read and write capabilities to the Aloha application software file server and FOH terminals.� This share needs to be applied to the root folder or drive in which the Aloha folder resides.� If the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.

Depending on the version of Windows XP you are using, you may have to enable file sharing before installing the Aloha application software.

If you are using Windows XP Home Edition, you must first perform the following to configure Windows sharing so the Aloha application software setup application can create the required BOOTDRV file share:

Right-click on the drive or folder in which you plan to install the Aloha application software and select Sharing and Security.

If you right-clicked on a drive and not a folder, you may receive a warning about sharing the root folder on a hard drive.� Continue past this warning.

The drive or folder properties window is where you enable network file sharing.� Click 'If you understand the security risks but want to share files without running the wizard' to enable network file sharing.

Click 'Just enable file sharing' on the Enable File Sharing window and click OK.

Click OK on the drive or folder properties window since you do not need to create a new share name (the Aloha application software setup application creates the BOOTDRV share for you).

Refer to document AKBID1006 for more information on configuring Windows logins and shares for the Aloha application software.

If you are using Windows XP Professional and you are part of a workgroup, then Windows enables simple file sharing by default, but you can disable simple file sharing in order to enable user-level file sharing.� If you want to use simple file sharing, you must perform the following before installing the Aloha application software:

Right-click on the drive or folder in which you plan to install the Aloha application software and select Sharing and Security.

If you right-clicked on a drive and not a folder, you may receive a warning about sharing the root folder on a hard drive.� Continue past this warning.

The drive or folder properties window is where you enable network file sharing.� Click 'If you understand the security risks but want to share files without running the wizard' to enable network file sharing.

Click 'Just enable file sharing' on the Enable File Sharing window and click OK.

Click OK on the drive or folder properties window since you do not need to create a new share name (the Aloha application software setup application creates the BOOTDRV share for you).

Refer to document AKBID1006 for more information on configuring Windows logins and shares for the Aloha application software.

If you are using Windows XP Professional as part of a workgroup and you want to enable user-level sharing, perform the following:

Open My Computer and select Tools/Folder Options/View.� Disable 'Use Simple File Sharing' and click OK.

Refer to document AKBID1006 for more information on configuring Windows logins for the Aloha application software.

If you are using Windows XP Professional and you are part of a domain, then Windows enables user-level sharing by default, but you can disable user-level file sharing in order to enable simple file sharing.� If you want to enable simple file sharing, you must perform the following before installing the Aloha application software:

Open My Computer and select Tools/Folder Options/View.� Enable 'Use Simple File Sharing' and click OK.

Right-click on the drive or folder in which you plan to install the Aloha application software and select Sharing and Security.

If you right-clicked on a drive and not a folder, you may receive a warning about sharing the root folder on a hard drive.� Continue past this warning.

The drive or folder properties window is where you enable network file sharing.� Click 'If you understand the security risks but want to share files without running the wizard' to enable network file sharing.

Click 'Just enable file sharing' on the Enable File Sharing window and click OK.

Click OK on the drive or folder properties window since you do not need to create a new share name (the Aloha application software setup application creates the BOOTDRV share for you).

Refer to document AKBID1006 for more information on configuring Windows logins and shares for the Aloha application software.

If you are using Windows XP Professional, you are part of a domain and you wish to use user-level sharing, then you only need to refer to document AKBID1006 for more information on configuring Windows logins for the Aloha application software.

Refer to Microsoft Knowledge Base document Q304040 for more information on Windows XP file sharing.

Display Settings

Set the Color palette to 256 Colors or higher.� Aloha Technologies typically uses 16-bit color.�

Refer to document AKBID1165 for screen resolution settings.

Do not enable a Windows screen saver.

Time Zone & Daylight Savings

For the file server and all terminals to display the correct time and adjust to daylight savings changes properly, the time and date settings must be properly configured in Windows so the file server and each terminal have the same time, date, time zone and daylight savings settings.� The time settings need to be the same on all terminals and the file server.� If the area observes daylight savings, then you must configure the file server and each terminal to automatically adjust for daylight savings.� You can disable automatic daylight savings adjustment if you are in an area that does not recognize daylight savings time (or if you do not want the file server and terminals to automatically adjust for daylight savings), but it needs to be disabled throughout the Aloha application software.� You cannot enable daylight savings on one terminal and not on another or enable it on the file server and not the terminals.

FIFO Buffers

Windows XP enables First-In-First-Out (FIFO) buffers for each COM port.� These buffers tend to interfere with printers using Xon/Xoff flow control, so Aloha Technologies disables these buffers on all COM ports on all terminals, regardless of the printer type.� (In the event of a printer or COM port failure, a printer using Xon/Xoff flow control may be temporally connected to the port in the future.)

To access the FIFO buffer settings, select Start/Settings/Control Panel/System or right click My Computer and select Properties.� Select Hardware/Device Manager, and click the plus sign (+) next to Ports to expand it.� Select each port one at a time, and select Properties/Port Settings/Advanced.� Clear 'Use FIFO buffer'.� Repeat for each COM port.� The LPT port does not have this option.

Login Name

Refer to document AKBID1006 for more information on configuring Windows logins for the Aloha application software.

Service Pack

Aloha Technologies recommends installing Windows XP Service Pack 1 after all software has been installed and Windows XP is configured properly.�

Reinstall the Service Pack anytime significant changes are made to Windows XP.

Install Aloha Software

Once Windows XP is set up according to the standards outlined in this document and you can view the network, use the terminal installation diskette to install the Aloha application software.� Ensure you have enabled Windows file sharing as explained in the File Sharing section of this document before installing the Aloha application software.

To create this diskette, insert the installation CD in the file server's CD-ROM, and run SETUPPOS.EXE /ADVANCED.� Select Make Diskettes/Create Terminal Installation Diskette from the Main Menu

Once the diskette is created, insert it into the terminal's floppy drive, and run SETUPTRM.EXE.� The setup program walks you through the rest of the installation and configures necessary file sharing, creates or copies (from the file server) the necessary folders and files, and adds a shortcut to the Windows StartUp folder.

If the terminal does not have a floppy drive, run the Terminal Installation application directly from the CD-ROM on the file server.� Map a drive to the CD-ROM on the file server.� Do not choose the Reconnect at Logon option when mapping the drive.� Run the file \TERMINST\SETUPTRM.EXE from the Aloha POS CD.� The setup program walks you through the rest of the installation.

Once the installation is complete, you can edit user access to the BOOTDRV share if you have enabled user-level file sharing.

Set Control Server and EDC Server Login on the File Server

You may need to adjust the login account used by CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) on the file server to ensure proper operation with terminals running Windows XP.� Refer to AKBID1197 for more information.

Enable a Hotplugged Keyboard

By default, Windows XP does not enable you to hotplug a keyboard if Windows has already started without a keyboard attached.� You can change this behavior and enable hotplugging a keyboard by performing the following to edit the Windows registry:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

Path out HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\i8042prt\Parameters.

Verify the Headless value exists in the folder.� If it does, double-click it and change Value Data to '1'.� If it does not exist, choose Edit/New/DWORD Value and name the key 'Headless'.� Then double-click the entry and change Value Data to '1'.

Select Registry/Exit to exit the Windows Registry Editor.

Restart Windows.

Extended Information

For additional performance, consider disabling features you do not plan to use, such as System Restore, Remote Assistance, QoS Packet Scheduler, and Windows Messenger.

Caveats

Windows XP uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.� To eliminate this, disable Media Sense.

============================================================================

See also:

AKBID1005 Microsoft Windows Auto Log In

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1010 Aloha Application Software System Environment Variables

AKBID1018 Network Lana Numbers

AKBID1048 Aloha Application Software Hardware and OS Specifications

AKBID1165 FOH Screen Resolution Settings

AKBID1175 Aloha Terminal Restart Options

AKBID1177 Windows XP File Server Setup

AKBID1178 Windows XP Server/Terminal Setup

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1197 Assigning Logins to Aloha Services

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1176 stage staging

Windows XP File Server Setup

Windows XP File Server Setup

============================================================================

AKBID1177

Created: 30 November 2001

Updated: 2 December 2003

Reviewed: 10 March 2004

Microsoft Windows Versions: Windows XP

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.211x � 5.3.x

Subject: Windows XP File Server Setup

============================================================================

Summary

The ALOHA^� application software requires you to configure the Microsoft^� Windows^� XP operating system (OS) to properly run on the run on the file server.� Failure to properly configure Windows XP will result in erroneous Aloha application software behavior.� If you are using the file server to run both Front-of-House (FOH) and Back-of-House (BOH) together, refer to document AKBID1178.

Information

Although some computers come with Windows XP preloaded while others do not, this document is based on editing the settings of an existing Windows XP installation.� Users who are installing Windows XP from scratch or upgrading another OS to Windows XP can still use this document either by employing these instructions after the Windows XP installation or by making some of these changes during the Windows XP installation.

In regards to the Aloha application software functionality, the only difference between Windows XP Home Edition and Windows XP Professional is the number of concurrent incoming user connections allowed by the OS.� Windows XP Home Edition enables up to five connections and Windows XP Professional enables up to 10 connections.� You cannot increase the number of connections.� Breaking the connection limit may disrupt the Aloha application software.� Refer to AKBID1048 for more information the recommended number of FOH terminals for each operating system.

Drive Sizes and Partitions

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

Set the workgroup name the same on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the workgroup name, but this name is arbitrary as long as it is consistent throughout the Aloha application software.�

You can configure Windows XP as a member of a workgroup or a domain.� Select a workgroup name.� Only experienced network administrators should consider enabling a domain name.

Aloha Technologies uses the network name ALOHABOH by default, but this name is arbitrary, so a different name can be used if desired.�

Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure that terminals always have an address assigned to them.� The Aloha application software will not function without an IP address assigned to the terminal.� You may have multiple protocols installed as long as the proper protocol for the Aloha application software has been marked as such by the lana number assignment.� Assign lana number zero to the network binding (protocol and adaptor) used by the Aloha application software.� Refer to document AKBID1018 for more information on assigning lana numbers.�

NetBIOS must be enabled over TCP/IP to use TCP/IP with the Aloha application software.� To do this, access the TCP/IP properties for the Local Area Connection, click the Advanced button, and select the WINS tab.� Select 'Enable NetBIOS over TCP/IP'.

TCP/IP Media Sense

Windows XP uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.�

Perform the following to disable Media Sense in the Windows Registry:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters.

3.        Verify the DisableDHCPMediaSense value exists in the folder.� If it does, double-click it and change Value Data to '1'.� If it does not exist, choose Edit/New/DWORD Value and name the key ' DisableDHCPMediaSense '.� Then double-click the entry and change Value Data to '1'.

4.        Select Registry/Exit to exit the Windows Registry Editor.

5.        Restart Windows.�

Media Sense provides the ability to connect to networks with different DHCP options in one Windows session without the need to release and renew the IP configuration by using IPCONFIG.EXE.� If you disable Media Sense, no new IP configuration information is obtained when you connect to a new network unless you restart the computer, or you release and renew the IP configuration by using IPCONFIG.EXE.

Refer to Microsoft Knowledge Base document Q239924 for more information on Media Sense.

File Sharing

The Aloha application software requires a network share labeled BOOTDRV that enables read and write capabilities to the Aloha application software file server and FOH terminals.� This share needs to be applied to the root folder or drive in which the Aloha folder resides.� If the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.

Depending on the version of Windows XP you are using, you may have to enable file sharing before installing the Aloha application software.

If you are using Windows XP Home Edition, you must first perform the following to configure Windows sharing so the Aloha application software setup application can create the required BOOTDRV file share:

Right-click on the drive or folder in which you plan to install the Aloha application software and select Sharing and Security.

If you right-clicked on a drive and not a folder, you may receive a warning about sharing the root folder on a hard drive.� Continue past this warning.

The drive or folder properties window is where you enable network file sharing.� Click 'If you understand the security risks but want to share files without running the wizard' to enable network file sharing.

Click 'Just enable file sharing' on the Enable File Sharing window and click OK.

Click OK on the drive or folder properties window since you do not need to create a new share name (the Aloha application software setup application creates the BOOTDRV share for you).

Refer to document AKBID1006 for more information on configuring Windows logins and shares for the Aloha application software.

If you are using Windows XP Professional and you are part of a workgroup, then Windows enables simple file sharing by default, but you can disable simple file sharing in order to enable user-level file sharing.� If you want to use simple file sharing, you must perform the following before installing the Aloha application software:

Right-click on the drive or folder in which you plan to install the Aloha application software and select Sharing and Security.

If you right-clicked on a drive and not a folder, you may receive a warning about sharing the root folder on a hard drive.� Continue past this warning.

The drive or folder properties window is where you enable network file sharing.� Click 'If you understand the security risks but want to share files without running the wizard' to enable network file sharing.

Click 'Just enable file sharing' on the Enable File Sharing window and click OK.

Click OK on the drive or folder properties window since you do not need to create a new share name (the Aloha application software setup application creates the BOOTDRV share for you).

Refer to document AKBID1006 for more information on configuring Windows logins and shares for the Aloha application software.

If you are using Windows XP Professional as part of a workgroup and you want to enable user-level sharing, perform the following:

Open My Computer and select Tools/Folder Options/View.� Disable 'Use Simple File Sharing' and click OK.

Refer to document AKBID1006 for more information on configuring Windows logins for the Aloha application software.

If you are using Windows XP Professional and you are part of a domain, then Windows enables user-level sharing by default, but you can disable user-level file sharing in order to enable simple file sharing.� If you want to enable simple file sharing, you must perform the following before installing the Aloha application software:

Open My Computer and select Tools/Folder Options/View.� Enable 'Use Simple File Sharing' and click OK.

Right-click on the drive or folder in which you plan to install the Aloha application software and select Sharing and Security.

If you right-clicked on a drive and not a folder, you may receive a warning about sharing the root folder on a hard drive.� Continue past this warning.

The drive or folder properties window is where you enable network file sharing.� Click 'If you understand the security risks but want to share files without running the wizard' to enable network file sharing.

Click 'Just enable file sharing' on the Enable File Sharing window and click OK.

Click OK on the drive or folder properties window since you do not need to create a new share name (the Aloha application software setup application creates the BOOTDRV share for you).

Refer to document AKBID1006 for more information on configuring Windows logins and shares for the Aloha application software.

If you are using Windows XP Professional, you are part of a domain and you wish to use user-level sharing, then you only need to refer to document AKBID1006 for more information on configuring Windows logins for the Aloha application software.

Refer to Microsoft Knowledge Base document Q304040 for more information on Windows XP file sharing.

Display Settings

Set the Color palette to 256 Colors or higher.� Aloha Technologies typically uses 16-bit color.�

Refer to document AKBID1165 for screen resolution settings.

Do not enable a Windows screen saver.

Time Zone & Daylight Savings

For the file server and all terminals to display the correct time and adjust to daylight savings changes properly, the time and date settings must be properly configured in Windows so the file server and each terminal have the same time, date, time zone and daylight savings settings.� The time settings need to be the same on all terminals and the file server.� If the area observes daylight savings, then you must configure the file server and each terminal to automatically adjust for daylight savings.� You can disable automatic daylight savings adjustment if you are in an area that does not recognize daylight savings time (or if you do not want the file server and terminals to automatically adjust for daylight savings), but it needs to be disabled throughout the Aloha application software.� You cannot enable daylight savings on one terminal and not on another or enable it on the file server and not the terminals.

Login Name

Refer to document AKBID1006 for more information on configuring Windows logins for the Aloha application software.

Processor Performance

By default, Windows XP is configured to assign foreground applications priority processing.� This can cause erroneous behavior in background applications, such as Control Server and EDC Server.� Aloha Technologies suggests setting the processor priority to background applications.

To configure the processor priority, open the System properties and select Advanced/Performance Options, and select Settings in the Performance section.� Select Advanced, and set the performance scheduling to Background Services.

Service Pack

Aloha Technologies recommends installing Windows XP Service Pack 1 after all software has been installed and Windows XP is configured properly.�

Reinstall the Service Pack anytime significant changes are made to Windows XP.

Install Aloha Software

Once Windows XP is set up to the standards outlined in this document, use the Aloha Application Software Installation CD to install the Aloha application software.� Run ADVANVED.EXE from the Aloha POS CD.� The setup program walks you through the rest of the installation.� Ensure you have enabled Windows file sharing as explained in the File Sharing section of this document before installing the Aloha application software.

Refer to document AKBID1162 for more information on running Control Server and EDC Server as Windows services.

Once the installation is complete, you can edit user access to the BOOTDRV share if you have enabled user-level file sharing.

Set Control Server and EDC Server Login

You may need to adjust the login account used by CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) on the file server to ensure proper operation with terminals running Windows XP.� Refer to AKBID1197 for more information.

Extended Information

Improving Performance

For additional performance, consider disabling features you do not plan to use, such as System Restore,

Remote Assistance, QoS Packet Scheduler, and Windows Messenger.

EOD File Copy Errors

If you are experience problems where the End-of-Day (EOD) process fails to copy files, you should perform the following in order to disable write caching for the hard drive in which the Aloha application software resides on the file server:

Open Windows Explorer, right-click on the hard drive in which the Aloha application software is installed, and select Properties.

Select the Hardware tab.

Select the physical drive, and select Properties.

Select the Policies tab.

Clear the 'Enable write caching on the disk' option, and press OK.

Caveats

Windows XP uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.� To eliminate this, disable Media Sense.

============================================================================

See also:

AKBID1005 Microsoft Windows Auto Log In

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1010 Aloha Application Software System Environment Variables

AKBID1018 Network Lana Numbers

AKBID1048 Aloha Application Software Hardware and OS Specifications

AKBID1176 Windows XP FOH Terminal Setup

AKBID1178 Windows XP Server/Terminal Setup

AKBID1148 Backup Procedures

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1197 Assigning Logins to Aloha Services

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1177 stage staging

Windows XP File Server/Terminal Setup

Windows XP File Server/Terminal Setup

============================================================================

AKBID1178

Created: 30 November 2001

Updated: 2 December 2003

Reviewed: 10 March 2004

Microsoft Windows Versions: Windows XP

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.211 � 5.3.x

Subject: Microsoft Windows XP File Server and Terminal on the Same Computer Setup

============================================================================

Summary

The ALOHA^� application software requires you to configure the Microsoft^� Windows^� XP operating system (OS) to properly run on the run both Front-of-House (FOH) and Back-of-House (BOH) together on the same computer.� Failure to properly configure Windows XP will result in erroneous Aloha application software behavior.� If you are using the computer as a file server only, refer to document AKBID1177.� If you are using the computer as a terminal only, refer to document AKBID1176.

Refer to document AKBID1116 for more information on the limitations of running both the FOH and BOH together on the same PC.

Information

Although some computers come with Windows XP preloaded while others do not, this document is based on editing the settings of an existing Windows XP installation.� Users who are installing Windows XP from scratch or upgrading another OS to Windows XP can still use this document either by employing these instructions after the Windows XP installation or by making some of these changes during the Windows XP installation.

If you are converting an existing file server to a file server/terminal, refer to the Extended Information section of this document.

In regards to the Aloha application software functionality, the only difference between Windows XP Home Edition and Windows XP Professional is the number of concurrent incoming user connections allowed by the OS.� Windows XP Home Edition enables up to five connections and Windows XP Professional enables up to 10 connections.� You cannot increase the number of connections.� Breaking the connection limit may disrupt the Aloha application software.� Refer to AKBID1048 for more information the recommended number of FOH terminals for each operating system.

Drive Sizes and Partitions

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

Set the workgroup name the same on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the workgroup name, but this name is arbitrary as long as it is consistent throughout the Aloha application software.�

You can configure Windows XP as a member of a workgroup or a domain.� Select a workgroup name.� Only experienced network administrators should consider enabling a domain name.

Set the file server/terminal's network name.� Aloha Technologies uses TERM1, TERM2, and so on by default.� You can use different names, but they must follow Aloha application software specifications.� The file server/terminal's name must be a common name used on all terminals (the TERMSTR, refer to document AKBID1010) followed by a number designating the terminal's ID number.� Examples include ALOHA1, ALOHA2, TSFOH_1, and TSFOH_2.� In this case, the TERMSTR would be 'ALOHA' or 'TSFOH_'.� Different TERMSTR names cannot be used within the same Aloha system.� Spaces cannot be used, but underscores can.� Leading zeros can be used if they are part of the TERMSTR, but it is not recommended.� The file server/terminal is general configured as terminal one.

Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure that terminals always have an address assigned to them.� The Aloha application software will not function without an IP address assigned to the terminal.� You may have multiple protocols installed as long as the proper protocol for the Aloha application software has been marked as such by the lana number assignment.� Assign lana number zero to the network binding (protocol and adaptor) used by the Aloha application software.� Refer to document AKBID1018 for more information on assigning lana numbers.�

NetBIOS must be enabled over TCP/IP to use TCP/IP with the Aloha application software.� To do this, access the TCP/IP properties for the Local Area Connection, click the Advanced button, and select the WINS tab.� Select 'Enable NetBIOS over TCP/IP'.

TCP/IP Media Sense

Windows XP uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.�

Perform the following to disable Media Sense in the Windows Registry:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters.

3.        Verify the DisableDHCPMediaSense value exists in the folder.� If it does, double-click it and change Value Data to '1'.� If it does not exist, choose Edit/New/DWORD Value and name the key ' DisableDHCPMediaSense '.� Then double-click the entry and change Value Data to '1'.

4.        Select Registry/Exit to exit the Windows Registry Editor.

5.        Restart Windows.�

Media Sense provides the ability to connect to networks with different DHCP options in one Windows session without the need to release and renew the IP configuration by using IPCONFIG.EXE.� If you disable Media Sense, no new IP configuration information is obtained when you connect to a new network unless you restart the computer, or you release and renew the IP configuration by using IPCONFIG.EXE.�

Refer to Microsoft Knowledge Base document Q239924 for more information on Media Sense.

File Sharing

The Aloha application software requires a network share labeled BOOTDRV that enables read and write capabilities to the Aloha application software file server and FOH terminals.� This share needs to be applied to the root folder or drive in which the Aloha folder resides.� If the Aloha application software resides in C:\ALOHA, share C:\ as BOOTDRV.� If it resides in D:\ALOHA, share D:\ as BOOTDRV.� If you created a special folder for the Aloha application software, share the special folder as BOOTDRV.� For example, if it resides in C:\POS\ALOHA, share the POS folder as BOOTDRV.

Depending on the version of Windows XP you are using, you may have to enable file sharing before installing the Aloha application software.

If you are using Windows XP Home Edition, you must first perform the following to configure Windows sharing so the Aloha application software setup application can create the required BOOTDRV file share:

Right-click on the drive or folder in which you plan to install the Aloha application software and select Sharing and Security.

If you right-clicked on a drive and not a folder, you may receive a warning about sharing the root folder on a hard drive.� Continue past this warning.

The drive or folder properties window is where you enable network file sharing.� Click 'If you understand the security risks but want to share files without running the wizard' to enable network file sharing.

Click 'Just enable file sharing' on the Enable File Sharing window and click OK.

Click OK on the drive or folder properties window since you do not need to create a new share name (the Aloha application software setup application creates the BOOTDRV share for you).

Refer to document AKBID1006 for more information on configuring Windows logins and shares for the Aloha application software.

If you are using Windows XP Professional and you are part of a workgroup, then Windows enables simple file sharing by default, but you can disable simple file sharing in order to enable user-level file sharing.� If you want to use simple file sharing, you must perform the following before installing the Aloha application software:

Right-click on the drive or folder in which you plan to install the Aloha application software and select Sharing and Security.

If you right-clicked on a drive and not a folder, you may receive a warning about sharing the root folder on a hard drive.� Continue past this warning.

The drive or folder properties window is where you enable network file sharing.� Click 'If you understand the security risks but want to share files without running the wizard' to enable network file sharing.

Click 'Just enable file sharing' on the Enable File Sharing window and click OK.

Click OK on the drive or folder properties window since you do not need to create a new share name (the Aloha application software setup application creates the BOOTDRV share for you).

Refer to document AKBID1006 for more information on configuring Windows logins and shares for the Aloha application software.

If you are using Windows XP Professional as part of a workgroup and you want to enable user-level sharing, perform the following:

Open My Computer and select Tools/Folder Options/View.� Disable 'Use Simple File Sharing' and click OK.

Refer to document AKBID1006 for more information on configuring Windows logins for the Aloha application software.

If you are using Windows XP Professional and you are part of a domain, then Windows enables user-level sharing by default, but you can disable user-level file sharing in order to enable simple file sharing.� If you want to enable simple file sharing, you must perform the following before installing the Aloha application software:

Open My Computer and select Tools/Folder Options/View.� Enable 'Use Simple File Sharing' and click OK.

Right-click on the drive or folder in which you plan to install the Aloha application software and select Sharing and Security.

If you right-clicked on a drive and not a folder, you may receive a warning about sharing the root folder on a hard drive.� Continue past this warning.

The drive or folder properties window is where you enable network file sharing.� Click 'If you understand the security risks but want to share files without running the wizard' to enable network file sharing.

Click 'Just enable file sharing' on the Enable File Sharing window and click OK.

Click OK on the drive or folder properties window since you do not need to create a new share name (the Aloha application software setup application creates the BOOTDRV share for you).

Refer to document AKBID1006 for more information on configuring Windows logins and shares for the Aloha application software.

If you are using Windows XP Professional, you are part of a domain and you wish to use user-level sharing, then you only need to refer to document AKBID1006 for more information on configuring Windows logins for the Aloha application software.

Refer to Microsoft Knowledge Base document Q304040 for more information on Windows XP file sharing.

Display Settings

Set the Color palette to 256 Colors or higher.� Aloha Technologies typically uses 16-bit color.�

Refer to document AKBID1165 for screen resolution settings.

Do not enable a Windows screen saver.

Time Zone & Daylight Savings

For the file server and all terminals to display the correct time and adjust to daylight savings changes properly, the time and date settings must be properly configured in Windows so the file server and each terminal have the same time, date, time zone and daylight savings settings.� The time settings need to be the same on all terminals and the file server.� If the area observes daylight savings, then you must configure the file server and each terminal to automatically adjust for daylight savings.� You can disable automatic daylight savings adjustment if you are in an area that does not recognize daylight savings time (or if you do not want the file server and terminals to automatically adjust for daylight savings), but it needs to be disabled throughout the Aloha application software.� You cannot enable daylight savings on one terminal and not on another or enable it on the file server and not the terminals.

FIFO Buffers

Windows XP enables First-In-First-Out (FIFO) buffers for each COM port.� These buffers tend to interfere with printers using Xon/Xoff flow control, so Aloha Technologies disables these buffers on all COM ports on all terminals, regardless of the printer type.� (In the event of a printer or COM port failure, a printer using Xon/Xoff flow control may be temporally connected to the port in the future.)

To access the FIFO buffer settings, select Start/Settings/Control Panel/System or right click My Computer and select Properties.� Select Hardware/Device Manager, and click the plus sign (+) next to Ports to expand it.� Select each port one at a time, and select Properties/Port Settings/Advanced.� Clear 'Use FIFO buffer'.� Repeat for each COM port.� The LPT port does not have this option.

Login Name

Refer to document AKBID1006 for more information on configuring Windows logins for the Aloha application software.

Processor Performance

By default, Windows XP is configured to assign foreground applications priority processing.� This can cause erroneous behavior in background applications, such as Control Server and EDC Server.� Aloha Technologies suggests setting the processor priority to background applications, but this can affect the FOH, which is also running on the file server.� If you experience problems with Control Server or EDC Server that you can attribute to processor time, consider changing the processor priority.

To configure the processor priority, open the System properties and select Advanced/Performance Options, and select Settings in the Performance section.� Select Advanced, and set the performance scheduling to Background Services.

Service Pack

Aloha Technologies recommends installing Windows XP Service Pack 1 after all software has been installed and Windows XP is configured properly.�

Reinstall the Service Pack anytime significant changes are made to Windows XP.

Install Aloha Software

Once Windows XP is set up according to the standards outlined in this document, use the Aloha Application Software Installation CD to install the Aloha application software.� Ensure you have enabled Windows file sharing as explained in the File Sharing section of this document before installing the Aloha application software.

Run ADVANCED.EXE from the Aloha POS CD.� The setup program walks you through the rest of the installation.� You must select 'Run Front of House and Back of House on same PC' on the Aloha Configuration window.

Refer to document AKBID1162 for more information on running Control Server and EDC Server as Windows services.

Once the installation is complete, you can edit user access to the BOOTDRV share if you have enabled user-level file sharing.

Restarting the FOH

Refer to document AKBID1116 for more information regarding restarting the FOH in this type of environment.�

Extended Information

Converting an Existing File Server to a File Server/Terminal

The steps for converting an existing file server to a file server/terminal depend on the usage.

If you are not going to make the file server/terminal master or server-capable (such as a COM interface server or a remote print server), then you can just add the MASTERCAPABLE, SERVERCAPABLE, LOCALDIR, TERM, CALIBRATE, and IBERROOT variables to the system environment variables and assign the proper values to them; and optionally configure a looping batch file to restart the FOH (refer to document AKBID1116).

If at any time you will make the file server/terminal master and/or server-capable, then you must add the MASTERCAPABLE, SERVERCAPABLE, LOCALDIR, TERM, CALIBRATE, and IBERROOT variables to the system environment variables and assign the proper values to them; rename the file server/terminal to match the TERMSTR+TERM nomenclature (Aloha Technologies suggests making it terminal one); and optionally configure a looping batch file to restart the FOH (refer to document AKBID1116).

Improving Performance

For additional performance, consider disabling features you do not plan to use, such as System Restore,

Remote Assistance, QoS Packet Scheduler, and Windows Messenger.

EOD File Copy Errors

If you are experience problems where the End-of-Day (EOD) process fails to copy files, you should perform the following in order to disable write caching for the hard drive in which the Aloha application software resides on the file server:

Open Windows Explorer, right-click on the hard drive in which the Aloha application software is installed, and select Properties.

Select the Hardware tab.

Select the physical drive, and select Properties.

Select the Policies tab.

Clear the 'Enable write caching on the disk' option, and press OK.

Caveats

Windows XP uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.� To eliminate this, disable Media Sense.

============================================================================

See also:

AKBID1005 Microsoft Windows Auto Log In

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1010 Aloha Application Software System Environment Variables

AKBID1018 Network Lana Numbers

AKBID1048 Aloha Application Software Hardware and OS Specifications

AKBID1176 Windows XP FOH Terminal Setup

AKBID1177 Windows XP File Server Setup

AKBID1116 File Server/Terminal Limitations

AKBID1148 Backup Procedures

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1165 FOH Screen Resolution Settings

AKBID1175 Aloha Terminal Restart Options

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1178 boh/foh bohfoh foh/boh fohboh stage staging terminal/server

Aloha BIN Folder Contents

Aloha BIN Folder Contents

============================================================================

AKBID1179

Created: 15 February 2001

Updated: 2 October 2003

Reviewed: 28 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 5.0x � 5.3.x

Subject: Aloha Application Software BIN Folder Contents File Types

============================================================================

Summary

The ALOHA^� application software BIN (binary) folder holds the core Aloha software applications and their associated files.� This document provides a brief description of each file.

The information in this document does not include the binary or application files for BackOffice add-ons.

Information

File Types

Extension

Name

Description

.BAT

Batch

Text-based file containing a series of commands, which are executed automatically in sequence.

.CNT

Contents

Table of contents for online help.

.EXE

Executable

Application files.

.DLL

Dynamic Link Library

A library of executable functions or data that can be used by an application.

.FTS

Full Text Search

Index file for online help searches

.GID

Global Index File

Index file for online help (usually hidden)

.HLP

Help

Online help for applications.

.IDL

Interface Definition Language

Used to develop applications that communicate with the Aloha application software using a Component Object Model (COM) interface.� These files are not required by the Aloha application software, and you can ignore or delete them.

.OCX

OLE Control Extension

An independent program module that can be accessed by other programs using an Object Linking and Embedding (OLE) Custom Control.

.MAP

Program structure file

Used by developers to track stack traces.

.TLB

Type-Library

Used to develop applications that communicate with the Aloha application software using a COM interface.� These files are not required by the Aloha application software, and you can ignore or delete them.

File List

File Name

Description

ALOHAFOH.IDL

FOH interface definition language file

ALOHAGL.DLL

Used with OpenGL 3D functionality in the FOH

ALOHALAB.DLL

Aloha Labor Scheduler Drop-down Menu Item module

ALOHALAB.TLB

Aloha Manager Labor Scheduler type-library

ALOHAMGR.EXE

Aloha Manager application

ALOHAMGR.TLB

Aloha Manager application type-library

ALOHAMGRCOMMON.TLB

Aloha Manager application type-library

ALOHAQSR.DLL

Interface to QSR Automations KDS software

ALOHASEC.EXE

Aloha BOH Security (logon) application

ALOHASEC.TLB

Aloha BOH Security (logon) application type-library

ALOHASPY.EXE

Aloha Spy (video security) application

ALOHASPY.TLB

Aloha Spy (video security) application type-library

AMGRPS.DLL

Aloha Manager Proxy/Stub module

AMGRSHIM.DLL

Used only in versions 5.0x, ActiveX controls module

AMGRSHIM.TLB

Used only in versions 5.0x, ActiveX controls module type-library

ARSEC.DLL

Remote Security module

ARSEC.TLB

Remote Security module type-library

ARSECPS.DLL

Remote Security Proxy/Stub module

ASECPS.DLL

Aloha Security Proxy/Stub module

ASPYPS.DLL

Aloha Spy Proxy/Stub module

CALCEDIT.OCX

Payment Reconciliation Calculator module

CALCEDITFIELD.TLB

Payment Reconciliation Calculator module type-library

CALIB.EXE

Elo TouchSystems calibration application (16-bit)

CB5.DLL

.DBF file format access module

CB532.DLL

.DBF file format access module

CDO32.DLL

Crystal Data Object module

CESSRVC.DLL

Aloha Remote HASP^� Key module

CESSVR.EXE

Aloha Remote HASP Key application

CESSVR.TLB

Aloha Remote HASP Key module type-library

CHITCFG.DLL

Renamed to INTERPRT.DLL, third-party printing module

CHITCFG.TLB

Renamed to INTERPRT.TLB, third-party printing module type-library

CHKINFO.EXE

Check Information application

CRPAIG32.DLL

Crystal Reports Text Object Support module

CRPE32.DLL

Crystal Reports Print Engine module

CTL4X.DLL

Aloha Manager Control (CTLSVR.EXE GUI) module

CTL4X.TLB

Aloha Manager Control (CTLSVR.EXE GUI) module type-library

CTLSVR.EXE

Control Server application

CTLSVR.TLB

Control Server application type-library

CTLSVRPS.DLL

Control Server Proxy/Stub module

DBCONFIG.EXE

Database Configuration utility

DBFDIFF.EXE

DBF Difference Utility

DBUP2.EXE

Database Update utility (database generation 2)

DBUP3.EXE

Database Update utility (database generation 3)

DRSQL.EXE

Dr.� SQL (SQL monitor) application

DW.DLL

EDC interface for Datawire Communications Networks, Inc.

ECARDPOS.CHM

Aloha eCard API reference

ECARDPOS.DLL

Aloha eCard Application Interface module

EDC.EXE

Electronic Draft Capture (EDCSVR.EXE GUI) application

EDCSEC.DLL

Electronic Draft Capture Security (login) module

EDCSEC.TLB

Electronic Draft Capture Security (login) module type-library

EDCSVR.EXE

Electronic Draft Capture Server application

EDCSVR.TLB

Electronic Draft Capture Server application type-library

EDCSVRPS.DLL

Electronic Draft Capture Server Proxy/Stub module

EDTPUNCH.DLL

Aloha Manager Edit Previous Day Clock Punches module

EDTPUNCH.TLB

Aloha Manager Edit Previous Day Clock Punches module type-library

ELOCALW.CPL

Elo TouchSystems Calibration Control Panel (16-bit)

ELOCALW.EXE

Elo TouchSystems Calibration application (16-bit)

ELOCALW.FTS

Elo TouchSystems Calibration online help search index

ELOCALW.GID

Elo TouchSystems Calibration online help index file (hidden)

ELOCALW.HLP

Elo TouchSystems Calibration online help

ERRMSG.EXE

N/A

FASTECH.DLL

BackOffice Application Interface module

FASTFOOD.IDL

QuickService interface definition language file

FASTFOOD.TLB

QuickService Order Entry application type-library

FPFLTR5.DLL

Installed and used by Veridicom thumbprint scanners

GRIND.EXE

TableService Grind application

GRINDQ.EXE

QuickService Grind application

HINSTALL.EXE

HASP^� Security Key Installation application

IBER.EXE

TableService Order Entry application

IBER.IDL

TableService interface definition language file

IBER.MAP

TableService Order Entry application program structure file

IBER.TLB

TableService Order Entry application type-library

IBERADM.DLL

Used to run external applications or batch files to administer the FOH

IBERPS.DLL

TableService Order Entry Application Proxy/Stub module

IBERQS.EXE

QuickService Order Entry application

IBERQS.MAP

QuickService Order Entry application program structure file

IBERQSPS.DLL

QuickService Order Entry Application Proxy/Stub module

IBERSQL.DLL

SQL database communication module

IBERSTR.DLL

Aloha Application Text String module

IMGSTUFF.DLL

Installed and used by Veridicom thumbprint scanners

IMPLODE.DLL

Crystal Reports module

INTERACT.DLL

Third-party interaction module type-library

INTERCEPTACTIVITY.TLB

Third-party activity module type-library

INTERCEPTPRINTING.TLB

Third-party printing module type-library

INTERPRT.DLL

Third-party printing module (not installed in versions 5.2.4.78 and higher)

KILLSVR.EXE

Service Termination application

KYQUAL.DLL

Installed and used by Veridicom thumbprint scanners

LABSCHED.EXE

Basic Labor Scheduler application

MFCOLEUI.DLL

Windows OLE User Interface module

MINULIB.DLL

Installed and used by Veridicom thumbprint scanners

MNT4X.DLL

Aloha Manager Maintenance module

MNT4X.TLB

Aloha Manager Maintenance module type-library

MPLAY.EXE

Media Player application

P2BXBSE.DLL

Crystal Report Physical Database module

P2SMON.DLL

Crystal Active Data Reporting module

PAYRECON.EXE

Payment Reconciliation application

PDBXBSE.DLL

Crystal Report Physical Database module

PGMFCT.DLL

Installed and used by Veridicom thumbprint scanners

PNLEDIT.CNT

Panel Editor table of contents for online help

PNLEDIT.FTS

Panel Editor online help search index

PNLEDIT.GID

Panel Editor online help index file (hidden)

PNLEDIT.HLP

Panel Editor online help

PROCRECS.EXE

Process Records application (used by CDM)

PRODSCHD.EXE

Production Schedule application

PROGTEST.EXE

Progressive KVS troubleshooting application

QSHELP.CNT

QuickService table of contents for online help

QSHELP.FTS

QuickService online help search index

QSHELP.GID

QuickService online help index file (hidden)

QSHELP.HLP

QuickService online help

QWERTY.OCX

Payment Reconciliation Keyboard module

QWERTY.TLB

Payment Reconciliation Keyboard module type-library

REGSVR32.EXE

.DLL Registration application

REPRINT.EXE

TableService BOH Reprint Guest Check and Employee Checkout application

REPRINTQ.EXE

QuickService BOH Reprint Guest Check and Employee Checkout application

RPT.EXE

BOH Report application

SETUPPOS.EXE

Aloha Application Software Installation application

SHW32.DLL

Win32 Memory Management module

STARTFOH.BAT

Delete %IBERDIR%\TMP\STOP batch file

STOPFOH.BAT

Create %IBERDIR%\TMP\STOP batch file

SUBRPT.EXE

BOH Subway Report application

SUM.EXE

Summary File Creation application

SVTEST.EXE

Select Electronics Video Test utility

TEAMSERV.EXE

Team Tip Distribution application

TIFFAPR.DLL

Installed and used by Veridicom thumbprint scanners

TSHELP.CNT

TableService table of contents for online help

TSHELP.FTS

TableService online help search index

TSHELP.GID

TableService online help index file (hidden)

TSHELP.HLP

TableService online help

U25DTS.DLL

Crystal Reports module

U2LDTS.DLL

Crystal Reports module

USERTOOL.DLL

Aloha Manager User Toolbar module

USERTOOLS.TLB

Aloha Manager User Toolbar module type library

VFPS.DLL

Installed and used by Veridicom thumbprint scanners

VFPSIMG.DLL

Installed and used by Veridicom thumbprint scanners

VFPSPLUS.DLL

Installed and used by Veridicom thumbprint scanners

VIDEO.EXE

Aloha Video application (Aloha Video only)

VIDEOMX.DLL

3^rd Party Video Interface module

VMATCHER.DLL

Installed and used by Veridicom thumbprint scanners

XMLKDS.DLL

Used by QSR Automations KDS software interface

XMLRDS.DLL

Used by QSR Automations KDS software interface

XMLTABLE.DLL

Used by QSR Automations KDS software interface

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1179 directory

�

Moving BackOffice Data

Moving BackOffice Data

============================================================================

AKBID1180

Created: 6 March 2001

Updated: 8 March 2004

Reviewed: 8 March 2004

Microsoft Windows Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

Subject: Moving the Aloha Application Software BackOffice Folders to a New Folder or Drive

============================================================================

Summary

The ALOHA^� application software BackOffice products utilize numerous Microsoft^� Windows^� registry entries in order to function properly.� For this reason, you should never move or relocate BackOffice products to another folder, logical drive, or computer by 'cutting and pasting' or copying the BackOffice folder from one location to another.� This document describes the steps required to move the BackOffice folder from one location to another as well as recovery instructions for BackOffice folders already improperly relocated.

Refer to document AKBID1128 for more information on moving Aloha application software sales data.

Refer to document AKBID1236 for more information on moving the CIM database.

Information

Perform one of the following (depending on the current state of the software) for each BackOffice module you are relocating:

If the BackOffice module is currently installed in one location and you need to move the software or data to another location (folder, drive, or computer):

1.        Refer to the table in the Data and Configuration Files section of this document to determine which data and configuration files you must backup before continuing to the next step.� Create backup copies of the files.

2.        Uninstall the BackOffice module using the Add/Remove Programs icon in the Windows Control Panel.

3.        Install the BackOffice module in the new location using the Aloha Installation CD.

4.        Restore the configuration files backed-up in step one to the new location.

5.        Following a successful confirmation of data integrity and product functionality in the new location, delete any remaining folders or files from the previous location.

If the BackOffice module was installed in one location and you have previously copied (not moved) the software or data to another location (folder, drive, or computer):

1.        Refer to the table in the Data and Configuration Files section of this document to determine which data and configuration files you must backup before continuing to the next step.� Create backup copies of the files.

2.        Uninstall the BackOffice module using the Add/Remove Programs icon in the Windows Control Panel.

3.        Install the BackOffice module in the new location (overwriting the existing files) using the Aloha Installation CD.

4.        Restore the configuration files backed-up in step one to the new location.

5.        Following a successful confirmation of data integrity and product functionality in the new location, delete any remaining folders or files from the previous location.

If the BackOffice module was installed in one location and you have previously moved (not copied) the software or data to another location (folder, drive, or computer):

1.        Refer to the table in the Data and Configuration Files section of this document to determine which data and configuration files you must backup before continuing to the next step.� Create backup copies of the files.

2.        Delete the BackOffice module's configuration information from the Windows Registry:

a)       To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

b)       Path out HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\CurrentVersion\Uninstall.

c)       Delete the folder representing the BackOffice module you are working with.

d)       Select Registry/Exit to exit the Windows Registry Editor.

e)       Restart Windows.

3.        Install the BackOffice module in the new location (overwriting the existing files) using the Aloha Installation CD.

4.        Restore the configuration files backed-up in step one to the new location.

Data and Configuration Files

BackOffice Product

Location

Files

All Products

\BACKOFFICE\LICENSE

FASTECH.LIC

Accounts Receivable (A/R)

\BACKOFFICE\DS

DSDATA.MDB, AR.INI

Advanced Reservations

\BACKOFFICE\AD

AD.INI, ADDATA.MDB

Aloha Labor Scheduler

\BACKOFFICE\SCHEDULE\DATA

All files

Corporate Reporting

\BACKOFFICE\DATABASE

FDATADW.MDB

Corporate Reporting

\DWX

All files

Delivery/Frequent Buyer

\BACKOFFICE\DS

DSDATA.MDB, DS.INI

Delivery/Frequent Buyer

\BACKOFFICE

AUTORUN.INI

Enterprise Messenger

\BACKOFFICE\ENTERPRISE MESSAGING

All files

Gift Certificates

\BACKOFFICE\GC

GC.INI, GCDATA.MDB

Gift Certificates

\BACKOFFICE

AUTORUN.INI

Inventory

\BACKOFFICE\DATABASE

~LFDATAS.MDB, B_FDATAS.MDB, FDATAS.MDB, FDATAS.INI

Extended Information

No information.

Caveats

The Aloha application software BackOffice products utilize numerous Windows registry entries in order to function properly.� For this reason, you should never move or relocate BackOffice products to another folder, logical drive, or computer by 'cutting and pasting' or copying the BackOffice folder from one location to another.

============================================================================

See also:

AKBID1128 Moving Aloha Data to a New File Server

AKBID1236 Moving a CIM SQL Database to a New File Server

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1180 reinstall

Using Interface Server as an Aloha Printer Server

Using Interface Server as an Aloha Printer Server

============================================================================

AKBID1181

Created: 29 March 2001

Updated: 15 May 2001

Reviewed: 9 December 2003

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.026 � 5.3.x

Subject: Using the Interface Server Feature to Create an Aloha Printer Server

============================================================================

Summary

The ALOHA^� application software added the Interface Server feature to enhance the support for installations that use the Component-Object-Model (COM) interface, such as handheld terminals, but you can also use the interface server feature to create a printer server for Front-of-House (FOH) receipt or remote printers.� For example, this feature enables you to attach receipt or remote printers to the Aloha file server or even setup a computer dedicated to driving receipt or kitchen printers.

Although this document only covers printers, you can attach other FOH-driven accessories using the same basic knowledge from this document.

Information

A History of Interface Server

The COM interface is an open standard by which two applications can communicate with one another.� This enables other software developers to interface their product with the Aloha application software without requiring any special changes to the Aloha application software.� Handheld terminals are a common example of this interface.�

The COM interface is part of IBER.EXE and IBERQS.EXE, also known as the FOH.� Since the FOH usually resides on dedicated FOH terminals and not the file server, the application that interfaces with the Aloha application software must reside on the FOH terminal as well.�

For example, Ameranth Wireless, Inc.^� develops software that enables handheld terminals to interface with the Aloha application software through Ameranth's 21^st Century Restaurant^� system and the COM interface.� The Ameranth software on the handheld terminal interfaces with the Ameranth software on the FOH terminal, which, in turn, interfaces via the COM interface with the Aloha application software FOH on the same terminal.

This creates a hardship for users who need to access the interface software on the FOH terminal because they may have to connect a keyboard to a FOH terminal in order to support or modify the software.� Users can overcome this buy purchasing an extra Aloha application software terminal license and running the FOH on the file server, but this creates an extra cost and forces users to navigate around the FOH application on the file server.� The interface server feature enables users to run the FOH on the file server (or any other computer) without these disadvantages.� The interface server feature instructs the FOH to run without a Graphical-User-Interface (GUI) and to not require an extra Aloha application software software license.� Even though the application is invisible to the user, all of the FOH functionality exists (it is the same FOH application as on the other FOH terminals), so support for printers and other peripherals still exists.

Configuring the Terminal

You can run the FOH (with the server interface feature) on either the file server or a dedicated computer.�

Regardless if you are configuring a file server or a dedicated computer to act as the printer server, do not count it in the quantity applied to the NUMTERMS (number of terminals) variable.

If you want to preserve Microsoft^� Windows^� double-click abilities, enable Doubleclick when you install the Aloha application software.

If you are going to use your file server as the server interface, use the appropriate Aloha Knowledge Base document to configure your file server as you would configure a standard file server running both the FOH and the Back-of-House (BOH) together.� Ensure you select 'Run Front of House and Back of House on same PC' when you are installing the Aloha application software software, but do not select Master Capable or File Server Capable (this does not effect the inherent file server capabilities of CTLSVR.EXE, or Control Server).

If you are running the server interface on your file server, you must apply the same limitations that are applied to a standard file server/terminal when restarting the FOH (server interface).� Refer to the 'Restarting the FOH' section of document AKBID1116 for more information.�

If you are going to use a dedicated computer for your printer server, use the appropriate Aloha Knowledge Base document to configure your computer as a standard FOH terminal.� Ensure you do not select Master Capable or File Server Capable when you are installing the Aloha application software software.

Configuring Aloha

Configure the interface server terminal in the Aloha application software as you would a standard terminal, except select 'Interface Server' in place of 'Order Entry' in terminal maintenance.

Configure printers connected to the interface server terminal as you would printers attached to standard order-entry terminals.

Extended Information

No information.

Caveats

Regardless if you are configuring a file server or a dedicated computer to act as the printer server, do not count it in the quantity applied to the NUMTERMS (number of terminals) variable.�

If you want to preserve Windows double-click abilities, enable Doubleclick when you install the Aloha application software.

If you are running the server interface on your file server, you must apply the same limitations that are applied to a standard file server/terminal when restarting the FOH (server interface).� Refer to the 'Restarting the FOH' section of document AKBID1116 for more information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1116 File Server/Terminal Limitations

AKBID1182 COM Interface Configuration

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1181 print server

style='mso-spacerun:yes'>� 2003

�

COM Interface Configuration

COM Interface Configuration

============================================================================

AKBID1182

Created: 2 April 2001

Updated: 17 September 2003

Reviewed: 10 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.026 � 5.3.x

Subject: Enabling and Configuring the Aloha Application Software COM Interface

============================================================================

Summary

The ALOHA^� application software enables interaction with third-party software through a Component-Object-Model (COM) interface.� This document explains how to enable the COM interface in the Aloha application software and the configuration options for existing COM applications, but application developers who want to develop a new application to communicate with the Aloha application software via a COM interface are handled on a case-by-case basis.� For more information on developing a COM-based interface with the Aloha application software, contact the Aloha Customer Service Center (CSC) at (817) 25-ALOHA (252-5642).

Information

A Brief Explanation of the COM Interface

Microsoft developed the COM interface to enable application developers to use a single standard for communication between multiple applications.� Aloha Technologies has enabled a COM interface in the Aloha application software Front-of-House (FOH) applications, IBER.EXE and IBERQS.EXE, to enable other applications to communicate with the FOH and perform FOH functions.� The Aloha application software Back-of-House (BOH) applications do not have the capability to interface with third-party software using a COM interface.

In order for other applications to communicate with the FOH applications via the COM interface, the application must reside on a terminal or computer that is also running the FOH applications.� The configuration requirements depend on the level of interaction between the third-party software and the FOH.� For example, a small utility that requires minimal interaction with guest checks requires a different setup than a complete third-party order-entry application.� This is required since a complete order-entry interface could interfere with someone entering orders through the FOH application on the same terminal as the interface.

Minimal COM Interaction

If you only require minimal COM interaction, such as with a small utility (for example, ADDGCTIP.EXE), then you can just enable the COM interface in the Aloha application software and place the third-party software (or utility) on the FOH terminals.� Remember, since only the FOH applications communicate via the COM interface, the third-party software must reside on a computer that is also running the FOH.

To enable the COM interface in the Aloha application software, open Aloha Manager, select Maintenance/Store Settings/System/Interfaces, and select 'Use FOH COM Interface'.� Refresh the system.

When the FOH restarts following the system refresh, each FOH terminal automatically registers IBER.EXE/IBERQS.EXE and IBERPS.DLL/IBERQSPS.DLL, and restarts a second time.

There are no visual indications of the COM interface activity in the FOH.

Once you have enabled the COM interface in the FOH, then you can configure the third-party application.

This type of configuration does not require any of the additional steps listed in this document.

Third-party Order Entry Software Configurations

If you are using the COM interface for a complete order-entry interface (for example, an interface to the Ameranth Wireless, Inc.^� 21^st Century Restaurant^� system or ORDERMAN), then you must utilize a specific setup based on the restaurant Point-of-Sale (POS) configuration.� Since the Aloha application software only provides communication via the COM interface through the FOH (IBER.EXE or IBERQS.EXE), then you must properly configure these applications on the same computer that is hosting the third-party application.� You must utilize one of the following configurations:

File Server � This is the most common method.� In this configuration, the Aloha application software uses a file server that is only intended to run the BOH, and it is not intended for use as a standard order-entry terminal.� The third-party application will also reside on the file server, so you will need to configure an Interface Server.

File Server/Terminal � Use this method of you intend to use the Aloha application software file server as both a file server and an order-entry terminal.� The third-party application will also reside on the file server/terminal, so you will need to configure an Interface Server on the file server in addition to your standard order-entry terminal.

FOH Terminal � Use this method if the third-party application will reside on an order-entry terminal.� For example, since a SuperSite does not have a dedicated file server for each store, you could load the third-party application on one of the order-entry terminals in each store, and use that terminal to provide the COM interface in addition to providing standard order-entry capabilities.

Dedicated COM Interface Computer � Use this method if the third-party application will reside on a computer that is dedicated to providing the interface between the third-party software and the Aloha application software.� For example, since a SuperSite does not have a dedicated file server for each store, you could load the third-party application on a dedicated interface computer for each store, and use that computer to provide the COM interface.

Refer to the appropriate section below for more information on setting up one of the above configurations.

Use the File Server to Host the COM Interface

You are required to use Windows NT^�, Windows 2000, Windows XP, or Windows Server 2003 on the Aloha application software file server if you are going to configure it to host the COM interface.

�

Configure Windows on your file server as you would configure a standard file server by using the appropriate Aloha Knowledge Base (AKB) document, and install the Aloha application software as you would a standard file server.� Since the COM interface host is neither master-capable nor server-capable, you do not need to configure the file server's network name using a TERMSTR+TERM nomenclature, but instead use a standard file server name such as ALOHABOH.�

Configure the standard FOH terminals in a normal fashion using the appropriate AKB document.

Configure the instance of the FOH that will run on the file server as an Interface Server by creating a new terminal in Aloha Manager, assign it the next available unused ID number, and select Interface Server instead of Order Entry terminal.� 'Interface Server' instructs the FOH to not display a GUI, and it does not count against the number of terminals for which you are licensed.� Do not include the interface server when assigning your NUMTERMS system environment variable on the file server or the FOH terminals.

To enable the COM interface in the Aloha application software, open Aloha Manager, select Maintenance/Store Settings/System/Interfaces, and select 'Use FOH COM Interface'.

Refresh the system.

When the FOH restarts on the standard FOH terminals following the system refresh, each FOH terminal will automatically register IBER.EXE/IBERQS.EXE and IBERPS.DLL/IBERQSPS.DLL, and restart a second time.� Once the terminals have restarted, there are no visual indications of the COM interface activity on the standard FOH terminals.

Download WAIT.EXE from the Aloha Technologies FTP site and place it in the Aloha application software BIN folder on the file server.� WAIT.EXE enables you to add timed pauses to batch files and is referred to later in this document.� Refer to document AKBID1012 for more information on WAIT.EXE.

Create a batch file in the file server's Aloha application software folder, and label is using the interface server's terminal number (for example D:\ALOHA\TERM5.BAT).� Besides declaring the LOCALDIR, TERM, DOUBLECLICK, and NOFATALMSGBOX variables, the batch file should disable master and server capabilities, and have logic to make it a looping batch file.� This ensures that the interface server automatically restarts (after pausing for 15 seconds) following a refresh or the EOD process.� For example:

@ECHO OFF

:TOP

CLS

ECHO *** Do not close this batch file. ***

ECHO *** It is required to auto restart ***

ECHO *** the Aloha COM interface. ***

SET TERM=5

SET LOCALDIR=D:\%IBERROOT%

SET DOUBLECLICK=TRUE

SET NOFATALMSGBOX=TRUE

SET MASTERCAPABLE=FALSE

SET SERVERCAPABLE=FALSE

IF EXIST %LOCALDIR%\TMP\EXITING DEL %LOCALDIR%\TMP\EXITING

START /WAIT %LOCALDIR%\BIN\IBER.EXE

CLS

ECHO *** Waiting 15 seconds for refresh. ***

%LOCALDIR%\BIN\WAIT.EXE 15

GOTO TOP

This batch file performs the following functions:

Disables unneeded text from appearing on the screen.

Clears the screen.

Displays a warning to not close the batch file, since it is essential for restarting the COM interface.

Assigns values the LOCALDIR and TERM system environment variables.

Uses the DOUBLECLICK system environment variable to enable double-click ability while the interface server is running.

Uses the NOFATALMSGBOX system environment variable to prevent the interface server from hanging on a message confirmation.

Disables master and server capability (this does not effect the inherent file server capabilities of CTLSVR.EXE, or Control Server).

Deletes the EXITING file, if it exists.

Starts the interface server (IBER.EXE or IBERQS.EXE) using the START /WAIT command.� The START /WAIT command instructs the batch file to wait for the FOH to exit before proceeding to the next line in the batch file.� '/WAIT' is in no way connected with the WAIT.EXE utility described later in this document.� /WAIT is a standard Microsoft command-line variable, and WAIT.EXE is a utility supplied by Aloha Technologies.

After the interface server exits, the batch file clears the screen.

The batch file clears the screen, uses the WAIT.EXE utility to create fifteen-second pause while the BOH finishes the refresh procedure, and starts the batch file over again.

The batch file is always active on the file server, and it continually restarts the interface server anytime it exits.� Since this terminal is designated an interface server, you will not see it running unless you view the Windows Task Manager.� Place shortcuts to the batch file (instead of shortcuts directly to IBER.EXE or IBERQS.EXE) in the Windows StartUp folder, desktop, and the Start Menu.

Once you have enabled the COM interface and the interface server in the file server, then you can configure the third-party application.

Use a File Server/Terminal to Host the COM Interface

You are required to use Windows NT, Windows 2000, Windows XP, or Windows Server 2003 on the Aloha application software file server/terminal if you are going to configure it to host the COM interface.

�

Configure Windows on your file server/terminal as you would configure a standard file server/terminal by using the appropriate AKB document, and install the Aloha application software as you would a standard file server/terminal.�

Configure the standard FOH terminals in a normal fashion using the appropriate AKB document.

The file server/terminal will run two instances of the FOH: one for order entry, and one for the COM interface.� After you create the instance of the FOH that will run on the file server/terminal for standard order-entry usage (usually terminal one) in Aloha Manager, you must also configure the instance of the FOH that will run on the file server as an Interface Server by creating a new terminal in Aloha Manager, assign it the next available unused ID number, and select Interface Server instead of Order Entry terminal.� 'Interface Server' instructs the FOH to not display a GUI, and it does not count against the number of terminals for which you are licensed.� Do not include the interface server when assigning your NUMTERMS system environment variable on the file server/terminal or the FOH terminals.

To enable the COM interface in the Aloha application software, open Aloha Manager, select Maintenance/Store Settings/System/Interfaces, and select 'Use FOH COM Interface'.

Refresh the system.

When the FOH restarts on the standard FOH terminals following the system refresh, each FOH terminal will automatically register IBER.EXE/IBERQS.EXE and IBERPS.DLL/IBERQSPS.DLL, and restart a second time.� Once the terminals have restarted, there are no visual indications of the COM interface activity on the standard FOH terminals.

Download WAIT.EXE from the Aloha Technologies FTP site and place it in the Aloha application software BIN folder on the file server.� WAIT.EXE enables you to add timed pauses to batch files and is referred to later in this document.� Refer to document AKBID1012 for more information on WAIT.EXE.

Since you will have two instances of the FOH running on the file server/terminal (one for order-entry and the other as the interface server for the COM interface), you must be able to differentiate the two so the third-party software communicates with the interface server rather than instance used for order-entry.� The easiest way to accomplish this is to rename the application used for order entry.� For example, if you copy IBER.EXE or IBERQS.EXE to IBEROE.EXE, then the instance of IBER.EXE or OBERQS.EXE for order entry will run IBEROE.EXE while the interface terminal will run IBER.EXE or IBERQS.EXE.� When the third-party application attempts in interact with 'IBER.EXE' or 'IBERQS.EXE', then it will interact with the interface server rather than the order entry instance ('IBEROE.EXE').

In order to perform this, you must edit the existing looping batch file for the order-entry instance that you created when originally configuring the file server/terminal in accordance with the appropriate AKB document.� Replace the portion of the batch file that states 'START /WAIT %LOCALDIR%\BIN\IBER.EXE' with the following:

ECHO Y | COPY %LOCALDIR%\BIN\IBER.EXE %LOCALDIR%\BIN\IBEROE.EXE

START /WAIT %LOCALDIR%\BIN\IBEROE.EXE

This ensures that the copy of IBEROE.EXE always matches IBER.EXE or IBERQS.EXE, and starts IBEROE.EXE rather than IBER.EXE or IBERQS.EXE.

Create a second batch file in the file server/terminal's Aloha application software folder to start the interface server, and label is using the interface server's terminal number (for example D:\ALOHA\TERM5.BAT).� Besides declaring the TERM, DOUBLECLICK, and NOFATALMSGBOX variables, the batch file should disable master and server capabilities, and have logic to make it a looping batch file.� This ensures that the interface server automatically restarts (after pausing for 15 seconds) following a refresh or the EOD process.� For example:

@ECHO OFF

:TOP

CLS

ECHO *** Do not close this batch file. ***

ECHO *** It is required to auto restart ***

ECHO *** the Aloha COM interface. ***

SET TERM=5

SET DOUBLECLICK=TRUE

SET NOFATALMSGBOX=TRUE

SET MASTERCAPABLE=FALSE

SET SERVERCAPABLE=FALSE

IF EXIST %LOCALDIR%\TMP\EXITING DEL %LOCALDIR%\TMP\EXITING

START /WAIT %LOCALDIR%\BIN\IBER.EXE

CLS

ECHO *** Waiting 15 seconds for refresh. ***

%LOCALDIR%\BIN\WAIT.EXE 15

GOTO TOP

This batch file performs the following functions:

Disables unneeded text from appearing on the screen.

Clears the screen.

Displays a warning to not close the batch file, since it is essential for restarting the COM interface.

Assigns a value the TERM system environment variable.

Uses the DOUBLECLICK system environment variable to enable double-click ability while the interface server is running.� If you are using QuickService, this might interfere with the use of the order-entry instance of IBERQS.EXE.� If it does, then remove this variable from the batch file.

Uses the NOFATALMSGBOX system environment variable to prevent the interface server from hanging on a message confirmation.

Disables master and server capability (this does not effect the inherent file server capabilities of CTLSVR.EXE, or Control Server).

Deletes the EXITING file, if it exists.

Starts the interface server (IBER.EXE or IBERQS.EXE) using the START /WAIT command.� The START /WAIT command instructs the batch file to wait for the FOH to exit before proceeding to the next line in the batch file.� '/WAIT' is in no way connected with the WAIT.EXE utility described later in this document.� /WAIT is a standard Microsoft command-line variable, and WAIT.EXE is a utility supplied by Aloha Technologies.

After the interface server exits, the batch file clears the screen.

The batch file clears the screen, uses the WAIT.EXE utility to create fifteen-second pause while the BOH finishes the refresh procedure, and starts the batch file over again.

Like the batch file for the order-entry instance, the batch file for the interface server is always active on the file server, and it continually restarts the interface server anytime it exits.� Since this terminal is designated an interface server, you will not see it running unless you view the Windows Task Manager.� Place shortcuts to the batch file (instead of shortcuts directly to IBER.EXE or IBERQS.EXE) in the Windows StartUp folder, desktop, and the Start Menu.

Once you have enabled the COM interface and the interface server in the file server/terminal, then you can configure the third-party application.

Use a FOH Terminal to Host the COM Interface

You are required to use Windows NT, Windows 2000, Windows XP, or Windows Server 2003 on the FOH terminal if you are going to configure it to host the COM interface.

�

Configure Windows on your FOH terminal/interface server as you would configure a standard FOH terminal by using the appropriate AKB document, and install the Aloha application software as you would a standard FOH terminal.�

Configure the file server and any additional FOH terminals in normal fashions using the appropriate AKB documents.

The FOH terminal/interface server will run two instances of the FOH: one for order entry, and one for the COM interface.� After you create the instance of the FOH that will run on the FOH terminal/interface server for standard order-entry usage in Aloha Manager, you must also configure the instance of the FOH that will run on the FOH terminal/interface server as an Interface Server by creating a new terminal in Aloha Manager, assign it the next available unused ID number, and select Interface Server instead of Order Entry terminal.� 'Interface Server' instructs the FOH to not display a GUI, and it does not count against the number of terminals for which you are licensed.� Do not include the interface server when assigning your NUMTERMS system environment variable on the file server or the FOH terminals.

To enable the COM interface in the Aloha application software, open Aloha Manager, select Maintenance/Store Settings/System/Interfaces, and select 'Use FOH COM Interface'.

When the FOH restarts following the system refresh, each FOH terminal will automatically register IBER.EXE/IBERQS.EXE and IBERPS.DLL/IBERQSPS.DLL, and restart a second time.� Once the terminals have restarted, there are no visual indications of the COM interface activity on the standard FOH terminals.

Refresh the system.

Since you will have two instances of the FOH running on the FOH terminal/interface server (one for order-entry and the other as the interface server for the COM interface), you must be able to differentiate the two so the third-party software communicates with the interface server rather than instance used for order-entry.� The easiest way to accomplish this is to rename the application used for order entry.� For example, if you copy IBER.EXE or IBERQS.EXE to IBEROE.EXE, then the instance of IBER.EXE or IBERQS.EXE for order entry will run IBEROE.EXE while the interface terminal will run IBER.EXE or IBERQS.EXE.� When the third-party application attempts in interact with 'IBER.EXE' or 'IBERQS.EXE', then it will interact with the interface server rather than the order entry instance ('IBEROE.EXE').

In order to perform this, you must edit the existing looping batch file for the order-entry instance that you created when originally configuring the FOH terminal/interface server in accordance with the appropriate AKB document.� Replace the portion of the batch file that states 'START /WAIT %LOCALDIR%\BIN\IBER.EXE' with the following:

ECHO Y | COPY %LOCALDIR%\BIN\IBER.EXE %LOCALDIR%\BIN\IBEROE.EXE

START /WAIT %LOCALDIR%\BIN\IBEROE.EXE

This ensures that the copy of IBEROE.EXE always matches IBER.EXE or IBERQS.EXE.

Create a second batch file in the FOH terminal/interface server's Aloha application software folder to start the interface server, and label it using the interface server's terminal number (for example D:\ALOHA\TERM5.BAT).� For example:

SET IBERROOT=ALOHA

SET LOCALDIR=%IBERROOT%

SET MASTERCAPABLE=FALSE

SET NOFATALMSGBOX=TRUE

SET NUMTERMS=4

SET SERVER=ALOHABOH

SET SERVERCAPABLE=FALSE

SET TERM=5

SET TERMSTR=TERM

IF EXIST %LOCALDIR%\TMP\EXITING DEL %LOCALDIR%\TMP\EXITING

START %LOCALDIR%\BIN\IBER.EXE

This batch file performs the following functions:

Assigns values to the IBERROOT, LOCALDIR, NUMTERMS, SERVER, TERM, and TERMSTR system environment variables.

Disables master and server capabilities.

Uses the NOFATALMSGBOX system environment variable to prevent the interface server from hanging on a message confirmation.

Deletes the EXITING file, if it exists.

Starts the interface server (IBER.EXE or IBERQS.EXE).

Since this terminal is designated an interface server, you will not see it running unless you view the Windows Task Manager.� Place shortcuts to the batch file (instead of shortcuts directly to IBER.EXE or IBERQS.EXE) in the Windows StartUp folder, desktop, and the Start Menu.

Once you have enabled the COM interface and the interface server on the FOH terminal/interface server, then you can configure the third-party application on the FOH terminal/interface server.

Use a Dedicated COM Interface Server to Host the COM Interface

The COM server will run the FOH like a standard order-entry terminal, but it will do so as an interface server, so you must configure an instance the terminal as an interface server by creating a new terminal in Aloha Manager as you would if the terminal were standard order-entry terminal, and select Interface Server instead of Order Entry terminal.� Interface server instructs the FOH to not display a GUI, and it does not count against the number of terminals for which you are licensed.� Do not include the COM server when assigning your NUMTERMS system environment variable on the file server or the FOH terminals.

Refresh the system

Configure Windows on your COM server as you would configure a standard FOH terminal by using the appropriate AKB document, and install the Aloha application FOH software as you would a standard FOH terminal, but do not enable the Master Capable or Server Capable options when you run SETUPTRM.EXE.� Also ensure that you enable the AUTOEXIT option in SETUPTRM.EXE in order for the COM server to properly restart following refreshes and the EOD process.

Configure the file server and any additional FOH terminals in normal fashions using the appropriate AKB documents.

To enable the COM interface in the Aloha application software, open Aloha Manager, select Maintenance/Store Settings/System/Interfaces, and select 'Use FOH COM Interface'.

When the FOH restarts following the system refresh, each FOH terminal will automatically register IBER.EXE/IBERQS.EXE and IBERPS.DLL/IBERQSPS.DLL, and restart a second time.� Once the terminals have restarted, there are no visual indications of the COM interface activity on the standard FOH terminals.

Once you have enabled the COM interface and the interface server on the COM server, then you can configure the third-party application on the COM server.

Extended Information

Old Application Files

If you have older copies of unused application files in your BIN folder, then they can inhibit the Aloha application software from properly registering the current versions of files required by the COM interface.�

For example, if you have a TableService system that also has old versions of the QuickService binary files in the BIN folder, then you will have the following files in your BIN folder:

IBER.EXE (current version)

IBERPS.DLL (current version)

IBERQS.EXE (old version)

IBERQSPS.DLL (old version)

The FOH will register both sets of binaries in alphabetical order, with the last set overwriting the first set.� So, the older version of IBERQS.EXE will overwrite the registration of the current version of IBER.EXE, and the older version of IBERQSPS.DLL will overwrite the registration of the current version of IBERQSPS.DLL.

If this occurs, remove the unused binary files from the BIN folder on both the file server and each FOH terminal, and restart the FOH.� The FOH will properly register the correct files.

Manually Registering Files

The Aloha application software is designed to automatically register the required application files for the COM interface, but you might have to manually register the applications in rare cases.� To manually register the Aloha application software FOH applications in order to interact via the COM interface, open a command prompt on each computer in which COM interaction will occur, type the following commands (use IBERQS.EXE and IBERQSPS.EXE for QuickService), and restart the computer:

IBER.EXE /REGSERVER

REGSVR32.EXE IBERPS.DLL

Depending on your operating system configuration, you might have to include the path to REGSVR32.EXE in the command line.

Caveats

No information.

============================================================================

See also:

AKBID1012 Aloha Application Software Utility Description and Usage

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1182 ameranth ce faceless hand held pocketpc

style='mso-spacerun:yes'>� 2003

�

Recommended Hard Drive Partitions, File Systems, and Setup

Recommended Hard Drive Partitions, File Systems, and Setup

============================================================================

AKBID1183

Created: 26 April 2001

Updated: 10 April 2003

Reviewed: 28 January 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 4.2x � 5.3.x

Subject: Recommended Hard Drive Partitions, File Systems, and Setup for the Aloha Application Software

============================================================================

Summary

Although there is not a required standard for the hard drive partitioning scheme used with the ALOHA^� application software, Aloha Technologies does suggest standards to enable the most recovery and fault tolerance options.� This document explains some of these partitioning scheme options.

Information

File Server Hard Drive Size

The Aloha application software application and configuration files require less than 200 megabytes of disk space (less than 100 megabytes in most cases), but you will need more than that to store historical data.� The amount of historical data, the operating system (OS), and additional third-party software all play a role in the required hard drive size.

In general, historical data requires approximately three megabytes of hard drive space each day, but this can vary between locations because of the size of the configuration data (number of items, employees, panels, submenus, and so on) and the amount of transaction performed each day (transaction log size).

At the time of this writing, a 20-gigabyte hard drive is about the smallest IDE-based 3.5" hard drive readily available for file servers.� In this case, you would be able to store about eighteen years of historical data, although this could vary with the OS, file system, amount of third-party software installed, Aloha configuration, and the number of daily transactions.

If the site is using a Relation-Database (RDB), historical data is stored in both dated folders and in the RDB, but the information contained in the dated folders is only required for reprinting guest checks, employee checkouts, and audit reports.� All other reports use the data from the RDB.� The RDB decreases the number of historical dated folders a site needs to keep readily available since long-term sales data is gleaned from the RDB.� For example, although a site may want to report sales for the previous year, they may only need the ability to reprint checks and checkouts for the previous three months, so they only require approximately 300 megabytes of storage for dated folders.� After three months, the can compress and archive the dated folders.� Compressed dated folders typically range from 500 kilobytes to one megabyte in size.� The RDB requires approximately one megabyte for each day, so even with an RDB, the 20-gigabyte hard drive is a sufficient starting point.� The daily RDB usage varies with the table population options you select the in the Aloha application software.

SuperSites follow the above RDB rules, but you must multiply them for each store.� For example, a 10-store SuperSite will require approximately 10 megabytes per day for historical data in the RDB (one megabyte per store).� Since a SuperSite stores dated folders on the order entry terminals, they are not a factor in the file server's hard drive size, although you should consider archiving dated folders to the file server or backup media.

File Server Partitions

Aloha Technologies suggests using multiple partitions on the file server to increase fault tolerance and enable easier recovery.� For example, by placing Microsoft^� Windows^� on a separate partition from the Aloha application software, you could format drive C: and reinstall Windows without harming the Aloha application software configuration or historical files.� You would have to reinstall the Aloha application software to restore various Windows files and settings used by the Aloha application software, but your data would remain intact.� The same reasoning applies to installing your RDB in a separate partition or using a separate partition to store your archived files.

Below is a suggested drive partition layout that is typically used on a 20-gigabyte drive on a site using dbf-based database files.�

Partition Letter

Partition Label

Partition Size

Partition Use

C:

WINDOWS

4 Gigabytes

Windows and non-Aloha applications

D:

ALOHA

12 Gigabytes

Aloha applications and data

E:

ARCHIVE

4 Gigabytes

Aloha data archive

Partition C: is intended for Windows and non-Aloha applications such as Symantec^� pcANYWHERE^� and Microsoft Office^�.

Partition D: is strictly for the Aloha application software and Aloha BackOffice use.� This partition is the largest of the three in order to hold more dated subdirectories for report viewing.� If you have a hard drive larger than 20 gigabytes, this is the partition that should receive the extra space.

Partition E: is used for archiving historical data such as dated folders and Electronic Draft Capture (EDC) settlement files.� Refer to document AKBID1148 for more information.

If the site is using a Microsoft SQL Server Relational Database (RDB) or a Microsoft Database Engine (MSDE) database, the recommended drive partitions change somewhat.� Below is a suggested drive partition layout that is typically used on a 20-gigabyte drive.

Partition Letter

Partition Label

Partition Size

Partition Use

C:

WINDOWS

4 Gigabytes

Windows and non-Aloha applications

D:

ALOHA

4 Gigabytes

Aloha applications

E:

RDB

10 Gigabytes

Aloha RDB database

F:

ARCHIVE

2 Gigabytes

Aloha data archive

Partition C: is intended for Windows and non-Aloha applications such as pcANYWHERE, Microsoft Office, and the intended RDB engine.�

Partition D: is strictly for the Aloha application software and Aloha BackOffice use.� This partition is only two gigabytes since the RDB database replaces most of the dated subdirectory's responsibilities and fewer dated folders are required.�

Partition E: is used solely for the RDB database.� This partition requires the extra space to store the most historical information.� If you have a hard drive larger than 20 gigabytes, this is the partition that should receive the extra space.�

Partition F: is used for archiving historical data such as dated folders and EDC settlement files.� Refer to document AKBID1148 for more information.

File Systems

What file system to use with each partition is more a question of OS and hard drive size compatibility than anything else, although some file systems have more options, such as partition sizes, reduced cluster sizes (usually at the price of speed), and file sizes.� Since the file system offers no direct functional advantage the Aloha application software, there are no standard recommendations.

The following table lists file system compatibility with operating systems:

Operating System

FAT16

FAT32

NTFS

Windows 95 (OSR2 and higher)

Yes

Yes

No

Windows 98

Yes

Yes

No

Windows Me

Yes

Yes

No

Windows NT

Yes

No

Yes

Windows 2000

Yes

Yes

Yes

Windows XP

Yes

Yes

Yes

Windows Server 2003

Yes

Yes

Yes

The following table lists the features and advantages of each operating system:

RDB users should note that only NTFS supports files larger than four gigabytes.

Feature

FAT16

FAT32

NTFS

Minimum partition size

n/a

512 megabytes

20 megabytes

Maximum partition size

2 gigabytes

2 terabytes

16 exabytes

Maximum file size

2 gigabytes

4 gigabytes

n/a

Space efficiency

Poor

Good

Good

FOH Hard Drive Configuration

Front-of-House (FOH) terminals do not contain as much data as the file server does nor is there any data that is not usually recoverable elsewhere in the Aloha application software.� Therefore, with the exception of SuperSites or using the FOH terminal to store archived data, FOH terminal partition and file system configuration is up to personal preference.

The Aloha application software requires approximately 80 to 100 megabytes for its core files, but this size will vary with each database.� You also need to consider extra space for the Debugging-Output-Files (debouts) and any dated folders that are created if the file server is down.� When possible, you should allocate at least 200 megabytes for the Aloha application software in order to sure uninterrupted functionality, although Aloha Technologies recommends two-gigabytes for s standard site and four-gigabytes for a SuperSite.

Since SuperSites store dated folders on the terminals, you should consider using a larger hard drive and creating separate partitions for Windows and the Aloha application software.� As stated previously in this document, expect dated folders to consume approximately three megabytes per day.

If you plan to archive historical data to FOH terminals, then you should consider a larger hard drive and separate partitions.� In this case, separate partitions for Windows, the Aloha application software, and archived information might be the best configuration.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

AKBID1148 Backup Procedures

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1183 disk diskspace edition harddisk harddrive install millennium

Consolidated Kitchen Chit Ingredient Tags

Consolidated Kitchen Chit Ingredient Tags

============================================================================

AKBID1184

Created: 17 April 2001

Updated: 18 April 2001

Reviewed: 24 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.225 � 5.3.x

Subject: Listing Consolidated Ingredients on Kitchen Chits Using CHITTAG.CFG

============================================================================

Summary

The ALOHA^� application software enables you to print a consolidated summary of ingredient information on the bottom of kitchen chits by configuring the CHITTAG.CFG.� You can utilize this feature to print some or all of the ingredients needed to prepare the items listed on the chit, such as the total number if steaks or shrimp needed for the entire table.

Information

To enable the consolidated ingredient summary on kitchen chits, create a new text file in the Aloha application software DATA folder labeled CHITTAG.CFG.� This file both enables the consolidated ingredient information feature as well as configures it.� There are no other variables required to enable this feature.

CHITTAG.CFG lists each item, the ingredient label, and the quantity using the following format:

ITEM_ID,<space>INGREDIENT_LABEL,<space>QUANTITY

ITEM_ID is a numeric field that lists the item's ID number assigned in the Aloha application software.� INGREDIENT_LABEL is an alphanumeric field that lists the ingredient associated with the item.� The ingredient label is limited to 80 characters.� For example, on a shrimp dinner, you might use 'SHRIMP' as the ingredient label.� QUANTITY is a numeric field that lists the weight or quantity associated with the ingredient label.� For example, if six shrimp come with the shrimp dinner, then you would use '6' as the quantity.

An example of this feature's usage is a Japanese steakhouse.� The chef must prepare the food cart before taking it out to the dining room in order to prepare the food in front of the client.� Assume that the steak dinner is item 1001 and uses 12 ounces of steak.� The shrimp dinner is item 1002 and uses 12 shrimp.� The steak and shrimp dinner is item 1003, and it uses eight ounces of steak and eight shrimp.� The chef needs a listing at the end of the kitchen chit showing the amount of steak and shrimp to place on the food cart.� In this case, you would add the following to CHITTAG.CFG (note that an item number can be listed multiple times):

1001, oz STEAK, 12

1002, SHRIMP, 12

1003, oz STEAK, 8

1003, SHRIMP, 8

If one of each item is ordered, the kitchen chit appears as the following:

STEAK DINNER

SHRIMP DINNER

STEAK & SHRIMP DINNER

---------------------------

20 oz STEAK

20 SHRIMP

The quantities are always consolidated in the summary section regardless of how the chit consolidation options are configured in Aloha Maintenance or Aloha Manager.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1184 bar chittag chittags consolidate house itemize itemized list many recipe requisition

�

Using TSButton.cfg to Launch Applications from TableService

Using TSButton.cfg to Launch Apps from TableService

============================================================================

AKBID1185

Created: 27 April 2001

Updated: 29 August 2003

Reviewed: 8 March 2004

Microsoft Windows Versions: All

Aloha Products: TableService

Aloha POS Versions: 5.2x - 5.3.x

Subject: Using TSButton.cfg to Launch Applications from TableService

============================================================================

Summary

TSButton.cfg enables you to launch external applications from the ALOHA^� application software TableService Front-of-House (FOH) Order Entry and Close Check screens.� You can use this to launch various third-party applications, batch files and Microsoft^� Windows^� applications such as calculator.

Information

Configuration

TSButton.cfg is a text file that resides in the Data folder and is enabled by its existence.� There are not any other switches required to enable it.

Do not include a copy of the TSButton.cfg in your Newdata folder, since it can overwrite the active copy in the Data folder if you refresh the system.

Configure TSButton.cfg using the following format:

TYPE,ID,INDEX,NAME,COMMAND,CONTEXT

TYPE specifies where the button will appear:

1 � Submenu button on the Order Entry screen

2 � Tender button on the Close Check screen

3 � Promo button on the Close Check screen

4 � Comp button on the Close Check screen

ID is the submenu ID if the button type is 1.� Otherwise this is 0.

INDEX is the position on the submenu or payment menu.� The buttons are numbered vertically, so if you are using a 3x7 button grid, the buttons are numbered as the following:

�

1

8

15

2

9

16

3

10

17

4

11

18

5

12

19

6

13

20

7

14

21

The second page of the submenu or payment menu starts with button 22 and continues to button 42.� If you place a button created in TSButton.cfg on the second page of a submenu or payment menu, there must be an existing item or payment button, otherwise the user will not be able to scroll to the second page and access the button created with TSButton.cfg.

NAME is the button label.� You can use '\n' to create a line break just as you would with a standard submenu or payment label.

COMMAND is the command line assigned to the button.

CONTEXT passes extended command line information to the command line in the form of the following command line variables:

/TermID <terminal ID>

/EmpNumber <current employee number>

/TableId <current tabloe ID>

/CheckId <current check number>

/OPOSMSR <OPOS magnetic stripe reader (MSR) name, if applicable>

These variables enable application developers to include variables from the Aloha application software in order to enhance their application's capabilities.� Set CONTEXT to 1 to enable the extended information or 0 to disable the extended information.� Enabling the extended information includes all of the above variables.

Examples

The following TSButton.cfg entry places a button in position five on submenu 102 that opens calculator:

1,102,5,Win\nCalc,calc.exe,0

The following TSButton.cfg entry places a button in position ten on the payment menu that opens C:\Aloha\Warning.txt using notepad:

2,0,10,Warning,notepad.exe c:\aloha\warning.txt,0

The following TSButton.cfg entry places a button in position 25 on the promo menu that enables an application called C:\Util\Promover.exe and uses the extended command line variables (Promo.exe is an example � it is not an existing Aloha application):

3,0,25,Verify,c:\util\promover.exe,1

The following TSButton.cfg entry places a button in position one on the comp menu that opens Windows Sound Recorder, plays C:\Waves\Manager.wav once, and exits:

4,0,1,Message,sndrec32.exe /play /close c:\waves\manager.wav,0

Troubleshooting

When you select a button created with TSButton.cfg, the command line issued by the button is recorded in the terminal's Debugging-Output-File (debout).� Use this information to verify that your command lines are functioning properly.

Test your command lines using either a Windows command prompt or by selecting Start/Run, entering the command line, and clicking OK.� If the command lines work in these environments, they should work with TSButton.cfg.� If they do not work in these environments, they will not work with TSButton.cfg.

Verify that you did not enable the extended command line variables via the CONTEXT field.� These variables can interfere with some applications, such as notepad.

Extended Information

Mplay.exe

If you are using TSButton.cfg to display video files, consider using Mplay.exe, which is included in the Aloha application software's Bin folder.� While Mplay.exe only supports a limited number of formats, it is a small and simple application, so it initializes relatively quickly.� If it supports your file format, then you should consider using it.� The best way to determine support is to test it with your file.� The usage is Mplay.exe <video file's path and name>.

Caveats

Do not include a copy of the TSButton.cfg in your Newdata folder, since it can overwrite the active copy in the Data folder if you refresh the system.

If you place a button created in TSButton.cfg on the second page of a submenu or payment menu, there must be an existing item or payment button, otherwise the user will not be able to scroll to the second page and access the button created with TSButton.cfg.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1185 config executable fire program ts tsbutton

�

FOH Manual and Magnetic Stripe Passwords

FOH Manual and Magnetic Stripe Passwords

============================================================================

AKBID1186

Created: 3 May 2001

Updated: 13 June 2001

Reviewed: 20 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

Subject: Aloha Application Software FOH Manual and Magnetic Stripe Passwords

============================================================================

Summary

The ALOHA^� application software enables you to log in to the Front-of-House (FOH) using manual passwords and magnetic stripe passwords in addition to standard login ID numbers.� This document explains the configuration and functionality of manual and magnetic strip passwords.

Information

Manual versus Magnetic Stripe Passwords

Manual and magnetic stripe passwords are separate passwords, each is entered into the system separately, and each is stored in a separate field in the EMP.DBF file.

Manual passwords are entered using the touch screen login keypad.� When you log in using a manual password, you must enter your employee number plus the password.� For example, if your employee number is 123 and the password is 789, then you would have to use 123789 to log into the FOH.

Magnetic stripe passwords are entered by swiping a magnetic stripe card (mag card) through a magnetic stripe reader (MSR).� When you log in using a mag card, you can swipe the card from the floating logo screen or the keypad login screen.� You do not need to enter your employee number or a manual password when using a mag card to log in to the system.

You can use manual passwords or magnetic stripe passwords to authorize functions that require a manager's authorization.

Manual passwords are stored in the PASSWORD field of the EMP.DBF, and magnetic stripe passwords are stored in the MAGCARD field of the EMP.DBF.� Regardless of the password type, both fields are encrypted and you cannot edit them using third-party database editing software.� Both fields are populated regardless if a password is assigned to the employee or not.

Enabling FOH Passwords

To enable passwords, open Aloha Manager and select Maintenance/Store Settings/Security/POS Password Settings.� You can disable passwords in the FOH, make them optional, or require them.� You can also set the minimum and maximum password lengths, but these lengths only apply to manual passwords.

To set each job code to use passwords, open Aloha Manager and select Maintenance/Labor/Job Codes and select 'Uses Password'.� If you want the FOH password to expire, select 'Password Expires' and set the number of days for renewal.� FOH password expiration only occurs if passwords are required in the POS Password Settings, Uses Password is enabled for the job code, Password Expires is enabled for the job code, and a valid number ('1' or higher) is defined for the renewal days.

If you want to require the use of mag cards for passwords, open Aloha Manager, select Maintenance/Employees, select the employee, and select 'Must use Mag Cards'.� If this is enabled, the employee will not be able to login using a manual password.� Even if this is not enabled, employees can still optionally use magnetic stripe passwords.�

Refresh the system.

Assigning, Clearing and Changing FOH Passwords

If an employee wants to assign themselves a password (manual, magnetic strip, or both), 'Uses Password' is enabled for their job code, and passwords are set to optional or required in the POS password settings, then they can do so via the 'Change Password' function in the FOH functions menu (Functions/Employee/Change Password).� They also use this function to change existing passwords (manual and magnetic stripe).� You cannot disable the 'Change Password' function without disabling passwords all together.

If an employee forgets their password, loses their mag card, or you have to clear their password for any other reason, you can do so from the FOH functions menu (Functions/Employee/Clear Password) as long as you are logged in using an access level with 'Clear Password' enabled.� This function enables you to clear the password of any employee configured in the system, so it should only be assigned to managerial access levels.

The 'Clear Password' function clears both manual and magnetic stripe passwords.

If passwords are required in the POS password settings, any employee logging in using a job code with 'Uses Password' enabled must create a manual password.� The FOH prompts them to do so.

If you enable 'Must use Mag Cards' for an employee, the employee will see a message stating 'You are required to login with a mag card' the first time they attempt to log into the system.� In order to assign a mag card and enable the employee to log in, an employee with an access level that enables the 'Clear Password' function must clear the employee's password.� This enables the employee to log in with their employee number so they can assign themselves mag card number.

Magnetic stripe passwords can be assigned to employees from within Aloha Manager if you have enabled 'Must use Mag Cards'.

Passwords and the End of Day Process

Current day password additions and changes are stored in the TRANS.LOG (transaction log) until the End-of-Day (EOD) process occurs.� Only during the EOD process are the changes incorporated into the EMP.DBF files residing in the Aloha application software NEWDATA and DATA folders.�

If you delete the transaction log following password additions or changes but before the EOD process occurs, the password additions and changes will be discarded.

SuperSite Password Propagation

In SuperSites, the grind process propagates password additions and changes between stores throughout the entire SuperSite.� Separate grind processes run for each store at set intervals, so the passwords additions and changes for a given store are collected and made available for the other stores each time grind gathers the latest data from the store.� When a grind for a different store runs, it picks up the changes reported by other store's grinds and sends the new information to its store.� The time it takes to propagate password additions and changes depends on the interval set for the grind processes and the amount of information that has changed since the last interval.

If a SuperSite store's grind process is disabled, the store will neither distribute nor receive password additions and changes to or from other stores.�

Whenever possible, FOH passwords in SuperSites should not be cleared, but only changed.� Clearing a password and then adding a new password are two separate functions with separate priorities (as assigned internally by the Aloha application software applications), so it is possible that one function could inadvertently override the other if your grind intervals are set to (or actually occur) five minutes or longer.

Extended Information

No information.

Caveats

FOH password expiration only occurs if passwords are required in the POS Password Settings, Uses Password is enabled for the job code, Password Expires is enabled for the job code, and a valid number ('1' or higher) is defined for the renewal days.

The 'Clear Password' function enables you to clear the password of any employee configured in the system, so it should only be assigned to managerial access levels.

The 'Clear Password' function clears both manual and magnetic stripe passwords.

If you delete the transaction log following password additions or changes but before the EOD process occurs, the password additions and changes will be discarded.

If a SuperSite store's grind process is disabled, the store will neither distribute nor receive password additions and changes to or from other stores.�

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1198 Magnetic Stripe Card Information

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1186 logon mag magcard magstripe

�

Enable or Disable RDB Grind User Interfaces

Enable or Disable RDB Grind User Interfaces

============================================================================

AKBID1187

Created: 2 May 2001

Updated: 2 May 2001

Reviewed: 11 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.014 � 5.3.x

Subject: How to Enable or Disable RDB Grind User Interfaces

============================================================================

Summary

The ALOHA^� application software grind application is always enabled (either grinding data or waiting for a signal to grind data) if you are using a Relational-Database (RDB).� While this is not a problem for non-SuperSites, it becomes a problem for SuperSites with multiple stores because the file server screen becomes filled with numerous graphical user interfaces (GUI) for each instance of the grind application.� Besides it being a burden for file server users, the grind GUIs also consume extra memory.� The Aloha application software uses the GRINDHIDEWINDOW ALOHA.INI variable and the HIDEGRIND and SHOWGRIND flag files to enable or disable the GUIs for the grind applications.

Information

The Aloha application software uses the following hierarchy when processing the settings discussed in this document: SHOWGRIND overrides HIDEGRIND overrides GRINDHIDEWINDOW.

GRINDHIDEWINDOW

GRINDHIDEWINDOW is an ALOHA.INI variable that disables or enables the grind GUIs on a global basis (all stores in a SuperSite).� This must be set to TRUE or FALSE in order to use the HIDEGRIND and SHOWGRIND flags discussed later in this document.� Setting this variable to TRUE globally disables the grind GUIs.� Setting this variable to FALSE globally enables the grind GUIs.

You must restart CTLSVR.EXE (Control Server) before changes to the GRINDHIDEWINDOW variable become effective.

HIDEGRIND and SHOWGRIND

Unlike GRINDHIDEWINDOW, which is an ALOHA.INI variable, HIDEGRIND and SHOWGRIND are flag files that reside in the store folders (%IBERDIR%\STRnnnn).� While GRINDHIDEWINDOW provides a rule, HIDEGRIND and SHOWGRIND provide exceptions to the rule, so you can enable the grind GUI for some stores, but not other stores.

If you set GRINDHIDEWINDOW to TRUE in the ALOHA.INI, you can place a SHOWGRIND file in the store folders for the stores you want to display the grind GUI.

If you set GRINDHIDEWINDOW to FALSE in the ALOHA.INI, you can place a HIDEGRIND file in the store folders for the stores you do not want to display the grind GUI.

You must restart the effected store's grind before changes created by the SHOWGRIND and HIDEGRIND flag files become effective.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

AKBID1151 Aloha Application Software Flag Files

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1187 hide

style='mso-spacerun:yes'>� 2003

�

Using Previous Version Dated Folders in 5.2x

Using Previous Version Dated Folders in 5.2x

============================================================================

AKBID1188

Created: 17 May 2001

Updated: 5 February 2002

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x

Subject: Using Previous Version Dated Folders in 5.2x

============================================================================

Summary

After you have upgraded the ALOHA^� application software from a previous version (5.0x or lower) to versions 5.229 and lower, you are required to upgrade and regrind all of the dated folders from the previous version in order to view Back-of-House reports, reprint guests checks, reprint employee checkouts, and view audit reports.� If you are using versions 5.230 and higher, you can view reports without upgrading and regrinding the dated folders, although you will be prompted to automatically upgrade the dated folder if you view an audit report or reprint guest checks or checkouts for a dated folder from a previous version.

Information

If you have to upgrade and regrind the dated folders, you can use either use the Regrind Subdirectories utility in Aloha Manager or you can manually grind each dated folder from a command line.

If you are using the Regrind Subdirectories utility, all database and Trans.log (transaction log) conversions are performed automatically without any user input.� Mark the selected dates to regrind, set Active to 'On', set Num Grinds to '1', and click Done.� Refer to the Aloha QuickService or TableService User Manual for more information on the Regrind Subdirectories utility.

If you are manually regrinding dated folders by initializing the grind process from a command line or by deleting the GndDBF30.xxx file from the dated folder, you must first update the database using DBConfig.exe.� To start DBConfig.exe, open Aloha Manager and select Utilities/Database Upgrade, or double-click DBConfig.exe in the Bin folder.� Set the Input and Output folders to the dated folder's location, select the following, and click run:

1.        DBF Files Only (if not using an RDB)

2.        Attended

3.        Debug

4.        Force Upgrade

Once the database is upgraded, initialize the grind process from a command line or delete the GndDBF30.xxx file from the dated folder.� Refer to document AKBID1016 for more information.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1016 Grind Process and Errors

AKBID1067 DBUp.exe and DBConfig.exe

AKBID1153 Types of Transaction Logs in Dated Folders

AKBID1160 Manually Upgrading Configuration Files in Aloha Manager

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1188 subdirectories subdirectory

EDC Modem Initialization Strings

EDC Modem Initialization Strings

============================================================================

AKBID1189

Created: 21 May 2001

Updated: 19 February 2003

Reviewed: 8 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 3.5x � 5.3.x

Subject: Creating and Customizing EDC Modem Initialization Strings

============================================================================

Summary

The ALOHA^� application software Electronic-Draft-Capture (EDC) application requires specialized modem initialization strings to properly communicate with credit card processors.� You can use the initialization strings supplied with EDC for many of the most common modems, but you might be required to create a custom initialization string for some modems.

Information

Creating Modem Initialization Strings

If your EDC modem is listed as a supported modem, use the initialization string supplied by EDC for it.� Many 33.6 and 56K modems use the same initialization string as their 28.8 counterparts.� If the modem is not listed or is not compatible with the initialization strings supplied by EDC, you might have to create a new initialization string.

�

The initialization string always begins with AT.� This is the 'Attention' command to the modem.

The next command in the initialization string should reset all modem defaults.� Typically, this is &F, but it varies from modem to modem.� This defines exactly which commands are set on the modem.� If you do not reset it, there might be a lingering setting from another program.

You must disable all intelligence on a high-speed modem (over 9600 baud).� Credit card processors have very short timeouts when negotiating a connection, and if the modem takes too long trying to establish a high-speed connection with advanced modem features enabled, then the processor hangs up.� Disable all of the following (that apply):

-          Disable V.42/MNP data compression

-          Disable DCE flow control

-          Direct data link only

-          Disable XON/XOFF or RTS/CTS flow control

You can use error correction some of the time, and it is useful for American Express settlement which occurs at 9600 baud.� If there are connection or LRC problems, try enabling or disabling error correction to see if it solves the problem.�

EDC versions 4.0x and higher support the use of different initialization strings for authorization and settlement for each processor.� This way you can enable error correction for American Express settlement, but not for American Express authorizations.� Disabling error correction might make authorizations work, but it can cause problems with settlement.� The modem's user manual should provide the command set to enable or disable error correction.

Dialing speed is also set in the initialization string.� Most modems enable this specification.� Set this as fast as possible in order to speed up the dialing process.

Alternative Initialization Strings and Baud Rates

The AT&F1 and AT&F0 initialization strings are not valid and are not supported by Aloha Technologies.� These initializing strings may solve short-term problems, but they will eventually cause new problems.

An alternative U.S. Robotics modem initialization string (besides the one built into EDC) is AT&F0L0M1Q0V1&A0&B1&D2&H0&I0&K0&M0S11=50.� This may be used for all processors.

An alternative U.S. Robotics External 56K modem initialization string is ATQ0V1E1S0=0S11=50.� This may be used for all processors.

When using a U.S.� Robotics modem to settle charges to American Express, use the AT&F0L0M1Q0V1&A0&B1&D2&H0&I0&K0&M5&N6S11=50 initialization string.

An alternative Practical Peripherals modem initialization string (besides the one built into EDC) is AT&F0&K0&Q0S46=0S11=55&C1&D2.� This may be used for all processors.

When using a Practical Peripherals modem to settle charges to American Express, use the AT&F0&K0&Q5S46=0S11=55&C1&D2 initialization string.

Zoom 56K modems use the AT&FS9=1S11=55&C1&D2, AT\N0, or AT&F0\N0&K0%C0&C0L1S11=50S37=6 initialization string.� Use AT&F0&C0 to settle American Express charges.� You can also try AT&F0\N0&K0%C0&C0L1S11=50S37=6+ms=v90,0 with Zoom modems.� Try AT&FS9=1S11=55&C1&D2+ms=v90,0 for settlements.

External Boca Research 33.6 modems use AT&F0%C0&K0\N1M1S11=30.

In versions 4.4x and 5.0x, you can adjust the authorization and settlement baud rates for each processor using the AUTHBAUD and SETTLEBAUD variables in the EDC.INI.� If these variables do not exist, they default to 1200 baud.� To change the baud rate, add the variables to the processor's section (for example [VISANET], [CES], and so on) of EDC.INI, and assign a baud rate.� For example, AUTHBAUD=9600, SETTLEBAUD=9600.� Different baud rates can be assigned to each processor.

In version 5.2x and higher, adjust the authorization and settlement baud rates from the processor settings in EDC.EXE.

Extended Information

No information.

Caveats

The AT&F1 and AT&F0 initialization strings are not valid and are not supported by Aloha Technologies.� These initializing strings may solve short-term problems, but they will eventually cause new problems.

============================================================================

See also:

Aloha Credit Card User Manual

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1189 auth batch init

�

Host-based Credit Card Processors

Host-based Credit Card Processors

============================================================================

AKBID1190

Created: 21 May 2001

Updated: 21 May 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 3.8x � 5.3.x

Subject: Host-based Credit Card Processors

============================================================================

Summary

Host-based (or hybrid) processors are different than the other processors supported by the ALOHA^� application software Electronic-Draft-Capture (EDC) application because all transaction information is stored on the host's (processor) side.� For support personnel, this limits the support options and does not enable deleting TXN files to settle a batch, and moving a batch aside to be dealt with later. This document explains the differences with using host-based processors with the Aloha application software.

Information

Host-based (or in NOVA's case, hybrid) processors store all information on the host's (processor) side.� Any updates to credit card transactions (voids, adjustments, authorizations, or refunds) are updated on the host's side as well as on the local EDC server.� All credit card transactions on the EDC server must match the transactions stored on the host when settling.� If they do not match, settlement is not possible, and you have to use one of the functions in EDC to rectify the problem.�

Editing a TXN file or deleting any TXN files will cause a mismatch with the information held by the host.

The EDC Functions drop-down menu enables three functions for use with NOVA: Get Current Batch Totals, Get Previous Batch Totals and Purge Batch.� These are only used when troubleshooting a problem with a host-based processor.

The Get Current Batch Totals function will call the host and return an on-screen dialogue showing the current batch totals as held by the processor.� If a batch will not settle, this is a useful function to compare totals from both sides and find the discrepancy.

The Get Previous Batch Totals function will call the host and return an on-screen dialogue showing the previous batch totals.� With this function confirms if there was an accidental settlement causing a discrepancy.

The Purge Batch function will purge the current batch from the host.� This function will not help diagnose the settling problem, and should be used as a last effort in synchronizing the information with the host computer.� This function will purge the current batch's information on the host's side and automatically rebuild it the next time EDC attempts a settlement using Settle Batch.� The automatic rebuild process will resynchronize the host totals with the information currently in the local EDC server.

The purge function does not guarantee that no transaction information will be lost or is incorrect.� Contact the processor first and manually check all the transactions for discrepancies.� It is extremely rare that a batch purge will be necessary, and in most cases the batch will rebuild correctly.

A frequent problem occurs when a technician calls NOVA with a problem settling, and NOVA will settle the batch on their end.� If this occurs, Purge Batch will fail! Since the host has cleared away the batch, the correct course of action in EDC is to use the Force Settlement function, which will archive the current batch and skip the settlement process itself.

Extended Information

No information.

Caveats

Editing a TXN file or deleting any TXN files will cause a mismatch with the information held by the host.

============================================================================

See also:

Aloha Credit Card User Manual

AKBID1020 EDC Process

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1190

�

Common EDC Processor Errors

Common EDC Processor Errors

============================================================================

AKBID1191

Created: 21 May 2001

Updated: 11 September 2003

Reviewed: 16 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 3.5x � 5.3.x

Subject: Common EDC Processor Errors

============================================================================

Summary

Some of the errors the ALOHA^� application software from credit card processors can be cryptic to the common user.� This document explains some of the more common errors and their possible causes.

Information

Amex

INVLD Response to INIT CTL: This may be a result of incorrect account information or baud rate.

Y Modem Error during transfer failed error -618: The carrier was lost during the settlement (phone line hung up before complete transmission of the settlement file).

Buypass

Buypass has a saved profile for Aloha application software installations that has an unused password field which defaults to '111111'.� If you receive an error message during settlement stating 'Invalid Password', then BuyPass has not configured the restaurant's account using the saved profile.� You can possibly double-charge customers if you resettle without rectifying this problem.

CES

Invalid Data Rec # : A packet was sent with incorrect information.� Enable debugging by adding DEBUG=1 to the [SYSTEM] section of the EDC.INI and find the last two transactions it sent.� Find out why they are failing or void them.�

By default, CES supports a maximum of 349 transactions.� Additional transactions result in an error stating 'Batch Full'.� In Aloha versions 5.2.5.104 and higher, you can add the MaxTransactionsPerBatch variable to the [CES] section of the EDC.INI and assign it a value that represents the expected maximum number of transactions.� CES does not recommend changing this value since it increases the opportunities for errors during settlement.

CES does not support tips for more than $999.00.� Attempting to settle a batch with a single tip for more than $999.00 does not produce a specific error other than a general failure to settle the batch.

FDC

Error Unresolved out of balance batch, contact First Data to clear: This means that the previous settlement did not complete.� The phone may have dropped the connection before the settlement finished.� Call the FDC helpdesk at (800) 647-3722 to clear this message, and re-settle the batch.

LynkSystems

Expired HO: This occurs if you have configured your LynkSystems processor as a VisaNet processor.� Use the information from your VisaNet processor to configure the LynkSystems processor, which uses the same information fields, and remove the VisaNet processor.� Ensure that you reassign each credit card type to use the LynkSystems processor.

NPC

No batch response received: Try the settlement again at a later time.� There could be too much load on the processors network for it to keep up, or processor network is temporarily out of service.

Error 66: Comes from NPC and means Duplicate Batch.

If you are trying to settle credit cards to NPC and receive an error stating 'Failed: Enquiry upload OK', ensure that you have not enabled Inquiry Only in the NPC configuration.

VisaNet

No batch response received: Try the settlement again at a later time.� There could be too much load on the processors network for it to keep up, or processor network is temporarily out of service.

Rejected batch - Parameter record nn field x error E: This error is usually caused by incorrect Merchant Account information.� Verify the account information, Bank ID number (BIN), and Merchant ID number.� Verify that Visanet has not terminated the account.� Verify the account is enabled for Multi-Trans before enabling the Multi-Trans check box.

Rejected batch - Detail record nn field y error E: This is often caused by an invalid forced transaction in the batch.� Also verify the merchant is entitled to settle American Express and Discover transactions if applicable.� If there is an invalid transaction, go to the void transaction function and select the transaction that is numbered nn.� Write down all the information so that the transaction can be retried later, and void the transaction to remove it from the batch.� Try to settle again.� Visanet does not publish the error numbers, so there is no easy way to diagnose why the transaction failed except by consulting Visanet support directly.

'Unexpected Bel' or 'Unexpected Ack' error when trying to settle: Like LRC errors, this error is usually indicative of a bad phone connection with the processor.� When a batch is sent to Visanet, it verifies each block sent by alternating between a bel or an ack response.� If two bels or two acks are received in a row, then a block of data was lost.� Immediately attempt to resettle the batch and it will typically settle.� If the problem persists, wait 30 minutes and try it again.�

Duplicate batch #xxx on mmdd: The Visanet setup properties displays a batch number in the lower left-hand corner.� Each batch is assigned a number, and this number will increment with each batch.� If a batch is settled outside of the restaurant, the batch number will not increment.� The batch number must be manually incremented.

Error 51 Declined: This response has been returned when authorizing and means 'Insufficient funds' or 'Insufficient Credit Limit'.

LRC Errors

A LRC is a Longitudinal Redundancy Check.� It is a checksum performed on all messages that are sent and received by EDC.� If the LRC does not match the message, some corruption of the message occurred.� Corruption can occur for one of the following reasons:

1.        The phone line is noisy.� The phone company needs to check the line.� EDC should use a direct line.� Running through a phone system is discouraged.� Ensure the phone line is not shared or being interrupted.

2.        Try using alternate phone numbers if they are available.� Switch between local and long distance numbers, or vice-versa.

3.        Experiment with the initialization string if it is an unfamiliar modem.� Enabling error correction sometimes helps.

4.        If the modem is running on an inferior serial port, it might be dropping characters.� The computer uses serial ports to send and receive characters.� The chip that handles the sending and receiving is called a Universal Asynchronous Receiver/Transmitter (UART).� Quality serial ports have buffered UARTs, which means they can store several characters at a time.� This greatly reduces the chance the computer will drop a character.� UARTs in the 16000-range (e.g. 16550) are generally good.� UARTs in the 8250 range are not buffered and might cause problems if they are used with EDC.

The symptoms of incorrect UARTs are almost indistinguishable from a bad phone line.� They include numerous retries and LRC errors in the DEBOUT.EDC.

Check if the First-In-First-Out (FIFO) buffers on the serial port are enabled in Microsoft Windows.� The location of this setting varies depending on the version of Windows.� If the FIFO settings are grayed out, the UART is not buffered.

Use the UARTTYPE.COM utility from the Aloha Technologies ftp site.� To perform properly, the utility must be used in a MS-DOS^� environment.� A bootable DOS floppy may be required to use this utility.� Refer to document AKBID1012 for more information.

American Express Settling Errors

If the American Express settlement is failing with an error stating 'YOU A$%#', then you are probably using the wrong phone number to settle American Express transactions.� American Express has several settlement hosts around the country, and a merchant is assigned to a host.� If the host that does not recognize the merchant, it will respond 'YOU ARE NOT AUTHORIZED TO ACCESS THIS HOST' and hang up.� They often hang up before they have finished sending the error message, so EDC only gets the first few characters, followed by garbage.� This might also occur if the restaurant is not set up properly with American Express to perform a settlement.

American Express might have the merchant setup for different application software.� If so, they will reject settlement attempts by the Aloha application software.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha Credit Card User Manual

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1020 EDC Process

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1191

�

Troubleshooting EDC Spooling

Troubleshooting EDC Spooling

============================================================================

AKBID1192

Created: 30 May 2001

Updated: 24 February 2004

Reviewed: 24 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 4.0x � 5.3.x

Subject: Troubleshooting EDC Spooling

============================================================================

Summary

The ALOHA^� application software Electronic-Draft-Capture (EDC) application uses credit card spooling for credit card fault tolerance.� This document explains the spooling process and how to troubleshoot common spooling problems.

Information

EDC Spooling Process

EDC spooling uses 'fake' authorizations when EDC is not functioning.� Front-of-House (FOH) EDC transactions are given a mock authorization code and stored on the Master terminal until EDC is back on line.� EDC vouchers print in the FOH just as the normal EDC process does.� Refer to the Aloha Credit Card User Manual to enable EDC spooling.

Spooling occurs in one of three instances:

1.        The EDC file server is off the network.� The FOH automatically enters spooling mode when this occurs. In versions 4.0x through 5.2.7.225, 5.2.8.1 through 5.2.8.152, and 5.3.1.1 though 5.3.2.149, spooling does not start until the first time the master terminal unsuccessfully attempts to create an EDC request file on the EDC file server.� In versions 5.2.7.226 through 5.2.7.x, 5.2.8.153 through 5.2.8.x, and 5.3.2.150 and higher, spooling starts the first time the master terminal unsuccessfully attempts to poll the EDC file server, which occurs approximately every 15 seconds.

2.        The EDC POS processing is disabled.� In versions 4.251 and later, the FOH will automatically enter spooling mode if the POS processing is disabled.� In versions lower than 4.251, the FOH will not automatically enter spooling mode in this case.

3.        EDC is not started on the EDC server.� In versions 4.251 and later, the FOH will automatically enter spooling mode if EDC does not respond.� The timeout for this is set by the WAITFOREDCRENAME=n entry in the ALOHA.INI file, where n is the number of seconds to wait.� It is advisable to not set this time lower than 30 seconds.� This variable is not available in versions 4.250 and lower, so the FOH will not automatically enter spooling mode in this case.

Non-software related issues such as a busy or a disconnected phone line does not enable spooling mode.� The EDC POS processing can be manually disabled to force spooling while the problem is fixed.

If the FOH enters spooling mode, a SPOOLING marker file is created in the EDC folder on the Master terminal.� Each new EDC request file is renamed to a .SPL file and held.� In versions 5.025 and higher, if SHOWSPOOLDOWN is set to TRUE in the ALOHA.INI, then a message stating 'This credit card has been processed offline.� Please contact your manager' is displayed each time a credit card authorization is spooled.

EDC recovery is automatic.� When EDC is back on line, it searches each terminal's EDC folder for SPOOLING and .SPL files.� The SPOOLING file is deleted and the .SPL files are processed as if they are normal request files.�

Once EDC is back on line, spooled files are processed regardless if the hardware and software are properly configured.� If the hardware and software are not completely configured, the spooled files may be processed, declined, and require manual reentry.

In versions 5.2.5.99 and lower, once EDC is back on line, spooled files are processed regardless if the hardware and software are properly configured.� If the hardware and software are not completely configured, the spooled files may be processed, declined, and require manual reentry.

In versions 5.2.5.100 and higher, if EDC cannot process the spooled transactions because it cannot connect to the processor, then by default, it will hold the transactions and attempt to process them again in 300 seconds.� You can adjust this timeout in the [System] section of the EDC.INI using the RESENDSPOOLEDSECONDS variable.� EDC will continue to attempt processing the spooled transactions for 48 hours, but you can adjust this timeout in the [System] section of the EDC.INI using the RESENDSPOOLLIMITHOURS variable (assign this a value of '0' in order to disable retries).� If EDC is not able to authorize spooled transactions, then you cannot adjust the tips on these transactions while they are in the authorization queue.� In this case, you should consider reentering spooling mode.

In the event there are multiple Master terminals when spooling is enabled, EDC processes the SPOOLING and .SPL files from each terminal.

FOH Continually Enters Spooling Mode

If the FOH continually enters into spooling mode even though EDC appears to be functioning properly, check the FOH terminal's debugging-output-file (debout) and the EDC debout to help you determine what caused the Aloha application software to enter into spooling mode.� Refer to document AKBID1134 for more information on debouts.

For example, was there a network problem at the time the spooling file was created that disabled the FOH from accessing the EDC server? Was EDC disabled or was POS processing disabled? Can you currently access (read and write) the EDC folder on the file server from the FOH?

The EDCPATH variable (refer to document AKBID1010) is only required for SuperSites or sites where EDC does not reside in the Aloha folder on the POS file server (for example, if you have a dedicated EDC file server or multiple concepts on a single file server).� If you are using the EDCPATH variable, ensure it is set correctly on each FOH terminal.� If are not using the EDCPATH variable, then the path to the EDC folder on the Aloha file server is automatically resolved by the FOH terminals by using the IBERDIR variable (which is assigned dynamically by the master terminal � you do not need to create an IBERDIR environment variable on the FOH terminals) in the \\%IBERDIR%\EDC format.

BOH Does Not Automatically Process Spooled Files

If the Back-of-House (BOH) does not automatically find and process spooled files, it is usually a result of incorrect TERMSTR and IBERROOT environment variable settings on the EDC file server.� When EDC Server initializes, it lists the terminals paths it is scanning in the DEBOUT.EDC, so first verify that EDC Server is scanning the correct paths to reach the terminals.

Also verify that the EDC file server has read and write access to the BOOTDRV share on each FOH terminal.� If you have configured EDC Server to login with a specific user rather than the default system account (refer to document AKBID1197), ensure that the user has read and write access to the BOOTDRV share on each FOH terminal.

If you require additional scanning information in the DEBOUT.EDC, perform the following to add the DEBUGSCAN variable to the EDCSVR.EXE (EDC Server) command line in the Microsoft^� Windows^�:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

1.        Select Start/Run, type REGEDIT, and click OK to open the Windows Registry Editor.

2.        Path out HKEY_CLASSES_ROOT\AppId\{583B6E82-64F1-11D1-8EF3-0040054AB0A4}.

3.        Double-click AlohaEdcSvrParameters and append a space and '/DEBUGSCAN' to the existing Value Data.

4.        Select Registry/Exit to exit the Windows Registry Editor.

5.        Restart Windows.

After restarting Windows and EDC Server, verify the network paths were captured in the DEBOUT.EDC.� Once you have found the source of the problem, perform the following to remove the DEBUGSCAN variable from the EDCSVR.EXE command line:

Select Start/Run, type REGEDIT, and click OK to open the Windows Registry Editor.

Path out HKEY_CLASSES_ROOT\AppId\{583B6E82-64F1-11D1-8EF3-0040054AB0A4}.

Double-click AlohaEdcSvrParameters and remove '/DEBUGSCAN' from the existing Value Data.

Select Registry/Exit to exit the Windows Registry Editor.

Restart Windows.

Windows 98, Windows NT, Windows 2000, Windows XP, or Windows Server 2003 FOH Terminals

If you have FOH terminals running Windows NT^�, Windows 2000, Windows XP, or Windows Server 2003 with a file server running Windows NT, Windows 2000, or Windows XP or if you have FOH terminals running Windows 98 with a file server running Windows 2000, Windows XP, or Windows Server 2003, the file server may not be able to access the FOH terminal to delete or process the SPOOLING or .SPL files because of limitations to the built-in Windows system account used by EDC Server.� Refer to document AKBID1197 for more information.

Multiple Instances of EDC on a Single File Server

If you have configured multiple instances of EDC to run simultaneously on a single file server, then you must point each instance of EDC Server to separate Aloha application software folders (using the IBERDIR system environment variable) or data folders (using the DATADIR system environment variable) if each instance of EDC server exclusively serves specific terminals.�

For example, if a SuperSite has an EDC server with one instance of EDC servicing terminals 1-50 and a second instance of EDC server serving terminals 51-100, then each instance of EDC Server must use a copy of TRM.DBF that only contains the terminals in which it serves.� If each instance of EDC Server uses the same copy of TRM.DBF, then each instance of EDC Server will scan all terminals (including the terminals serviced by other instances of EDC), which will result in one instance of EDC authorizing spooled transactions intended for another instance of EDC.

Multiple EDC File Servers in a SuperSite

If you have configured multiple EDC file servers to run simultaneously in a SuperSite (for example, file server one covers stores 1-10 and file server two covers stores 11-20), then you must use a TRM.DBF specific only to the file server's target terminals on each EDC file server in order to ensure that each EDC file server exclusively serves its specific stores.� If you use a site-wide TRM.DBF, then each EDC file server will attempt to process spooled transactions from all stores (including the stores serviced by other EDC file servers), not just their assigned stores.

For example, if a SuperSite has one EDC file server servicing stores 1-10 and a second EDC file server serving stores 11-20, then each EDC file server must use a copy of TRM.DBF that only contains the terminals in which it serves.�

Extended Information

No information.

Caveats

In versions 5.2.5.99 and lower, once EDC is back on line, spooled files are processed regardless if the hardware and software are properly configured.� If the hardware and software are not completely configured, the spooled files may be processed, declined, and require manual reentry.

If EDC is not able to authorize spooled transactions, you cannot adjust the tips on these transactions while they are in the authorization queue.� In this case, you should consider reentering spooling mode.

============================================================================

See also:

Aloha Credit Card User Manual

AKBID1010 Aloha Application Software System Environment Variables

AKBID1020 EDC Process

AKBID1107 Aloha Application Software Fault Tolerance Functionality

AKBID1134 Debouts

AKBID1197 Assigning Logins to Aloha Services

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1192

�

Purging Dated Folders in Aloha Manager

Purging Dated Folders in Aloha Manager

============================================================================

AKBID1193

Created: 5 June 2001

Updated: 5 June 2001

Reviewed: 2 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.017 � 5.3.x

Subject: Purging Dated Folders in Aloha Manager

============================================================================

Summary

The ALOHA^� application software has an automated purge feature that removes dated folders from the file server that are older than a designated number of days.� This document explains the purge feature, configuration, and usage.

Information

To enable and configure the purging feature, open Aloha Manager, select Maintenance/Store Settings/System/Disk Maintenance, and configure the following:

'Number of days to keep on' � This is the number of previous days (based on the system date) to store on the hard drive before purging the dated folders.� Setting this to a number greater than zero enables the purging feature.

'Use archive bit to purge data' � Instructs the Aloha application software not to purge the dated folder if the files' archive bits are enabled.

After adjusting either of these settings, ensure that you refresh the system and restart Ctlsvr.exe (Control Server) in order to activate the changes.

Control Server performs the purging process during the End-of-Day (EOD) process when it detects an EOD marker file in the Aloha application software Data folder.� The purging activity is logged in Debout.svr and appears similar to the following:

Jun 05, 13:52:55� CTLSVR: Detected End Of Day in progress...

Jun 05, 13:52:55� CtlSvr: Checking for directories to purge from 20010406...

Jun 05, 13:52:55� Purged directory C:\ALOHA\20010306

If purging is not performed because of the archive bit, information similar to the following appears in Debout.svr:

Jun 05, 14:33:22� CTLSVR: Detected End Of Day in progress...

Jun 05, 14:33:22� CtlSvr: Checking for directories to purge from 20010406...

Jun 05, 14:33:22� CTL: Skipping 20010314 due to archive bit

Extended Information

No information.

Caveats

After adjusting either of these settings, ensure that you refresh the system and restart Control Server in order to activate the changes.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1193 archiving

�

Check Comp Form

Check Comp Form

============================================================================

AKBID1194

Created: 6 June 2001

Updated: 29 May 2002

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.670 � 5.3.x

Subject: Printing a 'Comp Form' with Each Check Containing a Comp

============================================================================

Summary

You can enable the ALOHA^� application software to print a user-configured 'comp form' with each check to which a comp was applied.� This is intended for record keeping purposes in restaurants that require a manager to complete a short form for each check containing a comp.

Comp forms are available in TableService versions 3.670 and higher, and QuickService versions 5.2.4.0 and higher.

Information

Enable Comp Forms

To enable the comp form in versions 5.239 and lower, edit the ALOHA.INI in the Aloha application software NEWDATA folder, set the COMPFORMONCHECK variable to TRUE (for example, COMPFORMONCHECK=TRUE), and refresh the system.

To enable the comp form in versions 5.2.4.0 and higher, open Aloha Manager, select Maintenance/Store Settings/Printing/Check Content 1, and enable 'Print defined Comp Check lines'.

The comp form only prints when the check is closed and if a comp has been applied to the check.� This form will not print if you do not have the Aloha application software configured to print a check when the check is closed or if a comp has not been applied to the check.

Only one copy of each type of comp form prints for each check, even if the check contains multiple instances of the same comp.� If a check has multiple types of comps, then the Aloha application software prints a separate comp form for each comp, provided that a comp form exists for each type of comp applied to the check.

Create the Comp Form

Configure the comp form layout by creating a text file labeled COMPFORM.TXT or CPFnnnnn.TXT (where nnnnn is the comp ID without the leading zeros) in the Aloha application software DATA folder.� Whereas COMPFORM.TXT is a global setting for all comps, CPFnnnnn.TXT (available in versions 5.2.4.0 and higher) are comp-specific.� If a CPFnnnnn.TXT exists for a comp, the Aloha application software uses the comp form in CPFnnnnn.TXT rather than COMPFORM.TXT; otherwise the Aloha application software uses the comp form in COMPFORM.TXT.� If neither a CPFnnnnn.TXT nor a COMPFORM.TXT exist, then the Aloha application software does not print a comp form for the check.

�

Use the following rules when adding content to COMPFORM.TXT or CPFnnnnn.TXT:

1.        Each line must begin with 'MSG'.� All other lines are ignored.

2.        A '&' in the fifth text line position (MSG plus one space) instructs the printer to perform a partial cut (if the printer is capable).

3.        A '^' in the fifth text line inserts the system date and the check number on the left side of the form.� This uses a yyyymmdd � 99999 format (for example, 20010606 � 10001).

4.        A '@' in the fifth text line instructs the printer to start using a large font.

5.        A '#' in the fifth text line instructs the printer to stop using a large font.

6.        If the printed guest check is set to use the large font, then the comp form will default to the large font.� You must use a '#' at the beginning of the form to default to the smaller font.

7.        Since the printer's paper cutter is not at the same location as the print head, paper cuts may appear several lines above location defined in the comp form.� You will have to experiment with your printer type and compensate for this in your comp form design.

The following is an example comp form:

MSG &

MSG

MSG ^

MSG

MSG @

MSG�� COMP SLIP

MSG

MSG Restaurant: ______________________

MSG

MSG Shift:_____

MSG #

MSG

MSG Check all That apply and Print

MSG�� Name

MSG

MSG __ Customer Relations______________

MSG Explanation:______________________

MSG ________________________________

MSG ________________________________

MSG __ Executive Meal_________________

MSG __ Manager Meal__________________

MSG __ 50% Emp Meal_________________

MSG

MSG -------------------------------------------

MSG | Date�� 20�� |

MSG --------------------------------

MSG |�� Description�� |� Amount� |

MSG -------------------------------------------

MSG | Liquor�� |�� |� |

MSG -------------------------------------------

MSG | Beer�� |�� |� |

MSG -------------------------------------------

MSG | Wine�� |�� |� |

MSG -------------------------------------------

MSG | Food�� |�� |� |

MSG -------------------------------------------

MSG |�� Total� |�� |� |

MSG -------------------------------------------

MSG

MSG ________________________________

MSG Waitperson�� Emp #

MSG

MSG ________________________________

MSG Customer/Employee Signature

MSG

MSG ________________________________

MSG Manager Signature

Extended Information

No information.

Caveats

Comp forms are available in TableService versions 3.670 and higher, and QuickService versions 5.2.4.0 and higher.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1194 append complimentary

�

Deleting the DOWNTIME.INI

Deleting the DOWNTIME.INI

============================================================================

AKBID1195

Created: 18 June 2001

Updated: 18 June 2001

Reviewed: 20 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

Subject: Deleting the Aloha Application Software DOWNTIME.INI

============================================================================

Summary

In general, you should never delete the DOWNTIME.INI file on ALOHA^� application software Front-of-House (FOH) terminals.� The DOWNTIME.INI plays an important part in ensuring the Aloha application software fault tolerance functionality performs properly.� This document explains the role of the DOWNTIME.INI and why you should never delete the file.

Refer to document AKBID1107 for more information on Aloha application software fault tolerance (redundancy) functionality.

Information

The DOWNTIME.INI file is a text-based file that resides in the root of the Aloha application software folder (for example, D:\ALOHA\DOWNTIME.INI).� It provides a safeguard to ensure that if a FOH terminal becomes a redundant fileserver, that it will not stop being a fileserver until one of two things happens:

The terminal encounters another master terminal and merges transaction logs with the other master terminal.

The terminal receives a Recover Fileserver request from the Back-of-House (BOH), safely copies its TRANS.LOG (transaction log) back to the BOH fileserver, and resumes normal operation.

You should not consider deleting the DOWNTIME.INI as a 'fix all' for problems encountered while using the Aloha application software.

If you delete the DOWNTIME.INI on a FOH terminal that is currently acting as a redundant fileserver and restart the FOH, you will lose the data in the FOH terminal's transaction log (unless you manually saved the transaction log somewhere else) if another computer assumes the role of the file server following the restart.� Even in the event that you preserved the transaction log by manually saving it in a different location, you might not be able to merge the two (or more) logs for proper reporting.� This occurs because the FOH terminal no longer knows that it was a redundant file server, so it does not consider its current local data as valid.� Upon restarting the FOH, the terminal synchronizes its local DATA folder with the computer currently acting as file server and the previous information in the local DATA folder is overwritten.

�

The only time you can safely delete the DOWNTIME.INI is if there is no current transaction data in the system or you are in a lab or test environment where the data is not important.

Extended Information

No information.

Caveats

In general, you should never delete the DOWNTIME.INI file on Aloha application software FOH terminals

You should not consider deleting the DOWNTIME.INI as a 'fix all' for problems encountered while using the Aloha application software.

The only time you can safely delete the DOWNTIME.INI is if there is no current transaction data in the system or you are in a lab or test environment where the data is not important.

============================================================================

See also:

AKBID1107 Aloha Application Software Fault Tolerance Functionality

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1195 recovery

�

DBFUTIL.EXE

DBFUTIL.EXE

============================================================================

AKBID1196

Created: 23 July 2001

Updated: 6 June 2002

Reviewed: 15 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x - 5.3.x

Subject: DBFUTIL.EXE Description and Usage

============================================================================

Summary

DBFUTIL.EXE is designed to enable ALOHA^� application software users to combine multiple copies of the .DBF files created by the Grind process (refer to document AKBID1016).� For example, rather than using summary files created by the Aloha application software Summary process (refer to document AKBID1081), you can combine the grind files (refer to document AKBID1030) from multiple days into a single file that contains more information than the summary files.� You can also use this utility's /MF option to combine other Aloha application software .DBF files, such as combining two ITM.DBF files.

Information

DBUTIL.EXE resides in the \MISC folder on the Aloha Installation CD and uses the following command line options:

/D

Usage: DBFUTIL.EXE <source path/filename> /D > <destination path/filename>

Example: DBFUTIL.EXE GNDSALE.DBF /D > GNDSALE.CSV

Description: Exports the contents of the source file in a Comma-Separated-Value (.CSV) format.

/M

Usage: DBFUTIL.EXE <destination path/filename> /M <source path/filename>

Example: DBFUTIL.EXE GNDSALE.DBF /M WEEKSALE.DBF

Description: Merges a single source file to the destination file.� The files involved in the append process are required to have at least one date field.� The first date field, regardless of the name, will be assumed to be the date of the record and will be used as the key.� Prior to appending the source file to the destination file, any record in the destination file with the same date as a date from the source file will be deleted.

/MR

Usage: DBFUTIL.EXE <destination path/filename> /MR <source path/filename> <start date in format YYYYMMDD> <end date in format YYYYMMDD>

Example: DBFUTIL.EXE WEEKSALE.DBF /MR MNTHSALE.DBF 20010101 20010107

Description: Merges a date range of records within single a source file to the destination file.� The files being appended are expected to have at least one date field.� The first date field, regardless of the name, will be assumed to be the date of the record and will be used as the key.� Prior to the destination file being appended from the source file, any record in the destination file with the same date in the date range will be deleted.

/MF

Usage: DBFUTIL.EXE <destination path/filename> /MF <source path/filename> <column number>

Example: DBFUTIL.EXE MNTHSALE.DBF /MF GNDSALE.DBF 1

Description: Merges a single source file to the destination file using a user-defined column (the column number) as the key.� Prior to appending the source file to the destination file, any record in the destination file with the same value as the value from the source file will be deleted.

/MDS

Usage: DBFUTIL.EXE <destination path/filename> /MDS <source path> <source filename> <start date in format YYYYMMDD> <end date in format YYYYMMDD>

Example: DBFUTIL.EXE MNTHSALE.DBF /MDS D:\ALOHA GNDSALE.DBF 20010101 20010107

Description: Merges source files from dated folders to the destination file.� The files being appended are expected to have at least one date field.� The first date field, regardless of the name, will be assumed to be the date of the record and will be used as the key.� Prior to the destination file being appended from the source file, any record in the destination file with the same date in the date range will be deleted.

/KP

Usage: DBFUTIL.EXE <destination path/filename> /KP <n>

Example: DBFUTIL.EXE GNDSALE.DBF /KP 5

Description: Initiates a purge of a file for records over a defined number of dates.� n is the number of days to keep in the defined file.� This is an actual count of the number of days, not the number of days back from the system date.� For example, if the defined file has transactions from 03/10/2001, 03/09/2001, 03/08/2001, 03/07/2001, and 03/06/2001, the system date is 03/17/2001 and n = 5, when the /KP command line is run, the system will not purge any data.�

/KPD

Usage: DBFUTIL.EXE <destination path/filename> /KPD <date>

Example: DBFUTIL.EXE GNDSALE.DBF /KPD 20010101

Description: Initiates a purge of files prior to a defined date.� The date is in the format YYYYMMDD.� Any records in the file equal to and older than the defined date will be purged.�

/NDX

Usage: DBFUTIL.EXE <source path/filename> /NDX <index path/filename> <colname1> <colname2�>

Example: DBFUTIL.EXE GNDSALE.DBF /NDX GNDSALE.CDX DOB TYPE

Description: Generates an index file(s) for the source file.� Colname1, colname2, and so on are the column names, in order, on which the index will be created.� The index files use the .CDX extension.

/SAFE

Usage: DBFUTIL.EXE /SAFE

Example: DBFUTIL.EXE GNDSALE.DBF /M WEEKSALE.DBF /SAFE

Description: This is used with the /M, /MR, /MDS and /MF options.� While in this mode, if a record is found in the destination file with the same dates as the source file, the merge process will halt, and an error return code is generated.

/? or /H

Usage: DBFUTIL.EXE /? or DBFUTIL.EXE /H

Example: DBFUTIL.EXE /? or DBFUTIL.EXE /H

Description: Displays help information.

/DEBUG

Usage: DBFUTIL.EXE /DEBUG

Example: DBFUTIL.EXE GNDSALE.DBF /NDX GNDSALE.CDX DOB TYPE /DEBUG

Description: Outputs additional debugging information to the screen.

Error Return Codes

DBUTIL.EXE uses the following error return codes (in a batch file, check %ERRORLEVEL%):

Error

Return Code

ERROR_NONE

0

ERROR_INSUFFICIENT_PARAMETERS

-1

ERROR_INCORRECT_DATE_FORMAT

-2

ERROR_SOURCE_FILE_NOT_FOUND

-3

ERROR_DESTINATION_FILE_NOT_FOUND

-4

ERROR_INCOMPATIBLE_TABLES

-5

ERROR_SOURCE_HAS_NO_DATE_COLUMN

-6

ERROR_DESTINATION_HAS_NO_DATE_COLUMN

-7

ERROR_SAFE_MODE_DELETE

-8

ERROR_INVALID_COLUMN_NAME

-9

ERROR_UNRECOGNIZED_PARAMETER

-10

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

AKBID1016 Grind Process and Errors

AKBID1030 Grind Database Contents

AKBID1081 Summary Process and Files

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1196 databases

style='mso-spacerun:yes'>� 2003

Assigning Logins to Aloha Services

Assigning Logins to Aloha Services

============================================================================

AKBID1197

Created: 6 August 2001

Updated: 10 April 2003

Reviewed: 19 January 2003

Microsoft Windows Versions: Windows NT, Windows 2000, Windows XP, Windows Server 2003

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 4.2x � 5.3.x

Subject: Assigning Users to Aloha Services

============================================================================

Summary

Some ALOHA^� application software installations necessitate the increased security of user-level sharing or use versions of Microsoft^� Windows^� in the Back-of-House (BOH) or Front-of-House (FOH) that require to you to configure and assign specific Windows login accounts to CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server).� This document explains when specific logins are required and how to configure them.

Information

When to Assign Specific Login Users to Control Server and EDC Server

If you configure Control Server or EDC Server to run as a Windows service (refer to document AKBID1162) on file servers that use the Windows NT^�, Windows 2000, Windows XP, or Windows Server 2003 Operating System (OS), then by default, the Aloha application software configures the services to log in using the built-in Windows system account.� While this is acceptable in most cases, there are some instances where security or the Windows configuration requires Control Server or EDC Server to log in with a user-login rather than the Windows system account.�

This document applies to you if any of the following are true:

-          You have configured Control Server or EDC Server as a Windows Service on a Windows NT/2000/XP/2003 file server; and you are part of a domain that requires FOH terminals configured with user-level access rather than share-level access.

-          You have configured Control Server or EDC Server as a Windows Service on a Windows NT/2000/XP/2003 file server; and the FOH terminals are configured with Windows NT/2000/XP/2003.

-          You have configured Control Server or EDC Server as a Windows Service on a Windows 2000/XP/2003 SuperSite or EDC file server; and the FOH terminals are configured with Windows 98, Windows Millennium Edition (Me), Windows NT/2000/XP/2003.

-          You are experiencing a memory leak in Windows 2000.

Failure to configure Control Server or EDC Server to log in with a user other than the Windows system account in any of the previous scenarios may result in the following:

-          The Winhook batch file does not have access to copy files to another computer when it has been automatically activated by Control Server, but the files are copied without fault if you manually activate the Winhook batch file from a command line.

-          SuperSite grinds do not consistently connect to FOH terminals.

-          EDC Server cannot connect to FOH terminals to process spooled transactions and delete the SPOOLING file.�

Create a User for Aloha Services

Create a new user on the file server for use as the Control Server and EDC Server login account, and assign Administrator privileges to the login.� The user name is arbitrary, although you should use something descriptive such as 'AlohaSvr'.� Ensure that you have not unintentionally configured an expiring password.� You do not need to configure this user as the local computer's OS or network login.

If you are using Windows NT/2000/XP/2003 on the FOH terminals or if you are using user-level sharing with Windows 95/98/Me, ensure that the user you create for Control Server and EDC Server had read and write access to the BOOTDRV share on the FOH terminals.

Assign a User for Aloha Services

You must perform the following anytime you reregister Control Server or EDC Server as a service.

If you are using Aloha application software versions 5.230 and higher and you are registering Control Server or EDC Server as a service on a Windows NT/2000/XP/2003, then Control Server and EDC Server will automatically prompt you for the login type, so you do not need to manually configure the logins as described in this section.� Refer to document AKBID1019 for more information on command line overrides for login prompts.

If your file server uses the Windows NT OS, perform the following to set the new login as the Control Server and EDC Server login (each must be performed separately):

Select Start/Settings/Control Panel and double-click the Services icon.

Double-click the CtlSvr or EdcSvr service.� If CtlSvr or EdcSvr are not present in the list of services, then they are not configured as Windows services and this document does not apply to you.

Click 'This Account' in the login properties and enter the name and password that you configured for this use.

Click OK.

Restart the computer.

If your file server uses the Windows 2000/XP/2003 OS, perform the following to set the new login as the Control Server and EDC Server login (each must be performed separately):

If you are using Windows 2000 Professional, Windows XP Home Edition, or Windows XP Professional, select Start/Settings/Control Panel, and double-click Administrative Tools.� Double-click Computer Management.

If you are using Windows 2000 Server or Windows Server 2003, select Start/Programs/Administrative Tools, and select Computer Management.

Expand the Services and Applications tree, and select Services.

Double-click the CtlSvr or EdcSvr service.� If CtlSvr or EdcSvr are not present in the list of services, then they are not configured as Windows services and this document does not apply to you.

Select the Log On tab, click 'This account' in the login properties and enter the name and password that you configured for this use.

Click OK.

Restart the computer.

Invisible Grinds

Once you configure Control Server to log in using the above method, you may no longer see the Aloha application software grind applications when they are activated.� You can observe them in the Windows Task Manager, but the grind Graphical-User-Interface (GUI) is not visible.� This does not have an adverse effect on the Aloha application software's ability to function properly, but the following versions of Control Server (and subsequent versions) have been enhanced so as to display the grind GUI: 4.279, 4.427, 5.033, and 5.183.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

AKBID1019 Manually Registering and Un-registering Aloha Applications

AKBID1028 Winhook

AKBID1162 Microsoft Windows Service versus a Standard Application

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1197 connection fail

Magnetic Stripe Card Information

Magnetic Stripe Card Information

============================================================================

AKBID1198

Created: 21 August 2001

Updated: 16 January 2004

Reviewed: 16 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 3.5x � 5.3.x

Subject: Magnetic Stripe Formats and Configurations Accepted by the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software supports magnetic stripe cards as identification for credit cards, employee login cards, gift cards, frequent buyer cards and house account cards.� This document explains the type of magnetic stripe card formats accepted by the Aloha application software and how to configure the magnetic stripe information for each type of use.

Information

MSR Types and Limitations

The Aloha application software supports the following types of Magnetic-Stripe-Readers (MSRs): keyboard-wedge, OPOS (refer to document AKBID1074), and IBM POSS (used with the IBM 4695 POS terminal, refer to document AKBID1032).

If you are using a keyboard-wedge or IBM POSS MSR, the Aloha application software reads magnetic stripe cards with only track one populated, only track two populated, or both track one and track two populated.� If you are using an OPOS MSR with Aloha application software versions 5.036 and lower or versions 5.200 through 5.208, then the Aloha application software cannot read magnetic stripe cards with only track one populated.� Furthermore, Aloha application software versions 5.036 and lower or versions 5.200 through 5.208 cannot read magnetic stripe cards with only track two populated unless you enable the 'Track Two Only' MSR setting within the Aloha application software.� If you enable 'Track Two Only', the Aloha application software ignores any information on track one.� If you are using an OPOS MSR with the Aloha application software versions 5.037 through 5.0x or 5.209 and higher, the Aloha application software reads magnetic stripe cards with only track one populated, only track two populated, or both track one and track two populated (do not enable the 'Track Two Only' MSR setting).

The following table lists the limitations applied to each type of MSR:

Tracks Populated on Card

Keyboard-wedge

OPOS

IBM POSS

Track one only

Yes

Yes, in versions 5.037 through 5.0x or 5.209 and higher.

Yes

Track two only

Yes

Yes, but you must enable 'Track Two Only' in the Aloha application software is you are using versions 5.208 and lower.

Yes

Tracks one and two

Yes

Yes, but if 'Track Two Only' is enabled in the Aloha application software, then track one is ignored.

Yes

Magnetic Stripe Information

The Aloha application software uses the following sentinels and field separators with keyboard-wedge MSRs:

Sentinel

Character

Decimal

Hex

Track 1 start sentinel

%

37

0x25

Track 1 field separator

^

94

0x5E

Track 1 end sentinel

?

63

0x3F

Track 2 start sentinel

;

59

0x3B

Track 2 field separator

=

61

0x3D

Track 2 end sentinel

?

63

0x3F

End stripe read

Carriage Return

13

0x0D

You should only have a single carriage return at the very end of the read.� Do not include a carriage return after each track.� The Aloha application software will interpret each track as a separate cared read if you include a carriage return after each track.

Since a keyboard can mimic a keyboard-wedge MSR, you can test system functionality by typing the sentinels on your keyboard.� For example, to assign employee 400 a MSR password of '999', log in as employee 400, touch 'Change Password' from the Functions/Employee screen, type '%999?', and press the enter key.� Repeat it to verify the password and, in the future, sign on to the system from the floating logo by typing '%999?' and pressing enter.

The Aloha application software recognizes the following format on magnetic stripes (regardless of the MSR type):

Track

Field

Description

1

0

Start sentinel

1

1

A 'B' character (this is a MasterCard/Visa format code and is not required on other types of cards, but should be included to ensure maximum compatibility)

1

2

Account number

1

3

Field separator

1

4

Customer name (last name first, using '/' to separate names)

1

5

Field separator

1

6

Expiration date in YYMM format

1

7

Field separator

1

8

Other data (can be anything in any format)

1

9

End sentinel

Track

Field

Description

2

0

Start sentinel

2

1

Account number

2

2

Field separator

2

3

Expiration in YYMM format

2

4

Other data (can be anything in any format)

2

5

End sentinel

If you are using Aloha application software versions 5.0x and lower with magnetic stripe cards with both track one and track two populated, the Aloha application software parses the account number and expiration date from track one.� Although track two is captured, the contents are ignored.� If track one is not present, the magnetic stripe information is parsed from track two.� If track one is present but it is blank, the Aloha application software still attempts to parse the information from track one and yields a blank read.

If you are using Aloha application software versions 5.2x and higher with magnetic stripe cards with both track one and track two populated, the Aloha application software parses the account number and expiration date from track two.� Although track one is captured, the contents are ignored unless there is pertinent information not stored in track two (customer name).� If track two is not present, the magnetic stripe information is parsed from track one.� If track two is present but it is blank, the Aloha application software still attempts to parse the information from track two and yields a blank read.

It is typically acceptable to truncate track information if you do not require the information held in the fields.� For example, track two does not require fields two through four in order for the Aloha application software to read the account number from track two, although the start and end sentinels are still required.� On the other hand, if you are only eliminating certain fields but still require other fields that follow, you must keep the field separators between blank fields.

Place house account, gift card, and frequent buyer identification numbers in the account number field.

Creating Aloha Gift Certificate Manager Gift Cards

Refer to document AKBID1168 for more information.

Creating Aloha eCards

Magnetic stripe cards for use with Aloha eCards are only available from preferred vendors and are not covered in this document.

Creating Frequent Diner Cards

The Aloha application software does not support frequent diner cards with OPOS MSRs.

If you are using magnetic stripe cards as frequent diner cards, Aloha Technologies recommends programming the customer identification number on track two for maximum compatibility.� For example, using a keyboard-wedge MSR yields ';nnnnnnnnnnnnnnnn?', where 'n' is the card number.

The magnetic stripe card customer identification number must be numeric and match the identification number assigned to the customer card number field in the BackOffice.

Although the Front-of-House (FOH) interface screen defaults to users entering a phone number, if you swipe a magnetic stripe card, the information is input as the card number.� You do not have to manually select Card Number before swiping the magnetic stripe card in the FOH.

Creating House Account Cards

If you are using magnetic stripe cards for house account identification, Aloha Technologies recommends programming the customer identification number on track two for maximum compatibility.� For example, using a keyboard-wedge MSR yields ';nnnnnnnnnnnnnnnn?', where n is the card number.� You can also populate track one to include the customer name, but it is not required.� For example, using a keyboard-wedge MSR yields '%B nnnnnnnnnnnnnnnn^last/first?;nnnnnnnnnnnnnnnn?', where 'n' is the card number, 'last' is the customer's last name and 'first' is the customer's first name.

Creating Employee Login Cards

If you are using magnetic stripe cards as employee login cards, Aloha Technologies recommends programming the employee identification number on track two for maximum compatibility.� For example, using a keyboard-wedge MSR yields ';nnnnnnnnnnnnnnnn?', where 'n' is the identification number.

The FOH reads the magnetic stripe's first 16 characters as the employee ID.� The ID is not required to be 16 characters, but if the unique ID number is not 16 characters in length, additional characters may be mistaken for a portion of the ID number.

�

ID cards should have the same unique identification on both track one and track two.� This not only ensures compatibility with all MSR devices, but future versions of the Aloha application software may compare the readings from both tracks (if available) to verify the data and detect defective ID cards.�

Sites using MSR devices that are limited to reading only a single track may consider placing the unique identification on the single track read by the MSR.� This can result in card reads that are 50% faster.

Creating PMS Room Cards

The Aloha application software can process Property Management Systems (PMS) room cards with one of two methods.� The first method is a magnetic stripe card encoded with a straight number.� The Aloha application software sends this number to the PMS and the PMS must parse the room number from the information.� For example, if the card for room number 1234 is encoded with 0045001234000, the Aloha application software sends 0045001234000 to the PMS and the PMS must determine that this represents room 1234.� If the room cards have one or more common prefixes, you should consider adding these prefixes to the tender configuration in the Aloha application software to decrease mistakes, but you are not required to do so.

The Aloha application software uses a second method if the room card is programmed with standard magnetic stripe fields as described in the Magnetic Stripe Information section of this document.� In this case, the Aloha application software only sends the information from the Account Number field to the PMS.� As in method one, it is up to the PMS to parse the room number from the information sent by the Aloha application software.�

Utilities and Debugging

CARD.EXE (available on the Aloha Technologies FTP site or Reseller Portal) captures all keyboard-based magnetic stripe reader (MSR) and scanner input, including actual hexadecimal and decimal representations of the characters, which is useful for checking non-printing characters.

Usage: CARD.EXE [options]

Options:

> CARD.TXT�� Writes the data to CARD.TXT for future reference.

In Aloha versions 5.045 through 5.0x and 5.211 and higher, you can enable additional MSR information in the debouts with the DEBUGMSR system environment variable.� Enable the variable by assigning it a value of TRUE.

Extended Information

Magnetic stripe coercivity (hi-co or lo-co) is irrelevant to the Aloha application software.

Caveats

You should only have a single carriage return at the very end of the read.� Do not include a carriage return after each track.� The Aloha application software will interpret each track as a separate cared read if you include a carriage return after each track.

If you are using the Aloha application software versions 5.0x and lower and track one is not present on a magnetic stripe card, the magnetic stripe information is parsed from track two.� If track one is present but it is blank, the Aloha application software still attempts to parse the information from track one and yields a blank read.

If you are using the Aloha application software versions 5.2x and higher and track two is not present on a magnetic stripe card, the magnetic stripe information is parsed from track one.� If track two is present but it is blank, the Aloha application software still attempts to parse the information from track two and yields a blank read.

The Aloha application software does not support frequent diner cards with OPOS MSRs.

============================================================================

See also:

Delivery/Frequent Buyer User Manual

Gift Certificate Manager User Manual

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1032 IBM 4695 POS Terminal

AKBID1074 OPOS

AKBID1161 EMPMAGCARDMASK in the ALOHA.INI

AKBID1168 Configuring Gift Cards for Use with Gift Certificate Manager

AKBID1186 FOH Manual and Magnetic Stripe Passwords

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1198 co delivery delivery/fb fb hi hico high lo loco low mag magcard magcards swipe

�

Configuring a SuperSite FOH Terminal

Configuring a SuperSite FOH Terminal

============================================================================

AKBID1199

Created: 28 August 2001

Updated: 2 June 2003

Reviewed: 16 March 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Configuring a FOH Terminal for Use in a SuperSite

============================================================================

Summary

Front-of-House (FOH) terminals in ALOHA^� application software SuperSites are configured similar to FOH terminals in standard Aloha application software installations.� Although most of the differences reside in the AUTOEXEC.BAT and IBERCFG.BAT, some minor configuration changes are required that depend on the version of Microsoft^� Windows^� that is installed on the terminal.

Information

You must first configure the SuperSite's IBERCFG.BAT as explained in document AKBID1118 and place it in the SuperSite file server's Aloha application software BIN folder before proceeding with this document.

Configure Windows and Install the Aloha Application Software

Configure the terminal as a standard FOH terminal using the respective AKB document, but do not install the Aloha application software.

Windows 95 and Windows 98

Install the Aloha application software FOH using the FOH terminal installation application (\TERMINST\SETUPTRM.EXE) on the Aloha Installation CD.� Specify the SuperSite file server as the terminal's file server and logically configure the remaining options.� Since you are going to discard the IBERCFG.BAT created by the installation application and replace it with the IBERCFG.BAT you created for the SuperSite, it does not matter if the settings do not apply to the final configuration; you are only entering these settings in the installation application so it can locate a file server in which to copy the binary and data files and complete the installation.

Once the installation is complete, edit the AUTOEXEC.BAT so it performs the following tasks:

1.          Declares the system path.

2.          Declares the TERM variable (the terminal number).� This is the single variable required to designate the terminal in the IBERCFG.BAT and it is the terminal number assigned in the Aloha application software Back-of-House (BOH).

3.          Updates the BIN folder from the NEWBIN folder.� Since the IBERCFG.BAT is in the BIN folder, BIN updates should occur before the IBERCFG.BAT is called.

4.          Calls the IBERCFG.BAT.� The IBERCFG.BAT declares all other settings.

The following is an example of a Windows 95 or Windows 98 SuperSite terminal's AUTOEXEC.BAT:

SET PATH=%PATH%;C:\ALOHA\BIN

SET TERM=1

COPY C:\ALOHA\NEWBIN\*.* C:\ALOHA\BIN\*.*

ECHO Y | DEL C:\ALOHA\NEWBIN\*.*

CALL C:\ALOHA\BIN\IBERCFG.BAT

If you had configured your IBERCFG.BAT according to AKBID1118 and placed it in the SuperSite file server's BIN folder prior to running the FOH terminal installation application, then your should only have to restart the terminal to complete the configuration.�

Windows Me, Windows NT, Windows 2000, Windows XP, and Windows Server 2003

Install the Aloha application software FOH using the FOH terminal installation application (\TERMINST\SETUPTRM.EXE) on the Aloha Installation CD.� Specify the SuperSite file server as the terminal's file server and logically configure the remaining options.� Since you are going to discard the IBERCFG.BAT created by the installation application and replace it with the IBERCFG.BAT you created for the SuperSite, it does not matter if the settings do not apply to the final configuration; you are only entering these settings in the installation application so it can locate a file server in which to copy the binary and data files and complete the installation.

The FOH installation application creates an IBERCFG.BAT file in the Aloha application software folder.� Since Windows Millennium Edition (Me), Windows NT^�, Windows 2000, and Windows XP do not fully support an AUTOEXEC.BAT, this IBERCFG.BAT substitutes for the AUTOEXEC.BAT and it is called from the Windows StartUp folder.� This batch file will be referred to as the 'terminal IBERCFG.BAT' so as to not confuse it with the IBERCFG.BAT you created and placed in the BIN folder, which will be referred to as the 'SuperSite IBERCFG.BAT'.�

Once the installation is complete, edit the terminal IBERCFG.BAT in the Aloha application software folder so it performs the following tasks (remove any other functions added by the FOH terminal installation application):

1.          Declares the system path.

2.          Updates the BIN folder from the NEWBIN folder.� Since the IBERCFG.BAT is in the BIN folder, BIN updates should occur before the IBERCFG.BAT is called.

3.          Calls the SuperSite IBERCFG.BAT.� The SuperSite IBERCFG.BAT declares all other settings.

The following is an example of a Windows Me, Windows NT, Windows 2000 or Windows XP SuperSite terminal's terminal IBERCFG.BAT:

SET PATH=%PATH%;C:\ALOHA\BIN

COPY C:\ALOHA\NEWBIN\*.* C:\ALOHA\BIN\*.*

ECHO Y | DEL C:\ALOHA\NEWBIN\*.*

CALL C:\ALOHA\BIN\IBERCFG.BAT

Since the TERM system environment variable is required for the SuperSite IBERCFG.BAT, you must add it to the Windows system environment variables, and assign it a value to represents the terminal number assigned in the Aloha application software Back-of-House (BOH).

If you had configured your SuperSite IBERCFG.BAT according to AKBID1118 and placed it in the SuperSite file server's BIN folder prior to running the FOH terminal installation application, then you should only have to restart the terminal to complete the configuration.�

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

AKBID1009 Windows 95 FOH Terminal Setup

AKBID1013 Windows 98 FOH Terminal Setup

AKBID1035 Windows NT FOH Terminal Setup

AKBID1092 Windows 2000 FOH Terminal Setup

AKBID1101 Windows Me FOH Terminal Setup
AKBID1118 SuperSite IBERCFG.BAT

AKBID1125 SuperSite Time Synchronization

AKBID1126 SuperSite-Specific System Environment Variables

AKBID1176 Windows XP FOH Terminal Setup

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1199

�

Chit Information Files

Chit Information Files

============================================================================

AKBID1200

Created: 1 October 2001

Updated: 8 October 2001

Reviewed: 19 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x

Subject: Creating Chit Information Files

============================================================================

Summary

The ALOHA^� application software creates text files with remote printer chit information for you to use in creating and printing custom chits.� You must create an application or batch file that processes and deletes the chit information files.�

The Aloha application software does not offer any fault tolerance features for chit information files.

Information

The following variables enable and control chit information file output:

Variable

Location

Description

CHITFILEPATH

System Environment

Enables chit information files on the local terminal and defines the local location of the chit information files.� For example, SET CHITFILEPATH=C:\ALOHA\CHITS

CHECKFILEDELIMITER

ALOHA.INI

Defines the field separator used in the chit output files.� For example, CHECKFILEDELIMITER=,

The CHITFILEPATH environment variable enables chit information file output and defines the location in which to write the chit information files.� You must define this variable independently on each terminal, and you must manually create the target folder if it does not already exist.

CHITFILEPATH does not use the FISCALPRINTEXE or SKIPALOHAPRINT variables in the ALOHA.INI as CHECKFILEPATH does (refer to AKBID1105 for more information on guest check information files and the CHECKFILEPATH system environment variable).

New chit information files are created in the CHITFILEPATH each time the Aloha application software prints a chit.� You have to employ third-party software to process and delete the chit information files.� Processing chit files can include formatting and sending the information to a printer, Kitchen-Video-System (KVS) or other hardware such as a drink dispenser.� The third-party software must delete the chit information files after processing them.

Since chit information files are only created when the Aloha application software attempts to print a remote chit, you have to configure mock printers and printer groups (assuming you do not want the Aloha application software to print actual remote chits).

Chit Information Files

The Aloha application software labels chit information files using table_x_n.CHT, where table is the table number, x is the printer ID (as configured in the Aloha application software) and n is a sequentially increasing number related to this transaction.

Chit information files are not created for employees using the Aloha application software's training mode.

Chit information files are multi-line ASCII text file with the following format:

<keyword>�� <value(s)>

Keywords start in column one and values start in column 15.� The total length of each line is variable (depending on the values) and the following keywords are supported:

Keyword

Values

EMPLOYEE

Employee number, first name, last name, nickname

DOB

Date of business (YYYYMMDD)

DATE

System date (YYYYMMDD)

TIME

System time (HH:MM:SS)

ORDERNAME

Name of the TableService table or QuickService order.

GUESTS

Number of guests.

ITEM

Item ID, quantity

VOIDITEM

Voided item ID, quantity

SPECIALMSG

Special item modifier message to print on check.

MODIFIER

Item ID, quantity

Extended Information

No information.

Caveats

The Aloha application software does not offer any fault tolerance features for chit information files.

============================================================================

See also:

AKBID1105 Guest Check Information Files

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1200 bar dump kitchen

style='mso-spacerun:yes'>� 2003

�

Multi-resolution Bitmap Folders

Multi-resolution Bitmap Folders

============================================================================

AKBID1201

Created: 2 October 2001

Updated: 3 April 2003

Reviewed: 18 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.3.x

Subject: Bitmap Folder and Naming Conventions in an Environment with Multiple Resolutions

============================================================================

Summary

Some ALOHA^� application software installations use a mix of terminals with different screen resolutions.� For example, two terminals may use an 800x600 screen resolution while a third terminal may use a 640x480 screen resolution.� This can become confusing to users when they try to assign bitmaps to buttons, screens and panels in the Aloha application software panel editor because they do not know for which resolution the bitmap is designed.� For example, you may have a version of each bitmap for the 800x600 screen resolution and a second version of each bitmap for the 640x480 screen resolution.� This document describes the bitmap placement created by Aloha Technologies to assist panel editor users.

Information

You can place bitmaps in the Aloha application software BMP folder or in subfolders for each screen resolution within the BMP folder.� The subfolders for each screen resolution are labeled using a 'x_y' format, where x is the screen width (in pixels) and y is the screen height (in pixels).� For example, you would label the folder for the 640x480 screen resolution as \BMP\640_480, the 800x600 screen resolution as \BMP\800_600, and so on.�

This enables you to place bitmaps that are common to all screen resolutions in the BMP folder and bitmaps for a specific screen resolution in a separate folder.� When you open panel editor, you are required to select the screen resolution of the panels for which you are editing.� This resolution is used in loading bitmaps.� The bitmap drop-down list only displays bitmaps in the BMP folder.� In order to use bitmaps in the screen resolution folders, they must have the same file name as the file in the BMP folder.

�

For example, if you select a screen resolution of 800x600 when opening panel editor, then your bitmap drop-down lists only display bitmaps in the BMP folder.� However, bitmaps are loaded from the 800_600 folder first, and the BMP directory second.� This is less complicated than trying to select bitmaps from a list of bitmaps for different screen resolutions.

The Aloha application software Front-of-House (FOH) is also designed to read bitmaps in both the BMP folder and the screen resolution subfolder.� This is automatically determined by the screen resolution detected by the FOH or set via the ALOHAXRES and ALOHAYRES system environment variables.� Refer to AKBID1119 for more information on the ALOHAXRES and ALOHAYRES system environment variables.

As of this writing, TableService bitmaps used for cool interfaces, item buttons or tender buttons must reside in the Aloha POS BMP folder, not a subfolder for the screen resolution.� Refer to document AKBID3137 for more information on assigning item and tender bitmaps in TableService.

Extended Information

No information.

Caveats

As of this writing, TableService bitmaps used for cool interfaces, item buttons or tender buttons must reside in the Aloha POS BMP folder, not a subfolder for the screen resolution.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1119 FOH Adjustable Resolution Settings

AKBID3137 TableService Tender and Item Bitmaps

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1201 bmps 1024 1024x768 480 600 640 768 800 plan

style='mso-spacerun:yes'>� 2003

�

Installing Microsoft SQL Server 2000

Installing Microsoft SQL Server 2000

============================================================================

AKBID1202

Created: 8 October 2001

Updated: 16 December 2003

Reviewed: 16 December 2003

Microsoft Windows Versions: Windows NT, Windows 2000, Windows XP, Windows Server 2003

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x

Subject: Installing Microsoft SQL Server 2000 for use with the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software versions 5.2x and higher supports Microsoft^� SQL Server 2000 relational-databases (RDB).� This document explains how to configure SQL Server for use with the Aloha application software, and how to install the Aloha application software in order to use a RDB.

Information

For easiest installation and configuration, setup an Aloha application software file server with SQL Server in the following order:

Install and configure Microsoft^� Windows NT^�, Windows^�2000, Windows XP, or Windows Server 2003.

Install and configure SQL Server.

Install and configure the Aloha application software.

If you are converting an existing .DBF-based system to an SQL system, following the steps listed in this document, and reinstall Aloha from the Aloha Installation CD just as if it were a new installation.� The Aloha application software will use the existing data and configuration to create the RDB.� You will have to regrind any existing dated folders in order to add them to the RDB, though.

Operating System Configuration

Install the Windows operating system (OS) as described in the appropriate Aloha Knowledge Base (AKB) document.

The preferred hard drive-partitioning scheme for an Aloha application software file server with an RDB is different than a non-RDB Aloha application software file server.� Rather than configuring hard drive space for dated folders, space for the RDB becomes paramount.� Refer to document AKBID1183 for more information on hard drive partitions and file systems.

SQL Licenses

SQL Server 2000 requires a single Per Seat Client-Access-License (CAL) for each Device that accesses the database. Therefore, one CAL is required for the POS file server and an additional Per Seat CAL is required for each workstation running a remote instance of Aloha Manager.

This information is based on Aloha Technologies understanding of Microsoft's terms documented in the LICENSE.TXT file located in the root folder of the Microsoft SQL 2000 installation CD. Aloha Technologies does not warrant that this information is correct. Refer to the LICENSE.TXT file or consult Microsoft for specific questions.

Installing SQL

Insert the SQL Server 2000 installation CD.� If the installation application does not automatically start, manually start AUTORUN.EXE from the root folder of the Microsoft SQL Server 2000 installation CD.

Install any perquisites suggested by the installation application before installing SQL Server and before proceeding with the following SQL Server 2000 instructions:

Click 'Install SQL Server 2000 Components'.

Click 'Install Database Server' from the Install SQL Server 2000 Components window.�

Select 'Local Computer' from the Computer Name window, and click Next.

Select 'Create a new instance of SQL server, or install Client Tools' from the Installation Selection windows and click 'Next'.

Select 'Server and Client Tools' from the Installation Definition window and click Next.

Select 'Default' from the Instance Name window and click Next.

Select 'Typical', and select the program and data file locations from the Setup Type window.� Install the program files on the partition intended for non-Aloha applications (usually the default location on C:), and install the database files on the partition intended for the RDB database files (such as E:).� If you just enter the drive letter for the database location, then SQL Server 2000 automatically assumes the path of \MSSQL\DATA.� For example, if you enter E: for the database location, SQL Server 2000 installs the database in E:\MSSQL\DATA.� Click Next.

Set SQL Server to use the local system account (unless otherwise required by the site's network administrator) and set the SQL Server service to automatically start.� Click Next.

Select 'Mixed Mode' from the Authentication Mode window, set the sa password to a blank password and click Next.� The Aloha application software requires a blank password for the sa user during installation.� For security purposes, a password can be configured for the sa user after the Aloha application software is installed.

When the installation is complete, restart the computer.

Configuring SQL

After the computer has restarted, perform the following to configure SQL Server:

Click Start/Programs/Microsoft SQL Server/Enterprise Manager to open the SQL Server Enterprise Manager.

On the left side of the screen, expand Microsoft SQL Servers/SQL Server Group/<the file server's network name> and double-click Databases.

Delete the Northwind and Pubs databases to conserve disk space.

On the left side of the screen, expand Microsoft SQL Servers/SQL Server Group/<the file server's network name>/Security and click Logins.� Double-click the 'sa' user.

Clear the sa user password, and click OK.

Close SQL Server Enterprise Manager.

The Aloha application software requires a blank password for the sa user during installation.� For security purposes, a password can be configured for the sa user after the Aloha application software is installed.

The Aloha application software installation will not complete without a blank password for the sa user or if administrative abilities are removed from the sa user.

Installing Aloha

Install the Aloha application software using the Aloha Installation CD.

Select 'MS SQL Server' on the Database Configuration window, and set the 'Computer Name' and 'Path To Database'.� Set the database path to the same location as you set when you configured the SQL Server 2000 software, but include the entire path (for example, E:\MSSQL\DATA).� Click 'Next', finish the installation, and restart the computer.

If the Aloha application software is already installed on the file server without selecting the SQL options, reinstall the Aloha application software from the Aloha Installation CD using the SQL options.

If the Aloha application software cannot create the new RDB, open the file server properties in SQL Enterprise Manager and ensure that you configured the Security Authentication as 'SQL Server and Windows' rather than 'Windows Only'.

Configuring Aloha

The Aloha application software automatically configures the RDB during the installation process, but you can change the amount of data stored in the RDB and the number of days before purging it.

To access the Aloha application software data storage options, open Aloha Manager, and select Maintenance/SQL Settings.� The Sales Group 1, Sales Group 2, and Payments/Labor subtabs contain options for summary data stored in the RDB.� The Grind subtab contains options for detailed data stored in the RDB.

The RDB becomes very large over time and users should consider adjusting these settings to best suite them.� In general, the summary data is intended for long term storage, and the detailed (or Grind) data is intended for short-term storage.

Changing the sa Password

The Aloha application software requires a user name of sa with a blank password to access the RDB during the initial installation process.� Once the Aloha application software is installed, user's can change the user name and password that the Aloha application software uses to access the RDB.

Once the new user or sa password is configured in SQL Server, edit the SQL.INI on the %IBERDIR%\SQL folder, and change the DBUserName and DBPassword variables to reflect the correct information.

Since the password is viewable in the SQL.INI, some users set the password to 'true', so the SQL.INI reads 'DBPassword=true'.� This is intended to appear as a setting to enable or disable the password instead of displaying the actual password.

Database Maintenance

The ability to enable auto-expansion of databases is part of SQL Server 2000.� This option enables SQL Server to increase the size of the RDB as needed rather than require manual intervention the RDB is full.

With auto-expansion enabled, the RDB may eventually consume the allotted hard drive space without the user knowing it.� It is important that the user devises an RDB archiving and purging scheme to combat this problem.

Perform the following to enable auto-expansion:

Click Start/Programs/Microsoft SQL Server/ Enterprise Manager to open the SQL Server Enterprise Manager.

On the left side of the screen, expand Microsoft SQL Servers/SQL Server Group/<the file server's network name> and click Databases.

Right-click the ibersql database and select Properties.

Select the Data Files tab from the ibersql Properties window.

Select 'Automatically grow file' and set it to 10%.

Set the maximum file size in regards to the disk space you have allocated to the RDB.

Select OK.

User Maintenance

Perform the following to configure ibersql as the default database for the sa user:

Click Start/Programs/Microsoft SQL Server/Enterprise Manager to open the SQL Server Enterprise Manager.

On the left side of the screen, expand Microsoft SQL Servers/SQL Server Group/<the file server's network name>/Security and click Logins.� Double-click the sa user.

Adjust the properties of the sa user to use ibersql as the default database.

Close SQL Server Enterprise Manager.

Extended Information

Remote SQL

You can also run SQL Server on a separate computer than the Aloha application software file server.� This is useful for clients that want to keep the Aloha application software SQL database consolidated with existing SQL databases on a separate SQL server.� This enables you to run Aloha Manager (and thus, Grind) on one file server and store data on a different file server.

To enable the Aloha application software to utilize a remote SQL server, install the Aloha application software on the Aloha file server as explained in the Installing Aloha section of this document, but set a different 'Computer Name' and 'Path to Database' than previously explained.� Set the SQL server's network name as the 'Computer Name' (for example, SQLSERVER) and set the SQL server's local path to the database as the 'Path to Database' (for example, E:\MSSQL\DATA).� The path must be the SQL server's local path as if you were actually on the SQL server.

You are not required to install the Aloha application software on the SQL server.

If you are using a remote SQL server on a SuperSite where you will experience a high flow of data between the Aloha file server and the SQL file server, you should consider using dedicated network adaptors for communication between the two file servers.� This will decrease the strain placed on the rest of the network, increase the bandwidth between the two file servers, and provide additional fault tolerance by bypassing the other points of failure throughout the rest of the network.

Caveats

The licensing information in this document is based on Aloha Technologies understanding of Microsoft's terms documented in the LICENSE.TXT file located in the root folder of the Microsoft SQL 2000 installation CD. Aloha Technologies does not warrant that this information is correct. Refer to the LICENSE.TXT file or consult Microsoft for specific questions.

The Aloha application software installation will not complete without a blank password for the sa user or if administrative abilities are removed from the sa user.

If the Aloha application software cannot create the new RDB, open the file server properties in SQL Enterprise Manager and ensure that you configured the Security Authentication as 'SQL Server and Windows' rather than 'Windows Only'.

With auto-expansion enabled, the RDB may eventually consume the allotted hard drive space without the user knowing it.� It is important that the user devises an RDB archiving and purging scheme to combat this problem.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1131 Installing a New RDB Over and Existing RDB

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID3108 Setting RDB Grind Positions

AKBID3109 Re-synchronizing DBF Files From an RDB

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1202 sql2000

style='mso-spacerun:yes'>� 2003

�

Configuring Aloha as a Thin Client on Windows Terminal Server

Configuring Aloha as a Thin Client on Windows Terminal Server

============================================================================

AKBID1203

Created: 5 November 2001

Updated: 28 October 2003

Reviewed: 17 December 2003

Microsoft Windows Versions: Windows 2000, Windows Server 2003

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.232 � 5.3.x

Subject: Configuring Aloha for use as a Windows Terminal Server Client

============================================================================

Summary

You can configure the ALOHA^� application software Front-of-House (FOH) as a thin-client using Microsoft^� Windows^� Terminal Server, which are part of the Windows 2000 Server and Windows Server 2003 operating systems (OS).� This enables you to run the FOH as a thin-client on virtually any operating system or computer that supports Terminal Server clients, such as Windows CE.

Although it is possible to base all of an installation's FOH terminals on Terminal Server technology, Aloha Technologies does not recommend this configuration since it nullifies the Aloha application software's built-in fault tolerance functionality (refer to document AKBID1107).� Thin-clients are not configured as master-capable or server-capable, so in the event that network connectivity with the master terminal or the file server is lost, the thin-client terminals cannot assume master or file server functionality.

Information

You can configure Terminal Server on the Aloha application software file server or on a stand-alone file server.� While the prior configuration is more cost effective, the later configuration decreases the Aloha application software file server's workload and offers increased fault tolerance (since it can function without the Aloha application software file server).

Install Terminal Server on the Aloha File Server

If you are going to install Terminal Server on your Aloha file server, configure Windows 2000 Server (you cannot use Windows 2000 Professional) or Windows Server 2003 on your file server as you would configure a standard file server by using document AKBID1093 or AKBID1224, and install the Aloha application software as you would a standard file server.� Since the thin-client terminals are neither master-capable nor server-capable, you do not need to configure the file server's network name using a TERMSTR+TERM nomenclature, but instead use a standard file server name such as Alohaboh.� Ensure that you enable the Terminal Server components when you configure the Windows options.

Following installation of the Terminal Server components, you must activate the Terminal Server licenses through Microsoft.� Failure to activate Terminal Server results in client licenses that expire after 90 days.

Configure the standard FOH terminals in a normal fashion using the appropriate Aloha Knowledge Base (AKB) document and configure the thin-client terminals in Aloha Manager as you would a standard FOH terminal.

Download Wait.exe from the Aloha Technologies FTP site and place it in the Aloha application software Bin folder on the Terminal Server file server.� Wait.exe enables you to add timed pauses to batch files and is referred to later in this document.� Refer to document AKBID1012 for more information on Wait.exe.

Create a batch file in the file server's Aloha application software folder for each thin client terminal (for example D:\Aloha\Term5.bat, Term6.bat and so on).� Besides declaring the TERM and CALIBRATE variables, the batch file should disable master and server capabilities, and have logic to make it a looping batch file.� This ensures that the Aloha application software automatically restarts (after pausing for 15 seconds) following a refresh or the EOD process.� For example:

:TOP

SET CALIBRATE=D:\ALOHA\BIN\CALIB.EXE

SET TERM=5

SET MASTERCAPABLE=FALSE

SET SERVERCAPABLE=FALSE

IF EXIST %LOCALDIR%\TMP\EXITING DEL %LOCALDIR%\TMP\EXITING

START /WAIT %LOCALDIR%\BIN\IBER.EXE

%LOCALDIR%\BIN\WAIT.EXE 15

GOTO TOP

If your client device does not already have a Terminal Server Client installed, then install the Microsoft Terminal Server Client software (on the file server in C:\Windows\System32\Clients\TSClient\Win32) on the FOH thin-client terminals, and use the Terminal Server Client Wizard to configure the client to automatically log in to the Terminal Server file server and start the terminal's batch file.� The 'Save my password' option is not available on all versions of the client or all operating systems.

If you are installing the client software on a Windows CE device that does not already include the client software, refer to the �Installing Windows Terminal Server Client on Windows CE Devices� section it he Extended Information portion of this document.

If you are using Windows 2000 Server and enable automatic login on the client, then you must also perform the following to enable it on the Terminal Server file server:

Select Start/Programs/Administrative Tools/Terminal Server Configuration.

Double-click the RDP-Tcp connections.

Select the Logon Settings tab.

Clear 'Always prompt for password'.

Click OK.

Aloha Technologies recommends that you use different logins for each Terminal Server client.� This enables you to better differentiate each client when viewing them from the Terminal Server Management application in Windows.

Install Terminal Server on a Stand-alone File Server

If you are configuring your Terminal Server file server as a stand-alone file server, first configure the Aloha file server as you would a standard file server using the appropriate AKB document and configure your standard FOH terminals in a normal fashion using the appropriate AKB document.� Also configure the thin-client terminals in Aloha Manager as you would a standard FOH terminal.

Configure your Terminal Server file server with Windows 2000 Server (you cannot use Windows 2000 Professional) or Windows Server 2003 as you would a standard FOH terminal using AKBID1092 or AKBID1223, ensuring that you enable the Terminal Server components when you configure the Windows options.� Since the thin-client terminals are neither master-capable nor server-capable, the network name given to the Terminal Server file server is irrelevant, although the FOH terminal installation application forces you to use the TERMSTR+TERM nomenclature during installation.� You might consider using the TERMSTR+TERM nomenclature as it applies to one of your thin-client terminals as the Terminal Server file server's permanent network name.� For example, if your system's TERMSTR is TERM and your thin-client terminals are terminals five, six and seven, name the Terminal Server file server Term5.

Following installation of the Terminal Server components, you must activate the Terminal Server licenses through Microsoft.� Failure to activate Terminal Server results in client licenses that expire after 90 days.

Install the Aloha application software using the FOH terminal installation application in the Terminst folder on the Aloha Installation CD, but do not configure the terminal as either master-capable or server-capable and disable AUTOEXIT and REBOOTNT.

Download Wait.exe from the Aloha Technologies FTP site and place it in the Aloha application software Bin folder on the Terminal Server file server.� Wait.exe enables you to add timed pauses to batch files and is referred to later in this document.� Refer to document AKBID1012 for more information on Wait.exe.

The FOH terminal installation application creates an Ibercfg.bat batch file in the Aloha application software folder (for example D:\Aloha\Ibercfg.bat); create copies of this file for use by each thin-client FOH terminal (for example, D:\Aloha\Term5.bat, Term6.bat and so on) and edit the TERM variable in each batch file to assign it a value reflecting the correct terminal number.� Also add logic to the batch file to make it a looping batch file.� This ensures that the Aloha application software automatically restarts (after pausing for 15 seconds) following a refresh or the EOD process.� For example:

:TOP

SET IBERROOT=ALOHA

SET LOCALDIR=D:\ALOHA

SET CALIBRATE=D:\ALOHA\BIN\CALIB.EXE

SET EDCPATH=\\ALOHABOH\BOOTDRV\ALOHA\EDC

SET TERMSTR=TERM

SET TERM=5

SET NUMTERMS=7

SET SERVER=ALOHABOH

SET MASTERCAPABLE=FALSE

SET SERVERCAPABLE=FALSE

IF EXIST %LOCALDIR%\TMP\EXITING DEL %LOCALDIR%\TMP\EXITING

COPY %LOCALDIR%\NEWBIN\*.* %LOCALDIR%\BIN

ECHO Y | DEL %LOCALDIR%\NEWBIN\*.*

START /WAIT %LOCALDIR%\BIN\IBER.EXE

%LOCALDIR%\BIN\WAIT.EXE 15

GOTO TOP

If your client device does not already have a Terminal Server Client installed, then install the Microsoft Terminal Server Client software (on the file server in C:\Windows\System32\Clients\TSClient\Win32) on the FOH thin-client terminals, and use the Terminal Server Client Wizard to configure the client to automatically log in to the Terminal Server file server and start the terminal's batch file.� The 'Save my password' option is not available on all versions of the client or all operating systems.

If you are installing the client software on a Windows CE device that does not already include the client software, refer to the �Installing Windows Terminal Server Client on Windows CE Devices� section it he Extended Information portion of this document.

If you are using Windows 2000 Server and enable automatic login on the client, then you must also perform the following to enable it on the Terminal Server file server:

Select Start/Programs/Administrative Tools/Terminal Server Configuration.

Double-click the RDP-Tcp connections.

Select the Logon Settings tab.

Clear 'Always prompt for password'.

Click OK.

Aloha Technologies recommends that you use different logins for each Terminal Server client.� This enables you to better differentiate each client when viewing them from the Terminal Server Management application in Windows.

Using STOPLOGO to Decrease Long Login Pause

Since all screen activity is transferred over the network, you may experience long pauses when you touch the Aloha application software's FOH floating logo, since the motion of the logo will have consumed a lot of bandwidth, especially on a wireless system.� If you are using Aloha version 5.211 or higher, enable the STOPLOGO system environment variable (SET STOPLOGO=TRUE) to disable the logo from floating and alleviate the pause.� This variable is considered true regardless of the assigned value.� If this variable is not desired, completely remove it.

Extended Information

Troubleshooting the FOH

Remember, the FOH is actually running on the terminal server file server, even though the client software is on a different device.� If you are having problems with the FOH, you should attempt to run the client's batch file directly on the file server, thus removing the client software from the problem.� That way, it is no different than running the FOH on a standard terminal, so you might have an easier time troubleshooting the problem in a more familiar setting.

Handheld Resolution Configuration

If you are using low-resolution displays (such as the display on a handheld device or pocket PC), refer to documents AKBID1097 and AKBID1107 for information on adjusting the FOH screen and font sizes.

If you are using a handheld device, Aloha Technologies recommends using a utility for Windows CE that enables you to rotate the display on handheld devices to landscape and increase the resolution to 640x480.� JS Landscape (available from Jimmy Software at http://www.jimmysoftware.com) enables you to perform these functions, as does Nyditot Virtual Display (available from Nyditot at http://www.nyditot.com).� The Nyditot works with Windows CE .NET, whereas at the time of this writing, JS Landscape does not.

Terminal Server Client Starts Multiple Sessions

Depending on your version of Windows CE, the Windows CE Terminal Server client might not display an icon in the list of open applications in the Windows CE start menu.� This can lead you to believe that the client (and thus, the Aloha application software FOH) is not running, so you might inadvertently start a second copy of the client.� This results in the FOH to displaying a 0xd network error on the Windows CE device because you are attempting to start two copies of the Aloha application software FOH with the same TERM variable.� To alleviate this problem, remove shortcuts to the Terminal Server client from the Start Menu and Windows desktop, and instead place a shortcut only in the Windows StartUp folder.� This way, the only way to start the client is to restart the device, but it eliminates this error from occurring because you are not able to start a second connection with the same terminal number.

To further ensure that you do not start a second copy of the same instance, you should configure Terminal Server to immediately end the session once the connection is broken.� To do this, perform the following:

1.        Start the Terminal Server Configuration applet.

2.        Open the connection properties.

3.        Select the Sessions tab.

4.        Disable the �Override User Settings� option top near that enables time limits on sessions.

5.        Enable the �Override User Settings� option near the bottom that lets you lets you immediately end the session when a connection is broken.

This way, it will not start a second session if you reset the device.

Using WAITCE.EXE for NICs That Initialize Slowly

Some Windows CE devices, when used in conjunction with some wireless Network-Interface-Cards (NICs), may attempt to start the Terminal Server client in the StartUp folder before the NIC has initialized.� This may cause the Terminal Server client to fail.� Use the Waitce.exe utility to work around this.� Refer to document AKBID1012 for more information on Waitce.exe.

Symbol Technologies MSR Support

ALOHA_SYMBOL_MSR_ARM.EXE is designed for use with a Symbol Technologies Windows CE-based handheld device that uses a StrongARM processor.� This utility, specifically tested with a Symbol Technologies PPT2846 handheld and a Symbol Technologies MSR3006 Magnetic-Stripe-Reader (MSR), converts MSR input from RS232 to keyboard input.� This enables communication with the Aloha application software FOH if you are using Windows Terminal Server.� Refer to document AKBID1012 for more information).

Installing Windows Terminal Server Client on Windows CE Devices

If your Windows CE-based device does not come preloaded with the Terminal Server client software, you can download the client software for Pocket PC or Windows CE .NET at http://www.microsoft.com/windowsmobile/resources/downloads/pocketpc/default.mspx.� Once you install the client software, you must run \Windows\Mstc.exe in order to configure a new connection.

If you are using a previous version of Windows CE, Windows CE 3.0 Terminal Server client software is available from Microsoft at http://www.microsoft.com/mobile/handheldpc/downloads/default.asp.� Perform the following if you are unable to install the Terminal Server client on your device because of compatibility errors generated by the installation application:

Copy Rdp_hpc_*.cab from the \Program Files\Microsoft Activesync\Terminal Server Client folder to a temporary folder on your device.

Using the Windows CE device, double-click Rdp_hpc_*.cab file that is designed for your type of device (if you are not sure which .cab file to use, you can attempt to install each one and Windows CE will only enable you to install the correct file) to install the software (ignore any compatibility errors).

Navigate to the \My Device\Program Files\Terminal Server Client folder on your Windows CE device.� There are two applications: Mstc40 (the Terminal Server client) and Tscwiz (the Terminal Server client wizard).� You can cut and paste these files to the \Windows\Start Menu\Programs folder to add them to the Programs menu.

Disabling Buttons on Handheld Devices

If you are not able to disable the buttons on your handheld device, DoNothing.exe (available from http://www.scottandmichelle.net/scott/cestuff.html) enables you to assign buttons to an application that does nothing.

Configuring Automatic Logon for the Terminal Server Client

If automatic login fails to function properly, perform the following to disable the DontDisplayLastUserName registry key from the Terminal Server file server:

The incorrect use of the Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.

To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

Path out HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Current Version\Winlogon.

Double-click the DontDisplayLastUser key, change the value to '0' and click OK.

Select Registry/Exit to exit the Windows Registry Editor.

Restart Windows.

You also have to enable automatic login for the client in the Terminal Server Configuration.� Open the Terminal Server Configuration, open the connection's properties, select the Logon Settings tab and disable 'Always prompt for password'.

Caveats

Although it is possible to base all if an installation's FOH terminals on Terminal Server technology, Aloha Technologies does not recommend this configuration since it nullifies the Aloha application software's built-in fault tolerance functionality (refer to document AKBID1107).� Thin-clients are not configured as master-capable or server-capable, so in the event that network connectivity with the master terminal or the file server is lost, the thin-client terminals cannot assume master or file server functionality.

Following installation of the Terminal Server components, you must activate the Terminal Server licenses through Microsoft.� Failure to activate Terminal Server results in client licenses that expire after 90 days.

============================================================================

See also:

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1092 Windows 2000 FOH Terminal Setup

AKBID1093 Windows 2000 File Server Setup

AKBID1097 Aloha Application Software Font Name and Size Variables

AKBID1107 Aloha Application Software Fault Tolerance Functionality

AKBID1119 FOH Adjustable Resolution Settings

AKBID1223 Windows Server 2003 FOH Terminal Setup

AKBID1224 Windows Server 2003 File Server Setup

AKBID3009 CTLSVR.EXE Registry Variables

AKBID3228 Setting a Custom Resolution in Panel Editor

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1203 citrix terminal service terminal services

style='mso-spacerun:yes'>� 2003

�

Default Aloha System Environment Variable Placement

Default Aloha System Environment Variable Placement

============================================================================

AKBID1204

Created: 8 November 2001

Updated: 10 April 2003

Reviewed: 16 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 5.0x � 5.3.x

Subject: Default Aloha System Environment Variable Placement by OS and Configuration

============================================================================

Summary

The location or method in which the ALOHA^� application software declares system environment variables varies with the version of the Microsoft^� Windows^� operating system (OS) that is installed and the PC's intended usage (file server, terminal or a file server/terminal).� This document explains the default methods used by the Aloha Installation CD to declare system environment variables for each configuration.

The information in this document reflects the default system environment variable configurations created by the Back-of-House (BOH) installation application (SETUPPOS.EXE) and the Front-of-House (FOH) installation application (\TERMINST\SETUPTRM.EXE) on the Aloha Installation CD for versions 5.0x and higher.� Custom configurations can differ significantly from the information in this document.

Information

File Server System Environment Variables

If you are using Windows 95 or Windows 98, SETUPPOS.EXE configures all of the environment variables in the C:\IBERCFG.BAT, which is called from the C:\AUTOEXEC.BAT.

If you are using Windows Millennium Edition (Me), SETUPPOS.EXE configures all of the environment variables in the C:\AUTOEXEC.BAT.� This differs from Windows 95 and Windows 98 because Windows Me only supports system environment variable declaration in the AUTOEXEC.BAT, so Windows Me does not support the 'CALL C:\IBERCFG.BAT' line used in the Windows 95 and Windows 98 AUTOEXEC.BAT.

If you are using Windows NT^�, Windows 2000, Windows XP, or Windows Server 2003, SETUPPOS.EXE configures all of the system environment variables in the System Environment Variables Control Panel.

Terminal System Environment Variables

Refer to document AKBID1118 for more information on configuring system environment variables on FOH terminals in a SuperSite.

If you are using Windows 95/98, SETUPTRM.EXE configures the C:\IBERCFG.BAT, which is called from the C:\AUTOEXEC.BAT, to declare the environment variables and update the BIN folder (from the NEWBIN folder).

If you are using Windows Me/NT/2000/XP/2003, SETUPTRM.EXE configures the IBERCFG.BAT located in the Aloha application software folder (for example, D:\ALOHA\IBERCFG.BAT), which is subsequently called from a shortcut in the Windows StartUp folder, to declare the environment variables and update the BIN folder.� Besides declaring the system environment variables and updating the BIN folder, the IBERCFG.BAT also initializes IBER.EXE or IBERQS.EXE.� This configuration enables users to view or edit environment variables over the network from the file server.

File Server/Terminal System Environment Variables

If you are using Windows 95/98, SETUPPOS.EXE configures all of the environment variables in the C:\IBERCFG.BAT, which is called from the C:\AUTOEXEC.BAT.

If you are using Windows Me, SETUPPOS.EXE configures all of the environment variables in the C:\AUTOEXEC.BAT.�

If you are using Windows NT/2000/XP/2003, SETUPPOS.EXE configures all of the system environment variables in the System Environment Variables Control Panel.

Extended Information

CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) environment variables are also declared in their respective command lines in the Windows registry.� Refer to documents AKBID3009 and AKBID3010 for more information.

Caveats

The information in this document reflects the default system environment variable configurations created by the BOH installation application (SETUPPOS.EXE) and the FOH installation application (\TERMINST\SETUPTRM.EXE) on the Aloha Installation CD for versions 5.0x and higher.� Custom configurations can differ significantly from the information in this document.

============================================================================

See also:

AKBID1010 Aloha Application Software System Environment Variables

AKBID1118 SuperSite IBERCFG.BAT

AKBID3009 CTLSVR.EXE Registry Variables

AKBID3010 EDCSVR.EXE Registry Variables

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1204 set

�

Configuring Subway WISR and Control Reports

Configuring Subway WISR and Control Reports

============================================================================

AKBID1205

Created: 13 December 2001

Updated: 13 December 2001

Reviewed: 26 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService

Aloha POS Versions: 5.010 � 5.3.x

Subject: Configuring Subway WISR and Control Reports in the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software enables you to view and print the Subway Weekly Inventory Sales report (WISR) and the Subway Control report using Subrpt.exe.� This document explains how to configure Subrpt.exe to run these reports.

Information

Your database configuration must conform to Subway's standards to ensure accurate reporting.

Subrpt.exe

Subrpt.exe is included with the Aloha Installation CD in the \Misc\Subway folder.� You need to manually copy Subrpt.exe to the Aloha application software Bin folder on the file server.

Subrpt.exe is a separate module and it is not part of the standard Aloha application software report package, so you have to create standard Microsoft^� Windows^� shortcuts to Subrpt.exe, or add shortcuts to the Aloha Manager Navigation Bar as a User Tool in order to view or print reports.� Refer to the Aloha QuickService User Manual for more information on adding shortcuts to the Aloha Manager Navigation Bar.� You can configure the shortcuts to call the WISR report or the Control report.

WISR Report

WISR report contains inventory, sales, royalty and F.A.F. calculations, and several other Subway-specific calculations and fields.

The WISR report uses the /RSW command line argument for the basic report and the /RSW /SETTINGS command line arguments for additional configuration options.� For example:

%IBERDIR%\Bin\Subrpt.exe /RSW

%IBERDIR%\Bin\Subrpt.exe /RSW /SETTINGS

Control Report

Control report contains weekly sales, quick count, coupon, non-sales category, void and inventory information.

The Control report uses the /RSC command line argument for the basic report and the /RSC /SETTINGS command line arguments for additional configuration options.� For example:

%IBERDIR%\Bin\Subrpt.exe /RSC

%IBERDIR%\Bin\Subrpt.exe /RSC /SETTINGS

Extended Information

No information.

Caveats

Your database configuration must conform to Subway's standards to ensure accurate reporting.

============================================================================

See also:

Aloha QuickService User Manual

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1205 wiser

�

Printing Foreign Characters

Printing Foreign Characters

============================================================================

AKBID1206

Created: 12 February 2002

Updated: 10 November 2003

Reviewed: 23 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

Subject: Configuring the Aloha Application Software to Print Foreign Characters

============================================================================

Summary

You can configure the ALOHA^� application software to support and print foreign characters.� This document explains what characters are supported and how to configure the Aloha application software for their support.

Information

European Characters

The Aloha application software provides support for the following characters:

Character

Keystroke

�

Alt+0228

�

Alt+0196

�

Alt+0235

�

Alt+0203

�

Alt+0239

�

Alt+0207

�

Alt+0246

�

Alt+0214

�

Alt+0252

�

Alt+0220

�

Alt+0255

�

Alt+0167

The Aloha application software supports these characters for Epson printers in versions 5.0x and higher providing the printer model supports the 858 code page.� Contact Epson to verify if your printer supports the 858 code page and if any steps are required to enable it.� You must configure the Aloha application software to use the 858 code page in the printer configuration settings in Aloha Manager.

Aloha application software versions 5.2x and higher also support these characters with Star^� Micronics printers.

If you are unable to print the � character, ensure that the SKIPMAPSTAR variable in the ALOHA.INI is set to FALSE (SKIPMAPSTAR=FALSE).

Chinese Characters

The Aloha application software supports Chinese characters providing the printer firmware supports Chinese characters.� Contact the printer manufacturer to verify compatibility.

In order to print Chinese characters from the Aloha application software, you must set the SKIPMAPSTAR variable in the ALOHA.INI to TRUE (for example, SKIPMAPSTAR=TRUE).

If you are not using a Chinese version of Microsoft^� Windows^�, you can consider using NJStar Communicator from NJStar Software (http://www.njstar.com) to assist you with generating Chinese text.� As you type into Aloha Manager, NJStar will display the Chinese characters (if any are associated with the keys) along the bottom of the screen.� You can select the appropriate character and NJStar will insert that character into Aloha Manager.

The NJStar software outputs a variety of character codes.� Ensure that you select character codes that are supported by your printer's firmware.

The Aloha application software supports 15 characters in an item's Chit Name field, but since Unicode requires two bytes per character, you are limited to seven Unicode (and thus Chinese) characters.� Exceeding seven charters might result in unreadable text.

Extended Information

No information.

Caveats

If you are unable to print the � character, ensure that the SKIPMAPSTAR variable in the ALOHA.INI is set to FALSE (SKIPMAPSTAR=FALSE).

The NJStar software outputs a variety of character codes.� Ensure that you select character codes that are supported by your printer's firmware.

The Aloha application software supports 15 characters in an item's Chit Name field, but since Unicode requires two bytes per character, you are limited to seven Unicode (and thus Chinese) characters.� Exceeding seven charters might result in unreadable text.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1206 chits kitchen

�

Configuring and Using CHKINFO.EXE

Configuring and Using CHKINFO.EXE

============================================================================

AKBID1207

Created: 16 April 2002

Updated: 12 June 2003

Reviewed: 15 December 2003

Microsoft^� Windows^� Versions: All��

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.4x � 5.3.x

Subject: Configuring and Using CHKINFO.EXE to Append Customer Information to Transactions

============================================================================

Summary

CHKINFO.EXE is an external application that enables ALOHA^� application software users to associate additional customer information to guest checks, such as zip codes, customer ID numbers, and so on.� This document explains how to configure, enable and use CHKINFO.EXE with the Aloha application software.

Information

CHKINFO.EXE communicates with the Aloha application software via TOFOH.TXN messages that are incorporated into the TRANS.LOG (transaction log).� Using a version of CHKINFO.EXE that is incompatible with the working version of IBER.EXE or IBERQS.EXE (for example, using a 4.4x version of CHKINFO.EXE with a 5.2x version of IBER.EXE) may hinder functionality and cause corruption in the transaction log.

TableService

Configure CHKINFO.EXE in TableService using the RUNPROGRAMCLOSE and RUNPROGRAMCLOSETEXT variables in the ALOHA.INI.�

Assign the command line (including the path) for CHKINFO.EXE to the RUNPROGRAMCLOSE variable (for example, RUNPROGRAMCLOSE=D:\ALOHA\BIN\CHKINFO.EXE).� CHKINFO.EXE's default prompt is 'Card Number', but you can change this by including the /PROMPT variable in the CHKINFO.EXE command line (for example, use RUNPROGRAMCLOSE=D:\ALOHA\BIN\CHKINFO.EXE /PROMPT "Zip Code" to display 'Zip Code' as the prompt).

Besides the user-configurable PROMPT variable, IBER.EXE also appends the following variables to the command line (the values are automatically assigned by IBER.EXE):

Variable

Description

/EMPNUMBER

Employee ID

/QUEUEID

Queue ID

/TABLEID

Unique table ID

/CHECKID

Unique check ID

/IBERDIR

Path to Aloha application software folder on the master terminal

IBER.EXE displays a 'Run Program' button on the Close Check screen if there is a value assigned to the RUNPROGRAMCLOSE variable.� Pressing this button initializes CHKINFO.EXE.� You can customize the button's text using the RUNPROGRAMCLOSETEXT variable (for example, RUNPROGRAMCLOSETEXT=Zip\nCode).

Information gathered by CHKINFO.EXE is captured in the transaction log and included in the GCHKINFO.DBF files created by the Grind process (refer to document AKBID1016).

QuickService 4.4x � 5.0x

Configure CHKINFO.EXE on a button in Panel Editor via the Run Application button function.�

Assign the command line (including the path) for CHKINFO.EXE to the Run Application function (for example, D:\ALOHAQS\BIN\CHKINFO.EXE).� CHKINFO.EXE's default prompt is 'Card Number', but you can change this by including the /PROMPT variable in the CHKINFO.EXE command line (for example, use D:\ALOHAQS\BIN\CHKINFO.EXE /PROMPT "Zip Code" to display 'Zip Code' as the prompt).

You must enable the 'Pass Parameters' option in the Run Application button configuration to enable the following command line variables (the values are automatically assigned by IBERQS.EXE):

Variable

Description

/EMPNUMBER

Employee ID

/QUEUEID

Queue ID

/TABLEID

Unique table ID

/CHECKID

Unique check ID

/IBERDIR

Path to Aloha application software folder on the master terminal

Information gathered by CHKINFO.EXE is captured in the transaction log and included in the GCHKINFO.DBF files created by the Grind process (refer to document AKBID1016).

QuickService 5.2x and Higher

Configure Check Information on a button in Panel Editor via the Check Info button function.� Create a new button, assign the Check Info function to it and enter the user prompt in the Prompt textbox (the default prompt is 'Card Number' if you fail to enter a custom prompt).

Information gathered by this process is captured in the transaction log and included in the GCHKINFO.DBF files created by the Grind process (refer to document AKBID1016).

Extended Information

GCHKINFO.DBF contains the following fields:

Field

Description

UNIT

Store ID

DOB

Date-of-Business

EMPLOYEE

Employee ID

QUEUEID

Queue ID

TABLEID

Unique table ID

CHECKID

Unique check ID in versions 5.2.7.82 and lower; check number in versions 5.2.7.83 and higher.

ATTNAME

Prompt text

ATTTEXT

Text entered by user

FKTABID

Table number ('0' if it a tab name is used)

TABNAME

Tab name (if this was a table number, uses 'Table nn', where nn is the table number)

Caveats

CHKINFO.EXE communicates with the Aloha application software via TOFOH.TXN messages that are incorporated into the transaction log.� Using a version of CHKINFO.EXE that is incompatible with the working version of IBER.EXE or IBERQS.EXE (for example, using a 4.4x version of CHKINFO.EXE with a 5.2x version of IBER.EXE) may hinder functionality and cause corruption in the transaction log.

============================================================================

See also:

AKBID1016 Grind Process and Errors

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1207 checkinfo.exe

style='mso-spacerun:yes'>� 2003

�

Configuring Fiscal Manager and Fiscal Printers in Aloha

Configuring Fiscal Manager and Fiscal Printers in Aloha

============================================================================

AKBID1208

Created: 25 April 2002

Updated: 8 July 2002

Reviewed: 5 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2.4.0 � 5.3.x

Subject: Configuring Fiscal Manager and Fiscal Printers in the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software supports fiscal printers using FISCALMGR.EXE (Fiscal Manager), which communicates with the Aloha application software Front-of-House (FOH) using XML and TCP sockets.� This document explains how to install and configure Fiscal Manager on an Aloha application software file server, terminal or stand-alone print server.

Information

Basic Fiscal Manager Communication

Fiscal Manager acts as a bridge between the Aloha application software and the fiscal printer.� All print requests (receipts, reports, and chits) are routed to the printer via Fiscal Manager rather than going directly to the printer from the FOH.

When the FOH sends print requests or fiscal data to the printer, it does so by sending XML data over a TCP/IP connection to Fiscal Manager.� Fiscal Manager processes the data and sends it to the printer via a printer-specific .DLL file.� The .DLL file then communicates directly with the printer.

Since the Aloha application software is required to send the entire print job to the fiscal printer before the printer will process and print the information, some print requests may print out of order.� For example, if you print a sales report and then print a receipt, the receipt may print before the sales report since the sales report takes longer to process.� All fiscal data gets priority, though.

Each type of printer has a .DLL made specifically for that type of printer and must be supplied by the user.� If a .DLL for the type of printer you are using is not already available to you, contact Aloha Technologies for more information on creating your own .DLL for the type of printer that you are using.

Fiscal Manager Installation and Configuration

You must install Fiscal Manager on any computer to which a fiscal printer is connected.� Fiscal Manager installation is the same for all configurations, regardless if it is on the file server, FOH terminal, or on a separate print server.� To install Fiscal Manager, run SETUPFPM.EXE from the FISCALMGR folder on the Aloha Installation CD.

SETUPFPM.EXE performs the following basic actions:

-          Creates an Aloha application software folder (if one does not already exist)

-          Creates a BIN folder inside of the Aloha application software folder (if one does not already exist)

-          Places FISCALMGR.EXE and any printer .DLL files in the BIN folder

-          Creates a DATA folder inside of the Aloha application software folder (if one does not already exist)

-          Creates a FPDLLS.DAT file in the DATA folder to store the printer .DLL information

-          Creates a FISCAL folder (if one does not already exist)

-          Creates a FPMGR.INI file in the FISCAL folder to store Fiscal Manager configuration settings

-          Creates a batch file in the FISCAL folder that launches FISCALMGR.EXE (a shortcut to the batch file is also added to the Microsoft^� Windows^� StartUp folder since Fiscal Manager must be running at all times in order for users to close check or print receipts, reports or chits)

-          Creates a TMP folder (if one does not already exist)

Once you have installed Fiscal Manager, you need to configure the fiscal printer type, printer communications port, and TCP socket port in Fiscal Manager.� Start Fiscal Manager using the batch file created in the FISCAL folder and configure the printer type, printer communications port, and TCP socket port.� You can usually select 3454 for the TCP socket port, but refer to document AKBID3187 for more information on selecting an open TCP socket port using NETINFO.EXE.

If your printer type is not listed in the printer drop-down list, then you must supply a printer .DLL for your type of printer.� Once you have the .DLL, place it in the Aloha application software BIN folder, edit FPDLLS.DAT in the DATA folder, and add the printer to FPDLLS.DAT.� FPDLLS.DAT is a text file that uses a <DLL NAME>,<DLL FILE> format, where <DLL NAME> is the printer name displayed in Fiscal Manager's printer type drop-down list and <DLL FILE> is the printer's .DLL file name.� For example, if you have a .DLL file for an Epson TM-U200 labeled TMU200.DLL, then add the following line to FPDLLS.DAT:

Epson TM-U200,TMU200.DLL

Once you have added your printer to FPDLLS.DAT, restart Fiscal Manager and select your printer from the drop-down list.

Since the Aloha application software FOH synchronizes the DATA folder with the file server, ensure that any edited versions of FPDLLS.DAT on FOH terminals are not overwritten by older versions on the file server by keeping a copy of the most up to date version of FPDLLS.DAT on the file server.

Configuring Fiscal Printers in Aloha Manager

You must configure the fiscal printer and Fiscal Manager in Aloha Manager in printer maintenance and terminal maintenance.

Define the printer in printer maintenance (Maintenance/Hardware/Printers) and configure it as a fiscal printer.� Select Fiscal Manager as the printer type since the actual printer type is configured in Fiscal Manager instead of Aloha Manager.� Also select the TCP socket port (the same port as you configured previously in Fiscal Manager) and the TCP/IP address of the computer on which Fiscal Manager resides.

Configure Fiscal Manager in terminal maintenance (Maintenance/Hardware/Terminals/Other) by assigning the TCP socket port and TCP/IP address.

Configure any printer routing as you would for a standard printer and refresh the system.

Fiscal Manager Usage Notes

Fiscal Manager logs debugging information in DEBOUT.FPM, located in the Aloha application software TMP folder.

The Aloha application software is only responsible for transporting the fiscal data and printer requests to the printer's .DLL file.� It is up to the printer .DLL file to communicate directly with the printer.

FISCALDEBUG.DLL is a mock printer .DLL that outputs fiscal and print data to the screen for testing and troubleshooting.

Fiscal printers have hard-coded tax settings.� You must configure your tax ID numbers in the Aloha application software to match the tax ID numbers configured in the fiscal printer.

�

In order to handle taxes correctly, some comps and promotions might not display in the fiscal data as they appear on the screen, although the totals will be correct.

Extended Information

If you are configuring a separate print server for fiscal printers, configure the computer as you would any standard network computer, enable TCP/IP networking, and assign a valid TCP/IP address.� The computer name does not matter to the Aloha application software and file sharing is not required since all communication is performed via TCP sockets.

Caveats

Since the Aloha application software is required to send the entire print job to the fiscal printer before the printer will process and print the information, some print requests may print out of order.� For example, if you print a sales report and then print a receipt, the receipt may print before the sales report since the sales report takes longer to process.� All fiscal data gets priority, though.

Since the Aloha application software FOH synchronizes the DATA folder with the file server, ensure that any edited versions of FPDLLS.DAT on FOH terminals are not overwritten by older versions on the file server by keeping a copy of the most up to date version of FPDLLS.DAT on the file server.

============================================================================

See also:

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID3187 Selecting an Open TCP Port for AlohaSpy and Fiscal Manager

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1208

�

Configuring the Aloha Application Software VizorVest Interface

Configuring the Aloha Application Software VizorVest Interface

============================================================================

AKBID1209

Created: 7 May 2002

Updated: 25 July 2002

Reviewed: 11 February 2004

Microsoft Windows Versions: All

Aloha Products: TableService

Aloha POS Versions: 5.2.4.0 � 5.3.x

Subject: Configuring the Aloha Application Software VizorVest Interface

============================================================================

Summary

The ALOHA^� application software supports the VizorVest^SM investment program for tipped restaurant employees.� This document explains how to install and configure the VizorVest software, how to configure the Aloha application software for use with the VizorVest software, and the processes the Aloha application software uses to report income to the VizorVest software.

Information

Install VizorVest Software

Install the VizorVest software on the Aloha application software file server using the installation application provided with the VizorVest software.� You must install the Aloha application software software prior to installing the VizorVest software since the VizorVest software detects the Aloha application software and uses an Aloha-specific installation routine.

Do not install the VizorVest software without first installing the Aloha application software software.

Refer to the VizorVest user manual for more information regarding the VizorVest installation and configuration procedures.

Configure the Aloha Application Software

The VizorVest options are enabled in the Aloha application software only if the HASP^� security key enables them.� You must have a HASP key with VizorVest option enabled in order to use the VizorVest program with the Aloha application software.

Any employee participating in the VizorVest program must have a unique social security number assigned to them in Employee maintenance and clock-in with a job code that has both 'Order Entry' and 'Participates in Vizor' enabled.

All employees participating in the VizorVest program must have unique social security number.

You must configure Winhook to process employee information and send the polling files to the Vizor Group^SM each night following the End-of-Day (EOD) process.� Configure a Winhook batch file using the information in document AKBID1028 and add the following command lines to process employee information and initiate the VizorVest polling process:

%IBERDIR%\VIZOR\VIZORPOS.EXE EOD

%IBERDIR%\VIZOR\VZ_POLL.EXE

If you are using the modem normally used by the Aloha application software Electronic Data Capture (EDC) application, you must temporarily disable the EDC software prior to initializing the VizorVest polling process.� Refer to document AKBID1167 for more information on temporarily disabling EDC.

Usage and Processes

The Aloha application software uses %IBERDIR%\VIZOR\VIZORPOS.EXE on the file server for all Front-of-House (FOH) interaction with the VizorVest software.� The following process applies to the Aloha application software VizorVest interface:

If an employee with a job code capable of participating in the VizorVest program clocks-in, then IBER.EXE runs VIZORPOS.EXE with the employee information as parameters.

If the employee has not signed up for the VizorVest program, then VIZORPOS.EXE prompts them to sign up.� If the employee is already part of the VizorVest program, then VIZORPOS.EXE does not prompt the employee.

When the employee performs their checkout, IBER.EXE uses %IBERDIR%\VIZOR\VIZORPOS.TXT to determine if the employee is participating in the VizorVest program and uses %IBERDIR%\VIZOR\VIZORPOS.INI to determine if the employee has met the minimum VizorVest contribution amount.� If the employee is participating in the VizorVest program and has met the minimum contribution amount, IBER.EXE creates a transaction.� IBER.EXE informs the employee whether or not they have made a contribution from the shift.

Following the EOD process, the grind process creates a .TRN export file in the folder designated by the PATH variable in the VIZORPOS.INI.� The .TRN file uses the format ccccsssssmmdd.TRN, where cccc is the company ID (with leading zeros), sssss is the store ID (with leading zeros), mm is the month and dd is the day..

Winhook processes the employee information and initializes the polling process that sends the data to the Vizor Group.

If the employee does not perform a checkout and their checkout is subsequently performed by the EOD process, then their contribution is not recorded for processing by the VizorVest software, nor is it deducted in Aloha application software reports.

If the employee is contributing a percentage of their earning towards the VizorVest program, the calculations are based on the employee's tippable sales.� Refer to document AKBID3134 for more information on tippable sales calculations.

If you experience problems with any of these processes, refer to the Debugging-Output (debout) files for more information.� The Aloha application software records many of the problems and exceptions to the debout files.

VizorVest contribution information is reported in BOH Weekly and Daily Sales Summaries, BOH Labor Report, FOH Restaurant Sales Report, FOH checkout reports, and clock-out chits.

File Server/Terminals

If you have a multi-terminal system where the file server acts as both a file server and a FOH terminal and the file server/terminal is using the Microsoft^� Windows^� 95, Windows 98. or Windows Millennium Edition (Me) operating system, you must disable server-capability on all of the FOH terminals (with the exception of the file server/terminal) in order to use the VizorVest interface.� Failure to do so can result in another FOH terminal assuming the role of file server and inhibiting the FOH from accessing the VizorVest applications and configuration files.

If you have a multi-terminal system where the file server acts as both a file server and a FOH terminal and the file server/terminal is using the Windows NT^�, Windows 2000, or Windows XP operating system, you must ensure that CTLSVR.EXE (Control Server) is not registered with the /NONET command line variable in the Windows Registry.� Refer to document AKBID3009 for more information on editing or viewing Control Server command-line variables in the Windows Registry.

Fault Tolerance Restrictions

If the FOH is not connected with the file server and has assigned a FOH terminal as a temporary file server, the FOH cannot initialize VIZORPOS.EXE.� This means that new employees are not prompted to sign up for VizorVest program.

Since the VizorVest contribution is recorded by the Aloha application software when the employee performs a checkout, the FOH must be connected to the file server when the employee performs a checkout, otherwise the contribution is not recorded for processing by the VizorVest software, nor is it deducted in Aloha application software reports.� As long as the FOH is connected to the file server at the time of checkout, the VizorVest contribution will be recorded and processed, even if the FOH is not connected to the file server when the employee clocked-in (assuming the employee has previously signed up for the VizorVest program) or if the FOH is not connected to the file server during the EOD process.�

In the event that the FOH terminal is not connected to the file server during the EOD process, the VizorVest contributions are reported to the VizorVest software when the dated folder is transferred from the FOH terminal (that temporarily acted as the file server) to the Back-Of-House (BOH) file server and the grind process has completed.

Extended Information

No information.

Caveats

Do not install the VizorVest software without first installing the Aloha application software software.

All employees participating in the VizorVest program must have unique social security number.

If the employee does not perform a checkout and their checkout is subsequently performed by the EOD process, then their contribution is not recorded for processing by the VizorVest software, nor is it deducted in Aloha application software reports.

============================================================================

See also:

AKBID1028 Winhook

AKBID1167 Temporarily Disabling EDC for Modem Availability

AKBID3009 CTLSVR.EXE Registry Variables

AKBID3134 Tippable Sales Calculations

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1209 vest

Converting an Existing .DBF Site to a Relational Database

Converting an Existing .DBF Site to a Relational Database

============================================================================

AKBID1210

Created: 24 September 2002

Updated: 20 November 2002

Reviewed: 11 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x

Subject: Converting an Existing Site with DBF Database Site to a Relational Database ============================================================================

Summary

The ALOHA^� application software supports both .DBF-based databases and Relational Databases (RDB).� This document explains how to convert an existing site that is using a .DBF-based database to a RDB.

Information

The conversion method depends on the type of RBD to which you are converting.

Converting to SQL Server

If you converting a site to a Microsoft SQL Server database, then you must first ensure that your hard drive configuration supports the use of an RDB.� Document AKBID1183 explains recommended hard drive configurations for an RDB, but if you are using an existing system that uses a configuration different than what is described in the document, then you must use the provided information to evaluate your current configuration in order to determine if you can use it with an RDB.

After you have configured your hard drive, install SQL Server using the appropriate document for your version of SQL Server, and reinstall the Aloha application software using the Aloha Installation CD according to the appropriate document for your version of SQL Server (ensure that you select the correct database type).� The installation process will not overwrite the current data, but instead, it will upgrade it (if needed) and create a new RDB based on the data.

Once you have reinstalled the Aloha application software and created the RDB, you must regrind your dated folders in order to populate the RDB with the historical information.� Refer to document AKBID1016 for more information on regrinding dated folders.

Converting to MSDE

If you converting a site to Microsoft Database Engine (MSDE) database, then you must first ensure that your hard drive configuration supports the use of an RDB.� Document AKBID1183 explains recommended hard drive configurations for an RDB, but if you are using an existing system that uses a configuration different than what is described in the document, then you must use the provided information to evaluate your current configuration in order to determine if you can use it with an RDB.

After you have configured your hard drive, install MSDE using the information in document AKBID1218, and reinstall the Aloha application software using the Aloha Installation CD according to the information in document AKBID1218 (ensure that you select the correct database type).� The installation process will not overwrite the current data, but instead, it will upgrade it (if needed) and create a new RDB based on the data.

Once you have reinstalled the Aloha application software and created the RDB, you must regrind your dated folders in order to populate the RDB with the historical information.� Refer to document AKBID1016 for more information on regrinding dated folders.

Converting to Access

The Aloha application software only supports Microsoft Access 97, so if you plan to view or manipulate the database outside of the Aloha application software, then you must use Access 97.� If you open the database in a newer version of Access, then it can upgrade the database, making it incompatible with the Aloha application software.� For this reason, Aloha Technologies recommends using and MSDE database in place of an Access database, and this document does not cover the conversion process for an Access database.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

AKBID1016 Grind Process and Errors

AKBID1110 Installing Microsoft SQL 7.0

AKBID1183 Recommend Hard Drive Partitions, File Systems, and Setup

AKBID1202 Installing Microsoft SQL Server 2000

AKBID1218 Using MSDE with the Aloha Application Software

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1210 change changing migrate migrating

�

Common Microsoft Error Return Codes

Common Microsoft Error Return Codes

============================================================================

AKBID1211

Created: 28 June 2002

Updated: 28 August 2003

Reviewed: 8 March 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

Subject: Common Microsoft Error Return Codes Reported by the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software reports some erroneous behavior by logging error codes returned by Microsoft^� Windows^�.� This document lists the more common error codes encountered by Aloha application software users.

Information

Error Code

Explanation

0, 00, 0L

No error, successful

2, 02, 2L

File not found

3, 03, 3L

Path not found

5, 05, 5L

Access denied

8, 08, 8L

Not enough memory

13, 13L

Invalid data

22, 22L

Bad command

32, 32L

Sharing violation

53, 53L

Bad network path

55, 55L

Network resource or device is no longer available

64, 64L

The specified network name is no longer available.

67, 67L

Network name cannot be found

71, 71L

Remote computer has too many connections and is not accepting any more

121, 121L

The semaphore timeout period has expired.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1211 errno extended_error_code last returned returns

Aloha Application Software Version Numbering Scheme

Aloha Application Software Version Numbering Scheme

============================================================================

AKBID1212

Created: 2 July 2002

Updated: 8 December 2003

Reviewed: 8 December 2003

Microsoft^� Windows^� Versions:

Aloha Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 5.2.4.x � x.x.x.x

Subject: Aloha Application Software Version Numbering Scheme

============================================================================

Summary

Aloha Technologies, Ltd. currently uses a version numbering scheme for the ALOHA^� application software that differs from the previous scheme.� This document explains the current version numbering scheme and how it applies to future products.

Information

The Aloha application software version-numbering scheme uses the format p.m.e.b (for example, 5.2.4.24).

p represents the Product number.� This only changes when Aloha Technologies introduces an entirely new product.� A previous example was the change from version 4.4 to 5.0.

m represents the Major Enhancement number.� This only changes when Aloha Technologies adds major enhancements to the product.� Previous examples of this are the change from version 4.0 to 4.2 and version 5.0 to 5.2.

e represents the Minor Enhancement version.� This changes each time Aloha Technologies releases a product with new minor enhancements.� Previous examples of this were 5.2 Rev A, 5.2 Rev B and so on.� With the new version numbering scheme, the terms 'Rev' or 'Revision' are no longer used to describe Aloha versions.

b represents the Build number.� This changes each time Aloha Technologies creates a new software build.� Previous examples of this were the change from version 5.007 to 5.008 or version 5.234 to 5.235.� The Aloha application software suppresses the build number from the user interface in versions 5.3.1.x and higher.� You can still view the build number in the Debugging-Output-Files (debouts) and in the file properties.

Using 5.2.4.24 as an example, subsequent builds with minor 'bug' fixes will be 5.2.4.25, 5.2.4.26, 5.2.4.27 and so on.

The next minor enhancement release (previously known as a 'Rev') will be 5.2.5.0, although the build number will have increased by the time it is released to the public (for example, 5.2.5.15).

The next major enhancement release will be 5.3.1.� Subsequent minor enhancement versions will be 5.3.2, 5.3.3, and so on.

Previous version numbering schemes reserved odd-numbered versions of major enhancements for development purposes.� This method is no longer used.

The next product release will be 6.0.0.� Subsequent major enhancement versions will be 6.1.x, 6.2.x and so on.� Subsequent minor enhancement versions will be 6.1.x, 6.1.x and so on.

Aladdin^� Hardware-Against-Software-Piracy (HASP^�) security key activation codes are issued to run applications for all versions within the Major Enhancement number (and lower). For example, if you are licensed for version 5.2, you can run any version of 5.2.x.x, including all versions below (such as version 5.0x or 4.2x).

BackOffice Applications

The version number for each BackOffice application is in the format p.me (for example, 1.13).

p represents the Product number.� This only changes when Aloha Technologies introduces an entirely new product within a given application line.� A previous example was the change from Aloha Delivery/Frequent Buyer version 4.xx to version 5.xx.

m represents the Major Enhancement number.� This only changes when Aloha Technologies adds major enhancements to the product.� A previous example was the change from Aloha Inventory Control 1.0x to 1.1x.

e represents the Minor Enhancement version.� This changes each time Aloha Technologies releases a product with new minor enhancements.� A previous example was the change from Aloha Inventory Control 1.12 to 1.13.

The BackOffice application version might also include a Service Pack suffix in the form (SPx), where x is a single digit number starting with one and incrementing by one for each service pack release for a given p.me version. Service Pack releases are introduced to correct defects and do not typically introduce enhancements.

HASP security key activation codes are issued to run BackOffice applications for all versions within the Major Enhancement number (and lower). For example, if you are licensed for Aloha Inventory Control version 1.1, you can run any version up to and including version 1.19 (at any service pack level), including all versions below 1.10 (such as version 1.02).

Extended Information

In rare cases, the Aloha application software version-numbering scheme may take on the format p.m.e.b.r, where r is a revision number.

Version labels might also include text following the version number that represents a special purpose, such as Pre-alpha, Alpha, Beta, or a customer name.

You must update your HASP^� key activation codes if you upgrade to a version of the Aloha application software with a newer Product or Major Enhancement number.� New key activation codes are not required for upgrades to versions with newer Minor Enhancement or Build numbers.

Caveats

No information.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1212 new numbers

style='mso-spacerun:yes'>� 2003

�

Using EDC Linger Time to Decrease Authorization Time

Using EDC Linger Time to Decrease Authorization Time

============================================================================

AKBID1213

Created: 27 August 2002

Updated: 29 August 2002

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 4.2x � 5.3.x

Subject: Using EDC Linger Time to Decrease Authorization Time by Lingering on the Phone

============================================================================

Summary

The ALOHA^� application software Electronic-Draft-Capture (EDC) application support 'Linger Time' functionality, which forces EDC to not immediately disconnect from the credit card processor following a credit card transaction.� Since EDC is already connected to the credit card processor, the next transaction will not have to reconnect to the processor, which decreases the authorization time.� This document explains how to configure linger time in EDC.

Because of the limited use of this feature, it has not been thoroughly tested by Aloha Technologies with each processor.� You should test this feature with your processor prior to introducing it to a live site.� It is possible that linger time may not function properly with all processors.

Information

Prior to enabling linger time in EDC, you must first verify that your credit card processor supports this functionality and that they support 'multitrans' functionality, which enables EDC to perform multiple transactions within the same call to the credit card processor.

Enabling linger time or multitrans without your credit card processor authorizing or supporting its use can lead to authorization failures.� Do not enable linger time without specific authorization from your credit card processor.

To enable linger time, first configure your credit card processor in EDC to enable multitrans for each processor that will use linger time.

After you have enabled multitrans, edit the EDC.INI, and add the LINGERTIME variable to each processor's section.� Assign the variable a value representing the number of seconds to linger on the phone line.� For example:

[Visanet]

LINGERTIME=30

Restart EDC.EXE and EDC Server.

Once linger time is enabled, EDC will linger on the phone line for the amount of time specified in the EDC.INI or until the processor disconnects the phone connection.� If EDC receives a new transaction request while lingering on the phone liner, the linger time timeout is reset.

Extended Information

No information.

Caveats

Because of the limited use of this feature, it has not been thoroughly tested by Aloha Technologies with each processor.� You should test this feature with your processor prior to introducing it to a live site.� It is possible that linger time may not function properly with all processors.

Enabling linger time or multitrans without your credit card processor authorizing or supporting its use can lead to authorization failures.� Do not enable linger time without specific authorization from your credit card processor.

============================================================================

See also:

Aloha Credit Card User Manual

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1213 wait

�

Using COMPVER.TXT to Verify Names Applied to Comps

Using COMPVER.TXT to Verify Names Applied to Comps

============================================================================

AKBID1214

Created: 29 August 2002

Updated: 5 September 2002

Reviewed: 10 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService

Aloha POS Versions: 4.0x � 5.3.x

Subject: Using COMPVER.TXT to Verify Names Applied to Comps

============================================================================

Summary

You can configure COMPVER.TXT to force the ALOHA^� application software Front-of-House (FOH) to verify names applied to comps.� If you enter an employee number that is listed in COMPVER.TXT, then the FOH applies the employee's name and number to the comp name on the check.� If you enter an employee number for the comp's name that is not listed in COMPVER.TXT, the FOH warns you that it is not a valid employee, but you can still apply the comp to the check.� This document explains how to enable and configure COMPVER.TXT in the FOH.

Information

Comp name verification uses COMPVER.TXT in the Aloha application software DATA folder to verify employee names.� COMPVER.TXT is a text file that uses the following fields:

Column

Description

1-10

Employee number, which is verified by the FOH.

11-25

Employee's first name.

26-40

Employee's last name.

41-45

Verify Type (numeric)

The following is an example of a COMPVER.TXT:

123�� Joe�� Smith�� 1

234�� Bill�� Changer�� 1

345�� Mary�� McConnell�� 2

The Verify Type field enables COMPVER.TXT for a particular comp.� The Aloha application software correlates this value with the value listed in Aloha Manager/Maintenance/Payments/Comps/Restrictions/Verify Type.� When you apply a comp to a check, the FOH only looks for employees in COMPVER.TXT with matching verify type values.� The FOH ignores any verify type values that are blank or set to a zero value.

You must enable the 'Must Enter Name' option in comp maintenance for any comp that will verify names with COMPVER.TXT.

Once you apply a comp in the FOH, you must enter the employee number in the name field.� If the FOH finds a matching employee number in COMPVER.TXT (with the same verify type value as the comp), it applies the employee name and number from COMPVER.TXT to the guest check.� If the FOH does not find a matching employee number, then the FOH warns you about this, but it still enables you to apply the comp to the check.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1214

�

Configuring Veridicom Thumbprint Scanners

Configuring Veridicom Thumbprint Scanners

============================================================================

AKBID1215

Created: 3 September 2002

Updated: 16 January 2004

Reviewed: 16 January 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x

Subject: Configuring Veridicom Thumbprint Scanners for the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software supports Veridicom thumbprint scanners for use with clocking into and/or logging into the Front-of-House (FOH).� This document explains the installation and configuration of Veridicom thumbprint scanners for use with the Aloha application software.

Refer to document AKBID1048 for a list of supported Veridicom models.

Information

Device Connections and HASP Key Conflicts

If you are have attached a HASP^� security key to your parallel (LPT) port on your Aloha file server that also functions as a FOH terminal, and you are also connecting an LPT-based Veridicom thumbprint scanner to the file server, then you must configure the system with one of the following configurations in order to avoid conflicts between the thumbprint scanner and the HASP security key:

-          Configure two LPT ports, one port for the HASP security key and one port for the thumbprint scanner.� The Aloha application software will automatically sense which LPT port the HASP security key is attached, although you can use the information in document AKBID1220 to assign the Aloha application software to only check a specific LPT port.

-          Configure a single LPT port for the HASP security key, and configure a Universal-Serial-Bus (USB) port for the thumbprint scanner.� The Aloha application software will automatically sense that a USB thumbprint scanner is attached.� Verify that your operating system supports USB ports.

-          Configure a single LPT port for the thumbprint scanner, and configure a USB port for the HASP security key.� The Aloha application software will automatically sense that an LPT thumbprint scanner is attached, and it will automatically sense that a USB security key is attached.� Verify that your operating system supports USB ports.

You can configure thumbprint scanners on either a LPT port or a USB port on dedicated FOH terminals to which a security key is not attached.

LPT Port Configuration

If you are attaching the thumbprint scanner to a LPT port, configure the port to ECP mode.� If you are using a terminal from POSIFLEX Business Machines, Inc. and experience communication issues, try configuring the port to ETP mode if ETP mode is an option on your particular terminal.

Install the Veridicom Device Drivers and Test Scanner

Install the Veridicom device drivers on each FOH terminal to which the thumbprint scanner is attached by initializing VINSTALL.EXE in the \MISC\VERIDICOM folder on the Aloha Installation CD and completing the installation process.

After you install the Veridicom drivers, you can use the Veridicom applet the in the Microsoft^� Windows^� Control Panel to calibrate and test the thumbprint scanner.� If you cannot communicate with the thumbprint scanner using this utility, then the Aloha application software will not be able to communicate with the thumbprint scanner.

You must be able to test the thumbprint scanner using the Veridicom applet in the Windows Control Panel in order for the Aloha application software to communicate with the thumbprint scanner.

Add Veridicom Interface Files to BIN Folder

Update the Aloha application software BIN folder on the file server with the Veridicom interface files in the \MISC\VERIDICOM\BIN folder on the Aloha Installation CD, and refresh the system to propagate the files to the FOH terminals.

The Aloha application software FOH cannot communicate with the thumbprint scanner without these files in the local Aloha application software BIN folder.

Configure Scanners, FOH Passwords, Employees, Job Codes, and Access Levels

Refer to the Aloha QuickService or TableService User Manual for more information about the subjects covered in this section.

Enable the thumbprint scanner for the each terminal in Aloha Manager/Maintenance/Hardware/Terminals/Readers/Thumb Scanner.

You must also configure your FOH passwords, employees, job codes, and access levels to enable the thumbprint scanners.

Configure your FOH passwords as optional or required in Aloha Manager/Maintenance/Store Settings/Security/POS Password Settings.

Configure any employees that are to use thumbprint scanners by enabling Must Use Thumbprint Scanner for clock-ins and/or log-ins.

Configure any job codes that are to use thumbprint scanners by enabling Uses Password.

Configure any access levels that are to enroll other employee's thumbprints by enabling Enroll Thumbprints.

If you are using QuickService, add a new button to the FOH manager functions, and assign the button to use the Enroll Thumbprints function.

FOH Usage

You must enroll new thumbprints from the FOH.� If you are using TableService, select Manager Functions/Employee/Enroll Thumbprints.� If you are using QuickService, select the Enroll Thumbprints button that you created.

If the Enroll Thumbprints buttons does not function or is not displayed in the TableService Manager Functions, verify that you are logged in with an access level that enables this function, that you have updated the Aloha application software BIN folder with the Veridicom Interface Files, and that the thumbprint scanner is functioning (use the Veridicom applet in the Windows Control Panel).

Once employees are enrolled, they must use the thumbprint scanner to clock in and/or log in to the FOH.

Extended Information

No information.

Caveats

You must be able to test the thumbprint scanner using the Veridicom applet in the Windows Control Panel in order for the Aloha application software to communicate with the thumbprint scanner.

The Aloha application software FOH cannot communicate with the thumbprint scanner without the Veridicom interface files added to the local Aloha application software BIN folder.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1048 Aloha Application Software Hardware and OS Specifications

AKBID3212 Thumbprint Scanner and HASP Key Conflicts

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1215 finger login print reader thumb

�

Enabling and Configuring FOH Enhanced Graphical Interface

Enabling and Configuring FOH Enhanced Graphical Interface

============================================================================

AKBID1216

Created: 3 September 2002

Updated: 2 June 2003

Reviewed: 29 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2.5.x � 5.3.x

Subject: Enabling and Configuring FOH Enhanced Graphical Interface

============================================================================

Summary

The ALOHA^� application software supports the Enhanced Graphical Interface (EGI) that updates the look of the software on the Front-of-House (FOH) terminals using OpenGL technology.� Besides using schemes pre-configured by Aloha Technologies, you can also create new schemes of your own.� This document explains how to enable the EGI in the Aloha application software, and how to configure your own schemes.

Information

The EGI consumes additional system resources, so they might not be compatible with older, less powerful FOH terminals.

While the EGI can function along side Cool Interfaces, the EGI enhancements are not as readily noticeable with Cool Interfaces enabled.� Aloha Technologies recommends using either one or the other, but not both.

Enabling the EGI

In Aloha versions 5.2.7.x and higher, the EGI is enabled by default for any terminal with at least 64 megabytes of memory and 16-bit color.� The EGI is available in versions 5.2.5.x and 5.2.6.x, but they are not enabled by default and Aloha Technologies has not fully tested the EGI in these versions.�

The EGI is not fully tested by Aloha Technologies in versions 5.2.5.x and 5.2.6.x.� If you enable the EGI in these versions, you are using it at your own risk.

If you are using Aloha versions 5.2.7.x and higher, you can control the EGI or override the default settings in Aloha Manager/Store Settings/User Interface/POS.

If you are using versions 5.2.5.x or 5.2.6.x, you can add the following variables to the system environment variables or the ALOHA.INI (if they do not already exist) in order to control the EGI or override the default settings:

Variable

Type

Description

EGI

System Environment Variable

Set to TRUE or FALSE, explicitly enables or disables the interface, overriding the 64 megabytes of memory/16-bit color requirements.� Use this to enable the EGI in Aloha versions 5.2.5.x.

DISABLEEGIPOS

ALOHA.INI

If you set this to TRUE, it forces FOH terminals to not use the EGI.

DISABLEEGIMNT

ALOHA.INI

If you set this to TRUE, it forces ALOHAMGR.EXE (Aloha Manager) to not use the EGI for screen maintenance functions.

EGISCHEME

ALOHA.INI

Enables a specific the EGI scheme from EGI.CFG or EGI2.CFG by the numerical ID.� If it is not defined in EGI.CFG or EGI2.CFG, the system uses default appearance.

Creating Custom EGI Schemes

You can create custom schemes using EGI.CFG or EGI2.CFG.� These are configuration files that contain the colors and bitmaps used by the schemes.� You should edit the copies in the NEWDATA folder.� Refresh the system in order to copy it to the DATA folder, which enables it in the FOH.

EGI.CFG is the default configuration file that us supplied with the Aloha application software.� Although you can edit this file and change the schemes in the file, this file might be overwritten if you upgrade the Aloha application software.� EGI2.CFG, on the other hand, is intended for user-defined schemes, and it is not overwritten during an upgrade.� Aloha Technologies suggests only editing EGI2.CFG.

Each configuration file is a text-based file that contains variables and values that set the configuration.� Each scheme within the configuration file is defined by a scheme name labeled [Schemen], where n is the scheme number (for example, [Scheme1], [Scheme1001], and so on).� When you create EGI2.CFG, you should number your schemes starting with 1000 in order to avoid conflicts with the scheme numbers used by Aloha Technologies in EGI.CFG.

EGI.CFG and EGI2.CFG use the following variables:

Name

Default

Description

NAME

None

The name of the scheme.� Recommend 20 characters or less.

BUTTONCOLOR

176,176,208

Red-Green-Blue (RGB) value of the default button color.

BACKGROUND

None

The name of a bitmap to use as the background texture for dialogs.

BACKGROUNDCOLOR

255,255,255

RGB value of the default dialog background color.

MSGBOXCOLOR

192,192,193

RGB value of the default message box color.

BORDERPIXELS

8,7, or 3

The number of pixels around the button border.� The defaults are based on resolution: 1024x768=8, 800x600=7, 640x480=3.

CHECKBACKGROUND

None

The name of a bitmap to use as the background texture for the check display.� As of this writing, this function is not yet implemented.

CHECKCOLOR

255,255,255

RGB value of the default color for an un-selected check.

SELECTEDCHECKCOLOR

51,204,255

RGB value of the default color of a selected check.

TRAININGCHECKCOLOR

102,255,153

RGB value of the default color of training checks.

LABEL

0,0,0

RGB value of the default color for text labels on the window background.

RED

255,0,0

RGB value of the color to substitute for Red text on buttons.

GREEN

0,255,0

RGB value of the color to substitute for Green text on buttons.

BLUE

0,0,255

RGB value of the color to substitute for Blue text on buttons.

WHITE

255,255,255

RGB value of the color to substitute for White text on buttons.

BLACK

0,0,0

RGB value of the color to substitute for Black text on buttons.

PURPLE

255,0,255

RGB value of the color to substitute for Purple text on buttons.

MAROON

128,0,0

RGB value of the color to substitute for Maroon text on buttons.

MSGBMPPREFIX

Msg

The prefix for the default message box animation bitmaps.� The files are expected to be named the following: x1.bmp, x2.bmp, x3.bmp, and so on, where x is the prefix.� For example, Msg1.bmp, Msg2.bmp, and so on.

PRTBMPPREFIX

MsgPrt

The prefix for the printer error message box animation bitmaps.� The files are expected to be named the following: x1.bmp, x2.bmp, x3.bmp, and so on, where x is the prefix.� For example, MsgPrt1.bmp, MsgPrt2.bmp, and so on.

ARROWBMPPREFIX

Arrow

The prefix for the six scroll button bitmaps.� The files are expected to be named the following: xUp.bmp, xPageUp.bmp, xDown.bmp,

xPageDown.bmp, xLeft.bmp, and xRight.bmp, where x is the prefix.� For example, ArrowUp.bmp, ArrowPageDown.bmp, and so on.

You must store all bitmaps in the Aloha application software BMP folder, and they must use a .BMP suffix.

�

The RGB value for gray (192,192,192) has a special meaning to the Aloha application software because it is replaced with the default button color wherever it occurs on buttons.� Therefore you must use 192,192,193 to specify gray in most cases.

If you are not using a setting, do not leave it blank.� Comment it out using a semicolon.� Otherwise it will force the value to zero or blank, instead of using the default value.

Name all bitmaps that go with a scheme using a common prefix that is like the scheme name.

Be sure to test your scheme in all resolutions.� If your scheme is resolution-specific, include the resolution in the name.

If you substitute Red, use some kind of 'alert' color.� There are a several of places that are affected where the Aloha application software uses red as a warning color, so whatever color you substitute should stand out.

Don't forget to test training mode since it uses a different color for the check area.

It is easiest to start out by copying an existing scheme that has similar colors and then editing it.

Extended Information

If the FOH terminal screens repaint too slowly after enabling the EGI, try updating the video driver from the manufacturer's web site.� Drivers from the manufacturer might offer increased configuration options for OpenGL and better support for OpenGL than the drivers supplied with Windows.

Caveats

The EGI consumes additional system resources, so they might not be compatible with older, less powerful FOH terminals.

While the EGI can function along side Cool Interfaces, the EGI enhancements are not as readily noticeable with Cool Interfaces enabled.� Aloha Technologies recommends using either one or the other, but not both.

The EGI is not fully tested by Aloha Technologies in versions 5.2.5.x and 5.2.6.x.� If you enable the EGI in these versions, you are using it at your own risk.

============================================================================

See also:

AKBID3320 EGI Causes Windows Error on DigiCom Terminals

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1216 3-d 3d modern

�

Configuring QSR Automations KDS

Configuring QSR Automations KDS

============================================================================

AKBID1217

Created: 2 October 2002

Updated: 15 July 2003

Reviewed: 6 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2.4.x � 5.3.x

Subject: Configuring QSR Automations KDS with the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software supports both the QSR^� Automations RDS hardware drivers and the QSR Automations KDS software.� This document explains how to configure the QSR KSD software with the Aloha application software; refer to document AKBID1115 for more information on configuring the QSR RDS with the Aloha application software.

Information

This document is written to supplement the Aloha Video User Manual and the QSR KDS User Manual, not to replace them.

The Aloha application software offers two means of interfacing to the QSR video hardware: directly through the QSR RDS hardware drivers, or through the QSR KDS.

The QSR RDS integration utilizes the standard Aloha application software video display logic to drive the QSR video hardware.� The QSR KDS integration utilizes a software video display engine developed by QSR Automations that provides an alternative appearance and functionality than the standard Aloha application software video display logic.

Configure TCP/IP for Network Communication

You must use the TCP/IP protocol for network communication.� Refer document AKBID1063 for more information.

Install DCOM on FOH Terminal

You must install Distributed Component Object Model (DCOM) on the terminal that interfaces with the QSR KDS.� Refer to document AKBID1049 for more information.

Configure QSR KDS in the Aloha Application Software

To enable the QSR KDS interface in the Aloha application software, open Aloha Manager and select Maintenance/Store Settings/System/Interfaces.� Enable 'Use FOH COM Interface' and select 'Enable QSR Video KDS Interface'.� When you save your settings, Aloha Manager automatically fills the first available External Activity Interceptors box with 'AlohaQSR.AlohaQSR.1'.

Do not enable Maintenance/Store Settings/Video/Use Video.� If this is enabled, disable it.� This setting is intended for remote display systems that communicate via the VIDEOMX.DLL.

When you configure Video Groups in the Aloha application software, also configure each video group ID as a Department Number in the QSR KDS software.

If you enable a Delay Time for an item, it is passed to the QSR KDS software as the Cook Time.

When you configure Order Modes in the Aloha application software, also configure each order mode ID as a Destination in the QSR KDS software.

Aloha Communication with the QSR KDS

The ALOHAQSR.DLL module acts as a bridge between the Aloha application software and the QSR KDS.� This file resides in the Aloha application software BIN folder and it is automatically registered by the Aloha application software Front-of-House (FOH).� If you need to manually register ALOHAQSR.DLL, open a command prompt on the FOH terminal and use the following command line:

REGSVR32.EXE %LOCALDIR%\BIN\ALOHAQSR.DLL

You might have to include the path to REGSVR32.EXE in your command line.

The ALOHAQSR.DLL communicates with the QSR KDS through the QSRSOCK.DLL, which also resides in the Aloha application software BIN folder.� QSRSOCK.DLL requires three additional DLLs: XMLRDS.DLL, XMLKDS.DLL, and XMLTABLE.DLL.� The QSR installation process places these two files in the Windows SYSTEM or SYSTEM32 folder (depending on the operating system) and you have to manually copy these files to the Aloha application software BIN folder.

Environment Variables

Configure the following system environment variables on any terminal that is driving videos:

Variable

QSRDEBUG

Applications

IBER.EXE, IBERQS.EXE

Description

If set to TRUE, then the FOH logs extensive detail to the Debugging-Output-Files (debouts) for all data sent and received from the KDS.

System Variable Example

SET QSRDEBUG=FALSE

Command Line Example

N/A

Variable

QSRLOCALPORT

Applications

IBER.EXE, IBERQS.EXE

Description

Defaults to 0x6000 (hexadecimal) or 24576 (decimal).� Defines the local IP port on the local terminal.� If the value starts with '0x', then it is interpreted as a hexadecimal number.� If not, it is treated as decimal.

System Variable Example

SET QSRLOCALPORT=0x6000

Command Line Example

N/A

Variable

QSRLOCALADDR

Applications

IBER.EXE, IBERQS.EXE

Description

You can use this to specify an IP address for the local terminal in rare cases where a terminal has more than one IP address.

System Variable Example

SET QSRLOCALADDR=10.100.100.100

Command Line Example

N/A

Variable

QSRKDSPORT

Applications

IBER.EXE, IBERQS.EXE

Description

Defaults to 0x8000 (hexadecimal) or 32769 (decimal).� This value must match the port specified in the QSR KDS setup under Advanced/System/Socket Port.� If the value starts with '0x', then it is interpreted as a hexadecimal number.� If not, it is treated as decimal.

System Variable Example

SET QSRKDSPORT =0x8000

Command Line Example

N/A

Variable

QSRKDSADDR

Applications

IBER.EXE, IBERQS.EXE

Description

You can use this to specify an IP address for the KDS terminal in rare cases where a terminal has more than one IP address.

System Variable Example

SET QSRKDSADDR=10.100.100.100

Command Line Example

N/A

Variable

QSRDRIVETHRU

Applications

IBER.EXE, IBERQS.EXE

Description

You should set this value to TRUE for QuickService drive-thru terminals.� If this value is set to TRUE, then the terminal will output a 'Store' transaction when new orders are stored, and will output a 'Recall' transaction when stored orders are recalled.

System Variable Example

SET QSRDRIVETHRU=FALSE

Command Line Example

N/A

Troubleshooting

Use the debouts on each terminal to assist you in diagnosing problems with the QSR KDS.� Refer to document AKBID1134 for more information on debouts.

Here is a sample of a debout from a properly functioning system:

Dec 05, 09:49:39� Aloha Quick Service started... version 5.203BL12

Dec 05, 09:49:40� AlohaActivity: Created CLSID AlohaQSR.AlohaQSR.1

Dec 05, 09:49:40� ALOHAQSR: Environment initialized, terminal 2

Dec 05, 09:49:40� ALOHAQSR: Loading QSRSOCK.DLL...

Dec 05, 09:49:40� ALOHAQSR: Loaded QSRSOCK.DLL ok

Dec 05, 09:49:40� ALOHAQSR: Opened QSR Socket 140

Dec 05, 09:49:40� Begin initializing network...

If you do not see any ALOHAQSR activity in the debout at all, then verify that you properly enabled the COM and QSR KDS interfaces in the Aloha application software and that ALOHAQSR.DLL is properly registered.

�

You might see the following error if the required QSR DLL's are not in the Aloha BIN directory (QSRSOCK.DLL, XMLRDS.DLL, XMLKDS.DLL):

Mar 08, 15:35:38� ALOHAQSR: Could not load QSRSOCK.DLL, error 0

If the above activity is present, but items are not appearing on the videos, then view the transaction activity from within the QSR KDS software.� If you see transactions coming from the Aloha application software, then the problem is related to your QSR KDS configuration.

If the KDS shows no transactions coming from the Aloha application software, then turn add the QSRDEBUG=TRUE system environment variables the terminal and restart them.� You should see transactional activity in the log similar to the following:

Dec 04, 17:56:20� ALOHAQSR: Header: Txn 2097192 Trm 2 Dst 0 Table 0 Server 200 SrvName 'AM-T2' CustName 'CTR-239' Flg 0

Dec 04, 17:56:20� ALOHAQSR: Item: SubFunc 4 Txn 2097192 Desc '1 Donut' Msg '' ItemId 110101

Dec 04, 17:56:20� ALOHAQSR:�� ItemNum 2100623 Dept 11 Parent 0 Seat 0 Time 0 Pri 99 Price 54 Cat 2000 Flg 0

Dec 04, 17:56:23� ALOHAQSR: CancelItemEx: Txn 2097192 ItemNum 2100623

Dec 04, 17:56:23� ALOHAQSR: TenderedEx: Txn 2097192 Tax 0 SubTotal 0 Total 0

If this information is not present in the debout, then either you did not properly configure the QSRDEBUG variable, or you are not running a version of the Aloha application software that supports the QSR KDS.

If this transactional activity is present in the debout, but not on the KDS transaction viewer, then the socket settings for ALOHAQSR.DLL probably do not match the KDS settings.� If the settings match, then you need to examine the overall IP configuration.

Ensure that you disable QSRDEBUG after troubleshooting, to avoid unnecessarily large debug files and slower performance.

Extended Information

No information.

Caveats

Do not enable Maintenance/Store Settings/Video/Use Video.� If this is enabled, disable it.� This setting is intended for remote display systems that communicate via the VIDEOMX.DLL.

============================================================================

See also:

AKBID1049 Install DCOM in Windows

AKBID1063 TCP/IP

AKBID1115 Configuring QSR Automations RDS Ethernet Video

AKBID1134 Debouts

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1217

�

Using MSDE with the Aloha Application Software

Using MSDE with the Aloha Application Software

============================================================================

AKBID1218

Created: 14 November 2002

Updated: 14 November 2002

Reviewed: 11 February 2004

Microsoft^� Windows^� Versions: Windows 2000, Windows XP, Windows Server 2003

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x

Subject: Using MSDE with the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software versions 5.2x and higher support Microsoft Database Engine (MSDE) relational-databases (RDB).� This document explains how to configure the Aloha application software for use with an MSDE RDB.

Information

Operating System Configuration

Install the Windows operating system (OS) as described in the appropriate Aloha Knowledge Base (AKB) document.

The preferred hard drive-partitioning scheme for an Aloha application software file server with an RDB is different than a non-RDB Aloha application software file server.� Rather than configuring hard drive space for dated folders, space for the RDB becomes paramount.� Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Install the Aloha Application Software and MSDE

Install the Aloha application software using the Aloha Installation CD.

Select 'MSDE' on the Database Configuration window.� If you have not already installed MSDE, the installation application will prompt you to install it.� The MSDE installation requires you to set the 'MSDE Path' (target location for the MSDE program files, which is usually C:\MSSQL7) and the 'MSDE data root path' (target location for the MSDE databases, which should be on your RDB partition, such as E:\MSSQL7).� Click 'Install MSDE' to install MSDE.�

Once MSDE is installed, set the 'Computer Name' and 'Path To Database'.� Set the database path to the same location as you set when you configured the MSDE software, but include the 'DATA' folder in the path (for example, E:\MSSQL7\DATA). �Click 'Next', finish the installation, and restart the computer.

If the Aloha application software was already installed on the file server and is currently using a .DBF database, you can reinstall the Aloha application software from the Aloha Installation CD using the MSDE options in order to convert it to a MSDE RDB.� The Aloha application software will create a RDB based on the current DBF data.

Configuring Aloha

The Aloha application software automatically configures the RDB during the installation process, but you can change the amount of data stored in the RDB and the number of days before purging it.

To access the Aloha application software data storage options, open Aloha Manager, and select Maintenance/SQL Settings.� The Sales Group 1, Sales Group 2, and Payments/Labor subtabs contain options for summary data stored in the RDB.� The Grind subtab contains options for detailed data stored in the RDB.

The RDB becomes very large over time and users should consider adjusting these settings to best suite them.� In general, the summary data is intended for long-term storage, and the detailed (or Grind) data is intended for short-term storage.

Administering the RDB

MSDE is only the RDB engine, so it does not include any management tools.� You should consider using a third-party application to administer your database.

Reinstalling the Aloha Application Software with an Existing MSDE RDB

If you have already installed the Aloha application software with an MSDE database, you cannot reinstall (rather than upgrade) the Aloha application software and create a new MSDE database without first deleting the existing database.

You can install a third-party database management application in order to delete the database.� Otherwise, you have to uninstall MSDE, delete the IberSQL database on the file level, and reinstall the Aloha application software using the Aloha Installation CD (ensure that you enable MSDE).

Refer to document AKBID1131 for more information.

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

AKBID1131 Installing a New RDB Over and Existing RDB

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID3108 Setting RDB Grind Positions

AKBID3109 Re-synchronizing DBF Files From an RDB

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1218

�

Updating Binary Files on an Existing Aloha Installation CD

Updating Binary Files on an Existing Aloha Installation CD

============================================================================

AKBID1219

Created: 3 February 2003

Updated: 27 October 2003

Reviewed: 12 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2.5.x � 5.3.x

Subject: Updating Binary Files on an Existing Aloha Installation CD Image

============================================================================

Summary

When Aloha Technologies releases a new build for an existing version of the ALOHA^� application software, you can just download the updated applications (in compressed .ZIP format) rather than download the entire Aloha Installation CD, and then update your local copy of the installation CD.� This document explains how to perform this task and which binary files belong on each .ZIP file on the installation CD.

The information in this document only applies to upgrading the build number of an existing release.� You should not use this information to create a new installation CD for a major or minor enhancement release (refer to document AKBID1212 for an explanation of major enhancement releases, minor enhancement releases, and build numbers).� You must always download the new CD image for each major or minor enhancement release in order to ensure that you upgrade additional add-on software and that all necessary tasks are carried out in the upgrade procedure.� Failure to do so can lead to erroneous behavior or system failure.

Information

Before you can update the files on an existing installation CD, you must first copy the installation CD's contents to a hard drive or otherwise have read and write access to the media containing the installation CD's files.� Ensure that the read-only attribute is disabled for the files that you are updating from the installation CD.

Once you have read and write access to the files from the installation CD and you have download the updated application files from Aloha Technologies, you can decompress and extract the updated files into a temporary folder.� From this temporary folder, you can drag-and-drop the updated application files into their respective .ZIP files from the installation CD.�

After you update the files, also update the VERSION.INI from the root folder on the installation CD with the new build number.� This will ensure that the 'one-button-upgrade' feature functions properly.

Once you have updated the application files and VERSION.INI, you can burn a new installation CD containing the new build.

The following table lists each application (binary) file and the .ZIP file in which it resides on the Aloha Installation CD:

Binary File

.ZIP File(s) on Installation CD

ALOHAGL.DLL

\ALOHAQS\MISCBIN.ZIP

\ALOHATS\MISCBIN.ZIP

ALOHALAB.DLL

\ALOHAQS\AMGRMISC.ZIP

\ALOHATS\AMGRMISC.ZIP

ALOHAMGR.EXE�

\ALOHAQS\AMGR.ZIP

\ALOHATS\AMGR.ZIP

ALOHAQSR.DLL

\ALOHAQS\VIDEO.ZIP

\ALOHATS\VIDEO.ZIP

ALOHASEC.EXE

\ALOHAQS\ASEC.ZIP

\ALOHATS\ASEC.ZIP

ALOHASPY.EXE

\ALOHAQS\AMGRSPY.ZIP

\ALOHATS\AMGRSPY.ZIP

AMGRPS.DLL

\ALOHAQS\AMGR.ZIP

\ALOHATS\AMGR.ZIP

AMGRSHIM.DLL

\ALOHAQS\AMGR.ZIP

\ALOHATS\AMGR.ZIP

ARSEC.DLL

\ALOHAQS\ASEC.ZIP

\ALOHATS\ASEC.ZIP

ARSECPS.DLL

\ALOHAQS\ASEC.ZIP

\ALOHATS\ASEC.ZIP

ASECPS.DLL

\ALOHAQS\ASEC.ZIP

\ALOHATS\ASEC.ZIP

ASPYPS.DLL

\ALOHAQS\AMGRSPY.ZIP

\ALOHATS\AMGRSPY.ZIP

CALCEDIT.OCX

\ALOHAQS\PAYRECON.ZIP

\ALOHATS\PAYRECON.ZIP

CHKINFO.EXE

\MISC\CHECKINFO\CHECKINFO.EXE

CTL4X.DLL

\ALOHAQS\CTL4X.ZIP

\ALOHATS\CTL4X.ZIP

CTLSVR.EXE

\ALOHAQS\CTLSVR.ZIP

\ALOHATS\CTLSVR.ZIP

CTLSVRPS.DLL

\ALOHAQS\CTLSVR.ZIP

\ALOHATS\CTLSVR.ZIP

DBCONFIG.EXE

\ALOHAQS\AMGRDB.ZIP

\ALOHATS\AMGRDB.ZIP

DBFDIFF.EXE

\ALOHAQS\AMGRDB.ZIP

\ALOHATS\AMGRDB.ZIP

DBUP3.EXE

\ALOHAQS\AMGRDB.ZIP

\ALOHATS\AMGRDB.ZIP

DRSQL.EXE

\ALOHAQS\MISCBIN.ZIP

\ALOHATS\MISCBIN.ZIP

DW.DLL

\ALOHAQS\EDC.ZIP

\ALOHATS\EDC.ZIP

ECARDPOS.DLL

\ALOHAQS\EDC.ZIP

\ALOHATS\EDC.ZIP

ECARDPOS.CHM

Unused

EDC.EXE

\ALOHAQS\EDC.ZIP

\ALOHATS\EDC.ZIP

EDCSEC.DLL

\ALOHAQS\ASEC.ZIP

\ALOHATS\ASEC.ZIP

EDCSVR.EXE

\ALOHAQS\EDC.ZIP

\ALOHATS\EDC.ZIP

EDCSVRPS.DLL

\ALOHAQS\EDC.ZIP

\ALOHATS\EDC.ZIP

EDTPUNCH.DLL

\ALOHAQS\EDTPUNCH.ZIP

\ALOHATS\EDTPUNCH.ZIP

FASTECH.DLL

\ALOHAQS\FASTECH.ZIP

\ALOHATS\FASTECH.ZIP

GRIND.EXE

\ALOHATS\GRIND.ZIP

GRINDQ.EXE

\ALOHAQS\GRINDQ.ZIP

IBER.EXE

\ALOHATS\IBER.ZIP

IBER.EXE (Demo)

\DEMO\IBERTSD.ZIP

IBERADM.DLL

\ALOHAQS\MISCBIN.ZIP

\ALOHATS\MISCBIN.ZIP

IBERPS.DLL

\ALOHATS\MISCBIN.ZIP

IBERQS.EXE

\ALOHAQS\IBERQS.ZIP

IBERQS.EXE (Demo)

\DEMO\IBERQSD.ZIP

IBERQSPS.DLL

\ALOHAQS\MISCBIN.ZIP

IBERSQL.DLL

\ALOHAQS\MISCBIN.ZIP

\ALOHATS\MISCBIN.ZIP

IBERSTR.DLL

\ALOHAQS\MISCBIN.ZIP

\ALOHATS\MISCBIN.ZIP

INTERACT.DLL

Unused

INTERPRT.DLL

\ALOHAQS\AMGRMISC.ZIP

\ALOHATS\AMGRMISC.ZIP

LABSCHED.EXE

\ALOHAQS\LABSCHED.ZIP

\ALOHATS\LABSCHED.ZIP

MNT4X.DLL

\ALOHAQS\MNT4X.ZIP

\ALOHATS\MNT4X.ZIP

MPLAY.EXE

\ALOHAQS\MISCBIN.ZIP

\ALOHATS\MISCBIN.ZIP

PAYRECON.EXE

\ALOHAQS\PAYRECON.ZIP

\ALOHATS\PAYRECON.ZIP

PROCRECS.EXE

\ALOHAQS\AMGRDB.ZIP

\ALOHATS\AMGRDB.ZIP

PRODSCHD.EXE

\ALOHAQS\AMGRMISC.ZIP

\ALOHATS\AMGRMISC.ZIP

PRODSCHD.EXE

\ALOHAQS\PRODSEXE.ZIP

QWERTY.OCX

\ALOHAQS\PAYRECON.ZIP

\ALOHATS\PAYRECON.ZIP

REPRINT.EXE

\ALOHATS\REPRINT.ZIP

REPRINTQ.EXE

\ALOHAQS\REPRINTQ.ZIP

RPT.EXE

\ALOHAQS\RPT.ZIP

\ALOHATS\RPT.ZIP

SUM.EXE

\ALOHAQS\AMGRDB.ZIP

\ALOHATS\AMGRDB.ZIP

SYNCTIME.EXE

\ALOHATS\MISCBIN.ZIP

TEAMSERV.EXE

\ALOHAQS\AMGRMISC.ZIP

\ALOHATS\AMGRMISC.ZIP

USERTOOL.DLL

\ALOHAQS\AMGRMISC.ZIP

\ALOHATS\AMGRMISC.ZIP

VIDEO.EXE

\ALOHAQS\VIDEO.ZIP

\ALOHATS\VIDEO.ZIP

VIDEOMX.DLL

\ALOHAQS\VIDEO.ZIP

\ALOHATS\VIDEO.ZIP

Extended Information

No information.

Caveats

The information in this document only applies to upgrading the build number of an existing release.� You should not use this information to create a new installation CD for a major or minor enhancement release (refer to document AKBID1212 for an explanation of major enhancement releases, minor enhancement releases, and build numbers).� You must always download the new CD image for each major or minor enhancement release in order to ensure that you upgrade additional add-on software and that all necessary tasks are carried out in the upgrade procedure.� Failure to do so can lead to erroneous behavior or system failure.

============================================================================

See also:

AKBID1212 Aloha Application Software Version Numbering Scheme

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1219 corporate ftp portal reseller

�

Assigning the HASP LPT Port in the Aloha Application Software

Assigning the HASP LPT Port in the Aloha Application Software

============================================================================

AKBID1220

Created: 18 February 2003

Updated: 18 February 2003

Reviewed: 8 December 2003

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, BackOffice

Aloha POS Versions: 5.2.7.x � 5.3.x

Subject: Assigning the HASP LPT Port in the Aloha Application Software in Order to Fix LPT Conflicts

============================================================================

Summary

By default, the ALOHA^� application software scans all available parallel (LPT) ports for a HASP^� security key until one is located.� If you have a device such as a printer attached to LPT1 and the HASP security key attached to LPT2, then the Aloha application software will attempt to initialize the HASP security key on LPT1 before moving on to LPT2.� This can result in a conflict with the device attached to LPT1 and render the device inoperative.� This document explains how to configure the Aloha application software to only attempt to initialize the HASP security key on a specific LPT port.

Only perform the steps in this document if you are experiencing problems similar to those described above.� In most cases, the Aloha application software will function free of errors and not require the procedures listed in this document.

Information

Configuring the Aloha application software to only search for a HASP security key on a specific LPT port requires two steps: editing the Microsoft^� Windows^� registry to assign the port to which the HASP security key is attached and configuring the HASP security key drivers to not scan all of the available ports in order to automatically detect the key.

Defining the Port in the Windows Registry

Use the HASPLPTPORT.EXE utility that is available in the \MISC\HASP folder on the Aloha Installation CD to view, configure, or remove the LPT port number in the Windows registry.� HASPLPTPORT.EXE using the following syntax:

Usage: HASPLPTPORT.EXE [options]

Options:

/G�� Displays the current LPT port number defined in the Windows registry.

0, 1, or 2�� Defines the LPT port to which the HASP security key is attached.� '0' instructs the Aloha application software to search all of the LPT ports, '1' instructs the Aloha application software to use only LPT1, and '2' instructs the Aloha application software to use only LPT2.

/R�� Removes the LPT port definition from the Windows registry.

If you assign the HASP security key to LPT1 in the Windows registry using HASPLPTPORT.EXE but physically attach the HASP security key to LPT2 (or vice versa), then the Aloha application software will not locate the key and display a message stating 'Security key not found'.

To view the current HASP security key port assignment, type the following from a command line:

HASPLPTPORT.EXE /G

To assign the HASP security key to LPT1, type the following from a command line:

HASPLPTPORT.EXE 1

To remove the current HASP security key port assignment, type the following from a command line:

HASPLPTPORT.EXE /R

Disabling Automatic Key Detection in the HASP Drivers

After you assign the HASP security key port in the Aloha application software, you must perform the following in order to disable the HASP security key driver from attempting to automatically detect the HASP security key:

Open a command prompt and navigate to the Aloha application software BIN folder.

Uninstall the HASP security key driver using the following command line:

HINSTALL.EXE -R -KP -ALLDRV

3.        Reinstall the HASP security key driver using the following command line in order to disable the automatic detection feature:

HINSTALL.EXE -AD=NO -I

4.        Restart the computer.

If you need to reinstate automatic detection, then perform the steps above, but use the following command line when reinstalling the HASP security key driver:

HINSTALL.EXE -AD=YES -I

Extended Information

No information.

Caveats

Only perform the steps in this document if you are experiencing problems similar to those described above.� In most cases, the Aloha application software will function free of errors and not require the procedures listed in this document.

If you assign the HASP security key to LPT1 in the Windows registry using HASPLPTPORT.EXE but physically attach the HASP security key to LPT2 (or vice versa), then the Aloha application software will not locate the key and display a message stating 'Security key not found'.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1220 all all-in-one grind hasplptport hewlett hp lock lock-up one parallel packard reports up

style='mso-spacerun:yes'>� 2003

�

Store Lockout File

Store Lockout File

============================================================================

AKBID1221

Created: 26 February 2003

Updated: 26 February 2003

Reviewed: 5 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.4x � 5.3.x

Subject: Configuring and Implementing the SLO.CFG Store Lockout File

============================================================================

Summary

The ALOHA^� application software Store-Lockout-File (SLO.CFG) enables you to prevent users from adding, editing, or deleting any or all records within one or more Aloha database files, even if they login using the Super-Secret-Password (SSP).� This document explains how to configure and implement the SLO.CFG in the Aloha application software.

Information

The SLO.CFG is designed to interact with the Aloha application software Central Data Management (CDM) functionality, but you can also use it by itself.� Whereas the Aloha application software security levels limit users from accessing a specific database file or table, the SLO.CFG works in conjunction with security levels to further restrict the user's record-level access.

For example, you want users to be able to edit items 1000 through 2000 in Aloha Manager, but you do not want them to be able to edit items 2001 through 3000.� You would enable the user to edit items in the user's security level, and then you would configure the SLO.CFG to specifically restrict them from editing items 2001 through 3000.

Configuring the SLO.CFG

To enable the SLO.CFG, create a new text file (labeled SLO.CFG) in the Aloha application software NEWDATA folder.� Edit the SLO.CFG and add new restrictions in the format of '<filename>,<ID range>'.� 'Filename' is the name of the database file or table to restrict access (for example, ITM, SUB, TRM, and so on).� Refer to document AKBID1042 for a complete list of Aloha application software database files or tables.� 'ID Range' is the record number or range of record numbers in the database file to restrict.� Use an ID range of '0' to completely block users from editing all records in a database file or table.

For example, to restrict users from editing item numbers 3,000 to 3,999, add the following to the SLO.CFG:

ITM,3000-3999

To restrict users from editing menu number 199, add the following to the SLO.CFG:

MNU,199

To restrict users from editing printer numbers 10 and 11, add the following to the SLO.CFG:

PRT,10

PRT,11

To completely restrict users from editing any terminals, add the following to the SLO.CFG:

TRM,0

You must use a carriage return after each line in the SLO.CFG or you will experience syntax errors when you log into Aloha Manager.

You can include number ranges that do not yet exist in your restrictions.

Database name errors in the SLO.CFG are reported in Verify.� For example, if you use ITEM instead of ITM (for ITM.DBF), Verify informs you that there is not a file labeled ITEM.DBF in the Aloha application software NEWDATA folder.

When the SLO.CFG is distributed via Aloha Enterprise.com, the file attributes are automatically changed to Read-only and Hidden for security reasons.� If you manually distribute the SLO.CFG, you should manually edit the file attributes.

SLO.CFG Employee Records

If you want to limit access to the employee database file (EMP.DBF), you only have the option of 0 or 2.� Zero completely restricts users from editing, adding, or deleting employees.� Two enables users to add new employees, but they cannot edit employees after saving the record for the first time.

To disable users from adding, editing or deleting employees, add 'EMP,0' to the SLO.CFG.� To enable users to add new employees by not enable them to edit or delete employees, add 'EMP,2' to the SLO.CFG.

Extended Information

No information.

Caveats

At the time of this writing, the following restrictions and limitations apply to the SLO.CFG:

1.        You must restart Aloha Maintenance or log off Aloha Manager in order to enable changes made to the SLO.CFG.

2.        To gain full access to database records, you must remove or rename the SLO.CFG from the NEWDATA folder and restart Aloha Manager.

3.        The SLO.CFG does not currently function with a relation database (RDB).

4.        The SLO.CFG applies to all users.� Access cannot be limited to specific users or differ between users.

5.        You cannot add remarks (REM statements) to the SLO.CFG.

You must use a carriage return after each line in the SLO.CFG or you will experience syntax errors when you log into Aloha Manager.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1042 Aloha Application Software Database Files

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1221 7003 certain lock out super user superuser

�

Configuring Aloha Applications as the Windows Shell

Configuring Aloha Applications as the Windows Shell

============================================================================

AKBID1222

Created: 27 February 2003

Updated: 27 August 2003

Reviewed: 5 March 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, BackOffice

Aloha POS Versions: 5.0x � 5.3.x

Subject: Configuring ALOHAMGR.EXE, IBER.EXE, or IBERQS.EXE as the Windows Shell

============================================================================

Summary

Microsoft^� Windows^� enables you to assign third-part applications as the Windows shell, replacing EXPLORER.EXE.� This document explains how to configure the ALOHA^� application software to act as the Windows shell.

Third party software (including device drivers such as OPOS) might not function properly with an Aloha application configured as the Windows shell.

At the time of this writing, you must use Windows Explorer as the Windows shell if you are using Aloha eCard.

Information

Windows 95, Windows 98, and Windows Me

ALOHAMGR.EXE, IBER.EXE, and IBERQS.EXE can replace EXPLORER.EXE as the Windows shell.� With the new shell, you do not have access to the Windows Start menu, but you can press <Ctrl> plus <Esc> on the keyboard to display the Task Manager.� From the Task Manager, you can run other applications, such as Windows Explorer or a command prompt.

Perform the following to change the Windows shell:

Remove any shortcuts to the Aloha application software from the Windows StartUp folder

Edit the SYSTEM.INI file in the Windows folder and remark (;) out the line stating SHELL=EXPLORER.EXE.�

Insert a new line in the SYSTEM.INI that states SHELL=D:\ALOHA\BIN\IBER.EXE (use the correct path and file name) under the declaration that you previously remarked out.� It should appear similar to the following:

;SHELL=EXPLORER.EXE

SHELL=D:\ALOHA\BIN\IBER.EXE

Save and close the SYSTEM.INI.

Restart Windows.

To enable the default Windows settings, remove the remark from the original shell line, place it at the beginning of the new shell line, and restart Windows.

Windows NT, Windows 2000, and Windows XP

ALOHAMGR.EXE, IBER.EXE, and IBERQS.EXE can replace EXPLORER.EXE as the Windows shell.� With the new shell, you do not have access to the Windows Start menu, but you can press <Ctrl> plus <Shift> plus <Esc> on the keyboard to display the Task Manager.� From the Task Manager, you can run other applications, such as Windows Explorer or a command prompt.

Perform the following to change the Windows shell:

The incorrect use of the Windows Registry Editor can lead to serious, system-wide problems that might require the reinstallation of the operating system.� Use this tool at your own risk.�

Remove any shortcuts to the Aloha application software from the Windows StartUp folder

To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

Path out HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\Current Version\Winlogon.

Double-click the Shell key, and change the Value Data to the path and application of the new Windows shell (for example, D:\ALOHA\BIN\ALOHAMGR.EXE).

Select Registry/Exit to exit the Windows Registry Editor.

Restart Windows.

To enable the default Windows settings, perform the same steps as above, but use EXPLORER.EXE as the Shell key's value, and restart Windows.

Shortcuts in Aloha Manager

You can use the Aloha Manager Navigation Bar or Aloha Manager's HTML-based background to add shortcuts to various applications, such as EDC.EXE (EDC), Aloha BackOffice applications, Windows Explorer, and so on.

If you create shortcuts to any BackOffice applications, ensure that you configure the BACKOFFICE folder as the 'Initial Directory' or working folder.

Disable Users from Exiting Aloha Manager

You can disable users from exiting Aloha Manager in Aloha versions 5.2.8.75 and higher.� Aloha Technologies recommends doing so if you are using Aloha Manager as the Windows shell, since exiting Aloha Manager yields a blank screen and could confuse users.

Extended Information

No information.

Caveats

Third party software (including device drivers such as OPOS) might not function properly with an Aloha application configured as the Windows shell.

At the time of this writing, you must use Windows Explorer as the Windows shell if you are using Aloha eCard.

The incorrect use of the Windows Registry Editor can lead to serious, system-wide problems that might require the reinstallation of the operating system.� Use this tool at your own risk.�

If you create shortcuts to any BackOffice applications, ensure that you configure the BACKOFFICE folder as the 'Initial Directory' or working folder.

============================================================================

See also:

Microsoft Knowledge Base Article ID: Q100328

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1222

�

Windows Server 2003 FOH Terminal Setup

Windows Server 2003 FOH Terminal Setup

============================================================================

AKBID1223

Created: 4 April 2003

Updated: 16 April 2003

Reviewed: 2 March 2004

Microsoft Windows Versions: Windows Server 2003

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2.7.105 � 5.3.x

Subject: Windows Server 2003 FOH Terminal Setup

============================================================================

Summary

The ALOHA^� application software requires several specialized settings (as well as several preferred settings) in the Microsoft^� Windows^� Server 2003 operating system (OS) to properly run on a terminal.� Failure to properly configure Windows Server 2003 will result in erroneous Aloha application software behavior.� If you are using the terminal to run both Front-of-House (FOH) and Back-of-House (BOH) together, refer to document AKBID1225.

Information

Although some computers come with Windows Server 2003 preloaded while others do not, this document is based on editing the settings of and existing Windows Server 2003 installation.� Users who are installing Windows Server 2003 from scratch or upgrading another OS to Windows Server 2003 can still use this document either by employing these instructions after the Windows Server 2003 installation or by making some of these changes during the Windows Server 2003 installation.

Microsoft Windows Server 2003 Server limits the number of users to the number of licenses purchased. �Breaking the connection limit can disrupt the Aloha application software.� Refer to document AKBID1048 for more information the recommended number of FOH terminals for each operating system.

File System

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

Set the workgroup name the same on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the workgroup name, but this name is arbitrary as long as it is consistent throughout the Aloha application software.�

You can configure Windows Server 2003 as a member of a workgroup or a domain.� Select a workgroup name.� Only experienced network administrators should consider enabling a domain name.

Set the terminal's network name.� Aloha Technologies uses TERM1, TERM2, and so on by default.� You can use different names, but they must follow Aloha application software specifications.� You must use a common name on all terminals (the TERMSTR, refer to document AKBID1010) followed by a number designating the terminal's ID number.� Examples include ALOHA1, ALOHA2, TSFOH_1, and TSFOH_2.� In this case, the TERMSTR would be 'ALOHA' or 'TSFOH_'.� You cannot use different TERMSTR names within the same Aloha system.� You cannot use spaces, but you can use underscores.� You can use leading zeros if they are part of the TERMSTR, but it is not recommended.

Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure that terminals always have an address assigned to them.� The Aloha application software will not function without an IP address assigned to the terminal.� You can install multiple protocols as long as the proper protocol for the Aloha application software has been marked as such by the lana number assignment.� You must assign lana number zero to the network binding (protocol and adaptor) used by the Aloha application software.� Refer to document AKBID1018 for more information on assigning lana numbers.�

You must enable NetBIOS over TCP/IP in order to use TCP/IP with the Aloha application software.� To do this, access the TCP/IP properties for the Local Area Connection, click the Advanced button, and select the WINS tab.� Select 'Enable NetBIOS over TCP/IP'.

TCP/IP Media Sense

Windows Server 2003 uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.�

Perform the following to disable Media Sense in the Windows Registry:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that might require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters.

3.        Verify the DisableDHCPMediaSense value exists in the folder.� If it does, double-click it and change Value Data to '1'.� If it does not exist, choose Edit/New/DWORD Value and name the key' DisableDHCPMediaSense'.� Then double-click the entry and change Value Data to '1'.

4.        Select Registry/Exit to exit the Windows Registry Editor.

5.        Restart Windows.�

Media Sense provides the ability to connect to networks with different DHCP options in one Windows session without the need to release and renew the IP configuration by using IPCONFIG.EXE.� If you disable Media Sense, no new IP configuration information is obtained when you connect to a new network unless you restart the computer, or you release and renew the IP configuration by using IPCONFIG.EXE.

Refer to Microsoft Knowledge Base document Q239924 for more information on Media Sense.

Display Settings

Set the Color palette to 16-bit color or higher.�

Refer to document AKBID1165 for screen resolution settings.

Do not enable a Windows screen saver.

Time Zone & Daylight Savings

For the file server and all terminals to display the correct time and adjust to daylight savings changes properly, the time and date settings must be properly configured in Windows so the file server and each terminal have the same time, date, time zone and daylight savings settings.� The time settings need to be the same on all terminals and the file server.� If the area observes daylight savings, then you must configure the file server and each terminal to automatically adjust for daylight savings.� You can disable automatic daylight savings adjustment if you are in an area that does not recognize daylight savings time (or if you do not want the file server and terminals to automatically adjust for daylight savings), but it needs to be disabled throughout the Aloha application software.� You cannot enable daylight savings on one terminal and not on another or enable it on the file server and not the terminals.

FIFO Buffers

Windows Server 2003 enables First-In-First-Out (FIFO) buffers for each COM port.� These buffers tend to interfere with printers using Xon/Xoff flow control, so Aloha Technologies disables these buffers on all COM ports on all terminals, regardless of the printer type.� (In the event of a printer or COM port failure, a printer using Xon/Xoff flow control may be temporally connected to the port in the future.)

To access the FIFO buffer settings, select Start/Settings/Control Panel/System or right click My Computer and select Properties.� Select Hardware/Device Manager, and click the plus sign (+) next to Ports to expand it.� Select each port one at a time, and select Properties/Port Settings/Advanced.� Clear 'Use FIFO buffer'.� Repeat for each COM port.� The LPT port does not have this option.

Login Name

Refer to document AKBID1006 for more information on configuring Windows logins for the Aloha application software.

Install Aloha Software

Once Windows Server 2003 is configured according to the standards outlined in this document and you can view the network, use the terminal installation diskette to install the Aloha application software.

To create this diskette, insert the Aloha Installation CD in the file server's CD-ROM, and run ADVANCED.EXE.� Select Make Diskettes/Create Terminal Installation Diskette from the Main Menu

Once you have created the diskette, insert it into the terminal's floppy drive, and run SETUPTRM.EXE.� The setup program walks you through the rest of the installation and configures necessary file sharing, creates or copies (from the file server) the necessary folders and files, and adds a shortcut to the Windows StartUp folder.

If the terminal does not have a floppy drive, run SETUPTRM.EXE directly from the CD-ROM on the file server.� In order to do this, map a drive to the CD-ROM on the file server, but do not select the Reconnect at Logon option when mapping the drive.� Run \TERMINST\SETUPTRM.EXE from the Aloha Installation CD.� The setup program walks you through the rest of the installation and configures necessary file sharing, creates or copies (from the file server) the necessary folders and files, and adds a shortcut to the Windows StartUp folder.

Once the installation is complete, you can edit user access to the BOOTDRV.

Set Control Server and EDC Server Login on the File Server

You may need to adjust the login account used by CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) on the file server to ensure proper operation with terminals running Windows Server 2003.� Refer to AKBID1197 for more information.

Enable a Hot-plugged Keyboard

By default, Windows Server 2003 does not enable you to hot-plug a keyboard if Windows has already started without a keyboard attached.� You can change this behavior and enable hot-plugging a keyboard by performing the following to edit the Windows registry:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that might require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

Path out HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\i8042prt\Parameters.

Verify the Headless value exists in the folder.� If it does, double-click it and change Value Data to '1'.� If it does not exist, choose Edit/New/DWORD Value and name the key 'Headless'.� Then double-click the entry and change Value Data to '1'.

Select Registry/Exit to exit the Windows Registry Editor.

Restart Windows.

Extended Information

No information.

Caveats

Windows Server 2003 uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.� To eliminate this, disable Media Sense.

============================================================================

See also:

AKBID1005 Microsoft Windows Auto Log In

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1010 Aloha Application Software System Environment Variables

AKBID1018 Network Lana Numbers

AKBID1048 Aloha Application Software Hardware and OS Specifications

AKBID1165 FOH Screen Resolution Settings

AKBID1175 Aloha Terminal Restart Options

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1197 Assigning Logins to Aloha Services

AKBID1204 Default Aloha System Environment Variable Placement

AKBID1224 Windows Server 2003 File Server Setup

AKBID1225 Windows Server 2003 Server/Terminal Setup

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1223 stage staging windows 2003

Copyright Aloha Technologies, Ltd. �2004

Windows Server 2003 File Server Setup

Windows Server 2003 File Server Setup

============================================================================

AKBID1224

Created: 4 April 2003

Updated: 19 June 2003

Reviewed: 2 March 2004

Microsoft Windows Versions: Windows Server 2003

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2.7.105 � 5.3.x

Subject: Windows Server 2003 File Server Setup

============================================================================

Summary

The ALOHA^� application software requires you to configure the Microsoft^� Windows^� Server 2003 operating system (OS) to properly run on the run on the file server.� Failure to properly configure Windows Server 2003 will result in erroneous Aloha application software behavior.� If you are using the file server to run both Front-of-House (FOH) and Back-of-House (BOH) together, refer to document AKBID1225.

Information

Although some computers come with Windows Server 2003 preloaded while others do not, this document is based on editing the settings of an existing Windows Server 2003 installation.� Users who are installing Windows Server 2003 from scratch or upgrading another OS to Windows Server 2003 can still use this document either by employing these instructions after the Windows Server 2003 installation or by making some of these changes during the Windows Server 2003 installation.

Microsoft Windows Server 2003 Server limits the number of users to the number of licenses purchased.� Breaking the connection limit can disrupt the Aloha application software.� Refer to document AKBID1048 for more information the recommended number of FOH terminals for each operating system.

Drive Sizes and Partitions

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

Set the workgroup name the same on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the workgroup name, but this name is arbitrary as long as it is consistent throughout the Aloha application software.�

You can configure Windows Server 2003 as a member of a workgroup or a domain.� Select a workgroup name.� Only experienced network administrators should consider enabling a domain name.

Aloha Technologies uses the network name ALOHABOH by default, but this name is arbitrary, so you can use a different name if desired.�

Aloha Technologies prefers the use of static IP addresses (which are defined on the file server instead of dynamically assigned), but you can use dynamic addressing as long as you ensure the file server always has an address assigned to it.� The Aloha application software will not function without an IP address assigned to the file server.� You can install multiple protocols as long as the proper protocol for the Aloha application software has been marked as such by the lana number assignment.� You must assign lana number zero to the network binding (protocol and adaptor) used by the Aloha application software.� Refer to document AKBID1018 for more information on assigning lana numbers.�

You must enable NetBIOS over TCP/IP in order to use TCP/IP with the Aloha application software.� To do this, access the TCP/IP properties for the Local Area Connection, click the Advanced button, and select the WINS tab.� Select 'Enable NetBIOS over TCP/IP'.

TCP/IP Media Sense

Windows Server 2003 uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.�

Perform the following to disable Media Sense in the Windows Registry:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that might require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters.

3.        Verify the DisableDHCPMediaSense value exists in the folder.� If it does, double-click it and change Value Data to '1'.� If it does not exist, choose Edit/New/DWORD Value and name the key ' DisableDHCPMediaSense '.� Then double-click the entry and change Value Data to '1'.

4.        Select Registry/Exit to exit the Windows Registry Editor.

5.        Restart Windows.�

Media Sense provides the ability to connect to networks with different DHCP options in one Windows session without the need to release and renew the IP configuration by using IPCONFIG.EXE.� If you disable Media Sense, no new IP configuration information is obtained when you connect to a new network unless you restart the computer, or you release and renew the IP configuration by using IPCONFIG.EXE.

Refer to Microsoft Knowledge Base document Q239924 for more information on Media Sense.

Display Settings

Set the Color palette to 16-bit color or higher.�

Refer to document AKBID1165 for screen resolution settings.

Do not enable a Windows screen saver.

Time Zone & Daylight Savings

For the file server and all terminals to display the correct time and adjust to daylight savings changes properly, the time and date settings must be properly configured in Windows so the file server and each terminal have the same time, date, time zone and daylight savings settings.� The time settings need to be the same on all terminals and the file server.� If the area observes daylight savings, then you must configure the file server and each terminal to automatically adjust for daylight savings.� You can disable automatic daylight savings adjustment if you are in an area that does not recognize daylight savings time (or if you do not want the file server and terminals to automatically adjust for daylight savings), but it needs to be disabled throughout the Aloha application software.� You cannot enable daylight savings on one terminal and not on another or enable it on the file server and not the terminals.

Login Name

Refer to document AKBID1006 for more information on configuring Windows logins for the Aloha application software.

Processor Performance

By default, Windows Server 2003 is configured to assign foreground applications priority processing.� This can cause erroneous behavior in background applications, such as Control Server and EDC Server.� Aloha Technologies suggests setting the processor priority to background applications.

To configure the processor priority, open the System properties, select Advanced, and select Settings in the Performance section.� Select Advanced, and set the performance scheduling to Background Services.

Install Aloha Software

Once Windows Server 2003 is set up to the standards outlined in this document, use the Aloha Installation CD to install the Aloha application software.� Run ADVANVED.EXE from the Aloha Installation CD.� The setup program walks you through the rest of the installation.

Refer to document AKBID1162 for more information on running Control Server and EDC Server as Windows services.

Once the installation is complete, you can edit user access to the BOOTDRV share.

Set Control Server and EDC Server Login

You may need to adjust the login account used by CTLSVR.EXE (Control Server) and EDCSVR.EXE (EDC Server) on the file server to ensure proper operation with terminals running Windows Server 2003.� Refer to AKBID1197 for more information.

Extended Information

HASP Security Key Drivers

You must use version 4.95 or higher of the HASP^� security key drivers.� If the Aloha Installation CD does not install a compatible version, then you must download an updated version of the HASP drivers from www.ealaddin.com.� Refer to document AKBID3016 for more information on HASP driver installation.

EOD File Copy Errors

If you are experience problems where the End-of-Day (EOD) process fails to copy files, you should perform the following in order to disable write caching for the hard drive in which the Aloha application software resides on the file server:

Open Windows Explorer, right-click on the hard drive in which the Aloha application software is installed, and select Properties.

Select the Hardware tab.

Select the physical drive, and select Properties.

Select the Policies tab.

Clear the 'Enable write caching on the disk' option, and press OK.

Caveats

Windows Server 2003 uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.� To eliminate this, disable Media Sense.

============================================================================

See also:

AKBID1005 Microsoft Windows Auto Log In

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1010 Aloha Application Software System Environment Variables

AKBID1018 Network Lana Numbers

AKBID1048 Aloha Application Software Hardware and OS Specifications

AKBID1148 Backup Procedures

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1197 Assigning Logins to Aloha Services

AKBID1204 Default Aloha System Environment Variable Placement

AKBID1223 Windows Server 2003 FOH Terminal Setup

AKBID1225 Windows Server 2003 Server/Terminal Setup

AKBID3016 Manual HASP Driver Installation and Removal

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1224 stage staging windows 2003

Windows Server 2003 File Server/Terminal Setup

Windows Server 2003 File Server/Terminal Setup

============================================================================

AKBID1225

Created: 4 April 2003

Updated: 19 June 2003

Reviewed: 2 March 2004

Microsoft Windows Versions: Windows Server 2003

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2.7.105 � 5.3.x

Subject: Microsoft Windows Server 2003 File Server and Terminal on the Same Computer Setup

============================================================================

Summary

The ALOHA^� application software requires you to configure the Microsoft^� Windows^� Server 2003 operating system (OS) to properly run on the run both Front-of-House (FOH) and Back-of-House (BOH) together on the same computer.� Failure to properly configure Windows Server 2003 will result in erroneous Aloha application software behavior.� If you are using the computer as a file server only, refer to document AKBID1224.� If you are using the computer as a terminal only, refer to document AKBID1223.

Refer to document AKBID1116 for more information on the limitations of running both the FOH and BOH together on the same PC.

Information

Although some computers come with Windows Server 2003 preloaded while others do not, this document is based on editing the settings of an existing Windows Server 2003 installation.� Users who are installing Windows Server 2003 from scratch or upgrading another OS to Windows Server 2003 can still use this document either by employing these instructions after the Windows Server 2003 installation or by making some of these changes during the Windows Server 2003 installation.

If you are converting an existing file server to a file server/terminal, refer to the Extended Information section of this document.

Microsoft Windows Server 2003 Server limits the number of users to the number of licenses purchased.� Breaking the connection limit can disrupt the Aloha application software.� Refer to document AKBID1048 for more information the recommended number of FOH terminals for each operating system.

Drive Sizes and Partitions

Refer to document AKBID1183 for more information on hard drive partitions and file systems.

Network

Set the workgroup name the same on all terminals and the file server.� Aloha Technologies generally uses IBERTECH as the workgroup name, but this name is arbitrary as long as it is consistent throughout the Aloha application software.�

You can configure Windows Server 2003 as a member of a workgroup or a domain.� Select a workgroup name.� Only experienced network administrators should consider enabling a domain name.

Set the file server/terminal's network name.� Aloha Technologies uses TERM1, TERM2, and so on by default.� You can use different names, but they must follow Aloha application software specifications.� You must use a common name on all terminals (the TERMSTR, refer to document AKBID1010) followed by a number designating the terminal's ID number.� Examples include ALOHA1, ALOHA2, TSFOH_1, and TSFOH_2.� In this case, the TERMSTR would be 'ALOHA' or 'TSFOH_'.� You cannot use different TERMSTR names within the same Aloha system.� You cannot use spaces, but you can use underscores.� You can use leading zeros if they are part of the TERMSTR, but it is not recommended.

Aloha Technologies prefers the use of static IP addresses (which are defined on the file server/terminal instead of dynamically assigned), but you can use dynamic addressing as long as you ensure the file server/terminal always has an address assigned to it.� The Aloha application software will not function without an IP address assigned to the file server.� You can install multiple protocols as long as the proper protocol for the Aloha application software has been marked as such by the lana number assignment.� You must assign lana number zero to the network binding (protocol and adaptor) used by the Aloha application software.� Refer to document AKBID1018 for more information on assigning lana numbers.�

You must enable NetBIOS over TCP/IP in order to use TCP/IP with the Aloha application software.� To do this, access the TCP/IP properties for the Local Area Connection, click the Advanced button, and select the WINS tab.� Select 'Enable NetBIOS over TCP/IP'.

TCP/IP Media Sense

Windows Server 2003 uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.�

Perform the following to disable Media Sense in the Windows Registry:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that might require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters.

3.        Verify the DisableDHCPMediaSense value exists in the folder.� If it does, double-click it and change Value Data to '1'.� If it does not exist, choose Edit/New/DWORD Value and name the key ' DisableDHCPMediaSense '.� Then double-click the entry and change Value Data to '1'.

4.        Select Registry/Exit to exit the Windows Registry Editor.

5.        Restart Windows.�

Media Sense provides the ability to connect to networks with different DHCP options in one Windows session without the need to release and renew the IP configuration by using IPCONFIG.EXE.� If you disable Media Sense, no new IP configuration information is obtained when you connect to a new network unless you restart the computer, or you release and renew the IP configuration by using IPCONFIG.EXE.�

Refer to Microsoft Knowledge Base document Q239924 for more information on Media Sense.

Display Settings

Set the Color palette to 16-bit color or higher.�

Refer to document AKBID1165 for screen resolution settings.

Do not enable a Windows screen saver.

Time Zone & Daylight Savings

For the file server and all terminals to display the correct time and adjust to daylight savings changes properly, the time and date settings must be properly configured in Windows so the file server and each terminal have the same time, date, time zone and daylight savings settings.� The time settings need to be the same on all terminals and the file server.� If the area observes daylight savings, then you must configure the file server and each terminal to automatically adjust for daylight savings.� You can disable automatic daylight savings adjustment if you are in an area that does not recognize daylight savings time (or if you do not want the file server and terminals to automatically adjust for daylight savings), but it needs to be disabled throughout the Aloha application software.� You cannot enable daylight savings on one terminal and not on another or enable it on the file server and not the terminals.

FIFO Buffers

Windows Server 2003 enables First-In-First-Out (FIFO) buffers for each COM port.� These buffers tend to interfere with printers using Xon/Xoff flow control, so Aloha Technologies disables these buffers on all COM ports on all terminals, regardless of the printer type.� (In the event of a printer or COM port failure, a printer using Xon/Xoff flow control may be temporally connected to the port in the future.)

To access the FIFO buffer settings, select Start/Settings/Control Panel/System or right click My Computer and select Properties.� Select Hardware/Device Manager, and click the plus sign (+) next to Ports to expand it.� Select each port one at a time, and select Properties/Port Settings/Advanced.� Clear 'Use FIFO buffer'.� Repeat for each COM port.� The LPT port does not have this option.

Login Name

Refer to document AKBID1006 for more information on configuring Windows logins for the Aloha application software.

Processor Performance

By default, Windows Server 2003 is configured to assign foreground applications priority processing.� This can cause erroneous behavior in background applications, such as Control Server and EDC Server.� Aloha Technologies suggests setting the processor priority to background applications, but this can affect the FOH, which is also running on the file server.� If you experience problems with Control Server or EDC Server that you can attribute to processor time, consider changing the processor priority.

To configure the processor priority, open the System properties, select Advanced, and select Settings in the Performance section.� Select Advanced, and set the performance scheduling to Background Services.

Install Aloha Software

Once the installation is complete, you can edit user access to the BOOTDRV share.

Once Windows Server 2003 is set up to the standards outlined in this document, use the Aloha Installation CD to install the Aloha application software.� Run ADVANVED.EXE from the Aloha Installation CD.� The setup program walks you through the rest of the installation.� You must select 'Run Front of House and Back of House on same PC' on the Aloha Configuration window.

Refer to document AKBID1162 for more information on running Control Server and EDC Server as Windows services.

Once the installation is complete, you can edit user access to the BOOTDRV share.

Refer to document AKBID1116 for more information on configuring a looping batch file to start the FOH on the file server/terminal.

Extended Information

HASP Security Key Drivers

You must use version 4.95 or higher of the HASP^� security key drivers.� If the Aloha Installation CD does not install a compatible version, then you must download an updated version of the HASP drivers from www.ealaddin.com.� Refer to document AKBID3016 for more information on HASP driver installation.

Converting an Existing File Server to a File Server/Terminal

The steps for converting an existing file server to a file server/terminal depend on the usage.

If you are not going to make the file server/terminal master or server-capable (such as a COM interface server or a remote print server), then you can just add the MASTERCAPABLE, SERVERCAPABLE, LOCALDIR, TERM, CALIBRATE, and IBERROOT variables to the system environment variables and assign the proper values to them; and optionally configure a looping batch file to restart the FOH (refer to document AKBID1116).

If at any time you will make the file server/terminal master and/or server-capable, then you must add the MASTERCAPABLE, SERVERCAPABLE, LOCALDIR, TERM, CALIBRATE, and IBERROOT variables to the system environment variables and assign the proper values to them; rename the file server/terminal to match the TERMSTR+TERM nomenclature (Aloha Technologies suggests making it terminal one); and optionally configure a looping batch file to restart the FOH (refer to document AKBID1116).

EOD File Copy Errors

If you are experience problems where the End-of-Day (EOD) process fails to copy files, you should perform the following in order to disable write caching for the hard drive in which the Aloha application software resides on the file server:

Open Windows Explorer, right-click on the hard drive in which the Aloha application software is installed, and select Properties.

Select the Hardware tab.

Select the physical drive, and select Properties.

Select the Policies tab.

Clear the 'Enable write caching on the disk' option, and press OK.

Caveats

Windows Server 2003 uses Media Sense with TCP/IP to determine whether the network card is in a link state.� If the computer is removed from the network or the network becomes disabled, Media Sense disables TCP/IP, which can disrupt the Aloha application software.� To eliminate this, disable Media Sense.

============================================================================

See also:

AKBID1005 Microsoft Windows Auto Log In

AKBID1006 Configuring Windows User and Share Permissions for Aloha

AKBID1010 Aloha Application Software System Environment Variables

AKBID1018 Network Lana Numbers

AKBID1048 Aloha Application Software Hardware and OS Specifications

AKBID1116 File Server/Terminal Limitations

AKBID1148 Backup Procedures

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1165 FOH Screen Resolution Settings

AKBID1175 Aloha Terminal Restart Options

AKBID1183 Recommended Hard Drive Partitions, File Systems, and Setup

AKBID1204 Default Aloha System Environment Variable Placement

AKBID1223 Windows Server 2003 FOH Terminal Setup

AKBID1224 Windows Server 2003 File Server Setup

AKBID3016 Manual HASP Driver Installation and Removal

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1225 boh/foh bohfoh foh/boh fohboh stage staging terminal/server windows 2003

Front-of-House Item Pricing Hierarchy

Front-of-House Item Pricing Hierarchy

============================================================================

AKBID1226

Created: 11 April 2003

Updated: 25 July 2003

Reviewed: 11 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Front-of-House Item Pricing Hierarchy

============================================================================

Summary

The ALOHA^� application software supports multiple methods of assigning prices to items, and in some cases, you can assign two or more prices to a single item by using different pricing methods.� This document explains the hierarchy used by the Aloha application software when determining the price to apply to an ordered item.

Information

TableService Items Ordered from a Submenu or Modifier Menu

The following rules apply to ordering items via a submenu or modifier menu:

Quantity Pricing and Fixed Pricing override all other pricing methods, in that order.

Submenu and Modifier Menu radio buttons:

Button price at the submenu and modifier menu level overrides all pricing methods, except fixed pricing and quantity pricing.

If you enable the Item Price, then the price assigned in item maintenance is used unless there is a Price Level assigned to the item, in which case the price level's price us used.� If a 'price level change' event occurs, this would in turn override the price level.� If a 'price change' event occurs, it would overwrite the item price.

If you assign a price level to an item on the submenu or modifier menu, then it takes precedence over both the item price and the price level assigned in item maintenance.� If a 'price level change' event occurs, it looks to see if the price level is assigned on the submenu or modifier menu in order to make the adjustment.

In summary, item pricing uses the following hierarchy when ordering items via a submenu or modifier menu, with quantity pricing overriding all other prices:

Quantity pricing

Fixed pricing

Price assigned to the submenu or modifier button

An event that changes the price level

Price level assigned to the submenu or modifier button

Price level assigned in item maintenance

Price assigned in item maintenance

TableService Items Ordered from a Barcode Scanner or a PLU Button

The following rules apply to ordering items via a barcode scanner or a PLU button:

Quantity pricing and fixed pricing override all other pricing methods, in that order.

Barcode scanner and PLU input do not recognize the price configuration on submenus and modifier menus.

If you assign a price level to an item, then it takes precedence over the item price.� If a 'price level change' event occurs, then it takes precedence over the price level assigned to the item.� The item price is used if there is not a price level assigned to the item.� If an 'item price change' event occurs, then it takes precedence over the item price assigned to the item

In summary, item pricing uses the following hierarchy when ordering items via a barcode scanner or a PLU button, with quantity pricing overriding all other prices:

Quantity pricing

Fixed pricing

An event that changes the price level

Price level assigned in item maintenance

An event that changes the item price

Price assigned in item maintenance

QuickService Items Ordered from a Panel or Modifier Menu

The following rules apply to ordering items via a button or modifier menu:

Quantity Pricing overrides all other pricing methods.

Modifier menu radio buttons:

Button price at the modifier menu level overrides all pricing methods.

If you enable the item price, then the price assigned in item maintenance is used unless there is a price level assigned to the item, in which case the price level's price us used.� If a 'price level change' event occurs, this would in turn override the price level.� If a 'price change' event occurs, it would overwrite the item price.

If you assign a price level to an item on the modifier menu, then it takes precedence over both the item price and the price level assigned in item maintenance.� If a 'price level change' event occurs, it looks to see if the price level is assigned on the submenu or modifier menu in order to make the adjustment.

In summary, item pricing uses the following hierarchy when ordering items via a submenu or modifier menu, with quantity pricing overriding all other prices:

Quantity pricing

Price assigned to the modifier button

An event that changes the price level

Price level assigned to the modifier button

Price level assigned in item maintenance

An event that changes the item price

Price assigned in item maintenance

QuickService Items Ordered from a Barcode Scanner or a PLU Button

The following rules apply to ordering items via a barcode scanner or a PLU button:

Quantity pricing overrides all other pricing methods.

Barcode scanner and PLU input do not recognize the price configuration on buttons.

If you assign a price level to an item, then it takes precedence over the item price.� If a 'price level change' event occurs, then it takes precedence over the price level assigned to the item.� The item price is used if there is not a price level assigned to the item.� If an 'item price change' event occurs, then it takes precedence over the item price assigned to the item.

In summary, item pricing uses the following hierarchy when ordering items via a barcode scanner or a PLU button, with quantity pricing overriding all other prices:

Quantity pricing

Fixed pricing

An event that changes the price level

Price level assigned in item maintenance

An event that changes the item price

Price assigned in item maintenance

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1226

�

Aloha Application Software Relational Database Tables

Aloha Application Software Relational Database Tables

============================================================================

AKBID1227

Created: 21 July 2003

Updated: 17 December 2003

Reviewed: 17 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.0x � 5.3.x

Subject: Aloha Application Software Relational Database Tables

============================================================================

Summary

This document lists the Relational-Database (RDB) tables used by the ALOHA^� application software, each table's description, and whether they are used with QuickService or TableService.� Refer to document AKBID1030 for information on Grind (GND) files, and AKBID1081 for more information on Summary (SUM) files.

Information

Some tables might exist in both QuickService and TableService, even though only one of the two products actually uses the tables.� Tables in this document are attributed to the product only if they are actually used by the product.

��

Table

Description

QS

TS

Access

Access Levels

X

X

Aloha.ini

Configuration

X

X

AutoMenu

Auto Menu

-

X

AutoMenuDetail

Auto Menu Details

-

X

Availability

ALS Employee Availability

X

X

Button

Panel Buttons

X

X

CashAccount

Petty Cash Accounts

X

X

CashCard

Cash Cards

X

X

Category

Categories

X

X

CategoryItem

Category Items

X

X

ClockInMessage

Clock-In Message Definitions

X

X

ClockInMessageLine

Clock-In Message Content

X

X

Comp

Comps

X

X

CompositeRecipe

Quick Count Composite Item Recipes

X

X

CompositeTrackItem

Quick Count Composite Tracking Items

X

-

Concepts

Concepts

X

X

CorporateEvent

CDM Event Groups

-

X

CorporateEventSubscriber

CDM Event Group Subscriptions

X

X

DayPart

Day Parts

X

X

DayPartJobGroup

Day Part Job Groups

X

X

Drawer

Cash Drawers

X

X

DrinkDispener

Drink Dispensers

X

X

DsplyBrd

Display Boards

X

X

Employee

Employees

X

X

EmployeeI9

Employee I9 Information

X

X

EmployeeJob

ALS Employee Policies

X

X

EmployeeType

ALS Employee Types

X

X

ExceptionModifier

Exception Modifier Groups

X

X

ExceptionModifierItem

Exception Modifier Group Items

X

X

FixedPricing

Fixed Item Pricing

-

X

FlexTax

Flex Taxes

X

X

GiftCertificate

Basic Gift Certificates

X

X

GiftCertificateGroup

Basic Gift Certificate Group Definitions

X

X

GPRedem

TGI Friday's Gold Points Redeemed

-

X

GuestCheckInfo

Guest Check Information

X

X

GuestCheckInfoMessages

Guest Check Information Message Content

X

X

GuestCheckInfoTitle

Guest Check Information Message Titles

X

X

HouseAccount

House Accounts

X

X

Item

Items

X

X

ItemGrp

Item Size Groups

X

-

ItemGrpList

Item Size Group List

X

-

ItemModifier

N/A

-

-

JobCode

Job Codes

X

X

JobRevenue

Job by Revenue Center

X

X

Label

Labels

X

X

LaborCategory

Labor Groups

X

X

LaborCategoryJob

Labor Group Job Code Assignments

X

X

LaborCategorySale

Labor Group Sales Category Assignments

X

X

LaborPeriod

ALS Labor Periods

X

X

LaborPeriodLimit

ALS Labor Period Limits

X

X

LaborPeriodTime

ALS Labor Period Times

X

X

MemberHoldReasons

Membership Hold Reasons

X

X

Membership

Memberships

-

X

Menu

Menus

-

X

MenuReroute

Menu-level Tax and Printer Reroutes

-

X

MenuSubMenu

Menu Submenu Assignments

-

X

MessageLine

Main Screen Message Content

X

X

Messages

Main Screen Messages

X

X

Modifier

Modifier Groups

X

X

ModifierItem

Modifier Group Item Assignments

X

X

MultCurrency

Foreign Currencies

X

X

NoSaleReason

No Sale Reasons

X

X

Occasion

Occasions

X

X

OccasionCategory

Occasion Categories

X

X

OrderMode

Order Modes

X

X

OtherWages

Other Wages

X

X

PackagePromo

Chuck E. Cheese's Package Promos

X

-

PackagePromoComponent

Chuck E. Cheese's Package Promo Components

X

-

PackagePromoGroupComponent

Chuck E. Cheese's Package Promo Group Components

X

-

PackagePromoGroupPricing

Chuck E. Cheese's Package Promo Group Pricing

X

-

Panel

Panels

X

X

PCPriceLevelDetail

Price Change Price Level Detail

X

X

PCPromoDetail

Price Change Promotion Detail

X

X

Performance

Performance Measures

X

X

PollEvent

Customer Poll Events

X

X

PollEventFile

Customer Polls

X

X

PollEventSubscriber

Customer Poll Subscribers

X

X

PriceChange

Price Changes

X

X

PriceChangeItemDetail

Price Change Item Detail

X

X

PriceLevel

Price Levels

X

X

PrintData

N/A

-

-

Printer

Printers

X

X

PrinterGroup

Printer Groups

X

X

PrinterGroupPrinters

Printer Group Printer Assignments

X

X

ProBogo

BOGO-type Promotion Configurations

X

X

ProCombo

Combo-type Promotion Configurations

X

X

ProComboCat

Combo-type Promotion Category Configurations

X

X

ProCoupon

Coupon-type Promotion Configurations

X

X

ProjctnsCompositeTrackItem

Preparation Projections

X

X

ProjctnsTrackItem

Preparation Projection Tracking

X

X

Promotion

Promotions

X

X

ProNewPrice

New Price-type Promotion Configurations

X

X

ProNewPriceItem

New Price-type Promotion Item Configurations

X

X

ProQuick

Quick Combo-type Promotion Configurations

X

X

ProQuickChoice

Quick Combo-type Promotion Choice Configurations

X

X

ProQuickItem

Quick Combo-type Promotion Item Configurations

X

X

ProReduction

Reduction-type Promotion Configurations

X

X

PunchReason

Edit Punch Reasons

X

X

QuantityPricing

Quantity Pricing

X

X

Queue

Order Queues

X

X

QueueVideoReroute

Order Queue Remote Display Reroute Configurations

X

X

Reason

Void Reasons

X

X

Region

Regions

X

X

RegrindDetail

Regrind Dated Folders Information

X

X

RequirementRule

ALS Requirement Rules

X

X

Revenue

Revenue Centers

X

X

RoutingLevel

Routing Levels

X

-

RoutingLevelQueue

Routing Level Order Queue Configuration

X

-

Scale

Scales

X

X

Schedules

Schedule

X

X

ScheduleShift

ALS Shifts

X

X

ScheduleShiftTag

ALS Shift Tags

X

X

Screen

Screens

X

X

ScreenPanel

Screen Panels

X

X

SecurityLevel

Security Levels

X

X

SecurityLevelDetail

Security Level Details

X

X

ServerInfoMessage

Server Information Messages

X

X

ServerInfoMessageBullet

Server Information Message Bullets

X

X

ServerInfoMessageJob

Server Information Message Job Code Configurations

X

X

ServerInfoMessageLine

Server Information Message Content

X

X

SmartCard

Smart Cards

X

X

SpecialRequest

ALS Special Requests

X

X

SQLReport

SQL Reports

X

X

SQLReportParms

SQL Report Parameters

X

X

Store

Stores

X

X

StoreEdit

CDM Store Edits

X

X

StoreGroup

CDM Store Groups

X

X

StoreGroupMembers

CDM Store Group Members

X

X

SubMenu

Submenus

-

X

SubMenuItem

Submenu Item Assignments

-

X

Surcharge

Surcharges

X

X

Survey

Surveys

X

X

SurveyBanner

Survey Banners

X

X

SurveyFrequency

Survey Frequency

X

X

SurveyMessage

Survey Messages

X

X

Tab

Tables

-

X

TableDefinition

CDM Table Definitions

X

X

Tare

Tare Weights

X

X

Task

ALS Tasks

X

X

TaskType

ALS Task Types

X

X

Tax

Taxes

X

X

TaxArray

Tax Breakpoint Array Configuration

X

X

Tender

Payment Tenders

X

X

TenderValidation

Valid Tender Identifiers

X

X

Terminal

Terminals

X

X

TermService

Team Service Tip Distribution

-

X

TieredTax

Tiered Taxes

X

X

TrackItem

Quick Count Tracking Items

X

-

Version

Database Version Number

X

X

VideoDevice

Remote Display Devices

X

X

VideoGroup

Remote Display Groups

X

X

VideoGroupVideo

Remote Display Group Video Assignments

X

X

VideoKeypad

Remote Display Keypads

X

X

VideoQueue

Remote Display Queues

X

X

VolumeLevel

Volume Levels

X

-

WorkPolicy

Work Policies

X

X

Zap

Termination Reasons

X

X

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1030 Grind Database Contents

AKBID1042 Aloha Application Software Database Files

AKBID1081 Summary Process and Errors

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1227 access sequel server sql 7.0 sql 2000

style='mso-spacerun:yes'>� 2003

�

Demo both QS and TS with a Single Instance of Aloha Manager

Demo both QS and TS with a Single Instance of Aloha Manager

============================================================================

AKBID1228

Created: 4 August 2003

Updated: 4 August 2003

Reviewed: 19 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 5.2x � 5.3.x

Subject: Configuring QuickService and TableService on a Single Computer for Demonstration Purposes

============================================================================

Summary

This document explains how to configure a single instance of ALOHAMGR.EXE (Aloha Manager) to run both QuickService and TableService on a single computer for demonstrating the ALOHA^� application software QuickService and TableService products.� If you want to use separate instances of Aloha Manager run QuickService and TableService on a single computer for demonstration purposes, then refer to document AKBID1082 for more information.

The information in this document is not intended for use in a live restaurant.� It is intended for demonstration purposes only.

Information

Security Key Codes

You must use HASP^� security key activation codes from a key designed for use in both a QuickService and a TableService environment, such as a 'Dealer Super Key'.

Configure Your Computer and Install TableService

Configure your computer and install TableService using the appropriate Aloha Knowledge Base (AKB) document for your environment.� If you are using a stand-alone file server, then ensure that you use the AKB document that regards your operating system on a stand-alone file server.� If you are running both the Front-of-House (FOH) and the Back-of-House (BOH) on the same computer, then use the AKB document that regards your operating system on a file server/terminal.

Convert the BOH to Both QuickService and TableService

After you have installed TableService and everything is functioning properly, perform the following in order to convert the BOH to run both QuickService and TableService:

Shut down Aloha Manager and CTLSVR.EXE (Control Server).

Extract the contents of IBERQS.ZIP, GRINDQ.ZIP, and REPRINTQ.ZIP from the ALOHAQS folder on the Aloha Installation CD to the BIN folder on your file server.

Create a new flag file labeled QSTSBOTH in the Aloha application software folder on the file server (for example, D:\ALOHA\QSTSBOTH).

Restart Control Server and Aloha Manager.

Aloha Manager should display 'QuickService/TableService' in the title bar.� As you navigate through Aloha Manager, any settings using red text only apply to QuickService, settings using blue text only apply to TableService, and settings using black text apply to both QuickService and TableService.

Building a QuickService/TableService Menu

If you do not already have a menu database built for use with both QuickService and TableService, then you must build a new one, starting with either a QuickService-only database or a TableService-only database.� In general, it is not feasible to attempt to merge a QuickService-only database and a TableService-only database into a single QuickService/TableService database.

Grinding Data

If you are grinding TableService data, then Control Server automatically starts the TableService grind (GRIND.EXE).�

If you are grinding QuickService data, then you must manually create a flag file labeled FASTFOOD in the Aloha application software folder on the file server (for example, D:\ALOHA\FASTFOOD) in order to signal Control Server to start the QuickService grind (GRINDQ.EXE).� You must manually delete the FASTFOOD flag in order to Control Server to resume using GRIND.EXE for TableService data.

Extended Information

If you are not using a HASP security key, refer to document AKBID1173.

Caveats

The information in this document is not intended for use in a live restaurant.� It is intended for demonstration purposes only.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1010 Aloha Application Software System Environment Variables

AKBID1082 Separate QS and TS Installations on a Single Demo Computer

AKBID1099 Network Troubleshooting

AKBID1162 Microsoft Windows Service versus a Standard Application

AKBID1170 Multiple Version of Aloha on a Single Demo Computer

AKBID1173 Demo Aloha without a HASP Key

AKBID3169 KEY.TXT HASP Security Key Identification Files

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1082 demonstrate

�

Logic Controls Logic Net Kitchen Display System (Serial)

Logic Controls Logic Net Kitchen Display System (Serial)

============================================================================

AKBID1229

Created: 15 August 2003

Updated: 15 August 2003

Reviewed: 25 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

Subject: Using the Logic Net Kitchen Display System (Serial) with the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software supports the serial version of the Logic Controls, Inc., Logic Net^� Kitchen Display System (KDS).� The Logic Net KDS requires you to assign address numbers to each video controller and set the proper Microsoft^� Windows^� environment variables in order to interface it with the Aloha application software.

Information

Set the Video Device Type in the Aloha application software to IBM.� For additional information on configuring videos in the Aloha application software, refer to the Aloha Video User Manual.

When adjusting the Logic Net KDS settings, you must restart the Logic Net KDS components along with the Aloha application software.

Setting Device Address Numbers

You must configure each I/O device to use a separate address between 00 and 15.� The address matches the identification number you assigned to the video monitor in the Aloha application software Back-of-House (BOH).

After connecting all of the hardware, perform the following on each I/O device to assign an address to it:

1.        Press the reset button on the I/O device (or unplug the I/O device and plug it back in).

2.        As soon as the diagnostic menu appears, immediately press the down arrow on the bump pad.

3.        Select 'Address Setup' from the diagnostic menu.

4.        Set the address.

5.        Exit the diagnostic menu.

Environment Settings

The Aloha application software uses the IBMVIDEOS, IBMMODE, and IBMPORT environment variables to communicate with the Logic Net KDS.�

IBMVIDEOS enumerates the number of Logic Net KDS devices chained off the serial port.� For example, if video numbers one, two, and three are connected to the port, the IBMVIDEOS variable is the following:

SET IBMVIDEOS=1,2,3

If video numbers one, three, and five are connected to the port, the IBMVIDEOS variable is the following:

SET IBMVIDEOS=1,3,5

IBMMODE sets the video characters per line and number of lines on the monitor.� Mode 1 is 40x25, and Mode 3 is 80x25.� This is not typically used.

IBMPORT sets the serial port the Logic Net KDS is attached to.� For example, if the system uses port number two, the variable is the following:

SET IBMPORT=2

Extended Information

No information.

Caveats

When adjusting the Logic Net KDS settings, you must restart the Logic Net KDS components along with the Aloha application software.

============================================================================

See also:

Aloha Video User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1229 kds kvs

�

Adding Tips to Gift Card Payments

Adding Tips to Gift Card Payments

============================================================================

AKBID1230

Created: 5 September 2003

Updated: 22 April 2004

Reviewed: 22 April 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2.8.x � 5.3.x

Subject: Using AddGCTip.exe to Add Tips to Gift Cards in the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software supports adding tip to gift card payments using the AddGCTip.exe utility.� You can use AddGCTip.exe to apply tips to native Aloha eCards as well as third-party gift cards such as Valuelink and Paymentech.� This document explains how to configure and use AddGCTip.exe with the Aloha application software.

Information

A Brief Explanation of AddGCTip.exe

AddGCTip.exe communicates with the Aloha application software Front-of-House (FOH) using the Microsoft Component Object Model (COM) interface included in the Aloha application software.� Once you have applied the gift card payment, you can activate AddGCTip.exe in the FOH in order to add a gift card tip to the check.� AddGCTip.exe prompts you for a tip amount, and then adds the tip amount to the check via the COM interface.

Where to Obtain AddGCTip.exe

AddGCTip.exe resides in the Aloha application software BIN folder.� If AddGCTip.exe is not included in your BIN folder, contact the Aloha Customer Service Center (CSC) in order to obtain a copy.� Newer versions of the Aloha application software include AddGCTip.exe in the BIN folder.

How to Configure AddGCTip.exe in QuickService

Add a compatible version of AddGCTip.exe to the Aloha application software BIN folder if it does not already exist.

To enable the COM interface in the Aloha application software, open AlohaMgr.exe (Aloha Manager), and select Maintenance/Store Settings/System/Interfaces, and select Use FOH COM Interface.

Once you have enabled the COM interface, you can use Panel Editor to assign AddGCTip.exe to a FOH tender button.� Edit the button in Panel Editor that you want to use to initialize AddGCTip.exe, assign it to the Run Application function, enter AddGCTip.exe as the application to run, and select 'Pass Parameters'.

Refresh the system.

How to Configure AddGCTip.exe in TableService

Add a compatible version of AddGCTip.exe to the Aloha application software BIN folder if it does not already exist.

To enable the COM interface in the Aloha application software, open Aloha Manager, and select Maintenance/Store Settings/System/Interfaces, and select Use FOH COM Interface.

Once you have enabled the COM interface, you can assign AddGCTip.exe to a FOH tender button using TSButton.cfg.� Refer to document AKBID1185 for more information on configuring TSButton.cfg.� Use a command line similar to the following in TSButton.cfg in order to add a button for initializing AddGCTip.exe to the FOH tender screen:

2,0,21,Add GC\nTip,ADDGCTIP.EXE,1

Refresh the system.

AddGCTip.exe Usage

After you have applied the gift card payment in the FOH, you can activate AddGCTip.exe using the assigned button.� AddGCTip.exe prompts you for a tip amount, and then adds a gift card tip to the check via the COM interface.

When you launch AddGCTip.exe from the FOH, it will look for any gift card payments on the active check, and it will react accordingly:

-          If the check does not contain any gift card payments, AddGCTip.exe will state that there are not any gift card payments on the check.

-          If the check contains a single gift card payment, then AddGCTip.exe displays a prompt for the tip amount.

-          If the check contains two or more gift certificate payments, then you must first select the gift card payment prior to initializing AddGCTip.exe.

You can only apply one tip per gift card payment.

The tips appear on the check as a separate payment with a zero amount sale, but with the applied tip amount.� Since the amount is recognized as a tip, it is treated like any other non-cash tip in the Aloha application software.

Tips are processed as separate gift card transactions, which might subject the transaction to a processor fee.

You can adjust or delete gift card tips on open checks using Adjust Payment on the Close Check screen.� You can adjust or delete gift card tips on closed checks using the using Adjust Payments in the FOH Manager Functions.

Add GCTip.exe does not adhere to the maximum tip allowance configured for the tender.

Extended Information

Error Code 1157

If you receive error code 1157 in the FOH debout while attempting to use AddGCTip.exe, then you might not have all of the necessary .DLL files on the local terminal.�

If you are using Windows 95, Windows 98, or Windows Me, unzip WIN95DLL.ZIP and WIN95DLL2.ZIP from the ALOHATS folder on the Aloha Installation CD to the Windows SYSTEM folder.� Do not overwrite newer versions of the files.� You may have to restart the computer in MS-DOS^� mode to perform this step, since Windows might be using some of the files.

If you are using Windows NT, Windows 2000, Windows XP, or Windows Server 2003, unzip WINNTDLL.ZIP and WINNTDLL2.ZIP from the ALOHATS folder on the Aloha Installation CD into the Windows SYSTEM32 folder.� Do not overwrite newer versions of the files.� You might have to employ the SETUPSYS.EXE utility to perform this step, since Windows might be using some of the files.� Refer to document AKBID1012 for more information.

Error 0x80040150

If you receive an error in the debout stating 'ADDGCTIP failed to create IIberFuncs4, error 0x80040150', then the user does not have access to the Windows Registry or that the Registry is corrupt.

Automatic Gratuities

Automatic gratuities are applied to gift cards as a standard gift card tender transaction.� If you apply the gratuity to the check before applying the gift card payment, then the gratuity is included in the initial payment.� If you apply the gratuity after applying the gift card payment, then you must apply a second gift card payment for the amount of the gratuity.� In either case, you will not use AddGCTip.exe.

Caveats

No information.

============================================================================

See also:

AKBID1182 COM Interface Configuration

AKBID1185 Using TSButton.cfg to Launch Applications from TableService

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1230 80040150 add addgctip gc tip certificate giftcard

�

Masking Credit Card Numbers

Masking Credit Card Numbers

============================================================================

AKBID1231

Created: 9 December 2003

Updated: 11 December 2003

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.3.x � 5.4.x

Subject: Options for Masking Credit Card Number in the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software enables several options for masking credit card account numbers, which include no masking, partial masking, and full masking.� This document explains how to enable each type of masking on guest checks, credit card vouchers, and Back-of-House (BOH) reports.

This document only applies to Aloha versions 5.3.x and higher.� If you are using Aloha versions 5.2.x.x or lower, refer to documents AKBID3039, AKBID3040, and AKBID3041 for more information.

Information

The Aloha application software provides three global options for masking credit card numbers:

Always show the full credit card number.

Always mask the credit card number, except on the first credit card voucher.

Always mask the credit card number.

Open Aloha Manager and select Maintenance/Store Settings/Credit Card/Voucher Printing in order to access the global settings.�

These settings only apply to tenders when have been assigned a credit card type in the tender configuration.

The subsequent sections in this document explain how these settings behave in different parts of the Aloha application software.

Guest Checks and Credit Card Vouchers

The masking option you select in the global credit card configuration settings directly relates to how credit card numbers are displayed on guest checks (printed, on-screen, or re-printed) and credit card vouchers.

If you enabled masking, then by default, the Aloha application software masks all but the last four digits of the credit card number.� The last four digits enable a reference point for the applied credit card.� You can configure which digits are masked by configuring the CCnMASK in the ALOHA.INI.

To change the masked digits, add CCnMASK=z to the ALOHA.INI, if it does not already exist.� Replace n with the number of digits in the credit card number.� You will need a different variable for credit card length.� Replace z with the digits to mask, using X to mask the digit and O to display the digit.

For example, Visa credit card numbers range from 13 to 16 digits.� To mask only the first four digits on all Visa credit cards (or any credit card number of 13 to 16 digits in length), you would add the following variables to the ALOHA.INI:

CC13MASK=XXXXOOOOOOOOO

CC14MASK=XXXXOOOOOOOOOO

CC15MASK=XXXXOOOOOOOOOOO

CC16MASK=XXXXOOOOOOOOOOOO

Grind Files and BOH Reports

The credit card number is always masked in the Grind files and BOH reports, regardless of the global credit card configuration settings, unless you select 'Disable Masking in Grind Files' in the specific tender's configuration.� Once you have disabled masking for the specific credit card tender, the credit card number is masked according to the masking configuration in the global credit card configuration settings.

As with guest check and credit card vouchers, the Aloha application software masks all but the last four digits, and you can configure which digits are masked by editing the CCnMASK variables in the ALOHA.INI.

The grind process reads the credit card masking configuration from the DATA folder, not the dated folder.� If you need to unmask credit cards from a historical date, then first you must first ensure that the configuration files (ALOHA.INI and TDR.DBF) in the DATA folder disable masking in the grind files and in the global credit card configuration, and then regrind the specific date.�

This process will unmask the credit card numbers for the current data as well as any additional historical data that you regrind.� Ensure that you have re-enable credit card masking in the current configuration once you have performed a regrind of the dated folder.

EDC Report

By default, the EDC report masks digits six through nine of the credit card number.� To disable the mask, add the following line to the [REPORT] section of the EDC.INI file, if it does not already exist:

PRINTFULLCARDNUMBER=1

EDC Files

The credit card number in the EDC files (TXN, .REQ, .HLD, .ANS, and .STL) is encrypted, but Aloha Technologies uses the CARDMASK field to supply technicians with the last four digits of the credit card number as a reference for troubleshooting.

Extended Information

Suppressing the Credit Card Expiration Date

You can suppress the credit card expiration date on guest checks by selecting the credit card tender in Aloha Manager/Maintenance/Payments/Tenders, selecting the Type subtab, and clearing the option for Print Expiration.

You can suppress the credit card expiration date on credit card chits by opening Aloha Manager, selecting Maintenance/Store Settings/Credit Card/Voucher Printing, and selecting the option for 'Do Not Print Expiration Date'.

Caveats

This document only applies to Aloha versions 5.3.x and higher.� If you are using Aloha versions 5.2.x.x or lower, refer to document AKBID3039, AKBID3040, and AKBID3041 for more information.

These settings in this document only apply to tenders when have been assigned a credit card type in the tender configuration.

============================================================================

See also:

AKBID3039 Masking the Credit Card Numbers on the Guest Check

AKBID3040 Show or Hide Credit Card Numbers on EDC Report

AKBID3041 Masking the Credit Card Number on the Voucher

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1231 display hide remove show

�

Formatting Seat Numbers on Kitchen and Bar Chits

Formatting Seat Numbers on Kitchen and Bar Chits

============================================================================

AKBID1232

Created: 11 December 2003

Updated: 11 December 2003

Reviewed: 11 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 5.2.8.x � 5.3.x

Subject: Formatting Seat Numbers on Kitchen and Bar Chits

============================================================================

Summary

The ALOHA^� application software can automatically include seat information on kitchen and bar (remote) chits if you have enabled Pivot Seating (refer to the Aloha TableService User Manual for more information).� This document explains the different formats available for printing the seat numbers on remote chits.

Information

Disable Seat Information on Remote Chits

If you do not want to print any seat information on remote chits, then open Aloha Manager, select the printer in Maintenance/Hardware/Printers, select the Options subtab, and select 'Never print seat information'.

Default Seat Information

If you disable the item consolidation options in Aloha Manager/Maintenance/Store Settings/Printing-Chits/Appearance, and you disable both 'Never print seat information' and 'Always sort by seat number' in Aloha Manager/Maintenance/Hardware/Printers/Options, then the remote chits will appear similar to the following:

S1 House Salad

S1�� Ranch

S1 Steak

S1�� Med

S2 House Salad

S2�� Honey Mustard

S2 Chix Tenders

Consolidating Items

If you enable the item consolidation options in Aloha Manager/Maintenance/Store Settings/Printing-Chits/Appearance, then the seat information will print as a modifier to each item and appear similar to the following:

2 House Salad

�� 1 Ranch

�� ^^^Seat 1^^^

�� 1 Honey Mustard

�� ^^^Seat 2^^^

Steak

�� Med

�� ^^^Seat 1^^^

Chix Tenders

^^^Seat 2^^^

Always Sorting by Seat Numbers

If you enable Aloha Manager/Maintenance/Hardware/Printers/Options/'Always sort by seat number', it will override the consolidation options described in the Consolidating Items section of this document, and remote chits will separate each seat, similar to the following:

*** Seat 1 ***

House Salad

�� Ranch

Steak

�� Med

*** Seat 2 ***

House Salad

�� Honey Mustard

Chix Tenders

'Always sort by seat number' overrides the consolidation options described in the Consolidating Items section of this document.

Extended Information

No information.

Caveats

'Always sort by seat number' overrides the consolidation options described in the Consolidating Items section of this document.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1232 seats

style='mso-spacerun:yes'>� 2003

�

Select Electronics OAsys Kitchen Display System

Select Electronics OAsys Kitchen Display System

============================================================================

AKBID1233

Created: 15 December 2003

Updated: 15 December 2003

Reviewed: 15 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.0x � 5.3.x

Subject: Using the Select Electronics OAsys Kitchen Display System with the Aloha Application Software

============================================================================

Summary

The ALOHA^� application software supports the Select Electronics OAsys Kitchen Video System.� This document supplemental configuration information, but you must also refer to the Aloha RDS User Manual and the Select Electronics OAsys User Manual for the most complete configuration information.

Refer to document AKBID1122 if you are using the Select Electronics SV2000 KVS.

Information

OAsys Kitchen Video System Configuration

Using the information in the Select Electronics OAsys User Manual available at http://www.selectelectronics.com, configure the video ID numbers for each video card and bump bar, and configure the communication settings to RS232 and 28,800 baud.

Aloha Video Configuration

Using the information in the Aloha RDS User Manual, configure the RDS options, groups, queues, devices, and keypads in the Aloha POS system, and assign the video groups to items.

Environment Settings

The Aloha application software uses the SVIDEOS, SVMODE, and SVPORT environment variables to communicate with the OAsys system, and you must configure these variables on each terminal to which an OAsys system is connected.�

SVIDEOS enumerates the number of video card IDs that included in the OAsys system connected to the serial port.� For example, if video numbers one, two, and three are connected to the port, the SVIDEOS variable is the following:

SET SVIDEOS=1,2,3

If video numbers one, three, and four are connected to the port, the SVIDEOS variable is the following:

SET SVIDEOS=1,3,4

SVMODE sets the video characters per line and number of lines on the monitor.� Mode 1 is 40x25, and Mode 3 is 80x25.� This is not typically used.

SVPORT sets the serial port to which the OAsys system is attached.� For example, if the OAsys system is connected port number two, the variable is the following:

SET SVPORT=2

Extended Information

No information.

Caveats

No information.

============================================================================

See also:

Aloha Video User Manual

AKBID1122 Select Electronics Video

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 1233

style='mso-spacerun:yes'>� 2003

�

Configuring Aloha to Conform with the Visa CISP Guidelines

Configuring Aloha to Conform with the Visa CISP Guidelines

============================================================================

AKBID1234

Created: 17 December 2003

Updated: 18 December 2003

Reviewed: 18 December 2003

Microsoft Windows Versions: Windows NT, Windows 2000, Windows XP, Windows Server 2003

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 5.2.7.x � 5.3.x

Subject: Configuring the Aloha Application Software to Conform with the Visa CISP Guidelines

============================================================================

Summary

The ALOHA^� application software provides security and configuration options that support the Visa U.S.A. Cardholder Information Security Program (CISP).� This document provides tips for configuring Microsoft^� Windows^� and the Aloha application software in order to conform the guidelines set forth by the CISP.� Refer to web page http://www.usa.visa.com/cisp for more information on the CISP.

The information in this document only summarizes portions of the information available in the CISP that directly pertain to configuring the Aloha application software.� Aloha Technologies strongly recommends that you review the CISP in whole in order to verify that you meet all of the security requirements.

This information in this document only applies to Windows NT^�, Windows 2000, Windows XP, and Windows Server 2003.� Windows 95, Windows 98, and Windows Millennium Edition (Me) do not enable the necessary security functionality required by the CISP.

Information

Stored Data Protection

You can use the Local Security Policy in Windows in order to restrict file-level access to current and historical information by disabling access to the Aloha folder structure, and you can use the Back Office Security Levels to restrict access in the Aloha application software, such as EDC and Back-of-House (BOH) reports.� Furthermore, Aloha versions 5.3.x and higher encrypt the credit card information stored in the EDC communication and storage files.

You should limit the amount of historical credit card data that you keep for reference (for example, EDC settlement files) to that which is required by local laws. �Cardholders generally have 90 days to dispute a charge. Following this period, you should purge the credit card information.� At the time of this writing, the Aloha application software does not enable you to configure an automatic purge, so you must manually purge the data once it has expired.

Computer Access

Each user must have a unique Windows login.� You should train users to log out of Windows when not using the computer, and also configure the Windows screensaver to automatically lock the computer after a time of activity in case the user fails to log out.� You should also disable any default users, passwords, and automatic logins provided by hardware and software vendors.

You must also assign a unique BOH login for each Aloha user.� This enables you to track each user's activity.� You should disable any default users and passwords provided by Aloha Technologies.

You can use the Windows Local Security Policy and various audit logs provided by Windows, hardware such as routers, and third-party software in order to further enhance and track activity on the computer.� Ensure that you restrict access to view or delete the audit logs, including the Debugging-Output-Files (debouts) created by the Aloha application software.

Customer Receipts and Credit Card Vouchers

You should mask the credit card information printed on customer receipts and credit card vouchers.� Refer to document AKBID1231.

Firewall Protection

Install and maintain a firewall in order to prevent external computers from accessing cardholder information.� Limit traffic from un-trusted networks to web protocols, system administration protocols, and other protocols required for business. �You should disable all other traffic in your router configuration.

Also implement Internet Protocol (IP) masquerading in order to prevent internal addresses from being translated and revealed on the internet.

Security Patches

Always update the security patches for all installed software within one month of release.� Ensure that you test all patches prior to deploying them.

Antivirus

Install an anti-virus application and configure a system of updating the virus definitions on a regular basis.

Extended Information

No information.

Caveats

The information in this document only summarizes portions of the information available in the CISP that directly pertain to configuring the Aloha application software.� Aloha Technologies strongly recommends that you review the CISP in whole in order to verify that you meet all of the security requirements.

This information in this document only applies to Windows NT, Windows 2000, Windows XP, and Windows Server 2003.� Windows 95, Windows 98, and Windows Millennium Edition (Me) do not enable the necessary security functionality required by the CISP.

============================================================================

See also:

AKBID1231 Masking Credit Card Numbers

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1234

style='mso-spacerun:yes'>� 2003

�

Moving a CIM SQL Database to a New File Server

Moving a CIM SQL Database to a New File Server

============================================================================

AKBID1236

Created: 8 March 2004

Updated: 8 March 2004

Reviewed: 8 March 2004

Microsoft^� Windows^� Versions: Windows NT^�, Windows 2000, Windows XP, Windows Server 2003

Aloha Products: BackOffice

Aloha POS Versions: 5.2x � 5.3.x

Subject: Migrating the CIM SQL Database from One File Server to Another File Server

============================================================================

Summary

Moving the ALOHA^� Customer-Information-Management (CIM) database from one file server to another requires you to follow a specific procedure in order to successfully move the database.� In general, you must 'detach' the database from SQL Server on the source file server, copy the database file to the target file server, and 'attach' it to SQL Server on the target file server.

Information

While you can copy a database from MSDE or SQL Server 7.0 to MSDE, SQL Server 7.0 or SQL Server 2000, you can not copy a database from SQL Server 2000 to either MSDE or SQL Server 7.0.

The procedure detailed in this document assumes that you will no longer run the CIM database on the source server. As such, certain steps in this procedure will disable the source file server's ability to run the CIM database.� If this is not your intent, you must follow a different procedure � please contact your CIM support organization for more information.

Locating the CIMData folder

The CIM database is stored in a folder labeled CIMData.� This folder typically resides within SQL Server's 'Data' folder.� The following table lists the location of the CIMData folder for default installations of the currently supported SQL Server products.

Product

Default location of CIMData folder

MSDE or SQL Server 7.0��

C:\MSSQL7\Data\CIMData

SQL Server 2000

C:\Program Files\Microsoft SQL Server\MSSQL\Data\CIMData

Moving the Database

Perform the following to move the CIM database from one file server to another:

On the target file server, if you are not using MSDE, then you must install� SQL Server 7.0 or SQL Server 2000.

On the target file server, run DBInstall.exe from the CIM folder on the Aloha installation CD to completion in order to configure the file server to run the CIM database properly, and install a demonstration version of the CIM database.� If you did not previously install SQL Server, then DBInstall.exe will also install MSDE.

On the target file server, open a command prompt window and enter the following commands:

osql �Usa� (Ensure that you capitalize the 'U' in 'Usa'.� When you are prompted for the password, enter the sa user's password for this file sever.� If you do not know the password, try leaving the password blank and pressing Enter.)

1> use msdb

2> go

1> sp_detach_db CIMData

2> go

1> quit

�

On the source file server, open a command prompt and enter the following commands:

osql �Usa� (Ensure that you capitalize the 'U' in 'Usa'.� When you are prompted for the password, enter the sa user's password for this file sever.� If you do not know the password, try leaving the password blank and pressing Enter.)

1> use msdb

2> go

1> sp_delete_job �CIMData Nightly Processing�

2> go

1> sp_delete_job �CIMData_Daily_Backup�

2> go� (This will fail if you did not enable daily backups during DBInstall on this system.)

1> sp_detach_db CIMData

2> go

1> use master

2> go

1> drop procedure CIMData_AutoStart

2> go

1> quit

Copy the CIMData_Data.mdf file from the CIMData folder on the source file server to the CIMData folder on the target file server, replacing the existing copy on the target file server.

Delete the CIMData_Log.ldf file from the CIMData folder on the target file server.

On the target file server, open a command prompt and enter the following commands:

osql �Usa� (Ensure that you capitalize the 'U' in 'Usa'.� When you are prompted for the password, enter the sa user's password for this file sever.� If you do not know the password, try leaving the password blank and pressing Enter.)

1> use msdb

2> go

1> sp_attach_db CIMData, �c:\mssql7\data\cimdata\cimdata_data.mdf�� (You must replace the name of the file in quotes with the actual path to the database file that you copied in step five.� The example path given is the default path for MSDE and SQL Server 7.0 installations.)

2> go

1> quit

On the source file server, delete the CIMData folder and delete any CIM database backup files (found in the SQL Server's 'Backup' folder).

Run the SQL Server Utilities on any workstation in which you have installed the CIM application and change the Database Server Name (via the Utilities/Configuration screen) to the name of the target file server.

Extended Information

No information.

Caveats

While you can copy a database from MSDE or SQL Server 7.0 to MSDE, SQL Server 7.0 or SQL Server 2000, you can not copy a database from SQL Server 2000 to either MSDE or SQL Server 7.0.

The procedure detailed in this document assumes that you will no longer run the CIM database on the source server. As such, certain steps in this procedure will disable the source file server's ability to run the CIM database.� If this is not your intent, you must follow a different procedure � please contact your CIM support organization for more information.

============================================================================

See also:

AKBID1180 Moving BackOffice Data

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 1236 mas meal accountability system

�

Exact and Next Dollar Tenders

Exact and Next Dollar Tenders

============================================================================

AKBID3001

Created: 23 March 2000

Updated: 13 December 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.8x � 5.3.x

============================================================================

The ALOHA^� application software enables you to set cash tenders to apply the exact dollar amount or the next dollar amount to guest checks.� These settings are available in QuickService versions 3.8x and higher, and in TableService versions 4.2x and higher.

To set a cash tender to apply the exact dollar amount, set the Default Amount to '�2.00'.

To set a cash tender to apply the next dollar amount, set the Default Amount to '�1.00'.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected]

Additional query words: 3001 whole

Windows 95 Auto Scandisk

Windows 95 Auto Scandisk

============================================================================

AKBID3002

Created: 30 March 2000

Updated: 8 May 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: Windows 95

ALOHA^� Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

If you improperly shut down Microsoft^� Windows^� 95, then Windows prompts you to run Scandisk displays the next time Windows restarts.

To automatically run Scandisk without user intervention, perform the following:

1.        Open Explorer and select View/Options.�

2.        Select 'Show All Files'.

3.        Edit C:\MSDOS.sys using Notepad and add AutoScan=2 to the [Options] section.

4.        Download ScanDisk.zip from the Aloha Technologies FTP site.� Extract the ScanDisk.ini to the Windows Command folder (overwrite the existing file) to instruct Windows to correct Scandisk errors without user intervention.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3002

Editing the Check and Queue Sizes

Editing the Check and Queue Sizes

============================================================================

AKBID3003

Created: 30 March 2000

Updated: 6 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

ALOHA^� Products: QuickService

Aloha POS Versions: 3.8x � 5.0x

============================================================================

To edit the size and position of the QuickService Open Check and Order Queue from inside the Panel Editor, close Maintenance or Aloha Manager, and edit PNL.DBF with database editing software.

The Order Queue ID is 9800, and the Open Check ID is 9900.� Set the TEMPLATE, FIXEDPOS, and FIXEDBTNS fields to 'N', exit the editor, and reopen Maintenance or Aloha Manager.

Once you have set the new sizes and positions, set the fields back to 'Y'.

============================================================================

See also:

Aloha QuickService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3003

The File Formerly Known as BOHSEC

The File Formerly Known as BOHSEC

============================================================================

AKBID3004

Created: 31 March 2000

Updated: 6 September 2002

Reviewed: 3 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The 'File Formerly Known as BOHSEC' file is the Back-of-House (BOH) security file from previous versions (versions 4.4x and lower) of the ALOHA^� application software.� The contents are imported into SECLVL.DBF and SECLVLDT.DBF, so the file is not longer needed, and you can remove it.�

If the BOHSEC file exists along with the 'File Formerly Known as BOHSEC' file, the BOH passwords are deleted after End-of-Day (EOD) process (refer to document AKBID1015) since BOHSEC is again converted to SECLVL.DBF and SECLVLDT.DBF files.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1015 EOD Process and Errors

AKBID1042 Aloha Application Software Database Files

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected]

Additional query words: 3004 lose lost

Foreign Tenders

Foreign Tenders

============================================================================

AKBID3005

Created: 4 April 2000

Updated: 26 May 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

Adding foreign tenders to the ALOHA^� application software requires two steps:

1.        Open Aloha Manager, and select Maintenance/Payments/Foreign Currencies to create the foreign currency.

2.        Open Aloha Manager, and select Maintenance/Payments/Tenders to create the foreign tender.� Assign the foreign currency to the foreign tender under the Type subtab.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3005

Include Comps or Promos in Net Sales

Include Comps or Promos in Net Sales

============================================================================

AKBID3006

Created: 4 April 2000

Updated: 29 August 2001

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

To include Comps or Promos in the Net Sales figured in the ALOHA^� application software reports, open Aloha Manager, and select Maintenance/Store Settings/Financials/Reports.� Select 'Include Comps In Net Sales' and/or 'Include Promos In Net Sales'.

These setting do not affect the Back-of-House (BOH) Labor Reports, the Front-of-House (FOH) server checkout, or the FOH clock-out chits.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3006 nethascomps nethaspromos

Manually Update the HOUSEnn File

Manually Update the HOUSEnn File

============================================================================

AKBID3007

Created: 31 March 2000

Updated: 20 December 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

You can update the ALOHA^� application software HOUSE32 or HOUSE50 house account file by using the following command line with GRIND.EXE:

GRIND.EXE /DATE DATA /HOUSE <yyyymmdd> <yyyymmdd>

This (re)posts transactions for the specified date range, but double-posts transactions if they already exist.

The DATE flag points to the DATA folder so the Aloha application software can verify the database version.� Transactions residing in the DATA folder are not included in the Grind results.

============================================================================

See also:

AKBID1010 Aloha Application Software System Environment Variables

AKBID1016 Grind Process and Errors

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3007 activity rebuild recreate regrind

OK File

OK File

============================================================================

AKBID3008

Created: 29 March 2000

Updated: 3 September 2002

Reviewed: 10 February 2004

Microsoft^� Windows^� Versions: All

ALOHA^� Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

============================================================================

When IBER.EXE or IBERQS.EXE displays 'Waiting for system configuration files to complete' for an extended period, check for the existence of an OK file in the DATA folder on the file server.�

If an OK file does not exist, create an OK file by typing the following from a command prompt on the file server:

ECHO 1 > %IBERDIR%\DATA\OK

The OK file signals the Front-of-House (FOH) terminals that the data on the file server (or a FOH terminal acting as the file server) is ready for use by the FOH.

============================================================================

See also:

AKBID1107 Aloha Application Software Fault Tolerance Functionality

AKBID3013 Sub-Folders Inside System Folders

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3008

CTLSVR.EXE Registry Variables

CTLSVR.EXE Registry Variables

============================================================================

AKBID3009

Created: 31 March 2000

Updated: 8 May 2002

Reviewed: 3 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The ALOHA^� application software stores CTLSVR.EXE (Control Server) command-line variables in the Microsoft^� Windows^� Registry.� Perform the following to view or edit the Control Server command-line variables in the Microsoft Windows Registry:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_CLASSES_ROOT\AppId\{81DD90A1-CF22-11D1-A84F-0080AD1C6910}.

3.        Then double-click AlohaCtlSvrParameters and view or edit the command-line variables in the Value Data.

4.        Select Registry/Exit to exit the Windows Registry Editor.

5.        Restart Windows.�

============================================================================

See also:

AKBID1010 Aloha Application Software System Environment Variables

AKBID1019 Manually Registering and Un-registering Aloha Applications

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3009 settings

EDCSVR.EXE Registry Variables

EDCSVR.EXE Registry Variables

============================================================================

AKBID3010

Created: 31 March 2000

Updated: 8 May 2002

Reviewed: 3 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

ALOHA^� application software stores EDCSVR.EXE (EDC Server) command-line variables in the Microsoft^� Windows^� Registry.� Perform the following to view or edit the EDC Server command-line variables in the Windows Registry:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that might require the reinstallation of the operating system.� Use this tool at your own risk.�

1.        Select Start/Run, type REGEDIT, and click OK to open the Windows Registry Editor.

2.        Path out HKEY_CLASSES_ROOT\AppId\{583B6E82-64F1-11D1-8EF3-0040054AB0A4}.

3.        Double-click AlohaEdcSvrParameters and view or edit the command-line variables in the Value Data.

4.        Select Registry/Exit to exit the Windows Registry Editor.

5.        Restart Windows.

============================================================================

See also:

AKBID1010 Aloha Application Software System Environment Variables

AKBID1019 Manually Registering and Un-registering Aloha Applications

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3010 iberdir

OLK Files

OLK Files

============================================================================

AKBID3011

Created: 31 March 2000

Updated: 6 February 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.8x � 5.3.x

============================================================================

.OLK files, found in the ALOHA^� application software DATA folder, are created when a check is accessed by a user.� The file is named by the check number, and has an .OLK (order lock) extension.

If an .OLK file exists for a check, that check is currently in use and is not accessible by other employees.

============================================================================

See also:

Aloha QuickService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3011

LCK Files

LCK Files

============================================================================

AKBID3012

Created: 31 March 2000

Updated: 6 February 2001

Reviewed: 18 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

.LCK (lock) files, found in the ALOHA^� application software DATA folder, are created when an employee is logged in to the system or if a manager is accessing an employee's checks.� The file is labeled according to the employee number, and it has an .LCK extension.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID3057 Employee Locked on Another Terminal

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3012

style='mso-spacerun:yes'>� 2003

Sub-folders Inside System Folders

Sub-folders Inside System Folders

============================================================================

AKBID3013

Created: 31 March 2000

Updated: 23 October 2001

Reviewed: 10 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

============================================================================

If IBER.EXE or IBERQS.EXE displays 'Waiting for system configuration files to complete' for an extended period, check for the existence of subfolders inside the BIN, DATA, BMP (versions 5.0x or lower) or RECIPE folders on the file server and terminals.� The ALOHA^� application software versions 5.2x and higher compensate for subfolders within the BMP folder in order to enable multi-resolution bitmaps (refer to document AKBID1201).

The Aloha application software does not function properly with folders within these folders.� Reviewing the debugging output files (debouts) will display the root of the problem.

============================================================================

See also:

AKBID1107 Aloha Application Software Fault Tolerance Functionality

AKBID1201 Multi-resolution Bitmap Folders

AKBID3008 OK File

AKBID3096 Synchronization of Data Fails

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3013 copy copying fail failing fails subdirectories subdirectory synchronizing

Cashier Guest Counts

Cashier Guest Counts

============================================================================

AKBID3014

Created: 30 March 2000

Updated: 20 July 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

If the cashier job code also has Bartender enabled, the guest counts entered by the server do not carry over when the Get Check function is used by the cashier.

Either clear the Bartender option from the cashier job code or enable Guest Counts for bartenders.

============================================================================

See also:

AKBID1053 TableService Order Entry Job Code Options

AKBID1086 Get Check versus Transfer Check

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3014

Softkey Upgrades

Softkey Upgrades

============================================================================

AKBID3015

Created: 30 March 2000

Updated: 16 April 2003

Reviewed: 11 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.246 � 5.3.x

============================================================================

Check if the following is true if ALOHA^� application software soft-security-key (softkey) upgrades do not work properly:

1.        You are using CTLSVR.EXE (Control Server) is 4.246f or higher.

2.        You correctly entered the HASP^� security key activation codes.

3.        The upgraded HASP security key activation codes are not for a different key.

4.        Control Server is running.

5.        You have correctly set the LOCALDIR system environment variable in the Front-of-House.

6.        The ALOHA.INI (with the new HASP security key activation codes) has propagated to the terminals.

7.        Aloha Technologies upgraded the HASP security key activation codes to the correct options.

8.        You have installed the HASP security key driver.

9.        If the FOH is displaying an error stating 'Wrong Security Key', ensure that you have restarted Control Server since updating the new HASP security key activation codes.� If you have not done so, then the BOH is broadcasting one set of codes while the FOH is reading a different set of codes from the ALOHA.INI.

============================================================================

See also:

AKBID1112 HASP Key Troubleshooting

AKBID1163 FOH HASP Key Expiration

AKBID3016 HASP Driver

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3015 soft

Manual HASP Driver Installation and Removal

Manual HASP Driver Installation and Removal

============================================================================

AKBID3016

Created: 30 March 2000

Updated: 29 January 2004

Reviewed: 29 January 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

To remove the ALOHA^� application software HASP^� security key driver, type the following from a command line and restart the computer:

%IBERDIR%\BIN\HINSTALL -R -KP -ALLDRV

If HINSTALL.EXE does not already reside in the BIN folder, you can extract it from \ALOHATS\HINSTALL.ZIP on Aloha Installation CDs for versions 5.2.x.x and lower, or copy it from the \MISC\HASP folder on Aloha Installation CDs for versions 5.3.x and higher.� The Aloha application software installs the HASP security key driver automatically during the set up process, unless you select the 'Demo' option.

To install the HASP Aloha application software security key driver, type the following from a command line and restart the computer:

%IBERDIR%\BIN\HINSTALL �I

If errors persist on Microsoft^� Windows NT^�, Windows^� 2000, Windows XP, or Windows Server 2003 computers, rename the HASPNT.SYS file in the Windows SYSTEM32 folder, and reinstall the HASP driver.

If you receive an error stating 'Operation failed, some processes accessing the driver are open', ensure that you have disabled all Aloha software applications, including BackOffice applications.� If this error occurs when the computer is restarting following the HASP driver installation, ensure that there are no Aloha software applications that are starting at the same time (for example, BackOffice interfaces).

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1112 HASP Key Troubleshooting

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3016 hinstall

Adjust Control and Maintenance Window Sizes

Adjust Control and Maintenance Window Sizes

============================================================================

AKBID3017

Created: 30 March 2000

Updated: 8 May 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: All

ALOHA^� Products: QuickService, TableService

Aloha POS Versions: 3.5x � 4.4x

============================================================================

To adjust the Control and Maintenance window sizes, exit Control and Maintenance, and edit the WIN.INI located in the Microsoft^�Windows^� folder.� Navigate to the [Ibertech] section and change the following variables:

MntWidth=n adjusts the Maintenance window width in pixels.

MntHeight=n adjusts the Maintenance window height in pixels.

CtlWidth=n adjusts the Control window width in pixels.

CtlHeight=n adjusts the Control window height in pixels.

Save and close the WIN.INI, and restart Control and Maintenance.

============================================================================

See also:

AKBID3018 Adjust Control and Maintenance Window Positions

AKBID3019 Control not Responding on Task Bar

AKBID3020 Adjust Control and Maintenance Window Timeouts

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3017

Adjust Control and Maintenance Window Positions

Adjust Control and Maintenance Window Positions

============================================================================

AKBID3018

Created: 30 March 2000

Updated: 5 May 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha^� Products: QuickService, TableService

Aloha POS Versions: 3.5x � 4.4x

============================================================================

To adjust the Control and Maintenance window positions, exit Control and Maintenance, and edit the WIN.INI in the Microsoft^�Windows^� folder.� Navigate to the [Ibertech] section, and change the following variables:

MntX=n sets the X (horizontal) coordinate of the upper left corner of the Maintenance window in pixels.

MntY=n sets the Y (vertical) coordinate of the upper left corner of the Maintenance window in pixels.

CtlX=n sets the X (horizontal) coordinate of the upper left corner of the Control window in pixels.

CtlY=n sets the Y (vertical) coordinate of the upper left corner of the Control window in pixels.

Save and close the WIN.INI.

Restart Control and Maintenance.

============================================================================

See also:

AKBID3017 Adjust Control and Maintenance Window Sizes

AKBID3019 Control not Responding on Task Bar

AKBID3020 Adjust Control and Maintenance Window Timeouts

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected]

Additional query words: 3018 location

Control not Responding on Task Bar

Control not Responding on Task Bar

============================================================================

AKBID3019

Created: 30 March 2000

Updated: 6 October 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: All

ALOHA^� Products: QuickService, TableService

Aloha POS Versions: 3.5x � 4.4x

============================================================================

If the Control icon on the Microsoft^�Windows^� task bar does not respond to mouse clicks, right-click the icon and select Maximize.� Log in to Control, and exit Control.

Edit the WIN.INI file located in the Windows folder.� Navigate to the [Ibertech] section, and set CtlY, CtlX, CtlWidth, and CtlHeight variables each to 100.

Save and close the WIN.INI.� Reopen Control, and adjust the size to your preference.�

Close Control to save the size settings.

============================================================================

See also:

AKBID3017 Adjust Control and Maintenance Window Sizes

AKBID3018 Adjust Control and Maintenance Window Positions

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3019 minimize minimized open

Adjust Control and Maintenance Timeouts

Adjust Control and Maintenance Timeouts

============================================================================

AKBID3020

Created: 30 March 2000

Updated: 4 May 2001

Reviewed: No longer reviewed

Microsoft Windows Versions: All

ALOHA^� Products: QuickService, TableService

Aloha POS Versions: 3.5x � 4.4x

============================================================================

To adjust the Control and Maintenance timeouts, edit the WIN.INI in the Microsoft^�Windows^� folder, scroll to the [Ibertech] section and change the following variables:

MntTimeout=n adjusts the Maintenance timeout in seconds from 0-999.� '0' is no timeout.

CtlTimeout=n adjusts the Control timeout in seconds from 0-999.� '0' is no timeout.

Save and close the WIN.INI, and restart Windows.

============================================================================

See also:

AKBID3017 Adjust Control and Maintenance Window Sizes

AKBID3018 Adjust Control and Maintenance Window Positions

AKBID3019 Control not Responding on Task Bar

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3020 out time timeout

FOH Looping Batch File

FOH Looping Batch File

============================================================================

AKBID3021

Created: 31 March 2000

Updated: 25 August 2003

Reviewed: 5 March 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

Do not use the AUTOEXIT or REBOOTNT system environment variables on ALOHA^� application software terminals used as both the Back-of-House (BOH) file server and a Front-of-House (FOH) terminal, because the FOH might exit and restart Microsoft^� Windows^� following a refresh before the Aloha application software completes the refresh and deletes the STOP file.� This will result in the FOH not restarting without use intervention.

Instead, run the FOH from a looping batch file utilizing the WAIT.EXE utility (refer to document AKBID1012).� This way, a batch file restarts the FOH without restarting Windows, and it properly compensates for the time required for the refresh to complete.�

Label the batch file FOHSTART.BAT, place it in the root Aloha application software folder (for example, D:\ALOHA\FOHSTART.BAT), and include following lines in the batch file:

@ECHO OFF

:START

CLS

ECHO *** Do not close this batch file. ***

ECHO *** It is required to auto restart Aloha. ***

IF EXIST %LOCALDIR%\TMP\EXITING DEL %LOCALDIR%\TMP\EXITING

START /WAIT %LOCALDIR%\BIN\IBER.EXE

CLS

ECHO *** Waiting 10 seconds for refresh. ***

WAIT.EXE 10

GOTO START

This batch file performs the following functions:

1.        Disables unneeded text from appearing on the screen.

2.        Clears the screen.

3.        Displays a warning to not close the batch file, since it is essential for restarting the FOH.

4.        Deletes the EXITING file, if it exists.

5.        Starts the FOH using the START /WAIT command.� The START /WAIT command instructs the batch file to wait for the FOH to exit before proceeding to the next line in the batch file.� '/WAIT' is in no way connected with the WAIT.EXE utility described later in this document.� /WAIT is a standard Microsoft command-line variable, and WAIT.EXE is a utility supplied by Aloha Technologies.

6.        After the FOH exits, the batch file clears the screen.

7.        The batch file clears the screen, uses the WAIT.EXE utility (refer to document AKBID1012 for more information) to create ten-second pause while the BOH finishes the refresh procedure, and starts the batch file over again.

The batch file is always active on the FOH/BOH computer, and it continually restarts the FOH anytime it exits.� Place shortcuts to the batch file (instead of shortcuts directly to IBER.EXE or IBERQS.EXE) in the Windows StartUp folder, desktop, Start Menu, or wherever else you place a shortcut to start the FOH.

============================================================================

See also:

AKBID1010 Aloha Application Software System Environment Variables

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1116 File Server/Terminal Limitations

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3021 boh/foh bohfoh foh/boh fohboh terminal/server

Windows NT/Windows 2000 HASP Driver BSOD

Windows NT/Windows 2000 HASP Driver BSOD

============================================================================

AKBID3022

Created: 31 March 2000

Updated: 29 September 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: Windows NT, Windows 2000

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 4.2x

============================================================================

Older versions of the HASP^� security key driver might cause a 'Blue Screen of Death' (BSOD) when used with the Microsoft^� Windows NT^� or Windows^� 2000 operating system. �This only occurs on systems with multiple processors and when the ALOHA^� application software is starting two or more applications that access the security key at the same time.

To fix this, uninstall the current HASP key driver (refer to document AKBID3016), and install the HASP key driver version 3.81 or higher.

============================================================================

See also:

AKBID1112 HASP Key Troubleshooting

AKBID3016 HASP Driver Removal and Installation

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3022 bsd

Clock-Out Time is Less than Clock-In Time

Clock-Out Time is Less than Clock-In Time

============================================================================

AKBID3023

Created: 31 March 2000

Updated: 20 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

If you receive the error 'The Clock Out is less than the Clock In time' when editing punches in ALOHA^� application software Front-of-House (FOH), then the 'open time' is incorrectly set in the Back-of-House (BOH).

Set the 'open time' (refer to the Aloha QuickService or TableService User Manual) to reflect when the first person clocks-in, not the time the restaurant opens to the public.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3023 clockin clockout edit

Erase Sales Data for Go Live

Erase Sales Data for Go Live

============================================================================

AKBID3024

Created: 31 March 2000

Updated: 2 June 2003

Reviewed: 10 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

To erase the ALOHA^� application software sales data files before a going live, shut down the Front-of-House (FOH), close all Back-of-House (BOH) applications, and delete the following files on the file server:

1.        %IBERDIR%\DATA\*.LOG

2.        %IBERDIR%\DATA\NONRESET

3.        %IBERDIR%\DATA\NRTOTALS

4.        %IBERDIR%\DATA\HOUSE

5.        %IBERDIR%\DATA\HOUSE32

6.        %IBERDIR%\DATA\HOUSE50

7.        %IBERDIR%\DATA\*.CKD

8.        %IBERDIR%\DATA\*.CKP

9.        %IBERDIR%\EDC\<processor>\TXN*.*

10.     %IBERDIR%\EDC\<processor>\*.STL

11.     %IBERDIR%\PMS\TXN*.*

12.     Dated folders

13.     %IBERDIR%\HISTORY\GCLOG.*

14.     If you are using a Relational Database (RDB), create a fresh RDB and void of any historical information by creating a new RDB as described in document AKBID1131.

Restart the file server and terminals.�

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1131 Using .DBF Files to Create a New RDB Over an Existing RDB

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3024 clear go out remove removing reset zero zeroing

Javelin LC Customer Display Settings

Javelin LC Customer Display Settings

============================================================================

AKBID3025

Created: 31 March 2000

Updated: 9 November 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.201 � 5.3.x

============================================================================

Perform the following to enable the Javelin LC customer (pole) display in the ALOHA^� application software:

1.        Install the hardware (including the J5 jumper) according to Javelin's instructions.

2.        In the BIOS Peripheral Setup, set the Customer Display Emulation to Ultimate, and set the Customer Display Baud Rate to 4800.

3.        Cold-boot the computer.

4.        In the Aloha application software, set the Pole Display Type to PD220XL, and the Port to COM 2.

5.        Refresh the system.�

You may have to manually configure COM 2 in Microsoft^� Windows^� using the same settings as those in the BIOS.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3025 lcp line rear

Inclusive Tax Formula

Inclusive Tax Formula

============================================================================

AKBID3026

Created: 31 March 2000

Updated: 14 November 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

The ALOHA^� application software uses the following formula to figure inclusive taxes:

TAX= (AMOUNT * RATE) / (1 + RATE)

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1114 Tax and Surcharge Calculations

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3026

No Double-Click Ability with FOH Running

No Double-Click Ability with FOH Running

============================================================================

AKBID3027

Created: 31 March 2000

Updated: 29 December 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.8x � 5.3.x

============================================================================

To gain Microsoft^� Windows^� double-click abilities while the ALOHA^� application software TableService Front-of-House (FOH) is running on the local computer, add the system variable:

SET DOUBLECLICK=TRUE

This variable is considered true regardless of the assigned value.�� If this variable is not desired, completely remove it.

Although this variable enables double-click abilities with QuickService running, it interferes with QuickService operation in a way that multiple screen touches in quick succession are not all registered.�

============================================================================

See also:

AKBID1010 Aloha Application Software System Environment Variables

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3027

Labor Scheduler Log In

Labor Scheduler Log In

============================================================================

AKBID3028

Created: 4 April 2000

Updated: 11 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.4x � 5.3.x

============================================================================

The Aloha Labor Scheduler (ALS) login security has been increased in the ALOHA^� POS versions 4.4x and higher.�

Users cannot log in unless their ALOHA^� application software Security Level has 'Execute Labor Scheduler' enabled.

============================================================================

See also:

Aloha Labor Scheduler Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3028

Labor Scheduler Pay Periods do not Appear

Labor Scheduler Pay Periods do not Appear

============================================================================

AKBID3029

Created: 4 April 2000

Updated: 20 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

If a dated folder is not present for each day of an Aloha Labor Scheduler (ALS) Pay Period, ALS does not display the pay period when calculating sales projections.

A work-around is to create empty dated folders in the ALOHA^� application software for the missing days.

============================================================================

See also:

Aloha Labor Scheduler User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3029

Supported Crystal Report Writer Versions

Supported Crystal Report Writer Versions

============================================================================

AKBID3030

Created: 4 April 2000

Updated: 26 July 2002

Reviewed: 16 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The ALOHA^� application software uses the \BIN\CRPE32.DLL file to view and print reports created with Seagate Crystal Reports^�.

Aloha application software versions 4.2x and 4.4x use CRPE32.DLL version 5.01.1.108 (Crystal Reports version 5.0).

Aloha application software versions 5.0x and higher use CRPE32.DLL version 7.0.100.15 (Crystal Reports 7.0).

If you are using a newer version of Crystal Reports, replace the CRPE32.DLL file in the Aloha application software BIN folder with the version provided with your Crystal Reports software.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1108 Using the Crystal Report Interface with .DBF Files

AKBID1129 Using the Crystal Report Interface with an RDB

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3030 crw supported versions writer

Delete Previous Like Item

Delete Previous Like Item

============================================================================

AKBID3031

Created: 4 April 2000

Updated: 20 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The Delete function in the ALOHA^� application software Panel Editor has options for 'Previous Item' and 'Previous Like Item'.

'Previous Item' deletes the selected item or the last item added to the check.

'Previous Like Item' deletes the selected item or the last item added to the check, and all like items in conjunction with the quantity function.� For example, if you add 21 cookies to the check, but you must delete six of them, select the quantity '6', then select a button assigned with the 'Delete Previous Like Items' function.� Six of the 21 cookies are deleted.

============================================================================

See also:

Aloha QuickService User Manual

AKBID3032 Consolidate QuickService Open Check Items

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3031

Consolidate QuickService Open Check Items

Consolidate QuickService Open Check Items

============================================================================

AKBID3032

Created: 4 March 2000

Updated: 8 February 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

You can enable the ALOHA^� application software QuickService item consolidation on open checks by performing the following:

1.        Open Aloha Manager, and select Maintenance/Store Settings.

2.        Select the User Interface Group, and select the QuickService Layout subtab.�

3.        Select Consolidate Items.�

4.        Save the changes and refresh the system.

A small guest check icon appears on the Front-of-House (FOH) order entry screen above the guest.� Touch this icon to toggle item consolidation on and off.

============================================================================

See also:

Aloha QuickService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3032

Slow 16 MB 4.2 Terminals

Slow 16 MB 4.2 Terminals

============================================================================

AKBID3033

Created: 4 April 2000

Updated: 20 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.247 � 4.259

============================================================================

In versions 4.247 through 4.259, the ALOHA^� application software mistakenly allocates an additional eight megabytes of memory when you view a Front-of-House (FOH) Sales Report.� This can cause FOH terminals with 16 megabytes (or less) of memory to slow down significantly until you restart them.

This problem does not appear to effect terminals with 32 megabytes of memory.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3033

Disable QuickService Compulsory Cash Drawers

Disable QuickService Compulsory Cash Drawers

============================================================================

AKBID3034

Created: 4 April 2000

Updated: 20 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService

Aloha POS Versions: 4.210 � 5.3.x

============================================================================

To disable Compulsory Cash Drawers in ALOHA^� application software QuickService, edit the ALOHA.INI file in the NEWDATA folder.� Assign the CASHDRAWERTIMEOUT value to �1.�

Refresh the system.

============================================================================

See also:

Aloha QuickService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3034 close drawer open out time timeout

Gift Certificate Get_Entry_Name Error

Gift Certificate Get_Entry_Name Error

============================================================================

AKBID3035

Created: 4 April 2000

Updated: 20 October 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, BackOffice

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

If you are selling a BackOffice Gift Certificate in the Front-of-House (FOH) and receive an error stating 'Get_Entry_Name', then verify that the 'Ask for Price' option is not enabled for the item if the gift certificate is from a series that uses an assigned price.

Clear the 'Ask for Price' option for the gift certificate item in item maintenance.

============================================================================

See also:

Aloha BackOffice Gift Certificate User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3035

Survey ID Codes

Survey ID Codes

============================================================================

AKBID3036

Created: 4 April 2000

Updated: 11 September 2002

Reviewed: 10 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 4.228 � 5.3.x

============================================================================

They ALOHA^� application software can assign non-unique 10-digit or unique 15-digit ID numbers to customer surveys.

The following breaks down the ID number information for type of ID number:

Digit

10-digit Usage

15-digit Usage

1

Unit number digit 4

Check number digit 5

2

Hour digit 2

Hour digit 2

3

Unit number digit 1

Unit digit 4

4

Unit number digit 3

Check number digit 4

5

Month digit 2

Unit number digit 2

6

Unit number digit 2

Month digit 2

7

Day digit 2

Check number digit 3

8

Day digit 1

Unit number digit 1

9

Hour digit 1

Check number digit 2

10

Month digit 1

Month digit 1

11

Unused

Day digit 2

12

Unused

Unit number digit 3

13

Unused

Day digit 1

14

Unused

Hour digit 1

15

Unused

Check number digit 1 + 1

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3036

style='mso-spacerun:yes'>� 2003

BackOffice Green Keys

BackOffice Green Keys

============================================================================

AKBID3037

Created: 4 April 2000

Updated: 16 April 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The BackOffice installation files on the ALOHA^� Installation CD use the white HASP^� security key, and do not function with the green Fastech-issued security keys.

Obtain updated HASP security key activation codes from Aloha Technologies before upgrading a site (using the Aloha Installation CD) that is currently using a green Fastech-issued key.

Refer to document AKBID1112 for more information on the white HASP security key versus the green Fastech-issued security key.

============================================================================

See also:

AKBID1112 HASP Key Troubleshooting

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3037 dongle

LANDRYS Flag

LANDRYS Flag

============================================================================

AKBID3038

Created: 4 April 2000

Updated: 31 July 2003

Reviewed: 18 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

If you create either a LANDRYS file or a LANDRYS folder in the root of C: (for example, C:\LANDRYS), then the ALOHA^� application software enables the following changes:

1.        The Back-of-House (BOH) 'Super-Secret-Password' uses a U-shape instead of a Z-shape.

2.        The BOH Sales Report does not have a Settings button (excluding versions 5.001 � 5.021).

3.        The BOH Sales Report prompts for the Weather (excluding versions 5.001 � 5.021).� The weather information is stored in WEATHER.TXT in the DATA folder or dated folder.� Instances of WEATHER.TXT in the DATA folder are moved to the dated folder during the End-of-Day (EOD) routine.

4.        The BOH Sales Report includes the text 'Final Copy' if it is printed from a dated folder (excluding versions 5.001 � 5.021).

5.        In versions 5.2.5.x and higher, the grind process creates an export file in the dated folder labeled LPyyyymmdd.LOG, and additional grind file labeled GNDAUDIT.DBF and GNDEDC.DBF.

In versions 5.001 � 5.021, the BOH Sales Report changes are only available by running the Landry's Sales Report from a command line (refer to document AKBID1038).

============================================================================

See also:

Aloha TableService User Manual

AKBID1038 Report Command Line Parameters

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3038 landries landry's log login logon on rpt

Masking the Credit Card Numbers on the Guest Check

Masking the Credit Card Numbers on the Guest Check

============================================================================

AKBID3039

Created: 4 April 2000

Updated: 9 December 2003

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 4.247 � 5.2.8.x

============================================================================

If you are using Aloha versions 5.3.x or higher, refer to document AKBID1231.

If you are using ALOHA^� application software versions 4.247 though 5.0x, edit the ALOHA.INI file in the NEWDATA folder and assign the MASKCREDITCARDNUMBERS variable to a value of 1 in order to mask credit card numbers on guest checks (both printed and on-screen).� Use a value of 0 disables credit card number masking.

If you are using Aloha application software versions 5.2x and higher, open Aloha Manager and select Maintenance/Store Settings/Credit Card/Voucher Printing and enable the credit card number mask.� This masks credit card numbers on guest checks (both printed and on-screen) and on credit card vouchers.

The credit card number mask defaults to only displaying the last four digits of the credit card, but you can customize this in versions 5.017 and higher.� Refer to document AKBID3041 for more information.

Although you can completely disable credit card masking in versions 5.230 and higher, you cannot disable the Aloha application software from masking the credit card number on the first credit card voucher in versions 5.229 and lower.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1231 Masking Credit Card Numbers

AKBID3040 Show Credit Card Numbers on the EDC Report

AKBID3041 Masking the Credit Card Number on the Voucher

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3039 display hide remove show

Show or Hide Credit Card Numbers on EDC Report

Show or Hide Credit Card Numbers on EDC Report

============================================================================

AKBID3040

Created: 6 April 2000

Updated: 29 May 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 4.0x � 5.3.x

============================================================================

The ALOHA^� application software Back-of-House (BOH) Electronic Draft Capture (EDC) Transaction Reports mask the credit card numbers for security reasons by default.

To disable the mask, add the following line to the [REPORT] section of the EDC.INI file if it does not already exist:

PRINTFULLCARDNUMBER=1

============================================================================

See also:

Aloha EDC User Manual

AKBID1231 Masking Credit Card Numbers

AKBID3039 Masking the Credit Card Numbers on the Guest Check

AKBID3041 Masking the Credit Card Number on the Voucher

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3040 display hide remove show

Masking the Credit Card Number on the Voucher

Masking the Credit Card Number on the Voucher

============================================================================

AKBID3041

Created: 4 April 2000

Updated: 9 March 2004

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 4.247 � 5.2.8.x

============================================================================

If you are using Aloha versions 5.3.x or higher, refer to document AKBID1231.

If ALOHA^� application software versions 4.247 through 5.229 are configured to print two copies of the credit card voucher, then by default, the customer's credit card number is automatically masked (or hidden) only on the second credit card voucher.� You can print the full credit card number or mask the credit card number on all vouchers in 5.230 and higher by opening Aloha Manager and enabling Maintenance/Store Settings/Credit Card/Voucher Printing/'Always show full number' or 'Only show last 4 digits on all vouchers'.

The credit card number mask defaults to only displaying the last four digits of the credit card number, but you can customize this in versions Aloha 5.017 and higher. �To change the masked digits, add CCnMASK=z to the ALOHA.INI, if it does not already exist.� Replace n with the number of digits in the credit card number.� You will need a different variable for credit card length.� Replace z with the digits to mask, using X to mask the digit and O to display the digit.

For example, Visa credit card numbers range from 13 to 16 digits.� To mask the first four numbers on all Visa credit cards, you would add the following variables to the ALOHA.INI:

CC13MASK=XXXXOOOOOOOOO

CC14MASK=XXXXOOOOOOOOOO

CC15MASK=XXXXOOOOOOOOOOO

CC16MASK=XXXXOOOOOOOOOOOO

In versions 5.2x and higher, this mask is also applied to credit card numbers on the guest check, not just the credit card vouchers.� You must also enable credit card masking, as explained in AKBID3039, for this feature to function properly.

In versions 5.2.8.x and higher, you can suppress the credit card expiration date on credit card chits by opening Aloha Manager, selecting Maintenance/Store Settings/Credit Card/Voucher Printing, and selecting the option for 'Do Not Print Expiration Date'.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1231 Masking Credit Card Numbers

AKBID3039 Masking the Credit Card Numbers on the Guest Check

AKBID3040 Show Credit Card Numbers on the EDC Report

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3041 hide show

Default Magnetic Stripe Reader Sentinels

Default Magnetic Stripe Reader Sentinels

============================================================================

AKBID3042

Created: 4 April 2000

Updated: 5 September 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.0x

============================================================================

The information in this document has been replaced by information in document AKBID1198.

============================================================================

See also:

AKBID1198 Magnetic Stripe Card Information

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3042

Aloha Manager Navigation Bar Settings

Aloha Manager Navigation Bar Settings

============================================================================

AKBID3043

Created: 4 April 2000

Updated: 11 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The ALOHA^� application software Aloha Manager Navigation Bar settings reside in the PROFILES folder.

Each user has a folder inside the PROFILES folder labeled by the user ID number.� For example, the folder for employee ID 100 is labeled USER100.

The NAVBAR.CFG file stores Navigation Bar shortcuts and groups.�

The USERxxx.CFG (where xxx is the user ID number) stores the Navigation Bar width and auto-hide settings.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1166 Aloha Manager BOH Security Files

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3043 store

CLOSETIME ALOHA.INI Setting

CLOSETIME ALOHA.INI Setting

============================================================================

AKBID1044

Created: 4 April 2000

Updated: 20 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

The CLOSETIME variable in the ALOHA^� application software ALOHA.INI file is an obsolete setting that was used to start the End-of-Day (EOD) process.

This setting not recognized by current versions, and you can remove it from the ALOHA.INI.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3044

EVENTTIME ALOHA.INI Setting

EVENTTIME ALOHA.INI Setting

============================================================================

AKBID1045

Created: 4 April 2000

Updated: 20 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

The EVENTTIME variable in the ALOHA^� application software ALOHA.INI file is an obsolete setting that was previously used to start events.

This setting not recognized by current versions, and you can remove it from the ALOHA.INI.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3045

CONNMGR.EXE

CONNMGR.EXE

============================================================================

AKBID3046

Created: 4 April 2000

Updated: 20 April 2001

Reviewed: No longer reviewed

Microsoft Windows Versions: Windows for Workgroups 3.11

Aloha Products: TableService

Aloha POS Versions: 3.0x � 4.0x

============================================================================

The ALOHA^� application software used CONNMGR.EXE (Connection Manager) as a Microsoft^� Windows^� shell for terminals using boot-floppies.

The Aloha application software no longer uses CONNMGR.EXE, and you should remove any Windows StartUp folder shortcuts or SHELL applications that reference CONNMGR.EXE.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3046

NCR 7454 Windows Protection Error

NCR 7454 Windows Protection Error

============================================================================

AKBID3047

Created: 4 April 2000

Updated: 20 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: Windows 95

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

A conflict with Crystal Ware Audio application supplied with the NCR 7454 POS terminal may result in a 'Windows Protection Error' when starting the ALOHA^� application software.

To correct the problem, edit C:\CONFIG.SYS, and change the buffers from 20 to 40.

If you are not using the Crystal Ware Audio application, remove the CWDINIT.EXE line from C:\CONFIG.SYS.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3047 general protection fault gp gpf

Illegal Operation Over the Floating Logo

Illegal Operation Over the Floating Logo

============================================================================

AKBID3048

Created: 4 April 2000

Updated: 28 October 2003

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

Corrupt printer logs can cause Microsoft^� Windows^� 'Illegal Operation' errors that appear over the floating logo, but still enable use of the ALOHA^� application software.

Check the terminal's Debugging-Output-File (debout) for evidence of log corruption when this error occurs.

This error can also appear if you are using AlohaSpy on a Windows 95-based terminal without installing Winsock2.� You must either disable AlohaSpy on this terminal or install Winsock2 from \MISC\WINSOCK2 folder the Aloha Installation CD.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1134 Debouts

AKBID1157 Aloha Application Software Printer Logs

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3048

FOH Sticks on 'Initializing POS' on FOH/BOH Computer

FOH Sticks on 'Initializing POS' on FOH/BOH Computer

============================================================================

AKBID3049

Created: 4 April 2000

Updated: 18 October 2002

Reviewed: 3 February 2004

Microsoft Windows Versions: Windows 95, Windows 98, Windows Me

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

============================================================================

If the ALOHA^� application software Front-of-House (FOH) sticks on 'Initializing POS' on a computer running both the FOH and Back-of-House (BOH), add the /NONET variable to the CtlSvr.exe (Control Server) variables in the Microsoft^� Windows^� Registry (refer to document AKBID3009).

The NONET variable is not required if you are using Windows NT^�, Windows 2000, or Windows XP.

============================================================================

See also:

AKBID1010 Aloha Application Software System Environment Variables

AKBID1116 File Server/Terminal Limitations

AKBID3009 CTLSVR.EXE Registry Variables

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3049 boh/foh bohfoh foh/boh fohboh terminal/server

EDC Type 4 Transactions

EDC Type 4 Transactions

============================================================================

AKBID3050

Created: 5 April 2000

Updated: 20 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

The ALOHA^� application software Electronic Draft Capture (EDC) application does not support Type 4 transactions, or full-duplex interleaving.

============================================================================

See also:

Aloha Credit Card User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3050

COM Port Error -1

COM Port Error -1

============================================================================

AKBID3051

Created: 5 April 2000

Updated: 20 October 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

The ALOHA^� application software Front-of-House (FOH) displays the error 'Failed to open Com Port n, status �1' if the serial (or COM) port assigned to a device (printer, cash drawer, and so on) that is non-existent, in use by another device, or not functioning properly because of hardware or address problems.

In rare cases, Microsoft^� Windows^� power management might disable the serial port to conserve battery life.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1139 Serial Port Error Return Codes

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3051

COM Port Error -3

COM Port Error -3

============================================================================

AKBID3052

Created: 5 April 2000

Updated: 20 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

The ALOHA^� application software Front-of-House (FOH) displays the error 'Failed to open Com Port n, status �3' if the serial (or COM) port assigned to a device (printer, cash drawer, and so on) is in use by another device, or not functioning properly because of hardware or address problems.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1139 Serial Port Error Return Codes

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3052

Terminal-Specific EDC Processors

Terminal-Specific EDC Processors

============================================================================

AKBID3053

Created: 5 April 2000

Updated: 7 May 2002

Reviewed: 18 February 2004

Microsoft Windows Versions: All

Aloha Products: EDC

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The ALOHA^� application software supports terminal-specific EDC accounts.� You can assign each Front-of-House (FOH) terminal to a specific EDC account or groups of FOH terminals to a specific EDC account.� Perform the following to configure terminal-specific EDC accounts:

1.        Create multiple accounts for the processor in EDC.� EDC labels each processor that you configure using the processor name followed by an index number.� For example, EDC will label multiple Visanet processors as VISANET, VISANET1, VISANET2, and so on.

2.        Assign your credit card types to a processor in Configure/Cards.� Only the initial processor (for example, VISANET) is listed in the credit card type's drop-down menu.� EDC automatically assigns transactions to the correct processor based on the information in step number three.

3.        Open the Aloha application software Back-of-House (BOH) and navigate to Terminal maintenance.� Assign each terminal to a processor index by configuring the EDC Info field.� You must configure this field using the INDEX=n format, where n is the processor index (for example, 'INDEX=1', 'INDEX=2' and so on).

4.        Refresh the system.

Although the Aloha application software always reads the modem and account information from the corresponding processor index, if you are using a processor that employs batch and sequence numbers (for example, Visanet), the default behavior is to always read the batch and sequence numbers from the first processor index.� If you want each processor index to use separate batch and sequence numbers, enable the MULTIPLEMERCHANTIDS variable in the EDC.INI by setting MULTIPLEMERCHANTIDS=TRUE to the [System] section of the EDC.INI.

============================================================================

See also:

Aloha QuickService or TableService User Manual

Aloha Credit Card User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3053

Remote pcANYWHERE Report Printing

Remote pcANYWHERE Report Printing

============================================================================

AKBID3054

Created: 5 April 2000

Updated: 20 October 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

Users accessing an ALOHA^� application software file server from a remote location using Symantec^� pcANYWHERE^� can print reports on a remote printer.� Refer to the pcANYWHERE user guide for more information.

Assign the Microsoft^� Windows^� default printer to the pcANYWHERE remote printer to print Aloha application software reports on the remote printer.�

Reassign the default printer back to the local printer after completion so the site can print Aloha application software reports if needed.

============================================================================

See also:

Aloha QuickService or TableService User Manual

Symantec pcANYWHERE User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3054

Shifted FOH Screen

Shifted FOH Screen

============================================================================

AKBID3055

Created: 5 April 2000

Updated: 20 October 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

If the Microsoft^� Windows^� taskbar is set to 'Always on top', it might cause the ALOHA^� application software Front-of-House (FOH) to appear 'shifted' or off-center.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3055 bottom cut off

Unable to Locate Security Descriptor

Unable to Locate Security Descriptor

============================================================================

AKBID3056

Created: 5 April 2000

Updated: 3 August 2001

Reviewed: 6 February 2004

Microsoft Windows Versions: Windows NT, Windows 2000

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

If the ALOHA^� application software file server is running Microsoft^� Windows NT^�, Windows^� 2000, or Windows XP, the error 'Unable to locate security descriptor' error may occur if a shortcut to ALOHAMGR.EXE (Aloha Manager), CTL.EXE (Control), or EDC.EXE (EDC) is in the Windows StartUp folder.

If you are using Windows automatic log in and you have configured CTLSVR.EXE (Control Server) or EDCSVR.EXE (EDC Server) to run as a Windows service, Windows can process the shortcuts in the Windows StartUp folder before the Control Server and EDC Server services have completely started.� This can also happen if you manually log into the system too quickly.� When this occurs, you will receive an error stating 'Unable to locate security descriptor'.

To fix this, either remove Aloha Manager, Control Server, or EDC Server from the StartUp folder (since they are running as services, there is no reason to place them in the StartUp folder) or initialize Aloha Manager, Control, or EDC from a batch file in the StartUp folder.� The batch file can utilize the WAIT.EXE utility (refer to document AKBID1012) to create a 30-secoind pause before initializing the application.� Since Control Server and EDC Server are running as Windows services (in this case), you do not have to start ALOHAMGR.EXE, CTL.EXE, or EDC.EXE in order for the Aloha application software file server to function properly.�

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1008 BackOffice Interfaces and RPC Service

AKBID1012 Aloha Application Software Utility Description and Usage

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3056

Employee Locked on Another Terminal

Employee Locked on Another Terminal

============================================================================

AKBID3057

Created: 5 April 2000

Updated: 6 October 2000

Reviewed: 16 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

Errors stating that an employee is locked on another Front-of-House (FOH) terminal are typically caused by one of the following:

1.        The employee is logged in to another terminal.

2.        A manager is editing the employee or the employee's open checks on another FOH terminal.

3.        The ALOHA^� application software file server is out of disk space, and the .LCK files (refer to document AKBID3012) are not being deleted.

4.        Faulty power or network issues.

In the case low disk space, refer to document AKBID1014 to recover disk space.� Once disk space has been recovered, stop the FOH, delete *.LCK from the DATA folder, and restart the FOH.

============================================================================

See also:

AKBID1014 Full Hard Drive Recovery

AKBID3012 LCK Files

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3057

Tip Refund

Tip Refund

============================================================================

AKBID3058

Created: 5 April 2000

Updated: 6 February 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

ALOHA^� Products: QuickService, TableService

Aloha POS Versions: 3.204 � 5.3.x

============================================================================

Tip Refund, also known as tip reduction, enables a restaurant to withhold a percentage of credit card tips to recover the credit card processor fees for the tip.�

Tip refund includes automatic gratuities in the tip refund calculation.

Tip refund is not related to tip share (refer to document AKBID1064).

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1064 Tip Share

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3058

Faded Cool Interfaces

Faded Cool Interfaces

============================================================================

AKBID3059

Created: 5 April 2000

Updated: 2 October 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: All

ALOHA Products: TableService

Aloha POS Versions: 3.8x � 5.3.x

============================================================================

If the CLRPAL.BMP file is not in the ALOHA^� application software BMP folder of each Front-of-House (FOH) terminal, the Cool Interfaces can appear faded or washed out.

If CLRPAL.BMP is not available, copy LOGBTNDN.BMP (in the BMP folder) to CLRPAL.BMP.

You must set your Microsoft^� Windows^� Display colors to 256 colors or higher.

============================================================================

See also:

Aloha TableService User Manual

AKBID1165 FOH Screen Resolution Settings

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3059

Job Code Revenue Center

Job Code Revenue Center

============================================================================

AKBID3060

Created: 5 April 2000

Updated: 6 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

ALOHA Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

ALOHA^� application software Job Code Revenue Centers are used only with the Hourly Sales and Labor Report.� They have no other effect on revenue center assignment.

You must assign each job code to a revenue center in order to properly report the 'Split Hourly Sales and Labor by Revenue Center' setting on the Hourly Sales and Labor Report.� If a job code is not assigned to a revenue center, then the report does not include labor information for that job code.� It will, however, report properly if the 'Split Hourly Sales and Labor by Revenue Center' setting is disabled.

This feature is not retroactive in regards to previous dated folders created without revenue centers assigned to job codes.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1054 Revenue Centers

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3060 jobcode

Aloha Manager SSP Timeout

Aloha Manager SSP Timeout

============================================================================

AKBID3061

Created: 5 April 2000

Updated: 15 January 2004

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The timeout for the Super-Secret-Password (SSP) used with ALOHA^� application software Back-of-House (BOH) applications is set to 10 minutes.� You cannot change the timeout.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3061 alt alt-x altx back backdoor door super user superuser x

FOH Server Sales Report Abbreviations

FOH Server Sales Report Abbreviations

============================================================================

AKBID3062

Created: 5 April 2000

Updated: 26 May 2000

Reviewed: 10 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

The ALOHA^� application software Front-of-House (FOH) Sales Report uses the following abbreviations:

AST (Average Sales Per Transaction) = Total Employee Sales / Total Employee Checks

TPP (Transaction Per Period) = Interval Seconds (user defined) / Total Employee Checks

ATT (Average Time of Transaction) = Total Employee Check Open Times / Total Employee

Checks.� Check Open Time is the time from when the first item is added to the check until the check is closed.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3062 abbreviation acronym acronyms

style='mso-spacerun:yes'>� 2003

Ultimate Technology Corporation Customer Display Settings

Ultimate Technology Corporation Customer Display Settings

============================================================================

AKBID3063

Created: 5 April 2000

Updated: 5 April 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.201 � 5.3.x

============================================================================

Ultimate Technology Corporation customer (rear) displays require the following settings for use with the ALOHA^� application software:

Baud Rate � 4800

Parity � None

Stop Bits � 2

Data Bits � 8

The display uses ASCII code 16 followed by ASCII code 0 to set the start position to the upper left-hand corner, and then it displays 40 characters of text.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected]..

Additional query words: 3063

Wait for Credit Card Authorization

Wait for Credit Card Authorization

============================================================================

AKBID3064

Created: 5 April 2000

Updated: 6 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

ALOHA^� Products: QuickService

Aloha POS Versions: 4.0x � 5.3.x

============================================================================

If you want to access the current order or open new orders in QuickService while processing a credit card, clear the 'Wait for credit card authorization' flag in the revenue center maintenance.

============================================================================

See also:

Aloha QuickService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3064 authorizations edc enter start

Windows 9x Fails to Initialize Microsoft Windows Networking

Windows 9x Fails to Initialize Microsoft Windows Networking

============================================================================

AKBID3065

Created: 5 April 2000

Updated: 18 September 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: Windows 95, Windows 98

Aloha Products: QuickService, TableService

ALOHA^� POS Versions: 3.5x � 5.3.x

============================================================================

On occasion, Microsoft^� Windows^� 95 and Windows 98 fail to initialize Windows networking, even though all of the settings are correctly configured.� One possible cause is the AutoLogin value in the Windows registry.� Perform the following to remove the value from the registry:

The incorrect use of Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

New registry entries described in this document are enclosed in quotation marks.� Please ignore these quotation marks when adding the entry in the Windows Registry.� All Registry entries are case sensitive.

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.

2.        Path out HKEY_LOCAL_MACHINE\Software\Micrsoft\Windows\CurrentVersion\Network\Real Mode Net.

3.        Delete the AutoLogin Value if it exists.

4.        Select Registry/Exit to exit the Windows Registry Editor.

5.        Restart Windows.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1099 Network Troubleshooting

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3065 datagram error failed in log login logon on return start

SuperSite PMS Settlement

SuperSite PMS Settlement

============================================================================

AKBID3066

Created: 6 April 2000

Updated: 13 November 2002

Reviewed: 4 March 2004

Microsoft Windows Versions: All

Aloha Products: EDC

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The ALOHA^� application software Property Management System (PMS) interface settlement occurs when the End-of-Day (EOD) process creates a DONE30 file in the file server's PMS folder (refer to document AKBID1062).

Since the SuperSite EOD process functions differently from a standard site, you have to manually create the DONE30 file on the EDC/PMS file server each night.� You should activate the batch file each night using the Microsoft^� Windows^� Schedule Service (refer to document AKBID1047) or Windows Task Scheduler at a time when all of the SuperSite stores are closed or during the least busy point.� The batch file must create a DONE30 file in the PMS folder on the file server.� Once EDCSVR.EXE (EDC Server) detects the DONE30 file, it will delete the DONE30 file and all of the current TXN files.�

The batch file only requires a single line:

ECHO 1 > %IBERDIR%\PMS\DONE30

============================================================================

See also:

AKBID1047 Microsoft Windows Schedule Service

AKBID1062 Property Management Systems

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3066 txn

QS Append to Current Quantity

QS Append to Current Quantity

============================================================================

AKBID3067

Created: 6 April 2000

Updated: 26 May 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

ALOHA^� Products: QuickService

Aloha POS Versions: 3.8x � 5.3.x

============================================================================

The 'Append to current qty' option in the QuickService Quantity button function appends the additional quantity numbers to the initial number.

For example, create ten buttons with quantities 0 � 9.� Select the 'Append to current qty' option on each button.

Select 1/0/<item> if you want to order ten items in the Front-of-House (FOH).� If you want to order 32 items, select 3/2/<item>.

============================================================================

See also:

Aloha QuickService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3067 ordering

Bump to Video Group

Bump to Video Group

============================================================================

AKBID3068

Created: 13 April 2000

Updated: 6 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The ALOHA^� application software versions 5.0x and higher offer the 'Bump To Video Group' option.� To access the option, open Aloha Manager, and select Maintenance/Hardware/Video Monitors.

This option bumps orders from one video monitor to another video group.� This process continues with each bump until the order reaches a video monitor that does not have a 'Bump To Video Group' defined.

============================================================================

See also:

Aloha Video User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3068

Negative Price Modifiers

Negative Price Modifiers

============================================================================

AKBID3069

Created: 13 April 2000

Updated: 26 May 2000

Reviewed: 9 December 2003

Microsoft^� Windows^� Versions: All

ALOHA^� Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

Menus can have negative priced modifiers to decrease the price of an item, but, at the time of this writing, 'Modify Base Price' does not support negative dollar amounts.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3069 minus subtract

style='mso-spacerun:yes'>� 2003

Irregular Mouse Movement when CTLSVR.EXE is Running

Irregular Mouse Movement when CTLSVR.EXE is Running

============================================================================

AKBID3070

Created: 13 April 2000

Updated: 1 November 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

ALOHA^� Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

In cases where the HASP^� key is removed from a computer after CTLSVR.EXE (Control Server) is started on a demonstration computer, the mouse movement becomes irregular and jerky.

This is caused by Control Server consuming resources while trying to communicate with the HASP key.� Reattach the HASP key or stop Control Server.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1112 HASP Key Troubleshooting

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3070 pauses slow

Incomplete Labor Reports

Incomplete Labor Reports

============================================================================

AKBID3071

Created: 13 April 2000

Updated: 6 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

ALOHA^� Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

If a week's Back-of-House (BOH) labor reports appear incorrect or incomplete, manually regrinding the dated folders might correct the problem.� Grind the first day of the pay period, and continue each day of the pay period in order of their date.

Refer to document AKBID1016 for more information on the Grind Process and manually grinding dated folders.

Always start with the first day, and always regrind each day of the pay period in order of their date.

============================================================================

See also:

AKBID1016 Grind Process and Errors

AKBID3247 Shifts not Listed on Labor Reports

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3071 hours pay zero zeros

Repairing a Corrupt TRANS.LOG

Repairing a Corrupt TRANS.LOG

============================================================================

AKBID3072

Created: 13 April 2000

Updated: 6 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

============================================================================

Many fatal ALOHA^� Application Software errors and software anomalies are attributed to TRANS.LOG (transaction log) corruption.� You can use FIXLOG.EXE (refer to document AKBID1012) to repair corrupt transaction logs.

There are multiple versions of FIXLOG.EXE called FIXLOG2.EXE, FIXLOG3.EXE, and so on.� Each version is designed for a specific version of the Aloha application software.� You must use the correct version of FIXLOG.EXE.

To repair a corrupt log for the current day's business, turn off all POS terminals, open a command prompt and navigate to the DATA folder on the file server, use FIXLOG.EXE to repair the transaction log on the file server using the following command line, and restart the POS terminals:

FIXLOG.EXE TRANS.LOG

To repair a corrupt log for previous days business, open a command prompt and navigate to the dated folder on the file server, repair the transaction log in the dated folder using the same command line as above, and manually regrind (refer to document AKBID1016) the dated folder.

FIXLOG.EXE does not alter the original transaction log, but, instead, creates a new transaction log labeled FIXED.LOG.� Create a backup copy of the original transaction log and rename FIXED.LOG to TRANS.LOG.

============================================================================

See also:

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1016 Grind Process and Errors

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3072 fix fixlog fixlog2 fixlog3 fixlog4 fixlog4327 fixlog5200

Aloha Technologies MSR Card Engraved Number

Aloha Technologies MSR Card Engraved Number

============================================================================

AKBID3073

Created: 13 April 2000

Updated: 20 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

ALOHA^� Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

The engraved number on employee Magnetic-Stripe-Reader (MSR) cards supplied by Aloha Technologies has no relation to the information encoded in the magnetic strip.

The number is for visual identification only.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3073 id mag magcard magcards swipe

Non-Redeemed Payments

Non-Redeemed Payments

============================================================================

AKBID3074

Created: 13 April 2000

Updated: 4 February 2003

Reviewed: 25 February 2004

Microsoft Windows Versions: All

ALOHA^� Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

Non-Redeemed payments are tenders with overpayments that do not supply change.� They are, in general, non-cash payments.� Non-redeemed payments occur when you apply a tender, decrease the sale amount (with a void, comp, or promo), and not adjust the tender to reflect the new total.

Cash tenders adjust automatically, and they do not encounter this problem.

Non-redeemed payments, often displayed as 'N/R' on reports, can create unbalanced report comparisons.

The easiest method to determine which checks had non-redeemed payments is to reprint all of the day's checks from CTL.EXE (Control) or ALOHAMGR.EXE (Aloha Manager) with the reprint output to set 'Screen'.� This creates a text file with all of the day's checks and Control or Aloha Manager opens the text file using the default viewer assigned in Microsoft^� Windows^� (for example, Notepad).� You can then search the text file for 'NR' or 'N/R' in order to see which checks had non-redeemed payments.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3074 nr

NOTOTALLINEONCHECK in the ALOHA.INI

NOTOTALLINEONCHECK in the ALOHA.INI

============================================================================

AKBID3075

Created: 12 May 2000

Updated: 12 May 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

ALOHA^� Products: QuickService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The NOTOTALLINEONCHECK variable in the ALOHA.INI disables the check total line on QuickService guest checks.

To access this setting on the Back-of-House (BOH), perform one of the following (based on version number):

In versions 4.4x and lower, open Maintenance, and select Options/Print/Guest Checks.� Select 'No Total Line on Check'.

In versions 5.0x and higher, open Aloha Manager, and select Maintenance/Store Settings/Printing.� Select 'Do not print a Total Line' in the Check Content 1 subtab.

============================================================================

See also:

Aloha QuickService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3075

Maximum Number of Items

Maximum Number of Items

============================================================================

AKBID3076

Created: 13 April 2000

Updated: 6 February 2001

Reviewed: 12 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The default maximum number of items allowed in the ALOHA^� application software is 15,000.� (This is not the highest ID number allowed, but the maximum number of entries in the database.)

You can increase the maximum number of items to 100,000, but this increases the memory usage on the Front-of-House (FOH) terminals.

Do not increase this value unless it is absolutely needed.� If you must increase the value, increase it in small increments if possible to monitor any performance degradation.

To increase the maximum number of items in versions 4.4x and lower, open Maintenance, select Options/Miscellaneous 1, and select the maximum numbers of items, in increments of 1000, in the 'Maximum number of items' text box.

To increase the maximum number of items in versions 5.0x and higher, open Aloha Manager, and select Maintenance/Store Settings/System/Aloha Settings.� Enter the maximum numbers of items, in increments of 1000, in the 'Maximum number of items' text box.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3076 max

style='mso-spacerun:yes'>� 2003

Multiple Chits Print

Multiple Chits Print

============================================================================

AKBID3077

Created: 13 April 2000

Updated: 17 April 2002

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 4.0x

============================================================================

If the ALOHA^� application software does not receive confirmation from the printer that the chit printed successfully, the software will print another copy of the chit with 'Reprint' displayed at the bottom.

If chit printers print multiple (and unintended) copies of chits, they are evidence of a printer or wiring problem.� Verify the printer settings in document AKBID1002 and verify the pin-outs of the wiring and adapters used with the printer.� Verify the wiring specifications in the Aloha A/C Power and Communication Requirements user manual.

============================================================================

See also:

Aloha A/C Power and Communication Requirements

Aloha QuickService or TableService User Manual

AKBID1002 Aloha Receipt and Kitchen Printer Settings

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3077 reprinting

style='mso-spacerun:yes'>� 2003

Delivery Interface not Responding to FOH

Delivery Interface not Responding to FOH

============================================================================

AKBID3078

Created: 13 April 2000

Updated: 20 October 2000

Reviewed: 3 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, BackOffice

Aloha POS Versions: 3.65x � 5.3.x

============================================================================

If the ALOHA^� application software Front-of-House (FOH) displays an error stating� 'NO RESPONSE.� DELIVERY INTERFACE PROBABLY NEEDS TO BE STARTED' when you are assigning a customer to a check, ensure the following are true:

The Aloha Interface is started on the file server.

The interface Message File Path is set to the \DELIVERY\MESSAGES\ (note the additional back-slash at the end) folder inside the Aloha application software folder.

The \DELIVERY\MESSAGES folder exists inside the Aloha application software folder.

The SERVER environment variable is correctly set in the FOH (refer to document AKBID1010).

The FOH terminals can access the file server over the network.

The BACKOFFICEDIR environment variable is not set or is set incorrectly (refer to document AKBID3128).

============================================================================

See also:

Aloha Delivery/Frequent Buyer User Manual

AKBID1010 Aloha Application Software System Environment Variables

AKBID3128 SuperSite BackOffice Messages Folder

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3078

NOMODCODES in ALOHA.INI

NOMODCODES in ALOHA.INI

============================================================================

AKBID3079

Created: 13 April 2000

Updated: 20 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions:

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.030 � 5.3.x

============================================================================

In order to suppress the NO, SIDE, and EXTRA modifier options in the ALOHA^� application software Front-of-House (FOH), edit the ALOHA.INI in the NEWDATA folder, and assign a value of TRUE to the NOMODCODES variable (for example, NOMODCODES=TRUE), and refresh the system.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID3229 Enabling the Substitute Modifier Button

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3079 codes modifiers remove

BOH Sort Preferences

BOH Sort Preferences

============================================================================

AKBID3080

Created: 17 April 2000

Updated: 26 February 2002

Reviewed: 5 March 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 4.4x, 5.031 � 5.3.x.x

============================================================================

The ALOHA^� application software Maintenance application (Aloha versions 3.5x through 4.4x) stores the default sort preferences in the [Ibertech] section of the WIN.INI located in the Microsoft^� Windows^� folder.

The following variables set the sort options for versions 3.5x through 4.4x:

Database

Variable

Exception Modifiers

MntExceptionSort=0

Items

MntItemSort=0

Menus

MntMenuSort=0

Modifiers

MntModifierSort=0

Submenus

MntSubmenuSort=0

Set the variable to '0' to sort alphabetically or set the variable to '1' to sort numerically.

Aloha Manager versions 5.031 � 5.0x automatically save the most recent preference settings as the default settings.� They are stored in the Windows registry, not the WIN.INI.

Aloha Manager versions 5.2x and higher save separate preferences for each user the Aloha application software PROFILES folder.� Settings for the Super-Secret-Password (SSP) are stored in the \COMMON\COMUSR.CFG file and user-specific settings are stored in the \USRn\USRn.CFG file (where n is the user ID).

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3080 super user superuser

Closing QS Refunds

Closing QS Refunds

============================================================================

AKBID3081

Created: 17 April 2000

Updated: 20 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService

Aloha POS Versions: 3.8x � 5.3.x

============================================================================

The ALOHA^� application software cannot close QuickService refunds to a tender.�

Close refunds with a button assigned to the Close Check function or a button assigned to a script with the Close Check function included in the script.

============================================================================

See also:

Aloha QuickService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3081

Scale Serial Port, Cable, and Miscellaneous Configuration

Scale Serial Port, Cable, and Miscellaneous Configuration

============================================================================

AKBID3082

Created: 17 April 2000

Updated: 1 May 2003

Reviewed: 25 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

Serial Port Settings

Scale

Bits per second

Data bits

Parity

Stop bits

Flow Control

METTLER TOLEDO

9600

7

Even

1

Xon / Xoff

NCI

19200

7

Even

1

Xon / Xoff

You might also have to edit the communication settings on the scale itself to use the above settings.�

Cables

METTLER TOLEDO - Serial DB9 to Scale DB9

DB9

2

3

4

5

DB9

3

2

6

5

METTLER TOLEDO - Serial DB25 to Scale DB9

DB25

2

3

7

20

DB9

2

3

5

6

�

NCI - Serial DB9 to Scale DB9

DB9

1

2

3

4

5

6

7

8

9

DB9

1

2

3

4

5

6

7

8

9

NCI - Serial DB25 to Scale DB9

DB25

2

3

4

5

6

7

8

20

22

DB9

3

2

7

8

6

5

1

4

9

Miscellaneous

European METTLER TOLEDO scales use a different protocol and the United States versions scales.� In order to configure the ALOHA^� application software versions 5.2.5.132 and higher to use the European protocol, edit the ALOHA.INI in the NEWDATA folder, and assign the METTLERFORMAT variable to a value of 1 (for example, METTLERFORMAT=1).� Refresh the system.� Assign a value of 0 for the standard or United States protocol.

You can add DEBUGSCALES to the Microsoft^� Windows^� system environment variables and assign it a value of TRUE in order to include additional debugging information in the terminal's Debugging-Output-File (debout).

============================================================================

See also:

Aloha QuickService or TableService User Manual

Aloha Accessories User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3082 db-9 db-25 pinout pinouts

Tip Share

Tip Share

============================================================================

AKBID3083

Created: 17 April 2000

Updated: 28 October 2003

Reviewed: 13 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

The ALOHA^� application software tip share functionality is designed to suggest the amount of money an order-entry employee adds to the tip share pool.� The tip share pool is distributed to other restaurant employees who do not directly receive tips.�

Tip share calculations are based on tippable sales (non-tippable sales are not included) and include inclusive taxes, but depending on the configuration, may or may not include exclusive taxes, comps, or promotions.� The Aloha application software calculates tip share on a per check basis, so the tip share amount may differ by a few cents from the total tips multiplied by the tip share percentage.

The Aloha application software does not display the person (or people) to receive any portion of the tip share amount, nor does any other employee see a tip share amount they are entitled to receive.

If tip share is not functioning properly, check the following:

1.        The default tip share is defined

2.        'Pays Tip Share' is selected for the job code

3.        The order mode is set as tippable

4.        A tip share event is not overriding the default tip share amount

5.        'Exclude from Tip Share Calculations' is not selected for the sales category

6.        Ensure that the job group in the job code is set to a number greater than zero.� If you are not using job groups for other functions, you can set the job group to an arbitrary number.

7.        Manually edit PRD.DBF and ensure the tip share percentages are set to zero (regardless of your desired tip share percentage)

8.        Verify if the tip share calculation configuration is set to your preference.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3083 promo promos

DBFDIFF.EXE

DBFDIFF.EXE

============================================================================

AKBID3084

Created: 18 April 2000

Updated: 20 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.4x � 5.3.x

============================================================================

DBFDIFF.EXE, found in the BIN folder, is used with the ALOHA^� application software Centralized Database Management (CDM) functionality.

It is used to compare two .DBF files and identify the changed records.� The changed records are then sent to the store as a single unit to update the store local copy.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3084

BOH Sales Report Calculated Cash Formula

BOH Sales Report Calculated Cash Formula

============================================================================

AKBID3085

Created: 20 April 2000

Updated: 10 October 2002

Reviewed: 29 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The ALOHA^� application software Back-of-House (BOH) Sales Report uses the following formula to figure the Calculated Cash:

Net Sales

+ Taxes

+ Sold Gift Certificates

+ Revenue Items

- Non-Cash Tenders (including tips and automatic gratuities)

+ Cash automatic gratuities¹

- Comps²

- Promotions²

+ Tip Reduction

+ Order Mode Charges

+ Surcharges

+ Not Redeemed Tenders³

+/- Petty Cash

¹The Aloha application software assumes that the employee keeps all cash automatic gratuities unless you enable 'Store Collects Employee Tips' in the job code.� Only include cash automatic gratuities in the calculation if you have enabled this option.

² The calculation depends on whether 'Include Comps In Net Sales' and 'Include Promos In Net Sales' are enabled.� Refer to document AKBID3006 for more information.

³ Refer to document AKBID3074.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID3006 Include Comps and Promos on Net Sales

AKBID3074 Non-Redeemed Payments

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3085 promo

Cloned Terminal Application Shortcuts

Cloned Terminal Application Shortcuts

============================================================================

AKBID3086

Created: 20 April 2000

Updated: 25 October 2000

Reviewed: No longer reviewed

Microsoft^�Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

If operating system (OS) and the ALOHA^� application software are installed on an order entry terminal using hard drive imaging or hard drive cloning software, some application shortcuts might not function properly.

The shortcut may refer to the UNC name of the hard drive image's original name, which can lead to serious errors in the Aloha application software.� Check the Aloha application shortcut paths if you are experiencing serious errors.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3086 blue screen of death bsd error general protection fault gp gpf

4.2x and 4.4x Full Screen 800x600 FOH Settings

4.2x and 4.4x Full Screen 800x600 FOH Settings

============================================================================

AKBID3087

Created: 25 April 2000

Updated: 11 January 2001

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 4.4x

============================================================================

In order to run the ALOHA^� application software version 4.4x and lower Front-of-House (FOH) in full screen 800x600 mode, then you must set the Microsoft^� Windows^� screen resolution to 800x600 and set the font size to Large Fonts.

There are not any settings within the Aloha application software software that control the screen size.

Refer to document AKBID1165 for more screen resolution options and resolution options for all versions of the Aloha application software.�

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1119 FOH Adjustable Resolution Settings

AKBID1165 FOH Screen Resolution Settings

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3087

Separate Tip and Auto-Gratuity Tracking

Separate Tip and Auto-Gratuity Tracking

============================================================================

AKBID3088

Created: 1 May 2000

Updated: 20 July 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 4.255 � 5.3.x

============================================================================

The ALOHA^� application software can print a '*** Tip Tracking ***' section on the employee checkout and clock-out that separates tips and automatic gratuities.� Perform one of the following to enable this option:

In versions 4.2x, add the line SEPARATETIPTRACKING=TRUE (if it does not already exist) to the ALOHA.INI file in the NEWDATA folder, and refresh the system.

In versions 4.4x, open Maintenance, and select Labor/Server Checkout.� Select 'Separate Tips and Grat in Tip Tracking', and refresh the system.

In versions 5.0x and higher, open Aloha Manager, select Maintenance/Store Settings/Printing/Employee Checkouts Cfg, and select 'Separate Tips and Grat in Tip Tracking'.� Refresh the system.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3088 check-out

Maintenance Only Creates TAB.CDX File

Maintenance Only Creates TAB.CDX File

============================================================================

AKBID3089

Created: 26 April 2000

Updated: 9 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x

============================================================================

If the ALOHA^� application software Date-of-Business (DOB) is '00 00 0000' in the \NEWDATA\ALOHA.INI file, Maintenance only creates the TAB.CDX file when rebuilding CDX files.

Set the DOB to a true date to rebuild all CDX files.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3089 index

Using IBEREXE.DLL to Disable the Super-Secret-Password

Using IBEREXE.DLL to Disable the Super-Secret-Password

============================================================================

AKBID3090

Created: 26 April 2000

Updated: 26 February 2002

Reviewed: 5 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

Creating an IBEREXE.DLL file in the ALOHA^� application software BIN folder disables the Back-of-House (BOH) Super-Secret-Password (SSP).�

You can create an IBEREXE.DLL file using the following command to disable the BOH SSP:

ECHO 1 > %IBERDIR%\BIN\IBEREXE.DLL

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3090 alt alt-x altx back backdoor door remove super user superuser x

EXITING File

EXITING File

============================================================================

AKBID3091

Created: 22 May 2000

Updated: 16 February 2004

Reviewed: 16 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x.x

============================================================================

The %IBERDIR%\TMP\EXITING file signals other ALOHA^� application software terminals that the local terminal is shutting down or is not currently running IBER.EXE or IBERQS.EXE.� IBER.EXE and IBERQS.EXE create a local copy of this file upon exiting and delete the local EXITING file when they start.

The file warns other terminals (and GRIND.EXE/GRINDQ.EXE in SuperSites) not to create a network connection since the terminal is restarting.

Front-of-House (FOH) terminals will not create a network connection to the terminal until the file no longer exists.� In SuperSites, GRIND.EXE and GRINDQ.EXE halt and wait until the file no longer exists.� If you experience problems with undesired EXITING files on FOH terminals, you can configure the IBERCFG.BAT to automatically delete the EXITING file by inserting the following line in the IBERCFG.BAT at a point where the LOCALDIR system environment variable has already been declared:

ECHO Y | DEL %LOCALDIR%\TMP\EXITING

If an EXITING file exists on the file server (or a terminal acting as the file server), the FOH terminals continuously reboot until the file is removed.� If you are running the FOH on your file server without using a looping batch file to automatically restart the FOH after exiting, then the FOH cannot delete the EXITING file since it did not restart.� To resolve this, use a batch file that starts FOH and then deletes the EXITING file after the FOH shuts down rather than just running IBER.EXE or IBERQS.EXE directly.� For example:

START /WAIT %LOCALDIR%\BIN\IBER.EXE

ECHO Y | DEL %LOCALDIR%\TMP\EXITING

EXIT

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3091 over restart

MSYNC File

MSYNC File

============================================================================

AKBID3092

Created: 26 April 2000

Updated: 8 January 2003

Reviewed: 6 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

============================================================================

The existence of an MSYNC file in the ALOHA^� application software master terminal's DATA folder informs the other Front-of-House (FOH) terminals that the master terminal is synchronizing data with the file server.

The other FOH terminals do not start synchronization until the master terminal deletes this file.

If the FOH terminals continually display a message stating 'Waiting for Multi Sync to Complete', perform the following:

1.        Verify if the TERMSTR environment variable is set and is correct on the file server and each terminal.

2.        Verify if the SERVER environment variable is set and is correct on the file server and each terminal.

3.        Check the Debugging-Output-Files (debouts) on the terminals for further causes.� Refer to document AKBID1134 for more information.

The most common cause of this problem is installing the FOH and Back-of-House (BOH) on the same computer, but not assigning the computer's network name according to the TERMSTR and terminal number.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1051 Aloha Application Software Flag and Marker Files

AKBID1134 Debouts

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3092 multiserver multisync

PULLDONE File

PULLDONE File

============================================================================

AKBID3093

Created: 26 April 2000

Updated: 29 September 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

Used in ALOHA^� application software SuperSites, the master terminal created the PULLDONE file in the store's folder on the file server when the master terminal has completed file synchronization with the file sever.

The PULLDONE file informs GRIND.EXE and GRINDQ.EXE to start processing again after the Front-of-House (FOH) terminals restart because of a refresh or the End-of-Day (EOD) process.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3093

FOH Restarts When Reading System Parameters

FOH Restarts When Reading System Parameters

============================================================================

AKBID3094

Created: 27 April 2000

Updated: 8 May 2000

Reviewed: 6 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

A STOP file in the TMP folder on the file server will cause the ALOHA^� application software Front-of-House (FOH) to restart when it is reading the system parameters.

In versions 4.4x and lower, open Control, and select 'Start Front of House' from the System drop-down menu in order to delete the STOP file.

In versions 5.0x and higher, open Aloha Manager, and select 'Start Front of House' from the Utilities drop-down menu to delete the STOP file.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1051 Aloha Application Software Flag and Marker Files

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3094 continuously reboots restarts

Network Name Unexpectedly De-registered

Network Name Unexpectedly De-registered

============================================================================

AKBID3095

Created: 27 April 2000

Updated: 30 July 2002

Reviewed: 3 February 2004

Microsoft Windows Versions: Windows 95, Windows 98, Windows Me

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The 'Network Name Unexpectedly De-registered' error typically occurs on file servers using the Microsoft^� Windows^� 95, Windows 98, or Windows Millennium Edition (Me) operating system running the ALOHA^� application software Front-of-House (FOH) and Back-of-House (BOH) together on the same computer without using the NONET variable.� CTLSVR.EXE (Control Server) and CTL.EXE (Control) require the NONET variable to coexist with the FOH.

It can also occur if the lana numbers are not configured properly (refer to document AKBID1018) or if network services are not enabled.

============================================================================

See also:

Aloha POS QuickService or TableService User Manual

AKBID1010 Aloha Application Software System Environment Variables

AKBID1018 Network Lana Numbers

AKBID1116 File Server/Terminal Limitations

AKBID3009 CTLSVR.EXE Registry Variables

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3095 boh/foh bohfoh foh/boh fohboh terminal/server

Synchronization of Data Fails

Synchronization of Data Fails

============================================================================

AKBID3096

Created: 27 April 2000

Updated: 23 October 2001

Reviewed: 10 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

============================================================================

The ALOHA^� application software Front-of-House (FOH) synchronizes the following folders with the Back-Of-House (BOH) each time the system starts: BIN, BMP, DATA, RECIPE.

The Aloha application software requires each FOH terminal to contain an Aloha application software folder with the following folders inside of it: BIN, BMP, DATA, EDC (for credit card transactions), NEWBIN (required for BIN synchronization), RECIPE, and TMP (for debugging files).� Synchronization does not complete without the required folders.

Synchronization might also fail if the BIN, BMP (versions 5.0x and lower), DATA, or RECIPE folders on either a FOH terminal or the BOH file server contain a folder inside of them.� For example, a C:\ALOHA\DATA\OLDDATA folder might impede the synchronization process.� The Aloha application software versions 5.2x and higher compensate for subfolders within the BMP folder in order to enable multi-resolution bitmaps (refer to document AKBID1201).

Review the Debugging-Output-Files (debouts) on the terminals for further causes.� Refer to document AKBID1134 for more information on debouts.

============================================================================

See also:

Aloha QuickService or TableService User Manuals

AKBID1134 Debouts

AKBID1201 Multi-resolution Bitmap Folders

AKBID3013 Sub-Folders Inside System Folders

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3096 copy copying fail failing fails subdirectories subdirectory synchronizing

Failed to Read Error Code

Failed to Read Error Code

============================================================================

AKBID3097

Created: 27 April 2000

Updated: 25 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

ALOHA^� Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

The error 'Failed to read error code nnnn' refers to the failure to read a configuration file.� Refer to document AKBID1042 to determine the erroneous file.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1042 Aloha Application Software Database Files

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3097

Corrupt Printer Log

Corrupt Printer Log

============================================================================

AKBID3098

Created: 27 April 2000

Updated: 27 July 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

The ALOHA^� application software cannot initialize with a corrupt printer log.� The printer logs reside in the DATA folder on the file server and each Front-of-House (FOH) terminal.� They are labeled PRTn.LOG, where n is the printer ID number.

To bring the Aloha application software on line, move the corrupted printer log on the file server to a temporary folder, and restart the FOH terminals.

Use the corrupted log along with debugging files to assist with diagnosing the cause of the problem.�

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1157 Aloha Application Software Printer Logs

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3098 corruption

QS Manager Access Buttons from Any Screen

QS Manager Access Buttons from Any Screen

============================================================================

AKBID3099

Created: 5 April 2000

Updated: 14 May 2002

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService

Aloha POS Versions: 3.8x � 5.0x

============================================================================

ALOHA^� application software versions 5.2x and higher verify item eligibility prior to applying a promotion, so this document is not applicable to versions 5.2x and higher.

To limit access of a payment or panel to only a manager (but still available on all employee screens), create a script that calls a mock promotion and then the prohibited function.� Configure the mock promotion to New Price, Manager Needed, Active, and a Maximum Per Check of 99.� When you create the script, do not select 'Continue script on error or cancel'.

When the user selects the button, the Front-of-House (FOH) prompts for a manager password, and continues to the true function of the script.

============================================================================

See also:

Aloha QuickService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3099 require restrict

FOH Flash Report Labor Information is Blank

FOH Flash Report Labor Information is Blank

============================================================================

AKBID3100

Created: 5 May 2000

Updated: 14 February 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

ALOHA^� Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

If the Front-of-House (FOH) Flash Report displays blank labor information, then you must create and configure one or more labor groups in the Back-of-House (BOH).� Refer to the Aloha QuickService or TableService User Manual for more information on creating and configuring labor groups.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3100 no nothing

Edit Punches Application does not Display Properly

Edit Punches Application does not Display Properly

============================================================================

AKBID3101

Created: 4 May 2000

Updated: 14 February 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

If the ALOHA^� application software 'edit punches' dialogue (EDOLDTM.EXE or EDTPUNCH.DLL) does not display properly, edit WIN.INI in the Windows folder, add the following lines to the [IBERTECH] section if they do not already exist and restart the computer:

EDOLDTM_EMP NO._WIDTH=70

EDOLDTM_EMPLOYEE_WIDTH=70

EDOLDTM_TIME IN_WIDTH=70

EDOLDTM_TIME OUT_WIDTH=70

EDOLDTM_JOBCODE_WIDTH=70

EDOLDTM_RATE_WIDTH=70

EDOLDTM_TIPS_WIDTH=70

EDOLDTM_TIPPABLE SALES_WIDTH=85

EDOLDTM_STORE_WIDTH=70

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3101 large punch small

BackOffice Interface Startup Shortcut Location

BackOffice Interface Startup Shortcut Location

============================================================================

AKBID3102

Created: 9 May 2000

Updated: 11 September 2002

Reviewed: 9 December 2003

Microsoft Windows Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 3.6x � 5.3.x

============================================================================

The shortcuts that automatically start the ALOHA^� application software BackOffice interfaces when Microsoft^� Windows^� starts are located in the All Users StartUp folder.

To access the All Users StartUp folder in Windows NT^�, open Windows Explorer, and path out %WINDIR%\PROFILES\ALL USERS\START MENU\PROGRAMS\STARTUP.

To access the All Users StartUp folder in Windows 2000, Windows XP, or Windows Server 2003, open Windows Explorer, and path out DOCUMENTS AND SETTINGS\ALL USERS\START MENU\PROGRAMS\STARTUP.

To access the All Users Start Up group in Windows 95, Windows 98, or Windows Millennium Edition (Me), open Windows Explorer, and path out %WINDIR%\ALL USERS\START MENU\PROGRAMS\STARTUP.

============================================================================

See also:

Aloha Accounts Receivable User Manual

Aloha Delivery/Frequent Buyer User Manual

Aloha Gift Certificate Manager User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3102

style='mso-spacerun:yes'>� 2003

BOH CTL3D32.DLL Error

BOH CTL3D32.DLL Error

============================================================================

AKBID3103

Created: 11 May 2000

Updated: 21 October 2002

Reviewed: 9 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

If the ALOHA^� application software displays an error regarding the CTL3D32.DLL file, perform the following:

1.        Close all Aloha software applications, processes, and services.

2.        If you are using Microsoft^� Windows^� 95, Windows 98, or Windows Millennium Edition (Me), delete all copies of CTL3D32.DLL on the hard drive except for the one that exist in the Windows SYSTEM folder.

3.        If you are using Windows NT^�, Windows 2000, or Windows XP, delete all copies of CTL3D32.DLL on the hard drive except for the one that exist in the Windows SYSTEM32 folder.

4.        If you are using Windows 95, Windows 98, or Windows Me, unzip WIN95DLL.ZIP and WIN95DLL2.ZIP from the ALOHATS folder on the Aloha Installation CD to the Windows SYSTEM folder.� Do not overwrite newer versions of the files.� You may have to restart the computer in MS-DOS^� mode to perform this step, since Windows might be using some of the files.

5.        If you are using Windows NT, Windows 2000, or Windows XP, unzip WINNTDLL.ZIP and WINNTDLL2.ZIP from the ALOHATS folder on the Aloha Installation CD into the Windows SYSTEM32 folder.� Do not overwrite newer versions of the files.� You might have to employ the SETUPSYS.EXE utility to perform this step, since Windows might be using some of the files.� Refer to document AKBID1012 for more information.

6.        Restart the computer.

============================================================================

See also:

AKBID1012 Aloha Application Software Utility Description and Usage

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected]..

Additional query words: 3103

Shutdown Terminal

Shutdown Terminal

============================================================================

AKBID3104

Created: 12 May 2000

Updated: 29 September 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: Windows 95, Windows 98, Windows Me

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The ALOHA^� application software 'Shutdown Terminal' Front-of-House (FOH) Manager Function instructs Microsoft^� Windows^� to perform a shutdown.�

If the AUTOEXIT variable is enabled, the terminal automatically restarts after the shutdown.� If the AUTOEXIT variable is not enabled, the terminal does not automatically restart.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1175 Aloha Terminal Restart Options

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3104 shut down

Barcodes for Basic House Accounts

Barcodes for Basic House Accounts

============================================================================

AKBID3105

Created: 17 May 2000

Updated: 6 September 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.0x � 5.3.x

============================================================================

The ALOHA^� application software basic house accounts support touch screens, magnetic stripe cards, and barcodes to input the customer's account number.� You can use a serial based-scanner or a keyboard-based scanner, but it must conform to the parameters listed in document AKBID1068.

If you are using a touch screen to enter the account information, the Aloha application software requires the exact account number or account name, but barcode information is limited to the account number.�

Refer to document AKBID1198 for more information on using magnetic stripe cards for house accounts.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1068 Barcodes and Scanners

AKBID1198 Magnetic Stripe Card Information

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3105

Separating Chits on a Single Printer

Separating Chits on a Single Printer

============================================================================

AKBID3106

Created: 18 May 2000

Updated: 18 June 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

ALOHA^� Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

============================================================================

To create separate chits on a single printer, use the 'Reroute Printer' event.� The 'Reroute Printer' event creates separate chits, while the 'Reroute Printer Group' does not.

For example, if the customer requires a separate 'Hot' chit and a separate 'Cold' chit on a single printer, perform the following:

1.        Create a 'Mock Cold' printer and a 'Mock Hot' printer.� Since neither of these printers is real, do not assign them to a terminal.

2.        Create a 'Mock Cold' printer group and a 'Mock Hot' printer group.

3.        Add the 'Mock Cold' printer to the 'Mock Cold' printer group, and add the 'Mock Hot' printer to the 'Mock Hot' printer group.

4.        Assign the items to either the 'Mock Cold' or 'Mock Hot' printer group.

5.        Create a 'Reroute Printer' event to reroute the 'Mock Cold' printer to the physical kitchen printer.

6.        Create a 'Reroute Printer' event to reroute the 'Mock Hot' printer to the physical kitchen printer.

The printer now produces separate chits for the 'Mock Cold' items and the 'Mock Hot' items.

In versions 5.007 through 5.026, you may have to disable stand-alone chit printing (part of the Aloha application software fault tolerance capabilities) in order for the functionality described in this document to function properly.� To disable stand-alone chit printing, edit the ALOHA.INI in the Aloha application software NEWDATA folder, set the DISABLESTANDALONECHITPRINT variable to TRUE (for example, DISABLESTANDALONECHITPRINT=TRUE), and refresh the system.

============================================================================

See also:

Aloha QuickService and TableService User Manual

AKBID1121 Reroute All Chits to Local Printers

AKBID3193 Printing One Items on Two Chits Using a Single Printer

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3106 bar cut different multiple remote

Windows Screensavers Causing Slow Terminals and Errors

Windows Screensavers Causing Slow Terminals and Errors

============================================================================

AKBID3107

Created: 18 May 2000

Updated: 18 March 2003

Reviewed: 26 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

Microsoft^� Windows^� screensavers (especially Open GL or 3D screensavers) can cause ALOHA^� application software terminals run slow because they can over-burden the system processor.�

This can produce errors and activity that appear to be network related.�

Ensure the file server and all Front-of-House (FOH) terminals do not have Windows screensavers enabled.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3107 error floating general protection fault gp gpf logo

Setting RDB Grind Screen Positions

Setting RDB Grind Screen Positions

============================================================================

AKBID3108

Created: 19 May 2000

Updated: 1 November 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

Perform the following to set the screen position for a live data feed Grind window:

1.        Position and size the Grind window on the desktop.

2.        Right-click the Grind window title bar, and select Close.

The Grind should restart in the new position with the new size.� If you fail to close the Grind window manually and CTLSVR.EXE (Control Server) closes it later, the new position and size are not saved.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3108 location supersite

Re-synchronizing .DBF Files From an RDB

Re-synchronizing .DBF Files From an RDB

============================================================================

AKBID3109

Created: 19 May 2000

Updated: 22 November 2002

Reviewed: 15 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

If the .DBF files lose synchronization with the relational database (RDB), close all open ALOHA^� software applications and services, start DBCONFIG.EXE from the BIN folder, and select the following:

-          Attended

-          Debug

-          Create DBF Files

Verify the IBERDIR, set the output folder to the NEWDATA folder, and click Run.

Restart ALOHAMGR.EXE (Aloha Manager), and refresh the system.

While this function does not cause the loss of current sales or historical data, errors may occur if the current transaction log references an entry that no longer exists in the .DBF files.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1067 DBUP.EXE and DBCONFIG.EXE

AKBID1093 Windows 2000 File Server Setup

AKBID1094 Windows 2000 File Server/Terminal Setup

AKBID1131 Installing a New RDB Over and Existing RDB

AKBID3108 Setting RDB Grind Positions

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3109 2000 7.0 access msde sql supersite

The Remote Variable

The Remote Variable

============================================================================

AKBID3110

Created: 22 May 2000

Updated: 13 May 2003

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The REMOTE system environment variable enables the use of a remote copy of the ALOHA^� application software Back-of-House on another network computer besides the Aloha application software file server, but in doing so, it instructs CTLSVR.EXE (Control Server) to not attempt to automatically grind new dated folders or broadcast file server functionality.

The REMOTE variable only applies to ALOHAMGR.EXE (Aloha Manager), CTL.EXE (Control), and Control Server.� It does not apply to IBER.EXE or IBERQS.EXE.� Apply the REMOTE variable to the application's command line.� For example:

\\ALOHABOH\BOOTDRV\ALOHA\BIN\ALOHAMGR.EXE /REMOTE

Use of the REMOTE variable outside of the proper environment or with other Aloha applications can result in system instability or failure.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1040 Run Control and Maintenance on a Remote Workstation

AKBID1113 Remote Aloha Manager

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3110

How to Shut Down the FOH Using a Keyboard

How to Shut Down the FOH Using a Keyboard

============================================================================

AKBID3111

Created: 24 May 2000

Updated: 7 September 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.65x � 5.3.x

============================================================================

To properly shut down the ALOHA^� application software Front-of-House (FOH), press and hold the following keys:

Ctrl � Shift � Alt � X

This closes open network connections and files, and stops IBER.EXE or IBERQS.EXE.

Depending on your AUTOEXIT and REBOOTNT system environment variable configuration, the FOH will either exit to the Windows desktop, log out of the terminal or restart the terminal.� Refer to document AKBID1175 for more information.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1010 Aloha Application Software System Environment Variables

AKBID1175 Aloha Terminal Restart Options

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3111 shutdown

HALT File

HALT File

============================================================================

AKBID3112

Created: 24 May 2000

Updated: 2 January 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

ALOHA^� application software no longer uses the C:\HALT file, although the Front-of-House (FOH) still creates it.

The HALT file was previously used to signal CONNMGR.EXE (Connection Manager) to restart, but the Aloha application software no longer uses Connection Manager.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3112

Serial Cash Drawer Compulsory Method

Serial Cash Drawer Compulsory Method

============================================================================

AKBID3113

Created: 31 May 2000

Updated: 13 March 2002

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The Compulsory Method drop-down list in cash drawer maintenance defines the serial connector pin number that sends the 'Drawer Closed' signal.� It is either the Clear to Send (CTS) pin or the Ring Indicator (RI) pin.� Compulsory cash drawers return status signals, so the ALOHA^� application software can react to cash drawers that have been left open.� Cash drawers that are driven by serial ports, OPOS or Star Micronics printers support compulsory signals.

If you define a compulsory method when there is not a compulsory-supporting cash drawer connected to the serial port, the Aloha application software will consider the cash drawer to always be open.

Other types of hardware can mimic the compulsory signal by setting the CTS or RI pin to 'high' or 'on' when the cash drawer is closed.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1004 Serial Pin Assignments

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3113

PRINTERBAUD in ALOHA.INI

PRINTERBAUD in ALOHA.INI

============================================================================

AKBID3114

Created: 1 June 2000

Updated: 1 June 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

ALOHA^� Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

You should always leave the PRINTERBAUD variable in ALOHA.INI set to the default '9600'.

This variable was added for earlier troubleshooting, and although it is still recognized by the Front-of-House (FOH), you should not change the variable from the default '9600' assignment.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3114

Enable or Disable Receipts when Manager Adjusts the Check

Enable or Disable Receipts when Manager Adjusts the Check

============================================================================

AKBID3115

Created: 2 June 2000

Updated: 13 December 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

Perform the following to enable or disable a receipt when a manager adjusts a check (for example, a void, comp, or promotions) in the ALOHA^� application software:

1.        Open Aloha Manager

2.        Select Maintenance/Store Settings/Printing/Check Style

3.        Select or clear 'Don't auto-print when manager adjusts checks'

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3115 promo promos

SERIALDRAWERCOUNT in ALOHA.INI

SERIALDRAWERCOUNT in ALOHA.INI

============================================================================

AKBID3116

Created: 2 June 2000

Updated: 2 June 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The ALOHA^� application software sends a succession of sixty zeroes (0) through the serial port to signal a serial-based cash drawer to open.� The number of zeros defaults to sixty, but you can use the SERIALDRAWERCOUNT variable in the ALOHA.INI to adjust the number of zeros sent.

Setting SERIALDRAWERCOUNT to a value of '0' is the default setting, and sixty zeroes are sent to the cash drawer.� If this value is higher than zero, the value represents the exact number of zeroes sent to the cash drawer.

For example:

Value

Number of zeroes sent to the cash drawer

SERIALDRAWERCOUNT=0

60

SERIALDRAWERCOUNT=1

1

SERIALDRAWERCOUNT=70

70

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3116 character signals

FOH 'Invalid Employee Number' Error

FOH 'Invalid Employee Number' Error

============================================================================

AKBID3117

Created: 6 June 2000

Updated: 16 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

If an employee is properly defined in the ALOHA^� application software database, but still receives an 'Invalid employee number' error in the Front-of-House (FOH), check the 'Number of Employee Digits' setting in the Back-of-House (BOH).� The number of digits in the employee ID number must match the number of digits defined in the 'Number of Employee Digits' setting, otherwise the employee must use leading zeros when manually entering their ID number in the FOH.

Perform the following to access the 'Number of Employee Digits' setting:

Open Aloha Manager

Select Maintenance/Store Settings/Security.�

Select the 'POS Password Settings' subtab, and set the number of digits in the 'Number Employee' text box.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3117

FOH 'Not Authorized for Video' Error

FOH 'Not Authorized for Video' Error

============================================================================

AKBID3118

Created: 6 June 2000

Updated: 2 June 2003

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.0x � 5.3.x

============================================================================

If the Front-of-House (FOH) displays the error 'Not authorized for video', then your database is configured to use a Remote-Display-System (RDS) while the HASP^� ALOHA^� application software security key is not programmed to allow its use. �

Using an ALOHA.INI from a database with an RDS configured in it typically causes this.� The Back-of-House (BOH) does not allow you to access RDS settings (since the key is not programmed for it), so you must edit the ALOHA.INI, and assign the USEMONITORS variable to a value of FALSE (for example, USEMONITORS=FALSE).

Since the FOH terminals check for this value prior to synchronizing their data with the file server, you have to manually copy the new ALOHA.INI from the file server to the DATA folder on each FOH terminal.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3118 disable

BOH Cool Interface Selection Only Displays 'Default'

BOH Cool Interface Selection Only Displays 'Default'

============================================================================

AKBID3119

Created: 6 June 2000

Updated: 19 September 2002

Reviewed: 12 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

If the Cool Interface selection in the ALOHA^� application software Back-of-House (BOH) only displays the 'Default' interface selection, replace the MM.INI in the NEWDATA and DATA folders with the MM.INI from \ALOHATS\SAMPDATA.ZIP or \ALOHATS\IBERCAFE.ZIP on the Aloha Installation CD.

Ensure that the required bitmaps reside in the BMP folder before enabling the cool interface.

For more information on the Enhanced Graphical Interface (EGI) available in versions 5.2.5.x and higher, refer to document AKBID1216.

============================================================================

See also:

Aloha TableService User Manual

AKBID1216 Enabling and Configuring FOH Enhanced Graphical Interface

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3119 add interfaces

style='mso-spacerun:yes'>� 2003

Two Cash Drawers Connected to a Single Printer

Two Cash Drawers Connected to a Single Printer

============================================================================

AKBID3120

Created: 12 June 2000

Updated: 16 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

Most receipt printers provide a single RJ11 outlet to plug a cash drawer into the printer, and they require an external RJ11 splitter to create the dual cash drawer outlets.

Each cash drawer connected to the printer with the RJ11 splitter must be designated as drawer number one or drawer number two in the ALOHA^� application software Back-of-House (BOH).� Designate the drawer as '1' or '2' in the 'Drawer Number' text box in the BOH.

Most cash drawers come pre-wired as drawer number one.� You must change the internal wiring of the second cash drawer to designate it as the second drawer.� For example, some cash drawers use the red wire and the black wire for the signal to open the cash drawer.� For cash drawer number one, the red wire connects to a green wire and the black wire connects to another black wire.� Cash drawer number two may require the red wire connected to a green wire, and the black wire connected to a yellow wire.

The wire colors that designate the cash drawer number vary from drawer to drawer.� Contact the cash drawer manufacturer for specific wire assignments.

Once the wiring is correct, plug each cash drawer into one of the ports on the RJ11 splitter.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID3154 Epson Printer Enunciators

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3120

Setting the Credit Card Refund Limit

Setting the Credit Card Refund Limit

============================================================================

AKBID3121

Created: 12 June 2000

Updated: 7 January 2002

Reviewed: 18 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The ALOHA^� application software uses separate variables to set the maximum credit card refund limit for Front-of-House (FOH) transactions and Back-of-House (BOH) transactions (using EDC.EXE).

To set the FOH limit, edit ALOHA.INI in the NEWDATA folder, and add the line MAXCCREFUNDLIMIT=n if it does not already exist, where n is the refund limit (for example, MAXCCREFUNDLIMIT=1000.00).� Set the variable to 0.00 for no limit.

To set the BOH limit for transactions originating from EDC.EXE, edit EDC.INI in the EDC folder, and add the line CC_REFUND_LIMIT=n to [SYSTEM] section if it does not already exist, where n is the refund limit (for example, CC_REFUND_LIMIT=1000.00).� Set the variable to 0.00 to disable refunds.� The limit defaults to $200.00 if you do not set the variable.

============================================================================

See also:

Aloha QuickService or TableService User Manual

Aloha Credit Card User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3121

style='mso-spacerun:yes'>� 2003

Show Subtotal on Customer Display

Show Subtotal on Customer Display

============================================================================

AKBID3122

Created: 22 June 2000

Updated: 11 July 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

ALOHA^� Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The 'Show Subtotal on Pole Display' option displays a running total on the customer display as each new item is added to the check.� The displayed total also includes the sales tax, which is not displayed without this option.

To enable this option, open Aloha Manager, and select Maintenance/Store Settings/User Interface.� Select the POS Settings tab, and select 'Show Subtotal in Pole Display'.

============================================================================

See also:

Aloha QuickService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3122 line pole rear

Print FOH Flash Report

Print FOH Flash Report

============================================================================

AKBID3123

Created: 11 July 2000

Updated: 7 March 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.4x � 5.3.x

============================================================================

To enable the option to print the ALOHA^� application software Front-of-House (FOH) Flash Report in versions 5.009 and lower, add the following line to the ALOHA.INI in the NEWDATA folder (if it does not already exist), and refresh the system:

FLASHPRINT=TRUE

To enable the option to print the Aloha application software FOH Flash Report in versions 5.010 and higher, open Aloha Manager, select \Maintenance\Store Settings\Printing\Reports\Print, enable 'Print Flash Report', and refresh the system.

This enables a Print button on the 'Entire Day Summary' page of the report.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3123

Delivery/Frequent Buyer POS Discount ID

Delivery/Frequent Buyer POS Discount ID

============================================================================

AKBID3124

Created: 11 July 2000

Updated: 11 July 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 3.65x � 5.3.x

============================================================================

The POS Discount ID in BackOffice Delivery/Frequent Buyer Bonus Plan Maintenance refers to the ID number assigned to the promotion by the ALOHA^� application software Back-of-House (BOH).

============================================================================

See also:

Aloha Delivery/Frequent Buyer User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3124

Inventory Control Event Viewer is Empty

Inventory Control Event Viewer is Empty

============================================================================

AKBID3125

Created: 12 July 2000

Updated: 12 July 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

If the ALOHA^� application software Inventory Control Event Viewer is empty, the IMAGEHLP.DLL file in the Windows SYSTEM or SYSTEM32 folder might be corrupt or otherwise unusable.� Perform the following to restore a copy of the file from the Aloha Installation CD:

1.        Select Start/Run.� Enter '<CD Drive>:\CIM\INVENTORY\SETUP\INSTALL\SETUP.EXE /X' and click OK.

2.        Select IMAGEHLP.DLL from the list and click OK.

3.        Select the folder (Windows SYSTEM or SYSTEM32, depending on the operating system), replace the old version, and restart the computer.

============================================================================

See also:

Aloha Inventory Control User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3125 blank

Inventory Control Event Viewer Warns of Uncosted Items

Inventory Control Event Viewer Warns of Uncosted Items

============================================================================

AKBID3126

Created: 12 July 2000

Updated: 12 July 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

ALOHA^� application software Inventory Event Viewer warnings containing 'uncosted' errors are not critical and do not stop processing.� The errors indicate that you are using more inventory than you are recording as available for sale.�

Common reasons for this are current day invoices not processed prior to current day sales or recipe/sales item maintenance is overstating usage.

============================================================================

See also:

Aloha Inventory Control User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3126

'Current period ends' is Blank in Inventory Control

'Current period ends' is Blank in Inventory Control

============================================================================

AKBID3127

Created: 12 July 2000

Updated: 10 October 2002

Reviewed: 29 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

If the 'Current period ends' drop-down menu is blank when you define accounting periods in the ALOHA^� application software Inventory Control System Parameters, you must generate accounting periods to list in the drop-down box.� Perform the following to generate accounting periods:

1.        Open Inventory Control and log in as an administrator.

2.        Select File/Parameters/System Parameters.

3.        Select the Accounting Periods tab.

4.        Select values for Type, Ends On, and Day, and click 'Generate Accounting Periods'.

The 'Current period ends' drop-down menu should now be populated.

============================================================================

See also:

Aloha Inventory Control User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3127

Defining the BackOffice Messages Folder Location

Defining the BackOffice Messages Folder Location

============================================================================

AKBID3128

Created: 17 July 2000

Updated: 10 October 2003

Reviewed: 10 October 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, BackOffice

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

By default, the ALOHA^� application software Front-of-House (FOH) and BackOffice applications write request and answer files to the %IBERDIR%\DELIVERY\MESSAGES folder on the file server in order to communicate with each other, but you can use the BACKOFFICEDIR system environment variable to route the request and answer files to a different location. �This is required if you are in a SuperSite environment or if you are using a stand-alone BackOffice file server (in any environment).�

The BACKOFFICEDIR variable replaces the %IBERDIR%\DELIVERY folder, but not the MESSAGES folder.� The MESSAGES folder must reside in the BACKOFFICEDIR folder.� For example, if the BackOffice application on the SuperSite or BackOffice file server uses the D:\ALOHA\DELIVERY\MESSAGES folder for messages, the BACKOFFICEDIR variable on the FOH terminals must be set to:

BACKOFFICEDIR=\\ALOHABOH\BOOTDRV\%IBERROOT%\DELIVERY

Using stand-alone BackOffice file servers to enhance fault tolerance both SuperSite and non-SuperSite systems.

============================================================================

See also:

AKBID1010 Aloha Application Software System Environment Variables

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3128 a/r accounts buyer certificate delivery frequent gift path receivable remote

TEKVisions Keyboard Error

TEKVisions Keyboard Error

============================================================================

AKBID3129

Created: 17 July 2000

Updated: 17 July 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

ALOHA^� POS Versions: 4.2x � 5.3.x

============================================================================

Book-size PC's from TEKVisions might display a keyboard error on the BIOS screen and halt the system when booting without a keyboard attached.� Perform the following to disable this error:

1.        Enter the system BIOS and select 'Advanced CMOS Setup' from the Advanced menu.

2.        Disable the 'Wait for F1 if error' option.

3.        Save the changes and exit the BIOS setup.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3129 tekvision

RunGrind File in the Data Folder

RunGrind File in the Data Folder

============================================================================

AKBID3130

Created: 17 July 2000

Updated: 23 August 2002

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

Remote copies of the ALOHA^� application software Control or Aloha Manager applications on a non-RDB system create a RunGrind file in the Data folder on the file server to instruct Ctlsvr.exe (Control Server) to start the Grind process (refer to document AKBID1016) for the current day's data.� This enables remote workstations to view current day's reports without running the Grind application locally, which requires a HASP^� security key.

============================================================================

See also:

AKBID1016 Grind Process and Errors

AKBID1040 Run Control and Maintenance from a Remote Workstation

AKBID1113 Remote Aloha Manager

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3130

QuickService Panel Background Bitmap

QuickService Panel Background Bitmap

============================================================================

AKBID3131

Created: 26 July 2000

Updated: 8 September 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService

Aloha POS Versions: 4.2x � 5.0x

============================================================================

You can enable a panel background bitmap in the ALOHA^� application software QuickService versions 5.0x and lower by enabling multimedia (cool interfaces).� If you enable cool interfaces, you are required to either build your own cool interface or use a cool interface from TableService.

Perform the following to use a TableService cool interface in QuickService:

1.        Extract either FABRIC.ZIP, MARBLE.ZIP, WAVE.ZIP from the ALOHATS folder on the Aloha Installation CD into the QuickService BMP folder.

2.        Extract MMCOMMON.ZIP from the ALOHATS folder on the Aloha Installation CD into the QuickService BMP folder.

3.        Extract MM.INI from \ALOHATS\IBERCAFE.ZIP on the Aloha Installation CD into the QuickService NEWDATA folder.

4.        Edit MM.INI and set DOMMGRAPHICS to TRUE, and set the MMSCHEME type.

5.        Copy MM.INI to the DATA folder.

============================================================================

See also:

Aloha QuickService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3131 panel

CNT Files in the DATA Folder

.CNT Files in the DATA Folder

============================================================================

AKBID3132

Created: 11 August 2000

Updated: 19 July 2002

Reviewed: 19 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.018 � 5.3.x

============================================================================

The ALOHA^� application software creates .CNT files in the DATA folder for tracking items enabled with Item Availability in the Front-of-House (FOH).� Although editing or deleting .CNT file associated with items actively tracked by Item Availability can cause unpredictable results, deleting unused or superfluous .CNT files will not have an adverse effect on the FOH since the tracking information is also stored in the TRANS.LOG (transaction log).

The .CNT file name uses the format ITMnnnnn.CNT, where nnnnn is the item number without leading zeros.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3132

TableService PLU Button BMP

TableService PLU Button BMP

============================================================================

AKBID3133

Created: 14 August 2000

Updated: 29 August 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

To place a bitmap on the submenu PLU button in the ALOHA^� application software, create a bitmap in the BMP folder and label it ITM999999.BMP.

============================================================================

See also:

Aloha TableService User Manual

AKBID3216 Enabling the TableService PLU Button

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3133

Tippable Sales Calculations

Tippable Sales Calculations

============================================================================

AKBID3134

Created: 8 September 2000

Updated: 3 March 2003

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The ALOHA^� application software does not include the following when figuring tippable sales on reports such as the Back-of-House (BOH) Labor Report:

-          Exclusive Taxes

-          Voids

-          Comps¹

-          Promotions¹

-          Surcharges

-          Revenue Items

-          Refunds

-          Items sold from categories with 'Exclude from Tipshare Calculations' enabled.

-          Items ordered using an order mode without 'Tippable Sales' enabled.

Inclusive taxes are included in tippable sales.

¹ Calculations depend in the whether the comp or promotion is marked as tippable in the comp or promotion's setup.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3134 promo

Gift Certificates Not in Aloha Manager Payments Menu

Gift Certificates Not in Aloha Manager Payments Menu

============================================================================

AKBID3135

Created: 22 August 2000

Updated: 7 December 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, BackOffice

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

Gift certificates do not appear in the ALOHA^� application software Back-of-House (BOH) Payments configuration menu if BackOffice gift certificates are enabled.�

If BackOffice gift certificates are enabled, access them by selecting Maintenance/Store Settings/Gift Certificates.

To disable BackOffice gift certificates and revert to basic gift certificates, close Aloha Manager, edit ALOHA.INI in the NEWDATA folder, set FASTECHGIFTCERT=FALSE, save the changes, and open Aloha Manager.�

============================================================================

See also:

Aloha QuickService or TableService User Manuals

Aloha Gift Certificate Manager User Manual

AKBID1085 Basic Gift Certificates

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3135

UNFORGIVING in Aloha.ini

UNFORGIVING in Aloha.ini

============================================================================

AKBID3136

Created: 25 September 2000

Updated: 25 September 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

The UNFORGIVING variable in the ALOHA^� application software Aloha.ini is always considered false regardless of the assignment (TRUE or FALSE).

Originally, if the variable were set to TRUE, the system would exit or 'crash' on certain error conditions, even if they were not necessarily going to lead to an unstable system.�

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3136

TableService Tender and Item Bitmaps

TableService Tender and Item Bitmaps

============================================================================

AKBID3137

Created: 8 September 2000

Updated: 12 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

You can assign bitmaps to ALOHA^� application software TableService item, modifier, and tender buttons.�

To assign a bitmap to an item or modifier button, copy the bitmap to the Aloha application software BMP folder, and label it ITMnnnnnn.BMP, where nnnnnn is the item ID number without the leading zeros.

To assign a bitmap to a tender's button, copy the bitmap to the Aloha application software BMP folder, and label it TDRnnn.BMP, where nnn is the tender ID number without the leading zeros.

Bitmaps sizes vary to user preference, the number of button rows and columns, and video resolution settings.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3137 bmps

Default EDC.EXE Window Size and Position

Default EDC.EXE Window Size and Position

============================================================================

AKBID3138

Created: 5 September 2000

Updated: 17 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

The default ALOHA^� application software does not enable you to adjust the EDC.EXE (EDC) window size.

Although you can change the EDC window position while the application is active, EDC will revert back to its default window position when EDC is restarted.� You cannot adjust the default window position.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3138 resize

Disabling Clock-in and Clock-out Chits

Disabling Clock-in and Clock-out Chits

============================================================================

AKBID3139

Created: 8 September 2000

Updated: 16 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

To access ALOHA^� application software clock-in and clock-out chit options, open Aloha Manager and select Maintenance/Store Settings/Labor, and select the Clock In/Out subtab.

If you select 'Disable Labor Reporting', neither clock-in nor clock-out chits will print.� This also disables the Front-of-House (FOH) Labor Report, but labor information is still available in other FOH reports.

To only disable clock-in chits, clear 'Print Clock-In'.� This configuration does not disable the FOH Labor Report.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID3153 Force Manager Approval for Employee Clock-in

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3139 clockin clockout

Hold Button is Replaced with a Reprint Check Button

Hold Button is Replaced with a Reprint Check Button

============================================================================

AKBID3140

Created: 7 September 2000

Updated: 7 December 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The ALOHA^� application software 'Allow to reprint own checks' job code option replaces the Front-of-House (FOH) Hold button with a Reprint Check button.� You must disable 'Allow reprint own checks' in order to re-enable the Hold button.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3140 disable override

Default Aloha Manager Window Size and Position

Default Aloha Manager Window Size and Position

============================================================================

AKBID3141

Created: 5 September 2000

Updated: 1 October 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

Although users can change the ALOHA^� application software Aloha Manager window size while the application is active, Aloha Manager versions 5.0x and lower revert back to its default window size when Aloha Manager is restarted.�

Aloha Manager versions 5.2x and higher remember the previous size settings and returns to them if Aloha Manager is restarted.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3141 resize

Changing the Default Aloha Manager HTML Page

Changing the Default Aloha Manager HTML Page

============================================================================

AKBID3142

Created: 8 September 2000

Updated: 7 December 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The ALOHA^� application software uses \HTML\Main.htm as the default Aloha Manager background page.� You can change the default background using one of the following two methods:

1.        Copy a new default background page to \HTML\Main.htm.

2.        Use the ALOHAMGRPAGE environment variable to define a different default background page.� For example, use SET ALOHAMGRPAGE=D:\Aloha\HTML\Default.htm to assign Default.htm as the background.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1010 Aloha Application Software System Environment Variables

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3142 alohamgr globe spinning

Users cannot Modify Items

Users cannot Modify Items

============================================================================

AKBID3143

Created: 11 September 2000

Updated: 11 September 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.0x � 5.3.x

============================================================================

If ALOHA^� application software users cannot modify items in the Front-of-House (FOH), verify if a sales category containing the items is designated the Pizza Category (refer to document AKBID1058).�

If items are in a sales category designated the Pizza Category, they are considered 'pizzas', and must follow the rules associated with modifying pizzas.� If the items do not follow these rules, the forced modifiers do not appear, nor can the user modify the item by pressing the Modify button.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1058 Pizza Modifiers

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected]..

Additional query words: 3143 can't

Using an Ampersand on a QuickService Button Label

Using an Ampersand on a QuickService Button Label

============================================================================

AKBID3144

Created: 12 September 2000

Updated: 4 November 2002

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

In order to display an ampersand (&) on an ALOHA^� application software QuickService button's label, you have to enter two ampersands (&&) when creating the button text.� The Front-of-House (FOH) automatically ignores the first ampersand and only display a single ampersand.

For example, to display 'Ham & Cheese' on a button, enter 'Ham && Cheese' in the button label's text box.�

============================================================================

See also:

Aloha QuickService User Manual

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3144 and sign

IPX/SPX Protocol

IPX/SPX Protocol

============================================================================

AKBID3145

Created: 25 September 2000

Updated: 18 February 2002

Reviewed: No longer reviewed

Microsoft Windows Versions: Windows 95, Windows 98, Windows Me

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

Since the IPX/SPX-compatible protocol is supported by NetBIOS (refer to document AKBID1075), it is compatible with the ALOHA^� application software.

If you are using the IPX/SPX-compatible protocol with Microsoft^� Windows^� 95, Windows 98, or Windows Millennium Edition (Me), you must enable NetBIOS compatibility in the protocol's network properties for it to function properly with the Aloha application software.

Windows NT^�, Windows 2000, and Windows XP enable NetBIOS compatibility by default.

============================================================================

See also:

AKBID1075 NetBIOS and the Aloha Application Software

AKBID1099 Network Troubleshooting

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3145 ipxspx

Payment Reconciliation Calculation

Payment Reconciliation Calculation

============================================================================

AKBID3146

Created: 4 October 2000

Updated: 7 November 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.4x - 5.3.x

============================================================================

The ALOHA^� application software Payment Reconciliation application (Payrecon.exe) includes all tendered payments in its calculations.� This includes non-redeemed payments (refer to document AKBID3074) and tips.

Petty Cash account activities and tips paid by a cashier to order takers are not accounted for in the calculation.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID3074 Non-redeemed Payments

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3146 payrecon

Using Modifiers with Item Availability

Using Modifiers with Item Availability

============================================================================

AKBID3147

Created: 4 October 2000

Updated: 4 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.2x � 5.3.x

============================================================================

Although the ALOHA^� application software Item Availability functionality does not let you directly access modifier menus to adjust the availability of modifiers, modifiers menus do reflect availability settings applied to the modifiers when added to a submenu as items.

Perform the following to enable users to assign item availability to modifiers:

1.        Create a submenu or submenus that include all of the modifiers as items in the submenu.�

2.        Create a designated menu to host the submenu or submenus created in step one, and add the submenu or submenus to the menu.

3.        Refresh the system.

To access the Modifier menu in the Front-of-House (FOH), select 'Next Menu' at the bottom of the Item Availability function screen until the Modifier menu appears.� Adjust the availability of the modifiers as you would regular items.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3147

Aloha Manager Failed Security Error

Aloha Manager Failed Security Error

============================================================================

AKBID3148

Created: 2 October 2000

Updated: 2 October 2000

Reviewed: 4 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

If Aloha Manager displays an error message stating 'Security setup failed.� Aloha Manager cannot log users in without a valid path to an Aloha data folder', perform the following:

1.        Verify if the IBERDIR environment variable is properly configured (refer to document AKBID1010).

2.        Verify if the DATA folder exists in the ALOHA^� application software folder.

3.        Use DBCONFIG.EXE to update the configuration files (refer to document AKBID1160).

============================================================================

See also:

AKBID1010 Aloha Application Software System Environment Variables

AKBID1160 Manually Upgrading Configuration Files in Aloha Manager

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3148

Auto Start BOH Terminal and Errors

Auto Start BOH Terminal and Errors

============================================================================

AKBID3149

Created: 28 September 2000

Updated: 26 April 2002

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.3x � 5.2x

============================================================================

IBERBOH.EXE was designed to enable users to connect POS printers to the ALOHA^� application software file server in order to print receipts and chits without running the Front-of-House (FOH) on the file server, which requires a license.� Since it was not fully developed and implemented, enabling it may cause the following errors to appear in DEBOUT.TXT:

CTLSVR: Failed to execute IBERBOH.EXE (2, file not found)

CTLSVR: Executing IBERBOH.EXE .� .� .

CTLSVR: Can't run c:\Aloha\Bin\Iberboh Term 1

To disable IBERBOH.EXE in versions 4.4x and lower, open Control and clear 'Auto Start BOH Terminal' from the System drop-down menu.

To disable IBERBOH.EXE in versions 5.0x and higher, open Aloha Manager, select Maintenance/Store Settings/System/Interfaces and clear 'Auto Start BOH Upon Startup'.

This functionality has been replaced with the Interface Server option in version 5.023 and higher.� Refer to document AKBID1181.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1181 Using Interface Server as an Aloha Printer Server

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3149

Editing Microsoft Windows Me Environment Variables

Editing Microsoft Windows Me Environment Variables

============================================================================

AKBID3150

Created: 28 September 2000

Updated: 26 August 2002

Reviewed: No longer reviewed

Microsoft Windows Versions: Windows Me

ALOHA^� Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 5.2x � 5.3.x

============================================================================

Although Microsoft^� Windows^� Millennium Edition (Me) enables you to add and edit system environment variables in the AUTOEXEC.BAT, you can not add additional tasks to the AUTOEXEC.BAT, such as the 'copy NEWBIN to BIN' commands, or the 'CALL C:\IBERCFG.BAT' command.

If you add information outside of system environment variables, Windows removes the information the next time the computer is restarted.

Because of this, the Aloha application software configuration applications (SETUPPOS.EXE and SETUPTRM.EXE) create an IBERCFG.BAT in the Aloha application software folder (for example, C:\ALOHA\IBERCFG.BAT) that declares system environment variables, updates the BIN folder, and starts IBER.EXE.� A shortcut to IBERCFG.BAT is added to the Windows StartUp folder.

============================================================================

See also:

AKBID1204 Default Aloha System Environment Variable Placement

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3150

TableService Open Item Options

TableService Open Item Options

============================================================================

AKBID3151

Created: 3 October 2000

Updated: 16 October 2000

Reviewed: 15 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The ALOHA^� application software enables two ways to specify, label, and price open items: using the 'Ask for Price' and 'Ask for Description' options in item maintenance or assigning the item ID between 30,100 and 30,199.

If you select the prior option, then you are not limited to an ID number range, and you can select the 'Ask for Price' and 'Ask for Description' options as needed.� To access the 'Ask for Price' and 'Ask for Description' options, open Aloha Manager and select Maintenance/Menu/Items/Miscellaneous.

If you select the latter option, you are required to assign the item an ID between 30,100 and 30,199.� You cannot disable the 'Ask for Price' prompt, nor can you disable the 'Ask for Description' prompt.�

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3151

style='mso-spacerun:yes'>� 2003

Items in Categories Have Zero Item Numbers

Items in Categories Have Zero Item Numbers

============================================================================

AKBID3152

Created: 3 October 2000

Updated: 2 January 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

If you are using ALOHA^� application software versions 5.0x and higher and install configuration files from versions 4.4x and lower without properly upgrading them, Aloha Manager might not display the data correctly.� For example, sales category maintenance display items with zero (000000) identification numbers.

To upgrade the data, refer to document AKBID1132 or AKBID1160.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1067 DBUP.EXE and DBCONFIG.EXE

AKBID1132 Installing a New .DBF Database Over an Existing Database

AKBID1160 Manually Upgrading Configuration File sin Aloha Manager

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3152 zeros

Force Manager Approval for Employee Clock-in

Force Manager Approval for Employee Clock-in

============================================================================

AKBID3153

Created: 3 October 2000

Updated: 18 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

To require the ALOHA^� application software to prompt for a manager each time an employee clocks-in, open Aloha Manager, select Maintenance/Store Settings/Labor/Scheduling, and enable the following:

-          Prompt for Manager Password if unscheduled

-          Use Schedule

-          Use Punctuality

To enable a job code to clock-in without requiring a manager, enable the 'Ignore labor schedule' job code setting.

To enable a manager to allow an employee to clock-in, enable Punctuality in the manager's access level.

After a manager has enabled an employee to clock-in, the employee much clock-in within the time frame specified by the 'Number of Minutes for Allow Clock-in Transaction' labor setting.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3153 clock clockin in must

Epson Printer Enunciators

Epson Printer Enunciators

============================================================================

AKBID3154

Created: 4 October 2000

Updated: 25 June 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The ALOHA^� application software supports Epson printers with internal and external enunciators (beepers).� To activate beeps after a print job has completed, specify a number of beeps in printer maintenance in Aloha Maintenance or Aloha Manager.

The Aloha application software sends beep requests to cash drawer port number one.� If you are using an internal beeper, set the dual in-line package (DIP) switches to select drawer number one.� If you are using an external beeper, configure or connect the beeper to cash drawer port number one, and configure or attach any cash drawers to cash drawer port number two.

If you configure or attach a cash drawer to an Epson printer's cash drawer port number one, and you have one or more printer beeps enabled, then the cash drawer will open each time the printer prints because it is attempting to initialize the beeper.� You must connect cash drawers to cash drawer port number two.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1002 Aloha Receipt and Kitchen Printer Settings

AKBID3120 Two Cash Drawers on a Single Printer

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected]

Additional query words: 3154 beep beeper buzz buzzer fire pop remote ring ringer

EVENTS.CFG Corruption

EVENTS.CFG Corruption

============================================================================

AKBID3155

Created: 9 October 2000

Updated: 3 June 2003

Reviewed: 16 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

Corruption of the ALOHA^� application software's event configuration file (EVENTS.CFG) can lead to events not initializing at the proper time (or not initializing at all).�

If you view the EVENTS.CFG file in the NEWDATA folder with a text editor, evidence of corruption includes unintelligible characters (for example, 'G��p_'), and multiple listings of the same event for the same time and date.�

Perform the following to remove corruption from EVENTS.CFG:

1.        Close (depending on the version) Maintenance or Aloha Manager.

2.        Print the EVENTS.CFG file that is in the NEWDATA folder or save it under a different name for later reference.

3.        Delete the EVENTS.CFG file in the NEWDATA folder.

4.        Restart Aloha Maintenance or Aloha Manager and navigate to event maintenance.

5.        Using the printed or backup copy of the EVENTS.CFG file, reconfigure the original events, leaving out the duplicate events caused by the corruption.

6.        Refresh the system.

Another cause of events not initializing is a Date-of-Business (DOB) setting out of synchronization with the system date by more than one day.

Verify that you do not have multiple event configuration files that are overwriting each other (refer to document AKBID3300).

Enable event-debugging output to the Debugging-Output-Files (debouts) in Aloha Manager/Maintenance/Store Settings/System/Aloha Settings, and review the debouts on the terminals for further causes.� Refer to document AKBID1134 for more information on debouts.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1134 Debouts

AKBID3300 Aloha FOH Reads Multiple Event Configuration Files

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3155 corrupt

WMF Pen Reader Pin-outs

WMF Pen Reader Pin-outs

============================================================================

AKBID3156

Created: 9 October 2000

Updated: 9 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x

============================================================================

The ALOHA^� application software requires the following serial port pin-outs for the WMF pen reader:

Pen Reader DB9

2

3

5

Serial Port DB9

3

2

5

Pen Reader DB9

2

3

5

Serial Port DB25

2

3

7

The WMF pen reader requires a 5v (at 250mA) power source on pin nine.� This is not provided by a standard serial port on pin nine or any other pin, so users must configure their own power source.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3156 db-9 db-25 pinout pinouts

AutoMenu not Initializing

AutoMenu not Initializing

============================================================================

AKBID3157

Created: 9 October 2000

Updated: 3 June 2003

Reviewed: 16 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.8x � 5.3.x

============================================================================

If an ALOHA^� application software AutoMenu does not initialize, perform the following:

1.        Verify if an event to set the AutoMenu exists in event maintenance.

2.        Verify if the events configuration file (EVENTS.CFG) is corrupted (refer to document AKBID3155)

3.        Verify that you do not have multiple event configuration files that are overwriting each other (refer to document AKBID3300).

4.        Verify if the Date-of-Business (DOB) setting is not out of synchronization with the system date by more than one day.

============================================================================

See also:

Aloha TableService User Manual

AKBID3155 EVENTS.CFG Corruption

AKBID3300 Aloha FOH Reads Multiple Event Configuration Files

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3157 auto menu

Use Any Area Code in Delivery/Frequent Buyer

Use Any Area Code in Delivery/Frequent Buyer

============================================================================

AKBID3158

Created: 9 October 2000

Updated: 9 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 3.65x � 5.3.x

============================================================================

To enable the use of any area code when entering new customers into the ALOHA^� application software Delivery/Frequent Buyer interface, do not enter any valid area codes when configuring the system parameters.

============================================================================

See also:

Aloha Delivery/Frequent Buyer User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3158

Clock-out Chit Sales Calculation

Clock-out Chit Sales Calculation

============================================================================

AKBID3159

Created: 9 October 2000

Updated: 14 November 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The sales amount listed on ALOHA^� application software clock-out chits is the tippable sales amount, not 'true' or gross sales.� Refer to document AKBID3134 for the tippable sales calculation.

============================================================================

See also:

AKBID3134 Tippable Sales Calculations

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3159 clock clockout out

Exporting BackOffice General Ledger Activity

Exporting BackOffice General Ledger Activity

============================================================================

AKBID3160

Created: 13 October 2000

Updated: 18 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

To export general ledger account activity to a comma-separated-values (CSV) file using the ALOHA^� application software Inventory Control application, create a new job in Data Manager and link it to \BACKOFFICE\DATA MANAGER TEMPLATES\OTHER\GL ACTIVITY EXPORT.DMT.�

The job exports the information to a file labeled ACTIVITY.TXT in the C:\GL folder.� You can modify the file location and label in the job's properties.

The export file includes the account number, account name, date, and amount posted.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3160 gl

Product Mix Report Specific Items Only

Product Mix Report Specific Items Only

============================================================================

AKBID3161

Created: 12 October 2000

Updated: 12 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.8x � 5.0x

============================================================================

The 'Specific Items Only' option in the ALOHA^� application software Product Mix report settings instruct the application to report only the items listed in the selected item file.

Item files are text files stored in the DATA folder and use the .ITM extension (for example, BURGERS.ITM or SALADS.ITM).� Item files contain a list of item numbers (with or without leading zeros) to report when the item file is selected.

The following is an example of an item file to report items 1001, 1002, 2485, and 2486:

1001

1002

2485

2486

When reporting with an item file, items are not displayed if they are not included in the selected sales or non-sales category or categories.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3161 p-mix pmix

Chits do not Display Entire Tab Name

Chits do not Display Entire Tab Name

============================================================================

AKBID3162

Created: 25 October 2000

Updated: 25 October 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

Bar and kitchen chits only display the first four characters of the tab name if large fonts are enabled for bar and kitchen chits in the ALOHA^� application software.� Disabling the large fonts enables eight characters.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3162 4

Ordinal not Found in Dynamic Link Library

Ordinal not Found in Dynamic Link Library

============================================================================

AKBID3163

Created: 30 October 2000

Updated: 15 August 2001

Reviewed: 9 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

If an ALOHA^� software application displays an error stating an ordinal is not found in a dynamic link library, then the version of the .DLL file referenced in the error may not be compatible with the Aloha application software.

Replace the .DLL file with the same file from the Aloha Installation CD.� The .DLL files are stored in the W95DLL.ZIP and W95DLL2.ZIP file for Microsoft^� Windows^� 95, Windows 98, and Windows Millennium Edition (Me) users or stored in WNTDLL.ZIP and WNTDLL2.ZIP for Windows NT^�, Windows 2000, Windows XP, and Windows Server 2003 users.� Do not overwrite newer files.�

If you are using the Windows NT, Windows 2000, Windows XP, or Windows Server 2003 operating system, you might have to use SETUPSYS.EXE (refer to document AKBID1012) to replace the .DLL file.

============================================================================

See also:

AKBID1012 Aloha Application Software Utility Description and Usage

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3163

BackOffice Shortcut 'Start in' Settings

BackOffice Shortcut 'Start in' Settings

============================================================================

AKBID3164

Created: 31 October 2000

Updated: 31 October 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

Microsoft^� Windows^� shortcuts to ALOHA^� application software BackOffice products might display database access errors or read the incorrect database if the shortcut's 'Start in' location is not configured properly.�

You must configure the 'Start in' location to the root BackOffice folder, not the folder where the target resides in.� For example, a shortcut to D:\Aloha\BackOffice\GC\Gcoli08f.EXE has a 'Start in' location of D:\Aloha\BackOffice.

This does not apply to shortcuts for Aloha Labor Scheduler (ALS).

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3164

Javelin Viper Customer Display Settings

Javelin Viper Customer Display Settings

============================================================================

AKBID3165

Created: 31 October 2000

Updated: 9 November 2000

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.201 � 5.3.x

============================================================================

The ALOHA^� application software uses the following settings for the Javelin Viper customer (pole) display:

1.        Install the hardware according to Javelin�s instructions.

2.        In the BIOS Peripheral Setup, set the Customer Display Emulation to Ultimate, and set the Customer Display Baud Rate to 4800.

3.        In the Aloha application software, set the Pole Display Type to PD220XL, and the Port to COM 6.

4.        Refresh the system.�

You might have to manually configure COM 6 in Microsoft^� Windows^� using the same settings as those in the BIOS.�

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3165 line rear

Meal Accountability System On-screen Keyboard

Meal Accountability System On-screen Keyboard

============================================================================

AKBID3166

Created: 20 December 2000

Updated: 20 December 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

To enable an on-screen keyboard for use with Aloha Customer Information Management/Meal Accountability System (CIM/MAS) in the ALOHA^� application software Front-of-House (FOH), set the following variable to TRUE in the ALOHA.INI in NEWDATA and refresh the system:

DELIVERYTOUCHSCREEN=TRUE

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3166 onscreen touch touchscreen

IBER.EXE/IBERQS.EXE Demonstration Restrictions

IBER.EXE/IBERQS.EXE Demonstration Restrictions

============================================================================

AKBID3167

Created: 7 November 2000

Updated: 5 November 2003

Reviewed: 19 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The 'demonstration' versions of the ALOHA^� application software Front-of-House (FOH) applications (IBER.EXE and IBERQS.EXE) places the following limitations on users:

1.        Non-cash tenders limited to $10.00 with a $2.00 tip

2.        Guest checks display a disclaimer

3.        Kitchen and bar chits display a disclaimer

4.        Employee checkouts display a disclaimer

5.        Credit card vouchers (chits) display a disclaimer

6.        The maximum number of checks is 30

7.        The total sales allowed is $500.00

8.        You cannot Grind a TRANS.LOG (Transaction Log) with transactions generated by the demonstration version.

The demonstration versions of the FOH applications are stored in the DEMO folder on the Aloha Installation CD.

============================================================================

See also:

Aloha Installation Guide

AKBID1173 Demo Aloha Without a HASP Key

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3167 demo iberdemo

Progressive Systems CVM Pin-outs

Progressive Systems CVM Pin-outs

============================================================================

AKBID3168

Created: 2 November 2000

Updated: 3 November 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.0x � 5.3.x

============================================================================

The ALOHA^� application software uses the following pin-outs to communicate with the Progressive Systems CVM kitchen-video-system (KVS):

KVS DB25

12,13

24

25

-

-

Terminal DB9

3

5

2

4,6

7,8

KVS DB25

12,13

24

25

-

-

Terminal DB25

2

7

3

4,5

6,20

For more information, refer to document 'CVM � Aloha, Color Monitor System, System Information' available on the Progressive Systems Internet site (http://www.progressiveseattle.com).

============================================================================

See also:

Aloha Video User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3168 db-9 db-25 pinout pinouts

KEY.TXT HASP Security Key Identification File

KEY.TXT HASP Security Key Identification File

============================================================================

AKBID3169

Created: 9 November 2000

Updated: 9 November 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

If the ALOHA^� application software installation applications (SETUPPOS.EXE and ADVANCED.EXE) detect the file C:\KEY.TXT, they will use the information in C:\KEY.TXT to populate the HASP^� security key activation codes during the installation process.� This feature is useful for laboratory and demonstration systems where you reinstall the Aloha application software on a regular basis.

The KEY.TXT file format includes a [Ibertech] header followed by the HASP security key activation code broken into each section.� For example:

[Ibertech]

SEC1=C3EA38CAE26253F

SEC2=3CA3384A9EC5D3

SEC3=E14DC17B671E87

SEC4=9CAA1714D526950

SEC5=39CBED4C5C671

SEC6=DE5910F50

============================================================================

See also:

Aloha Installation Guide

AKBID1112 HASP Key Troubleshooting

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3169 automatic automatically enter

Report Layout or Display Anomalies

Report Layout or Display Anomalies

============================================================================

AKBID3170

Created: 13 November 2000

Updated: 13 November 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

If you are experiencing problems with ALOHA^� application software reports that include missing columns, missing sections, font sizes or anomalies that you cannot explain otherwise, try using different printer drivers, installing/reinstalling the latest service pack for the operating system (OS), or checking the system for software viruses.� It is possible that incorrect or inferior printer drivers, a corrupt file, or a virus is the root of the problem.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3170 huge large read readable size small tiny

'Cannot load string' Errors in FOH Debouts

'Cannot load string' Errors in FOH Debouts

============================================================================

AKBID3171

Created: 13 November 2000

Updated: 20 November 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

Errors stating 'Cannot load string n' (where n is a string number) that appear in the ALOHA^� application software debugging-output-files (debouts) do not represent errors detrimental to the Aloha application software.� The errors refer to resource strings used in the software and you can ignore them.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3171

Event-level Tax Reroutes

Event-level Tax Reroutes

============================================================================

AKBID3172

Created: 14 November 2000

Updated: 6 December 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

Event-based tax reroutes in the ALOHA^� application software only apply to primary taxes, and they can only be rerouted to matching tax types (for example, inclusive tax to inclusive tax or exclusive tax to exclusive tax).� Secondary taxes, vendor taxes, or taxes assigned by order modes are not supported by event-based tax reroutes.

===========================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1084 Smart Tax

AKBID3026 Inclusive Tax Formula

AKBID1114 Tax and Surcharge Calculations

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3172

RIP1ITEM=0 in ALOHA.INI

RIP1ITEM=0 in ALOHA.INI

============================================================================

AKBID3173

Created: 6 December 2000

Updated: 6 December 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.0x � 5.3.x

============================================================================

The following variables in ALOHA.INI refer to 'refill_rule' functionality that either no longer exists in the ALOHA^� application software or was never activated:

RIP1ITEM=0

RIP1ACT=FALSE

RIP1RIC1=0

RIP1RIC1MULT=0

RIP2ITEM=0

RIP2ACT=FALSE

RIP2RIC1=0

RIP2RIC1MULT=0

Although you can delete these variables from the ALOHA.INI, their existence is not harmful to the Aloha application software functionality or stability.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3173 rip ripact ripitem ripric

Disable Drink Chits for Bartenders

Disable Drink Chits for Bartenders

============================================================================

AKBID3174

Created: 11 December 2000

Updated: 11 December 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

Most restaurants do not require the ALOHA^� application software to print remote bar chits for bar-drinks ordered by the bartender, but do require remote bar chits for bar-drinks ordered by all other employees.

To enable this in the Aloha application software, perform the following:

1.        Route all bar-drinks to the remote bar chit printer group

2.        Create a 'Null' printer group without any printers in it

3.        Create a separate menu for bartenders

4.        Create a menu-level reroute to send the remote bar chit printer group to the null printer group on the bartender's menu

The Aloha application software will reroute the bartender's remote bar chits (and anybody else's using this menu) to a non-existent printer.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3174 disable

Copyright Aloha Technologies, Ltd. �2004

Aloha does not Detect Open Javelin OPOS Cash Drawer

Aloha does not Detect Open Javelin OPOS Cash Drawer

============================================================================

AKBID3175

Created: 7 December 2000

Updated: 12 November 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.222 � 5.3.x

============================================================================

If the ALOHA^� application software does not recognize an open OPOS cash drawer a Javelin Systems Inc.� terminal, you must obtain the newest OPOS software from Javelin Systems Inc. that includes an updated JAVELINSO.DLL file.

You might also need to adjust the cash drawer status polarity in the OPOS software configuration.� If the polarity is not set properly, the OPOS software (and the Aloha application software) lists the cash drawer as closed when it is open and vice versa.

============================================================================

See also:

AKBID1074 OPOS

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3175 lc lcp lp viper wedge

SuperSite Terminals Restart, but do not Refresh

SuperSite Terminals Restart, but do not Refresh

============================================================================

AKBID3176

Created: 11 December 2000

Updated: 11 December 2000

Reviewed: 9 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

If ALOHA^� application software SuperSite terminals restart, but do not refresh the data from the file server, check the master terminal's debout for signs of network communication errors between the master terminal and the file server.� Errors include the inability to update the file server's Master file or process the Refresh flag on the terminal while the Aloha application software is initializing.

The file server might be able to communicate with the master terminal and place a Stop file in the terminal's Tmp folder to initiate restarting the terminals, but the master terminal may not be able to communicate with the file server after restarting to update (refresh) the data files.� This can lead to the allusion of a refresh, but in reality, the terminals are only restating and not refreshing their data at all.

============================================================================

See also:

AKBID1051 Aloha Application Software Flag and Marker Files

AKBID1150 Using LMHOSTS with a SuperSite

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3176 FOH front house update

Seat Numbers are not Printing on Chit

Seat Numbers are not Printing on Chit

============================================================================

AKBID3177

Created: 29 December 2000

Updated: 13 August 2002

Reviewed: 26 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The ALOHA^� application software versions 5.0x and lower print seat numbers on kitchen and bar chits if Pivot Seating is enabled and item consolidation is not enabled in the chit printing options.� If item consolidation in enabled, the seat numbers do not print on chits.

In versions 5.2x and higher, enable 'Always sort by seat number' in the printer configuration options to print seat numbers with consolidation enabled.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3177 seats

Quick Combo Select Item Panel Size and Color

Quick Combo Select Item Panel Size and Color

============================================================================

AKBID3178

Created: 3 January 2001

Updated: 3 January 2001

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService

Aloha POS Versions: 3.8x � 5.3.x

============================================================================

The 'Select Item' window displayed by ALOHA^� application software QuickService Quick Combos is not user-configurable.

The number of buttons and their sizes determines the panel size.� The button sizes match the size of the button that was used to launch the Quick Combo function.� The colors are based on the default colors configured in Microsoft^� Windows^�.

============================================================================

See also:

Aloha QuickService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected]

Additional query words: 3178 quickcombo selection

Tax Rounding Direction

Tax Rounding Direction

============================================================================

AKBID3179

Created: 4 January 2000

Updated: 4 January 2000

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The ALOHA^� application software rounds taxes to the nearest penny.

A dollar taxed with 1.3% returns a $.01 tax amount, 1.5% returns $.02, and 1.8% returns $.02.

============================================================================

See also:

Aloha QuickService or TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3179 round

Membership Interface Causes Grind PutIntField Overflow Errors

Membership Interface Causes Grind PutIntField Overflow Errors

============================================================================

AKBID3180

Created: 5 January 2001

Updated: 17 September 2003

Reviewed: 11 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

Since the export files created by the ALOHA^� application software Membership Interface only use 5-digit item ID numbers and 6-digit check numbers, you can not create new items with item numbers higher than 99,999 or use terminal ID numbers higher than 99.�

Databases with item ID numbers higher than 99,999 can cause 'PutIntField: overflow <item ID number> is longer than 5' errors when the Grind process creates the export file.�

Databases with terminal ID numbers higher than 99 can cause 'PutIntField: overflow <check ID number> is longer than 6' errors when the Grind process creates the export file.

If you are not using the Membership Interface, disable it in the ALOHA.INI by assigning a value of FALSE to the CLUBCORP variable (CLUBCORP=FALSE).� If you are using the Membership Interface, but you do not need to create an export file, assign a value of TRUE to the NOGRINDCLUBCORPEXPORT variable (NOGRINDCLUBCORPEXPORT=TRUE) in the ALOHA.INI.

============================================================================

See also:

Aloha Membership Interface User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected]

Additional query words: 3180 club clubcorp corp fatal error members

style='mso-spacerun:yes'>� 2003

Aloha Manager Only Displays a White Background

Aloha Manager Only Displays a White Background

============================================================================

AKBID3181

Created: 8 January 2001

Updated: 8 January 2001

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

If there is not a HASP^� key attached to the ALOHA^� application software file server when Aloha Manager starts, Aloha Manager might display a white background and not continue to initialize.� Verify if there is an error listed on the Microsoft^� Windows^� task bar.� The error might be hidden behind Aloha Manager.� To access the error dialogue box, perform the following:

1.        Click 'Aloha Manager' on the taskbar

2.        Click the error on the taskbar

3.        Acknowledge the error

Aloha Manager will continue to initialize once the error is acknowledged.

============================================================================

See also:

AKBID1173 Demo Aloha without a Security Key

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3181 alohamgr.exe

Enable 'Set Customer Balance to Zero' Option in A/R

Enable 'Set Customer Balance to Zero' Option in A/R

============================================================================

AKBID3182

Created: 9 January 2001

Updated: 9 January 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

To enable the 'Set customer balances to zero upon report completion' option for the ALOHA^� application software BackOffice Accounts Receivable (A/R) Customer Balance Report, edit AR.INI in the BackOffice \DS folder, and add the following information:

1.        If the [ARCBR] section does not exist in the AR.INI, create it (include the brackets).

2.        Add the following lines to the [ARCBR] section:

CurrentBalanceZeroMethod=0

AllowCurrentBalanceZero=1

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3182 ar

style='mso-spacerun:yes'>� 2003

QS Video Displays 'Order is not finalized' Error

QS Video Displays 'Order is not finalized' Error

============================================================================

AKBID3183

Created: 10 January 2001

Updated: 10 January 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

If you are using the ALOHA^� application software VIDEO.EXE in a QuickService environment, you must have a FASTFOOD flag in the Aloha application software folder on each Front-of-House (FOH) terminal.� If the file does not exist, VIDEO.EXE displays an error stating 'Order is not finalized' when you try to bump items from the video screen.

To create the FASTFOOD flag in a FOH terminal, open a command prompt and type the following command:

ECHO 1 > %LOCALDIR%\FASTFOOD

============================================================================

See also:

Aloha QuickService User Manual

Aloha Video User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3183 qs video.exe

Running ALS in Demo Mode with a HASP Key

Running ALS in Demo Mode with a HASP Key

============================================================================

AKBID3184

Created: 15 February 2001

Updated: 15 February 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 5.021 � 5.3.x

============================================================================

In version 5.021 and higher, ALOHA^� Labor Scheduler (ALS) users can enable demo-mode with the HASP^� security key attached by adding /DEMO to the ESP.EXE command line (for example, ESP.EXE /DEMO).

============================================================================

See also:

Aloha Labor Scheduler User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3184 data database demonstrate

Lookup_stat ID Errors

Lookup_stat ID Errors

============================================================================

AKBID3185

Created: 27 February 2001

Updated: 27 February 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The ALOHA^� application software displays lookup_stat errors on the screen or in the Debugging-Output-Files (debouts) for the following reasons:

1.        A database entry (for example, sales item, basic gift certificate, payment, and so on) listed in the TRANS.LOG (transaction log) has been deleted from the database.

2.        A sales item or basic gift certificate in the database is assigned to a sales or non-sales category that no longer exists.

3.        A database entry is linked to another database ID (for example, an item's printer group, a terminal's revenue center, and so on) that no longer exists.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3185 error lookup number stat

Cool Interface by Terminal

Cool Interface by Terminal

============================================================================

AKBID3186

Created: 7 March 2001

Updated: 19 September 2002

Reviewed: 12 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 5.010 � 5.3.x

============================================================================

For more information on the Enhanced Graphical Interface (EGI) available in versions 5.2.5.x and higher, refer to document AKBID1216.

The MMSCHEME system environment variable enables you to override the default ALOHA^� application software Front-of-House cool interface on a terminal-by-terminal basis.� For example, if a restaurant wants the cool interface on the bar terminals, but they do not want one on the dining room terminals (or they want different cool interfaces between the two areas), they can use the MMSCHEME variable to overwrite the default interface in the terminal.

To enable the MMSCHEME environment variable, add MMSCHEME to the system environment variables and assign it to the name of the cool interface scheme (non-case-sensitive).� For example:

SET MMSCHEME=WAVE

SET MMSCHEME=MARBLE

SET MMSCHEME=FABRIC

SET MMSCHEME=BLUESTONE800

SET MMSCHEME=CLASSIC

Assign MMSCHEME to 'CLASSIC' to disable the cool interface on the terminal.� Leave MMSCHEME unassigned to use the default scheme set in Aloha Manager/Maintenance/Store Settings/User Interface.

Cool interfaces schemes will not function properly unless the cool interface scheme is selected when installing the Aloha application software on the file server.

============================================================================

See also:

Aloha TableService User Manual

AKBID1216 Enabling and Configuring FOH Enhanced Graphical Interface

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3186 blue resolution stone

style='mso-spacerun:yes'>� 2003

Selecting an Open TCP Port for AlohaSpy and Fiscal Manager

Selecting an Open TCP Port for AlohaSpy and Fiscal Manager

============================================================================

AKBID3187

Created: 19 March 2001

Updated: 8 July 2002

Reviewed: 6 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The ALOHA^� application software requires you to assign TCP socket ports in order the Transaction Verification Systems, Inc. (TVS) hardware (used with AlohaSpy) and Fiscal Manager (used with fiscal printing) to communicate.� You can download NETINFO.EXE from the Aloha Technologies FPT site to assist with finding an open TCP port on each computer.�

You can determine if a port is open by entering a known port number and checking its status, or by viewing a list ports currently in use.

To check the status of a known port number, open NETINFO.EXE, enter the port number in the Port Number textbox (for example, 3999), and click Query Port.� If the result is 'No Service On This Port', then the port is open for use.� If the port is already in use, you must select a different port.

To view a list of ports currently in use, open NETINFO.EXE and click 'Get Service By Ports (All)'.� After a short wait, NETINFO.EXE displays a list of all port numbers currently in use.� Select an unlisted port number for use with AlohaSpy or Fiscal Manager.�

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1208 Configuring Fiscal Manager and Fiscal Printers in Aloha

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3187 spy udp

Logging Screen Touches for Debugging

Logging Screen Touches for Debugging

============================================================================

AKBID3188

Created: 20 March 2001

Updated: 26 August 2002

Reviewed: 17 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.023 � 5.3.x

============================================================================

ALOHA^� application software versions 5.023 and higher enable you to track Front-of-House (FOH) user activity (touches) in the Debugging-Output-Files (debouts).� You can use this data to enhance your abilities to reproduce problems.

Enabling this feature can result in very large debouts that might reduce system speed.� You should only use this feature when required and disable it immediately after your testing is completed.�

To enable the extra debugging in TableService (versions 5.023 and higher) or QuickService (versions 5.234 and higher), set DEBUGTOUCH to TRUE in the FOH terminal's system environment variables (for example, SET DEBUGTOUCH=TRUE).� This instructs the FOH to record to the debout each button pressed using the format 'WM_COMMAND: <screen>, <button id> "<button text>"; <touch coordinates>'.

To enable the additional debugging in QuickService versions 5.023 through 5.233, create a file in the FOH terminal's root of drive (C:\) labeled QSTRACE.TXT (for example, C:\QSTRACE.TXT).� The file's contents do not matter.� This instructs the FOH to record each button pressed to the debout using the format 'Button Pressed: Text <button text> Func <button function> Params <function parameters>'.� Only panel buttons are recorded.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3188 debug keystrokes

ODBC Version Error

ODBC Version Error

============================================================================

AKBID3189

Created: 29 March 2001

Updated: 29 March 2001

Reviewed: 9 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

If the ODBC Driver Manager displays a resource DLL error when you try to start CTLSVR.EXE (Control Server), reinstall the ODBC drivers located in the ODBC_30 folder on the ALOHA^� application software installation CD.� If the problem persists, reinstall the Microsoft Data Access drivers from the \MISC\MSDA folder on the Aloha installation CD.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3189 different odbc32.dll

style='mso-spacerun:yes'>� 2003

House Account Report Font

House Account Report Font

============================================================================

AKBID3190

Created: 30 March 2001

Updated: 2 April 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

The ALOHA^� application software uses Microsoft Notepad to display and print the House Account report.� In some cases, the default notepad font size may cause the report to appear distorted.� Perform the following to adjust the font size in the Windows registry in order to fix this problem:

The incorrect use of the Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT, and click OK.�

2.        Path out HKEY_CURRENT_USER\Software\Microsoft\Notepad.

3.        To adjust the font size, double-click the iPointSize key, select Decimal, change the value to the new font size, and click OK.� For example, set the font size to 120 for a 12-point font or 160 for a 16-point font.

4.        Select Registry/Exit to exit the Windows Registry Editor.�

5.        Restart Windows.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3190 carries carry line over reports second wrap wraps

NCR OPOS Memory Leak Causing Terminal Lockups

NCR OPOS Memory Leak Causing Terminal Lockups

============================================================================

AKBID3191

Created: 4 April 2001

Updated: 4 April 2001

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.011 � 5.3.x

============================================================================

Memory leaks can occur with the ALOHA^� application software Front-of-House (FOH) in systems using NCR OPOS drivers and NCR Fit Client, such as the NCR 7454 POS terminals.� The memory leaks can lead to system lock-ups or various Microsoft^� Windows^� errors.�

To fix the memory leak, edit the ALOHA.INI in the NEWDATA folder, add the line OLEINITIALIZE=TRUE (if it does not already exist), and refresh the system.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3191 general protection fault gp gpf

4.4x EDC Security Server Error

4.4x EDC Security Server Error

============================================================================

AKBID3192

Created: 11 April 2001

Updated: 11 April 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 4.4x

============================================================================

If a VER.DBF file exists in the ALOHA^� application software DATA folder, EDC version 4.4x displays an error stating 'Could not connect to the Aloha Security Server'.� Remove the VER.DBF file from the NEWDATA and DATA folders to enable EDC to function properly.

The VER.DBF file is a database file used by version 5.0x and higher to determine the database version number.� This file is also used by EDC to determine whether or not to enable the user login feature available in version 5.0x and higher, which requires the security server.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3192 unable

Printing One Item on Two Chits Using a Single Printer

Printing One Item on Two Chits Using a Single Printer

============================================================================

AKBID3193

Created: 25 April 2001

Updated: 18 June 2001

Reviewed: 17 December 2003

Microsoft^� Windows^� Versions: All

ALOHA^� Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

============================================================================

To print a single item on two separate chits using a single printer, use the 'Reroute Printer' event.� The 'Reroute Printer' event creates separate chits, while the 'Reroute Printer Group' does not.

For example, if the customer requires a chit with both a hamburger and a hot dog on one chit, but also requires a second chit from the same printer with just the hamburger, perform the following:

1.        Configure the physical kitchen printer and add it to the 'Kitchen' printer group.�

2.        Assign the hot dog to the 'Kitchen' printer group.

3.        Create a 'Mock Hamburger' printer.� Since the printer is not real, do not assign it to a terminal.

4.        Create a 'Mock Hamburger' printer group and add the 'Mock Hamburger' printer to it.

5.        Add the physical kitchen printer to the 'Mock Hamburger' printer group.

6.        Assign the hamburger to the 'Mock Hamburger' printer group.

7.        Create a 'Reroute Printer' event to reroute the 'Mock Hamburger' printer to the physical kitchen printer.

The printer now produces separate chits for the 'Kitchen' items (the hot dog and the hamburger) and the 'Mock Hamburger' items (the hamburger).

This setup will print the hamburger on two separate chits even if nothing else is ordered.� If that is the scope of your requirements, you can eliminate step number two.

In versions 5.007 through 5.026, you may have to disable stand-alone chit printing (part of the Aloha application software fault tolerance capabilities) in order for the functionality described in this document to function properly.� To disable stand-alone chit printing, edit the ALOHA.INI in the Aloha application software NEWDATA folder, set the DISABLESTANDALONECHITPRINT variable to TRUE (for example, DISABLESTANDALONECHITPRINT=TRUE), and refresh the system.

============================================================================

See also:

Aloha QuickService and TableService User Manual

AKBID1121 Reroute All Chits to Local Printers

AKBID3106 Separating Chits on a Single Printer

AKBID3316 Printing Multiple Copies of Chits on a Terminal's Local Printer

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3193 bar cut different multiple remote

style='mso-spacerun:yes'>� 2003

Configuring Customer Cards for Use with Frequent Buyer

Configuring Customer Cards for Use with Frequent Buyer

============================================================================

AKBID3194

Created: 27 April 2001

Updated: 5 September 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The information in this document has been replaced by information in document AKBID1198.

============================================================================

See also:

AKBID1198 Magnetic Stripe Card Information

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3194

Resetting Non-resetting Totals to Zero

Resetting Non-resetting Totals to Zero

============================================================================

AKBID3195

Created: 30 April 2001

Updated: 1 August 2001

Reviewed: 17 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.051 � 5.3.x

============================================================================

The ALOHA^� application software stores non-resetting totals information in the NRTOTALS (NONRESET in versions 4.0x and lower) file.� Delete the NRTOTALS file in the Aloha application software DATA folder to reset the non-resetting totals.

Copies of the NRTOTALS files that reside in dated folders are not used by reports, so you can keep them as copies of the original NRTOTALS file or you can delete them.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3195 clear clearing erase erasing non-reset nonresetting out zeroing

Event-level Menu Assignment Hierarchy

Event-level Menu Assignment Hierarchy

============================================================================

AKBID3196

Created: 16 May 2001

Updated: 16 May 2001

Reviewed: 16 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

If you are using events to set menus in the ALOHA^� application software, the Set Menu Group and Set Menu by Term/Jobcode event types override each other and the Set Server Menu event type.�

If you set a menu using the Set Menu Group or Set Menu by Term/Jobcode event types, you cannot set a new (overriding) menu using the Set Server Menu event type.�

This information also applies to the Set Bar Menu and Set Cashier Menu event types.� Refer to document AKBID1053 for more information on what determines a server job codes versus a bartender or cashier job code.

============================================================================

See also:

Aloha TableService User Manual

AKBID1053 TableService Order Entry Job Code Options

AKBID3300 Aloha FOH Reads Multiple Event Configuration Files

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3196

Enabling Retroactive Non-resetting Totals

Enabling Retroactive Non-resetting Totals

============================================================================

AKBID3197

Created: 18 May 2001

Updated: 18 May 2001

Reviewed: 24 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

Perform the following to enable the ALOHA^� application software non-resetting totals feature at a restaurant with existing dated folders that previously did not use non-resetting totals:

1.        Open Aloha Manager, select Maintenance/Store Settings/Security/Use Non-reset Totals, and refresh the system.

2.        Edit the ALOHA.INI file in each dated folder and set the NONRESETS variable to TRUE (NONRESETS=TRUE)

3.        Grind each dated folder in order from oldest to the most recent in order to create and/or update the \DATA\NRTOTALS file.� Refer to document AKBID1016 for more information on manually regrinding dated folders.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID1016 Grind Process and Errors

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3197 add adding non nonreset old previous report reset

EDC Processors Currently Supported by Aloha

EDC Processors Currently Supported by Aloha

============================================================================

AKBID3198

Created: 18 May 2001

Updated: 14 April 2004

Reviewed: 14 April 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

The ALOHA^� application software Electronic-Data-Capture (EDC) application currently supports the following processors:

Processor

Initial Aloha Support Version

Supported Card Types

Dial-up Support

TCP/IP Frame Support

TCP/IP Internet Secure or Encrypted Support (SSL)

Notes

$$$ in the Bank ($$$ on the Net, Shift4)

4.4

Credit Cards

No

Yes

No

AlohaNet

5.2

Credit Cards

No

Yes

No

Part of the Universal Payment Interface.

Amex (American Express)

3.5

Credit Cards

Yes

No

No

Buypass

4.4

Credit Cards

Yes

No

Yes

TCP/IP SSL communication supported in Aloha versions 5.3.6 and higher.

CES (FDMS North, Cardnet, First Data North)

3.5

Credit Cards, Gift Cards (ValueLink)

Yes

Yes

Yes (credit cards only)

TCP/IP communication supported in Aloha versions 5.2.5.x and higher.

ValueLink gift cards supported in Aloha versions 5.2.5.x and higher.

DirectNet (POSware)

4.4

Credit Cards

No

Yes

No

FDC (FDR, Envoy, FDR Omaha, First Data National, First Data Nashville)

3.8

Credit Cards

Yes

No

No

Fifth Third Processing Solutions (Fifth Third Bank, 53)

5.3

Credit Cards

Yes

Yes

Yes

LynkSystems (Lynk Systems)

4.2

Credit Cards

Yes

Yes

Yes

Use VisaNet in Aloha versions 5.0x and lower.

Use LynkSystems in Aloha versions 5.2x and higher.

TCP/IP communication supported in Aloha versions 5.2.5.x and higher.

Maverick (CardSystems)

4.2

Credit Cards

Yes

No

No

Nabanco (FDMS South (First Data South)

3.65

Credit Cards, Gift Cards (ValueLink)

Yes

Yes

Yes (credit cards only)

TCP/IP communication supported in Aloha versions 5.2.5.x and higher.

ValueLink gift cards supported in Aloha versions 5.2.5.x and higher.

NDC (Global Payments)

3.6

Credit Cards, Debit Cards, Check Authorization

Yes

No

No

Debit card authorization is supported in QuickService versions 5.2x and higher using the PIN pads listed later in this document.

Check authorization is only support in the Back-of-House (BOH).

NOVA

3.8

Credit Cards

Yes

No

No

NPC

3.5

Credit Cards

Yes

No

No

Settlement only.

Paytech (Paymentech)

4.4

Credit Cards, Gift Cards

Yes

Yes

Yes

TCP/IP Frame communication supported in Aloha versions 5.2.4.x and higher.

TCP/IP SSL credit card authorization supported in Aloha versions 5.3 and higher.

Gift cards supported in Aloha versions 5.2.5.x and higher.

Stored Value Systems

5.3

Gift Cards

No

Yes

No

VisaNet (Vital^�, Vitalnet)

3.5

Credit Cards, Debit Cards

Yes

Yes

Yes (credit cards only)

TCP/IP SSL communication supported in Aloha versions 5.2 and higher.

TCP/IP Frame communication supported in Aloha versions 5.2.7.90 and higher.�

Debit card authorization is supported in QuickService versions 5.2.7.90 and higher using the PIN pads listed later in this document.

The Aloha application software supports the following debit card PIN pads:

You must submit PIN pads to your debit card processor for encryption prior to implementing them.

PIN Pad

Initial Aloha Support Version

Notes

VeriFone PINpad 1000

5.2

VeriFone Everest

5.2.7.31

VeriFone EverestPlus

5.2.7.31

Configure as a VeriFone Everest in the Aloha application software.

============================================================================

See also:

Aloha Credit Card User Manual

AKBID3280 Port Used by EDCSVR.EXE for SSL Credit Card Authorization

AKBID3312 Configuring VeriFone PIN Pads for Use with Aloha

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3198 auth authorize dollars dsl ip process processing secure socket layer settle tcp

Credit Card Lengths and Prefixes

Credit Card Lengths and Prefixes

============================================================================

AKBID3199

Created: 21 May 2001

Updated: 3 December 2001

Reviewed: 4 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

The ALOHA^� application software automatically identifies credit card types using the following criteria, based on length and prefix:

Card Type

Length

Prefixes

Master Card

16

51, 52, 53, 54, 55

Visa

13 or 16

4

American Express

15

34, 37

Diners Club and Carte Blanche

14

30, 36, 38

Discover/Novus

16

6011

EnRoute

15

2014,2149

JCB

16

30, 31, 33, 35

There is also a special checksum (called the Luhn Mod 10 check) that the Aloha application software uses to identify invalid card numbers.� This prevents entering a random number starting with the correct prefix and with the correct length.

============================================================================

See also:

Aloha Credit Card User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3199 size

Increasing Credit Card Authorization Speed

Increasing Credit Card Authorization Speed

============================================================================

AKBID3200

Created: 21 May 2001

Updated: 13 May 2003

Reviewed: 27 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

Perform the following to increase the ALOHA^� application software EDC authorization speed for credit card authorization via a modem:

1.        If you are using an 800 number authorization, try using 950 numbers instead.� It takes a long time to dial and connect to an 800 number.� 950 numbers are special local numbers that connect extremely fast, usually on the first ring.� This can save several seconds per authorization.

2.        Use the Multi-trans feature in EDC.� If two EDC authorization requests appear at the same time, Multi-trans can authorize them during the same phone call.� This saves time for the second authorization, because if EDC is already connected, an authorization only takes about 3 seconds.� Some processors require user-authorization to use Multi-trans.�

3.        Ensure the initialization string configures the modem to dial touch-tones as fast as possible.� The default speed for touch-tones may be slow.� You can save one to two seconds by setting the touch-tone speed as fast as possible, typically 50 milliseconds.� To set speed to 50 milliseconds, add 'S11=50' to the initialization string.

4.        Very slow authorization times may be a symptom that the system is getting errors and re-dialing.� Check the Debout.edc for these errors.

5.        Using initialization strings such as AT&F0 do not send enough connection information to the modem, so the modem spends more time negotiating a connection with the host.� Using a proper initialization string (refer to document AKBID1189) will decrease the authorization time by decreasing the time it takes to establish a connection.

Authorization times below 20 seconds are about the fasted received.� Times below 15 seconds are unusual.� EDC should be able to authorize as fast as any other dial-up mechanism, at least within 2 seconds or so.

============================================================================

See also:

Aloha Credit Card User Manual

AKBID1020 EDC Process

AKBID1189 EDC Modem Initialization Strings

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3200 auth decrease faster lower slow time

Temporarily Moving EDC TXN Files

Temporarily Moving EDC TXN Files

============================================================================

AKBID3201

Created: 21 May 2001

Updated: 21 May 2001

Reviewed: 24 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

Some problems may require you to move the ALOHA^� application software EDC TXN files to a temporary location so the restaurant can start on a new batch.� Perform the following to move the TXN files to a temporary location:

Do not perform this with host-based processors (for example, Nova).

1.        Shut down EDC.EXE (EDC) and EDCSVR.EXE (EDC Server).

2.        Create a temporary folder inside the EDC folder.

3.        Move the TXN files from the processor folder to the temporary folder.

4.        Restart EDC Server and EDC

Credit Card processors vary in the expiration time applied to an authorization.� You should restore and settle the TXN files as soon as possible by performing the following:

1.        Settle any existing TXN files.�

2.        Shut down EDC and EDC Server.

3.        Move the TXN files from the temporary folder to the processor folder. Do not overwrite existing TXN files.

4.        Restart EDC Server and EDC.

============================================================================

See also:

Aloha Credit Card User Manual

AKBID1020 EDC Process

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3201

EDC Configuration not Saving Properly

EDC Configuration not Saving Properly

============================================================================

AKBID3202

Created: 21 May 2001

Updated: 21 May 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

If changes to the ALOHA^� application software EDC configuration do not save properly and are no longer present after exiting the configuration dialogue, create a new EDC.INI file.� In most cases, you can create a new EDC.INI by copying the contents of the current EDC.INI to a new text file and saving it as EDC.INI.

In some cases, you may have to build a new EDC.INI from scratch.� Perform this by renaming EDC.INI to EDC.OLD and opening EDC.EXE.� This creates a new blank EDC.INI.� Manually re-enter the configuration data into EDC.EXE.

Since the EDC transactions are stored in TXN and .STL files and not in EDC.INI, the existing credit card transactions settlements are not effected by either of the above methods.

============================================================================

See also:

Aloha Credit Card User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3202 retain

Duplicate Credit Card Transactions

Duplicate Credit Card Transactions

============================================================================

AKBID3203

Created: 21 May 2001

Updated: 21 May 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

The ALOHA^� application software Front-of-House (FOH) performs authorizations by creating a .req file and waiting for an .ans file.� The master terminal handles this.� If the Master terminal goes down while waiting for an .ans file, then a duplicate transaction, or a failed transaction, becomes possible.� The new master does not know whether the first .req transaction completed, so it creates a new .req file.� This second request file might result in a duplicate transaction in the batch or a rejected transaction because the processor recognizes it as a duplicate.

This is an extremely rare occurrence.� This should not result in a problem if you print or view a batch report before settling a batch, because the batch report very explicitly warns the merchant if there are duplicate transactions in the batch for the same credit card number.

============================================================================

See also:

Aloha Credit Card User Manual

AKBID1020 EDC Process

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3203 multiple

US Robotics 56K Modem Hang-up Issue

US Robotics 56K Modem Hang-up Issue

============================================================================

AKBID3204

Created: 21 May 2001

Updated: 21 May 2001

Reviewed: 28 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 4.0x � 5.3.x

============================================================================

Some versions of the U.S. Robotics 56K modem might not hang up properly after an ALOHA^� application software EDC authorization.� This is an U.S. Robotics issue, and you can fix it by using Symantec^� pcANYWHERE^�or other modem software to establish a high-speed connection and hang up.� This will properly reset the modem, and it should work until the modem loses power or is turned off again.� Other possible adjustments include the following (in the order they should be tried):

1.        Enable error correction in the initialization string (&M4).� There are two 'M' assignments in the modem initialization strings.� When enabling error correction, use the assignment with the leading ampersand (&), otherwise you may instead adjust the speaker volume.

2.        Send an extra carriage return when trying to disconnect the modem by adding SENDCRONHANGUP=1 to the [processor] section of the EDC.INI.� This may require up to four extra seconds to disconnect the modem.

3.        Send an extra End Of Transmission (EOT) when trying to disconnect by adding SENDEXTRAEOT=1 to the [processor] section of the EDC.INI.� This may require up to four extra seconds to disconnect the modem.� If you are using the CES processor, use SENDEXTRAEOT in favor of SENDCRONHANGUP.

4.        Increase the time EDC waits for the modem to hang up by adding PAUSETIMEDURINGHANGUP=5 to the [processor] section of the EDC.INI.� This may require several extra seconds to disconnect the modem.� Any value larger than 10 will automatically reset back to 10.

All of these settings are processor specific, so you can enable or disable them on a per-processor basis.

============================================================================

See also:

Aloha Credit Card User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3204 USR

FOH Hangs on Starting EDC

FOH Hangs on Starting EDC

============================================================================

AKBID3205

Created: 21 May 2001

Updated: 21 May 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

Refreshing the ALOHA^� application software Front-of-House (FOH) while processing an EDC transaction might cause the FOH to hang on 'Starting EDC' when restarting.� To fix this, delete any request (.req), hold (.hld), or answer (.ans) files from the EDC folder on the master terminal or file server and restart the FOH computer.� You might lose some EDC transaction and have to reprocess them.

If you delete any .ans files, ensure you are not double-charging the credit card if you apply the credit card to a check a second time.

============================================================================

See also:

AKBID1020 EDC Process

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3205 hangs stop stops

Balancing Reports Using /BALANCE

Balancing Reports Using /BALANCE

============================================================================

AKBID3206

Created: 30 May 2001

Updated: 30 May 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x.x

============================================================================

The ALOHA^� application software GRIND.EXE and GRINDQ.EXE applications support the /BALANCE command line variable to output detailed financial information to a text file in the target data folder labeled BALANCE.TXT.� The information in BALANCE.TXT is intended to assist with troubleshooting report balancing questions and issues.� For example, the following command line creates a BALANCE.TXT file in the dated folder labeled 20010530:

GRIND.EXE /DATE 20010530 /BALANCE

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3206 gross labor net reports sales

No 'Labor Scheduler' Drop-down Menu in Aloha Manager

No 'Labor Scheduler' Drop-down Menu in Aloha Manager

============================================================================

AKBID3207

Created: 4 June 2001

Updated: 5 June 2001

Reviewed: 28 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The ALOHA^� application software uses a Labor Scheduler drop-down menu in Aloha Manager to enable you to access the Aloha Labor Scheduler (ALS) application.� If the Labor Scheduler drop-down menu is not available in Aloha Manager, perform the following:

-          Ensure the correct HASP^� security key activation codes are entered in the system.

-          Ensure ALS is enabled on the HASP key.

-          Register ALOHALAB.DLL by opening a command prompt, navigating to the Aloha application software BIN folder, typing the following, and restarting the computer:

Edit the path to REGSVR32.EXE as needed.

C:\WINDOWS\SYSTEM\REGSVR32.EXE ALOHALAB.DLL

============================================================================

See also:

Aloha Labor Scheduler User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3207 alohamgr.exe schedule

EDC Reports Less Than Total Settlement

EDC Reports Less Than Total Settlement

============================================================================

AKBID3208

Created: 4 June 2001

Updated: 2 September 2003

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

Corruption in the ALOHA^� application software Electronic Draft Capture (EDC) settlement (.STL) file can cause the settlement report to display a settlement total that is less than the actual settlement.� For example, the actual settlement was $600.00, but the settlement report only shows $200.00.� Unintelligible characters (for example, 'G��p_') in any of the file's fields are evidence of corruption.

The easiest way to narrow down the corrupted areas is to edit a copy the original settlement file, truncate a small portion from the end of the settlement file, view a settlement report for the file and see if the total is the same as the original.� If it is, truncate more and continue to do so until the total changes.� This gives you the general area of the corruption from which you can scan and fix the corruption.� The easiest way to fix the corruption is to just remove it.

============================================================================

See also:

Aloha Credit Card User Manual

AKBID1020 EDC Process

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected]..

Additional query words: 3208 balance card credit different incorrect totals wrong

USEHUGECURRENCY in ALOHA.INI

USEHUGECURRENCY in ALOHA.INI

============================================================================

AKBID3209

Created: 13 July 2001

Updated: 13 July 2001

Reviewed: No Longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The USEHUGECURRENCY variable in the ALOHA.INI enables wide currency columns in the ALOHA^� application software for countries with item prices that require a large number of digits, such as 1,000,000.� You should only enable this variable (set the value to TRUE) in the rare cases where it is actually required.��

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3209 turkey turkish

BackOffice 'Invalid Activation Key' Message

BackOffice 'Invalid Activation Key' Message

============================================================================

AKBID3210

Created: 20 July 2001

Updated: 18 January 2002

Reviewed: 27 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

If the ALOHA^� application software BackOffice products display an error stating 'Invalid Activation Key', verify that you have properly configured the security key information in the BackOffice License Manager exactly as it appears on your security key information sheet.� This includes all user license, version number, corporate store, and option fields, even if you have not installed the software.

If you continue to have problems, verify if the \BACKOFFICE\LICENSE\FASTECH.LIC file is corrupt.� Consider deleting it and rebuilding a new one by reconfiguring your license information in the BackOffice License Manager.

============================================================================

See also:

AKBID1112 HASP Key Troubleshooting

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3210 ar gc delivery/fb inventory advanced reservations

Enable FOH Keyboard Input

Enable FOH Keyboard Input

============================================================================

AKBID3211

Created: 20 July 2001

Updated: 23 August 2001

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 5.2x � 5.3.x

============================================================================

You can enable the ALOHA^� application software Front-of-House (FOH) to accept keyboard input using a standard keyboard by selecting Aloha Manager/Maintenance/Store Settings/User Interface/POS and selecting 'Accept Keyboard Input', or edit the ALOHA.INI in the NEWDATA folder and set the ALLOWKEYBOARDINPUT to a value of TRUE.� If this is enabled, the FOH accepts keyboard input from any screen that accepts touch screen input.

You cannot use this feature in conjunction with Magnetic-Stripe-Readers (MSRs) that insert checksum characters at the beginning and end of the read magnetic stripe information unless you configure the MSR to disable the checksum characters.� The checksum characters are indistinguishable from keyboard input, so they can result in erroneous behavior.

============================================================================

See also:

Aloha TableService User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3211 card mag magcard

Thumbprint Scanner and HASP Key Conflicts

Thumbprint Scanner and HASP Key Conflicts

============================================================================

AKBID3212

Created: 20 August 2001

Updated: 12 September 2003

Reviewed: 8 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x - 5.3.x

============================================================================

If you are have attached a HASP^� security key to your parallel (LPT) port on your ALOHA^� application software file server that also functions as a Front-of-House (FOH) terminal, and you are also connecting an LPT-based Veridicom thumbprint scanner to the file server, then you must configure the system with one of the following configurations in order to avoid conflicts between the thumbprint scanner and the HASP security key:

-          Configure two parallel ports, one port for the HASP security key and one port for the thumbprint scanner.� The Aloha application software will automatically sense which LPT port the HASP security key is attached, although you can use the information in document AKBID1220 to assign the Aloha application software to only check a specific LPT port.

-          Configure a single LPT port for the HASP security key, and configure a Universal-Serial-Bus (USB) port for the thumbprint scanner.� The Aloha application software will automatically sense that a USB thumbprint scanner is attached.� Verify that your operating system supports USB ports.

-          Configure a single LPT port for the thumbprint scanner, and configure a USB port for the HASP security key.� The Aloha application software will automatically sense that an LPT thumbprint scanner is attached, and it will automatically sense that a USB security key is attached.� Verify that your operating system supports USB ports.

You can configure thumbprint scanners on either a LPT port or a USB port on dedicated FOH terminals to which a security key is not attached.

============================================================================

See also:

AKBID1112 HASP Key Troubleshooting

AKBID1215 Configuring Veridicom Thumbprint Scanners

AKBID1220 Assigning the HASP LPT Port in the Aloha Application Software

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3212 boh/foh bohfoh finger fingerprint foh/boh fohboh print terminal/server thumb

style='mso-spacerun:yes'>� 2003

Customer Lookup Screen Only Displays for an Instant

Customer Lookup Screen Only Displays for an Instant

============================================================================

AKBID3213

Created: 20 August 2001

Updated: 20 August 2001

Reviewed: 27 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 3.65x � 5.3.x

============================================================================

Using incorrect Front-of-House (FOH) timeout settings can cause the ALOHA^� application software customer lookup screen to briefly appear and exit before you can enter the customer information.

To adjust the timeout in TableService, open Aloha Manager, select Maintenance/Store Settings/User Interface/POS, and increase the default POS screen timeout or set it to zero to disable the timeout.� Refresh the system.

To adjust the timeout in QuickService, edit the Aloha.ini in the Aloha application software NewData folder and increase the FOHTIMEOUT variable's value or set the value to zero to disable the timeout.� Refresh the system.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3213 flash flashes

Default Report Output to Text or Printer

Default Report Output to Text or Printer

============================================================================

AKBID3214

Created: 20 August 2001

Updated: 20 August 2001

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

The ALOHA^� application software outputs the House Account report, Menu Item Prices by Name/Number report, System Parameter report, and guest check or employee checkout reprints to either the screen via the default text editor (usually Microsoft^� Windows^� Notepad) or directly to the default printer.

The default output setting is assigned by the PrintToScreen variable in the WIN.INI.� To edit the default value assigned to this variable, edit the WIN.INI in the Windows folder, navigate to the [Ibertech] section, and assign the PrintToScreen variable a value of '0' to output the report to a printer or '1' to output the reports to the screen.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3214

DOWNTIME.INI Updates

DOWNTIME.INI Updates

============================================================================

AKBID3215

Created: 20 August 2001

Updated: 19 July 2002

Reviewed: 10 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

============================================================================

The ALOHA^� application software only updates the DOWNTIME.INI on each Front-of-House (FOH) terminal when the FOH is initializing or if a different file server is elected.� The DOWNTIME.INI is not updated when a different master terminal is elected (unless the terminal is restarted).

You should not use the DOWNTIME.INI as a reference to reliably determine the master terminal.� Instead, you should use the terminal's Debugging-Output-File (debout) to reliably determine the master terminal (as seen by that terminal).

============================================================================

See also:

AKBID1107 Aloha Application Software Fault Tolerance Functionality

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3215

Enabling the TableService PLU Button

Enabling the TableService PLU Button

============================================================================

AKBID3216

Created: 29 August 2001

Updated: 20 November 2002

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 4.0x � 5.3.x

============================================================================

You can enable the Price Look-up (PLU) button on the ALOHA^� application software either globally on each submenu or only in select submenu button positions.

To enable the PLU button so it appears as the last button on each submenu, open Aloha Manager and select Maintenance/Store Settings/User Interface.� Click the Order Entry tab and select 'Place PLU/SKU Button On POS Submenus'.

To enable a PLU button only in a specific location on a submenu, do not enable the PLU button as explained in the previous steps.� Instead, create a new button and assign the button to item number 999999.

Although you cannot change the button text ('PLU'), you can assign a bitmap that includes a text label to the PLU button (refer to document AKBID3133).

When you enter a PLU number in the Front-of-House (FOH), the Aloha application software first searches for a match in the list of SKU numbers for each item and then searches the item ID numbers for a match.

============================================================================

See also:

AKBID3133 TableService PLU Button BMP

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3216

'License File Not Found' Error

'License File Not Found' Error

============================================================================

AKBID3217

Created: 1 October 2001

Updated: 18 March 2002

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x

============================================================================

The ALOHA^� application software displays one of the following errors if the license agreement file (ALOHA.LIC) does not exists in the Aloha application software folder (for example, D:\ALOHA\ALOHA.LIC):

'License Note Found.� Please reinstall your license agreement'

'The Aloha POS License Agreement is either missing or corrupt.� Please contact Customer Service for assistance'

To suppress these errors from occurring when you start Aloha Manager, copy the ALOHA.LIC file from the Aloha Installation CD to the local Aloha application software folder.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3217

Issued Certificate Report Status Codes

Issued Certificate Report Status Codes

============================================================================

AKBID3218

Created: 1 October 2001

Updated: 1 October 2001

Reviewed: 11 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

When viewed on-screen, the ALOHA^� application software BackOffice Issued Gift Certificate report displays a Status field.� The Status column is a series of one-character codes that indicate what has happened to the certificate since it's creation (in chronological order).

The codes are as follows:

Code

Description

F

Redeemed in full

U

Partially redeemed and the existing gift certificate was updated with the new balance

N

Partially redeemed and a new gift certificate was issued for the balance

C

Partially redeemed and cash was issued for the balance

E

Redemption erased

R

Reissued

P

Printed

D

Destroyed

Therefore, the status code 'PC' means that the certificate was printed and later partially redeemed with cash given as change.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3218 gc

style='mso-spacerun:yes'>� 2003

Changing a SuperSite Store's Date-of-Business

Changing a SuperSite Store's Date-of-Business

============================================================================

AKBID3219

Created: 1 October 2001

Updated: 2 October 2001

Reviewed: 16 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

Although the Front-of-House terminals in an ALOHA^� application software SuperSite update their ALOHA.INI from their store's folder on the SuperSite file server, they replace the Date-of-Business (DOB) in the ALOHA.INI with the local DOB rather than using the DOB from the store folder.� Furthermore, the DOB in the ALOHA.INI in the store's folder on the SuperSite file server is not updated during the End-of-Day (EOD) process.� In other words, a SuperSite store's DOB is controlled on the store-level, not on the SuperSite file server.

If you need to manually change the DOB in a SuperSite store, you must do so by manually editing the ALOHA.INI on each terminal and refreshing the store.� You are only required to change the DOB on the master terminal for the change to take effect, but it is possible that another terminal will acquire master-terminal status upon refreshing the system, so Aloha Technologies advises you to change the DOB on all of the store's terminals before refreshing the system.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3219 day

style='mso-spacerun:yes'>� 2003

Hourly Sales and Labor Report Revenue Accumulation

Hourly Sales and Labor Report Revenue Accumulation

============================================================================

AKBID3220

Created: 12 December 2001

Updated: 2 December 2003

Reviewed: 10 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x - 5.3.x

============================================================================

The ALOHA^� application software Back-of-House (BOH) Hourly Sales and Labor report accumulates sales as items are ordered, not when the check is opened on closed.

Additionally, all of the sales from a given check are attributed to the same time increment as when the first item was added to the check.� For example, if the first item on a check is added at 3:05 PM, then the report will attribute all subsequent sales on the check to the same time increment, as if they were also sold at 3:05 PM.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3220

Real-time Virus Protection Can Effect Aloha Performance

Real-time Virus Protection Can Effect Aloha Performance

============================================================================

AKBID3221

Created: 8 January 2002

Updated: 20 March 2003

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC, BackOffice

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

Real-time virus protection can have a substantial and negative effect on the performance of the ALOHA^� application software if you have set your virus protection software to scan all file types instead of only scanning file types that are common to viruses.

Refer to document AKBID1117 for more information on using anti-virus software with the Aloha application software.

============================================================================

See also:

AKBID1117 Using Anti-virus Software on FOH Terminals

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3221 slow

Windows 95 Illegal Operation with AlohaSpy

Windows 95 Illegal Operation with AlohaSpy

============================================================================

AKBID3222

Created: 20 February 2002

Updated: 20 February 2002

Reviewed: 27 February 2004

Microsoft Windows Versions: Windows 95

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

If an ALOHA^� application software Front-of-House (FOH) terminal that us running Microsoft^� Windows^� 95 experiences an illegal operation error when you enable AlohaSpy, you must install the Microsoft Winsock2 update on the FOH terminal.� The Winsock2 update is available from the \Misc\Winsock2 folder on the Aloha Installation CD.� You can also install the Winsock2 update using the FOH installation application (Setuptrm.exe) and enabling the Winsock2 update option.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3222 general protection fault gpf

NOREBOOTAFTERSYNCH in the ALOHA.INI

NOREBOOTAFTERSYNCH in the ALOHA.INI

============================================================================

AKBID3223

Created: 20 February 2002

Updated: 20 February 2002

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: N/A

============================================================================

The NOREBOOTAFTERSYNCH variable in the ALOHA^� application software ALOHA.INI is no longer used.� Never fully implemented, is disabled Front-of-House (FOH) from restarting following synchronization.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3223

NOORDERLOCKING in the ALOHA.INI

NOORDERLOCKING in the ALOHA.INI

============================================================================

AKBID3224

Created: 20 February 2002

Updated: 20 February 2002

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService

Aloha POS Versions: 3.8x � 5.3.x

============================================================================

The NOORDERLOCKING variable in the ALOHA^� application software Aloha.ini disables order locking enforcement.� You should not enable this variable unless specifically told to do so by Aloha Technologies.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3224

NEWEOD in the Aloha.ini

NEWEOD in the Aloha.ini

============================================================================

AKBID3225

Created: 20 February 2002

Updated: 20 February 2002

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: N/A

============================================================================

The NEWEOD variable in the ALOHA^� application software Aloha.ini is no longer used.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3225

FSRECOVERYEOD in the ALOHA.INI

FSRECOVERYEOD in the ALOHA.INI

============================================================================

AKBID3226

Created: 20 February 2002

Updated: 8 August 2003

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

============================================================================

The FSRECOVERYEOD variable in the ALOHA^� application software Aloha.ini instructs the Front-of-House (FOH) to attempt a file server recovery before running the End-of-Day (EOD) process.� This only applies to event-fired EOD processes.� This does not apply to forced EOD processes.�

You should not enable this variable unless specifically told to do so by Aloha Technologies.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3226

FOH Login Screen Memory Availability and Usage Figures

FOH Login Screen Memory Availability and Usage Figures

============================================================================

AKBID3227

Created: 21 February 2002

Updated: 21 February 2002

Reviewed: 2 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

Depending on the version of the ALOHA^� application software, the Front-of-House (FOH) login screen displays the following system memory information using two or four figures along the bottom of the screen:

Outer Left � Displayed in all versions, this figure represents the amount of available memory.

Inner Left � Displayed in versions 4.0x and lower, this figure represent the amount of resource memory available.

Inner Right � Displayed in all versions, this figure represents the amount of memory used by the FOH.

Outer Right � Displayed in some versions prior to 4.0x, this figure represents the memory utilization percentage, which is the FOH memory usage divided by the total available memory.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3227 corners RAM

Setting a Custom Resolution in Panel Editor

Setting a Custom Resolution in Panel Editor

============================================================================

AKBID3228

Created: 26 February 2002

Updated: 26 February 2002

Reviewed: 2 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.210 � 5.3.x

============================================================================

The ALOHA^� application software enables you to configure a custom resolution for use in Panel Editor by enabling the ALOHAPEXRES and ALOHAPEYRES system environment variables.� This is designed to assist you in creating screens for terminals with odd-sized screens, such as handheld PCs.� Set the screen width using the ALOHAPEXRES variable and the screen height using the ALOHAPEYRES variable.� For example:

SET ALOHAPEXRES=320

SET ALOHAPEYRES=240

You can select the custom resolutions using the [custom] selection in Panel Editor's list of resolutions.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3228 ce handhelds

Enabling the Substitute Modifier Button

Enabling the Substitute Modifier Button

============================================================================

AKBID3229

Created: 11 April 2002

Updated: 11 April 2002

Reviewed: 12 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

============================================================================

If you assign a Substitute Group to a Modifier Group in the ALOHA^� application software Back-of-House (BOH), the FOH displays a 'Subst' button on the modifier screen along with the No, Side and Extra buttons.� Touching the substitute button enables you to replace an item on the modifier group for an item in the substitution group.

============================================================================

See also:

Aloha QuickService or TableService User Manual

AKBID3079 NOMODCODES in ALOHA.INI

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3229

style='mso-spacerun:yes'>� 2003

Ameranth Terminal Connection Failure Error

Ameranth Terminal Connection Failure Error

============================================================================

AKBID3230

Created: 15 April 2002

Updated: 15 April 2002

Reviewed: 16 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 5.026 - 5.3.x

============================================================================

If you receive an error on a handheld device using the Ameranth Wireless, Inc.^� 21^st Century Restaurant^� system stating 'Login: Terminal communications failure', verify that the handheld device is using a terminal ID that is defined in the ALOHA^� application software, and that you have assigned the correct interface host to the terminal in Aloha Manager.� Refer to document AKBID1182 for more information on configuring terminals for use with Ameranth.

============================================================================

See also:

AKBID1182 COM Interface Configuration

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3230

style='mso-spacerun:yes'>� 2003

Multi-site EOD Run Date Error

Multi-site EOD Run Date Error

============================================================================

AKBID3231

Created: 15 April 2002

Updated: 15 April 2002

Reviewed: 15 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The ALOHA^� application software displays the following error in the DEBOUT.SVR if the EODDATE variable is not properly configured in the SQL.INI:

CTLSVR: Multisite EOD Error � Last Run Date Not Available

To rectify the problem, edit the SQL.INI in the Aloha application software SQL folder and set the EODDATE variable to reflect yesterday's date (for example, EODDATE=04 14 2002).� If the EODDATE variable does not exist, add it to the [IbertechSQL] section of the SQL.INI.

If you do not properly configure the EODDATE variable, some CTLSVR.EXE (Control Server) functions, such as purging the RDB, will not occur.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3231 sql supersite

style='mso-spacerun:yes'>� 2003

Remote Printers Continuously Print Chits

Remote Printers Continuously Print Chits

============================================================================

AKBID3232

Created: 18 April 2002

Updated: 18 April 2002

Reviewed: 17 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

Faulty printer cables are the leading cause of the ALOHA^� application software continuously printing single or multiple chits.� If this problem occurs, verify the printer configuration with document AKBID1002 and replace all cables and adapters associated with the printer.

============================================================================

See also:

AKBID1002 Aloha Receipt and Kitchen Printer Settings and Pin-outs

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3232

style='mso-spacerun:yes'>� 2003

Adding Memory Status Updates to FOH Debouts

Adding Memory Status Updates to FOH Debouts

============================================================================

AKBID3233

Created: 18 April 2002

Updated: 18 April 2002

Reviewed: 18 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.260 � 5.3.x

============================================================================

The ALOHA^� application software Front-of-House (FOH) will update the current memory status to the local terminal debout (refer to document AKBID1134) if you add the MEMORYSTATUSINTERVAL variable the ALOHA.INI, and assign it a value based on the number of seconds between update intervals (for example, MEMORYSTATUSINTERVAL=60).

The information in the debout includes memory status for Physical, Page, Virtual, and Smart Heap memory, with the first three types displaying both available memory and total memory.

============================================================================

See also:

AKBID1134 Debouts

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3233 leak leaks

style='mso-spacerun:yes'>� 2003

House Account Log Record Types

House Account Log Record Types

============================================================================

AKBID3234

Created: 29 April 2002

Updated: 29 April 2002

Reviewed: 9 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

The following record types are used in the ALOHA^� application software house account log file:

CREDIT � Defines a credit transaction

DEBIT � Defines a debit transaction

FORWARD � Defines a consolidated balance of purged and printed transactions

PAYMENT � Defines a payment transaction

The PRINT and PURGE fields are used in internally by the Aloha application software and are of no significance since they are always assigned a value of FALSE when you view them.

Refer to document AKBID1012 for more information on viewing house account log files.

============================================================================

See also:

AKBID1012 Aloha Application Software Utility Description and Usage

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3234 export house32 house50

Excluding Voids from Gross Sales on Checkouts

Excluding Voids from Gross Sales on Checkouts

============================================================================

AKBID3235

Created: 14 May 2002

Updated: 14 May 2002

Reviewed: 25 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.235 � 5.3.x

============================================================================

By default, the ALOHA^� application software includes voids in the gross sales listed on the employee checkouts.� You can exclude voids from the gross sales on the employee checkouts by setting the CHECKOUTVOIDSNOTINGROSS variable in the ALOHA.INI to TRUE.� If the variable does not already exists in the ALOHA.INI, add it and set the value to TRUE.

This variable only affects the gross sales listed on the employee checkout.� It does not change the gross sales amount on any other reports.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3235 check-out

Aloha Manager is Missing Drop-down Menus or Menu Options

Aloha Manager is Missing Drop-down Menus or Menu Options

============================================================================

AKBID3236

Created: 14 May 2002

Updated: 14 May 2002

Reviewed: 25 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

If ALOHAMGR.EXE (Aloha Manager) is missing drop-down menus or drop-down menu options, verify that the CTL4X.DLL, MNT4X.DLL, and USERTOOL.DLL applications are registered.� The easiest way to verify successful registration is to manually register them, and verify that they return a successful response.� Refer to document AKBID1019 for more information on manually registering and un-registering the ALOHA^� application software.

The following .DLL files affect the following drop-down menus:

CTL4X.DLL � Functions, Reports, Utilities

MNT4X.DLL � Maintenance

USERTOOL.DLL � Tools

============================================================================

See also:

AKBID1019 Manually Registering and Un-registering Aloha Applications

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3236

MASTERTERMINALID in the ALOHA.INI

MASTERTERMINALID in the ALOHA.INI

============================================================================

AKBID3237

Created: 14 May 2002

Updated: 14 May 2002

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

The MASTERTERMINALID variable in the ALOHA.INI enables users to designate a specific terminal as the master terminal.� While this is a requirement in versions of the ALOHA^� application software that do not include fault tolerance functionality, or if the fault tolerance functionality is disabled, it is ignored if fault tolerance is required or enabled.� Refer to document AKBID1107 for more information on the Aloha application software fault tolerance functionality.

Fault tolerance is not available in TableService versions 3.5x and lower.� Fault tolerance is optional in TableService versions 3.6x through 4.2x.� Fault tolerance is always enabled (and cannot be disabled) in QuickService versions 3.8x and higher and in TableService versions 5.0x and higher.

============================================================================

See also:

AKBID1107 Aloha Application Software Fault Tolerance Functionality

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3237

System Date Set to Prior Year Reports Log Corruption

System Date Set to Prior Year Reports Log Corruption

============================================================================

AKBID3238

Created: 15 May 2002

Updated: 15 May 2002

Reviewed: 19 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The ALOHA^� application software may report TRANS.LOG (transaction log) or printer log corruption if the system date is set to a year prior to the year in which the log was created.

If you have a complete Aloha application software installation or a single Front-of-House (FOH) terminal consistently reporting log corruption, verify that the system date on the file server and all FOH terminals is set to the correct date.�

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3238 0 attempting corrupt error errors from position recover zero

Dated Folders Missing from Reprint or Audit Report Lists

Dated Folders Missing from Reprint or Audit Report Lists

============================================================================

AKBID3239

Created: 21 May 2002

Updated: 21 May 2002

Reviewed: 20 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

While most of the reports in the ALOHA^� application software rely on the grind files and, thus, use the Gnddbf30.xxx file to determine whether or not to include a dated folder in the list of dates to report, the Audit Report and reprint reports gather data directly from the Trans.log (transaction log), so they use the Done30 file to determine whether or not to include a dated folder in the list of dates to report.

If you have a dated folder that is present in all other report date lists but not present in the date lists for the Audit Report or reprint reports, verify that the dated folder contains a Done30 file.� Refer to document AKBID1015 for more information on the Done30 file.

============================================================================

See also:

AKBID1015 EOD Process and Errors

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3239

NETBIOSERRORTHRESHOLD in the ALOHA.INI

NETBIOSERRORTHRESHOLD in the ALOHA.INI

============================================================================

AKBID3240

Created: 31 May 2002

Updated: 15 March 2004

Reviewed: 15 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2.4.0 � 5.3.x

============================================================================

If the ALOHA^� application software experiences excessive NetBIOS network errors, it displays the following error message on the Front-of-House (FOH) terminal's Debugging-Output-File (debout), and restarts the terminal:

'This terminal is getting too many NETBIOS errors.� It is being rebooted in an attempt to fix the problem.'

The default error threshold is 30 errors per hour, but you can change the default threshold with the NETBIOSERRORTHRESHOLD variable in the ALOHA.INI, although Aloha Technologies does not recommend changing this value.� Assign the variable a value representing the desired per hour threshold.� Do not use the NETBIOSERRORTHRESHOLD variable as a patch for network problems.

Do not ignore these NetBIOS errors or mask them using the NETBIOSERRORTHRESHOLD variable.� Doing so can lead to corrupt logs, missing checks, and other 'strange anomalies' in the Aloha application software.� You should not experience enough NetBIOS errors in a healthy environment to ever reach this threshold, so Aloha Technologies strongly recommends that you find and fix the root problem rather than masking it using the NETBIOSERRORTHRESHOLD variable.

In the event that a FOH terminal restarts because is has reached the threshold, an explanation is provided in the terminal's Debugging-Output-File (debout).� Refer to document AKBID1134 for more information on debouts.

============================================================================

See also:

AKBID1134 Debouts

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3240

Merging Transaction Logs

Merging Transaction Logs

============================================================================

AKBID3241

Created: 23 July 2002

Updated: 26 February 2004

Reviewed: 26 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The ALOHA^� application software can merge two transaction logs (TRANS.LOG) using GRIND.EXE or GRINDQ.EXE.� To merge the logs, place the two logs in the dated folder (or DATA for the current day).� The grind process renames the two logs to TRANS.BK1 and TRANS.BK2 and creates a new TRANS.LOG.� The command line is GRIND.EXE followed by /MERGETRANSLOGS, /DATE, the name of the dated folder you wish to grind, the name of the first TRANS.LOG and the name of the second TRANS.LOG.� For example:

GRIND.EXE /DATE 20000112 /MERGETRANSLOGS TRANS.LOG TRANS1.LOG

An alternative method of merging two TRANS.LOG files is to use the COPY /B command.� 'COPY' is a standard Microsoft^� Windows^� command, and the '/B' indicates binary files.� For example, the following command line will merge TRANS1.LOG and TRANS2.LOG into a single TRANS.LOG:

COPY /B TRANS1.LOG+TRANS2.LOG TRANS.LOG

Merging transaction logs is not always successful.� Radiant Systems cannot guarantee that the merge will always yield successful results.

============================================================================

See also:

AKBID1016 Grind Process and Errors

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3241 consolidate

Hard Check Printer Only Prints One Line Per Check

Hard Check Printer Only Prints One Line Per Check

============================================================================

AKBID3242

Created: 25 July 2002

Updated: 25 July 2002

Reviewed: 13 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x

============================================================================

If the ALOHA^� application software Front-of-House (FOH) only prints one line per check when using a hard check printer, open Aloha Manager, select Maintenance/Store Settings/Printing/Check Style, and verify that you have properly configured the number of hard check lines per sheet.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3242 checks hard-check hardcheck printer printing slip slips

Suppressing Errors for Temporary Terminals

Suppressing Errors for Temporary Terminals

============================================================================

AKBID3243

Created: 1 August 2002

Updated: 1 August 2002

Reviewed: 23 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

If an ALOHA^� application software terminal is offline, all of the other terminals display an error stating so.� If you have a terminal that is not regularly used and is not always online, you can suppress these errors by unassigning any printers from the terminal (set the terminal to None in printer maintenance).� Since the terminal is no longer configured to drive a printer, then the Aloha application software suppresses the error message since there is not a compelling reason to report the problem.

============================================================================

See also:

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3243 down remove

FOH Check Numbering Scheme

FOH Check Numbering Scheme

============================================================================

AKBID3244

Created: 23 August 2002

Updated: 15 July 2003

Reviewed: 2 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

The ALOHA^� application software numbers Front-of-House (FOH) guest checks by the terminal ID number and a consecutive four-digit number starting with one.� The terminal number is assigned using the terminal in which the check was created.� For example, check number 10001 is the first check created by terminal one, 1230001 is the first check created by terminal 123, check number 20456 is the 456^th check created by terminal two.

All check numbers are reset during the End-of-Day (EOD) process.

Gaps in the consecutive check numbers can occur because of merged checks, transferred checks, training checks (which do not use a separate numbering queue), or empty checks.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3244 missing

CTLSVR.EXE Says Another Terminal with the Same Number

CTLSVR.EXE Says Another Terminal with the Same Number

============================================================================

AKBID3245

Created: 27 August 2002

Updated: 27 August 2002

Reviewed: 8 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The ALOHA^� application software does not support two instances of CTLSVR.EXE (Control Server) on the same network broadcasting the same TERMSTR.� If two computers have Control Server running with the same TERMSTR, you will receive the following error in DEBOUT.SVR:

Fatal error: There is another terminal on the network with the same terminal number

Unless you are using the REMOTE variable (refer to document AKBID3110), you cannot have multiple copies of Control Server on the same network using the same TERMSTR.� You must assign each copy of Control Server to a different TERMSTR.

============================================================================

See also:

AKBID3110 The Remote Variable

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3245

QuickService Modifiers to not Auto Flow to Next Modifier

QuickService Modifiers to not Auto Flow to Next Modifier

============================================================================

AKBID3246

Created: 27 August 2002

Updated: 28 August 2002

Reviewed: 8 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService

Aloha POS Versions: 3.8x � 5.3.x

============================================================================

If your ALOHA^� application software QuickService modifiers to not automatically flow to the next modifier group, verify that the 'Exempt Bartenders from Flow' option is not enabled in the modifier configuration.� While this is primarily a TableService option and only appears in the MNT.EXE (Maintenance) ALOHAMGR.EXE (Aloha Manager) user interface for TableService, you can still enable or disable this option in QuickService.

While this setting is stored in the NOFLOWBAR column in the MOD.DBF, it is easier to perform the following to enable this option on modifiers in QuickService:

Close Maintenance or Aloha Manager.

Delete the FASTFOOD flag from the Aloha application software folder.� This enables Maintenance or Aloha Manager to open in TableService mode.

Open Maintenance or Aloha Manager, and select the 'Exempt Bartenders from Flow' option for the modifiers.

Close Maintenance or Aloha Manager.

Recreate the FASTFOOD flag from the Aloha application software folder.� This enables Maintenance or Aloha Manager to open in QuickService mode.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3246

Shifts are not Listed on Labor Reports

Shifts are not Listed on Labor Reports

============================================================================

AKBID3247

Created: 29 August 2002

Updated: 29 August 2002

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.8x � 5.3.x

============================================================================

If employees or labor shifts are missing from ALOHA^� application software labor reports, verify that 'Do not print job code' is not enabled for the job code in question.

Also verify that 'Auto Clockout' is enabled in Maintenance/Store Settings/Labor/Employee Settings.� If this setting is disabled, the End-of-Day (EOD) process discards any shifts where the employee did not clock-out.

============================================================================

See also:

AKBID3071 Incomplete Labor Reports

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3247 report

IBM SurePOS 500-xx2 Serial Port Pin-outs and Printer Cables

IBM SurePOS 500-xx2 Serial Port Pin-outs and Printer Cables

============================================================================

AKBID3248

Created: 3 September 2002

Updated: 3 September 2002

Reviewed: 12 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.026 � 5.3.x

============================================================================

The IBM^� SurePOS 500-xx2 POS terminals uses the following pin assignments for its RJ45-based serial ports:

Pin

1

2

3

4

5

6

7

8

Signal

DSR

CD

DTR

Ground

RXD

TXD

CTS

RTS

Use the following pin-outs to adapt a standard ALOHA^� application software printer cable from the IBM RJ45 serial port to a printer's DB25 port:

RJ45

5

6

4

7

DB25

2

3

7

20

Use the following pin-outs to adapt a standard Aloha application software printer cable from the IBM RJ45 serial port to a printer's DB9 port:

RJ45

5

6

4

7

DB9

3

2

5

4

Use the following pin-outs to adapt an IBM SureMark printer cable from the IBM RJ45 serial port to the printer's DB9 port:

RJ45

1

2

3

4

5

6

7

8

DB9

6

1

4

5

2

3

8

7

Use the following pin-outs to adapt a standard Aloha application software printer cable from the IBM RJ45 serial port to a printer's DB25 port using a RJ45-to-DB25 adaptor:

RJ45

1

2

3

4

5

6

7

8

Wire

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB25

Unused

Unused

Unused

7

2

3

20

Unused

Use the following pin-outs to adapt a standard Aloha application software printer cable from the IBM RJ45 serial port to a printer's DB9 port using a RJ45-to-DB9 adaptor:

RJ45

1

2

3

4

5

6

7

8

Wire

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB9

Unused

Unused

Unused

5

3

2

4

Unused

Use the following pin-outs to adapt an IBM SureMark printer cable from the IBM RJ45 serial port to a printer's DB9 port using a RJ45-to-DB9 adaptor:

RJ45

1

2

3

4

5

6

7

8

Wire

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB9

6

1

4

5

2

3

8

7

============================================================================

See also:

AKBID1002 Aloha Receipt and Kitchen Printer Settings and Pin-outs

AKBID1172 IBM SurePOS 500

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3248 4610 532 542 com db-9 db-25 pin-out pinout rj-45 xx2

style='mso-spacerun:yes'>� 2003

QSR Ethernet Creates Very Large Transaction and Video Logs

QSR Ethernet Creates Very Large Transaction and Video Logs

============================================================================

AKBID3249

Created: 5 September 2002

Updated: 11 November 2002

Reviewed: 12 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.412 � 5.3.x

============================================================================

If you are using an Ethernet-based version of QSR^� Automations' Kitchen-Video-System (KVS) and you are experiencing an abnormally large ALOHA^� application software TRANS.LOG (transaction log) or VIDEO.LOG (video log), then verify that multiple Front-of-House (FOH) terminals are not configured to drive the same video devices.

If multiple FOH terminals are configured (using QSRVIDEOS environment variable) to drive the same video device, then each terminal is sending duplicate order messages and bumps to each video device and log file.� This also creates additional burden on the network, which can slow down the FOH terminal's and video device's performance.

If your QSR terminals are configured as Primary and Secondary Hosts, edit the QSR configuration in order to change them to Stand Alone Hosts.� Refer to document AKBID1115 for more information.

============================================================================

See also:

AKBID1115 Configuring QSR Automations RDS Ethernet Video

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3249 kds kitchen rds-2000 rds2000

Offline Gift Card Authorizations do not Print Balance on Receipt

Offline Gift Card Authorizations do not Print Balance on Receipt

============================================================================

AKBID3250

Created: 5 September 2002

Updated: 5 September 2002

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2.5.x � 5.3.x

============================================================================

If the ALOHA^� application software has to authorize a gift card offline, then it will not print the gift card balance on the receipt since it cannot connect to the processor in order to get the amount.� If the gift card is authorized online, then the Aloha application software will print the gift card balance on the receipt.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3250

Brother Report Printer Prints Reports Inverted and Reversed

Brother Report Printer Prints Reports Inverted and Reversed

============================================================================

AKBID3251

Created: 5 September 2002

Updated: 5 September 2002

Reviewed: No longer reviewed

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

If you are using a Brother^� printer to print ALOHA^� application software reports in the Back-of-House (BOH) and it prints reports that are inverted or reversed, perform the following:

Open the printer properties in Microsoft^� Windows^�.

Open the Print Processor settings.

Change the processor from Brother to Winprt.

Click OK to exit the settings and printer properties.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected]..

Additional query words: 3251 backward backwards inversed

Cash Drawer Opens Each Time the Printer Prints

Cash Drawer Opens Each Time the Printer Prints

============================================================================

AKBID3252

Created: 6 September 2002

Updated: 6 September 2002

Reviewed: 15 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.8x � 5.3.x

============================================================================

The ALOHA^� application software supports Epson printers with internal and external enunciators (beepers).� To activate beeps after a print job has completed, specify a number of beeps in printer maintenance in Aloha Maintenance or Aloha Manager.

The Aloha application software sends beep requests to cash drawer port number one.� If you configure or attach a cash drawer to an Epson printer's cash drawer port number one, and you have one or more printer beeps enabled, the cash drawer will open each time the printer prints because it is attempting to initialize the beeper.� You must disable the printer beeps or connect cash drawers to cash drawer port number two.

============================================================================

See also:

AKBID3154 Epson Printer Enunciators

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3252 chit fire fires pop pops receipt

Caf� Service Errors

Caf� Service Errors

============================================================================

AKBID3253

Created: 19 September 2002

Updated: 19 September 2002

Reviewed: 12 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

If the ALOHA^� application software Front-of-House (FOH) displays errors regarding caf� service, disable caf� service in the ALOHA.INI in the NEWDATA folder by setting the COFFEE to a value of FALSE, and refresh the system.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3253 coffeeshop shop

style='mso-spacerun:yes'>� 2003

Supported Gift Card Transaction Types and Codes

Supported Gift Card Transaction Types and Codes

============================================================================

AKBID3254

Created: 30 September 2002

Updated: 30 September 2002

Reviewed: 27 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 5.2.5.x � 5.3.x

============================================================================

The ALOHA^� application software supports the following transaction types for Paymentech gift cards:

Transaction Type

Transaction Code

Current or Future Support

Issuance/Add Value

70

Current

Activation

71

Current

Block Activation

72

Current

Redemption

73

Current

Prior Issuance/Add Value

74

Future

Prior Activation

75

Future

Prior Redemption (Force)

77

Future

Void

78

Current

Redemption Auth Only

80

Future

Redemption Auth Completion

81

Future

Deactivation

82

Current

Reactivation

83

Future

Balance Inquiry

79

Current

The Aloha application software supports the following transaction types for ValueLink gift cards:

Transaction Type

Transaction Code

Current or Future Support

Activate

0100

Current

Redemption

0200

Future

Redemption Unlock

0201

Current

Redemption NO NSF

0202

Current

Reload

0300

Current

Inquire Current Balance

0400

Current

Inquire Current Balance with Lock

0401

Current

Inquire Current Balance with Partial Lock

0402

Future

Inquire Transaction History

0410

Future

Balance Merge

0420

Future

Balance Adjustment

0460

Future

Replacement

0500

Future

Report Lost/Stolen

0501

Future

Cash Out

0600

Future

Timeout Reversal

0704

Current

Void of Redemption/Cashout

0800

Current

Void of Reload

0801

Current

Void of Activation

0802

Current

Void of Balance Merge

0806

Future

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3254 giftcard link online payment paytech tech value

Reversing Comp Calculation Order

Reversing Comp Calculation Order

============================================================================

AKBID3255

Created: 30 September 2002

Updated: 30 September 2002

Reviewed: 19 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2.5.x � 5.3.x

============================================================================

By default, the ALOHA^� application software gives dollar-off comps priority over percent-off comps if both comps are applied to the same check.� If you want the Aloha application software to apply percent-off comps to the check's items prior to applying dollar-off comps, then you must set the APPLYPERCENTCOMPSFIRST variable in the ALOHA.INI to a value of TRUE (APPLYPERCENTCOMPSFIRST=TRUE).

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3255

style='mso-spacerun:yes'>� 2003

Accounting for a Traveling Cash Till on a Single Checkout

Accounting for a Traveling Cash Till on a Single Checkout

============================================================================

AKBID3256

Created: 1 October 2002

Updated: 1 October 2002

Reviewed: 18 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

If you are using traveling cash drawer in QuickService, where an employee and their cash till move between multiple cash drawers, you can still account for the employee's sales (and cash till contents) on a single checkout if you employ the proper method for adding and removing the employee from each cash drawer.

You must use the Manage Drawers function to initially assign the employee to the first cash drawer, but you must then use the Assign Drawer function to assign the employee to any subsequent cash drawers.� Always use Manage Drawers to de-assign the employee from each cash drawer.

In summary:

-          Use Manage Drawers for the initial assignment.

-          Use Assign Drawer for subsequent assignments.

-          Use Manage Drawers for de-assignments.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3256 breaking floating roaming

style='mso-spacerun:yes'>� 2003

FOH Cannot Start with Disconnected Veridicom Scanners

FOH Cannot Start with Disconnected Veridicom Scanners

============================================================================

AKBID3257

Created: 11 October 2002

Updated: 11 October 2002

Reviewed: 12 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x.

============================================================================

The ALOHA^� application software Front-of-House (FOH) cannot start if you have disconnected Veridicom thumbprint scanners.

To start the FOH, you must disable the thumbprint scanner in the Aloha Back-of-House (BOH) and refresh the system.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3257 fails finger fingerprint print thumb

Problems Installing MDAC 2.6 in Windows 2000

Problems Installing MDAC 2.6 in Windows 2000

============================================================================

AKBID3258

Created: 15 October 2002

Updated: 15 October 2002

Reviewed: 16 December 2003

Microsoft Windows Versions: Widows 2000

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.017 � 5.3.x

============================================================================

If you are installing the ALOHA^� application software on a Microsoft^� Windows^� 2000 file server and you cannot successfully install the Microsoft Data Access Components (MDAC) version 2.6, then download MDAC version 2.7 from Microsoft and install them on the file server.

In some cases, Windows 2000 will not let the Aloha application software overwrite an older version of MDAC with MDAC 2.6, but it will let you overwrite them with MDAC version 2.7

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3258

style='mso-spacerun:yes'>� 2003

Windows does not Read MSR without a Keyboard Attached

Windows does not Read MSR without a Keyboard Attached

============================================================================

AKBID3259

Created: 15 October 2002

Updated: 30 July 2003

Reviewed: 13 February 2004

Microsoft Windows Versions: Windows 2000, Windows XP

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.017 � 5.3.x

============================================================================

If Microsoft^� Windows^� 2000, Windows XP, or Windows Server 2003 does not read keyboard-based Magnetic-Stripe-Readers (MSRs) without a keyboard attached, perform the following in the Windows registry in order to fix this problem:

The incorrect use of the Windows Registry Editor can lead to serious, system-wide problems that may require the reinstallation of the operating system.� Use this tool at your own risk.�

1.        To open the Windows Registry Editor, select Start/Run, type REGEDIT.EXE, and click OK.�

2.        Path out HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\i8042prt\Parameters.

3.        Verify the Headless value exists in the folder.� If it does, double-click it and change Value Data to '1'.� If it does not exist, choose Edit/New/DWORD Value and name the key 'Headless'.� Then double-click the entry and change Value Data to '1'.

4.        Select Registry/Exit to exit the Windows Registry Editor.�

5.        Restart Windows.

If you are using Windows 2000, you must also install Windows 2000 Service Pack 3 or higher.

In some cases, it is the BIOS that is disabling the keyboard port, not Windows.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3259

QuickService Counter Service Errors

QuickService Counter Service Errors

============================================================================

AKBID3260

Created: 4 November 2002

Updated: 15 July 2003

Reviewed: 6 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService

Aloha POS Versions: 3.8x � 5.3.x

============================================================================

If you receive an error in the ALOHA^� application software Front-of-House (FOH) stating 'Counter Service limited to at most 3 printer(s)', then you must edit the ALOHA.INI and change the value of the COUNTERVERSION variable to FALSE.

Setting the value to TRUE enables the Counter Service option, which limits the number of terminals and printers available for use with the Aloha application software FOH.� The Counter Service option is no longer used.

If you receive an error in the Aloha application software FOH stating 'Only authorized for Counter Service', then HASP security key was mistakenly created for Counter Service.� The Counter Service option is available in the key generation software at Aloha Technologies, but since the Counter Service option is obsolete, it does not appear on the key information sheet, so there is no way to confirm if this option was selected for the HASP security key in question.� The only way to confirm that this is the root problem is to obtain a new HASP security key without the Counter Service option enabled.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3260 counterservice

SETUPPOS.EXE Opens a Visual Basic Editor

SETUPPOS.EXE Opens a Visual Basic Editor

============================================================================

AKBID3261

Created: 4 November 2002

Updated: 4 November 2002

Reviewed: 26 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.0x � 5.3.x

============================================================================

Some Microsoft^� Office products include a built-in Visual Basic^� editor.� If one of these products is active when you install the ALOHA^� application software using SETUPPOS.EXE, it is possible that the Office product will intercept certain Microsoft Windows^� command issues by SETUPPOS.EXE and open the command in a Visual Basic window.

If this occurs, close all open Office applications prior to running SETUPPOS.EXE.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3261 compile creategroup dim error private startup sub syntax vb

'BarDlgFunc: no table!' Error in TableService FOH

'BarDlgFunc: no table!' Error in TableService FOH

============================================================================

AKBID3262

Created: 30 January 2003

Updated: 30 January 2003

Reviewed: 25 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 3.8x � 5.3.x

============================================================================

If the ALOHA^� application software displays an error in the Front-of-House (FOH) stating 'BarDlgFunc: no table!', return all terminals to a floating logo, and delete any .OLK and .LCK files that exist in the DATA folder on the file server or FOH terminals.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3262 bardlgfunc ok

Equinox ESP 8 10/100 Serial Hub Printer Cable Pin-outs

Equinox ESP 8 10/100 Serial Hub Printer Cable Pin-outs

============================================================================

AKBID3263

Created: 11 November 2002

Updated: 20 November 2002

Reviewed: 8 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x

============================================================================

The Equinox ESP 8 10/100 Serial Hub uses the following pin assignments for its RJ45-based serial ports:

Pin

1

2

3

4

5

6

7

8

Signal

RTS

DSR

CD

RXD

TXD

GND

DTR

CTS

Use the following pin-outs to adapt a standard ALOHA^� application software printer cable from the Equinox ESP 8 10/100 Serial Hub's RJ45 port to a printer's DB25 port:

RJ45

4

5

6

8

DB25

2

3

7

20

Use the following pin-outs to adapt a standard Aloha application software printer cable from the Equinox ESP 8 10/100 Serial Hub's RJ45 port to a printer's DB9 port:

RJ45

4

5

6

8

DB25

3

2

5

4

Use the following pin-outs to adapt a standard Aloha application software printer cable from the Equinox ESP 8 10/100 Serial Hub's RJ45 port to a printer's DB25 port using a RJ45-to-DB25 adaptor:

RJ45

1

2

3

4

5

6

7

8

Wire

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB25

Unused

Unused

Unused

2

3

7

Unused

20

Use the following pin-outs to adapt a standard Aloha application software printer cable from the Equinox ESP 8 10/100 Serial Hub's RJ45 port to a printer's DB9 port using a RJ45-to-DB9 adaptor:

RJ45

1

2

3

4

5

6

7

8

Wire

Blue

Orange

Black

Red

Green

Yellow

Brown

White

DB9

Unused

Unused

Unused

3

2

5

Unused

4

============================================================================

See also:

AKBID1002 Aloha Receipt and Kitchen Printer Settings and Pin-outs

AKBID3269 Equinox SST-8P Serial I/O Adaptor Printer Cable Pin-outs

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3263 com db-9 db-25 pin-out pinout rj-45

Zero-byte .OLK Files Cause Windows Illegal Operation

Zero-byte .OLK Files Cause Windows Illegal Operation

============================================================================

AKBID3264

Created: 12 November 2002

Updated: 12 November 2002

Reviewed: 27 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

Errant zero-byte .OLK files in the ALOHA^� application software DATA folder can result in intermittent Microsoft^� Windows^� Illegal Operation errors in the Front-of-House (FOH).� These zero-byte files are the result of network, hardware, or power problems.� You can resolve this issue by deleting the zero-byte .OLK files from the file server and each FOH terminal, but do not delete the 4-byte .OLK files.

============================================================================

See also:

AKBID3011 OLK Files

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3264 blue screen of death bsd bsod general protection fault gpf

Incorrect ALS Installation Path Causes 'Anomalies'

Incorrect ALS Installation Path Causes 'Anomalies'

============================================================================

AKBID3265

Created: 12 November 2002

Updated: 12 November 2002

Reviewed: 2 March 2004

Microsoft Windows Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The target destination used by the ALOHA^� application software Aloha Labor Scheduler (ALS) installation application defaults to C:\ALOHA\BACKOFFICE\SCHEDULE, but you must ensure that you edit this destination to reflect true location of the Aloha application software folder.� You must install ALS within the %IBERDIR%\BACKOFFICE\SCHEDULE folder, where %IBERDIR% is the true location of your existing Aloha application software folder.� Failure to do so can result in various 'anomalies' and errors associated with ALS.

If you previously installed ALS in the wrong location, perform the following to reinstall ALS in the correct location:

Create a backup copy of the current ALS DATA folder (for example, D:\ALOHA\BACKOFFICE\SCHEDULE\DATA) and its contents.

Uninstall ALS via the Microsoft^� Windows^� Add/Remove Programs Control Panel applet.

Reinstall ALS in the correct folder.

Copy the information from the previous installation's DATA folder to the new installation's DATA folder.

============================================================================

See also:

Aloha Labor Scheduler User Manual

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3265

Configuring Network-based Receipt Printers with Aloha

Configuring Network-based Receipt Printers with Aloha

============================================================================

AKBID3266

Created: 14 November 2002

Updated: 14 November 2002

Reviewed: 29 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.222 � 5.3.x

============================================================================

The ALOHA^� application software Front-of-House (FOH) does not directly support network-based printers for receipts and chits, but since the FOH does support OLE for Retail Point-of-Sale (OPOS) printers and Windows-based printers, then the FOH can support network-based printers through either of these technologies.

In order to configure these printers in the Aloha application software, you only need to configure them as you would standard OPOS or Windows-based printer.� You must then consult the printer manufacturer's documentation for more information on configuring their OPOS or Windows drivers and their hardware for use as a network-based printer.

============================================================================

See also:

AKBID1026 Using Windows-based Printers with Aloha

AKBID1074 OPOS

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3266 ethernet ip network tcp tcp/ip

'Processor Not Configured' Error with Private Label Credit Cards

'Processor Not Configured' Error with Private Label Credit Cards

============================================================================

AKBID3267

Created: 14 November 2002

Updated: 14 November 2002

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 5.0x

============================================================================

If you use a private label card name that is longer than 10 characters, then the ALOHA^� application software Front-of-House (FOH) will return an error stating 'Processor Not Configured'.

To fix this problem, open EDC.EXE (EDC), disable POS processing, select Configure/Private Label Cards, and enter a 'Card Name' that is 10 characters or less.

You can use card names that are longer than 10 characters in versions 5.2x and higher.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3267 directnet

Purging ALS Data in Order to Increase Available Disk Space

Purging ALS Data in Order to Increase Available Disk Space

============================================================================

AKBID3268

Created: 15 November 2002

Updated: 15 November 2002

Reviewed: 4 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 5.2.6.x � 5.3.x

============================================================================

The ALOHA^� application software stores historical Aloha Labor Scheduler (ALS) schedule data, labor projections, and sales projections that can, over time, consume disk space.� For this reason, you should consider a method for purging this data on a regular basis.

Schedule files are stored in the Aloha application software SCHEDULE folder and they are labeled using the SSYYMMDD.DBF format.� Each schedule file also has a corresponding .CDX file, which contains the database's index information.� Labor projection files are stored in the Aloha application software PROJ folder and they are labeled using the LPYYMMDD.DBF format.� Sales projection files are stored in the Aloha application software PROJ folder and they are labeled using the SPYYMMDD.DBF format.

In order to determine the best method of purging this data, you must consider the client's requirements for historical information.� Aloha Technologies strongly recommends archiving the data prior to deleting it, and you must also consider how much historical data to keep on hand.� Since there is not built-in method for actually deleting the files, then you must also determine your own method for deleting the files.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3268 drive free full hard harddrive increase purge

Equinox SST-8P Serial I/O Adaptor Printer Cable Pin-outs

Equinox SST-8P Serial I/O Adaptor Printer Cable Pin-outs

============================================================================

AKBID3269

Created: 19 November 2002

Updated: 20 November 2002

Reviewed: 8 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x

============================================================================

The Equinox SST-8P Multiport Serial I/O Adaptor card uses the following pin assignments for its DB25-based serial ports:

Pin

2

3

4

5

6

7

8

20

Signal

TXD

RXD

RTS

CTS

DSR

GND

CD

DTR

The Equinox SST-8P Multiport Serial I/O Adaptor card uses the following pin assignments for its DB9-based serial ports:

Pin

1

2

3

4

5

6

7

8

Signal

CD

RXD

TXD

DTR

GND

DSR

RTS

CTS

Use the following pin-outs to adapt a standard ALOHA^� application software printer cable from the Equinox SST-8P Multiport Serial I/O Adaptor card 's DB25 port to a printer's DB25 port:

DB25

3

2

7

5

DB25

2

3

7

20

Use the following pin-outs to adapt a standard Aloha application software printer cable from the Equinox SST-8P Multiport Serial I/O Adaptor card 's DB25 port to a printer's DB9 port:

DB25

3

2

7

5

DB9

3

2

5

4

Use the following pin-outs to adapt a standard Aloha application software printer cable from the Equinox SST-8P Multiport Serial I/O Adaptor card 's DB9 port to a printer's DB25 port:

DB9

2

3

5

8

DB25

2

3

7

20

Use the following pin-outs to adapt a standard Aloha application software printer cable from the Equinox SST-8P Multiport Serial I/O Adaptor card 's DB9 port to a printer's DB9 port:

DB9

2

3

5

8

DB9

3

2

5

4

============================================================================

See also:

AKBID1002 Aloha Receipt and Kitchen Printer Settings and Pin-outs

AKBID3263 Equinox ESP 8 10/100 Serial Hub Printer Cable Pin-outs

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3269 com db-9 db-25 pin-out pinout rj-45

Configuring EDC TCP Timeout and Retries

Configuring EDC TCP Timeout and Retries

============================================================================

AKBID3270

Created: 21 November 2002

Updated: 21 November 2002

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

ALOHA^� Products: EDC

Aloha POS Versions: 5.2x � 5.3.x

============================================================================

By default, EDCSVR.EXE (EDC Server) is configured to timeout after 20 seconds and attempt four retries when authorizing a credit card using a TCP-type connection.� You can configure different values using the WaitForTCPResponseMessageTimeout and AuthRetries variables in the [System] section in the EDC.INI.� For example:

[System]

WaitForTCPResponseMessageTimeout=20

AuthRetries=4

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3270 dsl internet ssl tcp/ip

Too Many Delivery Orders Causes FOH to Exit

Too Many Delivery Orders Causes FOH to Exit

============================================================================

AKBID3271

Created: 2 January 2003

Updated: 2 January 2003

Reviewed: 27 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

Incompatible files installed by some versions of Microsoft Internet Explorer can cause the ALOHA^� application software Front-of-House (FOH) to exit to the desktop or restart the computer if you have more than a single page of open delivery orders.

To fix this problem, install Internet Explorer version 5.5 or higher.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3271 down drop error general protection fault gp gpf line page

Configuring POSIFLEX PD-2500 Customer Display

Configuring POSIFLEX PD-2500 Customer Display

============================================================================

AKBID3272

Created: 9 January 2003

Updated: 3 April 2003

Reviewed: 19 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.0x � 5.3.x

============================================================================

The ALOHA^� application software supports the POSIFLEX Business Machines, Inc. PD-2500 customer display using either Mintronix emulation or OPOS drivers.

Regardless of the interface method, use the following DIP switch settings in order to configure the customer display communications settings for 9600 baud, no parity, 8 data bits, 1 stop bit, and Epson emulation:

DIP Switch

1

2

3

4

5

6

Setting

On

Off

On

Off

Off

Off

Regardless of the interface method, use the following pin-outs with the RD-2500:

Serial DB9

1

2

3

4

5

6

7

8

Display DB9

1

2

3

4

5

6

7

8

Serial DB25

8

3

2

20

7

6

4

5

Display DB9

1

2

3

4

5

6

7

8

If you are configuring the customer display using Mintronix emulation, configure the display as a Mintronix 2x20 Line Display in the Aloha application software, and assign it to appropriate serial port.

If you are configuring the customer display using OPOS, configure the display as an OPOS customer display in the Aloha application software, and install the OPOS drivers provided by the manufacturer.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3272 line pole rear

style='mso-spacerun:yes'>� 2003

NCR OPOS MSR Stops Working After First Swipe

NCR OPOS MSR Stops Working After First Swipe

============================================================================

AKBID3273

Created: 22 January 2003

Updated: 22 January 2003

Reviewed: 17 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2.5.101 � 5.3.x

============================================================================

NCR Magnetic-Stripe-Readers (MSRs) driven by some versions of the NCR OPOS drivers might stop functioning after the first card swipe.� If this occurs, you can enable the NCR_MSR_FIX system environment variable in ALOHA^� application software version 5.2.5.101 and higher, and assign it a value of TRUE (for example, SET NCR_MSR_FIX=TRUE) in order to fix this problem.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3273 7454 7460 card one single

EDC 'CEdcDlg::OnInitDialog' Error

EDC 'CEdcDlg::OnInitDialog' Error

============================================================================

AKBID3274

Created: 22 January 2003

Updated: 22 January 2003

Reviewed: 18 February 2004

Microsoft^� Windows^� Versions: All

ALOHA^� Products: EDC

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

If EDC.EXE (EDC) displays an error stating 'CEdcDlg::OnInitDialog cannot find <file server name>\BOOTDRV\<Aloha folder name>', then EDC does not have access to the BOOTDRV share on the local computer.� The easiest way to confirm this is to select Start/Run, enter \\<file server name>\BOOTDRV\<Aloha folder name>, and click OK.� If you receive an error and cannot access the BOOTDRV share, then the local computer cannot access its own BOOTDRV share.

This is usually caused by problems related to the network.� Verify that the network if functioning properly and that the user has read and write access to the BOOTDRV share.� In cases where a store is part of a large corporate network, then the local computer might not have access to the domain controller in order to verify access privileges for the current user.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3274 alohaboh alohaqs cedcdlg oninitdialog

Configuring the Flytech POS600 MSR for Use with Aloha

Configuring the Flytech POS600 MSR for Use with Aloha

============================================================================

AKBID3275

Created: 31 January 2003

Updated: 31 January 2003

Reviewed: 10 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The ALOHA^� application software supports the Flytech POS600 Magnetic-Stripe-Reader (MSR) model P1-505-55-0NN using a keyboard interface.� You must open the communications settings and perform the following in the configuration utility provided by Flytech in order for the MSR to function with the Aloha application software:

-          Select the Output Characters tab and set the Select Terminator to CR.

-          Select the Magnetic Reader tab and set the Separator Character to NUL.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3275 600

Configuring the Flytech POS600 Customer Display

Configuring the Flytech POS600 Customer Display

============================================================================

AKBID3276

Created: 31 January 2003

Updated: 31 January 2003

Reviewed: 26 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.231 � 5.3.x

============================================================================

The ALOHA^� application software supports the Flytech POS 600 customer display model P0730601 using Mintronix emulation.�� Configure the customer display as a Mintronix 2x20 Line Display in the Aloha application software, and configure the customer display communications settings for 9600 baud, no parity, 8 data bits, 1 stop bit, and Epson ESC/POS emulation.

Use the following pin-outs with the customer display:

Serial DB9

1

2

3

5

6,8

Display RJ45

1,2

8

7

3,4

6

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3276 600 line pole rear

Configuring the CRS IT-8000 2X20 Rear Customer Display

Configuring the CRS IT-8000 2X20 Rear Customer Display

============================================================================

AKBID3277

Created: 3 February 2003

Updated: 3 February 2003

Reviewed: 26 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.231 � 5.3.x

============================================================================

The ALOHA^� application software supports the CRS IT-8000 2X20 Rear Customer Display using either Mintronix emulation or OPOS drivers.

Regardless of the interface method, configure the DIP switches on the customer display to the following settings in order to set the display's communication settings to 9600 baud, no parity, 8 data bits, 1 stop bit:

Switch

1

2

3

4

5

6

7

8

Setting

Off

Off

Off

Off

Off

Off

Off

Off

Regardless of the interface method, use the following pin-outs with the customer display:

Serial DB9

1

2

3

4

5

6

7

8

Display

1

2

3

4

5

6

7

8

If you are configuring the customer display using Mintronix emulation, configure the display as a Mintronix 2x20 Line Display in the Aloha application software, and assign it to COM 4.

If you are configuring the customer display using OPOS, configure the display as an OPOS customer display in the Aloha application software, and install the OPOS drivers provided by the manufacturer.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3277 cash pole register systems

NEVERPRINTFOHWAGES in the ALOHA.INI

NEVERPRINTFOHWAGES in the ALOHA.INI

============================================================================

AKBID3278

Created: 7 February 2003

Updated: 2 June 2003

Reviewed: 15 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2.7.x � 5.3.x

============================================================================

The NEVERPRINTFOHWAGES variable in the ALOHA^� application software ALOHA.INI suppresses wage information from the Front-of-House (FOH) Restaurant Labor report in QuickService or the FOH Clock In/Out Times report in TableService.�

In versions 5.2.8.x and higher, you can open ALOHAMGR.EXE (Aloha Manager), and select Store Settings/Printing/Reports/Suppress FOH Labor Report Wages in order to access this setting.

If you assign this variable a value of TRUE in QuickService, then the FOH does not include the wage information with the report.�

If you assign this variable a value of TRUE in TableService, then the FOH does not prompt the user whether or not to print the wages, and the report does not include wage information with the report.�

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3278

Configuring a T.O.D.D. System Controller in Aloha

Configuring a T.O.D.D. System Controller in Aloha

============================================================================

AKBID3279

Created: 11 February 2003

Updated: 11 February 2003

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService

Aloha POS Versions: 5.2.7.x � 5.3.x

============================================================================

The ALOHA^� application software uses the following pin-outs for communication with the Chuck E. Cheese's T.O.D.D. System Controller (token dispenser):

Serial DB9

1

3

4

T.O.D.D. DB9

2

3

7

To enable token distribution, open ALOHAMGR.EXE (Aloha Manager), select Maintenance/Store Settings/Token Distribution, and select 'Use Token Distribution'.

To configure the T.O.D.D., open Aloha Manager, select Maintenance/Hardware/Terminals/Other, and configure the dispenser type and port.

Token distribution configuration dialogue is only available in Aloha Manager if your HASP^� security key has this feature enabled.

Refresh the system.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3279 cec cheese coin pin-out pinout t.o.d. tod todd

Port Used by EDCSVR.EXE for SSL Credit Card Authorization

Port Used by EDCSVR.EXE for SSL Credit Card Authorization

============================================================================

AKBID3280

Created: 13 February 2003

Updated: 13 February 2003

Reviewed: 2 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

The ALOHA^� application software EDCSVR.EXE (EDC Server) application uses port 443 for credit card authorizations via a SSL or HTTPS connection.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3280 authorize broadband dsl http internet ip process processing tcp tcp/ip tcpip

Internet Credit Card Authorization via a Proxy Server

Internet Credit Card Authorization via a Proxy Server

============================================================================

AKBID3281

Created: 13 February 2003

Updated: 13 February 2003

Reviewed: 4 March 2004

Microsoft Windows Versions: All

Aloha Products: EDC

Aloha POS Versions: 5.2.5.106 � 5.3.x

============================================================================

The ALOHA^� EDCSVR.EXE (EDC Server) application versions 5.2.5.106 and higher use the proxy server configuration from Microsoft^� Internet Explorer in order to authorize credit cards over the internet via a proxy server.�

Since the Internet Explorer proxy server settings are configured separately for each user, you must login to Microsoft Windows^� using the same user name and password that EDC Server uses in order to configure the proxy server settings used by EDC Server.� Once you have configured the settings, you can revert back to your standard login user.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3281 authorize broadband dsl http https internet ip process processing tcp tcp/ip tcpip

Configuring the J2 800 CX MSR for Use with Aloha

Configuring the J2 800 CX MSR for Use with Aloha

============================================================================

AKBID3282

Created: 14 February 2003

Updated: 14 February 2003

Reviewed: 10 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The ALOHA^� application software supports the J2 800 CX MSR Magnetic-Stripe-Reader (MSR) using a keyboard interface.� You must open the communications settings and perform the following in the configuration utility provided by Flytech in order for the MSR to function with the Aloha application software:

-          Select the Output Characters tab and set the Select Terminator to CR.

-          Select the Magnetic Reader tab and set the Separator Character to NUL.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3282

Configuring the ID TECH MiniMag Compact MSR for Aloha

Configuring the ID TECH MiniMag Compact MSR for Aloha

============================================================================

AKBID3283

Created: 27 February 2003

Updated: 27 February 2003

Reviewed: 9 March 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

The ALOHA^� application software supports the ID TECH MiniMag Compact Magnetic Stripe Reader (keyboard wedge), but you must edit the default configuration in order for it to work with the Aloha application software.

By default, the Magnetic-Stripe-Reader (MSR) is programmed with a carriage-return after each track.� You must configure the MSR so it only has a carriage-return at the end of the entire read.� To do this, attach the MSR to a computer, open Microsoft^� Windows^� Notepad, type the following (case sensitive), and press enter (the MSR should beep):

/e/d/fq<space>\nul

Test the MSR to ensure that there is only a single carriage-return at the end of the read.

You cannot use the backspace while typing the programming information.� Instead, you must start over if you make a mistake.� Do not type more than characters per second.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3283 card idtech mag mini

NOVOIDFINALIZEDGCPAYMENTS Variable in the ALOHA.INI

NOVOIDFINALIZEDGCPAYMENTS Variable in the ALOHA.INI

============================================================================

AKBID3284

Created: 14 March 2003

Updated: 14 March 2003

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 5.2.5.123 � 5.3.x

============================================================================

The NOVOIDFINALIZEDGCPAYMENTS variable in the ALOHA^� application software ALOHA.INI is an unsupported feature that was created for a specific client.� Always assign a value of FALSE to this variable (for example, NOVOIDFINALIZEDGCPAYMENTS=FALSE).

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3284 darden

Using LOCALREAD to Decrease Wireless Network Traffic

Using LOCALREAD to Decrease Wireless Network Traffic

============================================================================

AKBID3285

Created: 14 March 2003

Updated: 30 June 2003

Reviewed: 3 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The ALOHA^� application software supports the LOCALREAD system environment variable, which instructs the Front-of-House (FOH) to read the data files from the local Aloha application software DATA folder rather than the file server.�

If you are using a wireless network where bandwidth is a concern, you can enable the LOCALREAD variable on each FOH terminal by assigning it a value of TRUE (for example, SET LOCALREAD=TRUE).� This can decrease the network traffic by 50% or more.

Do not enable the LOCALREAD variable on FOH terminals that are not master or server-capable, unless the terminal also acts as the Aloha application software's file server.� If a terminal is not master or server-capable, it does not synchronize the local DATA folder with the file server, so the information in the local DATA folder is not current.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3285

Removing the 'Clear' Button from the Order Entry Screen

Removing the 'Clear' Button from the Order Entry Screen

============================================================================

AKBID3286

Created: 20 March 2003

Updated: 20 March 2003

Reviewed: 15 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 5.2.5.134 � 5.3.x

============================================================================

In order to remove the 'Clear' button from the ALOHA application software Front-of-House (FOH) order-entry screen, edit the ALOHA.INI in the NEWDATA folder, assign a value of TRUE to the REMOVECLEARBUTTON variable (for example, REMOVECLEARBUTTON=TRUE), and refresh the system.

A blank space will occupy the area previously used by the button.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3286 all disable items suppress

style='mso-spacerun:yes'>� 2003

The Aloha Application Software FF.INI

The Aloha Application Software FF.INI

============================================================================

AKBID3287

Created: 21 March 2003

Updated: 21 March 2003

Reviewed: 10 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.8x � 5.3.x

============================================================================

The ALOHA^� application software FF.INI contains the grid configuration from the Panel Editor options.� In order to edit these settings, open Panel Editor and select Commands/Options.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3287 ff ini

PMS Interfaces Currently Supported by Aloha

PMS Interfaces Currently Supported by Aloha

============================================================================

AKBID3288

Created: 26 March 2003

Updated: 26 March 2003

Reviewed: 17 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 3.5x � 5.3.x

============================================================================

The ALOHA^� application software currently supports the following Property Management System (PMS) interfaces:

Interface

Initial Aloha Support Version

Notes

Generic Micros 4700

3.8x

Most PMS systems support the Micros 4700 interface.

Encore

3.8x

RDP

3.8x

Springer Miller

3.8x

HIS

3.8x

CSS

3.8x

Fidelio

4.2x

Fastech

4.2x

Marriott

4.4x

HIS Preauth

5.0x

============================================================================

See also:

Aloha Hotel Interface User Manual

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3288 auth authorize charge charges hotel room

style='mso-spacerun:yes'>� 2003

Using /DEV to Suppress Customer Data Errors During Testing

Using /DEV to Suppress Customer Data Errors During Testing

============================================================================

AKBID3289

Created: 11 April 2003

Updated: 11 April 2003

Reviewed: 28 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x

============================================================================

The ALOHA^� application software supports the /DEV command line variable for IBER.EXE and IBERQS.EXE (for example, IBER.EXE /DEV or IBERQS.EXE /DEV), which enables you to use a customer's database without having to modify it in order to function on your lab or office equipment.� The /DEV command line variable performs the following:

-          Suppresses End-of-Day (EOD) events.

-          Forces local terminal type to Clone.

-          Forces local Magnetic-Stripe-Reader (MSR) type to keyboard.

-          Forces any local cash drawers to an internal 'dummy' type.

-          Disables any local customer displays.

-          Disables any local barcode scanners.

-          Disables any local coin dispensers.

-          Disables any local pen readers.

-          Disables any local PIN pads.

-          Forces the 'X' cursor to display instead of the 'dot' cursor.

-          Disables all FOH passwords.

-          Forces NUMTERMS to equal the number of configured terminals.

-          In QuickService, it always forces at least one cash drawer to be local.

You must still manually configure your local HASP^� security key.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3289

PRINTSHORTCLOCKOUT in the ALOHA.INI

PRINTSHORTCLOCKOUT in the ALOHA.INI

============================================================================

AKBID3290

Created: 17 April 2003

Updated: 17 April 2003

Reviewed: 11 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 5.2.7.102 � 5.3.x

============================================================================

You can instruct the ALOHA^� application software to print an abbreviated version of the clock-out chit by assigning the PRINTSHORTCLOCKOUT variable in the ALOHA.INI to a value of TRUE (for example, PRINTSHORTCLOCKOUT=TRUE).�

If you enable this feature, then the clock-out chit only contains the following information:

-          Name

-          Date

-          Job

-          Time in

-          Time out

-          Hours this shift

-          Hours this week

-          Sales

-          Carry Over Tips

-          Declared Tips

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3290

Javelin Cash Drawer Ports Cause Fatal Errors

Javelin Cash Drawer Ports Cause Fatal Errors

============================================================================

AKBID3291

Created: 25 April 2003

Updated: 25 April 2003

Reviewed: 26 February 2004

Microsoft Windows Versions: Windows NT, Windows 2000, Windows XP, Windows Server 2003

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.8x � 5.3.x

============================================================================

If you are using the cash drawer ports on a Javelin order-entry terminal with the Microsoft^� Windows NT^�, Windows^� 2000, Windows XP, or Windows Server 2003 operating system (OS), then you must use the Javelin OPOS drivers to access the cash drawer ports rather than the native Javelin cash drawer port drivers built-into the ALOHA^� application software.� Refer to document AKBID1074 for more information on OPOS drivers.

The Aloha application software does not support using the native Javelin cash drawer port drivers in this environment because the Application-Programmer-Interface (API) commands used to communicate to the cash drawer are considered privileged instructions under the these OS platforms.� This can result in fatal errors.

============================================================================

See also:

AKBID1074 OPOS

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3291 error general protection fault gpf

Configuring a VeriFone PIN Pad on 'Port 4' on an IBM 4695

Configuring a VeriFone PIN Pad on 'Port 4' on an IBM 4695

============================================================================

AKBID3292

Created: 25 April 2003

Updated: 25 April 2003

Reviewed: 19 February 2004

Microsoft Windows Versions: All

Aloha Products: QuickService

Aloha POS Versions: 5.2.7.114 � 5.3.x

============================================================================

The ALOHA^� application software supports the connection of a VeriFone PINpad 1000, VeriFone Everest, or VeriFone EverestPlus PIN pad to 'Port 4' on an IBM 4695 POS terminal.� Perform the following in order to configure the PIN pad on port 4:

Remove any real-mode POSS drivers from the C:\CONFIG.SYS if they exist (for example, BASE.SYS, OED-DRVR.SYS, TCH-DRVR.SYS, and OEM-DRVR.SYS).

Configure your VeriFone PIN pad as 4683CN and use port 2A23 (68).

Install and configure IBM POSS for Microsoft^� Windows^�.

Configure the PIN pad type in ALOHAMGR.EXE (Aloha Manager).� The PIN pad port selection in Aloha Manager does not matter.

Create a VERIFONEONIBMPORT system environment variable on the terminal and assign it a value of TRUE (for example, SET VERIFONEONIBMPORT=TRUE).

Connect the PIN pad to port 4.

============================================================================

See also:

AKBID1032 IBM 4596 POS Terminal

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3292 cec cheese cheese's cheeses chuck e

TOFOH.TXN Files

TOFOH.TXN Files

============================================================================

AKBID3293

Created: 25 April 2003

Updated: 24 February 2004

Reviewed: 24 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

Since the ALOHA^� Back-of-House (BOH) does not write directly to the TRANS.LOG (transaction log), it uses TOFOH.TXN files to send messages, instructions, and updates to the Front-of-House (FOH) master terminal, and the master terminal parses the data and appends the information to the transaction log.� Examples include forcing the End-of-Day (EOD) process from the BOH and real-time updates to the FOH.

To update the FOH, the BOH places a TOFOH.TXN in the DATA folder.� The master terminal recognizes the file, appends the information to the current transaction log, and deletes the TOFOH.TXN file.

Like the transaction log, the TOFOH.TXN uses a proprietary binary format, so you cannot view or edit it.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3293

User 1500n Errors in the Debouts

User 1500n Errors in the Debouts

============================================================================

AKBID3294

Created: 2 May 2003

Updated: 2 September 2003

Reviewed: 9 March 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

The ALOHA^� application software uses terminal identification numbers 15000 through 15009 to reference certain applications or objects.� These are internal ID numbers, and they might appear in the Debugging-Output-Files.� Contact the Aloha Customer Service Center (CSC) in order to determine if debout messages that include these ID numbers represent harmful problems.�

Each terminal ID number represents the following applications or objects:

ID Number

Application or Object

15000

EDOLDTM.EXE or EDTPUNCH.DLL

15001

MNT.EXE or MNT4X.DLL

15002

REPRINT.EXE or REPRINTQ.EXE

15003

RPT.EXE

15004

SUM.EXE

15005

GRIND.EXE or GRINDQ.EXE

15006

CTL.EXE or CTL4X.DLL

15007

Master terminal

15008

Terminal receiving time synchronization messages from the file server

15009

PAYRECON.EXE

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3294 found not user

USESHORTCHECKNUMBERFORGC Variable in the ALOHA.INI

USESHORTCHECKNUMBERFORGC Variable in the ALOHA.INI

============================================================================

AKBID3295

Created: 5 May 2003

Updated: 5 May 2003

Reviewed: No longer reviewed

Microsoft^� Windows^� Versions: All

Aloha Products: TableService

Aloha POS Versions: 5.2.8.11 � 5.3.x

============================================================================

The USESHORTCHECKNUMBERFORGC variable in the ALOHA^� application software ALOHA.INI is an unsupported feature that was created for a specific client.� Always assign a value of FALSE to this variable (for example, USESHORTCHECKNUMBERFORGC=FALSE).

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3295 darden

Log Corruption Message on a File Server/Terminal

Log Corruption Message on a File Server/Terminal

============================================================================

AKBID3296

Created: 29 May 2003

Updated: 25 August 2003

Reviewed: 4 March 2004

Microsoft^� Windows^� Versions: Windows NT^�, Windows 2000, Windows XP, Windows Server 2003

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

============================================================================

If you are running both the Front-of-House (FOH) and Back-of-House (BOH) on the same computer and your computer's network name does not properly match the TERMSTR and TERM system environment variables, then the ALOHA^� application software will display a message stating 'EXITING � PREVENTING LOG CORRUPTION', followed by the path and name of the log.� This also results in the creation of an MSYNC file (refer to document AKBID3092), which you must manually delete each time you start the FOH.

To fix this problem, change the computer's network name to accurately reflect the true TERMSTR and TERM system environment variables.� If you are in a test lab environment, you can also temporarily disable CTLSVR.EXE, and force the FOH to assume file server duties in order to suppress this error rather than changing the computer's network name.� You could also disable master and server capability for this instance of the FOH, as long as there is another terminal that can assume the responsibility of the master terminal.

============================================================================

See also:

AKBID3092 MSYNC File

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3296 boh/foh bohfoh foh/boh fohboh msynch multiserver multisync multisynch terminal/server

Senor Tech Co., Ltd. R856008AST Customer Display

Senor Tech Co., Ltd. R856008AST Customer Display

============================================================================

AKBID3297

Created: 30 May 2003

Updated: 30 May 2003

Reviewed: 9 March 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x

============================================================================

The ALOHA^� application software supports the Senor Tech Co., Ltd. R856008AST Customer Display using Mintronix emulation.� Configure the customer display in the Aloha application software as a Mintronix 2x20 Customer Display and assign it to serial (COM) port one.

Ensure that the customer display's communication settings are configured as 9600 baud, no parity, 8 data bits, 1 stop bit.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3297 pole rear robot plus senortech

FOH Loses Magnetic Stripe Passwords Following EOD

FOH Loses Magnetic Stripe Passwords Following EOD

============================================================================

AKBID3298

Created: 2 June 2003

Updated: 2 June 2003

Reviewed: 15 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

If the ALOHA^� application software Front-of-House (FOH) loses magnetic stripe passwords following the End-of-Day (EOD) process, use document AKBID1160 to upgrade the configuration files in order to ensure that they are on the current database version.

If the problem still exists, download CLEARMAG.EXE from the Aloha Technologies FTP site.� This utility will clear all of the passwords from the FOH in order to ensure that there is not any corruption in the password data within the database file.� You will have to re-enter all of the magnetic stripe passwords after performing this task.� Refer to document AKBID1012 for more information on using CLEARMAG.EXE.

Contact the Aloha Customer Support Center (CSC) if you still experience problems with the FOH losing magnetic stripe passwords.

============================================================================

See also:

AKBID1012 Aloha Application Software Utility Description and Usage

AKBID1160 Manually Upgrading Configuration Files in Aloha Manager

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3298 card employee id log in login mag magcard missing password swipe

FOH Receipt and Chit Printers do not Automatically Reroute

FOH Receipt and Chit Printers do not Automatically Reroute

============================================================================

AKBID3299

Created: 2 June 2003

Updated: 2 June 2003

Reviewed: 15 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

If the ALOHA^� application software Front-of-House (FOH) receipt and chit printers do not automatically reroute printing when encountering an error (out of paper, printer off-line, and so on), ensure that the Reroute Timeout in the Back-of-House (BOH) printer configuration is set to a number greater than zero.

The timeout is the amount of time (in seconds) that the Aloha application software waits before rerouting printing to the designated backup printer if the primary printer is in a state of error.� If this is set to zero, then the Aloha application software does not reroute printing to the backup printer.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3299 out rerouting

Aloha FOH Reads Multiple Event Configuration Files

Aloha FOH Reads Multiple Event Configuration Files

============================================================================

AKBID3300

Created: 3 June 2003

Updated: 3 June 2003

Reviewed: 15 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.0x � 5.3.x

============================================================================

When the ALOHA^� application software parses the scheduled events from the events configuration files, it not only reads the standard EVENTS.CFG, but also any file labeled EVENTSx.CFG, where x is one or more characters.� This also includes the EVENTS-S.CFG used for store-specific events in Aloha Centralized Data Management (CDM), and EVENTS-C.CFG, used with Aloha CDM corporate-scheduled events.

If you are experiencing problems with events not firing or occurring at the wrong time, verify that you do not have any extra event configuration files in the Aloha application software NEWDATA and DATA folders.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3300 fire fires initialize initiate run start

Enable the FOH to Process BOH EDC Transactions

Enable the FOH to Process BOH EDC Transactions

============================================================================

AKBID3301

Created: 4 June 2003

Updated: 4 June 2003

Reviewed: 9 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService, EDC

Aloha POS Versions: 5.2.7.139 � 5.3.x

============================================================================

If you authorize or adjust a credit card transaction in the Back-of-House (BOH) using the ALOHA^� application software Electronic Draft Capture (EDC) application, then by default, the Front-of-House (FOH) terminals will not process the transactions into the FOH TRANS.LOG (Transaction Log).� Thus, if you void a credit card in the BOH that originated in the FOH, then the FOH will not compensate for the void.

If you want the FOH to detect and process the .ANS files created by transactions or adjustments originating in the BOH, then you must add the PROCESSBOHEDCTXNS variable to the ALOHA.INI and assign it a value of 1 (for example, PROCESSBOHEDCTXNS=1).�

Remove this variable to disable the FOH from processing EDC transactions and adjustments originating in the BOH.

============================================================================

See also:

AKBID1020 EDC Process

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3301 changes

style='mso-spacerun:yes'>� 2003

Comp and Promo Discount Distribution

Comp and Promo Discount Distribution

============================================================================

AKBID3302

Created: 4 June 2003

Updated: 4 June 2003

Reviewed: 9 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.8x � 5.3.x

============================================================================

The ALOHA^� application software distributes discounts applied to multiple items based on the item price in relation to the total price of all discounted items.

For example, the following would apply to a quick combo promo that discounts $1.00 off of a $4.00 meal:

Item

Original Price

Percent of Total

Promo Allocation

Selling Price

Hamburger

$2.00

50%

$.50

$1.50

French Fries

$1.00

25%

$.25

$.75

Drink

$1.00

25%

$.25

$.75

Total

$4.00

100%

$1.00

$3.00

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3302 comps distribute percentage promos promotions

style='mso-spacerun:yes'>� 2003

Enable PMS Tip or Tender Adjustments on Closed Checks

Enable PMS Tip or Tender Adjustments on Closed Checks

============================================================================

AKBID3303

Created: 9 June 2003

Updated: 9 June 2003

Reviewed: 11 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2.7.136 � 5.3.x

============================================================================

By default, the ALOHA^� application software does not enable you to adjust tip or tender amounts for payments authorized using a Property Management Systems (PMS) after the check has been closed.� If you want to enable users to adjust tip and tender amounts after the check has been closed, you must assign the ALLOWCLOSEDPMSTENDERADJUSTMENT variable in the ALOHA.INI to a value of 1 (for example, ALLOWCLOSEDPMSTENDERADJUSTMENT=1).

============================================================================

See also:

AKBID1062 Property Management Systems

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3303

style='mso-spacerun:yes'>� 2003

Configuring the CRS IT-1000-TM1K-2K 2-track MSR

Configuring the CRS IT-1000-TM1K-2K 2-track MSR

============================================================================

AKBID3304

Created: 23 June 2003

Updated: 23 June 2003

Reviewed: 18 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

The ALOHA^� application software supports the CRS IT-1000-TM1K-2K 2-track Magnetic Stripe Reader (MSR), but you must edit the default configuration in order for it to work with the Aloha application software.

By default, the MSR is programmed with a carriage-return after each track.� You must configure the MSR so it only has a carriage-return at the end of the entire read.� To do this, attach the MSR to a computer, and perform the following:

-          Open Microsoft^� Windows^� Notepad.

-          Open the MSR configuration menu by pressing the left-Ctrl, left-Alt, and F10.� A configuration menu will appear in Notepad.

-          Select 2 (use the top row of the keyboard, not the 10-key pad) for Set Magnetic String.

-          On the new menu, select 3 for Carriage Return.

-          On the new menu, select 4 for After All Data.

-          On the same menu, press 0 for Back.

On the main menu, press 0 to exit.

Test the MSR to ensure that there is only a single carriage-return at the end of the read.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3304 it1000 it-1000

style='mso-spacerun:yes'>� 2003

Configuring the J2 800 CX Customer Display for Use with Aloha

Configuring the J2 800 CX Customer Display for Use with Aloha

============================================================================

AKBID3305

Created: 26 June 2003

Updated: 26 June 2003

Reviewed: 19 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The ALOHA^� application software supports the J2 800 CX customer display using Mintronix emulation.�� Configure the customer display as a Mintronix 2x20 Line Display in the Aloha application software, and configure the customer display communications settings for 9600 baud, no parity, 8 data bits, 1 stop bit, and Epson ESC/POS emulation using the following DIP switch settings:

Switch

1

2

3

4

5

6

7

8

9

10

11

12

Setting

On

Off

Off

On

Off

Off

Off

On

Off

Off

On

Off

Use the following pin-outs with the customer display:

Serial DB9

1

2

3

5

6,8

Display RJ45

1,2

8

7

3,4

6

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3305 line pole rear

style='mso-spacerun:yes'>� 2003

Price Text Overwrites Graphics on AccuVIEW 150 Display Board

Price Text Overwrites Graphics on AccuVIEW 150 Display Board

============================================================================

AKBID3306

Created: 28 July 2003

Updated: 28 July 2003

Reviewed: 11 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.250 � 5.3.x

============================================================================

If you are using an AccuVIEW 150 display board from Texas Digital Systems, Inc. and the price text is overwriting or obstructing the graphics display, then you must edit the display's font configuration in the ALOHA^� application software Back-of-House (BOH).

Open the display board configuration in the Aloha application software BOH and set the font to 'Font 3 � 8 Lines, 23 Cols'.� Larger fonts can overwrite the display graphics section.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3306

Settling Gift Card Transactions in EDC

Settling Gift Card Transactions in EDC

============================================================================

AKBID3307

Created: 30 July 2003

Updated: 30 July 2003

Reviewed: 13 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 5.2.5.x � 5.3.x

============================================================================

Since the ALOHA^� application software creates EDC transaction (TXN) files for each gift card transaction processed by EDC.EXE, you need to periodically 'settle' the gift card transactions in order to clear the TXN files, although the gift card processor does not require settlement as credit card processors do.

If you are using the same processor to process both credit cards and gift cards, then the gift card TXN files are included with the credit card TXN files, so the gift card transactions are settled when you settle your credit card transactions.� You do not need to perform any other steps in order to settle the gift card transactions.

If you use a separate processor for gift cards, then you must settle them by using the Force Settlement feature in EDC.� This will erase the TXN files, but it will not attempt to send any information to the gift card processor.

Do not use the Force Settlement feature with credit card transactions unless you are specifically told to do so by Aloha Technologies support personnel.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3307 paymentech valuelink

Credit Card Adjustments Fail Because of Duplicate Transactions

Credit Card Adjustments Fail Because of Duplicate Transactions

============================================================================

AKBID3308

Created: 30 July 2003

Updated: 30 July 2003

Reviewed: 16 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 5.2.5.140 � 5.3.x

============================================================================

The ALOHA^� application software versions 5.2.5.140 and higher protect against double credit card authorizations by detecting duplicate transactions.� In some cases, this can lead to EDC declining credit card adjustments since the adjustment looks similar to the original transaction.� When this occurs, the EDC debout (DEBOUT.EDC) shows that the transaction was declined because it considered it a duplicate transaction.

To disable duplicate transaction detection, edit the EDC.INI, add the DisableDuplicateTxnChecking variable to the [System] section of the EDC.INI, assign the variable to a value of 1 (for example, DisableDuplicateTxnChecking=1), and restart EDC.EXE (EDC) and EDCSVR.EXE (EDC Server).

You can re-enable duplicate transaction detection by removing the DisableDuplicateTxnChecking variable from the EDC.INI, and restarting EDC and EDC Server.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3308 declines disable duplicate txn checking

Touch Screens Register Touch to the Previously Touched Button

Touch Screens Register Touch to the Previously Touched Button

============================================================================

AKBID3309

Created: 30 July 2003

Updated: 31 July 2003

Reviewed: 18 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.0x � 5.3.x

============================================================================

If you are having issues where the ALOHA^� application software Front-of-House (FOH) registers a second touch at the location of the previously ordered item, then verify the touch mode in the touch screen's configuration.� For example, you touch the Coke button and then the Hamburger button, but it reacts as if you touched the Coke button again.

In this case, ensure that the touch screen is configured to register the touch when the finger is lifted from the button.� For example, 'Liftoff mode' for 3/M Touch Systems/MicroTouch^� touch screens, or 'Click in Release Mode' for Elo TouchSystems touch screens.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3309 anomalies touches touchscreen touchscreens

Historical P-Mix Reports using Current Configuration Data

Historical P-Mix Reports using Current Configuration Data

============================================================================

AKBID3310

Created: 2 September 2003

Updated: 2 September 2003

Reviewed: 9 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2.8.67 � 5.3.x.x

============================================================================

The ALOHA^� application software uses the configuration settings from the most recent date selected when compiling Back-of-House (BOH) reports, but you can configure the Aloha application software to always use the current configuration (the DATA folder) when viewing the Product Mix (P-Mix) report.� This enables you to manipulate your Non-sales Categories in order to shift data and sales while viewing historical data.

To force the P-Mix report to always use the current configuration data, edit the RPT.INI in the NEWDATA folder, add the PmixData variable to the [Ibertech] section, and assign it a value of TRUE (for example, PmixData=TRUE).� Refresh the system.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3310 pmix

Windows 95 Terminals do not Detect Windows 2000+ File Server

Windows 95 Terminals do not Detect Windows 2000+ File Server

============================================================================

AKBID3311

Created: 2 September 2003

Updated: 2 September 2003

Reviewed: 9 March 2004

Microsoft Windows Versions: Windows 95

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.017 � 5.3.x

============================================================================

Front-of-House terminals using the Microsoft^� Windows^� 95 operating system (OS) might not properly detect and connect to ALOHA^� application software file servers using Windows 2000, Windows XP, or Windows Server 2003.� In order to correct this, you must create a HOST file in the Windows folder on each Windows 95 FOH terminal.

In order to configure HOST file, create a new text file in the Windows folder, and label it HOST.� Ensure that you do not include the .TXT file extension commonly associated with text files.� Edit the HOST file with a text editor, and add the following information:

w.x.y.z ALOHABOH #PRE

Replace 'w.x.y.z' with you file server's IP address, and replace 'ALOHABOH' with your file server's network name.� 'PRE' in #PRE must use capital letters.� Save you changes, and restart the terminal.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3311 can cannot find recognize

Configuring VeriFone PIN Pads for Use with Aloha

Configuring VeriFone PIN Pads for Use with Aloha

============================================================================

AKBID3312

Created: 12 September 2003

Updated: 4 February 2004

Reviewed: 4 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService

Aloha POS Versions: 5.2x � 5.3.x

============================================================================

The ALOHA^� application software requires you to configure the VeriFone PINpad 1000, VeriFone Everest, or VeriFone EverestPlus PIN pad to the following settings:

Setting

Value

Baud Rate

9600

Data Bits

7

Parity

Even

Key Management

DUKPT

You must have the PIN pads injected with DUKPT encryption keys by a certified secure injection service, such as VeriFone's.� Contact VeriFone for details about which companies can provide DUKPT encryption keys for their PIN pads.

Refer to document AKBID3198 for a list of processors and versions of the Aloha application software that support debit cards.

============================================================================

See also:

Aloha EDC User Manual

AKBID3198 EDC Processors Currently Supported by Aloha

AKBID3292 Configuring a VeriFone PIN Pad on 'Port 4' on an IBM 4695

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3312 derived unique key per transaction pads veriphone

Forcing End-of-Day from Outside of Aloha

Forcing End-of-Day from Outside of Aloha

============================================================================

AKBID3313

Created: 12 September 2003

Updated: 12 September 2003

Reviewed: 8 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

When you force an End-of-Day (EOD) in the ALOHA^� application software from the Back-of-House (BOH), it sends the EOD request to the Front-of-House (FOH) via a TOFOH.TXN file (refer to document AKBID3293 for more information on TOFOH.TXN files).� If you capture the TOFOH.TXN file and store it in a temporary location, then you can use it again for the same result.

In order to capture the EOD request, disable the FOH terminals and delete any existing TOFOH.TXN files from the Aloha application software DATA folder.� Open ALOHAMGR.EXE (Aloha Manager), and select Utilities/Force End of Day.� This creates a new TOFOH.TXN in the DATA folder with only the EOD request in it.� Move the TOFOH.TXN to a separate folder for storage.� Restart the FOH terminals.

You can initialize the EOD process at anytime by copying the TOFOH.TXN file from the storage location to the Aloha application software DATA folder.� You can use a batch file or another automated process (fired manually or using a scheduled task) to copy the TOFOH.TXN file and force the EOD process.

============================================================================

See also:

AKBID3293 TOFOH.TXN Files

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3313

style='mso-spacerun:yes'>� 2003

QuickService with RDS Consumes System Resources

QuickService with RDS Consumes System Resources

============================================================================

AKBID3314

Created: 12 September 2003

Updated: 12 September 2003

Reviewed: 8 December 2003

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

If you are using a Remote-Display-System (RDS) with the ALOHA^� application software in a QuickService environment, then you must have a FASTFOOD flag in the Aloha application software folder on each Front-of-House (FOH) terminal (for example, D:\ALOHAQS\FASTFOOD).� If the file does not exist, VIDEOMX.DLL will not properly allocate resources, and this can result in terminals consuming too many resources and ultimately slowing down or rebooting.

To create the FASTFOOD flag on a FOH terminal, open a command prompt on each terminal, and type the following command:

ECHO 1 > D:\ALOHAQS\FASTFOOD

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3314 crash kds memory progressive qsr select slow video videomx

style='mso-spacerun:yes'>� 2003

Configuring CES/First Data IPN Terminal ID Numbers

Configuring CES/First Data IPN Terminal ID Numbers

============================================================================

AKBID3315

Created: 17 September 2003

Updated: 4 February 2004

Reviewed: 4 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 5.2.5.x � 5.3.x

============================================================================

If you are using the First Data IPN to authorize credit cards with CES, then you must use Terminal ID numbers that are unique to the method of communication.�

Configure the Terminal ID number for dial-up and TCP/IP authorizations in the processor's Default Settings section of the EDC.EXE (EDC) CES processor configuration (Configure/Processors/CES), and configure the Terminal ID number for SSL authorizations in the First Data IPN section of the EDC CES processor configuration (Configure/First Data IPN).

You only need to configure the Terminal ID number in the First Data IPN section if you are using SSL communication.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3315 dsl FDMS North, Cardnet, First Data North

Printing Multiple Copies of Chits on a Terminal's Local Printer

Printing Multiple Copies of Chits on a Terminal's Local Printer

============================================================================

AKBID3316

Created: 25 September 2003

Updated: 25 September 2003

Reviewed: 17 December 2003

Microsoft^� Windows^� Versions: All

ALOHA^� Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

============================================================================

To print an item on two separate chits on the terminal's local printer, use the 'Reroute Print by Terminal' and the 'Reroute Printer' events.� This way you can manually distribute the chits in the kitchen.

The 'Reroute Print by Terminal' event ensures that the chits print locally, while the 'Reroute Printer' event creates separate chits (whereas the 'Reroute Printer Group' does not).

For example, if you want each terminal to print the chits at the local printer, but you also want to print two copies of each chit, then perform the following in the Aloha application software Back-of-House (BOH):

Configure the physical printer for each terminal.

Create two mock printers for each terminal.� For example, if you have three terminals, you will ultimately create six mock printers.� Since the printer is not real, do not assign it to a terminal.

Create a new printer group, but do not add any printers to it.

Create a new printer group for each terminal, and only add the terminal's two mock printers to it.

Route all items to the empty printer group created in step three.

Create a Reroute Print by Terminal event for each terminal to reroute the empty printer group (created in step three) to the terminal's 'mock printers' group created in step four.

Create a Reroute Print event for each of the terminal's mock printers to the terminal's local physical printer.

Refresh the system.

Any item that is routed to the empty printer group will get rerouted to the terminal's printer group by the Reroute Print by Terminal event.� The mock printers within each terminal's printer group are subsequently rerouted to the local printer by the Reroute Printer event.� Since you are using the Reroute Printer event for the mock printers, each mock printer's output is produced on a separate chit.

You can print than two chits by creating as many mock printers (and printer reroutes) for each terminal as you need.

In versions 5.007 through 5.026, you may have to disable stand-alone chit printing (part of the Aloha application software fault tolerance capabilities) in order for the functionality described in this document to function properly.� To disable stand-alone chit printing, edit the ALOHA.INI in the Aloha application software NEWDATA folder, set the DISABLESTANDALONECHITPRINT variable to TRUE (for example, DISABLESTANDALONECHITPRINT=TRUE), and refresh the system.

============================================================================

See also:

Aloha QuickService and TableService User Manual

AKBID1121 Reroute All Chits to Local Printers

AKBID3106 Separating Chits on a Single Printer

AKBID3193 Printing One Item on Two Chits Using a Single Printer

View this document in Rich-Text-Format (.RTF).

Please report any errors or omissions by email to [email protected].

Additional query words: 3316 bar cut different two remote

style='mso-spacerun:yes'>� 2003

Radiant RJ12 serial port Pin-outs and Cables

Radiant RJ12 serial port Pin-outs and Cables

============================================================================

AKBID3317

Created: 14 January 2004

Updated: 11 February 2004

Reviewed: 12 March 2004

Microsoft Windows Versions: Windows XP

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x

============================================================================

The Radiant Systems P400 and P1550 POS terminals use the following pin assignments for their RJ12-based serial ports:

Pin

1

2

3

4

5

6

Signal

Power/RTS

GND

TXD

RXD

GND

CTS

Use the following pin-outs to adapt a standard ALOHA^� printer cable from the RJ12 serial port to a printer's DB25 port:

RJ12

3

4

5

6

DB25

3

2

7

20

Use the following pin-outs to adapt a standard Aloha printer cable from the RJ12 serial port to a printer's DB9 port:

RJ12

3

4

5

6

DB9

2

3

5

4

Use the following pin-outs to adapt an OPOS or Microsoft^� Windows^� printer cable from the RJ12 serial port to the printer's DB25 port:

RJ12

1

2

3

4

5

6

DB25

6

1

3

2

7

20

Use the following pin-outs to adapt an OPOS or Windows printer cable from the RJ12 serial port to the printer's DB9 port:

RJ12

1

2

3

4

5

6

DB9

6

1

2

3

5

4

Use the following pin-outs to adapt a standard Aloha printer cable from the RJ12 serial port to a printer's DB25 port using a RJ12-to-DB25 adaptor:

RJ12

1

2

3

4

5

6

Wire

White

Black

Red

Green

Yellow

Blue

DB25

Unused

Unused

3

2

7

20

Use the following pin-outs to adapt a standard Aloha printer cable from the RJ12 serial port to a printer's DB9 port using a RJ12-to-DB9 adaptor:

RJ12

1

2

3

4

5

6

Wire

White

Black

Red

Green

Yellow

Blue

DB9

Unused

Unused

2

3

5

4

Use the following pin-outs to adapt an OPOS or Windows printer cable from the RJ12 serial port to a printer's DB25 port using a RJ12-to-DB25 adaptor:

RJ12

1

2

3

4

5

6

Wire

White

Black

Red

Green

Yellow

Blue

DB25

6

1

3

2

7

20

Use the following pin-outs to adapt an OPOS or Windows printer cable from the RJ12 serial port to a printer's DB9 port using a RJ12-to-DB9 adaptor:

RJ12

1

2

3

4

5

6

Wire

White

Black

Red

Green

Yellow

Blue

DB9

6

1

2

3

5

4

============================================================================

See also:

AKBID1002 Aloha Receipt and Kitchen Printer Settings and Pin-outs

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3317 1550 400 db-9 db-25 pin out pinout pinouts rads rj-12

Configuring the Radiant Systems P15xx MSR for Aloha

Configuring the Radiant Systems P15xx MSR for Aloha

============================================================================

AKBID3318

Created: 15 January 2004

Updated: 5 March 2004

Reviewed: 5 March 2004

Microsoft Windows Versions: Windows XP

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x

============================================================================

In order for the Magnetic-Stripe-Reader (MSR) on the Radiant Systems P1510 or P1550 terminal to communicate with the ALOHA^� application software, you must configure it as a keyboard wedge using the P15xx Hardware Settings applet in the Windows Control Panel.� If this applet does not exist, download and install Radiant_P15xx_1.0.7.18.zip from the Aloha FTP site.

Open the P15xx Hardware Settings applet, select the General tab, and enable the 'Enable Radiant MSR Keyboard Wedge (start at boot)' option in the MSR Configuration section.� Restart the terminal.

If you are prompted for files when installing Radiant_P15xx_1.0.7.18.zip, point to the C:\Windows\System32\Drivers folder for .SYS files and C:\Windows\System32 for .DLL files.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3318 1510 1550 card magcard rads

Enabling FOH EDC Transactions for Less Than $1.00

Enabling FOH EDC Transactions for Less Than $1.00

============================================================================

AKBID3319

Created: 16 January 2004

Updated: 16 January 2004

Reviewed: 16 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x

============================================================================

By default, the ALOHA^� application software Front-of-House (FOH) does not enable EDC credit card transactions for amounts less than $1.00.� You can enable the ability to perform transactions for less than $1.00 by assigning a value of TRUE to the EDCNOFLOORLIMIT variable in the ALOHA.INI.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3319

EGI Causes Windows Error on DigiCom Terminals

EGI Causes Windows Error on DigiCom Terminals

============================================================================

AKBID3320

Created: 29 January 2004

Updated: 29 January 2004

Reviewed: 29 January 2004

Microsoft Windows Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2.5.x � 5.3.x

============================================================================

If you have enable the Enhanced-Graphical-Interface (EGI) in the ALOHA^� application software Front-of-House (FOH) on a terminal manufactured by DigiCom International, Inc. and you experience fatal errors in Microsoft^� Windows^� when you touch the screen from the floating logo, then you must access the display properties and modify the type of hardware acceleration.

In the display adaptor's advanced properties, you have four options in regards to hardware acceleration:

1.        None � 'No accelerator functions'

2.        1/3 mark � 'Basic accelerator functions'

3.        2/3 mark � 'Most accelerator functions'

4.        Full � 'All accelerator functions'

You must configure one of the first two settings.� Because of compatibility issues, you cannot use the third or fourth settings with EGI.

============================================================================

See also:

AKBID1216 Enabling and Configuring FOH Enhanced Graphical Interface

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3320 gpf general protection fault

DEFAULTREVENUECENTER in the ALOHA.INI

DEFAULTREVENUECENTER in the ALOHA.INI

============================================================================

AKBID3321

Created: 29 January 2004

Updated: 29 January 2004

Reviewed: 29 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: N/A

============================================================================

The DEFAULTREVENUECENTER variable in the ALOHA^� application software Aloha.ini is not an active variable and is not currently used.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3321

RDB Report Date Ranges

RDB Report Date Ranges

============================================================================

AKBID3322

Created: 29 January 2004

Updated: 29 January 2004

Reviewed: 29 January 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.0x � 5.3.x

============================================================================

The ALOHA application software determines the range of dates available for a report from data in a Relational-Database (RDB) by querying the tables associated with the report for the lowest and highest Date-of-Business (DOB) that is part of the record key for the primary records that are used.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3322

Non-SERVERCAPABLE Terminals do not Sync Config Files

Non-SERVERCAPABLE Terminals do not Sync Config Files

============================================================================

AKBID3323

Created: 30 January 2004

Updated: 26 February 2004

Reviewed: 26 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 3.6x � 5.3.x

============================================================================

If you assign a value of FALSE to the SERVERCAPABLE environment variable on an ALOHA^� Front-of-House (FOH) terminal, then the terminal will not synchronize the local BMP, DATA, and RECIPE folders with those on the file server.

If you install software that is activated by the FOH reading a new variable in the ALOHA.INI (such as Aloha eCard), then you must manually copy the updated ALOHA.INI to any terminal in which the SERVERCAPABLE environment variable is assigned a value of FALSE.

However, the terminal will still synchronize the local BIN folder with the BIN folder on the file server.

In this case, since the terminal does not update the local configuration files with the information from the file server, you should not enable the LOCALREAD environment variable on any terminal in which you assign a value of FALSE to the SERVERCAPABLE variable.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3323

FASTECHGIFTCERT=Obsolete in the ALOHA.INI

FASTECHGIFTCERT=Obsolete in the ALOHA.INI

============================================================================

AKBID3324

Created: 4 February 2004

Updated: 4 February 2004

Reviewed: 4 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2.4.x � 5.3.x

============================================================================

The FASTECHGIFTCERT variable in the ALOHA.INI is no longer used in versions 5.2.4.x and higher, so the ALOHA^� application software assigns it a value of 'Obsolete' in order to denote its obsolescence.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3324

First Data IPN Requires DW.DLL

First Data IPN Requires DW.DLL

============================================================================

AKBID3325

Created: 4 February 2004

Updated: 4 February 2004

Reviewed: 4 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: EDC

Aloha POS Versions: 5.2.5.x � 5.3.x

============================================================================

If you are using First Data IPN in order to authorize credit cards with EDC and experience authorization or configuration issues, then you must ensure that DW.DLL resides in the ALOHA^� BIN folder.

If it does not, extract it from \ALOHATS\EDC.ZIP or \ALOHAQS\EDC.ZIP on the Aloha installation CD, and restart EDC.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3325 dsl internet

Radiant P701 Customer Display OPOS Configuration

Radiant P701 Customer Display OPOS Configuration

============================================================================

AKBID3326

Created: 16 February 2004

Updated: 23 April 2004

Reviewed: 23 April 2004

Microsoft Windows Versions: Windows XP

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x

============================================================================

The ALOHA^� application software currently supports the Radiant Systems P701 customer display using OPOS drivers.� You can configure the serial port assignment using the X200 Hardware Settings applet in the Microsoft^� Windows^� Control Panel.

You must also perform the following in order to manually install the display's OPOS control object:

Download radiant_p701_opos_ocx.zip from the Radiant Hospitality Systems FTP site and extract the contents into the \X200\OPOS\Drivers folder on the terminal.

Double-click Registeropos.cmd in order to register OPOSLineDisplay.ocx, and you should receive a successful registration confirmation.

Restart the terminal.

Once you have configured the control object, you can continue to configure the device in Aloha as explained in document AKBID1074.� You must configure the OPOS name in Aloha to RadsLineDisplay.

============================================================================

See also:

AKBID1074 OPOS

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3326 400 701 p400 pole display rads rear display

Radiant 16-inch Printer Driven Cash Drawer Cable Pin-outs

Radiant 16-inch Printer Driven Cash Drawer Cable Pin-outs

============================================================================

AKBID3327

Created: 19 February 2004

Updated: 19 February 2004

Reviewed: 5 March 2004

Microsoft^� Windows^� Versions:

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

The Radiant Systems 16-inch Printer Driven Cash Drawer supports printers manufactured by Epson, Ithaca (TransAct), and Star Micronics.� While the drawer is the same for each type of printer, the printer cable is unique to each printer.

Use the following pin-outs with an Epson printer:

Printer

Cash Drawer

1

1

2

2

4

3

6

4

Use the following pin-outs with an Ithaca printer:

Printer

Cash Drawer

2

5

3

6

4

3

5

2

6

1

Use the following pin-outs with a Star Micronics printer:

Printer

Cash Drawer

1

1

2

2

3

3

6

4

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3327 CD00046 pin outs pin out pinouts pinout rads wire

'Got Message Type 287 from BOH' Message in Debouts

'Got Message Type 287 from BOH' Message in Debouts

============================================================================

AKBID3328

Created: 26 February 2004

Updated: 26 February 2004

Reviewed: 26 February 2004

Microsoft^� Windows^� Versions: All

Aloha Products: QuickService, TableService

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

Messages in the ALOHA application software Front-of-House (FOH) Debugging-Output-Files (debouts) stating 'Got Message Type 287 from BOH' are informational messages that Edit Punch is updating the FOH with time and attendance adjustments for current day.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3328 debout

Configuring the Radiant Systems P1210 Integrated MSR

Configuring the Radiant Systems P1210 Integrated MSR

============================================================================

AKBID3329

Created: 2 March 2004

Updated: 2 March 2004

Reviewed: 2 March 2004

Microsoft^� Windows^� Versions: Windows XP

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.217 � 5.3.x

============================================================================

The ALOHA^� application software supports the Radiant Systems P1210 Integrated Magnetic-Stripe-Reader (MSR) using a keyboard interface.� You must download and install radiant_p1210_msr_v345.zip from the Radiant Systems FTP site in order to configure the MSR for use with the Aloha application software.

Once you have installed the MSR configuration utility, perform the following:

-          Select Start/Programs/S64 Decoder/S64 Decoder to open the configuration utility.�

-          Select Magnic_Reader/Communication to open the communication settings.

-          Select the Output Characters tab, and set Select Terminator to CR.

-          Select the Magnetic Reader tab, and set Separator Character to NUL.

-          Select Magnic_Reader/Interface to open the interface settings.

-          Select the Interface tab, and set Interface to Keyboard Mode.

-          Select Magnic_Reader/Transmit.

-          Set the Interface to Keyboard, and select 'Download to Decoder' in order to download the new settings to the MSR.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3329 1210 rads

Configuring the Radiant P1210 Integrated Customer Display

Configuring the Radiant P1210 Integrated Customer Display

============================================================================

AKBID3330

Created: 2 March 2004

Updated: 2 March 2004

Reviewed: 2 March 2004

Microsoft^� Windows^� Versions: Windows XP

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.217 � 5.3.x

============================================================================

The ALOHA^� application software supports the Radiant P1210 Integrated Customer Display using Mintronix emulation.�� Configure the customer display as a Mintronix 2x20 Line Display in the Aloha application software, and configure the customer display communications settings for 9600 baud, no parity, 8 data bits, 1 stop bit, and Epson ESC/POS emulation.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3330 1210 rads

Configuring the Radiant Systems P400 MSR for Aloha

Configuring the Radiant Systems P400 MSR for Aloha

============================================================================

AKBID3331

Created: 5 March 2004

Updated: 5 March 2004

Reviewed: 5 March 2004

Microsoft Windows Versions: Windows XP

Aloha Products: QuickService, TableService

Aloha POS Versions: 5.2x � 5.3.x

============================================================================

In order for the Magnetic-Stripe-Reader (MSR) on the Radiant Systems P400 terminal to communicate with the ALOHA^� application software, you must configure it as a keyboard wedge using the X200 Hardware Settings applet in the Windows Control Panel.� If this applet does not exist, download and install Radiant_P400_3.3.03.000.zip from the Aloha FTP site.

Open the X200 Hardware Settings applet, select the General tab, and enable the 'Enable Radiant MSR Keyboard Wedge (start at boot)' option in the MSR Configuration section.� Restart the terminal.

If you are prompted for files when installing Radiant_P400_3.3.03.000.zip, point to the C:\Windows\System32\Drivers folder for .SYS files and C:\Windows\System32 for .DLL files.

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3331 400 card magcard rads

Unit Definition Error When Opening Gift Certificate Designer

Unit Definition Error When Opening Gift Certificate Designer

============================================================================

AKBID3332

Created: 8 March 2004

Updated: 8 March 2004

Reviewed: 8 March 2004

Microsoft^� Windows^� Versions: All

Aloha Products: BackOffice

Aloha POS Versions: 4.2x � 5.3.x

============================================================================

If you are using ALOHA^� Gift Certificate Manager and you receive the following error, then you must ensure that the unit number defined in Options/System Information is included in the units listed in Maintenance & Queries/Unit Maintenance:

'Your unit number is not defined in the unit table.� Use the units maintenance program to define your unit.� Please make the required file maintenance changed and try again.'

============================================================================

See also:

View this document in Rich-Text-Format (.rtf).

Please report any errors or omissions by email to [email protected].

Additional query words: 3332 backoffice

	SW1	SW2	SW3	SW4	SW5	SW6	SW7	SW8	SW9	SW10
Set 1	Off	On	On	On	On	On	On	On	On	On
Set 2	On	Off	Off	On	On	On	Off	On	-	-

	SW1	SW2	SW3	SW4	SW5	SW6	SW7	SW8
Set 1	On	Off	Off	Off	Off	Off	On	Off
Set 2	Off	Off	Off	Off	Off	Off	Off	Off
Set 3	Off	On	On	On	On	Off	Off	Off
Set 4	Off	On	Off	Off	-	-	-	-

	SW1	SW2	SW3	SW4	SW5	SW6	SW7	SW8
Set 1	Off	On	On	Off	On	On	Off	Off
Set 2	Off	On¹	Off	On	-	-	-	-

	SW1	SW2	SW3	SW4	SW5	SW6	SW7	SW8
Set 1	On	Off	On	Off¹	On	On	On	On
Set 2	On	On	On	Off	Off	On	Off	Off

	Blue	Orange	Black	Red	Green	Yellow	Brown	White
DB9	1	2	3	4	5	6	7	8
DB25	Unused	2	3	Unused	7	Unused	Unused	20

Pin #	Term 1	Hub
1	White/Orange	White/Orange
2	Orange	Orange
3	White/Green	White/Green
4	Blue	Blue
5	White/Blue	White/Blue
6	Green	Green
7	White/Brown	White/Brown
8	Brown	Brown

Pin #	Term 1	Term 2
1	White/Orange	White/Green
2	Orange	Green
3	White/Green	White/Orange
4	Blue	Blue
5	White/Blue	White/Blue
6	Green	Orange
7	White/Brown	White/Brown
8	Brown	Brown

Pin	Function
1	Carrier Detect (CD)
2	Receive Data (RXD)
3	Transmit Data (TXD)
4	Data Terminal Ready (DTR)
5	Signal Ground (GND)
6	Data Set Ready (DSR)
7	Request To Send (RTS)
8	Clear To Send (CTS)
9	Ring Indicator (RI)

RJ45 Wire	Blue	Orange	Black	Red	Green	Yellow	Brown	White
DB9 Pin	1	2	3	4	5	6	7	8

Desktop Name	Target	Start in	Notes
My Computer	N/A	N/A	Windows default
Network Neighborhood	N/A	N/A	Windows default
Recycle Bin	N/A	N/A	Windows default
Explorer	EXPLORER.EXE	default
Command Prompt	COMMAND.COM	C:\ALOHA	Adjust the 'Start in' setting to reflect the Aloha folder.
Aloha POS	C:\ALOHA\IBER.BAT	default	Use only if this computer is a server/terminal.� Adjust the 'Target' setting to reflect the Aloha folder.
Aloha Manager	C:\ALOHA\BIN\ALOHAMGR.EXE	default	Adjust the 'Target' setting to reflect the Aloha folder.
Aloha Credit Cards	C:\ALOHA\BIN\EDC.EXE	default	If used, adjust the 'Target' setting to reflect the Aloha folder.
Aloha Labor Scheduler	C:\ALOHA\BACKOFFICE\SCHEDULE\ESP.EXE	default	Use if Labor Scheduler is installed.� Adjust the 'Target' setting to reflect the BackOffice folder.
Symantec^� pcANYWHERE^�	MODEM.BHF in pcANYWHERE's DATA folder.	Default	Use only if pcANYWHERE is installed.

Application	Variables
ALOHAMGR.EXE	ALOHAMANAGEREXITONLOGOUT, ALOHAMGRPAGE, ALOHAPEXRES, ALOHAPEYRES, DATA, IBERDIR, NOMUTEX, RECORDDUPDBFRECORDS, REMOTE, SQLMODE
ALOHASPY.EXE	CTLPROCESS, DEBUG, IBERDIR, MAXDEBOUTDAYS, MAXDEBOUTSIZE, NONET, REGSERVER, SERVICE, UNREGSERVER
CESSVR.EXE	REGSERVER, SERVICE, UNREGSERVER
CTL.EXE	CRYSTAL, DEBUG, DEBUGCOPYTOSTORE, DEBUGCRWREPORTPARMS, DEBUGGRINDMANAGER, DEBUGGRINDSTORE, DEBUGGRINDTHREAD, DELETEVID, EXIT, IBERDIR, MULTIDEBUG, NOMUTEX, NONET, NOROBUST, REMOTE, ROBUST, SERVER, SQLMODE, TERMSTR
CTLSVR.EXE	ACCOUNTNAME, CLUBIMPORTFILE, DEBUG, DEBUGGRINDMANAGER, IBERDIR, MAXDEBOUTDAYS, MAXDEBOUTSIZE, MULTIDEBUG, NOMUTEX, NONET, NOROBUST, PASSWORD, REGSERVER, REMOTE, ROBUST, SERVER, SERVICE, SNAME, SPWD, SQLMODE, TERMSTR, UNREGSERVER
DBFDIFF.EXE	HKEY
DBUP2.EXE	ASSIGNSECURITYLEVEL, ATTENDED, CDX, CDXCHECK, CENTRALSITE, CONFIGONLY, CREATEDB, CREATEDBF, DBFINPUT, DBFONLY, DBFOUTPUT, DBONLY, DEBUG, ENTERPRISE, FORCESECURITY, FORCEUPGRADE, IBERDIR, NODBFCOPY, VERBOSE
DBUP3.EXE	ALLTABLES, ASSIGNSECURITYLEVEL, ATTENDED, CDX, CDXCHECK, CENTRALSITE, CONFIGONLY, CREATEDB, CREATEDBF, DBFINPUT, DBFONLY, DBFOUTPUT, DBONLY, DEBUG, ENTERPRISE, FORCESECURITY, FORCEUPGRADE, IBERDIR, NODBFCOPY, VERBOSE
DRSQL.EXE	IBERDIR
EDC.EXE	EDCSVR, IBERDIR, REPORTMODE, SECSVR, SECSVRPATH
EDCSVR.EXE	ACCOUNTNAME, DATADIR, DEBUGEXT, DEBUGSCAN, EDCDIR, EDCPATH, IBERDIR, IBERROOT, MULTIPLEMERCHANTIDS, NOMUTEX, PASSWORD, PMSDIR, PMSPATH, REGSERVER, S, SCANRESTRICT, SERVICE, SNAME, SPWD, TERMSTR, UNREGSERVER
EDOLDTM.EXE	IBERDIR, N, P, SQLMODE
ESP.EXE	ADDEMP, DATA, DELEMP, EDITEMP, IBERDIR
FASTECH.DLL	BACKOFFICEDIR, IBERDIR
GRIND.EXE	BALANCE, CLUBIMPORT, DATA, DATE, DEBUG, DEBUGCONVERTLOG, DEBUGCONVERTTRANSLOG, DEBUGMERGETRANSLOGS, DEBUGSQLBUILD, FORCECONVERTLOG, HOUSE, IBERDIR, INTERVAL, MERGETRANSLOGS, NODELETELOG, NOMUTEX, NOWINDOW, PAYCHEX, REGRIND, ROBUST, SQLMODE, STOREDIR, STORENUM, TIMING, USESLEEPING
GRINDQ.EXE	BALANCE, CLUBIMPORT, DATA, DATE, DEBUG, DEBUGCONVERTLOG, DEBUGMERGETRANSLOGS, DEBUGSQLBUILD, FORCECONVERTLOG,� HOUSE, IBERDIR, INTERVAL, MERGETRANSLOGS, NODELETELOG, NOMUTEX, NOWINDOW, PAYCHEX, REGRIND, ROBUST, SQLMODE, STOREDIR, STORENUM, TIMING, USESLEEPING
IBER.EXE	ALOHABIGFONTNAME, ALOHABIGFONTSIZE, ALOHAHUGEFONTNAME, ALOHAHUGEFONTSIZE, ALOHALEFT, ALOHAMEDIUMFONTNAME, ALOHAMEDIUMFONTSIZE, ALOHASMALLFONTNAME, ALOHASMALLFONTSIZE, ALOHASYSTEMFONTNAME, ALOHASYSTEMFONTSIZE, ALOHATINYFONTNAME, ALOHATINYFONTSIZE, ALOHATOP, ALOHAXRES, ALOHAYRES, AUTOCREATE, AUTOEXIT, AUTOUPGRADE, CALIBRATE, CONTRAST, DATA, DEBUG, DEBUG_COM, DEBUG_DISPLAY_BOARD, DELETEVID, DEBUGMSR, DEBUGSCALES, DEBUGTOUCH, DEV, DOUBLECLICK, EDCPATH, EGI, IBERDIR, IBERROOT, IBM4695MSR, LIQUORPLUDIGITS, LOCALDIR, LOCALREAD, MASTERCAPABLE, MASTERFILEDEBUG, MASTERFILEFREQ, MMSHEME, MULTILIQUORTAPTERM, MULTISERVER, NCR_MSR_FIX, NOFATALMSGBOX, NOROBUST, NUMTERMS, PROHOSTDIR, REBOOTNT, REGSERVER, ROBUST, SERVER, SERVERCAPABLE, STOPLOGO, STOREID, SUPPRESSTIPLINE, TERM, TERMSTR, UNREGSERVER, USEFULLMEMBERMAGCARD, USEONLY5DIGITS
IBERQS.EXE	ALOHABIGFONTNAME, ALOHABIGFONTSIZE, ALOHAHUGEFONTNAME, ALOHAHUGEFONTSIZE, ALOHALEFT, ALOHAMEDIUMFONTNAME, ALOHAMEDIUMFONTSIZE, ALOHASMALLFONTNAME, ALOHASMALLFONTSIZE, ALOHASYSTEMFONTNAME, ALOHASYSTEMFONTSIZE, ALOHATINYFONTNAME, ALOHATINYFONTSIZE, ALOHATOP, ALOHAXRES, ALOHAYRES, AUTOCREATE, AUTOEXIT, AUTOUPGRADE, CALIBRATE, CONTRAST, DATA, DATE, DEBUG, DEBUG_COM, DEBUG_DISPLAY_BOARD, DEBUGMSR, DEBUGSCALES, DEBUGTOUCH, DELETEVID, DEV, DOUBLECLICK, EDCPATH, EGI, IBERDIR, IBERROOT, IBM4695MSR, LIQUORPLUDIGITS, LOCALDIR, LOCALREAD, MASTERCAPABLE, MMSCHEME, MULTILIQUORTAPTERM, MULTISERVER, NCR_MSR_FIX, NOFATALMSGBOX, NONET, NOTIPS, NUMTERMS, REBOOTNT, ROBUST, SERVER, SERVERCAPABLE, STOPLOGO, STOREID, SUPPRESSTIPLINE, TERM, TERMSTR, VERIFONEONIBMPORT
LABSCHED.EXE	DATA, IBERDIR
MNT.EXE	DATA, DATE, IBERDIR, SQLMODE
PAYRECON.EXE	DATADIR, IBERDIR
REPRINT.EXE	ALL, ALTALOHAINI, CKO, DATA, DATE, DEBUG, DEBUGCONVERTLOG, IBERDIR, RPTAUDIT, RPTXFERS, SQLMODE, STORENUM
RPT.EXE	CTLREMOTE, DATE, IBERDIR, NODEPOSIT, NUM, PRD, R, SQLMODE, TYPE
TEAMSERV.EXE	IBERDIR, NOMUTEX
USERTOOL.DLL	DATA, DATE, IBERDIR
VIDEO.EXE	AUTOEXIT, DATA, DATE, NONET, NOROBUST, ROBUST, SERVER, VIDEO, VIDEOHEIGHT, VIDEOWIDTH, VIDEOX, VIDEOY
VIDEOMX.DLL	DEBUGIBM, DEBUGPV, DEBUGQSR, DEBUGSV, IBERDIR, IBMBAUD, IBMMODE, IBMPORT, IBMVIDEOS, PVPORT, QSRBAUD, QSRMODE, QSRPORT, QSRVIDEO, QSRVIDEOS, SVBAUD, SVIDEOS, SVMODE, SVPORT

Variable	ACCOUNTNAME
Applications	CTLSVR.EXE, EDCSVR.EXE
Description	Specifies the user name with which the server will log in as if you are using 5.230 or higher with the Windows NT, Windows 2000 or Windows XP operating systems.� Used in conjunction with the PASSWORD environment variable.� Refer to document AKBID1019.
System Variable Example	N/A
Command Line Example	CTLSVR.EXE /SERVICE /ACCOUNTNAME .\<user name>

Variable	ADDEMP
Applications	ESP.EXE
Description	Adds an employee to the schedule.
System Variable Example	N/A
Command Line Example	ESP.EXE /ADDEMP <employee ID> <employee first name> <employee last name>

Variable	ALLTABLES
Applications	DBUP3.EXE
Description	Instructs DBUP.EXE to update all of the RDB tables, not just tables that have changed.� Refer to document AKBID1067 for more information.
System Variable Example	N/A
Command Line Example	DBUP3.EXE /ALLTABLES

Variable	ALOHABIGFONTNAME
Applications	IBER.EXE, IBERQS.EXE
Description	Defines the 'Big' font for use in the FOH.� Refer to document AKBID1097.
System Variable Example	SET ALOHABIGFONTNAME=<font name>
Command Line Example	N/A

Variable	ALOHABIGFONTSIZE
Applications	IBER.EXE, IBERQS.EXE
Description	Defines the 'Big' font size to use in the FOH.� Refer to document AKBID1097.
System Variable Example	SET ALOHABIGFONTSIZE=<size, e.g.� 10>
Command Line Example	N/A

Variable	ALOHAHUGEFONTNAME
Applications	IBER.EXE, IBERQS.EXE
Description	Defines the 'Huge' font for use in the FOH.� Refer to document AKBID1097.
System Variable Example	SET ALOHAHUGEFONTNAME=<font name>
Command Line Example	N/A

Variable	ALOHAHUGEFONTSIZE
Applications	IBER.EXE, IBERQS.EXE
Description	Defines the 'Huge' font size to use in the FOH.� Refer to document AKBID1097.
System Variable Example	SET ALOHAHUGEFONTSIZE=<size, e.g.� 10>
Command Line Example	N/A

Variable	ALOHALEFT
Applications	IBER.EXE, IBERQS.EXE
Description	Specifies the left coordinate for the FOH (in pixels).
System Variable Example	N/A
Command Line Example	IBERQS.EXE /ALOHALEFT <pixel number>

Variable	ALOHAMANAGEREXITONLOGOUT
Applications	ALOHAMGR.EXE
Description	Forces Aloha Manager to exit upon logout rather than just logging the user out.
System Variable Example	SET ALOHAMANAGEREXITONLOGOUT=TRUE
Command Line Example	N/A

All Documents

TableService

QuickService

EDC

BackOffice

Answer Wizards

Configuring the CALIBRATE Variable on Aloha Terminals

Summary

Information

Dynapro with Windows 9x

EloTouch with Windows 9x

MicroTouch

Radiant Systems P400 and P1550

Radiant Systems P1210

Extended Information

Caveats

Aloha Receipt and Kitchen Printer Settings and Pin-outs

Summary

Information

LPT Port Settings

FIFO Buffers

Printer Buffers

OPOS Printers

CBM 354x Serial

CBM CBM-710/720/730, and CBM-750 Serial (40 column version)

Serial DB9 to CBM-7xx DB25

Serial DB25 to CBM-7xx DB25

CBM CBM-1000 Serial

CBM CBM-1000 Type II Serial

CBM iDP3240 Serial

Eltron/Zebra Technologies LP2742

Epson TM-H6000 Serial

Epson TM-T80 Serial

Epson TM-T85 Serial

Epson TM-T88 Parallel

Epson TM-T88 Serial

Epson TM-U200 Serial

Epson TM-U200 Parallel

Epson TM-U220 Serial

Epson TM-295 Serial

Epson TM-U300 Serial

IBM SureMark 4610 Serial

Ithaca (TransAct) iTherm 280 Serial

Ithaca (TransAct) Model 82 Plus Serial

Ithaca (TransAct) Model 82 Plus Parallel

Ithaca (TransAct) Series 1000 Serial

Ithaca (TransAct) POSjet 1000 Serial

Nanoptix C21-BNSAB/C21-BNSBB Spill Proof Thermal Printer

NCR 7193 Serial

Set 1

NCR 7194 Serial

Olivetti OST12 Serial

Partner Tech Corp RP-200

Samsung SRP-270

Samsung SRP-270C

Samsung SRP-350

Samsung SRP-500C Serial and Parallel

Star 8340 Serial

Set 1

Star 300/312 Serial

Set 1

Star 300/312 Parallel

Set 1

Star SP512MD

Set 1

Star SP2000 Serial

Star TSP200 Serial

Set 1

Set 2

Star TSP400 Serial

Set 1

Pin-outs for Standard Printer Cables

Serial DB9 to Printer DB25

Serial DB9 to Printer DB9

Serial DB25 to Printer DB25

Serial DB25 to Printer DB9

RJ45 to RS232 Adapter Pin-outs for Standard Printer Cables

Serial DB9 to Printer DB25

Serial DB9 to Printer DB9

Serial DB25 to Printer DB25

Variable	ALOHAMEDIUMFONTNAME
Applications	IBER.EXE, IBERQS.EXE
Description	Defines the 'Medium' font for use in the FOH.� Refer to document AKBID1097.
System Variable Example	SET ALOHAMEDIUMFONTNAME=<font name>
Command Line Example	N/A

Variable	ALOHAMEDIUMFONTSIZE
Applications	IBER.EXE, IBERQS.EXE
Description	Defines the 'Medium' font size to use in the FOH.� Refer to document AKBID1097.
System Variable Example	SET ALOHAMEDIUMFONTSIZE=<size, e.g.� 10>
Command Line Example	N/A

Variable	ALOHAMGRPAGE
Applications	ALOHAMGR.EXE
Description	Sets the initial page for the Aloha Manager display.� The initial page usually resides on the local hard drive.
System Variable Example	SET ALOHAMGRPAGE=<web address or local HTML file>
Command Line Example	N/A

Variable	ALOHAPEXRES
Applications	ALOHAMGR.EXE
Description	Used with ALOHAPEYRES, defines the screen width in a custom resolution size for Panel Editor.� The custom resolution is displayed as [custom] in Panel Editor's list of resolutions.� Refer to document AKBID3228 for more information.
System Variable Example	SET ALOHAPEXRES=<size, e.g.� 240>
Command Line Example	N/A

Variable	ALOHAPEYRES
Applications	ALOHAMGR.EXE
Description	Used with ALOHAPEXRES, defines the screen height in a custom resolution size for Panel Editor.� The custom resolution is displayed as [custom] in Panel Editor's list of resolutions.� Refer to document AKBID3228 for more information.
System Variable Example	SET ALOHAPEYRES=<size, e.g.� 320>
Command Line Example	N/A

Variable	ALOHASMALLFONTNAME
Applications	IBER.EXE, IBERQS.EXE
Description	Defines the 'Small' font for use in the FOH.� Refer to document AKBID1097.
System Variable Example	SET ALOHASMALLFONTNAME=<font name>
Command Line Example	N/A

Variable	ALOHASMALLFONTSIZE
Applications	IBER.EXE, IBERQS.EXE
Description	Defines the 'Small' font size to use in the FOH.� Refer to document AKBID1097.
System Variable Example	SET ALOHASMALLFONTSIZE=<size, e.g.� 10>
Command Line Example	N/A

Variable	ALOHASYSTEMFONTNAME
Applications	IBER.EXE, IBERQS.EXE
Description	Defines the 'System' font for use in the FOH.� Refer to document AKBID1097.
System Variable Example	SET ALOHASYSTEMFONTNAME=<font name>
Command Line Example	N/A

Variable	ALOHASYSTEMFONTSIZE
Applications	IBER.EXE, IBERQS.EXE
Description	Defines the 'System' font size to use in the FOH.� Refer to document AKBID1097.
System Variable Example	SET ALOHASYSTEMFONTSIZE=<size, e.g.� 10>
Command Line Example	N/A

Variable	ALOHATINYFONTNAME
Applications	IBER.EXE, IBERQS.EXE
Description	Defines the 'Tiny' font for use in the FOH.� Refer to document AKBID1097.
System Variable Example	SET ALOHATINYFONTNAME=<font name>
Command Line Example	N/A