Hardware Platforms
Support for the following platforms has been added:
| • | Red Hat Enterprise Linux 6.6 64-bit (x86_64) |
| • | SuSE Linux Enterprise Server 11 SP3 (x86_64) |
| • | Mac OS X 10.9 64-bit (x86_64) |
|
Support for the following platforms has been dropped:
| • | Red Hat Enterprise Linux 6.2 64-bit (x86_64) |
| • | SuSE Linux Enterprise Server 11 SP2 (x86_64) |
| • | Windows Vista 64-bit (x86_64) |
| • | Mac OS X 10.8 64-bit (x86_64) |
|
Installation
HyperWorks 14.0 suite contains several independent product packages. This gives you the flexibility to download desired packages as needed. Any HyperWorks 14.0 standalone SA update package can be installed either on top of an existing 14.0 installation, or can be installed independently without the prerequisite of a 14.0 base. Multiple product SA updates can now be installed concurrently with or without the 14.0 base.
HyperWorks 14.0 installer brings the robust capabilities and features of the HyperWorks installer as well as the additional support for new products including new GUI based HyperXtrude and FEKO applications.
| - | New GUI based HyperXtrude |
| - | New Linux Compatibility Tool: HyperWorks 14.0 now includes a Linux utility for system diagnostics to help troubleshoot Linux issues |
| - | New GUI based license utility |
| - | HyperWorks Student Edition available for Mac OS X |
| - | MotionSolve subroutine builder |
| • | Standardized MPI implementations: The implementations of the Message Passing Interface (MPI) have been standardized across FEKO, AcuSolve, RADIOSS, and OptiStruct. The Intel, IBM Platform, Microsoft, and MPICH MPI implementations are now included. End users can still use their own MPI implementation. |
|
| • | Upgrade the HyperWorks Installer to InstallAnywhere 2014 SP1 |
| • | File Association: HyperWorks 14.0 on Windows now associate HyperWorks files with appropriate HyperWorks applications |
| • | File Preview: HyperMesh files now have previews in the icons |
|
| • | HyperMath is now available on on Mac OS X |
|
| • | Resolved issue encountered when non-HyperWorks product installers existing in the same directory as Altair HyperWorks installers |
| • | Improved error reporting for HyperWorks installation |
| • | Resolved an issue with help configuration in the installer |
| • | Resolved graphics issues on Optimus based video card setups |
|
| • | In Mac OS X 10.9 the installer will still report “-0” on the Summary panel due to a bug in InstallAnywhere. |
| • | Using the Back option during an installer may not reset the installer variables correctly. |
| • | On Linux and Mac OS X, installing in a directory with spaces is not supported. |
| • | On Windows 8, desktop and Start Menu icons are blank for server and client installations. This can be resolved by changing the Windows File Explorer policy to “Allow the use of remote paths in file shortcut icons”. |
| • | On Linux, during a console mode install, when using a response file output the Help Configuration in the file may not write out correctly. |
| • | If there is not enough TMP/TEMP space on the main drive (such as, C: under Windows), then the installer will prompt for the user to input to a new location. Some Java TMP/TEMP space will still try to go to the main drive even when selecting this new location. |
| • | When clicking on Cancel to stop an installation via the Master installer, the files that were already installed are not cleaned up, but the files in the TMP/TEMP folder are cleaned up. You will need to uninstall/delete the installed files from the chosen install folder manually if Cancel was used. |
| • | The HyperWorks installers do not support the use of the default InstallAnywhere installer.properties files. We request that a unique name is used when using a response file, (for example, installer_hw14.properties) and to use it with the ‘-f <path_to_file>/<filename>’ command line option. |
| • | For NETSETUP client installs, a UNC path must be used to get to the server installation path through Windows Explorer or Windows Network. Note, using mapped drive letters or variables is not currently supported in the installer. |
| • | With some versions of GNOME, there is a bug where the icons are not placed in a hierarchy. Instead, they are placed in “Other” with a flat layout, meaning that all the icons appear at the same folder level in “Other.” KDE is not affected. |
| • | On Linux, the installer does not run the icon installation by default; the user must run the icon installer located in the LinuxMenu directory. |
|
