PCBUILD Archives

Personal Computer Hardware discussion List

PCBUILD@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Mime-Version:
1.0
Sender:
PCBUILD - Personal Computer Hardware discussion List <[log in to unmask]>
Subject:
From:
Bryan Tyson <[log in to unmask]>
Date:
Sun, 6 Dec 1998 00:53:34 EST
Content-transfer-encoding:
7bit
Content-type:
text/plain; charset=US-ASCII
Reply-To:
PCBUILD - Personal Computer Hardware discussion List <[log in to unmask]>
Parts/Attachments:
text/plain (26 lines)
In a message dated 12/5/98 6:22:30 PM Eastern Standard Time, Wayne writes:

<<  I have used FDISK to partition the disk. This of course doesn't recognize
the
 2.5Gig hard drive I now have in there, it recognizes 504Meg. I figure that's
 fine, I can fix that later. Well it doesn't work. >>

If I were in Wayne's place, I would double check the LBA or block mode setting
in the BIOS, making sure it is enabled.

I had a similar experience that I can't explain. On an a 486 with Intel
Overdrive, I wanted to install a 1.2 gig drive. FDISK would not see the whole
drive, even with block mode enabled in BIOS. Wayne's case somewhat makes sense
with 504 being visible, but in my case it was a strange number, I think 208.

I then used Seagate Disk Wizard to install and partition the drive, and it
succeeded. Going back into FDISK, the whole drive was visible. I have no idea
why.

Bryan S. Tyson
Greenville SC

               PCBUILD mailing list is brought to you by:
                            The NOSPIN Group
                            http://nospin.com

ATOM RSS1 RSS2