Fdisk problem with new computer

[durbantus]

I fdisked
I set up a C: drive
I formatted this
I then set up a D: drive
I split this into two logical dos drives
I did not format these

I then loaded win me onto C : drive

For reasons I wont go into
I decided to scrap everything and restart all over again

I FORMATTED c: [I know]

So what do I do now to wipe off D: drive and get ready to fdisk from fresh again

If I try to fdisk at mo

I get a flashing warning in dos

"Unable to access drive 1"

The problem is
if I go into fdisk again i cant load any of items

I just get flashing warning in dos

"unable to access drive 1"


To try and resolve this problem i reinstalled win me

within win me system information i can see

c: drive [25,65 gb

d: drive [17.32 gb]

where has other "logical drive gone with remaining 17.32 mb]

I am very confused

Ideally Id like to wipe my hard disk clean and start all over again



under fdisk options I have :
Fdisk options
current fixed disk drive : 1

choose ine of the following
1
2
3
4

Enter choices

Unable to access Drive 1. [ <<<Flashing ]

If i try and use any options
I get this:

current fixed drive 1

unable to access Drive 1 [<<<Flashing]

any ideas

btw I only have one hdd


epox ep 8kha+ mobo
athlon xp 1900 cpu
ibm 60gxp 60 gb udma 100 hd
plex plexwriter 24/10/40a
asus v8200 t5 vid card
sb platinum sound card
768mb crucial pc2100 ddr

 

[hausdave]

Have you tried FDISK /MBR ?

 

[durbantus]

will that reset hard drive to how it was when i recieved it from supplier

thx

 

[bacillus]

are you sure you've got the ide cable connected securely as the source for the error message "unable to access drive 1" ?
if you're really stuck & want back the original "untouched" hdd then go
here & use the low level format utility in the drive fitness & IBM Feature Tool!

 

[durbantus]

thx
ill try that

 

[Mota331]

You can also try the Maxtor MaxBlast software MaxBlast Download it might work, last time I tried it on a NonMaxtor Hdd it wouldn't work. But on Another NonMaxtor drive it did work.

 

[Redwingsguy]

I dont know if IBM does something similar, but I had a b!tch of a time workin my WD drive because of the sector 63 offset