RE: FreeAXP 435

The FreeAXP User Guide and Release Notes have been updated. The update covers the use of end point security products on systems running FreeAXP. MCSa has reported that the Tanium ( www.tanium.com/ ) security product appears to block programs using a CPU at 100% for an extended period of time, as FreeAXP does. We recommend that the FreeAXP program (freeaxp.exe) be put on security and anti-virus exclusion lists. We also recommend that virtual disk and tape container files be put on anti-virus exclusion lists.

You can download the updated User Guide and Release Notes at these links:

User Guide: www.migrationspecialties.com/pdf/VirtualAlpha_UserGuide.pdf
Release Notes: www.migrationspecialties.com/pdf/VirtualAlpha_ReleaseNotes.pdf <hr>

Migration Specialties is pleased to announce the release of FreeAXP 3.0.0.617. The update can be downloaded from the links provided below. This update provides the following enhancement:

- Support for VSI's OpenVMS V8.4-2L2 Performance Release for Alpha.

FreeAXP 2.0.0.617 Kit: www.migrationspecialties.com/Downloads/freeaxpsetup_617.exe
Release Notes: www.migrationspecialties.com/pdf/VirtualAlpha_ReleaseNotes.pdf
User Guide: www.migrationspecialties.com/pdf/VirtualAlpha_UserGuide.pdf

Microsoft updates to Windows 10 Version 1709 have an additional security requirement that Microsoft countersign the MSI signing certificate used on the Avanti msipcap network driver. Avanti and FreeAXP 614 and 617 may loose network access after a Windows 10 update beyond Build 16299.309. The following solutions address this issue:

1) Install the updated FreeAXP/Avanti 617e kit. This kit contains an updated msipcap driver using a certificate accepted by the current release of Windows 10. www.freeaxp.com

2) Fall back to FreeAXP/Avanti 598. The signing certificate used in this version is exempt from the new Windows checks.

3) Turn off Windows Secure Boot and disable driver signature enforcement. There are many articles on the Internet that describe how to do this. However, doing so allows installation of unsigned drivers, so we do not recommend this option without a full understanding of your system’s security and vulnerabilities.

To our knowledge, this change does not impact Windows Server 2016 or any other Windows releases. Avanti 617 installs and runs without issue under Windows 7, 8.1, 2008 R2, 2012 Std & R2, and 2016 Standard, 10.0.14393 Build 14393. However, we expect Microsoft will add similar restrictions to Server 2016 going forward. If Avanti network services stop working after a Windows update, install the 617e kit.

To determine the version of Windows being run, open a Command Prompt or the run box and execute winver. To check on msipcap, open a Command Prompt as Administrator and execute the following command:

C:&#92;WINDOWS&#92;system32&gt; net start msipcap

If msipcap is installed, a message will display saying it has already been started. If Windows is blocking it, a message to that effect will be displayed.

FreeAXP 3.0.0.620 is now available. Download links are provided below. This update provides the following improvements:

Support for disk serial numbers.
Fix for Windows 10 kernel mode driver license change.

FreeAXP 3.0.0.620 Kit: www.migrationspecialties.com/Downloads/freeaxpsetup_620a.exe
Release Notes: www.migrationspecialties.com/pdf/VirtualAlpha_ReleaseNotes.pdf
User Guide: www.migrationspecialties.com/pdf/VirtualAlpha_UserGuide.pdf

[b:]Disk Serial Number Update (Tru64 UNIX)[/b:]

Avanti allows serial numbers to be assigned to each disk or CD drive in the advance disk options. OpenVMS and Tru64 UNIX 3.x and 4.x ignore the disk serial numbers. Tru64 UNIX 5.x requires them. If a serial number is not present, Avanti generates one for each disk.

Versions of Avant prior to 3.0.0.620 had three potential problem with disk serial numbers.

1. User defined CD device serial numbers are ignored. The Avanti generated serial number is always used.

2. Avanti generated serial numbers for disk devices are not unique across SCSI adapters. A disk on adapter 0 and a disk on adapter 1 may receive the same generated serial number. The workaround is to manual set the serial numbers.

3. The generated serial numbers for all HSZ22 disks was the same, resulting in system hangs under Tru64 UNIX 5.x. The workaround is to manual set the serial numbers.

These problems have been corrected in Avanti 3.0.0.620.

[b:]Windows 10 Pcap Signature[/b:]

Windows 10 Version 1709 Build 16299.371 and higher object to the msipcap signature in Avanti 614 and 617 and will not install Pcap, leaving Avanti without network access. Avanti 598 installs and runs without issue. Windows 10 Version 1709 Build 16299.309 and older do not have this problem.

The issue came about because Windows 10 now requires registration of kernel mode drivers with Microsoft. Avanti 3.0.0.620 addresses the problem. If you encounter the pcap license error, downgrade to Avanti 598 or upgrade to Avanti 620.

[b:]Important Notice[/b:]

Avanti 3.0 is built using the latest Windows Visual Studio and Intel C++ compiler. This development environment does not support the following legacy Windows O/S:

· Windows XP
· Windows Vista
· Windows Server 2003
· Windows Server 2008 Std

Migration Specialties maintains a legacy development environment to support customers with software support contracts running under these retired Windows O/S. See the current Virtual Alpha Release Notes for additional details.

The pending release of Avanti 4.0 incorporates a big change for FreeAXP, Migration Specialties free Alpha emulator. FreeAXP will no longer be a standalone product. Instead, it has been integrated into Avanti.

What does this mean for FreeAXP users?

• FreeAXP is now 64-bit only. It will not run on a 32-bit host system. The last 32-bit compliant FreeAXP release is 3.0.0.620.

• Instead of downloading a separate FreeAXP installation kit, the Avanti installation kit is downloaded.

• The FreeAXP.exe image file is now dec.exe. The installation folder will be “MSI Digital Emulator Collection”. If you have scripts calling FreeAXP.exe, they will need to be updated.

• The FreeAXP installation folder is no longer used. If FreeAXP configuration files are stored in the FreeAXP installation folder, update them before installing Avanti 4.0.

[i:][b:]• The limit of one instance of FreeAXP per host system has been eliminated![/b:][/i:]

You read that last bullet right. Starting with Avanti 4.0, the limit of one FreeAXP instance per host system has been removed. You can now have as many FreeAXP instances as there are host CPU’s available minus one. I.E. An eight-core system will support up to seven instances of FreeAXP. (A more realistic scenario is four FreeAXP instances on an eight-core system, but seven is legal).

Avanti 4.0 is in testing and will be released soon. If you are a FreeAXP user, start getting ready for the change. The pre-4.0 version of FreeAXP will remain available on our web site for download, but will no longer be supported.<hr>

The release of Avanti 4.0 incorporates a big change for FreeAXP, Migration Specialties free Alpha emulator. FreeAXP will no longer be a standalone product. Instead, it has been integrated into Avanti.

What does this mean for FreeAXP users?

• FreeAXP is now 64-bit only. It will not run on a 32-bit host system. The last 32-bit compliant FreeAXP release is 3.0.0.620. The pre-4.0 version of FreeAXP will remain available on our web site for download, but will no longer be supported.

• Instead of downloading a separate FreeAXP installation kit, the Avanti installation kit is downloaded.

• The FreeAXP.exe image file is now dec.exe. The installation folder will be “MSI Digital Emulator Collection”. If you have scripts calling FreeAXP.exe, they will need to be updated.

• The FreeAXP installation folder is no longer used. If FreeAXP configuration files are stored in the FreeAXP installation folder, move them before installing Avanti 4.0.

• The limit of one instance of FreeAXP per host system has been eliminated!

You read that last bullet right. Starting with Avanti 4.0, the limit of one FreeAXP instance per host system has been removed. You can now have as many FreeAXP instances as there are host CPU’s available minus one. I.E. An eight-core system will support up to seven instances of FreeAXP. (A more realistic scenario is four FreeAXP instances on an eight-core system, but seven is legal).

To date FreeAXP has been downloaded over 31,000 times. Thank you for your support!