Potential Operational Differences; Deployment Considerations; Local Update - NCR RealPOS 70XRT User Manual

10-4 Chapter 10: Wedge to USB MSR Software Migration

Potential Operational Differences

While the UnifiedPOS (UPOS) API is designed to hide differences between devices it
is possible that you may see some differences between the Wedge MSR and the USB
MSR in error reporting. Setting the
MSR_ERT_TRACK allows the delivery of good track data when one or more tracks have
errors. See the UnifiedPOS Retail Peripheral Architecture specification for more details
If you use the UnifiedPOS (UPOS) AutoDisable feature by setting this property to
TRUE, it is strongly recommend that you upgrade your RPSW to 3.0.1.0. The MSR can
get into a locked condition if certain swiping errors occur.

Deployment Considerations

When deploying this software change you may need to perform the following,
depending on the current version of RSPW on your terminals.
1. Modified installation to add the NCR5932 feature.
2. Upgrade to the latest version of RPSW; 3.0.1.0.
3. Replace the current OPOS Wedge MSR Profile with a profile configured for USB

Local Update

If you have a small number of terminals and your application permits access to the
Windows Desktop you may simply want to modify each terminal by running
Add/Remove Programs under the Control Panel.
If the RPSW .MSI file was deleted after the initial installation you will need to copy or
run the current version of RPSW from a USB Drive. You can then run the FitClient LE
or RSM LE, depending on your version of RPSW, delete your current Wedge MSR
profile, and create a new profile with the same name. Choose the Programmatic ID of
NCRFitClient.MSR and MSR Interface of USB.
MSR.
UPOS API ErrorReportingType property to