Terry Turner wrote: > During the boot process I get the following errors: > "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 file no longer exists. If you > deleted this file on purpose, try uninstalling the associated > application using its' uninstall or setup program. If you still want > to use the applications association with this device file, try > reinstalling that application to replace the missing file. > vnetsup.vxd > Press a key to continue" Many applications these days, unfortunately, install and register a number of device drivers and common DLL files just on the chance that the user might need them. Many of these you truly do NOT need, although others might. For instance, an application might decide to install VB runtime files even though you already have them. Then, another program comes along behind, sees the driver or whatever but modifies the file location, etc., etc., etc. This is why I run software which reports every change to my Registry, and why I back up my Registry before any significant install. Unplanned, unintended, and unnecessary Registry and INI file changes are perhaps one of the biggest problems with Windows - it can be positively chaotic trying to keep these vital databases clean. Since you say that your apps run properly....and I assume you mean that you have thoroughly checked very single app on your system....I think it can be assumed that you don't need whatever vxd the boot process cannot find. However, you still want to eliminate this interruption to the boot process. Here are some choices: 1. If you had uninstalled any applications before this occurred, reinstall them. 2. Check your application CDs/diskettes by running the "find" command against them to see if you can find anything that begins with "vnetsup" or "_vnetsup". It might be, for instance, "vnetsup.ex_" or something. If you find it, uninstall and then reinstall this application. Start with the application you installed last and work backward. 3. Use any Registry editor which has full search capabilities and look for this reference. If you don't find it, it may be in System.ini. There are similar editors for INI files. When found, simply delete the reference AFTER backing up whatever you are modifying (Registry or INI file). Brian Taylor PCSOFT maintains many useful files for download visit our download web page at: http://nospin.com/pc/files.html