Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!watmath!clyde!rutgers!princeton!allegra!ulysses!ucbvax!CITHEX.CALTECH.EDU!carl
From: carl@CITHEX.CALTECH.EDU.UUCP
Newsgroups: mod.computers.vax
Subject: SYS$SHARE:SMBSRVSHR.EXE problems, pass 2
Message-ID: <870202005559.02d@CitHex.Caltech.Edu>
Date: Mon, 2-Feb-87 03:55:58 EST
Article-I.D.: CitHex.870202005559.02d
Posted: Mon Feb  2 03:55:58 1987
Date-Received: Wed, 4-Feb-87 01:37:18 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 17
Approved: info-vax@sri-kl.arpa

A while ago, there was a note in this teleconference pointing out that the file
SMBSRVSHR.EXE ends up in SYS$SYSTEM: instead of SYS$SHARE: in the VMS 4.5 (or
was it 4.4?) installation.  I think I've found a good reason:  I just tried to
link a symbiont with the image in question sitting in SYS$SHARE:.  I got the
error message:

%LINK-I-DATMISMCH, createion of 3-SEP-1986 06:09 in shareable image -
	SYS$SYSROOT:[SYSLIB]SMBSRVSHR.EXE;2
	differs from date of 22-MAR-1986 17:54 in shareable image library -
	SYS$SYSROOT:[SYSLIB]IMAGELIB.OLB;1

from the linker.  Using the old version of SMBSRVSHR.EXE, which I fortunately
had not deleted yet, yields no such complaint.  Since we haven't yet installed
the device to be served by the symbiont, I haven't yet gotten around to trying

either of the images produced, but I will report on the results when I do so.
Meanwhile, any comments?