1024 cylinders) that is not compatible with Windows 95 protected-mode disk drivers.
• Run a recent antivirus program to detect and remove boot-sector viruses (such as Norton Anti-Virus, NAV). You might need to rewrite your boot sector using a DOS command, such as
FDISK /MBR.
• If you cannot detect any virus activity, check the disk-management software. Be sure that you’re using Disk Manager 7.0 or later (use Disk Manager 7.04 if you’re running DriveSpace 3, included with the Microsoft Plus pack.
3. If the driver name that is listed is in the CONFIG.SYS file, contact the driver’s manufacturer to determine whether there is a more recent version of the driver that allows protected-mode operation in Windows 95. You might be able to download the latest driver version from the driver manufacturer’s Website. If no driver is listed on the
Performance tab, check that the hard-disk controller is listed in the
Device manager. If not,
install it through the Add new hardware wizard. If the wizard cannot detect the controller automatically, run the wizard again, but do not let it attempt to detect the hardware in your computer—instead, select the controller specifically from the hardware list. If your particular controller is not listed, contact the manufacturer of the disk controller to obtain a Windows 95 protected-mode disk driver (or a Windows x bit disk access (FastDisk) driver, if available.
5. If the hard-disk controller is listed in the
Device manager, but has a yellow “!” over it, there is a resource conflict (IRQ, IO, DMA, or BIOS address range) with another device, the protected-mode
driver is missing or damaged, or the
Disable all 32-bit protected- mode disk drivers check box has been selected in
File system properties.
•
Doubleclick the
System icon in the
Control panel, click the
Performance tab, then click
File system. Select the
Troubleshooting tab and see that the
Disable all 32-bit protected- mode disk drivers check box has not been selected.
• Resolve any resource conflicts with other devices in the system (refer to Chapter
10).
• Check that the protected-mode driver is in the Windows\SYSTEM\IOSUBSYS directory and is loading properly. To find which driver is providing bit disk access, click
Properties for the disk controller in
Device manager and click the
Driver tab to see which driver files are associated with the controller. For most IDE,
EIDE,
and ESDI disk controllers, bit disk access is provided by the
ESDI_506.PDR driver. For SCSI controllers, Windows 95 often uses SCSIPORT.PDR and a mini port (or
.MPD) driver. Restart Windows 95, press
when the Starting Windows 95” message appears, then select a Logged (BOOTLOG.TXT) start. If the bit driver is listed as loading properly, you’re all set. Otherwise, the driver might be missing or damaged—try reinstalling the respective bit drivers.
6. Load SYSTEM.INI into a text editor and check to see if the MH2BIT.386 driver is being loaded (check fora line that reads “device=mh32bit.386”). This driver is installed by MicroHouse EZ-Drive software, and is not compatible with the Windows 95 protected mode disk drivers. Unfortunately, this driver is not removed by Windows 95 Setup, so you’ll need
to disable the line manually, save your changes, and reboot the PC.
7. If all else fails, you might be able to achieve protected-mode support from the disk controller by disabling any of the controller’s advanced features (i.e., caching, fast or turbo modes, or reducing data-transfer rates. You might also try systematically disabling advanced IDE controller features in the CMOS setup.
8. If problems persist, you might have to replace the drive controller with a model that better supports protected-mode operation.
Share with your friends: