Prev: NF7 rev.2 report
Next: TH7 -II
From: David Bahde on 11 Jun 2009 18:12
Paul <nospam(a)needed.com> wrote:

>I can tell you what is in my Device Manager, but mine is a different
>chip, so the Devices will have different numbers. (The SATA controller
>cannot have the same number. The IDE might, because that part of the
>design probably hasn't changed.
>
>IDE ATA/ATAPI controllers
> Primary IDE Channel atapi.sys, storprop.dll (sounds like default Microsoft) 1106-0571
> Secondary IDE Channel (same as previous one)
> VIA Bus Master IDE Controller - 0571 videX32.sys (available in Falcon driver or Hyperion Pro chipset)
> VIA Serial ATA Channel 0 - 5372 ViPrt.sys (available in SataIDE folder of Hyperion Pro, not Falcon)
> VIA Serial ATA Channel 1 - 5372 (same as previous one, 1106-5372 hardware id)
> VIA Serial ATA Controller - 5372 ViBus.sys 1106-5372
>
>So it looks like the IDE came from my Microsoft WinXP SP3 disc, while
>the SATA ones from the Hyperion Pro 5.12 chipset driver package
>(not the RAID, and not the Falcon package).
>
>I found a copy of your manual. On the first attempt, I got a bogus error
>from the download server. A second click succeeded.
>
>ftp://ftp-usa.abit.com.tw/pub/download/manual/english/vt7.zip
>
>I see an item in the BIOS screens
>
> "VIA Onchip IDE Devices" BIOS setup page
>
> SATA RAID ROM [enable,disable]
>
>My board is a bit different, in that it has two SATA
>related settings. One apparently controls the RAID setup
>screen, while a second setting puts the controller in
>RAID or non-RAID mode. It is possible the enumeration is
>reported differently, depending on that setting, and
>that is how Device Manager figures out which driver
>is appropriate. On your board, it could be that the
>two are tied together (which makes more sense anyway,
>that one BIOS setting enable or disable RAID mode).
>
>Yours could be 1106-3149 hardware ID, just a guess. 1106 = VIA
>and 3149 is officially listed at VT6420 (logic block used in
>a separate chip, as well as inside some Southbridges).
>
>http://pciids.sourceforge.net/pci.ids
>
>If I look in the Hyperion Pro package, the file ViPrt.inf is probably
>what has installed my SATA ports. The hardware IDs listed as valid are:
>
>%PCI\VEN_1106&DEV_3149&CC_0101.DeviceDesc%=StorageBus_Inst_x32, PCI\VEN_1106&DEV_3149&CC_0101
>%PCI\VEN_1106&DEV_3349&CC_0101.DeviceDesc%=StorageBus_Inst_x32, PCI\VEN_1106&DEV_3349&CC_0101
>%PCI\VEN_1106&DEV_0581&CC_0101.DeviceDesc%=StorageBus_Inst_x32, PCI\VEN_1106&DEV_0581&CC_0101
>%PCI\VEN_1106&DEV_0591&CC_0101.DeviceDesc%=StorageBus_Inst_x32, PCI\VEN_1106&DEV_0591&CC_0101
>%PCI\VEN_1106&DEV_5287&CC_0101.DeviceDesc%=StorageBus_Inst_x32, PCI\VEN_1106&DEV_5287&CC_0101
>%PCI\VEN_1106&DEV_5324&CC_0101.DeviceDesc%=StorageBus_Inst_x32, PCI\VEN_1106&DEV_5324&CC_0101
>%PCI\VEN_1106&DEV_5337&CC_0101.DeviceDesc%=StorageBus_Inst_x32, PCI\VEN_1106&DEV_5337&CC_0101
>%PCI\VEN_1106&DEV_5372&CC_0101.DeviceDesc%=StorageBus_Inst_x32, PCI\VEN_1106&DEV_5372&CC_0101
>
>So yours is likely the first one in the list, and mine is the last (since
>my chip can out in the last couple years).
>
>About all I can suggest at this point, is to verify
>the "SATA RAID ROM" in the BIOS is [disabled], and
>see if the driver situation changes.
>
> Paul

Thanks for your help and suggestions.

I tried the things you laid out in this message and made no progress.

So I decided I didn't need to fight this battle: I returned the SATA
drive and purchased an EIDE drive and had it going in about 45 min.

Thanks for your efforts, tips, and suggestions.
First  |  Prev  | 
Pages: 1 2
Prev: NF7 rev.2 report
Next: TH7 -II