VMS 8.2 VMSINSTAL Bug with RUN_IMAGE Persists?

[Richard J Maher]

Hi,

There was/is a bug with VMSINSTAL's Run_Image callback on 8.2 machines that exhibited the following symptoms at product installation time: -

* Do you want to purge files replaced by this installation [YES]?
%ANALYZE-E-OPENIN, error opening MISSING:[MISSING]VMI$NEW.EXE; as input
-SYSTEM-W-NOSUCHDEV, no such device available
%VMSINSTAL-E-INSFAIL, The installation of TIER3A V3.1 has failed.

The problem is that I've just had someone upgrading to 8.2 (Why not 8.3? I dunno :-) and the bug appears to still be there :-(

VMS 8.2 is still supported, is it not? Has anyone got a patch reference:

Below is from one of COVs kind souls many moons ago stating that this bug is *supposed* to have been fixed.

Any ideas?

Cheers Richard Maher

> 2. VMSINSTAL
>
> This failed miserably on VMS V8.2 on running T3$CHKACC, because there
> is a known bug in VMSINSTAL on V8.2 with the RUN_IMAGE vmi$callback.
>
> It craps out with:
>
> %ANALYZE-E-OPENIN, error opening MISSING:[MISSING]VMI$NEW.EXE; as input
> -SYSTEM-W-NOSUCHDEV, no such device available
> %VMSINSTAL-E-INSFAIL, The installation of TIER3A V3.1 has failed.
>
>
> This issue is allegedly fixed in VMS82A_KITTING-V0100, dated
> 10-JAN-2006, but that contains a copy of VMSINSTAL.COM from
> 10-AUG-2005, so doesn't solve the problem.
>
> Needless to say, I'm going to report that problem. I got Tier3
> installed by knobbling its KITINSTAL.COM thus:
>
> $! VMI$CALLBACK RUN_IMAGE "VMI$KWD:T3$CHKACC.EXE"
> $ tier3$missing = "true"

[Sebastian Bazley]

I know this won't help, but why is the product still using VMSINSTAL?

PCSI kits are the standard these days, and are not particularly difficult to create.

[I'd better duck now ...]