Interesting, the 16MHz Excelerator was a 68000 based design that could make use of a 68881 as if it were a 68020?
I think I finally figured out why the Radius16 needed a driver to work and these Accelerators don't. The 16 was originally a Killy Klip add-on to the 128k-Plus architecture from long before the SE's release. Being piggy-backed to the MoBo CPU meant that one had to be turned off for the Accelerator to run.
Later boards designed for the SE PDS with provision for RAM expansion required the SE's ROMs to be moved from the MoBo to the Accelerator. Moving the ROMs off the MoBo means its CPU just lies there like a Lox while the Accelerator boots from the relocated ROMs! No muss, no fuss, no driver required.
Later accelerators for the L2 Cache Slots of the 6360/6400/6500/5400/5500/TAM also require a driver to shut down the MoBo proc like their Killy Klipped kin.
I think I finally figured out why the Radius16 needed a driver to work and these Accelerators don't. The 16 was originally a Killy Klip add-on to the 128k-Plus architecture from long before the SE's release. Being piggy-backed to the MoBo CPU meant that one had to be turned off for the Accelerator to run.
Later boards designed for the SE PDS with provision for RAM expansion required the SE's ROMs to be moved from the MoBo to the Accelerator. Moving the ROMs off the MoBo means its CPU just lies there like a Lox while the Accelerator boots from the relocated ROMs! No muss, no fuss, no driver required.
Later accelerators for the L2 Cache Slots of the 6360/6400/6500/5400/5500/TAM also require a driver to shut down the MoBo proc like their Killy Klipped kin.