FAQ

Reports Guide

Troubleshooting

Wireless
Bump Bar Programming

Component Pricing

Remote Database Maintenance
(requires PowerPoint)


 

Frequently Asked Questions

Q: On bootup the first checklist has a RED X in Discount. Can I fix this?
A: Yes, Make a change to the Discount information in System Databuilding and save the file. Reboot and the X should now be a Checkmark.

Q: On Bootup the first Checklist shows a Red X in Global Options. Is this a problem? Can it be corrected?
A: This is not a problem and the system will run properly. To correct the issue you will need to call tech support.

Q: My System Crashes after TENDERING the first order. How can I stop this?
A: The system may have had a virus. The files may have been cleaned with the Junkie- virus killer. In doing so if appears to render the files useless on a Slave terminal.

Q: Tech Support told me to boot to the C: prompt. How do I do this?
A: There are several ways. One is, Using a keyboard, reboot the terminal and hold down the SHIFT button. The screen will prompt for Time and Date. Press ENTER twice on the keyboard. You should be at a C:\ prompt.

Q: When running reports, server shows "file error 4" How can I fix this?
A: This is a bug in version 5.07. Later versions corrected this  problem. The bug leaves previous reports open in the buffer. To resolve this , turn the Server off then on. If this doesn't correct it perform a "ramdisk 0" on Server.

Q: My system does not report voids. What do I do?
A: Perform a "ramdisk 0" on Server.

Q: How do I perform a "Ramdisk O" command?
A: Plug in the keyboard to the register. Boot it to DOS. Type A: then press enter. Type ramdisk 0 then press enter. The next screen may ask if you are sure, Press enter to continue. The system should format the RamDisk at 512K. If the number is other than 512K you will need to call Tech Support. Once the format is complete reboot the terminal.

Q: How do I program a RF Bump Bar?
A: Early Bump Bars were equipped with an optical sensor. Most Bump Bars today can be programmed by keypad input. Refer to the following link for programming instructions. How To Program The New “Extended Range” Bumpbar

Q. My register screens won't stay calibrated. How can I fix this?
Version 4 & 5: A. If the calibration from manager functions does not correct a calibration issue then you can try another form of calibration.
Hook up the keyboard to the problem register and reboot it. As soon as you hear the beep or beeps, hold down the Ctrl button and press the Pause/Break button on the keyboard. Release both, then press Ctrl and press Pause/Break again, then release. The register should display "Terminate Batch Job Y/N". Press "Y" for yes. At the "A:" prompt type UDMTEST. One of the options is to calibrate the screen. If you can not get to calibrate screen by touching the screen, press the F9 button on the keyboard. Look at the screen and press the "X" in the corner, the "X" will now appear in the opposite diagonal corner. Press that one as well. I usually try it again for good measure. When finished reboot the register and unplug the keyboard. The terminal should now be calibrated.

Version 6 - 8: A. If the calibration from manager functions does not correct a calibration issue then you can try another form of calibration.
Hook up the keyboard to the problem register and reboot it. As soon as you hear the beep or beeps, hold down the Ctrl button and press the "C" button on the keyboard. The register may display "Terminate Batch Job Y/N" or just a "C:>" prompt. Press "Y" for yes.
Type cd\utils, then enter. Then type "UDMCAL" then enter. The next screen has several options. Touch the Calibrate button and then press each of the 16 calibration buttons. 

When finished restart the register - CTL-ALT-DELETE. Unplug the keyboard. The terminal should now be calibrated.

 

Back to Home Page
Back to Home Page