-
January 9th, 2000, 09:13 AM
#1
IDE Controller and MS-DOS Compatibility Problems
My system displays the following mulfunction message: Drives using
msdos compatibilty mode file system. The problem often occurs on more
than one dive. Usually if it is caused by a driver in config.sys that
window doesn't recognise, and is related to the problem "Compatibility
Mode Paging" and reduces overall system performance. This problem can
occur with an IDE controller that requires serialization between the
primary and secondary IDE channels. The protected-mode drivers for
these IDE controllers can fail to be initialized if one of the
following situations occurs:
CAUSE:
Article Q151911 by microsft knowlede base, suggest, The protected-mode
driver for the hard disk controller was not properly initialized when
you started Windows previously. When this occurs, a NOIDE entry is
placed in the registry, preventing Windows from making future attempts
to initialize the protected-mode driver.
RESOLUTION:
To cause Windows to attempt to reinitialize the protected-mode IDE
driver, remove the NOIDE entry from the following registry key:
HKEY_LOCAL_MACHINE\SYSTEM\CURRENTCONTROLSET\SERVIC ES\VXD\IOS
I executed the resolution, but NOIDE was no where to be found in
registry.
2.Standard Dual PCI-IDE controller displays a yellow exclamation mark,
I removed it from device manager but comes back when system is
restarted.
3.Config.sys and Autoexec.bat files are empty! could this be the
problem?
4.It seems some if not most the drivers are windows 3.1 based, I think
all drivers shoud be specially for windows 95?
Imagine how anoying it is to switch on the computer..... works for
about 10 to 15 minutes and suddenly comes to a halt! or 'Freezes'
switch it off for another 20 to 30 minutes untill it's cool... healthy
computers can stay on for days. With cdrom it freezes much quicker,
for instance if a VCD movie is played, it freezes in less than three
minutes. I would appreciate your contributions towards a lasting
solution. 95man
-
January 10th, 2000, 12:05 AM
#2
Try cold booting and virus scanning from clean disk
-
January 12th, 2000, 12:13 AM
#3
anti-virus scan, no virus was found!
-
January 12th, 2000, 11:35 AM
#4
Rename (or delete) autoexec.bat and config.sys from the root c: drive. Windows doesn't need either of them. This will (usually) remove the MS-DOS compatibility mode.
------------------
Who needs a life, I have Internet!
members.cnx.net/reboot
Who needs a life, I have Internet! <a href="http://members.cnx.net/reboot/" target="_blank">Jim & Sue's Free Files</a> | <a href="http://reboot.8m.com" target="_blank">Jim's Modems</a> | [email protected]
-
January 12th, 2000, 08:15 PM
#5
Did you look in the Windrivers Tech Tips section ... their is a fix for this problem that i have used severall times when a system comes in using MS Dos compatability mode...
-
January 17th, 2000, 12:38 PM
#6
Under what date is the techtips fix for this problem? i looked but didn tsee it.
Thanks
Mike
-
January 17th, 2000, 12:48 PM
#7
Under what date is the techtips fix for this problem? i looked but didn tsee it.
Thanks
Mike
-
January 19th, 2000, 03:03 AM
#8
what do you mean "Techtip fix problem" ? if you mean Article Q151911, simply visit microsft knowlede base and search for trouble shooting resolution article of your choice.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|
Bookmarks