#EDIR DATA#
NetWare 3.12 System AdministrationDisclaimerNovell®, 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.TrademarksBtrieve, DR DOS, EXOS, LANalyzer, NetWare, OnLan/PC, Novell, and the N design are registered trademarks of Novell, Inc.Advanced NetWare, Boot Support Module, BSM, ElectroText, Hardware Specific Module, Hot Fix, HSM, Internetwork Packet Exchange, LAN Service, Link Support Layer, LSL, Media Support Module, MSM, Multiple Link Interface, MLI, Multiple Link Interface Driver, MLID, Multiple Protocol Interface, MPI, NetWare Access Server, NetWare Access Services, NetWare Core Protocol, NCP, NetWare Directory Services, NDS, NetWare DOS Requester, NDR, NetWare Express, NetWare Loadable Module, NLM, NetWare Management Agent, NetWare MultiProtocol Router, NetWare NFS, NetWare Requester, NetWare RPC, NetWare Runtime, Network Support Encyclopedia, NetWare 3270 LAN Workstation, NetWare 3270 LAN Workstation for DOS, NetWare 3270 LAN Workstation for Windows, NLM, NE/2, NE/2-32, NE1000, NE1500T, NE2000, NE2100, NE3200, NE32HUB, Novell Labs, Novell Virtual Terminal, NVT, NTR2000, Open Data-Link Interface, ODI, Packet Burst, RX-Net/2, SFT, Topology Specific Module, TSM, TSA, Transaction Tracking System, TTS, Turbo RX-Net, Virtual Loadable Module, and VLM are trademarks of Novell, Inc.NetWire is a service mark of Novell, Inc.Novell Authorized Reseller is a collective mark of Novell, Inc.3Com and 3+Share are registered trademarks of 3Com Corporation.ARCnet is a registered trademark of Datapoint Corporation.AT&T is a registered trademark of AT&T.Apple, AppleShare, AppleTalk, ImageWriter, LaserWriter, LocalTalk, and Macintosh are registered trademarks of Apple Computer, Inc.Citizen is a registered trademark of Tokei Kabushiki Kaisha.COMPAQ is a registered trademark of Compaq Computer Corporation.CompuServe is a registered trademark of CompuServe, Inc.DDS is a trademark of Sony Corporation.DEC is a trademark of Digital Equipment Corporation.Epson is a registered trademark of Seiko Epson Corporation.GE Information Services is a trademark of General Electric Company, USA, which is not connected with the General Electric Company p.l.c. of England.Hayes is a registered trademark of Hayes Microcomputer Products, Inc.Hewlett-Packard, Deskjet, HP, Laserjet, PCL, and Vectra are registered trademarks of Hewlett-Packard Company.IBM, AT, Micro Channel, NetView, OS/2, ProPrinter, and PS/2 are registered trademarks of International Business Machines Corporation.IBM Operating System/2 Local Area Network Server (LAN Server), Presentation Manager, SAA, and XT are trademarks of International Business Machines Corporation.Intel is a registered trademark of Intel Corporation.LAN Manager and LAN Manager Server are trademarks of Microsoft Corporation.Lotus is a registered trademark of Lotus Development Corporation.Microsoft and MS-DOS are registered trademarks of Microsoft Corporation.NFS is a registered trademark of Sun Microsystems, Inc.Okidata and Microline are registered trademarks of Oki Electric Industry Co., Ltd.Panasonic is a registered trademark of Panasonic Office Automation.Pinwriter, Spinwriter, and NEC are registered trademarks of NEC Corporation.PostScript is a registered trademark of Adobe Systems Incorporated.SDI is a registered trademark of Systems Data, Inc.SQL Server is a trademark of Sybase, Inc.Unicode is a registered trademark of Transoft Ltd.UNIX is a registered trademark of UNIX System Laboratories, Inc., a subsidiary of AT&T.WordPerfect is a registered trademark of WordPerfect Corporation.Xerox Diablo is a registered trademark of Xerox Corporation.Copyright Notices© Copyright 1983-1993 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.Novell, Inc.122 East 1700 SouthProvo, UT 84606U.S.A.Portions of Concepts and Supervising the Network are copyrighted © 1993 Imagery Software, Inc.lbl ="0"How to Use this ManualPurposeThe purpose of this manual is to help you be an effective system administrator of your NetWare network. You can use System Administration as a reference tool and troubleshooting guide.The manual includes general information about the file server utilities and about some tasks you can perform with them; it does not, however, give step-by-step instructions on completing all tasks. Most utilities have online help that explains how to complete tasks. This manual discusses the installation and use of the Novell's online documentation viewer.Also included in this manual are sections related to remote management of the network and troubleshooting hints.To use this manual, you should be familiar with the platform you are using and with NetWare terminology and concepts. For more information on NetWare terminology and concepts, see book="concepts" docset="nw312"Concepts. For procedural help on some tasks, seebook="utilref" docset="nw312"Utilities Reference.OrganizationThis manual is divided into four parts:Chapter 1, Using Server UtilitiesThis chapter is an alphabetical listing of server utilities, which are executed from the console prompt.Information for each utility includes tasks you can perform with the utility, command syntax and parameters, and instructions for using the utility. Many utilities also include examples.Three types of utilities are documented in this chapter: Console commands allow you to perform the following types of tasks: change memory allocations, monitor how the server is being used, and control the way workstations can use the server's resources.Loadable Modules link disk drivers, LAN drivers, name space modules, management applications, and enhancement utilities with the server's operating system.SERVER boots the NetWare operating system on the server. Chapter 2, Remote ManagementThis chapter provides an overview of what remote management is, who can use it, and how it works.Topics discussed in this chapter include:Different types of communication links that can be set up using remote management.Hardware and software requirements for establishing connections to remote servers and workstations.Using a remote console. This section addresses the purpose, activation, and use of the remote console.Chapter 3, Troubleshooting GuideThis chapter gives helpful hints on some of the more common problems you may encounter while maintaining your network.The Troubleshooting Guide is divided into three sections.Miscellaneous tips---intended to help you develop good system administration habits.Flow charts---designed to assist you in isolating possible network problems.Common problems---included to identify potential solutions to specific problems.Chapter 4, Using Novell ElectroTextThe NetWare Communication Services(tm) viewer, also known as Novell ElectroText(tm), allows you to read all of the NetWare v3.12 manuals online. This chapter documents the use of Novell ElectroText on the Windows and OS/2® platforms only. AppendixesAppendix A---lists LAN driver statistics available in MONITOR.Appendix B---lists the tracked resources that are displayed in MONITOR.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:Novell, Inc.Technical Publications MS C-23-1122 East 1700 South Provo, UT 84606 USAWe appreciate your comments.LBL="1"File Server UtilitiesOverviewThree types of file server utilities are documented in this manual: console commands, loadable modules, and SERVER (a DOS executable file, NetWare's "kernel"). Each type of file server utility is described here.Console CommandsYou enter console commands at the file server console prompt, a colon (:). You use these commands to perform the following types of tasks: change memory allocations, monitor how the file server is being used, and control the way workstations can use the file server's resources. Loadable ModulesNetWare Loadable Modules(tm) link disk drivers, LAN drivers, name space modules, management applications, and enhancement utilities with the file server's operating system. For additional information see "book="concepts" docset="nw312"Loadable module" in Concepts.SERVERThe executable file SERVER boots the NetWare operating system on the file server. You can execute SERVER from drive A: or from a DOS partition on drive C:. After SERVER executes, you can load disk or LAN drivers to complete the operating system configuration. Once the system is configured, you can enter console commands or load loadable modules to maintain and monitor network activity.ID="FM56807"ABORT idxid="w6943"book="_idx" docset="nw312" tidref="i71"REMIRROR idxid="w6944"book="_idx" docset="nw312" tidref="i6241"Why Use idxid="w6945"book="_idx" docset="nw312" tidref="i2127"ABORT REMIRROR?Use ABORT REMIRROR to stop the idxid="w6946"book="_idx" docset="nw312" tidref="i5785"remirroring of a idxid="w6947"book="_idx" docset="nw312" tidref="i3420"logical idxid="w6948"book="_idx" docset="nw312" tidref="i1590"partition.Command Format  ABORT REMIRROR numberCommand ParameterReplace number with the number of the logical partition you want to stop remirroring for.Stop Remirroring a Logical PartitionTo halt the process of remirroring a logical partition, type  ABORT REMIRROR number<Enter>For example, to stop remirroring for logical partition 2, you would type  ABORT REMIRROR 2 <Enter>ID="FM41827"Additional InformationFor more information about partition remirroring, IDREF="FM30824"see "REMIRROR PARTITION" on page 228ID="FM34136"ADD NAME SPACEWhy Use idxid="w6949"book="_idx" docset="nw312" tidref="i146"ADD idxid="w6950"book="_idx" docset="nw312" tidref="i3992"NAME SPACE?Use idxid="w6951"book="_idx" docset="nw312" tidref="i2127"ADD NAME SPACE to allow non-DOS files (such as idxid="w6952"book="_idx" docset="nw312" tidref="i3631"Macintosh idxid="w6953"book="_idx" docset="nw312" tidref="i3631"files) to be stored on a NetWare idxid="w6954"book="_idx" docset="nw312" tidref="i7372"volume. Execute this command only once for each non-DOS naming convention that you want to store on a volume.Before you can use this command, you must load the name space module. For instructions, IDREF="FM50686"see "LOAD name space" on page 158Command Format  ADD NAME SPACE name [TO [VOLUME]] volume_nameCommand ParametersReplace name with the name of the variable for the name space module you loaded. (See the documentation that comes with the name space module or use ADD NAME SPACE without any variables to display the name of the loaded name spaces.)Replace volume_name with the name of the volume you want to store the non-DOS files on.Additional InformationWhen adding name space, you should be aware of the following special considerations:You will need more file server memory.You must run VREPAIR to reverse ADD NAME SPACE.Calculating Extra Memory Required for the Name SpaceYour file server needs extra memory for each name space you add to a volume. Unless all users on your system will be using the name space, we recommend that you have a separate volume for each non-DOS name space that you add to your file server.It's possible that if you add name space to the volume, you might not have enough memory in the file server to mount the volume.Before adding a name space to a volume, idxid="w6955"book="_idx" docset="nw312" tidref="i3992"calculate idxid="w6956"book="_idx" docset="nw312" tidref="i146"the amount of memory idxid="w6957"book="_idx" docset="nw312" tidref="i3758"that the name space will require. First, view the current volume size with INSTALL. Then use the formulas described in the following table to estimate the total amount of memory needed per volume.LBL="1-1"Calculating extra memory required for the name spaceFILE="n312sa01.pbm"idxid="w6958"book="_idx" docset="nw312" tidref="i146"Reversing ADD NAME SPACEOnce a volume is set to store non-DOS files, you can reverse the setting only by running VREPAIR and destroying all the non-DOS file data.Set Up a Volume to Store idxid="w6959"book="_idx" docset="nw312" tidref="i2300"Non-DOS FilesTo set up a volume to store non-DOS files, complete the following.ProcedureMake sure the module for the non-DOS files is loaded. Type  MODULES <Enter>If the module has not been loaded, IDREF="FM50686"see "LOAD name space" on page 158 for instructions.Configure the volume for the new name space. For example, to add Macintosh name space to the MACVOL volume, type  ADD NAME SPACE MAC TO MACVOL <Enter>List the Current idxid="w6960"book="_idx" docset="nw312" tidref="i3992"Name SpaceTo see the name space support already added, type  ADD NAME SPACE <Enter>A message similar to the following appears:LBL="1-2"Name space support screenFILE="n312sa02.pbm"ID="FM75419"BINDWhy Use BIND?Use idxid="w6961"book="_idx" docset="nw312" tidref="i682"BIND to link LAN drivers to a idxid="w6962"book="_idx" docset="nw312" tidref="i3085"communication protocol and to a specific network board in the idxid="w6963"book="_idx" docset="nw312" tidref="i2127"file server. Unless you link a communication protocol to the board, the board cannot process packets.You may not need to use the BIND command. The "Product Options" feature of INSTALL may automatically insert a BIND command in an .NCF file. Consult the documentation for the network products that you use with your file server.Before you can bind the LAN driver, you must first install the network board and load the LAN driver. IDREF="FM79039"See "LOAD LAN driver" on page 122.Command Format  BIND protocol [TO] LAN_driver | board_name [driver_parameter...] [protocol_parameter...]Command ParametersReplace protocol with IPX(tm) or some other protocol. Consult NetWire®, your Novell Authorized ResellerCLM, or third-party dealers for other available options. If the communication protocol will not bind to the driver, IDREF="FM23270"See "PROTOCOL" on page 222.Replace LAN_driver with either the name of the driver you loaded for the network board or the board_name you assigned when you loaded the driver.Driver ParametersInclude a driver_parameter when you have more than one network board of the same type in your file server. (You do not need driver parameters if you bind a protocol to a board name rather than to a LAN driver.)Replace driver_parameter with one or more of the following parameters.DMA=numberFRAME=nameINT=numberMEM=numberPORT=numberSLOT=numberInclude those that make the network board unique from all other network boards of its type. If you include the driver parameter with the command, you must enclose it in square brackets.idxid="w6964"book="_idx" docset="nw312" tidref="i1627"DMA=numberIdentifies the DMA channel the driver is using for the network board. Bind the protocol with the same DMA channel that you used when you loaded the driver for the board.FRAME=nameIdentifies the idxid="w6965"book="_idx" docset="nw312" tidref="i2520"frame type the driver is using for the network board. Bind the protocol with the same frame type that you used when you loaded the driver for the board.idxid="w6966"book="_idx" docset="nw312" tidref="i2946"INT=number idxid="w6967"book="_idx" docset="nw312" tidref="i2946"Identifies the interrupt the driver is using for the network board. Bind the protocol with the same interrupt that you used when you loaded the driver for the board.MEM=numberIdentifies the memory idxid="w6968"book="_idx" docset="nw312" tidref="i3782"address the driver is using for the network board. Bind the protocol with the same memory address that you used when you loaded the driver for the board.PORT=numberIdentifies the idxid="w6969"book="_idx" docset="nw312" tidref="i2691"I/O idxid="w6970"book="_idx" docset="nw312" tidref="i2691"port the driver is using for the network board. Bind the protocol with the same I/O port that you used when you loaded the driver for the board.idxid="w6971"book="_idx" docset="nw312" tidref="i6351"SLOT=numberIdentifies the network board by the slot that the network board was installed in. This parameter is used with microchannel and EISA computers. Bind the protocol with the same slot number that you used when you loaded the driver for the board.Protocol ParametersUse protocol_parameter for the parameters unique to the communication protocol. IPX has one parameter: NET. (See the documentation that comes with other protocols for their specific protocol parameters.)NET=numberIdentifies a unique idxid="w6972"book="_idx" docset="nw312" tidref="i4508"network idxid="w6973"book="_idx" docset="nw312" tidref="i4551"number for the cabling system attached to the board.If the board is attached to an existing cabling system, use the network address of that cabling system.If the board is attached to a new cabling system, select a hexadecimal number that is different from all other network numbers (IPX internal network numbers and cabling systems).If you have loaded the driver with more than one frame type for a single board in the file server, you must select a hexadecimal number that is different from all other network numbers (IPX internal network numbers and cabling systems). Do not use the same number that was used for another frame type on the cabling system.You must specify this parameter when you bind IPX. If you do not enter this parameter at the command line, the operating system prompts you for a network number.Bind idxid="w6974"book="_idx" docset="nw312" tidref="i5640"a idxid="w6975"book="_idx" docset="nw312" tidref="i4508"Protocol idxid="w6976"book="_idx" docset="nw312" tidref="i1081"to a DriverThe steps for binding a protocol to a driver vary with how the driver has been loaded. Select the procedure that fits your situation.Driver Loaded Only OnceTo bind a idxid="w6977"book="_idx" docset="nw312" tidref="i3005"driver when the file server has only one network board of a particular type (such as an RX-Net board), complete the following steps.ProcedureType  BIND IPX TO TRXNET <Enter>Enter the network number for the cabling scheme.To bind the driver automatically when the file server is booted, add the following line to the AUTOEXEC.NCF file. In this example, the network number is 26. The line should follow the LOAD command for the driver.BIND IPX TO TRXNET NET=26Repeat the process for each driver in the file server.Driver Loaded More than Once for Additional Network BoardsFor file servers with multiple network boards of the same type, direct the operating system to bind a specific board by completing the following steps.Procedure Complete one of the following. (Both of the examples below explain how to bind the NE2000 driver to IPX.)Type the command, including the driver and protocol parameters. Type  BIND IPX TO NE2000 [INT=4] NET=26 <Enter>Type the command and answer the prompts. Type  BIND IPX TO NE2000 <Enter>The operating system lists the network boards installed in your file server and prompts you to enter the board number and the network number of the cabling system.To bind the driver automatically when the file server is booted, add the following line to the AUTOEXEC.NCF file. You must include complete configuration information in the file. In this example, network number = 26, port = 340, interrupt = 4, and frame type = Ethernet_802.3 (default). Enter the network number after NET=. The line should follow the command that loads the driver.BIND IPX TO NE2000 PORT=340 INT=4 FRAME=ETHERNET_802.3 NET=26Repeat the process for the other boards in the server.Driver Loaded with a idxid="w6978"book="_idx" docset="nw312" tidref="i3989"Name for the BoardWhen a board has been given a name, IDREF="FM79039"(see "LOAD LAN driver" on page 122), the operating system associates the driver parameters and the frame type with the board name. To bind the protocol to the board name, complete the following steps.ProcedureTo bind IPX to a board named BACKBONE, type  BIND IPX BACKBONE <Enter>Enter the network number for the cabling scheme.To bind the driver automatically when the file server is booted, add the following line to the AUTOEXEC.NCF file. In this example, the network number is 26 and the board name is BACKBONE. The line should follow the load command for the driver.BIND IPX TO BACKBONE NET=26Driver idxid="w6979"book="_idx" docset="nw312" tidref="i5640"Loaded More than Once for Additional Frame TypesTo bind a protocol to a driver that is loaded with two or more frame types for the same network board, complete the following.ProcedureTo bind IPX to an NE2000 driver, type  BIND IPX TO NE2000 <Enter>A list of configurations for the driver appears.Enter the number of the configuration that you want to bind.Enter the network number for the cabling scheme.Each frame type must use its own unique network address for the cabling scheme. For additional information see "book="concepts" docset="nw312"Network numbering" inConcepts.To bind the driver automatically when the file server boots, add the following line to the AUTOEXEC.NCF file. You must include complete configuration information. The line should follow the load command for the driver.BIND IPX TO NE2000 [PORT=300 INT=3 FRAME=ETHERNET_SNAP] NET=26Repeat the process for each frame type.ID="FM15237"BROADCASTWhy Use idxid="w6980"book="_idx" docset="nw312" tidref="i766"BROADCAST?Use BROADCAST to send a idxid="w6981"book="_idx" docset="nw312" tidref="i2034"idxid="w6982"book="_idx" docset="nw312" tidref="i2096"idxid="w6983"book="_idx" docset="nw312" tidref="i2127"message to all users logged in or attached to the file server or to a list of users or connection numbers.Command Format  BROADCAST "message" [[TO] username|connectionnumber] [[and|,] username|connectionnumber...]Command ParametersReplace message with the text (up to 55 characters) you want to send.If no user or connection number is specified, the message is sent to all attached users.Replace username with the user or users you want to send the message to. Separate multiple users with a comma, a space, or and.Replace connectionnumber with the number of the workstation you want to send the message to. Separate multiple connection numbers with a comma, a space, or and. To determine the connection number, see IDREF="FM22079""Connection Information" on page 180.Additional InformationWho Receives MessagesAll logged-in users except the following receive the messages:Users who have used the CASTOFF ALL utility.Users who are logged in using ACS or NACS.Users who are logged in on remote workstations.Users who are using some graphics applications. These users may still hear the beep and should press <Ctrl><Enter> to proceed. To prevent the beep, users can run CASTOFF ALL before running the graphics applications.Where Messages AppearThe BROADCAST message appears on the 25th line of the screen. Messages do not interfere with the workstation's screen display; however, the user cannot make any entries on the screen until the message is cleared.How idxid="w6984"book="_idx" docset="nw312" tidref="i6151"to Clear idxid="w6985"book="_idx" docset="nw312" tidref="i3839"MessagesTo clear the message from a workstation screen and resume work, press <Ctrl><Enter> at the workstation.How to Stop Message DisplaysUse idxid="w6986"book="_idx" docset="nw312" tidref="i3839"CASTOFF with the ALL option to prevent messages from being received or displayed.Send a Console idxid="w6987"book="_idx" docset="nw312" tidref="i3839"MessageSend a Message to All UsersTo send a message to all users logged in or attached to the file server, type  BROADCAST message<Enter>You do not need to use quotation marks when you send a message to all users.Send a Message to a Specific UserTo send a message to a user named Jack, type  BROADCAST "message" Jack <Enter>Send a Message to a Specific WorkstationTo send a message to workstation number 1, type  BROADCAST "message" 1 <Enter>Send a Message to Users and WorkstationsTo send a message to users Fred, Jack, and Mary and to workstations 1 and 4, you can type  BROADCAST "message" to Fred, Jack, 1, 4, Mary <Enter>idxid="w6988"book="_idx" docset="nw312" tidref="i942"CDROMWhy Use CDROM?Use CRROM to idxid="w6989"book="_idx" docset="nw312" tidref="i7369"allow the server to use a idxid="w6990"book="_idx" docset="nw312" tidref="i930"CD-ROM disk as a read-only volume.Command Format  LOAD [path] CDROMCommand ParametersReplace path with the full path to the directory containing the CDROM module. Using CDROMThe following sections explain these tasks that can be accomplished using the idxid="w6991"book="_idx" docset="nw312" tidref="i942"console commands associated with the CDROM.NLM:Display Help information.List the CD-ROM devices.List all volumes identified on the CD-ROM devices.Dismount a CD-ROM volume.Request the root directory of a volume.Mount a CD-ROM volume.Change the media in a CD-ROM drive.Decrease the time required to remount a volume.Display Help InformationTo display help information at the console, type  CD HELP <Enter>CD HELP is available only if you have loaded the CDROM.NLM.idxid="w6992"book="_idx" docset="nw312" tidref="i930"List the idxid="w6993"book="_idx" docset="nw312" tidref="i3231"CD-ROM DevicesTo list the CD-ROM devices that the system knows about at the console, type  CD DEVICE LIST <Enter>Devices are listed in groups of 10. If you repeat the command, the next group of 10 devices is listed.The list includes the following for each device:Device numberDevice nameMedia volume name (if found)Volume mount status"Device" is the CD-ROM drive that contains the system interface and allows the CD-ROM to read the information.List All idxid="w6994"book="_idx" docset="nw312" tidref="i3231"Volumes Identified on the CD-ROM DevicesWIDTH="156"ToWIDTH="144"TypeWIDTH="156"List all the volumes identified on the  CD-ROM devices that the system  knows about at the consoleWIDTH="144"CD VOLUME LISTVolumes are listed in groups of 10. If you repeat the command, the next group of 10 volumes is listed.The list includes the following for each volume:Device nameVolume mount statusThe CD VOLUME LIST command doesn't display information for devices that do not have media present.idxid="w6995"book="_idx" docset="nw312" tidref="i930"Dismount a idxid="w6996"book="_idx" docset="nw312" tidref="i1613"CD-ROM VolumeWIDTH="156"ToWIDTH="156"TypeWIDTH="156"Dismount a previously mounted  CD-ROM volumeWIDTH="156"CD DISMOUNT [device number]  [volume name]Specify the device, the drive number of the currently mounted volume, or the volume name.After CD DISMOUNT is executed, all system resources are returned to the system.Request the Root Directory of a VolumeWIDTH="156"ToWIDTH="156"TypeWIDTH="156"Request the root directory of a  volume from the consoleWIDTH="156"CD DIR [device number] [volume  name]Specify the device, the drive number of the currently mounted volume, or the volume name.CD DIR lists directory entries in DOS format.CD DIR allows you to view the contents of a CD-ROM volume to verify a volume root directory. Each CD-ROM is treated as one volume for NetWare access. The volume does not need to be mounted to use CD DIR.idxid="w6997"book="_idx" docset="nw312" tidref="i930"Mount a idxid="w6998"book="_idx" docset="nw312" tidref="i3963"CD-ROM VolumeWIDTH="156"ToWIDTH="156"TypeWIDTH="156"Mount a CD-ROM volumeWIDTH="156"CD MOUNT [device number]  [volume name]Specify the device, the drive number of the volume, or the volume name.The mounted CD-ROM volume is a NetWare read-only volume.Volume names must be unique.idxid="w6999"book="_idx" docset="nw312" tidref="i947"Change the idxid="w7000"book="_idx" docset="nw312" tidref="i3750"Media in a CD-ROM idxid="w7001"book="_idx" docset="nw312" tidref="i930"driveWIDTH="156"ToWIDTH="156"TypeWIDTH="156"Change the media in a CD-ROM  driveWIDTH="156"CD CHANGE [device number]  [volume name]Specify the device, the drive number of the currently mounted volume, or the volume name.The volume is dismounted and you are prompted to replace the media. The new media is mounted as a NetWare volume. During mounting or changing a CD-ROM disk, the selected device is deactivated. This is normal.idxid="w7002"book="_idx" docset="nw312" tidref="i7369"Decrease the Time Required to Remount a VolumeWIDTH="156"ToWIDTH="156"TypeWIDTH="156"Decrease the time required to  remount a volume when working  with several CD-ROMs that have  large directoriesWIDTH="156"CD MOUNT [device number]  [volume name] /RThe /R option tells the system to reuse existing data files instead of recreating or rebuilding them. This allows volumes to be remounted faster.CLEAR STATIONWhy Use idxid="w7003"book="_idx" docset="nw312" tidref="i7493"CLEAR STATION?Use idxid="w7004"book="_idx" docset="nw312" tidref="i2300"CLEAR STATION when a workstation has somehow "crashed" and left open files on a file server. The file server closes the workstation's files and erases all the server's internal tables for the workstation (including drive mappings not saved in the login script). The communication link between the file server and the cleared workstation is broken.Command Format  CLEAR STATION nCommand ParametersReplace n with the number of the workstation you want to clear from the file server. To determine the connection number, use MONITOR at the file server console to view "Connection Information" or use USERLIST at the workstation.If you use CLEAR STATION while the workstation is in the middle of a transaction or a file update, files might be saved with incorrect data.Remove All File Server idxid="w7005"book="_idx" docset="nw312" tidref="i2034"Resources from a WorkstationTo clear a workstation, enter CLEAR STATION at the file server console, replacing n with the number of the workstation. (You can determine the number of the workstation by using MONITOR at the file server or USERLIST at a workstation.)For example, to clear workstation 5, type  CLEAR STATION 5 <Enter>Attached to one file server. If the cleared workstation is attached to only one file server when CLEAR STATION is executed, the workstation shell automatically attempts to re-establish a connection with the default file server.The following message appears on the workstation screen:LBL="1-3"CLEAR STATION message screenFILE="n312sa03.pbm"Type "A" (for abort) to remove the file server resources from your workstation.Attached to multiple file servers. If the cleared workstation is attached to another file server and has a drive mapped to that server, the following message appears at the workstation:  Current drive is no longer valid.Change to a valid drive.CLIBWhy Use idxid="w7006"book="_idx" docset="nw312" tidref="i3300"CLIB?Use idxid="w7007"book="_idx" docset="nw312" tidref="i977"CLIB if you have a loadable module (such as PSERVER or BTRIEVE) that requires CLIB's library of routines and functions. Load CLIB before the loadable module that uses it.idxid="w7008"book="_idx" docset="nw312" tidref="i2127"CLIB requires the STREAMS module. If you do not load idxid="w7009"book="_idx" docset="nw312" tidref="i6540"STREAMS before CLIB, the operating system will load STREAMS for you. IDREF="FM57739"See "STREAMS" on page 320.Command Format  LOAD [path]CLIBCommand ParametersReplace path with a full path to the directory containing the CLIB module. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path, the operating system looks for CLIB in SYS:SYSTEM. (Use SEARCH to set up additional paths for automatic searching.)Additional InformationCLIB sets a time zone when it loads. Since the default is Eastern Standard Time, use the console command SET TIMEZONE IDREF="FM53359"(see "SET TIMEZONE" on page 311) in the AUTOEXEC.NCF file to change the time zone for your location when the file server boots.Load CLIBTo load CLIB, type  LOAD CLIB <Enter>To make sure that the CLIB and STREAMS load automatically when the file server boots, add the following commands to the AUTOEXEC.NCF file:LOAD STREAMSLOAD CLIBFor instructions on editing the AUTOEXEC.NCF file, IDREF="FM11821"see "INSTALL" on page 47, or IDREF="FM69715"see "EDIT" on page 40, or see "book="utilref" docset="nw312"SYSCON" in Utilities Reference.CLSWhy Use idxid="w7010"book="_idx" docset="nw312" tidref="i998"CLS?Use idxid="w7011"book="_idx" docset="nw312" tidref="i2127"CLS to clear the file server console screen.Command Format  CLSClear idxid="w7012"book="_idx" docset="nw312" tidref="i2034"the File idxid="w7013"book="_idx" docset="nw312" tidref="i2096"Server Console idxid="w7014"book="_idx" docset="nw312" tidref="i3839"idxid="w7015"book="_idx" docset="nw312" tidref="i6151"ScreenTo clear the console screen, type  CLS <Enter>You can also use OFF to clear the console screen.CONFIGWhy Use idxid="w7016"book="_idx" docset="nw312" tidref="i1114"idxid="w7017"book="_idx" docset="nw312" tidref="i2127"CONFIG?Use idxid="w7018"book="_idx" docset="nw312" tidref="i2111"CONFIG to display the following information:The idxid="w7019"book="_idx" docset="nw312" tidref="i2111"file server idxid="w7020"book="_idx" docset="nw312" tidref="i4006"nameThe internal network number of the file serverThe loaded idxid="w7021"book="_idx" docset="nw312" tidref="i3005"idxid="w7022"book="_idx" docset="nw312" tidref="i1134"LAN idxid="w7023"book="_idx" docset="nw312" tidref="i3085"driversThe idxid="w7024"book="_idx" docset="nw312" tidref="i2640"hardware settings on all network boards Use CONFIG before installing any memory boards, network boards, or idxid="w7025"book="_idx" docset="nw312" tidref="i2672"host bus adapters in the file server so that you have a current list of all hardware settings on the network boards.The node (station) idxid="w7026"book="_idx" docset="nw312" tidref="i164"addresses of the network boardsConsult this utility to make a current list of all assigned node addresses.The idxid="w7027"book="_idx" docset="nw312" tidref="i1081"communication protocol bound to the network boardThe network number of the idxid="w7028"book="_idx" docset="nw312" tidref="i4551"cabling scheme for a network boardThe idxid="w7029"book="_idx" docset="nw312" tidref="i2520"frame type assigned to the boardMore than one frame type can be assigned to Ethernet and Token-Ring boardsThe board name assignedFor an explanation of internal network idxid="w7030"book="_idx" docset="nw312" tidref="i2933"numbers, network numbers for cabling, and node address, see "book="concepts" docset="nw312"Network numbering" in ConceptsCommand Format  CONFIGAdditional InformationUse MODULES and MONITOR to display information about loadable modules linked to the operating system.Use INSTALL and MONITOR to display configuration information about disk drivers.Use idxid="w7031"book="_idx" docset="nw312" tidref="i2691"DISPLAY NETWORKS to list all network numbers being used by file servers on your network.Display idxid="w7032"book="_idx" docset="nw312" tidref="i2946"Configuration InformationAt the file server console, type  CONFIG <Enter>Information similar to the following appears on the console screen:LBL="1-4"Configuration information screenFILE="n312sa07.pbm"DISABLE LOGINWhy Use idxid="w7033"book="_idx" docset="nw312" tidref="i1536"DISABLE idxid="w7034"book="_idx" docset="nw312" tidref="i2127"idxid="w7035"book="_idx" docset="nw312" tidref="i3426"LOGIN?Use idxid="w7036"book="_idx" docset="nw312" tidref="i2034"DISABLE LOGIN to prevent users from logging in to the idxid="w7037"book="_idx" docset="nw312" tidref="i2092"file server.Use this command when you do not want users logged in because you are making repairs, backing up files, or loading software.Command Format  DISABLE LOGINPrevent Users from Logging in to the File ServerTo prevent users from logging in to the file server, type  DISABLE LOGIN <Enter>Users logged in to the file server are not affected. However, once a user logs out, the user cannot log in again until ENABLE LOGIN is executed.DISABLE TTSWhy Use idxid="w7038"book="_idx" docset="nw312" tidref="i1538"DISABLE idxid="w7039"book="_idx" docset="nw312" tidref="i6861"TTS?During normal operation, you do not need to disable TTS (Transaction Tracking System); the file server automatically disables TTS if necessary. TTS, an integral part of the file server operating system, protects the bindery from becoming corrupted. Disabling TTS frees up very little file server memory for other loadable modules (about 40 bytes for most transactions, and at most 400KB). For a complete description, see "book="concepts" docset="nw312"TTS" in Concepts.idxid="w7040"book="_idx" docset="nw312" tidref="i6864"DISABLE idxid="w7041"book="_idx" docset="nw312" tidref="i2127"TTS is primarily a tool for application developers who need to test transactional applications with TTS disabled.To restore TTS after you have disabled it, use ENABLE TTS or reboot the file server.Command Format  DISABLE TTSDisable TTS in the File ServerTo disable TTS, type  DISABLE TTS <Enter>The following message appears:TTS disabled by operator.TTS remains disabled until you enable it with ENABLE TTS or reboot the file server. ID="FM38327"DISKSETWhy Use idxid="w7042"book="_idx" docset="nw312" tidref="i2127"idxid="w7043"book="_idx" docset="nw312" tidref="i1606"DISKSET?Use idxid="w7044"book="_idx" docset="nw312" tidref="i3300"DISKSET idxid="w7045"book="_idx" docset="nw312" tidref="i1606"to do the following tasks:Install an ADIC/Novell DCB subsystem.Place identification information about external hard disks on the EEPROM chip of the host bus adapter board.The term "host bus adapter," as used in this manual, includes the specific product "Disk Coprocessor Board" ( idxid="w7046"book="_idx" docset="nw312" tidref="i1552"DCB).Place configuration information about the hard disks attached to the host bus adapter on the board's EEPROM chip.Format an external hard disk through the host bus adapter.Back up the NetWare Ready configuration information from a NetWare Ready disk to a diskette.Restore the NetWare Ready configuration information from a backup diskette to the NetWare Ready disk.If you are using a DCB disk driver for a disk subsystem, run DISKSET.EXE before installing your NetWare server. Command Format  DISKSET [path] <Enter>Command ParametersReplace path with the full path to the directory containing DISKSET. Refer to the README.312 file on the installation diskette for information on the source diskette or directory. (On CD-ROM, the README.312 file is in each language directory under NETWARE.312)Using DISKSETRefer to the ADIC manual for information on running DISKSET.EXE.You may need to refer to the documentation for your board.The configuration information allows the NetWare server to communicate with the hard disk through the host bus adapter.DISMOUNTWhy Use idxid="w7047"book="_idx" docset="nw312" tidref="i1612"idxid="w7048"book="_idx" docset="nw312" tidref="i2127"DISMOUNT?Use DISMOUNT to make a volume unavailable to users. This allows you to maintain or repair the volume and to upgrade disk drivers while the file server is up.If you have a volume that is not used very often, you can dismount it until you need to use it again. Mounted volumes take up memory allocated for file caching and slow down the system.Command Format  DISMOUNT volume_nameDismount a idxid="w7049"book="_idx" docset="nw312" tidref="i7372"VolumeTo dismount a volume, complete the following steps at the file server console.ProcedureUse BROADCAST to inform all users that they should close all files and not work in the volume you are going to dismount.Dismount the volume by typing  DISMOUNT volume_name<Enter>Replace volume_name with the name of the volume you want to dismount.ID="FM87975"DISPLAY NETWORKSWhy Use idxid="w7050"book="_idx" docset="nw312" tidref="i1618"DISPLAY idxid="w7051"book="_idx" docset="nw312" tidref="i2127"idxid="w7052"book="_idx" docset="nw312" tidref="i4551"NETWORKS?Use DISPLAY NETWORKS to list all networks and assigned network idxid="w7053"book="_idx" docset="nw312" tidref="i873"numbers that the file server router recognizes. All network numbers (internal and cabling system) are listed.To see a list of servers on the network, use the DISPLAY SERVERS command.Command Format  DISPLAY NETWORKSDisplay idxid="w7054"book="_idx" docset="nw312" tidref="i2933"a List of Networks idxid="w7055"book="_idx" docset="nw312" tidref="i4581"idxid="w7056"book="_idx" docset="nw312" tidref="i6027"To display a list of networks, type  DISPLAY NETWORKS <Enter>Information similar to the following appears on the console screen:LBL="1-5"DISPLAY NETWORKS information screenFILE="n312sa18.pbm"This screen shows the network number, the number of hops (networks that must be crossed) to reach the network, and the estimated time in ticks (1/18 of a second) for a packet to reach the network. The number of known networks is displayed at the bottom of the screen.If a file server is running NetWare v3.1x, both the internal idxid="w7057"book="_idx" docset="nw312" tidref="i3005"IPX network numbers and the cabling network numbers are displayed.In the previous example screen display, two network numbers are zero hops away.One number (00000001) is the internal network number for the file server on which the DISPLAY NETWORKS command was issued.One number (000000AD) is the cabling system number of the file server on which the DISPLAY NETWORKS command was issued. If the file server had more than one network board installed, more than two numbers would be zero hops away.ID="FM76631"DISPLAY SERVERSWhy Use idxid="w7058"book="_idx" docset="nw312" tidref="i1620"DISPLAY idxid="w7059"book="_idx" docset="nw312" tidref="i2127"SERVERS?Use DISPLAY SERVERS to list all servers that the idxid="w7060"book="_idx" docset="nw312" tidref="i2034"file server idxid="w7061"book="_idx" docset="nw312" tidref="i6027"router recognizes.To see a list of networks, use the DISPLAY NETWORKS command.Command Format  DISPLAY SERVERSDisplay a List of File ServersTo list known file servers, type  DISPLAY SERVERS <Enter>Information similar to the following appears on the console screen:LBL="1-6"DISPLAY SERVERS information screenFILE="n312sa19.pbm"The list shows the known servers' names and the number of hops (networks that must be crossed) to reach each server. The number of known servers is displayed at the bottom of the screen.If your file server's name does not appear in the list, volume SYS: is not mounted.ID="FM32696"DOWNWhy Use idxid="w7062"book="_idx" docset="nw312" tidref="i1720"DOWN?Use DOWN to ensure data integrity before turning off the power to the file server. DOWN ensures data idxid="w7063"book="_idx" docset="nw312" tidref="i2300"integrity by writing all cache buffers to disk, closing all files, and updating the appropriate Directory and File Allocation Tables.Command Format  DOWNAdditional InformationChanges made to data files are held in memory (cache buffers). These changes are not normally written to the disk until a minimum time has passed (the default is 3 seconds). When DOWN is used, the file server writes the file cache buffers to disk, updates the tables, and closes the files. These changes will be lost if you turn off the power without downing the file server first.After you down the file server, the server is still idxid="w7064"book="_idx" docset="nw312" tidref="i1204"connected to the network and still receives packets. You can continue to execute console commands, such as TRACK ON and TRACK OFF, that deal with packets.Down idxid="w7065"book="_idx" docset="nw312" tidref="i2127"the idxid="w7066"book="_idx" docset="nw312" tidref="i2034"File ServerTo down the file server, complete the following steps.ProcedureUse BROADCAST to inform all users that they should close all files and log out.Type  DOWN <Enter>Information similar to the following appears:LBL="1-7"DOWN server information screenFILE="n312sa20.pbm"You can use EXIT to return to DOS. However, if you have used the REMOVE DOS command prior to issuing the DOWN command, the EXIT command will reboot the server.If files are still open, the monitor displays the files that are open, the user who opened them, and the workstation connection number. The following prompt then appears:  Down server anyway? nExamine the list of open files and answer"No" if database files or word processing files are open; you should close these files from the application rather than from the file server. Press <Enter>; then either broadcast another message or go to the workstations and close the files."Yes" if the files will not be corrupted or lose data when the connection is broken. Type "Y" and press <Enter>.ID="FM69715"EDITWhy Use idxid="w7067"book="_idx" docset="nw312" tidref="i3300"EDIT?Use idxid="w7068"book="_idx" docset="nw312" tidref="i977"EDIT idxid="w7069"book="_idx" docset="nw312" tidref="i1777"to create or modify a text file. idxid="w7070"book="_idx" docset="nw312" tidref="i2127"EDIT is particularly useful in creating .NCF batch files to execute file server commands automatically. You can use EDIT with text files on either DOS or NetWare partitions. EDIT.NLM can be used to edit files of 8 KB or less.Command Format  LOAD [path]EDITCommand ParametersReplace path with a full path to the directory containing the EDIT module. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path, the operating system looks for EDIT in SYS:SYSTEM. (Use SEARCH to set up additional paths for automatic searching.)Edit or Create idxid="w7071"book="_idx" docset="nw312" tidref="i1780"Text FilesTo load the idxid="w7072"book="_idx" docset="nw312" tidref="i1290"EDIT.NLM and edit a idxid="w7073"book="_idx" docset="nw312" tidref="i6768"text idxid="w7074"book="_idx" docset="nw312" tidref="i2300"file, complete the following steps.ProcedureLoad the module by typing  LOAD EDIT <Enter>At the "File to Edit" prompt, enter the complete directory path for the file.For example, to edit the AUTOEXEC.NCF file in the SYSTEM directory, type  SYS:SYSTEM/AUTOEXEC.NCF <Enter>A file or a blank screen appears, depending on whether you are editing or creating a file. The path you entered appears at the top of the screen.After editing or creating the text file, press <Esc> to exit.When the confirmation box appears, select "Yes" to save the file or "No" to exit without saving the changes.ENABLE LOGINWhy Use idxid="w7075"book="_idx" docset="nw312" tidref="i1816"ENABLE idxid="w7076"book="_idx" docset="nw312" tidref="i2092"LOGIN?Use idxid="w7077"book="_idx" docset="nw312" tidref="i7232"ENABLE idxid="w7078"book="_idx" docset="nw312" tidref="i3426"LOGIN to re-enable the login function or to enable the SUPERVISOR's account when the account has been idxid="w7079"book="_idx" docset="nw312" tidref="i2034"locked by the intruder detection function.You do not need to use idxid="w7080"book="_idx" docset="nw312" tidref="i2127"ENABLE idxid="w7081"book="_idx" docset="nw312" tidref="i2034"LOGIN when you boot the file server. The login function is automatically enabled during the bootup process.Command Format  ENABLE LOGINAllow Users to Log InTo allow users to log in again after you have disabled the login function, type  ENABLE LOGIN <Enter>All login privileges are restored.ID="FM99452"ENABLE TTSWhy Use idxid="w7082"book="_idx" docset="nw312" tidref="i1820"ENABLE idxid="w7083"book="_idx" docset="nw312" tidref="i6864"TTS?Use idxid="w7084"book="_idx" docset="nw312" tidref="i2127"ENABLE TTS to start the transaction tracking (NetWare Transaction Tracking System, or TTS) in the file server.Normally transaction tracking is always enabled. However, you can disable TTS with DISABLE TTS.The file server automatically disables TTS if one of the following happens:Volume SYS: gets full. (SYS: is the TTS backout volume.)The file server has insufficient memory to operate TTS.After TTS has been disabled (automatically or manually), use the ENABLE TTS command to enable TTS in the file server.Command Format  ENABLE TTSAdditional InformationFor a complete description, see "book="concepts" docset="nw312"TTS" in Concepts.For more information on the TTS$LOG.ERR file, see IDREF="FM33727"TTS Problems on page 451Enable TTS in the File ServerTo enable TTS in the file server, type  ENABLE TTS <Enter>The following message appears:  Transactional tracking system enabledIf you try to enable TTS when the SYS volume is not mounted or when the file server does not have sufficient resources (disk space or memory) to enable TTS, you will receive one of the following messages.If you try to enable TTS when the SYS volume is not mounted, the following message appears:  TTS can not be enabled because the TTS work volume is not mounted.Mount volume SYS: with MOUNT before you enable TTS.idxid="w7085"book="_idx" docset="nw312" tidref="i6910"If volume SYS: is full, the following message appears:  TTS disabled because of error allocating more disk space for the backout file.To allow sufficient space for the backout TTS file, you must free up 1 MB of disk space on volume SYS:.If you try to enable idxid="w7086"book="_idx" docset="nw312" tidref="i6864"TTS when the file server does not have enough free memoryidxid="w7087"book="_idx" docset="nw312" tidref="i3758", the following message appears:  TTS cannot allocate sufficient memory.idxid="w7088"book="_idx" docset="nw312" tidref="i2599"TTS requires about 40 bytes of memory to track a transaction. idxid="w7089"book="_idx" docset="nw312" tidref="i6864"TTS can track up to 10,000 individual transactions. You should not need more than 400 KB of memory for TTS.To increase the amount of memory available for TTS, do one or more of the following:Unload any file server modules that you do not need (such as INSTALL or MONITOR).Use ENABLE TTS again to see if you have freed up enough memory for TTS. If you have, TTS will be enabled Dismount any disk volumes (other than SYS) that users are not currently using.Use ENABLE TTS again to see if you have freed up enough memory for TTS. If you have, TTS will be enabled.Add more memory to the file server. After you have installed the memory, the file server will automatically enable TTS when it boots.ID="FM93496"EXITWhy Use idxid="w7090"book="_idx" docset="nw312" tidref="i1931"EXIT?Use idxid="w7091"book="_idx" docset="nw312" tidref="i2127"EXIT to return to DOS after you have downed the file server. This allows you to access DOS files or rerun the SERVER.EXE file with new parameters.Use EXIT to warm boot the file server after you have issued the REMOVE DOS and DOWN commands.For further information, see IDREF="FM32696""DOWN." and IDREF="FM96399""REMOVE DOS."Command Format  EXITReturn to idxid="w7092"book="_idx" docset="nw312" tidref="i1638"DOS after Downing the File ServerTo return to DOS after you have used the DOWN command, type  EXIT <Enter>Warm Boot the File ServerTo warm boot the file server after you have used the REMOVE DOS and DOWN commands, type  EXIT <Enter>ID="FM11821"INSTALLWhy Use idxid="w7093"book="_idx" docset="nw312" tidref="i2828"INSTALL?Use idxid="w7094"book="_idx" docset="nw312" tidref="i3300"INSTALL idxid="w7095"book="_idx" docset="nw312" tidref="i2127"to complete the following installation and maintenance tasks:Create, delete, test, or modify NetWare hard disk partitions.Mirror or unmirror hard disks.Create, delete, expand, or modify volumes.Create or modify the AUTOEXEC.NCF and STARTUP.NCF files.Copy the SYSTEM and PUBLIC files onto the file server.Format a hard disk.Execute a surface test of the hard disk for bad blocks.Load the NetWare diskettes.Install and configure products on the file server.Command Format  LOAD [path]INSTALL [NH]Command ParametersReplace path with the path to the directory containing INSTALL. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path and volume SYS: has been mounted, the operating system looks for INSTALL in the SYS:SYSTEM directory. (Use SEARCH to set up additional paths for automatic searching.)The optional NH idxid="w7096"book="_idx" docset="nw312" tidref="i4916"parameter loads INSTALL without idxid="w7097"book="_idx" docset="nw312" tidref="i2659"help screens, saving 16 KB. This is useful if your available cache memory is low. (Use MONITOR to view memory statistics.)Main screenINSTALL is a menu program. As you move through the INSTALL menus, press <F1> at any time for help. The main menu screen for INSTALL appears below, with the tasks that relate to each menu option following.LBL="1-8"INSTALL main menuFILE="n312sa26.pbm"InstallWIDTH="264"TaskWIDTH="48"PageLoad INSTALLIDREF="FM16689"50Disk OptionsWIDTH="264"TaskWIDTH="48"PageWIDTH="264"Add a hard disk to the file serverWIDTH="48"IDREF="FM92680"51Replace a hard diskIDREF="FM96360"53Recover volume data from an unmirrored hard diskIDREF="FM75070"55Format a hard diskIDREF="FM35279"56Create NetWare partitionsIDREF="FM46125"59Delete partitionsIDREF="FM90101"62Edit Hot Fix informationIDREF="FM65426"63Mirror or duplex hard disksIDREF="FM51767"65Unmirror hard disksIDREF="FM54624"67Test hard disks for bad blocksIDREF="FM14232"68Volume OptionsWIDTH="264"TaskWIDTH="48"PageWIDTH="264"Create a volumeWIDTH="48"IDREF="FM21946"71Delete a volumeIDREF="FM90088"73Rename a volumeIDREF="FM49080"74Increase the size of a volumeIDREF="FM92037"76System OptionsWIDTH="264"TaskWIDTH="48"PageWIDTH="264"Copy the SYSTEM and PUBLIC filesWIDTH="48"IDREF="FM86774"78Change the file server's nameIDREF="FM10084"79Change the file server's internal network numberIDREF="FM30120"80Create the AUTOEXEC.NCF fileIDREF="FM97050"81Edit the AUTOEXEC.NCF fileIDREF="FM38546"82Create the STARTUP.NCF fileIDREF="FM28664"86Edit the STARTUP.NCF fileIDREF="FM34636"87Product OptionsWIDTH="264"TaskWIDTH="48"PageWIDTH="264"Install, uninstall, or configure a product on the file serverWIDTH="48"IDREF="FM23830"89ExitWIDTH="264"TaskWIDTH="48"PageWIDTH="264"Exit INSTALLWIDTH="48"IDREF="FM84140"90ID="FM16689"Load INSTALL idxid="w7098"book="_idx" docset="nw312" tidref="i2828"To load INSTALL, type  LOAD INSTALL <Enter>If INSTALL is already loaded, the following message appears:  This module is ALREADY loaded and cannot be loaded more than once.If this message appears, complete one of the following:Press <Alt><Esc> to move through the activated screens until the INSTALL screen appears.Press <Ctrl><Esc> and select "Install Screen" from the list of available screens.ID="FM92680"Add idxid="w7099"book="_idx" docset="nw312" tidref="i2599"a Hard Disk to the File ServerWhen a volume needs to be expanded, you can add a new hard disk to the file server and designate it as a new segment of an existing volume. The steps for adding an internal hard disk vary from the steps for installing an external hard disk. Follow the procedure in one of the following sections that fits your situation.ID="FM40968"Add Internal Hard DiskTo install an internal hard disk, complete the following steps.ProcedureUse BROADCAST to inform all users that the file server is going down.Down the file server by Typing  DOWN <Enter>Turn off the power and install the new hardware.Boot the file server.Load INSTALL.Create a NetWare partition.If you need help, see IDREF="FM46125""Create NetWare Partitions" on page 59.ID="FM46410"Designate the partition as a new segment of an existing volume. If you need help, see IDREF="FM92037""Increase the Size of a Volume" on page 76.Add External Hard Disk in a SubsystemUsers can stay logged in to the file server while the following steps are performed, but the disk driver to the subsystem must not be loaded. All volumes with data stored on the subsystem must not be mounted.To add a hard disk to the subsystem, complete the following steps.ProcedureDismount all volumes with data on the disks in the subsystem by typing  DISMOUNT volume_name<Enter>Replace volume_name with the name of the volume that needs to be dismounted. Repeat this step for each volume that has data stored on the subsystem.Unload the disk driver for the subsystem by typing  UNLOAD driver<Enter>Replace driver with the name of the disk driver. Repeat this step for each disk driver that controls hard disks in the subsystem.Turn off the power to the disk subsystem and install the hard disk.Turn on the power to the disk subsystem.Load the disk drivers that you unloaded in Step 2.Mount the volumes that you dismounted in Step 1.(Conditional) Run DISKSET if the hard disk is connected to a host bus adapter.If you need help, IDREF="FM38327"see "DISKSET"Load INSTALL.ID="FM76757"Create a NetWare partition. If you need help, see IDREF="FM46125""Create NetWare Partitions" on page 59.Designate the partition as a new segment of an existing volume. If you need help, see IDREF="FM92037""Increase the Size of a Volume" on page 76.Repeat Steps 9 and 10 for each new hard disk.ID="FM96360"idxid="w7100"book="_idx" docset="nw312" tidref="i2599"Replace a idxid="w7101"book="_idx" docset="nw312" tidref="i2599"Hard DiskIf a hard disk becomes unreliable or unusable, follow these steps to remove the disk from the network. If you do not complete these steps, the driver will hang the system for a few minutes while it looks for the missing hard disk.If you have been making backups of your data consistently, you will be able to reload data for the volumes affected by the disk failure.Deleting partitions and volumes destroys data. Make extra backups, if possible, before you begin.ProcedureDismount the volume at the console prompt by Typing  DISMOUNT volume_name<Enter>Load INSTALL.If the hard disk is mirrored, unmirror it.If you need help, see IDREF="FM54624""Unmirror Hard Disks" on page 67.Delete the NetWare partition. If you need help, see IDREF="FM90101""Delete Partitions" on page 62.Complete one of the following:If the hard disk is located internally, press <Alt><Esc> and down the file server by typing  DOWN <Enter>Then skip to Step 8.If the hard disk is located in a subsystem, dismount any other volumes that have data on hard disks in the subsystem by typing  DISMOUNT volume_name<Enter>Replace volume_name with the name of the volume that needs to be dismounted. Repeat this step for each volume with data stored on the subsystem.If you are not replacing the hard disk with the same type of disk you are removing, run DISKSET (or the driver's configuration utility) to remove the hard disk's configuration information from the EEPROM chip.Unload the disk driver for the subsystem by typing  UNLOAD driver<Enter>Replace driver with the name of the disk driver. If more than one disk driver is controlling hard disks in the subsystem, repeat this step for each disk driver.Turn off the system containing the disk.Using the instructions that came with the hard disk, remove the hard disk and connect the replacement.Complete one of the following:If the hard disk is located internally, run the computer's setup program. Then boot the file server and skip to Step 14.If the hard disk is located in a subsystem, reload the disk drivers.Mount any dismounted volumes.Run DISKSET (or the driver's configuration utility) and set up the configuration information on the EEPROM chip.Load INSTALL.Create a new partition. If you need help, see IDREF="FM46125""Create NetWare Partitions" on page 59.Complete one of the following:If the disk was not mirrored, create the volume and then restore the data from a backup. (IDREF="FM21946"See "Create a Volume" on page 71.)If the hard disk was mirrored, remirror the disk. (IDREF="FM51767"See "Mirror or Duplex Hard Disks" on page 65.)If you replaced the "Not Mirrored" disk rather than the idxid="w7102"book="_idx" docset="nw312" tidref="i4332""Out Of Sync" disk, recover the volume data from the "Out Of Sync" disk before remirroring the disks. (See the following section.)ID="FM75070"Recover idxid="w7103"book="_idx" docset="nw312" tidref="i7372"Volume Data from an Unmirrored Hard DiskOnce a hard disk is unmirrored, its status is listed as either "Not Mirrored" or "Out Of Sync" on the "Partition Mirroring Status" list. When a hard disk is listed as "Out Of Sync," the operating system does not recognize any volume information on the "Out Of Sync" hard disk.To recover data from the "Out Of Sync" partition, complete the following steps.ProcedureLoad INSTALL.Select "Disk Options" from the "Installation Options" menu.Select "Mirroring" from the "Available Disk Options" menu.Highlight the "Out Of Sync" partition and press <F3>.The following warning may appear if another volume segment with the same name exists on another disk:  Warning!! The selected partition contains "volume <name> segment <number>" and that volume is already defined.  <Press ESCAPE To Continue>Press <Esc> and answer "Yes" at the "Rename the Volume Segment?" prompt.Enter a unique name for the new volume segment.Answer "Yes" to the prompt to salvage the volume segment.idxid="w7104"book="_idx" docset="nw312" tidref="i2599"ID="FM35279"Format a Hard DiskFormatting is not a required step in NetWare v3.1x. Hard disks are usually formatted by the manufacturer.If the manufacturer recommends that the hard disk be formatted, follow the manufacturer's procedures. Most hard disks that require formatting have utilities (the DOS FORMAT command or a utility on a reference diskette) that must be performed prior to installation in the NetWare v3.1x file server.Use INSTALL's "Format" option in the following instances:You have a hard disk that is unreliable and you hope to salvage the disk. (Formatting may not solve the problem.)The hard disk manufacturer recommends the procedure. Start with Step 3.You have changed the controller type on a hard disk, and the controller uses a different format for data storage. Start with Step 3.Before you format a hard disk, make sure that all users have logged out of the file server and that no other network activity is occurring. Use BROADCAST to tell the users to log out. Use MONITOR to delete any remaining connections. Once all connections are clear, use DISABLE LOGIN to prevent users from logging in during the procedure.To format a hard disk, complete the following steps.ProcedureBack up the data on the hard disk using NBACKUP or a third-party backup utility.Dismount all volumes that have data on the hard disk you are going to format by typing  DISMOUNT volume_name<Enter>Replace volume_name with the name of the volume that is on the hard disk. Repeat this step if you have more than one volume on the hard disk.Load INSTALL.Complete one of the following:If the hard disk is mirrored, unmirror the disk. (IDREF="FM54624"See "Unmirror Hard Disks" on page 67.)If the hard disk is not mirrored, delete the volumes on the hard disk. (IDREF="FM90088"See "Delete a Volume" on page 73.)Select "Disk Options" from the "Installation Options" menu.Select "Format (optional)" from the "Available Disk Options" menu.If you have more than one hard disk, select the hard disk from the "Available Disk Drives" list.The following screens appear:LBL="1-9"INSTALL disk "Format information" and "Format Options" screensFILE="n312sa29.pbm"The "Format Information" box can display the following status information:WIDTH="96"NoneWIDTH="192"The disk has not been formatted since  INSTALL was last loaded.FormattingThe disk is currently being formatted.CompletedThe disk has been formatted  successfully.Not SupportedThe disk driver for the hard disk does  not support the format command.FailedThe disk failed the formatting process.Select "Format Disk Drive" from the "Format Options" menu.If the hard disk still has NetWare information on it, you will be warned that you must delete the volumes first. Recheck the volume information to make sure you have dismounted all volumes. If any partitions exist, you will be warned that all information on the disk will be lost. Press <Esc> to continue.Enter the interleave factor. The default is 2. Check the hard disk's documentation for its interleave factor.Once the interleave factor is entered, the formatting begins. Formatting can take a long time (from a few hours to a few days), depending on the disk's capacity.You cannot complete any other tasks with INSTALL while INSTALL is formatting. If you use <Esc> to return to a previous menu, INSTALL appears to be hung. Be patient. The status in the "Format Information" box will change to either "Completed" or "Failed."If the format is successful, re-create a NetWare partition on the hard disk. See the following section.ID="FM46125"Create idxid="w7105"book="_idx" docset="nw312" tidref="i2599"NetWare idxid="w7106"book="_idx" docset="nw312" tidref="i4332"PartitionsYou can create a NetWare partition on any hard disk formatted at the factory or stamped as NetWare Ready. IDREF="FM35279"See "Format a Hard Disk" on page 56.If the hard disk has partitions on it that you want to delete, see IDREF="FM90101""Delete Partitions" on page 62. Then continue with the following steps.ProcedureLoad INSTALL.Select "Disk Options" from the "Installation Options" menu.Select "Partition Tables" from the "Available Disk Options" menu.Select the disk you need to partition from those listed on the "Available Disk Drives" menu. Screens similar to the following appear:LBL="1-10"INSTALL NetWare "Partition Type" and "Partition Options" screensFILE="n312sa30.pbm"If no partition table exists, you will see a message stating so. Press <Esc> to continue.Select "Create NetWare Partition" from the "Partition Options" menu.A form similar to the one below shows the total space on the hard disk and the blocks allocated to each function.LBL="1-11"INSTALL NetWare "Partition Information" screenFILE="n312sa31.pbm"NetWare automatically sets up the following configuration for the partition:All "Free Space" is assigned to the NetWare partition.The data area receives 98% of the available space.The idxid="w7107"book="_idx" docset="nw312" tidref="i2686"Hot Fix redirection area receives 2% of the available space.Some idxid="w7108"book="_idx" docset="nw312" tidref="i4458"NetWare-Ready hard disks leave a little free space even though you accept the defaults for using the whole disk for a NetWare partition. NetWare cannot use this free space.To reduce the partition size, enter the new size in the "Partition idxid="w7109"book="_idx" docset="nw312" tidref="i4332"Size" field.To change the size of the Data Area or the Hot Fix Redirection Area, press <Enter> or use the arrow keys to move to either field. Type the new number of blocks for that field and press <Enter>. NetWare automatically assigns any remaining space to the other field.If you change the size of the Hot Fix area after data is stored on the hard disk, all data is destroyed. Back up data before you change the size of the Hot Fix area.Press <Esc> and answer "Yes."Press <Esc> again.If you need to create a partition on more than one hard disk, select the next hard disk from the "Available Disk Drives" list and repeat Steps 3 through 9.ID="FM90101"Delete idxid="w7110"book="_idx" docset="nw312" tidref="i4332"PartitionsID="FM19220"You can use INSTALL to delete partitions (such as DOS, NetWare, or OS/2) on a hard disk. You may need to delete a partition for the following reasons:You are adding a hard disk that was previously used and you want to use the space for a NetWare v3.1x partition.The idxid="w7111"book="_idx" docset="nw312" tidref="i2686"Hot Fix Redirection Area needs to be increased because all the blocks have been used.If you delete a partition, you destroy all data on the partition. If the data is important, back it up. Then continue with the following steps.ProcedureLoad INSTALL.If the hard disk is mirrored, continue with Step 2.If the hard disk is not mirrored, skip to Step 3.Unmirror any hard disks associated with the partition. IDREF="FM54624"See "Unmirror Hard Disks" on page 67.Complete one of the following:If you are deleting the partition on the "Out Of Sync" partition, skip to Step 5.If you are deleting the partition on the "Not Mirrored" partition, continue with Step 4.Delete the volumes on the partition. IDREF="FM90088"See "Delete a Volume" on page 73.Select "Disk Options" from the "Installation Options" menu.Select "Partition Tables" from the "Available Disk Options" menu.If you have more than one hard disk, select the hard disk containing the target partition from the "Available Disk Drives" list.Select "Delete Partition" from the "Partition Options" menu.If more than one partition has been created on the hard disk, select the partition you want to delete from the "Available Partitions" menu.Answer "Yes" to the prompt to delete the partition.ID="FM65426"Edit Hot Fix InformationTo change the size of the Hot Fix Redirection Area on a hard disk, you must dismount all volumes and delete all volume information on that hard disk. These steps destroy all data on the hard disk.ProcedureBack up data that you want to save using a reliable backup utility.Load INSTALL.Complete one of the following:If the hard disk is mirrored, continue with Step 4.If the hard disk is not mirrored, skip to Step 6.Unmirror any hard disks mirrored to the target hard disk. IDREF="FM54624"See "Unmirror Hard Disks" on page 67.Complete one of the following:If you are changing the Hot Fix area on the "Not Mirrored" partition, continue with Step 6.If you are changing the Hot Fix area on the "Out Of Sync" partition, skip to Step 7.Delete the volumes. IDREF="FM90088"See "Delete a Volume" on page 73.Select "Disk Options" from the "Installation Options" menu.Select "Partition Tables" from the "Available Disk Options" menu.If you have more than one hard disk, select the target hard disk from "Available Disk Drives."Select "Change Hot Fix" from "Partition Options." A screen similar to the following appears:LBL="1-12"Changing Hot Fix from INSTALL NetWare "Partition Information" screenFILE="n312sa31.pbm"To change the size of either the Data Area or the Redirection Area, do the following: Press <Enter> or use the arrow keys to move to the field. Type the new number of blocks in that field, and press <Enter>. NetWare automatically assigns the remaining space to the other field.Verify the change to the Hot Fix Redirection Area. At least 2% of the NetWare partition should be in this area.Press <Esc> and select "Yes" at the "Change Partition Information?" prompt.Complete one of the following:If the hard disk was not mirrored, skip to Step 17.If the hard disk was mirrored, continue with Step 15.Select the other hard disk of the pair and repeat Steps 4 through 13. Remirror the hard disks IDREF="FM51767"See "Mirror or Duplex Hard Disks" on page 65.Recreate the volumes. IDREF="FM21946"See "Create a Volume" on page 71.Restore the files and directories to the volume.ID="FM51767"Mirror idxid="w7112"book="_idx" docset="nw312" tidref="i2599"idxid="w7113"book="_idx" docset="nw312" tidref="i3917"or idxid="w7114"book="_idx" docset="nw312" tidref="i2599"Duplex idxid="w7115"book="_idx" docset="nw312" tidref="i1754"Hard idxid="w7116"book="_idx" docset="nw312" tidref="i1585"DisksNetWare v3.1x protects data from hard disk failure by letting you duplicate (mirror) one hard disk's data on one or more other hard disks. When you mirror hard disks on different host bus adapters, this is called "duplexing." The INSTALL processes for mirroring and duplexing are the same.Mirrored and duplexed hard disks must have partitions of similar size (within several megabytes). In the mirroring process, NetWare makes adjustments so the mirrored partitions are exactly the same size.Although you can mirror eight partitions together, mirroring two partitions is usually sufficient.If a hard disk fails and cannot be accessed by the server, you can unmirror the hard disks and salvage the volume from the functional disk. IDREF="FM75070"See "Recover Volume Data from an Unmirrored Hard Disk" on page 55.To mirror two or more disks to each other, follow these steps.ProcedureLoad INSTALL.Select "Disk Options" from the "Installation Options" menu.ID="FM36772"Select "Mirroring" from the "Available Disk Options" menu. A "Partition Mirroring Status" list similar to the following appears:LBL="1-13"ID="FM48992"INSTALL "Partition Mirroring Status" listFILE="n312sa32.pbm"Each partition displays one of the following conditions:WIDTH="96"Not MirroredWIDTH="192"The partition is not currently  mirrored to another partition.MirroredThe partition is currently mirrored to  another partition.Out Of SyncThe partition was mirrored to another  partition, but is currently unmirrored  from that partition.Select the partition you want to mirror from the "Partition Mirroring Status" list.A "Mirrored idxid="w7117"book="_idx" docset="nw312" tidref="i4332"NetWare Partitions" list appears. The hard disks that are currently mirrored to the partition you selected appear in this list.The partition you select becomes the primary partition of the mirrored pair. For an explanation of how logical partitions relate to the installed hard disks see "book="concepts" docset="nw312"Device numbering" in Concepts.Press <Insert> and select a hard disk from the "Available Partitions" list.If you are mirroring hard disks, the status on the "Mirrored NetWare Partitions" list will show "Out Of Sync" for one of the disks. As soon as mirroring is completed, the status of both disks will be "In Sync."ID="FM54624"Unmirror Hard DisksBefore you can change the Hot Fix Redirection Area, delete a partition, or conduct surface tests, you must unmirror the mirrored hard disks.ProcedureLoad INSTALL.Select "Disk Options" from the "Installation Options" menu.ID="FM78953"Select "Mirroring" from the "Available Disk Options" menu.Select the "Mirrored" partition to unmirror from the "Partition Mirroring Status" list.Highlight the hard disk you want to unmirror in the "Mirrored NetWare Partitions" list and press <Delete>. For an explanation of the device number, see "book="concepts" docset="nw312"Device numbering" in Concepts.Press <Esc>; then select "Mirroring" again. The "Out Of Sync" status appears next to the disk you unmirrored.You can now repair or replace the hard disk, format the hard disk, delete the partition on the hard disk, change the Hot Fix Redirection Area, or salvage the volume information on the "Out Of Sync" partition.(Optional) If you want to allocate the unmirrored partition as a new volume segment: Highlight the partition and press <F3>, Answer "No" to the prompts.ID="FM14232"Test idxid="w7118"book="_idx" docset="nw312" tidref="i2599"Hard Disks for idxid="w7119"book="_idx" docset="nw312" tidref="i652"Bad idxid="w7120"book="_idx" docset="nw312" tidref="i716"BlocksUse the idxid="w7121"book="_idx" docset="nw312" tidref="i6603"surface idxid="w7122"book="_idx" docset="nw312" tidref="i6765"test to check a hard disk you are adding to the file server. The surface test runs in the background so you can work on other hard disks during the test. You must dismount the volumes on the disk being tested. Users should log out.Test for bad blocks when there is no activity on the file server. Otherwise, workstations connected to the file server may hang or appear to hang.You can run two types of tests:Destructive. This test destroys all data on the hard disk as it reads and writes test patterns. After the test is over, the disk still retains the test patterns. If you decide to run a destructive test, back up all data you want to save.Nondestructive. A nondestructive test pre-reads the data on the disk, writes and reads its test patterns, and then restores the original data. The nondestructive test protects your data but takes 20% longer to run than a destructive test.Complete the following steps to test your hard disk for bad blocks.ProcedureAt the console prompt dismount each volume on the hard disk by typing   DISMOUNT volume_name<Enter>Replace volume_name with a name of a volume on the disk. Repeat the step for each volume on the disk.Load INSTALL.Select "Disk Options" from the "Installation Options" menu.Select "Surface Test" from the "Available Disk Options" menu.If you have more than one hard disk on your file server, select the disk you want to check from the "Available Disk Drives" list. Screens similar to the following appear:LBL="1-14"ID="FM81056"INSTALL "Disk Surface Test Status" and "Surface Test Options" screensFILE="n312sa33.pbm"ID="FM52555"The "Test Type" field can show the following status information:WIDTH="96"NoneWIDTH="192"The partition is not being tested.FailedA disk error occurred that Hot Fix  could not correct.CompletedThe test was successful.TerminatedThe test was stopped. All data on the  hard disk will be lost.Nondestructive  DestructiveData on the hard disk will be  preserved.Select "Begin Surface Test" from the "Surface Test Options" menu.Select the type of test. Remember, destructive destroys all data; nondestructive protects your data.For a complete test, let the test run several hours until the number of blocks tested is equal to the total blocks listed on the status screen.To end the test before it finishes, select "Stop Surface Test" from the "Surface Test Options" menu.To perform other file server operations while the surface test is running (such as testing other hard disks), press <Esc> to move to the other options in INSTALL, or press <Alt><Esc> to go to the console prompt.All testing will stop if you exit INSTALL.At the end of the test, the "Disk Surface Test Status" form displays the number of blocks tested, the number of bad blocks found, and the total blocks tested. The "Test Type" field displays "Terminated" or "Completed."ID="FM21946"Create a idxid="w7123"book="_idx" docset="nw312" tidref="i7372"VolumeYou can create a new volume on any hard disk that has a NetWare v3.1x partition. Your file server can have up to 64 volumes. The needs of your users determines how many volumes you need on your file server; the operating system requires only one volume, SYS:, to function properly. For suggestions on setting up your volumes, see "book="concepts" docset="nw312"Volumes" in Concepts.To reduce the size of a volume, you must delete it (and the data) first, and then recreate it with a smaller size. If your system will have more than one volume, we recommend that you leave a few megabytes unassigned to any volume. This reserve can later be assigned to the volume that is in critical need of more disk space.Complete the following steps to create a volume.ProcedureLoad INSTALL.Select "Volume Options" from the "Installation Options" menu.When the "Volumes" list appears, press <Insert>.Multiple hard disks. If you have more than one hard disk with available disk space, a "Free Space Available for Volume Segments" list appears. Select the disk you want to create the volume on. The "New Volume Information" form appears. One hard disk. If only one hard disk has available disk space, the "New Volume Information" form appears:LBL="1-15"INSTALL "New Volume Information" screenFILE="n312sa34.pbm"To name the volume, highlight the "Volume Name" field and enter the name of the new volume.Press <Enter> to move to the next field; then enter the idxid="w7124"book="_idx" docset="nw312" tidref="i712"block size idxid="w7125"book="_idx" docset="nw312" tidref="i7372".Consider the following points as you decide which block size is best:The default block size is 4 KB.Block size must be the same on all segments of a volume. Once a block size has been selected, it cannot be changed for additional segments.Small block sizes require more file server memory to track the File Allocation and Directory Entry Tables. Large block sizes use more disk space because small files must be assigned at least one block.Larger block sizes are best for large database records.DOS utilities may calculate the amount of free disk space incorrectly if you select large block sizes (32 KB or 64 KB).Press the Down-arrow key to move to the "Initial Segment Size" field.Complete one of the following:To assign the entire available segment to the volume, skip to Step 11.To calculate the number of blocks to assign to the volume, continue with Step 8.Divide the size of a megabyte (1024) by the selected block size.1024/4 = 256 blocks per megabyte1024/8 = 128 blocks per megabyteMultiply the number of blocks per megabyte by the number of megabytes you want to allocate.256 x 25MB = 6400128 x 25MB = 3200Enter the number calculated in Step 9 in the "Initial idxid="w7126"book="_idx" docset="nw312" tidref="i7372"Segment Size" field.To create the volume with the configuration entered in the "New Volume Information" form, press <Esc> and answer "Yes" to the prompt to create the volume.With the new volume name highlighted, press <Enter> to return to the "Volume Information" screen.Highlight the "Status" field and press <Enter>.Select "Mount Volume."ID="FM90088"Delete a idxid="w7127"book="_idx" docset="nw312" tidref="i7372"Volume idxid="w7128"book="_idx" docset="nw312" tidref="i7372"You can delete volumes as needed. Complete these steps while the network is up.ProcedureUse MONITOR to determine who has files opened on the volume. Use BROADCAST to tell users to move to another volume.Back up any data you want to save from the volume you intend to delete.Load INSTALL.Select "Volume Options" from the "Installation Options" menu.Select the volume you want to delete.Highlight the "Status" field and press <Enter>.Select "Dismount Volume."Press <Esc> to return to the "Volumes" list.Highlight the volume and press <Delete>.Answer "Yes" to the prompt to delete the volume.ID="FM49080"Rename a VolumeYou can use INSTALL to rename a volume. To rename volume SYS:, dismount SYS:, create another volume, and name the new volume "SYS:".To rename a volume, complete the following steps.ProcedureUse MONITOR to determine if users have files opened on the volume. Use BROADCAST to tell users to move to another the volume.Load INSTALL.Select "Volume Options."Select the volume you want to rename. The "Volume Information" form appears:LBL="1-16"Renaming a volume from INSTALL "Volume Information" formFILE="n312sa35.pbm"Highlight the "Status" field and press <Enter>.Select "Dismount Volume."Move to the "Volume Name" field.Type the new name of the volume over the old name and press <Enter>.Answer "Yes" at the prompt to change the volume name.To mount the newly named volume, highlight the "Status" field and press <Enter>.Select "Mount Volume."ID="FM92037"Increase the idxid="w7129"book="_idx" docset="nw312" tidref="i7372"Size of a VolumeA volume can have multiple segments spanning multiple hard disks. This allows you to add a hard disk when you need to expand a given volume.Keep the following idxid="w7130"book="_idx" docset="nw312" tidref="i7372"requirements in mind as you expand volumes:The maximum number of segments in a volume is 32.The maximum number of segments you can create on one hard disk is 8.The maximum number of volumes is 64.You can add segments to a volume without destroying data, but you cannot remove the segments without destroying data.You can increase the size of a volume in two ways:Add a new volume segment on the same hard disk as the volume.Add a new volume segment by adding a segment from a new hard disk.To add another segment to an existing volume, complete the following steps.ProcedureLoad INSTALL.Select "Volume Options" from the "Installation Options" menu.From the "Volumes" list, select the volume you want to add the segment to. A form similar to the following appears.LBL="1-17"Adding volume segments from the INSTALL "Volume Information" screenFILE="n312sa35.pbm"Select the "Volume Segments" field. A list of the current segments in the selected volume appears.Press <Insert>. One of the following happens:If more than one free area exists, a list of disks with free areas appears. Select the hard disk from the list. Then continue with Step 6.If only one disk has a free area, the disk is selected for you. Continue with Step 6.If no free areas exist, nothing happens. A hard disk needs to be added to the file server and a NetWare partition created on the disk before you can select a segment. IDREF="FM92680"See "Add a Hard Disk to the File Server" on page 51.Type the number of blocks you want in the new volume segment and press <Enter>. The default number is the whole area. We recommend that you leave an unassigned segment of at least 6 MB on one hard disk.Answer "Yes" at the prompt to add a new segment to the volume.ID="FM86774"Copy the idxid="w7131"book="_idx" docset="nw312" tidref="i6656"SYSTEM and idxid="w7132"book="_idx" docset="nw312" tidref="i5696"PUBLIC idxid="w7133"book="_idx" docset="nw312" tidref="i2300"FilesYou can recopy the SYSTEM and idxid="w7134"book="_idx" docset="nw312" tidref="i2300"PUBLIC utility files from diskette onto volume SYS: using INSTALL. INSTALL automatically assigns the proper attributes to the files. If you copy the files any other way, they will not be assigned the proper attributes and they might be deleted.Do not just rely on INSTALL to restore all files in the SYS:SYSTEM and SYS:PUBLIC directories. Use a backup utility to back up these directories. If you accidentally delete volume SYS:, the AUTOEXEC.NCF file and the system login script will be destroyed, and you will have to recreate them.To recopy the SYSTEM and PUBLIC files, complete the following steps.ProcedureLoad INSTALL. If volume SYS: is not mounted, you have to load INSTALL from the hard disk or the System_2 diskette.Select "System Options" from the "Installation Options" menu.Select "Copy System and Public Files" from the "Available System Options" menu. Insert the System_2 diskette into drive A: as prompted.Follow the system prompts to insert the remaining diskettes.If you want to skip one or more diskettes after copying the first one, press <F7>. Then answer "Yes." Repeat this procedure to continue skipping diskettes until you come to the one you want to copy.If security is a priority, copy INSTALL.NLM to another secured directory. Then delete INSTALL.NLM from the SYS:SYSTEM directory. This will prevent an intruder who has gained access to the file server console from deleting volumes and partitions.ID="FM10084"Change the idxid="w7135"book="_idx" docset="nw312" tidref="i2034"File Server's idxid="w7136"book="_idx" docset="nw312" tidref="i2107"NameYou can change the file server's name by using the FILE SERVER NAME command in the AUTOEXEC.NCF file. The next time the server is booted, the file server will be assigned the new name.ProcedureLoad INSTALL.Select "System Options" from the "Installation Options" menu.Select "Edit AUTOEXEC.NCF file" from the "Available System Options" menu.Locate the present server name in the file and type the new name over the old one.The name can have as many as 47 characters, but only 10 will show in any of the system messages. Do not use spaces or any of the following characters:" * + , \ / | ; : = < > ? [ ] .Press <Esc> and answer "Yes" to the "Save Changes" prompt.Press <Alt><Esc> to return to the console prompt.Use SEND to broadcast a message to all users to log out.Down the file server by typing  DOWN <Enter>Reboot the file server:The new name will be in effect once the server is up.You may need to change drive mappings in the system login script and the user login scripts to reflect the file server's new name. You may also need to change the workstations' AUTOEXEC.BAT files.ID="FM30120"Change the idxid="w7137"book="_idx" docset="nw312" tidref="i2034"File Server's idxid="w7138"book="_idx" docset="nw312" tidref="i2107"Internal idxid="w7139"book="_idx" docset="nw312" tidref="i2933"Network NumberYou can use the IPX INTERNAL NET command in the AUTOEXEC.NCF file to change the file server's internal network number. The next time the file server boots, it has the new internal network number.ProcedureLoad INSTALL.Select "System Options" from the "Installation Options" menu.Select "Edit AUTOEXEC.NCF file" from the "Available System Options" menu.Locate the IPX INTERNAL NET command in the file and type the new number for the server over the old number. The number must be one of these:A hexadecimal number (base 16, using numbers 0 through 9 and letters A through F)One to eight digits longPress <Esc> and answer "Yes" to the "Save Changes" prompt.Press <Alt><Esc> to return to the console prompt.Use SEND to broadcast a message to all users to log out.Down the file server by typing  DOWN <Enter>Reboot the file server.The new internal network number will be in effect once the server is brought up.ID="FM97050"Create the idxid="w7140"book="_idx" docset="nw312" tidref="i595"AUTOEXEC.NCF FileThe AUTOEXEC.NCF file is a batch file (similar to a DOS batch file) that contains idxid="w7141"book="_idx" docset="nw312" tidref="i1218"commands that execute after the NetWare operating system is booted and STARTUP.NCF is executed. This file is stored in the SYS:SYSTEM directory and is executed after volume SYS: has been mounted. After AUTOEXEC.NCF executes, the file server becomes accessible from attached workstations.The operating system uses the AUTOEXEC.NCF file to complete the boot process for the file server. More specifically, the file provides the following types of configuration information:The file server's nameThe internal network numberLOAD commands for LAN driversBIND commands to bind communication protocols to the LAN driversThe network numbers for the LAN driversLOAD commands for loadable modules such as MONITOR and PSERVERCommands to mount volumesCommands to execute console commands such as SET parametersIf the file server's AUTOEXEC.NCF file has been deleted, complete the following steps to recreate it.ProcedureLoad INSTALL.Select "System Options" from the "Installation Options" menu.Select "Create AUTOEXEC.NCF file" from the "Available System Options" menu.Press <Esc> and answer "Yes" to the prompt to create the AUTOEXEC.NCF file.For further information about creating the file during initial installation, see Chapter 2, "book="install" docset="nw312"File Server Installation" in Installation and Upgrade.For details on the commands that can be included in the file, see the next section, IDREF="FM38546""Edit the AUTOEXEC.NCF File."ID="FM38546"Edit the idxid="w7142"book="_idx" docset="nw312" tidref="i595"AUTOEXEC.NCF FileYou can change commands in the AUTOEXEC.NCF file. However, these changes do not affect the configuration of the file server until the file server is rebooted. Usually, you change the file server's configuration with a console command and then save the command in the file. This procedure ensures that the command executes the next time the file server is booted.You can execute console commands, load loadable modules, change SET parameters, or execute file server batch file commands with the AUTOEXEC.NCF file.ProcedureLoad INSTALL.Select "System Options" from the "Installation Options" menu.Select "Edit AUTOEXEC.NCF file" from the "Available System Options" menu.Place any of the commands discussed in the following sections at the end of the file.You can also use a text editor to create other file server batch files that include these commands. Add an .NCF extension to any files created this way. If the file is copied to the SYS:SYSTEM directory, the file can then be executed at the console by typing the filename.Loadable idxid="w7143"book="_idx" docset="nw312" tidref="i3278"idxid="w7144"book="_idx" docset="nw312" tidref="i3935"Modules  LOAD INSTALL  LOAD MONITOR  LOAD PSERVERFor more information on loadable module commands, see the documentation for the loadable module.LAN idxid="w7145"book="_idx" docset="nw312" tidref="i3123"Driver idxid="w7146"book="_idx" docset="nw312" tidref="i595"CommandsThe following sample commands are preceded with a comment line that explains what the command loads.To load the NE2000 driver the first time:  LOAD NE2000 PORT=300 INT=3To load the NE2000 driver with a frame type:  LOAD NE2000 PORT=3000 INT=3 FRAME=ETHERNET_IIFor more information on LAN driver commands, IDREF="FM79039"see "LOAD LAN driver" on page 122BIND CommandsThe following sample commands are preceded with a comment line that explains what the command binds.To bind a protocol to a driver that is loaded once:  BIND IPX NE2000 NET=26To bind to a driver that is loaded more than once:  BIND IPX NE2000 [PORT=340 INT=4 FRAME= ETHERNET_802.3] NET=27BIND should follow the LOAD command for the LAN driver. For more information, IDREF="FM75419"see "BIND" on page 8idxid="w7147"book="_idx" docset="nw312" tidref="i6296"SET CommandsThe following SET commands indicate the default parameter on the first line and the parameter limits on the second line.  Set Minimum File Cache Report Threshold=20  #Limits: 0 to 1000  Set Minimum Directory Cache Buffers=20  #Limits: 10 to 2000  Set Minimum File Delete Wait Time=1 minute 5.9 seconds  #Limits: 0 seconds to 7 days  Set File Delete Wait Time=5 minutes 29.6 seconds  #Limits: 0 seconds to 7 days  Set Maximum Packet Receive Buffers=100  #Limits: 50 to 2000  Set Allow Unencrypted Passwords=OFFNetWare v3.1x supports encrypted passwords. To allow NetWare v2.x users to access NetWare v3.1x file servers, set this command to ON in the AUTOEXEC.NCF file and upgrade the NetWare v2.x file servers with NetWare v3.1x utilities. For details on updating NetWare v2.x file servers, see Chapter 2, "book="install" docset="nw312"Upgrade: Follow-Up After Upgrade," inInstallation and Upgrade.For more information on parameters for SET commands, IDREF="FM73882"see "SET" on page 258idxid="w7148"book="_idx" docset="nw312" tidref="i1218"Console Commands  MOUNT  REMOVE DOS  SECURE CONSOLE  SPOOL  TRACK ON  UPS STATUSFor more console commands and for more information, refer to the individual commands discussed in this manual.ID="FM21207"File Server Batch File Commands  #  ECHO  FILE SERVER NAME  IPX INTERNAL NET  #. The pound sign allows you to put remarks in the file so that you can remember why a command was added to the file.ECHO. When the file server is booting, the default for ECHO is set to OFF. The file server does not display any of the commands from the boot files. The file server does, however, display the results of the commands as they are executed.ECHO ON allows the file server to display commands on the screen as they are executed.Use ECHO ON to troubleshoot errors in the AUTOEXEC.NCF file. If commands are not executing properly when the file server boots, add the ECHO ON command as the first line in the file. Then, as the file is executed, the commands and the results are displayed.The command preceding the error message is the command you need to edit.The default is ECHO OFF.FILE SERVER NAME. This command assigns a name to the file server as it boots. If you need to change the name of your file server, change the name in the AUTOEXEC.NCF file; then reboot the file server. (IDREF="FM10084"See "Change the File Server's Name" on page 79.)IPX INTERNAL NET. This command assigns the internal network number for the file server. If you need to change the internal network number, change the number in the AUTOEXEC.NCF file; then reboot the file server. (IDREF="FM30120"See "Change the File Server's Internal Network Number" on page 80.)ID="FM28664"Create idxid="w7149"book="_idx" docset="nw312" tidref="i6489"the idxid="w7150"book="_idx" docset="nw312" tidref="i1561"STARTUP.NCF idxid="w7151"book="_idx" docset="nw312" tidref="i1218"FileThis file, stored on either the file server boot diskette or the DOS partition, provides the file server with the commands it needs to load any disk drivers or name space modules (*.NAM). After the commands in this file execute, the server searches for the AUTOEXEC.NCF file to continue the boot process.You created this file during the initial installation process. If the file server's STARTUP.NCF file is missing, complete the following steps to recreate it.ProcedureLoad INSTALL.Select "System Options" from the "Installation Options" menu.Select "Edit STARTUP.NCF file" from the "Available System Options" menu.If the path to STARTUP.NCF is drive C:, press <Home> and change A: to C:.Press <Enter> and then <Esc>.Answer "Yes" to the prompt to create the STARTUP.NCF file.ID="FM81822"For details on the commands that can be included, see the next section, IDREF="FM34636""Edit the STARTUP.NCF File."For instructions on creating this file during initial installation, see Chapter 3, "book="install" docset="nw312"File Server Installation," in Installation and Upgrade.ID="FM34636"Edit idxid="w7152"book="_idx" docset="nw312" tidref="i6489"the STARTUP.NCF FileYou can change the STARTUP.NCF file at any time. However, these changes do not affect the configuration of the file server until the file server is rebooted. Usually you change the file server's configuration with a console command, and then save the command in the file. This procedure ensures that the command executes the next time the file server is booted.However, some commands cannot be entered at the console, but must be entered in the STARTUP.NCF file. Then you must reboot the file server for the new configuration to take effect.To edit the STARTUP.NCF file, complete the following steps.ProcedureLoad INSTALL.Select "System Options" from the "Installation Options" menu.Select "Edit STARTUP.NCF file" from the "Available System Options" menu.If the path to STARTUP.NCF is drive C:, press <Home> and change A: to C:.You can place any of the commands discussed in the following sections at the end of the file.You can also use a text editor to create other startup files. Give the file a unique name and an .NCF extension. If the file is stored in the file server's boot directory, you can execute this file, rather than the default STARTUP.NCF file, by using a SERVER parameter. IDREF="FM49124"See "SERVER" on page 254.Disk idxid="w7153"book="_idx" docset="nw312" tidref="i3278"Driver idxid="w7154"book="_idx" docset="nw312" tidref="i3935"CommandsIn the following commands, the default parameters are given for the drivers that require parameters:  LOAD ISADISK INT=E PORT=1F0  LOAD PS2ESDI  LOAD DCB PORT=340  LOAD PS2MFM  LOAD PS2SCSI SLOT=1For more information on the commands, IDREF="FM53960"see "LOAD disk driver" on page 107Name idxid="w7155"book="_idx" docset="nw312" tidref="i3992"Space Commands  LOAD MAC  LOAD NFS  LOAD OS2ID="FM89384"File Server Batch File Commands  #  ECHO OFF/ONFor an explanation of batch file commands, see IDREF="FM21207""File Server Batch File Commands" on page 85.idxid="w7156"book="_idx" docset="nw312" tidref="i6296"SET ParametersThe following SET commands indicate the default on the first line and the limits on the second line. For more information on SET parameters, IDREF="FM73882"see "SET" on page 258  Set Cache Buffer Size=4096 (bytes)Limits: 4096 to 16384  Set Display Disk Device Alerts=OFF  Set Display Relinquish Control Alerts=OFFID="FM23830"Install idxid="w7157"book="_idx" docset="nw312" tidref="i2869", idxid="w7158"book="_idx" docset="nw312" tidref="i2034"Uninstall, or idxid="w7159"book="_idx" docset="nw312" tidref="i1134"Configure a idxid="w7160"book="_idx" docset="nw312" tidref="i5596"Product on the idxid="w7161"book="_idx" docset="nw312" tidref="i2034"File ServerINSTALL's "Product Options" feature allows you to work with NetWare products like name space modules and SBACKUP. To install, uninstall, or configure a product, complete the following steps. When you use the "Product Options" feature of INSTALL, BTRIEVE and CLIB are automatically loaded.Information about currently installed products and their current configuration options is in SYS:SYSTEM\PRODUCTS.DAT (a BTRIEVE database).ProcedureLoad INSTALL.Select "Product Options" from the "Installation Options" menu. The "Currently Installed Products" list appears. If no products are currently installed, the list is empty.To uninstall a product, delete it from the list. To install a product, press <Insert> and follow the prompts. To set configuration options for a product, select that product from the list.ID="FM53765"Some products may not have configuration or uninstall options. A message explaining this appears if you try to perform unsupported operations. For further installation instructions and configuration options, refer to the documentation on the product.ID="FM84140"Exit idxid="w7162"book="_idx" docset="nw312" tidref="i2828"INSTALLYou can exit INSTALL by pressing <Esc> until the exit prompt appears, or, you can exit temporarily by pressing the hot key.EscapeThis form of exit unloads INSTALL and frees up memory.Press <Esc> until the "Exit Install" prompt appears, and then answer "Yes." The console prompt appears.Hot KeyINSTALL, as well as the other file server menu utilities, allows you to exit the program temporarily by pressing <Alt><Esc>.The module is still loaded, and you can press <Alt><Esc> to return to INSTALL at any time.IPXSWhy Use idxid="w7163"book="_idx" docset="nw312" tidref="i3300"IPXS?Use idxid="w7164"book="_idx" docset="nw312" tidref="i3028"IPXS idxid="w7165"book="_idx" docset="nw312" tidref="i2127"if you have an NLM that requires idxid="w7166"book="_idx" docset="nw312" tidref="i6540"idxid="w7167"book="_idx" docset="nw312" tidref="i6540"STREAMS-based IPX idxid="w7168"book="_idx" docset="nw312" tidref="i3005"protocol idxid="w7169"book="_idx" docset="nw312" tidref="i5640"idxid="w7170"book="_idx" docset="nw312" tidref="i1081"services idxid="w7171"book="_idx" docset="nw312" tidref="i1087".Command Format  LOAD [path]IPXSCommand ParametersReplace path with a full path to IPXS.NLM. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path and volume SYS: is mounted, the operating system looks for IPXS in SYS:SYSTEM. (Use SEARCH to set up more paths.)Additional InformationDo not unload a protocol-stack NLM such as IPXS until you have unloaded all applications that are potentially using it.To use IPXS, load these modules in the following order:STREAMSCLIBidxid="w7172"book="_idx" docset="nw312" tidref="i6800"TLIIPXSLoad IPXSTo load IPXS, type  LOAD IPXS <Enter>ID="FM89343"KEYBWhy Use KEYB?Use KEYB to change the idxid="w7173"book="_idx" docset="nw312" tidref="i3060"keyboard idxid="w7174"book="_idx" docset="nw312" tidref="i3150"type for the NetWare idxid="w7175"book="_idx" docset="nw312" tidref="i4393"server console.Command Format  LOAD [path]KEYB [parameter]Command ParametersReplace path with the full path to the directory containing KEYB.NLM. Replace parameter with the keyboard type you want. The following types are available:English (United States)FrenchGermanItalianSpanishLoad KEYBTo load KEYB, type  LOAD KEYB [parameter] <Enter>If you load KEYB without entering a keyboard parameter, a list of the available keyboards is displayed.LIST idxid="w7176"book="_idx" docset="nw312" tidref="i3224"DEVICESWhy Use idxid="w7177"book="_idx" docset="nw312" tidref="i2127"LIST DEVICES?Use LIST DEVICES to display idxid="w7178"book="_idx" docset="nw312" tidref="i1402"device information for the server.Command Format  LIST DEVICESDisplay Device InformationTo display device information for the server, type  LIST DEVICES <Enter>Additional InformationA idxid="w7179"book="_idx" docset="nw312" tidref="i1402"device can be a disk driver, tape driver, optical disk driver, or any other storage device driver.ID="FM19779"LOADWhy Use idxid="w7180"book="_idx" docset="nw312" tidref="i3252"LOAD?Use idxid="w7181"book="_idx" docset="nw312" tidref="i2127"LOAD idxid="w7182"book="_idx" docset="nw312" tidref="i2127"to idxid="w7183"book="_idx" docset="nw312" tidref="i3278"link idxid="w7184"book="_idx" docset="nw312" tidref="i2119"modules to the operating system.Exercise caution when selecting loadable modules to allow on the file server. If you are unsure of the source or the purpose of the module, you may want to first test the module in a secure environment that you can easily recover. Loadable modules supplied by Novell have been tested prior to release.This section describes the following tasks:WIDTH="264"TaskWIDTH="48"PageWIDTH="264"idxid="w7185"book="_idx" docset="nw312" tidref="i4306"Load a moduleWIDTH="48"IDREF="FM67110"97Troubleshoot LOADIDREF="FM68201"98See the following pages for each module type.WIDTH="264"Module typeWIDTH="48"PageWIDTH="264"idxid="w7186"book="_idx" docset="nw312" tidref="i3278"Disk driversWIDTH="48"IDREF="FM40291"107LAN driversIDREF="FM89882"122Name spaceIDREF="FM62696"158NLM utilitiesIDREF="FM87679"164Command Format  LOAD [path]loadable_module [parameter...]Command ParametersReplace path with a full path to the directory containing the loadable module. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path and volume SYS: has not yet been mounted, the operating system assumes that the loadable module is located in the default DOS directory. Once volume SYS: is mounted, the operating system assumes that the loadable module is located in the SYS:SYSTEM directory. (Use SEARCH to set up additional paths for automatic searching.)Replace loadable_module with an option from one of the four types of loadable modules:Disk driversLAN driversName spaceNLM utilitiesEach type of loadable module is described in the following sections. Each description includes a list of modules being shipped with the operating system.Consult NetWire, your Novell Authorized Reseller, or third-party dealers for other available loadable modules.idxid="w7187"book="_idx" docset="nw312" tidref="i1561"Disk DriversLoadable modules for disk drivers establish communication between the operating system and the hard disks' controller boards.For an explanation of how to load disk drivers and for a list of parameters that can be used with disk drivers, IDREF="FM53960"see "LOAD disk driver" on page 107idxid="w7188"book="_idx" docset="nw312" tidref="i3278"LAN Drivers idxid="w7189"book="_idx" docset="nw312" tidref="i3085"Loadable modules for LAN drivers establish communication between the operating system and the network boards installed in the file server.For an explanation of how to load LAN drivers and for a list of parameters that can be used with LAN drivers, IDREF="FM79039"see "LOAD LAN driver" on page 122idxid="w7190"book="_idx" docset="nw312" tidref="i3278"Name Space idxid="w7191"book="_idx" docset="nw312" tidref="i3992"Loadable modules for name space link non-DOS naming conventions to the operating system. Once linked, the naming convention can be assigned to the volumes on the file server; those volumes can then store files created with the specific type of naming convention.For an explanation of how to load name space, IDREF="FM50686"see "LOAD name space" on page 158idxid="w7192"book="_idx" docset="nw312" tidref="i3278"idxid="w7193"book="_idx" docset="nw312" tidref="i4603"NLM UtilitiesLoadable modules for NetWare Loadable Module (NLM) utilities link management and enhancement programs with the operating system. These utilities can include the following types of programs: installation, monitor, volume repair, backup, print server, database server, communication gateway, and diagnostic.For an explanation of how to load these NLM utilities, IDREF="FM52889"see "LOAD NLM utility" on page 164Additional InformationA loadable module links itself to the operating system and allocates a portion of the file server's memory for its use.Some modules, such as LAN drivers and disk drivers, need to be loaded every time the file server is booted. Other modules, such as the NLM utilities, can be loaded, used, and then unloaded. When modules are unloaded, all allocated resources are returned to the operating system.idxid="w7194"book="_idx" docset="nw312" tidref="i3935"If you want modules to be loaded automatically when the file server boots, you must store the LOAD commands in either the AUTOEXEC.NCF file or the STARTUP.NCF file. For instructions on editing the .NCF files, IDREF="FM11821"see "INSTALL" on page 47When you install the SYSTEM and PUBLIC files, .NLM, .LAN, and .NAM loadable modules are copied to the SYS:SYSTEM directory. You must copy the .DSK and .NAM modules that your system uses to the boot directory of the file server. For instructions, see Chapter 3, "book="install" docset="nw312"File Server Installation," in Installation and Upgrade. For a complete description of the types of loadable modules, see "book="concepts" docset="nw312"Loadable Module" in Concepts.ID="FM67110"Load idxid="w7195"book="_idx" docset="nw312" tidref="i3252"a ModuleHow you load a module depends on where it is. You can copy a module to and load it from any of the following partitions:A diskette in the floppy disk drive of the file serverA DOS partition on the file serverNetWare directories on the file serverExamples of loading MONITOR from each source are in the following sections. To set up search paths to other directories, IDREF="FM12543"see "SEARCH."idxid="w7196"book="_idx" docset="nw312" tidref="i3935"SYS:SYSTEM directoryYou can load any module that has been copied to the SYS:SYSTEM directory as long as volume SYS: is mounted. To load MONITOR, for example, type  LOAD MONITOR <Enter>idxid="w7197"book="_idx" docset="nw312" tidref="i3935"Floppy disk driveYou can load any module on a diskette from the file server's floppy disk drive. To load MONITOR, for example, insert a diskette with the MONITOR module into drive A: of the file server and type  LOAD A:MONITOR <Enter>If you have removed DOS with the REMOVE DOS or SECURE CONSOLE command, you cannot load a module from drive A:.idxid="w7198"book="_idx" docset="nw312" tidref="i3935"DOS partitionIf you have set up your file server to boot from a DOS partition, you can load any module from the DOS partition that you have copied to it. ID="FM36928"To load MONITOR, for example, type  LOAD C:MONITOR <Enter>If you have removed DOS with the REMOVE DOS or SECURE CONSOLE command, you cannot load a module from the DOS partition.idxid="w7199"book="_idx" docset="nw312" tidref="i3935"NetWare directoryYou can load a module from any directory on the file server as long as the module has been copied to the directory. To load MONITOR from the SYS:MODULES directory, for example, type  LOAD SYS:MODULES/MONITOR <Enter>If you have used SECURE CONSOLE, you cannot load modules from any network directory other than SYS:SYSTEM.ID="FM68201"idxid="w7200"book="_idx" docset="nw312" tidref="i3935"Troubleshoot idxid="w7201"book="_idx" docset="nw312" tidref="i3278"LOAD idxid="w7202"book="_idx" docset="nw312" tidref="i6910"idxid="w7203"book="_idx" docset="nw312" tidref="i3252"All loadable modules that you link to your operating system should be approved by Novell, Inc. If you are running third-party loadable modules, check with NetWire or ask your Novell Authorized Reseller for a list of approved modules. If you load a module that is not approved, your server may abend or data may become corrupted.Occasionally a loadable module displays warnings as it loads, or it does not load at all. These problems and their possible solutions are described in the following sections.idxid="w7204"book="_idx" docset="nw312" tidref="i205"Warning idxid="w7205"book="_idx" docset="nw312" tidref="i3278"MessagesIf you load NetWare v3.0 modules on a NetWare v3.1x file server, you will receive warning messages that the module is using old API calls. The following message is displayed on the file server console:  This module is using <number> old API calls Contact the module vender regarding the availability of a newer moduleNetWare after v3.0 changed some API calls to include resource tagging. Resource tagging ensures that the loadable modules return all allocated resources to the operating system when unloaded. The old API calls still work; however, they are slower than the new 3.1x API calls. Contact the vender of the module for an updated version that uses the new API calls.Module Will Not LoadModules will not load when one or more of the following conditions exist:The file server cannot find the loadable module.The file server does not have enough free memory to load another module.The loadable module depends on another loadable module.An invalid parameter is specified when the module is loaded from the console prompt.LOAD is not entered before the module name.An invalid command is entered in the .NCF files.Possible solutions for these problems are described in the following sections.The File Server Cannot idxid="w7206"book="_idx" docset="nw312" tidref="i3278"Find the ModuleWhen the operating system cannot find the module, it usually returns the message "Unable to find load file filename."The solution depends upon whether volume SYS: is mounted. Use VOLUMES to list the mounted volumes.If volume SYS: is mounted, go to "volume SYS: mounted" on page IDREF="FM73829"100.If volume SYS: is not mounted, go to "volume SYS: not mounted" on page IDREF="FM87018"101.If volume SYS: will not mount, go to "volume SYS: will not mount" on page IDREF="FM99143"101.Volume ID="FM73829"SYS: mounted. If SYS: is mounted but the module is not in SYS:SYSTEM, use one of the following methods to change the search path of the operating system:Specify the path with the LOAD command. For examples, see IDREF="FM67110""Load a Module" on page 97.Use the SEARCH command to add search drives to the operating system.The operating system's search is limited if you have issued the SECURE CONSOLE or REMOVE DOS commands.SECURE CONSOLE. If you have issued the SECURE CONSOLE command, the operating system looks only in the SYS:SYSTEM directory for a loadable module. To load a module that is not in the SYS:SYSTEM directory, do either of the following:Remove the SECURE CONSOLE command from the AUTOEXEC.NCF file (if you have added it to the file). Down the file server; then reboot the server to disable the SECURE CONSOLE command.Copy the module into the SYS:SYSTEM directory from a workstation.REMOVE DOS. If you have issued the REMOVE DOS command, the operating system cannot load modules from any DOS drive. Copy the module to the SYS:SYSTEM directory; then load the module.Volume ID="FM87018"SYS: not mounted. Loadable modules are normally kept in two areas: the SYS:SYSTEM directory and the file server boot directory.When the operating system is first installed, all loadable modules (except disk drivers) are copied into the SYS:SYSTEM directory; the operating system automatically looks in SYS:SYSTEM for the module.If the module is in the SYS:SYSTEM directory, mount the SYS volume.If the module is not in the SYS:SYSTEM directory, For examples on how to specify a path, see IDREF="FM67110""Load a Module" on page 97.Volume ID="FM99143"SYS: will not mount. If SYS: will not mount, a number of possible causes exist; however, only one is related to loadable modules. For other causes, see IDREF="FM14588""Troubleshooting Guide" on page 385.The operating system needs to be able to find the necessary loadable modules to mount SYS:. For example, the operating system must be able to find the disk driver module for the disk that contains SYS:. Also, if SYS: stores non-DOS files, the operating system must be able to find the name space module.The following conditions can prevent volume SYS: from mounting:The disk drivers and name space modules are not in the same directory as the file server boot files.An incorrect path is specified in the command to load the disk drivers or name space modules.The commands to load the disk drivers or name space modules are not in the STARTUP.NCF file.Complete one or more of the following procedures:If you have not loaded the necessary name space and disk drivers and you have used REMOVE DOS or SECURE CONSOLE, down the file server.Then copy the necessary modules to the boot directory and reboot the file server. (Boot the file server without the AUTOEXEC.NCF file if that file contains the REMOVE DOS or SECURE CONSOLE command. IDREF="FM49124"See "SERVER" on page 254.)If your file server boots from a DOS partition, load the necessary modules from drive A:. Then use RCONSOLE to copy the modules to the DOS partition.If your file server boots from a floppy diskette, copy the disk drivers and name space modules to the diskette. Then load the modules.Edit the STARTUP.NCF file and correct the path for the disk driver or name space module.Enter the commands to load the disk drivers and name space modules at the console prompt, and then add the commands to the STARTUP.NCF file.For the proper syntax for these commands, IDREF="FM50686"see "LOAD name space" on page 158 or IDREF="FM53960""LOAD disk driver" on page 107.The File Server Does Not Have Enough Free idxid="w7207"book="_idx" docset="nw312" tidref="i3278"MemoryUse MONITOR to view the memory allocations. Do one or more of the following:Unload some of your loaded modules.Use SET to change memory allocations. If the "Alloc Memory Pool" statistic ("Server Memory Statistics" window in MONITOR) is near the default of 8,000,000 bytes, increase this pool. (IDREF="FM72268"See "Maximum Alloc Short Term Memory = number" on page 280.)For instructions on saving the new settings in the AUTOEXEC.NCF file, IDREF="FM11821"see "INSTALL" on page 47Add more memory to the file server. If the "Cache Buffers" statistic ("Server Memory Statistics" window in MONITOR) is near 20%, the file server needs more memory before it can load any more modules.The Module Is idxid="w7208"book="_idx" docset="nw312" tidref="i3278"Dependent on another ModuleSome modules depend on others to define some of their variables. For example, REMOTE must be loaded before RSPX because REMOTE provides variables that RSPX needs in order to work correctly. Some modules contain instructions that tell the operating system to load another module first. This is called "Autoloading." Other modules are not programmed with this information.Autoloading. If autoloading has been programmed into the module, the module instructs the operating system to load the other module. If the operating system can find the dependent module either in its search paths or in the directory from which the command to load the first module was issued, the dependent module is loaded.A message similar to the following appears:  Auto-loading module <module name>If the operating system cannot find the dependent module, neither module is loaded. You need to specify where the dependent module can be found. Load the dependent module with a path command. Then load the other module.Non-autoloading. If the module is not programmed for autoloading, the following message is displayed when you try to load a module before its dependent module has been loaded:  Loader cannot find public symbol: <symbol name>  Load file referenced undefined public variable.When this dependency exists, the modules must be loaded in the right order. Check the documentation that came with the module to determine the correct loading order.An idxid="w7209"book="_idx" docset="nw312" tidref="i3278"Invalid Parameter Is EnteredSome modules, especially LAN drivers and disk drivers, require parameters. These modules do not load if the following conditions exist:The parameters you selected conflict with other drivers' parameters.The parameters you entered do not match the board's configuration.The board's hardware has failed.None of the boards installed in the file server can use the driver you are trying to load.Do one or more of the following:LAN drivers. Use CONFIG to view hardware configuration information about loaded LAN drivers. Write down the parameters so that you can configure the newly installed board with parameters that do not duplicate any of the displayed parameters. Bring down the file server, reconfigure the board, and reboot the server.Disk drivers. Load INSTALL and view the STARTUP.NCF file. Write down the disk driver parameters so that you can configure the newly installed controller board with parameters that do not duplicate any of the displayed parameters. Bring down the file server, reconfigure the board, and reboot the server.Board configurations. Bring down the file server. Check the board's configuration and reconfigure it (if necessary) or install a different board of the same type. Then reboot the file server.LOAD Is Not Entered before the Module NameYou must precede all loadable modules with LOAD. If you don't, you receive the following message:  ??? Unknown command???To load MONITOR, for example, you would type  LOAD MONITOR <Enter>Make sure you leave a space between "LOAD" and the NLM.An Invalid Command Is in the .NCF FileIf the console displays error messages about invalid commands as the file server boots, invalid commands are probably in the idxid="w7210"book="_idx" docset="nw312" tidref="i595"AUTOEXEC.NCF or idxid="w7211"book="_idx" docset="nw312" tidref="i6489"STARTUP.NCF file. Commands in the .NCF files do not execute if the following conditions exist:The command does not use the proper syntax.The command is in the wrong file.The command requires another command before it.Do one or more of the following:Add "ECHO ON" to the top of the STARTUP.NCF and AUTOEXEC.NCF files so the console displays each command as it executes or fails to execute. This helps you determine which command is failing first.Check the syntax and order of your module load commands.WIDTH="264"Module typeWIDTH="48"PageWIDTH="264"LOAD disk driverWIDTH="48"IDREF="FM53960"107LOAD LAN driverIDREF="FM79039"122LOAD name spaceIDREF="FM50686"158LOAD NLM utilityIDREF="FM52889"164Make sure the commands are in the correct .NCF file. (IDREF="FM34636"See "Edit the STARTUP.NCF File" on page 87 and IDREF="FM38546""Edit the AUTOEXEC.NCF File" on page 82.)ID="FM53960"LOAD disk driverID="FM40291"Why Use idxid="w7212"book="_idx" docset="nw312" tidref="i1240"LOAD idxid="w7213"book="_idx" docset="nw312" tidref="i1552"idxid="w7214"book="_idx" docset="nw312" tidref="i1552"idxid="w7215"book="_idx" docset="nw312" tidref="i1561"disk idxid="w7216"book="_idx" docset="nw312" tidref="i1553"driver?Use idxid="w7217"book="_idx" docset="nw312" tidref="i3257"LOAD idxid="w7218"book="_idx" docset="nw312" tidref="i1553"disk driver to establish communication between the operating system and the hard idxid="w7219"book="_idx" docset="nw312" tidref="i1561"disk controllers installed in your idxid="w7220"book="_idx" docset="nw312" tidref="i2034"idxid="w7221"book="_idx" docset="nw312" tidref="i2034"file server.During the initial operating system installation, idxid="w7222"book="_idx" docset="nw312" tidref="i2127"LOAD idxid="w7223"book="_idx" docset="nw312" tidref="i1627"diskdriver links a driver with your idxid="w7224"book="_idx" docset="nw312" tidref="i2599"hard disk controller. Afterwards, use it to link an updated driver to your controller or to link a driver to an additional hard disk controller.A conflict will occur if you have installedidxid="w7225"book="_idx" docset="nw312" tidref="i1240" more than 16 MB of idxid="w7226"book="_idx" docset="nw312" tidref="i3758"memory and the disk adapter board uses 16- or 24-bit DMA or Bus-Master DMA.If a memory address conflict occurs, you can solve it by doing either of the following:Upgrade to full 32-bit bus adapters.Use drivers that have been modified and certified to compensate for these memory addressing limitations.The following tasks are described in this section.WIDTH="264"TaskWIDTH="48"PageWIDTH="264"Load a disk driver in an ISA (AT bus) computerWIDTH="48"IDREF="FM52573"113Load a disk driver for the internal disk controller  (microchannel)IDREF="FM84236"115Load a disk driver for a disk controller board (microchannel)IDREF="FM62462"116Upgrade a disk driverIDREF="FM43011"118Troubleshoot the host-bus-adapter driverIDREF="FM16025"119Command Format  LOAD [path]disk_driver [driver_parameter...]Command ParametersReplace path with a full path to the directory containing the loadable module. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path and volume SYS: has been mounted, the operating system assumes that the loadable module is located in the SYS:SYSTEM directory. (Use SEARCH to set up additional paths for automatic searching.)Replace idxid="w7227"book="_idx" docset="nw312" tidref="i3278"disk_driver with the name of the disk driver for your disk controller. Those shipped with the operating system are found on System_2 diskette and are listed in IDREF="FM60700"Figure 1-18, "Disk drivers included with the operating system," on page 109 lists these drivers.All idxid="w7228"book="_idx" docset="nw312" tidref="i1561"disk idxid="w7229"book="_idx" docset="nw312" tidref="i1240"driver idxid="w7230"book="_idx" docset="nw312" tidref="i2034"names end with a .DSK extension. Consult NetWire or your Novell Authorized Reseller for a list of other certified disk drivers and idxid="w7231"book="_idx" docset="nw312" tidref="i2252"controller idxid="w7232"book="_idx" docset="nw312" tidref="i2248"boards idxid="w7233"book="_idx" docset="nw312" tidref="i2257".For a list of valid parameters for the drivers, see IDREF="FM57610""Driver Parameters" on page 123.LBL="1-18"ID="FM60700"Disk drivers included with the operating systemFILE="n312sa1i.pbm"Additional InformationSince most controllers can be configured more than one way, you must specify parameters for the controller each time you load a disk driver. The drivers use the parameters to identify which controller they should link with. However, controllers that use the PS2ESDI disk driver or the PS2MFM disk driver do not need any parameters because they cannot be configured.Record the configuration options for all disk coprocessor boards (adapters and controllers) on the "File Server Worksheet" in Installation and Upgrade.Make sure the board settings do not conflict with other hardware settings in the computer. No other piece of hardware (COM ports, monitors, keyboards) can use the same I/O port or interrupt. (In a few cases, interrupts can be shared. If you configure hardware to share an interrupt, make sure that the hardware allows sharing.)Drivers that can link with more than one configuration can be loaded more than once. These drivers either produce multiple copies of the driver code in memory or load idxid="w7234"book="_idx" docset="nw312" tidref="i1561"re-entrantly.When a driver loads re-entrantly, the operating system produces only one copy of the code in memory and allocates a small data block of memory each time the driver is loaded.Driver idxid="w7235"book="_idx" docset="nw312" tidref="i4916"idxid="w7236"book="_idx" docset="nw312" tidref="i1736"idxid="w7237"book="_idx" docset="nw312" tidref="i1561"Parameters idxid="w7238"book="_idx" docset="nw312" tidref="i1561"Some drivers can read the information from the controller board installed in the file server. These types of drivers do not prompt you for any parameters. Other drivers must be told the configuration of the controller to find the controller in the file server.Each parameter should have a unique value, different from any other boards installed in the file server. A few boards can share interrupts. Check the documentation that comes with the boards.Each parameter is defined in this section. Following the definitions is a table for each driver which includes the supported parameters, the default value for the parameters, and all supported values. The PS2ESDI and PS2MFM drivers are not included because these drivers have no parameters.You can enter parameters at the command line, (For configuration information, see the documentation that came with the controller board.) or you can let the operating system prompt you for them.The driver parameters for each disk driver are unique. However, most drivers use one or more of the following:DMA=numberINT=numberMEM=numberPORT=numberSLOT=numberidxid="w7239"book="_idx" docset="nw312" tidref="i1627"DMA=numberReserves a DMA channel for the driver.idxid="w7240"book="_idx" docset="nw312" tidref="i2946"INT=numberReserves a hardware interrupt for the driver. The operating system uses hexadecimal values for the interrupts (10=A, 11=B, 12=C, 13=D, 14=E, 15=F).MEM=numberReserves a idxid="w7241"book="_idx" docset="nw312" tidref="i3781"memory address for the driver.PORT=numberReserves an idxid="w7242"book="_idx" docset="nw312" tidref="i2691"I/O port for the driver.idxid="w7243"book="_idx" docset="nw312" tidref="i6351"SLOT=numberTells the operating system which board to link the driver to. This option is used with microchannel and bus master slots on EISA computers. The interrupts, memory addresses, and I/O ports are set with the reference diskette that comes with the computer.DCBThe idxid="w7244"book="_idx" docset="nw312" tidref="i1325"DCB idxid="w7245"book="_idx" docset="nw312" tidref="i1553"driver can be loaded four times. When the driver is loaded more than once, the driver loads re-entrantly. You can specify any of the following DCB parameters.WIDTH="84"ParameterWIDTH="60"DefaultWIDTH="156"Supported ValuesWIDTH="84"PORTWIDTH="60"340WIDTH="156"320, 328, 340, 348, 380, 388/s=0/s=0The /s=0 parameter is different from the PORT parameter. Use it the first time you load the DCB driver for a board that has been used with different hard disks and does not have current hard disk information. This speeds the load process.You can then use DISKSET to edit the EEPROM information and add the current hard disks that are attached to the board.Although the driver does not prompt you for an interrupt, the board uses an interrupt; the driver displays which interrupt it is using while the driver loads.idxid="w7246"book="_idx" docset="nw312" tidref="i3033"ISADISKThe ISADISK driver can be loaded twice. When the driver is loaded more than once, the driver loads re-entrantly. You can specify any of the following hexadecimal parameters.WIDTH="84"ParameterWIDTH="84"DefaultWIDTH="132"Supported ValuesWIDTH="84"INTWIDTH="84"EWIDTH="132"B, C, E, FPORT1F0170, 1F0The default settings are the standard values for an internal controller. Use the other supported values only if you are adding a secondary ISA adapter.idxid="w7247"book="_idx" docset="nw312" tidref="i5656"PS2SCSIThe PS2SCSI driver can be loaded four times. When the driver is loaded more than once, the driver loads re-entrantly. You can specify the following PS2SCSI parameter:Parameter: SLOTDefault: NoneSupported values: All availableID="FM52573"Load a Disk idxid="w7248"book="_idx" docset="nw312" tidref="i2252"Driver in an ISA (AT Bus) ComputerTo load a disk driver in an ISA computer, complete the following steps.ProcedureComplete one of the following, depending on the type of controller you are loading a disk driver for:If the controller is internal, boot the file server and skip to Step 2.If the controller is a disk controller board, complete Steps 1a through 1f.If you have already loaded a disk driver for a controller board and do not know its configuration, view the STARTUP.NCF file to obtain needed configuration information before downing the file server.Down the file server.Disconnect the power.Configure the board and install it in the file server. Follow the instructions in the documentation that came with the board. Record all configuration information on the "File Server Worksheet" in Installation and Upgrade.Connect the hard disks to the board.Connect the power.Run the appropriate setup program.If you are installing a secondary ISA adapter, use the setup program to specify the hard disk types; then boot the file server.If you are installing a host bus adapter, boot the file server; then load DISKSET. For instructions, IDREF="FM38327"see "DISKSET" on page 32Insert a working copy of the NetWare System_2 diskette into drive A:.Load the disk driver at the command line with or without parameters. Without driver parameters. To load the ISADISK driver, for example, type  LOAD A:ISADISK <Enter>Answer the configuration prompts.You can only select options that do not conflict with previously loaded drivers (LAN and disk). To change a default parameter, type in the number that matches your board's configuration.With driver parameters. To load the DCB driver, for example, type  LOAD A:DCB PORT=320 <Enter>The driver loads only if the parameters match the board's configuration and do not conflict with already loaded LAN and disk drivers.If you have set the board to a conflicting configuration, you must down the file server, remove the board, and reconfigure the board.Edit the STARTUP.NCF file by adding the command to load the disk driver.For example, to load the DCB driver with an I/O port of 320, you would add the following line to the file:LOAD DCB PORT=320IDREF="FM34636"See "Edit the STARTUP.NCF File" on page 87 for more information.Copy the disk driver file from theSystem_2 diskette to the file server's boot directory. Use RCONSOLE to copy the file.ID="FM84236"Load a Disk Driver for the Internal idxid="w7249"book="_idx" docset="nw312" tidref="i2257"Disk Controller ( idxid="w7250"book="_idx" docset="nw312" tidref="i3892"Microchannel)A microchannel computer can have three types of internal controllers: ESDI, MFM, and SCSI. Use the reference diskette that came with the computer to determine the type of controller installed in your computer.The following steps explain how to load the PS2ESDI and PS2MFM drivers. If you have a SCSI controller, see IDREF="FM62462""Load a Disk Driver for a Disk Controller Board (Microchannel)" on page 116.ProcedureBoot the file server with DOS.Run SERVER.Enter the file server's name and internal network number.See Chapter 3, "book="install" docset="nw312"File Server Installation," in Installation and Upgrade for more information about Steps 1 through 3.Insert a working copy of theSystem_2 diskette into drive A: of the file server. Load a driver.To load the PS2ESDI driver, for example, type  LOAD A:PS2ESDI <Enter>Edit the STARTUP.NCF file by adding the command to load the disk driver.For example, add the following line to the file for the PS2ESDI driver:  LOAD PS2ESDIIDREF="FM34636"See "Edit the STARTUP.NCF File" on page 87 for more information.Copy the disk driver file from theSystem_2 diskette to the file server's boot directory. Use RCONSOLE to copy the file.ID="FM62462"Load a idxid="w7251"book="_idx" docset="nw312" tidref="i2257"Disk Driver for a Disk Controller Board ( idxid="w7252"book="_idx" docset="nw312" tidref="i3892"Microchannel)If the controller board comes with its own instructions, please follow them. Use the following instructions for loading the PS2SCSI driver.To load a disk driver for a controller board installed in a microchannel computer, complete the following steps.ProcedureDown the file server.Disconnect the power.Install the board in the file server.Connect the hard drives to the board.Copy the configuration file to the reference or setup diskette for the microchannel computer. The configuration file is usually an .ADF file on the diskette that came with the board.Connect the power.Complete one of the following:If the controller board came with a setup program, run the setup program to select the hard disks. Then boot the file server and continue with Step 8.If the controller board uses DISKSET to select the hard disks, boot the file server. Then continue with Step 8. (You select the hard disks in Step 12.)Insert a working copy of theSystem_2 diskette into drive A:.The driver can be loaded at the command line with or without driver parameters. Complete one of the following options:Load without driver parameters. To load the PS2SCSI driver, for example, type  LOAD A:PS2SCSI <Enter>Enter the slot number for the board.Load with driver parameters. To load the PS2SCSI driver, for example, type  LOAD A:PS2SCSI SLOT=4 <Enter>Edit the STARTUP.NCF file. IDREF="FM34636"See "Edit the STARTUP.NCF File" on page 87.Add the command to load the disk driver.For example, to load the PS2SCSI driver (installed in slot 4), add the following line to the file:  LOAD PS2SCSI SLOT=4Copy the disk driver file from theSystem_2 diskette to the file server's boot directory. Use RCONSOLE to copy the file.If the controller board uses DISKSET to select the hard disks, load DISKSET. For instructions on selecting the hard disks, IDREF="FM38327"see "DISKSET" on page 32ID="FM43011"Upgrade idxid="w7253"book="_idx" docset="nw312" tidref="i1561"a Disk DriverProcedureDetermine the current configuration information for the disk driver being upgraded. View the STARTUP.NCF file IDREF="FM34636"(see "Edit the STARTUP.NCF File" on page 87).Dismount all volumes stored on the hard disks connected to the controller board by typing  DISMOUNT volume_name<Enter>Replace volume_name with the name of a volume on the hard disks. Repeat this step for all volumes stored on the hard disks.If you do not dismount all the volumes but still attempt to unload the disk driver, the operating system warns you that the driver is being used by mounted volumes and lists the volumes that are using the driver.If you override the warning and unload the disk driver without dismounting the volumes, the file server automatically dismounts all volumes that are using the disk driver. Users who are logged in receive the following message:Volume "volume_name" dismounted due to drive deactivation.Unload the disk driver. For example, to unload the ISADISK driver, type  UNLOAD ISADISK <Enter>Load the updated driver. For example, to load the ISADISK driver from a diskette into drive A:, type  LOAD A:ISADISK <Enter>If DOS has been removed with the SECURE CONSOLE or REMOVE DOS command, you cannot load the driver from drive A:. You have to copy the driver to the SYS:SYSTEM directory.Remount the volumes. IDREF="FM70396"See "MOUNT" on page 213.Copy the updated driver to the directory containing the file server boot files. Either down the file server or use RCONSOLE.ID="FM16025"Troubleshooting idxid="w7254"book="_idx" docset="nw312" tidref="i6910"the Host Bus Adapter idxid="w7255"book="_idx" docset="nw312" tidref="i1325"DriverCertain Host Bus Adapter (HBA) drivers reserve memory addresses between 14 MB and 16 MB. These addresses may conflict with (and corrupt) system memory if you have more than 14 MB installed. If this happens, you must remove the system memory or, if the server is an EISA machine, configure the conflicting addresses out of system memory. See the documentation that comes with your disk driver for address ranges.The HBA cannot load unless the hard disks and controllers have been addressed, terminated, and configured properly.The disk subsystem power must also be turned on. If the HBA driver fails to load, check the following:Make sure the hard disks are addressed and terminated correctly. If the controller can have two hard disks cabled to it, make sure that disk 0 is cabled and addressed as disk 0 and that it is terminated. Disk 1 needs to be cabled and addressed as disk 1, but it should not be terminated. If only one disk is attached to the controller, make it disk 0.Make sure the HBA is terminated if it connects to external subsystems and does not connect to any internal hard disks. Make sure the termination has been removed if the HBA is connected to internal hard disks.Make sure the last controller daisy-chained to the HBA is terminated.Make sure you address each controller attached to the host bus adapter according to its position in the daisy chain. For example, the controller attached directly to the Host Bus Adapter should have address 0, the controller attached to controller 0 should have address 1, etc.Disable parity on SCSI hard disks connected to an HBA. Most SCSI disks are shipped with parity enabled; you need to remove the jumper to disable parity. See the documentation that came with the hard disk.Check the power supply to the disk subsystem.Check interrupt conflicts. The following chart lists possible conflicts:WIDTH="72"Hex Value  InterruptsWIDTH="72"Decimal Value  InterruptsWIDTH="144"Possible ConflictsWIDTH="72"BWIDTH="72"11WIDTH="144"ISADISK.DSKC12ISADISK.DSK, mouse port  (COMPAQ & compatibles)F15ISADISK.DSKCheck for I/O port conflicts. The following chart lists some possible areas of conflict:WIDTH="108"I/O portWIDTH="192"Possible LAN driver conflictsWIDTH="108"320WIDTH="192"3C505,NE1000,NE20003283C503 (330)340NE1000, NE20003483C503 (350), TRXNET (350)ID="FM79039"LOAD LAN driverID="FM89882"Why Use idxid="w7256"book="_idx" docset="nw312" tidref="i3271"LOAD idxid="w7257"book="_idx" docset="nw312" tidref="i3085"LAN idxid="w7258"book="_idx" docset="nw312" tidref="i1627"driver?ID="FM26535"Use idxid="w7259"book="_idx" docset="nw312" tidref="i2127"LOAD LAN driver to link the appropriate drivers with the network boards installed in your file idxid="w7260"book="_idx" docset="nw312" tidref="i4508"server.Avoid memory conflicts. If you have installed more than 16 MB of memory, do not install a network board that uses online idxid="w7261"book="_idx" docset="nw312" tidref="i1561"DMA or that is an AT bus master board. The board will corrupt the file server's memory.If you want to use such a board, complete one of the following to remove the memory from the operating system:If you are using an EISA computer with memory above 16 MB, see IDREF="FM20331""Auto Register Memory above 16 Megabytes = value" on page 281.If you have a microchannel or ISA computer, remove the REGISTER MEMORY command from the AUTOEXEC.NCF file and reboot the file server.The following tasks are described in this section:WIDTH="264"TaskWIDTH="48"PageWIDTH="264"Load a LAN driver in an EISA file serverWIDTH="48"IDREF="FM92424"143Load a LAN driver in an ISA (AT bus) file serverIDREF="FM41811"145Load a LAN driver in a microchannel file serverIDREF="FM89838"146Change an optional parameter of a loaded driverIDREF="FM43915"148Load a driver more than onceIDREF="FM87181"149Upgrade a LAN driverIDREF="FM12879"153Troubleshooting LAN driversIDREF="FM40275"155Command Format  LOAD [path]LAN_driver [driver_parameter...]Command ParametersReplace path with a full path. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path and volume SYS: is mounted, the operating system assumes that the loadable module is located in the SYS:SYSTEM directory. Use SEARCH to set up additional paths for automatic searching.Replace LAN_driver with the appropriate driver for your idxid="w7262"book="_idx" docset="nw312" tidref="i4508"network idxid="w7263"book="_idx" docset="nw312" tidref="i3085"board. LAN drivers shipped with the operating system are found on theSystem_2 diskette. IDREF="FM24433"Figure 1-19, "LAN drivers shipped with the operating system," on page 124 lists these drivers. See NetWire or your Novell Authorized Reseller for a list of other certified LAN drivers and boards.idxid="w7264"book="_idx" docset="nw312" tidref="i1736"idxid="w7265"book="_idx" docset="nw312" tidref="i3085"ID="FM57610"Driver idxid="w7266"book="_idx" docset="nw312" tidref="i4916"Parametersidxid="w7267"book="_idx" docset="nw312" tidref="i3085"LAN drivers parameters may be required or optional.The LAN driver prompts you for required parameters if you do not specify them on the command line.The LAN driver does not prompt you for optional parameters; the default values are coded into the driver. To modify the default value, you must specify the new value at the command line when you load the driver.Most drivers use one or more of the following parameters.DMA=numberINT=numberNAME=boardnamePORT=numberSLOT=numberFRAME=nameMEM=numberNODE=numberRETRIES=numberThese driver parameters, and a few specialized TOKEN parameters, are described here. Lists and explanations of the parameters that each driver supports begin on page IDREF="FM40294"130.LBL="1-19"ID="FM24433"LAN drivers shipped with the operating systemFILE="n312sa1j.pbm"idxid="w7268"book="_idx" docset="nw312" tidref="i1627"DMA=numberSpecifies the Direct Memory Access (DMA) channel the driver should use for the network board.idxid="w7269"book="_idx" docset="nw312" tidref="i2520"idxid="w7270"book="_idx" docset="nw312" tidref="i2502"FRAME idxid="w7271"book="_idx" docset="nw312" tidref="i2520"=name idxid="w7272"book="_idx" docset="nw312" tidref="i2520"Tells the Ethernet and Token-Ring drivers which type of packet header to use with NetWare. The default for Ethernet is the 802.2 standard (a length code); the default for Token-Ring is Token-Ring.idxid="w7273"book="_idx" docset="nw312" tidref="i2520"Ethernet. If you are using idxid="w7274"book="_idx" docset="nw312" tidref="i1861"Ethernet drivers, replace name with one of the following:WIDTH="96"NameWIDTH="204"ExplanationWIDTH="96"Ethernet 802.3 WIDTH="204"Assigns a Novell frame. Use on a network that is  using only NetWare.Ethernet_IIAssigns a unique packet header (type code). Use  on networks connected to DEC or to computers  using the TCP/IP protocol.Ethernet_802.2  (default)Assigns the IEEE and OSI standard frame type.Ethernet_SNAPUse when the 802.2 SNAP extension is required.If you select an option other than the default frame type (Ethernet_802.2), you must configure the drivers for the workstations. Each workstation that you want to communicate with the file server needs its driver configured to the file server's frame type. Use the following chart to determine the type of driver you can use in the workstation:WIDTH="96"Frame typeWIDTH="96"DOS driverWIDTH="96"DOS ODI driverWIDTH="96"Ethernet_802.3WIDTH="96"YesWIDTH="96"YesEthernet_IIYesYesEthernet_SNAPNoYesEthernet_802.2NoYesFor instructions on using the DOS ODI driver, see Chapter 2 "book="ws_get" docset="nw312"Preparing to Install Workstation Software" in Workstation Basics and Installation.For instructions on configuring the DOS NET.CFG file for ODI drivers, seebook="ws_dos" docset="nw312"Workstation for DOS and Windows.idxid="w7275"book="_idx" docset="nw312" tidref="i6821"Token-Ring idxid="w7276"book="_idx" docset="nw312" tidref="i2520". If you are using Token-Ring drivers, replace name with one of the following:WIDTH="96"NameWIDTH="204"ExplanationWIDTH="96"Token-RingWIDTH="204"Assigns the standard packet header 802.2  (default). Use only with protocols which require  802.2 encapsulation (such as the OSI protocol  suite.)Token-Ring_SNAPAssigns the 802.2 with SNAP header. Use with  networks that need to communicate with such  protocols as AppleTalk and TCP/IP.If you select Token-Ring_SNAP, your workstations must use DOS ODI drivers that are configured for Token-Ring_SNAP. For instructions on configuring DOS ODI drivers, seebook="ws_dos" docset="nw312"Workstation for DOS and Windows.idxid="w7277"book="_idx" docset="nw312" tidref="i2946"INT=numberReserves a unique interrupt for the driver. Some ISA (AT bus) drivers prompt for this parameter. Microchannel computers set this parameter with the reference diskette that comes with the computer.idxid="w7278"book="_idx" docset="nw312" tidref="i3212"LS=numberDetermines the number of 802.5 link stations for the Token-Ring driver. This optional parameter can be modified at the command line only when the driver is loaded.idxid="w7279"book="_idx" docset="nw312" tidref="i3782"MEM=numberReserves a unique memory address for the driver. Some ISA (AT bus) drivers prompt for this parameter. Microchannel computers set this parameter with the reference diskette that comes with the computer.idxid="w7280"book="_idx" docset="nw312" tidref="i3989"NAME=board nameAssigns a unique name to the board's configuration. You can use this optional parameter to identify network boards when you have more than one network board of the same type installed in the file server. The name can be 17 characters long.idxid="w7281"book="_idx" docset="nw312" tidref="i4651"NODE=numberOverrides the node address setting on some network boards. Use this optional parameter only if you or someone else keeps track of and assigns node addresses. The address selected must be a valid hexadecimal address for the board. Some drivers may not support this parameter.idxid="w7282"book="_idx" docset="nw312" tidref="i2691"PORT=numberReserves a unique I/O port for the driver. Some ISA (AT bus) drivers prompt for this parameter. Microchannel computers set this parameter with the reference diskette that comes with the computer.idxid="w7283"book="_idx" docset="nw312" tidref="i5929"RETRIES idxid="w7284"book="_idx" docset="nw312" tidref="i4903"=numberInstructs the driver to retry the packet transmission a specified number of times when a packet transmission fails. This optional parameter can be modified at the command line only when the driver is loaded.idxid="w7285"book="_idx" docset="nw312" tidref="i6257"SAPS=numberDetermines the 802.2 service access point stations for the Token-Ring driver. This optional parameter can be modified at the command line only when the driver is loaded.idxid="w7286"book="_idx" docset="nw312" tidref="i6351"SLOT=numberTells the operating system which board to link the driver to. This parameter is used with microchannel and EISA computers. The I/O ports, interrupts, memory addresses, and node addresses are set with the reference or setup diskette that comes with the computer.idxid="w7287"book="_idx" docset="nw312" tidref="i851"TBC=numberDetermines the idxid="w7288"book="_idx" docset="nw312" tidref="i6903"transmit buffer count for the Token-Ring driver. This optional parameter can be modified at the command line only when the driver is loaded.idxid="w7289"book="_idx" docset="nw312" tidref="i851"TBZ=numberDetermines the idxid="w7290"book="_idx" docset="nw312" tidref="i6903"transmit buffer size for the Token-Ring driver. The default assigns the maximum packet size allowed by either the board or the operating system. This optional parameter can be modified at the command line only when the driver is loaded.For information on increasing the operating system's maximum packet size, IDREF="FM73882"see "SET" on page 258Additional InformationBefore you can load a v3.1x driver, you must do the following:Configure and idxid="w7291"book="_idx" docset="nw312" tidref="i3278"install the idxid="w7292"book="_idx" docset="nw312" tidref="i4508"network board in the file server.Make sure each network board is uniquely configured.Load (or autoload) NMAGENT.Third-party v3.0 drivers work with NetWare v3.1x. However, v3.0 drivers do not need NMAGENT. System messages will be displayed about old API calls. Use the driver until an updated version is available.If you have more than one network board of the same type in your file server, or if you need to use more than one frame type, you should understand how to load drivers more than once and how to load additional frames.Multiple idxid="w7293"book="_idx" docset="nw312" tidref="i4508"BoardsMost LAN drivers can be loaded more than once. Some drivers produce multiple copies in memory. These drivers produce the entire driver code in memory for each configuration entered with the driver.Other drivers load re-entrantly. These drivers produce only one copy of code and global data in memory and then allocate a small data block of memory for parameters each time the driver is loaded. These drivers use less memory than drivers that load the entire code in memory each time they are loaded.idxid="w7294"book="_idx" docset="nw312" tidref="i4508"Logical BoardsEthernet and Token-Ring drivers can be configured so that the same network board can communicate using more than one frame type. When you load a driver using the same parameters except for frame type, the operating system views the second loading as another board.For example, if two frame types are loaded for one NE2000 network board, the NE2000 board is treated as two logical boards---a board for each frame type.ID="FM40294"LAN Driver ParametersThe LAN drivers and the parameters they support are described on the following pages.LBL="1-1" INLINE="F"LAN driver parametersWIDTH="264"LAN driverWIDTH="48"PageWIDTH="264"3C503WIDTH="48"IDREF="FM52608"1323C505IDREF="FM98820"1333C523IDREF="FM50860"133NE2IDREF="FM98040"134NE2-32IDREF="FM85594"135NE1000IDREF="FM47910"137NE2000IDREF="FM82181"138NE3200IDREF="FM22463"139PCN2IDREF="FM72802"140TOKENIDREF="FM51255"141TRXNETIDREF="FM91558"142idxid="w7295"book="_idx" docset="nw312" tidref="i55"ID="FM52608"3C503 idxid="w7296"book="_idx" docset="nw312" tidref="i3074"You can have up to four idxid="w7297"book="_idx" docset="nw312" tidref="i1864"3C503 boards in an ISA (AT) bus file server. You can load this driver for each board and for each additional frame type assigned to the board (maximum: 16 times). This driver loads re-entrantly.LBL="1-2" INLINE="F"3C503 driverWIDTH="60"ParameterWIDTH="96"DefaultWIDTH="168"Supported valuesWIDTH="72"OptionalWIDTH="60"FRAMEWIDTH="96"Ethernet_802.2WIDTH="168"Ethernet_802.2Ethernet_IIEthernet_SnapEthernet_802.3WIDTH="72"YesINT32, 3, 4, 5NoMEMC8000*C8000, CC000, D8000, DC000NoNAMENoneAny unique 17-character nameYesNODEBoard valueAny 12-digit hexadecimal number**YesPORT300300, 310, 330, 350, 250, 280, 2A0, 2E0NoRETRIES50---255YesTo change the transceiver type from BNC (thin ethernet cabling or an internal transceiver) to DIX (thick ethernet cabling or an external transceiver), load the driver with the DIX parameter by typing  LOAD 3C503 DIX <Enter>The default is BNC. This parameter does not need to be specified. If the driver has been loaded with DIX, you can unload the driver and then reload the driver without the DIX parameter to set the driver to the default (BNC).ID="FM98820"idxid="w7298"book="_idx" docset="nw312" tidref="i3074"3C505You can have up to three idxid="w7299"book="_idx" docset="nw312" tidref="i1864"3C505 idxid="w7300"book="_idx" docset="nw312" tidref="i58"boards in an ISA (AT) bus file server. However, the board must be installed in a 16-bit slot. You can load this driver for each board and for each frame type assigned to a board (maximum: 12 times). The driver loads re-entrantly.LBL="1-3" INLINE="F"3C505 driverWIDTH="60"ParameterWIDTH="96"DefaultWIDTH="168"Supported valuesWIDTH="72"OptionalWIDTH="60"DMAWIDTH="96"5WIDTH="168"1, 3, 5, 6, 7WIDTH="72"NoFRAMEEthernet_802.2Ethernet_802.2Ethernet_IIEthernet_SnapEthernet_802.3YesINT32, 3, 4, 5NoMEMC8000*C8000, CC000, D8000, DC000NoNAMENoneAny unique 17-character nameYesNODEBoard valueAny 12-digit hexadecimal number**YesPORT300300, 310, 330, 350, 250, 280, 2A0, 2E0NoRETRIES50---255YesThis driver uses the board's DMA. Do not use this driver in a file server that has more than 16 MB of memory installed.idxid="w7301"book="_idx" docset="nw312" tidref="i3074"ID="FM50860"3C523You can have up to four idxid="w7302"book="_idx" docset="nw312" tidref="i1864"3C523 idxid="w7303"book="_idx" docset="nw312" tidref="i61"boards in the microchannel file server. You can load this driver for each board and for each additional frame type assigned to the board (maximum: 16 times). This driver loads re-entrantly.Set the interrupts, memory addresses, I/O ports, and transceiver type with the computer's setup or reference diskette. You must also enable the board with the reference diskette. The driver reads these settings when you enter the slot number in which the board is installed.LBL="1-4" INLINE="F"ID="FM50860"3C523 driverWIDTH="60"ParameterWIDTH="96"DefaultWIDTH="168"Supported valuesWIDTH="72"OptionalWIDTH="60"FRAMEWIDTH="96"Ethernet_802.2WIDTH="168"Ethernet_802.2Ethernet_IIEthernet_SnapEthernet_802.3WIDTH="72"YesNAMENoneAny unique 17-character nameYesNODEBoard valueAny 12-digit hexadecimal number**YesRETRIES100---255YesSLOTNoneAll availableNoID="FM98040"NE2 idxid="w7304"book="_idx" docset="nw312" tidref="i3074"You can have as many as four idxid="w7305"book="_idx" docset="nw312" tidref="i1864"NE/2 idxid="w7306"book="_idx" docset="nw312" tidref="i4077"boards in a microchannel file server, installed in 16-bit slots. You can load this driver for each board and for each additional frame type assigned to the board (maximum: 16 times). This driver loads re-entrantly.Set the interrupts, memory addresses, and I/O ports with the computer's setup or reference diskette. The recommended setting for memory is disabled. The driver reads the settings when you enter the slot number in which the board is installed.LBL="1-5" INLINE="F"ID="FM98040"NE2 driverWIDTH="60"ParameterWIDTH="96"DefaultWIDTH="168"Supported valuesWIDTH="72"OptionalWIDTH="60"FRAMEWIDTH="96"Ethernet_802.2WIDTH="168"Ethernet_802.2Ethernet_IIEthernet_SnapEthernet_802.3WIDTH="72"YesNAMENoneAny unique 17-character nameYesNODEBoard valueAny 12-digit hexadecimal number**YesRETRIES50---255YesSLOTFirst one found  scanning from slot  1 to 81---8NoID="FM85594"NE2-32 idxid="w7307"book="_idx" docset="nw312" tidref="i4080"The idxid="w7308"book="_idx" docset="nw312" tidref="i3074"NE2-32 idxid="w7309"book="_idx" docset="nw312" tidref="i1864"driver can be loaded for as many NE2-32 boards as can fit in a microchannel file server. If your server has only three 32-bit slots, you can install three boards. You can load this driver for each board and for each additional frame type assigned to the board. This driver loads re-entrantly.Set the interrupts, memory addresses, and I/O ports with the computer's setup or reference diskette. The driver reads these settings when you enter the slot number in which the board is installed.LBL="1-6" INLINE="F"NE2-32 driverWIDTH="60"ParameterWIDTH="96"DefaultWIDTH="168"Supported valuesWIDTH="72"OptionalWIDTH="60"FRAMEWIDTH="96"Ethernet_802.2WIDTH="168"Ethernet_802.2Ethernet_IIEthernet_SnapEthernet_802.3WIDTH="72"YesNAMENoneAny unique 17-character nameYesRETRIES50---255YesSLOTNoneAll availableNoID="FM47910"NE1000 idxid="w7310"book="_idx" docset="nw312" tidref="i3074"You can have as many as four idxid="w7311"book="_idx" docset="nw312" tidref="i4074"NE1000 idxid="w7312"book="_idx" docset="nw312" tidref="i1864"boards in an ISA (AT bus) file server if the boards are configured so that they do not conflict with other components in the file server. You can load this driver for each board and for each additional frame type assigned to the board (maximum: 16 times). This driver loads re-entrantly.LBL="1-7" INLINE="F"NE1000 driverWIDTH="60"ParameterWIDTH="96"DefaultWIDTH="168"Supported valuesWIDTH="72"OptionalWIDTH="60"FRAMEWIDTH="96"Ethernet_802.2WIDTH="168"Ethernet_802.2Ethernet_IIEthernet_SnapEthernet_802.3WIDTH="72"YesINT32, 3, 4, 5NoNAMENoneAny unique 17-character nameYesNODEBoard valueAny 12-digit hexadecimal number*YesPORT300300, 320, 340, 360NoRETRIES50---255YesID="FM82181"NE2000 idxid="w7313"book="_idx" docset="nw312" tidref="i3074"idxid="w7314"book="_idx" docset="nw312" tidref="i3074"You can have up to four idxid="w7315"book="_idx" docset="nw312" tidref="i1864"NE2000 idxid="w7316"book="_idx" docset="nw312" tidref="i4083"boards in an ISA (AT bus) file server if the boards are configured so that they do not conflict with other hardware in the file server. However, each board must be installed in a 16-bit slot. You can load this driver for each board and for each additional frame type assigned to the board (maximum: 16 times). This driver loads re-entrantly.LBL="1-8" INLINE="F"NE2000 driverWIDTH="60"ParameterWIDTH="96"DefaultWIDTH="168"Supported valuesWIDTH="72"OptionalWIDTH="60"FRAMEWIDTH="96"Ethernet_802.2WIDTH="168"Ethernet_802.2Ethernet_IIEthernet_SnapEthernet_802.3WIDTH="72"YesINT32, 3, 4, 5NoNAMENoneAny unique 17-character nameYesNODEBoard valueAny 12-digit hexadecimal number*YesPORT300300, 320, 340, 360NoRETRIES50---255YesID="FM22463"NE3200 idxid="w7317"book="_idx" docset="nw312" tidref="i3074"You can have up to six idxid="w7318"book="_idx" docset="nw312" tidref="i4086"NE3200 idxid="w7319"book="_idx" docset="nw312" tidref="i1864"boards in the EISA (Extended Industry Standard Architecture) file server. However, the board must be installed in a 32-bit bus master slot. You can load this driver for each board and for each additional frame type assigned to the board (maximum: 24 times). This driver loads re-entrantly.Set interrupts and connector types with the CONFIGURATION (or similarly named) diskette. The driver reads these settings when you enter the slot number in which the board is installed.LBL="1-9" INLINE="F"NE3200 driverWIDTH="60"ParameterWIDTH="96"DefaultWIDTH="168"Supported valuesWIDTH="72"OptionalWIDTH="60"FRAMEWIDTH="96"Ethernet_802.2WIDTH="168"Ethernet_802.2Ethernet_IIEthernet_SnapEthernet_802.3WIDTH="72"YesNAMENoneAny unique 17-character nameYesRETRIES50---255YesSLOTNoneAll availableNoThe NE3200 driver uses more than one packet receive buffer. If the "No ECB available count" counter in MONITOR increments, IDREF="FM73882"see "SET" on page 258 to increase the minimum and maximum number of packet receive buffers.ID="FM72802"PCN2 idxid="w7320"book="_idx" docset="nw312" tidref="i3074"You can have a maximum of two idxid="w7321"book="_idx" docset="nw312" tidref="i5041"PCN2 boards in a file server, one each at the primary port addresses.LBL="1-10" INLINE="F"PCN2 driverWIDTH="60"ParameterWIDTH="96"DefaultWIDTH="168"Supported valuesWIDTH="72"OptionalWIDTH="60"FRAMEWIDTH="96"PCN2_802.2WIDTH="168"PCN2_802.2PCN2_SnapWIDTH="72"YesNAMENoneAny unique 17-character nameYesNODEBoard valueAny 12-digit hexadecimal number*YesPORT620620, 628NoID="FM51255"TOKEN idxid="w7322"book="_idx" docset="nw312" tidref="i6807"idxid="w7323"book="_idx" docset="nw312" tidref="i6821"You can use this driver in both ISA (AT bus) and microchannel file servers. You can have a maximum of two idxid="w7324"book="_idx" docset="nw312" tidref="i3074"Token-Ring network boards in your file server.All parameters are optional. You can modify parameters at the command line only when you load the driver. All users of the idxid="w7325"book="_idx" docset="nw312" tidref="i3212"driver can set the NAME, NODE, MEM, and idxid="w7326"book="_idx" docset="nw312" tidref="i6903"TBZ parameters. You should not set the other parameters unless you are a programmer.The shared RAM should not be set higher than 16 KB. Even though some boards can be set to 64 KB, use 16 KB. The file server will still use all 64 KB on the board.LBL="1-11" INLINE="F"TOKEN driverWIDTH="48"ParameterWIDTH="108"DefaultWIDTH="168"Supported valuesWIDTH="72"OptionalWIDTH="48"FRAMEWIDTH="108"IBM_TOKEN_RINGWIDTH="168"IBM_TOKEN_RINGIBM_TOKEN_RING_SNAPWIDTH="72"YesLS00---255YesMEM0*A0000---F0000YesNAMENoneAny unique 17-character nameYesNODEBoard valueAny 8-digit hexadecimal number**YesPORTA20A20, A24YesSAPS00---255YesSLOTNoneAll availableYesTBC20---2YesTBZ0***96---65535YesID="FM91558"TRXNETThis driver can be used for both ISA (AT bus) and microchannel file servers.An ISA file server can have as many as four RX-Net boards installed; therefore, you can load this driver four times in an ISA file server.A microchannel file server can have as many as six idxid="w7327"book="_idx" docset="nw312" tidref="i7033"RX-Net boards installed; therefore, you can load this driver six times in a microchannel file server.The driver loads re-entrantly.ISA parameters. When loading the idxid="w7328"book="_idx" docset="nw312" tidref="i7033"TRXNET driver in an ISA file server, select values from the following table.LBL="1-12" INLINE="F"TRXNET driverWIDTH="60"ParameterWIDTH="96"DefaultWIDTH="168"Supported valuesWIDTH="72"OptionalWIDTH="60"INTWIDTH="96"2WIDTH="168"2, 3, 4, 5*, 7WIDTH="72"NoNAMENoneAny unique 17-character nameYesMEMD0000C0000, CC000, D0000, DC000, E0000NoPORT2E02E0, 2F0, 300, 310, 350NoRETRIES1000---255YesID="FM20891"Microchannel parameters. Select interrupts, memory addresses, and I/O ports with the computer's setup or reference diskette. When you load the driver, use the values from the chart below.LBL="1-13" INLINE="F"TRXNET driver for microchannel computersWIDTH="60"ParameterWIDTH="96"DefaultWIDTH="168"Supported valuesWIDTH="72"OptionalWIDTH="60"NAMEWIDTH="96"NoneWIDTH="168"Any unique 17-character nameWIDTH="72"YesRETRIES1000---255YesSLOTNoneAll availableYesID="FM92424"Load a idxid="w7329"book="_idx" docset="nw312" tidref="i3123"LAN Driver in an EISA idxid="w7330"book="_idx" docset="nw312" tidref="i2248"File idxid="w7331"book="_idx" docset="nw312" tidref="i3278"ServerTo load a driver in an EISA file server, complete the following steps. (For a list of the configuration options supported by the driver, see the parameters listed on pages IDREF="FM40294"130 through IDREF="FM20891"143.)Procedure to Down the file server.Make sure all power is off before installing a network board.Install the board in the file server. See the NetWare supplement or the documentation that came with the computer for installation instructions.Connect the power to the file server.Copy the .CFG file from the diskette that came with the board to the CONFIGURATION (or similarly named) diskette for the file server.Configure the board with the EISA configuration utility.Boot the file server.If NMAGENT is not loaded, NMAGENT automatically loads with the driver.Load the driver. You can load the driver at the command line with or without parameters. Do one of the following:Without driver parameters. For example, to load the NE3200 driver without driver parameters, type  LOAD NE3200 <Enter>You are prompted to enter the board's slot number.With driver parameters. For example, to load the NE3200 driver with driver parameters and the name BACKBONE, type  LOAD NE3200 SLOT=3 NAME=BACKBONE <Enter>Bind a communication protocol to the board. IDREF="FM75419"See "BIND" on page 8.Edit the AUTOEXEC.NCF file to load and bind the driver automatically.For example, to load the NE3200 driver automatically (configuration: slot=3, name=BACKBONE) and bind IP to the driver, add the following lines to the AUTOEXEC.NCF file:  LOAD NE3200 SLOT=3 NAME=BACKBONE  BIND IP TO BACKBONE NET=26For instructions on editing the AUTOEXEC.NCF file, see IDREF="FM38546""Edit the AUTOEXEC.NCF File" on page 82.ID="FM41811"Load idxid="w7332"book="_idx" docset="nw312" tidref="i3278"a LAN driver idxid="w7333"book="_idx" docset="nw312" tidref="i2252"in an ISA (AT bus) idxid="w7334"book="_idx" docset="nw312" tidref="i3123"File idxid="w7335"book="_idx" docset="nw312" tidref="i3031"ServerTo idxid="w7336"book="_idx" docset="nw312" tidref="i2252"load a driver in an ISA file server, complete the following steps. (For a list of the configuration options that are supported by the driver, see the parameters listed on pages IDREF="FM40294"130 through IDREF="FM20891"143.) If you do not know the configuration of the boards already installed in the file server, run CONFIG.Down the file server.Make sure the power is off before installing a network board.Configure the board and install it in the file server.See the NetWare supplement or the documentation that came with the board for appropriate jumper settings.Select settings that are supported by the driver and that do not conflict with the boards already installed. Record the configuration information for the new board.Connect the power.Boot the file server.If NMAGENT is not loaded, the driver loads it.Load the driver. The driver can be loaded at the command line with or without driver parameters. Complete one of the following:Without driver parameters. For example, to load the NE2000 driver without driver parameters, type  LOAD NE2000 <Enter>You are prompted to enter the configuration information.You can select only options that do not conflict with boards already installed. To change a default parameter, type the value that corresponds to the board's configuration.With driver parameters. For example, to load the TRXNET driver with driver parameters, type  LOAD TRXNET INT=3 PORT=2E0 MEM=C0000<Enter>The driver only loads if the parameters match the board's configuration and the board's configuration does not conflict with any other server hardware.If you have set the board to a conflicting configuration, the driver will not load. You will need to down the file server, remove the board, and set the board differently before the driver can load. See the NetWare supplement or the documentation for the LAN driver board.Bind a communication protocol to the driver. IDREF="FM75419"See "BIND" on page 8.Edit the AUTOEXEC.NCF file and add lines to load the driver and bind it to a protocol.For example, to load the TRXNET driver (configuration: interrupt=3, I/O port=2E0, and memory address=C0000) and bind it to IPX, add the following lines to the AUTOEXEC.NCF file:  LOAD TRXNET INT=3 PORT=2E0 MEM=C0000  BIND IPX TO TRXNET NET=26For instructions on editing the AUTOEXEC.NCF file, see IDREF="FM38546""Edit the AUTOEXEC.NCF File" on page 82.ID="FM89838"Load a idxid="w7337"book="_idx" docset="nw312" tidref="i3123"LAN idxid="w7338"book="_idx" docset="nw312" tidref="i3892"Driver in a idxid="w7339"book="_idx" docset="nw312" tidref="i3278"Microchannel idxid="w7340"book="_idx" docset="nw312" tidref="i2257"File ServerTo load a driver in a microchannel file server, complete the following steps. (For a list of the configuration options supported by the driver, see the parameters on pages IDREF="FM40294"130 through IDREF="FM20891"143.)Down the file server.Turn the power off before you install a network board.Install the board in the file server. See the NetWare supplement or the documentation that came with the board for installation instructions.Copy the *.ADF file from the diskette that came with the board to the setup or reference diskette for the file server. For more information, see the instructions that came with the reference diskette.Connect the power to the file server.Run the setup or reference program and configure the board. If you are using RX-Net boards and compatibles, make sure that the node address is unique and is not 0.Boot the file server.If NMAGENT is not loaded, NMAGENT will automatically load with the driver.Load the driver.You can load the driver with or without parameters at the command line. Do one of the following:Without driver parameters. For example, to load the TRXNET driver without driver parameters, type  LOAD TRXNET <Enter>You are prompted to enter the board's slot number.With driver parameters. For example, to load the NE2 driver with parameters and the name BACKBONE, type  LOAD NE2 SLOT=3 NAME=BACKBONE <Enter>Bind a communication protocol to the board. IDREF="FM75419"See "BIND" on page 8.Edit the AUTOEXEC.NCF file and add lines to load the driver and bind it to a protocol.For example, to load the NE2 driver automatically (configuration: slot=3, name=BACKBONE) and bind it to the IP protocol, add the following lines to the file:  LOAD NE2 SLOT=3 NAME=BACKBONE  BIND IP TO NE2 NET=26For instructions on editing the AUTOEXEC.NCF file, see IDREF="FM38546""Edit the AUTOEXEC.NCF File" on page 82.ID="FM43915"Change idxid="w7341"book="_idx" docset="nw312" tidref="i3085"an Optional Parameter of a Loaded DriverYou can change optional parameters for loaded drivers. (For a list of optional parameters for your LAN driver, see pages IDREF="FM40294"130 through IDREF="FM20891"143.) Hardware configuration options cannot be changed following these steps.If users are logged in and doing critical processes, do not change the driver parameters until the users have logged out.You should be able to change an optional parameter in less than five minutes. If a logged-in user makes a call to the file server during the process, the user receives a lost connection message. If the user waits until you finish (and you finish within 15 minutes), the user can re-establish the connection by choosing to retry.If this process takes 15 minutes or longer, users who are logged in lose their current work and their connections to the file server.ProcedureType "CONFIG" at the console and record the parameter information for the driver you are going to change.Unload the driver at the console prompt. For example, to unload the TRXNET driver, type  UNLOAD TRXNET <Enter>Load the driver with the value for the optional parameter.For example, to add a board name for the TRXNET driver, type  LOAD TRXNET NAME=LOCAL <Enter>You are prompted to enter needed configuration information if you did not enter it with the optional parameter.If more than one network board uses the driver, load the driver for each board.Bind a communication protocol to the network board.IDREF="FM75419"See "BIND" on page 8.If the driver is used by more than one network board, bind a communication protocol to each board.Edit the AUTOEXEC.NCF file and add lines to load the driver and bind it to a protocol. For example, to load the NE2 driver automatically (configuration: slot=3, name=BACKBONE) and bind it to the IP protocol, add the following lines to the AUTOEXEC.NCF file:  LOAD NE2 SLOT=3 NAME=BACKBONE  BIND IP TO NE2 NET=26For instructions on editing the AUTOEXEC.NCF file, see IDREF="FM38546""Edit the AUTOEXEC.NCF File" on page 82.ID="FM87181"Load a Driver More than OnceIf you have installed more than one network board of the same type or if you need to use more than one frame type, you must load the same driver more than once. For more information on frame types, see "book="concepts" docset ="nw312"Frame" in Concepts.From the procedures that follow, select the one that fits your situation.Load the Driver for a Second BoardTo load the driver a second time for an additional network board installed in the file server, complete the following steps.ProcedureLoad the driver.For example, to load the NE2000 driver, type  LOAD NE2000 <Enter>Answer "No" to the following prompt by pressing <Enter>:  Do you want to add another frame type for a previously loaded board? nAnswer the prompts for the configuration parameters.When you have successfully added the second configuration to the driver, the following prompt appears:  Previously loaded module was used re-entrantly.Bind a configuration protocol to this unique configuration of the network board.IDREF="FM75419"See "BIND" on page 8.Edit the AUTOEXEC.NCF file and add the commands to load and bind the driver.For example, to load the NE2000 driver (configuration: interrupt=4, port=340, protocol=IPX, net=26) automatically, add the following lines to the AUTOEXEC.NCF file:  LOAD NE2000 INT=4 PORT=340  BIND IPX NE2000 NET=26For more information on editing this file, see IDREF="FM38546""Edit the AUTOEXEC.NCF File" on page 82.Load the Driver for a Second Frame TypeTo add a second frame type to a loaded driver, complete the following steps.ProcedureLoad the driver again.For example, to load the NE2000 driver, type  LOAD NE2000 <Enter>Answer "Yes" to the following prompt by typing "Y" and pressing <Enter>:  Do you want to add another frame type for a previously loaded board? nA list of supported frame types for the board appears.Enter the number of the frame type you want to add and press <Enter>.Bind a configuration protocol to this unique configuration of the network board.IDREF="FM75419"See "BIND" on page 8.Edit the AUTOEXEC.NCF file and add the commands to load and bind the driver.For example, to load and bind the NE2000 driver (configuration: interrupt=3, port=300, frame=ETHERNET_II, protocol=IPX, net=27) automatically, add the following lines to the file:  LOAD NE2000 INT=3 PORT=300 FRAME=ETHERNET_II  BIND IPX NE2000 [PORT=300 INT=3 FRAME=ETHERNET_II] NET=27For instructions on editing this file, see IDREF="FM38546""Edit the AUTOEXEC.NCF File" on page 82.Add Multiple Frames to More than One Network BoardTo add more than one frame type to a network board when the driver has already been loaded for more than one network board, complete the following steps.ProcedureLoad the driver.For example, to load the NE2000 driver, type  LOAD NE2000 <Enter>Answer "Yes" to the following prompt by typing "y" and pressing <enter>:  Do you want to add another frame type for a previously loaded board? nA list of configurations for the network board appears.Enter the number of the configuration that you want to add the frame type to and press <Enter>.A list of supported frame types for the board appears.Enter the number of the frame type you want to add and press <Enter>.Bind a configuration protocol to this unique configuration for the network board.IDREF="FM75419"See "BIND" on page 8.Edit the AUTOEXEC.NCF file and add the command to load and bind the driver with the new configuration.For example, to load and bind the NE2000 driver (configuration: interrupt=4, port=340, frame=Ethernet_SNAP, protocol=IPX, net=30) automatically, add the following lines to the file:  LOAD NE2000 INT=4 PORT=340 FRAME=ETHERNET_SNAP  BIND IPX NE2000 [PORT=340 INT=4 FRAME=ETHERNET_SNAP] NET=30For more information on editing this file, see IDREF="FM38546""Edit the AUTOEXEC.NCF File" on page 82.ID="FM12879"Upgrade idxid="w7342"book="_idx" docset="nw312" tidref="i3085"a LAN DriverIf the developer of a LAN driver releases an updated version of the driver, you can load it without downing the file server.If users are logged in and running critical processes, do not upgrade the driver until they have logged out.You should be able to upgrade the driver in less than five minutes. If a logged-in user makes a call to the file server during the process, the user receives a lost connection message. If the user waits until you finish (and you finish within 15 minutes), the user can re-establish the connection by choosing to retry.If the upgrade takes more than 15 minutes, users lose their current connections and their work.To upgrade a driver, complete the following steps.ProcedureFrom a workstation, log in to the file server as SUPERVISOR (or supervisor equivalent).Copy the updated driver to the SYS:SYSTEM directory.Run CONFIG and record the configuration settings for the network boards that will use the updated driver.Type  CONFIG <Enter>Unload the current driver.For example, type  UNLOAD TRXNET <Enter>When you unload the driver, the driver unbinds all communication protocols.Load the updated driver.For example, type  LOAD TRXNET <Enter>Enter the parameters that match the board's configuration. If more than one network board uses the driver, load the driver for each board.Bind a communication protocol to the network board.IDREF="FM75419"See "BIND" on page 8.If you have loaded the driver more than once, bind a protocol to each network board.ID="FM40275"Troubleshooting idxid="w7343"book="_idx" docset="nw312" tidref="i6910"idxid="w7344"book="_idx" docset="nw312" tidref="i3085"LAN DriversID="FM21971"Most LAN drivers cannot be loaded unless the idxid="w7345"book="_idx" docset="nw312" tidref="i2034"idxid="w7346"book="_idx" docset="nw312" tidref="i2122"network board has a cable attached and the cabling has been properly terminated. Check the cabling. See the appropriate NetWare supplement for your network board to set up and terminate the cabling system.LAN drivers cannot share interrupts, I/O ports, or memory addresses with any other piece of hardware in the file server.The exception is the TOKEN driver, which allows you to configure two Token-Ring network boards to the same interrupt. However, the TOKEN driver cannot share the interrupt with other types of LAN drivers.The following sections should help you prevent conflicts with other network boards, the print server, and other types of hardware in the file server.Network idxid="w7347"book="_idx" docset="nw312" tidref="i3085"Board ConflictsIf two network boards have been configured to the same parameter, the file server may display one of the following symptoms:The LAN driver does not initialize when loaded.The computer refuses to boot DOS or beeps when DOS is booted.If the driver loads and initializes, the conflict prevents the driver from broadcasting any packets.Make sure you fill out the "File Server Worksheet" in Installation and Upgrade so that you have an accurate record of the parameters. Do not configure any network boards (except interrupts for two Token-Ring boards) to the same interrupt, I/O port, memory address, or DMA.Another source of conflict with LAN drivers is overlapping memory addresses or I/O port addresses. Each address parameter specifies a range of bytes that begins at the parameter. (CONFIG displays the range for a loaded LAN driver.)For example, the TOKEN driver (for a board configured to 16 KB) starts its memory address at D80000 and uses all memory from D80000 to DC0000. If you load another driver or install hardware that uses memory starting at D70000 and ending at D85000, the TOKEN driver will not initialize (because of the memory conflict).To avoid memory address and I/O port conflicts, do either of the following:Map the memory ranges of all hardware I/O ports and memory addresses. Make sure that no conflicts exist. (CONFIG displays the memory range of memory addresses and I/O ports for all loaded drivers.)Select options as far away from each other as the software and hardware will allow. For example, if you configure the NE1000 board with an I/O port of 300, select 2E0 or 350 rather than 310 for the I/O port of the RX-Net board.idxid="w7348"book="_idx" docset="nw312" tidref="i3085"Print Server ConflictsThe network board configurations can also conflict with printers if your file server is also your print server. The printers attached to the file server can be configured to use the same interrupts as a LAN board.To prevent conflicts with PSERVER.NLM, complete one or more of the following:Use PCONSOLE to display the interrupts selected for the printers attached to the file server. Do not configure a network board to any interrupt used by a printer.Change a printer so that it is polled and does not use an interrupt (see Chapter 2, "book="print" docset="nw312"Print Server Installation," in Print Server). Polling will free the interrupt so that a network board can use the interrupt.Reconfigure the board's interrupt (see the NetWare supplement for the network board).idxid="w7349"book="_idx" docset="nw312" tidref="i3085"Hardware ConflictsThe following chart lists the interrupts and I/O ports of various pieces of hardware. If the hardware is installed, check the parameters to see if they conflict with the configuration you set for the network board.WIDTH="108"HardwareWIDTH="84"Interrupt (decimal)WIDTH="108"I/O port (hexadecimal)WIDTH="108"COM1WIDTH="84"4WIDTH="108"3F8 - 3FFCOM232F8 - 2FFLPT17378 - 37FIf LPT3 exists, thenLPT1LPT2LPT375-3BC - 3BE378 - 37A278 - 27AAT Controller141FO - 1F817O - 177Floppy Controller61FO - 1F8Tape Controller5280 - 28FEGA23CO - 3CFVGA-102, 46E8Mono Adapter-3BO - 3BFColor Graphics-3DO - 3DFFor example, if you configure a 3C503 network board to interrupt 2 and your file server has an EGA monitor, the network board's interrupt conflicts with the monitor's interrupt.ID="FM50686"LOAD name spaceID="FM62696"Why Use idxid="w7350"book="_idx" docset="nw312" tidref="i2127"LOAD idxid="w7351"book="_idx" docset="nw312" tidref="i3992"idxid="w7352"book="_idx" docset="nw312" tidref="i3274"name space?Use LOAD name space if you have computers that need to store non-DOS files on your idxid="w7353"book="_idx" docset="nw312" tidref="i2300"file server.The following tasks are described in this section:WIDTH="264"TaskWIDTH="48"PageWIDTH="264"Load name spaceWIDTH="48"IDREF="FM50686"158Upgrade name spaceIDREF="FM22118"162Command Format  LOAD [path]name_spaceCommand ParametersReplace path with a full directory path to the directory containing the name space module. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path and volume SYS: is mounted, the operating system assumes that the loadable module is located in the SYS:SYSTEM directory. (Use SEARCH to set up additional paths for automatic searching.)Replace name_space with the name of the module that you need. Name space modules all end with the .NAM extension and are found on the NetWare Operating System_2 diskette. Included with NetWare v3.12 are MAC and OS/2 name space modules.Consult NetWire, your Novell Authorized Reseller, or third-party dealers for a list of other certified name space modules.Additional Information idxid="w7354"book="_idx" docset="nw312" tidref="i3631"idxid="w7355"book="_idx" docset="nw312" tidref="i3631"idxid="w7356"book="_idx" docset="nw312" tidref="i3603"idxid="w7357"book="_idx" docset="nw312" tidref="i7372"A name space module allows you to store non-DOS files on a NetWare file server. When you link the name space module to a volume with the ADD NAME SPACE command, the operating system maintains a directory table with two entries for each file--- one for DOS naming conventions and information and one for non-DOS naming conventions and information. For more information, see "book="concepts" docset="nw312"Name space" in Concepts.Because name space support takes extra memory, be sure to leave enough idxid="w7358"book="_idx" docset="nw312" tidref="i7372"memory to mount the volume.Before adding a name space to a volume, you need to calculate the amount of memory that the name space will require. View the current volume size with INSTALL IDREF="FM92037"(see "Increase the Size of a Volume" on page 76). Then use the following chart IDREF="FM69398"(Table 1-20) to estimate the total amount of memory needed per volume.LBL="1-20"ID="FM69398"Calculating memory for adding name spaceFILE="n312sa01.pbm"In addition to loading the name space module, you must also complete the following tasks to set up the file server for non-DOS files:Link the module to the volumes where you want to store the specific type of non-DOS files on. Use ADD NAME SPACE.For further instructions, see the documentation that accompanies the name space module.Load Name SpaceProcedureTo load name space, type "LOAD" and the name of the name space module.For example, to load support for Macintosh filenames, type  LOAD MAC <Enter>Copy the module to the appropriate directory by completing one of the following:If the name space module is used with volume SYS:, use RCONSOLE to copy the module to the directory containing the file server boot files. Step 3 explains how to add the command to the STARTUP.NCF file.If the module is not used with volume SYS:, do one of the following:Copy the module to the SYS:SYSTEM directory. Step 3 explains how to add the command to the AUTOEXEC.NCF file.Use RCONSOLE to copy the module to the directory containing the file server boot files. Step 3 explains how to add the command to the STARTUP.NCF file.Add the following command to the appropriate .NCF file:  LOAD MACFor instructions on editing this file, IDREF="FM38546"see "Edit the AUTOEXEC.NCF File" on page 82, or IDREF="FM34636""Edit the STARTUP.NCF File" on page 87.Configure a volume to support an additional type of name space.IDREF="FM34136"See "ADD NAME SPACE" on page 3.For further instructions, refer to the documentation that accompanies your non-DOS product.ID="FM22118"Upgrade idxid="w7359"book="_idx" docset="nw312" tidref="i3992"Name SpaceIf the manufacturer of the name space module produces a new version of the module, you can update the module without downing the file server.These steps do not work if volume SYS: is using the name space module and you have used the SECURE CONSOLE or REMOVE DOS command. You will have to down the file server, copy the updated module to the file server boot directory, and then reboot the file server.To update the module without downing the file server, complete the following steps:ProcedureBack up the data on all volumes that use the name space module.Dismount all volumes that use the name space module.Unload the current name space module.For example, to unload the MAC module, type  UNLOAD MAC <Enter>If you did not dismount all the volumes using the non-DOS module, a list of volumes still using the module will appear. Answer "No" to the prompt and use DISMOUNT to dismount the remaining volumes.Insert the diskette with the updated module into drive A of the file server.If you have used SECURE CONSOLE or REMOVE DOS, you cannot load the module from a DOS drive. Use RCONSOLE to copy the file to SYS:SYSTEM and the file server boot directory.Load the updated module.For example, to load the MAC module, type  LOAD A:MAC <Enter>Mount all volumes that were using the module by typing  MOUNT ALL <Enter>The operating system mounts all dismounted volumes. If you do not want all dismounted volumes to mount, mount individual volumes by using MOUNT with the names of the volumes.Copy the updated module to the directory that has the older version of the module.ID="FM52889"LOAD NLM utilityID="FM87679"Why Use Load NLM utility?Use idxid="w7360"book="_idx" docset="nw312" tidref="i3278"LOAD idxid="w7361"book="_idx" docset="nw312" tidref="i2127"NLM idxid="w7362"book="_idx" docset="nw312" tidref="i3275" ( idxid="w7363"book="_idx" docset="nw312" tidref="i4603"NetWare Loadable Module) utility to link management and enhancement programs with the operating idxid="w7364"book="_idx" docset="nw312" tidref="i3278"system. These programs may provide such services as installation, monitor, volume repair, backup, and diagnostics.Some idxid="w7365"book="_idx" docset="nw312" tidref="i4306"NLMs require that you load other NLMs first. Some NLMs load other NLMs automatically. Still others load from the product options menu of INSTALL IDREF="FM23830"(see "Install, Uninstall, or Configure a Product on the File Server" on page 89).Command Format  LOAD [path]NLM_utility [parameter...]Command ParametersReplace path with a full directory path to the directory containing the NLM utility. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path and volume SYS: is mounted, the operating system assumes that the loadable module is located in the SYS:SYSTEM directory. (Use SEARCH to set up additional paths for automatic searching.)Replace NLM_utility with the name of the module you want to load. NLMs shipped with NetWare v3.12 are on the System-2 and System-3 diskettes. Consult NetWire, your Novell Authorized Reseller, or third-party dealers for a list of other approved NLMs. All utilities that are loadable modules have an .NLM extension.Replace parameter with the parameters supported by the module you are loading.Load an NLM UtilityTo load an NLM utility, type "LOAD" and the name of the NLM at the console prompt. For example, to load the INSTALL utility, type  LOAD INSTALL <Enter>Do not unload a protocol-stack NLM such as IPXS or SPXS until you have unloaded all applications that potentially depend on it.idxid="w7366"book="_idx" docset="nw312" tidref="i3665"MAGAZINEWhy Use idxid="w7367"book="_idx" docset="nw312" tidref="i2198"MAGAZINE idxid="w7368"book="_idx" docset="nw312" tidref="i3300"?Use MAGAZINE to confirm that idxid="w7369"book="_idx" docset="nw312" tidref="i3666"magazine requests ("Insert Magazine" and "Remove Magazine") from the idxid="w7370"book="_idx" docset="nw312" tidref="i4371"NetWare server have or have not been satisfied.Command Format  MAGAZINE [parameter]Command ParametersReplace parameter with one of these four options:WIDTH="72"OptionWIDTH="228"ExplanationWIDTH="72"InsertedWIDTH="228"Acknowledges that the specified media magazine was  inserted in response to the "Insert Magazine" console  message.Not InsertedAcknowledges that the specified media magazine was  not inserted in response to the "Insert Magazine"  console message.Not RemovedAcknowledges that the specified media magazine was  not removed in response to the "Remove Magazine"  console message.RemovedAcknowledges that the specified media magazine was  removed in response to the "Remove Magazine"  console message.MATHLIBWhy Use idxid="w7371"book="_idx" docset="nw312" tidref="i3743"MATHLIB idxid="w7372"book="_idx" docset="nw312" tidref="i3300"?Use idxid="w7373"book="_idx" docset="nw312" tidref="i2127"MATHLIB if your server has a idxid="w7374"book="_idx" docset="nw312" tidref="i3741"math coprocessor (a 486 computer or a 386 computer with a math coprocessor chip). You must load idxid="w7375"book="_idx" docset="nw312" tidref="i6540"STREAMS and idxid="w7376"book="_idx" docset="nw312" tidref="i977"CLIB before you load MATHLIB.Command Format  LOAD [path]MATHLIBCommand ParametersReplace path with a full directory path to the directory containing the module. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path and volume SYS: is mounted, the operating system assumes that the loadable module is located in the SYS:SYSTEM directory. (Use SEARCH to set up additional paths for automatic searching.)Additional InformationThe following modules need to be loaded in the order listed below:STREAMSCLIBMATHLIBLoad MATHLIBTo load MATHLIB, type  LOAD MATHLIB <Enter>To make sure that the modules necessary for MATHLIB are loaded automatically when the file server is booted, add the following commands to the AUTOEXEC.NCF file. For instructions on editing the AUTOEXEC.NCF file, see IDREF="FM38546""Edit the AUTOEXEC.NCF File" on page 82.LOAD STREAMSLOAD CLIBLOAD MATHLIBMATHLIBCWhy Use idxid="w7377"book="_idx" docset="nw312" tidref="i3744"MATHLIBC?Use idxid="w7378"book="_idx" docset="nw312" tidref="i3300"MATHLIBC if your file server does not have a idxid="w7379"book="_idx" docset="nw312" tidref="i3741"math coprocessor (a 386 machine without the math coprocessor chip). You must load STREAMS and idxid="w7380"book="_idx" docset="nw312" tidref="i977"CLIB before you load idxid="w7381"book="_idx" docset="nw312" tidref="i2127"MATHLIBC.Command Format  LOAD [path]MATHLIBCCommand ParametersReplace path with a full directory path to the directory containing the module. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path and volume SYS: is mounted, the operating system assumes that the loadable module is located in the SYS:SYSTEM directory. (Use SEARCH to set up additional paths for automatic searching.)Additional InformationThe following modules need to be loaded in the order listed below:idxid="w7382"book="_idx" docset="nw312" tidref="i6540"STREAMSCLIBMATHLIBCLoad MATHLIBCTo load MATHLIBC, type  LOAD MATHLIBC <Enter>To make sure that the modules necessary for MATHLIBC are loaded automatically when the file server is booted, add the following commands to the AUTOEXEC.NCF file. For instructions on editing the AUTOEXEC.NCF file, see IDREF="FM38546""Edit the AUTOEXEC.NCF File" on page 82.LOAD STREAMSLOAD CLIBLOAD MATHLIBCMEDIAWhy Use idxid="w7383"book="_idx" docset="nw312" tidref="i3753"MEDIA?Use idxid="w7384"book="_idx" docset="nw312" tidref="i2198"MEDIA to confirm that idxid="w7385"book="_idx" docset="nw312" tidref="i3750"media requests ("Insert Media" and "Remove Media") from the idxid="w7386"book="_idx" docset="nw312" tidref="i4371"NetWare server have or have not been satisfied.Command Format  MEDIA [parameter]Command ParametersReplaceparameter with one of these four options:WIDTH="108"OptionWIDTH="192"ExplanationWIDTH="108"InsertedWIDTH="192"Acknowledges that the specified media was  inserted in response to the "Insert Media"  console message.Not InsertedAcknowledges that the specified media was  not inserted in response to the "Insert Media"  console message.Not RemovedAcknowledges that the specified media was  not removed in response to the "Remove  Media" console message.RemovedAcknowledges that the specified media was  removed in response to the "Remove Media"  console message.MEMORYWhy Use idxid="w7387"book="_idx" docset="nw312" tidref="i3787"MEMORY?Use idxid="w7388"book="_idx" docset="nw312" tidref="i2127"MEMORY to display the total amount of installed idxid="w7389"book="_idx" docset="nw312" tidref="i3758"memory that the operating system can address.Command Format  MEMORYAdditional InformationNetWare v3.1x automatically addresses memory above 16 MB on EISA computers. On microchannel and ISA (AT bus) computers, NetWare can only automatically address memory up to 16 MB. Use the REGISTER MEMORY command to enable the operating system to address memory above 16 MB.Display the Total Amount of MemoryTo display the total amount of installed memory that the operating system is currently addressing, type  MEMORY <Enter>MIRROR idxid="w7390"book="_idx" docset="nw312" tidref="i3914"STATUSWhy Use idxid="w7391"book="_idx" docset="nw312" tidref="i2127"MIRROR STATUS?Use MIRROR STATUS to display all idxid="w7392"book="_idx" docset="nw312" tidref="i3915"mirrored idxid="w7393"book="_idx" docset="nw312" tidref="i3420"logical partitions and the idxid="w7394"book="_idx" docset="nw312" tidref="i6526"status of each.Command Format  MIRROR STATUSDisplay Status of Mirrored Logical PartitionsTo display the status of all idxid="w7395"book="_idx" docset="nw312" tidref="i1590"mirrored logical partitions, type  MIRROR STATUS <Enter>MIRROR STATUS displays five statuses for partitions. The following table explains each status.LBL="1-14" INLINE="F"Mirror statusesWIDTH="96"StatusWIDTH="204"ExplanationWIDTH="96"Not mirroredWIDTH="204"The partition is not being mirrored.Orphaned stateThe integrity of the data in this partition is not  guaranteed. Use the "Mirroring" option in the  INSTALL utility to recover the partition from its  orhpaned state.Fully synchronizedThe mirrored partitions have the same data and  are functioning correctly.Out of  synchronizationOne of the servers does not have the same data  and is not being remirrored.Being remirroredThe partition is being remirrored. The  percentage of remirroring completed is  displayed.ID="FM90371"MODULESWhy Use idxid="w7396"book="_idx" docset="nw312" tidref="i3933"MODULES?Use MODULES to display the following information about the modules currently loaded in the idxid="w7397"book="_idx" docset="nw312" tidref="i2127"file server:The short name used to load the moduleA idxid="w7398"book="_idx" docset="nw312" tidref="i3278"descriptive string or long name for each moduleThe version number for disk and LAN driversCommand Format  MODULESAdditional InformationA loadable module links itself to the operating system and allocates a portion of the file server's memory for its use. Some modules, such as LAN drivers and disk drivers, need to be loaded every time the file server is brought up. Other modules, particularly the NLM utilities, can be loaded, used, and then unloaded. When the module is unloaded, the module returns its allocated resources to the file server.For additional information, see "book="concepts" docset="nw312"Loadable modules" in Concepts.For additional information about loading and unloading modules, IDREF="FM19779"see "LOAD" and IDREF="FM53575""UNLOAD."List idxid="w7399"book="_idx" docset="nw312" tidref="i3085"the Loaded ModulesTo list the loaded modules, type  MODULES <Enter>Information similar to the following appears:  MONITOR.NLMNetWare 386 Console MonitorVersion 1.67 February 7, 1991Copyright 1991 Novell, Inc. All rights reserved.  RSPX.NLMNetWare 386 Console SPX DriverVersion 1.30 February 9, 1991Copyright 1991 Novell, Inc. All rights reserved.  REMOTE.NLMNetWare 386 Remote ConsoleVersion 1.31 February 13, 1991Copyright 1991 Novell, Inc. All rights reserved.ID="FM91936"MONITORWhy Use idxid="w7400"book="_idx" docset="nw312" tidref="i3300"MONITOR?Use idxid="w7401"book="_idx" docset="nw312" tidref="i3949"MONITOR to lock the file server console and to see how efficiently your network is operating. Use idxid="w7402"book="_idx" docset="nw312" tidref="i2096"MONITOR idxid="w7403"book="_idx" docset="nw312" tidref="i2127"to view information about the following:Utilization and overall activityCache memory statusConnections and their statusDisk drivesMounted volumesLAN driversLoaded modulesFile lock statusMemory usageCommand Format  LOAD [path]MONITOR [parameter]Command ParametersReplace path with a full path. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path and volume SYS: has been mounted, the operating system assumes that the loadable module is located in the SYS:SYSTEM directory. (Use SEARCH to set up additional paths for automatic searching.)nsReplace parameter with ns (no saver) to turn off the screen saver option.If idxid="w7404"book="_idx" docset="nw312" tidref="i3946"idxid="w7405"book="_idx" docset="nw312" tidref="i4916"MONITOR idxid="w7406"book="_idx" docset="nw312" tidref="i2096"is not loaded with the ns parameter, a utilization snake appears on the screen after 1 minute of inactivity if the console is locked (after 10 minutes if it is not locked). As network usage increases, the snake moves faster and the tail (moving randomly around the screen) gets longer. To retrieve the MONITOR display, press any key.nhReplace parameter with nh (no help) if you do not want to load the idxid="w7407"book="_idx" docset="nw312" tidref="i2659"HELP function (and use the additional memory).-pReplace parameter with -p (processor utilization) if you want the Processor Utilization option to appear on the "Available Options" menu.ID="FM28733"Load idxid="w7408"book="_idx" docset="nw312" tidref="i3949"MONITORTo load MONITOR, type  LOAD MONITOR <Enter>If MONITOR is already loaded, the following message appears:  This module is already loaded and cannot be loaded more than once.If this message appears, complete one of the following:Press <Alt><Esc> to move through the activated screens until the MONITOR screen appears.Press <Ctrl><Esc> and select "Monitor Screen" from the list of available screens.ID="FM69598"Interpret the Main idxid="w7409"book="_idx" docset="nw312" tidref="i3946"MONITOR ScreenThe main MONITOR screen displays the status of the network. It also displays an "Available Options" menu that you can use to access detailed information. When idxid="w7410"book="_idx" docset="nw312" tidref="i2111"MONITOR is loaded, a screen similar to the following appears:LBL="1-21"MONITOR main screenFILE="n312sa46.pbm"Each item on the screen is described in the following paragraphs:idxid="w7411"book="_idx" docset="nw312" tidref="i2111"Operating System Version and Date. The idxid="w7412"book="_idx" docset="nw312" tidref="i7289"version and release date of the idxid="w7413"book="_idx" docset="nw312" tidref="i4832"operating system (upper-left corner of the screen).idxid="w7414"book="_idx" docset="nw312" tidref="i2111"Information For Server. The idxid="w7415"book="_idx" docset="nw312" tidref="i4006"name of the file server.File Server Up Time. The length of time the file server has been running since it was last booted.Utilization. The percentage of time the processor is busy.idxid="w7416"book="_idx" docset="nw312" tidref="i879"Original Cache Buffers. The number of cache buffers available when the file server is first booted. The figure represents the number of blocks installed as memory in your file server. The default block size is 4 KB.Total idxid="w7417"book="_idx" docset="nw312" tidref="i879"Cache Buffers. The number of blocks currently available for idxid="w7418"book="_idx" docset="nw312" tidref="i2012"file caching. This number decreases as modules are loaded into memory.idxid="w7419"book="_idx" docset="nw312" tidref="i851"Dirty Cache Buffers. The number of file blocks in memory that are waiting to be written to disk.idxid="w7420"book="_idx" docset="nw312" tidref="i2599"Current Disk Requests. The number of disk requests (in a queue) that the server is waiting to service.idxid="w7421"book="_idx" docset="nw312" tidref="i851"Packet idxid="w7422"book="_idx" docset="nw312" tidref="i4878"Receive Buffers. The number of buffers available to handle station requests. Default: 10.idxid="w7423"book="_idx" docset="nw312" tidref="i1484"Directory idxid="w7424"book="_idx" docset="nw312" tidref="i879"Cache Buffers. The number of buffers allocated to handle directory caching.idxid="w7425"book="_idx" docset="nw312" tidref="i6260"Service Processes. The number of "task handlers" allocated for station requests. When the number of station requests exceeds a certain limit, the file server employs extra task handlers to execute the requests. Once memory is allocated for a service process, it remains allocated. The only way to remove this memory allocation is to down the file server.idxid="w7426"book="_idx" docset="nw312" tidref="i1204"Connections In Use. The number of stations currently attached to the file server.idxid="w7427"book="_idx" docset="nw312" tidref="i2300"Open Files. The number of idxid="w7428"book="_idx" docset="nw312" tidref="i2300"files being accessed by the file server and by network stations.Use "Available Options" MenuThe tasks that can be accomplished with each menu option in the "Available Options" menu on the main screen are listed on the following pages.ID="FM22079"Connection InformationWIDTH="264"TaskWIDTH="48"PageWIDTH="264"List active connectionsWIDTH="48"IDREF="FM10530"182List physical record locks for a userIDREF="FM37964"185Clear a connectionIDREF="FM16225"186List open filesIDREF="FM59490"187Disk InformationWIDTH="264"TaskWIDTH="48"PageWIDTH="264"List system hard disksWIDTH="48"IDREF="FM36784"187List volume segments per hard diskIDREF="FM57085"189Change the "Read After Write Verify" status of the hard diskIDREF="FM28731"191Flash the hard disk lightIDREF="FM11348"192Activate/deactivate a hard diskIDREF="FM77075"194Mount/dismount a removable media deviceIDREF="FM46063"195Lock/unlock a removable media deviceIDREF="FM22029"196ID="FM43045"LAN InformationWIDTH="264"TaskWIDTH="48"PageWIDTH="264"List LAN drivers and statisticsWIDTH="48"IDREF="FM30163"197System Module InformationWIDTH="264"TaskWIDTH="48"PageWIDTH="264"List system modulesWIDTH="48"IDREF="FM25218"201List resources used by system modulesIDREF="FM69637"202Lock File Server ConsoleWIDTH="264"TaskWIDTH="48"PageWIDTH="264"Lock the file server consoleWIDTH="48"IDREF="FM21721"203Unlock the file server consoleIDREF="FM78041"203File Open/ Lock ActivityWIDTH="264"TaskWIDTH="48"PageWIDTH="264"Check the status of a fileWIDTH="48"IDREF="FM81755"204View mounted volumesIDREF="FM43570"206Resource UtilizationWIDTH="264"TaskWIDTH="48"PageWIDTH="264"View memory statisticsWIDTH="48"IDREF="FM99912"206View tracked resourcesIDREF="FM87904"209Processor UtilizationWIDTH="264"TaskWIDTH="48"PageWIDTH="264"Check server processor utilizationWIDTH="48"IDREF="FM26275"211The "Processor Utilization" option appears on the "Available Options" menu only if you use the -P parameter when you load MONITOR.ExitWIDTH="264"TaskWIDTH="48"PageWIDTH="264"Exit MONITORWIDTH="48"IDREF="FM75852"212ID="FM10530"List Active idxid="w7429"book="_idx" docset="nw312" tidref="i1204"ConnectionsUse this option to view information about individual connections.ProcedureSelect "Connection Information" from the "Available Options" menu.Select a username to see information about the user's connection.A display similar to the following appears. The top of the display gives statistics on the user; the bottom half shows the idxid="w7430"book="_idx" docset="nw312" tidref="i2300"open files. In the following displays, idxid="w7431"book="_idx" docset="nw312" tidref="i7137"user SUPERVISOR has SYSCON open.LBL="1-22"MONITOR "Connection Information" screenFILE="n312sa49.pbm"Each item in the display is described in the following paragraphs:idxid="w7432"book="_idx" docset="nw312" tidref="i7137"Connection idxid="w7433"book="_idx" docset="nw312" tidref="i1203"time. Shows how long the user has been logged in to the network. Accounts can be billed for connection time.idxid="w7434"book="_idx" docset="nw312" tidref="i4485"Network idxid="w7435"book="_idx" docset="nw312" tidref="i164"address. Displays the network address (cabling idxid="w7436"book="_idx" docset="nw312" tidref="i4551"network number), the station (node) address, and the socket address. The socket address is used mainly with OS/2 idxid="w7437"book="_idx" docset="nw312" tidref="i7493"workstations. Network OS/2 workstations can have several socket addresses (or logical connections to the file server), enabling the workstation to perform multiple operations simultaneously.idxid="w7438"book="_idx" docset="nw312" tidref="i2034"Requests. Displays the number of requests the connection has made to the file server since the server was last booted. Accounts can be billed by the number of requests made.Kilobytes read. Displays the number of kilobytes the connection has accessed for reading. Accounts can be billed for the number of kilobytes read.Kilobytes written. Displays the number of kilobytes the connection has used in writing data to disk. Accounts can be billed for the number of kilobytes written.Status. Displays one of the following messages:WIDTH="96"NormalWIDTH="204"Logged in and functioning.WaitingWaiting for a file to be unlocked so that  the station can get the file and lock it.Not-logged-inAttached to the idxid="w7439"book="_idx" docset="nw312" tidref="i1204"file server, but not  logged in.idxid="w7440"book="_idx" docset="nw312" tidref="i6219"Semaphores. Displays the number of semaphores a connection has open. A semaphore can arbitrate the following:How many tasks can use a resource (bus, hard disk, network) at the same timeHow many workstations can run a program at the same timeidxid="w7441"book="_idx" docset="nw312" tidref="i3423"Logical record locks idxid="w7442"book="_idx" docset="nw312" tidref="i3378"idxid="w7443"book="_idx" docset="nw312" tidref="i3378". Displays the number of logical record locks a connection has. A logical record lock flags a file or application so that only one station at a time can use it.idxid="w7444"book="_idx" docset="nw312" tidref="i2300"Open files. Lists the files that are currently being accessed by the workstation.ID="FM37964"List idxid="w7445"book="_idx" docset="nw312" tidref="i5083"Physical Record Locks for a UserWhile accessing a database, a workstation can have records locked for its use. Other workstations cannot access these locked records. Follow these steps to see which records are locked.ProcedureSelect "Connection Information" from the "Available Options" menu.Select the user whose information you want to see.Select an open file to see the current record locks, if any.A "Record Lock" screen similar to the following appears:LBL="1-23"MONITOR "Record Lock Status" screenFILE="n312sa50.pbm"Each item in the screen is described below:Start. The lock begins at this offset in the file.End. The lock ends at this offset in the file.Record idxid="w7446"book="_idx" docset="nw312" tidref="i5083"lock. Displays one of the following messages:WIDTH="108"Locked ExclusiveWIDTH="192"Locked so that no one else can read or  write to the record.Locked ShareableLocked so that other stations can  read, but not write to, the record.LockedLogged for future locking. The type of  lock is specified when the lock is  completed.TTS Holding LockUnlocked by the application;  however, file transactions are not  completed, so TTS has locked it. TTS  can restore original data to the record  if it needs to back out the transaction.Status. Displays one of the following messages:WIDTH="108"LoggedWIDTH="192"A set of records is being prepared for  locking. The file server logs each file  before locking the set to avoid  deadlock or "deadly embrace."Not LoggedThis is the normal condition. There  are no pending requests for a set of  locks.ID="FM16225"Clear idxid="w7447"book="_idx" docset="nw312" tidref="i1204"a connectionWhen a workstation hangs, its files are left open. Before rebooting the workstation, use MONITOR to idxid="w7448"book="_idx" docset="nw312" tidref="i2300"close the files safely and clear the connection.ProcedureSelect "Connection Information" from the "Available Options" menu.Select the user whose workstation is not functioning and press <Delete>.Use the Mark key (<F5> on most computers) to select more than one user.Answer "Yes" to the prompt to clear the connection.ID="FM59490"List Open idxid="w7449"book="_idx" docset="nw312" tidref="i2300"FilesDetermine the extent of a user's activity on the file server by viewing such statistics as the number of requests to read from or write to a file and the number of files that the user currently has open.ProcedureSelect "Connection Information" from the "Available Options" menu.Select the user whose activity you want to check. The user's statistics and opened files are displayed on the screen.Although executable files can be displayed in the window, they are not usually listed because once the files have been read into memory, they are closed.ID="FM36784"List System idxid="w7450"book="_idx" docset="nw312" tidref="i2599"Hard idxid="w7451"book="_idx" docset="nw312" tidref="i2599"DisksTo check the number and type of hard disks attached to the file server, complete the following steps.ProcedureSelect "Disk Information" from the "Available Options" menu.Select one of the hard disks you need information about.For an explanation of the numbers and codes, see "book="concepts" docset="nw312"Device Numbering" in Concepts.A screen similar to the following idxid="w7452"book="_idx" docset="nw312" tidref="i2599"appears:LBL="1-24"MONITOR hard disk information screenFILE="n312sa1h.pbm"Each item on the screen is described below. A description of the tasks that can be performed from the "Drive Status" form start on page IDREF="FM57085"189 ("List Volume Segments Per Hard Disk").ID="FM72257"idxid="w7453"book="_idx" docset="nw312" tidref="i1561"Driver. The name of the disk driver that operates the hard disk.Disk size. The size (in megabytes) of all partitions on the hard disk.Partitions. The number of partitions defined on the hard disk.idxid="w7454"book="_idx" docset="nw312" tidref="i3917"Mirror idxid="w7455"book="_idx" docset="nw312" tidref="i2599"Status idxid="w7456"book="_idx" docset="nw312" tidref="i1585". Status options are explained below:WIDTH="108"MirroredWIDTH="192"Data is stored on more than one hard  disk.Not mirroredData is stored on one disk.RemirroringData is being copied to a duplicate  hard disk so that both disks have the  same (mirrored) data.idxid="w7457"book="_idx" docset="nw312" tidref="i2682"Hot idxid="w7458"book="_idx" docset="nw312" tidref="i2599"Fix Status. Hot Fix options are explained below:WIDTH="108"NormalWIDTH="192"Hot Fix is functioning.Not-hot-fixedHot Fix has failed. Remove the hard  disk from the file server.Partition Blocks. The total space on the partition shown in blocks. (Default block size is 4 KB.)Data Blocks. The space (shown in blocks) on the hard disk available to hold data.Redirection Blocks. The number of blocks currently allocated for the Hot Fix Redirection Area.Redirected Blocks. The number of bad blocks found by Hot Fix.Reserved Blocks. Blocks reserved for Hot Fix tables.When the number of Reserved Blocks plus the number of Redirected Blocks equals the number of Redirection Blocks, Hot Fix has failed on the hard disk.ID="FM57085"List idxid="w7459"book="_idx" docset="nw312" tidref="i7372"Volume Segments Per Hard DiskIf you discover errors on a particular hard disk, you can determine which volumes have segments, or parts, on the hard disk.ProcedureSelect "Disk Information" from the "Available Options" menu.Select one of the hard disks.For an explanation of the device codes, see "book="concepts" docset="nw312"Device numbering" in Concepts.A "Drive Status" form similar to the following appears:LBL="1-25""Drive Status" formFILE="n312sa51.pbm"If the "Drive Operating Status" field lists "Inactive," the "Volume Segments On Drive" field will be blank.IDREF="FM77075"See "Activate/Deactivate a Hard Disk" on page 194 and activate the disk. Then continue with Step 4.Select the "Volume Segments on Drive" field in the "Drive Status" menu.A window similar to the following appears. This window lists the volumes that are on the hard disk.LBL="1-26"ID="FM73250""Volume Segments" listFILE="n312sa52.pbm"ID="FM28731"Change the "Read After Write idxid="w7460"book="_idx" docset="nw312" tidref="i7283"Verify" Status of the idxid="w7461"book="_idx" docset="nw312" tidref="i2599"Hard DiskEach driver has a default setting for verifying that the data written to disk matches the data still in memory. To change the default setting for a selected hard disk, complete the following steps.ProcedureSelect "Disk Information" from the "Available Options" menu.Select one of the hard disks.For an explanation of the device codes, see "book="concepts" docset="nw312"Device numbering" in Concepts.A "Drive Status" form appears.Complete one of the following:If the driver for the hard disk you selected supports the "Read After Write Verify" option, the field displays a status message ("Software Level," "Hardware Level," or "Disabled"). Continue with Step 4.If the driver displays "Not Supported," you cannot change the default setting. Press <Esc> and select another hard disk.Select the "Read After Write Verify" field.The following menu idxid="w7462"book="_idx" docset="nw312" tidref="i7283"appears:LBL="1-27""Read After Write Status menuFILE="n312sa53.pbm"Each option is described here. Not all options are available for all drivers. The driver determines which options are supported.Software Level Verify. Selects the driver to perform the read-after-write verification. Displays a "Software Level" status in the "Read After Write Verify" field in the "Drive Status" form.Hardware Level Verify. Selects the controller to perform the read-after-write verification. Displays a "Hardware Level" status in the "Read After Write Verify" field in the "Drive Status" form.Disable Verify. Disables both the driver and the controller from performing a read-after-write verification. Select this option if your hard disk performs a read-after-write verification internally. (Check the hard disk's specifications.) The option displays a "Disabled" status in the "Read After Write Verify" field in the "Drive Status" form.Select the option you want.The "Drive Status" form reappears. If the option you selected is not displayed in the "Read After Write Verify" field, that option is not supported by the driver.idxid="w7463"book="_idx" docset="nw312" tidref="i2599"ID="FM11348"Flash the Hard Disk LightUse the "Drive Light Status" option to physically identify which hard disk corresponds to the drive listed in the "System Disk Drives" window. This option can be set so that the disk light flashes at a timed interval.ProcedureSelect "Disk Information" from the "Available Options" menu.Select a hard disk from the "System Disk Drives" window.For an explanation of the device codes, see "book="concepts" docset="nw312"Device numbering" in Concepts.A "Drive Status" form appears.Complete one of the following:If the driver for the hard disk you selected supports the "Drive Light Status" option, the field displays a status message ("Normal" or "Flashing"). Continue with Step 4.If the driver displays "Not Supported," you cannot change the default setting. Press <Esc> and select another hard disk.Select the "Drive Light Status" field.The following menu appears:LBL="1-28""Drive Light Status" fieldFILE="n312sa54.pbm"Each option is described below.Flash Light. Flashes the hard disk light at a regular interval so that you can identify the disk. Displays a "Flashing" status in the "Drive Light Status" field in the "Drive Status" form.Return To Normal. Returns control of the light to the hard disk. Displays a "Normal" status in the "Drive Light Status" field in the "Drive Status" form.Select the option you want.The "Drive Status" form reappears.ID="FM77075"Activate/ idxid="w7464"book="_idx" docset="nw312" tidref="i2599"Deactivate a Hard DiskUse the "Drive Operating Status" option to manually activate or deactivate a hard disk.ProcedureSelect "Disk Information" from the "Available Options" menu.Select a hard disk from the "System Disk Drives" window.For an explanation of the device codes, see "book="concepts" docset="nw312"Device numbering" in Concepts.A "Drive Status" form similar to the following appears:Select the "Drive Operating Status" field.The following menu appears:LBL="1-29""Operating Status" menuFILE="n312sa56.pbm"Each option is described below.Activate Drive. Controls whether the "Drive Status" window displays information about the hard disk (such as Hot Fix and mirror status information). Displays an "Active" status in the "Drive Operating Status" field in the "Drive Status" form.Deactivate Drive. Removes all NetWare information from the drive status window except for the disk size and the driver the hard disk was using. Displays an "Inactive" status in the "Drive Operating Status" field in the "Drive Status" form.Select the option you want.The "Drive Status" form reappears.ID="FM46063"Mount/Dismount idxid="w7465"book="_idx" docset="nw312" tidref="i5845"a idxid="w7466"book="_idx" docset="nw312" tidref="i5845"Removable Media DeviceUse the "Removable Drive Mount Status" option to manually mount or dismount a removable media device.ProcedureSelect "Disk Information" from the "Available Options" menu.Select a removable media device from the "System Disk Drives" window.A "Drive Status" form appears.Complete one of the following:If the driver for the hard disk you selected supports the "Removable Drive Mount Status" option, the field displays a status message ("Mounted" or "Dismounted"). Continue with Step 4.If the driver displays nothing in the "Removable Drive Mount Status" field, the device you selected is not a removable media device. Press <Esc> and select another device.ID="FM53008"Select the "Removable Drive Mount Status" field.The following menu appears:LBL="1-30""Drive Mount Status" menuFILE="n312sa58.pbm"Each option is described here.Mount Drive. Mounts the media so that information can be accessed from it. Displays a "Mounted" status in the "Removable Drive Mount Status" field in the "Drive Status" form.Dismount Drive. Dismounts the media so that information cannot be accessed from it. Displays a "Dismounted" status in the "Removable Drive Mount Status" field in the "Drive Status" form.Select the option you want.The "Drive Status" form reappears.ID="FM22029"Lock/Unlock a Removable Media DeviceUse the "Removable Drive Lock Status" option to lock or unlock a removable media device. Locking the device prevents the media from being physically removed.ProcedureSelect "Disk Information" from the "Available Options" menu.Select a removable media device from the "System Disk Drives" window.A "Drive Status" form appears.Complete one of the following:If the driver for the hard disk you selected supports the "Removable Drive Lock Status" option, the field displays a status message ("Locked" or "Unlocked"). Continue with IDREF="FM30977"Step 4.If the driver displays nothing in the "Removable Drive Lock Status" field, the device you selected is not a removable media device. Press <Esc> and select another device.ID="FM30977"Select the "Removable Drive Lock Status" field.The following menu appears:LBL="1-31""Drive Lock Status" menuFILE="n312sa60.pbm"Each option is described below.Lock Drive. Locks the media so that the media cannot be removed from the device. Displays a "Locked" status in the "Removable Drive Lock Status" field in the "Drive Status" form.Unlock Drive. Unlocks the media so that it can be removed from the device. Displays an "Unlocked" status in the "Removable Drive Lock Status" field in the "Drive Status" form.Select the option you want.The "Drive Status" form reappears.ID="FM30163"List idxid="w7467"book="_idx" docset="nw312" tidref="i3085"LAN Drivers and idxid="w7468"book="_idx" docset="nw312" tidref="i1081"StatisticsBy comparing information about the LAN drivers installed on the file server, you can tell which cabling system is handling the most traffic. If errors occur frequently on a high-traffic system, you may want to switch some of the workstations on the busy system to a new cabling system or to a less busy cabling system.ProcedureSelect " idxid="w7469"book="_idx" docset="nw312" tidref="i1081"LAN Information" from the "Available Options" menu.Select a LAN driver.A screen similar to the following appears:LBL="1-32"Sample LAN driver statistics screenFILE="n312sa61.pbm"Use the Up- and Down-arrow keys or the PageUp and PageDown keys to view all available information.The idxid="w7470"book="_idx" docset="nw312" tidref="i1731"version, address, and protocol information is similar to the information you can view with CONFIG.The generic statistics common to most of the current drivers are listed on the following pages.Custom statistics vary, depending on the LAN driver installed. For detailed definitions of the statistics listed by the LAN drivers that Novell currently supports, IDREF="FM56327"see "Custom LAN Driver Statistics Shown in MONITOR." For statistical information about third-party drivers, check the documentation that comes with the driver.Driver name. The driver name and parameters that correspond to the hardware settings on the network board.idxid="w7471"book="_idx" docset="nw312" tidref="i7289"Version. The current version of the driver.idxid="w7472"book="_idx" docset="nw312" tidref="i158"Node idxid="w7473"book="_idx" docset="nw312" tidref="i164"address. The station idxid="w7474"book="_idx" docset="nw312" tidref="i158"or node address of the network board in the file server.Protocols. The communication protocols bound to the driver with BIND.idxid="w7475"book="_idx" docset="nw312" tidref="i4551"Network address. The network number assigned to the cabling system the LAN driver is operating on. This address appears only if the IPX protocol has been bound to the board.Total packets sent. The number of packets sent from the file server through this LAN driver. By comparing this figure with the figures for other LAN drivers, you can see which driver is handling the most traffic.idxid="w7476"book="_idx" docset="nw312" tidref="i4903"Total packets received. The number of packets received by the file server since it was last booted (includes file service requests, packets routed to another network, and packets sent to other IPX sockets in the file server).No ECB available count. A counter that increments when a device sends a packet to your file server, but a idxid="w7477"book="_idx" docset="nw312" tidref="i4878"packet receive buffer is not available. The file server allocates more packet receive buffers after each incident until the file server reaches its maximum limit (configurable with a SET parameter).If you are using an EISA or microchannel bus master board (such as the NE3200 board), you probably need to increase both the minimum and maximum number of packet receive buffers. See the following SET parameters: IDREF="FM85712""Minimum Packet Receive Buffers = number" on page 276 and IDREF="FM40728""Maximum Packet Receive Buffers = number" on page 275.Send packet too big count. A counter that increments when your file server tries to transmit a packet that is too large for your file server's hardware to handle.Send packet too small count. A counter that increments when a device transmits a packet that is too small for your file server's hardware to handle.Receive packet overflow count. A counter that increments when your file server receives a packet that is too big to store in a cache buffer. This should happen rarely, unless you are running a software program that does not negotiate packet size. Contact the vender for an updated version of the software.Receive packet too big count. A counter that increments when the file server receives a packet that is too big.Receive packet too small count. A counter that increments when the file server receives a packet that is too small.Send packet miscellaneous errors. A counter that increments when errors occur with send packets.Receive packet miscellaneous errors. A counter that increments when errors occur with receive packets.Send packet retry count. A counter that increments when the file server tries to send a packet but is unsuccessful because of a hardware error. Based on the number of retries in the retry counter, the file server will continue to try to send the packet until it is successfully sent or the retry setting is reached. If you are receiving a large number of these errors, use LOAD LANdriver to increase the maximum retry count, or check the cabling and workstation hardware.Checksum errors. A counter that increments when the checksum byte at the end of the packet does not match the sum of the bytes contained in the packet. This indicates a data error.Hardware receive mismatch count. A counter that increments when the packet length received by the hardware and the packet length specified by the packet do not match.ID="FM25218"List System ModulesLoaded modules use memory and other types of file server resources. To see the amount of memory and the types of resources each module uses, complete the following steps.ProcedureSelect "System Module Information" from the "Available Options" menu.Select a module. A screen similar to the following appears:LBL="1-33"System module information screenFILE="n312sa62.pbm"The first screen indicates the size of the module and the name the loadable module was loaded with.The NetWare operating system is not a loadable module, even though it will be listed as a module in this screen. As a result, MONITOR does not track the size of its code and data.The "Resource Tags" menu is described in the following section, "List Resources Used by System Modules."ID="FM69637"List idxid="w7478"book="_idx" docset="nw312" tidref="i3278"Resources Used by System ModulesProcedureSelect "System Module Information" from the "Available Options" menu.Select a module.A system module information screen appears.The "Resource Tags" menu lists all the resource tags defined by the module. Each tag allows the module to allocate resources from the file server.To view how much of a resource a resource tag uses, select a tag from the menu.A screen similar to the following appears:LBL="1-34""Resource Information" screenFILE="n312sa63.pbm"Each item on the screen is described below.Tag. The name of the resource tag that the loadable module gave to a resource.Module. The name of the module using the tag. The NetWare operating system can be used as a module name.Resource. The type of idxid="w7479"book="_idx" docset="nw312" tidref="i5908"resource the tag is using. For a definition of each type of idxid="w7480"book="_idx" docset="nw312" tidref="i5908"resource, see IDREF="FM33775""Tracked Resources Displayed in MONITOR" on page 519.In Use. The amount of idxid="w7481"book="_idx" docset="nw312" tidref="i5908"memory, in bytes, currently used or the number of resources being used. For example, the Cache Movable Memory resource displays the total number of bytes; the Screens resource displays the total number of activated screens.ID="FM21721"Lock idxid="w7482"book="_idx" docset="nw312" tidref="i2096"the File Server Console idxid="w7483"book="_idx" docset="nw312" tidref="i6177"You can lock the file server console so that only those who know either the keyboard password or the SUPERVISOR password can unlock the keyboard and use commands and equipment associated with the file server.To lock the console, complete the following steps.ProcedureSelect "Lock File Server Console" from the "Available Options" menu.Type in a password to lock the keyboard.Use either the SUPERVISOR's password or another password of your choice.ID="FM78041"Unlock the File Server ConsoleProcedureIf the console monitor is creating patterns, press any key to restore the main MONITOR display.Type either the SUPERVISOR password or the keyboard password and press <Enter>.ID="FM81755"Check the Status of a FileUse MONITOR to display how often a file is being used, how many idxid="w7484"book="_idx" docset="nw312" tidref="i2300"connections are using a file, how a file is used, or whether a file is locked.ProcedureSelect "File Open / Lock Activity" from the "Available Options" menu.Select the path (volume, directory, subdirectory, file), one level at a time, from the "Select an Entry" window.When you have selected a file, screens similar to the following appear:LBL="1-35"File Lock/Activity screenFILE="n312sa64.pbm"Each item in the display is described below.Use count. The number of connections that have the file open, logged, or locked.Open count. The number of connections that currently have the file open.Open for read. The number of connections that currently have the file open for reading.Open for write. The number of connections that currently have the file open for writing.Deny read. The number of connections that have opened the file and will not allow other stations access.Deny write. The number of connections that have opened the file and will not allow other stations to write to the file.idxid="w7485"book="_idx" docset="nw312" tidref="i2300"Status. Displays one of the following messages:WIDTH="108"LockedWIDTH="192"Other users cannot access the file.Not LockedOther users can access the file.Conn. A list of the connections using the file.Task. A number assigned by the shell to an application program.idxid="w7486"book="_idx" docset="nw312" tidref="i2300"Lock Status. Displays one of the following messages:WIDTH="108"ExclusiveWIDTH="192"No one else can read or write to the  record.ShareableOthers may read, but not write to, the  record.TTS Holding LockThe file was unlocked by the  application; however, the  transactions are not completed, so  TTS has locked it. TTS can restore  original data to the record if it needs  to back out the transaction.Not LoggedThis is the normal condition. No  requests for a set of locks are pending.ID="FM43570"View Mounted VolumesYou can use MONITOR to determine which volumes are currently mounted on your file server.Select "File Open / Lock Activity" from the "Available Options" menu.The "Select An Entry" screen lists all currently mounted volumes.ID="FM99912"View Memory Statisticsidxid="w7487"book="_idx" docset="nw312" tidref="i3758"Memory usage statistics can help you determine how the idxid="w7488"book="_idx" docset="nw312" tidref="i3758"memory in your idxid="w7489"book="_idx" docset="nw312" tidref="i851"file server is being used and when to add more memory.Select "Resource Utilization" from the "Available Options" menu.A screen similar to the following appears:LBL="1-36""Server Memory Statistics" screenFILE="n312sa65.pbm"ID="FM84508"The "byte" column indicates how many bytes of memory are reserved for a particular memory pool or buffer.The "percentage" column indicates the amount of available memory being used for a particular memory pool or buffer.The "in use" column indicates how many of the available bytes are being used by a particular memory pool. If you run VREPAIR and the "In Use" statistics are considerably lower than the total amount in the memory pools, down the file server to return the Alloc and Permanent pools to their original amounts.The types of memory pools and buffers are described below. For a complete description, see "book="concepts" docset="nw312"Memory Pools" in Concepts.Permanent Memory pool. This statistic contains both permanent and semi-permanent memory. Both pools are used for long-term memory needs such as directory cache buffers and packet receive buffers.Once this memory is allocated as either permanent or semi-permanent memory, the memory is not returned to the regular cache buffers unless the file server is rebooted.Alloc Memory pool.Alloc Memory pool is a shorter name for the Alloc Short Term Memory pool. This pool allocates memory to loadable modules for temporary or short-term use. For example, modules with pop-up windows use Alloc Memory to store previous menu information on screen.The operating system also uses this pool for the following types of information: mappings, user connection information, and server advertising.Once memory is allocated to this pool, it is not returned to the regular cache buffers. When the module is unloaded, the allocated memory returns to the pool for other loadable modules.The "Maximum Alloc Short Term Memory" parameter in SET controls the size of the Alloc Short Term Memory pool. If the amount of memory allocated to this pool reaches the default of 8,000,000 bytes, increase the SET parameter by 1,000,000.idxid="w7490"book="_idx" docset="nw312" tidref="i879"Cache Buffers. This memory pool lists the total amount of memory available for data caching. The amount is listed in bytes. When this figure reaches 20%, you need to add more memory to your file server.You can do any of the following to temporarily increase the number of cache buffers.Unload loadable modules, such as INSTALL, DISKSET, or MONITOR, that are not currently needed.Down the file server and reboot it to recover unused blocks in the permanent and allocated memory pools.Use REMOVE DOS to free the file server memory being used by DOS.Cache Movable Memory. This pool lists memory buffers that are "rotating free blocks" in a certain range of memory. The operating system can move the location of these memory blocks at any time to facilitate memory management. Hash tables are a good example of data that uses this kind of a buffer. Once a program is no longer using these buffers, it returns the buffers to the cache buffer pool.Cache Non-Movable Memory. This pool lists memory buffers that are allocated to a program temporarily. Once the program no longer needs these buffers, it returns the buffers to the cache buffer pool.Total Server Work Memory. This statistic displays the total number of bytes available for the server to use. This total equals the amount of installed memory minus the memory needed for SERVER.EXE, DOS, and ROM BIOS.ID="FM87904"View idxid="w7491"book="_idx" docset="nw312" tidref="i3278"Tracked ResourcesNames are given to various operating system idxid="w7492"book="_idx" docset="nw312" tidref="i5908"resources so that the resources can be idxid="w7493"book="_idx" docset="nw312" tidref="i6857"tracked. The operating system allocates these resources to loadable modules when they are loaded, and then tracks the resources to make sure that all the resources are returned when the module is unloaded. By looking at each resource, you can see which modules are using that particular resource. For a definition of each tracked resource, see IDREF="FM33775""Tracked Resources Displayed in MONITOR" on page 519.To view tracked resources, complete the following steps.ProcedureSelect "Resource Utilization" from the "Available Options" menu.A list similar to the following appears:LBL="1-37""Tracked Resources" listFILE="n312sa67.pbm"Use the Up- and Down-arrow keys or the PageUp and PageDown keys to scroll through the list.Select the idxid="w7494"book="_idx" docset="nw312" tidref="i5908"resource you want information about.A list similar to the following appears:LBL="1-38""Resource Tags" listsFILE="n312sa66.pbm"The module that assigned the resource tag is listed first, followed by the resource tag name.From the "Resource Tag" list, select the module that you want more resource information about.A screen similar to the following appears:LBL="1-39""Resource Information" screenFILE="n312sa68.pbm"Each item on the screen is described below.Tag. The name of the resource tag. If the module needs to allocate a resource for more than one function, it can assign a different resource tag to each function. For example, the "Resource Tags" screen in Step 3 shows SERVER.NLM with six different resource tags for the same resource (Alloc Short Term Memory).Module. The name of the module using the tag. The NetWare operating system can be used as a module name.idxid="w7495"book="_idx" docset="nw312" tidref="i5908"Resource. The type of resource the tag is using. For a definition of each type of resource, see IDREF="FM33775""Tracked Resources Displayed in MONITOR" on page 519.In Use. The amount of idxid="w7496"book="_idx" docset="nw312" tidref="i5908"memory, in bytes, currently used by the loadable module, or the number of resources being used. For example, the Cache Movable Memory resource displays the total number of bytes; the Screens resource displays the total number of activated screens.ID="FM26275"Checking a Server's idxid="w7497"book="_idx" docset="nw312" tidref="i4371"idxid="w7498"book="_idx" docset="nw312" tidref="i5591"Processor idxid="w7499"book="_idx" docset="nw312" tidref="i7270"UtilizationOne possible cause of network problems is the monopolizing of the Central Processing Unit (CPU) by a single process. This procedure helps you know which processes are using the CPU and how much load they are putting on the CPU's time.ProcedureSelect "Processor Utilization" from the "Available Options" menu. The "Processor Utilization" option appears on the "Available Options" menu only if you used the -P parameter when you loaded MONITOR as in the example below:  LOAD idxid="w7500"book="_idx" docset="nw312" tidref="i3954"MONITOR -P <Enter>Press <F3> to view a list of the currently loaded idxid="w7501"book="_idx" docset="nw312" tidref="i5586"processes and interrupts.For each item on the list, notice the percentage given in the "Load" column. This percentage shows which processes are taking the most CPU time.To idxid="w7502"book="_idx" docset="nw312" tidref="i5591"balance processor utilization, unload noncritical NLMs that are taking a large percentage of CPU time.ID="FM75852"Exit idxid="w7503"book="_idx" docset="nw312" tidref="i3949"MONITORYou can exit MONITOR by pressing <Esc> until the exit prompt appears or by pressing the hot key to exit temporarily.Using the Escape KeyUse <Esc> to unload the MONITOR module and free up memory.ProcedurePress <Esc> until "Exit" appears on the "Available Options" menu.Answer "Yes" to the "Exit Monitor?" prompt.Using the Hot KeyYou can temporarily exit MONITOR by pressing <Alt><Esc>. This also works for any other loadable module with menus.Even though the module no longer appears on the screen, it is still loaded. You can press <Alt><Esc> to return to MONITOR at any time.ID="FM70396"MOUNTWhy Use idxid="w7504"book="_idx" docset="nw312" tidref="i3962"MOUNT?Use idxid="w7505"book="_idx" docset="nw312" tidref="i2127"MOUNT to make a idxid="w7506"book="_idx" docset="nw312" tidref="i6910"volume available to your users. You can idxid="w7507"book="_idx" docset="nw312" tidref="i7372"mount and dismount one or all volumes while the file server is running.Command Format  MOUNT volume_nameor  MOUNT ALLMount a New idxid="w7508"book="_idx" docset="nw312" tidref="i7372"Volume or One that Is Not Used OftenUse MOUNT to make a newly created volume available to your users or to mount a volume that is not used very often. You may want to leave rarely used volumes dismounted since each mounted volume takes up memory and reduces the memory available for file caching.To mount a volume, type  MOUNT volume_name<Enter>If you try to mount a volume before creating it with INSTALL or if the file server has a problem locating all the segments in a given volume, the following message appears:  Volume volume_name could NOT be mounted.  Some or all volume segments cannot be located.  If you try to mount a volume that is already mounted, the following message appears:  Volume volume_name is already mounted.Mount idxid="w7509"book="_idx" docset="nw312" tidref="i7372"Several VolumesTo mount several volumes at once, type  MOUNT ALL <Enter>NAMEWhy Use idxid="w7510"book="_idx" docset="nw312" tidref="i2127"idxid="w7511"book="_idx" docset="nw312" tidref="i3982"NAME?Use NAME to display the name of the file server.Command Format  NAMEDisplay the idxid="w7512"book="_idx" docset="nw312" tidref="i2111"Name idxid="w7513"book="_idx" docset="nw312" tidref="i4006"of the File ServerTo view the name of the file server, type  NAME <Enter>When you enter this command, the console displays the name of the file server in the following format:  This is Server server_nameNLICLEAR (Not-Logged-In CLEAR)Why Use NLICLEAR?NLICLEAR is an NLM that is copied from the SYSTEM-3 diskette. NLICLEAR deletes or "clears" unauthenticated user connections. Unauthenticated connections cannot be reused until they are cleared. NLICLEAR allows you to reuse idle connections by periodically deleting them.Command Format  LOAD [path]NLICLEAR [parameter...]Command ParametersReplace path with a full path to the directory containing the NLICLEAR module. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path, the operating system looks for NLICLEAR in SYS:SYSTEM. (Use SEARCH to set up additional paths for automatic searching.)Replace parameter with one or more of the following parameters.NOTIFYCauses a message to be written to the server console screen each time a connection is cleared.Default: No notificationPOLL=numberSets the time (in seconds) for NLICLEAR to wait between checks of the user connection table. The number of seconds can be from 15 to 3600.Default: 60 secondsCONN=numberSets the uppermost number of connections to check. Connections are assigned from 1 to the number of licensed connections. For example, on a 250-user version of NetWare v3.12, CONN=50 would only check the last 50 connections (201-250). Connections 1-200 would not be checked or cleared by NLICLEAR. NLICLEAR does not load on a one-user server if you use this parameter. Default: Number of licensed user connectionsAdditional InformationUnauthenticated user connections occur whenA user specifies a login name after a LOGIN or ATTACH       command, but does not enter a password to complete the login procedure.A user logs out without logging in elsewhere.The shell establishes a connection with the file server, but no login is attempted.In these cases, the connection is made to the server, but no authentication is granted to the user except to complete the login or to log in elsewhere.NMAGENTWhy Use idxid="w7514"book="_idx" docset="nw312" tidref="i4634"NMAGENT?Use idxid="w7515"book="_idx" docset="nw312" tidref="i2127"NMAGENT idxid="w7516"book="_idx" docset="nw312" tidref="i3300"to allow LAN drivers to register and pass network management parameters. NMAGENT must be loaded before idxid="w7517"book="_idx" docset="nw312" tidref="i3085"LAN drivers can be loaded. If you do not load NMAGENT before loading a LAN driver, the operating system will try to autoload NMAGENT for you.Command Format  LOAD [path]NMAGENTCommand ParametersReplace path with a full directory path to the directory containing the module. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path and volume SYS: is mounted, the operating system assumes that the loadable module is located in the SYS:SYSTEM directory. (Use SEARCH to set up additional paths for automatic searching.)Additional InformationNMAGENT registers three resources for tracking: NetWork Management Triggers, Network Management Managers, and Network Management Objects. You can view these tracked resources with MONITOR.Load NMAGENTTo load NMAGENT, type  LOAD NMAGENT <Enter>NUTWhy Use NUT?Use NUT (NLM Utility User Interface) if you have a NetWare v3.11 loadable module (such as v3.11 MONITOR) that requires NUT's library of routines and functions. Most loadable modules that use NUT will autoload NUT before they load. Use the MODULES console command to see if you already have NUT loaded.Command Format  LOAD [path]NUTCommand ParameterReplace path with the full path to the directory containing the NUT module.NWSNUT idxid="w7518"book="_idx" docset="nw312" tidref="i4786"Why Use NWSNUT?Use NWSNUT (NLM Utility User Interface) if you have a NetWare v4.0 loadable module that requires NWSNUT's library of routines and functions.Most loadable modules that use NWSNUT will autoload NWSNUT before they load. Use the MODULES console command to see if you already have NWSNUT loaded.Command Format  LOAD [path]NWSNUTCommand ParametersReplace path with the full path to the directory containing the NWSNUT module.OFFWhy Use idxid="w7519"book="_idx" docset="nw312" tidref="i2127"OFF?Use OFF to idxid="w7520"book="_idx" docset="nw312" tidref="i2096"clear information from the file server idxid="w7521"book="_idx" docset="nw312" tidref="i4819"console screen.Command Format  OFFidxid="w7522"book="_idx" docset="nw312" tidref="i2034"Clear the File Server Console ScreenTo idxid="w7523"book="_idx" docset="nw312" tidref="i6151"clear the console screen, type  OFF <Enter>You can also use the CLS command to clear the file server console screen.ID="FM23270"PROTOCOLWhy Use idxid="w7524"book="_idx" docset="nw312" tidref="i5601"PROTOCOL?Use PROTOCOL to view the protocols registered on your idxid="w7525"book="_idx" docset="nw312" tidref="i2127"file server. Use PROTOCOL REGISTER to register additional protocols and frame types.LAN drivers automatically register only IPX. Other protocol stacks automatically register themselves. Using PROTOCOL REGISTER is only necessary for unusual cases, such as using a new media.Command Format  PROTOCOLor  PROTOCOL REGISTER protocolframe id#ID="FM69760"Command ParametersReplace protocol with the protocol name. Only IPX is automatically registered with the operating system.Consult your Novell Authorized Reseller for approved protocol loadable modules. Check the documentation that comes with the protocol module for the protocol name.Replace frame with the name representing the frame type that is to be bound to the idxid="w7526"book="_idx" docset="nw312" tidref="i1081"communication protocol. LAN drivers automatically idxid="w7527"book="_idx" docset="nw312" tidref="i5640"register a frame type when they are loaded. If the LAN driver supports more than one frame type, the frame type is registered when you load the driver with that frame type.Replace id# with the Protocol Identification number ( idxid="w7528"book="_idx" docset="nw312" tidref="i5605"PID), a unique, assigned hexadecimal number that tells the file server how to recognize data coming from a certain network board through a designated communication protocol (such as IPX). idxid="w7529"book="_idx" docset="nw312" tidref="i5605"You idxid="w7530"book="_idx" docset="nw312" tidref="i5605"may idxid="w7531"book="_idx" docset="nw312" tidref="i5605"find this number called a protocol ID or (PID), an Ethernet type (or E-type), or an SAP, although it may be called something else entirely.View the idxid="w7532"book="_idx" docset="nw312" tidref="i1081"Kinds of Protocols and idxid="w7533"book="_idx" docset="nw312" tidref="i2520"Frame Types on Your NetworkAt the console prompt, type  PROTOCOL <Enter>Information similar to the following is displayed:  The following protocols are registered  Protocol: IPX Frame type: VIRTUAL_LAN Protocol ID: 0LAN drivers automatically register additional frame types when you load them with a frame type other than the default. For example, when the NE2000 driver is loaded with an Ethernet_II frame type, information similar to the following appears:  The following protocols are registered:  Protocol: IPX Frame type: VIRTUAL_LAN Protocol ID: 0  Protocol: IPX Frame type: Ethernet_802.3 Protocol ID: 0  Protocol: IPX Frame type: Ethernet_II Protocol ID: 8137Add a New idxid="w7534"book="_idx" docset="nw312" tidref="i1081"Protocol idxid="w7535"book="_idx" docset="nw312" tidref="i1081"or Frame to Your NetworkBecause the idxid="w7536"book="_idx" docset="nw312" tidref="i5605"protocol (IPX) and idxid="w7537"book="_idx" docset="nw312" tidref="i2520"frame types listed in IDREF="FM69760""Command Parameters" on page 222 are already registered with NetWare, use the following example as a guide for loading new protocols and frames.To add a new protocol called XYZ to an Ethernet network that is using the NE2000 LAN driver, complete the following steps.ProcedureCheck the protocol documentation for the protocol name, frame name, and protocol ID number.For this example, assume the protocol name is XYZ, the frame name is Ethernet_Snap, and the ID number is 8137.Load the loadable module for the protocol by typing  LOAD XYZ <Enter>Register the new protocol with NetWare by typing  PROTOCOL REGISTER XYZ ETHERNET_SNAP 8137 <Enter>Bind the protocol to a loaded LAN driver by typing  BIND XYZ TO NE2000 <Enter>The LAN driver must support the specified frame type.PSERVERWhy Use idxid="w7538"book="_idx" docset="nw312" tidref="i5404"PSERVER?Use PSERVER to load the print server on the idxid="w7539"book="_idx" docset="nw312" tidref="i2127"file idxid="w7540"book="_idx" docset="nw312" tidref="i2034"idxid="w7541"book="_idx" docset="nw312" tidref="i3300"server and to establish print services for the network.Command Format  LOAD PSERVER printserverBefore you load the print server, you must use PCONSOLE to set up a print server and configuration files. For more information, seebook="print" docset="nw312"Print Server.REGISTER MEMORYWhy Use idxid="w7542"book="_idx" docset="nw312" tidref="i5781"REGISTER idxid="w7543"book="_idx" docset="nw312" tidref="i2127"idxid="w7544"book="_idx" docset="nw312" tidref="i2257"MEMORY?Use idxid="w7545"book="_idx" docset="nw312" tidref="i2252"REGISTER MEMORY if the operating system does not recognize installed idxid="w7546"book="_idx" docset="nw312" tidref="i3758"memory above 16 MB. If you have an idxid="w7547"book="_idx" docset="nw312" tidref="i2248"EISA computer, see IDREF="FM20331""Auto Register Memory above 16 Megabytes = value" on page 281.ID="FM88652"If you have installed more than 16 MB of file server memory, avoid memory address conflicts. A conflict will occur if you have installed more than 16 MB of memory and the idxid="w7548"book="_idx" docset="nw312" tidref="i1240"disk adapter board uses 16- or 24-bit DMA or Bus-Master DMA.If a memory conflict occurs, you can solve it by doing either of the following:Upgrade to full 32-bit bus adapters.Use drivers that have been modified and certified to compensate for these memory-addressing limitations.Command Format  REGISTER MEMORY start lengthCommand ParametersReplace start with the starting hexadecimal address where the memory beyond 16 MB begins. In most instances, the starting address will be 0x1000000 (which equals 16 MB).Replace length with a hexadecimal length of the memory installed beyond 16 MB. This number must be on an even paragraph boundary (a number that is divisible by 10h).Additional InformationIf the additional memory is added successfully, the message "Memory successfully added" appears and the additional memory is visible in MONITOR. Use the MEMORY command to display the total amount of idxid="w7549"book="_idx" docset="nw312" tidref="i6910"memory the file server is idxid="w7550"book="_idx" docset="nw312" tidref="i3758"addressing.If the memory is not added, see the "Important" on IDREF="FM88652"page 226 and check for the following errors:An incorrect hexadecimal value was specified for start or length.The length value exceeds the total installed memory. Use the setup or reference diskette that came with the computer to determine the total amount of installed memory.The following chart lists start and length values for standard computers that begin addressing memory above 16 MB at 0x1000000:WIDTH="96"Total MemoryWIDTH="96"start (hex)WIDTH="96"Length (hex)WIDTH="96"20 MBWIDTH="96"1000000WIDTH="96"40000024 MB100000080000028 MB1000000C0000032 MB1000000100000036 MB1000000140000040 MB10000001800000Register Memory Above 16 MBTo add 4 MB of memory above 16 MB, type  REGISTER MEMORY 1000000 400000 <Enter>To have the memory registered automatically when the file server is booted, add the following line to the AUTOEXEC.NCF file:  REGISTER MEMORY 1000000 400000Add this line just after the lines for the file server name and the IPX internal network number. For instructions on editing the AUTOEXEC.NCF file, IDREF="FM38546"see "Edit the AUTOEXEC.NCF File" on page 82, or "book="utilref" docset="nw312"SYSCON" inUtilities ReferenceID="FM30824"REMIRROR idxid="w7551"book="_idx" docset="nw312" tidref="i5784"PARTITIONWhy Use REMIRROR PARTITION?Use idxid="w7552"book="_idx" docset="nw312" tidref="i2127"REMIRROR PARTITION to start idxid="w7553"book="_idx" docset="nw312" tidref="i5785"remirroring of a idxid="w7554"book="_idx" docset="nw312" tidref="i4978"logical idxid="w7555"book="_idx" docset="nw312" tidref="i1590"partition.Command Format  ID="FM55591"REMIRROR PARTITION numberCommand ParameterReplace number with the number of the logical partition you want to start remirroring for.Start Remirroring a Logical PartitionTo start remirroring a logical partition, type  REMIRROR PARTITION number<Enter>The server remirrors partitions automatically. Use REMIRROR PARTITION only if you have stopped remirroring or if something else has caused your server to cease remirroring.For example, to start remirroring for logical partition 4, you would type  REMIRROR PARTITION 4 <Enter>Additional InformationFor information about stopping a partition remirror, IDREF="FM56807"see "ABORT REMIRROR" on page 2.REMOTEWhy Use idxid="w7556"book="_idx" docset="nw312" tidref="i5813"REMOTE idxid="w7557"book="_idx" docset="nw312" tidref="i2127"?Use idxid="w7558"book="_idx" docset="nw312" tidref="i3300"REMOTE idxid="w7559"book="_idx" docset="nw312" tidref="i5802"to access the file server console from a workstation. After you load REMOTE, you must also load RSPX for REMOTE to function fully.Command Format  LOAD [path]REMOTE [password]Command ParametersReplace path with a full directory path to the directory containing the module. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path and volume SYS: is mounted, the operating system assumes that the loadable module is located in the SYS:SYSTEM directory. (Use SEARCH to set up additional paths for automatic searching.)Replace password with the password that you want all remote administrators of the file server to use.Additional InformationREMOTE requires a password. If you do not enter the password with the command, REMOTE will prompt you for a password.The password can be the same as the SUPERVISOR's password or the console password (that you enter with MONITOR), or the password can be unique. Even if a unique password is entered, the SUPERVISOR's password can still be used with the RCONSOLE utility to access the file server.Load REMOTETo load REMOTE without a password on the command line, type  LOAD REMOTE <Enter>You will then be prompted to enter a password.To load REMOTE with the password SECRET, type  LOAD REMOTE SECRET <Enter>Set Up Autoloading of Remote ConsoleTo make sure that the modules necessary for remote console access are automatically loaded when the file server is booted, add the following commands to the AUTOEXEC.NCF file. For instructions on editing this file, IDREF="FM38546"see "Edit the AUTOEXEC.NCF File" on page 82, or "book="utilref" docset="nw312"SYSCON" in Utilities Reference.  LOAD REMOTE password  LOAD RSPXThe command to load REMOTE must precede the command to load RSPX. Replace password with the password you want to use with RCONSOLE.ID="FM96399"REMOVE DOSWhy Use idxid="w7560"book="_idx" docset="nw312" tidref="i5853"REMOVE DOS?Use idxid="w7561"book="_idx" docset="nw312" tidref="i1638"REMOVE idxid="w7562"book="_idx" docset="nw312" tidref="i2096"DOS idxid="w7563"book="_idx" docset="nw312" tidref="i2034"to Remove DOS from the file server's memory. The memory that was used for idxid="w7564"book="_idx" docset="nw312" tidref="i2127"DOS is returned to the operating system for file idxid="w7565"book="_idx" docset="nw312" tidref="i3758"caching. If available memory in the file server is low, use this command to free additional memory for file caching.Increase file server idxid="w7566"book="_idx" docset="nw312" tidref="i6177"security. With DOS removed, loadable modules cannot be loaded from the file server's DOS drives (floppy disk drives or a DOS partition on the hard disk).Warm boot the file server with the EXIT command.Command Format  REMOVE DOSAdditional InformationOnce this command is issued, DOS is no longer resident in the file server and loadable modules located on DOS drives are no longer accessible. These modules can be loaded only if they are copied to a network drive on the file server.After the file server is downed, the EXIT command will no longer return you to DOS. However, the EXIT command will warm boot the file server. This feature allows users who are using RCONSOLE to reboot the file server remotely.Remove DOS from the File ServerTo remove DOS from the file server, type  REMOVE DOS <Enter>The following message appears:  DOS removed and its memory given to the disk cacheIDREF="FM93496"See also "EXIT" on page 46 and IDREF="FM61834""SECURE CONSOLE" on page 249.ID="FM63130"RESET ROUTERWhy Use idxid="w7567"book="_idx" docset="nw312" tidref="i5905"RESET ROUTER?Use RESET ROUTER to reset an inaccurate or corrupted idxid="w7568"book="_idx" docset="nw312" tidref="i6037"router table in the idxid="w7569"book="_idx" docset="nw312" tidref="i2127"file server. For example, if several file servers or bridges on your network go down, any idxid="w7570"book="_idx" docset="nw312" tidref="i6027"packets sent to or through their routers are lost. If you reset the router in each file server that is up, the router sends a request (an advertising packet) to nearby file servers to verify any other networks the servers know about. The router builds a new, accurate router table from this information.This command cannot be used when the file server is down.In normal situations, the router updates its tables every two minutes to automatically handle situations in which other servers or their routers have gone down. This command speeds up the normal process of updating the router table.Command Format  RESET ROUTERReset idxid="w7571"book="_idx" docset="nw312" tidref="i6027"the Router TableTo reset the router table, type  RESET ROUTER <Enter>ROUTEWhy Use idxid="w7572"book="_idx" docset="nw312" tidref="i6019"ROUTE idxid="w7573"book="_idx" docset="nw312" tidref="i3300"?Use idxid="w7574"book="_idx" docset="nw312" tidref="i2127"ROUTE idxid="w7575"book="_idx" docset="nw312" tidref="i6414"to allow NetWare to pass frames (packets) through idxid="w7576"book="_idx" docset="nw312" tidref="i6414"idxid="w7577"book="_idx" docset="nw312" tidref="i6414"IBM bridges on a idxid="w7578"book="_idx" docset="nw312" tidref="i6821"Token-Ring cabling system. You must load the TOKEN LAN driver before you load idxid="w7579"book="_idx" docset="nw312" tidref="i6414"ROUTE idxid="w7580"book="_idx" docset="nw312" tidref="i6414".All NetWare idxid="w7581"book="_idx" docset="nw312" tidref="i7493"workstations on Token-Ring networks must use the new Token-Ring workstation driver.If you are using ODI shells, see ODI Shell for DOS for instructions on setting up the workstation boot diskettes with the new driver.For instructions on setting up workstations and NetWare 286 file servers and idxid="w7582"book="_idx" docset="nw312" tidref="i762"bridges for idxid="w7583"book="_idx" docset="nw312" tidref="i6414"source routing, see Installation Supplement for IBM Token-Ring Network.The following tasks are described in this section:WIDTH="264"TaskWIDTH="48"PageWIDTH="264"Set up the file server for source routingWIDTH="48"IDREF="FM52096"239Change a source routing parameterIDREF="FM85609"239Command Format  LOAD [path]ROUTE [parameter...]Command ParametersReplace path with a full directory path to the directory containing the module. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path and volume SYS: is mounted, the operating system assumes that the module is located in the SYS:SYSTEM directory. (Use SEARCH to set up additional paths for automatic searching.)Replace parameter with one or more of the following:WIDTH="108"BOARD = numberWIDTH="192"REMOVE = numberCLEARRSP = valueDEFTIME = numberGBRUNLOADMBREach parameter is described below.Parameters idxid="w7584"book="_idx" docset="nw312" tidref="i6414"All the parameters described on the following pages are optional. ROUTE can be loaded re-entrantly (a second time) with a specified parameter to change ROUTE's configuration.Most of the parameters have default values that should work with simple configurations for IBM bridges. If you have installed parallel IBM bridges, you can change some of the parameters to reduce traffic on some of the paths.For more information about source routing and broadcast frames, see the IBM Token-Ring Network Architecture Reference produced by IBM.BOARD = numberUse this parameter if the Token-Ring driver is not the first driver loaded. The operating system numbers the boards, starting with the first driver loaded. That board is board number one. (Check the order in the AUTOEXEC.NCF file if you have more than one driver. IDREF="FM38546"(See "Edit the AUTOEXEC.NCF File" on page 82.) Use this parameter to specify which board you want to change parameters on or load ROUTE for.CLEARUse this parameter to clear the Source Routing idxid="w7585"book="_idx" docset="nw312" tidref="i6414"table. This parameter forces a dynamic rebuilding of the table by sending a default frame to each specific node in the network. Use this parameter when an IBM bridge on the network has gone down and an alternate route is available.DEFUse this parameter to prevent frames that have unknown (DEFault) destination addresses from being sent across Single Route IBM bridges.If this parameter is specified, all frames that have addresses not currently in the file server's Source Routing table are forwarded as All Routes Broadcast frames.If this parameter is not specified, all frames that have addresses not currently in the file server's Source Routing table are forwarded as Single Route Broadcast frames.If ROUTE has already been loaded with the DEF parameter, reloading ROUTE with this parameter broadcasts all subsequent Single Route Broadcast frames as All Routes Broadcast frames.GBRUse this parameter to specify that all General BRoadcast frames are to be sent as All Routes Broadcast frames.If this parameter is not specified when ROUTE is loaded, all General BRoadcast frames are broadcast as Single Route Broadcast frames.If ROUTE has already been loaded with the GBR parameter, reloading ROUTE with this parameter broadcasts all subsequent General BRoadcast frames as All Routes Broadcast frames.MBRUse this parameter to specify that all Multicast BRoadcast frames are to be sent as All Routes Broadcast frames.If the parameter is not specified when ROUTE is loaded, all Multicast BRoadcast frames are broadcast as Single Route Broadcast frames.If ROUTE has already been loaded with the MBR parameter, reloading ROUTE with this parameter broadcasts all subsequent Multicast BRoadcast frames as All Routes Broadcast frames.REMOVE = numberUse this parameter to remove a specified node address from the file server's Source Routing table. Use the parameter when a bridge has gone down. When you remove the node from the Source Routing table, you force the file server to determine an alternate route.Replace number with a 12-digit (06-byte) hexadecimal number. If less than 9 digits are entered, ROUTE prefixes the address with 4000h. For example, REMOVE=2 is interpreted as REMOVE=400000000002RSP = valueUse this parameter to specify how the file server should ReSPond to a broadcast request.Replace value with one of the following:WIDTH="48"NRWIDTH="252"Specifies that all Broadcast Requests are to be  responded to directly. A Broadcast Response is Not  Required (this is the default value).ARSpecifies that all Broadcast Requests are to be  responded to with an All Routes Broadcast frame.SRSpecifies that all Broadcast Requests are to be  responded to with a Single Route Broadcast frame.TIME = numberUse this parameter to specify how often the Source Routing table should be updated. This parameter forces the table to be updated with a new route if the current route has not been used during the specified time period. This parameter enables ROUTE to determine alternate routes dynamically when an IBM bridge goes down.Replace number with a value from 03 to 255 seconds. The default is 03 seconds.UNLOADUse this parameter after the board parameter to specify the board from which you want to remove source routing. To unload ROUTE.NLM from the file server, use UNLOAD ROUTE.ID="FM21343"Additional InformationAs frames pass through an IBM bridge, source routing information is added to the frame header at the Media Access Control (MAC) layer. NetWare's bridging is done above this layer. ROUTE.NLM enables NetWare to do the following:Keep track of the source routing information in the frames.Configure the source routing information in the frames according to the parameters with which ROUTE is loaded.ROUTE can be loaded re-entrantly.If you have two Token-Ring boards in the file server, ROUTE should be loaded twice. The second time it is loaded, you must use the BOARD parameter to specify a board number.If you need to change the configuration, load ROUTE with the parameter that needs to be changed.ID="FM52096"Set Up the File Server for Source RoutingProcedureLoad the TOKEN.NLM LAN driver.IDREF="FM79039"See "LOAD LAN driver" on page 122.Load ROUTE by typing  LOAD ROUTE <Enter>To set up the workstations and NetWare v2.x file servers and bridges for source routing, see Installation Supplement for IBM Token-Ring Network.ID="FM85609"Change a Source Routing ParameterTo change a parameter in ROUTE after ROUTE has been loaded, follow the procedure in the following section that fits your situation.One Token-Ring Network BoardTo clear the Source Routing table when only one driver has been loaded, type  LOAD ROUTE CLEAR <Enter>Two Token-Ring Network BoardsTo change a parameter when more than one driver has been loaded, complete the following steps. Procedure(This procedure shows how to change the update time for the Source Routing table from the default of 3 seconds to 10 seconds.)To change the TIME parameter for the first driver, type  LOAD ROUTE BOARD=01 TIME=10 <Enter>To change the TIME parameter for the second driver, type  LOAD ROUTE BOARD=02 TIME=10 <Enter>ID="FM29350"idxid="w7586"book="_idx" docset="nw312" tidref="i6066"RPLWhy Use RPL?Use idxid="w7587"book="_idx" docset="nw312" tidref="i3300"RPL to enable remote idxid="w7588"book="_idx" docset="nw312" tidref="i743"booting of IBM PC idxid="w7589"book="_idx" docset="nw312" tidref="i1605"diskless idxid="w7590"book="_idx" docset="nw312" tidref="i7493"workstations that have network boards installed.Command Format  LOAD [path]RPL Command ParametersReplace path with the full path to the directory containing the RPL module. Load idxid="w7591"book="_idx" docset="nw312" tidref="i5640"RPLTo load RPL, type  LOAD RPL <Enter>ID="FM69184"Additional InformationWIDTH="204"For information aboutWIDTH="204"Refer toWIDTH="204"Remote booting a DOS workstationWIDTH="204""book="ws_dos" docset="nw312"4. Create a Single or Multiple Remote Boot  Disk Image File(s)" in NetWare Workstation for  DOS and WindowsRemote booting an OS/2 workstation"book="ws_os2" docset="nw312"11. Remote-Booting OS/2 Workstations" in NetWare Workstation for OS/2  RS232Why Use idxid="w7592"book="_idx" docset="nw312" tidref="i6084"RS232 idxid="w7593"book="_idx" docset="nw312" tidref="i5802"?Use idxid="w7594"book="_idx" docset="nw312" tidref="i3300"RS232 idxid="w7595"book="_idx" docset="nw312" tidref="i2127"to set up a communications port for remote management. idxid="w7596"book="_idx" docset="nw312" tidref="i6084"RS232 is an asynchronous communications driver that initiates the file server's communication port and transfers screen and keystroke information to and from REMOTE.NLM.Command Format  LOAD [path]RS232 [comm port] [modemspeed]Command ParametersIf the module is in the SYS:SYSTEM directory, you do not need to specify a path. If the module is in a different directory, replace path with the full directory path to the directory containing RS232.NLM. Begin with a DOS drive letter or a NetWare volume name.Replace comm port with the idxid="w7597"book="_idx" docset="nw312" tidref="i1064"communications port number (1 or 2). If you do not enter this number when entering the LOAD command, you will be prompted to enter it.Replace modem speed with the baud rate of your modem (2400, 4800, or 9600). If you do not enter the modem speed when entering the LOAD command, you will be prompted to select a baud rate.RSPXWhy Use idxid="w7598"book="_idx" docset="nw312" tidref="i6089"RSPX idxid="w7599"book="_idx" docset="nw312" tidref="i5802"?Use idxid="w7600"book="_idx" docset="nw312" tidref="i3300"RSPX idxid="w7601"book="_idx" docset="nw312" tidref="i2127"to allow the RCONSOLE utility to access a file server. RSPX loads the SPX driver for REMOTE and advertises the server to workstations (therefore, you should load REMOTE before you load RSPX). Command Format  LOAD [path]RSPXCommand ParametersReplace path with a full directory path to the module. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path and volume SYS: is mounted, the operating system looks for RSPX in the SYS:SYSTEM directory. (Use SEARCH to set up additional paths for automatic searching.)Additional InformationYou need two NLMs (RSPX and REMOTE) and a menu utility (RCONSOLE) to set up Remote Console. Load REMOTE; then load RSPX. Then you can use the file server console with RCONSOLE from a workstation using the IPX/SPX protocol.RCONSOLE is in the SYS:SYSTEM directory; to use it, you must be logged in as SUPERVISOR or have Read and File Scan rights in the SYS:SYSTEM directory.Load idxid="w7602"book="_idx" docset="nw312" tidref="i5640"RSPXTo load RSPX, type  LOAD RSPX <Enter>ID="FM74549"idxid="w7603"book="_idx" docset="nw312" tidref="i6141"SBACKUPWhy Use SBACKUP?Use idxid="w7604"book="_idx" docset="nw312" tidref="i3300"SBACKUP to back up and idxid="w7605"book="_idx" docset="nw312" tidref="i5922"restore idxid="w7606"book="_idx" docset="nw312" tidref="i1314"data that you specify on a idxid="w7607"book="_idx" docset="nw312" tidref="i4395"NetWare idxid="w7608"book="_idx" docset="nw312" tidref="i4395"server, idxid="w7609"book="_idx" docset="nw312" tidref="i7493"workstation, or service that you select.Command Format  LOAD [path]SBACKUP SIZE=xx BUFFER=xCommand ParametersReplace path with the full path to the directory containing SBACKUP.For the SIZE and BUFFER parameters, use values from the following table. LBL="1-15" INLINE="F"SBACKUP parameter valuesWIDTH="96"ParameterWIDTH="60"SyntaxWIDTH="144"ValuesWIDTH="96"Buffer SizeWIDTH="60"SIZE = xxWIDTH="144"16, 32, 64, 128, or 256 Default: 64 KBNumber of BuffersBUFFER = x2 to 10 Default: 4ID="FM43969"Additional InformationFor information about using SBACKUP, refer to "book="backup" docset="nw312"Rules for Using SBACKUP" in Chapter 2 of Server BackupID="FM80203"SCAN idxid="w7610"book="_idx" docset="nw312" tidref="i6149"FOR NEW DEVICESWhy Use SCAN FOR NEW DEVICES?Use idxid="w7611"book="_idx" docset="nw312" tidref="i2127"SCAN FOR NEW DEVICES to check for idxid="w7612"book="_idx" docset="nw312" tidref="i1402"disk idxid="w7613"book="_idx" docset="nw312" tidref="i2640"hardware that has been added since the idxid="w7614"book="_idx" docset="nw312" tidref="i4371"NetWare server was last booted.Command Format  SCAN FOR NEW DEVICESCheck for New Hardware DevicesTo check for new hardware devices that have been added since the NetWare server was last booted, type  SCAN FOR NEW DEVICES<Enter>ID="FM12543"SEARCHWhy Use idxid="w7615"book="_idx" docset="nw312" tidref="i6156"SEARCH?Use SEARCH to tell the file server where to look for loadable module files and .NCF files. The default idxid="w7616"book="_idx" docset="nw312" tidref="i6168"search idxid="w7617"book="_idx" docset="nw312" tidref="i2127"path is SYS:SYSTEM.You can use SEARCH to add other search paths or to delete current search paths. You can also use SEARCH to view the current search paths for the operating system.The following tasks are explained in this section:WIDTH="264"TaskWIDTH="48"PageWIDTH="264"Display the current search pathsWIDTH="48"IDREF="FM45060"247Add a search pathIDREF="FM24577"247Delete a search pathIDREF="FM64798"248Command Format  SEARCH [ADD [number] path]or  SEARCH DEL numberCommand ParametersReplace number with the number of the search drive you want to add or the number of the search drive you want to remove.Replace path with the complete path of the directory you want searched. Begin with a DOS drive letter or a NetWare volume name.ID="FM63045"Additional InformationIf you execute SECURE CONSOLE, SEARCH is disabled. The SYS:SYSTEM search path remains in effect, but you cannot create any new search paths.Once you execute SECURE CONSOLE, you must down the file server and reboot it in order to create additional search paths.ID="FM45060"Display the idxid="w7618"book="_idx" docset="nw312" tidref="i6168"Current Search PathsTo display the current search paths on the file server, type  SEARCH <Enter>Information similar to the following appears:LBL="1-40"Current search path informationFILE="n312sa75.pbm"ID="FM24577"Add a idxid="w7619"book="_idx" docset="nw312" tidref="i3278"Search idxid="w7620"book="_idx" docset="nw312" tidref="i6168"PathIf you have copied loadable modules to directories other than SYS:SYSTEM and want to load a module without specifying the path, you can add a search path. During a command to load a module, the operating system searches the path you specified for loadable modules. The following examples explain how to add a search path to the file server's local drive or to a network directory, and how to specify a search number.To a Local DriveTo add drive A: as a search path in the list, type  SEARCH ADD A: <Enter>To a Network DirectoryTo add a network directory on the file server, you must enter the path, starting with the volume name. For example, to add the SYS:MODULES directory as a search path, you would type  SEARCH ADD SYS:MODULES <Enter>To a Specific NumberWhen you add a search path to the operating system, the default is to make the path last on the list. If you want to have one path searched before another, you must specify a number. To make a directory the first directory searched, use 1; second, 2; etc. For example, to have drive C: searched first, type  SEARCH ADD 1 C: <Enter>ID="FM64798"Delete a idxid="w7621"book="_idx" docset="nw312" tidref="i6168"Search PathProcedureDisplay a list of current search paths by typing  SEARCH <Enter>From the list displayed, choose the number of the drive you want to delete and then type in the DELETE command. For example, to delete search drive 2, you would type  SEARCH DEL 2 <Enter>ID="FM61834"SECURE CONSOLEWhy Use idxid="w7622"book="_idx" docset="nw312" tidref="i6176"SECURE idxid="w7623"book="_idx" docset="nw312" tidref="i2127"CONSOLE?Use SECURE CONSOLE to implement the following idxid="w7624"book="_idx" docset="nw312" tidref="i6177"security measures:Prevent loadable modules from being loaded from any directory other than SYS:SYSTEM.Prevent keyboard entry into the OS debugger.Prevent anyone other than a console operator from changing the date and time.Remove idxid="w7625"book="_idx" docset="nw312" tidref="i1638"DOS from the file server.Command Format  SECURE CONSOLEAdditional InformationThe SECURE CONSOLE command prevents the following types of breaches in security. For additional security tips, see "book="Concepts" docset="nw312"Console" in Concepts.Unauthorized NLMsAn intruder could load an NLM that accesses or alters any information on the file server. In addition, these loadable modules can change user account information at the BINDERY security level. Because of this danger, we recommend using SECURE CONSOLE, especially in security-sensitive environments.When SECURE CONSOLE has not been used, a module can be loaded from a DOS partition, a diskette drive, or any directory on a NetWare volume. If you allow modules to be loaded from all these drives, anyone who has access to the file server console can load a loadable module.Date and Time ConsiderationsSome security and accounting features depend on date and time for their enforcement. These features include password expiration, time restrictions (when a user can log in to the server), intruder detection, and lockout intervals. An intruder can change the date and time at the file server and bypass these time-dependent features. SECURE CONSOLE prevents this. Although FCONSOLE can still be used to change the date and time, the user must have console operator or supervisor rights.DOS idxid="w7626"book="_idx" docset="nw312" tidref="i1638"ConsiderationsIf DOS remains enabled on the file server console, an intruder can down the file server and execute a DOS file developed expressly to steal or alter data. With DOS removed from the file server, the intruder must turn the file server off and then on again to access DOS. If you have armed your file server with a power-on password, the intruder cannot access DOS. (See the documentation that comes with the computer for information on setting a power-on password. Not all computers have this feature.)Secure the idxid="w7627"book="_idx" docset="nw312" tidref="i2092"File idxid="w7628"book="_idx" docset="nw312" tidref="i2096"Server from Unauthorized System ProgramsTo secure the file server, type  SECURE CONSOLE <Enter>SENDWhy Use idxid="w7629"book="_idx" docset="nw312" tidref="i2096"SEND idxid="w7630"book="_idx" docset="nw312" tidref="i6225"?Use SEND to send a message to all users logged in or attached to the idxid="w7631"book="_idx" docset="nw312" tidref="i2034"file idxid="w7632"book="_idx" docset="nw312" tidref="i2127"server or to a list of users or connection numbers.Command Format  SEND "message" [[TO] username|connection number] [[and|,] username|connection number]Command ParametersReplace message with the information (up to 55 characters) you want to send.If no user or connection number is specified, the message is sent to all attached users.Replace username with the user or users you want to send the message to. Separate multiple users with a space, a comma, or an and.Replace connectionnumber with the number of the workstation you want to send the message to. Separate multiple connection numbers with a space, a comma or an and. To determine the connection number, see IDREF="FM22079""Connection Information" on page 180.Additional InformationWho Receives MessagesAll logged-in users except the following receive the messages:Users who have used the CASTOFF ALL utility.Users who are logged in using ACS or NACS.Users who are logged in on remote workstations.Users who are using some graphics applications. These users may hear the beep and should press <Ctrl><Enter> to proceed (even though no message appears telling them to do so). To prevent the beep, run CASTOFF in a batch file before running the graphics applications.Where Messages AppearAll attached users receive SEND messages on the 25th line of the screen. Messages do not interfere with the workstation's screen display; however, you cannot make any entries on the screen until you clear the message.How to Delete MessagesTo idxid="w7633"book="_idx" docset="nw312" tidref="i3839"delete the idxid="w7634"book="_idx" docset="nw312" tidref="i3839"message from a workstation screen and resume work, press <Ctrl><Enter>.How to Stop Message DisplaysUse idxid="w7635"book="_idx" docset="nw312" tidref="i3839"CASTOFF with the ALL option to prevent messages from being received and displayed. (See "book="utilref" docset="nw312"CASTOFF" in Utilities.)Send a idxid="w7636"book="_idx" docset="nw312" tidref="i3839"Console MessageSend a Message to All UsersTo send a message to all users logged in or attached to the file server, type  SEND "message" <Enter>Send a Message to a Specific UserTo send a message to a user named Jack, type  SEND "message" Jack <Enter>Send a Message to a Specific WorkstationTo send a message to workstation 1, type  SEND "message" 1 <Enter>Send a Message to Users and WorkstationsTo send a message to a combination of users and workstations, you could type   SEND "message" to Fred, Jack, 1, 4, Mary <Enter>ID="FM49124"SERVERWhy Use idxid="w7637"book="_idx" docset="nw312" tidref="i6489"idxid="w7638"book="_idx" docset="nw312" tidref="i2211"idxid="w7639"book="_idx" docset="nw312" tidref="i1638"SERVER?Use SERVER (SERVER.EXE) to boot idxid="w7640"book="_idx" docset="nw312" tidref="i4455"NetWare on your idxid="w7641"book="_idx" docset="nw312" tidref="i743"file server. idxid="w7642"book="_idx" docset="nw312" tidref="i1925"SERVER idxid="w7643"book="_idx" docset="nw312" tidref="i2127"is a DOS-executable file that boots the NetWare idxid="w7644"book="_idx" docset="nw312" tidref="i4832"operating system. As part of the boot process, SERVER performs the following tasks. (For complete information, see Chapter 3, "book="install" docset="nw312"File Server Installation," in Installation and Upgrade.)Executes the STARTUP.NCF idxid="w7645"book="_idx" docset="nw312" tidref="i1561"file.Mounts volume SYS:.Executes the idxid="w7646"book="_idx" docset="nw312" tidref="i3123"AUTOEXEC.NCF idxid="w7647"book="_idx" docset="nw312" tidref="i595"file.If neither of the .NCF files exists, SERVER prompts you for a file server name and an IPX internal network number; SERVER then brings up the console prompt (:).Command Format  SERVER [parameter]Command idxid="w7648"book="_idx" docset="nw312" tidref="i4916"ParametersReplace parameter with one of the following:-S [path]filenameInclude this parameter when you want to use an alternate to the idxid="w7649"book="_idx" docset="nw312" tidref="i6489"STARTUP.NCF file. You can include a idxid="w7650"book="_idx" docset="nw312" tidref="i1064"drive letter and/or the directory path with the filename. If you do not specify a drive or directory path, the operating system will look for the file in the current boot directory.-NAInclude this parameter when you do not want to execute the AUTOEXEC.NCF file that you created in INSTALL. This parameter is useful if you are changing drivers or other commands in your AUTOEXEC.NCF file.-NSInclude this parameter when you do not want to execute the STARTUP.NCF and AUTOEXEC.NCF files created in INSTALL. This parameter is useful if you want to change the boot process.-C cache_buffer_numberInclude this parameter if you want to change the block size of the cache buffer. Valid block sizes are 4 KB, 8 KB, or 16 KB.Default: 4 KBDo not use a cache buffer size larger than the block allocation size (for example, do not specify an 8 KB cache buffer with a 4 KB block allocation). The server will not mount any volume whose block allocation size is smaller than the cache buffer size.If you are using block allocation sizes larger than 4 KB, you can improve performance in some situations by increasing the cache buffer size.Boot idxid="w7651"book="_idx" docset="nw312" tidref="i743"the File idxid="w7652"book="_idx" docset="nw312" tidref="i743"ServerAt the DOS prompt, type  SERVER <Enter>SERVER executes the idxid="w7653"book="_idx" docset="nw312" tidref="i2211"STARTUP.NCF and AUTOEXEC.NCF files, if they exist. If you have not created the .NCF idxid="w7654"book="_idx" docset="nw312" tidref="i743"files, you have to load all necessary disk and LAN drivers. IDREF="FM38546"See "Edit the AUTOEXEC.NCF File" on page 82.Boot with an idxid="w7655"book="_idx" docset="nw312" tidref="i743"Alternate STARTUP FileYou can use an alternate STARTUP file to boot the file server. For example, if you have a file server with both an internal hard disk and a disk subsystem, you may want to boot the file server to function only from the internal disk (perhaps to do maintenance on the disk subsystem). The contents of the alternate STARTUP file would be similar to the following:  load ISADISK port=1F0 int=ETo boot the file server using a file called ALTDISK.NCF, type  SERVER -S ALTDISK.NCF <Enter>Boot without a idxid="w7656"book="_idx" docset="nw312" tidref="i743"STARTUP.NCF FileYou can boot the file server without a STARTUP.NCF file. For example, if you are doing maintenance or troubleshooting on the hard disks in the file server and you add a new disk subsystem, you might want to test the subsystem before you load the drivers for the internal disks.To boot the file server without a STARTUP.NCF file, type  SERVER -NS <Enter>Boot idxid="w7657"book="_idx" docset="nw312" tidref="i743"without an AUTOEXEC.NCF FileYou can boot the file server without executing an AUTOEXEC.NCF file. For example, when you are doing maintenance or troubleshooting on the volumes or the LAN drivers, you might want to manually load the LAN drivers or mount the volumes.If you add a new cabling system to your file server, you might want to test communication just on the new cabling. If you execute SERVER without the AUTOEXEC.NCF file, you can load only the LAN drivers and loadable modules needed for the test.To boot the file server without executing an AUTOEXEC.NCF file, type  SERVER -NA <Enter>Boot with a idxid="w7658"book="_idx" docset="nw312" tidref="i743"Different idxid="w7659"book="_idx" docset="nw312" tidref="i879"Cache Buffer SizeIf you have a file server that contains mainly large files (8 KB or larger), you might increase access speed to the files by specifying a larger cache buffer size. The larger cache size allows a larger portion of the file to be read into memory with only one request.Do not use a cache buffer size larger than the smallest block allocation size (for example, do not use an 8 KB cache buffer with a 4 KB block allocation). The server will not mount any volume whose block allocation size is smaller than the cache buffer size.To boot the file server with an 8KB block cache buffer, type  SERVER -C8KB <Enter>Add the following line to the STARTUP.NCF file so that the file server automatically boots with the larger cache buffer size:  SET CACHE idxid="w7660"book="_idx" docset="nw312" tidref="i879"BUFFER SIZE = 8192ID="FM73882"SETWhy Use idxid="w7661"book="_idx" docset="nw312" tidref="i4916"SET idxid="w7662"book="_idx" docset="nw312" tidref="i6292"?Use idxid="w7663"book="_idx" docset="nw312" tidref="i2127"SET to view the current operating system parameters and to configure the idxid="w7664"book="_idx" docset="nw312" tidref="i892"operating idxid="w7665"book="_idx" docset="nw312" tidref="i892"idxid="w7666"book="_idx" docset="nw312" tidref="i1493"idxid="w7667"book="_idx" docset="nw312" tidref="i1493"system to fit your situation. Most of the parameters do not need to be changed. They have been set to give maximum performance to most users. However, by changing some of the parameters, you may be able to increase the performance of your operating system.The following tasks are explained on the indicated pages:WIDTH="264"TaskWIDTH="48"PageWIDTH="264"View current operating system configurationsWIDTH="48"IDREF="FM10129"271Change an operating system parameter at the console  promptIDREF="FM50253"272Change an operating system parameter in the STARTUP.NCF  fileIDREF="FM93047"272Understand the operating system parametersIDREF="FM16553"273Command Format  SET [parameter]The available parameters (listed on pages IDREF="FM21173"264 through IDREF="FM10129"271) are divided into nine categories.The categories, along with their parameters, are explained on the following pages.WIDTH="264"CategoryWIDTH="48"PageWIDTH="264"CommunicationsWIDTH="48"IDREF="FM61196"273MemoryIDREF="FM79028"280File cachingIDREF="FM26817"282Directory cachingIDREF="FM67437"285File systemIDREF="FM89876"289LocksIDREF="FM48344"295Transaction trackingIDREF="FM80156"297DiskIDREF="FM13537"300MiscellaneousIDREF="FM10635"301Additional InformationSET can be used to display or change current settings, control idxid="w7668"book="_idx" docset="nw312" tidref="i3758"memory allocations, and configure other types of operating system functions. The following sections give a brief overview of SET.Displaying and Changing Current SettingsSET can be used both to display and change current settings.If you use SET without a parameter, a list of categories appears. When you select a category, the current settings for the parameters in that category are displayed.If you use SET with a parameter, the current setting for the parameter is displayed.If you use SET with a parameter and give the parameter a value, the operating system reconfigures itself according to the specified value.Configuring Memory AllocationsSET controls how much memory can be allocated for the following items and how fast the additional memory can be allocated:File cachingDirectory cachingPacket receive buffersServer processesConfiguring other Types of Operating System FunctionsSET also configures the following functions:Number of open and locked filesCache buffer sizePhysical receive packet sizeWarning parameters for full volumesEncrypted passwordsPurging times for deleted filesLength of time between disk writesidxid="w7669"book="_idx" docset="nw312" tidref="i4835"Entering ParametersMost idxid="w7670"book="_idx" docset="nw312" tidref="i2096"SET parameters can be executed from the console prompt and saved permanently in the AUTOEXEC.NCF file. However, some parameters can only be changed in the STARTUP.NCF file; a few others can be changed in the STARTUP.NCF file, at the console, or in the AUTOEXEC.NCF file.At the Console PromptMost of the parameters can be set at the console prompt. If you try to enter a STARTUP.NCF file parameter at the console prompt, you are prompted to enter it into the STARTUP.NCF file.When a parameter is set at the console, the operating system is immediately configured to that setting. Any setting in the AUTOEXEC.NCF file is automatically overridden until the file server is rebooted.In the idxid="w7671"book="_idx" docset="nw312" tidref="i595"AUTOEXEC.NCF FileAny parameter set at the console prompt can be saved in the AUTOEXEC.NCF file.When a parameter is saved in this file, the file server automatically configures itself to the parameter when the server is rebooted.When the parameter is not saved in the file, the operating system returns to the default setting for the parameter when the file server is booted.Edit the AUTOEXEC.NCF file with INSTALL.In the ID="FM94808"STARTUP.NCF idxid="w7672"book="_idx" docset="nw312" tidref="i6489"FileThe following parameters must be set in the STARTUP.NCF file. They cannot be set at the console prompt or saved in the AUTOEXEC.NCF file.Auto Register Memory Above 16 MegabytesAuto TTS Backout FlagCache Buffer SizeMaximum Physical Receive Packet SizeMaximum Subdirectory Tree DepthMinimum Packet Receive BuffersReserved Buffers Below 16 MegConcurrent Remirror RequestsThe STARTUP.NCF file can be edited from within the INSTALL utility.ID="FM31072"Console, AUTOEXEC.NCF File, or STARTUP.NCF FileThe following parameters can be set in any one of either the STARTUP.NCF file, the AUTOEXEC.NCF file, or at the console.Display Spurious Interrupt AlertsDisplay Lost Interrupt AlertsDisplay Disk Device AlertsDisplay Relinquish Control AlertsDisplay Old API NamesMaximum Packet Receive BuffersReply to Get Nearest ServerNCP Packet Signature OptionMaximum Alloc Short Term MemoryEnable Disk Read After Write VerifyDisplay Incomplete IPX Packet AlertsReplace Console Prompt with Server NameAllow Change to Client RightsThese parameters control the display of alert messages about hardware, loadable modules, and hard disks. The parameters can be entered as the first commands in the STARTUP.NCF file so that the alerts appear for all modules that you load and all hardware devices that you add.Using Parameters That Control the Allocation of ServicesSome SET parameters control how the operating system dynamically allocates services. Three types of parameters interact to control the actual allocation of a resource:Maximum limits control how many resources the operating system can allocate for a particular service.Minimum limits allow the operating system to allocate a minimum number of resources as soon as a request is received. Low minimum limits slow the growth of a particular service. High minimum limits allow rapid growth.For example, if the minimum number of directory cache buffers is set to 20, the operating system immediately allocates another buffer resource as soon as a request is made until 20 cache buffers have been allocated. When 20 directory cache buffers have been allocated, the operating system waits 2.2 seconds (default) when a request comes in, and then allocates another buffer if the request is still active. However, if the minimum number of directory cache buffers is set to 40, the operating system allocates 40 directory cache buffers before it starts slowing the growth by waiting 2.2 seconds after each request.Wait time limits control how rapidly the operating system can allocate a new resource.ID="FM70995"Parameters idxid="w7673"book="_idx" docset="nw312" tidref="i4916"The SET categories and their associated idxid="w7674"book="_idx" docset="nw312" tidref="i4835"parameters are listed in the following tables. The parameter name and default value are listed in the left column and the parameter limits are shown in the right column.ID="FM21173"idxid="w7675"book="_idx" docset="nw312" tidref="i1077"Communications ParametersThe following table lists the default value and limits for each of the Communications parameters. For an explanation of these SET parameters, see Communications on page IDREF="FM61196"273.LBL="1-16" INLINE="F"Communications parametersWIDTH="180"ParameterWIDTH="120"LimitsWIDTH="180"Console Display idxid="w7676"book="_idx" docset="nw312" tidref="i7433"Watchdog Logouts =  OFFWIDTH="120"ON, OFFNew idxid="w7677"book="_idx" docset="nw312" tidref="i4878"Packet idxid="w7678"book="_idx" docset="nw312" tidref="i4903"Receive Buffer Wait Time =  0.1 seconds0.1 to 20 secondsMaximum Physical Receive Packet Size =  1514618 to 4202Maximum Packet Receive Buffers = 40050 to 2000Minimum Packet Receive Buffers = 1010 to 1000Number of Watchdog Packets = 1005 to 100Delay Between Watchdog Packets = 59.3  seconds9.9 seconds to 10 minutes  26.2 secondsDelay Before First Watchdog Packet = 4  minutes 56.6 seconds15.7 seconds to 20 minutes  52.3 secondsNCP Packet Signature Option = 10 to 3Enable Packet Burst Statistics Screen =  OFFON, OFFReply to Get Nearest Server = ONON, OFFEnable IPX Checksum = ONON, OFFAllow LIP = ONON, OFFID="FM50736"idxid="w7679"book="_idx" docset="nw312" tidref="i3758"Memory ParametersThe following table lists the default value and limits for each of the Memory parameters. For an explanation of these SET parameters, see Memory on page IDREF="FM79028"280.LBL="1-17" INLINE="F"Memory parametersWIDTH="180"ParameterWIDTH="120"LimitsWIDTH="180"Cache Buffer Size = 4096 bytesWIDTH="120"4096, 8192, or 16384  bytesMaximum Alloc Short Term Memory =  838860850000 to 33554432Auto Register Memory Above 16  Megabytes = ONON, OFFID="FM24508"idxid="w7680"book="_idx" docset="nw312" tidref="i2009"File idxid="w7681"book="_idx" docset="nw312" tidref="i3758"Caching idxid="w7682"book="_idx" docset="nw312" tidref="i3758"Parameters idxid="w7683"book="_idx" docset="nw312" tidref="i2012"The following table lists the default value and limits for each of the File Caching parameters. For an explanation of these SET parameters, see File Caching on page IDREF="FM26817"282.LBL="1-18" INLINE="F"File Caching parametersWIDTH="180"ParameterWIDTH="120"LimitsWIDTH="180"Maximum Concurrent Disk Cache  Writes  = 50WIDTH="120"10 to 1000Dirty Disk Cache Delay Time = 3.3  seconds0.1 to 10 secondsMinimum File Cache Report Threshold =  200 to 1000Minimum File Cache Buffers = 2020 to 1000Read Ahead Enabled = ONON, OFFRead Ahead LRU Sitting Time Threshold  = 10 seconds0 seconds to 1 hourReserved Buffers Below 16 Meg = 168 to 300idxid="w7684"book="_idx" docset="nw312" tidref="i1484"Directory Caching idxid="w7685"book="_idx" docset="nw312" tidref="i1493"ParametersThe following table lists the default value and limits for each of the Directory Caching parameters. For an explanation of these SET parameters, see Directory Caching on page IDREF="FM67437"285.LBL="1-19" INLINE="F"Directory Caching parametersWIDTH="180"ParameterWIDTH="120"LimitsWIDTH="180"Dirty Directory Cache Delay Time = 0.5  secondsWIDTH="120"0 to 10 secondsMaximum Concurrent Directory Cache  Writes = 105 to 50Directory Cache Allocation Wait Time =  2.2 seconds0.5 seconds to 2 minutesDirectory Cache Buffer NonReferenced  Delay = 5.5 seconds1 second to 5 minutesMaximum Directory Cache Buffers = 50020 to 4000Minimum Directory Cache Buffers = 2010 to 2000ID="FM78209"idxid="w7686"book="_idx" docset="nw312" tidref="i2278"File System ParametersThe following table lists the default value and limits for each of the File System parameters. For an explanation of these SET parameters, see File System on page IDREF="FM89876"289.LBL="1-20" INLINE="F"File System parametersWIDTH="180"ParameterWIDTH="120"LimitsWIDTH="180"Maximum Extended Attributes per File  or Path = 8WIDTH="120"4 to 512Immediate Purge Of Deleted Files = OFFON, OFFidxid="w7687"book="_idx" docset="nw312" tidref="i6563"Maximum Subdirectory Tree Depth = 25 10 to 100idxid="w7688"book="_idx" docset="nw312" tidref="i7372"Volume Low Warn All Users = ONON, OFFVolume Low Warning Reset Threshold =  2560 to 100000Volume Low Warning Threshold = 2560 to 1000000Turbo FAT Re-Use Wait Time = 5 minutes  29.6 seconds0.3 seconds to 1 hour 5  minutes 54.6 secondsMinimum File Delete Wait Time = 1  minute 5.9 seconds0 seconds to 7 daysFile Delete Wait Time = 5 minutes 29.6  seconds0 seconds to 7 daysNCP File Commit = ONON, OFFMaximum Percent of Volume Used By  Directory = 135 to 50Maximum Percent of Volume Space  allowed for Extended Attributes = 105 to 50idxid="w7689"book="_idx" docset="nw312" tidref="i3378"Lock ParametersThe following table lists the default value and limits for each of the Lock parameters. For an explanation of these SET parameters, see Lock on page IDREF="FM48344"295.LBL="1-21" INLINE="F"Lock parametersWIDTH="180"ParameterWIDTH="120"LimitsWIDTH="180"Maximum Record Locks Per  Connection = 500WIDTH="120"10 to 10000Maximum File Locks Per Connection =  25010 to 1000Maximum Record Locks = 20000100 to 200000Maximum File Locks = 10000100 to 100000Transaction Tracking ParametersThe following table lists the default value and limits for each of the Transaction Tracking parameters. For an explanation of these SET parameters, see Transaction Tracking on page IDREF="FM80156"297.LBL="1-22" INLINE="F"Transaction Tracking parametersWIDTH="180"ParameterWIDTH="120"LimitsWIDTH="180"Auto TTS Backout Flag = OFFWIDTH="120"ON, OFFTTS Abort Dump Flag = OFFON, OFFMaximum Transactions = 10000100 to 10000TTS Unwritten Cache Wait Time = 1  minute 5.9 seconds11 seconds to 10 minutes  59.1 secondsTTS Backout File Truncation Wait Time =  59 minutes 19.2 seconds1 minute 5.9 seconds to 1  day 2 hours 21 minutes  51.3 secondsID="FM21314"Disk ParametersThe following table lists the default value and limits for each of the Disk parameters. For an explanation of these SET parameters, see Disk on page IDREF="FM13537"300.LBL="1-23" INLINE="F"Disk parametersWIDTH="180"ParameterWIDTH="120"LimitsWIDTH="180"Enable disk read after write verify = ONWIDTH="120"ON, OFFConcurrent Remirror Requests = 22 to 30ID="FM41641"Miscellaneous ParametersThe following table lists the default value and limits for each of the Miscellaneous parameters. For an explanation of these SET parameters, see Miscellaneous on page IDREF="FM10635"301.LBL="1-24" INLINE="F"ID="FM41641"Miscellaneous parametersWIDTH="180"ParameterWIDTH="120"LimitsWIDTH="180"Maximum Outstanding NCP Searches =  51WIDTH="120"10 to 1000Allow Unencrypted idxid="w7690"book="_idx" docset="nw312" tidref="i4980"Passwords = OFFON, OFFNew Service Process Wait Time = 2.2  seconds0.3 to 20 secondsPseudo Preemption Time = 20001000 to 10000Display Spurious Interrupt Alerts = ONON, OFFDisplay Lost Interrupt Alerts = ONtag="Superscript"ON, OFFDisplay Disk Device Alerts = OFFON, OFFDisplay Relinquish Control Alerts = OFFON, OFFDisplay Old API Names = OFFON, OFFMaximum idxid="w7691"book="_idx" docset="nw312" tidref="i6260"Service Processes = 205 to 40Display Incomplete IPX Packet Alerts =  ONON, OFFReplace Console Prompt with Server  Name = ONON, OFFAllow Change to Client Rights = ONON, OFFID="FM10129"View Current idxid="w7692"book="_idx" docset="nw312" tidref="i1134"Operating idxid="w7693"book="_idx" docset="nw312" tidref="i4835"System ConfigurationsTo view the current configuration for the SET parameters, complete the following steps.ProcedureAt the console prompt, type  SET <Enter>The following information appears:LBL="1-41"Current operating system configuration informationFILE="n312sa77.pbm"To select a category, type the number of the category and press <Enter>.ID="FM50253"Change an idxid="w7694"book="_idx" docset="nw312" tidref="i1134"Operating System Parameter at the Console PromptTo change a idxid="w7695"book="_idx" docset="nw312" tidref="i6296"SET idxid="w7696"book="_idx" docset="nw312" tidref="i6296"parameter that can be set at the console prompt, type "SET" and the parameter.For example, to set the " idxid="w7697"book="_idx" docset="nw312" tidref="i4980"Allow unencrypted passwords" parameter so that unencrypted passwords are valid, type  SET ALLOW UNENCRYPTED PASSWORDS = ON <Enter>To set the parameter idxid="w7698"book="_idx" docset="nw312" tidref="i595"each time the file server is booted, add the following line to the AUTOEXEC.NCF file:  SET ALLOW UNENCRYPTED PASSWORDS = ONYou can modify the AUTOEXEC.NCF file with INSTALL or SYSCON.ID="FM93047"Change an Operating System Parameter in the STARTUP.NCF FileSome idxid="w7699"book="_idx" docset="nw312" tidref="i6296"SET parameters can be set only in the STARTUP.NCF file. For a list, see IDREF="FM94808""In the STARTUP.NCF File" on page 262.To change one of those parameters, complete the following steps.ProcedureLoad INSTALL. At the console prompt, type  LOAD INSTALL <Enter>Select "System Options."Select "Edit STARTUP.NCF file."Complete one of the following:If the STARTUP.NCF file is on the diskette in drive A:, press <Enter>.If the STARTUP.NCF is on the DOS partition, delete the "A" and type "C". Then press <Enter>.If the STARTUP.NCF file is located in a DOS partition directory other than C:\, verify that the proper directory path is specified following the drive letter designation.Add the SET parameter to the file. For example, to change the maximum subdirectory depth to 30, type  SET MAXIMUM SUBDIRECTORY TREE DEPTH = 30Save the file with the changes. Answer "Yes" to the exit prompts.Down the file server by typing  DOWN <Enter>Reboot the file server.ID="FM16553"Understand the Operating System ParametersThe following parameters are described according to their groupings in the SET information screens. ID="FM61196"Communications idxid="w7700"book="_idx" docset="nw312" tidref="i1077"The communication parameters determine the idxid="w7701"book="_idx" docset="nw312" tidref="i1077"settings for the packet idxid="w7702"book="_idx" docset="nw312" tidref="i4878"receive buffers and the watchdog packets. Packet receive buffers are areas in the file server's memory set aside to hold data packets. The packets remain in the buffers while the file server processes them. Use MONITOR to view the idxid="w7703"book="_idx" docset="nw312" tidref="i4878"number of packet receive buffers currently allocated.The idxid="w7704"book="_idx" docset="nw312" tidref="i7433"watchdog packets are used to make sure idxid="w7705"book="_idx" docset="nw312" tidref="i7493"workstations are currently connected. If the server has not received a packet from a workstation in a certain time (set by the Delay Before First Watchdog Packet parameter), a watchdog packet is sent to the station. If the station does not respond within a certain time (set by the Delay Between Watchdog Packets parameter), another watchdog packet is sent. If the station still does not respond to a certain number of watchdog packets (the Number of Watchdog Packets parameter), the server assumes that the station is no longer connected and clears the station's connection.NCP packet signature levels on the server are controlled with the NCP Packet Signature Option parameter.Console Display idxid="w7706"book="_idx" docset="nw312" tidref="i1204"Watchdog idxid="w7707"book="_idx" docset="nw312" tidref="i7433"Logouts = valueThis parameter determines whether a console message is displayed when a connection is cleared.If your network is running smoothly and stations are not having any problems with file server connections, you do not need to display watchdog logouts.If your stations are having connection problems, the watchdog logout messages can help you isolate which stations are not receiving or successfully sending watchdog packets.Supported values: ON and OFFDefault: OFFID="FM67970"Maximum Physical Receive Packet Size = numberThis parameter determines the maximum size of packets that can be transmitted on any of the file server's networks. The default allows 1 KB (data with the packet header) to be transmitted.If you are using Token-Ring or Ethernet boards, the default is acceptable.If some of the network boards can transmit more than 512 bytes of data per packet, set this parameter for the largest packet size.This parameter cannot be modified at the console prompt. To modify the default, you must include the parameter in the STARTUP.NCF file.Supported values: 618 to 24682Default: 1514ID="FM40728"Maximum Packet idxid="w7708"book="_idx" docset="nw312" tidref="i4878"Receive Buffers = numberThis parameter determines idxid="w7709"book="_idx" docset="nw312" tidref="i4903"the maximum number of packet receive buffers that the operating system can allocate.Before increasing this parameter, use MONITOR to view the file server's current use of packet receive buffers and service processes.If the number of packet receive buffers is at its maximum, increase this value in increments of 10 until you have one packet receive buffer per workstation.If you have EISA or microchannel bus master boards in your file server, increase this parameter to allow for at least 5 buffers per board. Use MONITOR ("LAN Information") to determine if the board is producing "No ECB available count" errors. If you are receiving "No ECB available count" errors, increase the parameter to allow for 10 packet receive buffers per board.If the number of allocated service processes is at its maximum, you can increase the "Maximum number of service processes" parameter to decrease the need for more packet receive buffers.Supported values: 50 to 2000Default: 400ID="FM85712"Minimum Packet Receive Buffers = numberThis parameter determines the minimum number of packet receive buffers that the operating system can allocate. Rather than waiting for requests to come in, the operating system allocates the minimum number of buffers as soon as the file server boots.Before increasing this parameter, use MONITOR to view the file server's current use of packet receive buffers. If the allocated number is higher than 10 and the server is slow in responding immediately after it has been booted, increase this number.If you have EISA or microchannel bus master boards in your file server and are receiving "No ECB available count" errors IDREF="FM43045"(see "LAN Information" on page 181) right after the file server boots, increase this parameter. Increase the parameter so that each board can have at least 5 packet receive buffers.This parameter can be changed only in the STARTUP.NCF file.Supported values: 10 to 1000Default: 100New idxid="w7710"book="_idx" docset="nw312" tidref="i4878"Packet Receive Buffer idxid="w7711"book="_idx" docset="nw312" tidref="i7418"Wait Time = timeThis parameter determines how long the operating system waits after receiving a request for another packet receive buffer before granting another buffer.This parameter prevents the operating system from granting too many packet receive buffers during a sudden peak in usage. If you have an EISA bus master board in your file server, this parameter should never be changed.Supported values: 0.1 seconds to 20 secondsDefault: 0.1 secondsNumber of Watchdog Packets = numberThis is the number of watchdog packets that the server will send out, without receiving a reply from a workstation, before eliminating the workstation's connection.Supported values: 5 to 100Default: 10Delay Between Watchdog Packets = timeThis is the amount of time between watchdog packets. After the server sends out the first watchdog packet, it waits the specified time before sending out the succeeding packets if it receives no reply.Supported values: 9.9 seconds to 10 minutes 26.2 secondsDefault: 59.3 secondsDelay Before First Watchdog Packet = timeThis is the amount of time the server waits without receiving a request from a workstation before it sends out the first watchdog packet to that workstation.Supported values: 15.7 seconds to 20 minutes 52.3 secondsDefault: 4 minutes 56.6 secondsidxid="w7712"book="_idx" docset="nw312" tidref="i4054"NCP idxid="w7713"book="_idx" docset="nw312" tidref="i6177"Packet Signature Option =numberThis parameter determines the packet signature level for the server. The signature level that is set on the server works in conjunction with the signature level of the client to determine the effective packet signature.Supported values: 0 to 3Default: 1This parameter can be set in the STARTUP.NCF file.After startup, you can only increase the packet signature level.The following table explains each of the packet signature level options for the server.WIDTH="72"NumberWIDTH="240"ExplanationWIDTH="72"0WIDTH="240"Server does not sign packets (regardless of the client  level)1Server signs packets only if the client requests it (client  level is 2 or higher)2Server signs packets if the client is capable of signing  (client level is 1 or higher)3Server signs packets and requires all clients to sign  packets (or logging in will fail)Some combinations of server and client packet signature levels may slow performance. However, low CPU-demand systems may not show any performance degradation. Network supervisors can choose the packet signature level that meets both their performance needs and their security requirementsEnable Packet Burst Statistics Screen = valueThis parameter determines whether the NCP Packet Burst Statistics Screen is displayed.Supported values: ON and OFFDefault: OFFReply to Get Nearest Server = valueThis parameter determines if the server will respond to Get Nearest Server requests from workstations that are attempting to locate a server.This parameter can be set in the STARTUP.NCF file.Supported values: ON and OFFDefault: ONEnable IPX Checksums = numberThis parameter determines the level of IPX checksums to be performed.Supported values: 0 to 2Default: 1The following table explains each of the IPX checksum level options.WIDTH="72"NumberWIDTH="240"ExplanationWIDTH="72"0WIDTH="240"No checksums performed1Checksums performed if enabled at the client2Checksums requiredAllow LIP = valueThis parameter determines if Large Internet Packet support is enabled.Supported values: ON and OFFDefault: ONID="FM79028"MemoryThe memory parameters control the size of the dynamic memory pool, the block size of the cache buffers, and the automatic registering of memory on EISA bus computers.ID="FM72268"Maximum idxid="w7714"book="_idx" docset="nw312" tidref="i198"Alloc Short Term idxid="w7715"book="_idx" docset="nw312" tidref="i3758"Memory = numberThe Alloc Short Term Memory pool stores the following information:Drive mappingsService request buffersOpen and locked filesUser connection informationMessages waiting to be broadcastLoadable module tablesQueue manager tablesThis parameter controls how much memory the operating system can allocate to the Alloc Short Term Memory pool. The 8MB default should be sufficient for up to 1000 users, each with 26 drive mappings.Decrease this value if the server is allocating more memory to this pool than is usually needed, due to a temporary situation.Increase this value if the file server issues warnings that operations cannot be completed because this memory pool has reached its limits. Increase the limit in increments of 1 MB.Use MONITOR to view the amount of memory allocated to the "Alloc Memory Pool" (the "Server Memory Statistics" window).Supported values: 50000 to 33554432Default: 8388608ID="FM20331"Auto Register Memory above 16 Megabytes = valueThis parameter controls the automatic registering of memory above 16 MB in EISA computers.Set this parameter to OFF if you have installed a network board or a disk adapter board that uses on-line DMA or AT bus mastering. Since the board uses 24-bit address lines, the board can address only 16 MB of memory correctly.If you install one of these boards and the file server addresses more than 16 MB of memory, the board will corrupt file server memory. The board will address low memory rather than its assigned high memory and corrupt the low memory being used by the operating system.Set this parameter to ON if you want memory above 16 MB to be registered with the operating system.This parameter cannot be set at the console prompt. To change the value, you must add the parameter to the STARTUP.NCF file and reboot the file server.Supported values: ON and OFFDefault: ONCache Buffer Size = numberThis parameter controls the block size of the cache buffer.If you are using block allocation sizes larger than 4,096 bytes (4 KB) on all volumes, you can improve performance in some situations by increasing the cache idxid="w7716"book="_idx" docset="nw312" tidref="i743"buffer size.If you are not using block allocation sizes larger than 4,096 bytes (4 KB), making the cache buffer larger decreases performance and wastes memory space. The operating system will not mount any volumes that have block allocation sizes smaller than the cache block size.If your volumes have different block allocation sizes, make your cache buffer size no larger than the smallest block allocation size.This parameter cannot be modified at the console prompt. To idxid="w7717"book="_idx" docset="nw312" tidref="i879"change the default value, include the parameter in the STARTUP.NCF file or run SERVER with the -c parameter. IDREF="FM49124"See "SERVER" on page 254.Supported values: 4096, 8192, and 16384 bytesDefault: 4096 bytesID="FM26817"File idxid="w7718"book="_idx" docset="nw312" tidref="i3758"Cachingidxid="w7719"book="_idx" docset="nw312" tidref="i2009"File caching allows faster access to frequently used files by idxid="w7720"book="_idx" docset="nw312" tidref="i7550"holding a file (or a portion of the file) in memory. Files that are being read from or written to are kept in file cache buffers. The number of files kept in memory depends on the number of file cache buffers. The number of file cache buffers is determined by the amount of available memory and the "Minimum file cache buffers" setting.Following are the operating system file caching parameters. idxid="w7721"book="_idx" docset="nw312" tidref="i2012"Minimum File Cache Buffers = numberThis idxid="w7722"book="_idx" docset="nw312" tidref="i2012"parameter sets the idxid="w7723"book="_idx" docset="nw312" tidref="i879"minimum number of idxid="w7724"book="_idx" docset="nw312" tidref="i879"cache buffers that the operating system can allow for file caching. All memory not allocated for other processes is given to file caching. As memory is requested for other uses, the file server gives up cache buffers. This limit specifies when the file server should stop giving file cache buffers to other processes.If you set the minimum too high, other server processes may not be able to allocate necessary memory resources. For example, a loadable module could fail to load because the file server has run out of available memory.Supported values: 20 to 1000Default: 20Maximum idxid="w7725"book="_idx" docset="nw312" tidref="i2008"Concurrent Disk Cache Writes = numberThis idxid="w7726"book="_idx" docset="nw312" tidref="i1517"parameter determines how many write requests for changed file data can be put in the elevator before the disk head begins a sweep across the disk.A high number makes the servicing of write requests more efficient.A low number makes the servicing of read requests more efficient.You should monitor the number of dirty cache buffers on the information screen of MONITOR. If this number is above 70% of the total cache buffers, you can optimize the write speed by increasing the limit for "Maximum concurrent disk cache writes."Supported values: 10 to 1000Default: 50Dirty Disk Cache Delay Time = timeThis parameter determines how long the operating system will keep a write request (that does not fill a cache buffer) in memory before writing the request to disk.If your users are making many small write requests, you can increase the time to make disk writing more efficient. If you decrease the time, you only slightly reduce the chances of losing data and you can drastically reduce performance.Supported values: 0.1 seconds to 10 secondsDefault: 3.3 secondsMinimum File Cache Report Threshold = numberThis parameter sets a threshold so that the operating system idxid="w7727"book="_idx" docset="nw312" tidref="i7429"warns you when it has allocated all available cache buffers within a idxid="w7728"book="_idx" docset="nw312" tidref="i879"specified number greater than the minimum. (Use SET to view the "Minimum file cache buffers" parameter for your system.)For example, if the minimum number of cache buffers is set to 20 and the "Minimum File Cache Report Threshold" is set to 20, the operating system warns you when all but 40 cache buffers have been allocated for other processes (directory caching, server processes, loadable modules, volume FATs). When the threshold has been reached, you receive the following message:  Number of cache buffers is getting too low.Regardless of how this parameter is set, the operating system warns you when the operating system's memory allocation resources reach the minimum number of cache buffers. When this threshold is reached, you receive the following message:  Cache memory allocator exceeded minimum cache buffer left limitSupported values: 0 to 1000Default: 20Read Ahead Enabled = valueWhen set to ON, and while sequential file access is taking place, background reads are done in advance to get blocks that are to be put into the cache.Supported values: ON and OFFDefault: OFFRead Ahead LRU Sitting Time Threshold = timeThis parameter determines the time after which the read ahead will occur. If the cache LRU sitting time is below the threshold setting, the read ahead will not take place.Supported values: 0 seconds to 1 hourDefault: 10 secondsReserved Buffers Below 16 Meg = numberThis parameter determines the number of cache buffers to be kept for certain device drivers which are unable to access memory above 16 MB.This parameter can be set only in the STARTUP.NCF file.Supported values: 8 to 300Default: 16ID="FM67437"Directory idxid="w7729"book="_idx" docset="nw312" tidref="i3758"Cachingidxid="w7730"book="_idx" docset="nw312" tidref="i1493"Directory idxid="w7731"book="_idx" docset="nw312" tidref="i1493"caching allows fast access to frequently used directories. A idxid="w7732"book="_idx" docset="nw312" tidref="i1484"directory cache buffer is a portion of file server memory that holds entries from the directory table. A directory entry stays in a cache buffer as long as it is being accessed frequently (the default setting is 33 seconds). When the directory entry is not being accessed frequently, the operating system can overwrite the entry if all the allocated directory cache buffers have been accessed more frequently.When the file server boots, the operating system allocates a minimum number of directory cache buffers (the default is 20). The operating system creates these buffers immediately when it receives a request for a new directory cache buffer.When the minimum number of directory cache buffers has been allocated and another one is needed, the operating system must wait a specified amount of time (the default is 1.1 seconds) before allocating another buffer. If necessary, the operating system keeps allocating directory cache buffers until the maximum number is reached.If a sufficient number of directory cache buffers have been allocated and enough memory is available for directory caching, the complete directory tables can be cached in memory.As directory cache buffers increase, file cache buffers decrease. Thus, a trade-off exists between directory caching and file caching. If you adjust the system to use too much memory for directory caching, you can leave too little memory for file caching, and vice versa. Directory caching and file caching need to be carefully balanced for maximum performance.Six directory caching parameters control the allocation of directory cache buffers. Usually, only the first three parameters listed below need to be changed.idxid="w7733"book="_idx" docset="nw312" tidref="i1484"Directory Cache idxid="w7734"book="_idx" docset="nw312" tidref="i1493"Buffer NonReferenced Delay = timeThis parameter sets how long a directory entry must be cached before it can be overwritten by another directory entry.If you increase the time, the operating system allocates more directory cache buffers. The longer time quickens directory access because a directory is more likely to be cached in memory.If you decrease the time, directory access can slow down because a directory is less likely to be in memory. But decreasing the time reduces the need for directory cache buffers since the operating system waits less before it reuses a cache buffer.Supported values: 1 second to 5 minutesDefault: 5.5 secondsMaximum Directory Cache Buffers = numberThis parameter sets the maximum cache buffers used for directory cache buffers. When the operating system allocates a directory cache buffer, the allocation is permanent until the file server reboots; the buffers do not return to file caching when the need for directory cache buffers decreases.This parameter keeps the operating system from allocating too many directory cache buffers so that memory is available for other file server processes.Increase this limit if the file server responds slowly to directory searches.Decrease this limit if too much memory is being allocated for directory caching. If users are alerted by the operating system that the server is low on memory, this parameter should be one of the first to be reduced. However, you must reboot the file server to return the memory to the cache buffer memory pool.idxid="w7735"book="_idx" docset="nw312" tidref="i1484"Supported values: 20 to 4000Default: 500idxid="w7736"book="_idx" docset="nw312" tidref="i1484"Minimum Directory Cache Buffers = numberThis parameter determines the minimum number of cache buffers that the operating system can allocate for directory caching. The parameter needs to be high enough that directory searches can be done quickly, but no higher than necessary.If the operating system does not need the minimum number of directory cache buffers, the buffers cannot be reallocated to file caching. The unneeded portion remains unused.If the file server responds slowly to directory searches after it has been booted, monitor the number of directory cache buffers usually allocated for directory caching. If the number is significantly higher than this limit, consider increasing the limit to remove the delay time that would normally occur while the file server is self-configuring. Use MONITOR to view the current statistics.Supported values: 10 to 2000Default: 20Dirty Directory Cache Delay Time = timeThis parameter determines how long the operating system keeps a directory idxid="w7737"book="_idx" docset="nw312" tidref="i1517"table write request in memory before writing it to disk.If you increase the delay time, the operating system gives slightly quicker performance, but the change also increases the probability of the directory tables becoming corrupted.If you decrease the delay time, you slightly reduce the chance of directory tables becoming corrupted, but the added number of disk writes can also slightly reduce performance. A zero setting dramatically reduces performance.Supported values: 0 to 10 secondsDefault: .5 secondsMaximum Concurrent idxid="w7738"book="_idx" docset="nw312" tidref="i1492"Directory Cache Writes = numberThis parameter determines how many write requests from directory cache buffers can be put in the elevator before the disk head begins a sweep across the disk.If you increase the number, the servicing of write requests becomes more efficient and the servicing of read requests becomes less efficient.If you decrease the number, the servicing of read requests becomes more efficient and the servicing of write requests becomes less efficient.Supported values: 5 to 50Default: 10idxid="w7739"book="_idx" docset="nw312" tidref="i1484"Directory Cache Allocation idxid="w7740"book="_idx" docset="nw312" tidref="i7418"Wait Time = numberThis parameter determines how long the operating system must wait after allocating a new directory cache buffer before it can allocate another buffer. During this time, all requests for a new directory cache buffer are ignored.If the wait time is too low, peak usage requests will cause more resources to be allocated to directory caching than needed.If the wait time is too high, the operating system will be very slow in allocating the directory cache buffers necessary to service the usual number of directory requests.If directory searches seem slow even after the file server has been running for 15 minutes, you may want to decrease this time.Supported values: 0.5 seconds to 2 minutesDefault: 2.2 secondsID="FM89876"File idxid="w7741"book="_idx" docset="nw312" tidref="i2278"SystemFile system parameters are used to control the following:File purgingWarnings about volumes that are almost fullidxid="w7742"book="_idx" docset="nw312" tidref="i2278"Re-use of turbo FATsThe file-purging parameters influence other parameters which, in turn, control warnings about almost-full volumes. All deleted files remain on the disk for a specified minimum amount of time. The operating system calculates a volume's remaining space by subtracting the following from the total space:Actual filesSalvageable files that cannot be purged because their "Minimum file delete wait times" have not expiredImmediate Purge Of Deleted Files = valueThis parameter controls the idxid="w7743"book="_idx" docset="nw312" tidref="i2300"salvageable file feature.If this parameter is set to OFF, files can be salvaged with the SALVAGE utility. See "book="utilref" docset="nw312"SALVAGE" in Utilities Reference.If this parameter is set to ON, all files are immediately purged when they are deleted. The ON setting disables all NetWare salvage features.Supported values: ON and OFFDefault: OFFidxid="w7744"book="_idx" docset="nw312" tidref="i7372"Volume Low idxid="w7745"book="_idx" docset="nw312" tidref="i7429"Warn All Users = valueThis parameter controls whether the operating system warns users when a volume is almost full. If you choose not to warn your users, monitor the volume statistics at least daily with CHKVOL or VOLINFO.Supported values: ON and OFFDefault: ONVolume Low Warning Reset Threshold = numberThis parameter controls how much disk space must be freed up before a second warning is issued. (The first warning is controlled by the "Volume Low Warn All Users" parameter.)When a volume is almost full, it can hover at its warning threshold. As users delete files and the files become candidates for purging, the space on the volume can move slightly above the warning threshold; then, as they create new files, the space on the volume can dip below the threshold. If a volume is hovering at its threshold, you do not want to warn users each time the volume dips below the threshold.This parameter controls the minimum amount of space that must be available above the threshold before users will again be warned that the space on the volume has dipped below the threshold.For example, suppose the following conditions exist:The volume block size is 4 KB.The "Volume low warning reset threshold" parameter is 256.The "Volume low threshold" parameter is set to 256.The volume has less than 1 MB of free space.Given these conditions, the volume must gain at least 1 MB of free space (for a total of 2 MB of free space) and then dip below 1 MB before the operating system sends a second warning that the volume is almost full.Supported values: 0 to 100000 blocksDefault: 256 blocksVolume Low Warning Threshold = numberThis parameter controls how little free disk space can remain on a volume before the operating system issues a warning. The parameter is set by entering the desired number of blocks. (A block is the minimum space allocated to a file; a file can only grow in multiples of the block size.)The block's physical size is determined when the volume is created. A volume can be assigned a 4KB, 8KB, 16KB, 32KB, or 64KB block size. For example, if you enter 256 blocks and the volume's block size is 4 KB, the operating system warns you that the volume is full when about 1 MB of space is left.If your volumes have been assigned different block sizes, each volume will have a different amount of free space when the warning is issued.Supported values: 0 to 100000 blocksDefault: 256 blocksMinimum File Delete idxid="w7746"book="_idx" docset="nw312" tidref="i7418"Wait Time = timeThis parameter determines how long a deleted file must stay in a idxid="w7747"book="_idx" docset="nw312" tidref="i6115"salvageable idxid="w7748"book="_idx" docset="nw312" tidref="i2300"state on the volume. Deleted files that have not met this minimum time limit will not be purged automatically even if the volume is full and users are unable to create new files.Supported values: 0 seconds to 7 daysDefault: 1 minute and 5.9 secondsFile Delete Wait Time = timeThis parameter determines when a salvageable file can be purged to create free space on the volume. The operating system tries to keep at least a minimum of 1/32 of the available space on the volume free for new files.When a file has been deleted for a greater time than the "File delete wait time," the operating system marks the file as a candidate for purging. When the volume becomes full of files that can be purged and needs free space to maintain the minimum amount, the operating system begins deleting the oldest files that can be purged.Set this parameter as high as is useful for your users, but remember that this parameter does not guarantee that the file will remain in a salvageable state. The parameter only guarantees that the file will not be purged to maintain the volume's minimum amount of free disk space (1/32 of the volume's size).Files that have not met this time limit will still be purged if the volume is full and the operating system needs space for a user to create a new file.Supported values: 0 seconds to 7 daysDefault: 5 minutes 29.6 secondsMaximum Percent Of Volume Used By Directory = percentageThis parameter limits the portion of a volume that may be used as directory space.Supported values: 5 to 50Default: 13Maximum Percent Of Volume Space Allowed For Extended Attributes = percentageThis parameter limits the portion of volume space that may be used for extended attribute storage. This setting only takes effect when the volume is being mounted.Supported values: 5 to 50Default: 10Maximum Extended Attributes Per File or Path = numberThis parameter sets a limit to the number of extended attributes that can be assigned to a file or path (subdirectory). This limit is for all the volumes on the server.Supported values: 4 to 512Default: 8NCP File Commit = valueThis parameter controls whether applications can flush all pending file writes to disk. When a File Commit NCP is issued and the flag is set to ON, a file is flushed from the cache to disk immediately, instead of waiting for the cache manager to flush it to disk some time later.Supported values: ON and OFFDefault: ONMaximum idxid="w7749"book="_idx" docset="nw312" tidref="i6563"Subdirectory Tree Depth = numberThis parameter determines how many levels of idxid="w7750"book="_idx" docset="nw312" tidref="i6563"subdirectories the operating system supports. Some DOS applications cannot support more than 10 levels if the subdirectories have eleven-character names.Increase the number if your applications support trees deeper than 25.Decrease the number if your applications support only shallow tree structures.This parameter cannot be set at the console prompt. To change the value, you must add the parameter to the STARTUP.NCF file and reboot the file server.Supported values: 10 to 100Default: 25idxid="w7751"book="_idx" docset="nw312" tidref="i7418"Turbo FAT Re-Use Wait Time = timeThis parameter determines how long a idxid="w7752"book="_idx" docset="nw312" tidref="i1968"turbo FAT buffer remains in memory after an idxid="w7753"book="_idx" docset="nw312" tidref="i2300"indexed file is closed. Once the wait-time value has passed, the operating system can allocate the buffer to another indexed file.The NetWare v3.x operating system automatically indexes any randomly accessed file that has 64 entries in the FAT. When a program starts randomly accessing a file that contains more than 64 FAT entries, the operating system automatically builds a turbo FAT index for the file so that the information can be accessed quickly.Since a turbo FAT index takes time to build, the operating system does not immediately delete the index from its buffer when the file is closed. Having the turbo FAT index already in memory makes reopening the file and accessing the information faster.Increase the wait time if you want the turbo FAT index to remain in memory for long periods of time, even when the file is closed.Increase the wait time if you frequently reopen the same file after a specific delay and know that another file opened during that delay will reuse the index.Decrease the wait time if you want the memory immediately released to service the next file that needs to be indexed.Supported values: 0.3 seconds to 1 hour 5 minutes 54.6 secondsDefault: 5 minutes 29.6 secondsID="FM48344"Lock idxid="w7754"book="_idx" docset="nw312" tidref="i3378"The lock parameters control how many open idxid="w7755"book="_idx" docset="nw312" tidref="i2300"files each station can have and how many total open files the operating system can handle. They also control how many record idxid="w7756"book="_idx" docset="nw312" tidref="i2300"locks each connection can have and how many total record locks the operating system can handle. These parameters control three types of locks: file, physical, and idxid="w7757"book="_idx" docset="nw312" tidref="i3423"logical.A file lock secures the entire file and prevents other stations from accessing the file.Aidxid="w7758"book="_idx" docset="nw312" tidref="i5083"physical record lock controls data access by multiple users. It prevents other users from accessing or changing a range of bytes (a record) in a file. A physical record lock is enforced by the operating system. If another user attempts to access a range of bytes that is physically locked, the user receives an "Access Denied" error message.A logical record lock also controls data access by multiple users. The application assigns a name to each section of data that needs to be locked. The application then locks this name whenever it accesses the data. A logical lock is not enforced by the operating system; it is enforced only to the extent that the application checks the name each time it needs access to data.idxid="w7759"book="_idx" docset="nw312" tidref="i7493"Maximum Record Locks Per Connection = numberThis parameter controls how many record locks a station can use at one time.Increase this parameter when an application cannot lock enough records and fails.Decrease this parameter if workstations are using too many file server resources. Use MONITOR to view how many record locks a workstation is using.Supported values: 10 to 10000Default: 500Maximum File Locks Per Connection = numberThis parameter controls how many idxid="w7760"book="_idx" docset="nw312" tidref="i7493"opened and locked files a station can use at one time.Increase this parameter when an application cannot open enough files and fails. An OS/2 workstation might need a higher default than 250. You may also need to increase the number of file handles in the workstation's NET.CFG file.Decrease this parameter if workstations are using too many file server resources. Use MONITOR to view how many opened and locked files a workstation is using.Supported values: 10 to 1000Default: 250idxid="w7761"book="_idx" docset="nw312" tidref="i2034"Maximum Record Locks = numberThis parameter controls how many record locks the operating system can handle.Increase this parameter if users are having problems running applications and are receiving messages indicating that not enough record locks are available.Decrease this parameter if users are using too many file server resources. Use MONITOR to view how many record locks a workstation is using.Supported values: 100 to 200000Default: 20000idxid="w7762"book="_idx" docset="nw312" tidref="i2034"Maximum File Locks = numberThis parameter controls how many idxid="w7763"book="_idx" docset="nw312" tidref="i2034"opened and locked files the operating system can handle.Use MONITOR to view the number of files that are open during peak usage.Increase this parameter if the current number of open files is near or equal to the default.Decrease this parameter if you want to restrict the number of available file server resources.Supported values: 100 to 100000Default: 10000ID="FM80156"Transaction Trackingidxid="w7764"book="_idx" docset="nw312" tidref="i6864"The transaction tracking parameters control the Transaction Tracking System (TTS). A transaction is a set of write operations that must be completed together in order to maintain file and database integrity. Write operations consist not only of data and data records, but also of changes to the index and the key structures that are important to an application's continual operation.TTS guarantees that a transaction will be either written to disk in its complete form or backed out if incomplete. This ensures database integrity in the event that the workstation, the file server, or the LAN fails before a transaction has been completed. Most of these idxid="w7765"book="_idx" docset="nw312" tidref="i6864"parameters should not be changed.Auto TTS Backout Flag = valueThis parameter determines whether a crashed file server with transactional files can automatically back out any incomplete transactions when the file server is booted.When this parameter is set to ON, the file server automatically backs out any incomplete transactions during its bootup procedures.When the parameter is set to OFF, the file server waits for you to answer the following prompt before it finishes its bootup procedures.  Incomplete transaction(s) found. Do you wish to back them out?You can only set this parameter in the STARTUP.NCF file, not at the console prompt.Supported values: ON and OFFDefault: OFFTTS Abort Dump Flag = valueThis parameter controls whether a file will be created to log transactional backout data. When the file server fails during a data write to a file that is flagged transactional, the operating system can back out the incomplete write.If this parameter is set to ON, the information that is backed out is written to the TTS$LOG.ERR file located in volume SYS:. To read the file, either print the file or view it with a text editor.If this parameter is set to OFF, the information that is backed out is not saved.Supported values: ON and OFFDefault: OFFMaximum Transactions = numberThis parameter determines how many transactions can occur at the same time.Supported values: 100 to 10000Default: 10000idxid="w7766"book="_idx" docset="nw312" tidref="i7418"TTS UnWritten Cache Wait Time = timeThis parameter determines how long a block of transactional data can be held in memory. Some blocks of transaction data wait for other transactional blocks to be written first. If one of these blocks reaches its maximum time limit, other write requests are held up and this block is written to disk.Supported values: 11 seconds to 10 minutes 59.1 secondsDefault: 1 minute 5.9 secondsTTS Backout File idxid="w7767"book="_idx" docset="nw312" tidref="i7418"Truncation Wait Time = timeThis parameter determines the minimum amount of time that allocated blocks remain available for the TTS backout file when these blocks are not currently being used.Supported values: 1 minute 5.9 seconds to 1 day 2 hours 21 minutes  51.3 secondsDefault: 59 minutes 19.2 secondsID="FM13537"DiskThe disk parameters control read-after-write verification and the number of remirror requests per logical partition.The idxid="w7768"book="_idx" docset="nw312" tidref="i2599"disk parameter Enable Disk Read After Write Verify controls one part of idxid="w7769"book="_idx" docset="nw312" tidref="i2682"Hot idxid="w7770"book="_idx" docset="nw312" tidref="i2599"Fix redirection. Hot Fix redirection can occur during a write request, a read request, or a idxid="w7771"book="_idx" docset="nw312" tidref="i5757"read-after-write verification.Write redirection occurs when the disk reports an error during a write request. The operating system marks the block as bad and redirects the data to a different block.Read redirection occurs when a disk error occurs during a read request. If the hard disk is mirrored, the operating system retrieves the data from the mirrored disk and redirects the data on the primary disk. If the hard disk is not mirrored, the data is lost, but the block is marked as bad so that future data will not be stored there.Read-after-write verify redirection occurs after the data is written to disk. The data on disk is then read and compared to that in memory. If the two do not match, the operating system marks the block as bad and redirects the data to a different block.Enable Disk Read After Write Verify = valueThis parameter controls whether information written to disk will be compared with that in memory. Normally, you would not want to disable this portion of Hot Fix. However, if your disks are mirrored and reliable and you need extra speed on disk writes, disabling read-after-write verify can almost double the speed of disk writes.Supported values: ON and OFFDefault: ONConcurrent Remirror Requests = numberThis parameter determines the number of remirror requests per logical partition.This parameter can be set only in the STARTUP.NCF file.Supported values: 2 and 30Default: 4ID="FM10635"MiscellaneousThe miscellaneous parameters control the following:Encrypted passwordsAlertsNCP searchesServer processesChanges to client rightsNormally, you will only need to change the setting for encrypted passwords.ID="FM60106"Allow Unencrypted idxid="w7772"book="_idx" docset="nw312" tidref="i4980"Passwords = valueThis parameter controls the use of unencrypted passwords. An ON setting allows users to use both unencrypted and encrypted passwords. An OFF setting allows users to use only encrypted passwords.If file servers on your network are running versions of NetWare earlier than NetWare v3.0 and you leave the default to OFF, your users may have problems logging in.If your network has file servers running NetWare v2.12 and later but none running v2.0a, you can copy the NetWare v3.1x utilities to these file servers and set this parameter to OFF. If you do not copy the NetWare v3.1x utilities to the NetWare v2.x file servers, set the parameter to ON.If all file servers are running NetWare v3.1x, set this parameter to OFF.If you have file servers running NetWare v2.0a, set this parameter to ON.Supported values: ON and OFFDefault: OFFidxid="w7773"book="_idx" docset="nw312" tidref="i183"Display Spurious Interrupt Alerts = valueThis parameter controls the alerts about spurious interrupts. A message is sent to the file server console whenever the hardware in the file server creates an interrupt that has been defined and reserved for another device. Such interrupts, which are labeled spurious, generate the following type of message:  Spurious hardware interrupt <number> detectedThis message indicates a serious error in the hardware.If your file server console displays this message, remove all add-on boards and run SERVER. If the message does not appear, add the boards one at a time until you have discovered which piece of hardware is creating the spurious interrupt. Then contact the vender. (Set the parameter to OFF while you are waiting for a resolution.)Supported values: ON and OFFDefault: ONDisplay idxid="w7774"book="_idx" docset="nw312" tidref="i183"Lost idxid="w7775"book="_idx" docset="nw312" tidref="i2946"Interrupt Alerts = valueThis parameter controls the alerts about lost interrupts. A message is sent to the file server console whenever a driver or board requests a service with an interrupt call and then drops the request before the CPU can respond to the request. Such interrupts, which are labeled lost, generate the following message:  Interrupt controller detected a lost hardware interruptThis message indicates a hardware or driver problem that could degrade performance. Unload all the drivers, and then reload them one at a time to determine which driver has the problem. Then contact the vender of the driver. (Set the parameter to OFF while you are waiting for a resolution.)Supported values: ON and OFFDefault: ONDisplay Disk idxid="w7776"book="_idx" docset="nw312" tidref="i1559"Device idxid="w7777"book="_idx" docset="nw312" tidref="i183"Alerts = valueThis parameter controls the informational messages about idxid="w7778"book="_idx" docset="nw312" tidref="i2599"hard disks. A message is generated each time a hard disk is added, activated, deactivated, mounted, or dismounted. For example, if the parameter is set to ON, the following types of messages appear:  Device # 0 (20000) ISA Type 043 added  Device # 0 (20000) ISA Type 043 activated.  Device # 0 (20000) ISA Type 043 deactivated dueSet this parameter to ON if you want such messages displayed when a disk driver is loaded or unloaded, when the file server is booted or downed, or when you are trying to isolate a problem with a disk driver or a hard disk.Set this parameter to OFF if you are not experiencing any hard disk problems.Supported values: ON and OFFDefault: OFFDisplay idxid="w7779"book="_idx" docset="nw312" tidref="i183"Relinquish idxid="w7780"book="_idx" docset="nw312" tidref="i6910"Control Alerts = valueThis parameter controls messages about CPU control. If an NLM uses the processor for more than .4 seconds without relinquishing control to other processes, the following types of idxid="w7781"book="_idx" docset="nw312" tidref="i6910"messages appear:  <process name> Process did not relinquish control frequently.  Module: <module name>  Code offset in module: <memory address>This parameter controls whether the generated messages are sent to the file server console.Set this parameter to ON if you are writing your own NLMs.Set this parameter to OFF if you are not writing your own NLMs.Supported values: ON and OFFDefault: OFFDisplay Old API Names = valueThis parameter controls messages about NetWare v3.0 idxid="w7782"book="_idx" docset="nw312" tidref="i183"API idxid="w7783"book="_idx" docset="nw312" tidref="i205"calls. NetWare v3.1x renamed some of the APIs as additional resources were tracked. (Resource tracking protects your file server from loadable modules that try to use more than their share of resources. In addition, resource tracking forces the loadable modules to relinquish all their resources when unloaded.)The following types of messages appear when a module that uses the old APIs is loaded:  Module is using old API: SetInterruptVector  Module is using old API: ReturnPermanentMemory  Module is using old API: AllocateReturnablePermMemoryThe old APIs work, but more slowly than the new APIs. If you receive these messages, contact the vender of the module.Set this parameter to ON if you are writing your own NLMs and you are upgrading NetWare v3.0 NLMs to the new v3.1x APIs.Set this parameter to OFF if you are not upgrading NLMs to NetWare v3.1x.Supported values: ON and OFFDefault: OFFPseudo Preemption Time = timeThis parameter is available for certain NLMS to keep an NLM process from using too much CPU time. Set this parameter only as your NLM documentation recommends.Supported values: 1000 to 10000 (raw CPU time, approximately .84 seconds each.)Default: 2000Maximum Outstanding NCP Searches = numberThis parameter idxid="w7784"book="_idx" docset="nw312" tidref="i1475"determines the maximum number of idxid="w7785"book="_idx" docset="nw312" tidref="i4236"NetWare Core Protocol (NCP) directory searches that can be processed at the same time.Normally, only one idxid="w7786"book="_idx" docset="nw312" tidref="i4041"NCP directory search occurs at a time. Increase this default only if you are using applications that support multiple outstanding directory search operations at the same time and you have problems with corrupted or invalid directory information.Supported values: 10 to 1000Default: 51New idxid="w7787"book="_idx" docset="nw312" tidref="i6260"Service Process idxid="w7788"book="_idx" docset="nw312" tidref="i7418"Wait Time = timeThis parameter determines how long the operating system waits after receiving a request for another service process before making the allocation.Supported values: 0.3 seconds to 20 secondsDefault: 2.2 secondsMaximum Service Processes = numberThis parameter determines the maximum number of service processes that the operating system can create. The number that have currently been allocated can be viewed in MONITOR.Decrease this number temporarily if the file server is low on memory. If the file server is always low on memory, add memory.Increase this number if the service processes number is at the maximum. File servers supporting many users and heavy usage may need more than the default of 20 service processes. However, increasing this number will help only if more than 20 requests are being delayed simultaneously for a disk I/O to be completed.Supported values: 5 to 40Default: 20Display Incomplete IPX Packet Alerts = valueThis parameter determines if alert messages are displayed when IPX receives incomplete packets.This parameter can be set only in the server's STARTUP.NCF file.Supported values: ON and OFFDefault: ONReplace Console Prompt with Server Name = valueThis parameter determines if the console prompt should be replaced with the server name.This parameter can be set in the server's STARTUP.NCF file.Supported values: ON and OFFDefault: ONAllow Change to Client Rights = valueThis parameter determines whether a server can assume the rights of a client. For example, when this parameter is set to ON, a print on the job server is allowed to assume the rights of the submitter of the queue job as it is being submitted.This parameter can be set in the server's STARTUP.NCF file.Supported values: ON and OFFDefault: ONThe default is for this parameter ON, because certain job servers and third-party applications cannot function without changing to client rights. If the parameter is set to OFF, some of these third-party applications may not function.SET TIMEWhy Use idxid="w7789"book="_idx" docset="nw312" tidref="i6302"SET TIME?Use SET TIME to set the date and time kept by the idxid="w7790"book="_idx" docset="nw312" tidref="i2127"file server.Command Format  SET TIME [month/day/year] [hour:minute:second]Replace the variables with the appropriate information.Time FormatEnter the time in either standard or military format:1:15:32 (standard time)13:15:32 (military time)Separate the hours, minutes, and seconds with colons (hours:minutes:seconds). You can omit the minute and second entries, but you must include the colon after the hour.You can also specify AM or PM (for example, 7:14:32 AM). If you do not specify AM or PM, the file server supplies this information for you, based on usual working hours.The file server always displays the time in the standard format (1:15:32 PM).Date FormatEnter the date in any of these formats:11/28/93November 28, 199328 November 1993Additional InformationYou can set both the date and the time in the same command, or you can set each one separately. You can enter either the date or the time first. If you replace only one variable, the other variable remains unaffected.If you do not enter either the date or the time, the file server console displays the current date and time recorded in the file server's clock.Set the idxid="w7791"book="_idx" docset="nw312" tidref="i1321"Date and idxid="w7792"book="_idx" docset="nw312" tidref="i6789"Time on the File ServerExampleFor example, idxid="w7793"book="_idx" docset="nw312" tidref="i2218"to set the date and time on your file server to December 19, 1993 at 2:15 PM, type  SET TIME 12/19/93 2:15:00 PM <Enter>or  SET TIME December 19, 1993 14:15:00 <Enter>or  SET TIME 19 December 1993 2:15:00 <Enter>ID="FM53359"SET TIMEZONEWhy Use idxid="w7794"book="_idx" docset="nw312" tidref="i2218"SET TIMEZONE?Use idxid="w7795"book="_idx" docset="nw312" tidref="i6303"SET TIMEZONE idxid="w7796"book="_idx" docset="nw312" tidref="i2127"to configure time zone information in idxid="w7797"book="_idx" docset="nw312" tidref="i977"CLIB. This information is used by NLMs that make calls to CLIB. This command does not automatically change the file server from standard time to daylight time.The default value is EST5EDT (Eastern Standard Time, 5 hours from Greenwich Mean Time, Eastern Daylight Time).Command Format  SET TIMEZONEor  SET TIMEZONE zone[hours[daylight]]Command ParametersReplace zone with a three-letter abbreviation for the name of the time zone. For example, in the continental United States, one of the following would be used:WIDTH="168"Time zoneWIDTH="132"ZoneWIDTH="168"Eastern Standard TimeWIDTH="132"ESTCentral Standard TimeCSTMountain Standard TimeMSTPacific Standard TimePSTReplace hours with the number of hours west of Greenwich Mean Time (GMT). Use a plus in front of the number if your time zone is east of the GMT time zone line. For example, in the continental United States, you would use one of the following:WIDTH="168"Time zoneWIDTH="132"Hours from GMTWIDTH="168"ESTWIDTH="132"5CST6MST7PST8Replace daylight with a three-letter abbreviation for the daylight savings code. This parameter is optional. If you do not enter this parameter, CLIB assumes that you are on standard time.For example, in the continental United States, one of the following would be used during the daylight savings months:WIDTH="168"Time zoneWIDTH="132"Daylight zoneWIDTH="168"ESTWIDTH="132"EDTCSTCDTMSTMDTPSTPDTDisplay the idxid="w7798"book="_idx" docset="nw312" tidref="i6786"Time Zone InformationTo display the time zone, type  SET TIMEZONE <Enter>A message similar to the following appears:  Timezone is set to: EST5EDTChange the idxid="w7799"book="_idx" docset="nw312" tidref="i6786"Time Zone InformationTo change the time zone to Mountain Standard Time, type  SET TIMEZONE MST7 <Enter>To change the time zone to California Pacific Daylight Time, type  SET TIMEZONE PST8PDT <Enter>If you live east of London, you enter the hours with a plus, meaning later than Greenwich Mean Time. For example, to set the time zone for Germany, type  SET TIMEZONE MEZ+1 <Enter>SPEEDWhy Use idxid="w7800"book="_idx" docset="nw312" tidref="i2127"SPEED idxid="w7801"book="_idx" docset="nw312" tidref="i6437"?Use SPEED to display the speed at which the processor is running.Command Format  SPEEDView the idxid="w7802"book="_idx" docset="nw312" tidref="i1265"Processor SpeedTo view the idxid="w7803"book="_idx" docset="nw312" tidref="i5594"processor speed, type  SPEED <Enter>The processor speed rating is determined by the following:CPU clock speed (16MHz, 20MHz, 25MHz, etc.)CPU type (80386SX, 80386, 80486, etc.)Number of memory wait states (0, 1, 2, etc.)An 80386SX CPU running at 16MHz should get a rating of about 95. An 80386 CPU running at 16MHz should get a rating of about 120. If your computer has a slower rating than you expected, check the CPU speed setting.Some computers have an AUTO or COMMON CPU speed mode that can reduce the clock speed to as little as 6MHz.Check your computer's documentation and set the CPU speed setting to the highest setting.SPOOLWhy Use idxid="w7804"book="_idx" docset="nw312" tidref="i6439"SPOOL idxid="w7805"book="_idx" docset="nw312" tidref="i2127"?Use SPOOL to create, change, or display spooler idxid="w7806"book="_idx" docset="nw312" tidref="i6447"mappings.These mappings are necessary to set up idxid="w7807"book="_idx" docset="nw312" tidref="i1345"default idxid="w7808"book="_idx" docset="nw312" tidref="i5375"print queues for idxid="w7809"book="_idx" docset="nw312" tidref="i4755"NPRINT and idxid="w7810"book="_idx" docset="nw312" tidref="i922"CAPTURE. They also support applications that make calls to printer numbers rather than to queues.Command Format  SPOOL n [TO] [QUEUE] nameFor a complete explanation of SPOOL, seebook="print" docset="nw312"Print Server.SPXCONFGWhy Use idxid="w7811"book="_idx" docset="nw312" tidref="i3278"SPXCONFG idxid="w7812"book="_idx" docset="nw312" tidref="i3300"?Use idxid="w7813"book="_idx" docset="nw312" tidref="i6460"SPXCONFG idxid="w7814"book="_idx" docset="nw312" tidref="i6457"to configure certain parameters of SPX. You may use SPXCONFG in an .NCF file, as a console command, or as an interactive menu utility.Command Format  LOAD [path]SPXCONFG [option[=value]] [option[=value]]Command ParametersReplace path with a full path to the directory containing the SPXCONFG module. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path, the operating system looks for SPXCONFG in SYS:SYSTEM. (Use SEARCH to set up additional paths for automatic searching.)If you do not specify a parameter, a menu of parameters appears. You can then select parameters to change interactively. The available options and values are as follows:WIDTH="108"OptionWIDTH="192"ExplanationWIDTH="108"A=WIDTH="192"SPX Watchdog Abort timeout (in ticks)V=SPX Watchdog Verify timeout (in ticks)W=SPX Ack wait timeout (in ticks)R=SPX Default Retry countS=Maximum concurrent SPX sessionsQ=1Quiet mode (suppresses display of changed  settings)HDisplays SPXCONFG help screenSet SPX Parameters in a Single Command or in an .NCF FileYou may set SPX parameters in a single console command, or add the command to an .NCF file. To do so, use SPXCONFG with the desired parameters. For instructions on editing or creating an .NCF file, IDREF="FM69715"see "EDIT" on page 40 or IDREF="FM11821""INSTALL" on page 47. Following is a sample usage:  LOAD SPXCONFG A=1000 Q=1 <Enter>Use SPXCONFG Interactively to Change SPX ParametersProcedureTo load SPXCONFG, type  LOAD SPXCONFG <Enter>A menu similar to the following menu appears:LBL="1-42""SPX Configuration Control Program" menuFILE="n312sa87.pbm"The numbers on the right of the parameters are the current settings.Press the letter of the parameter you want to change.Minimum, maximum, and default values for the parameter are shown in parentheses.Type in the value you want.The screen returns to the main menu displaying the value you selected.Repeat Steps 2 and 3 if you want to change other parameters. When you are finished setting SPX parameters, press <Esc> to exit.SPXSWhy Use idxid="w7815"book="_idx" docset="nw312" tidref="i6460"SPXS?Use idxid="w7816"book="_idx" docset="nw312" tidref="i2127"SPXS idxid="w7817"book="_idx" docset="nw312" tidref="i3300"to provide idxid="w7818"book="_idx" docset="nw312" tidref="i6540"STREAMS-based idxid="w7819"book="_idx" docset="nw312" tidref="i6456"SPX protocol services.Command Format  LOAD [path]SPXSCommand ParametersReplace path with a full path to the directory containing the SPXS module. Begin with a DOS drive letter or a NetWare volume. If you do not specify a path and volume SYS: is mounted, the operating system assumes idxid="w7820"book="_idx" docset="nw312" tidref="i5640"SPXS is in the SYS:SYSTEM directory. (Use SEARCH to set up paths for automatic searching.)Additional InformationDo not unload a protocol-stack NLM such as SPXS until you have unloaded all applications that may use it.If your module needs STREAMS-based SPX protocol services, load the following modules in the order listed:idxid="w7821"book="_idx" docset="nw312" tidref="i6540"STREAMSidxid="w7822"book="_idx" docset="nw312" tidref="i977"CLIBidxid="w7823"book="_idx" docset="nw312" tidref="i6800"TLISPXSLoad SPXSTo load SPXS, type  LOAD SPXS <Enter>ID="FM57739"STREAMSWhy Use STREAMS idxid="w7824"book="_idx" docset="nw312" tidref="i3300"?Use idxid="w7825"book="_idx" docset="nw312" tidref="i2127"STREAMS if you have a loadable module that requires the CLIB loadable module or uses STREAMS-based protocol services. STREAMS must be loaded before CLIB is loaded.Command Format  LOAD [path]STREAMSCommand ParametersReplace path with a full directory path to the directory containing the module. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path and volume SYS: is mounted, the operating system assumes that the loadable module is located in the SYS:SYSTEM directory. (Use SEARCH to set up additional paths for automatic searching.)Load STREAMSTo load STREAMS, type  LOAD STREAMS <Enter>TIMEWhy Use idxid="w7826"book="_idx" docset="nw312" tidref="i2127"TIME idxid="w7827"book="_idx" docset="nw312" tidref="i6776"?Use TIME to display the date and time kept by the file server's clock.Command Format  TIMEAdditional InformationTo reset the file server's date or time, use SET TIME.View idxid="w7828"book="_idx" docset="nw312" tidref="i1321"the File Server's Date and idxid="w7829"book="_idx" docset="nw312" tidref="i6789"TimeTo idxid="w7830"book="_idx" docset="nw312" tidref="i2218"view the date and time kept by the file server, type  TIME <Enter>A message similar to the following appears:  September 3, 1993 3:11:25 PMTLIWhy Use idxid="w7831"book="_idx" docset="nw312" tidref="i6800"TLI idxid="w7832"book="_idx" docset="nw312" tidref="i3300"?Use idxid="w7833"book="_idx" docset="nw312" tidref="i2127"TLI to provide TLI idxid="w7834"book="_idx" docset="nw312" tidref="i1087"communication services. TLI requires STREAMS and CLIB, so TLI loads them automatically if you haven't loaded them. You also need to load one or more protocol service NLMs, such as SPXS or IPXS.Command Format  LOAD [path]TLICommand ParametersReplace path with a full directory path to the directory containing the module. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path and volume SYS: is mounted, the operating system assumes that the loadable module is located in the SYS:SYSTEM directory. (Use SEARCH to set up additional paths for automatic searching.)Additional Informationidxid="w7835"book="_idx" docset="nw312" tidref="i6540"After idxid="w7836"book="_idx" docset="nw312" tidref="i977"loading TLI, load the protocol service modules.Load TLITo load TLI, type  LOAD TLI <Enter>ID="FM16803"TRACK OFFWhy Use idxid="w7837"book="_idx" docset="nw312" tidref="i6854"TRACK OFF idxid="w7838"book="_idx" docset="nw312" tidref="i2127"?Use TRACK OFF to prevent the file server from displaying network advertising idxid="w7839"book="_idx" docset="nw312" tidref="i4903"packets that are received or sent on the idxid="w7840"book="_idx" docset="nw312" tidref="i6027"Router Tracking Screen. This command turns off the Router Tracking Screen.Command Format  TRACK OFFTurn Off the Router Tracking ScreenTo turn off the Router Tracking Screen, first get to the console prompt by typing <Alt><Esc>. Then type  TRACK OFF <Enter>IDREF="FM23472"See also "TRACK ON" on page 324.ID="FM23472"TRACK ONWhy Use idxid="w7841"book="_idx" docset="nw312" tidref="i1064"TRACK ON idxid="w7842"book="_idx" docset="nw312" tidref="i6856"?Use idxid="w7843"book="_idx" docset="nw312" tidref="i2127"TRACK ON idxid="w7844"book="_idx" docset="nw312" tidref="i4903"to display the Router Tracking Screen and to make it the active screen. This command signals the idxid="w7845"book="_idx" docset="nw312" tidref="i2111"router to display all server and network advertising packets that are received or sent.Command Format  TRACK ONSignal the idxid="w7846"book="_idx" docset="nw312" tidref="i6027"Router to Display PacketsTo turn on the Router Tracking Screen, type  TRACK ON <Enter>IDREF="FM16803"See also "TRACK OFF"; IDREF="FM87975""DISPLAY NETWORKS"; IDREF="FM76631""DISPLAY SERVERS"; and IDREF="FM63130""RESET ROUTER."Additional InformationTRACK ON displays three types of information:ServerNetworkConnection requestsThis information is formatted according to whether the file server is receiving the information (IN), broadcasting the information (OUT), or receiving a connection request.Incoming idxid="w7847"book="_idx" docset="nw312" tidref="i6037"InformationIncoming information looks similar to the following:LBL="1-43"Router Tracking Screen incoming informationFILE="n312sa89.pbm"Each item in the display is described below.WIDTH="108"INWIDTH="192"Indicates that the message is  incoming.00DOC200Indicates the network number of the  file server sending the packet.  NetWare v3.1x file servers broadcast  on their internal and cabling network  numbers.0001B026C09Indicates the node address of the file  server sending the packet.Either server or network information follows the node address.Server InformationWIDTH="108"BILLYBOBWIDTH="192"Indicates the name of a file server  known by the sending file server.5Indicates the number of hops from  the sending file server to this file  server.Network InformationWIDTH="108"00001EEEWIDTH="192"Indicates the network number of a  network known by the sending file  server.2/Indicates the number of hops from  the sending file server to this network./3Indicates the number of ticks (1/18th  of a second) that a packet would take  to reach this network from the  sending file server.Outgoing InformationOutgoing information looks similar to the following:LBL="1-44"Router Tracking Screen outgoing informationFILE="n312sa90.pbm"Each item in the display is described below.WIDTH="108"OUTWIDTH="192"Indicates that the message is  outgoing.1986DAD0Indicates the network number of the  file server sending the packet.  NetWare v3.1x file servers broadcast  on their internal and cabling network  numbers.FFFFFFFFFFFFIndicates that the message is for all  nodes on the network.Either file server or network information follows the node address. Connection RequestWhen a workstation boots and loads the NETx file, a "GET Nearest Server" request is broadcast on the network to which the workstation is cabled. Any file server that is connected can receive the message and respond to the workstation with a "Give Nearest Server" response. The workstation initially attaches to the first file server to respond to the "Get Nearest Server" request.UNBINDWhy Use idxid="w7848"book="_idx" docset="nw312" tidref="i7069"UNBIND idxid="w7849"book="_idx" docset="nw312" tidref="i2127"?Use UNBIND to remove a communication protocol from the LAN driver of a network board or to change the network number. Use UNBIND to disable communication on a specific board.The following tasks are described in this section:WIDTH="264"TaskWIDTH="48"PageWIDTH="264"Unbind a protocol from a driverWIDTH="48"IDREF="FM83654"330Change the network number for the cablingIDREF="FM90834"332Command Format   UNBIND protocol [FROM] LAN_driver [driver_parameter...]Command OptionsReplace protocol with idxid="w7850"book="_idx" docset="nw312" tidref="i3005"IPX. If you have bound protocols other than IPX, replace idxid="w7851"book="_idx" docset="nw312" tidref="i3085"protocol with the name of the protocol you want to unbind.Replace LAN_driver with a driver you are currently using. The following drivers ship with NetWare:3C5033C5053C523NE2NE2-32NE1000NE2000NE3200PCN2TOKENTRXNETSpecify a driver_parameter only when you have more than one network board of the same type in your file server. You must tell the operating system which board to unbind the communication protocol from.If you have multiple boards, you must unbind each one separately.If you do not include driver_parameter at the command line, the operating system prompts you for the appropriate network board.Replace driver_parameter with one or more of the following parameters. Include the parameters that make the network board unique from all other installed network boards of its type. When the driver parameter is included with the UNBIND command, the driver parameter must be enclosed in square brackets.idxid="w7852"book="_idx" docset="nw312" tidref="i1627"DMA=numberIdentifies the DMA channel the driver is using for the network board. Use the same DMA channel that you used when you loaded the driver.idxid="w7853"book="_idx" docset="nw312" tidref="i2946"INT=numberIdentifies the interrupt the driver is using for the network board. Use the same interrupt that you used when you loaded the driver.idxid="w7854"book="_idx" docset="nw312" tidref="i3782"MEM=numberIdentifies the memory address the driver is using for the network board. Use the same memory address that you used when you loaded the driver.idxid="w7855"book="_idx" docset="nw312" tidref="i2691"PORT=numberIdentifies the I/O port the driver is using for the network board. Use the same I/O port that you used when you loaded the driver.idxid="w7856"book="_idx" docset="nw312" tidref="i6351"SLOT=numberIdentifies the network board by the slot that the network board was installed in. This parameter is used by microchannel and EISA computers. Use the same slot number that you used when you loaded the driver.ID="FM83654"Unbind a Protocol from a DriverThe steps for unbinding a protocol from a driver vary with how the driver has been loaded. Select the example that fits your situation.Driver Loaded Only OnceTo unbind a protocol when the driver has only been loaded once, type  UNBIND IPX FROM LAN_driver<Enter>Replace LAN_driver with the name of the LAN driver you want to unbind.To prevent the driver from binding automatically when the file server is booted, delete the following line from the AUTOEXEC.NCF file:BIND IPX TO LAN_driverNET=numberFor instructions on editing the AUTOEXEC.NCF file, see IDREF="FM38546""Edit the AUTOEXEC.NCF File" on page 82.Driver Loaded More Than OnceWhen you have loaded the driver more than once, you need to tell the operating system which board you want to unbind the protocol from.Specify the board by including parameters or by selecting the board from a list. Complete one of the following (these examples show how to unbind the NE2000 driver from IPX):Type the command and include the driver parameters in brackets:  UNBIND IPX FROM NE2000 [INT=4] <Enter>Type the command without the driver parameters:  UNBIND IPX FROM NE2000 <Enter>The operating system will list the network boards installed in your file server. Enter the number of the board.To prevent the driver from binding automatically when the file server is booted, delete the following line from the AUTOEXEC.NCF file:BIND IPX TO NE2000 [INT=4] NET=26For instructions on editing the AUTOEXEC.NCF file, see IDREF="FM38546""Edit the AUTOEXEC.NCF File" on page 82.ID="FM90834"Change idxid="w7857"book="_idx" docset="nw312" tidref="i2107"the Network Number for the CablingProcedureID="FM75479"At the console prompt of the file server, type  UNBIND IPX FROM LAN_driver<Enter>Replace LAN_driver with the name of the LAN driver whose network number you want to change.Type  BIND IPX TO LAN_driver<Enter>Replace LAN_driver with the name of the LAN driver you used in IDREF="FM75479"Step 1.When prompted for the network number, type in the new network number.ID="FM64671"Load INSTALL and edit the network number in the AUTOEXEC.NCF file. For information on editing the AUTOEXEC.NCF file, see IDREF="FM38546""Edit the AUTOEXEC.NCF File" on page 82.ID="FM53575"UNLOADWhy Use idxid="w7858"book="_idx" docset="nw312" tidref="i3278"UNLOAD idxid="w7859"book="_idx" docset="nw312" tidref="i7078"?Use idxid="w7860"book="_idx" docset="nw312" tidref="i2127"UNLOAD idxid="w7861"book="_idx" docset="nw312" tidref="i2119"to unload a idxid="w7862"book="_idx" docset="nw312" tidref="i4306"loadable module that was previously loaded with the LOAD command. When the module is unloaded, all resources are returned to the operating system.Use UNLOAD to unload old drivers so that updated drivers can be loaded.Read "Additional Information" before unloading any modules.The following tasks are described in this section:WIDTH="264"TaskWIDTH="48"PageWIDTH="264"Unload a loadable moduleWIDTH="48"IDREF="FM76547"335Troubleshooting UNLOADIDREF="FM17872"335Command Format  UNLOAD loadable_moduleReplace loadable_module with the name of the module you want to unload.ID="FM45961"Additional InformationRead the following information before unloading LAN drivers, name space, or disk drivers.LAN idxid="w7863"book="_idx" docset="nw312" tidref="i3085"DriversWhen you unload a LAN driver, the driver is automatically unbound from all communication protocols and removed from all network boards to which the driver has been linked. If the driver has been loaded more than once and you want to disable the communication on only one board, use the UNBIND command instead of the UNLOAD command.Once the LAN driver is unloaded, logged-in users who have been using the network boards to communicate with the server will lose their connections when they attempt to access the server. They will receive the following network error:  Network error on Server <fileserver>: Error receiving from network. Abort, Retry?These users should retry once to see if an alternate bridge to the file server is available on another network.If the retry produces another network error, they should wait until the LAN driver is reloaded and bound to the communication protocols. Then they should retry.These users must establish a connection within 15 minutes. If the connection is broken for more than 15 minutes, the file server watchdog will terminate the workstation's connection.If you plan to have the LAN driver unloaded for 15 minutes or longer, you should have users log out before unloading the LAN driver.Name SpaceBefore unloading name space modules, dismount all volumes that are using the module. These volumes cannot be remounted until the module is loaded again.Disk idxid="w7864"book="_idx" docset="nw312" tidref="i1561"DriversBefore unloading a disk driver, dismount all volumes stored on the hard disks connected to the controller or host bus adapter. If you fail to dismount all the volumes, the operating system will warn you that the driver is being used by mounted volumes and will list the volumes that are using the driver.If you override the warning and unload the disk driver without dismounting the volumes, the file server will automatically dismount the affected volumes. Users who are logged in will receive the following message:Volume "volume names" dismounted due to drive deactivation.ID="FM76547"Unload a Loadable ModuleBefore unloading a loadable module, read the cautions about unloading disk driver, LAN driver, and name space modules in "Additional Information," which starts on page IDREF="FM45961"333. Never unload a module that other modules depend on.To unload a module, type "UNLOAD" and the name of the module. For example, to unload MONITOR type  UNLOAD MONITOR <Enter>IDREF="FM19779"See also "LOAD" and IDREF="FM90371""MODULES."ID="FM17872"Troubleshooting UNLOADWhen a module is unloaded, sometimes you see a warning message, the module refuses to unload the module, or the system abends. Possible causes and solutions are described here.Warning Messages are DisplayedIf the loadable module did not return all its resources when it unloaded, a message similar to the following appears:  <module name> -Alloc Memory <resource tag> did not release <number> Alloc Short Tern Memory <resource> BytesContact the vender for an updated version of the module.Module Will Not UnloadSome modules depend on other modules to define variables. For example, RSPX depends on REMOTE. If you try to unload REMOTE before unloading RSPX, the following message appears:  Unable to unload module REMOTE.NLM (error 2)RSPX must unload before REMOTE can load. Check with the documentation that came with the loaded modules. (Use MODULES to list the currently loaded modules.) Determine which module is using the module you are trying to unload.File Server idxid="w7865"book="_idx" docset="nw312" tidref="i6910"AbendsIf the file server abends when you unload a module, do not load that module again. The module failed to return allocated resources correctly to the operating system. Check with the developer for an upgraded version of the module.UPSWhy Use idxid="w7866"book="_idx" docset="nw312" tidref="i3300"UPS?Use idxid="w7867"book="_idx" docset="nw312" tidref="i4916"UPS when you attach an idxid="w7868"book="_idx" docset="nw312" tidref="i7105"uninterruptible power supply (UPS) to your file server. idxid="w7869"book="_idx" docset="nw312" tidref="i7098"UPS idxid="w7870"book="_idx" docset="nw312" tidref="i2127"is the software link between the file server and the idxid="w7871"book="_idx" docset="nw312" tidref="i7105"UPS device connected to the file server.The UPS loadable module must be loaded to activate UPS monitoring.Command Format  LOAD [path]UPS [type port discharge recharge]Command ParametersReplace path with a full path. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path and volume SYS: is mounted, the operating system assumes that the loadable module is in the SYS:SYSTEM directory. (Use SEARCH to set up additional paths for automatic searching.)The parameters are explained here. If you do not enter the parameters at the command line, you will be prompted for them.ID="FM79765"type= nameReplace name with the name of the interface board for your UPS:DCBEDCBSTANDALONEKEYCARDMOUSE OTHERDefault: DCBIf you enter STANDALONE and the software does not accept the name, try entering KEYCARD. If you allow the software to prompt you for the parameters, follow the instructions on the screen.ID="FM27752"idxid="w7872"book="_idx" docset="nw312" tidref="i2691"port = numberReplace number with a hexadecimal number corresponding to the jumper setting on the board.DCB---346, 34E, 326, 32E, 286, 28EEDCB---380, 388, 320, 328Keycard---230, 238Mouse (no port number required)Other (see accompanying board documentation)Standalone---240, 231discharge = numberReplace number with an estimate of the number of minutes the network can operate on idxid="w7873"book="_idx" docset="nw312" tidref="i7098"battery power before depleting the battery. Consult the idxid="w7874"book="_idx" docset="nw312" tidref="i7098"battery's idxid="w7875"book="_idx" docset="nw312" tidref="i7098"documentation for time estimates. You may need to reduce the discharge time as your UPS becomes older.idxid="w7876"book="_idx" docset="nw312" tidref="i7098"recharge = numberReplace number with an estimate of the minutes the battery will need to recharge after the network has been on battery power. You may need to increase the recharge time as your UPS becomes older.Add an idxid="w7877"book="_idx" docset="nw312" tidref="i7105"Uninterruptible Power idxid="w7878"book="_idx" docset="nw312" tidref="i2034"Supply (UPS)ProcedureInstall the UPS hardware (board and power supply) and connect the power. See the documentation that comes with the UPS and the board for appropriate jumper settings.Load the UPS module and enter the parameters in one of these two ways:Type the command, including the parameters:  LOAD UPS TYPE=DCB PORT=346 DISCHARGE=20 RECHARGE=120 <Enter>Type the command and answer the screen prompts for type, I/O port, discharge time, and recharge time:  LOAD UPS <Enter>To load UPS automatically whenever the file server is booted, add the command to the AUTOEXEC.NCF file. For example, to load UPS with a DCB, add the following line:  LOAD UPS TYPE=DCB PORT=346 DISCHARGE=20 RECHARGE=120idxid="w7879"book="_idx" docset="nw312" tidref="i6910"idxid="w7880"book="_idx" docset="nw312" tidref="i7105"Troubleshooting UPSYou must configure the controller to match the UPS that you have. If the configuration does not match the UPS hardware, the driver may either fail to load or function incorrectly when loaded. One of the following could cause the driver to fail or to function incorrectly:The controller's configuration is different from the configuration you entered as you loaded UPS. Check the configuration of the controller and enter the correct port.The jumpers controlling online and offline status do not agree with the configuration on the UPS. For example, if the jumpers are set incorrectly, the UPS will signal the file server that it is on battery power when commercial power is still on. Change the jumpers on the controller to match the UPS.We recommend that you test the UPS functionality by unplugging the power and waiting 20 seconds to see if the commercial "power off" message appears.This test should be run only after all users have logged out and all LAN and disk drivers have been unloaded. Unloading the LAN and disk drivers protects your data from corruption if the UPS fails to function correctly.UPS STATUSWhy Use idxid="w7881"book="_idx" docset="nw312" tidref="i2127"UPS STATUS idxid="w7882"book="_idx" docset="nw312" tidref="i7110"?Use UPS STATUS to check the idxid="w7883"book="_idx" docset="nw312" tidref="i7098"uninterruptible power supply (UPS) attached to the file server.If the UPS module has not been loaded, executing UPS STATUS gives you the error "??? Unknown command???"Command Format  UPS STATUSCheck Power Supply StatusTo check the status of your uninterruptible power supply, type  UPS STATUS <Enter>A screen similar to the following appears:LBL="1-45""UPS Status" screenFILE="n312sa95.pbm"Each of the lines on the screen is explained here. To change the time parameters, IDREF="FM91812"see "UPS TIME."Power being used. The UPS is using either commercial power or battery power.Discharge time requested/remaining. The idxid="w7884"book="_idx" docset="nw312" tidref="i7098"first number is an estimate of the time that the network can run safely on battery power.The second number is the safe time remaining if the network is currently on battery power. If the network is running on commercial power and the battery is charged, this number is the same as the first number.Battery status. The battery is either recharged, low, or being recharged.If the battery status is low, the battery should be repaired or replaced.Recharge time requested/remaining. The first number is an estimate of the time that the battery needs to recharge after the battery has been totally discharged.The second number is an estimate of the time needed to recharge the battery.If the network is running on commercial power, the time needed to recharge the battery is 0 if the battery is fully charged.If the network is running on battery power, this number increases as the battery is discharged. The number indicates the time the battery needs to recharge.Current network power status. This field shows one of the following:WIDTH="120"NormalWIDTH="192"Running on commercial power.Server downRunning on battery power.Server going downRunning on battery power; enough in  __ minutespower is left to run the  network for the indicated number of  minutes.ID="FM91812"UPS TIMEWhy Use idxid="w7885"book="_idx" docset="nw312" tidref="i7112"UPS TIME?Use idxid="w7886"book="_idx" docset="nw312" tidref="i2127"UPS TIME to change the amount of time you want to allow the network to function on battery power and the time you estimate the battery idxid="w7887"book="_idx" docset="nw312" tidref="i7098"needs to fully recharge.This command is only valid if the UPS loadable module has been loaded.If the UPS module has not been loaded, executing UPS TIME gives you the error "??? Unknown command???"Command Format  UPS TIME [discharge recharge]Command ParametersID="FM20454"discharge = nidxid="w7888"book="_idx" docset="nw312" tidref="i7105"Replace discharge with an estimate of the number of minutes the network can operate on battery power before depleting the battery. Consult the battery's documentation for time estimates. You may need to reduce the discharge time as your UPS grows older.recharge = nReplace recharge with an estimate of the minutes needed to recharge the battery after the network has been on battery power.Consult the battery's documentation for time estimates. You may need to increase the recharge time as your UPS grows older.Change the UPS Discharge and Recharge TimesEnter the parameters for the discharge and recharge times in one of the following ways:Type the command and include the parameters:  UPS TIME DISCHARGE=20 RECHARGE=120 <Enter>Type the command and answer the prompts for discharge time and recharge time:  UPS TIME <Enter>VERSIONWhy Use idxid="w7889"book="_idx" docset="nw312" tidref="i7294"VERSION idxid="w7890"book="_idx" docset="nw312" tidref="i2127"?Use idxid="w7891"book="_idx" docset="nw312" tidref="i7289"VERSION to display the file server's idxid="w7892"book="_idx" docset="nw312" tidref="i6396"version information and copyright idxid="w7893"book="_idx" docset="nw312" tidref="i1260"notice.Command Format  VERSIONView Version Information and Copyright NoticeTo view the file server version information and copyright notice, type  VERSION <Enter>A message similar to the following appears:  Novell NetWare 386 v3.12 9/3/93  (c) Copyright 1988, 1993 Novell, Inc.  All rights reserved.VOLUMESWhy Use idxid="w7894"book="_idx" docset="nw312" tidref="i7411"VOLUMESUse idxid="w7895"book="_idx" docset="nw312" tidref="i2127"VOLUMES to list the volumes currently idxid="w7896"book="_idx" docset="nw312" tidref="i7372"mounted on the idxid="w7897"book="_idx" docset="nw312" tidref="i2111"file server.Command Format  VOLUMESView Mounted VolumesTo view a list of volumes on the file server, type  VOLUMES <Enter>A message similar to the following appears:  The following volumes are mounted:  SYS  MACID="FM32162"VREPAIRWhy Use idxid="w7898"book="_idx" docset="nw312" tidref="i7415"VREPAIR idxid="w7899"book="_idx" docset="nw312" tidref="i3300"?Use idxid="w7900"book="_idx" docset="nw312" tidref="i2127"VREPAIR to correct volume problems or to remove name space entries from File Allocation Tables and Directory Entry Tables.If you upgrade to NetWare v3.12 from another version and then need to return to that version, make sure you use the version of VREPAIR that matches the operating system.The following tasks are described on the pages indicated:WIDTH="264"TaskWIDTH="48"PageWIDTH="264"Repair a volume or remove name space entriesWIDTH="48"IDREF="FM54869"350Set VREPAIR optionsIDREF="FM62024"352Command Format  LOAD [path]VREPAIRCommand ParametersReplace path with a full path to the directory containing VREPAIR. Begin with a DOS drive letter or a NetWare volume name. If you do not specify a path and volume SYS: has been mounted, the operating system assumes that the VREPAIR loadable module is located in the SYS:SYSTEM directory.Additional InformationVREPAIR comes on the NetWare Operating System-2 diskette. Copy VREPAIR.NLM and the VREPAIR name space support modules (V_namespace.NLM) to the boot partition of your file server. Then, if volume SYS: fails to mount, you can load VREPAIR and run it from the boot directory.idxid="w7901"book="_idx" docset="nw312" tidref="i1309"Minor idxid="w7902"book="_idx" docset="nw312" tidref="i5752"problems idxid="w7903"book="_idx" docset="nw312" tidref="i7549"idxid="w7904"book="_idx" docset="nw312" tidref="i2599"can idxid="w7905"book="_idx" docset="nw312" tidref="i6910"occur if the primary File Allocation Table ( idxid="w7906"book="_idx" docset="nw312" tidref="i1969"FAT) or idxid="w7907"book="_idx" docset="nw312" tidref="i1517"Directory Entry Table (DET) becomes corrupted. VREPAIR compares the primary tables with their mirrored counterparts. (The operating system keeps two copies of all tables. If hard disks are mirrored, then four copies are kept.) VREPAIR checks the sets of tables for errors and uses the most correct table entry as the corrected entry. VREPAIR then writes the corrected entry to both the primary and mirrored tables. VREPAIR may have to delete some corrupted files or tables.Use VREPAIR in these situations:A hardware failure has either prevented a idxid="w7908"book="_idx" docset="nw312" tidref="i7372"volume from mounting or caused a disk read error.A power failure has corrupted a volume.The file server console displays a mirroring error when the server boots.The file server displays memory errors and cannot mount a volume after a name space (such as Macintosh) has been added to the volume. You must either add more memory to the file server or remove the newly added name space. For instructions, see IDREF="FM62024""Set VREPAIR Options" on page 352.The following kinds of errors in FATs or DETs signal bad blocks:Data mirror mismatch errors Fatal DIR errors Read errorsMultiple allocation errorsWrite errorsVREPAIR can run on a bad volume that you have dismounted while other file server volumes are functioning. After you finish running VREPAIR, you can mount the repaired volume (in most cases idxid="w7909"book="_idx" docset="nw312" tidref="i6910").ID="FM54869"Repair a Volume or Remove Name Space EntriesTypically, you cannot mount a volume if it has had even minor damage. Occasionally the volume mounts but causes an error in the process. Complete these steps to repair the volume.ProcedureIf the volume you want to repair is mounted, refer to "Connection Information" on the "Available Options" screen in MONITOR to check for users who have open files on the volume you need to dismount. Use BROADCAST or SEND to warn these users to close their files and move to another volume.Dismount the volume.  DISMOUNT volume_name<Enter>Replace volume_name with the volume you need to repair.Do one of the following:If volume SYS: is mounted, type  LOAD VREPAIR <Enter>If volume SYS: is not mounted, set a path to VREPAIR.NLM and the name space support modules. (IDREF="FM80203"See "SCAN FOR NEW DEVICES" on page 245.)Check the VREPAIR options. You can use these options to control whether name space information is deleted and how FAT and DET information is written to disk. (IDREF="FM62024"See "Set VREPAIR Options" on page 352.)Select "Repair A Volume" from the "Options" menu.If more than one volume is not mounted, select the volume to be repaired from those listed. If only one volume has been dismounted, a screen similar to the following appears:  Total errors:  Current settings:  Pause after each error  Do not log errors to a file  Press F1 to change settingsIf VREPAIR seems to be finding a large number of errors, you may want to change one or both of the current settings. These settings can be changed while the program is running. To set either option, press <F1>.Select Option 1 if you do not want VREPAIR to pause after each error. A screen appears, describing the error that was corrected. Press any key to continue.Select Option 2 if you want VREPAIR to log errors in a text file. Any errors found will be written to a file you specify. The repaired files may no longer be valid and may need to be restored from a backup.Select Option 3 to stop the repair of the volume.The size of the volume determines the time it takes to complete VREPAIR. If the volume is over 1000 MB, the process can take at least 30 minutes.When VREPAIR has finished running, the screen displays information similar to the following:LBL="1-46"VREPAIR information screenFILE="n312sa99.pbm"Answer "Yes" to the prompt to write repairs to the disk.Press any key to return to the "Options" menu.Type "0" to exit.If you are unable to mount the volume after running VREPAIR, you must delete the volume, recreate the volume using INSTALL, and restore the data from a backup file.ID="FM62024"Set VREPAIR OptionsTo change an option, complete the following stepsProcedureLoad VREPAIR by typing  LOAD VREPAIR <Enter>If volume SYS: is not mounted, include a path to VREPAIR.NLM.Type the number for "Set VREPAIR Options" and press <Enter>.Type the number of the option you want to change and press <Enter>. See "Available Options" below for a description.Answer the confirmation prompts.The new setting is displayed in the "Current Vrepair Configuration" list. For instructions on how to repair a volume, see IDREF="FM54869""Repair a Volume or Remove Name Space Entries" on page 350.Available OptionsThis section describes the options available in VREPAIR.idxid="w7910"book="_idx" docset="nw312" tidref="i3992"Remove Name Space Support from the Volume/ Quit If A VREPAIR Name Space Support NLM Is Not LoadedThese options control whether name space support for non-DOS files is retained in the volume tables. If you have added a name space to a volume and the operating system no longer has enough memory to mount the volume, select "Remove Name Space support from the volume." Then select the name space you want to delete. To be successful in deleting the name space entries, VREPAIR must be able to find the name space support module (V_namespace.NLM).If you remove a name space, the accompanying extended file information is destroyed. For example, if you remove Macintosh name support, the Macintosh long names, the finder icons, and the resource forks are destroyed. (The DOS name and its data file are kept and are accessible from DOS workstations.)Default: Quit If a Vrepair Name Space Support NLM Is Not LoadedWrite Only Changed Directory and FAT Entries Out to Disk/ Write All Directory and FAT Entries Out to DiskThese options control the changes that are made to the FATs and Directory Entry Tables. The first time you attempt to repair a volume, write only the changes to disk.If the first attempt fails to repair the volume and the volume resides on mirrored disks, select "Write All Directory and FAT Entries Out to Disk" to force the tables on both hard disks to be updated. Do not use this option if the file server crashed during the updating of important files. Instead, for other possible solutions, see IDREF="FM44189""A Volume Cannot Be Mounted Because of Corrupted Directory Entry Tables or Fats." on page 419.Default: Write Only Changed Directory and FAT Entries Out to DiskKeep Changes in Memory for Later Update / Write Changes Immediately to DiskWhen only a few errors need to be corrected, VREPAIR runs faster by saving all changes in memory and then writing them to disk at the end. However, VREPAIR runs very slowly when more than 1,000 changes have to be kept in memory. The memory needed to store the changes can also cause the file server to run out of memory.Select "Keep Changes in Memory for Later Update" if the volume problem occurred when only a few users were updating files.Select "Write Changes Immediately to Disk" if the volume problem occurred during peak usage or if you are removing name space entries.Default: Keep Changes in Memory for Later Update.LBL="2"ID="FM34471"Remote ManagementOverviewidxid="w7911"book="_idx" docset="nw312" tidref="i5817"The information idxid="w7912"book="_idx" docset="nw312" tidref="i5802"in this idxid="w7913"book="_idx" docset="nw312" tidref="i2096"section idxid="w7914"book="_idx" docset="nw312" tidref="i2034"has been organized into the following sections:Overview IDREF="FM30068"(page 355). This section explains what remote management is, who can use it, and how it works. It also explains the different types of communication links that can be set up using remote management.Setting up remote management IDREF="FM27961"(page 363). This section explains the hardware and software requirements of remote management and gives procedures for the following:Adding remote capability to a NetWare v3.1x file server IDREF="FM27565"(page 365).Adding remote capability to a standalone PC IDREF="FM72274"(page 367).Using a idxid="w7915"book="_idx" docset="nw312" tidref="i5802"remote console IDREF="FM36233"(page 367). This section discusses activating and using the remote console. Menus and function keys specific to the remote console program are explained. This section also contains instructions for remote administration tasks that can be completed from the remote console's "Available Options" menu. IntroductionNetWare's remote management capability was developed as the NetWare idxid="w7916"book="_idx" docset="nw312" tidref="i5818"Remote Management Facility (RMF). Remote management allows you to idxid="w7917"book="_idx" docset="nw312" tidref="i6001"manage all of your NetWare file servers (v3.1 and later) from one location. It gives you easier access to and greater control of the file servers, no matter where those servers are located.After setting up a remote console at a workstation, you can see and control all the file servers that have the appropriate remote management software loaded.You have greater control of file server security when you use remote management. Because a workstation can act as a file server console, you can remove the keyboard and monitor from your file server, or you can lock the file server in an area where you can control access.Remote management works idxid="w7918"book="_idx" docset="nw312" tidref="i6001"with NetWare v3.1x operating system software. It can cross all NetWare links and work with all certified NetWare platforms and DOS workstations.When you establish a communication link to a file server, you can perform the following functions:Use console commands as you would at the file server console.Scan directories and edit text files in both DOS and NetWare partitions on a remote file server.Transfer files to (but not from) a remote file server.Add an existing NetWarev3.1x file server to an established remote management network.Reboot a file server from a remote console.Who Can Use Remote Management?For security reasons, only NetWare supervisors and remote console operators can use remote management.These users must have appropriate rights and must pass password security checks before they can access a file server from a remote console. The remote console does not disable or bypass the MONITOR idxid="w7919"book="_idx" docset="nw312" tidref="i3059"keyboard lock. If this lock is set, you must enter the password to gain access. A remote idxid="w7920"book="_idx" docset="nw312" tidref="i1223"console operator uses a idxid="w7921"book="_idx" docset="nw312" tidref="i5796"remote password to open a communication session with a file server. The remote console operator must have File Scan and Read idxid="w7922"book="_idx" docset="nw312" tidref="i5995"rights in SYS:SYSTEM. After successfully passing security checks, the operator can perform the tasks described in this manual and execute console commands.A NetWare idxid="w7923"book="_idx" docset="nw312" tidref="i6595"supervisor can open a remote console session using either the remote or the supervisor idxid="w7924"book="_idx" docset="nw312" tidref="i4980"password. However, volume SYS: must be mounted in order for the supervisor password to work. Although the supervisor password allows remote access to a file server, only remote management tasks can be performed. A NetWare supervisor cannot create users or assign rights from a remote console.How Does Remote Management Work?Remote management establishes a communication link with a file server. This enables a workstation or standalone PC to act as a file server console, or "remote idxid="w7925"book="_idx" docset="nw312" tidref="i5796"console."The software that manages the remote console does not disable the regular console keyboard. Remote management supports idxid="w7926"book="_idx" docset="nw312" tidref="i1110"concurrent idxid="w7927"book="_idx" docset="nw312" tidref="i1204"connections to a file server. This feature is helpful for training both inexperienced file server supervisors and managers. It is also helpful for troubleshooting.For example, a remote console operator can open a communication session with a file server and enter commands to help a local supervisor. Both users can enter keystrokes, and both the file server screen and the remote console screen display file server information.The remote console does not need to remain dedicated until a process is completed. After a server process is initiated, the remote console can terminate the session without affecting the process.IDREF="FM47003"Figure 2-1 shows the software needed for remote management. Following the figure are more detailed descriptions of the software.LBL="2-1"ID="FM47003"Software necessary for remote managementFILE="n312sa1a.pbm"File Server Software for Remote ManagementBoth file server and workstation software are needed for remote management. Files with an .NLM extension are loaded from the file server.idxid="w7928"book="_idx" docset="nw312" tidref="i5813"REMOTE.NLM. This loadable module manages the reception and transmission of keyboard and monitor information to and from the communications drivers.idxid="w7929"book="_idx" docset="nw312" tidref="i6089"RSPX.NLM. This loadable module is a media-specific idxid="w7930"book="_idx" docset="nw312" tidref="i1064"communications driver that provides SPX support for REMOTE.NLM. This module also advertises that the file server is available for remote access.idxid="w7931"book="_idx" docset="nw312" tidref="i6084"RS232.NLM. This loadable module is an asynchronous communications driver that initiates the file server's communication port and transfers screen and keystroke information to and from REMOTE.NLM.ID="FM96208"Workstation Software for Remote ManagementFiles with an .EXE extension are loaded from the workstation.idxid="w7932"book="_idx" docset="nw312" tidref="i123"ACONSOLE.EXE. This utility works like many standard communication programs in that it allows control of a client modem (to dial, hang up, etc.). This utility also controls the transfer of screen and keystroke information to and from the remote file server.idxid="w7933"book="_idx" docset="nw312" tidref="i5747"RCONSOLE.EXE. This utility is a communication program that turns a workstation into a remote console. This utility also controls the transfer of screen and keystroke information to and from the remote file server.What Types of Communication Links Can I Set Up?You can establish three types of connections with file servers on local and wide area networks:Direct link. Set up a direct link to file servers physically attached to your network through an internetwork cable or T1 line.Asynchronous link. Attach asynchronously to a file server at a remote location, such as a wide area network, using a modem. Redundant link. Establish redundant links, which are both direct and asynchronous connections to the same file server. These connections are explained in further detail in the following sections.idxid="w7934"book="_idx" docset="nw312" tidref="i1204"Direct idxid="w7935"book="_idx" docset="nw312" tidref="i1064"Link idxid="w7936"book="_idx" docset="nw312" tidref="i1445"One way to establish a remote session with a file server is by using a direct connection link. This works for file servers on a local or wide area network, where the servers are connected by cabling or by a T-link using IPX/SPX protocol.In IDREF="FM61364"Figure 2-2, "Remote session using a direct link," the file servers are part of an internetwork connected by cabling. The workstation acting as a remote console can log in to a file server on a LAN and then open a communication idxid="w7937"book="_idx" docset="nw312" tidref="i6275"session with a remote server across the internetwork.LBL="2-2"ID="FM61364"Remote session using a direct linkFILE="n312sa1b.pbm"idxid="w7938"book="_idx" docset="nw312" tidref="i476"Asynchronous LinkAnother way of establishing a remote idxid="w7939"book="_idx" docset="nw312" tidref="i6275"session is through modems. You can use this type of idxid="w7940"book="_idx" docset="nw312" tidref="i1064"idxid="w7941"book="_idx" docset="nw312" tidref="i1204"connection to open a communication session with a file server on a different internetwork.In IDREF="FM84332"Figure 2-3, the workstation acting as a remote console can log in to the file server on the LAN and then dial the remote file server modem.LBL="2-3"ID="FM84332"Remote session using an asynchronous link (via a file server)FILE="n312sa1c.pbm"You can also establish an asynchronous session using a standalone PC. You do not have to connect through a file server on a LAN.In IDREF="FM59436"Figure 2-4, a standalone PC with a modem has an asynchronous connection to a file server with a modem.LBL="2-4"ID="FM59436"Remote session using an asynchronous link (via a standalone PC)FILE="n312sa1d.pbm"Redundant idxid="w7942"book="_idx" docset="nw312" tidref="i5776"idxid="w7943"book="_idx" docset="nw312" tidref="i6275"LinkYou also have the option of setting up redundant idxid="w7944"book="_idx" docset="nw312" tidref="i1064"communication links to a file server. The term redundant link means that you set up both direct and asynchronous connections to a file server. Redundant links are possible because the software for a direct link and a modem link can coexist on a file server.This type of setup has certain advantages. For example, if a LAN driver or disk driver is unloaded, or if volume SYS: is dismounted, a direct communication link will be lost. The network supervisor or remote console operator can open an asynchronous session with the file server and reboot the server.In IDREF="FM91912"Figure 2-5, the remote console can open either a direct or an asynchronous communication session with the file server.LBL="2-5"ID="FM91912"Remote session using a redundant linkFILE="n312sa1e.pbm"ID="FM27961"Setting Up idxid="w7945"book="_idx" docset="nw312" tidref="i5747"Remote ManagementBefore you set up remote management, be sure your hardware and software meet the requirements listed in this section. To use a remote console to manage a network, you must load appropriate software on a workstation or standalone PC and on the file servers you want to access.To prevent idxid="w7946"book="_idx" docset="nw312" tidref="i6177"unauthorized access to file servers, you should keep remote management idxid="w7947"book="_idx" docset="nw312" tidref="i6177"software, particularly idxid="w7948"book="_idx" docset="nw312" tidref="i5747"RCONSOLE.EXE and ACONSOLE.EXE, in your SYSTEM directory.Two setup options are described in this section. Review the choices carefully and follow the instructions for the situation that applies to you.Adding remote capability to a NetWare v3.1x file server IDREF="FM27565"(page 365)Adding remote capability to a standalone PC IDREF="FM72274"(page 367).Hardware idxid="w7949"book="_idx" docset="nw312" tidref="i2640"and idxid="w7950"book="_idx" docset="nw312" tidref="i6001"Software Requirements for idxid="w7951"book="_idx" docset="nw312" tidref="i6001"Remote ManagementIn order to run remote management software, file servers and workstations or standalone PCs must meet the following requirements.ID="FM30556"File Server RequirementsThe idxid="w7952"book="_idx" docset="nw312" tidref="i2034"hardware requirements for a file server include the following:386- or 486-based microcomputer48 KB of available idxid="w7953"book="_idx" docset="nw312" tidref="i3758"memory to run NLMsA Hayes-compatible idxid="w7954"book="_idx" docset="nw312" tidref="i667"modem idxid="w7955"book="_idx" docset="nw312" tidref="i3922"capable of communicating at 2400, 4800, or 9600 baud (for asynchronous connections)idxid="w7956"book="_idx" docset="nw312" tidref="i6396"Software requirements for the idxid="w7957"book="_idx" docset="nw312" tidref="i2034"file server include the following:NetWare v3.0 or laterIPX/SPX network protocolsID="FM69353"Workstation idxid="w7958"book="_idx" docset="nw312" tidref="i7493"RequirementsHardware requirements for workstations or idxid="w7959"book="_idx" docset="nw312" tidref="i6472"standalone PCs include the following:Novell-tested and - approved computer typeNovell-tested and - approved network adapter boardsAt least 200 KB of memoryA Hayes-compatible modem capable of communicating at 2400, 4800, or 9600 baud (for asynchronous connections)idxid="w7960"book="_idx" docset="nw312" tidref="i7493"Workstation or idxid="w7961"book="_idx" docset="nw312" tidref="i6472"standalone PCs must be running idxid="w7962"book="_idx" docset="nw312" tidref="i1638"DOS 2.x or later.ID="FM27565"Adding Remote idxid="w7963"book="_idx" docset="nw312" tidref="i6001"Capability to a NetWare idxid="w7964"book="_idx" docset="nw312" tidref="i2869"v3.1x File ServerThese instructions are for adding remote management capability to a file server running NetWare v3.1x. They do not apply to new file servers or to file servers running v3.0 or earlier.In order for you to load the modules discussed in this section, they must be on the file server to which you want to add remote capability. If you have not already done so, copy the appropriate files to the server. For file server security, you should keep remote management files in the SYS:SYSTEM directory.If you want the modules for remote console access to be loaded automatically each time the file server is booted, place the commands discussed in this section in an AUTOEXEC.NCF file. The only condition is that the idxid="w7965"book="_idx" docset="nw312" tidref="i595"AUTOEXEC.NCF file must load REMOTE.NLM first.ID="FM71481"Load idxid="w7966"book="_idx" docset="nw312" tidref="i5813"REMOTE.NLMFor idxid="w7967"book="_idx" docset="nw312" tidref="i5640"all types of connection links, you must load REMOTE.NLM. Type  LOAD [path]REMOTE [password] <Enter>If REMOTE.NLM is in the SYS:SYSTEM directory, you do not need to specify a path. If the module is in a different directory, replace path with the directory path where the module is located. Begin with a DOS drive letter or a NetWare volume name.Replace idxid="w7968"book="_idx" docset="nw312" tidref="i5813"password with a unique idxid="w7969"book="_idx" docset="nw312" tidref="i4980"password to be used by the remote console operator (up to 47 idxid="w7970"book="_idx" docset="nw312" tidref="i4980"characters). If you do not enter a password, you will be prompted for one.Load idxid="w7971"book="_idx" docset="nw312" tidref="i6089"idxid="w7972"book="_idx" docset="nw312" tidref="i1445"RSPX.NLMIf you want to access a file server by a direct communication link, you must load RSPX.NLM after you load REMOTE.NLM.Type  LOAD [path]RSPX <Enter>If RSPX.NLM is in the SYS:SYSTEM directory, you do not need to specify a path. If RSPX.NLM is in a different directory, replace path with the directory path where the module is located. Begin with a DOS drive letter or a NetWare volume name.Load idxid="w7973"book="_idx" docset="nw312" tidref="i6084"RS232.NLMIf you want the file server to be accessible to idxid="w7974"book="_idx" docset="nw312" tidref="i476"asynchronous connection links, you must load RS232.NLM after you idxid="w7975"book="_idx" docset="nw312" tidref="i3922"load REMOTE.NLM.idxid="w7976"book="_idx" docset="nw312" tidref="i667"Type  LOAD [path]RS232 [commport] [modemspeed] <Enter>If RS232.NLM is in the SYS:SYSTEM directory, you do not need to specify a path. If RS232.NLM is in a different directory, replace path with the directory path where the module is located. Begin with a DOS drive letter or a NetWare volume name.idxid="w7977"book="_idx" docset="nw312" tidref="i6084"Replace comm port with the communications port number (1 or 2). If you do not enter this number when entering the LOAD command, you will be prompted to enter it.Replace modem speed with the baud rate (2400, 4800, or 9600). If you do not enter the modem speed when entering the LOAD command, you will be prompted to select a baud rate.ID="FM11853"Where to Go from HereThe file server can now be accessed using a remote console. For instructions, IDREF="FM36233"see "Using a Remote Console" on page 367.ID="FM72274"Adding Remote Capability to a Standalone PCYou can use a idxid="w7978"book="_idx" docset="nw312" tidref="i5033"standalone idxid="w7979"book="_idx" docset="nw312" tidref="i6472"PC as a remote console if the required software is copied to a directory on the PC.Create a directory on the standalone PC's hard disk and copy the following idxid="w7980"book="_idx" docset="nw312" tidref="i2300"files to that directory:ACONSOLE.EXERCONSOLE.HLPIBM$RUN.OVLCMPQ$RUN.OVL$RUN.OVLSYS$ERR.DATSYS$HELP.DATSYS$MSG.DATWith these files on your standalone PC, you can activate a remote console and open an asynchronous communication session with a file server by following the instructions IDREF="FM16261"in "Activating ACONSOLE from a Network Station," beginning on page 369.ID="FM36233"Using a Remote ConsoleThe tasks described in this section apply to file servers with remote console software loaded. If you have not yet set up your remote system, read the information in IDREF="FM27961""Setting Up Remote Management" on page 363.This section explains how to activate a remote console session and how to access and use the remote console menus and screens.The following tasks are explained:Activate RCONSOLE from a network workstation (beginning this page). Activate ACONSOLE from a network workstation IDREF="FM11052"(page 368).Activate ACONSOLE from a standalone PC IDREF="FM87877"(page 371).Exit from a remote console after closing a file server session IDREF="FM41038"(page 372).ID="FM11052"Activating RCONSOLE from a Network WorkstationTo idxid="w7981"book="_idx" docset="nw312" tidref="i5796"open a connection using RCONSOLE, you must first log in to a file server on your network. Then you use idxid="w7982"book="_idx" docset="nw312" tidref="i5807"RCONSOLE idxid="w7983"book="_idx" docset="nw312" tidref="i5747"to idxid="w7984"book="_idx" docset="nw312" tidref="i5796"connect to the remote file server.RCONSOLE also works through communication servers such as the Novell Access Server.ProcedureFrom a workstation, log in to the local network file server as SUPERVISOR.If you do not have a idxid="w7985"book="_idx" docset="nw312" tidref="i6168"search drive mapped to the directory containing the remote console files (usually SYS:SYSTEM), type  MAP S16:=SYS:SYSTEM <Enter>Activate RCONSOLE by typing  RCONSOLE <Enter>The "Available Servers" list appears, showing the file servers on your network that have REMOTE and RSPX loaded.Select the file server you want from the "List of Available Servers" window and press <Enter>.When the "Password" window appears, log in to the remote server in one of the following ways:Enter the remote password for the remote file server. Enter the SUPERVISOR password. This will work only if volume SYS: is mounted.After a few moments, one of the following appears:The MONITOR screen (if MONITOR is loaded on the file server with the keyboard lock option)An active file server screen The remote system console screen (:) If the "Keyboard Lock Password" prompt appears, enter the MONITOR password and press <Enter>.The remote console session is now open. You can see file server screens and use the remote console options as specified in IDREF="FM92370""Using the Remote Console for Administrative Tasks" on page 372.ID="FM16261"Activating idxid="w7986"book="_idx" docset="nw312" tidref="i123"ACONSOLE idxid="w7987"book="_idx" docset="nw312" tidref="i5807"from a idxid="w7988"book="_idx" docset="nw312" tidref="i5807"Network StationBoth the workstation and file server must have modems connected to either a COM1 or COM2 port.You open this connection by logging in to a file server on your network. Then you use ACONSOLE to connect to the remote file server.ProcedureFrom a workstation, log in to the local network file server as SUPERVISOR.If you do not have a search drive mapped to the directory containing the remote console files (usually SYS:SYSTEM), type  MAP S16:=SYS:SYSTEM <Enter>In order for remote management to operate properly, you must map a search drive to the directory containing the remote console files.Activate ACONSOLE by typing  ACONSOLE <Enter>When the "Main Menu" appears, select "Connect to Remote Location" to access your phone list.If you have not configured the modem, or if you want to change the current modem configuration, go to IDREF="FM80516""Configuring the Modem" on page 382 and then continue here with IDREF="FM34181"Step 5.ID="FM34181"Select the appropriate file server from the phone list by pressing <Enter>.If you have not created a phone list, or if you want to change your phone list, go to IDREF="FM80516""Configuring the Modem" on page 382 and then return to this step.A "Modem Result Codes" screen appears. Messages appear on the screen to inform you of the progress of the connection attempt.When the connection is established, the "Available Servers" screen appears showing the name of the server you called.ACONSOLE idxid="w7989"book="_idx" docset="nw312" tidref="i123"does not provide a guaranteed packet delivery transport. When trying to send packets to or receive packets from a file server with extensive disk or LAN activity, ACONSOLE may "time out" when sending data to the file server or waiting for a response from the server. If so, one of the following idxid="w7990"book="_idx" docset="nw312" tidref="i4877"messages will appear in the "Modem Result Codes" idxid="w7991"book="_idx" docset="nw312" tidref="i1780"message screen:Unable to Send Request to ServerNo Response from ServerIf either message appears, press <Esc> and continue or retry the operation.Select the server and press <Enter>.When the "Password" window appears, enter one of the following passwords:The REMOTE password for the remote file server.The SUPERVISOR password. This will work only if volume SYS: is mounted at the remote server.After a few moments, one of the following screens or prompts appears:The keyboard lock password prompt (if MONITOR is loaded on the file server and the keyboard lock option has been selected)An active file server screenThe remote system console screen (:)If the keyboard lock password prompt appears, type the password and press <Enter>.The ACONSOLE session is now open. You can see file server screens and use the remote management console options as explained IDREF="FM92370"in "Using the Remote Console for Administrative Tasks" on page 372.ID="FM87877"Activating ACONSOLE from a Standalone PCTo idxid="w7992"book="_idx" docset="nw312" tidref="i6472"establish a idxid="w7993"book="_idx" docset="nw312" tidref="i5033"standalone PC as a remote console and open an asynchronous idxid="w7994"book="_idx" docset="nw312" tidref="i5033"connection, the idxid="w7995"book="_idx" docset="nw312" tidref="i5807"PC and the remote file idxid="w7996"book="_idx" docset="nw312" tidref="i6472"server must be set up as follows:Both the standalone PC and the file server must have modems. The standalone PC must be set up as explained in IDREF="FM72274""Adding Remote Capability to a Standalone PC" on page 367.The file server must be running NetWare v3.1 or later.The file server must have the REMOTE and RS232 modules loaded.After the standalone PC is set up, use ACONSOLE to open a communication session. At this point, you can perform tasks in the same way as a workstation with an asynchronous link does. ID="FM41038"Exiting the idxid="w7997"book="_idx" docset="nw312" tidref="i123"Remote ConsoleYou can exit a remote console idxid="w7998"book="_idx" docset="nw312" tidref="i5747"session from the "Available Options" menu or from the remote system console prompt.Exit from the "Available Options" MenuProcedureSelect "End Remote Session With Server."Press <Enter>.Answer "Yes" at the "Quit Remote Console Session" confirmation box.Exit from the Remote System Console PromptProcedurePress <Shift><Esc>.Press <Esc>.Answer "Yes" at the "Exit Remote Console" confirmation box.ID="FM92370"Using the Remote Console for Administrative TasksThis section describes how to use the remote console and how to perform administrative tasks. The tasks in this section are not in chronological order. This is a reference section to help you complete routine, isolated tasks. If you have not opened a remote console session, follow the instructions in IDREF="FM36233""Using a Remote Console" on page 367 before proceeding.The following tasks are explained in this section:How to use remote console screens and menus (IDREF="FM31839"page 373)How to scan file server directories in a floppy drive or on a NetWare or DOS partition IDREF="FM25131"(page 375)How to reboot a file server from a remote console IDREF="FM12248"(page 375)How to transfer files to a remote file server IDREF="FM12384"(page 376)How to add or upgrade a LAN or disk driver on a remote file server IDREF="FM45375"(page 380)How to configure a modem IDREF="FM84184"(page 382)ID="FM31839"Use Remote Management idxid="w7999"book="_idx" docset="nw312" tidref="i3064"Screens and idxid="w8000"book="_idx" docset="nw312" tidref="i6001"MenusUse the "Available Options" MenuWIDTH="120"TaskWIDTH="192"ProcedureWIDTH="120"Access the menuWIDTH="192"Press <*> on the number pad.Move down through  menu levelsPress <Enter>.Move up through menu  levelsPress <Esc>.Exit the menuPress <Esc> or <Alt><F10>.Move through Active ScreensWIDTH="120"TaskWIDTH="192"ProcedureWIDTH="120"Display the "Available  Options" menuWIDTH="192"Press <*> on the number pad.Move between active idxid="w8001"book="_idx" docset="nw312" tidref="i6151"file  server screensPress <-> or <+> on the number pad (does  not work in the "Available Options" menu).Terminate a session with  a file serverPress <Shift><Esc> until the "List of  Servers" screen reappears.See a list of active file  server screensPress <*> on the number pad to access the  "Available Options" menu, and then select  "Select a Screen to View."View an active file server  screenSelect "Select a Screen to View" from the  "Available Options" menu, and then select  the screen to view from the list of active  screens.ID="FM25131"Scan idxid="w8002"book="_idx" docset="nw312" tidref="i2034"File Server idxid="w8003"book="_idx" docset="nw312" tidref="i1475"DirectoriesProcedureFrom the "Available Options" menu, select "Directory Scan."Enter the directory you want to scan by completing one of the following:To scan a network drive, enter the path for the directory you want to see and then press <Enter>. For example, to scan the directories in the SYSTEM directory, type  SYS:SYSTEM <Enter>To scan a DOS drive, enter the drive letter and then press <Enter>.For example, to scan the DOS directories on drive C, type  C: <Enter>If the file server has only one floppy drive, do not attempt to scan directories on drive B. Specifying a logical drive will cause the workstation to hang until a keystroke is entered at the file server console.To scroll through directories, use the <PgUp> and <PgDn> keys.ID="FM12248"Reboot idxid="w8004"book="_idx" docset="nw312" tidref="i1780"a idxid="w8005"book="_idx" docset="nw312" tidref="i2034"File Server from a idxid="w8006"book="_idx" docset="nw312" tidref="i5796"Remote ConsoleYou can reboot a file server from a remote console by executing an .NCF file containing the appropriate commands.ProcedureIf the EDIT.NLM is not loaded, type  Load EDIT <Enter>Do one of the following:Create an .NCF file and include the following commands in the order given:  REMOVE DOS  DOWN  EXITIf you have already created a reboot file, go to IDREF="FM23675"Step 4.Save the file in the SYS:SYSTEM directory.ID="FM23675"At the system console prompt, enter the name of the .NCF file you created to reboot the file server.The keyboard will be disabled for a few minutes while the file is processed.When a prompt appears telling you that the connection is lost, press <Esc>.When the "List of Servers" screen appears, exit from the remote console.Open a new remote console connection with the file server.ID="FM12384"Transfer Files to a Remote idxid="w8007"book="_idx" docset="nw312" tidref="i2300"File ServerYou can idxid="w8008"book="_idx" docset="nw312" tidref="i5796"transfer files from a workstation (acting as a remote console) to a file server in several ways. Follow the procedure which best serves your needs.When reading the instructions for any of the file transfer methods, keep in mind that idxid="w8009"book="_idx" docset="nw312" tidref="i6428"source means the current location of the files that you want to transfer (where the files are being copied from), and idxid="w8010"book="_idx" docset="nw312" tidref="i6701"target means the destination of the files (where the files are being copied to). Both network drives and local hard drives can be used as sources or targets.Transfer Specific FilesUse this method to transfer individual files or all files in a directory to a remote file server. For example, you can transfer customized files or update selected SYSTEM, PUBLIC, or LOGIN files.This transfer method works with both asynchronous and direct communication sessions.To transfer files from a remote console to a target file server, open a remote console session, and then complete the following steps.ProcedureFrom the "Available Options" menu, select "Transfer Files to Server."Enter the source directory path (including wildcard characters if applicable) for the files you want to transfer.To transfer files from a diskette, type the drive letter followed by the source directory path. For example, to transfer all of the files from theSystem_1 diskette, insert the diskette into drive A: and type  A:\ <Enter>To transfer files from a network drive, type the drive letter followed by the source directory path. If the remote console has a drive mapped to the source directory, enter the drive letter and the filename or a wildcard character.For example, to transfer the RCONSOLE.EXE file from the SYS:ADMIN\UTILS directory which is mapped to drive G:, type  G:RCONSOLE.EXE <Enter>If the workstation does not have a drive mapped to the source directory, enter the complete directory path. For example, to transfer the file described above, type  SYS:ADMIN\UTILS\RCONSOLE.EXE <Enter>Enter the directory path on the target file server.To transfer files to a diskette at the file server, enter the target drive letter followed by the directory path. For example, to transfer the RCONSOLE.EXE file to drive A: in the SYSTEM directory, type  A:\SYSTEM\RCONSOLE <Enter>If the file server has only one floppy drive, do not attempt to transfer files to a logical drive (such as drive B:). Specifying a logical drive will cause the workstation to hang until a keystroke is entered at the file server console.To transfer files to a network drive, enter the target directory path.For example, to transfer the SYSTEM files to the target SYSTEM directory, type  SYS:SYSTEM <Enter>As each file is transferred to the target file server, it is listed on the remote console screen.If you want to verify that the files were transferred, follow the procedures in IDREF="FM25131""Scan File Server Directories" on page 375.ID="FM45614"Transfer idxid="w8011"book="_idx" docset="nw312" tidref="i6656"All SYSTEM and idxid="w8012"book="_idx" docset="nw312" tidref="i2869"PUBLIC idxid="w8013"book="_idx" docset="nw312" tidref="i5696"FilesUse idxid="w8014"book="_idx" docset="nw312" tidref="i7086"this method to automatically transfer all NetWare system files from a network drive located on one file server to a remote (different) file server.This transfer method works with both asynchronous and direct communication sessions. However, it is not recommended for asynchronous connections because ACONSOLE does not provide a guaranteed packet delivery transport.When trying to send packets to or receive packets from a file server with extensive disk or LAN activity, ACONSOLE may "time out" when sending data to the file server or while waiting for a response from the server.This option automates the process of transferring NetWare operating system files to remote file servers. Once the appropriate source directories and files are created on a source network drive, the "Transfer System and Public Files" option on the remote management "Available Options" menu automatically copies the files to the correct directories on the target file server.ProcedureIf the source directory is already set up, skip to IDREF="FM82351"Step 3.Create subdirectories on the source network drive that match the names of their respective NetWare v3.12 diskettes, for example, SYSTEM_1, SYSTEM_2, etc.ID="FM82351"Use the NCOPY command to copy the files from the NetWare system diskettes to the respective network subdirectories with the same names.For example, to copy files from a diskette in drive A: at the workstation to a network directory called "SYSTEM_1" on drive G:, type  NCOPY A:*.* G:\SYSTEM_1 /S <Enter>Once the source directories and files are created on the source file server, the files can be transferred to the SYSTEM, PUBLIC, and LOGIN directories on the target file server.From a workstation, log in as SUPERVISOR to the file server on which you created the source files.If you do not have a search drive mapped to the directory containing the remote console files (usually SYS:SYSTEM), type  MAP S16:=SYS:SYSTEM <Enter>For remote management to operate properly, you must map a search drive to the directory containing the remote console files.From the drive or directory containing the source subdirectories, activate a remote console (as explained in IDREF="FM36233""Using a Remote Console" on page 367). Activate the remote console using this directory as your default directory.Access the "Available Options" menu and select "Copy System and Public Files." The remote console scans the default directory for a SYSTEM_2 subdirectory with a idxid="w8015"book="_idx" docset="nw312" tidref="i2290"FILEDATA.DAT file. If the file is found, a window appears and each file is listed as it is copied to the target file server. If the file is not found, you will be prompted to insert installation diskettes into the target file server or to press <F7> to cancel.ID="FM45375"Upgrade a idxid="w8016"book="_idx" docset="nw312" tidref="i3085"LAN or Disk DriverUsing a remote console, you can add a new LAN driver or disk driver to a file server, or upgrade an existing LAN or disk driver.ID="FM77532"Add or idxid="w8017"book="_idx" docset="nw312" tidref="i7086"Upgrade a LAN driverProcedureActivate a remote console (as explained in IDREF="FM36233""Using a Remote Console" on page 367).From the "Available Options" menu, select "Transfer Files to Server."Enter the source directory path of the LAN driver you want to transfer.Enter the target directory path for the LAN driver.Enter the following commands according to the type of session you have opened. For ACONSOLE sessions, enter the commands at the system console prompt (:). For RCONSOLE sessions, create an .NCF file and enter the commands in the file.Enter the commands in this order:  UNLOAD old_driver<Enter>  AUTOEXEC <Enter>For RCONSOLE sessions, save and execute the .NCF file.If you have opened a connection using RCONSOLE, the commands must be placed in an .NCF file because the RSPX connection will be terminated when the old LAN driver is unloaded.ID="FM13005"Add or Upgrade a idxid="w8018"book="_idx" docset="nw312" tidref="i7086"Disk idxid="w8019"book="_idx" docset="nw312" tidref="i1561"DriverProcedureActivate a remote console (as explained in IDREF="FM36233""Using a Remote Console" on page 367).Make sure all users are logged out. You can use the MONITOR utility to do this.Disable logins to the file server by typing  DISABLE LOGIN <Enter>Dismount all volumes on drives that are serviced by the controller whose driver you will unload.Use the UNLOAD command to unload the old disk driver by typing  UNLOAD old_driver <Enter>Access the remote console "Available Options" menu and select "Transfer Files to Server."Enter the source directory path of the new disk driver and press <Enter>.Enter the target directory path for the new disk driver and press <Enter>.Exit the "Available Options" menu and go to the system console prompt.Use the LOAD command to load the new disk driver by typing  LOAD new_driver <Enter>Type "MOUNT ALL" at the prompt.Enable logins to the file server by typing  ENABLE LOGIN <Enter>ID="FM80516"Configuring idxid="w8020"book="_idx" docset="nw312" tidref="i3922"the idxid="w8021"book="_idx" docset="nw312" tidref="i1134"ModemID="FM84184"Modify the Modem idxid="w8022"book="_idx" docset="nw312" tidref="i1134"ConfigurationProcedureFrom the ACONSOLE "Main Menu," select "Configure Modem."When the "Current Modem Configuration" screen appears, select the field you want to modify and make changes as follows.We recommend that you do not change the modem Reset, Initialization, Dial, or Hangup commands. The default settings are recommended for these commands.To modify idxid="w8023"book="_idx" docset="nw312" tidref="i1064"SELECT COMM PORT, press <Enter> and select the communications port to which you have connected your modem.To modify SELECT idxid="w8024"book="_idx" docset="nw312" tidref="i667"BAUD RATE, press <Enter> and select the baud rate from the list.To modify USER CONNECTION ID, press <Enter> and enter a name for the modem user (up to 40 characters).This field must contain an ID name before the modem will attempt a call.ID="FM60107"Create or Modify the Modem idxid="w8025"book="_idx" docset="nw312" tidref="i5078"Phone ListPhone list entries can be up to 40 characters long. The purpose of the "Location" field is to help you remember which phone number is associated with a particular file server. For example, you can enter the name of a file server or the name of a department or city.When you enter a idxid="w8026"book="_idx" docset="nw312" tidref="i3922"phone number for a remote server, you must include any necessary dial modifiers. (See your modem user's guide for this information.) The modifiers must be entered because the number is appended to the dial command being sent to your local modem.ProcedureFrom the ACONSOLE "Main Menu," select "Connect to Remote Location."When the phone list appears, you can change your phone list in any of the ways explained in the following table.WIDTH="96"TaskWIDTH="216"ProcedureWIDTH="96"Add a numberWIDTH="216"Press <Insert>; then enter the phone number  and a name for the remote server. Press <Esc> to  save the entry.Modify a numberSelect the number to be modified. Press <F3>  and enter the new information. Press <Esc> to  save the entry.Delete a numberSelect the number to be deleted. Press <Del>.  When the confirmation box appears, select "Yes."LBL="3"ID="FM14588"Troubleshooting GuideOverviewidxid="w8027"book="_idx" docset="nw312" tidref="i6910"This is a guide to some of the most common idxid="w8028"book="_idx" docset="nw312" tidref="i5578"problems you may encounter while maintaining your network. It is not intended to be exhaustive. If you need more help, contact your Novell Service Representative. This guide is divided into the following sections: Maintenance tips---designed to help you develop habits that prevent problems IDREF="FM81230"(page 386)Flow charts---designed to isolate the source of the problem IDREF="FM47739"(page 395)Common problems---designed to identify possible solutions to specific idxid="w8029"book="_idx" docset="nw312" tidref="i6910"idxid="w8030"book="_idx" docset="nw312" tidref="i6910"problems IDREF="FM94039"(page 421)The following sections in Chapter 1 also contain helpful troubleshooting ideas: INSTALL, LOAD, LOAD disk driver, LOAD LAN driver, MONITOR, SET, UPS, UNLOAD, and VREPAIR.The following workstation utilities, found in Utilities Reference, also contain troubleshooting information: BINDFIX, BINDREST, and NBACKUP.Appendix D in Installation and Upgrade contains troubleshooting information for remote booting of diskless workstations.ID="FM81230"Maintenance idxid="w8031"book="_idx" docset="nw312" tidref="i6796"TipsThis section explains some tips on managing your file server and its resources. These tips are not intended to be inclusive, but only to get you started in setting up a routine idxid="w8032"book="_idx" docset="nw312" tidref="i3676"maintenance schedule that will keep the file server and its resources functioning effectively. LBL="3-1" INLINE="F"Maintenance tipsWIDTH="240"Memory maintenance WIDTH="72"IDREF="FM17967"386Disk maintenance IDREF="FM31265"389Security maintenance IDREF="FM49651"391Bindery maintenance IDREF="FM37667"393Volume maintenance IDREF="FM49998"394ID="FM17967"Memory idxid="w8033"book="_idx" docset="nw312" tidref="i3758"idxid="w8034"book="_idx" docset="nw312" tidref="i3676"MaintenanceNetWare has been configured so that your system can grow as your organization grows. Many of the resources that use memory can allocate additional memory as required. The NetWare operating system warns you when memory is getting low. The operating system warns you again when it cannot allocate additional memory for a resource.If you monitor how fast available memory is being used by growing resources, you can plan for future needs. We suggest that you monitor the following statistics:Cache buffersAlloc Short Term MemoryService processesPacket receive buffersCache idxid="w8035"book="_idx" docset="nw312" tidref="i879"BuffersYou can view the percentage of memory available for cache buffers in MONITOR ("Server Memory Statistics" window). Cache buffers are used to store frequently used files (for fast access) and to allocate memory to other memory pools. As memory is allocated to other pools (for example, to the Non-Movable Memory pool to load loadable modules), the number of available cache buffers decreases. The number of cache buffers will naturally decrease as you add additional hard disks and as the number of files and their size increase.If the cache buffers get too low, performance decreases. Frequently used files can no longer be cached because not enough cache buffers are available. The files will have to be read from the hard disk (a process that is considerably slower than reading them in from memory).The number of buffers you need depends on your system (the number of users and the tasks that they are performing). By monitoring the rate of the decrease of available cache buffers, you can plan to add more memory to the file server. When the percentage of available cache buffers reaches 20%, you need to add more memory. However, you may need to add more memory at 30% (or even at 40% or 50%) for your system. Alloc idxid="w8036"book="_idx" docset="nw312" tidref="i198"Short Term MemoryYou can view the percentage of memory idxid="w8037"book="_idx" docset="nw312" tidref="i198"allocated for the idxid="w8038"book="_idx" docset="nw312" tidref="i198"Alloc Short Term Memory pool in MONITOR ("Server Memory Statistics" window). A SET parameter ("Maximum Alloc Short Term Memory") controls the maximum size of this pool. The default size is 8 MB. As the pool grows close to 8,000,000 bytes, increase the SET parameter by 1 MB. You should also view the resource tags for Alloc Short Term Memory and track which modules are using more and more of this type of memory. Most modules should not need a growing amount of this memory. If a loadable module is the source of growth for this memory pool, contact the vender of the module.ID="FM49112"Service idxid="w8039"book="_idx" docset="nw312" tidref="i6260"ProcessesYou can view the number of service processes created to handle requests in MONITOR ("Information for Server servername" window).The number of service processes increases as the number of outstanding disk I/Os increases. A SET parameter ("Maximum Service Processes") controls the number of service processes that the operating system allocates. The default is 20. If your file server is low on cache buffers IDREF="FM91936"(see "MONITOR" on page 176), do not increase the number of service processes. If you decrease the cache buffers, you increase the likelihood that a service process has to wait for a disk I/O rather than being able to service the request immediately from the cache buffers.If your system approaches the default number of server processes and your file server has sufficient memory, you can either increase the default by 5 or use the following suggestions to increase idxid="w8040"book="_idx" docset="nw312" tidref="i2599"disk I/O:Use the SPEED command to check the speed of the CPU. Make sure that the jumpers have been set for the highest speed (check the computer's documentation).Add a host bus adapter and attach some of the hard disks to it.Turn off the driver's automatic read-after-write verify function if your hard disks do a read-after-write verification automatically. (See the documentation for the hard disks.) This function is controlled under the "Disk Information" option in MONITOR.Configure your volumes so that they span more than one hard disk. IDREF="FM11821"See "INSTALL."Increase the number of cache buffers by adding more memory to the file server. If you increase the available cache buffers, you increase the likelihood that the file will be in memory and decrease the likelihood that an existing service process will have to wait for a disk I/O.Upgrade to a computer that has a higher CPU speed.Upgrade to a microchannel or EISA computer and use either microchannel or EISA bus master boards. The number of packet receive buffers also influences the need for service processes. See the next section, "Packet receive buffers."Packet idxid="w8041"book="_idx" docset="nw312" tidref="i4878"Receive idxid="w8042"book="_idx" docset="nw312" tidref="i4878"BuffersYou can view the number of allocated packet receive buffers in MONITOR ("Information for Server servername" window). A SET parameter ("Maximum Packet Receive Buffers") determines how many of these buffers can be allocated. As your server approaches the default of 100, increase the parameter in increments of 20 until you have one packet receive buffer per station. If you have bus master boards in either an EISA or microchannel computer, you may need more than one packet receive buffer per station. The NE3200 driver, for example, can use 41 packet receive buffers when under maximum load.If you are not using bus master boards and MONITOR shows that the operating system is using a packet receive buffer for each connected workstation, your file server cannot process disk I/Os fast enough. You can decrease the need for more packet receive buffers by increasing the number of service processes and implementing the suggestions for improving disk I/O. IDREF="FM49112"See "Service Processes" on page 388.ID="FM31265"Disk idxid="w8043"book="_idx" docset="nw312" tidref="i3676"MaintenanceNetWare has many features that help protect your data from corruption or loss. Hot Fix, mirroring, duplexing, and the salvageable file system all help, but an application can still corrupt the data files or two idxid="w8044"book="_idx" docset="nw312" tidref="i2599"mirrored hard disks can fail at the same time.For maximum security against loss of data, do the following:Back up your data regularly.Check your hard disks regularly for warning signs.Back idxid="w8045"book="_idx" docset="nw312" tidref="i2599"Up the DataCurrent and valid backups are essential for maintenance. Every administrator, sooner or later, experiences a hardware or software failure that requires data from a backup.If your system uses backup devices that are attached to your file server, or if you have name spaces other than DOS and MAC, you should use SBACKUP for your backups. If your backup device is attached to a workstation and you have only DOS or MAC file types, you can use NBACKUP.We recommend the following types of backups:A backup of modified files. You should have enough backup storage for two weeks (one set for the current week and an archived set for the past week).A complete backup of everything. This makes a mirror image of the file server. Then, if you lose everything, you can at least return to this point and use the modified file backups to bring the server to a more current state.A backup of the idxid="w8046"book="_idx" docset="nw312" tidref="i683"bindery. Most backup software programs that are NetWare compatible back up the bindery, but some third-party programs do not.If you have never restored a bindery with the hardware and software you are currently using, use SBACKUP to back up the bindery.A backup of the trustee assignments. Most backup programs that are NetWare compatible back up the trustee assignments, but some third-party programs do not.If you have never restored trustee assignments with the hardware and software you are currently using, use SBACKUP to back up the trustee assignments. Set the "Backup Subdirectories" and "Backup Trustees" options to "Yes" and use the "Files to exclude" option with *.* as the filename to exclude all files. The directory structure with its trustee assignments will be backed up.Check the Hard DisksYou need to check the status of each hard disk at least weekly. An increase in redirected blocks can indicate that a hard disk is having problems and may need to be repaired or replaced. You can view the number of redirected blocks in MONITOR (use the "Disk Information" option). When the number of "Redirected Blocks" plus the number of "Reserved Blocks" reaches half the total number of "Redirection Blocks," idxid="w8047"book="_idx" docset="nw312" tidref="i2682"Hot Fix is close to failing on the disk. Back up the data on the disk. Then use INSTALL ("Available Disk Options") to run either a destructive or nondestructive surface test on the hard disk. If the disk fails the surface test, you will have to remove the disk and repair or replace it.When blocks are redirected or when mirroring or Hot Fix fails, warning messages are displayed on the file server console and recorded in the File Server Error Log that can be read in SYSCON. Scan this error log at least weekly for disk messages. If you suspect problems, view the log daily.ID="FM49651"Security idxid="w8048"book="_idx" docset="nw312" tidref="i6177"idxid="w8049"book="_idx" docset="nw312" tidref="i3676"MaintenanceIf you need a secure system, use the security features of NetWare. Then set up a schedule to test your security. The more secure your system needs to be, the more frequently you should test it for violations. Test for general violations in the security setup, monitor your users' login habits, and monitor the effective rights in sensitive directories.General ViolationsUse the SECURITY command to list the weakest points in your security system. SECURITY lists the following types of potential security problems:Users who have been made supervisor equivalentUsers who have insecure passwords or no passwordsUsers who have trustee assignments at the root directory of any volumeUsers who have rights to the SYS:SYSTEM directoryUse SYSCON to view the File Server Error Log. This file records the following kinds of information that can indicate a breach in security:The node addresses of stations connecting to the file server console with RCONSOLEThe date and time when the file server is downed, TTS enabled or disabled, login enabled or disabled, and the bindery opened and closedLogin HabitsMonitor your users' login habits to ensure that they are not leaving the system open.Run USERLIST to make sure users are logging out when they leave for lunch and for the night. Teach them to use a keyboard lock or to log out whenever they leave a workstation unattended.Run USERLIST to monitor who is logged in as SUPERVISOR, how long the user has been logged in, and from which workstation the user has logged in. A user should never leave a workstation unattended when logged in as SUPERVISOR.Effective RightsRegularly check the security of the directories that need to be protected to ensure that only those users who should have rights to the directories do. As users move to new assignments in your department or business, their trustee assignments should also change. Check effective rights by completing the following:Use the FILER "Who has rights here" option to view users' effective rights in the directories and files that need to be secure. (This option is more complete than the TLIST command that lists only the trustee assignments given to the directory.) The FILER option scans the directory structure and reports all users who can exercise rights in the directory.Use SYSCON to review group member lists and delete users who have new assignments that no longer require them to be members of a particular group.Use NBACKUP or SBACKUP to back up directory trustee assignments whenever you have made significant changes to these assignments.ID="FM37667"Bindery idxid="w8050"book="_idx" docset="nw312" tidref="i3676"idxid="w8051"book="_idx" docset="nw312" tidref="i683"MaintenanceUse SYSCON to delete users who are no longer using the file server.Check the idxid="w8052"book="_idx" docset="nw312" tidref="i7049"TTS$LOG.ERR file. Transaction Tracking System idxid="w8053"book="_idx" docset="nw312" tidref="i6864"(TTS) protects the bindery database from corruption. If the operating system shuts down TTS because of system problems, your bindery could become corrupted. The TTS$LOG.ERR file, which is located in the root directory of the SYS volume, records all significant TTS events. The file can be read with any text editor program.For more information, IDREF="FM33727"see "TTS Problems" on page 451 or see "book="concepts" docset="nw312"TTS" in Concepts.Keep a backup copy of the bindery files in a secure place. Record the SUPERVISOR's password or back up the bindery with no password for user SUPERVISOR.Keep a current copy of the .OLD idxid="w8054"book="_idx" docset="nw312" tidref="i683"bindery files. To create these files, run BINDFIX. From the SYS:SYSTEM directory, copy the NET$OBJ.OLD, NET$PROP.OLD, and NET$VAL.OLD files to a diskette. Then delete the .OLD files from the SYS:SYSTEM directory. Record the SUPERVISOR's password and store the diskette in a secure place. If you lose your bindery and cannot restore it from a regular backup, copy the .OLD files into the SYS:SYSTEM directory. Run BINDREST. The .OLD files will be restored as the file server's bindery.ID="FM49998"Volume idxid="w8055"book="_idx" docset="nw312" tidref="i7372"idxid="w8056"book="_idx" docset="nw312" tidref="i3676"MaintenanceUse NBACKUP, SBACKUP, or third-party software regularly to back up the data on the volume. Use CHKVOL, CHKDIR, and VOLINFO to monitor the growth of directories and files. By determining how fast a volume is growing, you can plan for adding hard disks or removing files and directories that are no longer used. Check the idxid="w8057"book="_idx" docset="nw312" tidref="i7333"VOL$LOG.ERR file for each volume. This file is located in the root directory of the volume. For example, the file for volume SYS: is located in SYS:. This file records all system alerts for the volume. See NetWare System Messages for an explanation of the alerts. Use a DOS text editor to view the file.Use CHKVOL to monitor the amount of disk space being used by deleted files. If you need the space, use the SET parameters ("Immediate Purge of Deleted Files," "Minimum File Delete Wait Time," and "File Delete Wait Time") to increase available space. Log in as SUPERVISOR and use PURGE at the volume level to free the space immediately.Use LISTDIR /S at the root directory of a volume to view idxid="w8058"book="_idx" docset="nw312" tidref="i6563"subdirectory depth. A SET parameter ("Maximum Subdirectory Tree Depth") controls how many levels of subdirectories the operating system will support. The default is 25. If your structure approaches the default, either move some of the directories to a level closer to the root (see "book="utilref" docset="nw312"FILER" in Utilities Reference) or change the limit with the SET parameter.ID="FM47739"Flow idxid="w8059"book="_idx" docset="nw312" tidref="i6910"idxid="w8060"book="_idx" docset="nw312" tidref="i2451"ChartsThe following flow charts are designed to help isolate most problems on NetWare v3.1x networks. They also point you to specific suggestions in IDREF="FM94039""Communication Problems". LBL="3-2" INLINE="F"Troubleshooting flow chartsWIDTH="84"ChartWIDTH="228"PurposeWIDTH="84"PageWIDTH="84"HardwareWIDTH="228"Designed to isolate hardware problems that prevent  DOS from loading.WIDTH="84"IDREF="FM79078"396File ServerDesigned to isolate problems that prevent the file  server from booting after DOS has been loaded.IDREF="FM77153"401WorkstationDesigned to isolate problems that prevent the  workstation from logging in to a file server after DOS  has been loaded.IDREF="FM75467"406LBL="3-1"ID="FM79078"idxid="w8061"book="_idx" docset="nw312" tidref="i1638"idxid="w8062"book="_idx" docset="nw312" tidref="i2640"Hardware flow chartFILE="n312sa2a.pbm"LBL="3-2"ID="FM77153"File server flow chartFILE="n312sa3a.pbm"LBL="3-3"ID="FM75467"idxid="w8063"book="_idx" docset="nw312" tidref="i7493"idxid="w8064"book="_idx" docset="nw312" tidref="i3005"Workstation flow chartFILE="n312sa4a.pbm"Common ProblemsThis portion of the troubleshooting section lists a number of solutions to specific idxid="w8065"book="_idx" docset="nw312" tidref="i6910"problems that may be isolated by the flow chart. The solutions are organized into the following sections:WIDTH="264"Section WIDTH="48"PageWIDTH="264"File server, hard disk, and volume problems WIDTH="48"IDREF="FM28497"409Communication problems IDREF="FM94039"421Workstation problems IDREF="FM93596"433Application problems IDREF="FM99603"435TTS problems IDREF="FM33727"451If you need more help IDREF="FM68419"454ID="FM28497"File Server, idxid="w8066"book="_idx" docset="nw312" tidref="i2599"Hard Disk, and idxid="w8067"book="_idx" docset="nw312" tidref="i6910"Volume Problemsidxid="w8068"book="_idx" docset="nw312" tidref="i6910"File idxid="w8069"book="_idx" docset="nw312" tidref="i2034"server and idxid="w8070"book="_idx" docset="nw312" tidref="i6910"hard disk problems commonly appear during installation or upgrade. The conditions are explained on the following pages.WIDTH="264"Section WIDTH="48"PageWIDTH="264"General solutions WIDTH="48"IDREF="FM99861"410Console commands cannot be entered at the file server  console, or they do not function correctly IDREF="FM93860"410The file server does not keep track of time correctly IDREF="FM44271"411The file server "hangs" after mounting the last volume IDREF="FM80570"412The operating system reports FAT errors when the file server  is first booted after the installation of an RX-Net network  board IDREF="FM30290"413A hard disk cannot be accessed IDREF="FM42993"413None of the volumes, including SYS: , were mounted IDREF="FM94538"414The operating system reports disk errors when a volume is  being mounted IDREF="FM44609"415The operating system reports memory errors when a volume  is being mounted IDREF="FM64258"416A volume cannot be mounted because of corrupted directory  tables or FATs IDREF="FM44189"419A volume cannot be mounted because a name space module  was not loaded first IDREF="FM72276"420ID="FM99861"General SolutionsIf the problem occurred after installation, it may indicate that the network was installed incorrectly. Do the following first:Check all network boards for possible conflicting address and I/O settings. IDREF="FM40275"See "Troubleshooting LAN Drivers" on page 155.Each component should be able to work as a standalone system. Remove all network boards in the file server and boot DOS. Add each board and make sure that DOS still boots. Make sure that all cables are fastened securely to all network boards and network connectors and that terminating resistors are installed correctly.ID="FM93860"Console Commands Cannot Be Entered at the File Server Console, or They Do Not Function Correctly.Possible CausesThe NetWare operating system may be configured incorrectly.You are not looking at the command screen.The SERVER.EXE file is corrupted.The server has been downed.The server has hung.Possible SolutionsCheck your file server records of network board configurations. Then check the actual hardware configuration on each network board in the file server to ensure that 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 network board settings for possible interrupt and I/O port conflicts. You can set an interrupt on a network board incorrectly and still have the file server boot up initially. The most common conflict occurs when a network board is set to interrupt 4 and a printer is connected to the file server's serial port, which also uses interrupt 4.Make sure all cables are fastened securely to all network boards and network connectors. Check the cabling for proper termination.From a backup, copy a new version of SERVER.EXE to the file server boot directory and reboot the file server.Have all users close their files and log out. Down the file server, if possible. If not, wait a few minutes after all users have logged out; then reboot the file server.ID="FM44271"The File idxid="w8071"book="_idx" docset="nw312" tidref="i2218"Server Does Not Keep Track of Time Correctly.Possible CausesWhen the file server is booted initially, the NetWare operating system gets the date and time from the internal clock. After that, the operating system keeps track of time by counting the computer's clock "ticks." If the oscillator on the main system board is fast or slow, the system time is fast or slow accordingly.Possible Solutions If the file server only loses time when the server is off, the battery may be low or dead. Replace the battery.If replacing the battery does not help, replace the main system board.ID="FM80570"The idxid="w8072"book="_idx" docset="nw312" tidref="i2034"File Server "Hangs" After Mounting the Last idxid="w8073"book="_idx" docset="nw312" tidref="i7372"Volume.Possible CausesThe file server network board may not be initializing when the file server is brought up because the board is not installed or seated correctly.The file server network board may not be configured correctly.Possible Solutions Run CONFIG at the file server console to see what settings appear on the screen. Check the network board configurations. Make sure the settings match.Make sure that all file server and workstation network boards are seated properly and that cabling and connections are attached securely.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 station address settings.ID="FM30290"The Operating System Reports idxid="w8074"book="_idx" docset="nw312" tidref="i1969"Fat Errors When the File Server is First Booted After the Installation of an RX-Net Network Board.Possible CauseThe network board was not connected to an active hub or to a workstation that was powered on.Possible SolutionAn RX-Net system using third-party network boards must be connected to an active hub (powered on) or another workstation (powered on) when the server is booted.ID="FM42993"A idxid="w8075"book="_idx" docset="nw312" tidref="i2599"Hard Disk Cannot Be Accessed. (The Format or Surface Test Options in Install Will Not Run, for Example.)Possible Causes The disk driver has not been loaded.A hard disk is not installed or cabled correctly.The communication channel between the controller interface board, the host bus adapter, and the hard disk is not functioning.The hard disk controller interface board is not terminated or addressed correctly.The hard disk has not been partitioned.Possible SolutionsMake sure the disk driver is loaded. Run MODULES to view the loaded disk drivers. Use DISKSET if you have loaded the host-bus-adapter driver more than once.Check the cables between the hard disks and the controller interface 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 and on the controller interface boards.Check the jumper settings on the host bus adapter, the controller interface board, and the hard disk. See the hardware documentation for correct jumper settings.Run DISKSET to make sure the hardware configurations contained on the EEPROM chip on the host bus adapter match the hard disks in your file server.Run DOS FDISK for internal hard disks.Load INSTALL to check the NetWare partition and volume information on the hard disk.Make sure that each controller interface board connected to the same host bus adapter has its own valid address.ID="FM94538"None of the idxid="w8076"book="_idx" docset="nw312" tidref="i7372"Volumes, Including SYS:, Were Mounted.Volume SYS: is the backout volume for TTS. It also contains the bindery files and NLMs. If this volume does not mount when the file server is booted, the AUTOEXEC.NCF file will not execute, LAN drivers will not load, the bindery cannot be opened, and TTS will not be enabled.Possible CausesVolume SYS: is corrupted.The hard disk containing volume SYS: has failed.The cable or power to the external hard disks has malfunctioned.Possible SolutionsRun VREPAIR on volume SYS:.Check the cabling and power to the external hard disks. Replace any faulty components.Replace the hard disk containing volume SYS:.If you install a new hard disk type to replace the hard disk in a disk subsystem, be sure to run DISKSET.Load INSTALL to create the partitions and volume SYS:.Restore the data from a backup copy.ID="FM44609"The Operating System Reports idxid="w8077"book="_idx" docset="nw312" tidref="i2599"Disk Errors When a Volume is Being Mounted.Possible CausesThe file 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 file server is turned off without the DOWN command.Possible Solutions Load MONITOR and check the status of the available cache buffers. If the cache buffers are less than 20%, add more memory to your file server.Minor will 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 with TTS.ID="FM64258"The Operating System Reports idxid="w8078"book="_idx" docset="nw312" tidref="i7372"Memory Errors When a Volume is Being Mounted.Possible CausesVolumes 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. Therefore, if your file server is using most of the memory (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 Directory Tables. Adding name space support can cause the tables to grow so large that the file server does not have enough memory to mount the volume.Possible Solutions Load MONITOR and check the status of the available cache buffers. If the cache buffers are less than 20%, add more memory to your file server.Free up memory by unloading resources.Streamline the directory structure. Every subdirectory takes at least one directory block (a 4KB block of memory). Therefore, 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 purge the deleted subdirectories and files, you can free up memory.Remove the recently added name space support. This is a destructive step and destroys all the extended file information. Before taking this step, try to free 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. Down the file server and reboot it to return memory from the Permanent and Alloc pools to the Cache Buffer pool.To remove the idxid="w8079"book="_idx" docset="nw312" tidref="i3992"name space, load VREPAIR and select the "Remove All Name Space Entries" and "Write Changes Immediately To Disk" options. Then run VREPAIR on the volume that will not mount. Calculate how much idxid="w8080"book="_idx" docset="nw312" tidref="i3758"memory idxid="w8081"book="_idx" docset="nw312" tidref="i3992"you need and add memory to the file server. View current idxid="w8082"book="_idx" docset="nw312" tidref="i7372"volume size with INSTALL IDREF="FM11821"(see page 47). Then use the following chart to estimate the total amount of memory needed per volume.LBL="3-4"Calculating memory needed for added name spaceFILE="n312sa01.pbm"ID="FM44189"A Volume Cannot Be Mounted Because of Corrupted Directory Entry Tables or idxid="w8083"book="_idx" docset="nw312" tidref="i1969"Fats.Possible CausesThe following can cause mismatches in the duplicate copies of the FAT and Directory Entry Table:A power failure occurs and the file server is not downed 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.Possible SolutionsComplete one or more of the following:Run VREPAIR.Add a UPS system so that the file server is automatically downed when a commercial power failure occurs.Replace faulty disks or controllers.If the volume resides on idxid="w8084"book="_idx" docset="nw312" tidref="i2599"mirrored hard disks, salvage the data on one of the drives. Use INSTALL to unmirror the hard disks (highlight the hard disk you think is least reliable and delete that disk from the mirroring list). Then run VREPAIR on the volume and mount the volume. If the volume will 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.ID="FM72276"A idxid="w8085"book="_idx" docset="nw312" tidref="i7372"Volume Cannot Be Mounted Because a idxid="w8086"book="_idx" docset="nw312" tidref="i3992"Name Space Module was Not Loaded idxid="w8087"book="_idx" docset="nw312" tidref="i3992"First.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:The 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 file server. Possible SolutionsLoad the name space module; then mount the volume. Copy the name space module to the file server boot directory (C: or A:), and add the load command to the STARTUP.NCF file. The module then loads automatically whenever the file server is booted.Delete the name space configuration from the volume. This is a destructive step and destroys all the extended file information. Back up all non-DOS files. Then load VREPAIR and select the "Remove All Name Space Entries" and "Write Changes Immediately To Disk" options. Then run VREPAIR on the volume.ID="FM94039"Communication idxid="w8088"book="_idx" docset="nw312" tidref="i6910"idxid="w8089"book="_idx" docset="nw312" tidref="i1064"ProblemsCommunication problems are related to network boards, LAN drivers, network performance, and file server/workstation communications, as well as to internetwork communications. The problems are treated on the following pages:WIDTH="264"Section WIDTH="48"PageWIDTH="264"General solutions WIDTH="48"IDREF="FM30368"421The file server does not boot after a network board is installed IDREF="FM14256"423The file server could not be found by the workstations on the  network IDREF="FM59790"424File servers do not recognize each other on the network IDREF="FM16826"425Responses from the file server are noticeably slow IDREF="FM88571"427Workstations can log in, but periodically lose their  connections to the file server IDREF="FM81616"429ARCnet-specific problems IDREF="FM17217"430Ethernet-specific problems IDREF="FM16022"431Token-Ring-specific problems IDREF="FM66880"432ID="FM30368"General SolutionsIf the problem occurred simultaneously on several workstations, it is probably a result of one of the following:The file server network board is not seated or configured correctly.The network board cable from the file server is faulty.Cabling on the network is faulty.The connector closest to the file server is faulty.The RX-Net active hub is off. The repeater is off or nonfunctional.The cabling is not terminated.Volume SYS: is not mounted.Possible SolutionsRun VOLUMES at the file server console. If SYS: is not mounted, mount it. The file server does not broadcast to the network until SYS: is mounted.Run CONFIG at the file server console to check the configuration of the network boards. Then down the file server, turn off the power, and check the actual network board settings: Make 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 (station) address on the board is a legal address. Addresses 0 and FFFFFFFFFFFF are reserved for NetWare, so do not use them.Run CONFIG at the file server console to make sure that each network board has a LAN protocol bound to it. Network boards cannot broadcast without a protocol.Run USERLIST /A at a workstation, if possible, to check node (station) addresses. Each station address on the network should be unique. Sometimes you can find the problem by turning off all workstations and bringing them up one at a time.Check all hubs and repeaters to make sure they are on.Check the cables for proper termination.Make sure the file server network board is seated properly.Replace the file server network board with a board that works correctly. Make sure it has the same jumper settings.Have a user log in to the network from a workstation. Load MONITOR and select "Connection Information" from the "Available Options" menu. If the "Active Connections" list shows the user's login name, the file server is receiving and responding to the workstation shell's request.If the workstation receives a "File server cannot be found" error, continue replacing segments of cable and cabling connections until communication is restored.ID="FM14256"The idxid="w8090"book="_idx" docset="nw312" tidref="i2122"File Server Does Not Boot After a Network Board is Installed.Possible CausesThe network board is not attached properly to the cable.The hardware conflicts with other boards, the monitor, or ports in the file server.Possible SolutionsCable 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 "File Server Worksheet" in Installationand Upgrade to record the information. Also do the following to identify potential conflicts.Check the documentation that comes 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. Reconfigure the equipment so that no conflicts exist.For additional information, IDREF="FM40275"see "Troubleshooting LAN Drivers" on page 155.ID="FM59790"The idxid="w8091"book="_idx" docset="nw312" tidref="i2122"File Server Could Not Be Found by the idxid="w8092"book="_idx" docset="nw312" tidref="i7493"Workstations on the Network.Possible CausesThe network board may not be initializing when the file server is brought up because it is not configured correctly or it has failed.The file server may be anticipating the wrong frame type.Address or interrupt conflicts may exist between two boards within the file server or between a board and the computer's hardware.The file server may not have enough packet receive buffers.A protocol (IPX) may not have been bound to the network board.The cabling may be too close to sources of interference.Volume SYS: may not be mounted.Possible SolutionsRun CONFIG at the file server console to see what settings appear on the screen. Then check network board configurations in the file server. Be sure the network board configurations match the settings that appear when you run CONFIG.Run VOLUMES at the file server console to ensure that SYS: is mounted. SYS: must be mounted before the file server can advertise its name to the network.Make sure all network connectors (including transceivers and repeaters) are installed and the cable is attached securely.Check node (station) address settings on all file server and workstation network boards. Each address should be unique.Check all network numbers (internal and cable). Each file server and cabling system should have a unique network number.Make sure no two boards in the file server are using the same I/O port, memory address, or interrupt.Make sure all network boards are seated firmly and the cabling connections are in place.Bind the driver (TRXNET, NE1000, TOKEN, etc.) to IPX (or another communication protocol).Make sure the network cable is terminated properly. Many network boards send a broadcast message during initialization and hang if the network is not cabled or terminated properly.If you have a lot of network interaction, increase the maximum number of packet receive buffers. IDREF="FM73882"See "SET" on page 258.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.ID="FM16826"File idxid="w8093"book="_idx" docset="nw312" tidref="i2122"Servers Do Not Recognize Each Other on the Network.Possible CausesThe hardware settings in the file server are incorrect.The network or internetwork addresses conflict.The bindery is corrupted.Possible SolutionsRun CONFIG at the file server console to see what settings appear on the screen. Then check network board configurations in the file server. Be sure the network board configurations match the settings that appear when you run CONFIG.Check the internal network number for the file server and the network number for the cabling.When multiple file servers share the same cabling system (called a multiserver network), all file servers must have the same cabling network number. However, the file servers must have unique file server internal network numbers and unique station addresses.When network cabling systems are connected through bridges (internal or external), each cabling system must have a unique network number. NetWare v3.1x file servers must also have a unique internal network number apart from the cabling. The unique network address is the first item read in a packet sending/receiving interaction.Run BINDFIX if you suspect a corrupted bindery.Reset the router with the RESET ROUTER console command.Check the cabling system for faulty termination.Down all file servers except one. Reset its router with RESET ROUTER. Bring up each file server, one at a time, establishing communications with it before bringing up the next one. Run DISPLAY NETWORKS to check for duplicate network addresses as each file server is booted.ID="FM88571"Responses From the idxid="w8094"book="_idx" docset="nw312" tidref="i2122"File Server are Noticeably Slow.Possible CausesThe workstation network board is slow or faulty.Network cabling is faulty.The file server network board is slow or faulty.Too many users are using the network.The file server speed is not set to the highest speed.The file server hard disk is slow or faulty.The file server is low on memory.The volume has too many deleted files.Network traffic is extremely high.The cabling system is experiencing too much interference.A hard disk has failed or is failing.Insufficient directory buffers, cache buffers, or packet receive buffers have been allocated.Possible SolutionsCheck 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 file 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 file server to the network.Load MONITOR to check the status of the memory. If the Cache Buffers pool is near 20%, install more memory in the file server. If the Alloc Memory pool is near 8,000,000 bytes, use the "Maximum Alloc Short Term Memory" parameter in SET to increase the pool by 1MB.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, IDREF="FM17967"see "Memory Maintenance" on page 386.Load MONITOR and check the Hot Fix status of all hard disks. Check the mirroring status of all mirrored disks.Run PURGE to eliminate deleted files.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, recable the network so that the boards have equal loads.If you are on a multiserver network or an internetwork, recable the system with a backbone to reduce network traffic. See "book="concepts" docset="nw312"Bridges" 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.ID="FM81616"Workstations idxid="w8095"book="_idx" docset="nw312" tidref="i7493"Can Log In, But Periodically Lose Their Connections to the File Server.Possible CausesA network board in either the file server or a workstation is faulty.A user on the network is using an old shell file.Two workstations have the same node (station) address.The cabling system is not terminated properly.Possible SolutionsRun USERLIST /A. Make sure all node (station) addresses are unique.Check all boot files. Make sure everyone is using the latest version of the shell files.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 Care and a LANalyzer are available from Novell.) Replace faulty boards and cables.Use the appropriate NetWare installation supplement 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. IDREF="FM73882"See "SET" on page 258.If workstations are being cleared by the watchdog, check all network boards and the entire cabling system between the workstations and the file server. Check for faulty cables, improper termination, and faulty hubs.ID="FM17217"ARCnet-Specific idxid="w8096"book="_idx" docset="nw312" tidref="i455"ProblemsPossible CausesThe passive or active hubs are faulty.The network boards are faulty.Receive buffer sizes conflict.Node addresses are illegal or conflicting.The monitor board conflicts with the network board.Improper cable lengths connect to passive or active hubs.Two passive hubs are connected together.A passive hub is terminated improperly.Possible SolutionsRun USERLIST /A. Make sure that all node (station) addresses are unique and that no station uses 0.Check the fuses in all 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 cable lengths connecting active and passive hubs to ensure that they are within specifications. (See the appropriate NetWare installation supplement to review the cabling specifications for your network board.) 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. (See the appropriate NetWare installation supplement for a list of supported options for your 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.ID="FM16022"Ethernet-Specific idxid="w8097"book="_idx" docset="nw312" tidref="i1861"ProblemsPossible CausesT-connectors are not terminated properly.The 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).Hardware conflicts exist between the workstation and the network board.The workstation and the file server are using two different Ethernet frame types.Possible SolutionsCheck 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) you are using.Some VGA boards use interrupt 3. If the monitor is blank when the network board is installed, set the network board to an option that does not use interrupt 3. (See the appropriate NetWare installation supplement for a list of supported options for your network board.)Make sure that the file server LAN drivers and the workstation LAN drivers have been configured for the same Ethernet frame type. For information on frame types, see "book="concepts" docset="nw312"Ethernet configuration" in Concepts. Configure the workstations for the appropriate frame type.For instructions on configuring DOS ODI drivers, see ODI Shell for DOS.For the parameter you need to configure the Ethernet LAN driver in the file server, see "LOAD LAN driver" on IDREF="FM79039"page 122.Check terminators with an ohm meter for a resistance of 48 to 52 ohms. Replace any terminators that do not fall within the specified range.If you have used DOS ODI drivers or specialized software that sets the node address of the network boards, run USERLIST /A to make sure that each network board has a unique node address.ID="FM66880"Token-Ring idxid="w8098"book="_idx" docset="nw312" tidref="i6821"-Specific ProblemsPossible CausesA MAU is faulty.A MAU has been set improperly.A faulty Token-Ring adapter has been installed in a workstation or file server.TOKREUI/LAN Support has not been loaded at the workstations.Possible SolutionsReset 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 LAN SUPPORT PROGRAM diskette.Check for breaks in the daisy-chained MAUs.Check for duplicate node addresses if you have used DOS ODI 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 LAN SUPPORT PROGRAM diskette.ID="FM93596"Workstation idxid="w8099"book="_idx" docset="nw312" tidref="i7493"ProblemsThe idxid="w8100"book="_idx" docset="nw312" tidref="i6910"workstation problems discussed here are for problems that occur on only one network workstation. If the problems occur on more than one workstation simultaneously, IDREF="FM94039"see "Communication Problems" on page 421.If the problem occurred on only one workstation, it can probably be traced to one of the following sources:The workstation itself is not operating properly.The network shell is corrupted.The network board is faulty.The network board is not set correctly.The cabling attached to the workstation is faulty or connected improperly.The network shell's configuration does not match the network board's configuration.Possible SolutionsBoot the workstation with DOS only. Then run the computer's diagnostics utility to make sure that the computer can recognize all internal components. (For example, run the IBM PC AT Diagnostic for an IBM PC AT or IBM PC AT compatible.)If DOS cannot load, refer to the manufacturer's hardware installation or maintenance manual for your particular computer.Recopy the NetWare boot files to the boot diskette. If the files were generated with SHGEN, copy the files from the master shell diskette or rerun SHGEN. If the files are DOS ODI files, copy the files from a working copy of the NetWare ODI Shell for DOS diskette.Load MONITOR and select "Connection Information" from the "Available Options" menu. If the "Active Connections" list shows the user's login name, the file server is receiving and responding to the workstation shell's request.Set the "Console Display Watchdog Logouts" parameter to ON. IDREF="FM73882"See "SET" on page 258.Check the interrupt, I/O, and base memory address of the board in question and make sure that the board settings match the shell you generated for that board. (Type "IPX I" to view the configuration information for the shell.) Make sure that the configuration does not conflict with any other hardware installed in the workstation. Reinstall the board and try again.Replace the network board with a board that you know works properly. Be sure the shell you are using is specific to the network board you are using. If the new network board does not work, replace the old board and check the cabling and the network connectors.Make sure that the cable is attached firmly to the network board and network connectors, and boot the workstation again.Install a cable you know works properly and reboot.Replace any network connectors (such as T-Connectors) and reboot the workstation.Log in when all other users are logged out. If you can log in from the workstation when you are the only user, you probably have a node address conflict.ID="FM99603"Application idxid="w8101"book="_idx" docset="nw312" tidref="i6910"ProblemsSome application problems can occur when a NetWare utility and a software application perform the same tasks. Other network problems occur only when a particular software application is used. These problems are discussed on the following pages.WIDTH="264"Section WIDTH="48"PageWIDTH="264"General installation problems WIDTH="48"IDREF="FM57922"436Compatibility problems (problems installing copy-protected  applications; problems installing incompatible software) IDREF="FM39830"438File I/O problems (problems accessing files from the hard disk,  caused by NetWare security or the workstation's  environment)IDREF="FM93985"439File and record locking problems (problems using multiuser  applications) IDREF="FM58211"443DOS utilities (problems using certain DOS utilities on  NetWare) IDREF="FM16775"444General failure (problems causing the workstation to "hang"  or be unresponsive) IDREF="FM25555"447Miscellaneous problems (problems with archiving/backup,  asynchronous communication, screen display, and search  paths)IDREF="FM27848"449ID="FM57922"General idxid="w8102"book="_idx" docset="nw312" tidref="i442"Installation ProblemsPossible Causesidxid="w8103"book="_idx" docset="nw312" tidref="i442"Insufficient rights were granted to the users in idxid="w8104"book="_idx" docset="nw312" tidref="i7013"trustee assignments.Insufficient rights were granted to the user installing the application.The application was installed too deep in the directory structure.The application files were copied to the network rather than installed with the application's installation program.All the idxid="w8105"book="_idx" docset="nw312" tidref="i442"application files were flagged SRo.The workstations' CONFIG.SYS files were not modified.Conflicts exist between the application's interrupt and the network boards installed in the workstations and the file server.Conflicts exist between the NET.CFG parameters and the CONFIG.SYS parameters.Search drives were not mapped in the users' login scripts or in the system login script.A single-user version of the software was installed.Possible SolutionsIf you can run the application when you are logged in as SUPERVISOR, but cannot run it when you are logged in as a user, you have not granted the right trustee assignments to the users.Create a group for the application and grant the group all rights to the application's directory. Delete one right from the trustee assignment, log in as a member of the group, and try to run the application. Users need at least Read, Create, Delete, Write, Modify, and File Scan rights if they are going to write to files.Some applications create temporary files. Map a search drive to the application and have users try running the application from a directory to which they have all rights.Some applications create the temporary files in the same directory as the data files. Users need at least Create, Delete, File Scan, and Read rights at the directory level for these types of applications. Some applications check for rights at the root directory when they are installed. You must log in as SUPERVISOR to install these types of applications.Not all application files can be flagged SRo. If the user needs to write to the file, flag the file SRw.Use the MAP ROOT command to make the application's current directory a root directory. Then try to run the application. (You may have to reinstall the application after you change the directory to a root directory.)If the MAP ROOT command does not solve the problem, try installing the application in a directory below the volume level. Install the application using the application's installation program. Some applications' files cannot just be copied to the network. They must be installed using the application's installation program.Read the application's installation documentation. Modify all workstation CONFIG.SYS files to handle the application's requirements (such as number of open files or additional memory required for the DOS environment).Make sure that the NET.CFG parameters do not conflict with the CONFIG.SYS parameters. If your application needs 50 open files, the CONFIG.SYS parameter (files = 50) and the NET.CFG parameter (file handles = 50) must be changed.Add search mappings to the user or system login script. If you create groups for your applications, use the IF...THEN command in the system login script to set up the search mappings for the users accessing the application.Contact the vender for a multiuser version of the software.ID="FM39830"Application Problems: idxid="w8106"book="_idx" docset="nw312" tidref="i442"CompatibilityThis section covers problems with copy-protected applications and incompatible applications running on NetWare.Novell does not condone the use of single-user applications in a network environment. Most applications have multiuser versions that should be purchased to avoid copy-protection violations and environment problems inherent in single-user applications.The Application is Copy Protected and Cannot be Installed on the File Server's Hard Disks.Possible CauseAbsolute DiskRead-INT 25h or Absolute DiskWrite-INT 26h are not valid function calls on NetWare. These interrupts transfer control directly to the DOS device driver. Since there are no local DOS device drivers for the file server's hard disks, the application will return errors when used on drives mapped to network hard disks.Possible SolutionThe application may require a "key diskette" to be placed in the workstation's local hard disk in order to run, or you may need to buy a multiuser version of the application.The Application is Supposed to Work on Dos v3.1 and Later, But It Does Not Recognize NetWare.Possible CausesSome applications use the Get Machine Name function call (5E00h Interrupt 21h) to check for the IBM PC Network Program and to ensure that all workstations on the LAN have a unique call number.Some applications use the PC LAN Network Program's LAN Installation Check (B800h Interrupt 2Fh) or the SHARE Installation Check (INT 2F) to see if the application is running on a LAN.Possible SolutionsIf the application uses the Get Machine Name function call, give the user's workstation a machine name in each login script, using the MACHINE="NAME" command. Replace NAME with a unique name (in all capitals) for each user. For example, add the following line to the user's login script:  MACHINE="HARRY'S STATION"If the application uses an installation check, load either idxid="w8107"book="_idx" docset="nw312" tidref="i6328"SHARE.COM or idxid="w8108"book="_idx" docset="nw312" tidref="i2909"INT2F.COM (Rev 2). INT2F.COM is located on the DOS / DOS ODI Workstation Services diskette.ID="FM93985"Application Problems: File I/OPossible CauseWhen accessing a file from the file server's hard disk, you may encounter problems with NetWare's security or the workstation's environment. See "book="concepts" docset="nw312"Security" inConcepts.Possible SolutionsNetWare's default flag settings for a file are Non-Shareable/Read Write. This default cannot be idxid="w8109"book="_idx" docset="nw312" tidref="i442"changed; however, you can modify a file's flag by using the FLAG command. For more information, see "book="utilref" docset="nw312"FLAG" in Utilities Reference.You can also set and modify flags using some applications.A File Has Been Flagged Shareable and Now It is Non-Shareable.Possible CausesThe file has been overwritten by a program that recreates the file. Often a file is read into a temporary working file for modification. When the modification is done, the application deletes the original file and renames the temporary file to the original filename. The original file attributes are lost and the modified file takes on the attributes of the temporary file.The application is setting the file attributes.Possible SolutionsFlag the file Read Only to prevent the file from being recreated or overwritten. Also, you can contact the software developer, who can create the temporary file with a Shareable flag.If the application is setting the file attributes, you may not be able to share the file.Increase the trustee rights to the file.An idxid="w8110"book="_idx" docset="nw312" tidref="i442"Application Cannot Find Files.Possible CausesThe user does not have sufficient rights to a directory.The file is being used by another workstation.The application cannot find the files because the search drives have been set up improperly.The user may not have adequate security rights given at the root directory for the application to find and open the file.Some applications look for a file in the default directory, and then start a search at the root directory. In DOS, the application goes to the root of the default hard disk (such as H:\), and then searches down repetitively. Possible SolutionsLog in as SUPERVISOR. If SUPERVISOR can run the program, the user does not have sufficient trustee rights to the directory. For an explanation of a directory's Inherited Rights Mask and trustee assignments, see book="concepts" docset="nw312"Concepts.Give the user sufficient trustee rights to the directory. You may need to change the Inherited Rights Mask for the directory, giving the user sufficient effective rights to use a file in this directory.Load MONITOR; then determine if the file is open and being used by another workstation. Some applications return an error of "file not found" when the file is being used by another workstation.No set directive exists on how low-level error codes should be handled by applications. Some applications have their own way of handling and interpreting DOS critical errors or NetWare's interrupt signals. This means that a DOS "file lock" may be interpreted by an application as a "file not found."Read the application's documentation concerning error messages. If you need more assistance, contact the application vender and ask how the low-level system error code is handled.Map a search drive to the directory containing the files the application will use. If the mapping solves the problem, add a search drive mapping to the login script.Run the program as SUPERVISOR. If you can run the application as SUPERVISOR, change the user's rights to include the entire directory path. Please note, however, that this solution sacrifices network security.Use SMODE to set a different search mode for the application. See book="utilref" docset="nw312"Utilities Reference.You Are Denied Writing Access to a File While Having idxid="w8111"book="_idx" docset="nw312" tidref="i442"Rights in the Directory.Possible CausesThe file has been flagged as Read Only and cannot be written to.You do not have sufficient rights in the directory. If the file does not exist on the hard disk you are using, the shell may find the file in one of the search drives. If the file is found on a network drive, NetWare checks for appropriate rights. If you do not have sufficient rights in that directory, you cannot write to the file.Some applications may expect the NetWare v2.x rights convention. Since NetWare v3.1x rights are different, the application may not work correctly.Possible SolutionsChange the file's flag to Read Write.If you supply the filename to the application, preface the filename with a directory path. This shuts off the shell's search drive capability. If, on the other hand, you are not required to supply the filename to the application, you must copy the file into your current directory.Contact the application manufacturer for an upgraded version of the application that is compatible with NetWare v3.1x.ID="FM58211"Application Problems: idxid="w8112"book="_idx" docset="nw312" tidref="i442"File and Record idxid="w8113"book="_idx" docset="nw312" tidref="i3378"LockingBecause file sharing must be regulated in a multiuser environment, file and record locking attributes control users' idxid="w8114"book="_idx" docset="nw312" tidref="i442"access to information. This section lists some of the file and record locking problems you may encounter while running software applications on a NetWare network.The File or Record Locking is Not Working.Possible CausesThe application is using DOS 3.1 or later file locking functions. However, the workstation did not boot with DOS 3.1 or later; therefore, the application cannot use this locking method.The application is using the logical record lock or semaphore-locking function, but the application is being accessed from an attached file server.Possible SolutionsIf the application requires DOS 3.1 or later to perform its record-locking functions, be sure that the workstation is booted with DOS 3.1 or later.Check with the application vender to see if the application can be run in a network environment.Do not use the application from a search drive if you are attached to other file servers. Log in directly to the file server rather than attaching to the file server across an internetwork. All workstations using the application must be logged in to the file server in order to use logical record locking.If the application is not written for a multiserver environment, do not map network search drives to the application's directory. Have each user map a regular drive to the application and execute the application from that drive.You Have a Contaminated Database.Possible CausesThe hard disk may be physically damaged.A power failure or spike may have occurred.The application uses a record/file locking algorithm that does not take into consideration a multiple file server environment.Possible SolutionsUse VREPAIR to find and repair inconsistencies in the FATs. You may also need to run BINDFIX to fix the bindery problems. IDREF="FM32162"see "VREPAIR" on page 348 and "book="utilref" docset="nw312"BINDFIX" in Utilities Reference.If VREPAIR and BINDFIX do not solve the problem, make sure you have a recent backup copy of the entire hard disk. Run the surface test option in INSTALL. You can run a nondestructive test (which preserves all data) or a destructive test (which destroys all data). IDREF="FM11821"See "INSTALL" on page 47.Make sure all workstations execute the program from the same default drive on the same file server.If the database does not have its own protection against incomplete updates, use TTS to protect the database files. For information, see "book="concepts" docset="nw312"TTS" in Concepts.ID="FM16775"Application Problems: idxid="w8115"book="_idx" docset="nw312" tidref="i442"DOS UtilitiesThis segment lists some of the problems you may encounter while using DOS commands on a NetWare network.The DOS v3.1 and Later idxid="w8116"book="_idx" docset="nw312" tidref="i1669"BACKUP Command Will Not Back Up Files Flagged Shareable.Possible CauseThe DOS BACKUP command in DOS 3.1 and later is not compatible with the Shareable flag in NetWare.Possible SolutionFlag files Non-Shareable or use NetWare's NBACKUP utility to back up data.When You Are on a Hard Disk (Local or Network) and Type "DIR volume name", the Hard Disk Becomes Mapped to the Volume.Possible CauseWhen you use the idxid="w8117"book="_idx" docset="nw312" tidref="i1669"DOS DIR command with a volume name, the drive you are on is automatically mapped to the root, or volume, name.Possible SolutionsUse MAP to remap the drive.Do not use volume names in the DIR command.When Path is Used, All the Search Drives are Lost.Possible CauseThe DOS idxid="w8118"book="_idx" docset="nw312" tidref="i1669"PATH command deletes and overwrites NetWare search drives.Possible SolutionsUse the NetWare MAP command instead of PATH. Reboot the workstation or use MAP to set up the search drives again.RENAME Will Not Work on NetWare Directories, But it Will Work on Files.Possible CauseThe idxid="w8119"book="_idx" docset="nw312" tidref="i1669"RENAME command is a DOS command.Possible SolutionUse the NetWare RENDIR utility to rename NetWare directories.You are Receiving Error Messages Telling You to Load SHARE.COM.Possible CauseYou have not loaded SHARE.COM. Some data synchronization primitives (extended opens and DOS record locking) require that SHARE.COM be loaded. Possible SolutionUnder NetWare, it is not necessary to load idxid="w8120"book="_idx" docset="nw312" tidref="i6328"SHARE.COM. Instead, load a much smaller program called idxid="w8121"book="_idx" docset="nw312" tidref="i2909"INT2F.COM (Rev 2). This program simulates the presence of SHARE.COM in memory and supports the SHARE installation check. INT2F.COM is located on the DOS / DOS ODI Workstation Services diskette.CHKDSK Does Not Function When Used on a Network Hard Disk.Possible Causeidxid="w8122"book="_idx" docset="nw312" tidref="i1669"CHKDSK is a DOS command.Possible SolutionCHKDSK works only on a DOS hard disk (local hard disk). Use NetWare VOLINFO or CHKVOL to check the status of a NetWare volume.ID="FM25555"Application Problems: General FailureGeneral failure problems occur when the application or workstation hangs or when the computer does not respond to a request made from the application.The Application idxid="w8123"book="_idx" docset="nw312" tidref="i442"Hangs.Possible CauseThe application uses a software interrupt that is also used by NetWare.Possible SolutionIf you have an interrupt conflict, call your local vender or Novell for assistance. No industry policies exist to prevent interrupt conflicts.The Program Hangs After a Netware Message is Sent to the idxid="w8124"book="_idx" docset="nw312" tidref="i7493"Workstation.Possible CausesThe application takes over the keyboard and monitor, but the <Ctrl><Enter> prompt from the NetWare message is not displayed.The monitor is in graphics mode.Possible SolutionPress <Ctrl><Enter> to free up the keyboard. If this does not work, reboot. Then use CASTOFF to prevent messages from being sent when you are using that application. Use CASTON when you exit the application and want to receive messages again. See "book="utilref" docset="nw312"CASTOFF" and "book="utilref" docset="nw312"CASTON" in Utilities Reference.Several Users Are Working in an Application, But Another User is Denied idxid="w8125"book="_idx" docset="nw312" tidref="i442"Access.Possible CausesThe application programmer is limiting the number of users through the use of semaphores. For example, if an application has a limit of five users, the semaphore limit will prevent a sixth user from accessing the application. Sometimes the workstation hangs because of the sixth user's attempt to access the application. Sometimes the application appears to hang until the fifth user exits the application, making room for the sixth; then the sixth workstation can enter the application, and the application continues working.A communication resource limitation may exist if the application requires NetBIOS or NetWare's NetBIOS emulator. This problem does not occur very often, because NetBIOS usually has enough resources.Possible SolutionsMake sure you have a site license for the application and stay within the limit of that license. If a site license is not available, the application may have a user limitation. Contact the application vender about user limitations; and, if necessary buy an extended license.Check with the application developer for information on resource limitations with NetBIOS.An Application Periodically idxid="w8126"book="_idx" docset="nw312" tidref="i442"Hangs For a Time Before It Continues. This Occurs at Different Times with No Apparent idxid="w8127"book="_idx" docset="nw312" tidref="i7493"Pattern.Possible CausesThe application may wait until the record or file is released from use. Instead of returning an error, the application waits until the record or file is free. This wait could be any amount of time.Most applications try to read a locked file a certain number of times before sending an error message. This, too, can give the impression that the workstation is hanging.The network is not installed properly. The operating system may not have enough memory for file caching. Inadequate file caching can make the file server appear to hang for a time.Possible SolutionsContact the application developer and ask how the application handles locked files. Ask the developer for a solution.Load MONITOR and check the amount of memory available for the cache buffer pool. If the pool is near 20%, install more memory in the file server.Load MONITOR and check "Connection Information." If the user is waiting for a record or file, the connection status should be "Waiting."ID="FM27848"Application Problems: MiscellaneousAdditional applications-related problems that may occur on a file server are listed here.Trustee idxid="w8128"book="_idx" docset="nw312" tidref="i7013"Rights Are Lost in the Backup or Restore Process.Possible CauseYou may be using a backup program not written for NetWare. The backup program may be written for either a single-user environment or a non-NetWare system environment.Possible SolutionUse a NetWare-compatible program. If the backup program is not written for NetWare, the bindery and other essential security features will be lost, and the backup program will not be able to restore NetWare.Characters Coming into the Serial Port are Being Lost.Possible CauseThe baud rate is too high. The characters are coming into the serial port faster than they can be picked up. When a character arrives at the port, the operating system gives an interrupt to pick up the character. All characters not picked up immediately are overwritten by the next incoming character.This problem occurs when the operating system turns off the hardware interrupts, thereby not allowing the CPU full control. Because the interrupts are turned off, incoming characters are not acknowledged. Interrupts are turned off whenever the operating system handles other requests from the network interface board, or when it handles interrupts from within the system.Possible SolutionsSlow the baud rate to 2400 baud. This should be enough to avoid interrupts and prevent incoming character loss.Purchase serial port buffers. Serial port buffers allow incoming characters to wait until the operating system can handle them. Port buffers can be purchased from various software venders.The File Server idxid="w8129"book="_idx" docset="nw312" tidref="i2096"Screen Displays Garbage Characters.Possible CausesTwo workstations have the same station (node) address. All file servers and workstations on the same cabling system must have unique station addresses.The data being accessed is corrupted.Possible SolutionsCheck the cabling system for bad connections.Check the file server and workstation addresses for duplicate address numbers.Check the workstation records to ensure that no two workstations have the same station address. If you do not have a record of workstation station addresses, log in all workstations and execute the USERLIST /A command on one workstation to see the station address listings.If the data is corrupted, run VREPAIR. Before using VREPAIR, back up all file server data. You may also want to keep the most recent backup that was made before the data was corrupted. IDREF="FM32162"See "VREPAIR" on page 348.ID="FM33727"TTS idxid="w8130"book="_idx" docset="nw312" tidref="i6910"idxid="w8131"book="_idx" docset="nw312" tidref="i6864"ProblemsTTS keeps backout information in a special system file, used only by the NetWare operating system. (For an explanation of how TTS works, see "book="concepts" docset="nw312"TTS" in Concepts.) TTS events are logged in idxid="w8132"book="_idx" docset="nw312" tidref="i7049"TTS$LOG.ERR, a file located in the root directory of volume SYS:. The TTS$LOG.ERR file contains information about what happened with particular transactions when a failure occurred; however, TTS does not actually use this file for backing out data. This file shows when TTS was enabled or disabled; it also gives pertinent dates, times, file offsets, record sizes, record data before the backout, and record data from the original copy of the data (see the following figure).LBL="3-5"ID="FM93065"TTS$LOG.ERR file informationFILE="n312sa98.pbm"By holding workstation record locks until the end of a transaction, TTS avoids database corruption that can occur when workstation applications release record locks before transactions are complete. However, holding workstation record locks until the end of a transaction allows for the possibility of deadlocks between workstations using some applications. If the application uses records that can be unlocked in the middle of transactions to avoid deadlocks, then TTS introduces the possibility of deadlocks for that application (by holding record locks until the end of a transaction). A deadlock means that the two workstations involved hang. To fix this problem, reboot both workstations; TTS can still maintain database integrity by backing out the transactions that were in process. Although rebooting the workstations is not desirable, it allows TTS to maintain the integrity of the database.If TTS is automatically disabled because volume SYS: (the TTS backout volume) is full, you must free up disk space on SYS:. Under normal conditions, TTS requires only 1 MB of disk space to track all transactions. If you are adding or deleting large database records (of more than 1 MB each), you need to have free space on SYS: equal to the size of the largest added or deleted record. Once you have freed up sufficient disk space on SYS:, you can enable TTS with ENABLE TTS. If you want to receive a warning when the free space on SYS: is less than you need for TTS, refer to the volume parameters described under "SET" (beginning on page IDREF="FM70995"264).If TTS is automatically disabled because the file server does not have enough free memory, you must increase the memory available to TTS in one of the following ways:Unload file server modules you do not need currently (such as INSTALL or MONITOR). You can also dismount volumes to free up file server memory. Use ENABLE TTS again to see if you have freed up enough memory for TTS. If enough free memory is available, TTS enables; if not, it remains disabled.Add more memory to the file server. TTS requires about 40 bytes to track each transaction. TTS can track up to 10,000 transactions; at peak transaction load, the file server would require no more than 400 KB of memory to track transactions. After you have installed sufficient memory, the file server enables TTS automatically when it boots.If TTS is disabled then the file server fails before all transactions have been written to disk, the information in the TTS backout file is unreliable. You should not back out any transactions. If TTS is shut down, the file server cannot track when transactions are made. If TTS is allowed to back out any transactions (after being enabled), it could incorrectly overwrite information that was changed after TTS was disabled. You can reduce the risk of this situation by attaching a UPS to your file server and disk subsystems.If the file server fails, incomplete transactions are backed out when the file server comes up again. However, transactions started before the file server failed may have been written to file server cache memory and not to disk. Since a transaction is not marked "completed" by the operating system until it has been written to disk, the file server would back out the transaction, even though the workstation application considered it "completed."If the "TTS Abort Dump Flag" IDREF="FM73882"(see "SET" on page 258) is set to ON, a copy of the original data from the transaction is written to the TTS$LOG.ERR file in the root directory of SYS:. You can compare this information (which would have been restored to the database) with what was entered at the workstation to determine whether the information needs to be re-entered from the workstation.ID="FM68419"If You Need More idxid="w8133"book="_idx" docset="nw312" tidref="i6910"HelpIf you cannot find the solution to a network problem in this section, call your Novell Authorized Reseller. Before calling for assistance, make sure you have the configuration information from the "File Server Worksheet" and the "Workstation Configuration Worksheet" available. Be prepared to describe the problem and the details of each attempt you have made to solve the problem.If you receive a solution from a source other than your Novell Authorized Reseller, please inform Novell of the problem and solution. This will assist us in updating this manual and offering timely answers to others with similar problems.LBL="4"ID="FM85438"Using Novell ElectroTextOverviewidxid="w8134"book="_idx" docset="nw312" tidref="i930"idxid="w8135"book="_idx" docset="nw312" tidref="i4676"idxid="w8136"book="_idx" docset="nw312" tidref="i4676"idxid="w8137"book="_idx" docset="nw312" tidref="i4676"idxid="w8138"book="_idx" docset="nw312" tidref="i4676"The Novell ElectroText(tm) viewer allows you to read NetWare user manuals on your computer screen. All of the manuals in the NetWare v3.12 manual set are available online.This chapter documents the use of Novell ElectroText only on the Windows and OS/2 platforms. Viewer Featuresidxid="w8139"book="_idx" docset="nw312" tidref="i4676"The Novell ElectroText viewer gives you the following advantages over printed documentation:Scroll gradually or sequentially through a book.Move quickly from one part of the book to another by selecting a section from the table of contents outline.Move quickly to another part of the book or a different book to follow a cross-reference.Return or step back to sections of the book that you previously viewed.Search for specific words or phrases in a library, bookshelf, or book.Print book sections on demand.Open several books at one time.Basic ComponentsThe Novell ElectroText viewer contains several components. These components are summarized below and described in detail later in this chapter. Library Windowidxid="w8140"book="_idx" docset="nw312" tidref="i4726"The library window lists the bookshelves that are available in the library. The library generally corresponds to one company's set of documentation. The window's title bar will show "Novell Documentation." See IDREF="FM32704""Using the Library Window" on page 459 for more information about this window.Bookshelf Windowidxid="w8141"book="_idx" docset="nw312" tidref="i4718"The bookshelf window lists the books available for you to read. The bookshelf corresponds to a set of documentation. The window's title bar will show "NetWare v3.12 Documentation." See IDREF="FM29551""Using the Bookshelf Window" on page 461 for more information about this window.Book Windowidxid="w8142"book="_idx" docset="nw312" tidref="i4710"After you have selected a book to read, the book window displays the book's table of contents outline and text. The title of the book will be in the window's title bar. You can select a section of the book to read from the outline, or you can page through the book sequentially. The text of the book also contains cross-references; clicking on one of these moves you to the referenced section of the book or another book. See IDREF="FM27883""Using the Book Window" on page 465 for more information about this window.Search Fieldidxid="w8143"book="_idx" docset="nw312" tidref="i4734"A "Search" field at the bottom of the library, bookshelf, and book windows allows you to search for words or phrases that appear in the library, bookshelf, or book. Both simple and advanced (keyword or Boolean) searches are supported. After you search for the word or phrase, the library window displays the number of matches in each bookshelf, the bookshelf window displays the number of matches in each book, and the outline in the book window shows which sections of the book include matches. See IDREF="FM35807""Using the "Search" Field" on page 471 for more information about searching.Installing Novell ElectroTextidxid="w8144"book="_idx" docset="nw312" tidref="i4676"idxid="w8145"book="_idx" docset="nw312" tidref="i2869"Novell ElectroText can be installed on either a NetWare server or a local hard disk. In addition, you must set up a workstation to view Novell ElectroText.Installing on a NetWare ServerThe procedure for installing Novell ElectroText on a NetWare server is described in "book="install" docset="nw312"Copy NetWare Files" in Chapter 2 of Installationand Upgrade. This procedure involves copying the Novell ElectroText files from the CD-ROM distribution disk as a file set to your server's hard disk during the NetWare installation process. Installing on a Local Hard DiskThe procedure for installing Novell ElectroText on a local hard disk is described in "book="install" docset="nw312"Installing Novell ElectroText" in Appendix B of Installationand Upgrade. This procedure involves copying the Novell ElectroText files from the CD-ROM distribution disk to your hard disk. Running From the CD-ROMThe procedure for running Novell ElectroText directly from the CD-ROM disk is discussed in "book="install" docset="nw312"Installing Novell ElectroText" in Appendix B of Installationand Upgrade. This procedure involves setting up your workstation to use the Novell ElectroText files directly from the CD-ROM.Setting Up a Windows or OS/2 Workstation for ViewingThe procedure for setting up a Windows or OS/2 workstation for viewing Novell ElectroText is described in "book="install" docset="nw312"Installing Novell ElectroText" in Appendix B of Installationand Upgrade. This procedure involves copying setup files to the workstation's WINDOWS directory and creating a Windows program group and icon. ID="FM32704"Using the idxid="w8146"book="_idx" docset="nw312" tidref="i4726"idxid="w8147"book="_idx" docset="nw312" tidref="i3198"Library WindowAccessing the idxid="w8148"book="_idx" docset="nw312" tidref="i4726"Library WindowProcedureStart the Novell ElectroText viewer by selecting the "Novell ElectroText" icon on your workstation desktop. The first window that appears is the library window, as shown in the following figure. LBL="4-1"ID="FM28169"The ET library windowFILE="n312sa5a.pbm"The Novell ElectroText library is structured hierarchically; the library contains bookshelves which, in turn, contain books. A bookshelf usually contains books that are related to each other; for example, the NetWare v3.12 bookshelf contains all the books in the NetWare v3.12 manual set.ID="FM90546"Moving to a Different idxid="w8149"book="_idx" docset="nw312" tidref="i4726"LibraryWhen you first open the library window, the Novell ElectroText viewer opens to a default library for NetWare documentation. To move to another library, do the following.ProcedureSelect "Choose Library" from the "File" menu.Select the name of a library from the list.Click on the "Visit" button.To specify a different default library, see IDREF="FM44754""Default Setup and Configuration Files" on page 486.ID="FM29551"Using the idxid="w8150"book="_idx" docset="nw312" tidref="i4718"idxid="w8151"book="_idx" docset="nw312" tidref="i723"Bookshelf WindowOpening a idxid="w8152"book="_idx" docset="nw312" tidref="i4718"BookshelfProcedureChoose the library that contains the bookshelf you want to select.Select the bookshelf's icon (or by highlight the icon and select "Open" from the "File" menu). The bookshelf window appears displaying icons for each of the books in the bookshelf, as shown in the following figure.LBL="4-2"ID="FM43096"The ET bookshelf windowFILE="n312sa5b.pbm"ID="FM27864"Opening a idxid="w8153"book="_idx" docset="nw312" tidref="i4676"BookProcedureChoose the bookshelf that contains the book you want to open.Open the book by selecting the book's icon (or by highlighting the book's icon and selecting "Open" from the "File" menu).Moving to a idxid="w8154"book="_idx" docset="nw312" tidref="i4718"Different BookshelfAfter you open a bookshelf, you can move to another bookshelf by doing the following. ProcedureReturn to the library window by closing the bookshelf window (or by selecting "Choose Library" from the "File" menu, selecting the name of a library, and then choosing the "Visit" button).Select a new bookshelf's icon (or select the icon and then select "Open" from the "File" menu).ID="FM94228"Searching Bookshelves and BooksYou can search the contents of any or all bookshelves in the library window and any or all books in the bookshelf window. See IDREF="FM35807""Using the "Search" Field" on page 471 for more information about searching.ID="FM33886"Setting Preferencesidxid="w8155"book="_idx" docset="nw312" tidref="i5134"idxid="w8156"book="_idx" docset="nw312" tidref="i4726"Set preferences to specify how things appear in the Novell ElectroText viewer by doing the following. ProcedureSelect "Preferences" from the "File" menu of the library window. The Preferences window appears, as shown in the following figure.LBL="4-3"ID="FM77272"The ET Preferences windowFILE="n312sa5c.pbm"The settings you make here will apply to all books you open from the library or bookshelf windows. To set preferences for a single book, select "Preferences" from the "File" menu in the book window, and then complete Steps 2 and 3.Change the preferences on the screen according to the following explanation.Outline Placement: The book window shows both the outline and the text of the book. You can place these either side by side or one above the other. Click on the appropriate button to designate the placement of the outline in relationship to the text.Search Area: Specify whether you want the "Search" field placed automatically at the bottom of the library or bookshelf window every time the window opens. To make the "Search" field appear at the bottom when the window opens, select the "Visible" box. (You can override this setting and show or hide the "Search" field by choosing "Visible" from the "Search" menu.)You can also specify whether the viewer uses the advanced query language. If you do not select this, the viewer uses a simple search; the entire text that is entered is searched for. If you select this box, the viewer uses an advanced search which allows use of Boolean keywords. See IDREF="FM35807""Using the "Search" Field" on page 471 for more information.Book Window Size" You can specify whether the book window is maximized (fills the entire screen) when it opens. Select the "Maximized" box to make the book window maximized when it opens. (Optional) Save these preferences for future use by selecting the "Save these preferences" box. Exiting the idxid="w8157"book="_idx" docset="nw312" tidref="i4676"ViewerProcedureTo close all open books and exit the viewer, select "Exit" from the "File" menu. You are returned to the Windows desktop.ID="FM27883"Using the idxid="w8158"book="_idx" docset="nw312" tidref="i4710"idxid="w8159"book="_idx" docset="nw312" tidref="i721"Book WindowOpening a idxid="w8160"book="_idx" docset="nw312" tidref="i4710"Book WindowProcedureChoose the bookshelf that contains the book you want to open.Select the book's icon from the bookshelf. The book window opens, as shown in the following figure. The different parts of the book window are explained in the following sections.LBL="4-4"ID="FM85942"The ET book windowFILE="n312sa5d.pbm"The look of the window is determined by preferences that are set using the "Preferences" option in the library window's "File" menu and the "Preferences" option in the book window's "File" menu.ID="FM23525"Using the idxid="w8161"book="_idx" docset="nw312" tidref="i4710"Outline The outline portion of the book window displays the hierarchical outline of the book. You can use the outline to move to different sections of the book. Using the Outline to NavigateWhile a book is being displayed, the section heading corresponding to the currently visible portion of the book text is indicated with a black pointer in the left margin.ProcedureTo move to another section of the book's text, click on the corresponding section heading in the outline. The text portion of the book window displays that section of the text, and the pointer in the outline moves to show your new location in the book.You can easily return to your previous position in the text by using the "Go Back" option in the "History" menu.ID="FM84935"Expanding/Collapsing the Outlineidxid="w8162"book="_idx" docset="nw312" tidref="i4676"You can expand or collapse the book's outline either globally or selectively. LBL="4-1" INLINE="F"Expanding/Collapsing the outlineWIDTH="96"To expand/collapseWIDTH="216"Do thisWIDTH="96"The entire outlineWIDTH="216"Select "Outline level" from the "View" menu;  then select a level number.For example, to expand or collapse the outline so  that all headings down to a third-level head are  displayed, select "3" from the "Outline level" list.A section of the  outlineClick on the plus (+) or minus (-) sign next to the  section title.The plus sign indicates that this section in the  outline has subsections. To expand the section  and display these subsections in the outline, click  on the plus sign.The minus sign indicates that this section in the  outline has been expanded and its subsections  are displayed. To collapse the section and hide its  subsections, click on the minus sign.Modifying the Outline Displayidxid="w8163"book="_idx" docset="nw312" tidref="i4676"The book can display outlines for the idxid="w8164"book="_idx" docset="nw312" tidref="i4676"table of contents (TOC), idxid="w8165"book="_idx" docset="nw312" tidref="i4676"list of figures, and idxid="w8166"book="_idx" docset="nw312" tidref="i4676"list of tables. The outline can also be placed at different locations on the screen, and can take up different proportions of the screen. The following table explains how to modify the outline displayLBL="4-2" INLINE="F"Modifying ET outline displayWIDTH="120"If you want toWIDTH="192"ThenWIDTH="120"Display a different  outline (TOC, list of  figures, or list of tables).WIDTH="192"Select "Outline" from the "View" menu,  and then select the outline you want to  view.Display only the outline  (hide the text).Select "Outline Only" from the "View"  menu.Display only the text  (hide the outline).Select "Text Only" from the "View" menu.Display both the text  and the outline.Select "Outline and Text" from the "View"  menu.Place the outline at a  different location of the  screen (top, bottom,  left, or right).Select "Preferences" from the "File" menu,  and then select the appropriate box.Modify the proportion of  the screen used for  displaying the book's  outline.Use the mouse to drag the border  separating the outline from the text.Setting idxid="w8167"book="_idx" docset="nw312" tidref="i5134"idxid="w8168"book="_idx" docset="nw312" tidref="i4710"PreferencesYou can specify how things appear in the Novell ElectroText viewer by setting preferences. ProcedureSelect "Preferences" from the "File" menu of the book window. These settings will apply only to this book. To set preferences for an entire library, select "Preferences" from the "File" menu in thelibrary window.Set preferences as desired.See IDREF="FM33886""Setting Preferences" on page 463 for a description of the preference fields.Save these preferences for future use by selecting the "Save these preferences" box. Searching BooksYou can search the contents of the book. See IDREF="FM35807""Using the "Search" Field" on page 471 for more information about searching.The Book Text WindowThe text portion of the book window displays the text of the opened book, cross-references, and icons representing graphics and tables. Navigating through the Bookidxid="w8169"book="_idx" docset="nw312" tidref="i4710"You can move through the book's text using either the scroll bar or the outline. LBL="4-3" INLINE="F"Navigating through ET bookWIDTH="72"To navigate  usingWIDTH="240"Do thisThe outlineClick on the section heading or table/figure number  that you want to go to; the book's text jumps to that  position. See IDREF="FM23525""Using the Outline" on page 466 for more  information.The scroll  barDrag the scroll box up or down the bar, or click on the  arrows at the top and bottom of the bar. You can also  use the Up- or Down-arrow keys (or <PgUp> and  <PgDn>) on your keyboard to scroll through the book.Viewing Tables and Graphicsidxid="w8170"book="_idx" docset="nw312" tidref="i4676"Tables and idxid="w8171"book="_idx" docset="nw312" tidref="i4676"graphics (illustrations) are represented by icons preceded by the table or figure number and its caption. These icons are illustrated in the two following figures.LBL="4-5"ID="FM73731"The ET table iconFILE="n312sa5e.pbm"LBL="4-6"ID="FM87587"The ET graphic iconFILE="n312sa5f.pbm"ProcedureView tables and graphics by selecting the icon you want. Another window opens displaying the table or graphic. Use standard procedures for your window environment to resize, move, and close the table or graphic window. Using Cross-Referencesidxid="w8172"book="_idx" docset="nw312" tidref="i4676"A cross-reference to another section in either your current book or another book is represented by colored or underlined text (depending on your monitor type). ProcedureSelect the text of the referenced section (in quote marks) or the referenced manual (in italics). Where the cross-reference jumps to depends on the reference:If the cross-reference is to a section in the same book, the text of the book moves to that new section. After reading the cross-referenced section, you can return to your original position in the book by selecting "Go Back" from the "History" menu.If the cross-reference is to a section in another book, the other book opens in another window and the specified section is displayed. After reading the cross-referenced section, you can close this new window to return to your position in the original book. You can also toggle between the books by pressing <Alt><Tab> (or by clicking on any exposed part of a book to bring it to the front again).If the cross-reference is to another book, without a section being specified, the other book opens in a new window and the top of the book is displayed. After reading the cross-referenced book, you can close this new window to return to your position in the original book. You can also toggle between the books by pressing <Alt><Tab> (or by clicking on any exposed part of a book to bring it to the front again).Using the "History" MenuProcedureSelect "Go idxid="w8173"book="_idx" docset="nw312" tidref="i4676"Back" from the "History" menu to return, step by step, back over the sections of text you followed to get wherever you currently are. This feature is useful, for example, if you are following cross-references from one section to another. "Go Back" will not return you to a different book.ID="FM35807"Using the "Search" Fieldidxid="w8174"book="_idx" docset="nw312" tidref="i4734"idxid="w8175"book="_idx" docset="nw312" tidref="i6174"The "Search" field gives you the ability to search for words or phrases that appear in a bookshelf or book. The "Search" field appears at the bottom of a library or bookshelf window when it opens if you specified this on the "Preferences" screen for the library or the book. (Select "Preferences" from the "File" menu; then check the "Visible" box under "Search Area.") You can also show or hide this field in the book window by toggling "Visible" in the "Search" menu.ID="FM79989"What You Can SearchYou can search different parts of the library depending on which window is active and what icons are displayed in the window.Search idxid="w8176"book="_idx" docset="nw312" tidref="i4726"bookshelves in the library. If the library window displays bookshelf icons, you can search for instances of words or phrases in any or all bookshelves in the library. The search results are displayed as a number next to each icon representing the number of matches in that bookshelf. To look at the search results in an individual book, open the bookshelf and then the book. The number of matches in each section is displayed in the book's table of contents. Select the section title, and/or select the "Next" button to go to the next match.Search idxid="w8177"book="_idx" docset="nw312" tidref="i4718"books in the bookshelf. If the bookshelf window displays book icons, you can search for instances of words or phrases in any or all books in the bookshelf. The search results are displayed as a number next to each icon representing the number of matches in that book. To look at the search results in an individual book, open the book. The number of matches in each section is displayed in the book's table of contents. Select the section title, or select the "Next" button to go to the next match.Search a idxid="w8178"book="_idx" docset="nw312" tidref="i4710"book in the bookwindow. If the book window displays the text of an individual book, you can search for instances of words or phrases in just that book. The search results are displayed as a number next to section in the table of contents. To look at the search results in the book, select the section title, or select the "Next" button to go to the next match.Choosing What to SearchA box around a bookshelf or book icon indicates that the bookshelf or book will be included in the search. To add or delete a bookshelf or book from the list of those to be searched, do the following.ProcedureOpen the "Search" menu from either the library or bookshelf window.If you want to search all books, check "Search All" and proceed with the search (skip IDREF="FM90372"Step 3 and see IDREF="FM58291""Doing a Simple Search". ID="FM90372"If you want to search only some of the books, make sure "Search All" is not checked. Then hold down the <Shift> key while selecting a bookshelf's or book's icon to either add or delete it from the search list (add or delete the box around the icon). You can also add or delete bookshelves or books from the search list by using the "Add to Search" and "Remove from Search" options on the "Search" menu. ID="FM58291"Doing a Simple Searchidxid="w8179"book="_idx" docset="nw312" tidref="i4734"To search for a word or phrase in a bookshelf or book, do the following:ProcedureEnter the word or phrase to be searched for in the "Search" field at the bottom of the library, bookshelf, or book window.Remember the following when you enter a word or phrase for searching:The search ignores case.The search ignores line breaks in the text.No more than 10 words may be entered in a search phrase.Any letter or number may be used in a search word or phrase. The following characters cannot be used in a search word or phrase:  < > ( ) =Common words such as "and," "the," and "for" are not indexed. If you include them in your search, they are treated as wildcards that match any word at that position in the search phrase.Do not use Boolean expressions in a simple search. If you want to include keywords or Boolean expressions in your search, see IDREF="FM32520""The Advanced Query Language" on page 480.Press <Enter> (or choose "Next"). The viewer searches for the exact word or phrase you entered. To see the results of your search, continue with the next section.Viewing Search Resultsidxid="w8180"book="_idx" docset="nw312" tidref="i4734"If you started the search from the library window, the number of matches in each bookshelf appears in the library window. Open a bookshelf to view the number of matches in each book.If you started the search from the bookshelf window, the number of matches in a book appears in the bookshelf window, as shown in the following figure. Open a book to view the location of the matches in that book.LBL="4-7"ID="FM41751"Search results in the ET bookshelf windowFILE="n312sa5g.pbm"ProcedureOpen a book that contains matches.Each match in the book is highlighted in the book text window, and the number of matches in each section of the book appears next to the section's title in the outline window. See the following figure.LBL="4-8"ID="FM78659"Search results in the ET book windowFILE="n312sa5h.pbm"Do one or more of the following to help you find a match.(Optional) Expand the outline hierarchy (see IDREF="FM84935""Expanding/Collapsing the Outline" on page 466) to help pinpoint the exact sections containing the matches. To move to a section of the book, choose the section title in the TOC outline.To move to the next match, choose "Next."To move to the previous match, choose "Previous."To start a new search, choose the "Clear" button; then enter a new search word or phrase.To repeat a previous search, see the following section.ID="FM41968"Using Search "History"idxid="w8181"book="_idx" docset="nw312" tidref="i4734"idxid="w8182"book="_idx" docset="nw312" tidref="i2663"To go back and perform a search again, use the "Search History" dialog box. ProcedureSelect "History" from the "Search" menu. The dialog box lists the searches that you have made in this library or book, as shown in the following figure. LBL="4-9"ID="FM70050"The ET Search History dialog boxFILE="n312sa5i.pbm"Select the search that you would like to perform again, and then click on "Use."The word you selected is placed in the search field.For example, you can search for the word "netbios"; then for the word "cabling"; then for the phrase "drive *"; and then for the word "server." Later, you can go back and look at the results of a previous search ("cabling") again. You would select "Show History" from the "Search" menu, select "cabling" from the list, and then click on "Use." Using the Search "Word List"idxid="w8183"book="_idx" docset="nw312" tidref="i4734"The "Word List" dialog box displays a list of words in the current book. Use this list to help you think of a word to search for.Procedure Select "Word List" from the "Search" menu. Select a word from the list by using the mouse or by typing the first letter or letters of the word. Select "Use." The word is copied into the "Search" field. Proceed with the search.See IDREF="FM58291""Doing a Simple Search" on page 473.ID="FM60706"Using the Search "Forms"idxid="w8184"book="_idx" docset="nw312" tidref="i4734"Use a search form to specify what parts of the books to search. A search form allows you to specify, for example, that you want to search for words or phrases appearing in just headings, just table captions, just procedures, etc. ProcedureSelect "Forms" from the "Search" menu. The menu that appears is shown in the following figure.LBL="4-10"ID="FM12599"The ET Search Forms menuFILE="n312sa5j.pbm"Select the name of the search form to use. All searches in this book will use this form until you select a different form.If you select the "Standard" search form searches are made of the entire text of the book, including the book text, sections headings, figure and table captions, etc. Other search forms restrict searches to just a specific part of the book, such as table captions.The forms that are available depend on the book that you have open. ID="FM32520"The Advanced Query Languageidxid="w8185"book="_idx" docset="nw312" tidref="i4676"Query language defines what words or characters may be used in a search word or phrase. The easiest way to perform a search is to enter a simple word or phrase to search for. In addition to doing a simple search, you can also enter words or characters to do wildcard, Boolean, and restrictive searches by specifying to use the advanced query language.To perform advanced searches, check the "Advanced Query Language" box in the "Preferences" dialog box (see IDREF="FM33886""Setting Preferences" on page 463). The following sections are valid only if you have done so. If this is not checked, the viewer searches for exactly the text that you enter; your search text effectively has quotation marks placed around it. Even if you have set the "Advanced Query Language" on the "Preferences" screen, you can perform a simple search by enclosing your search text in quotation marks.Using Wildcard Searchesidxid="w8186"book="_idx" docset="nw312" tidref="i4734"idxid="w8187"book="_idx" docset="nw312" tidref="i7440"You can include wildcard characters in your search to specify patterns of words or phrases. Question MarkThe question mark (?) matches occurrences of any single character. For example  s?tmatches sit, set, sat, etc. And   net?matches NET3 and NETX, but not network or NetWare.Square BracketsSquare brackets ([ ]) match specific characters or ranges or characters. For example  s[ae]tmatches sat and set but not sit. And   net[0-9]matches NET3 and NET4, but not NETX.AsteriskThe asterisk (*) matches any set of zero or more characters up to the end of a word. For example  net*matches network, networks, NETCFG, and NetWare.An asterisk preceded by a space can also be used to represent an entire word in a phrase, so that   disk *matches disk drive, disk partition, and any other two-word phrase beginning with disk.An asterisk at the end of words matches plurals and variant forms. For example, to find all references to printing, use  print*to find print, printing, prints, printed, and printer.Using Keyword Searchesidxid="w8188"book="_idx" docset="nw312" tidref="i4734"Use the keywords after, before, of, near, within, word, and words to perform proximity searches. For example, when you use the search phrase  print queue within 10 words before print server,any occurrences of the phrase print queue that are within the 10 words preceding the phrase print server are found. If you need to explicitly search for a phrase containing one of the above keywords, enclose the keyword or the phrase containing the keyword in quotation marks. For example, the word after is a keyword, so to search for the phrase after installing the server, you must use   "after installing the server"or  "after" installing the serverThis ensures a simple search for the phrase after installing the server rather than a keyword search for something that occurs after the phrase installing the server.Using Boolean Searchesidxid="w8189"book="_idx" docset="nw312" tidref="i724"idxid="w8190"book="_idx" docset="nw312" tidref="i4734"Use the keywords and, or, and not to perform Boolean searches. For example, when you use the search phrase  print queue or print serverany occurrences of either phrase are found. When you use the search phrase   print queue and print serveronly occurrences of both phrases together are found. When you use the search phrase   print queue not print serveronly occurrences of print queue not together with print server are found.Using the Stop Listidxid="w8191"book="_idx" docset="nw312" tidref="i4734"The viewer contains a list of common words (for example a, an, the, is, and for) called a "stop list"; these words are skipped during searches in order to speed up the search. If you enter one of these common words as part of your search phrase, it is replaced with a wildcard so that any word matches. For example, if you use the phrase   the printerthe phrase actually used is * printer. The phrases the printer, laser printer, my printer, and network printer all would be considered matches.ID="FM20137"Printingidxid="w8192"book="_idx" docset="nw312" tidref="i4676"idxid="w8193"book="_idx" docset="nw312" tidref="i5566"You can print a book or sections of a book to any printer or file specified by your Windows setup. ProcedureSelect "Print" from the "File" menu. The dialog box shown in the following figure appears.LBL="4-11"ID="FM81327"The ET Print dialog boxFILE="n312sa5k.pbm"Select the portion of the book to print. To print the entire book, select "Entire Book."To print specific sections of the book, select "Sections you select from outline below"; then click on the sections you want to print.Expand or collapse the outline as explained in IDREF="FM84935""Expanding/Collapsing the Outline" on page 466. Specify the format to use by pulling down the "Format" list and selecting a print style sheet from the list that appears. Choose "OK."The selected section(s) of the book are printed on the printer or to the file currently specified in your Windows environment. See your Windows documentation for more information. Configuring Novell ElectroTextidxid="w8194"book="_idx" docset="nw312" tidref="i4676"After Novell ElectroText is installed, you can do custom configurations to modify the way Novell ElectroText works and how the documentation looks on your workstation. The configuration information in the following sections is applicable only to Novell ElectroText running on Windows or OS/2 workstations. Starting Novell ElectroText from the Command Lineidxid="w8195"book="_idx" docset="nw312" tidref="i4676"You can start Novell ElectroText and open a specific book directly from the command line, or create a Windows program item to open a specific book. Do either of these to save time and steps getting to information you frequently use. As with other Windows applications, Novell ElectroText can be started directly from the command line. Enter the following command:  WIN path/ET.EXE <Enter>In addition, you can specify the bookshelf and book that automatically opens when Novell ElectroText starts. The command line syntax is as follows:  ET.EXE B;docset;booknameReplace docset with "nw312" or another docset (bookshelf) name, and bookname with the short name for a book (for example, "install" for NetWare 3.12 Installation and Upgrade). These values can be found in the NOVELL.ETL file. The bookshelf and book names can be entered on the command line along with the command to start Windows, or they can be added to the command line for a program item icon in Windows so that choosing the icon starts Novell ElectroText and opens a specific bookshelf or book. Creating Custom Libraries and Bookshelvesidxid="w8196"book="_idx" docset="nw312" tidref="i4676"Novell ElectroText documentation is arranged hierarchically in libraries and bookshelves. For example, the Novell library could contain one or more bookshelves; the default setup for this library contains the NetWare v3.12 bookshelf. Each bookshelf can contain one or more books; the default setup for the NetWare v3.12 bookshelf contains the books in the NetWare v3.12 manual set. idxid="w8197"book="_idx" docset="nw312" tidref="i4676"Three different configuration files (described in the following section) specify the organization and makeup of the Novell ElectroText library and the location of the library and book files. By editing these files, you can create your own custom libraries and bookshelves. ID="FM44754"Default Setup and Configuration FilesET.INIidxid="w8198"book="_idx" docset="nw312" tidref="i4676"idxid="w8199"book="_idx" docset="nw312" tidref="i1860"This file, which is copied to each user's local Windows directory when Novell ElectroText is installed (see "book="install" docset="nw312"Installing and Using Novell ElectroText" in Chapter 5 of Installationand Upgrade), specifies the location of files and sets up preferences. Because this file is specific to the workstation, changes made here affect only users using that workstation. The DOCSETS section of this file specifies the locations of the default bookshelves (docsets). For example, the location of the directories containing the books in the NetWare 3.12 bookshelf (the "nw312" docset) is specified. Note that this location depends on the value set for the NWLANGUAGE environment variable.   [DOCSETS]  nw312=c:/doc/$NWLANGUAGE/nw312  ethelp=c:/doc/$NWLANGUAGE/ethelpThe LIBRARIES section lists the location of the files in the libraries, the libraries that are available to the user, which one to open by default (OPEN=), and the definitions of the libraries. For example, LIB1 is opened by default and is defined as "novell."   [LIBRARIES]  ETLPATH=c:/doc/$NWLANGUAGE  OPEN=LIB1  LIB1=novell  LIB2=personalThe HELP section lists the book name and bookshelf name of the help books that will be opened when the user selects "Help" from the library, bookshelf, or book window.   [HELP]  LIBWIN=ethelp;hlp_libr  BOOKWIN=ethelp;hlp_bookOther sections of this file such as DYNATEXT and TABLES are not used for customizing libraries and bookshelves, and should not normally be modified.NOVELL.ETLidxid="w8200"book="_idx" docset="nw312" tidref="i4676"idxid="w8201"book="_idx" docset="nw312" tidref="i4746"This file, which is located in the \DOC\language directory, specifies the books that are included in the bookshelf (docset). For example, the name of the library defined here is "Novell Documentation," and it contains the docset "nw312." The docset "nw312" is defined as "NetWare v3.12 Manuals" and contains the aliases of the books in the bookshelf (See the next section for more information about aliases).   [LIBRARY]  TITLE="Novell Documentation"  SHELF1=nw312    [SHELF nw312]  TITLE="NetWare v3.12 Manuals"  BOOK1=nw312;btrieve  BOOK2=nw312;concepts  BOOK3=nw312;getstart  .  .BOOKLIST.TXTidxid="w8202"book="_idx" docset="nw312" tidref="i4676"idxid="w8203"book="_idx" docset="nw312" tidref="i722"This file, which is located in the \DOC\language\docset directory, specifies the aliases and titles of the books that are included in the docset. For example, the NOVELL.ETL file specifies that the book "getstart" is included in the "nw312" docset, and the BOOKLIST.TXT file specifies that the full name of "getstart" is "Getting Started with NetWare v3.12."   <book name="btrieve" alias="NetWare v3.12 Btrieve Installation and Operation">  <book name="concepts" alias="NetWare v3.12 Concepts">  <book name="getstart" alias="Getting Started with NetWare v3.12">  .  .  .This file is not used for the Windows or OS/2 versions of Novell ElectroText, but is required for compatibility with other platforms.TITLEidxid="w8204"book="_idx" docset="nw312" tidref="i4676"idxid="w8205"book="_idx" docset="nw312" tidref="i6797"Files by this name, one of which exists for each book and is located in each book's directory, contains the title of the book that appears on the book's icon in the bookshelf window and in the title bar of the book window.Modifying an Existing Bookshelfidxid="w8206"book="_idx" docset="nw312" tidref="i4718"You can modify an existing bookshelf by adding or deleting books from the bookshelf or bookshelves from the library. For example, to remove the book NetWare 3.12 Installation and Upgrade from the NetWare 3.12 bookshelf in the NetWare v3.12 bookshelf, delete the line   BOOK4=nw312;installfrom the NOVELL.ETL file and the line  <book name ="install" alias="NetWare v3.12 Installation and Upgrade">from the BOOKLIST.TXT file. The book's icon no longer appears on the bookshelf window. You can also remove a bookshelf from a library by deleting the "SHELFx=" line and its corresponding section from the NOVELL.ETL file. Creating a New Bookshelfidxid="w8207"book="_idx" docset="nw312" tidref="i4718"You can create a new bookshelf by adding a line defining the new bookshelf to the NOVELL.ETL file, and then adding books to the bookshelf from various docsets. For example, to create a bookshelf with your own selection of NetWare 3.12 manuals, add the line   SHELF2=mydocsto the NOVELL.ETL file. Then add a section defining the titles of the bookshelf and the books in the bookshelf:  [SHELF mydocs]  TITLE="My Set of Manuals"  BOOK1=nw312;ws_dos  BOOK2=nw312;conceptsThe docset name in the "BOOKn=" line remains "nw312" because that is the directory path location of the book files, as specified by the DOCSET section of the ET.INI file. Books from other docsets can be included in your custom bookshelf if they are present in your NetWare environment. For example, to add the Library Reference manual from the NetWare 3.12 NLM System Developer's kit to the bookshelf above, you would add the line  BOOK3=nw312nlm;librefThe physical location of each docset is specified in each workstation's ET.INI file.Creating a New Libraryidxid="w8208"book="_idx" docset="nw312" tidref="i4726"ProcedureCreate a new library by adding a line defining the new library to the ET.INI file. Create a new .ETL file that lists the books and the bookshelves in the library.Make sure to use the same format as the existing NOVELL.ETL file; you may want to save the file under a new name before you edit it.Add the name of the .ETL file to a "LIBx=" line in the [LIBRARIES] section of the ET.INI file.Troubleshootingidxid="w8209"book="_idx" docset="nw312" tidref="i6910"idxid="w8210"book="_idx" docset="nw312" tidref="i4676"Your workstation setup can affect proper Novell ElectroText operation. The following are some of the most likely things to cause problems and what you should do about them.LBL="4-4" INLINE="F"Troubleshooting ETWIDTH="144"SymptomWIDTH="144"Explanation/SolutionWIDTH="144"The message "error: can't read  authorization file" appears when  you start .WIDTH="144"The drive letters and/or directory  paths you set in the ET.INI file are  not valid. Edit the file to correct  the problem. See "book="install" docset="nw312"Installing and  Using Novell ElectroText" in  Chapter 5 of Installation and  Upgrade. beeps and  locks up as you are scrolling  through a table.A table cell is too large to fit on  your screen. Enlarge the viewing  window or hide the outline (select  "Text Only" from the "View"  menu) to increase the space  available to display the table. cannot find a  file.You do not have enough  environment space allocated for  files that  needs  to use. Make sure that the "files="  and "buffers=" variables are both  set to at least 20 in your  workstations CONFIG.SYS file.locks up.Your NetWare server is down or  your workstation is out of  memory. Bring the server back up  or add memory to your  workstation.LBL="A"ID="FM56327"Custom LAN Driver Statistics Shown in MONITORidxid="w8211"book="_idx" docset="nw312" tidref="i1292"MONITOR idxid="w8212"book="_idx" docset="nw312" tidref="i3085"enables you to idxid="w8213"book="_idx" docset="nw312" tidref="i6525"monitor your network activity, even down to counters that are set every time something occurs.You can use the LAN driver statistics to monitor network traffic, hardware conditions, and errors. Use SET (explained on page IDREF="FM73882"258) to reconfigure the file server to handle network traffic more efficiently.Generic LAN driver statistics are discussed in MONITOR on page IDREF="FM91936"176. As you view the statistics on the LAN driver information screen, use the arrow keys, <PgUp>, <PgDn>, <Ctrl><PgUp>, or <Ctrl><PgDn> to view all available information. Custom LAN driver statistics are discussed on the following pages.WIDTH="264"LAN driverWIDTH="48"PageWIDTH="264"3C503WIDTH="48"IDREF="FM45852"4943C505IDREF="FM53492"4963C523IDREF="FM65477"498NE2IDREF="FM94063"501NE2-32IDREF="FM66620"507NE1000IDREF="FM81032"504NE2000IDREF="FM66620"507NE3200IDREF="FM21912"510PCN2IDREF="FM91469"511TOKENIDREF="FM80981"513TRXNETIDREF="FM27867"516ID="FM45852"3C503 idxid="w8214"book="_idx" docset="nw312" tidref="i55"Custom Statistics3C503ResetCountIncrements when a Hard Transmit Error, Bad Network Error, or a Hardware Receive Mismatch occurs and the network board is reset to a known state.CarrierSenseLostCountIncrements when the transmitter on the card loses the carrier (indicating the cable connection is lost).ID="FM87194"EnqueuedSendsCountIncrements when the driver is unable to transmit a packet and must put the packet in a queue until the transmitter is available. Use this counter to track congestion on the network board.ExcessCollisionsCountIncrements when packets collide on a network board or in the cabling. Since Ethernet does a random "back off," packets should not collide the second time they are sent. However, two network boards could have node addresses that are too close, or the traffic on the network may be too heavy for Ethernet to handle. Solve the problem by installing a new network board or by splitting the network.GotNothingCountIncrements when the file server receives an interrupt from a network board that is not transmitting or receiving anything. This is not serious.ReceiveFIFOOverrunErrorCountIncrements when an incoming packet causes an overflow because FIFO (first-in, first-out memory) was not serviced.ReceiverMissedPacketCountIncrements when a packet goes to a network board that cannot accept the packet because its receive buffers are full.RxPagingErrorCountIncrements when errors occur because internal buffers on the card are corrupted.TotalCollisionsCountIncrements with each collision. A rapidly growing number in this count does not mean something is wrong, but rather that there is heavy traffic on the network.TransmitTimeoutCountIncrements when a network board interrupts the file server with the message that the "send bit" is lost. This is a hardware problem caused by faulty cabling, a bad network board, or a missing terminator.UnderrunErrorCountIncrements when the RAM buffer on the network board is full; the board cannot accept any more packets until the RAM buffer is cleared.UnsupportedFramePacketCountIncrements when the driver receives a packet with a frame type that the driver does not support or has not been registered for.UnsupportedMulticastCountIncrements for each multicast packet received by the card that is not registered with the driver.ID="FM53492"3C505 idxid="w8215"book="_idx" docset="nw312" tidref="i58"Custom Statistics# of Ethernet 802.2 Packets ReceivedIncrements when the driver successfully receives a packet with an Ethernet_802.2 frame type.# of Ethernet 802.3 Packets ReceivedIncrements when the driver successfully receives a packet with an Ethernet_802.3 frame type.# of Ethernet_II Packets ReceivedIncrements when the driver successfully receives a packet with an Ethernet_II frame type.# of Ethernet_SNAP Packets ReceivedIncrements when the driver successfully receives a packet with an Ethernet_SNAP frame type.# of Unsupported Frame From Packets ReceivedIncrements when the driver receives a packet with a frame type that the driver does not support.GetNICCommandTimeOutIncrements during initialization when the network board sends the driver a timeout.NICCmdLengthMismatchIncrements during initialization when the network board sends the driver commands of unexpected different lengths.NICCmdRequestDMSIsActiveIncrements when the driver receives a command from the network board in the interrupt routine, but the DMA is active.NICCmdRequestInvalidIncrements when the driver receives unexpected commands from the network board.NICCommandTooBigIncrements during initialization when the network board sends the driver a command that is too big.NICCommandTooLargeIncrements during initialization when the network board sends the driver an excessive number of commands.NICCommandTooSmallIncrements during initialization when the network board sends the driver a command that is too small.NotDoingDMACountIncrements when DMA is inactive and the driver receives a request to service DMA in the interrupt routine.ResetNICCountIncrements when an error occurs and the network board is reset to a known state.ID="FM65477"3C523 idxid="w8216"book="_idx" docset="nw312" tidref="i61"Custom StatisticsEnqueuedSendsCountIncrements when the driver is unable to transmit a packet and must put the packet in a queue until the transmitter is available. Use this counter to track congestion on the network board.RBD_act_cnt Not SetIncrements when the received packet's size is not set in the receive buffer descriptor (RBD).Recv Buffer Two Bytes OffIncrements when the received packet is moved two bytes to the right in the receive buffer. Sometimes this counter increments when a packet is trashed because of packet size or frame type.Reset82586Increments when an error occurs and the network board is reset to a known state.RxDMAOverrunIncrements when DMA overruns while receiving a packet.RxFailedTestsSoItWasTrashedIncrements when a received packet is trashed because it failed one or more of the reception tests.RxMediaMismatchIs not used.RxPacketsMisalignedAndCRCErrorIncrements when a packet with a CRC error and a misaligned error is received.RxPacketsWithCRCErrorIncrements when a packet with a CRC error is received.RxTrashedNoNICRxBuffersIncrements when a packet is trashed because no receive buffers are available for the packet. Use SET to increase the number of packet receive buffers.TxCollisionsIncrements when packets collide on the network. You may need to install another network board or split the network to reduce traffic.TxDeferIncrements when a transmission is deferred.TxDMAUnderrunIncrements when DMA is underrun during a transmission.TxLostClearToSendIncrements when a transmission fails because the clear to send signal was lost during the transmission of the packet. This usually indicates a hardware problem with faulty cabling, a bad network board, or a missing terminator.TxNoCarrierSenseIncrements when a transmission fails because the carrier sense was lost during the transmission of the packet.TxQueuedNoTBIncrements when no transmit buffers are available and a packet has to be put in a queue. Use this counter to monitor network traffic.TxTrashedMaxRetriesReachedIncrements when a packet is trashed because the file server could not transmit the packet in the preset number of times.TxTrashedNoCommandBlocksIncrements when a packet is trashed because no command blocks are available to use for transmission. Use SET to increase the number of packet receive buffers.TxTrashedTooManyCollisionsIncrements when a packet is trashed because of packet collisions. You may need to reduce traffic by adding another network board or by splitting the network.UnsupportedFramePacketCountIncrements when the driver receives a packet with a frame type that the driver does not support or has not been registered for.ID="FM94063"NE2 idxid="w8217"book="_idx" docset="nw312" tidref="i4077"Custom StatisticsID="FM28079"BackToBackSendsIncrements each time the driver can buffer a send packet onto the network board while the board is sending a previous buffer. Use this counter to track congestion on the network board.CarrierSenseLostCountIncrements when the transmitter on the card loses the carrier (indicating that the cable connection is lost).ExcessCollisionsIncrements once each time packets have collided sixteen times. Since Ethernet does a random "back off," packets should not collide the second time they are sent. However, two network boards could have node addresses that are too close and thus be "In Sync," or you may have a hardware problem. Solve the problem by installing a network board with a different node address or by finding and fixing the hardware problem (faulty board, missing terminator, faulty cable).OverflowReSendsIncrements when a transmission fails because of an overflow. The driver sends the packet again. If you receive too many of these, you may want to reconfigure your network to reduce traffic.OverrunIncrements when the RAM buffer on the network board is full and cannot accept any more packets. Packets will be accepted when the RAM buffer is cleared.PagingErrorIncrements when the operating system detects a pointer error on the network board's RAM. The system reinitializes the pointers on the network board and discards any packets in the RAM buffer. Paging errors can occur during normal operation.PageZeroErrorsIncrements when the operating system detects that a pointer has a value of zero. The system reinitializes the pointers on the network board. Page zero errors can occur during normal operation.ReceiveErrorIncrements when the network board gets an error receiving a packet. Receive errors can occur during normal operation.RxMulticastPacketIncrements every time the file server receives a multicast packet. (Ethernet can designate multiple recipients for one packet of information.)RxPagingErrorCountIncrements when errors occur because internal buffers on the card are corrupted.TotalCollisionsCountIncrements with each collision. A rapidly growing number in this count does not mean something is wrong, but rather that there is heavy traffic on the network.TransmitFailedIncrements when the driver is unable to transmit a packet a preset number of times.TransmitTimeoutCountIncrements when a network board interrupts the file server with the message that the "send bit" is lost. This is a hardware problem caused by faulty cabling, a bad network board, or a missing terminator.UnderrunErrorCountIncrements when an incoming packet causes an overflow because FIFO (first-in, first-out memory) was not serviced.UnsupportedMulticastCountIncrements for each multicast packet received by the card that is not registered with the driver.ID="FM81032"NE1000 idxid="w8218"book="_idx" docset="nw312" tidref="i4074"Custom StatisticsCarrierSenseLostCountIncrements when the transmitter on the card loses the carrier (indicating that the cable connection is lost).EnqueuedSendsCountIncrements when the driver is unable to transmit a packet and must put the packet in a queue until the transmitter is available. Use this counter to track congestion on the network board.ExcessCollisionsCountIncrements when packets collide on a network board or in the cabling. Since Ethernet does a random "back off," packets should not collide the second time they are sent. However, two network boards could have node addresses that are too close, or the traffic on the network may be too heavy for Ethernet to handle. Solve the problem by installing a new network board or by splitting the network.GotNothingCountIncrements when the file server receives an interrupt from a network board that is not transmitting or receiving anything. This is not serious.In32BitModeCountIncrements if a network board is ever found in 32-bit mode. (Currently, workstations run in 8-bit mode.) Occasionally, older NE1000 boards have bad chips that make the boards go into 32-bit mode. If you ever see this counter incremented, you probably have one of those older boards on the network.NE1000ResetCountIncrements when a Hard Transmit Error, Bad Network Error, or Hardware Receive Mismatch occurs and the network board is reset to a known state.ReceiveFIFOOverrunErrorCountIncrements when an incoming packet causes an overflow because FIFO (first-in, first-out memory) was not serviced.ReceiverMissedPacketCountIncrements when a packet is sent to a network board that cannot accept the packet because all its receive buffers are full.RxPagingErrorCountIncrements when errors occur because internal buffers on the card are corrupted.TotalCollisionsCountIncrements with each collision. A rapidly growing number in this count does not mean something is wrong, but rather that there is heavy traffic on the network.TransmitTimeoutCountIncrements when a network board interrupts the file server with the message that the "send bit" is lost. This is a hardware problem caused by faulty cabling, a bad network board, or a missing terminator.UnderrunErrorCountIncrements when the RAM buffer on the network board is full; the board cannot accept any more packets until the RAM buffer is cleared.UnsupportedFramePacketCountIncrements when the driver receives a packet with a frame type that the driver does not support or has not been registered for.UnsupportedMulticastCountIncrements for each multicast packet received by the card that is not registered with the driver.ID="FM66620"NE2-32 idxid="w8219"book="_idx" docset="nw312" tidref="i4080"and idxid="w8220"book="_idx" docset="nw312" tidref="i4083"NE2000 Custom StatisticsID="FM16864"BackToBackSendCountIncrements each time the driver can buffer a send packet onto the network board while the board is sending a previous buffer. Use this counter to track congestion on the network board. IDREF="FM87194"See also "EnqueuedSendsCount" on page 494.CarrierSenseLostCountIncrements when the transmitter on the card loses the carrier (indicating that the cable connection is lost).EnqueuedSendsCountIncrements when the driver is unable to transmit a packet and must put the packet in a queue until the transmitter is available. Use this counter to track congestion on the network board. IDREF="FM16864"See also "BackToBackSendCount" on page 507.ExcessCollisionsCountIncrements when packets collide on a network board or in the cabling. Since Ethernet does a random "back off," packets should not collide the second time they are sent. However, two network boards could have node addresses that are too close, or the traffic on the network may be too heavy for Ethernet to handle. Solve the problem by installing a new network board or by splitting the network.GotNothingCountIncrements when the file server receives an interrupt from a network board that is not transmitting or receiving anything. This is not serious.NE2000ResetCountIncrements when a HardTransmitError, BadNetworkError, or HardwareReceiveMismatch occurs and the network board is reset to a known state.ReceiveFIFOOverrunErrorCountIncrements when an incoming packet causes an overflow because FIFO (first-in, first-out memory) was not serviced.ReceiverMissedPacketCountIncrements when a network board cannot accept packets sent to it because all of its receive buffers are full.RxPagingErrorCountIncrements when errors occur because internal buffers on the card are corrupted.TotalCollisionsCountIncrements with each collision. A rapidly growing number in this count does not mean something is wrong, but rather that there is heavy traffic on the network.TransmitTimeoutCountIncrements when a network board interrupts the file server with the message that the "send bit" is lost. This is a hardware problem caused by faulty cabling, a bad network board, or a missing terminator.UnderrunErrorCountIncrements when the RAM buffer on the network board is full; the board cannot accept any more packets until the RAM buffer is cleared.UnsupportedFramePacketCountIncrements when the driver receives a packet with a frame type that the driver does not support or has not been registered for.UnsupportedMulticastCountIncrements for each multicast packet received by the card that is not registered with the driver.ID="FM21912"NE3200 idxid="w8221"book="_idx" docset="nw312" tidref="i4086"Custom StatisticsTransmit Retry FailureIncrements when the driver is unable to transmit a packet a preset number of times. This may indicate a hardware problem.No Nic Board Receive BuffersIncrements when the driver does not have enough packet receive buffers on the NE3200 board to hold all the packets it needs to service. If this counter increments, the NE3200 board has a hardware problem. Replace the board.Number Of Resets To NicIncrements when the software corrects itself for minor problems. Under normal conditions, more of these errors should occur during idle time than when the driver is busy. For this counter to warn you of potential hardware problems, you must receive thousands of these errors when the network is busy.ID="FM91469"PCN2 idxid="w8222"book="_idx" docset="nw312" tidref="i5041"Custom Statistics802.2PacketsReceivedIncrements for each PCN_802.2 packet received.BadTransmitCompleteInterruptCountIncrements for each complete transmission with no transmit active.CurrentEnqueuedCountIncrements as the current number of packets waiting in the queue increases (until the transmitter is available).EnqueuedSendsCountIncrements when the driver is unable to transmit a packet and must put the packet in a queue until the transmitter is available. Use this counter to track congestion on the network board.GotNothingCountIncrements when the driver receives an interrupt from the card indicating that it has completed a receive but there is no data in the card's receive buffer. This is not serious.HotCarrierInterruptCountIncrements when the board detects a carrier longer than expected without a transmit. This generally indicates that some board on the network has failed or is starting to go bad.No82588InterruptCountIncrements each time it receives an interrupt from the card but not the 82588 chip. This should never happen.PCN2ResetCountIncrements when an error occurs and the driver resets the board to a known state.ReceivedShortPacketCountIncrements when a packet of less then 17 bytes is received.ReceiveUnderrunErrorCountIncrements when the driver finds less data in the card's buffer than the card said was there.SNAPPacketsReceivedCountIncrements when the driver successfully receives a packet with an Ethernet_SNAP frame type.TotalTransmitErrorCountIncrements each time the file server is unable to transmit a packet, even if it eventually succeeds.UnsupportedFramePacketCountIncrements for each unregistered frame received.WeirdInterruptCountIncrements when the file server has received an interrupt from the card, but the card claims not to have sent one. This should never happen.ID="FM80981"TOKEN idxid="w8223"book="_idx" docset="nw312" tidref="i6807"Custom StatisticsMuch of this information for idxid="w8224"book="_idx" docset="nw312" tidref="i6821"Token-Ring custom statistics is condensed from the IBM Token-Ring Network Architecture Reference produced by IBM.Abort DelimitersIncrements when a ring station transmits an abort delimiter. An abort delimiter is transmitted when a ring station receives a frame in which the token bit of the access control field is set to show "Token" and not "Frame." A ring station can also transmit an abort delimiter if an internal hardware error has occurred.A/C ErrorsIncrements when a ring station receives a "Standby Monitor Present" MAC frame with the A/C bits in the Frame Status field equal to zero without first receiving an "Active Monitor Present" MAC frame.Bad Correlator CountIncrements when a network board responds with a request for data from the file server that the file server does not have. The ECB or some other code may be corrupted. Eventually, this type of error will down the server. If this counter is non-zero, you should try to find the software that is corrupting the data.Burst ErrorsIncrements when a ring station detects the absence of "five half-bit times" (a burst-five error). Other stations will detect a burst-four error followed by idles.Frame Copied ErrorsIncrements when a ring station receives or repeats a frame that appears to have a duplicate address.Frequency ErrorsIncrements when a ring station detects a frequency error.Internal ErrorsIncrements as a ring station has recoverable internal errors, which means a ring station is probably marginal.Last Ring StatusChanges each time the ring status changes. Status codes, their function, and meaning are listed on the next page. If you receive errors not listed in the chart, see the IBM Token-Ring Network Architecture Reference produced by IBM.Line ErrorsIncrements when a frame or token is repeated by the ring station. A frame is repeated when a "Frame Check Sequence" error occurs or a code violation exists between the starting and ending delimiters of the frame.Lost FramesInstances when a ring station transmits a frame that does not return to the station. The active monitor sends a new token.Receive Congestion ErrorsIncrements when a ring station recognizes a frame addressed to it but has no buffer space available for the frame.Token ErrorIncrements when an active monitor cannot send a token. Circulating priority tokens, circulating frames, or lost tokens can prevent tokens from being transmitted.Unknown ARB RequestCounts bad ARBs (Adapter Request Blocks). Normally the network board (adapter) uses one of four known commands to communicate with the driver. If a network board sends a command that is not one of the four, the driver does not recognize the request. This is not a catastrophic error. Sometimes old adapters send bad ARB requests because of software problems resident on the board. NetWare responds to the network board so that the board will not hang.LBL="A-1" INLINE="F"Unknown ARB Request codesWIDTH="36"CodeWIDTH="72"FunctionWIDTH="180"MeaningWIDTH="36"8000WIDTH="72"Signal lossWIDTH="180"No received signal detected.4000Hard errorBeacon frames were transmitted or  received.2000Soft errorThe adapter has transmitted a soft error  report MAC frame.1000Transmit  beaconThe adapter transmitted beacon frames.0800Lobe wire faultAn open or short circuit was detected in  the lobe data path. (The adapter will be  closed.)0400Auto-removal  error1An adapter hardware error occurred  following the beacon auto-removal  process.0200Reserved0100Remove  receivedA remove MAC frame was received. The  adapter is closed.0080Counter  overflowOne of the adapter error log counters has  been incremented from 254 to 255.  (Issue the DIR.READ.LOG command.)0040Single stationThe adapter has opened and is the only  station on the ring. (The bit will be reset  when another station is detected.)0020Ring recoveryThe adapter is transmitting or receiving  Monitor Contention MAC frames. This bit  will be reset upon receipt of a Ring Purge  MAC frame.ID="FM27867"TRXNET idxid="w8225"book="_idx" docset="nw312" tidref="i7033"Custom StatisticsFatal RetransmissionsIncrements when the file server reaches the limit for retry transfers in sending a packet. You can increase the number of retry transfers with a driver parameter IDREF="FM79039"(see "LOAD LAN driver" on page 122). Retries, however, slow down the system.First Halves CancelledIncrements when the TRXNET driver splits a data buffer and starts sending the packets in the sequence, but only the first few packets of the sequence arrive because someone turned off the driver before all the packets could be sent.Number of Orphaned PacketsIncrements when the TRXNET driver breaks a data buffer (on a send) into a sequence of smaller packets and sends them out in order but a packet in the sequence is received before a preceding packet in the sequence; then all packets in the sequence are dropped and the "Number of Orphaned Packets" counter increments once for the sequence.Raw TransmissionsIncrements when the driver sends a packet without attaching a NetWare header and split flags.Sends CancelledIncrements when someone unloads the driver from the network while the driver is functioning. The send commands are waiting to be sent. Since there is no driver, the commands are eliminated and the counter is incremented.Sends Ignored - Driver Shut DownIncrements when a workstation sends a packet intended for a driver that has been unloaded.Spurious InterruptsIncrements when the TRXNET driver in the file server receives an interrupt in the middle of an interrupt service routine. The hardware interrupt should be turned off during an interrupt service routine to allow the interrupt service routine to complete its task. This counter increments, and the hardware is polled before the interrupt service routine exits.Timed Out Receive ECBsIncrements when all of the packets in a sequence do not arrive in a specified amount of time. The TRXNET driver split a data buffer and started sending packets, but only the first few packets of the sequence arrived on time. This should be a rare occurrence unless you have heavy network traffic on your cables.Timed Out SendsIncrements when the file server sends a packet to the network board, but the board does not respond during a preset amount of time. (The board should acknowledge each packet it receives.) This is not a serious problem.LBL="B"ID="FM33775"Tracked Resources Displayed in MONITORidxid="w8226"book="_idx" docset="nw312" tidref="i6857"NetWare v3.12 tracks many operating resources. It does this tracking so that when you unload an NLM, the resources return to the operating system and become available for other NLMs.An NLM, as you load it, requests idxid="w8227"book="_idx" docset="nw312" tidref="i5908"resource tags. The operating system assigns each resource tag a resource tag name, and then grants resources to each resource tag.For example, when you load idxid="w8228"book="_idx" docset="nw312" tidref="i3949"MONITOR it requests an "Alloc Memory" resource tag. The operating system grants MONITOR the resource tag and allocates some "Alloc Short Term Memory" to the resource tag.The operating system also uses resource tags to track its own use of memory. It uses "Alloc Short Term Memory" for a number of functions, and gives each function its own tag. For example, the operating system uses the following resource tags for the "Alloc Short Term Memory" resource:Broadcast SystemConnection User InformationDisk Management SystemEvent NotificationFile LocksLoadable modules can also add resources to be tracked. For example, idxid="w8229"book="_idx" docset="nw312" tidref="i4634"NMAGENT adds the following resources:Network Management FiltersNetwork Management ManagersNetwork Management ObjectsThis appendix defines all resources tracked by the operating system and those tracked resources added by the NMAGENT module. See the documentation for third-party NLMs for any tracked resources they add.You can view the tracked resources two different ways from MONITOR's "Available Options" menu. You can view them from the "System Module Information" option or from the "Resource Utilization" option."System Module Information" shows you which types of resources a particular module uses."Resource Utilization" shows you which module uses how much of a particular resource.Improperly implemented NLMs can cause file server resources (memory, service processes, and buffers) to reach their limits quickly. For example, if nothing new has been added to the system, permanent memory should not grow at a rate of 2 MB a day. Use the statistical information gathered from tracked resources to identify loadable modules that use more resources than they need.The function of each resource is described in the following sections.AES Process Call-BacksAES stands for asynchronous event service. This resource allows an NLM to schedule a future event. For example, when the power fails, UPS schedules a delayed down command for the file server. The command then executes a specified number of minutes before the battery's power is depleted.Alloc Short Term Memory (Bytes)NetWare v3.1x has five memory pools. It uses Alloc Memory for short-term memory requests. Loadable modules with pop-up windows use Alloc Memory to store previous menu information on the screen. When the user escapes back to the previous menu, the memory returns immediately to the operating system. The "Server Memory Statistics" window ("Alloc Memory Pool" option) displays the total amount of memory used for this resource.C Library BSD SocketsTracks the number of Berkeley UNIX sockets.Cache Movable Memory (Bytes)NetWare v3.1x has five memory pools. It uses the Cache Movable Memory pool for system tables such as directory tables and FATs that grow dynamically. Name space modules also use this resource. The "Server Memory Statistics" window ("Cache Movable Memory") displays the total amount of memory used by this resource.Cache Non-Movable Memory (Bytes)NetWare has five memory pools. It uses the Cache Non-Movable Memory pool to load modules into memory and to allocate large memory buffers. The "Server Memory Statistics" window ("Cache Non-Movable Memory") shows the total amount of memory used by this resource.Console Command HandlersNetWare uses this resource to track console command resources. Loadable modules can add console commands to the operating system as you load them. For example, UPS adds two console commands (UPS STATUS and UPS TIME) when you load it.Disk Adapter LocksTracks loadable modules that need to know about disk adapters, controllers, or host bus adapters.Disk Drive LocksTracks loadable modules that need to know about the hard disks that you have added to the operating system. It then informs these modules when you remove the hard disk.Disk File System Partition LocksTracks loadable modules that register a need to access information about logical partitions. For example, INSTALL uses this resource when it mirrors two drives.Disk Raw Partition LocksTracks access to disk partitions. For example, INSTALL uses this resource when it installs Hot Fix on a partition.Event Notification Call-BacksAllows modules to detect when system events occur. For example, MONITOR uses it to detect when you mount or dismount a volume.Hardware Interrupt HandlersTracks which loadable modules and hardware use which interrupts. LAN drivers and disk drivers that require the interrupts also use this resource.Interrupt Time Call-BacksTracks NLMs that have processes which occur at regularly timed intervals. For example, MONITOR uses this resource to update the statistics in its windows every second.IPX SocketsTracks NLMs that establish a socket connection between two devices. A different socket handles each type of communication. For example, the operating system uses one socket for workstation communication. The RSPX module establishes another socket for RCONSOLE communication.LSL AES Event Call-Backs(AES stands for asynchronous event service.) Allows LAN drivers to schedule a future event.LSL Default Protocol StacksTracks protocol NLMs that register to receive all packets that no other protocol claims. By default, the operating system discards any unclaimed packets. However, when a protocol NLM registers, the default is overridden.LSL Packet Receive BuffersTracks which LAN driver is using a particular packet receive buffer so that the buffers can be freed when the LAN driver is unloaded.LSL Pre-Scan Protocol StacksTracks protocol NLMs that register to pre-scan all incoming packets to see if the packets belong to them. Each board can have only one pre-scan protocol.LSL Protocol StacksTracks NLMs that register as protocol stacks. The operating system registers the IPX protocol stack automatically.NCP ExtensionsTracks loadable modules that define their own NCPs (NetWare Core Protocols).Network Management ManagersTracks the number of network management managers the NMAGENT loadable module has allocated.Network Management ObjectsTracks the number of network management objects the NMAGENT loadable module has allocated.Network Management TriggersTracks the number of network management triggers the NMAGENT loadable module has allocated.Permanent Memory (Bytes)NetWare has five memory pools. The Permanent Memory pool is used as a source of memory for the Semi-Permanent Memory pool and Alloc Short Term Memory pool. The Permanent Memory pool is used by the operating system for permanent tables. Loadable modules cannot use this memory.Poll Procedure Call-BacksTracks loadable modules that have processes executing at defined intervals.ProcessesTracks loadable modules that start processes. The resource makes sure that the process is deleted when the module is unloaded.Processor Exception HandlersTracks exceptions to the rules that hardware detects. For example, if the CPU determines that an NLM is trying to divide by zero, the operating system notifies the NLM that it has broken the rules. The NLM then sends a message to the console or workstation. (These messages are documented by the NLM's vender.)Registered Disk AdaptersTracks the configuration options of disk drivers (interrupts, DMA, memory addresses, I/O ports, and slots).Registered Hardware OptionsTracks LAN drivers that request interrupts, DMA, memory addresses, I/O port addresses, and slots.Registered MLID BoardsTracks the number of LAN drivers that have been loaded and ensures that a LAN driver's resources are returned to the operating system when the driver is unloaded.Remote Server Sessions (Instances)Tracks the number of remote servers that have at least one remote connection.Screen Input Call-BacksTracks NLMs that use an alternate method for key input from a console screen. TRACK ON uses this resource.ScreensTracks how many screens an NLM has created or opened on the file server console. Most NLMs with menus (such as MONITOR) will activate a screen. NLMs without menus (such as LAN drivers and disk drivers) do not activate any screens.SemaphoresTracks NLMs that use semaphores. Semaphores control multiple access to a resource that can be used by only one user at a time.Semi-Permanent Memory (Bytes)NetWare v3.1x has five memory pools. Semi-Permanent Memory is used for small amounts of memory that a loadable module expects to use for a long time. LAN drivers and disk drivers use this type of memory.Service Advertising (Instances)Tracks the number of times an NLM advertises itself over the network. Normally this is 1 or 0.Service Connection Task NumbersTracks the task numbers that are assigned to an NLM for use on a connection. (An NLM can log in and use a connection slot.)Service ConnectionsTracks the file server to workstation connections. This resource tracks all attached and logged-in users.Setable ParametersTracks NLMs that add parameters to the SET command. It ensures that, when the NLM is unloaded, the SET parameters are also unloaded.STREAMS: Active Stream HandlesTracks the number of communication streams that are currently in use.Tracked Resource TypesTracks NLMs that add tracked resources to the operating system. The resource ensures that, when the NLM is unloaded, the resource types are also unloaded. For example, the operating system tracks NMAGENT with this resource. When NMAGENT is unloaded, NMAGENT's three tracked resources ("Network Management Filters," "Network Management Managers," and "Network Management Objects") are also unloaded.