Johnny Billquist wrote:
> Now, ANF-10 was a network protocol used on some machines way back. I
> mostly used it on TOPS-10, but I don't know if some other systems also
> supported it. I'm also not entirely sure what physical links were used
> in real life, but it appears Bygg have started to g
On 5 January 2016 at 00:25, Mark Pizzolato wrote:
> Thanks for the image and config.
>
You're quite welcome.
> I don't see the " XM4: is missing ECO's, but will still function."
> Messages... Can you explain?
>
There's only one DMR11 and one DMC11 configured. When you boot up, you'll see:
sim>
Hi Christian,
Thanks for the image and config.
I don't see the " XM4: is missing ECO's, but will still function." Messages...
Can you explain?
Thanks.
- Mark
On Monday, January 4, 2016 at 8:11 PM, Christian wrote:
> Forgot to mention: The password for account [1,2] is "operator"; the account
Very cool! Thank you very much, Johnny(s)!
Eric kd5uwl
> On Jan 4, 2016, at 8:27 PM, Johnny Billquist wrote:
>
> (Being the other Johnny here, but anyway...)
>
> What Bygg appear to be doing is implementing ANF-10 (or at least the
> simulated physical links over which ANF-10 can communicate).
Forgot to mention: The password for account [1,2] is "operator"; the
account [1,4] is also created, using [1,2] as a template; it also has
the password "operator".
And just for clarity's sake: The system has the DECnet address of
11.94, and node name of RSTS10. It knows of two other systems (provi
On 4 January 2016 at 18:10, Mark Pizzolato wrote:
> I still need a RSTS disk image and configuration file which has several
> DMC/DMR's
> configured and attempts to start the network
>
I've setup a small RSTS/E 10.1-L system with DECnet; it's kitted out
with a DELUA, DMR11, and a DMC11.
Here
(Being the other Johnny here, but anyway...)
What Bygg appear to be doing is implementing ANF-10 (or at least the
simulated physical links over which ANF-10 can communicate).
Now, ANF-10 was a network protocol used on some machines way back. I
mostly used it on TOPS-10, but I don't know if so
Johnny,
If it's not too much trouble, would you mind going into a little more
detail for the "noobs" following along out here?
I'm not _100%_ ignorant .. I was a UNIX admin for 15 years, I have a
real VAX (3900) in the garage and fooled around with VMS on it. I've
had VMS running in cluster mode
On Monday, January 4, 2016 at 12:06 PM, Paul Koning wrote:
> > On Jan 4, 2016, at 2:53 PM, Mark Pizzolato wrote:
> >
> >> ...
> >
> > I vaguely remember that something else depends on how it is currently
> > implemented. The wait delay was added to accommodate the fact that
> > something didn't e
On 2016-01-04 21:05, Paul Koning wrote:
On Jan 4, 2016, at 2:53 PM, Mark Pizzolato wrote:
...
I vaguely remember that something else depends on how it is currently
implemented. The wait delay was added to accommodate the fact that something
didn't expect immediate response. A delay of
> On Jan 4, 2016, at 2:53 PM, Mark Pizzolato wrote:
>
>> ...
>
> I vaguely remember that something else depends on how it is currently
> implemented. The wait delay was added to accommodate the fact that something
> didn't expect immediate response. A delay of 1 is essentially the same as n
On Monday, January 4, 2016 at 11:38 AM, Paul Koning wrote:
> It looks like the problems RSTS is having with DMC/DMR is due to
> unexpected behavior of the master clear bit. It's documented as self-
> clearing, so the driver sets it and then subsequently assumes it will read as
> cleared. That isn
On Mon, Jan 4, 2016 at 2:38 PM, Paul Koning wrote:
By the way, if I connect a DMC to a DMR, it doesn't come up. Is that
> expected? I thought DMC and DMR were sufficiently compatible that it would
> work...
The DMR had a switch-selectable DMC compatibility mode. Not sure if that's
implemente
It looks like the problems RSTS is having with DMC/DMR is due to unexpected
behavior of the master clear bit. It's documented as self-clearing, so the
driver sets it and then subsequently assumes it will read as cleared. That
isn't actually happening correctly, at least not if two accesses are
Status update for my little hobby project:
I just gave the following command:
.net/a/t
[ANF10 network: connected to VENUS(10), located at VENUS(10), 3 nodes]
NodeODEN(1) 10, 4
NodeLOKE(4) 1
NodeVENUS (10)1
This might look innocent, but:
Node
> On Jan 4, 2016, at 12:34 AM, Christian Gauger-Cosgrove
> wrote:
>
> Just an addendum because I think I may not have been too clear:
>
> On 4 January 2016 at 00:03, Christian Gauger-Cosgrove
> wrote:
>> Also, this might be more my inexperience, but I can't seem to figure
>> out how to get DE
> On Jan 4, 2016, at 5:09 AM, Mark Pizzolato wrote:
>
> On Sunday, January 3, 2016 at 5:25 PM, Paul Koning wrote:
>> ...
>> So attach the device in SIMH before boot, and things will work.
>
> This is a basic requirement of functionality. Having the DMC/DMR device
> "ATTACHED" merely means tha
> On Jan 4, 2016, at 4:51 AM, Mark Pizzolato wrote:
>
> On Sunday, January 3, 2016 at 2:17 PM, Paul Koning wrote:
>> ...That is with two DMCs pointing at each other:
>>
>> sim> show dmc
>> DMC lines=2, connectpoll=2, address=17760070-17760107*
>> vector=300*, 2 units
>> DMC0attac
On Sunday, January 3, 2016 at 5:25 PM, Paul Koning wrote:
> > On Jan 3, 2016, at 6:42 PM, Christian Gauger-Cosgrove
> wrote:
> >
> > On 3 January 2016 at 16:42, Paul Koning wrote:
> >> No, that's not what that means.
> >>
> >> It does say that micro diagnostics are required; when those are disabl
On Sunday, January 3, 2016 at 2:17 PM, Paul Koning wrote:
> > On Jan 3, 2016, at 1:46 PM, Christian Gauger-Cosgrove
> wrote:
> >
> > Well, I was attempting it with RSTS/E since the "XM0: is missing
> > ECO's, but will still function." error implies that the DMC11 device
> > would still function. I
On Sunday, January 3, 2016 at 1:43 PM, Paul Koning wrote:
> > On Jan 2, 2016, at 5:41 PM, Christian Gauger-Cosgrove
> wrote:
> >
> > As the subject line says, there's an issue with the DMC device under
> > RSTS/E 10.1-L.
> >
> > When starting the system, when it does the hardware scan, the
> > fol
21 matches
Mail list logo