PCBUILD Archives

Personal Computer Hardware discussion List

PCBUILD@LISTSERV.ICORS.ORG

Options: Use Forum View

Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Dennis Thiel <[log in to unmask]>
Reply To:
PCBUILD - Personal Computer Hardware discussion List <[log in to unmask]>
Date:
Mon, 12 Oct 1998 22:55:54 -0400
Content-Type:
text/plain
Parts/Attachments:
text/plain (28 lines)
I had this problem also, and with the help of the bootlog analyzer (BA)
program that someone suggested, I was able to track down the problem. My
computer was choking on a driver called vnbt.386, taking 24 seconds to load
just that driver, according to BA. The Win 98 Resource Kit has a utility
called Microsoft File Information that shows detailed information on system
files, and it says vnbt.386 is "Microsoft 32-bit Windows 98 virtual TCP/IP
on NetBIOS (NBT) device driver file."

So I went into my Network properties and removed the TCP/IP protocol from my
ne2000 network adapter, since I don't use TCP/IP on my network at home. When
I rebooted, it still loaded vnbt.386, but it didn't choke on it...I chopped
approximately 24 seconds off my boot-up time.

I don't remember who originally posted this problem but give the BA program
a try...without it I never would have known which driver was causing the
problem.

I don't remember who suggested the BA program either, because I deleted the
messages, but thank you for pointing me in the right direction.

Hope this helps,

Dennis Thiel

                                  -----
                PCBUILD mailing list -  http://nospin.com
         Bob Wright:[log in to unmask] - Drew Dunn:[log in to unmask]

ATOM RSS1 RSS2