Yeah I know it is not the cards fault [ typing doesn't express the tone of humor in blaming the card ] , here is a technical explaination of what I believe is my problem ;
" So, for those of you who are aware of that classic UDMA 40wire vs. 80wire stuff, note that this CF DMA/UDMA affair is quite a different story. If you try to run a DMA-capable CF card in an old PIO-only CF socket, the card doesn't work at all, UDMA2 doesn't help, not even MWDMA, and there's no salvation in automatic fallback to PIO. The CF card is identified by the BIOS and OS, but as soon as the BIOS or the OS attempts some UDMA transfer, that IO transaction immediately grinds to a screeching halt, maybe followed by a series of pathetic messages about timeouts and bus resets. Your only chance out of this mess is by forcing "PIO4 only" in some way, ahead of talking (U)DMA to the card at all (since the last power-up/reset).
Consequently, using a 40pin cable (CF socket wiring) doesn't help, as even that way, BIOS/Windows/Linux attempt the 40pin-compliant UDMA2 (33 MBps) and fail. There are also some higher-end CF cards of the past, featuring high transfer rates, yet uncapable of UDMA, but supporting MWDMA - those are guaranteed to fail as well, with identical symptoms."
Mine was identified by both bios and setup as C:\ but nothing except error if I tried to do anything .
So I will try a PIO mode CF card and see if it works , have to wait a few weeks tho . Funny how the card works fine as a slave . The joys of old stuff , good thing I find it fun .