aplmak
Experienced Member
So user Svenska on this board was able to successfully create a little program he calls “ndate” to bring my Altos Xenix 3.2 into this century. At least until 2038… He spent hours and I cannot thank him enough!!! Very talented!!!
I have an issue though.. while he was in my system programming somehow he was able to set the RTC to the actual century as seen here in this first photo. So the entire system RTC and software clock were in 2022! But of course I had to tinker since there is a leap year issue.. and I ran the regular date command to set the date to a year when it had 29 days. At any rate I CANNOT bring the systems RTC back to this century in 2022!!! See the second photo!!
The program he compiled “ndate” works great but it only sets the software date.. not the RTC..
I’ve attached the standard Xenix 3.2 date command which only lets you specify a two digit year. Not sure if that helps.. there are
This is kinda driving me nutz… the system did have the software and real-time clock set to 2022…. I don’t know how it happened but it did… so I cannot find out how to get back in 2022 in the RTC..
The default date command has parameters to set the RTC but again it only allows you to do a two digit year which brings you to 1970.
date -c = Prints the current date from the real-time hardware clock
date -m = Sets the system software clock to the current hardware real-time clock
Anyone have any ideas on how “we” managed to set the RTC originally to the correct date and time??? Maybe parameters need to be added into “ndate” that he created???
I have an issue though.. while he was in my system programming somehow he was able to set the RTC to the actual century as seen here in this first photo. So the entire system RTC and software clock were in 2022! But of course I had to tinker since there is a leap year issue.. and I ran the regular date command to set the date to a year when it had 29 days. At any rate I CANNOT bring the systems RTC back to this century in 2022!!! See the second photo!!
The program he compiled “ndate” works great but it only sets the software date.. not the RTC..
I’ve attached the standard Xenix 3.2 date command which only lets you specify a two digit year. Not sure if that helps.. there are
This is kinda driving me nutz… the system did have the software and real-time clock set to 2022…. I don’t know how it happened but it did… so I cannot find out how to get back in 2022 in the RTC..
The default date command has parameters to set the RTC but again it only allows you to do a two digit year which brings you to 1970.
date -c = Prints the current date from the real-time hardware clock
date -m = Sets the system software clock to the current hardware real-time clock
Anyone have any ideas on how “we” managed to set the RTC originally to the correct date and time??? Maybe parameters need to be added into “ndate” that he created???
Attachments
Last edited:
