Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Posting-Version: version B 2.10.3 4.3bsd-beta 6/6/85; site ucbvax.BERKELEY.EDU
Path: utzoo!watmath!clyde!burl!ulysses!ucbvax!info-vax
From: barach@BBNCC3.ARPA (Dave Barach)
Newsgroups: mod.computers.vax
Subject: Image Activator problem
Message-ID: <8603030858.AA10647@ucbvax.berkeley.edu>
Date: Sun, 2-Mar-86 10:55:40 EST
Article-I.D.: ucbvax.8603030858.AA10647
Posted: Sun Mar  2 10:55:40 1986
Date-Received: Tue, 4-Mar-86 02:28:04 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 20
Approved: info-vax@sri-kl.arpa

Re:  Problems installing sharable libraries

I've had similar problems with a shared library.  I've traced the problem to
copying a new version of the sharable .EXE file on top of the old one WITHOUT
FIRST running INSTALL to delete the known file entry (etc.).   

The problem manifests itself in the following (bizarre) way:  The image
activator appears not to correctly fix-up the transfer vectors for SOME OTHER
library.  It took me a long time to figure this out; I still don't really
understand what could be going on.  

You can tell for sure if you've done yourself in this way by inspecting the
global section reference-count with INSTALL.  If the count is absurd (usually
65535 -- (unsigned minus-one!)), you've definitely been bitten.

The above holds for MicroVMS; I expect it also obtains for regular VMS, too.

Someone please help us out and try to explain what's going on...

Dave