

NOVELL TECHNICAL INFORMATION DOCUMENT

DOCUMENT PROCESSING INFO:
TITLE:  DR DOS 6 & NOVELL NETWARE
DOCUMENT ID:  TID800063
DOCUMENT REVISION:  A
DATE:  18AUG94
AUTHOR:  SNICOSIA;CEREKSON
ALERT STATUS:  Yellow
DISTRIBUTION:  Public
INFORMATION TYPE:  Symptom Solution
README FOR:  NA
NOVELL PRODUCT CLASS:

Desktop Products

NOVELL PRODUCT and VERSION:

DR DOS 6.0

CATEGORY:

Client

ABSTRACT:

N/A

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

SYMPTOM

SYMPTOM:

INFORMATION ON USING DR DOS 6 WITH NETWARE

CAUSE

ISSUE/PROBLEM:

DR DOS 6.0 is internally compatible with DOS 3.31 data structures.  As a
result, when the Novell NetWare shell programs check DR DOS 6 for a
version number, it reports 3.31.  This requires special consideration
when installing DR DOS with NetWare.

SOLUTION

SOLUTION:

Here are some guidelines for the installation of DR DOS with NetWare.

Server Installation

Non-dedicated NetWare requires the use of extended memory for the system. 

It is not possible to use any of the MemoryMAX utilities on such a system. 
This will be true of any memory manager. Please consult the NetWare
installation manuals for information on non-dedicated NetWare server
installation.

When configuring a network so that all the system utilities are loaded on
the server, the NetWare server should contain copies of all the required
DOS files used at each workstation.  When a DR DOS 6.0 workstation is
logged onto the network, at least one of the workstation's network drives
will be mapped to the directory on the server holding the DR DOS 6.0
system files.

Refer to the DR DOS 6.0 User Guide, Appendix F, for information on
configuring a NetWare server to properly load the DR DOS 6.0 operating
system on remote diskless workstations.

Workstation Installation

When installing DR DOS on a network workstation that is part of an
existing network, you will usually not have to make any changes to the
workstation. Simply install DR DOS once the NetWare server has been
updated with the DR DOS 6.0 operating system.  If you are upgrading from
DOS 3.x to DR DOS 6.0, it should not be necessary to upgrade your existing
NetWare shells.  However, if you are upgrading from DOS 4.x or MS-DOS 5,
you will have to use NetWare shells intended for use with DOS 3.x.  You
can use the proper set of NetWare shell programs obtained from your
network administrator or Novell, or you can use the set provided in the
NETWARE directory on the DR DOS 6.0 ViewMAX installation
diskette.

If you have to change shell programs, you might need to generate a new
IPX.COM
program to accompany the new shell version. Consult the Novell NetWare
reference manuals or your network administrator for information on how to
accomplish this.

Using TaskMAX with NetWare

Before using TaskMAX on a NetWare workstation, you must update your
NetWare
shell programs must be updated.  The necessary files are provided in the
NETWARE directory on the last DR DOS floppy diskette (labelled ViewMAX). 
This
update should be done by the Network System Administrator.

Under most circumstances, no further adjustments will be necessary to run
TaskMAX on a NetWare workstation.

Load the NetWare shell programs and have all drives and printers mapped
before
loading TaskMAX.  If NetWare utilities like MAP, LOGIN, and SESSION are
run
from more than one task, the resulting drive and printer mappings might
not
work as expected.

If one or more applications run under TaskMAX makes direct calls to the
Novell IPX or SPX TSR program (sometimes called a peer-to-peer
application), there may be a need to load the IPX data buffering program
called TBMI2.COM before loading TaskMAX.  This program will handle the
buffering of information from IPX or SPX so that data is not lost after

switching away from one of these peer-to-peer applications. Further
information on TBMI2.COM can be found in a file called TBMI2.DOC on the DR
DOS 6.0 ViewMAX diskette.

Using MemoryMAX with NetWare

When using the DR DOS 6.0 operating system on a NetWare workstation that
supports upper memory, you can relocate the required NetWare programs can
be relocated outside conventional memory and into upper memory. These
programs can be loaded into upper memory using the HILOAD command in the
AUTOEXEC.BAT file or from the DR DOS command line.

Using HILOAD

When upper memory is available and when FREE areas exist large enough to
contain the NetWare programs, the HILOAD command can be used to move the
NetWare programs into upper memory.  Upper memory is made available by
loading the appropriate MemoryMAX driver at boot time and executing the
MEMMAX +U command to open upper memory so that it will accept programs
loaded by HILOAD. The following four lines describe one way to load the
NetWare programs using HILOAD:

MEMMAX +U
HILOAD IPX.COM
HILOAD NETX.COM
MEMMAX -U

These lines can be appended to the AUTOEXEC.BAT file or they can be
executed from the DR DOS command line.  The DR DOS INSTALL program will
automatically insert the command, MEMMAX -U >NUL, into the AUTOEXEC.BAT
file, so MEMMAX +U must be added to override it.  The >NUL portion of the
command instructs the DR DOS 6.0 operating system not to display the
output of the MEMMAX command on the screen.

Note:
*HILOAD will work only with the DR DOS MemoryMAX drivers, and not with
third party memory managers such as QEMM386.SYS and 386MAX.SYS.

*HILOAD will not run after the NET?.COM shell has been loaded.  This is
because Novell replaces the DOS routines (INT 21 functions) that handle
HILOADs under the DR DOS 6.0 operating system with their own routines,
which cannot place programs into upper memory.

KEY WORDS:
DR6 NETWARE

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