#EDIR DATA#
NetWare Workstation Basics and InstallationDisclaimerNovell®, 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.LBL="0"How to Use This ManualThis manual refers to manuals in both the NetWare v4. 0 and NetWare v3.12 manual sets. If you choose a cross referene to a set that is not installed, a message similar to the following will appear:"Hypertext Link failed - Could not find destination"or "Your ET.INI file does not set NW40 in the section [DOCSETS]."If one of the above meassages appear, this only means that the manual set is not installed. If you need access to the set, check the ET installation or obtain a copy of the set and install it.Workstation Basics and Installation covers concepts and procedures for installing and using NetWare® workstation software on NetWare v2.x, v3.x, and v4.0 networks. References are made to each version of NetWare. Ignore any references which do not pertain to the version of NetWare you are connecting to.You should read this manual before using the other workstation manuals:book="ws_dos" docset="nw40"Workstation for DOS and Windowsbook="ws_os2" docset="nw40"Workstation for OS/2®Use Workstation for DOS and Windows and Workstation for OS/2 for information on managing your workstation and advanced workstation setup.Use Figure 0-1 to determine which chapters you should read to install and use network workstations.LBL="1"ID="FM38165"Flowchart - Workstation Basics and InstallationFILE="c312b39a.pbm"Installation and Setup ChecklistTo set up your NetWare workstation, use the chapters in the following checklist in the order shown. Use Chapter, 1 "Understanding Networking Basics," to learn more about basic networks and connections. There is a brief discussion about network resources, users, security and the file system. You also introduced to NetWare Directory Services(tm) and the network file system in NetWare v4.0. Use Chapter 2, "Preparing to Install Workstation Software," to help prepare your workstation hardware, determine your network board settings, and prepare your workstation software for workstation installation. It also guides you through steps on how to get and configure your NetWare workstation software for installation.Use Chapter 3, "Installing a NetWare Workstation," to guide you through the steps for installing DOS, Windows and OS/2 workstations. There is a brief description of the NetWare DOS Requester(tm) (new to DOS and Windows workstations). There is also information about what happens during installation.Use Chapter 4, "Setting Up Workstations to Log in to the Network," to guide you through basic steps for modifying your NET.CFG file to simplify login to a NetWare Directory Services network.Use Chapter 5, "Workstation Login," for procedures on how to log in to the network from DOS, Windows, and OS/2. The section on OS/2 explains how to log in for VDM, VM BOOT, and the OS/2 Desktop.Use Chapter 6, "Using NetWare Tools," for an overview of how to access and use the features included in the NetWare Tools for your workstation. There are NetWare Tools for DOS, Windows, and OS/2.Use Chapter 7, "Setting Up Workstation Printing," to set up printing for your workstation. This chapter covers initial setup for printing in DOS, Windows, and OS/2 workstations.Appendix A and Appendix B explain briefly the WSUPGRD and WSUPDATE utilities. You will find WSUPGRD useful for multiple installations. WSUPDATE is useful for new revisions and re-installations.LBL="1"ID="FM13821"Understanding Networking BasicsOverviewThis chapter provides a basic overview of the concepts for adding a workstation to your network and for using that workstation. WIDTH="264"TopicWIDTH="48"PageWIDTH="264"IDREF="FM99348""Understanding Basic Networks"WIDTH="48"IDREF="FM99348"2IDREF="FM94455""Understanding Network Connections"IDREF="FM94455"3IDREF="FM39204""Understanding Network Resources"IDREF="FM39204"4IDREF="FM24874""Understanding the Structure of the File System"IDREF="FM24874"7IDREF="FM27356""Understanding Network Users"IDREF="FM27356"10IDREF="FM45493""Understanding Login"IDREF="FM45493"11IDREF="FM68483""Understanding Network Security"IDREF="FM68483"13IDREF="FM99067""Understanding Network Printing"IDREF="FM99067"16IntroductionIn order to take advantage of your NetWare workstation, you need to understand how your workstation relates to the NetWare operating system it is connecting to and to review basic networking concepts.Users connecting to NetWare v2.x and v3.x need to understand how their workstations relate to NetWare bindery server networks.Users connecting to NetWare v4.0 will need to understand NetWare Directory Services (NDS(tm)) and how it affects their environment. ID="FM99348"Understanding Basic NetworksA network links two or more computers together to share resources and peripherals (such as disk drives, printers, and data). There are two categories of networks: peer-to-peer and client-server.Peer-to-Peer NetworksThe simplest idxid="w6696"book="_idx" docset="nw312" tidref="i5062"peer-to-peer network has two personal computers connected together, each able to use the resources of the other. All machines on a peer-to-peer network are (or can be) equal. No one machine is designated as the main computer or central point of control. Client-Server NetworksThe idxid="w6697"book="_idx" docset="nw312" tidref="i994"client-server network has at least one personal computer configured as a server. As shown in IDREF="FM31837"Figure 1-1, the server is a machine running the network operating system. The server controls communication and shared network resources. The client machines are the individual user workstations connected to the network.LBL="1-1"ID="FM31837"A simple client-server networkFILE="c312b20a.pbm"Understanding ID="FM94455"Network ConnectionsYou must make two types of connections to use shared network resources:A physical connection, and A logical connectionidxid="w6698"book="_idx" docset="nw312" tidref="i5082"Physical ConnectionIn order for resources and information to be shared on a network, servers, workstations, and other network devices must be physically connected. Each device on the network must have a network board. A cable attached to the network board provides the communication pathway, as shown in IDREF="FM40142"Figure 1-2. LBL="1-2"ID="FM40142"Network board and cablingFILE="c312b21a.pbm"The physical connection determines the kind of cable used, the way the cable is configured (called the idxid="w6699"book="_idx" docset="nw312" tidref="i6852"topology of the network), and the way information is transmitted over the cable (called the idxid="w6700"book="_idx" docset="nw312" tidref="i5630"protocol).idxid="w6701"book="_idx" docset="nw312" tidref="i3418"Logical ConnectionAfter the physical connection to the network is made, you must make a logical connection to access the network services.To make the logical connection on a NetWare network, you must prove that you are an authorized user. This is done when you log in to the network and provide the NetWare operating system your user identification and a valid password. By logging in to a network or attaching to a server you make a logical connection.ID="FM39204"Understanding Network ResourcesAfter connecting to a NetWare network, you have access to physical and logical resources across the network. A definition for each resource is maintained in a database used by the NetWare operating system. An example of this is a print queue or group name. How you interact with the resource database depends greatly on which version of the NetWare operating system you are running.ID="FM64958"Understanding the Resources for NetWare v2.x and v3.xNetWare v2.x and v3.x uses a flat-database structure called a bindery for managing network resource definitions. A definition for each network resource is maintained in the bindery. For example, a definition exists for your user information, such as your username and password. A bindery exists for each server in the network and is independent of resource definitions created on other servers.The bindery structure for each server is flat with a single location for accessing and managing network resources. Therefore, when you use network resources in a multiple server network, you must be aware of their physical and logical locations in order to use them. ID="FM18317"Understanding the Resources for NetWare v4.0NetWare v4.0 uses a global-database structure called NetWare Directory Services for managing network resource definitions. idxid="w6702"book="_idx" docset="nw312" tidref="i4240"NetWare Directory Services (NDS) treats all network resources as objects in a distributed database known as the idxid="w6703"book="_idx" docset="nw312" tidref="i4239"Directory database. This database organizes resources in a hierarchical tree structure, independent of their physical location.The Directory supports an entire network of servers. Instead of storing all information on each individual server as in NetWare v2.x and v3.x, information is distributed over a global database and can be accessed by all servers.Users can access any network service, such as file services or print services, without having to know the physical location of the server that provides the service.Components of a Directory TreeNetWare Directory Services operates in a logical organization called the idxid="w6704"book="_idx" docset="nw312" tidref="i1520"Directory tree. It is called a Directory tree because objects are stored in a hierarchical tree structure, starting with the root object and branching out.Three types of objects make up the Directory tree: the root object, container objects, and leaf objects.idxid="w6705"book="_idx" docset="nw312" tidref="i4793"Root objectThe root object is placed at the top of the Directory tree by the installation program.idxid="w6706"book="_idx" docset="nw312" tidref="i4793"Container objectsA branch of the Directory tree consists of a container object and all the objects it holds, which can include other container objects. idxid="w6707"book="_idx" docset="nw312" tidref="i4793"Leaf objectsLeaf objects are at the end of branches and do not contain any other objects. Volumes, Users, and NetWare Servers are some examples of leaf objects.IDREF="FM76561"Figure 1-3 shows how container objects and leaf objects make up the Directory tree.LBL="1-3"ID="FM76561"Example of a Directory treeFILE="c312b01a.pbm"To refer to where an object is in the idxid="w6708"book="_idx" docset="nw312" tidref="i1520"Directory tree, the term context is used. The position of the object within its container is its context. For example, in IDREF="FM76561"Figure 1-3, the context of User object Jody is Development.MedTech. To identify a particular object, you must know its context. To make it easy for users to locate the objects that they work with on a regular basis, you can set up configuration files to specify the context of each object. This gives the users a more manageable view of the tree; they do not have to know exactly where each object is located in the tree.ID="FM24874"Understanding the Structure of the File SystemThe bindery and NetWare Directory Services help you manage network resources such as NetWare servers and printers, but they do not provide control over the file system (volumes, directories, and files). Graphical and text utilities help you manage both network resources and the file system.The idxid="w6709"book="_idx" docset="nw312" tidref="i2286"file system structure is separate from the bindery or NetWare Directory Services structure. Physically, all network information is stored on hard disks that are controlled by a server. But logically, the file system is represented in NetWare v2.x and v3.x as a volume and NetWare v4.0 as a Volume object.Three types of structures make up the file system: volumes, directories, and files.ID="FM59473"Understanding the File Structure for NetWare v2.x and v3.xThe file structure in NetWare v2.x and v3.x begins with the file server. The physical hard disks in a file server are divided into volumes, much like a set of books. A volume may contain several physical hard disks, or a single hard disk can be divided into multiple volumes.A volume marks the base of each directory structure. It appears and acts like a DOS root directory or disk drive. Directories are stored at the volume level and subdirectory levels. Files are stored within directories and subdirectories in the same manner as DOS or OS/2 systems store files.IDREF="FM60415"Figure 1-4 shows how the file structure of NetWare v2.x and v3.x works.LBL="1-4"ID="FM60415"idxid="w6710"book="_idx" docset="nw312" tidref="i2286"File system structure and directory pathFILE="c312b02a.pbm"ID="FM68608"Understanding the File Structure for NetWare v4.0The file structure in NetWare v4.0 begins with the Volume object. A idxid="w6711"book="_idx" docset="nw312" tidref="i7412"Volume object is one type of leaf object. It refers to a physical volume where files are stored and allows NetWare Directory Services to locate files. The root directory of a physical volume is also represented as part of a Volume object. It is the highest level of the file system structure. The Volume object provides a link between NetWare Directory Services and each physical volume's file system.idxid="w6712"book="_idx" docset="nw312" tidref="i1474"Directories and files are not objects in the Directory tree. They are only a part of the file system. To access directories and files from the Directory tree, open a Volume object or set up Directory Map Objects.IDREF="FM60415"Figure 1-5 shows how these structures make up the file system.LBL="1-5"ID="FM60415"idxid="w6713"book="_idx" docset="nw312" tidref="i2286"File system structure and directory pathFILE="c312b02a.pbm"The position of a file within the file system is its idxid="w6714"book="_idx" docset="nw312" tidref="i1500"directory path.To identify a file, you must know the context of the Volume representing the physical volume that contains the file, and the directory path through the file system structure, including the name of the file. You can make it easy for users to find files by setting up Directory Map objects that point to a particular location in a volume's file system structure.Understanding ID="FM27356"Network UsersBefore anyone can have access to a NetWare network, they must be identified to the NetWare operating system as a idxid="w6715"book="_idx" docset="nw312" tidref="i4576"network user. NetWare v2.x and v3.x UsersNetWare v2.x and v3.x allow for four types of network users which have varying levels of responsibility on the network. The four types are:Regular network usersOperators (file server console operators, print queue operators, and print server operators)Managers (workgroup managers and user account managers)Network supervisors Regular network users are the people who work on the network. They can run applications and work with files according to the rights assigned to them.Operators are regular network users who have been assigned additional privileges. For example, a file server console operator is a network user who is given specific rights to use the FCONSOLE utility.Managers are users who have been given responsibility for creating or managing other users. Workgroup managers can create and manage users; user account managers can manage, but not create, users. Managers function as supervisors over a particular group, but they do not have supervisor equivalence. Network supervisors are responsible for the operation of the whole network. Network supervisors maintain the system, restructuring and updating it as needed. NetWare v4.0 UsersNetWare Directory Services identifies the same network users as NetWare v2.x and v3.x. In addition, NetWare v4.0 identifies a User object named ADMIN.Using ADMIN for NetWare Directory ServicesThe first time the network supervisor logs in, it is as User object ADMIN, which is created by default during NetWare v4.0 installation. (The termnetwork supervisor refers to the person responsible for setting up NetWare v4.0. A single network supervisor is not a requirement for NetWare v4.0.)When User ADMIN is created on the first NetWare v4.0 server that you install, it can manage all objects because it has the Supervisor right to every object. Initially, ADMIN can also manage all directories and files on every volume in the Directory tree.User ADMIN does not have any special significance like the user SUPERVISOR did in previous versions of NetWare. It is only the first User object created and, therefore, is granted rights to create and manage all objects.To use the network, every user must have a idxid="w6716"book="_idx" docset="nw312" tidref="i7147"User object in the Directory tree. The User object represents the individual and keeps track of the person's use of the network.ID="FM45493"Understanding idxid="w6717"book="_idx" docset="nw312" tidref="i3426"LoginBefore you can use any of the network services, you must attach to and log in to the network. Bindery users log in to or attach to individual servers, whereas idxid="w6718"book="_idx" docset="nw312" tidref="i4240"NetWare Directory Services users log in to the network. Therefore, bindery users need a password for each server they are logging in to. NetWare Directory Services users need only one password to gain access to all network resources that they have the right to use.Starting up and logging in from a workstation always consists of the same steps.Booting the workstation.This loads the workstation operating system and is done automatically when you turn on the power or "reboot" by pressing the <Ctrl><Alt><Del> keys at the same time.Loading the network software and drivers.Changing the default drive to a network drive.Logging in with a username and (usually) a password.NetWare prompts you for your username and password and completes the network connection. See IDREF="FM75071"Figure 1-6.The way users actually perform these steps depends on how the network supervisor has set up the network and the workstation. All four steps can be accomplished automatically so that the only thing users do is type their password. For more information, see IDREF="FM38025""Setting Up Workstations to Log In to the Network" on page IDREF="FM38025"57.LBL="1-6"ID="FM75071"idxid="w6719"book="_idx" docset="nw312" tidref="i3426"Logging in to the networkFILE="c312b23a.pbm"For example, users can log in to the network by typing  LOGIN ESAYERSor  LOGIN SERVERNAME/ESAYERSLOGIN is usually executed from the AUTOEXEC.BAT or another batch file. The command line syntax is the same for DOS and OS/2 but is different in NetWare versions v2.x and v3.x without Directory Services, than in NetWare v4.0. If you are using NetWare v3.x, see book="utilref" docset="nw312"Utilities Reference for a complete description of the utility. If you are using NetWare v4.0, see book="utilref" docset="nw40"Utilities Reference for a complete description of the utility.When users access resources on the network, background idxid="w6720"book="_idx" docset="nw312" tidref="i578"authentication processes in NetWare v4.0 verify that the users are who they say they are.Once a user logs in to the network, user trustee rights in the bindery or Directory allow the user access in the network.ID="FM68483"Understanding Network Securityidxid="w6721"book="_idx" docset="nw312" tidref="i4575"Security is vital in maintaining a productive network environment. NetWare provides an extensive security system to protect the data on the network.Network Security LevelsNetWare v2.x, v3.x, and v4.0 have three levels of security that can be used separately or in various combinations. These levels are:File system securityLogin and password securityServer securityFile System Securityidxid="w6722"book="_idx" docset="nw312" tidref="i6177"File system security consists of rights security and attributes security.idxid="w6723"book="_idx" docset="nw312" tidref="i6177"Rights security controls what the user is allowed to access and do to network directories and files. Rights can be granted at either the directory or file level. Rights security is administered by granting trustee assignments to objects and by acquiring effective rights through inheritance and security equivalence.idxid="w6724"book="_idx" docset="nw312" tidref="i6177"Attribute security assigns various characteristics to individual directories and files. Directory and file attributes have priority over rights security and can prevent tasks that effective rights would allow. Attributes can be used to prevent users from:Deleting a file or directoryCopying a fileViewing a file or directoryWriting to a fileidxid="w6725"book="_idx" docset="nw312" tidref="i556"Attributes can also be used to:idxid="w6726"book="_idx" docset="nw312" tidref="i556"Mark a file for single-user access or multiple-user accessMark a file as modified so that a backup program can select it and leave unmodified files aloneidxid="w6727"book="_idx" docset="nw312" tidref="i556"Protect a file from corruption by ensuring that either all changes are made or no changes are made when a file is modifiedLogin and Password Securityidxid="w6728"book="_idx" docset="nw312" tidref="i3560"Login and password idxid="w6729"book="_idx" docset="nw312" tidref="i6177"security controls who can access the network. The network supervisor uses login and password security to:idxid="w6730"book="_idx" docset="nw312" tidref="i3426"Assign usernames to users of the networkidxid="w6731"book="_idx" docset="nw312" tidref="i3426"Require passwordsAdditional password restrictions include a minimum password length, periodic password changes, unique passwords, and a number of grace logins after password expiration.idxid="w6732"book="_idx" docset="nw312" tidref="i3426"Control the use of network resources by restricting where and when users can log inidxid="w6733"book="_idx" docset="nw312" tidref="i3426"Detect intruders who attempt to use a user's account without the correct passwordidxid="w6734"book="_idx" docset="nw312" tidref="i3426"Prevent unauthorized access to the server consoleServer Securityidxid="w6735"book="_idx" docset="nw312" tidref="i6177"Server security controls access to the server console. Access is controlled in three ways:idxid="w6736"book="_idx" docset="nw312" tidref="i5944"Supervisor rights to the server are granted to give specific users rights to use a consoleidxid="w6737"book="_idx" docset="nw312" tidref="i5944"Directory rights are granted so that only specific users have access to the SYS:SYSTEM directory, where key server files are storedServer utilities such as MONITOR and SECURE CONSOLE are used to prevent unauthorized access to the server console.idxid="w6738"book="_idx" docset="nw312" tidref="i4240"NetWare Security for NetWare v4.0NetWare v4.0 identifies the same network security as NetWare v2.x and v3.x. In addition, NetWare v4.0 identifies NetWare Directory Services security.Additional NetWare Directory Services SecurityNetWare Directory Services security controls what objects and properties the user is allowed to access. idxid="w6739"book="_idx" docset="nw312" tidref="i4793"Object rights control what a trustee can do with an idxid="w6740"book="_idx" docset="nw312" tidref="i5944"object. These rights control the object as a single piece in the Directory tree, but don't allow access to information stored within that object (unless the Supervisor object right is granted).idxid="w6741"book="_idx" docset="nw312" tidref="i5944"Property rights control a trustee's access to information stored within the object---that is, the information stored in the object's properties. Each object has several properties to which access is controlled separately.Rights security is administered by granting trustee assignments to objects and by acquiring effective rights through inheritance and security equivalence.ID="FM99067"Understanding idxid="w6742"book="_idx" docset="nw312" tidref="i4568"Network PrintingStandalone PrintingA idxid="w6743"book="_idx" docset="nw312" tidref="i6478"standalone workstation can only print to a printer attached to one of its ports. Print jobs are sent directly to the attached printer. As shown in IDREF="FM52307"Figure 1-7, a printer connected to a single computer allows only the person using that computer to access the printer.LBL="1-7"ID="FM52307"idxid="w6744"book="_idx" docset="nw312" tidref="i6478"Standalone printingFILE="c312b25a.pbm"Network Workstation PrintingNetwork printing allows all users on the network to share network printers. A printer can be connected to the network by connecting either directly to a server or to a network workstation, depending on the configuration of the printer and the network.NetWare uses a print queue, print server, and printer driver to allow several network workstations to print to a network printer. The print server takes print jobs from the print queue and sends them to the printer as shown in ID="FMPrint"IDREF="FM38031"Figure 1-8.LBL="1-8"ID="FM38031"idxid="w6745"book="_idx" docset="nw312" tidref="i4565"Network printingFILE="c312b24a.pbm"Where to Go from HereWith a basic understanding of networking and network functions for NetWare, you are ready to upgrade or install your NetWare workstation.WIDTH="144"If you want toWIDTH="156"Go toWIDTH="144"Set up workstation network  hardwareWIDTH="156"IDREF="FM88739""Preparing Your Workstation  Hardware" on IDREF="FM88739"page 20Prepare your workstation  software for a NetWare  workstation installationIDREF="FM83891""Preparing Your Workstation  Software" on IDREF="FM83891"page 23Prepare the installation  softwareIDREF="FM40337""Preparing Installation Software" on IDREF="FM40337"page 24Additional Information for NetWare v2.x and v3.xWIDTH="180"For more information about WIDTH="228"Refer toWIDTH="180"Understanding NetWare binderyWIDTH="228""book="Concepts" docset="nw312"Bindery" in ConceptsNetwork Printing"book="print" docset="nw312"Printing" in Print ServerPrint queuesConcepts, under "book="concepts" docset="nw312"Print queue"Print serversConcepts, under "book="concepts" docset="nw312"Print server"PrintersConcepts, under "book="concepts" docset="nw312"Printers"NetWare volumesConcepts, under "book="concepts" docset="nw312"Volume"NetWare file system (directory structure)Concepts, under "book="concepts" docset="nw312"Directory Structure"NetWare drivesConcepts, under "book="concepts" docset="nw312"Network Drive Mapping"Additional Information for NetWare v4.0WIDTH="180"For more information about WIDTH="228"Refer toWIDTH="180"Understanding NetWare Directory  ServicesWIDTH="228""book="getstart" docset="nw40"Understanding NetWare Directory Services" in Getting Started with NetWare v4.0Network Printing"book="print" docset="nw40"Printing" in Print ServicesPrint queuesConcepts, under "book="concepts" docset="nw40"Print queue"Print serversConcepts, under "book="concepts" docset="nw40"Print server"PrintersConcepts, under "book="concepts" docset="nw40"Printer"NetWare volumesConcepts, under "book="concepts" docset="nw40"Volume"NetWare file system (directory structure)Concepts, under "book="concepts" docset="nw40"Directory structure"NetWare Directory Services Directory treeConcepts, under "book="concepts" docset="nw40"Directory tree""book="getstart" docset="nw40"Understanding NetWare Directory Services" in Getting Started with NetWare v4.0.NetWare drivesConcepts, under "book="concepts" docset="nw40"Drive mapping"LBL="2"Preparing to Install Workstation SoftwareOverviewThis chapter explains what you need to do before installing NetWare workstation software.WIDTH="264"TopicWIDTH="48"PageWIDTH="264"IDREF="FM88739""Preparing Your Workstation Hardware"WIDTH="48"IDREF="FM88739"20IDREF="FM83891""Preparing Your Workstation Software"IDREF="FM83891"23IDREF="FM40337""Preparing Installation Software"IDREF="FM40337"24IDREF="FM96914""Creating Workstation Installation Diskettes from CD-ROM"IDREF="FM96914"25IDREF="FM67985""Setting Up Your Workstation for Installing from a Network  Directory"IDREF="FM67985"27IDREF="FM62449""Editing the INSTALL.CFG File for DOS and Windows  Installation Software"IDREF="FM62449"32IDREF="FM65627""Upgrading Your IPX Driver to ODI"(tm)IDREF="FM65627"33IntroductionProper preparation is important to the ease and success of your installation. Preparation ensures that your hardware and software are configured properly and that you have the necessary information to complete your workstation installation.This chapter assumes that you are familiar with the following operating systems and hardware:DR-DOS®, PC-DOS®, or MS-DOS® if you are installing NetWare workstation software for DOSWindows v3.x if you are installing NetWare workstation software for WindowsOS/2 v2.x if you are installing NetWare workstation software for OS/2ID="FM88739"Preparing Your Workstation idxid="w6746"book="_idx" docset="nw312" tidref="i2842"HardwareThe following checklists will help you prepare your workstation for installing the NetWare workstation software. If you are upgrading your workstation from a previous version of NetWare, go to IDREF="FM83891""Preparing Your Workstation Software" on page IDREF="FM83891"23.DOS and Windows WorkstationsAn IBM PC (or compatible) with an XT(tm), AT®, 386, or 486 (SX or DX) processor.idxid="w6747"book="_idx" docset="nw312" tidref="i3794"A hard drive with 1.2 MB of storage or a 1.2 MB floppy drive and diskette.A Novell® (or compatible) Remote Reset PROM inserted in each workstation that will boot remotely.A network board installed in your workstation. Record the board settings to use during installation. See IDREF="FM62756""Determining Your Network Board Settings" on page IDREF="FM62756"22 for more information on how to find your board settings. For more information on installing the network board, see the manufacturer's documentation.idxid="w6748"book="_idx" docset="nw312" tidref="i872"Network cabling.Each type of network board requires unique cabling. See the manufacturer's documentation packaged with your network board for requirements.Token-Ring network boards require a cable connection to the MAU before installing the operating system. Otherwise, the TOKEN driver will not load.OS/2 WorkstationsAn IBM PC (or compatible) with a 386 or 486 (SX or DX) processor. OS/2 v2.x operates only with 386 (SX and DX) processors and above because of its 32-bit architecture. OS/2 v1.3x and above cannot operate on an IBM PC or XT.idxid="w6749"book="_idx" docset="nw312" tidref="i3794"A hard drive with 2.2 MB of storage.A Novell (or compatible) Remote Reset PROM inserted in each workstation that will boot remotely.A network board installed in your workstation. Record the board settings to use during installation. See IDREF="FM62756""Determining Your Network Board Settings" on page IDREF="FM62756"22 for more information on how to find your board settings. For more information on installing the network board, see the manufacturer's documentation.idxid="w6750"book="_idx" docset="nw312" tidref="i872"Network cabling.Each type of network board requires unique cabling. See the manufacturer's documentation packaged with your network board for requirements.Token-Ring network boards require a cable connection to the MAU before installing the operating system. Otherwise, the TOKEN driver will not load.ID="FM62756"Determining Your Network Board Settingsidxid="w6751"book="_idx" docset="nw312" tidref="i4494"The workstation installation program requires specific information about the network board installed in your workstation. Record the values for the following settings before loading the workstation installation program:idxid="w6752"book="_idx" docset="nw312" tidref="i2648"Hardware interruptIn most cases, you can use idxid="w6753"book="_idx" docset="nw312" tidref="i2648"IRQ3 or IRQ5 for your network board. If neither IRQ3 nor IRQ5 is available, see the manufacturer's documentation.idxid="w6754"book="_idx" docset="nw312" tidref="i659"Base I/O portEach hardware device included in your workstation must have a different base I/O port setting. For more information on the base I/O port for your network board, see the manufacturer's documentation.idxid="w6755"book="_idx" docset="nw312" tidref="i3754"Media frame typeAll workstations and servers using a single network address must use the same frame type. See "book="ws_dos" docset="nw40"FRAME frame_type" in Workstation for DOS and Windows and "book="ws_os2" docset="nw40"Specifying Frame Types for a Driver" in Workstation for OS/2 for information on frame types supported by common network board drivers.Other settingsThere are other settings unique to the network board installed in your workstation. See the documentation provided with your network board for more information.In most cases, you should leave your network board set to the factory default settings. If you need to change the default settings, see the manufacturer's documentation.idxid="w6756"book="_idx" docset="nw312" tidref="i4494"You can obtain setting information for your network board by using the following procedures.LBL="2-1" INLINE="F"Finding board settingsWIDTH="72"If you have WIDTH="228"ThenWIDTH="72"EISA or  MCA®  network  boardsWIDTH="228"Run the computer's setup or reference program. This  program will list the values for your network board  settings.ISA network  boardsPhysically view the network board to obtain the specific  settings. The documentation provided with your  network board will direct you where to locate each  value.If you have a network connection already, type NVER at the command line to view board settings. ID="FM83891"Preparing Your idxid="w6757"book="_idx" docset="nw312" tidref="i7540"Workstation SoftwareThe following checklists will help you prepare your workstation software for installing a NetWare workstation.If you are using DOS and Windows, you must be running DR DOS v5.x or above, MS-DOS v3.x or above, or PC-DOS v3.x or above.Edit the INSTALL.CFG file. See IDREF="FM62449""Editing the INSTALL.CFG File for DOS and Windows Installation Software" on IDREF="FM62449"page 32.If you are using Windows, you must have a copy of Windows v3.x already installed on your workstation.If you are using OS/2, you must have a copy of OS/2 v2.x already installed on your workstation.(Optional) If you have DOS and Windows workstations running a previous version of NetWare, upgrade your IPX drive to ODI. See IDREF="FM65627""Upgrading Your IPX Driver to ODI" on IDREF="FM65627"page 33 for instructions.ID="FM40337"Preparing idxid="w6758"book="_idx" docset="nw312" tidref="i2842"Installation SoftwareThe following checklists and procedures will help you prepare your NetWare workstation software for installation. If your workstation software is on CD-ROM, go to:idxid="w6759"book="_idx" docset="nw312" tidref="i2842"IDREF="FM96914""Creating Workstation Installation Diskettes from CD-ROM" on page IDREF="FM96914"25 for preparing to install from diskettes.IDREF="FM67985""Setting Up Your Workstation for Installing from a Network Directory" on page IDREF="FM67985"27 for preparing to install from a network directory.If your workstation software is on diskette, complete the following checklist.Prerequisitesidxid="w6760"book="_idx" docset="nw312" tidref="i2842"If installing for DOS and Windows, have working copies of the following NetWare workstation diskettes:idxid="w6761"book="_idx" docset="nw312" tidref="i2864"WSDOS_1WSWIN_1WSDRV_1WSDRV_2idxid="w6762"book="_idx" docset="nw312" tidref="i2842"If installing for OS/2, have working copies of the following NetWare workstation diskettes:WSOS2_1WSOS _2WSDRV_1(Optional) Have working copies of any NetWare compatible third-party network board drivers.idxid="w6763"book="_idx" docset="nw312" tidref="i4494"You will need a third-party MLID(tm) driver for the network board installed in your workstation if one is not provided with the NetWare workstation software. NetWare workstation software supports most network boards. If a driver is not listed for your network board, check the packaging or contact the network board manufacturer to obtain a NetWare-compatible driver. idxid="w6764"book="_idx" docset="nw312" tidref="i2864"ID="FM96914"Creating Workstation Installation Diskettes from idxid="w6765"book="_idx" docset="nw312" tidref="i941"CD-ROMYou can install the CD-ROM either as a DOS volume or as a network device.idxid="w6766"book="_idx" docset="nw312" tidref="i2864"ProcedureFormat high-density diskettes using the DOS FORMAT command.For DOS and Windows, format four diskettes.For OS/2, format three diskettes.Complete the following steps if you set up the CD-ROM as a DOS volume.Install the CD-ROM drive as a DOS device according to manufacturer's instructions.Go to the drive corresponding to the CD-ROM.Change to the CLIENT directory.Go to Step 4.Complete the following steps if you set up the CD-ROM as a network device.Map a drive to SYS:PUBLIC\CLIENT.Change to the drive letter which is mapped to SYS:PUBLIC\CLIENT.Continue with Step 4.Change to one of the following subdirectories.LBL="2-2" INLINE="F"Client subdirectoriesWIDTH="120"If creating diskettes forWIDTH="180"Go to this subdirectoryWIDTH="120"DOSWIDTH="180"DOSWINWindowsDOSWINOS/2OS2idxid="w6767"book="_idx" docset="nw312" tidref="i6295"Set the "nwlanguage" environment variable by typing the following at the command line. (For NetWare v4.0 only. Skip to step 6 if you are installing for any other version.  SET NWLANGUAGE=language <Enter>Replace language with the appropriate language found in the NLS subdirectory under either CLIENT\OS2 or CLIENT\DOSWIN. Type  MAKEDISK drive_letter: <Enter>Replace drive_letter with the diskette drive letter into which you are inserting the empty formatted diskettes. For example, type either:  MAKEDISK A: <Enter>or  MAKEDISK B: <Enter>The MAKEDISK utility copies the client installation files from the CD-ROM directory to the diskettes. It prompts you to insert new formatted diskettes.Label each diskette with the following namesLBL="2-3" INLINE="F"Client diskette labelsWIDTH="48"Diskette  numberWIDTH="120"Label for DOS/WindowsWIDTH="132"Label for OS/2WIDTH="48"1WIDTH="120"WSDOS_1WIDTH="132"WSOS2_12WSWIN_1WSOS2_23WSDRV_1WSDRV_14WSDRV_2Save these diskettes until after you have installed all of the NetWare workstations on your network.idxid="w6768"book="_idx" docset="nw312" tidref="i2842"ID="FM67985"Setting Up Your Workstation for Installing from a Network DirectoryThe following checklist and procedures will help you set up your workstation for installing NetWare workstation software from a network directory. It is the quickest and easiest way to upgrade your NetWare workstation software. This section applies only to workstations that already have a previous version of NetWare workstation software installed. If you are installing a new NetWare workstation for OS/2, go to Chapter 3, IDREF="FM88239""Installing a NetWare Workstation" on page IDREF="FM88239"35. If you are installing a new DOS or Windows workstation, go to IDREF="FM62449""Editing the INSTALL.CFG File for DOS and Windows Installation Software" on page IDREF="FM62449"32.PrerequisitesYou must have a previous version of the NetWare workstation software running on your workstation.A copy of the NetWare workstation software must exist on a network. The NetWare server installation program has features to copy these files. See IDREF="FM27434""Copying Files to a Network Directory" on page IDREF="FM27434"28 for more details.Files for DOS and Windows workstations should be copied to the PUBLIC\CLIENT\DOSWIN directory on volume SYS:. Files for OS/2 workstations should be copied to the PUBLIC\CLIENT\OS2 directory on volume SYS:.You must be logged in to a NetWare server.If you are using DOS or Windows, your workstation must have a drive mapped to the PUBLIC\CLIENT\DOSWIN directory on volume SYS:.If you are using OS/2, your workstation must have a drive mapped to the PUBLIC\CLIENT\OS2 directory on volume SYS:.ID="FM27434"idxid="w6769"book="_idx" docset="nw312" tidref="i2842"Copying Files to a Network DirectoryYou can use the server installation program on the CD-ROM to copy workstation files to the PUBLIC\CLIENT directory on volume SYS:. If you are connecting to a NetWare v3.x network, seebook="install" docset="nw312"Installation and Upgrade for details on using the server installation program. If you are connecting to a NetWare v4.0 network, seebook="install" docset="nw40"Installation and Upgrade for details on using the server installation program.Copying Workstation Software Directly from the CD-ROMTo copy files directly from the CD-ROM, follow the steps below.ProcedureMake a subdirectory named CLIENT under SYS:PUBLIC for the workstation files.Install the CD-ROM drive as a DOS device according to manufacturer's instructions.Copy files from the CLIENT directory on the CD-ROM to SYS:PUBLIC by typing either:  NCOPY source_directory: destination_directory: /s /e /cor  XCOPY source_directory: destination_directory: /s /eFor example, type  NCOPY D:CLIENT\DOSWIN\ H:\PUBLIC\CLIENT\DOSWIN /s /e /cor  XCOPY D:CLIENT\DOSWIN\ H:\PUBLIC\CLIENT\DOSWIN /s /eDo not use the COPY command for this procedure. It is important that the directory structure within each subdirectory is maintained.You can also set up your CD-ROM drive as a volume on your network. This allows you to run the workstation installation programs directly from the subdirectories under CLIENT on the CD-ROM. If you are connecting to a NetWare v3.x network, see book="install" docset="nw312"Installation and Upgrade for information.If you are connecting to a NetWare v4.0 network, see book="supernt" docset="nw40"Supervising the Network for information.Copying Workstation Software Directly from the Workstation DiskettesTo copy files directly from the workstation diskettes, follow the steps below.ProcedureMake the following subdirectories under SYS: PUBLIC for the workstation files.WIDTH="120"If copying files forWIDTH="180"Make this subdirectoryWIDTH="120"DOS and WindowsWIDTH="180"CLIENT\DOSWINOS/2CLIENT\OS2Copy files from the workstation diskettes to the corresponding directories in the PUBLIC directory on volume SYS:.WIDTH="120"Copy files and subdirectories  from WIDTH="180"To the following subdirectoryWIDTH="120"WSDOS_1WSWIN_1WSDRV_1WSDRV_2WIDTH="180"PUBLIC\CLIENT\DOSWINWSOS2_1WSOS2_2WSDRV_1PUBLIC\CLIENT\OS2Type either  NCOPY source_directory: destination_directory: /s /e /cor  XCOPY source_directory: destination_directory: /s /eFor example, type  NCOPY A: H:\PUBLIC\CLIENT\DOSWIN /s /e /cor  XCOPY A: H:\PUBLIC\CLIENT\DOSWIN /s /eDo not use the COPY command for this procedure. It is important that the directory structure within each subdirectory is maintained.LBL="2-4" INLINE="F"DIrectory structure for workstation installation directoriesWIDTH="120"PUBLIC\CLIENT\DOSWIN  Directory StructureWIDTH="180"PUBLIC\CLIENT\OS2 Directory StructureWIDTH="120"\DOSWIDTH="180"\REQUESTR\NLS\LOGIN\OS2\NLS\DOS.NP\SQL\WINDOWS\RPLID="FM71920"Mapping a Drive for Installing from a Network Directoryidxid="w6770"book="_idx" docset="nw312" tidref="i2842"Map a drive to the volume and directory containing the NetWare workstation files. The volume and directory are SYS:PUBLIC\CLIENT\DOSWIN for DOS and Windows and SYS:PUBLIC\CLIENT\OS2 for OS/2. The following procedure shows you how to map a drive to the appropriate volume and directory.ID="FMMappi"ProcedureMap the next network drive to SYS:PUBLIC by typing   MAP N SYS:PUBLIC<Enter>This mapping may already be set up as a search drive in a login script for your workstation. Use the MAP utility to view a list of existing drive mappings.Change to the network drive that is mapped to the PUBLIC subdirectory. For example, if you mapped network drive G:, type  G:<Enter>ID="FM62449"Editing the idxid="w6771"book="_idx" docset="nw312" tidref="i2839"INSTALL.CFG File for DOS and Windows Installation SoftwareThis section applies to DOS and Windows workstations only. If you are using OS/2, go to chapter 3, IDREF="FM88239""Installing a NetWare Workstation" on page IDREF="FM88239"35.You can set up the installation program software for DOS and Windows to suit your particular networking environment. You should edit the [NETCFG] section of the INSTALL.CFG file before installing the workstation software on multiple workstations with similar NET.CFG files.NET.CFG is a configuration file that contains section headings and options that deviate from the established defaults of the workstation software. Use entries in the NET.CFG file to change the workstation's network environment or configuration. For more details on how to edit or create a NET.CFG file, see "book="ws_dos" docset="nw40"Configuring Your Workstation" in Workstation for DOS and Windows.Configuring the idxid="w6772"book="_idx" docset="nw312" tidref="i2839"[NETCFG] section in INSTALL.CFGThe INSTALL.CFG file is copied on the WSDOS_1 diskette. The default configuration for the [NETCFG] section adds a line for the first network drive option only. You will need to edit the INSTALL.CFG file to add lines for other settings under the NetWare DOS Requester(tm) line option. A sample of the [NETCFG] section in the INSTALL.CFG file is as follows:  [NETCFG]     NetWare DOS Requester     FIRST NETWORK DRIVE = FLeave a space of one line between the [NETCFG] heading and the "NetWare DOS Requester" line. Indent all entries under the heading.ID="FM65627"Upgrading Your idxid="w6773"book="_idx" docset="nw312" tidref="i3016"IPX Driver to ODIIf your workstation is using a dedicated IPX driver, you should upgrade to an ODI version. An ODI ( idxid="w6774"book="_idx" docset="nw312" tidref="i4825"Open Data-Link(tm) specification) version of IPX gives your workstation greater functionality by supporting multiple communication protocols. You can upgrade in two ways:Use the workstation installation program to upgrade during installation.Use the WSUPGRD utility to upgrade your version of IPX prior to using the installation program. See Appendix A, IDREF="FM11451""Using the WSUPGRD Utility" on page IDREF="FM11451"125 for information and procedures. Upgrading prior to installation makes a workstation installation virtually automatic. The installation program will recognize network board settings from loaded board drivers which support ODI and prompt you to use the driver and settings it recognizes. When you use WSUPGRD, your version of IPX and network board driver will be updated automatically. Where to Go from HereAfter you have recorded the values for various board settings and your equipment is installed and meets site requirements, you are ready to begin installation. Go to Chapter 3, IDREF="FM88239""Installing a NetWare Workstation" to continue.LBL="3"ID="FM88239"Installing a NetWare WorkstationOverviewThis chapter explains the procedures for installing NetWare workstation software and gives a brief summary of what happens during installation.WIDTH="264"TopicWIDTH="36"PageWIDTH="264"IDREF="FM60333""Understanding the NetWare Requester"WIDTH="36"IDREF="FM60333"36IDREF="FM75873""Installing NetWare for DOS and Windows Workstations"IDREF="FM75873"36IDREF="FM39542""What Happens When You Install for DOS and Windows?"IDREF="FM39542"41IDREF="FM55042""Installing NetWare for OS/2 Workstations"IDREF="FM55042"48IDREF="FM50291""What Happens When You Install for OS/2?"IDREF="FM50291"51IntroductionThe installation program installs the NetWare DOS Requester for DOS and Windows and the NetWare Requester(tm) for OS/2. It also provides resources to edit configuration files for each operating environment to run on NetWare.ID="FM60333"Understanding the NetWare RequesterThe idxid="w6775"book="_idx" docset="nw312" tidref="i4248"NetWare Requester directs network requests from the workstation to the network. After you install the NetWare Requester on your workstation, you can connect to a NetWare network and perform basic network tasks.See Appendix A, "book="ws_dos" docset="nw40"Technical Information" in Workstation for DOS and Windows and Appendix C, "book="ws_os2" docset="nw40"Architecture Diagrams" in Workstation for OS/2 to learn more about how the Requester works.If you are installing a DOS and Windows workstation, go to IDREF="FM75873""Installing NetWare for DOS and Windows Workstations" onpage IDREF="FM75873"36. If you are installing an OS/2 workstation, go to IDREF="FM55042""Installing NetWare for OS/2 Workstations" on page IDREF="FM55042"48.ID="FM75873"Installing NetWare for DOS and Windows Workstationsidxid="w6776"book="_idx" docset="nw312" tidref="i2842"DOS and Windows workstations share the same installation program. To provide for this, the installation program runs within the DOS environment. Review the following checklist to make sure you are prepared to install NetWare workstation software. Close Windows before loading the installation program. The workstation installation program will modify some Windows files that are used when in Windows. Do not install from a Windows DOS Box.If you are installing from a network directory, make sure you have a drive mapped to SYS:PUBLIC. See IDREF="FM71920""Mapping a Drive for Installing from a Network Directory" on page IDREF="FM71920"31.If you are installing from diskettes, make sure you have working copies of the NetWare workstation files.ID="FM50418"What Happens during InstallationThe following things happen when you install NetWare workstation software:A directory is created in the root of the drive from which you boot DOS.All workstation files for DOS and Windows are copied to the directory specified during installation. Five kinds of files are copied:NetWare User Tools files for DOS and WindowsVLM(tm) (Virtual Loadable Module(tm)) program filesVLM ManagerNetwork board driversUnicode® tables with corresponding code pages, numbers and country codes.DOS, Windows, and NetWare configuration files are created or modified.(Windows) A NetWare User Tools group file is created in Windows Program Manager.For detailed information, see IDREF="FM39542""What Happens When You Install for DOS and Windows?" on page IDREF="FM39542"41.Loading the Installation ProgramFor brief instructions, see the Quick Reference Cards for DOS and Windows and the screen instructions to complete the installation. For more detailed information, refer to this manual.Follow the instructions below for steps on how to load the installation program.WIDTH="120"Installing from diskettesWIDTH="180"Installing from idxid="w6777"book="_idx" docset="nw312" tidref="i2842"network directoryWIDTH="120"1. Insert the diskette  labeled WSDOS_1 into a  disk drive.WIDTH="180"1. Change the PUBLIC directory to the  CLIENT\DOSWIN subdirectory. For  example, type    CD\CLIENT\DOSWIN2. Change to the drive  that contains the WSDOS_1 diskette. For  example, type    A:<Enter>2. Type     INSTALL<Enter>3. Type    INSTALL<Enter>3. Follow the instructions on your screen.4. Follow the instructions  on your screen.IDREF="FM40883"Figure 3-1 gives an example of the opening screen in the installation program.LBL="3-1"ID="FM40883"DOS and Windows installation programFILE="c312b47a.pbm"Use the arrow keys to move between the fields. Press <Enter> to modify a field.Installing a Network Board Driveridxid="w6778"book="_idx" docset="nw312" tidref="i4494"The following table will help you with "Step 4" of the workstation installation program. NetWare workstation software supports a majority of network boards. Follow the steps in the chart below to install the driver for your workstation.LBL="3-1" INLINE="F"Installing network  board driversWIDTH="132"If you want toWIDTH="180"Do thisWIDTH="132"Install a driver for a  NetWare-supported  network boardWIDTH="180"Press <Esc>, then replace the WSDOS_1  diskette with a driver diskette (WSDRV_x). Press <Esc> again to display  the list. Use the arrow keys or the  <PgDn> key to move through the list.  Highlight the driver you want to install  and press <Enter>.Install a driver for a network  board not listed in displayPress <Esc>, then replace the WSDOS_1  diskette with a driver diskette which was  included in your network board kit.  Press <Esc> again to display the list. Use  the arrow keys or the <PgDn> key to  move through the list. Highlight the  driver you want to install and press  <Enter>.Install a driver for dedicated  IPX (non-ODI)This will be the case for any  older network boards you  may have without ODI  support. Contact your  board manufacturer for  information not displayed  in the list.Press <Esc>, then replace the WSDOS_1  diskette with a driver diskette (WSDRV_x). Press <Esc> again to display  list. Use the arrow keys or the <PgDn>  key to move through the list. Highlight  the driver listing for "dedicated ipx" and  press <Enter>.Make sure that the network board you installed is supported by NetWare or has a NetWare-compatible driver included.A box will appear, prompting you to modify the value settings for your workstation. The following are some of the main options available:Base I/O portHardware interruptsMedia frame typeThere are numerous other options available depending on your network board type and driver.Refer to the help at the bottom of the page for information about an appropriate value setting for each option.If you are unsure of your workstation`s network board settings, refer to your records or accept the default settings.In order for your modifications or new software installation to function, you need to reboot your workstation. Restart your workstation or press <Ctrl><Alt><Del>.ID="FM39542"What Happens When You Install for DOS and Windows?A Directory Is CreatedA directory is created for the DOS workstation files according to the target directory specified during installation. If you are installing for Windows, the Windows workstation files are copied to the specified Windows directory. (The default is C:\NWCLIENT.)Files Are CopiedAll workstation files for DOS and Windows are copied to the directories specified during installation.Five kinds of files are copied:NetWare User Tools for DOS and WindowsVLM (Virtual Loadable Module) program filesVLM ManagerNetwork board driversUnicode® tables with corresponding code pages, numbers, and country codesDOS and NetWare Configuration Files Are Created or ModifiedThe previous version of CONFIG.SYS and AUTOEXEC.BAT are automatically saved as CONFIG.BNW and AUTOEXEC.BNW. If no previous versions existed, new files are created for you.idxid="w6779"book="_idx" docset="nw312" tidref="i2300"CONFIG.SYSidxid="w6780"book="_idx" docset="nw312" tidref="i1115"The line LASTDRIVE=Z is added to your workstation's CONFIG.SYS file.idxid="w6781"book="_idx" docset="nw312" tidref="i2300"AUTOEXEC.BATidxid="w6782"book="_idx" docset="nw312" tidref="i589"The lines @CALL drive:\ arget_directory\STARTNET and SET NWLANGUAGE=language are added to your workstation's AUTOEXEC.BAT file.idxid="w6783"book="_idx" docset="nw312" tidref="i2300"STARTNET.BATidxid="w6784"book="_idx" docset="nw312" tidref="i6486"The installation program creates a file called STARTNET.BAT in the target directory you specified. It contains the following commands:  @echo off  drive:  cd\ arget directory  LSL  NE2000.COM  IPXODI  VLM  cd\idxid="w6785"book="_idx" docset="nw312" tidref="i2300"NET.CFGThe installation program creates a new NET.CFG file to set a configuration for the network board installed in your workstation. Your old NET.CFG file is saved as NET.BNW.The following listing is an example of a NET.CFG file for a Novell NE2000 Ethernet board. It contains the following settings:  LINK DRIVER NE2000     PORT 300     INT 3     FRAME ETHERNET_802.2  NETWARE DOS REQUESTER     FIRST NETWORK DRIVE = FWindows Configuration Files Are Created or ModifiedWhen you select "Install Windows pieces," the installation program makes changes to your SYSTEM.INI, WIN.INI, and PROGMAN.INI files:For workstations loading Windows from a network server, changes to the SYSTEM.INI and WIN.INI files will need to be made manually. idxid="w6786"book="_idx" docset="nw312" tidref="i2300"SYSTEM.INIidxid="w6787"book="_idx" docset="nw312" tidref="i6684"The installation program adds or makes the following modifications to the SYSTEM.INI file:[boot]The line network.drv= is replaced by network.drv=netware.drv. This will load NetWare User Tools when Windows.[boot.description]The line network.drv= is replaced by network.drv=NetWare (vx.x). This notifies Windows Setup of the NetWare device version you are using. [386Enh]The line network=dosnet is replaced by network=*vnetbios;vipx.386;vnetware.386. This specifies the type of network used with Windows 386 Enhanced mode.The line TimerCriticalSection= is replaced by TimerCriticalSection=10000. NetWare uses this setting to ensure that network traffic on your workstation runs smoothly.Many of the modifications may already exist. Make sure that these modifications have been made if you experience any problems.idxid="w6788"book="_idx" docset="nw312" tidref="i2300"WIN.INIidxid="w6789"book="_idx" docset="nw312" tidref="i7442"The installation program adds or makes the following modifications to the WIN.INI file:[windows]The line load= is replaced by load=nwpopup.exe. This will cause Windows to run the NetWare User Tools application as an icon when Windows is loaded.idxid="w6790"book="_idx" docset="nw312" tidref="i2300"PROGMAN.INIThe installation program adds or makes the following modifications to the PROGMAN.INI file:[Groups]The line Groupx=C:\nwclient\nwuser.exe is added to the list of group files. This will cause Windows to run the NetWare User Tools application as an icon when Windows is loaded.Modifying Windows Configuration Files on a NetWork Directoryidxid="w6791"book="_idx" docset="nw312" tidref="i7460"If the workstation installation program cannot find a Windows system directory, it will copy all necessary Windows files to a directory on your local boot disk. The directory it creates is named SYSTEM. The following files will be copied to this directory:NETWARE.DRVNETWARE.HLPNWPOPUP.EXEVIPX.386VNETWARE.386You will need to copy these files to the system directory for Windows on a network directory. You will also need to make the above changes to the Windows .INI files. See "book="supernt" docset="nw40"Loading Windows onto the Network" in Supervising the Network for details on where the system directory and .INI files are located.Running Windows in Enhanced Modeidxid="w6792"book="_idx" docset="nw312" tidref="i7459"The VIPX.386 device driver for Windows in enhanced mode requires the maximum frame size to be less than 8000 bytes. Network packet size can be set in the NET.CFG file using the "book="ws_dos" docset="nw312"Max Frame Size" option. See book="ws_dos" docset="nw40"Workstation for DOS and Windows for more information.Editing Your AUTOEXEC.BAT File after Installationidxid="w6793"book="_idx" docset="nw312" tidref="i589"This section applies only to workstations that were upgraded from a previous version of NetWare. If you have just installed a new NetWare workstation, go to IDREF="FM45880""Where to Go from Here" on page IDREF="FM45880"47.The workstation installation program for DOS and Windows requires you to edit your AUTOEXEC.BAT file after installation. This is to ensure that the previous shell and driver are not loading on top of the NetWare DOS Requester and network board driver.The workstation installation program inserts the line @CALLdrive:\ arget_directory\STARTNET at the beginning to your workstation's AUTOEXEC.BAT file. The STARTNET.BAT file will load the NetWare DOS Requester and network board driver.Delete or comment out any previous NetWare shells or network board drivers in your AUTOEXEC.BAT that may conflict with the newly installed software. If any of the following files exist in your AUTOEXEC.BAT, delete or comment them out:LSL.COM(tm)Network board driver (e.g. NE2000.COM)IPXODI.COMNETx.COMIPX.COMYour original AUTOEXEC.BAT file is saved as AUTOEXEC.BNW.ID="FM45880"Where to Go from HereAfter installation of your NetWare workstation is completed you need to prepare your workstation for logging in to the network.WIDTH="132"If you want toWIDTH="180"Go toWIDTH="132"Set up your workstation to  logging in to the network.WIDTH="180"IDREF="FM38025""Setting Up Workstations to Log In to  the Network" on page IDREF="FM38025"57Determine your name  context within the  Directory tree (NetWare  v4.0 only).IDREF="FM51934""Understanding Logging In to NDS" on  page IDREF="FM51934"63ID="FM55042"Installing NetWare for OS/2 WorkstationsReview the following checklist to make sure you are prepared to install NetWare workstation software.If you are using LAN Server®, LAN Requester®, or Extended Services®, make sure that they are already installed on your workstation.If you are installing from a network directory, make sure you have a drive mapped to SYS:PUBLIC. See IDREF="FM71920""Mapping a Drive for Installing from a Network Directory" on page IDREF="FM71920"31.If you are installing from diskettes, make sure you have working copies of the NetWare workstation files.ID="FM76167"What Happens during InstallationThe following things happen when you install NetWare workstation software:A directory is created in the root of the drive from which you boot OS/2.All workstation files for OS/2 are copied to the directory specified during installation. Five kinds of files are copied:Requester program filesDLL files (Dynamic Link Libraries)Network board driversUtility files (INSTALL, NPRINTER, NWTOOLS, LOGIN, NLIST, MAP, CX, OS2_TSA)Unicode tables with corresponding code pages numbers and country codesOS/2 and NetWare configuration files are created or modifiedA Novell icon is created in the Desktop window.For detailed information, see IDREF="FM50291""What Happens When You Install for OS/2?" on page IDREF="FM50291"51.Loading the Installation Programidxid="w6794"book="_idx" docset="nw312" tidref="i2842"For brief instructions, see the Quick Reference Cards for OS/2 and the online help to complete the installation. For more detailed information, use this manual and the online helpFollow the instructions below for steps on how to load the installation program.WIDTH="120"Installing from diskettesWIDTH="180"Installing from a idxid="w6795"book="_idx" docset="nw312" tidref="i2842"network directoryWIDTH="120"1. Insert the diskette  labeled WSOS2_1 into a  disk drive.WIDTH="180"1. On the OS/2 workstation, open an  OS/2 Full Screen or Window.     A prompt similar to the following  appears:    [C:\]2. Choose the "Drive A"  icon on the desktop.2. Change to the PUBLIC directory. For  example, if drive G: is mapped to PUBLIC,  type    G:<Enter>3. Select the "Drive A"  icon from the "Drive A  Tree-View."3. At the PUBLIC directory, change  directory to the CLIENT\OS2  subdirectory. For example, type    CD\CLIENT\OS24. Select the  "INSTALL.EXE" icon to  load the installation  program.4. Type     INSTALL<Enter>5. Select "Requester on  workstation..." from the  "Installation" menu.5. Select "Requester on workstation..."  from the "Installation" menu.6. Follow the instructions  on your screen.6. Follow the instructions on your screen.IDREF="FM38578"Figure 3-2 gives an example of the opening screen in the installation program. LBL="3-2"ID="FM38578"Installation program for OS/2 workstationsFILE="c312b13a.pbm"For information on specific topics concerning installation, choose the "Help" option at the top of the screen.Accept the defaults if you do not know whether to change them. Accepting the defaults will be satisfactory in most cases. Even though the files are copied, the Requester is not actually installed until the machine is rebooted. Shut down your computer before you reboot. Press your right mouse button to show the system menu, then choose "Shut down."If you need to configure the NetWare Requester or you don't know if you need to configure it, see Chapter 4, "book="ws_os2" docset="nw40"How to Configure Your Workstation" in NetWare Workstation for OS/2. ID="FM50291"What Happens When You Install for OS/2?A Directory Is CreatedA \NETWARE directory is created in the root of the drive from which you boot OS/2.Files Are CopiedAll Requester files are copied to the directory specified during installation. You can change your settings later without copying additional files from the NWOS2_1 diskette.Five kinds of files are copied:Requester program filesDLL files (Dynamic Link Libraries)Network board driversUtility files (INSTALL, NPRINTER, NWTOOLS, LOGIN, NLIST, MAP, CX, OS2_TSA)Unicode tables with corresponding code pages numbers and country codesMost files on the diskette are compressed. The installation program automatically decompresses them. To decompress an individual file, use the NWUNPACK.EXE utility on the diskette. Type NWUNPACK and the target directory, followed by the name of a file.The Novell Group Icon Is CreatedA group icon called Novell is created on the OS/2 desktop. This group contains:The Requester installation programThe NetWare User ToolsThe NPRINTER remote printing utilityThe OS2_TSA programThe CONFIG.SYS File Is Modifiedidxid="w6796"book="_idx" docset="nw312" tidref="i1115"The previous version of CONFIG.SYS is automatically saved as CONFIG.BAK.The L:\OS2, P:\OS2 and P:\ directories are included at the end of the PATH statement. The P:\ directory works with the P:=SYS:PUBLIC drive mapping for NetWare workstations to access OS/2 utilities. The P:\OS2 directory works with the P:=SYS:PUBLIC drive mapping, which is commonly used in previous versions of NetWare for accessing OS/2 utilities.The C:\NETWARE directory (or directory you specified) is included at the end of the PATH, LIBPATH, and DPATH statements so that OS/2 can find the Requester files.Based on the ODI driver and settings you choose, the NetWare Requester section of CONFIG.SYS includes lines loading Requester components. This section is identified by comments before and after.Do not delete the comments before and after the Requester lines. Everything between these comments is deleted and rewritten when you use the installation program to edit CONFIG.SYS. If you are also running Extended Services, LAN Requester, or other IBM communications products, CONFIG.SYS may be modified even more. See Appendix C, "book="ws_os2" docset="nw40"Architecture Diagrams" of NetWare Workstation for OS/2 for more information about interoperability with IBM products.You should make a backup copy of your CONFIG.SYS file after your workstation installation is completed. Other configuration programs such as IBM's Extended Services may rearrange your CONFIG.SYS file in such a way as to invalidate the NetWare Requester.IDREF="FM40527"Figure 3-3 shows a sample CONFIG.SYS file after installing the Requester.LBL="3-3"ID="FM40527"Sample idxid="w6797"book="_idx" docset="nw312" tidref="i1115"CONFIG.SYS file after Requester installationFILE="c312b34a.pbm"ID="FM54345"Where to Go from HereWith your NetWare workstation installation completed, you are ready to set up your workstation for login to the network.WIDTH="132"If you want toWIDTH="180"Go toWIDTH="132"Set up your workstation to  log inWIDTH="180"IDREF="FM38025"See Chapter 4, "Setting Up  Workstations to Log In to the Network,"  on page IDREF="FM38025"57Modify your NET.CFG file  for NetWare v2.x and v3.x  workstations to simplify  loginSee Chapter 4, IDREF="FM95233""Modifying Your  NET.CFG for Logging In to NetWare  v2.x and v3.x" on page IDREF="FM95233"58Modify your NET.CFG file  for NetWare v4.0  workstations to simplify  loginSee Chapter 4, IDREF="FM95233""Modifying Your  NET.CFG for Logging In to NetWare  v4.0" on page IDREF="FM95233"60Learn more about logging  in to NDSSee Chapter 4, IDREF="FM51934""Understanding Logging  In to NDS" on page IDREF="FM51934"63LBL="4"ID="FM38025"Setting Up Workstations to Log In to the Network OverviewThis chapter explains how to modify your NET.CFG file to simplify logging in to a NetWare network.WIDTH="264"TopicWIDTH="48"PageWIDTH="264"IDREF="FM95233""Modifying Your NET.CFG for Logging In to NetWare v2.x  and v3.x"WIDTH="48"IDREF="FM95233"58IDREF="FM95233""Modifying Your NET.CFG for Logging In to NetWare v4.0"IDREF="FM95233"60IDREF="FM20828""Editing the NetWare Requester for DOS Section"IDREF="FM20828"61IDREF="FM37820""Editing the NetWare Requester for OS/2 Section"IDREF="FM37820"62IDREF="FM51934""Understanding Logging In to NDS" (For NetWare v4.0 only)IDREF="FM51934"63IntroductionProper workstation setup can make logging in to the network virtually transparent. This chapter assumes that the following tasks are completed.A User object or user account is created for each userNetWare workstation software is installedA home directory is created for each userUsers with NetWare v2.x or v3.x workstation connections to a Netware v4.0 network must have a User object created in the container where the bindery-based server's context is set. NetWare v2.x or v3.x users do not need to know their context because they log in to the server rather than the Directory tree.ID="FM95233"Modifying Your NET.CFG for Logging In to NetWare v2.x and v3.xidxid="w6798"book="_idx" docset="nw312" tidref="i4092"When logging in to NetWare v2.x and 3.x, you attach to an individual server. Following, you make additional attachments to other servers on which you have a user account.ID="FM99068"Using the Preferred Server Settingidxid="w6799"book="_idx" docset="nw312" tidref="i5135"Use the Preferred Server setting in the idxid="w6800"book="_idx" docset="nw312" tidref="i4092"NET.CFG file to direct the workstation software to the server on which your user information is located. For networks with multiple servers, this setting is very useful to speed up logging in to the network. This setting also allows you to log in with only your username.The setting for DOS and Windows workstations is as follows:  idxid="w6801"book="_idx" docset="nw312" tidref="i5135"preferred server =server_nameThe setting for OS/2 workstations is as follows:  preferred server server_nameDo not use both the Preferred Server and Preferred Tree settings simultaneously. The second setting will override the first.ID="FM20828"Adding the Preferred Server Setting to NET.CFG for DOS and Windowsidxid="w6802"book="_idx" docset="nw312" tidref="i4248"The Netware DOS Requester option allows you to configure the way your DOS and Windows workstation software interacts with the network. If you are using OS/2, see IDREF="FM37820""Editing the NetWare Requester for OS/2 Section" on page IDREF="FM37820"62.ProcedureOpen your NET.CFG file in a text editor.Your workstation's NET.CFG file was copied to the target directory for DOS files specified during software installation.Under the "NetWare DOS Requester" option, type      preferred server=server_nameFor example, type      preferred server=mktsalesExample of the NetWare Requester for DOS Section  idxid="w6803"book="_idx" docset="nw312" tidref="i4248"NetWare DOS Requester     Preferred Server=mktsales     First Network Drive=fID="FM20828"Adding the Preferred Server Setting to NET.CFG for OS/2The Netware Requester option allows you to configure the way your OS/2 workstation software interacts with the network. This section doesn't apply to DOS and Window users. See IDREF="FM20828""Editing the NetWare Requester for DOS Section" on page IDREF="FM20828"61.ProcedureOpen your NET.CFG file in a text editor.Your workstation's NET.CFG file was copied to the target directory specified during software installation. Under the "NetWare Requester" option, type      preferred server server_nameFor example, type      preferred server mktsalesExample of the NetWare Requester Line for OS/2  idxid="w6804"book="_idx" docset="nw312" tidref="i4349"Netware Requester  Preferred server mktsalesGo to Chapter 5, IDREF="FM67133""Workstation Login" page IDREF="FM67133"67 for details on how to proceed. ID="FM95233"Modifying Your NET.CFG for Logging In to NetWare v4.0idxid="w6805"book="_idx" docset="nw312" tidref="i4092"When logging in to NetWare v4.0, you don't attach to individual servers as with previous versions of NetWare, but you log in to the entire network.With your idxid="w6806"book="_idx" docset="nw312" tidref="i1097"complete name (CN), you can simplify the login process by adding information to your workstation's idxid="w6807"book="_idx" docset="nw312" tidref="i4092"NET.CFG file. You will need to add lines to the NetWare Requester option for OS/2 workstations and NetWare DOS Requester option for DOS and Windows workstations.idxid="w6808"book="_idx" docset="nw312" tidref="i3387"If you add lines for the following settings, you will not need to type your complete name each time you log in to the network after booting your workstation. The settings are:Name ContextPreferred TreeYou must know your context before making these modifications. Without knowing the context, you will not be able to add entries for the above settings. See IDREF="FM51934""Understanding Logging In to NDS" on page IDREF="FM51934"63.ID="FM48848"Using the Name Context Settingidxid="w6809"book="_idx" docset="nw312" tidref="i3986"Using the name context setting in the idxid="w6810"book="_idx" docset="nw312" tidref="i3983"NET.CFG file will inform the Requester of your name context within the Directory tree. The login utility will then locate your User object and connect you to the network. Add this option setting to your NET.CFG file if you are using NetWare v4.0. The setting for DOS and Windows workstations is as follows:  idxid="w6811"book="_idx" docset="nw312" tidref="i3986"name context="name_context"The setting for OS/2 workstations is as follows:  name context "name_context"The default is at the root for this setting, which may cause confusion if duplicate usernames exist within a Directory tree. If you are using a previous version of the NetWare shell on your workstation, the name context setting is invalid. NetWare v4.0 creates a User object for you in the same container as the NetWare Server object to which you will log in. (Bindery emulation is set by default for every NetWare Server object that is installed.) Users log in directly to a server rather than the Directory tree.ID="FM55326"Using the Preferred Tree Settingidxid="w6812"book="_idx" docset="nw312" tidref="i5142"Use the Preferred Tree setting in the idxid="w6813"book="_idx" docset="nw312" tidref="i4092"NET.CFG file to direct the Requester to the Directory tree where your name context is set. The login utility will then search only the preferred Directory tree.Add this setting to your NET.CFG file if you are using NetWare v4.0 on a network with multiple Directory trees. The setting for DOS and Windows workstations is as follows:  idxid="w6814"book="_idx" docset="nw312" tidref="i5142"preferred tree=tree_nameThe setting for OS/2 workstations is as follows:  preferred tree tree_nameThe default is at the root for this setting. Because of this, it is important that the Preferred Tree setting is used to avoid confusion if duplicate usernames exist within separate Directory trees.Do not use both the Preferred Server and Preferred Tree settings simultaneously. The second setting will override the first.ID="FM20828"Editing the NetWare Requester for DOS Sectionidxid="w6815"book="_idx" docset="nw312" tidref="i4248"The Netware DOS Requester option allows you to configure the way your DOS and Windows workstation software interacts with the network. If you are using OS/2, see IDREF="FM37820""Editing the NetWare Requester for OS/2 Section" on page IDREF="FM37820"62.ProcedureOpen your NET.CFG file in a text editor.Your workstation's NET.CFG file was copied to the target directory specified during software installation.Under the "NetWare DOS Requester" option, type      name context="complete_name"For example, type      name context="esayers.sales.novell us"If your network has multiple Directory trees, type      preferred tree=preferred_tree_nameFor example, type      preferred tree=novell usExample of the NetWare Requester for DOS Section  idxid="w6816"book="_idx" docset="nw312" tidref="i4248"NetWare DOS Requester     name context "Esayers.sales.novell us"     preferred tree=novell us     first network drive=fID="FM37820"Editing the NetWare Requester for OS/2 Sectionidxid="w6817"book="_idx" docset="nw312" tidref="i4342"The Netware Requester option allows you to configure the way your OS/2 workstation software interacts with the network. This section doesn't apply to DOS and Window users. See IDREF="FM20828""Editing the NetWare Requester for DOS Section" on page IDREF="FM20828"61.ProcedureOpen your NET.CFG file in a text editor.Your workstation's NET.CFG file was copied to the target directory specified during software installation. Under the "NetWare Requester" option, type      name context "complete_name"For example, type      name context "esayers.sales.novell us"If your network has multiple Directory trees, type      preferred tree preferred_tree_nameAn example of this is:      preferred tree novell usExample of the NetWare Requester Line for OS/2  idxid="w6818"book="_idx" docset="nw312" tidref="i4349"Netware Requester  name context "esayers.sales.novell us"  preferred tree novell usID="FM51934"Understanding Logging In to NDSidxid="w6819"book="_idx" docset="nw312" tidref="i3387"NetWare Directory Services (NDS) makes logging in to the network convenient. User information resides in a global database. Each User is assigned a position or context within the global database that informs the network where your workstation is located in relationship to the entire network. This idxid="w6820"book="_idx" docset="nw312" tidref="i1230"context is referred to as your"name context."When you log in to the network, the LOGIN utility must know where your particular User object is located---its context. The User object's context also forms its idxid="w6821"book="_idx" docset="nw312" tidref="i1097"complete name. The path from the object to the root of the tree forms the object's complete name, which is unique to other object's names.Your User object's complete name is a bottom-up traversal of the tree, from the object up to the root.Using Your Complete Name for Logging In to the Networkidxid="w6822"book="_idx" docset="nw312" tidref="i1097"When you use a complete name of a User object, the common name of it is listed first, followed by a period (.), then the name of the container object, also followed by a period, and on up through the Organization object name (and the Country object name, if used). So your User object's complete name could be represented by:Common name.Organizational Unit name.Organization name. Country nameThis depends on the way your network is defined. Specifying the Name Type of an Objectidxid="w6823"book="_idx" docset="nw312" tidref="i4005"At times, such as when you move from one container object to another, you must include the name type of the object when typing out the complete name of the object. A name type distinguishes the class of object to which you are referring, such as a User object or an Organizational Unit object.For example, you could express:ESAYERS.SALES PV.SALES.NOVELL US as:CN=ESAYERS.OU=SALES PV.OU=SALES.O=NOVELL USwhere CN is the common name of the User object, OU is the Organizational Unit name, and O is the Organization name.Changing Your Contextidxid="w6824"book="_idx" docset="nw312" tidref="i3983"If you are referring to an idxid="w6825"book="_idx" docset="nw312" tidref="i1230"object that is in the same container as your User object, then you need to refer to that object only by its common name, instead of by its complete name. See Chapter 2, "book="getstart" docset="nw40"Understanding NetWare Directory Services," in Getting Started for more details.You must always include the name type of the object in complete names when you include the Country object in your Directory tree. This means that even when you refer to objects located in the same container object, you must designate the name type (CN or OU or O) of the object.ID="FM90992"Logging In to Your ContextProcedureidxid="w6826"book="_idx" docset="nw312" tidref="i3387"Type:  login contextReplace context with your complete name. For example, type  F:\login esayers.sales.novell usType your user password if required.What to Do Now?Make sure that necessary modifications to your NET.CFG file are completed.Log in to your workstation. Go to Chapter 5, IDREF="FM67133""Workstation Login" on page IDREF="FM67133"67.LBL="5"ID="FM67133"Workstation LoginOverviewThis chapter explains how to log in to a NetWare network from a NetWare workstation.WIDTH="264"TopicWIDTH="48"PageWIDTH="264"IDREF="FM79231""Logging In from the DOS Prompt"WIDTH="48"IDREF="FM79231"68IDREF="FM96378""Logging In from Windows"IDREF="FM96378"70IDREF="FM53896""Logging In from OS/2"IDREF="FM53896"72IDREF="FM18105""Logging In from NWTOOLS"IDREF="FM18105"75IntroductionThis chapter assumes that the following tasks are completed:NetWare workstation software is installed.Your workstation NET.CFG file has been modified for login.With the necessary modifications made to your NET.CFG file, you need only your username and password to log in to a preferred server or a NetWare v4.0 network.WIDTH="132"If you are logging in from: WIDTH="180"Go toWIDTH="132"A DOS promptWIDTH="180"IDREF="FM79231""Logging In from the DOS Prompt" on  page IDREF="FM79231"68WindowsIDREF="FM96378""Logging In from Windows" on page IDREF="FM96378"70The OS/2 command lineIDREF="FM83119""Logging In from the OS/2 Command  Line" on page IDREF="FM83119"72An OS/2 Virtual DOS  Session (VDOS)IDREF="FM18207""Logging In from an OS/2 Virtual DOS  Session (VDM)" on page IDREF="FM18207"73An OS/2 Virtual MS-DOS  BOOT Session (VM BOOT)IDREF="FM94267""Logging In from an OS/2 Virtual DOS  Boot Session (VMBOOT)" on page IDREF="FM94267"74.OS/2 DesktopIDREF="FM18105""Logging In from NWTOOLS" on  page IDREF="FM18105"75.ID="FM79231"Logging In from the DOS Promptidxid="w6827"book="_idx" docset="nw312" tidref="i3387"The login program will connect your workstation to the network. The NetWare DOS Requester automatically maps the first network drive to your workstation. Follow the steps below to log in to a bindery server or a NetWare v4.0 network:idxid="w6828"book="_idx" docset="nw312" tidref="i3387"ProcedureLoad the DOS Requester.If your workstation uses an ODI network board driver, load the following programs:LSL.COMNetwork board driver (e.g. NE2000.COM)IPXODI.COMVLM.EXEIf your workstation uses a dedicated IPX driver (non-ODI), load the following programs:IPX.COMVLMChange to the first network drive. Type  F: <Enter>The NetWare DOS Requester automatically maps the first network drive for your workstation. The default setting is drive F:. To change the default, edit your NET.CFG file.Log in to the network in one of the following ways:To log in using your username only, type  login usernameFor example, type  login esayersTo log in to a specific server, type  login servername\usernameFor example, type  login tsmkt\esayersType your password if required.Logging In to NetWare v4.0 from a idxid="w6829"book="_idx" docset="nw312" tidref="i690"NetWare v2.x and v3.x Workstationidxid="w6830"book="_idx" docset="nw312" tidref="i3387"ProcedureType  login server/username /bReplace server with the name of the idxid="w6831"book="_idx" docset="nw312" tidref="i690"bindery server. Replace username with your username. For example:  F:\login tsmkt/esayers /bType your password if required.ID="FM96378"Logging In from Windowsidxid="w6832"book="_idx" docset="nw312" tidref="i3387"Use the NetWare User Tools in Windows to log in to NetWare v2.x, v3.x, and v4.0.ProcedureLoad the idxid="w6833"book="_idx" docset="nw312" tidref="i3387"DOS Requester.If your workstation uses an ODI network board driver, load the following programs.LSL.COMNetwork board driver (e.g. NE2000.COM)IPXODI.COMVLM.EXEIf your workstation uses a dedicated IPX driver (non-ODI), load the following programs:IPX.COMVLMStart Windows.To load the NetWare User Tools, choose the "NWuser" icon from the "NetWare" group.The following screen appears:LBL="5-1"NetWare ConnectionsFILE="c312b08a.pbm"Choose the server icon.The "NetWare Connections" window displays available resources.Choose the resource to which you want to log in from the "Resources" list.Choose "Login."Choose the help button for more details.The "Login" option does not run a login script for your workstation. Use the "Permanent" option in the "NetWare Drive Connections window" to set up your workstation drive mappings. If you want to run a login script, your initial login should be done at the command line with the LOGIN utility.ID="FM53896"Logging In from OS/2OS/2 supports a variety of operating system platforms referred to as sessions. The following headings will direct you to the kind of login that works best with the platform you use.WIDTH="132"If you are logging in from: WIDTH="180"Go toWIDTH="132"The OS/2 command  lineWIDTH="180"IDREF="FM83119""Logging In from the OS/2 Command  Line" on page IDREF="FM83119"72An OS/2 Virtual DOS  Session (VDOS)IDREF="FM18207""Logging In from an OS/2 Virtual DOS  Session (VDM)" on page IDREF="FM18207"73An OS/2 Virtual MS-DOS  BOOT Session (VM BOOT)IDREF="FM94267""Logging In from an OS/2 Virtual DOS  Boot Session (VMBOOT)" on page IDREF="FM94267"74.OS/2 DesktopIDREF="FM18105""Logging In from NWTOOLS" on  page IDREF="FM18105"75.ID="FM83119"Logging In from the OS/2 Command Line idxid="w6834"book="_idx" docset="nw312" tidref="i3387"The NetWare Requester automatically maps drive L: to the first network drive mapped to the SYS:LOGIN\OS2 directory. However, you should log in from your NetWare workstation directory. C:\NETWARE is the default directory. The login program connects your workstation to the network.ProcedureOpen an OS/2 Full Screen or Window.A prompt similar to the following appears:  [C:/]Log in to the network in one of the following ways:To log in using your username only, type  login usernameFor example, type  login esayersTo log in to a specific server, type  login servername\usernameFor example, type  login tsmkt\esayersType your password if required.ID="FM94947"Logging In to NetWare v4.0 from a idxid="w6835"book="_idx" docset="nw312" tidref="i690"NetWare v2.x or v3.x Workstationidxid="w6836"book="_idx" docset="nw312" tidref="i3387"ProcedureType:  login server/username /bReplaceserver with the name of the bindery server. Replace username with your username. For example, type  F:\login tsmkt/esayers /bType your password if required.ID="FM18207"Logging In from an OS/2 Virtual DOS Session (VDM)idxid="w6837"book="_idx" docset="nw312" tidref="i3387"Logging in from an OS/2 VDM environment is the same as logging in from a DOS prompt. See " Virtual DOS and Windows Sessions" in book="ws_os2" docset="nw312"Workstation for OS/2 for information.You cannot log in to a NetWare v4.0 network from a virtual DOS session unless the network supports idxid="w6838"book="_idx" docset="nw312" tidref="i690"bindery emulation. If a NetWare v4.0 network supports bindery emulation, your DOS session will be seen as a bindery-based workstation.ProcedureLoad the NetWare shell. Type  NETX.EXEThe OS/2 VDM environment does not support NetWare Directory Services (NDS) and the v4.0 VLMs. This means that you can log in only to a v3.x server. You must first load NETX.EXE before login is initiated.Open a VDM Full Screen or Window.A prompt similar to the following appears:  [C:/]Change to network drive L:. Type  L:<Enter>The NetWare Requester automatically maps drive L: to the first network drive.Type  login server/username /bReplace server with the name of the bindery server. Replace username with your username. For example, type  F:\login tsmkt/esayers /bType your password if required.ID="FM94267"Logging In from an OS/2 Virtual DOS Boot Session (VMBOOT)idxid="w6839"book="_idx" docset="nw312" tidref="i3387"Logging in from an OS/2 VM Boot environment is the same as logging in from a DOS prompt. See IDREF="FM79231""Logging In from the DOS Prompt" on page IDREF="FM79231"68 for information. See "book="ws_os2" docset="nw40"Virtual DOS and Windows Sessions" in Workstation for OS/2 for information.You must first open a VM BOOT full screen or window before initiating login procedures from the DOS prompt in OS/2.ID="FM18105"Logging In from NWTOOLSidxid="w6840"book="_idx" docset="nw312" tidref="i3387"Use NWTOOLS idxid="w6841"book="_idx" docset="nw312" tidref="i3387"on the desktop to log in to the network.ProcedureChoose the Novell icon on your OS/2 desktop window.From the Novell-Icon View on your desktop, choose the "NetWare Tools" icon.The NetWare Tools windows appears.Choose the "Tools" option from the menu bar.A menu list appears.Select the "Tree" option from the menu list.The Directory Tree window appears.Choose the "Tree" option from the menu bar.A menu list appears.Select "Login."The following dialog appears.LBL="5-2"Login to Directory Tree windowFILE="c312b26a.pbm"Log in to the network.To log in to a v2.x or v3.x or v4.0 server, select "Server."To log in to a NetWare v4.0 Directory tree, select "Tree."Enter your username and password into the appropriate fields.Choose "Login."If the login is unsuccessful, check your context and try again.For more information about this Tool, choose Help.The "Login" option does not run a login script for your workstation. Use the "Save Settings" option in the "Network" menu to maintain your connections. If you want to run the login script, your initial login should be done at the command line with the LOGIN utility.Where to Go from HereWith your login completed, you are ready to use the NetWare User Tools for DOS, Windows, or OS/2, depending on your particular workstation platform. Go to Chapter 6, IDREF="FM23643""Using Workstation Tools" page IDREF="FM23643"77.LBL="6"ID="FM23643"Using Workstation ToolsOverviewThis chapter briefly explains how you can use the NetWare User Tools to perform common network tasks.WIDTH="264"TopicWIDTH="48"PageWIDTH="264"IDREF="FM56760""Starting NETUSER"WIDTH="48"IDREF="FM56760"79IDREF="FM32927""Starting NetWare User Tools for Windows"IDREF="FM32927"84IDREF="FM94213""Accessing and Changing Directory and File Attributes"IDREF="FM94213"98IDREF="FM56032""Starting NetWare User Tools for OS/2"IDREF="FM56032"101IntroductionUse the NetWare User Tools to display and modify the current status of your workstation, drive mappings, servers, printers, queues, volumes, and other necessary information.NetWare User Tools are compatible with NetWare v2.x, v3.x, and v4.0 networks.NetWare User Tools are available for DOS, Windows, and OS/2.PrerequisitesComplete the procedures in Chapter 5.If you are using NetWare v4.0, you should also be familiar with the following topics inConcepts:WIDTH="132"For more information aboutWIDTH="180"Refer toWIDTH="132"NetWare Directory ServicesWIDTH="180""book="concepts" docset="nw40"NetWare Directory Services" in ConceptsContext"book="concepts" docset="nw40"Context" in ConceptsObjects"book="concepts" docset="nw40"Objects" in ConceptsProperties"book="concepts" docset="nw40"Properties" inConceptsPrint queues"book="concepts" docset="nw40"Print queue" in ConceptsIf you are using NetWare v2.x or 3.x, you should also be familiar with the following topics inConcepts:WIDTH="132"For more information aboutWIDTH="180"Refer toWIDTH="132"BinderyWIDTH="180""book="concepts" docset="nw312"Bindery" in ConceptsObjects"book="concepts" docset="nw312"Object" in ConceptsProperties"book="concepts" docset="nw312"Property" inConceptsPrint queues"book="concepts" docset="nw312"Printing" in ConceptsID="FM56760"Starting NETUSERPrerequisitesidxid="w6842"book="_idx" docset="nw312" tidref="i4194"Before you can start NETUSER, your workstation requires the following:A physical connection to the network.DR DOS, PC-DOS, or MS-DOS loaded and running.The DOS Requester files loaded and running. See IDREF="FM60333""Understanding the NetWare Requester" on page IDREF="FM60333"36.An attachment to the network.ProcedureMap the next network drive to SYS:PUBLIC by typing  MAP N SYS:PUBLIC<Enter>This mapping may already be set up as a search drive in a login script for your workstation. Use the MAP utility to view a list of existing drive mappings.Change to the network drive that is mapped to the PUBLIC subdirectory. For example, if you mapped network drive G:, type  G:<Enter>Start NETUSER. Type  NETUSER<Enter>Using NETUSERidxid="w6843"book="_idx" docset="nw312" tidref="i4194"IDREF="FM82673"Figure 6-1 shows you the tasks you can do with NETUSER.LBL="6-1"ID="FM82673"NETUSER TasksFILE="c312b40a.pbm"IDREF="FM83712"Figure 6-2is an example of the NETUSER utility screen.LBL="6-2"ID="FM83712"NetWare User Tools for DOS Menu OptionsFILE="c312b36a.pbm"Accessing Online HelpTo see a list of commands and the procedures you can perform with NETUSER, press <F1>.Printingidxid="w6844"book="_idx" docset="nw312" tidref="i5537"Use the "Printing" option toSet up print queuesControl network printingView information about network printingRedirect a printer port to the networkMessagesidxid="w6845"book="_idx" docset="nw312" tidref="i3869"Use the "Messages" option toSend a brief message from your workstation to one or more users or groups on the networkDisable or enable incoming messages sent from other workstationsDrivesidxid="w6846"book="_idx" docset="nw312" tidref="i1723"Use the "Drives" options toView current drive idxid="w6847"book="_idx" docset="nw312" tidref="i3738"mappingsCreate or change network drive mappingsMap a drive to a fake root directoryMap the next available driveAttachmentsidxid="w6848"book="_idx" docset="nw312" tidref="i1204"Use to "Attachments" options to Create or delete network attachmentsidxid="w6849"book="_idx" docset="nw312" tidref="i4980"Change your passwordView server informationModify login scriptsChange ContextThis option is only available in NetWare Directory Services mode. Use the "Change Context" option toBrowse the Directory treeChange your current contextIf the resource you want is not listed, check to see if you are first attached to the server containing this resource. For more information about this option, choose "Help."Exiting NETUSERYou exit NETUSER through the "Exit?" menu box. This menu prompts you to choose "Yes" or "No" to exit. You can display this menu box in two ways:Press the<Esc> key until the "Exit?" menu box appears. Then select "Yes" and press <Enter>.Press <Alt><F10> anywhere within NETUSER to display the "Exit?" menu box. Then select "Yes" and press <Enter>.Where to Go from HereWith a basic understanding of NETUSER, you are ready to set up network printing for your workstation platform. See IDREF="FM46147""Setting Up Printing for DOS Workstations" on page IDREF="FM46147"116.ID="FM32927"Starting idxid="w6850"book="_idx" docset="nw312" tidref="i4435"NetWare User Tools for WindowsPrerequisitesidxid="w6851"book="_idx" docset="nw312" tidref="i4435"Before you can start NetWare User Tools for Windows, your workstation requires the following:A physical connection to the network.DR DOS, PC-DOS, or MS-DOS loaded and running.The DOS Requester files loaded and running. See IDREF="FM60333""Understanding the NetWare Requester" on page IDREF="FM60333"36.A copy of Windows v3.x installed on your workstation.ProcedureStart Windows.Press <F6> or select the "NWuser" icon in the "NetWare" program group.If the NWuser icon is not displayed, you can also access NetWare User Tools for Windows by creating a Program Object in the Windows Program Manager with NWUSER.EXE. You can find the NWUSER.EXE file in your target directory for the workstation installation. Using NetWare User Tools for WindowsThe idxid="w6852"book="_idx" docset="nw312" tidref="i4435"NetWare User Tools for Windows provide you with a graphical way of accessing network resources, such as volumes, directories, printers, and users. The NetWare User Tools for Windows also allow you to configure your workstation and customize NetWare User Tools display settings.You can do the following with the NetWare User Tools for Windows:Manage drive mappingsManage printer connections and setupManage server connectionsSend messagesModify settingsSet the NetWare User Tools hotkeyChange directory and file propertiesUsing Quick Keysidxid="w6853"book="_idx" docset="nw312" tidref="i4435"Each Tool in the NetWare User Tools for Windows can be accessed by using quick keys. The available quick keys are listed in IDREF="FM68091"Table 6-1 .LBL="6-1" INLINE="F"ID="FM68091"Quick key menuWIDTH="180"Tool WIDTH="132"Quick key WIDTH="180"Exit WIDTH="132"<Alt><X>NetWare Drive Connections <Alt><D>NetWare Printer Connections <Alt><P>NetWare Connections <Alt><C> NetWare Send Messages <Alt><M>NetWare Settings <Alt><S>NetWare User Tools for Windows Help <Alt><H>User Define 1<Alt><1>User Define 2<Alt><2>Using the Menu Baridxid="w6854"book="_idx" docset="nw312" tidref="i4435"The menu bar shows menu options you can use. To complete a task, first choose the button that corresponds with the task or connection you are performing. See IDREF="FM48856"Figure 6-3for an example of the menu bar.LBL="6-3"ID="FM48856"Menu bar for NetWare User Tools for WindowsFILE="c312b38a.pbm"Each time you select a menu option, the corresponding button will depress or a dialog box appears. If an option is grayed, that option is not active or available.All connections can be made by choosing the corresponding button or drag-and-drop. Accessing Online HelpTo see a list of commands and the procedures you can perform with NetWare User Tools for Windows, choose the "Help" button from the menu bar.NetWare Drive Connectionsidxid="w6855"book="_idx" docset="nw312" tidref="i1723"Use the "NetWare Drive Connections" window to idxid="w6856"book="_idx" docset="nw312" tidref="i3740"map network resources in the Directory Tree and file system to your workstation drives. Select the resource you want to connect in the "Resources" list, then choose a workstation drive. Now, choose the "Map" button at the bottom of the window. Keyboard entry is done within the "Path" field.For example, see IDREF="FM73324"Figure 6-4 for "NetWare Drive Connections."LBL="6-4"ID="FM73324"NetWare Drive ConnectionsFILE="c312b03a.pbm"When using the "NetWare Drive Connections" window, remember:You must first log in to a Directory Services tree or server that contains the object for which you want to connect before using "NetWare Drive Connections."NetWare User Tools for Windows will recognize all drive mappings that exist before starting Windows. However, when you are using a DOS Box inside Windows, your previous search drives are disabled.Viewing the "Resources" ListThe "Resources" list within the "NetWare Drive Connections" window contains the following:VolumesDirectoriesNetWare Directory Services objectsNetWare Directory Services containersThe volumes and directories are listed in a hierarchical structure. Choose the "Volume" icon to display subdirectories. NetWare Printer Connectionsidxid="w6857"book="_idx" docset="nw312" tidref="i5537"Use the "NetWare Printer Connections" window to capture network print queues to your workstation printing ports. Select the resource you want to connect in the "Resources" list, then choose a workstation port. Now, choose the "Capture" button at the bottom of the window. Keyboard entry is done within the "Queue" field.For example, see IDREF="FM52012"Figure 6-5 for "NetWare Printer Connections."LBL="6-5"ID="FM52012"NetWare Printer ConnectionsFILE="c312b05a.pbm"When using the "NetWare Printer Connections" window, remember:You must first log in to a server or Directory Services tree that contains the object for which you want to connect before using "NetWare Printer Connections."NetWare User Tools for Windows will recognize all print queue captures that exist before starting Windows. Viewing the "Resources" ListThe "Resources" list within the "NetWare Printer Connections" window contains the following:Printer objectsPrint queue objectsSetting Printer Optionsidxid="w6858"book="_idx" docset="nw312" tidref="i5537"Use the "LPT: Settings" option to access the "Printer Options for LPT:" window. IDREF="FM88064"Table 6-2 lists settings you can assign.LBL="6-2" INLINE="F"ID="FM88064"LPT: setting optionsWIDTH="84"LPT: setting optionWIDTH="228"This functionWIDTH="84"" idxid="w6859"book="_idx" docset="nw312" tidref="i4672"Notify" idxid="w6860"book="_idx" docset="nw312" tidref="i3579"WIDTH="228"Provides a confirmation of print job completion." idxid="w6861"book="_idx" docset="nw312" tidref="i2490"Formfeed" idxid="w6862"book="_idx" docset="nw312" tidref="i3579"Places a page break between print jobs." idxid="w6863"book="_idx" docset="nw312" tidref="i1247"Copies" idxid="w6864"book="_idx" docset="nw312" tidref="i3579"Specify the number of copies to print." idxid="w6865"book="_idx" docset="nw312" tidref="i1817"Enable Tabs" idxid="w6866"book="_idx" docset="nw312" tidref="i3579"Specifies the number of characters in a tab stop." idxid="w6867"book="_idx" docset="nw312" tidref="i1818"Enable  Timeout" idxid="w6868"book="_idx" docset="nw312" tidref="i3579"Specifies the amount of time before the print buffer  is closed and the job is sent to a printer." idxid="w6869"book="_idx" docset="nw312" tidref="i1813"Enable  Banner" idxid="w6870"book="_idx" docset="nw312" tidref="i3579"Allows for a banner page to be printed at the front  of your print job." idxid="w6871"book="_idx" docset="nw312" tidref="i2484"Form Name" idxid="w6872"book="_idx" docset="nw312" tidref="i3579"Allows you to select a defined print form." idxid="w6873"book="_idx" docset="nw312" tidref="i579"Auto endcap" idxid="w6874"book="_idx" docset="nw312" tidref="i3579"Specifies that the captured printing jobs be closed " idxid="w6875"book="_idx" docset="nw312" tidref="i1448"Direct" idxid="w6876"book="_idx" docset="nw312" tidref="i3579"If there are no jobs resident, your print job will  bypass the print queue (Personal NetWare only)." idxid="w6877"book="_idx" docset="nw312" tidref="i2665"Hold" idxid="w6878"book="_idx" docset="nw312" tidref="i3579"Stops a print file from being sent to a queue.See the online help for more information about each option.If you are connecting to a NetWare v3.x network, book="print" docset="nw312"Print Server also describes each option in more detail. If you are connecting to a NetWare v4.0 network, book="print" docset="nw40"Print Services also describes each option in more detail.NetWare Connectionsidxid="w6879"book="_idx" docset="nw312" tidref="i1204"Use the "NetWare Connections" window to connect to Directory trees and network servers. Select the resource you want to connect to in the "Resources" list, then choose the "Login" button at the bottom of the window. For example, see IDREF="FM68369"Figure 6-6 for "NetWare Connections."LBL="6-6"ID="FM68369"NetWare ConnectionsFILE="c312b08a.pbm"When using the "NetWare Connections" window, remember:"NetWare Connections" can be used for connecting to Directory trees, directly to NetWare Server objects, or to bindery-based servers.The "Login" option does not run a login script for your workstation. Use the "Permanent" option in the "NetWare Drive Connections window" to set up your workstation drive mappings. If you want to run a login script, your initial login should be done at the command line with the LOGIN utility. See Chapter 5, IDREF="FM67133""Workstation Login" on page IDREF="FM67133"67 for details.If you are connected to a NetWare v4.0 network, log out of a Directory tree before logging in to another Directory tree.Viewing the "Resources" ListThe resources displayed in the "Resources" list within the "NetWare Connections" window depend on the type of network you are connected to. Your context within a Directory tree in NetWare v4.0 will also influence what is being displayed. The following are some of the possible resources to which you can log in:An OrganizationAn Organizational UnitA NetWare Server ObjectA bindery serverUse the NET.CFG file to set or change your starting context for NetWare v4.0 networks. See page IDREF="FM95233"60, IDREF="FM95233""Modifying Your NET.CFG for Logging In to NetWare v4.0" for details.Setting a New Passwordidxid="w6880"book="_idx" docset="nw312" tidref="i4980"You can modify your existing password by using the "Set Pass" option in the "NetWare Server Connection" window. Choosing the "Set Pass" button will display the following dialog displayed in IDREF="FM32172"Figure 6-7.LBL="6-7"ID="FM32172"NetWare Set PasswordFILE="c312b09a.pbm"Choose the "Help" button for procedures and information. NetWare Send Messageidxid="w6881"book="_idx" docset="nw312" tidref="i3869"Use the "NetWare Send Message" window to send a message to a user or group of users on the network. Select the resource you want to send a message to from the "Resources" list, type your message in the box, then choose the "Send" button at the bottom of the window. For example, see IDREF="FM49109"Figure 6-8 for "NetWare Send Message."LBL="6-8"ID="FM49109"NetWare Send MessageFILE="c312b07a.pbm"When using the "NetWare Send Message" window, remember that you must first log in to a Directory Services tree or server that contains the object for which you want to send a message.Viewing the "Resources" ListThe "Resources" list within the "NetWare Send Message" window contains users and groups.Use the show or hide features to control the displayed resources in the "Resources" list.NetWare SettingsUse the "NetWare Settings" window to modify display options, message reception and access to NetWare User Tools for Windows. Select the option you want to modify and choose "OK."For example, see IDREF="FM66361"Figure 6-9 for "NetWare Settings."LBL="6-9"ID="FM66361"NetWare SettingsFILE="c312b10a.pbm"When using the "NetWare Settings" window, remember:The settings you choose in the "NetWare Settings" window take effect each time you start Windows. These settings are retained in your NETWARE.INI, WIN.INI, and SYSTEM.INI files.NetWare User Tools for Windows will recognize the previous settings each time you start Windows.Using NetWare SettingsUse the "NetWare Settings" window to:Allow or block incoming messagesSet display optionsChange the hotkey value for NetWare User Tools for WindowsAllow for persistent connectionsIDREF="FM48622"Table 6-3 shows the setting you can modifyLBL="6-3" INLINE="F"ID="FM48622"Description of NetWare settingsWIDTH="108"NetWare Setting OptionWIDTH="300"FunctionWIDTH="108"idxid="w6882"book="_idx" docset="nw312" tidref="i3837"Messages ReceptionWIDTH="300""Broadcasts" allows you to block or receive messages sent to your  workstation by other network stations and servers.By default, this box is checked so that you receive broadcast messages.If you block broadcast messages, all messages sent to your station are  lost. You cannot retrieve them later."Network Warnings" alerts you of the following network problems:The NetWare VLM is not loaded.Your DOS Requester configuration is not set up correctly.Memory is insufficient to load network support.By default, this box is checked so you are notified of network problems. idxid="w6883"book="_idx" docset="nw312" tidref="i5248"Print Manager DisplayAllows you to configure the look and content of your Windows Print  Manager display. The following option settings are available:"Maximum jobs" allows you to set the number of print jobs that can  be stored in the Print Manager queue. Default: 50Maximum: 250Minimum: 1"Update seconds" allows you to select how often (in seconds) the Print  Manager updates the Print Manager queue. Default: 30 Maximum: 65 Minimum: 1idxid="w6884"book="_idx" docset="nw312" tidref="i5906"Resource Display"Bindery" displays available bindery servers in the "Resources" list."Personal" displays available Personal NetWare servers in the  "Resources" list."DS Object" displays available NetWare Directory Services objects  in the "Resources" list."DS Containers" displays available NetWare Directory Services  containers in the "Resources" list."Name Sort" displays resources sorted by their name."Type Sort" displays resources sorted by their type.idxid="w6885"book="_idx" docset="nw312" tidref="i2690"Enable HotkeySpecifies any hotkey value you want. The default hotkey is <F6>. The  hotkey value for NetWare User Tools for Windows takes priority over any  other system setting with the same value.idxid="w6886"book="_idx" docset="nw312" tidref="i5071"Persistent ConnectionsPrompts you to reconnect any network connection made in the  previous session of Windows.See the online help for more information about each option.Using the User-Defined Buttons "1" and "2"idxid="w6887"book="_idx" docset="nw312" tidref="i7155"The "1" and "2" buttons in the right side of the menu bar allow you to load additional programs within NetWare User Tools for Windows. This can be very useful for accessing the Windows File Manager and Print Manager applications. To define the User-Defined buttons, complete the following steps:ProcedureOpen the "User Defined Path" dialog.You can open the "User Defined Path" dialog in the following two ways:Choose the "1" or "2" button, if no previous path is defined.Press<Alt><1> or <Alt><2>.The "User Defined Path" dialog appears.Type the path and program filename in the "Command Line" field. For example, to define the Windows File Manager to load from NetWare User Tools, type  C:\windows\winfile.exeChoose "OK."An icon for the particular application appears in the button bar. Changing the User-Defined Pathidxid="w6888"book="_idx" docset="nw312" tidref="i7153"Once a path is set, you will need to use the quick key to access the "User Defined Path" dialog. Press <Alt><1> or <Alt><2>.ID="FM94213"Accessing and Changing Directory and File Attributesidxid="w6889"book="_idx" docset="nw312" tidref="i556"Follow the steps below to access and change file and directory attributes:ProcedureOpen the Windows File Manager.Select the file for which you want to set attributes.This function applies only for files on network drives.Choose the "Properties" option from the "File" menu.Choose "NetWare" in the "Properties" window.Select the appropriate check box to enable or disable an attribute.IDREF="FM63048"Figure 6-10 show the "Properties" window.LBL="6-10"ID="FM63048"File and directory propertiesFILE="c312b06a.pbm"When using the "Properties" option, remember that you can only set properties for network files and directories. Properties for directories and files on local drives are set within the Windows File Manager.Setting File and Directory Attributesidxid="w6890"book="_idx" docset="nw312" tidref="i556"IDREF="FM79082"Table 6-4 lists the settings you can modify.LBL="6-4" INLINE="F"ID="FM79082"Description of properties settingsWIDTH="84"Properties setting  optionWIDTH="216"FunctionWIDTH="84"idxid="w6891"book="_idx" docset="nw312" tidref="i6326"Sharable idxid="w6892"book="_idx" docset="nw312" tidref="i2024"WIDTH="216"Allows users simultaneous access to a fileidxid="w6893"book="_idx" docset="nw312" tidref="i6874"Transactional idxid="w6894"book="_idx" docset="nw312" tidref="i2024"Indicates that a file is protected by the  Transactional Tracking System (tm)idxid="w6895"book="_idx" docset="nw312" tidref="i5703"Purge idxid="w6896"book="_idx" docset="nw312" tidref="i2024"Notifies NetWare to purge a file when it is deletedidxid="w6897"book="_idx" docset="nw312" tidref="i5859"Rename Inhibit idxid="w6898"book="_idx" docset="nw312" tidref="i2024"Prevents users from renaming a fileidxid="w6899"book="_idx" docset="nw312" tidref="i1350"Delete Inhibit idxid="w6900"book="_idx" docset="nw312" tidref="i2024"Prevents users from deleting a fileidxid="w6901"book="_idx" docset="nw312" tidref="i1250"Copy Inhibit idxid="w6902"book="_idx" docset="nw312" tidref="i2024"Prevents users from copying a file (Macintosh®  workstations only)Choose the "Help" button for more information about these attributes. Exiting NetWare User Tools for WindowsTo exit the NetWare User Tools for Windows, complete one of the following:Choose the "Exit" button from the menu bar.Press <Alt><X> or <Alt><F4>.Choose the system menu box (the box in the upper left corner of NetWare User Tools for Windows). A menu appears. Choose "Close."Where to Go from HereWith a basic understanding of NetWare User Tools for Windows, you are ready to set up network printing for your workstation platform. See IDREF="FM17351""Setting Up Printing for Windows" on page IDREF="FM17351"117.ID="FM56032"Starting idxid="w6903"book="_idx" docset="nw312" tidref="i4429"NetWare User Tools for OS/2Prerequisitesidxid="w6904"book="_idx" docset="nw312" tidref="i4431"Before you can start the NetWare User Tools for OS/2, your workstation requires the following:A physical connection to the network.OS/2 v2.x loaded and running.The NetWare Requester files loaded and running. (The OS/2 Requester files are loaded within the OS/2 CONFIG.SYS file during boot up.)ProcedureChoose the Novell icon on your OS/2 desktop window.If the Novell icon is not displayed, press your right mouse button to show the system menu, then choose "Arrange." If the Novell - Icon folder is still not on your desktop, open an OS/2 full screen or OS/2 window, change to the directory containing Requester files (usually C:\NETWARE), and type NWTOOLS. This will load NetWare User Tools for OS/2. From the Novell - Icon View on your desktop, choose the "NetWare Tools" icon.LBL="6-11"Opening NetWare User Tools for OS/2FILE="c312b41a.pbm"For easier access to the network, you may want to keep the NetWare User Tools Window minimized on your desktop whenever your computer is on. ID="FM46779"Using the NetWare User Tools for OS/2idxid="w6905"book="_idx" docset="nw312" tidref="i4431"The NetWare User Tools for OS/2 provide a graphical way of accessing network resources, such as volumes, directories, printers, and users. The NetWare User Tools also allow you a way of configuring your workstation and customizing NetWare User Tools display settings. NetWare User Tools allow you to do the following:Manage drive mappingsManage printer connections and setupManage Directory tree and server connectionsDisplay network usersSend messagesUsing the Menu Baridxid="w6906"book="_idx" docset="nw312" tidref="i4431"The menu bar shows the options you can use. To complete a task, choose the menu option that corresponds with the task you are performing.Each time you select a menu option, the corresponding menu box will appear. If an option is grayed, that option is not active or available. IDREF="FM65814"Table 6-12 shows the "Network" menu option.LBL="6-12"ID="FM65814"Network menu optionsFILE="c312b33a.pbm"Use the "Network" option to modify, save, and reload your workstation network settings. A dialog appears for each option.Choosing the "New Settings" option disconnects all current server connections. Make sure that all open files and applications are closed.For more information about this Tool, choose "Help."Tools MenuUse the" Tools" menu to use the NetWare User Tools. Choosing the "Tools" option causes a menu box to appear with the following options:Disk drivesPrinter portsServersDirectoryUser listsPrint queuesA window appears for each option.For easier access, leave open all of the tools you will commonly use. The "Window" option in the menu bar allows you to arrange the "Tools" window display. You can set the display for cascade or tile.The menu bar will refresh itself according to the "Tools" window you have activated currently.For more information about these tools, choose "Help."Window MenuUse the "Window" menu to arrange the windows on the screen and switch between views.Help MenuUse the "Help" menu to access the online help. (You can also press the<F1> key for help.) Use the "Contents" option to see a list of commands, keyboard instructions, and a comprehensive task list.Drives Menuidxid="w6907"book="_idx" docset="nw312" tidref="i1723"Use the "Drives" menu to map network resources in the Directory tree and file system to your workstation drives. Choose the drive letter for which you want to map a drive.LBL="6-13"ID="FM26366"Drives menuFILE="c312b17a.pbm"A "Drives" window appears as seen in IDREF="FM26366"Figure 6-13. Select the resource you want to connect to in the "Volume" and "Directory" lists, then choose the "Map" button at the bottom of the window. Keyboard entry is done within the "Path" field.IDREF="FM38675"Figure 6-14 shows the "Drives" dialog.LBL="6-14"ID="FM38675"Map windowFILE="c312b32a.pbm"When using the " idxid="w6908"book="_idx" docset="nw312" tidref="i3739"Map" window, remember:You must log in to a server or Directory tree or that contains the object for which you want to connect before using the "Drives" menu.NWTOOLS will recognize all drive mappings that are made at the command line.For more information about this window, choose "Help."Viewing the "Volume" and "Directory" ListsThe "Volume" and "Directory" lists within the "Map" window contain the following:VolumesDirectoriesThe volumes and directories are listed in a hierarchical structure. Choose the "Volume" icon to display subdirectories. If the volume or directory you want to map does not appear in the "Volume" or "Directory" list, check to see if you are attached to the server containing this resource. Choose "Server" from the "Tools" option to see connected servers.NetWare User Tools "Printer" Menuidxid="w6909"book="_idx" docset="nw312" tidref="i5537"Use the "Printers" menu to capture network print queues to your workstation printing ports. Choose the printer port you want to capture.IDREF="FM47107"Figure 6-15 shows the "Printer" menu.LBL="6-15"ID="FM47107"Printers menuFILE="c312b14a.pbm"The "Capture" window appears. Select the resource you want to capture in the "Printer/Queue" list, then choose "Capture" at the bottom of the window. Keyboard entry is done within the "Queue" field.IDREF="FM68861"Figure 6-16 shows the "Capture" dialog.LBL="6-16"ID="FM68861"Capture windowFILE="c312b27a.pbm"When using the "Capture" window, remember:You must first log in to a server or Directory tree that contains the resource you want to capture before using the "Capture" window.NWTOOLS will recognize all print queue captures made at the command line. For more information about this window, choose "Help."Viewing the Printer/Queue ListThe "Printer/Queue" list within the "Capture" window contains the following:Printer objectsPrint queue objectsYou must highlight the port to which you want to capture a print queue before choosing the "Capture" button.You must highlight the port and print queue name you want to view before choosing the "View Queue" option.If the print queue you want to capture does not appear in the "Queue" list, check to see if you are attached to the server containing this resource. Choose "Server" under the "Tools" option to see connected servers.Setting Printer Optionsidxid="w6910"book="_idx" docset="nw312" tidref="i5537"Use the "Printer Options" field to assign the following settings:LBL="6-5" INLINE="F"Description of printer optionsWIDTH="84"Printer optionWIDTH="216"FunctionWIDTH="84"idxid="w6911"book="_idx" docset="nw312" tidref="i4671"NotifyWIDTH="216"Confirms print job completionidxid="w6912"book="_idx" docset="nw312" tidref="i2489"FormfeedPlaces a page break between print jobsidxid="w6913"book="_idx" docset="nw312" tidref="i1247"CopiesSpecifies the number of copies to printidxid="w6914"book="_idx" docset="nw312" tidref="i6686"Tabs SizeSpecifies the number of characters in a tab stopidxid="w6915"book="_idx" docset="nw312" tidref="i2018"File ContentsSpecifies the type of print file being printedidxid="w6916"book="_idx" docset="nw312" tidref="i5150"Print BannerAllows for a banner page to be printed at the front  of your print jobidxid="w6917"book="_idx" docset="nw312" tidref="i2486"FormAllows you to select a defined print formSee the online help for more information about each option. If you are connecting to a NetWare v2.x or v3.x network, book="print" docset="nw312"Print Server describes each option in more detail. If you are connecting to a NetWare v4.0 network, book="print" docset="nw40"Print Services describes each option in more detail.Tree Option (NetWare v4.0 only)This tool is only used with NetWare v4.0 networks. For NetWare v2.x and v3.x networks, use the "Servers" option to attach to network servers.idxid="w6918"book="_idx" docset="nw312" tidref="i1204"Use the "Tree" option to do the following:Display resourcesChange Directory treesChange context idxid="w6919"book="_idx" docset="nw312" tidref="i1230"with the networkLog in to the networkidxid="w6920"book="_idx" docset="nw312" tidref="i4980"Change your passwordChoose the "Tree" option from the main menu bar. A menu box will appear. IDREF="FM72047"Figure 6-17 shows the "Tree" menu:LBL="6-17"ID="FM72047"Tree menuFILE="c312b11a.pbm"Choose the "Login" option from the menu box. The "Login to Directory Tree" dialog appears. IDREF="FM35116"Figure 6-18 shows the Login to directory Tree" dialog.LBL="6-18"ID="FM35116"Login to Directory Tree dialogFILE="c312b26a.pbm"When using the "Tree" option, it is important that you remember that:The "Login" option does not run a login script for your workstation. Use the "Save Settings" option in the "Network" menu box to maintain your connections. If you want to run a login script, your initial login should be done at the command line with the LOGIN utility. See IDREF="FM67133""Workstation Login" on page IDREF="FM67133"67.You must log out of a Directory tree before logging in to another Directory tree.For more information about this dialog, choose "Help."Servers Optionidxid="w6921"book="_idx" docset="nw312" tidref="i1204"Use the "Servers" option to do the following:Display Directory Services NetWare Server objectsDisplay bindery-based serversAttach to bindery-based serversChange your passwordChoose the "Servers" option from the menu bar. The "Servers" menu appears.IDREF="FM61032"Figure 6-19 shows the "Servers" menu.LBL="6-19"ID="FM61032"Servers menuFILE="c312b16a.pbm"Choose the "Attach" option from the menu. The "Attach To Server" dialog appears. IDREF="FM45515"Figure 6-20 shows the "Attach To Server" dialog.LBL="6-20"ID="FM45515"Attach To Server dialogFILE="c312b31a.pbm"When using the "Servers" option, it is important that you remember that:This tool is used with NetWare v2.x, v3.x and v4.0 networks to attach to network servers.The "Attach" option does not run a login script for your workstation. Use the "Save Settings" option in the "Network" menu box to maintain your connections. If you want to run a login script, your initial login should be done at the command line with the LOGIN utility. For more information about this option, choose "Help."Users OptionUse the "Users" option to display network users or groups and send a message to them. Select the resource you want to send a message to from the "Users" list. IDREF="FM24574"Figure 6-21 shows the "Users" menu.LBL="6-21"ID="FM24574"Users menuFILE="c312b19a.pbm"You must be logged in to a server or Directory tree that contains the object for which you want to send a message. Then, c idxid="w6922"book="_idx" docset="nw312" tidref="i3869"hoose the user or group you to whom you want to send a message. The "Send a Message" dialog appears. Type your message in the "Messages" field, then choose "Send." IDREF="FM85721"Figure 6-22 shows the "Send A Message" dialog.LBL="6-22"ID="FM85721"Send A Message dialogFILE="c312b12a.pbm"You must highlight the users to which you want to send a message before choosing the "Send Message" option.If the user or group you want to send a messages to does not appear in the "Users" list, check to see if you are attached to the server containing this user or group. Choose "Server" under the "Tools" option to see connected servers.For more information about this tool, choose "Help."Exiting NetWare User Tools for OS/2To exit NetWare User Tools for OS/2, complete one of the following:Choose the "Exit" option within the "Network" menu.Press<Alt><F4>.Choose the system menu (the box in the upper left corner). A menu box appears. Choose "Close."LBL="6-23"Exit NWTools dialogFILE="c312b29a.pbm"Where to Go from HereWith a basic understanding of NetWare User Tools for OS/2, you are ready to set up network printing for your workstation platform. See IDREF="FM91348""Setting Up Printing for OS/2 Workstations" on page IDREF="FM91348"121.LBL="7"Setting Up Workstation PrintingOverviewThis chapter explains how to set up network printing on your NetWare workstation.WIDTH="264"TopicWIDTH="48"PageWIDTH="264"IDREF="FM46147""Setting Up Printing for DOS Workstations"WIDTH="48"IDREF="FM46147"116IDREF="FM17351""Setting Up Printing for Windows"IDREF="FM17351"117IDREF="FM91348""Setting Up Printing for OS/2 Workstations"IDREF="FM91348"121IntroductionNetWare uses a print queue, a print server, and a printer driver to allow several network workstations to print to a network printer. The print server takes print jobs from the print queue and sends them to the printer.PrerequisitesComplete the procedures in Chapter 5 to ensure that you are connected to the network and have access to network printing resourcesInstall NetWare User Tools for DOS, Windows, and OS/2.Go to the appropriate section for the platform you are using.WIDTH="132"If you are usingWIDTH="180"Go toWIDTH="132"DOSWIDTH="180"IDREF="FM46147""Setting Up Printing for DOS  Workstations" on page IDREF="FM46147"116WindowsIDREF="FM17351""Setting Up Printing for Windows" on  page IDREF="FM17351"117OS/2IDREF="FM91348""Setting Up Printing for OS/2  Workstations" on page IDREF="FM91348"121ID="FM46147"Setting Up Printing for DOS Workstationsidxid="w6923"book="_idx" docset="nw312" tidref="i5537"Most applications send print jobs directly to the print queue. If you use an application that prints only to local ports, use NETUSER to redirect printing to a network print queue.Setting up printing in DOS is done within NETUSER. The following sections explain the procedures.ProcedureChange to the SYS:PUBLIC directory.Load NetWare User Tools for DOS. For example, if SYS:PUBLIC is mapped to drive Z:, type  Z:>NETUSER <Enter>The NETUSER menu appears. Press <Enter> to move to the next option. Use the <Esc> key to back out of windows within NETUSER. User the arrow keys to move between options. Choose the "Printing" option.The "Available Ports" window appears.Choose a port from the list.The "Available Options" window appears.Choose the "Change Printers" option.The "Printer\Print Queues" window appears. If the print queue you want to capture is not listed, make sure that you chose the correct server containing this print queue.Choose a print queue name from the list.If you don't know the queue name, use the arrow keys to see the list of available print queues.Press <Enter> to capture the print queue to the port you specified.Your screen will return to the previous window. Your current workstation information in the top portion of your screen will be updated.ID="FM17351"Setting Up Printing for Windowsidxid="w6924"book="_idx" docset="nw312" tidref="i5537"Setting up workstation printing in Windows requires you to first set up the Print Manager in Windows, then access the "NetWare Printer Connections" option in NetWare User Tools for Windows.ProcedureActivate the Print Manager.In the Windows Control Panel, choose the Printer icon.The "Printers" dialog appears.Mark the "Use Print Manager" box.The Print Manger is activated.LBL="7-1"ID="FM32123"Printers dialogFILE="c312b44a.pbm"Select a printer driver from the "Installed Printers" list.If the printer driver for your network printer is not listed, choose "Add" to display the list of available printer drivers.Select a printer driver from the "List of Printers" for your network printer.Choose "Install."Windows prompts you to insert a Windows diskette and then copies the selected printer driver to the Windows directory.Assign printing ports to network print queues.Choose "Connect."The "Connect" dialog appears.LBL="7-2"ID="FM57684"Connect dialogFILE="c312b45a.pbm"ID="FM26874"Select a port from the "Ports" list.If you have a local printer, it is recommended that you leave it assigned to the port to which it is already connected.Choose "Network."The "NetWare Printer Connections" window appears.LBL="7-3"ID="FM64239"NetWare Printer ConnectionsFILE="c312b05a.pbm"Choose the same port from the "Ports" list that you selected in "Step 3b" on page IDREF="FM26874"119.Choose a print queue name from the "Resources" list.If you don't know the queue name, use "Browse" to see available print queues.Choose "Capture."Exit the "NetWare Printer Connections" window.Your screen will return to the "Connect" dialog you were in Step 3.Choose "OK."Your screen will return to the "Printers" dialog.Choose "Close" to exit the "Printer" dialog.This will return you to the "Control Panel" window.Close the "Control Panel" window.Choose the "Print Manager" icon.The "Print Manager" window appears.Select the "Options" option.The "Options" menu appears.Choose "Network Settings."The "Network Options" dialog appears.Enable the "Print Net Jobs Direct" option.With this option marked, Windows bypasses the Print Manager and prints directly to the network print queue, giving you optimal printing performance.LBL="7-4"ID="FM66845"Network Options dialogFILE="c312b46a.pbm"ID="FM91348"Setting Up Printing for OS/2 Workstationsidxid="w6925"book="_idx" docset="nw312" tidref="i5537"Setting up workstation printing in OS/2 is done within NetWare User Tools for OS/2.ProcedureChoose the Novell Icon from your desktop.Choose the "NetWare Tools" icon from the Novell - Icon View window on your desktop.Choose the "Tools" menu in the upper menu bar.Choose "Printer Ports."A "Printers" window will appear and a "Printers" option will appear in the menu bar.LBL="7-5"ID="FM80488"NetWare User Tools Printer OptionFILE="c312b14a.pbm"Choose a port.You can also select a port and choose "Printers" from the upper menu bar in the NetWare User Tools window. Then choose "Capture."A "Capture" window appears.LBL="7-6"ID="FM70552"Capture dialogFILE="c312b27a.pbm"Highlight a print queue name in the "Printers/Queue" list.Choose "Capture."If the print queue you want to capture does not appear in the "Printers/Queue" list, check to see if you are attached to the server containing this resource. Choose "Server" from the "Tools" option to see connected servers.Use the "Save Settings" option in the "Network" menu to maintain your connections.For more information about this tool, choose "Help."Where to Go from HereWith printing set up on your workstation, you are now ready to use your workstation on the network. See book="ws_dos" docset="nw40"Workstation for DOS and Windows and book="ws_os2" docset="nw40"Workstation for OS/2 for additional information on setting up and configuring your workstation.LBL="A"ID="FM11451"Using the WSUPGRD UtilityOverviewThis appendix contains information about using the WSUPGRD utility for upgrading dedicated IPX drivers to ODI drivers. The following topics are included.WIDTH="264"TopicWIDTH="48"PageWIDTH="264"IDREF="FM12193""Setting Up the Public Directory for WSUPGRD"WIDTH="48"IDREF="FM12193"126IDREF="FM84650""Using the WSUPGRD /I Option"IDREF="FM84650"127IDREF="FM95238""Upgrading Your Network Board Driver from the Command  Line"IDREF="FM95238"128IDREF="FM14923""Upgrading Network Board Drivers from a Login Script"IDREF="FM14923"128Introductionidxid="w6926"book="_idx" docset="nw312" tidref="i7561"The WSUPGRD utility upgrades the IPX network board driver on your workstation to the corresponding ODI driver. If your workstation is running a previous version of NetWare, your workstation will be running on an IPX driver or a corresponding ODI driver.This utility is recommended for large installations with similar hardware and software configurations. Networks with a variety of network boards and driver types will need to manually upgrade each workstation. It cannot be used for upgrading RPL workstations.The workstation installation program will provide you with a Novell ODI driver for your network board. The workstation installation program cannot, however, detect board settings from an IPX driver. If you are running an IPX driver on your workstation, you should upgrade your network board driver to ODI before using the workstation installation program.The workstation installation program will automatically detect if an ODI driver is used on your workstation and set the driver settings for you. This will make upgrading each network workstation from a previous version of NetWare with the installation program very automatic.ID="FM12193"Setting Up the Public Directory for WSUPGRDidxid="w6927"book="_idx" docset="nw312" tidref="i7561"A typical upgrade requires the following files in SYS:PUBLIC:WSUPGRD.EXELSL.COM IPXODI.COMAppropriate ODI drivers (e.g. NE2000.COM)Auxiliary files:DRVRXLAT.TXTdriver_name.LDCAuxiliary FilesThe auxiliary files are optional but can make upgrading a complex network easier if they exist.idxid="w6928"book="_idx" docset="nw312" tidref="i2300"DRVRXLAT.TXTThe idxid="w6929"book="_idx" docset="nw312" tidref="i1749"DRVRXLAT.TXT file is in SYS:PUBLIC. This file contains one line for each ODI driver type in use on the network. Each line has the hexadecimal hardware identification of the IPX driver, the path to the files, and the name of the corresponding ODI driver.If no DRVRXLAT.TXT file exists or if no line with the correct hardware identification is found in the DRVRXLAT.TXT file, then WSUPGRD will look in the PUBLIC directory for an ODI driver with the same name as the existing IPX driver. If it fails to find one, no upgrade will be performed.driver_name.LDCThe .LDC files are in the same directory as the ODI drivers of the same name (driver_name.COM). These files contain lines that are to be copied into the NET.CFG file in addition to any lines the utility creates normally.ID="FM84650"Using the WSUPGRD /I Optionidxid="w6930"book="_idx" docset="nw312" tidref="i7561"The /I option in WSUPGRD lets you print out the hardware identification for your IPX network board driver.The DRVRXLAT.TXT file contains a master configuration table. Check the master configuration table to make sure that your IPX driver identification matches a registered driver. The table lists the driver name, the company name, and the hardware identification. If the listing in the table does not match your IPX driver, you should not use this utility. If your IPX driver is not registered, the identification that your IPX driver uses may be registered for a different type of network board. You cannot use the WSUPGRD /I option with any other WSUPGRD options.ID="FM95238"Upgrading Your idxid="w6931"book="_idx" docset="nw312" tidref="i7561"Network Board Driver from the Command LineProcedureMap the next network drive to SYS:PUBLIC by typing:  MAP N SYS:PUBLIC <Enter>Change to the drive and directory from which your workstation boots.For example, if your workstation boots from drive C:, type:  C: <Enter>To start WSUPGRD and specify your network board, type  WSUPGRD odi_driver<Enter>For example, type  WSUPGRD NE2000 <Enter>ID="FM14923"Upgrading Network Board Drivers from a idxid="w6932"book="_idx" docset="nw312" tidref="i3442"Login Scriptidxid="w6933"book="_idx" docset="nw312" tidref="i7561"You can insert the WSUPGRD command into a system login script for upgrading network board drivers. Use SYSCON for NetWare v2.x and v3.x workstations. Use the graphical NetWare Administrator or the NETADMIN text utility for NetWare v4.0 workstations. All three procedures are documented in this section. If this utility is loaded from a system login script, all of the workstations that log in to this server must have drivers with the same name. If this is not the case, users will have to run WSUPGRD from the DOS command line supplying the path to and the name of the IPX driver on their respective workstations.ID="FM13592"Inserting WSUPGRD in a Login Script Using SYSCONThis tool is only used with NetWare v2.x and v3.x networks only. For NetWare v4.0 networks, use the NWADMIN or NETADMIN utility to edit your login script. See IDREF="FM52788""Inserting WSUPGRD in a Login Script Using the NetWare Administrator" on page IDREF="FM52788"130 or IDREF="FM39201""Inserting WSUPGRD in a Login Script Using NETADMIN" on page IDREF="FM39201"132.PrerequisitesA workstation logged into the network, running DOS v3.x or later. For more information on the LOGIN syntax and options, see "book="utilref" docset="nw312"LOGIN" in Utilities Reference.You must have rights to modify a system login scriptProcedureLog in to a server as SUPERVISOR.For example, type:  LOGIN SUPERVISOR <Enter>Enter a password (if prompted).At the workstation command line, type  SYSCON <Enter>Enter SYSCON and choose "Supervisor Options" from the "Available Topics" menu.Choose "System Login Script." If a system login script already exists, it appears; otherwise, the screen is blank.Map a drive to SYS:PUBLIC if a mapping does not exist. Type  MAP drive:=SYS:PUBLICInsert the WSUPGRD command after the drive mapping in the login script. Type  WSUPGRD odi_driver [option]For example, type  WSUPGRD NE2000 /NThis command upgrades your IPX driver with an NE2000.COM ODI driver without deleting your IPX driver.Update any batch files that are run by users at login.To exit the system login script, press <Esc>. Confirm changes you made in the login script.ID="FM52788"Inserting WSUPGRD in a Login Script Using the idxid="w6934"book="_idx" docset="nw312" tidref="i7561"NetWare AdministratorThis tool is only used with NetWare v4.0 networks. For NetWare v2.x and v3.x networks, use the SYSCON utility to edit your login script. See IDREF="FM13592""Inserting WSUPGRD in a Login Script Using SYSCON" on page IDREF="FM13592"129.PrerequisitesA workstation logged into the network, running Windows v3.1 or OS/2 v2.x. For more information on the LOGIN syntax and options, see "LOGIN" in Chapter 3, "book="utilref" docset="nw40"Using Text Workstation Utilities" of Utilities Reference.You must have rights to modify a system login scriptProcedureLog in to the network as ADMIN.The login command must include your context. Depending on the Directory tree structure you set up for the server during installation, use the name typing sequence of Common Name, Organizational Unit, Organization, and Country.For example, if you installed this server into an Organization called ABC_INC, with no Organizational Unit or Country defined in the Directory tree, type:  LOGIN .CN=ADMIN.O=ABC_INC <Enter>Enter a password (if prompted).Start Windows.Choose the "NetWare Administrator" icon.Select the object whose login script you want to edit.A login script can be a property of a container, Profile, or User object.You may have to browse through the Directory tree to get to the object you want. For information about moving around in the Browser and selecting objects, choose "Help."Choose "Object" from the NetWare Administrator menu bar.Choose "Details" from the "Object" menu.Choose "Login Script" from the pages on the right side of the window.To edit the login script, click inside the "Login Script" input box.Map a drive to SYS:PUBLIC. Type  MAPdrive:=SYS:PUBLICInsert the WSUPGRD command after the drive mapping in the login script. Type  WSUPGRD odi_driver [option]For example, type  WSUPGRD NE2000 /NThis command upgrades your IPX driver with an NE2000.COM ODI driver without deleting your IPX driver.Choose "OK." Update any batch files that are run by users at login.ID="FM39201"Inserting WSUPGRD in a Login Script Using idxid="w6935"book="_idx" docset="nw312" tidref="i7561"NETADMINThis tool is only used with NetWare v4.0 networks. For NetWare v2.x and v3.x networks, use the SYSCON utility to edit your login script. See IDREF="FM13592""Inserting WSUPGRD in a Login Script Using SYSCON" on page IDREF="FM13592"129.PrerequisitesA workstation logged into the network, running DOS v3.x or later. For more information on the LOGIN syntax and options, see "book="utilref" docset="nw40"LOGIN" in Chapter 3 of Utilities Reference.You must have rights to modify a system login scriptProcedureLog in to the network as ADMIN.The login command must include your context. Depending on the Directory tree structure you set up for the server during installation, use the name typing sequence of Common Name, Organizational Unit, Organization, and Country.For example, if you installed this server into an Organization called ABC_INC, with no Organizational Unit or Country defined in the Directory tree, type:  LOGIN .CN=ADMIN.O=ABC_INC <Enter>Enter a password if prompted.At the workstation command line, type  NETADMIN <Enter>Choose "Manage Objects" from the "Netadmin Options" menu.A login script can be a property of a container, Profile, or User object.Select the object whose login script you want to edit by completing the following steps.If the object you want appears on the list, select it and press<F10>.If the object is not on the list, browse the Directory tree by selecting objects and pressing <Enter> until you see the object you want. Select it and press <F10>.Choose "View or edit object properties."Choose "Login Script." Enter the login script commands and information in the login script text box.Map a drive to SYS:PUBLIC. Type  MAP drive:=SYS:PUBLICInsert the WSUPGRD command after the drive mapping in the login script. Type  WSUPGRD odi_driver [option]For example, type  WSUPGRD NE2000 /NThis command upgrades your IPX driver with an NE2000.COM ODI driver without deleting your IPX driver.Update any batch files that are run by users at login.Press <F10> to save the script.Update any batch files that are run by users at login.Additional InformationIf you are using NetWare v2.x and 3.x, see the following references for more information about WSUPGRD and related topics:WIDTH="132"For more information aboutWIDTH="180"Refer toWIDTH="132"Login scriptsWIDTH="180""book="utilref" docset="nw312"SYSCON" of Utilities ReferenceMapping network drives"book="utilref" docset="nw312"MAP" in Utilities ReferenceIf you are using NetWare v4.0, see the following references for more information about WSUPGRD and related topics:WIDTH="132"For more information aboutWIDTH="180"Refer toWIDTH="132"Login scriptsWIDTH="180"Chapter 3, "book="supernt" docset="nw40"Creating Login Scripts and  Menus" in Supervising the NetworkMapping network drivesChapter 3, "book="utilref" docset="nw40"Using Text Workstation  Utilities" of Utilities ReferenceUsing the WSUPGRD utilityChapter 3, "book="utilref" docset="nw40"Using Text Workstation  Utilities" of Utilities ReferenceLBL="B"Using the WSUPDATE UtilityOverviewThis appendix contains information about using the WSUPDATE utility for updating workstation files automatically. The following topics are included.WIDTH="264"TopicWIDTH="48"PageWIDTH="264"IDREF="FM65247""Using WSUPDATE"WIDTH="48"IDREF="FM65247"136IDREF="FM67987""Updating Files on a Workstation from the Command Line"IDREF="FM67987"136IDREF="FM13592""Inserting WSUPDATE in a Login Script Using SYSCON"IDREF="FM13592"137IDREF="FM79564""Inserting WSUPDATE in a Login Script Using the NetWare  Administrator"IDREF="FM79564"138IDREF="FM91141""Inserting WSUPDATE in a Login Script Using NETADMIN"IDREF="FM91141"140IntroductionThe WSUPDATE utility allows you to copy updates of workstation files automatically. Use WSUPDATE to:Copy new revisions of filesReinstall NetWare workstation filesCopy updates of your own filesThis utility is not recommended for first-time installation of NetWare v4.0 workstation files. WSUPDATE can only update files that exist already on the workstation. Use the workstation installation programs for first-time Netware v4.0 installations. WSUPDATE cannot be used for updating RPL workstations.ID="FM65247"Using WSUPDATEWSUPDATE allows you to copy updates of workstation files automatically.Prerequisitesidxid="w6936"book="_idx" docset="nw312" tidref="i7552"Before you can start WSUPDATE, make sure that:The files you are copying to the workstation reside in the same directory as the WSUPDATE utilityIf you are using WSUPDATE in a login script, each workstation needs to have a search drive mapped to SYS:PUBLIC.ID="FM67987"Updating Files on a Workstation from the idxid="w6937"book="_idx" docset="nw312" tidref="i7552"Command LineProcedureMap the next network drive to SYS:PUBLIC by typing:  MAP N SYS:PUBLIC <Enter>Change to the network drive that is mapped to the PUBLIC subdirectory. For example, if you mapped network drive G:, type  G: <Enter>Start WSUPDATE and specify the file and path you want updated. For example, type  WSUPDATE /F=C:\NE2000.COM <Enter>(The /F option lets you specify the file location.)Updating Workstation Files from a idxid="w6938"book="_idx" docset="nw312" tidref="i3442"Login Scriptidxid="w6939"book="_idx" docset="nw312" tidref="i7561"You can insert the WSUPDATE command into a system login script for upgrading workstation files. Use SYSCON for NetWare v2.x and v3.x workstations. Use the graphical NetWare Administrator or the NETADMIN text utility for NetWare v4.0 workstations. All three procedures are documented in this section. ID="FM13592"Inserting WSUPDATE in a Login Script Using SYSCONThis tool is only used with NetWare v2.x and v3.x networks. For NetWare v4.0 networks, use the NWADMIN or NETADMIN utility to edit your login script. See IDREF="FM79564""Inserting WSUPDATE in a Login Script Using the NetWare Administrator" on page IDREF="FM79564"138 or IDREF="FM91141""Inserting WSUPDATE in a Login Script Using NETADMIN" on page IDREF="FM91141"140.PrerequisitesA workstation logged into the network, running DOS v3.x or later. For more information on the LOGIN syntax and options, see "book="utilref" docset="nw312"LOGIN" in Utilities Reference.You must have rights to modify a system login scriptProcedureLog in to a server as SUPERVISOR.For example, type:  LOGIN SUPERVISOR <Enter>Enter a password (if prompted).At the workstation command line, type  SYSCON <Enter>Enter SYSCON and choose "Supervisor Options" from the "Available Topics" menu.Choose "System Login Script." If a system login script already exists, it appears; otherwise, the screen is blank.In the login script, map a drive to the file on the network you want copied to the workstation.For example, if you wanted to copy the "NE2000.COM" file from the \DRIVERS directory, add a drive mapping similar to the following:  MAP J:=VOL2:DRIVERS\Insert the WSUPDATE command after the drive mapping in the login script.For example, if you mapped drive J: as shown in Step 7, add the following command after the drive mapping:  #WSUPDATE J: NE2000.COMThe above command searches all local drives of the workstation and replaces NE2000.COM with the newer version on drive J:.It renames any old NE2000.COM files on the local drives to NE2000.OLD.To exit the system login script, press <Esc>. Confirm changes you made in the login script.ID="FM79564"Inserting WSUPDATE in a idxid="w6940"book="_idx" docset="nw312" tidref="i3442"Login Script Using the idxid="w6941"book="_idx" docset="nw312" tidref="i7552"NetWare AdministratorThis tool is only used with NetWare v4.0 networks. For NetWare v2.x and v3.x networks, use the SYSCON utility to edit your login script. See IDREF="FM13592""Inserting WSUPDATE in a Login Script Using SYSCON" on page IDREF="FM13592"137.ProcedureSelect the object whose login script you want to edit.A login script can be a property of a container, Profile, or User objects.You may have to browse through the Directory tree to get to the object you want. For information about moving around in the Browser and selecting objects, choose "Help" from the menu.Choose "Object" from the NetWare Administrator menu bar.Choose "Details" from the "Object" menu.Choose the "Login Script" page button.To edit the login script, click inside the "Login Script" input box.In the login script, map a drive to the file on the network you want copied to the workstation.For example, if you want to copy the "NE2000.COM" file from the \DRIVERS directory, add a drive mapping similar to the following:  MAP J:=VOL2:DRIVERS\Insert the WSUPDATE command after the drive mapping in the login script.For example, if you mapped drive J: as shown in Step 6, add the following command after the drive mapping:  #WSUPDATE J: NE2000.COMThe above command searches all local drives of the workstation and replaces NE2000.COM with the newer version on drive J:.It renames any old NE2000.COM files on the local drives to NE2000.OLD.Choose "OK."ID="FM91141"Inserting WSUPDATE in a Login Script Using idxid="w6942"book="_idx" docset="nw312" tidref="i7552"NETADMINThis tool is only used with NetWare v4.0 networks. For NetWare v2.x and v3.x networks, use the SYSCON utility to edit your login script. See IDREF="FM13592""Inserting WSUPDATE in a Login Script Using SYSCON" on page IDREF="FM13592"137.ProcedureAt the workstation command line, type  NETADMIN <Enter>Choose "Manage Objects" from the "Options" menu.A login script can be a property of a container, Profile, or User object.Select the object whose login script you want to edit by completing the following steps.If the object you want appears on the list, select it and press <F10>.If the object is not on the list, browse the Directory tree by selecting objects and pressing <Enter> until you see the object you want. Select it and press <F10>.Choose "View or edit object properties."Choose "Login Script." Enter the login script commands and information in the login script text box. In the login script, map a drive to the file on the network you want copied to the workstation.For example, if you want to copy the "NE2000.COM" file from the \DRIVERS directory, add a drive mapping similar to the following:  MAP J:=VOL2:DRIVERS\Insert the WSUPDATE command after the drive mapping in the login script.For example, if you mapped drive J: as shown in Step 7, add the following command after the drive mapping:  #WSUPDATE J: NE2000.COMThe above command searches all local drives of the workstation and replaces NE2000.COM with the newer version on drive J:.It renames any old NE2000.COM files on the local drives to NE2000.OLD.Press<F10> to save the login script.Additional InformationIf you are using NetWare v2.x and 3.x, see the following references for more information about WSUPDATE and related topics:WIDTH="132"For more information aboutWIDTH="180"Refer toWIDTH="132"Login scriptsWIDTH="180""book="utilref" docset="nw312"SYSCON" of Utilities ReferenceMapping network drives"book="utilref" docset="nw312"MAP" in Utilities ReferenceIf you are using NetWare v4.0, see the following references for more information about WSUPDATE and related topics:WIDTH="132"For more information aboutWIDTH="180"Refer toWIDTH="132"Login scriptsWIDTH="180"Chapter 3, "book="supernt" docset="nw40"Creating Login Scripts and  Menus" in Supervising the NetworkMapping network drivesChapter 3, "book="utilref" docset="nw40"Using Text Workstation  Utilities" of Utilities ReferenceUsing the WSUPDATE utilityChapter 3, "book="utilref" docset="nw40"Using Text Workstation  Utilities" of Utilities Reference