                     Personal NetWare Release Notes
                     ==============================

The Personal NetWare Tutorial
=============================

There are two tutorials supplied with Personal NetWare.
One describes how to use the DOS versions of the Personal NetWare 
programs, the other the MS Windows versions.

To install the tutorial for MS Windows, load MS Windows and run
WINTUTOR.EXE from "Tutorial disk 1".  Follow the instructions given on 
the screen. Once installation is complete, run the tutorial by 
selecting the Tutorial icon from the Personal NetWare Tutorial 
program group.

To install the tutorial for DOS, insert "Tutorial disk 1" in your 
diskette drive and run DOSTUTOR.EXE from that drive. Follow the 
instructions given on the screen. Once installation is complete, run 
the DOS tutorial by entering PNWTRAIN at the system prompt.   

Note: If you choose to install the DOS Personal NetWare tutorial to a 
directory other than the default one, you must change to this directory 
to run the tutorial.

Connecting to NetWare 2.x and 3.x Servers
=========================================

If you experience difficulty connecting to NetWare 2.X or 3.X servers, 
ask your system administrator to check that you have the correct Frame
settings for your network in NET.CFG.

Notes For Existing NetWare 2.x and 3.x Users
============================================

1. Do not use NETX.COM or related shells with Personal NetWare. The
   Personal NetWare client gives you simultaneous access to all NetWare
   2.x, 3.x, and 4.x servers as well as Personal NetWare servers.

2. Path names must be less than 64 characters long. VLMs cannot support
   a path name of more than 64 characters. To use longer paths, map a root
   drive and continue from there.

Using a Network Copy of MS Windows on the Local Server
======================================================

If you run a network installation of MS Windows on your the local server
and you want to use that version of MS Windows at the server, you must map
a drive to the server and make sure that your path statement references
both the network copy of MS Windows and your own MS Windows directory.

NWCACHE 
=======

Delayed write mode is disabled as part of the default configuration
for NWCACHE. This is a safety feature to prevent loss of data if the
computer is switched off before disk writes have been completed. Enabling
delayed write mode will improve performance but you must make sure you do
NOT switch off your computer before all data is written to the disk. Do
this in one of the following ways:

1. Perform a "soft boot" (press Ctrl+Alt+Del) before switching the
   computer off. A soft boot automatically flushes all pending data to
   disk.

2. Wait beyond the delayed write time you specified, after the disk access
   light goes out.

3. Wait for the system prompt to return (see below).

When delayed write mode is enabled, the cache is 'flushed' (all data is
written to the disk) BEFORE the system prompt returns, by default. This is
a safety feature. You can disable (or re-enable) this feature by specifying
the following option in the NWCACHE start-up or control command at the
system prompt:

/FLUSH=ON|OFF

If delayed write is enabled (on a computer that is running the Personal
NetWare server software), you can also save memory by setting the number
of I/O buffers to zero via the NET ADMIN program.

OEM-supplied Network Board Drivers
==================================

To use a third-party network board driver that does not include a .INS
file, do the following:

1. Copy the driver file to the directory into which you installed
   Personal NetWare. For example:

   COPY A:\MYDRIVER.COM C:\NWCLIENT

2. Change to the Personal NetWare directory and rename the INS.OEM file
   to xxxxxxxx.INS, where xxxxxxxx is the name of the driver file. For
   example:

   REN INS.OEM MYDRIVER.INS

3. Edit the new .INS file with an ASCII text editor and replace the two
   references to 3RDPARTY.COM with the file name of your driver. The .INS
   file looks like this:

   InS_StArT
   3RDPARTY.COM
   1.0
   ^ Third Party Driver without .INS file,3RDPARTY.COM,IE0
   !RIE0(INT)
   2
   @3
   4
   5
   10
   11
   12
   15
   !RIE0(PORT)
   @300
   320
   340
   360
   240
   280
   2C0
   InS_EnD

4. Run SETUP. On the screen that allows you to choose the primary
   network interface board, display the list of drivers and choose
   'Third party driver without .INS file'.

5. Choose to save changes and exit, to confirm your choice.  

DOS Protected Mode Services (DPMS)
==================================

Be aware that the DPMS driver MUST be loaded before the software
that uses it (NWCACHE and SERVER.EXE).

Using Your Favourite Text Editor to Edit Local Login Scripts
============================================================

You can choose to use your favourite ASCII text editor to edit the local
Login script from within the NET utility by changing the Editor setting
in the [Third Party] section of SETUP.INI. To use the TEXTED.EXE program
from the C:\TOOLS directory, for example, change the Editor statement in
SETUP.INI to Editor = C:\TOOLS\TEXTED.EXE. Note that the text editor you
specify MUST be an ASCII editor.

Increasing the Number of File Handles
=====================================

If, as you run more applications and add more users, you encounter
problems running applications across the network, be aware that the
number of file handles allocated in the CONFIG.SYS file at the server
may not be sufficient. This may also be true when you are running the
server under MS Windows. An indication that this situation has occurred 
would be getting unexpected "File not found" or "Directory not found" 
error messages when doing a DIR command to a drive on that server.

The documentation for your applications should indicate the number of 
file handles required per user; make sure that you allow the correct number 
in the server's CONFIG.SYS, given the number of users running the 
application and the number of times the application is run. If necessary, 
change the FILES value. If a value greater than 255 is required, use 
NET ADMIN to reconfigure the server so that it does not use the CONFIG.SYS 
FILES value and set the required value.

Running Personal NetWare with Other Networking Products
=======================================================

The name (NET.EXE) of the Personal NetWare NET program is likely to
exist in other networking products. After you install Personal NetWare,
the PATH command will cause the operating system to search the NWCLIENT
directory first. NWCLIENT contains NET.EXE. If you want to use a different
NET.EXE program, edit the PATH command so that the appropriate directory
is searched BEFORE the NWCLIENT directory.

Alternatively, you may find that if you install a different networking
product (or MS Windows), the PATH command is changed so that the NWCLIENT
directory is no longer searched first and a different NET.EXE program
is run instead of Personal NetWare NET.EXE. If you want the Personal
NetWare NET program to run, edit the PATH command so that NWCLIENT is
searched first.

Full-Screen Programs and Non-Standard VGAs
==========================================

Some portable, laptop, and notebook computers with LCD or TFT displays 
support a non-standard VGA text mode known as 'Expanded' or 'Stretched' 
text. This mode 'stretches' the standard 80x25 (400 pixels high) text 
mode so that it fills the entire physical screen which is 480 
pixels high. This mode, if used, may interfere with the enhanced text 
mode of the full-screen programs, such as NET ADMIN. 

If you encounter problems, it is recommended that you disable the 
'Stretched' text on your computer. Refer to the documentation for your 
computer for information about CMOS setup configuration.

If you cannot disable this mode or prefer to keep 'Stretched' 
mode enabled, you can disable the enhanced text mode of the full-screen 
programs when you run them by entering the name of the program followed 
by the /N switch at the system prompt.

Personal NetWare Modifications to MS Windows INI Files
======================================================

When you install the MS Windows element of Personal NetWare,
the following files are modified automatically: SYSTEM.INI,
WIN.INI, and PROGMAN.INI.

The following modifications are made to SYSTEM.INI:

in the [boot] section:		network.drv= is replaced by
				network.drv=netware.drv
				(This loads the NetWare user
				tools)

in the [boot.description]:	network.drv= is replaced by
				network.drv=Personal NetWare
				(This defines which Personal NetWare
				device version you are using)

in the [386Enh] section:	network=dosnet is replaced by
				network=*vnetbios;vipx.386;vnetware.386
				(This specifies the type of network
				used with MS Windows 386 Enhanced mode)
				
				TimerCriticalSection= is replaced by
				TimerCriticalSection=10000
				(Personal NetWare uses this setting to
				ensure that network traffic on your
				computer runs smoothly)
 
				ReflectDOSInt2A=TRUE is added.

				OverlappedIO=OFF is added.

				PSPIncrement=5 is added.

				UniqueDOSPSP=TRUE is added.

The following modifications are made to WIN.INI:
	
in the [windows] section:	load= is replaced by
				load=nwpopup.exe
				(This allows network messages to display
				in MS Windows)

				Netwarn=1 is added
				(If this is set but the network is not
				loaded, MS Windows will display a pop-up
				indicating that the network is not loaded)

The following modifications are made to PROGMAN.INI:

in the [groups] section:	Groupx=C:\windows\pnw.grp is added to
				the list of group files.
				(This causes MS Windows to load the
				Personal NetWare program group in
				Program Manager).
Documentation Updates
=====================

The following are updates and corrections to the information contained
in the Personal NetWare User Guide.

NET RIGHTS Command
------------------

The NET RIGHTS command has an additional option. You can view the rights
of all users to a specified directory by entering a command in the
following form:

NET RIGHTS dirpath ALL

NET SETDOG Command
------------------

The NET SETDOG command parameters have been changed from

NET SETDOG server minutes
to 
NET SETDOG minutes [server]

If no server is specified, all server timeouts are set.

Note: The NET SETDOG command does not apply to NetWare 2.x and 3.x
servers.

Entering Options in NET.CFG
---------------------------

The documentation states that headings and options entered in the
NET.CFG file are case-sensitive. This is incorrect; headings and
options are NOT case-sensitive.

LINK DRIVER and LINK SUPPORT Parameters
---------------------------------------

The documentation states that an equal sign (=) should be used
when specifying LINK DRIVER and LINK SUPPORT parameters:
dma=[#1|#2], for example. This is incorrect; the equal sign should
NOT be included when specifying parameters. If it is used, the
parameter will be ignored.

