BIOS Direct Not Working

User discussion and information resource forum for Image products.

BIOS Direct Not Working

Postby kangarootaco » Mon May 23, 2016 3: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).
kangarootaco
 
Posts: 8
Joined: Sun Mar 08, 2015 3:50 pm

Re: BIOS Direct Not Working

Postby mjnelson99 » Mon May 23, 2016 4:59 pm

I would suggest using Image For Linux instead of IFD.
It might make a difference.

On 5/23/2016 5:38 PM, kangarootaco wrote:
> 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).
>
>
mjnelson99
 
Posts: 771
Joined: Thu Aug 11, 2011 6:24 pm

Re: BIOS Direct Not Working

Postby TeraByte Support » Mon May 23, 2016 10:28 pm

if you don't see the (sata) (pata) indicator on the list of partitions, it
has fallen back to using BIOS. It wouldn't see the NVMe but if the bios
doesn't give it information on what drive is what, it can just give up and
go the BIOS directly.

"kangarootaco" wrote in message news:11579@public.image...

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).

TeraByte Support
 
Posts: 2338
Joined: Thu May 05, 2011 3:37 pm


Return to Image for DOS/Linux/Windows