On Mon, May 27, 2019 at 10:37 AM Paul Koning <paulkon...@comcast.net> wrote: > > > 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? >
It was installed from the RSTS/E 10.0 tape image that recently (2019-05-09) appeared on Bitsavers: http://www.bitsavers.org/bits/DEC/pdp11/rsts/RSTS_V10.ZIP I have installed from a RSTS/E 10.1 tape image in the past and I seem to remember it being more Y2K friendly. I used the Bitsavers 10.0 tape image as an example here because the 10.1 tape image source that I previously used was not public at the time to provide a link. > > 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. > Yeah, those messages bug me slightly and I should try to figure out what they mean. I don't remember seeing those when I used a 10.1 install. I just wanted to get this example out there for Rod now, and worry about clean up issues later. Thanks.