MDP,

I am using BLA.exe and set it to show delays. There are about 15 items from
..278 seconds to the highest of 10.778 seconds (IFSHLP.SYS). Do you have any
other suggestions? Thanks.
Steve

"mdp" wrote in message
...
There is a way to measure how long everything takes to boot. The
application that collects the information from bootlog.txt is called
bla.exe. Unzip the following download:

http://www.geocities.com/Athens/Troy...wnLoad/Bla.zip

More info from the same site:

http://www.geocities.com/~budallen/bootboot.html

Follow the instructions here under "Using Bootlog Analyzer":


http://www.greatis.com/webhelp/regru...g_analyser.htm

Good luck.

"Steve L" slupardi at comcast dot net wrote in message
...
I have tried the suggestions on the link with the static IP address, but
no
luck. Still 3 minutes to start up once the blank desktop appears. Any
other
suggestions are welcome. Thanks.

Steve


"mdp" wrote in message
...
Without knowing how you're set up, it may be a case of trial and error.
However if you want to experiment, try this site - the addresses are
typical
of home networks:



http://support.dlink.com/faq/view.as...ral-Networking


"Steve L" slupardi at comcast dot net wrote in message
...
Can you tell me briefly how to turn off DHCPand adding a static IP
address.
I assume it's thru the Network settings in control panel. Thanks.
Steve

"mdp" wrote in message
...
I've shortened boot time considerably on Win98 by turning DHCP off
and
setting a static IP. Home networks typically use 192.168.0.X (pick
X).
Be
aware that whatever the NIC is connected to (e.g. router, modem,
etc)
may
also need to be properly configured.

"Steve L" slupardi at comcast dot net wrote in message
...
Last week I fooled with my LinkSys LNE100 network card. Now WIN98
(1st
edition) boots very slow. It stays on the blank desktop for over 2
minutes, then the icons start to load and everything goes as
normal.
I
reinstalled the network card drivers several times, did updated
NAV
scans,
spyware checks etc. A boot log analysis shows Ndis2sup.vxd failed
(but
I
read that's normal). This is not a
ram problem or such. There must be some setting or conflict with
something.
I suspect that windows is having a hard time finding something
(like
a
network ) at start up. Any ideas, either network or other?
Thanks.

Steve L