Category : Network Files
Archive   : NOVELFAX.ZIP
Filename : 1012550.TXT

FYI

(Note: 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.)

TITLE: NWLite 1.1 and Windows 3.1 Compatibility
DOCUMENT ID#: FYI.P.6122
DATE: 29JAN93
PRODUCT: NetWare Lite
PRODUCT VERSION: All versions
SUPERSEDES: FYI.P.6077
LITE FAX DOC #: 2550

SYMPTOM

NA

ISSUE/PROBLEM

NetWare Lite 1.1 and Windows 3.1 Compatibility

Installing Windows 3.1 on a NetWare Lite 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
NetWare Lite v1.1 in both Stand Alone and Shared Network versions. The
second section, entitled "DR DOS 6.0 Configuration Items," discusses
general suggestions for configuring DR DOS 6.0, NetWare Lite v1.1, and
Windows 3.1 to have a peak performance among the three. The last
section, "Tips for Running Windows 3.1," describes general items
regarding Windows 3.1 and NetWare Lite v1.1 regardless of what operating
system you are using.

Installing Windows 3.1

Installing a Stand Alone Version of Windows 3.1

Follow the regular installation procedures to install Windows 3.1 as a
stand alone version. To be able to access network resources, run the
setup program and select "No Network Installed" as the network type. 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 NetWare Lite
Server then for a NetWare Lite 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: ).

3. Type SETUP /A. When Windows prompts for the network path to which
it should install, type C:\WINDOWS 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 NetWare Lite menu utility by typing NET and pressing
. Then select "Supervise the network" and then "Network
directories" options. Create a network directory by pressing the
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. Press
to exit and save the changes, and exit back to the Main Menu.

5. At the Main Menu in the NET utility, select "Supervise the Network,"
then select "Server Configuration." The CLIENT TASKS option
defaults to 10 at the time of NetWare Lite installation. Set the
CLIENT TASKS in the FUTURE column to 15 per machine connected to the
network. (For example, if you had three computers on the network,
you would set the client tasks to 45.)

6. When NetWare Lite is installed, the FILES=xx in the CONFIG.SYS file
is set to be at least 30. This needs to be increased on the server
by 20 per machine connected. You can change this by using a text
editor (such as DR-DOS 6.0 EDITOR) to edit the CONFIG.SYS file.

7. 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 in the previous steps. 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 run from the shared copy
installed on the server in the steps above.

Setting up Windows in this way will take up less disk space
than option A above. However, it will run slower and client
machines still must 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 in
the steps above.

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, and C above.

Option A. Copy all files to the Client machine's hard drive.

1. Load NetWare Lite by typing STARTNET. Map a drive to the
network directory that was created on the server in the Steps
for Configuring a Server listed above. For example, if the
Network Directory you created in step 4 above was WIN31, you
would type the following:

NET MAP I: WIN31

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

I:

3. Type SETUP and press , 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 to "let you make the
modifications later" option. You will then be prompted with a
path and file name 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.

DR DOS 6.0 None of these changes are necessary if you are
running 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. See the section on
"Third-Party Disk Caches," towards the end of
this document. It is suggested that you run
with either NetWare Lite NLCache or DR-DOS
PCKwik disk cache.

In the CONFIG.SYS file, Windows will usually try
to include its own memory manager, which
includes the HIMEM.SYS file, and the EMM386.EXE
file. 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 these 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 to MS-DOS to handle
hardware interrupts.

5. Follow the prompts to continue the installation of Windows.
Note: When prompted to install printers, select and install
any printers you have connected. Make sure they are specified
as connected to port LPT1.DOS or LPT2.DOS, depending on which
ports you have captured to network printers, instead of the
normal LPT1 and LPT2 ports. See "Network Printing and Windows
3.1" later in this document.

In the printer configuration, you will need to turn off the
"Fast Printing Direct to Port" option. Printing with this
enabled bypasses any DOS calls; therefore, you would not be
able to print to network printers. To do this, choose
"Connect" at the printer definition window. Turn of the "Fast
Printing Direct to Port" option.

6. Continue following the prompts to finish the installation of
Windows.

After you finish the installation of Windows, you will need to
edit the SYSTEM.INI file in the directory to which you
installed Windows. See the section "Changes to SYSTEM.INI"
towards the end of this document.

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. Custom configuration files are copied to the Client machine's
hard drive. All other files will be run from the shared copy
installed on the server in the steps above.


1. Load NetWare Lite by typing STARTNET. Map a drive to the
network directory that was created on the server in the Steps
for Configuring a Server listed above. For example, if the
Network Directory you created in step 4 above was WIN31, you
would type the following:

NET MAP I: WIN31

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

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

I:

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

þ Also, at the configuration screen, select the "No Network
Installed" Network option.

5. When Windows prompts you, choose to "let you make the
modifications later" option. Then you will be prompted a path
and file name 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.

DR DOS 6.0 None of these changes are necessary if you are
running DR DOS. You will only need to verify,
after installing Windows, that the network
directory where the shared version of Windows is
installed and the user subdirectory to which you
installed the custom configuration files (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. See the section on
"Third-Party Disk Caches," towards the end of
this document. It is suggested that you run
with either NetWare Lite NLCache or DR-DOS
PCKwik disk cache.


In the CONFIG.SYS file, Windows will usually try
to include its own memory manager, which include
the HIMEM.SYS file, and the EMM386.EXE file.
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
these 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 to MS-DOS to handle hardware
interrupts.

6. Follow the prompts to continue the installation of Windows.
Note: When prompted to install printers, select and install any
printers you have connected. Make sure they are specified as
connected to port LPT1.DOS, or LPT2.DOS, depending on which
ports you have captured to network printers instead of the
normal LPT1 and LPT2 ports. See the "Network Printing and
Windows 3.1" section later in this document.

In the printer configuration, you will need to turn off "Fast
Printing Direct to Port" off. Printing with this enabled
bypasses any DOS calls; therefore you would not be able to
print to network printers. To do this, choose "Connect" at the
printer definition window. Turn off the "Fast Printing Direct
to Port" option.

7. Continue following the prompts to finish installing Windows.

After you finish the installation of Windows, you will need to edit
the SYSTEM.INI file in the subdirectory to which you installed
Windows custom configuration files (C:\DAVE in this example). See
the "Changes to SYSTEM.INI" section towards the end of this
document.

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

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 in
the steps above.

1. Load NetWare Lite by typing STARTNET. Map a drive to the
network directory that was created on the server in the "Steps
for Configuring a Server" section listed above. For example,
if the Network Directory you created in step 4 above was WIN31,
you would type the following:

NET MAP I: WIN31

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

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

þ Enter the NetWare Lite menu utility by typing NET and
pressing .

þ Then select the "Supervise the network" then "Network
directories" options.
þ Create a network directory by pressing the key.
þ Select the server on which you want to store your custom
files.
þ Enter the path of the subdirectory you created in step 3,
such as C:\STEVE.

4. Map a drive to this network directory:

NET MAP G: STEVE

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

I:

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:).

þ Also, at the configuration screen, select the Network
option "No Network Installed."

7. When Windows prompts you, choose to "let you make the
modifications later." You will then be prompted a path and
file name 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.

DR DOS 6.0 None of these changes are necessary if you are
running DR DOS. You will only need to verify,
after installing Windows, that the network
directory where the shared version of Windows is
installed and the network directory to which you
installed the custom configuration files (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. See the section on
"Third-Party Disk Caches," towards the end of
this document. It is suggested that you run
with either NetWare Lite NLCache or DR-DOS
PCKwik disk cache.

In the CONFIG.SYS file, Windows will usually try
to include its own memory manager, which include
the HIMEM.SYS file, and the EMM386.EXE file.
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
these 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 to MS-DOS to handle hardware
interrupts.

8. Follow the prompts to continue the installation of Windows.
Note: When prompted to install printers, select and install
any printers you have connected. Make sure they are specified
as connected to port LPT1.DOS, or LPT2.DOS, depending on which
ports you have captured to network printers, instead of the
normal LPT1 and LPT2 ports. See the "Network Printing and
Windows 3.1" section later in this document.

In the printer configuration, you will need to turn off "Fast
Printing Direct to Port" option. Printing with this enabled
bypasses any DOS calls; therefore, you would not be able to
print to network printers. To do this, choose "Connect" at the
printer definition window. Turn off the "Fast Printing Direct
to Port" option.

9. Continue following the prompts to finish installing Windows.

After you finish the installation of Windows, you will need to edit
the SYSTEM.INI file in the network directory to which you installed
Windows custom configuration files (G: in this example). See the
"Changes to SYSTEM.INI" section towards the end of this document.

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.

DR DOS 6.0 Configuration Items:

The following items are for maximizing performance of Windows 3.1 on a
NetWare Lite 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, there were changes made 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, there are certain things you can do to
optimize the performance of Windows and NetWare Lite v1.1. First,
you will need to have a line in your CONFIG.SYS file that calls the
Super PC-Kwik Windows driver, called PCKWIN.SYS. A sample command
line for this would be the following:

DEVICE=C:\DRDOS\PCKWIN.SYS.

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


/H- This option needs to be added for compatibility with
NetWare Lite. It turns off the advanced reads and writes
that can cause data corruption on some networks. There
will still be read caching that is performed and not just
the advanced reads and writes.

/L:xxx

/R:xxx Both of these options, if present on the command-line of
SUPERPCK, should be removed. PC-Kwik defaults to use all
available extended or expanded memory for the disk cache.
Then it will, if a request is made by some application
such as Windows, turn around and lend up to half of that
memory back. That is controlled by these options.

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:xxx This option instructs SUPERPCK how much memory to use for
its cache, and you do not have to worry about how much is
getting lent back. You just tell the cache exactly how
much you do want it to use.

If you do not include an amount (xxx), the /S: option will
default to all available extended memory. The following
are suggested amounts of memory to allocate to the cache
through the /S: parameter based on the amount of RAM in
your machine.

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ AMOUNT OF RAM ³ SUGGESTED 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 reason for the small cache sizes is that Windows needs
all the memory that it can get to perform at its peak. By
taking RAM away from Windows and allocating it to a cache,
Windows may be forced to use a swap file on disk where it
could have run more from RAM if no cache or a smaller
cache had been allocated. So by having a small cache, you
increase disk performance, and you also leave as much
memory available to Windows as possible so that it will be
running at an optimum speed.

3. 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.SYS command. The format will be similar to
the following:

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

Where /E tells the memory manager (EMM386.SYS) not to allocate the
range from nnnn to mmmm to any other programs. (It is in use by
your network board; and you need to make sure that no other programs
are loaded at the same memory addresses). The nnnn and mmmm
represent beginning and ending range addresses for the range to
exclude. The following table shows the most common RAM addresses
used by network boards, and the values for nnnn and mmmm based on
those values.

ÚÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÂÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ¿
³ MEMORY ADDRESS ³ nnnn* ³ 8 KB---mmmm*--16 KB ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÅÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
³ C0000 ³ C000 ³ C1FF C3FF ³
³ C8000 ³ C800 ³ C9FF CBFF ³
³ CC000 ³ CC00 ³ CDFF CFFF ³
³ D0000 ³ D000 ³ D1FF D3FF ³
³ D8000 ³ D800 ³ D9FF DBFF ³
ÃÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÁÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ´
³ * nnnn indicates starting memory address as found in NET.CFG file.³
³ * mmmm indicates 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:\NWLITE\NET.CFG and look at the MEM
value. (The NET.CFG file instructs your board driver how to
initialize your network board.)

If you are not using EMM386.SYS 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.

Note: For more information on the EMM386.SYS exclude command-line
option, please see pages 17 through 19 in the DR DOS 6.0
Customization and Optimization Tips manual.

4. If you are running on a SuperStored drive, be aware that swap files
(whether permanent or temporary) cannot exist on a compressed
partition of your hard drive. If your entire hard drive is
compressed or if not enough room is on the uncompressed partition,
you will either have to run without a swap file or go through a few
steps to reset your SuperStore partition.

Swap files are written to the disk in nonstandard formats. This
gives it the benefit of a fast access time. However, swap files may
not be created on SuperStored partitions.

If you decide you want to have a swap file on your hard drive that
is SuperStored and do not have the space on the uncompressed
partition, the following steps can help you set up your drive again
for use with Windows:

a. Backup all data on the compressed partition of your hard drive.
You will be removing the SuperStore 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 SuperStore utility (SSTOR)
and choosing "remove" to remove the SuperStore partition.

Note: If the entire hard disk was SuperStored, you may need to
reinstall DR DOS because removing the SuperStore partition will
remove any files on your hard disk thus removing your DR DOS
files.

c. Recreate the SuperStore partition by running SuperStore and
choosing "create." When prompted, enter the amount of space to
be left uncompressed. You will need to enter this amount 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. (A 5 MB swap
file is a good size.)

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

There is one more thing to remember about SuperStored
partitions. When Window searches for the memory manager
(EMM386.SYS), it will be searching for the manager in the same
path from which it was loaded. You will need to make sure that
the EMM386.SYS driver is in the same subdirectory on both the
compressed and noncompressed partitions of your hard drive.
For example, if the EMM386.SYS file is in the DRDOS
subdirectory on your noncompressed partition, make sure that
there is a DRDOS subdirectory with the same file in it on your
compressed partition.

TIPS FOR RUNNING WINDOWS 3.1

Network Operations

You should run STARTNET.BAT before entering Windows. You should also map
drives and capture ports before entering Windows.

Mapped Drives and Connections

Windows will display an error message if you try to access a drive on a
server that has gone down. Any attempt to access that drive will fail.
Under regular DOS, this error is trapped and the client saves enough
information to automatically restore the connection to that network
directory when the downed server returns to the network. Windows
prevents regular DOS from trapping this error. To restore connections to
your mapped drive, exit Windows and reissue the NET MAP command when the
server is back on the network.

Network Printing and Windows 3.1

If you want to print from Windows to a network printer, you must setup
the printer in Windows as a printer on port LPT1.DOS (that replaces
LPT1.OS2 in Windows 3.0) or LPT2.DOS depending on which port is captured.
This is to instruct Windows to use the information that DOS provides it
(such as a NET CAPTURE command you may have issued to print to the
network printer) to print to LPT1 instead of trying to go to its own
physical LPT port.

In the printer configuration, you will need to turn off "Fast Printing
Direct to Port" option. Printing with this enabled bypasses any DOS
calls; therefore, you would not be able to print to network printers. To
do this, go into the Control Panel, in Printers, and highlight the
printer. This option will show up after highlighting the printer and
choosing "Connect." Turn off "Fast Printing Direct to Port" option.

You will also want to disable the Print Manager inside Windows for the
best printing performance. The reason for this is that using the print
manager only makes the print job go through two print spoolers. It
passes once through the print manager, then through the NetWare Lite
spooler. This only takes more time and will slow down your printing.

NetWare Lite Messages

Messages sent to network users through NetWare Lite will not be received
if the user to whom you are sending the message is in Windows.

Windows Modes

If you are experiencing a problem that only occurs when NetWare Lite is
loaded and if the problem seems unsolvable, experiment with the other
Windows mode to see if the problem is corrected. The Windows mode can be
changed by using one of the following command line parameters:

Standard Mode: WIN /S
Enhanced Mode: WIN /3

(Note that Windows 3.1 does not include an option to run in Real Mode as
did version 3.0.)

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 or create temporary swap files on any network drive other
than a separate user subdirectory to which other users will not have
access. It will corrupt any other swap file that may be in that
subdirectory. Every user needs to have access to their own swap files.

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
network directories and not use the DOS SUBST command. This is unique to
Windows 3.1. In all other applications, Novell recommends using the DOS
SUBST command on a server in place of the NET MAP command.)

Interrupts

VPICDA.386 is a patch written by Microsoft that fixes problems that arise
when network boards are set to an interrupt of 2, 3, or 9 and above, for
use with Windows 3.0. Microsoft states that you no longer need this
patch with Windows 3.1. If you run across problems using these
interrupts, check to see if you have a conflict with some other device
using the same interrupt. Interrupt 2, being used by a machine with a
VGA monitor, is the most common conflict that people run into. (See Fax
Document 2601 or FYI.P.6054 for information on resolving interrupt and
I/O address conflicts.)


Base I/O Addresses

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

Changes to SYSTEM.INI

Make sure that the following lines are in the [386Enh] section of the
Windows SYSTEM.INI file:

[386Enh]
UniqueDOSPSP = ON
PSPIncrement=5
TimerCriticalSection=10000
ReflectDOSInt2A=ON
OverlappedIO=OFF

If you do not have these options set, you will not be able to enter
Windows if you have NetWare Lite loaded. You will be given a message
that they need to be added and returned to the DOS prompt. The purpose
of these changes is to enhance the compatibility between Windows and
networks.

Changes to WIN.INI

There are several options you can set in the WIN.INI file for network
control. NetWare Lite does not require using anything other than the
default values for these options. Consult your Windows documentation for
further information if you wish to change these options.

Third-Party Disk Caches

Some third-party disk caches do not work with NetWare Lite v1.1 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 as explained in the section "DR DOS 6.0 Configuration
Items," number 2, which discusses Super PCKwik.

If you are using a disk cache other than the NetWare Lite NLCache, you
will need to disable the advanced reads and 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 NetWare Lite.

Third Party Memory Managers

If you have questions about your memory manager, you may want to check
the section DR DOS 6.0 Configuration Items, numbers 3 and 4, which
discuss EMM386.SYS, the memory manager that ships with DR DOS 6.0.
Though the syntax of commands may be different, the items that you need
to do are usually the same. You will need to refer to your documentation
on your memory manager to decide the best format for those commands.

SOLUTION

NA