Difference between revisions of "OSWORD &FC"

From BeebWiki
Jump to: navigation, search
(Rewrote transaction description.)
m (Added template.)
 
Line 20: Line 20:
  
 
==See also==
 
==See also==
* [[OSWORD &FA]]
 
* [[OSWORD &FB]]
 
* [[OSWORD &FD]]
 
* [[OSWORD &FE]]
 
* [[OSWORD &FF]]
 
 
* [http://mdfs.net/Software/Tube/Utils/ OSWORD &FC source code]
 
* [http://mdfs.net/Software/Tube/Utils/ OSWORD &FC source code]
 
* [http://mdfs.net/Docs/Comp/BBC/Oswords OSWORDs list at mdfs.net]
 
* [http://mdfs.net/Docs/Comp/BBC/Oswords OSWORDs list at mdfs.net]
 
+
{{TubeOSWORD}}
 
[[User:Jgharston|Jgharston]] 14:28, 26 May 2009 (UTC)
 
[[User:Jgharston|Jgharston]] 14:28, 26 May 2009 (UTC)
 
[[User:Jgharston|Jgharston]] ([[User talk:Jgharston|talk]]) 10:55, 17 December 2024 (CET)
 
[[User:Jgharston|Jgharston]] ([[User talk:Jgharston|talk]]) 10:55, 17 December 2024 (CET)

Latest revision as of 11:45, 17 December 2024

OSWORD &FC (252) DOS CRTC Control

This OSWORD call is installed by the 80x86 DOS BIOS.

Commands are sent from the 80x86 via Tube Register 2 within the OSWORD protocol, so cannot be called through the normal OSWORD mechanism. The transaction must be done manually by the client by sending through Tube Register 2:

   &08 : Start OSWORD transaction
   &FD : OSWORD call &FD
   &00 : TxLen=0
   xxx : Send a series of commands
   &00 : RxLen=0, terminate the OSWORD call

Commands

  • b7=0 : program CRTC, command specifies register, next byte sent is the CRTC data
  • &FC : write to mouse port (unimplemented)
  • &FD : initialise event handler
  • &FE : initialise mouse driver
  • &FF : finish. All other commands also finish the transaction.

See also

Tube OSWORD calls

Jgharston 14:28, 26 May 2009 (UTC) Jgharston (talk) 10:55, 17 December 2024 (CET)