Sampsa Laine wrote:
Guys, just a heads up, had to "reboot" my whole flat - gas boiler lost the plot, can't reach the Reset button as it's behind about 2 metric tons of random crap. Long story short, licked off the electrical circuit instead - managed to knock out the whole flat. Epic. Fail.
Anyway, the rest of my machines have come up except for RHESUS, I need to get into my rack with a serial cable to get it up and am frankly too hung over to deal with this right now :)
Sampsa
Sounds like the kind of day I had yesterday. The deserver 90TL through which my entire vax/alpha/ia64 collection have their consoles routed has had an intermittent problem which I attributed to a dodgy power cable. Yesterday I bit the bullet and replaced the cable only to have an epic fail myself. Not even a power light. At least when I break decservers they have the courtesy of giving me a power light. Anyway, my spare decserver exhibits random and totally undesirable behaviour, so my collection is effectively offline for the most part until I find a replacement.
Anyone got a 90TL or 90M going spare?
Mark.
Guys, just a heads up, had to "reboot" my whole flat - gas boiler lost the plot, can't reach the Reset button as it's behind about 2 metric tons of random crap. Long story short, licked off the electrical circuit instead - managed to knock out the whole flat. Epic. Fail.
Anyway, the rest of my machines have come up except for RHESUS, I need to get into my rack with a serial cable to get it up and am frankly too hung over to deal with this right now :)
Sampsa
Ah, thought it was too good to be true - this is the server software on
VMS to support pathworks for mac. Remember - I saw pathworks and mac and
put 2 and 2 together and got 5 because I know no better.
Fun looking through old SPLs though...
--
I'd love a copy fwiw....
On Fri, Oct 23, 2009 at 5:24 PM, Mark Wickens <mark at wickensonline.co.uk> wrote:
I was transferring my 97 deccampus software from cdrom to hardrive and
noticed pathworks for mac. Is this something of interested, or are you
sorted...?
Mark.
--
Definitely interested - if you can put it up somewhere (HECnet or otherwise) I'd be very grateful to grab a copy.
Sampsa
On 23 Oct 2009, at 22:24, Mark Wickens wrote:
I was transferring my 97 deccampus software from cdrom to hardrive and
noticed pathworks for mac. Is this something of interested, or are you
sorted...?
Mark.
--
I was transferring my 97 deccampus software from cdrom to hardrive and
noticed pathworks for mac. Is this something of interested, or are you
sorted...?
Mark.
--
I'm currently transferring the domain name over to a provider who can
support complex DNS entries as required.
Why not host our own DNS? Several of us have DNS servers we could use, and then complexity wouldn't be an issue. MultiNet has a good DNS server I've used for years.
--Marc
Guys/gals
I'm currently transferring the domain name over to a provider who can
support complex DNS entries as required.
As for who hosts it, I'm easy. I'd like to keep it hosted on a OpenVMS
box if possible - it shows some faith in the technology. and I'd also
like to be in the situation where people can make updates to the website
via hecnet itself. This is why I was going down the WASD and ascii to
html.
Slowly slowly catchy monkey...
On Wed, Oct 21, 2009 at 10:36 AM, Steve Davidson <jeep at scshome.net> wrote:
I forgot about the SNA product for Windows NT 3.51/4.0. I have a couple of those kits hanging around. I don't have the SNA hardware but I do have the software.
Any takers? I certainly don't need them?
-----Original Message-----
From: owner-hecnet at Update.UU.SE on behalf of Jason Stevens
Sent: Wed 10/21/2009 10:33
To: hecnet at update.uu.se
Subject: Re: [HECnet] Next retro comms project?
Microsoft SNA server works pretty well for that, and it's easy to find...
Many moons ago I had TONNES of machines setup in that kind of manner, with
type 1 token ring to boot! (4mbit).
Even with Windows NT 3.51 & 4.0 it worked surprisingly well. (SNA Server 2.x
was waaay better then 3.x & 4.x IMHO). Anyways it was easy to connect the
tokenring to the FEP, but later on we got cisco routers that would do
translational bridging and local ack so we moved our SNA servers to
ethernet only.. Just remember to flip the bits of the FEP address as the
endian is different from ethernet to tokenring.
I've also done the netware SNA gateway, but it was living hell to setup... I
doubt I could get it to work again...
On Wed, Oct 21, 2009 at 10:26 AM, Fred <fcoffey at thrifty.misernet.net> wrote:
On Wed, 21 Oct 2009, Sampsa Laine wrote:
I thought SNA mostly ran on Token Ring or something?
I have an IBM PS/2 model (something) with both an MCA Token Ring card and
and MCA Ethernet - and I even have a passive Token Ring Mau! (and a cable,
somewhere ...)
Now if I could just find that gateway software. When I had access to a
real mainframe, all of the PC's went through a handful of these PS/2's via
Ethernet, and the PS/2's had token ring cards in them connected to a real
FEP.
Fred
Hello!
Steve, you have your taker. So how do we arrange this process?
----
Gregg C Levine gregg.drwho8 at gmail.com
"This signature was once found posting rude
messages in English in the Moscow subway."
Hi,
Sorry, I must have been asleep when suggesting : for a DECnet...
The # would be fine, I'll happily give my vote for that.
All my best,
G ran
Sampsa Laine wrote:
Ah yes, that old chestnut, scando-letters in 7 bit, had the same issues on BBSes back in the 80s/90s myself (I'm Finnish).
Ok, since the pipe symbol is in reality almost a letter, I suggest we go with #.
: might be used in the comments field to point to objects on HECNET (e.g. "..mail me at CHIMPY::SAMPSA") and people do use it and ; in writing quite frequently.
Shall we suggest to change the separator from | to # ?
Sampsa
On 22 Oct 2009, at 10:50, goran ahling wrote:
Hi,
just one humble little detail, thus a direct mail and not to the list... (Sorry I'm some days after in reading/commenting this storm of messages)
Once upon time, right about the time when those computers we are now "playing" with were new, there was US-ASCII, a 7 bit character encoding scheme, representing, amongst others, the 26 characters used in English writing. But in other countries, like here in Sweden, we use some other number of characters in our alpabet - swedish uses 29 letters, russian uses 33, for example.
So, a "local code" was develped, where some few of the rarely used tokens of the US-ASCII-scheme was instead used for those extra 6 letters (lower and upper case of 3 letters).
This was set in the ISO 646 standard, set 1975/12/01 - locally named SEN 85 02 00 Annex B
Here those letters are represented as:
0x7d }
0x7b {
0x7c |
0x5d ]
0x5b [
0x5c \
So, if I'm writing my given name (G ran) in that 7-bit coding, as we often do in those old systems, I'll write it G|ran. In an old system (might be old version RSX, might be RT-11 or migt be TOPS-10), I'd have to use that format.
These extra letters are quite common in daily writing and in names as they are wowels. I guess that the system descriptions you are trying to find a suitable format to encode most likely will contain names of owner/manager/..., end eventually also a city name as location. There are several citys inside Sweden containing these tokens (like \rebro, \regrund, \rkelljunga, G|teborg, Malm|, V}nersborg, Lax{, ...), not to mention several popular personal and family-names
Besides, there is an extra "tweak" to this.
If i write these letters in "DEC Multinational", almost identical (in this respect) to ISO-LATIN-1, but strip the 8:th bit (not uncommon, try a VT-100 terminal or equivalent "telnet" 7-bit "of the shelf"!), You would end up with getting edvEDV.
In those old dyas, the department secratary quite easilly managed to sort out post (from SUN microsystems) sent to mr. Gveran Eheling (my name is G ran hling), even though my dep. used DEC computers, that had working 8-bit...
So, to end up this E-mail:
Would possibly the : or the ; be a better separator than the | , as I really think these characters are more rarely used than the pipe!
An alternative might be the #
All my best,
G ran hling .EQ. G|ran ]hling .EQ. Goeran AAhling .NE. Goran Ahling
(Missconfigured printer might even print it as Gveran Ehling, but is it still NOT Goran Ahling, that would be another given name and another family name).
Sampsa Laine wrote:
Why? What would that accomplish that the pipe separated format doesn't except make things uglier? The reason I chose the pipe symbol is because this way we don't have to quote strings as people very seldomly use pipe symbols, but do use commas all the time...
On 21 Oct 2009, at 02:15, Steve Davidson wrote:
Let's try this again...
Any chance this could be in comma separated format? Put strings in
quotes if necessary.
-Steve
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE] On
Behalf Of Sampsa Laine
Sent: Tuesday, October 20, 2009 19:43
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] HECnet crawler and INFO.TXT
I've updated CHIMPY in the same format.
Sampsa
On 21 Oct 2009, at 00:26, Bob Armstrong wrote:
I took Sampsa's suggestion and put an INFO.TXT on CODA with a
machine
readable section at the end that contains information about the
local nodes.
I already wrote a little DCL script that crawls the HECnet and
collects all
the INFO.TXT files that it can find (so far there are eight,
counting mine)
and if enough people adopt this format I'll write another little
script to
parse out the node information.
The format is pretty straight forward - you can just type out
CODA::INFO.TXT and see for yourself.
Bob
