"Cory Smelosky" <b4 at gewt.net> writes:
On 16 Jun 2013, at 16:43, "Dave McGuire" <mcguire at neurotica.com> wrote:
=20
On 06/16/2013 04:08 PM, Bob Armstrong wrote:
Does anybody have a copy of the DECserver-200 management kit for VMS, =
v3.0?=20
It=92d be DS2030.A and DS2030.B. I have the v2.0 kit, but not 3.0.
=20
Urrr? I don't have it, but then I've never heard of it. Does it =
allow for
things like centralized management of a group of DECservers or =
something like
that?
I believe it allowed you to configure different software images based on =
MAC address. It seems to have simplified a couple things.
I could be wrong.
Just how many software images would one need for a DECserver-200. I would
have installed the latest and greatest, and disregarded and discarded any
prior versions.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
Well I speak to machines with the voice of humanity.
On 16 Jun 2013, at 16:59, "Dave McGuire" <mcguire at neurotica.com> wrote:
On 06/16/2013 04:51 PM, Bob Armstrong wrote:
Dave McGuire wrote:
I've never heard of it
http://h30266.www3.hp.com/masterindex/installation_guide/installation_guide_
0000b767.txt
It's basically the VMS kit that contains the DS200 load software, but it
comes with several useful command procedures too.
Neat! Thanks for the pointer. I've always just gotten the bare images and
dropped them into place...I guess I never stopped to think of how those
images would've gotten installed in the first place.
When I was a VMS sysadmin, we used a few Emulex terminal servers
("Performance 4000" if memory serves) that were really nice...I don't recall
them having to boot from the network, though. I have a few of those here
with dead power supplies. I should send them to Cory. ;)
Go ahead. ;) I m could use some more systems to replace the power supplies on! :)
My supply of computer PSUs is running short, I might need to start scrapping other stuff.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 16 Jun 2013, at 23:59, Dave McGuire <mcguire at neurotica.com> wrote:
When I was a VMS sysadmin, we used a few Emulex terminal servers
("Performance 4000" if memory serves) that were really nice...I don't recall
them having to boot from the network, though. I have a few of those here
with dead power supplies. I should send them to Cory. ;)
-Dave
I've got a 48 port cyclades sitting in my flat in London, not even plugged in.
It does everything pretty much, even has a built-in PPP/SLIP server in case you want to run your own ISP.
Alas, it does not talk LAT, just IP.
sampsa
On 06/16/2013 04:51 PM, Bob Armstrong wrote:
Dave McGuire wrote:
I've never heard of it
http://h30266.www3.hp.com/masterindex/installation_guide/installation_guide_
0000b767.txt
It's basically the VMS kit that contains the DS200 load software, but it
comes with several useful command procedures too.
Neat! Thanks for the pointer. I've always just gotten the bare images and
dropped them into place...I guess I never stopped to think of how those
images would've gotten installed in the first place.
When I was a VMS sysadmin, we used a few Emulex terminal servers
("Performance 4000" if memory serves) that were really nice...I don't recall
them having to boot from the network, though. I have a few of those here
with dead power supplies. I should send them to Cory. ;)
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 16 Jun 2013, at 16:43, "Dave McGuire" <mcguire at neurotica.com> wrote:
On 06/16/2013 04:08 PM, Bob Armstrong wrote:
Does anybody have a copy of the DECserver-200 management kit for VMS, v3.0?
It d be DS2030.A and DS2030.B. I have the v2.0 kit, but not 3.0.
Urrr? I don't have it, but then I've never heard of it. Does it allow for
things like centralized management of a group of DECservers or something like
that?
I believe it allowed you to configure different software images based on MAC address. It seems to have simplified a couple things.
I could be wrong.
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
On 06/16/2013 04:08 PM, Bob Armstrong wrote:
Does anybody have a copy of the DECserver-200 management kit for VMS, v3.0?
It d be DS2030.A and DS2030.B. I have the v2.0 kit, but not 3.0.
Urrr? I don't have it, but then I've never heard of it. Does it allow for
things like centralized management of a group of DECservers or something like
that?
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
Does anybody have a copy of the DECserver-200 management kit for VMS, v3.0? It d be DS2030.A and DS2030.B. I have the v2.0 kit, but not 3.0.
Thanks,
Bob
On Saturday, June 15, 2013 at 10:49 PM, Gregg Levine wrote:
On Sun, Jun 16, 2013 at 1:18 AM, Mark Pizzolato - Info Comm
<Mark at infocomm.com> wrote:
On Saturday, June 15, 2013 at 10:01 PM, Gregg Levine wrote:
On Sun, Jun 16, 2013 at 12:51 AM, Mark Pizzolato - Info Comm
<Mark at infocomm.com> wrote:
On Thursday, June 13, 2013 at 7:47 PM, Gregg Levine wrote:
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.
The Windows Binaries (including VAXStation I and VAXStation II) are
now available at:
https://github.com/simh/Win32-Development-Binaries
Download the latest zip file.
Hello!
Nice to know Mark. Any suggestions for implementing it on a
Raspberry Pi system w/ 512MB of memory?
I don't see any reason it wouldn't work as long as you've got the
right SDL
development pieces available.
I did get the code outside of your screen idea to build properly.
I'm not sure what this sentence means.... what does "code outside
of your
screen idea" mean?
- Mark
Hello!
Oh sorry. I meant everything contained within the entire SIMH
retrieval except for the screen presentation method.
I think you are trying to say that all simulators except the MicroVAX I
(VAXStation I) and MicroVAX II (VAXStation II) built. OK, that is expected.
Numerous folks are running the latest code on Raspberry Pi systems. The
QVSS video on the MicroVAX I and MicroVAX II simulators was just merged
into the code base last week.
If you can't get the MicroVAX I and MicroVAX II to build, I'm going to need
more information to help. Please create an issue at
https://github.com/simh/simh/issues to record the problem and to contain
the details of chasing this down to a solution.
Please Include the output produced when you attempted to build these
simulators.
Thanks.
- Mark
Hello!
That's just it Mark. After using the git pull <repository name> command to
pull everything into the source directory I chose, I then entered the created
one, examined everything briefly, and then entered the command make and
off it went.
I first made the BIN directory, and then did that. I did need to build the Altair
ones out of sequence however. Also the Nova one as well. I did not make
the ones for the older IBM machines or the other simulators that I wasn't
familiar with.
I found that the screen thing needed the SDL library and I wasn't ready to
massage the repositories that make up Debian on Raspberry Pi to find that
one so I let wait.
My only complaint is that when I ran the vax simulation to confirm that was
all working, it then told me that the IDLE function was disabled, that was
when I asked it about the devices.
Hi Gregg,
Nothing in the new codebase should have changed idle behavior (or availability) for any simulator.
Please provide the output of "SHOW VERSION" in the simulator which isn't behaving as you want.
The complete output produced when the simulator was built will also be useful.
- Mark
On 2013-06-16 15:11, Johnny Billquist wrote:
On 2013-06-16 14:58, Steve Davidson wrote:
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Paul_Koning at Dell.com
Sent: Saturday, June 15, 2013 12:51
To: bqt at softjar.se
Cc: hecnet at Update.UU.SE; bob at jfcl.com
Subject: Re: [HECnet] DECnet default access on RSX...
On Jun 15, 2013, at 11:14 AM, Johnny Billquist wrote:
On 2013-06-15 17:03, Paul_Koning at Dell.com wrote:
On Jun 15, 2013, at 9:19 AM, Johnny Billquist wrote:
...
Proxy access is not standardized or documented (at the
protocol level). I think it's simply this: the access
control fields in the session control protocol are optional.
If they are omitted, it's up to the receiving node to decide
what to do about it (if the application protocol in question
has the notion of access control). In some systems, the
answer is "reject". In others, the answer is "use a default
account" (RSTS has this).
Well, proxy is something that needs to be enabled on both
sides for it to work, so it definitely involves passing some
information in the packets. So it has to be documented
somewhere. Keep searching.
I don't think so. RSTS has no notion of proxy, but I
distinctly remember having proxies on VMS work when accessed
from RSTS with no access control specified.
paul
I have a proxy from PLUTO::[1,2] to SGC::SYSTEM. The behavior is
exactly what Paul says it is.
How do you know it is a proxy access, and not the default DECnet account
in VMS?
Here is one RSX system to another, as illustration:
.set /host
Host=JOCKE RSX-11M-PLUS V5.0 BL88
.ncp set exec out prox dis
.nft mim::info.txt/li
NFT -- Error in reading directory MIM::INFO.TXT
Access control rejected
.ncp set exec out prox ena
.nft mim::info.txt/li
Directory MIM::DU4:[BQT]
16-JUN-13 15:09:17
INFO.TXT;1 8./35. 08-JUL-10 10:54:52
Total of 8./35. Blocks in 1. Files
.
Tell you what. Anyone who wants to play with proxy, just try talking to
MIM without giving an account. With proxy disabled at your end (or if
you lack the capability), you will not be able to talk with MIM, while
if you enable proxy at your end, you will.
Oh yeah, and to show that you are probably not using proxy information when talking to SGC::
.ncp set exec out prox dis
.nft sgc::info.txt/li
Directory SGC::SYS$SPECIFIC:[DECNET]
16-JUN-13 15:24:22
INFO.TXT;1 6./9. 30-DEC-11 13:11:22
Total of 6./9. Blocks in 1. Files
Johnny
--
Johnny Billquist || "I'm on a bus
|| on a psychedelic trip
email: bqt at softjar.se || Reading murder books
pdp is alive! || tryin' to stay hip" - B. Idol
