Weird error message regarding Hard drive....

[Kitros]

In con. panel-->system prop.-->performance:

Message in bottom box:

Drive D: is using MS-DOS compatibilty mode file system:
Drive E: " "
In help/details:


<< If you only see the message Drive X is using an MS-DOS compatibility mode file system on one drive, that drive is using an MS-DOS compatibility (real-mode) driver, which may reduce that drive?s performance. Contact your hardware manufacturer to see if an updated driver is available for your drive. If not, the drive?s performance may be less than optimal, but you can still use it. >>



This is one HDD, that I just Fdisk'd, enebling large disk support.
It's a 7200rpm 20GB HDD by Maxtor that ever since I formatted a few weeks ago, HAS NOT been letting me use as a PRIMARY HD. After installing windows and try to load it, I get an error message in the BSoD mentioning VFAT yada yada not compatible. etc...


What's going on? This has been bothering me for 2 weeks...
Thnks- steveD

 

[Kitros]

^^^'

 

[Henry Kuo]

my friend had exactly the same error. turns out the reason is that he didn't install his promise ata 100 driver correctly. he is using asus a7v

you are using k7v, and from what you say, i will try to make sure the installation of the ata66 driver is correct. that should get rid of the problem. oh yeah, also make sure you installed the most recent 4-in-1 driver. it should be 4.24a

 

[Eli]

It means that Windows thinks you are using some old 16bit drivers, and went into compatiblity mode to &quot;prevent corruption&quot;.

If I remember right, the fix is to search the registry for &quot;NOIDE&quot;, and delete that entry.


If you're getting VFAT errors, don't delete that entry without backing your registry up. If you delete that entry, and get the BSOD, then... there's something not right. I'm afraid I can't help you anymore than that..

 

[DaddyG]

Winblows will do this for several reasons, if the Master Boot Record is not what WIN wants (FDISK /MBR from Boot Floppy should fix). Also if the 32-bit Protected Mode drivers are bad or not found. Lastly, some geometry remapping software (EZBIOS etc) screws up the MBR.