After all these years I picked up this problem again. Used a multimeter to check the 86pin CPU slot in the Sidecar. Bingo! Pins 80 and 82 pins didn't make contact. Managed to solder these and voilà, the Sidecar works again.
Lucky you
I received a Sidecar as a gift, more than ten years ago. When I first plugged it in, it too would cause the system to crash when Binddrivers was invoked. I couldn't immediately figure out what was wrong, and since there was no alternative hardware I could have tested it with (it doesn't really connect well to an A500), it subsequently sat on the shelf.
I had bought the A1000 used, and it sported a curious memory expansion which fit into the 68000 CPU socket. In order to use it, you had to run a special program which knew where the memory would show up in the address space and made it available for use. This was likely a major ugly hack, and opening up the A1000 for the first time, I discovered that the previous owner had actually sawed off part of the metal shielding around the main board so that he could stick that memory expansion into the machine.
When I eventually received a MicroBotics memory expansion for the A1000 as a gift, I removed the CPU socket memory expansion hack for good. And out of curiousity, I also tried the Sidecar again. Guess what, it worked perfectly. What kept crashing the system was the awful CPU socket memory expansion that didn't even support AutoConfig.
It has been a very long time since I powered up the Sidecar. Maybe I'm going to take it out of storage over the holidays
