[Info-vax] Product Install

[Steven Schweda]

> [...] I found a tcpip file in kit.dir;1. [...]

   As I wrote earlier:

> I see that it has a PCSI kit:
>       [TCPIP_VAX051.KIT]DEC-VAXVMS-TCPIP-V0501-15-1.PCSI

   All valid directories are ".DIR;1" (except for case
variations on ODS5 file systems on non-VAX systems), so one
would normally refer to a "[.KIT]" subdirectory rather than
the "KIT.DIR;1" file which holds that subdirectory.

> product install /log dec-vaxvms-tcpip-v0501-15-1
> %PCSI-E-S_INVNAM, invalid product name

   As I wrote earlier:
   
> And [TCPIP_VAX051.DOCUMENTATION]TCPIP_IGUIDE.TXT offers the
> usual "Installation and Configuration" guide (featuring a
> "PRODUCT INSTALL TCPIP" command).

   While old/obsolete, you're dealing here with a commercial
product, not some pile of freeware.  It comes with
documentation, like, for example, product installation
instructions.  If you read and follow them, and _then_ you
have problems, then you might productively report them.

>     Ok. Is product used or vmsinstal used.

   What did we say earlier about the use of that special
character: "?"?  (You're apparently careless with your
apostrophes, too.)

   What does it say in the "Installation and Configuration"
guide?

> Traversing directories can be hard. 

      HELP SET DEFAULT

   Actually, although it may he harder than with UNIX, it's
usually pretty easy, once you learn the basics.  Lacking an
example of what you wish to do and what you tried which
failed, specific advice would require psychic powers stronger
than mine.  (On the bright side, explicit device names have
some benefits, like not hiding some useful details about the
storage structure.  Such benefits can also be seen as
annoyances, depending on circumstances.)


> [...] in my ISO (9660).

   ISO 9660 is the standard.  What you have is a disk image. 
Whether it's a disk image with an ISO 9660 file system can be
determinied by trying to read it on a non-VMS system.  (I
predict limited success, at best.)