CortexJPOS Windows (64-bit Operating Systems)

CortexJPOSSetup-6.1.1-Windows_x86.exe Installation executable for 32-bit x86-64 Intel / AMD processor architectures 64-bit Architecture CortexJPOSSetup-6.1.1-Windows_x86-64.exe Installation executable for 64-bit x86 Intel / AMD processor architectures

1. NEW FEATURES IN THIS RELEASE

The following are notable new features in this release.

  • None

2. ENHANCEMENTS/IMPROVEMENTS/FIXES

CortexJPOS 6.1.1 (2021-05)

  • Added support for CR2700 paired with A271.
  • Added support for CR1100
  • Added support for CR5200
  • Updated JPOS installer

CortexJPOS 6.0 (2018-02)

The following are JIRA issues resolved by this release. Note feature requests are in bold while bugs are in normal text. Note the italicized JIRA issues are issues found during Code's internal testing.

  • JPOSPSW-1 (Bugzilla 1217) - An error message should come up letting the user know that JPOS can't run if CortexTools/CortexWedge is running
  • JPOSPSW-2 (Bugzilla 1216) - JPOS will not ignore modems that are connected to the computer
  • JPOSPSW-3 (Bugzilla 1098) - Script error on application load
  • JPOSPSW-4 (Bugzilla 1083) - CortexJPOS driver crashes on second attempt to claim a device when none present
  • JPOSPSW-6 (Bugzilla 288) - After adding a device in the OPOS/JPOS device manger screen, the image displayed next to the device is the same (CR1000) for all readers
  • JPOSPSW-7 (Bugzilla 583) Reader de-enumerates / re-enumerates continuously if it decodes something during POSTest "claim"
  • JPOSPSW-8- Add software support for 8200-family readers using CodeUtil2 SDK (CodeUtil2.dll)
  • JPOSPSW-10-Device manager's "Cancel" button label shows "Can..."
  • JPOSPSW-11-The device name field is grayed out when adding a serial device
  • JPOSPSW-14-Message comes up to configure 950 and 8200 readers that have already been added to the device manager
  • JPOSPSW-15 - InstallShield incorrectly gives an error on Java version
  • JPOSPSW-16-If CortexJPOS works with JRE 9, installation should state "JRE 8 or later"
  • JPOSPSW-17 - Message saying you have to uninstall the old version of JPOS should come up
  • JPOSPSW-18 - A serial device is not detected when it is connected and requires the appropriate platform selection (CT8000- versus CT8200-technology)
  • JPOSPSW-19-Connected serial reader shows it is not present on re-opening Device manager
  • JPOSPSW-20-JPOS won't install on a computer with Java version 8 update 111
  • JPOSPSW-21-JPOS doesn't list the CR5000 when it detects it
  • JPOSPSW-23 - Message about "device claim failed" comes up when both the sample application and device manager are open
  • JPOSPSW-24-No matter what barcode is scanned the only output is the same
  • JPOSPSW-27-Change JPOS zip file name
  • JPOSPSW-30-When clicking on the disconnect button when a 950 and 8200 reader is disconnected, the sample app crashes
  • JPOSPSW-35-CR1400 was disconnected but no message came up indicating it was not present
  • JPOSPSW-36-Only 8200 readers can be configured as a serial device
  • JPOSPSW-37-JPOS occasionally crashes when first launched
  • JPOSPSW-38-JPOS sample app crashes when attempting to connect to 8200-family serial reader

CortexJPOS 4.0.5 (2013-10-23)

  • Connected devices not listed in device manager after deleting the connected device profile name and clicking the "Add device" button without restarting the application
  • CR900 Device not detected in JPOS device Manager
  • Devices that are added already in the device manager with the option "Lock the hardware" still listed in the "Available new device" options after restarting the JPOS device manager
  • Device name for the connected devices not added when we rename the default logical device name in JPOS Device manager
  • Serial port device not detected in JPOS device manager
  • Configuration for single reader of the particular type is not working for multiple devices
  • Sample application crashed when unplugging connected devices

CortexJPOS 3.0 (2012-02-27)

  • Device manager not detecting the device connected in the sample application and asks to remove the device name while opening the device manager after opening the sample application
  • Option for removing individual device from missing devices in the device manager is not available

CortexJPOS 2.0 (2012-02-06)

  • Initial Release

3. CHANGES TO DEFAULT SETTINGS

CortexJPOS 6.1.1

  • None

CortexJPOS 6.0

  • None

4. OUTSTANDING ISSUES

  • A serial-based, 8000-family reader requires the user to select a COM port with the normal COMx port name, while a serial-based, 8200-family reader (CR950, CR8200) requires the user to select a COM port with the "8200" COMx(8200) port name. This situation arises because CortexJPOS must use an 8000-family SDK to communicate with 8000-family readers and an 8200-family SDK to communicate with 8200-family readers, and their communication protocols are incompatible. Until the CortexJPOS application has a solution provided by the coming enhancement of the SDKs to permit automatic detection and reader differentiation before the application must use an SDK, the user will need to select the reader using a differentiated COM port name so CortexJPOS "knows" which SDK to use.
Hier herunterladen
CortexJPOS Windows (64-bit Operating Systems)