[Info-vax] GKS : gopwk problem with VSI's version of GKS

[Stephen Hoffman]

On 2021-03-18 07:12:48 +0000, Joukj said:

> I got it solved: I realy had to reboot (I thought OpenVMS was not 
> Windows(#$%^&@)). So simply remove old GKS, install new GKS and rerun 
> @sys$startup:gkstartup is not enough; in that case you will end-up in a 
> "mixed version of old/new.

Good that you got this solved and got GKS working.

OpenVMS installers tend to become problematic once outside the 
feature-set necessary to load vendor-provided layered product kits into 
vendor-assigned places. Even within, sometimes.

This having written more than a few PCSI and VMSINSTAL installers.

I have horror stories around trying to make this stuff work across 
different and diverging configurations too, without shifting the whole 
mess off onto the doc writers and support folks, and onto the end user 
folks to manually edit files. As is common.

Apps on OpenVMS have a nasty habit of using logical names for 
configuration data, and cleaning up the old stuff arguably either 
requires a reboot, or more cross-version tracking than most kit 
developers want or can even deal with.

App removal and cleanup—whether for product removal or as part of an 
upgrade—is more of a morass. PCSI really does try, too.

App removal back to the lack of any real design for app installation 
and app storage, too. The OpenVMS just-stick-it-everywhere model is 
reminiscent of the classic old-school Microsoft Windows app model.




-- 
Pure Personal Opinion | HoffmanLabs LLC