On Wed, Jan 16, 2013 at 11:40 PM, Dave McGuire <mcguire at neurotica.com> wrote:
Yes, that's SIMH running *on* VMS.
Binaries are here, currently only for VAX, still working on alpha,
feel free to download:
ebola::disk$user:[decnet.simh.vax]
Note that there's no network support. Network support works on Alpha,
but not VAX. Not sure why.
I just shut down an instance of RSTS/E v10.1 under SIMH on my VAX
7700. I'm currently booting VMS 7.3. =)
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
Hello!
There are plenty of reasons why something does not want to work.
-----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature fought the Time Wars, time and again."
Yes, that's SIMH running *on* VMS.
Binaries are here, currently only for VAX, still working on alpha,
feel free to download:
ebola::disk$user:[decnet.simh.vax]
Note that there's no network support. Network support works on Alpha,
but not VAX. Not sure why.
I just shut down an instance of RSTS/E v10.1 under SIMH on my VAX
7700. I'm currently booting VMS 7.3. =)
-Dave
--
Dave McGuire, AK4HZ
New Kensington, PA
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
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.
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.
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.
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.
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.
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.
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