Latest News

Performance Improvements at Point Of Sale - A Guide to Getting the most out of your 4690 System.

It is clear that many of the IBM 4690 POS applications could use an overhaul. But who has the time? And where would one start?

Learn more.

How to install Flexview on an NCR 7858-4001 Terminal
Documentation - Flexview

Steps in Building an NCR XPe terminal with Flexview

Note that we are setting up an NCR 7858-4001 equipped with both a digital display (Dynakey) and a regular monitor.

  1. Assure that the machine is setup with the proper machine defaults.  All serial ports you intend to use should be enabled, the machine should be set to boot from the hard drive, and the parallel port should be enabled and set to unidirectional mode (if you intend to attach a 2x20 display to the parallel port).
  2. Ghost the XPe image from NCR to a hard drive (it may come pre-installed) and install the hard drive, if necessary.
  3. You need to install the DLC protocol to work with your network adapter.  DLC was not included as a protocol for XP, but it is available on the Microsoft web site. Search the Microsoft web site for it, download it, and make sure it is installed properly.
  4. If the Intel Extreme Graphics 2 drivers are not already installed, go to the NCR web site, download their Intel Extreme Graphics 2 driver.  Look in the XP, not XPe location for this driver.  Begin looking at:  http://www.ncr.com/support/support_drivers_patches.asp?class=External\display
  5. From the NCR web site, download the Retail Software for Windows software. It is located at: http://www.ncr.com/support/support_drivers_patches.asp?class=External\display
  6. Install the “Retail Software for Windows” program, selecting default values, controls, and objects for devices you expect to be using.  Be sure that you specify the correct NCR terminal you are installing this on – do not choose PC.
  7. Using the FitClient option for the Retail Software for Windows program, configure the attached devices to be controlled by the OPOS controls.  The video screens, dynakey, printer, and cash drawer are NOT controlled by OPOS and should not be set up.  Configure (as required) NCRScanner1, NCRScale1, Keylock1, LineDisplay1, and LineDisplay2 to be controlled by OPOS.  They must be properly configured and tested with FitClient before you proceed. Diagnostic testing using FitClient offers proof that OPOS is in proper control of any given peripheral.
  8. Install the OPOS Common Controls package from Monroe Consulting Services (http://monroecs.com/oposccos.htm).  You need only to install the common controls.  These controls will be used by Flexview to access NCR objects.
  9. Install the Intel Extreme Graphics 2 drivers and, using the Intel Extreme Icon in the Control Panel, set the machine up for the Extended Desktop.  The digital display (dynakey) attached to the DVI port should be primary; the VGA display (monitor) should be secondary. Set both at 800 x 600 resolution.  Uncheck the “Enable Twin Configuration” checkbox.  Do not choose the Notebook for anything.
  10. Install the proper version of Terminal Services for Windows.  Choose defaults except you should “unclick” the option: “launch terminal services at startup” for testing purposes.
  11. Copy the following QVS-provided files to the c:\tsnt\bin directory: qvsrpam.dll,  tlrdvusb.dll, and flexview.exe.
  12. Register the qvsrpam.dll file:  With “tsnt\bin” as the default path,  type:
    • regsvr32 qvsrpam.dll
  13. Copy the file, “qcdifile.ipl”, provided to you by QVS into the c:\tsnt directory on the terminal hard drive
  14. Install Sun Java version 1.1.8 onto the terminal.
  15. Copy the following configuration files provided to you by QVS into the c:\adx_udt1 directory on the master controller:
    • qcdifile.mst
    • keymap.000
    • dynakey.000
    • graphics files, etc???
  16. Distribute the above files to assure they also are updated on the alternate master controller (if this applies to your setup)
  17. Set up the terminal to boot directly to the main terminal services screen upon bootup.
  18. Make sure that the terminal number you expect to attach to the controller has been defined on the controller.  It must be defined as if a real 4690 terminal were to be attached.  The application to run on your terminal will be read from this configuration file on the controller, so that, at least, must be correct.
  19. When the terminal properly boots up the first time and is connected to the master store controller, you should see the following prompt on the 2x20 screen on the dynakey display: Z001
  20. Turn the key on the dynakey to the “Ex” position.  Using the numeric keys, type in 1xxx, S2,    where xxx is the 3 digit representation of the terminal number you intend to use for this terminal.  S2 should appear on the dynakey screen.
  21. In response, if everything is configured and connected properly, the terminal should restart and load the application from the controller.
  22. If everything is working as expected and you want to ghost this image, complete the following steps:
    • edit “c:\tsnt\qcdifile.ipl” to remove references to TermNum and StoreNum, if used
    • Delete the file, “c:\tsnt\batprmem.dat”
    • Delete the file, “c:\tsnt\qcdifile.log”
    • Delete the files contained in “c:\tsnt\log” directory
    • Delete the files contained in the “c:\tsnt\logq” directory
    • Remove any local network links which are attempted at startup.
  23. Disconnect the keyboard and mouse, since, from this point, the terminal should behave like a standard POS terminal using the Dynakey as input and the two displays as visual outputs.
 
© 2012 QVS Software, Inc.