Based on the tests that I have performed, this is the situation as I currently understand it:
(1) I have TWO samples of the problem Seagate USB2 disk. These disks have their own mains power supply (they are not bus-powered).
(2) Both samples exhibit the same problem, namely that BIBM 1.32 cannot see them when BIBM is booted from a USB3 socket on my Lenovo Ideapad 700-15ISK laptop, and the disk is connected to a USB2 socket. I have also tried other socket combinations, and other USB cables, with the same result.
(3) Windows 10 has no problem seeing and operating either disk. I conclude from the foregoing points that it is unlikely that the disks have developed a hardware fault.
(4) BING on a 12-year-old Sony laptop CAN see the problem Seagate disks, and Windows XP on that laptop can too.
(5) BIBM on the Sony laptop CANNOT see the problem Seagate disks. The ONLY difference between (4) and (5) is the software, i.e. BING versus BIBM.
(6) So the problem seems to be with BIBM. Now the problem could be the BIBM settings, but I compared the BIBM settings with the BING settings, and made them as similar as possible (some BIBM settings don't exist in BING), but this did not make a difference. BIBM still cannot see the Seagate disks.
We now have five USB standards (1.0, 1.1, 2.0, 3.0, 3.1), and for all I know there may have been intermediate minor revisions to these standards. In addition, each manufacturer of USB controller chips will interpret the standard in the way that he believes to be correct. If a standard is written rather imprecisely, different USB controller chips may behave differently in certain circumstances.
The job of the software (BIBM in this case) is to cope with the variations in responses from USB controller chips and USB devices. I suspect that the piece of code in BING that deals with the response from devices like the Seagate disk has been accidentally omitted from BIBM, or (more likely) tests earlier in the processing in BIBM are slightly incorrect, with the result that the code that deals with the Seagate response never gets executed (so BIBM concludes that the response is invalid and does not recognise the device).
This is the Seagate disk:http://www.instructables.com/id/Disasse ... Harddrive/
-- from CyberSimian in the UK
Last edited by CyberSimian
on Sun Aug 14, 2016 9:41 am, edited 1 time in total.