#EDIR DATA#
DOCTYPE='BOOK' PUBLICID='' SYSTEMID='/dtd/docbook.dtd'NetWare 4.1 InstallationNetWare 4.1 InstallationNovell, Inc.DisclaimerNovell, Inc. makes no representations or warranties with
respect to the contents or use of this manual, and specifically
disclaims any express or implied warranties of merchantability or
fitness for any particular purpose. Further, Novell, Inc. reserves the
right to revise this publication and to make changes to its content,
at any time, without obligation to notify any person or entity of such
revisions or changes.Further, Novell, Inc. makes no representations or warranties
with respect to any NetWare software, and specifically disclaims any
express or implied warranties of merchantability or fitness for any
particular purpose. Further, Novell, Inc. reserves the right to make
changes to any and all parts of NetWare software, at any time, without
any obligation to notify any person or entity of such changes.TrademarksThe following are registered trademarks of Novell, Inc.: DR DOS, Fastpath, LAN WorkPlace, LANalyzer, NetWare, NetWare Name Service, Novell Press, UnixWare, WordPerfect.UNIX is a registered trademark of Novell, Inc. in the United States and other countries, licensed exclusively through X/Open Company, Ltd.The following are trademarks of Novell, Inc.: Advanced NetWare, Enterprise Certified NetWare Engineer, ECNE, EXOS, FirstMail, Global MHS, HSM, Hardware Specific Module, Hot Fix, IPX, IPX/SPX, IPXWAN, Internetwork Packet Exchange, LSL, Link Support Layer, MLI, MLID, MSL, MSM, MacIPX, MacNCP, MacNDS, Media Support Module, Mirrored Server Link, Multiple Link Interface, Multiple Link Interface Driver, NCP, NDR, NDS, NE/2, NE/2-32, NE1000, NE1500T, NE2000, NE2100, NE3200, NE32HUB, NLM, NLSP, NMS, NSE Pro, NTR2000, NVT, NetSync, NetWare 3, NetWare 4, NetWare 4.01, NetWare 4.1, NetWare Application Notes, NetWare Care, NetWare Client, NetWare Core Protocol, NetWare DOS Requester, NetWare Directory Services, NetWare Express, NetWare IPX Router, NetWare Link Services Protocol, NetWare Link/Frame Relay, NetWare Link/PPP, NetWare Link/X.25, NetWare Loadable Module, NetWare Logotype (teeth logo), NetWare MHS, NetWare Management Agent, NetWare Management System, NetWare Message Handling Service, NetWare MultiProtocol Router, NetWare Navigator, NetWare Peripheral Architecture, NetWare Ready, NetWare Requester, NetWare Runtime, NetWare SFT, NetWare SFT III, NetWare Tools, NetWare UAM, NetWare/IP, Netware Notify, Network Support Encyclopedia Professional Volume, Novell Labs, Novell Research Reports, Novell Virtual Terminal, ODI, Open Data-Link Interface, Packet Burst, Personal NetWare, RX-Net, RXNet/2, Red Box, SFT, SFT III, SMS, SPX, Sequenced Packet Exchange, Storage Management Services, Streams, TSM, Topology Specific Module, Transaction Tracking System, TTS, VLM, Virtual Loadable Module, "Yes, It Runs With NetWare Logo", and the "Yes, NetWare Tested and Approved Logo".The following are registered service marks of Novell, Inc.: Novell Technology Institute, NetWire.The following are service marks of Novell, Inc.: Novell Registry, Certified NetWare Administrator, CNA, Certified NetWare Engineer, CNE, Certified NetWare Instructor, CNI, Novell Authorized Service Center, NASC, Novell Technical Support.The following are collective marks of Novell, Inc.: Novell Authorized Reseller, Technical Support Alliance, TSA.3Com, 3+Share, and TokenLink are registered trademarks of 3Com Corporation.4.3BSD is a trademark of the Regents of University of California, Berkeley.ARCnet is a registered trademark of Datapoint Corporation.AT is a registered trademark of International Business Machines Corporation.AT&T is a registered trademark of American Telephone & Telegraph.Adobe and PostScript are registered trademarks of Adobe Systems Incorporated.Apple, AppleShare, AppleTalk, EtherTalk, ImageWriter, LaserWriter, LocalTalk, Macintosh, and MultiFinder are registered trademarks, and Finder and Mac are trademarks, of Apple Computer, Inc.Btrieve is a registered trademark of Btrieve Technologies, Inc.Canon is a registered trademark of Canon, Inc.COMPAQ is a registered trademark of COMPAQ Computer Corporation.Cisco Systems is a trademark of Cisco Systems, Inc.Citizen is a registered trademark of Tokei Kabushiki Kaisha.Claris is a trademark and MacWrite is a registered trademark of Claris Corporation.CompuServe is a registered trademark of CompuServe, Inc.DEC, DECnet, and Digital are trademarks of Digital Equipment Corporation.DeskJet, DeskWriter, LaserJet, PaintJet, PaintWriter, and PCL are registered trademarks of Hewlett-Packard Company.Diablo is a registered trademark of Xerox Corporation.DynaText is a registered trademark of Electronic Book Technologies, Inc.Epson is a registered trademark of Seiko Epson Corporation.EtherPrint is a trademark of 3Com Corporation.TokenPrint is a registered trademark of Dayna Communications.EtherFlex is a registered trademark of Extended Systems International.GatorBox is a registered trademark of Cayman Systems.Hewlett Packard, HP, HP-GL, LaserJet, and PCL are registered trademarks of Hewlett-Packard Company.Hayes is a registered trademark of Hayes Microcomputer Products, Inc.IBM, OS/2, Micro Channel, ProPrinter, and PS/2 are registered trademarks and AFP, Presentation Manager, and SAA are trademarks of International Business Machines Corporation.Intel is a registered trademark and Pentium is a trademark of Intel Corporation.LaserBridge is a registered trademark of Sonic Systems.Lotus is a registered trademark of Lotus Development Corporation.MS-DOS and Microsoft are registered trademarks and LAN Manager is a trademark of Microsoft Corporation.MacPlot is a registered trademark of Microspot.NEC, Spinwriter, and Pinwriter are registered trademarks of NEC Corporation.NFS is a registered trademark of Sun Microsystems, Inc.Okidata and MicroLine are registered trademarks of Oki Electric Industry Co., Ltd.PageMaker is a registered trademark of Aldus Corporation.Panasonic is a registered trademark of Panasonic Office Automation.PowerPrint is a trademark of GDT Softworks, Inc.SQL Server is a trademark of Sybase, Inc.SprintTalk is a registered trademark of Digital Products.Ultra is a trademark of Hayes Microcomputer Products, Inc.Unicode is a registered trademark of Transoft Ltd.Word is a registered trademark of Microsoft Corporation.XT is a trademark of International Business Machines Corporation.Xerox is a registered trademark and XNS is a trademark of Xerox Corporation.cc:Mail is a trademark of cc:Mail, a Division of Lotus.All other trademarks, service marks, certification marks, and
collective marks --- registered or not --- are the property of their
respective owners.Copyright Notices© Copyright 1983-1994 Novell, Inc. All rights reserved. No
part of this publication may be reproduced, photocopied, stored on a
retrieval system, or transmitted without the express written consent
of the publisher.TYPE="VERT"Novell, Inc.122 East 1700 SouthProvo, UT 84606U.S.A.User Comment FormNovell encourages and welcomes your feedback and suggestions on ways we can improve our manuals. You can help us by sharing your comments and suggestions about how our manuals could be made more useful to you, and about any inaccuracies or information gaps they contain.Submit your comments by printing this User Comment form (click on the icon to display the form, then select "Print" from the "File" menu), filling it in, then faxing or mailing it to us.LABEL="0" FLOAT="0"User Comment FormFILEREF="ucomment.tif"PAGENUM=7 ID="BP1"Your NetWare 4.1 DocumentationNetWare® 4.1 includes a complete set of DynaText* 
manuals, which are accessible from a NetWare client or standalone computer.LABEL="1" FLOAT="0"NetWare 4.1 Manuals OnlineFILEREF="n41in38a.tif"Your hard-copy manuals IDXID="w2904"BOOK="_idx" COLLECTION="nw41" TIDREF="i3074"
include Introduction to NetWare Directory Services, Installation, Upgrade, and Installing and Using Novell Online Documentation for NetWare 4.1.This manual includes complete documentation for installing your NetWare 4.1 server. Procedures for installing client software are also included.PAGENUM=8 ID="BP2"FILEREF="n41in19a.tif"ID="FM73519"Read Introduction to NetWare Directory Services and plan your Directory tree.FILEREF="n41in20a.tif"Install a new NetWare 4.1 server. (Optional) Install NetWare 4.1 SFT IIITM for mirrored servers.FILEREF="n41in21a.tif"From the "Other Installation Items/Products" menu, create client diskettes and, if desired, copy the NetWare 4.1 online documentation to the server.FILEREF="n41in22a.tif"Install the NetWare client software on each computer.PAGENUM=9 ID="BP3"FILEREF="n41in04a.tif"Set up or install the NetWare 4.1 online documentation by reading Installing and Using Novell Online Documentation for NetWare 4.1.FILEREF="n41in05a.tif"Administer the network using the NetWare administration utilities.PAGENUM=11 ID="BP4"ID="FM66968"How to Use This ManualThere are many steps to getting your NetWare® 4.1 server installed and operating with client workstations on a network. A diagram outlining the process is shown on IDREF="FM73519"page viii.Begin by reading 
BOOK="getstenu" COLLECTION="nw41"Introduction to NetWare Directory Services to plan your NetWare 4.1 Directory tree.Next, install a new NetWare 4.1 server by following the installation procedures in IDREF="FM90747"Chapter 2,  "Simple Installation," on page 15, or IDREF="FM44025"Chapter 3,  "Custom Installation," on page 63.If you desire, perform other installation options such as copying online documentation to the NetWare 4.1 server and creating client diskettes. Procedures for performing other installation options are included at the end of the "Simple Installation" and "Custom Installation" chapters.Next, install the NetWare client software on each workstation in your network. Next, set up the documentation viewers to view the NetWare 4.1 online documentation. Procedures for doing so are included in 
BOOK="docinenu" COLLECTION="nw41"Installing and Using Novell Online Documentation for NetWare 4.1.Finally, administer the NetWare 4.1 network by reading 
BOOK="superenu" COLLECTION="nw41"Supervising the Network, which is available online.RENDERAS="SECT1"PAGENUM=12 ID="BP5"Installation OptionsYou can install a NetWare 4.1 server using either the "Simple Installation" or "Custom Installation" IDXID="w2905"BOOK="_idx" COLLECTION="nw41" TIDREF="i1816"
option.The "Simple Installation" option makes a number of assumptions, and therefore requires less interaction from the installer. This makes the server both easier and quicker to install.The "Custom Installation" option makes no assumptions and lets you customize your server installation. Additional options, such as spanning volumes across multiple drives and loading and binding TCP/IP and AppleTalk, are available only in the "Custom Installation" option.Procedures for installing using the "Simple Installation" method are found in IDREF="FM90747"Chapter 2,  "Simple Installation," on page 15.Procedures for installing using the "Custom Installation" option are found in IDREF="FM44025"Chapter 3,  "Custom Installation," on page 63.RENDERAS="SECT1"Technical Support IncludedMARK=BULLETContext-sensitive help. If you are using a NetWare menu utility and want more information about how to complete a task, press <MOREINFO="NONE"F1>.DynaText* Online Documentation. The DynaText viewer allows you to read online manuals from your MS Windows, Macintosh*, UNIX, or OS/2* workstation.All NetWare 4.1 manuals are available on the NetWare 4.1 Online Documentation CD-ROM.RENDERAS="SECT1"PAGENUM=13 ID="BP6"Other Technical SupportMARK=BULLETNovell Authorized Service CentersSM( NASCsSM) are local support providers authorized and supported by Novell®. NASCs provide both telephone and on-site assistance, and should be your first source for technical support.For the Novell Authorized Service Center nearest you, call 1-800-338-NASC.Hardware manuals. Many network problems occur because of malfunctioning hardware.If you can isolate a problem to a certain computer component or cable segment, check the manuals that came with the hardware involved.NetWare Management SystemTM (NMS)TM helps you manage the cabling system, computers, software, and other components of the network.For more information about using NMS on your network, contact your Novell Authorized ResellerCLM.Other Novell publications. NetWare Applications NotesTM and Novell Research ReportsTM cover technical aspects of NetWare-based system design, implementation, and management.NetWare Application Notes is a collection of technical articles published monthly. Novell Research Reports is published as the research becomes available.To purchase subscriptions and back issues of these publications call the Novell Research Order Desk at 1-800-UPDATE1. From outside the United States or Canada, call 1-800-429-5380.Third-party books and periodicals. Many books on NetWare topics, including books published by Novell Press€, are available at most bookstores.In addition, numerous networking periodicals give advice on configuring, managing, and troubleshooting your network.PAGENUM=14 ID="BP7"NetWireSM on CompuServe*. A fairly inexpensive way to get up-to-date advice and patches is through the NetWire service on the CompuServe bulletin board.To open a CompuServe account, call one of the following numbers:MARK=BULLETIn the United States or Canada: 1-800-524-3388.In the United Kingdom: 0800-289-378.In Germany: 0130-37-32.In other European countries: 44-272-255-111.In all other locations, use the appropriate country code for the U.S. and call 1-614-457-0802.Ask for "Representative 200." This phrase identifies you as a Novell customer.Network Support EncyclopediaSM. This encyclopedia gives customers access to regularly-updated information from Novell and other vendors on products and services.In addition the Network Support Encyclopedia Professional VolumeSM provides customers with additional information such as patches, fixes, etc.Both are distributed on CD-ROM on a subscription basis. Updates are sent out several times each year. (For more information, contact your Novell Authorized Reseller.)Troubleshooting hardware and software. Specialized hardware and software packages, such as Novell's LANalyzer®, are available to help you isolate network problems.Customer service. You may want to contact your Novell Authorized Reseller for technical assistance.Most Novell Authorized Resellers have Certified NetWare EngineersSM on their staffs ready to assist users with their networking problems.RENDERAS="SECT1"PAGENUM=15 ID="BP8"User CommentsWe are continually looking for ways to make our products and our manuals as easy to use as possible.You can help us by sharing your comments and suggestions about how our manuals could be made more useful to you and about inaccuracies or information gaps they may contain.Submit your comments either by filling out the "User Comments" form at the end of this manual or by writing to us directly at the following address:TYPE="VERT"Novell, Inc.Technical Publications MS C-23-1122 East 1700 South Provo, UT 84606 USAWe appreciate your comments.LABEL="1"PAGENUM=1 ID="BP9"ID="FM43011"ID="FM93569"Prepare Your Site and EquipmentIf your network hardware is already installed and meets site and power conditioning requirements, go to IDREF="FM90747"Chapter 2, "Simple Installation," on page 15 and determine if that method of installation is right for you.  If you determine that the "Simple Installation" option is not right for you, go to IDREF="FM44025"Chapter 3, "Custom Installation," on page 63.RENDERAS="SECT1"What You NeedTo prepare your network IDXID="w2906"BOOK="_idx" COLLECTION="nw41" TIDREF="i4167"
location, you mustMARK=CHECKBOXMeet the hardware requirementsEnsure proper power and power conditionsSet up computer and networking hardwarePAGENUM=2 ID="BP10"RENDERAS="SECT2"ID="FM69886"Hardware RequirementsYou need the following hardware for installing a NetWare® 4.1 server.MARK=CHECKBOXA PC (or PC compatible) with a IDXID="w2907"BOOK="_idx" COLLECTION="nw41" TIDREF="i10"
386 or 486 (SX or DX) or higher processor.If you plan to install your server from CD-ROM or from floppy diskettes, you will need a minimum of 8 MB of RAM.If you plan to install your server from a remote network installation area, you will need a minimum of 10 MB of RAM.The additional 2 MB of RAM is needed when installing from a remote network installation area, because the new server will need to load the CLIB and STREAMS NLM programs.A hard disk with sufficient storage space for your network. The IDXID="w2908"BOOK="_idx" COLLECTION="nw41" TIDREF="i1636"
minimum amount of storage space required is 90 MB: 15 MB for a DOS partition plus 75 MB for a NetWare disk partition containing volume SYS:.However, if all file NetWare file groups are copied to the server, (see IDREF="FM80634""Select Optional NetWare File Groups" on page 124) you will need a minimum of 100 MB for volume SYS: We therefore recommend a larger volume SYS:.In some cases, it is easier to troubleshoot server problems by increasing the DOS partition 1 MB for every 1 MB of server RAM. For example, if your server had 12 MB of RAM, you might want to increase the DOS partition from 15 MB to 27 MB (15 MB + 12 MB = 27 MB).If you plan to install the DynaText* viewer and the NetWare 4.1 IDXID="w2909"BOOK="_idx" COLLECTION="nw41" TIDREF="i3074"
documentation on the server, add another 60 MB of disk space.If desired, you can read the NetWare 4.1 online manuals directly from CD-ROM without having to install the files to the server.At least one network board. Network cabling (Ethernet, token ring, FDDI, ARCnet*, baseband, etc.).(If installing from CD-ROM) A CD-ROM drive that can read ISO 9660 formatted CD-ROM disks.PAGENUM=3 ID="BP11"RENDERAS="SECT1"ID="FM95452"Site and Equipment PreparationRENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"IDXID="w2910"BOOK="_idx" COLLECTION="nw41" TIDREF="i3361"
Check the operating environment and power requirements for your equipment.Consult the documentation provided with your computer for specific requirements in the following areas:
TYPE="VERT"Temperature/humidityPower frequencyPower consumptionHeat dissipationPERFORMANCE="REQUIRED"Use dedicated power lines and grounded outlets.Use dedicated power lines for all hardware components (NetWare servers, workstations, printers, etc.) on your NetWare network. Connect only network components to these lines. Electrical outlets should be standard three-wire grounded outlets, with the ground wire connected to an earth ground. (If you connect the ground wire to a conduit ground, make sure the conduit ground is an earth ground.)PERFORMANCE="REQUIRED"Install power conditioning equipment.Protect NetWare servers from power fluctuations with a regulating 
IDXID="w2911"BOOK="_idx" COLLECTION="nw41" TIDREF="i4648"
uninterruptible power supply (

UPS). In addition to protecting hardware from damage caused by power surges and voltage spikes, a UPS protects data held in RAM during a power failure.In addition, we strongly recommend that you use UPS protection for network workstations and other peripherals.If this is not feasible, connect all network hardware to protective devices such as line-surge suppressors (also called power conditioners or line filters) and ferro-resonant isolation transformers. These devices are inexpensive and can protect equipment from various power irregularities such as electric noise and minor voltage spikes. However, these devices cannot protect equipment from large power surges or preserve any data in RAM during power outages.
PAGENUM=4 ID="BP12"PERFORMANCE="REQUIRED"Protect network equipment from 
IDXID="w2912"BOOK="_idx" COLLECTION="nw41" TIDREF="i4269"
static 
IDXID="w2913"BOOK="_idx" COLLECTION="nw41" TIDREF="i1302"
electricity.Make sure that, for all NetWare hardware, the operating environment does not subject equipment to static electricity. We strongly recommend the following protective measures:
MARK=BULLETTreat carpets with anti-static chemicals (available in spray form from most computer stores).Use anti-static protective covers for carpets, or conductive covers connected to an earth ground. Do not use plastic or other synthetic carpet protectors near network equipment. Such protectors generate large amounts of static electricity.Ground equipment through a one-megohm resistor to bleed off the static slowly and thus avoid a static discharge from conductive surfaces.Make sure personnel working on open computer equipment take precautionary measures, such as wearing grounded wrist straps. Work on open computer equipment should be done only with the computer turned off.PERFORMANCE="REQUIRED"Back up files located on your hard drives.During the installation process, existing files located on any hard disk area other than the bootable DOS partition are erased.In addition, the installation utility finds any existing nonbootable partitions and asks whether you want to delete them, which would give you more hard disk space for the NetWare partition.Backing up desired files before installation ensures that files on your hard disks will be saved.
PAGENUM=5 ID="BP13"RENDERAS="SECT1"ID="FM43321"Set Up HardwareIDXID="w2914"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"NetWare 4.1 servers can operate on many kinds of hardware. To ensure that there are no conflicts, use unique interrupt request IDXID="w2915"BOOK="_idx" COLLECTION="nw41" TIDREF="i1985"
(IRQ) settings on NetWare server boards.RENDERAS="SECT2"Novell's Yes ProgramTo be certain of hardware compatibility with NetWare, look for one of the following IDXID="w2916"BOOK="_idx" COLLECTION="nw41" TIDREF="i4869"
symbols:FILEREF="n41in60a.tif"MARK=BULLETProducts that receive the Yes, It Runs with NetWareTM designation have been verified by the vendor to work with NetWare.These products are developer-tested only; Novell makes no warranties with respect to these products.Products that receive the Yes, NetWare Tested and ApprovedTM certification have passed rigorous testing by Novell LabsTM.Novell engineers have worked closely with the vendor to ensure that these products meet Novell's strict quality standards.Novell publishes bulletins containing test results on each NetWare Tested and Approved product.Products that receive the NetWare ReadyTM mark have been certified by Novell Labs and are bundled with NetWare.This is designed to simplify and reduce the time spent on the network installation process by allowing participating OEM partners to offer products that are bundled or pre-installed with the NetWare operating system, Personal NetWareTM, or other client software.PAGENUM=6 ID="BP14"RENDERAS="SECT2"ID="FM58132"Calculate Necessary Server IDXID="w2917"BOOK="_idx" COLLECTION="nw41" TIDREF="i580"
RAMIDXID="w2918"BOOK="_idx" COLLECTION="nw41" TIDREF="i3665"This section contains a simple procedure for determining an approximate amount of RAM necessary for your NetWare 4.1 server.For more detailed information on calculating RAM requirements, see IDREF="FM69155"Appendix A "Calculate RAM Requirements" on IDREF="FM69155"page 271.RENDERAS="SECT3"ProcedureTo calculate your server's total RAM requirements, perform the following steps. (NetWare 4.1 can support up to IDXID="w2919"BOOK="_idx" COLLECTION="nw41" TIDREF="i3665"
4 GB of RAM and up to IDXID="w2920"BOOK="_idx" COLLECTION="nw41" TIDREF="i1636"
32 TB of disk storage space.)PERFORMANCE="REQUIRED"ID="FM64182"If you are installing your server from CD-ROM or from floppy diskettes, make sure that you have a minimum of 8 MB of RAM. If you are installing your server from a remote installation area, make sure you have a minimum of 10 MB or RAM.The additional 2 MB of RAM is needed when installing from a remote network installation area, because the new server will need to load the CLIB and STREAMS NLM programs.PERFORMANCE="REQUIRED"ID="FM80755"Add 2 MB to install one or more of the following:
MARK=BULLETAdditional NetWare products (such as NetWare for Macintosh*, NetWare for NFS*, etc.).A print server (PSERVER.NLM) on this server.Any of the following NetWare Loadable ModulesTM: MONITOR.NLM, INSTALL.NLM, SERVMAN.NLM. (Many systems require these NLMsTM.)PERFORMANCE="REQUIRED"Multiply the amount of your system's disk space (in megabytes) by 0.008 and add this number to the total from 
IDREF="FM64182"Steps 1 and 
IDREF="FM80755"2.For example, 200 MB multiplied by 0.008 equals 1.6 MB.PERFORMANCE="REQUIRED"Add 1 to 4 MB for additional 
IDXID="w2921"BOOK="_idx" COLLECTION="nw41" TIDREF="i572"
cache buffer RAM to optimize performance.The more 
IDXID="w2922"BOOK="_idx" COLLECTION="nw41" TIDREF="i93"
RAM you provide for cache buffers, the better your system's performance will be.
PAGENUM=7 ID="BP15"If you have a server that contains more than 16 MB of RAM, do
 not use anything less than 32-bit AT busmastering or 
IDXID="w2923"BOOK="_idx" COLLECTION="nw41" TIDREF="i1162"
DMA boards in the server, unless the driver supports going above 16 MB of RAM. For more information, contact the computer manufacturer.If you have a IDXID="w2924"BOOK="_idx" COLLECTION="nw41" TIDREF="i2446"
386 computer manufactured in 1987, it may not carry out some 32-bit instructions. This could adversely affect the functioning of NetWare.  If a problem exists, NetWare displays a message. You may be able to correct the problem by replacing a ROM chip on the board. For more information, contact your computer manufacturer.PAGENUM=8 ID="BP16"RENDERAS="SECT1"IDXID="w2925"BOOK="_idx" COLLECTION="nw41" TIDREF="i1825"
Install and IDXID="w2926"BOOK="_idx" COLLECTION="nw41" TIDREF="i738"
Configure Your IDXID="w2927"BOOK="_idx" COLLECTION="nw41" TIDREF="i1644"
HardwareRENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Record the following hardware information on the NetWare 4.1 Server Worksheet on IDREF="FM68531"page 175.MARK=BULLETNetWare server: name, make, and model.Memory amount.Non-network boards: type and settings (optional).Network boards: associated LAN drivers, IPX external network number, I/O address, memory address, interrupt, and node address.When installing two or more network boards of the same type, check your network board documentation to avoid IDXID="w2928"BOOK="_idx" COLLECTION="nw41" TIDREF="i2846"
address conflicts. Some LAN drivers and their default settings are listed in IDREF="FM91651"Table 1-1. For more information about settings, see the documentation that came with your network board.LABEL="1-1" PGWIDE=1 TOCENTRY="1"IDXID="w2929"BOOK="_idx" COLLECTION="nw41" TIDREF="i1987"ID="FM91651" Default LAN Driver Settings for ISA Network BoardsCOLS=4 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="4*"COLNAME=3 COLWIDTH="6*"COLNAME=4 COLWIDTH="4*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"LAN driverCOLNAME=2 ROTATE="0" MOREROWS="0"I/O AddressCOLNAME=3 ROTATE="0" MOREROWS="0"Memory AddressCOLNAME=4 ROTATE="0" MOREROWS="0"InterruptVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"TRXNETCOLNAME=2 ROTATE="0" MOREROWS="0"2E0COLNAME=3 ROTATE="0" MOREROWS="0"D000COLNAME=4 ROTATE="0" MOREROWS="0"2COLNAME=1 ROTATE="0" MOREROWS="0"NE1000COLNAME=2 ROTATE="0" MOREROWS="0"300COLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=4 ROTATE="0" MOREROWS="0"3COLNAME=1 ROTATE="0" MOREROWS="0"NE2000COLNAME=2 ROTATE="0" MOREROWS="0"300COLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=4 ROTATE="0" MOREROWS="0"3COLNAME=1 ROTATE="0" MOREROWS="0"PCN2 (primary)COLNAME=2 ROTATE="0" MOREROWS="0"620COLNAME=3 ROTATE="0" MOREROWS="0"CC00 (RAM)COLNAME=4 ROTATE="0" MOREROWS="0"2COLNAME=1 ROTATE="0" MOREROWS="0"PCN2 (alternate)COLNAME=2 ROTATE="0" MOREROWS="0"628COLNAME=3 ROTATE="0" MOREROWS="0"CC00 (RAM)COLNAME=4 ROTATE="0" MOREROWS="0"2COLNAME=1 ROTATE="0" MOREROWS="0"TOKENCOLNAME=2 ROTATE="0" MOREROWS="0"A20COLNAME=3 ROTATE="0" MOREROWS="0"D800 (RAM)COLNAME=4 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"3C503COLNAME=2 ROTATE="0" MOREROWS="0"300COLNAME=3 ROTATE="0" MOREROWS="0"C8000COLNAME=4 ROTATE="0" MOREROWS="0"3COLNAME=1 ROTATE="0" MOREROWS="0"3C505COLNAME=2 ROTATE="0" MOREROWS="0"300COLNAME=3 ROTATE="0" MOREROWS="0"5 (DMA)COLNAME=4 ROTATE="0" MOREROWS="0"3PAGENUM=9 ID="BP17"Defaults for the following IDXID="w2930"BOOK="_idx" COLLECTION="nw41" TIDREF="i2445"
microchannel IDXID="w2931"BOOK="_idx" COLLECTION="nw41" TIDREF="i960"
network boards are set by the CLASS=DISKReference diskette. You may be prompted to enter the slot number.TYPE="VERT"TOKENDMANE/2TMTOKENNE/2-32TM3C523Options for the NE3200TM EISA network board are set by the computer's configuration utility. NetWare needs the slot number.For details, see the documentation that came with your network board.Floppy disk drives: diskette size and storage size.Internal hard disks: make, model, and storage size.For microchannel machines, make sure you record the type of disk controller. You will need this information later when you load disk drivers.Disk coprocessor boards (DCBs): 
DCB drivers and I/O address.For microchannel servers, use the CLASS=DISKReference diskette to set the disk coprocessor boards.Default DCB settings for standard architecture servers are based on the type of PAL chip installed at position U3.11 and U4.11 on the board. Jumper settings must also match the PAL, which controls the interrupt I/O address. The default settings are listed in IDREF="FM24892"Table 1-2, on page 10. (For alternate settings, see the DCB documentation.)LABEL="1-2" PGWIDE=1 TOCENTRY="1"IDXID="w2932"BOOK="_idx" COLLECTION="nw41" TIDREF="i1113"ID="FM24892" Default Settings for DCBsCOLS=4 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="7*"COLNAME=3 COLWIDTH="6*"COLNAME=4 COLWIDTH="6*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Part number of PAL at position U3.11COLNAME=2 ROTATE="0" MOREROWS="0"Part Number of PAL at position U4.11COLNAME=3 ROTATE="0" MOREROWS="0"I/O AddressCOLNAME=4 ROTATE="0" MOREROWS="0"InterruptVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"814-198-001COLNAME=2 ROTATE="0" MOREROWS="0"814-197-001COLNAME=3 ROTATE="0" MOREROWS="0"340COLNAME=4 ROTATE="0" MOREROWS="0"BCOLNAME=1 ROTATE="0" MOREROWS="0"814-198-001COLNAME=2 ROTATE="0" MOREROWS="0"814-197-002COLNAME=3 ROTATE="0" MOREROWS="0"348COLNAME=4 ROTATE="0" MOREROWS="0"CCOLNAME=1 ROTATE="0" MOREROWS="0"814-198-002COLNAME=2 ROTATE="0" MOREROWS="0"814-197-001COLNAME=3 ROTATE="0" MOREROWS="0"320COLNAME=4 ROTATE="0" MOREROWS="0"ACOLNAME=1 ROTATE="0" MOREROWS="0"814-198-002COLNAME=2 ROTATE="0" MOREROWS="0"814-197-002COLNAME=3 ROTATE="0" MOREROWS="0"328COLNAME=4 ROTATE="0" MOREROWS="0"FPAGENUM=10 ID="BP18"Disk subsystems: number of drives, drive types, and storage sizes.Mirrored disks: which drives will be mirrored.PERFORMANCE="REQUIRED"Install hard disks and network boards.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"If necessary, set switches or jumpers on hard disks and network boards.Set each address and interrupt according to the worksheet you completed in Step 1.PERFORMANCE="REQUIRED"Install internal hard disks and check for proper jumper settings and termination.See your hard disk documentation. See also "BOOK="cncptenu" COLLECTION="nw41"SCSI bus" in Concepts.PERFORMANCE="REQUIRED"Place each board in a slot in the server.If you install IDXID="w2933"BOOK="_idx" COLLECTION="nw41" TIDREF="i4511"
token ring network boards, cable the boards in the server to the MAU before installing the operating system. Otherwise, the TOKEN LAN driver will not load.PERFORMANCE="REQUIRED"Connect peripheral equipment to the server and check jumper settings and termination.See the documentation for each peripheral. See also "BOOK="cncptenu" COLLECTION="nw41"SCSI bus" in Concepts.PERFORMANCE="REQUIRED"(Optional) Install optical disks.For instructions, see Chapter 6, "BOOK="superenu" COLLECTION="nw41"Migrating Data Using the High Capacity Storage System," in Supervising the Network.PAGENUM=11 ID="BP19"PERFORMANCE="REQUIRED"Configure the hardware by using the hardware's setup (reference or configuration) program.For details on the setup program, see the documentation that came with your computer.Do not select "Set network server mode" if your setup program lists this option. This mode disables IDXID="w2934"BOOK="_idx" COLLECTION="nw41" TIDREF="i2015"
keyboard input after DOS executes an AUTOEXEC.BAT file. As a result, you wouldn't be able to use the keyboard after the server booted.Instead, use the keyboard protection feature in MONITOR. See "BOOK="utlrfenu" COLLECTION="nw41"MONITOR" in Utilities Reference.If your hardware supports a power-on password, use it to secure the server from unauthorized use.Do not change the arbitration level of the 

MFM or 

ESDI fixed-disk driver from the factory default setting. NetWare requires the default setting.PERFORMANCE="REQUIRED"(Conditional) If you plan to install NetWare 4.1 from CD-ROM, install the CD-ROM drive as a DOS device, according to the manufacturer's instructions.
PAGENUM=12 ID="BP20"RENDERAS="SECT1"ID="FM75630"Make Working Copies of the Diskettes (Conditional)If you plan to install NetWare 4.1 from floppy diskettes rather than from CD-ROM or from a remote network installation area, use only working copies of diskettes. This way, should your working copies get corrupted, you can use the original NetWare 4.1 diskettes to make other working copies. To make working copies of the NetWare diskettes, complete the following steps.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Boot a personal computer with DOS or OS/2.PERFORMANCE="REQUIRED"Use the DISKCOPY command to format and copy each NetWare diskette to a high-capacity diskette.PERFORMANCE="REQUIRED"Label each copied diskette with the same name that appears on the original diskette.PERFORMANCE="REQUIRED"After making the working copies, store the original NetWare diskettes in a secure place. Throughout the installation, whenever you are instructed to insert a specific diskette, use the working copy.
PAGENUM=13 ID="BP21"RENDERAS="SECT1"Where to Go from HereWith the initial hardware preparation completed and (if applicable) working copies of the NetWare diskettes made, you are ready to install the NetWare server.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Install a new NetWare 4.1 server using the "Simple Installation" methodCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM90747"Chapter 2, "Simple Installation," on page 15.COLNAME=1 ROTATE="0" MOREROWS="0"Install a new NetWare 4.1 server using the "Custom Installation" methodCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM44025"Chapter 3, "Custom Installation," on page 63.COLNAME=1 ROTATE="0" MOREROWS="0"Install a new NetWare Server for OS/2COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM72388"Chapter 4, "Install NetWare Server for OS/2," on page 177.COLNAME=1 ROTATE="0" MOREROWS="0"Install NetWare SFT IIICOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM38629"Chapter 5, "Install NetWare 4.1 SFT III," on page 237.LABEL="2"PAGENUM=15 ID="BP22"ID="FM90747"Simple InstallationThe "Simple Installation" option allows you to easily install a NetWare®  4.1 server using a streamlined user interface. The "Simple IDXID="w2935"BOOK="_idx" COLLECTION="nw41" TIDREF="i4157"IDXID="w2936"BOOK="_idx" COLLECTION="nw41" TIDREF="i1816"
Installation" assumesMARK=CHECKBOXAn existing DOS partition of at least 15 MB on the hard disk. A 15 MB DOS partition should be sufficient for storing the files used to boot your server. If you need to store additional files on the DOS partition, you may want to make the partition larger.DOS is installed on the DOS partition.The server will boot from a DOS partition on the hard disk, rather than from floppy boot diskettes.Hard disks (including hard disk subsystems, if any), won't be mirrored or duplexed.All hard disk space not allocated to the DOS partition will be allocated to NetWare.Each disk will contain one NetWare volume.A randomly generated IPX internal network number.No changes will be made to the AUTOEXEC.NCF and STARTUP.NCF files.A default NetWare Directory Services€ hierarchy with a single container for all objects.The IPX protocol as the only installed communications protocol, without the option to install TCP/IP or AppleTalk*.PAGENUM=16 ID="BP23"TCP/IP and AppleTalk can be added after installation. If the "Simple Installation" option isn't possible in your environment, follow the procedures in IDREF="FM44025"Chapter 3, "Custom Installation," on page 63.RENDERAS="SECT1"Prerequisite TasksMARK=CHECKBOXPlan your Directory tree. See BOOK="getstenu" COLLECTION="nw41"Introduction to NetWare Directory Services for guidelines and suggestions.If your computer has never been a server before, complete the tasks explained in IDREF="FM93569"Chapter 1, "Prepare Your Site and Equipment," on page 1.Run the computer's Setup program and set the computer's time to the exact local time. (The time synchronization feature in NetWare Directory Services uses the computer's time setting.)If you install from another server, make sure the new server is cabled to the network and has the NetWare client software installed.If necessary, partition and format your hard disk. Boot from the NetWareCLASS=DISK License diskette; type IDXID="w2937"BOOK="_idx" COLLECTION="nw41" TIDREF="i1439"IDXID="w2938"BOOK="_idx" COLLECTION="nw41" TIDREF="i1636"
FDISK and follow the screen prompts to repartition the hard disk. Reboot the machine and type IDXID="w2939"BOOK="_idx" COLLECTION="nw41" TIDREF="i1551"IDXID="w2940"BOOK="_idx" COLLECTION="nw41" TIDREF="i1636"
FORMAT to format the partition.Reformatting your hard disk erases all stored files. Be sure to back up your hard disk prior to partitioning and formatting.PAGENUM=17 ID="BP24"RENDERAS="SECT1"Suggested ResourcesMARK=CHECKBOXThe NetWare Server Installation quick path card for an overview of the installation process.A copy of the NetWare 4.1 Server Worksheet (located on IDREF="FM68531"page 175).The NetWare CLASS=DISKLicense diskette.One of the following:MARK=BULLETNetWare 4.1 CD-ROMs.Working copies of NetWare 4.1 diskettes.Access to NetWare 4.1 installation files on a remote network installation area (the NetWare 4.1 Operating System CD-ROM mounted as a NetWare volume, or an image of the CD-ROM on another server).RENDERAS="SECT1"File Sets Copied During InstallationThe Simple Installation option does not copy all NetWare 4.1 file IDXID="w2941"BOOK="_idx" COLLECTION="nw41" TIDREF="i1473"
sets during installation. File sets that are copied, and those that are not copied, are listed below:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"File Sets CopiedCOLNAME=2 ROTATE="0" MOREROWS="0"File Sets Not CopiedVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"System filesCOLNAME=2 ROTATE="0" MOREROWS="0"UNIX utilitiesCOLNAME=1 ROTATE="0" MOREROWS="0"DOS utilitiesCOLNAME=2 ROTATE="0" MOREROWS="0"Client upgrade filesCOLNAME=1 ROTATE="0" MOREROWS="0"OS/2 utilitiesCOLNAME=2 ROTATE="0" MOREROWS="0"Upgrade and migration filesCOLNAME=1 ROTATE="0" MOREROWS="0"MS Windows utilitiesCOLNAME=2 ROTATE="0" MOREROWS="0"NetWare for Macintosh filesFile sets that are not copied to the server may be copied later through the "Copy Files" option of IDXID="w2942"BOOK="_idx" COLLECTION="nw41" TIDREF="i1838"IDXID="w2943"BOOK="_idx" COLLECTION="nw41" TIDREF="i843"
INSTALL.NLM. For more information, see "BOOK="superenu" COLLECTION="nw41"Copying NetWare Files" in Chapter 7 of Supervising the Network.PAGENUM=18 ID="BP25"RENDERAS="SECT1"ID="FM50906"Install Server SoftwareInstall your NetWare 4.1ID="FMSERVE"server software by following the procedures in the sections that follow.RENDERAS="SECT2"Choose an Installation MediumYou can install a NetWare 4.1 server from CD-ROM, from floppy diskettes (available only through the NetWare Fulfillment Center), or from a remote network installation area.If you are installing the first in a series of NetWare 4.1 servers on a new network, you must install from CD-ROM or from floppy diskettes.IDREF="FM82077"Figure 2-1 lists factors to consider before choosing an installation medium.LABEL="2-1" FLOAT="0"ID="FM82077"Installation MediaFILEREF="n41in03a.tif"PAGENUM=19 ID="BP26"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"To install fromCOLNAME=2 ROTATE="0" MOREROWS="0"SeeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"CD-ROMCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM27196""Install from CD-ROM" on page 20.COLNAME=1 ROTATE="0" MOREROWS="0"A network volumeCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM83900""Installing from a Remote Network Installation Area" on page 22.COLNAME=1 ROTATE="0" MOREROWS="0"Floppy diskettesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM80366""Install from Floppy Diskettes" on page 29.PAGENUM=20 ID="BP27"RENDERAS="SECT1"ID="FM27196"Install from CD-ROMRENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"If you have not done so already, install the CD-ROM drive and drivers according to the manufacturer's instructions. Usually, the installation program for your 
IDXID="w2944"BOOK="_idx" COLLECTION="nw41" TIDREF="i603"
CD-ROM will automatically update the CONFIG.SYS and AUTOEXEC.BAT files to add the CD-ROM device driver.If not, follow the manufacturer's instructions to create or update these files.PERFORMANCE="REQUIRED"Insert the 
CLASS=DISKNetWare 4.1 Operating System CD-ROM into the CD-ROM drive.PERFORMANCE="REQUIRED"Reboot the computer.Rebooting executes the CONFIG.SYS and AUTOEXEC.BAT files and recognizes the CD-ROM drive as a DOS device.PERFORMANCE="REQUIRED"Change to the drive letter corresponding to the CD-ROM.This is generally drive D:.PERFORMANCE="REQUIRED"Type 
FORMAT="LINESPECIFIC"MOREINFO="NONE"INSTALL MOREINFO="NONE"<Enter>A menu similar to the one below appears.LABEL="2-2" FLOAT="0"Choose the Desired Server LanguageFILEREF="n41in25a.tif"PAGENUM=21 ID="BP28"PERFORMANCE="REQUIRED"Choose the language in which you want the server installed and press MOREINFO="NONE"<Enter>.The "Select the Type of Installation Desired" menu appears.PERFORMANCE="REQUIRED"Choose "NetWare Server Installation" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Go to 
IDREF="FM51075""Name Your Server and Copy Boot Files" on page 30.
PAGENUM=22 ID="BP29"RENDERAS="SECT1"ID="FM83900"Installing from a Remote Network Installation AreaIDXID="w2945"BOOK="_idx" COLLECTION="nw41" TIDREF="i3750"A NetWare 4.1 server may be installed over the network from a mounted CD-ROM NetWare volume, or from CD-ROM or floppy diskette files copied to another server.In either scenario, a user logs in to a server with a remote network installation area and installs the workstation as a NetWare 4 server through the Installation utility.Requirements and recommendations for a IDXID="w2946"BOOK="_idx" COLLECTION="nw41" TIDREF="i3750"
remote installation are outlined below.RENDERAS="SECT2"Requirements for a Network Installation AreaMARK=BULLETThe server with the CD-ROM image should not be RIP-filtered from the server being installed.To find out if your network is utilizing IDXID="w2947"BOOK="_idx" COLLECTION="nw41" TIDREF="i3863"
RIP filtering, load FILTCFG.NLM at the server and view IPX protocol filters.The server being installed should use an IPX internal network number that is not RIP-filtered from the server with the CD-ROM image.When installing using the "Simple Installation" option, a randomly generated IPX internal network number is chosen for you. If you need to enter a specific IPX internal network number, you should install using the "Custom Installation" option.RENDERAS="SECT2"Recommendations for a Network Installation AreaMARK=BULLETFor better performance, the server with the CD-ROM image should have Packet BurstTM support. NetWare 3.12 and NetWare 4TM servers have Packet Burst support built in. NetWare 3.11 requires PBURST.NLM for Packet Burst support.For better performance, the server with the CD-ROM image should have LIP (Large Internet Packet) support enabled. NetWare 3.12 and NetWare 4 servers have LIP support enabled by default (SET "ALLOW LIP = ON"). NetWare 3.11 requires LIPX.NLM for LIP support.PAGENUM=23 ID="BP30"RENDERAS="SECT2"Remote Installation AreasThe remote installation area can consist of one of the following:MARK=BULLETA NetWare 4.1 CD-ROM mounted as a NetWare volumeThe NetWare 4.1 CD-ROM or floppy diskette files copied to a volume on a NetWare 4 serverCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Install from a NetWare 4.1 CD-ROM mounted as a NetWare volumeCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM95237""Install from a CD-ROM Mounted as a NetWare Volume" on page 24.COLNAME=1 ROTATE="0" MOREROWS="0"Install from a NetWare server volume containing copied NetWare 4.1 CD-ROM filesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM64462""Install from a NetWare Volume with Files Copied on a Server" on page 27.PAGENUM=24 ID="BP31"RENDERAS="SECT2"ID="FM95237"Install from a CD-ROM Mounted as a NetWare VolumeRENDERAS="SECT3"IDXID="w2948"BOOK="_idx" COLLECTION="nw41" TIDREF="i2523"IDXID="w2949"BOOK="_idx" COLLECTION="nw41" TIDREF="i2822"
Necessary ResourcesMARK=CHECKBOXA CD-ROM drive that can read ISO 9660 formatted CD-ROM disks.An existing NetWare server. (This will be the host server.)An existing NetWare workstation. (This will be the new server you install.)RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Cable the CD-ROM drive to the NetWare 4.1 server (the host server). Since you are installing the CD-ROM as a NetWare volume, you do not need to install any drivers at this time.PERFORMANCE="REQUIRED"Insert the 
CLASS=DISKNetWare 4.1 Operating System CD-ROM into the CD-ROM drive.PERFORMANCE="REQUIRED"At the C:\NWSERVER directory, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"SERVER MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"At the server console type 
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>The menu shown on the next page appears.
PAGENUM=25 ID="BP32"LABEL="2-3" FLOAT="0"The "Installation Options" MenuFILEREF="n41in16a.tif"PERFORMANCE="REQUIRED"Choose "Driver Options."The "Driver Options" menu appears.PERFORMANCE="REQUIRED"Choose "Configure Disk and Storage Device Drivers."The "Additional Driver Actions" menu appears.PERFORMANCE="REQUIRED"Choose "Select an Additional Driver."You are prompted to enter the path to the source directory where the NetWare 4.1 files are located.PERFORMANCE="REQUIRED"Verify or change the source path and press MOREINFO="NONE"<Enter>.The "Select a Driver" list appears.PERFORMANCE="REQUIRED"Choose the necessary CD-ROM drivers according to the documentation that accompanied your CD-ROM drive.If the device drivers you need are not listed, press MOREINFO="NONE"<Ins> and follow the prompts to access a new list of drivers.  For information on the CD-ROM drivers that are shipped in the Red BoxTM (NetWare 4.1 product package), along with their proper load order, see IDREF="FM28651"Appendix F, "Red Box CD-ROM Drivers," on page 311.PERFORMANCE="REQUIRED"Once you have loaded all necessary drivers, from the "Additional Driver Actions" menu choose "Return to Previous Menu."PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Alt>+<F10> and choose "Yes" to exit INSTALL.NLM.
PAGENUM=26 ID="BP33"You are returned to the server console.PERFORMANCE="REQUIRED"At the console prompt, type the following commands:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD NWPA MOREINFO="NONE"<Enter> 
LOAD CDROM MOREINFO="NONE"<Enter> 
CD MOUNT NW410 MOREINFO="NONE"<Enter> This mounts the CD-ROM as a NetWare volume.PERFORMANCE="REQUIRED"Go to the workstation that is to become a server and log in to the host server with the mounted CD-ROM NetWare volume.PERFORMANCE="REQUIRED"Map a drive to the mounted CD-ROM volume.For example:
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP N NW410:MOREINFO="NONE" <Enter>PERFORMANCE="REQUIRED"At the mapped drive letter, type 
FORMAT="LINESPECIFIC"MOREINFO="NONE"INSTALL MOREINFO="NONE"<Enter>A menu similar to the one below appears.LABEL="2-4" FLOAT="0"Choose the Desired Server LanguageFILEREF="n41in25a.tif"PERFORMANCE="REQUIRED"Choose the language in which you want the server installed and press MOREINFO="NONE"<Enter>.The "Select the Type of Installation Desired" menu appears.PERFORMANCE="REQUIRED"Choose "NetWare Server Installation" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Go to 
IDREF="FM51075""Name Your Server and Copy Boot Files" on page 30.
PAGENUM=27 ID="BP34"RENDERAS="SECT2"ID="FM64462"Install from a NetWare Volume with Files Copied on a ServerRENDERAS="SECT3"Necessary ResourcesMARK=CHECKBOXAn existing NetWare server with sufficient disk space (at least 170 MB) to store the NetWare 4.1 operating system files. (This will be the host server.)An existing NetWare workstation. (This will be the server you install.)(Conditional) A CD-ROM drive that can read ISO 9660 formatted CD-ROM disks.This is used to copy the NetWare 4.1 files from the CD-ROM to the host server.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Create a NETWARE directory on an existing server and 
copy the 
files from the installation medium to that directory.For example, to copy from CD-ROM drive D: to network drive K:, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"K: MOREINFO="NONE"<Enter> 
MD NETWARE MOREINFO="NONE"<Enter> 
CD NETWARE MOREINFO="NONE"<Enter> 
NCOPY D: /S /E /V 
MOREINFO="NONE"<Enter> To copy from floppy diskettes, perform the NCOPY command shown above for each diskette.PERFORMANCE="REQUIRED"On every computer you want to make a NetWare 4.1 server, create a DOS partition of at least 15 MB.PERFORMANCE="REQUIRED"On every computer you want to make a NetWare 4.1 server, install NetWare DOS client software.For instructions on installing workstation software, refer to 
IDREF="FM32801"Chapter 6, "Install NetWare Clients," on page 263.PERFORMANCE="REQUIRED"On every computer you want to make a NetWare 4.1 server, map a drive to the network server directory that contains the NetWare 4.1 files.
PAGENUM=28 ID="BP35"PERFORMANCE="REQUIRED"At the mapped drive letter, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"INSTALL MOREINFO="NONE"<Enter>A menu similar to the one below appears.LABEL="2-5" FLOAT="0"ID="FM78210"Choose the Desired Server LanguageFILEREF="n41in25a.tif"PERFORMANCE="REQUIRED"Choose the language in which you want the server installed and press MOREINFO="NONE"<Enter>.The "Select the Type of Installation Desired" menu appears.PERFORMANCE="REQUIRED"Choose "NetWare Server Installation" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Go to 
IDREF="FM51075""Name Your Server and Copy Boot Files" on page 30.
PAGENUM=29 ID="BP36"RENDERAS="SECT1"ID="FM80366"Install from IDXID="w2950"BOOK="_idx" COLLECTION="nw41" TIDREF="i1135"
Floppy 
DiskettesRENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Make working copies of all NetWare 4.1 diskettes. For instructions, see 
IDREF="FM75630""Make Working Copies of the Diskettes (Conditional)" on page 12.PERFORMANCE="REQUIRED"Insert the 
CLASS=DISKInstall diskette into drive A:.PERFORMANCE="REQUIRED"Turn on or reboot your computer.The "Select the Type of Installation Desired" menu appears.PERFORMANCE="REQUIRED"Choose "NetWare Server Installation" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Continue with 
IDREF="FM51075""Name Your Server and Copy Boot Files" on page 30.
PAGENUM=30 ID="BP37"RENDERAS="SECT1"ID="FM51075"Name Your Server and Copy Boot FilesIDXID="w2951"BOOK="_idx" COLLECTION="nw41" TIDREF="i843"Once you've selected the language in which the server will be installed, the following menu appears.LABEL="2-6" FLOAT="0"Installation OptionsFILEREF="n41in26a.tif"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Select "NetWare 4.1" and press MOREINFO="NONE"<Enter>.A menu appears displaying additional installation options.PERFORMANCE="REQUIRED"Select "Simple Installation of NetWare 4.1" and press MOREINFO="NONE"<Enter>.A screen appears requesting a server name.PERFORMANCE="REQUIRED"Type the server name in the field provided and press MOREINFO="NONE"<Enter>.For help on rules for naming servers, press 
MOREINFO="NONE"<F1>.The server 
IDXID="w2952"BOOK="_idx" COLLECTION="nw41" TIDREF="i492"IDXID="w2953"BOOK="_idx" COLLECTION="nw41" TIDREF="i843"
boot files are copied to the server.PERFORMANCE="REQUIRED"(Conditional) If you are installing from floppy diskettes, during the copy process, insert the NetWare diskettes into drive A: as prompted and press MOREINFO="NONE"<Enter>.Once the boot files have been copied to the server, if your CONFIG.SYS file does not set a country code, or if the country code is not set at 001 (U.S.), the following 
IDXID="w2954"BOOK="_idx" COLLECTION="nw41" TIDREF="i2048"
screen appears.LABEL="2-7" FLOAT="0"Language Configuration ScreenFILEREF="n41in64a.tif"PAGENUM=31 ID="BP38"PERFORMANCE="REQUIRED"(Conditional) Specify the 
IDXID="w2955"BOOK="_idx" COLLECTION="nw41" TIDREF="i859"
country code, 
IDXID="w2956"BOOK="_idx" COLLECTION="nw41" TIDREF="i669"
code page, and 
IDXID="w2957"BOOK="_idx" COLLECTION="nw41" TIDREF="i2015"
keyboard mapping.For information on any of the settings in this screen, press <F1> or refer to your DOS manual.Use the Up- and Down-arrow keys to maneuver through the screen.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> to view options and select an applicable country code.The "Code Page" filed is highlighted.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> and select an applicable code page.The "Keyboard Mapping" field is highlighted.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> and select an applicable keyboard type.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> to save and continue.A number of boot files are then copied to the DOS partition of the hard disk.PERFORMANCE="REQUIRED"Continue with 
IDREF="FM82220""Load the Disk and CD-ROM Drivers" on page 32.
PAGENUM=32 ID="BP39"RENDERAS="SECT1"ID="FM82220"Load the Disk and CD-ROM DriversThe following screen appears.LABEL="2-8" FLOAT="0"Select Your Disk DriverFILEREF="n41in13a.tif"If you are installing from CD-ROM and the CD-ROM drive is connected to a SCSI adapter shared by another internal or external device (hard disk, tape device, etc.), you may experience a IDXID="w2958"BOOK="_idx" COLLECTION="nw41" TIDREF="i2015"
keyboard lockup problem while loading drivers or copying files.  If this occurs, contact your SCSI adapter manufacturer for updated drivers.A 
disk driver enables communication between the disk controller and the server's CPU. Similarly, a CD-ROM driver enables communication between the CD-ROM and the server's CPU.In some cases, you will need to select a CD-ROM driver as well as a disk driver.PAGENUM=33 ID="BP40"Disk drivers have a description that appears as you highlight the driver. A list of standard Novell€ drivers is shown belowLABEL="2-1" PGWIDE=1 TOCENTRY="1"IDXID="w2959"BOOK="_idx" COLLECTION="nw41" TIDREF="i1229"ID="FM91176" Standard Novell Disk DriversCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="8*"COLNAME=3 COLWIDTH="8*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Computer architectureCOLNAME=2 ROTATE="0" MOREROWS="0"Controller COLNAME=3 ROTATE="0" MOREROWS="0"Disk driver you must loadVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Industry Standard Architecture (ISA)COLNAME=2 ROTATE="0" MOREROWS="0"ATCOLNAME=3 ROTATE="0" MOREROWS="0"ISADISKCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDE (ATA)COLNAME=3 ROTATE="0" MOREROWS="0"IDECOLNAME=1 ROTATE="0" MOREROWS="0"MicrochannelCOLNAME=2 ROTATE="0" MOREROWS="0"ESDICOLNAME=3 ROTATE="0" MOREROWS="0"PS2ESDICOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IBM SCSICOLNAME=3 ROTATE="0" MOREROWS="0"PS2SCSICOLNAME=1 ROTATE="0" MOREROWS="0"Extended Industry Standard Architecture (EISA)COLNAME=2 ROTATE="0" MOREROWS="0"AT classCOLNAME=3 ROTATE="0" MOREROWS="0"ISADISKCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDE (ATA)COLNAME=3 ROTATE="0" MOREROWS="0"IDECOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"EISA vendor proprietaryCOLNAME=3 ROTATE="0" MOREROWS="0"See vendorFor example, if you have an ISA computer, you need to load the IDE disk driver.Besides Novell drivers, additional third-party drivers are also included with NetWare 4.1.If you experience problems with third-party drivers, contact the manufacturer listed in the driver description that appears as you highlight the driver. PAGENUM=34 ID="BP41"RENDERAS="SECT2"ProcedureIf more than one hard disk of the same type is installed in your computer, and if the disks are both connected to the same disk controller, load only one disk driver.  If the disks are connected to different controllers, load the driver multiple times or load additional disk drivers.PERFORMANCE="REQUIRED"ID="FM28319"Choose your disk driver.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If COLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"The driver is listedCOLNAME=2 ROTATE="0" MOREROWS="0"Choose the appropriate disk driver and continue with IDREF="FM30760"Step 2COLNAME=1 ROTATE="0" MOREROWS="0"The driver is not listedCOLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<Ins> and follow the prompts. Then skip to IDREF="FM70322"Step 3The selected disk driver is then copied to the server boot directory before it is loaded.PERFORMANCE="REQUIRED"ID="FM30760"View the displayed parameter settings and verify that they are correct.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Accept the default valuesCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "Save Parameters and Continue." COLNAME=1 ROTATE="0" MOREROWS="0"Change the defaults because they do not match the installed hardwareCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "Select/Modify Driver Parameters and Continue."PAGENUM=35 ID="BP42"A prompt appears asking if you want to load any additional disk drivers.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want to COLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Load additional disk drivers, or load separate CD-ROM driversCOLNAME=2 ROTATE="0" MOREROWS="0"Select "Yes" and press <Enter>. Then repeat IDREF="FM28319"Steps 1 and IDREF="FM30760"2.COLNAME=1 ROTATE="0" MOREROWS="0"Proceed without loading additional disk driversCOLNAME=2 ROTATE="0" MOREROWS="0"Continue with IDREF="FM70322"Step 3PERFORMANCE="REQUIRED"ID="FM70322"Continue with 
IDREF="FM72483""Load the LAN Drivers" on page 36.
PAGENUM=36 ID="BP43"RENDERAS="SECT1"ID="FM72483"Load the LAN DriversAfter you load your disk and CD-ROM drivers, the following screen appears.LABEL="2-9" FLOAT="0"Select Your LAN DriversFILEREF="n41in14a.tif"Loading a LAN driver establishes a network connection (if the server is physically connected to the network cabling). Your choice of 
LAN drivers depends on the cabling system and the network 
board you are using.Most NetWare 4.1 LAN drivers have an individual description that appears on the screen when you choose the driver. Refer to IDREF="FM38136"Table 2-2, on page 37 and to the on-screen descriptions to determine which LAN driver to load.If you experience problems with third-party drivers, contact the manufacturer listed in the driver description that appears as you highlight the driver. LABEL="2-2" PGWIDE=1 TOCENTRY="1"IDXID="w2960"BOOK="_idx" COLLECTION="nw41" TIDREF="i2991"IDXID="w2961"BOOK="_idx" COLLECTION="nw41" TIDREF="i1229"ID="FM38136" Novell LAN DriversCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="13*"COLNAME=3 COLWIDTH="10*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ID="FM85625"Cabling systemCOLNAME=2 ROTATE="0" MOREROWS="0"Network boardCOLNAME=3 ROTATE="0" MOREROWS="0"LAN driver you must loadVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ARCnet*COLNAME=2 ROTATE="0" MOREROWS="0"RX-NetCOLNAME=3 ROTATE="0" MOREROWS="0"TRXNET.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"RX-Net IICOLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"RX-Net/2COLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"EthernetCOLNAME=2 ROTATE="0" MOREROWS="0"NE/2  NE/2T COLNAME=3 ROTATE="0" MOREROWS="0"NE2.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE/2-32COLNAME=3 ROTATE="0" MOREROWS="0"NE2_32.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE1000 - ASSY 950-054401  NE1000 - ASSY 810-160-001COLNAME=3 ROTATE="0" MOREROWS="0"NE1000.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE2000 - ASSY 810-149  NE2000T - ASSY 810-000220COLNAME=3 ROTATE="0" MOREROWS="0"NE2000.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE2100 - ASSY 810-000209COLNAME=3 ROTATE="0" MOREROWS="0"NE2100.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE1500T - ASSY 810-000214  (twisted-pair version of NE2100)COLNAME=3 ROTATE="0" MOREROWS="0"NE1500T.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE3200COLNAME=3 ROTATE="0" MOREROWS="0"NE3200.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE32HUBCOLNAME=3 ROTATE="0" MOREROWS="0"NE32HUB.LANCOLNAME=1 ROTATE="0" MOREROWS="0"Token RingCOLNAME=2 ROTATE="0" MOREROWS="0"NTR2000COLNAME=3 ROTATE="0" MOREROWS="0"NTR2000.LANPAGENUM=37 ID="BP44"For example, if you have a Novell NE2100TM network board installed in your computer, you must load the NE2100.LAN driver.PAGENUM=38 ID="BP45"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"ID="FM52245"Choose your LAN driver.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="14*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If COLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"The driver is listedCOLNAME=2 ROTATE="0" MOREROWS="0"Choose the appropriate LAN driver and continue with IDREF="FM30760"Step 2COLNAME=1 ROTATE="0" MOREROWS="0"The driver is not listedCOLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<Ins> and follow the prompts. Then continue with IDREF="FM30760"Step 2.The selected LAN driver is then copied and stored temporarily in the C: drive before it is loaded.PERFORMANCE="REQUIRED"View the displayed LAN driver parameter settings and verify that they are correct.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Accept the default valuesCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "Save Parameters and Continue."COLNAME=1 ROTATE="0" MOREROWS="0"Change the defaults because they are incomplete or they conflict with other hardware settingsCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "Select/Modify Driver Parameters" and enter the settings.Exit the screen by pressing MOREINFO="NONE"<Esc>.Continue with IDREF="FM97996"Step 3A prompt appears asking if you want to select additional network drivers.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Load additional LAN driversCOLNAME=2 ROTATE="0" MOREROWS="0"Select "Yes" and press MOREINFO="NONE"<Enter>. Then repeat IDREF="FM52245"Steps 1 and IDREF="FM30760"2.COLNAME=1 ROTATE="0" MOREROWS="0"Proceed without loading additional LAN driversCOLNAME=2 ROTATE="0" MOREROWS="0"Continue with IDREF="FM97996"Step 3The "Load Server Drivers" screen appears with the selected disk and LAN drivers displayed.
PAGENUM=39 ID="BP46"LABEL="2-10" FLOAT="0"Selected Drivers Are Displayed Prior to Being LoadedFILEREF="n41in36a.tif"If you want to modify the settings of any previously selected disk or LAN drivers, or load additional disk or LAN drivers, you may do so through the "Select Additional or Modify Selected Disk/LAN Drivers" option.PERFORMANCE="REQUIRED"ID="FM97996"From the "Driver Actions" menu, choose "Continue Installation."At this time, NetWare 4.1 loads the Ethernet 802.2, Ethernet 802.3, Ethernet SNAP, and Ethernet II frame types. The installation utility will later bind the IPX protocol to 
only the frame types found on the network.If you are installing from CD-ROM, the following screen may appear.LABEL="2-11" FLOAT="0"ID="FM52132"You Can Try to Mount the CD-ROM as a NetWare VolumeFILEREF="n41in41a.tif"PERFORMANCE="REQUIRED"(Conditional) If you are installing from CD-ROM and the menu in 
IDREF="FM52132"Figure 2-11 appears, choose one of the menu options.If a disk or CD-ROM driver you selected earlier conflicts with the DOS CD-ROM driver, your 
IDXID="w2962"BOOK="_idx" COLLECTION="nw41" TIDREF="i2015"
keyboard may lock up during installation. To avoid this, you can attempt to 
IDXID="w2963"BOOK="_idx" COLLECTION="nw41" TIDREF="i2523"
mount the CD-ROM as a NetWare volume. In doing so, you may be prompted to install new disk or CD-ROM drivers.PERFORMANCE="REQUIRED"Continue with 
IDREF="FM41080""Install the License and Create NetWare Disk Partitions" on page 40.
PAGENUM=40 ID="BP47"RENDERAS="SECT1"ID="FM41080"Install the License and Create NetWare Disk
PartitionsIDXID="w2964"BOOK="_idx" COLLECTION="nw41" TIDREF="i1825"IDXID="w2965"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"Once all drivers have been loaded, the following screen appears prompting you to insert your CLASS=DISKLicense diskette.LABEL="2-12" FLOAT="0"License Diskette PromptFILEREF="n41in91a.tif"If your server's hard disk contains existing nonbootable disk partitions, a message appears telling you so.  Decide whether you want to delete existing nonbootable disk partitions and make them part of the NetWare partition, or save them and exclude them from being part of the NetWare partition.Selecting "Yes" will delete any extended DOS partitions you may have. PAGENUM=41 ID="BP48"RENDERAS="SECT2"ID="FM15916"NetWare Partition OverviewEvery NetWare 4.1 server needs a disk partition for NetWare files and shared data. You can have only one NetWare 4.1 disk partition per disk, but you can have up to eight volume segments on the NetWare disk partition.If your server's primary hard disk has a DOS partition, use the rest of the IDXID="w2966"BOOK="_idx" COLLECTION="nw41" TIDREF="i873"
disk space as a IDXID="w2967"BOOK="_idx" COLLECTION="nw41" TIDREF="i1126"
NetWare disk partition.LABEL="2-13" FLOAT="0"IDXID="w2968"BOOK="_idx" COLLECTION="nw41" TIDREF="i1124"Disk Partitions and Volumes on an Internal Hard DiskFILEREF="n40in11a.tif"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"(Conditional) If prompted whether to delete existing nonbootable partitions, choose "Yes" or "No" and press MOREINFO="NONE"<Enter>.To maximize your NetWare disk partition space, delete all nonbootable disk partitions. Press <Alt>+<F10> to exit the installation, then back up any files you wish to keep and start the installation again.PERFORMANCE="REQUIRED"When prompted, insert the 
CLASS=DISKLicense diskette and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"When prompted that the license is installed successfully, press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Remove the 
CLASS=DISKLicense diskette and store it in a safe place.
PAGENUM=42 ID="BP49"If you are installing from CD-ROM (not from a remote installation area) or from floppy diskettes, NetWare begins copying the files needed for the installation utility to continue.LABEL="2-14" FLOAT="0"The Files Needed to Continue are CopiedFILEREF="n41in89a.tif"PERFORMANCE="REQUIRED"If you are installing from a network volume, continue with 
IDREF="FM74247""Establish the Server-to-Server Session (Conditional)" on page 43; otherwise, continue with 
IDREF="FM34943""Install NetWare Directory Services" on page 45.
PAGENUM=43 ID="BP50"RENDERAS="SECT1"ID="FM74247"Establish the Server-to-Server Session (Conditional)If you are installing from a remote network installation area, the following screen appears.LABEL="2-15" FLOAT="0"Enter Your Password to Reconnect to the Source ServerFILEREF="n41in10a.tif"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Reenter your password to reconnect to the source server, and press MOREINFO="NONE"<Enter>.When installing 
IDXID="w2969"BOOK="_idx" COLLECTION="nw41" TIDREF="i4067"
from a remote network installation area, a client connection to the source server is disrupted once the LAN driver is loaded.The path to the source server is saved in memory, but the password must be reentered.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> again.The copying process begins.
PAGENUM=44 ID="BP51"LABEL="2-16" FLOAT="0"The Files Needed to Continue are CopiedFILEREF="n41in89a.tif"PERFORMANCE="REQUIRED"Continue with 
IDREF="FM34943""Install NetWare Directory Services" on page 45.
PAGENUM=45 ID="BP52"RENDERAS="SECT1"ID="FM34943"Install NetWare Directory ServicesIDXID="w2970"BOOK="_idx" COLLECTION="nw41" TIDREF="i2727"
Once the appropriate files have been copied to the server, the network is scanned for Directory trees. Unless you are installing the first NetWare 4 server in the network, you will most likely want to install the server into an existing Directory tree.Based on your network configuration, one of the following screens appears.LABEL="2-17" FLOAT="0"ID="FM25148"When No Directory Tree Is LocatedFILEREF="n41i112a.tif"If no NetWare 4 server (and accompanying Directory tree) can be located on the network, the menu shown above appears.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If COLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"The menu in IDREF="FM25148"Figure 2-17 appearsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM37832""Nonlocatable Directory Tree, or First Server" on page 47.PAGENUM=46 ID="BP53"LABEL="2-18" FLOAT="0"ID="FM82255"When a Single Directory Tree Is LocatedFILEREF="n41i103a.tif"If a single Directory tree is located, the Directory tree name is displayed as in the menu above.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IfCOLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"The menu in IDREF="FM82255"Figure 2-18 appearsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM80633""A Single Directory Tree Is Located" on page 51.LABEL="2-19" FLOAT="0"ID="FM42370"When Multiple Directory Trees are LocatedFILEREF="n41in59a.tif"If multiple Directory trees are located, the menu shown above appears.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If COLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"The menu in IDREF="FM42370"Figure 2-19 appearsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM72796""Multiple Directory Trees are Found" on page 144. (Located in IDREF="FM44025"Chapter 3, "Custom Installation." )PAGENUM=47 ID="BP54"RENDERAS="SECT2"ID="FM37832"Nonlocatable Directory Tree, or First ServerThe menu below appears if there is no IDXID="w2971"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"
previously installed NetWare 4 server, or if the server you are installing cannot see the previously installed NetWare 4 server(s).LABEL="2-20" FLOAT="0"When No Directory Tree Is LocatedFILEREF="n41i112a.tif"RENDERAS="SECT3"ID="FM76223"If the Server Cannot Locate a Previously Installed Directory TreeRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the "Is This the First NetWare 4 Server?" menu, choose "No, Connect to Existing NetWare 4 Network" and press MOREINFO="NONE"<Enter>.The following menu appears.LABEL="2-21" FLOAT="0"Select NetWare 4 Network MenuFILEREF="n41i114a.tif"You can find out the network name by loading MONITOR.NLM on an existing server on the network. The network name is the same as the Directory tree name.PAGENUM=48 ID="BP55"PERFORMANCE="REQUIRED"ID="FM20731"Select one of the menu optionsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If COLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"You have verified that an existing NetWare 4 server is up and physically connected to the network, and that both servers are bound to IPX with the proper LAN driver, frame type, and IPX external network numberCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "Recheck for NetWare 4 Network" and press MOREINFO="NONE"<Enter>.If a single Directory tree is located, go to IDREF="FM80633""A Single Directory Tree Is Located" on page 51.If multiple Directory trees are located, go to IDREF="FM72796""Multiple Directory Trees are Found" on page 144. (Located in IDREF="FM44025"Chapter 3, "Custom Installation." )COLNAME=1 ROTATE="0" MOREROWS="0"Your network has IDXID="w2972"BOOK="_idx" COLLECTION="nw41" TIDREF="i3946"
SAP filtering and you know the IPX internal network number of an existing NetWare 4 serverCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "Specify Address of NetWare 4 Server" and press <Enter>.Enter the name of the Directory tree and press MOREINFO="NONE"<Enter>.Enter the IPX internal network number of an existing NetWare 4 server in the Directory tree and press MOREINFO="NONE"<Enter>.If a single Directory tree is located, go to IDREF="FM80633""A Single Directory Tree Is Located" on page 51.If multiple trees are located, go to IDREF="FM72796""Multiple Directory Trees are Found" on page 144. (Located in IDREF="FM44025"Chapter 3, "Custom Installation." )PAGENUM=49 ID="BP56"RENDERAS="SECT3"If This Is the First NetWare 4 Server in the Directory TreeRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Choose "Yes, This Is the IDXID="w2973"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"
First NetWare 4 Server" and press MOREINFO="NONE"<Enter>. A list of time zones appear.PERFORMANCE="REQUIRED"ID="FM54535"Choose the time zone where the server will be installed and press MOREINFO="NONE"<Enter>.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If COLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"The time zone is listedCOLNAME=2 ROTATE="0" MOREROWS="0"Move the cursor to the time zone and press MOREINFO="NONE"<Enter>. COLNAME=1 ROTATE="0" MOREROWS="0"The time zone is not listedCOLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<Ins> and fill out the "Verify/Enter Time Configuration Information for This Server" screen.Note: An explanation of this screen can be found in IDREF="FM44025"Chapter 3, "Custom Installation."  beginning with IDREF="FM77174"Step 3b on page 132.Once entered, continue with IDREF="FM71020"Step 3 below. The following screen appears, requesting your NetWare Directory Services (NDS) Organization name.LABEL="2-22" FLOAT="0"Enter Your Organization NameFILEREF="n41i113a.tif"PERFORMANCE="REQUIRED"ID="FM71020"Enter the name of your organization and press MOREINFO="NONE"<Enter>.Your NDS 
IDXID="w2974"BOOK="_idx" COLLECTION="nw41" TIDREF="i3113"
Organization name can be your company, division or department name. It will also be the name of your Directory tree.Once you have entered the NDS Organization name and pressed MOREINFO="NONE"<Enter>, a screen appears requesting your administrator password.
PAGENUM=50 ID="BP57"PERFORMANCE="REQUIRED"ID="FM67661"Enter the administrator password and press MOREINFO="NONE"<Enter>.You will need this 
IDXID="w2975"BOOK="_idx" COLLECTION="nw41" TIDREF="i122"
password later to log in and administer the network.If you forget the administrator password, you will have to reinstall. This password is also the password for the bindery user IDXID="w2976"BOOK="_idx" COLLECTION="nw41" TIDREF="i4330"
SUPERVISOR. If you change the administrator password later, the SUPERVISOR password will not change until you change it using the SYSCON utility.PERFORMANCE="REQUIRED"At the prompt, retype the password and press MOREINFO="NONE"<Enter> to continue.PERFORMANCE="REQUIRED"ID="FM47822"Go to 
IDREF="FM69725""Copy Remaining NetWare Files" on page 54.
PAGENUM=51 ID="BP58"RENDERAS="SECT2"ID="FM80633"A Single Directory Tree Is LocatedIf, after scanning the network, a IDXID="w2977"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"
single Directory tree is located, the tree name is displayed along with the following menu.LABEL="2-23" FLOAT="0"When a Single Directory Tree Is LocatedFILEREF="n41i103a.tif"Depending on its structure, the displayed Directory tree can be either a "simple" tree (only one level) or a "custom" tree (multilevel).RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Choose an option from the menu.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If COLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"You want to install into the displayed Directory treeCOLNAME=2 ROTATE="0" MOREROWS="0"Go to IDREF="FM19443""Install into a Displayed Directory Tree" on page 52.COLNAME=1 ROTATE="0" MOREROWS="0"You want to install into a Directory tree that is not displayedCOLNAME=2 ROTATE="0" MOREROWS="0"Go to IDREF="FM76223""If the Server Cannot Locate a Previously Installed Directory Tree" on page 47.COLNAME=1 ROTATE="0" MOREROWS="0"You want to create a new Directory treeCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "Select Another Tree" and press MOREINFO="NONE"<Enter>.Press <Ins>.At the confirmation prompt, press MOREINFO="NONE"<Enter>.Follow the procedures under IDREF="FM96975""If This Is the First NetWare 4 Server" on page 131. (Located in IDREF="FM44025"Chapter 3, "Custom Installation." )PAGENUM=52 ID="BP59"RENDERAS="SECT2"ID="FM19443"Install into a Displayed Directory TreeInstall the new NetWare 4.1 server into the Directory tree displayed in the menu below, by following the procedures that follow.LABEL="2-24" FLOAT="0"When a Single Directory Tree is LocatedFILEREF="n41i103a.tif"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Choose "Install into Tree tree name" and press MOREINFO="NONE"<Enter>.A list of time zones appear.PERFORMANCE="REQUIRED"Choose the time zone where the server will be installed and press MOREINFO="NONE"<Enter>.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If COLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"The time zone is listedCOLNAME=2 ROTATE="0" MOREROWS="0"Move the cursor to the time zone and press MOREINFO="NONE"<Enter>. COLNAME=1 ROTATE="0" MOREROWS="0"The time zone is not listedCOLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<Ins> and fill out the "Verify/Enter Time Configuration Information for This Server" screen.Note: An explanation of this screen can be found in IDREF="FM44025"Chapter 3, "Custom Installation."  beginning with IDREF="FM77174"Step 3b on page 132.Once entered, continue with the procedures below.PAGENUM=53 ID="BP60"One of the following screens appears.LABEL="2-25" FLOAT="0"IDXID="w2978"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"IDXID="w2979"BOOK="_idx" COLLECTION="nw41" TIDREF="i4155"ID="FM41432"When a Simple Directory Tree Is LocatedFILEREF="n41in06a.tif"LABEL="2-26" FLOAT="0"IDXID="w2980"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"IDXID="w2981"BOOK="_idx" COLLECTION="nw41" TIDREF="i902"ID="FM30834"When a Custom Directory Tree Is LocatedFILEREF="n41in07a.tif"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If COLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"The screen in IDREF="FM41432"Figure 2-25  appearsCOLNAME=2 ROTATE="0" MOREROWS="0"Type the administrator password and press MOREINFO="NONE"<Enter>.Continue with IDREF="FM69725""Copy Remaining NetWare Files" on page 54.COLNAME=1 ROTATE="0" MOREROWS="0"The screen in IDREF="FM30834"Figure 2-26  appearsCOLNAME=2 ROTATE="0" MOREROWS="0"If necessary, type the administrator name and press MOREINFO="NONE"<Enter>.Type the administrator password and press MOREINFO="NONE"<Enter>.Go to IDREF="FM57773"page 138page 138 in IDREF="FM44025"Chapter 3, "Custom Installation,"  and complete IDREF="FM57773"Steps 4a through IDREF="FM41118"4e.Then continue with IDREF="FM69725""Copy Remaining NetWare Files" on page 54.COLNAME=1 ROTATE="0" MOREROWS="0"The screen in IDREF="FM41432"Figure 2-25  appears and you wish to make the simple Directory tree a custom (multilevel) treeCOLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<F4>.If necessary, type the administrator name and press MOREINFO="NONE"<Enter>.Type the administrator password and press MOREINFO="NONE"<Enter>.Go to IDREF="FM57773"page 138 in IDREF="FM44025"Chapter 3, "Custom Installation,"  and complete IDREF="FM57773"Steps 4a through IDREF="FM41118"4e.Then continue with IDREF="FM69725""Copy Remaining NetWare Files" on page 54.PAGENUM=54 ID="BP61"RENDERAS="SECT1"ID="FM69725"Copy Remaining NetWare FilesOnce NetWare Directory Services has been installed, NetWare begins copying the remaining NetWare files to IDXID="w2982"BOOK="_idx" COLLECTION="nw41" TIDREF="i843"
volume IDXID="w2983"BOOK="_idx" COLLECTION="nw41" TIDREF="i4793"
SYS:. This could take a few minutes.LABEL="2-27" FLOAT="0"The Remaining NetWare Files Are CopiedFILEREF="n41in90a.tif"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"(Optional) Review IDREF="FM32778""What Does the Directory Tree Look Like Now?" on page 55 and IDREF="FM71821""What Trustee Assignments Were Created During this Installation?" on page 56.PERFORMANCE="REQUIRED"Continue with 
IDREF="FM64334""Other Installation Options (Optional)" on page 57, or skip to 
IDREF="FM64994""Exit the Installation Utility" on page 62.
PAGENUM=55 ID="BP62"RENDERAS="SECT3"ID="FM32778"What Does the Directory Tree Look Like Now?The following IDXID="w2984"BOOK="_idx" COLLECTION="nw41" TIDREF="i3042"
objects were created in the Directory tree: MARK=BULLETIDXID="w2985"BOOK="_idx" COLLECTION="nw41" TIDREF="i4044"
Server object.IDXID="w2986"BOOK="_idx" COLLECTION="nw41" TIDREF="i4787"
Volume objects (servername_SYS and other volumes you specified).User object IDXID="w2987"BOOK="_idx" COLLECTION="nw41" TIDREF="i118"
ADMIN (the IDXID="w2988"BOOK="_idx" COLLECTION="nw41" TIDREF="i122"
administrator who has Supervisor object rights to this context). This object is placed directly under the Organization level. User object ADMIN is created only once, and only on the first server in the tree.User object IDXID="w2989"BOOK="_idx" COLLECTION="nw41" TIDREF="i4330"
Supervisor (for bindery services purposes only). This object is recognized only by pre-NetWare 4.1 utilities. User object Supervisor takes on User object ADMIN's password. These objects are placed in the same context you defined for your server. The following illustration shows what your IDXID="w2990"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"
Directory tree might look like after you installed your first NetWare 4.1 server.FILEREF="n41in15a.tif"PAGENUM=56 ID="BP63"RENDERAS="SECT3"ID="FM71821"What IDXID="w2991"BOOK="_idx" COLLECTION="nw41" TIDREF="i4593"IDXID="w2992"BOOK="_idx" COLLECTION="nw41" TIDREF="i3995"
Trustee IDXID="w2993"BOOK="_idx" COLLECTION="nw41" TIDREF="i3853"
Assignments Were Created During this IDXID="w2994"BOOK="_idx" COLLECTION="nw41" TIDREF="i960"
Installation?MARK=BULLETUser IDXID="w2995"BOOK="_idx" COLLECTION="nw41" TIDREF="i3042"
object IDXID="w2996"BOOK="_idx" COLLECTION="nw41" TIDREF="i118"
ADMIN has the Supervisor object right on the [Root] object. By inheritance, ADMIN also has the Supervisor right on all Volume objects in the Directory.IDXID="w2997"BOOK="_idx" COLLECTION="nw41" TIDREF="i35"
[Public] has the Browse right on the [Root] object.[Public] is equal to the group EVERYONE in the NetWare 3 environment. Any IDXID="w2998"BOOK="_idx" COLLECTION="nw41" TIDREF="i810"
container object has Read and File Scan rights to the PUBLIC directories of all system volumes in that container.The [Root] object (or security equivalent) of a tree has:MARK=BULLETThe Browse right on all User objects in that tree. This can be blocked by an Inherited Rights Filter or removed from a container's Access Control List (ACL).The Read right to the Member property of any Group object.The Read right to the following properties of any Volume object: Host Server Name (the server that the physical volume resides on) and Host Resource (the physical volume).All IDXID="w2999"BOOK="_idx" COLLECTION="nw41" TIDREF="i4715"
User objects have the Read right to their own properties and to the properties of any profile they belong to. User objects also have Read and Write rights to their user login script. For more information on rights and trustee assignments, see "BOOK="cncptenu" COLLECTION="nw41"Rights" and "BOOK="cncptenu" COLLECTION="nw41"Trustee" in Concepts and Chapter 2, "BOOK="superenu" COLLECTION="nw41"Managing Directories, Files, and Applications," and Chapter 3, "BOOK="superenu" COLLECTION="nw41"Creating Login Scripts," in Supervising the Network.PAGENUM=57 ID="BP64"RENDERAS="SECT1"ID="FM64334"Other Installation Options (Optional)Once all NetWare files have been copied to volume SYS:, the following screen appears listing other available installation options.LABEL="2-28" FLOAT="0"ID="FM14109"Other Installation OptionsFILEREF="n41in45a.tif"All of the options listed above may be done any time from the server by loading INSTALL.NLM at the server console.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If COLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"You want to perform any of the listed installation actions at this timeCOLNAME=2 ROTATE="0" MOREROWS="0"Follow the procedures under the headings that follow.COLNAME=1 ROTATE="0" MOREROWS="0"You do not want to perform any of the listed installation actions at this timeCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "Continue Installation" from the "Other Installation Actions" menu and press MOREINFO="NONE"<Enter>.After being prompted that the installation is complete, press MOREINFO="NONE"<Enter> to access the server console.Go to IDREF="FM96605""Where to Go from Here" on page 62.PAGENUM=58 ID="BP65"RENDERAS="SECT2"Create a IDXID="w3000"BOOK="_idx" COLLECTION="nw41" TIDREF="i3564"IDXID="w3001"BOOK="_idx" COLLECTION="nw41" TIDREF="i3726"
Registration DisketteHaving a CLASS=DISKRegistration diskette is useful in case you experience system problems in the future and must call Novell Technical SupportSM.The installation program can read information such as OS version, addresses, number of licensed connections, SFT level, amount of RAM installed, network board configuration, and disk drive configuration, and copy this information to the CLASS=DISKRegistration diskette.This might be useful in case you experience system problems in the future and need to call Novell Technical Support. Novell support technicians can access the above information, which greatly speeds up their ability to help you.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Other Installation Actions" menu, select "Choose an Item or Product Listed" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Choose "Create a Registration Diskette" and press MOREINFO="NONE"<Enter>.The screen that appears lists three prerequisites:
MARK=BULLETThe NetWare 4.1 CLASS=DISKRegistration disketteThe name and address of your Novell Authorized ResellerCLMYour company's reseller contact (the person in your company in responsible for purchases).PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to continue.PERFORMANCE="REQUIRED"In the "Reseller Information" form that appears, fill in the name and address of the Novell Authorized Reseller you purchased NetWare 4.1 from. PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Press
MOREINFO="NONE" <Enter> after each entry. PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to continue. PERFORMANCE="REQUIRED"In the "Customer Information" form, fill in the reseller contact's name and the name of your company (or organization).PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Press
MOREINFO="NONE" <Enter> after each entry. PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to continue. 
PAGENUM=59 ID="BP66"PERFORMANCE="REQUIRED"Insert the
IDXID="w3002"BOOK="_idx" COLLECTION="nw41" TIDREF="i843"
CLASS=DISKRegistration diskette into drive A: and press MOREINFO="NONE"<Enter>. The installation program now copies the registration information to this diskette.PERFORMANCE="REQUIRED"(Optional) Copy 
IDXID="w3003"BOOK="_idx" COLLECTION="nw41" TIDREF="i738"IDXID="w3004"BOOK="_idx" COLLECTION="nw41" TIDREF="i1135"
configuration information to the 
CLASS=DISKRegistration diskette. PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F2> to view configuration information.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to exit the screen.PERFORMANCE="REQUIRED"When asked "Copy This Information to the Diskette?" choose "Yes" or "No."PERFORMANCE="REQUIRED"Insert the 
CLASS=DISKRegistration diskette into the mailer labeled "Product Registration" and send it to Novell.PERFORMANCE="REQUIRED"Continue performing any additional installation options listed on 
IDREF="FM88888"pages 60 through 
IDREF="FM83190"61, or go to 
IDREF="FM64994""Exit the Installation Utility" on page 62.
PAGENUM=60 ID="BP67"RENDERAS="SECT2"ID="FM88888"Create DOS/MS Windows/OS2 Client Install DiskettesIf you don't want to make IDXID="w3005"BOOK="_idx" COLLECTION="nw41" TIDREF="i1135"IDXID="w3006"BOOK="_idx" COLLECTION="nw41" TIDREF="i646"
client diskettes at this time, you can make them later from the server by loading INSTALL.NLM or from a workstation by running MAKEDISK.BAT. (See IDREF="FM56136"Appendix D, "Creating Client Diskettes," on page 293.)RENDERAS="SECT3"PrerequisitesFormat the appropriate number of high-density diskettes using the table below.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For COLNAME=2 ROTATE="0" MOREROWS="0"FormatVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"DOS/MS Windows workstationsCOLNAME=2 ROTATE="0" MOREROWS="0"Five 3.5-inch or 5.25-inch diskettesCOLNAME=1 ROTATE="0" MOREROWS="0"OS/2 workstationsCOLNAME=2 ROTATE="0" MOREROWS="0"Six 3.5-inch diskettesRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Other Installation Actions" menu, select "Choose an Item or Product Listed Above" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Choose "Create DOS/MS Windows/OS2 Client Install Diskettes" and press MOREINFO="NONE"<Enter>.The following menu appears.LABEL="2-29" FLOAT="0"Select the Client Files You Want to Copy to DisketteFILEREF="n41i115a.tif"PERFORMANCE="REQUIRED"Select or deselect the file groups you want copied by pressing MOREINFO="NONE"<Enter>. PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to accept the marked groups and continue.
PAGENUM=61 ID="BP68"PERFORMANCE="REQUIRED"Specify the destination that the client files will be copied to. By default, the client files are copied to drive A:. To specify a new path, press 
MOREINFO="NONE"<F3> and type the new path.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> to accept the path.PERFORMANCE="REQUIRED"Insert the labeled diskettes as prompted.PERFORMANCE="REQUIRED"Continue performing any additional installation options listed below, or go to 
IDREF="FM64994""Exit the Installation Utility" on page 62.RENDERAS="SECT2"Create NetWare CLASS=DISKUpgrade/Migrate DiskettesThis option allows system administrators to create the diskettes necessary to upgrade an existing NetWare 2.x, 3.x, or 4.x server to NetWare 4.1.For procedures on using this option, see 
BOOK="upmigenu" COLLECTION="nw41"Upgrade.RENDERAS="SECT2"ID="FM83190"Install Online Documentation and ViewersIDXID="w3007"BOOK="_idx" COLLECTION="nw41" TIDREF="i3074"IDXID="w3008"BOOK="_idx" COLLECTION="nw41" TIDREF="i1825"
This option installs the NetWare 4.1 online manual set and DynaText* viewers on the NetWare 4.1 server. Entire NetWare 4.1 online manual sets are available in English, French, Italian, German, and Spanish.Be aware that a single language manual set requires 60 MB of free server disk space.For complete instructions on installing the online documentation and viewers, see BOOK="docinenu" COLLECTION="nw41"Installing and Using Novell Online Documentation for NetWare 4.1.PAGENUM=62 ID="BP69"RENDERAS="SECT1"ID="FM64994"Exit the Installation UtilityThe installation of the NetWare 4.1 server is now complete.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"To exit the installation utility and return to the server console, press MOREINFO="NONE"<Enter>. PERFORMANCE="REQUIRED"Continue with "
IDREF="FM96605"Where to Go from Here."RENDERAS="SECT1"ID="FM96605"Where to Go from HereCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Install additional NetWare 4.1 serversCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM50906""Install Server Software" on page 18.COLNAME=1 ROTATE="0" MOREROWS="0"Install NetWare clientsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM32801"Chapter 6 "Install NetWare Clients" on IDREF="FM32801"page 263.COLNAME=1 ROTATE="0" MOREROWS="0"Install NetWare SFT IIICOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM38629"Chapter 5, "Install NetWare 4.1 SFT III," on page 237.LABEL="3"PAGENUM=63 ID="BP70"ID="FM44025"Custom InstallationThe "Custom Installation" option allows you to customize your installation of NetWare® 4.1 by allowing you to change the defaults for any of the following configuration options.MARK=CHECKBOXBooting the server from boot diskettes or a DOS partition on the hard diskAssigning a specific IPX internal network number yourself Partitioning hard disksMirroring hard disksSpecifying volume namesSpanning volumes across multiple drivesModifying time zone parameters in NetWare Directory ServicesTMEditing the AUTOEXEC.NCF and STARTUP.NCF filesSelecting nonrouting TCP/IP or AppleTalk* protocols in addition to IPXIf you determine that you don't need any of the options listed above, install NetWare 4.1 by following the "Simple Installation" procedures in IDREF="FM90747"Chapter 2, "Simple Installation," on IDREF="FM90747"page 15.PAGENUM=64 ID="BP71"RENDERAS="SECT1"Prerequisite TasksMARK=CHECKBOXPlan your Directory tree. See BOOK="getstenu" COLLECTION="nw41"Introduction to NetWare Directory Services for guidelines and suggestions.If your computer has never been a server before, complete the tasks explained in IDREF="FM43011"Chapter 1, "Prepare Your Site and Equipment," on IDREF="FM43011"page 1.Run the computer's Setup program and set the computer's time to the exact local time. (The time synchronization feature in NetWare Directory ServicesTM uses the computer's time setting.)If you install from another server, make sure the new server is cabled to the network and has the NetWare client software installed.If you intend to boot the server from a DOS partition, create a DOS partition of at least 15 MB on your hard disk.If you need to partition and format your hard disk, boot from the NetWare IDXID="w3009"BOOK="_idx" COLLECTION="nw41" TIDREF="i1135"
CLASS=DISKLicense 
diskette and type IDXID="w3010"BOOK="_idx" COLLECTION="nw41" TIDREF="i1439"IDXID="w3011"BOOK="_idx" COLLECTION="nw41" TIDREF="i1636"
FDISK to repartition the hard disk. After rebooting, type IDXID="w3012"BOOK="_idx" COLLECTION="nw41" TIDREF="i1551"IDXID="w3013"BOOK="_idx" COLLECTION="nw41" TIDREF="i1636"
FORMAT to format the partition.A 15MB DOS partition should be sufficient for storing the files needed to boot your server. If you need to store additional files on the DOS partition, you may want to make the partition larger.Installation is much easier when you install with the intention of booting the server from a DOS partition on the server's hard disk. However, If you want to boot the server from floppy diskettes, you do not need a DOS partition.For procedures on installing the server to boot from floppy diskette, see IDREF="FM28298"Appendix C, "Install To Boot From Floppy Diskette," on page 281.Reformatting your hard disk erases all stored files. Be sure to back up your hard disk prior to partitioning and formatting.PAGENUM=65 ID="BP72"RENDERAS="SECT1"Suggested ResourcesMARK=CHECKBOXThe NetWare Server Installation quick path card for an overview of the process.A copy of the NetWare Server Worksheet (located on IDREF="FM68531"page 175).The NetWare CLASS=DISKLicense diskette.One of the following:MARK=BULLETNetWare 4.1 CD-ROMs.Working copies of NetWare 4.1 diskettes.Access to NetWare 4.1 installation files on another server (the CLASS=DISKNetWare 4.1 Operating System CD-ROM mounted as a NetWare volume, or an image of the CD-ROM on another server).PAGENUM=66 ID="BP73"RENDERAS="SECT1"ID="FM43309"ID="FM46642"ID="FM41144"Install the Server SoftwareIDXID="w3014"BOOK="_idx" COLLECTION="nw41" TIDREF="i4044"Install your NetWare 4.1 server software by following the procedures in the sections that follow.RENDERAS="SECT2"ID="FM63016"Choose an Installation MediumYou can install a NetWare 4.1 server from CD-ROM, from floppy diskettes (available only through the NetWare Fulfillment Center), or from a remote network installation area.If you are installing the first in a series of NetWare 4.1 servers on a new network, you must install from CD-ROM or from floppy diskettes.IDREF="FM38091"Figure 3-1 lists factors to consider before choosing an installation medium.LABEL="3-1" FLOAT="0"ID="FM38091"Installation MediaFILEREF="n41in03a.tif"PAGENUM=67 ID="BP74"RENDERAS="SECT2"Choose a Server Boot MethodIn most cases, proper physical security measures, combined with the security features in NetWare 4.1, should be sufficient for your security needs.Though not typically recommended, as a possible additional security measure, you can make the server bootable from a pair of diskettes, rather than from a DOS partition on the hard drive.You can then store the boot diskettes in a secure place and be assured that no one but you can boot the server.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"To boot your server fromCOLNAME=2 ROTATE="0" MOREROWS="0"Continue with VALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"A DOS partition on the hard diskCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM16976""Installing from CD-ROM," on page 68orIDREF="FM54169""Installing from a Remote Network Installation Area," on page 70or IDREF="FM43776""Installing from Floppy Diskettes," on page 77.COLNAME=1 ROTATE="0" MOREROWS="0"Floppy diskettesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM28298"Appendix C, "Install To Boot From Floppy Diskette," on page 281.PAGENUM=68 ID="BP75"RENDERAS="SECT1"ID="FM16976"Installing from CD-ROMIDXID="w3015"BOOK="_idx" COLLECTION="nw41" TIDREF="i603"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"If you have not done so already, install the CD-ROM drive and drivers according to the manufacturer's instructions. Usually, the installation program for your CD-ROM will automatically update the CONFIG.SYS and AUTOEXEC.BAT files to add the CD-ROM device driver.If not, follow the manufacturer's instructions to create or update these files.PERFORMANCE="REQUIRED"Insert the 
CLASS=DISKNetWare 4.1 Operating System CD-ROM into the CD-ROM drive.PERFORMANCE="REQUIRED"Reboot the computer.Rebooting, the computer executes the CONFIG.SYS and AUTOEXEC.BAT files and recognizes the CD-ROM drive as a DOS device.PERFORMANCE="REQUIRED"Change to the drive letter corresponding to the CD-ROM.This is generally drive D:.PERFORMANCE="REQUIRED"Type 
FORMAT="LINESPECIFIC"MOREINFO="NONE"INSTALL MOREINFO="NONE"<Enter>A menu similar to the following appears.LABEL="3-2" FLOAT="0"Choose the Desired Server LanguageFILEREF="n41in25a.tif"PAGENUM=69 ID="BP76"PERFORMANCE="REQUIRED"Choose the language in which you want to server installed and press MOREINFO="NONE"<Enter>.The "Select the Type of Installation Desired" menu appears.PERFORMANCE="REQUIRED"Choose "NetWare Server Installation" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Go to 
IDREF="FM62592""Name Your Server and Assign an IPX Network Number" on page 78.
PAGENUM=70 ID="BP77"RENDERAS="SECT1"ID="FM54169"Installing from a Remote Network Installation AreaIDXID="w3016"BOOK="_idx" COLLECTION="nw41" TIDREF="i1832"IDXID="w3017"BOOK="_idx" COLLECTION="nw41" TIDREF="i3750"A NetWare 4.1 server can be installed over the network from a mounted CD-ROM NetWare volume, or from CD-ROM or floppy diskette files copied to another server.In either scenario, a user logs in to a server with a remote network installation area and installs the workstation as a NetWare 4 server through the Installation utility.Requirements and recommendations for a IDXID="w3018"BOOK="_idx" COLLECTION="nw41" TIDREF="i3750"
remote installation are outlined below.RENDERAS="SECT2"Requirements for a NetWork Installation AreaMARK=BULLETThe server with the CD-ROM image should not be IDXID="w3019"BOOK="_idx" COLLECTION="nw41" TIDREF="i3863"
RIP-filtered from the server being installed.To find out if your network is utilizing RIP filtering, load FILTCFG.NLM at the server and view IPX protocol filters.The server being installed should use an IPX internal network number that is not RIP-filtered from the server with the CD-ROM image.RENDERAS="SECT2"Recommendations for a Network Installation AreaMARK=BULLETFor better performance, the server with the CD-ROM image should have Packet Burst€ support. NetWare 3.12 and NetWare 4€ servers have Packet Burst support. NetWare 3.11 requires PBURST.NLM for Packet Burst support.For better performance, the server with the CD-ROM image should have LIP (Large Internet Packet) support enabled. NetWare 3.12 and NetWare 4 servers have LIP support enabled by default (set command, NCP, "Allow LIP = On"). NetWare 3.11 requires LIPX.NLM for LIP support.PAGENUM=71 ID="BP78"RENDERAS="SECT2"Remote Installation AreasThe remote installation area can consist of one of the following:MARK=BULLETA NetWare 4.1 CD-ROM mounted as a NetWare volumeThe NetWare 4.1 CD-ROM files copied to a volume on a NetWare 4 serverCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Install from a NetWare 4.1 CD-ROM mounted as a NetWare volumeCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM39130""Installing from a CD-ROM Mounted as a NetWare Volume" on page 72.COLNAME=1 ROTATE="0" MOREROWS="0"Install from a NetWare server volume containing copied NetWare 4.1 CD-ROM filesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM28465""Installing from a NetWare Volume with Files Copied on a Server" on page 75.PAGENUM=72 ID="BP79"RENDERAS="SECT2"ID="FM39130"Installing from a CD-ROM Mounted as a NetWare VolumeRENDERAS="SECT3"IDXID="w3020"BOOK="_idx" COLLECTION="nw41" TIDREF="i2523"IDXID="w3021"BOOK="_idx" COLLECTION="nw41" TIDREF="i2822"
Necessary ResourcesMARK=CHECKBOXA CD-ROM drive that can read ISO 9660 formatted CD-ROM disks.An existing NetWare server. (This will be the host server.)An existing NetWare workstation. (This will be the new server you install.)RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Cable the CD-ROM drive to the NetWare 4.1 server (the host server). Since you are installing the CD-ROM as a NetWare volume, you do not need to install any drivers at this time.PERFORMANCE="REQUIRED"Insert the 
CLASS=DISKNetWare 4.1 Operating System CD-ROM into the CD-ROM drive.PERFORMANCE="REQUIRED"At the C:\NWSERVER directory, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"SERVER MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"At the server console type 
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>The menu shown on the next page appears.
PAGENUM=73 ID="BP80"LABEL="3-3" FLOAT="0"The "Installation Options" MenuFILEREF="n41in16a.tif"PERFORMANCE="REQUIRED"Choose "Driver Options."The "Driver Options" menu appears.PERFORMANCE="REQUIRED"Choose "Configure Disk and Storage Device Drivers."The "Additional Driver Actions" menu appears.PERFORMANCE="REQUIRED"Choose "Select an Additional Driver."You are prompted to enter the path to the source directory where the NetWare 4.1 files are located.PERFORMANCE="REQUIRED"Verify or change the source path and press MOREINFO="NONE"<Enter>.The "Select a Driver" list appears.PERFORMANCE="REQUIRED"Choose the necessary CD-ROM drivers according to the documentation that accompanied your CD-ROM drive.If the device drivers you need are not listed, press MOREINFO="NONE"<Ins> and follow the prompts to access a new list of drivers.  For information on the CD-ROM drivers that are shipped in the Red BoxTM (NetWare 4.1 product package), along with their proper load order, see IDREF="FM28651"Appendix F, "Red Box CD-ROM Drivers," on page 311.PERFORMANCE="REQUIRED"Once you have loaded all necessary drivers, from the "Additional Driver Actions" menu choose "Return to Previous Menu."PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Alt>+<F10> and choose "Yes" to exit INSTALL.NLM.
PAGENUM=74 ID="BP81"You are returned to the server console.PERFORMANCE="REQUIRED"At the console prompt, type the following commands:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD NWPA MOREINFO="NONE"<Enter> 
LOAD CDROM MOREINFO="NONE"<Enter> 
CD MOUNT NW410 MOREINFO="NONE"<Enter> This mounts the CD-ROM as a NetWare volume.PERFORMANCE="REQUIRED"Go to the workstation that is to become a server and log in to the host server with the mounted CD-ROM NetWare volume.PERFORMANCE="REQUIRED"Map a drive to the mounted CD-ROM volume.For example:
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAP N NW410:MOREINFO="NONE" <Enter>PERFORMANCE="REQUIRED"At the mapped drive letter, type 
FORMAT="LINESPECIFIC"MOREINFO="NONE"INSTALL MOREINFO="NONE"<Enter>A menu similar to the one below appears.LABEL="3-4" FLOAT="0"Choose the Desired Server LanguageFILEREF="n41in25a.tif"PERFORMANCE="REQUIRED"Choose the language in which you want the server installed and press MOREINFO="NONE"<Enter>.The "Select the Type of Installation Desired" menu appears.PERFORMANCE="REQUIRED"Choose "NetWare Server Installation" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Go to 
IDREF="FM62592""Name Your Server and Assign an IPX Network Number," on page 78.
PAGENUM=75 ID="BP82"RENDERAS="SECT2"ID="FM28465"Installing from a NetWare Volume with Files Copied on a ServerRENDERAS="SECT3"Necessary ResourcesMARK=CHECKBOXAn existing NetWare server with sufficient disk space (at least 170 MB) to store the NetWare 4.1 operating system files. (This will be the host server.)An existing NetWare workstation. (This will be the server you install.)(Conditional) A CD-ROM drive that can read ISO 9660 formatted CD-ROM disks.This is used to copy the NetWare 4.1 files from the CD-ROM to the host server.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Create a NETWARE directory on an existing server and 
copy the 
files from the installation medium to that directory.For example, to copy from CD-ROM drive D: to network drive K:, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"K:MOREINFO="NONE" <Enter> 
MD NETWARE MOREINFO="NONE"<Enter> 
CD NETWARE MOREINFO="NONE"<Enter> 
NCOPY D: /S /E /V MOREINFO="NONE"<Enter> To copy from floppy diskettes, perform the NCOPY command shown above for each diskette.PERFORMANCE="REQUIRED"On every computer you want to make a NetWare 4.1 server, create a DOS partition of at least 15 MB.PERFORMANCE="REQUIRED"On every computer you want to make a NetWare 4.1 server, install NetWare DOS client software.For instructions on installing workstation software, refer to 
IDREF="FM32801"Chapter 6, "Install NetWare Clients," on 
IDREF="FM32801"page 263.PERFORMANCE="REQUIRED"On every computer you want to make a NetWare 4.1 server, map a drive to the network host server directory that contains the NetWare 4.1 files.
PAGENUM=76 ID="BP83"PERFORMANCE="REQUIRED"At the mapped drive letter, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"INSTALL MOREINFO="NONE"<Enter>A menu similar to the one below appears.LABEL="3-5" FLOAT="0"Choose the Desired Server LanguageFILEREF="n41in25a.tif"PERFORMANCE="REQUIRED"Choose the language in which you want the server installed and press MOREINFO="NONE"<Enter>.The "Select the Type of Installation Desired" menu appears.PERFORMANCE="REQUIRED"Choose "NetWare Server Installation" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Go to 
IDREF="FM62592""Name Your Server and Assign an IPX Network Number," on page 78.
PAGENUM=77 ID="BP84"RENDERAS="SECT1"ID="FM43776"Installing from Floppy DiskettesRENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Make working copies of all NetWare 4.1 IDXID="w3022"BOOK="_idx" COLLECTION="nw41" TIDREF="i1135"
diskettes.For instructions, refer to 
IDREF="FM75630""Make Working Copies of the Diskettes (Conditional)" on page 12.PERFORMANCE="REQUIRED"Insert the 
CLASS=DISKInstall diskette into drive A:.PERFORMANCE="REQUIRED"Turn on or reboot your computer.The "Select the Type of Installation Desired" menu appears.PERFORMANCE="REQUIRED"Choose "NetWare Server Installation" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Continue with 
IDREF="FM62592""Name Your Server and Assign an IPX Network Number" on page 78.
PAGENUM=78 ID="BP85"RENDERAS="SECT1"ID="FM62592"Name Your Server and Assign an IPX Network NumberOnce you've selected the language in which the server will be installed, the following menu appears.LABEL="3-6" FLOAT="0"Installation OptionsFILEREF="n41in26a.tif"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Select "NetWare 4.1" and press MOREINFO="NONE"<Enter>.A menu appears displaying additional installation optionsPERFORMANCE="REQUIRED"Select "Custom Installation of NetWare 4.1" and press MOREINFO="NONE"<Enter>.A screen appears requesting a server name.PERFORMANCE="REQUIRED"Type the server name in the field provided and press MOREINFO="NONE"<Enter>.For help on rules for naming servers, press 
MOREINFO="NONE"<F1>.A new screen appears displaying a randomly generated 
IDXID="w3023"BOOK="_idx" COLLECTION="nw41" TIDREF="i304"IDXID="w3024"BOOK="_idx" COLLECTION="nw41" TIDREF="i1936"
IPX internal network number, an ID number that identifies and advertises this server on the network.PERFORMANCE="REQUIRED"Either accept the randomly generated IPX internal network number or enter a new one, and press MOREINFO="NONE"<Enter>.You can't assign an IPX internal network number of "0" or "FFFFFFFF."For more information on the IPX internal network number, see "

IPX internal network number" in
 the
BOOK="cncptenu" COLLECTION="nw41" Concepts manual, which is available online.For future reference, record your IPX internal network number on the NetWare 4.1 Server Worksheet on IDREF="FM68531"page 175.PERFORMANCE="REQUIRED"Continue with 
IDREF="FM99643""Copy Server Boot Files to the DOS Partition," on page 79.
PAGENUM=79 ID="BP86"RENDERAS="SECT1"ID="FM99643"Copy Server Boot IDXID="w3025"BOOK="_idx" COLLECTION="nw41" TIDREF="i843"IDXID="w3026"BOOK="_idx" COLLECTION="nw41" TIDREF="i843"
Files to the DOS PartitionIDXID="w3027"BOOK="_idx" COLLECTION="nw41" TIDREF="i492"A screen similar to the one below shows the default path and destination directory that the server boot files will be copied to.LABEL="3-7" FLOAT="0"The Source and Destination PathsFILEREF="n41in27a.tif"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Accept or change the default destination path and copy the files.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Copy the boot files to the default destination directory created for youCOLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<Enter>.COLNAME=1 ROTATE="0" MOREROWS="0"Copy the boot files to a destination directory of your own choiceCOLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<F4>, type a directory path and name, press <Enter>, choose "Yes," and press MOREINFO="NONE"<Enter> again.PERFORMANCE="REQUIRED"(Conditional) If you are installing from floppy diskettes, insert the NetWare diskettes into drive A: as prompted and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Continue with 
IDREF="FM67857""Specify Language and Filename Format Information," on page 80.
PAGENUM=80 ID="BP87"RENDERAS="SECT1"ID="FM67857"Specify Language and Filename Format InformationOnce all files are copied, the "Language Configuration" screen appears with the "Country Code" field highlighted.LABEL="3-8" FLOAT="0"IDXID="w3028"BOOK="_idx" COLLECTION="nw41" TIDREF="i2048"Language Configuration ScreenFILEREF="n41in64a.tif"For information on any of the settings in this screen, press <F1> or refer to your DOS manual.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"ID="FM92806"Specify the country code, code page, and keyboard mapping.Use the Up- and Down-arrow keys to maneuver through the screen.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"ID="FM60097"(Conditional) If the country code setting is 
not correct, press MOREINFO="NONE"<Enter> to view options and select an applicable country code.The "Code Page" field is highlighted.PERFORMANCE="REQUIRED"ID="FM87306"(Conditional) If the 
IDXID="w3029"BOOK="_idx" COLLECTION="nw41" TIDREF="i669"
code page setting is 
not correct, press MOREINFO="NONE"<Enter> and select an applicable code page.The "Keyboard Mapping" field is highlighted.PERFORMANCE="REQUIRED"(Conditional) If you do 
not have a standard U.S. English keyboard, press MOREINFO="NONE"<Enter> and select an applicable keyboard type.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to continue.The following screen appears.
PAGENUM=81 ID="BP88"LABEL="3-9" FLOAT="0"Select a Filename FormatFILEREF="n41in65a.tif"This screen allows you to indicate acceptable naming conventions for all files stored in the DOS name space on the server.Selecting "DOS Filename Format" limits you to using valid 
IDXID="w3030"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"
DOS filename characters according to the country code and code page selections in 
IDREF="FM60097"Step 1a and 
IDREF="FM87306"Step 1b, respectively.Limiting the server to valid DOS filename characters prevents workstations using NETX shells (rather than VLMs) from 

creating files using nonstandard DOS filename characters.Selecting "NetWare Filename Format" allows you to use NetWare-acceptable characters that may or may not be valid DOS filename characters.PERFORMANCE="REQUIRED"Select the filename format you need and press MOREINFO="NONE"<Enter>.You are asked if you want to specify startup SET commands.PERFORMANCE="REQUIRED"ID="FM20444"Select "Yes" or "No."Selecting "Yes" brings up an edit box for entering the startup commands.If you have disk, CD-ROM, or other devices that use ASPI, you should add the following line to your STARTUP.NCF file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"SET RESERVED BUFFERS BELOW 16MB = 200To see if your device uses ASPI, refer to the device documentation. PERFORMANCE="REQUIRED"(Conditional) If you specified any startup SET commands in 
IDREF="FM20444"Step 4, save them by pressing 
MOREINFO="NONE"<F10>.
PAGENUM=82 ID="BP89"PERFORMANCE="REQUIRED"(Optional) Add SERVER.EXE to your AUTOEXEC.BAT file.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="4*"COLNAME=2 COLWIDTH="20*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you chooseCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"YesCOLNAME=2 ROTATE="0" MOREROWS="0"SERVER.EXE runs automatically when you reboot the computer.COLNAME=1 ROTATE="0" MOREROWS="0"NoCOLNAME=2 ROTATE="0" MOREROWS="0"The DOS prompt appears whenever you reboot and you must type SERVER in the directory containing SERVER.EXE.The installation program now executes SERVER.EXE and 
IDXID="w3031"BOOK="_idx" COLLECTION="nw41" TIDREF="i2755"
INSTALL.NLM.PERFORMANCE="REQUIRED"Continue with 
IDREF="FM65610""Load the Disk Drivers and CD-ROM Drivers" on page 83.
PAGENUM=83 ID="BP90"RENDERAS="SECT1"ID="FM65610"Load the Disk Drivers and CD-ROM DriversThe following screen appears.LABEL="3-10" FLOAT="0"Select Your Disk DriverFILEREF="n41in13a.tif"If you are installing from CD-ROM and the CD-ROM drive is connected to a SCSI adapter shared by another internal or external device (hard disk, tape device, etc.), you may experience a keyboard lockup problem while loading drivers or copying files.  If this occurs, contact your SCSI adapter manufacturer for updated drivers.A 
disk driver enables communication between the disk controller and the server's CPU. Similarly, a CD-ROM driver enables communication between the CD-ROM and the server's CPU.In some cases, you will need to select a CD-ROM driver as well as a disk driver.RENDERAS="SECT2"Determine Your Driver ArchitectureIn earlier versions of NetWare 4, a single disk driver (a .DSK file) served as the single interface between the NetWare operating system and all devices on the interface adapter. This is known as monolithic architecture.NetWare 4.1 introduces NetWare Peripheral ArchitectureTM (NPA), which diverts the disk driver interface responsibilities to two new modules: a Host Adapter Module (HAM) and a Custom Device Module (CDM).PAGENUM=84 ID="BP91"You can install your NetWare 4.1 server using either the traditional monolithic architecture (which uses the .DSK drivers) or the NPA. For a quick overview of the advantages and disadvantages of using monolithic architecture and NPA, see the table below.LABEL="3-1" PGWIDE=1 TOCENTRY="1" Disk Driver Architecture OverviewCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="13*"COLNAME=3 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Architecture TypeCOLNAME=2 ROTATE="0" MOREROWS="0"AdvantagesCOLNAME=3 ROTATE="0" MOREROWS="0"DisadvantagesVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Monolithic (.DSK)COLNAME=2 ROTATE="0" MOREROWS="0"Has been around much longer.Individual drivers have been tested for compatibility by both Novell and third-party manufacturers.COLNAME=3 ROTATE="0" MOREROWS="0"Requires a compliant driver to run all hardware devices connected to the adapter.COLNAME=1 ROTATE="0" MOREROWS="0"NetWare Peripheral Architecture (NPA)COLNAME=2 ROTATE="0" MOREROWS="0"Each hardware device connected to the adapter uses an individual CDM, which makes it better designed for scalability.Will be the principle disk driver architecture in future releases of NetWare.COLNAME=3 ROTATE="0" MOREROWS="0"New architecture.Has not gone through extensive third- party testing.For a detailed discussion of each architecture type, read the following sections and determine the driver architecture you want before following the procedures on IDREF="FM98535"page 88.RENDERAS="SECT3"Monolithic ArchitectureAs stated earlier, IDXID="w3032"BOOK="_idx" COLLECTION="nw41" TIDREF="i2512"
monolithic architecture uses a single disk driver (a .DSK file) as the single interface between the NetWare operating system and all devices on the interface adapter.You may use this architecture, provided that the disk driver supports all connected hardware devices.PAGENUM=85 ID="BP92"Each NetWare 4.1 monolithic disk driver has an individual description that appears on the screen as you highlight the driver. Refer to these descriptions or to IDREF="FM80502"Table 3-2 to determine which driver to load.LABEL="3-2" PGWIDE=1 TOCENTRY="1"IDXID="w3033"BOOK="_idx" COLLECTION="nw41" TIDREF="i2991"IDXID="w3034"BOOK="_idx" COLLECTION="nw41" TIDREF="i1229"IDXID="w3035"BOOK="_idx" COLLECTION="nw41" TIDREF="i2991"ID="FM80502" Novell Monolithic Disk DriversCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="8*"COLNAME=3 COLWIDTH="8*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Computer architectureCOLNAME=2 ROTATE="0" MOREROWS="0"Controller COLNAME=3 ROTATE="0" MOREROWS="0"Disk driver you must loadVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Industry Standard Architecture (ISA)COLNAME=2 ROTATE="0" MOREROWS="0"ATCOLNAME=3 ROTATE="0" MOREROWS="0"ISADISKCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDE (ATA)COLNAME=3 ROTATE="0" MOREROWS="0"IDECOLNAME=1 ROTATE="0" MOREROWS="0"MicrochannelCOLNAME=2 ROTATE="0" MOREROWS="0"ESDICOLNAME=3 ROTATE="0" MOREROWS="0"PS2ESDICOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IBM SCSICOLNAME=3 ROTATE="0" MOREROWS="0"PS2SCSICOLNAME=1 ROTATE="0" MOREROWS="0"Extended Industry Standard Architecture (EISA)COLNAME=2 ROTATE="0" MOREROWS="0"AT classCOLNAME=3 ROTATE="0" MOREROWS="0"ISADISKCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"IDE (ATA)COLNAME=3 ROTATE="0" MOREROWS="0"IDECOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"EISA vendor proprietaryCOLNAME=3 ROTATE="0" MOREROWS="0"See vendorFor example, if you have an ISA computer, you need to load the IDE disk driver.Besides Novell® drivers, additional third-party drivers are also included with NetWare 4.1.If you experience problems with third-party drivers, contact the manufacturer listed in the driver description that appears as you highlight the driver. PAGENUM=86 ID="BP93"RENDERAS="SECT3"NetWare Peripheral Architecture (NPA)IDXID="w3036"BOOK="_idx" COLLECTION="nw41" TIDREF="i2777"
NPA allows for broader driver support for host bus adapters and connected hardware devices.NPA separates NetWare driver support into two components: a IDXID="w3037"BOOK="_idx" COLLECTION="nw41" TIDREF="i1692"
Host Adapter Module (HAM) and a IDXID="w3038"BOOK="_idx" COLLECTION="nw41" TIDREF="i900"
Custom Device Module (CDM). The HAM is the component used to drive the host bus adapter hardware. The CDM is the component used to drive hardware devices attached to a host adapter bus.The main advantage of using NPA over monolithic architecture is that NPA is better designed for scalability.When you want to connect a new hardware device to the host bus adapter, you need to load only the appropriate CDM for that hardware device (in addition to the HAMs and CDMs already loaded), not a compatible disk driver to run all hardware devices connected to the adapter.HAMs and CDMs are loaded the same way you load other disk drivers. The difference is that you load a HAM for the adapter in your server, and a CDM for each device type attached to the adapter. When the first HAM is loaded, the NWPA.NLM is loaded automatically. NWPA.NLM is an interface between the NPA and the Media Manager. The Media Manager provides a storage management interface between applications and storage device drivers.Once the HAM and NWPA.NLM are loaded, the server is scanned for new devices. Based on what new devices are found, the appropriate Novell CDMs are then loaded. Standard Novell CDMs are listed in IDREF="FM44951"Table 3-3 on page 87.If you are using a third-party CDM, rather than one of the Novell standard CDMs, it must be loaded manually.A description of NetWare 4.1 HAMs and CDMs appears on the screen as you highlight the driver. PAGENUM=87 ID="BP94"LABEL="3-3" PGWIDE=1 TOCENTRY="1"IDXID="w3039"BOOK="_idx" COLLECTION="nw41" TIDREF="i2991"ID="FM44951" Novell NPA Disk Drivers, HAMs, and CDMsCOLS=4 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="6*"COLNAME=3 COLWIDTH="7*"COLNAME=4 COLWIDTH="14*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Computer architectureCOLNAME=2 ROTATE="0" MOREROWS="0"Controller COLNAME=3 ROTATE="0" MOREROWS="0"HAM you must loadCOLNAME=4 ROTATE="0" MOREROWS="0"Novell CDM that is loadedVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Industry Standard Architecture (ISA)COLNAME=2 ROTATE="0" MOREROWS="0"AT classIDE (ATA)COLNAME=3 ROTATE="0" MOREROWS="0"IDEATA.HAMCOLNAME=4 ROTATE="0" MOREROWS="0"IDEHD.CDM (For a hard disk)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"Adaptec 154XCOLNAME=3 ROTATE="0" MOREROWS="0"SCSI154X.HAMCOLNAME=4 ROTATE="0" MOREROWS="0"SCSIHD.CDM (For a hard disk)SCSICD.CDM (For a CD-ROM drive)SCSIMO.CDM (For a magneto-optical drive)SCSI2TP.CDM (For a tape device)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=4 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"MicrochannelCOLNAME=2 ROTATE="0" MOREROWS="0"IBM SCSICOLNAME=3 ROTATE="0" MOREROWS="0"SCSIPS2.HAMCOLNAME=4 ROTATE="0" MOREROWS="0"SCSIHD.CDM (For a hard disk)SCSICD.CDM (For a CD-ROM drive)SCSIMO.CDM (For a magneto-optical drive)SCSI2TP.CDM (For a tape device)COLNAME=1 ROTATE="0" MOREROWS="0"Extended Industry Standard Architecture (EISA)COLNAME=2 ROTATE="0" MOREROWS="0"AT classIDE (ATA)COLNAME=3 ROTATE="0" MOREROWS="0"IDEATA.HAMCOLNAME=4 ROTATE="0" MOREROWS="0"IDEHD.CDM  (For a hard disk)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=4 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"Adaptec 154XCOLNAME=3 ROTATE="0" MOREROWS="0"SCSI154X.HAMCOLNAME=4 ROTATE="0" MOREROWS="0"SCSIHD.CDM (For a hard disk)SCSICD.CDM (For a CD-ROM drive)SCSIMO.CDM (For a magneto-optical drive)SCSI2TP.CDM (For a tape device)COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"EISA vendor proprietaryCOLNAME=3 ROTATE="0" MOREROWS="0"See vendorCOLNAME=4 ROTATE="0" MOREROWS="0"See vendorFor more information about the NPA, refer to "BOOK="cncptenu" COLLECTION="nw41"NetWare Peripheral Architecture" in Concepts.PAGENUM=88 ID="BP95"RENDERAS="SECT4"ProcedureIf more than one hard disk of the same type is installed in your computer, and if the disks are both connected to the same disk controller, load only one disk driver. If the disks are connected to different controllers, load the driver multiple times or load additional disk drivers.PERFORMANCE="REQUIRED"ID="FM98535"Choose your disk driver.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If COLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"The driver is listedCOLNAME=2 ROTATE="0" MOREROWS="0"Choose the appropriate disk driver and continue with Step 2.COLNAME=1 ROTATE="0" MOREROWS="0"The driver is not listedCOLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<Ins> and follow the prompts. Then skip to IDREF="FM72276"Step 3.The selected disk driver is then copied to the server boot directory before it is loaded.PERFORMANCE="REQUIRED"View the displayed parameter settings and verify that they are correct.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Accept the default valuesCOLNAME=2 ROTATE="0" MOREROWS="0"Select "Save Parameters and Continue." COLNAME=1 ROTATE="0" MOREROWS="0"Change the defaults because they do not match the installed hardwareCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "Select/Modify Driver Parameters and Continue." A prompt appears asking if you want to load any additional disk driversCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want to COLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Load additional disk drivers, or load separate CD-ROM driversCOLNAME=2 ROTATE="0" MOREROWS="0"Select "Yes" and press <Enter>. Then repeat Steps 1 and 2.Once all appropriate disk drivers have been selected, continue with IDREF="FM72276"Step 3.COLNAME=1 ROTATE="0" MOREROWS="0"Proceed without loading additional disk driversCOLNAME=2 ROTATE="0" MOREROWS="0"Continue with IDREF="FM72276"Step 3.PAGENUM=89 ID="BP96"PERFORMANCE="REQUIRED"ID="FM72276"Continue with 
IDREF="FM28857""Load the LAN Drivers and Protocols," on page 90.
PAGENUM=90 ID="BP97"RENDERAS="SECT1"ID="FM28857"Load the LAN Drivers and ProtocolsAfter you load your disk drivers, the following screen appears, ready for you to choose your LAN drivers.LABEL="3-11" FLOAT="0"Select Your LAN DriversFILEREF="n41in14a.tif"Your choice of 
LAN drivers depends on the cabling system and the 
network 
board you are using. Loading a LAN driver establishes a network connection (if the server is physically connected to the network cabling.)Most NetWare 4.1 LAN drivers have an individual description that appears on the screen after you choose the driver. Refer to IDREF="FM24424"Table 3-4 on page 91 and to the on-screen descriptions to determine which LAN driver to load.If you experience problems with third-party drivers, contact the manufacturer listed in the driver description that appears as you highlight the driver. LABEL="3-4" PGWIDE=1 TOCENTRY="1"IDXID="w3040"BOOK="_idx" COLLECTION="nw41" TIDREF="i2991"IDXID="w3041"BOOK="_idx" COLLECTION="nw41" TIDREF="i1229"ID="FM24424" Novell LAN DriversCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="13*"COLNAME=3 COLWIDTH="10*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Cabling systemCOLNAME=2 ROTATE="0" MOREROWS="0"Network boardCOLNAME=3 ROTATE="0" MOREROWS="0"LAN driver you must loadVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"ARCnetCOLNAME=2 ROTATE="0" MOREROWS="0"RX-NetCOLNAME=3 ROTATE="0" MOREROWS="0"TRXNET.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"RX-Net IICOLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"RX-Net/2COLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"EthernetCOLNAME=2 ROTATE="0" MOREROWS="0"NE/2  NE/2T COLNAME=3 ROTATE="0" MOREROWS="0"NE2.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE/2-32COLNAME=3 ROTATE="0" MOREROWS="0"NE2_32.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE1000 - ASSY 950-054401  NE1000 - ASSY 810-160-001COLNAME=3 ROTATE="0" MOREROWS="0"NE1000.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE2000 - ASSY 810-149  NE2000T - ASSY 810-000220COLNAME=3 ROTATE="0" MOREROWS="0"NE2000.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE2100 - ASSY 810-000209COLNAME=3 ROTATE="0" MOREROWS="0"NE2100.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE1500T - ASSY 810-000214  (twisted-pair version of NE2100)COLNAME=3 ROTATE="0" MOREROWS="0"NE1500T.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE3200COLNAME=3 ROTATE="0" MOREROWS="0"NE3200.LANCOLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NE32HUBCOLNAME=3 ROTATE="0" MOREROWS="0"NE32HUB.LANCOLNAME=1 ROTATE="0" MOREROWS="0"Token RingCOLNAME=2 ROTATE="0" MOREROWS="0"NTR2000COLNAME=3 ROTATE="0" MOREROWS="0"NTR2000.LANPAGENUM=91 ID="BP98"For example, if you have a Novell NE2100TM network board installed in your computer, you must load the NE2100.LAN driver.PAGENUM=92 ID="BP99"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"ID="FM56936"Choose your LAN driver.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="14*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If COLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"The driver is listed.COLNAME=2 ROTATE="0" MOREROWS="0"Choose the appropriate LAN driver and continue with IDREF="FM96317"Step 2.COLNAME=1 ROTATE="0" MOREROWS="0"The driver is not listed.COLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<Ins> and follow the prompts.Then continue with IDREF="FM96317"Step 2.The selected LAN driver is then copied and stored temporarily in the C: drive before it is loaded. The following screen appears.LABEL="3-12" FLOAT="0"Available Protocols and LAN Driver Parameters Are DisplayedFILEREF="n41i105a.tif"PERFORMANCE="REQUIRED"(Conditional) 
ID="FM96317"If you want your server to load additional network 
IDXID="w3042"BOOK="_idx" COLLECTION="nw41" TIDREF="i3609"IDXID="w3043"BOOK="_idx" COLLECTION="nw41" TIDREF="i255"IDXID="w3044"BOOK="_idx" COLLECTION="nw41" TIDREF="i4456"
protocols, in addition to IPX, choose "Select/Modify Driver Parameters and Protocols" from the "Parameter Actions" menu.Protocols selected here will be nonrouting. If you want to configure routing protocols, you will need to do so through the "Configure Network Protocols" option, which is available after the server is installed. See IDREF="FM61994" "Configure Network Protocols," on page 169.The cursor is placed in the protocol form displayed at the top of the screen.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"ID="FM89055"Press MOREINFO="NONE"<Enter> to select or deselect protocols.
PAGENUM=93 ID="BP100"PERFORMANCE="REQUIRED"If you selected TCP/IP in 
IDREF="FM89055"Step 2a, enter the IP address and IP mask numbers and press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"ID="FM10800"(Optional) If you want to choose specific IPX frame types for the server, press 
MOREINFO="NONE"<F3>.A list of frame types appear.NetWare 4.1, by default, loads all applicable frame types, but will bind to only the frame types found on the network. Once the server is rebooted, only bound frame types are loaded.  By making selections in this list, you indicate specifically the frame types you want bound to IPX.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select the desired frame types by pressing MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to save the frame type settings.PERFORMANCE="REQUIRED"ID="FM24722"View the displayed LAN driver parameters and verify that they are correct.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Accept the default valuesCOLNAME=2 ROTATE="0" MOREROWS="0"From the "LAN Board Actions" menu, choose "Save Parameters and Continue."COLNAME=1 ROTATE="0" MOREROWS="0"Change the defaults because they are either incomplete, or they conflict with other hardware settingsCOLNAME=2 ROTATE="0" MOREROWS="0"From the "LAN Board Actions" menu, choose "Select/Modify Driver Parameters and Protocols."Use the Down-arrow key to advance to the "Board Parameters" screen.Enter the correct parameter settings in the appropriate fields.Choose "Save Parameters and Continue."PAGENUM=94 ID="BP101"A prompt appears, asking if you want to load any additional network drivers.PERFORMANCE="REQUIRED"Choose whether to load additional LAN drivers.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Load additional network driversCOLNAME=2 ROTATE="0" MOREROWS="0"Select "Yes" and press MOREINFO="NONE"<Enter>. Then repeat IDREF="FM56936"Steps 1 through IDREF="FM24722"4.Once all appropriate network drivers have been selected, continue with IDREF="FM35211"Step 6.COLNAME=1 ROTATE="0" MOREROWS="0"Proceed without loading additional network driversCOLNAME=2 ROTATE="0" MOREROWS="0"Continue with IDREF="FM35211"Step 6.The "Choose the Server Drivers---Summary" screen appears with the selected disk and LAN drivers displayed.LABEL="3-13" FLOAT="0"Selected Drivers Are Displayed Prior to Being LoadedFILEREF="n41in36a.tif"PERFORMANCE="REQUIRED"ID="FM35211"Choose "Continue installation" from the "Driver Actions" menu.If you are installing from CD-ROM, the following screen may appear.LABEL="3-14" FLOAT="0"ID="FM58958"You Can Try to Mount the CD-ROM as a NetWare VolumeFILEREF="n41in41a.tif"PAGENUM=95 ID="BP102"PERFORMANCE="REQUIRED"(Conditional) If you are installing from CD-ROM and the menu in 
IDREF="FM58958"Figure 3-14 appears, choose one of the menu options.If a disk or CD-ROM driver you selected earlier conflicts with the DOS CD-ROM driver, your keyboard may lock up during installation.To avoid this, you can attempt to mount the CD-ROM as a NetWare volume. In doing so, you may be prompted to install new disk or CD-ROM drivers.For each frame type found on the network, a screen appears informing you that the frame type will be bound to IPX.LABEL="3-15" FLOAT="0"A Screen Appears for Each Frame Type Found on the NetworkFILEREF="n41i100a.tif"You should record the displayed IPX external network address, server IPX internal network number, and network board node address in the NetWare 4.1 Server Worksheet on IDREF="FM68531"page 175.PERFORMANCE="REQUIRED"(Conditional) If you selected frame types using the 
MOREINFO="NONE"<F3> key in 
IDREF="FM10800"Step 3, you may be prompted to enter the IPX external network number for each frame type.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> to bind IPX with the listed information.If you do not want to bind IPX with the listed information, press 
MOREINFO="NONE"<F3>.PERFORMANCE="REQUIRED"Continue with 
IDREF="FM94272""Create NetWare Disk Partitions" on page 96.
PAGENUM=96 ID="BP103"RENDERAS="SECT1"ID="FM94272"ID="FM91881"Create IDXID="w3045"BOOK="_idx" COLLECTION="nw41" TIDREF="i873"IDXID="w3046"BOOK="_idx" COLLECTION="nw41" TIDREF="i2732"
NetWare Disk PartitionsThe following screen appears, ready for you to create NetWare disk partitions.LABEL="3-16" FLOAT="0"Create NetWare Disk PartitionsFILEREF="n41in37a.tif"Every NetWare 4.1 server needs a disk partition for NetWare files and shared data. You can have only one NetWare 4.1 disk partition per disk, but you can have up to eight volume segments on the NetWare disk partition.If your server's boot hard disk has a DOS partition, use the rest of the disk space as a NetWare disk partition.LABEL="3-17" FLOAT="0"Disk Partitions and Volumes on an Internal Hard DiskFILEREF="n40in11a.tif"PAGENUM=97 ID="BP104"The Custom Installation option offers two ways of creating NetWare disk partitions, automatically and manually.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="19*"COLNAME=2 COLWIDTH="6*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IfCOLNAME=2 ROTATE="0" MOREROWS="0"ChooseVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"You want NetWare to create NetWare disk partitions in the available disk space without the option of mirroring or duplexing the disksCOLNAME=2 ROTATE="0" MOREROWS="0"Automatically  (see IDREF="FM85614""Create NetWare Disk Partitions Automatically" on page 98COLNAME=1 ROTATE="0" MOREROWS="0"MARK=BULLETYou want to specify the size of the NetWare partitionYou need room for other operating systems on the diskYou want to mirror or duplex disk partitions (this is possible only if you have more than one disk and have more than one disk controller)You want to change the size of the Hot Fix Redirection AreaYou want to selectively delete current disk partitionsCOLNAME=2 ROTATE="0" MOREROWS="0"Manually  (see IDREF="FM20470""Create NetWare Disk Partitions Manually" on page 99PAGENUM=98 ID="BP105"RENDERAS="SECT2"ID="FM85614"Create NetWare Disk Partitions AutomaticallyThis option automatically creates a NetWare disk partition in the available disk space on each disk.MARK=BULLETOn the boot disk, a NetWare partition is created on the disk space not occupied by the DOS partition. If you indicate you want to delete existing partitions, any existing NetWare partitions (but not DOS partitions) will be destroyed.On other disks, all disk space is allocated to the NetWare partition.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Create NetWare Disk Partitions" menu, choose "Automatically."PERFORMANCE="REQUIRED"Go to 
IDREF="FM58546""Manage NetWare Volumes" on page 105.
PAGENUM=99 ID="BP106"RENDERAS="SECT2"ID="FM20470"Create NetWare Disk Partitions ManuallyRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"ID="FM16162"From the "Create NetWare Disk Partitions" menu, choose "Manually" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"From the "Disk Partition and Mirroring Options" menu, choose "Create, Delete, and Modify Disk Partitions" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"ID="FM23464"(Conditional) If you have more than one disk, from the "Available Disk Drives" menu, choose the disk you need to partition and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Choose "Create NetWare Disk Partition" and press 
MOREINFO="NONE"<Enter>.NetWare allows only one NetWare partition per disk. PERFORMANCE="REQUIRED"In the "Disk Partition Information" screen, 

specify the size of the NetWare partition (in megabytes) and press MOREINFO="NONE"<Enter>.LABEL="3-18" FLOAT="0"The "Disk Partition Information" ScreenFILEREF="n41in94a.tif"The Hot Fix information is adjusted automatically. NetWare adjusts the percentage for Hot Fix according to the disk capacity.For more information on 
IDXID="w3047"BOOK="_idx" COLLECTION="nw41" TIDREF="i1698"
Hot Fix, see "
BOOK="cncptenu" COLLECTION="nw41"Data protection" or "
BOOK="cncptenu" COLLECTION="nw41"Hot Fix" in 
Concepts.
PAGENUM=100 ID="BP107"Many disk drive manufacturers advertise drive sizes in millions of bytes (for megabytes) or billions of bytes (for gigabytes). However, NetWare reports the drive size in true megabytes (1,048,576 bytes).If the drive size for a NetWare partition appears smaller than expected, this is most likely the reason.In addition, NetWare disk space does not show the disk space allocated for Hot Fix (the Hot Fix Redirection Area).PERFORMANCE="REQUIRED"(Conditional) If necessary, change the 
IDXID="w3048"BOOK="_idx" COLLECTION="nw41" TIDREF="i2496"
size of either the data 
IDXID="w3049"BOOK="_idx" COLLECTION="nw41" TIDREF="i3716"
area (in megabytes) or the Hot Fix Redirection Area (in percentage of disk partition size) and press MOREINFO="NONE"<Enter>.If you change one of the fields, the installation utility calculates the space remaining for the other field.PERFORMANCE="REQUIRED"To save and continue, press 
MOREINFO="NONE"<Esc>.PERFORMANCE="REQUIRED"ID="FM37189"When prompted to "Create NetWare Partition?" choose "Yes" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"(Optional) If you want to create NetWare partitions on multiple drives, press 
MOREINFO="NONE"<Esc> and then repeat 
IDREF="FM23464"Steps 3 through 
IDREF="FM37189"8.PERFORMANCE="REQUIRED"If you want to mirror or duplex disks, continue with 
IDREF="FM82887""Mirror or Duplex NetWare Disk Partitions (Optional)," on page 101. If you don't want to mirror disk partitions, press 
MOREINFO="NONE"<Esc>, select "Continue with Installation," and go to 
IDREF="FM58546""Manage NetWare Volumes" on page 105.
PAGENUM=101 ID="BP108"RENDERAS="SECT2"ID="FM82887"Mirror or Duplex NetWare Disk Partitions (Optional)IDXID="w3050"BOOK="_idx" COLLECTION="nw41" TIDREF="i2732"NetWare 4.1 protects IDXID="w3051"BOOK="_idx" COLLECTION="nw41" TIDREF="i1428"
data from IDXID="w3052"BOOK="_idx" COLLECTION="nw41" TIDREF="i1636"IDXID="w3053"BOOK="_idx" COLLECTION="nw41" TIDREF="i914"IDXID="w3054"BOOK="_idx" COLLECTION="nw41" TIDREF="i3585"
hard disk failure by letting you duplicate (mirror) one hard disk's data on one or more other hard disks.Then, if one of the disks fails and cannot be accessed by the server, you can continue to work from the functional disk.You can safeguard your data in either of two ways.MARK=BULLETIDXID="w3055"BOOK="_idx" COLLECTION="nw41" TIDREF="i2732"Mirroring. The operating system stores duplicate data on two disks using the same controller.Duplexing. The operating system stores duplicate data on two disks using different controllers.Duplexing offers better protection because losing two disk controllers simultaneously is even less likely than losing two hard disks.Mirroring and duplexing options are available only on systems having more than one hard disk.Mirroring and duplexing are illustrated in the following figure.LABEL="3-19" FLOAT="0"Mirroring and DuplexingFILEREF="n41in62a.tif"PAGENUM=102 ID="BP109"RENDERAS="SECT3"Consider the following as you mirror or duplex your hard disks:MARK=BULLETThe installation processes for mirroring and duplexing are the same.Partition sizes of the mirrored or duplexed hard disks should be similar. Otherwise, any remaining space on the larger partition is wasted, since NetWare makes adjustments so that the mirrored partitions are exactly the same size.Two mirrored partitions are usually sufficient, but you can mirror as many as eight partitions.Which hard disks you mirror depends on how you decide to set up volumes on the server. See IDREF="FM58792""Suggestions for Creating Volumes" on page 106Before mirroring or duplexing a hard disk, back up your data.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the "Disk Partition and Mirroring Options" menu, choose "Mirror and Unmirror Disk Partition Sets" and press MOREINFO="NONE"<Enter>.The "Disk Partition Mirroring Status" screen appears.LABEL="3-20" FLOAT="0"The "Disk Partition Mirroring Status" ScreenFILEREF="n41i106a.tif"PAGENUM=103 ID="BP110"The "Disk Partition Mirroring Status" screen displays one of the following conditions for each disk partition.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"StatusCOLNAME=2 ROTATE="0" MOREROWS="0"ExplanationVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Not MirroredCOLNAME=2 ROTATE="0" MOREROWS="0"The disk partition is not currently mirrored to another partition.COLNAME=1 ROTATE="0" MOREROWS="0"MirroredCOLNAME=2 ROTATE="0" MOREROWS="0"The disk partition is currently mirrored to another disk partition.COLNAME=1 ROTATE="0" MOREROWS="0"Out Of SyncCOLNAME=2 ROTATE="0" MOREROWS="0"The disk partition was previously mirrored to another disk partition, but mirroring isn't currently active. The disk partition can't be accessed until mirroring is restored. Press MOREINFO="NONE"<F3> to restore mirroring.COLNAME=1 ROTATE="0" MOREROWS="0"RemirroringCOLNAME=2 ROTATE="0" MOREROWS="0"The partitions are being remirrored.All disk partitions will initially appear as "Not Mirrored."PERFORMANCE="REQUIRED"Choose one of the disk devices (disk partitions) you want to mirror or duplex and press MOREINFO="NONE"<Enter>.The partition you choose becomes the primary partition of the mirrored set. (See "
BOOK="cncptenu" COLLECTION="nw41"Device numbering" in 
Concepts for an explanation of how logical partitions relate to the installed hard disks.)A list of disk partitions on the selected disk device appears.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Ins> to access the "Available Disk Partitions" list.PERFORMANCE="REQUIRED"Select the disk partition you want to mirror to the device (disk partition) you chose in Step 3, and press MOREINFO="NONE"<Enter>.If this disk partition is smaller or larger than the disk partition it will be mirrored to, the following message appears:
FORMAT="LINESPECIFIC"MOREINFO="NONE"The selected NetWare disk partition is larger/smaller than the original NetWare partition. These partitions must be the same size in order to be mirrored. Press <Enter> to continue.PAGENUM=104 ID="BP111"PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"(Conditional) Press MOREINFO="NONE"<Enter> to continue.The "Change the Selected NetWare Disk Partition's Size?" prompt then appears.PERFORMANCE="REQUIRED"(Conditional) Choose "Yes" to make the partitions the same size and press MOREINFO="NONE"<Enter>.NetWare automatically adjusts the size of the larger disk partition to match that of the smaller partition.The "Mirrored NetWare Disk Partitions" menu appears. PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to return to the "Disk Partition Mirroring Status" screen.The "Disk Partition Mirroring Status" screen displays those disk partitions that are mirrored to each other.For example, if you mirrored disk (device) 0 to disk (device) 1, the "Disk Partition Mirroring Status" screen would appear similar to the one below.LABEL="3-21" FLOAT="0"The "Disk Partition Mirroring Status" ScreenFILEREF="n41in93a.tif"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to return to the "Disk Partition and Mirroring Options" menu. PERFORMANCE="REQUIRED"Select "Continue with Installation" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Continue with 
IDREF="FM58546""Manage NetWare Volumes" on page 105.
PAGENUM=105 ID="BP112"RENDERAS="SECT1"ID="FM58546"Manage NetWare VolumesIDXID="w3056"BOOK="_idx" COLLECTION="nw41" TIDREF="i2327"The "IDXID="w3057"BOOK="_idx" COLLECTION="nw41" TIDREF="i4795"
Manage NetWare Volumes" screen lists the volumes the installation utility creates for you unless you change the defaults. The number of volumes listed depends on the hard disks.LABEL="3-22" FLOAT="0""Manage NetWare Volumes" ScreenFILEREF="n41in08a.tif"For servers with single hard disks, the installation utility assigns all disk space (except for a DOS partition) to a single volume SYS:. In the "Volume Disk Segment List" (see IDREF="FM69297"Figure 3-23 on page 108), volume SYS: is displayed as "Device 0."For servers utilizing several hard disks, the installation utility creates one volume for each hard disk. In the "Volume Disk Segment List," additional volumes appear as "Device 1," "Device 2," etc.RENDERAS="SECT2"Modify Volume ParametersYou can rename any of the volumes, except for volume SYS:. Having a volume SYS: is mandatory since it stores system information needed by NetWare.You can also change the number and sizes of the volumes by deleting one or more of them and reallocating the resulting free space.We recommend allocating at least 75 MB of disk space to volume SYS:. However, you may need to allocate additional space in the following situations:MARK=BULLETYou plan to install several "optional" files (NetWare OS/2 utilities, for example). If not enough volume space is available when file copying begins (see IDREF="FM90248""Copy NetWare Files," on page 123), you are prompted to resize the volume before continuing with the file copy.PAGENUM=106 ID="BP113"You plan to print large files. NetWare needs additional storage space to spool these files.You plan to install a single language set of NetWare 4.1 online documentation and a single DynaText* viewer. (This requires approximately 60 MB of free space on volume SYS:.)RENDERAS="SECT2"NDS and Volume SYS:After you've installed NetWare Directory Services (see IDREF="FM32481""Installing NetWare Directory Services" on page 127), each server's volume SYS: appears as servername_SYS in the IDXID="w3058"BOOK="_idx" COLLECTION="nw41" TIDREF="i4795"
Directory tree. This logical name is the IDXID="w3059"BOOK="_idx" COLLECTION="nw41" TIDREF="i4795"
name of the IDXID="w3060"BOOK="_idx" COLLECTION="nw41" TIDREF="i4787"
Volume object in the Directory tree.For example, if you named the server TECHSERVER, its volume SYS: would appear as Volume object TECHSERVER_SYS in the Directory tree. The name of the physical volume, as seen from the server, still remains SYS:.RENDERAS="SECT2"ID="FM58792"IDXID="w3061"BOOK="_idx" COLLECTION="nw41" TIDREF="i4795"Suggestions for Creating VolumesMARK=BULLETReserve volume SYS: for the NetWare files and create one or more additional volumes for applications and data. If fault tolerance is more important than performance, create one volume per disk.If performance is more important than fault tolerance, span one NetWare volume over many hard disks with one segment of the volume on each hard disk. If any disk on a spanned volume fails, the whole volume is lost. Make sure you back up spanned volumes regularly so you can restore the entire volume (all its segments) from backup once the disk(s) is repaired or replaced. PAGENUM=107 ID="BP114"If both performance and fault tolerance are important, you can both span and duplex, but we recommend that you duplex every hard disk partition of the spanned volume. See IDREF="FM82887""Mirror or Duplex NetWare Disk Partitions (Optional)" on page 101.For maximum fault tolerant protection, we recommend purchasing NetWare SFT III.If your network includes workstations using an operating system that allows IDXID="w3062"BOOK="_idx" COLLECTION="nw41" TIDREF="i4795"
long filenames (such as Macintosh*), it is a good idea to create a separate IDXID="w3063"BOOK="_idx" COLLECTION="nw41" TIDREF="i93"
volume for each operating system.Long 
filenames (filenames longer than those allowed by DOS) take up disk space that is not required for DOS files. Also, you can isolate network problems more easily. For example, if your network includes both DOS and Macintosh file types, you may want to create two volumes for data, DOSVOL: and MACVOL:. This way, you add name space only to those volumes whose files need it.If you are using the NetWare auditing feature and one volume will contain data to be reviewed by two or more auditors, you can (for security reasons) create a separate volume for each auditor.For example, assume you plan to audit a volume that contains accounting and sales data, but plan to have two auditors do the work.In this situation, if you are concerned about these auditors accessing each other's audit reports, you should create two separate volumes, one for accounting data and one for sales data.Auditing rights for the file system are assigned per volume (after server installation) using the AUDITCON utility. For more information, refer to Chapter 8, "BOOK="superenu" COLLECTION="nw41"Auditing Network Events," in Supervising the Network.PAGENUM=108 ID="BP115"RENDERAS="SECT2"ID="FM51733"Modify the Size of a Volume IDXID="w3064"BOOK="_idx" COLLECTION="nw41" TIDREF="i4795"
Segment (Optional)If you do not want to modify the size of a volume segment, you can go to any of the optional procedures in this section, or you can continue the installation by going to IDREF="FM84768""Save and Mount Volumes and License Software," on page 120.You can modify the size of an existing volume (a volume that's been saved to disk) only by deleting and re-creating it.To modify a volume segment size (for example, to decrease the size of volume SYS: in order to create another volume), follow these steps.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"In the "Manage NetWare Volumes" screen, press MOREINFO="NONE"<Ins> or <MOREINFO="NONE"F3>.The "Volume Disk Segment List" screen appears.LABEL="3-23" FLOAT="0"ID="FM69297"The "Volume Disk Segment List" ScreenFILEREF="n41in96a.tif"PERFORMANCE="REQUIRED"Choose the device number whose volume size you want to modify and press MOREINFO="NONE"<Enter>.The "Disk segment parameters" list appears.PERFORMANCE="REQUIRED"In the "Disk Segment Size" field, type the new volume size in megabytes (or fraction thereof) and press MOREINFO="NONE"<Enter>. 
PAGENUM=109 ID="BP116"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to return to the "Volume Disk Segment List" screen.If you decrease the size of the volume, the remaining space appears as "free space." You can assign it to another volume by highlighting the "free space" listing and pressing MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Modify other volume parameters on 
IDREF="FM14849"pages 110 through 
IDREF="FM15242"118, or press 
MOREINFO="NONE"<Esc> and continue with 
IDREF="FM84768""Save and Mount Volumes and License Software" on page 120.
PAGENUM=110 ID="BP117"RENDERAS="SECT2"ID="FM14849"Modify IDXID="w3065"BOOK="_idx" COLLECTION="nw41" TIDREF="i4795"
Volume Name (Optional)If you do not want to modify the volume name, you can go to any of the optional procedures in this section, or you can continue the installation by going to IDREF="FM84768""Save and Mount Volumes and License Software," on page 120.Volume SYS: can't be renamed.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"In the "Manage NetWare Volumes" screen, choose the volume whose name you want to change and press MOREINFO="NONE"<Enter>.The "Volume Information" screen appears.LABEL="3-24" FLOAT="0"The "Volume Information" ScreenFILEREF="n41i101a.tif"PERFORMANCE="REQUIRED"Select the "Name" field in the "Volume Information" screen and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Type in a new volume name and press MOREINFO="NONE"<Enter>.Press 
MOREINFO="NONE"<F1> for naming rules.PERFORMANCE="REQUIRED"Either modify other volume parameters or press 
MOREINFO="NONE"<Esc> to return to the list of volumes.
PAGENUM=111 ID="BP118"Unlike some parameter settings, which can be modified later, the following parameter settings can be modified 
only before volumes are saved and mounted:
MARK=BULLETEnable/Disable File Compression (see IDREF="FM49972"page 112)Enable/Disable Block Suballocation (see IDREF="FM69043"page 116)PERFORMANCE="REQUIRED"Modify other volume parameters on 
IDREF="FM85813"pages 112 through 
IDREF="FM15242"118, or press 
MOREINFO="NONE"<Esc> and continue with 
IDREF="FM84768""Save and Mount Volumes and License Software," on page 120.
PAGENUM=112 ID="BP119"RENDERAS="SECT2"ID="FM85813"ID="FM13507"Modify Volume IDXID="w3066"BOOK="_idx" COLLECTION="nw41" TIDREF="i474"
Block Size (Optional)If you do not want to modify the volume block size, you can go to any of the optional procedures in this section, or you can continue the installation by going to IDREF="FM84768""Save and Mount Volumes and License Software," on page 120.The installation utility sets the following defaults for IDXID="w3067"BOOK="_idx" COLLECTION="nw41" TIDREF="i2496"
block size. These block sizes minimize RAM and disk space requirements for the volume sizes indicated.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Volume sizeCOLNAME=2 ROTATE="0" MOREROWS="0"Block sizeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"0 to 31 MBCOLNAME=2 ROTATE="0" MOREROWS="0"4 KB or 8 KBCOLNAME=1 ROTATE="0" MOREROWS="0"32 to 149 MBCOLNAME=2 ROTATE="0" MOREROWS="0"16 KBCOLNAME=1 ROTATE="0" MOREROWS="0"150 to 499 MBCOLNAME=2 ROTATE="0" MOREROWS="0"32 KBCOLNAME=1 ROTATE="0" MOREROWS="0"500+ MBCOLNAME=2 ROTATE="0" MOREROWS="0"64 KBWe recommend accepting these defaults, but there may be advantages to adjusting block sizes.Small block sizes require more server memory to track the File Allocation Table (FAT) and Directory Entry Table (DET). Also, larger block sizes are best for large database records. Larger block sizes are preferred if block suballocation is enabled (seeIDREF="FM69043" "Enable/Disable Block Suballocation (Optional)," on page 116).Since you cannot change the block size once a volume is saved to disk, if you plan to eventually expand volumes, choose the block size according to the final predicted volume size.PAGENUM=113 ID="BP120"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"In the "Manage NetWare Volumes" screen, choose the volume whose block size you want to change, and press MOREINFO="NONE"<Enter>.The "Volume Information" screen appears.LABEL="3-25" FLOAT="0"The "Volume Information" ScreenFILEREF="n41i101a.tif"PERFORMANCE="REQUIRED"Use the arrow keys to highlight the "Volume Block Size" field and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Choose a new block size and press MOREINFO="NONE"<Enter>.Large block sizes (32 KB or 64 KB) can cause some DOS utilities to calculate the amount of free hard disk space incorrectly.PERFORMANCE="REQUIRED"Modify other volume parameters on 
IDREF="FM49972"pages 114 through 
IDREF="FM15242"118, or press 
MOREINFO="NONE"<Esc> and continue with 
IDREF="FM84768""Save and Mount Volumes and License Software," on page 120.
PAGENUM=114 ID="BP121"RENDERAS="SECT2"ID="FM49972"Enable/Disable File Compression (Optional)If you do not want to IDXID="w3068"BOOK="_idx" COLLECTION="nw41" TIDREF="i1318"
enable or disable IDXID="w3069"BOOK="_idx" COLLECTION="nw41" TIDREF="i1457"
file IDXID="w3070"BOOK="_idx" COLLECTION="nw41" TIDREF="i1105"
compression, you can go to any of the optional procedures in this section, or you can continue the installation by going to IDREF="FM84768""Save and Mount Volumes and License Software," on page 120.If file compression is enabled, files in a volume that are not accessed for a specified amount of time are converted to a compressed state, thus saving disk space. A compressed file becomes uncompressed when it is accessed.The default setting for file compression is "On."File compression is enabled at the volume level. To set individual files in that volume either with or without compression, you must use the FLAG utility or the NetWare Administrator utility (after installation).Once file compression for a volume is enabled and volume information is saved to disk, you can't change the compression status of the volume. You must delete the volume and re-create it to change the file compression status.To maximize disk space, you should enable both file compression and block suballocation (see IDREF="FM69043" "Enable/Disable Block Suballocation (Optional)," on page 116).For more information, see "BOOK="cncptenu" COLLECTION="nw41"File Compression" in Concepts or "BOOK="superenu" COLLECTION="nw41"Using File Compression" in Chapter 7 of Supervising the Network.PAGENUM=115 ID="BP122"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the "Manage NetWare Volumes" screen, choose the volume you want to change the file compression status for and press MOREINFO="NONE"<Enter>.The "Volume Information" screen appears.LABEL="3-26" FLOAT="0"The "Volume Information" ScreenFILEREF="n41i101a.tif"PERFORMANCE="REQUIRED"Use the arrow keys to highlight the "File Compression" field and press MOREINFO="NONE"<Enter>.The "Select a Volume Compression Setting" screen appears.PERFORMANCE="REQUIRED"Toggle between "On" and "Off" by pressing MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Modify other volume parameters on 
IDREF="FM69043"pages 116 through 
IDREF="FM15242"118 or press 
MOREINFO="NONE"<Esc> and continue with 
IDREF="FM84768""Save and Mount Volumes and License Software," on page 120.
PAGENUM=116 ID="BP123"RENDERAS="SECT2"IDXID="w3071"BOOK="_idx" COLLECTION="nw41" TIDREF="i474"IDXID="w3072"BOOK="_idx" COLLECTION="nw41" TIDREF="i1318"IDXID="w3073"BOOK="_idx" COLLECTION="nw41" TIDREF="i1105"IDXID="w3074"BOOK="_idx" COLLECTION="nw41" TIDREF="i4311"IDXID="w3075"BOOK="_idx" COLLECTION="nw41" TIDREF="i474"IDXID="w3076"BOOK="_idx" COLLECTION="nw41" TIDREF="i1318"IDXID="w3077"BOOK="_idx" COLLECTION="nw41" TIDREF="i1105"IDXID="w3078"BOOK="_idx" COLLECTION="nw41" TIDREF="i4311"
ID="FM69043"Enable/Disable Block Suballocation (Optional)If you do not want to enable or disable block suballocation, you can go to any of the optional procedures in this section, or you can continue the installation by going to IDREF="FM84768""Save and Mount Volumes and License Software," on page 120.Block suballocation allows the last part of several files to share one disk block, saving disk space.Block suballocation divides any partially used disk block into 512-byte suballocation blocks. These suballocation blocks are used to share the remainder of the block with "leftover" fragments of other files.For example, if block suballocation is not enabled, storing a 5KB file takes two 4KB blocks (on a volume with a 4KB block size); consequently, 3 KB of disk space is wasted.With block suballocation enabled, the same 5KB file takes up only 5 KB of disk space: one 4KB block and two 512-byte suballocation blocks of another 4KB block. Subsequent files in need of suballocation blocks take them from this block as well, until the 4KB block is used up.The default setting for block suballocation is "On."To maximize disk space, you should enable both file compression and block suballocation.  If you are considering using High Capacity Storage System (HCSS) now or in the future, we recommend turning block suballocation and file compression off.For more information, see "BOOK="cncptenu" COLLECTION="nw41"Block suballocation" in Concepts.PAGENUM=117 ID="BP124"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"In the "Manage NetWare Volumes" screen, choose the volume you want to change the block suballocation status for and press MOREINFO="NONE"<Enter>.The "Volume Information" screen appears.LABEL="3-27" FLOAT="0"The "Volume Information" ScreenFILEREF="n41i101a.tif"PERFORMANCE="REQUIRED"Use the arrow keys to highlight the "Block Suballocation" field and press MOREINFO="NONE"<Enter>.The "Select a Volume Compression Setting" screen appears.PERFORMANCE="REQUIRED"Toggle between "On" and "Off" by pressing MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Continue with 
IDREF="FM15242""Disable/Enable Data Migration (Optional)" on page 118, or press 
MOREINFO="NONE"<Esc> and go to 
IDREF="FM84768""Save and Mount Volumes and License Software," on page 120.
PAGENUM=118 ID="BP125"RENDERAS="SECT2"ID="FM15242"Disable/Enable IDXID="w3079"BOOK="_idx" COLLECTION="nw41" TIDREF="i914"IDXID="w3080"BOOK="_idx" COLLECTION="nw41" TIDREF="i1105"IDXID="w3081"BOOK="_idx" COLLECTION="nw41" TIDREF="i1318"
Data Migration (Optional)If you do not want to enable or disable data migration, you can go to any of the optional procedures in this section, or you can continue the installation by going to IDREF="FM84768""Save and Mount Volumes and License Software," on page 120.Enabling data migration lets you migrate (move) data to an external storage device (disk, tape, optical disk), while the NetWare operating system still perceives the data as residing on the volume.This frees up valuable hard disk space for frequently used files while still allowing access, though somewhat slower, to infrequently used files.For example, a law firm might store case reports on a 500MB volume. They don't want to archive these files, because they might need any of them at any time. Any single case, however, has only a small chance of being used.Enabling data migration allows this firm to call up to 256 GB of case data from their 500MB hard disk, when using Novell's High Capacity Storage System (HCSS). All cases are migrated and take only a few extra seconds to call up.The default setting for data migration is "Off."If you are planning to use an external storage system, this parameter must be set to "On." If you are planning on moving files to an optical storage system (such as HCSS), set file compression and block suballocation to "Off" to allow HCSS to optimize disk storage.For more information, see "BOOK="cncptenu" COLLECTION="nw41"Data migration" or "BOOK="cncptenu" COLLECTION="nw41"High Capacity Storage System" in Concepts and Chapter 6, "BOOK="superenu" COLLECTION="nw41"Migrating Data Using the High Capacity Storage System," in Supervising the Network.PAGENUM=119 ID="BP126"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"In the "Manage NetWare Volumes" screen, choose the volume you want to change the data migration status for and press MOREINFO="NONE"<Enter>.The "Volume Information" screen appears.LABEL="3-28" FLOAT="0"The "Volume Information" ScreenFILEREF="n41i101a.tif"PERFORMANCE="REQUIRED"Use the arrow keys to highlight the "Data Migration" field and press MOREINFO="NONE"<Enter>.The "Select a Volume Compression Setting" screen appears.PERFORMANCE="REQUIRED"Toggle between "On" and "Off" by pressing MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Continue with 
IDREF="FM84768""Save and Mount Volumes and License Software," on page 120.
PAGENUM=120 ID="BP127"RENDERAS="SECT1"ID="FM84768"Save and 
Mount Volumes and License SoftwarePrior to saving and mounting volumes and licensing the NetWare software, you should have made any desired modifications to the NetWare volumes settings.Once a volume is saved and mounted, you cannot make modifications to the volume settings covered on IDREF="FM51733"pages 108 through IDREF="FM15242"118 without deleting the volumes and re-creating them.The "Manage NetWare Volumes" screen should be present on your screen.LABEL="3-29" FLOAT="0"Manage NetWare Volumes ScreenFILEREF="n41in08a.tif"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"While in the list of volumes, press MOREINFO="NONE"<F10> to save all volume information.A confirmation screen appears.PERFORMANCE="REQUIRED"Select "Yes" to save the volume changes.After you have saved volume information to disk, the installation utility mounts all volumes to make them accessible to network users. 
PAGENUM=121 ID="BP128"The following screen appears.LABEL="3-30" FLOAT="0"Insert the License Diskette When PromptedFILEREF="n41in91a.tif"PERFORMANCE="REQUIRED"Insert your 
IDXID="w3082"BOOK="_idx" COLLECTION="nw41" TIDREF="i2105"IDXID="w3083"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"CLASS=DISKLicense diskette into drive A:.Be sure to keep your CLASS=DISKLicense diskette as a backup. You may need it in the future if your installed license should get corrupted.A message appears that the server 
IDXID="w3084"BOOK="_idx" COLLECTION="nw41" TIDREF="i1825"
license was successfully installed.PERFORMANCE="REQUIRED"Remove the 
CLASS=DISKLicense diskette and store it in a safe place.PERFORMANCE="REQUIRED"Continue by following the applicable path in the table below.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you are installing fromCOLNAME=2 ROTATE="0" MOREROWS="0"Continue withVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"CD-ROM or diskettesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM90248""Copy NetWare Files," on page 123COLNAME=1 ROTATE="0" MOREROWS="0"A remote network installation areaCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM34162""Establish Server-to-Server Session (Conditional)" on page 122PAGENUM=122 ID="BP129"RENDERAS="SECT1"ID="FM34162"Establish Server-to-Server Session (Conditional)IDXID="w3085"BOOK="_idx" COLLECTION="nw41" TIDREF="i4067"If you are installing from a remote network installation area, the following screen appears.LABEL="3-31" FLOAT="0"Enter your Password to Reconnect to the Source ServerFILEREF="n41in10a.tif"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Reenter your password to reconnect to the source server, and press MOREINFO="NONE"<Enter>When installing from a remote network installation area, a client connection to the source server is disrupted once the LAN driver is loaded.The path to the source server is recalled from memory, but the password must be reentered.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> again.PERFORMANCE="REQUIRED"Continue with 
IDREF="FM90248""Copy NetWare Files," on page 123.
PAGENUM=123 ID="BP130"RENDERAS="SECT1"ID="FM90248"Copy 
NetWare FilesThis part of the installation automatically IDXID="w3086"BOOK="_idx" COLLECTION="nw41" TIDREF="i843"
copies selected NetWare 4.1 
system files and utilities to IDXID="w3087"BOOK="_idx" COLLECTION="nw41" TIDREF="i4793"
volume SYS:.A screen appears prompting you to verify or change the source path.LABEL="3-32" FLOAT="0"Verify the Path Before CopyingFILEREF="n41in09a.tif"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Verify or change the source path and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Continue with 
IDREF="FM80634""Select Optional NetWare File Groups," on page 124.
PAGENUM=124 ID="BP131"RENDERAS="SECT1"ID="FM80634"Select Optional NetWare File GroupsOnce the selected system files and utilities have been copied, the following menu appears.LABEL="3-33" FLOAT="0"Choose Applicable NetWare FilesFILEREF="n41in63a.tif"File groups such as those for NetWare workstation utilities can be copied to the SYSTEM, PUBLIC, LOGIN, and MAIL directories on volume SYS:. (These directories are created by NetWare.) All file groups except for the language-specific files at the bottom of the menu are initially selected to be copied.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"ID="FM90105"Indicate which file groups you do not want to load by highlighting each group and pressing MOREINFO="NONE"<Enter>.For example, if you don't have any OS/2 client workstations in your internetwork, you probably do not want to take up disk space by copying OS/2 workstation utilities to the server. (You can selectively install OS/2 utilities, as well as all the other utilities, at a later date, if needed.)To select a file group you previously deselected, press MOREINFO="NONE"<Enter> again. An "
x" appears next to the file group to indicate that it has been selected for copying to the server.If you plan to access the server to make client diskettes, or to access the latest VLMs from the server, you should select "Set up a Network Directory for Client Install." This creates the CLIENT directory in SYS:PUBLIC where the client files are then stored.PERFORMANCE="REQUIRED"ID="FM42080"To start copying files, press 
MOREINFO="NONE"<F10>.
PAGENUM=125 ID="BP132"At this time, NetWare copies only the SYSTEM and LOGIN files necessary to continue the installation. Once NetWare Directory Services has been installed, the remaining files, including those selected in 
IDREF="FM90105"Step 1, are copied.LABEL="3-34" FLOAT="0"The Files Needed to Continue Are CopiedFILEREF="n41in89a.tif"PERFORMANCE="REQUIRED"(Conditional) If you are installing from diskettes, insert the NetWare diskettes you are prompted for into drive A: and press MOREINFO="NONE"<Enter>.
PAGENUM=126 ID="BP133"PERFORMANCE="REQUIRED"(Conditional) If you selected the TCP/IP protocol in 
IDREF="FM96317"Step 2 on page 92, indicate whether you want to install NetWare IPTM from the menu below.LABEL="3-35" FLOAT="0"You Are Given the Option to Install NetWare IPFILEREF="n41in01a.tif"You must have purchased 
IDXID="w3088"BOOK="_idx" COLLECTION="nw41" TIDREF="i2833"IDXID="w3089"BOOK="_idx" COLLECTION="nw41" TIDREF="i1825"
NetWare/IPTM previously to install NetWare/IP at this time. NetWare/IP can also be installed later.If you select "Yes," refer to the documentation that came with NetWare/IP to complete the NetWare/IP installation. Then return to this manual to complete the server installation.PERFORMANCE="REQUIRED"Continue with 
IDREF="FM32481""Installing NetWare Directory Services" on page 127.
PAGENUM=127 ID="BP134"RENDERAS="SECT1"ID="FM32481"Installing NetWare Directory ServicesIDXID="w3090"BOOK="_idx" COLLECTION="nw41" TIDREF="i2727"Once the preliminary files have been copied to the server, the network is scanned for Directory trees. Unless you are installing the first NetWare 4 server in the network, you will most likely want to install the server into an existing Directory tree.Based on your network configuration, one of the following screens appears.LABEL="3-36" FLOAT="0"ID="FM35033"When No Directory Tree Is LocatedFILEREF="n41i112a.tif"If no NetWare 4 server (and accompanying Directory tree) can be located on the network, the menu shown above appears.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IfCOLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"The menu in IDREF="FM35033"Figure 3-36COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM10364" "A Nonlocatable Directory Tree, or the First Server," on page 129LABEL="3-37" FLOAT="0"IDXID="w3091"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"ID="FM83312"When a Single Directory Tree Is LocatedFILEREF="n41i103a.tif"If a single Directory tree is located, the Directory tree name is displayed as in the menu above.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IfCOLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"The menu in IDREF="FM83312"Figure 3-37 appearsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM69152""A Single Directory Tree Is Found" on page 141PAGENUM=128 ID="BP135"LABEL="3-38" FLOAT="0"ID="FM18978"When Multiple Directory Trees Are LocatedFILEREF="n41in59a.tif"If multiple Directory trees are located, the menu shown above appears.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IfCOLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"The menu in IDREF="FM18978"Figure 3-38 appearsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM72796""Multiple Directory Trees are Found" on page 144PAGENUM=129 ID="BP136"RENDERAS="SECT2"ID="FM10364"A Nonlocatable Directory Tree, or the First ServerIDXID="w3092"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"The menu below appears if there is no previously-installed NetWare 4 server, or the server you are installing cannot see the previously-installed NetWare 4 server(s).LABEL="3-39" FLOAT="0"When No Directory Tree Is LocatedFILEREF="n41i112a.tif"RENDERAS="SECT3"ID="FM66916"If the Server Cannot Locate a Directory Tree that Was Installed PreviouslyRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the "Is This the First NetWare 4 Server?" menu, choose "No, Connect to Existing NetWare 4 Network" and press MOREINFO="NONE"<Enter>.The following menu appears.LABEL="3-40" FLOAT="0"Select NetWare 4 Network MenuFILEREF="n41i114a.tif"You can find out the network name by loading MONITOR.NLM on an existing server on the network. The network name is the same as the Directory tree name.PAGENUM=130 ID="BP137"PERFORMANCE="REQUIRED"ID="FM99334"Select one of the menu options.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IfCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"You have verified that an existing NetWare 4 server is up and physically connected to this server, and that both servers are bound to IPX with the proper LAN driver, frame type, and IPX external network numberCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "Recheck for NetWare 4 Network" and press MOREINFO="NONE"<Enter>.If a single Directory tree is located, go toIDREF="FM69152" "A Single Directory Tree Is Found," on page 141If multiple Directory trees are located, go to IDREF="FM72796" "Multiple Directory Trees are Found," on page 144 COLNAME=1 ROTATE="0" MOREROWS="0"Your network has SAP filtering and you know the IPX internal network number of an existing NetWare 4 serverCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "Specify Address of NetWare 4 Server" and press MOREINFO="NONE"<Enter>.Enter the name of the Directory tree and press MOREINFO="NONE"<Enter>.Enter the IPX internal network number of an existing NetWare 4 server in the Directory tree and press MOREINFO="NONE"<Enter>.If a single Directory tree is located, go to IDREF="FM69152" "A Single Directory Tree Is Found," on page 141If multiple Directory trees are located, go to IDREF="FM72796" "Multiple Directory Trees are Found," on page 144 PAGENUM=131 ID="BP138"RENDERAS="SECT3"ID="FM96975"If This Is the First NetWare 4 ServerRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Choose "Yes, This Is the IDXID="w3093"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"
First NetWare 4 Server" and press MOREINFO="NONE"<Enter>.The following screen appears, ready for you to name your new Directory tree.LABEL="3-41" FLOAT="0"Enter a name for the Directory treeFILEREF="n41in12a.tif"For help on rules for naming a Directory tree, press 
MOREINFO="NONE"<F1>.PERFORMANCE="REQUIRED"Specify the 
IDXID="w3094"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"
Directory tree name and press MOREINFO="NONE"<Enter>. Each Directory tree (hierarchy of the NetWare Directory database) must have a name that's unique across the internetwork. (Most organizations will have only one Directory tree.) The tree name 
MARK=BULLETEnables client workstations to access data on multiple servers in a Directory tree without logging in to each server.Enables client workstations to log in to different Directory trees by specifying the tree name.Each Directory tree has its own database of objects that is not visible from another tree. Be aware of this limitation before creating multiple Directory trees.Once a Directory tree name has been entered, a list of time zones appears. (This list does not contain all existing time zones.) 
PAGENUM=132 ID="BP139"PERFORMANCE="REQUIRED"ID="FM43164"Set up 
IDXID="w3095"BOOK="_idx" COLLECTION="nw41" TIDREF="i4357"IDXID="w3096"BOOK="_idx" COLLECTION="nw41" TIDREF="i4478"
time synchronization.Time synchronization is important to NDS, because it 
MARK=BULLETMonitors and adjusts a NetWare server's internal time to ensure consistency of reported time across the network.Indicates when a server's time is synchronized with the rest of the network.Provides time stamps to establish the order of events in the Directory.Setting up time synchronization incorrectly can cause network synchronization problems within the Directory database.For more information on time synchronization, see "
BOOK="getstenu" COLLECTION="nw41"Understanding Time Synchronization in NDS" in 
Introduction to NetWare Directory Services, "
BOOK="superenu" COLLECTION="nw41"Managing Network Time Synchronization" in Chapter 7 of 
Supervising the Network, and "
BOOK="cncptenu" COLLECTION="nw41"Time synchronization" in 
Concepts.To enable time synchronization, you need to specify
MARK=BULLETWhat time zone the server will be in.What type of time server category this server falls into.Whether the server is in a zone that observes daylight saving time.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Choose the 
IDXID="w3097"BOOK="_idx" COLLECTION="nw41" TIDREF="i4254"
time zone this server is installed in.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If the time zoneCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Is listedCOLNAME=2 ROTATE="0" MOREROWS="0"Move the cursor to the appropriate time zone and press MOREINFO="NONE"<Enter>. Verify that the information presented is correct. If it is, press MOREINFO="NONE"<F10> and skip to IDREF="FM76826"Step 4If it isn't, follow IDREF="FM77174"Steps 3b through IDREF="FM91569"3j to enter the correct information.COLNAME=1 ROTATE="0" MOREROWS="0"Is not listedCOLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<Ins> and continue with IDREF="FM77174"Step 3bPERFORMANCE="REQUIRED"At the "Time Configuration Parameters" screen, 
ID="FM77174"verify or specify time synchronization parameters.The following screen appears. The cursor will be in the "Standard Time Zone Abbreviation" field. PAGENUM=133 ID="BP140"LABEL="3-42" FLOAT="0"ID="FM62712"Time Configuration ScreenFILEREF="n41in56a.tif"PERFORMANCE="REQUIRED"(Conditional) If you want to choose a different 
IDXID="w3098"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"IDXID="w3099"BOOK="_idx" COLLECTION="nw41" TIDREF="i4478"
time server type, highlight the "Time Server 
IDXID="w3100"BOOK="_idx" COLLECTION="nw41" TIDREF="i4619"
Type" field and press MOREINFO="NONE"<Enter>.There are four time server types: MARK=BULLETSingle ReferenceReferencePrimarySecondaryThe default sets the first NetWare 4.1 server in a Directory tree as a Single Reference server. All other servers default as Secondary servers.Do not change the time server defaults without a clear understanding of time server types. Press MOREINFO="NONE"<F1> for help, or refer to "BOOK="getstenu" COLLECTION="nw41"Time Servers" in Chapter 4 of Introduction to NetWare Directory Services for a description of these time server types.PAGENUM=134 ID="BP141"PERFORMANCE="REQUIRED"In the "Standard Time Zone Abbreviation" field, enter the three-letter abbreviation for your standard 
IDXID="w3101"BOOK="_idx" COLLECTION="nw41" TIDREF="i4496"
time zone and press MOREINFO="NONE"<Enter>.Not all time zones have agreed-upon abbreviations. Time zone information is subject to local custom and national rules. Find out what the commonly used abbreviation for your standard time zone is, or enter your own abbreviation. The time information you specify is saved in this server's AUTOEXEC.NCF file. You can change it later by editing this file (see IDREF="FM86651""Modify the AUTOEXEC.NCF File" on page 156).PERFORMANCE="REQUIRED"In the "Standard Time Offset from UTC" field, enter the 
IDXID="w3102"BOOK="_idx" COLLECTION="nw41" TIDREF="i3067"IDXID="w3103"BOOK="_idx" COLLECTION="nw41" TIDREF="i836"
offset (in hours) from UTC (Universal Coordinated Time, formerly known as Greenwich Mean Time) and press MOREINFO="NONE"<Enter>.If your time zone is east of UTC, use "AHEAD" with the number, since your time is ahead of UTC. For example, in Germany, you would type "1" and then press MOREINFO="NONE"<Enter> to toggle to "AHEAD."If your time zone is west of UTC, toggle to "BEHIND," because your time is behind UTC. Use the following illustration to find your time zone's offset from 
UTC.PAGENUM=135 ID="BP142"LABEL="3-43" FLOAT="0"IDXID="w3104"BOOK="_idx" COLLECTION="nw41" TIDREF="i4847"IDXID="w3105"BOOK="_idx" COLLECTION="nw41" TIDREF="i4496"World Time Zones and Their Offsets from UTCFILEREF="n40in29a.tif"PERFORMANCE="REQUIRED"In the "Does Your Area Have Daylight Saving Time (DST)" field, press MOREINFO="NONE"<Enter> and use the arrow keys to toggle between "Yes" and "No."LABEL="3-5" PGWIDE=1 TOCENTRY="1" Daylight Saving Time OptionsCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="4*"COLNAME=3 COLWIDTH="7*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IfCOLNAME=2 ROTATE="0" MOREROWS="0"Then chooseCOLNAME=3 ROTATE="0" MOREROWS="0"And thenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Your time zone switches to daylight saving time (and back to standard time) during each yearCOLNAME=2 ROTATE="0" MOREROWS="0"YesCOLNAME=3 ROTATE="0" MOREROWS="0"Continue with IDREF="FM23432"Step 3gCOLNAME=1 ROTATE="0" MOREROWS="0"Your time zone never switches to daylight saving timeCOLNAME=2 ROTATE="0" MOREROWS="0"NoCOLNAME=3 ROTATE="0" MOREROWS="0"Go to IDREF="FM65195"Step 3kPAGENUM=136 ID="BP143"PERFORMANCE="REQUIRED"ID="FM23432"In the "DST Time Zone Abbreviation" field, enter the three-letter abbreviation your time zone uses during 
IDXID="w3106"BOOK="_idx" COLLECTION="nw41" TIDREF="i943"IDXID="w3107"BOOK="_idx" COLLECTION="nw41" TIDREF="i4496"
daylight saving time and press MOREINFO="NONE"<Enter>.If you do not specify the abbreviation for daylight saving time, the server won't automatically adjust for the seasonal change. Internal algorithms assume that if no DST abbreviation is specified, local custom is to not observe DST.Not all time zones have agreed-upon abbreviations. Time zone information is subject to local custom and national rules. Find out what the commonly used abbreviation for your daylight saving time zone is, or enter your own abbreviation. PERFORMANCE="REQUIRED"In the "DST Offset from Standard Time" field, enter the 
IDXID="w3108"BOOK="_idx" COLLECTION="nw41" TIDREF="i3067"
difference between standard time and daylight saving time and press MOREINFO="NONE"<Enter>.Enter the offset in hours:minutes:seconds. The default is 1:00:00 (one hour) ahead, meaning that your daylight saving time is one hour ahead of your standard time.If daylight saving time in your area varies from your standard time by more or less than the default (one hour), enter a different time offset.PERFORMANCE="REQUIRED"In the "DST Start" field, specify the starting day for daylight saving time and press MOREINFO="NONE"<Enter>.Follow the screen prompts to decide which format to use.PERFORMANCE="REQUIRED"ID="FM91569"In the "DST End" field, specify the day daylight saving time ends and press MOREINFO="NONE"<Enter>.Follow the screen prompts to decide which format to use.PERFORMANCE="REQUIRED"ID="FM65195"Save the time configuration information by pressing 
MOREINFO="NONE"<F10> and then MOREINFO="NONE"<Enter>.
PAGENUM=137 ID="BP144"PERFORMANCE="REQUIRED"ID="FM76826"Specify the 

server's (name) 
IDXID="w3109"BOOK="_idx" COLLECTION="nw41" TIDREF="i2727"
context.The following screen appears, prompting you to specify the server's NDS context.LABEL="3-44" FLOAT="0"Server Context ScreenFILEREF="n41in55a.tif"The 

server context, or name context, specifies where the server is located in the hierarchical Directory tree. The context is composed of 
MARK=BULLETA company or organization name (example: O=Novell).Optional names of organizational units and subunits, such as divisions or departments (example: OU=Sales).An optional country code (example: C=US).For recommendations on how to lay out your Directory tree, see "BOOK="getstenu" COLLECTION="nw41"Planning NetWare Directory Services Implementation" in Chapter 5 of Introduction to NetWare Directory Services.PAGENUM=138 ID="BP145"For 

example, if your NetWare server were located in the "Sales_LA" group of the Sales department of a company called "Novell_US," the server's context would look like this:LABEL="3-45" FLOAT="0"ID="FM47603"Example of a ContextFILEREF="n40in24a.tif"The object IDXID="w3110"BOOK="_idx" COLLECTION="nw41" TIDREF="i36"
"[Root]" is automatically created during NDS installation. For more information on context and naming conventions, see "
BOOK="getstenu" COLLECTION="nw41"Understanding NetWare Directory Services" in Chapter 1 of 
Introduction to NetWare Directory Services and "
BOOK="cncptenu" COLLECTION="nw41"Context" in 
Concepts.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"ID="FM57773"In the "
IDXID="w3111"BOOK="_idx" COLLECTION="nw41" TIDREF="i711"
Company or Organization" field, type your company or organization name and press MOREINFO="NONE"<Enter>.Only valid characters (letters A through Z or a through z, numbers 0 through 9, hyphen, underscore) may be used. PERFORMANCE="REQUIRED"(Optional) In the "Level 1 (Sub)Organizational Unit" field, type in an 
IDXID="w3112"BOOK="_idx" COLLECTION="nw41" TIDREF="i3113"
Organizational Unit name (such as a division or a department) and press MOREINFO="NONE"<Enter>.Use this name to further specify your Directory tree. This could be a division name, a locality name, a department name, or anything that reflects your organization's structure.Notice that the information in the "Server Context" field is updated every time you enter a new name.PERFORMANCE="REQUIRED"(Optional) In the "Level 2 (Sub)Organizational Unit" field, type in an additional Organizational Unit name and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"(Optional) In the "Level 3 (Sub)Organizational Unit" field, type in an additional Organizational Unit name and press MOREINFO="NONE"<Enter>.
PAGENUM=139 ID="BP146"You can manually enter more than three levels of Organizational Units (up to 25) into the "Server Context" field. Make sure you enter a period (.) as a delimiter between each new name entry.PERFORMANCE="REQUIRED"ID="FM41118"(Optional) Return to the "Server Context" field and type a 
IDXID="w3113"BOOK="_idx" COLLECTION="nw41" TIDREF="i859"IDXID="w3114"BOOK="_idx" COLLECTION="nw41" TIDREF="i859"
country code or additional Organizational Units and press MOREINFO="NONE"<Enter>.Enter the country code after the company name, separated by a period. For example, if your country is France, add ".C=FR" to the end of the server context. Although a country code is not required, it can be useful in a multinational organization. For a list of country codes, see IDREF="FM47650"Appendix B, "Country Codes," on page 279.Adding a IDXID="w3115"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
country name to the context may create some problems with default naming in some NetWare 4.1 utilities, because the utilities assume the highest level to be O=organization.  That means that if you use Country in the Directory tree, you always have to include name typing (CN=.OU=.O=) whenever you log in or refer to an object name in the tree, regardless of what context you or the other object are in. For example, if you included the country code for the United States (US), the object name for Dave Smith might beCN=DSMITH.OU=ACCOUNTING.O=NOVELL.C=US  For more information, see "BOOK="getstenu" COLLECTION="nw41"Directory Objects" in Introduction to NetWare Directory Services and "BOOK="utlrfenu" COLLECTION="nw41"CX" in Utilities Reference.If you want to establish more than three Organizational Unit levels, you can do so while in the "Server Context" field. For example, if you wanted to create a fourth Organizational Unit level in IDREF="FM47603"Figure 3-45, you would type OU=organizational unit name on the left end of the context.PERFORMANCE="REQUIRED"Record the administrator's name on the NetWare 4.1 Server Worksheet on 
IDREF="FM68531"page 175. The default common name (CN) for the administrator of the first NetWare 4.1 server in a Directory tree is ADMIN. The installation program creates this User object ADMIN directly under the Organization (O=) level.
PAGENUM=140 ID="BP147"The administrator can 
MARK=BULLETManage this Server object.Manage User objects in this container.Manage the Directory tree (only applies to ADMIN created on the first NetWare 4.1 server).You can change the name of user ADMIN using the NETADMIN (or NetWare Administrator) utility after the server is installed and you have set up a workstation.PERFORMANCE="REQUIRED"ID="FM31872"Type the administrator's password and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"At the prompt, retype the password and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"(Optional) Record the password on the NetWare 4.1 Server Worksheet on 
IDREF="FM68531"page 175.This password is also the password for the bindery user SUPERVISOR. If you change the administrator password later, the IDXID="w3116"BOOK="_idx" COLLECTION="nw41" TIDREF="i4330"
SUPERVISOR password will not change until you change it using the SYSCON utility.PERFORMANCE="REQUIRED"To save Directory information, press 
MOREINFO="NONE"<F10>.A message appears indicating that NetWare Directory Services is being installed.PERFORMANCE="REQUIRED"Review 
IDREF="FM49655""How Does the Directory Tree Appear Now?," on page 151 and 
IDREF="FM77581""What Trustee Assignments were Created During the Installation?," on page 152. Then continue with 
IDREF="FM37645""Modify the STARTUP.NCF File," on page 153.
PAGENUM=141 ID="BP148"RENDERAS="SECT2"ID="FM69152"A Single Directory Tree Is FoundIf, after scanning the network, a single Directory tree is found, the tree name is displayed along with the following menu.LABEL="3-46" FLOAT="0"When a Single Directory Tree Is FoundFILEREF="n41i103a.tif"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Choose an option from the menu.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IfCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"You want to install into the displayed Directory treeCOLNAME=2 ROTATE="0" MOREROWS="0"Go toIDREF="FM43190" "Install into the Displayed Directory Tree," on page 142COLNAME=1 ROTATE="0" MOREROWS="0"You wish to install into a Directory tree that is not displayedCOLNAME=2 ROTATE="0" MOREROWS="0"Go toIDREF="FM66916" "If the Server Cannot Locate a Directory Tree that Was Installed Previously," on page 129 COLNAME=1 ROTATE="0" MOREROWS="0"You want to create a new Directory treeCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "Select Another Tree" and press MOREINFO="NONE"<Enter>.Press MOREINFO="NONE"<Ins>.At the confirmation prompt, press MOREINFO="NONE"<Enter>.Follow the procedures underIDREF="FM96975" "If This Is the First NetWare 4 Server," on page 131 PAGENUM=142 ID="BP149"RENDERAS="SECT2"ID="FM43190"Install into the Displayed Directory TreeInstall the new NetWare 4.1 server into the Directory tree displayed in the menu below, by following the procedures that follow.LABEL="3-47" FLOAT="0"When a Single Directory Tree Is FoundFILEREF="n41i103a.tif"Depending on its structure, the displayed Directory tree can be either a "simple" tree (only one level) or a "custom tree (multilevel).RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Choose "Install into Tree tree name" and press MOREINFO="NONE"<Enter>.A list of time zones appear.PERFORMANCE="REQUIRED"Set up time synchronization by completing 
IDREF="FM43164"Step 3 on page 132.After setting up time synchronization, one of the following screens appear.LABEL="3-48" FLOAT="0"IDXID="w3117"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"IDXID="w3118"BOOK="_idx" COLLECTION="nw41" TIDREF="i4155"ID="FM93241"When a Simple Directory Tree Is FoundFILEREF="n41in06a.tif"PAGENUM=143 ID="BP150"LABEL="3-49" FLOAT="0"IDXID="w3119"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"IDXID="w3120"BOOK="_idx" COLLECTION="nw41" TIDREF="i902"ID="FM84976"When a Custom Directory Tree Is FoundFILEREF="n41in07a.tif"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IfCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"The screen in IDREF="FM93241"Figure 3-48appearsCOLNAME=2 ROTATE="0" MOREROWS="0"Type the administrator password and press MOREINFO="NONE"<Enter>.Continue withIDREF="FM37645""Modify the STARTUP.NCF File," on page 153COLNAME=1 ROTATE="0" MOREROWS="0"The screen in IDREF="FM84976"Figure 3-49appearsCOLNAME=2 ROTATE="0" MOREROWS="0"If necessary, type the administrator name and press MOREINFO="NONE"<Enter>.Type the administrator password and press MOREINFO="NONE"<Enter>.Go to IDREF="FM57773"page 138 and complete IDREF="FM57773"Steps 4a through IDREF="FM41118"4e to set up the server's context.Then continue withIDREF="FM37645""Modify the STARTUP.NCF File," on page 153COLNAME=1 ROTATE="0" MOREROWS="0"The screen in IDREF="FM93241"Figure 3-48 appears and you want to customize the Directory treeCOLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<F4>.If necessary, type the administrator name and press MOREINFO="NONE"<Enter>.Type the administrator password and press MOREINFO="NONE"<Enter>.Go to IDREF="FM57773"page 138 and complete IDREF="FM57773"Steps 4aSteps  through IDREF="FM41118"4eThen continue with IDREF="FM37645""Modify the STARTUP.NCF File," on page 153PAGENUM=144 ID="BP151"RENDERAS="SECT2"ID="FM72796"Multiple Directory Trees are FoundIf multiple Directory trees are found, the "Existing Directory Trees" menu appears.LABEL="3-50" FLOAT="0"When Multiple Directory Trees Are FoundFILEREF="n41in59a.tif"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Choose the IDXID="w3121"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"
Directory tree you want this server to be part of. A list appears of all Directory trees that are visible from this server. Most organizations will have only one Directory tree. The tree name is established during the installation of the first NetWare 4.1 server in a tree. Make sure you choose the correct Directory tree name. If your organization has more than one tree, attaching to the wrong tree or creating a new Directory tree will prevent this server from sharing data within the desired Directory database.Choosing an existing tree makes this new server part of that tree's NetWare Directory database.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"(Conditional) If the Directory tree you want this server to be part of is not displayed, verify that an existing NetWare 4 server in that tree is up and physically connected to this server, and that both servers are bound to IPX with the proper LAN driver, frame type, and IPX external network number. Then press 
MOREINFO="NONE"<F4> to rebuild the list.PERFORMANCE="REQUIRED"(Conditional) If your network has SAP filtering and you know the IPX internal network number of an existing NetWare 4 server, press 
MOREINFO="NONE"<F3> and enter the name of the Directory tree and press MOREINFO="NONE"<Enter>. Then, enter the IPX internal network number of an existing NetWare 4 server in the Directory tree and press MOREINFO="NONE"<Enter>.
PAGENUM=145 ID="BP152"PERFORMANCE="REQUIRED"(Conditional) If you need to create a new Directory tree on the network, press 
MOREINFO="NONE"<Ins>. At the confirmation prompt, press MOREINFO="NONE"<Enter>. Follow the procedures under 
IDREF="FM96975""If This Is the First NetWare 4 Server," on page 131.PERFORMANCE="REQUIRED"Specify 
IDXID="w3122"BOOK="_idx" COLLECTION="nw41" TIDREF="i4357"IDXID="w3123"BOOK="_idx" COLLECTION="nw41" TIDREF="i4478"
time synchronization parameters. PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Choose the time zone you want to install this server in.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If COLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Your time zone is listedCOLNAME=2 ROTATE="0" MOREROWS="0"Move the cursor to your time zone and press MOREINFO="NONE"<Enter>. Verify that the information presented is correct.If it is, press <F10> and continue with IDREF="FM39321"Step 3If it isn't, enter the correct information using IDREF="FM77174"Steps 3bthrough IDREF="FM91569"3j beginning on IDREF="FM10364"page 129COLNAME=1 ROTATE="0" MOREROWS="0"Your time zone is not listedCOLNAME=2 ROTATE="0" MOREROWS="0"Press <Ins> and proceed with IDREF="FM77174"Step 3bunder IDREF="FM96975" "If This Is the First NetWare 4 Server," on page 131The time configuration defaults for all servers except the first NetWare 4.1 server appear. LABEL="3-51" FLOAT="0"Time Configuration ScreenFILEREF="n40in57a.tif"PAGENUM=146 ID="BP153"PERFORMANCE="REQUIRED"(Conditional) If you chose a simple Directory tree, the following screen appears.LABEL="3-52" FLOAT="0"If You Chose a Simple Directory TreeFILEREF="n41in06a.tif"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IfCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"You want to install this server into the simple Directory treeCOLNAME=2 ROTATE="0" MOREROWS="0"Type the administrator password and press MOREINFO="NONE"<Enter>.Continue withIDREF="FM37645" "Modify the STARTUP.NCF File," on page 153COLNAME=1 ROTATE="0" MOREROWS="0"You want to customize the simple Directory tree (create multiple levels)COLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<F4>.If necessary, type the administrator name and press MOREINFO="NONE"<Enter>.Type the administrator password and press MOREINFO="NONE"<Enter>.Go to IDREF="FM57773"page 138and complete IDREF="FM57773"Steps 4athrough IDREF="FM41118"4e to set up the server's context.Continue withIDREF="FM37645" "Modify the STARTUP.NCF File," on page 153PERFORMANCE="REQUIRED"In the "Verify/Enter Time Configuration Information for this Server" screen, verify or specify time synchronization parameters.Refer to "BOOK="getstenu" COLLECTION="nw41"Understanding Time Synchronization in NDS" in Introduction to NetWare Directory Services for information on how to plan for time synchronization.Then see IDREF="FM10364""A Nonlocatable Directory Tree, or the First Server" on page 129 for instructions on how to configure time parameters.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to save and continue.After you have finished setting up time synchronization, you are prompted to specify a Directory administrator login name and password.PAGENUM=147 ID="BP154"PERFORMANCE="REQUIRED"ID="FM39321"(Conditional) If the administrator's name is not displayed, type the administrator's name and press MOREINFO="NONE"<Enter>. Enter the complete name of the administrator. This could be
MARK=BULLETYour login name.The name of any User object with the Supervisor object right to this context. User object ADMIN. For example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"CN=ADMIN.O=NOVELL MOREINFO="NONE"<Enter>Or, if you specified a country
FORMAT="LINESPECIFIC"MOREINFO="NONE"CN=ADMIN.O=Novell.C=USFor more information about complete context names, refer to 
BOOK="getstenu" COLLECTION="nw41"Introduction to NetWare Directory Services.When the first NetWare 4.1 server is installed, the administrator's default name is ADMIN, but this name could have been changed after the first NetWare 4.1 server was installed.There also could be more than one administrator in your Directory tree. Without supplying the correct name, you cannot install this server as part of the Directory tree.PERFORMANCE="REQUIRED"ID="FM30080"Type the administrator's password and press MOREINFO="NONE"<Enter>.This password authenticates the administrator (the user installing the server) to the Directory.
PAGENUM=148 ID="BP155"PERFORMANCE="REQUIRED"In the screen shown below, choose an existing NetWare 4.1 

context or specify a new one.LABEL="3-53" FLOAT="0"Specify the Server ContextFILEREF="n41in58a.tif"COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Place this new server into a context that has been previously definedCOLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<Enter> at each organizational level to view existing container objects and choose the object you need.COLNAME=1 ROTATE="0" MOREROWS="0"Define a new context for this serverCOLNAME=2 ROTATE="0" MOREROWS="0"Enter one or more new Organizations (O=) and/or Organizational Units (OU=). See below for examples.You can either place this new server into a previously defined context or you can specify a new context. By defining a context that doesn't exist yet, you "create" the context---that is, you create a new branch in the Directory tree. Assume the context of the only existing NetWare 4.1 server is MOREINFO="NONE"OU=NEW_PRODUCTS.OU=MARKETING.O=NOVELLIf you specify the new server's context asMOREINFO="NONE"OU=SALES.O=NOVELLthe Directory tree will have a new "branch" (Sales). After server installation, you can view your Directory tree using the NETADMIN or NetWare Administrator utility.
PAGENUM=149 ID="BP156"The following illustration shows the expanded example tree.

FILEREF="n41in54a.tif"By default, the installation utility adds a replica of the partition that contains the server's context only if the total number of existing replicas is less than three.  However, if the server is not a NetWare 4 server and contains bindery files (SYS:SYSTEM\NET$*.SYS), a replica will be added, regardless of the number of replicas.  In the example above, the master replica of the partition "OU=Sales" resides on server SALESERVER. Its read-write replica resides on server SERVER1. You can modify partitions with the PARTMGR or NetWare Administrator utility, after server and workstation installations are complete.  For more information on Directory partitions, see "BOOK="getstenu" COLLECTION="nw41"Understanding NetWare Directory Services" in Introduction to NetWare Directory Services and "BOOK="cncptenu" COLLECTION="nw41"NetWare Directory partition" in Concepts. PAGENUM=150 ID="BP157"PERFORMANCE="REQUIRED"To save Directory information, press 
MOREINFO="NONE"<F10>.A confirmation menu appears.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> to select "Yes."PERFORMANCE="REQUIRED"ID="FM99983"Review
IDREF="FM49655" "How Does the Directory Tree Appear Now?," on page 151 and
IDREF="FM77581" "What Trustee Assignments were Created During the Installation?," on page 152. Then continue with
IDREF="FM37645" "Modify the STARTUP.NCF File," on page 153.
PAGENUM=151 ID="BP158"RENDERAS="SECT3"ID="FM49655"How Does the Directory Tree Appear Now?The following objects were created in the Directory tree:MARK=BULLETIDXID="w3124"BOOK="_idx" COLLECTION="nw41" TIDREF="i2796"IDXID="w3125"BOOK="_idx" COLLECTION="nw41" TIDREF="i4044"
Server object.IDXID="w3126"BOOK="_idx" COLLECTION="nw41" TIDREF="i4787"
Volume objects (servername_SYS and other volumes you specified).User object IDXID="w3127"BOOK="_idx" COLLECTION="nw41" TIDREF="i118"
ADMIN (the IDXID="w3128"BOOK="_idx" COLLECTION="nw41" TIDREF="i122"IDXID="w3129"BOOK="_idx" COLLECTION="nw41" TIDREF="i122"
administrator who has Supervisor object rights to this context). The installation utility places this object directly under the Organization level.User object ADMIN is created only once, and only on the first server in the Directory tree.User object IDXID="w3130"BOOK="_idx" COLLECTION="nw41" TIDREF="i4330"
Supervisor (for bindery services purposes only). This object can be recognized only from pre-NetWare 4.1 utilities. User object Supervisor takes on User object ADMIN's password. These objects are placed in the same context you defined for your server. The following illustration shows what your IDXID="w3131"BOOK="_idx" COLLECTION="nw41" TIDREF="i1082"
Directory tree might look like after you installed your first NetWare 4.1 server.FILEREF="n41in23a.tif"PAGENUM=152 ID="BP159"RENDERAS="SECT3"ID="FM77581"What Trustee Assignments were Created During the Installation?IDXID="w3132"BOOK="_idx" COLLECTION="nw41" TIDREF="i4593"IDXID="w3133"BOOK="_idx" COLLECTION="nw41" TIDREF="i3995"IDXID="w3134"BOOK="_idx" COLLECTION="nw41" TIDREF="i960"MARK=BULLETIDXID="w3135"BOOK="_idx" COLLECTION="nw41" TIDREF="i3853"User object IDXID="w3136"BOOK="_idx" COLLECTION="nw41" TIDREF="i118"
ADMIN has the Supervisor object right on the [Root] object. By inheritance, ADMIN also has the Supervisor right on all Volume objects in the Directory.IDXID="w3137"BOOK="_idx" COLLECTION="nw41" TIDREF="i35"
[Public] has the Browse right on the [Root] object.[Public] is equal to the group EVERYONE in the NetWare 3 environment. Any IDXID="w3138"BOOK="_idx" COLLECTION="nw41" TIDREF="i810"
container object has Read and File Scan rights to the PUBLIC directories of all system volumes in that container.The [Root] object (or security equivalent) of a tree has the Browse right on all User objects in that tree. This can be blocked by an Inherited Rights Filter or removed from a container's trustee list (ACL).The IDXID="w3139"BOOK="_idx" COLLECTION="nw41" TIDREF="i36"
[Root] object has the Read right to the member property of any Group object.The [Root] object has the Read right to the following properties of any Volume object: host server name (the server that the physical volume resides on) and host resource (the physical volume).All IDXID="w3140"BOOK="_idx" COLLECTION="nw41" TIDREF="i4715"
User objects have the Read right to their own properties and to the properties of any profile they belong to. User objects also have Read and Write rights to their user login script. For more information on rights and trustee assignments, see "BOOK="cncptenu" COLLECTION="nw41"Rights" and "BOOK="cncptenu" COLLECTION="nw41"Trustee" in Concepts and Chapter 2, "BOOK="superenu" COLLECTION="nw41"Managing Directories, Files, and Applications," and Chapter 3, "BOOK="superenu" COLLECTION="nw41"Creating Login Scripts," in Supervising the Network.PAGENUM=153 ID="BP160"RENDERAS="SECT1"ID="FM37645"Modify the STARTUP.NCF FileIDXID="w3141"BOOK="_idx" COLLECTION="nw41" TIDREF="i1289"IDXID="w3142"BOOK="_idx" COLLECTION="nw41" TIDREF="i4264"IDXID="w3143"BOOK="_idx" COLLECTION="nw41" TIDREF="i4264"IDXID="w3144"BOOK="_idx" COLLECTION="nw41" TIDREF="i4264"The STARTUP.NCF file resides on the boot disk partition, together with SERVER.EXE. It executes immediately after SERVER.EXE.The STARTUP.NCF file contains the commands to load the disk drivers you specified under "Load Disk Drivers." You can add other commands to this file or delete existing ones.A sample STARTUP.NCF file is shown below.LABEL="3-54" FLOAT="0"ID="FM68186"Sample STARTUP.NCF FileFILEREF="n41in97a.tif"Volume SYS: is automatically mounted when its corresponding disk driver is loaded during the STARTUP.NCF file's execution.PAGENUM=154 ID="BP161"The following table shows some of the commands you may want to add to the IDXID="w3145"BOOK="_idx" COLLECTION="nw41" TIDREF="i93"
STARTUP.NCF file.LABEL="3-6" PGWIDE=1 TOCENTRY="1"ID="FM57804" Syntax Examples for Assorted CommandsCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want to COLNAME=2 ROTATE="0" MOREROWS="0"Add these or other commandsVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w3146"BOOK="_idx" COLLECTION="nw41" TIDREF="i2152"
Load IDXID="w3147"BOOK="_idx" COLLECTION="nw41" TIDREF="i2589"
name spaces for Macintosh, OS/2, UNIX, or FTAMCOLNAME=2 ROTATE="0" MOREROWS="0"LOAD MAC.NAM  LOAD OS2.NAM  LOAD NFS.NAM  LOAD FTAM.NAMThese commands must precede the command to 
mount the volume that stores the files using the name space.COLNAME=1 ROTATE="0" MOREROWS="0"Set server IDXID="w3148"BOOK="_idx" COLLECTION="nw41" TIDREF="i3213"
parametersCOLNAME=2 ROTATE="0" MOREROWS="0"You can add the following six SET commands to the STARTUP.NCF file only. You can add other IDXID="w3149"BOOK="_idx" COLLECTION="nw41" TIDREF="i4090"
SET commands to either the STARTUP.NCF or the AUTOEXEC.NCF file.SET Maximum Physical Receive Packet Size  SET Auto Register Memory Above 16 Megabytes  SET Reserved Buffers Below 16 Meg  SET Maximum Subdirectory Tree Depth  SET Auto TTS Backout Flag  SET Minimum Packet Receive Buffer(For more information on these and other SET commands, see "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference or type "SET" at the server console.)COLNAME=1 ROTATE="0" MOREROWS="0"Pause after each commandCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w3150"BOOK="_idx" COLLECTION="nw41" TIDREF="i3257"
PAUSEPAGENUM=155 ID="BP162"RENDERAS="SECT2"ProcedureTo modify the STARTUP.NCF file, complete these steps.PERFORMANCE="REQUIRED"Type one command on each line.IDREF="FM57804"Table 3-6 on page 154 gives some syntax examples for assorted commands.PERFORMANCE="REQUIRED"To 
IDXID="w3151"BOOK="_idx" COLLECTION="nw41" TIDREF="i988"
delete or modify commands, simply backspace to erase the command.PERFORMANCE="REQUIRED"When you're finished modifying the file, press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"When asked whether you want to save the file, choose "Yes."If you make changes to this file, they take effect only when you reboot the server after the installation is finished.Once STARTUP.NCF loads disk drivers and any name spaces you add to it, control is passed 
IDXID="w3152"BOOK="_idx" COLLECTION="nw41" TIDREF="i1019"
to the AUTOEXEC.NCF file to complete the boot process.You can also add commands to the STARTUP.NCF file by loading INSTALL.NLM, or by using the SERVMAN server utility.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For more information onCOLNAME=2 ROTATE="0" MOREROWS="0"SeeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Editing the STARTUP.NCF file through INSTALL.NLMCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="superenu" COLLECTION="nw41"Creating or Editing a Server Batch (.NCF) File" in Chapter 7 of Supervising the Network.COLNAME=1 ROTATE="0" MOREROWS="0"Editing the STARTUP.NCF file using SERVMANCOLNAME=2 ROTATE="0" MOREROWS="0""BOOK="utlrfenu" COLLECTION="nw41"SERVMAN" in Utilities Reference.PERFORMANCE="REQUIRED"Continue with 
IDREF="FM86651""Modify the AUTOEXEC.NCF File," on page 156.
PAGENUM=156 ID="BP163"RENDERAS="SECT1"ID="FM86651"IDXID="w3153"BOOK="_idx" COLLECTION="nw41" TIDREF="i362"IDXID="w3154"BOOK="_idx" COLLECTION="nw41" TIDREF="i1289"IDXID="w3155"BOOK="_idx" COLLECTION="nw41" TIDREF="i2496"Modify the AUTOEXEC.NCF FileThe IDXID="w3156"BOOK="_idx" COLLECTION="nw41" TIDREF="i362"
AUTOEXEC.NCF IDXID="w3157"BOOK="_idx" COLLECTION="nw41" TIDREF="i362"
file is located in the SYS:SYSTEM directory. It runs after the server has mounted the system volume (volume SYS:). It provides the NetWare server with commands to complete the boot process after SERVER.EXE and STARTUP.NCF are executed. A sample AUTOEXEC.NCF file is shown below.LABEL="3-55" FLOAT="0"Sample AUTOEXEC.NCF FileFILEREF="n41in98a.tif"The AUTOEXEC.NCF file will display commands you specified earlier in the program. These include:MARK=BULLETIDXID="w3158"BOOK="_idx" COLLECTION="nw41" TIDREF="i4496"
Time zone SET commands (time server type, time zones, daylight saving time status and offset).IDXID="w3159"BOOK="_idx" COLLECTION="nw41" TIDREF="i460"IDXID="w3160"BOOK="_idx" COLLECTION="nw41" TIDREF="i813"
Bindery context (for bindery services, set automatically at this server's context).Users logging in, attaching, or mapping to a NetWare 4.1 server from a client running NETX rather than VLMs need to use the bindery context set in the server's AUTOEXEC.NCF file.Server name.IDXID="w3161"BOOK="_idx" COLLECTION="nw41" TIDREF="i1936"
IPX internal network number.PAGENUM=157 ID="BP164"All LOAD and BIND commands for LAN drivers, protocols, and frame types.ID="FM73839"The following table shows some of the commands you may want to add to the IDXID="w3162"BOOK="_idx" COLLECTION="nw41" TIDREF="i362"
AUTOEXEC.NCF file.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="14*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"Add these or other commandsVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Load other IDXID="w3163"BOOK="_idx" COLLECTION="nw41" TIDREF="i2755"
modules (NLMs) when the server bootsCOLNAME=2 ROTATE="0" MOREROWS="0"LOAD MONITOR  LOAD NLMnameCOLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w3164"BOOK="_idx" COLLECTION="nw41" TIDREF="i2516"
Mount volumesCOLNAME=2 ROTATE="0" MOREROWS="0"MOUNT volumename  MOUNT ALLNote: Volume SYS: is automatically mounted when its corresponding disk driver is loaded during the STARTUP.NCF file's execution.COLNAME=1 ROTATE="0" MOREROWS="0"Set IDXID="w3165"BOOK="_idx" COLLECTION="nw41" TIDREF="i3213"
server parameters, including time synchronization parametersCOLNAME=2 ROTATE="0" MOREROWS="0"For a complete list of all available IDXID="w3166"BOOK="_idx" COLLECTION="nw41" TIDREF="i4090"
SET commands, see "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.COLNAME=1 ROTATE="0" MOREROWS="0"Execute any other valid console commands during the boot processCOLNAME=2 ROTATE="0" MOREROWS="0"SECURE CONSOLE COLNAME=1 ROTATE="0" MOREROWS="0"Pause after a commandCOLNAME=2 ROTATE="0" MOREROWS="0"IDXID="w3167"BOOK="_idx" COLLECTION="nw41" TIDREF="i3257"
PAUSEIf you make changes to the AUTOEXEC.NCF file, they take effect only when you reboot the server after the installation is finished.  You can also add commands to the IDXID="w3168"BOOK="_idx" COLLECTION="nw41" TIDREF="i93"
AUTOEXEC.NCF by loading INSTALL.NLM at the server (see "BOOK="superenu" COLLECTION="nw41"Creating or Editing a Server Batch (.NCF) File" in Chapter 7 of Supervising the Network), or the SERVMAN server utility (see "BOOK="utlrfenu" COLLECTION="nw41"SERVMAN" in Utilities Reference).PAGENUM=158 ID="BP165"RENDERAS="SECT2"ProcedureTo modify the AUTOEXEC.NCF file, complete these steps.PERFORMANCE="REQUIRED"Press the Up-arrow key to edit the AUTOEXEC.NCF file.PERFORMANCE="REQUIRED"Verify the syntax for the command in 
Utilities Reference.PERFORMANCE="REQUIRED"To add commands, type one command on each line.PERFORMANCE="REQUIRED"To 
IDXID="w3169"BOOK="_idx" COLLECTION="nw41" TIDREF="i988"
delete or modify commands, simply backspace to erase the command.PERFORMANCE="REQUIRED"When you're finished modifying the file, press 
MOREINFO="NONE"<F10>.PERFORMANCE="REQUIRED"When asked whether you want to save this file, choose "Yes."The remaining NetWare files are copied to the server. This could take a few minutes.After these files are copied, the server installation is essentially complete. If you want, you can install additional items or products (seeIDREF="FM63004" "Perform Other Installation Options (Optional)," on page 160).PAGENUM=159 ID="BP166"LABEL="3-56" FLOAT="0"ID="FM15835"The Remaining NetWare Files Are Copied to the ServerFILEREF="n41in90a.tif"PERFORMANCE="REQUIRED"Continue with 
IDREF="FM63004""Perform Other Installation Options (Optional)," on page 160.
PAGENUM=160 ID="BP167"RENDERAS="SECT1"ID="FM63004"ID="FM53566"Perform Other Installation Options (Optional)The following screen appears listing other available installation options.LABEL="3-57" FLOAT="0"Other Installation OptionsFILEREF="n41in18a.tif"All of the options listed above can be performed at any time from the server by loading INSTALL.NLM at the server console.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If COLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"You want to perform any of the listed installation actions at this timeCOLNAME=2 ROTATE="0" MOREROWS="0"Follow the procedures under the headings that follow.COLNAME=1 ROTATE="0" MOREROWS="0"You want to install an optional product not listedCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "Install a Product Not Listed" from the "Other Installation Options" menu.Then follow the server prompts.COLNAME=1 ROTATE="0" MOREROWS="0"You do not want to perform any of the listed installation actions at this timeCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "Continue Installation" from the "Other Installation Actions" menu and press MOREINFO="NONE"<Enter>.After being prompted that the installation is complete, press <Enter> to get to the server console.Go to IDREF="FM87049""Where to Go from Here," on page 174.PAGENUM=162 ID="BP168"RENDERAS="SECT2"Create a IDXID="w3170"BOOK="_idx" COLLECTION="nw41" TIDREF="i3564"IDXID="w3171"BOOK="_idx" COLLECTION="nw41" TIDREF="i3726"
Registration DisketteHaving a CLASS=DISKRegistration diskette is useful in case you experience system problems in the future and must call Novell Technical SupportSM.The installation program can read information such as OS version, addresses, number of licensed connections, SFT level, amount of RAM installed, network board configuration, and disk drive configuration, and copy this information to the CLASS=DISKRegistration diskette.This might be useful in case you experience system problems in the future and need to call Novell Technical Support. Novell support technicians can access the above information, which greatly speeds up their ability to help you.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Other Installation Actions" menu, select "Choose an Item or Product Listed Above" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Choose "Create a Registration Diskette" and press MOREINFO="NONE"<Enter>.The screen that appears lists three prerequisites:
MARK=BULLETThe NetWare 4.1 CLASS=DISKRegistration disketteThe name and address of your Novell Authorized ResellerCLMYour company's reseller contact (the person in your company in responsible for purchases).PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to continue.PERFORMANCE="REQUIRED"In the "Reseller Information" form that appears, fill in the name and address of the Novell Authorized Reseller you purchased NetWare 4.1 from. PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Press
MOREINFO="NONE" <Enter> after each entry. PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to continue. PERFORMANCE="REQUIRED"In the "Customer Information" form, fill in the reseller contact's name and the name of your company (or organization).PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Press
MOREINFO="NONE" <Enter> after each entry. PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to continue. 
PAGENUM=163 ID="BP169"PERFORMANCE="REQUIRED"Insert the
IDXID="w3172"BOOK="_idx" COLLECTION="nw41" TIDREF="i843"
CLASS=DISKRegistration diskette into drive A: and press MOREINFO="NONE"<Enter>. The installation program now copies the 
IDXID="w3173"BOOK="_idx" COLLECTION="nw41" TIDREF="i1135"
registration information to this diskette.PERFORMANCE="REQUIRED"(Optional) Copy 
IDXID="w3174"BOOK="_idx" COLLECTION="nw41" TIDREF="i738"
configuration information to the 
CLASS=DISKRegistration diskette. PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F2> to view configuration information.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Esc> to exit the screen.PERFORMANCE="REQUIRED"ID="FM63044"When asked "Copy This Information to the Diskette?" choose "Yes" or "No" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Insert the 
CLASS=DISKRegistration diskette into the mailer labeled "Product Registration" and send it to Novell.PERFORMANCE="REQUIRED"Continue performing any additional installation options listed on 
IDREF="FM81287"pages 163 through 
IDREF="FM52631"173, or go to 
IDREF="FM37550""Exit the Installation Utility," on page 174.RENDERAS="SECT2"ID="FM81287"Upgrade 3.1x Print ServicesThis option allows system administrators upgrading their printer-supported NetWare IDXID="w3175"BOOK="_idx" COLLECTION="nw41" TIDREF="i4682"
3.1x server to NetWare 4.1, to upgrade print configuration files.For procedures on using this option see 
BOOK="upmigenu" COLLECTION="nw41"Upgrade.PAGENUM=164 ID="BP170"RENDERAS="SECT2"ID="FM42605"Create DOS/MS Windows/OS2 Client Install DiskettesIf you don't want to make IDXID="w3176"BOOK="_idx" COLLECTION="nw41" TIDREF="i646"IDXID="w3177"BOOK="_idx" COLLECTION="nw41" TIDREF="i1135"
client diskettes at this time, you can make them later from the server by loading INSTALL.NLM or from a workstation by running MAKEDISK.BAT. (See IDREF="FM56136"Appendix D, "Creating Client Diskettes," on page 293.)RENDERAS="SECT3"PrerequisitesFormat the appropriate number of high-density diskettes using the table below.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For COLNAME=2 ROTATE="0" MOREROWS="0"FormatVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"DOS/MS Windows workstationsCOLNAME=2 ROTATE="0" MOREROWS="0"Five 3.5-inch or 5.25 inch diskettesCOLNAME=1 ROTATE="0" MOREROWS="0"OS/2 workstationsCOLNAME=2 ROTATE="0" MOREROWS="0"Six 3.5-inch diskettesRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the "Other Installation Actions" menu, select "Choose an Item or Product Listed Above" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Choose "Create DOS/MS Windows/OS2 Client Install Diskettes" and press MOREINFO="NONE"<Enter>.The following menu appears.LABEL="3-58" FLOAT="0"Select the Client Files You Want to Copy to DisketteFILEREF="n41i115a.tif"PERFORMANCE="REQUIRED"Select or deselect the file groups you want copied by pressing MOREINFO="NONE"<Enter>. PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to accept the marked groups and continue.
PAGENUM=165 ID="BP171"PERFORMANCE="REQUIRED"Specify the destination that the client files will be copied to. By default, the client files are copied to drive A:. To specify a new path, press 
MOREINFO="NONE"<F3> and type the new path.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> to accept the path.PERFORMANCE="REQUIRED"Insert the labeled diskettes as prompted.PERFORMANCE="REQUIRED"Continue performing any additional installation options listed on 
IDREF="FM95097"pages 165 through 
IDREF="FM52631"173, or go to
IDREF="FM37550" "Exit the Installation Utility," on page 174.RENDERAS="SECT2"ID="FM95097"Create NetWare CLASS=DISKUpgrade/Migrate DiskettesThis option allows system administrators to create the diskettes necessary to IDXID="w3178"BOOK="_idx" COLLECTION="nw41" TIDREF="i4684"IDXID="w3179"BOOK="_idx" COLLECTION="nw41" TIDREF="i1135"
upgrade an existing NetWare 2.x, 3.x, or 4.x server to NetWare 4.1.For procedures on using this option, see 
BOOK="upmigenu" COLLECTION="nw41"Upgrade.PAGENUM=166 ID="BP172"RENDERAS="SECT2"ID="FM42624"Install NetWare for MacintoshThis option allows you to install NetWare for IDXID="w3180"BOOK="_idx" COLLECTION="nw41" TIDREF="i2743"IDXID="w3181"BOOK="_idx" COLLECTION="nw41" TIDREF="i1825"
Macintosh on the NetWare 4 server.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Other Installation Items/Products" menu, select "Choose an Item or Product Listed Above" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Choose "Install NetWare for Macintosh" and press MOREINFO="NONE"<Enter>.A screen appears, displaying the path that the NetWare for Macintosh files will be copied from.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IfCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"The path to the NetWare for Macintosh files is correctCOLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<Enter> to continue.COLNAME=1 ROTATE="0" MOREROWS="0"The path to the NetWare for Macintosh files is incorrectCOLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<F3> and specify a new directory path. When finished, press <Enter> to begin copying.For detailed information on installing and configuring NetWare for Macintosh, read the NetWare for Macintosh documentation listed in the following table.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ToCOLNAME=2 ROTATE="0" MOREROWS="0"ReadVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Install and configure NetWare for Macintosh on the serverCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="nwmfpenu" COLLECTION="nw41"NetWare for Macintosh File and Print Services.COLNAME=1 ROTATE="0" MOREROWS="0"Install and configure a NetWare for Macintosh clientCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="macclenu" COLLECTION="nw41"Using MacNDS Client for NetWare 4.PAGENUM=167 ID="BP173"To view these documents online on a Macintosh workstation, you must install and configure the online documentation reader on a standalone Macintosh workstation with a connected CD-ROM drive.For instructions, refer to the Macintosh section of 

BOOK="docinenu" COLLECTION="nw41"Installing and Using Online Documentation for NetWare 4.1.If you do not have a Macintosh workstation with a CD-ROM drive, view the manuals from an MS Windows workstation as described in 

BOOK="docinenu" COLLECTION="nw41"Installing and Using Novell Online Documentation for NetWare 4.1.PERFORMANCE="REQUIRED"Continue performing any additional installation options listed on 
IDREF="FM68222"pages 168 through 
IDREF="FM52631"173, or go to 
IDREF="FM37550""Exit the Installation Utility," on page 174.
PAGENUM=168 ID="BP174"RENDERAS="SECT2"ID="FM68222"Install NetWare MHS ServicesInstalling NetWare IDXID="w3182"BOOK="_idx" COLLECTION="nw41" TIDREF="i2767"IDXID="w3183"BOOK="_idx" COLLECTION="nw41" TIDREF="i1825"
MHS Services adds NetWare message handling service functionality to the NetWare 4 server. MHS allows users to communicate electronically across a network. Using MHS, users can exchange electronic mail, share calendars, schedule facilities, and perform many other activities.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Other Installation Items/Products" menu, select "Choose an Item or Product Listed Above" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Choose "Install NetWare MHS Services" and press MOREINFO="NONE"<Enter>.A screen appears, displaying the path that the NetWare MHS Services files will be copied from.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"IfCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"The path to the NetWare MHS Services files is correctCOLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<Enter> to continue.COLNAME=1 ROTATE="0" MOREROWS="0"The path to the NetWare MHS Services files is incorrectCOLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<F3> and specify a new directory path. When finished, press <Enter> to begin copying.PERFORMANCE="REQUIRED"Continue performing any additional installation options listed on 
IDREF="FM61994"pages 169 through 
IDREF="FM52631"173, or go to 
IDREF="FM37550""Exit the Installation Utility," on page 174.
PAGENUM=169 ID="BP175"RENDERAS="SECT2"ID="FM61994"Configure Network ProtocolsChoosing this option loads the INETCFG.NLM, which allows you to configure the IDXID="w3184"BOOK="_idx" COLLECTION="nw41" TIDREF="i756"IDXID="w3185"BOOK="_idx" COLLECTION="nw41" TIDREF="i3609"IDXID="w3186"BOOK="_idx" COLLECTION="nw41" TIDREF="i1795"
protocols you selected in IDREF="FM96317"Step 2 on page 92 as routing protocols.This means that the server will not only function as a NetWare 4.1 server, but will also route IPXTM, TCP/IP, and AppleTalk* packets to other network segments.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Other Installation Actions" menu, select "Choose an Item or Product Listed Above" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Choose "Configure Network Protocols" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Use the table below to find out which manual to refer to for configuring the protocol.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For ConfiguringCOLNAME=2 ROTATE="0" MOREROWS="0"SeeVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IPXCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="ipxrtenu" COLLECTION="nw41"NetWare IPX Router Reference.COLNAME=1 ROTATE="0" MOREROWS="0"TCP/IPCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="tcpipenu" COLLECTION="nw41"NetWare TCP/IP Reference.COLNAME=1 ROTATE="0" MOREROWS="0"AppleTalkCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="atrefenu" COLLECTION="nw41"NetWare AppleTalk Reference.PERFORMANCE="REQUIRED"Continue performing any additional installation options listed on 
IDREF="FM14923"pages 170 through 
IDREF="FM52631"173, or go to 
IDREF="FM37550""Exit the Installation Utility," on page 174.
PAGENUM=170 ID="BP176"RENDERAS="SECT2"ID="FM14923"Install an Additional Server LanguageThis IDXID="w3187"BOOK="_idx" COLLECTION="nw41" TIDREF="i2052"
option allows you to install message and help files for a selected language. Languages include English, French Italian, German, and Spanish. You can later change the server language to display the installed language files through the "Change Server Language" option.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Other Installation Actions" menu, select "Choose an Item or Product Listed Above" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Choose "Install an Additional Server Language" and press MOREINFO="NONE"<Enter>.A screen appears indicating the source path that you installed from. By default, the source path is the location of the NETMAIN.ILS file, a script file used to locate file sets.PERFORMANCE="REQUIRED"Accept the path by pressing MOREINFO="NONE"<Enter>, or press 
MOREINFO="NONE"<F3> and indicate a new path.The following screen appears.LABEL="3-59" FLOAT="0"Indicate Which File Groups You Want InstalledFILEREF="n41in42a.tif"PAGENUM=171 ID="BP177"PERFORMANCE="REQUIRED"Indicate the language files you want to copy by highlighting each group and pressing MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to accept the marked groups and continue.The selected file sets are then copied to volume SYS: To implement the newly installed files, see
IDREF="FM30572" "Change Server Language," on page 172.PERFORMANCE="REQUIRED"Continue performing any additional installation options listed on 
IDREF="FM30572"pages 172 through 
IDREF="FM52631"173, or go to 
IDREF="FM37550""Exit the Installation Utility," on page 174.
PAGENUM=172 ID="BP178"RENDERAS="SECT2"ID="FM30572"Change Server LanguageThis option allows you to IDXID="w3188"BOOK="_idx" COLLECTION="nw41" TIDREF="i2052"
change the server language to a language selected earlier through the "Install an Additional Server Language" option.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Other Installation Actions" menu, select "Choose an Item or Product Listed Above" and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Choose "Change Server Language" and press MOREINFO="NONE"<Enter>.A screen appears indicating the source path that you installed from. By default, the source path is the location of the NETMAIN.ILS file, a script file used to locate file sets.PERFORMANCE="REQUIRED"Accept the path by pressing MOREINFO="NONE"<Enter>, or press 
MOREINFO="NONE"<F3> and indicate a new path.The following screen appears.

FILEREF="n41in40a.tif"PERFORMANCE="REQUIRED"Choose the desired server language.This must be a language that you installed earlier through the "Install an Additional Server Language" option (seeIDREF="FM14923" "Install an Additional Server Language," on page 170).The files are copied to the server. To have the server invoke the new language, bring down the server and then bring it back up.PERFORMANCE="REQUIRED"Install the NetWare 4.1 online documentation to the server by reading 
IDREF="FM52631""Install Online Documentation on the Server," on page 173, or go to 
IDREF="FM37550""Exit the Installation Utility," on page 174.
PAGENUM=173 ID="BP179"RENDERAS="SECT2"ID="FM52631"Install Online Documentation on the ServerIDXID="w3189"BOOK="_idx" COLLECTION="nw41" TIDREF="i3074"IDXID="w3190"BOOK="_idx" COLLECTION="nw41" TIDREF="i1825"
This option installs the NetWare 4.1 IDXID="w3191"BOOK="_idx" COLLECTION="nw41" TIDREF="i3074"
online manual set and DynaText viewers on the NetWare 4.1 server. Entire NetWare 4.1 online manual sets are available in English, French, Italian, German, and Spanish.Be aware that a single language manual set requires 60 MB of free server disk space.For complete instruction on installing the online documentation and viewers, see BOOK="docinenu" COLLECTION="nw41"Installing and Using Novell Online Documentation for NetWare 4.1.PAGENUM=174 ID="BP180"RENDERAS="SECT1"ID="FM37550"Exit the Installation UtilityThe installation of the NetWare 4.1 server is now complete.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"To exit the installation utility and go to the server console, press MOREINFO="NONE"<Enter>. PERFORMANCE="REQUIRED"Continue with 
IDREF="FM87049""Where to Go from Here."RENDERAS="SECT1"ID="FM87049"Where to Go from HereCOLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Install additional NetWare 4.1 serversCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM43309""Install the Server Software," on page 66COLNAME=1 ROTATE="0" MOREROWS="0"Install NetWare clientsCOLNAME=2 ROTATE="0" MOREROWS="0"Chapter 6, IDREF="FM32801""Install NetWare Clients," on page 263COLNAME=1 ROTATE="0" MOREROWS="0"Install NetWare SFT IIICOLNAME=2 ROTATE="0" MOREROWS="0"Chapter 5, IDREF="FM38629""Install NetWare 4.1 SFT III," on page 237PAGENUM=175 ID="BP181"LABEL="3-60" FLOAT="0"IDXID="w3192"BOOK="_idx" COLLECTION="nw41" TIDREF="i4836"ID="FM65030"NetWare 4.1 Server WorksheetID="FM68531"FILEREF="n41in02a.tif"LABEL="4"PAGENUM=177 ID="BP182"ID="FM72388"Install NetWare Server for OS/2RENDERAS="SECT1"OverviewIDXID="w3193"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"The installation of NetWare Server for OS/2* consists of two parts: MARK=BULLETA graphical installation program that installs drivers and utility programs that allow NetWare 4TM to operate on an OS/2 computer. This chapter explains that installation.The NetWare installation program that installs NetWare 4.1. That installation is explained in Chapter 3, IDREF="FM44025""Custom Installation," on page 63.RENDERAS="SECT1"ID="FM58973"Necessary ResourcesRENDERAS="SECT2"Hardware RequirementsIDXID="w3194"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"IDXID="w3195"BOOK="_idx" COLLECTION="nw41" TIDREF="i1641"MARK=CHECKBOXA PC (or PC compatible) with a 386 or 486 processor. In a large network, the first NetWare Server for OS/2 you install should have a fast processor for more efficient NetWare Directory ServicesTM (NDS) synchronization.At least 16 MB of RAM (a minimum of 8 MB to be used by OS/2 and a minimum of 8 MB to be used by NetWare Server for OS/2). If you plan to install from a remote network installation area, you will need at minimum of 18 MB of RAM. The additional 2 MB of RAM are needed for CLIB.NLM and STREAMS.NLM.A hard disk with a minimum storage capacity of 150 MB. A minimum of 80 MB of that total must be partitioned as free space on the hard disk when OS/2 is installed (the OS/2 installation uses approximately 50 MB). The free space is used by NetWare Server for OS/2. PAGENUM=178 ID="BP183"Although these minimum requirements will allow you to install OS/2 and NetWare Server for OS/2, Novell® recommends that you install a larger hard disk to accommodate your storage needs.(Conditional) If you install the NetWare 4 online documentation on the server, another 60 MB of disk space is required.If you want to share a network board between NetWare ClientTM for OS/2 and NetWare Server for OS/2 (on the same computer), you need at least one network board. If you do not want to share a network board, you will need at least one network board for the client and one network board for the server.A CD-ROM drive (if installing from CD-ROM) with the corresponding OS/2 drivers.RENDERAS="SECT2"Software RequirementsIDXID="w3196"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"IDXID="w3197"BOOK="_idx" COLLECTION="nw41" TIDREF="i4201"MARK=CHECKBOXOS/2 version 2.1x or later.If installing from CD-ROM, the CLASS=DISKNetWare 4.1 Operating System CD-ROM and the NetWare 4 CLASS=DISKOnline Documentation CD-ROM.If installing from floppy diskettes, working copies of all the NetWare 4.1 diskettesCLASS=DISK.CLASS=DISKLicense diskette.(Conditional) If you are sharing a network board between NetWare Client for OS/2 and NetWare Server for OS/2, and the client software has not been installed, you will need the latest version of the client software.(Optional) Working copies of NetWare 4.1 compatible third-party disk drivers, LAN drivers, or NetWare Loadable ModulesTM (NLMsTM).PAGENUM=179 ID="BP184"RENDERAS="SECT1"Install Server SoftwareIDXID="w3198"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"For help during installation, select the "Help" menu, choose the "Help" buttons when boxes appear, or press MOREINFO="NONE"<F1>.To move back to a previous dialog box during installation, choose the "Cancel" button.RENDERAS="SECT2"PrerequisitesMARK=CHECKBOXMake sure you have the necessary hardware, software and memory requirements to install NetWare Server for OS/2 and NetWare 4.1. See IDREF="FM58973""Necessary Resources" on page 177.If your OS/2 computer will be used as a Netware Server for OS/2 and a NetWare Client for OS/2 sharing one network board, you need to install the client software before installing the server. (If you have not installed the client, the installation program will prompt you).Install at least one network board (if you are sharing the network board between the client and server) and cabling according to manufacturer instructions. Note the network board settings such as interrupt, I/O, DMA, etc. (You enter these settings during installation.)Install OS/2 version 2.1 (or later) on your computer and leave at least 80 MB of free disk space for NetWare. (80 MB is the absolute minimum needed to install NetWare. If you want to store files and applications on the server, you will need to leave more free space for NetWare.) If OS/2 is already installed on your computer, you may need to use the OS/2 FDISK utility to delete a current partition and create free disk space. For more information, see the OS/2 documentation about FDISK.  Using FDISK to create free space could destroy data on your hard disk. Be sure to back up files before using FDISK.PAGENUM=180 ID="BP185"RENDERAS="SECT2"Choose an Installation MediumYou can install NetWare Server for OS/2 either from CD-ROM, from floppy diskettes (available only through the NetWare Fulfillment Center), or from an existing NetWare server from a remote network installation area.There are advantages and disadvantages to each:MARK=BULLETRemote network. This is the fastest installation option. It requires that you have a CD-ROM mounted as a NetWare volume, or that you have another NetWare 4 server.CD-ROM. This option is not as fast as installing from the network, but is faster than installing from floppy diskettes. It requires a CD-ROM drive installed as an OS/2 device on the computer on which you want to install NetWare Server for OS/2.Floppy diskettes. This is the slowest option. It requires a 3.5-inch floppy disk drive.The following procedures explain how to install from each medium.PAGENUM=181 ID="BP186"RENDERAS="SECT1"Install from CD-ROMIDXID="w3199"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"IDXID="w3200"BOOK="_idx" COLLECTION="nw41" TIDREF="i603"Make sure you have installed a SCSI board in your OS/2 computer and have connected a CD-ROM drive to it. (See your CD-ROM documentation for information about installing the CD-ROM drive and the corresponding drivers.)RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Insert the CLASS=DISKNetWare 4.1 Operating System CD-ROM into the CD-ROM drive.PERFORMANCE="REQUIRED"Open an OS/2 window or full screen session.PERFORMANCE="REQUIRED"Change to the drive corresponding to the CD-ROM.If you are unsure which drive corresponds to the CD-ROM, choose the "OS/2 System" icon; then choose the "Drives" icon from the "OS/2 System Icon View" window.A list of OS/2 drives and their corresponding devices appears. The CD-ROM drive corresponds to the "CD-ROM" icon.PERFORMANCE="REQUIRED"Type
FORMAT="LINESPECIFIC"MOREINFO="NONE"INSTALL MOREINFO="NONE"<Enter>A dialog box similar to the one shown in 
IDREF="FM93369"Figure 4-1 will appear.LABEL="4-1" FLOAT="0"ID="FM93369"Choose a Language to InstallFILEREF="n41in73a.tif"PAGENUM=182 ID="BP187"PERFORMANCE="REQUIRED"Choose the language you want to install and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Go to 
IDREF="FM33172""Determine Which Installation Option to Use" on page 190.
PAGENUM=183 ID="BP188"RENDERAS="SECT1"Install from a Remote Network Installation AreaIDXID="w3201"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"IDXID="w3202"BOOK="_idx" COLLECTION="nw41" TIDREF="i3750"A NetWare 4.1 Server for OS/2 can be installed over the network from either a mounted CD-ROM NetWare volume or another NetWare 4 server.In either scenario, an OS/2 workstation running NetWare client software logs in to a remote area server and becomes a NetWare Server for OS/2 through the installation utility.Requirements and recommendations for a remote installation are outlined below.RENDERAS="SECT2"Requirements for a Network Installation AreaMARK=BULLETThe server with the CD-ROM image should not be RIP-filtered from the server being installed.The server being installed should use an IPX internal network number that is not RIP-filtered from the server with the CD-ROM image.When installing using the "Simplified NetWare Server for OS/2" option, a randomly generated IPX internal network number is chosen for you. If you need to enter a specific IPX internal network number, you should install using the "NetWare Server for OS/2" option.If you are installing from a NetWare 4 server, the NDS User object you log in as must be in the same container as the Server object.RENDERAS="SECT2"Recommendations for a Network Installation AreaMARK=BULLETFor better performance, the server with the CD-ROM image should have Packet BurstTM support. NetWare 3.12 and NetWare 4 servers have Packet Burst support built in. NetWare 3.11 requires PBURST.NLM for Packet Burst support.For better performance, the server with the CD-ROM image should have LIP (Large Internet Packet) support enabled. NetWare 3.12 and NetWare 4 servers have LIP support enabled by default (using the SET command "Allow LIP = On"). NetWare 3.11 requires LIPX.NLM for LIP support.PAGENUM=184 ID="BP189"RENDERAS="SECT2"Remote Installation AreasThe remote installation area can consist of one of the following:MARK=BULLETThe CLASS=DISKNetWare 4.1 Operating System CD-ROM mounted as a NetWare volume.The CLASS=DISKNetWare 4.1 Operating System CD-ROM files copied to a volume on a NetWare 4 server.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Install from the CLASS=DISKNetWare 4.1 Operating System CD-ROM mounted as a NetWare volumeCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM31273""Install from a CD-ROM Mounted as a NetWare Volume" on page 185COLNAME=1 ROTATE="0" MOREROWS="0"Install from the NetWare server volume containing copied CLASS=DISKNetWare 4.1 Operating System CD-ROM filesCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM63946""Install from a NetWare Volume with Files Copied on a Server" on page 188PAGENUM=185 ID="BP190"RENDERAS="SECT2"ID="FM31273"Install from a CD-ROM Mounted as a NetWare VolumeIDXID="w3203"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"IDXID="w3204"BOOK="_idx" COLLECTION="nw41" TIDREF="i603"RENDERAS="SECT3"Necessary ResourcesMARK=CHECKBOXA CD-ROM drive that can read ISO 9660 formatted CD-ROM disks.An existing NetWare 4.1 server. (This will be the host server.)An existing NetWare workstation. (This will be the new server you install.)RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Cable the CD-ROM drive to the NetWare 4 server. Since you are installing the CD-ROM as a NetWare volume, you do not need to install any drivers at this time.PERFORMANCE="REQUIRED"Insert the 
CLASS=DISKNetWare 4.1 Operating System CD-ROM into the CD-ROM drive.PERFORMANCE="REQUIRED"At the C:\NWSERVER directory, type 
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWOS2 MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"At the server console, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>The following menu appears.LABEL="4-2" FLOAT="0"The "Installation Options" MenuFILEREF="n41in16a.tif"PAGENUM=186 ID="BP191"PERFORMANCE="REQUIRED"Choose "Driver Options."The "Driver Options" menu appears.PERFORMANCE="REQUIRED"Choose "Configure Disk and Storage Device Drivers."The "Additional Driver Actions" menu appears.PERFORMANCE="REQUIRED"Choose "Select an Additional Driver."The "Select a Driver" list appears.PERFORMANCE="REQUIRED"Choose the necessary CD-ROM drivers according to the documentation that accompanied your CD-ROM drive.If the device drivers you need are not listed, press MOREINFO="NONE"<Ins> and follow the prompts to access a new list of drivers.  Load CDROMSHR.DSK if you want the CD-ROM drive to be shared by OS/2 and NetWare Server for OS/2. CDROMSHR.DSK allows NetWare to access CD-ROM devices operating under OS/2. CDROMSHR.DSK is the interface from NetWare to OS/2 and OS/2 is the interface to the CD-ROM drive.PERFORMANCE="REQUIRED"Once you have loaded all necessary drivers, from the "Additional Driver Actions" menu choose "Return to Previous Menu."PERFORMANCE="REQUIRED"ID="FM14101"Press 
MOREINFO="NONE"<Alt>+<F10> and choose "Yes" to exit INSTALL.NLM.You are returned to the server console.PERFORMANCE="REQUIRED"At the console prompt, type the following commands:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD NWPA MOREINFO="NONE"<Enter> 
LOAD CDROM MOREINFO="NONE"<Enter> 
CD MOUNT NW410 MOREINFO="NONE"<Enter> PERFORMANCE="REQUIRED"Go to the OS/2 workstation on which you want to load NetWare Server for OS/2 and log in to the host server with the mounted CD-ROM NetWare volume.PERFORMANCE="REQUIRED"Map a drive to the CD-ROM.PERFORMANCE="REQUIRED"On the CD-ROM drive, type 
PAGENUM=187 ID="BP192"FORMAT="LINESPECIFIC"MOREINFO="NONE"INSTALL MOREINFO="NONE"<Enter>A dialog box allowing you to choose the language you want to install appears (see 
IDREF="FM93369"Figure 4-1 on page 181).PERFORMANCE="REQUIRED"Choose the language you want to install and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Go to 
IDREF="FM33172""Determine Which Installation Option to Use" on page 190.
PAGENUM=188 ID="BP193"RENDERAS="SECT2"ID="FM63946"Install from a NetWare Volume with Files Copied on a ServerIDXID="w3205"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"RENDERAS="SECT3"Necessary ResourcesMARK=CHECKBOXAn existing NetWare server with sufficient disk space (at least 170 MB) to store the NetWare 4.1 operating system files. (This will be the host server.)An existing OS/2 workstation with the NetWare Client for OS/2 installed on it. (This will be the new NetWare Server for OS/2.)(Conditional) A CD-ROM drive that can read ISO 9660 formatted CD-ROMs.This is used to copy the NetWare 4.1 files from the CD-ROM to the host server.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Create a NETWARE directory on an existing server and copy the files from the installation medium to that directory.For example, to copy from CD-ROM drive D: to network drive K:, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"K: MOREINFO="NONE"<Enter>
MD NETWARE MOREINFO="NONE"<Enter> 
CD NETWARE MOREINFO="NONE"<Enter> 
NCOPY D: /S /E /V MOREINFO="NONE"<Enter> To copy from floppy diskettes, make subdirectories for each of the diskettes, type the following command for each floppy diskette:
FORMAT="LINESPECIFIC"MOREINFO="NONE"NCOPY A: /S /E /V MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Install NetWare Client for OS/2 on each computer you want to be a NetWare Server for OS/2.If the client software is not installed, you cannot connect to the host server. For instructions on installing client software, see 
IDREF="FM30513""Install NetWare Client for OS/2" on page 213.PERFORMANCE="REQUIRED"On every computer you want to make a NetWare Server for OS/2, map a drive to the network server directory that contains the NetWare 4.1 files.
PAGENUM=189 ID="BP194"PERFORMANCE="REQUIRED"Change to the drive corresponding to the server where you copied the installation files.PERFORMANCE="REQUIRED"Type
FORMAT="LINESPECIFIC"MOREINFO="NONE"INSTALL MOREINFO="NONE"<Enter>A dialog box allowing you to choose the language you want to install appears (see 
IDREF="FM93369"Figure 4-1 on page 181).PERFORMANCE="REQUIRED"Choose the language you want to install and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Go to 
IDREF="FM33172""Determine Which Installation Option to Use" on page 190.RENDERAS="SECT1"ID="FM10516"Install from Floppy DiskettesIDXID="w3206"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"IDXID="w3207"BOOK="_idx" COLLECTION="nw41" TIDREF="i1135"RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Open an OS/2 window or full screen session.PERFORMANCE="REQUIRED"Insert the 
CLASS=DISKInstall diskette into drive A:. PERFORMANCE="REQUIRED"Change to the floppy drive and type
FORMAT="LINESPECIFIC"MOREINFO="NONE"INSTALL MOREINFO="NONE"<Enter>A dialog box allowing you to choose the language you want to install appears (see 
IDREF="FM93369"Figure 4-1 on page 181).PERFORMANCE="REQUIRED"Choose the language you want to install and press MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Continue with the next section, 
IDREF="FM33172""Determine Which Installation Option to Use."PAGENUM=190 ID="BP195"RENDERAS="SECT1"ID="FM33172"Determine Which Installation Option to UseAfter you choose the language you want to install, the installation utility appears (see IDREF="FM94024"Figure 4-3).LABEL="4-3" FLOAT="0"ID="FM94024"NetWare for OS/2 Installation UtilityFILEREF="n41in51a.tif"This utility is used for installing NetWare Server for OS/2 and NetWare Client for OS/2.The main screen includes help information. For example, if NetWare Client for OS/2 is not running on your computer, a help message indicates possible reasons. The help message also indicates how to begin the installation.PAGENUM=191 ID="BP196"There are three options for installing. Use the table below to determine which option to use.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want toCOLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Install a new custom NetWare Server for OS/2COLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM54664""Install Using the NetWare Server for OS/2 Option" on page 196COLNAME=1 ROTATE="0" MOREROWS="0"Install a new simplified NetWare Server for OS/2 using defaults the system chooses for youCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM70845""Install Using Simplified NetWare Server for OS/2 Option" on page 192COLNAME=1 ROTATE="0" MOREROWS="0"Upgrade an existing NetWare Server for OS/2 to a newer versionCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM40320""Upgrade NetWare Server for OS/2" on page 220PAGENUM=192 ID="BP197"RENDERAS="SECT1"ID="FM70845"Install Using Simplified NetWare Server for OS/2 OptionIDXID="w3208"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"The "Simplified NetWare Server for OS/2" option is designed to make installation of NetWare Server for OS/2 easier. When you use this option, it makes certain assumptions about your setup that may or may or may not be acceptable.RENDERAS="SECT2"Assumptions Made by the Simplified OptionThe "Simplified NetWare Server for OS/2" option assumesMARK=CHECKBOXNetWare Server for OS/2 and NetWare Client for OS/2 are running on the same computer.NetWare Client for OS/2 and NetWare Server for OS/2 share a network board.Default selections for network board sharing.Only IPX/SPX communication protocols with TCP/IP support (no IBM* communication protocols) will be used on the network.Randomly generated IPX internal network numbers and other server information defaults are acceptable.The hard disk will not be mirrored or duplexed.One NetWare volume per disk.Automatic update of the CONFIG.SYS, NET.CFG, AUTOEXEC.NCF, and STARTUP.NCF files.A default NetWare Directory Services hierarchy. The Simplified Installation (in NetWare 4.1) assumes a single container for all objects.PAGENUM=193 ID="BP198"RENDERAS="SECT3"PrerequisitesMARK=CHECKBOXDetermine whether this computer will be aMARK=BULLETNetWare Server for OS/2 and NetWare Client for OS/2 sharing a network board.NetWare Server for OS/2 and NetWare Client for OS/2 using more than one network board for the server and client.NetWare Server for OS/2 only (using no client software).(Conditional) If you are sharing a network board, you must install NetWare Client for OS/2 before installing NetWare Server for OS/2.  For information on installing the client software, see IDREF="FM30513""Install NetWare Client for OS/2" on page 213.  For more detailed information about installing and configuring the client software, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the "Installation" pull-down menu, choose "Simplified NetWare Server for OS/2."The following dialog box appears.LABEL="4-4" FLOAT="0"ID="FM85929"NetWare Server for OS/2 InstallationFILEREF="n41in74a.tif"ID="FM28139"This dialog box allows you to verify the target directories where the server and driver files will be copied. The target directories are \NETWARE for driver files and \NWSERVER for server files on your OS/2 boot drive.
PAGENUM=194 ID="BP199"PERFORMANCE="REQUIRED"Choose "Copy" to copy the server and driver files to the target directories.The bar at the bottom of the installation utility indicates which files are being copied. After several minutes, an "Installation Message" appears indicating that the files have been copied.PERFORMANCE="REQUIRED"Choose "OK" to continue the installation.The "Server Information" dialog box appears (see 
IDREF="FM75080"Figure 4-5).LABEL="4-5" FLOAT="0"ID="FM75080"The "Server Information" Dialog BoxFILEREF="n41in85a.tif"PERFORMANCE="REQUIRED"Type the server name in the box provided and record the name for future reference.When the NetWare operating system (SERVER.EXE) loads, it reads this name.PERFORMANCE="REQUIRED"Choose "OK" to accept the server name.The installation utility main screen appears with a message indicating that you have completed the first part of the NetWare for OS/2 installation. The second part consists of installing NetWare 4.1.PERFORMANCE="REQUIRED"Exit the installation program by double-clicking on the small icon in the upper-left corner of the installation utility main screen.A message appears indicating that you need to reboot the computer so the changes made to the CONFIG.SYS and NET.CFG files will take effect.PERFORMANCE="REQUIRED"Choose "OK" to close the message.PERFORMANCE="REQUIRED"Use the OS/2 shutdown feature to reboot your computer. 
PAGENUM=195 ID="BP200"Click the right mouse button on the desktop and select "Shut Down" from the menu that appears.When the computer reboots, the second part of the installation (installing NetWare 4.1) starts automatically. PERFORMANCE="REQUIRED"Go to 
IDREF="FM86942""Choose the Server Drivers" on page 206.
PAGENUM=196 ID="BP201"RENDERAS="SECT1"ID="FM54664"Install Using the NetWare Server for OS/2 OptionIDXID="w3209"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"RENDERAS="SECT2"PrerequisitesMARK=CHECKBOXDetermine whether this computer will be aMARK=BULLETNetWare Server for OS/2 and NetWare Client for OS/2 sharing a network board.NetWare Server for OS/2 and NetWare Client for OS/2 using more than one network board for the server and client.NetWare Server for OS/2 only (no client software).(Conditional) If you are sharing a network board, you must install NetWare Client for OS/2 before installing NetWare Server for OS/2.  For information on installing the client software, see IDREF="FM30513""Install NetWare Client for OS/2" on page 213.  For more detailed information about installing and configuring the client software, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"From the "Installation" pull-down menu, choose "NetWare Server for OS/2."If NetWare Client for OS/2 is installed and running on your computer, the following dialog box appears.LABEL="4-6" FLOAT="0"ID="FM19906"Target Directories for Server FilesFILEREF="n41in74a.tif"PAGENUM=197 ID="BP202"This dialog box allows you to verify the target directories where the server and driver files will be copied. The target directories are \NETWARE for driver files and \NWSERVER for server files on your OS/2 boot drive.If NetWare Client for OS/2 is not installed, a message appears indicating that if you are sharing a network board, you must install the client software before installing NetWare Server for OS/2.  If you need to install the client software, choose "OK" and go to IDREF="FM30513""Install NetWare Client for OS/2" on page 213.PERFORMANCE="REQUIRED"Choose "Copy" to copy the server and driver files to the target directories.The bar at the bottom of the installation utility indicates which files are being copied. After several minutes, a message appears indicating that the files have been copied (see 
IDREF="FM65639"Figure 4-7).LABEL="4-7" FLOAT="0"ID="FM65639"System MessageFILEREF="n41in77a.tif"PERFORMANCE="REQUIRED"Choose "OK" to continue the installation.The following message appears (see 
IDREF="FM29925"Figure 4-8).LABEL="4-8" FLOAT="0"ID="FM29925"Sharing a Network Board Between the Client and ServerFILEREF="n41in83a.tif"PAGENUM=198 ID="BP203"Use the decision table below to determine how to answer the message.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If the client and serverCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Will share the same network board (the client and server are on the same computer)COLNAME=2 ROTATE="0" MOREROWS="0"Choose "Yes."The "Network Board Sharing Options" dialog box appears. Continue with the next section, IDREF="FM27637""Sharing a Network Board."COLNAME=1 ROTATE="0" MOREROWS="0"Will not share the same network board.COLNAME=2 ROTATE="0" MOREROWS="0"Choose "No."The "Save Changes to CONFIG.SYS" dialog box appears.Choose "OK" to save changes to the CONFIG.SYS file.Go to IDREF="FM59647""Enter Installation Information" on page 203RENDERAS="SECT2"ID="FM27637"Sharing a Network BoardIDXID="w3210"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"If you answered Yes to 
sharing a network board between the client and server, the "Network Board Sharing Options" dialog box appears (see IDREF="FM75864"Figure 4-9).LABEL="4-9" FLOAT="0"ID="FM75864"Network Board Sharing OptionsFILEREF="n41in75a.tif"PAGENUM=199 ID="BP204"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Select the options in the "Network Board Sharing Options" dialog box that apply to your NetWare Server for OS/2 setup.The "Additional NetWare Protocols" and "Token Ring, With or Without Other Topologies" options are selected as defaults.Use the decision box below to determine if you need to select options other than the defaults.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If your computer is sharing a network board usingCOLNAME=2 ROTATE="0" MOREROWS="0"ChooseVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Other NetWare protocols in addition to IPX/SPX (TCP/IP, AppleTalk*, etc.)COLNAME=2 ROTATE="0" MOREROWS="0""Additional NetWare Protocols" and "Token Ring With or Without Other Topologies."IDXID="w3211"BOOK="_idx" COLLECTION="nw41" TIDREF="i4521"IDXID="w3212"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"
TOKENSHR.LAN will be loaded for you in the NetWare 4.1 installation.Continue with IDREF="FM98643"Step 2below.COLNAME=1 ROTATE="0" MOREROWS="0"IBM communication protocolsCOLNAME=2 ROTATE="0" MOREROWS="0""IBM Communication Products that Use IBM Protocols" and "Token Ring With or Without Other Topologies."IDXID="w3213"BOOK="_idx" COLLECTION="nw41" TIDREF="i4519"IDXID="w3214"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"
TOKENLNK.LAN will be loaded for you in the NetWare 4.1 installation. This option requires that you are on a token ring network, that you have a token ring network board installed in your computer, and that you set up ODINSUP.Continue with IDREF="FM98643"Step 2below.COLNAME=1 ROTATE="0" MOREROWS="0"IPX/SPX protocols onlyCOLNAME=2 ROTATE="0" MOREROWS="0""IPX/SPX Communication Protocols" and "Ethernet or Other Non-Token Ring Topology."IDXID="w3215"BOOK="_idx" COLLECTION="nw41" TIDREF="i2055"IDXID="w3216"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"
LANSHARE.LAN will be loaded for you in the NetWare 4.1 installation.Continue with IDREF="FM98643"Step 2below.PERFORMANCE="REQUIRED"ID="FM98643"Choose "OK" to continue the installation.
PAGENUM=200 ID="BP205"The "Save Changes to CONFIG.SYS" dialog box appears.LABEL="4-10" FLOAT="0"Save Changes to CONFIG.SYSFILEREF="n41in84a.tif"Several lines are added to the CONFIG.SYS file based on the options you selected in the "Network Board Sharing Options" dialog box (in Step 1). This dialog box confirms the location of your CONFIG.SYS file. If you want to save the changes to another file, you can enter the path in this box. You would then need to update changes to the CONFIG.SYS file manually.PERFORMANCE="REQUIRED"ID="FM13529"Choose "OK" to save the changes to the CONFIG.SYS file.One of two different dialog boxes will appear depending on the choices you made in the "Network Board Sharing Options" dialog box (in Step 1).COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you choseCOLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0""IBM Communication Products that use IBM Protocols"COLNAME=2 ROTATE="0" MOREROWS="0"A message appears indicating that you need to set up ODINSUP.Choose "Yes" and continue with the next section, IDREF="FM16952""Set Up ODINSUP for Network Board Sharing."COLNAME=1 ROTATE="0" MOREROWS="0"Any other optionCOLNAME=2 ROTATE="0" MOREROWS="0"The "Enter Installation Information" box appears (see IDREF="FM64649"Figure 4-13Continue with IDREF="FM59647""Enter Installation Information" on page 203PAGENUM=201 ID="BP206"RENDERAS="SECT3"ID="FM16952"Set Up ODINSUP for Network Board SharingIDXID="w3217"BOOK="_idx" COLLECTION="nw41" TIDREF="i3060"IDXID="w3218"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"The "ODINSUP Configuration Files" box appears (see IDREF="FM32408"Figure 4-11).LABEL="4-11" FLOAT="0"ID="FM32408"ODINSUP Configuration FilesFILEREF="n41in80a.tif"OS/2 and IBM communication programs, such as Extended Services and LAN Services, use protocol drivers and network drivers written to the NDIS specification.NetWare Server for OS/2 and NetWare Client for OS/2 use protocol drivers and network drivers written to the ODITM (Open Data-link InterfaceTM) specification.The ODINSUP setup provides a way for NetWare products and IBM products to share a network board, by replacing the NDIS driver with a driver called ODINSUP.SYS.The "ODINSUP Configuration Files" dialog box displays the location of the PROTOCOL.INI, NET.CFG, and CONFIG.SYS files. These files are edited during ODINSUP setup.If the location of the configuration files as they appear in this box is incorrect, type the correct path in the box next to each filename.For more information about sharing network boards and setting up ODINSUP, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide and "BOOK="cncptenu" COLLECTION="nw41"ODINSUP" in Concepts.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"Choose "OK" to continue the installation.PAGENUM=202 ID="BP207"The following dialog box appears (see 
IDREF="FM90359"Figure 4-12).LABEL="4-12" FLOAT="0"ID="FM90359"ODINSUP Setup BoxFILEREF="n41in81a.tif"PERFORMANCE="REQUIRED"ID="FM74715"Select the NDIS driver and the ODI driver you want to replace it with from the lists in the "ODINSUP Setup Box."If you do not know which NDIS driver to select, check the documentation for the IBM program you are using.The "Replace NDIS" button is not active until a driver from each list is selected.PERFORMANCE="REQUIRED"ID="FM64287"Choose "Replace NDIS."The drivers you select are displayed in the "Current Configuration" field with a message indicating that the ODI driver is replacing the NDIS driver.If you select the wrong NDIS or ODI driver to be replaced, choose "Remove" to remove the selected drivers from the "Current Configuration" field.PAGENUM=203 ID="BP208"PERFORMANCE="REQUIRED"Repeat 
IDREF="FM74715"Step 2 and 
IDREF="FM64287"Step 3 for each NDIS driver you want replaced by an ODI driver.PERFORMANCE="REQUIRED"Choose "OK" to replace the NDIS drivers with the ODI drivers you selected.ODINSUP is set up and your NET.CFG, CONFIG.SYS, and PROTOCOL.INI files are edited for you.For more detailed information about setting up ODINSUP, and editing the NET.CFG and CONFIG.SYS files, see "BOOK="ws_osenu" COLLECTION="nw41"Using ODINSUP and LANSUP" in NetWare Client for OS/2 User Guide.PERFORMANCE="REQUIRED"Continue with the next section, 
IDREF="FM59647""Enter Installation Information."RENDERAS="SECT2"ID="FM59647"Enter Installation InformationThe "Enter Installation Information" box appears (see IDREF="FM64649"Figure 4-13 ).LABEL="4-13" FLOAT="0"ID="FM64649"Enter Installation InformationFILEREF="n41in82a.tif"PAGENUM=204 ID="BP209"To move among the fields in the "Enter Server Information" dialog box, press MOREINFO="NONE"<Tab> or use the mouse.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"In the "Server Name" field, type the server name in the box provided and record the name for future reference.When the NetWare operating system (SERVER.EXE) loads, it reads this server name.PERFORMANCE="REQUIRED"In the "IPX Internal Network Number" field, accept the randomly generated number, or assign a new IPX number to this server.The IPX internal network number is a logical network number that identifies an individual NetWare 4 server. Each server on a network must have a unique IPX internal network number.If your NetWare Server for OS/2 is on a small network, the randomly generated number is probably sufficient, because there is low probability that it will be repeated.Whether you accept the random number or enter your own, you should record the number for future reference.For more information about IPX internal network numbers, see "BOOK="cncptenu" COLLECTION="nw41"Network numbering" in Concepts. PERFORMANCE="REQUIRED"(Optional) Verify the country code, code page, and keyboard information for your server.For information on the country code, code page, or keyboard mapping, see your OS/2 manual.For a brief explanation, choose "Help" or press 
MOREINFO="NONE"<F1>.PERFORMANCE="REQUIRED"(Optional) Select a filename format.The "DOS Filename Format" is selected as a default and is recommended. This filename format limits you to using valid DOS filename characters according to the country code and code page selections.Limiting the server to valid DOS filename characters prevents workstations using NETX shells from creating files using nonstandard DOS filename characters.
PAGENUM=205 ID="BP210"Selecting "NetWare Filename Format" allows you to use NetWare-acceptable characters that may or may not be valid DOS characters.PERFORMANCE="REQUIRED"Choose "OK" to accept the settings in the "Enter Installation Information" box.The installation main screen appears again with a message indicating that you have completed the first part of the NetWare Server for OS/2 installation. The second part consists of installing NetWare 4.1.PERFORMANCE="REQUIRED"Exit the installation program by double-clicking on the small icon in the upper-left corner of the main screen.A message appears indicating that you should reboot the computer so the changes you made to the CONFIG.SYS and NET.CFG files will take effect.LABEL="4-14" FLOAT="0"Reboot the ComputerFILEREF="n41in28a.tif"PERFORMANCE="REQUIRED"Choose "OK."PERFORMANCE="REQUIRED"Use the OS/2 shutdown feature to reboot your computer. Click the right mouse button on the desktop and select "Shut Down" from the menu that appears.When the computer reboots, the second part of the installation (installing NetWare 4.1) will start automatically. PERFORMANCE="REQUIRED"Continue with the next section, 
IDREF="FM86942""Choose the Server Drivers."PAGENUM=206 ID="BP211"RENDERAS="SECT1"ID="FM86942"Choose the Server DriversAfter you reboot the computer, the server is brought up automatically and the NetWare 4.1 installation utility starts. A screen listing the available LAN drivers appears (see IDREF="FM74607"Figure 4-15).If this screen does not appear after rebooting, open an OS/2 Window or Full Screen and change to the \NWSERVER directory. Then typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NWINSTAL MOREINFO="NONE"<Enter>This will bring up the server and start the NetWare 4.1 installation program.RENDERAS="SECT2"Load a LAN DriverIDXID="w3219"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"When the NetWare 4.1 installation program starts, it scans for available disk and LAN drivers, and the following screen appears.LABEL="4-15" FLOAT="0"ID="FM74607"Available LAN DriversFILEREF="n41in30a.tif"PAGENUM=207 ID="BP212"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"ID="FM45018"Choose the driver corresponding to the network board installed in your computer.Use the Up- and Down-arrow keys to select the LAN driver. (The mouse does not function in the NetWare 4.1 installation program.)COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="14*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If COLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"The driver is listedCOLNAME=2 ROTATE="0" MOREROWS="0"Choose the appropriate LAN driver and press <Enter>. Continue with IDREF="FM34537"Step 2COLNAME=1 ROTATE="0" MOREROWS="0"The driver is not listedCOLNAME=2 ROTATE="0" MOREROWS="0"Press MOREINFO="NONE"<Ins> and follow the prompts. Continue with IDREF="FM34537"Step 2If you chose the TOKENLNK network board sharing option (see IDREF="FM27637""Sharing a Network Board" on page 198), you must have a token ring network board installed in your computer and you must load the token ring driver corresponding to it.  For a current list of network boards and drivers that work with TOKENLNK, see the README file included with the NetWare Server for OS/2 installation utility.A screen similar to the following appears (see 
IDREF="FM63841"Figure 4-16).
PAGENUM=208 ID="BP213"LABEL="4-16" FLOAT="0"ID="FM63841"Network Driver ParametersFILEREF="n41in31a.tif"PERFORMANCE="REQUIRED"ID="FM34537"Verify that the driver parameters match the settings on the network board in your computer.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If the default values COLNAME=2 ROTATE="0" MOREROWS="0"ThenVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Are correctCOLNAME=2 ROTATE="0" MOREROWS="0"Continue with IDREF="FM47021"Step 3COLNAME=1 ROTATE="0" MOREROWS="0"Are incomplete or conflict with other hardware settingsCOLNAME=2 ROTATE="0" MOREROWS="0"Choose "Select/Modify Driver Parameters" and enter the parameters.Press <F10> or <Esc> to exit the screen and save your changes.Continue with IDREF="FM47021"Step 3PAGENUM=209 ID="BP214"If you chose the TOKENLNK network board sharing option, random ring numbers have been selected for you. If you need to enter specific ring numbers for your network board, choose "Select/Modify Driver Parameters" and enter the ring numbers.PERFORMANCE="REQUIRED"ID="FM47021"Choose "Save Parameters and Load Driver" and press MOREINFO="NONE"<Enter>.A screen appears indicating that IPX will be bound to the driver you just selected.PERFORMANCE="REQUIRED"ID="FM52777"Press MOREINFO="NONE"<Enter> to continue.A screen appears asking if you want to select another network driver.PERFORMANCE="REQUIRED"Choose "No" and press MOREINFO="NONE"<Enter>.The following screen appears (see 
IDREF="FM94464"Figure 4-17).LABEL="4-17" FLOAT="0"ID="FM94464"Choose the Server DriversFILEREF="n41in86a.tif"PAGENUM=210 ID="BP215"This screen indicates that the LAN driver you have just selected is currently loaded. This screen also displays the default disk and LAN drivers that were chosen for you to be loaded.When the NetWare 4.1 installation utility started automatically, it scanned for available disk and LAN drivers (see 
IDREF="FM86942""Choose the Server Drivers" on page 206). DSKSHARE is always the default disk driver if your OS/2 and NetWare file systems share the same hard disk. 
IDXID="w3220"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"
DSKSHARE allows OS/2 and NetWare to use separate partitions on the same hard disk. DSKSHARE is the interface to OS/2, and OS/2 is the interface to the driver for the hard drive.If you install additional hard disks that are used only by NetWare, you will need to install additional NetWare disk drivers to handle those disks.The default LAN driver chosen for you varies depending on the choices you made for sharing a network board (see 
IDREF="FM27637""Sharing a Network Board" on page 198).For example, if you chose "IBM Communication Products that Use IBM Protocols," 
IDXID="w3221"BOOK="_idx" COLLECTION="nw41" TIDREF="i4519"IDXID="w3222"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"
TOKENLNK is the chosen default driver. If you chose "IPX/SPX Communication Protocols Only," 
IDXID="w3223"BOOK="_idx" COLLECTION="nw41" TIDREF="i2055"IDXID="w3224"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"
LANSHARE is the default driver. If you accepted the default choices, 
IDXID="w3225"BOOK="_idx" COLLECTION="nw41" TIDREF="i4521"IDXID="w3226"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"
TOKENSHR is the default driver.The default driver must be loaded in addition to the LAN driver you loaded corresponding to the network board in your computer. The default driver allows OS/2 and NetWare to share the same physical network board. The default driver is the interface from OS/2 to NetWare. The LAN driver you loaded in 
IDREF="FM45018"Step 1 is the interface from NetWare to the network board.PERFORMANCE="REQUIRED"Choose "Continue Installation."The "Bind LAN Driver to IPX" screen appears (see 
IDREF="FM14967"Figure 4-18).
PAGENUM=211 ID="BP216"LABEL="4-18" FLOAT="0"ID="FM14967"Bind LAN Driver to IPXFILEREF="n41in87a.tif"The LAN driver you selected corresponding to the network board in your computer has already been loaded and bound to IPX. The default LAN driver (LANSHARE or TOKENSHR) must also be bound to IPX. Use this screen to assign an IPX external network number to the driver. The IPX external network number assigned to this driver must be unique and cannot match the IPX external network number that is bound to the other LAN driver you loaded.You can accept the randomly generated IPX external network number or enter your own IPX external network number to be bound to the default driver.Record this IPX external number for future reference.For more information about the IPX external network number, see "
BOOK="cncptenu" COLLECTION="nw41"Network numbering" in 
Concepts.
PAGENUM=212 ID="BP217"If you are using the TOKENLNK network board sharing option, your token ring driver and TOKENLNK will not be bound to IPX. A message will appear indicating that the drivers have loaded successfully.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> to accept the IPX external network number and continue with the installation.PERFORMANCE="REQUIRED"Use the table below to determine where to go to continue the installation.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you installed theCOLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0""Simplified NetWare Server for OS/2" optionCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM15916""NetWare Partition Overview" on page 41(Located in IDREF="FM15916"Chapter 2 "Simple Installation."COLNAME=1 ROTATE="0" MOREROWS="0""NetWare Server for OS/2" optionCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM94272""Create NetWare Disk Partitions" on page 96(Located in IDREF="FM44025"Chapter 3 "Custom Installation."PAGENUM=213 ID="BP218"RENDERAS="SECT1"ID="FM30513"Install NetWare Client for OS/2IDXID="w3227"BOOK="_idx" COLLECTION="nw41" TIDREF="i1825"IDXID="w3228"BOOK="_idx" COLLECTION="nw41" TIDREF="i2711"If NetWare Client for OS/2 is not installed or is not currently running on your computer and you attempt to install NetWare Server for OS/2, the following message appears.LABEL="4-19" FLOAT="0"Share network boardFILEREF="n41in67a.tif"If you are sharing a network board between the client and server, you must install NetWare Client for OS/2.If you answer "Yes," a "Set Target Directory" dialog box appears (see IDREF="FM53760"Figure 4-20).LABEL="4-20" FLOAT="0"ID="FM53760"Set Target DirectoryFILEREF="n41in32a.tif"This dialog box allows you to verify the source drive that the client files will be copied from and the target directory that the files will be copied to.PAGENUM=214 ID="BP219"For example, if you are installing from CD-ROM, the source drive is the drive associated with the CD-ROM reader and the target directory is \NETWARE on your OS/2 boot drive (for example, D:\NETWARE).This section briefly explains how to install the client software. For a more detailed explanation, see 
BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Choose "OK" in the "Set Target Directory" dialog box to confirm where the client files will be copied to.The "Requester Installation" dialog box appears (see 
IDREF="FM50985"Figure 4-21).LABEL="4-21" FLOAT="0"ID="FM50985"Requester InstallationFILEREF="n41in68a.tif"The "Edit CONFIG.SYS and Copy All Files" option is selected as a default. You should use this default option if you are doing a complete client installation for the first time. For information about the other options in this dialog box, either press 
MOREINFO="NONE"<F1>, choose "Help," or refer to 

BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.PERFORMANCE="REQUIRED"Choose "OK" to copy the files to your target directory.The "Choose the ODI LAN Driver" dialog box appears.
PAGENUM=215 ID="BP220"LABEL="4-22" FLOAT="0"Choose the ODI LAN DriverFILEREF="n41in33a.tif"PERFORMANCE="REQUIRED"Choose the LAN driver for your computer.You can type the name of the driver in the "Choose the ODI LAN Driver" dialog box or click on the scroll arrow and select the driver from the list.If you are installing NetWare Client for OS/2 from floppy diskettes, you will be prompted to insert the CLASS=DISKWSDRV_1 diskette.PERFORMANCE="REQUIRED"Choose "Continue."The "Choose NetWare Support for DOS and Windows Applications" dialog box appears (see 
IDREF="FM88534"Figure 4-23).LABEL="4-23" FLOAT="0"ID="FM88534"Choose NetWare Support for DOS and Windows ApplicationsFILEREF="n41in69a.tif"PERFORMANCE="REQUIRED"ID="FM69471"Turn on "IPX Support for DOS and Windows" and select one of the "Default NetWare Shell Support" options.
PAGENUM=216 ID="BP221"If "IPX Support for DOS and Windows" is turned off, you cannot access the NetWare network from DOS or MS Windows sessions. For more information about the other options in this dialog box, either press 
MOREINFO="NONE"<F1>, choose "Help," or refer to 

BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.PERFORMANCE="REQUIRED"Choose "Continue" to accept the options you selected.The "Save Changes to AUTOEXEC.BAT" dialog box appears (see 
IDREF="FM91228"Figure 4-24).LABEL="4-24" FLOAT="0"ID="FM91228"Save Changes to AUTOEXEC.BATFILEREF="n41in70a.tif"ID="FM96307"If you selected "Private or Global NetWare Support" (in 
IDREF="FM69471"Step 5), make sure that "NETX.EXE" is selected. This causes NETX.EXE to be loaded automatically when you start a DOS or MS Windows session.If you selected IPX/SPX support, you need to select "TBMI2.COM" if you are using any MS Windows applications that use TBMI2 to directly access the network (some E-mail packages may require TBMI2). PERFORMANCE="REQUIRED"Choose "Save" to save the changes to the AUTOEXEC.BAT file and continue with the installation.
PAGENUM=217 ID="BP222"A message appears asking if you want to add NETX.EXE and TBMI2.COM commands to another batch file.LABEL="4-25" FLOAT="0"Installation MessageFILEREF="n41in34a.tif"PERFORMANCE="REQUIRED"Choose "No" to continue with the installation. For more information about adding NETX.EXE and TBMI2.COM to another batch file, see 

BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.A message appears (see 
IDREF="FM99806"Figure 4-26) indicating that you need to set "DOS_LASTDRIVE=" to the last drive of your hard disk in the "DOS Window Settings" and "DOS Full Screen Settings" dialog boxes. (For example, if you have partitioned drives C:, D:, and E: on your hard disk, you would set DOS_LASTDRIVE=E).LABEL="4-26" FLOAT="0"ID="FM99806"Set DOS LASTDRIVEFILEREF="n41in35a.tif"For more information about entering settings for DOS sessions, see your OS/2 manual.PERFORMANCE="REQUIRED"Choose "OK" to continue with the installation.The "Choose Optional Protocols" dialog box appears (see 
IDREF="FM15758"Figure 4-27).
PAGENUM=218 ID="BP223"LABEL="4-27" FLOAT="0"ID="FM15758"Choose Optional ProtocolsFILEREF="n41in71a.tif"PERFORMANCE="REQUIRED"Choose the protocol support you want, then choose "Save."For more information about protocol support, either press <F1>, choose "Help," or refer to 

BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User Guide.The "Save Changes to CONFIG.SYS" dialog box appears.LABEL="4-28" FLOAT="0"Save Changes to CONFIG.SYSFILEREF="n41in84a.tif"This dialog box displays the current location of your CONFIG.SYS file.PERFORMANCE="REQUIRED"Choose "OK."The "Copy ODI LAN Driver Files" dialog box appears (see 
IDREF="FM83899"Figure 4-29).
PAGENUM=219 ID="BP224"LABEL="4-29" FLOAT="0"ID="FM83899"Copy ODI LAN Driver filesFILEREF="n41in72a.tif"The option "Copy Only the Default Driver" is selected as a default. If you want to copy all available ODI drivers to your client directory, choose "Copy All the Drivers on the Disk."PERFORMANCE="REQUIRED"Choose "OK" to copy the driver files.The driver files are copied to the target directory. The "Copy Requester Files" dialog box appears.LABEL="4-30" FLOAT="0"Copy Requester FilesFILEREF="n41in39a.tif"PERFORMANCE="REQUIRED"Choose "Copy" to copy the client files to the target directory shown in the "Copy Requester Files" box.PERFORMANCE="REQUIRED"Follow the screen prompts to complete the NetWare Client for OS/2 installation.PERFORMANCE="REQUIRED"Go to 
IDREF="FM54664""Install Using the NetWare Server for OS/2 Option" on page 196.
PAGENUM=220 ID="BP225"RENDERAS="SECT1"ID="FM40320"Upgrade NetWare Server for OS/2IDXID="w3229"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"IDXID="w3230"BOOK="_idx" COLLECTION="nw41" TIDREF="i4688"Use this installation option if you are upgrading from a NetWare 4.01 or 4.02 Server for OS/2 to a NetWare 4.1 Server for OS/2.You can upgrade NetWare Server for OS/2 from CD-ROM, or from a remote server installation area that has the updated NetWare filed copied onto it.RENDERAS="SECT2"Upgrade from CD-ROMRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED" Change to the CD-ROM drive and typeFORMAT="LINESPECIFIC"MOREINFO="NONE"INSTALL MOREINFO="NONE"<Enter>The installation utility appears.You do not need to down the server. PERFORMANCE="REQUIRED"From the "Installation" pull-down menu, choose "Upgrade NetWare Server for OS/2."The "NetWare Server for OS/2 Installation" dialog box appears (see 
IDREF="FM15334"Figure 4-31).LABEL="4-31" FLOAT="0"ID="FM15334"NetWare Server for OS/2 InstallationFILEREF="n41in74a.tif"PAGENUM=221 ID="BP226"This dialog box allows you to verify the target directories that the server and driver files will be copied to. For example, the target directories are \NETWARE for driver files and \NWSERVER for server files on your OS/2 boot drive.If you want to copy the files into directories other than the ones indicated, you can change the path and target directories in the boxes provided. However, the driver files must be copied to the same directory that contains NetWare Client for OS/2 (the \NETWARE directory).PERFORMANCE="REQUIRED"Choose "Copy" to copy the server and driver files to the target directories.The bar at the bottom of the installation utility indicates which files are being copied. After the files are copied, a "Drivers Not Updated" box similar to 
IDREF="FM23114"Figure 4-32 may appear.LABEL="4-32" FLOAT="0"ID="FM23114"List of Drivers Not UpgradedFILEREF="n41in88a.tif"This is a list of drivers found in the destination path that were not updated. These drivers may or may not work with the updated version.PERFORMANCE="REQUIRED"Choose "OK" to continue the installation.PERFORMANCE="REQUIRED"Exit the installation utility by double-clicking on the small icon in the upper-left corner of the main screen.
PAGENUM=222 ID="BP227"A message appears indicating that you should reboot the computer so the changes you made to the CONFIG.SYS and NET.CFG files will take effect.LABEL="4-33" FLOAT="0"Reboot Your ComputerFILEREF="n41in28a.tif"PERFORMANCE="REQUIRED"Choose "OK."PERFORMANCE="REQUIRED"Down the server.PERFORMANCE="REQUIRED"Use the OS/2 shutdown feature to reboot your computer. Click the right mouse button on the desktop and select "Shut Down" from the menu that appears.When the computer reboots, the second part of the installation (installing NetWare 4.1) will start automatically.PERFORMANCE="REQUIRED"Go to 
IDREF="FM86942""Choose the Server Drivers" on page 206.RENDERAS="SECT2"Upgrade from a Remote Server Installation AreaRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Open an OS/2 window or full screen session.PERFORMANCE="REQUIRED"ID="FM32883"Map a drive to the server that has a copy of the NetWare 4.1 installation files.PERFORMANCE="REQUIRED"Change to the drive you mapped in 
IDREF="FM32883"Step 2.PERFORMANCE="REQUIRED"Change to the 4.10 subdirectory and type
FORMAT="LINESPECIFIC"MOREINFO="NONE"INSTALL MOREINFO="NONE"<Enter>
PAGENUM=223 ID="BP228"The installation utility appears.PERFORMANCE="REQUIRED"From the "Installation" pull-down menu, choose "Upgrade NetWare Server for OS/2."The "NetWare Server for OS/2 Installation" dialog box appears (see 
Figure 4-34).LABEL="4-34" FLOAT="0"NetWare Server for OS/2 InstallationFILEREF="n41in74a.tif"This dialog box allows you to verify the target directories that the server and driver files will be copied to. For example, the target directories are \NETWARE for driver files and \NWSERVER for server files on your OS/2 boot drive.If you want to copy the files into directories other than the ones indicated, you can change the path and target directories in the boxes provided. However, the driver files must be copied to the same directory that contains NetWare Client for OS/2 (the \NETWARE directory).PERFORMANCE="REQUIRED"Choose "Copy" to copy the server and driver files to the target directories.The bar at the bottom of the installation utility indicates which files are being copied. After the files are copied, a "Drivers Not Updated" box similar to 
Figure 4-35 may appear.
PAGENUM=224 ID="BP229"LABEL="4-35" FLOAT="0"List of Drivers Not UpgradedFILEREF="n41in88a.tif"This is a list of drivers found in the destination path that were not updated. These drivers may or may not work with the updated version.PERFORMANCE="REQUIRED"Choose "OK" to continue the installation.PERFORMANCE="REQUIRED"Exit the installation utility by double-clicking on the small icon in the upper-left corner of the main screen.A message appears indicating that you should reboot the computer.LABEL="4-36" FLOAT="0"Reboot Your ComputerFILEREF="n41in28a.tif"PERFORMANCE="REQUIRED"Choose "OK."PERFORMANCE="REQUIRED"Down the server.PERFORMANCE="REQUIRED"Use the OS/2 shutdown feature to reboot your computer. 
PAGENUM=225 ID="BP230"Click the right mouse button on the desktop and select "Shut Down" from the menu that appears.When the computer reboots, the second part of the installation (installing NetWare 4.1) will start automatically.PERFORMANCE="REQUIRED"Go to 
IDREF="FM86942""Choose the Server Drivers" on page 206.
PAGENUM=226 ID="BP231"RENDERAS="SECT1"Changing Network Board Sharing ConfigurationsIDXID="w3231"BOOK="_idx" COLLECTION="nw41" TIDREF="i2791"This section explains how to load and unload drivers for different network board sharing configurations after the server has been installed.RENDERAS="SECT2"Changing from TOKENSHR to TOKENLNKRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the NetWare Server for OS/2 console, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>The "Installation Options" menu appears (see 
IDREF="FM20801"Figure 4-37).LABEL="4-37" FLOAT="0"ID="FM20801"Installation OptionsFILEREF="n41i109a.tif"PERFORMANCE="REQUIRED"Choose "Driver Options."The "Driver Options" menu appears (see 
IDREF="FM96636"Figure 4-38).
PAGENUM=227 ID="BP232"LABEL="4-38" FLOAT="0"ID="FM96636"Driver OptionsFILEREF="n41i108a.tif"PERFORMANCE="REQUIRED"Choose "Configure Network Drivers."The "Additional Driver Actions" menu appears (see 
IDREF="FM11952"Figure 4-39).
PAGENUM=228 ID="BP233"LABEL="4-39" FLOAT="0"ID="FM11952"Additional Driver ActionsFILEREF="n41i107a.tif"ID="FM11537"PERFORMANCE="REQUIRED"Choose "Deselect a Selected Driver."PERFORMANCE="REQUIRED"Choose "TOKENSHR" from the "Selected Network Drivers" field.Use the Up- and Down-arrow keys to select the driver.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> to unload the selected driver.A message appears indicating that the selected driver has been successfully unloaded.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> to continue.PERFORMANCE="REQUIRED"Choose "Select an Additional Driver" from the "Additional Driver Actions" menu.
PAGENUM=229 ID="BP234"A list of available drivers appears (see 
IDREF="FM59424"Figure 4-40).LABEL="4-40" FLOAT="0"ID="FM59424"List of Available DriversFILEREF="n41in30a.tif"PERFORMANCE="REQUIRED"Select TOKENLNK.LAN from the list of available drivers.A screen appears allowing you to verify the ring numbers for the selected driver.PERFORMANCE="REQUIRED"Choose "Save Parameters" and load driver and press MOREINFO="NONE"<Enter>.A message appears indicating that the driver has been successfully loaded.
ID="FM37632"A message appears asking if you want to select an additional network driver.PERFORMANCE="REQUIRED"Choose "No" and press MOREINFO="NONE"<Enter>.The "Additional Driver Actions" menu appears again.PERFORMANCE="REQUIRED"Choose "Return to the Previous Menu."
PAGENUM=230 ID="BP235"The "Driver Options" menu appears.PERFORMANCE="REQUIRED"Choose "Return to Previous Menu."The "Installation Options" menu appears.PERFORMANCE="REQUIRED"Choose "Exit" to exit the installation utility.PERFORMANCE="REQUIRED"Bring down the server and reboot your computer so that the changes will take effect.RENDERAS="SECT2"Changing from TOKENLNK to TOKENSHRRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the NetWare Server for OS/2 console, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>The "Installation Options" menu appears (see 
IDREF="FM20801"Figure 4-37).PERFORMANCE="REQUIRED"Choose "Driver Options."The "Driver Options" menu appears (see 
IDREF="FM96636"Figure 4-38).PERFORMANCE="REQUIRED"Choose "Configure Network Drivers."The "Additional Driver Actions" menu appears (see 
IDREF="FM11952"Figure 4-39).PERFORMANCE="REQUIRED"Choose "Deselect a Selected Driver."PERFORMANCE="REQUIRED"Choose "SRBRIDGE" from the "Selected Network Drivers" field.SRBRIDGE is the multiple protocol source routing bridge driver used with TOKENLNK.LAN. Use the Up- and Down-arrow keys to select the driver.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> to unload the selected driver.A message appears indicating that the selected driver has been successfully unloaded.PERFORMANCE="REQUIRED"Press MOREINFO="NONE"<Enter> to continue.PERFORMANCE="REQUIRED"ID="FM88604"Unload each token ring driver bound to SRBRIDGE.LAN.
PAGENUM=231 ID="BP236"Choose "Deselect a Selected Driver" from the "Additional Driver Actions" menu for each token ring driver.The drivers need to be unloaded because they are bound to SRBRIDGE.LAN. (Because SRBRIDGE.LAN is unloaded, the drivers have nothing to be bound to.)PERFORMANCE="REQUIRED"Choose "Select an Additional Driver" from the "Additional Driver Actions" menu.A list of available drivers appears.PERFORMANCE="REQUIRED"Select each token ring driver that you unloaded in 
IDREF="FM88604"Step 8.The drivers need to be reloaded so they can be bound to IPX and TOKENSHR.LAN.A screen appears allowing you to verify the parameters for the selected driver.PERFORMANCE="REQUIRED"Choose "Save Parameters and Load Driver" and press MOREINFO="NONE"<Enter>.A screen appears allowing you to bind the driver to IPX.PERFORMANCE="REQUIRED"Enter an IPX external network number for each token ring driver, or press MOREINFO="NONE"<Enter> to accept the randomly generated IPX external network number.For more information about the IPX external network number,
see "BOOK="cncptenu" COLLECTION="nw41"Network numbering" in 
Concepts.A message appears asking if you want to select an additional network driver.PERFORMANCE="REQUIRED"Choose "Yes" to select an additional network driver.PERFORMANCE="REQUIRED"Select TOKENSHR.LAN from the list of available drivers.The "Parameter Actions" menu appears.PERFORMANCE="REQUIRED"Choose "Save Parameters and Load Driver."PERFORMANCE="REQUIRED"Enter an IPX external network number, or press 
MOREINFO="NONE"<Enter> to accept the randomly generated IPX external network number.A message appears asking if you want to select an additional network driver.
PAGENUM=232 ID="BP237"PERFORMANCE="REQUIRED"Choose "No."The "Additional Driver Actions" menu appears again.PERFORMANCE="REQUIRED"Choose "Return to the Previous Menu."The "Driver Options" menu appears.PERFORMANCE="REQUIRED"Choose "Return to Previous Menu."The "Installation Options" menu appears.PERFORMANCE="REQUIRED"Choose "Exit" to exit INSTALL.PERFORMANCE="REQUIRED"Bring down the server and reboot your computer so that the changes will take effect.RENDERAS="SECT2"Changing from LANSHARE to TOKENSHR or TOKENLNKRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Open the NET.CFG file in an OS/2 text editor by typing the following in an OS/2 window:FORMAT="LINESPECIFIC"MOREINFO="NONE"EPM NET.CFG MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Add the following lines to the NET.CFG file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LINK DRIVER drivername 
   NODE ADDRESS 
address Replace 
drivername with TOKENSHR or TOKENLNK, depending on the network board sharing option you are using. Replace 
address with a 12-byte node address.PERFORMANCE="REQUIRED"Open the CONFIG.SYS file in an OS/2 text editor.Replace the following line:
FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=drive:\NETWARE\LANSHARE.SYSwith the following two lines:
FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=drive:\NETWARE\drivername.SYS 
PAGENUM=233 ID="BP238"DEVICE=
drive:\NETWARE\ROUTE.SYS Replace 
drive with the letter of the drive where the \NETWARE directory is located. Replace 
drivername with TOKENSHR or TOKENLNK, depending on the network board sharing option you are using.PERFORMANCE="REQUIRED"Start NetWare Server for OS/2.You can start the server by double-clicking on the NetWare Server for OS/2 icon, or by changing to the \NWSERVER directory in an OS/2 window and typing 
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWOS2 MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"At the NetWare Server for OS/2 console prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>The "Installation Options" screen appears (see 
IDREF="FM20801"Figure 4-37).PERFORMANCE="REQUIRED"Choose "Driver Options."The "Driver Options" menu appears (see 
IDREF="FM96636"Figure 4-38).PERFORMANCE="REQUIRED"Choose "Configure Network Drivers."The "Additional Driver Actions" menu appears (see 
IDREF="FM11952"Figure 4-39).PERFORMANCE="REQUIRED"Choose "Deselect a Selected Driver."PERFORMANCE="REQUIRED"Choose "LANSHARE" from the "Selected Network Drivers" field.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to unload the selected driver.A message appears indicating that the selected driver has been successfully unloaded.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to continue.PERFORMANCE="REQUIRED"Choose "Select an Additional Driver" from the "Additional Driver Actions" menu.A list of available LAN drivers appears.
PAGENUM=234 ID="BP239"PERFORMANCE="REQUIRED"Select "TOKENSHR.LAN" or "TOKENLNK.LAN," depending on the network board sharing option you are using.The "Parameters Actions" menu appears.PERFORMANCE="REQUIRED"Choose "Save Parameters and Load Driver."PERFORMANCE="REQUIRED"Enter an IPX external network number, or press 
MOREINFO="NONE"<Enter> to accept the randomly generated IPX external network number.A message appears asking if you want to select an additional network driver.PERFORMANCE="REQUIRED"Choose "No."The "Additional Driver Actions" menu appears again.PERFORMANCE="REQUIRED"Choose "Return to the Previous Menu."The "Installation Options" menu appears.PERFORMANCE="REQUIRED"Choose "Exit" to exit INSTALL.PERFORMANCE="REQUIRED"Bring down the server and reboot your computer so that the changes will take effect.RENDERAS="SECT2"Changing from TOKENSHR or TOKENLNK to LANSHARERENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Open the CONFIG.SYS file in an OS/2 text editor by typing the following in an OS/2 windowFORMAT="LINESPECIFIC"MOREINFO="NONE"EPM CONFIG.SYS MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Delete the following two lines from the CONFIG.SYS file.
FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=drive:\NETWARE\drivername.SYS 
DEVICE=
drive:\NETWARE\ROUTE.SYS Replace 
drive with the letter of the drive where the \NETWARE directory is located. Replace 
drivername with TOKENSHR or TOKENLNK, depending on the network board sharing option you are using.
PAGENUM=235 ID="BP240"PERFORMANCE="REQUIRED"Add the following line to the CONFIG.SYS file.
FORMAT="LINESPECIFIC"MOREINFO="NONE"DEVICE=drive:\NETWARE\LANSHARE.SYSReplace 
drive with the letter of the drive where the \NETWARE directory is located.PERFORMANCE="REQUIRED"Start NetWare Server for OS/2.You can start the server by double-clicking on the NetWare Server for OS/2 icon, or by changing to the \NWSERVER directory in an OS/2 window and typing 
FORMAT="LINESPECIFIC"MOREINFO="NONE"NWOS2 MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"At the NetWare Server for OS/2 console prompt, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>The "Installation Options" screen appears (see 
IDREF="FM20801"Figure 4-37).PERFORMANCE="REQUIRED"Choose "Driver Options."The "Driver Options" menu appears (see 
IDREF="FM96636"Figure 4-38).PERFORMANCE="REQUIRED"Choose "Configure Network Drivers."The "Additional Driver Actions" menu appears (see 
IDREF="FM11952"Figure 4-39).PERFORMANCE="REQUIRED"Choose "Deselect a Selected Driver."PERFORMANCE="REQUIRED"Choose "TOKENSHR" or "SRBRIDGE," depending on the network board sharing option you are using.SRBRIDGE is the multiple protocol source routing bridge driver used with TOKENLNK.LAN.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to unload the selected driver.A message appears indicating that the selected driver has been successfully unloaded.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to continue.PERFORMANCE="REQUIRED"Choose "Select an Additional Driver" from the "Additional Driver Actions" menu.
PAGENUM=236 ID="BP241"A list of available LAN drivers appears.PERFORMANCE="REQUIRED"Choose "LANSHARE" from the list of available drivers.The "Parameters Actions" menu appears.PERFORMANCE="REQUIRED"Choose "Save Parameters and Load Driver."PERFORMANCE="REQUIRED"Enter an IPX external network number, or press 
MOREINFO="NONE"<Enter> to accept the randomly generated IPX external network number.A message appears asking if you want to select an additional network driver.PERFORMANCE="REQUIRED"Choose "No."The "Additional Driver Actions" menu appears again.PERFORMANCE="REQUIRED"Choose "Return to Previous Menu."The "Installation Options" menu appears.PERFORMANCE="REQUIRED"Choose "Exit" to exit INSTALL.PERFORMANCE="REQUIRED"Bring down the server and reboot your computer so that the changes will take effect.LABEL="5"PAGENUM=237 ID="BP242"ID="FM38629"Install NetWare 4.1 SFT IIIThis chapter describes how to install the NetWare 4.1® SFT IIITM operating system on two network servers: a NetWare® 4.1 server (Server 1), and a computer that doesn't have NetWare installed on it (Server 2).You must have NetWare 4.1 installed on one server or NetWare SFT III 3.11 installed on two servers before you can install NetWare 4.1 SFT III.To upgrade from NetWare SFT III 3.11 to NetWare 4.1 SFT III, see IDREF="FM37377""Upgrade from SFT III 3.11" on page 256.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="16*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you haveCOLNAME=2 ROTATE="0" MOREROWS="0"Do the followingVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NetWare 2.x, 3.x, or 4.0x installed on one serverCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="upmigenu" COLLECTION="nw41"Upgrade to NetWare 4.1.COLNAME=1 ROTATE="0" MOREROWS="0"NetWare 4.1 installed on one serverCOLNAME=2 ROTATE="0" MOREROWS="0"Begin with IDREF="FM40325""Prerequisite Tasks" on page 240COLNAME=1 ROTATE="0" MOREROWS="0"NetWare SFT III 3.11 installed on two serversCOLNAME=2 ROTATE="0" MOREROWS="0"Follow steps in IDREF="FM37177""Edit SFT III 3.11 .NCF Files (Optional)" on page 257RENDERAS="SECT1"Necessary ResourcesMARK=CHECKBOXThe NetWare 4.1SFT III Installation quick path card to get an overview of the process.Two IDXID="w3232"BOOK="_idx" COLLECTION="nw41" TIDREF="i1641"IDXID="w3233"BOOK="_idx" COLLECTION="nw41" TIDREF="i1825"
similar (preferably identical) 386, 486, or Pentium* computers (certified by Novell®) to be used as NetWare servers. Both computers must have similar (preferably identical) MARK=BULLETIDXID="w3234"BOOK="_idx" COLLECTION="nw41" TIDREF="i864"
CPU speed, memory, and storage capacityBrand and IDXID="w3235"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"
version of DOS (3.1 or later)Monitors (both monochrome or both color) and IDXID="w3236"BOOK="_idx" COLLECTION="nw41" TIDREF="i2503"
monitor boards (both VGA or both EGA, for example)PAGENUM=238 ID="BP243"A minimum of 16 MB of IDXID="w3237"BOOK="_idx" COLLECTION="nw41" TIDREF="i2383"IDXID="w3238"BOOK="_idx" COLLECTION="nw41" TIDREF="i3665"
RAM in each NetWare server. (Some configurations may require more RAM.)CPU hardware running at a minimum of 25 MHz in each NetWare server.A CD-ROM drive and drivers installed as a DOS device on Server 1.A diskette drive on each server. (NetWare 4.1 CLASS=DISKMain Server License diskette is 31/2 inches)The NetWare 4.1 CLASS=DISKOperating System CD-ROM.The CLASS=DISKNetWare 4.1 SFT III License diskette.(Optional) Working IDXID="w3239"BOOK="_idx" COLLECTION="nw41" TIDREF="i4201"
copies of third-party disk drivers, LAN drivers, MSLTM drivers, or NLMsTM.A Mirrored Server Link (MSL) connecting the two servers.The following table lists the third-party MSL boards certified at the time of publication. Additional boards may have been certified since. For full details on MSL board compatibility with NetWare 4.1 SFT III, call one of the following numbersFaxback: 1-801-429-2776   
  1-800-414-LABS (5227) 
Hotline: 1-801-429-5544COLS=4 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="0*"COLNAME=2 COLWIDTH="11*"COLNAME=3 COLWIDTH="6*"COLNAME=4 COLWIDTH="7*"NAMEST=1 NAMEEND=2 SPANNAME=SPAN1T2 ALIGN=LEFTNAMEST=1 NAMEEND=4 SPANNAME=SPAN1T4 ALIGN=LEFTVALIGN="BOTTOM"SPANNAME=SPAN1T2 ROTATE="0" MOREROWS="0"Company/Board NameCOLNAME=3 ROTATE="0" MOREROWS="0"Bus typeCOLNAME=4 ROTATE="0" MOREROWS="0"Driver nameVALIGN="TOP"SPANNAME=SPAN1T4 ROTATE="0" MOREROWS="0"Digital Equipment Corporation  1-800-DIGITAL or 1-603-884-6660COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"DEC* DEFEA Series Adapter for MSLCOLNAME=3 ROTATE="0" MOREROWS="0"EISACOLNAME=4 ROTATE="0" MOREROWS="0"DECMSL4X.MSLSPANNAME=SPAN1T4 ROTATE="0" MOREROWS="0"Eagle Technology  1-800-733-2453 or 1-408-441-7453COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NMSL  NE2000® (limited)  NE/2-32® (limited)COLNAME=3 ROTATE="0" MOREROWS="0"EISA  ISA  MCACOLNAME=4 ROTATE="0" MOREROWS="0"NMSL.MSL  HNE2000.MSL  HNE232.MALSPANNAME=SPAN1T4 ROTATE="0" MOREROWS="0"Microdyne  1-800-255-3967 or 1-703-329-3700COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"NMSLCOLNAME=3 ROTATE="0" MOREROWS="0"EISACOLNAME=4 ROTATE="0" MOREROWS="0"NMSL.MSLSPANNAME=SPAN1T4 ROTATE="0" MOREROWS="0"Plaintree Systems  1-800-370-2724 or 1-617-239-8077COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"WaveBus MSL (latest)COLNAME=3 ROTATE="0" MOREROWS="0"EISA, MCACOLNAME=4 ROTATE="0" MOREROWS="0"WBMSL.MSLSPANNAME=SPAN1T4 ROTATE="0" MOREROWS="0"Thomas Conrad Corporation  1-800-332-8683 or 1-512-836-1935COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"Thomas Conrad MSL (latest)  TCNS* MSL (latest)  TCNS* MSL Adapters (latest)COLNAME=3 ROTATE="0" MOREROWS="0"EISA, MCA, ISA  EISA, MCA, ISA  EISA, MCA, ISACOLNAME=4 ROTATE="0" MOREROWS="0"TCMSL.MSL  TCMSL.MSL  TCMSL.MSLSPANNAME=SPAN1T4 ROTATE="0" MOREROWS="0"SysKonnect  1-408-725-4650COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"SK-Net Series MSLCOLNAME=3 ROTATE="0" MOREROWS="0"EISA  MCA  ISACOLNAME=4 ROTATE="0" MOREROWS="0"SKFEMSL.MSL  SKFMMSL.MSL  SKFMSL.MSLSPANNAME=SPAN1T4 ROTATE="0" MOREROWS="0"Vinca  1-801-223-3100COLNAME=1 ROTATE="0" MOREROWS="0"COLNAME=2 ROTATE="0" MOREROWS="0"V32 MSLCOLNAME=3 ROTATE="0" MOREROWS="0"EISA, MCA, ISACOLNAME=4 ROTATE="0" MOREROWS="0"V32MSL.MSLPAGENUM=240 ID="BP244"RENDERAS="SECT1"ID="FM40325"Prerequisite Tasks MARK=CHECKBOXInstall NetWare 4.1 on Server 1. (See IDREF="FM44025"Chapter 3,  "Custom Installation", on IDREF="FM44025"page 63.)Create a DOS partition on Server 2 that is preferably the same size as the DOS partition on Server 1 (at least 15 MB).If you wish to accommodate core dumps to your hard drive, make the DOS partitions 15 MB plus the number of megabytes (MB) of RAM per server. For example, if each server has 16 MB of RAM, the DOS partition would be at least 31 MB (15 MB + 16 MB).Format three high-density diskettes and label them "Disk 1," "Disk 2," and "Disk 3."IDXID="w3240"BOOK="_idx" COLLECTION="nw41" TIDREF="i2547"
Install MSL (
Mirrored Server LinkTM) boards in Server 1 and Server 2. Cable the MSL boards in each server directly to each other (as shown in IDREF="FM70893"Figure 5-1). See the MSL board manufacturer's documentation for installation details.  Note the MSL board's address and the interrupt number for use later during installation.LABEL="5-1" FLOAT="0"ID="FM70893"MSL InstallationFILEREF="n41in66a.tif"PAGENUM=241 ID="BP245"For best performance, assign the MSL board a higher priority IDXID="w3241"BOOK="_idx" COLLECTION="nw41" TIDREF="i1883"IDXID="w3242"BOOK="_idx" COLLECTION="nw41" TIDREF="i2547"
interrupt than the network boards in the server.  Interrupt priorities from high to low are: 0, 1, 2 or 9, A, B, C, D, E, F, 3, 4, 5, 6, 7, and 8. Interrupt 2 is the highest priority you can assign to an MSL board, because interrupts 0 and 1 are reserved.(Optional) Install and cable an IDXID="w3243"BOOK="_idx" COLLECTION="nw41" TIDREF="i167"IDXID="w3244"BOOK="_idx" COLLECTION="nw41" TIDREF="i2547"
alternate MSL board in each server for hardware redundancy in case of primary MSL board failure.PAGENUM=242 ID="BP246"RENDERAS="SECT1"IDXID="w3245"BOOK="_idx" COLLECTION="nw41" TIDREF="i4121"
Install SFT III ServersThe installation of NetWare 4.1 SFT III includes these procedures:MARK=BULLETNaming and numbering the server enginesCopying NetWare 4.1 SFT III filesChoosing MSL (Mirrored Server Link) driversInstalling NetWare 4.1 SFT III on Server 2Creating and mirroring the NetWare partitionsRENDERAS="SECT2"Name and Number the Server EnginesRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Insert the NetWare 4.1 CLASS=DISKOperating System CD-ROM into the CD-ROM drive on Server 1.PERFORMANCE="REQUIRED"Turn on the CD-ROM drive.PERFORMANCE="REQUIRED"Boot DOS on Server 1.PERFORMANCE="REQUIRED"Change to the root directory of the CD-ROM drive.For example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"D: MOREINFO="NONE"<Enter> 
CD\ 
MOREINFO="NONE"<Enter> PERFORMANCE="REQUIRED"Type
FORMAT="LINESPECIFIC"MOREINFO="NONE"INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Select the language in which you want to install the software.PERFORMANCE="REQUIRED"Select "NetWare Server Installation."PERFORMANCE="REQUIRED"Select "NetWare 4.1 SFT III Installation."A menu displaying NetWare 4.1 SFT III installation options appears.
PAGENUM=243 ID="BP247"PERFORMANCE="REQUIRED"Select "Convert NetWare 4.1 to SFT III."PERFORMANCE="REQUIRED"In the space provided, type the 
IDXID="w3246"BOOK="_idx" COLLECTION="nw41" TIDREF="i2543"
MSEngine name and press 
MOREINFO="NONE"<Enter>.By default, the name you assigned to Server 1 when you installed NetWare 4.1 appears in the box. You may use this name for the MSEngine, or type in a different name.The MSEngine name should be a unique name that is 2 to 47 characters long, with no periods or spaces. Valid characters are A-Z, 0-9, hyphen, and underscore.  SFT III requires three unique server names: one for the mirrored operating system functions (MSEngine), and one for each server's input and output functions (IOEngine).  The system creates two IDXID="w3247"BOOK="_idx" COLLECTION="nw41" TIDREF="i1901"
IOEngine names by appending the characters "_IO1" and "_IO2" to the MSEngine name.  For more information see "BOOK="cncptenu" COLLECTION="nw41"MSEngine" and "BOOK="cncptenu" COLLECTION="nw41"IOEngine" in Concepts.PERFORMANCE="REQUIRED"Specify 
IDXID="w3248"BOOK="_idx" COLLECTION="nw41" TIDREF="i1936"
IPX internal network numbers for each engine by doing one of the following:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Select "Continue with Installation" to accept the randomly-generated numbers. PERFORMANCE="REQUIRED"Select "Modify Network Numbers" to assign your own IPX internal network numbers.Each internal network number should be a unique, hexadecimal number that is one to eight digits long. You can't assign an IPX internal network number of "0" or "FFFFFFFF."  Each IOEngine must have its own unique IPX internal network number, and the MSEngine number must be different from both IOEngine numbers.PAGENUM=244 ID="BP248"RENDERAS="SECT2"Copy NetWare 4.1 SFT III FilesRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"On Server 1, accept the default DOS boot directory or specify a new one.The installation utility copies MSERVER.EXE and other SFT III-specific files to the boot directory.If you specify a directory other than the one in which the STARTUP.NCF file for NetWare 4.1 is located, you will be asked to provide the location of STARTUP.NCF.PERFORMANCE="REQUIRED"Specify the location of your  AUTOEXEC.BAT file.If SERVER.EXE is in Server 1's AUTOEXEC.BAT file, the installation utility changes SERVER.EXE to MSERVER.EXE.PERFORMANCE="REQUIRED"Specify the diskette drive letter for Server 1.PERFORMANCE="REQUIRED"Insert 
CLASS=DISKDisk 1 (a blank, formatted, high-density diskette) into the diskette drive on Server 1 and press 
MOREINFO="NONE"<Enter>.The installation utility copies SFT III-specific files, MSL drivers, and batch files to Disk 1.If the diskette isn't blank, answer "Yes" to the prompt, "This diskette is not empty. Delete data and proceed?" If you wish to retain the data currently on the diskette, replace it with a blank diskette.PERFORMANCE="REQUIRED"Insert the other two diskettes as prompted.The installation utility copies MSERVER.EXE and installation batch files to 
CLASS=DISKDisk 2 and 
CLASS=DISKDisk 3.
PAGENUM=245 ID="BP249"RENDERAS="SECT2"Choose Mirrored Server Link (MSL) DriversRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Specify the IDXID="w3249"BOOK="_idx" COLLECTION="nw41" TIDREF="i2547"
MSL driver for the MSL board installed in Server 1.PERFORMANCE="REQUIRED"(Conditional) If the MSL board uses an MSL driver not listed on the screen, press 
MOREINFO="NONE"<Ins>.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Specify the drive for the MSL driver diskette.PERFORMANCE="REQUIRED"Select the MSL driver.PERFORMANCE="REQUIRED"Specify the memory address and interrupt number for the MSL board.PERFORMANCE="REQUIRED"(Conditional) If you installed an 
IDXID="w3250"BOOK="_idx" COLLECTION="nw41" TIDREF="i167"IDXID="w3251"BOOK="_idx" COLLECTION="nw41" TIDREF="i2547"
alternate MSL board in Server 1, specify an additional MSL driver.The INSTALL program loads the IOEngine on Server 1. After the MSL driver loads, installation on Server 1 is complete.RENDERAS="SECT2"Install SFT III on Server 2RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Leave Server 1 running and take the three DOS diskettes, the driver diskette(s), and the CLASS=DISKNetWare 4.1 SFT III License diskette to Server 2.PERFORMANCE="REQUIRED"Boot DOS on Server 2.PERFORMANCE="REQUIRED"Insert 
CLASS=DISKDisk 1 into the diskette drive on Server 2.PERFORMANCE="REQUIRED"Change to the diskette drive on Server 2 and type
FORMAT="LINESPECIFIC"MOREINFO="NONE"INSTALL MOREINFO="NONE"<Enter>The installation utility copies MSERVER.EXE, SFT III-specific files, MSL drivers, and batch files to Server 2's boot directory, which is the same as on Server 1.PERFORMANCE="REQUIRED"When prompted, insert 
CLASS=DISKDisk 2 and 
CLASS=DISKDisk 3 into the diskette drive on Server 2 and press 
MOREINFO="NONE"<Enter>.
PAGENUM=246 ID="BP250"PERFORMANCE="REQUIRED"After the files have been copied, remove 
CLASS=DISKDisk 3 from the diskette drive.PERFORMANCE="REQUIRED"Specify the MSL driver for the MSL board installed in Server 2.PERFORMANCE="REQUIRED"(Conditional) If the MSL board uses an MSL driver not listed on the screen, press 
MOREINFO="NONE"<Ins>.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Specify the path to the MSL driver diskette.PERFORMANCE="REQUIRED"Select the MSL driver.PERFORMANCE="REQUIRED"Specify the memory address and interrupt for the MSL board.PERFORMANCE="REQUIRED"(Conditional) If you installed an alternate MSL board in Server 2, specify an additional MSL driver.Load the MSL drivers on Server 2 in the same order they were loaded on Server 1.The installation utility loads the IOEngine on Server 2, synchronizes the memory, and executes the ACTIVATE SERVER command. ACTIVATE SERVER loads the MSEngine. The two server consoles display the same installation screen.PERFORMANCE="REQUIRED"Choose the server drivers for the hardware installed in Server 2.If Server 2's LAN and Disk hardware are the same as the hardware in Server 1, select "Make Drivers on the New Machine the Same as the Original."PERFORMANCE="REQUIRED"From the "Driver Actions" menu, select "Continue Installation."The disk and LAN drivers for Server 1 load, and the IPX external network numbers bound to the network boards in Server 1 are displayed.Note the board names if you have multiple network boards of the same type in the server.PERFORMANCE="REQUIRED"Continue by pressing 
MOREINFO="NONE"<Enter>.The disk and LAN drivers for Server 2 load, and you are prompted to accept or change the protocols bound to the network boards in Server 2.
PAGENUM=247 ID="BP251"Note the board names if you have multiple network boards of the same type in the server.PERFORMANCE="REQUIRED"Continue by pressing 
MOREINFO="NONE"<Enter>.RENDERAS="SECT2"Create and Mirror the NetWare Disk PartitionsRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Choose a partitioning method."Automatically" creates a NetWare disk partition in the available free space on Server 2, then mirrors the NetWare disk partition from Server 1 to Server 2. This method assumes that the disk storage is identical on both machines."Manually" allows you to specify the NetWare partition size and Hot FixTM Redirection Area on Server 2. Then, you must set up disk mirroring between the two servers' disk partitions.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"If you chose "Automatically," go to Step 15.PERFORMANCE="REQUIRED"If you chose "Manually," continue with Step 2.PERFORMANCE="REQUIRED"Select "Create, Delete, and Modify Disk Partitions."PERFORMANCE="REQUIRED"From the "Available Disk Drives" menu, select the disk drive for Server 2 (
MSEnginename_IO2).PERFORMANCE="REQUIRED"Select "Create NetWare Disk Partition" and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Specify the NetWare partition size on the disk drive for Server 2 (
MSEnginename_IO2) so that it matches the size of the NetWare partition for Server 1(
MSEnginename_IO1).If you don't make the NetWare partitions the same size on both servers, they will not mirror.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"From the "Disk Partition Information" screen, highlight the number next to "MB" on the "Partition Size" line.PERFORMANCE="REQUIRED"Type the size of the NetWare partition in megabytes (MB) and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Continue by pressing 
MOREINFO="NONE"<F10>.
PAGENUM=248 ID="BP252"PERFORMANCE="REQUIRED"When prompted to "Create NetWare Partition," choose "Yes."PERFORMANCE="REQUIRED"Return to "Disk Partition and Mirroring Options" by pressing 
MOREINFO="NONE"<Esc> twice.PERFORMANCE="REQUIRED"Set up disk mirroring between the two servers by selecting "Mirror/Unmirror Disk Partition Sets."Mirror each disk to a disk on the other server. This preserves your data if one server goes down.PERFORMANCE="REQUIRED"Select the disk partition for Server 1 (
MSEnginename_IO1) and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Add the disk partition for Server 2 (
MSEnginename_IO2) to the mirrored set by pressing 
MOREINFO="NONE"<Ins>.PERFORMANCE="REQUIRED"Select the disk partition for Server 2 (
MSEnginename_IO2) and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Continue by pressing 
MOREINFO="NONE"<F10>.The "Disk Partition Mirroring Status" list appears.An "In Sync" status on one partition alone does not mean the disk data is mirrored. After disk mirroring is complete, both partitions will be "In Sync." PERFORMANCE="REQUIRED"Return to "Disk Partition and Mirroring Options" by pressing 
MOREINFO="NONE"<Esc>.The percentage of mirroring completed appears. You can continue the installation process while the disks are mirroring.PERFORMANCE="REQUIRED"Select "Continue with Installation" and press 
MOREINFO="NONE"<Enter>.The installation utility mounts volume SYS:.PERFORMANCE="REQUIRED"ID="FM57309"When prompted, insert the 
CLASS=DISKNetWare 4.1 SFT III License diskette into the drive on Server 2 and press 
MOREINFO="NONE"<Enter>.Installation on both NetWare 4.1 SFT III servers is now complete.Although the installation process is finished, disk mirroring continues in background mode. The mirror status is displayed on the screen.Do not bring down the server or turn on Server Test Mode until the disks are fully mirrored. Otherwise, data may be lost.PAGENUM=249 ID="BP253"PERFORMANCE="REQUIRED"Exit the installation utility or edit the server configuration files as explained below.RENDERAS="SECT2"ID="FM16695"Edit Server Configuration Files (Optional) IDXID="w3252"BOOK="_idx" COLLECTION="nw41" TIDREF="i2616"IDXID="w3253"BOOK="_idx" COLLECTION="nw41" TIDREF="i738"When you turn on or restart the servers, NetWare 4.1 SFT III reads from server configuration files with the .NCF filename extension that were automatically created by the installation utility.After you set up disk mirroring, you can edit the .NCF files to customize your NetWare 4.1 SFT III system with additional LOAD commands or SET parameters. You can cut from one file and paste to another.To cut text, press MOREINFO="NONE"<Tab> to move to the window from which you want to copy. Use the arrow keys to place the cursor at the beginning of the text you wish to copy. Press MOREINFO="NONE"<F5> and then use the arrow keys to place the cursor at the end of the text you wish to copy. The selected text will be highlighted. Press MOREINFO="NONE"<delete> to cut. Press MOREINFO="NONE"<F6> to copy.To paste text, press MOREINFO="NONE"<Tab> to move to the window into which you want to copy. Use the arrow keys to place the cursor at the point you want to paste and then press MOREINFO="NONE"<Ins>.IDREF="FM80989"Table 5-1 lists the SFT III 
server configuration files, locations, and contents.LABEL="5-1" PGWIDE=0 TOCENTRY="1"ID="FM80989"SFT III Configuration Files in Order of ExecutionCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="7*"COLNAME=3 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"FileCOLNAME=2 ROTATE="0" MOREROWS="0"LocationCOLNAME=3 ROTATE="0" MOREROWS="0"ContentsVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"IDXID="w3254"BOOK="_idx" COLLECTION="nw41" TIDREF="i4121"
IOSTART.NCF  (Two files---one for each server)COLNAME=2 ROTATE="0" MOREROWS="0"DOS partitionCOLNAME=3 ROTATE="0" MOREROWS="0"IOEngine name and IPX internal network number; loading instructions for disk drivers and MSL drivers; IOEngine SET parameters; loading instructions for NLMs that do not require an active MSEngine or a mounted volume SYS:.COLNAME=1 ROTATE="0" MOREROWS="0"MSSTART.NCF  (Two identical files)COLNAME=2 ROTATE="0" MOREROWS="0"DOS partition of each machine in the startup directory with MSERVER.EXECOLNAME=3 ROTATE="0" MOREROWS="0"Commands that are executed by the MSEngine after the server is mirrored but before the system volume is mounted. Some SET parameters can be set only in MSSTART.NCF.COLNAME=1 ROTATE="0" MOREROWS="0"MSAUTO.NCFCOLNAME=2 ROTATE="0" MOREROWS="0"SYS:SYSTEMCOLNAME=3 ROTATE="0" MOREROWS="0"Commands that are executed by the MSEngine after the server is mirrored and the system volume mounted; initialization commands for Time Services; Directory Services, and most other Mirrored-Server NLMs; name and IPX internal network number; loading instructions for MSEngine NLMs.COLNAME=1 ROTATE="0" MOREROWS="0"IOAUTO.NCF  (Two files---one for each server)COLNAME=2 ROTATE="0" MOREROWS="0"DOS partition or Volume SYS:COLNAME=3 ROTATE="0" MOREROWS="0"Commands for loading network drivers and binding network protocols; loading instructions for NLMs that require an active MSEngine and a mounted volume SYS: (such as printing and backup NLMs).PAGENUM=250 ID="BP254"Changes to commands in the .NCF files do not take effect until you reboot the server.RENDERAS="SECT3"IDXID="w3255"BOOK="_idx" COLLECTION="nw41" TIDREF="i1903"
Edit the IOSTART.NCF FilesRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From the MSEngine prompt on either SFT III server, type FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w3256"BOOK="_idx" COLLECTION="nw41" TIDREF="i1838"
INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Select "NCF Files" and edit the IOSTART.NCF files for each NetWare server.PERFORMANCE="REQUIRED"Select the IOSTART.NCF option for Server 1.IDXID="w3257"BOOK="_idx" COLLECTION="nw41" TIDREF="i1903"
Example of IOSTART.NCF for primary 
IDXID="w3258"BOOK="_idx" COLLECTION="nw41" TIDREF="i1901"
IOEngine:
FORMAT="LINESPECIFIC"MOREINFO="NONE"ioengine name SFT3_IO1
ioengine ipx internal net 7654321
load isadisk port=1f0 int=e
PAGENUM=251 ID="BP255"load nmslThe LOAD command for the MSL driver should be the last line of the IOSTART.NCF file. The disk and MSL drivers should be in the same directory as MSERVER.EXE.PERFORMANCE="REQUIRED"Save the file by pressing 
MOREINFO="NONE"<F10> or <Esc> and then
MOREINFO="NONE" <Enter>.PERFORMANCE="REQUIRED"Select the IOSTART.NCF option for Server 2.Example of IOSTART.NCF for 
IDXID="w3259"BOOK="_idx" COLLECTION="nw41" TIDREF="i1901"
secondary IOEngine:
FORMAT="LINESPECIFIC"MOREINFO="NONE"ioengine name SFT3_IO2
ioengine ipx internal net 6543210
load isadisk port=1f0 int=e
load nmslThe LOAD command for the MSL driver should be the last line of the IOSTART.NCF file.PERFORMANCE="REQUIRED"Save the file by pressing 
MOREINFO="NONE"<Esc> and then 
MOREINFO="NONE"<Enter>.
PAGENUM=252 ID="BP256"RENDERAS="SECT3"IDXID="w3260"BOOK="_idx" COLLECTION="nw41" TIDREF="i1898"
Edit IOAUTO.NCF FilesRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From "NCF Files," select the IOAUTO.NCF option for Server 1.Example of 
IDXID="w3261"BOOK="_idx" COLLECTION="nw41" TIDREF="i1898"
IOAUTO.NCF file:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD NE2000 INT=3 PORT=300 FRAME=ETHERNET_802.2 NAME=NE2000_2_E82
BIND IPX NE2000_2_E82 NET=1012672PERFORMANCE="REQUIRED"Edit the file to load additional modules in Server 1's IOEngine.PERFORMANCE="REQUIRED"Save the file by pressing 
MOREINFO="NONE"<Esc> and then
MOREINFO="NONE" <Enter>.PERFORMANCE="REQUIRED"Select the IOAUTO.NCF option for Server 2.PERFORMANCE="REQUIRED"Edit the file to load modules in Server 2's IOEngine.PERFORMANCE="REQUIRED"Save the file by pressing 
MOREINFO="NONE"<Esc> and then 
MOREINFO="NONE"<Enter>.RENDERAS="SECT3"IDXID="w3262"BOOK="_idx" COLLECTION="nw41" TIDREF="i2540"
Edit MSAUTO.NCF FilesRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From "NCF Files," select the MSAUTO.NCF option.PERFORMANCE="REQUIRED"Edit the file to change the MSEngine name or IPX internal network number.Changes to the MSEngine name or IPX internal network number do not take effect until after you bring down both servers and reboot them.PERFORMANCE="REQUIRED"Save the file by pressing 
MOREINFO="NONE"<Esc> and then 
MOREINFO="NONE"<Enter>.
PAGENUM=253 ID="BP257"RENDERAS="SECT3"IDXID="w3263"BOOK="_idx" COLLECTION="nw41" TIDREF="i2552"
Edit MSSTART.NCF FilesRENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"From "NCF Files," select the MSSTART.NCF option.PERFORMANCE="REQUIRED"Type instructions in the MSSTART.NCF file to customize the SET parameters for your MSEngine. MSEngine parameters that can be set only in the MSSTART.NCF file include Minimum Packet Receive Buffers, Cache Buffer Size, Maximum Subdirectory Tree Depth, Auto TSS Blackout Flag, and Concurrent Remirror Requests. See SFT III Parameters under "
BOOK="utlrfenu" COLLECTION="nw41"SET" in
 Utilities Reference.PERFORMANCE="REQUIRED"Save the file by pressing 
MOREINFO="NONE"<Esc> and then
MOREINFO="NONE" <Enter>.
PAGENUM=254 ID="BP258"RENDERAS="SECT1"IDXID="w3264"BOOK="_idx" COLLECTION="nw41" TIDREF="i800"
View SFT III Console DisplaysSFT III servers have three console IDXID="w3265"BOOK="_idx" COLLECTION="nw41" TIDREF="i4121"
displays: the primary IOEngine, the secondary IDXID="w3266"BOOK="_idx" COLLECTION="nw41" TIDREF="i1901"
IOEngine, and the IDXID="w3267"BOOK="_idx" COLLECTION="nw41" TIDREF="i2543"
MSEngine. Press MOREINFO="NONE"<Alt> to see the IDXID="w3268"BOOK="_idx" COLLECTION="nw41" TIDREF="i800"
console IDXID="w3269"BOOK="_idx" COLLECTION="nw41" TIDREF="i4505"
title bar. The right side of the title bar indicates the primary or secondary console.Press MOREINFO="NONE"<Alt>+<Esc> or MOREINFO="NONE"<Ctrl>+<Esc> to view the server console displays in SFT III.MARK=BULLETTo select the primary IOEngine, the secondary IOEngine, the MSEngine, or other console displays (such as the installation screen), press MOREINFO="NONE"<Alt>+MOREINFO="NONE"<Esc>.To display a menu of console options, press MOREINFO="NONE"<Ctrl>+MOREINFO="NONE"<Esc>. Type the number of the console you wish to display.PAGENUM=255 ID="BP259"RENDERAS="SECT1"IDXID="w3270"BOOK="_idx" COLLECTION="nw41" TIDREF="i1264"
Implement Dual Processing (Optional) To implement dual processing with NetWare 4.1 SFT III, you must have a server with two IDXID="w3271"BOOK="_idx" COLLECTION="nw41" TIDREF="i864"
CPUs installed and a dual-processing IDXID="w3272"BOOK="_idx" COLLECTION="nw41" TIDREF="i1264"
driver (available from your server hardware manufacturer). A second processor may be installed in one or both SFT III servers.Follow the procedure below to assign one CPU to the IOEngine and one CPU to the MSEngine.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"From the IOEngine console of the server with two CPUs installed, load the dual processing driver.See the server hardware manufacturer's installation instructions for loading the dual processing driver. For example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD 2NDPROC MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"To implement dual processing at startup, put the load command in the IOSTART.NCF file of the server with two CPUs.
PAGENUM=256 ID="BP260"RENDERAS="SECT1"ID="FM37377"Upgrade from SFT III 3.11IDXID="w3273"BOOK="_idx" COLLECTION="nw41" TIDREF="i4680"IDXID="w3274"BOOK="_idx" COLLECTION="nw41" TIDREF="i4121"RENDERAS="SECT2"Necessary ResourcesMARK=CHECKBOXThe NetWare 4.1 SFT III Installation quick path card to get an overview of the processNetWare SFT III 3.11 installed on two serversA CD-ROM drive on one serverA diskette drive on each serverThe NetWare 4.1 CLASS=DISKOperating System CD-ROM and the NetWare 4.1 CLASS=DISKMain Server License disketteThe CLASS=DISKNetWare 4.1 SFT III License disketteThree formatted, high-density diskettes labeled "Disk 1," "Disk 2," and "Disk 3"RENDERAS="SECT2"Prerequisite TasksMARK=CHECKBOXBack up your NetWare SFT III 3.11 servers, including files in the DOS partitions of both servers.Note the directory in which MSERVER.EXE currently resides if you plan to install version 4.1 in the same directory as version 3.11.Make sure that all users are logged out.(Optional) Edit the .NCF files in both servers. See IDREF="FM37177""Edit SFT III 3.11 .NCF Files (Optional)" on page 257.Bring down the MSEngine and both IOEngines.PAGENUM=257 ID="BP261"RENDERAS="SECT2"ID="FM37177"Edit SFT III 3.11 .NCF Files (Optional)Before upgrading your NetWare SFT III servers to NetWare 4.1 SFT III, edit both servers' .NCF files ifMARK=BULLETThe .NCF files contain LOAD commands for third-party drivers or modules that aren't compatible with NetWare 4.1. To determine which drivers and modules are compatible with NetWare 4.1, call one of the following
numbers:Faxback: 1-801-429-2776   
  1-800-414-LABS (5227) 
Hotline: 1-801-429-5544Update the LOAD commands with the 4.1 driver or module names and the appropriate path names (if not on volume SYS:).Your servers use the Ethernet 802.3 frame type, but the frame type is not specified in the .NCF files.Specify the 802.3 frame type in the LOAD command in the IOAUTO.NCF files. For example, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD NE2000 FRAME=ETHERNET_802.3 INT=3 PORT=300The .NCF files contain old SET parameter names. Use the table below to update SET parameter names from previous versions to NetWare 4.1 SFT III SET parameter names.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="11*"COLNAME=2 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Old SET parameter namesCOLNAME=2 ROTATE="0" MOREROWS="0"SFT III 4.1 SET parameter namesVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Mirrored Server Comm ACK Wait Time OutCOLNAME=2 ROTATE="0" MOREROWS="0"MSL Error Wait TimeCOLNAME=1 ROTATE="0" MOREROWS="0"Secondary Take Over Delay AmountCOLNAME=2 ROTATE="0" MOREROWS="0"Secondary Take Over Wait TimeCOLNAME=1 ROTATE="0" MOREROWS="0"Comm Deadlock Detect Wait TimeCOLNAME=2 ROTATE="0" MOREROWS="0"MSL Deadlock Wait TimeCOLNAME=1 ROTATE="0" MOREROWS="0"Check Server to Server CommCOLNAME=2 ROTATE="0" MOREROWS="0"Extra MSL CheckingCOLNAME=1 ROTATE="0" MOREROWS="0"Primary Server Comm Deadlock Recovery OptionCOLNAME=2 ROTATE="0" MOREROWS="0"Primary Server MSL Deadlock Recovery OptionCOLNAME=1 ROTATE="0" MOREROWS="0"Secondary Server Comm Deadlock Recovery OptionCOLNAME=2 ROTATE="0" MOREROWS="0"Secondary Server MSL Deadlock Recovery OptionCOLNAME=1 ROTATE="0" MOREROWS="0"MSEngine Outputs DifferentCOLNAME=2 ROTATE="0" MOREROWS="0"MSEngine Outputs Different Recovery OptionCOLNAME=1 ROTATE="0" MOREROWS="0"Primary Server Comm Consistency Recovery OptionCOLNAME=2 ROTATE="0" MOREROWS="0"Primary Server MSL Consistency Error Recovery OptionCOLNAME=1 ROTATE="0" MOREROWS="0"Secondary Server Comm Consistency Recovery OptionCOLNAME=2 ROTATE="0" MOREROWS="0"Secondary Server MSL Consistency Error Recovery OptionCOLNAME=1 ROTATE="0" MOREROWS="0"Primary Server Comm Driver Stuck Recovery OptionCOLNAME=2 ROTATE="0" MOREROWS="0"Primary Server MSL Send Blocked Recovery OptionCOLNAME=1 ROTATE="0" MOREROWS="0"Secondary Server Comm Driver Stuck Recovery OptionCOLNAME=2 ROTATE="0" MOREROWS="0"Secondary Server MSL Send Blocked Recovery OptionCOLNAME=1 ROTATE="0" MOREROWS="0"Primary Server Comm Hardware Failure Recovery OptionCOLNAME=2 ROTATE="0" MOREROWS="0"Primary Server MSL Hardware Failure Recovery OptionCOLNAME=1 ROTATE="0" MOREROWS="0"Secondary Server Comm Hardware Failure Recovery OptionCOLNAME=2 ROTATE="0" MOREROWS="0"Secondary Server MSL Hardware Failure Recovery OptionCOLNAME=1 ROTATE="0" MOREROWS="0"Notify Users Of Mirrored Server SynchronizationCOLNAME=2 ROTATE="0" MOREROWS="0"Notify All Users Of Mirrored Server SynchronizationCOLNAME=1 ROTATE="0" MOREROWS="0"Notify Users Of Mirrored Server FailuresCOLNAME=2 ROTATE="0" MOREROWS="0"Server Failure Notification NamePAGENUM=259 ID="BP262"RENDERAS="SECT2"Upgrade Server 1RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Install the DOS CD-ROM drivers on the server with the CD-ROM drive.PERFORMANCE="REQUIRED"Insert the NetWare 4.1 
CLASS=DISKOperating System CD-ROM into the CD-ROM drive on Server 1.PERFORMANCE="REQUIRED"Turn on the CD-ROM drive.PERFORMANCE="REQUIRED"Boot DOS on Server 1.PERFORMANCE="REQUIRED"Change to the root directory of the CD-ROM drive.For example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"D: MOREINFO="NONE"<Enter> 
CD\ 
MOREINFO="NONE"<Enter> PERFORMANCE="REQUIRED"Type
FORMAT="LINESPECIFIC"MOREINFO="NONE"INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Select the language in which you want to install the software.PERFORMANCE="REQUIRED"Select "NetWare Server Installation."PERFORMANCE="REQUIRED"Select "NetWare 4.1 SFT III."A menu displaying SFT III installation options appears.PERFORMANCE="REQUIRED"Select "Upgrade SFT III 3.11 to SFT III 4.1" and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Specify the path for the destination directory.The destination directory can be the directory where the 3.11 version of MSERVER.EXE currently resides or it can be a new directory. If you install to the directory where the 3.11 version resides, you should first backup that directory. The installation utility will overwrite existing files when it copies the 4.1 MSERVER.EXE and other SFT III-specific files to the destination directory.PAGENUM=260 ID="BP263"PERFORMANCE="REQUIRED"(Conditional) Check the list of third-party drivers that were not updated in the DOS boot directory. These drivers may be compatible with NetWare 4.1, but if they are not you will need NetWare 4.1-compatible replacements on diskette.PERFORMANCE="REQUIRED"Specify the locale configuration and file format.See 
IDREF="FM67857""Specify Language and Filename Format Information" on page 80.PERFORMANCE="REQUIRED"Create diskettes for Server 2.Insert 
CLASS=DISKDisk 1, 
CLASS=DISKDisk 2, and 
CLASS=DISKDisk 3 as prompted.PERFORMANCE="REQUIRED"Remove 
CLASS=DISKDisk 3 when the files have been copied.PERFORMANCE="REQUIRED"Take the three diskettes to Server 2.RENDERAS="SECT2"Upgrade Server 2RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Boot DOS on Server 2. If you are using third-party drivers on Server 2, you will have to copy the drivers to the DOS boot directory and SYS:SYSTEM manually. They will not be copied during the automated installation procedure.PERFORMANCE="REQUIRED"Insert 
CLASS=DISKDisk 1 in the diskette drive of Server 2.PERFORMANCE="REQUIRED"Change to the diskette drive and type
FORMAT="LINESPECIFIC"MOREINFO="NONE"INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Insert 
CLASS=DISKDisk 2 and 
CLASS=DISKDisk 3 when prompted.PERFORMANCE="REQUIRED"Specify the path to the 3.11 IOSTART.NCF and MSSTART.NCF files from SFT III 3.11.PERFORMANCE="REQUIRED"Remove 
CLASS=DISKDisk 3 when the files have been copied and you are prompted for the NetWare 4.1
CLASS=DISK Main Server License diskette.PERFORMANCE="REQUIRED"Insert the NetWare 4.1
CLASS=DISK Main Server License diskette when prompted.
PAGENUM=261 ID="BP264"PERFORMANCE="REQUIRED"Insert the 
CLASS=DISKSFT III License diskette when prompted.For additional information about the procedural steps below, see IDREF="FM44025"Chapter 3,  "Custom Installation," beginning with IDREF="FM80634""Select Optional NetWare File Groups" on page 124.PERFORMANCE="REQUIRED"Select optional NetWare files to copy.PERFORMANCE="REQUIRED"Choose a Directory tree or create a new Directory tree.PERFORMANCE="REQUIRED"Specify the time zone and time configuration.PERFORMANCE="REQUIRED"Specify the server context.PERFORMANCE="REQUIRED"Specify the password for ADMIN.PERFORMANCE="REQUIRED"Save the NetWare Directory ServicesTM information.NetWare files copy to the SYSTEM and PUBLIC directories.PERFORMANCE="REQUIRED" (Conditional) If the IOSTART.NCF files contain load commands for network drivers, move those load commands from the IOSTART.NCF files to the IOAUTO.NCF files.The upgrade to NetWare 4.1 SFT III is complete.LABEL="6"PAGENUM=263 ID="BP265"ID="FM32801"Install NetWare ClientsRENDERAS="SECT1"OverviewThis chapter provides a basic overview of the procedures for installing a NetWare client on your network.RENDERAS="SECT1"IntroductionBefore you can continue setting up your network, you must install a single client. Installing a client will allow you to view the additional manuals provided in the NetWare 4.1 online documentation set, and to run either the NetWare Administrator utility or NETADMIN to start creating objects on your network. You can install and customize other clients later, using the following manuals provided in NetWare 4.1 online documentation.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="19*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ClientCOLNAME=2 ROTATE="0" MOREROWS="0"Manual TitleVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"DOS and  MS WindowsCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="ws_d1enu" COLLECTION="nw41"NetWare Client for DOS and MS Windows User GuideCOLNAME=1 ROTATE="0" MOREROWS="0"OS/2*COLNAME=2 ROTATE="0" MOREROWS="0"BOOK="ws_osenu" COLLECTION="nw41"NetWare Client for OS/2 User GuideCOLNAME=1 ROTATE="0" MOREROWS="0"MacintoshCOLNAME=2 ROTATE="0" MOREROWS="0"BOOK="macclenu" COLLECTION="nw41"Using MacNDS Client for NetWare 4Due to the extensive procedures for installing a Macintosh* client, and then configuring the AppleTalk* protocol, procedures for installing a Macintosh client are not included in this manual.PAGENUM=264 ID="BP266"RENDERAS="SECT1"ID="FM74198"Installing NetWare Client SoftwareBefore you can install the 
client software, you must have access to installation diskettes for NetWare ClientTM software.If you are installing the NetWare server from CD-ROM, you need to create these client diskettes. For instructions, see IDREF="FM41202""Create Client Diskettes from a Workstation" on page 296.When you have client installation diskettes available, use the table below to locate installation procedures for your particular client operating system.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="10*"COLNAME=2 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If you want to installCOLNAME=2 ROTATE="0" MOREROWS="0"Go toVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"NetWare Client software for DOS and MS Windows client workstationsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM69794""Install a DOS and MS Windows Client" on page 265COLNAME=1 ROTATE="0" MOREROWS="0"NetWare Client software for OS/2 client workstationsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM11329""Install an OS/2 Client" on page 268PAGENUM=265 ID="BP267"RENDERAS="SECT2"ID="FM69794"Install a DOS and MS Windows ClientIDXID="w3275"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"DOS and MS Windows clients share the same installation program. To provide for this, the installation program runs within the DOS environment. RENDERAS="SECT3"IDXID="w3276"BOOK="_idx" COLLECTION="nw41" TIDREF="i1825"
PrerequisitesMARK=CHECKBOXAn IBM* PC (or compatible) with an XT, AT, 386, 486, or higher (SX or DX) processor.IDXID="w3277"BOOK="_idx" COLLECTION="nw41" TIDREF="i2383"
A hard drive or a floppy drive and diskette with the following amount of available disk space:MARK=BULLETDOS only: IDXID="w3278"BOOK="_idx" COLLECTION="nw41" TIDREF="i1181"
1.2 MBDOS and MS Windows: IDXID="w3279"BOOK="_idx" COLLECTION="nw41" TIDREF="i2534"
4 MBA network board installed in your client computer. Network boards are supplied with default settings for the interrupt, base I/O port address and base 
memory address. You should already know the hardware board settings for your particular network board before running the installation program. For more information on installing the network board, see the manufacturer's documentation.Most network boards use interrupt 3 or 5 if these are not used by COM2: or LPT2:.The base I/O port addresses often available for the network board are 300h and 340h.If you specify an interrupt for the network board that is already being used by another device, you can still install the network board, but the network software will not run successfully.The base memory address often available for the network board is D800 (sometimes written as D8000). Some network boards do not use RAM; if your network board is one of these, you do not need to specify a value for this setting. If you use a memory manager (for example, EMM386 or QEMM*), you might need to exclude the base memory address controlled by the memory manager, if the memory manager cannot automatically detect that it is used by the network board.PAGENUM=266 ID="BP268"IDXID="w3280"BOOK="_idx" COLLECTION="nw41" TIDREF="i561"
Network cabling.Each type of network board requires unique cabling. See the manufacturer's documentation packaged with your network board for requirements.Token ring network boards require a cable connection to the MAU before installing the operating system. Otherwise, the NTR2000 driver will not load.(Optional) A computer cabled to the network and running MS Windows 3.1.If you are using MS Windows, close MS Windows before loading the installation program. The client installation program will modify some MS Windows files that are used when in MS Windows. Do not install from an MS Windows DOS Box.At least one NetWare 4.1 server installed.Five formatted diskettes with the following names and labels:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="16*"COLNAME=2 COLWIDTH="8*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Diskette nameCOLNAME=2 ROTATE="0" MOREROWS="0"Volume labelVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows  Disk 1COLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_1COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows  Disk 2COLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_2COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows  Disk 3COLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_3COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows  Disk 4COLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_4COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows  ODI LAN driversCOLNAME=2 ROTATE="0" MOREROWS="0"WSDOS_5PAGENUM=267 ID="BP269"RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"Insert the CLASS=DISKNetWare Client for DOS and MS Windows Installation Diskette #1 into your floppy disk drive.PERFORMANCE="REQUIRED"Change to the drive containing the installation diskette.For example, to install from drive A:, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"A:MOREINFO="NONE" <Enter>PERFORMANCE="REQUIRED"Load the installation utility by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"INSTALLMOREINFO="NONE" <Enter>PERFORMANCE="REQUIRED"Follow the installation instructions on your screen.Default settings for the NetWare Client software should be sufficient for an initial connection. You can do a standard installation with the default settings and configure other options later.Use the arrow keys to move between the fields. Press MOREINFO="NONE"<Enter> to modify a particular field.PERFORMANCE="REQUIRED"Exit the installation utility by pressing the 
MOREINFO="NONE"<Esc> key.PERFORMANCE="REQUIRED"Reboot your computer.In order for your modifications or new installation to take effect, you need to reboot your computer. PERFORMANCE="REQUIRED"Set up your workstation for accessing the online documentation by reading 

BOOK="docinenu" COLLECTION="nw41"Installing and Using Novell Online Documentation 
for NetWare 4.1.
PAGENUM=268 ID="BP270"RENDERAS="SECT2"ID="FM10660"ID="FM11329"Install an OS/2 ClientReview the following checklist to make sure you are prepared to install the NetWare Client software for OS/2. RENDERAS="SECT3"IDXID="w3281"BOOK="_idx" COLLECTION="nw41" TIDREF="i1825"
PrerequisitesMARK=CHECKBOXAn IBM PC (or compatible) with a 386 or 486 (SX or DX) processor. OS/2 v2.x operates only with 386 (SX and DX) processors and above because of its 32-bit architecture. IDXID="w3282"BOOK="_idx" COLLECTION="nw41" TIDREF="i2383"
A hard disk with 4.5 MB of storage.A network board installed in your client computer. Network boards are supplied with default settings for the interrupt, base I/O port address and base 
memory address. You should already know the hardware board settings for your particular network board before running the installation utility. For more information on installing the network board, see the manufacturer's documentation.Most network boards use interrupt 3 or 5 if these are not used by COM2 or LPT2.The base I/O port addresses often available for the network board are 300h and 340h.If you specify an interrupt for the network board that is already being used by another device, you can still install the network board, but the network software will not run successfully.The base memory address often available for the network board is D800 (sometimes written as D8000). Some network boards do not use RAM; if your network board is one of these, you do not need to specify a value for this setting. PAGENUM=269 ID="BP271"IDXID="w3283"BOOK="_idx" COLLECTION="nw41" TIDREF="i561"
Network cabling.Each type of network board requires unique cabling. See the manufacturer's documentation packaged with your network board for requirements.Token ring network boards require a cable connection to the MAU before installing the operating system. Otherwise, the TOKEN driver will not load.At least one NetWare 4.1 server installed.Six formatted diskettes (seven if you want to create an optional VLM boot diskette) with the following diskette names and volume labels:COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Diskette NameCOLNAME=2 ROTATE="0" MOREROWS="0"Volume LabelVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKWSOS2_1COLNAME=2 ROTATE="0" MOREROWS="0"WSOS2_1COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKWSOS2_2COLNAME=2 ROTATE="0" MOREROWS="0"WSOS2_2COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKWSOS2_3COLNAME=2 ROTATE="0" MOREROWS="0"WSOS2_3COLNAME=1 ROTATE="0" MOREROWS="0"OSUTIL1COLNAME=2 ROTATE="0" MOREROWS="0"OSUTIL1COLNAME=1 ROTATE="0" MOREROWS="0"OS2DOC_XCOLNAME=2 ROTATE="0" MOREROWS="0"OS2DOC_XCLASS=DISK1 = English  2 = French  3 = German  4 = Italian  5 = SpanishCOLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKWSDRV_1COLNAME=2 ROTATE="0" MOREROWS="0"WSDRV_1COLNAME=1 ROTATE="0" MOREROWS="0"CLASS=DISKVLMBOOTCLASS=DISK (optional)COLNAME=2 ROTATE="0" MOREROWS="0"VLMBOOTPAGENUM=270 ID="BP272"RENDERAS="SECT3"ProcedureThese procedures are presented in greater detail in IDREF="FM72388"Chapter 4 "Install NetWare Server for OS/2." If you are installing an OS/2 client for the first time, we recommend following the procedures under IDREF="FM30513""Install NetWare Client for OS/2" on page 213.PERFORMANCE="REQUIRED"Start the OS/2 client and open an OS/2 full screen or window.PERFORMANCE="REQUIRED"Insert the 
CLASS=DISKWSOS2_1 diskette into the diskette drive.PERFORMANCE="REQUIRED"Change to the drive where you inserted the diskette and type
FORMAT="LINESPECIFIC"MOREINFO="NONE"INSTALL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Select "Requester on Client" from the "Installation" menu.PERFORMANCE="REQUIRED"Follow the screen prompts and the online help to finish installing the Requester. Because this computer is being installed to get you started with the network setup, you can do a standard installation with the default settings and configure other options later.During installation, a directory called NETWARE is created for the Requester files on the drive you booted OS/2 from. A program group called NOVELL is also created on the OS/2 desktop.PERFORMANCE="REQUIRED"Exit the installation program by selecting "Exit" from the "Installation" menu.PERFORMANCE="REQUIRED"Remove the diskette from the floppy drive, and then select the OS/2 shutdown feature to reboot the computer.In order for your modifications or new installation to take effect, you need to reboot your computer.PERFORMANCE="REQUIRED"Set up your workstation for accessing the online documentation by reading 

BOOK="docinenu" COLLECTION="nw41"Installing and Using Novell Online Documentation for NetWare 4.1LABEL="A"PAGENUM=271 ID="BP273"ID="FM69155"Calculate RAM RequirementsThis appendix provides a detailed IDXID="w3284"BOOK="_idx" COLLECTION="nw41" TIDREF="i580"
formula for IDXID="w3285"BOOK="_idx" COLLECTION="nw41" TIDREF="i1556"IDXID="w3286"BOOK="_idx" COLLECTION="nw41" TIDREF="i3665"IDXID="w3287"BOOK="_idx" COLLECTION="nw41" TIDREF="i3665"
calculating your NetWare® 4.1 RAM requirements.Calculating RAM requirements involves defining RAM usage for three major components:MARK=BULLETNetWare operating systemVolumesNetWare Loadable ModulesTM (NLMTM) programsThe following charts list items that take up RAM, and provide a formula for calculating that item's RAM usage. An example calculation follows in IDREF="FM65953""Example RAM Calculation" on page 275.For information on any item in the charts, see 
BOOK="cncptenu" COLLECTION="nw41"Concepts.PAGENUM=272 ID="BP274"RENDERAS="SECT1"NetWare Operating System IDXID="w3288"BOOK="_idx" COLLECTION="nw41" TIDREF="i3665"
RequirementsSome of the following information can only be obtained by installing a server and loading MONITOR.NLM to see server statistics.LABEL="A-1" PGWIDE=1 TOCENTRY="1"ID="FM27125" Operating System RequirementsCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="7*"COLNAME=2 COLWIDTH="14*"COLNAME=3 COLWIDTH="12*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ItemCOLNAME=2 ROTATE="0" MOREROWS="0"RAM usageCOLNAME=3 ROTATE="0" MOREROWS="0"NotesVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Core NetWare operating systemCOLNAME=2 ROTATE="0" MOREROWS="0"7 MBCOLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"Cache memoryCOLNAME=2 ROTATE="0" MOREROWS="0"1 MB + (MB of disk space online  x 3 KB)COLNAME=3 ROTATE="0" MOREROWS="0"This formula is an estimate based on reasonable performance per user. It assumes that the number of users increases with disk space.COLNAME=1 ROTATE="0" MOREROWS="0"Media ManagerCOLNAME=2 ROTATE="0" MOREROWS="0"150 KB + (0.2 KB x MB of disk space online)COLNAME=3 ROTATE="0" MOREROWS="0"COLNAME=1 ROTATE="0" MOREROWS="0"Connections in useCOLNAME=2 ROTATE="0" MOREROWS="0"2 KB per user connectionCOLNAME=3 ROTATE="0" MOREROWS="0"For an installed server, see MONITOR.NLM.COLNAME=1 ROTATE="0" MOREROWS="0"Packet receive buffersCOLNAME=2 ROTATE="0" MOREROWS="0"2.3 KB per buffer COLNAME=3 ROTATE="0" MOREROWS="0"For an installed server, see MONITOR.NLM.COLNAME=1 ROTATE="0" MOREROWS="0"Directory cache buffersCOLNAME=2 ROTATE="0" MOREROWS="0"4.3 KB per buffer COLNAME=3 ROTATE="0" MOREROWS="0"For an installed server, see MONITOR.NLM.COLNAME=1 ROTATE="0" MOREROWS="0"Service processesCOLNAME=2 ROTATE="0" MOREROWS="0"9 KB per service processCOLNAME=3 ROTATE="0" MOREROWS="0"For an installed server, see MONITOR.NLM.COLNAME=1 ROTATE="0" MOREROWS="0"File compression enabled on any volumeCOLNAME=2 ROTATE="0" MOREROWS="0"250 KBCOLNAME=3 ROTATE="0" MOREROWS="0"PAGENUM=273 ID="BP275"RENDERAS="SECT1"Volume-Related IDXID="w3289"BOOK="_idx" COLLECTION="nw41" TIDREF="i3665"IDXID="w3290"BOOK="_idx" COLLECTION="nw41" TIDREF="i4800"
RequirementsYou need to calculate the following items for each volume individually and then add up the results from all volumes.LABEL="A-2" PGWIDE=1 TOCENTRY="1"ID="FM42176" Volume RequirementsCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="10*"COLNAME=3 COLWIDTH="15*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ItemCOLNAME=2 ROTATE="0" MOREROWS="0"RAM usageCOLNAME=3 ROTATE="0" MOREROWS="0"NotesVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"File Allocation Tables (FAT)COLNAME=2 ROTATE="0" MOREROWS="0"Volume Blocks x 8.2 bytes COLNAME=3 ROTATE="0" MOREROWS="0"Calculate Volume Blocks by dividing the size of the volume by its block size. For a listing of default volume block sizes, refer to IDREF="FM85813""Modify Volume Block Size (Optional)" on page 112COLNAME=1 ROTATE="0" MOREROWS="0"Block suballocation enabledCOLNAME=2 ROTATE="0" MOREROWS="0"((Blocksize x 2)-1) x 4096 bytes) + (5 x Number of files) bytesCOLNAME=3 ROTATE="0" MOREROWS="0"Calculate the approximate number of files by dividing the volume size by the average file size.COLNAME=1 ROTATE="0" MOREROWS="0"Directory Entry Tables (DET) COLNAME=2 ROTATE="0" MOREROWS="0"Number of files x 10 bytesCOLNAME=3 ROTATE="0" MOREROWS="0"Calculate the approximate number of files by dividing the volume size by the average file size.PAGENUM=274 ID="BP276"RENDERAS="SECT1"NLM IDXID="w3291"BOOK="_idx" COLLECTION="nw41" TIDREF="i3665"IDXID="w3292"BOOK="_idx" COLLECTION="nw41" TIDREF="i2755"
RequirementsThe following chart lists some NLMs that take up more RAM than most other NLMs and, therefore, should be included in this calculation.LABEL="A-3" PGWIDE=1 TOCENTRY="1"ID="FM89203" NLM RequirementsCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="9*"COLNAME=2 COLWIDTH="7*"COLNAME=3 COLWIDTH="18*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ItemCOLNAME=2 ROTATE="0" MOREROWS="0"RAM usageCOLNAME=3 ROTATE="0" MOREROWS="0"NotesVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"BTRIEVE.NLMCOLNAME=2 ROTATE="0" MOREROWS="0"700 KBCOLNAME=3 ROTATE="0" MOREROWS="0"Needed for products such as NetWare for Macintosh* and NetWare for NFSCOLNAME=1 ROTATE="0" MOREROWS="0"CLIB.NLMCOLNAME=2 ROTATE="0" MOREROWS="0"500 KBCOLNAME=3 ROTATE="0" MOREROWS="0"Needed for products such as Print Server, and for many other NetWare Loadable ModulesCOLNAME=1 ROTATE="0" MOREROWS="0"INSTALL.NLMCOLNAME=2 ROTATE="0" MOREROWS="0"600 KB COLNAME=3 ROTATE="0" MOREROWS="0"Needed for installation and maintenanceCOLNAME=1 ROTATE="0" MOREROWS="0"PSERVER.NLMCOLNAME=2 ROTATE="0" MOREROWS="0"200 KBCOLNAME=3 ROTATE="0" MOREROWS="0"Needed for Print ServerPAGENUM=275 ID="BP277"RENDERAS="SECT1"Calculate Your RAM RequirementsRENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"Calculate each of the operating system requirements in IDREF="FM27125"Table A-1 on page 272.PERFORMANCE="REQUIRED"Then add the volume requirements calculated in 
IDREF="FM42176"Table A-2 on page 273.PERFORMANCE="REQUIRED"Then add the NLM requirements calculated in 
IDREF="FM89203"Table A-3 on page 274.See the example below.RENDERAS="SECT1"ID="FM65953"Example IDXID="w3293"BOOK="_idx" COLLECTION="nw41" TIDREF="i3665"
RAM CalculationAssume you want to install a system with MARK=BULLET500 users2 GB (2,000 MB) of disk spaceFour volumes with file compression and block suballocation enabled:MARK=BULLETVolume SYS: with 100 MBVolume MACVOL: with 500 MBVolume DATA: with 1 GB (file compression enabled)Volume ACCOUNTS: with 400 MBAn average file size of 30 KBBased on these assumptions, a RAM calculation would look like the following.PAGENUM=276 ID="BP278"RENDERAS="SECT2"NetWare OS RequirementsTo make the calculation easier, assume 1 KB to mean 1,000 bytes (instead of 1,024 bytes), and 1 MB to mean 1,000,000 bytes (instead of 1,048,576 bytes.)NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Assume a core operating system requirement of 7 MB.Add 11 MB for cache memory.1 MB + (2000 x 5 KB) = 11 MBAdd 550 KB for the Media Manager.150 KB + (0.2 KB x 2000) = 550 KBAdd 1 MB for user connections.2 KB x 500 users = 1,000 KB = 1 MBAdd 230 KB for packet receive buffers.Assume you need about 100 buffers for a system of this size.2.3 KB x 100 = 230 KBAdd 430 KB for directory cache buffers.Assume you need about 100 buffers for a system of this size.4.3 KB x 100 = 430 KBAdd 180 KB for service processes.Assume about 20 service processes for a system of this size. (Service processes are workstation requests that are tracked by MONITOR.NLM.)Add 250 KB for file compression.Total approximate RAM requirements for the NetWare operating system: 20.7 MBPAGENUM=277 ID="BP279"RENDERAS="SECT2"Volume RequirementsCalculate these requirements individually for each volume on your system.NUMERATION=ARABIC CONTINUATION="RESTARTS" INHERITNUM="IGNORE"Add 2 MB for FAT tables on all four volumes.Volume SYS: (100 MB) needs 0.1 MBVolume MACVOL: (500 MB) needs 0.5 MBVolume DATA: (1 GB) needs 1 MBVolume ACCOUNTS: (400 MB) needs 0.4 MBTotal requirements for FAT tables: 2 MBAdd 1 MB for block suballocation on all four volumes.Volume SYS: (100 MB) needs 80 KBVolume MACVOL: (500 MB) needs 341 KBVolume DATA: (1 GB) needs 425 KBVolume ACCOUNTS: (400 MB) needs 194 KBTotal requirements for block suballocation: 1 MBAdd 666 KB for directory entries on all four volumes.Volume SYS: (100 MB) needs 33 KBVolume MACVOL: (500 MB) needs 167 KBVolume DATA: (1GB) needs 333 KBVolume ACCOUNTS: (400 MB) needs 133 KBTotal requirements for directory entries: 666 KBTotal approximate RAM requirements for all volumes: 3.67 MBPAGENUM=278 ID="BP280"RENDERAS="SECT2"NLM RequirementsAssuming that you need CLIB.NLM (500 KB), INSTALL.NLM (600 KB), and PSERVER.NLM (200 KB), add 1.3 MB for NLMs. RENDERAS="SECT2"Grand TotalOS + Volume + NLM requirements = Grand Total20.7 MB + 3.67 MB + 1.3 MB = 25.67 (25.7) MBThe approximate minimum RAM requirement for a NetWare system of this size is 25.7 MB.LABEL="B"PAGENUM=279 ID="BP281"ID="FM47650"Country CodesThis appendix lists the CCITT country codes you can use in specifying the NetWare® 4.1 
server's context. The country object is optional in the Directory tree, and can be used if you have a multinational organization or if you want to match the ISO X.500 standard. You can, however, comply with X.500 without specifying a country code.The following list of IDXID="w3294"BOOK="_idx" COLLECTION="nw41" TIDREF="i859"
country codes may be incomplete or inaccurate due to the constantly changing worldwide geopolitical situation.LABEL="B-1" FLOAT="0"Country CodesFILEREF="n41in17a.tif"PAGENUM=280 ID="BP282"LABEL="C"PAGENUM=281 ID="BP283"ID="FM28298"Install To Boot From Floppy DisketteNetWare® 4.1 supports booting the server from floppy diskette. However, for ease of installation, we recommend booting the server from an internal hard disk.  To install your NetWare 4.1 server to boot from an internal hard disk, see IDREF="FM50906""Install Server Software," on page 18 if you are installing using the Simple Installation option, or IDREF="FM43309""Install the Server Software," on page 66 if you are using the Custom Installation option.RENDERAS="SECT1"OverviewIDXID="w3295"BOOK="_idx" COLLECTION="nw41" TIDREF="i502"IDXID="w3296"BOOK="_idx" COLLECTION="nw41" TIDREF="i1135"
Booting a NetWare server IDXID="w3297"BOOK="_idx" COLLECTION="nw41" TIDREF="i502"
from floppy diskette circumvents that part of the NetWare 4.1 installation program that copies files to the DOS partition of your internal hard disk. The following circumstances call for a floppy diskette boot method for a new installation or upgrade:MARK=BULLETYou don't want a DOS partition on the NetWare server's internal hard disk.The computer you want to install NetWare on has no internal hard disk.PAGENUM=282 ID="BP284"RENDERAS="SECT1"IDXID="w3298"BOOK="_idx" COLLECTION="nw41" TIDREF="i1135"IDXID="w3299"BOOK="_idx" COLLECTION="nw41" TIDREF="i491"
Boot Diskette Advantages and DisadvantagesCompared to booting from a hard disk, booting from a floppy diskette has the following advantages:MARK=BULLETThe entire internal hard disk can be used for a NetWare disk partition.Boot diskettes can be stored apart from the NetWare server to prevent tampering.However, consider these disadvantages as well:MARK=BULLETBooting from floppy diskette is considerably slower than the hard disk method.You may run out of diskette space in future upgrades.This method requires multiple diskettes and is therefore a manual operation.RENDERAS="SECT1"Installation Procedure LocationsProcedures for installing the server to boot from floppy diskette are documented exclusively in a README file named BOOTDISK.TXTIf you are installing from CD-ROM, the BOOTDISK.TXT file is located on the Operating System CD-ROM in the following directory:FORMAT="LINESPECIFIC"MOREINFO="NONE"NW410\INSTALL\LANGUAGE\README\BOOTDISK.TXTReplace LANGUAGE with the directory name for the language you are installing (ENGLISH, ITALIANO, etc.).If you are installing from floppy diskettes, the BOOTDISK.TXT file is located in the README directory on the README_1 diskette.The BOOTDISK.TXT file can also be accessed within the installation utility.  First type INSTALL, choose your desired server language, and then choose "NetWare Server Installation."Then choose "Display Information (README) File," and locate and select the "Creating Server Boot Diskettes" README file.If you want to print the BOOTDISK.TXT file, you must do so from the CD-ROM or diskette.LABEL="D"PAGENUM=293 ID="BP294"ID="FM56136"Creating Client DiskettesID="FMINSTA"During installation, the "Other Installation Items" menu allows you to create client diskettes. If you don't create client diskettes at that time, you may do so by following the procedures in this section.RENDERAS="SECT1"PrerequisitesFormat the appropriate number of high-density diskettes using the table below.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="13*"COLNAME=2 COLWIDTH="13*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"For COLNAME=2 ROTATE="0" MOREROWS="0"FormatVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"DOS/MS Windows workstationsCOLNAME=2 ROTATE="0" MOREROWS="0"Five 3.5-inch or 5.25 inch diskettes.COLNAME=1 ROTATE="0" MOREROWS="0"OS/2* workstationsCOLNAME=2 ROTATE="0" MOREROWS="0"Six 3.5-inch diskettes (Seven if you want to create an optional VLM boot diskette).COLNAME=1 ROTATE="0" MOREROWS="0"Macintosh workstationsCOLNAME=2 ROTATE="0" MOREROWS="0"One 800 KB diskette.PAGENUM=294 ID="BP295"RENDERAS="SECT1"Create DOS, MS Windows, and OS/2 Client DiskettesYou can create DOS, MS Windows, and OS/2 client diskettes at the NetWare 4.1 server, or from a DOS, MS Windows, or OS/2 workstation. Procedures for both methods follow.RENDERAS="SECT2"Create Client Diskettes at the ServerRENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"At the server console typeFORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>The "Installation Options" menu appears.PERFORMANCE="REQUIRED"Choose "Product Options" and press 
MOREINFO="NONE"<Enter>.The "Other Installation Actions" menu appears.PERFORMANCE="REQUIRED"Select "Choose an Item or Product Listed Above" and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Choose "Create DOS/MS Windows/OS2 Client Install Diskettes" and press 
MOREINFO="NONE"<Enter>.You are prompted to enter the path to the source directory where the NetWare 4.1 files are located.PERFORMANCE="REQUIRED"Verify or change the source path and press 
MOREINFO="NONE"<Enter>.A screen appears prompting you for your user name and password.PERFORMANCE="REQUIRED" Enter your user name and password and press 
MOREINFO="NONE"<Enter>.
PAGENUM=295 ID="BP296"The following menu appears.FLOAT="0"Select the Client Files You Want to Copy to DisketteFILEREF="n41i115a.tif"PERFORMANCE="REQUIRED"Select or deselect the file groups you want copied by pressing 
MOREINFO="NONE"<Enter>. PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F10> to accept the marked groups and continue.PERFORMANCE="REQUIRED"Specify the destination to where the client files will be copied. By default, the client files are copied to drive A:. To specify a new path, press 
MOREINFO="NONE"<F3> and type the new path.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to accept the path.PERFORMANCE="REQUIRED"Insert the formatted diskettes as prompted.
PAGENUM=296 ID="BP297"RENDERAS="SECT2"ID="FM41202"Create Client Diskettes from a WorkstationYou can create client diskettes from a workstation either by using a CD-ROM drive connected directly to the workstation as a DOS device, or by mapping a drive to a server with the NetWare 4 Operating System CD-ROM mounted as a NetWare volume.RENDERAS="SECT3"ProcedurePERFORMANCE="REQUIRED"(DOS volume only) Install the IDXID="w3300"BOOK="_idx" COLLECTION="nw41" TIDREF="i603"IDXID="w3301"BOOK="_idx" COLLECTION="nw41" TIDREF="i646"
CD-ROM drive as a DOS device according to manufacturer's instructions.PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Go to the drive corresponding to the CD-ROM.PERFORMANCE="REQUIRED"Change to the CLIENT directory.PERFORMANCE="REQUIRED"Skip to 
IDREF="FM91629"Step 3.PERFORMANCE="REQUIRED"(NetWare volume) If you set up the CD-ROM as a NetWare volume, complete the following steps:PERFORMANCE="REQUIRED"PERFORMANCE="REQUIRED"Map a drive to the following path:
FORMAT="LINESPECIFIC"MOREINFO="NONE"NW410:CLIENTPERFORMANCE="REQUIRED"Change to the drive letter mapped to CD-ROM volume.PERFORMANCE="REQUIRED"Continue with 
IDREF="FM91629"Step 3.PERFORMANCE="REQUIRED"ID="FM91629"Change to one of the following subdirectories.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="12*"COLNAME=2 COLWIDTH="14*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"If creating diskettes forCOLNAME=2 ROTATE="0" MOREROWS="0"Go to this subdirectoryVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"DOS/MS WindowsCOLNAME=2 ROTATE="0" MOREROWS="0"DOSWINCOLNAME=1 ROTATE="0" MOREROWS="0"OS/2COLNAME=2 ROTATE="0" MOREROWS="0"OS2PERFORMANCE="REQUIRED"Type
FORMAT="LINESPECIFIC"MOREINFO="NONE"IDXID="w3302"BOOK="_idx" COLLECTION="nw41" TIDREF="i2311"
MAKEDISK drive_letter: language MOREINFO="NONE"<Enter>Replace 
drive_letter with the letter of the diskette drive you are inserting the empty formatted diskettes into.Replace 
language with the language you want to install. The following languages are available: English, Francais, Deutsch, Italiano, Español.
PAGENUM=297 ID="BP298"For example, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAKEDISK A: espanol MOREINFO="NONE"<Enter>or
FORMAT="LINESPECIFIC"MOREINFO="NONE"MAKEDISK B: italiano MOREINFO="NONE"<Enter>The MAKEDISK utility copies the client installation files from the CD-ROM directory to the diskettes. Follow the prompts to insert new empty formatted diskettes.PERFORMANCE="REQUIRED"Attach a label to each diskette and write the following on the corresponding labels.LABEL="D-1" PGWIDE=0 TOCENTRY="1" Client Diskette LabelsCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="3*"COLNAME=2 COLWIDTH="14*"COLNAME=3 COLWIDTH="7*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"Diskette #COLNAME=2 ROTATE="0" MOREROWS="0"Label for DOS/MS WindowsCOLNAME=3 ROTATE="0" MOREROWS="0"Label for OS/2VALIGN="TOP"COLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"1COLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 1COLNAME=3 ROTATE="0" MOREROWS="0"CLASS=DISKWSOS2_1COLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"2COLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 2COLNAME=3 ROTATE="0" MOREROWS="0"CLASS=DISKWSOS2_2COLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"3COLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 3COLNAME=3 ROTATE="0" MOREROWS="0"CLASS=DISKWSOS2_3COLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"4COLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows Disk 4COLNAME=3 ROTATE="0" MOREROWS="0"CLASS=DISKOSUTIL1COLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"5COLNAME=2 ROTATE="0" MOREROWS="0"CLASS=DISKNetWare Client for DOS and MS Windows ODI LAN driversCOLNAME=3 ROTATE="0" MOREROWS="0"CLASS=DISKOS2DOC_XCLASS=DISK1 = English  2 = French  3 = German  4 = Italian  5 = SpanishCOLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"6COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"CLASS=DISKWSDRV_1COLNAME=1 ALIGN="CENTER" ROTATE="0" MOREROWS="0"7COLNAME=2 ROTATE="0" MOREROWS="0"COLNAME=3 ROTATE="0" MOREROWS="0"VLMBOOT (optional)PERFORMANCE="REQUIRED"Refer to 
IDREF="FM32801"Chapter 6, "Install NetWare Clients," on page 263 to install your NetWare client workstations.
PAGENUM=298 ID="BP299"RENDERAS="SECT1"ID="FM95788"Create Macintosh Client DiskettesFollow the procedures below to create a Macintosh Client installation diskette.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"From an existing Macintosh workstation, log in to the server containing the installation files.IDXID="w3303"BOOK="_idx" COLLECTION="nw41" TIDREF="i2290"
Before you can install the NetWare for Macintosh client software, you must prepare the files for installation.If NetWare for Macintosh was installed on the server, the installation utility copied the client software to the server in the form of a self-extracting archive (MACNDS.SEA) file
IDXID="w3304"BOOK="_idx" COLLECTION="nw41" TIDREF="i2292"
.If you are installing from a NetWare drive after installing NetWare for Macintosh, connect to the server with bindery services enabled. Log in as user SUPERVISOR with bindery services enabled. Next, mount the volume on which you installed the client installation files.PERFORMANCE="REQUIRED"Locate the correct self-extracting archive in the PUBLIC\MAC folder.The MAC folder inside the PUBLIC folder contains at least one language folder. Each language folder is named according to the language in which its user interface is presentedFor example, the archive of the English version of MacNDS is in the following location:
FORMAT="LINESPECIFIC"MOREINFO="NONE"SYS:PUBLIC\MAC\ENGLISH\MACNDS.SEALikewise, the German archive resides in this location:
FORMAT="LINESPECIFIC"MOREINFO="NONE"SYS:PUBLIC\MAC\DEUTSCH\MACNDS.SEAPERFORMANCE="REQUIRED"ID="FM30236"Double-click the MACNDS.SEA file for your language.A file dialog box appears, asking you where you want to put the extracted files. Select the default location to create a MACNDS folder within your language folder, or choose a different location if you want to store the extracted files elsewhere.
PAGENUM=299 ID="BP300"PERFORMANCE="REQUIRED"Copy the files from the server directory in which you extracted the MacNDS files to the 800KB floppy diskette.PERFORMANCE="REQUIRED"Rename the floppy diskette.The diskette should have the same name as the server directory containing the extracted MACNDS files (not the *.SEA files). This is the directory you created in 
IDREF="FM30236"Step 3.If you do not name the diskette correctly, the installer will not work correctly. You will get an error message stating that you need to insert the correct diskette.LABEL="E"PAGENUM=301 ID="BP301"Install Using RCONSOLEThe IDXID="w3305"BOOK="_idx" COLLECTION="nw41" TIDREF="i3677"IDXID="w3306"BOOK="_idx" COLLECTION="nw41" TIDREF="i1825"
RCONSOLE utility allows network supervisors to perform server console actions from a DOS client, or from a PC using a IDXID="w3307"BOOK="_idx" COLLECTION="nw41" TIDREF="i2487"
modem.You can use the RCONSOLE utility on a DOS client toMARK=BULLETInstall a NetWare 4TM server remotely through either a LAN, WAN, or modem.Install several NetWare 4 servers from a single remote location.LABEL="E-1" FLOAT="0"Remote Installation Using RCONSOLEFILEREF="n41i102a.tif"PAGENUM=302 ID="BP302"RENDERAS="SECT1"Hardware Configuration RequirementsYou must have the followingIDXID="w3308"BOOK="_idx" COLLECTION="nw41" TIDREF="i1641"
 hardware configuration before installing using RCONSOLE:MARK=CHECKBOXAn existing DOS client with an installed CD-ROM drive.One or more computers (which will be referred to as "new servers") meeting all of the hardware requirements listed under IDREF="FM69886""Hardware Requirements" on page 2.Each computer connected to the DOS client via a LAN, WAN, or modem.RENDERAS="SECT1"Prerequisite TasksMARK=CHECKBOXPlan your Directory tree. See BOOK="getstenu" COLLECTION="nw41"Introduction to NetWare Directory Services for guidelines and suggestions.If the new server has never been a server before, complete the tasks explained in IDREF="FM93569"Chapter 1, "Prepare Your Site and Equipment," on page 1.Run the new server's Setup program and set its time to the exact local time. (The time synchronization feature in NetWare Directory ServicesTM uses the computer's time setting.)If necessary, partition and format your hard disk. Boot from the NetWare®CLASS=DISK License diskette; type FDISK and follow the screen prompts to partition the hard disk. Reboot the machine and type FORMAT to format the partition.We suggest you create a 15MB DOS partition. This will store the NetWare 4.1 server boot files.Reformatting your hard disk erases all stored files. Be sure to back up your hard disk prior to partitioning and formatting.PAGENUM=303 ID="BP303"RENDERAS="SECT1"Necessary ResourcesMARK=CHECKBOXThe NetWare 4.1 CLASS=DISKLicense disketteThe NetWare 4.1 Operating System CD-ROMTwo high-density floppy diskettesRENDERAS="SECT1"Copy Files For the New ServerFollow the procedures below to copy the IDXID="w3309"BOOK="_idx" COLLECTION="nw41" TIDREF="i843"
files needed by the new server.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"At the DOS workstation, insert the CLASS=DISKNetWare 4.1 Operating System CD-ROM into the CD-ROM drive.PERFORMANCE="REQUIRED"Change to the BOOT directory of the CD-ROM.For example, if the CD-ROM drive were drive D:, the path would be:
FORMAT="LINESPECIFIC"MOREINFO="NONE"D:\NW410\BOOTPERFORMANCE="REQUIRED"ID="FM64893"Copy the following files onto the floppy diskettes:
MARK=BULLETRSPX.NLM (for a remote installation from a workstation) or RS232.NLM (required only for an installation via modem)REMOTE.NLMNWSNUT.NLMINSTALL.NLMCLIB.NLM (required only for an installation using a modem)STREAMS.NLM (required only for an installation using a modem)PERFORMANCE="REQUIRED"Change to the NATIVE subdirectory.For example:
FORMAT="LINESPECIFIC"MOREINFO="NONE"D:\NW410\BOOT\NATIVE
PAGENUM=304 ID="BP304"PERFORMANCE="REQUIRED"Copy the SERVER.EXE file onto one of the diskettes.PERFORMANCE="REQUIRED"(Conditional) If you will be installing over a modem, change to the SYSTEM directory.For example, if the CD-ROM drive were drive D:, the path would be:
FORMAT="LINESPECIFIC"MOREINFO="NONE"D:\NW410\SYSTEMPERFORMANCE="REQUIRED"(Conditional) If you will be installing over a modem, copy the AIO.NLM file (and any communications port driver) on one of the floppy diskettes.PERFORMANCE="REQUIRED"Change to the PREINST subdirectory.For example, if the CD-ROM drive were drive D:, the path would be:
FORMAT="LINESPECIFIC"MOREINFO="NONE"D:\NW410\SYSTEM\PREINSTPERFORMANCE="REQUIRED"Copy the ICMD.NLM file onto one of the two diskettes.PERFORMANCE="REQUIRED"Copy applicable topology files.The remaining files to be copied vary, depending on your topology and network board.For example, if you were using an Ethernet topology and an NE2000TM LAN driver, you would copy the following files:
MARK=BULLETNE2000.LAN from the NW410\LANDRV subdirectoryMSM.NLM and ETHERTSM.NLM from the NW410\LANDRV\CORE subdirectoryPAGENUM=305 ID="BP305"RENDERAS="SECT1"Install Files and Configure the New ServerFollow the procedures below to install the files on the new server, and to prepare the new server for remote installation from the DOS client.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"On each new server, create a new directory and name it "NWSERVER."PERFORMANCE="REQUIRED"Change to the NWSERVER subdirectory.PERFORMANCE="REQUIRED"Insert the diskettes into the server diskette drive and copy the files that you copied in 
IDREF="FM64893"Step 3 on page 303 to the NWSERVER directory.PERFORMANCE="REQUIRED"Type 
FORMAT="LINESPECIFIC"MOREINFO="NONE"SERVER MOREINFO="NONE"<Enter>You are prompted to enter a server name.PERFORMANCE="REQUIRED"ID="FM83150"Enter a name for this server and press 
MOREINFO="NONE"<Enter>.You are prompted for an IPX internal network number.PERFORMANCE="REQUIRED"Enter a an IPX internal network number and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"(Conditional) If you are installing through an SPX connection (rather than through a modem), load your LAN driver.For example, to load the NE2000 LAN driver, you would type:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD NE2000 MOREINFO="NONE"<Enter>You are prompted for the I/O port number.PERFORMANCE="REQUIRED"(Conditional) If you are installing through an SPX connection, type the LAN driver I/O port number.For example, if your LAN driver is configured for I/O port 300, you would type:
FORMAT="LINESPECIFIC"MOREINFO="NONE"300 MOREINFO="NONE"<Enter>
PAGENUM=306 ID="BP306"PERFORMANCE="REQUIRED"(Conditional) If you are installing through an SPX connection, type the LAN driver interrupt.For example, if your LAN driver is configured for interrupt 3, you would type:
FORMAT="LINESPECIFIC"MOREINFO="NONE"3 MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"(Conditional) If you are installing through an SPX connection, bind the protocol to the LAN driver.For example, for an IPXTM protocol and an NE2000 LAN driver, you would type:
FORMAT="LINESPECIFIC"MOREINFO="NONE"BIND IPX NE2000 NET=IPX external network number MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Load the communications protocol.For example, if your new server is connected to the DOS client via a LAN, or a WAN fiber optic link, you would load the RSPX communications protocol. Type:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD RSPX MOREINFO="NONE"<Enter>If your new server is connected to the DOS client via a a modem, you would load the RS-232 communications protocol. Type:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD RS232 MOREINFO="NONE"<Enter>After loading the communications protocol, you are prompted for a remote console password.PERFORMANCE="REQUIRED"ID="FM79466"Type a remote console password and press 
MOREINFO="NONE"<Enter>.This password will be used by the DOS client to establish a remote connection.
PAGENUM=307 ID="BP307"RENDERAS="SECT1"Configure the DOS Client and Install the ServerFollow the procedures below to configure your DOS client to communicate with the new server and then install the NetWare 4.1 server.RENDERAS="SECT2"ProcedurePERFORMANCE="REQUIRED"At the DOS client, load the Link Support Layer by typing:FORMAT="LINESPECIFIC"MOREINFO="NONE"LSL MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Load your LAN driver.For example, to load the NE2000 LAN driver, type:
FORMAT="LINESPECIFIC"MOREINFO="NONE"NE2000 MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Load IPXODI by typing:
FORMAT="LINESPECIFIC"MOREINFO="NONE"IPXODI MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Insert the 
CLASS=DISKNetWare 4.1 Operating System CD-ROM.PERFORMANCE="REQUIRED"Change to the desired language subdirectory under the INSTALL directory.For example, if the CD-ROM drive were drive D:, the path would be:
FORMAT="LINESPECIFIC"MOREINFO="NONE"D:\NW410\INSTALL\LANGUAGEPERFORMANCE="REQUIRED"Type 
FORMAT="LINESPECIFIC"MOREINFO="NONE"RCONSOLE MOREINFO="NONE"<Enter>The "Connection Type" menu appears.PERFORMANCE="REQUIRED"From the "Connection Type" menu, select the applicable connection type and press 
MOREINFO="NONE"<Enter>.For example, if you were connected to the new server via a LAN, you would select "SPX."The "Available Servers" menu appears.
PAGENUM=308 ID="BP308"PERFORMANCE="REQUIRED"Highlight the server name you entered in 
IDREF="FM83150"Step 5 on page 305 and press 
MOREINFO="NONE"<Enter>.You are prompted for a password.PERFORMANCE="REQUIRED"Enter the remote console password you entered in 
IDREF="FM79466"Step 12 on page 306 and press 
MOREINFO="NONE"<Enter>.PERFORMANCE="REQUIRED"Load INSTALL.NLM by typing
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>The following menu appears. LABEL="E-2" FLOAT="0"The "Installation Options" MenuFILEREF="n41in16a.tif"PERFORMANCE="REQUIRED"Choose "Server Options" and press 
MOREINFO="NONE"<Enter>.The "Server Installation Options" menu appears.PERFORMANCE="REQUIRED"From the "Server Installation Options" menu, choose "Install a New 4.1 Server" and press 
MOREINFO="NONE"<Enter>.An information screen appears which, in this case, is not applicable.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<Enter> to continue.A screen appears indicating the default path from which NetWare 4.1 files will be installed.PERFORMANCE="REQUIRED"Press 
MOREINFO="NONE"<F4> to select a remote client as the source.
PAGENUM=309 ID="BP309"A screen appears for you to enter the path to the remote client.PERFORMANCE="REQUIRED"Enter the path to the CD-ROM drive of the DOS client.For example, if the CD-ROM drive were drive D:, the path would be:
FORMAT="LINESPECIFIC"MOREINFO="NONE"D:\NW410\INSTALL\LANGUAGE MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Continue the installation by following the procedures under 
IDREF="FM65610""Load the Disk Drivers and CD-ROM Drivers" on page 83 (in 
IDREF="FM44025"Chapter 3 "Custom Installation."Since the LAN driver is already loaded and bound, when prompted for the LAN driver, press MOREINFO="NONE"<F10> to skip that procedure and continue.LABEL="F"PAGENUM=311 ID="BP310"ID="FM28651"Red Box CD-ROM DriversThe following list defines the IDXID="w3310"BOOK="_idx" COLLECTION="nw41" TIDREF="i603"IDXID="w3311"BOOK="_idx" COLLECTION="nw41" TIDREF="i3714"
CD-ROM drivers and their load order needed to enable a CD-ROM device to mount a CD-ROM as a NetWare® volume.The list may or may not be complete, as drivers may have been added to the Novell® Red BoxTM (NetWare 4.1 product package) after the list was created.An updated list can be obtained via Novell's faxback server by calling 1-800-NETWARE and requesting document #1344.Please note that this list simply defines the IDXID="w3312"BOOK="_idx" COLLECTION="nw41" TIDREF="i603"
load order of drivers included in the Red Box. The configurations listed may not work in every possible hardware configuration. Novell has made every effort to ensure the accuracy of the document and the information contained herein.LABEL="F-1" PGWIDE=0 TOCENTRY="1" Red Box CD-ROM Drivers and Load OrderCOLS=3 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="8*"COLNAME=2 COLWIDTH="8*"COLNAME=3 COLWIDTH="8*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"ManufacturerCOLNAME=2 ROTATE="0" MOREROWS="0"AdapterCOLNAME=3 ROTATE="0" MOREROWS="0"Driver load orderVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"AdaptecCOLNAME=2 ROTATE="0" MOREROWS="0"AHA-1510ACOLNAME=3 ROTATE="0" MOREROWS="0"AHA1510.DSKASPITRAN.DSKASPICD.DSKNWPA.NLMCDROM.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"AdaptecCOLNAME=2 ROTATE="0" MOREROWS="0"AHA-1522ACOLNAME=3 ROTATE="0" MOREROWS="0"AHA1520.DSKASPITRAN.DSKASPICD.DSKNWPA.NLMCDROM.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"AdaptecCOLNAME=2 ROTATE="0" MOREROWS="0"AHA-1542CFAHA-174xAS6*AHA-174xAS200*AHA-174xA**Standard ModeCOLNAME=3 ROTATE="0" MOREROWS="0"AHA1540.DSKASPITRAN.DSKASPICD.DSKNWPA.NLMCDROM.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"AdaptecCOLNAME=2 ROTATE="0" MOREROWS="0"AHA-1640S6COLNAME=3 ROTATE="0" MOREROWS="0"AHA1640.DSKASPITRAN.DSKASPICD.DSKNWPA.NLMCDROM.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"AdaptecCOLNAME=2 ROTATE="0" MOREROWS="0"AHA-1742AS6*AHA-174xAS6*AHA-174xAS200AHA-174xA**Enhanced ModeCOLNAME=3 ROTATE="0" MOREROWS="0"AHA1740.DSKASPITRAN.DSKASPICD.DSKNWPA.NLMCDROM.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"AdaptecCOLNAME=2 ROTATE="0" MOREROWS="0"AHA-2742AAHA-2742A-TAHA-2742TCOLNAME=3 ROTATE="0" MOREROWS="0"AIC7770.DSKASPITRAN.DSKASPICD.DSKNWPA.NLMCDROM.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"AlwaysCOLNAME=2 ROTATE="0" MOREROWS="0"IN-2000COLNAME=3 ROTATE="0" MOREROWS="0"IN2000.DSKADAASPI.DSKNWPA.NLMCDROM.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"AlwaysCOLNAME=2 ROTATE="0" MOREROWS="0"AL-6000COLNAME=3 ROTATE="0" MOREROWS="0"AL6000.DSKADAASPI.DSKNWPA.NLMCDROM.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"AlwaysCOLNAME=2 ROTATE="0" MOREROWS="0"AL-7000COLNAME=3 ROTATE="0" MOREROWS="0"AL7000.DSKADAASPI.DSKNWPA.NLMCDROM.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"BuslogicCOLNAME=2 ROTATE="0" MOREROWS="0"BT-542/545BT-640/646BT-742/747BT-445SBT-946CCOLNAME=3 ROTATE="0" MOREROWS="0"BT4X.DSKNWPA.NLMCDROM.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"DPTCOLNAME=2 ROTATE="0" MOREROWS="0"PM2012BPM2022/9XPM2122/9XCOLNAME=3 ROTATE="0" MOREROWS="0"PM12NW40.DSKNWPA.NLMCDROM.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"DPTCOLNAME=2 ROTATE="0" MOREROWS="0"PM2011BPM2021/9XCOLNAME=3 ROTATE="0" MOREROWS="0"PM11NW40.DSKNWPA.NLMCDROM.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"DTCCOLNAME=2 ROTATE="0" MOREROWS="0"DTC 3290COLNAME=3 ROTATE="0" MOREROWS="0"DTC90AS4.DSKDTC90HD4.DSKASPICD.DSKNWPA.NLMCDROM.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"DTCCOLNAME=2 ROTATE="0" MOREROWS="0"DTC 3280COLNAME=3 ROTATE="0" MOREROWS="0"DTC80AS4.DSKDTC80HD4.DSKASPICD.DSKNWPA.NLMCDROM.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"Future DomainCOLNAME=2 ROTATE="0" MOREROWS="0"TMC-16XXMCS-600/700TMC3260COLNAME=3 ROTATE="0" MOREROWS="0"SIM18_4.DSKFUTXPT.DSKFUTD_4.DSKNWPA.NLMCDROM.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"Future DomainCOLNAME=2 ROTATE="0" MOREROWS="0"TMC-8XXCOLNAME=3 ROTATE="0" MOREROWS="0"SIM950_4.DSKFUTXPT.DSKFUTD_4.DSKNWPA.NLMCDROM.NLMCOLNAME=1 ROTATE="0" MOREROWS="0"MylexCOLNAME=2 ROTATE="0" MOREROWS="0"DAC960-3DAC960-5COLNAME=3 ROTATE="0" MOREROWS="0"DACNET4.DSKASPIDAC.DSKASPICD.DSKNWPA.NLMCDROM.NLMPAGENUM=314 ID="BP311"LABEL="G"PAGENUM=315 ID="BP312"ID="FM55488"TroubleshootingRENDERAS="SECT1"IDXID="w3313"BOOK="_idx" COLLECTION="nw41" TIDREF="i4582"IDXID="w3314"BOOK="_idx" COLLECTION="nw41" TIDREF="i4582"IDXID="w3315"BOOK="_idx" COLLECTION="nw41" TIDREF="i4582"
Server, IDXID="w3316"BOOK="_idx" COLLECTION="nw41" TIDREF="i1636"IDXID="w3317"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"IDXID="w3318"BOOK="_idx" COLLECTION="nw41" TIDREF="i4049"
Hard Disk, and IDXID="w3319"BOOK="_idx" COLLECTION="nw41" TIDREF="i4795"IDXID="w3320"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
Volume ProblemsServer and hard disk problems commonly occur during installation. Some problems and solutions are explained on the following pages.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="19*"COLNAME=2 COLWIDTH="6*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"SectionCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"General solutions to try firstCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM57253"316COLNAME=1 ROTATE="0" MOREROWS="0"Console commands cannot be entered at the server console or they do not function correctlyCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM72664"316COLNAME=1 ROTATE="0" MOREROWS="0"The server "hangs" after mounting the last volumeCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM80627"317COLNAME=1 ROTATE="0" MOREROWS="0"A hard disk cannot be accessedCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM25606"318COLNAME=1 ROTATE="0" MOREROWS="0"None of the volumes, including SYS:, was mountedCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM92370"319COLNAME=1 ROTATE="0" MOREROWS="0"The operating system reports disk errors when a volume is being mountedCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM98644"320COLNAME=1 ROTATE="0" MOREROWS="0"The operating system reports memory errors when a volume is being mountedCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM19345"321COLNAME=1 ROTATE="0" MOREROWS="0"A volume cannot be mounted because of corrupted directory tables or FATsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM40942"322COLNAME=1 ROTATE="0" MOREROWS="0"A volume cannot be mounted because a name space module was not loaded firstCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM23985"324COLNAME=1 ROTATE="0" MOREROWS="0"The keyboard locks while copying files from CD-ROMCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM82502"325PAGENUM=316 ID="BP313"RENDERAS="SECT2"ID="FM57253"General solutions to try firstIf the problem occurred after installation, it may indicate that the network was installed incorrectly.MARK=BULLETCheck all network boards for possible conflicting IDXID="w3321"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
address and I/O settings.Each component should be able to work as a standalone system. Remove all network boards in the server and boot DOS. Add each board one at a time and make sure that DOS still boots after each addition. Make sure that all cables are fastened securely to all network boards and network connectors, and that terminating resistors are installed correctly.RENDERAS="SECT2"ID="FM72664"
Console commands cannot be entered at the server console or they do not function correctlyIDXID="w3322"BOOK="_idx" COLLECTION="nw41" TIDREF="i801"RENDERAS="SECT3"Possible causesMARK=BULLETSome SET parameters can only be set in the STARTUP.NCF file.You are not at the system console.The server has been brought down.The server has failed ("hung").The IDXID="w3323"BOOK="_idx" COLLECTION="nw41" TIDREF="i4069"IDXID="w3324"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
SERVER.EXE file is corrupted.The NetWare® operating system has been configured incorrectly.RENDERAS="SECT3"Possible solutionsMARK=BULLETType the SET parameter in the STARTUP.NCF file and then bring the server down and back up.Make sure all cables are fastened securely to all network boards and network connectors. Check that terminating resistors are installed correctly.PAGENUM=317 ID="BP314"From a backup, or from the NetWare 4.1 Operating System CD-ROM, copy a new version of SERVER.EXE to the server boot directory. Have all users close their files and log out.Bring down the server, if possible. If not, wait a few minutes after all users have logged out; then reboot the server.Check your server worksheet for network board configurations (see the IDREF="FM65030"NetWare 4.1 Server Worksheet on IDREF="FM65030"page 175). Then check the actual hardware configuration on each network board in the server to make sure the two match.If your recorded network board configurations do not agree with the actual hardware configurations, reload the LAN driver with the correct parameters or change the hardware settings to match the LAN driver parameters.Check all IDXID="w3325"BOOK="_idx" COLLECTION="nw41" TIDREF="i2846"
network board settings for possible interrupt and I/O port conflicts. The server can boot up initially even if the interrupt on a network board is set incorrectly. The most common conflict occurs when a network board is set to interrupt 4 and a printer is connected to the server's serial port, which also uses interrupt 4. RENDERAS="SECT2"ID="FM80627"ID="FM85552"The server "hangs" after mounting the last volumeRENDERAS="SECT3"Possible causesMARK=BULLETThe server network board is not initializing when the server is brought up because the board is not installed or seated correctly.The IDXID="w3326"BOOK="_idx" COLLECTION="nw41" TIDREF="i2847"
server network board is not configured correctly.RENDERAS="SECT3"Possible solutions MARK=BULLETRun CONFIG at the server console to see what settings appear on the screen. Check the network board configurations of the boards in the server. Make sure the settings match.Make sure that all server and workstation IDXID="w3327"BOOK="_idx" COLLECTION="nw41" TIDREF="i2847"
network boards are seated properly and that cabling and connections are attached securely.PAGENUM=318 ID="BP315"Make sure that the terminators on cables have the right ohm rating and are installed correctly. The IBM* PC Cluster sends a broadcast message during initialization and hangs if the network is not cabled or terminated properly.Check the network boards in all workstations for correct node address settings.RENDERAS="SECT2"ID="FM25606"ID="FM82674"A IDXID="w3328"BOOK="_idx" COLLECTION="nw41" TIDREF="i1636"
hard disk cannot be accessedRENDERAS="SECT3"Possible causesMARK=BULLETThe disk driver has not been loaded.A hard disk is not installed or cabled correctly.The communication channel between the IDXID="w3329"BOOK="_idx" COLLECTION="nw41" TIDREF="i828"IDXID="w3330"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
controller interface board, the disk coprocessor board, and the hard disk is not functioning.The hard disk controller board is not terminated or addressed correctly.RENDERAS="SECT3"Possible solutionsMARK=BULLETMake sure the disk driver is loaded. At the console, type MODULES to view the loaded disk drivers. Check the cables between the hard disks and the controller boards. Be sure Pin 1 of each cable is attached to Pin 1 of each connector.Check the power cables and make sure they are seated correctly in the power sockets on the hard disks.Check the jumper settings on the disk coprocessor board (DCB), the controller board, and the hard disk. Refer to the hardware documentation for correct jumper settings.If you are using a DCB, run DISKSET to make sure the hardware configurations contained on the EEPROM chip on the disk coprocessor board match those for the hard disks in your server.Load INSTALL to check the NetWare disk partition and volume information on the hard disk. For details, see "BOOK="superenu" COLLECTION="nw41"Maintaining Volumes" in Chapter 7 of Supervising the Network.PAGENUM=319 ID="BP316"Make sure that each controller interface board connected to the same disk coprocessor board has its own valid address.RENDERAS="SECT2"ID="FM92370"None of the volumes, including SYS:, was 
mountedVolume SYS: is the backout volume for TTSTM (Transaction Tracking SystemTM). Volume SYS: also contains the NetWare system files and the NLMTM programs.If volume SYS: does not mount when the server is booted, the AUTOEXEC.NCF file does not execute, LAN drivers do not load, TTS can't be enabled, and the volume does not become part of the Directory tree.RENDERAS="SECT3"Possible causesMARK=BULLETVolume SYS: is corrupted.The hard disk containing volume SYS: has failed.The cable or power to the external hard disks has malfunctioned.RENDERAS="SECT3"Possible solutionsMARK=BULLETRun VREPAIR on volume SYS: (VREPAIR autoloads from the DOS partition).Check the cabling and power to the external hard disks. Replace any faulty components.Replace the hard disk containing volume SYS:.MARK=BULLETLoad INSTALL to create the partitions and volume SYS:.Restore the data from a backup copy.PAGENUM=320 ID="BP317"RENDERAS="SECT2"Some of the volumes mount, while others won'tRENDERAS="SECT3"Possible causeMARK=BULLETThe server does not have enough RAM.The disk driver for external drives may not be loaded.RENDERAS="SECT3"Possible solutionMARK=BULLETAdd more RAM.At the server console, type MODULES to see which drivers are loaded.RENDERAS="SECT2"ID="FM98644"The IDXID="w3331"BOOK="_idx" COLLECTION="nw41" TIDREF="i2775"IDXID="w3332"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
operating system reports disk errors when a volume is being mountedRENDERAS="SECT3"Possible causesMARK=BULLETThe server does not have enough memory to mount the volume.The operating system is experiencing directory sector mismatching. This mismatching can be caused if the media is defective or if the server is turned off without the DOWN command.RENDERAS="SECT3"Possible solutionsMARK=BULLETLoad MONITOR and check the status of the available cache buffers. If the cache buffers are fewer than 20%, add more memory to your server.Minor errors usually correct themselves through normal network use. For example, if a FAT entry is wrong, the entry is updated and corrected the next time it is written to. If errors do not correct themselves, run VREPAIR.Some problems may be corrected automatically by TTS.PAGENUM=321 ID="BP318"RENDERAS="SECT2"ID="FM19345"The IDXID="w3333"BOOK="_idx" COLLECTION="nw41" TIDREF="i2775"IDXID="w3334"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
operating system reports memory errors when a volume is being mountedRENDERAS="SECT3"Possible causesMARK=BULLETVolumes take more memory to mount than they require after being mounted because the mounting process performs consistency checks (for example, the duplicate copies of all the tables are checked). Volumes and directory entries grow dynamically. Thus, if your server is using most of the RAM (file cache buffers are close to 20% of the memory) and you dismount a volume, you may not be able to remount the volume unless additional memory is available.Each additional name space support that you add to a volume increases the size of the FATs and DETs. Adding name space support can cause the tables to grow so large that the server does not have enough RAM to mount the volume.RENDERAS="SECT3"Possible solutions MARK=BULLETLoad MONITOR and check the status of the available cache buffers. If the cache buffers are fewer than 20%, add more RAM to your server.Free up memory by unloading resources.Streamline the directory structure. Every subdirectory takes at least one directory block (by default, a 4KB block of memory). Thus, subdirectories with only one file require as much memory as directories with 32 files. If you combine directories so that most directories have about 32 files, and then purge the deleted subdirectories and files, you will free up memory.Calculate how much memory you need and add memory to the server. View the current volume size with INSTALL. (See "BOOK="superenu" COLLECTION="nw41"Modifying the Size of a Volume" in Chapter 7 of Supervising the Network.)See Appendix A, IDREF="FM69155""Calculate RAM Requirements," on page 271 for a formula for estimating the total amount of server memory needed.For a more accurate assessment of available RAM, load MONITOR, select "Resource Utilization" from the "Available Options" menu, and view the "Cache Buffers" setting in the "Server Memory Statistics" screen. If the percentage is below 20%, you should add more memory.PAGENUM=322 ID="BP319"Remove the recently added name space support. This is a destructive step that destroys all the extended file information. Before taking this step, try to free up enough memory so that the volume mounts and you can back up the data. Have all users log out, and then unload all modules except the volume's disk drivers. Dismount any mounted volumes.To remove the name space, load VREPAIR and choose the "Remove Name Space Support From The Volume" and "Write All Directory and FAT Entries Out to Disk" options. Then run VREPAIR on the volume that would not mount. RENDERAS="SECT2"ID="FM40942"A volume cannot be mounted because of corrupted IDXID="w3335"BOOK="_idx" COLLECTION="nw41" TIDREF="i1054"IDXID="w3336"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
Directory Entry tables (DETs) or IDXID="w3337"BOOK="_idx" COLLECTION="nw41" TIDREF="i1450"IDXID="w3338"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
File Allocation Tables (FATs)RENDERAS="SECT3"Possible causesThe following can cause mismatches in the duplicate copies of the 
FAT and DET:MARK=BULLETA power failure occurs and the server is not brought down with the DOWN command. A hard disk fails.A disk channel error occurs.A volume is not dismounted with the DISMOUNT command. Directory information in cache is not completely written to disk.PAGENUM=323 ID="BP320"RENDERAS="SECT3"Possible solutionsComplete one or more of the following:MARK=BULLETRun VREPAIR.Add a UPS system so that the server is brought down automatically when a power failure occurs.Replace faulty disks or controllers.If the volume resides on mirrored hard disks, use FILER to salvage the data on one of the drives.Use INSTALL to unmirror the hard disks (select the hard disk you think is least reliable and delete it from the mirroring list). Then run VREPAIR on the volume and mount the volume.If the volume still does not mount or the data shows some corruption, read the next suggestion before remirroring the hard disks.If the volume resides on mirrored hard disks, salvage the data on both hard disks.Use INSTALL to unmirror the hard disks and to salvage the orphaned (Out Of Sync) hard disk as a new volume. Run VREPAIR on both the old and the new volumes.Mount both volumes and compare the files. Use INSTALL to delete the volume that has the least useful information; rename the salvaged volume, if necessary. Then use INSTALL to remirror the hard disks.PAGENUM=324 ID="BP321"RENDERAS="SECT2"ID="FM23985"A volume cannot be mounted because a name space module was not loaded firstRENDERAS="SECT3"Possible causesOnce a volume has been configured to support more than the DOS naming convention, the loadable name space module must be loaded before the volume can be mounted. One of the following has probably occurred:MARK=BULLETThe command to load the name space module is not in the STARTUP.NCF file.The module to load the name space has not been copied to the boot directory of the server. RENDERAS="SECT3"Possible solutionsMARK=BULLETLoad the name space module; then mount the volume. Copy the name space module to the server boot directory and add the load command to the STARTUP.NCF file. The module then loads automatically whenever the server is booted.Delete the name space configuration from the volume. This is a destructive step that destroys all of the extended file information. Back up all non-DOS files. Then load VREPAIR and choose the "Remove All Name Space Entries" and "Write Changes Immediately To Disk" options. Then run VREPAIR on the volume.PAGENUM=325 ID="BP322"RENDERAS="SECT2"ID="FM82502"The keyboard locks while copying files from CD-ROMRENDERAS="SECT3"Possible causeIf you have a CD-ROM device that shares a SCSI bus with a disk subsystem containing volumes to which NetWare installation files are copied (typically volume SYS:), your IDXID="w3339"BOOK="_idx" COLLECTION="nw41" TIDREF="i2016"
keyboard may lock up while loading drivers or copying files to the volume.IDREF="FM61296"Figure G-1 shows possible configuration conflicts.LABEL="G-1" FLOAT="0"ID="FM61296"SCSI Adapter ConflictsFILEREF="n41in50a.tif"PAGENUM=326 ID="BP323"RENDERAS="SECT3"SolutionRemove the CD-ROM device drivers that you used to set up the CD-ROM drive as a DOS device from your CONFIG.SYS file. This will avoid possible conflicts when the NetWare 4.1 CLASS=DISKOperating System CD-ROM is mounted as a NetWare volume.RENDERAS="SECT4"ProcedurePERFORMANCE="REQUIRED"ID="FM33629"Press MOREINFO="NONE"<Alt>+<Esc> until you are at the console prompt (:).PERFORMANCE="REQUIRED"Type 
FORMAT="LINESPECIFIC"MOREINFO="NONE"DOWN MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Then type
FORMAT="LINESPECIFIC"MOREINFO="NONE"EXIT MOREINFO="NONE"<Enter>PERFORMANCE="REQUIRED"Using a text editor, remove the CD-ROM device drivers from your CONFIG.SYS file.PERFORMANCE="REQUIRED"Save the updated CONFIG.SYS file.PERFORMANCE="REQUIRED"Using a text editor, remove any references to the CD-ROM drivers from your AUTOEXEC.BAT file.PERFORMANCE="REQUIRED"Save the updated AUTOEXEC.BAT file.PERFORMANCE="REQUIRED"Reboot the server by pressing 
MOREINFO="NONE"<Ctrl>+<Alt>+<Del>.PERFORMANCE="REQUIRED"(Conditional) If the server doesn't boot automatically from the AUTOEXEC.BAT file, change to the subdirectory with your SERVER.EXE (this is NWSERVER.EXE in the "Simple Installation") and other boot files, and type
FORMAT="LINESPECIFIC"MOREINFO="NONE"CD\NWSERVER MOREINFO="NONE"<Enter> 
SERVER 
MOREINFO="NONE"<Enter> 
PAGENUM=327 ID="BP324"PERFORMANCE="REQUIRED"(Conditional) If you are using ASPI device drivers (for example, for an Adaptec controller), you need to perform one of the following commands:
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD AHA1540 MOREINFO="NONE"<Enter> 
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD ASPICD MOREINFO="NONE"<Enter> or
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD CDNASPI MOREINFO="NONE"<Enter> PERFORMANCE="REQUIRED"At the console, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD NWPA MOREINFO="NONE"<Enter> PERFORMANCE="REQUIRED"At the console, type the following
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD CDROM MOREINFO="NONE"<Enter> 
CD MOUNT NW410 
MOREINFO="NONE"<Enter> PERFORMANCE="REQUIRED"At the console, type
FORMAT="LINESPECIFIC"MOREINFO="NONE"LOAD INSTALL MOREINFO="NONE"<Enter>
PAGENUM=328 ID="BP325"RENDERAS="SECT1"IDXID="w3340"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
Communication ProblemsIDXID="w3341"BOOK="_idx" COLLECTION="nw41" TIDREF="i698"
Communication problems are related to network boards, LAN drivers, network performance, and server/workstation communications, as well as to internetwork communications. Some problems and solutions are explained on the following pages.COLS=2 CHAROFF="50" CHAR="" ALIGN="LEFT"COLNAME=1 COLWIDTH="19*"COLNAME=2 COLWIDTH="6*"VALIGN="BOTTOM"COLNAME=1 ROTATE="0" MOREROWS="0"SectionCOLNAME=2 ROTATE="0" MOREROWS="0"PageVALIGN="TOP"COLNAME=1 ROTATE="0" MOREROWS="0"Widespread problemsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM69129"329COLNAME=1 ROTATE="0" MOREROWS="0"The server does not boot after a network board was installedCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM64780"331COLNAME=1 ROTATE="0" MOREROWS="0"The server cannot be found by the workstations on the networkCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM92868"331COLNAME=1 ROTATE="0" MOREROWS="0"Servers do not recognize each other on the networkCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM55217"333COLNAME=1 ROTATE="0" MOREROWS="0"Responses from the server are noticeably slowCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM40477"334COLNAME=1 ROTATE="0" MOREROWS="0"Users can log in, but periodically workstations lose their connections to the serverCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM67652"336COLNAME=1 ROTATE="0" MOREROWS="0"ARCnet-specific problemsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM25144"337COLNAME=1 ROTATE="0" MOREROWS="0"Ethernet-specific problemsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM37644"339COLNAME=1 ROTATE="0" MOREROWS="0"Token Ring-specific problemsCOLNAME=2 ROTATE="0" MOREROWS="0"IDREF="FM22161"340PAGENUM=329 ID="BP326"RENDERAS="SECT2"ID="FM69129"Widespread problemsRENDERAS="SECT3"Probable causesIf a problem occurs simultaneously on several workstations, it is probably a result of one of the following:MARK=BULLETThe server IDXID="w3342"BOOK="_idx" COLLECTION="nw41" TIDREF="i2847"
network board is not seated or configured correctly.The network board cable from the server is faulty.IDXID="w3343"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
Cabling on the network is faulty.The connector closest to the server is faulty.The IDXID="w3344"BOOK="_idx" COLLECTION="nw41" TIDREF="i3935"
RX-NetTM active hub is off. The correct Ethernet IDXID="w3345"BOOK="_idx" COLLECTION="nw41" TIDREF="i1571"
frame type has not been specified. NetWare 4.1 defaults to frame type 802.2.The repeater is off or nonfunctional.The IDXID="w3346"BOOK="_idx" COLLECTION="nw41" TIDREF="i561"
cabling is not terminated properly.Volume SYS: is not mounted.IDXID="w3347"BOOK="_idx" COLLECTION="nw41" TIDREF="i1987"IDXID="w3348"BOOK="_idx" COLLECTION="nw41" TIDREF="i4582"
ISA disk controller boards installed in EISA machines have not been configured.RENDERAS="SECT3"Possible solutionsMARK=BULLETCheck all hubs and repeaters to make sure they are on.Check the cables for proper termination.Make sure the server network board is seated properly.Replace the server network board with a board that works correctly. Make sure the new board has the same jumper settings.Run VOLUMES at the server console. If volume SYS: is not mounted, mount it. The server does not broadcast to the network until volume SYS: is mounted.PAGENUM=330 ID="BP327"Run CONFIG at the server console to check the configuration of the IDXID="w3349"BOOK="_idx" COLLECTION="nw41" TIDREF="i2847"
network boards. Then bring down the server, turn off the power, and check the actual network board settings: MARK=BULLETMake sure all settings agree with the settings used to load the driver. If you load the driver with an interrupt that conflicts with the board's setting, the network board cannot broadcast on the network.Make sure the node address on the board is a legal address. (Addresses 0 and FFFFFFFFFFFF are reserved; do not use them.)Run CONFIG at the server console to make sure each IDXID="w3350"BOOK="_idx" COLLECTION="nw41" TIDREF="i2847"
network board has a LAN protocol bound to it. Network boards cannot broadcast without a protocol.Run NLIST at a workstation, if possible, to check node addresses. Each node address on the network should be unique. Sometimes you can find the problem by turning off all workstations and turning them on one at a time.Have a user log in to the network from a workstation. Load MONITOR and choose "Connection Information" from the "Available Options" menu.If the "Active Connections" list shows the user's login name, the server is receiving and responding to the workstation's request.If the workstation receives a "Server cannot be found" error, make sure the server and workstation are using the same frame type.Replace segments of cable and cabling connections until communication is restored.PAGENUM=331 ID="BP328"RENDERAS="SECT2"ID="FM64780"The server does not boot after a network board is installedRENDERAS="SECT3"Possible causesMARK=BULLETThe IDXID="w3351"BOOK="_idx" COLLECTION="nw41" TIDREF="i2847"
network board is not attached properly to the cable.The IDXID="w3352"BOOK="_idx" COLLECTION="nw41" TIDREF="i774"IDXID="w3353"BOOK="_idx" COLLECTION="nw41" TIDREF="i4050"IDXID="w3354"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"IDXID="w3355"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
hardware conflicts with other boards, the monitor board, or ports in the server.The IDXID="w3356"BOOK="_idx" COLLECTION="nw41" TIDREF="i2847"
network board is faulty.RENDERAS="SECT3"Possible solutionsMARK=BULLETCable the network board to at least one workstation and check the termination.Make a list of all I/O ports, interrupts, and memory addresses used by the equipment. Use the IDREF="FM65030"NetWare 4.1 Server Worksheet on IDREF="FM65030"page 175 to record the information.Also do the following to identify potential conflicts:MARK=BULLETCheck the documentation that came with the computer and all installed hardware components. Make sure no two pieces of hardware are using the same I/O port, interrupt, or memory address.Make sure that the memory range for the I/O ports and memory addresses do not overlap. If there are conflicts, reconfigure the equipment so that no conflicts exist.RENDERAS="SECT2"ID="FM92868"The server cannot be found by the workstations on the networkRENDERAS="SECT3"Possible causesMARK=BULLETThe server's IDXID="w3357"BOOK="_idx" COLLECTION="nw41" TIDREF="i2847"
network board is not initializing when the server is brought up because it is not configured correctly or it has failed.The server is anticipating the wrong IDXID="w3358"BOOK="_idx" COLLECTION="nw41" TIDREF="i1571"
frame type. NetWare 4.1 uses Ethernet 802.2 as the default frame type for Ethernet LAN drivers that were loaded at the system console. Workstations running earlier versions of NetWare may be using Ethernet 802.3.PAGENUM=332 ID="BP329"Address or interrupt conflicts exist between two boards inside the server or between a board and the computer's hardware.The server does not have enough IDXID="w3359"BOOK="_idx" COLLECTION="nw41" TIDREF="i549"IDXID="w3360"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"IDXID="w3361"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
packet receive IDXID="w3362"BOOK="_idx" COLLECTION="nw41" TIDREF="i3183"
buffers.A IDXID="w3363"BOOK="_idx" COLLECTION="nw41" TIDREF="i3609"IDXID="w3364"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
protocol (such as IDXID="w3365"BOOK="_idx" COLLECTION="nw41" TIDREF="i1950"
IPXTM) is not bound to the network board.The IDXID="w3366"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
cabling is too close to sources of interference.Volume SYS: is not mounted.RENDERAS="SECT3"Possible solutionsMARK=BULLETMake sure all network connectors (including transceivers and repeaters) are installed and the cable is attached securely.Make sure all network boards are seated firmly and the cabling connections are in place.Make sure the network cable is IDXID="w3367"BOOK="_idx" COLLECTION="nw41" TIDREF="i561"
terminated properly. Many network boards send a broadcast message during initialization and will hang if the network is not cabled or terminated properly.Check cabling for interference from fluorescent lights, microwaves, radar, X rays, and copy machines. Either move the cable or shield it from the source of interference.Run VOLUMES at the server console to ensure that volume SYS: is mounted. Volume SYS: must be mounted before the server can advertise its name to the network.Run CONFIG at the server console to see what settings appear on the screen. Then check network board configurations in the server. Be sure the network board configurations match the settings that appear when you run CONFIG.Check the workstation frame types to see that they match those of the server.Check node address settings on all server and workstation network boards. Each address should be unique.PAGENUM=333 ID="BP330"Check all IPX internal and external network numbers. Each server and cabling system should have a unique IPX external network number.Make sure no two boards in the server are using the same I/O port, memory address, or interrupt.Bind the LAN driver (TRXNET, NE1000TM, TOKEN, etc.) to IPX (or another communication protocol).If you have a lot of network traffic, increase the maximum number of packet receive IDXID="w3368"BOOK="_idx" COLLECTION="nw41" TIDREF="i549"
buffers. (See "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.)RENDERAS="SECT2"ID="FM55217"Servers do not recognize each other on the networkRENDERAS="SECT3"Possible causesMARK=BULLETThe hardware IDXID="w3369"BOOK="_idx" COLLECTION="nw41" TIDREF="i2789"
settings in the server are incorrect.IDXID="w3370"BOOK="_idx" COLLECTION="nw41" TIDREF="i1931"
The IPX internal/external network numbers conflict.The NetWare Directory database is corrupted. Frame types are different.The server could have RESTRICT.NLM loaded.The router could be filtering out the IPX external network number.RENDERAS="SECT3"Possible solutionsMARK=BULLETRun CONFIG at the server console to see what settings appear on the screen. Then check network board configurations in the server. Be sure the network board configurations match the settings that appear when you run CONFIG.Check the IPX internal network number for the server and the IPX external network number for the cabling.When multiple servers share the same cabling system (called a multiserver network), all servers must have the same IPX external network number. However, the servers must have unique IPX internal network numbers and unique node numbers.PAGENUM=334 ID="BP331"When network cabling systems are connected through routers (internal or external), each cabling system must have a unique IPX external network number. NetWare 4TM servers must also have a unique IPX internal network number apart from the cabling.The unique IPX external network number is the first item read in a packet sending/receiving interaction.Reset the router with the RESET ROUTER console command.Check the cabling system for faulty termination.Bring down all servers except one. Reset its router with RESET ROUTER. Bring up each server, one at a time, establishing communications with it before bringing up the next one. Run DISPLAY NETWORKS to check for duplicate IPX external network numbers as each server is booted.Run DSREPAIR.Add the server to the Restrict list.Load FILTCFG.NLM at each server and verify that SAP traffic is being routed.RENDERAS="SECT2"ID="FM40477"Responses from the server are noticeably slowRENDERAS="SECT3"Possible causesMARK=BULLETThe workstation IDXID="w3371"BOOK="_idx" COLLECTION="nw41" TIDREF="i2847"
network board is slow or faulty.Network IDXID="w3372"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
cabling is faulty.The server network board is slow or faulty.Too many users are using the network.The server IDXID="w3373"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
speed is not set to the highest speed.The server hard disk is slow or faulty.The server is low on memory.The volume has too many deleted files that have not been purged.PAGENUM=335 ID="BP332"Network IDXID="w3374"BOOK="_idx" COLLECTION="nw41" TIDREF="i2888"IDXID="w3375"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
traffic is extremely high.The cabling system is experiencing too much IDXID="w3376"BOOK="_idx" COLLECTION="nw41" TIDREF="i1850"IDXID="w3377"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
interference.A hard disk has failed or is failing.IDXID="w3378"BOOK="_idx" COLLECTION="nw41" TIDREF="i1839"
Insufficient directory IDXID="w3379"BOOK="_idx" COLLECTION="nw41" TIDREF="i549"IDXID="w3380"BOOK="_idx" COLLECTION="nw41" TIDREF="i1045"IDXID="w3381"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"IDXID="w3382"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
buffers, IDXID="w3383"BOOK="_idx" COLLECTION="nw41" TIDREF="i572"
cache buffers, or IDXID="w3384"BOOK="_idx" COLLECTION="nw41" TIDREF="i3183"
packet receive buffers have been allocated.IDXID="w3385"BOOK="_idx" COLLECTION="nw41" TIDREF="i1298"
An EISA controller board needs to be configured to use interrupts.RENDERAS="SECT3"Possible solutionsMARK=BULLETCheck the computer's documentation for switch information. Set the CPU speed to its highest setting. Use SPEED to verify that the CPU is running at the appropriate speed.If a workstation or the server seems slow, insert a new network board into the slow computer to check performance. If the speed is still below normal, reinstall the original network board and replace the cable attaching the workstation or server to the network.Load MONITOR to check the status of packet receive buffers and service processes. Compare their values to the maximum allowable.Use SET to increase the values for the following parameters if your system is at the maximum value: Maximum Service Processes and Maximum Packet Receive Buffers.(For additional ideas, see "BOOK="superenu" COLLECTION="nw41"Assessing Server RAM" in Chapter 7 of Supervising the Network.)Load MONITOR and check the Hot FixTM status of all hard disks. Verify that all mirrored disks are still mirrored.Run the FILER text utility or the NetWare Administrator graphical utility to purge deleted files. Or set the "Purge" attribute on files you want to be purged immediately after being deleted.For more information, see Chapter 2, "BOOK="superenu" COLLECTION="nw41"Managing Directories, Files, and Applications," in Supervising the Network.PAGENUM=336 ID="BP333"Load MONITOR and check the LAN driver statistics. If you have more than one network board, compare the boards' "Total packets sent" statistics. If one board is receiving most of the traffic, re-cable the network so that the boards have equal loads.If you are on a multiserver network or an internetwork, re-cable the system with a backbone to reduce network traffic. See "BOOK="cncptenu" COLLECTION="nw41"Network backbone" in Concepts for a description of a backbone.Check the cabling for interference from fluorescent lights, microwaves, radar, X rays, and copy machines. Either move the cable or shield it from the source of interference.RENDERAS="SECT2"ID="FM67652"Users can log in, but IDXID="w3386"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
workstations periodically lose their IDXID="w3387"BOOK="_idx" COLLECTION="nw41" TIDREF="i646"IDXID="w3388"BOOK="_idx" COLLECTION="nw41" TIDREF="i796"
connections to the serverRENDERAS="SECT3"Possible causesMARK=BULLETA IDXID="w3389"BOOK="_idx" COLLECTION="nw41" TIDREF="i2847"
network board in either the server or a workstation is faulty.A user on the network is using an old shell file (for example NETX.COM).Two workstations have the same IDXID="w3390"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"IDXID="w3391"BOOK="_idx" COLLECTION="nw41" TIDREF="i2954"
node number.The IDXID="w3392"BOOK="_idx" COLLECTION="nw41" TIDREF="i561"IDXID="w3393"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
cabling system is not terminated properly.RENDERAS="SECT3"Possible solutionsMARK=BULLETRun NLIST to make sure all node numbers are unique. At a DOS workstation, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NLIST USER /A MOREINFO="NONE"<Enter>Check all boot files. Make sure all users are using the latest version of the workstation software.Check the cabling for improper termination, loose connections, and faulty components. Use a LAN analyzer product to check the network boards, cables, and packets. (NetWare CareTM and LANalyzer® are available from your Novell Authorized ResellerCLM.) Replace faulty boards and cables.PAGENUM=337 ID="BP334"Refer to your network hardware's documentation to review the cabling specifications for your cabling system. Make sure your system is in compliance with all the specifications.Set the console to display all workstation connections cleared by the watchdog. (See "BOOK="utlrfenu" COLLECTION="nw41"SET" in Utilities Reference.) If workstations are being cleared by the watchdog, check all network boards and the entire cabling system between the workstations and the server. Check for faulty cables, improper termination, and faulty hubs.RENDERAS="SECT2"ID="FM25144"IDXID="w3394"BOOK="_idx" COLLECTION="nw41" TIDREF="i283"
ARCnet-specific IDXID="w3395"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
problemsRENDERAS="SECT3"Possible software-related causesMARK=BULLETThe LAN driver being used is not specifically designed for the ARCnet* network board.The LAN driver is outdated.Receive buffer sizes conflict.Node numbers are illegal or conflicting.The monitor board settings conflict with the network board settings.RENDERAS="SECT3"Possible software solutionsMARK=BULLETLoad the LAN driver that matches the IDXID="w3396"BOOK="_idx" COLLECTION="nw41" TIDREF="i2847"
network board installed.Contact the vendor for an updated version of the LAN driver.Run NLIST. Make sure that all client workstation addresses are unique and that no station uses 0. At a DOS workstation, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NLIST USER /A MOREINFO="NONE"<Enter>
PAGENUM=338 ID="BP335"If the monitor is blank when the network board is in the workstation, the monitor could be using interrupt 2. Try setting the network board to an option that does not use interrupt 2; then edit the NET.CFG file to reconfigure the workstation's IPXODI.COM file.(See the hardware documentation for a list of supported options for your board.)RENDERAS="SECT3"Possible hardware-related causesMARK=BULLETThe passive or active IDXID="w3397"BOOK="_idx" COLLECTION="nw41" TIDREF="i1735"
hubs are faulty.The network boards are faulty.Improper IDXID="w3398"BOOK="_idx" COLLECTION="nw41" TIDREF="i561"
cable lengths connect to passive or IDXID="w3399"BOOK="_idx" COLLECTION="nw41" TIDREF="i84"
active hubs.Two passive hubs are connected together.A passive hub is terminated improperly.RENDERAS="SECT3"Possible hardware solutionsMARK=BULLETCheck the fuses in all IDXID="w3400"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
active hubs. Replace faulty fuses.If active hub lights blink, bad packets are being sent on the network. Check for conflicting node addresses, bad network boards, and improperly terminated passive hubs.Check all passive hubs for proper termination.Check the lengths of the cables connecting active and passive hubs to make sure they are within specifications. (See the hardware documentation to review the cabling specifications for your IDXID="w3401"BOOK="_idx" COLLECTION="nw41" TIDREF="i2847"
network board.)Check the cabling system for loopbacks, such as a cable from an active hub that attaches back to the active hub rather than to a workstation. Make sure that two passive hubs are not cabled to each other.PAGENUM=339 ID="BP336"RENDERAS="SECT2"ID="FM37644"Ethernet-specific IDXID="w3402"BOOK="_idx" COLLECTION="nw41" TIDREF="i1353"IDXID="w3403"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
problemsRENDERAS="SECT3"Possible software-related causesMARK=BULLETThe workstation and the server are using two different Ethernet frame types.The monitor board settings conflict with the IDXID="w3404"BOOK="_idx" COLLECTION="nw41" TIDREF="i2847"
network board settings.RENDERAS="SECT3"Possible software solutionsMARK=BULLETMake sure that the server LAN drivers and the workstation LAN drivers have been configured for the same Ethernet frame type. (See "BOOK="cncptenu" COLLECTION="nw41"Frame" in Concepts for information on frame types.) Configure the workstations for the appropriate frame type.MARK=BULLETFor instructions on configuring workstation LAN drivers, see BOOK="ws_d1enu" COLLECTION="nw41"NetWare Client for DOS and Windows User Guide.See "BOOK="utlrfenu" COLLECTION="nw41"LOAD" in Utilities Reference for the parameter you need to configure the Ethernet LAN driver in the NetWare server.Some VGA boards use interrupt 2. If the monitor is blank when the network board is installed, set the network board to an option that does not use interrupt 2; then edit the NET.CFG file to reconfigure the workstation software.(See the appropriate hardware documentation for a list of supported options for your network board.)For workstation LAN drivers or specialized software that sets the node address for the client workstation's network board, run NLIST to make sure that each network board has a unique node number. At a DOS workstation, typeFORMAT="LINESPECIFIC"MOREINFO="NONE"NLIST USER /A MOREINFO="NONE"<Enter>RENDERAS="SECT3"Possible hardware-related causesMARK=BULLETIDXID="w3405"BOOK="_idx" COLLECTION="nw41" TIDREF="i4622"IDXID="w3406"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
T-connectors are not terminated properly.The IDXID="w3407"BOOK="_idx" COLLECTION="nw41" TIDREF="i2847"
network board is set up for one type of cabling, but it is connected to a different type (such as thick Ethernet instead of thin Ethernet).PAGENUM=340 ID="BP337"Hardware conflicts exist between the workstation and the network board.RENDERAS="SECT3"Possible hardware solutionsMARK=BULLETCheck for faulty termination. Each T-connector that has only one cable attached to it must be terminated. Each trunk must be terminated with a grounded terminator.Check the network boards. Make sure that the board is set for the type of cabling (thick or thin Ethernet) you are using.Check terminators with an ohmmeter for a resistance of 48 to 52 ohms. Replace any terminators that do not fall within the specified range.RENDERAS="SECT2"ID="FM22161"Token ring-specific IDXID="w3408"BOOK="_idx" COLLECTION="nw41" TIDREF="i4511"IDXID="w3409"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
problemsRENDERAS="SECT3"Possible software-related causeIDXID="w3410"BOOK="_idx" COLLECTION="nw41" TIDREF="i2044"MARK=BULLETIBM IDXID="w3411"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"LAN Support has not been loaded at the workstations.RENDERAS="SECT3"Possible software solutionsMARK=BULLETCheck for duplicate client workstation addresses if you have used DOS ODITM drivers or specialized software to set the node addresses.Run DXMAID at each workstation, and set LAN Support to load automatically when the workstation is booted. The DXMAID program is on the IBM CLASS=DISKLAN Support Program diskette.RENDERAS="SECT3"Possible hardware-related causesMARK=BULLETA IDXID="w3412"BOOK="_idx" COLLECTION="nw41" TIDREF="i2348"IDXID="w3413"BOOK="_idx" COLLECTION="nw41" TIDREF="i4577"
MAU (Medium Attachment Unit) is faulty or a MAU has been set improperly.A faulty token ring adapter has been installed in a workstation or server.PAGENUM=341 ID="BP338"RENDERAS="SECT3"Possible hardware solutionsMARK=BULLETReset the MAU. Check the MAU for faulty fuses, power problems, and bad ports.Check for faulty token ring adapters by running the DXMAID program found on the IBM CLASS=DISKLAN Support Program diskette.Check for breaks in the daisy-chained MAUs.