> On May 27, 2019, at 1:23 PM, Glen Slick via cctalk <cctalk@classiccmp.org>
> wrote:
>
> ...
> Then boot from DU0, and if everything worked along the way it should
> just work. Assuming it boots OK into RSTS/E 10.0, use the SHOW DISK
> command to verify that the reported disk size is the expected 311200
> blocks.
Nice.
You can run the file system checker -- in INIT, to the "start timesharing"
prompt, answer "refresh", then <ret> for the system disk, and when asked
"Rebuild" say yes. It should complete with no complaints.
> The output below is booting from the SCSI disk on a KDJ11-D 11/53.
>
> 9 8 7 6 5 4 3 2 1
>
> Commands are Help, Boot, List, Map, Test and Wrap.
> Type a command then press the RETURN key: BOOT DU0
>
>
> DU0
>
> RSTS V10.0-L RSTS (DU0) INIT V10.0-0L
>
>
> Today's date? 19.5.27
>
> Current time? 9:50
>
> ...
> ;9.05.27 09:50
Hm, Y2K bug in that version?
> Proceed with system startup? <YES>
>
> Beginning RSTS/E system startup...
> 19.05.27 09:50 Installing monitor overlays
> 19.05.27 09:50 Mounting disks
> 19.05.27 09:50 Assigning logical names
> 19.05.27 09:50 Starting error logging
> 19.05.27 09:50 Setting system characteristics
> 27-May-19 09:50 AM Installing run-time systems and libraries
> 27-May-19 09:50 AM Starting Operator/Message Services
> ?Invalid time
> ?Undefined symbol
> ?Undefined symbol
This says there's some stuff in your start.com that RSTS is not happy with, but
it's not clear what that might be. It doesn't seem to cause any real problems.
paul
