Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Anchor
TOC
TOC
Include Page
KBCOMMON:KB-CSSstyle
KBCOMMON:KB-CSSstyle

...

  • A Charon license update is required before upgrading. Stromasys might request a HASP dongle state (c2v file) or a host fingerprint taken by HASP Update Service (which is included in the Charon kit) in order to issue a license update. Please refer to License Update Service for details.
  • Due to a Charon installation procedure update, if you upgrade from a version older than 4.8, it is required to uninstall all Charon products before installing Charon-PDP version 4.11. Please use the Windows Control Panel to do perform the operation.
  • (warning) If you upgrade from version 4.8, 4.9, 4.10 or 4.11 (previous build):
    • It is not necessary to save boot parameters at the SRM level (console). Parameters will be kept.
    • It is mandatory to update all existing Charon Virtual Machines to make them run the latest version using the Virtual Machines Manager, VM Configuration tab.
  • The following Microsoft Windows update has to be installed on Windows 7, Server 2008 R2 in order to support new Charon drivers signed with SHA2 signature:
    https://docs.microsoft.com/en-us/security-updates/SecurityAdvisories/2015/3033929.
  • If VMware is used, it must be upgraded to version 5.5, 6.0, 6.5 or 6.7.
  • It is recommended to archive the old Charon log files before starting the new version in order to avoid mixing character encoding in the log files.
  • Intelligent packet processing should be switched off for the network adapters dedicated to Charon with "Network Control Center" (NCC) utility. Please refer to FTP, NFS, and general network issues with Charon-AXP and Charon on Windows for details.
  • The user that runs Charon-PDP must have local administrator privileges and be a member of Charon-GRP group (which is created during the Charon installation).
  • Charon executables, libraries and data (disk container files) files should be excluded from all the antivirus checks, including on-the-fly checks and scheduled scans.
  • HT (Hyper-Threading Technology) should be disabled on the hosting server.
  • Power management, USB power saving management and screen save should be switched off on the hosting server.
  • Please note that the actual network communication speed and mode are determined by the Windows network speed and mode settings.
  • For network connections, interface="connection:..." syntax is preferred in the Charon configuration file.
  • The packet_port keyword in the Charon configuration file can be used on any hosting platform instead of the platform specific keywords ndis5_chpack_port and ndis6_chpack_port


    For example, the Charon configuration file lines:

    load ndis5_chpack_port/chnetwrk EWA0 interface="..."

    and

    load ndis6_chpack_port/chnetwrk EWA0 interface="..."

    can be replaced with:

    load packet_port/chnetwrk EWA0 interface="..."


  • On VMware virtual appliance network adapters and vSwitch should be set to Promiscuous mode
  • On VMware, legacy_mode should be set in the Charon configuration for emulated PDP network adapters if Promiscuous mode cannot be set (this solution does not work in multi-instance configurations)

...

Known restrictions of version 4.11 build 204-11

  • Charon fails to boot RSX-11M-PLUS V4.3 (ID#5423). Workaround is enabling autoboot, for example: "set CPU_0 auto_boot = DU0".
  • The Charon installation may fail with the error message "The installation process cannot replace hasplms.exe because the file is in use". It is known problem of the Sentinel HASP driver installer included in the Charon installation procedure as a 3rd party software. If you face this issue stop the hasplms.exe process manually and re-run Charon installation procedure. See the Installation chapter below for more information.
  • In certain situations, when a network adapter is dedicated to Charon by NCC, its status is shown as if it is still dedicated to HOST (ID#5415).
  • Charon may not boot from physical tapes (ID#1936).
  • A crash may occur when emulated NIC is bound to a teamed host NIC on VMWare (ID#5380, Case #00030554).
  • Only Windows SCSI devices with a driver that uses SCSIport method could be used with the direct SCSI access. Those include most of the device drivers on Windows XP and Windows Server 2003 (R2), and most non disk devices on Windows 7 and Server 2008 (R2). If SCSIport is not supported (and Storport method is used instead), direct SCSI access can't be used.
    This is most likely to be the case for Windows 7 and Windows Server 2008 (R2) disk controller drivers.
    This restriction mainly applies to the disk access. Most part of tape drivers currently support SCSIport. When direct SCSI access is used for devices without Windows drivers, this restriction does not apply.
  • Charon does not support direct access to SCSI devices on Windows 8.1 and Windows Server 2012 R2.
  • Charon-PDP has limited support for teamed network adapters. They could be used only if the MAC address of the virtual network adapter is not changed during Charon-PDP session. In this case the desired MAC address should be set manually in the properties of the network team and in the Charon-PDP configuration file by "station_address=XX-XX-XX-XX-XX-XX" configuration option.
  • Charon-PDP does not support virtual network adapters (i.e. MS bridges, etc).
  • Network speed auto negotiation works with some restrictions. It is always recommended to use full duplex mode on the hosting server.
  • Network Control Center could show some minor problems on Simplified Chinese version of Windows.
  • The correct license must be available to enable the Charon-PDP to start. Check the capability of your license by using the utility "HaspView" which is available as a part of the kit.
  • If Charon is being moved to another hosting platform and direct the SCSI access method is used to access some SCSI devices, the new hosting platform SCSI drivers should support the SCSIport method. If drivers supporting SCSIport method are not available, direct SCSI access cannot be used. This is most likely to be the case for most Windows 7 and Windows Server 2008 (R2) devices. The recommended workaround for disk access is to use the \\.\PhysicalDriveX method.
  • Due to the change of "Charon Virtual Machines Manager" to "Charon Virtual Machine Manager", an upgrade from a version prior to 4.11 will create a new shortcut on the desktop and will not remove the one pointing to "Charon Virtual Machines Manager". This then has to be done manually. Please note that both shortcuts point to the same executable file.

...

  • Charon Network Packet NDIS Signed driver for Windows 10, Windows Server 2016/2019 working with Secure Boot enabled.
  • Sentinel Runtime upgraded to version 8.13.
  • New version of PuTTY, supporting "-title" option and new way of storing/loading sessions definitions in the registry to avoid unnecessary duplication of session definitions for each user (ID#5590).
  • MkDisk utility logo is updated (ID#5246).
  • Sample configuration files are updated (ID#5246, #5622).
  • "Charon Virtual Machines Manager" is changed to "Charon Virtual Machine Manager" (ID#5246). Note: if you're upgrading from a previous version, the "Charon Virtual Machines Manager" icon has to be removed manually.
  • The NDIS driver is upgradable, newer version of the driver in a Charon kit to be installed updates the driver automatically (ID#5585).
  • A specific dialog is added for recommended actions if a container cannot be extracted in the process of a Charon installation (ID#5586).
  • All relevant Charon components are installed independently by each Charon build to be installed on the host if these components are not "upgradable" (shared between builds) (ID#5504).
  • Charon installation procedure graphics are updated to display correct slogan (ID#5558).
  • MkDisk utility graphics are updated to display correct slogan (ID#5562).
  • Serial lines logging is corrected (ID #5647).

New functionality introduced in version 4.10 build 202-03

  • IEQ11 board is implemented on top of (couple of) NI PCI-GPIB interface cards (ID#4670).
  • Spectracom TPRO/BI timer board is implemented (ID#4481).
  • Log is flushed regularly and asynchronously to facilitate online LOG monitoring by third-party tools (ID#5532).
  • Correct installation of x64 HostPrint utility in all Charon products is implemented (in the folder beside the corresponding executables) (ID#5570).
  • VMware Ethernet adapters: in addition to the E1000, E1000E and VMXNETx adapters are now fully supported.
  • Copyright notes are updated in all sample configuration files (ID#5399).
  • EXE/DLL copyright is updated (ID#5503).
  • The value of "log_repeat_filter" parameter is "off" by default (ID#5405).
  • Licensing mechanism is improved (ID#5375, 5458, 5459).
  • Network License management processing changes (ID#4631).
  • Redistributable Visual C++ runtime is upgraded (ID#5385).
  • Installation procedure detects inconsistent and/or damaged installation and deals with it properly (ID#5476).
  • In "Repair" mode installation, the procedure keeps the current Charon installation in case of errors (ID#5477).
  • All Charon components are installed independently for every build (ID#5504).
  • Patches to Charon kits are able to keep all the previous executables independent from each other (ID#5506).
  • Backup patch scripts are installed for each build independently (ID#5517).
  • Virtual Machines renaming feature is disabled (ID#5394).
  • "hasp_view" command line mode is extended to output all available licenses details to a file (ID#5442).
  • NCC utility is improved (ID#5497).

...

  • Fixed a problem where patch script created incorrect backup directories (ID#5516)
  • Fixed HOSTprint working on Windows 10 (ID#5054)
  • Fixed broken "license_key_lookup_retry" option functionality (ID#5538)
  • Fixed a problem with incorrect selection of default product while creating VM with Charon Manager (ID#5530)
  • Fixed a problem where Charon VMs (services) lost dependency on HASPLMS (ID#5529)
  • Fixed a problem where InstallShell defined versions of VC redistributives installed incorrectly (ID#5494)
  • Fixed an error during installation on Windows Server 2016: "NDIS Packet driver is not installed" (ID#5544)
  • Correct Charon service dependencies persist now when upgrading existing Charon VMs (ID#5546)
  • InstallShell graphics is updated for correct slogan (ID#5558)
  • MkDisk utility graphics is updated for correct slogan (ID#5562)
  • Fixed a problem where HOSTprint stays running when emulator process terminates (ID#5505)
  • Fixed a problem with long duration of Charon-installation (ID#5360)
  • Fixed a problem with incorrect behavior of action for Edit Configuration in VM Manager (ID#5413)
  • Fixed a problem where host NIC dedicated to Charon is shown as dedicated to host in the Network Control Center (ID#5415, 5429)
  • Fixed a problem where there is no network connection when "packet_port" is in legacy mode (ID#5427)
  • Fixed a problem where Charon reports "Can not change current ethernet address... Dynamic change of ethernet address is disabled or is not supported" if port_enable_mac_addr_change is set to false (error code 00000113) as an error instead of a warning (ID#5443)
  • Fixed a problem with unexpected forced Windows reboot during Charon installation (ID#5455)
  • Fixed a problem where in "Repair" mode (only) Installation, the procedure processes running "logmond" incorrectly (ID#5479)
  • Fixed a problem where Installation procedure detects versions of installed VC++ redistributives incorrectly (ID#5494)
  • Fixed a problem where NCC fails to install NDIS driver (ID#5177)
  • Fixed a aproblem where Charon crashes when emulated NIC is bound to a teamed host NIC on VMWare (ID#5380).
  • Fixed a problem where Virtual Machine Manager does not pick up changes in log file specification and configuration names if the VM name contains spaces (ID#5390).

  • Fixed a problem where no RDP warning is displayed in local license key environment (ID#5400).

  • HALT is not available (disabled, greyed out) on emulator's system tray menu (ID#5437 and ID#5451)
  • Did not detect "no power" status correctly (ID#5458, 5459)
  • CHMAC installation failure (ID#5508)

...

  • Unpack Charon kit into a temporary (installation) folder.
  • Run the "InstallShell.exe" file in the installation folder.
  • Choose the products to install and proceed with suggested steps.
  • Please note that the media may contain more products than allowed by your license.

(warning) Charon installation may fail with an error message "The installation process cannot replace hasplms.exe because the file is in use". It is known problem of the Sentinel HASP driver installer included to Charon installation procedure as a 3rd party software.

In this case follow the procedure recommended by Sentinel:

  1. Login as an user having Administrator Rights.
  2. Use the Sentinel HASP Runtime Environment Removal tool (https://sentinelcustomer.gemalto.com/sentineldownloads/?s=removal&c=#)
  3. Stop any antivirus or firewall available on the system.
  4. Stop and remove "hasplms.exe" manually. This file is available under "C:\Windows\System32". In case if "hasplms.exe" is read only or hidden change the file properties accordingly.
  5. Restart the system
  6. Run Charon installation again

...