• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Repetitive stupid question...

Cocytus

Senior member
When windows is booting, it says it cant find 3 vxd files. Then on the desktop after boot, it says it can't find msnp32.dll and that the Microsoft network is unavailable.


I get this each time the system starts.


I know, I know, I got this same message when I reinstalled it last time, but I forgot which components I need to add...

Thanks in advance....
 
Cocytus:

As far as those *.vxd files, I saw this question about a month ago:

http://forums.anandtech.com/messageview.cfm?catid=34&threadid=425485

In the same vein as that thread, you probably had program installed at one time that referenced those three files, but after uninstalling the program a registry key was never removed (or a reference to the file in the system.ini file, but that is less likely).

Run regedit, backup your registry, then to a search for each *.vxd filename. Delete those keys where this shows up (you backed up your registry, right?), and reboot. You should be fine.

If you're really worried about hosing your box, backup your data as well.... As for that *.dll that shows up, I'll try to come back tomorrow on that, I'm running late for my wife, who is pickup me up from work tonight....
 
The link for the msnp32.dll problem on the MS tech site...I followed the instructions exactly and was unable to extract any files.

I have no idea as to how to search the registry (I have reg cleaner and I toyed with it, but saw no way to search for the vxd's. I also eyeballed the regedit, and its greek to me....)

I remember that someone told me to simply install a certain component or components from the 98SE CD ROM. It worked last time. This only makes old invalid registry
entries valid, but I have no idea how to detect and remove these invalid keys.

Please be EXTREMELY DETAILED and SPECIFIC in your response. My name is spelled M-O-R-O-N.
 
You could try to reinstall windows over your current install. However there is no guarranty that would work. 🙁
If you cannot install the individual files from the CD (never worked for me in the past) then you have basically two options. You could try to reinstall windows over your current install. OR you can format your hardrive and reinstall windows from scratch.
Either way mark off a good hour or two of your time for doing this. 🙁

Do you have an actual copy of win98 2nd edition or is it a "boot cd?" A boot CD is a preinstalled copy on the CDROM. This normally comes from manufacturers such as Compaq, Gateway and such. If it is a boot CD then you have to just wipe out your harddrive and reinstall. There should be documentation on the cdrom to tell you how.
 
Cocytus:

OK, to fix the *.vxd problem, follow these steps (I'm using Win2k, so some of the menu names might be slightly different):

1. Click on Start - Run.

2. Type "regedit" in the Run dialog box and click OK.

3. The Registry Editor program opens. To back up your registry, click on Registry - Export Registry File.

4. The Export Registry File dialog box opens. Type a file name in the File name dropbox, and choose the radio button labeled All in the Export range section at the bottom of the dialog box, then click save.

5. Highlight My Computer, which should be at the very top of the tree.

6. Click on Edit - Find. The Find dialog box opens; type the file name of the first *.vxd file in the Find what textbox, then click Find Next.

7. For the first instance of the *.vxd file that regedit finds, delete the associated key by right-clicking the key (in the right window pane), and click Delete in the popup menu. Click on Edit - Find Next to find the next instance until done. This will be indicated by a dialog box which states "Finished searching through the registry.".

8. Repeat steps 5-7 for the other two *.vxd files.

Post back to let me know how that goes. Don't feel like you're a moron or something. At least you knew which forum to post in....🙂
 
Smudge, just wanted to say Thanks for your informative and professional reply. I, like the originator, am a bit new to the NT world (I'm Unix). It really saddens me to see scarcastic and possibly damaging replies (if taken seriously) to us folks that don't know as much as others, BUT are trying to learn. I KNOW I'm NT challenged, and I don't need someone else rubbing my face in it, but they do, and it sometimes makes me hesitant to posts questions (and I'm sure there are other out there with this same feeling).
Again, you are a credit to the forums, thank-you.
 
LadyTech:

You are most welcome! Actually, I learn quite a bit also just by putting procedures such as those in writing, and besides, a few years ago I wouldn't have known how to tackle the problem myself. Thank you for the kind words....
 
Your method worked perfectly on the VXD's.....and the DLL file (I like to gamble). This mother jumps up with zero "file missing" messages.

Whether or not this actually worked has no bearing on LadyTech's compliment. She is absolutely correct, and I wholeheartedly appreciate the fact that you took the time to sit down and compose that solution.

 
Back
Top