Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations Mike Lewis on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Startup Problems - MS-DOS Compatibility Mode

Status
Not open for further replies.

Makapuu

Technical User
Sep 24, 2001
2
0
0
US
I recently installed a TDK24/10/40 veloCD ReWriter in my HP Pavilion 6370Z running Windows Millenium Edition (v4.90.3000). I also have a second CD-ROM and Zip 100 ATAPI/IDE internal drive. All of these devices were working properly immediately after installation.

I then attempted to install the TDK Digital MixMaster and Nero 5.5 Multimedia Recording Software. I was unable to install the InCD Packet-Writing Software because I was given a message that said I already had PacketCD installed.

I already had Roxio's Easy CD Creator 5 Platinum installed (v. 5.0 P/N 1875500UN REV A v5.0) (which I believe had replaced PacketCD with a more recent version). This was an upgrade from my original Cequadrat software. Cequadrat was purchased by Adaptec which spun off Roxio.

(Easy CD Creator worked fine with my previous Ricoh MP7040A CD-RW.)

After I attempted to uninstall Easy CD Creator 5 Platinum I was unable to startup my computer. I got repeated blue screen warning and hangs. I tried repeatedly to fix this problem. I even reinstalled Windows ME.

This also did not work.

After considerable research effort, and some recommendations from Roxio, I was able to uninstall Easy CD Creator (and other related Adaptec and Cequadrat software).

I also completely uninstalled ZoneAlarm and McAfee antivirus software which had been implicated in similar problems, but I was still unable to restart my computer. It would make it part way through the startup sequence then go into a blue screen freeze, generally with the following message:

"An exception 06 has occurred at 0028:000000XX in VxD ---. This was called from 0028:XXXXXXXX in VxD ---. It may be possible to continue normally.

*Press any key to attempt to continue.
Press CTRL+ALT+DEL to restart your computer.
You will lose any unsaved information in all applications.

Press any key to continue"

Where X is a varying character.

This was followed by:

"Windows protection error. You need to restart your computer. System halted."

After some troubleshooting, I was able to isolate the problem. In Safe Mode I ran msconfig to get the System Configuration Utility. After many troubleshooting steps, I selected Advanced and then selected Force Compatibility Mode Disk Access.

I was then able to startup in the regular mode. My CDROM was still not recognized.

Under System Properties/Device Manager/Standard Floppy Disk Controller and Primary IDE Controller (dual fifo), I go the following message:

This device is either not present or not working properly, or does not have all of the drivers installed (Code 10)

Try upgrading the device drivers for this device (I did, but the existing driver was the most up-to-date).

In the Resources tab, no conflicts were present.

The appropriate drivers were present for both devices (hsflpo.pdr and vmm32.vxd for the Standard Floppy Disk Controller and esdi_506.pdr and vmm32.vxd for the Primary IDE Controller (dual fifo) (the devices on the Secondary IDE Controller were removed, as was the Secondary IDE Controller).

Under System Properties/Performance the following messages were present:

Compatibility mode paging reduces overall system performance.

Drive A is using MS-DOS compatibility mode file system.

Drive C is using MS-DOS compatibility mode file system.

(Oddly enough, when I go to Control Panel/System Properties the Connect to dialog box for Dial Up for my old ISP (I have Road Runner Cable Internet Service now)!?)

Based on this information, I went to Microsoft's Article No. Q151911 (MS-DOS Compatibility Mode Problems with PCI IDE Controllers) and Microsoft's Article No. Q130179 (Troubleshooting MS-DOS Compatibility Mode on Hard Disks)

According to Microsoft's Article No. Q151911, the stated CAUSE is:

This behavior can occur if the protected-mode driver for the hard disk controller is not properly initialized when you start Windows. When this occurs, a NOIDE value is placed in the registry which prevents Windows from making future attempts to initialize the protected-mode driver.

The RESOLUTION is to:

1. Click Start , click Run , type regedit in the Open box, and then press ENTER.

2. Locate and click the following registry key:

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\VxD\IOS

3. In the right pane, right-click the NOIDE value, and then click Delete .

4. Quit Registry Editor.

I tried this, but there was no NOIDE entry in this path.

MORE INFORMATION

This issue can occur if your computer has an IDE controller that requires serialization between the primary and secondary IDE channels. The protected-mode drivers for these IDE controllers may not be initialized if one of the following situations occurs:

If one IDE channel has a supported hard disk, and the second channel has a CD-ROM or another type of drive that requires Real-mode drivers. Because there must be serialization between the two IDE channels, Windows cannot access the hard disk in Protected mode and use the other device in Real mode. When this occurs, the Protected-mode driver is not initialized and the NOIDE switch is placed in the registry to prevent future errors. Both disk devices can then operate in Real mode.

-or-

If you manually remove the driver for the IDE controller from Device Manager and then reinstall it, or if you disable and then re-enable the protected-mode driver. Some PCI controller drivers are not designed for dynamic enabling and disabling, and can cause the Protected-mode driver to not initialize properly.

The Windows device drivers for the following controllers may cause this behavior:

CMD PCI-0640 PCI-IDE controller
Standard Dual PCI-IDE controller
Opti Dual PCI-IDE controller
Intel 82371 AB/EB PCI Bus Master IDE Controller (This is present)
Ali M5229 PCI Busmaster IDE Controller

Other PCI IDE controllers that use serialization between the IDE channels may also cause this behavior.

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Can anybody provide additional information on how to fix this problem?

Thanks in advance,

 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top