Are you sure that isn't AdSCSI (one "D") by ICD? Can you get the manufacturer's ID code for the board?
It's hard to tell from the picture, but does this thing even support autoboot? All I could make out was a two-pin header for the LED. If not, then you'll need to make a boot floppy that has the drivers/handlers in the "Expansion" drawer. ICD's site only shows the TriFecta drive, maybe BBoAH?.
Remembering WB1.2 modes (vaguely), I recall that there were no autobooters. Once 1.3 allowed for this, the ROMs had to be updated on the controllers, and the proper jumpers set. Otherwise, even if you had WB4 shoved in there, it wouldn't autoboot unless the card supported it, but the card would still be ID'd by the OS.
As pointed out, there may be a >=4GB (or even 512MB) issue. Also, a funny thing happened a while back with my brother's GVP A500 unit when he popped in a new Q540: it hung. He played with it until I got there, to no avail. My solution? Wait. It turned out that the GVP had a validation routine that checked the drive, and it took about a good two minutes before it gave up (because it was a blank drive). After the wait, it booted the FaastPrep and ran as advertised. You might just want to let it run for about ten minutes or so to see if this might be the case.
But my best guess is that you have a non-booting controller with limited drive support that'll need some kind of custom startup-sequence to get going.
banzai
