Installation and Operations Guide > Installing on UNIX and LINUX > 3.5 Optional Steps
XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX''">   
3.5 Optional Steps
Enabling Optimal Virtual Memory Access
The Patran system is a collection of 32-bit executables that interact with one another. The main program is the familiar graphical user interface (GUI) component, but many other back-end processors are likely to be invoked during a typical user session. Each individual executable employs standard Unix system calls such as malloc() for dynamically allocating virtual memory in sufficient quantities for processing end user requests based on model size and complexity. The theoretical maximum size (program size plus data space) for a 32-bit process is 4GB. However, some operating systems reserve a portion of memory for system functions and therefore limit the total memory available to user processes. This section will describe the issues relevant to each platform and will provide guidance on tuning your system, where possible, to maximize the amount of virtual memory available to Patran.
Hewlett-Packard HP-UX
HP-UX PA-RISC systems do not impose any significant limitation on the usable address space for a typical 32-bit process. Itanium systems running a minimum level of HP-UX 11.23 with patch PHKL_31500 will be capable of supporting user process sizes approaching 4GB. In order to achieve these results you must be certain that your system is configured with adequate RAM and swap space. Please also ensure that your maxdsiz, maxtsiz, and maxssiz kernel parameters are set as described in Required Hardware & Software Configurations, 79 of this guide.
IBM AIX
The AIX operating system divides memory into 256 MB segments. 32-bit executables can access 16 total memory segments (4 GB) but not all segments are available to end-user processes. AIX provides three separate address model options for 32-bit processes: the default memory model, the large memory model, and the very large memory model. Patran is configured to use the AIX very large memory model, which enables up to 2GB of virtual memory per user process on AIX 5.1 and up to 3.25 GB beginning with AIX 5.2. No special system tuning is required to achieve the maximum process sizes indicated above, as long sufficient physical RAM and swap space resources exist on your system.
Sun Solaris
The Solaris operating system does not impose any significant limitation on the usable address space for a typical 32-bit process. You can expect to achieve a maximum process size of nearly 4GB for Patran if your system is configured with adequate RAM and swap space.
Red Hat Linux
The Red Hat Linux operating system does not impose any significant limitation on the usable address space for a typical 32-bit process. You can expect to achieve a maximum process size of nearly 4GB for Patran if your system is configured with adequate RAM and swap space.
 
Installing 3Dconnexion Spaceball for Use with Patran
Patran supports the 3Dconnexion Spaceball 4000, 5000, and SpacePilot. Follow the SpaceWare installation instructions for these products. No additional steps are required for use with Patran. You can obtain these instructions, as well as the latest drivers, at the 3Dconnexion web site, www.3dconnexion.com/.
1. Downloaded driver from: <http://www.3dconnexion.com/downlink.asp>
From this page you can choose your operating system.
2. Create a "spaceball" directory in /usr or /opt
By default the directory will be called "magellan".
3. Go into that directory, and install the driver.
4. To invoke it, call /usr/spaceball/xdriver.static
The spaceball automatically has translation and rotation in x, y, z turned ON. Right button automatically re-centers the model.