Subject: | |
From: | |
Reply To: | |
Date: | Wed, 8 Mar 1995 09:03:49 PDT |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
Craig Vespe said:
> How about using the HPCIGETVAR Intrinsic using HPVERSION for the
> CI variable, then parse the results. Keep in mind for "5.0" you
> can get back X.50.20, X.50.50, C.50.00...
As has been pointed out before, the HPVERSION value reflects a user-alterable
sysgen parameter, and thus cannot be trusted. We have one customer who stores
the date they installed the OS in this field! It can get rather ugly if you try
to use HPVERSION to determine OS version right before diving into some low level
privileged data structure :-)
The new variables that HP is adding to the 5.0 express release will take care
of this problem.
Jeff wrote:
> :showvar hp@version
> HPOSVERSION = B.79.06 (can't be changed)
> HPRELVERSION = B.79.05 (can't be changed)
> HPVERSION = B.79.05 <== this can be changed in sysgen.
Whoa! Jeff, what's this B.79.05 stuff? Shouldn't HPRELVERSION show "C.50.xx"?
We assume that we can take the middle two digits if the release version and
divide by 10 to get what everybody thinks of as the MPE version. I don't want
to have to add another whole set of mappings like 7.9==5.0, etc.
G.
|
|
|