Use drive sig rather than HD# suggestion
Posted: Sat Nov 28, 2015 9:37 pm
Just as you have stated in a statement made in the IFW Forum, would it be possible to modify BIBM's hard drive# selection criteria (boot details) to use the drive signature number or the hard drive ID number?
My motherboard BIOS treats a usb/pen drive as hardware ID 0, which pushes all BIBM disk hardware numbers off by one. Two pens installed, BIBM configured drives are off by a count of 2. As a result, even though my system boots to BIBM, BIBM is not usable if I have a pen drive installed. Using the drive sig would fix this and allow any hard drives drive to be connected in any order. Just a suggestion. I understand that this is a BIOS oddity and that the other problem was a Windows oddity, yet the overall problem is similar.
--------------------------------------------------------------------------------------------
Previous Statement:
Was it Visa or 7, Windows started to init drives in parallel to try and
speed boots so drives may end up in a different order. Anyway, you can use
the signature of the drive instead of drive number in your script (using the
#0xAABBCCDD in place of just the number where AABBCCDD is the hex signature
(shown next to the drive in the list in IFW or properties via
details/information) - when using gpt you'd use the {GUID} instead).
My motherboard BIOS treats a usb/pen drive as hardware ID 0, which pushes all BIBM disk hardware numbers off by one. Two pens installed, BIBM configured drives are off by a count of 2. As a result, even though my system boots to BIBM, BIBM is not usable if I have a pen drive installed. Using the drive sig would fix this and allow any hard drives drive to be connected in any order. Just a suggestion. I understand that this is a BIOS oddity and that the other problem was a Windows oddity, yet the overall problem is similar.
--------------------------------------------------------------------------------------------
Previous Statement:
Was it Visa or 7, Windows started to init drives in parallel to try and
speed boots so drives may end up in a different order. Anyway, you can use
the signature of the drive instead of drive number in your script (using the
#0xAABBCCDD in place of just the number where AABBCCDD is the hex signature
(shown next to the drive in the list in IFW or properties via
details/information) - when using gpt you'd use the {GUID} instead).