• We should now be fully online following an overnight outage. Apologies for any inconvenience, we do not expect there to be any further issues.

What is causing my win98se booting so looooooooong?

MAMAFUFU

Senior member
Oct 9, 1999
415
0
76
Recently I find that my win98se machine takes very long time to boot up.(It usually boots up very fast.) So I run the bootup analyzer, and found the following:
Delayed events
Failed events

Can anyone tell me what is TSR Query and why it takes so long to initialise?

Also the fail.htm shows HUNDREDS of failed events, they look like fonts are unable to load, but I can use all fonts(both chinese and english fonts) in Word without any problem. So what happens?

 

esung

Golden Member
Oct 13, 1999
1,063
0
0
ouch.. I had a similar problem enountered on my mom and my sister's system. and no one so far knows what's the failure code 0016 means, or how to correct it. Did you try to use RegClean or other registry cleaning too to fix it(backup first, of course). The computer has problems were end up reinstalling the OS. A question of mine: Did you get infacted by the W32QAZ virus before by any chance?
 

MAMAFUFU

Senior member
Oct 9, 1999
415
0
76
My comp(actually there are 10 computers with same config, same problem) is coonected to a router for broadband internet access. But all were boot up fast initially, with connection to the router, only recently they all take a long time to boot. Of course I installed some hardware and software in this period, but I don't know what what hardware/software might be causing this problem.

I only re-install win98se yesterday, no improvement on boot up time.
 

LordOfAll

Senior member
Nov 24, 1999
838
0
0
from the microshaft knowledge base

InitCompleteFailed = SDVXD
Windows automatically loads a miniature disk cache to increase the speed of the startup process. When the startup process is complete, the miniature disk cache is unloaded from memory. When the cache is unloaded, the "InitCompleteFailed = SDVXD" line is added to the Bootlog.txt file to indicate that the miniature disk cache has been removed from memory. This behavior is typical

LoadFailed = ndis2sup.vxd
If the network driver interface specification (NDIS) 2 support driver does not find any NDIS 2 drivers to support, the driver is not loaded.

Font Failures
After you first start Windows, the Bootlog.txt file may list many font load failures. This behavior is typical. When Font Manager searches the hard disk for fonts, it may find fonts in several folders. After Font Manager finds fonts, it records the information so that future attempts to locate a font proceed more quickly.

This and others can be found here

 

LordOfAll

Senior member
Nov 24, 1999
838
0
0
A TSR is a terminate and stay resident program. For example in the old DOS days you would want to run some things automatically at start up, like antivirus, disk cache, etc... I would look for a piece of software that is looking for hardware that is not attached to the machine anymore or I would have to point the finger at the antivrus software. Try uninstalling it and see if that delay is removed. Then it is up to you if you want to keep it resident. I would lean toword having av software, but you may want to try a different av program.
 

cavingjan

Golden Member
Nov 15, 1999
1,719
0
0
If this happened at the same time you added the router (and possibly nics?), it is simply the dhcp taking time in give the computer an ip address. Not too many options here. You can either keep it as is, or give everybody static ip addresses and deal with it in the router. And how long is a long time? about a minute? two minutes? five minutes?
 

MAMAFUFU

Senior member
Oct 9, 1999
415
0
76
The router was added a long time ago, but the long boot up time only occur recently, so I think it's not the router causing the delay.
You can see from the Delayed events that the initialisation of TSR cause a delay of more than 33 seconds.

Also all fonts are placed in the same(default) folder.
 

skace

Lifer
Jan 23, 2001
14,488
7
81
MAMAFUFU,
To really make sure it is not the router, you should remove one of the computers from the network and turn off all its network settings. Then and only then will you know it is something else that is happening...

I've never seen a win98 problem that migrated across 10 computers that wasn't network related... (other than a virus)