Vnetsup.vxd, vredir.vxd, dfs.vxd, and userver.vxd along with msnp32.dll are coming up in bootup with the following message, "unable to load dynamic link library, and reinstall the appllication." This sounds like network stuff. I'm not on a network, (Internet perhaps) please tell me how to get rid of these messages which appear each time I boot.... Many thanks

from safe mode go to add\remove programs and uninstall IE4. When you reboot you will probably get the same message again, not to worry. go back into safe mode and go to control panel\networking and remove all adapters, protocols, and services. That'll do it. Now reinstall IE4 from a good copy.

here is some info that fixed the error message on my computer. We dont even need the file! you can find this info at the "stump jeff" section of zdnet.com... http://www.zdnet.com/zdhelp/tip_help/stump041598.html Click the link at the botton of this e-mail to go there -------------------------------------------- Here is what the article said... -------------------------------------------- PBorgman wrote: Recently I was installing CompuServe on a brand new machine. At one point the installation prompted me to insert the Windows 95 CD-ROM but I didn't have it handy, so I interrupted the installation process. In spite of taking this step, there was on the desktop a shortcut to CompuServe, and clicking that shortcut launched what looked like the normal CompuServe startup screen. I didn't worry, figuring the files the installer needed must have been on the hard drive. But when I rebooted the machine I got 10 error messages, each with the same theme: "The Registry contains a reference to a file but Windows cannot find that file, so certain applications and functions will be unavailable. Press a key to continue." The files were: vnetsup.vxd, nwlink.vxd, nwredir.vxd, nscl.vxd, vredir.vxd, ndis.vxd, ndis2sup.vxd, vnetbios.vxd, nwnp32.dll, and msnp32.dll. Jeff's Answer I knew what happened as soon as I read that you interrupted CompuServe's installation. Interrupting the installation of online services such as CompuServe or Microsoft Network causes the same kinds of errors. The reason is that the installer can add items to the Registry, including references to DLLs and other files, before actually copying those files to the hard drive. Interrupting the installation doesn't undo those changes, and uninstalling the application doesn't always make them go away, either. Here's what I recommend. Uninstall CompuServe using Control Panel's Add/Remove Programs. Then edit the Registry and delete every reference to the files mentioned in the Registry. Then you can re-install CompuServe and everything should work just fine. I realize editing the Registry can be a little scary, but this should be a no-brainer. From the Start menu, choose Run, and enter REGEDIT. This launches the Registry Editor with the My Computer icon selected at the top. Choose Find from the Edit menu, enter the name of the first file mentioned in the error message (in lower-case letters), and click the Find Next button. When you do, a "searching the Registry" style message appears. If a match is found, that object will be highlighted in the right-hand pane of the Registry Editor window. Press [Delete] to delete that item, confirm the deletion, and then press [F3] to continue searching for the next occurrence of the filename in question. Every time you find an occurrence of the filename, press [Delete] and confirm it. When there are no more occurrences of that filename left, you're ready to search for the next filename. The key is to start each new search from the top of the Registry structure. To start at the top, you use the mouse to re-select the My Computer icon in the left-hand pane of the Registry Editor window. After deleting all occurrences of the files mentioned in the error messages, close the Registry Editor and reboot the machine. All the nasty error messages should be gone and you can re-install CompuServe. The moral of the story: never interrupt an installation program if you can possibly help it. If, when you start your machine, you're getting bizarre error messages about missing files, you may be able to eliminate those errors by editing the Registry as described in this article. A lot of people are understandably leery of editing the Registry. In this case, all you do is search for a filename, press the [Delete] key, and search some more. You don't add anything new, and you don't delete anything that isn't "found" when you search for missing filenames. Looking for more Windows 95 tips? Request a free issue of ZD Journals' Inside Windows 95.

I did that, and did not work