vnetbios.vxd error

[Aero]

I just reloaded Win98SE in one of my systems but it's giving me this error on boot-up.

Cannot find a device file that may be needed to run Windows or a Windows application.
The Windows registry or SYSTEM.INI file refers to this device file, but it no longer exists.
Try uninstalling the associated application or reinstall that application to replace the missing file.

What is causing this error?
Can I just transfer this file from one of my other systems to replace it?

Currently the only hardware I've got installed is the video card.

Any help is appreciated!

http://support.microsoft.com/default...EN-US;q166832&

its weird tho cause you say you only have video installed. do you have any onboard hardware?

[vass0922]

uninstall and reinstall dial up networking
I used to get nailed with that awhile ago too

[Aero]

Thanks, GZ

Nope, no onboard sound or anything like that- it's an Asus P5a-b mobo.

Quote from that MS support article:
----------------------------
This problem can occur if you install Dial-Up Networking, Dial-Up Adapter, or Virtual Private Networking and then cancel Setup while the Copying Files dialog box is displayed. The Dial-Up Networking files are not copied to the hard disk but the file names are added to the registry. When the computer is restarted, the files are requested and cannot be found.
----------------------------

This could be the problem, because at first the dial-up adapter showed a yellow "!" in the device manager- but after reboot it appeared to fine. I didn't see the dial-up adapter installing, nor did I cancel Setup.

I found a possible solution below on Google but I'd rather not go mucking about in the registry if I can help it.

There is a way to fix this problem, which is caused by a program, even the windows98 setup gimping out during the install, but not before adding the definition (data) "vnetbios.vxd" to Static VxD (name).
READ TO THE END BEFORE ATTEMPTING - it's easy, but there are implications!

The quick, easy, and **if you're careful** perfect solution is to manually edit the windows registry to take out the offending line. I've done this at least 5 times with perfect success. Note: DO NOT do this unless you are ready to LOSE EVERYTHING (i.e. at very least, backup you data and be prepared for a reinstall). Every computer is a little different so while you're hoping for the best, plan for the worst.
1) at the windows start button, choose run and type 'regedit'
2) very carefully and deliberately, navigate the left window, choose the following:
HKEY_LOCAL_MACHINE,
then SYSTEM,
then CurrentControlSet,
then Services,
then Vxd,
then VNETBIOS,
Once you've clicked on VNETBIOS, look at the right-hand window. You will see a few lines in the Name and Data columns, including one to the effect of "StaticVxD" and "Netbios.vxd" (both the preceeding on the same line). Carefully select that line and then hit the Delete key on the keyboard.
Then click the registry menu (top left) and exit (changes are automatic). Restart the computer and voila. If ever it doesn't work and you were going to reinstall anyways, you've wasted a whole 10 minutes!

Thanks vass, I'll give that a try...

[Aero]

Reinstalling dial up networking worked like a charm, thanks for the assistance!

Well looky there, I finally hit the 200 post mark!

[BFlurie]

Vnetbios.vxd doesn't do a dang thing unless file & printer sharing are enabled. Worse, it exposes network ports 137-139 to the internet if no firewall. If you don't need file/printer sharing, delete its Reg entry, but it will reinstall every time you go thru Network properties clicking OK.

[Aero]

I'll be running a firewall, so I should probably just leave things alone- right?

[BFlurie]

Just go to www.grc.com & test your ports. If the netbios port 139 is open, you got a security leak. My point was that M$$ networking has some glaring errors.

[jdbic]

What if you don't reinstall the dialup networking? does it have to be there ?

[BFlurie]

Depends on yer needs. If you use a dial-up modem, you do. But just plain networking (not dial-up) adds the vnetbios.vxd. A firewall should block those ports for ya.