QConnect FAQs

How do I configure graphics files to run under QConnect CE?

The URL/URL2 keywords in the dynakey file pass the URL to Internet Explorer running in one of the two windows on our dialog. The files passed to IE can be bitmaps, gif files, html files, etc. Our samples include html files that load bitmap and gif files. You can essentially show any image in the window that you can show in IE.

There are some limits as size and such that are mentioned below.

Add the URL="...." and/or URL2="...." on a STATE or GROUP line in they dynakey file and that URL will be displayed. Any file that the URL points to or references must be in the "webCacheDir" on your controller AND be included in the webfiles.lst file in the "webCacheDir".

Here are a couple of tibits if you want to make changes or add files etc.:

  1. Keep the number of files in the webfiles.lst to a minimum as they use memory in the terminal. For example, if you want to replace the bitmap of the NCR flag on Wall Street with an ACME graphic, add your file to the directory, add it to the list and remove the ncrhq.bmp from the list. You do not have to remove the file from the directory - only the files in the webfiles.lst will be transferred to the terminal.
  2. The sizes of the browser windows are:
    Top browser - 632 width x 48 height
    Side browser - 244 width x 414

    Images bigger than these will cause scroll bars to be displayed in the browser windows.

  3. The _xxx.htm files are used to turn off borders and such. (I do not claim to be an html expert!)
  4. The xxx.htm files handle background colors, sizing etc, and determine which graphic to display.
  5. Internet Explorer for CE only supports JScript - not VBScript.

What are the steps to install and configure QConnect CE?

Controller Configuration

Install the QVS DHCP server, QVS TFTP Server, and QVS Log Server (See the help file, How to set up a controller to load an NCR PXE terminal.html, for details). These programs load the terminal image and capture diagnostic information from the terminal.

Copy the terminal QConnectCE/Image to \adx_udt1 directory. The image consists of 2 files, qxxxxxx.sys (the boot loader) and qxxxxxx.bce (the binary CE image). Note: The xxxxxx varies depending on the type of terminal image being loaded.

Using the QCONNECT CE configuration program, QCCE_CFG, make appropriate changes to QCDIFILE.000 to match your machine configuration. You can refer to the file, qcdifile sample for QCONNECT CE.html, for details on some parameters you may need to modify via editor. Note that TCP/IP addresses required for the operation of the DHCP server (Step 1) must be added to the [binl] section of this file.

Copy your modified qcdifile.000 to \adx_udt1.

Copy the included graphics files to the directory you specify in QCDIFILE.000 using the keyword, webCacheDir=R::\xxxx_xxx. These graphics files are used to show store ads or customer messages on unused areas of the Customer Information Display. The format of these html files may need to be changed, depending on the format used to display QCONNECT-related information on the screen. Please refer to the document, How to configure graphics files to run under QCONNECTCE.htm for information on how to modify these files.

See sample dynakey.xxx file for an example of how to trigger the display of certain graphics files. Search for the keyword URL. URL is the side browser and URL2 is the top browser. See the sample file, QCDIFILE SAMPLE FOR QCONNECT CE.HTML, to see an example of how to set up your terminal to load the HTML files.

The IDs for terminals you intend to install must be configured under both "Terminal Configuration" and the "LAN definition" option under "System Configuration" on the master store controller. Since these procedures are designed to configure TGCS equipment, no information you specify is important except the 4690 application name you intend to run on the terminals you are installing and the terminal IDs themselves.

7452-4000 Terminal Configuration and Loading

Make sure the BIOS is upgraded to at least a 2.1.2.3 bios level. When that upgrade is complete, the BIOS settings will all be set to defaults, which is fine. If you have a hard drive installed in the machine, be sure to set up the BIOS to load using PXE, not the hard drive.

The video setting of PCI vs AGP seems to make no difference. The parallel port should be enabled. Generally, default settings work fine.

The DYNAKEY screen MUST be plugged into the motherboard port, NOT into a dynakey interface card. This is very important.

The terminal CMOS must be cleared prior to attempting to load this image. Use the diskette image sent to you by QVS designed to clear CMOS for either DOS or CE.

The terminal Wedge must be configured once. Using the diskette provided to you by QVS, boot up the terminal and the wedge interface will be automatically configured. This configuration sets hardware parameters for proper operation of a wedge-attached scanner and sets parameters to allow dynakey entries while the keylock is in the "L" position (preferred). Contact QVS personnel to obtain a downloadable image of this diskette for use from a remote location.

If the controller has been properly set up to load the terminals via TFTP and the terminal is set up to boot using the PXE protocol, the terminal, when powered up, should load an image from the controller. The image name loaded would be the default image specified in the [binl] section of QCDIFILE.000. While this image is being loaded, a "thermometer" should appear on the screen showing image loading progress. The load should complete in several seconds.

The terminal, following loading of the image, should show a blank screen for several seconds, flash, then a few seconds later, you should see a CE Operating system desktop, then a typical dynakey screen layout with progress messages appearing on the 2x20 area of the dynakey screen.

If the CMOS has been cleared, you will see the S1/S2 dynakeys outlined in RED and a Z001 shown on the 2x20 area of the screen. Enter 1xxx, S2 where xxx represents the terminal ID (this ID must be defined and activated on the controller and must have a valid terminal application associated with it).

The terminal should reboot and load the application. If, after reloading, the 2x20 screen area shows a U007 and stops there, the most likelly problem is you do not have a printer attached to the port where you have specified it to be in QCDIFILE.000. Application loading will not continue until your printer is properly attached to the configured port.

The application should load and will use keymap and dynakey definitions present in the normal KEYMAP.xxx and DYNAKEY.xxx files. If these files represent defaults used in every terminal in the store, xxx should be 000.

How do I dump a terminal to diagnose QConnect problems?

How to Dump a 7052 Diskless Terminal

  1. Place the terminal in a state for which a dump is desired.
  2. Power the terminal OFF
  3. Using a proper key, put the keyboard lock switch into the Ex position
  4. Power the terminal ON
  5. You will see a menu screen. Choose the following sequence:
  6. 4 - Diagnostics
    3 - Do not print
    9 - More tests
    6 - Memory Dump
    2 - Dump via ETHERNET
    2 - Base Memory Dump

  7. After the dump has completed, send the file, ADX_UDT1:TERMMEM.DMP, found on the Store Controller to QVS for analysis

How to Dump a 7450 Diskless Terminal

  1. Place the terminal in a state for which a dump is desired.
  2. Place the PCMCIA flash memory card into the tray on the lower left front of the machine and close the tray completely.
  3. Locate the dump switch on the back of the machine. It is behind a small hole on the right side just to the left of the keyboard connector.
  4. Using a paper clip or similar tool, push it into the hole far enough to depress the dump switch
  5. The register should begin beeping.
  6. At first the beeping will be regular beeps
  7. After a time, the beeps will become warbled.
  8. Once the warble tones begin, the 7450 should be turned off.
  9. Take out the PCMCIA card and send it to QVS.

How to Dump a 7452 Terminal with or without a Hard Drive

There are two methods which could be used. The first method is preferred. If the failure of the terminal is such that communication with the Store Controller is not possible, the second method should be used.

Method #1 (preferred)

  1. Place the terminal in a state for which a dump is desired.
  2. Go to the Store controller
  3. Hit the Alt-Sys Req key combination
  4. Choose option c: "Access the Store Controller Functions Screen"
  5. Choose option 1: "Terminal Functions"
  6. Choose option 8: "Dump Terminal Memory"
  7. After the dump is completed and the terminal has rebooted, copy the file: ADX_UDT1:TERMMEM.DMP or ADX_UDT1:TERM0nnn.DMP (where nnn is the terminal number) from the Store Controller to a diskette.
  8. Transmit the file to QVS for analysis.

Method #2 (Used only if Method #1 fails)

  1. Obtain a formatted TGCS 1.44 Meg diskette
  2. Place the terminal in a state for which a dump is desired
  3. Make sure no diskette is in the diskette drive
  4. Locate and press the dump switch:
  5. Open the lower access panel on the front of the terminal
  6. The dump switch is located just to the right of the 4 lights
  7. Obtain a pencil or other small device to use to press the recessed switch
  8. You will hear a musical tone followed by a long beep, then 2 short beeps
  9. As the long, 2 short beep cycle continues, place the diskette into the drive
  10. The disk drive light will glow as the terminal memory image is written to the diskette
  11. When the write completes, you will hear a long tone followed by a musical tone
  12. Remove the diskette and send it or a copy of its contents to QVS for analysis

How do I maintain QConnect DOS on a hard drive?

Sometimes, fixes need to be downloaded to a QCONNECT DOS terminal. If the customer is using a Hard Drive to boot QCONNECT, the emulator will look for an update file on the controller at each startup of QCONNECT. If it finds the file, ADX_UDT1:QMAINT.DAT, on the store controller, the following sequence takes place:

  1. The file will be downloaded to the terminal
  2. It is renamed to an executable
  3. The file is executed, causing the module that has been downloaded to be unzipped.
  4. The terminal reboots

To show how this process works, let's assume that a fix for the QCONNECT emulator is required. The updated emulator, 7452emu.exe, will be zipped up to a file of any name and converted to an executable of any name. The utilities to use to do this are PKZIP.EXE and ZIP2EXE.EXE, respectively.

The resulting xxxxx.exe file is then renamed to QMAINT.DAT and downloaded to the ADX_UDT1: directory. Once there, it will be detected by the QCONNECT emulator and downloaded, if it has not already done so. After it is downloaded, the terminal reboots.

How do I do a QConnect trace?

There are two major ways to do a trace. You can begin a trace at a particular point in a terminal operation or you can begin tracing from the moment QCONNECT begins execution. Both methods are described in this discussion. Case 2, described below is not available if the terminal you are attempting to trace does not use a CDIFILE.xxx configuration file. See Case 2 for details.

CASE 1: Tracing beginning at a point within the application transaction some time after the terminal has booted and is executing the application.

  1. At the keyboard, place the keylock switch in "Ex" position.
  2. Using a calculator, divide today's date by 17.
    Example: July 15, 1998 -> 071598/17 = 4211.647
  3. Ignoring the remainder, key in the whole number in the following sequence:
    S1, 00xxxx, S2 where xxxx is the whole number you calculated in the previous step
    Example:
    For the July 15th date, enter:
    S1,004211,S2
  4. If this number is correct, the screen gives no indication. If it is in error, an error message is displayed.
  5. Following an error-free entry, key the following sequence:
    S1,999,S2 (this initiates the trace function)
  6. You will be prompted for trace options. Always choose the following:
    basic, verbose, ioproc, serial, and log to file. In addition, trace any other IO devices you think may be involved in the specific error you are trying to capture.
  7. Turn the keylock back to the "R" position and attempt to duplicate the problem you are trying to capture.
  8. When the error condition has been captured, turn the keylock back to the "Ex" position and turn off tracing either by powering off the terminal or using the following key sequence:
    S1,999,S2 -> Then, enter "0" at each prompt.
  9. Turn the keylock back to the "R" position. Your terminal should now be operating normally and tracing should be disabled.
  10. Copy the file TRDMP.TRC from the root directory of the Store Controller and save for analysis.

CASE 2: Tracing from the moment the emulator begins execution.

  1. Go to the store controller and edit the file, ADX_UDT1:CDIFILE.xxx where xxx is the ID or number of the terminal you wish to trace or is "000" (the default CDIFILE)
  2. Modify the last line in the file which is labeled with the "tracing" tag. Use the comments in the file or instructions from QVS personnel to determine the options to use. Always use option "L" to cause a disk log file to be created on the controller.
  3. Boot the terminal. You will notice that it will be running slower and should show a blinking "tr" indicator on the screen.
  4. Run the application through the condition you want to trace.
  5. If possible, run an operation or two past the failure point you are tracing just to assure that the failure will be logged.
  6. Power down the terminal.
  7. Edit the CDIFILE you had modified and remove the trace options you had added. Note the "tracing" tag should show null data ("")
  8. Copy the file TRDMP.TRC from the root directory of the Store Controller and save for analysis.
  9. Reboot the terminal. Tracing should be disabled.

What system functions are supported by QConnect?

Function Name Function Number Supported by QCONNECT?
Display Wait Message 1 Yes
Display Offline Message 2 Yes
Display System Message 3 Yes
Change Keyboard Tone Volume * 6 Yes
Display Terminal Number 7 Yes
Display Date Format 50 Yes
Set Date on Offline Terminal 51 Yes
Set Time on Offline Terminal 52 Yes
Set Terminal Characteristics 71 Yes
Enable Storage Retention ** 72 Yes
Disable Storage Retention ** 73 Yes
Enter Test Mode*** 91 Yes
Enter Customer Setup Mode 92 No
Display Available Memory 96 Yes
Dump Terminal Memory 9898 Yes

* Some keyboards do not support changing tone volume.
** Some terminal models do not support Storage Retention. For these terminals, the function will appear to successfully execute.
*** Refer to the "TGCS 4680 Store System and 4683/4684 POS Terminal Problem Determination Guide" (SY27-0330) for details on running these tests
Note: The complete key sequence is: S1, Function Number, S2

How do I determine what level of QConnect is installed on a terminal?

To determine what level of QCONNECT is running in your terminal, go to the Store Controller used to load your terminal and look at the contents of the file, QCONFIG.xxx, where xxx is the terminal number. This file is located in the root directory.

For example, if you want to determine the QCONNECT level being run on terminal #004, do the following:

  1. Go to the Store Controller which loads Terminal 4 and enter Command Mode (option 7 on the System Main Menu)
  2. Type the following Command:
    type \qconfig.004
  3. Record the Date/Time Stamp information displayed on the screen