On 2013-06-15 15:28, Bob Armstrong wrote:
if a request comes in without any account information, VMS applies
the default account as the user under which to run the request.
Ah - and 11M+ can't do this? Didn't know that... Thanks.
Right. No RSX have any default account for DECnet. However, M+ have proxy, which can be made to work pretty close.
Johnny
if a request comes in without any account information, VMS applies
the default account as the user under which to run the request.
Ah - and 11M+ can't do this? Didn't know that... Thanks.
Bob
On 2013-06-15 14:59, Bob Armstrong wrote:
My workaround for that is to use DECnet proxy information.
However, I'm not sure that is available in 11M.
Sadly, there is no proxy support on M - only M+.
I still don't understand how it works when talking to a VMS system,
though? LENTO is doing the same thing in either case, but with a VMS system
on the far end all is well and with an RSX system on the other end it
doesn't work.
In all cases, if account information is passed in the request, it is used. For any OS. If no account information is passed, but both requesting node includes proxy information, and responding nodes make use of proxy information, this is used to get an account under which to process the reqeuest.
With VMS, if a request comes in without any account information, VMS applies the default account as the user under which to run the request. The requesting node have no involvement in this.
Johnny
My workaround for that is to use DECnet proxy information.
However, I'm not sure that is available in 11M.
Sadly, there is no proxy support on M - only M+.
I still don't understand how it works when talking to a VMS system,
though? LENTO is doing the same thing in either case, but with a VMS system
on the far end all is well and with an RSX system on the other end it
doesn't work.
Bob
On 2013-06-13 08:23, Mark Benson wrote:
Due to the limits on our ability to get internet service of any decent
speed, we're having to change packages meaning we will lose out fixed IP
in November. I'd like to work towards being able to stay on HECnet
before then using STAR69 to maintain my connection.
Well, do you know if you'll get different addresses often? Many ISPs give dynamic IP addresses, but you actually stay on the same address for months, which makes it a rather small problem. I haven't had a change in address in over 6 months myself.
Johnny
Hi, Bob.
On 2013-06-13 15:11, Bob Armstrong wrote:
or What I know about DECnet-11 (several things, undoubtedly :-)
I have a DECnet-11 RSX-11M (no + !) system, LENTO. On LENTO I can say
>NFT LEGATO::/LI [LEGATO is a
VMS node]
and I get a directory of the default DECnet account on LEGATO - exactly
what I d expect to happen. But if I say
>NFT MIM::DU:[4,54]/LI [MIM being an RSX node]
I get
NFT -- Error in reading directory MIM::DU:[4,54]
Access control rejected
On VMS this behavior is controlled by the SET EXECUTOR DEFAULT ACCESS
characteristic, but DECnet-11 doesn t seem to have an equivalent.
What s the secret to making this work on RSX?
Right.
The problem is that in RSX you do not have a default access account.
My workaround for that is to use DECnet proxy information. However, I'm not sure that is available in 11M. But that is what you need to look for. I know of no other solution.
Johnny
On Thu, Jun 13, 2013 at 9:07 PM, Mark Pizzolato - Info Comm
<Mark at infocomm.com> wrote:
On Tuesday, June 11, 2013 at 8:42 AM, Mark Pizzolato wrote:
On Tuesday, June 11, 2013 at 8:36 AM, Sampsa Laine write:
This looks cool, anyone try it?
http://www.9track.net/simh/video/
Hi Sampsa,
How timely of you to observe this today.
Just last night I got code pieces from Matt Burke (the guy at 9track.net) to
add VCB01 (QVSS) support to the simh codebase for the MicroVAX I and
MicroVAX II simulators.
I'm in the process of merging that code and adding the necessary build
mechanisms to the makefile as we speak.
This will be cleaned up and visible at https://github.com/simh/simh in at
most a couple of days....
For folks who build their own binaries, the latest github code has a VAXStation I and VAXStation II with the MonoChrome QVSS video capabilities.
sim> SET CPU MODEL=VAXSTATION
enables the video subsystem.
The VAXStation I has a limit of 4MB of RAM, the VAXStation II has a limit of 16MB.
The makefile should just build the right thing if the development support for libSDL is installed on your platform.
Please provide bug reports and/or other feedback with issues created at https://github.com/simh/simh/issues
There is a glitch in my scripts which build and package the windows binaries which is failing to build the simulators with video support, so folks who count on the Windows Binaries will have to wait until I fix this.
Thanks.
- Mark Pizzolato
Hello!
Nice to know Mark. Any suggestions for implementing it on a Raspberry
Pi system w/ 512MB of memory? I did get the code outside of your
screen idea to build properly.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
On Tuesday, June 11, 2013 at 8:42 AM, Mark Pizzolato wrote:
On Tuesday, June 11, 2013 at 8:36 AM, Sampsa Laine write:
This looks cool, anyone try it?
http://www.9track.net/simh/video/
Hi Sampsa,
How timely of you to observe this today.
Just last night I got code pieces from Matt Burke (the guy at 9track.net) to
add VCB01 (QVSS) support to the simh codebase for the MicroVAX I and
MicroVAX II simulators.
I'm in the process of merging that code and adding the necessary build
mechanisms to the makefile as we speak.
This will be cleaned up and visible at https://github.com/simh/simh in at
most a couple of days....
For folks who build their own binaries, the latest github code has a VAXStation I and VAXStation II with the MonoChrome QVSS video capabilities.
sim> SET CPU MODEL=VAXSTATION
enables the video subsystem.
The VAXStation I has a limit of 4MB of RAM, the VAXStation II has a limit of 16MB.
The makefile should just build the right thing if the development support for libSDL is installed on your platform.
Please provide bug reports and/or other feedback with issues created at https://github.com/simh/simh/issues
There is a glitch in my scripts which build and package the windows binaries which is failing to build the simulators with video support, so folks who count on the Windows Binaries will have to wait until I fix this.
Thanks.
- Mark Pizzolato
--
DECtec mailing list
http://dectec.info
To unsubscribe from this list see page at: http://dectec.info/mailman/listinfo/dectec_dectec.info
