At 05:10 06-06-98 +0300, Gary wrote:
>My system runs well and is stable but I found a number of "LoadFaileds"
>[in bootlog.txt] which are unfamiliar to me. Perhaps someone can
>explain what these are and the importance of them.
>
>14:30:25    0.11  LoadFailed  = vserver.vxd
>14:30:26    0.11  LoadFailed  = ndis2sup.vxd
>14:30:27    0.00  LoadFailed  = ebios
>14:30:27    0.00  LoadFailed  = vshare
>14:30:28    0.22  LoadFailed  = EBIOS
>14:30:36    0.06  Dynamic load failed  naapi.vxd : [000E589E] File not
>found


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.

Vserver.vxd does not load statically so that it can save memory by
loading later in the boot process only if it is needed.

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

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

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.

David Gillett wrote about naapi.vxd in a list message dated 11 March 98:

"According to a post I found on the web, this is a driver for a
Creative Labs sound card THAT WORKS ONLY WITH THE JAPANESE VERSION OF
WIN95.  You aren't the only one whose machine is trying to load this,
but obviously it shouldn't even try."

Check out "Load Failures Listed in the Bootlog.txt File"
at <http://support.microsoft.com/support/kb/articles/q127/9/70.asp>.

Regards,
Bill