Hi Paul,
How was this tested: 11M+ to 11M+ or 11M+ to PyDecnet?
Reindert
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf
Of Paul Koning
Sent: Thursday, 23 December, 2021 02:36
To: hecnet at update.uu.se
Subject: Re: [HECnet] native Dup sync line revisited --> preliminary tests
reveals problems
> On Dec 13, 2021, at 9:15 AM, Paul Koning <paulkoning at comcast.net> wrote:
>
> ...
> So if the plain sync device emulation were to do the above, that would
give us an emulation that interoperates with the DMC emulation if the
software controlling the device is running DDCMP.
More on this...
I built an M+ system with DUP lines, and unlike what was reported in this
thread, I did NOT see problems talking to other things (like PyDECnet or DMC
emulation) that expect plain data without frame length fields. I don't see
frame lengths in the trace.
I don't understand this because the code is clearly there in the emulator,
so apparently it's not being hit. Not by DECnet/RSX anyway. More to be
studied.
paul
?Supratim,
Thanks for your comments on the HECnet mail-list. Also, I enjoyed reading about
your work modifying the Frodo distribution for a dual ethernet 11/93. Nice work!
I?ve been planning to update the Frodo distribution to update some of the layered product software (BasicPlus2, Datatrieve and APL to use I/D space) and the latest TCP/IP including the new updates to the TYDRV that require a SYSGEN to rebuild.
BestRegards,
Mark
> On Dec 22, 2021, at 2:50 PM, Supratim Sanyal <supratim at riseup.net> wrote:
> ?
> Sorry - Mark already responded.
>
> There is interesting history behind "FRODO" too ...
>
> On 12/22/21 1:35 PM, Mark Matlock wrote:
>
>> Paul,
>> You could also download ftp://ftp.trailing-edge.com/pub//rsx_dists/rsx11mpbl87.dsk.bz2 which is
>> a baseline RSX11M+ V4.6 disk image ready for a SYSGEN from [200,200] It also has DECnet V4.6 already in [137,10] for a NETgen. This DECnet distribution only generates endnotes however and you may want to get an
>> area routing DECnet distribution from MIM.
>>
>> Also a RSX11M+ V4.6 with DECnet (for Unibus systems) and a very old version of Johnny?s BQTCP/IP is available at:
>>
>> http://www.rsx11m.com/PiDP11_DU0.zip
>>
>> It has area routing DECnet running but you would really need to update the TCP/IP but you can FTP
>> that from Mim.update.uu.se and get Johnny?s latest version.
>>
>> Best,
>> Mark
>>
>>
>>
>>
>>> On Dec 22, 2021, at 12:14 PM, Paul Koning <paulkoning at comcast.net> wrote:
>>>
>>>
>>>
>>>> On Dec 22, 2021, at 1:07 PM, Johnny Billquist <bqt at softjar.se> wrote:
>>>>
>>>> Hi, Paul. Sorry I didn't answer earlier. Saw some other mails I should have responded too as well, but been a bit busy.
>>>>
>>>> Anyway. 4.0 is way old and have various issues you do not want or need. Locate M+ 4.6 instead. That's basically the only version I'd recommend.
>>>> And yes, M+ is definitely easier to deal with than 11M.
>>>>
>>>> You can find both tapes at http://bitsavers.org/bits/DEC/pdp11/magtapes/rsx11mplus/
>>>>
>>>> Basically you want BB-J0830-01.L01_RSX11M+_V4.6_BRU_1999.tap, which should be bootable, and contain all you need for M+ itself. There is a second tape (BB-J0830-01.M01_RSX11M+_V4.6_1999.tap), which might be the second tape if the whole thing came on two tapes. (I got M+ 4.6 on TK50, which just came on a single cartridge.)
>>>>
>>>> Then you want DECnet, which is decnet11mp46-netkit.tap. The manuals are online, but of course you can also just ask. And since you seem to have already managed once, it should hopefully not be too complicated.
>>> I used the DECnet 4.0 kit because I could not make sense out of that 4.6 kit. The installation procedure in the manual (DECnet/RSX 4.5, which says it's for M+ 4.3) doesn't work at all with that tape. It says to use FLX to copy PREGEN.CMD from the tape, but the tape isn't anything FLX understands. Instead, it seems to be an ANSI labeled tape with 3 files on it, the first one named "INSTALL". Is that a BRU tape? Or a DSC tape? What do I do with it?
>>>
>>> paul
> --
Are there any thoughts about adding file transfer capabilities to PyDECnet at some point in the future? If a pyDECnet node could implement a FAL server to share a directory and/or offer a way to copy files to/from other nodes over DECnet, that would be really cool. I think it could make a very nice option for moving files between DECnet nodes and modern systems without needing to wrestle with Linux DECnet drivers or install TCP/IP on the DECnet nodes. I don't know how hard it would be to implement, or if there's any way I could contribute.
I'm imagining a silly future in which there is a native Python implementation of an entire RSX-11 or VMS system. :)
While I'm here... is this mailing list disappearing soon due to the Update eviction? I plan to chip in for an Update membership for 2022.
--
Mark J. Blair, NF6X <nf6x at nf6x.net>
https://www.nf6x.net/
I'm trying to build a DECnet/RSX system, and since I've never done anything like that I figured I'd try M+ as (right?) the easiest option.
Did a sysgen, that seemed to work ok. Found a DECnet kit on Bitsavers, the 4.0 one marked "3errs", used that to do netgen. That too seemed ok.
Now I'm trying "netins". That fails mid-way and I have no clue why:
>@[5,1]netins
>* Do you want to install and load the CEX system? [Y/N]: y
>* Do you want to install and start DECnet? [Y/N]: n
>* On what device are the network tasks [D=DU0:] [S]:
>INS XX:[5,54]NTINIT
>INS XX:[5,54]NTL
>INS XX:[5,54]MLD
>INS XX:[5,54]EVC
>INS XX:[5,54]NCPRES
>; INS XX:[5,54]CFERES
>; INS XX:[5,54]VNP
>INS XX:[5,54]NMVACP
>SET /SYSUIC=[5,54]
>ASN XX:=LB:
>LOA NM:/HIGH/VEC
>CON ONL NM:
>ASN =LB:
>SET /SYSUIC=[2,54]
>INS XX:[5,54]LOO
>INS XX:[5,54]LOO/TASK=LOO...
>INS XX:[5,54]EVFRES
>SET /UIC=[5,54]
>NCP SET SYS
12:56:33 Task "NTL..." terminated
Odd address or other trap four
R0=000000
R1=000000
R2=000005
R3=000004
R4=151775
R5=157724
SP=120614
PC=160252
PS=170000
Any ideas?
paul
How do I setup the ethernet connection on Windows in order to enable
SimH/VAXVMS to communicate with the world?
I used:
Set xu enable
Set xu eth7 (my Wi-Fi connection)
This gives me:
sim> sho xu
XU address=2013F948-2013F94F, vector=50, BR5, MAC=08:00:2B:00:01:05
type=DELUA, throttle=disabled
attached to eth7
But VMS does not recognize UNA-0.
Groeten,
Rien Timmer
Johnny Billquist <bqt at softjar.se> writes:
>That /NOTYPE_AHEAD would disable logins in VMS is a bit surprising.
>In my eyes, that's very unintuitive. /NOINTERACTIVE seems much more
>sensible (yay for RSTS/E).
When a terminal has no associated process and it receives unsolicited
input, it forks into routine UNSOL in module TTYSUB. UNSOL notifies
the job controller of the occurrance by sending a message to the job
cntroller's permanet mailbox. This message contains the device name
and precipitates the creation of a login process. There are various
other actions based upon the type of terminal and other attributes of
the device that may occur prior to the actions of the job controller
but without TYPE_AHEAD, none of this occurs.
>Sounds like VMS also have /NOINTERACTIVE...?
VMS has no /NOINTERACTIVE. Interactive is a process right assigned
to a process that is instantiated via an unsolicited interrupt on a
terminal device.
>In RSX, /NOTYPE_AHEAD just means you don't have any typeahead. If you
>try typing something when nothing is reading, the characters are just
>thrown away. But if a read is in progress, things works just as normal.
I thought this was a question concerning VMS.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
I speak to machines with the voice of humanity.
"Mark J. Blair" <nf6x at nf6x.net> writes:
>
>
>> On Dec 20, 2021, at 6:00 PM, Brian Schenkenberger, VAXman- =
><system at TMESIS.COM> wrote:
>>=20
>>> Sounds like VMS also have /NOINTERACTIVE...?
>>=20
>> VMS has no /NOINTERACTIVE. Interactive is a process right assigned
>> to a process that is instantiated via an unsolicited interrupt on a
>> terminal device.
>
>/NOINTERACTIVE is not listed in the HELP SET TERM text, but SET TERM =
>TTAn: /PERM/NOINTERACTIVE is accepted as a command where I tried it in =
>v5.5 and v7.3, and it changes the first characteristic shown by SHOW =
>TERM from "Interactive" to "Passall". /shrug
/[NO]PASSALL is obsolete. You'll also find that it will disable other
terminal features you may desire keeping.
>From the VMS HELP for SET TERMINAL/TYPE_AHEAD:
SET
TERMINAL
/TYPE_AHEAD
/TYPE_AHEAD (default)
/NOTYPE_AHEAD
Controls whether the terminal accepts unsolicited input to the
limit of the type-ahead buffer.
When you specify the /NOTYPE_AHEAD qualifier, the terminal
accepts input only when a program or the system issues a read
to the terminal, such as for user input at the DCL prompt ($).
When you specify the /TYPE_AHEAD qualifier, the amount of data
that can be accepted is governed by the size of the type-ahead
buffer. That size is determined by system generation parameters.
>Thank you for your explanation of how a login prompt gets triggered.
>That was neat. It's quite different from the way that happens in
>unix-like OSes.
Yup. Having a getty hanging about on all possible terminals seems a bit
1970 to me.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
I speak to machines with the voice of humanity.
The recent thread "Disallow system from dz lines (OpenVMS/VAX 7.3)" started me wondering how to entirely disable the login prompts on a given serial line, such as to use the port for some other purpose like controlling external hardware. I've been trying to find out how to do that in the manuals, but I haven't found it yet. It seems like it might be something to do with SET TERM, but I don't see obvious flags for that. Can anybody offer any hints? I won't be too surprised if my eyes have already glided over the answer in the manuals and HELP SET TERM text.
--
Mark J. Blair, NF6X <nf6x at nf6x.net>
https://www.nf6x.net/
"Mark J. Blair" <nf6x at nf6x.net> writes:
>The recent thread "Disallow system from dz lines (OpenVMS/VAX 7.3)" =
>started me wondering how to entirely disable the login prompts on a =
>given serial line, such as to use the port for some other purpose like =
>controlling external hardware. I've been trying to find out how to do =
>that in the manuals, but I haven't found it yet. It seems like it might =
>be something to do with SET TERM, but I don't see obvious flags for =
>that. Can anybody offer any hints? I won't be too surprised if my eyes =
>have already glided over the answer in the manuals and HELP SET TERM =
>text.
Set the terminal line /NOTYPE_AHEAD.
--
VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG
I speak to machines with the voice of humanity.
Hi folks,
I need to port a simple DECnet task-to-task program to RSTS/E V10.1,
DECnet/E V4.1
Do any of you PDP-11 buffs have a DECnet/E programming manual. I know
bitsavers doesn't.
A small example in Fortran, Basic, Basic-Plus will also do.
The functionality, expressed in VMS DCL, is as follows:
$ open /read /write NETCHN REMOTE::"150="
$ write NETCHN "''f$trnlnm(SYS$NODE)'"
$ read NETCHN time
$ close NETCHN
Thanks,
Wilm