v7.3-2 Upgrade Problem

[Rick Dyson]

I tried to upgrade a stand-alone box from v7.3-1 to v7.3-2. It currently has some problem with the DECWindows that HP has no idea how to fix except to upgrade and see if that fixes it.

The upgrade started and stopped at:

[SYSLIB]sys$starlet_c.tlb not installed or is present but out of scope: module update skipped.

It then recommened terminating, which I did. It had already removed all the Product recovery patches.

I am still able to boot the old system disk and I have access to the Sys$Library:Sys$Starlet_C.tlb file.

I can't find any reference to this kind of error on this ITRC (DSN is dead now, right?)

On a previous upgrade from 7.2 -> v7.3-1 a couple years back, I had a similar sounding problem that required HP to analyze my TLB and give me a list of modules to delete from the library BEFORE upgrading. I believe they blamed it on bugs in PCSI...

Has anyone else seen this problem or something like it?

I have attached a full directory listing of the TLB file and a library listing of my Starlet_C text library for reference.

rick

[Willem Grooters]

I know there is an issue with this upgrade, but that had to do with another patch, yhis has been coverd in this forum. I guess you should at leat install ALL the PCSI patches. It might be you'll need to do all DECWindows patches as well (and probably some more, the C compiler might be another one)

If you have a spare disk you can use to create a backup system disk on (before upgrading) you could try the continue. If the system is not used for developing programs (in C or C++) this libary is likely to be non-critical and could be missed - unless some product would require it duirng install (it would require a C/C++ compiler as well, plus it;s PAK)

[Veli Körkkö · Accepted solution]

I found the following:

...
The problem (for both upgrade paths) is triggered by the installation of the
VMS731_PTHREAD V4.0 remedial kit. It is possible that a version of the
VMS731_UPGRADE kit (that includes this PTHREAD kit) could trigger the problem.

The good news is that [SYSLIB]SYS$STARLET_C.TLB is upgraded correctly when
upgrading to V7.3-2 if the user answers NO to the "Do you want to terminate?
[YES]" question. The step being "skipped" is not necessary to perform since
the whole library file will be replaced anyway. The error message, in this
case, simply should not have been displayed.

...
For customers who upgrade from V7.3-1 to V7.3-2 and have VMS731_PTHREAD V4.0
installed, the workaround is to answer NO to the terminate question. Anyone
who really wants to verify that [SYSLIB]SYS$STARLET_C.TLB is ok can compare
the file from the bootable CD with the one on the target (upgraded) system
disk.

----

That being it apparently, you could check

$ product show history vms731*

whether VMS731_PTHREAD or VMS731_UPDATE has been been applied to system. And anyway, just continue the upgrade.

_veli

[Rick Dyson]

EXCELLENT! Both of you!

I always keep things patched. :) So I guess I brought this on myself!

PRODUCT KIT TYPE OPERATION DATE AND TIME
----------------------------------- ----------- ----------- --------------------
DEC AXPVMS VMS731_PTHREAD V4.0 Patch Install 26-JUL-2004 22:18:39
DEC AXPVMS VMS731_PTHREAD V3.0 Patch Install 05-JUN-2004 15:18:10
DEC AXPVMS VMS731_PTHREAD V2.0 Patch Install 10-SEP-2003 09:54:46

I will try again (I don't have a spare disk on this box big enough to make an image copy of the system disk (I tried!) but I did make a backup tape first. :)

I will try again and Just Say NO.

rick

[Rick Dyson]

p.s. Veli, Where did you find that? Being able to find those kind of things would be great, if I could!

This kind of stuff used to be in the DSN system, but that has gone away. I tried searching all of ITRC, but could never find a match to anything I tried.

rick

[Volker Halle]

Rick,

the same thing happened to me during installation of the E8.2 fieldtest upgrade (from a V7.3-1 system with VMS731_PTRHEAD-V0400 installed). Raised as PTR 75-107-39 and included in the V8.2 Release Notes chapter 1.9.3 Error on Upgrade from Version V7.3-1

Volker.

[Rick Dyson]

I have found that indeed, the suggestion to carry on through the warning worked just fine. I have finished and gotten the intial reboots finished.

Of course, the driving force was to fix a DECWindows problem and I am still stuck at an all white screen with a "X11" mouse and nothing else. :( I will have to run through all the patches now and see if one of them fixes it.

Thanks to all of you who helped!

rick