PUB2: Network Admin Can Use WordArt but Users Cannot

Q112832

------------------------------------------------------------------------
The information in this article applies to:

 - Microsoft Publisher for Windows, versions 2.0, 2.0a
------------------------------------------------------------------------

SYMPTOMS
========

If Microsoft Publisher 2.0 is installed as a shared application on a Novell
Network (for example, NetWare 3.11), a person with administrators' rights
to the server drive will be able to use WordArt from within Publisher as
the destination application. Users without administrative network rights,
however, may receive an error message such as:

   Cannot launch or communicate with server application.

CAUSE
=====

This problem may occur if the program is installed (using SETUP /A) on the
network drive that was accessed using the Novell Map command, instead of
the Novell Map Root command.

WORKAROUND
==========

The installation of Publisher as a shared application (as outlined in
Appendix D, page 383-385 of the "Microsoft Publisher User's Guide" for
version 2.0) on a Novell Network can be successfully accomplished if the
Map Root command (not the Map command) is used to connect the network
(remote) drive. This will ensure consistent pathing information between the
administrator's (full rights) network installation and the users' (limited
rights) workstation installation. The Map Root command is used for both the
administrative (SETUP /A) and workstation (SETUP /N) routines.

MORE INFORMATION
================

Beginning with version 3.01, Novell NetWare includes the Map Root command,
which is an addition to the Map command. It allows directories to be mapped
as the root of a logical drive, making it impossible to change the
directory to a parent directory. The Map Root command is used with the same
syntax as the Map command (see below).

For Windows 3.1, Novell recommends mapping drives and setting a path on a
Novell Network by:

1. Using the Map Root command to map each drive

2. Using the MS-DOS Set Path command to set an MS-DOS path variable to
   avoid having the path overwritten by the login script

   You can also avoid this problem as follows:

    - Configure your AUTOEXEC.BAT file to log you onto the network and
      then execute the MS-DOS PATH statement.

      -or-

    - Log on manually after the AUTOEXEC.BAT file and then run
      a batch (.BAT) file after logging on to restore the path.

Using this method resolves pathing problems with a server drive.

Additional query words: 2.00 administrator 2.00a mspub