Vampire 500 V2+ compatablity with other expansions????

[SpeedGeek]

One should be very carefully distinguish two things: First, the lack of proper announcement of the hardware available on the vampire itself ("no autoconfig"), and second, the abilitiy of the board to identify other autoconfig boards in the system.

The former is lack of maturity of the vampire system, though it does not prevent per se other autoconfig hardware in the chain from working.

The second would be a more serious defect of which I hope that it does not occur. This is because autoconfig itself is not controlled by the vampire, but by the buster chip on the mainboard.

The A500 doesn't have a Buster chip but was designed to support one Auto-config device on it's 68000 expansion bus. Only the Vampire designers know exactly how their custom FPGA logic works, but there is really no (good) reason why it should not support Auto-config.

One possible issue is the A2000/A500 expansion.library support for anything beyond ZorroII 24 bit addressing (e.g. ZorroIII 32 bit addressing).

[SpeedGeek]

That part of expansion is at least identical over all versions, i.e. decoding of the Z-III extended flags in the config defs. It would not make much of a difference anyhow as the A2000 does not have the ability to address anything beyond the 24-bit space on its Zorro.

Well, since there are different model specific versions of expansion.library it certainly implies that the model specific memory maps are an issue. But even if this is not an issue for the latest versions of expansion.library it could be for older library versions.

... and even though the A500/A2000 motherboards are limited to the ZorroII 24 bit address space accelerators with 32 bit CPUs can access 32 bit local bus hardware which could be implemented in ZorroIII format.