public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Guest section DW <dwguest@win.tue.nl>
To: Josh Fryman <fryman@cc.gatech.edu>, linux-kernel@vger.kernel.org
Subject: Re: IDE drives mis-reporting size... bug or feature?
Date: Wed, 20 Jun 2001 20:34:44 +0200	[thread overview]
Message-ID: <20010620203444.A22204@win.tue.nl> (raw)
In-Reply-To: <3B30E4CC.3794331@cc.gatech.edu>
In-Reply-To: <3B30E4CC.3794331@cc.gatech.edu>; from Josh Fryman on Wed, Jun 20, 2001 at 02:00:44PM -0400

On Wed, Jun 20, 2001 at 02:00:44PM -0400, Josh Fryman wrote:

> this is an odd one.  i think it's technically a feature
> but might be perceived instead as a "bug".  anyway, i've
> got a pair of Ultra100 Maxtor 52049h4 20GB drives, on a 
> Promise Ultra 100 (PDC20267) controller.  
> 
> the drives were popped in with the jumper on for the
> 4096 cylinder limit forced.
> 
> the promise controller recognizes the drives on boot-up
> init as being what they are - ~20GB - and continues on
> merrily.  
> 
> Windows 2000 recognizes the drives as ~2GB in size, due to
> the jumper.  it's observing the 4096cyl limit on the drive
> in some way.  (remove the jumper and it sees ~20GB too.)
> 
> Linux 2.4.3 recognizes the drives as ~20GB regardless of
> the jumper.
> 
> so, is this a bug or feature?  is windows or linux not 
> working right here?  what *should* be seen with the drive
> jumpered such?

The jumper is to overcome a BIOS defect.
The operating system should see the true size.
In order to get Windows to see the true size you may need MaxBlast
or similar boot manager stuff.

      reply	other threads:[~2001-06-20 18:35 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-20 18:00 IDE drives mis-reporting size... bug or feature? Josh Fryman
2001-06-20 18:34 ` Guest section DW [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20010620203444.A22204@win.tue.nl \
    --to=dwguest@win.tue.nl \
    --cc=fryman@cc.gatech.edu \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox