On 28.6.2012 23:28, Rok Vidmar wrote:
I don't think that will work.
How about a bridge translating HECnet's area 1 to an
area unused in Italian net and translating Italian area 1
to an unused area in HECnet?
--
Regards, Rok
.
That's exactly what an ATG (Address Translation Gateway) does. Although I haven't used it over TCP/IP (Internet in this case). Maybe it would work if it is configured in either end of a GRE tunnel. Could be worth testing.
Kari
On Thu, Jun 28, 2012 at 6:26 AM, Tony Blews <tonyblews at gmail.com> wrote:
Ultrix not liking the year 2000 means you need to be preposterous, sadly.
Slightly related: while poking around in the shed looking for a spare kettle lead, I found a shrink-wrapped copy of SCO Unix on 5.25" disks and a copy of the "Unix for VMS Users" book. I've moved house 7 times in the last 20 years. Why do i keep this crap?
What version of SCO Unix...?
I don't think that will work.
How about a bridge translating HECnet's area 1 to an
area unused in Italian net and translating Italian area 1
to an unused area in HECnet?
--
Regards, Rok
?REDO FROM START always annoyed me on the PET. It just made no sense given the context.
On Thu, Jun 28, 2012 at 6:59 PM, Marc Chametzky <marc at bluevine.net> wrote:
When I was much younger (back in high school), I used a PDP-11/03 running RSTS and MU-BASIC (v1). It used three character error codes.
So, while in BASIC, we typed in:
WHAT DID YOU DO LAST SUNDAY?
and it responded:
?SYN
That was terribly amusing to us teenagers.
--Marc
When I was much younger (back in high school), I used a PDP-11/03 running RSTS and MU-BASIC (v1). It used three character error codes.
So, while in BASIC, we typed in:
WHAT DID YOU DO LAST SUNDAY?
and it responded:
?SYN
That was terribly amusing to us teenagers.
--Marc
On 2012-06-28 16:48, Paul_Koning at Dell.com wrote:
Various operating systems have amusing messages. One of the fun ones in RSTS (unless you got it) was what it would print if the program was killed due to an addressing error or parity error or the like.
"Program lost -- sorry"
Indeed. There are several in BP2:
25 ?Disk pack needs 'CLEANing'
66 ?Missing special feature
87 ?Expression too complicated
103 ?Program lost-Sorry
108 ?End of statement not seen
109 ?What?
136 ?Illegal or illogical access
174 ?File expiration date unexpired
236 ?TIME limit exceeded
239 ?Arrays must be square
Just to pick a few...
This one is "classic" in RSX:
.err -69
000273 (-69): %I/O-F-IE.NFW, path lost to partner
Johnny
paul
On Jun 28, 2012, at 5:31 AM, Tony Blews wrote:
Hi.
Has anyone had any success emulating Ultrix with DECnet under SimH?
I managed to find a copy of 4.0, and the "tape" claimed that it was installing DECnet, but I couldn't find any evidence of it anywhere on the system.
I may just be being stupid (this is not unknown).
An aside: You've got to love an OS that gives you error messages containing the word "preposterous"!
Tony.
--
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
Various operating systems have amusing messages. One of the fun ones in RSTS (unless you got it) was what it would print if the program was killed due to an addressing error or parity error or the like.
"Program lost -- sorry"
paul
On Jun 28, 2012, at 5:31 AM, Tony Blews wrote:
Hi.
Has anyone had any success emulating Ultrix with DECnet under SimH?
I managed to find a copy of 4.0, and the "tape" claimed that it was installing DECnet, but I couldn't find any evidence of it anywhere on the system.
I may just be being stupid (this is not unknown).
An aside: You've got to love an OS that gives you error messages containing the word "preposterous"!
Tony.
On 2012-06-28 15:45, Peter Coghlan wrote:
It is triggered by the setting of the todr at boot time. In principle,
it picks the mtime of / to get a rough estimate of what time it is at
boot time. It's done in inittodr, which is called from ufs_mount.
inittodr checks if the date is before 1975, and if it is, the it's
preposterous.
I've booted both VMS and OSF/1 or Tru64 or Digital Unix or whatever it is
called this week on the same Alphaserver 2100. The oses use the TOY clock
differently unfortunately.
When VMS notices that the time is "preposterous" is prompts me to enter the
correct date and time before allowing the machine to boot. Unix gives me the
"preposterous" message and advises me to fix the clock later while going on to
boot and put "preposterous" dates on various files :-( The VMS approach can
also be somewhat inconvenient when trying to do "lights out" operations.
A pity that a standard way of using the TOY clock could not have been agreed
for all the oses supported on a particular processor.
Note that Ultrix does not output the "preposterous" error message for any value in the todr. It's based on a date in the file system.
However, I agree that it's a shame that Ultrix and VMS is not compatible in their use of the todr. However, it would be extremely hard to do, since VMS keeps the todr in local time, while Ultrix keeps it in UTC.
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
On 2012-06-28 15:57, Sampsa Laine wrote:
Guys,
Do you think it would be possible to have a host that would somehow bridge HECnet with the Italian DECNET and then use the "poor mans routing" (i.e. HOST1::HOST2::<object) to pass e.g. mail across our two networks?
I have no idea how this works in practice, but just throwing the idea out there. From what I understood is that the Italians use many of the same nets / nodes as us (mainly network 1) which would make a network merger impractical.
I don't think that will work.
PMR is used to be able to forward traffic to a node, which you either do not know about, or else can't address (for example a Phase V address).
There needs to live a machine in the middle with connections both ways.
This means that you cannot have machines with conflicting node numbers available to that machine in the middle, but this is exactly what will happen with the italian network. :-(
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
On 28 Jun 2012, at 14:45, Peter Coghlan <HECNET at beyondthepale.ie> wrote:
I've booted both VMS and OSF/1 or Tru64 or Digital Unix or whatever it is
called this week on the same Alphaserver 2100. The oses use the TOY clock
differently unfortunately.
When VMS notices that the time is "preposterous" is prompts me to enter the
correct date and time before allowing the machine to boot. Unix gives me the
"preposterous" message and advises me to fix the clock later while going on to
boot and put "preposterous" dates on various files :-( The VMS approach can
also be somewhat inconvenient when trying to do "lights out" operations.
A pity that a standard way of using the TOY clock could not have been agreed
for all the oses supported on a particular processor.
The DEC 'Enter date and time DD-MMM-YY (later YYYY) HH:MM' prompt
pre-dates VMS, it is also present in several PDP-11 OSs (because many
PDPs didn't have a TOY clock). I think it was DEC's defacto way of
handling the date issue that got handed down to VMS.
--
Mark Benson
http://markbenson.org/bloghttp://twitter.com/MDBenson
