Difference between revisions of "OSWORD &0F"

From BeebWiki
Jump to: navigation, search
(Added subfunction 5.)
(Function code to set date is 15, not 16)
(One intermediate revision by one other user not shown)
Line 1: Line 1:
 
[[Category:OSWORD]]
 
[[Category:OSWORD]]
OSWORD &0F (15) - Write CMOS clock
+
{{PageTitle|OSWORD &0F (15): Write Real-Time clock}}
 
 
 
  On entry:
 
  On entry:
   XY?0=function code
+
   XY?0=length of data passed - function code
 
   XY+1.. value to use.
 
   XY+1.. value to use.
 
  Functions are:
 
  Functions are:
 
   5 - Set time to value in centisecond count since 00:00:00 01-Jan-1900 (where supported)
 
   5 - Set time to value in centisecond count since 00:00:00 01-Jan-1900 (where supported)
 
   8 - Set time to value in format "HH:MM:SS"
 
   8 - Set time to value in format "HH:MM:SS"
   16 - Set date to value in format "Day,DD Mon Year"
+
   15 - Set date to value in format "Day,DD Mon Year"
 
   24 - Set time and date to value in format "Day,DD Mon Year.HH:MM:SS"
 
   24 - Set time and date to value in format "Day,DD Mon Year.HH:MM:SS"
 +
 +
The caller should simply store the length of the passed string at XY?0 and store
 +
the passed string or data at XY+1. The caller must not put any interpretation on
 +
the string and length it passes, that is entirely the responsibility of the code
 +
that implements the call, ''not'' the caller.
  
 
==See Also==
 
==See Also==

Revision as of 01:35, 20 November 2022

OSWORD &0F (15): Write Real-Time clock
On entry:
 XY?0=length of data passed - function code
 XY+1.. value to use.
Functions are:
  5 - Set time to value in centisecond count since 00:00:00 01-Jan-1900 (where supported)
  8 - Set time to value in format "HH:MM:SS"
 15 - Set date to value in format "Day,DD Mon Year"
 24 - Set time and date to value in format "Day,DD Mon Year.HH:MM:SS"

The caller should simply store the length of the passed string at XY?0 and store the passed string or data at XY+1. The caller must not put any interpretation on the string and length it passes, that is entirely the responsibility of the code that implements the call, not the caller.

See Also

Jgharston 12:57, 26 May 2009 (UTC)