<!DOCTYPE BOOK SYSTEM "/dtd/docbook.dtd" [
<!ENTITY % localentities SYSTEM "/dtd/novlents">
%localentities;
]>

<BOOK><TITLE>Installation and Administration Guide</TITLE>
<BOOKINFO>
<BOOKBIBLIO><TITLE>Installation and Administration Guide</TITLE>
<AUTHORGROUP><CORPAUTHOR>Novell, Inc.</CORPAUTHOR></AUTHORGROUP></BOOKBIBLIO>
<LEGALNOTICE>
<TITLE>Disclaimer</TITLE>

<PARA>Novell, 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.</PARA>

<PARA>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.</PARA>

</LEGALNOTICE>

<LEGALNOTICE>
<TITLE>Trademarks</TITLE>

<PARA>NetWare, Novell, the NetWare Logotype,
and the N design are registered trademarks of Novell, Inc.</PARA>

<PARA>GroupWise, Internetwork Packet Exchange, IPX, Link Support Layer, LSL, NetWare 3, NetWare 4, NetWare Client, NetWare Connect, NetWare Directory Services, NDS, NetWare DOS Requester, NDR, NetWare/IP, NetWare Loadable Module, NLM, NetWare Mobile, NetWare Requester, NE/2, NE/2-32, NE1000, NE1500T, NE2000, NE2100, NE3200, Novell DOS, NTR2000, Open Data-Link Interface, ODI, RX-Net, RX-Net/2, Sequenced Packet Exchange, Virtual Loadable Module, and VLM are trademarks of Novell, Inc.</PARA>

<PARA>386 is a trademark of Intel Corporation.</PARA>

<PARA>AT&amp;T is a registered trademark of AT&amp;T.</PARA>

<PARA>DynaText is a registered trademark of Electronic Book Technologies.</PARA>

<PARA>Hayes and V-series are registered trademarks of Hayes Microcomputer Products, Inc.</PARA>

<PARA>IBM is a registered trademark of International Business Machines Corporation.</PARA>

<PARA>Intel is a registered trademark of Intel Corporation.</PARA>

<PARA>MCI is a registered trademark of MCI Communications Corporation.</PARA>

<PARA>Microsoft, MS-DOS and Windows are registered trademarks of Microsoft
Corporation.</PARA>

<PARA>PostScript is a registered trademark of Adobe Systems
Incorporated.</PARA>

<PARA>Smartmodem 2400 is a trademark of Hayes Microcomputer Products,
Inc.</PARA>

<PARA>Sprint is a registered trademark of Borland International, Inc.</PARA>

<PARA>Stacker is a registered trademark of Stac Electronics.</PARA>

<PARA>All other trademarks, service marks, certification marks, and
collective marks --- registered or not --- are the property of their
respective owners.</PARA>

</LEGALNOTICE>

<LEGALNOTICE>
<TITLE>Copyright Notices</TITLE>

<PARA>©Copyright 1983-1995 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.</PARA>

<PARA>
<SIMPLELIST>
<MEMBER>Novell, Inc.</MEMBER>
<MEMBER>122 East 1700 South</MEMBER>
<MEMBER>Provo, UT 84606</MEMBER>
<MEMBER>U.S.A.</MEMBER>
</SIMPLELIST>
</PARA>

</LEGALNOTICE>
</BOOKINFO>
<PREFACE><TITLE><BEGINPAGE PAGENUM=5 ID="BP1">About This Guide</TITLE><PARA>NetWare® Mobile(tm) is networking software that allows mobile users to connect to the network from anywhere in the world and work as they would in the office, even when a physical connection to the network is impossible.</PARA>
<PARA>This manual is intended for the network administrator or the person responsible for installing and configuring NetWare Mobile. It includes the following:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA><IXREF idref="FM27522">Chapter 1 "Installing NetWare Mobile"</IXREF></PARA>
<PARA>This chapter explains how to install the NetWare Mobile software and provides a summary of what happens during the installation and initial configuration process.</PARA>
</LISTITEM>
<LISTITEM><PARA><IXREF idref="FM34715">Chapter 2 "Setting Up the Mobile Network"</IXREF></PARA>
<PARA>This chapter provides information about how NetWare Mobile handles mobile data. Read this information before you run the Mobile File Assistant for the first time after installation to set up the user's mobile network.</PARA>
</LISTITEM>
<LISTITEM><PARA><IXREF idref="FM37555">Chapter 3 "Advanced Location Configuration"</IXREF></PARA>
<PARA>This chapter describes how to edit configuration files for a number of special requirements and situations.</PARA>
</LISTITEM>
<LISTITEM><PARA><IXREF idref="FM24049">Chapter 4 "Logging in to NetWare"</IXREF></PARA>
<PARA>This chapter provides information about logging in to NetWare servers when running a NetWare Mobile client. In particular, network administrators may want to read the information about login scripts, if they need to create or debug scripts for mobile users.</PARA>
<BEGINPAGE PAGENUM=5 ID="BP2"><BEGINPAGE PAGENUM=6></LISTITEM>
<LISTITEM><PARA><IXREF idref="FM22163">Chapter 5 "Managing Mobile NDS Objects"</IXREF></PARA>
<PARA>This chapter explains how to create and manage Dial-in Service and Mobile File Group objects.</PARA>
</LISTITEM>
<LISTITEM><PARA><IXREF idref="FM15821">Chapter 6 "Troubleshooting"</IXREF></PARA>
<PARA>This chapter contains information about some common situations that may cause problems for the NetWare Mobile user and what to do about them.</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>For a general introduction to the product, both administrators and mobile users should read the <CITETITLE>NetWare Mobile User's Overview</CITETITLE>. After product installation, users should run the quick tour and use the extensive online help for detailed information about NetWare Mobile and its features.</PARA>
<PARA></PARA>
</PREFACE>
<CHAPTER LABEL="1"><TITLE><BEGINPAGE PAGENUM=1 ID="BP3"><XMARK id="FM27522">Installing NetWare Mobile</TITLE><PARA>
This 
chapter explains how to install the NetWare® Mobile(tm) software and provides a summary of what happens during the installation and initial configuration process.</PARA>
<PARA>You install the NetWare Mobile client software by running the Setup program on each mobile computer that will be using the network. You can run Setup from the installation diskettes or from a network server. Setup copies the necessary software to specified directories on the computer's hard disk and makes changes to existing configuration files, such as CONFIG.SYS and WIN.INI. The Setup program also allows you to configure the current networking environment for the mobile computer, and to configure environments in other locations where the mobile user will be working in future.</PARA>
<PARA>In addition to the client software, NetWare Mobile includes a "synchronization accelerator" that can be installed on a network server to significantly improve mobile data synchronization speed over a slow dial-in link. You can also install an electronic version of the NetWare Mobile documentation set on the server. This chapter includes information about how to install the Accelerator and the online manuals. It also includes information about pre-installing the client software on a server so that NetWare Mobile can be installed from the network.</PARA>
<SECT1><TITLE>Preparing for Installation</TITLE><PARA>
Before you run Setup on a mobile client computer to install NetWare Mobile, read the following sections. They represent a "checklist" of the information you need to know before copying the NetWare Mobile software to the computer's hard disk and configuring it correctly to use the network at the current (and other) locations.</PARA>
<BEGINPAGE PAGENUM=1 ID="BP4"><BEGINPAGE PAGENUM=2><SECT2><TITLE>Client Hardware Requirements</TITLE><PARA>
In order to 
use NetWare Mobile, a client computer must be an IBM* PC (or compatible) with a 386* (or later) processor with at least 4 MB of RAM. The hard drive must have a minimum of 12 MB of available disk space.</PARA>
<PARA>To make a physical connection to the network, you must also have a network adapter card (with the appropriate software and cabling) or a modem.</PARA>
</SECT2>
<SECT2><TITLE>Client Software Requirements</TITLE><PARA>
The 
following software must be running on a client computer before you can install NetWare Mobile:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Novell® DOS(tm) 7, MS-DOS* 5 (or later), or PC-DOS 5 (or later)</PARA>
</LISTITEM>
<LISTITEM><PARA>Windows* 3.10 (or later) or Windows for Workgroups 3.11 running in 386 Enhanced mode.</PARA>
<NOTE><PARA>If you intend to use NetWare Mobile with Windows 95, make sure you read the <CITETITLE>NetWare Mobile Release Notes</CITETITLE>.</PARA>
</NOTE>
</LISTITEM>
</ITEMIZEDLIST>
</SECT2>
<SECT2><TITLE>Network Requirements</TITLE><PARA>
NetWare 
3.11, 3.12, 4.0x, 
or 4.1 must be running on a network server before it can support NetWare Mobile clients.</PARA>
<NOTE><PARA>NetWare administration support for NetWare Mobile requires NetWare 4.1.</PARA>
</NOTE>
<PARA>NetWare servers which support dial-in connections must be running one of the following types of dial-in service:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>NetWare Connect(tm) 2.0</PARA>
</LISTITEM>
<LISTITEM><PARA>Shiva PPP version 3.5 (or later)</PARA>
</LISTITEM>
<LISTITEM><PARA>Generic PPP.</PARA>
<BEGINPAGE PAGENUM=3 ID="BP5"></LISTITEM>
</ITEMIZEDLIST>
</SECT2>
<SECT2><TITLE>Product Serial Number</TITLE><PARA>
NetWare Mobile Setup will require you to register the product using the serial number. Refer to the product registration card or the label on the first installation diskette for the serial number of your copy of NetWare Mobile.</PARA>
</SECT2>
<SECT2><TITLE>Installing the Quick Tour</TITLE><PARA>
Setup 
will ask 
whether or not you want to install the quick tour, which is an optional component of NetWare Mobile. The quick tour provides an overview of the product and its features, using text and graphics. </PARA>
<PARA>Be aware that, for performance reasons, a 486 computer with 8 MB of RAM is the recommended minimum requirement for running the quick tour. If you are installing on a 4 MB computer, however, make sure that you configure Windows to use a permanent swap file.</PARA>
<PARA>You will be able to uninstall the quick tour after using it by choosing the Uninstall Quick Tour icon from the NetWare Mobile program group in Windows.</PARA>
</SECT2>
<SECT2><TITLE>Destination Directories</TITLE><PARA>
Setup will ask you to specify destination directories for the NetWare Mobile software.</PARA>
<SECT3><TITLE>NetWare Client</TITLE><PARA>The Novell VLM(tm) NetWare Client(tm) for DOS and Windows is installed as part of NetWare Mobile.</PARA>
<PARA>By default, Setup installs this client software to 
C:\NWCLIENT. You are recommended to accept this default when prompted to specify the destination directory. If a NetWare client is already installed on the computer, existing 
NET.
CFG parameters will be used. Be aware, however, that all existing VLM files in the NWCLIENT directory will be overwritten; if you want to save existing client software, specify a different destination directory for the NetWare Mobile client.</PARA>
<BEGINPAGE PAGENUM=3 ID="BP6"><BEGINPAGE PAGENUM=4><PARA>Before making any modifications, Setup saves the existing NET.CFG and 
STARTNET.BAT 
files in C:\NWCLIENT (if they exist) as NET.<REPLACEABLE>nnn</REPLACEABLE> and STARTNET.<REPLACEABLE>nnn</REPLACEABLE>, where <REPLACEABLE>nnn</REPLACEABLE> is 000 or the first number not already used.</PARA>
</SECT3>
<SECT3><TITLE>Mobile Programs</TITLE><PARA>
By default, Setup sets C:\NWMOBILE as the destination for the mobile components of NetWare Mobile. The C:\NWMOBILE directory is automatically created during installation. You can specify a different directory, if you wish.</PARA>
</SECT3>
</SECT2>
<SECT2><TITLE>Storing Replicated Data</TITLE><PARA>
If there is more than one drive on the computer's hard disk, Setup will ask you to specify the 
drive that you want to use for storing the files and directories you replicate from network servers. Before deciding which drive to use, consider the following points:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>The amount of network data that you can replicate on to a client computer is limited by the amount of disk space available. Therefore, the drive must contain sufficient space for all the data you want to replicate.</PARA>
</LISTITEM>
<LISTITEM><PARA>A drive must be compressed <EMPHASIS>before</EMPHASIS> you replicate data on to it, if the drive is going to be compressed at all using a disk compression program such as Stacker*.</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>
Setup automatically creates a hidden directory called DNW in the root of the specified hard disk drive for storing replicated data. For more information, refer to <IXREF idref="FM34715">Chapter 2 "Setting Up the Mobile Network"</IXREF>.</PARA>
<BEGINPAGE PAGENUM=4 ID="BP7"><BEGINPAGE PAGENUM=5></SECT2>
<SECT2><TITLE>Configuring Network Devices</TITLE><PARA>
For each location profile that you create during Setup, you will need to specify information about the network device that you want to use to work online at the location.</PARA>
<SECT3><TITLE>LAN Connection</TITLE><PARA>
If you want to use a LAN connection to the network, a network adapter must be installed inside the client computer or inserted into a PC Card slot attached to the computer. For information about installing a network board or PC Card hardware, refer to the manfacturer's instructions.</PARA>
<SECT4><TITLE>Adapter Type</TITLE><PARA>
Make sure you know the manufacturer and model of your network adapter before installing NetWare Mobile. This software supports the majority of network adapters; make sure, however, that the adapter you use is supported by NetWare or includes a driver that is compatible with NetWare.</PARA>
<PARA>If your adapter is already installed and the appropriate drivers loaded before you run Setup, the program will automatically recognize its type and you will be able to select it from a list of installed adapters.</PARA>
<PARA>If you want to install a new adapter during Setup, you will be able to select from a list of most commonly-used adapters. If you want to know whether or not your adapter will appear in the list now, refer to <IXREF idref="FM27220">Appendix A "Supported Adapters and Modems"</IXREF>. If your adapter does not appear in the list, you will need a driver diskette in order to install it. You will also need an INS file for the driver. If an INS file is not included with your LAN driver, you will need to create one; refer to <IXREF idref="FM18631">Appendix B "Creating an INS File for a LAN Driver"</IXREF>.</PARA>
<BEGINPAGE PAGENUM=5 ID="BP8"><BEGINPAGE PAGENUM=6></SECT4>
<SECT4><TITLE>Adapter Settings</TITLE><PARA>
When you install an adapter, you may need to enable or configure it. Some network boards require you to configure them by setting switches manually, before fixing the card inside the computer. Many PC Cards include software that you must run to enable PCMCIA Card and Socket Services, after the hardware is physically installed. Refer to the documentation that came with the adapter to determine what you need to do to enable or configure it.</PARA>
<PARA>The NetWare Mobile Setup program asks you for information about an adapter so that the software can be configured correctly to use it. Therefore, it is important that you keep a record of the values assigned to adapter settings. Although the information you need to supply in Setup depends on the type of adapter you are using, configuring most adapters includes setting the following:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Base I/O Port Address</PARA>
<PARA>Each hardware device in a computer must have a unique base I/O port address. For information about the address to use for your network adapter, refer to the manufacturer's instructions.</PARA>
</LISTITEM>
<LISTITEM><PARA>Hardware Interrupt</PARA>
</LISTITEM>
<LISTITEM><PARA>Media Frame Type</PARA>
<PARA>All client computers and servers using the same network address must use the same frame type. For information about the frame types supported by most network adapters, refer to the <CITETITLE>NetWare 3.12 Workstation for DOS and MS Windows</CITETITLE> manual or the <CITETITLE>NetWare 4.1 Client for DOS and Windows Technical Reference </CITETITLE>manual.</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>For settings unique to your particular type of network adapter, refer to the manufacturer's documentation.</PARA>
<BEGINPAGE PAGENUM=6 ID="BP9"><BEGINPAGE PAGENUM=7></SECT4>
</SECT3>
<SECT3><TITLE>Modem Connection</TITLE><PARA>
If you are going to connect to the network by dialing in over telephone lines using a modem, your modem must be correctly installed and (if necessary) configured. For information about installing a modem, refer to the manufacturer's instructions. In most cases, you will not need to perform any configuration steps before running NetWare Mobile Setup. Some modems, however, have switches which may need to be set.</PARA>
<SECT4><TITLE>Modem Type</TITLE><PARA>
Make sure you know the manufacturer and model of your modem before installing NetWare Mobile. During Setup, you will be able to select your modem from a list of supported modems. If the modem you are using does not appear in the list, you can select the GENERIC modem type; the GENERIC settings will work for most Hayes*-compatible modems.</PARA>
<PARA>If you find that the GENERIC settings do not work, you may need to add your modem to NetWare Mobile's modem database by editing the appropriate .INI files. For information about how to do this, refer to <IXREF idref="FM37555">Chapter 3 "Advanced Location Configuration"</IXREF>. For a list of the modem types that the database already includes, refer to <IXREF idref="FM27220">Appendix A "Supported Adapters and Modems"</IXREF>.</PARA>
<PARA>If you are using a PCMCIA card that requires Card and Socket Services, you may need to run an enabler program. Refer to the documentation for your PC Card.</PARA>
</SECT4>
<SECT4><TITLE>COM Port</TITLE><PARA>Before running Setup and creating a dial-in location profile, also make sure you know which communication port is being used by your modem or its software.</PARA>
<BEGINPAGE PAGENUM=7 ID="BP10"><BEGINPAGE PAGENUM=8></SECT4>
</SECT3>
</SECT2>
<SECT2><TITLE>Logging in to NetWare</TITLE><PARA>
Each 
location profile you create includes information about how you want to log in to NetWare. Even when you create a profile for working offline, you need to log in to NetWare in order to use replicated network data.</PARA>
<PARA>Setup will ask you for information about logging in to NetWare. NetWare Mobile is then able to configure the location so that logging in to the network is as transparent as possible.</PARA>
<PARA>Before you install NetWare Mobile, the following must already exist on the NetWare network for the user of the client computer:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>A User object or user account</PARA>
</LISTITEM>
<LISTITEM><PARA>A home directory.</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>For information about creating and managing NetWare Directory Services(tm) (NDS(tm)) objects, refer to the <CITETITLE>NetWare 4.1 Supervising the Network</CITETITLE> manual. If you are using NetWare 3.11 or 3.12, refer to the <CITETITLE>NetWare 3.12 Installation and Upgrade</CITETITLE> manual for information about creating user accounts.</PARA>
<PARA>Depending on whether you are going to be logging in to NetWare 3(tm) or NetWare 4(tm) servers, and how you want to log in, make sure you know the following before installing NetWare Mobile and creating a location profile:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Preferred Server</PARA>
<PARA>You can specify a preferred server for the location during Setup. This is the NetWare server where your user information is located. If you want to log in to a particular NetWare server, or if you are going to log in to NetWare 3.11 or 3.12, make sure you know the name of your preferred server before running Setup.</PARA>
<BEGINPAGE PAGENUM=8 ID="BP11"><BEGINPAGE PAGENUM=9></LISTITEM>
<LISTITEM><PARA>Preferred Tree</PARA>
<PARA>If you are logging in to NetWare 4.x, you can specify a preferred NDS tree.</PARA>
<NOTE><PARA>This will override any preferred server you specify at the same time.</PARA>
<PARA>The preferred tree directs NetWare Mobile to the tree where your name context is set; specifying a tree speeds up the login process because only the specified tree is searched for the name context.</PARA>
</NOTE>
</LISTITEM>
<LISTITEM><PARA>Context</PARA>
<PARA>If you are logging in to NetWare 4.x, you can simplify the login process most effectively by specifying your name context <EMPHASIS>and</EMPHASIS> the preferred tree.</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>If NetWare client software is already installed on the computer before you run NetWare Mobile Setup and login information already exists in NET.CFG, the existing values are shown as the defaults in Setup.</PARA>
<PARA>NetWare Mobile will run the login scripts defined for a server or NDS tree, if they exist. For information about login scripts, refer to <IXREF idref="FM24049">Chapter 4 "Logging in to NetWare"</IXREF>.</PARA>
</SECT2>
<SECT2><TITLE>Configuring TCP/IP</TITLE><PARA>
If you 
want to use the Internet or any other service that requires TCP/IP at a location, you can enable TCP/IP when you create the location profile during Setup.</PARA>
<NOTE><PARA>You only need to configure TCP/IP in Setup if you are defining a location that uses a LAN adapter; if you are defining a dial-in location, IP address information is part of the dial-in service, which you can only define after NetWare Mobile is installed and running on the client computer.</PARA>
</NOTE>
<PARA>If the server you log in to at the location is not an IP address server, you will also need to provide the following IP address information:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>IP address</PARA>
</LISTITEM>
<LISTITEM><PARA>Subnet mask</PARA>
<PARA>This is required if your network is subnetted.</PARA>
<BEGINPAGE PAGENUM=10 ID="BP12"></LISTITEM>
<LISTITEM><PARA>Domain name</PARA>
<PARA>This is required if your network uses a Domain SAP Server (DSS).</PARA>
</LISTITEM>
<LISTITEM><PARA>IP addresses for DSS</PARA>
<PARA>At least one address is required if you are using NetWare/IP(tm).</PARA>
</LISTITEM>
<LISTITEM><PARA>IP addresses for routing servers</PARA>
<PARA>You can specify up to three IP addresses, if your network uses routing servers. </PARA>
<NOTE><PARA>If the computer on which you are going to install NetWare Mobile is already running NetWare client software and is configured to use TCP/IP, IP address information may already exist in NET.CFG.</PARA>
</NOTE>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>For detailed information about TCP/IP and related parameters, refer to the following NetWare manuals:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA><CITETITLE>NetWare 3.12 TCP/IP Transport Supervisor's Guide</CITETITLE></PARA>
</LISTITEM>
<LISTITEM><PARA><CITETITLE>NetWare 4.1 Advanced Protocol Configuration and Management Guide</CITETITLE></PARA>
</LISTITEM>
<LISTITEM><PARA><CITETITLE>NetWare 4.1 TCP/IP Reference</CITETITLE></PARA>
</LISTITEM>
</ITEMIZEDLIST>
</SECT2>
</SECT1>
<SECT1><TITLE>Preparing to Install from a Network Directory</TITLE><PARA>
If the computers on which you are going to install NetWare Mobile are already running NetWare client software, the quickest and easiest way to install the new software (if you have a multi-licence version of the product) is from a network directory.</PARA>
<PARA>Before you can do this, however, you need to pre-install the NetWare Mobile client software on an existing NetWare server using the NetWare installation program.</PARA>
<PARA>
The NetWare INSTALL program provides menus and prompts to guide you through installing product components, using default directory structures.</PARA>
<BEGINPAGE PAGENUM=10 ID="BP13"><BEGINPAGE PAGENUM=11><PARA>Do the following:</PARA>
<PROCEDURE><STEP><PARA>Insert the first NetWare Mobile installation diskette into a disk drive on the server or load the CD-ROM.</PARA>
</STEP>
<STEP><PARA>At the console prompt, enter the following:
<LITERALLAYOUT><USERINPUT>LOAD INSTALL
</USERINPUT></LITERALLAYOUT>
</PARA>
</STEP>
<STEP><PARA>From "Installation Options", choose 
<INTERFACE class=menuitem>Product options (other installation items)</INTERFACE>.
</PARA>
</STEP>
<STEP><PARA>From "Other Installation Actions", choose 
<INTERFACE class=menuitem>Install a product not listed</INTERFACE>.
</PARA>
<PARA>Alternatively, you can choose "View/Configure/Remove installed products" and then press 
<KEYCAP>&lt;Insert></KEYCAP>.
</PARA>
</STEP>
<STEP><PARA>If necessary, press 
<KEYCAP>&lt;F3></KEYCAP> and enter the path to the NetWare Mobile installation diskette or the CD-ROM.
</PARA>
<PARA>By default, the path from which to install the software is A:\.
</PARA>
<PARA>A list of NetWare Mobile installation options will appear.
</PARA>
</STEP>
<STEP><PARA>From the list of NetWare Mobile installation options, select "Pre-install NetWare Mobile on Server" and then press 
<KEYCAP>&lt;F10></KEYCAP> to accept the marked option.
</PARA>
<PARA>The copying process requires a temporary location for NetWare Mobile which by default is SYS:\SYSTEM\TMP. If you want to specify a different temporary destination, do so when prompted.
</PARA>
</STEP>
<STEP><PARA>When prompted, specify a destination directory for the NetWare Mobile files.
</PARA>
<PARA>By default, the NetWare Mobile files will be installed in SYS:\SYSTEM\NWMOBILE.
<BEGINPAGE PAGENUM=11 ID="BP14"><BEGINPAGE PAGENUM=12></PARA>
</STEP>
</PROCEDURE>
</SECT1>
<SECT1><TITLE>Running Setup</TITLE><PARA>
To run Setup on the client computer, do either of the following:</PARA>
<SECT2><TITLE>To install from diskettes ...</TITLE><PROCEDURE><STEP><PARA>Start Windows.</PARA>
</STEP>
<STEP><PARA>Insert the first installation diskette into a disk drive.
</PARA>
</STEP>
<STEP><PARA>In Program Manager, choose 
<INTERFACE class=menuitem>Run...</INTERFACE> from the File menu.
</PARA>
</STEP>
<STEP><PARA>Enter the following, where 
<REPLACEABLE>d</REPLACEABLE> is the drive containing the diskette:
<LITERALLAYOUT><USERINPUT><REPLACEABLE>d</REPLACEABLE>:\SETUP
</USERINPUT></LITERALLAYOUT>
</PARA>
</STEP>
<STEP><PARA>Follow the instructions on the screen.
</PARA>
</STEP>
</PROCEDURE>
</SECT2>
<SECT2><TITLE>
To install from a network directory ...</TITLE><PROCEDURE><STEP><PARA>Log in to NetWare.</PARA>
</STEP>
<STEP><PARA>Start Windows.
</PARA>
</STEP>
<STEP><PARA>If you have not already done so, map a drive to the network directory containing the NetWare Mobile files.
</PARA>
</STEP>
<STEP><PARA>In Program Manager, choose 
<INTERFACE class=menuitem>Run...</INTERFACE> from the File menu.
</PARA>
</STEP>
<STEP><PARA>Enter the following, where 
<REPLACEABLE>path</REPLACEABLE> is the path to the network directory containing the NetWare Mobile files.
<LITERALLAYOUT><USERINPUT><REPLACEABLE>path</REPLACEABLE>\SETUP
</USERINPUT></LITERALLAYOUT>
</PARA>
</STEP>
<STEP><PARA>Follow the instructions on the screen.
<BEGINPAGE PAGENUM=12 ID="BP15"><BEGINPAGE PAGENUM=13></PARA>
</STEP>
</PROCEDURE>
</SECT2>
<SECT2><TITLE>Replacing Files in Setup</TITLE><PARA>
When Setup copies new files to the computer's hard disk, you may be prompted to specify whether or not you want to replace existing files. Be aware that if you choose not to replace files, your NetWare Mobile installation may not be successful.</PARA>
</SECT2>
<SECT2><TITLE>Getting Help in Setup</TITLE><PARA>
On any of the dialogs in Setup, you can get help information by choosing either the <KEYCAP>&lt;Help></KEYCAP> button or the <KEYCAP>&lt;F1></KEYCAP> key.</PARA>
</SECT2>
<SECT2><TITLE>Rebooting After Setup</TITLE><PARA>
When Setup is finished, you are prompted to reboot the client computer so that NetWare Mobile installation can take effect.</PARA>
<PARA>Because some files that Setup needs to modify or replace may be open in Windows when you run the program, the NetWare Mobile files are copied to temporary file names. When you reboot and AUTOEXEC.BAT is run, the files are renamed. This process only occurs once, when you install NetWare Mobile.</PARA>
</SECT2>
<SECT2><TITLE>Customizing Setup</TITLE><PARA>
As a network administrator, you may want to customize NetWare Mobile installation to suit particular user requirements. Do this by creating different versions of SETUP.INI.</PARA>
<PARA>You might, for example, want to reduce the number of questions that the user needs to answer during installation. You can force Setup to jump from registration information to information about the location, accepting default answers to all questions the program would have asked in between. Do this by editing the following section in SETUP.INI, setting the value to 1:</PARA>
<LITERALLAYOUT><USERINPUT>[Unattended]
Unattended=0
<BEGINPAGE PAGENUM=13 ID="BP16"><BEGINPAGE PAGENUM=14></USERINPUT></LITERALLAYOUT>
<PARA>You may also want to pre-define the user and product registration information or change the default destination directories for the NetWare Mobile program files. Do this by editing the following section in SETUP.INI:</PARA>
<LITERALLAYOUT><USERINPUT>[User Choices]
UserName=<REPLACEABLE>user_name</REPLACEABLE>
UserCompany=<REPLACEABLE>company_name</REPLACEABLE>
ProductSerialNo=<REPLACEABLE>n</REPLACEABLE>
DirMobile=C:\NWMOBILE
DirClient=C:\NWCLIENT
...
</USERINPUT></LITERALLAYOUT>
<SECT3><TITLE>Running a Customized Setup</TITLE><PARA>By default, the Setup program looks for SETUP.INI in the directory from which SETUP.EXE was loaded. The user can run a different SETUP.INI file by doing the following:</PARA>
<PROCEDURE><STEP><PARA>Start Windows.</PARA>
</STEP>
<STEP><PARA>In Program Manager, choose 
<INTERFACE class=menuitem>Run...</INTERFACE> from the File menu.
</PARA>
</STEP>
<STEP><PARA>Enter the following, where 
<REPLACEABLE>filespec</REPLACEABLE> is the path and filename of the customized .INI file to be used.
<LITERALLAYOUT><USERINPUT>SETUP /i:<REPLACEABLE>filespec</REPLACEABLE>
</USERINPUT></LITERALLAYOUT>
</PARA>
</STEP>
</PROCEDURE>
</SECT3>
</SECT2>
</SECT1>
<SECT1><TITLE><XMARK id="FM30213">What Happens During Installation</TITLE><PARA>When you install NetWare Mobile, the required destination directories are created (if they do not already exist) and the software is copied to those directories. In addition, various configuration files are created or modified.</PARA>
<PARA>Normally, you will not need to edit any of these configuration files. For information about situations where it may be necessary to do so, however, refer to <IXREF idref="FM37555">Chapter 3 "Advanced Location Configuration"</IXREF>.</PARA>
<BEGINPAGE PAGENUM=15 ID="BP17"><SECT2><TITLE>DOS Configuration Files</TITLE><PARA>
The following line is added to CONFIG.SYS, if required:</PARA>
<LITERALLAYOUT><USERINPUT>LASTDRIVE=Z
</USERINPUT></LITERALLAYOUT>
<PARA>Also, the following section is added:</PARA>
<LITERALLAYOUT><USERINPUT>[common]
DEVICE=C:\NWMOBILE\LOCATION.EXE
INSTALL=C:\NWMOBILE\DNWHELP.EXE
DEVICE=C:\NWMOBILE\MRUDRV.SYS
</USERINPUT></LITERALLAYOUT>
<PARA><USERINPUT>LOCATION.EXE</USERINPUT> is the location selection program and <USERINPUT>MRUDRV.SYS </USERINPUT>is the driver for the Mobile File Assistant's Most Recently Used Files feature. <USERINPUT>DNWHELP.EXE</USERINPUT> is a TSR that provides Windows 32-bit file system support for working offline. The [<USERINPUT>common</USERINPUT>] label specifies that the statements which follow are common to all locations. You can edit CONFIG.SYS to load devices on a location-dependent basis; refer to <IXREF idref="FM37555">Chapter 3 "Advanced Location Configuration"</IXREF>, for more information.</PARA>
<PARA>
The following line is added to AUTOEXEC.BAT to call STARTNET.BAT:</PARA>
<LITERALLAYOUT><USERINPUT>CALL C:\NWCLIENT\STARTNET.BAT
</USERINPUT></LITERALLAYOUT>
<PARA>The <USERINPUT>PATH</USERINPUT> statement in AUTOEXEC.BAT is changed to include the NWCLIENT and NWMOBILE directories.</PARA>
<PARA>If the computer is already running NetWare client software, Setup adds <USERINPUT>REM</USERINPUT> to the beginning of any existing network commands in AUTOEXEC.BAT.</PARA>
<PARA>Your old CONFIG.SYS and AUTOEXEC.BAT files are saved as CONFIG.000 and AUTOEXEC.000, if possible. If the .000 extension has already been used during a previous installation, .001 is used, then .002, and so on.</PARA>
<BEGINPAGE PAGENUM=15 ID="BP18"><BEGINPAGE PAGENUM=16></SECT2>
<SECT2><TITLE>Location Configuration Files</TITLE><PARA>
When you create at least one location profile during installation, a file called LOCATION.INI is created in C:\NWMOBILE\PROFILE.</PARA>
<PARA>The [<USERINPUT>Locations</USERINPUT>] section of LOCATION.INI specifies the names of your existing locations. For example:</PARA>
<LITERALLAYOUT><USERINPUT>[Locations]
Location1=in the office (LAN)
Location2=at home (modem)
</USERINPUT></LITERALLAYOUT>
<PARA>The [<USERINPUT>CurrentLocation</USERINPUT>] section specifies the ID number of your current location. For example:</PARA>
<LITERALLAYOUT><USERINPUT>[CurrentLocation]
LocationID=1
</USERINPUT></LITERALLAYOUT>
<PARA>During installation, a subdirectory in C:\NWMOBILE\PROFILE is created for each location to contain the "location profile". The name of the profile subdirectory is LOC_<REPLACEABLE>n</REPLACEABLE>, where <REPLACEABLE>n</REPLACEABLE> is the location ID number.</PARA>
<PARA>C:\NWMOBILE\PROFILE\LOC_<REPLACEABLE>n</REPLACEABLE> contains the following configuration files: PROFILE.INI, NET.CFG, STARTNET.BAT, RESOLV.CFG, NOTES.TXT, and STARTUP.GRP.</PARA>
<PARA>If NET.CFG, STARTNET.BAT, or RESOLV.CFG exist before you install NetWare Mobile, they are stored in C:\NWMOBILE\PROFILE\LOC_0 after installation.</PARA>
<SECT3><TITLE>PROFILE.INI</TITLE><PARA>
Most of the 
information you provide in Setup when creating a location profile is defined in a PROFILE.INI file. NetWare Mobile uses the values from PROFILE.INI to configure a location when you choose it from the Location Selection dialog at startup time, after running CONFIG.SYS.</PARA>
<PARA>You should not need to edit PROFILE.INI. All values can be set through Setup or, after installation, by changing location properties through the NetWare Mobile Locations program.</PARA>
<BEGINPAGE PAGENUM=16 ID="BP19"><BEGINPAGE PAGENUM=17><NOTE><PARA>If you need to configure network device drivers or protocols by adding command line parameters, you should edit the 
STARTNET.BAT 
file for the location rather than the [<USERINPUT>STARTNET</USERINPUT>] section of PROFILE.INI. Refer to <IXREF idref="FM37555">Chapter 3 "Advanced Location Configuration"</IXREF>, for more information.</PARA>
</NOTE>
<PARA>The following is a PROFILE.INI file for an online location which has been configured to use a LAN connection.</PARA>
<LITERALLAYOUT><USERINPUT>[General]
Connection=1
DefaultPrinter=HP Laserjet PostScript,pscript,LPT1:
</USERINPUT></LITERALLAYOUT>
<LITERALLAYOUT><USERINPUT>[LAN Adapter]
Type=Novell NE2000
</USERINPUT></LITERALLAYOUT>
<LITERALLAYOUT><USERINPUT>[Modem]
Manufacturer=
Model=
CommunicationsPort=COM1
OptimumSpeed=0
MaximumSpeed=2400
Compression=0
FlowControl=2
ErrorCorrection=1
Speaker=1
ExtraInitialization=
</USERINPUT></LITERALLAYOUT>
<LITERALLAYOUT><USERINPUT>[Protocols]
UseTCPIP=0
UseNetWare=1
NetWare=0
</USERINPUT></LITERALLAYOUT>
<LITERALLAYOUT><USERINPUT>[NetWare]
DialOnLine=0
Username=jsmith
LoginAtStartup=1
</USERINPUT></LITERALLAYOUT>
<LITERALLAYOUT><USERINPUT>[Dialing]
Country=United States,United States
Area=
DialbackNumber=
<BEGINPAGE PAGENUM=18 ID="BP20">OutsideLine=No
CallingCard=
DefaultDialInService=0,0
DialType=0
CallWaitingPresent=0
TurnOffCallWaiting=
WaitForDialTone=1
</USERINPUT></LITERALLAYOUT>
<LITERALLAYOUT><USERINPUT>[Synchronization]
AtLogin=1
AtLogout=1
Periodically=0
Interval=
PromptBeforeStart=1
PromptAfterConflict=1
HideProgress=0
IgnoreOfflineDeletes=0
</USERINPUT></LITERALLAYOUT>
<LITERALLAYOUT><USERINPUT>[STARTNET]
LSL=C:\NWCLIENT\LSL.COM
NESL=C:\NWCLIENT\NE2000
Driver0=
Driver1=C:\NWCLIENT\NE2000
Driver2=
Protocol1=C:\NWCLIENT\IPXODI.COM
Protocol2=
Redir=C:\NWCLIENT\VLM.EXE /C=C:\NWCLIENT\NET.CFG
</USERINPUT></LITERALLAYOUT>
<LITERALLAYOUT><USERINPUT>[Permanent]
<BEGINPAGE PAGENUM=18 ID="BP21"><BEGINPAGE PAGENUM=19></USERINPUT></LITERALLAYOUT>
</SECT3>
<SECT3><TITLE>NET.CFG</TITLE><PARA>
A 
NET.CFG file is created for each location profile you create.</PARA>
<PARA>The Link driver section of the NET.CFG file configures the LAN adapter you will be using at the location. You provide this information in Setup when you create the location profile and specify adapter settings.</PARA>
<PARA>The following, for example, is the Link driver information for a Novell NE2000(tm) Ethernet adapter:</PARA>
<LITERALLAYOUT><USERINPUT>Link driver NE2000
FRAME Ethernet_802.2
FRAME Ethernet_II
INT 3
PORT 300
Protocol IPX E0 Ethernet_802.2
</USERINPUT></LITERALLAYOUT>
<PARA>The NetWare DOS Requester(tm) section configures the way in which your client software interacts with the network. You provide this information when you create the location profile and specify the way in which you want to log in to NetWare.</PARA>
<PARA>The following is a sample NetWare DOS Requester section from NET.CFG:</PARA>
<LITERALLAYOUT><USERINPUT>NetWare DOS Requester
FIRST NETWORK DRIVE = F
NETWARE PROTOCOL = NDS,BIND
Preferred Server US-MKTG
Preferred Tree BRANCH
Name Context "domestic.sales.branch"
VLM = AUTO.VLM
<BEGINPAGE PAGENUM=19 ID="BP22"><BEGINPAGE PAGENUM=20></USERINPUT></LITERALLAYOUT>
</SECT3>
<SECT3><TITLE>STARTNET.BAT</TITLE><PARA>
A STARTNET.BAT 
file is created for each location profile you create.</PARA>
<PARA>STARTNET.BAT sets the preferred language, adds the NWMOBILE directory to the path, loads the NetWare client software, and loads the network drivers configured for the location.</PARA>
<NOTE><PARA>To allow location-dependent loading of drivers and protocols, STARTNET.BAT contains keywords to represent drivers rather than the driver names themselves. The values for the keywords are defined in the PROFILE.INI file for each location. For information about adding command line parameters to drivers, refer to <IXREF idref="FM37555">Chapter 3 "Advanced Location Configuration"</IXREF>.</PARA>
</NOTE>
<PARA>The following is a sample STARTNET.BAT:</PARA>
<LITERALLAYOUT><USERINPUT>SET NWLANGUAGE=ENGLISH
C:\NWMOBILE\ISINPATH C:\NWMOBILE
if errorlevel 1 goto skippath
PATH=C:\NWMOBILE;%PATH%
:skippath
C:
CD C:\NWCLIENT
C:\NWCLIENT\LOCLOAD LSL
C:\NWCLIENT\LOCLOAD NESL
C:\NWMOBILE\LOCLOAD DRIVER1
C:\NWMOBILE\LOCLOAD DRIVER2
C:\NWMOBILE\LOCLOAD PROTOCOL1
C:\NWMOBILE\LOCLOAD PROTOCOL2
C:\NWMOBILE\LOCLOAD REDIR
CD \
<BEGINPAGE PAGENUM=20 ID="BP23"><BEGINPAGE PAGENUM=21></USERINPUT></LITERALLAYOUT>
</SECT3>
</SECT2>
<SECT2><TITLE>Windows Configuration Files</TITLE><PARA>
When you install NetWare Mobile, Setup makes changes to the following Windows configuration files: SYSTEM.INI, WIN.INI, WINFILE.INI, PROGMAN.INI, and NWADMIN.INI. It also creates the NWMOBILE.INI and NETWARE.INI files in the WINDOWS directory.</PARA>
<SECT3><TITLE>SYSTEM.INI</TITLE><PARA>
In the [<USERINPUT>boot</USERINPUT>] section, Setup makes the following change to the <USERINPUT>network.drv=</USERINPUT> line:</PARA>
<LITERALLAYOUT><USERINPUT>network.drv=netware.drv
</USERINPUT></LITERALLAYOUT>
<PARA>In the [<USERINPUT>boot description</USERINPUT>] section, Setup makes the following change to the <USERINPUT>network.drv=</USERINPUT> line:</PARA>
<LITERALLAYOUT><USERINPUT>network.drv=Novell NetWare Mobile 1.0
</USERINPUT></LITERALLAYOUT>
<PARA>In the [<USERINPUT>386Enh</USERINPUT>] section, the <USERINPUT>network=</USERINPUT> line is changed as follows:</PARA>
<LITERALLAYOUT><USERINPUT>network=*vnetbios,vnetware.386,vipx.386
</USERINPUT></LITERALLAYOUT>
<PARA>The <USERINPUT>device=</USERINPUT> lines to load <USERINPUT>DNWCRYPT.386</USERINPUT> and <USERINPUT>DNWFS.386</USERINPUT> are added to the [<USERINPUT>386Enh</USERINPUT>] section and a [<USERINPUT>DNWNP</USERINPUT>] section is added to the file. For information about these changes, refer to <IXREF idref="FM34715">Chapter 2 "Setting Up the Mobile Network"</IXREF>.</PARA>
<PARA>Your old SYSTEM.INI file is saved as SYSTEM.000, if possible. If the .000 extension has already been used during a previous installation, .001 is used, then .002, and so on.</PARA>
</SECT3>
<SECT3><TITLE>WIN.INI</TITLE><PARA>
In the [<USERINPUT>windows</USERINPUT>] section, Setup makes the following change to the <USERINPUT>load=</USERINPUT> line so that the NetWare Mobile synchronization software runs automatically whenever you start Windows:</PARA>
<LITERALLAYOUT><USERINPUT>load=NWPOPUP.EXE C:\NWMOBILE\SYNCMAN.EXE
</USERINPUT></LITERALLAYOUT>
<PARA>You old WIN.INI file is saved as WIN.000, if possible. If .000 has already been used, .001 is used, then .002, and so on.</PARA>
<BEGINPAGE PAGENUM=22 ID="BP24"></SECT3>
<SECT3><TITLE>WINFILE.INI</TITLE><PARA>
The following line is added to the [<USERINPUT>AddOns</USERINPUT>] section of WINFILE.INI:</PARA>
<LITERALLAYOUT><USERINPUT>NetWare Mobile Extension=C:\NWMOBILE\FMEXT.DLL
</USERINPUT></LITERALLAYOUT>
<PARA>FMEXT.DLL provides the NetWare Mobile support in Windows File Manager.</PARA>
</SECT3>
<SECT3><TITLE>PROGMAN.INI</TITLE><PARA>
Setup causes PROGMAN.EXE to create a new program group for NetWare Mobile and add the following line to PROGMAN.INI:</PARA>
<LITERALLAYOUT><USERINPUT>Group<REPLACEABLE>n</REPLACEABLE>=C:\WINDOWS\NWMOBILE.GRP
</USERINPUT></LITERALLAYOUT>
<PARA>The group number (<REPLACEABLE>n</REPLACEABLE>) will depend on how many groups are already created in the PROGMAN.INI file.</PARA>
</SECT3>
<SECT3><TITLE>NWADMIN.INI</TITLE><PARA>
Setup adds the following lines to the NWADMIN.INI file:</PARA>
<LITERALLAYOUT><USERINPUT>[Snapin Object DLLs]
SNAPINNWMOBILE1=C:\NWMOBILE\RAPADMIN.DLL
SNAPINNWMOBILE2=C:\NWMOBILE\MOBADMIN.DLL
</USERINPUT></LITERALLAYOUT>
<PARA>These lines load the "snapins" to support the additional NDS object classes for NetWare Mobile: Dial-in Service (<USERINPUT>RAPADMIN.DLL</USERINPUT>) and Mobile File Group (<USERINPUT>MOBADMIN.DLL</USERINPUT>).</PARA>
<PARA>For information about creating and managing Dial-in Service and Mobile File Group objects, refer to <IXREF idref="FM22163">Chapter 5 "Managing Mobile NDS Objects"</IXREF>.</PARA>
</SECT3>
<SECT3><TITLE>NWMOBILE.INI</TITLE><PARA>
Setup creates a file called NWMOBILE.INI, to define various NetWare Mobile program settings.</PARA>
<BEGINPAGE PAGENUM=23 ID="BP25"></SECT3>
<SECT3><TITLE>NETWARE.INI</TITLE><PARA>
The NETWARE.INI file, which defines settings for the NetWare User Tools interface, is also created in the WINDOWS directory. NetWare User Tools allows you to make network drive and printer connections.</PARA>
</SECT3>
</SECT2>
</SECT1>
<SECT1><TITLE>What Happens When NetWare Mobile Loads</TITLE><PARA>
Once NetWare Mobile is installed on the client computer, the software will load automatically every time the user arrives at a location and starts the computer. NetWare Mobile will prompt the user to choose the current location from a list of all the existing location profiles created during Setup or after installation.</PARA>
<PARA>The following series of events occurs after a NetWare Mobile client computer is started:</PARA>
<PROCEDURE><STEP><PARA>The user is asked to select the current location.</PARA>
</STEP>
<STEP><PARA>The location is configured.
</PARA>
<PARA>For information about how NetWare Mobile configures a location, refer to 
<IXREF idref="FM39151">"Configuring the Location (STARTNET.BAT and NET.CFG)" on page 25</IXREF>.
</PARA>
</STEP>
<STEP><PARA>The NetWare client software loads.
</PARA>
</STEP>
<STEP><PARA>The user starts Windows, if necessary.
</PARA>
<PARA>Windows may be started automatically in AUTOEXEC.BAT.
</PARA>
</STEP>
<STEP><PARA>The user is prompted to log in to NetWare.
</PARA>
<PARA>This assumes that the user has not already logged in from DOS.
</PARA>
<PARA>If the location is configured to use a modem and for automatic dialing at startup, the Dialer Assistant will appear and a dial-in connection will be made.
<BEGINPAGE PAGENUM=23 ID="BP26"><BEGINPAGE PAGENUM=24></PARA>
</STEP>
<STEP><PARA>The login script defined for the location is run.
</PARA>
<PARA>If the location is configured to use a network adapter or configured to use a modem (and dial in automatically at startup), the user is logged in online.
</PARA>
<PARA>If the location is configured for working offline or configured to use a modem (but not to dial in automatically at startup), the user is logged in offline.
</PARA>
</STEP>
<STEP><PARA>Any permanent drive and printer connections for the location are re-established.
</PARA>
</STEP>
<STEP><PARA>Any startup applications defined for the location are started.
</PARA>
</STEP>
</PROCEDURE>
<SECT2><TITLE>Automatic Location Selection</TITLE><PARA>
By default, the Location Selection dialog will remain on screen indefinitely, until the user selects a location from the list. You can specify a timeout value, however, so that the most recently used location (indicated on the Location Selection dialog by an asterisk) is automatically selected after the specified amount of time has passed.</PARA>
<PARA>
Do this by editing CONFIG.SYS. Add the /T:<REPLACEABLE>nn</REPLACEABLE> switch to the DEVICE statement that loads LOCATION.EXE, where <REPLACEABLE>nn</REPLACEABLE> is a number of seconds between 1 and 99.</PARA>
<PARA>The following statement, for example, causes the most recently used location to be selected automatically after 5 seconds:</PARA>
<LITERALLAYOUT><USERINPUT>DEVICE=C:\NWMOBILE\LOCATION.EXE /T:5
<BEGINPAGE PAGENUM=24 ID="BP27"><BEGINPAGE PAGENUM=25></USERINPUT></LITERALLAYOUT>
</SECT2>
<SECT2><TITLE><XMARK id="FM39151">Configuring the Location (STARTNET.BAT and NET.CFG)</TITLE><PARA>
When the user chooses a location, the 
STARTNET.BAT 
and 
NET.CFG files for the <EMPHASIS>previous</EMPHASIS> location are copied from C:\NWCLIENT back to C:\NWMOBILE\PROFILE\LOC_<REPLACEABLE>n</REPLACEABLE> (where <REPLACEABLE>n</REPLACEABLE> is the ID number of the location). 
RESOLV.CFG is 
also copied back, from C:\NWMOBILE\TCP.</PARA>
<PARA>Then, the STARTNET.BAT and NET.CFG files for the new location are copied from C:\NWMOBILE\PROFILE\LOC_<REPLACEABLE>n</REPLACEABLE> (where <REPLACEABLE>n</REPLACEABLE> is the ID of the new location) to C:\NWCLIENT. The RESOLV.CFG file for the location is copied to C:\NWMOBILE\TCP.</PARA>
<PARA>For more information about the STARTNET.BAT and NET.CFG files for locations, refer to <IXREF idref="FM30213">"What Happens During Installation" on page 14</IXREF> of this chapter.</PARA>
</SECT2>
</SECT1>
<SECT1><TITLE>Installing Server Components</TITLE><PARA>
In addition to the client software, NetWare Mobile includes a synchronization Accelerator and an electronic documentation set, both of which you can optionally install on a network server which supports NetWare Mobile clients.</PARA>
<SECT2><TITLE>Installing the Synchronization Accelerator</TITLE><PARA>
The 
Accelerator is designed to improve performance when the user is synchronizing mobile data over a slow dial-in link to the network.</PARA>
<PARA>It works by reducing the amount of data that needs to be transferred during file synchronization. The "old" version of a file at one end of the link provides information about its contents to the other end of the link. This information and the "new" file (which contains the differences that need to be applied to the old file) are used to create a "delta" file. The delta file is compressed and sent back over the link to be decompressed and used to create the updated file.</PARA>
<PARA>Installing the Accelerator is optional because it will only benefit users who connect to a server over a slow dial-in link and when mobile files have not been changed entirely and are compressible. Once the Accelerator is installed on a server, however, NetWare Mobile automatically detects and uses it when clients make a dial-in connection to that server.</PARA>
<BEGINPAGE PAGENUM=26 ID="BP28"><NOTE><PARA>By default, the Accelerator will only be enabled for dial-in connections. If you want to change this behaviour, refer to <IXREF idref="FM24248">"Enabling and Disabling Use of the Accelerator" on page 28</IXREF>.</PARA>
</NOTE>
<SECT3><TITLE>Requirements</TITLE><PARA>
To install the Accelerator, you need access to the NetWare Mobile installation diskettes or CD-ROM.</PARA>
<PARA>You can install the Accelerator on any NetWare 3 or NetWare 4 server on which CLIB version 3.12 (or later) is also installed.</PARA>
</SECT3>
<SECT3><TITLE>Running INSTALL on the Server</TITLE><PARA>
The NetWare INSTALL program provides menus and prompts to guide you through installing product components, using default directory structures.</PARA>
<PARA>Do the following:</PARA>
<PROCEDURE><STEP><PARA>Insert the first NetWare Mobile installation diskette into a disk drive on the server or load the CD-ROM.</PARA>
</STEP>
<STEP><PARA>At the console prompt, enter the following:
<LITERALLAYOUT><USERINPUT>LOAD INSTALL
</USERINPUT></LITERALLAYOUT>
</PARA>
</STEP>
<STEP><PARA>From "Installation Options", choose 
<INTERFACE class=menuitem>Product options (other installation items)</INTERFACE>.
</PARA>
</STEP>
<STEP><PARA>From "Other Installation Actions", choose 
<INTERFACE class=menuitem>Install a product not listed</INTERFACE>.
</PARA>
<PARA>Alternatively, you can choose "View/Configure/Remove installed products" and then press 
<KEYCAP>&lt;Insert></KEYCAP>.
</PARA>
</STEP>
<STEP><PARA>If necessary, press 
<KEYCAP>&lt;F3></KEYCAP> and enter the path to the NetWare Mobile installation diskette or the CD-ROM.
</PARA>
<PARA>By default, the path from which to install the software is A:\.
</PARA>
<PARA>A list of NetWare Mobile installation options will appear.
<BEGINPAGE PAGENUM=27 ID="BP29"></PARA>
</STEP>
<STEP><PARA>From the list of NetWare Mobile installation options, select "NetWare Mobile NLMDELTA Installation" and then press 
<KEYCAP>&lt;F10></KEYCAP> to accept the marked option.
</PARA>
<PARA>NLMDELTA will be installed in SYS:\SYSTEM. The copying process requires a temporary location for NLMDELTA, however, which by default is SYS:\SYSTEM\TMP. If you want to specify a different temporary destination, do so when prompted.
</PARA>
</STEP>
</PROCEDURE>
<PARA>When the Accelerator is installed, the AUTOEXEC.NCF file is modified automatically so that it loads NLMDELTA.NLM.</PARA>
<PARA>NLMDELTA creates a directory on the server called ACCDELTA for storing temporary files and a log file. Temporary files will be deleted from ACCDELTA every time the Accelerator is reloaded.</PARA>
<PARA>By default, ACCDELTA is created in the SYS: volume. You can specify a different location for ACCDELTA, however, by using a NLMDELTA command line switch; see "Configuring the Accelerator on the Server" below.</PARA>
<PARA>Also by default, ACCDELTA has supervisor rights only, but user's rights to their own files are assigned automatically as required.</PARA>
</SECT3>
<SECT3><TITLE>Configuring the Accelerator on the Server</TITLE><PARA>
You can specify options for the Accelerator using command line switches.</PARA>
<PARA>To display online help, enter the following:</PARA>
<LITERALLAYOUT><USERINPUT>LOAD NLMDELTA /?
</USERINPUT></LITERALLAYOUT>
<PARA>To enable a full-screen monitor console, enter the following:</PARA>
<LITERALLAYOUT><USERINPUT>LOAD NLMDELTA /D
</USERINPUT></LITERALLAYOUT>
<PARA>To create and use a log file, enter the following:</PARA>
<LITERALLAYOUT><USERINPUT>LOAD NLMDELTA /L
<BEGINPAGE PAGENUM=27 ID="BP30"><BEGINPAGE PAGENUM=28></USERINPUT></LITERALLAYOUT>
<PARA>The log file is called ACC_LOG.TXT and is contained in the ACCDELTA directory. When the file reaches 100 KB in size, it is automatically renamed ACC_LOG.BAK and a new ACC_LOG.TXT is created.</PARA>
<PARA>The /L switch also enables the full-screen monitor console.</PARA>
<PARA>To specify a location for the ACCDELTA directory, enter the following:</PARA>
<LITERALLAYOUT><USERINPUT>LOAD NLMDELTA /v<REPLACEABLE>volume</REPLACEABLE>:
</USERINPUT></LITERALLAYOUT>
<SECT4><TITLE>Example:</TITLE><PARA>The following command creates the log file, invokes the full-screen monitor console, and causes the ACCDELTA directory to be created in VOL1: on the server:</PARA>
<LITERALLAYOUT><USERINPUT>LOAD NLMDELTA /D /L /vVOL1:
</USERINPUT></LITERALLAYOUT>
</SECT4>
</SECT3>
<SECT3><TITLE><XMARK id="FM24248">Enabling and Disabling Use of the Accelerator</TITLE><PARA>
By default, the Accelerator will be enabled whenever a mobile user dials in to the server. When the user has a LAN connection, the Accelerator will not be enabled and the synchronization process defaults to simply copying files. To change this default action, you will need to edit the [<USERINPUT>MobileComputer</USERINPUT>] section of C:\WINDOWS\NWMOBILE.INI, as follows:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>If you want the Accelerator to be enabled during LAN connections, change the <USERINPUT>UseAccelerator=</USERINPUT> line to the following:</PARA>
<LITERALLAYOUT><USERINPUT>UseAccelerator=1
</USERINPUT></LITERALLAYOUT>
</LISTITEM>
<LISTITEM><PARA>If you want to restore the Accelerator's default use (enable for dial-in connections only), remove the <USERINPUT>UseAccelerator=</USERINPUT> line from the file.</PARA>
<BEGINPAGE PAGENUM=28 ID="BP31"><BEGINPAGE PAGENUM=29></LISTITEM>
<LISTITEM><PARA>If you want to disable all use of the Accelerator, during both dial-in and LAN connections, change the <USERINPUT>UseAccelerator=</USERINPUT> line to the following:</PARA>
<LITERALLAYOUT><USERINPUT>UseAccelerator=0
</USERINPUT></LITERALLAYOUT>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>Windows must be restarted before any of these changes can take effect.</PARA>
</SECT3>
</SECT2>
<SECT2><TITLE>Installing DynaText Documentation</TITLE><PARA>
NetWare Mobile includes DynaText* versions of the following manuals:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA><CITETITLE>NetWare Mobile User's Overview</CITETITLE></PARA>
</LISTITEM>
<LISTITEM><PARA><CITETITLE>NetWare Mobile Installation and Administration Guide</CITETITLE></PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>If you choose to install this online documentation, NetWare Mobile users will be able to access the manuals from the network.</PARA>
<SECT3><TITLE>Requirements</TITLE><PARA>
Before you can install the DynaText documentation, NetWare online documentation and the DynaText viewer for Windows must already be installed on the server.</PARA>
<PARA>Before a NetWare Mobile user can use the online manuals, the DynaText viewer must be set up on the client computer.</PARA>
<PARA>For information about performing these tasks, refer to the <CITETITLE>NetWare 4.1 Installing and Using Novell Online Documentation</CITETITLE> manual.</PARA>
<BEGINPAGE PAGENUM=29 ID="BP32"><BEGINPAGE PAGENUM=30></SECT3>
<SECT3><TITLE>Running the INSTALL Program</TITLE><PARA>
Install the DynaText documentation in the same way that you install the synchronization Accelerator, using the NetWare INSTALL program.</PARA>
<PARA>Do the following:</PARA>
<PROCEDURE><STEP><PARA>Insert the first NetWare Mobile installation diskette into a disk drive on the server or load the CD-ROM.</PARA>
</STEP>
<STEP><PARA>At the console prompt, enter the following:
<LITERALLAYOUT><USERINPUT>LOAD INSTALL
</USERINPUT></LITERALLAYOUT>
</PARA>
</STEP>
<STEP><PARA>From "Installation Options", choose 
<INTERFACE class=menuitem>Product options (other installation items)</INTERFACE>.
</PARA>
</STEP>
<STEP><PARA>From "Other Installation Actions", choose 
<INTERFACE class=menuitem>Install a product not listed</INTERFACE>.
</PARA>
<PARA>Alternatively, you can choose "View/Configure/Remove installed products" and then press 
<KEYCAP>&lt;Insert></KEYCAP>.
</PARA>
</STEP>
<STEP><PARA>If necessary, press 
<KEYCAP>&lt;F3></KEYCAP> and enter the path to the NetWare Mobile installation diskette or the CD-ROM.
</PARA>
<PARA>By default, the path from which to install the software is A:\.
</PARA>
<PARA>A list of NetWare Mobile installation options will appear.
</PARA>
</STEP>
<STEP><PARA>From the list of NetWare Mobile installation options, select "NetWare Mobile Documentation Installation" and then press 
<KEYCAP>&lt;F10></KEYCAP> to accept the marked option.
</PARA>
<PARA>The DynaText files will be installed in SYS:\DOC\
<REPLACEABLE>language</REPLACEABLE>\NWMOB, where 
<REPLACEABLE>language</REPLACEABLE> is the language version you are installing. The copying process requires a temporary location, however, which by default is SYS:\SYSTEM\TMP. If you want to specify a different temporary destination, do so when prompted.
<BEGINPAGE PAGENUM=30 ID="BP33"><BEGINPAGE PAGENUM=31></PARA>
</STEP>
<STEP><PARA>If you are installing from diskette, insert the last NetWare Mobile installation diskette into the disk drive when prompted.
</PARA>
<PARA>You will also be prompted to insert the first installation diskette again.
</PARA>
</STEP>
</PROCEDURE>
<PARA>To add the NetWare Mobile manuals to the list of public documents on the server, you need to specify document access rights. </PARA>
<PARA>Do the following:</PARA>
<PROCEDURE><STEP><PARA>From the list of NetWare Mobile installation options, select "Specify Document Access Rights" and then press <KEYCAP>&lt;F10></KEYCAP> to accept the marked option.</PARA>
</STEP>
<STEP><PARA>Choose the option to add the documentation to the list of public documents.
</PARA>
<PARA>By choosing the other option, you can remove the NetWare Mobile documentation from the list.
</PARA>
</STEP>
</PROCEDURE>
<PARA>If you choose to add the NetWare Mobile manuals, an entry for them is added to SYS:PUBLIC\SYSDOCS.CFG; if you choose to remove the manuals, that entry will be removed.</PARA>
<PARA></PARA>
</SECT3>
</SECT2>
</SECT1>
</CHAPTER>
<CHAPTER LABEL="2"><TITLE><BEGINPAGE PAGENUM=33 ID="BP34"><XMARK id="FM34715">Setting Up the Mobile Network</TITLE><PARA>
After 
installing 
NetWare® Mobile(tm), you need to specify the way in which the user is going to work offline with replicated network files and directories (or "mobile network").</PARA>
<PARA>This chapter provides information about how NetWare Mobile handles mobile data. Read this information before you run the Mobile File Assistant for the first time after installation to set up the user's mobile network.</PARA>
<SECT1><TITLE><XMARK id="FM33148">What Happens During Installation</TITLE><PARA>
When you run 
Setup and install the NetWare Mobile client software, configuration files are modified and directories are created to enable mobile operation.</PARA>
<SECT2><TITLE>SYSTEM.INI Modified</TITLE><PARA>
The following lines are added to the [<USERINPUT>386Enh</USERINPUT>] section of SYSTEM.INI during installation:</PARA>
<LITERALLAYOUT><USERINPUT>device=DNWCRYPT.386
device=DNWFS.386
</USERINPUT></LITERALLAYOUT>
<PARA><USERINPUT>DNWCRYPT.386</USERINPUT> is the encryption driver and <USERINPUT>DNWFS.386</USERINPUT> is the replicated file system driver.</PARA>
<BEGINPAGE PAGENUM=33 ID="BP35"><BEGINPAGE PAGENUM=34><PARA>The following section is also added to SYSTEM.INI:</PARA>
<LITERALLAYOUT><USERINPUT>[DNWNP]
SPRoot=C:\DNW
SPUserName=Guest
SPName=NetWare Mobile
SPDescription=Novell NetWare Mobile V1.0
SPProvider=DNWNP32.DLL
</USERINPUT></LITERALLAYOUT>
<PARA><USERINPUT>SPUserName</USERINPUT> defines the offline username. <USERINPUT>Guest</USERINPUT> is used as a temporary default until you run the Mobile File Assistant for the first time.</PARA>
<PARA>After you specify options to set up the mobile network, SYSTEM.INI is further modified. In the [<USERINPUT>DNWNP</USERINPUT>] section, the offline username you specified is added to the <USERINPUT>SPUserName=</USERINPUT> line. The following lines are also added:</PARA>
<LITERALLAYOUT><USERINPUT>SPCrypt=OFF€ON
SPRights=OFF€ON
SPRecoveryKey=
<REPLACEABLE>path</REPLACEABLE></USERINPUT></LITERALLAYOUT>
<PARA>The values for <USERINPUT>SPCrypt</USERINPUT>, <USERINPUT>SPRights</USERINPUT>, and <USERINPUT>SPRecoveryKey</USERINPUT> will depend on the choices you made when setting up the mobile network; read <IXREF idref="FM38645">"Running the Mobile File Assistant for the First Time" on page 35</IXREF>. </PARA>
</SECT2>
<SECT2><TITLE>DNW Directory Created</TITLE><PARA>
When the client 
computer is first restarted after NetWare Mobile installation, a hidden directory called DNW is created in the root of the hard disk drive for storing replicated files and directories.</PARA>
<NOTE><PARA>If there is more than one hard disk drive, you will be prompted to specify the drive during Setup.</PARA>
</NOTE>
<PARA>DNW\DNWCRYPT.VOL is also created for storing replicated files and 
directories in 
encrypted form. You can choose whether or not you want to encrypt replicated data when you set up the mobile network; see <IXREF idref="FM38645">"Running the Mobile File Assistant for the First Time" on page 35</IXREF>. You can also change this preference at any time after the initial setup; see <IXREF idref="FM29782">"Changing Preferences for the Mobile Network" on page 37</IXREF> in this chapter.</PARA>
<BEGINPAGE PAGENUM=35 ID="BP36"><PARA>DNW\@@ is created for storing replicated files and directories in non-encrypted form.</PARA>
<PARA>DNW\ETC is also created and contains configuration files that specify information about the user, servers and volumes containing replicated files, and recorded login scripts.</PARA>
<PARA>You should not attempt to edit the information contained in the DNW directory. The only way you should use mobile data is by logging in to NetWare at a location configured for working offline and accessing mobile files and directories through applications such as Windows File Manager, in the same way that you use network files when working online.</PARA>
</SECT2>
</SECT1>
<SECT1><TITLE><XMARK id="FM38645">Running the Mobile File Assistant for the First Time</TITLE><PARA>
To set up the mobile network, after NetWare Mobile is installed, do the following:</PARA>
<PROCEDURE><STEP><PARA>Start Windows*.</PARA>
</STEP>
<STEP><PARA>Choose the Mobile File Assistant from the NetWare Mobile program group.
</PARA>
</STEP>
<STEP><PARA>Follow the instructions on the screen.
</PARA>
<PARA>If you need help information, choose 
<KEYCAP>&lt;Help></KEYCAP> or 
<KEYCAP>&lt;F1></KEYCAP> on any of the dialogs.
</PARA>
</STEP>
</PROCEDURE>
<SECT2><TITLE>Setting the Offline Username and Password</TITLE><PARA>
You will be prompted to specify the NetWare offline username and 
password for the user of the computer. NetWare Mobile allows only one offline user per client computer.</PARA>
<PARA>You are recommended to specify an offline username that is identical to the online username. The advantage of using the same password is that the offline username and password will not need to be specified (for accessing the Mobile File Assistant) when the user is already logged in online. For security, however, you may want to specify a different offline password, especially if you choose not to encrypt mobile data.</PARA>
<BEGINPAGE PAGENUM=36 ID="BP37"></SECT2>
<SECT2><TITLE>Saving Password Information</TITLE><PARA>The offline password is stored on the user's hard disk in encrypted form. You are also given the option of saving password information in a location of your choice (such as a directory on the network) so that the user can access the Mobile File Assistant if the password is forgotten. Make sure you choose a secure location; if you store password information on the local hard disk, any user with access to the computer could potentially discover the offline password.</PARA>
<PARA>
To recover offline password information and log in, the user needs to run the Repair program. Read <IXREF idref="FM14449">"Running the Repair Program" on page 38</IXREF> in this chapter for more information.</PARA>
</SECT2>
<SECT2><TITLE>Enforcing NetWare File Rights Offline</TITLE><PARA>
The NetWare file 
rights stored for replicated files and directories offline are those rights that exist when the files and directories are replicated. As part of setting up the mobile network, you can specify when you want those rights to be enforced. If you choose to enforce rights at all times, mobile file 
synchronization will be slower.</PARA>
</SECT2>
<SECT2><TITLE>Encrypting Mobile Files and Directories</TITLE><PARA>
You can choose to 
encrypt mobile files and directories. If you choose encryption, the only way the user will be able to read mobile data is by logging in to NetWare at a location that is configured for working offline and supplying the offline username and password. Mobile file synchronization will be slower when data is encrypted, however.</PARA>
<PARA>Encryption changes the way replicated files and directories are stored on the local hard disk. Refer to <IXREF idref="FM33148">"What Happens During Installation" on page 33</IXREF> for more information.</PARA>
<BEGINPAGE PAGENUM=36 ID="BP38"><BEGINPAGE PAGENUM=37></SECT2>
<SECT2><TITLE>Creating a Default Offline Location</TITLE><PARA>
If you run the Mobile File Assistant 
for the first time after NetWare Mobile installation but before you create a location profile for working offline, you can choose to create a default location called "On the Road".</PARA>
<PARA>The "On the Road" location is based on the current location profile. The preferred tree you log in to at the current location, for example, will also be set as the preferred tree for "On the Road". The offline location can be changed at any time by using the Locations program, from the Mobile Control Panel.</PARA>
<PARA>For more information about location configuration files, refer to <IXREF idref="FM30213">"What Happens During Installation" on page 14</IXREF> in <IXREF idref="FM27522">Chapter 1 "Installing NetWare Mobile"</IXREF>.</PARA>
</SECT2>
</SECT1>
<SECT1><TITLE><XMARK id="FM29782">Changing Preferences for the Mobile Network</TITLE><PARA>
At any time after the initial mobile network setup, you can change the preferences you specified when you ran the Mobile File Assistant for the first time.</PARA>
<PARA>
Before any of the preferences can be changed, however, all existing replicated data must be removed from the computer's hard disk. You will be prompted to remove data when you change preferences. The user will need to replicate network files and directories again, when working online, using the Mobile File Assistant.</PARA>
<PARA>
To change the 
offline user or to change the preferences for encryption or NetWare file rights, do the following:</PARA>
<PROCEDURE><STEP><PARA>Choose the Mobile File Assistant from the NetWare Mobile program group.</PARA>
</STEP>
<STEP><PARA>Choose 
<INTERFACE class=menuitem>Preferences...</INTERFACE> from the Network menu.
</PARA>
</STEP>
<STEP><PARA>On the Mobile Network Preferences dialog, choose 
<KEYCAP>&lt;Change...></KEYCAP>.
</PARA>
</STEP>
<STEP><PARA>When prompted, enter the offline password for the current user.
<BEGINPAGE PAGENUM=38 ID="BP39"></PARA>
</STEP>
<STEP><PARA>When prompted, choose to remove all existing replicated data from the hard disk.
</PARA>
</STEP>
<STEP><PARA>Restart Windows and choose the Mobile File Assistant from the Mobile Control Panel.
</PARA>
<PARA>You will be prompted to set up the mobile network again, to specify your new preferences.
</PARA>
</STEP>
</PROCEDURE>
</SECT1>
<SECT1><TITLE><XMARK id="FM14449">Running the Repair Program</TITLE><PARA>
The Repair program allows you to specify a new offline password, 
when the current password has been forgotten, and to check and repair (or purge) the mobile file system on the computer.</PARA>
<PARA>To run Repair, do the following:</PARA>
<PROCEDURE><STEP><PARA>Start Windows (if necessary).</PARA>
</STEP>
<STEP><PARA>Choose 
<INTERFACE class=menuitem>Run...</INTERFACE> from the File menu and enter the following:
<LITERALLAYOUT><USERINPUT>C:\NWMOBILE\REPAIR
</USERINPUT></LITERALLAYOUT>
</PARA>
</STEP>
</PROCEDURE>
<PARA>For detailed information about Repair, choose <KEYCAP>&lt;Help></KEYCAP> or <KEYCAP>&lt;F1></KEYCAP> when using the program itself.</PARA>
<PARA></PARA>
</SECT1>
</CHAPTER>
<CHAPTER LABEL="3"><TITLE><BEGINPAGE PAGENUM=39 ID="BP40"><XMARK id="FM37555">Advanced Location Configuration</TITLE><PARA>
The 
NetWare® Mobile(tm) Setup program will install the required software in the correct location on a client computer and ensure that configuration files are created or modified correctly. Additional configuration files are created when you create new location profiles after installation, using the Locations program from the Mobile Control Panel. When the user selects a location after starting the computer, it will be configured according to the properties currently specified but you can use the Locations program to change the properties of a location at any time.</PARA>
<PARA>
Although you should not normally need to edit files manually in order to configure a location, you may need to do so for some networking environments. This chapter describes how to edit configuration files for a number of special requirements and situations.</PARA>
<SECT1><TITLE>Editing Configuration Files</TITLE><PARA>
To edit a NetWare Mobile configuration file, use any ASCII text editor.</PARA>
<PARA>
If you 
need to edit the NET.CFG or 
STARTNET.BAT 
file for a location, however, you can invoke an editor automatically in NetWare Mobile.</PARA>
<PARA>Do the following:</PARA>
<PROCEDURE><STEP><PARA>Choose the Mobile Control Panel.</PARA>
</STEP>
<STEP><PARA>Choose Locations.
</PARA>
</STEP>
<STEP><PARA>Choose 
<KEYCAP>&lt;Advanced...></KEYCAP>.
</PARA>
</STEP>
<STEP><PARA>Specify the file you want to edit: choose 
<KEYCAP>&lt;Edit NET.CFG...></KEYCAP> or 
<KEYCAP>&lt;Edit STARTNET.BAT...></KEYCAP>.
<BEGINPAGE PAGENUM=40 ID="BP41"></PARA>
</STEP>
</PROCEDURE>
<PARA>For information about the NET.CFG and STARTNET.BAT files created for a location, refer to <IXREF idref="FM30213">"What Happens During Installation" on page 14</IXREF> in <IXREF idref="FM27522">Chapter 1 "Installing NetWare Mobile"</IXREF>.</PARA>
</SECT1>
<SECT1><TITLE>Configuring Network Device Drivers</TITLE><PARA>
When you create a location profile, a 
STARTNET.BAT 
file is created for that location. STARTNET.BAT loads the appropriate network drivers and protocols. Because each location profile includes its own STARTNET.BAT file, you can customize specifically for the location in any way you want.</PARA>
<PARA>If you want to add command line parameters to network drivers, however, be aware that a STARTNET.BAT file created by NetWare Mobile uses keywords instead of the driver names themselves, as follows:</PARA>
<LITERALLAYOUT><USERINPUT>C:\NWMOBILE\LOCLOAD LSL
C:\NWMOBILE\LOCLOAD NESL
C:\NWMOBILE\LOCLOAD DRIVER1
C:\NWMOBILE\LOCLOAD DRIVER2
C:\NWMOBILE\LOCLOAD PROTOCOL1
C:\NWMOBILE\LOCLOAD PROTOCOL2
C:\NWMOBILE\LOCLOAD REDIR
</USERINPUT></LITERALLAYOUT>
<PARA>Therefore, 
add 
command line parameters to network drivers in the PROFILE.INI file for the location, where the keywords used in STARTNET.BAT are defined. For example:</PARA>
<LITERALLAYOUT><USERINPUT>[STARTNET]
LSL=
NESL=
Driver1=C:\NWCLIENT\NE2000.COM
Driver2=
Protocol1=C:\NWCLIENT\IPXODI.COM
Protocol2=
Redir=
<BEGINPAGE PAGENUM=40 ID="BP42"><BEGINPAGE PAGENUM=41></USERINPUT></LITERALLAYOUT>
<PARA>The only exception to this is loading drivers high. You may want to load network drivers into upper memory to maximize the amount of conventional memory available on the computer. To load a driver into upper memory, edit the appropriate line in STARTNET.BAT and add the /HI parameter.</PARA>
<PARA>The following STARTNET.BAT lines, for example, load LSL(tm), DRIVER1 (NE2000(tm)), and PROTOCOL1 (IPXODI) into upper memory:</PARA>
<LITERALLAYOUT><USERINPUT>C:\NWCLIENT\LOCLOAD /HI LSL
C:\NWCLIENT\LOCLOAD NESL
C:\NWMOBILE\LOCLOAD /HI DRIVER1
C:\NWMOBILE\LOCLOAD DRIVER2
C:\NWMOBILE\LOCLOAD /HI PROTOCOL1
C:\NWMOBILE\LOCLOAD PROTOCOL2
C:\NWMOBILE\LOCLOAD REDIR
</USERINPUT></LITERALLAYOUT>
</SECT1>
<SECT1><TITLE>Loading Location-Dependent Devices</TITLE><PARA>
You can edit 
CONFIG.SYS so that specific device drivers, such as CD-ROM drivers and PCMCIA card enablers, are loaded depending on which location the user chooses when starting the mobile computer.</PARA>
<PARA>Do the following:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Immediately after the DEVICE statement for LOCATION.EXE, add the following line, exactly as shown:</PARA>
<LITERALLAYOUT><USERINPUT>REM -=* START OF LOCATION-DEPENDENT ENTRIES *=-
</USERINPUT></LITERALLAYOUT>
</LISTITEM>
<LISTITEM><PARA>For each location where you want to load specific devices, add the following, where <REPLACEABLE>name</REPLACEABLE> is the location name as defined in the location properties, immediately before the appropriate DEVICE statements:</PARA>
<LITERALLAYOUT><USERINPUT>REM Location:<REPLACEABLE>name</REPLACEABLE>
</USERINPUT></LITERALLAYOUT>
</LISTITEM>
<LISTITEM><PARA>Immediately following the DEVICE statements for the last location you want to include, add the following line, exactly as shown:</PARA>
<LITERALLAYOUT><USERINPUT>REM -=* END OF LOCATION-DEPENDENT ENTRIES *=-
<BEGINPAGE PAGENUM=42 ID="BP43"></USERINPUT></LITERALLAYOUT>
</LISTITEM>
</ITEMIZEDLIST>
<SECT2><TITLE>Example:</TITLE><PARA>For example, assume you want to do the following:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Load IFSHLP.SYS and DISPLAY.SYS at a location called LOC1</PARA>
</LISTITEM>
<LISTITEM><PARA>Load RAMDRIVE.SYS at LOC2</PARA>
</LISTITEM>
<LISTITEM><PARA>Load IFSHLP.SYS, DISPLAY.SYS, and RAMDRIVE.SYS at LOC3</PARA>
</LISTITEM>
<LISTITEM><PARA>Do not load any specific devices at LOC4</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>You should make the following changes to CONFIG.SYS:</PARA>
<LITERALLAYOUT><USERINPUT>...
...
DEVICE=C:\NWMOBILE\LOCATION.EXE
REM -=* START OF LOCATION-DEPENDENT ENTRIES *=-
REM Location:LOC1
DEVICE=C:\WINDOWS\IFSHLP.SYS
DEVICE=C:\DOS\DISPLAY.SYS CON=(,,1)
REM Location:LOC2
DEVICE=C:\DOS\RAMDRIVE.SYS /E
REM Location:LOC3
DEVICE=C:\WINDOWS\IFSHLP.SYS
DEVICE=C:\DOS\DISPLAY.SYS CON=(,,1)
DEVICE=C:\DOS\RAMDRIVE.SYS /E
REM Location:LOC4
REM -=* END OF LOCATION-DEPENDENT ENTRIES *=-
...
...
<BEGINPAGE PAGENUM=42 ID="BP44"><BEGINPAGE PAGENUM=43></USERINPUT></LITERALLAYOUT>
</SECT2>
</SECT1>
<SECT1><TITLE>Advanced Dial-in Service Configuration</TITLE><PARA>
Dial-in service properties are defined in 
C:\NWMOBILE\DATA\PPHONEBK.INI. 
Most properties can be specified when you create a dial-in service using the Phone Book. There are some advanced PPP configuration settings, however, that you can only change by manually editing PPHONEBK.INI. The default values provided for these settings are designed to work for most network connections; change them only if the default values do not work because of an unusual configuration.</PARA>
<PARA>You will need to edit PPHONEBK.INI to change any of the following PPP settings:</PARA>
<NOTE><PARA>This information is highly technical and is provided to assist network administrators and other expert users in understanding the configuration flexibility of the dialer. Refer to the documentation for the dial-in service to understand how to take advantage of these advanced features.</PARA>
</NOTE>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA><USERINPUT>IPXCompress=1</USERINPUT></PARA>
<PARA>Enable or disable IPX(tm) header compression.</PARA>
<PARA>Specify 1 to enable or 0 to disable.</PARA>
<PARA>The default value is 1.</PARA>
</LISTITEM>
<LISTITEM><PARA><USERINPUT>MRU=1500</USERINPUT></PARA>
<PARA>The size of the largest unit (packet) you expect to send or receive over this connection, in a decimal number of bytes.</PARA>
<PARA>If you use the asynchronous character control map to embed control characters in the data stream, the number of characters per packet may be fewer than the number of bytes.</PARA>
<PARA>You can specify a value between 76 and 1500.</PARA>
<PARA>The default value is 1500 for PPP and 1006 for SLIP.</PARA>
<BEGINPAGE PAGENUM=43 ID="BP45"></LISTITEM>
<LISTITEM><BEGINPAGE PAGENUM=44 ID="BP46"><PARA><USERINPUT>TCPIPComp=1</USERINPUT></PARA>
<PARA>Enable or disable Van Jacobson compression for packet headers.</PARA>
<PARA>Use this setting to improve communication speed if your network dial-in service supports header compression. Compression is very useful for TCP/IP protocols such as TELNET, and can greatly reduce the time it takes for the remote device to echo your keystrokes.</PARA>
<PARA>Specify 1 to enable or 0 to disable.</PARA>
<PARA>The default value is 1.</PARA>
</LISTITEM>
<LISTITEM><PARA><USERINPUT>PCompress=1</USERINPUT></PARA>
<PARA>Enable or disable Van Jacobson compression for TCP/IP slot IDs used in packets.</PARA>
<PARA>Use this setting to improve communication speed if your network dial-in service supports this compression.</PARA>
<PARA>Specify 1 to enable or 0 to disable.</PARA>
<PARA>The default value is 1.</PARA>
</LISTITEM>
<LISTITEM><PARA><USERINPUT>ACCompress=1</USERINPUT></PARA>
<PARA>Enable or disable compression for the address and control fields in the PPP packet header.</PARA>
<PARA>This compression is in addition to that provided by IPX header compression. Use this setting to improve communication speed if your network dial-in service supports both types of compression.</PARA>
<PARA>Specify 1 to enable or 0 to disable.</PARA>
<PARA>The default value is 1.</PARA>
<BEGINPAGE PAGENUM=44 ID="BP47"></LISTITEM>
<LISTITEM><BEGINPAGE PAGENUM=45 ID="BP48"><PARA><USERINPUT>RemoteAddress=0</USERINPUT></PARA>
<PARA> The IP address for the remote device, if required.</PARA>
<PARA>This setting can be used to assign an IP address to another computer running the dialer so that you can connect the two computers.</PARA>
<PARA>Specify a hexadecimal value between 0 and FFFFFFFF.</PARA>
<PARA>The default value is 0.</PARA>
</LISTITEM>
<LISTITEM><PARA><USERINPUT>MagicNumber=0</USERINPUT></PARA>
<PARA>A number used by the network PPP driver for error detection and internal datalink control.</PARA>
<PARA>The PPP drivers on your computer and the remote service use this number to detect and correct loopback conditions during option negotiation.</PARA>
<PARA>Specify a hexadecimal value between 0 and FFFFFFFF.</PARA>
<PARA>The default value is 0.</PARA>
</LISTITEM>
<LISTITEM><PARA><USERINPUT>AsyncCCMap=0</USERINPUT></PARA>
<PARA>Determines which control characters are embedded in the data stream in mapped form.</PARA>
<PARA>Characters that are not mapped can perform control functions on the connection.</PARA>
<PARA>Set the ACCM to match the expectations of the network PPP driver.</PARA>
<PARA>Character mapping can significantly slow transmission speed. You can optimize throughput by reducing mapping to the minimum required by the network PPP driver.</PARA>
<PARA>Specify a hexadecimal value between 0 and FFFFFFFF. Specify 0 to perform no character mapping. Specify FFFFFFFF to map all control characters.</PARA>
<PARA>The default value is 0.</PARA>
<BEGINPAGE PAGENUM=45 ID="BP49"><BEGINPAGE PAGENUM=46></LISTITEM>
</ITEMIZEDLIST>
<PARA>You can change the following values to optimize the speed of a PPP connection or to allow more time or more retries when you encounter difficulty connecting. You can determine which values to adjust from the retry and timeout error messages received from the network PPP driver.</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA><USERINPUT>ConfigReq=10</USERINPUT></PARA>
<PARA>The number of times you want configuration request messages to be re-sent if there is no response from the network dial-in service.</PARA>
<PARA>Specify a value between 0 and 999.</PARA>
<PARA>The default value is 10.</PARA>
</LISTITEM>
<LISTITEM><PARA><USERINPUT>TerminateReq=2</USERINPUT></PARA>
<PARA>The number of times you want terminate request messages to be re-sent if there is no response from the network dial-in service.</PARA>
<PARA>Specify a value between 0 and 999.</PARA>
<PARA>The default value is 2.</PARA>
</LISTITEM>
<LISTITEM><PARA><USERINPUT>ConfigNAK=10</USERINPUT></PARA>
<PARA>The number of times you want configuration negative acknowledge (NAK) messages to be re-sent if there is no response from the network dial-in service.</PARA>
<PARA>Specify a value between 0 and 999.</PARA>
<PARA>The default value is 10.</PARA>
</LISTITEM>
<LISTITEM><PARA><USERINPUT>Timeout=3</USERINPUT></PARA>
<PARA>The number of seconds to wait before re-sending request packets if there is no response from the network dial-in service.</PARA>
<PARA>Specify a value between 0 and 999.</PARA>
<PARA>The default value is 3.</PARA>
<BEGINPAGE PAGENUM=46 ID="BP50"><BEGINPAGE PAGENUM=47></LISTITEM>
</ITEMIZEDLIST>
</SECT1>
<SECT1><TITLE>Adding a New Modem</TITLE><PARA>
When you install NetWare Mobile, you may find that the modem you want to use to dial in to the network is not included in the list of available modems. If this is the case, try selecting the GENERIC modem type; the GENERIC settings will work for most Hayes*-compatible modems.</PARA>
<PARA>If you find that you need to specify settings for your particular modem type, however, you will need to modify the modem database and add the appropriate modem details. Then, when you run Locations from the Mobile Control Panel and choose to change the location properties, your modem will be added to the list and you will be able to select it.</PARA>
<SECT2><TITLE>Adding a New Model</TITLE><PARA>To add a new modem model, when the manufacturer already exists in the list, you need to edit the .INI file for that manufacturer and specify the required details about the new model.</PARA>
<PARA>
To 
determine which .INI file you need to edit, read C:\NWMOBILE\MODEM.INI. A .INI file for each modem manufacturer exists in C:\NWMOBILE\MODEMS.</PARA>
<PARA>The following, for example, is the .INI file for Hayes modems (HAYES.INI). The HAYES.INI file contains details about two different models: the Smartmodem 2400* and the V-series* 2400. The models defined in the [<USERINPUT>Models</USERINPUT>] section are the entries that will appear in the list of models when you are specifying location properties.</PARA>
<LITERALLAYOUT><USERINPUT>[Models]
Smartmodem 2400=
V-series 2400=
</USERINPUT></LITERALLAYOUT>
<LITERALLAYOUT><USERINPUT>[Hayes,Smartmodem 2400]
DEFAULT SPEED=2400
MAXIMUM SPEED=2400
INIT0=ATE0Q0V1X4F1&amp;C1&amp;D2&amp;L0&amp;M0
INIT1=ATS0=0S7=[W]S10=20S12=25
ANSWER=ATA
ORIGINATE=ATD
<BEGINPAGE PAGENUM=48 ID="BP51">AUTO ANSWER=ATS0=[R]
LEASED LINE=AT&amp;L1
BONG STRING=$
</USERINPUT></LITERALLAYOUT>
<LITERALLAYOUT><USERINPUT>[Hayes,V-series 2400]
DEFAULT SPEED=2400
MAXIMUM SPEED=2400
INIT0=ATE0N1Q0V1X4W1&amp;C1&amp;D2&amp;Q0&amp;K0&amp;L0
INIT1=ATS0=0S7=[W]S10=20S12=25
INIT2=ATS36=1S37=0S38=2
ANSWER=ATA
ORIGINATE=ATX1D
AUTO ANSWER=ATS0=[R]
LEASED LINE=AT&amp;L1
FLOW CONTROL=AT&amp;K3
ERROR CORRECTING=AT&amp;Q5
BONG STRING=$
</USERINPUT></LITERALLAYOUT>
<PARA>To determine the information you need to specify for a new model, refer to the documentation for the modem.</PARA>
</SECT2>
<SECT2><TITLE>Adding a New Manufacturer and Model</TITLE><PARA>To add a new modem manufacturer as well as the model, you need to create a .INI file in C:\NWMOBILE\MODEMS.</PARA>
<PARA>You also need to specify the name of the new .INI file in C:\NWMOBILE\MODEM.INI. The following line in MODEM.INI, for example, specifies the manufacturer name that will appear in the list (<USERINPUT>Hayes</USERINPUT>) and the .INI file for that manufacturer:</PARA>
<LITERALLAYOUT><USERINPUT>Hayes=HAYES.INI
<BEGINPAGE PAGENUM=48 ID="BP52"><BEGINPAGE PAGENUM=49></USERINPUT></LITERALLAYOUT>
</SECT2>
</SECT1>
<SECT1><TITLE>Adding a New Calling Card Service Provider</TITLE><PARA>
To pay for dial-in network connections, users can specify a telephone calling card. Information about the calling cards available is kept in the Calling Card Wallet, which can be selected from the Mobile Control Panel.</PARA>
<PARA>When you choose to add a new calling card to the Calling Card Wallet, you select the service provider of the card from a pre-defined list. The list includes the following:</PARA>
<SIMPLELIST><MEMBER>AT&amp;T</MEMBER>
<MEMBER>British Telecom
</MEMBER>
<MEMBER>Deutsche Telekom T-Card
</MEMBER>
<MEMBER>Executive TeleCard Intl.
</MEMBER>
<MEMBER>France Telecom
</MEMBER>
<MEMBER>MCI
</MEMBER>
<MEMBER>Mercury Calling Card
</MEMBER>
<MEMBER>Mercury Residential (UK only)
</MEMBER>
<MEMBER>Sprint World Traveler
</MEMBER>
<MEMBER>Telecom Australia, Australia Direct
</MEMBER>
<MEMBER>Telecom Australia, World Direct
</MEMBER>
</SIMPLELIST>
<PARA>
You 
may want to add a service provider to this list. In order to do this, you must edit C:\NWMOBILE\COUNTRY.INI and specify the dialing rules for the new service provider. After you add the appropriate information to COUNTRY.INI, the new service provider will appear in the list and you will be able to select it when adding a new calling card to the Calling Card Wallet.</PARA>
<PARA>You need to add an entry to the [<USERINPUT>ChargeCards</USERINPUT>] section of COUNTRY.INI, which specifies the service providers available. These are the service providers that appear in the list you see when you are adding a new card to the Calling Card Wallet. Each service provider is defined as follows:</PARA>
<LITERALLAYOUT><USERINPUT><REPLACEABLE>name</REPLACEABLE>=[<REPLACEABLE>name</REPLACEABLE>,<REPLACEABLE>alias</REPLACEABLE>[,<REPLACEABLE>alias</REPLACEABLE>]...]
</USERINPUT></LITERALLAYOUT>
<PARA><REPLACEABLE>name</REPLACEABLE> is the service provider name as it appears in the list and <REPLACEABLE>alias</REPLACEABLE> is an additional name for the same card, as it appears in the list. For example:</PARA>
<LITERALLAYOUT><USERINPUT>British Telecom=
<BEGINPAGE PAGENUM=50 ID="BP53"></USERINPUT></LITERALLAYOUT>
<PARA>You also need to add an entry to the section of COUNTRY.INI for each country where the calling card may be used. The information in these sections specifies the dialing rules for the country and the rules for each calling card in that country. For example:</PARA>
<LITERALLAYOUT><USERINPUT>[Germany]
Country_Code=49
National_Prefix=0
Direct_Dial="","[1]","0[2][1]","00[3][2][1]"
AT&amp;T="01300010","[6][7],0149"[2][1]#,[5][4],","[6...
British Telecom=
Executive TeleCard Intl.="01304749","[6],[5]#[4]0...
Mercury CallingCard="0130804444","[6],,[5][4],00[...
MCI="01300012","[6][7],[5][4][7],01149[2][1],","[...
Sprint World Traveler="01300013","[6][7],[5][4],0...
Hayes_Init=ATS6=4 S7=50 S10=20 S11=90 S29=8 S30=10
</USERINPUT></LITERALLAYOUT>
<PARA><USERINPUT>Country_Code=</USERINPUT><REPLACEABLE>n</REPLACEABLE> specifies the international telephone code for the country.</PARA>
<PARA><USERINPUT>National_Prefix=</USERINPUT><REPLACEABLE>n</REPLACEABLE> specifies the number required when dialing within the same country (but not locally).</PARA>
<PARA><USERINPUT>Direct_Dial="</USERINPUT><REPLACEABLE>ascii_string1</REPLACEABLE><USERINPUT>","</USERINPUT><REPLACEABLE>ascii_string2</REPLACEABLE><USERINPUT>","</USERINPUT><REPLACEABLE>ascii_string3</REPLACEABLE><USERINPUT>","</USERINPUT><REPLACEABLE>ascii_string4</REPLACEABLE><USERINPUT>" </USERINPUT>specifies the dialing rules when no calling card is being used. The ASCII strings specify the following:</PARA>
<PARA><REPLACEABLE>ascii_string1</REPLACEABLE> = blank</PARA>
<PARA><REPLACEABLE>ascii_string2</REPLACEABLE> = dialing rules for a local number</PARA>
<PARA><REPLACEABLE>ascii_string3</REPLACEABLE> = dialing rules for a national number</PARA>
<PARA><REPLACEABLE>ascii_string4</REPLACEABLE> = dialing rules for an international number</PARA>
<BEGINPAGE PAGENUM=50 ID="BP54"><BEGINPAGE PAGENUM=51><PARA>Within each ASCII string, the numbers [1] through [3] represent the following:</PARA>
<PARA>[1] = the telephone number</PARA>
<PARA>[2] = the national code</PARA>
<PARA>[3] = the international code</PARA>
<PARA><REPLACEABLE>calling_card</REPLACEABLE><USERINPUT>="</USERINPUT><REPLACEABLE>ascii_string1</REPLACEABLE><USERINPUT>","</USERINPUT><REPLACEABLE>ascii_string2</REPLACEABLE><USERINPUT>","</USERINPUT><REPLACEABLE>ascii_string3</REPLACEABLE><USERINPUT>","</USERINPUT><REPLACEABLE>ascii_string4</REPLACEABLE><USERINPUT>"</USERINPUT> specifies the dialing rules for a particular calling card, where <REPLACEABLE>calling_card</REPLACEABLE> is the name of the service provider (as defined in the [<USERINPUT>ChargeCards</USERINPUT>] section). The ASCII strings specify the following:</PARA>
<PARA><REPLACEABLE>ascii_string1</REPLACEABLE> = local access number for the card</PARA>
<PARA><REPLACEABLE>ascii_string2</REPLACEABLE> = dialing rules for a local number</PARA>
<PARA><REPLACEABLE>ascii_string3</REPLACEABLE> = dialing rules for a national number</PARA>
<PARA><REPLACEABLE>ascii_string4</REPLACEABLE> = dialing rules for an international number</PARA>
<PARA>Within each ASCII string, the numbers [1] through [6] represent the following:</PARA>
<PARA>[1] = the telephone number</PARA>
<PARA>[2] = the national code</PARA>
<PARA>[3] = the country code</PARA>
<PARA>[4] = the PIN number for the card</PARA>
<PARA>[5] = the account number for the card</PARA>
<PARA>[6] = the access code for the card</PARA>
<PARA>[7] = the "wait for bong" character or string</PARA>
<BEGINPAGE PAGENUM=51 ID="BP55"><BEGINPAGE PAGENUM=52><PARA>The ASCII string can also include the name of another country, which means that the dialing rules for that country should be used. For example:</PARA>
<PARA><USERINPUT>MCI="19,0019","</USERINPUT>[<USERINPUT>6</USERINPUT>][<USERINPUT>7</USERINPUT>]<USERINPUT>,</USERINPUT>[<USERINPUT>5</USERINPUT>][<USERINPUT>4</USERINPUT>][<USERINPUT>7</USERINPUT>]<USERINPUT>,..."</USERINPUT>[<USERINPUT>United States</USERINPUT>]<USERINPUT>"</USERINPUT></PARA>
<PARA></PARA>
</SECT1>
</CHAPTER>
<CHAPTER LABEL="4"><TITLE><BEGINPAGE PAGENUM=53 ID="BP56"><XMARK id="FM24049">Logging in to NetWare</TITLE><PARA>
This chapter provides information about logging in to NetWare® servers when running a NetWare Mobile(tm) client. In particular, network 
administrators may want to read the information about login scripts, if they need to create or debug scripts for mobile users.</PARA>
<SECT1><TITLE>Using NetWare User Tools</TITLE><PARA>
If you want to log in to NetWare at any time after starting a Windows* session, NetWare Mobile allows you to use the NetWare User Tools program (NWUSER.EXE) in the same way you used the program before you installed NetWare Mobile, assuming you were already running a NetWare client. NetWare User Tools is included in the NetWare Mobile program group in Windows.</PARA>
<PARA>For information about logging in to network resources using NetWare User Tools, refer to the <CITETITLE>NetWare 4.1 Client for DOS and Windows User Guide</CITETITLE> or the <CITETITLE>NetWare 3.12 Workstation Basics and Installation</CITETITLE> manual.</PARA>
<PARA>As an alternative to using NetWare User Tools, you can log in to NetWare at any time by choosing the NetWare Login icon from the NetWare Mobile program group.</PARA>
<BEGINPAGE PAGENUM=53 ID="BP57"><BEGINPAGE PAGENUM=54><SECT2><TITLE>Configuring NetWare User Tools for Different Location Types</TITLE><PARA>
The NetWare User Tools window displays a list of all the network resources available at the current location. If a very large number of resources are available, the list may take a long time to build. The list begins to display immediately, but is continuously updated.</PARA>
<PARA>When working online, the user is able to interrupt the building of the resource list by doing either of the following:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Pressing <KEYCAP>&lt;Alt></KEYCAP></PARA>
</LISTITEM>
<LISTITEM><PARA>Pressing <KEYCAP>&lt;Alt></KEYCAP> and the appropriate hot key for a different NetWare User Tools window: <KEYCAP>&lt;D></KEYCAP> for Drive Connections, for example.</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>
By default, the network resource list is displayed as it builds at locations configured to use a LAN or modem only. At offline locations, the list does not display until it is completely built. You can change the types of locations at which the resource list displays as it builds by manually editing 
C:\WINDOWS\NETWARE.INI. For a dial-in location at which a very small number of network resources are available, for example, you may want the resource list to display only after it is completely built; by default, the list at that location would display as it builds.</PARA>
<PARA>Edit the following line in the [<USERINPUT>ListboxUpdate</USERINPUT>] section of NETWARE.INI to change the value of <USERINPUT>LocationType</USERINPUT>. The value represents the type of locations at which you see the resource list as it builds.</PARA>
<LITERALLAYOUT><USERINPUT>LocationType=3
</USERINPUT></LITERALLAYOUT>
<PARA>Specify one of the following values:</PARA>
<SIMPLELIST><MEMBER>0 = none</MEMBER>
<MEMBER>1 = LAN connection
</MEMBER>
<MEMBER>2 = modem connection
</MEMBER>
<MEMBER>3 = LAN connection or modem connection
</MEMBER>
<MEMBER>4 = no connection (offline)
</MEMBER>
<MEMBER>5 = offline or LAN connection
</MEMBER>
<MEMBER>6 = offline or modem connection
</MEMBER>
<MEMBER>7 = all connections
</MEMBER>
<BEGINPAGE PAGENUM=55 ID="BP58"></SIMPLELIST>
<PARA>You can also change the amount of time between updates to the resource list. If you need to see each resource as it is added, for example, you can specify a very short interval between updates. Edit the following line in the [<USERINPUT>ListUpdate</USERINPUT>] section of NETWARE.INI to change the value of <USERINPUT>LBXUpdateInterval_Millisecs</USERINPUT>:</PARA>
<LITERALLAYOUT><USERINPUT>LBXUpdateInterval_Millisecs=1000
</USERINPUT></LITERALLAYOUT>
</SECT2>
</SECT1>
<SECT1><TITLE>Using Login Scripts</TITLE><PARA>
Whenever a user logs in to NetWare, one or more login scripts are executed. Usually, the main purpose of a login script is to map drives to NetWare server volumes and to assign printers to local devices such as LPT1. A user's computing environment relies on these mappings; most users associate resources such as data files and executables with a drive letter (such as T: or U:) rather than locations on particular server volumes.</PARA>
<PARA>
When a user works offline, login scripts will still be executed. The same drive mappings established online will also be established offline, thereby maintaining the user's computing environment. The mappings made offline, however, are to the user's mobile NetWare servers.</PARA>
<NOTE><PARA>Login scripts run offline will not normally capture any printers; for information about offline printing, refer to the online help when using NetWare Mobile.</PARA>
</NOTE>
<BEGINPAGE PAGENUM=55 ID="BP59"><BEGINPAGE PAGENUM=56><SECT2><TITLE>Running Login Scripts in Windows</TITLE><PARA>
Logging in under 
Windows in NetWare Mobile provides some special features which you may want to use when creating or editing login scripts.</PARA>
<SECT3><TITLE>Viewing Login Scripts</TITLE><PARA>
When a login script runs under Windows on a NetWare Client(tm), you will see the following, in a login script output window, by default:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Information about the script (such as servers to which you attach)</PARA>
</LISTITEM>
<LISTITEM><PARA>Messages generated by the script (including error messages)</PARA>
</LISTITEM>
<LISTITEM><PARA>An "Attach to NetWare Server" dialog, whenever the script attempts to attach to a server for which the current username and password are not valid.</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>Also by default, the login script output window will close automatically, after a short pause, when the script is finished running. If you find that you do not have sufficient time to read messages before the windows closes, disable automatic closure by doing the following:</PARA>
<PROCEDURE><STEP><PARA>Choose <KEYCAP>&lt;Options...></KEYCAP> on the Login to NetWare dialog, before the login script runs.</PARA>
</STEP>
<STEP><PARA>Uncheck "Close on completion" in the Script Output Window box.
</PARA>
<PARA>When the login script runs, the output window will now remain open until you choose 
<KEYCAP>&lt;Close></KEYCAP>.
</PARA>
</STEP>
</PROCEDURE>
<PARA>
You can also 
change the length of the pause before the output window closes automatically by editing the [<USERINPUT>Login</USERINPUT>] section of C:\WINDOWS\NWMOBILE.INI and changing the <USERINPUT>OutputTimeout</USERINPUT> value. You can specify any number of seconds from 0 to 60.</PARA>
<BEGINPAGE PAGENUM=56 ID="BP60"><BEGINPAGE PAGENUM=57></SECT3>
<SECT3><TITLE>Changing the Running Mode</TITLE><PARA>
NetWare Mobile allows you to control the way in which a login script is executed.</PARA>
<SECT4><TITLE>Verbose Output Mode</TITLE><PARA>
If you specify verbose output for a login script, you will see each command in the login script window as it is executed. Verbose output also causes MAP errors and information to be displayed in the window; the MAP ERROR OFF and MAP DISPLAY OFF login script commands will be ignored.</PARA>
<PARA>To enable verbose output, do the following:</PARA>
<PROCEDURE><STEP><PARA>Choose <KEYCAP>&lt;Options...></KEYCAP> on the Login to NetWare dialog, before the login script runs.</PARA>
</STEP>
<STEP><PARA>Check "Verbose script output".
</PARA>
</STEP>
</PROCEDURE>
</SECT4>
<SECT4><TITLE>Debug Mode</TITLE><PARA>
Running a login 
script in debug mode causes the login script debug window to display. You can use the debug window to find errors in login scripts, as they execute line by line.</PARA>
<PROCEDURE><STEP><PARA>Choose <KEYCAP>&lt;Options...></KEYCAP> on the Login to NetWare dialog, before the login script runs.</PARA>
</STEP>
<STEP><PARA>Check "Run in debug mode".
</PARA>
</STEP>
</PROCEDURE>
<PARA>For detailed information about using the debugger, read the context-sensitive online help by choosing <KEYCAP>&lt;Help></KEYCAP> from the debug window.</PARA>
<BEGINPAGE PAGENUM=57 ID="BP61"><BEGINPAGE PAGENUM=58></SECT4>
</SECT3>
<SECT3><TITLE>Error Handling</TITLE><PARA>
By default, any 
error generated by a login script will cause a message to be displayed in the output window, when the error occurs. If possible, processing will then continue.</PARA>
<PARA>You can change this action, however, so that when a serious error occurs, script processing pauses and you see a dialog that allows you to ignore the error or to invoke the login script debug window.</PARA>
<PARA>To specify the way you want errors to be handled, do the following:</PARA>
<PROCEDURE><STEP><PARA>Choose <KEYCAP>&lt;Options...></KEYCAP> on the Login to NetWare dialog, before the login script runs.</PARA>
</STEP>
<STEP><PARA>Uncheck "Ignore errors", if you want to be prompted when errors occur.
</PARA>
<PARA>Leave the box checked, or check it if necessary, if you do not want to be prompted.
</PARA>
</STEP>
</PROCEDURE>
</SECT3>
<SECT3><TITLE>Running DOS Commands</TITLE><PARA>
Most login script 
commands (such as MAP) are executed internally by the Login program. Many login scripts, however, also contain commands that run DOS programs. These are known as "external" commands and always begin with a # sign. The # sign instructs Login to pass the rest of the line to DOS for processing.</PARA>
<PARA>In the past, login scripts have been designed to run under DOS, using LOGIN.EXE. Under Windows, many external commands no longer serve a useful purpose. Windows login, therefore, ignores external DOS commands by default.</PARA>
<BEGINPAGE PAGENUM=58 ID="BP62"><BEGINPAGE PAGENUM=59><PARA>In most environments, it will not be necessary to enable external commands. They may be needed, however, for either of the following reasons:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>To execute DOS programs that are still useful under Windows.</PARA>
</LISTITEM>
<LISTITEM><PARA>
To force the use of the DOS #CAPTURE command rather than the CAPTURE command built into Windows login.</PARA>
<PARA>
#CAPTURE, the printer capture program, is the most frequently-
used external command. For example:</PARA>
<LITERALLAYOUT><USERINPUT>#CAPTURE Q=QUEUE_FOR_LASERJET NB TI=10 NFF
</USERINPUT></LITERALLAYOUT>
<PARA>Under Windows login, however, the CAPTURE command is built into the Login program. This built-in CAPTURE command will be invoked by any line beginning with CAPTURE <EMPHASIS>or</EMPHASIS> #CAPTURE, by default. It is not necessary to enable the execution of external commands simply to support the #CAPTURE function.</PARA>
<PARA>The built-in CAPTURE command run by default does not support <EMPHASIS>all</EMPHASIS> of the command line options available under DOS #CAPTURE. The supported options are: AU, B, C, F-number (F=name is not supported), FF, HOLD, K, LPT, NAM, NA, NB, NFF, NNOTI, NT, NOTI, P, Q, T, and TI. If you require any other option, you will need to enable the execution of DOS #CAPTURE.</PARA>
<NOTE><PARA>Refer to the <CITETITLE>NetWare 4.1 Supervising the Network</CITETITLE> manual or the <CITETITLE>NetWare 3.12 Installation and Upgrade</CITETITLE> manual for a full description of CAPTURE's command line options.</PARA>
</NOTE>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>To enable external DOS commands, do the following:</PARA>
<PROCEDURE><STEP><PARA>Choose <KEYCAP>&lt;Options...></KEYCAP> on the Login to NetWare dialog, before the login script runs.</PARA>
</STEP>
<STEP><PARA>Select the appropriate option in the Enable DOS Commands box.
</PARA>
<PARA>The options are: All, #CAPTURE only, All except #CAPTURE, and None.
<BEGINPAGE PAGENUM=59 ID="BP63"><BEGINPAGE PAGENUM=60></PARA>
</STEP>
</PROCEDURE>
</SECT3>
<SECT3><TITLE>Using the PAUSE Command</TITLE><PARA>
PAUSE can be used wherever you want a pause in the execution of a login script.</PARA>
<PARA>When a login script runs under Windows, PAUSE causes a message box to appear that contains the text "Choose OK to continue running your login script" and an<KEYCAP> &lt;OK></KEYCAP> button.</PARA>
<PARA>You can also specify different text for the message box by using the PAUSE command as follows:</PARA>
<LITERALLAYOUT><USERINPUT>PAUSE "[<REPLACEABLE>text</REPLACEABLE>][%<REPLACEABLE>identifier</REPLACEABLE>]" [;][<REPLACEABLE>identifier</REPLACEABLE>]
</USERINPUT></LITERALLAYOUT>
<PARA>Replace text with the words that you want to display in the message box.</PARA>
<PARA>Replace identifier with a variable that you want to display, such as a username.</PARA>
<PARA>PAUSE is used the same way as the WRITE command, except that text appears in a message box rather than in the login script output window. For more information, refer to the description of WRITE in the <CITETITLE>NetWare 4.1 Supervising the Network</CITETITLE> manual or the <CITETITLE>NetWare 3.12 Installation and Upgrade</CITETITLE> manual.</PARA>
</SECT3>
<SECT3><TITLE>Using the DISPLAY Command</TITLE><PARA>
Under DOS login, DISPLAY followed by a filename causes the contents of the specified file to be displayed.</PARA>
<PARA>Under Windows, DISPLAY performs the same function but with the following differences:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>If the specified file has an extension that has been registered with Windows as being associated with an installed application, the application will be invoked and the file opened. You do not need to quit the application before login script processing can continue.</PARA>
</LISTITEM>
<LISTITEM><PARA>If the specified file has no extension or if the extension is not recognized by Windows, it will be displayed in the login script output window.</PARA>
<BEGINPAGE PAGENUM=61 ID="BP64"></LISTITEM>
</ITEMIZEDLIST>
</SECT3>
<SECT3><TITLE>Login Script Commands Not Supported in Windows</TITLE><PARA>
The following login script commands are ignored when a login script is run in Windows: BREAK, 
DOS BREAK, EXIT (when followed by a program name), and NO BANNER.</PARA>
</SECT3>
<SECT3><TITLE>Variables for NetWare Mobile</TITLE><PARA>
Windows login provides the following new variables intended for use in mobile login scripts.</PARA>
<INFORMALTABLE><TGROUP COLS=2><COLSPEC colname=1 colwidth="10*">
<COLSPEC colname=2 colwidth="16*">
<THEAD><ROW><ENTRY colname=1><PARA>Variable </PARA></ENTRY>
<ENTRY colname=2><PARA>Explanation</PARA></ENTRY>
</ROW>
</THEAD>
<TBODY><ROW><ENTRY colname=1><PARA><REPLACEABLE>LOCATION</REPLACEABLE></PARA></ENTRY>
<ENTRY colname=2><PARA>Name of the current location, if any.</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA><REPLACEABLE>OFFLINE</REPLACEABLE> </PARA></ENTRY>
<ENTRY colname=2><PARA>1 if there is no network connection, 0 if there is one.</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA><REPLACEABLE>SLOWLINK</REPLACEABLE><REPLACEABLE></REPLACEABLE></PARA></ENTRY>
<ENTRY colname=2><PARA>1 if there is a dial-in network connection, 0 otherwise.</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA><REPLACEABLE>WINDOWS_LOGIN</REPLACEABLE><REPLACEABLE></REPLACEABLE></PARA></ENTRY>
<ENTRY colname=2><PARA>1 if the login script is executed under Windows, 0 if it is not.</PARA></ENTRY>
</ROW>
</TBODY>
</TGROUP>
</INFORMALTABLE>
<PARA>
LOCATION, 
OFFLINE, and 
SLOWLINK are built-in Windows login script variables. 
WINDOWS_LOGIN is an environment variable.</PARA>
<SECT4><TITLE>Example:</TITLE><PARA>The following login script uses the NetWare Mobile identifier variables to take different action depending on the type of network connection being made:</PARA>
<LITERALLAYOUT><USERINPUT>...
IF "%&lt;WINDOWS_LOGIN>"="1" THEN
REM This login script must be running under Windows
IF OFFLINE="1" THEN
REM There is no physical connection to the network
WRITE "You have logged in offline"
END
IF DIALUP="1" THEN
REM Logging in over a dial-in connection so map
<BEGINPAGE PAGENUM=62 ID="BP65">REM essential drives only
...
...
...
END
WRITE "Your location is %LOCATION"
END
...
</USERINPUT></LITERALLAYOUT>
<PARA>Note that this entire example is enclosed by <USERINPUT>IF "%&lt;WINDOWS_LOGIN>"="1" THEN</USERINPUT> and <USERINPUT>END</USERINPUT>. This prevents all the statements in between from being executed under DOS login where the <USERINPUT>OFFLINE</USERINPUT>, <USERINPUT>DIALUP</USERINPUT>, and <USERINPUT>LOCATION</USERINPUT> would not be recognized.</PARA>
<PARA>Also note that both <USERINPUT>OFFLINE</USERINPUT> and <USERINPUT>DIALUP</USERINPUT> are tested to cause special action when the user has a certain type of connection. When there is a slow dial-in link, time-consuming operations such as drive mappings can be kept to a minimum.</PARA>
</SECT4>
</SECT3>
<SECT3><TITLE>Running Login Scripts Offline</TITLE><PARA>
NetWare Mobile records a login script whenever it is run online during any of the following events:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Windows startup</PARA>
</LISTITEM>
<LISTITEM><PARA>Login via NetWare User Tools</PARA>
</LISTITEM>
<LISTITEM><PARA>Login via the NetWare Login icon in the NetWare Mobile program group</PARA>
</LISTITEM>
<LISTITEM><PARA>Windows startup after login under DOS</PARA>
<NOTE><PARA>Offline locations should be configured so that the user logs in to the network at Windows startup. Enable this option, if necessary, by running Locations from the Mobile Control Panel, selecting the location and then choosing <KEYCAP>&lt;Properties></KEYCAP>. Open the NetWare properties tab and check "Log in at Windows startup".</PARA>
</NOTE>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>Recorded login scripts are saved in the DNW\ETC directory on the local hard disk. Refer to <IXREF idref="FM33148">"What Happens During Installation" on page 33</IXREF> in <IXREF idref="FM34715">Chapter 2 "Setting Up the Mobile Network"</IXREF>, for more information.</PARA>
<BEGINPAGE PAGENUM=63 ID="BP66"><PARA>Login scripts are replayed offline when the user logs in to the same NDS(tm) tree or NetWare server. When a location is configured for working offline, therefore, the preferred tree or server you specify must be the same as the preferred tree or server for the online location at which files and directories are replicated. Otherwise, the correct login scripts will not be run offline and the user will not log in to the correct mobile servers.</PARA>
</SECT3>
</SECT2>
<SECT2><TITLE>Running Login Scripts Under DOS</TITLE><PARA>
Be aware 
that if you log in to NetWare from DOS when working online, NetWare Mobile can still record and save your login script (when you start Windows) but some of your login environment details will be missing. Therefore, you are strongly recommended to configure all location profiles for logging in to NetWare under Windows rather than DOS.</PARA>
<PARA>Also be aware that DOS login is not supported when you are working offline.</PARA>
</SECT2>
<SECT2><TITLE>For More Information</TITLE><PARA>For detailed information about creating login scripts, and all login script commands and identifier variables, refer to the <CITETITLE>NetWare 4.1 Supervising the Network</CITETITLE> manual or the <CITETITLE>NetWare 3.12 Installation and Upgrade</CITETITLE> manual.</PARA>
<PARA></PARA>
</SECT2>
</SECT1>
</CHAPTER>
<CHAPTER LABEL="5"><TITLE><BEGINPAGE PAGENUM=65 ID="BP67"><XMARK id="FM22163">Managing Mobile NDS Objects</TITLE><PARA>
NetWare® 
Mobile(tm) includes support for creating and managing new NetWare Directory Services(tm) (NDS(tm)) object classes via the NetWare 
Administrator program (NWADMIN.EXE). There are two NetWare Mobile objects: Dial-in Service and Mobile File Group.</PARA>
<PARA>This chapter is intended for NetWare 4.x administrators and explains how to create and manage Dial-in Service and Mobile File Group objects.</PARA>
<PARA>For information about how to use the dial-in services and mobile file groups created by the administrator, mobile users should read the online help when using the NetWare Mobile Phone Book, Dialer Assistant, and Mobile File Assistant programs.</PARA>
<SECT1><TITLE>What is a Dial-in Service?</TITLE><PARA>
The Dial-in Service object defines a connection to the network for users who dial in. It includes the following information about the service:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Telephone number details</PARA>
</LISTITEM>
<LISTITEM><PARA>Server type, security options, and supported protocols</PARA>
</LISTITEM>
<LISTITEM><PARA>Connection settings</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>Mobile users can create their own personal dial-in services through the Phone Book and the Dialer Assistant. The services defined by the administrator through NetWare Administrator, however, are referred to as "corporate" services. After a corporate dial-in service is created or updated, an entry is added (or changed) in a user's Phone Book whenever he chooses to update it. The contents of a corporate Dial-in Service object can only be changed permanently by the administrator.</PARA>
<BEGINPAGE PAGENUM=66 ID="BP68"></SECT1>
<SECT1><TITLE>What is a Mobile File Group?</TITLE><PARA>
A Mobile File Group object is a group of related network files which a mobile user can choose to replicate, via the Mobile File Assistant, with a single operation. The administrator can define all the files that make up a certain application as a Mobile File Group, for example, so that users will not need to replicate each file separately. The contents of a Mobile File Group can only be changed by the administrator.</PARA>
</SECT1>
<SECT1><TITLE>Updating the NDS Schema</TITLE><PARA>
When you install NetWare Mobile, Setup adds the Dial-in Service and Mobile File Group "snap-ins" to 
NWADMIN.INI.</PARA>
<NOTE><PARA>Refer to <IXREF idref="FM27522">Chapter 1 "Installing NetWare Mobile"</IXREF>, for more information about what happens to configuration files during installation.</PARA>
</NOTE>
<PARA>The first time you run NWADMIN after installing NetWare Mobile on a client computer, the snap-ins check the NDS schema for the presence of Dial-in Service and Mobile File Group object classes. If they are not found, you will be prompted to add them.</PARA>
<PARA>In order to add the new object classes, you must have the Supervisor right to the entire tree.</PARA>
</SECT1>
<SECT1><TITLE>Creating Mobile NDS Objects</TITLE><PARA>
Before 
you can create a Dial-in Service or Mobile File Group object, your network must be using NetWare 4.x and you must be using a NetWare Mobile client computer running the NetWare administration program (NWADMIN.EXE).</PARA>
<PARA>You must have the Create right to the container object within which you want to create a Dial-in Service or Mobile File Group.</PARA>
<NOTE><PARA>The "rules" for creating a Dial-in Service or Mobile File Group (such as naming conventions) are the same as for any other type of leaf object. For complete information about managing NDS objects, refer to the <CITETITLE>NetWare 4.1 Supervising the Network</CITETITLE> manual.</PARA>
</NOTE>
<BEGINPAGE PAGENUM=66 ID="BP69"><BEGINPAGE PAGENUM=67><PARA>To create a new object, do the following:</PARA>
<PROCEDURE><STEP><PARA>Choose the NetWare Administrator icon from Windows* Program Manager or choose <INTERFACE class=menuitem>Run...</INTERFACE> from the File menu and enter the following:<LITERALLAYOUT><USERINPUT>NWADMIN
</USERINPUT></LITERALLAYOUT>
</PARA>
<PARA>You may need to specify a directory path for NWADMIN.EXE.</PARA>
</STEP>
<STEP><PARA>Select the object that will contain the new leaf object.
</PARA>
<PARA>Select a container object such as Organization (O) or Organizational Unit (OU).
</PARA>
<PARA>For information on moving around in the browser and selecting objects, press 
<KEYCAP>&lt;F1></KEYCAP>.
</PARA>
</STEP>
<STEP><PARA>Choose 
<INTERFACE class=menuitem>Create...</INTERFACE> from the Object menu.
</PARA>
</STEP>
<STEP><PARA>From the New Object dialog, select the class of object you want to create.
</PARA>
<PARA>If Dial-in Service or Mobile File Group do not appear under "New Object", you cannot create that object in this container. Select another container to hold the object.
</PARA>
</STEP>
<STEP><PARA>Choose 
<KEYCAP>&lt;OK></KEYCAP>.
</PARA>
</STEP>
<STEP><PARA>Enter a name for the object and check "Define Additional Properties".
</PARA>
<PARA>If you check "Create Another Object", another Create dialog is displayed immediately after the object is created.
</PARA>
</STEP>
<STEP><PARA>Choose 
<KEYCAP>&lt;Create></KEYCAP>.
</PARA>
</STEP>
</PROCEDURE>
<PARA>The dialogs you see after specifying the object name and choosing to define object properties differ depending on whether you are creating a Dial-in Service or a Mobile File Group.</PARA>
<BEGINPAGE PAGENUM=67 ID="BP70"><BEGINPAGE PAGENUM=68><SECT2><TITLE>Defining Dial-in Service Properties</TITLE><PARA>
The Dial-in Service Properties dialog you see in NetWare Administrator is the same dialog the user sees when creating or modifying his own dial-in services, through the NetWare Mobile Phone Book or Dialer Assistant.</PARA>
<PARA>For detailed information about dial-in service properties, view the online help from the Dial-in Service dialog by choosing the <KEYCAP>&lt;Help></KEYCAP> button or <KEYCAP>&lt;F1></KEYCAP>.</PARA>
<SECT3><TITLE>General Properties</TITLE><PARA>General properties include the following:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Name</PARA>
<PARA>This is the name of the dial-in service that will appear in the user's Phone Book. Make sure you specify a name beginning with a letter so that Phone Book entries can be stored alphabetically.</PARA>
</LISTITEM>
<LISTITEM><PARA>Country</PARA>
<PARA>The country where the dial-in service is located. If required, the appropriate country code will be inserted into the dialing string automatically.</PARA>
</LISTITEM>
<LISTITEM><PARA>Area Code</PARA>
<PARA>If required, the area code will be inserted into the dialing string automatically.</PARA>
</LISTITEM>
<LISTITEM><PARA>Phone Number</PARA>
<PARA>You can also specify that you want the phone number dialed "exactly as shown"; this means that no prefixes or suffixes will be inserted into the dialing string, including country and area codes.</PARA>
<BEGINPAGE PAGENUM=68 ID="BP71"><BEGINPAGE PAGENUM=69></LISTITEM>
</ITEMIZEDLIST>
</SECT3>
<SECT3><TITLE>Server Properties</TITLE><PARA>Server properties include information about the server which the user will be dialing in to.</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Type</PARA>
<PARA>The following types of dial-in server are supported: Generic SLIP, Generic PPP, Shiva PPP, and NetWare Connect(tm) PPP.</PARA>
</LISTITEM>
<LISTITEM><PARA>Security</PARA>
<PARA>You can choose to enable the Password Authentication Protocol (PAP) for the dial-in connection.</PARA>
<NOTE><PARA>Security can only be enabled for NetWare Connect PPP, Shiva PPP, and Generic PPP.</PARA>
</NOTE>
</LISTITEM>
<LISTITEM><PARA>Advanced NetWare Security</PARA>
<PARA>If PAP is enabled, you can also enable the NetWare Connect Authentication Protocol (NWCAP) for NetWare Connect PPP servers.</PARA>
<PARA>The Dialback feature provides additional security by disconnecting the incoming call, and then dialing a dialback number to re-establish the connection.</PARA>
</LISTITEM>
<LISTITEM><PARA>Terminal Window</PARA>
<PARA>If the type of dial-in service you are defining is one that prompts you for additional information after dialing and before a connection is made, you can choose to show the Terminal Window. This will allow you to enter any required commands.</PARA>
<PARA>If the Terminal Windows is displayed, you can also run an automatic script for the connection.</PARA>
</LISTITEM>
<LISTITEM><PARA>Supported Protocols</PARA>
<PARA>You can specify the network protocols supported by the dial-in service. You can also change the configuration settings of supported protocols (NetWare/IP(tm) and TCP/IP).</PARA>
<PARA>When you dial, NetWare Mobile automatically checks that the dial-in service supports the protocol you are using at your current location.</PARA>
<BEGINPAGE PAGENUM=70 ID="BP72"></LISTITEM>
</ITEMIZEDLIST>
</SECT3>
<SECT3><TITLE>Connection Properties</TITLE><PARA>Connection information defines the type of connection provided by the dial-in service modem. This includes the type of parity, the number of data bits per byte that the modem transmits, the number of stop bits between bytes, and whether the modem uses a leased line.</PARA>
</SECT3>
<SECT3><TITLE>For More Information</TITLE><PARA>For detailed information about dial-in services (such as NetWare Connect PPP) and how they can be configured, refer to the documentation for the dial-in service.</PARA>
</SECT3>
</SECT2>
<SECT2><TITLE>Defining Mobile File Group Properties</TITLE><PARA>
After you enter the name of the new Mobile File Group object, specify that you want to define properties, and choose <KEYCAP>&lt;Create></KEYCAP>, you see an Identification dialog for the object. This dialog shows the object's full NDS name. Choose <KEYCAP>&lt;Modify...></KEYCAP> to invoke the Mobile File Assistant.</PARA>
<PARA>The Mobile File Assistant is the same interface that a user sees when he chooses network data for replication (or removal from the hard disk). In NetWare administrator, however, all functions not related to mobile file groups are not available.</PARA>
<PARA>To define files as part of the file group you are creating, do the following:</PARA>
<PROCEDURE><STEP><PARA>Browse the network until you find the file or directory that you want to include and then select it.</PARA>
</STEP>
<STEP><PARA>Choose 
<INTERFACE class=menuitem>Take...</INTERFACE> from the File menu.
</PARA>
</STEP>
<STEP><PARA>On the Take File dialog, choose 
<KEYCAP>&lt;OK></KEYCAP>.
</PARA>
</STEP>
</PROCEDURE>
<PARA>Repeat these steps until you have chosen all the files you want included in the file group.</PARA>
<BEGINPAGE PAGENUM=70 ID="BP73"><BEGINPAGE PAGENUM=71></SECT2>
<SECT2><TITLE>Default Trustee Assignments</TITLE><PARA>
When you create a Dial-in Service leaf object within a container object, all mobile users with the Browse object right and the Read property right to the container will be able to add the dial-in service to their NetWare Mobile Phone Books.</PARA>
<PARA>
When you create a Mobile File Group leaf object within a container object, all mobile users with the Browse object rights and the Read property right to the container will be able to view the file group in the Mobile File Assistant and choose to take it.</PARA>
</SECT2>
</SECT1>
<SECT1><TITLE>Changing Mobile NDS Object Properties</TITLE><PARA>
To change the 
properties of an existing Dial-in Service or Mobile File Group object, you must have the Create right to the object containing the leaf object you want to update.</PARA>
<PARA>Do the following:</PARA>
<PROCEDURE><STEP><PARA>Choose the NetWare Administrator icon from Windows Program Manager or enter the following:<LITERALLAYOUT><USERINPUT>NWADMIN
</USERINPUT></LITERALLAYOUT>
</PARA>
<PARA>You may need to specify a directory path for NWADMIN.EXE.</PARA>
</STEP>
<STEP><PARA>Double-click on the object you want to change or select it and choose 
<INTERFACE class=menuitem>Details...</INTERFACE> from the Object menu.
</PARA>
<PARA>The Identification page appears.
</PARA>
</STEP>
<STEP><PARA>If you are changing a Dial-in Service object, choose "Properties".
</PARA>
<PARA>The Dial-in Service Properties dialog appears.
</PARA>
</STEP>
<STEP><PARA>If you are changing a Mobile File Group object, choose "Modify".
</PARA>
<PARA>An administrator's version of the Mobile File Assistant starts.
<BEGINPAGE PAGENUM=72 ID="BP74"></PARA>
</STEP>
</PROCEDURE>
</SECT1>
<SECT1><TITLE>Deleting Mobile NDS Objects</TITLE><PARA>
To delete a Dial-in Service or 
Mobile File Group object, you must have the Delete right to the object that you want to delete.</PARA>
<PROCEDURE><STEP><PARA>Choose the NetWare Administrator icon from Windows Program Manager or enter the following:<LITERALLAYOUT><USERINPUT>NWADMIN
</USERINPUT></LITERALLAYOUT>
</PARA>
<PARA>You may need to specify a directory path for NWADMIN.EXE.</PARA>
</STEP>
<STEP><PARA>Using the browser, select the object that you want to delete.
</PARA>
</STEP>
<STEP><PARA>Choose 
<INTERFACE class=menuitem>Delete</INTERFACE> from the Object menu.
</PARA>
<PARA>You cannot "undo" an object deletion. To get the object back, you must re-create it and re-enter all property information.
</PARA>
</STEP>
</PROCEDURE>
</SECT1>
<SECT1><TITLE>Purging the NDS Schema</TITLE><PARA>
If you want to remove the Dial-in Service and Mobile File Group object classes from the NDS schema, run the NDSPURGE program (NDSPURGE.EXE). NDSPURGE searches the current tree for existing Dial-in Service and Mobile File Group objects and deletes them. The Dial-in Service and Mobile File Group object classes are then removed.</PARA>
<PARA>In order to use NDSPURGE to remove object classes, you must have the Supervisor right to the entire tree. If you have the Supervisor right to part of the tree only, NDSPURGE will delete objects at and below that level of the tree but it will not be able to remove the object class.</PARA>
<PARA>To run NDSPURGE, do the following:</PARA>
<PROCEDURE><STEP><PARA>Choose <INTERFACE class=menuitem>Run...</INTERFACE> from the File menu and enter the following:<LITERALLAYOUT><USERINPUT>C:\NWMOBILE\NDSPURGE
</USERINPUT></LITERALLAYOUT>
</PARA>
</STEP>
<STEP><PARA>Choose the object class you want to remove.
</PARA>
<PARA>NDSPURGE will display all existing objects of the specified class.
</PARA>
</STEP>
<STEP><PARA>Choose 
<KEYCAP>&lt;Remove></KEYCAP> to remove the objects and the object class.
<BEGINPAGE PAGENUM=73 ID="BP75"></PARA>
</STEP>
</PROCEDURE>
</SECT1>
<SECT1><TITLE>Other Object Management Tasks</TITLE><PARA>You can search for, move, and rename Dial-in Service and Mobile File Group objects in the same way as any other type of NDS leaf object. For detailed information about managing objects, refer to the <CITETITLE>NetWare 4.1 Supervising the Network</CITETITLE> manual.</PARA>
<PARA></PARA>
</SECT1>
</CHAPTER>
<CHAPTER LABEL="6"><TITLE><BEGINPAGE PAGENUM=75 ID="BP76"><XMARK id="FM15821">Troubleshooting</TITLE><PARA>
This chapter contains information about some common situations that may cause problems for the NetWare® Mobile(tm) user and what to do about them.</PARA>
<SECT1><TITLE>Dialing</TITLE><PARA>The information provided in this section relates to dialing in to the network.</PARA>
<PARA>If you experience difficulties when dialing, make the following basic checks:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>Check the hardware. Make sure you are using the correct phone jack.</PARA>
</LISTITEM>
<LISTITEM><PARA>Check the cables. Make sure you are using the correct modem cable.</PARA>
</LISTITEM>
<LISTITEM><PARA>Check for a signal. Make sure the speaker on the modem is turned up and listen for a dial tone or the modem's dial-out tones.</PARA>
</LISTITEM>
<LISTITEM><PARA>Check your software settings.</PARA>
</LISTITEM>
<LISTITEM><PARA>Try changing the baud rate to a lower value. In the Dialer Assistant, choose <INTERFACE class=menuitem>Modem...</INTERFACE> from the Options menu.</PARA>
</LISTITEM>
</ITEMIZEDLIST>
<PARA>If you get an error message when dialing, refer to the NetWare Mobile online help for information about error messages.</PARA>
<BEGINPAGE PAGENUM=75 ID="BP77"><BEGINPAGE PAGENUM=76><SECT2><TITLE>Calling Card Bong Tone Not Supported by Modem</TITLE><PARA>You may find that your modem is not waiting for the correct "bong" tone from the service provider before sending calling card details. Normally, the ampersand (&amp;) is used by the modem so that it waits for the bong. If your modem does not support this, refer to the modem documentation to see if the modem supports a different character, such as a dollar sign ($), and edit the dialing string accordingly. If your modem does not support a different character, use commas to specify a time interval. Start with two commas.</PARA>
</SECT2>
<SECT2><TITLE>Repeated Loss of Signal and Modem Hangs Up</TITLE><PARA>Disable the call waiting feature on your telephone. In the Dialer Assistant, choose <INTERFACE class=menuitem>Modem...</INTERFACE> from the Options menu and then choose <KEYCAP>&lt;Advanced...></KEYCAP>. Check the call waiting checkbox and enter the number to turn off the waiting feature.</PARA>
</SECT2>
</SECT1>
<SECT1><TITLE>Logging in to NetWare</TITLE><PARA>The information in this section relates to logging in to NetWare.</PARA>
<SECT2><TITLE>Password Lockout During Automatic Dial-in for Synchronization</TITLE><PARA>When you are working offline at a location with a modem available and you choose to synchronize from the Mobile File Assistant, you will be prompted to dial in to the required network servers automatically. NetWare Mobile uses your offline username and password to log you in to those servers online, however, so if your offline password is different from your online password, NetWare Mobile's automatic login attempt will fail and you will be asked to provide your online password. If your offline password is different, you cannot prevent this failed login attempt and you may find that if you then type an incorrect online password by mistake, you will be locked out and unable to access the servers you require.</PARA>
<PARA>Whether or not this situation occurs depends on the current password intruder lockout value. To prevent lockout as a result of automatic failed login attempts during synchronization, you are recommended to set the password intruder lockout value to at least 5.</PARA>
<BEGINPAGE PAGENUM=77 ID="BP78"></SECT2>
</SECT1>
<SECT1><TITLE>Printing Offline</TITLE><PARA>The information in this section relates to printing using the offline printer and print queue.</PARA>
<SECT2><TITLE>Unexpected Results</TITLE><PARA>If you find that you get unexpected results when printing jobs from the offline print queue, such as incorrect margin widths and lines of text ending in the wrong places, printer options may not be set correctly. For accurate results via the offline printer, printer options must be set consistently for the document, the offline printer, and the printer you want to use online to actually print the document.</PARA>
<PARA>Many word processors allow you to set the page size and orientation for a document using a Page Setup or Format option. Check to make sure that the paper size and orientation settings for both the online and offline printers are consistent with the settings for the document and with each other. Also make sure that the resolution setting (in dots per inch) is the same for both printers.</PARA>
<PARA>To check printer settings, and change them if necessary, select the printer in Windows* Print Manager and then choose the <INTERFACE class=menuitem>Printer Setup</INTERFACE> option from the Options menu.</PARA>
<PARA>To check or change printer settings for the online printer, you can also select the printer in the Offline Print Assistant and then choose &lt;<KEYCAP>Setup...</KEYCAP>>.</PARA>
<PARA>For some printers, you will need to choose an advanced options dialog in printer setup to check or change the resolution. For the offline printer, choose &lt;<KEYCAP>Custom...</KEYCAP>> from the printer setup dialog to check or change a specific resolution value.</PARA>
<BEGINPAGE PAGENUM=77 ID="BP79"><BEGINPAGE PAGENUM=78></SECT2>
</SECT1>
<SECT1><TITLE>Replicating Network Files and Directories</TITLE><PARA>The information in this section relates to replicating files and directories from the network.</PARA>
<SECT2><TITLE>Automatic Backups Cannot be Created in Name-only Directories</TITLE><PARA>When you use an application that makes "safe saves" or automatic backups, it will attempt to create .BAK or other backup files in the same directory as the files it is backing up or overwrite previous backup files in that directory. If the application is backing up a replicated file when you are working offline but the directory or existing backup files in the directory are replicated as name-only, the backup file cannot be created. Therefore, you are recommended to replicate entire directories rather than single files.</PARA>
<PARA></PARA>
</SECT2>
</SECT1>
</CHAPTER>
<APPENDIX LABEL="A"><TITLE><BEGINPAGE PAGENUM=79 ID="BP80"><XMARK id="FM27220">Supported Adapters and Modems</TITLE><PARA>
This 
appendix lists the network adapters and modems you will be able to choose from when configuring locations.</PARA>
<PARA>If you want to use an adapter that is not included in the list, you will need a diskette containing the appropriate driver for your adapter. You will also need an INS file; for information about creating INS files, refer to <IXREF idref="FM18631">Appendix B "Creating an INS File for a LAN Driver"</IXREF>.</PARA>
<PARA>If you want to use a modem that is not included in the list, try selecting the GENERIC modem settings during location configuration. These settings will work for most Hayes*-compatible modems. If they do not work for your modem, you will need to add your modem to the modem database. For information about doing this, refer to <IXREF idref="FM37555">Chapter 3 "Advanced Location Configuration"</IXREF>. </PARA>
<SECT1><TITLE>Adapters</TITLE><PARA></PARA>
<INFORMALTABLE><TGROUP COLS=2><COLSPEC colname=1 colwidth="9*">
<COLSPEC colname=2 colwidth="26*">
<TBODY><ROW><ENTRY colname=1><PARA>3Com: </PARA></ENTRY>
<ENTRY colname=2><PARA>3Com TokenLink III Adapter</PARA><PARA>3Com EtherLink III Parallel Tasking PCMCIA Adapter</PARA><PARA>3Com EtherLink III Parallel Tasking Family</PARA><PARA>3Com 3C770 FDDILink</PARA><PARA>3Com 3C689 PCMCIA Token-Ring Adapter</PARA><PARA>3Com 3C503 EtherLink II/16</PARA><PARA>3Com 3C503 EtherLink II/16 TP</PARA><PARA>3Com 3C503 EtherLink II</PARA><PARA>3Com 3C503 EtherLink II TP</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Cabletron Systems: </PARA></ENTRY>
<ENTRY colname=2><PARA>Cabletron Systems Token-Ring T20</PARA><PARA>Cabletron Systems FDDI F70</PARA><PARA>Cabletron Systems Ethernet E22</PARA><PARA>Cabletron Systems Ethernet E21</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Digital: </PARA></ENTRY>
<ENTRY colname=2><PARA>Digital Equipment Corporation EB40</PARA><PARA>Digital Equipment Corporation DE425</PARA><PARA>Digital DE205</PARA><PARA>Digital DE204</PARA><PARA>Digital DE203</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Eagle: </PARA></ENTRY>
<ENTRY colname=2><PARA>Eagle NE3200</PARA><PARA>Eagle NE2000PLUS</PARA><PARA>Eagle NE2000PLUS T</PARA><PARA>Eagle NE2000PLUS 3</PARA><PARA>Eagle NE2000</PARA><PARA>Eagle NE2-32</PARA><PARA>Eagle NE/2T</PARA><PARA>Eagle NE/2</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Hewlett-Packard: </PARA></ENTRY>
<ENTRY colname=2><PARA>Hewlett-Packard PC Adapter 8/16/16+</PARA><PARA>Hewlett-Packard MC Adapter 16</PARA><PARA>HP PC LAN Adapter NC/16 TP (J2405A)</PARA><PARA>HP PC LAN Adapter NC/16 (J2405B)</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>IBM: </PARA></ENTRY>
<ENTRY colname=2><PARA>ODI Module for the IBM LAN Support Program</PARA><PARA>IBM Token-Ring Network Adapter/A</PARA><PARA>IBM Token-Ring Network Adapter II &amp; 16/4 Adapter</PARA><PARA>IBM Token-Ring Network 16/4 Adapter/A</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Intel:</PARA></ENTRY>
<ENTRY colname=2><PARA>Intel TokenExpress(TM) PRO Adapter</PARA><PARA>Intel EtherExpress32</PARA><PARA>Intel EtherExpress PRO</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Madge: </PARA></ENTRY>
<ENTRY colname=2><PARA>Madge Smart 16/4 PC Ringnode</PARA><PARA>Madge Smart 16/4 MC32 Ringnode</PARA><PARA>Madge Smart 16/4 MC Ringnode</PARA><PARA>Madge Smart 16/4 ISA Client Ringnode</PARA><PARA>Madge Smart 16/4 EISA Ringnode</PARA><PARA>Madge Smart 16/4 AT Ringnode</PARA><PARA>Madge Smart 16 Ringnode</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Microdyne: </PARA></ENTRY>
<ENTRY colname=2><PARA>Microdyne NTR2000 Token-Ring Adapter</PARA><PARA>Microdyne NE3300 Ethernet</PARA><PARA>Microdyne NE3200T</PARA><PARA>Microdyne NE3200</PARA><PARA>Microdyne NE2000PLUS</PARA><PARA>Microdyne NE2000PLUS T</PARA><PARA>Microdyne NE2000PLUS 3</PARA><PARA>Microdyne NE2000</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>National Semiconductor: </PARA></ENTRY>
<ENTRY colname=2><PARA>National Semiconductor NE2000 InfoMover</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Novell: </PARA></ENTRY>
<ENTRY colname=2><PARA>Novell RX-Net/2</PARA><PARA>Novell RX-Net &amp; RX-Net II</PARA><PARA>Novell NTR2000 Token-Ring Adapter</PARA><PARA>Novell NE3200</PARA><PARA>Novell NE2100</PARA><PARA>Novell NE2000</PARA><PARA>Novell NE/2-32</PARA><PARA>Novell NE1500T</PARA><PARA>Novell NE1000</PARA><PARA>Novell NE/2</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Olicom: </PARA></ENTRY>
<ENTRY colname=2><PARA>Olicom Token-Ring MC 16/4 Adapter</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Proteon: </PARA></ENTRY>
<ENTRY colname=2><PARA>Proteon p199X RapiMac Driver</PARA><PARA>Proteon p199X RapiMac Driver</PARA><PARA>Proteon p199X RapiMac Driver</PARA><PARA>Proteon p139X RapiDriver</PARA><PARA>Proteon p199X RapiMac Driver</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Racal: </PARA></ENTRY>
<ENTRY colname=2><PARA>Racal InterLan PCI Ethernet MLID</PARA><PARA>Racal InterLan MCA/NI9210 Ethernet MLID</PARA><PARA>Racal InterLan EtherBlaster/NI6510 Ethernet MLID</PARA><PARA>Racal InterLan ES3210 Ethernet MLID</PARA><PARA>Racal InterLan AT/NI6610 Ethernet MLID</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Standard Microsystems Corp.: </PARA></ENTRY>
<ENTRY colname=2><PARA>Standard Microsystems Corporation SMC9000</PARA><PARA>SMC TokenCard Elite Master32 ESIA Adapter</PARA><PARA>SMC Token Ring EliteFamily Adapter</PARA><PARA>SMC Ethernet PCMCIA LAN Adapter</PARA><PARA>SMC Ethernet LAN Adapter</PARA><PARA>SMC EtherCard Elite32C Ultra EISA Adapter</PARA><PARA>SMC 8432/PCI</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Thomas-Conrad: </PARA></ENTRY>
<ENTRY colname=2><PARA>Thomas-Conrad TC6x46 ARCnet MC Adapter</PARA><PARA>Thomas-Conrad TC6x45 ARCnet 16-bit Adapter</PARA><PARA>Thomas-Conrad TC6x42 ARCnet 8-bit Adapter</PARA><PARA>Thomas-Conrad TC5048 PCI Ethernet Adapter</PARA><PARA>Thomas-Conrad TC5047 Ethernet Adapter</PARA><PARA>Thomas-Conrad TC5046 Ethernet Adapter - 32 bit</PARA><PARA>Thomas-Conrad TC4046 Adapter</PARA><PARA>Thomas-Conrad TC4035/TC4045 Adapter</PARA><PARA>Thomas-Conrad TC3047 TCNS EISA Adapter</PARA><PARA>Thomas-Conrad TC3046 TCNS MC Adapter</PARA><PARA>Thomas-Conrad TC3045 TCNS 16-bit Adapter</PARA><PARA>Thomas-Conrad TC3042 TCNS 8-bit Adapter</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Xircom: </PARA></ENTRY>
<ENTRY colname=2><PARA>Xircom Credit Card Ethernet Adapter</PARA></ENTRY>
</ROW>
</TBODY>
</TGROUP>
</INFORMALTABLE>
<BEGINPAGE PAGENUM=83 ID="BP81"><BEGINPAGE PAGENUM=83><BEGINPAGE PAGENUM=84></SECT1>
<SECT1><TITLE>Modems</TITLE><PARA></PARA>
<INFORMALTABLE><TGROUP COLS=2><COLSPEC colname=1 colwidth="9*">
<COLSPEC colname=2 colwidth="26*">
<TBODY><ROW><ENTRY colname=1><PARA>GENERIC: </PARA></ENTRY>
<ENTRY colname=2><PARA>Hayes compatible 2400</PARA><PARA>Hayes compatible 9600</PARA><PARA>Hayes compatible 14400</PARA><PARA>Hayes compatible 28800</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>ACEEX: </PARA></ENTRY>
<ENTRY colname=2><PARA>1496</PARA><PARA>1414</PARA><PARA>2814</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Acer: </PARA></ENTRY>
<ENTRY colname=2><PARA>Modem 2424</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>AdTrans: </PARA></ENTRY>
<ENTRY colname=2><PARA>ISU 128</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Ampac: </PARA></ENTRY>
<ENTRY colname=2><PARA>Connoisseur RDX14400</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Anchor: </PARA></ENTRY>
<ENTRY colname=2><PARA>Signalman Lightning 24</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Angia: </PARA></ENTRY>
<ENTRY colname=2><PARA>V.32/V.32bis</PARA><PARA>SafeJack 28.8</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Apex: </PARA></ENTRY>
<ENTRY colname=2><PARA>V.32bis</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Archtek: </PARA></ENTRY>
<ENTRY colname=2><PARA>SmartLink 14400 V.32bis</PARA><PARA>SmartLink 28800</PARA><PARA>SmartLink V.32bis Fax modem</PARA><PARA>SmartLink 9624 Voice/Fax modem</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>AT&amp;T: </PARA></ENTRY>
<ENTRY colname=2><PARA>2224 CEO</PARA><PARA>4000</PARA><PARA>4024</PARA><PARA>Comsphere 3800 Series</PARA><PARA>Paradyne 9600 PCMCIA</PARA><PARA>Paradyne DM424/DM424PC</PARA><PARA>Paradyne KeepInTouch</PARA><PARA>DataPort 14.4/FAX - Cellular</PARA><PARA>DataPort 14.4/FAX</PARA><PARA>Secure Data 1900</PARA><PARA>Secure Data 1910</PARA><PARA>7400B Plus Data Module</PARA><PARA>3811 modem</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Banksia: </PARA></ENTRY>
<ENTRY colname=2><PARA>MyFastModem</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Bausch: </PARA></ENTRY>
<ENTRY colname=2><PARA>EuroScout</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>BestData: </PARA></ENTRY>
<ENTRY colname=2><PARA>SmartOne 1442F</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Bocamodem: </PARA></ENTRY>
<ENTRY colname=2><PARA>14.4Kbps Pocket</PARA><PARA>14.4Kbps V.32bis</PARA><PARA>V.FAST MV28K</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>CALPAK: </PARA></ENTRY>
<ENTRY colname=2><PARA>MX-2400/MXE-2400</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Cardinal: </PARA></ENTRY>
<ENTRY colname=2><PARA>9600 V.42</PARA><PARA>9600 V.32/V.42bis</PARA><PARA>14400 V.32/V.42bis</PARA><PARA>9600 1/2 Card V.32/V.42bis</PARA><PARA>14400 1/2 Card V.32/V.42bis</PARA><PARA>19200 V.32terbo/V.42bis</PARA><PARA>MVP144CC</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Codex: </PARA></ENTRY>
<ENTRY colname=2><PARA>1132/PC Modem</PARA><PARA>2234</PARA><PARA>2264</PARA><PARA>3220</PARA><PARA>3260/3265</PARA><PARA>326X FAST</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Communicate: </PARA></ENTRY>
<ENTRY colname=2><PARA>1440C</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Compaq: </PARA></ENTRY>
<ENTRY colname=2><PARA>PCMCIA 14.4 Data/Fax</PARA><PARA>SpeedPAQ 144</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>CompuCom: </PARA></ENTRY>
<ENTRY colname=2><PARA>Speedmodem Combo</PARA><PARA>Speedmodem STAR</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>CXR AJ: </PARA></ENTRY>
<ENTRY colname=2><PARA>High Speed V.32bis</PARA><PARA>High Speed V.32ter</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>DAP: </PARA></ENTRY>
<ENTRY colname=2><PARA>MS 20 ISDN Terminal Adapter</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Data Race: </PARA></ENTRY>
<ENTRY colname=2><PARA>Action 32L</PARA><PARA>Redi Card PCMCIA</PARA><PARA>Redi Modem</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Dataflex: </PARA></ENTRY>
<ENTRY colname=2><PARA>Design Pocket ISDN V.24/X.21</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Datatronics: </PARA></ENTRY>
<ENTRY colname=2><PARA>Discovery 1200C</PARA><PARA>Discovery 1200P</PARA><PARA>Discovery 2400E</PARA><PARA>Discovery 1414CX</PARA><PARA>Discovery 2814CX</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Dell: </PARA></ENTRY>
<ENTRY colname=2><PARA>Data/Fax 96/96V</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>DSD: </PARA></ENTRY>
<ENTRY colname=2><PARA>9642+</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>DSI: </PARA></ENTRY>
<ENTRY colname=2><PARA>9624</PARA><PARA>Scout Plus</PARA><PARA>Connection 14.4+Fax</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Dynalink: </PARA></ENTRY>
<ENTRY colname=2><PARA>14400</PARA><PARA>14400/9600</PARA><PARA>Easydata</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>ELSA: </PARA></ENTRY>
<ENTRY colname=2><PARA>MicroLink 14.4</PARA><PARA>MicroLink ISDN</PARA><PARA>MicroLink 28800</PARA><PARA>MicroLink 2460</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>ETech: </PARA></ENTRY>
<ENTRY colname=2><PARA>Bullet E2400</PARA><PARA>Bullet E9696M</PARA><PARA>Bullet PC2400MH</PARA><PARA>UFOmate P1496MX</PARA><PARA>UFOmate P1414MX</PARA><PARA>UFOmate P9696MX</PARA><PARA>Bullet E1414MX</PARA><PARA>PCMCIA C1414AX</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>EuroViVa: </PARA></ENTRY>
<ENTRY colname=2><PARA>14.4/Fax</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Everex: </PARA></ENTRY>
<ENTRY colname=2><PARA>Evercom 24E</PARA><PARA>Evercom 24E+</PARA><PARA>Evercom 96E+</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Fastcomm: </PARA></ENTRY>
<ENTRY colname=2><PARA>FDX Series</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Forval: </PARA></ENTRY>
<ENTRY colname=2><PARA>14400</PARA><PARA>9600 V32</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Galaxy: </PARA></ENTRY>
<ENTRY colname=2><PARA>Apollo V.32turbo</PARA><PARA>UFO V.32 Turbo/V.42bis</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Gateway 2000: </PARA></ENTRY>
<ENTRY colname=2><PARA>Telepath Fax/Modem</PARA><PARA>Telepath V.32/42bis</PARA><PARA>Telepath II Fax/Modem</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>GDC: </PARA></ENTRY>
<ENTRY colname=2><PARA>914 ADR</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>General Datacom: </PARA></ENTRY>
<ENTRY colname=2><PARA>m MNP5</PARA><PARA>m V.42bis</PARA><PARA>m VF 28.8</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>GVC: </PARA></ENTRY>
<ENTRY colname=2><PARA>9600</PARA><PARA>9600 V.42bis</PARA><PARA>14400 V.42bis</PARA><PARA>Super Modem 2400</PARA><PARA>DM2814 Fax modem</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Hayes: </PARA></ENTRY>
<ENTRY colname=2><PARA>compatible</PARA><PARA>Smartmodem 300</PARA><PARA>Smartmodem 1200</PARA><PARA>Smartmodem 2400</PARA><PARA>V-series 2400</PARA><PARA>V-series 9600</PARA><PARA>Smartmodem OPTIMA 96</PARA><PARA>Smartmodem OPTIMA 14.4</PARA><PARA>Smartmodem 28.8 V.FC</PARA><PARA>V-series Ultra 96</PARA><PARA>V-series Ultra 144</PARA><PARA>ACCURA 96</PARA><PARA>ACCURA 144</PARA><PARA>ACCURA 288 V.FC</PARA><PARA>ISDN - V.120</PARA><PARA>ISDN - X.25</PARA><PARA>Smartmodem 9600 - V.32</PARA><PARA>OPTIMA 14.4 PCMCIA</PARA><PARA>Smartmodem OPTIMA 14.4 for PCMCIA</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Hi-Per: </PARA></ENTRY>
<ENTRY colname=2><PARA>96/96</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Hotline Handy: </PARA></ENTRY>
<ENTRY colname=2><PARA>144CC</PARA><PARA>28.8CC V-FC</PARA><PARA>28.8CC V.34</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Identity: </PARA></ENTRY>
<ENTRY colname=2><PARA>14400 Fax/Modem</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Incomm: </PARA></ENTRY>
<ENTRY colname=2><PARA>Turbo 4800</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Infotel: </PARA></ENTRY>
<ENTRY colname=2><PARA>144</PARA><PARA>14400 Data/Fax</PARA><PARA>28800 Data/Fax</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Intel: </PARA></ENTRY>
<ENTRY colname=2><PARA>2400EX</PARA><PARA>2400 EX MNP</PARA><PARA>9600EX</PARA><PARA>14.4EX</PARA><PARA>Faxmodem 14.4</PARA><PARA>SatisFAXtion</PARA><PARA>SatisFAXtion/400</PARA><PARA>SatisFAXtion/400E</PARA><PARA>PCMCIA 14.4 Faxmodem - Rel 3</PARA><PARA>PCMCIA 96 Faxmodem - Rel 3</PARA><PARA>PCMCIA 14.4 Faxmodem - Rel 2</PARA><PARA>PCMCIA 96 Faxmodem - Rel 2</PARA><PARA>144/144e</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>I&amp;M: </PARA></ENTRY>
<ENTRY colname=2><PARA>1442 bis</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>KKI:</PARA></ENTRY>
<ENTRY colname=2><PARA>28800</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>LASAT: </PARA></ENTRY>
<ENTRY colname=2><PARA>unique 144</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Leading Edge: </PARA></ENTRY>
<ENTRY colname=2><PARA>L 1200</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Lightning: </PARA></ENTRY>
<ENTRY colname=2><PARA>Model L 1200</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Longshine: </PARA></ENTRY>
<ENTRY colname=2><PARA>LCS 8896 Fax modem</PARA><PARA>LCS 8896 Plus Fax modem</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Maestro: </PARA></ENTRY>
<ENTRY colname=2><PARA>Executive Series 144FM</PARA><PARA>Companion PB96M</PARA><PARA>Companion PB96FM</PARA><PARA>Companion PB144M</PARA><PARA>Companion PB144FM</PARA><PARA>Companion PW144FM</PARA><PARA>Companion PW192FM</PARA><PARA>Companion PW240FM</PARA><PARA>Companion PW288FM</PARA><PARA>Executive 96M</PARA><PARA>Executive 96FM</PARA><PARA>Executive 144M</PARA><PARA>Executive 144FM</PARA><PARA>Executive 192FM</PARA><PARA>Executive 240FM</PARA><PARA>Executive 288FM</PARA><PARA>Super Executive V.32</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Maxan:</PARA></ENTRY>
<ENTRY colname=2><PARA>Maxmodem 2400EI</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Maxum: </PARA></ENTRY>
<ENTRY colname=2><PARA>Super Modem 2400</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Mayze: </PARA></ENTRY>
<ENTRY colname=2><PARA>96/96R</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Megahertz: </PARA></ENTRY>
<ENTRY colname=2><PARA>96/24 FAX/Modem</PARA><PARA>P296FMV FAX/Modem</PARA><PARA>T3144 FAX/Modem</PARA><PARA>C5144 FAX/Modem</PARA><PARA>A2144,CC3144,P2144,TX3144</PARA><PARA>XJ1144</PARA><PARA>XJ2288</PARA><PARA>XJ 2144</PARA><PARA>CC3144</PARA><PARA>CC3288</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>MegaPlus: </PARA></ENTRY>
<ENTRY colname=2><PARA>Fax V.32bis</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>MICC: </PARA></ENTRY>
<ENTRY colname=2><PARA>4824</PARA><PARA>9600/9610/9620</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Microcom: </PARA></ENTRY>
<ENTRY colname=2><PARA>AX/1200-2400 series</PARA><PARA>AX/9600</PARA><PARA>AX/9612-9624 series</PARA><PARA>DeskPorte FAST ES 28.8</PARA><PARA>DeskPorte ES</PARA><PARA>DeskPorte FAST</PARA><PARA>QX/12K and QX/V.32c</PARA><PARA>QX/4232bis</PARA><PARA>QX/4232hs</PARA><PARA>HD/4232bis</PARA><PARA>HD/FAST 28.8</PARA><PARA>MicroPorte 542</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Migent: </PARA></ENTRY>
<ENTRY colname=2><PARA>Pocket Modem</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Mitsuba: </PARA></ENTRY>
<ENTRY colname=2><PARA>9600</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Modular Technology: </PARA></ENTRY>
<ENTRY colname=2><PARA>M5124</PARA><PARA>M5132</PARA><PARA>M5134</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Motorola: </PARA></ENTRY>
<ENTRY colname=2><PARA>CELLect 14.4</PARA><PARA>CELLect 14.4 PCMCIA</PARA><PARA>CELLect PCMCIA Cellular</PARA><PARA>V.3400</PARA><PARA>V.3229</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>MultiTech: </PARA></ENTRY>
<ENTRY colname=2><PARA>1200</PARA><PARA>224</PARA><PARA>224E</PARA><PARA>224EH5/EH7</PARA><PARA>696</PARA><PARA>MultiModem II MT932</PARA><PARA>MultiModem II MT1432</PARA><PARA>MultiModem II MT1932</PARA><PARA>MultiModem II (slow unit)</PARA><PARA>MultiModem V32</PARA><PARA>MT2834</PARA><PARA>MultiModem 1932 ZDX</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Muxum: </PARA></ENTRY>
<ENTRY colname=2><PARA>ECM FAST V32 Terbo</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>NEC: </PARA></ENTRY>
<ENTRY colname=2><PARA>N9631</PARA><PARA>DSP 9630</PARA><PARA>14.4</PARA><PARA>14.4 - Cellular</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Netcomm: </PARA></ENTRY>
<ENTRY colname=2><PARA>SmartModem M11F</PARA><PARA>SmartModem V.32bis E7/M7F</PARA><PARA>E4/M4F</PARA><PARA>Automodem E11F</PARA><PARA>ProRack M4</PARA><PARA>ProRack M5</PARA><PARA>ProRack M7</PARA><PARA>SmartModem M4/M5</PARA><PARA>Trailblazer v.32</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Nokia: </PARA></ENTRY>
<ENTRY colname=2><PARA>Cellular Data Card</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Nomad: </PARA></ENTRY>
<ENTRY colname=2><PARA>9600 Modem</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Okidata: </PARA></ENTRY>
<ENTRY colname=2><PARA>Okitel 9600</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>OmniTel: </PARA></ENTRY>
<ENTRY colname=2><PARA>Netcomm Q1200</PARA><PARA>Netcomm Q2400</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>ONBIT: </PARA></ENTRY>
<ENTRY colname=2><PARA>CONNECTY PCMCIA 144</PARA><PARA>144</PARA><PARA>288</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>OSITECH: </PARA></ENTRY>
<ENTRY colname=2><PARA>LapTALK Plus 14.4</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Pace: </PARA></ENTRY>
<ENTRY colname=2><PARA>Linnet 32 PLUS</PARA><PARA>Linnet 32 PLUS fx</PARA><PARA>UltraLink Thirty-Two Plus</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Penril: </PARA></ENTRY>
<ENTRY colname=2><PARA>Alliance V.32</PARA><PARA>Datalink 2400</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Piiceon: </PARA></ENTRY>
<ENTRY colname=2><PARA>Dispatcher</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>PNB: </PARA></ENTRY>
<ENTRY colname=2><PARA>14400</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>PowerBit: </PARA></ENTRY>
<ENTRY colname=2><PARA>14400 Modem</PARA><PARA>28800 Modem</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Power: </PARA></ENTRY>
<ENTRY colname=2><PARA>28.8 Data/Fax Modem</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Practical Peripherals: </PARA></ENTRY>
<ENTRY colname=2><PARA>2400SA MNP</PARA><PARA>2400SA V.42bis</PARA><PARA>1200</PARA><PARA>2400SA</PARA><PARA>9600SA</PARA><PARA>PM14400FXMT</PARA><PARA>14400FXSA</PARA><PARA>28.8 V.FC</PARA><PARA>ProClass 28.8</PARA><PARA>PM144MT II</PARA><PARA>PM288MT II V.FC</PARA><PARA>MC288MT II V.FC</PARA><PARA>Modem 14400FX</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Prometheus: </PARA></ENTRY>
<ENTRY colname=2><PARA>ProModem 1200</PARA><PARA>LineLink 14.4</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Pure Data: </PARA></ENTRY>
<ENTRY colname=2><PARA>PDMCIA V32bis</PARA><PARA>PDMCIA V.17</PARA><PARA>PDMCIA V.29</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Racal: </PARA></ENTRY>
<ENTRY colname=2><PARA>Milgo RMD 3232</PARA><PARA>Milgo RMD 3222</PARA><PARA>Milgo RMD 3264</PARA><PARA>ALM 3223</PARA><PARA>Vadic 9632VP</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Rockwell: </PARA></ENTRY>
<ENTRY colname=2><PARA>RG 2400 PC Modem</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>SBN: </PARA></ENTRY>
<ENTRY colname=2><PARA>2314L</PARA><PARA>2324L</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Sharp: </PARA></ENTRY>
<ENTRY colname=2><PARA>9624e</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>SmartLink: </PARA></ENTRY>
<ENTRY colname=2><PARA>FaxModem V.32</PARA><PARA>FaxModem V.32bis</PARA><PARA>FaxModem 28.8</PARA><PARA>Fax/Modem 144LC</PARA><PARA>Express 144</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Sonix: </PARA></ENTRY>
<ENTRY colname=2><PARA>Volante</PARA><PARA>Volante ISDN T/A</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Supra: </PARA></ENTRY>
<ENTRY colname=2><PARA>FaxModem V.32</PARA><PARA>FaxModem V.32bis</PARA><PARA>FaxModem 28.8</PARA><PARA>Fax/Modem 144LC</PARA><PARA>Express 144</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>TA210: </PARA></ENTRY>
<ENTRY colname=2><PARA>ISDN Terminator Adapter</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Telebit: </PARA></ENTRY>
<ENTRY colname=2><PARA>WorldBlazer</PARA><PARA>QBlazer</PARA><PARA>T1000</PARA><PARA>T1600</PARA><PARA>T2500</PARA><PARA>T3000</PARA><PARA>TrailBlazer Plus</PARA><PARA>TrailBlazer</PARA><PARA>/Octocom OSI 8396</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Telecom: </PARA></ENTRY>
<ENTRY colname=2><PARA>DataPlex 225</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Telelink: </PARA></ENTRY>
<ENTRY colname=2><PARA>IMS-08 Faxline</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Telenetics: </PARA></ENTRY>
<ENTRY colname=2><PARA>TC921</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Texas: </PARA></ENTRY>
<ENTRY colname=2><PARA>Instruments: V.32bis/V.17</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Toshiba: </PARA></ENTRY>
<ENTRY colname=2><PARA>PC-T144PF4 PCMCIA</PARA><PARA>T144PF4 PCMCIA</PARA><PARA>Adv. PCMCIA Modem</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Touchbase: </PARA></ENTRY>
<ENTRY colname=2><PARA>Worldport 1200</PARA><PARA>Worldport 2400</PARA><PARA>Worldport 9600</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Twincom: </PARA></ENTRY>
<ENTRY colname=2><PARA>96/42i</PARA><PARA>144DF</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Twinhead: </PARA></ENTRY>
<ENTRY colname=2><PARA>FB THV-1414</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>UDS: </PARA></ENTRY>
<ENTRY colname=2><PARA>PCTA120</PARA><PARA>FasTalk 2400</PARA><PARA>FasTalk 32x</PARA><PARA>FasTalk V.32/42b</PARA><PARA>FasTalkII</PARA><PARA>V.32</PARA><PARA>V.3225</PARA><PARA>V.3229</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Ven-Tel: </PARA></ENTRY>
<ENTRY colname=2><PARA>9600 Plus/Plus II</PARA><PARA>Pathfinder</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>V-Fast: </PARA></ENTRY>
<ENTRY colname=2><PARA>144/144</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Viva: </PARA></ENTRY>
<ENTRY colname=2><PARA>14.4/Fax</PARA><PARA>9624</PARA><PARA>14.4/9642e</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Western Datacom: </PARA></ENTRY>
<ENTRY colname=2><PARA>432 LineBkr V.32</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>WinBook: </PARA></ENTRY>
<ENTRY colname=2><PARA>XP 14.4</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Xircom: </PARA></ENTRY>
<ENTRY colname=2><PARA>Ethernet+Modem</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Zeos: </PARA></ENTRY>
<ENTRY colname=2><PARA>14.4 Data/Fax Modem</PARA><PARA> 14.4</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>Zoltrix: </PARA></ENTRY>
<ENTRY colname=2><PARA>14400</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>ZyXEL: </PARA></ENTRY>
<ENTRY colname=2><PARA>U-1496 </PARA></ENTRY>
</ROW>
</TBODY>
</TGROUP>
</INFORMALTABLE>
<BEGINPAGE PAGENUM=103 ID="BP82"><PARA></PARA>
</SECT1>
</APPENDIX>
<APPENDIX LABEL="B"><TITLE><BEGINPAGE PAGENUM=95 ID="BP83"><XMARK id="FM18631">Creating an INS File for a LAN Driver</TITLE><PARA>
If your 16-bit DOS ODI(tm) LAN driver will be installed with the installation utility, the utility must know how to set up the configuration file (NET.CFG). This means the utility must know each driver's parameter options and which choices the user must make. The driver installation information (.INS) file provides the installation utilities with this required information.</PARA>
<PARA>Each driver has only one .INS file even though the driver usually supports many boards. If the installation utility does not find an INS file for a driver, the utility does not create a NET.CFG file entry for the driver. The installation program uses the .INS file to prompt the user for the parameter options and values necessary to generate a NET.CFG file. Sample INS files are included at the end of this appendix.</PARA>
<PARA>When you have created your .INS file, copy it to the directory containing the LAN driver. </PARA>
<SECT1><TITLE>General Rules</TITLE><PARA>Your INS file must conform to the following rules and also to the conventions used in the examples at the end of this appendix.</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>The INS file must not contain blank lines or tabs. Space characters are not permitted between fields unless otherwise specified.</PARA>
</LISTITEM>
<LISTITEM><PARA>Items shown in angle brackets indicate that the user must supply information describing that aspect of the driver.</PARA>
<PARA>Example:</PARA>
<LITERALLAYOUT><USERINPUT>&lt;DriverName>
NE2000.COM
</USERINPUT></LITERALLAYOUT>
</LISTITEM>
<LISTITEM><PARA>Items shown in square brackets ([) and (]) are optional.</PARA>
<BEGINPAGE PAGENUM=96 ID="BP84"></LISTITEM>
</ITEMIZEDLIST>
</SECT1>
<SECT1><TITLE>File Syntax</TITLE><PARA>The format of the INS file for 16-bit DOS ODI drivers is shown below:</PARA>
<LITERALLAYOUT><USERINPUT>InS_StArT
&lt;DriverName>
&lt;Version>[,&lt;AssociatedFileList>]
^&lt;Board1 Description>
^&lt;Board2 Description>
$
$
$
[?&lt;Help Text>]
&lt;Parameter1 Definition>
&lt;Parameter2 Definition>
$
$
$
InS_EnD
</USERINPUT></LITERALLAYOUT>
<SECT2><TITLE>Signature Lines</TITLE><PARA>Note the initial and final lines:</PARA>
<LITERALLAYOUT><USERINPUT>InS_StArT
$
$
$
InS_EnD
</USERINPUT></LITERALLAYOUT>
<PARA>These lines illustrate the following crucial points:</PARA>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA>The <USERINPUT>InS_StArt</USERINPUT> and <USERINPUT>InS_EnD</USERINPUT> signature lines shown above bracket the driver installation information.</PARA>
</LISTITEM>
<LISTITEM><PARA>The body of the INS file is preceded by the <USERINPUT>InS_StArT</USERINPUT> keyword and is terminated by the <USERINPUT>InS_EnD</USERINPUT> keyword. </PARA>
<BEGINPAGE PAGENUM=97 ID="BP85"></LISTITEM>
</ITEMIZEDLIST>
</SECT2>
<SECT2><TITLE>Driver Name</TITLE><PARA>The driver filename, including the .COM or .EXE extension, is the first line of the installation information. Installation uses the driver filename to generate the NET.CFG Link Driver <USERINPUT>&lt;DriverName></USERINPUT> command.</PARA>
</SECT2>
<SECT2><TITLE>Version</TITLE><PARA>The version field indicates the version of the INS specification to which the INS file is written. The version field enables installation utilities to properly handle any future changes to the specification. The version number format is "<REPLACEABLE>X</REPLACEABLE>.<REPLACEABLE>X</REPLACEABLE>." For this specification, the version is 1.1.</PARA>
</SECT2>
<SECT2><TITLE>Associated File List</TITLE><PARA>The version number may be optionally followed by a list of associated files separated by commas. The user must copy these files, along with the driver, to the area where the user is installing the client pieces. Firmware BIN files and special configuration or diagnostic utilities for the adapter or driver are examples of associated files.</PARA>
</SECT2>
<SECT2><TITLE>Board Description</TITLE><PARA>The "Board Description(s)" provide a list of adapters and related information that the SETUP.INI uses. More than one board can be listed if a single driver will work with a given adapter and its clones. Place multiple board descriptions on separate lines in the [<USERINPUT>Adapters</USERINPUT>] section of the SETUP.INI file and only use them when the hardware options are identical for all the boards. The user generally knows what board he/she has installed, but not necessarily what driver he/she should use with that board.</PARA>
<PARA>Each "Board Description" is preceded by a caret (^) and has the following format:</PARA>
<PARA><EMPHASIS>syntax</EMPHASIS>:</PARA>
<LITERALLAYOUT><USERINPUT>&lt;BoardName,DriverName,BusCode[,ProductID]>
</USERINPUT></LITERALLAYOUT>
<PARA><EMPHASIS>example</EMPHASIS>:</PARA>
<LITERALLAYOUT><USERINPUT>Novell NE2000,NE2000.COM,IEO
<BEGINPAGE PAGENUM=98 ID="BP86"></USERINPUT></LITERALLAYOUT>
<ITEMIZEDLIST MARK=BULLET><LISTITEM><PARA><REPLACEABLE>BoardName</REPLACEABLE> is the full name of the network adapter. This field can contain spaces and can be a maximum of 48 characters long.</PARA>
</LISTITEM>
<LISTITEM><PARA><REPLACEABLE>DriverName</REPLACEABLE> is the filename (including the extension) of the board's driver. This field can be a maximum of 13 characters long.</PARA>
</LISTITEM>
<LISTITEM><PARA><REPLACEABLE>BusCode</REPLACEABLE> is a six character code depicting the bus type(s) supported for the adapter. The code is described below:</PARA>
<INFORMALTABLE><TGROUP COLS=3><COLSPEC colname=1 colwidth="10*">
<COLSPEC colname=2 colwidth="7*">
<COLSPEC colname=3 colwidth="16*">
<THEAD><ROW><ENTRY colname=1><PARA>Character</PARA></ENTRY>
<ENTRY colname=2><PARA>Code</PARA></ENTRY>
<ENTRY colname=3><PARA>Description</PARA></ENTRY>
</ROW>
</THEAD>
<TBODY><ROW><ENTRY colname=1><PARA>1st character</PARA></ENTRY>
<ENTRY colname=2><PARA>I (alpha)</PARA></ENTRY>
<ENTRY colname=3><PARA>supports ISA adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA></PARA></ENTRY>
<ENTRY colname=2><PARA>0 (numeric)</PARA></ENTRY>
<ENTRY colname=3><PARA>does not support ISA adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>2nd character</PARA></ENTRY>
<ENTRY colname=2><PARA>E (alpha)</PARA></ENTRY>
<ENTRY colname=3><PARA>supports EISA adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA></PARA></ENTRY>
<ENTRY colname=2><PARA>0 (numeric)</PARA></ENTRY>
<ENTRY colname=3><PARA>does not support EISA adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>3rd character</PARA></ENTRY>
<ENTRY colname=2><PARA>M (alpha)</PARA></ENTRY>
<ENTRY colname=3><PARA>supports MCA adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA></PARA></ENTRY>
<ENTRY colname=2><PARA>0 (numeric)</PARA></ENTRY>
<ENTRY colname=3><PARA>does not support MCA adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>4th character</PARA></ENTRY>
<ENTRY colname=2><PARA>A (alpha)</PARA></ENTRY>
<ENTRY colname=3><PARA>supports PCMCIA adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA></PARA></ENTRY>
<ENTRY colname=2><PARA>0 (numeric)</PARA></ENTRY>
<ENTRY colname=3><PARA>does not support PCMCIA adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>5th character</PARA></ENTRY>
<ENTRY colname=2><PARA>P (alpha)</PARA></ENTRY>
<ENTRY colname=3><PARA>supports PCI adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA></PARA></ENTRY>
<ENTRY colname=2><PARA>0 (numeric)</PARA></ENTRY>
<ENTRY colname=3><PARA>does not support PCI adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>6th character</PARA></ENTRY>
<ENTRY colname=2><PARA>V (alpha)</PARA></ENTRY>
<ENTRY colname=3><PARA>supports VESA Local Bus adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA></PARA></ENTRY>
<ENTRY colname=2><PARA>0 (numeric)</PARA></ENTRY>
<ENTRY colname=3><PARA>does not support VESA Local Bus adapters</PARA></ENTRY>
</ROW>
</TBODY>
</TGROUP>
</INFORMALTABLE>
<NOTE><PARA>Because all ISA boards work in EISA machines, "I" and "E" should both be used for ISA boards. This enables ISA boards installed in an EISA bus to appear in the installation utility. Keep in mind that ISA boards installed in EISA machines retain ISA functionality and features. </PARA>
</NOTE>
<BEGINPAGE PAGENUM=98 ID="BP87"><BEGINPAGE PAGENUM=99></LISTITEM>
<LISTITEM><PARA>The <REPLACEABLE>ProductID</REPLACEABLE> field is optional and only applies to MCA and EISA boards. This field contains the ID string that is stored in the POS registers of Micro Channel* and in configuration registers of EISA machines. The installation utility uses this ID string to select the appropriate driver for the board found in the machine. This field is left blank for ISA boards.</PARA>
</LISTITEM>
</ITEMIZEDLIST>
</SECT2>
<SECT2><TITLE>Help Text</TITLE><PARA>You can supply one line of optional help text after the board description lines. The help text is preceded with a question mark (?), can be up to 256 bytes in length (not including the question mark), and can contain spaces. The installation program automatically word wraps the help text.   The width of the help windows will probably vary because installation programs on different platforms display a different number of characters on a line.</PARA>
</SECT2>
<SECT2><TITLE>Parameter Definitions</TITLE><PARA>The <REPLACEABLE>Parameter Definition</REPLACEABLE> section of the INS file specifies the configurable parameters for the driver and defines the valid options for each parameter. The parameter format is described in the next section. </PARA>
<PARA>If the network board can be configured by software and does not need to use the NET.CFG file, there should be no parameter definitions.</PARA>
<BEGINPAGE PAGENUM=99 ID="BP88"><BEGINPAGE PAGENUM=100></SECT2>
</SECT1>
<SECT1><TITLE>Parameter Syntax</TITLE><PARA>The NET.CFG file is created with parameter keywords and values. The INS file can define standard and/or custom parameters. The standard driver parameter keywords are: BUS ID, IRQ, PORT, MEM, DMA, SLOT, NODE ADDRESS, and FRAME (see <CITETITLE>ODI Specification: DOS Client HSMs</CITETITLE>, document version 4.0). The INS file can specify as many parameters as are needed to describe the available hardware and software options. </PARA>
<PARA>A parameter definition has the following format:</PARA>
<LITERALLAYOUT><USERINPUT>&lt;ParameterCode>(&lt;ParameterKeyword>)&lt;ParameterName>
[&lt;Parameter Help Text>]
   &lt;Valid Parameter Options>
$
$
$
</USERINPUT></LITERALLAYOUT>
<SECT2><TITLE>Parameter Code</TITLE><PARA>The <REPLACEABLE>ParameterCode</REPLACEABLE> field is eight characters long. The characters are defined as follows:</PARA>
<SECT3><TITLE>First character</TITLE><PARA>The code's first character specifies the prompt format the installation utility will use to display the parameter on the screen for the user.   This character will also affect how the <USERINPUT>&lt;valid parameter options></USERINPUT> are indicated. The possible values for the first character are listed below.</PARA>
<INFORMALTABLE><TGROUP COLS=2><COLSPEC colname=1 colwidth="10*">
<COLSPEC colname=2 colwidth="16*">
<TBODY><ROW><ENTRY colname=1><PARA>!</PARA></ENTRY>
<ENTRY colname=2><PARA>Select only one option from the list.</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>*</PARA></ENTRY>
<ENTRY colname=2><PARA>Select more than one option from the list.</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>$</PARA></ENTRY>
<ENTRY colname=2><PARA>User input within a range (slightly different from above).</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>#</PARA></ENTRY>
<ENTRY colname=2><PARA>Reserved for future use.</PARA></ENTRY>
</ROW>
</TBODY>
</TGROUP>
</INFORMALTABLE>
<BEGINPAGE PAGENUM=101 ID="BP89"></SECT3>
<SECT3><TITLE>Second character</TITLE><PARA>The code's second character indicates whether the user must select this parameter value or whether it is optional. This character also indicates whether a NET.CFG entry will be generated.</PARA>
<INFORMALTABLE><TGROUP COLS=3><COLSPEC colname=1 colwidth="10*">
<COLSPEC colname=2 colwidth="7*">
<COLSPEC colname=3 colwidth="16*">
<THEAD><ROW><ENTRY colname=1><PARA>Code</PARA></ENTRY>
<ENTRY colname=2><PARA>Usage</PARA></ENTRY>
<ENTRY colname=3><PARA>Description</PARA></ENTRY>
</ROW>
</THEAD>
<TBODY><ROW><ENTRY colname=1><PARA>R (alpha)</PARA></ENTRY>
<ENTRY colname=2><PARA>Required</PARA></ENTRY>
<ENTRY colname=3><PARA>This parameter must be selected. A NET.CFG entry is always generated.</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>0 (numeric)</PARA></ENTRY>
<ENTRY colname=2><PARA>Optional</PARA></ENTRY>
<ENTRY colname=3><PARA>If nothing is selected, no NET.CFG entry will be generated.</PARA></ENTRY>
</ROW>
</TBODY>
</TGROUP>
</INFORMALTABLE>
</SECT3>
<SECT3><TITLE>Last characters</TITLE><PARA>The last six characters indicate the bus type dependency of the parameter. The installation utility uses this code to determine whether the parameter is to be displayed (used), depending on the bus type of the machine. The <REPLACEABLE>ParameterCode's</REPLACEABLE> 3 bus type characters are defined as follows:</PARA>
<INFORMALTABLE><TGROUP COLS=3><COLSPEC colname=1 colwidth="10*">
<COLSPEC colname=2 colwidth="7*">
<COLSPEC colname=3 colwidth="16*">
<THEAD><ROW><ENTRY colname=1><PARA>Character</PARA></ENTRY>
<ENTRY colname=2><PARA>Code</PARA></ENTRY>
<ENTRY colname=3><PARA>Description </PARA></ENTRY>
</ROW>
</THEAD>
<TBODY><ROW><ENTRY colname=1><PARA>3rd character</PARA></ENTRY>
<ENTRY colname=2><PARA>I (alpha)</PARA></ENTRY>
<ENTRY colname=3><PARA>supports ISA adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA></PARA></ENTRY>
<ENTRY colname=2><PARA>0 (numeric)</PARA></ENTRY>
<ENTRY colname=3><PARA>does not support ISA adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>4th character</PARA></ENTRY>
<ENTRY colname=2><PARA>E (alpha)</PARA></ENTRY>
<ENTRY colname=3><PARA>supports EISA adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA></PARA></ENTRY>
<ENTRY colname=2><PARA>0 (numeric)</PARA></ENTRY>
<ENTRY colname=3><PARA>does not support EISA adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>5th character</PARA></ENTRY>
<ENTRY colname=2><PARA>M (alpha)</PARA></ENTRY>
<ENTRY colname=3><PARA>supports MCA adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA></PARA></ENTRY>
<ENTRY colname=2><PARA>0 (numeric)</PARA></ENTRY>
<ENTRY colname=3><PARA>does not support MCA adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>6th character</PARA></ENTRY>
<ENTRY colname=2><PARA>A (alpha)</PARA></ENTRY>
<ENTRY colname=3><PARA>supports PCMCIA adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA></PARA></ENTRY>
<ENTRY colname=2><PARA>0 (numeric)</PARA></ENTRY>
<ENTRY colname=3><PARA>does not support PCMCIA adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>7th character</PARA></ENTRY>
<ENTRY colname=2><PARA>P (alpha)</PARA></ENTRY>
<ENTRY colname=3><PARA>supports PCI adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA></PARA></ENTRY>
<ENTRY colname=2><PARA>0 (numeric)</PARA></ENTRY>
<ENTRY colname=3><PARA>does not support PCI adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>8th character</PARA></ENTRY>
<ENTRY colname=2><PARA>V (alpha)</PARA></ENTRY>
<ENTRY colname=3><PARA>supports VESA Local Bus adapters</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA></PARA></ENTRY>
<ENTRY colname=2><PARA>0 (numeric)</PARA></ENTRY>
<ENTRY colname=3><PARA>does not support VESA Local Bus adapters</PARA></ENTRY>
</ROW>
</TBODY>
</TGROUP>
</INFORMALTABLE>
<BEGINPAGE PAGENUM=102 ID="BP90"><PARA>For example, a driver running on an ISA or EISA bus may require the PORT parameter. However, a driver running on an MCA machine may require only the SLOT parameter.</PARA>
<LITERALLAYOUT><USERINPUT>!RIE0000(PORT)Base I/O Port
$
$
$
!R00M000(SLOT)Slot Number
$
$
$
</USERINPUT></LITERALLAYOUT>
</SECT3>
<SECT3><TITLE>Parameter Keyword</TITLE><PARA>The parameter's NET.CFG file keyword immediately follows the parameter code characters. The parameter keyword is enclosed in parenthesis and can be up to a maximum of 20 characters. The user-selected value for that parameter is placed in the NET.CFG file if no keyword (empty parenthesis) exists. These keywords can be custom keywords or any of the standard keywords listed in <IXREF idref="FM19121">Table B-1 on page 103</IXREF>.</PARA>
</SECT3>
<SECT3><TITLE>Parameter Name</TITLE><PARA>The parameter name follows the parameter keyword. This name is the title the installation utility displays to the user. The length of this field is limited to 30 characters. The parameter names are given in <IXREF idref="FM19121">Table B-1 on page 103</IXREF>.</PARA>
<BEGINPAGE PAGENUM=102 ID="BP91"><BEGINPAGE PAGENUM=103></SECT3>
<SECT3><TITLE>Parameter Help Text</TITLE><PARA>A single line of optional help text may follow the parameter line. This line is preceded with a question mark (?) and can be a maximum of 256 characters long. You should only use help text with custom keywords, because the installation utility supplies help text for each standard keyword. Any help text must follow the keyword line and precede the parameter value lines described next in the NET.CFG file. If help is supplied with a standard keyword such as PORT, it will be appended to the default help text available from the installation utility.</PARA>
<PARA>The following table lists the standard parameter keywords and the default help text supplied by the installation utility:</PARA>
<TABLE label="B-1" PGWIDE=1><TITLE><XMARK id="FM19121"> Standard Parameter Keywords</TITLE><TGROUP COLS=3><COLSPEC colname=1 colwidth="9*">
<COLSPEC colname=2 colwidth="9*">
<COLSPEC colname=3 colwidth="16*">
<THEAD><ROW><ENTRY colname=1><PARA>Parameter Keywords</PARA></ENTRY>
<ENTRY colname=2><PARA>Parameter Names</PARA></ENTRY>
<ENTRY colname=3><PARA>Default Parameter Help Text</PARA></ENTRY>
</ROW>
</THEAD>
<TBODY><ROW><ENTRY colname=1><PARA>IRQ</PARA></ENTRY>
<ENTRY colname=2><PARA>Hardware Interrupt</PARA></ENTRY>
<ENTRY colname=3><PARA>"Select the interrupt level that corresponds to the interrupt setting on the board or other device. The interrupt setting must be unique (one not used by another device in the machine)".</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>PORT</PARA></ENTRY>
<ENTRY colname=2><PARA>Base I/O Port</PARA></ENTRY>
<ENTRY colname=3><PARA>"Select the port value (base I/O address) that corresponds to the port address setting on the board or other device. Make sure the block of I/O addresses does not overlap the addresses of another device in the machine".</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>MEM</PARA></ENTRY>
<ENTRY colname=2><PARA>Memory I/O Address</PARA></ENTRY>
<ENTRY colname=3><PARA>"Select the memory address that corresponds to the memory setting on the board or other device. Make sure the block of memory addresses does not overlap the addresses of another device in the machine".</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>DMA</PARA></ENTRY>
<ENTRY colname=2><PARA>DMA</PARA></ENTRY>
<ENTRY colname=3><PARA>"Select the DMA channel that corresponds to the DMA setting on the board or other device. Make sure the DMA (Direct Memory Access) channel does not conflict with that of another device in the machine".</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>SLOT</PARA></ENTRY>
<ENTRY colname=2><PARA>Slot</PARA></ENTRY>
<ENTRY colname=3><PARA>"Select the slot number that corresponds to the expansion slot where the board or other device is installed".</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>NODE ADDRESS</PARA></ENTRY>
<ENTRY colname=2><PARA>Node Address</PARA></ENTRY>
<ENTRY colname=3><PARA>"Do not change this address unless you are prepared to administer local addresses according to the IEEE 802.2 specifications. The driver defaults to the node address on the board".</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>FRAME</PARA></ENTRY>
<ENTRY colname=2><PARA>Frame Type</PARA></ENTRY>
<ENTRY colname=3><PARA>"Select the frame type(s) used by the protocol(s) that your network requires. Make sure you have both the server and client configured for the same frame type".</PARA></ENTRY>
</ROW>
<ROW><ENTRY colname=1><PARA>BUS ID</PARA></ENTRY>
<ENTRY colname=2><PARA>Bus ID</PARA></ENTRY>
<ENTRY colname=3><PARA>"Select the bus type that corresponds to the bus used by the network interface card".</PARA></ENTRY>
</ROW>
</TBODY>
</TGROUP>
</TABLE>
<BEGINPAGE PAGENUM=104 ID="BP92"></SECT3>
</SECT2>
<SECT2><TITLE>Valid Parameter Options</TITLE><PARA>Each line that follows the parameter description (up to the next parameter description and not including any help) is interpreted as a possible value for that parameter. Note that these are TEXT values and can be no longer than 20 characters. These values must also be in the same format as they would in the NET.CFG file.</PARA>
<PARA>The valid parameter values are specified in either <EMPHASIS>list</EMPHASIS> or <EMPHASIS>range</EMPHASIS> notation, depending on the first character of the <REPLACEABLE>ParameterCode</REPLACEABLE>. When you specify parameter values in a list form, you must enter each valid parameter value on a separate line.</PARA>
<PARA>Value <EMPHASIS>ranges</EMPHASIS> use only three value lines. The first value line is the beginning of the range. The second is the end of the range. The third is optional and is a default value preceded with an @ sign. If a default value is specified, the installation utility will generate the NET.CFG entry. If a default value is not specified, the installation utility will only generate a NET.CFG entry if the user enters a value. If the parameter is required, you must specify a third default value line.</PARA>
<BEGINPAGE PAGENUM=105 ID="BP93"><PARA>The installation utility treats these values as strings. This allows the user to enter an L or M after the NODE ADDRESS parameter, designating in the NET.CFG file that the node address specified is in canonical (LSB) or noncanonical (MSB) format (see the <CITETITLE>ODI Specification Supplement: Canonical and Noncanonical Addressing</CITETITLE>, part number 107-000059-001). </PARA>
<SECT3><TITLE>Default Parameter Value   </TITLE><PARA>You designate a default parameter value in the INS file by preceding the value line with an @ sign. In the example on the following page, the board setting defaults are INT 3 and PORT 300.</PARA>
<PARA>All required parameters must have a default specified. If a parameter is optional, you need not specify the default. The installation utility always displays a blank selection to the user for optional parameters. If no default is specified, then the "no value" option becomes the default. A NET.CFG entry is generated for any option other than the "no value" option. The installation utility does not generate a NET.CFG entry for a "no value" option.</PARA>
<PARA>The default settings in the driver INS file should match the default jumper settings of the network board as shipped by the manufacturer, where possible. If the jumper settings cannot be guaranteed, the defaults should match the most likely jumper settings, or the most common user settings.</PARA>
<BEGINPAGE PAGENUM=105 ID="BP94"><BEGINPAGE PAGENUM=106></SECT3>
<SECT3><TITLE>Example INS File (NE2000)</TITLE><LITERALLAYOUT><USERINPUT>InS_StArT
NE2000.COM
1.0
^Novell/Eagle NE2000,NE2000.COM,IE0000
?Please select the options that match your board's jumper settings.
!RIE0000(INT)Hardware Interrupt
2
@3
5
7
!RIE0000(PORT)Base I/O Port
@300
320
340
360
$OIE0000(NODE ADDRESS)Optional Node Address
0
FFFFFFFFFFF
*RIE0000(FRAME)Media Frame Type(s)
?NOTE:  Ethernet_802.2 is now the default frame type for ODI drivers.  Existing LANs may be using Ethernet_802.3.
@Ethernet_802.2
Ethernet_802.3
Ethernet_II
Ethernet_SNAP
InS_EnD
<BEGINPAGE PAGENUM=106 ID="BP95"><BEGINPAGE PAGENUM=107></USERINPUT></LITERALLAYOUT>
</SECT3>
<SECT3><TITLE>Example INS File (using various options)</TITLE><LITERALLAYOUT><USERINPUT>InS_StArT
PCN2.COM
1.0,ROUTE.COM
^IBM PC NetWork BroadBand or BaseBand Adapter II,PCN2.COM,IE0000
^IBM PC NetWork BroadBand or BaseBand Adapter/2,PCN2.COM,00M000,EFEF
?This board may be used with Source Routing.  If your network is using Source Routing simply load the ROUTE.COM file after the PCN2.COM file has been loaded.
!RIE0000(PORT)Base I/O Port
@620
628
!O00M000(SLOT)Optional Slot Number
1
2
3
4
5
6
7
8
$OIEM000(NODE ADDRESS)Optional Node Address
0
FFFFFFFFFFF
!OIEM000()Primary or Alternate Adapter
?If your adapter is configured for Alternate, please select this option.
ALTERNATE
*RIEM000(FRAME)Media Frame Type
@IBM_PCN2_802.2 MSB
IBM_PCN2_802.2 LSB
IBM_PCN2_SNAP MSB
IBM_PCN2_SNAP LSB
InS_EnD
<BEGINPAGE PAGENUM=108 ID="BP96"></USERINPUT></LITERALLAYOUT>
<PARA></PARA>
</SECT3>
</SECT2>
</SECT1>
</APPENDIX>
</BOOK>
