Release Notes Introduction SCO Support and Online Information Services SCO World Wide Web (WWW) site SCO Online Support Anonymous ftp Anonymous UUCP FTPmail InfoFAX SCOFORUM on CompuServe SCO-related Usenet newsgroups SCO Support contracted service SCO Authorized Support Centers Contacting SCO How can we improve our products? Chapter 1 Read this before installation Installation hardware requirements System memory Disk space Upgrading from an earlier SCO OpenServer Release 5 system Basic system requirements for upgrades SCO Compaq EFS upgrade Upgrading from an SCO Open Desktop system Installing on Using the ATAPI (EIDE CD-ROM) driver ATAPI (EIDE CD-ROM) installation procedure Determining your system configuration for ATAPI (EIDE CD-ROM) ATAPI (EIDE CD-ROM) limitations Network installations Installation limitations and workarounds Chapter 2 Read this after installation System configuration Configuring the system for additional users and CPUs Using documentation servers Configuring the kernel to enable Configuring multi-byte support Hardware configuration Software configuration Installing and configuring Internet FastStart Installing and configuring IPX/SPX Installing and configuring PC-Interface Installing and configuring SCO Gateway for NetWare Installing NetWare Loadable Modules Installing WordPerfect 6.0 Introduction This book contains critical information you need to know before and just after installing SCO OpenServer(TM) Release 5.0.4. Familiarize yourself with the information in these notes that is relevant to your system, then install SCO OpenServer according to the instructions in the SCO OpenServer Handbook. This release runs in English, French, and German. Translated documentation consists of the System Administration Guide, SCO OpenServer Handbook, SCO OpenServer Features and Limitations, and these Release Notes, as well as desktop and client help information. Other parts of the documentation set are not translated and are available only in English. For notes about system, graphical environment, help, mail, networking, and DOS and Windows features, limitations, and workarounds, see SCO OpenServer Features and Limitations online. See ``Getting help'' in the SCO OpenServer Handbook to learn how to access the online documentation. SCO Support and Online Information Services SCO(r) provides these services free of charge to all SCO customers: + ``SCO World Wide Web (WWW) site'' + ``SCO Online Support (SOS) System'' + ``Anonymous ftp'' + ``Anonymous UUCP'' + ``FTPmail'' + ``InfoFAX'' Online SCO user forums are available through: + CompuServe + Usenet news SCO also provides: + fee-based support services direct from SCO + support through SCO Authorized Support Centers For more information, contact SCO at one of our worldwide offices. SCO World Wide Web (WWW) site The SCO World Wide Web site contains hyperlinks to: + SCO Software Support Library (SSL), the searchable technical articles database + supplemental patches and fixes for SCO products + supplements that improve or enhance products + device drivers for newly released hardware + archives of freely available software ported to SCO platforms + bug reporting form + datasheets on SCO products and services + listing of Authorized Support Centers (ASC) + class schedules for Authorized Education Centers (AEC) + Directory of Third Party Products and Services + news and other timely information To access the SCO web site, you must have an Internet browser, such as Netscape(TM) Navigator(TM) or scohelp(XC), and an Internet connection. Set your browser to: http://www.sco.com/ SCO Online Support (SOS) System SOS is a menu-driven BBS program that provides a character-based, easy- to-use front-end for those who do not have a Web browser or Internet access. The SOS system contains similar information to that available on WWW. To access the SOS system, you must have one of the following: + a terminal and modem + a computer, modem, and third-party communications package + the cu(C) command for SCO XENIX or SCO UNIX(r) systems _________________________________________________________________________ NOTE To download supplemental patches, your third-party communications package must support XMODEM, YMODEM, ZMODEM, or kermit transfer protocols. _________________________________________________________________________ Use these telephone numbers: United States, Canada, Pacific Rim, Asia, and Latin America: + v.32 and v.32bis: (408) 426-9495 + Telebit Trailblazer: (408) 426-9525 Europe, the Middle East, and Africa: + Hayes Acura 288, v.32, v.32 bis and v.34: +44 (0) 1923 210888 Internet access using telnet(TC) is available by entering telnet sos.sco.com. Anonymous ftp SCO's anonymous ftp site contains: + supplemental patches for specific SCO products + device driver for newly released hardware + archives of freely available software ported to SCO platforms _________________________________________________________________________ NOTE For additional information regarding availability in each of the supplementary software distributions, download the README file located in the ftp root directory. _________________________________________________________________________ For ftp access to SCO's Internet site, you need the ftp(TC) program and an Internet connection. ftp is a standard function in UNIX systems and also is available in Microsoft Windows 95, Windows NT, and many other popular operating environments. To access anonymous ftp: 1. Enter ftp ftp.sco.com. 2. Log in as the user anonymous. 3. Use your e-mail address as the password. Anonymous UUCP When UUCP is configured, you can access the sosco (US) or scolon (UK) systems to download the supplementary distribution files located in the /usr/spool/uucppublic directory. A sample entry for accessing sosco using uucp(C) is located in the /usr/lib/uucp/Systems file on the local machine. SCO's anonymous UUCP site contains: + supplemental patches for specific SCO products + device drivers for newly released hardware + archives of freely available software ported to SCO platforms _________________________________________________________________________ NOTE Download the /usr/spool/uucppublic/README file using UUCP for additional information regarding availability in each of the supplementary software distributions. _________________________________________________________________________ To access the SCO UUCP site, you must have a modem and UUCP installed and configured on your system. In Canada, the United States, Pacific Rim, Asia, and Latin America: 1. Dial one of these telephone numbers: + v. 32, v.32bis: + (408)425-3502 + Telebit Trailblazer: + (408)429-1786 2. Enter this information: Machine name = sosco Login name = uusls No Password In Europe, the Middle East, and Africa: 1. Dial one of these telephone numbers: + v.32: +44 (0) 1923 222681 + Dowty Trailblazer: +44 (0) 1923 210911 2. Enter this information: Machine name = scolon Login name = uusls Password = bbsuucp FTPmail FTPmail is an automated e-mail service which acts as a gateway between electronic mail and ftp, executing ftp commands received by e-mail, and sending back the requested files to the user by e-mail. To use this, you need an e-mail program, accessible from the Internet (that is, through your Internet service provider). For more information, send email to ftpmail@sco.com. Leave the subject line blank and create a message consisting only of the word ``help''. InfoFAX InfoFAX is an unattended FAX-back service. InfoFAX contains copies of the most commonly requested technical articles, educational offerings, and product information. To access InfoFAX, call +(408) 427-6800. You must have a touch-tone phone (or equivalent software) and a FAX machine. For a listing of the available articles, request article 1000. SCOFORUM on CompuServe An extensive set of ongoing CompuServe sections, discussion areas, and technical information is available about SCO in the SCOFORUM area of CompuServe. To access these services, you must have a CompuServe Account and a third-party communications package. For more information on acquiring a CompuServe account or to get local access phone number, call CompuServe at 1-800-524-3388 and ask for Representative #432. You can access CompuServe's website at: http://world.compuserve.com As an account holder, to access this area: 1. Log onto CompuServe. 2. Enter GO SCOFORUM. SCO-related Usenet newsgroups There are several public SCO-related Usenet newsgroups available for those who have Internet access. These newsgroups contain questions, answers, comments and discussion about past, present, and future SCO products and services. The pertinent newsgroups are: comp.unix.sco.announce (moderated) comp.unix.sco.misc comp.unix.sco.programmer comp.unix.unixware.misc comp.unix.xenix.sco To access the Usenet newsgroups, you need news-reading software, which is available in most commercial Internet browsers, or any of the well-known UNIX newsreaders, such as tin, trn, nn, or rn. SCO Support contracted service Fee-based telephone support services are available. Contact your SCO service or software provider or refer to the SCO home page at http://www.sco.com/Support for services available from SCO and authorized providers. See also ``SCO Authorized Support Centers''. SCO Authorized Support Centers The Authorized Support Center (ASC) program offers SCO customers the freedom of choice of quality providers and products to meet all of their service needs. This is an open systems approach to service delivery. The ASC partners are highly qualified service providers who can offer a wide range of service options, including worldwide support 24 hours per day, 7 days per week. The ASCs meet SCO's program requirements to ensure quality support on SCO products to a wide range of SCO customers. They have a minimum of two certified SCO ACE engineers employed, backup support from SCO, and metrics in place to ensure a high level of customer satisfaction in delivering support. United States and Canada ASCs: Data Dynamics, Inc. Enterprise Support Services 508 Broad Street 7305 Rapistan Court Shrewsbury, NJ 07702 Mississauga, Ontario L5N 5Z4 Tel: 908-758-0040 Tel: 800-821-2286 Fax: 908-758-8340 Phone Locally: 905-542-0755 Fax: 905-542-3127 E-mail: support@esshelp.com ICS Support, Inc. Multi-User Solutions 12015 115th Avenue Northeast 3000 Miller Court West Suite 215 Norcross, GA 30071 Kirkland, WA 98034 Tel: 770-246-8500 or Tel: 206-820-6120 ext. 109 Fax: 206-820-6420 800-295-7904 E-mail: info@icss.wa.com Fax: 770-453-9163 E-mail: sales@multiuser.com NCR Corporation Regional Care Center 1346 Oakbrook Drive, Suite 170 Norcross, GA 30093 ASCs in Europe, Middle East, Asia, Africa, and the Pacific Rim: Australia Denmark MUA Pty Limited ACE Level 1, 66 Dickson Avenue Nordskraenten 19 Artarmon 2064 DK-2980 Kokkedal New South Wales Tel: +45 42 57 07 99 Tel: +61 2 9928 5111 Fax: +61 2 9436 0185 Contact: Geoff Wilson Contact: Jon Svejgaard France TIM Unisys France 56/60 Avenue du Vieux Chemin de Saint Denis 7 Boulevard des Bouvets 92230 Gennevilliers 92027 Nanterre Cedex Tel: +33 (0) 1 41 47 14 00 Tel: +33 (0) 1 46 69 51 84 Contact: Philippe Michaud Contact: Claude Courdy Germany Italy Siemens AG Oaxis srl Oestl Rheinbruecken Strasse 50 Via Serio 14 76187 Karlsruhe 20100 Milano Tel: +49 (0) 721 59 54 844 Tel: +39 (0) 2 57 30 32 03 Contact: Hermann Wanhorst Contact: Vittorio Manfredini The Netherlands Poland Foundation Software bv ABA Randstad 21 - 57 31-261 Krakow 1314 BH Almere-Stad Ul Wybickiego 7 Tel: +31 (0) 36 54 85 010 Tel: +48 (0) 12 32 49 78 Contact: Eric Otten Contact: Tomasz Barbaszewski Russia Olly Limited 14 Linia - VO 39 199178 St Petersburg Tel: +7 (0) 812 21 80 450 Contact: Pavel Yakovlev United Kingdom ICL Sorbus Olivetti UK Limited Hanover House Olivetti House Plane Tree Crescent 1 Deltic Avenue Feltham Rooksley Middlesex TW13 7HJ Milton Keynes MK13 8LD Tel: 0345-669933 (UK) Tel: +44 (0) 1908 69 07 90 +44 (0) 181 83 14 741 (International) Contact: Les Gray Contact: Software Services Sales Desk Unisys Limited Fox Milne Milton Keynes MK15 0YS Tel: +44 (0) 1908 21 24 10 Contact: Richard West Contacting SCO You can contact SCO at these offices throughout the world. See also World Wide Web site: http://www.sco.com Corporate and Americas Headquarters European Headquarters The Santa Cruz Operation, Inc. The Santa Cruz Operation, Ltd. 400 Encinal Street, P.O. Box 1900 Croxley Centre, Hatters Lane Santa Cruz, CA 95061-1900 Watford WD1 8YN Sales and Info: 1-800-SCO-UNIX (726-8649) United Kingdom 408-425-7222 Fax: 408-458-4227 +44 (0) 1923 816344 TELEX: 917372 SCOLON G Fax: +44 (0) 1923 817781 E-mail: ...uunet!sco!info info@sco.COM E-mail: ...uknet!scol!info info@sco.COM Asian Headquarters Australia The Santa Cruz Operation (Asia) Ltd. The Santa Cruz Operation, Ltd. 171b Chin Swee Road Level 7 #03-05/06 San Centre 157 Walker Street Singapore 169877 North Sydney NSW Tel: 011-65-536-6606 Australia, 2060 Fax: 011-65-536-6619 (Asean & South Asia) Tel: 011-61-2-966-1999 Fax: 011-65-536-7291 (Pacific Rim HQ) Fax: 011-61-2-955-1077 Canada China SCO Canada SCO Beijing Queen's Quay Room 461 Shangri-La Hotel Executive Offices Ltd. 29 Zizhuyuan Road 20 Bay St., Ste 1205 Beijing 100081, China Toronto, Ontario M5J 2NB Tel: 011-8610-841-2211 Ext 461 Tel: 416-214-9793 Fax: 011-8610-847-1102 Fax: 416-214-9810 E-mail: scobj@bepc2.ihep.ac.cn Colombia Eastern Europe and Central Asia SCO Colombia The Santa Cruz Operation Calle 100 # 8A-49 Eastern Europe & Central Asia Oficina 602 Torre B Werftstrasse 20-22 Santa Fe de Bogota, Colombia 40545 Duesseldorf 11, Germany Tel: 011-57-1-611-3841 Tel: 011-49-211-5768-41 Fax: 011-57-1-611-3817 Fax: 011-49-211-5738-61 TELEX: 8584579 France Germany/Headquarters The Santa Cruz Operation (France) Sarl. SCO (Deutschland) GmbH 4 Boulevard des Iles Norsk-Data-Str. 3, Ober -Eschbach 92130 Issy Les Moulineaux, France 61352 Bad Homburg v.d.H., Germany Tel: 011-33-1-4190-2400 Tel: 011-49-6172-48670 Fax: 011-33-1-4190-2424 Fax: 011-49-6172-486712 Germany/Munich Hong Kong OEM Vertriebsburo The Santa Cruz Operation Inc. Edelsbergstrasse 8 Room 2902 Windsor House 80686 Munchen, Germany 311 Gloucester Road Tel: 011-49-89-5707-674 Causeway Bay, Hong Kong Fax: 011-49-89-5705-493 Tel: +852 2882 7377 Fax: +852 2882 7366 Italy Japan The Santa Cruz Operation (Italia) Srl Nihon SCO K.K. Centro Direzionale Lombardo Nakamura Bldg. 2nd Floor Palazzo B Scala 1, Via Roma 108 2-24-3 Ohashi, Meguro-ku 20060 Cassina de Pecchi Tokyo, 153, Japan Milano, Italy Tel: 011-81-3-5486-3905 Tel: 011-392-953-01-383 Fax: 011-392-951-63-94 Fax: 011-81-3-5486-3918 SCO K.K. Mexico 1-8-27, Kohnan, Minato-ku, The Santa Cruz Operation, Inc. Tokyo 108, Japan Rio Rhin #22 Ph.2 Tel: 011-81-3-5462-9678 Col. Cuauhtemoc 06500 Fax: 011-81-3-5462-9687 Mexico, DF, Mexico Tel: 011-525-566-1781 Fax: 011-525-592-0572 Nordic Region/Denmark Middle East The Santa Cruz Operation Ltd. The Santa Cruz Operation Ltd. Nordic Region 7th Floor Hanne Nielsens Vej 10 Dubai World Trade Centre DK- 2840 Holte, Denmark P.O. Box 9204 Tel: 011-45-42-42-57-75 Dubai, United Arab Emirates Fax: 011-45-42-42-27-78 Tel: +97 14 313712 Fax: +97 14 313493 Spain South Africa SCO Spain SCO Representative Office Paseo de Recoletos, 16 8 0 1st Floor, Block F 28001 Madrid, Spain Lonehill Office Park Tel: +34-(9)1-436-01-36 Lonehill 2162 Fax: +34-(9)1-436-01-37 Johannesburg, Republic of South Africa Tel: +27 11 465 7025 Fax: +27 11 465 7024 Sweden California/Los Angeles The Santa Cruz Operation Ltd. The Santa Cruz Operation, Inc. Gavlegatan 18 B 11601 Wilshire Blvd. Suite 500 S-113 31 Stockholm, Sweden Los Angeles, CA 96025 Tel: +46 8 34 7560 Tel: 310-575-4819 Fax: +46 8 34 541 Fax: 310-575-1848 Florida/Miami (Latin American sales) Florida/Altamonte Springs The Santa Cruz Operation, Inc. The Santa Cruz Operation, Inc. 400 South E. 2nd Ave. 4th Floor 405 Douglas Ave Suite 1305 Miami, FL 33131-2117 Altamont Springs, FL 32714 Tel: 305-579-0224 Tel: 407-786-0334 Fax: 305-579-9105 Fax: 407-786-0337 Illinois/Chicago Texas/Dallas The Santa Cruz Operation, Inc. The Santa Cruz Operation, Inc. 2001 Spring Road The Plaza at Riverbend Suite 480 1230 River Bend Drive Oakbrook, IL 60525 Dallas, TX 75247 Tel: 630-574-2382 Tel: 214-589-0960 Fax: 630-645-8159 Fax: 214-589-0973 Texas/Austin Virginia/Reston (Federal customers) The Santa Cruz Operation, Inc. The Santa Cruz Operation, Inc. 1015 East Yager Lane, Suite 23 2100 Reston Parkway, Ste. 102 Austin, TX 78753 Reston, VA 22091 Tel: 512-837-9775 Tel: 703-715-8700 Fax: 512-837-9792 Fax: 703-715-8750 How can we improve our products? If you have comments regarding the ease of using this and other SCO products, please e-mail usability@sco.com. Chapter 1 Read this before installation To successfully install SCO OpenServer, you must be familiar with this important information about: + Installation limitations and workarounds + Installation hardware requirements The complete installation and upgrade instructions are in the SCO OpenServer Handbook. See also: + Installing on SCSI subsystems + Using the ATAPI (EIDE CD-ROM) driver + Upgrading from an earlier SCO OpenServer Release 5 system + Network installations Installation hardware requirements Before installing SCO OpenServer, make sure your system has at least the minimum required system memory and hard disk space specified here. See the SCO OpenServer Development System Release and Installation Notes for SCO OpenServer Development System installation requirements. System memory SCO OpenServer installation requires a minimum of 16MB RAM for the Host, Desktop or Enterprise Systems. We recommend at least 32MB RAM. _________________________________________________________________________ NOTE The installation procedure checks your system for available RAM and displays an error message if it is below the minimum requirements. If so, you must install the Small Memory Supplement, which will be available soon after the release of this SCO OpenServer product. See your SCO distributor for more information. _________________________________________________________________________ Disk space These sizes are representative and might not be the same on all systems. Fresh installation type For a default Fresh installation, the SCO OpenServer Host System requires 215MB, the SCO OpenServer Desktop System requires 230MB, and the SCO OpenServer Enterprise System requires at least 240MB of hard disk space. In each case, 15MB is reserved for /stand, and swap space is an additional requirement. French and German language support require 17MB per language. To accommodate more than one graphical user, we strongly recommend that you specify swap space that is 150% to 200% as large as the RAM in your system. For non-graphical systems, we recommend swap space that is 150% as large as the system's RAM. The default minimum swap space presented during installation is 24MB. The root filesystem is no longer limited to the first 1024 cylinders of the hard disk and can be made much larger than the (approximately) 200MB of space required to accomodate the software installation. The layout of the root filesystem can be controlled manually at installation using the Interactive disk setup; for more information, see ``Partitioning the hard disk using fdisk (Interactive installation)'' in the SCO OpenServer Handbook. The /stand (boot) filesystem must be large enough to hold three kernels, plus some extra software. It defaults to 15MB; we strongly recommend at least 10MB. SCO Virtual Disk Manager, SCO SMP License, SCO Merge, and the SCO OpenServer Development System all require additional space in the root filesystem: _________________________________________________________ For Add _________________________________________________________ SCO Virtual Disk Manager 1MB SCO Symmetrical Multiprocessing Support 1MB SCO Merge 12MB SCO OpenServer Development System 51MB See these product's Release Notes for more information. Preserve hard disk setup Within a Fresh installation, you can choose the Preserve hard disk setup (see ``Choosing an upgrade path'' in Chapter 2 of the SCO OpenServer Handbook). For a Preserve setup, the required disk space on the root filesystem is the same as given in the information on Fresh installation type in ``Disk space'', plus the amount of swap space already configured on the system. The recommended space goes entirely to the root filesystem; Preserve does not create a /stand filesystem. If you preserve a non-root filesystem on any hard disk, it will not be mounted on the first boot after installation. For any non-root filesystem, record the block device and mount point before installing SCO OpenServer. After installation, run mkdev fs for each such filesystem and enter the associated block device and mount point. Once you have installed all filesystems, reboot the system to activate these changes. Upgrade installation type For an Upgrade installation, your new system software will be installed either in the root filesystem (the default) if there is enough free space in that filesystem, or in root and another filesystem with free space. If you do not have enough free space in root, the installation procedure will automatically detect this and prompt you to relocate parts of your new software. If your total disk space is insufficient, see ``Adding a disk for an upgrade''. _________________________________________________________________________ CAUTION Once you choose to relocate software during installation, you will not be able to reverse this action from within the current installation procedure. To cancel software relocation, abort the current installation procedure, reboot the system, and select the Fresh installation type. Before you proceed with software relocation, read ``About the Upgrade installation type'' in Chapter 2 of the SCO OpenServer Handbook carefully. Relocating software to the wrong filesystem can cause serious problems. _________________________________________________________________________ To install the SCO OpenServer product entirely in the root filesystem, you must have at least as much free space as listed for your scenario in this table: _________________________________________________________ To upgrade from To SCO OpenServer Free Release 5.0.0 & 5.0.2 Release 5.0.4 space _________________________________________________________ SCO Open Server Enterprise Enterprise System 150MB System SCO OpenServer Desktop System Enterprise System 130MB SCO OpenServer Host System Enterprise System 100MB If you do not have enough free space in the root filesystem and choose to proceed with the installation by allowing software to be relocated into another filesystem with enough free space, you will still need 50MB of free space plus 17MB per language in your root filesystem, plus the amount listed above for your upgrade scenario. If you intend to install SCO Virtual Disk Manager, SCO SMP License, SCO Merge, or the SCO OpenServer Development System, you need additional space in the root filesystem, as specified in the table above. If you have additional system software (such as the SCO OpenServer Development System) on the root filesystem before the upgrade, increase the minimum required root filesystem space by the amount used by that additional software. In an upgrade of the system that had the Localized Desktop installed, both the French and German language support products will be installed. Thus, in such an upgrade, disk space for both language support products will have to be available. See also ``Upgrading from an earlier SCO OpenServer Release 5 system''. Upgrading from an earlier SCO OpenServer Release 5 system This release offers the Upgrade installation type for previous SCO OpenServer Release 5 releases. This option removes all earlier versions of SCO products whose functionality has been incorporated into SCO OpenServer Release 5.0.4 and installs the new versions. It does not remove other files on the system. _________________________________________________________________________ NOTE After an Upgrade installation, the Software Manager (or custom) might show some patches still loaded on your system. Any patches that are loaded and applied are still functional. Examine any that are loaded and not applied. If they apply to the base operating system, they are obsolete in SCO OpenServer Release 5.0.4 and can be removed. If they apply to other products, consult the most current release information for that product to see if they are still relevant. _________________________________________________________________________ Before choosing the Upgrade installation type, read this entire section and ``About the Upgrade installation type'' in Chapter 2 of the SCO OpenServer Handbook. To upgrade from SCO(r) Open Desktop(r) Release 3.0 or 2.0 to SCO OpenServer Release 5.0.4 see ``Upgrading from an SCO Open Desktop system'' and ``Choosing an upgrade path'' in the SCO OpenServer Handbook. _________________________________________________________________________ NOTE Before you begin any upgrade: + Back up your current system and verify that the backup was successful. See ``Running unscheduled filesystem backups'' in the System Administration Guide for more information. + Run fsck(ADM) and shut the system down cleanly. _________________________________________________________________________ See also: + Basic system requirements for upgrades + SCO DCE Development System upgrade + Compaq EFS upgrade Basic system requirements for upgrades SCO OpenServer Release 5.0.4 is larger than previous releases. See ``Disk space'' for specific space requirements for each upgrade path. Adding a disk for an upgrade If you have insufficient disk space for an upgrade, you can add a disk before beginning the upgrade. Install and configure the disk on your current system, relink the kernel, then reboot; see Chapter 17, ``Adding hard disks'' in the SCO OpenServer Handbook for more information. Run mkdev fs to create any filesystems that you need. Then, verify that you can access the disk (for example, with the mount(ADM) command) before beginning the upgrade. The installation or upgrade can use as many as two non-SCSI disks. If you have a SCSI subsystem, you can add one or more SCSI disks. Upgrading third-party LLI drivers If you upgrade from a previous SCO operating system with a network adapter driver that was not provided by SCO, you might see an error message similar to: Error: Cannot configure lo0 under sco_tcp Press to ignore this error message; TCP/IP will be fully functional after the upgrade. Upgrading cron and at jobs If you upgrade from a system that uses /usr/lib/cron/cron.deny instead of /usr/lib/cron/cron.allow, then both files will exist on the system after an upgrade. To continue using /usr/lib/cron/cron.deny, remove /usr/lib/cron/cron.allow. (If you are using /usr/lib/cron/cron.allow, you do not need to change.) Similarly, if you upgrade from a system that uses /usr/lib/cron/at.deny instead of /usr/lib/cron/at.allow, then both files will be present after the upgrade, and you should remove /usr/lib/cron/at.allow. (If you are using /usr/lib/cron/at.allow, you do not need to change.) Upgrading a system with user crontab(C) entries might produce an error message similar to: Error: Unable to add custom symlinks report to crontab file Press to ignore this error message and continue; your crontab files will be preserved during the Upgrade installation. Upgrading the sendmail aliases database After an upgrade installation of a system that uses sendmail as the Mail Transfer Agent, run the newaliases(ADMN) command as root. This rebuilds the sendmail aliases database. SCO DCE Development System upgrade Prior to performing an Upgrade installation, remove the SCO DCE Development System. After the upgrade, install the SCO DCE Development System Release 1.0.3g; this is the only version that will run on SCO OpenServer. See ``SCO Support and Online Information Services'' for more information about obtaining this product. Compaq EFS upgrade Prior to performing an Upgrade installation, remove any existing Compaq EFS. After the upgrade, install the latest version. Any Compaq EFS 5.0 or later is engineered for SCO OpenServer Release 5. Compaq supplements are available from your Compaq distributor, the Compaq ftp site (ftp.compaq.com), or SCO Support Services. Upgrading from an SCO Open Desktop system To preserve the hard disk setup of an SCO Open Desktop Release 3.0 or 2.0, select Fresh as the Installation type, then select Preserve under Hard disk setup. (See ``Choosing an upgrade path'' in Chapter 2 of the SCO OpenServer Handbook.) You must start the installation on an active UNIX(r) partition with a clean root filesystem with device nodes that match those in /etc/default/filesys. Your current SCO system must be on the first division of the active partition. _________________________________________________________________________ NOTE Before you install SCO OpenServer on a computer with a previous SCO operating system, run fsck(ADM) and shut it down cleanly. _________________________________________________________________________ Installing on SCSI subsystems Before installing on SCSI subsystems, familiarize yourself with these potential problems: + ``SCSI termination problems'' + ``SCSI boot problems'' SCSI termination problems The installation process for SCO OpenServer is sensitive to SCSI termination. Because the SCSI bus is heavily loaded during installation, incorrect termination will prevent the installation process from completing correctly. Incorrect SCSI termination might result in one of the two following error conditions: + During the installation process, the following set of messages is displayed: Export phase for "SCO: UNIX" failed Error exporting component SCO:UNIX:5.0.0nn to /{somedir} Error exporting packages of component SCO:UNIX to client... Error exporting package SCO:UNIX:RTS Error exporting file /var/opt/K/SCO/UNIX/... Error creating symbolic link of ... Not a directory + When you reboot the system after an installation procedure which was apparently successful, the following message is displayed: PANIC: srmountfun - Error 22 mounting rootdev hd(1/42) Before you attempt to reinstall, follow the procedure below which applies to your installation hardware situation to recover from these conditions. _________________________________________________________________________ WARNING Before following these procedures, turn off the power and remove the power cord from the power source. There is risk of injury to person or equipment if you do not do so. _________________________________________________________________________ Internal devices If the installation CD-ROM and the root hard diskare physically located on the internal bus (inside the machine): 1. Remove all devices from the external SCSI bus by unplugging the cable from the back of the SCSI host adapter card (the backplane). 2. Terminate the host adapter either by plugging a resistor pack into the backplane, setting jumpers, or by using the BIOS setup program. 3. Remove all devices from the internal SCSI bus except for the installation device CD-ROM and the root hard disk. You must remove secondary hard drives. Floppy drives might remain on the host adapter because they are not connected to the SCSI bus. 4. Ensure that only the host adapter and the last device on the internal cable are terminated. 5. Reinstall your SCO OpenServer system. Mixed internal and external devices If either the installation device or the root hard disk is on the external bus and the other device (installation device or root hard disk) is on the internal bus: 1. Ensure that the external device either has a resistor pack plugged into the back of the SCSI peripheral controller (tape device, CD- ROM, or hard disk), or that the device's termination is activated by using the appropriate settings to enable active termination. (See the device documentation for appropriate switch settings.) 2. Carefully remove any resistor packs installed on the host adapter card. (See your host adapter documentation for specific location.) 3. Remove all devices from the internal SCSI bus except for the installation device CD-ROM and the root hard disk. Floppy drives might remain on the host adapter because they are not connected to the SCSI bus. 4. Ensure that only the last devices on the internal and external cables are terminated. The SCSI host adapter itself should not be terminated. 5. Reinstall your SCO OpenServer system. External devices If both the installation device and the root hard disk are located on the external SCSI bus: 1. Ensure that the last physical connection of the external cable chain is plugged into a terminated device. 2. Ensure resistor packs are installed on the host adapter card. 3. Remove (unplug) the internal SCSI bus cable. 4. Reinstall your SCO OpenServer system. If you still experience problems after following these steps, check the SCSI termination again. Also consider replacing the internal-bus SCSI cable and/or the passive resistor pack used to terminate the external bus. SCSI boot problems Problems found during the boot phase of the installation might require certain SCSI drivers to be disabled. To disable a driver at boot time, add disable=driver_name to the bootstring(HW). For example, the following command at the boot(HW) prompt restarts the installation and disables the alad SCSI host adapter driver: restart disable=alad Disable the driver that corresponds to the init() function shown in the following table; init()functions are displayed in the boot hardware listing: _________________________________________________________________________ driver init() device name function name _________________________________________________________________________ ad ahainit Adaptec 154x, 164x, 174x (in Standard mode) arad aradinit Adaptec 274x (7770 Chip) alad aladinit Adaptec 294x (7870 & 7880 Chip) ams amsinit Advanced Micro Devices PCscsi blc blcinit BusLogic Multi Master Adapters ciha cihainit Corollary 386/486 CBUS SCSI-CPU dptr dptrinit DPT SCSI & RAID Host Adapters efp ehainit Olivetti ESC-1, ESC-2, and EFP Adapters eiad eiadinit Adaptec 174x (in Enhanced mode) fdhb fdi_init Adaptec 292x, Future Domain 16x0, 600, 700 (18x0 Chip) flashpt fptinit BusLogic FlashPoint Adapters hf hfinit IBM HardFile Host Adapters mdac mdacinit Mylex Disk Array Controller ncr ncrinit NCR Microchannel Systems Host Adapters piiop piiopinit Tricord Intelligent I/O Processor slha slhainit Symbios Logic (formerly NCR MPD) 53c8xx Host Adapters smad smadinit Adaptec 151x, 152x (6260 & 6360 Chip) tmcha tmc_init Future Domain 845, 850, 860, 885 (950 Chip) wd wdinit Enhanced IDE, ATAPI Interface (for tapes and CD-ROMs) wdex wdexinit Future Domain (formerly Western Digital) 7000EX wdha wdhainit Future Domain (formerly Western Digital) 7000 Using the ATAPI (EIDE CD-ROM) driver The ATAPI driver provides support for Extended IDE (EIDE) CD-ROM drives by representing the drive as a SCSI device to the operating system. In order to present a consistent interface, the following restrictions apply: + A maximum of two IDE controllers can be present on any system. + No more than two IDE devices might be present on any one IDE controller. + If there is only one IDE device on a controller, it must be configured as a ``Master'' device. If there are two devices on the controller, one must be configured as a ``Master'' device and the other as a ``Slave'' device. + If only one IDE controller is present, it must be configured as the ``Primary'' controller. If there are two controllers, one must be configured as ``Primary'' and the other as ``Secondary''. _________________________________________________________________________ NOTE The procedure you need to apply to install and configure EIDE- or IDE-interface hardware (controllers, disk drives, ATAPI CD-ROM and ATAPI tape drives) for your system is described in the documentation provided by your hardware supplier. Any information provided by your hardware supplier might invalidate the information here. _________________________________________________________________________ ATAPI (EIDE CD-ROM) installation procedure To install your system using an Extended IDE CD-ROM drive: 1. Boot from the boot disk. 2. Enter restart or press at the boot prompt unless you need to alter the default configuration. In most cases, this is not necessary; see ``Installation limitations and workarounds''. 3. At the ``Media device'' window, choose ``IDE CD-ROM'' as the media device type. 4. If the CD-ROM drive is attached to the Primary IDE controller in a system with one or two IDE controllers, select Primary under IDE Controller. If the CD-ROM drive is attached to the Secondary IDE controller in a system with two IDE controllers, select Secondary under IDE Controller. 5. If the CD-ROM drive is configured as a Master device, select Master under Master or Slave. If the CD-ROM drive is configured as a Slave device, select Slave under Master or Slave. _________________________________________________________________________ NOTE A hard disk and a CD-ROM drive present on the same IDE controller are usually configured as Master and Slave devices respectively. If no hard disk drive is present on the same controller, the CD-ROM drive will usually have been configured as a Master device. _________________________________________________________________________ From this point, continue with the installation as described in the SCO OpenServer Handbook. Determining your system configuration for ATAPI (EIDE CD-ROM) If you are uncertain of the hardware configuration of your system, but you know that the primary hard disk is attached to an IDE controller, the following information will allow you to determine the most likely configuration. This information is displayed at boot time. Entries for the ATAPI CD-ROM will take one of the following forms, as indicated by the presence of the string type=IDE: %cd-rom - - - type=IDE ctlr=pri cfg=mst drv=Srom->wd Here, pri indicates that the ATAPI CD-ROM drive is attached to the Primary IDE controller. %cd-rom - - - type=IDE ctlr=sec cfg=mst drv=Srom->wd Here, sec indicates that the ATAPI CD-ROM drive is attached to the Secondary IDE controller. If you are in doubt as to your system configuration, check the documentation that was supplied with your hardware. ATAPI (EIDE CD-ROM) limitations + If your CD-ROM drive does not read, it might be because the device does not support 6-byte SCSI read commands. In this case, add Srom.ten to your bootstring(HW). At the boot prompt, enter: defbootstr Srom.ten To make this change permanent, you can add the product identification string to a table in the Srom driver's space.c file. To do so: 1. Determine your device's product identification string using one of these methods: - Enter Srom.display or defbootstr Srom.display at the boot prompt. The Srom driver will display the vendor identification string, the product identification string, and the product revision level for the device. Pointers in the display indicate that device is open; blank spaces are significant. - Edit the /etc/conf/pack.d/Srom/space.c file, setting each of the following variables to 1: Srom_Inq_VID vendor identification string Srom_Inq_PID product identification string Srom_Inq_PRL product revision level When the device is opened, the strings are displayed. You must relink and reboot your system after editing this file. 2. Edit the /etc/conf/pack.d/Srom/space.c file, adding the product identification string to the Srom_TenByte[] array. 3. Relink and reboot your system. The system will now automatically recognize your CD-ROM as a device requiring ten-byte SCSI read commands. Contact your hardware vendor about your device's read command requirements; see also the Srom(HW) manual page. + Internal IDE CD-ROM drives might not be recognized if the initial configuration was set incorrectly, for example: Identifying the installation media device Media device to be used: IDE CD ROM IDE Controller: primary Master or Slave: slave If you have this problem, the boot hardware information display will be similar to: %adapter 0x0170-0x0177 15 - type=IDE ctlr=primary dvr=wd %tape - - - type=IDE ctlr=pri cfg=slv dvr=Stp->wd %cd-rom - - - type=IDE ctlr=pri cfg=slv dvr=Srom->wd This problem has been encountered in some Toshiba laptops. To correct it, rerun the initial configuration routine and set the controller values to: IDE Controller: secondary Master or Slave: master + ATAPI CD-ROM drives might hang during installation if you also have SCSI devices configured on your system. The installation process attempts to scan for additional hard drives to allow them to be configured during installation rather than after the installation is complete. However, this scan might cause some ATAPI CD-ROM drives to hang on systems that have both SCSI and ATAPI hardware enabled. If you encounter problems, add wd.noscan to your bootstring to prevent scanning during installation. If you need to configure additional hard drives, do so after installation is complete. This bootstring is not required after installation. See bootstring(HW) for more information. Systems that include single types of mass storage devices (that is, EIDE/ATAPI or SCSI only) do not need this bootstring. Network installations If you are configuring your system as a network (remote) installation server, you might need to extract additional product database files from your original media before completing the server configuration. For example, if you install the SCO OpenServer product on the server and you want to support network installations of the SCO OpenServer Desktop System and SCO OpenServer Host System products, log in as root and enter these commands: cd / mount -r /dev/cd0 /mnt cpio -idumvI /mnt/opt/archives/VOL.000.002 "opt/P/SCO/odtps/*" \ "opt/P/SCO/unixos/*" netisl server on umount /mnt _________________________________________________________________________ NOTE The names of the product database files for the Host, Desktop, and Enterprise Systems are unixos, odtps, and odtes respectively. To also load the databases for the French and German language support products, append _FR for the French support product and _DE for the German support product. For example, the commands above are for the English product. To make the French language support product available for network installation, include "opt/P/SCO/odtps_FR/*" and "opt/P/SCO/unixos_FR/*" on the cpio command line. Similarly, if you need to make the German language support product available for network installation, include "opt/P/SCO/odtps_DE/*" and "opt/P/SCO/unixos_DE/*" in the cpio command line. _________________________________________________________________________ If you install the SCO OpenServer Development System on the server and you want to support network installations of the Application Development Libraries and Linker, log in as root and enter these commands: cd / mount -r /dev/cd0 /mnt cpio -idumvI /mnt/opt/archives/VOL.000.002 "opt/P/SCO/odslite/*" netisl server on umount /mnt For further information, see Chapter 19, ``Installing and managing software over the network'' in the Networking Guide and ``Network installation adapters'' in SCO OpenServer Features and Limitations online. Installation limitations and workarounds These notes supplement or correct the installation instructions in ``Installing or upgrading an SCO system'' in the SCO OpenServer Handbook. _________________________________________________________________________ NOTE Before you install any new system software, back up your current system and verify that the backup was successful. See ``Running unscheduled filesystem backups'' in the System Administration Guide for more information. Resolving installation problems requires you to be familiar with the hardware configuration information displayed when your system boots. If the hardware boot information scrolls by too quickly to see, use the isl.pause option to defbootstr to pause the installation. At the boot prompt, enter: defbootstr isl.pause For more information, see the boot(HW) manual page. _________________________________________________________________________ Licensing and registration Although you must license as well as install every SCO OpenServer product before you can use it, you should wait until you are confident your system is properly installed before registering it. When you register your system, you must supply the current SCO System ID. However, a new System ID is generated whenever you: + reformat the hard disk + change the partition layout If you perform one of these operations during re-installation, you must contact an SCO Registration Center to obtain a new Registration Key and repeat the registration process in the SCO OpenServer Handbook. For more information, see Chapter 6, ``Licensing and registering SCO products'' in the SCO OpenServer Handbook. SCO Software Support Library (SSL) articles #482659 and #482755 also describe commonly encountered licensing problems; see ``SCO Support and Online Information Services'' for information about accessing SSL articles. Boot-time loadable driver (BTLD) support Use link(HW) to overwrite Boot-Time Loadable Drivers (BTLDs); the ahslink functionality included in previous releases has been incorporated into link. Boot-Time Loadable Drivers (BTLDs) are drivers which can be link-edited into the SCO OpenServer system kernel during the booting process. The link-editing is done by link after the driver is loaded into memory (RAM), but before the kernel is started. A BTLD enables SCO OpenServer to be installed either onto, or using, new hardware as soon as a driver for the hardware is available. SCO OpenServer supports installations using BTLDs for hard disk and tape controllers. _________________________________________________________________________ NOTE The Sjk and mc drivers are not boot-time loadable. _________________________________________________________________________ With certain BTLDs, the installation will stop and prompt you for BTLD configuration towards the end of the installation before proceeding. On some Compaq(r) models, you must boot from the boot floppy to load a BTLD. If you boot from the hard disk, the BTLD installation will fail. Installing from a serial console To install SCO OpenServer from a serial console onto a machine that does not have a video adapter, the required settings are 9600 baud, 8 data bits, one stop bit, and direct connect (usually to com1). Ignore initial reboot system dump warning After installation, you might get a warning during initial reboot that a system dump exists in the swap space. This warning can be safely ignored; you do not need to save the system dump. IBM Microchannel systems require bootstring If you have an IBM(r) Microchannel(TM) system and the primary hard disk is a SCSI drive with a capacity greater than 1GB, you need to specify the biosgeom bootstring at the boot prompt as follows: biosgeom defbootstr This ensures that the contents of the disk are interpreted correctly by both the hardware and the software. If you do not specify biosgeom during installation, or at a subsequent boot from the hard disk, the installation will appear to be successful, but you will not be able to boot the system from the hard disk. See boot(HW) for more information. NCR Microchannel systems using NCR 77C22 or 77C22E video chip If you have an NCR(r) Microchannel(r) System with an NCR 77C22 or 77C22E video chip integrated on the motherboard, select the IBM VGA 640x480 with 16 colors setting during installation. After the installation completes, run the Video Configuration Manager (or scoadmin video at the command line) in character mode and then select NCR VGA. NCR VGA automatically detects which video chip is installed on the motherboard. _________________________________________________________________________ NOTE During installation, you will see the error: VGA MAP_CLASS failed ... You can safely ignore this error message, which denotes a recognition problem of the NCR chipset. _________________________________________________________________________ If you have one of these chipsets, you must always run the Video Configuration Manager in character mode after initial installation. Your NCR chipset might not be recognized properly in graphical mode. Use ATI and Diamond DOS setup programs for higher graphics resolution To access resolutions higher than 640x480 and to correctly initialize certain ATI and Diamond adapters, you must boot DOS and run the manufacturer-supplied programs according to the instructions for those programs. This applies to the ATI Ultra Pro, Ultra Plus, and Mach64 graphics adapters, and the Diamond SpeedStar Pro, Stealth 24, and Stealth Pro graphics adapters. Compaq Proliant slow when booting from floppy disk The Compaq Proliant might run very slowly when booting from a floppy disk. To avoid this, set the System Configuration -> Power-On Defaults -> Set Power-On Speed option in the EISA Configuration program to ``High'' rather than ``Auto''. (The EISA Configuration program is the utility used to configure the EISA bus cards in the machine. All EISA bus machines are shipped with a utility to do this. Compaq normally ships its version on the SmartStart CD-ROM.) Installing Compaq IDA devices on non-Compaq platforms The Compaq IDA driver checks the system BIOS to verify that it is on a Compaq system. If you use Compaq IDA hardware on non-Compaq platforms, you must add ida.nocheck to your install bootstring or the driver will not function. See bootstring(HW) for more information. After the installation is complete, you must also add this bootstring to the /etc/default/boot file. See boot(HW) for more information. Installing on a machine with multiple host adapters If your system contains more than one type of host adapter, SCO OpenServer might find the secondary adapter first and assume it is the controller for the root disk. In this case, Upgrade might not be offered as an option for Installation type. If this happens, restart the installation and specify the location of your root hard disk at the Boot prompt. For example, if the root disk is at ID 0 on the first bus of an Adaptec 294x host adapter, enter the following at the boot prompt: defbootstr Sdsk=alad(0,0,0,0) If the root disk is on a second adapter of the same type, enter the following: defbootstr Sdsk=alad(1,0,0,0) If you have a different SCSI host adapter, use the appropriate driver name from the following table instead of alad: ____________________________________________________________________ Host adapter Driver name ____________________________________________________________________ Adaptec 151x, 152x (6260 & 6360 Chip) smad Adaptec 154x, 164x, 174x (Standard mode) ad Adaptec 174x (Enhanced mode) eiad Adaptec 274x (7770 Chip) arad Adaptec 292x, Future Domain 16x0, 600, 700 (18x0 Chip) fdhb Adaptec 294x (7870 & 7880 Chip) alad Advanced Micro Devices PCscsi ams BusLogic MultiMaster Adapters blc BusLogic 93x FlashPoint Adapters flashpt Corollary 386/486 CBUS SCSI-CPU ciha DPT SCSI & RAID Host Adapters dptr Enhanced IDE, ATAPI Interface (for tapes and CD-ROMs) wd Future Domain (formerly Western Digital) 7000 wdha Future Domain (formerly Western Digital) 7000EX wdex Future Domain 845, 850, 860, 885 (950 Chip) tmcha IBM HardFile Host Adapters hf Mylex Disk Array Controller mdac NCR Microchannel Systems Host Adapters ncr Olivetti ESC-1, ESC-2, and EFP Adapters efp Storage Plus SCSI-AT (SUMO) sumo Symbios Logic (formerly NCR MPD) 53c8xx Host Adapters slha Tricord Intelligent I/O Processor iiop See the boot(HW) and bootstring(HW) manual pages and ``Using bootstrings'' in the SCO OpenServer Handbook for more information. Wangtek 5150ES SCSI tape drive with SCSI hard disk installation failure If your system is configured with both a Wangtek 5150ES SCSI tape drive (with Firmware Versions FA03 or FA23) and a SCSI hard disk on an Adaptec 7870 chipset device (controlled by the alad driver), the installation procedure might fail when the tape is accessed to transfer files to the hard disk. To prevent this problem, use the Adaptec SCSI Select BIOS configuration to disable the SCSI bus parity checking. This solution is not known to work in all cases. The problem has been corrected in the most recent version of the firmware. Wangtek QIC-80 cartridge tape drives mkdev(ADM) incorrectly creates device nodes for this device with minor numbers 1 and 129. These should be deleted and replaced with minor numbers 5 and 9 respectively using mknod(C). Running badtrk with CIHA SCSI adapters When using badtrk(ADM) to lock out defective disk blocks, you can choose to use the target device's defect management or the SCO OpenServer system's own defect management. If the SCSI host adapter controlling the defective disk is a Corollary Integrated Host Adapter (CIHA), you must choose the target device's defect management to prevent file corruption. To access this badtrk option, you must select the Interactive fdisk/divvy disk setup option during installation. Not running badtrk during installation If you choose not to run badtrk during installation, no space is reserved for the defect list maintained by the operating system. This means that on non-SCSI disks, you will not to be able to map any bad blocks found in this partition and for SCSI disks you will only be able to use the device-maintained defect list. DPT PM 2022 SCSI Disk Controller SCO OpenServer installs correctly on a DPT PM2022 with SmartROM BIOS 2B and Firmware FW-0230-005E-E/O, but the kernel reboot fails. You can prevent this by upgrading to SmartROM BIOS 2.D1 and Firmware FW- 0230-005E-E/O, which is the current release of the Firmware as of this writing. The SCO OpenServer system is known to work correctly on the DPT PM2122 with SmartROM BIOS 2D and Firmware FW-0215-005E, which is the current Firmware as of this writing. ISA bus support disabled for DPT SCSI host adapters Default ISA bus support for DPT SCSI host adapters has been removed for this SCO OpenServer release. To re-enable ISA support for DPT SCSI devices, add dptr.isa=1 to the installation bootstring. See bootstring(HW) for more information. The installation will update the driver configuration files, so you do not need to add the bootstring to your default boot file. Do not set the installation CD-ROM or tape drive SCSI ID higher than 7 SCO OpenServer does not support CD-ROMs or tape drives which have SCSI IDs set to a value greater than 7 for installation. IDs greater than 7 are supported after installation on wide SCSI adapters. Obsolete tape drives Selections for Emerald, Mountain, and Everex cartridge tape drives are provided in mkdev tape for backwards compatibility only. These drives are no longer supported; in particular, they cannot be used for installations. Future Domain flopticals 21MB disks cannot be used as boot devices or removable hard disks. Adaptec Arrow SCSI chip sets Intermittent disk errors occur on 284x cards. This will be fixed in a future release. Adaptec 154x series clone devices Adaptec 154x clone devices might not install properly using the ad(HW) driver. If you encounter problems, add ad.nocheck to your bootstring so that the device can be recognized. See bootstring(HW) for more information. Some Adaptec 154x clone devices might also be recognized by the BusLogic driver. In this case, disable the blc driver by adding disable=blc to your bootstring. This does not apply to BusLogic MultiMastering devices using the blc driver. SMC 8432/8434 EtherPower PCI network adapters Standard Microsystems SMC 8432 and 8434 EtherPower PCI Ethernet Adapters do not auto-detect properly for BNC connectors. You must explicitly select BNC in the Advanced Options window. Configuring mice on laptops When configuring internal mice on most laptops, select Keyboard mouse when prompted for the mouse type. Choosing between MMDF and sendmail At installation, you can choose between two Mail Transfer Agents (MTAs) provided with SCO systems, mmdf(ADM) and sendmail(ADMN). The default MTA is MMDF, but we recommend sendmail to take full advantage of Internet FastStart mail capabilities; in particular, MMDF does not support e-mail with virtual domains. For more information on the benefits of each MTA, see ``Comparison of sendmail with MMDF'' and ``Changing Mail Transfer Agents'' in the Mail and Messaging Guide. _________________________________________________________________________ NOTE sendmail" does not support maildelivery(F) (except for vacation) and mail notification in scocal(XC). _________________________________________________________________________ See also: + the printed book SCO OpenServer Internet Services + Chapter 1, ``Using and administering electronic mail'' in the Mail and Messaging Guide Chapter 2 Read this after installation After installation, but before further configuring your system, read these important notes: + System configuration + Hardware configuration + Software configuration System configuration Software Manager exits abnormally if you cancel too early The Software Manager and custom(ADM) exit abnormally if you use: Software -> Examine -> Files and then start and cancel an installation or removal procedure before the progress window is displayed. To examine the files in a given software package after encountering this problem, exit and restart the Software Manager. Remote administration To administer systems across the network with SCOadmin, you must configure your system appropriately. See ``Configuring remote administration'' in SCO OpenServer Features and Limitations online for more information. Verification discrepancies Immediately after installation, the Verify Software and Verify System options in the Software menu of the Software Manager will show some discrepancies, as will the command-line equivalent, custom -v verify_type. In particular, the files listed below are intended to be symbolic links, but become real files after installation because the symbolic links are broken by the installation process: /etc/passwd /etc/shadow /etc/group /etc/default/scsihas /tcb/files/auth/m/mmdf /tcb/files/auth/r/root The file /usr/spool/lp/model/pciremote has the wrong mode and group ID. The following custom verification discrepancy may be displayed: /opt/K/SCO/Unix/5.0.2Do/.softmgmt/var wrong uid These discrepancies are expected and you will be prompted to correct these, which you should do immediately. See Chapter 4, ``Installing and managing software components'' in the SCO OpenServer Handbook for more information. find -mount not reporting mount points When cpio(C) is used in conjunction with the -mount option to find(C) on the root filesystem, mount points are not backed up. This is because -mount skips mounted filesystems. Unless these filesystems are unmounted, the mount points are skipped as well. When restoring the root filesystem, you may need to recreate the mount points manually before restoring the filesystems associated with them. For example, after you restore the root filesystem, you may need to create the /stand directory before restoring your backup of the boot filesystem. _________________________________________________________________________ NOTE The Backup Manager takes this behavior into account and automatically re-creates mount points as needed. _________________________________________________________________________ No root filesystem shown under divvy If your previous system had only a root filesystem, and you selected the Preserve hard disk setup option for the SCO OpenServer installation, running divvy(ADM) afterwards shows these unexpected results: + no filesystem is named ``root'' + the root filesystem is named ``boot'' + EAFS is the filesystem type for the swap division These results do not indicate problems with the hard disk setup. The root filesystem and the swap division are still valid. PPP Manager does not configure the PPP driver The PPP Manager does not add the PPP driver to the link kit. To work around this problem, configure your WAN device and protocol stack with the Network Configuration Manager, then use the either the Network Configuration Manager or the PPP Manager to configure PPP. For more information, see Chapter 1, ``Configuring network connections'' in Configuring Network Connections and ``Configuring PPP'' in the Networking Guide. scologin now uses authorization To avoid potential security problems, scologin(XC) now uses authorization by default to control X display access. To turn off authorization, edit the /usr/lib/X11/scologin/Xconfig file and set the authorize resource to false: DisplayManager*authorize: false See also: + ``Granting access to specific accounts'' in the Graphical Environment Guide + the scologin(XC) manual page Floppy drive I/O errors If you receive I/O errors when accessing the floppy drive on high- activity machines and you know the floppy media is sound, your system might be sending data faster than the floppy drive can process it. You can remedy this problem by enabling FIFO buffering for the floppy device. To do so, edit the /etc/conf/pack.d/fd/space.c file and reset these variables from their initial value of 0: fd_enable_FIFO Set to 1 to enable FIFO buffering. fd_FIFOthresh Set the buffer threshold (in bytes) to a sufficiently high value for your system; the range is 1-15. We recommend setting the value to 13 for most Pentium processors, although you may have to experiment to find the appropriate value for your system. See also: + Configuring the system for additional users and CPUs + Using documentation servers + Configuring the kernel to enable SUDS + Configuring multi-byte support Configuring the system for additional users and CPUs When you add users to your SCO OpenServer system, the demand on various system resources increases. When you license additional users with the License Manager, it prompts you, just before exiting, to tune kernel resources to accommodate the higher demand. We strongly recommend that you allow the License Manager to tune the resources for you. Once the resources are tuned, the License Manager prompts you to relink the kernel. Relinking the kernel at this point ensures that the modifications are saved. To activate the modified kernel, reboot the system. _________________________________________________________________________ NOTE When you add SCO User Licenses, the License Manager tunes a basic set of kernel resources. Refer to the Performance Guide for detailed information on tuning the kernel to match the needs of your particular system configuration. When you remove SCO User Licenses, the License Manager does not tune the kernel to reflect the change in demand on system resources. _________________________________________________________________________ When you license or unlicense one or more additional CPUs, the License Manager modifies the MAXACPUS kernel parameter automatically. Therefore, before exiting, the License Manager prompts you to relink the kernel. Relinking the kernel at this point ensures that the required modification is saved. To activate the modified kernel, reboot the system. _________________________________________________________________________ WARNING If you have installed SCO Symmetrical Multiprocessing Support, and any additional CPUs are licensed, all additional CPUs must be licensed at the same time. Failure to do so might cause some systems to hang when you reboot. _________________________________________________________________________ License Manager and kernel parameters When new user licenses are added to the system, the License Manager adjusts the following kernel parameters according to the number of users: + serial I/O parameters: NCLIST, TTHOG + Streams memory parameters: NSTREAM, NMUXLINK, NSTREVENT, NSTRPAGES + number of Stream pipe connections: NUMSP + number of pseudo-ttys: NSPTTYS + number of TCP/IP and UNIX domain sockets: NSOCKET, NUSOCOTS If your system is licensed for more than 5 users and you did not use the License Manager to add the user licenses, you may need to modify these parameters manually. See ``Configuration tools'' in the Performance Guide for more information. The License Manager also increments the MAXACPUS kernel parameter when additional CPUs are added, so you might need to modify this parameter if you failed to run the License Manager. (The base processor is not included in the count of CPUs.) Using documentation servers If you intend to use a remote documentation server, you must: + Complete the procedures in ``Configuring a help document server system'' in the Networking Guide. + Modify the Services object activate script (/usr/lib/X11/IXI/XDesktop/tools/Accessories.ts/Services.obj/activate) and the window manager configuration file (/usr/lib/X11/system.pmwmrc if you are using pmwm mode, or /usr/lib/X11/system.mwmrc for mwm mode) to refer to the name of the documentation server instead of localhost. For example, if your documentation is located on a server called scotty, you would change the following line in the Services object activate script: scohelp 'http://localhost/SCO_SERVICES/CONTENTS.html.Z' & to: scohelp 'http://scotty:457/SCO_SERVICES/CONTENTS.html.Z' & Similarly, for the window manager configuration file, you would change: f.exec "/usr/bin/X11/scohelp http://localhost/XPanHelp/CONTENTS.html" to: f.exec "/usr/bin/X11/scohelp http://scotty:457/XPanHelp/CONTENTS.html" Configuring the kernel to enable SUDS The SUDS (Software Update for Database Systems) driver that is needed by the SUDS library is configured into the kernel by default when you select the Database services initial system profile during installation; see ``Installation and upgrade checklist'' in the SCO OpenServer Handbook. If you want to use the SUDS library or use an application that has been linked with the library and you did not configure Database services at installation, follow this procedure. If you are unsure whether an application requires this, refer to the documentation provided with that application. 1. Log in as root. 2. Enable the SUDS driver by editing the /etc/conf/sdevice.d/suds file, and changing the N in the second field to a Y. 3. Use mkdev aio or the Hardware/Kernel Manager to enable support for asynchronous I/O and relink the kernel. To allow users to lock down memory for use with this type of I/O, update the aiomemlock(F) file should be updated to include the names of users that can use AIO and the maximum amounts of memory they can lock down. Many applications use setuid on their binaries so that you only need to specify a single user. Refer to the documentation provided with the application to see if this is the case for your application. Once you complete this process, reboot the system to take account of the new kernel and the memory locking privileges that have been assigned to particular users. 4. The process and thread synchronization primitives supported by SUDS can require users of these features to be authorized by the system administrator. This is achieved by assigning all such users to a particular group(s) and giving that group the necessary privileges with the suds_ctrl(ADM) command. This process can be made automatic by including the suds_ctrl command in an appropriate rc2.d(ADM) script. 5. Certain database applications require the administrator to also configure the database for use with SUDS or asynchronous I/O. This should be described by the documentation provided with the application. 6. You must shut down the system and reboot for the changes to take effect. Configuring multi-byte support SCO OpenServer includes multi-byte support for Asian locales. It is implemented in: + multi-byte clients, formerly available in the EUC (Extended UNIX Coding) Supplement + language-specific supplements, which include: - multi-byte locales - messaging files - input method server and client - X11 Codeset and Compose files - app-defaults files This release of SCO OpenServer includes new multi-byte clients in the /usr/bin/euc directory: + ksh + scocal + scohelp + scomail + sed + vi _________________________________________________________________________ NOTE These multi-byte clients are in a separate directory from their single-byte counterparts. You must therefore add /usr/bin/euc to your path to use these clients. Single- and multi-byte functionality for these clients will be integrated in a later release. Multi-byte clients have not been extensively tested. _________________________________________________________________________ To enable these clients, you must install a language supplement specific to the desired locale; contact your SCO distributor for more information. Hardware configuration scologin problems on Unisys MPE-46651 systems Your MPE-46651 system may hang during SCOlogin start and stop operation. If it does, set the variable kdm_doinb to 1 in /etc/conf/pack.d/kbmouse/space.c, relink the kernel, and reboot. Use Video Configuration Manager for full graphical functionality During initial installation, the following adapters default to IBM VGA 640x480 16-color: + Appian Rendition III + Imagraph ITX + Microfield I8 + NCR VGA + Number 9 GXi To get the full functionality of your adapter, use the Video Configuration Manager after completing the installation. PCI adapters requiring interrupts should not have disabled interrupt line Certain computers (in particular, some DEC models) have the ability to disable interrupts in the PCI BIOS. If an adapter is recognized but does not seem to be working properly, you can determine whether this is a problem by running hwconfig(C) and examining the output for the adapter. If the output contains the string vec=255, re-enable interrupts using your computer's hardware setup program. This does not apply to PCI adapters that do not require interrupts, such as graphics adapters. Use full device names to format floppy disks When you format floppy disks, you cannot specify the abbreviated device names /dev/rfd0 and /dev/rfd1. Use the full device names that specify disk density. For example, use /dev/rfd0135ds18 for the primary 3.5-inch floppy disk drive. Keyboard selections If you change the keyboard setting from the default during initial installation, your system might not be fully configured for the language you selected. Use the International Settings Manager to reconfigure the keyboard selection after installation if necessary. Do not connect or disconnect keyboard mouse on a running system Do not connect or disconnect a keyboard (PS/2-style) mouse on a running SCO OpenServer system, as this might cause damage to hardware on some systems. Always turn off the system before connecting or disconnecting a keyboard mouse. Software configuration Context-sensitive help and online documentation Context-sensitive help and online documentation for any given technology is normally included as a documentation package within that technology. If you choose not to install or subsequently remove the documentation package, you will not have access to help or online documentation for that technology. Online documentation for some technologies is bundled with a related technology. Therefore, if you choose not to install a documentation package or remove one later, you might also be removing the online documentation for another, related technology. The online help for scohelp(XC) (Help on Help) is available only if the Graphics documentation package is installed. If third-party software does not install, change rel= value If a third-party software product will not install because the base operating system (or a component of it) is the wrong release, change the rel= value in the appropriate perms file from rel=5.0.4 to rel=3.2.4. This is because some custom-installed third-party products check this value before allowing the installation to proceed. Check with the software vendor before trying this, as certain packages are kernel-dependent. You must change the line back to rel=5.0.4 after installing the software product. Ignore netconfig message at end of NFS installation The netconfig utility runs automatically when NFS(r) is installed on SCO OpenServer systems. Disregard the screen message at the end of the installation script that directs you to run it again. See also: + Installing and configuring Internet FastStart + Installing and configuring IPX/SPX + Installing and configuring PC-Interface + Installing and configuring SCO Gateway for NetWare + Installing WordPerfect 6.0 Installing and configuring Internet FastStart Before installing Internet FastStart, familiarize yourself with the updates and known limitations listed in the printed SCO OpenServer Internet Services. Installing and configuring IPX/SPX IPX/SPX(TM) is provided with SCO OpenServer, and is installed when you select a full installation of the Connectivity component during installation. IPX/SPX can be configured either during installation or after installation (by running the Network Configuration Manager to add the IPX/SPX stack to an existing or new networking card). _________________________________________________________________________ NOTE The context-sensitive help and online documentation for IPX/SPX are part of the networking documentation bundled with TCP/IP. You must therefore install the documentation package of TCP/IP to get context-sensitive help and online documentation for IPX/SPX. _________________________________________________________________________ For system installation instructions, see Chapter 2, ``Installing or upgrading an SCO system'' in the SCO OpenServer Handbook. For information on the Network Configuration Manager, see ``Configuring protocols'' in Configuring Network Connections. Installing the DOS component of IPX/SPX The DOS binary NVT.EXE has been updated to provide support for Windows 95(r) and Windows NT(r) clients. NVT.EXE must be installed from a floppy. An image of the required DOS floppy is stored on the install CD-ROM. To create the floppy, follow these steps as root: 1. Label a floppy diskette ``IPX/SPX DOS Component'' and use format(C) to format the diskette. 2. Mount the CD: mount -r /dev/cd0 /mnt 3. Change to the directory where the image is stored: cd /mnt/images/ipxspx 4. Use dd(C) to copy the image to the formatted diskette: dd if=01 of=/dev/install bs=9k 5. Verify the sum of the diskette matches the sum stored in 01sum: sum -r /dev/install should have the same output as cat 01sum For further instructions, see ``Installing and using the DOS component'' in the Networking Guide. Terminal emulator products reported to work with IPX/SPX The following DOS terminal emulator products are reported to work with the SCO OpenServer version of IPX/SPX: _________________________________________________________________________ Vendor Product Terminal types _________________________________________________________________________ SCO TermVision(TM) SCO UNIX/XENIX Console (ANSI), wy60, vt52, vt100, vt220, vt320, vt420 JSB MultiView DeskTop, vt100, vt220, vt241, Version 4.2 SCO UNIX/XENIX Console (ANSI) Advanced S/W Tech AST-Cons, ansi, SCO color console Version 1.0 Century Software Tiny TERM, wy50, wy60, ansi, Versions 1.0.8, 1.0.10 vt52, vt100/102, vt220 DigiBoard DoubleVIEW, wy60, ansi, Version 1.3 vt100 (untested) Spry Inc. AIR for Windows ansi, vt100, vt220, wy52 U.A. Systems Smart Terminal ansi, esprit3, tvi925, vt100, wy50, wy350 Walker, Richer, WRQ Reflection 2+, vt52, vt102, vt220, Quinn Inc. Version 4.13 vt300-7, vt300-8, vt320 _________________________________________________________________________ NOTE SCO recommends ``ansi'' terminal emulation as the preferred mode of operation. Terminal emulators must support the INT14 or 6B capability. _________________________________________________________________________ An up-to-date list of terminal emulation products is available from SCO Support Services. Installing and configuring PC-Interface See also the PC-Interface Guide, which contains detailed information on administering and using PC-Interface(TM). _________________________________________________________________________ NOTE PC-Interface provides print, file, terminal emulation, and other services from SCO OpenServer systems to DOS, Windows, or OS/2(r) systems. Corresponding client software is required to access these services and is provided by Platinum Technology. For more information, visit their WWW site at: http://www.platinum.com _________________________________________________________________________ System requirements To install and run the PC-Interface server, you need: + Any appropriate computer running the SCO OpenServer Enterprise System. TCP/IP networking software is required if you plan to provide LAN services to PC-Interface clients. + PC-Interface software installed on each client computer. + A minimum of 2.8MB of disk space in /usr. + Cabling to the LAN (if you plan to offer LAN services). + Cabling to each computer that is to be connected for RS-232 service. Each computer requires its own serial port on the server. If you are using routers on your network, see ``Modifying routers to handle PC-Interface broadcasts'' in the PC-Interface Guide. Installing the PC-Interface server The PC-Interface server is automatically installed during a full SCO OpenServer installation. If you did not initially perform a full installation and want to install PC-Interface, use the Software Manager to install PC-Interface from the SCO OpenServer Connectivity package. _________________________________________________________________________ NOTE If a previous version of the PC-Interface server exists on your system, remove it with Software Manager before installing a new version. _________________________________________________________________________ See ``Installing software'' in the SCO OpenServer Handbook. Configuration and tuning You can configure and tune your SCO OpenServer system for the PC- Interface server using the configure program as root. For complete information, see the configure(ADM) manual page and the Performance Guide. _________________________________________________________________________ NOTE After modifying any of the values shown in the following tables, you must relink the kernel and reboot the system to implement the changes or the modified configuration will not properly reflect the actual system. _________________________________________________________________________ Two sets of values are given in the tables, one for RS-232-only systems and one for RS-232 and LAN systems. The values given should be added to your current values; they should not replace them. When using configure, first select the section to which the configurable parameter belong. Then, select the new values for each parameter. The parameters to change for the PC-Interface server are outlined below, along with the sections in which they belong. For servers providing RS-232 services only: _________________________________________________________________________ Section Variable 1-16 User 17-32 User 33-64 User _________________________________________________________________________ Semaphores SEMMNI + 20 + 40 + 80 Semaphores SEMMNU + 40 + 80 + 160 Shared Data SHMMNI + 20 + 40 + 80 For servers providing LAN and RS-232 service: _________________________________________________________________________ Section Variable 1-16 User 17-32 User 33-64 User _________________________________________________________________________ Semaphores SEMMNI + 20 + 40 + 80 Semaphores SEMMNU + 40 + 80 + 160 Shared Data SHMMNI + 20 + 40 + 80 Streams Data NSTREAM + 20 + 40 + 80 Streams Data NUMTIM + 20 + 40 + 80 Local configuration using environ To perform configuration specific to the PC-Interface server, modify the environ file in /usr/pci/bin/environ. This Bourne shell script is invoked when the pcistart script is run and whenever an RS-232 user logs in for file service. See ``Configuring the server environment'' in the PC-Interface Guide for a description of the environment variables that you can set in this file. Network configuration PC-Interface makes use of whatever name resolution procedure is in use on your system. For information on setting up the Domain Name Service (DNS) on your PC-Interface server, see Chapter 6, ``Configuring the Domain Name Service'' in the Networking Guide. Configuring pseudo-tty ports By default, the LAN version of the PC-Interface server is configured with six terminal emulation ports. Two RS-232 ports are configured. To add or delete terminal emulation ports for PC-Interface users, see ``Procedure for enabling and disabling ports'' in the PC-Interface Guide. Starting and stopping the server When the SCO OpenServer system enters multiuser mode, it runs the script /etc/rc2.d/S95pci. This program verifies some aspects of your SCO OpenServer system and invokes pcistart. For more information, see the pcistart(PCI) manual page. When the SCO OpenServer system shuts down, it runs the script /etc/rc0.d/K95pci. This script shuts down the PC-Interface server in an orderly fashion. root can manually stop the PC-Interface server with the pcistop script at any time. However, because of system-required security, you cannot restart the PC-Interface server without rebooting the system. Installing and configuring SCO Gateway for NetWare See also the Guide to Gateways for LAN Servers, which contains detailed information on administering and using SCO(r) Gateway for NetWare(r). System requirements To install and run SCO Gateway for NetWare, you need: + One or more NetWare file servers (and, optionally, print servers) to connect to. Each must run NetWare Version 2.2, 3.11, 3.12, 4.01, 4.02, or 4.1, and should have the NetWare Loadable Module (NLM) installed and running where appropriate. See ``Installing and configuring the NetWare component of SCO Gateway for NetWare'' for more information. + The SCO OpenServer system on which IPX/SPX is configured. + Networking cards and cabling to connect the SCO OpenServer system to a LAN. Configuring the UNIX component of SCO Gateway for NetWare SCO Gateway for NetWare is automatically configured over IPX/SPX during a Fresh installation when both IPX/SPX and SCO Gateway for NetWare are installed and IPX/SPX configuration information is supplied. For all other scenarios, follow the instructions below. Use the Network Configuration Manager to configure SCO Gateway for NetWare over IPX/SPX: 1. As root, enter scoadmin Network Configuration Manager. 2. Select the adapter already configured for use with IPX/SPX, to which you want to add SCO Gateway for NetWare. 3. Select Add protocol from the Protocol menu. 4. Select ``SCO Gateway for NetWare'' and click on Add. 5. When prompted, click on Yes to relink the kernel. Answer yes to the following two kernel questions. 6. Reboot your system. Installing and configuring the NetWare component of SCO Gateway for NetWare In general, NetWare file servers do not understand most UNIX filesystem operations. However, an NLM (NetWare Loadable Module) is provided that adds UNIX filesystem semantics to NetWare Version 3.11, 3.12, 4.01, or 4.02 file servers. If you have such a server, you should install this NLM on your file server. If you do not, you will only get DOS file semantics after mounting the filesystem. For more information on installing and using these NLMs, see ``NetWare Loadable Modules'' in the Guide to Gateways for LAN Servers. Adding and removing SCO Gateway for NetWare printers Use the Printer Manager to add and remove SCO Gateway for NetWare printers. See ``Adding a SCO Gateway for NetWare printer'' and ``Removing a SCO Gateway for NetWare printer'' in the Guide to Gateways for LAN Servers. Installing NetWare Loadable Modules (NLMs) on NetWare The new NUC.NLM for NetWare 4.x is now supported. _________________________________________________________________________ NOTE The installation procedure for these new NLMs differs considerably from the procedure for earlier versions. The UNISTART.NCF file must now specifically name each volume you want to load. In addition, extra steps are required to load the NLMs on a 3.11 or 4.x NetWare server. _________________________________________________________________________ The NUC and NFS NLMs run on NetWare versions 3 and greater. When a NetWare filesystem is mounted from a UNIX system, the loaded NUC and NFS NLMs give the NetWare filesystem UNIX semantics such as long filenames, mixed case letters in filenames, symbolic links, and support for owners and groups. To take advantage of these features, install the NLMs on all NetWare file servers version 3 and above, that will be mounted by an SCO OpenServer system running the SCO Gateway for NetWare. Ensure that the SCO Gateway for NetWare is installed on the UNIX system before proceeding. Step 1: 3.11 only: Install NetWare patch and load other NLMs If you are installing on NetWare 3.11, you must install a server patch. The patch is available from ftp.novell.com, as /pub/updates/nwos/nw312/libup5.exe. After installing the patch, and before installing the new NLMs, enter: load nwsnut load bcastlib You might see the message: unable to find load file BCASTLIB. This message can safely be ignored. If you see it, however, you will also see the message: Could not load module PKERNEL for configuration during step 4. This message may also safely be ignored; press to continue. The missing bcastlib NLM file will then be installed on your system. Step 2: Cut two floppy disks containing the NLMs The NLMs must be installed from two floppies. Images of the required DOS floppies were stored on the SCO OpenServer CD-ROM, in the /images/nuc directory. Copy the images to two double-sided, high density, 3.5-inch floppy disks. Step 3: Copy NLMs from the floppies to the NetWare file server 1. From the NetWare server, press simultaneously to start the Current Screens menu. This menu displays the currently loaded options. Start the Install Screen option in one of two ways: + If Install Screen is on the menu, select the number corresponding to it. + If Install Screen is not available on the menu, you must load it. Select the number corresponding to System Console. At the System Console prompt (:) enter load install. 2. From the Installation Options menu, select Product Options. 3. When the Currently Installed Products window appears, press . 4. Insert the first NLM floppy in the NetWare server floppy drive. 5. At the prompt, select the drive in one of two ways: + To select the displayed default drive, press . + To select another drive, over the default drive and enter the drive letter, followed by ``:''. Then, press . 6. At the prompt, select the drive you are using to boot NetWare. The most common choices are drive A: for the 3.5-inch floppy drive and drive C: for the hard drive. Select the drive in one of two ways: + To select the displayed default drive, press . + To select another drive, over the default drive and enter the drive letter, followed by ``:''. Then press . 7. If you are booting the NetWare server from a floppy disk, the system prompts for the volume name of the NetWare boot floppy. After you enter the volume name, the system prompts you to insert the NLM floppies and the boot floppy disk several times to transfer the required data. Step 4: Add UNIX name space support to NetWare volumes To add UNIX filesystem name space to NetWare volumes, you must reserve space on the volumes that will be mounted by UNIX clients to hold the extra UNIX filesystem semantic information. From the NetWare file server: 1. If you are not already at the Current Screens menu, press simultaneously to start the Current Screens menu. 2. Select the number corresponding to System Console. 3. At the system console prompt (:) enter: load nfs add name space nfs to volume volume_name where volume_name is the name of the NetWare volume to be mounted. This takes several minutes. During this time, you are informed of disk space requirements for this operation. 4. Repeat the add name space nfs to volume volume_name command for each NetWare volume that requires UNIX filesystem semantics. The commands load nfs and add name space are done once per NUC NLM installation. These commands do not need to be added to AUTOEXEC.NCF. Step 5: Edit the NFSUSERS, NFSGROUP, and PASSWD files 1. Log in to the NetWare server as supervisor. 2. Create the group EVERYONE on NetWare if it does not already exist. Add all users to this group. This facilitates an automatic mapping between the UNIX system others category and the NetWare EVERYONE group. 3. Edit the SYS:\ETC\NFSUSERS and SYS:\ETC\NFSGROUP files, which were created when the NLMs were installed. The NFSUSERS file contains lines with the format: UnixUid NetWareLogin and the NFSGROUP file contain lines with the format: UnixGid NetWareGroup UnixUid is the UNIX system user identification number NetWareLogin is the NetWare login name UnixGid is the UNIX system group identification number NetWareGroup is the NetWare group name Add entries for all the UNIX system users and groups that will to use the NetWare file server. 4. Update the SYS:\ETC\PASSWD file to contain entries identical to those in the /etc/passwd file on the UNIX system. Step 6: Edit the UNISTART file Edit or create the file SYS:\SYSTEM\UNISTART.NCF. This file must contain the lines: load tsaproxy load nuc all If you want only some of your NetWare volumes to support NFS name space, you must name each one separately: load nuc volume_name_1 volume_name_2 _________________________________________________________________________ NOTE This is different from the previous installation procedure. The file may already contain the line load nuc. It must be changed to read load nuc all. _________________________________________________________________________ Step 7: 3.11 only: Add a first line to start bcastlib If you are installing on NetWare 3.11, add the following as the first line of the UNISTART file: load bcastlib Step 8: Edit the UNISTOP file Edit or create the file SYS:\SYSTEM\UNISTOP.NCF. This file must contain one unload line for each load line in UNISTART. For example: unload nuc Step 9: 4.x only: Load inetdb If you are installing on NetWare 4.x, run the command: load inetdb admin_login password where admin_login is the fully-qualified NDS administrative login for this server, and password is the password for this account. Run this command only once. It does not need to be repeated after subsequent reboots. Step 10: Start the NLM manually To start the NUC NLM now without rebooting: 1. Press simultaneously to start the Current Screens menu. 2. Select the number corresponding to System Console. 3. At the system console prompt (:), enter unistart. _________________________________________________________________________ NOTE To stop the NLM at any time, enter unistop at the system console prompt (:). _________________________________________________________________________ Step 11: Configure the system to start the NLM automatically To ensure the NLMs are started when the server is booted, edit the AUTOEXEC.NCF file. From the NetWare server: 1. Press simultaneously to start the Current Screens menu. This menu displays the currently loaded options. Start the Install Screen option in one of two ways: + If Install Screen is on the menu, select the number corresponding to it. + If Install Screen is not available on the menu, you must load it. Select the number corresponding to System Console. At the System Console prompt (:), enter load install. 2. Select System Options. 3. Select Edit AUTOEXEC.NCF. 4. Near the end of the AUTOEXEC.NCF file, add the command: unistart.ncf This should usually be placed just before the line with the load monitor command. 5. Delete the command load nuc if it is present in the file. 6. Press when done. 7. Select Yes to save the modified file or to cancel this edit. Step 12: 4.x only: Set up NDS mappings On NetWare 4.x, for the owner and group mappings to work, you must create NDS (NetWare Directory Services) users and groups for every user and group referenced. NDS users and groups are created using the NWADMIN command from a Windows client, or the NETADMIN command from a DOS client. Installing WordPerfect 6.0 To install WordPerfect(r) 6.0 from its CD-ROM: 1. Create a backup copy of the /etc/perms/rts file. 2. Edit /etc/perms/rts and change the line #rel=5.0.2xx (where xx is a combination of an uppercase and a lowercase letter) to #rel=3.2.4. 3. After you install WordPerfect 6.0, replace the modified /etc/perms/rts file with the original version saved to your backup copy. 4. Enter: echo "prd=unixos rel=3.2" >> /usr/lib/custom/history _________________________________________________________________________ WARNING Be careful to type ``>>'' and not ``>'' in this command. _________________________________________________________________________ 5. Follow the steps in the ``Loading WordPerfect from a CD-ROM'' section of the WordPerfect Version 6.0 Installation Guide for the X Window System for UNIX systems; however, replace the mount command shown with: mount -f ISO9660,lower /dev/cd0 /mnt 6. Continue the installation according to the WordPerfect instructions. _________________________________________________________________________ NOTE To avoid warnings during WordPerfect startup, set the LANG environment variable to a value with no suffix. For example, if LANG is set to C_C.C, change it to either C or C_C. See ``Understanding variables'' in the Operating System User's Guide for instructions. _________________________________________________________________________ These concerns only apply to WordPerfect 6.0. Later versions of the product will install as described in the WordPerfect documentation. (c)1983-1997 The Santa Cruz Operation, Inc. All rights reserved. This publication is protected under copyright laws and international treaties. (c)1992-1994 AT&T Global Information Solutions Company; (c)1987-1989 Computer Associates, Inc.; (c)1987 Convergent Technologies, Inc.; (c)1989 Digital Equipment Corporation; (c)1987-1989 Hewlett-Packard Company; (c)1993-1994 Platinum Technologies; (c)1988 Massachusetts Institute of Technology; (c)1985-1989 Metagraphics Software Corporation; (c)1980-1989 Microsoft Corporation; (c)1989 Open Software Foundation, Inc.; (c)1993-1994 Programmed Logic Corporation; (c)1994 Sun Microsystems, Inc.; (c)1988 UNIX Systems Laboratories, Inc. All rights reserved. Information in this document is subject to change without notice and does not represent a commitment on the part of The Santa Cruz Operation, Inc. SCO, The Santa Cruz Operation, the SCO logos, VP/ix, SCO OpenServer, UnixWare, dbXtra, Panner, SCO Global Access, SCO MPX, SCO Doctor, SCO Doctor for Networks, SCO Doctor Lite, SCO Premier Motif, SCO Visual Tcl, SCO VisionFS, SCO ToolWare, SCO TermLite, SCO Vision 97, SCO CIFS Bridge, SCO WebTop, The Internet Way of Computing, and IWoC are trademarks or registered trademarks of The Santa Cruz Operation, Inc. in the USA and other countries. IXI, X.desktop, Deskworks, Wintif, IXI Panorama, Deskterm, and IXI Desktop are trademarks or registered trademarks of IXI Limited, a subsidiary of The Santa Cruz Operation, Inc. Visionware, Devkit.Vision, Esprit, Kodon, Super.Vision, Visionware Super.Vision, Term.Vision, Visionware Direction, the Visionware logo, Visionware SQL-Retriever, and XVision are registered trademarks of Visionware Limited, a subsidiary of The Santa Cruz Operation, Inc. SuperVision, TermVision, X-Visionware, SQL-Retriever, and Vision Builder are trademarks of Visionware Limited. UNIX is a registered trademark in the United States and other countries, licensed exclusively through X/Open Company Limited. Cheyenne and ARCserve are registered trademarks of Cheyenne Software, Inc. Netscape, Netscape Navigator, Netscape Communications Server, Netscape Commerce Server, Netscape Proxy Server, Netscape FastTrack Server, Netscape Enterprise Server, Netscape SuiteSpot, Netscape Catalog Server, Netscape News Server, Netscape Mail Server, and Netscape Navigator Gold are trademarks of Netscape Communications Corporation. NFS was developed by Legent Corporation (formerly Lachman Associates, Inc.) based on LACHMAN SYSTEM V NFS. LACHMAN is a trademark of Legent Corporation. NFS is a trademark of Sun Microsystems, Inc. TCP/IP was developed by Legent Corporation (formerly Lachman Associates, Inc.) based on LACHMAN SYSTEM V STREAMS TCP, a joint development of Lachman Associates and Convergent Technologies. MPX was developed by Corollary, Inc. VP/ix is a product developed and licensed by Phoenix Technologies, Ltd/INTERACTIVE Systems Corporation. XRemote is a registered trademark of Network Computing Devices, Inc. Oracle is a registered trademark of Oracle Corporation, Redwood City, California. Java is a trademark of Sun Microsystems, Inc. All other brand and product names are or may be trademarks of, and are used to identify products or services of, their respective owners. The Santa Cruz Operation, Inc. and SCO Skunkware are not related to, affiliated with or licensed by the famous Lockheed Martin Skunk Works(r), the creator of the F-117 Stealth Fighter, SR-71, U-2, Venturestar(TM), Darkstar(TM), and other pioneering air and spacecraft. The SCO software that accompanies this publication is commercial computer software and, together with any related documentation, is subject to the restrictions on US Government use as set forth below. If this procurement is for a DOD agency, the following DFAR Restricted Rights Legend applies: RESTRICTED RIGHTS LEGEND: Use, duplication, or disclosure by the US Government is subject to restrictions as set forth in subparagraph (c)(1)(ii) of Rights in Technical Data and Computer Software Clause at DFARS 252.227-7013. Contractor/Manufacturer is The Santa Cruz Operation, Inc., 400 Encinal Street, Santa Cruz, CA 95060. If this procurement is for a civilian government agency, this FAR Restricted Rights Legend applies: RESTRICTED RIGHTS LEGEND: This computer software is submitted with restricted rights under Government Contract No. _________ (and Subcontract No. ________, if appropriate). It may not be used, reproduced, or disclosed by the Government except as provided in paragraph (g)(3)(i) of FAR Clause 52.227-14 alt III or as otherwise expressly stated in the contract. Contractor/Manufacturer is The Santa Cruz Operation, Inc., 400 Encinal Street, Santa Cruz, CA 95060. The copyrighted software that accompanies this publication is licensed to the End User only for use in strict accordance with the End User License Agreement, which should be read carefully before commencing use of the software. Document Version: 5.0.4 30 May 1997