That is, the counter will run for 1 year and 4 months and wrap and thus, it cannot store a "longer" interval of time. (I guess this was ment to hold the time during short downtimes where a timestamp and the current TOY is saved to disk. Given that most downtimes are in the timeframe of minutes..weeks, that'll perfectly work, but it's not useable as a RTC.) With this in mind, ISTR that VMS asks for system time at each reboot. Maybe this is directly connected?

Standard operating procedure on VAX/VMS is to run SET TIME at least once per year. This command writes the current year to SYS.EXE and the month/day/etc to the TOY register. As long as you do a SET TIME before May the following year, you'll be OK. In our case, we should probably write the current year to a known place in the kernel image. Later, Kenn _______________________________________________ Linux-Vax mailing list Linux-Vax@pergamentum.com http://www.pergamentum.com/mailman/listinfo/linux-vax