Some further work reveals the following:
1. There is no CF driver for the BeOS.
2. With the type of adapter I have (CF drive attached to IDE bus as first slave) you _can_ get BeOS to boot, but it requires going into safe boot screen - hitting F1 when the logo first appears - then setting IDE DMA to OFF. This dramatically slow down all HDD access but does allow read/write to the CF card.
3. I have now transferred both Airman's images to CF and cannot mount them from within the BeOS. This means they are either encrypted or the copy process he used was faulty. Either is possible, reading the BeIA specs says that zipping and encryption is used.
4. Images created from the BeIA devkit don't boot either, but at least I can mount them as CFS partitions from within BeOS and read/write them on the desktop machine.
My biggest problem here is that I'm totally locked out of the Clipper, and have the stone-age BeIA 1.0 version on it. The only chance may be to remove either the NVRAM or DoC and reprogram them. I have the skills for this but not the necessary equipment; adapters for SM chips are rare and I certainly don't have them for my programmer. Nor do I possess SM desoldering gear here, I'd have to find someone who would let me use theirs.
Finally, without a known good image of either (and don't forget, there are no reports of Airman's images having been used successfully as yet) I'd still be guessing.
Hmmm. It gets tricky, doesn't it.
Codefrog, can you get to the terminal or use any kind of networking from your current Slackware image in the Clipper? If so you may be able to hack your way out of this mess. But short of a breakthrough, looks like I'm dead here.