
NETWORKS.TXT

This file contains information about making your network
compatible with MS-DOS 6.

If you are running MS-DOS 5, no changes are
required to make it compatible with MS-DOS 6. 

If Setup referred you to this file, see section 1 below. 
Otherwise, if you are looking for additional information
on your network software, find the appropriate section
below.

1.  Setup referred you to NETWORKS.TXT
2.  MS-DOS Shell and Networks 
3.  Arcnet systems
4.  3+Share
5.  Artisoft LANtastic
6.  AT&T StarGroup (non-LAN Manager) 
7.  Banyan VINES
8.  DEC Pathworks and PCSA
9.  IBM PC LAN
10. IBM DOS LAN Requester Version 1.30 or Earlier
11. Microsoft LAN Manager and 100-Percent Compatible
    Networks
12. Microsoft MS-Net and 100-Percent Compatible
    Networks
13. Net/One PC  
14. Novell Networks
15. Novell Networks and DoubleSpace
16. PC-NFS
17. TCS 10Net or DCA 10Net

1.  Setup referred you to NETWORKS.TXT 

If Setup displayed the "You have specified that your
computer is connected to a network" screen, your computer
might be running an older version of network software
that is incompatible with MS-DOS 6. Find the section in this
file that addresses your network software. If you don't find
instructions for making your network compatible
with MS-DOS 6, you should obtain an upgrade of your 
network software from your network vendor, install the 
upgraded network files, and then run Setup again. 

After you have upgraded your network software,
when Setup still displays the "You have specified
that your computer is connected to a network" screen,
choose the Continue option. Your network should work 
correctly with MS-DOS 6.

2. MS-DOS Shell and Networks
-----------------------------
Most network software won't work correctly if you start it
from a MS-DOS Shell command prompt. Start your network
before starting MS-DOS Shell.

3. Arcnet systems
------------------
If your network uses Arcnet hardware, you may need to run MSD
with the /I switch. If you must use the /I switch, do not choose 
the Networks option in MSD.

4. 3+Share
-----------
If your network software is 3+Share, contact Microsoft Product 
Support Services. For information about contacting Microsoft 
Product Support Services, see the "Welcome" section of the
Microsoft MS-DOS User's Guide.

5. Artisoft LANtastic
----------------------
Before you run Setup with any version of Artisoft LANtastic, 
make sure to shut down the LANtastic server. There is no need
to shut down the redirector.

Artisoft LANtastic versions 3.02 and higher are compatible 
with MS-DOS 6.

If you are using LANtastic versions 2.5 through 3.01,
you need to type two SETVER commands at the command prompt.
The SETVER command reports to your network software the
version of MS-DOS that it was designed to run with--in this
case, version 4.0.

If you are using a LANtastic version earlier than 2.5,
contact your network vendor for an update.

To update LANtastic versions 3.01 or earlier:

1. Shut down the LANtastic server. You may leave the
   redirector running.

2. Set up MS-DOS 6 on your computer. For more information
   about installing MS-DOS 6, see "Getting Started."

   MS-DOS may display an "Incorrect DOS version" message
   when your network restarts. Ignore it.

3. Type the following command at the command prompt:

   setver server.exe 4.00

4. Restart your computer.

If you are using EMM386, you might need to exclude the
memory area used by the network adapter card. To do this,
use the x switch with the DEVICE command for EMM386.EXE in
your CONFIG.SYS file. If you are using the factory-set
defaults for the LANtastic 2Mbps adapter, include the x=d800-
dfff switch with the DEVICE command for EMM386.EXE. If this
memory region is not excluded, you might experience problems
with programs that use expanded memory.

For more information about EMM386 options, type HELP EMM386.EXE
at the command prompt after you have installed MS-DOS 6.

NOTE
The Microsoft Defrag program is incompatible with 
LANtastic network software if the server service is loaded. 
If only the redirector is loaded, the program is compatible
with LANtastic network software.

NOTE
You cannot use DoubleSpace to compress a drive on a LANtastic server
because all local drives are viewed as network drives. To compress 
a drive, disable the server service by typing REM and space in front 
of the server command in your AUTOEXEC.BAT file, and restarting the
computer. Then run DoubleSpace. After you run DoubleSpace,
you can remove the REM command from your AUTOEXEC.BAT file.

After compressing a drive on a server, some of DoubleSpace's features--
such as the LIST, CHKDSK, MOUNT, and UNMOUNT features--will not work
correctly unless you stop the server service.

6. AT&T StarGroup (non-LAN Manager) 
------------------------------------
If your network software is AT&T StarGroup, you should run Setup
again, choose Continue when Setup displays the "You have
specified that your computer is connected to a network" screen,
and follow the instructions on your screen. If you cannot 
run your network software after Setup, carry out the following
procedure:

1  Type the following commands:

   SETVER SETUP.EXE 4.00
   SETVER ATTSTART.EXE 4.00

2  Restart your computer.

3  Use your StarGroup installation disks to remove the
   existing network software from your computer.

4  Reinstall StarGroup. When the StarGroup installation
   prompts you to indicate which version of MS-DOS you are
   using, choose MS-DOS version 4.0.

7. Banyan VINES 
----------------
Banyan VINES versions 4.1 and higher are compatible with MS-DOS 
6. You can use Banyan VINES version 4.0x with MS-DOS 6 if you
have the REDIRALL.EXE or REDIR4.EXE file in the BANYAN
directory on your hard disk.

If neither file is on your hard disk, but you have the VINES
installation disks that include one of these files, copy
the file to the directory on your hard disk that contains
network files.

If the files are not on either your hard disk or the VINES
installation disks, contact your Banyan VINES network
vendor.

If you have a VINES version earlier than 4.0, contact your
network vendor for an update.

NOTE
In some cases, Banyan VINES is incompatible with MemMaker. For
example, if your network software is loading multiple components
into different UMB regions, MemMaker may not work correctly on
your computer.


8. DEC Pathworks and PCSA
--------------------------
If you have DEC PATHWORKS for DOS version 4.1,
carry out the following procedure:

1. If you are upgrading from MS-DOS version 3.3 or earlier,
   you need to update your redirector file, REDIR.EXE. Obtain
   REDIR.400 from the PATHWORKS disks or system service,
   rename it to REDIR.EXE, and place it in your DECNET
   directory.

2. Install MS-DOS 6 on your computer. For more information about 
   installing MS-DOS 6, see "Getting Started."

Version 4.0 of PATHWORKS for DOS is compatible with MS-DOS
6. However, you must take several steps to achieve this
compatibility.

To update PATHWORKS version 4.0:

1. If you are upgrading from MS-DOS version 3.3 or earlier,
   you need to update your redirector file, REDIR.EXE. Obtain
   REDIR.400 from the PATHWORKS disks or system service,
   rename it to REDIR.EXE, and place it in your DECNET
   directory.

2. Install MS-DOS 6 on your computer. For more information about 
   installing MS-DOS 6, see "Getting Started."

3. Restart your computer, but do not yet run STARTNET.BAT,
   which starts the network.

4. Type each of the following lines at the command prompt:

   setver use.exe 4.00

   setver memman.exe 4.00

   setver lad.exe 4.00

   setver show.exe 4.00

   setver netsetup.exe 4.00

5. Restart your computer, and run STARTNET.BAT.

Note: If you upgrade to PATHWORKS 4.1 from PATHWORKS 4.0,
      you must disable the SETVER commands you typed in this
      procedure. To do this after you install PATHWORKS 4.1,
      type the same commands, but replace the 4.00 with /d in
      each command.

If you are using a version of PATHWORKS or PCSA earlier than
4.0, contact your network vendor for an update. Meanwhile,
if you are using PATHWORKS or PCSA version 3.x, you can
start using MS-DOS 6 by carrying out the following
procedure.

Note: To get support for MS-DOS Task Swapper, use
      PATHWORKS for DOS version 4.1 or later.

To temporarily update PATHWORKS or PCSA version 3.x:

1. If you are upgrading from MS-DOS version 3.3 or earlier,
   you need to update your redirector file, REDIR.EXE. Obtain
   REDIR.400 from the PATHWORKS disks or system service,
   rename it to REDIR.EXE, and place it in your DECNET
   directory.

2. Install MS-DOS 6 on your computer. For more information about 
   installing MS-DOS 6, see "Getting Started." MS-DOS might display 
   a series of "Incorrect DOS version" messages when your network 
   restarts. Ignore these.

3. Type all of the following commands at the command
   prompt:

   setver use.exe 4.00
   setver emsload.exe 4.00
   setver sch.exe 4.00
   setver netsetup.exe 4.00
   setver ncp.exe 4.00
   setver dnnethat.exe 4.00
   setver lad.exe 4.00
   setver dll.dxe 4.00
   setver memman.exe 4.00
   setver dnnethld.exe 4.00
   setver show.exe 4.00

4. Restart your computer.

9. IBM PC LAN
--------------
If you use IBM PC LAN 1.34 and have problems with
applications that use record locking or file locking, you
may need an updated REDIR50.EXE file included in ICO 3039.
Contact IBM Support Channel.

IBM PC LAN Program Version 1.33 or Earlier

To use MS-DOS 6 with IBM PC LAN Program (PCLP), you need
one of the following:

o IBM PCLP version 1.34 installed.

o IBM PCLP version 1.3x that has been updated to version
  1.34 by applying the appropriate IBM Corrective Service 
  Disks. Contact IBM Product Support to obtain the software 
  you need.

If you are running a PCLP version earlier than 1.30, contact
IBM for the necessary software and instructions.

To update IBM PCLP versions 1.30 through 1.34:

1. Skip to step 3 if you are upgrading from version 1.34.
   Otherwise, install the necessary IBM PCLP software by 
   following the instructions included with the Corrective 
   Service Disk(s) you received from IBM.

2. Restart your computer, and make sure the network starts.

   If the network doesn't start, quit this procedure and
   contact IBM for help.

3. Set up MS-DOS 6 on your computer. For more information
   about installing MS-DOS 6, see the chapter "Getting 
   Started."

4. Restart your computer.

   The following message appears on your screen:

   Start PC LAN Program 1.3 (Y/N)?

5. Type n, and press ENTER.

6. Type the following at the command prompt:

   setver net.com /d

7. Restart your computer.

   The following message appears on your screen:

   Start PC LAN Program 1.3 (Y/N)?

8. Type y, and press ENTER.

   Note: If, after setting up MS-DOS, your CONFIG.SYS file
         has a command for loading the IFSFUNC.EXE file,
         disable it by typing "rem" and a space in front
         of the command. Then save the file and restart
         your computer.

   Note: The Microsoft Defrag program will not run on a PCLP
         server.

10. IBM DOS LAN Requester Version 1.30 or Earlier
--------------------------------------------------
To use MS-DOS 6 with IBM DOS LAN Requester, you need one
of the following:

o DOS LAN Requester files that are included with OS/2 LAN
  Server version 1.30.1.

o DOS LAN Requester files that come with OS/2 LAN Server
  version 1.30, which has had IBM Corrective Service
  Diskette (CSD) 5015 applied to it.  Contact IBM Product
  Support to obtain the software you need.

If you are running a DOS LAN Requester version earlier than
1.30, contact IBM for the necessary software and
instructions.

To update IBM DOS LAN Requester version 1.30:

1. Upgrade your DOS LAN Requester software to version
   1.30.1 by following the instructions included with IBM
   Corrective Service Disk 5015.

2. Restart your computer and make sure the network starts.

   If the network doesn't start, quit this procedure and
   contact IBM for help.

3. Set up MS-DOS 6 on your computer. For more information
   about installing MS-DOS 6, see the chapter "Getting 
   Started."

4. Restart your computer.

   The following message appears on your screen:

   Start DOS LAN Requester (Y/N)?

5. Type n, and press ENTER.

6. Type the following at the command prompt:
 
   setver net.com /d

7. Restart your computer.

   The following message appears on your screen:

   Start DOS LAN Requester (Y/N)?

8. Type y, and press ENTER.

   Note: If, after setting up MS-DOS, your CONFIG.SYS file
         has a command for loading the IFSFUNC.EXE file,
         disable it by typing "rem" and a space in front
         of the command. Then save the file and restart
         your computer.

11. Microsoft LAN Manager and 100-Percent Compatible
    Networks
-----------------------------------------------------
If you are running any version of Microsoft LAN Manager
or a 100-Percent Compatible network, and Setup referred
you to this file, contact Microsoft for updated network
files. 

12. Microsoft MS-Net and 100-Percent Compatible
    Networks
------------------------------------------------
If you are running any version of Microsoft MS-Net
or a 100-Percent Compatible network, and Setup referred
you to this file, contact Microsoft for updated network
files.

13. Net/One PC
---------------
If Ungermann-Bass Net/One PC does not load with MS-DOS 6,
do one of the following:
                              
*    Contact your vendor to get an updated LOADNIU.EXE file.
*    Put a UBPAUSE command between the LOADNIU and XNSBIOS
     lines of the MSNET.INI file.
*    Issue network commands from a batch file that includes a
     PAUSE command between the LOADNIU and XNSBIOS lines.
     
14. Novell Networks
--------------------
As of publication of this file, the current version of the
workstation shell is 3.31. You should obtain version
3.31 or later for use with MS-DOS 6.

If you have a NetWare version earlier than 2.1, or your network
software uses any of the following files, contact your network
vendor:

NET3.COM
NET4.COM
XMSNET3.EXE
XMSNET4.EXE
EMSNET3.EXE
EMSNET4.EXE

If you can't use Task Swapper in MS-DOS Shell when running
a Novell network, contact your network vendor.

If you can't load MS-DOS 6 on your remote-boot workstation,
contact Novell for the RPLFIX.COM file.

If you run LOGIN.EXE, MAP.EXE, and SESSION.EXE from MS-DOS
Shell or while MS-DOS Shell is running, a search path is not
added to the existing path. Use these programs before starting
MS-DOS Shell.

If you use the Novell login program to set the COMSPEC
variable after starting MS-DOS 6, and you can't
reload the COMMAND.COM file, edit the SHELL command line
in your CONFIG.SYS file. Make sure the path to
COMMAND.COM points to the root directory and remove the
c:\dos\ parameter that follows the path, if one exists.

For example, suppose your SHELL command line looks like
this:

    SHELL=C:\DOS\COMMAND.COM  C:\DOS\  /P  /E:512

Change it to look like this:

    SHELL=C:\COMMAND.COM  /P  /E:512

Or contact your Novell vendor to get a new login program.

If you are having problems using Microsoft Undelete on 
a Novell network, use the MAP ROOT command in conjunction
with the delete-sentry method of protection. (If you have
Novell Netware version 2.15c or older, obtain the most
recent MAP.EXE file from your network vendor.) For example,
you would use the following MAP ROOT syntax (normally
specified in the server's login script):

MAP ROOT F:=COUNT/SYS:USERS/JOEB

where F is the network drive letter, COUNT is a file server name,
SYS is the volume name, USERS is a subdirectory of volume SYS, and
JOEB is the root for a network user. On JOEB's computer, the
AUTOEXEC.BAT would contain the following syntax:

UNDELETE /SF

where /S specifies the delete-sentry method of protection and F
specifies a network drive to be protected. The AUTOEXEC.BAT should
specify /S[drive] for each drive to be protected.

NOTE
If you back up files to a network and your network software is NetWare
286, the gas gauge in Microsoft MS-DOS and Windows Backup will move very
slowly at first. This is due to the way NetWare 286 handles writing 
files to the network.

NOTE
The %OS_VERSION parameter used in login scripts will return v5.00 if
you are using any shell up to, and including, version 3.31. Until
Novell releases an updated shell, you should refrain from using
the %OS_VERSION parameter or you should map a v6.00 drive over 
the existing v5.00 drive in a user's login script.

15. Novell Networks and DoubleSpace
------------------------------------
When you load netx.com, it establishes a network drive 
connection using the drive letter that follows the drive 
letter specified with the LASTDRIVE command in your 
CONFIG.SYS file. This also applies to any of the following 
files:

NET5.COM
BNETX.COM
BNETX.EXE
XMSNET5.EXE
XMSNETX.EXE
EMSNET5.EXE
EMSNETX.EXE

If you don't specify a LASTDRIVE command, MS-DOS uses "E"
as its default, and your network software uses "F" when it 
establishes a network connection.

By default, DoubleSpace reserves four drive letters between the
local compressed drive and the host drive for the Compressed 
Volume File (CVF). These drive letters are reserved for future use
by such items as a RAMDRIVE, a CD-ROM drive, or a second hard 
drive. Thus, a drive letter conflict can arise when you compress 
your local drive.

For example, if you have one logical partition C on your hard drive,
and you compress drive C, DoubleSpace reserves drive letters
"D" through "G" for future use and "H" for the drive hosting
the CVF. If you had not specified a LASTDRIVE command, your 
network software would use the drive letter following the
host drive--in this case "I". In your AUTOEXEC.BAT file or in the 
batch file you use to log on to the nework, any commands that 
assume the network drive has a different drive letter will cause 
problems.

There are two ways of avoiding drive conflicts:

* When you install DoubleSpace, run it in Custom mode. Then specify
  for your host drive a letter that won't conflict with the letter
  your network software uses. For example, if your network drive is
  currently "F," you could use "E" for your host drive when you
  install DoubleSpace.

* Change the drive references in your AUTOEXEC.BAT file or batch file you
  use to log on to the network. Make sure the references match
  what your network software will default to after you have installed
  DoubleSpace. Also, if you log in manually, use a drive letter that          
  follows the drive letter DoubleSpace uses for the host drive.


16. PC-NFS
---------------
If you use SETVER to report a different version of a program
to MS-DOS, PC-NFS 3.x may report the program's version 
incorrectly. If you are having this problem, contact
your network vendor for updated network software.

If you use PC-NFS 3.0 with MS-DOS Shell, MS-DOS Shell may
display more drives than you have currently enabled. To
prevent this, use the PC-NFS /d switch to specify the number
of drives you are using. For more information, see your PC-
NFS documentation.

If you can't use the COPY or XCOPY command on PC-NFS 3.01,
contact your vendor to get an updated version of the
PCNFS.SYS device driver.

If you use PC-NFS network software, carry out the following procedure
before you run MemMaker:

1. Open your MEMMAKER.INF file using any text editor. This file is
   in the directory that contains your MS-DOS files.

2. Add the following line to the file:

   *NET

3. Save the file, and then run MemMaker.


17. TCS 10Net or DCA 10Net 
---------------------------
DCA 10Net Plus Versions 4.20 (20) and later, and DCA
10Net versions 3.3 (41) and later are compatible with
MS-DOS 6. If you have an earlier version, contact
your network vendor for an update.

If you are running a compatible version of 10Net Network 
Software, disable the network software, and then run MS-DOS 6 
Setup. After you install MS-DOS 6, reenable your network
software.

NOTE
The Microsoft Defrag program is incompatible with 
10Net network software if the server service is loaded. 
If only the redirector is loaded, the program is compatible
with 10Net network software.

NOTE
You cannot use DoubleSpace to compress a drive on a 10Net server
because all local drives are viewed as network drives. To compress 
a drive, disable the server service by typing REM and space in front 
of the server command in your AUTOEXEC.BAT file, and restarting the
computer. Then run DoubleSpace. After you run DoubleSpace,
you can remove the REM command from your AUTOEXEC.BAT file.

After compressing a drive on a server, some of DoubleSpace's features--
such as the LIST, CHKDSK, MOUNT, and UNMOUNT features--will not work
correctly unless you stop the server service.
