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 IBM 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.