PC World Komputer 1999 March/PCWK3A99.iso/Unixware/INFO/UW7/RTRNOTES.TXT

Text File | 1998-08-19 | 201.9 KB | 5,343 lines

 Copyright 1998 The Santa Cruz Operation, Inc.         All rights reserved.


 About this book

    This book contains critical information that supplements the UnixWare
    7.0.1 Installation Guide, UnixWare 7 System Handbook and online
    documentation.  It also includes information on runtime features and
    limitations that are not covered in New features and Differences for SCO
    OpenServer and SCO UnixWare 1 and 2 users in the online documentation.

    This book is available in French, German, Spanish and Japanese.


 Further information

    See the UnixWare online documentation for information about using
    UnixWare.


 Support services

    SCO offers a World Wide Web site which contains information about SCO
    products and services.

    If you are connected to the Internet, use Netscape(TM) (provided with
    UnixWare) or another World Wide Web browser to access the following URL
    (Uniform Resource Locator) to get to the SCO World Wide Web home page
    (http://www.sco.com/).


 Typographical conventions

    This publication presents commands, filenames, keystrokes, and other
    special elements as shown here:


    Example:     Used for:

    lp or lp(1)  commands, device drivers, programs, and utilities (names,
                 icons, or windows);  the letter in parentheses indicates the
                 reference manual section in which the command, driver,
                 program, or utility is documented

    /new/client.list
                 files, directories, and desktops (names, icons, or windows)

    root         system, network, or user names

    filename     placeholders  (replace with appropriate name or value)

    <Esc>        keyboard keys

    Exit program?
                 system output  (prompts, messages)

    yes or yes   user input

    ``Description''
                 field names or column headings  (on screen or in database)

    Cancel       button names

    Edit         menu names

    Copy         menu items

    File != Find != Text
                 sequences of menus and menu items

    open or open(2)
                 library routines, system calls, kernel functions, C
                 keywords;  the letter in parentheses indicates the reference
                 manual section in which the file is documented

    $HOME        environment or shell variables

    SIGHUP       named constants or signals

    ``adm3a''    data values

    employees    database names

    orders       database tables

    buf          C program structures

    b.b_errno    structure members


 How can we improve this book?

    What did you find particularly helpful in this book?  Are there mistakes
    in this book? Could it be organized more usefully? Did we leave out
    information you need or include unnecessary material?  If so, please tell
    us.

    To help us implement your suggestions, include relevant details, such as
    book title, section name, page number, and system component.  We would
    appreciate information on how to contact you in case we need additional
    explanation.

    _________________________________________________________________________
       NOTE  For answers to technical questions, please contact your
       software vendor or your support representative.  Technical
       Publications is not qualified to give technical support.
    _________________________________________________________________________


    To contact us, write to us at:


       Technical Publications
       Attn:  Customer Feedback Team
       The Santa Cruz Operation, Inc.
       PO Box 1900
       Santa Cruz, California  95061-9969
       USA


    or email us at:


       [e-mail]  or   ...  uunet!sco!techpubs


    Thank you.





 Chapter 1
 Read this before installation

    UnixWare 7.0.1 is an update to the UnixWare 7 Operating System that
    provides significant new features and enhancements. UnixWare 7.0.1 can be
    installed in either of these ways:

    +  By performing a full installation of UnixWare from the UnixWare 7.0.1
       installation media. Refer to the notes in this chapter and the
       instructions in Chapter 3, ``Installing a UnixWare 7 system'', in the
       Installation Guide.

    +  By performing a layered installation of the UnixWare 7.0.1 update
       packages on top of a previously installed UnixWare 7 system. Refer to
       the installation instructions in Chapter  3, ``Updating your system''.

    This chapter covers the following areas:

    +  ``Installation hardware requirements''

    +  ``Network installations''

    +  ``Installable components''

    +  ``Upgrading SCO UnixWare 2.1 VxVM to UnixWare''

    +  ``Installation limitations and workarounds''

    +  ``Installation troubleshooting''


 Installation hardware requirements

    Before installing UnixWare, make sure your system has at least the
    minimum required system memory and hard disk space.  See the Installation
    Guide for information.

    _________________________________________________________________________
       NOTE  A primary hard disk of 1GB or larger is recommended.

       The minimum supported hard disk size is 500MB, but a full
       installation is not possible on this size disk.
    _________________________________________________________________________


 Network installations

    The UnixWare 7.0.1 Installation CD-ROM contains images of all diskettes
    used to install and troubleshoot UnixWare. These are found in the
    /info/images directory.

    Your distribution does not contain media for the Magic diskette or the
    Network Installation Utilities diskettes. If you want to create diskettes
    from the images on the CD-ROM:

    1.  Log onto your UnixWare system as root.

    2.  Mount the CD-ROM. Enter:

           mount -F cdfs -r /dev/cdrom/cCbBtTlL /mnt

        where C, B, T, L are the controller, bus, target (SCSI ID), and
        logical unit number (LUN) of your CD-ROM device.

        _______________________________________________________________________
           NOTE  In many cases, you can substitute the wildcard * in place
           of the full device name; for example /dev/cdrom/*.
        _______________________________________________________________________


        Once the update has been installed, the CD-ROM drives can be accessed
        as cdrom1, cdrom2, cdrom3 and so on.

    3.  Enter:

           cd /mnt/info/images/


    4.  Format a blank diskette by inserting it into the primary diskette
        drive and entering:

           format -V /dev/rdsk/f03ht

        You can skip this step if the diskette is already formatted.

    5.  With a formatted diskette in the primary drive, enter:

           dd if=image of=/dev/rdsk/f0t bs=32b

        where image is the name of the source file for the diskette you are
        creating (for example, netinstall.image.1).

    6.  Verify the checksum, by comparing the value listed in
        /mnt/info/images/sums with the result of this command:

           sum -r /dev/rdsk/f03ht

        The checksums should match.

    From an SCO OpenServer(TM) machine, the syntax in steps 2, 4, 5, and 6
    is:

       mount -f HS,r /dev/cd0 /mnt
       format /dev/rfd0135ds18
       dd if=image.name of=/dev/rfd0 bs=32b
       sum -r /dev/rfd0


    Network installation onto systems of 16MB or less is not supported in
    this release.

    _________________________________________________________________________
       NOTE  This version of UnixWare 7 does not provide any drivers for
       PC CARD (PCMCIA) network interface adapters.  This means that while
       UnixWare 7 can be installed from CDROM onto a laptop computer,
       network installations onto a laptop computer are not currently
       supported.

       PCMCIA drivers from SCO(r) UnixWare(r) 2.1 will work on UnixWare 7,
       but these must be added after installation and cannot be used for
       network installations. In addition, SCO is continually updating the
       available drivers for UnixWare 7. See the SCO Compatible Hardware
       Web Pages (http://www.sco.com/chwp) for the latest information on
       PCMCIA network adapter drivers for UnixWare 7.
    _________________________________________________________________________



 Installable components

    See Appendix A, ``System profiles, services, and packages'' for a list of
    installable components.


 Upgrading SCO UnixWare 2.1 VxVM to UnixWare

    You can preserve a VxVM filesystem that is not your root or /usr
    filesystem from SCO UnixWare 2.1. To do so, follow this procedure:

    1.  Ensure that the VxVM ODM packages are installed and the filesystem is
        configured as you require it on SCO UnixWare 2.1.

    2.  Mount the filesystem.

    3.  Create an s5 filesystem on a floppy diskette as follows:

           # format /dev/rdsk/f03ht
           # mkfs -F s5 /dev/dsk/f03ht 2880


    4.  Mount the diskette and copy the necessary files and directories as
        follows:

           # mount -Fs5 /dev/dsk/f0t /mnt
           # find  /etc/vx/reconfig.d \
           /etc/vx/tempdb  \
           /etc/vx/volboot \
           /etc/vfstab | cpio -pd /mnt


    5.  Unmount the diskette and install UnixWare 7:

           # umount /mnt

        ________________________________________________________________________
           NOTE  After the installation of UnixWare 7 do not perform a
           vxinstall.
        ________________________________________________________________________


    6.  Copy the files from the diskette back to the UnixWare system:

           # mount -Fs5 /dev/dsk/f0t /mnt
           # cd /mnt
           # find  /etc/vx/reconfig.d \
           /etc/vx/tempdb  \
           /etc/vx/volboot | cpio -pd /

        Merge /mnt/vfstab and /etc/vfstab by hand.

    7.  If the mountpoint used in SCO UnixWare 2.1 (in step 2) does not
        exist, create it:  # mkdir mount_point

    8.  Remove the file /etc/vx/reconfig.d/state.d/install-db:

           # rm /etc/vx/reconfig.d/state.d/install-db


    9.  Reboot the system.

    10. Mount the VxVM filesystem or volume:

           # mount /mount-point



 Installation limitations and workarounds

    SCO has tested the installation of UnixWare 7 on a wide range of
    hardware. Note the following possible problems that have been identified
    during testing.  These notes supplement or correct the installation
    instructions in the Installation Guide.

    _________________________________________________________________________
       NOTE  Before you install any new system software, you should always
       back up your current system and verify that the backup was
       successful.
    _________________________________________________________________________

    _________________________________________________________________________
       NOTE  In some cases, you may need to switch to the character
       console (vt0) to resolve installation problems. To do this, press
       <Alt><SysReq>H.  To return to the graphical installation screen,
       press <Alt><SysReq><F1>.
    _________________________________________________________________________


    +  Please note that the fix incorporated into SCO UnixWare 2.1.3 to allow
       disks greater than 2GB in size to be backed-up with the -e option to
       emergency_rec has not been included in UnixWare 7.0.1.  A PTF may be
       created to fix this -- please check the SCO BBS.

    +  If you configure a non-existent network adapter then try to remove it
       and configure the correct one, the system may hang. If this happens,
       you must restart the system.
    +  If you do not know or are unsure of the network parameters for your
       network adapter, TCP/IP, IPX/SPX, or NIS, you should defer
       configuration until after installation rather than misconfigure these
       components. In most cases, the <F8> option is displayed at the bottom
       of the screen when you are able to defer configuration.

    +  Debugging is set switched off by default during installation.  To
       switch debugging on, set the boot parameter IVAR_DEBUG_ALL=1. See
       boot(1M) for information on setting boot parameters.

       When debugging is switched on, the installation process stores logs
       for each of the ui_modules in separate files in either /tmp/log or
       /isl/log directories.  (Logs are no longer written to stderr, which
       used to reside in the /tmp directory.)

       The logs are in two different locations depending on where you are
       during the installation:

       -  If you have not mounted the hard disk the logs are stored in
          /tmp/log.

       -  If the hard disk has been mounted the logs are stored in /isl/log,
          or /mnt/isl/log in the chroot environment, during packaging
          installation.

       The hard disk is mounted at the point when the installation process
       displays the message Making Filesystems.  This occurs shortly after
       you have reached the final confirmation screen of the installation
       questions.

       Once you have passed the final confirmation screen, all the
       information in the logs is transferred onto the hard disk.

       To extract files from the machine, switch to the character console on
       vt0. At the prompt in the appropriate directory (/tmp, /isl or
       /mnt/isl) enter the following command:

          ls log/* | cpio -ocuvO /dev/rdsk/f03ht

       To extract the files from the floppy diskette, enter the following
       command:

          cpio -icuvI /dev/rdsk/f03ht


    +  The default size for the swap slice, as calculated during the
       installation, is based on the total amount of memory in the system.
       If you intend to allocate a sizeable amount of system memory for use
       as dedicated memory, more swap will be allocated than is necessary.
       By entering the ``Customize filesystems and slices'' screen, you can
       resize the swap to a more reasonable value and allocate the space you
       free up to other slices or filesystems.  As a rough guide, start with
       twice the amount of non-dedicated memory as swap.

    +  UnixWare cannot install on a device that is not detected. If you do
       not pay attention to the device information presented on the
       installation screens, you may wind up installing UnixWare on a
       secondary disk (if one is present) because the primary disk was not
       found. If a secondary disk is not present, an error message is given
       that indicates the installation cannot proceed.

       UnixWare is installed on the primary hard disk found for the primary
       Host Bus Adapter (HBA). Typically, rules for determining which HBA, or
       which disk, is primary are as follows:

       +  IDE HBAs always take precedence over SCSI HBAs.

       +  IDE HBAs are designated primary and secondary usually in their
          physical setup (jumpers, for example).

       +  With IDE devices, disks are designated as master and slave usually
          by jumper settings on the disk drive.

       +  When multiple SCSI HBAs are present, usually the HBA in the lowest
          numbered bus slot is primary.

       +  With SCSI disks, the lowest numbered target id on the primary HBA
          is the primary disk.

       +  The secondary SCSI disk is the next lowest assigned target id
          starting with the primary HBA, until all HBAs are scanned and no
          further disks are found.

       You must be familiar with your system's physical configuration before
       you begin the installation. When the hardware diagnostics are run as
       the system first powers up, check the console messages for recognition
       of your devices. If you do not see what you expect, check the system
       BIOS setting to make sure there are no conflicts. Check power and bus
       cables to make sure they are well attached.

       Once the UnixWare HBA autodetection is complete during the
       installation interview process, you can switch to the system console
       screen to see diagnostic messages for devices that successfully load.
       HBA and disk information may be present on the screen.

       When configuring disk setup, verify the disk sizes being reported on
       the screen as well as the device names being presented. Device names
       contain the information about the controller and target id for the
       disk it refers to. See disk(7) for details.

       In Compaq servers, the system BIOS will boot from the HBA assigned the
       ``Controller order'' of ``first'', using the System Configuration
       Utility. Any controller may be selected as the first controller
       regardless of slot. The UnixWare HBA drivers for Compaq controllers
       will request HBA number 0 for this first controller.  It is important
       that HBA 0 be assigned to the ``primary'' or ``boot'' controller.
       Problems with /stand can result when the boot controller is not HBA 0.

    +  If you need to install an HBA, you should install it when the ISL
       procedure first asks you to. If you forget to install it at this time,
       and then try to retrieve the situation by going back to the screen,
       using <F9>, the ISL will appear to accept the HBA, but will actually
       fail to copy the HBA to the link kit.

       If the HBA is then used for the boot device, the system will panic on
       the first post install boot of the OS with a message indicating that
       the root file system cannot be mounted. At that point the only option
       is to restart the installation.

    +  If you choose to install the NetWare Services package during
       installation, you are asked for an IPX network number and frame type.
       If this is the first IPX/SPX installation on your subnet, it is
       recommended that you specify the network number and IEEE 802.2
       framing. If another system is already configured to use IPX/SPX on
       your subnet, you can make your system use autodiscovery to configure
       its IPX parameters by setting the network number to 0 and the frame
       type to AUTO_DISCOVER.

       _________________________________________________________________________
          NOTE  Do not use autodiscovery if the same cable segment is
          hosting more than one IPX subnet number or frame type.
          Autodiscovery is also not recommended if it is possible that
          there may be misconfigured systems on the same cable segment as
          the system that you are configuring.
       _________________________________________________________________________


    +  Installation fails on a system that has multiple paths to a CLARiiON
       system when some of the paths are inactive.

       To resolve this, turn the CLARiiON system off and proceed with
       installation.  When the system is up turn the  CLARiiON system back
       on, then hot add it or reboot.

    +  It is not possible to do network installations over non-Ethernet
       media, for example, Token-Ring or FDDI networks.

    +  The maximum functional year for installation is Year 2037 (2^31-1) .
       It is not Year 2070, as stated in the help for the Installation Year
       screen.

    +  During installation, the initial system load fails to configure token
       ring.  After the first reboot, you will first need to use the Network
       Configuration Manager to remove token ring; then you must use the
       Network Configuration Manager to add token ring.

    +  On a DECpc XL566 Pentium with the Symbios Logic NCR53c810, while the
       system is rebooting, after the message

          The system is coming is coming up. Please wait.

       the following message is displayed:

          WARNING: C8XX: Attempting to Send_ABORT to ha=0 id=0 lun=0 tag=FC

       This message can be ignored.

    +  ISL remains limited to 2 disks and 1 swap slice, sized to the entire
       main memory size present below 4GB. If you want to dedicate memory
       (that is, tune up DEDICATED_MEMORY), stripe your swap space across
       multiple slices, or both, then you must create a swap slice of the
       appropriate size at installation time. An appropriate way of
       calculating this is:

          swap_slice_size = (general_memory * 2) / stripe_width.

       where swap_slice_size gives the size of the swap slice to be reserved
       on the root disk. It is assumed here that the administrator will
       configure in the additional disks, and their associated swap slices,
       following the first reboot.
    +  Although the ISL seems to allow you to create a /stand that is greater
       than 128MB, it will not actually do it. If you do set the size of
       /stand to be greater than 128MB, the installation will fail when it
       tries to create /stand.  The error message does not give any
       indication why it failed.

    +  The ISL will only allow dump slices that are less than 2GB.

    +  The largest file system supported by UnixWare is 131104MB (128GB+).

    +  If you want to create a set of emergency floppies and you have not
       mounted /var, you will be unable to create the floppies. To
       successfully create the emergency floppies, you must first mount /var.

    +  When you try to create a set of emergency floppies, you may fail and
       encounter messages stating that modules such as /dev/dsk/c0b0t0d0s?
       and /home2 could not be found. If this occurs, you should comment out
       the /home2 line in /etc/vfstab.

    The following may occur during reboot:

    +  The system may appear to hang during reboot because of the time that
       the documentation indexing process takes. If this occurs, switch the
       power off on your system, then switch it on again and let it reboot.

    +  The system may panic or reboot in some circumstances while the boot
       process is running from the first diskette. This may be due to an
       incorrect detection of memory.  If this occurs, you should use the
       MEMADJUST command via the boot menu to specify the memory
       configuration manually. See ``Boot problems, hangs, and panics'' for
       details.

    +  Your Intel Extended Express system may panic during reboot.

       To prevent this, after you install the osmp package, ensure that the
       Advanced Programmable Interrupt Controllers (APICs) in the machine are
       enabled from the BIOS.


 Installation troubleshooting

    This section describes some problems that you may encounter during
    installation, and their solutions, under the following headings:

    +  ``Boot problems, hangs, and panics''

    +  ``Internal errors''

    +  ``Driver problems''

    +  ``Kernel build''

    +  ``Media errors''

    +  ``Memory problems''

    +  ``Network installation problems''

 Boot problems, hangs, and panics

    The following items explain how to solve some of the problems you may
    encounter during system boot or reboot. These are:

    +  ``Starting UnixWare message is not displayed''

    +  ``Panics or resets while booting from install diskette''

    +  ``System hangs during installation''

    +  ``System hangs during reboot''

    +  ``System has incompatible boot code''

    +  ``System hangs or panics during reboots''

    +  ``Problems with DPT controller with old firmware''

    +  ``Power saver option enabled''

    Starting UnixWare message is not displayed


    Problem
       When booting your system the Starting UnixWare... message is not
       displayed.

    Solution
       Check whether the boot disk drive contains a diskette. If so, remove
       the diskette and reboot your system. Otherwise, you may have a system
       hardware problem. See the documentation provided with your hardware.

       Many add-on devices and cards come with configuration utilities. Check
       all the connections and run the configuration utilities.

    Panics or resets while booting from install diskette


    Problem
       After booting your system with the Install Diskette, the UnixWare logo
       screen is displayed and then the system either displays a panic
       message or resets (system firmware messages are displayed again).

    Solution
       This problem is typically the result of not running a hardware
       configuration program, such as the ECU or the CMOS setup program,
       before installing UnixWare. To fix the problem, run all machine and
       peripheral hardware setup programs provided by your hardware vendor
       and verify that your hardware is correctly configured. In particular,
       check your memory size/control, cache control, bus speed, and video
       specifications. See your hardware documentation for details.

       For example, this problem may occur if the correct amount of memory is
       not configured.

       If running hardware setup programs does not solve the problem, then
       there may be a memory problem. You can try to set the amount of memory
       on your system manually as follows:

       1.  Press the reset button (or power the computer off, then on again
           if you do not have a reset button).

       2.  When the Starting UnixWare... prompt or the SCO logo is displayed,
           press <Space>.

           The interactive boot session prompt, [boot]#, is displayed.

       3.  Use the command show memory to display the memory ranges found by
           the boot loader, and identify the range of memory that is causing
           the problem.

       4.  Remove incorrect ranges of memory from use. Use MEMADJUST as
           follows:

              MEMADJUST=-range

           where range is:

              low_address-high_address

           Addresses are in decimal, and may be specified in bytes, or
           suffixed with ``K'' to indicate kilobytes (1024 bytes), ``M'' for
           megabytes, or ``G'' for gigabytes.  Addresses may not exceed 4G.

           For example, use this command to remove memory between 15MB and
           16MB:

              MEMADJUST=-15M-16M
              boot

           Alternatively, you can use MEMADJUST to add more memory.  For
           example, if the boot does not detect memory between 16MB and 64MB,
           set MEMADJUST as follows:

              MEMADJUST=+16M-64M
              boot

           _____________________________________________________________________
              NOTE  Only the last setting of MEMADJUST takes effect.

              You cannot use MEMADJUST to configure memory above 4GB.
           _____________________________________________________________________

           _____________________________________________________________________
              NOTE  Using MEMADJUST during the installation process will
              cause the MEMADJUST setting to be added to /stand/boot.  If
              it remains there, the memory will be configured every time
              the system is booted.  Delete the line that contains
              MEMADJUST line from /stand/boot after installation if it is
              no longer needed.
           ____________________________________________________________________


       5.  Continue the installation.

       In other reset conditions, you may need to set DISABLE_CACHE=yes to
       fix the problem.


    Problem
       After booting your system with the Install Diskette, the UnixWare logo
       screen is displayed, followed by a machine exception error.

    Solution
       You may need to perform the interactive boot process as in the
       previous problem, but instead of using MEMADJUST to adjust memory, set
       IGNORE_MACHINE_CHECK=yes.


    Problem
       When installing UnixWare, and using a HBA diskette that is not
       actually needed by the installation, the following message is
       repeatedly displayed after the software loads:

          Drivers on HBA diskette are not needed


    Solution
       You must reboot the system to clear this error. Do not insert the HBA
       diskette when you re-install the system.


    System hangs during installation


    Problem
       Your system hangs during installation. The gauge showing the
       percentage of files installed does not appear.

    Solution
       This occurs under the following circumstances:

       +  If your computer is not accessing your diskette drive, check in
          CMOS that your diskette drive type is properly configured. For
          example, if a 1.44MB diskette drive is configured as a 1.2MB drive,
          the diskette drive will not be accessed. Also check that your
          system memory is installed properly.

       +  If you suspect a hardware problem (SCSI or non-SCSI CD-ROM) or
          loose cable, check your system hardware.

       If you are sure that your system has none of these problems, contact
       your SCO software reseller and exchange your installation media for
       new media.

    System hangs during reboot


    Problem
       After the system self-test completes, the Starting UnixWare... message
       does not appear. The system may be hung.

    Solution
       To correct this, try one of the following solutions:

       +  If there is a diskette in diskette drive 1, remove it. Press any
          key on the keyboard and the system should come up properly. If it
          does not, use <Ctrl><Alt><Del> or press reset to reboot the system.

       +  If you recently installed an add-on card, and if your computer
          worked properly before installing the card, remove the new card and
          see if you can reboot the system. If this solves the problem, there
          is probably an IRQ or address conflict. Reconfigure the card with a
          non-conflicting IRQ or address and then reinstall the card.

       +  If your computer uses system shadow RAM or video shadow RAM, access
          your CMOS configuration and turn off the shadow function(s). While
          use of shadow memory improves performance for DOS systems, it has
          no useful effect on the performance of UnixWare.

       +  If your computer is not accessing your diskette drive, check in
          CMOS that your diskette drive type is properly configured. For
          example, if a 1.44MB diskette drive is configured as a 1.2MB drive,
          the diskette drive will not be accessed. Also check that your
          system memory is installed properly.

       +  If your computer has BIOS caching enabled, disable BIOS caching.

       +  If your system has an IDE disk drive that is larger than 512MB, and
          your disk head parameters are defined as greater than 16, verify
          that your system BIOS supports disk drive parameters with more than
          16 heads. If your system BIOS does not support large disk drives,
          redefine your disk drive parameters using 16 or fewer heads. See
          your hardware documentation for details.

       +  If your computer has a hard disk drive greater than one gigabyte
          and you have an Adaptec 1542 SCSI controller with extended
          translation enabled, disable the extended translation.

       +  If your computer had another operating system installed before
          installing UnixWare, especially an earlier version of SCO UnixWare,
          it may have placed master boot code on the hard disk that is
          incompatible with UnixWare. If this is the case, UnixWare will not
          boot. In most cases, there will be no error message; the system
          will just hang. To resolve this problem, see the following section.

    System has incompatible boot code


    Problem
       You did not choose to overwrite the boot code in response to the
       ``Configure special disk operations?'' when installing UnixWare and
       the boot code from your previous system will not boot UnixWare.

    Solution
       Install UnixWare again. This time, do not change the default setting
       for the ``Overwrite system master boot code:'' choice on the ``Disk
       Operations'' screen; it should be set to ``Yes''.

    System hangs or panics during reboots


    Problem
       The kernel builds successfully but the system does not boot or the
       system panics.

       A system panic may occur when there is a fatal error that the system
       cannot correct. This is most often caused by an improperly configured
       device or device driver. In a panic situation, the system prints a
       panic message. If the Kernel Debugger (kdb) package is installed,
       control transfers to the kernel debugger program.

    Solution
       If you have just installed new hardware, there may be an address or
       interrupt conflict with other hardware on the system. Power down the
       computer and verify that all controllers are properly seated and
       jumpered. Use vendor-supplied software to diagnose hardware conflicts
       and change address or interrupt values as needed.

    Problems with DPT controller with old firmware


    Problem
       On UnixWare systems with old DPT controllers, the installation ends
       just after the HBA drivers are loaded (when it says Checking Hardware
       Configuration...), with the message:

          Error: could not determine the size of the main disk
          press any key

       Then pressing any key displays the screen:

          Internal sequencer error: sequencer failed (first call, UI mapfile)


    Solution
       If you have one of the old DPT controllers, you can not use it with
       the IDE. If you want to use IDE, take this DPT controller out of the
       machine (otherwise this DPT controller will respond to the IDE driver
       as it tries to emulate IDE).

       If you want to use one of these old DPT controllers with UnixWare 7,
       you must disable the IDE driver even if you do not have an IDE
       controller in the system (otherwise this DPT controller will respond
       to the IDE driver as it tries to emulate IDE).

       The IDE emulation mode of DPT does not work under UNIX (it is supposed
       to work under DOS).

    Problem
       Some old DPT controllers support only LUN 0-5. However, when the SDI
       subsystem probes the controller at LUN 6 and beyond, the controller
       responds as if there is a unit attached at LUN 6. Later when SDI reads
       the capacity of the UNIT at LUN 6, the controller returns 0. This
       value gets used in a computation somewhere in UnixWare 7 and causes a
       ``Divide by Zero'' panic.

    Solution
       If IDE devices are present, edit the LUNSEARCH boot parameter to
       prevent the controller from returning 0.

    Problem
       The system panics at boot up after install on systems with a DPT
       controller. It gives the VT0> prompt and the ``divide by zero trap''
       message.

    Solution

       The LUNSEARCH boot parameter limits device searching beyond a
       specified logical unit number.  Most devices do not have logical unit
       numbers greater than 0. If you have any device which has logical unit
       numbers whose values are greater than 0, the LUNSEARCH parameter can
       be modified to specify that.

       The format for the LUNSEARCH parameter is:

          LUNSEARCH=(c:b,t,l)[,...]

       For example,

          LUNSEARCH=(0:1,3,5),(1)

       means that on controller 0 bus 1 device 3 (SCSI ID 3), logical units
       should not be searched beyond LUN 5 and no devices on controller 1
       should be searched beyond logical unit 0.

       For more information on the use of LUNSEARCH and other boot
       parameters, refer to boot(4).

    Power saver option enabled


    Problem
       Installation fails at random points after the hard disk is set up (or
       the message

          WARNING: Disk Driver Request Timed Out,
          Resetting Controller

       is displayed after a successful installation) on systems with the
       ``Power Saver'' option (also referred to as ``Power Management'' or
       ``Green PC'') enabled.

    Solution
       Turn off the ``green/energy star'' power-saving time outs in the
       system BIOS. (Refer to your hardware manual for details.)

 Internal errors

    The following item explains what to do if you encounter a system error.

    Internal error in system installation. Cannot continue.


    Problem
       This message indicates a fatal and probably unrecoverable error.

    Solution
       Perform an installation from the beginning to clear the problem.

 Driver problems

    The following item explains what to do if you encounter a driver problem.

    HBA driver problems

    On some platforms, attempting to load a driver for a board that is not
    installed on your system can cause installation failure. If this happens,
    disable loading of the offending driver during installation by entering
    the Device Configuration Utility (DCU) during the installation process.
    From within the DCU:

    1.  Select Software Device Drivers.

    2.  Select Host Bus Adapters.

    3.  Highlight the driver that is causing the problem.

        If you are not sure which driver is causing the problem, try
        switching virtual terminals using <Alt><SysReq>H and look for the
        driver name in the error message. Use <Alt><SysReq>F1 to return to
        the virtual terminal you were in.

    4.  Deselect the driver by pressing <Space>.

    5.  Press <Enter> to exit the menu.

    6.  Select Return to DCU Main Menu.

    7.  Select Apply Changes & Exit DCU.

    8.  Proceed with the installation.

 Kernel build

    The following item explains how to solve a problem you may encounter when
    the UnixWare kernel is built.

    Kernel build fails


    Problem
       Kernel build fails during installation.

    Solution
       If a kernel build fails during installation, review the error messages
       in the /tmp/kernel.build error file for details.

       If a failure occurs while rebuilding the UnixWare kernel, this may be
       the result of a corrupted kernel file or idbuild tool caused by bad
       media or a malfunctioning device. The installation halts at this
       point.

       Determine if your hardware (CD-ROM, diskette, or network) is working
       properly. To do so, run any hardware and vendor diagnostic utilities
       or contact your network administrator. If necessary, replace the
       installation media and restart the installation.

    Problem
       The kernel build gives a warning message about a circular dependency
       in module ``event''.

    Solution
       This is a harmless message and can be safely ignored.

 Media errors

    The following items explain what to do if a media error is displayed or
    if the media you want to install UnixWare from is not listed.

    Error reading media


    Problem
       A fatal error message indicates that there was a problem reading your
       installation or HBA diskette media.

    Solution
       Such error messages can be a hardware problem, or a problem with your
       network (if you are performing a network installation), or a problem
       with your media. Do the following:

       1.  If you are performing a network installation, contact your network
           administrator to verify that there is not a problem with the
           Install Server or network. If there is a problem with either the
           Install Server or your network, you may have to perform the
           installation again.

       2.  If the problem was not resolved in Step 1, shut down your system
           and check for hardware problems. Check all connections and run the
           diagnostic utilities provided with your system hardware.

       3.  If the problem is still not resolved, contact your SCO reseller to
           obtain replacement media. (If you used an HBA diskette from a
           third-party vendor, contact that vendor for a replacement
           diskette.)

    Installation devices not listed


    Problem
       You are installing from CD-ROM and CD-ROM is not listed as an
       installation device.

    Solution
       If UnixWare does not list your install device, check the following:

       +  Make sure the hardware in your system is supported. See ``Supported
          hardware'' and the SCO Compatible Hardware Web Pages
          (http://www.sco.com/chwp) for information.

       +  Make sure the device is powered on at boot time.

       +  Check the cabling to the device.

       +  Make sure your controller and devices are set up properly.

       +  If you are using a SCSI device, ensure that SCSI termination rules
          are followed.

       +  Restart the installation and enter the DCU. Check whether the
          device driver for this device has been configured.

       +  Run diagnostic software on that device to make sure it is not
          faulty.

       +  If necessary, swap that install device with another make or model.

 Memory problems

    The following items explain how to solve some of the system memory
    problems you may encounter.

    Insufficient memory during installation


    Problem
       During installation on EISA systems, an error message indicates that
       there is insufficient memory to load UnixWare.

    Solution
       Run the ECU provided by your hardware vendor and set the correct
       amount of memory.

    Incorrect amount of RAM memory detected


    Problem
       On EISA systems with exactly 16MB or less of RAM, the incorrect amount
       of RAM may be detected if ECU is incorrectly configured. This can lead
       to panics when non-existent memory is used.

    Solution
       You can determine the amount of memory detected by pressing any key
       while UnixWare is booting and the logo screen is showing, then typing
       ``show memory'' at the [boot] prompt; the last value shown will be the
       highest detected memory address.  If this value is greater than 16MB
       on a system with only 16MB of RAM, run the ECU provided by your
       hardware vendor and make sure the memory size is correctly set to
       16MB, then reboot. If this does not fix your problem, see ``Boot
       problems, hangs, and panics'' for details of how to use MEMADJUST to
       change the amount of memory used by UnixWare.

    Memory above 4GB not recognized


    Problem
       Memory above 4GB is not recognized.

    Solution
       Add ENABLE_4GB_MEM=Y to /stand/boot and reboot the system. See ``Large
       physical memory'' in Understanding system administration for
       information.

 Network installation problems

    The following items explain how to solve some problems you may encounter
    while performing a network installation.

    Network Utility Diskette not recognized


    Problem
       The Network Utility Diskette is not recognized. The installation
       process asks you to insert the first Network Utility Diskette even
       when it is already in the drive.

    Solution
       This problem occurs when your computer has a GSI model 21 Enhanced
       IDE/floppy diskette/tape controller. When this is installed according
       to the instructions, the diskette devices in the CMOS are set to ``Not
       installed''.

       To install UnixWare, define the floppy diskette drive in the system
       CMOS as well as with the controller's BIOS. Some machines may report
       floppy-diskette drive errors on boot as a result, but the boot should
       continue successfully.

    Cannot configure network interface card


    Problem
       When prompted to provide your network interface adapter configuration
       data, the value for one or more of your adapter's hardware parameter
       settings is not listed (for example, the IRQ, I/O address range,
       memory address range, and/or DMA channel).

    Solution
       Only hardware parameter values not already in use are listed. If the
       value for a hardware parameter is not listed, then another hardware
       controller is configured to use the same hardware setting. There are
       several ways to fix this problem:

       +  Repeat the installation from CD-ROM or diskette.

       +  Repeat the installation and use the DCU to disable hardware
          controllers that are not needed during installation (for example, a
          cartridge tape drive).

       +  Record the choices that are listed and then shut down your system.
          Reconfigure your networking card to use one of the values you
          recorded and then repeat the installation.


    Problem
       When running the networking configuration manager a smart-bus board
       (PCI, EISA, MCA) is not autodetected.

    Solution
       Run dcu(1M) and ensure that an ISA device is not using the same IRQ.
       If it is, you must disable the ISA device using dcu and also in BIOS
       if necessary. After doing this the card will appear as a selectable
       option.

    Error when configuring network


    Problem
       When performing a network installation, an error message is displayed
       following the Configuring Network message.

    Solution
       The last line of the error message explains the cause of the problem:

       +  If the message indicates a problem with your networking card
          selection, then either the wrong networking card or the wrong
          networking parameters were selected. Press <Enter> to restart
          installation from the beginning.

       +  If the message indicates a problem contacting an Install Server,
          first check that your networking cable is securely attached to your
          system.

          If the cable is securely attached to your system, ask your network
          administrator to check whether your network is up and whether an
          Install Server is enabled for network installation. Then select
          whether to return to the previous menu or to cancel the
          installation.

       +  If the cable is not securely attached to your system, attach the
          cable. Then select whether to return to the previous menu or to
          cancel the installation.

    Installing osmp from NFS filesystems


    Problem
       Network installation of the osmp package from an NFS filesystem fails
       because some files are accessible only with root privileges, which are
       not available via NFS.

    Solution
       Copy the osmp package to the local machine and install it from there.






 Chapter 2
 Read this after installation

    After you have installed UnixWare, you should follow the instructions for
    configuring your system in the Installation Guide in conjunction with the
    special information contained in this chapter.

    This chapter covers the following:

    +  Large physical memory support

    +  Reconfiguring IPX/SPX after installation

    +  Setting up SPX or TCP installation servers

    +  Switching auditing on

    +  Enabling SCOhelp searching


 Large physical memory support

    Any machine which contains memory at or above address 4G (2^32) requires
    large physical memory (LPM) support. Examples of machines that required
    LPM are a Corollary architecture system with more than 4GB of memory, or
    a Unisys Aquanta system with more than 3GB.

    See ``Large physical memory'' in the online documentation under System
    management -> Understanding system administration -> Performing basic
    system tuning and monitoring for details of how to configure LPM support.

    Note that the following corrections and clarifications apply to the
    information in ``Large physical memory'' in the online documentation:

    +  The references to tuning the PAGEOUTRATE parameter no longer apply.
       This parameter is autotuned.

    +  The DEDICATED_MEMORY parameter needs to be set only if you wish to
       dedicate memory below 4GB. If ENABLE_4GB_MEM is set, memory above 4GB
       is dedicated automatically. If you set DEDICATED_MEMORY in this case,
       you must set it to the amount of dedicated memory that you require,
       plus the total amount of memory over 4GB.

       Alternatively, set DEDICATED_MEMORY to ``unlimited'', then set
       GENERAL_MEMORY to the amount of general purpose memory that you
       require.  For example, to use 128MB as general purpose memory, and the
       remainder for dedicated memory, set the following tunables.

          DEDICATED_MEMORY        16777216
          GENERAL_MEMORY  32768


    +  In addition to setting ARG_MAX as suggested, you may also need to set
       the MAXRSS parameter as follows:

       ___________________________________________________________________
       Suggested value            For...
       ___________________________________________________________________
       0x2000                     typical systems
       0x20000                    netscape server or departmental server
       0x40000000                 data base server


    +  The commands required to set tunables for a Netscape server are
       similar to the following:

          /etc/conf/bin/idtune SDATLIM 0x7fffffff
          /etc/conf/bin/idtune HDATLIM 0x7fffffff
          /etc/conf/bin/idtune SVMMLIM 0x7fffffff
          /etc/conf/bin/idtune HVMMLIM 0x7fffffff



 Reconfiguring IPX/SPX after installation

    It is strongly recommended that you use the Network Configuration Manager
    (netcfg) rather than nwcm(1Mipx) if you need to modify your system's
    IPX/SPX configuration. Similarly, you should not modify IPX/SPX
    configuration files using a text editor.


 Setting up SPX or TCP installation servers

    Note that setting up TCP or SPX servers can be problematic if the server
    is also an NIS client as it will pick up the services map rather than the
    local /etc/services file. This can cause TCP/IP and IPX/SPX both to be
    misconfigured.  You need to ensure that the services map contains
    inetinst 6969/tcp and 1006/spx entries for network installs to work.

    Setting up an SPX server requires that a sapd is running. This means that
    the system must be configured with an internal network number via IPX/SPX
    configuration in netcfg. The router type must also be set to FULL so that
    the service will be advertised using RIP.


 Switching auditing on

    Even if you select the auditing package and therefore install it during
    the installation procedure, auditing is not turned on by default when the
    system boots.

    To turn auditing on manually, run auditon(1M) as root. You should run
    auditoff(1M), also as root, to turn auditing off before you shut down the
    system. Rebooting the system with auditing switched on is very slow and
    should be avoided.

    You should preferably switch auditing on automatically after the system
    boots and switch it off again before shutdown. To do this, edit
    /etc/rc2.d/S02audit to remove the comments from the lines that execute
    the commands auditon and auditoff.


 Enabling SCOhelp searching

    The SCOhelp search capability may not be enabled on your server. To
    enable it, you must run the Verity indexing command:

       /usr/man/bin/config_search -f

    _________________________________________________________________________
       NOTE  The configuration requires at last 32KB of RAM to be
       available on the system. Attempting it with less may result in a
       core dump.
    _________________________________________________________________________






 Chapter 3
 Updating your system

    You can install UnixWare 7.0.1 in one of two ways: as a full
    (destructive) installation, or as updates to your previously installed
    UnixWare 7 system.

    _________________________________________________________________________
       NOTE  For information on performing a full installation, see the
       Chapter 1 of these Release Notes and the Installation Guide.
    _________________________________________________________________________

    All UnixWare 7.0.1 update packages are located on the UnixWare 7.0.1
    Operating System Updates CD-ROM (Disk 2 of 3).

    To update your previously installed UnixWare system with UnixWare 7.0.1
    update packages:

    1.  Verify that your system's hardware and software is suitable for the
        update.

    2.  Install the update701 package if it has not already been installed,
        then reboot the system.

    3.  Install other desired update packages in this order:

        +  One or more host bus adapter drivers.

        +  Audio drivers.

        +  Graphics drivers.

        +  Network drivers.

        +  English-language SCOhelp documentation and manual pages.

        +  Localized SCOhelp documentation.

    4.  Install any desired software from the UnixWare 7.0.1 Optional
        Services CD-ROM (Disk 3 of 3).


 Update 7.0.1 installation requirements

    To install the update packages from the UnixWare 7.0.1 Operating System
    Updates CD-ROM, your system must have one of the following operating
    systems installed:

    +  UnixWare 7.0.0s

    +  UnixWare 7.0.0t

    +  UnixWare 7.0.0u

    These updates do not change the base hardware requirements described in
    the Installation Guide, but each update package does have a disk space
    requirement that must be satisfied for its installation to succeed:

    ___________________________________________
    Package                Space required (MB)
    ___________________________________________
    BASEdoc                27
    BASEman                17
    audio                  1
    basex                  2.5
    cpqhpcd                .05
    deBASEdoc              4
    esBASEdoc              4
    frBASEdoc              4
    hba drivers            0.1
    nics                   5
    update701              45
    xclients               1.5
    xdrivers               5
    xserver                7

    _________________________________________________________________________
       NOTE  The space required by the installation is usually larger than
       the space needed by the software after installation.

       If space is at a premium, install your packages one at a time
       rather than simultaneously.
    _________________________________________________________________________



 Installing the update701 package

    The update701 package contains many enhancements to the base operating
    system as detailed in Appendix B, ``New features and enhancements''.

    _________________________________________________________________________
       NOTE  When you install update701, only those components already
       installed on your system are updated. If you later install
       additional components from the UnixWare 7.0.1 Installation CD-ROM,
       you should re-install the update701 package to ensure that all
       fixes and enhancements are correctly applied.
    _________________________________________________________________________

    To install the update701 package:

    1.  Log in to the system as root.

    2.  Bring the system down to single user mode by entering:

           shutdown -y -g300 -i1

        This gives your users 5 minutes to log off the system.

    3.  After the system comes down, log in to the system as root at the
        console login prompt.

    4.  Insert the UnixWare 7.0.1 Operating System Updates CD-ROM into the
        CD-ROM drive.

    5.  Enter:

           pkgadd -d cdrom1 update701


        Messages appear as the software loads.

    6.  After the software loads, reboot the system to reflect changes to the
        kernel. Enter:

           init 6


    After you install the update701 package, you should install any other
    desired updates from this CD-ROM before installing any products from the
    Optional Services or other CD-ROMs.  For more details, see the following
    section.

    _________________________________________________________________________
       NOTE  Installing the update701 package temporarily disables
       domestic encryption capabilities. For more information and a
       workaround to this problem, see ``Domestic encryption''.
    _________________________________________________________________________



 Installing other updates

    Installation of other updates on the Operating System Updates CD-ROM
    requires that you first install update701.

    To install other updates:

    1.  Log in to the system as root.

    2.  Insert the UnixWare 7.0.1 Operating System Updates CD-ROM into the
        CD-ROM drive.

    3.  From either the CDE console or a graphical xterm window, enter:

           scoadmin application installer


        The Application Installer main window appears.

    4.  Select CD-ROM_1 from the Install From menu.

        The list of sets and packages found on this CD-ROM appear.

    5.  Click on the icon of the package or set you want to install, then
        press Install.

        Messages appear as the software loads.

        Repeat this step for each package or set you want to install.

    6.  When finished installing software, select Actions -> Exit to exit the
        Application Installer.

    7.  If you installed one or more drivers from the HBA set, reboot the
        system to reflect changes to the kernel. Enter:

           shutdown -y -g300 -i6

        This gives your users 5 minutes to log off of the system before it
        reboots.

    The following update packages are available:

    BASEdoc and BASEman
            The BASEdoc and BASEman packages update the SCOhelp topics and
            manual pages, respectively, to reflect UnixWare 7.0.1 software.
            These packages also contain enhanced documentation in many areas
            of the product, specifically in the areas of network and system
            administration.

    audio   The audio package contains drivers for all supported audio
            adapters, including new support for the following:

               Creative Labs SB AWE64 PnP (Type 2-CTL00C1)
               Creative Labs SB AWE64 Pnp (Type 3-CTL00C3)
               Creative Labs SB AWE64 PnP (Type 5-CTL00E4)
               Creative Labs SB 32/AWE Pnp (Type 3-CTL0048)
               Creative Labs SB 32/AWE Pnp (Type 4-CTL0042)
               Creative Labs SB 32/AWE Pnp (Type 5-CTL0043)
               Creative Labs SB 32/AWE PnP (Type 6-CTL0047)
               Creative Labs SB ViBRA16CL PnP (CTL0080)
               ESS ES1868 Plug and Play AudioDriver(ESS1868)
               ESS ES1869 Plug and Play AudioDrive (Type 1-ESS1869)
               ESS ES1869 Plug and Play AudioDrive (Type 2-ESS0003)
               ESS ES1878 Plug and Play AudioDrive (ESS1878)
               Maxi sound 64 / Home Studio 64 (audio only) (MAXI64)


    basex, xclients, xdrivers, xserver
            The basex, xclients, and xserver packages contain optimizations
            and enhancements to the X server, graphical libraries (libX11.so
            and libICE.so), Video Configuration Manager, xdm, and other
            aspects of the Graphical Environment.

            The xdrivers package contains drivers for all supported graphics
            adapters, including new or updated support for the following:

               r3p driver

               ATI RAGE PRO PCI and AGP chipset based adapters
               ATI Xpert@Play (RAGE PRO)
               ATI Xpert@Work (RAGE PRO)
               ATI All-In-Wonder PRO (RAGE PRO)

               m64 driver

               ATI Mach64 PCI (VT/GT) RAGE/II/II+/IIC chipset based adapters
               ATI 3D Charger

               mil driver

               Matrox Millennium I PCI and II PCI and AGP


    cpqhpcd The cpqhpcd package contains the hpcd driver, which supports PCI
            Hot Plug slots on Compaq Proliant 6500, Proliant 7000, & Proliant
            7000 Xeon series machines. Once installed, you can use the
            SCOadmin Hot Plug Manager, installed as part of the update701
            package, to manage PCI devices whose drivers support PCI Hot Plug
            capabilities (for example, DDI8 based drivers).

    deBASEdoc, esBASEdoc, frBASEdoc
            The updated localized documentation packages include updated
            SCOhelp topics in French (frBASEdoc), German (deBASEdoc), and
            Spanish (esBASEdoc).

    hba (set)
            A complete set of supported Host Bus Adapter drivers is found in
            the hba set. This set includes all previously-supported HBA
            drivers and the following new or updated drivers:

               adsb -- Adaptec PCI Ultra2 SCSI
               adsl -- Adaptec PCI SCSI
               c8xx -- Symbios PCI to SCSI
               dak -- Mylex DAC960 Array
               dpt -- DPT SCSI
               i2oOSM -- SCO I2O Mass Storage OSM
               qlc1020 -- QLogic PCI IQ
               qlc2100 -- QLogic PCI FC


    nics    The nics package contains drivers for all supported network
            adapters, including new support for the following:

               e3H driver

               3Com Fast EtherLink XL PCI (3C905B)

               dcfx driver

               DEC Fast EtherWORKS PCI 10/100 DE500-BA

               d21x driver

               Digital Semiconductor 21040 10 Ethernet
               Digital Semiconductor 21041 10 Ethernet
               Digital Semiconductor 21140 10/100 Ethernet
               Digital Semiconductor 21143/2 10/100 Ethernet

               skfp driver

               SysKonnect FDDI PCI adapter SK-5521 (SK-NET FDDI-UP)
               SysKonnect FDDI PCI adapter SK-5522 (SK-NET FDDI-UP DAS)
               SysKonnect FDDI PCI adapter SK-5541 (SK-NET FDDI-FP)
               SysKonnect FDDI PCI adapter SK-5543 (SK-NET FDDI-LP)
               SysKonnect FDDI PCI adapter SK-5544 (SK-NET FDDI-LP DAS)
               SysKonnect FDDI PCI adapter SK-5821 (SK-NET FDDI-UP64)
               SysKonnect FDDI PCI adapter SK-5822 (SK-NET FDDI-UP64 DAS)
               SysKonnect FDDI PCI adapter SK-5841 (SK-NET FDDI-FP64)
               SysKonnect FDDI PCI adapter SK-5843 (SK-NET FDDI-LP64)
               SysKonnect FDDI PCI adapter SK-5844 (SK-NET FDDI-LP64 DAS)

            This package also contains a variety of enhancements to
            previously-supported drivers.

    _________________________________________________________________________
       NOTE  Additional information about many of these packages appears
       in the online /info hierarchy on the UnixWare 7 Operating System
       Updates CD-ROM:

       audio     /info/audio/readme.txt

       basex     /info/basex/readme.txt

       cpqhpcd   /info/cpqhpcd/readme.txt

       hba       /info/hba/readme.txt

       nics      /info/nics/readme.txt

       xclients  /info/xclients/readme.txt

       xdrivers  /info/xdrivers/readme.txt

       xserver   /info/xserver/readme.txt

    _________________________________________________________________________






 Chapter 4
 Hardware notes

    This chapter supplements the information in the UnixWare 7 System
    Handbook and on the SCO web site, to which you should also refer for
    information about hardware supported for UnixWare.

    This chapter covers the following areas:

    +  Supported hardware

    +  Hardware compatibility issues

    +  Upgrading video adapters

    +  Hardware configuration notes

    +  Hardware limitations and workarounds


 Supported hardware

    To determine if your hardware is supported, please see the following
    README files on the UnixWare 7.0.1 Operating System Supplements CD-ROM:

    /info/hardware/audio.txt
                            sound cards and other audio devices

    /info/hardware/hba.txt  host bus adapters (HBAs)

    /info/hardware/isdn.txt ISDN adapters

    /info/hardware/mp.txt   multiprocessor support modules

    /info/hardware/nics.txt network adapters

    /info/hardware/xdrivers.txt
                            graphics adapters

    For information on hardware that is newly supported in UnixWare 7.0.1,
    see the lists in Chapter  3, ``Updating your system''.

    SCO is constantly adding support for additional hardware devices.  Check
    the SCO Compatible Hardware Web Pages (http://www.sco.com/chwp) regularly
    to see if hardware not listed in these Release Notes or in the online
    READMEs is now supported.


 Hardware compatibility issues

    Except where noted, the hardware described in SCO documentation has been
    tested with UnixWare 7 systems. However, because the manufacturers of
    compatible machines or add-on peripherals may change configuration,
    functionality, or firmware at any time, no guarantee is implied.

    To determine whether hardware components are compatible with your
    machine, you must know the processor (for example, 486 or Pentium) and
    the bus architecture (ISA, EISA, MCA and PCI) that it uses.  You should
    also be aware of the type of disk controller in your system.

    If you have added any adapters, make sure that all switches or software-
    controlled settings are set as recommended in the manufacturer's hardware
    manual for that board. Some computers require specific switches or
    software-controlled settings to run UnixWare systems. If your computer
    does not run the UnixWare system with the settings as shipped, contact
    your computer hardware representative for the proper settings.

    UnixWare supports ``versioning schemes'' to allow the operating system to
    support a range of devices of a given type without mixing older and newer
    fixtures within the driver. This makes for more robust drivers and
    simplifies driver development and support. Versions are implemented for
    various driver configuration files documented in Section 4dsp manual
    pages to specify different formats for the file.

    The principal versioning scheme is ``driver interface versioning'', which
    defines the set of interfaces used to code the driver. A driver's
    interface versions are set in the ``$interface'' field of the driver's
    Master(4dsp) file.  This file should be supplied with the driver; current
    driver versioning has been implemented for all devices listed in
    ``Supported hardware''.  If your device is not listed, consult your
    hardware vendor for the most current driver interface version.

    For example, DDI (Device Driver Interface) is the primary interface
    versioning scheme that is used for all kernel drivers. DDI8 is the newest
    interface version that is supported for UnixWare, but drivers written for
    DDI5 and later versions will run without modification on UnixWare.
    However, drivers written for DDI versions prior to version 8 do not
    support DDI8 features such as hotplug.  Other interface versions include
    SDI for mass storage devices and MDI for network adapter cards.

    _________________________________________________________________________
       NOTE  Drivers written for DDI1 through 4 that ran on SCO UnixWare
       2.0 do not run on UnixWare 7 unless they are modified to support a
       later DDI interface version. SCO UnixWare 2.0 network adapter card
       driver interfaces were not supported by a versioned interface; most
       of these drivers will run on UnixWare but they cannot be rebuilt
       and are unlikely to run on future versions of the operating system.
       SCO OpenServer drivers do not support DDI interface version and
       will not run on UnixWare.
    _________________________________________________________________________

    For more information on interface versioning, see Intro(7).


 Upgrading video adapters

    UnixWare 7 supports a large number of video adapters including those
    supported under SCO UnixWare 2.X and SCO OpenServer Release 5. In
    addition, UnixWare 7 provides the vesa X server driver. This generic
    driver can operate any new video card that honors the VESA BIOS
    interface, and is useful in supplying high resolution support to video
    cards that do not have a specific accelerated driver.  For more
    information on this feature, including performance implications, see the
    online documentation on your installed UnixWare 7 system.

    Most video adapters are automatically configured when you install your
    UnixWare 7 system. However, you should record your video configuration
    from your previous operating system in case any of the following occurs:

    +  UnixWare 7 cannot automatically configure the adapter

    +  UnixWare 7 incorrectly configures the adapter

    +  you incorrectly configure the adapter manually and need to restore the
       default configuration

    To manually configure a video adapter in UnixWare 7, use the SCOadmin
    Video Configuration Manager.

 Upgrading SCO UnixWare 2.X video adapters

    On your SCO UnixWare 2.X system, view or print the file
    /usr/X/defaults/Xwinconfig. This file contains keyboard, video adapter,
    and monitor definitions. The important lines are shown here:

         chipset = GD54xx                # video chipset
           model = "GD54xx"              # the core drawing lib for this class
      vendor_lib = gd54xx_256.so.2       # chip specific drawing lib
    virtual_size = 1024x768              # actual Frame Buffer size
          vendor = "Cirrus Logic - Generic"              # vendor name

    From this information, you can determine that the configured video
    adapter is a Cirrus Logic GD54xx series model configured for 1024x768
    mode.

    Record this information, then (if auto-detection or auto-configuration
    fails) use it to configure your adapter on UnixWare 7 using the SCOadmin
    Video Configuration Manager.

 Upgrading SCO OpenServer Release 5 video adapters

    To obtain information about the currently configured adapter, run the
    Video Configuration Manager.

    The display at the top of the screen lists the name of the adapter, any
    configured monitor, and the resolution.

    Record this information, then (if auto-detection or auto-configuration
    fails) use it to configure your adapter on UnixWare 7 using the SCOadmin
    Video Configuration Manager.

 Troubleshooting video configuration

    If you install your UnixWare 7 system and find that your video adapter is
    incorrectly configured, or you want to modify configuration, try the
    following.

    To run your system in a safe video mode

    Enter /usr/bin/X11/setvideomode -stdvga. This sets IBM VGA 640x480-16
    mode, which is almost always safe for any adapter.

    To restore the adapter's default configuration

    Enter /usr/bin/X11/setvideomode -default.

    Do this if initial auto-configuration worked well enough to get the video
    working, but you manually configured the adapter to a different setting
    and lost the use of the video adapter.

    This -default option restores the settings to initial auto-configuration
    defaults.

    To determine the video adapter in the system

    Enter /usr/bin/X11/VideoHelp.

    This command lets you know what video adapter is present on your system.

    If the video Configuration Manager is run in the graphical environment,
    the configuration could be lost after a reboot. Change video modes only
    on virtual terminals in text mode.


 Hardware configuration notes

    The UnixWare 7 System Handbook contains details of hardware
    configuration.


 Hardware limitations and workarounds

    The following limitations and workarounds apply to hardware and device
    drivers in UnixWare:

    Hot Plug PCI and replacement network adapters
         If your system supports Hot Plug PCI, then a network adapter can be
         hot replaced, but the replacement adapter must be of an identical
         make and model to the original.

    Device drivers not supported
         The following device drivers are no longer supported:

         +  c7xx for Symbios Logic 53c7xx chipsets

         +  efp2 for the Olivetti SCSI host adapter

         +  fdeb for the Future Domain HBA

         +  ida for older discontinued Compaq host adapter models IDA, IDA-E
            and IDA-2

         +  mcis for SCSI host bus adapters

         +  wd7000 for MicroChannel Integral SCSI host bus adapters

         +  zl5380 for Trantor T160 host adapter and the SCSI interface
            provided by the Media Vision Pro Audio Spectrum 16 host adapter

    DDI8 device files not deleted
         DDI8 device files in /dev are not deleted when a device is removed.

    STREAMS module and driver in same code do not load
         All drivers must have unique names, even in the case of a STREAMS
         module and a STREAMS device driver built together in one Driver.o.
         If such a combination STREAMS module/driver is also using a DDI
         version older than version 8, this failure will panic the system.

    ds_qlen not set for CLARiiON arrays
         The CLARiiON arrays on the Unisys XR6 do not report the
         instantaneous qlength (ds_qlen in met_disk_stats).

    Error from sdipath
         On a system with two qlc1020 adapters and two disks attached, when
         sdipath(1M) is used to fail or repair a path an error similar to the
         following may occur:

         UX:sdipath: ERROR: Could not find path for disk2.
         :4:Path path85 has been failed.

         The command is completed successfully.

    Hot swap on MPIO-based SCSI bus
         It is not possible to hot-swap disks on an MPIO-based SCSI bus.

    adsl driver may generate errors
         The adsl driver may generate errors similar to the following on
         systems with multiple Adaptec adapters:

         date system_name unx: WARNING: adsl: device queue full [810070311]
         (ha/targetID/ lun 0/0/ 0)
         date system_name unx: WARNING: DiskDriver: HA 0 TC 0 LU 0 -I/O Error
         0x4DD13002
         date system_name unx: WARNING: adsl: device queue full [810070311]
         (ha/targetID/ lun 0/0/ 0)
         date system_name unx: WARNING: DiskDriver: HA 0 TC 0 LU 0 -I/O Error
         0x4DD13002

         These may be ignored.

    Dependencies of DDI8 drivers
         DDI8 drivers may not have circular dependencies.  idbuild(1M) will
         report non-DDI8 drivers which have circular dependencies, but these
         are acceptable.

    System with MPIO cannot initialize multiple disks
         On a system with an MPIO driver, you cannot initialize disks using
         the Volume Manager. (See ``Initializing the Volume Manager'' in
         Online Data Manager overview and installation for full details of
         initializing disks.)

         To initialize multiple disks, turn the MPIO driver off, initialize
         the disks, then turn the MPIO driver back on.

    c8xx controllers
         adding the c8xx package to a system with no c8xx controller will
         panic the system on reboot.  This occurs because the driver attempts
         to be loaded on reboot even though a controller does not exist.  To
         prevent this occurrence, please make certain that a c8xx controller
         is present in the system when the package is installed.

    Zyxel modem definition
         When using the Zyxel modem, you should use the Hayes deinition
         rather than the autodetect mechanism.

    Tricom modem profile
         Before you use the Tricom Tempest 34 Modem, edit the file
         /etc/uucp/default/Tricom_Tempest_34 to change the entry
         ``MDM_SETUP=&K3\N3'' to ``MDM_SETUP=AT&K3\N3''.
    Connection server fails to return protocol information
         The Connection server fails to return protocol information to an
         application when it is determined by class from the ISDN dialer.

    Downloading firmware to qlogic adapter is slow
         At bootup time, the qlc1020 driver may take several minutes to
         download firmware to the adapter.

    Duplicate controller numbers
         On Compaq systems with an IDE controller and with more than one
         Compaq HBA installed (either SCSI-2 using the cpqsc driver, or SMART
         arrays using the ida driver), it is possible to get duplicate
         controller numbers in the resource manager database. This will
         result in a message at boot time requesting that you press <Esc> to
         continue or <Enter> to rebuild the kernel. The rebuild will occur
         automatically if no key is pressed for 30 seconds. The system will
         reboot and as the duplicate controller numbers remain in the
         database the process will loop.

         To recover from this reboot loop, press <Esc> to stop the kernel
         rebuild. After the system boots, run /sbin/dcu to change the UNIT
         number of the IDE controller to something unused by any other HBA
         controller on the system.  See dcu(1M) for instructions on how to
         run the DCU. You are likely to find that unit number 1 is not used
         by any other HBA controller. Be sure to save your changes when
         exiting the DCU. One additional reboot will be required so that the
         IDE driver will begin using the new UNIT number that you assigned
         using the DCU.

    IEEE 1284 compliant printers
         Some IEEE 1284 compliant printers do not operate correctly if the
         SELECTIN signal from the parallel port is asserted when printing.

         There are four tunable parameters that control the behavior of
         SELECTIN. They are LP0SELECT through to LP3SELECT.

         LP0SELECT indicates whether the SELECTIN signal on parallel printer
         port 0 should be asserted to select a printer.  LP1SELECT through to
         LP3SELECT have the same purpose for ports 1 through 3.

         If SELECTIN is to be asserted on port 0 while printing, set
         LP0SELECT to 1. Similarly for ports 1 through 3.

         If SELECTIN is not to be asserted on port 0 while printing, set
         LP0SELECT to 0. Similarly for ports 1 through 3.

         Note that many printers which are not IEEE 1284 compliant ignore the
         SELECTIN signal altogether, and so will be unaffected by the values
         to which these tunables are set.

    Selecting incorrect support modules
         During installation, UnixWare 7 automatically detects the
         multiprocessor configuration of your system and recommends a
         selection if you choose to install the Multiprocessor support
         package. Most of today's systems comply with the Intel
         multiprocessor specification.  In some cases, however, you need to
         select the vendor-specific multiprocessor support modules, which are
         listed on the multiprocessor selection page. Only if UnixWare cannot
         determine the appropriate multiprocessor support modules should you
         choose the selection by hand.

         Choosing the wrong multiprocessor support modules, for example,
         choosing the Compaq modules for a Compaq Proliant 2500 system, is a
         common error, because the option Compaq Proliant 2000 indicates the
         specific model, not a family of systems. This will often result in a
         kernel that will not boot properly.

         If you choose the incorrect support modules, interrupt the boot
         sequence, set PSM=atup, then, once the system has booted, use
         pkgrm(1M) to remove the osmp package and pkgadd(1M) to add the
         correct multiprocessor support modules.

    Corrupt display on Intel M440LX DP system
         On an Intel M440LX DP server board (such as the Micron NetFrame
         MVE5000) system with a Cirrus Logic 54M40 video chip on the
         motherboard using the native Cirrus Logic 54M40/30 driver, and the
         standard 0.5MB of video RAM, the SCOlogin screen is corrupt.

         This is because the graphics driver requires at least 1MB of video
         RAM to operate. The graphics device can be operated in high
         resolution mode by selecting the VESA driver within the Video
         Configuration Manager. To do this, start the Video Configuration
         Manager and press Modify.  If it then displays a short list of
         auto-detected adapters, press Configure adapter not listed above...
         to obtain a full list of all adapters. From the full list of
         adapters, near the bottom of the list, there will be an entry for
         ``VESA (...adapter name...)''. Choose this VESA entry.

    Remapping bad blocks from SCO OpenServer
         Remapping SCO OpenServer bad blocks may cause a panic with HBAs
         written to DDI 7.2.

         See ``Bad sector/track mapping'' in the online documentation for
         information about remapping disks.

    Stamps on converted SCO OpenServer disks
         When sdimkosr5(1M) converts disks from SCO OpenServer Server systems
         to be used on UnixWare 7 systems, it does not assign valid disk
         stamps on the converted disks.  As a result, the uninitialized disk
         stamps left on the converted disks may collide with stamps on other
         disks in MPIO configurations and cause data corruption.

    Compaq LTE5280
         On some newer laptop systems, the video drivers provided with
         UnixWare will fail to work properly. Contact your system vendor to
         ensure that you have the latest BIOS revision for your laptop.

    MPIO with two adsl drivers
         You cannot boot a system with MPIO installed that has two adsl 2944
         drivers configured on the same SCSI bus. A panic may occur if you
         try to do this.

    Storage Works RAID box
         At runtime, the Storage Works RAID box is not visible to the qlogic
         driver.

    Network adapters not suitable for network installation
         Systems that have the following network adapters cannot be used to
         perform a network installation:

            3Com 3C507 EtherLink 16 Series
            3Com 3C523 EtherLink MC Series
            Compaq NetFlex-1 ENET/TR (Board ID CPQ6100)
            Compaq NetFlex-2 ENET/TR (Board ID CPQ6101)
            Compaq NetFlex-2 TR (Board ID CPQ6002)
            Compaq NetFlex-2 DualPort ENET (Board ID CPQ6200)
            Compaq NetFlex-2 DualPort TR (Board ID CPQ6300)
            Intel 2104x/2114x based 10/100 Mbps Ethernet Controllers
              (Exceptions: SMC EtherPower 8432/8434 10 mbps PCI Ethernet
              Adapter, SMC EtherPower 9332DST/BDT/BVT 10/100 mbps PCI
              Adapter)

         In addition, adapters newly supported in UnixWare 7.0.1 (as listed
         in Chapter 3 of this book) are not suitable for performing a network
         installation. This limitation will be removed at a later date.

    Corrupted cursor
         The cursor is corrupted on systems with the following graphics
         adapters that have more than 64MB of memory:

         +  Diamond Stealth 64 (Trio64)

         +  S3 86c764

         +  S3 86c732

         To remedy this problem, for machines with more than 64MB but less
         than 2.5GB of memory, edit the grafinfo file as follows:

         +  Change each occurence of the following:

            MEMORY(0x4000000, 0x200000)

            to read:

            MEMORY(0xA0000000, 0x200000);   /* 2MB at 2.5GB */

            This moves memory to the 2.5GB limit.

         +  Change each occurence of the following:

            /* Set upper word of starting address: 0x4000000 (64 Mb) */
            out(0x3d4, 0x59);
            out(0x3d5, 0x04);       /* Upper byte 31:24 */
            out(0x3d4, 0x5a);
            out(0x3d5, 0x00);       /* lower byte 23:16 */

            to read:

            /* Set upper word of starting address: 0xA0000000 (2.5 Gb) */
            out(0x3d4, 0x59);
            out(0x3d5, 0xa0);       /* Upper byte 31:24 */
            out(0x3d4, 0x5a);
            out(0x3d5, 0x00);       /* lower byte 23:16 */

            The following two lines are changed:

            /* Set upper word of starting address: 0xA0000000 (2.5 Gb) */
            out(0x3d5, 0xa0);       /* Upper byte 31:24 */

         For machines with more than 4GB of memory, edit the grafinfo file as
         above, but instead of the fixed address of 0xA0000000, substitute
         the address assigned to the hardware by the PCI bus, which you can
         identify from the Resource Manager.

    Display corruption
         The Video Configuration Manager attempts to autodetect installed
         adapters whenever you use it to add or modify video configuration.
         When the manager is run in graphical mode, auto-detection might
         sometimes cause temporary corruption of your display. This condition
         is transient and benign, and it does not indicate problems with your
         video hardware or configuration.

    Serial OSA
         The serial OSA may take approximately five minutes to return
         information to managers and dialin services. Managers affected
         include:

         +  Serial Manager

         +  Network Configuration Manager

         +  Modem Manager

         The following message may be displayed:

            Determining configured serial ports


    SMC9332DST adapter
         The SMC9332DST adapter does not work on 10BaseT (10 Mbps) networks.
         The driver does not correctly detect media type for this model,
         though it does operate the SMC9332BDT correctly at 10Mbps.  The
         SMC9332DST adapter functions correctly on 100BaseTX networks.

    Matrox Mystique video driver
         You cannot use the CDE desktop on a system that uses a Matrox
         Mystique video driver.

    Removing modems using Network Configuration Manager
         After adding a modem device using the Network Configuration Manager,
         the option to remove the configured device will not be selectable
         from within the Network Configuration Manager. The configured modem
         can be removed by using the Modem Manager.

    Network Configuration Manager user
         You must be root to run the Network Configuration Manager.  It is
         not possible to run this manager as system owner.

    Toshiba Laptop Computers
         On many Toshiba laptop computers, the BIOS setup screen contains a
         configurable parameter for the Video Display Segment Address which
         defaults to ``E400''.  UnixWare 7 graphics modes will not function
         properly unless this parameter is set to ``C000''.

         If possible, set the parameter correctly before installation.  If
         you do not do so, the auto-detection of the video display chipset
         may fail and you will need to reconfigure it by hand later.

         If you have already installed UnixWare 7 on your laptop you will
         need to set the segment address correctly, then run the SCOadmin
         Video Manager to reset your display type.


 Console multiscreens

    In UnixWare 7, the default configuration of the console gives a similar
    look and feel to that of SCO OpenServer console multiscreens.

    When the system enters multiuser mode, seven multiscreen text login
    prompts and one graphical login prompt are presented. The traditional SCO
    OpenServer screen switch sequences can be used to navigate among the
    multiscreens, with the following exceptions:

    +  The first multiscreen is reached be pressing <Ctrl><Alt><Esc>, or
       alternatively <Ctrl><Alt>h, instead of <Ctrl><Alt><F1>.

    +  The graphical login prompt is reached by pressing <Ctrl><Alt><F1>.

    All the traditional SCO UnixWare 1 and 2 screen switch sequences have
    also been preserved and can be used in conjunction with the newer
    UnixWare switch sequences.  See the keyboard(7) manual page for further
    details of these. Users who prefer to use vtlmgr(1) and newvt(1) instead
    of multiscreens can still continue to do so. The default configuration
    described above uses virtual terminals 00 through 08. The first free
    virtual terminal available is therefore 09. To return the console to the
    traditional SCO UnixWare configuration without text login prompts, run
    the following command:

       sacadm -d -p contty

    The login prompts can be subsequently re-enabled by running the following
    command:

       sacadm -e -p contty

    If you prefer to have eleven text login prompts as in SCO OpenServer,
    instead of the default seven, you can run the following script to enable
    the extra login prompts:

       for i in 09 10 11 12
       do
       pmadm -a -p contty -s $i -S login -fu -v `ttyadm -V` \
       -m "`ttyadm -d /dev/vt$i -l console -s /usr/bin/shserv \
       -p \"Login (vt$i): \"`"
       done


    Note there must be no trailing spaces after the backslash (``\'')
    characters at the ends of the third and fourth lines.

    _________________________________________________________________________
       NOTE  This script was incorrect in the previous version of these
       release notes.  It is now correct.
    _________________________________________________________________________

    For more information on using multiscreens see ``Running programs
    simultaneously with multiscreen displays'' in the online documentation.
    Note that the diagram in this section indicates that the first
    multiscreen is on <Ctrl><Alt><F1>, when it is now on <Ctrl><Alt><Esc> as
    described above.





 Chapter 5
 Software notes

    This section describes software limitations under the following headings:

    +  ``Localization and internationalization''

    +  ``System management''

    +  ``Command line and shell''

    +  ``Users and groups''

    +  ``Filesystems''

    +  ``Backup and restore''

    +  ``SCO ARCserve/Open''

    +  ``Printing''

    +  ``Networking''

    +  ``Mail and messaging''

    +  ``Desktop, SCOhelp and Netscape''

    +  ``X server and graphical environment''

    +  ``man pages''

    +  ``Security''

    +  ``Tcl''

    +  ``Emergency recovery with an encapsulated or mirrored root disk''

    +  ``XENIX''

    +  ``Domestic encryption''

    +  ``Documentation''

    See also Differences for SCO OpenServer and SCO UnixWare 1 and 2 users
    for areas in which UnixWare software differs from SCO UnixWare 2.0 and
    SCO OpenServer.


 Localization and internationalization


    +  The Latin1 locales which were provided in SCO UnixWare 2.1 in the IBM
       codepages 437, 850, 865, 646 and 863 are preserved for backward
       compatibility. They will be retired in the next release of UnixWare
       and are not supported in this release.

    +  The International Settings Manager should not be used to administer
       the settings on a remote system and should only be run as a foreground
       task.

    +  In single-user mode, the console is only configured correctly for
       displaying text. It is not configured correctly for entering of text.
       The root password can therefore only contain 7 bit characters if the
       root user wishes to be able to log in in single-user mode.

       Once logged in, the root user needs to do the following:

       1.  Run mapkey(1M)

       2.  Run mapchan(1M)

       3.  Run stty(1) with the istrip option to stop the high bit being
           stripped.

       4.  Set TERM=AT386-ie and export it.

       This is necessary before running any kind of command which is screen-
       orientated, for example, vi or scoadmin.

       In multiuser mode, on any virtual terminal other than vt00, the
       console is not configured correctly.  If a user's password contains
       8-bit characters they will not be able to log in on these virtual
       terminals.  If the console is in multibyte mode, any multibyte
       character will not be displayed correctly.

       Once logged in, an ordinary user in an 8-bit locale needs to run the
       following:

          /etc/mapchan

       An ordinary user in a multibyte locale needs to run the following:

          /sbin/loadfont


 Not internationalized or localized

    The following scoadmin managers, applications and commands are not
    internationalized, or are only partially internationalized, and therefore
    will only appear in English:

    scoadmin managers


    +  parts of the Netconfig (TCP, WAN) Manager

    +  ISA Plug and Play Configuration Manager

    +  Netscape Server Admin Manager

    +  the titles in the NetWare Service Manager

    +  Process Manager

    +  SLIP Manager

    +  Veritas Volume Manager

    +  The list of timezones in the Time Zone Manager is not translated.


    Applications


    +  VisionFS is not internationalized. The interface appears in English
       only.

    +  SCO ARCserve/Open is not internationalized and therefore displays its
       menus and other interface components in English only. It will backup
       and restore filenames which include non-ASCII characters.

    +  Lynx is only partially internationalized.  English messages appear on
       some menus and prompts.

    +  pine(1) is not internationalized and therefore displays all its
       messages in English.  In addition, pine does not support Japanese mail
       standard ISO2022-JP.


    Commands


    +  The messages for the following commands always appear in English:

       -  sdipath(1M)

       -  sdimkosr5(1M)

       -  rlpconf(1M)

       -  hpnpcfg(1M)

    +  The list of timezones is not translated.

    +  The responses to questions from fsck(1M) are not localized. Press
       ``y'' for ``yes'' and ``n'' for ``no'' in all locales.


 Documentation


    +  When the locale is set to one whose codeset is not Latin 1 (for
       example, C, Japanese, Polish, Russian), the following characters may
       be displayed incorrectly or cause the terminal layout to be disrupted
       when viewing the English documentation:

       -  Copyright

       -  Registered Trademark

       -  Plus or minus

       -  Acute accent

       -  ``Half'' character

       -  ``Multiply'' character

       The copyright character occurs only at the foot of man pages and on
       copyright pages. The other characters may occur intermittently
       throughout the documentation set.

    +  Searching is currently supported in English, French, German and
       Spanish.  Searching is not supported for Asian languages.

    +  The Verity search engine uses only English-language rules to find
       ``stemmed'' (plural and other inflected) forms of words.  This may
       result in spurious results in languages other than English.  If this
       is a problem, enclose all search strings inside double quote (``"'')
       characters.

 CDE and X11


    +  dtlogin(X1) does not support dead keys or compose keys.  In general,
       users should not select passwords that contain non-alphanumeric (8-
       bit) characters.

       On the German keyboard, the following ASCII characters are unavailable
       to dtlogin:

          ~ [ ] { } |  @

       On the Spanish keyboard, the following ASCII characters are
       unavailable to dtlogin:

           | @ # [ ] { }

       On the French keyboard, the following ASCII characters are unavailable
       to dtlogin:

          ~ # { } [ ] | `  ^ @

       Please refer to your own keyboard for details on other characters.

    +  The following Xkeyboards cannot be installed:

       -  Russian

       -  Polish

       -  Czech

       -  Hungarian

    +  Non-Latin1 locales, other than Japanese, are supported only on the
       console and not under X.  The primary reason for this is that no X
       fonts are provided for these locales.  Users may download their own
       fonts from a variety of sources.  They may also need to modify several
       X font resources.

       The non-Latin1 locales are:

       -  Chinese
       -  Croat

       -  Czech

       -  Greek

       -  Hungarian

       -  Polish

       -  Romanian

       -  Russian

       -  Slovak

       -  Slovenian

       -  Turkish

       -  Ukrainian

    Japanese


    +  Neither dtterm nor xterm(X1) correctly handles multibyte characters.
       Do not use them if you are in a multibyte locale such as Japanese.

    +  Japanese buttons do not display completely in a dtterm or xterm.

    +  The input method for Japanese using SJXM is not fully functional in a
       dtterm or xterm.

    +  dtmail does not support the Japanese mail standard ISO-2022-JP.


 System management

    See also ``Emergency recovery with an encapsulated or mirrored root
    disk''.

    +  In order to install the Data Management services (SCO(r)
       ARCserve(r)/Open), it is first necessary to install SCO NetWare (nuc
       and nwnet). This dependency exists even if your server is not
       connected to a NetWare LAN because SCO ARCserve/Open tests for the
       presence of NetWare at runtime.

    +  To use the command emergency_disk(1M) while you are logged in to the
       CDE desktop, you must specify the full pathname of the command:

          #sh /sbin/emergency_disk -d / diskette1

       This example assumes that you are logged in as root and that /sbin is
       in your PATH environment.

    +  fstyp(1M) does not recognize the format of the emergency boot
       floppies.

    +  This release of UnixWare 7 is 7.0.1.

    +  If the Online Data Manager (ODM) is installed on the system, messages
       stating that a panic dump is available in /swap are not displayed. The
       panic dump information is, however, always available in /swap.

    +  When you add an ODM license, the following message is displayed:

          unknown product with id 157

       This message indicates a correctly installed VxVM mirroring or ODM.

    +  The LDAP, Network Config and Virtual Domain SCOadmin managers cannot
       be run as system owner; they must be run as root.

    +  devnm(1M) works only on filesystems mounted on devices that have
       backing storage. It fails on memfs and under ODM, and on other
       pseudo-filesystems.

    +  To reboot from the kdb(1M) prompt, enter the following:

          kdb>> 1 0 mdboot 2 call


    +  Loading kdb(1M) dynamically does not enable the Debug Extension bit of
       cr4 on Pentium processors and higher. Use statically linked kdb on
       these processors.

    +  On some multi-processor systems, the keyboard may become irrecoverably
       corrupted while kdb(1M) is running. The only solution to this is to
       press the restart button on the computer.

    +  When installing an application such as a commercial database package
       which makes use of raw asynchronous I/O (AIO_RAW), you will need to
       change the mode, group and owner (as appropriate) of the device node
       /dev/async.  See Node(4dsp).

    +  The system variable SYSDUMP_SELECTIVE is not configurable via the
       System Tuner. See crash(1M) for details.

    +  You cannot run pkgtrans(1) from csh.

    +  The Installation Manager leaves the CD-ROM mounted when installation
       is complete. Use umount(1M) to unmount the CD-ROM before removing it.
       Enter the following:

          umount /dev/cdrom/cCbBtTlL

       from the shell. C,B,T, and L are controller, bus, target (SCSI ID),
       and logical unit number (LUN) respectively.

       Once the update is installed, use the command:

          umount /dev/cdrom/cdromN

       where N is the CD-ROM driver number.

    +  The license scheme used by UnixWare 7 is different from that used by
       UnixWare 2. Applications originally designed to install on UnixWare 2,
       such as Oracle(r) 7.3.3, use the file /etc/.snum to verify that the
       operating system is UnixWare. This file is not part of the UnixWare 7
       licensing system, and therefore the installation of these applications
       may fail.

       To work around this problem, log on to the system as root or the
       system owner and enter:

          touch /etc/.snum


    +  When limited space is available on the hard disk, it may not be
       possible to remove unwanted packages to free up more space. Try to
       install only packages that are actually required.

    +  Do not use cp(1) or any other method to replace an executable file
       with an updated version while the existing file is being executed.
       This will result in a core dump.

    +  The real time performance monitor, rtpm(1M), may lose track of the
       current tty if the same session runs for a number of days.

    +  The Process Manager exits if it is running in background when you view
       processes using tty(1).

    +  The first time the details of a cron(1M) job are displayed, there is
       an extra zero in front of the hour field.

    +  To use SCOadmin managers in single-user mode, you must first set the
       terminal type manually. To identify and set the correct terminal type,
       see /etc/default/coterm or run the following command:

          eval `defadm coterm TERM`; export TERM


    +  The ``h'' accelerator key selects only the Help menu in the System
       Defaults Manager. Use the mouse or <Tab> and <Space> keys to select
       the Hosts menu.

    +  You can select only years up to 2037 in the Set Time Manager.

    +  The desktop menu option Copy to Folder is useful only on the CDE
       desktop. Do not attempt to use it on other desktops.

    +  In addition to the /etc/magic file shipped with UnixWare, there is a
       Java class aware version of the file available on the Skunkware CD-
       ROM.

    +  You can only select one processor at a time in the Processor Manager.

    +  SCOadmin managers may take a long time to start if the machine goes
       off the network.

    +  You cannot set the values of a table of MIB items using the SCOadmin
       Intranet Manager. This must be done from the command line using
       setany(1Msnmp).

    +  pkgadd(1M) may display the following message before exiting:

          UX:mailx: WARNING: No message

       This is harmless and may be ignored.

    +  In the SCOadmin License Manager, when you select a license from the
       list in character mode, be sure to deselect any license you do not
       want to act on by using the arrow keys to highlight the item, then
       pressing the space bar.

    +  When a package fails to install for any reason, the installation GUI
       may still report that the set of packages that contains it was
       installed successfully. The message reporting the failure is generated
       by pkgadd(1M).

       Similarly, if the removal of a package fails, the GUI does not report
       the failure. The icon for the set of packages goes away and is not
       replaced by the package icon for the package that is still on the
       system.

       The log created by pkgadd, which contains details of the failed
       processes, is in /var/sadm/install/logs/pkg.log where pkg is the name
       of the package.

    +  You cannot run the network installation server as owner. Use a root
       login.

    +  If the -c option to pkgmk is specified, you must also specify the -r
       option.

    +  pkgmk does not work with a tape device.

    +  The information provided in the documentation about starting the Hot-
       Plug Manager is incorrect.  The correct procedures are as follows:

       You can start the Hot-Plug Manager in any of these ways:

       +  Choose SCOadmin from the SCO menu (above the SCO logo) on the CDE
          desktop, then select Hardware, then select Hot-Plug Manager.

       +  Start the SCOadmin launcher by entering scoadmin on the command-
          line, then select Hardware, then select Hot-Plug Manager.

       +  Enter scoadmin Hotplug Manager on the command-line (or abbreviate
          to scoadmin hot).


 Command line and shell


    echo ignores -n argument
       The built-in echo command in ksh(1) ignores the -n argument if
       provided. This may cause problems with legacy shell scripts.

    ksh fails when incorrect script run
       ksh(1) fails when an incorrect script similar to the following is run:

          foo()
          {
          echo ${$1}

       The following error is displayed:

          The error: ksh: syntax error: `1' unexpected
          Memory fault(coredump)

       In some circumstances, the failure may occur when the next shell
       command is run.

    TIMEOUT for sh
       The manual page for sh(1) incorrectly implies that TIMEOUT can be set
       in the user's .profile. TIMEOUT can be set only on a system-wide
       basis.

    tr (1)
       tr(1) now requires the dash (-) character to be escaped with a
       backslash (\).

    vi editor
       When you edit a multiline command from the history file using vi(1),
       the cursor does not correctly step over a newline character (displayed
       as ^J).  Therefore, the cursor position in the edit buffer is
       incorrect.  The multiline command can be edited correctly by entering
       control mode, fetching the multiline command and typing v. This will
       invoke the /bin/vi command.

    SCO OpenServer scoterm
       If you run the SCO OpenServer scoterm command, it will corrupt the
       entries in /var/adm/utmpx.  As a result, all further login attempts
       will be blocked (as well as causing invalid data for any other
       administration commands which use it) until the utmpx entry is
       removed, and a UnixWare command rebuilds it.  Since this corruption
       can not be prevented, it is recommended that the SCO OpenServer
       scoterm binary is not run on UnixWare.

    Passwords reported as locked
       The command passwd -s -a always shows the user's password as locked
       (``LK''), even when the password is present or missing.

    terminfo settings
       The commands vi(1), pg(1) and possibly others that use the terminfo(4)
       settings, may fail unexpectedly if the settings for stty(1) are
       changed from the default. Use the command

          stty sane

       to restore the default stty settings.

    Using cu as root
       If your system is configured with a modem that accepts incoming calls,
       you cannot use cu(1bnu) to log into a remote sh shell as root.


 Users and groups


    +  When you log into an FTP server, the home directory is always ``/''.

    +  The root user is not permitted to perform a number of system
       administration tasks from the desktop. Only the root user, however,
       can install software using pkgadd(1M) from the command line.

    +  Only numbers and lower case letters are permitted in login names.
       Accented characters are not permitted.

    +  You cannot run the SCOadmin Account Manager in an xterm on an NCD-19
       system.

    +  If you create a user in the Account Manager and specify that the user
       must change the password at the first login, you must still enter a
       password in the password field. The user cannot log in without a
       password on the first login.

    +  The SCOadmin Account Manager does not set up a proper .login file for
       new csh users.  csh users wishing to use SCOadmin tools should add the
       following line to their .login:

          eval `/usr/lib/scoadmin/account/setenv -c $HOME`

       See csh(1) for full information.

    +  The SCOadmin Account Manager may create new user accounts with home
       directory permissions that differ from those specified in
       /etc/default/useradd. Use Options -> User Defaults in the Account
       Manager to set the desired permissions.


 Filesystems

    For VisionFS known problems and workarounds, see ``Late-breaking
    information'' in the online documentation.

    Panic when two processes close a FIFO
         A race condition may occur when two processes attempt to close the
         same FIFO. One process will find fn_open to be greater than 0 and
         will free the kernel memory for the stream. If that happens before
         the other process has woken up all the associated sleeping
         processes, the system will panic.

    NFS server man page
         The nfsd(1Mnfs) manual page for the NFS server front end refers to
         two options, -c and -q, which are not supported in UnixWare 7.

         These options relate to connection-based transports which are not
         supported by UnixWare 7 NFS, and should be ignored in the
         documentation.

    Listing of symbolic links over NWS
         The command ls -l (see ls(1)), when run over NWS, returns the size
         of the destination file, not that of the symbolic link in the
         directory in which it is run. This may cause problems when the
         output of the command is used as input to cpio(1).

    devnm
         The command devnm(1M) does not run on the root filesystem.

    Filesystem Manager permissions
         The owner may appear to not have permission to run the SCOadmin
         Filesystem Manager, even though permission has been granted.  This
         occurs when fsUtils.tlib has a newer date than fsUtils.tndx but the
         mode on fsUtils.tndx does not permit the owner to rebuild the .tndx
         file.

         Run the Filesystem Manager as root once, then it will work for
         owner.
    Bad block for VTOC causes panic
         The virtual table of contents (VTOC) resides on block 29 in the
         active UNIX Partition.  The system will panic if the physical block
         is bad. If this occurs, modify the UNIX partition by moving it up
         one cylinder so that the 29th block in the active partition no
         longer touches the bad block and is not used at all.

    Advanced Option option in Filesystem Manager
         In the Filesystem Manager, the text in the option ``Advanced Options
         for Mounting CD-ROM'' does not display correctly in character mode.
         Use the desktop version of the SCOadmin Filesystem Manager to use
         this option.

    Enabling DMAPI access to VXFS
         Data Management API (DMAPI) access to the kernel is not enabled by
         default.  Do the following to enable DMAPI kernel access.

         _______________________________________________________________________
            NOTE  Besides enabling DMAPI,  you must also license it before
            you can use it.

            VXFS must be configured into the system otherwise the system
            will not build with DMAPI.
         ______________________________________________________________________


         1.  Edit /etc/conf/sdevice.d/vxportal to change the second column of
             the last line from a N to a Y. That is, change this line:

                vxportal    N   0   0   0   0   0   0   0   0   -1

             to this:

                vxportal    Y   0   0   0   0   0   0   0   0   -1


         2.  Rebuild and reboot the system:

                /etc/conf/bin/idbuild -B


    Veritas Volume Manager (VxVM)
         The Veritas Volume Manager (VxVM) product will not install if the
         system is configured to have a separate /var file system.  If you
         wish to use VxVM to manage the root disk do not configure your
         system to have a separate /var file system.

    Shared directories error VxFS
         The Filesystem Manager may incorrectly display the following error
         when specifying shared directories on high-specification systems:

            Error while sharing directory

         This error is caused because the copy of the filesystem database
         that the graphical manager uses is updated only once per second. The
         process of sharing a filesystem updates the filesystem record more
         quickly than this on a fast system, and the modification date on the
         filesystem may therefore not match that of its record.

    You should install osmp during system installation if possible, in order
    to avoid possible corruption of large drivers that may occur when ODM is
    installed without osmp being present. This corruption may cause the
    Volume Manager and other managers to crash.

    In the SCOadmin Filesystem Manager, in a character environment, the
    Select button for the Remote Directory field on the Add Remote Filesystem
    screen is not reachable. Either enter the remote directory name by hand
    or use the X/Motif version of the Filesystem Manager.

    The SCOadmin Filesystem Manager may not show any mount status information
    after the Volume Manager has been installed. Refresh the view in the
    Filesystem Manager by selecting View -> Disk Usage then selecting View -
    > Mount Status again.

 Netscape and NFS

    Files may be truncated when saved from the Netscape browser and other
    clients to remote NFS filesystems.  This problem can only occur if the
    NFS filesystem is explicitly mounted with the intr or soft mount(1Mnfs)
    options. If you do save files from clients onto a remote file system
    mounted with the intr or soft options, you should check the file contents
    immediately afterwards.

 Large file support

    Filesystems up to 2^40 bytes (1TB) are supported. A single file can thus
    consume up to 1TB of disk store. A sparse file can exhibit length up to
    2^63 bytes. New system interfaces, lseek64(2) and mmap64(2), permit
    operations of this entire length. Compiler extensions allow for a C
    application to conveniently manipulate files of such size via 64 bit
    integers (called ``long long'').

    The pax(1) utility supports the archival of files larger than 2 Gigabytes
    (2GB) in size when using the default ``ustar'' format.  Files up to
    2^63-1 bytes in size are supported. The pax utility also supports
    filenames and symbolic link filenames up to 1024 characters long when
    using the default ``ustar'' format. Older versions of pax will not be
    able to extract files larger than 2GB in size, or files whose filenames
    or symbolic link names are larger than 255 characters long.

    The cpio(1) utility supports the archival of files larger than 2
    gigabytes (2GB) in size when using the ASCII (-c) or CRC (-H crc)
    formats. Files up to 2^63-1 bytes in size are supported. Previous
    versions of cpio will not be able to extract files larger than 2GB in
    size.

    A limited set of system utilities have been made large-file aware, and
    are noted as such on their respective manual pages.

    _________________________________________________________________________
       NOTE  Large file support is intended for specialized applications
       which need to deal with more than 2GB of data in a single file, and
       not for general purpose text files and similar.
    _________________________________________________________________________



 Backup and restore

    The SCO OpenServer version of cpio(1) is available so that you can
    restore archives made using the Backup Manager under SCO OpenServer. You
    should not use the SCO OpenServer command to make backups under UnixWare.

    Set the environment variable OSRCMDS=on to use the SCO OpenServer version
    of cpio or any command. Remember to unset the variable when you have
    finished restoring the backup.  Alternatively, use the full pathname
    /OpenServer/bin/cpio.

    Restore operations can be performed using the cpio utility on the command
    line. The examples included here assume you are using the standard tape
    device, /dev/ctape1.

    To restore a backup:

       cpio -iAmudB -I /dev/ctape1

    Restore individual files or directories by adding them to the end of the
    command line.  Use the full pathname and omit the leading ``/'', as in
    this example:

       tmp/hold/time

    Use the ``*'' Bourne shell wildcard character to restore a directory, as
    in this example:

       tmp/hold/other/*

    To verify a backup:

       cpio -itvn -I /dev/ctape1

    To list the files on a backup:

       cpio -iABmudq -I /dev/ctape1 \*

    This command reads the first file off the media.  Backups created by the
    SCO OpenServer Backup Manager include a file list called
    _BACKUP_CONTENTS_ at the beginning of each backup.  If the backup was
    created by another means, use this command to list the files:

       cpio -itv -I /dev/ctape1

    _________________________________________________________________________
       NOTE  When a disk is recovered, the size of the slices is rounded
       up. This means that the recovered filesystem may not fit on the
       same size disk if the backed up disk was nearly full.
    _________________________________________________________________________



 SCO ARCserve/Open


    SCO ARCserve/Open locks SCSI tape devices
            By default, SCO ARCserve/Open locks all of the SCSI tape devices
            attached to your system.  Because of this, your tape devices are
            unavailable for use by backup commands such as tar(1) or cpio(1),
            even if the devices are not currently in the process of
            performing a backup or restore operation by SCO ARCserve/Open.

            ___________________________________________________________________
               NOTE  SCO ARCserve/Open Lite, the version of ARCserve/Open
               provided by default with UnixWare 7 is limited to the use
               of a single SCSI tape drive.
            ___________________________________________________________________

            Depending on the number of tape devices available on your system,
            there are two possible workarounds to this situation.

            +  If your system contains a single SCSI tape drive, you can
               temporarily unlock the device by running astop as root user to
               shut down the SCO ARCserve/Open backend. When you are finished
               using the tape drive, restart SCO ARCserve/Open by running
               astart as root user.

            +  If your system contains multiple tape drives, you can unlock
               one or more individual devices by editing the
               /usr/lib/ARCserve/tapesvr.cfg file and commenting out the
               desired devices in the Device Table section.  Specific
               instructions on how to make these changes are documented
               within the tapesvr.cfg file.

               _________________________________________________________________
                  NOTE  Any tape devices that are commented out of the
                  tapesvr.cfg file are unavailable to SCO ARCserve/Open.
                  You should only use this approach if you do not mind
                  dedicating a tape device to non-SCO ARCserve/Open uses.
               _________________________________________________________________


    ARCserve/Open and high security systems
            If you run ARCserve on a system that has been configured with
            high security, and you create a backup using the Compare Tape to
            Disk verification option, file privileges for any file backed up
            are lost. This harms the system because commands that depend on
            fixed or inherited privileges, such as ftp, rlogin, ping, passwd,
            and share fail for users other than root.

            There are two workarounds:

            +  If you have not already created a backup using the Compare
               Tape to Disk option, turn the option off, by selecting one of
               the other Backup Options (None or Scan Tape Contents) when
               scheduling your backup.

            +  If you already have removed permissions by running a backup
               with the Compare Tape to Disk option turned on, you can
               restore your privileges by logging in as root and executing
               the following command:

               /etc/security/tools/setpriv -x



 Printing

    The following notes apply to printing:

    +  You cannot add a printer using the Printer Setup Manager if the
       printer output is sent to a file instead of to a printer.

       To add a printer of this type, use the command line as follows:

          /usr/lib/scoadmin/printer/pradmin printer_name filename\
          lpadmin  -T hplaserjet -D "HP LaserJet 5L/5ML (PCL)" -I pcl\
          -m standard -v filename -A mail -o nobanner\
          -o "stty='clocal -onlcr'" -p filename


       lp must have permissions to write to the filename

    +  The Printer Setup Manager displays the following error message if you
       use it to add a NetWare printer:

          Unexpected error: Vtcl Server VtSet - Widget not found

       This may be ignored.

    +  In the Printer Setup Manager, if you attempt to specify a nonexistent
       port as the connection port when you add a printer, the process will
       fail.

    +  When you use the Printer Setup Manager to add, copy or view the
       details of a TCP/IP printer connected via a remote server, using the
       <Tab> key to move the cursor across the screen again to the field ``On
       Remote Server'' erroneously toggles the values given for Remote Server
       and Remote Printer.

    +  <Del> has no effect on the Printer Setup Manager.  <Ctrl>C puts the
       terminal into raw mode, and should be avoided.

    +  The SCOadmin Printer Setup Manager does not permit printer names to
       contain the ``_'' character. To add a printer whose name includes a
       ``_'', add it from the command-line.  Once the printer name is
       created, the Printer Setup Manager will be able to manage it.

    +  If you install the highest level of security during installation, the
       Printer Setup Manager will not execute.

    +  To print to Hewlett-Packard printers, you must have installed the
       netmgt package.


 Networking

    The following notes apply to networking:

    +  If you defer network configuration during installation, then use
       netcfg(1M) to configure network drivers, you must reboot the system
       for the network configuration to take effect.

    +  The associated ttymon entry is not deleted when a modem is deleted in
       the Modem Manager. Delete it by hand if necessary, using pmadm(1M)
       with the -r option.

    +  Version 4.9.7 of BIND, which is shipped with UnixWare, does not allow
       underscore characters in hostnames. This is in compliance with RFC952.

    +  The SCOadmin SNMP Agent Manager may fail to run with an error of the
       form:

          Fatal error: building package index for
          `/usr/lib/scoadmin/snmpmgr/generic.tlib' failed: couldn't open
          "/usr/lib/scoadmin/snmpmgr/generic.tndx": permission denied

       To resolve this problem, run the SNMP Agent Manager as root. After it
       has been run once by root, the SNMP Agent Manager can then be run by
       any user with owner privileges.

    +  If a socket performs a listen(3sock), a semaphore is allocated for the
       socket. By default, there are 150 semaphores available on the system.
       If more than 150 semaphores are required the kernel tunable SEMMNI
       must be increased.

       listen(3sock) will fail with ENOSPC if no semaphores are available.

    +  The routine hstrerror is not available.  The manual page
       gethostent(3N) is incorrect.

    +  When TCP/IP is stopped, a message is displayed from talkd(1Mtcp).
       This should be ignored.

    +  DHCP only supports a single subnet on each network interface

    +  If an NIS user who has a long password enters more than eight
       characters of the password, ftpd(1Mtcp) refuses the login. The user
       should only type the first 8 characters.

    +  A problem in IP puts the wrong value, 8 instead of 4, in the
       ``dl_dest_addr_length'' field of the DL_UNITDATA_REQ message sent
       downstream when ARP is disabled.

    +  RFC 1323 is not fully implemented in UnixWare 7. Specifically:

       -  ifconfig(1Mtcp) options relating to rfc1323 are not present.

       -  inconfig(1Mtcp) options relating to rfc1323 are not present.

       -  TCP/IP support for scalable windows and timestamps is not present.

    +  To remove a network adapter configured with TCP using the Network
       Configuration Manager in a graphical session, launch the manager from
       the Panorama desktop only.  Doing this task while the CDE desktop is
       running will cause CDE to hang.  To recover from a hung CDE desktop,
       switch to a character screen, and reboot the system.

    +  You may encounter an error message, similar to the following, when
       trying to configure IPX/SPX over token ring:

          NetWare IPX setup at Fri May 15 11:46:23 EDT 1998
          NWCM-2.1-147: Folder 7 is NOT valid.
          NWNET-2.1-232: Invalid frame_type for configured adapter_type
          Novell Protocol Suite Streams Architecture Daemon
          Reading configuration from "/etc/netware/nwconfig"
          IPX Internal Network configured, setting Router Type to FULL
          Problem starting up npsd

       If you see this message, you should enter:

          nwcm -s "lan_1_adapter_type=TOKEN-RING_DLPI

       and reboot the system.

    +  The connection server can dump core if the Systems file does not have
       a phone number in the phone number field.

       The work around is to place a '-' in the phone number field when you
       do not have any phone numbers (for Direct connections for example).

    +  When UnixWare attempts to communicate with older RPC mechanism, it may
       fail.  This is likely to happen if you try to NFS mount a disk on a
       system that uses older versions of the RPC mechanism.

    +  The Network Configuration Manager incorrectly deletes the domain name
       associated with the primary interface to a gateway in /etc/resolv.conf
       if the domain name for a second interface is added. You must update
       /etc/resolv.conf by hand to include both domain names. See
       resolv.conf(4tcp) for details.

    +  The  command finger(1tcp) may report the idle time of the session from
       which it is called incorrectly.

    +  If you have installed DNS, make sure you have a valid Ethernet
       connection.  If your Ethernet connection is faulty or disconnected,
       and you try to remove packages, the system tries to send email to
       acknowledge the package removal. The system uses the resolve.conf file
       in /etc that was created during the DNS installation to acknowledge
       the package removal.

       If the Ethernet is faulty, the system cannot reconcile any email
       addresses on the network. Thus the system will appear to hang. If this
       occurs, ensure the Ethernet connection is valid and retry the package
       removal, or kill the email processes to free up the removal process.

    +  Do not specify a fully qualified domain name (FQDN) when adding a
       hostname to a primary zone using the DNS Manager. The domain name for
       the zone is appended automatically. For example, specify the hostname
       ``myhost'' rather than ``myhost.test.net.'' in the Records -> Add -
       > Host -> Hostname dialog.

    Anonymous FTP configured as NIS user
       When you use the FTP Server Manager to create the anonymous FTP user,
       if the host under configuration is a client in an NIS domain, the
       creation of the anonymous FTP user will fail if the user is already
       present in the NIS domain.

       To create a local anonymous FTP user, temporarily suspend NIS; create
       the user using the FTP Server Manager; then resume NIS.

    +  To use netcfg(1M) in single-user mode, you must set the terminal type.
       To identify the terminal type, run the following command:

          eval `defadm coterm TERM`; export TERM.


    +  Incoming and outgoing ISDN V.120 calls are not supported.  Devices
       configured as type ISDN_ASYNC are not supported. Service types of
       isdn_async in Callfilter and Callservices are not supported.

 Networking: PPP

    The following notes and limitations apply to the PPP Manager and PPP
    Internet Connection Manager:

    +  By default an ISDN adapter is configured with the Line Direction of
       Outgoing and Incoming enabled.  If the Outgoing Line Direction is
       disabled in the Network Configuration Manager, the ISDN adapter will
       not be available to the PPP Manager for configuration with PPP.  Do
       not disable the Outgoing Line direction for an ISDN adapter if you
       intend to configure the adapter with PPP, even for an incoming only
       PPP bundle.

    +  If the host under configuration is a client in an NIS domain the
       creation of PPP user will fail if the user is already present in the
       NIS domain.

       To create a local PPP user, temporarily suspend NIS; create the user
       using the PPP Server Manager; then resume NIS.

    +  Ensure that all WAN devices are configured for communication in the
       direction required before including them in any PPP configuration. Use
       the WAN view of the Network Configuration Manager, netcfg(1M), to set
       the communication direction for each device.

    +  When creating outgoing connections, ensure that the remote host name
       for the destination system is configured correctly in the Dialup
       Systems Manager.

    +  When creating incoming connections ensure that the devices used for
       the links are configured in the Dialer Services Manager.

 Configuring router discovery on multiple routers

    The routing daemon, routed(1Mtcp), in UnixWare 7 implements router
    discovery by default.

    On a router (a system with more than one network interface configured,
    and with ipforwarding and ipsendredirects set to 1), routed advertises
    and responds to router discovery solicitation messages. Note that systems
    that are configured with both a LAN connection and a WAN connection (PPP
    or SLIP) may also be acting as routers to external networks such as the
    Internet.

    On non-routing hosts, routed keeps track of received router
    advertizements, adding a default route for the highest preference route.
    For this reason, multiple routers running router discovery on the same
    subnet should use different preference values. A preference value is an
    integer greater than 0. The most preferred route should have the highest
    value. You should not configure a router to advertize a route on an
    interface if this might lead to inefficient routing of packets through
    the local subnets.

    The following example entries from the /etc/inet/gateways configuration
    file on a router cause routed to advertize a route with a preference of
    10 on the subnet connected to the net1 interface, but not to advertize on
    the subnet connected to the net0 interface:

       if=net0 no_rdisc_adv
       if=net1 rdisc_pref=10

    If some routers on a subnet implement router discovery while others do
    not, or if identical or incorrect preference values are configured on the
    routers, non-routing hosts may install an incorrect default route.

    To disable router discovery on routers and non-routing hosts running
    routed:

    1.  Add the following line to /etc/inet/gateways (create this file if it
        does not already exist):

           no_rdisc


    2.  Find out the process ID (PID) of in.routed by entering the following
        command:

           ps -ef | grep in.routed

        The process ID is the number in the second column. For example, the
        PID in the following output is 1991:

           root  1991  1   TS  80  0 11:28:32 ?   0:02 /usr/sbin/in.routed


    3.  Kill and restart routed by entering the following commands:

           kill PID
           in.routed

        Alternatively, shut down and reboot the router.

 NetWare Services

    The following notes apply to the NetWare Services software and
    documentation:

    NetWare licensing

    UnixWare 7 is shipped with a zero-user NetWare Services license. This
    allows an installed UnixWare system to participate in a NetWare network
    as documented without further action on your part. It is visible to other
    nodes, and users can see the NDS directory. For the system to use NWS
    services, you must obtain an Additive License Pack. Contact your SCO
    supplier for details.

    Directory Services Repair

    Running Directory Service Repair in an xterm can corrupt the display. To
    avoid this, run it on the console. See ``Directory Services Repair'' in
    the online documentation under Networking -> Administering NetWare
    Services (NWS) for information.

    The ``nwsup'' package

    The NetWare Services (NWS) ``nwsup'' package (NetWare Integration Kit) is
    not distributed with UnixWare 7, although references to it appear in the
    UnixWare 7 documentation.

    This package was distributed with SCO UnixWare 2.1 and contained floppy
    images of additional NetWare Loadable Modules (NLMs) which could be
    installed on top of existing Native NetWare servers.  These NLMs added
    support for additional UnixWare semantics when accessing files on the
    server (mode and ownership in particular).  They were known collectively
    as the ``NUC NLM'' or sometimes the ``UnixWare NLM''.

    A standard Native NetWare server supports file access semantics in what
    is called ``DOS Mode''. The NUC NLM added two more additional modes
    called ``NetWare Mode'' and ``UnixWare Mode'' which provided increasing
    levels of SCO UnixWare file access semantics.

    While the NUC NLM is no longer supported, references to ``NetWare Mode''
    and ``UnixWare Mode'' appear in the context of modes supported by the
    UnixWare NetWare server. These are still valid.  They are only obsolete
    when referring to the Native NetWare server with NUC NLMs added.

    This issue affects the Networking -> Administering NetWare Services
    (NWS) -> Administering NetWare Connectivity online documentation topic,
    particularly the following:

    +  Overview of NUC Connectivity

    +  NetWare Loadable Modules

    +  Accessing NetWare volumes from UnixWare

    +  NetWare backup and restore

    nwcm (1Mipx)

    The nwcm(1Mipx) manual page refers to the lan_x_adapter and lan_x_network
    parameters. These can no longer be accessed via nwcm: instead,
    configuration of these values is now handled with the netcfg(1M) utility.

    Directory Services installation in an xterm

    The Directory Services installation program may display empty dialog
    boxes when used in an xterm.  To avoid this, run it on the console.

    NetWare Setup

    The owner user cannot use NetWare Setup. The root user must use this
    manager.

    NetWare installation from command line

    The online topic Networking -> Administering NetWare Services (NWS) -
    > Installing NetWare Services -> Installing using the command line the
    command

       pkgadd -d cdrom nws

    should be as follows:

       pkgadd -d cdrom1 nws

    This assumes that there is only one CD-ROM on the machine.  If you have
    more than one CD-ROM drive, enter

       pkgadd -d cdromn nws

    In this case, n is the number of the CD-ROM drive in which you have
    inserted the CD-ROM.


 Mail and messaging

    The following notes apply to mail and messaging:

    +  biff(1) and comsat(1M) are not supported in UnixWare.

    +  xbiff(X1) is not fully supported in UnixWare.  It does not
       automatically determine the location of users' mailboxes configured in
       the message store.  By default it will monitor mailbox location
       /usr/spool/mail/username, where username is your login name.  If
       users' mailboxes are configured to be in a location other than the
       system spool directory (/usr/spool/mail, which is a symbolic link to
       /var/mail), then you must specify the filename location to xbiff by
       using its -file filename command line option.

       Also, xbiff does not use the ``flagup'' and ``flagdown'' bitmaps by
       default to show incoming mail status (as reported in the man page
       text), but rather uses the image of a two-tiered ``inbox'' which
       becomes filled with messages.

    +  The Netscape MUA does not recognize the inbox folder location
       specified for the message store configuration in /etc/default/mail.

    +  The message New mail has arrived is displayed after mailx(1) even when
       messages have been read or deleted.

    +  mailx(1) cannot make an IMAP connection to a remote host when the user
       is root, because IMAP will not allow root login for security reasons.
       If this is attempted, the message No new mail may be displayed when
       there is mail on the remote host.

    +  When mailx(1) is run as an IMAP client, the ``From '' line of a
       displayed message shows the date instead of the correct sender.

    +  Mail folders may not be configured as hard or symbolic links. The
       message store system will reject them for security reasons.

    +  For a non-networked system, the sendmail(1M) startup script
       /etc/mail/sendmailrc (which is linked to /etc/rc2.d/S81sendmail,
       /etc/rc1.d/K68sendmail, and /etc/rc0.d/K68sendmail) automatically
       creates the file /etc/service.switch with an entry which directs
       sendmail to only look up host names in /etc/hosts, effectively
       disabling DNS lookups.  The sendmailrc script overwrites any existing
       /etc/service.switch file. You must therefore edit /etc/mail/sendmailrc
       if you wish to include your own customizations for service.switch.

       See ``The service switch'' in the online documentation under Mail and
       Messaging -> Administering Mail and Messaging -> sendmail operations

    +  If you have added or removed a networking card from your hardware
       configuration using the Network Configuration Manager, you must stop
       and re-start sendmail(1M) in the case where the manager does not ask
       you to reboot the system.  You may do so by executing the following
       commands:

          /etc/mail/sendmailrc stop
          /etc/mail/sendmailrc start



 Desktop, SCOhelp and Netscape


    +  You cannot use the desktop File Manager to change the properties of
       files larger than 2GB.

    +  A rare race condition may occur on reboot that causes the following
        dtlogin error message to be displayed on the console:

          The X Server cannot be started on display machine_name:0

       The message incorrectly tells you to log in to the console and log out
       again to start dtlogin.  You must in fact log in to the console, use
       ps(1) to identify the dtlogin-daemon process, then send a kill -9
       signal to it.  You can now run scologin start command from the
       console.

    +  The <Del> key is not set up as the delete character for dtterm, which
       instead uses ^C as the delete character by default.  To use <Del> as
       the delete key, execute the following command in the dtterm window:

          stty intr ^?

       ``^?'' consists of the two characters ``^'' and ``?''.

    +  Using the Back button in the SCOhelp frame to return to the first page
       of search results causes an error. This is harmless, and may be
       ignored.  You may wish to redo the search.

    +  When you invoke SCOhelp from the SCO ARCserve/Open window, and click
       on any of the hotlinks displayed, a Javascript error similar to the
       following is displayed:

          Window.node has no property named 'location'

       This error may be ignored. Click OK in the error window to close it.

    +  If you resize the SCOhelp window, a JavaScript error message is
       displayed.  This is harmless. Click OK to close the error message
       window.

    +  You cannot assemble a topic in SCOhelp for printing until the search
       capability has been enabled.

    +  When Netscape and SCOhelp browsers are open at the same time, exiting
       from either closes both browsers. To exit from just one browser, use
       the File -> Close menu option.

    +  The Back and Forward buttons in each frame in the SCOhelp browser
       behave differently from the buttons with the same names in the browser
       tool bar and in the Netscape browser. The frame buttons work within
       frames, but only with the UnixWare online documentation set.
       Navigating to pages outside the documentation set causes the frame
       buttons to behave in unpredictable ways.

    +  A PostScript version of the Netscape Navigator Gold Authoring Guide is
       available

       on the web at:

          http://www.sco.com/documentation/postscript/navau/goldauth/


    +  The Directory buttons (and Directory menu options) have changed for
       the UnixWare version of Netscape.  To return to standard Netscape
       Directory behavior, move aside the following file:  /usr/X/lib/app-
       defaults/Netscape.cfg.

    +  In some circumstances, you may not be able to return to SCOhelp via
       the Netscape back buttons. If this happens, select File -> Open
       Location and enter the address localhost:457.

    +  SCOhelp may not be able to access the documentation set if the help
       browser was installed while a network was configured, and the network
       is disconnected.

    +  The Netscape Mail/News Preferences window is too big for an 800x600
       display. This means that the OK, Cancel and Defaults buttons are not
       visible.

       You can access these buttons using the <Tab> key. Move the cursor to
       the last item on the tab, then press <Tab> once more to move the
       cursor to just off the screen for OK. Press <Tab> once again for
       Cancel, and a third time for Defaults. The next <Tab> should bring the
       cursor back to the top of the tab.

    +  If you kill all the processes owned by the current desktop user while
       you are root in a console on the Panorama desktop, the desktop becomes
       unusable.

    +  During installation, the config_help(1M), config_man(1M), and
       config_views(1M) tools are run and the output captured to log files.
       After installation, you need to run the config_search(1M) tool (with
       the -f option) to complete SCOhelp configuration.

       These tools can return errors that might indicate a problem with the
       SCOhelp system;  more typically, they return warnings that do not
       affect the integrity of SCOhelp.

       The following paragraphs explain some of the messages you may see when
       running these tools.

                  config_search: lang: No search collection at
                  /usr/lib/scohelp/lang/_SearchIndex.
                  First run config_help or config_man

       This message (where lang: is a language specifier such as es, fr, de,
       ja), indicates that config_search was run with either no options or a
       -L option that pointed to a particular language, and no input to the
       search index was found for that language.  The result is that no
       search index processing is done for the indicated language, but
       otherwise SCOhelp is unaffected by this error.  However, if there is
       documentation for lang: present on the system, then run config_help
       and config_man, and run config_search again, this time with the -L
       lang:  option.

          mktitles: lang: 1: Warning: manpage claims to be in
                    section n: path

       This error indicates a problem in the source file at /usr/man/path.
       Specifically, the file named by path is in section n, but the text in
       the file says that the page is in another section.  The source file
       itself needs to be corrected or moved to the proper section under
       /usr/man.  This is typically a problem caused by the application
       package that installed the manual pages.

          mktitles: lang: path: No documentation found.

       The mktitles tool looks for documentation files in every directory it
       finds under /usr/lib/scohelp.  If prints a message like the above for
       every directory in which it expected to find documentation files but
       found none.  This usually occurs when a doc package has been removed,
       but the directories it used were not deleted during package removal.
       Directories are typically left behind in case users have added their
       own source files.

          config_views: lang: path parent view <view-name> does not exist

          config_views: lang: <view-name> view has non-existant
                        OverviewURL: path

          config_views: lang: path view refers to non-existant
                        URL: path

       These messages usually indicate a reference to a topic view (a left
       frame table of contents) that does not exist.  This is usually due to
       a reference in one package that depends on doc in another package that
       is not currently installed.  For example, if you install the BASEdoc
       package but not the ARCdoc package (for ARCserve documentation), then
       you will get messages like this since the top-level BASEdoc view
       Backup and Restore will not have any ARCserve documentation to which
       it can point.


 X server and graphical environment


    +  The option -crt to X(X1M) does direct the X server to a virtual
       terminal (/dev/vt10, for example).

    +  DISPLAY settings for applications for SCO OpenServer (including those
       on the Skunkware 96 disk) may not be valid for UnixWare 7.  An error
       similar to the following may result:

          Connection broken

       You may wish to try the following workaround:

          DISPLAY=localhost;export DISPLAY
          xhost +localhost


    +  When startx(X1M) is used to start a pmwm(X1) session, the X session
       continues to run in an xterm after the pmwm session is closed.

    +  If you have a two button mouse, then a middle button mouse click may
       be generated by holding down and releasing the left and right buttons
       of the mouse simultaneously.  However the middle button simulation can
       be unreliable with dtterm on the CDE desktop.

       If after installation you decide to use a three button mouse then
       change the value of MOUSEBUTTONS in /etc/default/mouse from 2 to 3 and
       reboot your system.


 man pages

    If you install any raw man pages, that is, man pages that are coded with
    the man troff macros, then you must have the BSDcompat package installed
    first.  That is because such pages require nroff, which is in BSDcompat.

    After installing the BSDcompat package, include /usr/ucb in the PATH
    variable if you want to run catman to process unformatted man pages from
    the root.


 Security


    +  In character mode, the Security Profile Manager fails with a hung
       remote session if you try to use the OpenHost option to access a host
       where you do not have permission to use rsh(1) (for example, where you
       have no .rhost entry).

    +  A Strong Encryption Supplement is included on the UnixWare 7 CD-ROM.
       This turns on the Netscape 128-bit encryption.

       Both weak encryption (40-bit) and strong encryption binaries for the
       Netscape products (FastTrack, NavGold) are packaged as part of
       UnixWare. By default, the 40-bit binaries are in place. Installing and
       licensing the Strong Encryption Supplement causes the 128-bit binaries
       to be moved into place. Any Netscape products subsequently loaded onto
       the system will also get the strong encryption binaries.

       The Strong Encryption Supplement is separate from the encryption
       included in the base UnixWare 7, in that it currently applies to the
       Netscape products only (and the Internet Security package on SCO
       OpenServer).

    +  Two problems have been reported that concern administering groups via
       the SCOadmin Account Manager.

       If a user account has a group configured in its ``multiple group''
       set, the SCOadmin Account Manager cannot remove that group.

       The Change Group Membership feature in the SCOadmin Account Manager
       does not remove groups in the ``Member of'' column from the
       /etc/groups file if all the groups are selected. A partial selection
       works correctly.

       It is recommended that the usermod(1M) command be used for these
       operations.


 Tcl

    The command select(1tcl) exits when a selected socket file descriptor
    closes, and then blocks the socket.


 Emergency recovery with an encapsulated or mirrored root disk

    There are three phases to performing an emergency recovery with an
    encapsulated or mirrored root disk:

    1.  ``Creating the Emergency Recovery diskettes and tapes''

    2.  ``Bringing the system back after emergency media is created''

    3.  ``Performing recovery when the primary and mirrored root disks fail''

    _________________________________________________________________________
       WARNING  If the following procedures are not adhered to exactly, it
       may result in your system entering an unrecoverable state.
    _________________________________________________________________________

    During the following process, use the vxprint(1M) command to obtain
    information about the encapsulated root disk and the disk to which it is
    mirrored.  In this example, an initial install was done with all
    additional filesystems created, and mirrored onto another disk.  Your
    installation may differ, so you may have a different number of partitions
    on the root disk.  This procedure is valid for recovering from a disaster
    where the primary and mirror disks both fail, and ODM was used only to
    encapsulate the root disk and mirror it.  Information on any other ODM
    disks should be saved so that they may later be restored.

 Creating the Emergency Recovery diskettes and tapes


    1.  Bring the machine down to init state 1 and log in as root

    2.  Run vxconfigd(1M) to start up the ODM configuration daemon

    3.  Use vxplex(1M) to disconnect the mirrored root plexes. Examples are
        given below:

           vxplex dis home-02
           vxplex dis home2-02
           vxplex dis rootvol-02
           vxplex dis standvol-02
           vxplex dis swapvol-02
           vxplex dis tmp-02
           vxplex dis var-02


    4.  Set up the kernel to ignore the ODM configuration:

        +  Make a backup copy of /etc/conf/pack.d/vol/space.c using the
           following command:

              cp /etc/conf/pack.d/vol/space.c /etc/conf/pack.d/vol/space.c.old

           then edit /etc/conf/pack.d/vol/space.c, and change the two lines:

              #define VOL_ROOTDEV_IS_VOLUME
              #define VOL_SWAPDEV_IS_VOLUME

           to:

              #undef VOL_ROOTDEV_IS_VOLUME
              #undef VOL_SWAPDEV_IS_VOLUME


        +  Make a backup copy of /etc/conf/init.d/kernel using the following
           command:

              cp /etc/conf/init.d/kernel /etc/conf/init.d_kernel.old

           then edit /etc/conf/init.d/kernel to move the ``swp1'' entry
           located just after the ``vol2'' entry to just below the ``vol1''
           entry, and change the line from:

              swp1::sysinit:/sbin/swap -a /dev/vx/dsk/swapvol > /dev/sysmsg 2>&1

           to:

              swp1::sysinit:/sbin/swap -a /dev/swap > /dev/sysmsg 2>&1


        +  Make a backup copy of /etc/conf/inittab using the following
           command:

              cp /etc/conf/inittab /etc/conf/inittab.old

           then edit /etc/conf/inittab in the same manner as you edited
           /etc/conf/init.d/kernel.

        +  Make a backup copy of /etc/vfstab using the following command:

              cp /etc/vfstab /etc/vfstab.old

           then edit /etc/vfstab, and make the following type of
           substitutions on the non-commented lines:

              Replace ``/dev/vx/[r]dsk/home'' with ``/dev/[r]dsk/c0b0t0d0s4''
              Replace ``/dev/vx/[r]dsk/var'' with ``/dev/[r]dsk/c0b0t0d0sb''
              Replace ``/dev/vx/[r]dsk/home2'' with ``/dev/[r]dsk/c0b0t0d0sc''
              Replace ``/dev/vx/[r]dsk/tmp'' with ``/dev/[r]dsk/c0b0t0d0sd''

           You should also comment out any other ODM-defined slices.

        +  Make a backup copy of /etc/swaptab using the following command:

              cp /etc/swaptab /etc/swaptab.old

           then edit /etc/swaptab, replacing ``/dev/vx/dsk/swapvol'' with
           ``/dev/swap''

        +  Run the following command:

              touch /etc/vx/reconfig.d/state.d/install-db


        +  Run the following command to obtain the major/minor numbers of the
           root slice:

              ls -l /dev/dsk/c0b0t0d0s1


        +  Replace the major/minor numbers for /.io/bootdisk/[r]root:

              rm /.io/bootdisk/*root
              mknod root b MAJOR MINOR
              mknod rroot c MAJOR MINOR

           where MAJOR and MINOR are the major and minor numbers displayed by
           the ls in the previous step.

    5.  Rebuild the kernel:

           /etc/conf/bin/idbuild -B


    6.  Reboot using the init 6 command. When you see the UnixWare logo
        appear, immediately press <Space> to enter the Bootstrap Command
        Processor. Enter the command initstate=1, followed by ``'boot'''.
        This will cause the machine to boot into single-user mode.

    7.  Run the emergency_disk(1M) and emergency_rec(1M) commands.

 Bringing the system back after emergency media is created


    1.  Undo the steps in step 4 of the previous procedure to restore the ODM
        configuration.  When you use mknod(1M) to create the
        /.io/bootdisk/*root nodes, use the major and minor numbers listed by
        the following command:

           ls -l /dev/vx/dsk/rootvol


    2.  Rebuild the kernel again:

           /etc/conf/bin/idbuild -B


    3.  Reboot using the init 6 command. When you see the UnixWare logo
        appear, immediately press <Space> to enter the Bootstrap Command
        Processor. Enter the command initstate=1, followed by ``'boot'''.
        This will cause the machine to boot into single-user mode.

    4.  When the system comes back up, log in as root, and run vxconfigd(1M)
        to start the ODM configuration daemon

    5.  Re-attach the plexes disconnected earlier, for the mirrored disk.

        For example:

           vxplex att home home-02
           vxplex att home2 home2-02
           vxplex att rootvol rootvol-02
           vxplex att standvol standvol-02
           vxplex att swapvol swapvol-02
           vxplex att tmp tmp-02
           vxplex att var var-02

        You should also remove the comments from other ODM-defined slices you
        previously commented out.

    6.  Reboot using init 6 and let the machine boot all the way into
        multiuser mode.

 Performing recovery when the primary and mirrored root disks fail


    1.  Boot from the Emergency Recovery diskettes.

        A message should be displayed indicating that the system is not sane.

        Continue to the Emergency Recovery menu and perform the Restore
        Disk(s) process.

    2.  After the recovery has completed, select the option to Reboot.  When
        you see the UnixWare logo appear, immediately press <Space> to enter
        the Bootstrap Command Processor. Enter the command initstate=1,
        followed by ``boot''.  This will cause the machine to boot into
        single-user mode.

    3.  Enter the following command:

           rm /etc/vx/reconfig.d/state.d/install-db


    4.  Run vxconfigd to remove all information about the mirrored disk:

           vxplex -o rm dis home-02
           vxplex -o rm dis home2-02
           vxplex -o rm dis rootvol-02
           vxplex -o rm dis standvol-02
           vxplex -o rm dis swapvol-02
           vxplex -o rm dis tmp-02
           vxplex -o rm dis var-02
           vxedit rm disk01


    5.  Run /etc/vx/bin/vxunroot.

    6.  Remove the VOLPUBLIC partition from BOTH the root disk and the
        mirrored disk, if they exist:

           prtvtoc -f /tmp/vtoc /dev/rdsk/c0b0t0d0s0

        Edit the /tmp/vtoc file and change the line that is similar to this:

           14  0xe 0x201   2048    2064384

        to:

           14  0x0 0x0     0   0

        Then rewrite the VTOC:

           edvtoc -f /tmp/vtoc /dev/rdsk/c0b0t0d0s0

        Reboot using the init 6 command.  When you see the UnixWare logo
        appear, immediately press <Space> to enter the Bootstrap Command
        Processor. Enter the command initstate=1, followed by ``boot''.  This
        will cause the machine to boot into single-user mode.  Ignore the
        vxconfigd errors.

    7.  Run vxinstall to re-install ODM and re-encapsulate root.  After the
        three reboots take place, you can re-mirror the root disk, add any
        other ODM disks, and restore the data to them.  The machine will be
        running in multiuser mode.



 XENIX

    XENIX compatibility has been removed.  Various  modules and commands have
    been removed from the system.  These include the DOS commands doscat,
    doscp, dosdir, dosls, dosmkdir, dosrmdir, and dosrm.  Equivalent
    functionality can be obtained from the ``mtools'' package found on the
    Skunkware CD. The following exec modules and commands i286x, x286emul,
    i286emul, and xout were removed.  These modules and commands provided
    compatibility for 286 and 386 XENIX binaries.  The XENIX filesystem and
    all supporting commands for it have been removed.  The module xnamfs has
    been removed which supports XENIX semaphores and shared data.

    The XENIX libraries libx, libxcurses, and libxtermlib have been removed.
    Support for the system call nap is now in libc.  The system calls
    creatsem, execseg, chsize, locking, nbwaitsem, opensem, proctl, sdenter,
    sdfree, sdgetv, sdleave, sdwaitv, sigsem, unexecseg, and waitsem that
    were in libx were not moved to another library.  The corresponding man
    pages for these system calls no longer exist.

    If you execute a XENIX binary you can expect exec to return ENOEXEC, and
    an error message similar to:

       file: cannot execute [Exec format error]

    depending on your shell.  You can identify whether a binary is a XENIX
    binary by using the file command.


 Domestic encryption

    Domestic encryption is broken when update701 is installed. If the
    crypt(1) version of libnsl or the ``crypt'' package are already
    installed, the following warning is given:

       Overriding the installed domestic libnsl

    You should update your system with a new version of the ``crypt''
    package, obtained by ordering the UnixWare DES encryption utilities.
    This package is for North American customers only.

    The ``crypt'' package contains a domestic libnsl that is UNIX95
    conformant.

    If you do not update the ``crypt'' package, the secure rpc functionality
    in libnsl is broken.


 Documentation

    The UnixWare 7 documentation states that multiple instances of an
    application may be installed, and that on installing a second (or nth)
    package instance, the instance component of the package identifier is
    automatically incremented. It goes on to state that, subsequently, using
    this identifier, each instance can be removed from the system
    independently of any other instances.  This is incorrect. To increment
    package instances, you begin by installing the package (using the
    pkgadd(1M) utility), called for example ``package''. Then, you create a
    second image of the package called ``package.1'', and install that
    version. This provides a variant of the package instance handling
    functionality described in the UnixWare 7 documentation, because the
    identifiers are different.

    However, it is not then possible to remove one instance without also
    removing all of the others, as pkgrm(1M) does not correctly use the
    VERSION parameter (in the package characteristics file) to distinguish
    one instance from another.

    Accordingly, the following modifications should be made to the online
    documentation topic Software Development -> Software Development Tools -
    > Packaging your Software Applications :

    +  In the section entitled ``Installation Parameters'', the description
       of PKGINST should be removed.

    +  ``Step 2. Defining a Package Instance'' in the section entitled
       ``Basic Steps of Packaging'' should also be removed.

    +  The pointer to this documentation given in the second item of the list
       in ``Basic Steps of Packaging'' should also be removed.

    The following manual pages should also be modified. In all cases,
    references to the inst component of the pkginst command line argument
    should be ignored.

    +  installf(1M)

    +  pkgadd(1M)

    +  pkgask(1M)

    +  pkgchk(1M)

    +  pkginfo(1)

    +  pkgmk(1)

    +  pkgparam(1)

    +  pkgrm(1M)

    +  pkgtrans(1)

    +  removef(1M)

    Similarly, the following manual pages should be amended as described:

    +  admin(4)

       References to the instance parameter should be ignored.
    +  depend(4)

       References to the (arch)version field should be ignored.

    +  pkginfo(4)

       References to the MAXINST parameter should be ignored.






 Chapter 6
 Netscape products features and limitations

    This chapter contains information about the UnixWare 7 Netscape Server
    and other Netscape products under the following headings:

    +  Netscape server configuration

    +  Netscape FastTrack Server notes

    +  Encryption Supplement

    +  Generic Netscape Server information


 Netscape server configuration

    This section contains information about configuring the Netscape server
    under the following headings:

    +  ``Configuring the Netscape Administration Server for remote access''

    +  ``Deferring or reconfiguring network configuration''

 Configuring the Netscape Administration Server for remote access

    To configure the Netscape Administration Server to allow remote access:

    1.  Open this URL:

           http://localhost:620


    2.  Select Configure Administration, then select the ``Access Control''
        link.

    3.  In the ``IP addresses to allow'' field, enter a list of all the IP
        addresses which are allowed access to the Administration Server,
        using the format

           (IP1|IP2|...)

        including the IP address of the system's primary network interface,
        the IP address associated with the system's name (if different to
        that of the primary network interface), and any other IP addresses by
        which the system might be referenced.

    4.  Restart the Administration Server to implement these access
        configuration changes:

           /etc/nsadmin restart


 Deferring or reconfiguring network configuration

    During installation, the Netscape servers are configured with default
    settings for the ``ServerName'', ``Hosts'', and ``Addresses'' fields.  If
    you reconfigure TCP/IP, your Netscape FastTrack Server might no longer be
    properly configured.  To configure a Netscape FastTrack Server after
    deferring or reconfiguring networking configuration, edit the appropriate
    configuration files.

    In /usr/ns-home/admserv/ns-admin.conf, set ``ServerName'' to the string
    returned by hostname.  Set ``Hosts'' and ``Addresses'' to the hostnames
    and IP addresses allowed to administer this server.  After setting these
    variables, use the Netscape Administration Server to further configure
    the server.

    In the /usr/ns-home/httpd-ServerName/config/magnus.conf file, set
    ``ServerName'' to the string returned by hostname.  When you next enter
    the Administration server, you will get a message indicating that the
    configuration has been manually edited.


 Netscape FastTrack Server notes

    This section contains information about setting up and using your
    Netscape FastTrack Server(TM).

 IP address configuration

    If networking configuration is deferred or incorrect, the Netscape
    Administration Server may be inaccessible. In this case, after
    configuring networking correctly, edit the /usr/ns-home/admserv/ns-
    admin.conf file.  Change the line beginning with ``Addresses'' to contain
    the correct IP address and restart the Administration Server.

 Default configuration

    The Netscape FastTrack Server installs with the following pre-configured
    defaults.

    _________________________________________________________________________
       NOTE  You can change these values after completing the
       installation.
    _________________________________________________________________________


    +  public server uses port 80

    +  server IP address is the first non-loopback address returned by
       netstat -in, or 127.0.0.1 if TCP/IP is not configured

    +  CGI directory /usr/ns-home/cgi-bin and .cgi filetype disabled

    +  user document directory $HOME/public_html enabled

    +  server-parsed HTML for .shtml filetype enabled

    +  runs as nobody

    +  administered on port:620

    +  server home  /usr/ns-home/httpd-80

    +  document root  /usr/ns-home/docs

    +  default system home page provided at /usr/ns-home/docs/index.shtml,
       with a number of useful links pre-configured

    +  server processes:

       -  Processes 1

       -  Minimum threads 4

       -  Maximum threads 32

    +  index files index.html or home.html

    +  never attempts to resolve IP addresses into host names

    +  all accesses logged

    +  administration access is limited to the local host

 CGI scripts

    The following CGI programs have been included in this release:

    randstyle
         select a random digit style from the directory of digits

    userinfo
         script to produce an HTML document containing information about any
         links to personal accounts on the machine on which the web server is
         running.

    Count.cgi
         an excellent counter contributed by Muhammad A. Muquit and included
         with his permission. For further information, see :

            http://www.fccc.edu/users/muquit/Count.html


 Administration scripts

    The Bourne shell scripts /etc/nsfast  and /etc/nsadmin are included in
    this release. These scripts can only be run by root and are used to start
    and stop the server, enable and disable automatic startup, and query the
    Administration server, and the port 80 and and other FastTrack server
    instances.

    To enable or disable automatic startup of the port 80 public HTTP server,
    issue these commands as root:

       /usr/sbin/nsfast enable [80]
       /usr/sbin/nsfast disable [80]

    To enable or disable automatic startup of the Netscape Administration
    server, issue the commands:

       /usr/sbin/nsadmin enable
       /usr/sbin/nsadmin disable

    To start, stop or query the port 80 or other public servers, run:

       /usr/sbin/nsfast stop [80]
       /usr/sbin/nsfast start [80]
       /usr/sbin/nsfast query [80]

    To start, stop or query the Administration Server, run:

       /usr/sbin/nsadmin stop
       /usr/sbin/nsadmin start
       /usr/sbin/nsadmin query

    See nsadmin(1M) and nsfast(1M) for full details.

 HTML snippets

    ``Snippets'' allow you to display system-specific configuration
    information collected automatically by the /etc/rc2.d/S90sysinfo2html
    script, which is run during system initialization.  This script gathers
    information about the system and formats it as HTML for later inclusion
    by an HTML document.

    To include this information in an HTML document, use the #include
    directive; for example:

       <!--#include file="include/filename.inc" -->

    The following HTML snippets reside in the /usr/ns-home/docs/include
    directory:

    boottime.inc
         contains the time of the last system boot

    hostname.inc
         contains the fully qualified domain name of the system (as returned
         by the hostname command)

    nodename.inc
         contains the node name of the system (as returned by the uname -n
         command)

    prtconf.inc
         contains system information as returned by the prtconf command

    scohelp.inc
         contains the hypertext reference for SCOhelp

    ttalogin.inc
         contains the URL to use for the Login button; it can be telnet, SCO
         Tarantella authentication, or a custom authentication mechanism. For
         more information about SCO Tarantella, see the SCO web site:

            http://www.tarantella.sco.com


 User publishing

    User document directories in $HOME/public_html are enabled, provided a
    $HOME/.html file is present. In addition, if a $HOME/public_html file is
    present, a personal web page is offered, with a URL as given there. If a
    $HOME/.ftp file is present, personal ftp is offered, with a URL as given
    there.  If a $HOME/.plan file is present, a link to the user's plan is
    offered, using the UNIX finger utility.

    To disable this feature, use the Netscape Administration Server.  In
    addition, the default port 80 server home page includes a link to a user
    information page generated automatically by a CGI script.  This script
    will publish information about users whose home directories contain any
    of these files:

    .html   indicates the user wishes their $HOME/public_html document
            directory published through this user information page and
            accessible at:

               http://ServerName/~UserName/


    .ftp    causes a link to the user's personal ftp directory to be
            published and accessible at:

               ftp://ServerName/pub/users/UserName/


    .plan   causes a link to the user's personal plan to be published using
            the UNIX finger utility

 Turning on DNS breaks Netscape server Java execution

    Netscape Java execution in the Netscape web server, enabled on the
    Programs -> Java frame, works without problems when DNS is not enabled on
    the System Settings -> Performance Tuning frame. The typical test is to
    enable Java execution on the web server, then test it by running one of
    the sample Java applets contained in the
    <ServerRoot>/plugins/java/applets/ directory.

    However, when DNS is enabled so that IP addresses are resolved to their
    full names in the log files and in the ACL directives, Java in the
    Netscape server fails. Attempting to access one of the applets results in
    the following page returned by the browser:

       Server Error

       This server has encountered an internal error which prevents it from
       fulfilling your request. The most likely cause is a misconfiguration.
       Please ask the administrator to look for messages in the server's error
       log.

    The error log contains the following entry:

       [22/Oct/1997:15:55:28] failure: for host h-205-217-236-19.netscape.com
       trying to GET /server-java/BrowserDataApplet, java-run reports:
       construction of new ServerApplet failed

    Turning off DNS in Netscape resolves the problem again and lets the
    applets run normally.


 Encryption Supplement

    This section contains information about the Encryption Supplement.

 System requirements


    SCO Strong Encryption Supplement 1.0

            Software:    UnixWare 7

            Disk space:  1MB free disk space


    Enabling SCO Strong Encryption Supplement
            Customers in the United States and Canada are allowed to use
            strong encryption with the Netscape products.  All the Netscape
            client and server products use 40-bit encryption by default when
            using the Secure Socket Layer (SSL) protocol to communicate
            secured information.  Strong encryption allows the use of 128-bit
            encryption between clients and servers.

            The SCO Strong Encryption Supplement (encrypt) must be installed
            to enable strong encryption for all Netscape products on this
            CD-ROM.  The installation of this product prompts for a license.
            You can purchase a license for the SCO Strong Encryption
            Supplement by calling 1-800-SCO-UNIX or your SCO Reseller.

            _________________________________________________________________
               NOTE  The license can be used on all systems at your site.
            _________________________________________________________________

            See encrypt_config(1M) for more information.


 Generic Netscape Server information


    Getting support for Netscape products
            Support for the Netscape products is provided by SCO.  Ignore any
            links or references that point to Netscape for support
            information.

    Starting the Netscape Server Admin manager
            To start the Netscape Server Admin manager, on the CDE desktop,
            select SCO Admin from the SCO menu (above the SCO logo), then
            click on Netscape Server Admin.

            If a Netscape browser is already running, a new window from the
            existing browser opens with the Netscape Server Admin URL.

            To run the Netscape Server Admin manager from an existing
            Netscape browser, open the following URL:

               http://ServerName:620


    Netscape Server Admin user ID and password
            When you start the Netscape Server Admin manager, you are
            prompted for the user ID and password.  At installation, the
            Netscape Server Admin user ID is set to admin and the admin
            password is set to the same as the root password.

    TCP/IP reconfiguration
            If you reconfigure TCP/IP, any Netscape servers installed on your
            system might be improperly configured.  To correct this, you must
            edit configuration files as described in ``Deferring or
            reconfiguring network configuration''.

    Changing the hostname
            To change the hostname of your UnixWare 7 system, follow the
            instructions in setuname(1M).

            Before rebooting, edit these Netscape server files to replace all
            occurrences of the old name with the new name:

               /usr/ns-home/admserv/ns-admin.conf
               /usr/ns-home/http[d | s]-<ServerName>/config/magnus.conf
               /usr/ns-home/httpdServerName/config/magnus.conf
               /usr/ns-home/httpsServerName/config/magnus.conf


    Warnings in Netscape Server log
            When the FastTrack server is run with Tarantella, it may hang and
            produce a number of warnings about failed calls to accept in the
            log.  These are harmless, and may be ignored. You should restart
            the server as usual.

 Accessing Netscape documentation

    To access online documentation, use SCOhelp (or your existing Netscape
    browser).  To use SCOhelp:

    +  Enter scohelp& at the command line in an xterm window on your desktop.

    +  On the CDE desktop, select the Help menu (above the help icon in the
       Control Panel), then select SCO Help.

    +  On the Panorama desktop, pull down the Root menu and select Help.

    To use your existing Netscape browser, open:

       http://localhost:457

    Select Internet and Intranet, then Netscape.

    Online documentation is also available at the SCO Internet Family
    Documentation page, http://www2.sco.com:1996/inethome.html.

    To access printable PostScript(r) images of books for the software on the
    UnixWare 7 Optional Services CD-ROM:

    1.  Download and install the gzip utility.

    2.  Download the files from the SCO web page:

           http://www.sco.com/documentation/postscript/


        Sub-directories for each product and book title contain the gzipped
        PostScript files.

    3.  Change to the download directory.  For example,

           cd /tmp


    4.  Uncompress and print the files:

           /usr/bin/gunzip * | lp -opost -dprintername *

        Substitute the name of a PostScript printer for printername and, if
        necessary, change the -opost option depending on your printer model
        script.

    To order printed Netscape documentation:

    1.  Visit the Netscape home page at http://home.netscape.com.

    2.  Click on Netscape Store, then Bookstore & Courses.

 Downloading gzip

    The PostScript books on the WWW are distributed in gzip (.gz) compressed
    format.  You must use gunzip to uncompress these files.  To download and
    install the gunzip utility:

    1.  Point your browser at:

           http://www.sco.com/documentation/postscript/bin/gunzip_uw7.tar

        Download gunzip_uw7.tar to a temporary directory.

    2.  Enter:

           tar xvf gunzip_uw7.tar

        This extracts the gunzip binary into the /usr/bin directory.

    To download the entire gzip package from Skunkware:

    1.  Point your browser at:

           http://www.sco.com/skunkware/uw7/shellutil/gzip/


    2.  Download gzip.pkg to a temporary directory, such as /tmp.

    3.  Use pkgadd(1M) to install the package:

           pkgadd -d /tmp/gzip.pkg






 Appendix A
 System profiles, services, and packages

    System profiles are collections of software that simplify the
    installation process. When you select a system profile, you ensure that
    the correct software (services and packages) is installed to enable the
    type of server you want.

    _________________________________________________________________________
       NOTE  The Basic Networking Utilities (BNU) documentation includes a
       small number of references to the ``bnu'' package, as if this were
       a separately-installable feature. This is not the case: the BNU
       commands, utilities, configuration files and so on, are an integral
       part of the UnixWare 7 base system. Accordingly, instructions that
       require the user to test for the presence of the ``bnu'' package,
       for example with pkginfo(1), should be disregarded.
    _________________________________________________________________________

    These system profiles are available:

    +  ``License based defaults''

    +  ``Small Footprint server''

    +  ``Full (All Packages) profile''

    +  ``Customize Installation of Packages''


 License based defaults

    The license based defaults system profile presents you with a default
    list of the packages available for the license that you have selected
    during installation.  The following licensing based defaults are
    available:

    _________________________________________________________________________
    License               Description
    _________________________________________________________________________
    Base                  Base Edition
    Business              Business Edition
    Departmental          Departmental Edition
    Development           Development System
    Enterprise            Enterprise Edition
    Free                  Free UnixWare 7
    Intranet              Intranet Edition
    Messaging             Messaging Edition



 Small Footprint server

    The Small Footprint server consists of the base operating system and
    networking utilities; it does not contain graphics support or
    documentation. It is intended for use in replicated sites, or on systems
    with small memory (less than 32MB) or limited disk capacity (less than
    500MB).

 Full (All Packages) profile

    The Full (All Packages) profile is designed to select a wide spectrum of
    technologies from the entire list of packages in the UnixWare 7
    distribution. Only packages that have hardware-sensitive application
    (osmp and mpio), language-specific context (language extensions), or
    debugging functionality (kdb) are left unselected in this profile.

    _________________________________________________________________________
       NOTE  Selecting this profile does not grant additional unlimited
       software licenses. If you install packages not covered by the
       license that you entered earlier in the installation, a 60-day
       evaluation license may be granted so that you may evaluate our
       software. It is up to you to obtain the necessary license to cover
       the software you wish to install on your system.

       See the cover letter in your product distribution for information
       on how to obtain further licenses.
    _________________________________________________________________________



 Customize Installation of Packages

    The Customize Installation of Packages option allows you to select and
    deselect individual packages for installation. By default, the list of
    packages is selected by the license you entered earlier in the
    installation. You can also select the Small Footprint server or Full (All
    Packages) profile then select this profile to change the list of packages
    selected for installation. You can reset to license-based defaults by
    reselecting the License-Based defaults profile.

    You can further customize the list of selected packages by choosing this
    option and toggling on or off individual packages.


 Package organization

    The installation process organizes software into groups called sets,
    services, and packages. Sets are groupings of one or more packages.
    Services are logical groupings of packages within a set. Packages are
    groupings of files and binaries that make up a particular technology.


 Installation sets

    The software available in the UnixWare 7 distribution is divided into the
    following sets:

    _________________________________________________________________________
    Set                   Description
    _________________________________________________________________________
    UnixWare              Core System Services
    BaseWeb               Internet Services
    arcserve              Data Management Services
    doc                   Documentation Services
    loc_doc               Localized Documentation Services
    winsrvcs              Windows Integration Services


 Core System Services set

    The UnixWare set contains provides the core system services.  The
    following services are defined here:

    +  ``Extended OS utilities (utilities)''

    +  ``SCO NetWare (netware)''

    +  ``Networking services (network)''

    +  ``Graphics services (graphics)''

    +  ``Database services (database)''

    +  ``Desktop services (desktop)''

    +  ``Language supplements (language)''

    The Core System Set includes the required packages. These packages are
    necessary to the operation of other packages and cannot be deselected via
    the installation process. The required packages are:

    _________________________________________________________________________
    Package               Description
    _________________________________________________________________________
    acp                   Enhanced Application Compatibility
    base                  Base System
    expect                expect
    ls                    Language Supplement
    nsu                   Network Support Utilities
    scoadmin              SCO System Administration (SCOadmin)
    tclrun                Tcl Runtime package
    terminf               Terminfo Utilities
    vtclrun               Vtcl Runtime package


    Extended OS utilities (utilities)

    This service includes application compatibility commands and libraries,
    auditing, compilers, advanced commands, the kernel debugger, system
    administration utilities, multiprocessor support, and printer support.

    The following packages are included:

    _________________________________________________________________________
    Package       Description                            Selected from
    _________________________________________________________________________
    acl           Access Control List Utilities          All Licenses
                                                         Full Profile
    audio         Audio Subsystem                        All Licenses
                                                         Full Profile
    audit         Auditing Subsystem                     All Licenses
                                                         Full Profile
    bsdcompat     BSD Compatibility                      All Licenses
                                                         Full Profile
    cmds          Advanced Commands                      All Licenses
                                                         Full Profile
    kdb           Kernel Debugger                        not selected
    lp            Printer Support                        All Licenses
                                                         Full Profile
    mpio          Multipath I/O Driver                   not selected
    osmp          OS Multiprocessor Support (OSMP)       not selected
    perl5         Perl 5.004                             All Licenses
                                                         Full Profile
    uccs          UDK Optimizing C Compilation System    All Licenses
                                                         Full Profile
    uedebug       UDK Enhanced Debugger                  All Licenses
                                                         Full Profile


    SCO NetWare (netware)

    This service includes the NetWare UNIX client and integration kit.

    The following packages are included:

    _________________________________________________________________________
    Package        Description                           Selected from
    _________________________________________________________________________
    nuc            NetWare UNIX Client                   All Licenses
                                                         Full Profile
    nwnet          NetWare Networking                    All Licenses
                                                         Full Profile


    Networking services (network)

    This service includes TCP/IP and related Internet technologies.

    The following packages are included:

    _________________________________________________________________________
    Package       Description                            Selected from
    _________________________________________________________________________
    dfs           Distributed File Systems utilities     All Licenses
                                                         Full Profile
    inet          Internet utilities                     All Licenses
                                                         Full Profile
    ldap          Lightweight Directory Access           All Licenses
                  Protocol utilities                     Full Profile
    netbios       TPI NetBIOS                            All Licenses
                                                         Full Profile
    netmgt        Network management utilities           All Licenses
                                                         Full Profile
    nfs           Network File System utilities          All Licenses
                                                         Full Profile
    nics          Network Drivers                        All Licenses
                                                         Full Profile
    nis           Network Information Services           All Licenses
                                                         Full Profile
    ppp           Point-to-Point Protocol utilities      All Licenses
                                                         Full Profile
    rpc           Remote Procedure Call utilities        All Licenses
                                                         Full Profile
    server        server utilities                       All Licenses
                                                         Full Profile


    Graphics services (graphics)

    This service includes the X11R6.1 Server, OSF/Motif, SCO Visual Tcl(TM),
    and video drivers.

    The following packages are included:

    _________________________________________________________________________
    Package        Description                           Selected from
    _________________________________________________________________________
    TEDlogin       CDE Login Manager                     All Licenses
                                                         Full Profile
    basex          X11R6 Base X Runtime System           All Licenses
                                                         Full Profile
    mtfrun         OSF Motif Runtime Environment         All Licenses
                                                         Full Profile
    xclients       X11R6 X Clients                       All Licenses
                                                         Full Profile
    xcontrib       X11R6 Contributed X Clients           All Licenses
                                                         Full Profile
    xdrivers       X11R6 Graphics Drivers                All Licenses
                                                         Full Profile
    xfonts         X11R6 Fonts                           All Licenses
                                                         Full Profile
    xserver        X11R6 X Server                        All Licenses
                                                         Full Profile


    Database services (database)

    This service contains online Virtual Disk Volume administration and
    management.

    The following packages are included:

    _________________________________________________________________________
    Package        Description                           Selected from
    _________________________________________________________________________
    vxva           VERITAS ODM Visual Administrator      Enterprise Edition
                                                         Full Profile
    vxvm           VERITAS Volume Manager                Enterprise Edition
                                                         Full Profile


    Desktop services (desktop)

    This service includes the CDE lightweight and full desktops, as well as
    the graphical login and CDE help system.

    The following packages are included:

    _________________________________________________________________________
    Package       Description                            Selected from
    _________________________________________________________________________
    TEDdesk       TriTeal Enterprise Desktop (CDE        All Licenses
                  Desktop)                               Full Profile
    TEDdocs       CDE Desktop PostScript Manuals         All Licenses
                                                         Full Profile
    TEDhde        CDE German help                        locale selected
    TEDhelp       CDE Online Help                        All Licenses
                                                         Full Profile
    TEDhfr        CDE French help                        locale selected
    TEDhjpe       CDE Japanese EUC help                  locale selected
    TEDlde        CDE German catalogs and miscellany     locale selected
    TEDles        CDE Spanish catalogs and miscellany    locale selected
    TEDlfr        CDE French catalogs and miscellany     locale selected
    TEDljpe       CDE Japanese EUC catalogs and          locale selected
                  miscellany
    TEDman        CDE Manual Pages                       All Licenses
                                                         Full Profile


    Language supplements (language)

    This service includes support for language extensions.

    The following packages are included:

    _________________________________________________________________________
    Package        Description                           Selected from
    _________________________________________________________________________
    dele           German language extension             locale selected
    esle           Spanish language extension            locale selected
    frle           French language extension             locale selected
    jale           Japanese language extension           locale selected

    One of the above packages is selected automatically, according to the
    locale that you choose during the installation. If you require other
    language supplements, you must use the Customize Installation of Packages
    option and switch them on.

 Internet Services set

    The Internet Services set (BaseWeb) provides web browsers and servers.
    It contains the Internet service (internet).

    The following packages are included:

    _________________________________________________________________________
    Package       Description                            Selected from
    _________________________________________________________________________
    FTRKdoc       Netscape FastTrack Server              All Licenses
                  Documentation                          Full Profile
    NAVIdoc       Netscape Navigator Documentation       All Licenses
                                                         Full Profile
    jdk113        JDK 1.1.3 for SCO                      All Licenses
                                                         Full Profile
    nsadmin       Netscape Administration Server 2.13    All Licenses
                                                         Full Profile
    nsfast        Netscape FastTrack Server 2.01a        All Licenses
                                                         Full Profile
    nsnavAu       Netscape Navigator Gold 3.04           All Licenses
                                                         Full Profile


 Data Management Services set

    The Data Management Services set (arcserve) provides SCO ARCserve/Open
    backup and restore. It contains the Data Management service (datamgt).

    The following packages are included:

    _________________________________________________________________________
    Package       Description                            Selected from
    _________________________________________________________________________
    ARCdoc        SCO(r) ARCserve(r) documentation       All Licenses
                                                         Full Profile
    ARCserve      SCO ARCserve commands and utilities    All Licenses
                                                         Full Profile


 Documentation Services set

    The Documentation Services set (doc) provides the documentation services
    and manual pages for use with the SCOhelp browser. It contains the
    Documentation service (documentation).

    The following packages are included:

    _________________________________________________________________________
    Package        Description                           Selected from
    _________________________________________________________________________
    BASEdoc        UnixWare Documentation                All Licenses
                                                         Full Profile
    BASEman        UnixWare Manual Pages                 All Licenses
                                                         Full Profile
    scohelp        SCOhelp online help system            All Licenses
                                                         Full Profile


 Localized Documentation Services set

    The Localized Documentation Services set (loc_doc) provides documentation
    and manual pages for use with the SCOhelp browser.

    The following packages are included:

    _________________________________________________________________________
    Package       Description                            Selected from
    _________________________________________________________________________
    frBASEdoc     UnixWare Documentation in French       All Licenses
                                                         Full Profile
    deBASEdoc     UnixWare Documentation in German       All Licenses
                                                         Full Profile
    esBASEdoc     UnixWare Documentation in Spanish      All Licenses
                                                         Full Profile
    jaBASEdoc     UnixWare Documentation in Japanese     All Licenses
                                                         Full Profile
    jaBASEman     UnixWare Manual Pages in Japanese      All Licenses
                                                         Full Profile


 Windows Integration Services set

    The Windows Integration Services set (winsrvcs) provides the file and
    print services and terminal emulation support for Windows. It contains
    the Windows Integration Service (windowsconn).

    The following packages are included:


    _________________________________________________________________________
    Package        Description                           Selected from
    _________________________________________________________________________
    visionfs       SCO VisionFS(TM)                      Not in Development
                                                         Edition
                                                         Full Profile
    termlite       SCO TermLite(TM)                      Not in Development
                                                         Edition
                                                         Full Profile






 Appendix B
 New features and enhancements

    This appendix provides information about new features and Program
    Temporary Fixes (PTFs) which have been incorporated into the UnixWare
    7.0.1 release.  All new features and enhancements are contained in the
    update701 package unless specifically noted, and are installed
    automatically during initial system load or when the update701 package is
    layered onto an existing UnixWare 7 system.


 New features

    UnixWare 7.0.1 includes the following new features:

    Unix95 conformance
            This release of UnixWare 7 fully conforms to the X/Open UNIX
            brand (Single UNIX specification).  By default UnixWare 7 is not
            strictly UNIX95 compliant, but you can fully enable strict
            compliancy by using the suscfg(1M) command which is located in
            /u95/bin.

    Core OS Performance Pack
            Includes performance improvements and bug fixes required to
            support the TPC/C benchmarking efforts.

    MMX support
            Permits applications which use MMX technology to execute.  This
            feature does not add support for building applications which use
            MMX.

    Merge performance
            Provides new kernel interfaces to Merge to accelerate context
            switching of Merge tasks.

    LFS tar/cpio
            Enables backups of files larger than 2GB and smaller than 1TB
            using tar, cpio or pax.

    PCI Hot-Plug
            Adds the capability to physically add, remove or replace a
            controller on a ``hot'' (running) system.

    HDK     Provides documentation for DDI and SDI.

    POSIX threads support
            Adds new POSIX threads (pthreads) interfaces based on P1003.1 -
            1996, and thread extensions from the Eastwood standard.

    NSC header file changes
            Provides changes to header files for NSC (NonStop Clusters); to
            provide user binary compatibility.

    Veritas File System Changes
            Allows VjFS/VxFS (statvfs), mount_vxfs and fsck_vxfs to provide
            support for UnixWare NonStop Clusters.

    2 Network card failover GUI support
            Enables a NIC to be configured as a failover device and be
            associated with a primary interface. The GUI also supports manual
            failover from the primary to failover device and a failback
            mechanism from the failover device to the primary NIC.

    Simplified Chinese locale
            A simplified Chinese locale (zh_CN.eucCN) is now provided. The
            user must provide their own fonts to make use of this locale. The
            font name must match the entry in /sbin/loadfont. See pcfont(1)
            for more details.

    Plug and Play Manager
            The new SCOadmin ISA PnP Configuration Manager allows you to
            detect and configure ISA Plug and Play devices, including sound
            cards, network cards, and other devices.

    Installation enhancements
            The Initial System Load of UnixWare now allows you to install
            software from multiple CD-ROMs in a single session.  See the
            Installation Guide for details.

    Enhanced hardware support
            UnixWare now supports additional popular audio, graphics, and
            networks adapters as described in Chapter  3, ``Updating your
            system''.  If you layer update701 on top of an existing UnixWare
            7 system, you must use pkgadd(1) to add the updated audio, nics,
            and xdrivers packages from the UnixWare 7.0.1 Operating System
            Updates CD-ROM.

    Updated documentation set
            The documentation set contains information on all new features
            and fuller coverage of other areas, particularly network and
            system administration.Updated localized documentation sets are
            also available. These packages are found on the UnixWare 7.0.1
            Operating System Updates CD-ROM.

    mailx now supports Japanese environment
            The mailx(1) command now supports Japanese.


 Enhancements in UnixWare 7.0.1

    UnixWare 7.0.1 includes fixes and enhancements previously released as the
    Release Supplement, localized UnixWare 7, and Program Temporary Fixes
    PTFs.

    The PTFs included in update701 are:

    ptf7002
         MPIO update supplement

    ptf7002b
         ICL fixes for MPIO/Clariion supplement

    ptf7003
         UnixWare supplement for Oracle 7

    ptf7004
         UnixWare language extension supplement

    ptf7005
         Filesystem update supplement

    ptf7010
         Accept protocol error supplement

    ptf7012
         UnixWare SNMP supplement

    ptf7011
         DLPI update supplement

    ptf7013
         UnixWare libsocket supplement

    ptf7014
         DDI8 CD-ROM supplement

    ptf7016
         UnixWare mem driver supplement

    ptf7017
         proc driver improvement supplement

    ptf7018
         UnixWare memsize supplement

    ptf7020
         UnixWare sysdump supplement

    ptf7021
         NFS update supplement

    ptf7022
         UnixWare support for Compaq Prosigna 800 and Compaq Wellness Driver

    ptf7024
         BIND 4.9.7 for UnixWare

    ptf7026
         UnixWare support supplement for Oracle 8

    ptf7027
         UnixWare seg_dev driver supplement

    ptf7028
         UnixWare postwait driver supplement
    ptf7102
         scohelp/netscape supplement





 Appendix C
 Supported locales and keyboards

    The current release supports the following locales:

    _________________________________________________________________________
    Locale                Description
    _________________________________________________________________________
    C                     C
    POSIX                 POSIX
    zh_CN                 Chinese for China
    hr_HR                 Croatian
    cs_CZ                 Czech
    da_DK                 Danish
    nl_BE                 Dutch/Flemish for Belgium
    nl_NL                 Dutch/Flemish for Netherlands
    en_AU                 English for Australia
    en_CA                 English for Canada
    en_GB                 English for Great Britain
    en_HK                 English for Hong Kong
    en_IN                 English for India
    en_IR                 English for Ireland
    en_SG                 English for Singapore
    en_US                 English for USA
    fr_BE                 French for Belgium
    fr_CA                 French for Canada
    fr_FR                 French for France
    fr_CH                 French for Switzerland
    fi_FI                 Finnish
    de_AT                 German for Austria
    de_DE                 German for Germany
    de_CH                 German for Switzerland
    el_GR                 Greek
    hu_HU                 Hungarian
    is_IS                 Icelandic
    it_IT                 Italian for Italy
    it_CH                 Italian for Switzerland
    ja_JP                 Japanese
    no_NO                 Norwegian
    pl_PL                 Polish
    pt_BR                 Portuguese for Brazil
    pt_PT                 Portuguese for Portugal
    ro_RO                 Romanian
    ru_RU                 Russian
    sk_SK                 Slovak
    sl_SI                 Slovenian
    es_AR                 Spanish for Argentina
    es_CL                 Spanish for Chile
    es_MX                 Spanish for Mexico
    es_ES                 Spanish for Spain
    es_VE                 Spanish for Venezuela
    sv_FI                 Swedish for Finland
    sv_SE                 Swedish for Sweden
    tr_TR                 Turkish
    uk_UA                 Ukrainian

    The following keyboards are supported:

    +  American

    +  American International

    +  Belgian

    +  British

    +  Canadian International

    +  Canadian French

    +  Czech

    +  Danish

    +  Dutch

    +  French

    +  German

    +  Greek

    +  Hungarian

    +  Icelandic

    +  Irish

    +  Italian

    +  Japanese A01

    +  Japanese AX

    +  Latin American

    +  Norwegian

    +  Polish

    +  Portuguese

    +  Romanian

    +  Russian

    +  Slovak

    +  Spanish

    +  Swiss German

    +  Swiss French

    +  Turkish F-Type

    +  Turkish Q-Type