Microsoft KB Archive/102096

From BetaArchive Wiki
< Microsoft KB Archive
Revision as of 15:02, 18 July 2020 by 3155ffGd (talk | contribs) (importing KB archive)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)

Publisher Err Msg: SHARE.EXE Is Not Running on Your Machine...

Publisher Err Msg: SHARE.EXE Is Not Running on Your Machine...


The information in this article applies to:

 - Microsoft Publisher for Windows, versions 2.0, 2.0a
 - Microsoft Windows operating system version 3.1


You must have SHARE.EXE running in memory to run Publisher 2.0 in
Windows 3.1. If SHARE.EXE is not running, you will receive the
following error message during the load process for Publisher 2.0:

   SHARE.EXE is not running on your machine. Publisher
   requires that SHARE.EXE be added to your AUTOEXEC.BAT or
   CONFIG.SYS. If you just ran Setup, you need to restart your
   machine for the changes to take effect. Otherwise, try
   running the Setup program again or refer to the Publisher Read
   Me file. Press F1 for more information on running the Setup

NOTE: You must run the correct version of SHARE.EXE, which is dependent on
what version of MS-DOS your are using. For example, if you are running MS-
DOS 5.0, you should run MS-DOS 5.0 SHARE.EXE.

NOTE: This error can also be caused by launching Windows from DOSSHELL. If
you launched Windows while DOSSHELL was running, Windows may not function
properly. Launching Windows from any menu system is unsupported. If you
want to run Windows, exit DOSSHELL first, and then launch Windows.


You can run SHARE.EXE automatically when you start your machine by
loading SHARE.EXE in either the AUTOEXEC.BAT or CONFIG.SYS file.

SHARE.EXE is usually located in the DOS directory and can be loaded
through the AUTOEXEC.BAT file when you start your machine if you add
the following to your AUTOEXEC.BAT file:

   C:\DOS\SHARE.EXE /L:100

Or, SHARE.EXE can be loaded if you add the following to your

   Install=C:\DOS\SHARE.EXE /L:100

Using Publisher with Windows for Workgroups

If you are running Microsoft Windows for Workgroups version 3.1 in enhanced
mode, you will not have this problem because Windows for Workgroups
automatically loads a virtual sharing device called VSHARE.386 in enhanced
mode. However, if you are running Windows for Workgroups in standard mode,
SHARE.EXE must be loaded before entering Windows for Workgroups.
For more information about VSHARE.386, query on the following words in
the Microsoft Knowledge Base:

   windows and workgroups and VSHARE.386 and file and sharing

Additional query words: 2.00 mspub SHARE.EXE share 2.00a