On Tue, 14 May 2013 08:00:52 -0000, you wrote:
Unfortunately it only /mostly/ works.
MARLEY TOPS-10 03:23:12 CTY system 1
Connected to Node MARLEY(0) Line # 632
[Checking terminal type . . . found VT100]
..LOGIN 1,2
..R OPR
[CCPWFD Waiting for file daemon to start]
%%TTY STOMPER - Starting
And it stalls right there unless I repeatedly hit Ctrl/C...
That happened to me more than once with some older pre-built monitors, then
went away when I did my own install and build of 7.04, so I do not have a
solution, and at the time I hadn't any knowledge about TOPS-10. That does not
mean that now I'm very proficient on it, but...
Upon further investigation, the problem is with OPR.EXE. It WILL NOT
execute on my generated monitor. The one provided with TWONKY works fine
though.
... Make sure that ORION and other Galaxy processes are all there and that
none of them shows a "^C" or "TO" status (IIRC). Also compare processes
between TWONKY and your installation and see if there are any differences.
OPR is just a client that talks to a daemon process so maybe it just stalls
because the daemon is not working, not responding, or not there.
Compare contents of SYS:SYSJOB.INI too.
HTH,
G.
On Tue, 14 May 2013 03:15:12 -0000, you wrote:
Could this be related?
*SYSTEM/SAVE/NOINITIAL/HASH:13K = /LOCALS -
#COMMON,COMDEV,COMMOD,TOPS10/SEARCH-
#/PATCH:200/COUNTERS/GO
[LNKRLC Reloc. ctr. initial value current value limit value
.LOW. 0 65125 330000
.HIGH. 340000 671326 734000
.CSUB. 330000 333466 340000
.INIT. 740000 766655 771000
.TWIC. 771000 772714 1000000
.XHGH. 2630000 2703030 2734000
.SYMS. 2000000 2000000 2630000
Absolute code loaded]
EXIT
It doesn't look like an error though...so I'm rather confused.
I've read the other message saying to disregard this one, anyway the above is
correct and I think is caused by the /COUNTERS switch. It's a status message
because its text is enclosed in square brackets. Warning and error messages
are preceded by "%" or "?" depending on their severity.
HTH, :)
G.
On Tue, 14 May 2013, Cory Smelosky wrote:
On Mon, 14 May 2013, Cory Smelosky wrote:
On Mon, 14 May 2013, Cory Smelosky wrote:
On Mon, 14 May 2013, Cory Smelosky wrote:
On Mon, 13 May 2013, G. wrote:
On Tue, 14 May 2013 00:27:49 +0200, you wrote:
Well, here are the symbols:
M.SNAM is the system name (apparently not related to DECnet)
M.DNAM is the DECnet node name
M.LNAM is te LAT (default?) service name
M.DHOM is the DECnet area number (octal!)
M.DNUM is the DECnet node number (octal!)
Beware: the names are SIXBIT strings, so you must discover how to input SIXBIT
vaules with FILDDT (I have no idea, probably it's something like <ESC>letter).
Correction/update: the above symbols are only used during MONGEN, but then are
equated to other ones inside the monitor sources. These are the equivalences:
STANAM is the system name (apparently not related to DECnet)
DCNNAM is the DECnet node name
LATNAM is te LAT (default?) service name
DCNHOM is the DECnet area number (octal!)
DCNNUM is the DECnet node number (octal!)
HTH,
G.
I have made progress! (I think)
BOOT>dskb:system.exe
[Loading from DSKB:SYSTEM.EXE[1,4]]
MARLEY TOPS-10 13-May-13
Why reload: new
Date:
Time:
It does however stall there...
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
Could this be related?
*SYSTEM/SAVE/NOINITIAL/HASH:13K = /LOCALS -
#COMMON,COMDEV,COMMOD,TOPS10/SEARCH-
#/PATCH:200/COUNTERS/GO
[LNKRLC Reloc. ctr. initial value current value limit value
.LOW. 0 65125 330000
.HIGH. 340000 671326 734000
.CSUB. 330000 333466 340000
.INIT. 740000 766655 771000
.TWIC. 771000 772714 1000000
.XHGH. 2630000 2703030 2734000
.SYMS. 2000000 2000000 2630000
Absolute code loaded]
EXIT
It doesn't look like an error though...so I'm rather confused.
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
Disregard. The monitor works now.
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
Unfortunately it only /mostly/ works.
MARLEY TOPS-10 03:23:12 CTY system 1
Connected to Node MARLEY(0) Line # 632
[Checking terminal type . . . found VT100]
..LOGIN 1,2
..R OPR
[CCPWFD Waiting for file daemon to start]
%%TTY STOMPER - Starting
And it stalls right there unless I repeatedly hit Ctrl/C...
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
Upon further investigation, the problem is with OPR.EXE. It WILL NOT execute on my generated monitor. The one provided with TWONKY works fine though.
Will investigate further. Hopefully they left their MONGEN scripts laying around!
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
On Mon, 14 May 2013, Cory Smelosky wrote:
On Mon, 14 May 2013, Cory Smelosky wrote:
On Mon, 14 May 2013, Cory Smelosky wrote:
On Mon, 13 May 2013, G. wrote:
On Tue, 14 May 2013 00:27:49 +0200, you wrote:
Well, here are the symbols:
M.SNAM is the system name (apparently not related to DECnet)
M.DNAM is the DECnet node name
M.LNAM is te LAT (default?) service name
M.DHOM is the DECnet area number (octal!)
M.DNUM is the DECnet node number (octal!)
Beware: the names are SIXBIT strings, so you must discover how to input SIXBIT
vaules with FILDDT (I have no idea, probably it's something like <ESC>letter).
Correction/update: the above symbols are only used during MONGEN, but then are
equated to other ones inside the monitor sources. These are the equivalences:
STANAM is the system name (apparently not related to DECnet)
DCNNAM is the DECnet node name
LATNAM is te LAT (default?) service name
DCNHOM is the DECnet area number (octal!)
DCNNUM is the DECnet node number (octal!)
HTH,
G.
I have made progress! (I think)
BOOT>dskb:system.exe
[Loading from DSKB:SYSTEM.EXE[1,4]]
MARLEY TOPS-10 13-May-13
Why reload: new
Date:
Time:
It does however stall there...
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
Could this be related?
*SYSTEM/SAVE/NOINITIAL/HASH:13K = /LOCALS -
#COMMON,COMDEV,COMMOD,TOPS10/SEARCH-
#/PATCH:200/COUNTERS/GO
[LNKRLC Reloc. ctr. initial value current value limit value
.LOW. 0 65125 330000
.HIGH. 340000 671326 734000
.CSUB. 330000 333466 340000
.INIT. 740000 766655 771000
.TWIC. 771000 772714 1000000
.XHGH. 2630000 2703030 2734000
.SYMS. 2000000 2000000 2630000
Absolute code loaded]
EXIT
It doesn't look like an error though...so I'm rather confused.
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
Disregard. The monitor works now.
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
Unfortunately it only /mostly/ works.
MARLEY TOPS-10 03:23:12 CTY system 1
Connected to Node MARLEY(0) Line # 632
[Checking terminal type . . . found VT100]
.LOGIN 1,2
.R OPR
[CCPWFD Waiting for file daemon to start]
%%TTY STOMPER - Starting
And it stalls right there unless I repeatedly hit Ctrl/C...
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
On Mon, 14 May 2013, Cory Smelosky wrote:
On Mon, 14 May 2013, Cory Smelosky wrote:
On Mon, 13 May 2013, G. wrote:
On Tue, 14 May 2013 00:27:49 +0200, you wrote:
Well, here are the symbols:
M.SNAM is the system name (apparently not related to DECnet)
M.DNAM is the DECnet node name
M.LNAM is te LAT (default?) service name
M.DHOM is the DECnet area number (octal!)
M.DNUM is the DECnet node number (octal!)
Beware: the names are SIXBIT strings, so you must discover how to input SIXBIT
vaules with FILDDT (I have no idea, probably it's something like <ESC>letter).
Correction/update: the above symbols are only used during MONGEN, but then are
equated to other ones inside the monitor sources. These are the equivalences:
STANAM is the system name (apparently not related to DECnet)
DCNNAM is the DECnet node name
LATNAM is te LAT (default?) service name
DCNHOM is the DECnet area number (octal!)
DCNNUM is the DECnet node number (octal!)
HTH,
G.
I have made progress! (I think)
BOOT>dskb:system.exe
[Loading from DSKB:SYSTEM.EXE[1,4]]
MARLEY TOPS-10 13-May-13
Why reload: new
Date:
Time:
It does however stall there...
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
Could this be related?
*SYSTEM/SAVE/NOINITIAL/HASH:13K = /LOCALS -
#COMMON,COMDEV,COMMOD,TOPS10/SEARCH-
#/PATCH:200/COUNTERS/GO
[LNKRLC Reloc. ctr. initial value current value limit value
.LOW. 0 65125 330000
.HIGH. 340000 671326 734000
.CSUB. 330000 333466 340000
.INIT. 740000 766655 771000
.TWIC. 771000 772714 1000000
.XHGH. 2630000 2703030 2734000
.SYMS. 2000000 2000000 2630000
Absolute code loaded]
EXIT
It doesn't look like an error though...so I'm rather confused.
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
Disregard. The monitor works now.
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
On Mon, 14 May 2013, Cory Smelosky wrote:
On Mon, 13 May 2013, G. wrote:
On Tue, 14 May 2013 00:27:49 +0200, you wrote:
Well, here are the symbols:
M.SNAM is the system name (apparently not related to DECnet)
M.DNAM is the DECnet node name
M.LNAM is te LAT (default?) service name
M.DHOM is the DECnet area number (octal!)
M.DNUM is the DECnet node number (octal!)
Beware: the names are SIXBIT strings, so you must discover how to input SIXBIT
vaules with FILDDT (I have no idea, probably it's something like <ESC>letter).
Correction/update: the above symbols are only used during MONGEN, but then are
equated to other ones inside the monitor sources. These are the equivalences:
STANAM is the system name (apparently not related to DECnet)
DCNNAM is the DECnet node name
LATNAM is te LAT (default?) service name
DCNHOM is the DECnet area number (octal!)
DCNNUM is the DECnet node number (octal!)
HTH,
G.
I have made progress! (I think)
BOOT>dskb:system.exe
[Loading from DSKB:SYSTEM.EXE[1,4]]
MARLEY TOPS-10 13-May-13
Why reload: new
Date:
Time:
It does however stall there...
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
Could this be related?
*SYSTEM/SAVE/NOINITIAL/HASH:13K = /LOCALS -
#COMMON,COMDEV,COMMOD,TOPS10/SEARCH-
#/PATCH:200/COUNTERS/GO
[LNKRLC Reloc. ctr. initial value current value limit value
.LOW. 0 65125 330000
.HIGH. 340000 671326 734000
.CSUB. 330000 333466 340000
.INIT. 740000 766655 771000
.TWIC. 771000 772714 1000000
.XHGH. 2630000 2703030 2734000
.SYMS. 2000000 2000000 2630000
Absolute code loaded]
EXIT
It doesn't look like an error though...so I'm rather confused.
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
On Mon, 13 May 2013, G. wrote:
On Tue, 14 May 2013 00:27:49 +0200, you wrote:
Well, here are the symbols:
M.SNAM is the system name (apparently not related to DECnet)
M.DNAM is the DECnet node name
M.LNAM is te LAT (default?) service name
M.DHOM is the DECnet area number (octal!)
M.DNUM is the DECnet node number (octal!)
Beware: the names are SIXBIT strings, so you must discover how to input SIXBIT
vaules with FILDDT (I have no idea, probably it's something like <ESC>letter).
Correction/update: the above symbols are only used during MONGEN, but then are
equated to other ones inside the monitor sources. These are the equivalences:
STANAM is the system name (apparently not related to DECnet)
DCNNAM is the DECnet node name
LATNAM is te LAT (default?) service name
DCNHOM is the DECnet area number (octal!)
DCNNUM is the DECnet node number (octal!)
HTH,
G.
I have made progress! (I think)
BOOT>dskb:system.exe
[Loading from DSKB:SYSTEM.EXE[1,4]]
MARLEY TOPS-10 13-May-13
Why reload: new
Date:
Time:
It does however stall there...
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
On Tue, 14 May 2013 00:27:49 +0200, you wrote:
Well, here are the symbols:
M.SNAM is the system name (apparently not related to DECnet)
M.DNAM is the DECnet node name
M.LNAM is te LAT (default?) service name
M.DHOM is the DECnet area number (octal!)
M.DNUM is the DECnet node number (octal!)
Beware: the names are SIXBIT strings, so you must discover how to input SIXBIT
vaules with FILDDT (I have no idea, probably it's something like <ESC>letter).
Correction/update: the above symbols are only used during MONGEN, but then are
equated to other ones inside the monitor sources. These are the equivalences:
STANAM is the system name (apparently not related to DECnet)
DCNNAM is the DECnet node name
LATNAM is te LAT (default?) service name
DCNHOM is the DECnet area number (octal!)
DCNNUM is the DECnet node number (octal!)
HTH,
G.
On 13 May 2013, at 19:07, "G." <gerry77 at mail.com> wrote:
On Mon, 13 May 2013 22:45:50 -0000, you wrote:
This one for DECnet (7.04 version, the latest available):
BB-X116D-BB Identified as "DECNET-10 V4.0 SUP 16MT9 1989"
I thought that was only a supplemental tape that isn't particularly useful?
Ah yes, now I remember everything: starting from some version I do not know
(maybe just 7.04), DECnet binaries were bundled with CUSP tapes, and sources
with Monitor tapes (see 704.BWR in the latter). The BB-X116D-BB tape is there
just because it contains the key files needed to decrypt DECnet patches.
Anything else in that tape is only for front-end DECnet support (DDCMP etc.).
Thank you! That helps a lot. Looks like I should be able to get this working tonight or tomorrow!
It contains NML.EXE too, which anyway will be replaced when installing TSUs,
but until you patch TOPS-10, you'll need NML.EXE from the above tape.
Ah.
G. :)
On Mon, 13 May 2013 22:45:50 -0000, you wrote:
This one for DECnet (7.04 version, the latest available):
BB-X116D-BB Identified as "DECNET-10 V4.0 SUP 16MT9 1989"
I thought that was only a supplemental tape that isn't particularly useful?
Ah yes, now I remember everything: starting from some version I do not know
(maybe just 7.04), DECnet binaries were bundled with CUSP tapes, and sources
with Monitor tapes (see 704.BWR in the latter). The BB-X116D-BB tape is there
just because it contains the key files needed to decrypt DECnet patches.
Anything else in that tape is only for front-end DECnet support (DDCMP etc.).
It contains NML.EXE too, which anyway will be replaced when installing TSUs,
but until you patch TOPS-10, you'll need NML.EXE from the above tape.
G. :)
