| Anchor | ||||
|---|---|---|---|---|
|
| Include Page | ||||
|---|---|---|---|---|
|
...
CHARON-VAX / CHARON-PDP model | Minimal number of host CPU cores | Recommended number of host CPU cores |
|---|---|---|
VAX 6610 | 2 | 4 |
VAX 6620 | 3 | 4 |
VAX 6630 | 4 | 6 |
VAX 6640 | 6 | 8 |
VAX 6650 | 8 | 12 |
VAX 6660 | 8 | 12 |
| Other models | 2 | 2 |
When starting, the CHARON-VAX software checks the available number of host CPU cores. Currently, this check is based on the maximum number of VAX CPUs that can be emulated, not on the number of the actually configured VAX CPUs. Therefore the number of host CPU cores recommended for the maximum number of emulated CPUs - as shown in the right column of the table above - must be available. If the available number of host CPU cores is below this number, CHARON-VAX will issue a warning message even if the requirements for the configured number of VAX CPUs are fulfilled. The CHARON-VAX software will work despite this warning if the requirements for the configured number of VAX CPUs are fulfilled.
| Note |
|---|
Hyperthreading must be switched off completely. Disable hyperthreading in the BIOS settings of the physical host or, for a VMware virtual machine, edit the virtual machine properties, select the Resources tab then select Advanced CPU. Set the Hyperthreaded Core Sharing mode to None. |
...
Login as the local system administrator ("Administrator") on the host system.
Create a special user for running CHARON-VAX / CHARON-PDP (optional). This user must have all the administrative privileges. Please consult with your Windows User's Guide on details.
Note The CHARON installation procedure will create a special group called CHARON-GRP and the current user will be automatically included to this group. Do not remove this group and do not remove any CHARON user from it, otherwise a problem with virtual memory allocation may appear on CHARON startup.
The created user may belong to some domain, but please note that in this case you have to add this user to the CHARON-GRP manually as it is described in this article and then reboot CHARON host.
Stay logged in as local system administrator ("Administrator") or log off and login as the CHARON-VAX / CHARON-PDP user having administrative privileges (if this option has been chosen).
Create a special directory for the CHARON-VAX / CHARON-PDP distribution kit and copy the provided files there.
In case of upgrading from V4upgrade:- from versions 4.7 and
- below → first uninstall all CHARON products.
- from version 4.8 → the version 4.9 can be installed directly. Please note 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 - otherwise they will remain at V4.8.
| Include Page | ||||
|---|---|---|---|---|
|
...
Directory | Description |
Build_XXX\x86 (and Build_XXX\x64 on x64 systems) | Contains product executables and libraries |
Drivers | Contains the CHARON drivers |
Chapi | Contains CHARON API files used for creating new emulated devices |
InstallShell | Contains the CHARON installation procedure executables |
Logs | Contains the CHARON installation log |
| Redistributables | Contains the redistributables needed for CHARON running (already installed, except the license alert script) |
| Virtual Machines Manager | Contains the most up-to-date version of CHARON Virtual Machines Manager |
| Virtual Machine Templates | Contains templates for creating CHARON Virtual Machines |
| Virtual Machines | Contains the CHARON Virtual Machines |
| Virtual Disk Images | Contains the CHARON virtual disk images, for example "charoncp012" and "idle_vms_pkg_v3.0" |
...
If a remote license server is to be used:
- Copy the file "
hasp_install\haspdinst.zip" from the CHARON distribution to any directory on the server, for example "C:\Temp". - Extract the content of this archive to the same directory.
- Login as "Administrator" on the server and open "
cmd.exe" from the "Start" menu. - Switch to that directory.
Install the extracted file.
Example:
...> cd c:\tempc:\temp> haspdinst.exe -fr -kp -nomsgc:\temp> haspdinst.exe -install -cm- Copy the file "
hasp_install\hasplib.zip" from the CHARON distribution to any directory on the server, for example "C:\Temp". - Extract the contents of this archive to the same directory.
- Copy the file "
haspvlib_68704.dll" to "C:\Program Files (x86)\Common Files\Aladdin Shared\HASP" (in case of x64 host) or "C:\Program Files\Common Files\Aladdin Shared\HASP" (in case of x86 host) - Connect the network HASP dongle to the server USB port.
...
Software licenses can also be uninstalled using the method, described in the "Removing CHARON-VAX Software Licenses" chapter of this Guide.
For license servers accessible only via non-broadcast search it is also possible to disable access to network licenses if only a local license is to be used: Click on the "Configuration" link to open the "Configuration for Sentinel Manager" page.
Uncheck the "Allow Access to Remote Licenses" checkbox from the "Access to Remote License Managers" tab then press the "Submit" button to apply changes.
| Note |
|---|
Starting with Charon-AXP/VAX 4.9 for Linux and Charon-AXP/VAX version 4.8 for Windows the Charon emulator products do not follow the settings in the Sentinel ACC with respect to querying remote license servers and network visibility. They perform a broadcast search for network licenses even if this has been disabled in the Sentinel ACC. If this behavior has to be prevented for specific reasons, the network access of the system has to be temporarily restricted or disabled, for example by blocking the relevant traffic in a firewall. Another possibility would be to block access to the network license at the license server side. Note that such methods can negatively impact other functions of the system or, in the case of blocking access to a network license on the server, even the functions on other license clients. |
| Info | |
|---|---|
It is possible to have several licenses available to CHARON-VAX at the same time. In this case you have to specify in the CHARON-VAX configuration file the license key ids to be used. Example:
|
...