Description
I'm wondering whether some special considerations apply when using this tape image with community maintained version of klh10
I can restore this image on 2 RP06s, using standard BB-H137F-BM tape, to 1xRP07 using either same standard DEC tape or a tape containing monitr.exe and dumper.exe previously restored off panda distribution tape, but I can't restore it onto 2 RP07s (using modified monitor provided by the distribution) regardless whether I'm using DLUSER before DUMPER run or not. Tried this with following boot tape contents:
system:monitr.exe
tops20:<subsys>dumper.exe
and
system:motnitr.exe
tops20:<subsys>dluser.exe
(data written by DUMP MTA0: command to DLUSER)
tops20:<subsys>dumper.exe
Both tapes were created using running Panda-distribution on single RP07.
When initially restoring onto empty RP07, a total of 7401 files were restored, one skipped.
When dumping (timeshaing-off) that RP07 to new DUMPER tape (just in case) total of 7400 files were saved, one skipped again
When restoring above DUMPER tape to a set of 2 RP07s, only 7399 files were restored, one skipped again.
Running DLUSER LOAD against one RP07 poses no problem (using DLUSER on DEC standard boot tape). DUMPER complains about existing directories though (CREDIR JSYS)
Trying to LOAD directory structure using DLUSER DUMP from that one RP07 (second "custom" boot tape) onto 2 empty RP07s leads into immediate complaints, but in both cases (both "custom" boot tapes) DUMPER behaves the same way, creating all dirs except <ROOT-DIRECTORY> where it complains in roughly same way as DLUSER leaving system unbootable. Subject message appears immediately when trying to load EDDT (/E command)