Towncivilian wrote on 2025-11-11, 19:02:

I flashed a (modified) BIOS 1015.002 and I'm able to consistently use the 4GB of RAM I purchased for this build. Thank you, 0005 […]
Show full quote

I flashed a (modified) BIOS 1015.002 and I'm able to consistently use the 4GB of RAM I purchased for this build. Thank you, 000557A!

I modified it with the same latest versions of the Marvell Yukon PXE option ROM and the VIA VT6240 SATA RAID OROM. I also deleted unnecessary microcode - the BIOS includes microcode for Socket 754 CPUs and also some Socket 940s.

I am still unable to test the onboard Promise SATA RAID controller regardless of the combination of settings I attempt. The controller is detected by Windows but cannot start after installing the driver, in either RAID or IDE mode. I think I will need to remove the Highpoint RocketRAID 1740 card to see if that makes a difference, but then I won't have an OS to boot from. I'll fool with it more another time.

Would you like a benchmark of the RocketRAID 1740 controller, shevalier? I believe it uses a Marvell chip.

Great to hear that you are having success with it!

Would it be possible if you shared the modified bios with me as well? I would love to have a more updated bios.

Thanks for your consideration !

Towncivilian wrote on 2025-11-11, 19:02:

I am still unable to test the onboard Promise SATA RAID controller regardless of the combination of settings I attempt.

I am far from thinking that in 2025 anyone will be using RAID functionality on such hardware.
In this post, @forteller shared firmware for this controller, including pure SATA.
If this firmware allows you to work without drivers, that's the best option.
Re: Promise PCI controller OEM?
PROMISE\bioses\asus-pc-dl\SATA378.bin

Would you like a benchmark of the RocketRAID 1740 controller, shevalier? I believe it uses a Marvell chip.

More tests, good ones and different ones. New screenshots are always interesting. 😀

I believe the BIOS setting for the Promise RAID controller operation mode determines whether the RAID or SATA option ROM is loaded at boot. The BIOS already contains both the RAID and SATA option ROMs. This setting is what I meant when describing my failure to have the computer boot up to Windows, which is connected via the PCI RocketRaid 1740 SATA controller. Having the option set to Legacy IDE shows the SATA option ROM at boot, and the drive connected is detected, but then Windows errors with an NTLDR error despite the hard drive connected to the Promise controller not being included in the boot order. With the operating mode set to RAID, I do not see any option ROM screen at boot, and the controller cannot start once Windows is loaded.

I will benchmark the RR1740 controller when time permits, and share the modified 1015.002 BIOS as well.

Towncivilian wrote on Yesterday, 13:18:

I believe the BIOS setting for the Promise RAID controller operation mode determines whether the RAID or SATA option ROM is loaded at boot. The BIOS already contains both the RAID and SATA option ROMs. This setting is what I meant when describing my failure to have the computer boot up to Windows, which is connected via the PCI RocketRaid 1740 SATA controller. Having the option set to Legacy IDE shows the SATA option ROM at boot, and the drive connected is detected, but then Windows errors with an NTLDR error despite the hard drive connected to the Promise controller not being included in the boot order. With the operating mode set to RAID, I do not see any option ROM screen at boot, and the controller cannot start once Windows is loaded.

I will benchmark the RR1740 controller when time permits, and share the modified 1015.002 BIOS as well.

I have similar problems with Silicon Image.
After installing the driver and removing the controller itself (after testing, for example), boot problems begin that can only be solved by reinstalling Windows.

I went to benchmark the RR1740 card, and now the system won't POST, even after clearing the CMOS. The joys of old hardware... I need to buy a POST analyzer card 😁