Bootlog Failure

I took a trip out to analyse my bootlog using this Bootlog Analyser and I notice 3 failures, 2 of which are mentioned by: Microsoft Knowledge Base Article - 127970 and are not significant but I am puzzled by the third:

[000010A5] Dynamic load device
[000010A5] Dynamic load failed : [000010A5] File not found

Is there any way I can identify what is causing this failure?

 

My guess is that it is trying to find a piece of hardware which is registered in your system, but you don't have any more.

If you looked in your bootlog.txt file with notepad, then you probably find something similar to:

A possible solution is to boot in safemode and check the device manager for any hardware, which is no longer in the machine and remove it from the system using the device manager.

 

There isn't any device that identifies with failure. Here is an expansion of the bootlog around the failure. The device manager doesn't indicate anything that shouldn't be there.

Where are the devices that get loaded specified?

 

Was just guessing, haven't been looking much into how the bootlog.txt works, maybe a more knowledgable person will step in and explain the funny entry.

I would probably just ignore it as long the computer works.

 

OK. i would like to get rid of the error since it costs some 15 seconds in the boot sequence.

Some sites indicate that this may be related to DirectX 6 but DxDiag does not report any errors for that version of DirectX.

Do you or anyone know of web sites dedicated to isolating bootlog errors?

Did try and use RegRepair 2000, which also identified the problems but did not fix them.

 

you have radeon card in there?

 

No, it's an AGP2X RAGE PRO chip. I don't think it is anything to do with the display device drivers (macxw4.vxd) this was loaded successfully. Some unknown device then attempted to load after this and failed with a file not found. For information Dr Watson did not find any errors.

 

I was reading up on the bootlog at Microsoft and came across a Bootvis tool at http://www.microsoft.com/whdc/hwdev...ot/bootvis.mspx but sadly the tool is temporarily unavailable.

Does anyone why this is so? and if there are plans to make it available? or if it is available elsewhere?

I'm still no closer to solving this problem.

 

This tool is made for WinXP only. Even if it was available it will not work for Win95, Win98, WinMe or Win2k.

If you are ready to try anything to get the device failure to disappear, then you could try:

Uninstall network/dun, reboot and install again.
Force Windows to redetect all the hardware

 

Yes, agree that the Bootvis tool that is advertised is for WinXP - wonder if there is one for Windows 98?

I followed through your web page deleting the Enum key as well as uninstalling network/dun and reinstalling. The Bootlog still shows the error with a vengeance, OK, 0.4 secs longer than before, i.e., 15 secs delay.

The redetection of all the hardware was fun, especially without a mouse and wrong device drivers chosen but eventually got a bootlog with the error.

Further reading seems to indicate that the information I seek is in held within VMM32.VXD - see Optimizing Windows 9x/Me Startup - will add to useful links section. Any tips on how look inside this virtual device driver file?

 

If you want to know something about the Vmm32.vxd then go here:

http://www.infinisource.com/techfiles/vmm32.html

 

Very Interesting, like the hogwash. However, my mission, if I should choose to accept it, will be to complete this next weekend. A quick look in the registry at the VMM key doesn't show either macxw4.vxd nor valcacr.vxd

Pity I couldn't go the other way from the bootlog entry to wherever the the erromeous file reference is.