MS-DOS Compatability mode / Code 10???!!

**Lachesis** · November 23rd, 2002, 12:31 AM

I've been working on this for about two weeks. I've done a lot of reading and tried various methods. I'm not really sure if this is a software problem or not. The following is a compilation of my own problem log. I'm sorry if it seems a little choppy. I just hope it makes sense to someone, I will greatly appreciate any help or suggestions.

I was coping music to my storage drive. When I came back to my computer a
few minutes later I had a "Blue Screen" message stating it was unable to
write to drive D. Since then I've had a number of problems. Slow
boot,Hangs, Freeze ups, and now my storage drive (Formally the D drive) does not show up at all. Before this I had IDE "C" drive, IDE "D", CD-ROM (E drive) and DVD-ROM (F drive). Now everything shows but the D drive.

I checked in the system info. It shows my secondary IDE ok, but the master
IDE showed the error code. I looked in the BIOS both drives show 'Enabled'.
I noticed a few things though. 1)The Master shows 78177792 sectors and
40027MB max capacity while the Slave shows 4156128 sectors and 21279MB max
cap. Both are 40 Gig HD's. 2) When I boot it sits on the HP Invent screen 1
or 2 minutes before It starts. 3) After it is up and running the
performance is very slow (it has a P3 935Mhz processor with 512MB memory).
4)System restore no longer works, It shows no restore dates available. In
HP system info it is still showing both drives, but nothing else will read
the slave.

Name Primary IDE controller (dual fifo)
Manufacturer (Standard hard disk drivers)
Status Error
Driver c:\windows\system\vmm32.vxd (, 1,019.88 KB (1,044,352 bytes),
Not Available)

Name Secondary IDE controller (dual fifo)
Manufacturer (Standard hard disk drivers)
Status OK
Driver c:\windows\system\vmm32.vxd (, 1,019.88 KB (1,044,352 bytes),
Not Available)

The Device Manager does show it. I checked the properties and the Slave
Device status reads "This device is working properly". However, the Primary
shows the yellow (!). Device status for the primary reads "This device is
either not present, not working properly, or does not have all the drivers
installed. (Code 10)" ... "Try upgrading the device drivers for this
device".

I also noticed a RED X on an item under 'DISK DRIVES' listed as 'GENERIC
IDE DISK TYP01'. The device status for this reads "This device is not
working properly because a device it depends on, Primary IDE controller
(dual fifo), has been dynamically disabled."

These two instances tied together I guess? I checked the performance tab.
There are two listings.

1) Compatibility mode paging reduces overall system performance.
Windows Millennium Edition was unable to identify a real-mode driver or
memory-resident program loaded in your Config.sys or Autoexec.bat file. You
will see another message that lists the name of the driver or program
causing the problem.
Because Windows Millennium Edition could not identify the driver or
program, it has switched to MS-DOS compatibility mode to ensure the program
will run. However, this decreases overall performance. To improve
performance, remove the program or driver causing the problem, or contact
its manufacturer for an upgraded version.

2) Drive X is using an MS-DOS compatibility mode file system.
This problem often occurs on more than one drive. Usually it is caused by a
driver listed in the Config.sys file that Windows Millennium Edition does
not recognize and that is related to the message Compatibility mode paging
reduces overall system performance. If you see both messages, see the Help
for the Compatibility mode paging reduces overall system performance
message first.
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 might 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 might be less than optimal, but
you can still use it.
the slave drive does not show in "fdisk /status".

When I try to run a DOS based recovery program or even run the drive overlay disk that came with the slave (Maxtor) I get this error code or one like it:

INT13h error code 01h in parameter AH.

I have checked the IOS registry for 'NOIDE', but I was unsure what to look for. I've been told that anything with a value of 00 or 01 was not good. I checked around the Registry a little more and found numerous values of 00 - 01 in different areas of the registry.

Could it be a memory resident virus? If so my anti-virus is not picking it up. I'm using Norton System Works I recently installed (after the problem started). I tried installing 'Go Back' but because it is operating in MS-DOS Comp Mode the OS won't let me.

My OS is Windows ME. The only other thing I can think of is to change the IDE cable. I don't think it is a physical problem with the HDD or maybe that's just wishful thinking.

That's all I can think of right now ... except... um, HELP!

One more thing. Might not be relevent, but just before this happened I deleted some files from the slave to make more room. They all seemed to be useless files. Just some junk I had laying around.

**Foggy** · November 23rd, 2002, 12:44 AM

The only time I ever had this problem it was the drivers for the MOBO. so you might try to download the latest drivers for your MOBO, hope this helps.

**SPEEDO** · November 23rd, 2002, 08:56 AM

Have a look here...........................

**Lachesis** · November 23rd, 2002, 02:16 PM

Thanks Speedo,
I read the article, but still nothing. There aren't any NOIDE in the registry anywhere. I would remove the driver, but it told me to remove the parent driver. I could but I'm a little shaky about that.

If I re-install Windows ME or even upgrade to XP, would that "fix" the problem? ... I just don't know. Everything seems like a good lead but ends up a virtual "dead end".

Thanks for the reply. Looks like you're finding the same info I have.

**OuTpaTienT** · November 23rd, 2002, 02:21 PM

Then remove the parent driver.

**SPEEDO** · November 23rd, 2002, 08:38 PM

Or try going to the properties of the item in question in device manager and updating the driver.

**Lachesis** · November 25th, 2002, 09:06 PM

No such luck!

I could only find 1 other driver. When I restarted, the beautiful blue screen came up to tell me that some devices were running in compatability mode. So the master driver was again set at Comp Mode.

Removing the Parent driver was uneventful. Might work, but it seems to have a mind of it's own. It locked up tight. The only thing that moved was my mouse. CTRL ALT DELETE wouldn't even reboot.

Very frustrating!

**Wizzard~Of~Ozz** · November 25th, 2002, 09:11 PM

You have to remove it from safemode, delete it in the registry (can't remember where and I run 2K) then reboot, it'll find the devices, ask you to reboot, say no, it'll find the second device then ask you to reboot, yes. done.

**Lachesis** · November 25th, 2002, 10:13 PM

Thanks Wiz.

I just did that and it came back the same way BUT... While I was in safe mode and Device Manager I noticed A LOT of duplicates. Almost everywhere I looked, the drivers were doubled.

Should I remove only one of each or remove everything that was doubled?

Mouse, Monitor, System Devices and PCM... something. Sorry, I didn't write it down.

I've read about having duplicates but nothing really said what to do about it.

I appreciate every ones help. This is the first REAL progress. What can I do?

**SPEEDO** · November 26th, 2002, 10:16 AM

I would remove everything that has a double and just leave one mouse left so you won't need to use the keyboard to reboot.

When you reboot Windows will install the items that are required.

**Wizzard~Of~Ozz** · November 26th, 2002, 05:49 PM

This is a thread on how to clean it all up.

in safe mode run regedit, delete the key hkey_local machine/enum (just highlight the word enum and delete)

If it's not in that location post back.

When you reboot it will find all your devices (make sure you have drivers handy, it will want some. if it asks you to restart your computer, keep hitting no. then when fully booted and there are no more pop-up's shut down and reboot, then check the drives.

Motherboard change question

**Lachesis** · November 26th, 2002, 11:22 PM

I'll try it.

If the slave drive has gone bad, could that cause all of this trouble?

Any way to tell if the drive IS bad? Windows only sees it in the device mngr and Sys Info. fdisk doesn't even see it. Other than that BIOS is the only thing that sees it. NOTHING will read from it.

The way it hangs on the blue HP screen at boot up bothers me.

Sorry for so many questions

Thanks again.

**Wizzard~Of~Ozz** · November 26th, 2002, 11:28 PM

Usually if a drive is bad you can't read from it but it won't disable the controller, IT's possible the controller on your board is bad, but if it doesn't work after this try a different drive on this controller, or do you have a CDrom on that controller? is it working?

**Lachesis** · November 27th, 2002, 12:18 AM

I think the CD rom isn't on that controller, It has been working but the software has been a little twitchy. EasyCD 4 works good, but Easy CD 5 is come and go. I've noticed that with a lot of my programs since all of this started.

I'll try your suggestion. If it still won't work, I'll open it up and put the ribbon to the slave on the CDrom. That should narrow it down, I hope. I'm stubborn and I hate the thought of losing all of my files. Some of it is irreplacable. My own fault, I didn't back it up.

Busy couple of days coming up. I'll post back later with an update.

Thanks!

L.

**Beemer** · November 27th, 2002, 01:00 AM

What are the hard drives?
I've cured Compatibility Mode Paging issues with reinstalling Priomise Ultra drivers on ATA drives.

Cheers!

**John Prophet** · November 27th, 2002, 01:30 AM

I second what was said about running regedit and deleting the hkey localmachine/enum folder..just delete it and reboot. With all those double entries in device manager..you need to delete the folder and start over. An alternate method is to just delete EVERYTHING from the device manager but you will soon see that takes a while...deleting the hkeylocalmachine/enum folder does the same thing quicker.

Get all of your drivers disks ready. After a bunch of reboots you will have redetected all of your hardware. Dont get frustrated if it detects stuff in the wrong order, in other words you may need to use the cdrom to install drivers but the ide controllers havnt been detected yet so no cdrom available....just skip it and come back to it. If you happen to get a double entry again somehow just delete both entries and reboot.

JP

**Wizzard~Of~Ozz** · November 27th, 2002, 01:38 AM

alternate method is to just delete EVERYTHING from the device manager but you will soon see that takes a while

It will automatically re-install the HD controller drivers the wrong way if you don't delete that key and only delete them in dev manager.

Also after it detect the primary controller it will ask to reboot usually, you have to say no or you will have to repeat the whole thing as the secondary will have errors after reboot.

**Lachesis** · November 27th, 2002, 03:09 PM

Wow! I step away for a few hours and...

Good thing I checked in...
Okay, hard drives are #1 Quantum Fireball and #2 Maxtor both 40Gb

I have the HP recovery disks that came with the machine. The one thing that might be a problem are the Video drivers. I installed an ATI card about a year ago. I had to remove the Driver that was there so that it wouldn't conflict with the ATI driver

I'll delete enum tonight, gonna be up late anyway. Iguess if that doesn't work I'll change the ribbon (who knows) If THAT doesn't work I'll start looking for someone who can recover as much data as possible.

**Lachesis** · November 28th, 2002, 12:35 AM

Deleting enum didn't work.
If the error is showing on the Primary IDE Controller, wouldn't that be the controller on the hard drive? This is a new area for me. I read a little. There is a main IDE controller internally, but doesn't each HD have a controller? Like I said, this is new to me. I'm not sure I completely understand... yet.

**Wizzard~Of~Ozz** · November 28th, 2002, 12:50 AM

Do you still have all the duplicates in safe mode?

When you rebooted did it start listing off all kinds of new devices?

Did you answer no to any time it asked to reboot?

Is it still the identical error?