Feels like in the Master 128 case, the fix would be for the MOS to only pass on the unknown ones though? The Master 128 always has an RTC so querying the time will always get the value from that. Otherwise, would it really count as an unknown OSWORD? As with any other OSWORD, I figure if you want to override a feature the MOS provides you can hook into OSWORD yourself.Coming from thoughts about the RTC API in the Time&Config thread, if the OSWORD 14 subcall is not recognised, the Master MOS passes it on to sideways ROMS, but if the OSWORD 15 subcall is not recognised, it is silently swallowed. This feels wrong.
In the Compact MOS, as it assumes there is no built-in RTC, OSWORD 14 and 15 first call the sideways ROMs, and if somebody responds that response is returned to the user. As examples, if you have ANFS then it asks the fileserver for the time&date (disconcertingly pausing for 30 seconds if there is no clock!), and SoftRTC and HADFS will return its time&date held in TIME, etc.
It would be a useful improvement to MOS 3.xx for OSWORD 15 to pass unknown calls to other ROMs, and the simplest way to implement this is to do as the Compact MOS does, and make OSWORD 14 and 15 first issue an Unknown OSWORD call, and only if not claimed then do its own thing.
--Tom
P.S. I've added this to the list for my updated MOS versions: https://github.com/tom-seddon/acorn_mos ... /issues/65
Statistics: Posted by tom_seddon — Sun Jan 26, 2025 6:49 pm