I read that too late. I've done the cut/paste thing in to putty to save the file then @it.
It might work... hopefully.
On Wed, Jun 5, 2013 at 12:47 AM, Brian Schenkenberger, VAXman- <system at tmesis.com> wrote:
Tony Blews <tonyblews at gmail.com> writes:
>John Egolf just sent me the PAK stuff. Now I have the problem of getting it
>on to the bloody machine. Without access to any networks (until they're
>licensed), i'm going through the arse-pain of copy/paste from one terminal
>window to another. Oh god its tedious.
Just load the VMS PAKs, TCPIP and DECnet PAKs. Reboot and then you should
be able to get the rest of the PAK file (I'm assuming it's a Stream-LF text
file just like the DSPP PAKs) copied over. You may need to set file's at-
tributes to be just Stream in order to execute the file as a procedure (ie.
@file).
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
Tony Blews <tonyblews at gmail.com> writes:
John Egolf just sent me the PAK stuff. Now I have the problem of getting it
on to the bloody machine. Without access to any networks (until they're
licensed), i'm going through the arse-pain of copy/paste from one terminal
window to another. Oh god its tedious.
Just load the VMS PAKs, TCPIP and DECnet PAKs. Reboot and then you should
be able to get the rest of the PAK file (I'm assuming it's a Stream-LF text
file just like the DSPP PAKs) copied over. You may need to set file's at-
tributes to be just Stream in order to execute the file as a procedure (ie.
@file).
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
John Egolf just sent me the PAK stuff. Now I have the problem of getting it on to the bloody machine. Without access to any networks (until they're licensed), i'm going through the arse-pain of copy/paste from one terminal window to another. Oh god its tedious.
On Wed, Jun 5, 2013 at 12:38 AM, Brian Schenkenberger, VAXman- <system at tmesis.com> wrote:
Gregg Levine <gregg.drwho8 at gmail.com> writes:
>On Tue, Jun 4, 2013 at 7:16 PM, Brian Schenkenberger, VAXman-
><system at tmesis.com> wrote:
>> Dave McGuire <mcguire at neurotica.com> writes:
>>
>>>
>>> You changed the IP address of the host machine running simh, and that
>>>buggered your VMS licenses?
>>>
>>> I find that very difficult to wrap my brain around. VERY difficult.
>>
>> Especially, since SYS$GRANT_LICENSE doesn't know diddly about TCP/IP or
>> DECnet.
>>
>> --
>> VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
>>
>> Well I speak to machines with the voice of humanity.
>
>Hello!
>Remember gang stranger things have happened. Incidentally Dave despite
>the fact that your still surrounded by yetis, they had nothing to do
>with the problem.
If the PAK, the correct PAK, is loaded into the LMF database, then VMS will
create a a kernel mode logical of the name LNM$<PRODUCER>_<PRODUCT> in the
table LMF$LICENSE_TABLE. The SYS$GRANT_LICENSE system service looks for the
kernel mode logical and translates its encoded equivalence string to valid-
ate the license. Unless there is some TCP/IP or DECnet information encoded
in the PAK -- it would have to be in the TOKEN or HARDWARE_ID components of
said PAK -- there is nothing that ties a PAK to any network addressing. In
fact, it would be stupid to do so. DEC/Compaq/H PAK requirements have been
very minimalistic too. Basically, if a PAK called LMF$<PRODUCER>_<PRODUCT>
exists, you are licensed to use said <product>.
Even *IF* a PAK had TOKEN or HARDWARE_ID components, it is up to the code
that invokes SYS$GRANT_LICENSE to enforce that which it has extracted from
the TOKEN or HARDWARE_ID components
Sorry but this is NOT the forum to discuss the weaknesses of the VMS LMF. ;)
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
Gregg Levine <gregg.drwho8 at gmail.com> writes:
On Tue, Jun 4, 2013 at 7:16 PM, Brian Schenkenberger, VAXman-
<system at tmesis.com> wrote:
Dave McGuire <mcguire at neurotica.com> writes:
You changed the IP address of the host machine running simh, and that
buggered your VMS licenses?
I find that very difficult to wrap my brain around. VERY difficult.
Especially, since SYS$GRANT_LICENSE doesn't know diddly about TCP/IP or
DECnet.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
Hello!
Remember gang stranger things have happened. Incidentally Dave despite
the fact that your still surrounded by yetis, they had nothing to do
with the problem.
If the PAK, the correct PAK, is loaded into the LMF database, then VMS will
create a a kernel mode logical of the name LNM$<PRODUCER>_<PRODUCT> in the
table LMF$LICENSE_TABLE. The SYS$GRANT_LICENSE system service looks for the
kernel mode logical and translates its encoded equivalence string to valid-
ate the license. Unless there is some TCP/IP or DECnet information encoded
in the PAK -- it would have to be in the TOKEN or HARDWARE_ID components of
said PAK -- there is nothing that ties a PAK to any network addressing. In
fact, it would be stupid to do so. DEC/Compaq/H PAK requirements have been
very minimalistic too. Basically, if a PAK called LMF$<PRODUCER>_<PRODUCT>
exists, you are licensed to use said <product>.
Even *IF* a PAK had TOKEN or HARDWARE_ID components, it is up to the code
that invokes SYS$GRANT_LICENSE to enforce that which it has extracted from
the TOKEN or HARDWARE_ID components
Sorry but this is NOT the forum to discuss the weaknesses of the VMS LMF. ;)
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
Gregg,
Yeti are under the control of The Great Intelligence.
But you knew that...
On Wed, Jun 5, 2013 at 12:24 AM, Gregg Levine <gregg.drwho8 at gmail.com> wrote:
On Tue, Jun 4, 2013 at 7:16 PM, Brian Schenkenberger, VAXman-
<system at tmesis.com> wrote:
> Dave McGuire <mcguire at neurotica.com> writes:
>
>>
>> You changed the IP address of the host machine running simh, and that
>>buggered your VMS licenses?
>>
>> I find that very difficult to wrap my brain around. VERY difficult.
>
> Especially, since SYS$GRANT_LICENSE doesn't know diddly about TCP/IP or
> DECnet.
>
> --
> VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
>
> Well I speak to machines with the voice of humanity.
Hello!
Remember gang stranger things have happened. Incidentally Dave despite
the fact that your still surrounded by yetis, they had nothing to do
with the problem.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
Due to my arsing about, the virtual machine seems to think that its a totally different hardware set up, and therefore needs a license. I don't know how I managed that.
On Wed, Jun 5, 2013 at 12:16 AM, Brian Schenkenberger, VAXman- <system at tmesis.com> wrote:
Dave McGuire <mcguire at neurotica.com> writes:
>
> You changed the IP address of the host machine running simh, and that
>buggered your VMS licenses?
>
> I find that very difficult to wrap my brain around. VERY difficult.
Especially, since SYS$GRANT_LICENSE doesn't know diddly about TCP/IP or
DECnet.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
On Tue, Jun 4, 2013 at 7:16 PM, Brian Schenkenberger, VAXman-
<system at tmesis.com> wrote:
Dave McGuire <mcguire at neurotica.com> writes:
You changed the IP address of the host machine running simh, and that
buggered your VMS licenses?
I find that very difficult to wrap my brain around. VERY difficult.
Especially, since SYS$GRANT_LICENSE doesn't know diddly about TCP/IP or
DECnet.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
Hello!
Remember gang stranger things have happened. Incidentally Dave despite
the fact that your still surrounded by yetis, they had nothing to do
with the problem.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
Dave McGuire <mcguire at neurotica.com> writes:
You changed the IP address of the host machine running simh, and that
buggered your VMS licenses?
I find that very difficult to wrap my brain around. VERY difficult.
Especially, since SYS$GRANT_LICENSE doesn't know diddly about TCP/IP or
DECnet.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
Tony Blews <tonyblews at gmail.com> writes:
Thanks! I had the name John Golf stuck in my head for some reason.
John Egolf. Nice fellow.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
Dave McGuire <mcguire at neurotica.com> writes:
On 06/04/2013 06:01 PM, Tony Blews wrote:
I've had my machine (TARDIS) offline for a while due to moving house, being
hospitalised and then going on holiday.
So, now I've come to restart the thing, it seems my licenses have expired,
which shouldn't have happened until September. Could this be down to moving
the simh instance to a new machine and giving it a new ip address?
That should have no effect on the licensing. The OS running under the
emulator has no access to that information; it thinks it's a real VAX.
Anyway, where do i get the licenses from again? All the addresses I had
either don't work, or give me completely unrelated websites.
If it is/was a Hobbyist license PAK, it must be renewed yearly.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
