This chapter describes the contents of the software on the CD labeled Software Supplement for The Solaris 9 Operating Environment. This CD is referred to in this document as the Supplement CD. The Supplement CD contains software for these Sun products:
SunVTS(TM) 5.0 diagnostic software
OpenGL\256 1.2.1 software
PC launcher/PC file viewer 1.0.1/1.0.1 software
ShowMe TV(TM) 1.3 software
Sun hardware manual pages
Solaris 9 on Sun hardware documentation
SunFDDI(TM) PCI 3.0 driver and SunFDDI SBus 7.0 driver
SunHSITM PCI 3.0 driver and SunHSI SBus 3.0 driver
SunATMTM 5.0 driver
SunForum(TM) 3.1 software
Remote System Control (RSC) 2.1 for Sun Enterprise servers
Java 3D(TM) 1.2.1 software
Sun Enterprise 10000 System Service Processor (SSP) 3.4 software
Sun Enterprise 10000 Capacity on Demand 1.0 software
Sun Fire 880 FC-AL Backplane Firmware 1.0
Netra ct Plaftorm 1.0 software
Netra t11xx Alarms 2.0 software
Netra Lights Out Management 2.0 software
CDRW 1.0
The following table lists the versions of the software in the current Solaris 9..
Table 3-1 Solaris 9 Supplement CD Content
Software |
Solaris 9 |
---|---|
CDRW |
1.0 |
Capacity on Demand |
1.0 |
Java 3D |
1.2.1 |
NetraTM ct Platform |
1.0 |
Netra t11xx Alarms |
2.0 |
Netra Lights Out Management |
2.0 |
OpenGL |
1.2.2 |
PC launcher, PC file viewer |
1.0.1, 1.0.1 |
RSC |
2.1 |
ShowMe TV |
1.3 |
SunATM |
5.0 |
SunFDDI PCI |
3.0 |
SunFDDI SBus |
7.0 |
SunForum |
3.1 |
SunHSI PCI |
3.0 |
SunHSI SBus |
3.0 |
SunVTS |
4.5 |
Sun Enterprise 10000 System Service Processor |
3.5 |
Sun Fire 880 FC-AL Backplane Firmware 1.0 |
1.0 |
There are at least two ways to install software from the Supplement CD:
Solaris Web Start 2.0
pkgadd
If you have installed any of the Supplement CD software from a previous release, you should remove the packages associated with that software before installing the new software.
You can use Solaris Web Start 2.0 to install Supplement CD software after you have installed the Solaris operating environment.
Insert the Supplement CD into your CD ROM drive.
In a shell, type:
# cd /cdrom/cdrom0# ./installer |
When the Solaris Web Start GUI is displayed, select Next.
See Table 3-2. In the Solaris Web Start 2.0 column, software is labeled "Installed by default" or "Optional".
Software |
Solaris Web Start 2.0 |
---|---|
SunVTS 5.0 software |
Installed by default |
OpenGL 1.2.1 software |
Installed by default |
PC launcher and PC file viewer software |
Installed by default |
ShowMe TV 1.3 software |
Installed by default |
Solaris on Sun Hardware AnswerBook2 Set |
Installed by default |
SunFDDI drivers |
Installed by default |
SunHSI drivers |
Installed by default |
SunATM driver |
Installed by default |
SunForum software |
Installed by default |
Java 3D 1.2.1 software |
Installed by default |
Remote System Control 2.1 (RSC) for Sun Enterprise Servers |
Installed by default |
CDRW 1.0 software |
Installed by default |
Sun Enterprise 10000 SSP 3.4 software |
Optional |
Alternate Pathing 2.3.1 software |
Optional |
Capacity On Demand (COD) 1.0 software |
Optional |
Netra ct Platform software |
Optional |
Netra t11 Alarms software |
Optional |
Netra Lights Out Management software |
Optional |
Sun Fire 880 FC-AL Backplane Firmware 1.0 |
Optional |
Insert the Supplement CD into your CD-ROM drive.
The File Manager window is displayed.
In a shell, become superuser using the su command and the superuser password.
Type:
# /usr/sbin/pkgadd -d /cdrom/cdrom0/directory/Product package_names |
or:
# cd /cdrom/cdrom0/directory/Product # pkdadd -d . package_names |
where directory is the software product directory from Table 3-3 and package_names are the package names from Table 3-3.
The argument to the -d option must be a full path name to a device or directory. If you do not specify the device on which the package resides, pkgadd checks the default spool directory (/var/spool/pkg). If the package is not there, installation fails.
To install a particular product, choose the appropriate packages:
Table 3-3 Software and Packages
Software |
Version |
Directory |
Packages |
---|---|---|---|
Validation Test Suite Software (SunVTS) |
4.5 |
SunVTS_4.5/ |
SUNWvts SUNWvtsmn SUNWvtsx SUNWvtsol |
OpenGL Runtime Libraries |
1.2.1 |
OpenGL_1.2.1/ |
SUNWafbgl SUNWafbgx SUNWffbgl SUNWffbgx SUNWifbgl SUNWifbgx SUNWglh SUNWglrt SUNWglrtu SUNWglrtx SUNWglsr SUNWglsrx SUNWglsrz |
PClauncher/PC file viewer |
1.0.1/1.0.1 |
PC_launcher_1.0.1_PC_fileviewer_1.0.1/ |
SUNWdtpcv SUNWdtpcz SUNWdtpcp |
Remote System Control Server |
2.1 |
RSC_2.1/ |
SUNWrsc SUNWrscd SUNWrscj |
ShowMe TV |
1.3 |
ShowMeTV_1.3/ |
SUNWsmtvh SUNWsmtvr SUNWsmtvt SUNWsmtvu |
SunForum |
3.1 |
SunForum_3.1 |
SUNWdat SUNWdatu |
SunFDDI PCI driver |
3.0 |
SunFDDI_PCI_3.0/ |
SUNWpfd SUNWpfh SUNWpfm SUNWpfu |
SunFDDI SBus driver |
7.0 |
SunFDDI_SBus_7.0/ |
SUNWnfd SUNWnfh SUNWnfm SUNWnfu |
SunHSI PCI driver |
3.0 |
SunHSI_PCI_3.0/ |
SUNWhsip SUNWhsipm SUNWhsipu |
SunHSI SBus driver |
3.0 |
SunHSI_SBus_3.0/ |
SUNWhsis SUNWhsism SUNWhsisu |
Sun Hardware AnswerBook2 |
1.0 |
Sun_Hardware_Answerbook/ |
SUNWabhdw |
Java 3D |
1.2.1 |
Java3D_1.2.1/ |
SUNWj3doc SUNWj3dem SUNWj3drt SUNWj3dut |
SunATM 5.0 |
5.0 |
SunATM_5.0/ |
SUNWatm SUNWatma SUNWatmu |
Alternate Pathing |
2.3.1 |
Alternate_Pathing_2.3.1/ |
SUNWapdocSUNWapdvSUNWaprSUNWapu SUNWabap |
Sun Enterprise 10000 SSP |
3.4 |
System_Service_Processor_3.4/ |
SUNWsspdfSUNWsspdoSUNWsspdrSUNWsspfpSUNWsspidSUNWsspmnSUNWsspobSUNWsspopSUNWssppoSUNWssprSUNWsspstSUNWsspue SUNWuessp |
Sun Enterprise 10000 Capacity On Demand (COD) software and AnswerBook |
1.0 |
Capacity_on_Demand_1.0/ |
SUNWcodSUNWcodbkSUNWcodmn |
Netra ct Platform software |
1.0 |
Netra_ct_Platform_1.0/ |
SUNW2jdrtSUNWctacSUNWcteuxSUNWctevxSUNWctmgx |
Netra t11 Alarms software |
2.0 |
Netra_t11xx_Alarms_2.0/ |
SUNWtsalmSUNWtsalrSUNWtsalu |
Netra Lights Out Management software |
2.0 |
Netra_Lights_Out_Management_2.0/ |
SUNWlommSUNWlomrSUNWlomu |
CDRW |
1.0 |
CDRW_1.0 |
SUNWcdrw |
Sun Fire 880 FC-AL Backplane Firmware |
1.0 |
Sun_Fire_880_FC-AL_Backplane_Firmware_1.0/ |
SUNWfcbpl.u |
If a problem occurs during package installation, information about the problem is displayed, followed by this prompt:
Do you want to continue with this installation?
Respond with either yes, no, or quit.
The SunVTS validation test suite is a diagnostic tool designed to test Sun hardware. By running multiple diagnostic hardware tests, the SunVTS software verifies the connectivity and functionality of most SPARC hardware controllers and devices in a 32-bit or 64-bit Solaris operating environment.
SunVTS provides an infrastructure for programmers to develop their own tests and run them using the SunVTS interface.
You can find the software for the SunVTS application on the Supplement CD. To use the SunVTS software, refer to the SunVTS 5.0 User's Guide, the SunVTS 5.0 Test Reference Manual, and the SunVTS Quick Reference Card.
Table 3-4 describes the main features of the SunVTS environment.
Table 3-4 SunVTS Diagnostic Tool Features
Feature |
Description |
---|---|
SunVTS kernel (vtsk) |
The SunVTS kernel controls all aspects of the testing. It is a daemon designed to stay in the background, and to be used when needed. Upon starting, the SunVTS kernel probes the hardware configuration of the system under test and waits for instructions from a SunVTS user interface. During testing, the SunVTS kernel coordinates the running of individual tests, and manages all the messages (informational and error messages) sent by these tests. |
SunVTS CDE user interface (vtsui) |
This interface is designed to run on top of the Common Desktop Environment (CDE). This user interface provides the means to configure, run, and monitor SunVTS test sessions for local and remote hosts. |
SunVTS TTY user interface (vtstty) |
Because not every system has a monitor, SunVTS has a TTY interface. This ASCII menu-based interface accepts various key sequences to control the test options and the test sessions. It can be used from a terminal, a shell tool, or a remote login session through a modem. |
Running an individual test from the command line |
Besides being run from a SunVTS user interface, each individual hardware test can be run from a UNIX® command line. Running a test alone can be helpful to validate only one piece of hardware. |
Custom test support |
A SunVTS user can run third-party executable test binaries under the SunVTS environment in the way that the test, rather than the SunVTS kernel, fully controls its input argument list and output log files. A user can simply modify the .customtest file provided by SunVTS to make it loosely coupled to the environment. |
Table 3-5 provides a list of SunVTS packages needed to run the SunVTS diagnostic tool.
Table 3-5 SunVTS Packages on the Supplement CD
Includes Packages |
Name |
Description |
---|---|---|
SUNWvts |
Validation Test Suite |
SunVTS kernel, user interface (UI), tests and tools |
SUNWvtsmn |
Validation Test Suite Manual Pages |
Manual pages for SunVTS utilities/binaries |
SUNWvtsx |
Validation Test Suite |
64-Bit Validation Test Suite software |
See "Installing Supplement CD Software".
To use SunVTS software, refer to the SunVTS 5.0 User's Guide in the Solaris 9 on Sun Hardware AnswerBook set. For SunVTS test and quick reference information, refer to the SunVTS 5.0 Test Reference Manual and SunVTS Quick Reference Card.
The Sun OpenGL software for Solaris is the Sun native implementation of the OpenGL application programming interface (API). The OpenGL API is an industry-standard, vendor-neutral graphics library. It provides a small set of low-level geometric primitives and many basic and advanced 3D rendering features, such as modeling transformations, shading, lighting, anti-aliasing, texture mapping, fog, and alpha blending.
The Sun OpenGL 1.2.1 software for Solaris supports the following devices:
Creator Graphics, Creator3D Graphics, Elite3D Graphics, and Expert3D Graphics--OpenGL functionality is accelerated in hardware.
SX, GX, GX+, TGX, TGX+, S24--OpenGL functionality is performed in software.
All Sun SPARC systems equipped with the following frame buffers are supported on the OpenGL 1.2.1 software: the TCX, SX, GX, Creator, Elite3D, and Expert3D families of frame buffers. This includes Ultra desktop, Sun Enterprise, and all the legacy SPARCstation family.
If you have older versions of the Sun OpenGL software for Solaris packages, you must use the pkgrm command to remove them.
Check to see whether any older versions of the OpenGL packages are installed using the pkginfo command.
The pkginfo | egrep -i "OpenGL" command lists any existing OpenGL packages that you have installed.
% pkginfo | egrep -i "OpenGL" application SUNWffbgl Creator Graphics (FFB) OpenGL Support application SUNWglrt OpenGL Runtime Libraries application SUNWglrtu OpenGL Platform Specific Runtime Libraries application SUNWglwrt OpenGL Widget Library application SUNWafbgl Loadable pipeline for UPA Bus Elite3D graphics application SUNWgldoc Solaris OpenGL Documentation and Man Pages application SUNWglh Solaris OpenGL Header Files application SUNWglut Solaris OpenGL Utilities and Example Programs application SUNWglwh Solaris OpenGL Widget Header Files |
To remove the packages, become superuser:
% su Password: superuser password |
Run pkgrm to remove all existing Sun OpenGL software for Solaris packages.
# pkgrm SUNWglrt SUNWglh... |
Table 3-6 lists the packages that are provided with the Sun OpenGL software for Solaris.
Table 3-6 OpenGL Packages
Package Name |
Description |
Default Install Location |
---|---|---|
SUNWglh |
OpenGL header files |
/usr |
SUNWglrt |
OpenGL client-side runtime libraries |
/usr/openwin/lib |
SUNWglsr |
OpenGL generic SPARC software renderer |
/usr/openwin/lib |
SUNWglrtu |
OpenGL libraries specific to UltraSPARCTM |
/usr/openwin/platform/sun4u/lib/GL |
SUNWglsrz |
OpenGL UltraSPARC software renderer |
/usr/openwin/platform/sun4u/lib/GL |
SUNWafbgl |
OpenGL device pipeline for Elite3D graphics accelerators |
/usr/openwin/lib/GL/devhandlers |
SUNWffbgl |
OpenGL device pipeline for Creator and Creator3D graphics accelerators |
/usr/openwin/lib/GL/devhandlers |
SUNWifbgl |
OpenGL device pipeline for Expert3D graphics accelerator |
/usr/openwin/lib/GL/devhandlers |
SUNWglrtx |
Sun OpenGL 64-bit Runtime Libraries |
/usr/openwin |
SUNWglsrx |
OpenGL 64-bit UltraSPARC software renderer |
/usr/openwin/platform/sun4u/lib/sparcv9/GL |
SUNWafbgx |
OpenGL 64-bit device pipeline for Elite3D graphics accelerator |
/usr/openwin/lib/sparcv9/GL/devhandlers |
SUNWffbgx |
OpenGL 64-bit device pipeline for Creator and Creator3D graphics accelerators |
/usr/openwin/lib/sparcv9/GL/devhandlers |
SUNWifbgx |
OpenGL 64-bit device pipeline for Expert3D graphics accelerator |
/usr/openwin/lib/sparcv9/GL/devhandlers |
See "Installing Supplement CD Software".
After installing the packages, do the following:
Exit the window system and restart it so that the window system loads the newly installed GLX server extension.
To verify that the OpenGL libraries are installed correctly, run ogl_install_check.
The ogl_install_check test program prints the version of the OpenGL library and renderer used, and renders a rotating wheel. The program returns the following output when it is run on an UltraSPARC Creator3D:
OpenGL Vendor: Sun Microsystems, Inc. OpenGL Version: 1.2.1 Sun OpenGL 1.2.1 for Solaris |
For diagnostic purposes, the following values should be noted if Solaris OpenGL software problems are seen:
OpenGL Renderer: Creator 3D, VIS OpenGL Extension Support: GL_EXT_texture3D GL_SGI_color_table GL_SUN_geometry_compression GL_EXT_abgr GL_EXT_rescale_normal OpenGL GLX Server: Detail Status Report GLX: Context is direct. GLX: OpenGL Rendering in use GLX: Double Buffering in use GLX: Color Buffer (GLX_BUFFER_SIZE) = 24 bits GLX: Depth Buffer (GLX_DEPTH_SIZE) = 28 bits GLX: Stencil Buffer (GLX_STENCIL_SIZE) = 4 bits GLX: RGBA (True Color/Direct Color) Visual in use OpenGL Library: Detail Status Report Number of color bits (R/G/B/A): 8/8/8/0 Frame Buffer Depth (GL_DEPTH_BITS):28 |
Whenever possible, Sun OpenGL software for Solaris renders directly to the frame buffer, bypassing the X server. This is enabled by Sun's DGA mechanism for locking portions of the screen. However, a Solaris security feature only allows the user who originally logged in to the window system to use DGA to lock portions of the screen. Only owners of the window system have access to DGA.
If you notice poor performance when rendering locally, the cause may be this Solaris security feature. For example, if you start the window system, and another user at the workstation changes to that user's own environment using su, the application will not run via DGA even though the second user is running the application locally.
If you notice slow local rendering, run the ogl_install_check diagnostic program (found in /usr/openwin/demo/GL) to determine whether the application is running via DGA. If the OpenGL GLX server status report from the ogl_install_check program says that the GLX context is indirect, edit the login permissions to enable DGA access for all users.
To give all local users access to DGA, follow these steps:
Become superuser:
% su Password: superuser password |
Edit permissions to allow world read/write access to the following devices:
% chmod 666 /dev/mouse /dev/kbd /dev/sound/* /dev/fbs/* |
This enables DGA access for all users for the duration of the current window system session (subject to X authorization, see xhost(1)).
Edit the /etc/logindevperm file and change the default permissions of all devices listed in the file to 0666 to allow world read/write access.
For example, in the following lines in logindevperm, change 0600 to 0666 so that the next time you log in and restart your window system, it will still be accessible by all users.
/dev/console 0600 /dev/mouse:/dev/kbd /dev/console 0600 /dev/sound/* # audio devices /dev/console 0600 /dev/fbs/* #frame buffers |
Note that your system is no longer secure.
PC launcher is designed for Solaris users who have access to Windows `98, ME, NT, or 2000 based PC environments
PC launcher provides you with the capability to view and edit PC files and attachments by launching the associated Windows applications and files in the PC environment. PC launcher enables you to launch attachments and files created in the Windows environment.
Software Supplement for The Solaris 9 Operating Environment 10/01 CD
If you don't have the Supplement CD, contact your Sun service representative.
Solaris 9 operating environment
CDE 1.3
32 MB RAM
SunPCiTM card
Software environment
PC Hardware with Windows `98, ME, NT, or 2000 (PCNFSTM/SolsticeTM Network Client)
In order for PC launcher to work, SunPCi and its host workstation must be able to ping each other by `name'. To do this, you must have:
IP connectivity between the two.
Name services (whatever you happen to be using) set up on each so that you can look up the other's name and get its IP address.
Because of the network architecture of SunPCi and the way it shares Ethernet access with its host, the SunPCI and host cannot see each other on the network.
To work around this, use an IP routing system (a "real" router, another Sun system, an NT system, etc.) on the same subnet to act as a proxy router.
You must have account access to the IP router you have selected, since you must add two routes to it.
For example, based on following setup:
SunPCi IP = 10.0.0.1
Host workstation IP = 10.0.0.2
Router IP = 10.0.0.3
you need to do the following:
On the host workstation:
route add 10.0.0.1 10.0.0.3 1
You can add an /etc/rc script to make this happen at every reboot.
On the routing proxy:
route add 10.0.0.2 10.0.0.3 0
route add 10.0.0.1 10.0.0.3 0 (or the equivalent)
You must add routes to all three systems in this fashion in order for this to work. Do NOT assume that "standard network default routers" or anything else will provide similar functionality; they will not.
After doing this, verify that the SunPCi can ping its host by IP, and vice versa. Once that works, make sure the systems can ping each other by name; add entries to the appropriate naming services if they cannot. On UNIX, examples of naming services are DNS or /etc/hosts. Windows can use DNS or the hosts file as well. Consult your system administrator to add these entries, based on your setup. Once the systems can ping each other by name, PC launcher installs.
For further assistance with installation of SunPCi, refer to the following publications:
SunPCi Installation Guide
SunPCi Release Notes
SunPCi 2.1 Windows NT Installation Guide
See "Installing Supplement CD Software".
You configure PC launcher by specifying your setup in the three steps on the PC launcher Configuration window.
Before configuring, you must have the following:
A network host name and network connectivity between your Solaris and Windows environments.
Your UNIX home directory mapped in your Windows environment.
From the CDE Toolbar, start the Application Manager.
Click Configure PC launcher under the Desktop controls. The PC launcher Configuration window is displayed. Answer the questions in the following three steps.
Click OK.
PC-type documents can be opened for viewing and editing through the Sun PCi card whenever you double-click a document. If you want to do "quick" viewing, select Let Solaris handle the file and PC file viewer is invoked. For editing, use the right-mouse button and select Open In Emulator.
From SunPCi, run h: \.dt\bin\win9x\intel\sdtpcactiond.exe. This step assumes h: is mapped to your UNIX home directory.
From the CDE toolbar, start the Application Manager.
Click Configure PC launcher under the Desktop controls then select or enter the following:
On-Board PC Emulator and SoftWindows.
Hostname
Let Solaris handle the file
PC-type documents can be opened for viewing and editing with a right-mouse double-click. If you selected "Let Solaris handle the file" when you configured PC launcher, then double-clicking on a file will launch PC file viewer.
Click OK.
From the software environment run:
h: \.dt\bin\win9x\intel\sdtpcactiond.exe |
This step assumes h: is mapped to your UNIX home directory.
From the CDE toolbar, start the Application Manager.
Click Configure PC launcher under the Desktop Applications then select or enter the following:
Click OK.
From Deskside PC run:
h: \.dt\bin\win9x\intel\sdtpcactiond.exe |
This step assumes h: is mapped to your UNIX home directory.
The CDE front panel and CDE workspace can be populated with an icon representing the PC environment, such as SunPCi. To do this, drag and drop OpenInSunPCi from the Desktop Applications in Application Manager, onto the Front Panel.
If you did not configure PC launcher, then the first time you open PC launcher, the PC launcher Configuration window will display. This is where you will configure PC launcher. You only need to configure PC launcher once.
Identification of many popular PC file formats in CDE allows you to select and launch them in your preferred PC environment, such as SunPCI. A right mouse click on these files gives you the three following choices in the menu:
Open--the double-click action.
OpenInEmulator--launches the file in your preferred hardware, such as SunPCi (or any software emulator).
OpenInRemotePC--launches the file in a standalone networked PC.
You can drag and drop Windows shortcuts onto the front panel. You can also put shortcuts on the CDE workspace by creating a windows short cut in your UNIX home directory and using dtfile to drag and drop. Refer to Windows help on creating shortcuts, and CDE help to get more information on drag and drop.
Double-click on the shortcut from the Solaris desktop.
The associated applications must be available to you. This procedure makes the Solaris desktop act like a Windows desktop. You can keep all your relevant applications inside the Solaris CDE front panel and CDE workspace and run them by double-clicking on them.
Double-click on the file (exe) and run inside the PC environment (for example, SunPCi).
Highlight the text you want to copy and select Copy from the Edit menu.
Click the place you want to paste the text, and select Paste from the Edit menu.
Click on the file and select View.
Select Print from the File menu
The file prints out on the PC printer.
Using manual steps, you can get to all of the Windows Start Menu choices in the CDE Application Manager.
Start Windows Explorer.
Copy C: \Window\StartMenu\ to H: \.dt\appmanager.
Start Application Manager.
Go to the desktop controls.
Click Reload Application.
Reconfigure PC launcher on the Configuration window.
Remove the PC's hostname in Step 2 on the PC launcher Configuration window.
Change your selection in Step 1 on the PC launcher Configuration window.
Help for PC launcher is available through the Help menu at the bottom of the PC launcher Configuration window.
The PC file viewer software provides you with an application to view popular PC file formats such as Microsoft Word, PowerPoint, Excel, Lotus 1-2-3, and AutoCAD. Use the viewer to choose a file and to copy and paste information from the viewer to another application, such as a text editor. CDE applications will be able to identify these filetypes and launch this application by double-clicking on the icon in your mail attachment or from File Manager (dtfile).
PC file viewer supports 17 different file types:
Word Processing Formats
Microsoft Word for Windows versions through 7.0 and Word 97
Microsoft Windows Works versions through 4.0
Word Perfect for Windows versions through 7.0
AMI/AMI Professional versions through 3.1
Spreadsheet Formats
Microsoft Excel Windows versions 2.2 through 7.0 and Excel 97
Microsoft Excel Chart versions 2.x through 7.0
Microsoft Windows Works versions through 4.0
Lotus 1-2-3 Windows versions through 6.x
Lotus 1-2-3 Chart Windows versions through 5.0
QuattroPro for Windows versions through 7.0
Presentation Formats
Microsoft PowerPoint versions through 7.0 and PowerPoint 97
Corel Presentation versions through 7.0
Freelance versions 1.0 and 2.0
Graphics Formats
BMP--Windows
DXF--versions through 13
GEM--bitmap and vector
PIC--Lotus
PC file viewer is limited to the following products and configurations for this Solaris release:
SPARC architecture ONLY
Printing is not supported
The following limitations are related to displaying items in a supported file:
Charts are not supported in QuattroPro.
Text that is designed to be shown vertically is shown horizontally in the viewer. This vertical text may overlap adjacent cells making reading what is in them difficult.
Figures and footers are aligned with the anchors in the text. If font sizes on the viewing system are not identical to those on the authoring system, then anchored objects will not be at the appropriate place in the text.
There is limited support for incremental shading in presentation file formats
There is no support for drawing objects in Microsoft Word and Lotus.
Borders in Word Perfect and AmiPro files are not supported
Copy & Paste does not work for Japanese text in Microsoft Office applications.
All of the above limitations also exist in the Microsoft Windows version of the product from Inso Corporation.
There is no support for OLE objects.
If a font that is used in a document is not on the system, the default system font is used and the viewed text may look different than what was seen in the authoring application.
If a special character is used in a document that is not in the available character set, it is replaced by an asterisk in the document as shown by the file viewer.
See "Installing Supplement CD Software".
Open File Manager (dtfile).
Go to the /opt/SUNWdtpcv/bin directory.
The PC file viewer icon appears there.
Open the CDE front panel where you want the icon.
For example, the Application or File sub-folder.
Drag and drop the PC file viewer icon from File Manager to InstallIcon in the selected subfolder.
Launch PC file viewer by clicking on the icon in the CDE front panel.
You can also promote the icon to appear on the front panel by default.
ShowMe TV is a television system for local- and wide-area networks. You can use it to view and broadcast live or prerecorded video programs on your network. Here are some examples of how you can use ShowMe TV:
Broadcast and view training courses
Lectures
Corporate messages
Monitor important news events
ShowMe TV contains the following components:
ShowMe TV Receiver
ShowMe TV Transmitter
ShowMe TV Address Book
Table 3-7 lists the packages that are provided with ShowMe TV.
Table 3-7 ShowMe TV Packages
Package Name |
Description |
Default Install Location |
---|---|---|
SUNWsmtvh |
Online help binaries and documentation |
/opt/SUNWsmtv |
SUNWsmtvr |
ShowMe TV receiver application and support files |
/opt/SUNWsmtv |
SUNWsmtvt |
ShowMe TV transmitter application and support files |
/opt/SUNWsmtv |
SUNWsmtvu |
Support utilities |
/opt/SUNWsmtv |
If you have ShowMe TV 1.1, 1.2, or 1.2.1 installed, you need to remove it before installing ShowMe TV 1.3.
To remove ShowMe TV 1.1, type:
# pkgrm SUNWsmUt1 SUNWstv SUNWstvs |
If you have an earlier release of ShowMe TV 1.2 installed, you need to remove it before installing any new software packages.
To remove ShowMe TV 1.2 or 1.2.1, type:
# pkgrm SUNWsmtvt SUNWsmtvu SUNWsmtvr SUNWsmtvh |
See "Installing Supplement CD Software".
The Supplement CD contains the ShowMe TV User's Guide in the following languages:
French
German
Spanish
Italian
Swedish
Japanese
Korean
Simplified Chinese
Traditional Chinese
The /cdrom/cdrom0/ShowMeTV1.3/Docs/UserGuide directory on the Supplement CD contains the following files:
Table 3-8 ShowMe TV Translated Documents
File Name |
Description |
---|---|
UG_en.ps |
English PostScript(TM) file |
UG_de.ps |
German PostScript file |
UG_fr.ps |
French PostScript file |
UG_es.ps |
Spanish PostScript file |
UG_it.ps |
Italian PostScript file |
UG_sv.ps |
Swedish PostScript file |
UG_ja.ps |
Japanese PostScript file |
UG_ko |
Korean HTML files |
UG_zh |
Simplified Chinese HTML files |
UG_zh_TW |
Traditional Chinese HTML files |
To view the desired PostScript manual, type the following at the command line:
# imagetool filename |
To print the manual, either use the File menu in Image Tool or type the following at the command line:
# lp filename |
To view the manuals in HTML format, use a Web browser and type the following in the address field:
file:/cdrom/cdrom0/ShowMeTV1.3/Docs/UserGuide/directory |
If you have copied the HTML files to a different directory, type in the path to that directory. Open the table of contents to determine which file to open.
Sun Remote System Control (RSC) is a secure server management tool that lets you monitor and control a Sun Enterprise 250, Sun Fire 280R, or Sun Fire 880 server over modem lines and over a network, using Solaris operating environment or Microsoft Windows clients. RSC can also notify you when server problems occur. RSC provides remote system administration for geographically distributed or physically inaccessible systems. All hardware functionality required to support RSC is already included with your Sun Enterprise 250, Sun Fire 280R, or Sun Fire 880 server.
The Sun Remote System Control for Sun Servers software is provided on the Supplement CD. For installation information, see "Installing Supplement CD Software". For configuration information for Remote System Control, see Remote System Control (RSC) User's Guide.
SunForum is a data conferencing product for Sun workstations. It is based on the T.120 standard, which enables your Sun system to conference over intranets and the Internet with other T.120 products, such as Microsoft NetMeeting and PictureTel LiveShare Plus, version 4.0. SunForum includes the following features:
View and control applications shared from other UNIX or PC machines that are based on the T.120 protocol.
Share local Solaris applications, which can be viewed and controlled by any conference participant.
Exchange ideas and data using the whiteboard, clipboard, chat, and file transfers.
See "Installing Supplement CD Software".
You can read information about SunForum online. You can access help from the Help menu located on any SunForum menu bar.
The following software is provided on the Supplement CD contained in your Solaris 9 Media Kit:
SunFDDI PCI driver software
SunFDDI SBus driver software
SunHSI PCI driver software
SunHSI SBus driver software
SunFDDI supports booting from the 32-bit kernel or the 64-bit kernel. SunFDDI will attach to whichever you choose to boot from with no special user interaction.
Before installing driver software from the Supplement CD, make sure that you have already installed the adapter hardware. Refer to the appropriate Platform Notes for more information.
See "Installing Supplement CD Software".
Refer to the following platform notes for more information:
Platform Notes: Sun FDDI Adapters
Platform Notes: The Sun GigabitEthernet Device Driver
Platform Notes: The SunHSI/P Device Driver
Platform Notes: The SunHSI/S Device Driver
Platform Notes: SunATM Driver Software
Platform Notes: The hme FastEthernet Device Driver
Platform Notes: The eri FastEthernet Device Driver
Platform Notes: Sun GigaSwift Ethernet Device Driver
Platform Notes: Sun Quad FastEthernet Device Driver
VLANs: Virtual Local Area Networks (VLANs) are commonly used to split up groups of network users into manageable broadcast domains, to create logical segmentation of workgroups, and to enforce security policies among each logical segment. With multiple VLANs on an adapter, a server with a single adapter can have a logical presence on multiple IP subnets. By default, 512 VLANs can be defined for each VLAN-aware adapter on your server.
If your network does not require multiple VLANs, you can use the default configuration, in which case no further configuration is necessary.
VLANs can be created according to various criteria, but each VLAN must be assigned a VLAN tag or VLAN ID (VID). The VID is a 12-bit identifier between 1 and 4094 that identifies a unique VLAN. For each network interface (ce0, ce1, ce2 and so on), 512 possible VLANs can be created. Because IP subnets are commonly used, it's best to use IP subnets when setting up a VLAN network interface. This means that each VID assigned to a VLAN interface of a physical network interface will belong to different subnets.
Tagging an Ethernet frame requires the addition of a tag header to the frame. The header is inserted immediately following the Destination MAC address and the Source MAC address. The tag header consists of two bytes of Ethernet Tag Protocol Identifier (TPID, 0x8100) and two bytes of Tag Control Information (TCI). Figure 3-1 shows the Ethernet Tag Header format.
Create one hostname.cenum file (hostname6.cenum file for IPv6) for each VLAN which will be configured for each adapter on the server, using the following naming format that includes both the VID and the physical point of attachment (PPA):
VLAN logical PPA = <1000 * VID> + <Device PPA> ce123000 = 1000*123 + 0
Example: hostname.ce123000
This format limits the maximum number of PPAs (instances) you can configure to 1000 in the /etc/path_to_inst file.
For example, on a server with the Sun GigabitEthernet/P 3.0 adapter having an instance of 0, that belongs to a member of two VLANs, with VID 123 and 224, you would use ce123000 and ce224000, respectively, as the two VLAN PPAs.
Use the ifconfig(1M) to configure a VLAN virtual device, for example:
# ifconfig ce123000 plumb up # ifconfig ce224000 plumb up |
The output of ifconfig -a on a system having VLAN devices ce123000 and ce224000:
# ifconfig -a lo0: flags=1000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4> mtu 8232 index 1 inet 127.0.0.1 netmask ff000000 hme0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 inet 129.144.131.91 netmask ffffff00 broadcast 129.144.131.255 ether 8:0:20:a4:4f:b8 ce123000: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 3 inet 199.199.123.3 netmask ffffff00 broadcast 199.199.123.255 ether 8:0:20:a4:4f:b8 ce224000: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 4 inet 199.199.224.3 netmask ffffff00 broadcast 199.199.224.255 ether 8:0:20:a4:4f:b8 |
On the switch, set VLAN tagging and set VLAN ports to coincide with the VLANs you've set up on the server. Using the examples in Step 2 , you would set up VLAN ports 123 and 224 on the switch.
Refer to the documentation that came with your switch for specific instructions for setting VLAN tagging and ports.
The Java 3D 1.2.1 API is a set of classes for writing three-dimensional graphics applications and 3D applets. It gives developers high level constructs for creating and manipulating 3D geometry and for constructing the structures used in rendering that geometry. Application developers can describe very large virtual worlds using these constructs, which provide Java 3D software with enough information to render these worlds efficiently.
OpenGL 1.1 software or later
JDK 1.2.1 software or later
See "Installing Supplement CD Software".
For SSP installation and update procedures, as well as SSP release notes, see the Sun Enterprise 10000 SSP Installation and Release Notes, a printed copy of which is included in your media kit.
For Capacity on Demand software installation, as well as release notes, see the Sun Enterprise 10000 Capacity on Demand 1.0 Installation Guide and Release Notes, a printed copy of which is included in your server media kit.
The Netra ct Platform 1.0 software on the Supplement CD contains the software required to support environmental monitoring, alarms (RSC software), and SNMP monitoring of the Netra ct servers.
The two current Netra ct servers are the Netra ct800 and the Netra ct400.
The software should not be installed on servers that are not Netra systems.