|
| |
1.11.001 -- December 4, 2007
This release supports all OPOS APIs from Release 1.01 through Release 1.11.
The 1.11 CCOs can be used with applications
built against previous CCO releases, beginning with the 1.5.1xx CCOs. No rebuild is needed.
For further details, see OPOS CCOs History.
1.12.901 Beta -- January 18, 2008
This release supports all OPOS APIs from Release 1.01 through Release 1.12.
The 1.12 CCOs can be used with applications
built against previous CCO releases, beginning with the 1.6 CCOs. No rebuild is needed.
The management of COM UUIDs is similar to the previous OPOS
releases:
- The CoClass, Library, and Event UUIDs are unchanged.
Should multiple installations of CCOs occur, then the last registered release
will be instantiated when an application creates a CCO. It is the
responsibility of the user to ensure that the registered CCOs are at least as
new as the newest version required by an application. For example, if
App A was built against release 1.8.001, App B was built against 1.9.002, and
App C was built against 1.11.001, then the user should install or register
1.11.001 last, since all three applications will run correctly with this
version.
- An additional Interface UUID has been added to those devices that have new methods and/or properties in this release.
In addition to new devices and APIs, several other changes are introduced in
this release:
- The CCOs are now built in Unicode mode only, for Windows 2000 and later.
- Windows 95/98/ME are no longer supported.
- Windows NT 4 is no longer supported.
- The CCOs are now built using Visual Studio 2005 (Service Pack 1), with
the standard ATL header files. Some preprocessor magic is used to work
around issues with HardTotal's Create method and LineDisplay's CreateWindow
method. (Previously, VC++ 6 (SP6) was used with modified ATL files.)
- COM Interface IDs for versions prior to those used in OPOS 1.6 are no
longer supported. Applications built against pre-1.6 CCOs that cached the
old IIDs (instead of using the default IID) will either need to continue to
use a previous CCO, or be rebuilt against these new ones.
- Some significant changes were made to the code:
- To conform to COM rules, previous release interfaces now include
only their properties and methods, instead of all properties and
methods. (Previously, each interface change effectively extended all
previous interfaces.)
- Variant variable handling has been reworked for safety and error
detection: NULL pointers and memory failures are detected and cause an
appropriate failure HRESULT to be returned, instead of assuming good
pointers and successful allocation.
- CCO initialization checks for critical failures and returns a
failure HRESULT, instead of assuming success.
- The library names have been changed to OposXxx_CCO, where "Xxx" is the
device name. These names will be retained in subsequent releases.
(Previously, the release number was included, which would cause development
environments that cache the name to fail when loading new CCOs.)
The author requests that those who evaluate these Beta CCOs consider the
following, and report issues or concerns to him:
- Operational deviations from previous releases.
- Source code issues and concerns, plus recommendations for improvement.
- If you test with Vista, please report any problems. The author has
limited access to Vista-based POS.
- These CCOs are noticeably larger than previous releases, despite
adjusting the available VS2005 compiler/linker options. (However, the debug
versions are smaller than previous releases.) If you know how to make
a significant reduction, please forward suggestions.
After an "appropriate" period in Beta, a release version will be generated.
For further details, see OPOS CCOs History.
Downloadable Files
|
Prior Releases |
Released |
Size |
|
|
|
 1.11.000 CCO Runtime (Wise
Install) |
2007/01/30 |
1,265,554 |
|
1.11.000 CCO Runtime (ZIP File) |
2007/01/30 |
1,101,477 |
|
1.11.000 CCO Debug Runtime (ZIP
File) [see warning below] |
2007/01/30 |
5,125,355 |
|
1.11.000 CCO Source Code and Data
Files (ZIP File) |
2007/01/30 |
1,520,726 |
|
|
|
|
1.10.002 CCO Runtime (Wise
Install) |
2007/12/04 |
1,129,131 |
|
1.10.002 CCO Runtime (ZIP File) |
2007/12/04 |
964,022 |
|
1.10.002 CCO Debug Runtime (ZIP
File) [see warning below] |
2007/12/04 |
4,575,043 |
|
1.10.002 CCO Source Code and Data
Files (ZIP File) |
2007/12/04 |
1,345,788 |
|
|
|
|
1.10.001 CCO Runtime (Wise
Install) |
2006/09/22 |
1,130,516 |
|
1.10.001 CCO Runtime (ZIP File) |
2006/09/22 |
965,286 |
|
1.10.001 CCO Debug Runtime (ZIP
File) [see warning below] |
2006/09/22 |
4,214,546 |
|
1.10.001 CCO Source Code and Data
Files (ZIP File) |
2006/09/22 |
1,345,740 |
|
|
|
|
1.9.002 CCO Runtime (Wise
Install) |
2007/12/04 |
1,054,267 |
|
1.9.002 CCO Runtime (ZIP File) |
2007/12/04 |
889,271 |
|
1.9.002 CCO Debug Runtime (ZIP
File) [see warning below] |
2007/12/04 |
3,722,920 |
|
1.9.002 CCO Source Code and Data
Files (ZIP File) |
2007/12/04 |
1,248,794 |
|
|
|
|
1.9.000 CCO Runtime (Wise
Install) |
2005/04/29 |
1,054,370 |
|
1.9.000 CCO Runtime (ZIP File) |
2005/04/29 |
889,250 |
|
1.9.000 CCO Debug Runtime (ZIP
File) [see warning below] |
2005/04/29 |
3,931,948 |
|
1.9.000 CCO Source Code and Data
Files (ZIP File) |
2005/04/29 |
1,236,872 |
The install files were packaged using Wise InstallMaster 7. No system DLLs are
installed. Files are only placed in the directory that you specify, plus its
subdirectories. The ZIP files package the CCO release with a batch file
for registering and unregistering the CCOs and support files (if needed).
The file types are
- Common Control Object Runtime.
This file installs the OPOS Control Objects and the OPOS header files.
The Control Objects use MBCS, so they may be deployed on Windows 95/98/ME™
and NT/2000/XP/2003™.
- Common Control Object Debug Runtime.
This file installs a debug version of the CCOs, along with the OPOS header
files plus tracing support files.
For details on tracing, see the Tracing
page.
- Warning! The debug CCOs trace
all data sent between the application and Service Object. Therefore,
they must not be used in live customer environments where sensitive information may be exposed. For example:
- The MSR debug CCO traces full card information including account numbers, names, and CVV.
- The PINPad debug CCO traces the card account number, encrypted PIN, and key serial number.
- The MICR debug CCO traces the bank transit number, checking account number, and check (serial) number.
- Common Control Object Source Code and Data Files.
This file installs:
- The source code, including a master project, projects for each control object, plus
common and bitmap files.
- The data files, which are used by a custom generator to produce much of the source
code.
Visitor: #
Last updated:
2008-01-18
|
