BLA indicates 23 second delay for TCP/IP network

I find this line in the BLA log list of delays,

15:51:11 24.28 Starting TCP/IP (NETWORK\MSTCP\0000)

I use dial-up and have no networks of any kind. Each time I open
Network in the Control Panel, a msg jumps up saying "Your network
in not complete. Do you want to continue".

I OK the msg and in the network configuration box I have
four icon listings.

Dial-Up Adapter [I use dial-up]
SIS 900 PCI Fast Ethernet Adapter
TCP/IP - Dialup Adapter
TCP/IP - SIS 900 PCI Fast Ethernet Adapter

I think the two SIS items are in case I want to use cable someday.
Are these entries causing the 24 second delay when I boot up or
is there another area I should be looking?

My other computer has a similar situation but only an 11 sec delay.

15:49:36 11.11 Starting TCP/IP (NETWORK\MSTCP\0001)

Network configuration box with about eight icon listings.

Is there a 'reversible' change I can make to eliminate the delay
without losing the future potential for a cable connection? Assuming
this has anything to do with it.

BoB

You've pretty much hit the nail on the head here, I think. The TCP/IP -
SIS network adapter entry is most likely causing your problem. If you have
your Windows 98 CD or the Windows Setup files on your hard drive (look for
several dozen files whose names all start with WIN98 and end in CAB) you can
remove the binding to the SIS network adapter for now, then reinstall it
when you need it.

--
Richard G. Harper [MVP Win9x]
* PLEASE post all messages and replies in the newsgroups
* for the benefit of all. Private mail is usually not replied to.
* HELP us help YOU ... http://www.dts-l.org/goodpost.htm


"BoB" wrote in message
...
I find this line in the BLA log list of delays,

15:51:11 24.28 Starting TCP/IP (NETWORK\MSTCP\0000)

I use dial-up and have no networks of any kind. Each time I open
Network in the Control Panel, a msg jumps up saying "Your network
in not complete. Do you want to continue".

I OK the msg and in the network configuration box I have
four icon listings.

Dial-Up Adapter [I use dial-up]
SIS 900 PCI Fast Ethernet Adapter
TCP/IP - Dialup Adapter
TCP/IP - SIS 900 PCI Fast Ethernet Adapter

I think the two SIS items are in case I want to use cable someday.
Are these entries causing the 24 second delay when I boot up or
is there another area I should be looking?

My other computer has a similar situation but only an 11 sec delay.

15:49:36 11.11 Starting TCP/IP (NETWORK\MSTCP\0001)

Network configuration box with about eight icon listings.

Is there a 'reversible' change I can make to eliminate the delay
without losing the future potential for a cable connection? Assuming
this has anything to do with it.

BoB

When I ran across this on another machine that was not connected to any networks and
whose NIC was configured to obtain an IP address automatically, what worked for me,
IIRC, was assigning the NIC a static IP address so that it did not try to contact a
DHCP server at startup:
192.168.0.1 (or actually 192.168.0.2 may be better), subnet mask 255.255.255.0
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm


"BoB" wrote in message
...
I find this line in the BLA log list of delays,

15:51:11 24.28 Starting TCP/IP (NETWORK\MSTCP\0000)

I use dial-up and have no networks of any kind. Each time I open
Network in the Control Panel, a msg jumps up saying "Your network
in not complete. Do you want to continue".

I OK the msg and in the network configuration box I have
four icon listings.

Dial-Up Adapter [I use dial-up]
SIS 900 PCI Fast Ethernet Adapter
TCP/IP - Dialup Adapter
TCP/IP - SIS 900 PCI Fast Ethernet Adapter

I think the two SIS items are in case I want to use cable someday.
Are these entries causing the 24 second delay when I boot up or
is there another area I should be looking?

My other computer has a similar situation but only an 11 sec delay.

15:49:36 11.11 Starting TCP/IP (NETWORK\MSTCP\0001)

Network configuration box with about eight icon listings.

Is there a 'reversible' change I can make to eliminate the delay
without losing the future potential for a cable connection? Assuming
this has anything to do with it.

BoB

BoB wrote in message ...
I find this line in the BLA log list of delays,

15:51:11 24.28 Starting TCP/IP (NETWORK\MSTCP\0000)

I use dial-up and have no networks of any kind. Each time I open
Network in the Control Panel, a msg jumps up saying "Your network
in not complete. Do you want to continue".

I OK the msg and in the network configuration box I have
four icon listings.

Dial-Up Adapter [I use dial-up]
SIS 900 PCI Fast Ethernet Adapter
TCP/IP - Dialup Adapter
TCP/IP - SIS 900 PCI Fast Ethernet Adapter

I think the two SIS items are in case I want to use cable someday.
Are these entries causing the 24 second delay when I boot up or
is there another area I should be looking?

My other computer has a similar situation but only an 11 sec delay.

15:49:36 11.11 Starting TCP/IP (NETWORK\MSTCP\0001)

Network configuration box with about eight icon listings.

Is there a 'reversible' change I can make to eliminate the delay
without losing the future potential for a cable connection? Assuming
this has anything to do with it.

BoB


http://groups.google.com/groups?selm...GP10.phx.gb l

On Thu, 24 Jun 2004 18:14:14 -0400, "Richard G. Harper"
wrote:

You've pretty much hit the nail on the head here, I think. The TCP/IP -
SIS network adapter entry is most likely causing your problem. If you have
your Windows 98 CD or the Windows Setup files on your hard drive (look for
several dozen files whose names all start with WIN98 and end in CAB) you can
remove the binding to the SIS network adapter for now, then reinstall it
when you need it.

Thanks Richard,

I appreciate confirmation prior to implementation.
Kinda like measure twice, cut once. :-)

BoB

On Thu, 24 Jun 2004 22:45:31 -0400, "glee"
wrote:

When I ran across this on another machine that was not connected to any networks and
whose NIC was configured to obtain an IP address automatically, what worked for me,
IIRC, was assigning the NIC a static IP address so that it did not try to contact a
DHCP server at startup:
192.168.0.1 (or actually 192.168.0.2 may be better), subnet mask 255.255.255.0

Thanks Glen,

I'll make a note of that.

BoB

On Fri, 25 Jun 2004 10:46:28 -0700, "Hugh Candlin" wrote:


BoB wrote in message ...
I find this line in the BLA log list of delays,

15:51:11 24.28 Starting TCP/IP (NETWORK\MSTCP\0000)

SNIP

BoB

http://groups.google.com/groups?selm...GP10.phx.gb l


Thanks Hugh. You, Richard and Glee all hit the nail on the head.
The reference was very easy to follow and now to make a note on
how to undo it, when I get cable.

The line now shows zero delay:

20:39:56 0.00 Starting TCP/IP (NETWORK\MSTCP\0000)

Now to put that extra 24 seconds everyday to good use. :-)

BoB

Excellent news! Thanks for letting us know.

"BoB" wrote in message
...
On Fri, 25 Jun 2004 10:46:28 -0700, "Hugh Candlin" wrote:


BoB wrote in message
...
I find this line in the BLA log list of delays,

15:51:11 24.28 Starting TCP/IP (NETWORK\MSTCP\0000)

SNIP

BoB


http://groups.google.com/groups?selm...FTNGP10.phx.gb
l


Thanks Hugh. You, Richard and Glee all hit the nail on the head.
The reference was very easy to follow and now to make a note on
how to undo it, when I get cable.

The line now shows zero delay:

20:39:56 0.00 Starting TCP/IP (NETWORK\MSTCP\0000)

Now to put that extra 24 seconds everyday to good use. :-)

BoB

"BoB" wrote in message
...
On Fri, 25 Jun 2004 10:46:28 -0700, "Hugh Candlin" wrote:


BoB wrote in message
...
I find this line in the BLA log list of delays,

15:51:11 24.28 Starting TCP/IP (NETWORK\MSTCP\0000)

SNIP

BoB

http://groups.google.com/groups?selm...GP10.phx.gb l


Thanks Hugh. You, Richard and Glee all hit the nail on the head.
The reference was very easy to follow and now to make a note on
how to undo it, when I get cable.

The line now shows zero delay:

20:39:56 0.00 Starting TCP/IP (NETWORK\MSTCP\0000)

Now to put that extra 24 seconds everyday to good use. :-)

BoB

I believe if you use 192.168.0.2 instead of 192.168.0.1, you may avoid the need to
change anything later. Glad you have added 24 seconds to each day!
--
Glen Ventura, MS MVP W95/98 Systems
http://dts-l.org/goodpost.htm

On Sat, 26 Jun 2004 22:44:05 -0400, "glee"
wrote:

"BoB" wrote in message
.. .

SNIP

Thanks Hugh. You, Richard and Glee all hit the nail on the head.
The reference was very easy to follow and now to make a note on
how to undo it, when I get cable.

The line now shows zero delay:

20:39:56 0.00 Starting TCP/IP (NETWORK\MSTCP\0000)

Now to put that extra 24 seconds everyday to good use. :-)

BoB

I believe if you use 192.168.0.2 instead of 192.168.0.1, you may
avoid the need to change anything later. Glad you have added 24
seconds to each day!

I noticed that in your first comment and changed to 0.2. For my
notes, what is the gist of 'avoid the need to change anything later',
please.

BoB