VNF3-250 SATA problem

bcherb2

n00b
Joined
Dec 26, 2004
Messages
1
Ive read quite a few SATA problems that are similar, but I cant find one with exactly my problems. Heres my setup

Chaintech VFN3-250 mobo [amd64 3200+ 2x512@400mhz memory]
IDE0 - Master - Maxtor 80gb IDE **[old boot drive]**
IDE0 - Slave - WD "Deathstar" 45gb IDE
IDE1 - Master - WD 20gb IDE
IDE1 - Slave - DVDRW IDE
IDE2 - Master - Maxtor 120gb SATA **[new boot drive]**
IDE3 - Master - None

Heres the problem, when all this is like it apears above, I get an error after the "Verifing DMI Pool..." to "INSERT VALID BOOT DISK" or whatever the exact message is. If I unplug all of the IDE0 then I can boot normally with the SATA into windows, the IDE1 channel works fine. However if I unplug IDE0-Master but leave IDE0-Slave, I get a windows cannot start, corrupt file <windows>/hal.dll warning.

Ive tried messing around with the BIOS in every possible way it seems :-/

HELP!

:confused: :confused: :confused:
 
sorry if this reply is too late, or redundant if you fixed it already, but I had the same issue.

IDE M0 - DVD-RW
IDE S0 - DVD-ROM
IDE M1 - 80GB HITACHI (data/games)
IDE S1 - 60GB Maxtor (pagefile/backups)
IDE M2 - 80GB SATA Maxtor (system)

.. no matter what boot order, or bios config, the only way the SATA drive booted XP was to pull the plug on the IDE || power connectors of channel 1, or disable the IDE channel from within the bios. I switched all devices, swapped slave/master positions, and fiddled with jumper settings on the drives, even manually defined sector/head count. nothing. I lurked on some other forums (amdmb), and someone suggested boot.ini//arc naming - no dice, it's spot on. I even tried a gentoo and centos SATA drive with grub on the boot sector, didn't matter.

Solution? 10.29 bios from chaintech (VN120A19.BIN). Boot order from within the bios, and from pressing 'esc' at the prompt all work perfectly now. I thought everything was great, until i realized that my FPS dropped by as much as 20% in some instances. Aquamark and 3dMark2005 were most greatly affected (big deal), as well as COD. I have an nforce3 rev A2 mcp, don't know if this problem is systemic among certain revisions, bad boards, or whatever.
 
Back
Top