Unsolved
This post is more than 5 years old
6 Posts
0
1759
January 12th, 2005 20:00
Help! Can't reinstall Win98SE - keeps getting BSOD after reinstall
Hello all,
To make a long story short, five days ago I updated (or TRIED to update) Aventail Connect software on my Dimension 4100. This apparently hosed my TCP/IP stack (modem worked O.K. and connected and did some handshaking, but NO data transfer). Finally reinstalled Win98SE - first from the C:\Windows\Options\CABS\setup.exe program, but TCP/IP was still hosed. Then tried deleting DUN and Win98SE became unstable. Have tried reinstalls from both CABS and the recovery CD, but now I get the following BSOD when trying to start the reinstall:
Invalid VxD dynamic link call from NWREDIR(04) + 000000D0 to device "0487", service 6. Your Windows configuration is invalid. Run the Windows Setup program to correct this problem.
(I HAVE - and still get the problem!.) After exiting the BSOD, I get on a plain screen:
While initializing device NWREDIR invalid VxD dynamic link call to device number 487, service 74. Your Windows configuration is invalid...
I can sometimes coax the system into Safe Mode. I've tried bringing Windows up in step-by-step mode and among other things I see the two Symantec VXDs and one Aventail VXD load, so I wonder if one of these is the problems (I'd gotten a funny error message that might have come from Symantec before trying the reinstall) the last thing that starts is msmouse.vxd, THEN I get the BSOD again.
This is a major nuisance to say the least - any assistance appreciated.
Thanks,
Evan
To make a long story short, five days ago I updated (or TRIED to update) Aventail Connect software on my Dimension 4100. This apparently hosed my TCP/IP stack (modem worked O.K. and connected and did some handshaking, but NO data transfer). Finally reinstalled Win98SE - first from the C:\Windows\Options\CABS\setup.exe program, but TCP/IP was still hosed. Then tried deleting DUN and Win98SE became unstable. Have tried reinstalls from both CABS and the recovery CD, but now I get the following BSOD when trying to start the reinstall:
Invalid VxD dynamic link call from NWREDIR(04) + 000000D0 to device "0487", service 6. Your Windows configuration is invalid. Run the Windows Setup program to correct this problem.
(I HAVE - and still get the problem!.) After exiting the BSOD, I get on a plain screen:
While initializing device NWREDIR invalid VxD dynamic link call to device number 487, service 74. Your Windows configuration is invalid...
I can sometimes coax the system into Safe Mode. I've tried bringing Windows up in step-by-step mode and among other things I see the two Symantec VXDs and one Aventail VXD load, so I wonder if one of these is the problems (I'd gotten a funny error message that might have come from Symantec before trying the reinstall) the last thing that starts is msmouse.vxd, THEN I get the BSOD again.
This is a major nuisance to say the least - any assistance appreciated.
Thanks,
Evan
0 events found
No Events found!
Denny Denham
2 Intern
•
18.8K Posts
0
January 12th, 2005 21:00
Did you do a clean install of Win98 SE following a format of the hard drive? Windows 98 does not respond well to a dirty install, usually exhibiting instability.
erobatino
6 Posts
0
January 12th, 2005 23:00
No, I didn't reformat the HD because I was hoping to avoid losing my data (I have a ZIP drive backup of the most crucial stuff, but NOT absolutely everything on the drive). I'd like to avoid reformatting the HD except as a last resort. Seems to me that there's some file(s) blocking a clean reinstall; perhaps deleting those would resolve the problem?
Thanks for the quick response,
Evan
erobatino
6 Posts
0
January 14th, 2005 12:00
http://support.microsoft.com/default.aspx?scid=kb;en-us;302589
Essentially, I followed Method 1 except that I installed "Client for Microsoft Networks" instead of "Client for Netware Networks" plus TCP/IP. The system instability had been caused by my having NO networking installed at all. Getting into Safe Mode and reinstalling at least a few basic network components cured the problem. I now have to reinstall the original video drivers (my display is a bit grainy right now) and fix a few other things, but I'm back up now (just have to figure out how to install Aventail SAFELY now - probably need to stop Symantec AntiVirus first, or something of that nature).