Alias - Wavefront Install Notes

Installing StudioTools 9.
5
Installing StudioTools 9.5
© 1999 Alias|Wavefront.
Printed in the U S A, All rights reserved.
Studio Documentation Team: Mona Albano, Pat Anderson, Matt Chaput, Stephen Gaebel, Karen
Hoogsteen, Adam Kozyniak, Joanne MacPhail, Margot Meijer.
The following are trademarks of Alias|Wavefront:

3Design™ Alias PowerCaster™ Kinemation™ SurfaceStudio™
Advanced Paint™ Alias PowerTracer™ Maya™ Artisan SuperConductors™
Advanced Visualizer™ Alias QuickRender™ Maya™ Cloth VisPaint2D™
Alias® Alias QuickShade™ Maya™ Complete Visualizer Server™
Alias Metamorph™ Alias QuickWire™ Maya™ Fur Wavefront™
Alias MotionSampler™ Alias RayCasting™ Maya™ Fusion Wavefront Composer™
Alias MultiFlip™ Alias RayTracing™ Maya™ F/X Wavefront Composerlite™
Alias Natural Phenomena™ Alias SDL™ Maya™ Invigorator Wavefront IPR™
Alias OpenAlias™ Alias ShapeShifter™ Maya™ Live Wavefront MediaStudio™
Alias OpenModel™ Composer™ Maya™ MEL Wavefront 3Design™
Alias OpenRender™ Conductors™ Maya™ PowerModeler ZaP!iT™
Alias OptiF/X™ Data Visualizer™ Maya™ Unlimited
Alias OpenRender™ Dynamation™ MetaMorph™
Alias PowerAnimator™ Explore™ StudioPaint™
Maya is a trademark of Silicon Graphics, Inc. exclusively used by Alias|Wavefront.
Microsoft and Windows NT are registered trademarks of Microsoft Corporation in the United States and/
or other countries. Solaris is a trademark of Sun Microsystems Inc. All other product names mentioned are
trademarks or registered trademarks of their respective holders.
This document contains proprietary and confidential information of Alias|Wavefront, Inc. and is protected
by international copyright law. The contents of this document may not be disclosed to third parties,
translated, copied, or duplicated in any form, in whole or in part, without the express written permission of
Alias|Wavefront, Inc.
The information contained in this document is subject to change without notice. Neither Alias|Wavefront,
Inc. nor its employees shall be responsible for incidental or consequential damages resulting from the use of
this material or liable for technical or editorial omissions made herein. Not all features described are
available in all products.
Alias|Wavefront, 210 King Street East, Toronto, Canada M5A 1J7

Introduction 1
I n st a l l i n g on Installing on Windows Systems 5

W i n d o w s S ystem s 3 Installation Workflow 6
Before You Begin the Installation 7
Installing StudioTools on Windows Systems 14
Licensing StudioTools 20
Confirming Installation 21
Tuning StudioTools Interface Performance 23
Re-installing StudioTools 25
Uninstalling StudioTools 26
Uses of the StudioTools CD ROM 28
Common Questions 29
Additional Resources 32
Licensing on Windows Systems 33
Licensing Overview 34
Obtaining Licenses 37
Licensing StudioTools on Windows Systems 38
Confirming License Installation 47
Troubleshooting License Problems 48
Examining a Licensing Log File 53
I n st a l l i n g on UNIX Installing on IRIX 63

61 Installation Workflow 64
Overview of Installation 65
Before You Install 69
Installing StudioTools with Software Manager 74
Installing StudioTools Using inst (Advanced) 79
Licensing StudioTools 82
Preparing to Use StudioTools 83
Installation Troubleshooting 96
Installing on the Solaris operating environment 101
Installation Workflow 102

Before You Install 103
Installing StudioTools Using Admintool 109
Licensing StudioTools Software 113
Setting Up User Accounts and Projects 114
Licensing on UNIX Platforms 119
Licensing Overview 120

Obtaining Licenses 122
Licensing StudioTools for UNIX Systems 123
Confirming License Installation 129
Troubleshooting Licensing Problems 131
Examining a Licensing Log File 133
Complementary Software and Peripherals (IRIX Only) 141
Setting up OCTANE Duo and Dual Display Configurations 142

Dial and Button Box 143
Spaceball 146
Space Mouse 147
SGI Impressario Printer Setup 150
Installing Dispatcher 151
A ppendixes 153 Appendixes 155
Getting Help and More Information 156

Understanding Licenses 160
Redundant Servers 165
Plotter Installation 181
File Structure (UNIX Only) 187
NFS Overview (UNIX Only) 196
Introduction
Welcome to Version 9.5 of StudioTools, which provides many
improvements from previous versions.
For information on... See...
Installing StudioTools Installing on Windows Systems on page 3

Installing on UNIX on page 61
Installing on the Solaris operating environment on page 101
Licensing StudioTools Licensing on Windows Systems on page 33
Licensing on UNIX Platforms on page 119
Setting up peripheral devices Complementary Software and Peripherals (IRIX Only) on
to work with StudioTools on page 141
IRIX
What’s been fixed for What’s New in StudioTools
StudioTools The Release Notes book in sections called, “Limitations Fixed.”
New and improved features What’s New in StudioTools
StudioTools bugs and The Release Notes
limitations
Environment variables used The Release Notes
by StudioTools
Important Tips
● The online version of this document will not be as up-to-
date as the printed version. Please use the printed book if
you want to see any last-minute additions.
● You must install EvalViewer from its CD for it to work
with the Studio advanced modeling/evaluation license.
For EvalViewer installation and release notes, see the
Quick Install & Release Notes for EvalViewer 9.5.
1
Introduction
2
Introduction
In stalling o n
Win d o ws S y stems
Installing on Windows
Installing on
Windows
Systems
Systems
This section describes how to install and license StudioTools
on Windows NT and Windows 2000:
Installation Workflow ........................................................................6
Before You Begin the Installation ......................................................7
Installing StudioTools on Windows Systems ..................................14
Licensing StudioTools ......................................................................20
Confirming Installation ...................................................................21
Tuning StudioTools Interface Performance .....................................23
Re-installing StudioTools ................................................................25
Uninstalling StudioTools.................................................................26
Uses of the StudioTools CD ROM...................................................28
Common Questions .........................................................................29
Additional Resources .......................................................................32
Installing on Windows Systems

5
Installation Workflow
If you are installing a basic configuration of StudioTools, your
task will not be as difficult as the size of this book might
indicate!
Here is a quick overview of what you have to do:

1 Verify that your system has the right hardware and
software. See Before You Begin the Installation on page 7.
2 Install StudioTools. See Installing StudioTools on Windows

Systems on page 14.
3 License StudioTools. See Licensing on Windows Systems on

page 33.
4 Confirm that you can use your StudioTools software. See

Confirming Installation on page 21.
If you run into trouble, be sure to go to the troubleshooting

sections:
● Common Questions on page 29
● Troubleshooting License Problems on page 48

6
Before You Begin the
Installation
To install and license StudioTools for Windows NT, you need a
basic understanding of how to use Windows NT, but you do
not need to be a professional administrator.
Installing on
Windows
Systems
Important
Your user account must have administrative privileges if

you are going to install and license StudioTools.
Setting up Windows NT and your hardware

The following pages describe system requirements and how to
set up Windows NT and your hardware for StudioTools for
Windows NT operation. Before you start, examine your
system as described below.
To examine your system capabilities

1 From the Windows NT Start menu, either:
◆ Select Programs > Administrative Tools (Common) >
Windows NT Diagnostics.
◆ Select Start > Run, type in winmsd, and press Enter.
The Windows NT Diagnostics window appears.
2 You can click on the following tabs to view various types

of information about your system: Version, System, Display,
Drives, Memory.
Tip You can save or print the contents of a tabbed page if you
need a record of your system capabilities. From the
Windows NT Diagnostics window, for each page select File
> Save Report or, alternatively, File > Print Report.
Hardware requirements
Alias|Wavefront certifies certain system configurations from

leading Windows NT workstation manufacturers.

7
Before You Begin the Installation
The minimum hardware requirements for running
StudioTools for Windows NT are:
● Pentium II processor, at least 300 MHz
● 300 Mb free hard disk space, with 60 Mb temporarily
available on the C: drive to start the installation program
● 128 Mb RAM
● A CD ROM drive, or a shared CD ROM drive accessed via
a networked mapped drive
● A mid-performance to high-performance hardware-
accelerated OpenGL graphics card. Overlay plane
capability is highly recommended
● A three-button mouse with mouse driver software. (The
Microsoft Intellimouse is not supported in this release.)
● For licensing, either:
◆ An Ethernet card
◆ A Pentium III machine with CPU ID enabled
◆ A hardware lock provided by Alias|Wavefront with
the StudioTools shipment.
For details, see Hardware requirements for licensing on
page 9.
For details on hardware requirements, see the StudioTools for

Windows NT Qualification Chart included with the printed
documentation. For an version updated with the latest
qualification information, see the Alias|Wavefront Web site.
Software requirements
● Windows NT 4.0 or Windows 2000
At the time of publication, we have confirmed StudioTools
operation on Windows NT 4.0 with Service Pack 5 or 6.
● Web browser (Netscape or Microsoft Explorer)
● Graphics card driver. See the StudioTools for Windows NT
Qualification Chart for tested drivers. Driver software is
available from the manufacturer’s web site.
● Driver software for optional hardware

8
Setting system properties
The following sections describe issues to consider for the
hardware you install for use with StudioTools for Windows
NT. Topics covered include:
● Additional Windows System Setup on page 9
Installing on
● Hardware requirements for licensing on page 9
Windows
Systems
● Graphics card requirements on page 11
● Mouse and keyboard settings on page 12
● Tablets on page 13
Additional Windows System Setup

● Before installing Studio, make sure that you have enough
disk space. You’ll need at least 300 Mb of free space for the
files to be installed, with at least 60 Mb temporarily
available on your C drive to start the installation
procedure. Also make sure you enable write permissions
in the directory where you plan to install Studio.
● Install networking software if you plan to use and share
files on other workstations or platforms. Contact your
network hardware and software vendors for details.
● Remember that user interface color and font descriptions
in StudioTools documentation are based on the default
Windows NT color scheme. If you change colors or fonts,
descriptions in the documentation might differ from what
you see on your screen.
Hardware requirements for licensing
To license StudioTools, you need one of the following security

methods on your system:
● An Ethernet card.
To see if your PC has an Ethernet card, run
C:\aw\COM\bin\lmtools.exe, and click on the System
Settings tab. If the Ethernet address is not blank (it’ll look
something like 00c04fa32f49), you can send this address to
Alias|Wavefront as your license identifier
● A Pentium III with a CPU ID.

9
You must enable the CPU ID on your system (for
instructions, refer to your workstations’ documentation).
To see if your Pentium III has an active CPU ID, run
C:\aw\COM\bin\lmtools.exe, and click on the System
Settings tab. If the CPU ID field is not blank (it’ll look
something like 0000-0673-0003-CC0A-B517-F75F),
you can send this ID to Alias|Wavefront as your license
identifier.
● A hardware lock.
The hardware lock (dongle) is an encoded connector
device you can purchase from Alias|Waverfont as an
alternative to an Ethernet card or a Pentium III CPU ID.
Before running licenses based on a hardware lock, you
will have to plug this lock into your machine. Power
down your machine and then:
To learn the difference ◆ For node-locked licenses, plug the hardware lock into
between node-locked and the parallel connector of the computer that will
floating licenses, see receive the license.
Licensing StudioTools on
page 20. ◆ For floating licenses, plug the hardware lock into the
parallel connector of the computer that will serve
licenses to client computers. Client computers do not
need a hardware lock. When you choose a computer
to operate as the license server, make sure that it is
stable and accessible to client computers on the
network via TCP/IP.
Notes on hardware locks:
◆ Be careful not to force the lock into the parallel
connector incorrectly. Secure the connector with the
supplied screws so it will not come loose and
interrupt StudioTools operation.
◆ If you install another Windows NT program that uses
a hardware lock, plug its lock into the back of the
Alias|Wavefront lock. The Alias|Wavefront lock
must connect directly to the parallel connector.
◆ You can plug your printer into the hardware lock. If
the lock seems to interfere with printing from the
parallel connector, remove the lock and plug the
printer directly into the parallel connector. When you
are finished, plug in the lock again.

10
◆ If you lose the lock, you must buy a new one from
Alias|Wavefront. Consider buying insurance for your
lock as you would for any valuable business property.
Graphics card requirements
The performance of StudioTools in displaying graphics
Installing on
depends on the quality of your graphics card and on the
Windows
Systems
option settings in the Display Properties window of
Windows NT.
To learn the option settings for graphics cards that are certified
for use with Studio, see the StudioTools for Windows NT
Qualification Chart. Also see the README file on your
installation CD ROM for last-minute updates.
If you are using a card that is not certified, do the following

steps. Some of these steps offer only general guidelines
because each manufacturer has a unique set of display
options.
To set your graphics card options

1 Right-mouse click a blank part of your Windows NT
desktop and select Properties from the pop-up menu.
This displays the Display Properties window, also
available through the Control Panel.
2 Click the Settings tab.
3 From the Color Palette pull-down menu, select True Color.
4 This specifies 24 bits of color for best color quality in

displayed images.
5 Drag the Desktop Area slider to the best display resolution

supported by your hardware.
The higher you set the display resolution, the more
graphics card main memory you need. This is sometimes
called video RAM or VRAM.
If your graphics card has VRAM to spare, StudioTools
generally works best at 1280 by 1024 resolution. However,
if you selected True Color and your card has only 8 Mb of

11
VRAM, a lower resolution works better. (At 1280 x 1024,
the card will likely run out of memory, keeping the
OpenGL driver from using hardware acceleration.)
6 When the driver software for your graphics card was

installed, a tab named for the card was likely created in
the Display Properties window. The tab has performance
options that vary with each kind of card. Here are some
general suggestions for setting performance options.
7 In the Display Properties window, click the tab named for

your graphics card, if there is one. If there isn’t, skip to
Step 9
8 Turn on the overlay plane feature, if there is one. If there

isn’t, skip to Step 9.
StudioTools for Windows NT takes advantage of the
hardware overlay plane feature of most mid-quality and
high-quality OpenGL graphics cards. Overlay planes
enable programs to more quickly display certain elements
of a user interface that exist on top of other elements,
without having to redraw the whole interface. On some
products, overlay planes are called hardware overlays.
StudioTools works with four-bit or greater overlay planes,
whether they are single-buffered or double-buffered. For
some graphics cards, you can use overlay planes only if
you turn off stencil planes. Because stencil planes are not
required by Studio, you can turn them off.
9 Select Apply, then OK.
Mouse and keyboard settings
Use standard mouse driver option settings. Do not, for

example, set the middle mouse button to work as a double-
click of the left button.
Some vendors offer Windows NT enhancement software that

lets you use your mouse to activate windows and panels in the
same way as in IRIX. For example, you can download an
XMouse productivity tool from microsoft.com to simulate IRIX
mouse-window activation. Be aware, however, that we have
not tested such software for use with StudioTools for
Windows NT.
The Microsoft Intellimouse is not supported in this release.

12
Tablets
If your Windows system has a Wacom tablet installed, it is

supported by StudioTools.
For information on how to install your Wacom tablet, refer to

the installation guide that came with the tablet, and check
with the Wacom Web site to access the latest available drivers.
Installing on
Windows
Systems
Unigraphics Windows Environment Setup
If you are going to use Unigraphics to transfer data, you must

set up your Windows system as follows:
1 From your Start menu, select Control Panel > System >
Environment.
2 Select the variable UG_ROOT_DIR.
3 Copy the value of this variable to the clipboard (use Ctrl-

C).
4 Highlight the Path variable.
5 Add a colon at the end of the Path value and then after the
colon paste in the contents of the value of UG_ROOT_DIR
(use Ctrl-V).

13
Installing StudioTools on
Windows Systems
The StudioTools CD ROM has an installation program that
guides you through installation on your Windows NT and
Windows 2000 systems. Before you run it, consider the
following:
● Your user account needs administrator privileges to install
Studio.
● You must install StudioTools on each computer where you
want to run it.
● You can install from a local CD ROM drive, or from a
shared CD ROM drive accessed via a networked mapped
drive.
● You can use the program to re-install StudioTools over an
existing version. Re-installing does not remove scenes,
images, user interface preferences, executable files, or
other files created by users. Only the StudioTools
execution software is replaced. See Re-installing StudioTools
on page 25.
To install StudioTools for Windows NT

1 There are two types of installation:
◆ If you are installing from the CD ROM, load it into
your computer. The Autorun program will start, and
an autorun window will appear. (If it doesn’t, browse
the CD ROM folder and double-click on the
autorun.exe icon to initiate the installation.
◆ If you are installing from a directory, double-click on
the autorun.exe icon.

14
Installing StudioTools on Windows Systems
In either type, an Autorun window similar to the
following should appear:
Installing on
Windows
Systems
2 Click Install.
The InstallShield wizard appears briefly:

15
Then the Installation window appears.
3 Read this window and click Next.
4 A window appears, allowing you to choose the

destination location.

16
Click Browse if you want to install StudioTools in a
location other than the default folder. A window appears
where you can change the drive and directory:
Installing on
Windows
Systems
Select a local drive from the drop-down list, and then
select a folder in which to install. (Alternatively, you can
type a new name. If you name a folder that does not exist,
you will be asked if you want the installation program to
create it.)
If you click Network, the Map Network Drive window
appears and you can select another drive on your
network.
5 Click Next.
6 A window appears providing configuration choices:

◆ Typical—installs a typical configuration of Studio.
◆ Compact—installs StudioTools without its help. This is
not recommended unless hard disk space is an issue,
because you will not be able to use the online help.
◆ Custom—lets you select which components of
StudioTools are installed. Choose from help, licensing
software, renderers, CourseWare (required for doing
the tutorials), base software, or floating license server
software.
Notes:
◆ If you are installing software for a floating license
server, you must choose the Custom > Licensing option
so that you can change the licensing software options.

17
◆ The renderer software is greyed out if you have
already opted to install the base components, of which
it is a part. For a render-only install, deselect base and
then select the Renderer in the custom installation.
◆ You can see the relative size of each of these
components, and how much disk space is required
and how much is available.
◆ If you are installing to a FAT16-formatted drive, a full
installation takes about 300 MB of additional disk
space. FAT16 uses a 32K cluster size, so a single 2K file
uses 32K of disk space. NTFS uses a cluster size of 4K,
so a 2K file on an NTFS-formatted drive takes up 4K
of disk space. A full installation takes up about 300
MB on NTFS and 350 MB on FAT16 (based on a FAT16
partition of 2048MB and an NTFS partition greater
than 2048MB.)
7 Once you select the StudioTools components you need,

click Next.
8 The installation program installs the StudioTools files on

the hard disk. The installation window displays the
progress of the installation.
9 When the installation is finished, the system asks whether

you would like to add to your desktop a shortcut to
StudioTools.
If you want a shortcut to StudioTools on your desktop,

click Yes.

18
10 Next, you are asked if you want to restart your computer.
Installing on
Windows
Systems
Remove all disks from your computer, including the
StudioTools for Windows NT installation CD ROM, click
Yes, then click Finish.
The computer restarts and your installation is complete.

19
Licensing StudioTools
You must go to Licensing on Windows Systems on page 33 to
install a license if you are:
● Installing a StudioTools product for the first time
● Upgrading to a newer version of your StudioTools
product
● Adding additional floating licenses to your floating
StudioTools product
● Relocating your StudioTools license to a different machine
or server
If you are updating an existing copy of StudioTools and have a

valid maintenance contract, then your license is probably
included on the software CD in an encrypted file and has been
installed automatically.
If you did not get a message confirming the installation of

your licenses, you need to install a license. Proceed to
Licensing on Windows Systems on page 33 before continuing
to the next section.

20
Confirming Installation
To confirm installation of your StudioTools product, you need
only start it:
● From the Windows NT Start menu, select Programs >
StudioTools9.5 > Studio.
Installing on
Windows
Systems
● Alternatively, if you created a shortcut to StudioTools
when prompted during installation, double-click the
StudioTools icon on your desktop.
For node-locked licenses, or for floating licenses that are

preconfigured to launch a particular StudioTools product, the
main window of StudioTools appears within ten seconds. It
has a central working area and groups of icons at the left side
and bottom. You might need to turn the latter on by selecting
Windows > Palette and Windows > Shelves in Studio.
If there is a problem with your license, or if you have a floating

license with more than one product available, the Application
Launcher appears:
Select a product that has available licenses listed beside it, and
then select Launch. If you see the main StudioTools window as

21
in the description above for node-locked licenses, StudioTools
is installed.
If an error message appears instead, or if the Application

Launcher indicates there are no licenses available, use the
following sections for troubleshooting:
● Licensing on Windows Systems on page 33 (including
Troubleshooting License Problems on page 48), if you suspect
there is a licensing problem.
● Common Questions on page 29
Confirming the stand-alone renderer is correctly

installed
1 From the DOS command prompt, go to the directory
where StudioTools is installed:
C:\aw\StudioTools9.5\bin\
2 Enter the following:

renderer -i
If the StudioTools stand-alone renderer fails to operate you

will see a licensing error in the command line detailing the
problem. For information, see Troubleshooting License Problems
on page 48.
For more information:

● About testing the newly installed stand-alone renderer
and about the renderer workflow, see the Stand-alone
Renderer addendum in the Release Notes.
● About batch renderer commands, see the online Stand-
alone Utilities guide.
● About using FCheck with the renderer, see the online
Stand-alone Utilities guide.

22
Tuning StudioTools Interface
Performance
The following sections describe options you can adjust to tune
interface performance. For details on other performance
issues, see the Release Notes.
Installing on
Windows
Systems
StudioTools for Windows NT menu items
Important menu items to help StudioTools to display or
manipulate objects more quickly are listed below:
● Preferences > Performance Options > RGB Complex Scene
Option
For details, see “Performance Options” in the chapter
“Customizing the Interface” in the Basic Tools book.
Windows NT options
You can set Windows NT Control Panel options to improve
interactive StudioTools performance.
Improve interactive display
Note If you are using an SGI Visual PC, set your Windows NT
Control Panel -> Display Properties to use the preset profile
Graphics and Animation Design.
Select Properties to confirm that the Back Buffer setting is set to

ON.
Otherwise:
1 Right-click any blank part of your Windows NT desktop
and select Properties from the pop-up menu.
This displays the Display Properties window that’s also
available through the Control Panel.
2 Click the tab named for your graphics card in the Display
Properties window.
Set the option for highest frame-to-frame refresh speed (if
available). The option varies by manufacturer. Here are a
few examples:

23
Tuning StudioTools Interface Performance
Turn off Synchronize Buffer Swap to Vertical Sync.
Turn on Higher Frame Rate Performance (Do not sync to screen
refresh).
In some cases, setting the option makes little difference in
speed and worsens the display of moving objects or
causes the display to flicker. If this occurs, turn off the
option.
3 In the Display Properties window, click the Plus! tab.
4 Turn off Show window contents while dragging.

When you drag windows, you’ll see an outline of the
window rather than the window contents. This speeds up
window dragging.

24
Tuning StudioTools Interface Performance
Re-installing StudioTools
You’ll need to install StudioTools if you want to:
● Include items that you omitted previously, such as online
documentation.
Upgrade to a newer or improved version
Installing on
●
Windows
Systems
If you are replacing the same version of the software, you
must uninstall it first (see the next section), and then proceed
with the installation.
If you are upgrading from an older version, the installation

proceeds as normal. The older version is kept, and you are
able to use it along with the newer version. If you added a
shortcut in the prior installation, it remains.

25
Re-installing StudioTools
Uninstalling StudioTools
You can uninstall StudioTools from the Windows Start menu.
To see the version number of the currently installed

StudioTools software, select Help > About Alias from the
StudioTools main menu bar.
To uninstall StudioTools for Windows NT

1 From the Windows NT Start menu, select Start > Settings >
Control Panel > Add/Remove Programs, then select the
StudioTools product you’ve installed.
Alternatively, select Programs > StudioTools9.5 > Uninstall
Studio.
2 If you are prompted to confirm that you want to remove

the application and all its components, click Yes.
Uninstalling StudioTools removes the StudioTools9.5

directory and its subdirectories, and possibly the Com
directory and its subdirectories if they are not used by other
products. It also removes StudioTools keys and values from
the Windows NT Registry.
As the uninstall program removes files, you might see a dialog

box that informs you of shared files that are no longer used by
any programs. You are asked whether you want to remove
these files.
The shared files are typically for license management, and

may be used by other Alias|Wavefront software. If you have
no other Alias|Wavefront software installed, you can
probably delete them. If you’re not certain whether you need
the files, leave them; they don’t occupy much disk space.
The uninstall program also tells you which StudioTools files or

directories it cannot remove. It does not remove any user’s
home StudioTools directory (or subdirectories) or other user-
created files. For example, uninstalling does not remove any
directories or files at or below C:\Aw\Robert. These
directories are not removed because it is likely that the user
wants to keep many of the files.

26
The uninstall program lets you view files that it cannot delete.
You can delete them, if you want, by dragging them to the
Recycle Bin.
You are notified when the uninstallation is complete.
Installing on
Windows
Systems

27
Uses of the StudioTools CD
ROM
Soon after you insert the StudioTools CD ROM, an Autorun
window similar to this one appears.
The window has menu items for these tasks:

● Installing Studio. See Installing StudioTools on Windows
Systems on page 14.
● Viewing the README. This displays a README file that
includes last-minute installation details.
● Exploring the StudioTools CD. This launches Windows
NT Explorer so that you can navigate through the contents
of the StudioTools CD ROM. This lets you know which
files are included on the CD ROM.
● Exiting from the installer. This interrupts installation. You
can quit installation and start over again later.

28
Uses of the StudioTools CD ROM
Common Questions
Installation
Q What happens if I exit from the installation program

prematurely?
Installing on
Windows
Systems
A If you installed a prior version of Studio, exiting from the
installation program returns StudioTools to the state it was in
before you started the installation program. If you are
installing StudioTools for the first time, exiting from the
installation program leaves your system in the state it was in
before you began installation.
Q Can I move the hardware lock to another computer?
A Yes. To move the lock from one node-locked computer to

another, attach the lock and install StudioTools on the other
computer, then copy the previous computer’s aw.dat file to the
new computer. To move a lock from one floating license server
to another, attach the lock to the new computer and do the
installation and licensing procedure over.
Q Can I manually uninstall StudioTools for Windows NT?
A No. Use the convenient uninstall program described in

Uninstalling StudioTools on page 26.
Q Does StudioTools for Windows NT affect the Windows NT

Registry?
A Yes. Some configuration data is stored in the Registry; for

example, the top-level folder of the StudioTools installation.
Operation and licensing
Q Can I run two copies of StudioTools at the same time?
A Yes. If your computer gets its StudioTools license from a

license server, it uses only one license even if you run multiple
copies of StudioTools for Windows NT.
Q How do I kill the StudioTools program when I can’t exit?
A The Windows NT Task Manager lets you kill a task that for
some reason no longer responds to your commands. To

29
Common Questions
display the Task Manager, press the Ctrl-Alt-Delete keys. If
possible, do not quit StudioTools in this way, because you are
likely to lose some of your work. Instead, quit StudioTools by
selecting File > Exit.
Q How do I find out which version of StudioTools I have?
A In StudioTools, select Help > About Alias; or on your desktop,

right-click on the icon and select Properties.
Q How long does it take StudioTools for Windows NT to start?
A This depends on the speed of your computer. In any case,

StudioTools for Windows NT should start within ten seconds.
Q Can I run StudioTools for Windows NT on Windows 95 or

Windows 98?
A No. You must use Windows NT or Windows 2000.
Q What do I do if I see errors when I try to start Studio?
A See Troubleshooting License Problems on page 48.
Other issues
Q What do I do if I lose the hardware lock?
A You must purchase a new lock from Alias|Wavefront.

Consider buying insurance for your lock as you would for any
valuable business property.
Q What do I do if the hardware lock falls off or is removed

while StudioTools is running?
A Reconnect it immediately after disconnection and

StudioTools operation should continue undisturbed. If the
lock is off for more than five minutes, StudioTools quits and
displays:
Lost connection to dongle or License manager,
exiting....
Your work has been saved to the file lostlock.
Look for a file called _m.saved or _checkpoint.saved. For

a node-locked license, reattach the lock, restart the computer,
and start StudioTools again. For a floating license, reattach the
lock to the license server computer, use FLEXlm License

30
Common Questions
Manager to stop and start the license server software, then
have all users on the network start StudioTools again.
Q How do I specify pathnames?
A Windows NT does not distinguish between uppercase and

lowercase letters in file and directory names. It also uses back
slashes (\) as path separators.
Installing on
Windows
Systems
However, in many cases StudioTools for Windows NT allows
forward slashes.

31
Common Questions
Additional Resources
● See the appendix, Getting Help and More Information on
page 156
● For information about Alias|Wavefront and StudioTools
issues, see the web site www.aliaswavefront.com.
● For information about various Windows NT issues, see
the web site www.microsoft.com.
● For information about licensing and hardware locks, see
the web site www.globetrotter.com.
● For details on installation and performance issues, check
the web site of your graphics card manufacturer.
● Bookstores provide an array of helpful books on Windows
NT for various types of users and administrators.

32
Additional Resources
Licensing on Windows
Installing on
Windows
Systems
Systems
Use this section to install licensing on your Windows NT and
Windows 2000 systems.
Licensing Overview .........................................................................34

Obtaining Licenses ..........................................................................37
Licensing StudioTools on Windows Systems ..................................38
Confirming License Installation ......................................................47
Troubleshooting License Problems ...................................................48
Examining a Licensing Log File ......................................................53
Licensing on Windows Systems

33
Licensing Overview
You must install a license if you are
product
StudioTools product
or server
Overview
Alias|Wavefront uses FLEXlm technology as part of its license
management system. Although we use much of the standard
FLEXlm setup, we have customized aspects to better suit the
way our products are installed, used, and licensed. For more
information on what license files look like, see Understanding
Licenses on page 160.
Floating versus Node-locked Licenses

StudioTools licenses are available in both node-locked and
floating forms:
● A node-locked license allows you to run your StudioTools
product on one particular system (machine) and only that
system. This machine must have an Ethernet ID, Pentium
III CPU ID, or a hardware lock attached.
You must contact Alias|Wavefront if you need to relocate
Ethernet ID-based or Pentium III CPU ID-based licenses to
a different system.
● A floating license allows anyone on the network to use the
licensed software, on as many machines as you have
purchased licenses for. For example, if you install five
licenses on your network, up to five machines on the
network can run the licensed software at any one time.

34
Licensing Overview
You will need to choose one machine on your network to
act as the server for these licenses. Only this server
machine needs an Ethernet ID, Pentium III CPU ID, or a
hardware lock attached. All other machines must be able
to connect to and receive their license from this server.
Tips
Installing on
Windows
Systems
● If you see a line near the top of your license that starts
with the word SERVER, you are installing floating
licenses. Otherwise, you are installing node-locked
licenses
● StudioTools products and options correspond with
FLEXlm license feature names. A table of the feature
names and what they represent can be found in the
appendix, Understanding Licenses on page 160.
● See Hardware requirements for licensing on page 9 for
information on Ethernet cards, Pentium III CPU IDs, and
hardware locks.
Licensing Changes from Previous Versions

We have improved our licensing process so that your
installations are more flexible. Note the following changes
from previous versions:
● It is now possible to use an Ethernet ID or Pentium III
CPU ID rather than a hardware lock.
● You can use the same server for all of your StudioTools
floating licenses. For example, you can have both
AutoStudio and SurfaceStudio licenses served from the
same machine.
● A floating license is valid for all supported platforms. For
example, a single license server providing a Studio license
can provide this license to a client operating on IRIX, the
Solaris operating environment, or Windows NT.
● Extra features are available for timed/evaluation licenses;
you are no longer required to remove or update your
permanent licenses in order to evaluate or add temporary
licenses to your servers.

35
Licensing Overview
● Error-prone VENDOR_STRINGs are eliminated, making it
easier to tailor your license for each option, module, or
product you purchase.
● Troubleshooting information is available to help you solve
licensing problems. See Troubleshooting License Problems on
page 48.

36
Licensing Overview
Obtaining Licenses
Typically, licenses have already been sent out to existing users
who are getting upgrades or to new customers who are
working with Alias|Wavefront dealers.
However, if you have not already received a license you need
Installing on
Windows
Systems
to fill out a SPAR (Software Product Authorization Request)
form and send it to Alias|Wavefront.
A paper SPAR form is included in your StudioTools box. Fill it

out and follow its instructions to fax or mail it in.
Upon receiving your SPAR request, Alias|Wavefront sends

you an e-mail copy of the form for your records. After we
process your request, we send you the license information file
you need to install the license. Follow the next section,
Licensing StudioTools on Windows Systems on page 38, to install
it.

37
Obtaining Licenses
Licensing StudioTools on
Windows Systems
Use this section to install the licensing for your StudioTools
software on Windows NT and Windows 2000.
Existing Customers:
If you are a customer on a valid maintenance contract, then
your licenses should have been installed automatically when
you installed StudioTools 9.5 software. A message indicates
that licensing was installed successfully.
If the licenses were successfully installed:

● and if you are using a node-locked license, this completes
licensing for your machine.
● and if you are setting up clients and servers with floating
licenses, proceed to Additional Setup for Floating Licenses
on page 43.
● and if you are a large organization setting up redundant
servers, proceed to Redundant Servers on page 165 in the
appendix.
If you get a message indicating that licensing was not

installed correctly, you must use the following steps to install
your license.
Prerequisites
Before you install licenses, make sure:
● You received your licenses from Alias|Wavefront (See
Obtaining Licenses on page 37.)
● You installed your StudioTools 9.5 software
● You rebooted your machine after installing StudioTools
● You have one of the following capabilities on each
machine (for node locked) or on the license server (for
floating licenses)
◆ Ethernet ID

38
Licensing StudioTools on Windows Systems
◆ Pentium III CPU ID enabled, or
◆ A hardware lock
The license you get from Alias|Wavefront is coded

specifically for the Ethernet card, Pentium III CPU ID, or
Installing on
hardware lock provided for your machine.
Windows
Systems
Ethernet or Pentium III CPU ID licenses cannot be
transferred to any other machine unless you contact
Alias|Wavefront for an updated license.
Hardware locks can be moved to another machine provided

you:
● move the physical lock
● copy over the aw.dat or aw_servername.dat file to
the new machine
● ensure the required parallel port driver is running on the
target machine. For details, see Confirming parallel port
driver installation (for hardware locks only) on page 51.
Preparing your Machines
To prepare each computer
Follow these instructions on every computer to make sure you

have a FLEXlm directory and the license files are viewable.
1 Open the My Computer icon on your desktop.
A window appears, displaying the contents of your
computer.
Tip If you don’t see an icon named My Computer, it may have

been renamed.
2 Double-click the C: drive icon in the My Computer

window. The C: drive window appears.
3 If the FLEXlm directory doesn’t exist under C, create it by

selecting File > New > Folder.
This directory location is mandatory.

39
4 Open the FLEXlm directory by double-clicking it.
5 From the window’s top bar, select View > Options. The
Options window appears.
Note For the following instructions, the interface may vary

depending on the version of your FLEXlm interface.
6 In the Options window, click the View tab.
7 Turn on Show all files by clicking it so there is a black dot in

the centre.
8 Make sure that Hide file extensions for known file types is
turned off (has no check mark), then click OK.

40
Installing Licenses
To install licenses from e-mail, fax, or mail

1 You should have already obtained a license from
Alias|Wavefront. If not, refer to Obtaining Licenses on
page 37.
Installing on
Windows
Systems
For an example of what the license should look like, refer
to Understanding Licenses on page 160.
Note If you requested node-locked licenses for several computers,

you’ll receive a separate e-mail, fax, or mail for each
computer, and should do these instructions for each
machine.
2 Save the e-mail you received from Alias|Wavefront to a

file with the following name:
C:\Temp\License.txt
You can leave the e-mail header information in the file.
If you received the license by fax or mail, carefully type
the license directly into the license.txt file. Use upper and
lowercase letters exactly as provided. (The license won’t
work if you make a typing error.)
Note that:
◆ The license is a text file. To install licenses, work with a
text editor such as Notepad, not with a word
processing program such as Microsoft Word that
might add formatting information to the text file and
make your licenses unusable. If you must use a word
processing program, be sure to save the license as a
text file.
● If the licensing information originates in an e-mail or other
file from a UNIX computer, make sure you transfer it to
your Windows system in ASCII mode rather than binary.
Otherwise, the file will contain additional control
characters and licensing will fail. You can use Windows
Notepad to check for added control characters.
3 Display the Alias|Wavefront License Installer window.

Either:
◆ From the Windows NT Start menu, select
Programs > StudioTools9.5 > Install license, or

41
◆ Run c:\aw\COM\bin\InstallKey.exe. (where c:
is the drive where you installed StudioTools)
4 In the License Installer window, make sure File is encrypted

is turned off.
5 In the Input File text box, enter the path and file name of the
text file you created in the preceding steps.
6 By default, the license is installed into:

◆ C:\Flexlm\aw.dat for node-locked licenses
◆ C:\Flexlm\aw_servername.dat (where server
is the name of the license server) for floating licenses.
If your organization cannot use these default filenames
and locations for these license files, then click on the
Advanced button to specify another path and filename.
7 Click Install.
The Alias|Wavefront License Installer installs the license
into the default Alias|Wavefront license file on your
computer (unless you specified a different location using
the Advanced option). It also converts to comments any
extraneous license information that is superseded by the
new license.
The License Installer doesn’t remove prior licenses, but it
might convert to comments license information that is
superseded by the new license.
8 You may want to confirm that the license information was

installed. Open the license file in a text editor such as
Notepad: the information should look like the license
information sent to you by Alias|Wavefront.
This completes licensing for your computer.

● If you are installing floating licenses, continue with the
instructions in the next section, Confirming License
Installation on page 47.
● If you are receiving error messages, see Troubleshooting
License Problems on page 48.

42
Additional Setup for Floating Licenses
Installing floating licenses is more complex than installing
node-locked licenses. You must set up the license server
computer, and then set up each client computer that will
request a floating license from the server.
Installing on
Windows
Systems
Note The following instructions apply to a Windows NT license
server. If you are using a UNIX license server, go to
Additional Setup for Floating Licenses on page 125
Before doing the following steps, ensure that:

● On the server, there is either:
◆ an Ethernet address for each server
◆ an active CPU ID if the server is a Pentium III machine
◆ a hardware lock plugged into the server machine.
● You have performed the custom installation required for
floating servers (see Installing StudioTools on Windows
Systems on page 14).
● You have performed the steps in the previous section.
To set FLEXlm license server options

1 From the Windows NT server machine, run
C:\aw\COM\bin\lmtools.exe (where C: is the drive
where StudioTools is installed).
2 Click the Service/License File tab.
3 Select Configuration using Services.
4 Click the Configure Services tab.
5 Turn on Start Server at Power-Up and Use Services.
6 Click the Save Service button.
To stop and start the license server
Stopping and starting the server prevents license server errors.

43
Note Every time you install a new license, or change a license,
you need to stop and start the license server, or reboot the
server machine, so that your licensing changes take effect.
7 Click the Stop/Start/Reread tab
8 Click Stop Server to stop the license server.

If the license server wasn’t running, an error message
indicates that the stop failed. Ignore this message and
proceed to the next step
9 Click Start Server to start the license server.
10 Click the Server Status tab.
11 Click Perform Status Enquiry to confirm the license server is

running.
12 If the server is up, the window displays:

servername: license server UP (MASTER)
where servername is the license server’s name.
To set up each client machine
Client machines can be running on any supported platform:

Windows NT, Windows 2000, IRIX, or the Solaris operating
environment.
They should all have Version 9.5 of StudioTools installed. (To

run previous versions concurrently, see the note at the end of
this section.)
Perform the following steps on each client machine.

1 Make sure the license server is accessible to the client
through a TCP/IP network.
2 Edit the aw_servername.dat file (where servername

is the name of the license server computer) using a text
editor:
◆ For Windows NT clients, choose Start > Run. In the
Open field, type the following:
notepad c:\FLEXlm\aw_servername.dat

44
◆ For UNIX clients, use a text editor such as vi to edit
the /var/flexlm/aw_servername.dat file.
If the file does not exist, be sure to confirm its creation if
prompted.
3 Confirm the following lines exist in the

aw_servername.dat file:
Installing on
Windows
Systems
SERVER servername hostid 7111
USE_SERVER
where
◆ servername is the name of the license server
computer
◆ hostid is the host ID. For hardware locks on
Windows NT, this value will be the ID of the hardware
lock on the server machine instead, and look like the
following: FLEXID=flexid, where flexid is the ID.
It is important that these lines are in the right order, and
that there is a carriage return at the end of the
USE_SERVER line.
If these lines don’t exist in the file, you must type them in
as per the e-mail, fax, or letter you were sent.
Notes:
◆ The USE_SERVER and SERVER lines in each client
computer’s aw_servername.dat file tell the client
which computer serves the licenses. This file is called
a license file, though it simply points to the server
computer containing the aw_servername.dat file
that actually includes the license features available to
users.
◆ If you received your StudioTools license by e-mail,
you can simply copy the entire SERVER line from the
e-mail into the text editor, and then replace the
servername entry with your actual license server
computer name. Use upper- and lowercase letters
exactly as shown. The license won’t work if you make
a typing error.
4 Save the file.
5 Close the text editor.

45
6 If the client is UNIX-based, ensure that there are no DOS
control characters in the license file. You can remove them
by typing the following commands in a shell (from the
directory where you stored the temporary file):
For IRIX, use the command:
to_unix aw_servername.dat
For the Solaris operating environment, use the command:
dos2unix -ascii aw_servername.dat /var/tmp/aw_servername.dat
(For the Solaris operating environment, you need to create
another file. After making appropriate backups, replace
the version of aw_servername.dat in /var/flexlm
with the one you just created in /tmp.)
You should be able to launch StudioTools from any client

machines you set up.
Note These instructions apply to customers running all clients at

Version 9.5 or higher. To run previous versions of the
StudioTools software concurrently on some UNIX client
machines, you must use the previous client setup method
for those machines: copy or mount the license file
/var/flexlm/aw_servername.dat to the machines, and
ensure that license file permissions are set to be readable by
everyone.
Next Steps
You’ve now completed the licensing procedure for floating

licenses.
In the next section, you will confirm the installation.

46
Confirming License Installation
To confirm you installed StudioTools licensing
1 Launch StudioTools using either of the following
methods:
Installing on
From the Windows Start menu, select Programs >
Windows
◆
Systems
StudioTools9.5 > Studio.
◆ If you created a shortcut to StudioTools when

prompted during installation, double-click the
shortcut icon on your desktop.
2 If you have a node-locked license, the StudioTools main

window should appear, ready for use.
If there is a problem with your license or if you have a
floating license with more than one product available, the
Application Launcher appears:
If this window indicates there are 0 licenses available for

your products, it’s possible that you have a licensing
problem. See Troubleshooting License Problems on page 48.

47
Troubleshooting License
Problems
This section provides troubleshooting tips for StudioTools
licensing.
After installation, if you start StudioTools and the Application

Launcher or another warning window reports a licensing
problem, use this section to find out why.
If you still have licensing problems after completing this

section, see the appendix on how to contact our Support
Services department (see Getting Help and More Information on
page 156).
Application Launcher Problems
Application Launcher
Possible Solutions
Problem
The Application Launcher • Ensure that you have a valid license installed in either
indicates that there are no c:\FLEXlm\aw.dat or
valid licenses. c:\FLEXlm\aw_servername.dat
(See Licensing StudioTools on Windows Systems on page 38.)
• Ensure that the license server is running.
• Check your license file for typing errors.
• Use the next section, Advanced License Troubleshooting on
page 49, to pinpoint licensing problems.
You run the appLaunch • If there is only one product available in your license, that
(Application Launcher) product will automatically start. You should only see the
command, but StudioTools Application Launcher window if there is a licensing problem
starts without showing the or if there is more than one StudioTools product available in
Application Launcher. the license file.

48
Troubleshooting License Problems
Possible Solutions
Problem
The Application Launcher • All product licenses have been checked out. You cannot
window appears with every run any of the StudioTools products until a license becomes
product name greyed out. available. (Click on the Retry button occasionally to check
whether a license is available yet.)
Installing on
Windows
Systems
You can start StudioTools • Ensure that the ALIAS_LICENSE variable is not defined
from the Application (see the Environment Variables appendix of the Release Notes
Launcher, but you get a for details).
license error if you try to run • It is possible that the product you initially set as your
the Alias executable directly. default product is no longer available. Select another product
in the Application Launcher and click on Save to save that
product as your default setting.
Advanced License Troubleshooting
First steps
If you feel you have already installed a valid license, but

continue to receive the following message:
No valid license found.
Proceed with the following steps:

1 Make sure you restarted the machine with the nodelocked
license, or the license server, after you installed
StudioTools.
2 If you tried to run StudioTools on a client or server, make

sure the time and date on the client and server are correct
and synchronized. If the time and date of the client differs
from the server by more than a half hour, the client might
not be able to get a license.
3 Review the licensing procedure to make sure you

completed all the steps.
4 Do the steps in Examining a Licensing Log File on page 53.
5 Do the steps in Checking for licensing errors with lmtools on

page 56.

49
6 From My Computer or Windows NT Explorer, verify that
the C:\FLEXlm\ directory contains the file aw.dat or
aw_servername.dat.
If this file doesn’t exist, you didn’t do steps required in
licensing. You’ll need to redo the licensing procedure as
described in Licensing StudioTools on Windows Systems on
page 38.

page 56.
Additional steps for floating licenses
If you are running a floating license, try the following

additional steps:
1 Stop and start the license server software as described in
Additional Setup for Floating Licenses on page 43.

page 56.
3 Restart the license server computer.
Additional steps for hardware locks
If you are using a hardware lock, try the following additional

steps:
1 Restart the computer where the lock is plugged in.
2 Make sure you attached the hardware lock correctly. See

Hardware requirements for licensing on page 9 for
installation details.
3 On the appropriate node-locked computer or license

server computer, make sure the parallel port is
operational. A quick way to check this is to plug a printer
into the parallel port connector and print something.
4 Do the steps in Confirming parallel port driver installation (for

hardware locks only) on page 51

50
Confirming parallel port driver installation (for
hardware locks only)
For hardware locks, a Sentinel driver enables communication
between a node-locked computer and its parallel port, or
between the license server computer and its parallel port. The
parallel port connector is where the hardware lock is attached.
Installing on
Windows
Systems
The installation program installs the Sentinel driver on your
computer. To make sure the driver was installed, do the
following steps on the computer where the hardware lock is
attached.
To check Sentinel driver installation:

1 Using My Computer or Windows NT Explorer, open the
Sentinel directory created where you installed the
StudioTools software.
The Sentinel directory is installed at
C:\Aw\Com\Sentinel, where c: is the drive where the
software is installed.
2 Open Setupx86.exe.
This starts the Sentinel Driver Setup Program.
3 Select Functions > Configure Sentinel Driver.
4 If no entry for a parallel port is listed in the window, click

Cancel and install the Sentinel Driver as follows.
To install the Sentinel driver:

1 Open Setupx86.exe to restart the Sentinel Driver Setup
Program.
2 Select Functions > Install Sentinel Driver.
3 In the path text box, specify the location of the files needed
by the Sentinel Driver Setup program to activate the
Sentinel driver.
The Setup program shows the path where it thinks these
files are located. This normally is the correct path. If so,
click OK. If you installed StudioTools in its default
location, you’ll find the files in
C:\Aw\Com\Sentinel\I386.

51
4 Click OK when prompted to restart the system.
5 From the Windows NT Start menu, select Shutdown.
6 Select Restart the computer and click Yes.

52
Examining a Licensing Log File
If you followed the steps in the previous section but still have
trouble with licensing, you may want to create and examine a
licensing log file to learn more about the error:
For a node-locked license, do the following steps on the
Installing on
Windows
Systems
computer where the message appears. For a floating license,
do the following steps on the license server machine.
To examine the license error log file:

1 From the Windows NT Start menu, select
Programs > Command Prompt.
2 At the command prompt, enter:

set FLEXLM_DIAGNOSTICS=2
3 To repeat the failed attempt to start StudioTools, type the

startup command:
Alias.exe
Because you set the environment variable
FLEXLM_DIAGNOSTICS, the attempt to start StudioTools
creates a licensing log file that you can open and examine.
4 To list the files in the current directory a page at a time,

enter:
dir /p
The licensing log file is named flexnumber.log file, where
number is the process identification number defined by the
operating system. If more than one flexnumber.log file is
present, choose the file with the latest time stamp.
5 To launch the Notepad text editor and display the contents

of the specified log file, enter:
notepad flexnumber.log
The log file reports each license failure for all StudioTools
products, so it can be quite long. For each product
(whether available to you or not), an error message is
logged beginning as follows:
FLEXlm checkout error:

53
6 Find the error message associated with the license you are
investigating, and look at Understanding log file error
messages on page 54 for troubleshooting information.
Ignore other information in the file. If the message isn’t
listed, call our Support Services department.
7 Exit from Notepad.

After you no longer need the licensing log file, you can
delete it by entering:
del flexnumber.log
where number is the number of the file.
8 Close the Command Prompt window.
Understanding log file error messages

When you create a licensing log file as described in the
previous section, you can browse the file to find error
messages to help you identify a problem.
The most common error messages are explained below. If

multiple errors exist, only the first one found is listed in the
log file. In the following explanations, the term license file
refers to the aw.dat file for node-locked licenses, and
aw_servername.dat (on the server) for floating licenses.
Log file error Possible solutions
FLEXLM checkout error: Invalid • Check the license file for a spelling error in the
(inconsistent) license key. password, expiration, or license version.
The license key and data for • If it is a floating license, check to see if the server
the feature do not match. This name and its host ID are entered correctly.
usually happens when a license
file has been altered.
FLEXLM checkout error: Feature • Either the current machine date is later than the
has expired... expiration date or there’s a typing mistake in the
expiration date.

54
FLEXLM checkout error: Invalid • Check the license file’s expiration date for an
date format in license file incorrect format, for example, may-4-2000. The
correct format is 4-may-2000.
• The password may have invalid characters. All
characters should be in hexadecimal format
(numbers or letters A through F).
• The license count digit may be absent. It should
Installing on
be “uncounted” for a node-locked license, and
Windows
Systems
greater than 0 for a floating license.
FLEXLM checkout error: Invalid • Check the entire license file for a typing mistake.
License File syntax.
FLEXLM checkout error: No such • Check the license file’s spelling of feature names.
feature exists.
FLEXLM checkout error: Future • Check the license file’s spelling of any part of the
license file format or string HOSTID number.
misspelling in license file. • Make sure that lines ending in “\” are not
incorrectly using “/” instead.
FLEXLM checkout error: No • For a node-locked license, check that the license
SERVER lines in license file. file’s license count is “uncounted”.
FLEXLM checkout error: license • Check the entire license file for a typing mistake.
in file appears to be
corrupted.
FLEXLM checkout error: The • Check that the license file’s Flex ID / host ID and
hostid of this system does not the machine’s actual Flex ID / host ID correspond.
match the hostid specified in See Checking for licensing errors with lmtools on
the license file. page 56 for details.
• Check that your hardware lock is plugged into
the parallel connector correctly. See Hardware
requirements for licensing on page 9.
FLEXLM checkout error: License • Check the license file to see if the feature has
server does not support this expired, the license server has not yet started, or
feature. the version number is incorrect.
• Make sure the USE_SERVER lines on the client
machine are in the right order.
FLEXLM checkout error: Invalid • Run C:\AW\COM\bin\lmtools.exe. Then,
host. click on the System Settings tab and check that the
server name matches the contents of Computer/
Hostname. See Checking for licensing errors with
lmtools on page 56.

55
FLEXLM checkout error: No • Check that sgiawd is spelled correctly in the
server for this feature. DAEMON line (VENDOR line for hardware locks).
feature. the version is wrong.
• Make sure the USE_SERVER lines are in the
right order.
FLEXLM checkout error: Cannot • Check that the server is started.
connect to license server. • Check that the SERVER servername line reflects
the name of the server.
• Check that everything is spelled correctly in the
DAEMON line (VENDOR line for hardware locks).
• Check that the sgiawd path is right. The default
should be C:\aw\COM\etc\sgiawd.exe (where
C: is the drive where StudioTools is installed).
FLEXLM checkout error: Clock • Make sure the time and date on the client and
difference too large between server are correct and synchronized. If the time and
client and server. date of the client differs from the server by more
than a half hour, the client might not be able to get
a license.
Checking for licensing errors with lmtools

Licensing sometimes fails because your licensing software is
using the wrong Flex ID / host ID (or server host ID). To verify
that this is the case, you can use the lmtools program.
For floating licenses only, you can also use the lmtools
program to check for errors not listed in Understanding log file
error messages on page 54.
To check license errors with lmtools

1 From My Computer or Windows NT Explorer, open the
Com\bin directory. By default, the directory is at
C:\Aw\Com\bin (where C: is the drive where StudioTools
is installed).
2 Double-click lmtools.exe.
3 Select Configuration using services. Your license server

should appear in the box below this field.

56
Note If you didn’t install the license file in the default location,
you must specify where it is. Select the Configure Services
tab, enter the license path under Path to the license file field,
and then select Save Service.
4 Look under the System Settings tab to find out which host
Installing on
IDs are used by your system.
Windows
Systems
Use the following table to find out which field to look at,
and what to compare it to in the license file. The license file
can be found at the following default locations:
◆ C:\FLEXlm\aw.dat for node-locked licenses
◆ C:\FLEXlm\aw_servername.dat for floating
licenses
(where C: is the drive where StudioTools is installed and
servername is the name of the license server computer).
For the
The value in... Should match...
security type...
Ethernet The System Setting’s Ethernet The HOSTID value in the license file,
Address field which should look like the following:
HOSTID=00c04f8ef647
Pentium III The System Setting’s CPU ID The HOSTID value in the license file,
CPU ID field which should look like the following:
HOSTID=0000-0AC0-9876-5432-
AAAA-0000
Hard disk serial The System Setting’s Disk The HOSTID value in the license file,
numbers Volume Serial Number field which should look like the following:
HOSTID=DISK_SERIAL_NUM=384ced4f
Hardware lock The System Setting’s FLEXID7 The HOSTID / FLEXID value in the
field, and printed on a sticker license file, which should look like the
on the hardware lock itself following:
HOSTID=FLEXID=7-b2857e57
Note:
if the FLEXID7 field contains the
value “FLEXID=7-0,” the
hardware lock is not plugged
into the parallel connector
correctly.

57
If the value in the system settings doesn’t match the value
in the aw.dat or aw_servername.dat file, either:
◆ You typed in the wrong server name in the aw.dat or
aw_servername.dat file (use Notepad to correct the
number)
◆ You were supplied with the wrong license
information (contact Alias|Wavefront)
To check for additional floating license errors
To customize and view a status report on the floating licenses:

1 Select Configuration using services.
Note If you didn’t install the license file in the default location,
you must specify where it is. Select the Configure Services
tab, enter the license path under Path to the license file field,
and then select Save Service.
2 Click on the Server Status tab.
3 Select Display Everything.
4 Click on the Perform Status Enquiry button.

After a few seconds wait, a lengthy list of status
information appears. In short, the status information
shows whether the license server is up and running, and
whether each feature line in aw_servername.dat has no
errors and the license count is correct.
Examine the following entries in the status information for
troubleshooting in the following steps:
License server status: 7111@servername
License file(s) on servername: C:\FLEXlm\aw_servername.dat:
servername: license server UP (MASTER) v7.0\
Vendor daemon status (on servername):
sgiawd: UP v7.0
(where servername is the name of the license server
computer).

58
5 In the top line, the number 7111 is a fixed number that
represents the TCP port used internally by the licensing
software.
If you see a number other than 7111, make sure that you
intend for that port number to be used. Otherwise, open
the file aw_servername.dat and change the number to 7111.
Installing on
6 In the next line of the status information, check that the
Windows
Systems
correct path to the license file is listed.
Note If you didn’t install the license files in the default location,
pay special attention that the path is correct.
7 The next line of the status information shows the license

server is up. If the license server isn’t up, you’ll see an
error message that begins like this:
lmgrd not running: Cannot connect to license server.
The server (lmgrd) has not been started yet, or the wrong port@host or license
file is being used, or the port or hostname in the license file has been
changed...
◆ Ensure that you have a valid license file with the
correct name.
◆ Keep handy the aw_servername.dat file, the Status
information, and any log file error messages you
examined previously. Call our Support Services
department and provide them with this information.
8 Below the status information is a list of features in the

aw_servername.dat file and whether the clients can
use the features.
An example follows:
Feature usage info:
Users of Studiof: (Total of 3 licenses available)
Users of AutoStudiof: (Total of 3 licenses available)
This example indicates that six licenses are available: three
for Studio (floating) and three for AutoStudio (also
floating).
If aw.dat or aw_servername.dat has a typing error, you’ll
see a message similar to the following:
Feature usage info:
Users of Studiof: (Error: 1 licenses, unsupported by licensed server)
Users of AutoStudiof: Total of 1 licenses available)

59
Check aw.dat or aw_servername.dat for a typing error in
the Studiof FEATURE line.
9 If the preceding procedure doesn’t fix the problem, call

our Support Services department and keep the
information from the preceding two steps handy.

60
In stalling o n UNIX
Installing on IRIX
Installation Workflow ......................................................................64
Overview of Installation ..................................................................65
Installing on
Before You Install.............................................................................69
UNIX
Installing StudioTools with Software Manager...............................74
Installing StudioTools Using inst (Advanced)................................79
Licensing StudioTools ......................................................................82
Preparing to Use StudioTools ..........................................................83
Confirming Installation ...................................................................90
Uninstalling StudioTools.................................................................92
Installation Troubleshooting ............................................................96
For a list of the files installed by StudioTools, see the appendix,

File Structure (UNIX Only) on page 187
Installing on IRIX
63
indicate!

software. See Before You Install on page 69.
2 Install StudioTools. Depending on the installation

procedures at your organization, use either of the
following sections:
◆ Installing StudioTools with Software Manager on page 74
◆ Installing StudioTools Using inst (Advanced) on page 79
3 License StudioTools. See Licensing on UNIX Platforms on

page 119.
4 Set up your user accounts. See Preparing to Use StudioTools

on page 83.

Confirming Installation on page 90.

sections:
● Installation Troubleshooting on page 96
● Troubleshooting Licensing Problems on page 131
Installing on IRIX
64
Overview of Installation
Types of Installation
These installation instructions apply to the following
products:
● StudioTools Studio
● StudioTools AutoStudio
● StudioTools DesignStudio
● StudioTools SurfaceStudio
Installing on
EvalViewer
UNIX
●
During installation you can load selection files to customize

your installation. See the following sections for information on
how to customize your respective product.
Studio, AutoStudio, or DesignStudio 9.5

● Normal (server) installation. This is the default
installation:
Base Software
Core Software and Renderers
Desktop Environment (icons and their catalog, etc.)
Online Documentation
Common Software
Common Utilities
Total disk space: 410 MB
● Client installation. Software Manager installs only the
support software needed to use a copy of the full package
across a network. Refer to Note on Client Installations on
page 67.
Common Utilities
Common Software
● Render-only installation. The Software Manager installs
only the rendering software. You can use render-only
installation to set up a machine as a rendering server for
client machines on the network.
Installing on IRIX
65
Core Software and Renderers
Desktop Environment
Common Utilities
SurfaceStudio 9.5
● Normal (server) installation:
Base Software
Common software
Common utilities
across a network. Refer to Note on Client Installations on
page 67:
Common Utilities
Common Software
EvalViewer 9.5
● Normal (server) installation:
Base Software
across a network. See the following Note on Client
Installations on page 67:
Common Utilities
Common Software
Installing on IRIX
66
Note on Client Installations
If there is a full installation of the StudioTools software on the
network, you have a fast network and NFS, you can act as a
“client” of a “server” running the full package. See Installing
StudioTools on Many Machines at Once on page 80.
For client installations, the server should contain all products

that might be used by any client machine (including Studio,
SurfaceStudio, and EvalViewer).
Optional and Specialized Software
Installing on
In addition to the base installations, you can install the
UNIX
following software:
Open Digital Studio (ODS)
Alias|Wavefront Dispatcher, 4.3.4
A|W StudioTools CourseWare Material (Tutorials)
Total Disk space: 110MB
Follow the instructions under “Installing Optional and

Specialized Software” to install these components.
Open Digital Studio
Consists of OpenAlias, OpenModel, OpenRender, and shared

files.
OpenAlias
allows you to add new functionality to StudioTools
through a plug-in architecture.
OpenModel
allows you to write applications that can read, write, and
modify StudioTools wire files.
OpenRender
allows you to write your own custom shaders, textures,
and lights.
These packages are only useful to programmers. If you will

not be creating custom plug-ins or modifications, you do not
need to install these files.
Installing on IRIX
67
If you install Open Digital Studio, you must also install
StudioTools Common Software, which contains the StudioTools
Common Libraries (N32).
Distributed Rendering
Distributed Rendering Control (DRC) is installed

automatically through Studio for your distributed rendering
needs.
If you would prefer a graphical user interface for controlling

rendering jobs on remote machines, the Dispatcher product is
also available through a separate installation. You do not need
to install Dispatcher if:
● you will not be using StudioTools software on a network
● you will not be sending rendering jobs to remote machines
(such as a rendering engine).
For information, see Installing Dispatcher on page 151.
CourseWare
The StudioTools CourseWare is a set of tutorial files that are

used in conjunction with the Learning StudioTools manual
included with StudioTools 9.5. To install the CourseWare select
the A|W StudioTools CourseWare Material (Tutorials) product
which is a sub-product of the main StudioTools 9.5
distribution. If you are installing SurfaceStudio, its associated
CourseWare will be installed by default.
To move the CourseWare material from the installed area

/usr/aw/alias9.5/CourseWare into your account
~/user_data/CourseWare:
1 Make sure you have installed the CourseWare product
from the Alias |Wavefront CD ROM.
2 Run the script Install_CourseWare from

/usr/aw/alias9.5/bin.
This copies all of the CourseWare material into to your
account.
Installing on IRIX
68
Before You Install
Installation Requirements
Before you install your new Alias|Wavefront software, check
the following:
● Operating system version: you must have IRIX 6.5 or
higher installed. StudioTools 9.5 will not install on
machines with a version of IRIX lower than 6.5.
● If you do not have IRIX 6.5 or higher installed, install it
before installing Alias|Wavefront software. Make sure
Installing on
you install the correct version for your machine.
UNIX
Note Not all hardware configurations are qualified at this time.
Consult the qualification chart in your box for details, or see
go to Additional resources on the Web on page 158 for
information on how to get the most up-to-date qualifications
on the Web.
● You must have 24-bit graphics.
● You must have a hardware Z-buffer except on the Indy or
the Indigo2 XL.
● You must have access to a CD ROM drive to install
StudioTools 9.5.
● If you are installing a license server, you must install the
FLEXlm software (see Installing FLEXlm Software for
License Servers on page 70
● To use the Unigraphics translators:
◆ You must have access to Unigraphics Version 15 or 16
on a networked machine
◆ The environment variables UGII_LICENSE_FILE
and UGII_BASE_DIR must be set.
◆ You must add UGII_ROOT_DIR to the path
$UG_ROOT_DIR
See your Unigraphics documentation for more
information.
Installing on IRIX
69
Before You Install
Space Requirements
● You must have at least 128 MB of memory to run
StudioTools 9.5. We recommend that you have at least 256
MB. Increasing available memory will increase
StudioTools 9.5 performance.
● You must have enough free space on your hard drive:
Base Software 202 MB
Renderers 54 MB
Online Documentation 150 MB
Open Digital Studio 79 MB (optional)
Total 485 MB
● If you need to make room for StudioTools 9.5, you can

remove other software in the “Manage Installed Software”
section of Software Manager.
Installing FLEXlm Software for License Servers

If your organization is large with many users of StudioTools,
you may want to set up a dedicated license server so that users
can have access to floating licenses.
For license servers, you need the FLEXlm license server

software installed.
To check for FLEXlm license server software
First check to see if you already have the needed software

installed. (The software is available as part of the IRIX system
installation, so may be installed already.)
1 Type the following at the command line:
versions | grep flexlm_server
2 Look for a return message similar to the following:

I license_eoe.sw.flexlm_server 09/20/1999
FLEXlm 6.1 Server Software
If you see this message, you already have the FLEXlm
software and do not need to install it.
Installing on IRIX
70
Before You Install
3 If you do not see any message, continue with the
following steps to install the software.
To install FLEXlm server software

1 Log in the license server machine as root.
2 Insert the StudioTools CD ROM into the drive.
3 At the command line, type inst.
4 At the inst> prompt, type:

from /CDROM/dist/FLEX_license_servers/dist
Installing on
(If you are using a remote CD ROM drive, specify its
UNIX
path.)
5 After the README information appears, select option 1,

Run the installation startup script now.
6 At the inst> prompt, type go.

This begins the installation process. When completed, you
should see the following message:
Installations and removals were successful.
7 Type quit to exit from inst.
Additional Information for license servers
● Be sure to do a customized installation of the custom

license server software (see To install a license server on
page 77)
● You must start and stop the server (see Additional Setup for
Floating Licenses on page 125).
● If you are a very large organization that needs access to
license servers all the time, see Redundant Servers on
page 165.
Installing Tablets
To use a Wacom Intuos tablet with any Alias|Wavefront
software, you must first install the tablet drivers that allow the
tablet to be used as an input device. You can find these drivers
Installing on IRIX
71
Before You Install
on your IRIX installation disk or get them from the Wacom
Web site.
Preparing to Install StudioTools
If you are installing to a filesystem other than /usr
To install StudioTools 9.5 in a directory other than /usr/aw/

alias9.5, you must create a soft link (called /usr/aw/
alias9.5) to the new location. Then, when inst starts to
install StudioTools 9.5 to /usr/aw/alias9.5, it follows the
link and installs in the new location.
● For example, to install Studio 9.5 or SurfaceStudio 9.5 to a
filesystem mounted as /v, enter:
mkdir /v/alias9.5
mkdir /usr/aw (if it doesn’t already
exist)
ln -s /v/alias9.5 /usr/aw
● To install EvalViewer 9.5 onto the same filesystem, enter:
mkdir /v/evalviewer9.5
mkdir /usr/aw (if it doesn’t already exist)
ln -s /v/evalviewer9.5 /usr/aw
● You can also install all Alias|Wavefront software onto a
non-default filesystem by making /usr/aw a soft link to
another filesystem. For example:
mkdir /v/aw
ln -s /v/aw /usr
Once you have created these links, any Alias|Wavefront

software installation will be installed to the /v filesystem.
However, if Alias|Wavefront software is currently installed on
your system, you can not create a new /v/aw link.
Note In some cases, if /usr does not have enough space to install
StudioTools, you will get a free space error, even though you
are installing to a different filesystem.
To work around this, type the following into the command
line at the bottom of the Software Manager window (or on
the inst command line):
set override_space_check true
Installing on IRIX
72
Before You Install
(If the command line is not visible in the Software Manager
window, choose it from the Panes menu.)
Make sure you have enough space to install StudioTools on
the new filesystem before using this command, since it
disables automatic space checking.
If you are doing a client installation
You must create a soft link (called /usr/aw) to the /usr/aw/

alias9.5 directory of the server machine.
● For Studio or SurfaceStudio, use the following command:
ln -s hostname:/usr/aw/alias9.5 /usr/aw
Installing on
Where hostname is the name of the machine with the
UNIX
server installation of StudioTools 9.5.
● To install Evalviewer9.5, use the following command:
ln -s hostname:/usr/aw/evalviewer9.5 /usr/aw
Where hostname is the name of the machine with the
server installation of EvalViewer9.5.
For referring to NFS volumes, your site may use a different

syntax, such as
hostname:/usr/aw/alias9.5, or
/nfs/hostname/usr/aw/alias9.5, or
/hostname/usr/aw/alias9.5.
Ask your system administrator about the correct syntax.
Mounting the CD ROM

If your machine does not have a CD ROM drive, you can
install your StudioTools software from a remote CD ROM
drive across the network if you have NFS on both machines.
For information on loading, setting up, and mounting CD

ROM drives, see:
● Your system administrator
● Your SGI workstation manual or the manual for your CD
ROM drive
● SGI Insight online help (available in the Toolchest as
Help > Online Books or through the insight command).
Installing on IRIX
73
Before You Install
Installing StudioTools with
Software Manager
This is the recommended method for installing StudioTools,
unless you are a very experienced IRIX user.
Starting Software Manager
On the local workstation

1 Log in as root.
2 Double-click the CD icon on the desktop.
3 The Software Manager window appears.
Across a network
1 Log in as root.
2 In the Toolchest choose System > Software Manager or in a

shell enter swmgr.
3 Use the IRIX desktop to find the StudioTools dist folder

icon on the remote CD, and then drag it into the “drop
pocket” next to the Available Software text box in the
Software Manager.
Lookup
Drop pocket
or
In the Available Software text box, enter the path to the
StudioTools dist path on the remote CD. For example:
<remotehost>:/CDROM/dist or /<remotehost>/
CDROM/dist (depending on how NFS volumes are
referenced at your site).
Installing on IRIX
74
Installing StudioTools with Software Manager
Do not use File > Browse Directory to find the dist
directory.
Running the Startup Script

1 In the Software Manager, click Lookup. The Installation
Startup Script window appears.
If your workstation has an irregular set-up, you may want
to check the script to make sure it won’t break on your
machine. Click View to read the script. The script does a
large amount of system housekeeping (see Behind the
Scenes on page 77).
Installing on
2 Click Execute in the Installation Startup Script window to
begin the installation.
UNIX
Click Ignore only if you want to quit the installation
completely. Do not click Ignore if you want to install
StudioTools software. Ignoring the script increases the
chance of conflicts during the installation.
Installing StudioTools 9.5
To do a normal (or server) installation

1 To complete the installation, click Start.
Refer to Studio, AutoStudio, or DesignStudio 9.5 on page 65
for a list of the default software installed in a normal (or
server) installation.
To do a SurfaceStudio installation
1 Choose File > Load Selections.
2 Browse to the dist directory on the CD ROM (for

example: /CDROM/dist).
3 Double-click the file name for surfacestudio.sel to

load the selections for a SurfaceStudio install.
This installs only the files necessary to run SurfaceStudio.
4 Read To install optional or specialized software or to explore the

available software on page 77 to install optional or
specialized software, or click Start to install.
Installing on IRIX
75
To do a client installation
2 Browse to the dist directory on the CD ROM (for example:

/CDROM/dist).
3 Double-click alias_client.sel to load the selections

for a client-only install.
4 This will install only the files needed to run a remote copy
of StudioTools 9.5 over the network.
5 Use the instructions below to install optional or

specialized software, or click Start to finish the installation.
To do a render-only installation

3 Double-click the filename for alias_render.sel to

load the selections for a render-only install.
This installs only the files necessary to run the rendering
software.

To do an EvalViewer installation

3 Double-click the filename for evalviewer.sel to load

the selections for a EvalViewer-only installation.
This will install only the files necessary to run EvalViewer.

Installing on IRIX
76
Note If you wish to install both Studio Version 9.5 and Evalviewer
Version 9.5 together, you can do so by loading the
alias.sel file and then going into Custom Installation
and selecting the EvalViewer 9.5 product.
To install optional or specialized software or to explore

the available software
1 Click Customize Installation.
2 To view or hide sub-components of the main products,

click the fold arrow next to the product name.
Installing on
UNIX
Click arrow to open sub-products for installation
Note To get back to the default product selections, either reload

the alias.sel file or click on the Lookup button in Software
Manager to reload the Distribution Area.
To install a license server
If the machine is going to act as a license server only, then you

only need to do a custom installation with the
Alias|Wavefront License Server Software component of the
Common Utilities.
Behind the Scenes

Software Manager automatically does the following:
● Creates /usr/aw (the base location for all
Alias|Wavefront software) if it does not already exist.
Installing on IRIX
77
● Creates/updates the symbolic link from /usr/aw/alias
to the installation location. The default location is /usr/
aw/alias9.5. See File Structure (UNIX Only) on page 187
for a complete list of files.
● Checks for StudioTools common software (a collection of
shared libraries and license related programs used by all
StudioTools software) installed on your system. The
common software is updated to work with the new
version of StudioTools and is also backwardly compatible
to work with older versions of StudioTools.
● Checks whether your site is a pre-keyed licensed site. If
you are a StudioTools customer, you might be listed in this
file. If you are, Software Manager will look for your
licenses here and update your license file (/var/flexlm/
aw.dat).
If your license is not found, you must get one from
Alias|Wavefront. See Licensing StudioTools on page 82.
● Creates symbolic links from some of the files in the
common software area (/usr/aw/COM) to the new
StudioTools software (this is not done for a render-only
installation). Links between the common OpenModel
shared libraries and the StudioTools library directory are
necessary for plugin development.
● Adds StudioTools-related information to IRIX: creates an
Alias|Wavefront software page in the Icon Catalog, adds
Alias|Wavefront file types to the file database (/etc/
magic), and adds imagery for minimized windows.
(Note: different icons are installed depending on whether
you use 4dwm or mwm).
● For the server only, creates a world-writable render
control directory (/usr/aw/alias9.5/
render_control) to allow this installation to be used as
a rendering engine.
If you want a demo account, you must set it up manually

using setupacct. See Preparing to Use StudioTools on page 83.
Installing on IRIX
78
Installing StudioTools Using
inst (Advanced)
We recommend using Software Manager’s graphical user
interface to install the StudioTools 9.5 software. Use inst only
if you are an expert IRIX user.
Starting inst
1 Log in as root.
2 In a shell, type inst.
Installing on
UNIX
3 At the inst> prompt type from and the path to the
StudioTools dist path on the local or remote CD. For
example:
from /CDROM/dist
or
from remotehost:/CDROM/dist
(depending on NFS syntax at your site).
4 After starting inst as described above, you will see the

installation README file. At the end of the README file you
are prompted to run the installation startup script.
Select option 1 to run the startup script, which you must
do for proper installation. The script does a large amount
of system housekeeping. (See Behind the Scenes on
page 77).
Do not choose option 2 to ignore the startup script.
Installing StudioTools 9.5 Using inst
To do a normal (or server) installation
Type go to finish the installation.
To do a client installation
1 Type the following:
admin load /CDROM/dist/alias_client.sel
Installing on IRIX
79
Installing StudioTools Using inst (Advanced)
2 Type list to show the components.

specialized software, or type go to finish the installation.
Products marked with an i are installed.
To do a render-only installation
1 Type the following:
admin load /CDROM/dist/alias_render.sel
2 Type list to show the components.

specialized software, or type go to finish the installation.
Products marked with an i are installed.
To install optional or specialized software
To install SurfaceStudio, type:

admin load /CDROM/dist/surfacestudio.sel
To install other optional or specialized software:

1 Type step to select more software.
2 Each time you press Enter, inst shows another product.

Type i when a product component is displayed to mark it
for installation.
3 When you are done, type go to finish the installation.
Installing StudioTools on Many Machines at

Once
The inst automatic mode is very useful for scripts and batch
installations. However, before using it, make sure that all
prerequisite software is installed, that there is enough disk
space for the installation, and that there are no installation
conflicts.
To install in automatic mode as root type:

/usr/sbin/inst -a -f dist -Vstartup_script:execute
Installing on IRIX
80
where dist is the location of the dist directory (for example:
/CDROM/dist).
Writing a batch script
Automatic mode is best used for installing StudioTools on

many machines at once. Here is a sample workflow to install
StudioTools on multiple machines in batch mode:
1 Generate a file containing the list of hosts on which you
want to install StudioTools, with one hostname per line.
2 Ensure that the StudioTools distribution CD is accessible

from each of the clients. NFS is the preferred method for
Installing on
doing this.
UNIX
3 Make sure that all the machines have the IRIX
prerequisites already installed.
4 If inst detects any missing prerequisites, the program

stops and your script will not work.
5 Create a script that logs into each host and runs this
command:
/usr/sbin/inst -a -fdist -Fdist/alias.sel
-Vstartup_script:execute
6 If you are using node-locked licenses see the Licensing

section to find out how to get all the licenses for your site
at once. Then distribute this file to each machine that has
StudioTools installed.
Tip This script installs with the alias.sel (normal or server)

selection file. You can substitute alias_client.sel or
alias_render.sel to install client or render-only
versions instead.
Installing on IRIX
81
You must go to Licensing on UNIX Platforms on page 119 to
install a license if you are:
product
StudioTools product
or server

If you did not get a message confirming the installation of

your licenses, you need to install a license. Proceed to
Licensing on UNIX Platforms on page 119 before continuing
Installing on IRIX
82
Preparing to Use StudioTools
This section will be completed for the product release.
This section assumes that you have already installed the

StudioTools software. For information, see:
● Overview of Installation on page 65
● Before You Install on page 69
● Installing StudioTools with Software Manager on page 74
Setting up User Accounts and Projects
Installing on
UNIX
The StudioTools software uses a shared location (/usr/aw/
alias9.5) for files that do not change between projects or
users, and individual directories (work areas) for files related
to individual users or projects.
This structure has the following advantages:

● protects key software components from accidental
damage
● allows users to customize their work areas
● allows several users to use the StudioTools software from
protected accounts, without duplicating common files.
The central shared area /usr/aw/alias9.5 should not be

used as a work area.
If you have many users or projects, each user should have his
or her own UNIX account. All users can then have their own
StudioTools work areas. If each job or project is the
responsibility of an individual user, this is sufficient since it
protects each project from accidental changes by other users,
and allows each user to customize the StudioTools
environment for each project.
Setting up an account
To use the StudioTools software, it is recommended that you

first set up your account. StudioTools 9.5 contains a setupacct
script that can be used to verify and update accounts using the
StudioTools software. Setupacct has been modified from
previous versions so that there is no removal or replacement of
Installing on IRIX
83
files at the account level. The following lists the new features
of setupacct as well as changes to StudioTools.
1 Log in using the account you want to set up.
or
Log in as root to set up an account other than your own.
If the account does not exist (in NIS or /etc/passwd)
setupacct creates it.
2 Type /usr/aw/alias9.5/bin/setupacct
When updating existing accounts setupacct will first
check for the existence of the following files:
.4Dwmrc: IRIS Extended Motif Window Manager
resource file used to override the default 4Dwm window
manager settings. This file should contain a line that
disables the third mouse button which is normally used to
post a window menu when the Alt key is pressed.
.4Dwmrc should contain the following line:
! Meta<Btn3Down> window|icon f.post_wmenu
StudioTools requires this setting to allow vertical grid
snapping. The line therefore should be disabled as listed
above. (The “!” symbol indicates that the line is disabled).
.Xresources: There are two lines that are important to
StudioTools:
*positionOnScreen and
4DWm*keyboardFocusPolicy.
*positionOnScreen is used so that when StudioTools is
launched all windows are drawn off screen until
everything is loaded. 4DWm*keyboardFocusPolicy is
used for proper mouse focus and allows you to type
values into text fields without first clicking in the cell.
.Xresources should contain the following lines:
*positionOnScreen: false
4DWm*keyboardFocusPolicy: pointer
.cshrc: Cshell resource file that includes StudioTools
specific environment variables and path settings.
.login: login file that is sourced at login time
.mwmrc: Motif window manager resource file that
contains the same information as .4Dwmrc but is only used
in your account with the motif window manager.
Installing on IRIX
84
If any of these files do not exist you will be prompted to
create each one (.4Dwmrc will only be needed if .mwmrc
does not exist. If .mwmrc does exist, .4Dwmrc will not be
created as it is assumed that you are running under the
Motif Window Manager.)
3 If any of these files currently exist in your account but

contain unsupported settings you will be notified by
setupacct and be given the option for appropriate
changes to be made to each file. This differs from the
previous method where the files were automatically saved
in a backup directory and replaced.
To run the StudioTools shell type the following in a shell:
Installing on
UNIX
/usr/aw/alias9.5/bin/winterm_alias9.5
or double click on the winterm_alias9.5 icon in the

Alias|Wavefront catalog.
Creating a new work area
Once your account is set up to use the StudioTools software,

decide where the StudioTools software will put your output
files (the work area).
If you want your output files saved to a user_data directory

in your home directory ($HOME), you do not need to change
anything: setupacct has already set this as your default
work area.
If you want your output files saved to a user_data directory

in a directory other than your home (such as a subdirectory or
another directory entirely):
1 Load your shell startup file (~/.cshrc) into a text editor.
2 Find the line reading:

setenv ALIAS_WORKENV $HOME
3 Replace the text $HOME with the path of your work area
directory.
4 Log out and log in again for the change to take effect, or
type:
source ~/.cshrc
Installing on IRIX
85
5 If the work area you just specified does not exist yet, create
it by typing:
mkdir -p $ALIAS_WORKENV
If your work area directory does not contain a user_data

sub-directory when StudioTools starts up, StudioTools will ask
if you want to create it. StudioTools requires that the
user_data directory exists.
Creating a new project directory
For information, see Basic To create a new project directory in you work area, choose File
Tools. > New Project in StudioTools.
Setting up Multiple Users on One Project

If two users are collaborating on a project, you can place the
project in one of their work areas, and use the IRIX chmod
command:
chmod -R g+rw user_data/project
to give other users in the same UNIX group permission to read

and write the files in that project. Edit the .cshrc file to
change umask 022 to umask 002. This ensures that new
files created are also writable by members of your group.
If you have a project that you want protected from alteration

by other users, use this command:
chmod -R go-w user_data/project
This removes write permission for group members and other

users; only the owner may then create or modify files in this
project. Edit the .cshrc file to change umask 002 to umask
022 (if you changed it earlier).
Note Other users may still read the files in your work area. See the
IRIX chmod manual page for more details.
If you work on many projects for many clients, you may want
to set up a shared, global area for project data. For example,
you might create the following structure:
Installing on IRIX
86
/usr/jobs/
/client1/
/user_data/
/project1/
/project2/
...
/client2/
/user_data/
/project1/
/project2/
...
Setting up an Account for Remote Rendering
Installing on
UNIX
Note This section assumes that your site has a machine dedicated
to rendering (a “rendering engine”), and you have already
installed the StudioTools Render Software on that system.
To set up an account able to render on a remote rendering

engine:
1 You need accounts on your local workstation and on the
remote rendering engine. These accounts should have the
same user ID and group ID numbers, and must have the
same username. Both machines must have NFS.
2 Make sure the rendering engine has a world-writable

directory called /usr/aw/alias9.5/
render_control.
3 You can run the setupacct script to verify that the

accounts are set up correctly. You can also create accounts
using this script when it is invoked as root.
4 Log in to your account on the local workstation and run

StudioTools. You will need to change some StudioTools
preferences to allow remote rendering.
Installing on IRIX
87
5 In StudioTools, choose Preferences > Edit Alias preferences.
The following window is displayed:
6 Open the Render Options section. In the Render machine text

field, type the host name of the rendering engine.
7 In the Render location field, type the name of the project

directory in which finished pix, mask and SDL files will be
placed by the remote renderer.
For example, if you enter user_data/demo, the files will
be placed in the following directories:
◆ user_data/demo/pix
◆ user_data/demo/mask
◆ user_data/demo/sdl
If the Render location does not start with a slash (/), it is
assumed to begin at your home directory on the rendering
engine. For example, user_data/demo would become
~/user_data/demo.
Important: these directories must exist on the rendering
engine, or the render will fail.
8 To perform a remote render, choose Render > Render-❐,

and turn the Remote option box on. Then choose Render >
Render to render on the remote rendering engine.
The rendering job runs on the remote machine. You can view
the progress of the remote render with Render > Show render.
Installing on IRIX
88
Once the rendering job is complete, the pix file is moved from
the remote rendering engine to the project’s pix directory on
the local workstation.
Installing on
UNIX
Installing on IRIX
89
only start it:
● From a shell, use the Alias command.
● Alternatively, if you created a shortcut to StudioTools

when prompted during installation, double-click the
StudioTools icon on your desktop.

main window of StudioTools appears within ten seconds. It
has a central working area and groups of icons at the left side
and bottom. You might need to turn the latter on by selecting
Windows > Palette and Windows > Shelves in Studio.

Launcher appears:
Select a product that has available licenses listed beside it, and
then select Launch. If you see the main StudioTools window as
Installing on IRIX
90
in the description above for node-locked licenses, StudioTools
is installed.

following sections for troubleshooting:
● Licensing on UNIX Platforms on page 119 (including
Troubleshooting Licensing Problems on page 131), if you
suspect there is a licensing problem.
● Installation Troubleshooting on page 96
Installing on
UNIX
Installing on IRIX
91
Alias|Wavefront products are designed so that more that one
version of a product can co-exist on the same system. This
allows our customers to install and try newer versions of our
software without risking impact to their production schedules.
At some point, you will want to remove your older version of

software.
For example, after you are ready to switch to using

StudioTools 9.5 and you decide that you no longer need
StudioTools 9.0, follow the procedure outlined below to
remove StudioTools 9.0.
Note In most cases, you may not be able to remove all the
software that you originally installed with StudioTools 9.0
because some of it may be needed by other Alias|Wavefront
applications. You will know when other Alias|Wavefront
software requires software that you try to remove, because
you will get conflicts. Unless you are prepared to remove all
of the Alias|Wavefront software from your system you will
be unable to remove the awcommon, license_eoe and
in some cases alias9_0_common software.
Removing Studio 9.0

To remove your old StudioTools 9.0 software:
1 Log in as root.
2 Start Software Manager.
3 Click on Manage Installed Software.
4 Select any StudioTools 9.0 software that you wish to

remove.
Product Names for StudioTools 9.0
Long Product Name - Default Software Short Product Name

Alias|Wavefront Alias 9.0 alias9_0
Installing on IRIX
92
A|W Alias Online Documentation alias9_0.docs
A|W Alias Online Documentation alias9_0.docs.base
A|W Alias Optional Plugins alias9_0.plugin
Alias|Wavefront Alias Software alias9_0.sw
A|W Alias Base Software alias9_0.sw.base
A|W Alias Desktop Environment alias9_0.sw.desktop
A|W Alias Core Software and Renderers alias9_0.sw.render
Alias|Wavefront Alias, Common Software 9.0 alias9_0_common
A|W Alias, Common Software alias9_0_common.sw
Installing on
A|W Alias Common Libraries alias9_0_common.sw.lib
UNIX
Alias|Wavefront Common Utilities, 3.1 awcommon
Alias|Wavefront Awxfiles, 1.4.1 awxfiles
A|W Awxfiles 1.4 for Alias9.0/Explore4.3.4 awxfiles.sw.base1_4
A|W Explore Common Export explore4_3_4.common.lib
Long Product Names - Non-default Software Short Product Names

A|W Alias Open Digital Studio Software alias9_0.sw.ods
A|W Studiopaint 4.0 9.0 Compatibility Libraries alias9_0.sw.sp4_0lib
Alias, Common Software (N32bit) alias9_0_common.sw32
A|W Alias Common Libraries (N32) alias9_0_common.sw32.lib
Alias|Wavefront Explore Professional, 4.3.4 explore4_3_4
Alias|Wavefront Dispatcher, 4.3.4 aw_dispatcher
Alias|Wavefront Evalviewer, 9.0 evalviewer9_0
Uninstalling StudioTools 9.0 using the versions Command
Software can be removed by the versions command. If you

wish to remove StudioTools 9.0 using this method do the
following:
Installing on IRIX
93
1 Log in as root.
2 type in a shell: versions remove alias9_0

alias9_0_common aw_dispatcher evalviewer9_0
awcommon awxfiles explore4_3_4 license_eoe
Note This will remove ALL software associated with Alias 9.0. If
you have already installed version 9.5 you will be unable to
remove awcommon and in some cases
alias9_0_common depending on other installed
Alias|Wavefront software. license_eoe is not specific to
Alias|Wavefront applications and may be required by other
non-Alias|Wavefront applications. In this case you will be
unable to remove this product.
Using the versions command on its own will list all

software installed on your system. If there are any
Alias|Wavefront products still installed they will show up.
Uninstalling StudioTools 9.5

The following lists the StudioTools 9.5 software products that
can be removed using the guidelines in this section:
Long Product Names - Default Software Short Product Names

Alias|Wavefront Studio 9.5 alias9_5
A|W Studio Online Documentation alias9_5.docs
A|W Studio Online Documentation alias9_5.docs.base
A|W Studio Optional Plugins alias9_5.plugin
Alias|Wavefront Studio Software alias9_5.sw
A|W Studio Base Software alias9_5.sw.base
A|W Studio Desktop Environment alias9_5.sw.desktop
A|W Studio Core Software and Renderers alias9_5.sw.render
Alias|Wavefront StudioTools, Common Software 9.5 alias9_5_common
A|W StudioTools, Common Software alias9_5_common.sw
A|W StudioTools, Common Software (N32bit) alias9.5_common.sw32
A|W StudioTools, Common Software (N32) alias9.5_common.sw32.lib
Installing on IRIX
94
A|W StudioTools Common Libraries alias9_5_common.sw.lib
Alias|Wavefront Common Utilities, 4.3 awcommon
A|W Common Software awcommon.sw
A|W Common Software awcommon.sw.base
A|W Common Desktop environment awcommon.sw.desktop
Long Product Names - Non-default Software Short Product Names

A|W Studio Open Digital Studio Software alias9_5.sw.ods
Installing on
UNIX
A|W Studio CourseWare Material (Tutorials) alias9_5.courseware
Alias|Wavefront Evalviewer, 9.5 evalviewer9_5
A|W License Server Software awcommon.sw.server
Uninstalling StudioTools 9.5 using the versions

command:
To uninstall StudioTools 9.5 using the versions command do

the following:
1 Log in as root.
2 Type in a shell:
versions remove alias9_5 alias9_5_common
evalviewer9_5 awcommon
Note This removes ALL software associated with StudioTools 9.5.

If you still have StudioTools 9.0 installed you will be unable
to remove awcommon and in some cases
alias9_5_common depending on other installed
Alias|Wavefront software. In this case you will be unable to
remove this product. If you installed SurfaceStudio 9.5 you
will need to remove the surfacestudio9_5 product instead of
alias9_5.
Using the versions command by itself lists all software

installed on your system. If there are any Alias|Wavefront
products still installed they will show up.
Installing on IRIX
95
Installation Troubleshooting
Common Problems and Solutions
Problem Possible Cause Solution
I’ve become lost in the Click Lookup in the Software Manager

installation procedure window to reload the dist file. Begin the
installation again from the start.
An “Alias|Wavefront You may be missing Follow the instructions given in the
Installation Error” prerequisite IRIX window before continuing with
window appears. software. installation.
Software Manager does Software Manager is Delete or rename /var/inst/
not act like the very customizable. A .swmgrrc. Software Manager will
instructions say it should. site manager may have revert to its default behavior.
changed its behavior.
Software Manager reports There are many To help prevent software conflicts:
a conflict. possible causes of • Do not click Cancel in the Installation
software conflicts. Software Script window.
Click the Conflict • Do not click the Default Installation
button to get more button in the Software Manager window.
details.
Software Manager tells A bug in Software The following work-around disables the
me I don’t have enough Manager. space-checking function. Make sure you
space on /usr even have enough room in the filesystem to
though I’m installing to a hold StudioTools before proceeding:
different filesystem. • From the Panes menu, choose
Command. Type the following in the
command line:
set override_space_check true
Installing on IRIX
96
Problem Possible Cause Solution
I get errors when I try to Common software is See Checking Common Software on
license or run my not installed. page 97.
StudioTools software.
Your account has not Set up the account with the setupacct
been properly set up. command. See Setting up User Accounts
and Projects on page 83.
Your license file is not See Troubleshooting Licensing Problems on
present, incorrect or page 131.
corrupt.
How do I remove Always use Software Manager or inst to
StudioTools? remove StudioTools files.
Installing on
If you are using Software Manager, click
UNIX
Manage Installed Software, select
Alias|Wavefront StudioTools, then click
Start.
Checking Common Software

From a Unix Shell, enter the command:
versions awcommon
The output from this command should read as follows:

I = Installed, R = Removed
Name Date Description
I awcommon 02/04/2000 Alias|Wavefront Common Utilities, 4.3

I awcommon.sw 02/04/2000 A|W Common Software
I awcommon.sw.base 02/04/2000 A|W Common Software
I awcommon.sw.desktop 02/04/2000 A|W Common Desktop environment
I awcommon.sw.server 02/04/2000 A|W License Server Software
● The output must show a capital “I”, which means the

software is installed.
● To use StudioTools 9.5, Version 4.3 or higher of the
Common Utilities must be installed.
● You need the Alias|Wavefront License Server Software if
you intend the machine to be used as a license server. This
is not installed by default.
Installing on IRIX
97
If the versions awcommon command indicates that you do
not have this subsystem installed then the Install procedure
did not complete successfully. Try reinstalling the awcommon
software from the StudioTools 9.5 installation CD.
Verification of other common subsystems
There are additional software subsystems that will cause

problems if they are missing.
From a Unix Shell, enter the command:

versions alias9_5 alias9_5_common license_eoe
The output should look like the following for each subsystem:
I = Installed, R = Removed
Name Date Description
I alias9_5 02/15/2000 Alias|Wavefront Studio 9.5

I alias9_5.sw 02/15/2000 Alias|Wavefront Studio Software
I alias9_5.sw.base 02/15/2000 A|W Studio Base Software
I alias9_5.sw.desktop 02/15/2000 A|W Studio Desktop Environment
I alias9_5.sw.render 02/15/2000 A|W Studio Core Software and Renderers
I alias9_5_common 02/15/2000
Alias|Wavefront StudioTools, Common
Software 9.5
I alias9_5_common.sw 02/15/2000 A|W StudioTools, Common Software
I alias9_5_common.sw.lib 02/15/2000 A|W StudioTools Common Libraries
I alias9_5_common.sw32 02/15/2000 A|W StudioTools, Common Software (N32bit)
I alias9_5_common.sw32.lib 02/15/2000 A|W StudioTools Common Libraries (N32)
I license_eoe 01/25/2000 License Tools 3.4.2

I license_eoe.books 01/25/2000 IRIS InSight Books, Release 2.2
I license_eoe.books.FLEXlm_EUM 01/25/2000 FLEXlm End User Manual
I license_eoe.man 01/25/2000 License Tools 3.4.2 Manual Pages
I license_eoe.man.flexlm_server 01/25/2000 FLEXlm 6.1 Server Software Manual
Pages
I license_eoe.man.flexlm_utils 01/25/2000 FLEXlm 6.1 Utilities Manual Pages
I license_eoe.man.license_eoe 01/25/2000 License Manager 3.4.2 Manual Pages
I license_eoe.man.relnotes 01/25/2000 License Tools 3.4.2 Release Notes
I license_eoe.sw 01/25/2000 License Tools 3.4.2 Software
I license_eoe.sw.flexlm_server 01/25/2000 FLEXlm 6.1 Server Software
I license_eoe.sw.flexlm_utils 01/25/2000 FLEXlm 6.1 Utilities
I license_eoe.sw.license_eoe 01/25/2000 License Manager 3.4.2 Software
Installing on IRIX
98
The output must show a capital “I” next to each line, which
means the software is installed.
If the versions command indicates that you do not have this

subsystem installed then the Install procedure did not
complete successfully. Try reinstalling the StudioTools
software.
Checking your Licenses

See Troubleshooting Licensing Problems on page 131.
Installing on
Make sure you have an up-to-date license
UNIX
In a shell window, enter
cd /var/flexlm
jot aw.dat
to verify which version is currently installed on your system.
Note If you are using a floating license, the file will be called:
aw_servername.dat, where servername is the host
name of your machine.
The file will be like the following:

FEATURE SurfaceStudio sgiawd 9.500 15-feb-2000 0 \
6CA04021G0553A483410 \
HOSTID=640e2139
The relevant information is the 9.500. This indicates the version

of StudioTools for which you are licensed.
Use FLEXlm tools to check for licensing conflicts
For Alias|Wavefront node-locked licenses, check the license

file by typing:
/usr/sbin/lmdiag -c /var/flexlm/aw.dat <enter>
For Alias|Wavefront floating licenses, add the server name to

the filename:
/usr/sbin/lmdiag -c /var/flexlm/aw_servername.dat
Installing on IRIX
99
awinfo Utility
We have included a utility with Alias 9.5, called awinfo
(/usr/aw/COM/bin/awinfo), to help Alias|Wavefront
Assist and field personnel gather system information from
customer sites.
This utility is designed make it easier for Alias|Wavefront

personnel to debug customer problems. You can run it at any
time to see the output it generates and possibly detect
correctable problems.
By default, awinfo creates an output file in /usr/tmp.
Installing on IRIX
100
Installing on the Solaris
operating environment
Installing on
Installation Workflow ....................................................................102
UNIX
Before You Install...........................................................................103
Installing StudioTools Using Admintool ......................................109
Licensing StudioTools Software..................................................... 113
Setting Up User Accounts and Projects........................................ 114
Confirming Installation ................................................................. 116
Uninstalling StudioTools............................................................... 118
For a list of the files installed by StudioTools, see the appendix,

File Structure (UNIX Only) on page 187.
Installing on the Solaris operating environment

101
indicate!

software. See Before You Install on page 103.
2 Install StudioTools using admintool. See Installing

StudioTools Using Admintool on page 109.
3 License StudioTools. See Licensing on UNIX Platforms on

page 119.
4 Set up your user accounts. See Setting Up User Accounts

and Projects on page 114.

Setting Up User Accounts and Projects on page 114.

section:
● Troubleshooting Licensing Problems on page 131

102
Before You Install
Graphics Configuration
To use StudioTools, you must configure your graphics
hardware to enable expanded visuals, server overlay visuals
and extended overlay visuals. You can do this from the root
user ID with the following commands:
● For Creator 3D graphics:
/usr/sbin/ffbconfig -sov enable -expvis enable -extovl enable
● For Elite 3D graphics:
Installing on
/usr/sbin/afbconfig -sov enable -expvis enable -extovl enable
UNIX
Reboot your machine after making these changes.
These changes will remain in effect for future sessions (until
you explicitly change them again with the ffbconfig or
afbconfig commands).
Note There may be some cases where changing the ffbconfig

or afbconfig settings will cause graphics incompatibilities
with other software. If you have questions about how these
settings may impact your other software, please review the
documentation for that software, or contact its vendor for
more information.
Installation Requirements for StudioTools

Before you install your new Alias|Wavefront software, ensure
that you have the following:
● The Solaris(TM) 7 operating environment must be installed.
● OpenGL 1.2 for Solaris must be installed.
● An Elite3D or Creator3D (FFB2+) graphics card must be
installed.
● The following patches should be installed for Solaris 7:
◆ 107544-03
◆ 106541-05
◆ 106980-07
◆ 107078-18

103
Before You Install
◆ 106147-06
◆ 107465-02
◆ 106147-06
● The following patches should be added before installing
OGL 1.2:
◆ 106148-09 (for Elite3D and Creator3D)
◆ 106144-16 (for Elite3D)
◆ 106145-14 (for Creator3D)
● The following patch should be added after installing
OGL 1.2:
◆ 108131-03 (for OGL 1.2)
● Your CD-ROM drive must be mounted as a filesystem.
If your CD-ROM is not mounted, see your workstation
manual for instructions on how to mount it.
Note Note that StudioTools 9.5 is qualified to run with Solaris 7

and OpenGL 1.2. (See the StudioTools 9.5 qualification chart
in your box, or see Additional resources on the Web on
page 158 for information on getting the most up-to-date
qualification information on the Web.)
Required Solaris system fonts
When you install the Solaris operating environment itself, the

installer allows options that may install only a minimal set of
system fonts. Potentially, StudioTools needs some of the
excluded fonts to run properly.
We recommend that you install all of the following fonts on

your Sun Microsystems workstation.
Solaris operating environment standard font packages:
system SUNWxwfnt X Windows platform

required fonts
Solaris operating environment optional font packages:
system SUNWxwcft X Windows common (not

required) fonts
system SUNWxwoft X Windows optional fonts

104
Before You Install
Space Requirements
To install StudioTools software, you need at least this amount

of free space on your hard drive:
● DesignStudio or StudioTools: 459 MB
● SurfaceStudio: 323 MB
● AutoStudio: 542 MB
● Stand-alone renderer: 150 MB
● EvalViewer: 162 MB
● Both EvalViewer and Studio: 542 MB
Installing on
UNIX
Other Requirements
● To use the Unigraphics translators:
◆ You must have access to Unigraphics Version 15 or 16
on a networked machine
◆ The environment variables UGII_LICENSE_FILE
and UGII_BASE_DIR must be set.
◆ You must add UGII_ROOT_DIR to the path
$UG_ROOT_DIR
See your Unigraphics documentation for more
information.
Preparing to Install
If you are installing to a filesystem other than /usr
To install StudioTools 9.5 in a directory other than /usr/aw/

alias9.5, you must create a soft link (called /usr/aw/
alias9.5) to the new location. The installation program will
follow the link and install in the new location.
● For example, to install StudioTools to a filesystem
mounted as /v, enter:
mkdir /v/alias9.5
mkdir /usr/aw (if it doesn’t already exist)
ln -s /v/alias9.5 /usr/aw
● To install EvalViewer 9.5 onto the same filesystem, enter:

105
Before You Install
mkdir /v/evalviewer9.5
mkdir /usr/aw (if it doesn’t exist
already)
ln -s /v/evalviewer9.5 /usr/aw
● You can also install all Alias|Wavefront software onto a
non-default filesystem by making /usr/aw a soft link to
another filesystem. For example:
mkdir /v/aw
ln -s /v/aw /usr
Once you have created these links, any Alias|Wavefront

software installation will be installed to the /v filesystem.
However, if Alias|Wavefront software is currently installed on
your system, you can not create a new /v/aw link.
If you are doing a client installation
You must create a soft link (called /usr/aw) to the /usr/aw/

alias9.5 directory of the server machine.
● For StudioTools, use the following command:
ln -s nfs_path/usr/aw/alias9.5 /usr/aw
where nfs_path is the path to the NFS-mounted installation
of StudioTools 9.5.
● To install Evalviewer 9.5, use the following command:
ln -s nfs_path/usr/aw/evalviewer9.5 /usr/aw
where nfs_path is the path to the NFS-mounted installation
of EvalViewer9.5.
Your site may use a variety of different syntaxes for referring
to NFS volumes, such as:
● hostname:/usr/aw/alias9.5
● /nfs/hostname/usr/aw/alias9.5
● /hostname/usr/aw/alias9.5.
Consult your system administrator for assistance
Mounting the CD-ROM on a local machine
You need root access to your machine to do the installation.

Ask your system administrator for assistance.

106
Before You Install
If your CD-ROM is already mounted as a filesystem, skip to
the next section.
For information on loading and setting up your CD-ROM

drive, see your workstation manual or the manual for your
CD-ROM drive.
Using a terminal (shell window)

1 Insert the CD-ROM into the CD-ROM drive.
2 Check whether the CD-ROM is already mounted. You can

verify this by entering
Installing on
ls /cdrom/cdrom0
UNIX
If you see the following items, your StudioTools CD-ROM
is mounted:
◆ For Studio:
Studio Alias_gltest.sh installStudio
◆ For SurfaceStudio:
SurfaceStudio Alias_gltest.sh
installSurfaceStudio
If the CD ROM filesystem is not mounted, ask your
system administrator to mount it.
Checking OpenGL
You need to check the version of OpenGL software in the
system where StudioTools will be installed. A script is
supplied on the StudioTools CD-ROM.
Note If you are installing only the stand-alone renderer, OpenGL

is not required.
To verify the version of OpenGL

1 On the StudioTools CD-ROM, use the command:
cd /cdrom/cdrom0
2 Run the script with the command:

./Alias_gltest.sh
If you have the correct version, the script tells you so.

107
Before You Install
If the correct version is missing or has missing files, the
script issues instructions for getting what you need.
3 Once you have the proper version installed, proceed with

the installation.

108
Before You Install
Installing StudioTools Using
Admintool
Start Admintool
To start Admintool on the local workstation:

1 Log in as root.
2 In a shell window, type swmtool.
The Admintool: Software window appears.
Installing on
Important!
UNIX
When installing or removing StudioTools, run swmtool
(Admintool) only with default settings.
In particular, do not change package administration

properties (Admintool > Properties > Package Administration).
Changing these properties could cause an incomplete
installation, or even removal of software packages. In the
worst case, the system’s package database may become
corrupted, making further installation or removal of
software difficult.
Note If you are planning on a dual installation where Version

9.5 will run concurrently with Version 9.0, you may need
to change these settings from their defaults. Refer to the
Release Notes in the Hardware and Operating System section
for details.
Note Symptoms of a corrupted package database include

repeated errors from Admintool informing you that
selected packages cannot be installed or removed. If this
occurs, and only if you are experienced with UNIX
system administration, run pkgchk -f to fix the
package database.

109
Installing StudioTools Using Admintool
Set your Source Medium
To set the CD-ROM as your source medium:

1 In the Edit menu, click Add.
The Set Source Media window appears.
2 Change the Software Location to CD with Volume
Management.
3 Change the CD Path to /cdrom/cdrom0.
4 Click OK in the Set Source Media window. The Add Software
window appears.
5 In the Add Software window, click Alias|Wavefront Studio 9.5,
then click Customize.
6 The Customize Installation window appears with all options
selected. Click Deselect All at the bottom of the window.
Choose your Installation Type

Select your type of installation as specified below.
Note Although the option names might be the same, these actions
install the specific software that you purchased.
To install on a client machine
To do a client installation from the client, click the option box

for Alias|Wavefront Common Software 9.5.
After you have finished selecting software, click the OK button

at the bottom of the Customize Installation window (see the
section called To continue with installing on page 112).
To install on your own machine or a server
To do a normal or server installation, use one of the following

procedures:

110
To install DesignStudio or Studio:
1 Click the option box for Alias|Wavefront Studio 9.5.
To install SurfaceStudio
1 Click the option box for Alias|Wavefront SurfaceStudio 9.5.
To install AutoStudio
1 Click the option boxes for both Alias|Wavefront Studio 9.5
and Alias|Wavefront EvalViewer 9.5.
Installing on
To install only the renderer
UNIX
1 Click the option box for Alias|Wavefront Common Software
9.5.
2 Click the arrow icon to the left of the selection box for
Alias|Wavefront Studio 9.5.
3 Click the option box for A|W Core Software and Renderers.
4 Click the option box for A|W Flexlm License Manager
Software 9.5 and Alias|Wavefront Flexlm License Manager
Utilities.
To install EvalViewer
1 Click the option box for Alias|Wavefront EvalViewer 9.5.
To install both EvalViewer and StudioTools

1 Click the option boxes for both Alias|Wavefront Studio 9.5
and Alias|Wavefront EvalViewer 9.5.
To customize your installation
You can select or deselect items for the installation.For

example, the courseware is installed by default, but can be
removed from the installation.
1 Click on the arrow to the left of Alias|Wavefront Studio 9.5.
2 Click on these items:

◆ A|W Studio CourseWare (Tutorials) (to deselect it)
◆ A|W Studio Open Digital Studio Software (to select it)

111
To install a license server
If the machine is going to act as a license server only, then you

only need to install the license server component of the
software, namely the Alias|Wavefront Standalone FLEXlm
License Manager and Utilities.
To continue with installing
After you have finished selecting or deselecting software:

1 Click the OK button at the bottom of the Customize
Installation window.
2 Click Add at the bottom left of the Add Software window.

A shell opens, listing the files as they are installed, along
with some progress messages. This process can take
several minutes.
Important: During the installation process, you may be
prompted to confirm installation choices:
◆ If questions appear about conflicting files, type Yes.
◆ If questions appear about whether to run scripts as
root or super user, type Yes.
3 After all the files are installed, you are prompted to press
the Return key to continue. Press Enter.
4 When installation is complete, exit from Admintool by
going to the File menu and clicking Exit.

112
Licensing StudioTools Software
You must go to Licensing on UNIX Platforms on page 119 to
install a license if you are
product
StudioTools product
or server
Installing on
UNIX
If the InstallKey.log file (found in your /usr/tmp

directory) indicates that the license installation was not
successful, you need to install a license. Proceed to
Licensing on UNIX Platforms on page 119 before continuing

113
Licensing StudioTools Software
Setting Up User Accounts and
Projects
The StudioTools software uses the following structure:
● a shared location (/usr/aw/alias9.5) for files that do
not change between projects or users
● individual directories (work areas) for files related to
individual users or projects
This structure has the following advantages:

● It protects key software components from accidental
damage.
● It allows users to customize their work areas.
● It allows several users to use the StudioTools software
from protected accounts without duplicating common
files.
The central shared area, /usr/aw/alias9.5, should not be

used as a work area.
If you have many users or projects, each user should have his
or her own UNIX account. All users can then have their own
StudioTools work areas. If each job or project is the
responsibility of an individual user, that protects each project
from accidental changes by other users, and allows each user
to customize the StudioTools environment for each project.
Setting Up an Account
Your account must be set up to work with the StudioTools
software. The directory /usr/aw/alias9.5/bin contains a
script, setupacct, that can verify and update accounts so
that they can use the StudioTools software.
The setupacct command for Solaris operating environment
systems does not remove or replace files.
To set up an account to use StudioTools

1 Log in:
◆ To configure your own account, log in using that
account

114
Setting Up User Accounts and Projects
or
◆ To set up an account other than your own, log in as
root. If the account does not exist (in NIS or in
/etc/passwd), setupacct creates it.
2 Enter the command /usr/aw/alias9.5/bin/

setupacct
Note When logging into a user account, you are presented with
an option to select CDE (Common Desktop Environment) or
Open Windows. Select CDE; StudioTools will only run
properly under CDE.
Installing on
UNIX
EvalViewer Troubleshooting Tip
If EvalViewer will not launch from within StudioTools, make
sure that the EvalViewer executable is in your directory path.
● If you created new accounts with the setupacct script,
this was done automatically.
● If you updated an existing account that already contained
a customized.cshrc file, be sure to add the following
line to your path:
/usr/aw/evalviewer/bin
Log out and log in again for this to take effect.
Note If you don’t want to use setupacct, be sure that the

settings in the .dt directory and the .cshrc and .kshrc
files are incorporated into your existing account. Look at
/usr/aw/alias/etc/acct/skel/ to find sample
configuration files.

115
Setting Up User Accounts and Projects
only start it:
● From a c shell, use the Alias command.
● Alternatively, there is a StudioTools entry on the CDE
toolbar with the runner icon.

main window of StudioTools appears within ten seconds. (If
you are prompted to create user data first, click Yes.)
The window has a central working area and groups of icons at

the left side and bottom. You might need to turn the latter on
by selecting Windows > Palette and Windows > Shelves in Studio.

Launcher appears:
Select a product that has available licenses, and then select

Launch. If you see the main StudioTools window as in the

116
description above for node-locked licenses, StudioTools is
installed.

following section for troubleshooting:
● Licensing on UNIX Platforms on page 119 (including
Troubleshooting Licensing Problems on page 131), if you
suspect there is a licensing problem.
Installing on
UNIX

117
Start Admintool
To start Admintool on your local workstation

1 Log in as root.
2 In a shell, type swmtool.
The Admintool: Software window appears, listing the
software on the system.
Select and Remove Packages

1 In the Admintool: Software window, select the software to
be removed by clicking on its name. Select multiple entries
by holding down the Ctrl key while clicking on the
entries.
To delete StudioTools software, select all lines beginning
with “A|W”.
2 In the Admintool Edit menu, click Delete.

The Admintool: Warning window appears, listing all the
software that you selected.
3 Confirm or halt the deletion:
◆ If you do not want to remove software, click Cancel.
◆ To remove it, click Delete.
If you click Delete, the Admintool: Delete Software
window appears, listing the first piece of software that
you selected and asking if you want to delete it:
The following package is currently installed:
(Lists software package)

Do you want to delete it?
4 If you want to remove the software, type y and press Enter
at each prompt.
The files are listed as they are deleted, along with progress
messages.

118
Licensing on UNIX
Platforms
Installing on
Licensing Overview .......................................................................120
UNIX
Obtaining Licenses ........................................................................122
Licensing StudioTools for UNIX Systems.....................................123
Confirming License Installation ....................................................129
Troubleshooting Licensing Problems .............................................131
Examining a Licensing Log File ....................................................133
Licensing on UNIX Platforms

119
Licensing Overview
You must install a license if you are
product
StudioTools product
or server
Overview
Alias|Wavefront uses FLEXlm technology as part of its license
management system. Although we use much of the standard
FLEXlm setup, we have customized aspects to better suit the
way our products are installed, used, and licensed. For more
information on what license files look like, see Understanding
Licenses on page 160.
Floating versus Node-locked Licenses

StudioTools licenses are available in both node-locked and
floating forms:
● A node-locked license allows you to run your StudioTools
product on one particular system (machine) and only that
system. You must contact Alias|Wavefront if you need to
relocate such a license to a different system.
● A floating license allows anyone on the network to use the
licensed software, on as many machines as you have
purchased licenses for. For example, if you install five
licenses on your network, up to five machines on the
network can run the licensed software at any one time.
You will need to choose one machine on your network to
act as the server for these licenses. All other machines
must be able to connect to and receive their license from
this server.

120
Licensing Overview
Tips
● If you see a line near the top of your license that starts
with the word SERVER, you are installing floating
licenses. Otherwise, you are installing node-locked
licenses
● StudioTools products and options correspond with
FLEXlm license feature names. A table of the feature
names and what they represent can be found in the
appendix, Understanding Licenses on page 160.
Licensing Changes from Previous Versions
Installing on
We have improved our licensing process so that your
UNIX
installations are easier. Note the following changes from
previous versions:
● You can use the same server for all of your StudioTools
floating licenses. For example, you can have both
AutoStudio and SurfaceStudio licenses served from the
same machine.
● A floating license is valid for all supported platforms. For
example, a single license server providing a Studio license
can provide this license to a client operating on IRIX, the
Solaris operating environment, or Windows NT.
● Extra features are available for timed/evaluation licenses;
you are no longer required to remove or update your
permanent licenses in order to evaluate or add temporary
licenses to your servers.
● Client systems no longer need a full copy of or symbolic
link to the server license file.
● Error-prone VENDOR_STRINGs are eliminated, making it
easier to tailor your license for each option, module, or
product you purchase.
● Troubleshooting information is available to help you solve
licensing problems. See Troubleshooting Licensing Problems
on page 131.

121
Licensing Overview
Obtaining Licenses
Typically, licenses have already been sent out to existing users
who are getting upgrades or to new customers who are
working with Alias|Wavefront dealers.
However, if you have not already received a license, you need

to fill out a SPAR (Software Product Authorization Request)
form and send it to Alias|Wavefront.
To fill out a paper SPAR form
A paper SPAR form is included in your StudioTools box. Fill it

out and follow its instructions to fax or mail it in.
To fill out a SPAR form online
You can use an online SPAR form:

1 Double-click the AW_License_Request icon in the
AliasWavefront icon catalog.
2 Click the link to proceed.
3 Make entries for all data boxes in the form.
4 Click Send E-mail at the bottom of the form to send the

form to Alias|Wavefront.
Receiving your License
Upon receiving your SPAR request, Alias|Wavefront sends

you an e-mail copy of the form for your records. After we
process your request, we send you the license information file
you need to install the license. Follow the next section,
Licensing StudioTools for UNIX Systems on page 123, to install it.

122
Obtaining Licenses
Licensing StudioTools for UNIX
Systems
Use this section to install the licensing for your StudioTools
software.
Existing Customers:
If you are a customer on a valid maintenance contract, then
your licenses should have been installed automatically when
you installed StudioTools 9.5 software.
Installing on
To check that the licenses were installed successfully, check
the messages in the InstallKey.log file, found in your
UNIX
/usr/tmp directory. Messages logged there will indicate
whether or not the license installation was successful.
If the licenses were successfully installed:

● If you are using a node-locked license, this completes
licensing for your machine.
● If you are setting up clients and servers with floating
licenses, proceed to Additional Setup for Floating Licenses
on page 125.
● If you are a large organization setting up redundant
servers, proceed to Redundant Servers on page 165 in the
appendix.
If your licenses were not installed successfully, then you must

use the following steps to install your license.
Prerequisites
Before you install licenses, make sure:
● You received your licenses from Alias|Wavefront (See
Obtaining Licenses on page 122.)
● You installed your StudioTools 9.5 software
● You rebooted your machine after installing StudioTools

123
Licensing StudioTools for UNIX Systems
Installing Licenses
The following instructions apply to both node-locked and
floating licenses.
To install licenses from e-mail, fax, or mail

1 You should have already obtained a license from
Alias|Wavefront. If not, refer to Obtaining Licenses on
page 122.
For an example of what the license should look like, refer
to Understanding Licenses on page 160.
2 Save the e-mail you received from Alias|Wavefront to a

file with the following name:
/usr/tmp/license.txt
You can leave the e-mail header information in the file.
If you received the license by fax or mail, carefully type
the license (using an ASCII editor like jot, vi, or dtpad)
directly into the license.txt file. Use upper and
lowercase letters exactly as provided. (The license won’t
work if you make a typing error.)
3 Log in as root
4 Change to the directory: /usr/aw/COM/bin
5 Type the following command: ./installKey

This will open up a License Installer window.
6 Make sure File is encrypted is turned off.
7 In the Input File text box, enter the path and file name of the
text file you created in the preceding steps.
8 By default, the license is installed into:

◆ /var/flexlm/aw.dat for node-locked licenses
◆ /var/flexlm/aw_servername.dat (where
server is the name of the license server) for floating
licenses.
(If you already have license files from Alias|Wavefront,
they will not be touched by this procedure. New
information is appended to the license files.)

124
Note If your organization uses a non-default filename or location
for license files, you can specify a different path and file
name by clicking on the Advanced button.
If you use non-standard locations for your license files, you
must already have set up FLEX licensing to handle this, or
your StudioTools licensing will fail.
9 Click Install.
The Alias | Wavefront License Installer installs the license
into the default Alias | Wavefront license file on your
computer (unless you specified a different location using
Installing on
the Advanced option). It also converts to comments
redundant license information that is superseded by the
UNIX
new license.
10 If you were informed that the license installation was

successful:
◆ For a node-locked license was installed, this completes
the licensing for your machine.
◆ For a floating license, continue with Additional Setup
for Floating Licenses on page 125.
If the license installation did not proceed correctly:
◆ If you received an error message, look at the log file in
/usr/tmp called InstallKey.log for more
detailed information.
◆ See Troubleshooting Licensing Problems on page 131 for
more information.
Additional Setup for Floating Licenses

To install floating licenses, you must also start the license
server process, then set up each client computer that obtains a
floating license from the server.
Note Every time you install a new license, or change a license,

you need to stop and start the license server so that your
licensing changes are replicated to all clients.

125
To stop and start the license server on UNIX
1 Log in as root if you have not already done so.
2 For IRIX, enter the following command:

/etc/chkconfig -f aw_flexlm on
(For the Solaris operating environment, this script is
automatically enabled so you don’t need to do anything.)
3 Stop the lmgrd daemon by entering the following

command:
/etc/init.d/aw_flexlm stop
◆ If the server was ON previously, the command issues
some status information. An example of this status
information is (where servername is the name of the
server machine):
lmdown - Copyright (C) 1989-1997 Globetrotter Software, Inc.
Shut down FLEXlm server on node servername 1 FLEXlm License Server shut down
◆ If the server is already OFF, you can ignore the
corresponding error message, which looks similar to
the following example (where servername is the name
of the server machine):
lmdown - Copyright (C) 1989-1997 Globetrotter Software, Inc.
Connection to "servername" failed: Cannot connect to license server(-15,12:146)
Connection refused
4 Start the server by entering the following command:

/etc/init.d/aw_flexlm start
If the server starts successfully, the status message should
look similar to this:
License file = /var/flexlm/aw_servername.dat
FLEXlm Licensing daemon for Alias|Wavefront software: /usr/etc/lmgrd
5 Log out of root.
6 You can now start StudioTools by selecting its icon, or

typing Alias at the prompt.
To set up each client machine
Client machines can be running on any supported platform:

Windows NT, Windows 2000, IRIX, or the Solaris operating
environment.

126
They should all have Version 9.5 of StudioTools installed. (To
run previous versions concurrently, see the note at the end of
this section.)
Perform the following steps on each client machine.

1 Make sure the license server is accessible to the client
through a TCP/IP network.
2 Edit the aw_servername.dat file (where servername

is the name of the license server computer) using a text
editor:
◆ For Windows NT clients, choose Start > Run. In the
Open field, type the following:
Installing on
notepad c:\FLEXlm\aw_servername.dat
UNIX
◆ For UNIX clients, use a text editor such as vi to edit
the /var/flexlm/aw_servername.dat file.
If the file does not exist, be sure to confirm its creation if
prompted.
3 Confirm the following lines exist in the

aw_servername.dat file:
SERVER servername hostid 7111
USE_SERVER
where
◆ servername is the name of the license server
computer
◆ hostid is the host ID. For hardware locks on
Windows NT, this value will be the ID of the hardware
lock on the server machine instead, and look like the
following: FLEXID=flexid, where flexid is the ID.
It is important that the lines are in the right order, and
that there is a carriage return at the end of the
USE_SERVER line.
If these lines don’t exist in the file, you must type them in
as per the e-mail, fax, or letter you were sent.
Notes:
◆ The USE_SERVER and SERVER lines in each client
computer’s aw_servername.dat file tell the client
which computer serves the licenses. This file is called
a license file, though it simply points to the server

127
computer containing the aw_servername.dat file
that actually includes the license features available to
users.
◆ If you received your StudioTools license by e-mail,
you can simply copy the entire SERVER line from the
e-mail into the text editor, and then replace the
servername entry with your actual license server
computer name. Use upper- and lowercase letters
exactly as shown. The license won’t work if you make
a typing error.
4 Save the file.
5 Close the text editor.
6 If the client is UNIX-based, ensure that there are no DOS

control characters in the license file. You can remove them
by typing the following command in a UNIX shell (from
the directory where you stored the temporary file):
For IRIX, use the command:
to_unix aw_servername.dat
For the Solaris operating environment, use the command:
dos2unix -ascii aw_servername.dat /var/tmp/aw_servername.dat
(For the Solaris operating environment, you need to create
another file. After making appropriate backups, replace
the version of aw_servername.dat in /var/flexlm
with the one you just created in /tmp.)
You should be able to launch StudioTools from any client

machines you set up.
Note These instructions apply to customers running all clients at

Version 9.5 or higher. To run previous versions of the
StudioTools software concurrently on some UNIX client
machines, you must use the previous client setup method
for those machines: copy or mount the license file
/var/flexlm/aw_servername.dat to the machines, and
ensure that license file permissions are set to be readable by
everyone.
Next Steps
You’ve now completed the procedure for floating licenses. In

the next section, you will confirm the installation.

128
To confirm you installed StudioTools licensing
1 Launch StudioTools:
◆ Issue the command Alias.
◆ If you created a shortcut to StudioTools when
prompted during installation, double-click the
shortcut icon on your desktop.
2 If you have a node-locked license, the StudioTools main

window should appear, ready for use. If you are prompted
Installing on
to set up user accounts, exit from the program and see the
UNIX
following sections:
◆ For IRIX: Preparing to Use StudioTools on page 83
◆ For the Solaris operating environment: Setting Up User
Accounts and Projects on page 114
If there is a problem with your license or if you have a
floating license with more than one product available, the
Application Launcher appears:

129
If this window indicates that there are 0 licenses available
for your products, you might have a licensing problem.
See Troubleshooting Licensing Problems on page 131.
If it indicates that you do have licenses available, proceed
to setting up your accounts (as mentioned above).

130
Troubleshooting Licensing
Problems
This section provides troubleshooting tips for StudioTools
installation and licensing.
During installation, the installation program displays error

messages in response to problems. After installation, if you
start StudioTools and the Application Launcher or another
warning window reports a licensing problem, use this section
to find out why.
Installing on
If you still have licensing problems after completing this
UNIX
section, see the appendix on how to contact our Support
Services department (see Getting Help and More Information on
page 156).
Application Launcher Problems
Possible Solutions
Problem
I start StudioTools, but an • Ensure that you have a valid license installed in either
Application Launcher /var/flexlm/aw.dat or
window appears indicating /var/flexlm/aw_servername.dat.
that it cannot find a valid (See Licensing StudioTools for UNIX Systems on page 123.)
license. • Ensure that the license server is running.
• Check your license file for typing errors.
I can start StudioTools from • Ensure that the ALIAS_LICENSE variable is not defined
the Application Launcher, but (see the appendix of the Release Notes for details).
I get a license error if I try to • It is possible that the product you initially set as your
directly run the Alias default product is no longer available. Select another product
executable. in the Application Launcher and click on Save to save that
product as your default setting.

131
Troubleshooting Licensing Problems
Possible Solutions
Problem
The Application Launcher • All product licenses have been checked out. You cannot
window appears with every run any StudioTools products until a license becomes
product name grayed out. available. (Click on the Retry button occasionally to see
whether a license is available yet.)
I run the appLaunch • If there is only one product available in your license, that
(Application Launcher) product automatically starts. You should see the Application
command, but Studio starts Launcher only if there is a licensing problem or if there is
without showing the more than one StudioTools product available in the license
Application Launcher. file.
Error Messages
No valid license
If you feel you have already installed a valid license, but

continue to receive the following message:
No valid license.
Please use installKey to install your license.
Proceed with the following steps:

1 If you tried to run StudioTools on a client or server, make
sure the time and date on the client and server are correct
and synchronized. If the time and date of the client differs
from the server by more than a half hour, the client might
not be able to get a license.
2 Review the licensing procedure to make sure you

completed all the steps.
Cannot find aw.dat (or aw_servername.dat) files

1 Verify that the /var/flexlm directory contains the file
aw.dat or aw_servername.dat.
2 If this file doesn’t exist, you probably did not do the steps
required in Licensing StudioTools for UNIX Systems on
page 123. You’ll need to reinstall licenses.

132
Troubleshooting Licensing Problems
If you following the steps in the previous section but still have
trouble with licensing, you may want to create and examine a
licensing log file to learn more about the error:
For a node-locked license, do the following steps on the

computer where the message appears. For a floating license,
do the following steps on the license server machine.
To examine the license error log file

1 In a UNIX C shell (csh), enter:
Installing on
setenv FLEXLM_DIAGNOSTICS 2
UNIX
2 Type Alias to repeat the attempt to start StudioTools. The
diagnostic information will be printed on the screen.
3 The FLEXlm checkout error message always refers to the

FEATURE below it. So the format is:
1. FLEXlm checkout error.
2. License file being used.
3. FEATURE line under the question.
4 Find the message in the following topic, Understanding log

file error messages on page 133 and follow the instructions.
Ignore other information in the file. If the message isn’t
listed, call our Support Services department.
Understanding log file error messages

Error messages within the file help you identify the problem.
The most common error messages are explained below. If
multiple errors exist, only the first one found is listed in the
log file. In the following explanations, license file refers to the
aw.dat file for node-locked licenses, and aw_servername.dat
(on the server) for floating licenses.

133
Error Possible solutions
FLEXLM checkout error: Invalid • Check the license file for a spelling error in the
(inconsistent) license key. password, expiration, or license version.
The license key and data for • If it is a floating license, check to see if the server
the feature do not match. This name and its host ID are entered correctly.
usually happens when a license
file has been altered.
FLEXLM checkout error: Feature • Either the current machine date is later than the
has expired... expiration date or there’s a typing mistake in the
expiration date.
FLEXLM checkout error: Invalid • Check the license file’s expiration date for an
date format in license file incorrect format, for example, may-4-2000. The
correct format is 4-may-2000.
• The password may have invalid characters. All
characters should be in hexadecimal format
(numbers or letters A through F).
• The license count digit may be absent. It should
be “uncounted” for a node-locked license, and
greater than 0 for a floating license.
FLEXLM checkout error: Invalid • Check the entire license file for a typing mistake.
License File syntax.
FLEXLM checkout error: No such • Check the license file’s spelling of feature lines.
feature exists.
FLEXLM checkout error: Future • Check the license file’s spelling of any part of the
license file format or string HOSTID number.
misspelling in license file. • Make sure that lines ending in “\” are not
incorrectly using “/” instead.
FLEXLM checkout error: No • For a node-locked license, check that the license
SERVER lines in license file. file’s License Count is 0.
FLEXLM checkout error: • Check the entire license file for a typing mistake.
license in file appears to be
corrupted.
FLEXLM checkout error: Invalid • Check that the machine possesses the right
host. HOSTID number with the lmhostid command
(see lmhostid on page 135)
• Check that the HOSTID is correct and not
misspelled.
FLEXLM checkout error: No • sgiawd in the DAEMON line may be spelled
server for this feature. incorrectly.

134
feature. the version is higher than the highest supported
version.
• Make sure that the USE_SERVER lines in the
client’s license file are in the right order.
FLEXLM checkout error: Cannot • Server has not been started.
connect to license server. • SERVER servername has not been changed to
reflect the name of the server.
• DAEMON is not spelled correctly.
• The sgiawd path is not right. The default
should be: /usr/aw/COM/etc/sgiawd
• Make sure that the USE_SERVER lines in the
Installing on
client’s license file are in the right order.
UNIX
FLEXLM checkout error: Clock • Make sure the time and date on the client and
difference too large between server are correct and synchronized. If the time and
client and server. date of the client differs from the server by more
than a half hour, the client might not be able to get
a license.
Other licensing diagnostic tools
lmhostid
The lmhostid tool prints to screen the host ID for the current
machine. You can find this tool in the following paths:
● On IRIX:
/usr/sbin/lmhostid
● On the Solaris operating environment:
/usr/aw/COM/bin/lmhostid
The value displayed by lmhostid should correspond to the

host ID in the aw.dat or aw_servername.dat licensing
file. If the values do not match, make sure that a typing
mistake was not made in the licensing file.
lmdiag
The lmdiag tool diagnoses problems when a license checkout

fails. You can use this tool for node-locked or floating licenses.

135
This tool first prints information about the license. It then
attempts to check out each license. If the checkout is
successful, it notifies you; if not, it gives the reasons why the
checkout failed.
You can find lmdiag in the following paths:

● On IRIX:
/usr/sbin/lmdiag
/usr/aw/COM/bin/lmdiag
The format of lmdiag is:

lmdiag -n -c /var/flexlm/LicenseFile FeatureName
where:
-n Runs lmdiag in non-interactive mode.

-c LicenseFile Specifies the license file to diagnose.
FeatureName Specifies which feature to diagnose. If you
do not specify a feature name, lmdiag
diagnoses all features in the file.
lmstat
The lmstat tool reports the status of the license manager

daemons and feature usage. It is only useful for checking
floating license errors, and must be run on the license server
machine.
For floating licenses, lmstat provides information about the

status of the server nodes, FEATURES and users of each
FEATURE.
You can find lmstat in the following paths:

● On IRIX:
/usr/sbin/lmstat
/usr/aw/COM/bin/lmstat
The format of lmstat is:

lmstat -a -c /var/flexlm/aw_servername.dat -f FeatureName

136
where:
-a Displays everything. Be prepared for a lot

of information if there are a lot of active
users.
-c license file This ensures that you are checking the
diagnostics for the correct license file.
-f FeatureName This confines the inquiries to a particular
feature or features.
How to read the output of lmstat
Installing on
UNIX
When running lmstat, a lengthy list of status information
appears. In short, the status information shows whether the
license server is up and running, and whether each feature line
in aw_servername.dat has no errors and the license count is
correct.
Examine the following entries in the status information for

troubleshooting:
lmstat - Copyright (C) 1989-1997 Globetrotter Software, Inc.
Flexible License Manager status on Thu 9/3/1998 10:51
License server status (License file: /var/flexlm/aw_servername.dat):
servername: license server UP (MASTER) V5.11
sgiawd: UP v7.0
(where servername is the name of the server machine).
For the line that starts with License server status:

● Make sure that the correct path to the license file is listed.
● If it is not the correct path, make sure that the license file
exists in the /var/flexlm directory, and make sure that
the name of the server machine is correct.
If you are unsure of the server name, use the following
command:
/usr/bin/uname -n
The next line of status information shows if the license server

is UP. If it is not UP, the following error message appears:

137
License server status (License file: /var/flexlm/aw_servername.dat):
servername: Cannot connect to license server (-15,12:146) Connection refused
sgiawd: Cannot connect to license server (-15,12:146) Connection refused
If you receive this message, follow these steps sequentially:

1 Confirm that the license server is up. See Additional Setup
for Floating Licenses on page 125 for more information.
2 Make sure that all server starts have a corresponding

server stop. You cannot continually restart the server
without stopping any of the previous server starts.
If you have been continually restarting the server, issue
the following command as root user from the UNIX
prompt.
ps -ef | grep lmgrd
If you see any processes containing
aw_servername.dat (where servername is the name of
the server machine), they should be removed using the
kill -9 command against their process ID.
3 Keep handy all of the diagnostic output messages, the

aw_servername.dat file, and the aw_flexlm.log file
(located in /usr/tmp). Call our Support Services
department and provide them with this information.
Below the status information is a list of features in the
aw_servername.dat file and information explaining
whether the clients can use the features. An example
follows:
Feature usage info:
Users of Studiof: (Total of 1 licenses available)
Users of AutoStudiof: (Total of 1 licenses available)
This example indicates that two floating licenses are

available: one Studio and one AutoStudio.
If aw_servername.dat has a typing error, you’ll see a
message similar to the following:
Feature usage info:
Users of Studiof: (Error: 1 licenses, unsupported by licensed server)
Users of AutoStudiof: Total of 1 licenses available)
If this is the case, check the aw_servername.dat for a

typing error in the Studiof FEATURE line.

138
4 If doing the preceding procedure doesn’t fix the problem,
call our Support Services department and keep the
information from the preceding two steps handy.
Installing on
UNIX

139
140
Complementary Software
and Peripherals (IRIX Only)
Installing on
Setting up OCTANE Duo and Dual Display Configurations......142
UNIX
Dial and Button Box......................................................................143
Spaceball ........................................................................................146
Space Mouse ..................................................................................147
SGI Impressario Printer Setup ......................................................150
Installing Dispatcher .....................................................................151
141
Setting up OCTANE Duo and
Dual Display Configurations
● OCTANE Duo Option
Version 9.5 supports OCTANE Duo option. This upgrade
enables one OCTANE workstation to support two users. It
requires special licensing, so please call your local Alias
|Wavefront sales representative.
● OCTANE Dual Display Option
Version 9.5 supports the OCTANE Dual Display
configuration. This upgrade enables a user to display
graphics and text on a second graphics monitor.
To set this option, set the environment variable
ALT_DISPLAY to the OCTANE secondary graphics
display name: (for example, type "setenv
ALT_DISPLAY :0.1").
Once this option has been set, you can move the main
window from the primary monitor to the secondary
monitor and back again, using the Utilities > ChangeScreen
menu. All other windows can be moved from one monitor
to the other by click-dragging on the window’s title bar to
drag the window between the two screens.
Note If the Preferences window only opens on the primary

monitor, move the main window to the primary monitor,
then open the Alias Preferences window from the
Preferences > User options > Alias preferences menu.
Complementary Software and Peripherals (IRIX Only)

142
Setting up OCTANE Duo and Dual Display Configurations
Dial and Button Box
On IRIX systems, the Dial Box is an alternative to the mouse
for the Views functions. It lets you use the Views functions
without interrupting the current function, and without having
to move the mouse from the current position to a pop-up
menu.
The Button Box can be used for hot keys. Use the prefix “BB”
and the button number (for example, BB3 or BB12) as you
would normal keys in the Hotkey editor.
Installing on
Using the Dial Box
UNIX
The dials work in a similar way to the current dolly and track
icons that appear in each window. The Dial Box has eight dials
with one function for view manipulation assigned to each dial.
The input from the dials is interpreted according to your left/
right turning movements. These functions can be used at any
time. Like zoom, track, and tumble icons, they are accessible
even inside other functions.
The following illustration shows the dials numbered from one

to eight:
8
7 8
7
6
5 6
5
4
3 4 3
2
1 2 1

143
Dial and Button Box
All modeling and SBD windows accept input from the dial
box.
To undo a change made with the Dial Box view controls, select
Cameras > Reset view.
The dials on the Dial Box have the following functions:
Dial 1 This is like the Cameras > World Move camera > Track feature where
View Track Horizontal the mouse is moved left and right while you hold down the middle
button.
Rotate the dial counter-clockwise to track the active view to the left
and clockwise to track the active view to the right.
Dial 2 This is like the Cameras > World Move camera > Track feature where
View Track Vertical the mouse is moved up and down while you hold down the right
button.
Rotate the dial counter-clockwise to track the active view to the
bottom, and clockwise to track the active view to the top.
Dial 3 This is like the Cameras > World Move camera > Tumble feature where
View Tumble about the mouse is moved left and right while you hold down the middle
the World Up Axis button.
The tumble function works only in the perspective window, so using
this dial changes the current window to a perspective window.
If there is more than one perspective window, the one with the
highest priority is chosen (priority 2 is higher than priority 3). If the
perspective windows have the same priority, the most-recently
current perspective window is chosen.
Rotate the dial counter-clockwise to revolve the camera clockwise
about the Z axis, and clockwise to revolve the camera counter-
clockwise about the Z axis (in the Z-up coordinate system). If you are
working in the Y-up coordinate system, rotation is about the Y axis.
Dial 4 This is like the Cameras > World Move camera > Tumble feature where
View Tumble Vertical the mouse is moved up and down while you hold down the right
button.
The tumble function works only in a perspective window, so using
this dial changes the current window to a perspective window. For
more than one perspective window, see Dial 3 above.
Rotate the dial to revolve the camera vertically.
Dial 5 This is like the Cameras > World Move camera > Dolly feature.
Dolly View In Rotate the dial counter-clockwise rotation to dolly the active view
out, and clockwise to dolly the active view in.

144
Dial and Button Box
Dial 6 This is like the Cameras > Local Move camera > Twist feature.
View Twist The twist function works only in a perspective window, so using this
dial changes the current window to a perspective window. For more
than one perspective window, see Dial 3 above.
Rotate the dial clockwise to rotate the camera clockwise, and counter-
clockwise to rotate the camera counter-clockwise.
Dial 7 This is like the Cameras > World Move camera > Dolly - ❏ feature, with
Anisotropic View Scaling set to NON PROPORTIONAL, where the mouse is moved
Scale Horizontal left and right while you hold down the middle button.
This operation works only in an orthographic window.
Rotate the dial counter-clockwise to decrease the view scale along the
horizontal axis in the active view, and clockwise to increase the view
scale along the horizontal axis in the active view.
Installing on
UNIX
Dial 8 This is like the Cameras > World Move camera > Dolly - ❏ feature, with
Anisotropic View Scaling set to NON PROPORTIONAL, where the mouse is moved
Scale Vertical up and down while you hold down the right button.
This operation works only in an orthographic window.
Rotate the dial counter-clockwise to decrease the view scale along the
vertical axis in the active view, and clockwise to increase the view
scale along the vertical axis in the active view.

145
Dial and Button Box
Spaceball
On IRIX systems, you can use a spaceball as an alternative to
the mouse for Views functions.
Like the Dial Box, the Spaceball enables you to use the Views
functions without interrupting the current function and
without having to move the mouse from the current position
to another menu.
The Spaceball buttons can also be used for hot keys. Use the
prefix ‘SB’ and the button number (for example, SB2) in the
Hotkey editor.
Using the Spaceball

The Spaceball is an input device with six degrees of freedom,
three for rotation and three for translation (about a side-to-side
horizontal axis). Each degree of freedom is mapped to a
separate viewing function as follows:
● To tumble vertically, rotate the Spaceball toward and away
from you. This is equivalent to using the tumble icon with
the right mouse button pressed.
● To tumble horizontally, rotate the Spaceball as if you were
twisting the lid of a jar open or closed (about a vertical
axis). This is equivalent to using the tumble icon with the
middle mouse button pressed.
● To twist, rotate the Spaceball to the left or the right (about
a horizontal fore-and-aft axis).
● To dolly, move the Spaceball towards and away from you.
This is equivalent to using the dolly icon.
● To track vertically, move the Spaceball up and down. This
is equivalent to using the track icon with the right mouse
button pressed.
● To track horizontally, move the Spaceball left and right.
This is equivalent to using the track icon with the middle
mouse button pressed.

146
Spaceball
Space Mouse
On IRIX systems, the Magellan space mouse, made by
Logitech, can be used to control your view or issue animation
time slider commands.
Toggling between Time and View Modes

You can toggle between View and Time ( jog/shuttle) modes
in two ways:
1 Click the * button on the space mouse
Installing on
2 Click the icon for the space mouse menu at the top right
UNIX
corner of the screen, under the menu bar, to the right of
the mag, grid, and crv buttons. Drag to the mode you want
and release the button.
The space mouse menu appears as follows:
Click here to open menu.
The button changes appearance to indicate the current mode.
If the View mode is selected, the button shows a movie

projector. This is the default space mouse mode, and provides
a tumble/dolly view.
If the Time mode is selected, the button shows a clock.
Note The button for the space mouse menu appears only if a
space mouse device is connected to your machine.
Otherwise the mag, grid, and crv buttons appear flush
against the right edge of the window.
Toggling Modes during Playback
You can toggle modes during playback as follows:

● start playback using the Time Slider.
● push the * button to toggle to View mode (dolly or
tumble).

147
Space Mouse
● select * to toggle back to Time mode.
● stop or reverse play using the space mouse.
Note Tumbling or dollying during playback affects playback

speed, depending on the power of your computer.
Space Mouse Sensitivity Settings

There are separate sensitivity settings and controls for Time
and View modes in the Preferences > Interface options window.
Lower slider values make the device more sensitive and faster.
Software Sensitivity: Acceleration Threshold/Acceleration

Factor
In Time mode, you can adjust the Acceleration threshold and

Acceleration factor in the Interface Options window. These
settings affect the fast forward or reverse playback feel
(Preferences > Interface options).
The Acceleration threshold value determines how much time

is needed during a twist of the cap to switch from single frame
to fast playback mode.
The Acceleration factor value is used to adjust how fast the

playback transitions into maximum playback.
Hardware Sensitivity
You can also adjust the sensitivity settings for the space mouse
in the hardware.
To adjust the translation sensitivity to the next setting, click the

* and 5 buttons simultaneously.
To adjust the rotation sensitivity to the next setting, click the
* and 6 buttons simultaneously.
Tip There are eight possible settings. You will hear a double
beep when you are back at the first, the default, setting.

148
Space Mouse
Time Mode Controls
Jog Forward 1 Frame twist clockwise and release.
Jog Backward 1 Frame twist counter-clockwise and
release.
Next Keyframe tilt to bottom and release.
Previous Keyframe tilt to top and release.
Play Forward tilt to right and release.
Play Backward tilt to left and release.
Stop push down.
Installing on
Fast Forward Playback twist clockwise and hold
UNIX
(progressive acceleration of
playback).
Fast Reverse Playback twist counter-clockwise and hold
(progressive acceleration of
playback).
Rewind (goto frame 1) push to left.
Wind (goto last frame) push to right.
Tip During playback, tap right and then tap left to quickly
change the playback direction.
Note An object must be selected and have some keyframes

assigned for the Next/Previous keyframe command to have
any affect (this is the same as using the time slider).

149
Space Mouse
SGI Impressario Printer Setup
StudioTools software supports SGI’s Impressario application.
Impressario allows printer manufacturers to add SGI support
for their printers. StudioTools uses Impressario to print, tso
hat support is added to StudioTools as well.
Contact your SGI representative for an updated list of printers

supported by Impressario or any other Impressario
information.
Note If you experience problems with printing, ensure that

fromalias and toalias are installed in your usr/sbin
directory. These components are on the IRIX system CD, and
are required for StudioTools peripherals.

150
SGI Impressario Printer Setup
Installing Dispatcher
Note that a complete set of Dispatcher documentation is
available to you online. After you install Dispatcher from its
inst image, a Dispatcher.doc icon is installed in the Find:
Alias/Wavefront toolchest. You can view the Dispatcher
documentation by clicking on this icon.
To install Dispatcher:
1 Log in as root.
2 Choose a machine on which the spooler is to run.
Installing on
3 Note its host name.
UNIX
4 Go to the subdirectory that contains the
dispatcher_install script.
cd /usr/aw/COM/bin
5 Run the installation script dispatcher_install as root

on each machine that you wish to use as a client by
entering:
./dispatcher_install
This script locates the Dispatcher binaries, keeps track of
the machine you are using as your spooler, and sets up a
shell script named dispatcher in the /etc/init.d
directory to control how the Dispatcher is executed. The
dot in the command stands for the working directory in
which you placed yourself at step 4.
To find out whether you have run the
dispatcher_install script or not, type the following
command:
chkconfig
If the Dispatcher client is not set to on in the list of options
that you can set, run dispatcher_install on that
machine.
6 Follow the instructions on the screen (the script shown as

follows includes explanations of what each section of the
script tells the Dispatcher to do).
7 If the automount feature is on, specify the default

pathname /usr/aw/COM/bin. Always express the
pathname relative to the symbolic link of the mount point.

151
For instance, if the directory /usr/aw is automounted
and is a symbolic link to /tmp_mnt/usr/aw, give the
pathname /usr/aw rather than /tmp_mnt/usr/aw.
8 Answer Yes whenever possible, especially to the e-mail

questions, because this makes it easier to troubleshoot any
configuration problems in your scripts or the scripts of
end users.
9 When the installation is complete, enter the following to

start the Dispatcher:
/etc/init.d/dispatcher start
An alternative to this command is to shut down and
restart your machine.
10 As root, log into each client machine (you can also do an

rlogin to each client machine), then enter:
./dispatcher_install
and answer the questions as explained for step 6. Each
time you install a spooler, you must re-install all the
clients. Previously installed clients cannot be used.

152
A pp end ixes
Appendixes
Getting Help and More Information .............................................156
Understanding Licenses ................................................................160
Redundant Servers ........................................................................165
Plotter Installation.........................................................................181
File Structure (UNIX Only) .........................................................187
NFS Overview (UNIX Only)........................................................196
Appendixes
Appendixes
155
Getting Help and More
Information
StudioTools Manuals
The following manuals are available both in print and online.
The online help includes a searchable index of all manuals.
● What’s New: new and improved features in this version.
● Installation: installing and licensing Studio.
● Fundamentals: understanding StudioTools software,
setting it up, starting and stopping it, learning your way
around the software, and customizing and using the
Studio interface.
● Basic Tools
◆ Part 1 — Interface: getting online help, customizing
the interface, opening and saving files, and using the
window layouts to improve your workflow.
◆ Part 2 — General Tools: using the basic StudioTools
tools to create and manipulate models; picking,
deleting, editing, and transforming objects; using
cameras; and doing standard system operations.
(Not available in ● Learning Studio: learning how to use the StudioTools

SurfaceStudio.) design and animation software through tutorials.
(Not available in Studio.) ● Learning SurfaceStudio: learning how to use the surface
engineering tools in SurfaceStudio through tutorials.
● Release Notes: detailed software notes about this release
of the StudioTools software. (The printed version is the
more recent.)
● Sketching: creating conceptual design sketches and
surface or cloud data annotations within StudioTools.
(Sketching tools are available only in StudioTools for
Windows NT.)
● NURBS Modeling: creating and modifying NURBS curves
and surfaces, as well as construction and evaluation tools.
(Not available in ● Polygonal Modeling: creating and modifying polygons

SurfaceStudio.) and polysets.
Appendixes
156
Getting Help and More Information
(Not available in ● Rendering: defining the look of your scene, creating
SurfaceStudio.) special effects, defining how the scene will render, and
creating final rendered images and animations.
(Not available in ● Animating: creating animations, building skeletons,

SurfaceStudio.) bringing creatures to life using inverse kinematics,
generating particles and special effects, and animating by
using time warps.
● Data Transfer for CAD and Solid Imaging: exchanging 3D
model data between StudioTools and CAD packages.
● EvalViewer: a stand-alone utility for industrial design. It
works as both a cloud data tool and a surface evaluation
tool. (EvalViewer is available only in StudioTools for
UNIX.)
The following manuals are provided only online. You can

display them from StudioTools by selecting Help > Online docs.
Parts of these manuals appear when you use Help > Help on
Function. You can also open their PDF files from the
Appendixes
Documentation CD and print them.
● Alias File Formats: descriptions of native Alias file
formats.
● Stand-alone Utilities Guide: utilities that can be run
separately from StudioTools. Includes how to use the
Alias File Batch Translator utility.
(Not available in ● Scene Description Language: the Alias SDL, including

SurfaceStudio.) procedural effects that you can achieve in rendering.
● OpenAlias/OpenModel API: the Alias API, which
provides programmers with access to StudioTools internal
data: OpenModel to Alias wire files and OpenAlias to the
StudioTools application.
(Not available in ● Alias OpenRender: the program interface for Alias

SurfaceStudio.) OpenRender, how the renderer works and how to write
modules to add Alias OpenRender code.
Printing Manuals from Files

Your StudioTools CD ROM contains Adobe Acrobat PDF files
of the manuals. You can print additional copies of your books
or the online-only reference help.
Appendixes
157
You can find the files for this manual in the directory:
aw/studiotools9.5/studio/PDF/InstallNotes.Pdf
Studio Assistant Online

The Assistant Online offers a vast Internet resource, updated
weekly, of valuable learning material. It includes:
● Lessons and finished models that allow you to exercise
modeling, rendering and presentational skills
● Content designed to optimize workflow for visual
presentation.
You can find the Assistant Online at

www.aw.sgi.com/assistant_online/design/studio/
Additional resources on the Web

● www.aliaswavefront.com provides information on various
Alias|Wavefront and StudioTools issues. Its Assistant
Online at http://www.aliaswavefront.com/assistant_online/
design/studio/ provides up-to-date samples, tutorials, and
other helpful information.
● http://www.aliaswavefront.com/pages/home/pages/support/
pages/qualification_charts/index.html provides information on
the latest system qualifications
● www.globetrotter.com provides information on licensing.
Contacting Support Services

If you feel that you’re making no progress while
troubleshooting, contact Alias|Wavefront Support Services
for help.
North America
9:00 a.m. to 8:00 p.m. EST (14:00 to 01:00 GMT):

● Toll-free from U.S. and Canada: 1 877-927-7478
● Toll call: 1 416-365-6959
● E-Mail: hotline@aw.sgi.com
Appendixes
158
Europe
9:00 MET to 18:30 MET (08:00 to 17:30 GMT):

● Toll-free from Germany: 0130-827660
● Toll-free from UK: 0800-7318923
● Toll-free from France: 0800-902295
● Toll-free from Italy: 0167-780809
● All others (toll call): +32 (0) 9 266 12 34
● E-Mail: hotline_esc@aw.sgi.com
Other Locations
For support services in other locations, contact your local

reseller or sales office for information.
Appendixes
Appendixes
159
Understanding Licenses
This section explains the contents of the license(s)
Alias|Wavefront sends you.
Tip If you see a line near the top of your license encryption that
starts with SERVER, you’re installing floating licenses.
Otherwise, you’re installing node-locked licenses.
Node-locked licenses
If you order node-locked licenses, you receive one license for
every machine. The contents of the e-mail, fax, or mail
depends on the StudioTools product you order. The following
figure shows the main elements of a node-locked license:
License License
Feature version count Key
FEATURE Studio sgiawd 9.500 3-mar-2000 uncounted 127529B5D12A \

HOSTID=69079ed3
Host ID Expiration
Feature
The StudioTools product package you purchased. For
details, see License file abbreviations on page 162.
License Version
The version number of the StudioTools product.
Expiration
The date on which the license expires, if this is a product
evaluation license. If this is a permanent license and there
is no expiration date, this field reads “permanent”.
License count
The number of licenses you ordered (in the case of node-
locked licenses, this number is not required, and reads
“uncounted”)
Appendixes
160
Key
An encrypted string that prevents copyright infringement.
Host ID
The host ID of the machine to be licensed.
This ID takes different forms depending on the type of
machine. For example:
◆ HOSTID=69079ed3, for UNIX
◆ HOSTID=00c04f8ef647, for ethernet (MAC) on
Windows NT
◆ HOSTID=0000-0XC0-9876-5432-AAAA-0000, for
Pentium III PCs with active CPU IDs (Windows NT)
◆ HOSTID=FLEXID=7-b2857e57, for hardware locks on
Windows NT
◆ HOSTID=DISK_SERIAL_NUM=123abc4d, for hard
disk evaluation licenses on Windows NT
Appendixes
Floating licenses
If you order floating licenses, you receive a single license for
the license server computer. The contents of the e-mail, fax, or
mail you receive depends on the StudioTools product you
order.
The following figure lists the main elements of the floating

license:
Your server Server Port License

name here Host ID Number Count
SERVER server 00c04f8ef647 7111

DAEMON sgiawd /usr/aw/COM/etc/sgiawd
FEATURE Studiof sgiawd 9.500 3-mar-2000 1 6B45C88303C2
Feature License Expiration Key

Version
Note In the above example, the word DAEMON is replaced by

VENDOR if hardware locks are used.
Appendixes
161
server
A place-holder where you must insert your actual server
name.
Server Host ID
The host ID of the server machine.
This ID takes different forms depending on the type of
server. For example:
◆ 69079ed3, for UNIX
◆ 00c04f8ef647, for ethernet (MAC) on Windows NT
◆ HOSTID=0000-0XC0-9876-5432-AAAA-0000, for
Pentium III PCs with active CPU IDs (Windows NT)
◆ FLEXID=7-b2857e57, for hardware locks
Port Number
A fixed number that represents the TCP port used
internally by the licensing software.
Feature
The StudioTools product package you purchased. For
details, see License file abbreviations on page 162.
License Version
The version number of the StudioTools product.
Expiration
The date on which the license expires, if this is a product
evaluation license. If this is a permanent license and there
is no expiration date, this field reads “Permanent”.
License count
The number of licenses you ordered.
Key
An encrypted string that prevents copyright infringement.
License file abbreviations

The following table describes the product abbreviations in the
license information provided by Alias|Wavefront. This
Appendixes
162
information is helpful when you want to know which
StudioTools product a license provides.
FLEXlm Feature Names
StudioTools Node-locked Floating

Product
Evaluation/ Evaluation/
Permanent Permanent
Time-out Time-out
AutoStudio AutoStudio AutoStudioEval AutoStudiof AutoStudioEvalf
SurfaceStudio SurfaceStudio SurfaceStudioEval SurfaceStudiof SurfaceStudioEvalf
Studio Base Studio StudioEval Studiof StudioEvalf
Studio with StudioADA StudioADAEval StudioADAf StudioADAEvalf
Advanced
Design
Animation
Appendixes
Studio with StudioAE StudioAEEval StudioAEf StudioAEEvalf
Advanced
Evaluation
Studio with StudioAM StudioAMEval StudioAMf StudioAMEvalf
Advanced
Modeling
EvalViewer EvalView EvalViewEval EvalViewf EvalViewEvalf
EvalViewer for EVSurf EVSurfEval EVSurff EVSurfEvalf

SurfaceStudio
EvalViewer EVCloud EVCloudEval EVCloudf EVCloudEvalf

with Cloud
Option
Renderer AliasRender AliasRenderEval AliasRenderf AliasRenderEvalf
Power Renders AliasPowerRender AliasPREval AliasPowerRenderf AliasPREvalf
AliasPowerRender2 AliasPR2Eval AliasPowerRender2f AliasPR2Evalf
I-DEAS Direct IDC IDCEval IDCf IDCEvalf
Connect
Unigraphic UgDC UgDCEval UgDCf UgDCEvalf
Direct Connect
CATIA Direct CatDC CatDCEval CatDCf CatDCEvalf
Connect
Appendixes
163
Notes:
● One renderer license is included with all base products
except for SurfaceStudio.
● AutoStudio includes EvalViewer with the cloud and
SurfaceStudio options.
● Studio with Advanced Evaluation includes EvalViewer
with the cloud option.
● Studio with Advanced Modeling includes EvalViewer
with the SurfaceStudio option.
Additional resources
● www.globetrotter.com provides information on licensing.
● See Getting Help and More Information on page 156.
Appendixes
164
Redundant Servers
Some large organizations may want the ability to create
redundant servers where they can ensure that licensing can
continue even if a license server is unavailable or is taken off-
line for maintenance.
For example, redundant license servers may be required by:

● Sites needing to serve licenses to many users
● Sites needing the highest possible degree of reliability and
availability of licenses.
This section is applicable only to these large sites, and should

be ignored by most Alias|Wavefront users.
Requirements
Appendixes
To successfully use redundant license servers, the following
conditions must be met:
● You must be an experienced system administrator.
● Redundant license servers can be on any qualified
StudioTools platform.
● Three or more systems must be configured as license
servers, with there being an odd number of servers (3, 5,
etc.).
The majority of the servers must be up at any one time (2
of 3, 3 of 5, etc.).
● Dedicated servers are required. Because of the network
and processor demands placed on the license servers,
these servers should not be user machines or be running
any other significant tasks.
● Machines must be networked well. For users to work with
software without any interruption or delays for license
checkout, all network services should be as stable and as
fast as possible.
● Servers and clients must be geographically close together
in the same building. Servers cannot be located in
locations other than clients, even if they share the same
network. Additional problems may be experienced when
crossing firewalls of any kind.
Appendixes
165
Redundant Servers
If you cannot meet the above conditions, use other methods
outlined in this book for licensing: for example, local
configuration on each system (node-locked licenses), or
standard floating licenses with one server.
The rest of this section is divided into two parts, based on the
platform of the server:
● Setting up Redundant Servers on Windows NT or Windows
2000 Systems on page 167
● Setting up Redundant Servers on UNIX on page 172
Appendixes
166
Redundant Servers
Setting up Redundant Servers on Windows NT
or Windows 2000 Systems
Note It is recommended that you are an experienced system

administrator to proceed. Your login account must have
administrative privileges.
Before you start
Ensure that you have completed the following before

continuing with the server setup.
● Install the License Server Software on each of the license
server machines (using the Custom install). See Installing
StudioTools on Windows Systems on page 14.
● A valid floating license is available. The redundant server
license differs from standard floating licenses (see the next
section).
Appendixes
Sample License
Below is part of a sample redundant license for StudioTools

9.5:
SERVER machine1 0930292f59eb 7111
SERVER machine2 03467675d603 7111
SERVER machine3 222c03f467f71 7111
DAEMON sgiawd C:\aw\Com\etc\sgiawd
FEATURE Studiof sgiawd 9.500 2-mar-2000 3 \

ABCDEF123456
FEATURE StudioAMf sgiawd 9.500 2-mar-2000 3 \
ABCDEF123456
FEATURE StudioAEf sgiawd 9.500 2-mar-2000 3 \
ABCDEF123456
FEATURE StudioADAf sgiawd 9.500 2-mar-2000 3 \
ABCDEF123456
FEATURE CatDCf sgiawd 9.500 2-mar-2000 3 \
ABCDEF123456
FEATURE UgDCf sgiawd 9.500 2-mar-2000 3 \
ABCDEF123456
FEATURE IDCf sgiawd 9.500 2-mar-2000 3 \
ABCDEF123456
FEATURE EvalViewf sgiawd 9.500 2-mar-2000 3 \
ABCDEF123456
FEATURE EVCloudf sgiawd 9.500 2-mar-2000 3 \
Appendixes
167
Redundant Servers
ABCDEF123456
FEATURE EVSurff sgiawd 9.500 2-mar-2000 3 \
ABCDEF123456
FEATURE AliasRenderf sgiawd 9.500 2-mar-2000 3 \
ABCDEF123456
FEATURE AliasPRf sgiawd 9.500 2-mar-2000 3 \
ABCDEF123456
For information on how to read the lines in this license, see

Understanding Licenses on page 160.
However, note in the above example that there are three

SERVER lines, for three license servers named machine1,
machine2 and machine3. The number immediately following
the server name will vary depending on the method used to
license the software.
The license file should be named based on the host name

(aw_hostname.dat). For example, the license for host
machine1 would be named aw_machine1.dat (the
aw_flexlm script will look first for a license file with this
name).
For the rest of this section, the examples will be based on the
above license sample, with the servers machine1, machine2
and machine3. The master server is machine1, and the slave
servers are machine2 and machine3.
Setting up license servers
Create license files on servers
A license file must be created on all machines that are to be

used as redundant license servers:
1 Using a text editor such as notepad or wordpad, create a
new file inside the C:\FLEXlm directory to store the
licensing information. Name the license file
aw_hostname.dat, where hostname is your host name.
For example, the license for host machine1 would be
named aw_machine1.dat (the aw_flexlm script will look
first for a license file with this name).
Appendixes
168
Redundant Servers
Tip Ensure that you do not have Hide file extensions turned on
in Explorer folder options. If the licensing file has a txt
extension, you will encounter a licensing error.
2 Copy all the license information sent to you from

Alias|Wavefront into this new file.
3 Save the file and exit from the text editor.
4 Back up and remove any existing license files, leaving

only the new license file.
Repeat the above steps on each of the server machines,

changing the name of the license file to the appropriate name
for that machine
Configure each of the license servers
Appendixes
Use the following instructions to set up and configure each of
the license servers:
● To set FLEXlm license server options on page 43
● To stop and start the license server on page 43
Repeat the above procedures on all server machines.
When all servers are set up, select the Start Server button on
each machine to start up each license server.
Use the debug log file to make sure the license servers are
connected. The debug log file also contains information on
possible problems.
Set up the Client Machines
After confirming that the license servers are operational,

Alias|Wavefront software can be installed and client licenses
configured; use the instructions in the section To set up each
client machine on page 44.
Note that the file aw_license.dat that you create should

have the following lines, where hostname and hostid are
the host name and host ID of your configuration:
Appendixes
169
Redundant Servers
SERVER machine1 0930292f59eb 7111
SERVER machine2 03467675d603 7111
SERVER machine3 222c03f467f71 7111
DAEMON sgiawd C:\aw\Com\etc\sgiawd
USE_SERVER
Tip The hostnames and host IDs can easily be copied into this
new file from the license on any license server.
Verify and troubleshoot a license checkout on each client
You should be able to launch the installed Studio Tools

product on each client, and view the available server licenses
in the Application Launcher (if there is more than one
available product).
If license checkout is not successful, check the following:

● View the debug log on a server for information on client
license checkouts, and address any errors that are
reported.
● Confirm network connectivity between the client and all
servers (use ping hostname to test).
● Verify that the client license is named correctly and is at
the correct location: c:\FLEXlm\aw_license.dat
(where c is the drive where Flexlm is installed).
● Verify that StudioTools has been properly installed on the
client machine.
Set up additional clients
Perform the preceding configuration and troubleshooting

steps for each client that is going to use the license servers.
Note that you can copy the same client license to each client
machine if it is sharing the same set of redundant license
servers.
Appendixes
170
Redundant Servers
Troubleshooting
Problem Suggestions
No licenses are available in • Verify that all license files end with the extension
Application Launcher, or a message is .dat. (Text editors may have added the extension
displayed indicating that licenses are .txt to a file.)
not found. • Verify that server and client license files contain
the correct information.
• Verify that server and client machines all have
FLEXlm licensing software installed.
Issuing a shutdown command to one This behavior is normal. To take one server off-line,
of the redundant servers shuts down stop it manually. It will come back up when
all servers. reconnected to the network and is recognized by the
other servers.
The server log file reports: This message usually indicates that the connection to
one of the other servers was lost.
Appendixes
ERROR: (LMGRD) lost connection to • Verify that the license server is up.
[hostname] • Verify that the network connection to the server is
not lost.
• Using Task Manager, verify that the tasks lmgrd
and sgiawd are still running.
The server log file reports: • Remove duplicate FEATURE entries in the server
license file.
ERROR: Duplicate feature in license
file detected.
Appendixes
171
Redundant Servers
Setting up Redundant Servers on UNIX
Before you start
Ensure that you have completed the following before

continuing with the redundant license server setup:
● FLEXlm software is installed on each of the license server
machines (three or more machines).
◆ On IRIX, these packages are called “FLEXlm 6.1
Server Software” and are installed from the IRIX
swmgr tool.
◆ On the Solaris operating environment, these packages
are called “Alias|Wavefront Standalone Flexlm
License Manager and Utilities” and are installed from
the admintool or swmtool tools.
● A valid floating license is available. The redundant server
license differs from standard floating licenses. When
requesting the license, the host name and hostid should be
available for each of the servers.
To obtain the hostid for each system use the following
command:
◆ For IRIX:
% /usr/sbin/lmhostid
◆ For the Solaris operating environment:
% /usr/aw/COM/bin/lmhostid
● All machines are running qualified releases of the Solaris
operating environment, IRIX, Windows NT or Windows
2000 with required patches. Qualified operating systems
and patches can be found at www.aliaswavefront.com
under the Support links.
● Machines are networked to each other and all client
machines
● For IRIX, the A|W License Server Software package
(awcommon.sw.server) is installed.
● You have a valid redundant server license for StudioTools.
(See the next section.)
Appendixes
172
Redundant Servers
Understanding your redundant server license
The following is an example of what a redundant server

license might look like:
SERVER yakko 609ac5aa 7111
SERVER wakko 60a21933 7111
SERVER dot 60a2cc04 7111
FEATURE AutoStudiof sgiawd 9.500 9-apr-2000 4 \
XX(REMOVED)X
FEATURE UgDCf sgiawd 9.500 9-apr-2000 4 \
XX(REMOVED)X
FEATURE EvalViewf sgiawd 9.500 9-apr-2000 4 \
XX(REMOVED)X
FEATURE EVCloudf sgiawd 9.500 9-apr-2000 4 \
XX(REMOVED)X
FEATURE EVSurff sgiawd 9.500 9-apr-2000 4 \
XX(REMOVED)X
FEATURE AliasRenderf sgiawd 9.500 9-apr-2000 4 \
XX(REMOVED)X
Appendixes
For information on how to read the lines in this license, see
Understanding Licenses on page 160.
However, note in the above example that there are three

SERVER lines, for three license servers named yacko, wacko
and dot. The number immediately following the server name
is the host ID for each machine.
The license file should be named based on the host name

(aw_hostname.dat). For example, the license for host yakko
would be named aw_yakko.dat (the aw_flexlm script will
look first for a license file with this name).
For the rest of this section, the examples will be based on the
above license sample, with the servers yakko, wakko and dot.
The master server is yakko, and the slave servers are wakko
and dot.
Appendixes
173
Redundant Servers
Setting up the servers
Log in to the servers
Because configuration is required on each of the machines

used as license servers, we suggest that you log in remotely to
each server, as root from one machine.
1 Open three shells on your local machine — one for each
server to be set up.
2 Use the first shell to administer the local machine, yakko,

so no remote login is necessary. In the first shell log in as
root by typing the following:
% su root
3 Use the second shell to administer wakko. In the second

shell type:
% rlogin -l root wakko
4 Use the third shell to administer dot. In the third shell

type:
% rlogin -l root dot
Create a license file on each of the three servers

1 Change the directory to the FLEXlm license directory:
% cd /var/flexlm
2 Create a new text file for the license:

% vi aw_yakko.dat
(any text editor can be used in place of vi)
3 Copy the entire license into this file, save it, and exit from
the text editor.
4 Back up and remove any unused licenses from this

directory, leaving only the aw_yakko.dat file
5 Repeat the above steps for each of the server machines

changing the name of the license file (aw_yakko.dat) to
the appropriate name for that machine (that is, dot =
aw_dot.dat, wakko = aw_wakko.dat).
6 For IRIX only, enable aw_flexlm checkconfig:
Appendixes
174
Redundant Servers
% chkconfig -f aw_flexlm on
Start the license servers

1 From the master server, yakko, type the following as root:
% /etc/init.d/aw_flexlm start
2 From the slave server, wakko, type the following as root:

3 From the slave server, dot, type the following as root:

Verifying that the license servers are running
The following steps will allow you to verify that the necessary
license daemons are running on each machine using the ps
command.
Appendixes
Note Depending on the version of UNIX you are using, ps may
have different arguments.
On IRIX, use the ps -ef command to get a detailed list of
active processes.
On the Solaris operating environment, the typical usage is
also ps -ef, although there are cases when ps ax should
be used instead. If you need help, consult the man pages for
more details (man ps).
Interpret the results on the master server
Perform the following test on the master server, yakko:

1 Verify that lmgrd is running:
% ps -ef | grep lmgrd
(If this command is not valid, read the note above.)
2 Verify that sgiawd is running:

% ps -ef | grep sgiawd
If lmgrd and sgiawd are running, you can skip the following
steps and proceed directly to Interpret the results on the slave
servers on page 176.
Appendixes
175
Redundant Servers
If neither lmgrd or sgiawd are running:
● Confirm that the license is valid.
● Check the location of the license. The license should be
located in the directory /var/flexlm
● Check the logfile for errors. (See the section Check the
FLEXlm log for errors on page 178 for details.)
If lmgrd is running, but sgiawd failed:

● Check the name of the license file. It should be
aw_hostname.dat
● Verify that the host ID for each machine in the license is
correct. Check the host ID using the lmhostid command
described in Before you start on page 172 and compare the
results with the hostid listed in the license file
● Confirm that the current version of sgiawd is installed.
On the Solaris operating environment, this should be
version 7.0d or greater; on IRIX, the current version is 6.1.
To check the current version, use the following command:
% /usr/aw/COM/etc/sgiawd -v
This should return a line similar to the following, printed
from the Solaris operating environment:
17: 27:02 (sgiawd) FLEXlm version 7.0d
sgiawd v7.0d - Copyright 1988-1999, Globetrotter Software, Inc.
Once you perform the above troubleshooting, repeat the steps

in the section Start the license servers on page 175 until the
master license server has started.
Do not proceed to the next steps until lmgrd and sgiawd
are running on the master server.
Interpret the results on the slave servers
When lmgrd and sgiawd are working on the master server

yacko, perform the following test on the slave servers (wakko
and dot):
1 Verify that lmgrd is running:
% ps -ef | grep lmgrd
Appendixes
176
Redundant Servers
2 Verify that sgiawd is running:
% ps -ef | grep sgiawd
If lmgrd and sgiawd are running, you can skip the following
steps and proceed directly to Check the FLEXlm log for errors on
page 178.
If neither lmgrd or sgiawd are running:

● Confirm that the license is valid
● Confirm that the network services between machines is
working properly
● Check the location of the license. The license should be
located in the directory /var/flexlm
If lmgrd is running, but sgiawd failed:
Appendixes
● Check the name of the license file. It should be
aw_hostname.dat, where hostname is the name of the
machine.
● Verify that the hostid for each machine in the license is
correct. Check the hostid using the lmhostid command
as outlined in Before you start on page 172.
● Type lmhostid and compare the results with the hostid
listed in the license file for each machine
● Confirm that the current version of sgiawd is installed.
On the Solaris operating environment, this should be
version 7.0d or greater; on IRIX, the current version is 6.1.
To check the current version, use the following command:
% /usr/aw/COM/etc/sgiawd -v
This should return a line similar to the following, printed
from the Solaris operating environment:
17: 27:02 (sgiawd) FLEXlm version 7.0d
sgiawd v7.0d - Copyright 1988-1999, Globetrotter Software, Inc.
Appendixes
177
Redundant Servers
Check the FLEXlm log for errors
If you believe that there may be a problem with any of the

servers , or want to check the status of the servers, perform the
following test on the master server first and then on each slave
server:
% tail /usr/tmp/aw_flexlm.log
Set up the Client Machines
After confirming that the license servers are operational,

Alias|Wavefront software can be installed on clients and
client licenses configured. The following examples are based
on the assumption that the software is installed locally on the
client.
Install StudioTools on clients
Before you proceed, use the following sections to install the

StudioTools software on the client machines:
● Installing on Windows Systems on page 5
● Installing on IRIX on page 63
● Installing on the Solaris operating environment on page 101
Configure client licenses
Once the license servers are operational, the clients (systems

that will be checking out licenses) can be configured.
1 Ensure that StudioTools is installed on each client.
2 Create a client license file called

/var/flexlm/aw_license.dat.
3 On the client machine, do the following commands to edit

the file. Note that any other text editor can be used in
place of vi.
% su root
% cd /var/flexlm/
% vi aw_license.dat
Appendixes
178
Redundant Servers
4 In the license file, add the following lines, substituting the
host name and host ID for your configuration:
SERVER yakko 609ac5aa 7111
SERVER wakko 60a21933 7111
SERVER dot 60a2cc04 7111
USE_SERVER
Tip The hostnames and host IDs can easily be copied into this
new file from the license on any license server.
5 Save the file and exit from the text editor.
Verify that the client can check out a license
After creating the client license, use the following command to

ensure that StudioTools can check out a license properly:
Appendixes
% /usr/aw/alias9.5/bin/Alias -i
If the license checkout is successful, the output of the above

command will the name of the product, version and cut
number.
If the license checkout is not successful, the above command

will report errors that can be used to diagnose licensing
problems. Use the diagnostics provided by this command to
correct any configuration problems. If after correcting any
reported errors, license checkout is still not successful, check
the following:
● Confirm network connectivity between client and all
servers (use ping or rlogin hostname to test).
● Verify that the client license is named correctly and is at
the correct location:
/var/flexlm/aw_license.dat
● Verify that StudioTools has been properly installed on the
client machine (see the installation notes elsewhere for
details).
Appendixes
179
Redundant Servers
Set up other clients
The client license above can be copied to other client machines

that will be using the same license servers. Before copying the
license file, ensure that StudioTools is properly installed on
each machine.
Troubleshooting
Problem Solution
You receive the following error when The FLEXlm software was not installed
running the command properly.
/etc/init.d/aw_flexlm start:
Re-install the software from the
Can’t find the FLEXlm server Alias|Wavefront software CD. Be sure that
program. . . when customizing the installation, the
Install the FLEXlm software. . . packages called “Alias|Wavefront Standalone
Flexlm License Manager and Utilities” are
selected.
You receive the following error when The correct license file does not exist or is
running the command named incorrectly.
/etc/init.d/aw_flexlm start:
Can’t find Alias|Wavefront server

license file /var/flexlm/
aw_[hostname].dat
FLEXlm server ... lmgrd not
started
You see the following error in the logfile: This error usually indicates that the connection
to one of the other servers was terminated
(LMGRD) lost connection to because either lmgrd or sgiawd stopped
[hostname] running:
• See if lmgrd and sgiawd are still running
on the server that caused the error (use the ps
command).
• If they are still running ensure that the
network connection is active between these
machines (using ping).
Appendixes
180
Redundant Servers
Plotter Installation
This section describes how to set the plotter and paper sizes to
plot from StudioTools.
● For Plotter setup, see the Basic Tools manual.
● For a Postscript plotter driver, see psplotf in the Utilities
online manual.
● For a HP Graphics Language or IBM-GL plotter driver, see
hp_glplotf or hp_gl2plotf in the Utilities online
manual.
Overview
StudioTools can plot to the Postscript, HP-GL and HP-GL2
printers and plotters, using the standard interface provided as
part of the UNIXTM Line Printer facility (namely, lp).
Appendixes
Therefore the plotter is accessible to StudioTools through the
network as well, if the UNIXTM line printing facility has been
set up to use the plotter.
Note Some plotters, like the HP-7475A and IBM 6184, which have
no sheet-feed capability, should have their use arbitrated
outside the UNIX Line Printer spooling facility.
StudioTools provides support for a variety of printers and

plotters including the following:
● Postscript-compatible printers
● IBM plotter models 6182, 6184, 6185, and 6186, via RS-232
serial connection
● IBM 4019/4029 printers in both HP-GL and Postscript
modes, via parallel connection
● Hewlett-Packard plotter models 7475A and 7595A
(Draftmaster) pen plotter via RS-232 connection
● Hewlett-Packard plotter model 755CM is supported the
HP-GL2 format
Other HP-GL and HP-GL2 printers and plotters can be

supported by your adding configuration information to the
file sys/install/hp_gl.cfg.
Appendixes
181
Printer/ Plotter Installation in UNIX
Before plotting from StudioTools, connect and set up your
printer or plotter and the UNIX Line Printer queue.
● For IRIX, this is described in detail in SGI’s Personal System
Administration Guide, Chapter 3, "Setting Up Network,
Peripheral, and Printer Connections," provided with each
system. This manual describes how to manage print
operations from IRIX using the Printer Manager. In IRIX,
you can open the Printer Manager through the Toolchest.
Recommendations
We recommend the following selections when you are adding

a printer or plotter:
RS-232 serial connected plotter:
Type of connection Serial
Printer type Serial Plotter
Type of handshaking Software
parallel connected plotter:
Type of connection Parallel
Printer type Generic Printer
Postscript(TM) printer:
for RS-232 serial connected printers:
Type of connection Serial
Type of handshaking Software
Printer type ● LaserWriter for an Apple

LaserWriter
● LaserWriter II for an Apple
LaserWriter II
● Generic Postscript for all others
Appendixes
182
Postscript(TM) printer:
for parallel connected printers:

Type of connection Parallel
Printer type Generic Postscript
Remote Plotting
To set up for remote plotting, you need to add a networked

printer.
● In IRIX systems, run the Printer Tool (in IRIX) on the
remote system and add a networked printer.
Type of connection Network
Remote hostname Enter the hostname of the machine

that the plotter is physically
Appendixes
attached to.
Remote printer name Enter the printer name as it is on
the machine that the plotter is
physically attached to
Appendixes
183
LP destination name for plotter in IRIX
Plotter device
Plotter device specifies the print queue for plotter output.
For example, specifying myprinter will write to the print
queue myprinter. (The name depends on your installation:
refer to the lp(1) section of the UNIX manual.) In IRIX you
see:
LP queue options for plot output in IRIX
Plotter options
Plotter options specify the options to be added when
StudioTools submits jobs to one of the following:
◆ lp(1) command
◆ translator program (bin/psplotf or bin/
hp_glplotf or hp_gl2plotf)
◆ etc/plotit script
These options should be in one of the following forms:
◆ -o<option> for the lp(1) command
◆ -f<option> for the translator programs
◆ -<option> for the etc/plotit script.
Appendixes
184
Some examples are:
-oh# lp specifies: don’t print the header page.

-s# specifies: save the Alias V9.0 plotfile.
Note If this variable is empty, no options are passed on to the

plotter driver. (See the Driver Options section below.)
Plot filter
This variable specifies the full path of the plot filter
program used by the Alias plot (See the Alias Plot System
section below). If the variable is not set, the default script
etc/plotit is used. Normally, the users can use this
variable to specify an alternate location of the plotit script.
The interactive package calls the plot filter script (typically
etc/plotit) as follows:
Appendixes
plotit <ALIAS_PLOT_OPTIONS> -t<ALIAS_PLOT_TYPE> \
-d<ALIAS_PLOT_DEVICE> <plotfile>
Plotter Diagnostics
If the plot does not come out as intended, please try the
following steps:
● Open your Printer Manager or Printer Settings window
(Start > Settings > Printers in Windows NT). Look for the
plotter that you have set up in the Alias Preferences option
box. If it is not available, the plotter is not installed
correctly.
● Select the printer icon and send a test page to your
printer/plotter from StudioTools. If the test page does not
succeed, the plotter installation is not correct. Check for
error messages for peripheral devices on your system.
● If the test page is successful, from StudioTools save the
plot output in a plotter file format. For example, save it as
a HP-GL2 file. Now send this file to the print queue.
In UNIX:
/usr/bin/lp -d <plotter_name> <filename>
Appendixes
185
If the file is plotted correctly, it could mean that the default
file format to send to the printer is not set correctly. For
example, the file might be HP-GL2 when the printer needs
an HP-GL file. To correct it, edit this line in the file etc/
plotit:
plotcmd="hp_gl2plotf"
Change it to
plotcmd="hp_glplotf"
This changes the format of the output sent to the plotter to
HP-GL.
Appendixes
186
File Structure (UNIX Only)
This section outlines the file structure for the Alias|Wavefront
StudioTools products running on the UNIX systems, as may
be required by system administrators.
This section contains:

● Base Software File Layout on page 187
● Render Software File Layout on page 188
● Contents of /usr/aw/alias/ on page 189
● Contents of a Project Directory on page 191
● Files Installed by inst Products on page 192
Base Software File Layout
Appendixes
The following layout is created if the Studio, DesignStudio, or
AutoStudio product is installed:
Note Files and directories enclosed in square brackets ([ ]) are

optionally installed.
The following components are installed outside of the /usr/

aw/tree.
/usr/aw/alias9.5/
/.Alias
/.AliasPrefs
/.cut
/AliasHotkeys.scm
/Anim/
/Cloud/
/Comlib/
[/CourseWare/]
/Extensions/
/Fonts/
/Gifts/
[/Help/]
/IGES.config/
/Image/
/Modeling/
/ODS/[Common]
Appendixes
187
/Games
/OpenAlias
/OpenModel
/[OpenRender]
/Render/
/STEP/
/Scheme/
/alt_bitmaps/
/app-defaults/
/bin/
/bitmaps/
/cel/
/etc/
/lib/
/lib32/ (IRIX only)
/pix/
/plugins/
/render_control/
/statwins/
/sys/NewFont
/drivers/
/install/
/hp_gl.cfg
/sys/option/
Render Software File Layout

The following layout is created if the Alias Render software is
installed:
/usr/aw/alias9.5/
/.Alias
/.cut
/.AliasPrefs
/AliasHotkeys.scm
/bin/
/alias_render_demon
/alinfo
/beep
/convert
/findit
/fstats
/gamma
/get_alias_variable
/getid
/pixdiff
Appendixes
188
/powercaster
/powercaster.i6.4k (IRIX only)
/powercaster.i6.5k (IRIX only)
/powertracer
/powertracer.i6.4k (IRIX only)
/powertracer.i6.5k (IRIX only)
/raytracer
/raytracer.i6.4k (IRIX only)
/raytracer.i6.5k (IRIX only)
/renderer
/renderer.i6.4k (IRIX only)
/renderer.i6.5k (IRIX only)
/renderit
/setupacct
/skd
/etc/acct/
/etc/skd
/render_control/
Appendixes
Contents of /usr/aw/alias/
The following table shows the directories and files placed in
the /usr/aw/alias directory created by a StudioTools
installation.
.AliasPrefs The default values for a number of peripheral devices and

other options (such as the default coordinate system). If you
modify the default preferences for the StudioTools software,
this file is copied to your home directory to reflect your
personal preferences. If this file is not present, StudioTools will
not launch.
.cut Information identifying the version of StudioTools software.
AliasHotkeys.scm The default settings for keyboard shortcuts supported by the
Alias|Wavefront software.
Appendixes
189
Anim/ StudioTools system directories
Cloud/
Comlib/
Conductors/
Extensions/
Image/
Modeling/
Render/
STEP/
Scheme/
alt_bitmaps/
app-defaults/
bitmaps/
cel/
lib/
pix/
plugins/
statwins/
Fonts/ Contains fonts for use with the Text tool (Objects > Text) in
StudioTools.
Gifts/ Contains a set of unsupported tools that users may find
useful.
Help/ Contains files for StudioTools online help.
IGES.config/ Contains configuration files for IGES files.
ODS/ Contains files for OpenAlias, Alias OpenModel, Alias
OpenRender, including example files.
bin/ Contains executable programs, including StudioTools,
renderer, and other products that you have purchased.
The file layout above for StudioTools Render software
indicates the installation of the R4000 (4k) and R5000/R10000
(5k) render products.
etc/ Contains other executable programs that you do not run
directly. They are run when needed by the StudioTools
software. This directory also contains a template of a typical
StudioTools user account, which is used by setupacct.
Appendixes
190
install/ Includes files that control the configuration of your system.
This directory contains hp_gl.cfg, a configuration file for
Hewlett Packard plotters.
sys/ All the files in sys and sys/install are system-wide. They
sys/install/ should not be changed, unless you are changing them for your
workstation as a whole, since all users share them. If you wish
to change the files, login as the owner of the StudioTools
software (the superuser) and make the changes in /usr/aw/
alias.
Contents of a Project Directory

When you run the StudioTools software for the first time it
will creating a default project called demo.
Appendixes
The demo project directory and any other project directories
you create contain the following sub-directories:
anim/ contains scene description files for animation. This is in SDL-

like format (see the File > Save anim documentation online for
details).
canvas/ contains files for Alias|Wavefront 2D and 3D programs (for
example, Alias StudioPaint 3D).
draw/ contains draw overlay information for Alias StudioPaint 3D.
environment/ contains environment shaders. Environment shaders are used
to set the attributes of a model’s surroundings when you
render.
light/ contains lights as created from the Multi-lister.
mask/ contains matte files in texture and other mapping procedures.
misc_data/ contains usr_colors.12bit, files that define colors used in
the interactive package.
option/ contains files that are used by the main Alias executable to
remember menu and option settings.
pix/ contains rendered image files.
plot/ is used for plotter output.
Appendixes
191
rib/ if you select RIB (Renderman Interchange Bytestream) output
the files will be placed in this directory.
sdl/ contains SDL (Scene Description Language) files for
rendering.
shader/ contains predefined shader information from the Render and
Multi-lister functions.
shelf/ contains data files used by Alias StudioPaint 3D.

sla/ contains data to be output to the Stereo Lithography
Apparatus (SLA) which is made by 3D Systems Inc.
stencil/ contains data files used by Alias StudioPaint 3D.
texture/ contains predefined texture information suitable for browsing
in Render and Multi-lister functions.
wire/ contains data files from modeling and animation.
Files Installed by inst Products

There are three inst products that install files into system
level directories:
inst product Software installation Description
DesktopInstall.txt awcommon.sw.desktop Alias|Wavefront common

desktop environment
aliasInstall.txt alias9_5.sw.desktop Alias|Wavefront Studio
desktop environment
awcommonServerInstall.txt awcommon.sw.server Alias|Wavefront license
server software
The following sections list the files installed by these products.
Common desktop environment installation
The DesktopInstall.txt inst product installs the

following files for the Alias|Wavefront common desktop
environment (awcommon.sw.desktop):
Appendixes
192
usr/lib/ImageVision/filefmt/libilALIAS.so
usr/lib/ImageVision/filefmt/libilAliasCompress.so
usr/lib/ImageVision/filefmt/libilAliasEclipse.so
usr/lib/ImageVision/filefmt/libilEXPLORE.so
usr/lib/ImageVision/filefmt/libilRLA.so
usr/lib/X11/app-chests/aw.chest
usr/lib/filetype/install/aw.common.ftr
usr/lib/filetype/install/aw.ftr
usr/lib/filetype/install/iconlib/aw.books.closed.fti
usr/lib/filetype/install/iconlib/aw.books.open.fti
usr/lib/filetype/install/iconlib/aw.device.FBD.fti
usr/lib/filetype/install/iconlib/aw.device.VTR.fti
usr/lib/filetype/install/iconlib/aw.dso.Audio.fti
usr/lib/filetype/install/iconlib/aw.dso.Font.fti
usr/lib/filetype/install/iconlib/aw.dso.Image.fti
usr/lib/filetype/install/iconlib/aw.dso.Outlet.fti
usr/lib/filetype/install/iconlib/aw.dso.PlugIn.fti
usr/lib/filetype/install/iconlib/aw.dso.Spark.fti
usr/lib/filetype/install/iconlib/aw.folder.closed.fti
usr/lib/filetype/install/iconlib/aw.folder.open.fti
usr/lib/filetype/install/iconlib/aw.installer.dist.closed.fti
Appendixes
usr/lib/filetype/install/iconlib/aw.installer.dist.open.fti
usr/lib/filetype/install/iconlib/aw.installer.exec.fti
usr/lib/filetype/install/iconlib/aw.license.fti
usr/lib/filetype/install/iconlib/aw.licenser.closed.fti
usr/lib/filetype/install/iconlib/aw.licenser.open.fti
usr/lib/filetype/install/iconlib/awkeys.folder.closed.fti
usr/lib/filetype/install/iconlib/awkeys.folder.open.fti
usr/local
usr/local/aw
usr/sbin/Licenser
usr/sbin/di
usr/sbin/fcheck
usr/sbin/imgcvt
usr/sbin/toimg
Studio desktop environment installation
The aliasInstall.txt inst product installs the following

files for the Alias|Wavefront Studio desktop environment
(alias9_5.sw.desktop):
usr/aw
usr/aw/alias9.5
usr/include/X11/bitmaps/alias_icon
c usr/lib/X11/input/config/wacom
usr/lib/filetype
usr/lib/filetype/install
usr/lib/filetype/install/Alias3D.ftr
Appendixes
193
usr/lib/filetype/install/iconlib/Alias3D.MS3.closed.fti
usr/lib/filetype/install/iconlib/Alias3D.MS3.open.fti
usr/lib/filetype/install/iconlib/Alias3D.RRFR.closed.fti
usr/lib/filetype/install/iconlib/Alias3D.RRFR.open.fti
usr/lib/filetype/install/iconlib/Alias3D.SoundSync.closed.fti
usr/lib/filetype/install/iconlib/Alias3D.SoundSync.open.fti
usr/lib/filetype/install/iconlib/Alias3D.anim.fti
usr/lib/filetype/install/iconlib/Alias3D.environment.fti
usr/lib/filetype/install/iconlib/Alias3D.flipbook.closed.fti
usr/lib/filetype/install/iconlib/Alias3D.flipbook.fti
usr/lib/filetype/install/iconlib/Alias3D.flipbook.open.fti
usr/lib/filetype/install/iconlib/Alias3D.light.fti
usr/lib/filetype/install/iconlib/Alias3D.mask.fti
usr/lib/filetype/install/iconlib/Alias3D.oldlight.fti
usr/lib/filetype/install/iconlib/Alias3D.oldsdl.closed.fti
usr/lib/filetype/install/iconlib/Alias3D.oldsdl.open.fti
usr/lib/filetype/install/iconlib/Alias3D.oldwire.closed.fti
usr/lib/filetype/install/iconlib/Alias3D.oldwire.open.fti
usr/lib/filetype/install/iconlib/Alias3D.oldwire.top.fti
usr/lib/filetype/install/iconlib/Alias3D.pix.fti
usr/lib/filetype/install/iconlib/Alias3D.qmexec.bottom.fti
usr/lib/filetype/install/iconlib/Alias3D.qmexec.closed.fti
usr/lib/filetype/install/iconlib/Alias3D.qmexec.open.fti
usr/lib/filetype/install/iconlib/Alias3D.qmfile.bottom.fti
usr/lib/filetype/install/iconlib/Alias3D.qmfile.closed.fti
usr/lib/filetype/install/iconlib/Alias3D.qmfile.open.fti
usr/lib/filetype/install/iconlib/Alias3D.qpexec.bottom.fti
usr/lib/filetype/install/iconlib/Alias3D.qpfile.bottom.fti
usr/lib/filetype/install/iconlib/Alias3D.rrfr.fti
usr/lib/filetype/install/iconlib/Alias3D.sdl.fti
usr/lib/filetype/install/iconlib/Alias3D.shader.fti
usr/lib/filetype/install/iconlib/Alias3D.sset.fti
usr/lib/filetype/install/iconlib/Alias3D.texture.fti
usr/lib/filetype/install/iconlib/Alias3D.wire.fti
usr/lib/filetype/install/iconlib/Alias3D_V7.exec.closed.fti
usr/lib/filetype/install/iconlib/Alias3D_V7.exec.open.fti
usr/lib/filetype/install/iconlib/Alias3D_preV7.exec.bottom.fti
usr/lib/filetype/install/iconlib/Alias3D_preV7.exec.closed.fti
usr/lib/filetype/install/iconlib/Alias3D_preV7.exec.open.fti
usr/lib/images
usr/lib/images/Alias.icon
usr/lib/images/DataBrowser.icon
usr/lib/images/FlipBook.icon
usr/lib/images/RRFR.icon
usr/lib/images/XWsh.icon
usr/lib/images/XWsh.icon
usr/lib/images/livewire.icon
usr/lib/images/soundsync.icon
usr/sbin/winterm_Alias9.5
usr/sbin/xterm_Alias9.5
Appendixes
194
License server installation
The awcommonServerInstall.txt inst product installs

the following files for the Alias|Wavefront license server
software (awcommon.sw.server):
etc/config/aw_flexlm
etc/init.d/aw_flexlm
etc/rc2.d/S51aw_flexlm
usr/aw/COM2.0/etc/sgiawd
tmp/magic.alias
Appendixes
Appendixes
195
NFS Overview (UNIX Only)
What is NFS?
NFS (Network File System) is a software option that allows the
file systems of two or more computers to be connected
together using Ethernet. NFS can help you save disk space by
sharing a single copy of files among two or more machines.
To use NFS you should be comfortable with simple operating

system administration since you may have to edit some
system files. This overview presents a brief introduction to
NFS and its possible uses with StudioTools.
For a more detailed explanation:

● For the Solaris operating environment, see your NFS
documentation or contact your system administrator.
● For IRIX, see SGI’s NFS and NIS Administration Guide or
contact your system administrator.
Example
Let's look at how NFS might be used with StudioTools.
For this example, assume you have two workstations —

identical except that one, big, has a lot of disk space, while the
other, little, does not. By using NFS to mount /usr/aw/
alias from big to little, you can save storage space on the
smaller machine. In this example, big is acting as a disk server
for little. Unless otherwise specified, all work must be done by
root.
NFS uses a file to determine which file systems can be

networked (or exported) to other systems. The name of this
NFS file depends on your operating system:
● For IRIX:
/etc/exports
● For the Solaris operating environment:
/etc/dfs/dfstab
Appendixes
196
1 First you have to determine which file system StudioTools
was installed in. If you used the default installation then
this is /usr but it may be a different file system if your
machine has more than one.
To determine what file system the software was installed
in run this command on big:
ls -l /usr/aw/alias
This prints a line that ends in something like this:
/usr/aw/alias -> alias9.5
2 In this example, StudioTools is installed in /usr. The NFS

file is the file mentioned above (/etc/exports on IRIX, /
etc/dfs/dfstab on the Solaris operating environment.
On big, edit the NFS file to add the file system where
StudioTools was installed. In the example of /usr you
would add the following to the NFS file:
◆ For IRIX:
/usr
Appendixes
save -F nfs /usr
3 Tell NFS to export this file system by running the

command:
◆ For IRIX:
/usr/etc/exportfs -a
/usr/sbin/shareall Solaris
4 The following file is used by the operating system when it

mounts file systems:
◆ For IRIX: /etc/fstab
◆ For the Solaris operating environment: /etc/ufstab
On little, edit this file to add the following line:
big:/usr /bigusr nfs rw,soft,bg 0 0
This allows the /usr file system on big to be accessed
from little using /bigusr.
5 On little, create a directory on which big:/usr can be

mounted, and mount it:
Appendixes
197
◆ For IRIX:
mkdir /bigusr
/etc/mount /bigusr
mkdir /bigusr
/usr/sbin/mount /bigusr
6 On little, verify that things are OK, then run df. You
should see something like this:
Filesystem Type blocks use avail %use Mounted on
big:/usr nfs 175488 156525 18962 89% /bigusr
7 On little, make /usr/aw/alias point to StudioTools on

big.
mkdir /usr/aw
ln -s /bigusr/aw/alias9.5 /usr/aw/alias
Note If /usr/aw/alias already exists on little, you need to

rename it or remove it before running these commands:
If StudioTools was installed in a file system other than /usr or

the software is not installed in the top level of a directory (for
example, /usr/u/aw/alias9.5) you will have to change the
above commands accordingly.
Now proceed to set up your accounts as outlined in the

Installation Notes.
Note
The files /var/flexlm/aw_servername.dat or

/var/flexlm/aw.dat must contain license information on
each machine for StudioTools to run. This example can be
extended to more workstations, with two conditions:
● A disk server and the network can handle a limited
volume of traffic. There is no hard limit; it depends on
your level of activity. If you see messages of the form:
NFS getattr failed for server big: RPC: Timed out
It means you have a network problem that could range
from network overloading to hardware problems.
Unfortunately, StudioTools in this NFS configuration
Appendixes
198
relies on the server for its menus. When this type of error
is encountered, the software must exit, but it will save
your work first.
● Another way in which NFS might be used is to place each
user’s home directory and work environment on one of
the machines, and use NFS to make that area accessible to
every workstation. (i.e, to mount it on every machine). In
this way, a user can sign on at any workstation and still
have immediate access to his or her files. Do not try this
unless you are familiar with how to administer your
system.
Appendixes
Appendixes
199
Appendixes
200
A installing (Windows) 14
installing on IRIX 76
installing on Solaris 110
DOS control characters
removing from ASCII file 128
dual displays (IRIX) 142
accounts, setting up client software
Solaris 114 IRIX 67
administrative privileges 7, 14 clients
Admintool
exiting from 112
setting links for (UNIX) 73
colors, in Windows
E
starting 109 default 9 error log
Solaris 118 setting 11 licenses (UNIX) 133
Admintool (Solaris) 109 confirming graphics card error messages
afbconfig command 103 capabilities 11 licensing (UNIX) 132
confirming installation licensing log file
Alias|Wavefront
of renderer (Windows) 54
Web site 32
on Windows 22 EvalViewer
of Stand-alone Renderer choosing to install
problems
on Windows 22 IRIX 77
UNIX 131
on IRIX 90 Solaris 111
Windows 48
on Solaris 116 installing
UNIX 129
on Windows 21 IRIX 76
Windows 47
Control Panel options launching
Assist, contacting 158 Solaris 115
Windows NT 23
Assistant Online 158 space requirements
AutoStudio IRIX 66
choosing to install Solaris 105
Solaris 110
installing
D exiting
from installation 28
IRIX 75 from StudioTools 29
DesignStudio
space requirements exploring StudioTools 28
choosing to install
IRIX 65
Solaris 110
Solaris 105
installing
aw.dat file (Windows) 42 IRIX 75
aw_servername.dat file
(Windows) 42
space requirements
IRIX 65
F
Solaris 105 ffbconfig command 103
desktop file extensions
Windows 11
C Dial Box (IRIX), 143–145
showing 40
file structure (UNIX
digitizer tablet 71 installation) 187
CD ROM
directories filesystems
installing from
specifying for installation other than /usr 72, 105
Windows NT 14
IRIX 72 filters
mounting 73, 106
user’s 26 Unigraphics
setting as source medium 109
using 28 disconnected hardware lock 30 IRIX 69
disk space 8, 9, 70, 105 Solaris 105
certified graphics hardware 11
Windows 13
checking Dispatcher (IRIX)
choosing to install 77 FLEXlm 70
version number
installing 151 installing
OpenGL 107
IRIX 71
StudioTools 30 Distributed Rendering
description 68 FLEXLM checkout errors
client
UNIX 134 moving to another Windows 14
Windows 54 computer 29 from CR ROM
FLEXlm directory troubleshooting 50 Solaris 109
installing (Windows) 39 hardware overlays IRIX 70
graphics cards 12 license server
FLEXlm technology 34, 120 IRIX 77
FLEXLM_DIAGNOSTICS 53 hardware requirements Solaris 111
IRIX 69 on local machine (Solaris) 110
floating licenses Windows 7
adding 20 over a network 73, 74
additional setup (UNIX) 125 host IDs plotters 181
additional setup identifying (UNIX) 135 using inst 79
(Windows) 43 identifying (Windows) 57 using Software Manager 74
definition 34, 120 hot lines 158 Intellimouse
identifying errors (UNIX) 136 not supported 8, 12
identifying errors interface performance
(Windows) 58
troubleshooting
(Windows) 50
I tuning (Windows) 23
interrupting
understanding 161 installation 28
vs. node-locked licenses 120 Icon Catalog StudioTools
updated by Software Man- using Task Manager 29
fonts, Solaris system 104 ager IRIX mouse, simulating 12
frequently asked questions IRIX 78
(Windows) 29 IRIX operating system
Impressario printer setup required version 69
(UNIX) 150
Indigo2
G hardware requirements 69
Indy K
hardware requirements 69
graphics 12
inst killing
graphics cards installing StudioTools 79 StudioTools application 29
configuring
Solaris 103 installation
Creator 3D (Solaris) 103 changing destination
Windows 16
displaying properties of 12
driver software 12
qualified 8
choosing what to install
IRIX 75
L
Elite 3D (Solaris) 103 Solaris 111 License Manager 30
manufacturers 32 confirming
IRIX 90 license server
memory 11 installing
option settings 11 on Windows 21
Solaris 116 Solaris 111
graphics requirements exiting from 28 starting and stopping
IRIX 69 preparing to install (UNIX) 126
IRIX 72 stopping and starting
re-installing 25 (Windows) 43
starting (Windows) 14 taking offline with redundant
H installation type
selecting 110 licenses
servers 165
hardware configurations 69 checking for errors

installing Windows 56
hardware locks client confirming installation
disconnected 30 IRIX 76 UNIX 129
losing 30 Solaris 110 Windows 47
more about 32 from a directory
error log file (Windows) 53 information from 32 overlays, enabling
floating example 161 mouse Windows 12
for StudioTools Microsoft Intellimouse 8
UNIX 120–139 simulating an IRIX mouse 12
IRIX 70 Windows 12
log file (UNIX) 133
node-locked example 160
P
not required with mainte-
packages
nance contract
(UNIX) 123 N removing (Solaris) 118
parallel
not required with mainte-
nance contract Network File System (NFS), connectors
(Windows) 38 UNIX 196 Windows 10
obtaining from Alias|Wave- networking software 9 parallel ports
front drivers
node-locked licenses
UNIX 122 confirming installation 51
definition 34, 120
Windows 37 Windows 10
understanding 160
prerequisites 38
patches, software
UNIX 123
required for Solaris 103
Windows 38
pathnames
transferring
Windows 39 O in Windows systems 31
PDF files 157
licensing
changes 121 OCTANE Duo (IRIX) 142 plotters
Windows 35 online documentation 25, 156 installing 181
Globetrotter Web site 158 Dispatcher 151 ports
overview 34, 120 space requirements 70 for hardware locks 51
licensing software 82, 113 online help 73 preparing to install 69, 103
lmdiag tool (UNIX) 135 onoline SPAR form 122 pre-set views
lmgrd daemon (UNIX) 126 Open Digital Studio with Dial Box 143
lmhostid tool (UNIX) 135 description 67 previous versions of
space requirements StudioTools 128
lmstat tool (UNIX) 136
IRIX 70
lmtools program printers
OpenAlias 67 using with hardware lock 10
(Windows) 56
OpenGL problems
local machine, installing on
checking version number 107 Application Launcher
(Solaris) 110
performance 12 UNIX 131
log file for licensing errors Solaris 103 Windows 48
(Windows) 53
OpenModel 67 EvalViewer
losing hardware locks 30 Solaris 115
OpenRender 67
frequently asked
operating environment questions 29
required (Solaris) 103 installation
M operating system
required
IRIX 96
UNIX 131
IRIX 69 licensing
maintenance contract
Windows 8, 30 UNIX 131
licensing with (UNIX) 123
licensing with (Windows) 38 optional software Windows 48
installing product information
manuals 156
IRIX 77 about Windows 32
menu items 23 Alias|Wavefront Web site 32
overlay planes
Microsoft graphics cards 12 graphics cards 32
hardware locks 32 software showing
Microsoft 32 Solaris 103 file extensions 40
Product Support 158 Windows 8 software
Solaris 103 removing 70
properties
Windows desktop 11 resolution, video software licenses
Windows 11 IRIX 70
resources Solaris 113
about graphics cards 32 UNIX 120
Q about hardware locks 32
at Alias|Wavefront Web
Windows 33
Software Manager
site 32 installing StudioTools 74
qualification at Microsoft 32
getting latest information on software requirements
the Web 158 resources, additional IRIX 69
books 32 Solaris 103
Qualification Chart 8, 11
Windows 8
questions and answers
(Windows) 29 Solaris
quitting installation 28 S CDE toolbar 116
system fonts 104
Solaris 7 operating
Sentinel driver environment 103
R confirming installation 51
server
source medium, setting
(Solaris) 109
what to do if continually
Readme file restarted (UNIX) 138 space mouse (IRIX) 147
viewing 28 server software space requirements
redundant servers 165 installations 67 IRIX 70
UNIX 172 Solaris 105
servers Windows NT 8
Windows 167 redundant 165
Registry UNIX 172 Spaceball (IRIX)
Windows NT 29 Windows 167 alternative to mouse 146
reinstalling StudioTools 25 setting SPAR form
color using to get software license
removing StudioTools UNIX 122
Windows 26 Windows 11
source medium 109 Windows 37
renderer speed
video resolution
choosing to install improving 23
Windows 11
Solaris 111
confirming installation setting up Stand-alone Renderer
on Windows 22 Impressario printers confirming installation
installing (UNIX) 150 on Windows 22
IRIX 76 user accounts space requirements
Windows 18 Solaris 114 Solaris 105
space requirements setupacct command 114 stand-alone renderer
IRIX 65, 70 Setupx86.exe program (Win- choosing to install
Solaris 105 dows Sentinel driver) 51 Solaris 111
rendering server installing
shared files 26 IRIX 76
IRIX 65
shortcut Windows 18
requirements to StudioTools space requirements
hardware IRIX 90 IRIX 65
IRIX 69 Solaris 116
Windows 7 starting
Windows 21 StudioTools
IRIX 69
IRIX 90
Solaris 116
Windows 21
Windows 48
EvalViewer 115
frequently asked questions
W
startup (Windows) 29 Wacom tablet 71
duration 30 installation
Web resources
IRIX 96
stencil planes from Alias|Wavefront 158
licensing
and graphics cards 12 UNIX 131 Windows 2000
Studio Windows 48 installing on 14
choosing to install tuning interface performance Windows NT
(Solaris) 110 (Windows) 23 improving interactive
installing performance 23
IRIX 75 installing on 14
space requirements options 23
IRIX 65
Solaris 105 U Registry 29
Service Pack 8
StudioTools setting up for StudioTools 7
licensing 82, 113 Unigraphics
Windows operating system
space requirements setup
required version 8
IRIX 70 IRIX 69
Solaris 105 Windows systems
Support, contacting 158 Windows 13 books about 32
SurfaceStudio desktop properties 11
uninstalling StudioTools
choosing to install pathnames 31
IRIX 92
Solaris 110 Solaris 118
installing Windows 26
IRIX 75
space requirements
IRIX 66
UNIX 121
upgrading
X
Solaris 105 StudioTools version 20
XMouse productivity tool 12
switching computers 29 upgrading StudioTools 25
symbolic links Utilities
created by Software Manager choosing to install
IRIX 78 IRIX 77
system capabilities 7
system qualifications
getting latest information 158
system requirements
V
Windows 7
version number
of OpenGL
checking 107
T StudioTools 30
version of StudioTools
running previous 128
tablet, digitizer 71 upgrading 25
Task Manager 29 video resolution
Technical Support 158 Windows 11
terminating StudioTools viewing the Readme file 28
using Task Manager 29 VRAM 11
troubleshooting
UNIX 131

Alias - Wavefront Install Notes

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Alias - Wavefront Install Notes

Uploaded by

Copyright:

Available Formats

Installing StudioTools 9.

The following are trademarks of Alias|Wavefront:

Maya is a trademark of Silicon Graphics, Inc. exclusively used by Alias|Wavefront.

Alias|Wavefront, 210 King Street East, Toronto, Canada M5A 1J7

I n st a l l i n g on Installing on Windows Systems 5

Licensing on Windows Systems 33

I n st a l l i n g on UNIX Installing on IRIX 63

Installation Workflow 102

Licensing on UNIX Platforms 119

Licensing Overview 120

Complementary Software and Peripherals (IRIX Only) 141

Setting up OCTANE Duo and Dual Display Configurations 142

A ppendixes 153 Appendixes 155

Getting Help and More Information 156

For information on... See...

Installing StudioTools Installing on Windows Systems on page 3

Installing on Windows Systems

Here is a quick overview of what you have to do:

2 Install StudioTools. See Installing StudioTools on Windows

3 License StudioTools. See Licensing on Windows Systems on

4 Confirm that you can use your StudioTools software. See

If you run into trouble, be sure to go to the troubleshooting

Installing on Windows Systems

Your user account must have administrative privileges if

Setting up Windows NT and your hardware

To examine your system capabilities

2 You can click on the following tabs to view various types

Alias|Wavefront certifies certain system configurations from

Installing on Windows Systems

For details on hardware requirements, see the StudioTools for

Installing on Windows Systems

Additional Windows System Setup

Hardware requirements for licensing

To license StudioTools, you need one of the following security

Installing on Windows Systems

Installing on Windows Systems

Graphics card requirements

The performance of StudioTools in displaying graphics

If you are using a card that is not certified, do the following

To set your graphics card options

2 Click the Settings tab.

3 From the Color Palette pull-down menu, select True Color.

4 This specifies 24 bits of color for best color quality in

5 Drag the Desktop Area slider to the best display resolution

Installing on Windows Systems

6 When the driver software for your graphics card was

7 In the Display Properties window, click the tab named for

8 Turn on the overlay plane feature, if there is one. If there

9 Select Apply, then OK.

Mouse and keyboard settings

Use standard mouse driver option settings. Do not, for

Some vendors offer Windows NT enhancement software that

The Microsoft Intellimouse is not supported in this release.

Installing on Windows Systems

If your Windows system has a Wacom tablet installed, it is

For information on how to install your Wacom tablet, refer to

If you are going to use Unigraphics to transfer data, you must

2 Select the variable UG_ROOT_DIR.

3 Copy the value of this variable to the clipboard (use Ctrl-

4 Highlight the Path variable.

Installing on Windows Systems

To install StudioTools for Windows NT

Installing on Windows Systems