[Info-vax] Problem upgrading to 8.4 on Itanium (from 8.3-1H1)

VAXman- at SendSpamHere.ORG VAXman- at SendSpamHere.ORG
Tue Aug 30 14:23:12 EDT 2011


In article <ed81e980-25a2-48d9-99de-de5e53997c20 at s8g2000vbx.googlegroups.com>, Dave <BaxterD at tessco.com> writes:
>On Aug 29, 1:34=A0pm, JF Mezei <jfmezei.spam... at vaxination.ca> wrote:
>> >>> >%PCSI-E-WRITEERR, error writing DISK$SYSI64_V84:[VMS$COMMON.]
>> >>> >[SYSHLP]HELPLIB.HLB;2
>> >>> >-LBR-E-DUPKEY, duplicate key in index
>>
>> So this is the result of using LIB/INSERT instead of LIB/REPLACE in the
>> PCSI script ?
>> (or perhaps not doing a SET NOON and then LIB/DELETE to ensure there is
>> no module by that name and then LIB/INSERT ?
>>
>> If they don't name the offending key/module, then this error message is
>> worthless.
>>
>> Consider a site that created its own help module called "chocolate".
>> With a new release of VMS, the engineers added the "chocolate" command
>> which is totally dfferent than what the site is doing.
>>
>> Should the insallation procedure simply replace "chocolate" without
>> warning ? Should it warn the user and perhaps save the old one ? =A0Or
>> perhaps just say that "chocolate" already exists and the whole VMS
>> installation is terminated. (at least the customer would then know what
>> key is duplicate and could fix it before proceeding with the install agai=
>n).
>
>To Brian,
>        Its OK, it took your response in the manner that you intended.

:D



>To JF,
>        I agree with your comments.   My real objections are
>
>         1.    a meaning less message warning me to terminate (or
>suffer the
>         implied, but unspecified, consequences).
>         2.    To subsequently find out that, not only is the issue
>(pretty much)
>         harmless, but also self-repairing, (at least in the example
>presented)
>         3.    They already knew about it, but didn't feel that it was
>worth
>         publicizing.   (I have mail folders full of other HP
>"Customer Advisories"
>         relating to the windows crap)
>
>        An indication of which module is the issue, would have
>helped.
>
>Anyway,  enough of this!!   (I guess I should be grateful that it only
>took about 90
>minutes to get a response from HP customer support.
>
>Dave.

Now comes the fun part of figuring out which patches you'll need to apply
and which patches you want to avaid at all costs.

-- 
VAXman- A Bored Certified VMS Kernel Mode Hacker    VAXman(at)TMESIS(dot)ORG

All your spirit rack abuses, come to haunt you back by day.
All your Byzantine excuses, given time, given you away.



More information about the Info-vax mailing list