Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows VistaWindows XPWindows MeWindows 98Windows 95Virtual PCInternet ExplorerOutlook ExpressWindows MediaSecurity
Related Topics
MS Server ProductsMS OfficePC HardwareMore Topics ...

Windows Forum / Windows 98 / Setup / June 2006

Tip: Looking for answers? Try searching our database.

Win98SE Installation problems (Win2k dual boot)

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
computerguy - 06 Jun 2006 20:37 GMT
Hi,

I just added Win98SE to my Win2k system in a dual boot configuration. Win2k
still works which is good since that is my primary system. The basic Win98SE
works except for the network. During installation I got the usual "Unknown
Device" errors, most of which were fixed when I installed the motherboard
(Intel)drivers. After some initial issues installing the on-board Ethernet
driver I was able to install it and the "?" no longer appears in the Device
Manager screen. However, during boot up there is an error message about
missing files such as
vnetbios.vxd
vredir.vxd
msnp32.dll
as well as problems with Microsoft Network.

How do I reinstall the Microsoft Network part of Win98SE to clear up these
errors?

Also, will this affect the Win2k installation?

TIA,
-GB
Ron Badour - 06 Jun 2006 22:37 GMT
See if this article helps:  http://support.microsoft.com/?kbid=166832

Signature

Regards

Ron Badour, MS MVP for W98
Tips:  http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo

> Hi,
>
[quoted text clipped - 21 lines]
> TIA,
> -GB
computerguy - 06 Jun 2006 23:51 GMT
Hi Ron,

Your suggestion helped, but not completely! I can now browse the web but I
still get the error messages at startup (missing vnetbios.vxd, vredir.vxd,
dfs.vxd as well as the msnp32.dll error dialog box). Also, the system is
unstable. It often reboots after I close IE. It also sometimes hangs on
reboot after the missing dfs.vxd message.

Do yo have any further suggestions?

TIA,
GB

> See if this article helps:  http://support.microsoft.com/?kbid=166832
> > Hi,
[quoted text clipped - 22 lines]
> > TIA,
> > -GB
computerguy - 07 Jun 2006 01:09 GMT
Hi,

As a followup, I used System File Checker to restore the 3 missing ".vxd"
files and now I do not get the error message.

I tried restoring msnp32.dll to the Windows\System directory but that did
not get rid of the error box, probably because destination folder was
incorrect.

Any further help would be greatly appreciated.

TIA,
-GB

> See if this article helps:  http://support.microsoft.com/?kbid=166832
>
[quoted text clipped - 23 lines]
> > TIA,
> > -GB
Ron Badour - 07 Jun 2006 02:29 GMT
The system folder should be the correct destination.

This article discusses the error message still appearing after extracting
the file:

http://support.microsoft.com/?kbid=243431

Also check out:  http://support.microsoft.com/?kbid=302590

Signature

Regards

Ron Badour, MS MVP for W98
Tips:  http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo

> Hi,
>
[quoted text clipped - 41 lines]
>> > TIA,
>> > -GB
computerguy - 07 Jun 2006 02:52 GMT
Hi Ron,

Your last suggestions seemed to have done the trick. Removing and
reinstalling "Client for Microsoft Networks" appears to have solved it.

Thanks a lot,
-GB

> The system folder should be the correct destination.
>
[quoted text clipped - 50 lines]
> >> > TIA,
> >> > -GB
Ron Badour - 07 Jun 2006 02:56 GMT
My pleasure--thanks for the feedback.

Signature

Regards

Ron Badour, MS MVP for W98
Tips:  http://home.satx.rr.com/badour
Knowledge Base Info:
http://support.microsoft.com/default.aspx?pr=kbinfo

> Hi Ron,
>
[quoted text clipped - 62 lines]
>> >> > TIA,
>> >> > -GB
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.