Thank you for selecting Motorola as your scanner solution tool provider. The "OPOS Driver for Symbol Scanners v3.31" provides the tools necessary for scanning barcodes.
OPOS (OLE for Retail POS) is a standard programming interface definition for POS peripheral devices. It provides hardware independence for the POS system developers and integrators by defining for the POS application a common interface for each type of POS peripheral. An additional benefit of using OPOS is that it allows the retail application to have a finer control over the scanner. The OPOS standard was initiated by four major retail industry vendors: Epson, ICL Retail Systems, Microsoft and NCR and is used and supported by many vendors, integrators and retailers worldwide.
For the latest software updates, go to the Support Central web site and select Software Downloads.
Thank you,
The Motorola Enterprise Mobility Software Development Team
Version 3.0.31
1. Maintenance release.
Version 3.0.27
- Defect Fixes-defect as :Populating ScanDataType when Decode Data property is set to value “False”. Fixed as :When decode data is false ScanDataType is not populated.
Version 3.0.26
- Defect Fixes-defect as :End user is using the STI85-0200 with OPOS version 3.24. He is able to get the correct date into the sample app, but the scan code type is reporting what we believe is the incorrect data. A bookland EAN code is being reported as a 201 which is a PDF417. Set to return as Unknown type for the particular bar code type
Version 3.0.24
- Defect Fixes-When check health method is called, it return wrong result code. It is corrected.
- Defect fixes-Calling the method, ClaimDevice(OPOS_FOREVER) (OPOS_FOREVER=-1) has given the error code OPOS_E_ILLEGAL and did not proceed with the device as it has returned a error code. Now ClaimDevice Method accept -1 as a correct input parameter value.
Version 3.0.23
1. Defect Fixes-Populating ScanDataType when Decode Data property is set to value “False”.
Corrected as -ScanDataType is populated when Decode Data is true
2. Defect fixes-addressed wrong memory access problem.
Version 3.0.22
1. Revert back to previous 0x60->0x0D replacement. There was data replacement in Version 3.19.
It was reverted back in this version. So in this version, there is no data replacement.
2. Make sure that all components represent the same version.
Version 3.0.21
1. Data event improvement.
Incorporated event firing thread.
Version 3.0.19
1.Registry change
1.1 Registry change was done-.
Defect:"STI_SCANNER" is hard coded in registry.
Fixed as: Put any name in registry and specify that name to call it .m_CtScanner.Open(MyScanner)
1.2. Connection Mode is identified from the value of key "Protocol".
FOR USB mode, Protocol is, "IBMHID". FOR RS232, Protocol is "RTS"
2 Data replacement: 0x60->0x0D
1.1 0x60 are replaced by 0x0D in scan data
1.2 In order to make it effect, user has to call/Set SetDecodeData(TRUE)
If the default install location is not changed, the components are installed in the following folders:
Component
Location
Visual C++ sample application
\Program Files\Symbol OPOS Driver\TestScan.exe
Visual Basic sample application
\Program Files\Symbol OPOS Driver\VBDemo.exe
Visual Basic Demonstration Program
\Program Files\Symbol OPOS Driver\VBDemon\*.*
Symbol control object-OCX
\WINDOWS\system32\scanner.ocx
Service Object-DLL
\WINDOWS\system32\stiopos.dll
Please uninstall any previous versions of this program before installing version 3.27.
This driver is tested on the following operating system:
- Microsoft Windows XP Operating System
Last
revised: 08 13, 2007