[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference noted::windows95

Title:Microsoft Windows 95 ("Chicago")
Notice:Please read topics 1 to 22 before writing anything
Moderator:EEMELI::BACKSTROM
Created:Sun Nov 13 1994
Last Modified:Fri Jun 06 1997
Last Successful Update:Fri Jun 06 1997
Number of topics:2958
Total number of notes:19968

2951.0. "PC hang / freeze as modem hangs-up" by FIEVEL::FILGATE (Bruce Filgate SHR3-2/W4 237-6452) Tue Jun 03 1997 11:31

 Having my PC require a reboot when disconecting from dial-up
 connections, both DEC and AT&T, I went looking for others folks
 with the same problem.

 In several places around the web, references were made to an `MS
 problem' that causes such a system freeze.  In all the cases that 
 I checked relative to windows 95, the operation of Netbios over
 TCP was listed as the cause, the recommended solution was to
 locate the vnbt.386 file, rename it, then reboot.

 While I don't know if this fixes all cases, I do know that the
 two machines that used to freeze when disconecting from the
 dial-up network now work fine.

 No where did I find an MS reference that referenced problem.

 It was pointed out in one reference that Lotus Notes may use LAN0
 on TCP, and that removing vnbt.386 will also remove the TCP
 access to LAN0.  I did not see any other references to `downsides'.

 While OSR2 shows that netbios support is checked in my tcp/network
 configurations, that box is disabled (grayed out) in the machines
 I looked at.  It is probably this reason that removing the file
 was recommended vs disabling the netbios in TCP.

 Bruce
T.RTitleUserPersonal
Name
DateLines
2951.1REOSV4::grantt.reo.dec.com::TaylorgrTue Jun 03 1997 11:4210
re-1

I get this hang sometimes when I disconnect from both my ISP's.
I've had the same problem with Win95 with and without the
Service pack and I have the same problem now after installing 
a new system with OSR2.

When the system hangs I have to hit RESET to restart my system.

Grant
2951.2so did deleting/renaming vnbt.386 fix the problem? break anything else?FIEVEL::FILGATEBruce Filgate SHR3-2/W4 237-6452Tue Jun 03 1997 13:570
2951.3REOSV4::grantt.reo.dec.com::TaylorgrWed Jun 04 1997 05:006
re-1

I have not tried that yet.  I have been lucky for the last
few days that my system has not hung when disconnecting.

Grant
2951.4MARVIN::GOODWINPete GoodwinWed Jun 04 1997 10:038
    Interesting... since I upgraded my WINSOCK and Dial Up Networking to
    the new ISDN support, a lot of the hanging on disconnect seems to have
    disappeared.
    
    I don't use ISDN - however it does upgrade WINSOCK and DUN. Seems to
    work ok for me.
    
    Pete
2951.5REOSV4::grantt.reo.dec.com::TaylorgrWed Jun 04 1997 11:118
re-1

I have had the problem with the ISDN Support installed.
I'm now running with OEM Service Release 2 from
the MSDN subscription.

Grant

2951.6Found the first machine that will not work with the hack in .0FIEVEL::FILGATEBruce Filgate SHR3-2/W4 237-6452Wed Jun 04 1997 21:3318
 My Samsung notebook will not recover from suspend w/o the vbnt.386 file
 available.  With the file removed, a restore from suspend results in
 the blue death screen and VXD fault with a serial port.

 The Samsung and Dell notebooks use the same Phoenix bios and disk
 suspend firmware, so I would expect the Dell to  have a similar problem.
 And I think we also sell a rebadged Dell.

 It is probably time to do a more sophisticated hack here.  If the
 netbios running over tcp is really the cause of the freeze, and
 there is grayed out configuration box with a check in it for netbiox,
 then there must be a means of manipulating the check somehow!
 Ideas?

 Which is newer, the ISDN patch or osr2 (August 24, 1996)?

 Bruce