HECnet

hecnet@lists.dfupdate.se

7 participants
15595 discussions

E11 and modules for peripherals other then the usual PC ones

by gregg.drwho8＠gmail.com

Hello! According to the manuals for E11, it now can be configured to communicate with peripherals other then the usual things that the PC normally wears. I am planning a peripheral who has the address of &H300 on the PC, according to my manuals for the PC, that's the address of the prototype board for them. I would like to write a module for E11 so that anything who writes to an appropriate location matching one of the PDP11's own gizmos for data communications other then the typical printer (parallel, serial), serial port for terminal, would have its output sent to this peripheral. I am asking here, since I saw an interesting post from John Wilson earlier this week. My next step would be to repeat this question on the newsgroups for the PDP11. And of course I will be reading and if necessary re-reading the documentation for the E11. ----- Gregg C Levine gregg.drwho8 at gmail.com "This signature was once found posting rude messages in English in the Moscow subway."

16 years, 5 months

HECnet crawler and INFO.TXT

by bob＠jfcl.com

Any chance this could be in comma separated format? Put strings in quotes if necessary. The F$ELEMENT() DCL lexical doesn't understand about items that contain embedded separators, quoted or not. Why do you want it to be a comma? Bob

16 years, 5 months

HECnet crawler and INFO.TXT

by jeep＠scshome.net

Let's try this again... Any chance this could be in comma separated format? Put strings in quotes if necessary. -Steve -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Sampsa Laine Sent: Tuesday, October 20, 2009 19:43 To: hecnet at Update.UU.SE Subject: Re: [HECnet] HECnet crawler and INFO.TXT I've updated CHIMPY in the same format. Sampsa On 21 Oct 2009, at 00:26, Bob Armstrong wrote: I took Sampsa's suggestion and put an INFO.TXT on CODA with a machine readable section at the end that contains information about the local nodes. I already wrote a little DCL script that crawls the HECnet and collects all the INFO.TXT files that it can find (so far there are eight, counting mine) and if enough people adopt this format I'll write another little script to parse out the node information. The format is pretty straight forward - you can just type out CODA::INFO.TXT and see for yourself. Bob

16 years, 5 months

HECnet crawler and INFO.TXT

by jeep＠scshome.net

Any chance that this could be in comma separated format? -Steve -----Original Message----- From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On Behalf Of Sampsa Laine Sent: Tuesday, October 20, 2009 19:43 To: hecnet at Update.UU.SE Subject: Re: [HECnet] HECnet crawler and INFO.TXT I've updated CHIMPY in the same format. Sampsa On 21 Oct 2009, at 00:26, Bob Armstrong wrote: I took Sampsa's suggestion and put an INFO.TXT on CODA with a machine readable section at the end that contains information about the local nodes. I already wrote a little DCL script that crawls the HECnet and collects all the INFO.TXT files that it can find (so far there are eight, counting mine) and if enough people adopt this format I'll write another little script to parse out the node information. The format is pretty straight forward - you can just type out CODA::INFO.TXT and see for yourself. Bob

16 years, 5 months

HECnet crawler and INFO.TXT

by roll＠Stupi.SE

NFT>type CODA::INFO.TXT So what is NFT actually doing with this as opposed to the other form?? Bob Being trouble.. Now we have to get it working from a VMSnet box trying to get a file, there is comments in the source history, but no matching code lines... " 0023 Make DIRPSW large enough to accommadate 39 character passwords so stack won't get destroyed. Also get default account for login so that a null account string will be allowed. "

16 years, 5 months

HECnet crawler and INFO.TXT

by bob＠jfcl.com

NFT>type CODA::INFO.TXT So what is NFT actually doing with this as opposed to the other form?? Bob

16 years, 5 months

HECnet crawler and INFO.TXT

by roll＠Stupi.SE

And in non VMSnet speak? It works for Sampsa - it must not like you, Peter :-) Access information for node CODA::/ACCOUNT:decnet I don't think "decnet" is the correct account to use for default access - it should be a null account name and a null password. In transparent DECnet speak, it would be CODA""::INFO.TXT. I don't know exactly how that translates to NFT. Bob Ok.... NFT>type CODA::INFO.TXT BOB AND DEBEE'S COMPUTER GARAGE ------------------------------- This is the node CODA, currently an AlphaServer DS20E running OVMS 8.3, in Bob and Debee's Computer Garage and Retirement Home for old DEC computers. It normally runs 24x7 and serves as our server for mail, DNS, NTP, Samba, and a few other services. It's also a hub of sorts for other machines which connect to HECnet via Multinet DECnet over TCP/IP connections. Thanks..

16 years, 5 months

HECnet crawler and INFO.TXT

by sampsa＠mac.com

I know, I was kidding - sorry...:) On 21 Oct 2009, at 00:53, Peter Lothberg wrote: http://rhesus.sampsa.com/cgi-bin/hecnetinfo/hecnetinfo.com?q=coda Yes... But we want this to work on HECnet, right.. Need some help here, as I knew nothing about VMS... And VMS assumes the other side is a VMS box.. -P :-P On 21 Oct 2009, at 00:48, Peter Lothberg wrote: I took Sampsa's suggestion and put an INFO.TXT on CODA with a machine readable section at the end that contains information about the local nodes. I already wrote a little DCL script that crawls the HECnet and collects all the INFO.TXT files that it can find (so far there are eight, counting mine) and if enough people adopt this format I'll write another little script to parse out the node information. The format is pretty straight forward - you can just type out CODA::INFO.TXT and see for yourself. Bob NFT>print CODA::INFO.TXT Access information for node CODA::/ACCOUNT:decnet User: decnet Password: ?Remote node refused connection - Access not permitted NFT> And in non VMSnet speak? -P

16 years, 5 months

HECnet crawler and INFO.TXT

by roll＠Stupi.SE

http://rhesus.sampsa.com/cgi-bin/hecnetinfo/hecnetinfo.com?q=coda Yes... But we want this to work on HECnet, right.. Need some help here, as I knew nothing about VMS... And VMS assumes the other side is a VMS box.. -P :-P On 21 Oct 2009, at 00:48, Peter Lothberg wrote: I took Sampsa's suggestion and put an INFO.TXT on CODA with a machine readable section at the end that contains information about the local nodes. I already wrote a little DCL script that crawls the HECnet and collects all the INFO.TXT files that it can find (so far there are eight, counting mine) and if enough people adopt this format I'll write another little script to parse out the node information. The format is pretty straight forward - you can just type out CODA::INFO.TXT and see for yourself. Bob NFT>print CODA::INFO.TXT Access information for node CODA::/ACCOUNT:decnet User: decnet Password: ?Remote node refused connection - Access not permitted NFT> And in non VMSnet speak? -P

16 years, 5 months

HECnet crawler and INFO.TXT

by bob＠jfcl.com

16 years, 5 months

Jump to page:

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet