Sata Drive + EIDE Mainboard

About 18 months ago I bought a Seagate SATA HD and
started using in external enclosure. After about a
year (programmed by warranty I supose) it stopped
working and I brought it into the computer case
and attached to PCI card via SATA cable. The Intel
board has no Sata connection. It worked for few
months and then stopped. The drive itself is
running and the case warm. PCI card appears in
hardware list - has no brand name but when in the
3rd slot from video card Device Mgr says its a
Intel ICH4/ICH4-M SMBus Control..... The few
instructions included were useless.

Two half size CDs came with that order - one was
deep blue color with Software Driver Ver: 3.8
printed on. It contains lots of drivers. The other
CD is black and has two rows of drivers printed on
it. The main title on that CD was USB Series
Driver 2007-3. It has USB, IDE, SATA drivers for
Audio, Data Transfer, Card readers etc. One choice
offered was Via Raid and I tried that too. It
installed but has a yellow blob.

I tried to reinstall on Win2000 and it found what
it claimed was a good driver match but again there
was a yellow blob.

This was error ms:
3249        PCI\VEN_1106&DEV_3249&SUBSYS_32491106&REV_50&29817089&0&10F0        10

Thx for help.

wrote:


Are you stating that if the card is in another slot, you no
longer see the Intel ICH4 SMBus control listed in Device
Manager? If so, do you see it again if the card is totally
removed from the system? I ask because the Intel SMBus
Control is a different part of the computer not related to
the PCI SATA card.



If the card does not have a heatsink permanently attached to
the RAID controller chip on it, you can do a web search for
that part number to identify it, or post them here if a web
search isn't finding it. However from the info you posted
below this may not be necessary.


3249        PCI\VEN_1106&DEV_3249&SUBSYS_32491106&REV_50&29817089&0&10F0        10

It appears to be a Via VT6420/6421 based RAID card, try the
following driver with the card in the slot it originally
worked in (you might also inspect the card electrical
contacts and the contacts in the slot) but if it just
suddenly refused to work one day without any massive changes
to windows (like installing a service pack) and you didn't
change the motherboard or RAID card bios (flash a different
one to the EEPROM) then I would suspect the card itself has
died.

However, you should power off and unplug the drive seeing
if the card will install ok with nothing connected to it
yet. When you turn the system on, see if you can enter the
RAID bios menu from the card, if you cannot even do that
then there seems no hope of it being just a windows driver
problem. That is, if you are sure it is supposed to be a
RAID capable card, if it did previosly display a message
when booting that you could press a certain key to set up
the RAID arrangement at the end of the BIOS POST and
enumeration screens.

http://www.viaarena.com/default.aspx?PageID=420&OSID=3&CatID=1240&SubCatID=117

Thanks Kony for that quick response.

kony wrote:

My idea that "Intel ICH4/ICH4-M ....." was associated with the PCI card
was nonsense. However, the third PCI slot was associated with that name
and that's where the SATA card was located at the time. I moved the card
to another slot and that Intel ICH4... name stayed put on the third
slot. I should have known better.


The card has no heat sink. It's small and slim - little energy required.

3249        PCI\VEN_1106&DEV_3249&SUBSYS_32491106&REV_50&29817089&0&10F0        10

You were pretty close. The card was so close to another one that I had
to dig it out to see VT6421A on the chip - no other company markings.
The mother board was the same one as before and the third slot was where
the card was when it previously worked. It did not work there when I
installed it this time. It turned out that I did not need to flash. More
below.


When adding and removing cords and components, almost always I shut
down. I moved the card to the PCI 1 slot and to my surprise it worked.
I then installed the RAID prog and it and all the hard disks are now
working ok, except one drive. The problem with it is that I encrypted a
folder on it over a year ago and the hassle of the past month has fuzzed
up my frazzled brain. The properties of the files indicate read only
but even that means nothing - all pages are blank. The encryption was
from Win2K. Looks like I'll now have to start on that task.

One thing I learned was that if an encrypted file is copied to an
external drive it maintains the encryption there.

Thanks again Kony for your help and have a great weekend.

RFR wrote:

http://pciids.sourceforge.net/pci.ids

1106 VIA Technologies, Inc.
        3249 VT6421 IDE RAID Controller

It is indeed a VIA chip.

What you need to do, is check the jumper on the Seagate drive. There is
probably room for two jumpers. One jumper controls "spread spectrum" and
you don't need to play with that one. The second jumper is called
"Force 150", and it is used to set the communications rate on the
cable. When mixing VIA chipsets, with SATA2 drives, you need to
install the Force 150 jumper, so that the cable operates at
150MB/sec. Once you do that, the drive may be detected.

You should also be able to look at the PCI card itself, and check
the writing on the main big chip. You should see "VT6421" on there
somewhere.

Look on the CD for a VIA storage driver of some sort.

Paul

Paul wrote:

Thank you Paul for your help.

The VIA chip had the number: VT6421A, so you were pretty close. By
moving the SATA card to a new slot - slot 1 - it started to work again
and I finally have all drives running again. I did not need to change
the jumper on the SATA drive - it worked ok as it was. There may be a
faster setting but what I have now is all I need.

Now I have an encryption problem (fortunately for one BIG folder only)
to solve. I set it up a year ago and a lot has happened since. At that
time after I logged into the computer I was aware of no restrictions on
that folder at all. Security settings show R only. Now with things moved
around I cannot access those files at all. However, I'll start worrying
about that one next week.

Thanks again and have a great weekend :-)