A Windows 98 & ME forum. Win98banter

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

Go Back   Home » Win98banter forum » Windows 98 » Improving Performance
Site Map Home Authors List Search Today's Posts Mark Forums Read Web Partners

Interpretation of failures and delays at boot.



 
 
Thread Tools Display Modes
  #41  
Old September 8th 04, 08:47 PM
George
external usenet poster
 
Posts: n/a
Default

Okay to SFB and Glen. I will track down the Western
Digital site and see what they have to impart. Perhaps
it's been a bad disk all along - started out with a
message: "Press any key to run ScanDisk with surface
analysis on these drives...Invalid Switch: /SIMPLEUI."
Then I did a Thorough ScanDisk and Defrag which took about
30 hours, and also did the anti-virus scans with Norton,
Spybot and Adaware. The "Invalid Switch" message went
away so thought it was probably software.

Will let you know the result of the visit to Western
Digital. Thanks for steering me along - couldn't do the
troubleshoot without you.

-----Original Message-----
Is your disk in good shape ?
Wondering if you should download the
disk diagnostic from the disk mfgr's web site and run the

non-destructive
tests.

Might have a flakey sector or two

"George" wrote in

message
...
Hello Glen. I'm using a dial-up connection and the best
speed we get in this area is usually 28,000 bps. Not on
any type of network, just a simple home set-up on a Dell
Precision 486 purchased the end of 1993 upgraded 1997 to
AMD K-6 chip, 96 RAM, 4GB HD - think the OS started with
Win3.1, then Win95 and upgraded to Win 98SE.

Earlier you had me do a full system virus scan which I

did
do. Next, I was able to download Spybot and Adaware but
not CWShredder. For some reason CWShredder would not
download into my system. I ran Spybot and Adaware for
several days, then cleared them out. Adaware found

nothing
and Spybot found one item which was promptly removed.
Right now I'm operating without an anti-virus program as
Norton Anti-Virus was uninstalled day before yesterday
since we thought it might be behind the long boot
problems. Also, I think I want to change to another

anti-
virus program. But I'm being careful and only coming to
this support.microsoft.com site when on the internet.

I have run the clean boot procedure from the Gary

Terhune
article recommended earlier. After completing his "clean
boot" list, this is what the Bootlog Analysis Report
(Delays) looked like:

6:56:38 154.72 LoadSuccess = C:\WINDOWS\IFSHLP.SYS
6:59:14 0.67 Loading Vxd = C:\WINDOWS\system\VMM32
\IFSMGR.VXD
6:59:15 0.28 Loading Vxd = C:\WINDOWS\system\VMM32
\IOS.VXD
6:59:19 0.72 Loading Vxd = dfs.vxd
6:59:26 0.50 DEVICEINITSUCCESS = VTD
6:59:28 0.33 Dynamic load device bios.vxd
6:59:31 0.89 Dynamic load device pci.vxd
6:59:36 0.61 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
6:59:38 3.89 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
6:59:43 0.72 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
6:59:44 0.33 DEVICEINIT = NDIS
6:59:44 4.50 Dynamic load device pppmac.vxd
6:59:50 3.22 Dynamic load device vdhcp.386
6:59:56 0.33 Initing hsflop.pdr
6:59:56 0.28 Initing esdi_506.pdr
6:59:57 0.61 Initing esdi_506.pdr
6:59:57 0.61 Init Success esdi_506.pdr
7:00:01 0.28 Dynamic load success
C:\WINDOWS\system\serial.vxd
7:00:02 2.44 Starting Wave Device for Voice Modem

(MODEMWAVE\HALFDUPLEXVOICEWAVEDEVICE\ROOT&UNIMODEM 631CD54E&
COM1)
7:00:05 1.06 Dynamic load success dsound.vxd
7:00:08 93.06 InitDone = TSRQuery (time estimated)

The above test was run yesterday morning (Tuesday 7 Sep
04), and this morning the same report showed 349 seconds
for = C:\WINDOWS\IFSHLP.SYS!! The clock-on-the-wall time
for yesterday's report displayed above was 8 min. 55

secs.
This covers the time from when the Win 98 Menu first
appears until the full icons appear on the desktop.

Don't
understand why the time on the Bootlog Analysis Report

is
much shorter.

An icon double-clicked on the desktop then takes another
55 secs. to pull up that selected item, but after it's
been used that first time and then closed and reopened -
the icon/progam/item responds by opening at normal speed
(about 5 secs). This is another symptom that has

continued
since it first slowed down about two weeks ago - seems
related.

How does one examen the time used in

C:\WINDOWS\IFHLP\SYS?
Your continued direction and advice appreciated.




-----Original Message-----
George, are you using a broadband connection or a dial-

up
connection? Do you have a
Network card (NIC) or integrated network interface in

the
computer? Are you on any
type of network?

Also, I suggest you do a complete check for

malware/adwa

Update your anti-virus app and then run a full-system

virus scan.

Use CWShredder, the CoolWeb removal tool, available

he
http://www.majorgeeks.com/downloads31.html
http://aumha.org/downloads/cwshredder.zip
Close all browser windows and open apps, start

CWShredder
and click the Fix button.

In addition, install Ad-Aware SE free edition, start

it,
click its 'Check for
Updates' link in the app to install updates, then use

it
to scan your system, and
remove what it finds.
Ad-Awa
http://www.lavasoftusa.com/support/download/

Install, update and run SpyBot Search & Destroy, scan

your system, and then remove
the items in RED only.
SpyBot S&D:
http://www.safer-networking.org/index.php?page=download

Install SpywareBlaster:
http://www.majorgeeks.com/download2859.html
Click the link in the app to check for and install

updates, then click to 'Enable
all protection'.
Update at least weekly.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George" wrote in

message
...
Here are the clock-on-the-wall times for a normal

boot:

1. Win98 Startup Menu 0:00
2. Win98 Blue Sky Page 0:30
3. Black Screen ending C:\ 4:40
4. Green Screen arrow/timeglass 5:35
5. Icons appear on desktop 7:35
6. Timeglass disappears 8:15

Yesterday I ran Maintenance Wizard - the defrag took

about
8 hours. I thought it a good idea after removing

Norton
Anti-Virus - that was the only thing done on this

computer.

For comparison here is the Bootlog Analysis Delays

and
Failures Report run just before the above timed boot:

6:56:38 154.72 LoadSuccess =

C:\WINDOWS\IFSHLP.SYS
6:59:14 0.67 Loading Vxd =

C:\WINDOWS\system\VMM32
\IFSMGR.VXD
6:59:15 0.28 Loading Vxd =

C:\WINDOWS\system\VMM32
\IOS.VXD
6:59:19 0.72 Loading Vxd = dfs.vxd
6:59:26 0.50 DEVICEINITSUCCESS = VTD
6:59:28 0.33 Dynamic load device bios.vxd
6:59:31 0.89 Dynamic load device pci.vxd
6:59:36 0.61 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
6:59:38 3.89 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
6:59:43 0.72 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
6:59:44 0.33 DEVICEINIT = NDIS
6:59:44 4.50 Dynamic load device pppmac.vxd
6:59:50 3.22 Dynamic load device vdhcp.386
6:59:56 0.33 Initing hsflop.pdr
6:59:56 0.28 Initing esdi_506.pdr
6:59:57 0.61 Initing esdi_506.pdr
6:59:57 0.61 Init Success esdi_506.pdr
7:00:01 0.28 Dynamic load success
C:\WINDOWS\system\serial.vxd
7:00:02 2.44 Starting Wave Device for Voice

Modem


(MODEMWAVE\HALFDUPLEXVOICEWAVEDEVICE\ROOT&UNIMODEM 631CD54E&
COM1)
7:00:05 1.06 Dynamic load success dsound.vxd
7:00:08 93.06 InitDone = TSRQuery (time estimated)

I'm puzzled by the first entry taking 154.72 secs.

for
=C:\WINDOWS\IFSHLP\SYS. Also, I've taken a once-over

look
at the eight page clean boot troubleshooting

procedure
and
the article on clean boot by Gary Terhune that you
referenced. Am I ready to try those procedures?

Sorry to be so much trouble and to take so much of

your
time.



-----Original Message-----
BTW, when I say the actual boot time on the clock, I

mean
the boot time when you are
doing a normal boot, not a logged boot.

Another suggestion that may or may not shed any

light,
is
to do a clean boot, then
while in the clean boot environment, do a logged

boot
and
see what the log show, and
also how long the boot takes in real time on the

clock.

How to Perform Clean-Boot Troubleshooting for

Windows
98
http://support.microsoft.com?kbid=192926

"CLEAN BOOT -- What it is and why you need it." by

MS
MVP
Gary Terhune
http://snipurl.com/8gam
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"glee" wrote in message
...
George, there is nothing abnormal that I can see
there....it looks like many
bootlogs I have seen. What is the actual time it

takes
right now for your
computer
to boot, from the time you see the first boot

screen
with the memory count, to the
time you first see the Desktop load up....I mean

actual
time on the clock on the
wall?
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm

"George"

wrote
in
message
...
Uninstalled the Norton Anti-Virus program and

the
only
long delays remaining (72.33 secs. total) are

for
the
many
entries which occur before TSRQuery is run. Here

is a
copy
of the excerpted list of entries from the end of

the
detailed Bootlog Analysis Report run after
uninstalling
Norton Anti-virus and rebooting:

12:22:26 0.06 INITCOMPLETE = VFBACKUP
12:22:26 0.00 INITCOMPLETESUCCESS = VFBACKUP
12:22:26 0.06 INITCOMPLETE = SHELL
12:22:26 0.00 INITCOMPLETESUCCESS = SHELL
12:22:26 0.00 Initializing KERNEL (time

estimated)
12:22:26 0.00 LoadStart = system.drv (time
estimated)
12:22:26 0.00 LoadSuccess = system.drv (time
estimated)
12:22:26 0.00 LoadStart = keyboard.drv (time
estimated)
12:22:26 0.00 LoadSuccess = keyboard.drv

(time
estimated)
12:22:26 0.00 LoadStart = mouse.drv (time
estimated)
12:22:26 0.00 LoadSuccess = mouse.drv (time
estimated)
12:22:26 0.00 LoadStart = trid_pci.drv (time
estimated)
12:22:26 0.00 LoadStart = DIBENG.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = DIBENG.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = trid_pci.drv

(time
estimated)
12:22:26 0.00 LoadStart = mmsound.drv (time
estimated)
12:22:26 0.00 LoadSuccess = mmsound.drv (time
estimated)
12:22:26 0.00 LoadStart = comm.drv (time

estimated)
12:22:26 0.00 LoadSuccess = comm.drv (time
estimated)
12:22:26 0.00 LoadStart = gdi.exe (time

estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\SYSTEM\GDI32.DLL
(time estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time

estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time

estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time

estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time

estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\SYSTEM\GDI32.DLL
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgasys.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgasys.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgafix.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgafix.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgaoem.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgaoem.fon
(time estimated)
12:22:26 0.00 LoadSuccess = gdi.exe (time
estimated)
12:22:26 0.00 LoadStart = user.exe (time

estimated)
12:22:26 0.00 LoadStart = DDEML.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = DDEML.DLL (time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\SYSTEM\USER32.DLL
(time estimated)
12:22:26 0.00 LoadStart = USER.EXE (time

estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time

estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time

estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time

estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time

estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\SYSTEM\USER32.DLL (time estimated)
12:22:26 0.00 LoadStart = COOL.DLL (time

estimated)
12:22:26 0.00 LoadSuccess = COOL.DLL (time
estimated)
12:22:26 0.00 Init = KEYBOARD (time

estimated)
12:22:26 0.00 InitDone = KEYBOARD (time

estimated)
12:22:26 0.00 Init = Mouse (time estimated)
12:22:26 0.00 Status = Mouse driver installed

(time
estimated)
12:22:26 0.00 InitDone = Mouse (time

estimated)
12:22:26 0.00 Init = (time estimated)
12:22:26 0.00 LoadStart = DISPLAY.drv (time
estimated)
12:22:26 0.00 LoadSuccess = DISPLAY.drv (time
estimated)
12:22:26 0.00 InitDone = DISPLAY (time

estimated)
12:22:26 0.00 Init = Display Resources (time
estimated)
12:22:26 0.00 InitDone = Display Resources

(time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\serife.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\serife.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\sserife.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\sserife.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\coure.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\coure.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\symbole.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\symbole.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\smalle.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\smalle.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_czec.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_czec.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_engl.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_engl.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_fren.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_fren.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_germ.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_germ.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_ital.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_ital.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_span.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_span.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_swed.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_swed.fon (time estimated)
12:22:26 0.00 LoadSuccess = user.exe (time
estimated)
12:22:26 0.00 LoadStart = MSGSRV32.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = MSGSRV32.EXE

(time
estimated)
12:22:26 0.00 Init = Final USER (time

estimated)
12:22:26 0.00 InitDone = Final USER (time
estimated)
12:22:26 0.00 Init = Installable Drivers

(time
estimated)
12:22:26 0.00 InitDone = Installable Drivers

(time
estimated)
12:22:26 0.00 Init = TSRQuery (time

estimated)
12:22:26 72.33 InitDone = TSRQuery (time

estimated)
12:23:39 0.22 Enumerating Standard Floppy

Disk
Controller (BIOS\*PNP0700\0B)
12:23:39 0.00 Enumerated Standard Floppy

Disk
Controller (BIOS\*PNP0700\0B)

The questionable list of items seems to start
with "Initializing KERNEL" and ends

with "InitDone
=
TSRQuery." Do you know whether this is a normal
sequence
for the start-up or if there is a problem which

can be
corrected? Thinking of using anti-virus software
called EZ
ARMOR LE by Computer Associates. Your further
thoughts and
advice appreciated.


-----Original Message-----
Quoting MS MVP Richard Harper:
"TSRQuery is not to blame. There are several
unlogged
actions that happen
before TSRQuery is run, so it appears to be the
problem
even though it is
not. There's no good way to tell what's to

blame
since
the actions are not
logged."

If you didn't have the problem before and do

now,
then it
must come from some change
you made just prior to the experienced

increase in
the
boot time. Likely it is some
driver causing it. The delays due to Symantec
entries I
can't help you with, as I
do not like or use their software. Were it my
machine, I
would uninstall all the
Symantec/Norton software, and see if the boot

delay
continues.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


wrote in
message
...
Thanks Glen, the mouse load up problem is

gone.
Here is
the latest Delays and Failures Report from

Bootlog
Analyzer:

11:50:31 9.11 LoadSuccess =
C:\WINDOWS\IFSHLP.SYS
11:50:41 0.11 LoadFailed = ndis2sup.vxd
11:50:43 0.28 Loading Vxd =
C:\WINDOWS\system\VMM32
\IFSMGR.VXD
11:50:43 0.33 Loading Vxd =
C:\WINDOWS\system\VMM32
\IOS.VXD
11:50:49 3.06 LoadSuccess = vnetbios.vxd
11:50:52 2.39 Loading Vxd = C:\PROGRA~1
\SYMANTEC\SYMEVNT.386
11:50:55 0.39 Loading Vxd = dfs.vxd
11:51:09 0.06 DEVICEINITFAILED = MTRR
11:51:10 0.50 DEVICEINITSUCCESS = VTD
11:51:11 0.28 DEVICEINIT = NTKERN
11:51:13 0.39 Dynamic load device

bios.vxd
11:51:18 0.83 Dynamic load device

pci.vxd
11:51:30 0.28 DEVICEINIT = IOS
11:51:31 0.44 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
11:51:33 2.50 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
11:51:39 0.83 Started Standard Serial

Mouse
(ROOT\*PNP0F0C\0000)
11:51:41 0.61 DEVICEINIT = NDIS
11:51:46 3.89 Dynamic load device

vdhcp.386
11:51:58 0.33 Initing hsflop.pdr
11:51:58 0.44 Initing esdi_506.pdr
11:51:59 0.67 Initing esdi_506.pdr
11:51:59 0.83 Init Success esdi_506.pdr
11:52:07 0.11 INITCOMPLETEFAILED = SDVXD
11:52:11 0.33 Dynamic load success
C:\WINDOWS\system\serial.vxd
11:52:12 0.28 Enumerated Printer Port

(LPT1)
(BIOS\*PNP0400\0C)
11:52:14 0.28 Dynamic load device

dsound.vxd
11:52:15 1.11 Dynamic load success

dsound.vxd
11:52:16 0.33 Dynamic load device

vjoyd.vxd
11:52:18 7.00 INITCOMPLETE = NAVAP
11:52:25 4.28 Dynamic load device

C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVEX15.VXD
11:52:29 3.11 Dynamic load device

C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
11:52:32 125.89 Dynamic load success

C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
11:54:38 0.28 INITCOMPLETESUCCESS = NAVAP
11:54:45 99.50 InitDone = TSRQuery (time
estimated)
11:56:25 0.83 Enumerating Standard Floppy

Disk
Controller (BIOS\*PNP0700\0B)

The two delays that stick out are, of course,

the
Norton
(Symantec) anti-virus program stuff and the
TSRQuery
items.
Any further help to hone in on those two

delay
places
will
be appreciated.


-----Original Message-----
My Logitech plugs into a serial port. What I

did
to
replace with a standard mouse driver was

this:
StartSettingsC. PanelSystemDevice

Manager
TabMouseHi-
lite MouseDriver TabUpdate Driver

buttonNext
buttonSelected Search for Better

Driver...etc.
After the search, a better MS driver was

found
and I
okayed its installation.

I will uninstall Logitech mouse and reboot.
Thanks for
the
explanation - sorry didn't get it the first

time!

-----Original Message-----
You say you replaced the Logitech mouse

driver
with a
standard mouse driver. Do you
have a serial mouse or a PS/2 mouse? The

driver
you
added is "Standard Serial
Mouse", which is only for a serial mouse,

and
you are
still loading the Logitech
driver.....Loading Vxd = LMOUSE.VXD

What I meant for you to try is to remove
(uninstall)
the
Logitech mouse (not add a
mouse manually), reboot, and let Windows

add
its
own
driver on its own.

I will see what else I can find re your

delays.
A lot
of
them are from Symantec
anti-virus loading, though the 8-minute

time
is
far
too
long.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George"


wrote
in
message
news:5c0d01c491f8$abc3cf70

...
Have never used MSBackup, so uninstalled

and
then
changed
file names per instruction. The tape

detection
has
been
disabled and it seems to be working okay

so
far!
Here is a copy of the new Failures and

Delays
Log:

14:52:30 7.28 LoadSuccess =
C:\WINDOWS\IFSHLP.SYS
14:52:38 0.11 LoadFailed =

ndis2sup.vxd
14:52:40 0.44 Loading Vxd =
C:\WINDOWS\system\VMM32
\IFSMGR.VXD
14:52:46 2.72 LoadSuccess =

vnetbios.vxd
14:52:49 1.11 Loading Vxd =

C:\PROGRA~1
\SYMANTEC\SYMEVNT.386
14:52:50 20.17 Loading Vxd =

LMOUSE.VXD
14:53:11 0.61 Loading Vxd = dfs.vxd
14:53:24 0.06 DEVICEINITFAILED =

MTRR
14:53:25 0.56 DEVICEINITSUCCESS =

VTD
14:53:26 0.28 DEVICEINIT = NTKERN
14:53:33 0.78 Dynamic load device

pci.vxd
14:53:44 0.39 DEVICEINIT = IOS
14:53:46 0.50 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
14:53:48 2.33 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
14:53:53 0.78 Started Standard Serial

Mouse
(ROOT\*PNP0F0C\0000)
14:53:56 0.50 DEVICEINIT = NDIS
14:54:01 2.11 Dynamic load device
vdhcp.386
14:54:10 0.56 DEVICEINITSUCCESS =

VDEF
14:54:14 2.22 INITCOMPLETE = IOS
14:54:17 10.39 INITCOMPLETESUCCESS =

IOS
14:54:30 0.06 INITCOMPLETEFAILED =

SDVXD
14:54:35 0.33 Dynamic load success
C:\WINDOWS\system\serial.vxd
14:54:38 2.56 Dynamic load success
dsound.vxd
14:54:41 0.44 Dynamic load device
vjoyd.vxd
14:54:43 7.61 INITCOMPLETE = NAVAP
14:54:50 4.61 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVEX15.VXD
14:54:55 2.50 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVENG.VXD
14:54:58 75.83 Dynamic load success
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVENG.VXD
14:56:14 0.67 INITCOMPLETESUCCESS =

NAVAP


.

.


.



.


.


.

  #42  
Old September 8th 04, 10:20 PM
SFB - KB3MM
external usenet poster
 
Posts: n/a
Default

Yes. The system can spend a lot of time trying and trying and trying to
read and re=read a sector.

"glee" wrote in message
...
Exactly....this is one of the things I am thinking also. I just haven't

time till
tonight to write a lengthy reply. :-)
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm

"SFB - KB3MM" wrote in message
...
Is your disk in good shape ?
Wondering if you should download the
disk diagnostic from the disk mfgr's web site and run the

non-destructive
tests.

Might have a flakey sector or two

"George" wrote in message
...
Hello Glen. I'm using a dial-up connection and the best
speed we get in this area is usually 28,000 bps. Not on
any type of network, just a simple home set-up on a Dell
Precision 486 purchased the end of 1993 upgraded 1997 to
AMD K-6 chip, 96 RAM, 4GB HD - think the OS started with
Win3.1, then Win95 and upgraded to Win 98SE.

Earlier you had me do a full system virus scan which I did
do. Next, I was able to download Spybot and Adaware but
not CWShredder. For some reason CWShredder would not
download into my system. I ran Spybot and Adaware for
several days, then cleared them out. Adaware found nothing
and Spybot found one item which was promptly removed.
Right now I'm operating without an anti-virus program as
Norton Anti-Virus was uninstalled day before yesterday
since we thought it might be behind the long boot
problems. Also, I think I want to change to another anti-
virus program. But I'm being careful and only coming to
this support.microsoft.com site when on the internet.

I have run the clean boot procedure from the Gary Terhune
article recommended earlier. After completing his "clean
boot" list, this is what the Bootlog Analysis Report
(Delays) looked like:

6:56:38 154.72 LoadSuccess = C:\WINDOWS\IFSHLP.SYS
6:59:14 0.67 Loading Vxd = C:\WINDOWS\system\VMM32
\IFSMGR.VXD
6:59:15 0.28 Loading Vxd = C:\WINDOWS\system\VMM32
\IOS.VXD
6:59:19 0.72 Loading Vxd = dfs.vxd
6:59:26 0.50 DEVICEINITSUCCESS = VTD
6:59:28 0.33 Dynamic load device bios.vxd
6:59:31 0.89 Dynamic load device pci.vxd
6:59:36 0.61 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
6:59:38 3.89 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
6:59:43 0.72 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
6:59:44 0.33 DEVICEINIT = NDIS
6:59:44 4.50 Dynamic load device pppmac.vxd
6:59:50 3.22 Dynamic load device vdhcp.386
6:59:56 0.33 Initing hsflop.pdr
6:59:56 0.28 Initing esdi_506.pdr
6:59:57 0.61 Initing esdi_506.pdr
6:59:57 0.61 Init Success esdi_506.pdr
7:00:01 0.28 Dynamic load success
C:\WINDOWS\system\serial.vxd
7:00:02 2.44 Starting Wave Device for Voice Modem
(MODEMWAVE\HALFDUPLEXVOICEWAVEDEVICE\ROOT&UNIMODEM 631CD54E&
COM1)
7:00:05 1.06 Dynamic load success dsound.vxd
7:00:08 93.06 InitDone = TSRQuery (time estimated)

The above test was run yesterday morning (Tuesday 7 Sep
04), and this morning the same report showed 349 seconds
for = C:\WINDOWS\IFSHLP.SYS!! The clock-on-the-wall time
for yesterday's report displayed above was 8 min. 55 secs.
This covers the time from when the Win 98 Menu first
appears until the full icons appear on the desktop. Don't
understand why the time on the Bootlog Analysis Report is
much shorter.

An icon double-clicked on the desktop then takes another
55 secs. to pull up that selected item, but after it's
been used that first time and then closed and reopened -
the icon/progam/item responds by opening at normal speed
(about 5 secs). This is another symptom that has continued
since it first slowed down about two weeks ago - seems
related.

How does one examen the time used in C:\WINDOWS\IFHLP\SYS?
Your continued direction and advice appreciated.




-----Original Message-----
George, are you using a broadband connection or a dial-up
connection? Do you have a
Network card (NIC) or integrated network interface in the
computer? Are you on any
type of network?

Also, I suggest you do a complete check for
malware/adwa

Update your anti-virus app and then run a full-system
virus scan.

Use CWShredder, the CoolWeb removal tool, available he
http://www.majorgeeks.com/downloads31.html
http://aumha.org/downloads/cwshredder.zip
Close all browser windows and open apps, start CWShredder
and click the Fix button.

In addition, install Ad-Aware SE free edition, start it,
click its 'Check for
Updates' link in the app to install updates, then use it
to scan your system, and
remove what it finds.
Ad-Awa
http://www.lavasoftusa.com/support/download/

Install, update and run SpyBot Search & Destroy, scan
your system, and then remove
the items in RED only.
SpyBot S&D:
http://www.safer-networking.org/index.php?page=download

Install SpywareBlaster:
http://www.majorgeeks.com/download2859.html
Click the link in the app to check for and install
updates, then click to 'Enable
all protection'.
Update at least weekly.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George" wrote in
message
...
Here are the clock-on-the-wall times for a normal boot:

1. Win98 Startup Menu 0:00
2. Win98 Blue Sky Page 0:30
3. Black Screen ending C:\ 4:40
4. Green Screen arrow/timeglass 5:35
5. Icons appear on desktop 7:35
6. Timeglass disappears 8:15

Yesterday I ran Maintenance Wizard - the defrag took
about
8 hours. I thought it a good idea after removing Norton
Anti-Virus - that was the only thing done on this
computer.

For comparison here is the Bootlog Analysis Delays and
Failures Report run just before the above timed boot:

6:56:38 154.72 LoadSuccess = C:\WINDOWS\IFSHLP.SYS
6:59:14 0.67 Loading Vxd = C:\WINDOWS\system\VMM32
\IFSMGR.VXD
6:59:15 0.28 Loading Vxd = C:\WINDOWS\system\VMM32
\IOS.VXD
6:59:19 0.72 Loading Vxd = dfs.vxd
6:59:26 0.50 DEVICEINITSUCCESS = VTD
6:59:28 0.33 Dynamic load device bios.vxd
6:59:31 0.89 Dynamic load device pci.vxd
6:59:36 0.61 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
6:59:38 3.89 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
6:59:43 0.72 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
6:59:44 0.33 DEVICEINIT = NDIS
6:59:44 4.50 Dynamic load device pppmac.vxd
6:59:50 3.22 Dynamic load device vdhcp.386
6:59:56 0.33 Initing hsflop.pdr
6:59:56 0.28 Initing esdi_506.pdr
6:59:57 0.61 Initing esdi_506.pdr
6:59:57 0.61 Init Success esdi_506.pdr
7:00:01 0.28 Dynamic load success
C:\WINDOWS\system\serial.vxd
7:00:02 2.44 Starting Wave Device for Voice Modem

(MODEMWAVE\HALFDUPLEXVOICEWAVEDEVICE\ROOT&UNIMODEM 631CD54E&
COM1)
7:00:05 1.06 Dynamic load success dsound.vxd
7:00:08 93.06 InitDone = TSRQuery (time estimated)

I'm puzzled by the first entry taking 154.72 secs. for
=C:\WINDOWS\IFSHLP\SYS. Also, I've taken a once-over
look
at the eight page clean boot troubleshooting procedure
and
the article on clean boot by Gary Terhune that you
referenced. Am I ready to try those procedures?

Sorry to be so much trouble and to take so much of your
time.



-----Original Message-----
BTW, when I say the actual boot time on the clock, I
mean
the boot time when you are
doing a normal boot, not a logged boot.

Another suggestion that may or may not shed any light,
is
to do a clean boot, then
while in the clean boot environment, do a logged boot
and
see what the log show, and
also how long the boot takes in real time on the clock.

How to Perform Clean-Boot Troubleshooting for Windows
98
http://support.microsoft.com?kbid=192926

"CLEAN BOOT -- What it is and why you need it." by MS
MVP
Gary Terhune
http://snipurl.com/8gam
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"glee" wrote in message
...
George, there is nothing abnormal that I can see
there....it looks like many
bootlogs I have seen. What is the actual time it
takes
right now for your
computer
to boot, from the time you see the first boot screen
with the memory count, to the
time you first see the Desktop load up....I mean
actual
time on the clock on the
wall?
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm

"George" wrote
in
message
...
Uninstalled the Norton Anti-Virus program and the
only
long delays remaining (72.33 secs. total) are for
the
many
entries which occur before TSRQuery is run. Here
is a
copy
of the excerpted list of entries from the end of
the
detailed Bootlog Analysis Report run after
uninstalling
Norton Anti-virus and rebooting:

12:22:26 0.06 INITCOMPLETE = VFBACKUP
12:22:26 0.00 INITCOMPLETESUCCESS = VFBACKUP
12:22:26 0.06 INITCOMPLETE = SHELL
12:22:26 0.00 INITCOMPLETESUCCESS = SHELL
12:22:26 0.00 Initializing KERNEL (time
estimated)
12:22:26 0.00 LoadStart = system.drv (time
estimated)
12:22:26 0.00 LoadSuccess = system.drv (time
estimated)
12:22:26 0.00 LoadStart = keyboard.drv (time
estimated)
12:22:26 0.00 LoadSuccess = keyboard.drv (time
estimated)
12:22:26 0.00 LoadStart = mouse.drv (time
estimated)
12:22:26 0.00 LoadSuccess = mouse.drv (time
estimated)
12:22:26 0.00 LoadStart = trid_pci.drv (time
estimated)
12:22:26 0.00 LoadStart = DIBENG.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = DIBENG.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = trid_pci.drv (time
estimated)
12:22:26 0.00 LoadStart = mmsound.drv (time
estimated)
12:22:26 0.00 LoadSuccess = mmsound.drv (time
estimated)
12:22:26 0.00 LoadStart = comm.drv (time
estimated)
12:22:26 0.00 LoadSuccess = comm.drv (time
estimated)
12:22:26 0.00 LoadStart = gdi.exe (time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\SYSTEM\GDI32.DLL
(time estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\SYSTEM\GDI32.DLL
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgasys.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgasys.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgafix.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgafix.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgaoem.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgaoem.fon
(time estimated)
12:22:26 0.00 LoadSuccess = gdi.exe (time
estimated)
12:22:26 0.00 LoadStart = user.exe (time
estimated)
12:22:26 0.00 LoadStart = DDEML.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = DDEML.DLL (time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\SYSTEM\USER32.DLL
(time estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\SYSTEM\USER32.DLL (time estimated)
12:22:26 0.00 LoadStart = COOL.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = COOL.DLL (time
estimated)
12:22:26 0.00 Init = KEYBOARD (time estimated)
12:22:26 0.00 InitDone = KEYBOARD (time
estimated)
12:22:26 0.00 Init = Mouse (time estimated)
12:22:26 0.00 Status = Mouse driver installed
(time
estimated)
12:22:26 0.00 InitDone = Mouse (time estimated)
12:22:26 0.00 Init = (time estimated)
12:22:26 0.00 LoadStart = DISPLAY.drv (time
estimated)
12:22:26 0.00 LoadSuccess = DISPLAY.drv (time
estimated)
12:22:26 0.00 InitDone = DISPLAY (time
estimated)
12:22:26 0.00 Init = Display Resources (time
estimated)
12:22:26 0.00 InitDone = Display Resources (time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\serife.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\serife.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\sserife.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\sserife.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\coure.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\coure.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\symbole.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\symbole.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\smalle.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\smalle.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_czec.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_czec.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_engl.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_engl.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_fren.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_fren.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_germ.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_germ.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_ital.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_ital.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_span.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_span.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_swed.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_swed.fon (time estimated)
12:22:26 0.00 LoadSuccess = user.exe (time
estimated)
12:22:26 0.00 LoadStart = MSGSRV32.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = MSGSRV32.EXE (time
estimated)
12:22:26 0.00 Init = Final USER (time estimated)
12:22:26 0.00 InitDone = Final USER (time
estimated)
12:22:26 0.00 Init = Installable Drivers (time
estimated)
12:22:26 0.00 InitDone = Installable Drivers
(time
estimated)
12:22:26 0.00 Init = TSRQuery (time estimated)
12:22:26 72.33 InitDone = TSRQuery (time
estimated)
12:23:39 0.22 Enumerating Standard Floppy Disk
Controller (BIOS\*PNP0700\0B)
12:23:39 0.00 Enumerated Standard Floppy Disk
Controller (BIOS\*PNP0700\0B)

The questionable list of items seems to start
with "Initializing KERNEL" and ends with "InitDone
=
TSRQuery." Do you know whether this is a normal
sequence
for the start-up or if there is a problem which
can be
corrected? Thinking of using anti-virus software
called EZ
ARMOR LE by Computer Associates. Your further
thoughts and
advice appreciated.


-----Original Message-----
Quoting MS MVP Richard Harper:
"TSRQuery is not to blame. There are several
unlogged
actions that happen
before TSRQuery is run, so it appears to be the
problem
even though it is
not. There's no good way to tell what's to blame
since
the actions are not
logged."

If you didn't have the problem before and do now,
then it
must come from some change
you made just prior to the experienced increase in
the
boot time. Likely it is some
driver causing it. The delays due to Symantec
entries I
can't help you with, as I
do not like or use their software. Were it my
machine, I
would uninstall all the
Symantec/Norton software, and see if the boot
delay
continues.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


wrote in
message
...
Thanks Glen, the mouse load up problem is gone.
Here is
the latest Delays and Failures Report from
Bootlog
Analyzer:

11:50:31 9.11 LoadSuccess =
C:\WINDOWS\IFSHLP.SYS
11:50:41 0.11 LoadFailed = ndis2sup.vxd
11:50:43 0.28 Loading Vxd =
C:\WINDOWS\system\VMM32
\IFSMGR.VXD
11:50:43 0.33 Loading Vxd =
C:\WINDOWS\system\VMM32
\IOS.VXD
11:50:49 3.06 LoadSuccess = vnetbios.vxd
11:50:52 2.39 Loading Vxd = C:\PROGRA~1
\SYMANTEC\SYMEVNT.386
11:50:55 0.39 Loading Vxd = dfs.vxd
11:51:09 0.06 DEVICEINITFAILED = MTRR
11:51:10 0.50 DEVICEINITSUCCESS = VTD
11:51:11 0.28 DEVICEINIT = NTKERN
11:51:13 0.39 Dynamic load device bios.vxd
11:51:18 0.83 Dynamic load device pci.vxd
11:51:30 0.28 DEVICEINIT = IOS
11:51:31 0.44 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
11:51:33 2.50 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
11:51:39 0.83 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
11:51:41 0.61 DEVICEINIT = NDIS
11:51:46 3.89 Dynamic load device vdhcp.386
11:51:58 0.33 Initing hsflop.pdr
11:51:58 0.44 Initing esdi_506.pdr
11:51:59 0.67 Initing esdi_506.pdr
11:51:59 0.83 Init Success esdi_506.pdr
11:52:07 0.11 INITCOMPLETEFAILED = SDVXD
11:52:11 0.33 Dynamic load success
C:\WINDOWS\system\serial.vxd
11:52:12 0.28 Enumerated Printer Port (LPT1)
(BIOS\*PNP0400\0C)
11:52:14 0.28 Dynamic load device
dsound.vxd
11:52:15 1.11 Dynamic load success
dsound.vxd
11:52:16 0.33 Dynamic load device vjoyd.vxd
11:52:18 7.00 INITCOMPLETE = NAVAP
11:52:25 4.28 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVEX15.VXD
11:52:29 3.11 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
11:52:32 125.89 Dynamic load success
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
11:54:38 0.28 INITCOMPLETESUCCESS = NAVAP
11:54:45 99.50 InitDone = TSRQuery (time
estimated)
11:56:25 0.83 Enumerating Standard Floppy
Disk
Controller (BIOS\*PNP0700\0B)

The two delays that stick out are, of course,
the
Norton
(Symantec) anti-virus program stuff and the
TSRQuery
items.
Any further help to hone in on those two delay
places
will
be appreciated.


-----Original Message-----
My Logitech plugs into a serial port. What I
did
to
replace with a standard mouse driver was this:
StartSettingsC. PanelSystemDevice Manager
TabMouseHi-
lite MouseDriver TabUpdate Driver buttonNext
buttonSelected Search for Better Driver...etc.
After the search, a better MS driver was found
and I
okayed its installation.

I will uninstall Logitech mouse and reboot.
Thanks for
the
explanation - sorry didn't get it the first
time!

-----Original Message-----
You say you replaced the Logitech mouse driver
with a
standard mouse driver. Do you
have a serial mouse or a PS/2 mouse? The
driver
you
added is "Standard Serial
Mouse", which is only for a serial mouse, and
you are
still loading the Logitech
driver.....Loading Vxd = LMOUSE.VXD

What I meant for you to try is to remove
(uninstall)
the
Logitech mouse (not add a
mouse manually), reboot, and let Windows add
its
own
driver on its own.

I will see what else I can find re your
delays.
A lot
of
them are from Symantec
anti-virus loading, though the 8-minute time
is
far
too
long.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George"
wrote
in
message
...
Have never used MSBackup, so uninstalled and
then
changed
file names per instruction. The tape
detection
has
been
disabled and it seems to be working okay so
far!
Here is a copy of the new Failures and
Delays
Log:

14:52:30 7.28 LoadSuccess =
C:\WINDOWS\IFSHLP.SYS
14:52:38 0.11 LoadFailed = ndis2sup.vxd
14:52:40 0.44 Loading Vxd =
C:\WINDOWS\system\VMM32
\IFSMGR.VXD
14:52:46 2.72 LoadSuccess = vnetbios.vxd
14:52:49 1.11 Loading Vxd = C:\PROGRA~1
\SYMANTEC\SYMEVNT.386
14:52:50 20.17 Loading Vxd = LMOUSE.VXD
14:53:11 0.61 Loading Vxd = dfs.vxd
14:53:24 0.06 DEVICEINITFAILED = MTRR
14:53:25 0.56 DEVICEINITSUCCESS = VTD
14:53:26 0.28 DEVICEINIT = NTKERN
14:53:33 0.78 Dynamic load device
pci.vxd
14:53:44 0.39 DEVICEINIT = IOS
14:53:46 0.50 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
14:53:48 2.33 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
14:53:53 0.78 Started Standard Serial
Mouse
(ROOT\*PNP0F0C\0000)
14:53:56 0.50 DEVICEINIT = NDIS
14:54:01 2.11 Dynamic load device
vdhcp.386
14:54:10 0.56 DEVICEINITSUCCESS = VDEF
14:54:14 2.22 INITCOMPLETE = IOS
14:54:17 10.39 INITCOMPLETESUCCESS = IOS
14:54:30 0.06 INITCOMPLETEFAILED =
SDVXD
14:54:35 0.33 Dynamic load success
C:\WINDOWS\system\serial.vxd
14:54:38 2.56 Dynamic load success
dsound.vxd
14:54:41 0.44 Dynamic load device
vjoyd.vxd
14:54:43 7.61 INITCOMPLETE = NAVAP
14:54:50 4.61 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVEX15.VXD
14:54:55 2.50 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
14:54:58 75.83 Dynamic load success
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
14:56:14 0.67 INITCOMPLETESUCCESS =
NAVAP


.

.


.



.


.




  #43  
Old September 8th 04, 10:20 PM posted to microsoft.public.win98.performance
SFB - KB3MM
external usenet poster
 
Posts: 129
Default Interpretation of failures and delays at boot.

Yes. The system can spend a lot of time trying and trying and trying to
read and re=read a sector.

"glee" wrote in message
...
Exactly....this is one of the things I am thinking also. I just haven't

time till
tonight to write a lengthy reply. :-)
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm

"SFB - KB3MM" wrote in message
...
Is your disk in good shape ?
Wondering if you should download the
disk diagnostic from the disk mfgr's web site and run the

non-destructive
tests.

Might have a flakey sector or two

"George" wrote in message
...
Hello Glen. I'm using a dial-up connection and the best
speed we get in this area is usually 28,000 bps. Not on
any type of network, just a simple home set-up on a Dell
Precision 486 purchased the end of 1993 upgraded 1997 to
AMD K-6 chip, 96 RAM, 4GB HD - think the OS started with
Win3.1, then Win95 and upgraded to Win 98SE.

Earlier you had me do a full system virus scan which I did
do. Next, I was able to download Spybot and Adaware but
not CWShredder. For some reason CWShredder would not
download into my system. I ran Spybot and Adaware for
several days, then cleared them out. Adaware found nothing
and Spybot found one item which was promptly removed.
Right now I'm operating without an anti-virus program as
Norton Anti-Virus was uninstalled day before yesterday
since we thought it might be behind the long boot
problems. Also, I think I want to change to another anti-
virus program. But I'm being careful and only coming to
this support.microsoft.com site when on the internet.

I have run the clean boot procedure from the Gary Terhune
article recommended earlier. After completing his "clean
boot" list, this is what the Bootlog Analysis Report
(Delays) looked like:

6:56:38 154.72 LoadSuccess = C:\WINDOWS\IFSHLP.SYS
6:59:14 0.67 Loading Vxd = C:\WINDOWS\system\VMM32
\IFSMGR.VXD
6:59:15 0.28 Loading Vxd = C:\WINDOWS\system\VMM32
\IOS.VXD
6:59:19 0.72 Loading Vxd = dfs.vxd
6:59:26 0.50 DEVICEINITSUCCESS = VTD
6:59:28 0.33 Dynamic load device bios.vxd
6:59:31 0.89 Dynamic load device pci.vxd
6:59:36 0.61 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
6:59:38 3.89 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
6:59:43 0.72 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
6:59:44 0.33 DEVICEINIT = NDIS
6:59:44 4.50 Dynamic load device pppmac.vxd
6:59:50 3.22 Dynamic load device vdhcp.386
6:59:56 0.33 Initing hsflop.pdr
6:59:56 0.28 Initing esdi_506.pdr
6:59:57 0.61 Initing esdi_506.pdr
6:59:57 0.61 Init Success esdi_506.pdr
7:00:01 0.28 Dynamic load success
C:\WINDOWS\system\serial.vxd
7:00:02 2.44 Starting Wave Device for Voice Modem
(MODEMWAVE\HALFDUPLEXVOICEWAVEDEVICE\ROOT&UNIMODEM 631CD54E&
COM1)
7:00:05 1.06 Dynamic load success dsound.vxd
7:00:08 93.06 InitDone = TSRQuery (time estimated)

The above test was run yesterday morning (Tuesday 7 Sep
04), and this morning the same report showed 349 seconds
for = C:\WINDOWS\IFSHLP.SYS!! The clock-on-the-wall time
for yesterday's report displayed above was 8 min. 55 secs.
This covers the time from when the Win 98 Menu first
appears until the full icons appear on the desktop. Don't
understand why the time on the Bootlog Analysis Report is
much shorter.

An icon double-clicked on the desktop then takes another
55 secs. to pull up that selected item, but after it's
been used that first time and then closed and reopened -
the icon/progam/item responds by opening at normal speed
(about 5 secs). This is another symptom that has continued
since it first slowed down about two weeks ago - seems
related.

How does one examen the time used in C:\WINDOWS\IFHLP\SYS?
Your continued direction and advice appreciated.




-----Original Message-----
George, are you using a broadband connection or a dial-up
connection? Do you have a
Network card (NIC) or integrated network interface in the
computer? Are you on any
type of network?

Also, I suggest you do a complete check for
malware/adwa

Update your anti-virus app and then run a full-system
virus scan.

Use CWShredder, the CoolWeb removal tool, available he
http://www.majorgeeks.com/downloads31.html
http://aumha.org/downloads/cwshredder.zip
Close all browser windows and open apps, start CWShredder
and click the Fix button.

In addition, install Ad-Aware SE free edition, start it,
click its 'Check for
Updates' link in the app to install updates, then use it
to scan your system, and
remove what it finds.
Ad-Awa
http://www.lavasoftusa.com/support/download/

Install, update and run SpyBot Search & Destroy, scan
your system, and then remove
the items in RED only.
SpyBot S&D:
http://www.safer-networking.org/index.php?page=download

Install SpywareBlaster:
http://www.majorgeeks.com/download2859.html
Click the link in the app to check for and install
updates, then click to 'Enable
all protection'.
Update at least weekly.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George" wrote in
message
...
Here are the clock-on-the-wall times for a normal boot:

1. Win98 Startup Menu 0:00
2. Win98 Blue Sky Page 0:30
3. Black Screen ending C:\ 4:40
4. Green Screen arrow/timeglass 5:35
5. Icons appear on desktop 7:35
6. Timeglass disappears 8:15

Yesterday I ran Maintenance Wizard - the defrag took
about
8 hours. I thought it a good idea after removing Norton
Anti-Virus - that was the only thing done on this
computer.

For comparison here is the Bootlog Analysis Delays and
Failures Report run just before the above timed boot:

6:56:38 154.72 LoadSuccess = C:\WINDOWS\IFSHLP.SYS
6:59:14 0.67 Loading Vxd = C:\WINDOWS\system\VMM32
\IFSMGR.VXD
6:59:15 0.28 Loading Vxd = C:\WINDOWS\system\VMM32
\IOS.VXD
6:59:19 0.72 Loading Vxd = dfs.vxd
6:59:26 0.50 DEVICEINITSUCCESS = VTD
6:59:28 0.33 Dynamic load device bios.vxd
6:59:31 0.89 Dynamic load device pci.vxd
6:59:36 0.61 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
6:59:38 3.89 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
6:59:43 0.72 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
6:59:44 0.33 DEVICEINIT = NDIS
6:59:44 4.50 Dynamic load device pppmac.vxd
6:59:50 3.22 Dynamic load device vdhcp.386
6:59:56 0.33 Initing hsflop.pdr
6:59:56 0.28 Initing esdi_506.pdr
6:59:57 0.61 Initing esdi_506.pdr
6:59:57 0.61 Init Success esdi_506.pdr
7:00:01 0.28 Dynamic load success
C:\WINDOWS\system\serial.vxd
7:00:02 2.44 Starting Wave Device for Voice Modem

(MODEMWAVE\HALFDUPLEXVOICEWAVEDEVICE\ROOT&UNIMODEM 631CD54E&
COM1)
7:00:05 1.06 Dynamic load success dsound.vxd
7:00:08 93.06 InitDone = TSRQuery (time estimated)

I'm puzzled by the first entry taking 154.72 secs. for
=C:\WINDOWS\IFSHLP\SYS. Also, I've taken a once-over
look
at the eight page clean boot troubleshooting procedure
and
the article on clean boot by Gary Terhune that you
referenced. Am I ready to try those procedures?

Sorry to be so much trouble and to take so much of your
time.



-----Original Message-----
BTW, when I say the actual boot time on the clock, I
mean
the boot time when you are
doing a normal boot, not a logged boot.

Another suggestion that may or may not shed any light,
is
to do a clean boot, then
while in the clean boot environment, do a logged boot
and
see what the log show, and
also how long the boot takes in real time on the clock.

How to Perform Clean-Boot Troubleshooting for Windows
98
http://support.microsoft.com?kbid=192926

"CLEAN BOOT -- What it is and why you need it." by MS
MVP
Gary Terhune
http://snipurl.com/8gam
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"glee" wrote in message
...
George, there is nothing abnormal that I can see
there....it looks like many
bootlogs I have seen. What is the actual time it
takes
right now for your
computer
to boot, from the time you see the first boot screen
with the memory count, to the
time you first see the Desktop load up....I mean
actual
time on the clock on the
wall?
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm

"George" wrote
in
message
...
Uninstalled the Norton Anti-Virus program and the
only
long delays remaining (72.33 secs. total) are for
the
many
entries which occur before TSRQuery is run. Here
is a
copy
of the excerpted list of entries from the end of
the
detailed Bootlog Analysis Report run after
uninstalling
Norton Anti-virus and rebooting:

12:22:26 0.06 INITCOMPLETE = VFBACKUP
12:22:26 0.00 INITCOMPLETESUCCESS = VFBACKUP
12:22:26 0.06 INITCOMPLETE = SHELL
12:22:26 0.00 INITCOMPLETESUCCESS = SHELL
12:22:26 0.00 Initializing KERNEL (time
estimated)
12:22:26 0.00 LoadStart = system.drv (time
estimated)
12:22:26 0.00 LoadSuccess = system.drv (time
estimated)
12:22:26 0.00 LoadStart = keyboard.drv (time
estimated)
12:22:26 0.00 LoadSuccess = keyboard.drv (time
estimated)
12:22:26 0.00 LoadStart = mouse.drv (time
estimated)
12:22:26 0.00 LoadSuccess = mouse.drv (time
estimated)
12:22:26 0.00 LoadStart = trid_pci.drv (time
estimated)
12:22:26 0.00 LoadStart = DIBENG.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = DIBENG.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = trid_pci.drv (time
estimated)
12:22:26 0.00 LoadStart = mmsound.drv (time
estimated)
12:22:26 0.00 LoadSuccess = mmsound.drv (time
estimated)
12:22:26 0.00 LoadStart = comm.drv (time
estimated)
12:22:26 0.00 LoadSuccess = comm.drv (time
estimated)
12:22:26 0.00 LoadStart = gdi.exe (time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\SYSTEM\GDI32.DLL
(time estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\SYSTEM\GDI32.DLL
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgasys.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgasys.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgafix.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgafix.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgaoem.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgaoem.fon
(time estimated)
12:22:26 0.00 LoadSuccess = gdi.exe (time
estimated)
12:22:26 0.00 LoadStart = user.exe (time
estimated)
12:22:26 0.00 LoadStart = DDEML.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = DDEML.DLL (time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\SYSTEM\USER32.DLL
(time estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\SYSTEM\USER32.DLL (time estimated)
12:22:26 0.00 LoadStart = COOL.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = COOL.DLL (time
estimated)
12:22:26 0.00 Init = KEYBOARD (time estimated)
12:22:26 0.00 InitDone = KEYBOARD (time
estimated)
12:22:26 0.00 Init = Mouse (time estimated)
12:22:26 0.00 Status = Mouse driver installed
(time
estimated)
12:22:26 0.00 InitDone = Mouse (time estimated)
12:22:26 0.00 Init = (time estimated)
12:22:26 0.00 LoadStart = DISPLAY.drv (time
estimated)
12:22:26 0.00 LoadSuccess = DISPLAY.drv (time
estimated)
12:22:26 0.00 InitDone = DISPLAY (time
estimated)
12:22:26 0.00 Init = Display Resources (time
estimated)
12:22:26 0.00 InitDone = Display Resources (time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\serife.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\serife.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\sserife.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\sserife.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\coure.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\coure.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\symbole.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\symbole.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\smalle.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\smalle.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_czec.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_czec.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_engl.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_engl.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_fren.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_fren.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_germ.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_germ.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_ital.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_ital.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_span.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_span.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_swed.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_swed.fon (time estimated)
12:22:26 0.00 LoadSuccess = user.exe (time
estimated)
12:22:26 0.00 LoadStart = MSGSRV32.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = MSGSRV32.EXE (time
estimated)
12:22:26 0.00 Init = Final USER (time estimated)
12:22:26 0.00 InitDone = Final USER (time
estimated)
12:22:26 0.00 Init = Installable Drivers (time
estimated)
12:22:26 0.00 InitDone = Installable Drivers
(time
estimated)
12:22:26 0.00 Init = TSRQuery (time estimated)
12:22:26 72.33 InitDone = TSRQuery (time
estimated)
12:23:39 0.22 Enumerating Standard Floppy Disk
Controller (BIOS\*PNP0700\0B)
12:23:39 0.00 Enumerated Standard Floppy Disk
Controller (BIOS\*PNP0700\0B)

The questionable list of items seems to start
with "Initializing KERNEL" and ends with "InitDone
=
TSRQuery." Do you know whether this is a normal
sequence
for the start-up or if there is a problem which
can be
corrected? Thinking of using anti-virus software
called EZ
ARMOR LE by Computer Associates. Your further
thoughts and
advice appreciated.


-----Original Message-----
Quoting MS MVP Richard Harper:
"TSRQuery is not to blame. There are several
unlogged
actions that happen
before TSRQuery is run, so it appears to be the
problem
even though it is
not. There's no good way to tell what's to blame
since
the actions are not
logged."

If you didn't have the problem before and do now,
then it
must come from some change
you made just prior to the experienced increase in
the
boot time. Likely it is some
driver causing it. The delays due to Symantec
entries I
can't help you with, as I
do not like or use their software. Were it my
machine, I
would uninstall all the
Symantec/Norton software, and see if the boot
delay
continues.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


wrote in
message
...
Thanks Glen, the mouse load up problem is gone.
Here is
the latest Delays and Failures Report from
Bootlog
Analyzer:

11:50:31 9.11 LoadSuccess =
C:\WINDOWS\IFSHLP.SYS
11:50:41 0.11 LoadFailed = ndis2sup.vxd
11:50:43 0.28 Loading Vxd =
C:\WINDOWS\system\VMM32
\IFSMGR.VXD
11:50:43 0.33 Loading Vxd =
C:\WINDOWS\system\VMM32
\IOS.VXD
11:50:49 3.06 LoadSuccess = vnetbios.vxd
11:50:52 2.39 Loading Vxd = C:\PROGRA~1
\SYMANTEC\SYMEVNT.386
11:50:55 0.39 Loading Vxd = dfs.vxd
11:51:09 0.06 DEVICEINITFAILED = MTRR
11:51:10 0.50 DEVICEINITSUCCESS = VTD
11:51:11 0.28 DEVICEINIT = NTKERN
11:51:13 0.39 Dynamic load device bios.vxd
11:51:18 0.83 Dynamic load device pci.vxd
11:51:30 0.28 DEVICEINIT = IOS
11:51:31 0.44 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
11:51:33 2.50 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
11:51:39 0.83 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
11:51:41 0.61 DEVICEINIT = NDIS
11:51:46 3.89 Dynamic load device vdhcp.386
11:51:58 0.33 Initing hsflop.pdr
11:51:58 0.44 Initing esdi_506.pdr
11:51:59 0.67 Initing esdi_506.pdr
11:51:59 0.83 Init Success esdi_506.pdr
11:52:07 0.11 INITCOMPLETEFAILED = SDVXD
11:52:11 0.33 Dynamic load success
C:\WINDOWS\system\serial.vxd
11:52:12 0.28 Enumerated Printer Port (LPT1)
(BIOS\*PNP0400\0C)
11:52:14 0.28 Dynamic load device
dsound.vxd
11:52:15 1.11 Dynamic load success
dsound.vxd
11:52:16 0.33 Dynamic load device vjoyd.vxd
11:52:18 7.00 INITCOMPLETE = NAVAP
11:52:25 4.28 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVEX15.VXD
11:52:29 3.11 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
11:52:32 125.89 Dynamic load success
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
11:54:38 0.28 INITCOMPLETESUCCESS = NAVAP
11:54:45 99.50 InitDone = TSRQuery (time
estimated)
11:56:25 0.83 Enumerating Standard Floppy
Disk
Controller (BIOS\*PNP0700\0B)

The two delays that stick out are, of course,
the
Norton
(Symantec) anti-virus program stuff and the
TSRQuery
items.
Any further help to hone in on those two delay
places
will
be appreciated.


-----Original Message-----
My Logitech plugs into a serial port. What I
did
to
replace with a standard mouse driver was this:
StartSettingsC. PanelSystemDevice Manager
TabMouseHi-
lite MouseDriver TabUpdate Driver buttonNext
buttonSelected Search for Better Driver...etc.
After the search, a better MS driver was found
and I
okayed its installation.

I will uninstall Logitech mouse and reboot.
Thanks for
the
explanation - sorry didn't get it the first
time!

-----Original Message-----
You say you replaced the Logitech mouse driver
with a
standard mouse driver. Do you
have a serial mouse or a PS/2 mouse? The
driver
you
added is "Standard Serial
Mouse", which is only for a serial mouse, and
you are
still loading the Logitech
driver.....Loading Vxd = LMOUSE.VXD

What I meant for you to try is to remove
(uninstall)
the
Logitech mouse (not add a
mouse manually), reboot, and let Windows add
its
own
driver on its own.

I will see what else I can find re your
delays.
A lot
of
them are from Symantec
anti-virus loading, though the 8-minute time
is
far
too
long.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George"
wrote
in
message
...
Have never used MSBackup, so uninstalled and
then
changed
file names per instruction. The tape
detection
has
been
disabled and it seems to be working okay so
far!
Here is a copy of the new Failures and
Delays
Log:

14:52:30 7.28 LoadSuccess =
C:\WINDOWS\IFSHLP.SYS
14:52:38 0.11 LoadFailed = ndis2sup.vxd
14:52:40 0.44 Loading Vxd =
C:\WINDOWS\system\VMM32
\IFSMGR.VXD
14:52:46 2.72 LoadSuccess = vnetbios.vxd
14:52:49 1.11 Loading Vxd = C:\PROGRA~1
\SYMANTEC\SYMEVNT.386
14:52:50 20.17 Loading Vxd = LMOUSE.VXD
14:53:11 0.61 Loading Vxd = dfs.vxd
14:53:24 0.06 DEVICEINITFAILED = MTRR
14:53:25 0.56 DEVICEINITSUCCESS = VTD
14:53:26 0.28 DEVICEINIT = NTKERN
14:53:33 0.78 Dynamic load device
pci.vxd
14:53:44 0.39 DEVICEINIT = IOS
14:53:46 0.50 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
14:53:48 2.33 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
14:53:53 0.78 Started Standard Serial
Mouse
(ROOT\*PNP0F0C\0000)
14:53:56 0.50 DEVICEINIT = NDIS
14:54:01 2.11 Dynamic load device
vdhcp.386
14:54:10 0.56 DEVICEINITSUCCESS = VDEF
14:54:14 2.22 INITCOMPLETE = IOS
14:54:17 10.39 INITCOMPLETESUCCESS = IOS
14:54:30 0.06 INITCOMPLETEFAILED =
SDVXD
14:54:35 0.33 Dynamic load success
C:\WINDOWS\system\serial.vxd
14:54:38 2.56 Dynamic load success
dsound.vxd
14:54:41 0.44 Dynamic load device
vjoyd.vxd
14:54:43 7.61 INITCOMPLETE = NAVAP
14:54:50 4.61 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVEX15.VXD
14:54:55 2.50 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
14:54:58 75.83 Dynamic load success
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
14:56:14 0.67 INITCOMPLETESUCCESS =
NAVAP


.

.


.



.


.




  #44  
Old September 9th 04, 12:45 AM
George
external usenet poster
 
Posts: n/a
Default

Well, it looks like my drive is bad. Here is what happened.

Went to the Western Digital site www.wdc.com. Until your
suggestion, I didn't know this free disk diagnosis service
was available. Anyway, downloaded from support.wdc.com
their lifeguard.exe into Temp Folder. It installed into
C:/DataLifeguard 9x Folder. Then I ran the program.

It first recognized my drives and offered to run a SMART
test which I then had done on the 4GB master drive (the
slave drive which was the original and holds all of
232MB). The message came back "SMART Test Passed. Would
you like to run a Quick Functional Test of your drive"?
(Recommended) Clicked Yes.

Twenty seconds later came back the result "Quick
Functional Test Failed!! Would you like to run the Quick
Restore Surface Scan? ... Note: Depending on system
performance and errors, this test may take up to an hour
to complete." Clicked Yes.

Two hours later with the scan only 13% completed, pop-up
box appeared and read "Repair has detected multiple drive
errors. It is recommended that you backup your data
immediately!!! Program aborted..."

I can't complain, seven years of trouble-free service is
beyond the call of duty for any drive. The good news is
that I still have access to the disk's data, and new units
are reasonably priced. Think around $2,000 was paid for
Dell 486 Dimension in 1993. Will probably try WinXP with
the new unit but will keep Win 98SE in reserve - it's been
an outstanding and very reliable operating system.

To both SFB and Glen, thank you once again for your
invaluable help. The best things in life are truly free.



-----Original Message-----
Okay to SFB and Glen. I will track down the Western
Digital site and see what they have to impart. Perhaps
it's been a bad disk all along - started out with a
message: "Press any key to run ScanDisk with surface
analysis on these drives...Invalid Switch: /SIMPLEUI."
Then I did a Thorough ScanDisk and Defrag which took

about
30 hours, and also did the anti-virus scans with Norton,
Spybot and Adaware. The "Invalid Switch" message went
away so thought it was probably software.

Will let you know the result of the visit to Western
Digital. Thanks for steering me along - couldn't do the
troubleshoot without you.

-----Original Message-----
Is your disk in good shape ?
Wondering if you should download the
disk diagnostic from the disk mfgr's web site and run

the
non-destructive
tests.

Might have a flakey sector or two

"George" wrote in

message
...
Hello Glen. I'm using a dial-up connection and the best
speed we get in this area is usually 28,000 bps. Not on
any type of network, just a simple home set-up on a

Dell
Precision 486 purchased the end of 1993 upgraded 1997

to
AMD K-6 chip, 96 RAM, 4GB HD - think the OS started

with
Win3.1, then Win95 and upgraded to Win 98SE.

Earlier you had me do a full system virus scan which I

did
do. Next, I was able to download Spybot and Adaware but
not CWShredder. For some reason CWShredder would not
download into my system. I ran Spybot and Adaware for
several days, then cleared them out. Adaware found

nothing
and Spybot found one item which was promptly removed.
Right now I'm operating without an anti-virus program

as
Norton Anti-Virus was uninstalled day before yesterday
since we thought it might be behind the long boot
problems. Also, I think I want to change to another

anti-
virus program. But I'm being careful and only coming to
this support.microsoft.com site when on the internet.

I have run the clean boot procedure from the Gary

Terhune
article recommended earlier. After completing

his "clean
boot" list, this is what the Bootlog Analysis Report
(Delays) looked like:

6:56:38 154.72 LoadSuccess =

C:\WINDOWS\IFSHLP.SYS
6:59:14 0.67 Loading Vxd = C:\WINDOWS\system\VMM32
\IFSMGR.VXD
6:59:15 0.28 Loading Vxd = C:\WINDOWS\system\VMM32
\IOS.VXD
6:59:19 0.72 Loading Vxd = dfs.vxd
6:59:26 0.50 DEVICEINITSUCCESS = VTD
6:59:28 0.33 Dynamic load device bios.vxd
6:59:31 0.89 Dynamic load device pci.vxd
6:59:36 0.61 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
6:59:38 3.89 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
6:59:43 0.72 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
6:59:44 0.33 DEVICEINIT = NDIS
6:59:44 4.50 Dynamic load device pppmac.vxd
6:59:50 3.22 Dynamic load device vdhcp.386
6:59:56 0.33 Initing hsflop.pdr
6:59:56 0.28 Initing esdi_506.pdr
6:59:57 0.61 Initing esdi_506.pdr
6:59:57 0.61 Init Success esdi_506.pdr
7:00:01 0.28 Dynamic load success
C:\WINDOWS\system\serial.vxd
7:00:02 2.44 Starting Wave Device for Voice Modem


(MODEMWAVE\HALFDUPLEXVOICEWAVEDEVICE\ROOT&UNIMODEM 631CD54E&
COM1)
7:00:05 1.06 Dynamic load success dsound.vxd
7:00:08 93.06 InitDone = TSRQuery (time estimated)

The above test was run yesterday morning (Tuesday 7 Sep
04), and this morning the same report showed 349

seconds
for = C:\WINDOWS\IFSHLP.SYS!! The clock-on-the-wall

time
for yesterday's report displayed above was 8 min. 55

secs.
This covers the time from when the Win 98 Menu first
appears until the full icons appear on the desktop.

Don't
understand why the time on the Bootlog Analysis Report

is
much shorter.

An icon double-clicked on the desktop then takes

another
55 secs. to pull up that selected item, but after it's
been used that first time and then closed and

reopened -
the icon/progam/item responds by opening at normal

speed
(about 5 secs). This is another symptom that has

continued
since it first slowed down about two weeks ago - seems
related.

How does one examen the time used in

C:\WINDOWS\IFHLP\SYS?
Your continued direction and advice appreciated.




-----Original Message-----
George, are you using a broadband connection or a

dial-
up
connection? Do you have a
Network card (NIC) or integrated network interface in

the
computer? Are you on any
type of network?

Also, I suggest you do a complete check for
malware/adwa

Update your anti-virus app and then run a full-system
virus scan.

Use CWShredder, the CoolWeb removal tool, available

he
http://www.majorgeeks.com/downloads31.html
http://aumha.org/downloads/cwshredder.zip
Close all browser windows and open apps, start

CWShredder
and click the Fix button.

In addition, install Ad-Aware SE free edition, start

it,
click its 'Check for
Updates' link in the app to install updates, then use

it
to scan your system, and
remove what it finds.
Ad-Awa
http://www.lavasoftusa.com/support/download/

Install, update and run SpyBot Search & Destroy, scan
your system, and then remove
the items in RED only.
SpyBot S&D:
http://www.safer-networking.org/index.php?

page=download

Install SpywareBlaster:
http://www.majorgeeks.com/download2859.html
Click the link in the app to check for and install
updates, then click to 'Enable
all protection'.
Update at least weekly.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George" wrote

in
message
...
Here are the clock-on-the-wall times for a normal

boot:

1. Win98 Startup Menu 0:00
2. Win98 Blue Sky Page 0:30
3. Black Screen ending C:\ 4:40
4. Green Screen arrow/timeglass 5:35
5. Icons appear on desktop 7:35
6. Timeglass disappears 8:15

Yesterday I ran Maintenance Wizard - the defrag took
about
8 hours. I thought it a good idea after removing

Norton
Anti-Virus - that was the only thing done on this
computer.

For comparison here is the Bootlog Analysis Delays

and
Failures Report run just before the above timed

boot:

6:56:38 154.72 LoadSuccess =

C:\WINDOWS\IFSHLP.SYS
6:59:14 0.67 Loading Vxd =

C:\WINDOWS\system\VMM32
\IFSMGR.VXD
6:59:15 0.28 Loading Vxd =

C:\WINDOWS\system\VMM32
\IOS.VXD
6:59:19 0.72 Loading Vxd = dfs.vxd
6:59:26 0.50 DEVICEINITSUCCESS = VTD
6:59:28 0.33 Dynamic load device bios.vxd
6:59:31 0.89 Dynamic load device pci.vxd
6:59:36 0.61 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
6:59:38 3.89 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
6:59:43 0.72 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
6:59:44 0.33 DEVICEINIT = NDIS
6:59:44 4.50 Dynamic load device pppmac.vxd
6:59:50 3.22 Dynamic load device vdhcp.386
6:59:56 0.33 Initing hsflop.pdr
6:59:56 0.28 Initing esdi_506.pdr
6:59:57 0.61 Initing esdi_506.pdr
6:59:57 0.61 Init Success esdi_506.pdr
7:00:01 0.28 Dynamic load success
C:\WINDOWS\system\serial.vxd
7:00:02 2.44 Starting Wave Device for Voice

Modem



(MODEMWAVE\HALFDUPLEXVOICEWAVEDEVICE\ROOT&UNIMODEM 631CD54E&
COM1)
7:00:05 1.06 Dynamic load success dsound.vxd
7:00:08 93.06 InitDone = TSRQuery (time

estimated)

I'm puzzled by the first entry taking 154.72 secs.

for
=C:\WINDOWS\IFSHLP\SYS. Also, I've taken a once-over
look
at the eight page clean boot troubleshooting

procedure
and
the article on clean boot by Gary Terhune that you
referenced. Am I ready to try those procedures?

Sorry to be so much trouble and to take so much of

your
time.



-----Original Message-----
BTW, when I say the actual boot time on the clock,

I
mean
the boot time when you are
doing a normal boot, not a logged boot.

Another suggestion that may or may not shed any

light,
is
to do a clean boot, then
while in the clean boot environment, do a logged

boot
and
see what the log show, and
also how long the boot takes in real time on the

clock.

How to Perform Clean-Boot Troubleshooting for

Windows
98
http://support.microsoft.com?kbid=192926

"CLEAN BOOT -- What it is and why you need it." by

MS
MVP
Gary Terhune
http://snipurl.com/8gam
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"glee" wrote in message
...
George, there is nothing abnormal that I can see
there....it looks like many
bootlogs I have seen. What is the actual time it
takes
right now for your
computer
to boot, from the time you see the first boot

screen
with the memory count, to the
time you first see the Desktop load up....I mean
actual
time on the clock on the
wall?
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm

"George"

wrote
in
message
...
Uninstalled the Norton Anti-Virus program and

the
only
long delays remaining (72.33 secs. total) are

for
the
many
entries which occur before TSRQuery is run.

Here
is a
copy
of the excerpted list of entries from the end

of
the
detailed Bootlog Analysis Report run after
uninstalling
Norton Anti-virus and rebooting:

12:22:26 0.06 INITCOMPLETE = VFBACKUP
12:22:26 0.00 INITCOMPLETESUCCESS =

VFBACKUP
12:22:26 0.06 INITCOMPLETE = SHELL
12:22:26 0.00 INITCOMPLETESUCCESS = SHELL
12:22:26 0.00 Initializing KERNEL (time
estimated)
12:22:26 0.00 LoadStart = system.drv (time
estimated)
12:22:26 0.00 LoadSuccess = system.drv (time
estimated)
12:22:26 0.00 LoadStart = keyboard.drv (time
estimated)
12:22:26 0.00 LoadSuccess = keyboard.drv

(time
estimated)
12:22:26 0.00 LoadStart = mouse.drv (time
estimated)
12:22:26 0.00 LoadSuccess = mouse.drv (time
estimated)
12:22:26 0.00 LoadStart = trid_pci.drv (time
estimated)
12:22:26 0.00 LoadStart = DIBENG.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = DIBENG.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = trid_pci.drv

(time
estimated)
12:22:26 0.00 LoadStart = mmsound.drv (time
estimated)
12:22:26 0.00 LoadSuccess = mmsound.drv

(time
estimated)
12:22:26 0.00 LoadStart = comm.drv (time
estimated)
12:22:26 0.00 LoadSuccess = comm.drv (time
estimated)
12:22:26 0.00 LoadStart = gdi.exe (time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\SYSTEM\GDI32.DLL
(time estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\SYSTEM\GDI32.DLL
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgasys.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgasys.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgafix.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgafix.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgaoem.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgaoem.fon
(time estimated)
12:22:26 0.00 LoadSuccess = gdi.exe (time
estimated)
12:22:26 0.00 LoadStart = user.exe (time
estimated)
12:22:26 0.00 LoadStart = DDEML.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = DDEML.DLL (time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\SYSTEM\USER32.DLL
(time estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\SYSTEM\USER32.DLL (time estimated)
12:22:26 0.00 LoadStart = COOL.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = COOL.DLL (time
estimated)
12:22:26 0.00 Init = KEYBOARD (time

estimated)
12:22:26 0.00 InitDone = KEYBOARD (time
estimated)
12:22:26 0.00 Init = Mouse (time estimated)
12:22:26 0.00 Status = Mouse driver

installed
(time
estimated)
12:22:26 0.00 InitDone = Mouse (time

estimated)
12:22:26 0.00 Init = (time estimated)
12:22:26 0.00 LoadStart = DISPLAY.drv (time
estimated)
12:22:26 0.00 LoadSuccess = DISPLAY.drv

(time
estimated)
12:22:26 0.00 InitDone = DISPLAY (time
estimated)
12:22:26 0.00 Init = Display Resources (time
estimated)
12:22:26 0.00 InitDone = Display Resources

(time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\serife.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\serife.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\sserife.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\sserife.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\coure.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\coure.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\symbole.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\symbole.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\smalle.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\smalle.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_czec.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_czec.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_engl.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_engl.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_fren.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_fren.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_germ.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_germ.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_ital.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_ital.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_span.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_span.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_swed.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_swed.fon (time estimated)
12:22:26 0.00 LoadSuccess = user.exe (time
estimated)
12:22:26 0.00 LoadStart = MSGSRV32.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = MSGSRV32.EXE

(time
estimated)
12:22:26 0.00 Init = Final USER (time

estimated)
12:22:26 0.00 InitDone = Final USER (time
estimated)
12:22:26 0.00 Init = Installable Drivers

(time
estimated)
12:22:26 0.00 InitDone = Installable Drivers
(time
estimated)
12:22:26 0.00 Init = TSRQuery (time

estimated)
12:22:26 72.33 InitDone = TSRQuery (time
estimated)
12:23:39 0.22 Enumerating Standard Floppy

Disk
Controller (BIOS\*PNP0700\0B)
12:23:39 0.00 Enumerated Standard Floppy

Disk
Controller (BIOS\*PNP0700\0B)

The questionable list of items seems to start
with "Initializing KERNEL" and ends

with "InitDone
=
TSRQuery." Do you know whether this is a normal
sequence
for the start-up or if there is a problem which
can be
corrected? Thinking of using anti-virus

software
called EZ
ARMOR LE by Computer Associates. Your further
thoughts and
advice appreciated.


-----Original Message-----
Quoting MS MVP Richard Harper:
"TSRQuery is not to blame. There are several
unlogged
actions that happen
before TSRQuery is run, so it appears to be

the
problem
even though it is
not. There's no good way to tell what's to

blame
since
the actions are not
logged."

If you didn't have the problem before and do

now,
then it
must come from some change
you made just prior to the experienced

increase in
the
boot time. Likely it is some
driver causing it. The delays due to Symantec
entries I
can't help you with, as I
do not like or use their software. Were it my
machine, I
would uninstall all the
Symantec/Norton software, and see if the boot
delay
continues.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


wrote in
message
...
Thanks Glen, the mouse load up problem is

gone.
Here is
the latest Delays and Failures Report from
Bootlog
Analyzer:

11:50:31 9.11 LoadSuccess =
C:\WINDOWS\IFSHLP.SYS
11:50:41 0.11 LoadFailed = ndis2sup.vxd
11:50:43 0.28 Loading Vxd =
C:\WINDOWS\system\VMM32
\IFSMGR.VXD
11:50:43 0.33 Loading Vxd =
C:\WINDOWS\system\VMM32
\IOS.VXD
11:50:49 3.06 LoadSuccess = vnetbios.vxd
11:50:52 2.39 Loading Vxd = C:\PROGRA~1
\SYMANTEC\SYMEVNT.386
11:50:55 0.39 Loading Vxd = dfs.vxd
11:51:09 0.06 DEVICEINITFAILED = MTRR
11:51:10 0.50 DEVICEINITSUCCESS = VTD
11:51:11 0.28 DEVICEINIT = NTKERN
11:51:13 0.39 Dynamic load device

bios.vxd
11:51:18 0.83 Dynamic load device

pci.vxd
11:51:30 0.28 DEVICEINIT = IOS
11:51:31 0.44 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
11:51:33 2.50 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
11:51:39 0.83 Started Standard Serial

Mouse
(ROOT\*PNP0F0C\0000)
11:51:41 0.61 DEVICEINIT = NDIS
11:51:46 3.89 Dynamic load device

vdhcp.386
11:51:58 0.33 Initing hsflop.pdr
11:51:58 0.44 Initing esdi_506.pdr
11:51:59 0.67 Initing esdi_506.pdr
11:51:59 0.83 Init Success esdi_506.pdr
11:52:07 0.11 INITCOMPLETEFAILED =

SDVXD
11:52:11 0.33 Dynamic load success
C:\WINDOWS\system\serial.vxd
11:52:12 0.28 Enumerated Printer Port

(LPT1)
(BIOS\*PNP0400\0C)
11:52:14 0.28 Dynamic load device
dsound.vxd
11:52:15 1.11 Dynamic load success
dsound.vxd
11:52:16 0.33 Dynamic load device

vjoyd.vxd
11:52:18 7.00 INITCOMPLETE = NAVAP
11:52:25 4.28 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVEX15.VXD
11:52:29 3.11 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
11:52:32 125.89 Dynamic load success
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
11:54:38 0.28 INITCOMPLETESUCCESS =

NAVAP
11:54:45 99.50 InitDone = TSRQuery (time
estimated)
11:56:25 0.83 Enumerating Standard

Floppy
Disk
Controller (BIOS\*PNP0700\0B)

The two delays that stick out are, of

course,
the
Norton
(Symantec) anti-virus program stuff and the
TSRQuery
items.
Any further help to hone in on those two

delay
places
will
be appreciated.


-----Original Message-----
My Logitech plugs into a serial port. What

I
did
to
replace with a standard mouse driver was

this:
StartSettingsC. PanelSystemDevice

Manager
TabMouseHi-
lite MouseDriver TabUpdate Driver

buttonNext
buttonSelected Search for Better

Driver...etc.
After the search, a better MS driver was

found
and I
okayed its installation.

I will uninstall Logitech mouse and reboot.
Thanks for
the
explanation - sorry didn't get it the first
time!

-----Original Message-----
You say you replaced the Logitech mouse

driver
with a
standard mouse driver. Do you
have a serial mouse or a PS/2 mouse? The
driver
you
added is "Standard Serial
Mouse", which is only for a serial mouse,

and
you are
still loading the Logitech
driver.....Loading Vxd = LMOUSE.VXD

What I meant for you to try is to remove
(uninstall)
the
Logitech mouse (not add a
mouse manually), reboot, and let Windows

add
its
own
driver on its own.

I will see what else I can find re your
delays.
A lot
of
them are from Symantec
anti-virus loading, though the 8-minute

time
is
far
too
long.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George"


wrote
in
message
news:5c0d01c491f8$abc3cf70

...
Have never used MSBackup, so

uninstalled
and
then
changed
file names per instruction. The tape
detection
has
been
disabled and it seems to be working

okay
so
far!
Here is a copy of the new Failures and
Delays
Log:

14:52:30 7.28 LoadSuccess =
C:\WINDOWS\IFSHLP.SYS
14:52:38 0.11 LoadFailed =

ndis2sup.vxd
14:52:40 0.44 Loading Vxd =
C:\WINDOWS\system\VMM32
\IFSMGR.VXD
14:52:46 2.72 LoadSuccess =

vnetbios.vxd
14:52:49 1.11 Loading Vxd =

C:\PROGRA~1
\SYMANTEC\SYMEVNT.386
14:52:50 20.17 Loading Vxd =

LMOUSE.VXD
14:53:11 0.61 Loading Vxd = dfs.vxd
14:53:24 0.06 DEVICEINITFAILED =

MTRR
14:53:25 0.56 DEVICEINITSUCCESS =

VTD
14:53:26 0.28 DEVICEINIT = NTKERN
14:53:33 0.78 Dynamic load device
pci.vxd
14:53:44 0.39 DEVICEINIT = IOS
14:53:46 0.50 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
14:53:48 2.33 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
14:53:53 0.78 Started Standard

Serial
Mouse
(ROOT\*PNP0F0C\0000)
14:53:56 0.50 DEVICEINIT = NDIS
14:54:01 2.11 Dynamic load device
vdhcp.386
14:54:10 0.56 DEVICEINITSUCCESS =

VDEF
14:54:14 2.22 INITCOMPLETE = IOS
14:54:17 10.39 INITCOMPLETESUCCESS =

IOS
14:54:30 0.06 INITCOMPLETEFAILED =
SDVXD
14:54:35 0.33 Dynamic load success
C:\WINDOWS\system\serial.vxd
14:54:38 2.56 Dynamic load success
dsound.vxd
14:54:41 0.44 Dynamic load device
vjoyd.vxd
14:54:43 7.61 INITCOMPLETE = NAVAP
14:54:50 4.61 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVEX15.VXD
14:54:55 2.50 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVENG.VXD
14:54:58 75.83 Dynamic load success
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVENG.VXD
14:56:14 0.67 INITCOMPLETESUCCESS =
NAVAP


.

.


.



.


.


.

.

  #45  
Old September 9th 04, 12:45 AM posted to microsoft.public.win98.performance
George[_2_]
external usenet poster
 
Posts: 11
Default Interpretation of failures and delays at boot.

Well, it looks like my drive is bad. Here is what happened.

Went to the Western Digital site www.wdc.com. Until your
suggestion, I didn't know this free disk diagnosis service
was available. Anyway, downloaded from support.wdc.com
their lifeguard.exe into Temp Folder. It installed into
C:/DataLifeguard 9x Folder. Then I ran the program.

It first recognized my drives and offered to run a SMART
test which I then had done on the 4GB master drive (the
slave drive which was the original and holds all of
232MB). The message came back "SMART Test Passed. Would
you like to run a Quick Functional Test of your drive"?
(Recommended) Clicked Yes.

Twenty seconds later came back the result "Quick
Functional Test Failed!! Would you like to run the Quick
Restore Surface Scan? ... Note: Depending on system
performance and errors, this test may take up to an hour
to complete." Clicked Yes.

Two hours later with the scan only 13% completed, pop-up
box appeared and read "Repair has detected multiple drive
errors. It is recommended that you backup your data
immediately!!! Program aborted..."

I can't complain, seven years of trouble-free service is
beyond the call of duty for any drive. The good news is
that I still have access to the disk's data, and new units
are reasonably priced. Think around $2,000 was paid for
Dell 486 Dimension in 1993. Will probably try WinXP with
the new unit but will keep Win 98SE in reserve - it's been
an outstanding and very reliable operating system.

To both SFB and Glen, thank you once again for your
invaluable help. The best things in life are truly free.



-----Original Message-----
Okay to SFB and Glen. I will track down the Western
Digital site and see what they have to impart. Perhaps
it's been a bad disk all along - started out with a
message: "Press any key to run ScanDisk with surface
analysis on these drives...Invalid Switch: /SIMPLEUI."
Then I did a Thorough ScanDisk and Defrag which took

about
30 hours, and also did the anti-virus scans with Norton,
Spybot and Adaware. The "Invalid Switch" message went
away so thought it was probably software.

Will let you know the result of the visit to Western
Digital. Thanks for steering me along - couldn't do the
troubleshoot without you.

-----Original Message-----
Is your disk in good shape ?
Wondering if you should download the
disk diagnostic from the disk mfgr's web site and run

the
non-destructive
tests.

Might have a flakey sector or two

"George" wrote in

message
...
Hello Glen. I'm using a dial-up connection and the best
speed we get in this area is usually 28,000 bps. Not on
any type of network, just a simple home set-up on a

Dell
Precision 486 purchased the end of 1993 upgraded 1997

to
AMD K-6 chip, 96 RAM, 4GB HD - think the OS started

with
Win3.1, then Win95 and upgraded to Win 98SE.

Earlier you had me do a full system virus scan which I

did
do. Next, I was able to download Spybot and Adaware but
not CWShredder. For some reason CWShredder would not
download into my system. I ran Spybot and Adaware for
several days, then cleared them out. Adaware found

nothing
and Spybot found one item which was promptly removed.
Right now I'm operating without an anti-virus program

as
Norton Anti-Virus was uninstalled day before yesterday
since we thought it might be behind the long boot
problems. Also, I think I want to change to another

anti-
virus program. But I'm being careful and only coming to
this support.microsoft.com site when on the internet.

I have run the clean boot procedure from the Gary

Terhune
article recommended earlier. After completing

his "clean
boot" list, this is what the Bootlog Analysis Report
(Delays) looked like:

6:56:38 154.72 LoadSuccess =

C:\WINDOWS\IFSHLP.SYS
6:59:14 0.67 Loading Vxd = C:\WINDOWS\system\VMM32
\IFSMGR.VXD
6:59:15 0.28 Loading Vxd = C:\WINDOWS\system\VMM32
\IOS.VXD
6:59:19 0.72 Loading Vxd = dfs.vxd
6:59:26 0.50 DEVICEINITSUCCESS = VTD
6:59:28 0.33 Dynamic load device bios.vxd
6:59:31 0.89 Dynamic load device pci.vxd
6:59:36 0.61 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
6:59:38 3.89 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
6:59:43 0.72 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
6:59:44 0.33 DEVICEINIT = NDIS
6:59:44 4.50 Dynamic load device pppmac.vxd
6:59:50 3.22 Dynamic load device vdhcp.386
6:59:56 0.33 Initing hsflop.pdr
6:59:56 0.28 Initing esdi_506.pdr
6:59:57 0.61 Initing esdi_506.pdr
6:59:57 0.61 Init Success esdi_506.pdr
7:00:01 0.28 Dynamic load success
C:\WINDOWS\system\serial.vxd
7:00:02 2.44 Starting Wave Device for Voice Modem


(MODEMWAVE\HALFDUPLEXVOICEWAVEDEVICE\ROOT&UNIMODEM 631CD54E&
COM1)
7:00:05 1.06 Dynamic load success dsound.vxd
7:00:08 93.06 InitDone = TSRQuery (time estimated)

The above test was run yesterday morning (Tuesday 7 Sep
04), and this morning the same report showed 349

seconds
for = C:\WINDOWS\IFSHLP.SYS!! The clock-on-the-wall

time
for yesterday's report displayed above was 8 min. 55

secs.
This covers the time from when the Win 98 Menu first
appears until the full icons appear on the desktop.

Don't
understand why the time on the Bootlog Analysis Report

is
much shorter.

An icon double-clicked on the desktop then takes

another
55 secs. to pull up that selected item, but after it's
been used that first time and then closed and

reopened -
the icon/progam/item responds by opening at normal

speed
(about 5 secs). This is another symptom that has

continued
since it first slowed down about two weeks ago - seems
related.

How does one examen the time used in

C:\WINDOWS\IFHLP\SYS?
Your continued direction and advice appreciated.




-----Original Message-----
George, are you using a broadband connection or a

dial-
up
connection? Do you have a
Network card (NIC) or integrated network interface in

the
computer? Are you on any
type of network?

Also, I suggest you do a complete check for
malware/adwa

Update your anti-virus app and then run a full-system
virus scan.

Use CWShredder, the CoolWeb removal tool, available

he
http://www.majorgeeks.com/downloads31.html
http://aumha.org/downloads/cwshredder.zip
Close all browser windows and open apps, start

CWShredder
and click the Fix button.

In addition, install Ad-Aware SE free edition, start

it,
click its 'Check for
Updates' link in the app to install updates, then use

it
to scan your system, and
remove what it finds.
Ad-Awa
http://www.lavasoftusa.com/support/download/

Install, update and run SpyBot Search & Destroy, scan
your system, and then remove
the items in RED only.
SpyBot S&D:
http://www.safer-networking.org/index.php?

page=download

Install SpywareBlaster:
http://www.majorgeeks.com/download2859.html
Click the link in the app to check for and install
updates, then click to 'Enable
all protection'.
Update at least weekly.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George" wrote

in
message
...
Here are the clock-on-the-wall times for a normal

boot:

1. Win98 Startup Menu 0:00
2. Win98 Blue Sky Page 0:30
3. Black Screen ending C:\ 4:40
4. Green Screen arrow/timeglass 5:35
5. Icons appear on desktop 7:35
6. Timeglass disappears 8:15

Yesterday I ran Maintenance Wizard - the defrag took
about
8 hours. I thought it a good idea after removing

Norton
Anti-Virus - that was the only thing done on this
computer.

For comparison here is the Bootlog Analysis Delays

and
Failures Report run just before the above timed

boot:

6:56:38 154.72 LoadSuccess =

C:\WINDOWS\IFSHLP.SYS
6:59:14 0.67 Loading Vxd =

C:\WINDOWS\system\VMM32
\IFSMGR.VXD
6:59:15 0.28 Loading Vxd =

C:\WINDOWS\system\VMM32
\IOS.VXD
6:59:19 0.72 Loading Vxd = dfs.vxd
6:59:26 0.50 DEVICEINITSUCCESS = VTD
6:59:28 0.33 Dynamic load device bios.vxd
6:59:31 0.89 Dynamic load device pci.vxd
6:59:36 0.61 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
6:59:38 3.89 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
6:59:43 0.72 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
6:59:44 0.33 DEVICEINIT = NDIS
6:59:44 4.50 Dynamic load device pppmac.vxd
6:59:50 3.22 Dynamic load device vdhcp.386
6:59:56 0.33 Initing hsflop.pdr
6:59:56 0.28 Initing esdi_506.pdr
6:59:57 0.61 Initing esdi_506.pdr
6:59:57 0.61 Init Success esdi_506.pdr
7:00:01 0.28 Dynamic load success
C:\WINDOWS\system\serial.vxd
7:00:02 2.44 Starting Wave Device for Voice

Modem



(MODEMWAVE\HALFDUPLEXVOICEWAVEDEVICE\ROOT&UNIMODEM 631CD54E&
COM1)
7:00:05 1.06 Dynamic load success dsound.vxd
7:00:08 93.06 InitDone = TSRQuery (time

estimated)

I'm puzzled by the first entry taking 154.72 secs.

for
=C:\WINDOWS\IFSHLP\SYS. Also, I've taken a once-over
look
at the eight page clean boot troubleshooting

procedure
and
the article on clean boot by Gary Terhune that you
referenced. Am I ready to try those procedures?

Sorry to be so much trouble and to take so much of

your
time.



-----Original Message-----
BTW, when I say the actual boot time on the clock,

I
mean
the boot time when you are
doing a normal boot, not a logged boot.

Another suggestion that may or may not shed any

light,
is
to do a clean boot, then
while in the clean boot environment, do a logged

boot
and
see what the log show, and
also how long the boot takes in real time on the

clock.

How to Perform Clean-Boot Troubleshooting for

Windows
98
http://support.microsoft.com?kbid=192926

"CLEAN BOOT -- What it is and why you need it." by

MS
MVP
Gary Terhune
http://snipurl.com/8gam
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"glee" wrote in message
...
George, there is nothing abnormal that I can see
there....it looks like many
bootlogs I have seen. What is the actual time it
takes
right now for your
computer
to boot, from the time you see the first boot

screen
with the memory count, to the
time you first see the Desktop load up....I mean
actual
time on the clock on the
wall?
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm

"George"

wrote
in
message
...
Uninstalled the Norton Anti-Virus program and

the
only
long delays remaining (72.33 secs. total) are

for
the
many
entries which occur before TSRQuery is run.

Here
is a
copy
of the excerpted list of entries from the end

of
the
detailed Bootlog Analysis Report run after
uninstalling
Norton Anti-virus and rebooting:

12:22:26 0.06 INITCOMPLETE = VFBACKUP
12:22:26 0.00 INITCOMPLETESUCCESS =

VFBACKUP
12:22:26 0.06 INITCOMPLETE = SHELL
12:22:26 0.00 INITCOMPLETESUCCESS = SHELL
12:22:26 0.00 Initializing KERNEL (time
estimated)
12:22:26 0.00 LoadStart = system.drv (time
estimated)
12:22:26 0.00 LoadSuccess = system.drv (time
estimated)
12:22:26 0.00 LoadStart = keyboard.drv (time
estimated)
12:22:26 0.00 LoadSuccess = keyboard.drv

(time
estimated)
12:22:26 0.00 LoadStart = mouse.drv (time
estimated)
12:22:26 0.00 LoadSuccess = mouse.drv (time
estimated)
12:22:26 0.00 LoadStart = trid_pci.drv (time
estimated)
12:22:26 0.00 LoadStart = DIBENG.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = DIBENG.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = trid_pci.drv

(time
estimated)
12:22:26 0.00 LoadStart = mmsound.drv (time
estimated)
12:22:26 0.00 LoadSuccess = mmsound.drv

(time
estimated)
12:22:26 0.00 LoadStart = comm.drv (time
estimated)
12:22:26 0.00 LoadSuccess = comm.drv (time
estimated)
12:22:26 0.00 LoadStart = gdi.exe (time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\SYSTEM\GDI32.DLL
(time estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\SYSTEM\GDI32.DLL
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgasys.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgasys.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgafix.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgafix.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgaoem.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgaoem.fon
(time estimated)
12:22:26 0.00 LoadSuccess = gdi.exe (time
estimated)
12:22:26 0.00 LoadStart = user.exe (time
estimated)
12:22:26 0.00 LoadStart = DDEML.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = DDEML.DLL (time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\SYSTEM\USER32.DLL
(time estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\SYSTEM\USER32.DLL (time estimated)
12:22:26 0.00 LoadStart = COOL.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = COOL.DLL (time
estimated)
12:22:26 0.00 Init = KEYBOARD (time

estimated)
12:22:26 0.00 InitDone = KEYBOARD (time
estimated)
12:22:26 0.00 Init = Mouse (time estimated)
12:22:26 0.00 Status = Mouse driver

installed
(time
estimated)
12:22:26 0.00 InitDone = Mouse (time

estimated)
12:22:26 0.00 Init = (time estimated)
12:22:26 0.00 LoadStart = DISPLAY.drv (time
estimated)
12:22:26 0.00 LoadSuccess = DISPLAY.drv

(time
estimated)
12:22:26 0.00 InitDone = DISPLAY (time
estimated)
12:22:26 0.00 Init = Display Resources (time
estimated)
12:22:26 0.00 InitDone = Display Resources

(time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\serife.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\serife.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\sserife.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\sserife.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\coure.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\coure.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\symbole.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\symbole.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\smalle.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\smalle.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_czec.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_czec.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_engl.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_engl.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_fren.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_fren.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_germ.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_germ.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_ital.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_ital.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_span.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_span.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_swed.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_swed.fon (time estimated)
12:22:26 0.00 LoadSuccess = user.exe (time
estimated)
12:22:26 0.00 LoadStart = MSGSRV32.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = MSGSRV32.EXE

(time
estimated)
12:22:26 0.00 Init = Final USER (time

estimated)
12:22:26 0.00 InitDone = Final USER (time
estimated)
12:22:26 0.00 Init = Installable Drivers

(time
estimated)
12:22:26 0.00 InitDone = Installable Drivers
(time
estimated)
12:22:26 0.00 Init = TSRQuery (time

estimated)
12:22:26 72.33 InitDone = TSRQuery (time
estimated)
12:23:39 0.22 Enumerating Standard Floppy

Disk
Controller (BIOS\*PNP0700\0B)
12:23:39 0.00 Enumerated Standard Floppy

Disk
Controller (BIOS\*PNP0700\0B)

The questionable list of items seems to start
with "Initializing KERNEL" and ends

with "InitDone
=
TSRQuery." Do you know whether this is a normal
sequence
for the start-up or if there is a problem which
can be
corrected? Thinking of using anti-virus

software
called EZ
ARMOR LE by Computer Associates. Your further
thoughts and
advice appreciated.


-----Original Message-----
Quoting MS MVP Richard Harper:
"TSRQuery is not to blame. There are several
unlogged
actions that happen
before TSRQuery is run, so it appears to be

the
problem
even though it is
not. There's no good way to tell what's to

blame
since
the actions are not
logged."

If you didn't have the problem before and do

now,
then it
must come from some change
you made just prior to the experienced

increase in
the
boot time. Likely it is some
driver causing it. The delays due to Symantec
entries I
can't help you with, as I
do not like or use their software. Were it my
machine, I
would uninstall all the
Symantec/Norton software, and see if the boot
delay
continues.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


wrote in
message
...
Thanks Glen, the mouse load up problem is

gone.
Here is
the latest Delays and Failures Report from
Bootlog
Analyzer:

11:50:31 9.11 LoadSuccess =
C:\WINDOWS\IFSHLP.SYS
11:50:41 0.11 LoadFailed = ndis2sup.vxd
11:50:43 0.28 Loading Vxd =
C:\WINDOWS\system\VMM32
\IFSMGR.VXD
11:50:43 0.33 Loading Vxd =
C:\WINDOWS\system\VMM32
\IOS.VXD
11:50:49 3.06 LoadSuccess = vnetbios.vxd
11:50:52 2.39 Loading Vxd = C:\PROGRA~1
\SYMANTEC\SYMEVNT.386
11:50:55 0.39 Loading Vxd = dfs.vxd
11:51:09 0.06 DEVICEINITFAILED = MTRR
11:51:10 0.50 DEVICEINITSUCCESS = VTD
11:51:11 0.28 DEVICEINIT = NTKERN
11:51:13 0.39 Dynamic load device

bios.vxd
11:51:18 0.83 Dynamic load device

pci.vxd
11:51:30 0.28 DEVICEINIT = IOS
11:51:31 0.44 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
11:51:33 2.50 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
11:51:39 0.83 Started Standard Serial

Mouse
(ROOT\*PNP0F0C\0000)
11:51:41 0.61 DEVICEINIT = NDIS
11:51:46 3.89 Dynamic load device

vdhcp.386
11:51:58 0.33 Initing hsflop.pdr
11:51:58 0.44 Initing esdi_506.pdr
11:51:59 0.67 Initing esdi_506.pdr
11:51:59 0.83 Init Success esdi_506.pdr
11:52:07 0.11 INITCOMPLETEFAILED =

SDVXD
11:52:11 0.33 Dynamic load success
C:\WINDOWS\system\serial.vxd
11:52:12 0.28 Enumerated Printer Port

(LPT1)
(BIOS\*PNP0400\0C)
11:52:14 0.28 Dynamic load device
dsound.vxd
11:52:15 1.11 Dynamic load success
dsound.vxd
11:52:16 0.33 Dynamic load device

vjoyd.vxd
11:52:18 7.00 INITCOMPLETE = NAVAP
11:52:25 4.28 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVEX15.VXD
11:52:29 3.11 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
11:52:32 125.89 Dynamic load success
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
11:54:38 0.28 INITCOMPLETESUCCESS =

NAVAP
11:54:45 99.50 InitDone = TSRQuery (time
estimated)
11:56:25 0.83 Enumerating Standard

Floppy
Disk
Controller (BIOS\*PNP0700\0B)

The two delays that stick out are, of

course,
the
Norton
(Symantec) anti-virus program stuff and the
TSRQuery
items.
Any further help to hone in on those two

delay
places
will
be appreciated.


-----Original Message-----
My Logitech plugs into a serial port. What

I
did
to
replace with a standard mouse driver was

this:
StartSettingsC. PanelSystemDevice

Manager
TabMouseHi-
lite MouseDriver TabUpdate Driver

buttonNext
buttonSelected Search for Better

Driver...etc.
After the search, a better MS driver was

found
and I
okayed its installation.

I will uninstall Logitech mouse and reboot.
Thanks for
the
explanation - sorry didn't get it the first
time!

-----Original Message-----
You say you replaced the Logitech mouse

driver
with a
standard mouse driver. Do you
have a serial mouse or a PS/2 mouse? The
driver
you
added is "Standard Serial
Mouse", which is only for a serial mouse,

and
you are
still loading the Logitech
driver.....Loading Vxd = LMOUSE.VXD

What I meant for you to try is to remove
(uninstall)
the
Logitech mouse (not add a
mouse manually), reboot, and let Windows

add
its
own
driver on its own.

I will see what else I can find re your
delays.
A lot
of
them are from Symantec
anti-virus loading, though the 8-minute

time
is
far
too
long.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George"


wrote
in
message
news:5c0d01c491f8$abc3cf70

...
Have never used MSBackup, so

uninstalled
and
then
changed
file names per instruction. The tape
detection
has
been
disabled and it seems to be working

okay
so
far!
Here is a copy of the new Failures and
Delays
Log:

14:52:30 7.28 LoadSuccess =
C:\WINDOWS\IFSHLP.SYS
14:52:38 0.11 LoadFailed =

ndis2sup.vxd
14:52:40 0.44 Loading Vxd =
C:\WINDOWS\system\VMM32
\IFSMGR.VXD
14:52:46 2.72 LoadSuccess =

vnetbios.vxd
14:52:49 1.11 Loading Vxd =

C:\PROGRA~1
\SYMANTEC\SYMEVNT.386
14:52:50 20.17 Loading Vxd =

LMOUSE.VXD
14:53:11 0.61 Loading Vxd = dfs.vxd
14:53:24 0.06 DEVICEINITFAILED =

MTRR
14:53:25 0.56 DEVICEINITSUCCESS =

VTD
14:53:26 0.28 DEVICEINIT = NTKERN
14:53:33 0.78 Dynamic load device
pci.vxd
14:53:44 0.39 DEVICEINIT = IOS
14:53:46 0.50 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
14:53:48 2.33 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
14:53:53 0.78 Started Standard

Serial
Mouse
(ROOT\*PNP0F0C\0000)
14:53:56 0.50 DEVICEINIT = NDIS
14:54:01 2.11 Dynamic load device
vdhcp.386
14:54:10 0.56 DEVICEINITSUCCESS =

VDEF
14:54:14 2.22 INITCOMPLETE = IOS
14:54:17 10.39 INITCOMPLETESUCCESS =

IOS
14:54:30 0.06 INITCOMPLETEFAILED =
SDVXD
14:54:35 0.33 Dynamic load success
C:\WINDOWS\system\serial.vxd
14:54:38 2.56 Dynamic load success
dsound.vxd
14:54:41 0.44 Dynamic load device
vjoyd.vxd
14:54:43 7.61 INITCOMPLETE = NAVAP
14:54:50 4.61 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVEX15.VXD
14:54:55 2.50 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVENG.VXD
14:54:58 75.83 Dynamic load success
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVENG.VXD
14:56:14 0.67 INITCOMPLETESUCCESS =
NAVAP


.

.


.



.


.


.

.

  #46  
Old September 9th 04, 02:01 AM
glee
external usenet poster
 
Posts: n/a
Default

Glad you found the cause.
Interestingly, it finally dawned on me that it could very well be the drive failing,
at about the same time that SFB mentioned it, and also about the same time that
another MVP suggested to me that the drive could be the problem when I ran it by
him. When you finally mentioned the age of the computer, that really increased the
likelihood of a hardware problem.

As for your plans to install Windows XP after replacing the hard drive, your 96MB
RAM is not going to be anywhere near enough, even if your processor is within
acceptable limits.

Good luck.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George" wrote in message
...
Well, it looks like my drive is bad. Here is what happened.

Went to the Western Digital site www.wdc.com. Until your
suggestion, I didn't know this free disk diagnosis service
was available. Anyway, downloaded from support.wdc.com
their lifeguard.exe into Temp Folder. It installed into
C:/DataLifeguard 9x Folder. Then I ran the program.

It first recognized my drives and offered to run a SMART
test which I then had done on the 4GB master drive (the
slave drive which was the original and holds all of
232MB). The message came back "SMART Test Passed. Would
you like to run a Quick Functional Test of your drive"?
(Recommended) Clicked Yes.

Twenty seconds later came back the result "Quick
Functional Test Failed!! Would you like to run the Quick
Restore Surface Scan? ... Note: Depending on system
performance and errors, this test may take up to an hour
to complete." Clicked Yes.

Two hours later with the scan only 13% completed, pop-up
box appeared and read "Repair has detected multiple drive
errors. It is recommended that you backup your data
immediately!!! Program aborted..."

I can't complain, seven years of trouble-free service is
beyond the call of duty for any drive. The good news is
that I still have access to the disk's data, and new units
are reasonably priced. Think around $2,000 was paid for
Dell 486 Dimension in 1993. Will probably try WinXP with
the new unit but will keep Win 98SE in reserve - it's been
an outstanding and very reliable operating system.

To both SFB and Glen, thank you once again for your
invaluable help. The best things in life are truly free.



-----Original Message-----
Okay to SFB and Glen. I will track down the Western
Digital site and see what they have to impart. Perhaps
it's been a bad disk all along - started out with a
message: "Press any key to run ScanDisk with surface
analysis on these drives...Invalid Switch: /SIMPLEUI."
Then I did a Thorough ScanDisk and Defrag which took

about
30 hours, and also did the anti-virus scans with Norton,
Spybot and Adaware. The "Invalid Switch" message went
away so thought it was probably software.

Will let you know the result of the visit to Western
Digital. Thanks for steering me along - couldn't do the
troubleshoot without you.

-----Original Message-----
Is your disk in good shape ?
Wondering if you should download the
disk diagnostic from the disk mfgr's web site and run

the
non-destructive
tests.

Might have a flakey sector or two

"George" wrote in

message
...
Hello Glen. I'm using a dial-up connection and the best
speed we get in this area is usually 28,000 bps. Not on
any type of network, just a simple home set-up on a

Dell
Precision 486 purchased the end of 1993 upgraded 1997

to
AMD K-6 chip, 96 RAM, 4GB HD - think the OS started

with
Win3.1, then Win95 and upgraded to Win 98SE.

Earlier you had me do a full system virus scan which I

did
do. Next, I was able to download Spybot and Adaware but
not CWShredder. For some reason CWShredder would not
download into my system. I ran Spybot and Adaware for
several days, then cleared them out. Adaware found

nothing
and Spybot found one item which was promptly removed.
Right now I'm operating without an anti-virus program

as
Norton Anti-Virus was uninstalled day before yesterday
since we thought it might be behind the long boot
problems. Also, I think I want to change to another

anti-
virus program. But I'm being careful and only coming to
this support.microsoft.com site when on the internet.

I have run the clean boot procedure from the Gary

Terhune
article recommended earlier. After completing

his "clean
boot" list, this is what the Bootlog Analysis Report
(Delays) looked like:

6:56:38 154.72 LoadSuccess =

C:\WINDOWS\IFSHLP.SYS
6:59:14 0.67 Loading Vxd = C:\WINDOWS\system\VMM32
\IFSMGR.VXD
6:59:15 0.28 Loading Vxd = C:\WINDOWS\system\VMM32
\IOS.VXD
6:59:19 0.72 Loading Vxd = dfs.vxd
6:59:26 0.50 DEVICEINITSUCCESS = VTD
6:59:28 0.33 Dynamic load device bios.vxd
6:59:31 0.89 Dynamic load device pci.vxd
6:59:36 0.61 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
6:59:38 3.89 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
6:59:43 0.72 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
6:59:44 0.33 DEVICEINIT = NDIS
6:59:44 4.50 Dynamic load device pppmac.vxd
6:59:50 3.22 Dynamic load device vdhcp.386
6:59:56 0.33 Initing hsflop.pdr
6:59:56 0.28 Initing esdi_506.pdr
6:59:57 0.61 Initing esdi_506.pdr
6:59:57 0.61 Init Success esdi_506.pdr
7:00:01 0.28 Dynamic load success
C:\WINDOWS\system\serial.vxd
7:00:02 2.44 Starting Wave Device for Voice Modem


(MODEMWAVE\HALFDUPLEXVOICEWAVEDEVICE\ROOT&UNIMODEM 631CD54E&
COM1)
7:00:05 1.06 Dynamic load success dsound.vxd
7:00:08 93.06 InitDone = TSRQuery (time estimated)

The above test was run yesterday morning (Tuesday 7 Sep
04), and this morning the same report showed 349

seconds
for = C:\WINDOWS\IFSHLP.SYS!! The clock-on-the-wall

time
for yesterday's report displayed above was 8 min. 55

secs.
This covers the time from when the Win 98 Menu first
appears until the full icons appear on the desktop.

Don't
understand why the time on the Bootlog Analysis Report

is
much shorter.

An icon double-clicked on the desktop then takes

another
55 secs. to pull up that selected item, but after it's
been used that first time and then closed and

reopened -
the icon/progam/item responds by opening at normal

speed
(about 5 secs). This is another symptom that has

continued
since it first slowed down about two weeks ago - seems
related.

How does one examen the time used in

C:\WINDOWS\IFHLP\SYS?
Your continued direction and advice appreciated.




-----Original Message-----
George, are you using a broadband connection or a

dial-
up
connection? Do you have a
Network card (NIC) or integrated network interface in

the
computer? Are you on any
type of network?

Also, I suggest you do a complete check for
malware/adwa

Update your anti-virus app and then run a full-system
virus scan.

Use CWShredder, the CoolWeb removal tool, available

he
http://www.majorgeeks.com/downloads31.html
http://aumha.org/downloads/cwshredder.zip
Close all browser windows and open apps, start

CWShredder
and click the Fix button.

In addition, install Ad-Aware SE free edition, start

it,
click its 'Check for
Updates' link in the app to install updates, then use

it
to scan your system, and
remove what it finds.
Ad-Awa
http://www.lavasoftusa.com/support/download/

Install, update and run SpyBot Search & Destroy, scan
your system, and then remove
the items in RED only.
SpyBot S&D:
http://www.safer-networking.org/index.php?

page=download

Install SpywareBlaster:
http://www.majorgeeks.com/download2859.html
Click the link in the app to check for and install
updates, then click to 'Enable
all protection'.
Update at least weekly.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George" wrote

in
message
...
Here are the clock-on-the-wall times for a normal

boot:

1. Win98 Startup Menu 0:00
2. Win98 Blue Sky Page 0:30
3. Black Screen ending C:\ 4:40
4. Green Screen arrow/timeglass 5:35
5. Icons appear on desktop 7:35
6. Timeglass disappears 8:15

Yesterday I ran Maintenance Wizard - the defrag took
about
8 hours. I thought it a good idea after removing

Norton
Anti-Virus - that was the only thing done on this
computer.

For comparison here is the Bootlog Analysis Delays

and
Failures Report run just before the above timed

boot:

6:56:38 154.72 LoadSuccess =

C:\WINDOWS\IFSHLP.SYS
6:59:14 0.67 Loading Vxd =

C:\WINDOWS\system\VMM32
\IFSMGR.VXD
6:59:15 0.28 Loading Vxd =

C:\WINDOWS\system\VMM32
\IOS.VXD
6:59:19 0.72 Loading Vxd = dfs.vxd
6:59:26 0.50 DEVICEINITSUCCESS = VTD
6:59:28 0.33 Dynamic load device bios.vxd
6:59:31 0.89 Dynamic load device pci.vxd
6:59:36 0.61 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
6:59:38 3.89 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
6:59:43 0.72 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
6:59:44 0.33 DEVICEINIT = NDIS
6:59:44 4.50 Dynamic load device pppmac.vxd
6:59:50 3.22 Dynamic load device vdhcp.386
6:59:56 0.33 Initing hsflop.pdr
6:59:56 0.28 Initing esdi_506.pdr
6:59:57 0.61 Initing esdi_506.pdr
6:59:57 0.61 Init Success esdi_506.pdr
7:00:01 0.28 Dynamic load success
C:\WINDOWS\system\serial.vxd
7:00:02 2.44 Starting Wave Device for Voice

Modem



(MODEMWAVE\HALFDUPLEXVOICEWAVEDEVICE\ROOT&UNIMODEM 631CD54E&
COM1)
7:00:05 1.06 Dynamic load success dsound.vxd
7:00:08 93.06 InitDone = TSRQuery (time

estimated)

I'm puzzled by the first entry taking 154.72 secs.

for
=C:\WINDOWS\IFSHLP\SYS. Also, I've taken a once-over
look
at the eight page clean boot troubleshooting

procedure
and
the article on clean boot by Gary Terhune that you
referenced. Am I ready to try those procedures?

Sorry to be so much trouble and to take so much of

your
time.



-----Original Message-----
BTW, when I say the actual boot time on the clock,

I
mean
the boot time when you are
doing a normal boot, not a logged boot.

Another suggestion that may or may not shed any

light,
is
to do a clean boot, then
while in the clean boot environment, do a logged

boot
and
see what the log show, and
also how long the boot takes in real time on the

clock.

How to Perform Clean-Boot Troubleshooting for

Windows
98
http://support.microsoft.com?kbid=192926

"CLEAN BOOT -- What it is and why you need it." by

MS
MVP
Gary Terhune
http://snipurl.com/8gam
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"glee" wrote in message
...
George, there is nothing abnormal that I can see
there....it looks like many
bootlogs I have seen. What is the actual time it
takes
right now for your
computer
to boot, from the time you see the first boot

screen
with the memory count, to the
time you first see the Desktop load up....I mean
actual
time on the clock on the
wall?
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm

"George"

wrote
in
message
...
Uninstalled the Norton Anti-Virus program and

the
only
long delays remaining (72.33 secs. total) are

for
the
many
entries which occur before TSRQuery is run.

Here
is a
copy
of the excerpted list of entries from the end

of
the
detailed Bootlog Analysis Report run after
uninstalling
Norton Anti-virus and rebooting:

12:22:26 0.06 INITCOMPLETE = VFBACKUP
12:22:26 0.00 INITCOMPLETESUCCESS =

VFBACKUP
12:22:26 0.06 INITCOMPLETE = SHELL
12:22:26 0.00 INITCOMPLETESUCCESS = SHELL
12:22:26 0.00 Initializing KERNEL (time
estimated)
12:22:26 0.00 LoadStart = system.drv (time
estimated)
12:22:26 0.00 LoadSuccess = system.drv (time
estimated)
12:22:26 0.00 LoadStart = keyboard.drv (time
estimated)
12:22:26 0.00 LoadSuccess = keyboard.drv

(time
estimated)
12:22:26 0.00 LoadStart = mouse.drv (time
estimated)
12:22:26 0.00 LoadSuccess = mouse.drv (time
estimated)
12:22:26 0.00 LoadStart = trid_pci.drv (time
estimated)
12:22:26 0.00 LoadStart = DIBENG.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = DIBENG.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = trid_pci.drv

(time
estimated)
12:22:26 0.00 LoadStart = mmsound.drv (time
estimated)
12:22:26 0.00 LoadSuccess = mmsound.drv

(time
estimated)
12:22:26 0.00 LoadStart = comm.drv (time
estimated)
12:22:26 0.00 LoadSuccess = comm.drv (time
estimated)
12:22:26 0.00 LoadStart = gdi.exe (time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\SYSTEM\GDI32.DLL
(time estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\SYSTEM\GDI32.DLL
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgasys.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgasys.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgafix.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgafix.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgaoem.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgaoem.fon
(time estimated)
12:22:26 0.00 LoadSuccess = gdi.exe (time
estimated)
12:22:26 0.00 LoadStart = user.exe (time
estimated)
12:22:26 0.00 LoadStart = DDEML.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = DDEML.DLL (time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\SYSTEM\USER32.DLL
(time estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\SYSTEM\USER32.DLL (time estimated)
12:22:26 0.00 LoadStart = COOL.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = COOL.DLL (time
estimated)
12:22:26 0.00 Init = KEYBOARD (time

estimated)
12:22:26 0.00 InitDone = KEYBOARD (time
estimated)
12:22:26 0.00 Init = Mouse (time estimated)
12:22:26 0.00 Status = Mouse driver

installed
(time
estimated)
12:22:26 0.00 InitDone = Mouse (time

estimated)
12:22:26 0.00 Init = (time estimated)
12:22:26 0.00 LoadStart = DISPLAY.drv (time
estimated)
12:22:26 0.00 LoadSuccess = DISPLAY.drv

(time
estimated)
12:22:26 0.00 InitDone = DISPLAY (time
estimated)
12:22:26 0.00 Init = Display Resources (time
estimated)
12:22:26 0.00 InitDone = Display Resources

(time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\serife.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\serife.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\sserife.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\sserife.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\coure.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\coure.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\symbole.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\symbole.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\smalle.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\smalle.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_czec.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_czec.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_engl.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_engl.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_fren.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_fren.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_germ.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_germ.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_ital.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_ital.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_span.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_span.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_swed.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_swed.fon (time estimated)
12:22:26 0.00 LoadSuccess = user.exe (time
estimated)
12:22:26 0.00 LoadStart = MSGSRV32.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = MSGSRV32.EXE

(time
estimated)
12:22:26 0.00 Init = Final USER (time

estimated)
12:22:26 0.00 InitDone = Final USER (time
estimated)
12:22:26 0.00 Init = Installable Drivers

(time
estimated)
12:22:26 0.00 InitDone = Installable Drivers
(time
estimated)
12:22:26 0.00 Init = TSRQuery (time

estimated)
12:22:26 72.33 InitDone = TSRQuery (time
estimated)
12:23:39 0.22 Enumerating Standard Floppy

Disk
Controller (BIOS\*PNP0700\0B)
12:23:39 0.00 Enumerated Standard Floppy

Disk
Controller (BIOS\*PNP0700\0B)

The questionable list of items seems to start
with "Initializing KERNEL" and ends

with "InitDone
=
TSRQuery." Do you know whether this is a normal
sequence
for the start-up or if there is a problem which
can be
corrected? Thinking of using anti-virus

software
called EZ
ARMOR LE by Computer Associates. Your further
thoughts and
advice appreciated.


-----Original Message-----
Quoting MS MVP Richard Harper:
"TSRQuery is not to blame. There are several
unlogged
actions that happen
before TSRQuery is run, so it appears to be

the
problem
even though it is
not. There's no good way to tell what's to

blame
since
the actions are not
logged."

If you didn't have the problem before and do

now,
then it
must come from some change
you made just prior to the experienced

increase in
the
boot time. Likely it is some
driver causing it. The delays due to Symantec
entries I
can't help you with, as I
do not like or use their software. Were it my
machine, I
would uninstall all the
Symantec/Norton software, and see if the boot
delay
continues.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


wrote in
message
...
Thanks Glen, the mouse load up problem is

gone.
Here is
the latest Delays and Failures Report from
Bootlog
Analyzer:

11:50:31 9.11 LoadSuccess =
C:\WINDOWS\IFSHLP.SYS
11:50:41 0.11 LoadFailed = ndis2sup.vxd
11:50:43 0.28 Loading Vxd =
C:\WINDOWS\system\VMM32
\IFSMGR.VXD
11:50:43 0.33 Loading Vxd =
C:\WINDOWS\system\VMM32
\IOS.VXD
11:50:49 3.06 LoadSuccess = vnetbios.vxd
11:50:52 2.39 Loading Vxd = C:\PROGRA~1
\SYMANTEC\SYMEVNT.386
11:50:55 0.39 Loading Vxd = dfs.vxd
11:51:09 0.06 DEVICEINITFAILED = MTRR
11:51:10 0.50 DEVICEINITSUCCESS = VTD
11:51:11 0.28 DEVICEINIT = NTKERN
11:51:13 0.39 Dynamic load device

bios.vxd
11:51:18 0.83 Dynamic load device

pci.vxd
11:51:30 0.28 DEVICEINIT = IOS
11:51:31 0.44 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
11:51:33 2.50 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
11:51:39 0.83 Started Standard Serial

Mouse
(ROOT\*PNP0F0C\0000)
11:51:41 0.61 DEVICEINIT = NDIS
11:51:46 3.89 Dynamic load device

vdhcp.386
11:51:58 0.33 Initing hsflop.pdr
11:51:58 0.44 Initing esdi_506.pdr
11:51:59 0.67 Initing esdi_506.pdr
11:51:59 0.83 Init Success esdi_506.pdr
11:52:07 0.11 INITCOMPLETEFAILED =

SDVXD
11:52:11 0.33 Dynamic load success
C:\WINDOWS\system\serial.vxd
11:52:12 0.28 Enumerated Printer Port

(LPT1)
(BIOS\*PNP0400\0C)
11:52:14 0.28 Dynamic load device
dsound.vxd
11:52:15 1.11 Dynamic load success
dsound.vxd
11:52:16 0.33 Dynamic load device

vjoyd.vxd
11:52:18 7.00 INITCOMPLETE = NAVAP
11:52:25 4.28 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVEX15.VXD
11:52:29 3.11 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
11:52:32 125.89 Dynamic load success
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
11:54:38 0.28 INITCOMPLETESUCCESS =

NAVAP
11:54:45 99.50 InitDone = TSRQuery (time
estimated)
11:56:25 0.83 Enumerating Standard

Floppy
Disk
Controller (BIOS\*PNP0700\0B)

The two delays that stick out are, of

course,
the
Norton
(Symantec) anti-virus program stuff and the
TSRQuery
items.
Any further help to hone in on those two

delay
places
will
be appreciated.


-----Original Message-----
My Logitech plugs into a serial port. What

I
did
to
replace with a standard mouse driver was

this:
StartSettingsC. PanelSystemDevice

Manager
TabMouseHi-
lite MouseDriver TabUpdate Driver

buttonNext
buttonSelected Search for Better

Driver...etc.
After the search, a better MS driver was

found
and I
okayed its installation.

I will uninstall Logitech mouse and reboot.
Thanks for
the
explanation - sorry didn't get it the first
time!

-----Original Message-----
You say you replaced the Logitech mouse

driver
with a
standard mouse driver. Do you
have a serial mouse or a PS/2 mouse? The
driver
you
added is "Standard Serial
Mouse", which is only for a serial mouse,

and
you are
still loading the Logitech
driver.....Loading Vxd = LMOUSE.VXD

What I meant for you to try is to remove
(uninstall)
the
Logitech mouse (not add a
mouse manually), reboot, and let Windows

add
its
own
driver on its own.

I will see what else I can find re your
delays.
A lot
of
them are from Symantec
anti-virus loading, though the 8-minute

time
is
far
too
long.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George"


wrote
in
message
news:5c0d01c491f8$abc3cf70

...
Have never used MSBackup, so

uninstalled
and
then
changed
file names per instruction. The tape
detection
has
been
disabled and it seems to be working

okay
so
far!
Here is a copy of the new Failures and
Delays
Log:

14:52:30 7.28 LoadSuccess =
C:\WINDOWS\IFSHLP.SYS
14:52:38 0.11 LoadFailed =

ndis2sup.vxd
14:52:40 0.44 Loading Vxd =
C:\WINDOWS\system\VMM32
\IFSMGR.VXD
14:52:46 2.72 LoadSuccess =

vnetbios.vxd
14:52:49 1.11 Loading Vxd =

C:\PROGRA~1
\SYMANTEC\SYMEVNT.386
14:52:50 20.17 Loading Vxd =

LMOUSE.VXD
14:53:11 0.61 Loading Vxd = dfs.vxd
14:53:24 0.06 DEVICEINITFAILED =

MTRR
14:53:25 0.56 DEVICEINITSUCCESS =

VTD
14:53:26 0.28 DEVICEINIT = NTKERN
14:53:33 0.78 Dynamic load device
pci.vxd
14:53:44 0.39 DEVICEINIT = IOS
14:53:46 0.50 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
14:53:48 2.33 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
14:53:53 0.78 Started Standard

Serial
Mouse
(ROOT\*PNP0F0C\0000)
14:53:56 0.50 DEVICEINIT = NDIS
14:54:01 2.11 Dynamic load device
vdhcp.386
14:54:10 0.56 DEVICEINITSUCCESS =

VDEF
14:54:14 2.22 INITCOMPLETE = IOS
14:54:17 10.39 INITCOMPLETESUCCESS =

IOS
14:54:30 0.06 INITCOMPLETEFAILED =
SDVXD
14:54:35 0.33 Dynamic load success
C:\WINDOWS\system\serial.vxd
14:54:38 2.56 Dynamic load success
dsound.vxd
14:54:41 0.44 Dynamic load device
vjoyd.vxd
14:54:43 7.61 INITCOMPLETE = NAVAP
14:54:50 4.61 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVEX15.VXD
14:54:55 2.50 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVENG.VXD
14:54:58 75.83 Dynamic load success
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVENG.VXD
14:56:14 0.67 INITCOMPLETESUCCESS =
NAVAP


.

.


.



.


.


.

.


  #47  
Old September 9th 04, 02:01 AM posted to microsoft.public.win98.performance
glee
External Usenet User
 
Posts: 2,458
Default Interpretation of failures and delays at boot.

Glad you found the cause.
Interestingly, it finally dawned on me that it could very well be the drive failing,
at about the same time that SFB mentioned it, and also about the same time that
another MVP suggested to me that the drive could be the problem when I ran it by
him. When you finally mentioned the age of the computer, that really increased the
likelihood of a hardware problem.

As for your plans to install Windows XP after replacing the hard drive, your 96MB
RAM is not going to be anywhere near enough, even if your processor is within
acceptable limits.

Good luck.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George" wrote in message
...
Well, it looks like my drive is bad. Here is what happened.

Went to the Western Digital site www.wdc.com. Until your
suggestion, I didn't know this free disk diagnosis service
was available. Anyway, downloaded from support.wdc.com
their lifeguard.exe into Temp Folder. It installed into
C:/DataLifeguard 9x Folder. Then I ran the program.

It first recognized my drives and offered to run a SMART
test which I then had done on the 4GB master drive (the
slave drive which was the original and holds all of
232MB). The message came back "SMART Test Passed. Would
you like to run a Quick Functional Test of your drive"?
(Recommended) Clicked Yes.

Twenty seconds later came back the result "Quick
Functional Test Failed!! Would you like to run the Quick
Restore Surface Scan? ... Note: Depending on system
performance and errors, this test may take up to an hour
to complete." Clicked Yes.

Two hours later with the scan only 13% completed, pop-up
box appeared and read "Repair has detected multiple drive
errors. It is recommended that you backup your data
immediately!!! Program aborted..."

I can't complain, seven years of trouble-free service is
beyond the call of duty for any drive. The good news is
that I still have access to the disk's data, and new units
are reasonably priced. Think around $2,000 was paid for
Dell 486 Dimension in 1993. Will probably try WinXP with
the new unit but will keep Win 98SE in reserve - it's been
an outstanding and very reliable operating system.

To both SFB and Glen, thank you once again for your
invaluable help. The best things in life are truly free.



-----Original Message-----
Okay to SFB and Glen. I will track down the Western
Digital site and see what they have to impart. Perhaps
it's been a bad disk all along - started out with a
message: "Press any key to run ScanDisk with surface
analysis on these drives...Invalid Switch: /SIMPLEUI."
Then I did a Thorough ScanDisk and Defrag which took

about
30 hours, and also did the anti-virus scans with Norton,
Spybot and Adaware. The "Invalid Switch" message went
away so thought it was probably software.

Will let you know the result of the visit to Western
Digital. Thanks for steering me along - couldn't do the
troubleshoot without you.

-----Original Message-----
Is your disk in good shape ?
Wondering if you should download the
disk diagnostic from the disk mfgr's web site and run

the
non-destructive
tests.

Might have a flakey sector or two

"George" wrote in

message
...
Hello Glen. I'm using a dial-up connection and the best
speed we get in this area is usually 28,000 bps. Not on
any type of network, just a simple home set-up on a

Dell
Precision 486 purchased the end of 1993 upgraded 1997

to
AMD K-6 chip, 96 RAM, 4GB HD - think the OS started

with
Win3.1, then Win95 and upgraded to Win 98SE.

Earlier you had me do a full system virus scan which I

did
do. Next, I was able to download Spybot and Adaware but
not CWShredder. For some reason CWShredder would not
download into my system. I ran Spybot and Adaware for
several days, then cleared them out. Adaware found

nothing
and Spybot found one item which was promptly removed.
Right now I'm operating without an anti-virus program

as
Norton Anti-Virus was uninstalled day before yesterday
since we thought it might be behind the long boot
problems. Also, I think I want to change to another

anti-
virus program. But I'm being careful and only coming to
this support.microsoft.com site when on the internet.

I have run the clean boot procedure from the Gary

Terhune
article recommended earlier. After completing

his "clean
boot" list, this is what the Bootlog Analysis Report
(Delays) looked like:

6:56:38 154.72 LoadSuccess =

C:\WINDOWS\IFSHLP.SYS
6:59:14 0.67 Loading Vxd = C:\WINDOWS\system\VMM32
\IFSMGR.VXD
6:59:15 0.28 Loading Vxd = C:\WINDOWS\system\VMM32
\IOS.VXD
6:59:19 0.72 Loading Vxd = dfs.vxd
6:59:26 0.50 DEVICEINITSUCCESS = VTD
6:59:28 0.33 Dynamic load device bios.vxd
6:59:31 0.89 Dynamic load device pci.vxd
6:59:36 0.61 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
6:59:38 3.89 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
6:59:43 0.72 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
6:59:44 0.33 DEVICEINIT = NDIS
6:59:44 4.50 Dynamic load device pppmac.vxd
6:59:50 3.22 Dynamic load device vdhcp.386
6:59:56 0.33 Initing hsflop.pdr
6:59:56 0.28 Initing esdi_506.pdr
6:59:57 0.61 Initing esdi_506.pdr
6:59:57 0.61 Init Success esdi_506.pdr
7:00:01 0.28 Dynamic load success
C:\WINDOWS\system\serial.vxd
7:00:02 2.44 Starting Wave Device for Voice Modem


(MODEMWAVE\HALFDUPLEXVOICEWAVEDEVICE\ROOT&UNIMODEM 631CD54E&
COM1)
7:00:05 1.06 Dynamic load success dsound.vxd
7:00:08 93.06 InitDone = TSRQuery (time estimated)

The above test was run yesterday morning (Tuesday 7 Sep
04), and this morning the same report showed 349

seconds
for = C:\WINDOWS\IFSHLP.SYS!! The clock-on-the-wall

time
for yesterday's report displayed above was 8 min. 55

secs.
This covers the time from when the Win 98 Menu first
appears until the full icons appear on the desktop.

Don't
understand why the time on the Bootlog Analysis Report

is
much shorter.

An icon double-clicked on the desktop then takes

another
55 secs. to pull up that selected item, but after it's
been used that first time and then closed and

reopened -
the icon/progam/item responds by opening at normal

speed
(about 5 secs). This is another symptom that has

continued
since it first slowed down about two weeks ago - seems
related.

How does one examen the time used in

C:\WINDOWS\IFHLP\SYS?
Your continued direction and advice appreciated.




-----Original Message-----
George, are you using a broadband connection or a

dial-
up
connection? Do you have a
Network card (NIC) or integrated network interface in

the
computer? Are you on any
type of network?

Also, I suggest you do a complete check for
malware/adwa

Update your anti-virus app and then run a full-system
virus scan.

Use CWShredder, the CoolWeb removal tool, available

he
http://www.majorgeeks.com/downloads31.html
http://aumha.org/downloads/cwshredder.zip
Close all browser windows and open apps, start

CWShredder
and click the Fix button.

In addition, install Ad-Aware SE free edition, start

it,
click its 'Check for
Updates' link in the app to install updates, then use

it
to scan your system, and
remove what it finds.
Ad-Awa
http://www.lavasoftusa.com/support/download/

Install, update and run SpyBot Search & Destroy, scan
your system, and then remove
the items in RED only.
SpyBot S&D:
http://www.safer-networking.org/index.php?

page=download

Install SpywareBlaster:
http://www.majorgeeks.com/download2859.html
Click the link in the app to check for and install
updates, then click to 'Enable
all protection'.
Update at least weekly.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George" wrote

in
message
...
Here are the clock-on-the-wall times for a normal

boot:

1. Win98 Startup Menu 0:00
2. Win98 Blue Sky Page 0:30
3. Black Screen ending C:\ 4:40
4. Green Screen arrow/timeglass 5:35
5. Icons appear on desktop 7:35
6. Timeglass disappears 8:15

Yesterday I ran Maintenance Wizard - the defrag took
about
8 hours. I thought it a good idea after removing

Norton
Anti-Virus - that was the only thing done on this
computer.

For comparison here is the Bootlog Analysis Delays

and
Failures Report run just before the above timed

boot:

6:56:38 154.72 LoadSuccess =

C:\WINDOWS\IFSHLP.SYS
6:59:14 0.67 Loading Vxd =

C:\WINDOWS\system\VMM32
\IFSMGR.VXD
6:59:15 0.28 Loading Vxd =

C:\WINDOWS\system\VMM32
\IOS.VXD
6:59:19 0.72 Loading Vxd = dfs.vxd
6:59:26 0.50 DEVICEINITSUCCESS = VTD
6:59:28 0.33 Dynamic load device bios.vxd
6:59:31 0.89 Dynamic load device pci.vxd
6:59:36 0.61 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
6:59:38 3.89 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
6:59:43 0.72 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
6:59:44 0.33 DEVICEINIT = NDIS
6:59:44 4.50 Dynamic load device pppmac.vxd
6:59:50 3.22 Dynamic load device vdhcp.386
6:59:56 0.33 Initing hsflop.pdr
6:59:56 0.28 Initing esdi_506.pdr
6:59:57 0.61 Initing esdi_506.pdr
6:59:57 0.61 Init Success esdi_506.pdr
7:00:01 0.28 Dynamic load success
C:\WINDOWS\system\serial.vxd
7:00:02 2.44 Starting Wave Device for Voice

Modem



(MODEMWAVE\HALFDUPLEXVOICEWAVEDEVICE\ROOT&UNIMODEM 631CD54E&
COM1)
7:00:05 1.06 Dynamic load success dsound.vxd
7:00:08 93.06 InitDone = TSRQuery (time

estimated)

I'm puzzled by the first entry taking 154.72 secs.

for
=C:\WINDOWS\IFSHLP\SYS. Also, I've taken a once-over
look
at the eight page clean boot troubleshooting

procedure
and
the article on clean boot by Gary Terhune that you
referenced. Am I ready to try those procedures?

Sorry to be so much trouble and to take so much of

your
time.



-----Original Message-----
BTW, when I say the actual boot time on the clock,

I
mean
the boot time when you are
doing a normal boot, not a logged boot.

Another suggestion that may or may not shed any

light,
is
to do a clean boot, then
while in the clean boot environment, do a logged

boot
and
see what the log show, and
also how long the boot takes in real time on the

clock.

How to Perform Clean-Boot Troubleshooting for

Windows
98
http://support.microsoft.com?kbid=192926

"CLEAN BOOT -- What it is and why you need it." by

MS
MVP
Gary Terhune
http://snipurl.com/8gam
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"glee" wrote in message
...
George, there is nothing abnormal that I can see
there....it looks like many
bootlogs I have seen. What is the actual time it
takes
right now for your
computer
to boot, from the time you see the first boot

screen
with the memory count, to the
time you first see the Desktop load up....I mean
actual
time on the clock on the
wall?
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm

"George"

wrote
in
message
...
Uninstalled the Norton Anti-Virus program and

the
only
long delays remaining (72.33 secs. total) are

for
the
many
entries which occur before TSRQuery is run.

Here
is a
copy
of the excerpted list of entries from the end

of
the
detailed Bootlog Analysis Report run after
uninstalling
Norton Anti-virus and rebooting:

12:22:26 0.06 INITCOMPLETE = VFBACKUP
12:22:26 0.00 INITCOMPLETESUCCESS =

VFBACKUP
12:22:26 0.06 INITCOMPLETE = SHELL
12:22:26 0.00 INITCOMPLETESUCCESS = SHELL
12:22:26 0.00 Initializing KERNEL (time
estimated)
12:22:26 0.00 LoadStart = system.drv (time
estimated)
12:22:26 0.00 LoadSuccess = system.drv (time
estimated)
12:22:26 0.00 LoadStart = keyboard.drv (time
estimated)
12:22:26 0.00 LoadSuccess = keyboard.drv

(time
estimated)
12:22:26 0.00 LoadStart = mouse.drv (time
estimated)
12:22:26 0.00 LoadSuccess = mouse.drv (time
estimated)
12:22:26 0.00 LoadStart = trid_pci.drv (time
estimated)
12:22:26 0.00 LoadStart = DIBENG.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = DIBENG.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = trid_pci.drv

(time
estimated)
12:22:26 0.00 LoadStart = mmsound.drv (time
estimated)
12:22:26 0.00 LoadSuccess = mmsound.drv

(time
estimated)
12:22:26 0.00 LoadStart = comm.drv (time
estimated)
12:22:26 0.00 LoadSuccess = comm.drv (time
estimated)
12:22:26 0.00 LoadStart = gdi.exe (time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\SYSTEM\GDI32.DLL
(time estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\SYSTEM\GDI32.DLL
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgasys.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgasys.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgafix.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgafix.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgaoem.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgaoem.fon
(time estimated)
12:22:26 0.00 LoadSuccess = gdi.exe (time
estimated)
12:22:26 0.00 LoadStart = user.exe (time
estimated)
12:22:26 0.00 LoadStart = DDEML.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = DDEML.DLL (time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\SYSTEM\USER32.DLL
(time estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\SYSTEM\USER32.DLL (time estimated)
12:22:26 0.00 LoadStart = COOL.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = COOL.DLL (time
estimated)
12:22:26 0.00 Init = KEYBOARD (time

estimated)
12:22:26 0.00 InitDone = KEYBOARD (time
estimated)
12:22:26 0.00 Init = Mouse (time estimated)
12:22:26 0.00 Status = Mouse driver

installed
(time
estimated)
12:22:26 0.00 InitDone = Mouse (time

estimated)
12:22:26 0.00 Init = (time estimated)
12:22:26 0.00 LoadStart = DISPLAY.drv (time
estimated)
12:22:26 0.00 LoadSuccess = DISPLAY.drv

(time
estimated)
12:22:26 0.00 InitDone = DISPLAY (time
estimated)
12:22:26 0.00 Init = Display Resources (time
estimated)
12:22:26 0.00 InitDone = Display Resources

(time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\serife.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\serife.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\sserife.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\sserife.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\coure.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\coure.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\symbole.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\symbole.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\smalle.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\smalle.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_czec.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_czec.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_engl.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_engl.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_fren.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_fren.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_germ.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_germ.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_ital.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_ital.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_span.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_span.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_swed.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_swed.fon (time estimated)
12:22:26 0.00 LoadSuccess = user.exe (time
estimated)
12:22:26 0.00 LoadStart = MSGSRV32.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = MSGSRV32.EXE

(time
estimated)
12:22:26 0.00 Init = Final USER (time

estimated)
12:22:26 0.00 InitDone = Final USER (time
estimated)
12:22:26 0.00 Init = Installable Drivers

(time
estimated)
12:22:26 0.00 InitDone = Installable Drivers
(time
estimated)
12:22:26 0.00 Init = TSRQuery (time

estimated)
12:22:26 72.33 InitDone = TSRQuery (time
estimated)
12:23:39 0.22 Enumerating Standard Floppy

Disk
Controller (BIOS\*PNP0700\0B)
12:23:39 0.00 Enumerated Standard Floppy

Disk
Controller (BIOS\*PNP0700\0B)

The questionable list of items seems to start
with "Initializing KERNEL" and ends

with "InitDone
=
TSRQuery." Do you know whether this is a normal
sequence
for the start-up or if there is a problem which
can be
corrected? Thinking of using anti-virus

software
called EZ
ARMOR LE by Computer Associates. Your further
thoughts and
advice appreciated.


-----Original Message-----
Quoting MS MVP Richard Harper:
"TSRQuery is not to blame. There are several
unlogged
actions that happen
before TSRQuery is run, so it appears to be

the
problem
even though it is
not. There's no good way to tell what's to

blame
since
the actions are not
logged."

If you didn't have the problem before and do

now,
then it
must come from some change
you made just prior to the experienced

increase in
the
boot time. Likely it is some
driver causing it. The delays due to Symantec
entries I
can't help you with, as I
do not like or use their software. Were it my
machine, I
would uninstall all the
Symantec/Norton software, and see if the boot
delay
continues.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


wrote in
message
...
Thanks Glen, the mouse load up problem is

gone.
Here is
the latest Delays and Failures Report from
Bootlog
Analyzer:

11:50:31 9.11 LoadSuccess =
C:\WINDOWS\IFSHLP.SYS
11:50:41 0.11 LoadFailed = ndis2sup.vxd
11:50:43 0.28 Loading Vxd =
C:\WINDOWS\system\VMM32
\IFSMGR.VXD
11:50:43 0.33 Loading Vxd =
C:\WINDOWS\system\VMM32
\IOS.VXD
11:50:49 3.06 LoadSuccess = vnetbios.vxd
11:50:52 2.39 Loading Vxd = C:\PROGRA~1
\SYMANTEC\SYMEVNT.386
11:50:55 0.39 Loading Vxd = dfs.vxd
11:51:09 0.06 DEVICEINITFAILED = MTRR
11:51:10 0.50 DEVICEINITSUCCESS = VTD
11:51:11 0.28 DEVICEINIT = NTKERN
11:51:13 0.39 Dynamic load device

bios.vxd
11:51:18 0.83 Dynamic load device

pci.vxd
11:51:30 0.28 DEVICEINIT = IOS
11:51:31 0.44 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
11:51:33 2.50 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
11:51:39 0.83 Started Standard Serial

Mouse
(ROOT\*PNP0F0C\0000)
11:51:41 0.61 DEVICEINIT = NDIS
11:51:46 3.89 Dynamic load device

vdhcp.386
11:51:58 0.33 Initing hsflop.pdr
11:51:58 0.44 Initing esdi_506.pdr
11:51:59 0.67 Initing esdi_506.pdr
11:51:59 0.83 Init Success esdi_506.pdr
11:52:07 0.11 INITCOMPLETEFAILED =

SDVXD
11:52:11 0.33 Dynamic load success
C:\WINDOWS\system\serial.vxd
11:52:12 0.28 Enumerated Printer Port

(LPT1)
(BIOS\*PNP0400\0C)
11:52:14 0.28 Dynamic load device
dsound.vxd
11:52:15 1.11 Dynamic load success
dsound.vxd
11:52:16 0.33 Dynamic load device

vjoyd.vxd
11:52:18 7.00 INITCOMPLETE = NAVAP
11:52:25 4.28 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVEX15.VXD
11:52:29 3.11 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
11:52:32 125.89 Dynamic load success
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
11:54:38 0.28 INITCOMPLETESUCCESS =

NAVAP
11:54:45 99.50 InitDone = TSRQuery (time
estimated)
11:56:25 0.83 Enumerating Standard

Floppy
Disk
Controller (BIOS\*PNP0700\0B)

The two delays that stick out are, of

course,
the
Norton
(Symantec) anti-virus program stuff and the
TSRQuery
items.
Any further help to hone in on those two

delay
places
will
be appreciated.


-----Original Message-----
My Logitech plugs into a serial port. What

I
did
to
replace with a standard mouse driver was

this:
StartSettingsC. PanelSystemDevice

Manager
TabMouseHi-
lite MouseDriver TabUpdate Driver

buttonNext
buttonSelected Search for Better

Driver...etc.
After the search, a better MS driver was

found
and I
okayed its installation.

I will uninstall Logitech mouse and reboot.
Thanks for
the
explanation - sorry didn't get it the first
time!

-----Original Message-----
You say you replaced the Logitech mouse

driver
with a
standard mouse driver. Do you
have a serial mouse or a PS/2 mouse? The
driver
you
added is "Standard Serial
Mouse", which is only for a serial mouse,

and
you are
still loading the Logitech
driver.....Loading Vxd = LMOUSE.VXD

What I meant for you to try is to remove
(uninstall)
the
Logitech mouse (not add a
mouse manually), reboot, and let Windows

add
its
own
driver on its own.

I will see what else I can find re your
delays.
A lot
of
them are from Symantec
anti-virus loading, though the 8-minute

time
is
far
too
long.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George"


wrote
in
message
news:5c0d01c491f8$abc3cf70

...
Have never used MSBackup, so

uninstalled
and
then
changed
file names per instruction. The tape
detection
has
been
disabled and it seems to be working

okay
so
far!
Here is a copy of the new Failures and
Delays
Log:

14:52:30 7.28 LoadSuccess =
C:\WINDOWS\IFSHLP.SYS
14:52:38 0.11 LoadFailed =

ndis2sup.vxd
14:52:40 0.44 Loading Vxd =
C:\WINDOWS\system\VMM32
\IFSMGR.VXD
14:52:46 2.72 LoadSuccess =

vnetbios.vxd
14:52:49 1.11 Loading Vxd =

C:\PROGRA~1
\SYMANTEC\SYMEVNT.386
14:52:50 20.17 Loading Vxd =

LMOUSE.VXD
14:53:11 0.61 Loading Vxd = dfs.vxd
14:53:24 0.06 DEVICEINITFAILED =

MTRR
14:53:25 0.56 DEVICEINITSUCCESS =

VTD
14:53:26 0.28 DEVICEINIT = NTKERN
14:53:33 0.78 Dynamic load device
pci.vxd
14:53:44 0.39 DEVICEINIT = IOS
14:53:46 0.50 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
14:53:48 2.33 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
14:53:53 0.78 Started Standard

Serial
Mouse
(ROOT\*PNP0F0C\0000)
14:53:56 0.50 DEVICEINIT = NDIS
14:54:01 2.11 Dynamic load device
vdhcp.386
14:54:10 0.56 DEVICEINITSUCCESS =

VDEF
14:54:14 2.22 INITCOMPLETE = IOS
14:54:17 10.39 INITCOMPLETESUCCESS =

IOS
14:54:30 0.06 INITCOMPLETEFAILED =
SDVXD
14:54:35 0.33 Dynamic load success
C:\WINDOWS\system\serial.vxd
14:54:38 2.56 Dynamic load success
dsound.vxd
14:54:41 0.44 Dynamic load device
vjoyd.vxd
14:54:43 7.61 INITCOMPLETE = NAVAP
14:54:50 4.61 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVEX15.VXD
14:54:55 2.50 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVENG.VXD
14:54:58 75.83 Dynamic load success
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVENG.VXD
14:56:14 0.67 INITCOMPLETESUCCESS =
NAVAP


.

.


.



.


.


.

.


  #48  
Old September 9th 04, 03:35 AM
Ron Badour
external usenet poster
 
Posts: n/a
Default

Your hardware is inadequate for XP and I do not think you will be happy with
the performance.
MS recommends 128 mb of ram and I personally recommend 256 mb or more. You
might want to ask for recommendations in an XP newsgroup.
--
Regards

Ron Badour, MS MVP for W98
Tips: http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo

"George" wrote in message
...
Well, it looks like my drive is bad. Here is what happened.

Went to the Western Digital site www.wdc.com. Until your
suggestion, I didn't know this free disk diagnosis service
was available. Anyway, downloaded from support.wdc.com
their lifeguard.exe into Temp Folder. It installed into
C:/DataLifeguard 9x Folder. Then I ran the program.

It first recognized my drives and offered to run a SMART
test which I then had done on the 4GB master drive (the
slave drive which was the original and holds all of
232MB). The message came back "SMART Test Passed. Would
you like to run a Quick Functional Test of your drive"?
(Recommended) Clicked Yes.

Twenty seconds later came back the result "Quick
Functional Test Failed!! Would you like to run the Quick
Restore Surface Scan? ... Note: Depending on system
performance and errors, this test may take up to an hour
to complete." Clicked Yes.

Two hours later with the scan only 13% completed, pop-up
box appeared and read "Repair has detected multiple drive
errors. It is recommended that you backup your data
immediately!!! Program aborted..."

I can't complain, seven years of trouble-free service is
beyond the call of duty for any drive. The good news is
that I still have access to the disk's data, and new units
are reasonably priced. Think around $2,000 was paid for
Dell 486 Dimension in 1993. Will probably try WinXP with
the new unit but will keep Win 98SE in reserve - it's been
an outstanding and very reliable operating system.

To both SFB and Glen, thank you once again for your
invaluable help. The best things in life are truly free.



-----Original Message-----
Okay to SFB and Glen. I will track down the Western
Digital site and see what they have to impart. Perhaps
it's been a bad disk all along - started out with a
message: "Press any key to run ScanDisk with surface
analysis on these drives...Invalid Switch: /SIMPLEUI."
Then I did a Thorough ScanDisk and Defrag which took

about
30 hours, and also did the anti-virus scans with Norton,
Spybot and Adaware. The "Invalid Switch" message went
away so thought it was probably software.

Will let you know the result of the visit to Western
Digital. Thanks for steering me along - couldn't do the
troubleshoot without you.

-----Original Message-----
Is your disk in good shape ?
Wondering if you should download the
disk diagnostic from the disk mfgr's web site and run

the
non-destructive
tests.

Might have a flakey sector or two

"George" wrote in

message
...
Hello Glen. I'm using a dial-up connection and the best
speed we get in this area is usually 28,000 bps. Not on
any type of network, just a simple home set-up on a

Dell
Precision 486 purchased the end of 1993 upgraded 1997

to
AMD K-6 chip, 96 RAM, 4GB HD - think the OS started

with
Win3.1, then Win95 and upgraded to Win 98SE.

Earlier you had me do a full system virus scan which I

did
do. Next, I was able to download Spybot and Adaware but
not CWShredder. For some reason CWShredder would not
download into my system. I ran Spybot and Adaware for
several days, then cleared them out. Adaware found

nothing
and Spybot found one item which was promptly removed.
Right now I'm operating without an anti-virus program

as
Norton Anti-Virus was uninstalled day before yesterday
since we thought it might be behind the long boot
problems. Also, I think I want to change to another

anti-
virus program. But I'm being careful and only coming to
this support.microsoft.com site when on the internet.

I have run the clean boot procedure from the Gary

Terhune
article recommended earlier. After completing

his "clean
boot" list, this is what the Bootlog Analysis Report
(Delays) looked like:

6:56:38 154.72 LoadSuccess =

C:\WINDOWS\IFSHLP.SYS
6:59:14 0.67 Loading Vxd = C:\WINDOWS\system\VMM32
\IFSMGR.VXD
6:59:15 0.28 Loading Vxd = C:\WINDOWS\system\VMM32
\IOS.VXD
6:59:19 0.72 Loading Vxd = dfs.vxd
6:59:26 0.50 DEVICEINITSUCCESS = VTD
6:59:28 0.33 Dynamic load device bios.vxd
6:59:31 0.89 Dynamic load device pci.vxd
6:59:36 0.61 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
6:59:38 3.89 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
6:59:43 0.72 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
6:59:44 0.33 DEVICEINIT = NDIS
6:59:44 4.50 Dynamic load device pppmac.vxd
6:59:50 3.22 Dynamic load device vdhcp.386
6:59:56 0.33 Initing hsflop.pdr
6:59:56 0.28 Initing esdi_506.pdr
6:59:57 0.61 Initing esdi_506.pdr
6:59:57 0.61 Init Success esdi_506.pdr
7:00:01 0.28 Dynamic load success
C:\WINDOWS\system\serial.vxd
7:00:02 2.44 Starting Wave Device for Voice Modem


(MODEMWAVE\HALFDUPLEXVOICEWAVEDEVICE\ROOT&UNIMODEM 631CD54E&
COM1)
7:00:05 1.06 Dynamic load success dsound.vxd
7:00:08 93.06 InitDone = TSRQuery (time estimated)

The above test was run yesterday morning (Tuesday 7 Sep
04), and this morning the same report showed 349

seconds
for = C:\WINDOWS\IFSHLP.SYS!! The clock-on-the-wall

time
for yesterday's report displayed above was 8 min. 55

secs.
This covers the time from when the Win 98 Menu first
appears until the full icons appear on the desktop.

Don't
understand why the time on the Bootlog Analysis Report

is
much shorter.

An icon double-clicked on the desktop then takes

another
55 secs. to pull up that selected item, but after it's
been used that first time and then closed and

reopened -
the icon/progam/item responds by opening at normal

speed
(about 5 secs). This is another symptom that has

continued
since it first slowed down about two weeks ago - seems
related.

How does one examen the time used in

C:\WINDOWS\IFHLP\SYS?
Your continued direction and advice appreciated.




-----Original Message-----
George, are you using a broadband connection or a

dial-
up
connection? Do you have a
Network card (NIC) or integrated network interface in

the
computer? Are you on any
type of network?

Also, I suggest you do a complete check for
malware/adwa

Update your anti-virus app and then run a full-system
virus scan.

Use CWShredder, the CoolWeb removal tool, available

he
http://www.majorgeeks.com/downloads31.html
http://aumha.org/downloads/cwshredder.zip
Close all browser windows and open apps, start

CWShredder
and click the Fix button.

In addition, install Ad-Aware SE free edition, start

it,
click its 'Check for
Updates' link in the app to install updates, then use

it
to scan your system, and
remove what it finds.
Ad-Awa
http://www.lavasoftusa.com/support/download/

Install, update and run SpyBot Search & Destroy, scan
your system, and then remove
the items in RED only.
SpyBot S&D:
http://www.safer-networking.org/index.php?

page=download

Install SpywareBlaster:
http://www.majorgeeks.com/download2859.html
Click the link in the app to check for and install
updates, then click to 'Enable
all protection'.
Update at least weekly.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George" wrote

in
message
...
Here are the clock-on-the-wall times for a normal

boot:

1. Win98 Startup Menu 0:00
2. Win98 Blue Sky Page 0:30
3. Black Screen ending C:\ 4:40
4. Green Screen arrow/timeglass 5:35
5. Icons appear on desktop 7:35
6. Timeglass disappears 8:15

Yesterday I ran Maintenance Wizard - the defrag took
about
8 hours. I thought it a good idea after removing

Norton
Anti-Virus - that was the only thing done on this
computer.

For comparison here is the Bootlog Analysis Delays

and
Failures Report run just before the above timed

boot:

6:56:38 154.72 LoadSuccess =

C:\WINDOWS\IFSHLP.SYS
6:59:14 0.67 Loading Vxd =

C:\WINDOWS\system\VMM32
\IFSMGR.VXD
6:59:15 0.28 Loading Vxd =

C:\WINDOWS\system\VMM32
\IOS.VXD
6:59:19 0.72 Loading Vxd = dfs.vxd
6:59:26 0.50 DEVICEINITSUCCESS = VTD
6:59:28 0.33 Dynamic load device bios.vxd
6:59:31 0.89 Dynamic load device pci.vxd
6:59:36 0.61 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
6:59:38 3.89 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
6:59:43 0.72 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
6:59:44 0.33 DEVICEINIT = NDIS
6:59:44 4.50 Dynamic load device pppmac.vxd
6:59:50 3.22 Dynamic load device vdhcp.386
6:59:56 0.33 Initing hsflop.pdr
6:59:56 0.28 Initing esdi_506.pdr
6:59:57 0.61 Initing esdi_506.pdr
6:59:57 0.61 Init Success esdi_506.pdr
7:00:01 0.28 Dynamic load success
C:\WINDOWS\system\serial.vxd
7:00:02 2.44 Starting Wave Device for Voice

Modem



(MODEMWAVE\HALFDUPLEXVOICEWAVEDEVICE\ROOT&UNIMODEM 631CD54E&
COM1)
7:00:05 1.06 Dynamic load success dsound.vxd
7:00:08 93.06 InitDone = TSRQuery (time

estimated)

I'm puzzled by the first entry taking 154.72 secs.

for
=C:\WINDOWS\IFSHLP\SYS. Also, I've taken a once-over
look
at the eight page clean boot troubleshooting

procedure
and
the article on clean boot by Gary Terhune that you
referenced. Am I ready to try those procedures?

Sorry to be so much trouble and to take so much of

your
time.



-----Original Message-----
BTW, when I say the actual boot time on the clock,

I
mean
the boot time when you are
doing a normal boot, not a logged boot.

Another suggestion that may or may not shed any

light,
is
to do a clean boot, then
while in the clean boot environment, do a logged

boot
and
see what the log show, and
also how long the boot takes in real time on the

clock.

How to Perform Clean-Boot Troubleshooting for

Windows
98
http://support.microsoft.com?kbid=192926

"CLEAN BOOT -- What it is and why you need it." by

MS
MVP
Gary Terhune
http://snipurl.com/8gam
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"glee" wrote in message
...
George, there is nothing abnormal that I can see
there....it looks like many
bootlogs I have seen. What is the actual time it
takes
right now for your
computer
to boot, from the time you see the first boot

screen
with the memory count, to the
time you first see the Desktop load up....I mean
actual
time on the clock on the
wall?
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm

"George"

wrote
in
message
...
Uninstalled the Norton Anti-Virus program and

the
only
long delays remaining (72.33 secs. total) are

for
the
many
entries which occur before TSRQuery is run.

Here
is a
copy
of the excerpted list of entries from the end

of
the
detailed Bootlog Analysis Report run after
uninstalling
Norton Anti-virus and rebooting:

12:22:26 0.06 INITCOMPLETE = VFBACKUP
12:22:26 0.00 INITCOMPLETESUCCESS =

VFBACKUP
12:22:26 0.06 INITCOMPLETE = SHELL
12:22:26 0.00 INITCOMPLETESUCCESS = SHELL
12:22:26 0.00 Initializing KERNEL (time
estimated)
12:22:26 0.00 LoadStart = system.drv (time
estimated)
12:22:26 0.00 LoadSuccess = system.drv (time
estimated)
12:22:26 0.00 LoadStart = keyboard.drv (time
estimated)
12:22:26 0.00 LoadSuccess = keyboard.drv

(time
estimated)
12:22:26 0.00 LoadStart = mouse.drv (time
estimated)
12:22:26 0.00 LoadSuccess = mouse.drv (time
estimated)
12:22:26 0.00 LoadStart = trid_pci.drv (time
estimated)
12:22:26 0.00 LoadStart = DIBENG.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = DIBENG.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = trid_pci.drv

(time
estimated)
12:22:26 0.00 LoadStart = mmsound.drv (time
estimated)
12:22:26 0.00 LoadSuccess = mmsound.drv

(time
estimated)
12:22:26 0.00 LoadStart = comm.drv (time
estimated)
12:22:26 0.00 LoadSuccess = comm.drv (time
estimated)
12:22:26 0.00 LoadStart = gdi.exe (time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\SYSTEM\GDI32.DLL
(time estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\SYSTEM\GDI32.DLL
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgasys.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgasys.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgafix.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgafix.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgaoem.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgaoem.fon
(time estimated)
12:22:26 0.00 LoadSuccess = gdi.exe (time
estimated)
12:22:26 0.00 LoadStart = user.exe (time
estimated)
12:22:26 0.00 LoadStart = DDEML.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = DDEML.DLL (time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\SYSTEM\USER32.DLL
(time estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\SYSTEM\USER32.DLL (time estimated)
12:22:26 0.00 LoadStart = COOL.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = COOL.DLL (time
estimated)
12:22:26 0.00 Init = KEYBOARD (time

estimated)
12:22:26 0.00 InitDone = KEYBOARD (time
estimated)
12:22:26 0.00 Init = Mouse (time estimated)
12:22:26 0.00 Status = Mouse driver

installed
(time
estimated)
12:22:26 0.00 InitDone = Mouse (time

estimated)
12:22:26 0.00 Init = (time estimated)
12:22:26 0.00 LoadStart = DISPLAY.drv (time
estimated)
12:22:26 0.00 LoadSuccess = DISPLAY.drv

(time
estimated)
12:22:26 0.00 InitDone = DISPLAY (time
estimated)
12:22:26 0.00 Init = Display Resources (time
estimated)
12:22:26 0.00 InitDone = Display Resources

(time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\serife.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\serife.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\sserife.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\sserife.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\coure.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\coure.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\symbole.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\symbole.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\smalle.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\smalle.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_czec.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_czec.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_engl.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_engl.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_fren.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_fren.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_germ.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_germ.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_ital.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_ital.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_span.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_span.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_swed.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_swed.fon (time estimated)
12:22:26 0.00 LoadSuccess = user.exe (time
estimated)
12:22:26 0.00 LoadStart = MSGSRV32.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = MSGSRV32.EXE

(time
estimated)
12:22:26 0.00 Init = Final USER (time

estimated)
12:22:26 0.00 InitDone = Final USER (time
estimated)
12:22:26 0.00 Init = Installable Drivers

(time
estimated)
12:22:26 0.00 InitDone = Installable Drivers
(time
estimated)
12:22:26 0.00 Init = TSRQuery (time

estimated)
12:22:26 72.33 InitDone = TSRQuery (time
estimated)
12:23:39 0.22 Enumerating Standard Floppy

Disk
Controller (BIOS\*PNP0700\0B)
12:23:39 0.00 Enumerated Standard Floppy

Disk
Controller (BIOS\*PNP0700\0B)

The questionable list of items seems to start
with "Initializing KERNEL" and ends

with "InitDone
=
TSRQuery." Do you know whether this is a normal
sequence
for the start-up or if there is a problem which
can be
corrected? Thinking of using anti-virus

software
called EZ
ARMOR LE by Computer Associates. Your further
thoughts and
advice appreciated.


-----Original Message-----
Quoting MS MVP Richard Harper:
"TSRQuery is not to blame. There are several
unlogged
actions that happen
before TSRQuery is run, so it appears to be

the
problem
even though it is
not. There's no good way to tell what's to

blame
since
the actions are not
logged."

If you didn't have the problem before and do

now,
then it
must come from some change
you made just prior to the experienced

increase in
the
boot time. Likely it is some
driver causing it. The delays due to Symantec
entries I
can't help you with, as I
do not like or use their software. Were it my
machine, I
would uninstall all the
Symantec/Norton software, and see if the boot
delay
continues.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


wrote in
message
...
Thanks Glen, the mouse load up problem is

gone.
Here is
the latest Delays and Failures Report from
Bootlog
Analyzer:

11:50:31 9.11 LoadSuccess =
C:\WINDOWS\IFSHLP.SYS
11:50:41 0.11 LoadFailed = ndis2sup.vxd
11:50:43 0.28 Loading Vxd =
C:\WINDOWS\system\VMM32
\IFSMGR.VXD
11:50:43 0.33 Loading Vxd =
C:\WINDOWS\system\VMM32
\IOS.VXD
11:50:49 3.06 LoadSuccess = vnetbios.vxd
11:50:52 2.39 Loading Vxd = C:\PROGRA~1
\SYMANTEC\SYMEVNT.386
11:50:55 0.39 Loading Vxd = dfs.vxd
11:51:09 0.06 DEVICEINITFAILED = MTRR
11:51:10 0.50 DEVICEINITSUCCESS = VTD
11:51:11 0.28 DEVICEINIT = NTKERN
11:51:13 0.39 Dynamic load device

bios.vxd
11:51:18 0.83 Dynamic load device

pci.vxd
11:51:30 0.28 DEVICEINIT = IOS
11:51:31 0.44 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
11:51:33 2.50 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
11:51:39 0.83 Started Standard Serial

Mouse
(ROOT\*PNP0F0C\0000)
11:51:41 0.61 DEVICEINIT = NDIS
11:51:46 3.89 Dynamic load device

vdhcp.386
11:51:58 0.33 Initing hsflop.pdr
11:51:58 0.44 Initing esdi_506.pdr
11:51:59 0.67 Initing esdi_506.pdr
11:51:59 0.83 Init Success esdi_506.pdr
11:52:07 0.11 INITCOMPLETEFAILED =

SDVXD
11:52:11 0.33 Dynamic load success
C:\WINDOWS\system\serial.vxd
11:52:12 0.28 Enumerated Printer Port

(LPT1)
(BIOS\*PNP0400\0C)
11:52:14 0.28 Dynamic load device
dsound.vxd
11:52:15 1.11 Dynamic load success
dsound.vxd
11:52:16 0.33 Dynamic load device

vjoyd.vxd
11:52:18 7.00 INITCOMPLETE = NAVAP
11:52:25 4.28 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVEX15.VXD
11:52:29 3.11 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
11:52:32 125.89 Dynamic load success
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
11:54:38 0.28 INITCOMPLETESUCCESS =

NAVAP
11:54:45 99.50 InitDone = TSRQuery (time
estimated)
11:56:25 0.83 Enumerating Standard

Floppy
Disk
Controller (BIOS\*PNP0700\0B)

The two delays that stick out are, of

course,
the
Norton
(Symantec) anti-virus program stuff and the
TSRQuery
items.
Any further help to hone in on those two

delay
places
will
be appreciated.


-----Original Message-----
My Logitech plugs into a serial port. What

I
did
to
replace with a standard mouse driver was

this:
StartSettingsC. PanelSystemDevice

Manager
TabMouseHi-
lite MouseDriver TabUpdate Driver

buttonNext
buttonSelected Search for Better

Driver...etc.
After the search, a better MS driver was

found
and I
okayed its installation.

I will uninstall Logitech mouse and reboot.
Thanks for
the
explanation - sorry didn't get it the first
time!

-----Original Message-----
You say you replaced the Logitech mouse

driver
with a
standard mouse driver. Do you
have a serial mouse or a PS/2 mouse? The
driver
you
added is "Standard Serial
Mouse", which is only for a serial mouse,

and
you are
still loading the Logitech
driver.....Loading Vxd = LMOUSE.VXD

What I meant for you to try is to remove
(uninstall)
the
Logitech mouse (not add a
mouse manually), reboot, and let Windows

add
its
own
driver on its own.

I will see what else I can find re your
delays.
A lot
of
them are from Symantec
anti-virus loading, though the 8-minute

time
is
far
too
long.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George"


wrote
in
message
news:5c0d01c491f8$abc3cf70

...
Have never used MSBackup, so

uninstalled
and
then
changed
file names per instruction. The tape
detection
has
been
disabled and it seems to be working

okay
so
far!
Here is a copy of the new Failures and
Delays
Log:

14:52:30 7.28 LoadSuccess =
C:\WINDOWS\IFSHLP.SYS
14:52:38 0.11 LoadFailed =

ndis2sup.vxd
14:52:40 0.44 Loading Vxd =
C:\WINDOWS\system\VMM32
\IFSMGR.VXD
14:52:46 2.72 LoadSuccess =

vnetbios.vxd
14:52:49 1.11 Loading Vxd =

C:\PROGRA~1
\SYMANTEC\SYMEVNT.386
14:52:50 20.17 Loading Vxd =

LMOUSE.VXD
14:53:11 0.61 Loading Vxd = dfs.vxd
14:53:24 0.06 DEVICEINITFAILED =

MTRR
14:53:25 0.56 DEVICEINITSUCCESS =

VTD
14:53:26 0.28 DEVICEINIT = NTKERN
14:53:33 0.78 Dynamic load device
pci.vxd
14:53:44 0.39 DEVICEINIT = IOS
14:53:46 0.50 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
14:53:48 2.33 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
14:53:53 0.78 Started Standard

Serial
Mouse
(ROOT\*PNP0F0C\0000)
14:53:56 0.50 DEVICEINIT = NDIS
14:54:01 2.11 Dynamic load device
vdhcp.386
14:54:10 0.56 DEVICEINITSUCCESS =

VDEF
14:54:14 2.22 INITCOMPLETE = IOS
14:54:17 10.39 INITCOMPLETESUCCESS =

IOS
14:54:30 0.06 INITCOMPLETEFAILED =
SDVXD
14:54:35 0.33 Dynamic load success
C:\WINDOWS\system\serial.vxd
14:54:38 2.56 Dynamic load success
dsound.vxd
14:54:41 0.44 Dynamic load device
vjoyd.vxd
14:54:43 7.61 INITCOMPLETE = NAVAP
14:54:50 4.61 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVEX15.VXD
14:54:55 2.50 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVENG.VXD
14:54:58 75.83 Dynamic load success
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVENG.VXD
14:56:14 0.67 INITCOMPLETESUCCESS =
NAVAP


.

.


.



.


.


.

.



  #49  
Old September 9th 04, 03:35 AM posted to microsoft.public.win98.performance
Ron Badour
External Usenet User
 
Posts: 957
Default Interpretation of failures and delays at boot.

Your hardware is inadequate for XP and I do not think you will be happy with
the performance.
MS recommends 128 mb of ram and I personally recommend 256 mb or more. You
might want to ask for recommendations in an XP newsgroup.
--
Regards

Ron Badour, MS MVP for W98
Tips: http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo

"George" wrote in message
...
Well, it looks like my drive is bad. Here is what happened.

Went to the Western Digital site www.wdc.com. Until your
suggestion, I didn't know this free disk diagnosis service
was available. Anyway, downloaded from support.wdc.com
their lifeguard.exe into Temp Folder. It installed into
C:/DataLifeguard 9x Folder. Then I ran the program.

It first recognized my drives and offered to run a SMART
test which I then had done on the 4GB master drive (the
slave drive which was the original and holds all of
232MB). The message came back "SMART Test Passed. Would
you like to run a Quick Functional Test of your drive"?
(Recommended) Clicked Yes.

Twenty seconds later came back the result "Quick
Functional Test Failed!! Would you like to run the Quick
Restore Surface Scan? ... Note: Depending on system
performance and errors, this test may take up to an hour
to complete." Clicked Yes.

Two hours later with the scan only 13% completed, pop-up
box appeared and read "Repair has detected multiple drive
errors. It is recommended that you backup your data
immediately!!! Program aborted..."

I can't complain, seven years of trouble-free service is
beyond the call of duty for any drive. The good news is
that I still have access to the disk's data, and new units
are reasonably priced. Think around $2,000 was paid for
Dell 486 Dimension in 1993. Will probably try WinXP with
the new unit but will keep Win 98SE in reserve - it's been
an outstanding and very reliable operating system.

To both SFB and Glen, thank you once again for your
invaluable help. The best things in life are truly free.



-----Original Message-----
Okay to SFB and Glen. I will track down the Western
Digital site and see what they have to impart. Perhaps
it's been a bad disk all along - started out with a
message: "Press any key to run ScanDisk with surface
analysis on these drives...Invalid Switch: /SIMPLEUI."
Then I did a Thorough ScanDisk and Defrag which took

about
30 hours, and also did the anti-virus scans with Norton,
Spybot and Adaware. The "Invalid Switch" message went
away so thought it was probably software.

Will let you know the result of the visit to Western
Digital. Thanks for steering me along - couldn't do the
troubleshoot without you.

-----Original Message-----
Is your disk in good shape ?
Wondering if you should download the
disk diagnostic from the disk mfgr's web site and run

the
non-destructive
tests.

Might have a flakey sector or two

"George" wrote in

message
...
Hello Glen. I'm using a dial-up connection and the best
speed we get in this area is usually 28,000 bps. Not on
any type of network, just a simple home set-up on a

Dell
Precision 486 purchased the end of 1993 upgraded 1997

to
AMD K-6 chip, 96 RAM, 4GB HD - think the OS started

with
Win3.1, then Win95 and upgraded to Win 98SE.

Earlier you had me do a full system virus scan which I

did
do. Next, I was able to download Spybot and Adaware but
not CWShredder. For some reason CWShredder would not
download into my system. I ran Spybot and Adaware for
several days, then cleared them out. Adaware found

nothing
and Spybot found one item which was promptly removed.
Right now I'm operating without an anti-virus program

as
Norton Anti-Virus was uninstalled day before yesterday
since we thought it might be behind the long boot
problems. Also, I think I want to change to another

anti-
virus program. But I'm being careful and only coming to
this support.microsoft.com site when on the internet.

I have run the clean boot procedure from the Gary

Terhune
article recommended earlier. After completing

his "clean
boot" list, this is what the Bootlog Analysis Report
(Delays) looked like:

6:56:38 154.72 LoadSuccess =

C:\WINDOWS\IFSHLP.SYS
6:59:14 0.67 Loading Vxd = C:\WINDOWS\system\VMM32
\IFSMGR.VXD
6:59:15 0.28 Loading Vxd = C:\WINDOWS\system\VMM32
\IOS.VXD
6:59:19 0.72 Loading Vxd = dfs.vxd
6:59:26 0.50 DEVICEINITSUCCESS = VTD
6:59:28 0.33 Dynamic load device bios.vxd
6:59:31 0.89 Dynamic load device pci.vxd
6:59:36 0.61 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
6:59:38 3.89 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
6:59:43 0.72 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
6:59:44 0.33 DEVICEINIT = NDIS
6:59:44 4.50 Dynamic load device pppmac.vxd
6:59:50 3.22 Dynamic load device vdhcp.386
6:59:56 0.33 Initing hsflop.pdr
6:59:56 0.28 Initing esdi_506.pdr
6:59:57 0.61 Initing esdi_506.pdr
6:59:57 0.61 Init Success esdi_506.pdr
7:00:01 0.28 Dynamic load success
C:\WINDOWS\system\serial.vxd
7:00:02 2.44 Starting Wave Device for Voice Modem


(MODEMWAVE\HALFDUPLEXVOICEWAVEDEVICE\ROOT&UNIMODEM 631CD54E&
COM1)
7:00:05 1.06 Dynamic load success dsound.vxd
7:00:08 93.06 InitDone = TSRQuery (time estimated)

The above test was run yesterday morning (Tuesday 7 Sep
04), and this morning the same report showed 349

seconds
for = C:\WINDOWS\IFSHLP.SYS!! The clock-on-the-wall

time
for yesterday's report displayed above was 8 min. 55

secs.
This covers the time from when the Win 98 Menu first
appears until the full icons appear on the desktop.

Don't
understand why the time on the Bootlog Analysis Report

is
much shorter.

An icon double-clicked on the desktop then takes

another
55 secs. to pull up that selected item, but after it's
been used that first time and then closed and

reopened -
the icon/progam/item responds by opening at normal

speed
(about 5 secs). This is another symptom that has

continued
since it first slowed down about two weeks ago - seems
related.

How does one examen the time used in

C:\WINDOWS\IFHLP\SYS?
Your continued direction and advice appreciated.




-----Original Message-----
George, are you using a broadband connection or a

dial-
up
connection? Do you have a
Network card (NIC) or integrated network interface in

the
computer? Are you on any
type of network?

Also, I suggest you do a complete check for
malware/adwa

Update your anti-virus app and then run a full-system
virus scan.

Use CWShredder, the CoolWeb removal tool, available

he
http://www.majorgeeks.com/downloads31.html
http://aumha.org/downloads/cwshredder.zip
Close all browser windows and open apps, start

CWShredder
and click the Fix button.

In addition, install Ad-Aware SE free edition, start

it,
click its 'Check for
Updates' link in the app to install updates, then use

it
to scan your system, and
remove what it finds.
Ad-Awa
http://www.lavasoftusa.com/support/download/

Install, update and run SpyBot Search & Destroy, scan
your system, and then remove
the items in RED only.
SpyBot S&D:
http://www.safer-networking.org/index.php?

page=download

Install SpywareBlaster:
http://www.majorgeeks.com/download2859.html
Click the link in the app to check for and install
updates, then click to 'Enable
all protection'.
Update at least weekly.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George" wrote

in
message
...
Here are the clock-on-the-wall times for a normal

boot:

1. Win98 Startup Menu 0:00
2. Win98 Blue Sky Page 0:30
3. Black Screen ending C:\ 4:40
4. Green Screen arrow/timeglass 5:35
5. Icons appear on desktop 7:35
6. Timeglass disappears 8:15

Yesterday I ran Maintenance Wizard - the defrag took
about
8 hours. I thought it a good idea after removing

Norton
Anti-Virus - that was the only thing done on this
computer.

For comparison here is the Bootlog Analysis Delays

and
Failures Report run just before the above timed

boot:

6:56:38 154.72 LoadSuccess =

C:\WINDOWS\IFSHLP.SYS
6:59:14 0.67 Loading Vxd =

C:\WINDOWS\system\VMM32
\IFSMGR.VXD
6:59:15 0.28 Loading Vxd =

C:\WINDOWS\system\VMM32
\IOS.VXD
6:59:19 0.72 Loading Vxd = dfs.vxd
6:59:26 0.50 DEVICEINITSUCCESS = VTD
6:59:28 0.33 Dynamic load device bios.vxd
6:59:31 0.89 Dynamic load device pci.vxd
6:59:36 0.61 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
6:59:38 3.89 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
6:59:43 0.72 Started Standard Serial Mouse
(ROOT\*PNP0F0C\0000)
6:59:44 0.33 DEVICEINIT = NDIS
6:59:44 4.50 Dynamic load device pppmac.vxd
6:59:50 3.22 Dynamic load device vdhcp.386
6:59:56 0.33 Initing hsflop.pdr
6:59:56 0.28 Initing esdi_506.pdr
6:59:57 0.61 Initing esdi_506.pdr
6:59:57 0.61 Init Success esdi_506.pdr
7:00:01 0.28 Dynamic load success
C:\WINDOWS\system\serial.vxd
7:00:02 2.44 Starting Wave Device for Voice

Modem



(MODEMWAVE\HALFDUPLEXVOICEWAVEDEVICE\ROOT&UNIMODEM 631CD54E&
COM1)
7:00:05 1.06 Dynamic load success dsound.vxd
7:00:08 93.06 InitDone = TSRQuery (time

estimated)

I'm puzzled by the first entry taking 154.72 secs.

for
=C:\WINDOWS\IFSHLP\SYS. Also, I've taken a once-over
look
at the eight page clean boot troubleshooting

procedure
and
the article on clean boot by Gary Terhune that you
referenced. Am I ready to try those procedures?

Sorry to be so much trouble and to take so much of

your
time.



-----Original Message-----
BTW, when I say the actual boot time on the clock,

I
mean
the boot time when you are
doing a normal boot, not a logged boot.

Another suggestion that may or may not shed any

light,
is
to do a clean boot, then
while in the clean boot environment, do a logged

boot
and
see what the log show, and
also how long the boot takes in real time on the

clock.

How to Perform Clean-Boot Troubleshooting for

Windows
98
http://support.microsoft.com?kbid=192926

"CLEAN BOOT -- What it is and why you need it." by

MS
MVP
Gary Terhune
http://snipurl.com/8gam
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"glee" wrote in message
...
George, there is nothing abnormal that I can see
there....it looks like many
bootlogs I have seen. What is the actual time it
takes
right now for your
computer
to boot, from the time you see the first boot

screen
with the memory count, to the
time you first see the Desktop load up....I mean
actual
time on the clock on the
wall?
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm

"George"

wrote
in
message
...
Uninstalled the Norton Anti-Virus program and

the
only
long delays remaining (72.33 secs. total) are

for
the
many
entries which occur before TSRQuery is run.

Here
is a
copy
of the excerpted list of entries from the end

of
the
detailed Bootlog Analysis Report run after
uninstalling
Norton Anti-virus and rebooting:

12:22:26 0.06 INITCOMPLETE = VFBACKUP
12:22:26 0.00 INITCOMPLETESUCCESS =

VFBACKUP
12:22:26 0.06 INITCOMPLETE = SHELL
12:22:26 0.00 INITCOMPLETESUCCESS = SHELL
12:22:26 0.00 Initializing KERNEL (time
estimated)
12:22:26 0.00 LoadStart = system.drv (time
estimated)
12:22:26 0.00 LoadSuccess = system.drv (time
estimated)
12:22:26 0.00 LoadStart = keyboard.drv (time
estimated)
12:22:26 0.00 LoadSuccess = keyboard.drv

(time
estimated)
12:22:26 0.00 LoadStart = mouse.drv (time
estimated)
12:22:26 0.00 LoadSuccess = mouse.drv (time
estimated)
12:22:26 0.00 LoadStart = trid_pci.drv (time
estimated)
12:22:26 0.00 LoadStart = DIBENG.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = DIBENG.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = trid_pci.drv

(time
estimated)
12:22:26 0.00 LoadStart = mmsound.drv (time
estimated)
12:22:26 0.00 LoadSuccess = mmsound.drv

(time
estimated)
12:22:26 0.00 LoadStart = comm.drv (time
estimated)
12:22:26 0.00 LoadSuccess = comm.drv (time
estimated)
12:22:26 0.00 LoadStart = gdi.exe (time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\SYSTEM\GDI32.DLL
(time estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadStart = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = GDI.EXE (time
estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\SYSTEM\GDI32.DLL
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgasys.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgasys.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgafix.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgafix.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\vgaoem.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\vgaoem.fon
(time estimated)
12:22:26 0.00 LoadSuccess = gdi.exe (time
estimated)
12:22:26 0.00 LoadStart = user.exe (time
estimated)
12:22:26 0.00 LoadStart = DDEML.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = DDEML.DLL (time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\SYSTEM\USER32.DLL
(time estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadStart = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = USER.EXE (time
estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\SYSTEM\USER32.DLL (time estimated)
12:22:26 0.00 LoadStart = COOL.DLL (time
estimated)
12:22:26 0.00 LoadSuccess = COOL.DLL (time
estimated)
12:22:26 0.00 Init = KEYBOARD (time

estimated)
12:22:26 0.00 InitDone = KEYBOARD (time
estimated)
12:22:26 0.00 Init = Mouse (time estimated)
12:22:26 0.00 Status = Mouse driver

installed
(time
estimated)
12:22:26 0.00 InitDone = Mouse (time

estimated)
12:22:26 0.00 Init = (time estimated)
12:22:26 0.00 LoadStart = DISPLAY.drv (time
estimated)
12:22:26 0.00 LoadSuccess = DISPLAY.drv

(time
estimated)
12:22:26 0.00 InitDone = DISPLAY (time
estimated)
12:22:26 0.00 Init = Display Resources (time
estimated)
12:22:26 0.00 InitDone = Display Resources

(time
estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\serife.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\serife.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\sserife.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\sserife.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\coure.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\coure.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\symbole.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\symbole.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\smalle.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\smalle.fon
(time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_czec.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_czec.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_engl.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_engl.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_fren.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_fren.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_germ.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_germ.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_ital.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_ital.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_span.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_span.fon (time estimated)
12:22:26 0.00 LoadStart =
C:\WINDOWS\fonts\wst_swed.fon
(time estimated)
12:22:26 0.00 LoadSuccess =
C:\WINDOWS\fonts\wst_swed.fon (time estimated)
12:22:26 0.00 LoadSuccess = user.exe (time
estimated)
12:22:26 0.00 LoadStart = MSGSRV32.EXE (time
estimated)
12:22:26 0.00 LoadSuccess = MSGSRV32.EXE

(time
estimated)
12:22:26 0.00 Init = Final USER (time

estimated)
12:22:26 0.00 InitDone = Final USER (time
estimated)
12:22:26 0.00 Init = Installable Drivers

(time
estimated)
12:22:26 0.00 InitDone = Installable Drivers
(time
estimated)
12:22:26 0.00 Init = TSRQuery (time

estimated)
12:22:26 72.33 InitDone = TSRQuery (time
estimated)
12:23:39 0.22 Enumerating Standard Floppy

Disk
Controller (BIOS\*PNP0700\0B)
12:23:39 0.00 Enumerated Standard Floppy

Disk
Controller (BIOS\*PNP0700\0B)

The questionable list of items seems to start
with "Initializing KERNEL" and ends

with "InitDone
=
TSRQuery." Do you know whether this is a normal
sequence
for the start-up or if there is a problem which
can be
corrected? Thinking of using anti-virus

software
called EZ
ARMOR LE by Computer Associates. Your further
thoughts and
advice appreciated.


-----Original Message-----
Quoting MS MVP Richard Harper:
"TSRQuery is not to blame. There are several
unlogged
actions that happen
before TSRQuery is run, so it appears to be

the
problem
even though it is
not. There's no good way to tell what's to

blame
since
the actions are not
logged."

If you didn't have the problem before and do

now,
then it
must come from some change
you made just prior to the experienced

increase in
the
boot time. Likely it is some
driver causing it. The delays due to Symantec
entries I
can't help you with, as I
do not like or use their software. Were it my
machine, I
would uninstall all the
Symantec/Norton software, and see if the boot
delay
continues.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


wrote in
message
...
Thanks Glen, the mouse load up problem is

gone.
Here is
the latest Delays and Failures Report from
Bootlog
Analyzer:

11:50:31 9.11 LoadSuccess =
C:\WINDOWS\IFSHLP.SYS
11:50:41 0.11 LoadFailed = ndis2sup.vxd
11:50:43 0.28 Loading Vxd =
C:\WINDOWS\system\VMM32
\IFSMGR.VXD
11:50:43 0.33 Loading Vxd =
C:\WINDOWS\system\VMM32
\IOS.VXD
11:50:49 3.06 LoadSuccess = vnetbios.vxd
11:50:52 2.39 Loading Vxd = C:\PROGRA~1
\SYMANTEC\SYMEVNT.386
11:50:55 0.39 Loading Vxd = dfs.vxd
11:51:09 0.06 DEVICEINITFAILED = MTRR
11:51:10 0.50 DEVICEINITSUCCESS = VTD
11:51:11 0.28 DEVICEINIT = NTKERN
11:51:13 0.39 Dynamic load device

bios.vxd
11:51:18 0.83 Dynamic load device

pci.vxd
11:51:30 0.28 DEVICEINIT = IOS
11:51:31 0.44 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
11:51:33 2.50 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
11:51:39 0.83 Started Standard Serial

Mouse
(ROOT\*PNP0F0C\0000)
11:51:41 0.61 DEVICEINIT = NDIS
11:51:46 3.89 Dynamic load device

vdhcp.386
11:51:58 0.33 Initing hsflop.pdr
11:51:58 0.44 Initing esdi_506.pdr
11:51:59 0.67 Initing esdi_506.pdr
11:51:59 0.83 Init Success esdi_506.pdr
11:52:07 0.11 INITCOMPLETEFAILED =

SDVXD
11:52:11 0.33 Dynamic load success
C:\WINDOWS\system\serial.vxd
11:52:12 0.28 Enumerated Printer Port

(LPT1)
(BIOS\*PNP0400\0C)
11:52:14 0.28 Dynamic load device
dsound.vxd
11:52:15 1.11 Dynamic load success
dsound.vxd
11:52:16 0.33 Dynamic load device

vjoyd.vxd
11:52:18 7.00 INITCOMPLETE = NAVAP
11:52:25 4.28 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVEX15.VXD
11:52:29 3.11 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
11:52:32 125.89 Dynamic load success
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004\NAVENG.VXD
11:54:38 0.28 INITCOMPLETESUCCESS =

NAVAP
11:54:45 99.50 InitDone = TSRQuery (time
estimated)
11:56:25 0.83 Enumerating Standard

Floppy
Disk
Controller (BIOS\*PNP0700\0B)

The two delays that stick out are, of

course,
the
Norton
(Symantec) anti-virus program stuff and the
TSRQuery
items.
Any further help to hone in on those two

delay
places
will
be appreciated.


-----Original Message-----
My Logitech plugs into a serial port. What

I
did
to
replace with a standard mouse driver was

this:
StartSettingsC. PanelSystemDevice

Manager
TabMouseHi-
lite MouseDriver TabUpdate Driver

buttonNext
buttonSelected Search for Better

Driver...etc.
After the search, a better MS driver was

found
and I
okayed its installation.

I will uninstall Logitech mouse and reboot.
Thanks for
the
explanation - sorry didn't get it the first
time!

-----Original Message-----
You say you replaced the Logitech mouse

driver
with a
standard mouse driver. Do you
have a serial mouse or a PS/2 mouse? The
driver
you
added is "Standard Serial
Mouse", which is only for a serial mouse,

and
you are
still loading the Logitech
driver.....Loading Vxd = LMOUSE.VXD

What I meant for you to try is to remove
(uninstall)
the
Logitech mouse (not add a
mouse manually), reboot, and let Windows

add
its
own
driver on its own.

I will see what else I can find re your
delays.
A lot
of
them are from Symantec
anti-virus loading, though the 8-minute

time
is
far
too
long.
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"George"


wrote
in
message
news:5c0d01c491f8$abc3cf70

...
Have never used MSBackup, so

uninstalled
and
then
changed
file names per instruction. The tape
detection
has
been
disabled and it seems to be working

okay
so
far!
Here is a copy of the new Failures and
Delays
Log:

14:52:30 7.28 LoadSuccess =
C:\WINDOWS\IFSHLP.SYS
14:52:38 0.11 LoadFailed =

ndis2sup.vxd
14:52:40 0.44 Loading Vxd =
C:\WINDOWS\system\VMM32
\IFSMGR.VXD
14:52:46 2.72 LoadSuccess =

vnetbios.vxd
14:52:49 1.11 Loading Vxd =

C:\PROGRA~1
\SYMANTEC\SYMEVNT.386
14:52:50 20.17 Loading Vxd =

LMOUSE.VXD
14:53:11 0.61 Loading Vxd = dfs.vxd
14:53:24 0.06 DEVICEINITFAILED =

MTRR
14:53:25 0.56 DEVICEINITSUCCESS =

VTD
14:53:26 0.28 DEVICEINIT = NTKERN
14:53:33 0.78 Dynamic load device
pci.vxd
14:53:44 0.39 DEVICEINIT = IOS
14:53:46 0.50 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\diskvsd.vxd
14:53:48 2.33 Dynamic load device
C:\WINDOWS\system\IOSUBSYS\acbhlpr.vxd
14:53:53 0.78 Started Standard

Serial
Mouse
(ROOT\*PNP0F0C\0000)
14:53:56 0.50 DEVICEINIT = NDIS
14:54:01 2.11 Dynamic load device
vdhcp.386
14:54:10 0.56 DEVICEINITSUCCESS =

VDEF
14:54:14 2.22 INITCOMPLETE = IOS
14:54:17 10.39 INITCOMPLETESUCCESS =

IOS
14:54:30 0.06 INITCOMPLETEFAILED =
SDVXD
14:54:35 0.33 Dynamic load success
C:\WINDOWS\system\serial.vxd
14:54:38 2.56 Dynamic load success
dsound.vxd
14:54:41 0.44 Dynamic load device
vjoyd.vxd
14:54:43 7.61 INITCOMPLETE = NAVAP
14:54:50 4.61 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVEX15.VXD
14:54:55 2.50 Dynamic load device
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVENG.VXD
14:54:58 75.83 Dynamic load success
C:\PROGRA~1
\COMMON~1
\SYMANT~1\VIRUSD~1\20030430.004

\NAVENG.VXD
14:56:14 0.67 INITCOMPLETESUCCESS =
NAVAP


.

.


.



.


.


.

.



 




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT +1. The time now is 12:57 PM.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2024, Jelsoft Enterprises Ltd.
Copyright ©2004-2024 Win98banter.
The comments are property of their posters.