PCBUILD Archives

Personal Computer Hardware discussion List

PCBUILD@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

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

Print Reply
Subject:
From:
Reply To:
PCBUILD - PC Hardware discussion List <[log in to unmask]>
Date:
Fri, 27 Feb 1998 17:23:36 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (24 lines)
On 27 Feb 98 at 9:00, Dean Kukral wrote:
> I recently had a similar problem.  I was building an essentially new
> pc, and I was using a dos 7 boot floppy trying to fdisk the new 6.4
> WD drive.  Fdisk would seem to run ok, but when I re-started my
> computer, the os would not see the drive for formatting purposes,
> but it would see it to run fdisk!  I do not know what was wrong -
> perhaps a defective boot disk.  I finally ran fdisk from a hard
> drive with W95 on it (temporarily installed) and then it was ok.

This can apparently happen with certain BIOSes (esp Phoenix).
You end up with a partition that win95 GUI uses quite happily but
DOS 7.0 cannot write to. If you run a DOS 6.22 FDISK on it you will
see the partition marked "NON-DOS".
Solution is to FDISK with the /X switch to maintain compatibility
with DOS.

If you like I can send you a document that describes this INT13h bug.

Gerard R Thomas      mailto:[log in to unmask] mailto:[log in to unmask]
Port of Spain        http://www.geocities.com/TheTropics/3829/
Trinidad and Tobago  http://community.wow.net/grt/
PGP Key ID 9DBCDE7D Send message with subject "send pgp" for key
Key fingerprint 83 84 E7 71 E1 05 68 2A  80 B0 54 15 7B AB C3 60

ATOM RSS1 RSS2