Yes, at this point the next step would be trying the card on another motherboard.
However, I am not at all satisfied with what happened
, the report on the Adaptec site describes a situation that I have seen before, a black screen with flashing cursor,
which is a clear conflict between the motherboard and card BIOS.
There is actually a (rather "rude" unfortunately) thing that I neglected to suggest you, and that I'm telling you now ONLY FOR THE RECORD KIDS, DON'T DO THIS AT HOME
, AND I DO MEAN IT, REALLY, REALLY, DON'T DO THIS
(well, at least I told you
An "old" trick when there are conflicts between the BIOS of a board and the one of an add-on card is to remove the BIOS chip from the add-on card ( I mean physically remove the EPROM/EEPROM/FLASH chip from it's socket) in many cases this "downgrades" the card to a "dumb-non-bootable" one, that can be booted from another media through the NTBOOTDD.SYS. Removing the chip may:
damage the chip
damage the card
void the warranty
On the other hand, I would have expected a "NTDETECT.COM failed" error, in a case like this where it seems that it is the driver that fails to "hook" the info reporteed by BIOS (when SCSI BIOS is enabled) or that it fails to detect properly the card/drive (with SCSI BIOS disabled).
It is also possible that being the 320 a fairly recent card, Adaptec's driver lacks the detecting part that older drivers had, one could try fiddling with older releases of the drivers and with drivers for ither cards, but cannot say whether there is a possibility of this approach working.
There is still a possibility, last one I am afraid, attempting to use the "fake signature" or "XP Kansas City Shuffle" method, which is however still largely experimental.
It cannot possibly work when you have not finished the TEXT MODE SETUP (i.e. when you have the problem with \$WIN_NT$.~BT\biosinfo.inf, but it may once you are past it, i.e. when you have the \WINDOWS\biosinfo.inf problem).
I guess your only practical way out at the moment is to keep both drives, with XP in the SATA one and using the SCSI one only for storage (and for the swap file).
If you are still into experimenting, the "XP Kansas City Shuffle" may work, but I think that we have to wait some more time until the procedure is made a bit more easy and follproof, cdob
is actively working on this:http://www.911cd.net...o...c=21242&hl=http://www.boot-land...?...ic=5487&hl=
but I had no time to test the new files/procedure.