TeraByte Unlimited

should be the number of hard drives that should show up - so if you boot
without it and it shows 1, try 2, if without it it shows 2, try 3.

But even with the forced count, if the BIOS fails requests for that drive
number, it won't show up.

"sigi" wrote in message news:[email protected]...

The Attachments show what I have done. Is there anything wrong or missing?
Does the correct number of drives to be included in SETNUMHD.COM encompass
the removable drives or does it only count internal HDD's and SSD's? And
what about the CD/DVD drive, which is permanently internal?

Should I correct the number to "3" or "2"?

From your answer I take it that what I did was correct. Meanwhile I have tested SETNUMHD.COM 4, 3 and 2. The HDD has not been detected by BIBM.

Are there any relevant BIBM settings I could try?

no, the bios isn't supporting the drive (reporting errors trying to access
it even when forced).

You could try a different drive that isn't formatted GPT just to see if that
bug is what the BIOS maker would consider a feature. At which point, you
need to ask them how to turn off that feature or otherwise fix their bug.


"sigi" wrote in message news:[email protected]...

From your answer I take it that what I did was correct. Meanwhile I have
tested SETNUMHD.COM 4, 3 and 2. The HDD has not been detected by BIBM.

Are there any relevant BIBM settings I could try?

Have you found an error message in my postings concerning BIOS recognition of the GPT HDD? Should there be any? Where?

Is the absence of an error message the "feature" that in your opinion should BIOS makers cause to get busy or what else do you mean by "feature" in this context?

How should I test a non-GPT HDD if I do not dare to meddle with the internal SATA ports? The only way I could think of would be to reformat the existing one, which should be feasible because I have created the validated full disk backup with IFW. But even if i did that, it would not cure the non-recognition of a GPT HDD, which is not acceptable, is it?

if you wanted to test it, you'd just pop in a new drive and see if it shows
up or not, then I'd change the disk type to gpt, reboot and see if it
disappears.


"sigi" wrote in message news:[email protected]...

Have you found an error message in my postings concerning BIOS recognition
of the GPT HDD? Should there be any? Where?

Is the absence of an error message the "feature" that in your opinion should
BIOS makers cause to get busy or what else do you mean by "feature" in this
context?

How should I test a non-GPT HDD if I do not dare to meddle with the internal
SATA ports? The only way I could think of would be to reformat the existing
one, which should be feasible because I have created the validated full disk
backup with IFW. But even if i did that, it would not cure the
non-recognition of a GPT HDD, which is not acceptable, is it?

QUESTION 1
What do you mean by "pop in"? As I said, I do not dare to meddle with the internal SATA ports.

And what about my two other questions? (excuse me if I am being stubborn
but I am rather interested in the answers). I prefer to repeat them here rather
than to quote them. It is a clearer layout (I would highly welcome
if the BBCode were ON):

QUESTION 2
Have you found an error message in my postings concerning BIOS recognition of the GPT HDD? Should there be any? Where?

QUESTION 3
Is the absence of an error message the "feature" that in your opinion should BIOS makers cause to get busy or what else do you mean by "feature" in this context?



TeraByte Support wrote:
> if you wanted to test it, you'd just pop in a new drive and see if it shows
>
> up or not, then I'd change the disk type to gpt, reboot and see if it
> disappears.

snip

"sigi" wrote in message news:[email protected]...

QUESTION 1
What do you mean by "pop in"? As I said, I do not dare to meddle with the
internal SATA ports.

>> Pop in means put a new hard drive in to test. If you don't want to
>> add/remove a drive then you can't test what the BIOS is doing.

And what about my two other questions? (excuse me if I am being stubborn
but I am rather interested in the answers). I prefer to repeat them here
rather
than to quote them. It is a clearer layout (I would highly welcome
if the BBCode were ON):

QUESTION 2
Have you found an error message in my postings concerning BIOS recognition
of the GPT HDD? Should there be any? Where?

>> forcing the drive count won't work if the BIOS calls returns with a
>> failure since the BIOS is saying it doesn't exist.

QUESTION 3
Is the absence of an error message the "feature" that in your opinion should
BIOS makers cause to get busy or what else do you mean by "feature" in this
context?

>> you'd have to see (by testing) if the BIOS is not allowing access to
>> drives with a GPT rather than handing multiple drives. They may consider
>> that a feature instead of bug. If they did, they should allow a way to
>> disable it, if not, they should fix the problem.

You can run "diskinfo" from a DOS boot disk which will return information
about drives it finds. it's on the free downloads page.

TeraByte Support wrote:
> if you wanted to test it, you'd just pop in a new drive and see if it
> shows
>
> up or not, then I'd change the disk type to gpt, reboot and see if it
> disappears.

snip

sigi,

Are you still planning to convert your HD from GPT to MBR/EMBR?

TeraByte Support wrote:
> no, the bios isn't supporting the drive (reporting errors trying to access
> it even when forced).
>
> You could try a different drive that isn't formatted GPT just to see if
> that bug is what the BIOS maker would consider a feature. At which point, you
> need to ask them how to turn off that feature or otherwise fix their bug.
>
>
> "sigi" wrote in message news:[email protected]...
>
> From your answer I take it that what I did was correct. Meanwhile I have
> tested SETNUMHD.COM 4, 3 and 2. The HDD has not been detected by BIBM.
>
> Are there any relevant BIBM settings I could try?



I am quoting this posting because it is shorter than your subsequent ones and because it contains all the statements that your subsequent two postings only explain in more detail. (It would be extraordinarily useful if one could refer to a specific posting by means of a posting number [#1, #2 etc.]. Couldn't you have your forum software changed accordingly?)

I wanted to thank you for the clarification you provided especially in your posting of Sat Aug 22, 2015 7:58 am. I understand now your posting quoted above. I am still undecided as to whether I should pursue this BIOS problem any further. Because of the obvious unwillingness of the notebook manufacturer to concede any changes to his partition scheme which he showed in our telephone conversatíons I tend to believe that the non-recognition of the GPT HDD is rather a feature than a bug and to leave it as it is.

So I will BIBM / IFD let be the master of the MBR SSD with Win 7 and LinuxMint on it and leave the GPT HDD with Win8 or the Upgrade Win10 on it to the Windows Boot Manager, the Windows Disk Management, and IFW for keeping an up-to-date full disk backup.

Brian K wrote:
> sigi,
>
> Are you still planning to convert your HD from GPT to MBR/EMBR?


Brian,
As I pointed out in the preceding posting I tend to leave everything as it is now.

With Secure Boot OFF and CSM ON, the HDD as the first boot device and the SSD as the second, the system will boot into the Win8/10 Boot Manager and allow booting this Windows version directly.

Once in the Win8/10 Boot Manager, ESC will take me to BIBM, from where I can directly boot Win7 or LinuxMint.

Each drive will have its own Extended Partition. the HDD one being administered by Windows Disk Management, the SSD one by BIBM.

Thank you for your assistance, which by the way has acquired a new IFW customer for Terabyte. In will always appreciate your help. Until the next time.