![[Return to Library]](BOOKSHELF.GIF){kind=small}
![[Contents]](TOC.GIF){kind=small}
![[Previous Chapter]](http://www.tru64unix.compaq.com/docs/base_doc/DOCUMENTATION/HTML/AA-QTLMB-TE_html/REW.GIF)
![[Next Section]](http://www.tru64unix.compaq.com/docs/base_doc/DOCUMENTATION/HTML/AA-QTLMB-TE_html/NEXT.GIF)
![[Next Chapter]](FF.GIF){kind=small}
![[Index]](INDEX.GIF){kind=small}
![[Help]](HELP.GIF){kind=small}
The notes in this chapter discuss the following topics:
Do not attempt to install Digital UNIX Version 4.0B without first reading in Chapter 2 the notes appropriate to your processor. Failure to read these notes can result in serious installation problems. Also, before you start your installation, be sure to review the hardware documentation that came with your system.
Enhancements have been made to the installation process for Version 4.0B. The installation cloning feature introduced in Version 4.0 has been enhanced to allow unattended installation cloning on client systems. For more information about this and other enhancements to the installation process, refer to the Installation Guide.
![[Previous Section]](http://www.tru64unix.compaq.com/docs/base_doc/DOCUMENTATION/HTML/AA-QTLMB-TE_html/PREV.GIF)
The following notes apply to the installation process in general.
If your system is one of the following newly supported hardware systems, follow the installation procedures in the corresponding section of the Installation Guide:
To verify that you have installed all the correct elements from the Digital UNIX Version 4.0B supplement, check the Digital UNIX revision level that appears in the /etc/motd file. The correct version string is:
Digital UNIX V4.0B Digital UNIX V4.0B Worksystem Software
The DEC 2000-300 system is not supported in a dataless environment and the software cannot be installed using Remote Installation Services (RIS).
When performing an installation from a slow device (for example, a CD-ROM or heavily loaded RIS server), the installation will terminate abruptly when the X server is killed. If this problem occurs, perform the following steps:
In this release, kernel object files are not needed for installation or kernel building. Only kernel modules are needed. The individual kernel object files are only needed for kernel development work.
The installation procedure automatically detects the disk(s) on a system, and asks you to specify the system (root) disk. If the disk label indicates that the a partition starts at a non-zero offset, the disk may not be detected by the installation procedure. This problem most commonly occurs with disks which have previously been used by LSM. LSM modifies the a partition to start at offset 16.
If all disks on the system cannot be detected because of this problem, the installation procedure will exit to a shell prompt #. If one or more disks are detected, while others are not, the undetected disks will not be presented to the user as devices where Digital UNIX can be installed.
You can correct this problem as follows. If the installation procedure does not automatically exit to the shell prompt, exit manually. In the graphical interface, click the UNIX Shell button, and click "OK" in the dialog box that appears. In the character-cell interface, press CTRL/C.
When you see the shell prompt, enter these commands:
#
cd /dev
#
./MAKEDEV <device>
where <device> is replaced by the actual device name such as rz3. If more than one disk is not detected by the installation procedure, enter a MAKEDEV command for each undetected disk.
Enter the following commands to restart the installation procedure:
#
cd /
#
restart
This note applies to all hardware configurations that do not have an attached graphics device. If the OSFXC2SEC410 subset is installed on a system that does not have a graphics controller installed on it, the following errors may be seen:
setld: Error installing "Graphical System Administration Utilities" (OSFXADMIN410) This subset requires following subset(s) to operate correctly:
"Graphical Base System Management Utilities" (OSFXSYSMAN410) setld: Please install required subset(s) first.
These errors are caused by subset dependency ordering and if the errors occur, the following subsets will not be properly installed onto your system.
OSFXC2SEC410 OSFXSYSMAN410 OSFCDEMIN410 OSFXADMIN410 OSFTKBASE410
Sometimes the following error message will be displayed during the installation of worldwide subsets and the installation procedure will abort:
/usr/sbin/setld: /usr/lbin/depord: arg list too long
This problem occurs because too many subsets were chosen and the shell ran out of memory during installation. You can work around it by choosing fewer subsets to install at first, and then installing additional subsets at a later time.
After changing the Install Type field (default to custom, or custom to default) and entering an invalid password, an error dialog box will be displayed but may not be in focus. An invalid password is one which is less than six characters long or contains only lowercase characters. Pressing Return to dismiss the dialog box when it is not in focus may cause you to be temporarily locked out of all editable fields. To avoid this situation after entering an invalid password, ensure the error dialog is in focus and either press Return or click on OK with the mouse to dismiss it. This will correctly clear the error dialog box and allow re-entry of the password.
If you encounter this temporary lock-out situation, you can work around the problem by setting focus to a non-editable field in the Installation Setup window (for example, clicking on a menu or button) and then setting focus back to the desired entry field. You can also set focus outside the Installation Setup window and back to it.
On booting, the Qlogic driver attempts to set the Data Overrun Recovery mode to that supported by Digital UNIX. If the operation fails, the driver will print a warning message on the system console:
isp<n>: WARNING - Data Overrun Recover Mode could NOT be set!
Where <n> is the number of the Qlogic controller encountered during system probe.
Digital recommends that the Qlogic ISP1020 or ISP1020A firmware be at a minimum revision level of 2.10. This is the minimum revision of Qlogic firmware required to implement reliable data overrun error detection and recovery.
An address conflict occurs between ISA serial devices configured as COM4 and ATI Mach64 graphics controllers. Both ISA GX and PCI ATI Mach64 CX/GX/CT products use the address range of 2EC-2EF. This is the same address range assigned to COM4 devices. Consult the hardware documentation for more information.
The installation process displays the following message during the installation of some subsets:
Broken Pipe
The installation will complete successfully and the message can be ignored.
The following notes apply to layered products for Digital UNIX, Version 4.0B.
DECthreads is Digital's multithreading run-time library. After installing the Digital UNIX Version 4.0B CMPDEVENH410 subset, static libraries for DECthreads are located in the /usr/opt/alt/usr/lib/threads directory.
Before using these static libraries, it is important that you read the README file in the same location.
If you plan to install any of the TruCluster software products on a system running Digital UNIX Version 4.0B , you must read Using TruCluster Software Products on Digital UNIX Version 4.0B, a supplement to the TruCluster software products documentation. This supplement is located on the Associated Products for Digital UNIX Version 4.0B, Volume 2 CD-ROM at:
/<mnt-pt>/DOCUMENTATION/TCR/POSTSCRIPT/AVAILABLE_SERVER/TCR140_USING_ON_4.0B.PS /<mnt-pt>/DOCUMENTATION/TCR/POSTSCRIPT/PRODUCTION_SERVER/TCR140_USING_ON_4.0B.PS /<mnt-pt>/DOCUMENTATION/TCR/POSTSCRIPT/MEM_CHANNEL_SW/TCR140_USING_ON_4.0B.PS
or
/<mnt-pt>/DOCUMENTATION/TCR/TEXT/TCR140_USING_ON_4.0B.TXT
Replace <mnt-pt> with the name of the directory where your CD-ROM is mounted.
DEC FUSE Version 2.1A and prior versions are not supported under Digital UNIX version 4.0B. DEC FUSE Version 3.0 is supported under Digital UNIX version 4.0B.
Hardware releases based on Digital UNIX Version 4.0B may not install the OSFBASE410.lk file; however, they will install a OSFBASE4??.lk lock file.
If you want to tie your product with Digital UNIX Version 4.0B you should use wildcards to check for the OSFBASE4??.lk file instead of OSFBASE410.lk file.
If you hard code the test for the OSFBASE410.lk into your subset control programs it will fail to find the lock file when run on a system with a Version 4.0B-based hardware release installed.
This policy has always been in place; however, until now, not following it had not caused any problems.
If you want to restrict your product from installing on Version 4.0B-based hardware releases, you can hardcode the OSFBASE410 string in your subset control program.
To update your Digital UNIX operating system software to Version 4.0B, you must use the installupdate or full installation procedures as described in the Installation Guide. Note that Version 4.0B only supports update installations from Digital UNIX Version 4.0 and Version 4.0A.
The following sections apply to the update installation procedure.
Use the wwinstallupdate procedure to update Version 3.2G or 4.0A Worldwide Language Support software to Version 4.0B
The update installation process does not convert the extended user profiles and tty information to the new database format. This can be done manually after the update installation completes with the following command:
#
/tcb/bin/convauth
The following sections provide information on installing Digital UNIX Server Extensions.
Due to incompatibilities between utilities used by Digital UNIX Version 4.0 (and later) and DEC OSF/1 V2.0, it is not possible for a OSF/1 V2.0 server to serve Digital UNIX V4.0 (and later) clients. You must upgrade the server operating system software to a minimum revision of DEC OSF/1 V3.0 to be able to serve Digital UNIX V4.0 (and later) clients.
If you install the Chinese subsets from a RIS server, the following error may occur:
Common Chinese Unicode Support Copying from hanax1 (inet) setld: cannot access server mapping (rcp: ris3.alpha/rp_mapping: No such file or directory) setld: Load from hanax1 failed, subset IOSZHUCSBASE410 Verifying setld: There were verification errors for "Common Chinese Unicode Support (IOSZHUCSBASE410)
This error causes the system to abort the installation process. The problem may happen in other Chinese subsets also.
The error occurs because of the number of subsets in the Worldwide kit.
To avoid this problem, create a RIS area with fewer subsets or Chinese subsets only. To do this, choose option 1 from the following menu when installing subsets to the RIS area:
Choose one of the following options:
1) Extract software from [kit location] 2) Create symbolic link to [kit location]
Enter your choice:
The subset size tables have been moved in to the Installation Guide in this release. If you want to add optional subsets after you install Digital UNIX Version 4.0B, use the df command to determine free disk space in blocks.