[Info-vax] Product Install

Bill Cunningham nospam at nspam.invalid
Sat Feb 27 19:41:59 EST 2016


"Steven Schweda" <sms.antinode at gmail.com> wrote in message 
news:e12505f4-1b96-4d96-a182-a848ed4d066c at googlegroups.com...
>> [...] 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).

    I have found those. In a dir called DOCUMENTATION.DIR;1 and it looks 
like text and post script files. And that's what I'm reading too. Another 
thing I'm not seeing anywhere. Can you pause the display? Like with *nixs 
|more or |less ? Or MSDOS's dir/p switch? I have to be able to read 
directories and guides.
dir [*...] and dir [...] shows a fast scrolling list of directories.


>   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.)

    ? IDK. I hit keys and they don't always print. Cheap keyboard. And I 
sometimes get excited and post before some proofreading.

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

    Now is that the user's manual? I have the user's manual and system 
manager's guide. I have a pdf I don't touch concerning decnet. IDK why I 
downloaded it. There is a DCL dictionary I guess too. That might come in 
handy.

>> 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.

    Traversing the directories I am focusing on. When learned probably quite 
easy. A wall for the beginner.

I will read the texts files like guide I copied from the ISO to the VMS 
created from backup. Installation on the Kits I will read about in the docs. 
If I can figure out how to keep them from scrolling by like a train. I'm not 
quite sure where to search for that.

 (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.)

    Already tried. No luck at all. 





More information about the Info-vax mailing list