Post by Simon Clubley Post by Rod Regier Post by Craig A. Berry
That could probably be remedied by disassembling the PCSI kit, modifying
the dependencies, and reassembling it. Sounds like work to me. Why not
just get the OS from VSI? It's the only game in town at this point anyway.
Can an end-user do those PCSI manipulations, or only the kit author? VSI is the kit author.
I can't think of any reason why you couldn't. As far as I know, if you
can run the PRODUCT command on a kit to install it, you could also run
it on that same kit to extract everything in it. Then you'd have to
fiddle with the dependencies in the description file and pack it all up
into your own PCSI kit to install it. Or manually move all the pieces
into place on your system and then manually run any post-installation
steps (there would probably be things with Samba like creating service
For all the gory details, search for "POLYCENTER Software Installation
Utility Developer's Guide."
Post by Simon Clubley
Is the PCSI kit signed ?
The one from VSI almost certainly would be, and the HP binary checker
would likely not recognize that signature, so you'd have to ignore the
warning about that to unpack the kit. At least I think that's what would
happen (I've never actually tried to unpack a VSI-built kit on HPE VMS).
Once unpacked, you've got the same files everyone else gets -- as long
as they didn't build it with the C99 kit installed you should be all set