You've specified smtp% as a prefix for the internet email address. Mail llooks for sys$share:smtp_mailshr.exe and doesn't find it there.
- do a dir sys$share:*mailshr.exe and see what files are there. Perhaps you'll find another one (e.g. IP_mailshr.exe)
- if the file is there, then it might not be installed (mc install and use help to run a list of all installed programs)
- the only logical name involved is. sys$share and if that wouldn't exist then mail problems would be low on your problems list ....
-----Original Message-----
From: Sampsa Laine <sampsa at mac.com>
Sender: owner-hecnet at Update.UU.SE
Date: Sun, 30 Oct 2011 21:01:50
To: <hecnet at Update.UU.SE>
Reply-To: hecnet at Update.UU.SESubject: [HECnet] MULTINET and SMTP mail
I've tried to configure SMTP on MULTINET and am stuck.
Here's the error:
--- SNIP ---
MAIL> send
To: smtp%"sampsa at mac.com"
%MAIL-E-ERRACTRNS, error activating transport SMTP
%LIB-E-ACTIMAGE, error activating image CHIMPY$DQA1:[SYS0.SYSCOMMON.][SYSLIB]SMTP_MAILSHR.EXE;
-RMS-E-FNF, file not found
--- SNIP ---
Here's the settings:
--- SNIP ---
{CHIMPY$} multinet config/mail
Process Software Mail Configuration Utility V5.3(28)
[Reading in configuration from MULTINET_ROOT:[MULTINET]START_SMTP_LOCAL.COM]
[Reading in configuration from MULTINET_COMMON_ROOT:[MULTINET]START_SMTP.COM]
MAIL-CONFIG>show
SMTP host name: none (will use IP host name)
Host name alias file: none
Postmaster userid: SAMPSA
Forwarder: 192.168.77.202
Send all REMOTE mail to forwarder: TRUE
Send all LOCAL mail to forwarder: FALSE
DECnet mail domain: none
Failed local mail will be returned to sender.
Retry Interval: 30 minutes
Return Interval: 96 hours
VMS Mail REPLY control: REPLY-TO
VMS Mail header control: MAJOR
Use RFC822 To: header as VMS Mail To: TRUE
Lowercase username on outgoing VMS Mail: TRUE
Disallow user Reply-To's: FALSE
Delivery Receipts enabled: FALSE
PSImail delivery disabled: FALSE
Include Resent Headers on VMS MAIL forwards: TRUE
Alias file name: MULTINET:SMTP_ALIASES.
SEND broadcast class: 16
Start queue manager: TRUE
Number of SMTP server queues:
Node name Count
--------- -----
(default) 1
No queue groupings.
Start RFC 2789 MIB agent: FALSE
--- SNIP ---
MAIL> send
To: smtp%"sampsa at mac.com"
%MAIL-E-ERRACTRNS, error activating transport SMTP
%LIB-E-ACTIMAGE, error activating image CHIMPY$DQA1:[SYS0.SYSCOMMON.][SYSLIB]SMTP_MAILSHR.EXE;
-RMS-E-FNF, file not found
MultiNet's SMTP components haven't been started. You're missing the MAIL$PROTOCOL_SMTP logical that would point to their "MAILSHR" image. Perhaps running @MULTINET:START_SMTP might be sufficient, but I don't know where that logical gets set. It's possible that running the START_MULTINET.COM procedure might be necessary.
--Marc
I've tried to configure SMTP on MULTINET and am stuck.
Here's the error:
--- SNIP ---
MAIL> send
To: smtp%"sampsa at mac.com"
%MAIL-E-ERRACTRNS, error activating transport SMTP
%LIB-E-ACTIMAGE, error activating image CHIMPY$DQA1:[SYS0.SYSCOMMON.][SYSLIB]SMTP_MAILSHR.EXE;
-RMS-E-FNF, file not found
--- SNIP ---
Here's the settings:
--- SNIP ---
{CHIMPY$} multinet config/mail
Process Software Mail Configuration Utility V5.3(28)
[Reading in configuration from MULTINET_ROOT:[MULTINET]START_SMTP_LOCAL.COM]
[Reading in configuration from MULTINET_COMMON_ROOT:[MULTINET]START_SMTP.COM]
MAIL-CONFIG>show
SMTP host name: none (will use IP host name)
Host name alias file: none
Postmaster userid: SAMPSA
Forwarder: 192.168.77.202
Send all REMOTE mail to forwarder: TRUE
Send all LOCAL mail to forwarder: FALSE
DECnet mail domain: none
Failed local mail will be returned to sender.
Retry Interval: 30 minutes
Return Interval: 96 hours
VMS Mail REPLY control: REPLY-TO
VMS Mail header control: MAJOR
Use RFC822 To: header as VMS Mail To: TRUE
Lowercase username on outgoing VMS Mail: TRUE
Disallow user Reply-To's: FALSE
Delivery Receipts enabled: FALSE
PSImail delivery disabled: FALSE
Include Resent Headers on VMS MAIL forwards: TRUE
Alias file name: MULTINET:SMTP_ALIASES.
SEND broadcast class: 16
Start queue manager: TRUE
Number of SMTP server queues:
Node name Count
--------- -----
(default) 1
No queue groupings.
Start RFC 2789 MIB agent: FALSE
--- SNIP ---
Heck! I'm in.
A community is all about the members, I hope I can contribute :)
/P
On 10/30/2011 02:00 PM, Mark Benson wrote:
Hi,
A while back myself and a couple of other HECnet list members discussed here a need for an alternative discussion forum for some of the less DECnet-related topics we (and especially I) had raised recently. There was some talk about a Notes-based list but talk about that seemed to fade, so I considered starting another e-mail list, and having attended DEC Legacy I was sure there would be some uptake. So I have started out on something I hope will become big.
I am announcing the launch of the first small step in what will be a bigger project. As of today http://DECtec.info is officially live.
My first step is to get a simple (and it is simple) website up and running and start a mailing list to provide that alternative forum for discussion. The list is active and you can subscribe right away. Details and guidelines (pretty-much the usual caveats) are at: http://DECtec.info/mailing-list.html
Now I am aware there are newsgroups and mailing lists out there already that are well established, such as comp.os.vms, comp.sys.dec, various alt.sys.* lists, CCTalk and others, but I have two issues. Stuff on 'Usenet' is not as easy to get at as it used to be. Sure there's Google Groups for a lot of it but it's frankly horrible. Secondly, because a lot of it concentrates on specific systems it gets a bit spread out. CCTalk/CCTech also is a great, great list but for someone like me who is only after DEC related info it's got a massive signal to noise ratio problem.
I am aware some people just join all of them and I'm pretty sure those people are probably crying into there cornflakes right now muttering 'not *another* list/site/so-called-community', but I want DECtec.info to be different in a few ways:
- More relaxed atmosphere. DEC Legacy was a blast, just a bunch of vary various, enthusiastic and knowledgable people in one place. I learnt so much there I wanted to keep it going somewhere where we could constantly tap on each others knowledge about the many and various aspects of DEC systems, OS, software and crazy stories. Yes the list will be moderated as any list has to be but I'm not a draconian dictator, banter (as long as it's friendly) and some slight wandering us fine, sometimes it even makes for a better atmosphere.
- Build a place to store knowledge. A mailing list is a great start and the archives over time will fill with plenty of knowledge, I am sure. But I don't want to stop there. I want to build a central knowledge base. I'm new to DEC and to it's ins and outs. I found it incredibly hard to get a foothold in the community. That bugs me - the number of people like me who are enthusiastic and interested have, for example, told me it's really hard to get a VMS license. It's not, it's really not, what's hard is finding someone who can tell you WHERE to get one, and keep that information up to date. Some of the knowledge is out there on the net but half of it is in people's heads and the other half is out of date. Furthermore, because a lot of certainly VMS-related stuff is still applicable to commercial interests there are walls and hurdles for Hobbyists that slow down or obfuscate the transfer of knowledge that isn't commercially sensitive but for some reason doesn't seem to be 'out there' either.
I had a simple idea. Build a Wiki. Every time you learn something new, or teach someone something they didn't know, copy and paste it to the Wiki. Even if you don't format it or type it out in pretty Wiki code it doesn't matter, the information is there. I can (or I can get volunteers to if it gets too much) do the fancy stuff to make it look pretty.
- Empower events. DEC Legacy was a great event. We should do it again, Mark says we probably will, and I want to support that. What I think was slightly lacking was an idea forum for the event. Sure it was pretty informal but it doesn't stop us talking ahead of the event and maybe planning out some stuff or even just establishing who's bringing what machines, and who needs help with what.
So I hope some people here feel inspired. I know it's a big idea and I'm a small workforce, but we all have to start somewhere and I start here.
Hi,
A while back myself and a couple of other HECnet list members discussed here a need for an alternative discussion forum for some of the less DECnet-related topics we (and especially I) had raised recently. There was some talk about a Notes-based list but talk about that seemed to fade, so I considered starting another e-mail list, and having attended DEC Legacy I was sure there would be some uptake. So I have started out on something I hope will become big.
I am announcing the launch of the first small step in what will be a bigger project. As of today http://DECtec.info is officially live.
My first step is to get a simple (and it is simple) website up and running and start a mailing list to provide that alternative forum for discussion. The list is active and you can subscribe right away. Details and guidelines (pretty-much the usual caveats) are at: http://DECtec.info/mailing-list.html
Now I am aware there are newsgroups and mailing lists out there already that are well established, such as comp.os.vms, comp.sys.dec, various alt.sys.* lists, CCTalk and others, but I have two issues. Stuff on 'Usenet' is not as easy to get at as it used to be. Sure there's Google Groups for a lot of it but it's frankly horrible. Secondly, because a lot of it concentrates on specific systems it gets a bit spread out. CCTalk/CCTech also is a great, great list but for someone like me who is only after DEC related info it's got a massive signal to noise ratio problem.
I am aware some people just join all of them and I'm pretty sure those people are probably crying into there cornflakes right now muttering 'not *another* list/site/so-called-community', but I want DECtec.info to be different in a few ways:
- More relaxed atmosphere. DEC Legacy was a blast, just a bunch of vary various, enthusiastic and knowledgable people in one place. I learnt so much there I wanted to keep it going somewhere where we could constantly tap on each others knowledge about the many and various aspects of DEC systems, OS, software and crazy stories. Yes the list will be moderated as any list has to be but I'm not a draconian dictator, banter (as long as it's friendly) and some slight wandering us fine, sometimes it even makes for a better atmosphere.
- Build a place to store knowledge. A mailing list is a great start and the archives over time will fill with plenty of knowledge, I am sure. But I don't want to stop there. I want to build a central knowledge base. I'm new to DEC and to it's ins and outs. I found it incredibly hard to get a foothold in the community. That bugs me - the number of people like me who are enthusiastic and interested have, for example, told me it's really hard to get a VMS license. It's not, it's really not, what's hard is finding someone who can tell you WHERE to get one, and keep that information up to date. Some of the knowledge is out there on the net but half of it is in people's heads and the other half is out of date. Furthermore, because a lot of certainly VMS-related stuff is still applicable to commercial interests there are walls and hurdles for Hobbyists that slow down or obfuscate the transfer of knowledge that isn't commercially sensitive but for some reason doesn't seem to be 'out there' either.
I had a simple idea. Build a Wiki. Every time you learn something new, or teach someone something they didn't know, copy and paste it to the Wiki. Even if you don't format it or type it out in pretty Wiki code it doesn't matter, the information is there. I can (or I can get volunteers to if it gets too much) do the fancy stuff to make it look pretty.
- Empower events. DEC Legacy was a great event. We should do it again, Mark says we probably will, and I want to support that. What I think was slightly lacking was an idea forum for the event. Sure it was pretty informal but it doesn't stop us talking ahead of the event and maybe planning out some stuff or even just establishing who's bringing what machines, and who needs help with what.
So I hope some people here feel inspired. I know it's a big idea and I'm a small workforce, but we all have to start somewhere and I start here.
--
Mark Benson
http://DECtec.info
Twitter: @DECtecInfo
Online Resource & Mailing List for DEC Enthusiasts.
We went through this back in September...
An update: The Micron part number is correct also. For a 512MB DIMM you want a MT18LSDT6472JG-10Exx. The JG indicates the 200-pin DIMM so that's significant as is the -10Exx which specifies the 2CL CAS latency.
John H. Reinhardt
On 9/24/11 11:52 AM, John H. Reinhardt wrote:
You have a DS10 so you don't have to be quite as picky. The DS10L needs a shorter DIMM board. The old DEC/Compaq part number for memory was MS310-xA where A=64MB, B=128MB, C=256MB, D=512MB, E=1GB. This is total size. Each kit is 2 DIMM boards so the largest is a set of 2 512MB DIMMS.
The trick about the DS10/DS10/DS20/ES40 memory is that it's on 200-pin DIMMs. And if you Google or search in Ebay you'll get a ton of hits because it's a common notebook memory size for SO-DIMMs. These will not fit. Be wary. IIRC the basic spec is 200-pin, PC100, ECC but I can't remember if they're buffered or un-buffered (registered or not).
Okay, I pulled a DIMM out of my DS10L and it's DEC part # 20-01ESA-08 and specifically a Samsung M378S6450ATQ-C1H
Googling this tells me it's a 200-pin, PC100, Synchronous, CL2, ECC DIMM.
I found one hit on the US Ebay for memory fitting this specification, however, the picture they have with the listing is for a Micron DIMM board and the part number decodes to a 186-pin DIMM. So either the picture is wrong, or generic or the listing is incorrect. In either case, beware. Alpha Memory 256MB 200pin Synch DIMM100MHz CL2 ECC
Your best bet is going to be searching on MS310-EA or 20-01ESA-08 and on the US EBay it looks like the best deal is
1GB (2x512MB) PC100 ECC Registered ECC 200pin Memory for $59.95 US.
It's an oddball memory and tough to find in the generic market. Good luck.
Cheers,
John H. Reinhardt
On 9/21/11 2:21 PM, Sampsa Laine wrote:
Thanks for that - but what TYPE (MHz etc) are they, exactly? I was going to just buy generic RAM.
Sampsa
On 21 Sep 2011, at 16:39, hvlems at zonnet.nl wrote:
The DS10 uses the same kind of memory as the DS20(E) and the ES40. Memory must be installed in pairs and the maximum size for 1 memory board is 512 MB.
Have a look at eBay Sampsa. Check the systems and options guide for the DS10 memory part numbers on the HP site
Hans
------Origineel bericht------
Van: Sampsa Laine
Afzender: owner-hecnet at Update.UU.SE
Aan: hecnet at Update.UU.SE
Beantwoorden: hecnet at Update.UU.SE
Onderwerp: [HECnet] Noob questions #42: RAM for DS10
Verzonden: 21 september 2011 14:45
Guys, what kind of DIMMs should I be looking for on ebay to add ram to my DS10?
I'd like the largest possible ones so that I can fill it up to 2 GB.
Sampsa
On 10/26/11 5:26 PM, Sampsa Laine wrote:
So i've been (with Steve D's) help researching upgrading the RAM on my DS10.
The HP part number 3X-MS310-EA. From what I can gather, this is a kit of 200 pin, 100 mhz 512 MB set of DIMMs.
Would generic RAM do instead?* If so, what spec? Anyone got pointers to a site that sells them (pref. in UK or EU), or maybe wants to unload some on me?
Sampsa
* The prices are pretty crazy high, 100-150 USD or so.
I don't know about the DS10, but in my PWS 433au, and my XP1000's I just used generic server RAM. The RAM in the PWS was pretty far out of spec, and I never had a problem. Same thing with my AlphaStation 200's and DEC 3000/300LX. As long as you can get parity RAM that fits, and is close to spec, odds are pretty good it will work.
Then there is my **** Alphastation 500/333 I bought from Compaq with only 96Mb of RAM. Over a decade later, it still only has 96Mb of RAM. I got a good deal on the PWS 433au, it and the RAM were cheaper than what it would have cost to get the AS 500/333 up to a usable amount of RAM. Who me, bitter? :-(
Zane
At 10:26 PM +0100 10/26/11, Sampsa Laine wrote:
So i've been (with Steve D's) help researching upgrading the RAM on my DS10.
The HP part number 3X-MS310-EA. From what I can gather, this is a kit of 200 pin, 100 mhz 512 MB set of DIMMs.
Would generic RAM do instead?* If so, what spec? Anyone got pointers to a site that sells them (pref. in UK or EU), or maybe wants to unload some on me?
Sampsa
* The prices are pretty crazy high, 100-150 USD or so.
--
| Zane H. Healy | UNIX Systems Administrator |
| healyzh at aracnet.com | OpenVMS Enthusiast |
| | Photographer |
+----------------------------------+----------------------------+
| My flickr Photostream |
| http://www.flickr.com/photos/33848088 at N03/ |
