Difference between revisions of "OSBYTE &9D"
m (1 revision) |
m (wdg) |
||
| (3 intermediate revisions by 2 users not shown) | |||
| Line 2: | Line 2: | ||
OSBYTE &9D (157) - Fast Tube BPUT | OSBYTE &9D (157) - Fast Tube BPUT | ||
| + | Write a byte to an open file | ||
X=byte to write Y=file handle | X=byte to write Y=file handle | ||
In OS 1.20 this call simply passes through the normal OSBPUT routine | In OS 1.20 this call simply passes through the normal OSBPUT routine | ||
| + | |||
| + | ;Notes | ||
| + | This call returns immediately when executed on a coprocessor, leaving the | ||
| + | coprocessor free to continue the application, and the host continuing the | ||
| + | operation. Therefore the call does not return a result from the operation.<ref | ||
| + | name="appnote-004">Acorn Computers (June 1992), | ||
| + | ''Application note 004: Tube application note'', p.6.</ref> | ||
| + | |||
| + | Acorn advises that because of this, users who wish to carry out bulk data | ||
| + | transfer between the host and the coprocessor should arrange to hook into | ||
| + | [[BYTEV]] and intercept this call on the I/O processor. To initiate a transfer, | ||
| + | the coprocessor should call OSBYTE &9D with parameters in X and Y for the | ||
| + | intercepting code on the host.<ref name="appnote-004" /> | ||
| + | The BPUT functionality of this call would therefore be supplanted, and become | ||
| + | available only from [[OSBPUT]]. | ||
==See Also== | ==See Also== | ||
* http://mdfs.net/Docs/Comp/BBC/Osbyte80 | * http://mdfs.net/Docs/Comp/BBC/Osbyte80 | ||
| + | |||
| + | ==References== | ||
| + | |||
| + | <references /> | ||
[[User:Jgharston|Jgharston]] 22:12, 26 May 2009 (UTC) | [[User:Jgharston|Jgharston]] 22:12, 26 May 2009 (UTC) | ||
Latest revision as of 12:52, 12 November 2020
OSBYTE &9D (157) - Fast Tube BPUT
Write a byte to an open file X=byte to write Y=file handle In OS 1.20 this call simply passes through the normal OSBPUT routine
- Notes
This call returns immediately when executed on a coprocessor, leaving the coprocessor free to continue the application, and the host continuing the operation. Therefore the call does not return a result from the operation.[1]
Acorn advises that because of this, users who wish to carry out bulk data transfer between the host and the coprocessor should arrange to hook into BYTEV and intercept this call on the I/O processor. To initiate a transfer, the coprocessor should call OSBYTE &9D with parameters in X and Y for the intercepting code on the host.[1] The BPUT functionality of this call would therefore be supplanted, and become available only from OSBPUT.
See Also
References
Jgharston 22:12, 26 May 2009 (UTC)
