Black Box 4/BlackBox.cdr/w3_comms/nettool.arj/WINUP2.TXT

Text File | 1991-06-21 | 50.7 KB | 1,625 lines

NOTE:  References to Figures in this text file do not apply.

Disclaimer
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.

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.

Novell, Inc.                           Documentation FAX:  [phone]
122 East 1700 South                    Tech. Support VOICE:  1-800-NetWare
Provo, Utah
U.S.A.

NetWare Workstation for Windows
1st Edition (June 1991)
Novell Part Number 100-001002-001

Trademarks
Novell, the N design, and NetWare are registered trademarks of Novell, Inc.
Windows is a trademark of Microsoft Corporation.

This guide is for network users who are running Windows v3.0 on
a NetWare network.

You should already be familiar with your computer and the
software (including Windows and NetWare) running on your
computer.

This guide explains how to use NetWare utilities which have been
designed to work as Windows applications.  It doesn't explain how
to perform all network tasks or how to use every network
command.  For more information on network tasks and
commands, see the manuals for your version of NetWare.

1      Installing NetWare Workstation for Windows

Introduction

The NetWare Workstation for Windows diskette contains files to
update your NetWare device driver files, load NetWare Tools, and
update your NetWare C Interface for Windows files (.DLL files).

The NetWare Workstation for Windows includes NetWare Tools
which let you perform certain network tasks. You can
*      Map network drives
*      Select network printers
*      Attach to or detach from file servers
*      List network users
*      View volume information
*      Set or change passwords
*      Send messages to network users and groups
*      Block or allow messages from other users
*      Customize your mappings and printer information for specific
       tasks

You can also use the Network icon and the Printer icon in the
Control Panel to complete some network tasks.

Windows must already be installed on your file server before you install the
NetWare Tools and drivers on your workstation.

Using the INSTALL program

The NetWare Workstation for Windows diskette contains an INSTALL
program that loads the NetWare drivers, NetWare Tools, and .DLL
files. INSTALL copies these files to the \WINDOWS and \SYSTEM
subdirectories in your Windows directory (whether it is on the
network or on your workstation). It also updates your SYSTEM.INI
and WIN.INI files.

For specific information about the files that will be updated and
changes that will be made to your SYSTEM.INI and WIN.INI files,
select the Help menu in INSTALL and choose "Using NetWare with
Windows."

Consider the following items when installing and configuring the
NetWare operating system with Windows.

Workstation shell files

Windows requires that you use workstation shell files (NETx.COM,
XMSNETx.COM, or EMSNETx.COM, and IPX.COM) version 3.01 or
later. If your shell files are an earlier version you will get an error
message when installing Windows.

Upgrading utilities

If you use the NetWare BINDFIX utility, you must update it to v1.2.
(v1.2 is included on the NetWare Workstation for Windows diskette).

Other NetWare utilities may need to be updated to function
properly with Windows. See Appendix A for a list of these utilities.

Show dots = on

You should add the following line to your NET.CFG or SHELL.CFG
file:

SHOW DOTS = ON

This allows you to see the parent directory [..] when you list
subdirectories. If you do not use SHOW DOTS = ON, your directory
listings will not show the parent directory, and you will not be able
to return to the parent directory after you change to a subdirectory.

Before running INSTALL

The first time INSTALL is run, it updates NetWare drivers and other
files in the Windows \SYSTEM directory. If you are using a shared
network version of Windows, the system administrator should run
INSTALL first to update the NetWare drivers and other files. When
INSTALL is run subsequent times, it will update only the users' .INI
files.

Before you begin INSTALL, you must

*      Exit Windows completely. Do not run INSTALL from the DOS
prompt within Windows.

*      Be in the directory that contains Windows (or set a path to your
Windows directory). INSTALL will start Windows.

*      Have Read, Write, and Modify rights in the directory where you
will run INSTALL and in the \WINDOWS directory. (This does
not apply if your directories are local directories.)

Only one user at a time can use INSTALL. INSTALL uses a temporary
file that only one user at a time can access. If you receive File
Sharing Errors in Windows or network errors from DOS, you are
trying to run INSTALL at the same time as someone else. Run
INSTALL from a diskette or a directory in your personal network
workspace, or wait until the other user exits INSTALL.

If you are installing Novell NetWare Workstation for Windows to a
shared network configuration, all network users must exit
Windows. Since INSTALL updates the NetWare drivers that are in
the Windows directories, no one can be using these drivers.

Running INSTALL


1.     At the DOS prompt, type

pathname/INSTALL <Enter>

Replace pathname with the full directory path leading to the directory where
NetWare INSTALL is located.

For example, if you are running INSTALL from a diskette in drive A, type

A:\INSTALL <Enter>

If you are running INSTALL from a network directory, you must include the drive
letter. For example, type

G:\WININST\INSTALL <Enter>

(You can use Windows startup flags, such as /R, with INSTALL.)

The INSTALL program will load the NetWare Tools files and update other files
needed to run Windows with NetWare. For help while using INSTALL, choose
the Help menu.

You see the NetWare Windows Workstation Services - INSTALL screen.

Running INSTALL



Figure 1-1
INSTALL window



The screen consists of three parts.

System Defaults. Shows the defaults used by your system. It shows

*      The type of installation you are performing: a shared network installation or
a local installation

*      The directory you are running INSTALL from

*      The directory you are installing to

Running INSTALL



Instructions. Lists the steps you need to do to complete the installation.
Follow the steps in the order listed.

Action. Explains what tasks INSTALL completes. It also informs you if an error
occurs, and gives you steps to correct the error.

2.     Choose README to read important installation information.

3.     Choose OK to begin the installation.

After the drivers and files have been loaded, the installation is complete.

When you start Windows, the NetWare Tools icon will appear at the
bottom of the screen. When you choose this icon, the NetWare
Tools window appears. This window displays icons for the NetWare
tasks you can complete in Windows. You can also create a Program
Manager group that contains the NetWare Tools icons.

If you do not want the Novell NetWare icon to appear on the
desktop, go to "Remove automatic loading" on page 7.

To create a Program Manager group that contains the NetWare
Tools icons, go to "Create a Novell NetWare Program Manager
group" on page 8.

Remove automatic
loading



1.     To remove automatic loading, choose the NetWare Tools icon.

2.     Select the system menu.

3.     Select SETUP from the menu.

The Install NWTools window appears.

4.     Deselect Load Automatically.

5.     Choose Install

The NetWare Tools icon will no longer appear on the desktop.

Create a Novell
NetWare Program
Manager group



1.     To create a Program Manager group that contains the NetWare Tools, choose the NetWare
Tools icon.

2.     Select the system menu.

3.     Select SETUP from the menu.

The Install NWTools window appears.

4.     Select Create Program Manager Groups

5.      Choose Install.

This will create a Novell NetWare Program Manager group. This group will
appear each time you start Windows.

2      Using NetWare Tools

Introduction

After the NetWare Tools have been installed, you can access them
by choosing the NetWare Tools icon from the desktop or by
choosing the Novell NetWare icon from the Program Manager.

Figure 2-1
Novell NetWare
window



To see specific help for running a NetWare tool on Windows, select
an icon; then press <F1>.

The following sections explain each NetWare Tool.

Map

When you choose the Map icon , the Network-Drive Connections
dialog box appears. You can

*      Map network drives

*      Modify existing drives

*      Delete drives

*      Map a drive to a root

Figure 2-2
Network-Drive
Connections dialog
box


The dialog box displays drive letters and the directories that they
are mapped to. Existing search drives are listed in the bottom box.
The drive mappings are the same for all DOS prompts you open. If
you change the drive mappings, drive mappings for all sessions will
change.

The following sections explain the dialog box and the tasks you can
perform. For more information on using Map, press <F1>.

Fields

Data Drives. Lists the drives you have mapped to local and network
directories. You can specify drive letters A through Z; however, the
higher letters are usually used by search drives. The brackets in the
path denote the root.

Path (box). Lists the drive mapping you want to add, delete, or
change. You can select an existing drive from the data drives or
search drives list. To enter a new drive, choose the Browse button,
or select the Path box and type in a drive.

Search drives. Lists existing search drives. The brackets in the path
denote the root.

Operation. Allows you to map a drive or delete an existing drive.

Path (buttons). Allows you to view network servers, volumes, and
directories, and to map a drive to the root directory.

Buttons

Close. Closes this dialog box. You will not be asked to confirm
changes; all changes are made to the mappings immediately.

Map. Sets a drive mapping. The drive you want to set must be listed
in the Path box.

Map Delete. Deletes the drive mapping that is listed in the Path
box.

Browse. Allows you to view network servers, volumes, and
directories. When you choose this button, the Browse Connections
dialog box appears. This dialog box lists the servers you are attached
to and the volumes and directories available on those servers. You
can attach to or detach from servers by using the Attach or Detach
buttons. When the path you want is listed at the top of the box,
choose OK.

Set Root. Allows you to map a drive as a fake root. A fake root is a
subdirectory that functions as a root directory. NetWare lets you
map a search drive to a fake root (a directory where rights can be
assigned to users). Enter the path in the path box, then place the
cursor where you want to set the root. Then choose Set Root.

Printers

When you choose the Printers icon , the Printers - Network
Connections dialog box appears. This dialog box allows you to

*      Capture a local printing port to an existing queue

*      End a capture

*      Set options

*      Attach to or detach from other file servers

Figure 2-3
Printers - Network
Connections dialog
box



Data sent to a local printer port can be routed to a network print
queue. Your network printer connections and available network
queues are listed.

The following sections explain the dialog box and the tasks you can
perform. For more information on using Printers, press <F1>.

Fields

Network Printer Connections. Lists your printer ports and the
servers and print queues they will go to.

Available Queues. Lists the available queues on the servers you are
attached to. To attach to or detach from additional servers, choose
the Other Servers button.

Operation. Allows you to connect a queue to a printer port or to
disconnect a queue from a printer port.

Buttons

Close. Closes this dialog box. You will not be asked to confirm
changes.

Options. Sets the printing options for the port you have selected.
When you choose this button, the Printer Options dialog box
appears. The options are explained below.

Notify. Informs you that your data has been printed. A message
appears at the bottom of your screen. It will not notify you if the
printer has a problem or if the job cannot be printed.

Form Feed. Enables form feed after your print job has been printed.
This means that the printer starts printing the next job at the top of
the next sheet of paper.

Copies. Indicates how many copies you want to print. Default: 1.
Maximum: 255. Minimum: 1.

Enable Tabs. Specifies the number of characters in one tab stop.
Choose this box if your application does not have a print formatter
(most applications do). Default: 8. Maximum: 18. Minimum: 0.

Enable Timeout. Allows you to print from an application without
exiting the application. This option sends data to the printer a
specified number of seconds after the application last writes to a
file. If your timeout is not long enough, you may have problems
printing some files, especially files with graphics. Increase the
timeout if only parts of files are being printed or if the files do not
print at all. Default: 90. Maximum: 1000. Minimum: 0.

Enable Banner. Specifies the text on the banner page. Enter the text
you want to appear on the lower part of the banner page in the
Banner Text box. Your username appears in the Banner Name box;
it will be printed on the top part of the banner page.

Form Name. Specifies which form to print the job on.

Connect. Connects a print queue to the selected port.

Disconnect. Disconnects the print queue from the selected port.

Other Servers. Allows you to attach to or detach from other file
servers.

Attachments

When you choose the Attachments icon , the Attachments dialog
box appears.

Use the Attachments dialog box to attach (connect) your
workstation to a file server.

Figure 2-4
Attachments dialog
box



You cannot log in from Windows; you must log in before Windows is started.
Once you are in Windows, use the Attachments Tool to attach to other servers.
You cannot log out of the network while you are in Windows. To log out, exit
Windows; then use the LOGOUT command at the DOS command line.

The following sections explain the dialog box and the tasks you can
perform. For more information on using Attachments, press <F1>.

Fields

Unattached Servers. Lists the available servers on your network
that you are not attached to.

Attached Servers. Lists the servers you are attached to.

Name. Lists your username for the server you want to attach to. If
the username is incorrect, type in the correct one.

Password. Type your password for the server you want to attach to
(if required).

Buttons

Attach. Attaches you to the specified server. Highlight the server
you want to attach to; then choose Attach.

Detach. Detaches you from the specifed server. Highlight the server
you want to detach from; then choose Detach.

Close. Closes this dialog box.

UserList

When you choose the UserList icon, the UserList dialog box
appears.

Figure 2-5
UserList dialog box



Use the UserList dialog box to list the users attached to the file
server. The information on this screen cannot be changed.

The following sections explain the dialog box and the tasks you can
perform. For more information on using UserList, press <F1>.

Fields

User List on Server. Displays the server for which you want to see
a list of users. You see information about the users attached to that
server.

Sort Order. Allows you to list users by connection number
(numerical) or by name (alphabetical).

Show Full Names. Lists users' full names. If a full name has not
been assigned, the user's login name is listed.

Buttons

Send Message. Use to send a message to a selected user. Highlight
the user; then choose Send. The Send Message dialog box appears.
Enter the message in this box.

Close. Closes this dialog box.

Volinfo

When you choose the Volinfo icon , the Volume Information dialog
box appears.

Figure 2-6
Volinfo dialog box



The information on this screen can't be changed.

The following sections explain the dialog box and the tasks you can
perform. For more information on using Volinfo, press <F1>.

Fields

Volume Information on Server. Displays the server for which you
want to view volume information. You see directory and space
information for all volumes on the server. The solid portion of the
circle indicates the amount of directories (or space) being used.

Update Interval. Specifies the amount of time (in seconds)
between screen updates. Enter any number from 0 to 9999.

Display Format. Allows you to display the directory and space
information in megabytes or kilobytes.

Button

Close. Closes this dialog box.

Set passwords

When you choose the Setpass icon, the SetPass dialog box appears.

Use this dialog box to set the password for your account on one or
more file servers. You can also synchronize your password on
multiple servers.

Figure 2-7
SetPass dialog box



The Setpass tool will not synchronize NetWare Naming Services passwords. You
must use a NetWare Naming utility to set passwords.

The following sections explain the dialog box and the tasks you can
perform. For more information on using SetPass, press <F1>.

Fields

Server and UserName. Displays the servers you are attached to and
the usernames you used on those servers. If you have the same
password on several servers and want to change the password on
those servers, highlight all those servers.

Old. Enter the password you want to change in this box.

New. Enter the new password you want for this server.

Retype. Type the new password again for verification.

Buttons

Other Servers. Allows you to attach to or detach from additional
servers.

Set Password. Changes your password. Enter your old and new
passwords before choosing this button.

Close. Closes this dialog box.

Send

When you choose the Send icon, the Send dialog box appears.

Figure 2-8
Send dialog box



The following sections explain the dialog box and the tasks you can
perform. For more information on using Send, press <F1>.

Fields

Groups. Allows you select a group to send a message to, or to
unmark a group. All groups on your default server are listed below
this field. All users in the group you select are listed in the Users
field.

Use the Select radio button to select groups you want to send
messages to.

Use the Deselect radio button to remove groups of users from the
list of who will receive messages.

For example, suppose you want to send a message to all groups in
your company except group SALES. Choose the Select radio button;
then choose group EVERYONE. All users in group EVERYONE are
highlighted in the list of users who will receive the message.

To remove users who belong to SALES from the list of users, choose
the Deselect button; then choose group SALES. Members of SALES
are no longer highlighted in the list of users, and they will not
receive your message.

Users. Allows you to list all users or only those who are logged in.
The users in the group you select are listed under this field.
Highlight the users you want to send the message to.

Servers. Displays the server for which you want to see a list of users.

Message. Type in the message you want to send.

Show Full Names. Displays the full name (including connection
number) for all users. If a user's full name has not been defined, the
user's login name will be listed.

Buttons

Clear. Use to unmark all marked groups and users (instead of
unmarking each one separately).

Send. Use to send a message to the specified groups and users. Select
the users and enter a message in the Message box before choosing
this button.

Close. Closes this dialog box.

Messages

When you choose the Messages icon in the Novell NetWare
window, the Messages dialog box appears.

Figure 2-9
Messages dialog
box



To allow your workstation to receive messages from other stations,
choose Enable Incoming Messages.

To prevent messages from reaching your workstation, choose
Disable Incoming Messages.

Choose OK to set your choice. Choose Cancel to start again.

For more information on using Messages, press <F1>.

Scripts

You can create customized scripts that set your servers, drive
mappings, and printer settings. This is useful if you have several
tasks that require you to use different servers or use different drive
mappings. Instead of changing the mappings and attachments
individually, you can create scripts that will do it for you
automatically. The script will execute one line at a time.

For example, you may have one task where you need the following
settings:

*      Attach to server PRUFROCK.

*      Use print queue PRINT1.

*      Map drive F: to PRUFROCK/DOC:HOME/KEVIN.

*      Map drive I: to RD/SYS:USERS/KWILKEY.

Instead of changing these settings one at a time, you can create a
script. Each time you begin this task, apply this script.

When you are finished with this task, you can apply another script
to change your servers, printer settings, and drive mappings.

When you choose the Scripts icon, the Scripts dialog box appears.

Figure 2-10
Scripts dialog box



The following sections explain the dialog box and the tasks you can
perform. For more information on using Scripts, press <F1>.

Field

Scripts. Lists the existing scripts.

Buttons

Apply scripts. Applies the selected script to your work
environment.

Cancel. Closes this dialog box.

Edit. Allows you to make changes to an existing script.

New. Allows you to create a new script.

Delete. Removes the highlighted script.

Take Snapshot. Creates a script from your current drive mappings,
attachments, and printer settings. You can modify this script by
choosing Edit after the script has been created.

Script commands

You can perform the following tasks in the script.

Attach

Use to attach to another file server. Enter the line

Attach fileserver/username;password

Replace fileserver with the name of the file server you want to attach
to. Replace username and password with your username and
password on that server. If you do not enter your username and
password here, you will be prompted to enter them when you apply
the script.

Detach

Use to detach from file servers you might be attached to. Enter the
line

Detach fileserver

Replace fileserver with the name of the server you want to detach
from.

Map

Use to map a data drive (you cannot map search drives in
Windows). Enter the line

X:=path

Replace X with the drive letter you want to assign. Replace path with
the full directory path you want to map.

For example, to map drive F: to PRUFROCK/SYS:APPS/FRAME in
your script, enter the line

F:=PRUFROCK/SYS:APPS/FRAME

Map delete

Use to delete a drive mapping. To delete a mapping, enter

X:=

Replace X with the drive letter assigned to the mapping you want
to delete.

For example, if drive K: is mapped to PRUFROCK/SYS:APPS/FRAME
and you want to delete that drive, enter the line

K:=

Capture

Use to capture a printing port. Enter the line

port:=fileserver/queue

Replace port with the name of the port you want to capture (such as
LPT1). Replace fileserver with the name of the server you want to
use. Replace queue with the name of the print queue you want to
use.

For example, if you want to capture port LPT1 and use server
MACBETH and print queue ATALK, enter the line

LPT1:=MACBETH/ATALK

End capture

Use to end the capture of a print port. To end a capture, enter the
line

port:=

Replace port with the port on which you want to end the capture
(such as LPT1).

For example, if LPT1 is captured and you want to end the capture,
enter the line

LPT1:=

Sample script

The following graphic shows a sample script, using all the
commands allowed.

Figure 2-11
Sample script



To create a script easily, set your drive mappings and printer settings using the
Map tool and the Printers tool before opening the Scripts tool . Then open
Scripts and apply current settings.

Using non-Windows NetWare utilities

You can also use NetWare utilities that have not been designed for
Windows to perform network tasks. To use these utilities, create a
PIF file for each utility you want to use, and run the utility as a PIF.
You can run all NetWare utilities as PIF files.

For information on creating PIF files, see your Windows manual.

For information on using the NetWare utilities, see the NetWare
Utilities Reference for your version of NetWare.

       3     Modifying Your Windows Setup

Using the Network dialog box

After you have installed the NetWare Windows Workstation
services, you can customize your setup by using the Network dialog
box.

The settings you choose in the Network dialog box will take effect
each time you start Windows. The changes you make here will be
reflected in your NETWARE.INI, WIN.INI, and SYSTEM.INI files.

This dialog box also displays version information about

*      NetWare device driver

*      NetWare shell

*      NetWare operating system

To access the Network dialog box, go to the Control Panel and select
the Network icon. The Network dialog box appears.

Figure 3-1
Network dialog box



The following sections explain the dialog box and the settings you
can use. For more information, press <F1>.

Fields

Message status at startup. Allows you to receive or block messages
sent to your workstation by other network stations and servers.

Choose Messages Enabled to receive messages.

Choose Messages Disabled to block messages.

386 Enhanced. Allows you to customize the way your drive
mappings work in Windows. (Applies only if you are running
Windows in enhanced mode.)

Select NWShare Handles if you want drive mapping changes in any
session to affect all sessions.

Select Restore Drives if you want drive mappings restored to their
previous state when you exit Windows.

Printing. Allows you to set some printer settings. Each item has an
edit box that shows the number set. Enter the number you want in
the edit box, or use the arrow buttons next to the box to select a
new number.

Select Max Jobs to set the number of print jobs you can see in the
Print Manager queue. Default: 50. Maximum: 250. Minimum: 1.

Select Buffer Size to set the maximum buffer size (in bytes) of a print
job. Default: 3500. Maximum: 30000. Minimum: 3500.

Select Updates to set the time interval (in seconds) for the Print
Manager to update the Print Manager queue. This change is
reflected immediately. Default: 30. Maximum: 65. Minimum: 1.

Network Warning. Warns you if the network is not running or if
the wrong network is running. This box should always be checked
so that you will be notified if something is wrong with the network.
If you are not using the network, you can deselect this box.

Buttons

Ok. Makes the settings and closes the window.

Cancel. Cancels changes you made.

NETWARE.INI

NETWARE.INI is created automatically by the NetWare driver.
When the NetWare device driver is loaded, it creates the
NETWARE.INI file if one is not present.

NETWARE.INI contains commands and configuration settings
related to NetWare. This file lists settings that you select in the
Network dialog box (explained above).

To change the information in your NETWARE.INI file, use the
Network dialog box. If you want to edit this file manually, use
Windows Notepad or another text editor.

NETWARE.INI contains several sections. Each section is specially
named and contains only certain commands, as explained below.

Configuration section

This section lists optional print queue configuration settings. The
section must be named [MSW30-PrQ]. This section is not required.

The following parameters can be added to this section.

MaxJobs

Specifies the maximum number of print jobs that can be stored in
the print queue. Enter "MaxJobs=number."

Default: 50
Maximum: 250
Minimum: 1

MaxBufSize

Specifies the maximum buffer size (in bytes) for the print queue.
Enter "MaxBufSize=number."

Default: 3500 bytes
Maximum: 30000 bytes
Minimum: 3500 bytes

UpDateSeconds

Specifies (in seconds) how often the Print Manager will be updated.
Enter "UpDateSeconds=number."

Default: 30 seconds
Maximum: 65 seconds
Minimum: 1 second

Options section

This section sets driver options. The section must be named
[Options]. This section is not required.

The following flag can be added to this section:

Messages

Specifies if you want to be warned if the network is not running or
if the wrong network is running. You should always have this line
set to 1 (on). If you are not using the network, you can turn off the
warnings by entering the line "Messages=0."

Default: Messages=1

Scripts

This section lists the scripts you have set up using the Scripts tool.
The section must be named [Scripts].Your scripts are listed directly
below the section name. The settings for each script appear in this
section. To change these settings, use the Scripts tool (see "Scripts"
on page 23).

NetWare Tools section

This section lists the DLL files used with the NetWare tool file
NWTOOL.EXE. The section must be named [NWTools_Modules].
This section is not required.

The following line will be added automatically when NetWare Tools
are installed:

Toolset1=NWT.DLL

If you add more DLL files to run with NetWare Tools, add more lines
starting with Toolset2, Toolset3, and so forth.

Tool settings section

Use this section to set NetWare tool options. The section must be
named [MSW30-Switches]. This section is not required.

Enter settings for each NetWare tool you will use. The following can
be entered:

UserList-Sort

Specifies the default method used for sorting usernames on the
UserList tool screen. Enter "UserList-Sort=name" or
"UserList-Sort=connection" on a new line following the heading.

VolInfo-Units

Specifies the default units used to list directory sizes in either
kilobytes or megabytes. Enter "VolInfo-Units=KB" or
"VolInfo-Units=MB" on a new line following the heading.

Update-Interval

Specifies how often, in seconds, that VolInfo information is
updated by default. This can be any number zero or greater. Enter
"Update-Interval=number."

Use-Full-Names

Specifies if the UserList or Send tools are using full names.

       4     Task-Switched Buffer Manager

Introduction

The Task-Switched Buffer Manager for IPX/SPX (TBMI) helps IPX
and SPX programs work in a multitasking environment (such as
Microsoft Windows 3.0).

The multitasking environment in real and standard modes allows
application task switching (swapping). Each application runs in a
separate DOS session (DOS prompt) in 640KB of memory. Global
memory contains drivers and TSRs such as COMMAND.COM and,
if you are running NetWare, IPX.COM and NETx.COM. Local
memory contains the application and application data.

The multitasking environment switches from one DOS application
to another by moving the contents of the current DOS session from
conventional memory to disk, and then loading the contents of the
new DOS session into conventional memory.

Only the local memory is switched; the global memory with its
drivers and TSRs stays intact and is used with the new session. This
means that separate local memory segments exist, one for each DOS
session, while only one global memory segment exists.  You do not
need to use TBMI if

*      The application goes through the NetWare shell (NETx) to access
IPX or SPX, or

*      You will not be switching between sessions.

You must use TBMI if

*      You will be switching between sessions, and

*      The application bypasses the NetWare shell (NETx) and accesses
IPX or SPX directly.

If your application requires TBMI and you don't use it, the session
will fail and may hang your workstation.

If you aren't sure your application needs TBMI, go ahead and run TBMI; it will
use only a small amount of memory.  After running the application for a period
of time, enter the command TBMI /D and look at the number in the Far Call
Usage field.  If this number is zero, your application has not used TBMI; you can
run your application without TBMI.

Using TBMI

You must always load TBMI before you start Windows. TBMI
includes the main TBMI program and the TASKID program.  (TBMI
cannot work without TASKID.)

TASKID allows TBMI to know which session it is receiving
information from. Load TBMI at the command line before you
begin Windows; load TASKID while you are in Windows after
opening a DOS prompt.

Use TBMI and
TASKID



1.      Copy TBMI.COM and TASKID.COM to any directory (you must be able to run TBMI from
this directory later).

2.     From the directory where TBMI is located, type

 TBMI <Enter>

3.     Start Windows.

4.      Start a DOS session.

5.     At the new DOS prompt, load TASKID. Type

 TASKID <Enter>

Repeat Step 5 for each DOS prompt you open before running an application from that
prompt.

6.      Before you close a DOS session with the EXIT command, unload TASKID by typing

 TASKID /U <Enter>

If you don't unload TASKID before you close the session, your computer may
hang.

You do not need to unload TBMI after you exit Windows unless you want to free
memory.

Parameters

You can use any of the following parameters with TBMI.

 /? or /H

Displays help or usage information.

/C<filename>

Specifies the configuration file TBMI should use. Do not put a space
between /C and the filename.  For example, type
"TBMI /CTBMI.CFG" at the DOS prompt.

 /D

Displays diagnostic information.

 /I

Displays version information.

/U

Unloads TBMI after exiting Windows.

Configuration file parameters

TBMI reads configuration information from a configuration file in
the current directory. One parameter is entered on each line in the
configuration file. The filename is NET.CFG by default. To specify a
different file, use the /C parameter on the command line.

INT 64

Allows applications to use interrupt 64h to access IPX and SPX
services. IPX and SPX now use interrupt 64h to maintain
compatibility with earlier versions of NetWare. If an application
requires interrupt 64h, set this parameter to OFF.

Default:  ON

INT 7A

Allows applications to use interrupt 7Ah to access IPX and SPX
services. IPX and SPX now use interrupt 7Ah to maintain
compatibility with NetWare v2.0a. If an application requires
interrupt 7Ah, set this parameter to OFF.

Default:  ON

ECB COUNT

Specifies how many nondata event control blocks (ECBs) will be
allocated for use by DOS programs needing virtualization. These
ECBs apply to most asynchronous event schedules (AES) events. If
TBMI runs out of nondata ECBs, data ECBs can be allocated for use.

Each allocated ECB requires 52 bytes of memory; the 20-ECB default
will require 1,040 bytes.The maximum allocation also depends on
available memory; the total size of all ECBs must be less than 64KB,
which will normally limit the ECB count to less than 255.  Use the
/D command line parameter to verify actual allocations.

Default:  20
Maximum:  255
Minimum:  10

DATA ECB COUNT

Specifies how many data ECBs will be allocated for use by DOS
programs needing virtualization. These ECBs apply to most IPX and
SPX send-and-receive packets. If a nondata ECB request is made
when none are available, a data ECB will be used.

Each allocated data ECB requires 628 bytes of memory; the 60-ECB
default will require 37,680 bytes. The maximum allocation also
depends on available memory; the total size of all ECBs must be less
than 64KB, which will normally limit the data ECB count to less
than 255.  Use the /D command line parameter to verify actual
allocations.

Default:  60
Maximum:  255 (the practical limit is 89)
Minimum:  10

Using batch files

You can include TBMI in a batch file starting Windows to ensure
that it is always started before entering the multitasking
environment and unloaded after exiting.

For example, the batch file could include the following:

TBMI
WINDOWS
TBMI /U

Troubleshooting TBMI

If you encounter problems while using TBMI, you may need to
troubleshoot the TBMI configuration.  Use the /D option to display
diagnostic information and the current allocation limits.

Check the values associated with Max Buffers Used, which tells you
how many buffers are used, and Configured Data ECBs, which tells
you how many are available.  If the number of buffers used
approaches or equals the number of buffers available, increase the
number of buffers available using the ECB COUNT and DATA ECB
COUNT parameters in the configuration file.

If the "Unavail buffer count" is ever more than zero, increase the
number of buffers available using the ECB COUNT and DATA ECB
COUNT parameters in the configuration file.

The COMCHECK and RCONSOLE utilities use too many buffers
and cannot be used with TBMI.

       5     Using Named Pipes

The Named Pipes extender is provided for DOS users who want
their workstations to be Named Pipes clients. The Named Pipes
extender for DOS is a terminate-and-stay resident program that
extends the capability of DOS to include use of remote Named
Pipes. You must have an OS/2 Named Pipes server in order to use
this extender.  This appendix explains how to install and configure
the extender.

Prerequisites

The workstation on which you install the extender must be running
DOS v3.1 or above.

Load the extender into memory

Follow the steps in this section to load the extender into memory.
To install the extender so that it is loaded automatically when you
boot your workstation, follow the steps under "Load the extender
automatically" on page 43.

Your workstation may require up to a minute after you run the extender for
DOS before it is ready to run a Named Pipes application. This is significant when
you run batch files; Named Pipes applications may fail if they are executed
immediately (with no pause) after running the extender.

Load the extender



1.     Insert the NetWare Workstation for DOS diskette into drive A.

2.     Change to drive A.

3.     Type the following:

DOSNP

The extender is now loaded in memory.

4.     Remove the diskette.

5.     If you want a report of the status of the Named Pipes extender, type the following on the
DOS command line:

DOSNP /I <Enter>

Unload the extender from memory

Type the following at the DOS command line:

DOSNP /U <Enter>

Load the extender automatically

You can load the extender into memory each time you boot your
workstation.

Load the extender
automatically



1.     Insert the NetWare Workstation for DOS diskette into drive A.

2.     Copy the following file to the boot drive (hard drive or floppy diskette):

A:DOSNP.EXE

3.     Add a line to your AUTOEXEC.BAT file that executes the copy of DOSNP.EXE that you put
on the boot drive. This line can be placed after the line that loads IPX.COM and before the
line that loads the DOS shell (usually called NETx.COM).

4.     Remove the diskette.

Each time you boot the workstation, the line you put in the AUTOEXEC.BAT file
loads the extender into memory.

Configuring the Named Pipes extender

You can use the NET.CFG (or SHELL.CFG) file to specify various
attributes of the Named Pipes extender.

You can specify the following characteristics of the extender in
NET.CFG:

Maximum machine names
Maximum open Named Pipes
Maximum communication buffers

Other uses of NET.CFG are described in the NetWare manual set.

Maximum machine names

Description

Controls the number of Named Pipe servers with which the
extender can communicate.

Syntax

np max machine names = number

Replace number with how many Named Pipe servers you want
cached on the DOS machine.

Default: 10
Maximum: 50
Minimum: 4

Examples

The following line in NET.CFG changes the number of Named Pipe
servers with which the workstation can communicate from 10 to
14:

np max machine names = 14

Maximum open Named Pipes

Description

Specifies the maximum number of Named Pipes the workstation
can have open simultaneously.

Syntax

np max open named pipes = number

Replace number with the maximum number of Named Pipes that
can be open simultaneously.

Default: 4
Maximum: 128
Minimum: 4

Examples

The following line in NET.CFG changes the maximum number of
Named Pipes that the workstation can have open simultaneously
from the default (4) to 6:

np max open named pipes = 6

Maximum communication buffers

Description

Specifies the number of communication buffers that the extender
can use to transmit data to and receive data from the Named Pipes
server.

Syntax

np max comm buffers = number

Replace number with the maximum number of communication
buffers the extender can use to communicate with the Named Pipes
server.

Specify at least two buffers per Named Pipe.

Default: 6
Maximum: 40
Minimum: 4

Examples

The following line in NET.CFG changes the number of
communication buffers that the extender can use to communicate
with the Named Pipes server from 6 to 10:

np max comm buffers = 10

Named Pipes and Windows 3.0 applications

To use Named Pipes with Windows 3.0 applications, you must
install a copy of NETAPI.DLL on the workstation's hard disk.
NETAPI.DLL is on the NetWare Workstation for Windows diskette.
With this diskette in drive A, copy the NETAPI.DLL file to one of the
following locations on the workstation's hard disk:

u      The default directory

u      A directory specified in the workstation's PATH command (in the
AUTOEXEC.BAT file)

u      The directory containing WIN.COM

u      The directory containing KERNEL.EXE

The Named Pipes extender must be loaded for NETAPI.DLL to work
because NETAPI.DLL sends requests to the DOS Named Pipes
extender.

       A     Update utilities

Check utility version

Check the version of your NetWare utilities to make sure they will
work properly with Windows (use the NetWare VERSION utility.)

RPRINTER

Use RPRINTER v1.21 with Windows. Versions of RPRINTER prior to
v1.21 do not function properly in standard or enhanced mode. If
you don't have this version, you can download it from
CompuServe's NetWire forum. It is available under the filename
PSV121.ZIP.

Utilities that use fake roots

Utilities that are included with NetWare v3.x and NetWare v2.x
support fake roots. Check your version of the following utilities:

CAPTURE      NDIR
FILER  NPRINT
FLAG   PRINTDEF
FLAGDIR      REMOVE
GRANT        REVOKE
LOGIN        RIGHTS
MAKEUSER     SESSION
MAP    TLIST
NCOPY

If you do not have the correct version of these utilities, you must
update them. You can download these files from CompuServe's
Novell Download Directory section (GO NDD). They are available
under the filenames DSWIN3.ZIP and DSWIN4.ZIP. Or contact your
Novell authorized reseller.

       B     Windows modes

Windows can run in one of three modes on an Intel
microprocessor-based computer: real, standard, or enhanced.  Each
mode treats memory and other system resources differently for DOS
applications than for Windows applications. NetWare supports all
these combinations.

In all modes, all network resources (such as drive mappings,
printers, and server attachments) are handled globally. In Windows
Enhanced mode, drive mappings can be either global or inherited.

Applications must be written especially for use with Windows.
Regular DOS applications are handled differently by Windows than
applications written especially for Windows.  Under Windows,
users can swap between DOS prompts, each of which can run a DOS
application.

In addition to the NetWare files usually used with DOS, Windows
requires five additional files: NETWARE.DRV, NWPOPUP.EXE,
NETWARE.HLP, VNETWARE.386, and VPICDA.386.

In all modes, the NETx.COM file can be replaced by EMSNETx.EXE
or XMSNETx.EXE; these are the network station shell files for
expanded or extended memory.

Real mode

Real mode is the native mode for the 8086/8088 processor, and the
only mode that this processor can run in.

The processor can address up to 1MB of memory in real mode.

Real mode uses the IPX.COM and NETx.COM files to run NetWare.
Windows additionally uses NETWARE.DRV, NETWARE.HLP, and
NWPOPUP.EXE.

Under Windows, users can swap between DOS prompts, each of
which can run a DOS application.

Standard mode

Standard mode is the native mode for the 80286 processor; this
processor can also run in real mode.

The processor can address up to 16MB of memory in standard
mode.  All this memory is available to applications in Windows;
however, only 640KB is available in the DOS prompt, unless the
application uses the DOS extender specification.

This mode uses the IPX.COM and NETx.COM files to run NetWare.
Windows additionally uses NETWARE.DRV, NETWARE.HLP, and
NWPOPUP.EXE.

Under Windows, users can swap between DOS prompts, each of
which can run a DOS application.

Enhanced mode

Enhanced mode is the native mode for the 80386 processor; this
processor can also run in either real or standard mode.

The processor can address up to 4GB of memory in enhanced mode.
All this memory is available to applications in Windows; however,
only 640KB is available in the DOS prompt, unless the application
uses the DOS extender specification.

This mode uses the IPX.COM and NETx.COM files to run NetWare.
Windows additionally uses NETWARE.DRV, NETWARE.HLP,
NWPOPUP.EXE, and VNETWARE.386.

In this mode, users can run several applications at the same time.

Virtual machines

Windows Enhanced mode supports multiple virtual machines.
Virtual machine 0 (VM0) is created when Windows starts.  Part of
the conventional memory space (0 - 640KB), which can be referred
to as low conventional memory, is loaded with drivers (such as
IPX.COM, NETx.COM, or COMMAND.COM), TSRs, and other files
prior to Windows startup.  The rest of the space up to 640KB
(referred to as high conventional memory) is reserved for
applications and Windows system functions.

The low conventional memory in VM0 is mapped by Windows into
the address space of the new virtual machines (DOS prompts) as
these are created. This means, for example, that the drivers and
other files in low conventional memory in VM0 will be used by
machines VM1, VM2, etc., as they are created.  Although the drivers
and other files in low conventional memory in VM0 will be used by
other machines, some data associated with these files will not;
instead, it is duplicated or instanced for each new machine. The
application space for each machine will also be unique.  (The
VNETWARE.386 driver assists with the creation of new virtual
machines and the mapping of instanced data.)

NetWare (running with Windows) uses global server attachments
and printer connections: all machines use the data kept in VM0.
Drive mappings are inherited by default: each new machine gets an
instanced copy of the drive data from VM0 when the machine is
created.

Since global data applies to all machines, a server attachment
change in one machine affects all machines.  The inherited data for
each virtual machine will be identical to VM0 when the new
machine is created or started up.  But because the startup
information is stored in a unique copy for the new machine, the
information for the new machine can be changed without
changing the startup for other machines.  This means that you need
to be careful about changing the server attachments, printer
connections, and drive mappings  in VM0, as other machines will
use this information.

Use Windows applications and the File Manager to determine what
the current VM0 drive mappings are before you create another
machine.  For example, the drive mappings for VM0 are copied to
VM1 when VM1 is created. The mappings in VM1 will match those
in VM0.  If the mappings in VM0 are changed and then VM2 is
created, VM2 will match VM0 but VM1 will not.  Furthermore, the
drive mappings for either VM1 or VM2 can be changed so that they
are different from those for any other machine.

The drive mappings that are in effect will then depend upon which
virtual machine is in the foreground.  Windows applications all run
in VM0, and all use the drive mappings stored there.  As new virtual
machines are started (by creating new DOS prompts), they will
originally have the same mappings as VM0 at the time the machine
is created; if these mappings are changed, the changes will affect
only that prompt (virtual machine).

 As the virtual machines (DOS prompts) are swapped, the instanced
data is swapped into and out of memory.  For example, as the user
moves from VM0 to VM1, instanced data and application data for
VM0 will be unloaded, and instanced data and application data for
VM1 will be loaded.  Some of this instanced data is placed in the
low conventional memory space.

The NWShareHandles value in the SYSTEM.INI file is used to
change the attributes of inherited data.  If this value is set to TRUE,
all instanced data will be global ( a drive mapping change in any
machine will change all machines).  The default is FALSE; instanced
data for drive mappings will be inherited as discussed above.  Other
instanced data will remain global.