On 22 Dec 2012, at 02:36, G. <gerry77 at mail.com> wrote:
On Sat, 22 Dec 2012 01:14:27 -0500, you wrote:
% DSK:MONGEN.MIC will not be written
% File DSK:MONGEN.MIC already exists
This is self explanatory: MONGEN will not overwrite MONGEN.MIC if it's already
there... I think it's done to avoid losing config data. :)
.do monbld
?MICCOF Cannot open file MIC:MONBLD.MIC - in "DO" command
Have you created MONBLD.MIC as I wrote? It's a non standard file "invented" by
me and should contain all those commands I've listed in my other message. :)
Just re-read your message and noticed my error. ;)
Now i'm trying to figure out how to use the TOPS-10 editor. ;)
I'm used to EDT instead of TECO!
HTH,
G.
On Sat, 22 Dec 2012 01:14:27 -0500, you wrote:
% DSK:MONGEN.MIC will not be written
% File DSK:MONGEN.MIC already exists
This is self explanatory: MONGEN will not overwrite MONGEN.MIC if it's already
there... I think it's done to avoid losing config data. :)
.do monbld
?MICCOF Cannot open file MIC:MONBLD.MIC - in "DO" command
Have you created MONBLD.MIC as I wrote? It's a non standard file "invented" by
me and should contain all those commands I've listed in my other message. :)
HTH,
G.
On 22 Dec 2012, at 01:14, Cory Smelosky <b4 at gewt.net> wrote:
On 22 Dec 2012, at 01:03, Cory Smelosky <b4 at gewt.net> wrote:
On 22 Dec 2012, at 00:48, G. <gerry77 at mail.com> wrote:
On Fri, 21 Dec 2012 18:50:05 -0500, you wrote:
Hey everyone,
I'm having a bit of trouble configuring DECnet on TOPS-10 in klh20.
[...]
As you can see, I changed the configuration to 9.10, yet it changes the mac
address from 9.10 back to that of 24.172.
Where else do I need to reconfigure this? ;)
Well, to be honest I didn't even remember the ONCE option to reconfigure the
network (are those settings sticky over reboots?)... Anyway, whenever I had to
reconfigure DECnet I've simply rebuilt the monitor with a new set of custom
parameters: once setup, the process is straightforward.
Monitor sources usually are in [10,7,MON] so you just go there with PATH or
SETSRC, then you have to run MONGEN and answer all its questions, notably the
one that asks if it has to write a MONGEN.MIC file (say yes). This produces a
tailored .MIC file with all your answers, which you can modify whenever you
need to change something, and two parameter files (SYSCNF.MAC and F.MAC).
Then I suggest you put something like what follows in a .MIC file, I've called
mine MONBLD.MIC:
.DAYTIME
.COMPILE/COMPILE F,S
.COMPILE/COMPILE DEVPRM,DTEPRM,NETPRM,D36PAR
.COMPILE/COMPILE SYSCNF+<COMMON,COMDEV,COMMOD>
.R LINK
*SYSTEM/SAVE/NOINITIAL/HASH:13K = /LOCALS -
*COMMON,COMDEV,COMMOD,REL:TOPS10/SEARCH-
*/PATCH:200/COUNTERS/GO
.DIRECT/DETAIL SYSTEM.EXE
.DAYTIME
So, whenever you need to rebuild your monitor with different parameters, you
can just edit your MONGEN.MIC (or a copy of) and then at the dot prompt simply
type DO MONGEN followed by DO MONBLD (or whatever names you have used). On a
modern system the whole process takes no more that 1-2 minutes. :)
The bunch of commands above comes from DEC manuals (I'm not so expert); note
that between /LOCALS and the hypen there must be a space, I do not know why
but manuals warn about this. You must have TOPS10.REL somewhere on your disk
(usually in REL:) and that place has to be clearly specified just before
/SEARCH. TOPS10.REL is the library file that contains almost every monitor
module. When MONBLD finished its work, you'll have a new SYSTEM.EXE in the
current directory: you can then rename and move it as you please.
If you need to modify standard modules (such as CLOCK1.MAC to implement KLH10
idle detection) the procedure is not much more complex than this.
Please excuse me if I wrote things you already know!
HTH, :)
G.
Thank you! I've not played much with TOPS-10, but you've helped a lot.
I learn a lot about DEC OSes by tuning them oftentimes incorrectly. ;)
Such as:
% DSK:MONGEN.MIC will not be written
% File DSK:MONGEN.MIC already exists
And then:
.do monbld
?MICCOF Cannot open file MIC:MONBLD.MIC - in "DO" command
OH! I GET IT NOW!
On 22 Dec 2012, at 01:03, Cory Smelosky <b4 at gewt.net> wrote:
On 22 Dec 2012, at 00:48, G. <gerry77 at mail.com> wrote:
On Fri, 21 Dec 2012 18:50:05 -0500, you wrote:
Hey everyone,
I'm having a bit of trouble configuring DECnet on TOPS-10 in klh20.
[...]
As you can see, I changed the configuration to 9.10, yet it changes the mac
address from 9.10 back to that of 24.172.
Where else do I need to reconfigure this? ;)
Well, to be honest I didn't even remember the ONCE option to reconfigure the
network (are those settings sticky over reboots?)... Anyway, whenever I had to
reconfigure DECnet I've simply rebuilt the monitor with a new set of custom
parameters: once setup, the process is straightforward.
Monitor sources usually are in [10,7,MON] so you just go there with PATH or
SETSRC, then you have to run MONGEN and answer all its questions, notably the
one that asks if it has to write a MONGEN.MIC file (say yes). This produces a
tailored .MIC file with all your answers, which you can modify whenever you
need to change something, and two parameter files (SYSCNF.MAC and F.MAC).
Then I suggest you put something like what follows in a .MIC file, I've called
mine MONBLD.MIC:
.DAYTIME
.COMPILE/COMPILE F,S
.COMPILE/COMPILE DEVPRM,DTEPRM,NETPRM,D36PAR
.COMPILE/COMPILE SYSCNF+<COMMON,COMDEV,COMMOD>
.R LINK
*SYSTEM/SAVE/NOINITIAL/HASH:13K = /LOCALS -
*COMMON,COMDEV,COMMOD,REL:TOPS10/SEARCH-
*/PATCH:200/COUNTERS/GO
.DIRECT/DETAIL SYSTEM.EXE
.DAYTIME
So, whenever you need to rebuild your monitor with different parameters, you
can just edit your MONGEN.MIC (or a copy of) and then at the dot prompt simply
type DO MONGEN followed by DO MONBLD (or whatever names you have used). On a
modern system the whole process takes no more that 1-2 minutes. :)
The bunch of commands above comes from DEC manuals (I'm not so expert); note
that between /LOCALS and the hypen there must be a space, I do not know why
but manuals warn about this. You must have TOPS10.REL somewhere on your disk
(usually in REL:) and that place has to be clearly specified just before
/SEARCH. TOPS10.REL is the library file that contains almost every monitor
module. When MONBLD finished its work, you'll have a new SYSTEM.EXE in the
current directory: you can then rename and move it as you please.
If you need to modify standard modules (such as CLOCK1.MAC to implement KLH10
idle detection) the procedure is not much more complex than this.
Please excuse me if I wrote things you already know!
HTH, :)
G.
Thank you! I've not played much with TOPS-10, but you've helped a lot.
I learn a lot about DEC OSes by tuning them oftentimes incorrectly. ;)
Such as:
% DSK:MONGEN.MIC will not be written
% File DSK:MONGEN.MIC already exists
And then:
.do monbld
?MICCOF Cannot open file MIC:MONBLD.MIC - in "DO" command
On 22 Dec 2012, at 00:48, G. <gerry77 at mail.com> wrote:
On Fri, 21 Dec 2012 18:50:05 -0500, you wrote:
Hey everyone,
I'm having a bit of trouble configuring DECnet on TOPS-10 in klh20.
[...]
As you can see, I changed the configuration to 9.10, yet it changes the mac
address from 9.10 back to that of 24.172.
Where else do I need to reconfigure this? ;)
Well, to be honest I didn't even remember the ONCE option to reconfigure the
network (are those settings sticky over reboots?)... Anyway, whenever I had to
reconfigure DECnet I've simply rebuilt the monitor with a new set of custom
parameters: once setup, the process is straightforward.
Monitor sources usually are in [10,7,MON] so you just go there with PATH or
SETSRC, then you have to run MONGEN and answer all its questions, notably the
one that asks if it has to write a MONGEN.MIC file (say yes). This produces a
tailored .MIC file with all your answers, which you can modify whenever you
need to change something, and two parameter files (SYSCNF.MAC and F.MAC).
Then I suggest you put something like what follows in a .MIC file, I've called
mine MONBLD.MIC:
.DAYTIME
.COMPILE/COMPILE F,S
.COMPILE/COMPILE DEVPRM,DTEPRM,NETPRM,D36PAR
.COMPILE/COMPILE SYSCNF+<COMMON,COMDEV,COMMOD>
.R LINK
*SYSTEM/SAVE/NOINITIAL/HASH:13K = /LOCALS -
*COMMON,COMDEV,COMMOD,REL:TOPS10/SEARCH-
*/PATCH:200/COUNTERS/GO
.DIRECT/DETAIL SYSTEM.EXE
.DAYTIME
So, whenever you need to rebuild your monitor with different parameters, you
can just edit your MONGEN.MIC (or a copy of) and then at the dot prompt simply
type DO MONGEN followed by DO MONBLD (or whatever names you have used). On a
modern system the whole process takes no more that 1-2 minutes. :)
The bunch of commands above comes from DEC manuals (I'm not so expert); note
that between /LOCALS and the hypen there must be a space, I do not know why
but manuals warn about this. You must have TOPS10.REL somewhere on your disk
(usually in REL:) and that place has to be clearly specified just before
/SEARCH. TOPS10.REL is the library file that contains almost every monitor
module. When MONBLD finished its work, you'll have a new SYSTEM.EXE in the
current directory: you can then rename and move it as you please.
If you need to modify standard modules (such as CLOCK1.MAC to implement KLH10
idle detection) the procedure is not much more complex than this.
Please excuse me if I wrote things you already know!
HTH, :)
G.
Thank you! I've not played much with TOPS-10, but you've helped a lot.
I learn a lot about DEC OSes by tuning them oftentimes incorrectly. ;)
On Fri, 21 Dec 2012 18:50:05 -0500, you wrote:
Hey everyone,
I'm having a bit of trouble configuring DECnet on TOPS-10 in klh20.
[...]
As you can see, I changed the configuration to 9.10, yet it changes the mac
address from 9.10 back to that of 24.172.
Where else do I need to reconfigure this? ;)
Well, to be honest I didn't even remember the ONCE option to reconfigure the
network (are those settings sticky over reboots?)... Anyway, whenever I had to
reconfigure DECnet I've simply rebuilt the monitor with a new set of custom
parameters: once setup, the process is straightforward.
Monitor sources usually are in [10,7,MON] so you just go there with PATH or
SETSRC, then you have to run MONGEN and answer all its questions, notably the
one that asks if it has to write a MONGEN.MIC file (say yes). This produces a
tailored .MIC file with all your answers, which you can modify whenever you
need to change something, and two parameter files (SYSCNF.MAC and F.MAC).
Then I suggest you put something like what follows in a .MIC file, I've called
mine MONBLD.MIC:
.DAYTIME
.COMPILE/COMPILE F,S
.COMPILE/COMPILE DEVPRM,DTEPRM,NETPRM,D36PAR
.COMPILE/COMPILE SYSCNF+<COMMON,COMDEV,COMMOD>
.R LINK
*SYSTEM/SAVE/NOINITIAL/HASH:13K = /LOCALS -
*COMMON,COMDEV,COMMOD,REL:TOPS10/SEARCH-
*/PATCH:200/COUNTERS/GO
.DIRECT/DETAIL SYSTEM.EXE
.DAYTIME
So, whenever you need to rebuild your monitor with different parameters, you
can just edit your MONGEN.MIC (or a copy of) and then at the dot prompt simply
type DO MONGEN followed by DO MONBLD (or whatever names you have used). On a
modern system the whole process takes no more that 1-2 minutes. :)
The bunch of commands above comes from DEC manuals (I'm not so expert); note
that between /LOCALS and the hypen there must be a space, I do not know why
but manuals warn about this. You must have TOPS10.REL somewhere on your disk
(usually in REL:) and that place has to be clearly specified just before
/SEARCH. TOPS10.REL is the library file that contains almost every monitor
module. When MONBLD finished its work, you'll have a new SYSTEM.EXE in the
current directory: you can then rename and move it as you please.
If you need to modify standard modules (such as CLOCK1.MAC to implement KLH10
idle detection) the procedure is not much more complex than this.
Please excuse me if I wrote things you already know!
HTH, :)
G.
On 2012-12-21 19:37, Cory Smelosky wrote:
On 21 Dec 2012, at 13:35, sampsa at mac.com <mailto:sampsa at mac.com> wrote:
On 21 Dec 2012, at 20:34, Cory Smelosky <b4 at gewt.net
<mailto:b4 at gewt.net>> wrote:
I intend to keep my NT systems (or at least 1 of them) on HECnet at
all times, as a part of my "NT 4 will run forever" experiment.
Does the NT PATHWORKS actually offer any services? Or is it client only?
Seems to be client only. :(
I wonder if I could throw up an interface to PATHWORKS' NCP on
http://winnt.dev.gimme-sympathy.org/
?
I have both FAL and NML (NICE server) running on my XP box, and it works just fine to access files from my remote RSX systems.
.ncp tell wxp sho exec cha
Node characteristics as of 22-DEC-12 01:36:02
Remote node = 1.20 (WXP)
Parameter #1902 = 7.4.112
State = On, Identification = DECnet-V5.2
Management version = 4.2.0, Incoming timer = 45
Outgoing timer = 60, Confidence timer = 15
Active links = 0, NSP version = 4.1.0
Maximum links = 64, Delay factor = 48
Delay weight = 2, Inactivity timer = 30
Retransmit factor = 6, Routing version = 2.0.0
Type = Endnode IV, Buffer size = 1484
Segment buffer size = 576
Parameter #934 =
Parameter #935 =
Parameter #1920 = C:\PW32\
Parameter #1921 = 6
Parameter #1922 = 6
Parameter #1934 = 0
Parameter #1950 = 5
Parameter #1951 = Auto
Parameter #1952 = IOCB segment, NETBIOS xonxoff
Parameter #1953 = 60
Parameter #1954 = 5
Parameter #1955 = 1
.
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 21 Dec 2012, at 19:21, Peter Lothberg <roll at Stupi.SE> wrote:
Yeah, i'm currently in the process of reestablishing my HECnet link=85and =
getting TOPS-10 to be convinced it's actually 9.10 instead of 24.127=85it =
insists on rewriting the mac address for no reason.
If it rewites it to "another DECnet mac" it must be getting it from
config somwhere. What is your "host operating system" for KLH?
Ubuntu Server.
(The MAC it's getting rewritten to is the default it gives me when I go to CHANGE NETWORK at boot, so what file do I need to edit to convince it it's 9.10 instead of 24.137?)
-p
Yeah, i'm currently in the process of reestablishing my HECnet link=85and =
getting TOPS-10 to be convinced it's actually 9.10 instead of 24.127=85it =
insists on rewriting the mac address for no reason.
If it rewites it to "another DECnet mac" it must be getting it from
config somwhere. What is your "host operating system" for KLH?
-p
On 21 Dec 2012, at 19:13, Peter Lothberg <roll at Stupi.SE> wrote:
-----Original Message-----
From: owner-hecnet at Update.UU.SE [mailto:owner-hecnet at Update.UU.SE]
On Behalf Of Cory Smelosky
Sent: 21 December 2012 23:29
To: hecnet at Update.UU.SE
Subject: Re: [HECnet] Nodelist additions!
On 21 Dec 2012, at 13:18, Cory Smelosky <b4 at gewt.net> wrote:
Hey Johhny,
Can you add:
MEAGHN (9.8)
MAKYLA (9.9)
to the nodelist please?
Thanks!
And
MARLEY (9.10) (It's special! It's TOPS-10!)
NCP>tell MARLEY sh exec char
NCP>
01:12:26 NCP
Request # 28 Accepted
01:12:26 NCP
Request # 28; Show Executor Node Characteristics Failed, Listener link
connect f
ailed,
Link Failure = Node unreachable
NCP>
01:12:33 -- DECnet link message --
Communication failure to the following nodes:
MARLEY
NCP>sh exec char
NCP>
01:12:43 NCP
Request # 29; Show Executor Node Characteristics Completed
Executor Node = 59.10 (SOL)
Identification = SC40M, Stupi Stockholm, Tops20
Management Version = 4.0.0
Loop Count = 1
Loop Length = 127
Loop With = Mixed
Incoming Timer = 30
Outgoing Timer = 60
NSP Version = 4.0.0
Maximum Links = 65535
Delay Factor = 48
Delay Weight = 10
Inactivity Timer = 120
Retransmit Factor = 10
Routing Version = 2.0.0
Type = Routing IV
Routing Timer = 600
Broadcast Routing Timer = 40
Maximum Address = 1023
Maximum Circuits = 20
Maximum Cost = 100
Maximum Hops = 16
Maximum Visits = 20
Maximum Broadcast Nonrouters = 64
Maximum Broadcast Routers = 32
Maximum Buffers = 80
Buffer Size = 576
Segment Buffer Size = 576
NCP>
Yeah, i'm currently in the process of reestablishing my HECnet link and getting TOPS-10 to be convinced it's actually 9.10 instead of 24.127 it insists on rewriting the mac address for no reason.
