Safe Drivers and the Safe Driver List

A real mode driver is safe if its functionality does not exceed the functionality of the corresponding Windows 95 protect mode driver. If a real mode driver is safe, the protect mode driver can take over all I/O operations for the corresponding device. Otherwise, Windows 95 routes all I/O operations through the real mode driver.

An example of an unsafe driver is a real mode IDE/ESDI driver that uses dynamic encryption for security reasons. In this case, Windows 95 does not provide encryption, so Windows 95 should not allow the protect mode IDE/ESDI driver to take over the real mode driver. Any real mode driver that has the following functionality (not supported by Windows 95) is considered unsafe:

• Data compression that is not compatible with DoubleSpace
• Data encryption
• Disk mirroring
• Bad sector mapping
• Fault tolerance, for example, maintenance of ECC correction on a separate disk
• Vendor-specific IOCTLs
• Microsoft-defined IOCTLs with vendor-extended features

The safe driver list is a Windows 95-maintained list of safe drivers. Each entry in the list identifies a driver or TSR that Windows 95 can take over with the corresponding protect mode driver. The list includes the following information:

• Name of the driver or TSR. This should be same as the name present in the CONFIG.SYS or AUTOEXEC.BAT file.
• Driver requirements
• Whether it hooks INT 13h
• Whether it needs to monitor INT 13h (regardless of whether the I/O is controlled by a protect mode driver)
• Whether it accesses the hardware directly

Windows 95 does not store the version number of the driver or TSR in the list, so it is the responsibility of the vendor to change the name of the driver if a future version of the driver is enhanced in a manner that makes the driver safe or unsafe.

By default, the following drivers are considered safe:

• MS-DOS 5-compatible real mode block device drivers
• INT 13 monitors (hooks INT 13h for monitoring INT 13h I/O but does not access the hardware directly or modify the I/O buffer)
• INT 13h hooker (hooks INT 13h for altering INT 13h I/O but does not access the hardware directly)
• INT 13h driver (provides INT 13h functionality and directly accesses the hardware)
• ASPI Manager (implements ASPI for MS-DOS specification)
• CAM Manager (implements MS-DOS CAM specification)

If your real mode driver has higher performance or provides some functions that may not be present in the Windows 95 protect mode driver, you should remove the driver from the safe driver list. The system will use real mode to access your driver. Similarly, if your real mode driver that can be safely taken over by the protect mode drivers, add that driver to the safe driver list.

Note

By default, Windows 95 assumes that a Master Boot Record (MBR) that contains code that hooks INT 13h is unsafe. You can override this default behavior and provide protected mode support is a VSD by using safe MBR INT13h hook routines. For more information, see About Vendor-Supplied Drivers.