

NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:  Installing a Shared Copy of Windows
DOCUMENT ID:  TID021236
DOCUMENT REVISION:  A
DATE:  20JUL94
ALERT STATUS:  Yellow
README FOR:  NA

NOVELL PRODUCT and VERSION:

PERSONAL NetWare 1.0

CATEGORY:

Windows

ABSTRACT:

This document contains instructions for installing and configuring Windows 3.1
on a Personal NetWare Network.

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

INSTALLING WINDOWS 3.1 ON A PERSONAL NETWARE NETWORK

If you are upgrading from a previous version of Windows to Windows 3.1, Novell
recommends that you delete the previous version of Windows from your hard 
drive before you begin installation of Windows 3.1.  This is recommended 
because Windows 3.1 handles many of the settings in the initialization files 
(*.INI) differently than before and will not always convert these parameters 
to the new format.  There are also many drivers, including all printer 
drivers, that have been changed from version 3.0 to 3.1.  By deleting any 
previous version of Windows before you install version 3.1, you ensure that 
all drivers will be upgraded to the correct versions.

The first section of this document describes installing Windows 3.1 on 
Personal NetWare 1.0 in both stand-alone and shared network versions.

The second section, entitled "DOS Configuration Items," discusses general 
suggestions for configuring NOVELL DOS 7, MS DOS 6.x, Personal NetWare 1.0, 
and Windows 3.1 for peak performance.  The last section, "Tips for Running 
Windows 3.1," describes general items regarding Windows 3.1 and Personal 
NetWare 1.0 regardless of what operating system you are using.



INSTALLING A STAND-ALONE VERSION OF WINDOWS 3.1

Follow the regular installation procedures to install Windows 3.1 as a stand-
alone version.  For more information, refer to the Getting Started with 
Microsoft Windows booklet included with Windows 3.1.


INSTALLING A SHARED VERSION OF WINDOWS 3.1

The following is intended for users who want to install Windows in shared 
mode.  You will need to follow the steps to install on a Personal NetWare 
server, then those for a Personal NetWare client.  Please refer to the Getting
Started with Microsoft Windows booklet, pages 6 to 12, for information about 
installing Windows on networks in general.

Steps for Configuring a Server:

1.	Decide which server you want to install the shared copy of Windows on.
NOTE:  There must be approximately 16 MB of hard disk space available on the 
server to install a shareable copy of Windows 3.1.

2.	Insert the Windows DISK 1 in the disk drive, and go to that drive 
(a: <Enter>).

3.	Type SETUP /A.  When Windows prompts for the network path to which it 
should install, type C:\WINADMIN or some other path to which you want to 
install Windows.  (If this directory does not exist, Windows will create it 
for you.)

As you follow the prompts, a shareable copy of Windows will be installed on 
the server.   NOTE:  This will not create an executable copy of Windows.  It 
merely creates a location where clients can pull the executable programs from 
after they have been set up (see steps for clients, below).

After the shared copy of Windows has been installed, the following steps must 
be taken to properly configure the network software on the server.

4.	Enter the Personal NetWare administration utility by typing NET ADMIN 
and pressing <Enter>.  Then select "View Shared Directories" by pressing 
Alt-D.  Create a network directory by pressing the <Insert> key.  Select the 
server where the WINDOWS directory is located.  Type a name for the network 
directory.  Then enter the path to which you installed Windows, from step 3 
above.

5.	While still in the NET ADMIN utility, configure the server by pressing
 the Alt-S keys.  Select the server where the Windows directory is located and
 press <Enter>.  Select "Configure..." and press <Enter>, then using the <Tab>
 key select "Advanced Settings..."  The CLIENT TASKS option defaults to 10 at 
the time of the Personal NetWare installation.  Set the CLIENT TASKS in the 
FUTURE column to 10 per machine connected to the network.  (For example, if 
you had three computers on the network, you would set the client tasks to 30.)
You can verify if you need to increase client tasks by pressing the Alt-S keys
in the NET ADMIN utility.  Press <Enter> on the appropriate server and select 
"Statistics...".  The CFG value of CLIENT TASKS should always be greater than 
the PEAK value.  If it is not, increase CLIENT TASKS.

6.	When Personal NetWare is installed, the FILES=xx in the CONFIG.SYS 
file is set to be at least 60.  This needs to be increased on the server based
 upon the number of open files each station will be using.  Each application 
is unique and has different requirements.  You may need to contact your 
software vendor to determine the number of open files used by each machine.  

Initially, try increasing the number of files by 20 per machine connected.  
You can change this by using a text editor (such as Novell DOS 7 EDIT) to edit
the CONFIG.SYS file.

7.	Remove the (R)ead only attribute on the sub-directory where Windows 
was installed on the server.  (ATTRIB C:\WINADMIN\*.* -R <Enter>).

8.	Make a SYSTEM sub-directory on the server under the directory where 
Windows was installed.  (MD C:\WINADMIN\SYSTEM <Enter>).

9.	Edit C:\NWDOS\SETUP.INI or C:\NWCLIENT\SETUP.INI (PNW stand-alone) 
and make the following changes:

		Change WinPath=C:\WINDOWS to WinPath=C:\WINADMIN.
		Change Windows=YES to Windows=NO.

10.	Verify that C:\WINDOWS is not in the current path by typing path.  If 
it is, remove Windows from the path by typing Path=C:\NWDOS.

11.	Run setup (C:\NWDOS\SETUP or C:\NWCLIENT\SETUP for Personal NetWare 
stand-alone), and answer yes to allow setup to install its Windows files.  You
will be prompted to insert either the Novell DOS 7 #3 or the Personal NetWare 
#1 diskette.  Setup will fail to change the Windows .INI files because there 
are none!  Click OK to bypass the error messages that setup cannot modify the 
.INI files.

12.	Delete the files in the system subdirectory and remove the system 
subdirectory by issuing the following three commands:

		COPY C:\WINADMIN\SYSTEM\*.* C:\WINADMIN
		DEL C:\WINADMIN\SYSTEM\*.*
		RD C:\WINADMIN\SYSTEM

13.	After you have performed these steps for the server, reboot the server
for these changes to take effect.

Steps for Configuring a Client:

There are three ways to set up Windows from the shared copy installed on the 
server.  Following are instructions on how to setup each configuration.  
Please refer to page 7 in Getting Started with Microsoft Windows for a further
explanation of the three methods.

Option A:	Copy all Windows 3.1 files to the client machine's hard drive.  Setting up Windows in this way will give each user the fastest performance of Windows.  However, it will also greatly increase the amount of disk space used and force all clients to have their own hard disks.

Option B:	Copy only custom configuration files to the client machine's 
hard drive.  All other files will be used from the shared copy installed on 
the server.  Setting up Windows in this way will take up less disk space than 
option A.  However, it will run slower and client machines must still have 
their own hard disks.

Option C:	No files will be stored on the Client machine's hard drive.  
Instead, the custom configuration files will be stored in a subdirectory on a 
network server and all other files will be run from the shared copy of Windows
installed on the server.  Setting up Windows in this way is the most 
conservative as far as disk space is concerned.  It also gives the option of 
leaving the client machines as "diskless workstations," or machines without 
hard disks.  However, it is also the slowest way to run Windows because 
everything must be pulled off the network any time Windows is run.

The steps below are instructions to install Windows from the shared copy 
using Options A, B, or C.

Option A

1.	Load Personal NetWare by typing STARTNET.  Map a drive to the network 
directory that was created on the server.  For example, if the network 
directory you created WINADMIN, you would type the following:

		NET MAP I: WINADMIN <Enter>

2.	Change to the drive you mapped (I: in this example):

		I: <Enter>

3.	Type SETUP and press <Enter>, and follow the prompts to install a copy
of Windows to your local drive.

	When prompted to either run an Express Setup or a Custom Setup, choose
 Custom.  The custom setup allows you to preview the changes that are being made to the different files on your computer.  Refer to Windows documentation for questions regarding the installation.

4.	When Windows prompts you, choose the "let you make the modifications 
later" option.  You will then be prompted with a path and filename in which to
place a file with Windows-proposed changes to your AUTOEXEC.BAT and CONFIG.SYS
files.  Depending on which version of DOS you are using, you will need to make
certain changes after installing Windows.

	Novell DOS 7/DR-DOS 6.0

	None of these changes are necessary if you are running Novell DOS or 
        DR DOS.  You will only need to verify, after installing Windows, that 
        the subdirectory to which you are installing Windows is in the PATH= 
        statement in your AUTOEXEC.BAT file.

	MS DOS

	If you are running MS-DOS, you will want to look at the Windows-
        proposed AUTOEXEC.BAT and CONFIG.SYS files to see the changes that it 
        wanted to make for you.  The changes you will be looking for are the 
        following:

	In the AUTOEXEC.BAT file, Windows will insert a line to run the 
        SmartDrive disk caching utility.  However, there have been some 
        problems running with SmartDrive.  It is suggested that you run 
        Personal NetWare's NWCACHE.

	In the CONFIG.SYS file, Windows will usually try to include its own 
        memory manager, which includes HIMEM.SYS and EMM386.EXE.  For MS-DOS 
        this should be fine.  However, if you experience memory problems or 
        are running with a different memory manager, you will want to leave 
        the lines how they were before the Windows installation.  You will 
        also want to include a line STACKS=9,256 in the CONFIG.SYS file, which
        is a fix for MS-DOS on how to handle hardware interrupts.

5.	Continue following the prompts to finish the installation of Windows. 
You will now run Windows from your local drive instead of the I: drive.  
Verify that the subdirectory on your local drive that you selected in SETUP is
included in your AUTOEXEC.BAT file in the PATH= statement, as you will need 
this to run Windows.

Option B

1.	Load Personal NetWare by typing STARTNET.  Map a drive to the network 
directory that was created on the server.  For example, if the network 
directory you created was WINADMIN, you would type the following:

		NET MAP I: WINADMIN <Enter>

2.	Create a subdirectory on the client's hard drive in which to put the 
custom files (MD C:\DAVE <Enter>).

3.	Go to the network drive containing the Windows files (I: in this 
example):

		I: <Enter>

4.	Type SETUP /N, then follow the Windows installation instructions.  
When prompted to either run an Express Setup or a Custom Setup, choose Custom.
This allows you to preview the changes that are being made to the different 
files on your computer.  NOTE:  At the prompt for the path of the Windows 
files, enter the subdirectory that you created in step 2 (C:\DAVE).

5.	When Windows prompts you, choose the "let you make the modifications 
later" option.  Then you will be prompted for a path and filename in which to 
place a file with Windows-proposed changes to your AUTOEXEC.BAT and CONFIG.SYS
files.  Depending on which version of DOS you are using, you will need to make
certain changes after installing Windows.

	Novell DOS 7/DR-DOS 6.0

	None of these changes are necessary if you are running Novell DOS or 
        DR DOS.  You will only need to verify, after installing Windows, that 
        the network directory where the shared version of Windows is installed
        to and the user subdirectory where the custom configuration files are 
        (I: and C:\DAVE in this example), are both in the PATH= statement in 
        your AUTOEXEC.BAT file.

	MS DOS

	If you are running MS DOS, you will want to look at the Windows-
        proposed AUTOEXEC.BAT and CONFIG.SYS files to see the changes that it 
        wanted to make for you.  The changes you will be looking for are the 
        following:

	In the AUTOEXEC.BAT file, Windows will insert a line to run the 
        SmartDrive disk caching utility.  However, there have been some 
        problems running with SmartDrive.  It is suggested that you run with 
        Personal NetWare's NWCACHE.

	In the CONFIG.SYS file, Windows will usually try to include its own 
        memory manager, which is HIMEM.SYS and EMM386.EXE.  For MS-DOS this 
        should be fine.  However, if you experience memory problems or are 
        running with a different memory manager, you will want to leave the 
        lines how they were before the Windows installation.  You will also 
        want to include a line STACKS=9,256 in the CONFIG.SYS file, which is 
        a fix for MS-DOS on how to handle hardware interrupts.

6.	Continue following the prompts to finish installing Windows.

7.	Make a SYSTEM sub-directory on the client under the user subdirectory 
that you created (MD C:\DAVE\SYSTEM <enter>).

8.	Edit C:\NWDOS\SETUP.INI or C:\NWCLIENT\SETUP.INI (Personal NetWare 
stand-alone) and make the following changes:

		Change WinPath=C:\WINDOWS to WinPath=I:\
		Change Windows=YES to Windows=NO.

9.	Run setup (C:\NWDOS\SETUP or C:\NWCLIENT\SETUP for Personal NetWare 
stand-alone) and answer yes to allow setup to install its Windows files.  You 
will be prompted to insert either the NOVELL DOS 7 #3 or the Personal NetWare 
#1 diskette.

10.	Delete the files in the system subdirectory and remove the system 
subdirectory by issuing the following commands:

		DEL C:\DAVE\SYSTEM\*.*
		RD C:\DAVE\SYSTEM

11.	After you reboot, load the network by typing STARTNET.  Then, after 
you have performed your drive mappings and printer captures, type WIN to enter
Windows.

Option C

1.	Load Personal NetWare by typing STARTNET.  Map a drive to the network 
directory that was created on the server.  For example, if the network 
directory you created was WINADMIN, you would type the following:

		NET MAP I: WINADMIN <Enter>

2.	Create a subdirectory on the server's hard drive in which to put the 
custom files (MD C:\STEVE <Enter>).

3.	Create a network directory that looks at the user's subdirectory by 
doing the following:

		Enter the Personal NetWare administration utility by typing 
                NET ADMIN and pressing <Enter>.

		Then select the Shared Directories View by pressing the Alt-D 
                keys.

		Create a network directory by pressing the <Insert> key and 
                filling in the Name field (STEVE).

		Select the server on which you want to store your custom files
                and click the OK button.

		Then, the Shared Directory Properties screen will appear.  
                Enter the directory path of the subdirectory you created in 
                step 3, such as C:\STEVE, and click the OK button.

4.	Map a drive to this network directory:

		NET MAP G: STEVE <Enter>

5.	Go to the network drive containing the Windows files (I: in this 
example).

		I: <Enter>

6.	Type SETUP /N, then follow the Windows installation instructions.  
When prompted to either run an Express Setup or a Custom Setup, choose Custom.
This allows you to preview the changes that are being made to the different 
files on your computer.   NOTE:  At the prompt for the path of the Windows 
files, enter the drive you have mapped to the custom files network directory 
from step 4 above (in this example it would be G:).


7.	When Windows prompts you, choose the option "let you make the 
modifications later."  You will then be prompted for a path and filename in 
which to place a file with Windows-proposed changes to your AUTOEXEC.BAT and 
CONFIG.SYS files.  Depending on which version of DOS you are using, you will 
need to make certain changes after installing Windows.

	Novell DOS 7/DR-DOS 6.0

	None of these changes are necessary if you are running Novell DOS 7 or
        DR DOS 6.0.  You will only need to verify, after installing Windows, 
        that the network directory where the shared version of Windows is 
        installed to and the network directory where the custom configuration 
        files are (I: and G:\ in this example), are both in the PATH= 
        statement in your AUTOEXEC.BAT file.

	MS DOS

	If you are running MS DOS, you will want to look at the Windows-
        proposed AUTOEXEC.BAT and CONFIG.SYS files to see the changes that it 
        proposed for you.  The changes you will be looking for are the 
        following:

	In the AUTOEXEC.BAT file, Windows will insert a line to run the 
        SmartDrive disk caching utility.  However, there have been some 
        problems running with SmartDrive.  It is suggested that you run 
        Personal NetWare's NWCACHE.

	In the CONFIG.SYS file, Windows will usually try to include its own 
        memory manager, which is HIMEM.SYS and EMM386.EXE.  For MS-DOS this 
        should be fine.  However, if you experience memory problems or are 
        running with a different memory manager you will want to leave the 
        lines how they were before the Windows installation.  You will also 
        want to include a line STACKS=9,256 in the CONFIG.SYS file, which is 
        a fix for MS-DOS on how to handle hardware interrupts.

8.	Make a SYSTEM sub-directory on the server under the user directory (MD
        C:\STEVE\SYSTEM <enter>).

9.	Edit C:\NWDOS\SETUP.INI or C:\NWCLIENT\SETUP.INI (Personal NetWare 
        stand-alone) and make the following changes:

		Change WinPath=C:\WINDOWS to WinPath=G:\
		Change Windows=YES to Windows=NO.

10.	Run setup (C:\NWDOS\SETUP or C:\NWCLIENT\SETUP for Personal NetWare 
        stand-alone), and answer yes to allow setup to install its Windows 
        files.  You will be prompted to insert either the NOVELL DOS 7 #3 or 
        the Personal NetWare #1 diskette.

11.	Delete the files in the system subdirectory and remove the system 
        subdirectory by issuing the following commands:

		DEL C:\STEVE\SYSTEM\*.* <Enter>
		RD C:\STEVE\SYSTEM <Enter>

12.	After you reboot, load the network by typing STARTNET.  Then, after 
        you have performed your drive mappings and printer captures, type WIN 
        to enter Windows.



NOVELL DOS 7 CONFIGURATION ITEMS

The following items are for maximizing performance of Windows 3.1 on a 
Personal NetWare network running Novell DOS 7.

1.	If you are using NWCACHE from Novell DOS, you can modify the NWCACHE 
parameters to optimize the speed and performance.  The options "maxsize" and 
"minsize" should be present on the NWCACHE line in the CONFIG.SYS file.  For 
example:

		NWCACHE 2048 1024


	These options instruct NWCACHE the maximum and minimum amount of 
memory to use for its cache.

	The following are suggested amounts of memory to allocate to the cache
 based on the amount of RAM in your machine.

		Ŀ
		  AMOUNT OF RAM    MAXSIZE    MINSIZE  
		ĳ
		  Less than 4 MB   Do not use a cache   
		  4 to 7 MB        1024 KB    512 KB   
		  8 to 15 MB       2048 KB    1024 KB  
		  above 16 MB      3072 KB    1536 KB  
		

	Two other NWCACHE parameters are LEND and DELAY.  A description of 
each follows:

	/LEND=ON	This option allows NWCACHE to share cache memory with 
                        other programs which require it, such as Windows.  
                        When lending is enabled, NWCACHE monitors application 
                        requests for memory and automatically reduces the 
                        cache size to fulfill the request.

	/DELAY=ON 	This option allows the cache to accumulate write 
                        requests in the cache for a few seconds before the 
                        data is written to the disk.  NWCACHE uses this time 
                        to eliminate duplicate sector writes and to combine 
                        multiple write requests into fewer and larger writes. 
                        This allows the application to continue processing 
                        without waiting to write to the disk, resulting in 
                        fewer disk accesses and less time required for writing
                        to disk.

2.	If you are running Windows on a Stacked drive, and want to have a 
swap file on the hard drive, you must create it with the Virtual Memory icon 
that Novell DOS places in the Control Panel of the Main group.  This icon will
only be present if the hard drive is Stacked and Windows is running in 386 
enhanced mode.

	DR DOS 6.0 CONFIGURATION ITEMS

	The following items are for maximizing performance of Windows 3.1 on a
        Personal NetWare network running DR DOS 6.0.

	1.	To run with Windows 3.1 you must have the DR DOS 6.0, April 
                92, Update diskettes.  Because Windows 3.1 was released after 
                DR DOS 6.0, Novell needed to make changes to several DR DOS 
                files to be fully compatible with Windows.

	2.	If you are using the Super PC-Kwik (SUPERPCK) disk caching 
                utility that comes with DR DOS 6.0, you will need to have a 
                line in your CONFIG.SYS file that calls the Super PC-Kwik 
                Windows driver, called PCKWIN.SYS.  The line will be similar 
                to this:

			DEVICE=C:\DRDOS\PCKWIN.SYS

		There are also a few command line switches that should be 
                changed or added to SUPERPCK.EXE.  They are the following:

		/H-		This option needs to be added for 
                                compatibility with Personal NetWare.  It turns
                                off the advanced reads and writes that can 
                                cause data corruption on some networks.

		/L:xxxx		This option should be removed if it is present
                                on the SUPERPCK line.  It enables the memory 
                                lending feature of Super PC-Kwik.  (The /S 
                                option, discussed later, is better to use.)

		/R:xxxx		This option should be removed if it is present
                                on the SUPERPCK line.  Super PC-Kwik defaults 
                                to use all available extended or expanded 
                                memory for the disk cache when this option is 
                                set to 0.  Then it will lend up to half of 
                                that memory back to applications that request 
                                memory depending on what the /L option is set 
                                to.  (The /S option, discussed later, is 
                                better to use.)

		However, it is easier to optimize the disk cache with Windows 
                if you can control the exact amount of the cache.  For this 
                reason, the next option is used.

		/S:xxxx		This option instructs SUPERPCK exactly how 
                                much memory to use for its cache, and you do 
                                not have to worry about how much is getting 
                                lent back since this option controls that.

		The following are suggested amounts of memory to allocate to 
                the cache through the /S:xxxx parameter based on the amount of
                RAM in your machine:

			Ŀ
			  AMOUNT OF RAM    CACHE SIZE          
			Ĵ
			  Less than 2 MB   Do not use a cache  
			  2 to 4 MB        512 KB              
			  4 to 6 MB        1024 KB             
			  above 6 MB       2048 KB             
			

		The smaller the cache, the more memory available to Windows so
                that it will not use a swap file on disk.  This allows Windows
                to run faster since it is using RAM.

	3.	If you are running on a SuperStored drive, be aware that swap 
                files (whether permanent or temporary) cannot exist on a 
                SuperStored compressed partition of your hard drive.


		If you decide you want to have a swap file on your hard drive 
                and do not have the space on the uncompressed partition, the 
                following steps will remove the SuperStor drive and recreate 
                it, leaving a larger uncompressed partition:

		a.	Backup all data on the compressed partition of your 
                        hard drive.  You will be removing the SuperStor 
                        partition; therefore, all data on the hard drive will 
                        be ERASED.  If you do not have a backup of your data, 
                        you will lose it all.

		b.	Uncompress the drive by running the SuperStor utility 
                        (SSTOR) and choosing "remove" to remove the SuperStor 
                        partition.

			NOTE:	If the entire hard disk was SuperStored, you 
                        may need to reinstall DR DOS because removing the 
                        SuperStor partition will remove all files on your 
                        hard disk including all DR DOS files.

		c.	Recreate the SuperStor partition by running SuperStor 
                        (SSTOR) and choosing "create."  When prompted, enter 
                        the amount of space to be left uncompressed in 
                        kilobytes ("K").  1024 kilobytes is equal to 1 
                        megabyte.  Remember that this portion of the disk 
                        needs to be large enough for your boot files and your 
                        permanent swap file (5 MB is a good size swap file).

		d.	You can now restore your data from backup to your 
                        newly compressed SuperStor partition.

			You will need to make sure that the EMM386.SYS driver 
                        is in the same subdirectory on both the compressed and
                        uncompressed partitions of your hard drive.  For 
                        example, if the EMM386.SYS file is in the DRDOS 
                        subdirectory on your uncompressed partition, make sure
                        that there is a DRDOS subdirectory with the same file 
                        in it on your compressed partition.


NETWORK INTERFACE CARDS

If you have a network board in a 386 or 486 machine that uses a RAM or shared 
memory address, you need to exclude that address in the memory manager command
line.  To do this, edit your CONFIG.SYS file and change the EMM386 memory 
manager command.  The format will be similar to the following:

NOVELL DOS
DEVICE=C:\NWDOS\EMM386.EXE...(current options).../E=nnnn-mmmm

DR DOS
DEVICE=C:\DRDOS\EMM386.SYS...(current options).../E=nnnn-mmmm

MS DOS
DEVICE=C:\DOS\EMM386.EXE...(current options).../X=nnnn-mmmm

The /E or /X option, depending on the DOS, indicates which memory addresses to
exclude from being used by any other programs (since it is in use by your 
network board and no other programs can be loaded at the same memory 
addresses).  The nnnn and mmmm represent the beginning and ending range 
addresses, respectively, for the memory manager to exclude.  The following 
table shows the most common RAM addresses used by network boards.

	Ŀ
	  MEMORY ADDRESS    nnnn*           mmmm*        
	                               8 KB       16 KB  
	Ĵ
	       C0000        C000       C1FF       C3FF   
	       C8000        C800       C9FF       CBFF   
	       CC000        CC00       CDFF       CFFF   
	       D0000        D000       D1FF       D3FF   
	       D8000        D800       D9FF       DBFF   
	Ĵ
	 * nnnn the starting address found in the NET.CFG  
	 * mmmm the suggested ending address to be used    
	

NOTE:	If you do not know whether your network board needs 8 KB or 16 KB for 
shared memory, you should use the larger 16 KB value.

NOTE:	If you do not know the memory address your network board uses, you can
type the command:  TYPE C:\NWCLIENT\NET.CFG to determine the MEM value (the 
NET.CFG file instructs the network driver how to initialize your network 
board).

If you are not using EMM386.SYS or EMM386.EXE in the CONFIG.SYS file, add the 
following line in the [386Enh] section of the SYSTEM.INI file in your WINDOWS 
directory:

	EMMExclude=nnnn-mmmm

Replace nnnn and mmmm with the values from the tables above.  Do not worry if 
there is already an EMMExclude line in your SYSTEM.INI file.  Multiple copies 
of this line are valid and will operate correctly.


TIPS FOR RUNNING WINDOWS 3.1

Network Operations

You must run STARTNET.BAT before entering Windows.  You should also map drives
and capture ports before entering Windows such as in a personal login script 
(see the NET SAVE command for more information).  Mapping drives and capturing
ports may be performed in Windows through the Personal NetWare utility.

Failed Connections

Windows will display an error message if you try to access a drive mapped to a
server that has gone down.  Any attempt to access that drive while the server 
is down will result in the error (A)bort, (R)etry, (F)ail.  Under Windows and 
DOS, this error is trapped.  The connection to the network may be restored by 
pressing (R)etry.  (A)bort or (F)ail will remove the connection.

Most software applications will continue to function once the connection has 
been restored.  Some software applications may return general protection 
faults, or will not reconnect to the server.  In this case, it is necessary to
exit Windows and reissue the NET MAP command (or use the Personal NetWare 
utility through Windows) when the server has come back on the network.

Swap Files

Windows 3.1 can use swap files to enhance the performance of multiple tasks.  
By default, Windows will try to create a swap file on your hard disk at 
installation.  Do not try to create a permanent swap file on a network drive. 

Additionally, a temporary swap file should be installed only to the user's 
subdirectory on  a network drive.  That way, other users will not have access 
to it.  If a swap file is installed to a subdirectory that already contains 
one, it will corrupt the other swap file in that subdirectory.

If you do not have a local hard disk on which to store a permanent swap file, 
Novell recommends using a temporary swap file in your user subdirectory on the
network.  This will avoid conflicts between two users' permanent or temporary 
swap files.

NOTE:	If you are running a shared version of Windows on the server, you 
should MAP drives to the server's network directories instead of using the 
DOS SUBST command.  This is unique to a network installation of Windows 3.1.  
In all other applications, Novell recommends using the DOS SUBST command on a 
server in place of the NET MAP command.

Base I/O Addresses

I/O addresses below 300 should not be used for network boards on machines that
also use Windows.

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:

	[boot]
	network.drv=netware.drv
	(This loads the NetWare user tools)

	[boot.description]
	network.drv=Personal NetWare (v1.0)
	(This defines the Personal NetWare device version used)

     [386Enh]
	network=*vnetbios,vnetware.386,vipx.386
	(This specifies the type of network used with MS Windows 386 Enhanced 
        mode)

	TimerCriticalSection=10000
	(Personal NetWare uses this setting to ensure that network traffic on 
        your computer runs smoothly)

	ReflectDOSInt2A=TRUE

	OverlappedIO=OFF

        PSPIncrement=5

        UniqueDOSPSP=TRUE

The following modifications are made to WIN.INI:

	[windows]
	load=nwpopup.exe
	(This allows network messages to display in Windows)

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

The following modifications are made to PROGMAN.INI:

	[Groups]
	Groupx=C:\WINDOWS\PNW.GRP
	(This causes Windows to load the Personal NetWare program group in 
        Program Manager)


THIRD-PARTY DISK CACHES

Some third-party disk caches do not work with Personal NetWare 1.0 or networks
in general.  If you have problems with Windows running slowly with your disk 
cache, you may want to shrink the size of memory allocated to the disk cache.

If you are using a disk cache other than the Personal NetWare NWCACHE, you 
will need to disable the advanced writes, sometimes called delayed or deferred
writes.  To do this, you will need to refer to the documentation of your 
particular disk cache.

If you have problems with corrupted files or lockups, you may want to remove 
your disk cache.  There are some third-party caches, especially those that 
perform advanced reads and delayed writes, that have compatibility problems 
with Personal NetWare.

_Verified by customer
_Verified by Novell

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