[Info-vax] openvms licensing

[Bill Cunningham]

"Steven Schweda" <sms.antinode at gmail.com> wrote in message 
news:44adf8c0-9194-4868-92e3-7a50720e6312 at googlegroups.com...
>> [...] I've tried numerous techniques [...]  There's nothing
>> but problems.
>
>   That tells me exactly nothing about what you've done or
> what happened when you did it.  As usual, showing actual
> commands with their actual output can be more helpful than
> vague descriptions or interpretations.
>
>>     Anyway I guess I'm going to make a last call [...]
>
>   It's been a long time since I've had to start a system
> from scratch, but, as I recall, the usual procedure is to
> register the basic VMS PAK(s) and enough networking stuff
> (DECnet (DVNET*) or TCPIP (UCX)) to enable transfer of the
> full hobbyist PAK DCL script.

Ok I should load what PAKs by vmslicense.com at minimum. People have told me 
to copy the license with two X windows. I've tried that. I am using linux.

 With my weak psychic powers, I
> can't guess what you've done, but, if you haven't tried it
> yet, you might consider:
>
>      @ sys$update:vmslicense.com

    Yeah as to now I haven't been very helpful. I'm not quite sure what to 
say. But vmslicense.com I have tried oh yes. Thre's always a checksum error. 
And you are right as you say below, It's pretty confusing the difference in 
the authorization program and the things the PAKs actually call for.

> and answer the questions based on the data in the hobbyist
> PAK DCL script.  Some of the terminology differs between the
> LICENSE command and VMSLICENSE.COM, so some confusion is
> possible, but if you provide any useful info, then you might
> be able to get some help with it (or with the LICENSE
> command, for that matter).
>
>   When reporting these things, feel free to obscure the
> checksums, but not anything else for no good reason.