LoadFailed=ndis2sup.vxd in Bootlog.txt
Michael J. Glanovsky
[00130240] Loading Vxd = ndis.vxd
[00130240] LoadSuccess = ndis.vxd
[00130240] Loading Vxd = ndis2sup.vxd
[00130240] LoadFailed = ndis2sup.vxd
Any ideas?
Thanks,
Mike
Bobby Davies
Try that.
Michael J. Glanovsky <michaelg...@home.com> wrote in message
news:#NIE2SRX#GA...@uppssnewspub05.moswest.msn.net...
Kirk Bubul
<michaelg...@home.com> wrote:
>Bootlog.txt contains the following Load Failure...
>
>
>[00130240] Loading Vxd = ndis.vxd
>[00130240] LoadSuccess = ndis.vxd
>[00130240] Loading Vxd = ndis2sup.vxd
>[00130240] LoadFailed = ndis2sup.vxd
>
Ndis2supd.vxd failure is well neigh universal. It is a false failure.
It simply means that nothing needed that driver.
Don't sweat it.
Bill B
Here is an excerpt from MS article 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.
BillB
Michael J. Glanovsky wrote in message
<#NIE2SRX#GA...@uppssnewspub05.moswest.msn.net>...
>Bootlog.txt contains the following Load Failure...
>
>
>[00130240] Loading Vxd = ndis.vxd
>[00130240] LoadSuccess = ndis.vxd
>[00130240] Loading Vxd = ndis2sup.vxd
>[00130240] LoadFailed = ndis2sup.vxd
>
>Any ideas?
>
>Thanks,
>
>Mike
>
>