Re: Hard drive limit?


***** charles wrote:
"Vilmos Soti" <vilmos@xxxxxxx> wrote in message

Thanks for the response. I usually check out my hardware in a
DOS/Windows environment since I am much more familiar in that
arena. When the hardware list came up and said 33G when it should
have said 41G I wanted to correct it. M$ fdisk would only "see"
33G of the whole thing so when I MaxBlasted it, that fixed the problem.
MaxBlast has a utility built in that is called "set max size" that cured it.
Funny, the drive seemed to run a lot hotter before I reset it. Now it is
cooler. There seem to be a lot more utilities for stuff like this in the
DOS/Windows world.

Now that I am sure the drive is working properly, it passed all
the diags and when I put Ubuntu on it, if there are any problems, I
will know that they aren't caused by hardware.

thanks,
charles....

FWIW - my older Intel, PII mobo (circa 2000) only recognizes 65Gigs(?)
of my 80GB drive -- the 'updated' win98/me FDisk utility (d/l from
Microshaft's site) can recognize the full size of the 80GB, but my BIOS
still sees only 60 some-odd GBs (yes, the BIOS is the latest available
- circa 2000).

No bother to me, as long as the OSes (Debian Sid + Win98 dual boot)
can/does utilize the whole drive. My Debian install (as of now) happens
to be on the Orig WD drive that was new (9.1GB only) when the system
was made -- but I previously had Debian installed on the 80GB too.

I suspect different translation parameters (LBA) between HDD Manu and
their utilities -- on any drives newer, than say oh, ~1999, one
shouldn't need to enter the CHS in the BIOS, as these newer drives use
ZonedBit recording and LBA to address the locations/regions/tracks.
Therefore the AUTO setting (in the BIOS) should suffice for most every
drive (as long as the drive's *jumpers* are set correctly), as it's
onboard Controller will communicate that info to the BIOS.

Just my .02 ;-)

Regards

.

Relevant Pages

  • Re: HDD Compatibility
    ... and new larger drives appear in the ... BIOS Upgrades ... available expansion slot and then connecting your hard drives to it. ... than having to connect them to the controller card itself. ...
    (alt.comp.hardware.pc-homebuilt)
  • Re: Ruined m-board with bios update
    ... Doubt that you will be back to this post to see this, but if you are, I received an an identical replacement motherboard from Intel today and just finished installing it. ... Plugged all the hard drives into the same connections as the old board and after all the other tiny little connections I turned it on. ... to re-set the clock in the bios and that was no problem. ... Turned power on & inserted recovery CD. ...
    (microsoft.public.windows.mediacenter)
  • Re: Ruined m-board with bios update
    ... Doubt that you will be back to this post to see this, but if you are, I received an an identical replacement motherboard from Intel today and just finished installing it. ... Plugged all the hard drives into the same connections as the old board and after all the other ... The only hitch was re-starting to re-set the clock in the bios and that was no problem. ... Turned power on & inserted recovery CD. ...
    (microsoft.public.windows.mediacenter)
  • Re: Ruined m-board with bios update
    ... drives into the same connections as the old board and after all the other ... bios and that was no problem. ... reactivating on a new motherboard. ... Turned power on & inserted recovery CD. ...
    (microsoft.public.windows.mediacenter)
  • Re: Ruined m-board with bios update
    ... Plugged all the hard drives ... reactivating on a new motherboard. ... Turned power on & inserted recovery CD. ... recovery bios! ...
    (microsoft.public.windows.mediacenter)