Technical docs for hacking inside the Classic Compatibility Environment ("BlueBox")

Go to file

Elliot Nunn feab1fb558 Cautiously process DR2 info Most egregiously, 0100 started as BALDebugStr and became BALFSDispatch. But mostly I think these should be fine. Functions that are not present in the last BlueBox version are now prepended with "-"		2019-03-21 00:07:47 +08:00
README.md	Add readme	2019-03-20 23:11:26 +08:00
blue_abstraction_calls.txt	Cautiously process DR2 info	2019-03-21 00:07:47 +08:00
search_call_sigs.py	Allow force-override of signatures	2019-03-20 23:57:06 +08:00

README.md

BlueBox technical docs

This is a list of prototypes for the functions that make up the Blue Abstraction Layer (BAL) of Apple's BlueBox. BAL function names start with "BAL" and seem to be safe to call from any code, 68k or PowerPC.

PowerPC CFM code should just link to BlueAbstractionLayerLib and call the desired functions that way. Classic 68k code must statically link to some glue that wraps the FE22 trap like so:

	(push four-byte arguments)
	MOVE.L	#selector,d0
	DC.W	$FE22

Note that "selector" is a long, when the selectors are actually shorts. This is to allow the number for four-byte arguments to be passed in the high word, as a stack-blowout-prevention method. By scraping these motifs from shipped 68k code, we have been able to determine the argument count for over 100 of the 602 BAL calls.

All BAL functions return a single 32-bit value.