1. You are viewing our forum as a guest. For full access please Register. WindowsBBS.com is completely free, paid for by advertisers and donations.

PCI controller card

Discussion in 'PC Hardware' started by crown711, 2004/08/25.

Thread Status:
Not open for further replies.
  1. 2004/08/25
    crown711

    crown711 Inactive Thread Starter

    Joined:
    2002/01/07
    Messages:
    46
    Likes Received:
    0
    i have bought a new 80gb maxtor diamond plus 9 ata/133 harddrive and can't get it working,i am using winxp pro w/ecs k7s5a.
    it looks like to me the new hdd is too fast for the MOBO.
    would a ata pci card 133 help?
     
  2. 2004/08/26
    mattman

    mattman Inactive Alumni

    Joined:
    2002/06/10
    Messages:
    8,198
    Likes Received:
    63
    Hi,

    Is the drive recognised in the BIOS? You can go into the BIOS settings and check there. If your BIOS has it, you can try "Autodetect drive ". I would expect that an ATA 133 drive should originally be set at ATA 100 to be "seen" by the majority of BIOSes. There will be a utility to download at Matrox to change the ATA (ATA 133 is "UDMA 6 "; ATA 100 is "UDMA 5 ").

    Your motherboard is only UDMA 5 (ATA 100) capable, so if you wanted to utilise the ATA 133 setting, yes, you would need a PCI IDE card...but...you would probably not notice the difference if you only ran the drive at ATA 100.

    Your drive may be "factory formatted" or completely blank. You would need the Maxtor utilities to partition and format it. The utilities are PowerMax and MaxBlast. Avoid installing the Dynamic Drive Overlay (Disk Manager) in MaxBlast, it may cause problems later.

    Let me know if any of this is "fuzzy ".

    Matt
     
    Last edited: 2004/08/26

  3. to hide this advert.

  4. 2004/08/26
    Chiles4

    Chiles4 Inactive

    Joined:
    2002/01/09
    Messages:
    654
    Likes Received:
    1
    I used to run that board in my kid's rig and half the time it wouldn't recognize the drive that was a permanent part of that rig if I messed with it at all! If I disconnected the drive or connected another drive, I couldn't get the board to recognize the original drive.

    There was only 1 thing for me to do and it always worked eventually - and that was to clear the CMOS. As far as I remember, that always did the trick.
    I attribute it to another flakey problem of the K7S5A, of which there have been many.

    Gary
     
Thread Status:
Not open for further replies.

Share This Page

  1. This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
    By continuing to use this site, you are consenting to our use of cookies.