[版主] 以下節自 Microsoft Knowledge Base
Load Failures Listed in the Bootlog.txt File
Article ID: Q127970
Creation Date: 22-MAR-1995
Revision Date: 10-FEB-1997
The information in this article applies to: Microsoft Windows 95
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
LoadFailed = dsound.vxd
LoadFailed = ebios
LoadFailed = ndis2sup.vxd
LoadFailed = vpowerd
LoadFailed = vserver.vxd
LoadFailed = vshare
InitCompleteFailed = SDVXD
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
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
The extended BIOS driver did not find an extended BIOS, so it does not load.
The NDIS 2 support driver did not find any NDIS 2 drivers to support, so it
does not load.
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:
1.In Control Panel, double-click System.
2.Click the Device Manager tab.
3.Double-click the System Devices branch to expand it.
4.Double-click the Advanced Power Management Support branch. (If this
branch does not exist, your computer does not support APM.)
5.Click the Settings tab.
6.Verify that the Enable Power Management Support check box is selected.
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
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.
After the first boot of Windows 95, 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.
Windows 95 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.