SEWALL@UCONNVM.BITNET (07/26/87)
Although I am getting better at figuring out how to send mail across
nets, and I've been getting some helpful instruction. This one has
me completely baffled, and Mr. Elton isn't the only person on
pro-sol.cts.com that I'd like to reach.
The problem seems to be how to get from bitnet to somewhere on UUCP
that recognizes pro-sol. Any help would be appreciated.
------------------------Message follows--------------------------
Received: from BRL-SMOKE.ARPA by wiscvm.wisc.edu ; Fri, 17 Jul 87 00:57:15 CDT
Received: from BRL-SMOKE.ARPA by SMOKE.brl.ARPA id aa11166; 16 Jul 87 6:57 EDT
Received: from amsaa.arpa by SMOKE.BRL.ARPA id aa10975; 16 Jul 87 6:52 EDT
Received: from seismo.CSS.GOV by AMSAA.AMSAA.ARPA id aa12486; 16 Jul 87 6:41 EDT
Received: from scubed.UUCP by seismo.CSS.GOV (5.54/1.14) with UUCP
id AA09185; Thu, 16 Jul 87 06:40:57 EDT
Received: by SCUBED.ARPA (4.12/5.20b)
id AA22962; Thu, 16 Jul 87 03:27:21 pdt
Received: by bigbang.UUCP (4.12/UUCP-Project/rel-1.0/11-09-86)
id AA09301; Thu, 16 Jul 87 02:57:15 pdt
Received: by crash.CTS.COM (5.54/UUCP-Project/rel-1.0/09-14-86)
id AA02760; Thu, 16 Jul 87 02:24:58 PDT
Reply-To: pnet01!pro-sol!pro-carolina!delton@seismo.CSS.GOV
Message-Id: <8707160924.AA02760@crash.CTS.COM>
Date: Wed, 15 Jul 87 18:00:50 EDT
From: Don Elton <scubed!pro-carolina!delton@seismo.CSS.GOV>
To: info-apple@AMSAA.arpa
Subject: ECP8 & ECP16
A note was posted asking for information about my ProDOS 8 and ProDOS 16 based
operating system shells. They are the Extended Command Processor 8 and 16.
You can get more info by replying to this note (to my address below) or in the
us mail at
Carolina System Software
3207 Berkeley Forest Drive
Columbia, SC 29209
Just to correct the note posted by Whitley.. ECP8 is $30, ECP16 is $40 and
includes ECP8.
UUCP: [ ihnp4 sdcsvax nosc ] !crash!pnet01!pro-sol!delton
ARPA: crash!pnet01!pro-sol!delton@nosc
INET: delton@pro-sol.cts.commdavis@pro-sol.UUCP (Morgan Davis) (07/26/87)
Surely, Mr. Sewall, some BITNET guru must know how to get from UCONNVM.BITNET into ARPA, and from there you can get to UUCP. The fact that you're able to post mail to the info-apple digest assumes that your site can reach into ARPANET. And if that's the case, UUCP is just another hop (no pun intended). I wish I knew the solution for you, but I don't. UUCP: [ ihnp4 cbosgd hplabs!hp-sdd sdcsvax nosc ] !crash!pnet01!pro-sol!mdavis ARPA: crash!pnet01!pro-sol!mdavis@nosc.mil INET: mdavis@pro-sol.CTS.COM
SEWALL@UCONNVM.BITNET (07/31/87)
Thank you for your thoughtful, and helpful message. As it happens I tried paths through seismo.css.gov and nosc.mil (I'd seen nosc before so I knew to send it to mil). Both came back with "host unknown." After I used henry's helpful path through uiuc, I took another look at that message and tried bigbang.uucp; it works and appears to involve fewer node to node transfers than uiuc. I've learned quite a lot about network paths as a result of that message and one or two others. I realized that one substantial source of difficulty is that I've wanted to respond to messages that were forwarded by a mailing list; so what I'm looking at is the path from sender to mailing list (which happens to be on arpa) rather than what I really want which is the path between the sender and me (on bitnet). That problem is about to become an order of magnitude worse as all bitnet subscribers have been switched to a redistribution by LISTSERV at NDSUVM1. While I fully understand that that is a far more efficient means of getting the mail out, a consequence is that almost ALL of the path information from the original message is deleted (if the "from" line isn't a legitimate address, there's virtually no way to figure out how to answer directly that I can see). Alas expecting help from the local network administrator is likely to be futile. The University of Connecticut, I fear, is xenophobic about the use of networks (the attitude is "the trouble with adding that service is that people will want to use it"). I am fortunate to be on the faculty, as there is a strong prejudice against letting students even find out that bitnet exists much less giving them access to it. The faculty is pretty much on its own as the "consultants" who are routinely available are students (even if they have some knowledge of the network, it's less than what I know already). It happens I do know who our local network administrator is, but he isn't what I'd describe as a visable (or even particularly available) presence. He'll probably say I should have sought him out; my response is I shouldn't have to go out of my way to find him (I sent him a message yesterday on another matter - no answer yet, but then it is mid-summer, he may not be in every day). I've found the existance of info-nets to be VERY helpful on occassions when I really get stuck (and I find I'm having trouble less and less often). However, I happened to find out about info-nets purely by a chance reading of a newslist item. Our mail system has a number of help files related to using the mailer executives themselves and a little about nodes on bitnet. No doubt additional documentation about network addresses (an explanation of "domains" written in language comprehensible in the liberal arts disciplines would be nice) and where to ask for help could and should be added.