MISSING FILES ON BOOT ON A *NON-NETWORKED* SYSTEM

(systems that have a cable modem that works through an Ethernet card are networked)

 

 

Most of these files will be referred to after this statement on boot:

"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 the device no longer exists.  If you deleted this file on purpose, try uninstalling the associated application using its uninstall program or setup program.  If you still want to use the application associated with this device file, try reinstalling that application to replace the missing file."

 

TRY THIS FIX FIRST

Hit enter on each error to get to windows

Once in windows click

START > SETTINGS> CONTROL PANEL > ADD REMOVE PROGRAMS> WINDOWS SETUP

Then uncheck

COMMUNICATION

Hit APPLY and OK

REBOOT the computer

And once back in windows click

START > SETTINGS> CONTROL PANEL > ADD REMOVE PROGRAMS> WINDOWS SETUP

Then “check” COMMUNICATION

Hit APPLY and OK

(you may need the windows 98 CD  or direct it to look at C Windows Options Cabs)

REBOOT the computer

If this fails to fix the problem follow the instructions below

 

The fix is to uninstall or install a driver or program (usually network-related), comment out one or more lines in SYSTEM.INI, or remove a Registry reference.

 

1.  If MSNP32.DLL, VREDIR.VXD, or VNETBIOS.VXD are missing, go into Network Properties (Control Panel / Network or right-click Network Neighborhood and click Properties).  If "Client for Microsoft Networks" is on the list, left-click it and the Remove button.  Otherwise, click Add / Client / Add, click Microsoft on the Manufacturers list and Client for Microsoft Networks on the Models list, then click OK / OK and reboot.  If one or more of these is still missing on boot, go back into Network Properties and remove Client for Microsoft Networks.

 

2.  If MSNP32.DLL is still missing after Step 1 above, uninstall and reinstall Dial-Up Networking (Control Panel / Add/Remove Programs / Windows Setup tab / Communications / Details).

 

3.  If NWLINK.VXD, NWREDIR.VXD, NSCL.VXD, or NWNP32.DLL are missing, go into Network Properties and uninstall or install/uninstall Client for Netware Networks as you did for Client for Microsoft Networks in Step 1 above.  If any of these files are still missing, go to Step 4.

 

4.  If NDIS.VXD or NDIS2SUP.VXD is missing, go into Network Properties.  If there is any other network adapter than AOL Adapter or Dial-Up Adapter, left-click on it and click the Remove button.  If this doesn't help, go into Network Properties, click Add / Adapter / Add, click Detected Network Driver on the Manufacturers list and Existing NDIS2 Driver on the Models list, and click OK.  If you are prompted for computer and workgroup names, type in something for each (ignore Description).  Click OK or Close until prompted to restart, then restart.  Go into Network Properties again, remove the network adapter, and reboot.  If nothing in this step helps, go to Step 3.  This step should also work for VNETSUP.VXD.

 

5.  If VSERVER.VXD is missing, go to Network Properties.  If "File and print sharing for Microsoft Networks" is on the list, left-click it and click the Remove button.  If not, click Add / Services / Add, click Microsoft on the Manufacturers list and "File and print sharing for Microsoft Networks" on the Models list, click OK / OK, and reboot.  Go into Network Properties again, remove file/print sharing, and reboot.

 

6.  If NWSERVER.VXD is missing, proceed as in Step 5 except you add and/or remove "File and print sharing for Netware Networks".  NOTE:  You can have either Microsoft sharing or Netware sharing installed, not both.

 

7.  If VNETSUP.VXD or DFS.VXD are missing:

    a.  If other files listed above are missing, troubleshoot these problems first.

    b.  If one or both files are still missing, open REGEDIT, go to the left side, left-click the pluses in front of HKEY_LOCAL_MACHINE, System, CurrentControlSet, Services, and VxD, double-click either the DFS or VNETSUP folder, go to the right side, delete the StaticVxD value, close REGEDIT, and reboot.  If both are missing, delete the StaticVxD value in each folder before closing REGEDIT.  Just removing the DFS or VNETSUP key (folder) may also work.

 

8.  See TechNet Articles Q137454 and Q140010 for more information.

 

9.  If other files are missing on the boot, search SYSTEM.INI for references and put a semicolon in front of the "offending" line(s), then search the Registry, back up any key where a reference is found, and delete the key or the StaticVxD value in it.  However, if TURBOVBF.VXD or TURBOVCD.VXD can't be found this normally indicates a modem problem, usually with the driver install.