From: krewat@kilonet.net (Arthur Krewat)
Subject: [TUHS] Date madness
Date: Wed, 13 Dec 2017 13:02:43 -0500 [thread overview]
Message-ID: <9ac6727e-17cc-3d8e-b175-c94d83d0c1d6@kilonet.net> (raw)
In-Reply-To: <00e601d37436$671baf80$35530e80$@ronnatalie.com>
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #1: Type: text/plain, Size: 1369 bytes --]
On 12/13/2017 12:18 PM, Ron Natalie wrote:
> The TOPS-10 software ran out in 1975 or so if I recall.
Nope, I can boot a 7.03 monitor and it understands Y2K and higher. I had
to edit SYSTAT.MAC to make it print the currect year after 2000, but
everything else just worked.
I believe a 6.03A monitor also behaves correctly.
Although, I believe the year is coming soon when it will implode and
wrap back around. I don't recall the specifics of that.
../simh/simhv28/pdp10 ks10.cfg.gold
PDP-10 simulator V2.8-4
Listening on socket 6
Modem control activated
sim> boot rp0
BOOT V3(47)
BOOT>
[Loading from DSKB:SYSTEM.EXE[1,4]]
LIRICS Timesharing Gold 07-08-01
Why reload: PM
Date: *<ENTER here takes date from hardware **clock>*
Time: *<ENTER here takes time from ***hardware ***clock>*
Startup option: go
*<snip>*
.SYS
Status of LIRICS Timesharing Gold at 12:59:09 on 13-Dec-2017
Uptime 3:17, 99% Null time = 99% Idle + 0% Lost, 0% Overhead
12 Jobs in use out of 128. 12 logged in, 10 detached.
*<snip>
*.
Monitor LIRICS Timesharing Gold
System uptime :04:08
Current date/time 13-Dec-2017 13:00:00 *<-- This time is spewed by the
monitor directly which I did not have to change>*
**
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://minnie.tuhs.org/pipermail/tuhs/attachments/20171213/f23f82c0/attachment-0001.html>
next prev parent reply other threads:[~2017-12-13 18:02 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-12-12 18:01 Noel Chiappa
2017-12-12 18:21 ` Warner Losh
2017-12-13 15:07 ` Random832
2017-12-13 17:00 ` Jason Stevens
2017-12-13 17:18 ` Ron Natalie
2017-12-13 18:02 ` Arthur Krewat [this message]
2017-12-13 15:39 ` Wolfgang Helbig
2017-12-14 0:57 ` Dave Horsfall
2017-12-14 14:09 ` William Cheswick
2017-12-17 16:19 ` Ron Natalie
2017-12-17 16:33 ` William Cheswick
2017-12-17 17:54 ` Random832
2017-12-17 22:15 ` Dave Horsfall
2017-12-17 22:54 ` Ian Zimmerman
2017-12-16 18:12 ` Wolfgang Helbig
2017-12-12 18:31 Noel Chiappa
2017-12-13 15:56 Noel Chiappa
2017-12-13 16:08 Noel Chiappa
2017-12-13 16:23 ` arnold
2017-12-13 16:31 Noel Chiappa
2017-12-13 16:50 ` arnold
2017-12-13 17:16 Noel Chiappa
2017-12-13 18:53 ` Tom Ivar Helbekkmo
2017-12-13 20:46 ` arnold
2017-12-15 16:41 ` Paul Winalski
2017-12-15 17:19 ` Dave Horsfall
2017-12-16 15:45 ` Clem Cole
2017-12-16 3:39 ` Dave Horsfall
2017-12-16 3:45 ` Lyndon Nerenberg
2017-12-17 1:43 ` Dave Horsfall
2017-12-14 3:08 ` Dave Horsfall
2017-12-14 3:13 ` Warner Losh
2017-12-13 19:12 Doug McIlroy
2017-12-14 3:07 ` Random832
2017-12-15 3:04 ` Random832
2017-12-13 20:22 Noel Chiappa
2017-12-13 22:16 Norman Wilson
2017-12-14 0:24 ` Chris Torek
2017-12-17 16:20 ` Ron Natalie
2017-12-17 18:53 ` Tom Ivar Helbekkmo
2017-12-17 20:07 ` Ron Natalie
2017-12-16 10:50 Doug McIlroy
2017-12-16 16:11 ` Random832
2017-12-16 17:11 ` Ralph Corderoy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=9ac6727e-17cc-3d8e-b175-c94d83d0c1d6@kilonet.net \
--to=krewat@kilonet.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).