Browse DevX
Sign up for e-mail newsletters from DevX

Tip of the Day
Language: Visual Basic
Expertise: Beginner
Aug 6, 1997



Building the Right Environment to Support AI, Machine Learning and Deep Learning

Searching For 16-Bit DLLs in Windows 95

Windows 95 uses an extra step when searching for 16-bit DLLs. A new registry key, "Known16DLLs," in Windows 95 under \\HKEY_LOCAL_MACHINE\System\CurrentControlSet\Con-trol\SessionManager functions in a similar way to KnownDLLs in Windows NT. Known16DLLs contains numerous subkeys, named after 16-bit DLLs, whose value is the name plus the DLL extension. If a 16-bit DLL is in this list, Windows 95 will first check the Windows\System directory for the 16-bit DLL and load it if it finds it. If the DLL is not in the Windows\System directory, a normal search (CurDir, windows, system, path) begins. Windows 95 puts a subkey for a 16-bit DLL in Known16DLLs the first time it loads it from Windows\System. But it won't remove the subkey should the 16-bit DLL be no longer found in the Windows\System directory. To summarize, when a 16-bit DLL is loaded from the Windows\System directory it goes into this list. Whenever an attempt is made to load it in the future, Win95 will see it in the list and will search Windows\System directory first. The only way to ensure the expected search for this 16-bit DLL is to remove the relevant subkey of Known16DLLs if it exists. Special thanks to Oliver Hodgkins, Microsoft Customer Support, England.
A. Nicklas
Comment and Contribute






(Maximum characters: 1200). You have 1200 characters left.



Thanks for your registration, follow us on our social networks to keep up-to-date