test

Solaris 7 5/99 Release Notes Supplement for Sun Hardware

Chapter 3 Open Issues

Prestoserve 2.4.2 -- Patch Required

The Prestoserve(TM) 2.4.2 release will not function properly with the Solaris 7 5/99 software environment if the workaround below is not implemented. Below is a partial list of some of the platforms and hardware options that may be affected:

If you installed Prestoserve 2.4.2 and are using a platform or hardware option listed above, you must do the following steps to provide compatibility:

  1. Edit the /etc/system file and add the following information: 

    set fas:fas_enable_sbus64 = 0

  2. Reboot your system.

    Caution - Caution -

    Failure to reboot your system can corrupt data.

A Prestoserve patch (#103043-08) that automatically adds the above information to the /etc/system file is available. If you prefer to make this change using the Prestoserve patch, contact your authorized Sun support provider. If you edit the /etc/system file as described above, you do not need the Prestoserve patch.

If you installed Prestoserve 2.4.2 and are using an Ultra 2 platform (200MHz or 300MHz), you must do the following steps to provide compatibility:

  1. Edit the /etc/system file and add the following information: 

    set fas:fas_enable_sbus64 = 0

  2. Reboot your system.

  3. Use pkgadd to add the SUNWprsto package.

  4. Add the Prestoserve patch (103043-08).

    Note -

    If the above steps are not followed, your Ultra 2 system may panic.

Booting From Partitions Greater Than 2-Gbytes (1234177)

Due to PROM limitations, all sun4c, sun4d, and sun4m architectures will not boot from partitions greater than 2-Gbytes. These systems will fail with the following message: 

bootblk: can't find the boot program

Note -

All sun4u architectures support booting from larger partitions.

One related bug (4023466) reports a problem with re-preinstall where the boot image for large disks creates root partitions greater than 2-Gbytes. System Administrators are cautioned not to use re-preinstall on sun4c, sun4d, and sun4m systems with large root disks (4-Gbytes and greater).

SunFDDI Adapters Cannot Boot Sun4d Diskless Clients (4144414)

Sun4d diskless clients cannot be booted using SunFDDI(TM) adapters (FDDI/S 6.0 or FDDI/P 2.0) installed in servers running the Solaris 7 5/99 operating evironment. If you intend using a Sun4d as a diskless client, deploy it in an ethernet section of your network.

Quad Ethernet Controller--Dynamic Reconfiguration Not Supported

The Quad Ethernet (QE) and Quad Ethernet Controller (QEC) must be configured with other non-Dynamic Reconfiguration (DR) boards. DR does not support QE and QEC on Sun Enterprise X000 platforms running the Solaris 7 5/99 operating environment or compatible versions.

Serial Parallel Controller Driver

Serial Parallel Controller Driver Does Not Support Dynamic Reconfiguration (4177805)

Contact your service provider for availability of patch 106827-01. The patch is not available at the time of this release.

ISDN -- Power Management Not Supported

ISDN does not support the Power Management(TM) suspend and resume features.

/usr/ucblib/sparcv9 is Not Available (4114650)

Any application requiring ucblib will not link or run with the 64-bit Solaris operating environment.

Workaround: No workaround is available at this time. Contact your authorized Sun support provider for more information.

SunScreen SKIP 1.1.1 Not Supported in Solaris 7 5/99 Operating Environment

If you have SunScreen(TM) SKIP 1.1.1 currently installed on your system, you should remove the SKIP packages before installing or upgrading to the Solaris 7 operating environment. The packages you should remove are:

Solstice SyMON Not Supported in Solaris 7 5/99 Operating Environment

If you have Solstice SyMON currently installed on your system, you should remove the SyMON packages before installing or upgrading to the Solaris 7 5/99 operating environment. The packages you should remove are:

For information on the availability of Sun Enterprise SyMON 2.0, go to:

http://www.sun.com/servers/symon.html

SunVTS 3.2 Issues

The following issues apply to the SunVTS(TM) 3.2 product.

New Features in This Release

A new test called sunpcitest was added to support testing of the SunPCi plug-in PCI card.

SunVTS OPEN LOOK User Interface Support

The SunVTS OPEN LOOK user interface may not support the latest SunVTS features. For full feature support, use the SunVTS CDE or TTY interface. The SunVTS OPEN LOOK user interface will be sustained, but not enhanced, as long as OPEN LOOK is supported in the Solaris environment.

Running SunVTS Online Diagnostics through Sun Enterprise SyMON

The SunVTS 3.2 online diagnostics feature (SUNWodu) is not accessible through the SyMON interface.

Instead, you can start SunVTS so it will run safely in an online environment by using the vtsui.online command.

Example: 

# /opt/SUNWvts/bin/vtsui.online -h hostname

For more information about running SunVTS in an online or offline environment, refer to the SunVTS 3.2 User's Guide.

Disk Test (disktest) Mounting Issues

As of SunVTS 3.0, SunVTS disktest by default does not mount any mountable partitions. To have SunVTS mount all partitions which contain a file system, set the environment variable BYPASS_FS_PROBE to 0 (zero), then start SunVTS. For more details, refer to the disktest chapter in the SunVTS 3.2 Test Reference Manual.

The SunVTS User Interface Disappears (4122829)

In some cases, the SunVTS user interface disappears during a SunVTS test session. The SunVTS kernel is still active and the test session may continue to run.

Workaround: Restart the SunVTS user interface.

Example (starting the SunVTS CDE user interface): 

# /opt/SUNWvts/bin/vysui

Some Devices Not Displayed Under Physical Mapping (4228489)

In some cases, some devices that are displayed under logical mapping are not displayed under physical mapping.

Workaround: Choose logical mapping in the SunVTS main window to select devices that do not come up under physical mapping.

ShowMe TV Known Problems

PCMCIA Issues

The following bugs have been filed against PCMCIA:

If the PC ATA, pcata, module is modunloaded the system will appear to hang (4096137)

Description: If there is a PCMCIA I/O card in a slot that has been accessed and the card driver is unloaded (as occurs during modunload -i 0 at the end of multi-user boot) the system will appear to hang. Sometimes removing the card will bring the system back.

Workaround: none

The PCMCIA, pcic nexus, driver, does not support 3.3Volts PC Card (4098998)

Description: The PCMCIA, pcic nexus, driver does not support 3.3V on devices. Cards that are 3.3V and 3.3V/5V will not work properly (seems to hang the system).

Workaround: none

The PC ATA, pcata, disk driver crashes and hangs the system and causes a memory leaks (4106401)

Description: Most attempts to insert/remove and use PCMCIA cards will crash or hang the machine. If it does not crash the machine it can cause memory leaks or create situations where other modules will not load.

Workaround: none

When booting Solaris 7 5/99 operating environment initially with 64-bit kernel the device /dev/term/pc0, PC card serial driver, may not get created (4162969)

Description: When booting Solaris 7 5/99 operating environment initially with 64-bit kernel, /dev/term/pc0 hardware device node for PC card serial device may not be created.

Workaround: Boot the system up with 32-bit kernel first, then reboot with 64-bit kernel.

The PC ATA, pcata, driver panics the 64-bit kernel (4174177)

Description: Inserting the PC card after system init panics the 64-bit Solaris. Booting the 32-bit Solaris and accessing the card will not panic the system. The PC ATA driver is not a 64-bit driver.

Workaround: none

PC File Viewer Issues

Install in the /opt Directory

The Solaris 7 5/99 Sun Hardware Platform Guide provides installation instructions that may indicate that PC file viewer can be installed in a directory other than the default directory. PC file viewer must be installed in the default (/opt) directory.

Known Bugs

Sun Remote System Control (RSC) Release Notes

What's New in This Version

This version of Sun Remote System Control (RSC) includes bug fixes and a new environment variable, tpe_link_test. In addition, the RSC device Internet address has been added to email and pager alert messages.

If you have already installed a previous version of Remote System Control, back up your RSC configuration before installing this version, following the directions in Chapter 2 of the RSC User's Guide, and then restore them after installation when you run the RSC configuration script.

The tpe_link_test variable enables 10BASE-T Ethernet link integrity tests when set to true, the default. If you are using RSC in a hub that does not support Ethernet link integrity tests or that has them disabled, set this variable to false. Changes to this variable take effect after the next RSC reset. The tpe_link_test variable behaves similarly to the OBP environment variable named "tpe-link-test?", which is available on some SPARC platforms.

RSC and the local hub should have Ethernet link integrity tests enabled or disabled consistently. If this setting is not consistent, communication may not be possible.

The following bugs have been fixed since the November 16, 1998 release:

Hardware and Software Configurations Supported for RSC

Supported Server:

Sun Enterprise(tm) 250 server only, running the Solaris(TM) 7 or Solaris 2.6 5/98 operating environment.

The Sun Enterprise 250 flash PROM must be updated to version 3.7.7 or later before installing the RSC software. Failing to do so may cause server and RSC malfunctions. For update instructions and a downloadable image, see the Sun Enterprise 250 Supplement Web page at http://sunsolve2.Sun.COM/sunsolve/E250/flash.html. If you install RSC from the Sun Enterprise 250 Supplement CD, you can update the flash PROM as part of the installation process.

Supported GUI Clients:

Sun JDK version 1.1.6 or a subsequent compatible version is required for GUI support on systems running the Solaris operating environment, and is included in the base Solaris 7 operating environment and the Sun Enterprise 250 Supplement CD. The required version for the Solaris 2.6 operating environment is available at http://www.sun.com/solaris/java. Sun JDK is included in the install package for Windows clients.

Supported CLI Clients:

Ethernet Support:

RSC is designed to function in a 10BASE-T network, and the RSC Ethernet port should be connected to a hub operating at 10-Mbps. If RSC does not respond to an Ethernet request, the first thing to check is that connection is to a 10BASE-T hub.

Uninterruptible Power Supply (UPS):

An American Power Conversion SmartUPS 1000 with PowerChute plus 4.2.2 software was used for testing.

SunVTS:

To run the SunVTS test for RSC on systems running the Solaris 2.6 5/98 operating environment, you must install the unbundled rsctest package. This package is available for download from the RSC Web page at http://sunsolve2.sun.com/sunsolve/E250_RSC/, and is also provided on the Sun Enterprise 250 Supplement CD. The rsctest package is already included in SunVTS version 3.0 and later.

Paging Support:

RSC paging requires that the customer's paging service adhere to the TAP protocol. Paging services in the Americas and Europe generally are TAP-compliant, but this is not necessarily so in other locales.

Testing RSC Paging

Due to the many variables associated with paging, Sun strongly recommends that you test the RSC paging mechanism to insure that your configuration options are set correctly.

The easiest way to test that all the components associated with RSC paging are functioning properly is to use the "rscadm send_event -c" command. This command can be invoked from a UNIX shell and will initiate an RSC alert. If the RSC page_enabled flag is set to true, this alert will send a page to the recipients specified by the page_info1 and page_info2 environment variables.

If RSC fails to send a page, a message similar to the following will be added to the event log:

THU AUG 27 22:31:09 1998 sst4828: 00060006: "Failed to send page alert for recent event"

If RSC successfully transmits a page, no error message is added to theevent log.

RSC can fail to send a page notification for the following reasons:

When a page fails, check the following:

  1. That your modem dip switch and software configuration variables are set correctly.

  2. That all the RSC page_variables (page_info1 and 2, page_init1 and 2, and page_baud1 and 2) are set correctly and match the settings for your paging service.

  3. Insure that your paging service supports the TAP protocol. Check with the paging service to insure that you have the proper phone number and modem configuration parameters.

  4. Attempt to connect with the paging service manually. Refer to the "Troubleshooting Modem Problems" section in Appendix B of the RSC User's Guide for instructions on manually connecting to a TAP paging service.

Troubleshooting

In some cases, it might be desirable to extend the pause period to allow themodem to recognize the dial tone of the phone line. This can be accomplishedon most modems by increasing the value in the S8 register. See documentation that came with your modem for more details.

Known Issues

  1. 4151918: The RSC subtests do not provide adequate failure information.

  2. 4171924: The RSC GUI occasionally reports invalid exceptions when you Logout or Exit.

  3. 4168266: Heavy use of UNIX tcsh shell commands in an RSC console session may stop RSC from responding to requests. Killing the tcsh shell restores RSC to normal behavior.

  4. 4167862: A loghistory error is reported when the "index -n" value you specify is greater than the number of lines in the buffer

  5. 4171929: RSC sometimes reports a fan failure erroneously after a thermal shutdown.

  6. 4145761: An RSC reset is required for changes to the serial_hw_handshake variable (or "Enable Hardware Handshaking" setting in the GUI) to take effect, but should not be required.

  7. 4167651: RSC default configuration settings for pagers do not match modem configuration settings suggested in documentation.

  8. 4171431: The GUI event log output differs from the CLI loghistory output.

  9. 4170988: The RSC GUI Back button for the first instance of Help does not return you to the previous view.

  10. 4172337: The error message displayed for an attempted third telnet or fifth user session needs improvement.

  11. 4162419: In the Windows operating environment, the RSC GUI goes to the background when you cancel an operation after an error message.

  12. 4158400: The message "[Loaded DTD html32 in 142ms]" appears when the RSC Help file is displayed.

  13. 4151674: Clicking on "Set RSC Date and Time" sometimes displays a duplicate image of the "Set RSC Date and Time" option just above the option list, and below the "RSC for <hostname>" title.

  14. 4159618: A GUI reset request and the resulting reset event are recorded in the incorrect order in the RSC event log.

  15. 4159562: The telnet connection resets intermittently when you try to connect to the RSC console from the GUI.

  16. 4159564: The Java Runtime Environment (JRE) may crash in the Windows 95 operating environment when you modify an RSC user account.

  17. 4172331: In the RSC GUI Serial Port settings, there is a typo in the error message for Invalid IP Address.

  18. 4159135: The RSC GUI has no option which shows the information returned by the CLI shownetwork command.

  19. 4157854: Sometimes when a thermistor displays a warning in the Environmental Status window and you refresh the screen, the warning is mistakenly displayed for a different thermistor. Another refresh corrects this problem.

  20. 4216814: Pressing Return in the GUI login screen fails to advance input focus to the next entry field.

SunVTS Test for PGX32 Available

The PGX32 VTS package is currently not bundled with SUNWvts. For version 3.2 refer to Patch #107732. This patch has been incorporated in the S7 5/99 Supplemental CD in the Patch directory.

Copyright Notices

The following copyright information was not included in the Software Supplement for the Solaris 7 5/99 Operating Environment for Sun Computer Systems CD.

SunForum 2.0 Notices:

  1. Copyright Data Connection Limited 1999. Data Connection\256 is a registered trademark of Data Connection Limited in the US and other countries

  2. Copyright Teles Ag 1999

ShowMe TV Notices:

Copyright\256 1993-1994 The Regents of the University of California. All rights reserved. Tous droits re'serve's.

Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:

  1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

  2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

  3. All advertising materials mentioning features or use of this software must display the following acknowledgement: This product includes software developed by the University of California, Berkeley and the Network Research Group at Lawrence Berkeley Laboratory.

  4. Neither the name of the University nor of the Laboratory may be used to endorse or promote products derived from this software without specific prior written permission.

Copyright 1990-1993 GROUPE BULL

Permission to use, copy, modify, and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of GROUPE BULL not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. GROUPE BULL makes no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.

GROUPE BULL disclaims all warranties with regard to this software, including all implied warranties of merchantability and fitness, in no event shall GROUPE BULL be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action, arising out of or in connection with the use or performance of this software.

Copyright 1992 by Stichting Mathematisch Centrum, Amsterdam, The Netherlands.

All Rights Reserved. Tous droits re'serve's.

Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appear in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the names of Stichting Mathematisch Centrum or CWI not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission.

STICHTING MATHEMATISCH CENTRUM DISCLAIMS ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OR MERCHANTABILITY AND FITNESS, IN NO EVENT SHALL STICHTING MATHEMATISCH CENTRUM BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF IR IN CONNECTION WITH THE USE OF PERFORMANCE OF THIS SOFTWARE.

OpenGL is a trademark of Silicon Graphics

Netscape Communicator Notices:

Copyright 1999, Netscape Communications Corporation. All Rights Reserved. Tous droits re'serve's.

Sun Enterprise 10000 SSP 105684-04, 106281-01, and 106282-01 Notices:

This software is copyrighted by the Regents of the University of California, Sun Microsystems, Inc., and other parties. The following terms apply to all files associated with the software unless explicitly disclaimed in individual files.

The authors hereby grant permission to use, copy, modify, distribute, and license this software and its documentation for any purpose, provided that existing copyright notices are retained in all copies and that this notice is included verbatim in any distributions. No written agreement, license, or royalty fee is required for any of the authorized uses.

Modifications to this software may be copyrighted by their authors and need not follow the licensing terms described here, provided that the new terms are clearly indicated on the first page of each file where they apply.

IN NO EVENT SHALL THE AUTHORS OR DISTRIBUTORS BE LIABLE TO ANY PARTY FOR DIRECT, INDIRECT, SPECIAL, INCIDENTAL, OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OF THIS SOFTWARE, ITS DOCUMENTATION, OR ANY DERIVATIVES THEREOF, EVEN IF THE AUTHORS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

THE AUTHORS AND DISTRIBUTORS SPECIFICALLY DISCLAIM ANY WARRANTIES,INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, AND NON-INFRINGEMENT. THIS SOFTWARE IS PROVIDED ON AN "AS IS" BASIS, AND THE AUTHORS AND DISTRIBUTORS HAVE NO OBLIGATION TO PROVIDE MAINTENANCE, SUPPORT, UPDATES, ENHANCEMENTS, OR MODIFICATIONS.

RESTRICTED RIGHTS: Use, duplication or disclosure by the government is subject to the restrictions as set forth in subparagraph (c) (1) (ii) of the Rights in Technical Data and Computer Software Clause as DFARS252.227-7013 and FAR 52.227-19.

Documentation Errata

The following errors in various documents have been reported.

PC launcher Manpage

The sdtpcaction.conf manpage was left out of the manpage packages. Here is the content of the manpage (bug ID 4230365): 

NAME


sdtpcaction.conf - sdtpcaction configuration file

FILE FORMAT
The format of this file is as follows. 
VERSION				: 1.0
SOLARIS_HOST			: Host name of Solaris
DEFAULT				: default PC_TYPE
PC_HOST				: Host name for PC 
PC_TYPE		 		: SunPC | SoftWindows | RemotePC
Optional:
PC_HOME				: Directory shared by PC and Solaris. Can be 
				  used if for security reason the user does not
				  want to map unix home directory to PC.

INITIALIZATION_COMMAND		: command to initialize PC emulator

CLIENT_NAME			: ICCCM client name of PC emulator window
These records are stored for each Solaris hostname.

FILES
 	$HOME/.dt/.sdtpcaction.conf   PC Proxy configuration file

Platform Notes: The hme SunFastEthernet Device Driver Guide

The Platform Notes: The hme SunFastEthernet Device Driver Guide lists the wrong default value for the adv_10fdx_cap parameter. The correct default value for this parameter is 1 for 10Mbit/sec full-duplex capable.See bug Id 4217150 for more information.

Sun Enterprise 10000 Dynamic Reconfiguration User's Guide Documenation Errata

The Sun Enterprise 10000 Dynamic Reconfiguration User's Guide that was released on the Sun Hardware Supplements CD-ROM contains improperly exported illustrations. Please use the corrected version on docs.sun.com.

Alternate Pathing Documenation Errata

The Sun Enterprise Server Alternate Pathing User's Guide that was released on the Sun Hardware Supplements CD-ROM contains improperly exported illustrations. Please use the corrected version on docs.sun.com.

Locale-Specific Bugs

SunForum BugID 4234195

In Helpful Information for WebStart installation, a link to the SunForum html file is broken. This problem can be seen in German, French, Italian, Spanish, and Swedish languages for the Desktop Configuration.If it's linked correctly, the following information is displayed:SunForum 2.0:SunForum is a suite of collaborative tools based on the International Telecommunications Union (ITU) T.120 standards. SunForum consists of a Share Application program, a Shared Whiteboard application, File Transfer utility and a Chat Utility.Requirements for SunForum 2.0:You need to allocate about 11 MB of disk space to this product.

ShowMe TV BugID 4234201

In "Co-Packaged Software Topics: Contents" for WebStart installation lists wrong version for ShowMe TV. ShowMe TV 1.2.1 is included in this release, not ShowMe TV 1.3. This problem can be seen in German, French, Italian, Spanish, and Swedish languages for the Desktop Configuration.

PC launcher Installation and Configuration

Audience

PC launcher is designed for Solaris users who have access to Windows `95 or `98 based PC environments

What is PC launcher?

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.

PC launcher Installation Requirements

You must have the Software Supplement for the Solaris 7 8/99 Operating Environment for Sun Computer Systems CD. If you don't have the Supplement CD, contact your Sun service representative.

System Requirements

Sun Workstation

Network PC Environment with one of the following:

PC launcher Installation

SunPCi Requirements

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:

  1. IP connectivity between the two.

  2. 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, they cannot see each other on the network.

To work around this, you need to 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.

Note -

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:

  1. On SunPCi:

    route add 10.0.0.2 10.0.0.3

    Note -

    You can create a Windows BAT file with this in it and put it in your StartUp folder so that it gets run at every login.

  2. On the host workstation:

    route add 10.0.0.1 10.0.0.3 1

    Note -

    You can add an /etc/rc script to make this happen at every reboot.

  3. 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)

Caution - Caution -

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 that they 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 will install.

For further assistance with installation of SunPCi, refer to the following publications:

Installing PC launcher Packages Using Sun WebStart

  1. Insert the Software Supplement for the Solaris 7 8/99 Operating Environment for Sun Computer Systems CD (assuming the CDROM is automatically mounted by the vold daemon).

  2. In a shell, change directories to /cdrom/cdrom0, become root, and at the prompt, type: 

    # installer

  3. Once Installer is Up and Running, click "Next".

  4. Select "Custom Install" then click "Next".

  5. Deselect any other products that you do not want to install at this time by clicking "No Install".

  6. Ensure that PC FileViewer/PC launcher is selected for "Default Install" then click "Next".

  7. Click "Install Now".

  8. Log out of the system (this completes the installation).

  9. Log back into the system (this initializes the new functionality).

Installing PC launcher Using pkgadd

  1. Insert the Software Supplement for the Solaris 7 8/99 Operating Environment for Sun Computer Systems CD (assuming the CDROM is automatically mounted by the vold daemon).

  2. In a shell, change directories to /cdrom/cdrom0/Product, become root, and at the prompt, type: 

    # pkgadd -d `pwd` SUNWdtpcz SUNWdtpcv SUNWdtpcp

  3. Log out of the system (this completes the installation).

  4. Log back into the system (this initializes the new functionality).

Configuring PC launcher

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:

Configuring for PCi

  1. From the CDE Toolbar, start the Application Manager.

  2. Click "Configure PC launcher" under the Desktop controls. The PC launcher Configuration window is displayed. Answer the questions in the following 3 steps.

    1. On-Board PC Emulator and SunPCI (default)

    2. Enter your Sun PCi's hostname (default)

    3. Let PC Emulator handle the file

  3. Click "OK".

    Note -

    PC documents are 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".

  4. From SunPCi run h: \.dt\bin\win9x\intel\sdtpcactiond.exe (assuming H: is mapped to your unix home directory).

Configuring for the Software Environment

  1. From the CDE Toolbar, start the Application Manager.

  2. Click "Configure PC launcher" under the Desktop controls.

    1. On-Board PC Emulator and SoftWindows.

    2. <Hostname>

    3. Let Solaris handle the file

      Note -

      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.

  3. Click "OK".

  4. From Software Environment run: 

    h: \.dt\bin\win9x\intel\sdtpcactiond.exe

    (assuming H: is mapped to your unix home directory).

Configuring for a Deskside PC

  1. From the CDE Toolbar, start the Application Manager.

  2. Click "Configure PC launcher" under the Desktop Applications.

    1. Standalone PC

    2. <Hostname>

    3. Let the Standalone PC handle the file

      Note -

      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.

  3. Click "OK".

  4. From Deskside PC run: 

    h: \.dt\bin\win9x\intel\sdtpcactiond.exe

    (assuming H: is mapped to your unix home directory).

Using PC launcher

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.

Working With Files

Windows Files

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:

Windows shortcuts can be dragged and dropped onto the Front Panel. They can also be put on the CDE workspace. To do this, create a windows short cut in your unix home directory and use dtfile to drag and drop. Please refer to Windows help to create short cut, and CDE help to get more information on drag and drop.

To open applications or datafiles, double-click on the shortcut from the Solaris desktop. This does require that you have the associated applications available to you. This 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.

Windows Binary Files

These files (exe) can be double-clicked and run inside the PC environment (for example, SunPCi).

Copy and Paste Text

Highlight the text you want to copy and select copy from your Edit menu.

Then click the place you want to paste the text, and select paste from your edit menu.

View and Search

View -- click on the file and select View.

Search -- under the Edit menu, select Find/Change; enter the name of the file into the Find field and click Find.

Print Files

Select 'Print' from your File menu and your file will print out on the PC printer.

Other Features

Bring Windows Start Menu to CDE

Using manual steps, you can get to all of the Windows Start Menu choices in the CDE Application Manager. To achieve this:

  1. Start Windows explorer.

  2. Copy C: \Window\StartMenu\ to H: \.dt\appmanager.

  3. Start Application Manager.

  4. Go to the Desktop controls.

  5. Click "Reload Application".

Login On a Different Machine

Reconfigure PC launcher on the Configuration window.

Reconfigure PC launcher

Remove the PC's hostname in Step 2 on the PC launcher Configuration window.

Switch Between Targets

Change your selection in Step 1 on the PC launcher Configuration window.

Getting Help for PC launcher

Help for PC launcher is available through the Help menu at the bottom of the PC launcher Configuration window.