Load Failures Listed in the Bootlog.txt File

ID: Q127970

The information in this article applies to:

Microsoft Windows 95
Microsoft Windows 98

SYMPTOMS

When you review the Bootlog.txt file in the root folder on your hard disk, you may see the following lines even though your computer seems to function properly:

LoadFailed = dsound.vxd

LoadFailed = ebios

LoadFailed = ndis2sup.vxd

LoadFailed = vpowerd

LoadFailed = vserver.vxd

LoadFailed = vshare

InitCompleteFailed = SDVXD

NOTE: The following lines may appear only in the Windows 98 Bootlog.txt file:

Deviceinitfailed = MTRR

SysCritInitFailed = JAVASUP

DeviceInitFailed = MTRR

CAUSE

These load failures do not necessarily mean that there is a problem. It is common for some, if not all, of these to fail, depending on your system configuration.

DSOUND

Many sound drivers are DirectSound enabled. DirectSound is part of Microsoft DirectX, a set of libraries used by most newer Windows-based games. When a DirectSound-enabled sound driver is loaded, it attempts to register with the DirectSound library so that games can use it. If no DirectX-based games are installed on your computer, the DirectSound library fails to load. This is normal.

EBIOS

The extended BIOS driver did not find an extended BIOS, so it does not load.

Ndis2sup.vxd

The NDIS 2 support driver did not find any NDIS 2 drivers to support, so it does not load.

VPOWERD

The Advanced Power Management (APM) driver determined that your computer does not support APM, so it does not load, or APM support may be disabled. To determine if you have inadvertently disabled APM in Device Manager, follow these steps:

In Control Panel, double-click System.

Click the Device Manager tab.

Double-click the System Devices branch to expand it.

Double-click the Advanced Power Management Support branch. (If this branch does not exist, your computer does not support APM.)

Click the Settings tab.

Verify that the Enable Power Management Support check box is selected.

Vserver.vxd

Vserver.vxd does not load statically so that it can save memory by loading later in the boot process only if it is needed. For example, Vserver.vxd might not be needed when you start a laptop computer while it is out of its docking station.

VSHARE

If you examine the Bootlog.txt file, you will notice that VSHARE loaded successfully earlier in the boot process. The second copy of VSHARE detects that VSHARE is already loaded and does not load.

Font Failures

After the first boot of Windows 95/98, the Bootlog.txt file may list many font load failures. This is a normal occurrence. When Font Manager searches the hard disk for fonts, it may find them in several folders. After it finds them, it records the information so that future attempts to locate a font proceed more quickly.

InitCompleteFailed=SDVXD

Windows 95/98 automatically loads a miniature disk cache to increase the speed of the boot process. When the boot process is complete, the miniature disk cache is unloaded from memory. When it is unloaded, the above line is added to the Bootlog.txt file to indicate that the miniature disk cache has been removed from memory.

This is normal behavior.

SysCritInitFailed=JAVASUP

The Java Support driver is not needed on your computer, so it did not load. Java is a programming language used on the World Wide Web (WWW). Microsoft Internet Explorer versions 3.0 and later include a Java subsystem.

DeviceInitFailed=MTRR

Memory Type Range Registers (MTRR) is a .vxd file responsible for manipulating memory ranges. This file is loaded with DirectX 5.0, however, none of the DirectX core components use the service provided by MTRR. Also, NTKERN and some display drivers do use the service provided by MTRR to change memory ranges.

Additional query words: loadfail

Keywords : kbtool win95
Version : 95
Platform : WINDOWS
Issue type : kbprb