Quote:
Originally posted by anindyanuri
Yes, my friend I only focused my problem only on the BIOS part and sought a solution for my specific question but unfortunately you have misunderstood and moved around topics from booting process, linux, etc.
Not understand what do you mean by saying, "Did you actually check what HD size FD3 shows?" I never heared that an operating system is detecting a hard disk as 40 GB after the BIOS of its system recognized it as 32 GB. I am interested to know if you have found it anywhere.
|
This is where you are wrong.
druuna is very right.
I happen to administer many boxes in my university and have seen this many times.
BIOS uses int13 to "see" the disk. I won't get in detail as there are many great articles about this.
Linux doesn't use BIOS routines to access the disk so doesn't have this limitation.
So what is the result ? BIOS reports the disk as 32GB. Lilo/Grub use BIOS to boot (it works ok, unless the kernel is after the 32GB
which doesn't happen frequently) and when the kernel boots it sees the disk as 40GB.
The same thing happens with 200GB (and BIOS sees it as 137GB).
There are many BIOS limitations as J.W. mentioned, so this is not a "take-and-go" case. You have a 486 you get a 200GB disk and
linux will see it. It doesn't work that way, but in most cases when hardware is a few years outdated it works fine.
So the comment "I never heared that an operating ...." is wrong.
Anyway, even druuna is wrong about the whole matter.
This is a forum. People help others because they want to. They don't gain anything.
So, the comment "However, do you have any real solution of my question or just have mailed to increase the mail number?"
is plainly unfair.
