| Author |
Message |
Danny
Guest
|
 Posted:
Sun Nov 06, 2005 8:26 am Post subject:
maximum hard drive size in Latitude cpi |
|
|
I have done some searching, but have found no definitive reference to
the maximum size drive that my Latitude cpi r400gt laptop will
recognize.
Please forgive my overlooking some obvious repository of info
somewhere. I just don't want to invest in a 80gig drive only to find
out that the bios will never under any circumstance see anything beyond
30 or 40.
Anyone have any personal experience with this laptop, or know where to
find this answer?
I also plan to have SUSE linux 9.0 sharing this drive with Windows 98
if this has any bearing here.
Thanks in advance. Danny |
|
| Back to top |
|
 |
Peter T. Breuer
Guest
|
| Posted:
Sun Nov 06, 2005 4:20 pm Post subject:
Re: maximum hard drive size in Latitude cpi |
|
|
Danny <dannyandsherri@gmail.com> wrote:
| Quote: | Please forgive my overlooking some obvious repository of info
somewhere. I just don't want to invest in a 80gig drive only to find
out that the bios will never under any circumstance see anything beyond
30 or 40.
|
Does it matter to you? The bios is only responsible for booting a couple
of files, which I am sure you can place within 30 or 40GB of the start
of the disk if push comes to shove!
After the bios has booted an o/s, the o/s does the disk i/o via linear
addressing on the appropriate bus, not using the bios! You really need
to persuade the bios to boot the disk, not of the size of the disk.
| Quote: | I also plan to have SUSE linux 9.0 sharing this drive with Windows 98
if this has any bearing here.
|
Yes it does - it means that you don't care what the bios thinks.
So long as it doesn't actively make its little brain hurt (in which
case you can likely jumper the disk for 8GB, I would imagine), you can
tell the kernel whatever you like about the size of the disk, via any
fake geometry for it you like to dream up.
Peter |
|
| Back to top |
|
|
Barry OGrady
Guest
|
| Posted:
Sun Nov 06, 2005 4:39 pm Post subject:
Re: maximum hard drive size in Latitude cpi |
|
|
On 5 Nov 2005 23:54:15 -0800, "Danny" <dannyandsherri@gmail.com> wrote:
| Quote: | I have done some searching, but have found no definitive reference to
the maximum size drive that my Latitude cpi r400gt laptop will
recognize.
Please forgive my overlooking some obvious repository of info
somewhere. I just don't want to invest in a 80gig drive only to find
out that the bios will never under any circumstance see anything beyond
30 or 40.
Anyone have any personal experience with this laptop, or know where to
find this answer?
I also plan to have SUSE linux 9.0 sharing this drive with Windows 98
if this has any bearing here.
|
I installed a 40 gig hd in a Latitude cpi using a boot manager.
| Quote: | Thanks in advance. Danny
|
Barry
=====
Home page
http://members.iinet.net.au/~barry.og |
|
| Back to top |
|
|
John Doue
Guest
|
| Posted:
Sun Nov 06, 2005 8:09 pm Post subject:
Re: maximum hard drive size in Latitude cpi |
|
|
Peter T. Breuer wrote:
| Quote: | Danny <dannyandsherri@gmail.com> wrote:
Please forgive my overlooking some obvious repository of info
somewhere. I just don't want to invest in a 80gig drive only to find
out that the bios will never under any circumstance see anything beyond
30 or 40.
Does it matter to you? The bios is only responsible for booting a couple
of files, which I am sure you can place within 30 or 40GB of the start
of the disk if push comes to shove!
After the bios has booted an o/s, the o/s does the disk i/o via linear
addressing on the appropriate bus, not using the bios! You really need
to persuade the bios to boot the disk, not of the size of the disk.
|
I am not sure I understand what you mean here. If you mean to say that
as long as the disk boots, the size seen by the Bios does not matter and
that the OS will be able to use all the usable capacity of the disk,
this is big news to me. My understanding and my experience are that if
you want to use the full size of a disk and if the bios recognizes only
part of it, you need to use a driver like Disk Manager, which exacts a
heavy toll on performance.
The question from Danny appears to me to be, what is the maximum size I
can buy for my machine. I do not have the answer, but someone certainly
knows those magic numbers.
snip
Regards
--
John Doue |
|
| Back to top |
|
|
Barry OGrady
Guest
|
| Posted:
Sun Nov 06, 2005 11:23 pm Post subject:
Re: maximum hard drive size in Latitude cpi |
|
|
On Sun, 06 Nov 2005 14:09:22 GMT, John Doue <notwobe@yahoo.com> wrote:
| Quote: | Peter T. Breuer wrote:
Danny <dannyandsherri@gmail.com> wrote:
Please forgive my overlooking some obvious repository of info
somewhere. I just don't want to invest in a 80gig drive only to find
out that the bios will never under any circumstance see anything beyond
30 or 40.
Does it matter to you? The bios is only responsible for booting a couple
of files, which I am sure you can place within 30 or 40GB of the start
of the disk if push comes to shove!
After the bios has booted an o/s, the o/s does the disk i/o via linear
addressing on the appropriate bus, not using the bios! You really need
to persuade the bios to boot the disk, not of the size of the disk.
I am not sure I understand what you mean here. If you mean to say that
as long as the disk boots, the size seen by the Bios does not matter and
that the OS will be able to use all the usable capacity of the disk,
this is big news to me. My understanding and my experience are that if
you want to use the full size of a disk and if the bios recognizes only
part of it, you need to use a driver like Disk Manager, which exacts a
heavy toll on performance.
The question from Danny appears to me to be, what is the maximum size I
can buy for my machine. I do not have the answer, but someone certainly
knows those magic numbers.
|
You are right. The bios limits the size the O/S can see due to the number of
bits used, but an overlay can overcome that.
| Quote: | snip
Regards
--
John Doue
|
Barry
=====
Home page
http://members.iinet.net.au/~barry.og |
|
| Back to top |
|
|
Peter T. Breuer
Guest
|
| Posted:
Sun Nov 06, 2005 11:58 pm Post subject:
Re: maximum hard drive size in Latitude cpi |
|
|
John Doue <notwobe@yahoo.com> wrote:
| Quote: | Peter T. Breuer wrote:
Danny <dannyandsherri@gmail.com> wrote:
Does it matter to you? The bios is only responsible for booting a couple
of files, which I am sure you can place within 30 or 40GB of the start
of the disk if push comes to shove!
After the bios has booted an o/s, the o/s does the disk i/o via linear
addressing on the appropriate bus, not using the bios! You really need
to persuade the bios to boot the disk, not of the size of the disk.
I am not sure I understand what you mean here. If you mean to say that
as long as the disk boots, the size seen by the Bios does not matter and
that the OS will be able to use all the usable capacity of the disk,
|
That's correct - modulo your o/s of course. But indeed, modern o/s's do
not use the bios calls to access the disk. That would be horribly
slow! I dn't think any o/s since dos and windows 3.0 (or whatever) has
even tried to do things that way.
| Quote: | this is big news to me. My understanding and my experience are that if
you want to use the full size of a disk and if the bios recognizes only
part of it, you need to use a driver like Disk Manager, which exacts a
|
I've no idea what it would do - is that some windows particular thing
or a piece of bot record code that is run before anything else?
| Quote: | The question from Danny appears to me to be, what is the maximum size I
can buy for my machine. I do not have the answer, but someone certainly
knows those magic numbers.
|
Anyone that fits, is the answer. The worst that can happen is that the
bios, when interrogating the disk, gets size values so big that it
hits a bug in the bios, which then falls over. In that case one
generally choses to boot from floppy or update the bios!
It is rather more usual to choose to forcibly set the disk size for the
bios to some small c/h/s number in order to avoid frightening it, and
tell the o/s kernel the real size (or let it figure it out for itself
when it talks to the bus/controller). This in principle shuld work for
all o/s's ever made since DOS and windows 3.0, but I really can't speak
for MS (I can speak for linux, freebsd, solaris86, netbsd, etc.). But
then again, it is really unlikely that the bios does not grok
32-bit addressing (LBA32), so it is really unlikely that there will
ever be any problem.
Peter |
|
| Back to top |
|
|
John Doue
Guest
|
| Posted:
Mon Nov 07, 2005 12:12 am Post subject:
Re: maximum hard drive size in Latitude cpi |
|
|
Peter T. Breuer wrote:
| Quote: | John Doue <notwobe@yahoo.com> wrote:
Peter T. Breuer wrote:
Danny <dannyandsherri@gmail.com> wrote:
Does it matter to you? The bios is only responsible for booting a couple
of files, which I am sure you can place within 30 or 40GB of the start
of the disk if push comes to shove!
After the bios has booted an o/s, the o/s does the disk i/o via linear
addressing on the appropriate bus, not using the bios! You really need
to persuade the bios to boot the disk, not of the size of the disk.
I am not sure I understand what you mean here. If you mean to say that
as long as the disk boots, the size seen by the Bios does not matter and
that the OS will be able to use all the usable capacity of the disk,
That's correct - modulo your o/s of course. But indeed, modern o/s's do
not use the bios calls to access the disk. That would be horribly
slow! I dn't think any o/s since dos and windows 3.0 (or whatever) has
even tried to do things that way.
this is big news to me. My understanding and my experience are that if
you want to use the full size of a disk and if the bios recognizes only
part of it, you need to use a driver like Disk Manager, which exacts a
I've no idea what it would do - is that some windows particular thing
or a piece of bot record code that is run before anything else?
|
Then I suggest you get some information about the problem. Most users,
like it or not (and I regret it) are using Windows, and if the Bios sees
only say 6G, so will MS operating systems. I would think things are not
different with Linux and other systems, but I readily admit, I do not
know. You seem to do ... except when it comes to Windows.
| Quote: |
The question from Danny appears to me to be, what is the maximum size I
can buy for my machine. I do not have the answer, but someone certainly
knows those magic numbers.
Anyone that fits, is the answer. The worst that can happen is that the
bios, when interrogating the disk, gets size values so big that it
hits a bug in the bios, which then falls over. In that case one
generally choses to boot from floppy or update the bios!
|
Sorry, but this is not true. What happens is, first, on most laptops,
there in no way to manually enter a disk size (that was feasible on
desktops a long time ago, probably no more), so the bios limits access
to the disk to the maximum size it has been designed for. Unless you use
a driver as mentionned earlier. Try it for yourself.
| Quote: |
It is rather more usual to choose to forcibly set the disk size for the
bios to some small c/h/s number in order to avoid frightening it, and
tell the o/s kernel the real size (or let it figure it out for itself
when it talks to the bus/controller). This in principle shuld work for
all o/s's ever made since DOS and windows 3.0, but I really can't speak
for MS (I can speak for linux, freebsd, solaris86, netbsd, etc.). But
then again, it is really unlikely that the bios does not grok
32-bit addressing (LBA32), so it is really unlikely that there will
ever be any problem.
|
If you cannot speak for MS OS's, I suggest you mention it clearly in
your posts, since most OP assume we are talking XP, or at worst 2K...!
Regards
--
John Doue |
|
| Back to top |
|
|
William P.N. Smith
Guest
|
| Posted:
Mon Nov 07, 2005 2:15 am Post subject:
Re: maximum hard drive size in Latitude cpi |
|
|
"Peter T. Breuer" <ptb@oboe.it.uc3m.es> wrote:
| Quote: | That's correct - modulo your o/s of course. But indeed, modern o/s's do
not use the bios calls to access the disk. That would be horribly
slow! I dn't think any o/s since dos and windows 3.0 (or whatever) has
even tried to do things that way.
|
As John points out, WinDoze needs BIOS support for large hard drives.
Since the {128,137}G laptop drives aren't out yet, the OP doesn't have
to worry about 48-bit LBA, so I think he's asking if it'll recognize a
drive larger than 8G... |
|
| Back to top |
|
|
Jerry Bloomfield
Guest
|
| Posted:
Mon Nov 07, 2005 8:26 am Post subject:
Re: maximum hard drive size in Latitude cpi |
|
|
On 5 Nov 2005 23:54:15 -0800, "Danny" <dannyandsherri@gmail.com>
wrote:
| Quote: | I have done some searching, but have found no definitive reference to
the maximum size drive that my Latitude cpi r400gt laptop will
recognize.
|
Personally, I have used a 60GB drive in an older Latitude CPi D300XT
that had the latest Dell BIOS. Based on that, your newer CPi R
series system should be able to use any available notebook drive as
long as your system has the latest BIOS as well. |
|
| Back to top |
|
|
Barry OGrady
Guest
|
| Posted:
Mon Nov 07, 2005 8:26 am Post subject:
Re: maximum hard drive size in Latitude cpi |
|
|
On Sun, 6 Nov 2005 18:58:40 +0100, "Peter T. Breuer" <ptb@oboe.it.uc3m.es> wrote:
| Quote: | John Doue <notwobe@yahoo.com> wrote:
Peter T. Breuer wrote:
Danny <dannyandsherri@gmail.com> wrote:
Does it matter to you? The bios is only responsible for booting a couple
of files, which I am sure you can place within 30 or 40GB of the start
of the disk if push comes to shove!
After the bios has booted an o/s, the o/s does the disk i/o via linear
addressing on the appropriate bus, not using the bios! You really need
to persuade the bios to boot the disk, not of the size of the disk.
I am not sure I understand what you mean here. If you mean to say that
as long as the disk boots, the size seen by the Bios does not matter and
that the OS will be able to use all the usable capacity of the disk,
|
That is not the case. Unless you use an overlay the bios will limit how much
of the drive the os can see.
| Quote: | That's correct - modulo your o/s of course. But indeed, modern o/s's do
not use the bios calls to access the disk. That would be horribly
slow! I dn't think any o/s since dos and windows 3.0 (or whatever) has
even tried to do things that way.
|
It would be inefficient to use an overlay when not required.
| Quote: | this is big news to me. My understanding and my experience are that if
you want to use the full size of a disk and if the bios recognizes only
part of it, you need to use a driver like Disk Manager, which exacts a
|
Correct.
| Quote: | I've no idea what it would do - is that some windows particular thing
or a piece of bot record code that is run before anything else?
|
Its code that is stored in the boot record of the hard drive.
| Quote: | The question from Danny appears to me to be, what is the maximum size I
can buy for my machine. I do not have the answer, but someone certainly
knows those magic numbers.
Anyone that fits, is the answer.
|
Noone will fit.
| Quote: | The worst that can happen is that the
bios, when interrogating the disk, gets size values so big that it
hits a bug in the bios, which then falls over. In that case one
generally choses to boot from floppy or update the bios!
|
One may be able to set a link or send a command to make the drive appear
of lower capacity so it can load the overlay which then replaces the bios for
disk i/o.
My AMD K6/500 had a bios limit of 32 gigs, and I wanted to use a 120 and a 60
gig drive. One of the drives used a link and the other a command to appear as
32 gigs each.
| Quote: | It is rather more usual to choose to forcibly set the disk size for the
bios to some small c/h/s number in order to avoid frightening it, and
tell the o/s kernel the real size (or let it figure it out for itself
when it talks to the bus/controller). This in principle shuld work for
all o/s's ever made since DOS and windows 3.0, but I really can't speak
for MS (I can speak for linux, freebsd, solaris86, netbsd, etc.). But
then again, it is really unlikely that the bios does not grok
32-bit addressing (LBA32), so it is really unlikely that there will
ever be any problem.
|
I had to use an overlay to get a 40 gig drive to work in my Latitude CPI.
Barry
=====
Home page
http://members.iinet.net.au/~barry.og |
|
| Back to top |
|
|
Peter T. Breuer
Guest
|
| Posted:
Mon Nov 07, 2005 2:55 pm Post subject:
Re: maximum hard drive size in Latitude cpi |
|
|
John Doue <notwobe@yahoo.com> wrote:
| Quote: | Peter T. Breuer wrote:
John Doue <notwobe@yahoo.com> wrote:
Peter T. Breuer wrote:
Danny <dannyandsherri@gmail.com> wrote:
this is big news to me. My understanding and my experience are that if
you want to use the full size of a disk and if the bios recognizes only
part of it, you need to use a driver like Disk Manager, which exacts a
I've no idea what it would do - is that some windows particular thing
or a piece of boot record code that is run before anything else?
Then I suggest you get some information about the problem. Most users,
like it or not (and I regret it) are using Windows, and if the Bios sees
only say 6G, so will MS operating systems.
|
There is no reason why it should. The disk will say exactly how big it
is when queried directly through the ide controller. Designing an o/s
that did NOT query the controller about the device attached to it would
be willfully perverse.
| Quote: | I would think things are not
different with Linux and other systems,
|
Then you would think wrong.
BTW, it would be difficult to decide to interact with the bios in any
way at all after the o/s has started up (including to get its idea of
how large the disk is), because talking to the bios has to be done with
the cpu in real mode, not the virtual mode that all modern o/s's have
exploited since the 386 became available. It really is difficult.
| Quote: | Anyone that fits, is the answer. The worst that can happen is that the
bios, when interrogating the disk, gets size values so big that it
hits a bug in the bios, which then falls over. In that case one
generally choses to boot from floppy or update the bios!
Sorry, but this is not true. What happens is, first, on most laptops,
there in no way to manually enter a disk size (that was feasible on
desktops a long time ago, probably no more)
|
It's "feasible" on every desktop machine I own, and has always been so
(I still run my 486sx50 TP as a bedside thin client, btw). Laptop
bioses vary in what they allow you to set, which is why I asked you if
the "driver" (surely not!) was a bit of boot record code (which would
maybe fiddle the bios when run, which is before the o/s starts up).
| Quote: | It is rather more usual to choose to forcibly set the disk size for the
bios to some small c/h/s number in order to avoid frightening it, and
tell the o/s kernel the real size (or let it figure it out for itself
when it talks to the bus/controller). This in principle shuld work for
all o/s's ever made since DOS and windows 3.0, but I really can't speak
for MS (I can speak for linux, freebsd, solaris86, netbsd, etc.). But
then again, it is really unlikely that the bios does not grok
32-bit addressing (LBA32), so it is really unlikely that there will
ever be any problem.
If you cannot speak for MS OS's, I suggest you mention it clearly in
your posts, since most OP assume we are talking XP, or at worst 2K...!
|
I assume no such thing - the last time I saw ms windows was about 3.1
days, and it was then to my eyes a horrible imitation of a windowing
interface and what I hear makes it sound to have not progressed.
Peter |
|
| Back to top |
|
|
Peter T. Breuer
Guest
|
| Posted:
Mon Nov 07, 2005 3:06 pm Post subject:
Re: maximum hard drive size in Latitude cpi |
|
|
Barry OGrady <atheist.xxx@gmail.com> wrote:
| Quote: | as long as the disk boots, the size seen by the Bios does not matter and
that the OS will be able to use all the usable capacity of the disk,
That is not the case. Unless you use an overlay the bios will limit how much
of the drive the os can see.
|
The bios does no "limiting" - the bios is not used to talk to the
disk, of course!
The only feasible mechanism for imposing such a limit would be for the
bios to be interrogated as to the disk size while the o/s kernel is
still in real mode, before it starts up properly and the o/s to
use that value. But once it is running it can ask the IDE controller
directly how big the disk says it is, so there is no reason to believe
the bios value.
| Quote: | That's correct - modulo your o/s of course. But indeed, modern o/s's do
not use the bios calls to access the disk. That would be horribly
slow! I dn't think any o/s since dos and windows 3.0 (or whatever) has
even tried to do things that way.
It would be inefficient to use an overlay when not required.
|
I really don't think you understand what you are talking about.
| Quote: | I've no idea what it would do - is that some windows particular thing
or a piece of bot record code that is run before anything else?
Its code that is stored in the boot record of the hard drive.
|
Aha - then yes, it would be just added real-mode boot code that
diddles the bios to lie about the disk size when queried. I doubt
it resides fully on the (tiny) mbr, however. But that's by and by.
| Quote: | One may be able to set a link or send a command to make the drive appear
of lower capacity so it can load the overlay which then replaces the bios for
disk i/o.
|
The bios does not "load an overlay" in the sense I think you mean - the
bios is not used when talking to the disk. The idea is preposterous.
Peter |
|
| Back to top |
|
|
Danny
Guest
|
| Posted:
Mon Nov 07, 2005 3:10 pm Post subject:
Re: maximum hard drive size in Latitude cpi |
|
|
Sorry I wasn't specific enough and left room for such confusion.
I have desktop witha p2l97 motherboard that refused to recognize a
40gig drive without jumpering it down to 30someting gig. It would be a
shame to go out of my way to purchase a new drive, spent the extra
money for a 60 or 80 gig drive only to find that it ABSOLUTELY cannot
be seen as anything over XX. I was hoping that someone had either
personal experience installing a 30 or 40- or knew of a listing from
Dell or wherever that lists an exact limitation. I have Suse 9.0
installed on my desktop, and unless there is a utility that I am
unaware of I still cannot get back that last 7-8 gig lost to the
jumper. Thanks to all who responded. Danny |
|
| Back to top |
|
|
John Doue
Guest
|
| Posted:
Mon Nov 07, 2005 4:03 pm Post subject:
Re: maximum hard drive size in Latitude cpi |
|
|
Danny wrote:
| Quote: | Sorry I wasn't specific enough and left room for such confusion.
I have desktop witha p2l97 motherboard that refused to recognize a
40gig drive without jumpering it down to 30someting gig. It would be a
shame to go out of my way to purchase a new drive, spent the extra
money for a 60 or 80 gig drive only to find that it ABSOLUTELY cannot
be seen as anything over XX. I was hoping that someone had either
personal experience installing a 30 or 40- or knew of a listing from
Dell or wherever that lists an exact limitation. I have Suse 9.0
installed on my desktop, and unless there is a utility that I am
unaware of I still cannot get back that last 7-8 gig lost to the
jumper. Thanks to all who responded. Danny
Danny, |
You have been clear enough. I am not sure I follow Peter (I recognize my
technical limitations in this area) but recognized size limitations due
to bios are a well known problem (see the second link at end of post)
and I am surprised Peter seems to dispute this fact (but may be I
misunderstand him).
What you do not say is, has your desktop the ability to manually enter
the parameters of your disk? If it has, then, you might want to try
entering those parameters (get them on the manufacturer's site) and see
if the disk full size is recognized (before you do, of course, make sure
you have a full backup of your disk).
If, as I suspect, you do not have this ability (which was standard on
older machines, as Peter reminded us), then, your only option is finding
out of the bios manufacturer's site (or your desktop manufacturer) if an
update to your bios is available.
As I mentionned in a previous post, yes, there is a utility that allows
to get back the full capacity of a disk, when part of it is not
accessible due to bios limitations. One of them is called Disk Manager.
IMHO, unless you have no other alternative, it is better not to use such
a utility which has a heavy impact on perfermonce. Check:
but in my case, the performance impact made this impractical. May be
this is not the case on a more modern machine, especially with more
memory. Since at least one version is free (I have it), you could try it
but remember, everything on the disk will be lost and you have to do a
full install of your OS. Your decision.
Regards
--
John Doue |
|
| Back to top |
|
|
Peter T. Breuer
Guest
|
| Posted:
Mon Nov 07, 2005 5:09 pm Post subject:
Re: maximum hard drive size in Latitude cpi |
|
|
John Doue <notwobe@yahoo.com> wrote:
| Quote: | You have been clear enough. I am not sure I follow Peter (I recognize my
technical limitations in this area) but recognized size limitations due
to bios are a well known problem (see the second link at end of post)
|
No they AREN'T. Please stop letting vague concepts step in front of your
frontal cortex! If you don't grok "bios is not used in disk i/o" you
are at a serious disadvantage from the get-go and you need to work on
assimilating that idea first. The bios can do no "limiting", since it is
not used.
What I daresay is happening is that the win o/s starts up with the cpu
in real mode (I don't know why ... to emulate dos?) and asks the bios
how big the disk is, then carries that info over to the multitasking o/s
that takes over in virtual 386 mode. A multitasking o/s cannot run in
real mode. Bios can only be used in real mode. You need to appreciate
those two facts to understand why the idea of the bios playing any
part in disk i/o is preposterous, not to mention fact three: "it would
be ridiculously slow" (it would be a kind of programmed i/o mode, but
since it's got to be done in real mode anyway, everything is dead).
The o/s can perfectly well ask the disk how big it is without asking
the bios anything. To illustrate, here's a query directed at my disk
from my TP:
% sudo hdparm -I /dev/hda
/dev/hda:
non-removable ATA device, with non-removable media
Model Number: IC25N030ATCS04-0
Serial Number: CSH305DADKY0NB
Firmware Revision: CA3OA71A
Standards:
Used: reserved
Supported: 2 3 4 5
Likely used: 5
Configuration:
Logical max current
cylinders 16383 16383
heads 15 15
sectors/track 63 63
bytes/track: 0 (obsolete)
bytes/sector: 0 (obsolete)
current sector capacity: 15481935
LBA user addressable sectors = 58605120
(the LBA addressing mode is the one that even the bios would be asked
to use by the o/s, if it asked the bios to do anything!)
Capabilities:
LBA, IORDY(can be disabled)
Buffer size: 1768.0kB ECC bytes: 4 Queue depth: 1
Standby timer values: spec'd by Vendor, no device specific
minimum
r/w multiple sector transfer: Max = 16 Current = 16
Advanced power management level: 16512
DMA: mdma0 mdma1 mdma2 udma0 udma1 udma2 udma3 udma4 *udma5
Cycle time: min=120ns recommended=120ns
(these are the standard methods of talking to the disk for i/o).
PIO: pio0 pio1 pio2 pio3 pio4
Cycle time: no flow control=240ns IORDY flow
(this is slow "programmed i/o" - the bios is likely to use that, but
since one would have to go to real mode to use the bios, uh, uh, no
way).
control=120ns
Commands/features:
Enabled Supported:
* NOP cmd
* READ BUFFER cmd
* WRITE BUFFER cmd
* Host Protected Area feature set
* look-ahead
* write cache
* Power Management feature set
Security Mode feature set
* SMART feature set
SET MAX security extension
Address offset used (large drive)
Power-Up In Standby feature set
* Advanced Power Management feature set
Security:
Master password revision code = 65534
supported
not enabled
not locked
not frozen
not expired: security count
not supported: enhanced erase
34min for SECURITY ERASE UNIT.
HW reset results:
CBLID- above Vih
Device num = 0 determined by the jumper
Checksum: correct
%
| Quote: | and I am surprised Peter seems to dispute this fact (but may be I
misunderstand him).
|
Quite probably. My typing at you seems to be wasted! Please try and
understand - the "overlay" nomenclature probably comes from MSDOS and is
probably either a bios extension (which could only be used by msdos,
since bios is only available in real mode), or a hook of some interrupt
vector (which could again only be used by msdos, since interrupts hooks
are rewritten to pass interrupts to the o/s by anything more recent
than msdos!). Either way, it's simply either "not used" or "not there"
by the time a more modern o/s gets running.
The only chance the extra boot code has to do something is while the
cpu is still in real mode, before the o/s gets going. It could
conceivably diddle the size parameters for the disk kept in the bios.
That's trivial. One ne then have to suppose that the windows o/s,
while still in the "loader" phase, running in real mode, grabs the
bios data and makes it available in some memory location or register
for its later incarnation as a modern o/s running in 386 virtual mode.
But when up and running, the o/s would have no reason not to query the
disk directly as to what it knows abut itself, as I just did! So the
design of windows must be perverse in that respect.
Peter |
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in