

              NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:              Getting Started with PERSONAL NetWare
DOCUMENT ID:        TID014928
DOCUMENT REVISION:  A
DATE:               09JUN94
ALERT STATUS:       Yellow
INFORMATION TYPE:   Issue
README FOR:         NA

NOVELL PRODUCT and VERSION:
PERSONAL NetWare 1.0

ABSTRACT:

This document covers some networking basics to help you get
started with PERSONAL NetWare.

------------------------------------------------------------------
DISCLAIMER
THE ORIGIN OF THIS INFORMATION MAY BE INTERNAL OR EXTERNAL TO
NOVELL.  NOVELL MAKES EVERY EFFORT WITHIN ITS MEANS TO VERIFY
THIS INFORMATION.  HOWEVER, THE INFORMATION PROVIDED IN THIS
DOCUMENT IS FOR YOUR INFORMATION ONLY.  NOVELL MAKES NO EXPLICIT
OR IMPLIED CLAIMS TO THE VALIDITY OF THIS INFORMATION.
------------------------------------------------------------------

ISSUE

NOTE: This document is intended to enhance the documentation and
tutorials that are provided with PERSONAL NetWare, not replace
it.


INSTALLATION:  MAKING IT EASY THE FIRST TIME

One machine on the network should be installed at a time.  After
a machine is installed, especially if it is a server, it should
remain up and running on the network while the other machines are
being installed.

Installation of PERSONAL NetWare is supplied by the PERSONAL
NetWare installation program, or the Novell DOS 7 installation
program, depending on the product you purchased.  With both
products the installation program is called INSTALL, and it is
located on the first (serialized) diskette.

The serial number for your PERSONAL NetWare or Novell DOS 7
product is found on the back of the first install diskette on a
white label.  You will need this number during installation, and
in communicating with Novell's Technical Support Department.

Before installing, you should have read the license agreement,
the quick-start card, the networking chapters of your manual
dealing with installing, and the README.TXT file found on the
last installation diskette.  In the PERSONAL NetWare manual, read
chapters 1, 2, 3 and 4.  In the Novell DOS 7 manual, read
chapters 1, 2, 3, 18, 19 and 20.  Using the information obtained
from those chapters, decide if the machine needs to share its
files, printers, and so forth with other machines on the network
(act as a SERVER), or if it needs to use the resources of other

machines on the network (act as a CLIENT), or if it needs to do
both (act as a SERVER/CLIENT).

Finally, to install, completely follow the instructions found on
the quick reference card or the manual.  This includes installing
the hardware correctly, cabling the machines together correctly,
and running the INSTALL program from the installation diskettes.

The purpose of the INSTALL program is to request and record
configuration information; expand and copy the PERSONAL NetWare
files from the installation diskettes to your hard drive; and
configure your DOS and Windows configuration files so that they
include the network drivers in their loading process.  It is
important to enter requested information accurately during the
INSTALL process, since that information will be used to configure
your machine.  Entering incorrect information could cause the
network to function incorrectly after installation.

A list of what files are modified and what new files are copied
on your hard disk is provided in the SETUP.INI file.  A list of
modifications made to the Windows .INI files when you install the
PERSONAL NetWare Windows component is in the README.TXT file. 
These files can be found in your C:\NWDOS or C:\NWCLIENT
directory by default.


FIRST-TIME SETUP (POST-INSTALL)

After the installation program has finished, you were prompted to
reboot your computer.  If you installed Novell DOS 7, you will
need to press 'y' when you are asked about loading the network
software.  If you installed PERSONAL NetWare stand-alone, after
re-booting you are automatically taken into the SETUP program.

The SETUP program is used to configure the network.  A first-time
setup option has been provided in SETUP to make much of this
process automatic.  You know you are running the first-time setup
program if you are prompted to "Continue with first time setup." 
(You can enter the first-time setup from the DOS prompt by
running SETUP /FIRST.)

The first-time setup will ask you to join or create a workgroup. 
If you are the first server on the network (or if other servers
on your network are turned off), you will have to create a
workgroup.  Creating a workgroup generates a unique workgroup ID.
This is why it is important to leave servers up while installing
other servers.

If you completely install one server and create a workgroup for
it, then, with that first server turned off, you create another
server and a workgroup for it using the same name as the first,
you will have two workgroups with the same name.  Two workgroups
with the same name, but different workgroup ID numbers are
considered different workgroups.  To correct this situation, use
the NET ADMIN utility to move one of the servers into a temporary
workgroup (do this by creating a new workgroup).  Now, there
should be two workgroups with different names.  Move the server
from the temporary workgroup to the original one and now both
servers should appear in the same workgroup.  From now on, leave
those servers up while installing the others.


NOTE:  After you move one of the servers to a temporary
workgroup, the workgroup that you moved it from will
automatically get deleted since a workgroup has to have at least
one server in it.

The first-time setup program also allows you to create default
resources.  You can create network drives (aka. volumes) for your
C: and D: drives.  You can also create network printers that may
be off your LPT1 and LPT2 ports.  Later, you can use the NET
ADMIN utility to create other network resources.

When the first-time setup program has all the information it
needs, it will create/join the workgroup you specified, create
the resources you specified, and create a user with the name you
gave the INSTALL program in the beginning.  By default, the
SUPERVISOR user is also created when the first server is added to
a workgroup.


COMPLETING THE SETUP

The NET ADMIN utility is used to configure the network and its
resources (as opposed to the NET utility that is used to make use
of those resources).  To complete the setup, use the NET ADMIN
utility to:

-    Configure your servers as needed (for example, increasing
your servers' client connections for more than 4 users).

-    Create any network drives (volumes) that haven't been
created and configure as required.

-    Create any network printers that haven't been created (for
example, a serial printer) and configure as required.

-    Create all the network users and give them the appropriate
rights to resources.

If you need help at any time, press the <F1> key.  By pressing
<F1> when inside one of the NET utilities, you will get a context
sensitive help.


USING NETWORK RESOURCES AND CREATING LOGIN SCRIPTS

To use resources in a workgroup, you must be logged into that
workgroup.  With PERSONAL NetWare 1.0, you can only be logged
into one workgroup at a time.  In many networks, there may be
only one workgroup.

To login to the workgroup, use the NET LOGIN command.  This is
placed at the end of the STARTNET.BAT file by default.  When that
command is run, you are prompted to enter your username.  Type it
in and hit <Enter>.  If the username you logged in as has a
password, you will then be prompted for that password.  Enter it
as you did the username.  Note, however, that the characters are
not displayed, only asterisks.  This is for security reasons.

If you entered the name of a user that doesn't exist (for
example, if you misspelled the username) in the workgroup, you
will be prompted for a password.  This is so that someone trying

to break into the system by entering bogus usernames will not
know if the username is valid or not.  Usernames and passwords
are NOT case sensitive.

After you are logged into a workgroup, you can use the resources
that your username has access to in that workgroup.  To see what
network drives (volumes) are available, use the NET VLIST
command.  To see what network printers are available, use the NET
PLIST command.  To map a drive letter to a network drive so you
can access it, use the NET MAP command.  To capture a logical
printer port to a network printer so you can print to it, use the
NET CAPTURE command.  For help with the NET command line
utilities, type NET HELP at the command line.

You can also map drives and capture printer ports through the NET
utility.  To access that utility, enter NET at the DOS command
line.  A menu driven utility, similar to NET ADMIN is brought up.
For context sensitive help from inside this utility, you can use
the <F1> key.

If you are in Windows, you can perform most of the same functions
as you can with NET and NET ADMIN from the PERSONAL NetWare
Windows based utility.  Help is also available within that
utility.

After you have all the drives mapped and printer ports captured
the way you want for this user, you can save those settings in a
script so they will automatically be reset when you log in the
next time.

This can be done from the DOS command line by using the NET SAVE
command.  If you type NET SAVE, your network settings and DOS
environment will be saved in a PNWLOGIN.BAT file in the current
directory.  To use that batch file as a login script, edit the
STARTNET.BAT file, and modify the NET LOGIN line so it reads NET
LOGIN @PNWLOGIN.BAT.  If the PNWLOGIN.BAT is not in the DOS path,
you may need to supply a path between the @ and PNWLOGIN.BAT.

If your machine is a server, you can use the NET SAVE /S command
instead.  This will create a file exactly like the PNWLOGIN.BAT
file, but called PNWLOGIN.SCR.  That file will be located in the
directory, C:\NWCLIENT\MAIL\<userID>.  The userID of SUPERVISOR
is 00000001.  The userID of all other users is a unique 8-digit
hexadecimal number.  In PERSONAL NetWare 1.0, there is no way to
find the userID of a specific user, but you shouldn't ever have
to.  If you need to edit the login script, you can do so in the
NET utility.  This script is only used if you log in at the
machine you ran NET SAVE /S on.  That machine must be a server. 
You do NOT need to edit the STARTNET.BAT file on the NET LOGIN
line.  The server will automatically search its mail directory
for a login script.

In Windows, login scripts are not used.  Instead, map your drives
and capture your printer ports as desired.  Then the ones you
want to be reset when you re-load Windows can be made permanent. 
For example, to make a drive mapping permanent, select that drive
mapping on the left side of the Drives window, pull down the File
menu and select the permanent option.



CREATE A LOGIN SCRIPT OR PERMANENT WINDOWS CONNECTIONS

If you are also connecting to a NetWare 3.x server, it is
recommended that you use the NET commands provided with PERSONAL
NetWare to connect to and use the NetWare 3.x resources as well
as the PERSONAL NetWare resources.  PERSONAL NetWare was written
to recognize and use other NetWare resources.  However, NetWare
3.x utilities do not recognize or use PERSONAL NetWare resources,
and may return errors in certain situations.


HAVING FUN

Get to know your network system.  PERSONAL NetWare is an advanced
peer-to-peer network system.  That means that every machine on
the network can use and share resources with every other machine
on the network.  It has quite a few features, many of that you
may not need, and many of which you may need but don't know they
exist.

For example, did you know that you can lock a user out of the
system at a specific time?  If you had an employee that was only
supposed to work certain hours, you could set up time
restrictions on that user so he/she could not access the network
except at the specified times.

Did you know that you could capture logical printer ports that
don't even exist on your machine to network printers?  When you
capture a logical port to a network printer, you don't have to
have that physical port actually on the machine.  You may only
have one printer port (LPT1), but you can capture, say LPT3 to a
printer on another machine that may be physically hanging off
that machine's COM2 port.  In fact, by editing the NET.CFG and
adding the statement NETWORK PRINTERS = 9 to the NetWare DOS
Requester section, you can capture LPT1 - LPT9!

To add to the fun, a network game called NetWars is included. 
You and several other people on other machines can battle it out
in a 3-dimensional space war game.  You can see your opponents
ship fly right by you as you fire away, or your opponents may see
you disappear as you cloak yourself.  However, it isn't just a
game.  It is also a way to test network connectivity and
bandwidth.  You see, the more players you have, the more
information is pushed on the network cabling system.  If two
players can't see each other, and they are selecting the same
space, then there is probably a communication problem; check your
network hardware!

----------------------------------------------------------------
Any trademarks referenced in this document are the property of
their respective owners.  Consult your product manuals for
complete trademark information.
----------------------------------------------------------------
