On Tue, 14 May 2013 22:50:17 -0000, you wrote:
That I CAN do so long as I can get MIC to run and PATH to operate without GALAXY functions operating.
I think you may try to get MIC running by logging into a new job, then RUNning
MIC, then doing CTRL/C twice (that stops the program but does not delete it
from core), then giving CCONTINUE to continue it in background, then ATTACH to
another job or just DETACH from the MIC job. Only be careful not to KJOB it.
HTH, :)
G.
On 14 May 2013, at 18:45, "G." <gerry77 at mail.com> wrote:
On Tue, 14 May 2013 22:34:05 -0000, you wrote:
I can't apply the patches because PATH isn't a recognised command. ;)
which seems to involve rebuilding a monitor which results in a CATCH-22.
PATH isn't a recognized command in TWONKY? Anyway, if you have SYS:PATH.EXE,
you may try to build a monitor with PATH command. Look at my MONGEN and you
will see the following:
Maybe in twonky, but I did a from-scratch install.
;Type "command-name,dispatch,flags,unique-bits,PRVTAB-name"
*PATH,,RUNFLG,UNIQ.2,
*
So you should be able to include PATH in a monitor of yours, isn't it? :)
That I CAN do so long as I can get MIC to run and PATH to operate without GALAXY functions operating.
G.
On Tue, 14 May 2013 22:34:05 -0000, you wrote:
I can't apply the patches because PATH isn't a recognised command. ;)
which seems to involve rebuilding a monitor which results in a CATCH-22.
PATH isn't a recognized command in TWONKY? Anyway, if you have SYS:PATH.EXE,
you may try to build a monitor with PATH command. Look at my MONGEN and you
will see the following:
;Type "command-name,dispatch,flags,unique-bits,PRVTAB-name"
*PATH,,RUNFLG,UNIQ.2,
*
So you should be able to include PATH in a monitor of yours, isn't it? :)
G.
Hi all,
once upon a time (!) I collected whatever DECserver software I was able to
find, thinking it would be eventually useful sometime into the future.
Now I see on this mailing list some messages about DECserver software, so I
thought about sharing whatever I know and have, to help others running their
DECservers and maybe to increase my collection too.
Here is what I have:
MNENG1.SYS V1.1C BL46-13
MNENG1_A.SYS V1.1C BL46A-13 From Digital?
MNENG2.SYS V2.0 BL10D-40
MNENG2_DNPG.SYS V2.4 BL50 Copyright Digital Networks, DNPG, LLC
MNENG3_DNPG.SYS V2.4 BL50 Copyright Digital Networks, DNPG, LLC
PS0801ENG.SYS V2.0 BL23
PR0801ENG.SYS V3.3A BL40
DP0601ENG.SYS V2.0 BL29-04
SH1601ENG.SYS V2.2C BL46-13
WWENG1.SYS V1.1C BL46-13
WWENG2.SYS V2.0 BL10D-40
And this is what I miss (both from Digital):
MNENG3.SYS
MNENG4.SYS
Finally, these should be the corresponding DECserver hardware devices:
DECserver 90L+ PROM-based, no firmware
DECserver 90TL MNENG1.SYS or MNENG2.SYS
DECserver 90M (1MB mem) MNENG2.SYS
DECserver 90M (2MB mem) MNENG3.SYS
DECserver 90M+ (4MB mem) MNENG4.SYS
DECserver 100 PS0801ENG.SYS
DECserver 200 PR0801ENG.SYS
DECserver 250 DP0601ENG.SYS
DECserver 300 SH1601ENG.SYS
DECserver 700 (1MB mem) WWENG1.SYS
DECserver 700 (2MB mem) WWENG2.SYS
DECserver 900TM WWENG2.SYS
So, MNENG4.SYS seems to be the most important miss in my collection...
Thanks to everyone, :)
G.
P.S. If you see anything wrong, let me know! :)
On 14 May 2013, at 18:25, G. <gerry77 at mail.com> wrote:
On Tue, 14 May 2013 22:14:22 -0000, you wrote:
Definitely. Maybe a syntax error in SYS:SYSJOB.INI? That unnamed job in "^C"
state is NO good at all. I do not remember exactly what to do (you may want to
check on alt.sys.pdp10), but I think you should ATTACH to that job and try to
give a CCONTINUE to it (its not a typo: CContinue), then ATTACH back.
Can't be. Same SYSJOB.INI works with the included TWONKY monitor.OPR.EXE runs and all processes start.
(I can't start OPR.EXE at all no matter what I do)
Try to CContinue that job and see what happens. Or try to apply TSU04 patches.
But if Galaxy jobs do no start, you'll have to give "manually" to the monitor
whatever command was thought for batch execution (.CTL files).
I can't apply the patches because PATH isn't a recognised command. ;)
which seems to involve rebuilding a monitor which results in a CATCH-22.
G.
On Tue, 14 May 2013 22:14:22 -0000, you wrote:
Definitely. Maybe a syntax error in SYS:SYSJOB.INI? That unnamed job in "^C"
state is NO good at all. I do not remember exactly what to do (you may want to
check on alt.sys.pdp10), but I think you should ATTACH to that job and try to
give a CCONTINUE to it (its not a typo: CContinue), then ATTACH back.
Can't be. Same SYSJOB.INI works with the included TWONKY monitor.OPR.EXE runs and all processes start.
(I can't start OPR.EXE at all no matter what I do)
Try to CContinue that job and see what happens. Or try to apply TSU04 patches.
But if Galaxy jobs do no start, you'll have to give "manually" to the monitor
whatever command was thought for batch execution (.CTL files).
G.
On 14 May 2013, at 18:06, "G." <gerry77 at mail.com> wrote:
On Tue, 14 May 2013 21:23:52 -0000, you wrote:
Job Who Line# What Size(P) State Run Time
2 [OPR] CTY SYSTAT 23+SPY RN 0
4 [OPR] DET751 FILDAE 17 HB 0
5 [OPR] 751 11 ^C 0
I think I should have more jobs than this...
Definitely. Maybe a syntax error in SYS:SYSJOB.INI? That unnamed job in "^C"
state is NO good at all. I do not remember exactly what to do (you may want to
check on alt.sys.pdp10), but I think you should ATTACH to that job and try to
give a CCONTINUE to it (its not a typo: CContinue), then ATTACH back.
Can't be. Same SYSJOB.INI works with the included TWONKY monitor.OPR.EXE runs and all processes start.
(I can't start OPR.EXE at all no matter what I do)
Look at http://pdp-10.trailing-edge.com/tops10v704_docc/index.html for some
other information, particularly in CMND.MEM (for CCONTINUE) and OPGD.MEM.
Off topic (?) for everyone:
You may want to try to contact /BAH alias Barb on alt.sys.pdp10 and ask her
(it's a lady!) for some suggestions. She is also on alt.folklore.computers.
She worked at DEC on TOPS-10 in the Seventies and Eighties and helped me a
lot. She was the "significant other" of Jim Flemming who once wrote almost all
of the (SMP) code in the TOPS-10 monitor. Every monitor programmer had its
three letter acronym: hers was /BAH, his was /JMF. She still signs herself as
/BAH :) Look for /JMF and /TW (Tony Wachs) in TOPS-10 sources. They were her
friends. She once even went to some public library to read some old sources
and give me some answer; I owe her almost any TOPS-10 knowledge. Another one
very worth a read on alt.sys.pdp10 is Rich Alderson (is he reading here too?)
from the Living Computer Museum.
I might do that. thank you.
This is worth a careful reading. My TOPS-10 setup is a tribute to BAH & JMF:
http://groups.google.com/group/alt.sys.pdp10/msg/7592579d5fdab7ae
HTH,
G.
P.S. She's a bit grumpy too :PPP
On Tue, 14 May 2013 21:23:52 -0000, you wrote:
Job Who Line# What Size(P) State Run Time
2 [OPR] CTY SYSTAT 23+SPY RN 0
4 [OPR] DET751 FILDAE 17 HB 0
5 [OPR] 751 11 ^C 0
I think I should have more jobs than this...
Definitely. Maybe a syntax error in SYS:SYSJOB.INI? That unnamed job in "^C"
state is NO good at all. I do not remember exactly what to do (you may want to
check on alt.sys.pdp10), but I think you should ATTACH to that job and try to
give a CCONTINUE to it (its not a typo: CContinue), then ATTACH back.
Look at http://pdp-10.trailing-edge.com/tops10v704_docc/index.html for some
other information, particularly in CMND.MEM (for CCONTINUE) and OPGD.MEM.
Off topic (?) for everyone:
You may want to try to contact /BAH alias Barb on alt.sys.pdp10 and ask her
(it's a lady!) for some suggestions. She is also on alt.folklore.computers.
She worked at DEC on TOPS-10 in the Seventies and Eighties and helped me a
lot. She was the "significant other" of Jim Flemming who once wrote almost all
of the (SMP) code in the TOPS-10 monitor. Every monitor programmer had its
three letter acronym: hers was /BAH, his was /JMF. She still signs herself as
/BAH :) Look for /JMF and /TW (Tony Wachs) in TOPS-10 sources. They were her
friends. She once even went to some public library to read some old sources
and give me some answer; I owe her almost any TOPS-10 knowledge. Another one
very worth a read on alt.sys.pdp10 is Rich Alderson (is he reading here too?)
from the Living Computer Museum.
This is worth a careful reading. My TOPS-10 setup is a tribute to BAH & JMF:
http://groups.google.com/group/alt.sys.pdp10/msg/7592579d5fdab7ae
HTH,
G.
P.S. She's a bit grumpy too :PPP
On Tue, 14 May 2013, G. wrote:
On Tue, 14 May 2013 20:55:21 -0000, you wrote:
Are some of your specifically-defined decimal values and similar REQUIRED?
I followed that MONGEN almost exactly and OPR.EXE STILL can't be run!
No, they are to increase the DECnet message size on Ethernet and to set the
DECnet "hello" timer to 90 seconds.
Ah.
Have you checked SYS:SYSJOB.INI against TWONKY? This is mine (working):
I don't think it matters...the same exact SYS:SYSJOB.INI lets OPR.EXE run with thw exact monitor from TWONKY unmodified.
If I log out and back in...I can't run OPR.EXE either.
-----
SET DEFAULT ACCOUNT SYSTEM
LOG
FILDAE
LOG
ACTDAE
LOG
DAEMON
LOG ;GALAXY JOBS
QUASAR
LOG
MIC
!Modern MICs (later than 11C(1231)) don't need this blank line, older ones do.
NODNAM ;Loads INI:NODNAM.INI then starts MX
-----
And what about system jobs? Is there any job in "^C" or "TO" state? Mine are
all in "SL" (sleep) or "HB" (hibernated) mode... Use SYSTAT to check:
-----
Job Who Line# What Size(P) State
1 [OPR] DET751 STOMPR 11+12 SL
2 [OPR] CTY OPR 61+40 HB
3 [OPR] 4 SYSTAT 23+SPY RN
7 [OPR] DET751 FAL-10 115+40 SL
8 [OPR] DET751 FILDAE 17 HB
9 [OPR] DET751 ACTDAE 67+40 SL
10 [OPR] DET751 DAEMON 11+SPY r HB
11 [OPR] DET751 QUASAR 155+40 SL
12 [OPR] DET751 PULSAR 66+40 HB
13 [OPR] DET751 MIC 5+15 SL
14 [OPR] DET751 NML 38+135 HB
15 [OPR] DET751 MX 124+47 HB
16 [OPR] DET751 ORION 51+40 SL
17 [OPR] DET751 NEBULA 27+40 HB
18 [OPR] DET751 CATLOG 147+40 HB
-----
Job Who Line# What Size(P) State Run Time
2 [OPR] CTY SYSTAT 23+SPY RN 0
4 [OPR] DET751 FILDAE 17 HB 0
5 [OPR] 751 11 ^C 0
I think I should have more jobs than this...
Some of the above (e.g. FAL-10, NML and MX) may not be present on your system.
HTH,
G.
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
On Tue, 14 May 2013 20:55:21 -0000, you wrote:
Are some of your specifically-defined decimal values and similar REQUIRED?
I followed that MONGEN almost exactly and OPR.EXE STILL can't be run!
No, they are to increase the DECnet message size on Ethernet and to set the
DECnet "hello" timer to 90 seconds.
Have you checked SYS:SYSJOB.INI against TWONKY? This is mine (working):
-----
SET DEFAULT ACCOUNT SYSTEM
LOG
FILDAE
LOG
ACTDAE
LOG
DAEMON
LOG ;GALAXY JOBS
QUASAR
LOG
MIC
!Modern MICs (later than 11C(1231)) don't need this blank line, older ones do.
NODNAM ;Loads INI:NODNAM.INI then starts MX
-----
And what about system jobs? Is there any job in "^C" or "TO" state? Mine are
all in "SL" (sleep) or "HB" (hibernated) mode... Use SYSTAT to check:
-----
Job Who Line# What Size(P) State
1 [OPR] DET751 STOMPR 11+12 SL
2 [OPR] CTY OPR 61+40 HB
3 [OPR] 4 SYSTAT 23+SPY RN
7 [OPR] DET751 FAL-10 115+40 SL
8 [OPR] DET751 FILDAE 17 HB
9 [OPR] DET751 ACTDAE 67+40 SL
10 [OPR] DET751 DAEMON 11+SPY HB
11 [OPR] DET751 QUASAR 155+40 SL
12 [OPR] DET751 PULSAR 66+40 HB
13 [OPR] DET751 MIC 5+15 SL
14 [OPR] DET751 NML 38+135 HB
15 [OPR] DET751 MX 124+47 HB
16 [OPR] DET751 ORION 51+40 SL
17 [OPR] DET751 NEBULA 27+40 HB
18 [OPR] DET751 CATLOG 147+40 HB
-----
Some of the above (e.g. FAL-10, NML and MX) may not be present on your system.
HTH,
G.
