[Info-vax] VMS83A_UPDATE V11

[Simon Clubley]

On 2009-12-14, Peter 'EPLAN' LANGSTOeGER <peter at langstoeger.at> wrote:
>
> Sorry for follow-up my own posting, but I have a new situation:
>
> Installing UPDATE V11 (filedate 4-DEC-2009) on one of my Alphas gave me:
>
> %PCSI-W-NOTFNDKIT, imglib module PTHREAD$DBGSHR from product DEC AXPVMS VMS83A_U
> PDATE V11.0 was in previous kit but is not in current kit
> %PCSI-W-NOTFNDKIT, imglib module PTHREAD$RTL from product DEC AXPVMS VMS83A_UPDA
> TE V11.0 was in previous kit but is not in current kit
> %PCSI-W-NOTFNDKIT, imglib module SDA$SHARE from product DEC AXPVMS VMS83A_UPDATE
>  V11.0 was in previous kit but is not in current kit
> %PCSI-W-NOTFNDKIT, imglib module SYS$PEDRIVER from product DEC AXPVMS VMS83A_UPD
> ATE V11.0 was in previous kit but is not in current kit
> %PCSI-W-NOTFNDKIT, imglib module SYS$PEDRIVER_MON from product DEC AXPVMS VMS83A
> _UPDATE V11.0 was in previous kit but is not in current kit
>
> %PCSI-W-KITNOTSAME, kit for product DEC AXPVMS VMS83A_UPDATE V11.0 differs from
> same version of product previously installed
> -PCSI-W-OPERMAYDEL, objects (identified above) previously installed may be delet
> ed and not replaced
> Do you want to continue? [YES]
>

So they have "fixed" the problem by removing the modules from the new patch
kit ?

How exactly is that a fix ? :-(

(The modules were presumably in the patch kit in the first place because
they fixed other unrelated problems).

The image I have is of clueless people pushing buttons until the messages
disappear. It seems to be of little concern to these people if the end
result of all the button pushing is a patch kit which doesn't actually
fix the problems it's intended to fix.

Simon.

-- 
Simon Clubley, clubley at remove_me.eisner.decus.org-Earth.UFP
Microsoft: Bringing you 1980's technology to a 21st century world