FDISK ?

Gustavus

Golden Member
Oct 9, 1999
1,840
0
0
If I boot with a recovery disk -- and I have several, some that use high memory, some that don't etc. -- and run FDISK, I get the expected screen saying one or more of the hard disks on this system is larger etc.. But no matter whether I enter Y or N the display goes back to the A prompt. In other words FDISK does not run.

If I let the system boot into Windows 98SE which is what it is set up with, it boots and runs just fine -- with all hard disks present and working. I have checked with Norton that all disks are working OK -- full capacity reported etc.

Beats me. Any suggestions would be appreciated.

Mystery deepens! Thinking that the FDISK file might be corrupt, I made a recovery disk on the other machine -- same result. I then went to an MS DOS prompt in Windows 98 and ran FDISK /STATUS. The HDs and their partitions were correctly reported. I then made new boot disks and a Windows 98 emergency recovery disk on this machine. When the machine boots into DOS from either of them and I run FDISK I get the same screen that it has detected drives larger than 512Meg etc. but no matter which option is chosen, on hitting ENTER the display goes back to the A prompt. I didn't have a problem (so far as I knew) when I started this, but now I am worried that I would not be able to get to my HDs to FDISK or FORMAT if I needed to. If anyone has any suggestions, please let me know.
 

Sukhoi

Elite Member
Dec 5, 1999
15,346
106
106
Are the hard drives detected correctly in the BIOS? Are you using any overlay software on the hard drives?
 

Gustavus

Golden Member
Oct 9, 1999
1,840
0
0
Yes the drives are detected correctly in the BIOS and I am not using any overlay software -- don't need to since my MB is an ABIT BE6 II Rev.2.
The only thing that is slightly different is that my C (boot) drive is on a Promise Ultra 100 controller which is detected correctly in the Bootup. If I run FDISK /system from a MS DOS window it correctly sees the drives, partitions etc.
As best I can tell everything -- except FDISK -- is working fine. I have all sorts of diagnostic and benchmarking software and routinely test everything in sight. Beats me what is going on here.


 

GregMal

Golden Member
Oct 14, 1999
1,427
0
71
I believe I've seen this discussed in the forums before.
I believe the answer was to remove the Promise controller and
hook the H/D to the M/B's IDE controller.
Then do your FDisk and reinstall your OS.
Then reinstall your promise controller.
I know it's kind of a kludge but.......
Greg