On 16 Oct 2003 21:00:26 GMT, in
<3f8f06e9$0$177$ s.net>
Boomer scrawled:
>°Mike° wrote:
>
>> Basic computer maintenance
>> http://uk.geocities.com/personel44/maintenance.html
>>
>> Download and install Bootlog Examiner
>> http://www.blueorbsoft.com/ble/index.html
>>
>> Boot the system up and hold the CTRL key. At the DOS
>> menu, choose 'Logged (bootlog.txt)'.
>>
>> After bootup, run Bootlog Examiner to find where the
>> delays are.
>[snip]
>
>Thank you, Mike.
You're welcome.
>Great little program. I needed it for a friends computer I have
>here.
>
>Could you help me with these? Suggestions please. 
>Windows 98 Compaq Presario 5152
>
>(Failures Only Shown)
>
> System Time Proc. Time Process
> ----------- ---------- -------
>
> 15:58:58 0.56 *** LoadFailed = ndis2sup.vxd
> 15:59:16 0.56 *** DEVICEINITFAILED = MTRR
> 15:59:53 0.56 *** INITCOMPLETEFAILED = SDVXD
These are 'normal failures' in Windows 98.
Load Failures Listed in the Bootlog.txt File
http://support.microsoft.com/default.aspx?kbid=127970
<snip>
>(Delays Only Shown)
>
> System Time Proc. Time Process
> ----------- ---------- -------
>
> 15:58:52 *** 1.11 Loading Device =
>C:\WINDOWS\SYSTEM\CPQIDECD.SYS
CD-ROM driver. Check if this is being loaded from
config.sys and autoexec.bat - it shouldn't need to
be.
> 15:58:54 *** 3.00 C:\CPQS\TOOLS\MINIFER2.EXE[000FCD62]
>starting
From what I could find out, this seem to be loaded from
autoexec.bat, and is something to do with Compaq Service
Connection Install. I don't know how important it is.
> 15:59:17 *** 1.11 DEVICEINIT = NTKERN
This is only a slight delay, but you could read the following - though
I don't think it's a problem.
How To Fix the NTKERN.VXD Device Loader Bug
http://www.donath.org/Rants/MSTechHorror/
> 15:59:27 *** 3.56 DEVICEINIT = VMOUSE
This (mouse driver) delay *could* be related to ntkern, if it's
a USB mouse.
> 15:59:34 *** 3.33 Dynamic load device vtdi.386
> 15:59:39 *** 1.56 Dynamic load success vnbt.386
Not sure what the above two are, but .386 device drivers are
old 16 bit drivers.
> 15:59:45 *** 1.78 Initing drvwq117.vxd
Seems to be a Seagate driver.
The good news is that nothing is actually failing, but the
bad news is I don't know exactly what is causing the
delays. It may just be down to the peculiarities of that
particular system.
<snip>