NOVELL TECHNICAL INFORMATION DOCUMENT

TITLE:              Volume Name Corruption and VAP GPI Fix
DOCUMENT ID:        TID000425
DOCUMENT REVISION:  A
DATE:               01JUL93
ALERT STATUS:       Yellow
INFORMATION TYPE:   Symptom Solution
README FOR:         VAPVOL.EXE

NOVELL PRODUCT and VERSION:
NetWare Pre 3.11 and 2.2

ABSTRACT:
This patch corrects a problem appearing in servers when VAPs are loaded. 
Some symptoms of the problem have been General Protection Interrupts, or
Stack Overflow errors while a VAP is loading, or corruption in volume names
on multi-volume systems.
_________________________________________________________________

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

Self-Extracting File Name:  VAPVOL.EXE

Files Included     Size     Date        Time

  VAPVOL.TXT          (This File)
   SFT_2.FIX        423    5-18-90      3:14p
   TTS_2.FIX        423    5-14-90      1:01p
     TTS.FIX        421    5-14-90      1:01p
     SFT.FIX        421    5-14-90      1:02p
     ADV.FIX        426    5-14-90     12:52a
   ADV_2.FIX        428    5-14-90     12:53a
  ZAPOBJ.EXE      23586    7-11-90     12:15a


This README file accompanies .FIX files for Advanced and SFT NetWare
v2.15c.

This patch corrects a problem appearing in servers when VAPs are loaded. 
Symptoms of this problem have been General Protection Interrupts or Stack
Overflow Errors while a VAP is loading, or corruption in volume names on
multi-volume systems.


ZAPOBJ.EXE is run against a .OBJ file using a .FIX parameter file. 
Parameter files containing temporary fixes (ie. *.FIX) are supplied for
both 3.5" and 5.25" media.  The first 8 characters of the .FIX files are
named the same as the .OBJ files which are to be patched.  ZAPOBJ syntax
is:

        ZAPOBJ <input>.OBJ <output>.OBJ <input>.FIX

This should be run for each .OBJ which needs to be patched.  ZAPOBJ.EXE
must be run in the same directory as the .OBJ.  The <output>.OBJ file has a
different name than the <input>.OBJ file, but it should be renamed to
<input>.OBJ after the patch process.

For example, in order to patch Advanced NetWare 3.5" media,

1) Copy ZAPOBJ.EXE and ADV.FIX to the ADOBJ diskette or subdirectory.

2) Execute the following statement:  ZAPOBJ ADV.OBJ NEWADV.OBJ ADV.FIX

3) Rename ADV.OBJ to ADV.BAK and rename NEWADV.OBJ to ADV.OBJ

4) Run NETGEN and ensure that the "Link/Configure NetWare Operating System"
option is selected and that NET$OS.EXE is copied to your network.

This patch need only be run against the one .OBJ file corresponding to the
network operating system you are generating (i.e. Advanced, SFT, or TTS -
SFT with TTS).

The following is a list of .FIX files, their associated .OBJ files to be
patched, the diskettes or subdirectories where the .OBJ file is located,
and the applicable media size.

   ADV.FIX          ADV.OBJ           ADOBJ     (for 3.5" media)
   SFT.FIX          SFT.OBJ           SFTOBJ    (for 3.5" media)
   TTS.FIX          TTS.OBJ           TTSOBJ    (for 3.5" media)
   ADV_2.FIX        ADV_2.OBJ         OSOBJ     (for 5.25" media)
   SFT_2.FIX        SFT_2.OBJ         OSOBJ     (for 5.25" media)
   TTS_2.FIX        TTS_2.OBJ         OSOBJ     (for 5.25" media)
ÿ