SIMH, fortunately, also provides a way to get the current timestamp in the form of %UTIME%, which is interpreted in any argument to any command.
I’ve thus written a utility called tsdate that takes a timestamp as argument and sets the current time to be that timestamp.
Because the calculation is just a naïve division by four, it actually works on the year 2000 itself. has February 29, if a year is: Leap seconds are also not accounted for, but that comes to nobody’s surprise.
Leap seconds just add a second 60 to the usual 00-59, so they don’t hurt doing date calculations on timestamps unless precisely on a leap second. Note that I haven’t gone through the system with a fine-toothed comb.
Once operational db admin can tighten up security if need be.
E) network topology Internal Firewalls Open ports on server, to server, from server, 41794,41795,41796,41797, 80, 443, 1433 for off application server SQL provider Content switches internal proxy servers.
The root cause for this is that the number register macros are required.
However, I’ve had another pet peeve for a while: How much manual labor is involved in booting the system. Yet DOS’s script skips over a part of the bootup procedure that can be fully automated with some additional tooling.
I put the executable in This approach already has a minor amount of time drift ab initio, namely the difference between the actual time on the host system and the UNIX timestamp. If for some reason you need higher accuracy than this, you’ll probably have a fairly hard time.
I could imagine some kind of NTP-over-serial, but you’d need support for chat scripts to get past the authentication due to getty(8) spawning login(1).
Macros for nroff(1)/troff(1), however, are blissfully unaware that years past 1999 may exist.
This causes man pages to be supposedly printed in the year 19118.