# CHARON-AXP for Windows 64bit
VERSION 2.4 Build 118-05 (Production)
Release notes

Please review the Release Notes and refer to the User Manual before proceeding with installation or upgrade of CHARON-AXP

## 1. Products included in the CHARON-AXP release version 2.4 build 118-05

In this document the term CHARON-AXP is used to refer to all the products below:

- CHARON-AXP/4100 for Windows 64bit
- CHARON-AXP/DS10 for Windows 64bit
- CHARON-AXP/DS20 for Windows 64bit
- CHARON-AXP/ES40 for Windows 64bit
- CHARON-AXP/GS80 for Windows 64bit
- CHARON-AXP/GS160 for Windows 64bit
- CHARON-AXP/GS320 for Windows 64bit

## 2. Supported software platforms

- Windows 2003 Server Standard or Enterprise (SP2) Edition 64 bit version
- Windows XP Professional (SP3) 64 bit version
- Windows Server 2008 Standard or Enterprise (SP2) Edition 64 bit version
- Windows Server 2008 R2 Standard or Enterprise Edition 64 bit
- Windows 7 Professional and Ultimate Editions 64 bit version

## 3. Hosting hardware recommendations

- The number of available (Intel or AMD) CPU cores in the hosting server should be at least 150% of the number of emulated AXP CPU cores
- The recommended number of available (Intel or AMD) CPU cores in the hosting server is twice the number of emulated AXP CPU cores
- Intel Xeon 566x, 567x, 5680, and Intel Core i7 980 CPUs are recommended for optimal CHARON-AXP performance for configurations with up to eight emulated AXP cores
- The Intel Xeon X7560 is recommended for optimal CHARON-AXP performance for configurations with eight and more emulated AXP cores
- Non-ECC DDR3 1600 MHz and 1333 MHz RAM is recommended for optimal CHARON-AXP performance

## 4. New functionality introduced in build 118-05

- A new product, CHARON-AXP/GS320, is now available for AlphaServer GS320 replacements. Please refer to the SPD for details
- A new emulated model AlphaServer 400 supporting 1 AXP CPU and up to 1 GB of memory is included into CHARON-AXP/4100
- CHARON-AXP supports Windows 7 and Windows Server 2008 R2
- The Network Control Center supports all AXP network interfaces
- DCI-1100 is supported via the pass-through driver
- Support of the PBXDA-BB and PBXDA-AC serial line adapters is available via the DIGI pass-through driver
- Ctrl-P, CONTINUE and CRASH commands implemented in SRM console
- CHARON utilities support for simplified Chinese Windows had been introduced
- Logging message format and content has been improved. Logfiles are opened in append mode by default
- The 'repeated messages' logging filter is enabled by default
- MkDisk utility has been expanded to handle .VDISK metadata
- A full de-installation removes all CHARON settings and files.
- SRM Console and advanced network configuration settings have been documented

## 5. Configuration changes required when upgrading from previous versions of CHARON-AXP to build 118-05

- A CHARON-AXP license update is required
- The user that that runs CHARON-AXP must have local administrator privileges
- CHARON-VAX executables, libraries, and data (container files/disks) 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, if using Intel CPUs capable of HT
- DEP (Data Execution Prevention) should be set to "Turn on DEP for essential Windows programs and services only"
- Power management and screen saver should be switched off on the hosting server
- The Tru64 kernel needs to be rebuilt for the emulated AS400 AXP model that is included in the CHARON-AXP/4100 product
- If CHARON-AXP is being moved to another hosting platform and direct the SCSI access method is used to access some SCSI devices (mainly disks), the new hosting platfrom 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 Windows 7 and Windows Server 2008 (R2) disk controller drivers.
  This restriction mainly applies to the disk access. Most tape drivers currently support SCSIport. When direct SCSI access is used for devices without Windows drivers, this restriction does not apply.
  The recommended workaround is to use CHARON-AXP disk container files or the \\.\PhysicalDriveX method.
  Please refer to this knowledge base article for additional information
- For the emulated network adapters DE500AA and DE500BA, the communication speed and mode should be set manually in the CHARON-AXP configuration file. For example:
  load DE500BA/dec21x4x EWA interface=EWA0
  load ndis6_chpack_port/chnetwrk EWA0 interface="..."
  set EWA adapter_mode="100BaseT-FD"
  Please note that the actual network communication speed and mode is determined by the Windows network speed and mode settings. This configuration change is required to avoid network timeouts in VMS/Tru64 during negotiation phase. This behavior will be fixed in the next CHARON-AXP release
- When changing hosting platform from Windows XP or Server 2003 to Windows Server 2008 (R2) or Windows 7, The NDIS6 driver should be used instead of NDIS5. For example:
  a CHARON configuration file line:
  load ndis5_chpack_port/chnetwrk EWA0 interface="..."
  Should be replaced with:
  load ndis6_chpack_port/chnetwrk EWA0 interface="..."
- It is recommended to use interface="connection:..." syntax. Please refer to the knowledge base article for the details.
- Intelligent packet processing should be switched off for the network ports dedicated to CHARON-AXP. Below are examples of the correct settings -- the exact naming of the parameters depends on the network adapter driver:
  Offload receive Ip checksum = off
  Offload receive tcp ckecksum = off
  Offload Transmit Ip checksum = off
  Offload Transmit TCP checksum = off

## 6. Problems fixed in build 118-05

- Windows Server 2008 CN: "Invisible" Installation Log (empty log file) (ID#2678)
- ds10l.exe installation fails on Win2008 Chinese version (ID#2685)
- DE435 is offline with VMS 6.2-1H3 on AS4100 (ID#2680)
- The firmware does not detect DE450 adapter and therefore does not print it in the device list (ID#2652)
- DE450 remains OFFLINE in VMS (ID#2653)
- Problem using CDROM on an HP blade server via USB (ID#2651)
- Digital UNIX 4.0B fails to install on AlphaServer 400 (ID#2631)
- Console logs are not appended to by default (ID#2628)
- AS400 Emulator crash while installing Digital UNIX 4.0F (ID#2619)
- AS2000 and AS2100 unable to "create an instance of the component dec_21040" (ID#2597)
- Incorrect behavior on HALT command in kernel mode (ID#2595)
- ES40 Emulator crashed when performing the SWINGBENCH test (ID#2586)
- -FILE boot option of the SRM console was not implemented (ID#2102)
- A file "mkdisk.vtable" is absent in the kit -- without it MKDISK cannot start (ID#2589).
- The configuration template for the AS400 model has incorrect HW_MODEL syntax and is missing the PKB bus (ID#2373).
- Incorrect text encoding in the NetDiag help on Chinese systems (ID#2373).
- Tru64 V5.1B was unable to load driver for DEC 21040 PCI Ethernet Adapter (ID#2304).
- CHARON-AXP crashed on UETP test (ID#2348).
- Ticket #7079: Charon crashed on a production system with segmentation violation (ID#2389)
- The old .BIN files lead to CHARON misbehavior. It should be replaced for new one (ID#2447)
- A disk device goes offline suddenly with the "mount verification in progress" message (ID#2512)
- Tru64/tar utility is unable to write if the output device is a tape. (ID#2383)
- Failed to unload the virtual tape on Tru64. (ID#2385)
- VMS 7.2-1 booted on DS10L and DS20 with FC Pass-Through enabled hangs VMS. (ID#2390)
- Some configured disks disappeared from the OpenVMS environment (SRM console) under CHARON-AXP/B108 AS4100.(ID#2393)
- CHARON-AXP/ES40 is unable to boot Tru64 from FC attached disk (ID#2412).
- TOY data (including data/time) is not saved (ID#2414).
- Install procedure does not issue warnings when unsupported host platform is used (ID#2431).
- Putty Console does not work (no proper session is available) when CHARON-AXP runs as a service (ID#2452).
- Ticket #7682: "BOOT EWA0" command in the SRM console leads to the emulators hanging (ID#2469).
- ID#2470 - Ticket #7684: BOOT DKA500 may boot from wrong device.
- ID#2471 - Ticket #7687: Pressing "F6" button terminates emulator. The default behavior has been changed to "none".
- Ticket #7716: SRM console HELP command is missing (ID#2472).
- Network Control Center utility does not recognize teamed interfaces (ID#2331)
- Some license messages are absent in the LOG file, for example "the license is expired" (ID#2040)
- NFS issue: "cp" command never ends and the "cp" process becomes zombie (ID#2257)
- SRM variables get saved in wrong console variables (ID#2295)
- Handling of some exceptional cases in DIT2 due to resource lock must be implemented to avoid possible overflow (ID#2404).
- Grammar error in message text: some typos had been corrected (ID#2428)
- Embedded network adapters and additional ones (having the same name) conflict without any notification (ID#2429)
- System hangs OpenVMS 7.1-2 with printing jobs (ID#2441)
- Compilation of C code using FP flags /FLOAT=IEEE /IEEE=DENORM result in zero values (ID#2446)
- log_method="append" does not work if specified separately from the other configuration commands for the logging definition (ID#2450).
- Utilities help does not start on "F1" on Windows 2008 / Vista operating systems (ID#2498)
- Ultrium tape drive fails on all VMS commands (ID#2386)
- Ticket #7774: Problems NDIS6 driver - memory leak was found (ID#2490)
- Many question marks sometimes displayed in the Network Control Center Chinese help file (ID#2373)
- Tape error: "-BACKUP-F-NOTANSI, tape is not valid ANSI format" (ID#2521)
- Exception (C0000005): Segmentation violation occurs on different configuration and applications (ID#2527, 2528, 2534, 2510)
- "EXA0: Failed to create symbolic link to the packet driver" error prevents using CHARON-AXP networking despite the configuration is correct (ID#2554)
- The OpenVMS V8.3 CPUSANITY bugcheck while performing KGPSA initialization
- Outgoing FTP hang problem on GS80/GS160 models (ID#1999)
- A problem with Fortran compiled code generating exceptions (ID#145)
- Several problems with physical tapes including tape initialization, label handling, tape restore, and Files-11 file system on the tape
- A problem reporting version 2.2 instead of 2.3 in the SRM console
- A problem with VMS freezing during shutdown
- A problem with freezing VMS boot after "%PKQDRIVER-W- PKA0, Chip reset failed, trying again" error message
- A problem with EW devices not showing up at AS2x00 CRM console
- A problem with multi instance configuration preventing more than one CHARON-AXP instance from running
- A problem with certain CPU affinity configurations causing "division by zero" crash
- "Back" button does not always work during installation
- An error message could appear during uninstallation of CHARON-AXP through Control Panel
- Setting particular disk and tape types with media_type parameter on KZPBA is not supported for \\PhysicalDriveX configuration style
- Emulated PCI network adapter DE435 is not recognized in the AXP SRM console, however it is recognized and works for the guest OS.
- CHARON-AXP may wrongly report that no license is present if the correct license is present.
- Too many scheduled starts and stops of CHARON-AXP service in a short period of time could cause CHARON-AXP crash.
- AlphaServer model 2100 could have problems with initializing of the network controller (DECchip 21040).
- CHARON Network Control Center utility does not have proper Simplified Chinese interface.
- Ultrium SCSI-1 DAT-72 tape drives currently do not work with CHARON-AXP.
- Virtual tape cannot be unloaded and container file replaced on Tru64.

## 7. Known restrictions of build 118-05

- Direct SCSI access only supports Windows SCSI devices which use a SCSIport driver. These 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 cannot 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.
- Performance tests could hang VMS 6.2-1H3 on emulated AS400.
- The message "MODEL NOT INSTALLED" occurs when trying to start Charon on Windows 7/2008/2008R2/Vista via the Launcher utility. Workaround: Run the "Launcher.exe" utility from Administrator (right click of the mouse on the executable, "run from Administrator" option). (ID#2557)
- There is a problem stopping CHARON if it is running service in "automatic" mode from the CHARON Service Manager utility. Workaround: Run the "CharonManager.exe" utility as Administrator (right click of the mouse on the executable, "run as Administrator" option). (ID#2624)
- CHARON-AXP modem communication sometimes may fail. This problem is under investigation. (ID#2642)
- UETP fails on a tape image if CHARON runs on VMware (ID#2427)
- CHARON-AXP does not emulate VGA adapters, thus OPA0 is always a system console. So all the applications hardcoded to use OPA0 and TTA0 as their own interfaces may not function correctly.
- Sometimes CHARON-AXP may not display its tray icon especially when it runs as service. Use "Ctrl-P" combination of keys to go to the SRM console.
- Network speed auto negotiation works with some restrictions (see the table below). It is always recommended to use full duplex mode on the hosting server.

  Host settings | VMS (autodetect mode) | Tru64 (autodetect mode)
  1 Gbps full duplex | 100 Mbps full duplex | 100 Mbps full duplex
  1 Gbps half duplex | 100 Mbps half duplex | 100 Mbps half duplex
  100 Mbps full duplex | 100 Mbps full duplex | 100 Mbps full duplex
  100 Mbps half duplex | 100 Mbps half duplex | 100 Mbps half duplex
  10 Mbps full duplex | 10 Mbps full duplex | 10 Mbps full duplex
  10 Mbps half duplex | 10 Mbps half duplex | 10 Mbps half duplex

- The virtual Alpha firmware is designed to support a maximum of 48 devices.
- The firmware does not support the command recall using the up/down arrow keys.
- MUX network driver installation could crash Simplified Chinese Windows
- The terminal emulator putty.exe may not work correctly during UNIX Tru64 installation. This happens when putty.exe is connected using TELNET and the key "Return" sends Telnet New Line instead of ^M escape sequence. Use the RAW connection ("-raw" switch): set OPA0 port=10003 application= "putty.exe -raw localhost:10003". For TELNET connection uncheck the box "Return key sends Telnet New Line instead of ^M" in the Change Configuration ... / Connection /Telnet. Alternatively use a commercial terminal emulator or connect hardware VTxxxx via a serial port or server.
- Do not include a terminal emulator startup in the CHARON-AXP configuration file starting as a service. The terminal emulator cannot start as no console session is available. Configure a TCP/IP port instead. This is the only way when using Windows Server 2008 and Windows Vista to get a console once CHARON-AXP is configured as a service.
- The VMS 7.x Monitor utility shows the maximum CPU quantity instead of actually configured quantity. It is a VMS 7.x restriction, and does not apply to VMS 8.x.
- Running Alpha Linux on the virtual Alpha is not supported
- Use of IDE is limited to ATAPI CDROM on the host machine. No iSCSI support is planned for IDE. UETP may produce error messages if IDE emulation is used.
- Floppy disks are not supportede.
- A Telnet session from OpenVMS running on emulated host freezes 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 is unable 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 an SSH connection.
- Running as a Service may fail as the Service manager may not be able to identify all configured disks.
  CHARON-AXP does not support virtual network adapters (i.e. MS bridges, etc.).
- CHARON-AXP has limited support for teamed network adapters. They can used only if the MAC address of the virtual VMA or Tru64 network adapter is not changed during CHARON-AXP session. In which case the desired MAC address should not be set manually in the properties of the network team or in the CHARON-AXP configuration file using the "station_address=XX-XX-XX-XX-XX-XX" configuration option.
- VMS 7.2-1 should be patched to the latest level in order to use Emulex FC adapters in pass-through mode.
- Please note that CHARON-AXP has not been tested with SAN attached storage over 2TB in size.
- The log of CHARON in simplified-Chinese cannot be opened by the Wordpad and Notepad text viewers. Some solution should be found for displaying the log (ID#2358)
- Virtual network adapter works incorrectly on Win2003-64: some duplicate packets are found on PING operation, "SET HOST" does not work, etc. (ID#2364).
- Tru64 temperature monitoring should be disabled. It could cause Tru64 version 5.x shutdown with the message: "system fan has failed, system is shutting down now". If installing Tru64 from scratch, do not install envmon package. If it is already installed, disable automatic startup by booting into SINGE USER mode and issue the following command:
  rm -f /sbin/rc?.d/*envmon
  then "exit" (Ctrl-D) to multi user mode.

## 8. New functionality introduced in the previous Production version 2.3 build 108-00

- A new product, CHARON-AXP/4100, has been introduced. It supports the emulation of AlphaServer 2000, 2100, 4000, and 4100. The earliest supported guest OS versions are: VMS 6.2-1H3 and Tru64 4.0F. SPD is available from http://www.stromasys.com. Please refer to the CHARON-AXP manual for details.
- CHARON-AXP is now delivered with half of the CPUs available for the particular model by default. For example, CHARON-AXP/GS80 can have up to eight AXP CPUs, hence the base license includes four CPUs.
- Support for 64bit Windows Server 2008 Standard and Enterprise (SP2) Editions, and 64bit Windows Vista Business (SP2) Edition.
- Multiple instances of CHARON-AXP can run on a hosting server simultaneously. Please refer to the CHARON-AXP manual for details.
- Connection to a physical FDDI network is supported using pass-through mechanism with physical DEPFA FDDI network adapter in the hosting server.
- Emulated AXP CPU performance has been improved. Please see SPDs and Product Announcements for the details, which are available from http://www.stromasys.com
- Significant network stability and performance gains after fixing a problem in the rx sequencer delay algorithm.
- DE435 network adapter emulation has been introduced, supporting VMS versions 6.2-1H3 and later.
- For disk and tape containers on KZPBA a particular type (for example, HSZ80) can be set using the media_type parameter, which may be necessary in order for Tru64 to recognize them.
- The Internal disk table had been extended to recognize RZ1ED, RZ1EF disk types.

## 9. New functionality introduced in the previous Production version 2.2 build 104-00

- Fiber Channel (SAN attached) storage can be used with emulated PCI KGPSA adapter if a specific Emulex HBA is used in the hosting server. Please refer to the User Manual for the details. The SAN target has to be configured for CHARON-AXP guest operating system. The configuration has been tested with both OpenVMS and Tru64.
- SRM console functionality had been improved to include FC configuration and booting commands.
- On Windows Server 2003 and Windows XP physical SCSI disks and SAN LUNs can be attached to CHARON-AXP using \\.\ScsiN:X:Y:Z notation. Please check the manual for details. There are three formats supported:
  \\.\SCSI<port-no>:<target-id>
  \\.\SCSI<port-no>:<target-id>:<lun>
  \\.\SCSI<port-no>:<path-no>:<target-id>:<lun>
- iSCSI disks can be attached to KZPBA SCSI controller using \\.\PhysicalDrive notation provided that they are created with Microsoft iSCSI Initiator (other initiators have not been tested).
- CHARON-AXP has Simplified Chinese interface and logfile if installed on Windows with Simplified Chinese localization.

## 10. Distribution and Installation

The kit is distributed as a standard CHARON installation. The installer version is 3.3.
Make sure there are no CHARON-AXP configurations running before the installation.
Run the "InstallShell.exe" file in the CHARON-AXP installation folder. Choose the products to install and proceed with suggested steps. Note that the media may contain more products than allowed by your license.
STROMASYS SA
http://www.stromasys.com
email: info@stromasys.com
Document: 60-17-008-011
Updated: 24 January 2011