BIOS Direct Not Working
Posted: Mon May 23, 2016 10:38 pm
I'm finding that after installing some new hardware, BIOS Direct mode in Image for DOS 2.99-00 no longer works. By not working I mean the program becomes extremely sluggish, and sometimes totally unresponsive when browsing for image files. When it does start, the speed is extremely slow, as in projecting days for an image restoration to complete.
Hardware details are as follows:
Motherboard: GA-EX58-UD3R Rev 1.0
CPU: Intel Xeon W3680
SATA III Controller: StartTech PEXSAT34RH connected to PCI-e x4 slot.
Hard Drive: Seagate ST3000DM001-1CH166 connected to on-board Intel SATA II controller
SSD: Samsung SSD 850 EVO 1TB connected to StarTech SATA III controller
NVMe Drive: Samsung 950 PRO 256GB connected to PCI-e x16 2.0 slot via generic adapter card.
I believe the described symptoms exist no matter what the source and target drives are. However, if *both* the SSD and HDD are connected to the SATA III controller and the NVMe drive is not connected, then BIOS Direct works. It also works if both are connected to the SATA II controller and the NVMe drive is not connected. Thus it appears that IFD's BIOS Direct mode does not like there to exist more than one drive interface.
Regular BIOS mode works, but it is quite a bit slower than BIOS Direct (when it works).
Hardware details are as follows:
Motherboard: GA-EX58-UD3R Rev 1.0
CPU: Intel Xeon W3680
SATA III Controller: StartTech PEXSAT34RH connected to PCI-e x4 slot.
Hard Drive: Seagate ST3000DM001-1CH166 connected to on-board Intel SATA II controller
SSD: Samsung SSD 850 EVO 1TB connected to StarTech SATA III controller
NVMe Drive: Samsung 950 PRO 256GB connected to PCI-e x16 2.0 slot via generic adapter card.
I believe the described symptoms exist no matter what the source and target drives are. However, if *both* the SSD and HDD are connected to the SATA III controller and the NVMe drive is not connected, then BIOS Direct works. It also works if both are connected to the SATA II controller and the NVMe drive is not connected. Thus it appears that IFD's BIOS Direct mode does not like there to exist more than one drive interface.
Regular BIOS mode works, but it is quite a bit slower than BIOS Direct (when it works).