Page Comparison

...

2. Save Secure boot is not supported by CHARON at the moment since in this case host OS will not accept signature of distributed NDIS drivers needed for CHARON networking. Disable save secure boot or use CHARON without networking (select "Ignore" when installation procedure reports that NDIS driver is not signed).

New functionalities introduced in build 194-02 since previous release (build 183-02)

...

• Network booting is supported with exception of VAX6xxx models.
• In certain situations of several CHARON virtual machines running on one host with DSSI cluster configured, CHARON may hang up if load on the nodes is very high (ID#5426)
• 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 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. 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.
• CHARONCP SET MAGTAPE utility does not support TQK50/TUK50 controllers (ID#5398)
• Sometimes VAX 6310 does not boot guest OS. The workaround is restart of the emulator and a second try (ID#5384)
• Sometimes OpenVMS 7.2 freezes on booting. The workaround is to restart the emulator (ID#5396)
• A segmentation violation in module NCR53C94 may very rarely occur. If that happens, please provide CHARON configuration and log files to Stromasys (ID#4633)
• CMS commands may slow down due to a its internal design. STROMASYS provides (on request) a special OpenVMS utility to solve the problem (ID#4651)
  
• CHARON cannot correctly define the total number of available CPUs on multi CPU groups systems (NUMA architecture, etc) - it reports only a number of the CPUs found in its first group. This problem will be fixed in future releases.
  As a workaround, enable "Node interleaving" from the BIOS (if available) to make the BIOS report the total number of available CPUs (as a part of one consolidated NUMA group) to the operating system.
  For example, on HP Proliant servers, the configuration sequence is the following:
  - Boot the server, press F9 and enter BIOS setup.
  - Select "Advanced Options" -> "Advance Performance Tuning Options" -> "Node Interleaving", set it to "Enabled".
  - Boot Windows.
• "Violation of constraint" may happen on RDB loading on VAXserver 3600 (ID#2832)
• MicroVAX II emulator hangs while booting MDM (ID#3382)
• CHARON may not boot from physical tapes (ID#1936)
• CHARON-VAX does not emulate graphical adapter. Applications hardcoded to use graphical hardware as their own interfaces may not function correctly
• 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. It's recommended to use CHARON-VAX for Linux if access to SCSI devices is necessary.
• CHARON-VAX has limited support for teamed network adapters. They could be used only if the MAC address of the virtual VMS network adapter is not changed during CHARON-VAX session. In this case the desired MAC address should be set manually in the properties of the network team and in the CHARON-VAX configuration file by "station_address=XX-XX-XX-XX-XX-XX" configuration option.
• CHARON-VAX 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.
• The firmware does not support the history of commands called with the up/down arrow keys.
• VMS 7.x Monitor utility shows the maximum CPU quantity instead of actually configured quantity.
• A Telnet session from OpenVMS running on emulated host may freeze console output. The console output can hang when the virtual serial line sends XOFF/XON sequence. The TELNET client sends XOFF to the remote node's TELNET server to suspend output, but for unknown reason XON is discarded and remote node's TELNET server has no chance to resume output. The console remains "frozen". As the remote site is not sending any output to it. When that happens, the local node is reachable over network, and can be unlocked by typing the 'break' character - usually "Ctrl-]" and exiting telnet session by typing "exit" at "TELNET>" prompt.
• Emacs hangs if the OPA0 console is used. Emacs works fine over telnet connection.
• VMS command START/CPU does not start an emulated CPU if it had been previously stopped with STOP/CPU command. This problem will be fixed in the next CHARON-VAX release.
• Network Control Center could show some minor problems on Simplified Chinese version of Windows.
• The correct license must be available to enable the CHARON-VAX to start. The software may wrongly report that no license is present if the correct license is not present. Check the capability of your license by using the utility "HaspView" which is available as a part of the kit.
• If installed on VMware, sometimes the POST tests report errors for emulated VAX models 4106 and 4108.
• 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 \\.\PhysicalDriveX method.
• The virtual machine associated service running Charon-VAX V4.9 B19402 is created with a missing dependency to hasplms service. This can cause a service (virtual machine) defined for automatic startup to fail with license missing on Charon server boot. The current workaround consists in opening a cmd.exe command as an Administrator and running the following command (do not omit space after the equal sign): sc config <service> depend= hasplms/tcpip . This operation will have to be performed on each service update until a patch is delivered.

...

• 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.

 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

...