|A%=0 : Y%=0 : result%=(USR&FFDA)AND&FF||Returns value in result%|
Download the complete list of filing system ids
Note that the Tube protocol for OSWord does not permit passing back the A, X, Y, or Status registers. OSWord calls with numbers greater than &7F should contain the number of parameters to send in the first byte of the parameter block and the number of parameters to receive in the second byte of the parameter block, these will be used by the Tube protocol software to correctly transfer the parameter block without it needing to know anything about the reason code.
To call an OSWord a parameter block is built somewhere in memory first. Then an OSWord call is made:
|X%=block MOD256 : Y%=block DIV256 : A%=callnumber : CALL&FFF1||V set if call unhandled|
Download the complete list of oswords
OSByte calls can be made from the command line (see below) or from within a program by passing the parameters required to the OSByte routine. Note: if param1 or param2 are missed from the command line, then zero will be substituted.
|X%=param1 : Y%=param2 : A%=callnumber : CALL&FFF4||V set if call unhandled|
OSBytes numbered 166 onwards have a read/write action on various important OS variables. In the case of a read
action the value returned is not shown at the command line, so reads from the command line are pointless.
They can be used to set/clear/read individual bits as the action is newvalue = (oldvalue AND param2) EOR param1. Hence
|To read||param1=0 ; param2=255|
|To write||param1=newvalue ; param2=0|
|To alter||param1=mask of bits to set ; param2=mask of bits to discard|
Download the first 128 osbytes (&00-&7F)
Download the osbytes 128 to 165 (&80-&A5)
Download the remaining 90 osbytes (&A6-&FF)
However, it is missing the actual mapping from the corresponding configuration command to the bit in the CMOS, thereby making it necessary for applications writers to deduce this by other means.
Download the Master 128 CMOS byte usage
Download the Master Compact EEPROM byte usage