Groups | Search | Server Info | Login | Register
Groups > alt.sys.pdp10 > #9845
| From | jayjwa <jayjwa@atr2.ath.cx.invalid> |
|---|---|
| Newsgroups | alt.sys.pdp10 |
| Subject | Re: TOPS-10 networking in modern time |
| Date | 2026-01-02 13:27 -0500 |
| Organization | atr2net 2026 |
| Message-ID | <87tsx3hntd.fsf@atr2.ath.cx> (permalink) |
| References | (9 earlier) <10iuivt$17bgf$1@dont-email.me> <87qzsblwm1.fsf@atr2.ath.cx> <10j1tq7$27kgq$1@dont-email.me> <87o6nefu4h.fsf@atr2.ath.cx> <10j6b3k$3l0qj$1@dont-email.me> |
"G." <nan6328@iperbole.invalid> writes:
> Maybe Simh assumes address 700 and therefore doing I/O at address 740
> causes an exception because there is no device at that address.
I tried both but it doesn't seem to matter, at least here. Yesterday I
built a new KL (witout any changes) and a new KS. Both see the "TO"
status and look like they have issues with ORION. If you leave OPR>, or
enter certain places like CONFIG> it hangs ORION. No more messages after
that and no shutdown (properly) either. You can, however, attach and
kill everything and .initia system and get ORION back -
somewhat. There's no SHOW HARDWARE values in KL at all - KS there is.
> Other places to look for this kind of information would be the HECnet
> and/or Simh mailing lists. In fact in the HECnet mailing list I found
> the following, written by me (!) in November 2021.
Great sources there. It's hard to find answers to questions for systems
this old. Everytime I search for "tops-10" I get some Top Ten list for
something completely unrelated.
> The fun fact is that I never patched mine for the 2021 bug and yet it
> works flawlessly. I wonder if that patch was only needed for systems
> that were actually up when that bug got triggered. Mine was not and
> thus I didn't need it (and in fact didn't know about it). Whatever, I
> just patched it.
Maybe KLH10 handles it better/differently. If you do attach the
pdp10-kl/ks interface for the network on an unpatched system (SIMH) it
does explode.
> Speaking about patches, I'm wondering if maybe changing stuff like
> memory size may have impacted something else, thus causing that
> erratic behavior.
I was thinking of that.
> You seem expert enough that you could consider doing your own
> installation from scratch. It's not difficult, just takes some
> time. :)
That thought crossed my mind. Maybe after I learn more about the build
system, compilers, and some more user commands. I have about a year or
more of TOPS-20 but that doesn't always translate to TOPS-10 experience.
> You just need to use any 7.04 KL bootable tape but the official one
> because it was faulty/buggy.
!!!
> NODNAM doesn't have to (must not?) be preceded by LOGIN and starts MX
> on its own after having loaded the node database, possibly because MX
> so requires. Maybe it was done to avoid some conflict. Whatever,
> NODNAM checks that MX is not already running to avoid having more than
> one.
That might be why I was seeing two MX running. I'll try the above today.
> Just out of curiosity, does SET KSYS NOW in OPR work? It's a command
> you give to OPR before shutting down. You seem to have lots of
> problems like I had when I started with some pre-made installation
> about 20 (!) years ago. Quite probably not the same as yours but it
> definitely reminds me of something...
Yes, you can use OPR and it responds...unless you ENTER CONFIG or leave
and come back. Then ORION seems to hang.
Maybe I'll just take what I have now. Mail works, DECnet works (just
real slow), I can kermit in/out stuff and I built my first BCPL
program. I'll look more into REACT today for user temples so maybe one
day I can give out accounts (they'd need ip6 to reach the TTY lines
though).
--
PGP Key ID: 781C A3E2 C6ED 70A6 B356 7AF5 B510 542E D460 5CAE
"The Internet should always be the Wild West!"
Back to alt.sys.pdp10 | Previous | Next — Previous in thread | Next in thread | Find similar
TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-14 20:55 -0500
Re: TOPS-10 networking in modern time Rich Alderson <news@alderson.users.panix.com> - 2025-12-14 21:23 -0500
Re: TOPS-10 networking in modern time Al Kossow <aek@bitsavers.org> - 2025-12-14 18:34 -0800
Re: TOPS-10 networking in modern time drb@ihatespam.msu.edu (Dennis Boone) - 2025-12-15 03:04 +0000
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-15 14:34 -0500
Re: TOPS-10 networking in modern time Rich Alderson <news@alderson.users.panix.com> - 2025-12-15 17:03 -0500
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-16 11:35 -0500
Re: TOPS-10 networking in modern time Rich Alderson <news@alderson.users.panix.com> - 2025-12-16 22:12 -0500
Re: TOPS-10 networking in modern time Johnny Billquist <bqt@softjar.se> - 2025-12-17 10:31 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-17 11:06 -0500
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-17 10:56 -0500
Re: TOPS-10 networking in modern time Johnny Billquist <bqt@softjar.se> - 2025-12-20 13:27 +0100
Re: TOPS-10 networking in modern time Lars Brinkhoff <lars.spam@nocrew.org> - 2025-12-20 13:23 +0000
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-20 11:59 -0500
Re: TOPS-10 networking in modern time Johnny Billquist <bqt@softjar.se> - 2025-12-25 11:35 +0100
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-29 17:59 +0100
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-28 10:47 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-28 18:21 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-29 11:07 +0100
Re: TOPS-10 networking in modern time Johnny Billquist <bqt@softjar.se> - 2025-12-29 13:20 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-29 12:22 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-29 20:43 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-30 11:57 -0500
Re: TOPS-10 networking in modern time Johnny Billquist <bqt@softjar.se> - 2025-12-31 15:21 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-31 12:33 -0500
Re: TOPS-10 networking in modern time Johnny Billquist <bqt@softjar.se> - 2025-12-31 15:20 +0100
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-29 17:59 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-29 12:05 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-29 19:58 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-30 12:15 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2025-12-31 02:21 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2025-12-31 12:17 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2026-01-01 18:32 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-02 13:27 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2026-01-05 13:37 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-05 12:52 -0500
Re: TOPS-10 networking in modern time "G." <nan6328@iperbole.invalid> - 2026-01-06 01:37 +0100
Re: TOPS-10 networking in modern time jayjwa <jayjwa@atr2.ath.cx.invalid> - 2026-01-06 12:18 -0500
csiph-web