At 12:12 AM 10/3/01 -0400, [EMAIL PROTECTED] wrote the following: >Everytime I get to the windows desktop a screen pops up stating Windows >Netwoking,unable to load dynamic links library one or more files are missing >or corrupt...x drive.I got rid of x drive a long time ago as I bought a >portable hard drive from buslink.I have no idea what this "dynamic link >library" is,I would like to get rid of this screen,everytime I get to the >desktop ..it's there.I have windows 98,with an 64 bytes of ram. >Do I need to go into the registry to fix this? Thanks for all the help you've >given so many :) [EMAIL PROTECTED]
A search for a DLL will proceed in the following fashion: ...directory containing the executable program ...current working directory ...registry entry Path in \\HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Current Version\App Paths\<executable name> ...PATH environment variable set via Windows2000/NT ControlPanel or Windows 95/98 AUTOEXEC.BAT So some program is being started and that program is looking for the DLL. The best method of tracking down the problem program is to use the System Configuration Utility (msconfig from Start -- Run) and selectively load items at startup. You do this with a clean startup and then load items one at a time until you get to the offending one. Select Diagnostic startup to create a clean environment for testing, then clcik OK to restart the computer. The Win 98 startup menu appears. Select step-by-step from the menu options and choose to process all BUT the AUTOEXEC.BAT and CONFIG.SYS files. If, while bypassing these files, the system hangs, restart the computer and process them line by line. Determine if the problem is eliminated in the clean environment. If so, a process of elimination can be employed to identify the source using Selective startup. If the problem didn't disappear, then follow these steps: ...advanced setting button, one-by-one ...Click on View and look at device manager (Yellow exclamation marks or red "x") ...A file is missing or corrupt (use SFC -- System File Checker) ...Registry is corrupted, Resrore a backup copy) ...Vir*s ...Bad hardware settings, Check CMOS ...Bad upgrade of previous Windows configuration Assuming it's not one of the above, the next step is to use selective startup and process these files one-by-one. You should now have identified the problem in one of these files. So we now must idientify the actual line that cause the problem. You do this by selecting the appropriate tab (lets say the file was the config.sys) You now process the file line by line until the problem goes away. There is more to this but you can use the help button to get the details. -- Gerry Boyd ============= PCWorks Mailing List ================= Don't see your post? Check our posting guidelines & make sure you've followed proper posting procedures, http://pcworkers.com/rules.htm Contact list owner <[EMAIL PROTECTED]> Unsubscribing and other changes: http://pcworkers.com =====================================================
