HECnet

hecnet@lists.dfupdate.se

15556 discussions

by mcguire＠neurotica.com

On 01/16/2013 04:02 AM, Mark Wickens wrote: If someone is interested, I have published the source code and the basic circuitry I have been using. I have also built a virtual console for the virtual pdp-11. Or if you like it more, a simulation of the simulated console for the simulated PDP-11. http://ancientbits.blogspot.com.es/2013/01/blinkenlights-not-so-difficult-a… Jordi Guillaumes i Pons jg at jordi.guillaumes.name HECnet: BITXOV::JGUILLAUMES PS: This mail _could_ end being duplicated... I apologize for it I was thinking of doing this as a retrochallenge project - it's really cool and stops me from thinking about purchasing a real PDP! which is good - no space *or* money at the moment! I dunno man, doesn't sound too good to me! ;) -Dave -- Dave McGuire, AK4HZ New Kensington, PA

12 years, 3 months

Sample DCL code for simple client-server task-to-task comms

by sampsa＠mac.com

OK, figured that out, I have to use an open to access it first. sampsa On 17 Jan 2013, at 02:35, sampsa at mac.com wrote: How come writing to SYS$NET doesn't send any output? FOOBAR.COM is now: $WRITE SYS$NET "Foobar" $DIRECTORY/OUTPUT=SYS$NET But I only get the directory listing. sampsa On 17 Jan 2013, at 02:32, "Brian Schenkenberger, VAXman-" <system at TMESIS.COM> wrote: sampsa at mac.com writes: Oh cool, that worked. Thanks. The "TASK=..." will open a channel to and execute the procedure. Logical SYS$NET is defined as the "back-channel" for communications. So, you can sent data back in any method you chose as long as it's channels through SYS$NET. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG Well I speak to machines with the voice of humanity.

12 years, 3 months

Sample DCL code for simple client-server task-to-task comms

by sampsa＠mac.com

How come writing to SYS$NET doesn't send any output? FOOBAR.COM is now: $WRITE SYS$NET "Foobar" $DIRECTORY/OUTPUT=SYS$NET But I only get the directory listing. sampsa On 17 Jan 2013, at 02:32, "Brian Schenkenberger, VAXman-" <system at TMESIS.COM> wrote: sampsa at mac.com writes: Oh cool, that worked. Thanks. The "TASK=..." will open a channel to and execute the procedure. Logical SYS$NET is defined as the "back-channel" for communications. So, you can sent data back in any method you chose as long as it's channels through SYS$NET. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG Well I speak to machines with the voice of humanity.

12 years, 3 months

Sample DCL code for simple client-server task-to-task comms

by system＠TMESIS.COM

sampsa at mac.com writes: Oh cool, that worked. Thanks. The "TASK=..." will open a channel to and execute the procedure. Logical SYS$NET is defined as the "back-channel" for communications. So, you can sent data back in any method you chose as long as it's channels through SYS$NET. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG Well I speak to machines with the voice of humanity.

12 years, 3 months

Sample DCL code for simple client-server task-to-task comms

by sampsa＠mac.com

Oh cool, that worked. Thanks. sampsa On 17 Jan 2013, at 02:27, "Brian Schenkenberger, VAXman-" <system at TMESIS.COM> wrote: sampsa at mac.com writes: I get this error in netserver.log: -------------------------------------------------------- Connect request received at 17-JAN-2013 03:17:45.52 from remote process RHESUS::"0=SYSTEM" for object "FOOBAR.COM" -------------------------------------------------------- %DCL-W-UNDFIL, file has not been opened by DCL - check logical name FOOBAR.COM does exist in the home directory of the user. sampsa On RHESUS, file FOOBAR.COM is: $ DIRECTORY/OUTPUT=SYS$NET Then, from another node: $ TYPE RHESUS"username password"::"TYPE=FOOBAR" -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG Well I speak to machines with the voice of humanity.

12 years, 3 months

Sample DCL code for simple client-server task-to-task comms

by system＠TMESIS.COM

sampsa at mac.com writes: I get this error in netserver.log: -------------------------------------------------------- Connect request received at 17-JAN-2013 03:17:45.52 from remote process RHESUS::"0=SYSTEM" for object "FOOBAR.COM" -------------------------------------------------------- %DCL-W-UNDFIL, file has not been opened by DCL - check logical name FOOBAR.COM does exist in the home directory of the user. sampsa On RHESUS, file FOOBAR.COM is: $ DIRECTORY/OUTPUT=SYS$NET Then, from another node: $ TYPE RHESUS"username password"::"TYPE=FOOBAR" -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG Well I speak to machines with the voice of humanity.

12 years, 3 months

Sample DCL code for simple client-server task-to-task comms

by sampsa＠mac.com

I get this error in netserver.log: -------------------------------------------------------- Connect request received at 17-JAN-2013 03:17:45.52 from remote process RHESUS::"0=SYSTEM" for object "FOOBAR.COM" -------------------------------------------------------- %DCL-W-UNDFIL, file has not been opened by DCL - check logical name FOOBAR.COM does exist in the home directory of the user. sampsa On 17 Jan 2013, at 01:58, "Brian Schenkenberger, VAXman-" <system at TMESIS.COM> wrote: sampsa at mac.com writes: Anybody have a snippet of DCL for doing this, i.e. talking from one host (client) to anohter (server) in DCL. Do you have the task object enabled? If so, you can use: $ TYPE NODE"username password"::"TASK=some_command_procedure.COM" The command procedure must reside in the home directory of the account associated with "username password". Once you've connected, communicate using the SYS$NET logical. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG Well I speak to machines with the voice of humanity.

12 years, 3 months

Sample DCL code for simple client-server task-to-task comms

by bqt＠softjar.se

On 2013-01-17 00:58, Brian Schenkenberger, VAXman- wrote: sampsa at mac.com writes: Anybody have a snippet of DCL for doing this, i.e. talking from one host (client) to anohter (server) in DCL. Do you have the task object enabled? If so, you can use: $ TYPE NODE"username password"::"TASK=some_command_procedure.COM" The command procedure must reside in the home directory of the account associated with "username password". Once you've connected, communicate using the SYS$NET logical. Ok, showing my ignorance here. It it not possible to do: $ TYPE NODE"username password"::"TASK=disk:[directory]command_procedure.COM" ? 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

12 years, 3 months

Sample DCL code for simple client-server task-to-task comms

by system＠TMESIS.COM

sampsa at mac.com writes: Anybody have a snippet of DCL for doing this, i.e. talking from one host (client) to anohter (server) in DCL. Do you have the task object enabled? If so, you can use: $ TYPE NODE"username password"::"TASK=some_command_procedure.COM" The command procedure must reside in the home directory of the account associated with "username password". Once you've connected, communicate using the SYS$NET logical. -- VAXman- A Bored Certified VMS Kernel Mode Hacker VAXman(at)TMESIS(dot)ORG Well I speak to machines with the voice of humanity.

12 years, 3 months

Multi-floor household (DECnet) routing help needed

by b4＠gewt.net

On 16 Jan 2013, at 18:39, Brian Hechinger <wonko at 4amlunch.net> wrote: If you have time tomorrow we can chat about it. I've had great success with it. I should have time tomorrow, anytime past 14:30/15:00 EDT. -brian On Jan 16, 2013, at 18:23, Cory Smelosky <b4 at gewt.net> wrote: On 16 Jan 2013, at 18:19, Brian Hechinger <wonko at 4amlunch.net> wrote: Is there coax in the place? If so look at MoCa devices. Works really well. Yeah, there's coax, but not in the same room as the /main/ switch There is in another room though that has a switch too. The equipment in the basement is a short run away from the coax splitter down there so that's actually a good idea. -brian On Jan 16, 2013, at 17:12, Cory Smelosky <b4 at gewt.net> wrote: Hello! I'm going to be moving some of my equipment to the basement here for several reasons (heat produced, noise, space, et cetera), and in planning i'm hitting a roadblock: networking. I've come up with several ideas: Wireless client-bridge: Linksys e1000 is garbage and doesn't like to pass DECnet or any of those protocols, so i'd either need a workaround or a better router. (workaround being: a virtual cisco tunnel to my other virtual cisco?) (Other router: /real/ Cisco or a another suggestion from someone on this list) Powerline ethernet: Is this reliable yet? How are the transfer speeds? Or: Adding a phone jack, getting DSL on the second line here. (installation costs, but would actually be $2 more/month to upgrade current plan + add a second identical plan not counting hardware rental fees, setup costs, and that stuff) Running cables all the way from the second floor isn't viable. Any (viable) options i'm missing? -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project. -- Cory Smelosky http://gewt.net/ Personal stuff! http://gimme-sympathy.org/ My permanently-a-work-in-progress pet project.

12 years, 3 months

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

HECnet