On 2012-07-11 22:55, Bob Armstrong wrote:
I ve set up an Internet SMTP to HECnet MAIL11 gateway. To send mail
from the Internet to a HECnet node, address it to
user at node.decnet.org <mailto:user at node.decnet.org>
where user is the VMS (or RSX or RSTS or whatever) user name and
node is the HECnet node name. If you re logged into a HECnet machine
you can send Internet mail by addressing it to
LEGATO::SMTP%user at whereever.com <mailto:user at whereever.com>
Note that LEGATO will store mail sent in either direction for up two
days if the target node is down at the time that means your HECnet
machine doesn t have to be online 24x7 in order to receive mail.
IMPORTANT - There is absolutely no SPAM filtering, so please be very
careful about where or how you publish these addresses unless you want
your VMS mailbox filled up with thousands of SPAMs
Nice. Thanks.
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
Hi, I've just tried this and got this error mailed back to me:
Bad address -- <"tardis::tony">
Error --
%MAIL-E-LOGLINK, error creating network link to node TARDIS
-SYSTEM-F-NOSUCHNODE, remote node is unknown
And mailing from the VMS box gives me this:
MAIL> mail
To: legato::smtp%tonyblews at gmail.com
%JBC-E-JOBQUEDIS, system job queue manager is not running
This is probably my fault, so what am I doin wrong?
On Wed, Jul 11, 2012 at 8:55 PM, Bob Armstrong <bob at jfcl.com> wrote:
I ve set up an Internet SMTP to HECnet MAIL11 gateway. To send mail from the Internet to a HECnet node, address it to
user at node.decnet.org
where user is the VMS (or RSX or RSTS or whatever) user name and node is the HECnet node name. If you re logged into a HECnet machine you can send Internet mail by addressing it to
LEGATO::SMTP%user at whereever.com
Note that LEGATO will store mail sent in either direction for up two days if the target node is down at the time that means your HECnet machine doesn t have to be online 24x7 in order to receive mail.
IMPORTANT - There is absolutely no SPAM filtering, so please be very careful about where or how you publish these addresses unless you want your VMS mailbox filled up with thousands of SPAMs
Bob
I ve set up an Internet SMTP to HECnet MAIL11 gateway. To send mail from the Internet to a HECnet node, address it to
user at node.decnet.org
where user is the VMS (or RSX or RSTS or whatever) user name and node is the HECnet node name. If you re logged into a HECnet machine you can send Internet mail by addressing it to
LEGATO::SMTP%user at whereever.com
Note that LEGATO will store mail sent in either direction for up two days if the target node is down at the time that means your HECnet machine doesn t have to be online 24x7 in order to receive mail.
IMPORTANT - There is absolutely no SPAM filtering, so please be very careful about where or how you publish these addresses unless you want your VMS mailbox filled up with thousands of SPAMs
Bob
-----Original Message-----
From: owner-hecnet at Update.UU.SE
[mailto:owner-hecnet at Update.UU.SE] On Behalf Of Bob Armstrong
Sent: Wednesday, July 11, 2012 10:11
To: hecnet at Update.UU.SE
Subject: RE: [HECnet] decnet.org
I used it a few times [SMTP <> MAIL11 gateway] and enjoyed it.
Ok, I'll look at setting it up again this afternoon. Maybe
I can get you to help me set up an RSX system in exchange.
Bob
Bob, (and Johnny),
If you give me the info I will setup this end (on Sunday) for hecnet.org
such that it points as follows:
<username>@<HECnet-nodename>.hecnet.org
-Steve
On 11 July 2012 15:42, Mark Benson <markbenson at mac.com> wrote:
I have ordered 100 MMJ plugs and a MMJ compatible crimp tool to make my own MMJ cables.
I would like to know the cable spec (how many cores, flat or round, twisted pair or not) and also the wiring spec for each end (does one end cross over or not).
--
Mark Benson
http://markbenson.org/bloghttp://twitter.com/MDBenson
--
DECtec mailing list
http://dectec.info
To unsubscribe from this list see page at: http://dectec.info/mailman/listinfo/dectec_dectec.info
Where did you order the crimper from? I have only been able to find very expensive crimpers I cannot justify buying.
Regards
Rob
Hi,
After reading the real experts discussing about the difficulties one has to expect generating a 11M (no plus) system I wanted to test it first hand and I've (almost) successfully sysgene'd from scratch a RSX11M 4.6 system from its tape distribution. I said "almost" because I've run into 2 little problems, one of those probably coming from my lack of knowledge about RSX itself...
1) I get no "REMove" task built. I've tried a SYSGEN3 and it doesn't get built either. I wonder if that task is absent from the "standard function" system and I will have to do a fully customized SYSGEN.
2) Even being logged on a privileged account I can't write anything under [1,54] unless I SET /UIC first. I get a privilege violation error when I try to PIP something if I have any other default directory. That causes installation scripts to fail (I've tried to install F77 and it aborts when it tries to copy the OTS and the compiler task. My SYSUID is set to [1,54]. I guess I'm missing something but have no clue about what is it.
If I can overcome these problems I plan to publish the installation log to help anyone wanting to do the same...
Jordi Guillaumes i Pons
Barcelona - Catalunya - Europa
You can't take the default on *all* questions, since some don't have ny
defaults.
The CSR and vector for the terminal lines, for example... :-)
You're right - I did have to enter the address for that one.
Simh is rather simple minded about the terminal muxes - it considers the
DZ11/DZV11/DZQ11/CYX08/CXY16 all to be the same. Although the hardware is
different as far as I know they all have the same programmer model so this
is not unreasonable. The only thing that differs is the number of lines per
board, and simh allows you to set that.
And the only floating vector in this configuration, AFAIK, is the DZ/CXY
and 300 is the first one, right?
FWIW I did a VMS SYSGEN (which, among other things allows you to enter a
list of devices and will calculate for you the correct CSR/vector
assignments) and it agrees with simh in that regard. It particular, it says
160100 and vector 300 for the DZ11. As far as I know the PDP-11 and VAX
rules for address and vector assignments are the same, but it's possible RSX
does something different. It's suspicious that the default answer for the
first DZ11 in the RSX SYSGEN is not the same as the default floating address
assignment.
The other devices (MSCP disk, MSCP tape, NI) are all their default
addresses for the first such device.
You really need to make sure your hardware is correctly configured before
you can expect ACF to work.
Sure, but that's the whole question. I think this is the correct
configuration unless you can see what's wrong.
The other possibility that there's some hardware in there that this
version of ACF doesn't know about.
I guess I could do another SYSGEN and just take out the DZ/CXY from the
simh configuration. That's easy enough to do.
Bob
On 2012-07-11 16:36, Bob Armstrong wrote:
Doubly so that CON ONLINE (if I remember right) also hang.
That's correct - the CON ONLINE ALL hangs on the generated system. The
Baseline system works OK.
The baseline system is a bit simpler, in that it don't have as many devices generated in...
Maybe a misconfiguration of some sort...?
Well, what? Like you said, the M+ SYSGEN is pretty simple and almost all
the questions, even w/o autoconfigure, take the default answers. Either
that, or there's something that's not supported by 4.3 (even though it says
that it is).
Looking at your other post, I'm looking suspiciously at your terminal lines...
You can't take the default on *all* questions, since some don't have ny defaults. The CSR and vector for the terminal lines, for example... :-)
Actually I'd easily believe that it was a misconfiguration except for the
fact that ACF also hangs. That says to me that there's something about this
configuration that either isn't supported or doesn't actually work with M+
v4.3.
ACF is a totally different story. ACF can hang for any number of reasons. You really need to make sure your hardware is correctly configured before you can expect ACF to work. ACF is probing all over the bus, and determines what type of device it is by what it has already detected. There is no easy way to detect the type of a device on a Unibus or Qbus. Thus, if you do not follow the rules in the manuals on what address to assign to devices in the floating address space, ACF will not work right for you, and might in fact think that your device is something completely different, and tries to program it accordingly.
CON ONLINE on the other hand uses the actual information you have provided, and just tries to talk to the expected device that you specified, at the expected address, which you also specified. If that fails, it would normally be because the device is not what you said.
Or there's a bug in simh - that'd be ugly...
Yes. But I am hesitant to blame simh at this point.
Johnny
Doubly so that CON ONLINE (if I remember right) also hang.
That's correct - the CON ONLINE ALL hangs on the generated system. The
Baseline system works OK.
Maybe a misconfiguration of some sort...?
Well, what? Like you said, the M+ SYSGEN is pretty simple and almost all
the questions, even w/o autoconfigure, take the default answers. Either
that, or there's something that's not supported by 4.3 (even though it says
that it is).
Actually I'd easily believe that it was a misconfiguration except for the
fact that ACF also hangs. That says to me that there's something about this
configuration that either isn't supported or doesn't actually work with M+
v4.3.
Or there's a bug in simh - that'd be ugly...
Bob
On 2012-07-11 16:24, Bob Armstrong wrote:
I'm always up for getting more RSX systems running. :-)
Did you see my message yesterday? Do you know why the ACF task hangs on
the 11/53 configuration?
Saw it. Have not had any time to ponder why... But it sounds weird. Doubly so that CON ONLINE (if I remember right) also hang. That would suggest a device not responding correctly. But this was in simh, so it's not really a case of broken hardware. Maybe a misconfiguration of some sort...? (Well, actually, probably...)
Johnny
