Bootlog.txt: "LoadFailed = EBIOS" - reason for "Protection Error"??
Robert Neary
------------------
Machine:
Gateway 486-DX2-66, I added Kingston DX4-133 processor 30 days ago.
16 MB of memory.
Mach 32 video card with 2mb VRAM
WD 1.2 Gig drive C: (downloaded flash BIOS upgrade from original to
read large media)
WD 405 mb drive D:
Mistsum CD-ROM drive E:
-----------------
Problem 1: Windows locking up when I click on an OK button. Cannot
ctrl-alt-del, machine must be shut off.
Problem 2: Irregular boot problem, "Windows protection error while
initializing
device VXDLDR: You need to restart your computer." Goes into SAVE
mode.
The lock-up problem seems to have disappeard when I disable the D:
drive in CMOS
The Protection Error happens randomly, sometimes the machine boots just
fine.
(See Bootlog.Txt errors below)
----------------
What I have tried so far that has not cured the problem:
--Removing the DX2-133 and replacing the original DX4-66
--Reinstalling Windows '95 overwriting the ATI video drivers
--Deleting Windows from the drive, total reinstall.
--Changing Video in Control Panel to generic super VGA driver
--Re-copying the COMMAND.COM from the original CD-ROM
--Virus scanned McAfee ver. "scn-253e" 12/20/96
I have checked the Microsoft/support web page; nothing applies.
There is nothing about this problem in the FAQ I got from
MIT.
I also reviewed the contents of BOOTLOG.TXT below. Copied the
drivers that "Load Failed". I don't know what "ebios" is but it failed
twice, cannot find a file by that name on the original CD-ROM.
Contents of BOOTLOG.TXT
[000F6D66] Loading Vxd = ndis2sup.vxd
[000F6D6A] LoadFailed = ndis2sup.vxd
[000F6D72] Loading Vxd = ebios
[000F6D72] LoadFailed = ebios
[000F6D72] Loading Vxd = vshare
[000F6D72] LoadFailed = vshare
[000F6D86] Loading Vxd = EBIOS
[000F6D86] LoadFailed = EBIOS
------------------
I am at a total loss to decide where to go from here. I am hoping
someone
has encountered this problem or someting similar to it. Short of
"Format c:/s"
I don't know what else to try.
I desperately need this machine up and running.
Thanks,
Robert Neary
nea...@teleport.com
Dirk Arnold
Robert Neary (nea...@teleport.com) wrote:
:
: Contents of BOOTLOG.TXT
:
: [000F6D66] Loading Vxd = ndis2sup.vxd
: [000F6D6A] LoadFailed = ndis2sup.vxd
:
: [000F6D72] Loading Vxd = ebios
: [000F6D72] LoadFailed = ebios
:
: [000F6D72] Loading Vxd = vshare
: [000F6D72] LoadFailed = vshare
:
: [000F6D86] Loading Vxd = EBIOS
: [000F6D86] LoadFailed = EBIOS
:
: ------------------
Hello together,
I don't have a solution but the same problem concerning the fails
in bootlog.txt.
If anybody knows, why these Vxds are marked as failed, please mail me, too.
Thank you very much.
Dirk Arnold
(Germany)
stef olde scholtenhuis
Same 'problems' here..
Could ebios mean some extra additional PNP bios emulation?
It wouldn;'t be necessary for my system becuase the BIOS itself IS
PNP. Could explain the fail.
ndis2sup* referres to some network files. Not important if you're
running a stand alone machine.
Anyway I think it's not important.
On 28 Jan 1997 11:22:51 GMT,
Andreas Heib
No problem, just annoying.
That is a known bug!
Win95 calls these files in registry AND system.ini. When they are called
for the second time, they cannot be loaded, cause they ARE loaded. REM them
out in system.ini! Your problem is blown away.
stef olde scholtenhuis <s.h.f.olde-...@ptt-telecom.nl> wrote in
article <330160ab.327212857@newsXgn>...
