Publisher: Files May Become Corrupted When Saved to Network
PSS ID Number: Q106148
Article last modified on 11-12-1993
PSS database name: W_MSPub

2.00

WINDOWS


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

 - Microsoft Publisher version 2.0
 - Microsoft Windows for Workgroups version 3.1
-------------------------------------------------------------------

SYMPTOMS
========

Publisher files may become corrupted when you save them to a network
drive. When opening or working with the file, you may receive one of
the following error messages:

   Application Error
   VSERVER.386 caused a General Protection Fault in module
   STORAGE.DLL at xxxx:xxxx.

where xxxx:xxxx is the address of the memory conflict, or

   Application Error
   MSPUB.EXE caused a General Protection Fault in module
   STORAGE.DLL at xxxx:xxxx

where xxxx:xxxx is the address of the memory conflict.

The error involving VSERVER.386 is most likely to occur if you are
using Windows for Workgroups version 3.1, and is caused by a problem 
in the VSERVER.386 file included with this version of Windows.

The error involving STORAGE.DLL is most likely to occur if you are 
using MS-DOS version 4.01, and is caused by this older version of
STORAGE.DLL.

RESOLUTION
==========

To correct these problems, do one of the following:

 - Upgrade to Windows for Workgroups version 3.11.

   The version of VSERVER.386 that ships with this release 
   corrects the problem with VSERVER.386.

   -or-

 - Use a different version of MS-DOS (other than version 4.01).

   The versions of STORAGE.DLL that ship with other versions 
   of MS-DOS (other than version 4.01) correct the problem 
   with STORAGE.DLL.

To obtain the Windows for Workgroups 3.11 upgrade, contact the 
Microsoft Sales Information Center at (800) 426-9400.

Additional reference words: 2.00 mspub pub20 win31 gpf corruption

Copyright Microsoft Corporation 1993.