Al 15/05/13 00:34, En/na Cory Smelosky ha escrit:
which seems to involve rebuilding a monitor which results in a CATCH-22.
I don't know if this can be of help...
I have uploaded at BITXOV:: the file TOPS10KLB.ZIP, which contains:
[BITXOV]$ unzip/list tops10klb
Archive: DUA1:[FAL$SERVER]TOPS10KLB.ZIP;1
Length Date Time Namem
-------- ---- ---- ----
22206272 05-10-13 17:40 t10bootkl.tap
120320 05-10-13 12:20 klboot.exe
-------- -------
22326592 2 files
klboot.exe is a bootloader which (should) work with KLH10 to boot t10bootkl.tap, which is a KL-bootable 7.04 tape. I made this stuff some months ago, and I was able to install 7.04 under KLH10 (including DECNET suport over ethernet). The details are semi-forgotten (I should have blogged that! :)), but I have just tried to boot the tape and I got into the monitor prompt.
Remember to answer '/TM3' to the BOOT> prompt.
Greetings all,
Thought I'd move this in to a cleaner, fresh thread...
I have managed to get a working install of TOPS-10 7.04/7.05 in KLH-10 with DECnet and LAT! I have tested it from my VT420.
You can test it too! SET HOST to MARLEY and LOGIN as 1,2 (no password yet...need to tweak that a bit). Let me know how it works for you!
I still have a long way to go, and I have NO IDEA if I can replicate this install ever again...I have saved a complete (857,360 line!) copy of the terminal output for future reference though!
Next comes either: getting this working in SIMH, or getting it working on a real KS10/KL10 (I can likely convert this setup to a KS10, too. I'd just need to consult the DECnet-10 manuals). Now if only I had a KS10...;))
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
On Tue, 14 May 2013, G. wrote:
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.
Everything works now that I've patched it to 7.05!
I still have less tasks than I should...but everything seems to work now!
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
On Tue, 14 May 2013, G. 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).
Well...I'm trying to get the TSU04 patches installed:
.MOUNT TSUTAP:/READ/REELID:(TSU1,TSU2,TSU3)
?Undefined switch /REA
I don't think that's supposed to happen! It reaches EOT...and feeds commands it shouldn't on to BACKUP.
I may be able to work around this...is there a SLEEP/WAIT command?
G.
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
On Tue, 14 May 2013, G. wrote:
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.
I decided to attach DDT to it...and if I am using DDT right...(and I'm probably not...) it's refusing to move past ADDR 0. It doesn't seem to be executing any actual instructions!
HTH, :)
G.
--
Cory Smelosky
http://gewt.net/ Personal stuff
http://gimme-sympathy.org Experiments
On 14 May 2013, at 18:59, "G." <gerry77 at mail.com> wrote:
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.
MIC automatically detaches here interesting enough.
HTH, :)
G.
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! :)
