#EDIR DATA#
NetWare 3.12 OverviewDisclaimerNovell®, 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 ManualThe new features of NetWare v3.12 are explained in Chapter 1. Chapter 2 explains how to use the NetWare shell files (NETX). Use Chapter 2 if you are not using the NetWare DOS Requester and VLMs.Other Resources for HelpBesides this manual, you may want to use the following resources:Context-sensitive help. If you are using a NetWare menu utility and want more information about how to complete a task, press <F1> for help.If you are unsure how to use a command line utility, type the utility name and add the /? option for help. For instance, for help with using the RIGHTS utility, type RIGHTS /?.Hardware manuals. Many network problems occur because of malfunctioning hardware. If you can isolate a problem to a certain computer component or cable segment, check the manuals that came with the hardware involved.Novell ElectoText(tm). The NetWare Communication Services Manager (tm) viewer allows you to read NetWare manuals from your Windows or OS/2 workstation.All NetWare v3.12 manuals except the Quick Access Guide are available on the NetWare v3.12 CD-ROM.Novell Network Management System (NMS). This product helps you manage the cabling system, computers, software, and other components of the network. Contact your Novell Authorized Reseller for more information about using NMS on your network based system design, implementation, and management. Application Notes are a collection of technical articles published monthly.Novell publishes Research Reports as the research becomes available.You may purchase subscriptions and back issues of these publications from within the United States or Canada by calling the Novell Research Order Desk at (800) UPDATE1. From outside the United States or Canada, call (801) 429-5380.Third-party books and periodicals. A number of books on NetWare, including books published by Novell Press(tm), are available at most bookstores. In addition, numerous networking periodicals give advice on configuring, managing, and troubleshooting your network.NetWire®on CompuServe®. A fairly inexpensive way to get up-to-date advice and patches is through NetWire on the CompuServe bulletin board. To open a CompuServe account, call one of the following numbers:From within the United States or Canada, call (800) 524-3388.From within the United Kingdom, call 0800-289-378.From within Germany, call 0130-37-32.From the rest of Europe, call 44-272-255-111.From outside of the United States, Canada, and Europe, use the appropriate country code for the U.S. to call (614) 457-0802.Ask for "Representative 200." This key phrase simply lets the membership representative know that you are a Novell customer.NetWare Support Encyclopedia. The NSE program gives customers access to regularly-updated information from Novell and other vendors on products and services. In addition, an NSE Professional Volume is available that provides customers with all of the information in the NSE, plus patches, fixes, and more.Troubleshooting hardware and software. Specialized hardware and software packages, such as Novell's LANalyzer, are available to help you isolate network problems.User CommentsWe are continually looking for ways to make our products and our manuals as easy to use as possible. You can help us by sharing your comments and suggestions about how our manuals could be made more useful to you and about any inaccuracies or information gaps they may currently contain.You can submit your comments either by filling out the "User Comments" form at the end of this manual or by writing to us directly at the following address:Novell, Inc.Technical PublicationsMS C-23-1122 East 1700 SouthProvo, UT 84606 USAWe sincerely appreciate your comments about our products.LBL="1"New FeaturesNCP Packet SignatureHow idxid="w108"book="_idx" docset="nw312" tidref="i4056"NCP Packet Signature WorksNCP(tm) packet signature is an enhanced security feature that protects servers and clients using the NetWare Core Protocol(tm) (NCP) by preventing packet forgery.NCP packet signature prevents packet forgery by requiring the server and the client to "sign" each NCP packet. The packet signature changes with every packet.When to Use NCP Packet SignatureNCP packet signature is not required for every installation. Some network supervisors may choose not to use NCP packet signature because they can tolerate certain security risks.For information and instructions on using NCP packet signature, see "book="sysadmin" docset="nw312"SET" in System Administration and "book="ws_dos" docset="nw312"Improving Speed and Security on your Workstation" in Workstation for DOS and Windows. NMENUidxid="w109"book="_idx" docset="nw312" tidref="i4641"NMENU can be used to replace the MENU utility included in earlier versions of NetWare. NMENU requires less idxid="w110"book="_idx" docset="nw312" tidref="i4637"memory than the old MENU utility. When you upgrade to NetWare v3.12, you can convert menus created with MENU to NMENU and continue using them. For information and instructions on using NMENU, see "book="utilref" docset="nw312"NMENU" in Utilities Reference.NetWare idxid="w111"book="_idx" docset="nw312" tidref="i1700"idxid="w112"book="_idx" docset="nw312" tidref="i4266"DOS Requester and idxid="w113"book="_idx" docset="nw312" tidref="i7328"VLMsThe NetWare DOS Requester(tm) consists of a number of files that provide NetWare support for a DOS client. Unlike NETX or other previous versions of the shell, the DOS Requester consists of a number of Virtual Loadable Modules(tm) (VLMs(tm)). A VLM is a modular executable program with a set of logically grouped features or APIs. For example, transport-related functions (send packets, receive packets, etc.) fit logically into a VLM.Features of the NetWare DOS RequesterThe NetWare DOS Requester provides several new improvements over NETX. It does the following:Supports NetWare Directory Services(tm).Provides a modular architecture that has advantages for current and future applications.Takes advantage of memory-swapping technology and DOS redirection capability.Includes Packet Burst(tm) protocol and Large Internet Packet (LIP).Supports installed base of NetWare users by providing backward compatibility with NETX.idxid="w114"book="_idx" docset="nw312" tidref="i4676"Novell idxid="w115"book="_idx" docset="nw312" tidref="i4676"ElectroTextThe NetWare Communication Services Manager viewer allows you to read idxid="w116"book="_idx" docset="nw312" tidref="i4676"NetWare user idxid="w117"book="_idx" docset="nw312" tidref="i4676"idxid="w118"book="_idx" docset="nw312" tidref="i4676"manuals on your computer screen. All of the manuals in the NetWare v3.12 manual set are available online, with the exception of the Quick Access Guide.Communications Services Manager can be installed on either a NetWare server or a local hard disk. In addition, you must set up a workstation to view NetWare Communication Services.For information on idxid="w119"book="_idx" docset="nw312" tidref="i4676"installing Communication Services Manager, see Appendix B, "book="install" docset="nw312"Installing and Using Novell ElectroText," of Installation and Upgrade.Viewer idxid="w120"book="_idx" docset="nw312" tidref="i4676"FeaturesThe NetWare Communication Services Manager viewer gives you advantages over printed documentation. With it, you can do the following:Scroll sequentially through a book.Move quickly from one part of the book to another by selecting a section from the table of contents outline.Move quickly to another part of the book or a different book to follow a cross-reference.Return or step back to sections of the book that you previously viewed.Search for specific words or phrases in a library, bookshelf, or book.Print book sections on demand.Open several books at one time.New Migration and In-Place Upgrade UtilitiesThe NetWare idxid="w121"book="_idx" docset="nw312" tidref="i3913"Migration Utility, a workstation-based utility, allows you to transfer your network information "across the wire" from a NetWare v2.x or v3.x server or a LAN Server to an existing NetWare v3.12 server that is on the same network. The idxid="w122"book="_idx" docset="nw312" tidref="i2795"In-Place Upgrade Utility, a server-based utility (NetWare Loadable Module(tm)), allows you to change your network server that is running NetWare v2.1x or later into a NetWare v3.12 server without purchasing additional hardware.For information on the across the wire migration and in-place upgrade utilities, see the "book="install" docset="nw312"Upgrade an Existing File Server" section in Installation and Upgrade. New NetWare Loadable Modules (NLMs)idxid="w123"book="_idx" docset="nw312" tidref="i939"CDROMThe CDROM.NLM allows the server to use a CD-ROM disk as a read-only volume. For more information, see "book="sysadmin" docset="nw312"CDROM" in System Administration. idxid="w124"book="_idx" docset="nw312" tidref="i3058"KEYBUse KEYB to change the keyboard type for the file server console. The following keyboard types are available:English (United States)FrenchGermanItalianSpanishFor more information, see "book="sysadmin" docset="nw312"KEYB" in System Administration. idxid="w125"book="_idx" docset="nw312" tidref="i4601"NLICLEAR (Not-Logged-In CLEAR) NLICLEAR is an NLM used with NetWare v3.12 Runtime that periodically deletes or "clears" unauthenticated connections. Unauthenticated user connections cannot be reused until they are cleared. For more information, see "book="sysadmin" docset="nw312"NLICLEAR" in System Administration or "book="concepts" docset="nw312"NetWare Runtime" in Concepts.idxid="w126"book="_idx" docset="nw312" tidref="i4767"NUTUse NUT (NLM Utility User Interface) if you have a NetWare v3.11 loadable module (such as v3.11 MONITOR) that requires the NUT library of routines and functions. For more information, see "book="sysadmin" docset="nw312"NUT" in System Administration. NWSNUT idxid="w127"book="_idx" docset="nw312" tidref="i4786"Use NWSNUT (NLM Utility User Interface) if you have a NetWare v4.0 loadable module that requires the NWSNUT library of routines and functions.For more information, see "book="sysadmin" docset="nw312"NWSNUT" in System Administration. NetWareMessagingYour NetWare box includes a messaging starter kit, which contains two products---NetWare Basic MHS(tm) and FirstMail(tm). This section explains why you might use messaging and describes both of these products.Why Use idxid="w128"book="_idx" docset="nw312" tidref="i3873"Messaging?Messaging has become a critical component of the network environment. In fact, messaging has become a core network service, third only to file and print services. It improves communication, increases productivity, and maximizes the use of existing resources.Improving communications. In an increasingly fast-paced environment, timely and reliable communication is critical. Messaging applications are one type of tool developed to meet communication needs. They allow employees to communicate even when meetings, travel schedules, and geographically dispersed locations prevent them from meeting face to face.Increasing productivity. Employees often miss phone calls, meetings, etc. Messaging increases productivity by improving the success rate for communications because it does not require all participants in a conversation to be available at the same time. Maximizing the use of existing resources. Without any additional resources, you can provide your users with all the benefits of a messaging solution.What is idxid="w129"book="_idx" docset="nw312" tidref="i661"idxid="w130"book="_idx" docset="nw312" tidref="i3873"Basic MHS?NetWare Basic Message Handling Service (MHS) is a product that provides message delivery among users on the same file server.Users create messages with an electronic mail application that complies with Novell's Standard Message Format (SMF) interface. The application submits the message to Basic MHS, which delivers it to the recipient's mailbox. (For a list of SMF-compatible applications, refer to the NetWare Messaging Solutions Guide, available from your Novell Authorized ResellerCLM or sales office.)Basic MHS is part of Novell's family of messaging products, which also includes NetWare Global MHS(tm). Global MHS, a scalable, full-featured MHS platform for NetWare v3.11 and later environments, provides message delivery among users at different file servers, across asynchronous and internetwork links. Through optional protocol modules, Global MHS also provides connectivity to SMTP, SNADS, and X.400 environments. When your need for messaging grows beyond a single server, you can upgrade to the Global MHS product. Basic MHS is fully compatible with Global MHS. The following features make Basic MHS easy to use:Full-name user addressing. Basic MHS simplifies addressing of messages by allowing you to use names as user addresses. For example, John Smith's user address can be "John Smith". Import of users from the NetWare bindery. The installation program allows you to import users from the NetWare bindery into the Basic MHS database. This minimizes the amount of time required for installation and administration of Basic MHS.Like the other products in the NetWare MHS family, Basic MHS supports a simple, file-based interface that you can use to write messaging-enabled applications. These applications can use NetWare MHS to send messages to users or to other applications. For example, a message-enabled database program can generate a report and use Basic MHS to distribute it to a group of MHS users.What Is idxid="w131"book="_idx" docset="nw312" tidref="i2430"idxid="w132"book="_idx" docset="nw312" tidref="i3873"FirstMail?FirstMail is a starter electronic mail utility that is available in both DOS and Macintosh versions. It provides such basic electronic mail functionality as the following:Create and send messages.Read, print, delete, save, reply to, and forward messages.Attach files to a message.Create and maintain an address directory.Organize messages in folders.FirstMail provides easy-to-use menus and (in FirstMail for DOS) context-sensitive online help. NetWare v3.12 Ethernet Frame TypesThe default idxid="w133"book="_idx" docset="nw312" tidref="i1873"idxid="w134"book="_idx" docset="nw312" tidref="i2518"Ethernet frame type for NetWare v3.12 is 802.2. The default Ethernet frame type for NetWare v3.11 and earlier is 802.3. Machines running only Ethernet frame type 802.2 cannot see machines running only Ethernet frame type 802.3, and vice versa.If you are installing NetWare v3.12 in an existing NetWare environment that is using Ethernet 802.3 frame types, you need to either specify both 802.2 and 802.3 frame types in your AUTOEXEC.NCF file and then bind IPX to both, or you must change the Ethernet frame type to 802.3.Binding IPX to both 802.2 and 802.3 frame types can affect network speed and performance. Do not bind to both frame types unless it is necessary.NetWare v3.12 PatchesThe following table describes idxid="w135"book="_idx" docset="nw312" tidref="i5027"patches that have been made to the OS since the release of NetWare v3.11. Since these patches are now included in the NetWare v3.12 OS, you do not have to manually load them. LBL="1-1" INLINE="F"Description of NetWare v3.12 patchesWIDTH="108"Patch nameWIDTH="312"DescriptionWIDTH="108"ASNCRDFX.NLMWIDTH="312"Fixes a problem that may occur when multiple threads do asynchronous  reads. It was possible for a thread to read data that was written by another  thread.BIGRFIX.NLMAllows the OS to prevent read requests larger than 512 KB from  overrunning the stack. This problem occurred when loading large NLMs.CLPHFIX.NLMFixes the "Clear Phantom called with not primary directory number"  problem. DIAGRFSX.NLMFixes two problems with network management. This NLM fixes the  problem of the server not responding to requests issued by the network  management console. It also fixes the problem of the server not  responding to network management requests directed to other networks  connected to the server.DIRLPFIX.NLMFixes the infinite loop problem caused when the DOS DIR, FindFirst and  FindNext commands were issued in a subdirectory with more than 65,535  files.DOSUNFIX.NLMFixes a problem with NetWare/NFS v1.2. A problem existed if a file was  renamed from 99999999.v0 to 99999999.V0.DOTFIX.NLMFixes a problem that allowed multiple directories with the same name to  be created at the SYS: (root) level.EAINFIX.NLMFixes a problem that occurred with extended attributes when two or more  stations executed XCOPY multiple times.EVENTFIX.NLMFixes a problem that occurred when a "delete bindery object" call was  made to the OS. FATFIX.NLMFixes a TurboFAT and FAT corruption problem that occurred when  multiple stations randomly accessed large database files.GETQFIX.NLMFixes the problem of .SRV files being deleted in the SYS:SYSTEM queue  subdirectories.GETRFIX.NLMFixes a problem that occurred when a driver requested a valid linked  request that had been changed by another process.GETSEFIX.NLMFixes a problem that occurred when more than 31 security equivalences  for a user or group ID were set up.GNSFIX.NLMFixes a problem that occurred when a user on a one-network system tried  to reboot and reconnect when all the connections were in use.HTFXFX.NLMFixes a problem that occurred when using disk block and cache buffer  sizes larger than 4 KB.MAXCDCFX.NLMChanges the maximum limit of the "Maximum Concurrent Disk Cache  Writes" SET parameter from 100 to 1000. This limit enables better  performance from high throughput disk controller drivers and high  throughput EISA drives. MFIXOPEN.NLMFixes a problem that occurred when the MAC gateway was run instead of  the AFP NLMs. MAC users were unable to open files flagged Read Only. MKDIRFIX.NLMCorrects invalid error codes returned by the "create directory" call or  when copying a file to an invalid path.NCPSPFIX.NLMPrevents a zero-length WriteToSpool NCP from being processed. OS2OPNFX.NLMAllows a user to use the TYPE command to view a file even though SCAN  file rights have not been granted.REMDEVFX.NLMFixes a problem that occurred when formatting removable devices.REQFIX.NLMFixes a problem that occurred in PAUDIT when several users used the same  workstation to log in. The "requests" value in PAUDIT was not reinitialized  for each user. This NLM fixes this problem by reinitializing the number of  requests made from a station each time a new user logs in.SPXFSFIX.NLMCorrects problems for certain applications that may hang due to lost Event  Control Blocks (ECBs).TRSTFIX.NLMFixes a problem that occurred when nine or more trustee directory  assignments for individual users or groups were made at the root level of  the same volume. This NLM also fixes a problem that occurred when  granting trustee rights to an existing group.TTSFIX.NLMFixes a problem that occurred when certain applications executed explicit  TTS(tm) and file locking was also used.UNKFIX.NLMFixes a problem that occurred when entering the complete filename of a  valid NetWare file at the server console. For example, typing  "MONITOR.NLM" instead of "LOAD MONITOR" would previously cause  this problem.WORMROFX.NLMFixes a problem that occurred when a new device with the Write Disable  tab set was inserted after a read/write device was removed. The OS did  not recognize the new device as Read Only.WSDFIX.NLMFixes the problem of APIs allowing users to access files on volumes where  they have no rights.LBL="2"Using the idxid="w136"book="_idx" docset="nw312" tidref="i4400"NetWare Shell FilesOverviewNovell recently upgraded the NetWare shell to a new architecture referred to as NetWare DOS Requester(tm), replacing the NETX file series. If you want to upgrade your workstation software to use this new architecture, see Chapter 1, "book="ws_dos" docset="nw312"About the NetWare DOS Requester," in Workstation for DOS and Windows. If you choose to use the previous architecture, this chapter provides you with a basic overview of the NetWare shell files and with the procedures for using them with your DOS and Windows workstations.WIDTH="264"TopicWIDTH="48"PageWIDTH="264"IDREF="FM53681""The Netware Shell Workstation Environment"WIDTH="48"IDREF="FM53681"13IDREF="FM90765""Decompressing the LSL, Network Board Driver, and IPXODI  Files"IDREF="FM90765"14IDREF="FM69947""Updating the NetWare Shell Files from the LOGIN Directory"IDREF="FM69947"15IDREF="FM84632""Updating the NetWare Shell Files from Diskette"IDREF="FM84632"17IDREF="FM51738""Loading the Workstation Files"IDREF="FM51738"18IDREF="FM30184""Understanding the NET.CFG File for the NetWare Shell"IDREF="FM30184"19IDREF="FM27915""Understanding NetWare Shell File Command Options and  Concepts"IDREF="FM27915"31IDREF="FM45594""NETX.EXE (NetWare Conventional Memory Shell)"IDREF="FM45594"31IDREF="FM92232""EMSNETX.EXE (NetWare Expanded Memory Shell)"IDREF="FM92232"34IDREF="FM30008""XMSNETX.EXE (NetWare Extended Memory Shell)"IDREF="FM30008"36ID="FM27321"Advantages of idxid="w137"book="_idx" docset="nw312" tidref="i4248"Using the NetWare DOS Requester The NetWare DOS Requester provides several new improvements over NETX:Supports NetWare Directory Services(tm) provided with NetWare v4.0.Provides a modular architecture that allows for more efficient use of memory and gives developers a more flexible platform.Takes advantage of memory-swapping technology and DOS redirection capability.Includes Packet Burst(tm) protocol and Large Internet Packet.Supports installed base of NetWare users by providing idxid="w138"book="_idx" docset="nw312" tidref="i4248"backward compatibility with NETX.IDREF="FM10380"Figure 2-1 shows the difference between NETX and the NetWare DOS Requester architectures.LBL="2-1"ID="FM10380"Comparison idxid="w139"book="_idx" docset="nw312" tidref="i4248"idxid="w140"book="_idx" docset="nw312" tidref="i4582"of NETX and NetWare DOS Requester architecturesFILE="n312o01a.pbm"The NetWare DOS Requester file replaces idxid="w141"book="_idx" docset="nw312" tidref="i4582"NETX.COM. It is recommended that you idxid="w142"book="_idx" docset="nw312" tidref="i4248"upgrade your workstation to use the new workstation files. Complete installation of the new workstation files by referencing Workstation Basics and Installation for information and procedures.If you chose to not upgrade your workstation to use the NetWare DOS Requester, continue reading the following sections.ID="FM53681"The Netware Shell Workstation idxid="w143"book="_idx" docset="nw312" tidref="i7493"EnvironmentThe key components of the NetWare shell workstation environment are four terminate-and stay-resident (TSR) programs: LSL(tm) ( idxid="w144"book="_idx" docset="nw312" tidref="i3594"Link Support Layer(tm))A network board driver (example: NE2000)IPXODI (Internetwork Packet Exchange Open Data-Link Interface)NETX (the network shell)If an ODI(tm)-compliant board driver is not available, your workstation environment will consist of two terminate-and-stay-resident (TSR) programs:IPX(tm) dedicated IPX driver (non-ODI)NETX (the network shell)The LSL.COM, network board driver.COM and IPXODI.COM files idxid="w145"book="_idx" docset="nw312" tidref="i3021"replace IPX.COM. It is recommended that you upgrade your workstation to use the new workstation files. See Chapter 3, "Installing a NetWare Workstation," of Workstation Basics and Installation for information and procedures on using a program-based installation, or install the files manually by using the procedure in the following section.ID="FM90765"idxid="w146"book="_idx" docset="nw312" tidref="i1333"Decompressing the idxid="w147"book="_idx" docset="nw312" tidref="i3595"LSL, idxid="w148"book="_idx" docset="nw312" tidref="i4507"Network Board Driver, and idxid="w149"book="_idx" docset="nw312" tidref="i3022"IPXODI FilesThe following idxid="w150"book="_idx" docset="nw312" tidref="i5579"idxid="w151"book="_idx" docset="nw312" tidref="i7529"workstation files are in compressed format on the WSDOS_1 and WSDRV_1 diskettes. LSL.COMnetwork board driver.COMIPXODI.COMYou must decompress these files to use them on your workstation. If your workstation software is on CD-ROM, go to "Creating Workstation Installation Diskettes from CD-ROM" in Chapter 2 of Workstation Basics and Installation.ProcedureDecompress and copy the LSL.COM and IPXODI.COM files from the WSDOS_1 diskette to your workstation directory. To decompress a file, type  idxid="w152"book="_idx" docset="nw312" tidref="i4609"NLUNPACK <filename> [destination_directory:] <Enter>For example, to expand LSL.COM, type  NLUNPACK A:LSL.CO_ C:\NWCLIENT <Enter>Decompress and copy the appropriate network board driver.COM file from the WSDRV_1 diskette to your workstation directory. To decompress a file, type  NLUNPACK <filename> [destination_directory:] <Enter>To expand NE2000.COM for example, type  NLUNPACK A:\DOS\NE2000.CO_ C:\NWCLIENT <Enter>Ensure that a NET.CFG file exists in the same directory as your workstation files.For information on how to create a NET.CFG file, see Chapter 2, "Configuring Your Workstation," of Workstation for DOS and Windows.Update your workstation's NetWare shell files.If you want to update the workstation NetWare shell file from your login directory, go to IDREF="FM69947""Updating the NetWare Shell Files from the LOGIN Directory" on page 15.If you want to update the workstation NetWare shell file from from diskette, go to IDREF="FM84632""Updating the NetWare Shell Files from Diskette" on page 17.ID="FM69947"Updating the idxid="w153"book="_idx" docset="nw312" tidref="i7083"idxid="w154"book="_idx" docset="nw312" tidref="i5579"NetWare Shell Files from the LOGIN idxid="w155"book="_idx" docset="nw312" tidref="i1532"idxid="w156"book="_idx" docset="nw312" tidref="i4400"DirectoryThis section applies only to workstations that already have a previous version of NetWare shell files installed. If you are installing a new NetWare workstation, go to IDREF="FM84632""Updating the NetWare Shell Files from Diskette" on page 17. The following checklists and procedures will help you set up your workstation for updating NetWare shell files from the LOGIN directory. PrerequisitesEnsure that the server you log in to is upgraded and running NetWare v3.12Ensure that a previous version of the NetWare shell files are loaded on your workstation.Ensure that a copy of the following NetWare shell files exist in your LOGIN directory:EMSNETX.EXENETX.EXEXMSNETX.EXEProcedureChange to the LOGIN directory.Copy the appropriate NetWare shell file for your workstation to your boot diskette or workstation directory. For example, to copy NETX.EXE, you would type  COPY NETX.EXE drive_letter:\client_directory<Enter>Replace drive_letter and client_directory with the drive letter and directory containing your workstation files. For example, if your workstation files are copied to the NWCLIENT directory on drive C:, you would type  COPY NETX.EXE C:\NWCLIENT <Enter>or, for a boot diskette, you might type  COPY NETX.EXE A:\ <Enter>If your workstation is capable of extended or expanded memory support, replace NETX.EXE with the file which corresponds to the type of memory support you have:XMSNETX.EXE (for extended memory)EMSNETX.EXE (for expanded memory)Reboot your workstation.Load the new NetWare shell file.Commonly, the workstation files are loaded automatically from a batch file. If you want to load the files manually, go to IDREF="FM51738""Loading the Workstation Files" on page 18.ID="FM84632"Updating the idxid="w157"book="_idx" docset="nw312" tidref="i5579"idxid="w158"book="_idx" docset="nw312" tidref="i7083"NetWare Shell Files from idxid="w159"book="_idx" docset="nw312" tidref="i1603"idxid="w160"book="_idx" docset="nw312" tidref="i4400"DisketteTo copy files directly from diskettes, follow these steps.ProcedureFormat a DOS diskette.Copy all the files in the LOGIN subdirectory on the NetWare v3.12 SYSTEM_3 diskette to the formatted diskette by typing  COPY source_directory:\wild_card destination_directory: <Enter>For example, type  COPY A:LOGIN\*.* B: <Enter>Label the formatted diskette "NetWare Shell Files."Insert the "NetWare Shell Files" diskette into a floppy disk drive and change to that drive. For example, if you have inserted the diskette into drive A:, type  A:<Enter>Copy the appropriate NetWare shell file for your workstation to your boot diskette or workstation directory. For example, to copy NETX.EXE, you would type  COPY NETX.EXE drive_letter:\client_directory<Enter>Replace drive_letter and client_directory with the drive letter and directory containing your workstation files. For example, if your workstation files are copied to the NWCLIENT directory on drive C:, you would type  COPY NETX.EXE C:\NWCLIENT <Enter>or, for a boot diskette, you might type  COPY NETX.EXE A:\ <Enter>If your workstation is capable of extended or expanded memory support, replace NETX.EXE with the file which corresponds to the type of memory support you have:XMSNETX.EXE (for extended memory)EMSNETX.EXE (for expanded memory)Reboot your workstation.Load the new NetWare shell file.Commonly, the workstation files are loaded automatically from a batch file. If you want to load the files manually, go to IDREF="FM51738""Loading the Workstation Files" on page 18.ID="FM51738"Loading the idxid="w161"book="_idx" docset="nw312" tidref="i3338"idxid="w162"book="_idx" docset="nw312" tidref="i5579"idxid="w163"book="_idx" docset="nw312" tidref="i7529"Workstation FilesYou can load the NetWare workstation files from the command line or from a batch file.Loading from the Command LineProcedureChange to your workstation directory by typing  CD\workstation_directory<Enter>Load the workstation files in the following order:  idxid="w164"book="_idx" docset="nw312" tidref="i3595"LSL <Enter>  network board driver.COM <Enter>  idxid="w165"book="_idx" docset="nw312" tidref="i3022"IPXODI <Enter>  idxid="w166"book="_idx" docset="nw312" tidref="i4582"NETX <Enter>Loading from a Batch FileAn example of a batch file using a NE2000 network board driver is as follows:  @ECHO OFF  C:  CD \NWCLIENT  LSL  NE2000.COM  IPXODI  NETX  CD \For command options and concepts, see IDREF="FM27915""Understanding NetWare Shell File Command Options and Concepts" on page 31.ID="FM30184"Understanding the NET.CFG idxid="w167"book="_idx" docset="nw312" tidref="i4097"idxid="w168"book="_idx" docset="nw312" tidref="i4097"File for the NetWare ShellThe NET.CFG file is a specialized text file that you create with any ASCII text editor and include in your workstaion directory or on a workstation boot diskette with any other necessary boot files. Like the DOS CONFIG.SYS file, the NET.CFG file contains configuration values that are read and interpreted when your workstation starts up. These values adjust the default operating parameter settings of the NetWare shell, IPX, or other workstation files.The NET.CFG file replaces the previous shell configuration file named SHELL.CFG. See Chapter 2, "Configuring Your Workstation," of Workstation for DOS and Windows for information on the NET.CFG file.ID="FM60465"Using a idxid="w169"book="_idx" docset="nw312" tidref="i4097"NET.CFG FileUse entries in the idxid="w170"book="_idx" docset="nw312" tidref="i5579"NET.CFG file to change the workstation's network environment or idxid="w171"book="_idx" docset="nw312" tidref="i4097"idxid="w172"book="_idx" docset="nw312" tidref="i7493"configuration. For example, you might want to change the configuration in these cases:You changed the default hardware settings on the network board.You are using multiple protocols.You are using Novell's LAN Workplace.ID="FM37540"Creating and Modifying the idxid="w173"book="_idx" docset="nw312" tidref="i5579"idxid="w174"book="_idx" docset="nw312" tidref="i4097"NET.CFG FileProcedureUse a DOS text editor to type section headings and options in in an existing NET.CFG file or a NET.CFG file which you create to set up your workstation configuration.See IDREF="FM78626""NET.CFG Options for NetWare Shell Parameter Settings" on page 22 for descriptions of these settings.Use the following idxid="w175"book="_idx" docset="nw312" tidref="i5579"idxid="w176"book="_idx" docset="nw312" tidref="i4097"idxid="w177"book="_idx" docset="nw312" tidref="i4916"idxid="w178"book="_idx" docset="nw312" tidref="i4916"conventions to create or modify a idxid="w179"book="_idx" docset="nw312" tidref="i4097"NET.CFG file:Type one heading or option per line.Headings and options are not case-sensitive. Blank lines are ignored, but they can be helpful in separating the section headings or options to make the NET.CFG file easier to read.Enter section headings at the left margin of the file with no spaces before or after them.Each NET.CFG section heading may have several options.Enter options, one per line, below the section heading to which they apply, and indent each one.Use<Spacebar> or <Tab> to indent options. Options must be indented at least one space.Place a hard return at the end of every line in the file, including the last line.If you don't put a return at the end of the last line, the line is ignored.Precede comment lines with a semicolon.Copy the NET.CFG file to the workstation boot diskette or directory.If all workstations use the same NET.CFG file, you can save time by copying the NET.CFG file onto a master workstation diskette. Then copy the files on the master workstation diskette to each workstation.If each workstation requires a unique NET.CFG file, you must copy a unique NET.CFG file to each workstation boot diskette or boot directory.ID="FM65261"Sample idxid="w180"book="_idx" docset="nw312" tidref="i4097"NET.CFG FileFollowing is a sample NET.CFG file thatChanges the IRQ on the link driver to 4Changes the port to 340Sets up F: as the first network drive when you log in to the network  LINK DRIVER NE2000     ; Change the interrupt (IRQ) to 4     INT #1 4     ; Change the port to 340 (hex)     PORT #1 340  NETX     ; Set up F: as the first drive on network     First Network Drive = FYou can also specify command line parameters for NETX. See IDREF="FM27915""Understanding NetWare Shell File Command Options and Concepts" on page 31 for these parameters.ID="FM78626"NET.CFG Options for NetWare Shell Parameter Settingsidxid="w181"book="_idx" docset="nw312" tidref="i4916"These NET.CFG parameter settings are for all three types of NetWare shell files:NETX.EXE (for conventional memory)EMSNETX.EXE (for expanded memory)XMSNETX.EXE (for extended memory)IDREF="FM75232"Figure 2-2 shows the various idxid="w182"book="_idx" docset="nw312" tidref="i4097"parameter idxid="w183"book="_idx" docset="nw312" tidref="i4097"settings that you can use. Description of the settings immediately follow the figure.LBL="2-2"ID="FM75232"NET.CFG options for NetWare Shell filesFILE="n312o02a.pbm"idxid="w184"book="_idx" docset="nw312" tidref="i4139"ALL SERVERS [ON | OFF]idxid="w185"book="_idx" docset="nw312" tidref="i196"Determines whether the End of Task is sent to all connected servers or only to those servers interacting with the task.If this option is set to ON, End of Task is sent to all connected servers.If this option is set to OFF, End of Task is sent to only those servers the current process has interacted with.Default: OFFidxid="w186"book="_idx" docset="nw312" tidref="i4139"ENTRY STACK SIZE numberidxid="w187"book="_idx" docset="nw312" tidref="i1829"Ensures that the code residing in expanded memory is visible in the memory page frame.Many TSRs and other programs using expanded memory may need this parameter increased.Default: 10 Range: 5 to 40This parameter is used only by EMSNETX.EXE.idxid="w188"book="_idx" docset="nw312" tidref="i4139"ENVIRONMENT PAD numberidxid="w189"book="_idx" docset="nw312" tidref="i1832"Defines the number of bytes that are added to a program's environment space before executing the program. Increasing this parameter allows NetWare utilities to update the path environment variable of the current environment when adding search paths. Default: 17 bytesRange: 17 to 512 bytesidxid="w190"book="_idx" docset="nw312" tidref="i4139"EOJ  [ON | OFF]Specifies whether files, locks, semaphores, etc. are closed automatically at the end of a job.Default: ONidxid="w191"book="_idx" docset="nw312" tidref="i4139"FILE HANDLES numberidxid="w192"book="_idx" docset="nw312" tidref="i2019"Sets how many files a workstation can have open on the network at one time.The setting for local files is handled through the DOS CONFIG.SYS file.Some applications ask for more than the default of 40 open files. If you receive many error messages that indicate no available files, increase the value.Default: 40 open filesidxid="w193"book="_idx" docset="nw312" tidref="i4139"GET LOCAL TARGET STACKS numberidxid="w194"book="_idx" docset="nw312" tidref="i2546"Specifies the number of stacks that should be allocated for use by IPX when processing Get Local Target requests from IPX applications. Each additional allocated stack increases IPX memory usage by 384 bytes.The default value is normally adequate for most users. However, if you are using a multitasking DOS product---such as DR DOS 6.0---and you are running more than one IPX application in different DOS sessions, you may have to increase the number of stacks. If you experience problems getting an IPX application to communicate with another node on the network, increasing the number of stacks may alleviate the problem.Default: 1 stackRange: 1 to 10idxid="w195"book="_idx" docset="nw312" tidref="i4139"HOLD  [ON | OFF]idxid="w196"book="_idx" docset="nw312" tidref="i2664"Determines whether workstation files should be held open if they have been accessed and then closed.If this parameter is set to ON, all files opened by a program are held open until the program exits.Older versions of certain applications that use FCB_IO may need this parameter set to ON.Default: OFFidxid="w197"book="_idx" docset="nw312" tidref="i4139"LIPACKETS [ON | OFF]idxid="w198"book="_idx" docset="nw312" tidref="i3223"In the past, NetWare communicated across routers and bridges with a 576-byte maximum packet size. However, Ethernet and Token- Ring are capable of using larger packets for communication.With this parameter set to ON, the maximum packet size negotiated between the NetWare server and the workstation, is used across routers and bridges.Default: ONSome routers and bridges have been hardcoded to use 576-byte packets. In this case, the NetWare shell can use only 576-byte packets, regardless of this parameter.idxid="w199"book="_idx" docset="nw312" tidref="i4139"LOCK DELAY numberidxid="w200"book="_idx" docset="nw312" tidref="i3373"Determines the amount of time (in ticks) the shell waits before trying to get a lock.When many users access the same file at the same time, the shell may be unable to gain access before its allotted wait time.Use this parameter if a workstation frequently receives error messages when a file is requested.This number is used for lock types that do not have a wait ability. For locks that have a wait ability, the wait time is calculated by multiplying this parameter number by the LOCK RETRIES number and then multiplying by 2. The resulting number is the time, in ticks, that the workstation waits for a lock.Default: 1 tick (about 0.5 seconds)idxid="w201"book="_idx" docset="nw312" tidref="i4139"LOCK RETRIES numberidxid="w202"book="_idx" docset="nw312" tidref="i3374"Specifies the number of times the shell attempts to get a lock on the network.It is part of an equation that determines the total time the shell waits when attempting to access a locked file. If a workstation frequently receives error messages when a file is requested, increase the value of this parameter.Default: 3 retriesidxid="w203"book="_idx" docset="nw312" tidref="i4139"MAX CUR DIR LENGTH numberidxid="w204"book="_idx" docset="nw312" tidref="i3745"Allows the number of bytes returned to be specified. DOS defines the Get Current Directory call to return 64 bytes of path.In the past, the shell allowed 128 bytes to be returned. This parameter is now configured.Default: 64 bytesRange: 64 to 255 bytesidxid="w205"book="_idx" docset="nw312" tidref="i4139"MAX PATH LENGTH numberidxid="w206"book="_idx" docset="nw312" tidref="i3746"Allows users to specify maximum path length, up to 255 characters. This path doesn't include NetWare server names or filenames.Default: 255 bytesRange: 64 to 255idxid="w207"book="_idx" docset="nw312" tidref="i4139"PATCH byte_offset valueidxid="w208"book="_idx" docset="nw312" tidref="i5026"Allows any address in the shell to be patched with any specified value.Use this parameter if a shell problem is announced and the solution is easily accomplished through changing some bytes within the programming. PATCH specifies the location of the bytes and inserts the correct values.Default: Noneidxid="w209"book="_idx" docset="nw312" tidref="i4139"SHARE [ON | OFF]idxid="w210"book="_idx" docset="nw312" tidref="i6327"Allows a child process to inherit all the resources of its parent process.Default: ONidxid="w211"book="_idx" docset="nw312" tidref="i4139"SIGN 386 MODE = numberidxid="w212"book="_idx" docset="nw312" tidref="i6343"Allows NCP(tm) packet signature for workstations that load Windows from the network and run in enhanced (386) mode.The number values are as follows0 = enables interrupts1 = disables interrupts and preserves 386 32-bit characters2 = forces 16-bit signingDefault: 1idxid="w213"book="_idx" docset="nw312" tidref="i4139"SPECIAL UPPERCASE  [ON | OFF]idxid="w214"book="_idx" docset="nw312" tidref="i6435"Used for foreign language and special characters. The shell does not translate uppercase ASCII characters above 128. Set this parameter to ON to cause the shell to call DOS for this translation. Default: OFF idxid="w215"book="_idx" docset="nw312" tidref="i4139"TASK MODE numberidxid="w216"book="_idx" docset="nw312" tidref="i6702"Determines the way the shell handles virtual machine task management.The default works with Windows 3.0. If you are using an earlier version of Windows or a third-party multitasking program, use 1. If you are not using a multitasking program and want a little extra speed, use 0.Default: 2idxid="w217"book="_idx" docset="nw312" tidref="i4139"TEMP DRIVE DETECTION [ON | OFF]idxid="w218"book="_idx" docset="nw312" tidref="i6763"Recognizes if a temporary drive is available for file-swapping.Default: ONidxid="w219"book="_idx" docset="nw312" tidref="i4139"Other NET.CFG Options for NetWare Shellsidxid="w220"book="_idx" docset="nw312" tidref="i4861"You can use the following NET.CFG options for your workstation. These options are not specific to the NetWare shell files.See Appendix B, "NET.CFG File Parameters," of Workstation for DOS and Windows for a description of the following parameters:CACHE BUFFERS numberCHECKSUM  [ON | OFF]DOS NAME nameLOCAL PRINTERS numberLONG MACHINE TYPE nameMAX TASKS numberPB BUFFERS numberPREFFERED SERVER server_namePRINT HEADER numberPRINT TAIL numberREAD ONLY COMPATIBILITY  [ON | OFF]SEARCH MODE numberSET STATION TIME  [ON | OFF]SHORT MACHINE TYPE nameSHOW DOTS  [ON | OFF]SIGNATURE LEVEL numberID="FM27915"Understanding NetWare Shell File Command Options and ConceptsAn application makes requests of the operating system through predefined function calls. The NetWare shell intercepts these requests and determines if the request is for the local operating system (DR-DOS, MS-DOS, PC-DOS) or the network operating system (NetWare). If the request should be handled by DOS, the shell hands the request off to DOS. If the request should be handled by NetWare, the shell packages the request for IPX. IPX takes the package to the destination and returns the requested information back to the shell, which then gives the information to the application.There is a NetWare shell file for each type of DOS memory available:NETX.EXE (for conventional memory)EMSNETX.EXE (for expanded memory)XMSNETX.EXE (for extended memory)You load only the shell file best suited for your particular workstation environment. ID="FM45594"NETX.EXE (NetWare Conventional Memory Shell)Use NETX to load the network shell, view the version of the shell, or unload the shell. This shell is for use with DOS 3.0 through 6.0.PrerequsitesYou must load the following NetWare shell files before loading the NETX.EXE file:LSL.COMnetwork board driver.COM (NE2000.COM)IPXODI.COMIf you are using dedicated IPX, you must load the IPX.COM file before loading the NETX.EXE file.IPX.COM is generated with the WSGEN.EXE utility. The WSGEN.EXE utility is not included with NetWare versions later than v3.11.Command Format  idxid="w221"book="_idx" docset="nw312" tidref="i4582"NETX [/?] | [PS = server name] | [/U] | [/F] | [/C=path\filename.ext]idxid="w222"book="_idx" docset="nw312" tidref="i4916"Command Options[/?]Displays help screens.[PS = server name]Specifies a preferred server.[/C=path\filename.ext]Specifies a configuration file for NETX to use. The default configuration file is NET.CFG.[/U]Unloads resident NETX from memory. When you execute this option, a screen similar to the following appears:  You are being logged out of all servers . . .  Memory for resident shell has been released.  The NetWare shell has been unloaded.[/F]Forces the resident NETX to unload. This option is useful for unloading NETX when other programs are loaded after NETX.Using this option may cause your system to fail if programs are still accessing NETX.Conceptsidxid="w223"book="_idx" docset="nw312" tidref="i4582"The NetWare shell file NETX.EXE captures network commands given to the workstation and redirects them to the network; if the messages were not redirected, DOS would attempt to execute them. idxid="w224"book="_idx" docset="nw312" tidref="i3802"The NetWare shell, NETX, intercepts requests by trapping software interrupts. Trapping means that the shell takes all requests made by the application before those requests get to DOS. The interrupts trapped are the following:Interrupt 20h, now a seldom-used way of exiting an applicationInterrupt 21h, used to call standard DOS functionsInterrupt 24h, used to handle critical errorsInterrupt 27h, now a seldom-used means of making an application a TSRInterrupt 17h, used to send data to local printer portsThe most used of these interrupts is 21h, the interrupt that DOS uses to service applications. After a request is inspected, the shell either passes it to the regular DOS interrupt routine, or it translates it into a request that is understood by the NetWare server and hands it to IPX for transmission to the NetWare server. When data returns from the server, the conversion of requests is handled in the same fashion but in reverse order. Whether the request is handled by local DOS or the network server is transparent to the application and the user. ID="FM92232"EMSNETX.EXE (NetWare Expanded Memory Shell)Use EMSNETX to load the network shell, view the version of the shell, or unload the shell. This shell is for use with DOS 3.0 through 6.0.PrerequsitesYou must load the following NetWare shell files before loading the EMSNETX.EXE file:LSL.COMnetwork board driver.COM (NE2000.COM)IPXODI.COMIf you are using dedicated IPX, you must load the IPX.COM file before loading the NETX.EXE file.IPX.COM is generated with the WSGEN.EXE utility. The WSGEN.EXE utility is not included with NetWare versions later than v3.11.Command Format  idxid="w225"book="_idx" docset="nw312" tidref="i1810"EMSNETX [/?] | [PS = server name] | [/U] | [/F] | [/C=path\filename.ext]idxid="w226"book="_idx" docset="nw312" tidref="i4916"Command Options[/?]Displays help screens.[PS = server name]Specifies a preferred server.[/C=path\filename.ext]Specifies a configuration file for EMSNETX to use. The default configuration file is NET.CFG.[/U]Unloads resident EMSNETX from memory. When you execute this option, a screen similar to the following appears:  You are being logged out of all servers . . .  Memory for resident shell has been released.  The NetWare shell has been unloaded.[/F]Forces the resident EMSNETX to unload. This option is useful for unloading EMSNETX when other programs are loaded after EMSNETX.Using this option may cause your system to fail if programs are still accessing EMSNETX.Conceptsidxid="w227"book="_idx" docset="nw312" tidref="i1810"Expanded memory refers to memory in addition to the 640KB limit of conventional memory. An expanded memory manager swaps memory that exists between the 640KB and the 1MB range into a window, or memory page. This allows DOS applications to access up to 32 KB of expanded memory. idxid="w228"book="_idx" docset="nw312" tidref="i3802"The NetWare Expanded Memory shell moves most of the shell out of conventional DOS memory and puts it in expanded memory. This frees up 35 KB of conventional memory. The remaining 8 KB of the shell must remain in conventional memory to handle interrupts and some data.The NetWare Expanded Memory shell was written to the specifications of LIM/EMS (Lotus/Intel/Microsoft Expanded Memory Specification) v4.0 memory manager.Expanded memory manufacturers provide expanded memory Specification (EMS)-compatible driver programs. You must load an EMS-compatible driver before loading the NetWare Expanded Memory shell. To install the NetWare Expanded Memory shell, you need to Load a third-party EMS-compatible driverCopy the NetWare Expanded Memory shell file, EMSNETX.EXE, to the workstation directory or boot disketteInclude the filename EMSNETX.EXE in the AUTOEXEC.BAT fileBecause this shell operates in expanded memory, larger applications can run in the conventional memory space. This approach is faster than disk swapping and overlays.The NetWare Expanded Memory shell works with NetWare v2.15 and later. All the shell configuration (NET.CFG) parameters work with the NetWare Expanded Memory shell.EMSNETX.EXE can be used only with DOS 3.0 and later. Do not use the expanded memory shell on a nondedicated file server. ID="FM30008"XMSNETX.EXE (NetWare Extended Memory Shell)Use XMSNETX to load the network shell into extended memory, view the shell version, or unload the shell. This shell is for use with DOS 3.0 through 6.0.PrerequsitesYou must load the following NetWare shell files before loading the XMSNETX.EXE file:LSL.COMnetwork board driver.COM (NE2000.COM)IPXODI.COMIf you are using dedicated IPX, you must load the IPX.COM file before loading the NETX.EXE file.IPX.COM is generated with the WSGEN.EXE utility. The WSGEN.EXE utility is not included with NetWare versions later than v3.11.Command Format  idxid="w229"book="_idx" docset="nw312" tidref="i7569"XMSNETX [/?] | [PS = server name] | [/U] | [/F] | [/C=(path\)filename.ext]idxid="w230"book="_idx" docset="nw312" tidref="i4916"Command Options[/?]Displays help screens.[PS = server name]Specifies a preferred server.[/C=(path\)filename.ext]Specifies a configuration file for XMSNETX to use. The default configuration file is NET.CFG.[/U]Unloads resident XMSNETX from memory. When you execute this option, a screen similar to the following appears:  You are being logged out of all servers . . .  Memory for resident shell has been released.  The NetWare shell has been unloaded.[/F]Forces the resident XMSNETX to unload. This option is useful for unloading XMSNETX when other programs are loaded after XMSNETX.Using this option may cause your system to fail if programs are still accessing XMSNETX.Conceptsidxid="w231"book="_idx" docset="nw312" tidref="i7569"Extended memory refers to memory above the 1MB range. Up to 15 MB of extended memory are addressable.idxid="w232"book="_idx" docset="nw312" tidref="i3802"The NetWare Extended Memory shell moves most of the shell out of conventional DOS memory and puts it in extended memory. This frees up 35 KB of conventional memory. The remaining 8 KB of the shell must remain in conventional memory to handle interrupts and some data.The Extended Memory shell requires the support of an XMS (Extended Memory Specification) v2.0 memory manager (or compatible), such as Microsoft's HIMEM.SYS. The memory manager makes the first 6 KB (beginning at the 1MB address) of extended memory directly available to any one DOS-based application.To install the NetWare Extended Memory shell, you need to Install a third-party extended memory managerCopy the NetWare Extended Memory shell file, XMSNETX.EXE, to the workstation boot diskInclude the filename XMSNETX.EXE in the AUTOEXEC.BAT fileBecause this shell operates in extended memory, larger applications can run in the conventional memory space. This approach is faster than disk swapping and overlays. The NetWare Extended Memory shell works with all versions of NetWare v2.15 and later.All the shell configuration (NET.CFG) parameters work with the NetWare extended memory shell except Entry Stack Size.XMSNETX.EXE can be used only with DOS 3.0 and later. The current VDISK.SYS from IBM is not compatible with HIMEM.SYS, so do not use the extended memory shell with VDISK.SYS. Do not use the extended memory shell on a nondedicated file server. Only one DOS application can be loaded in the HMA. If you are using the DOS 5 DOS=HIGH command, you cannot load XMSNETX.EXE.This shell requires a high degree of IBM compatibility. Depending on the brand of IBM compatible you are using, you may experience keyboard sluggishness or other hardware problems.