Difference between revisions of "OSWORD &0F"

From BeebWiki
Jump to: navigation, search
m (1 revision)
(Added notes.)
 
(3 intermediate revisions by 2 users not shown)
Line 1: Line 1:
 
[[Category:OSWORD]]
 
[[Category:OSWORD]]
OSWORD &0F (15 ) - Write CMOS clock Acorn Master MOS
+
{{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:
  8 - Set time to value in format "HH:MM:SS"
+
  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"
 
   16 - Set date to value in format "Day,DD Mon Year"
 
   16 - Set date to value in format "Day,DD Mon Year"
   24 - Set time and date to value in format
+
   24 - Set time and date to value in format "Day,DD Mon Year.HH:MM:SS"
  "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==
 +
* [[OSWORD &0E]]
 
* http://mdfs.net/Docs/Comp/BBC/Oswords
 
* http://mdfs.net/Docs/Comp/BBC/Oswords
  
 
[[User:Jgharston|Jgharston]] 12:57, 26 May 2009 (UTC)
 
[[User:Jgharston|Jgharston]] 12:57, 26 May 2009 (UTC)

Latest revision as of 16:56, 21 November 2021

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"
 16 - 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)