Author: Jeroen van Dorp
Date: 08:58:13 11/24/00
Go up one level in this thread
I'm not much of a Windows expert, but as I understand MFC stands for Microsoft Foundation Class (ver. 4.2) and dll for dynamic link library. For dummies like me I think it's best described by linking a program you run to the engine of Windows, the kernel (correct me experts if I'm wrong). I once read they developed the idea of dll's to save disk space. A dll is loaded into memory and used by many programs at a same time. When you have 10 or 15 (also resident)programs running, a lot of them could use mfc42.dll. With lots of disk space now available for low prices that's not that interesting anymore, but we're stuck with it. Sometimes (too often) it goes wrong. You install a new program and it uses the dll -file, promptly overwriting the old one. Proper installation programs should ask for permission, but not all do. In that case the library file is used by another program but is the wrong version or in the wrong location. Basically you could try to stick to one mfc42.dll and please the most recent version of it (look at the build, right clicking the file, and examining the version) in your windows/system directory, storing the rest for backup -if anything goes wrong. Most -not all- programs pull it then from the system directory. As there's only one version of mfc42.dll, chances of page faults and conflicts are minimized. You could try it with Fritz in any case. Good luck with the productivity tool Windows. Jeroen ;-)
This page took 0 seconds to execute
Last modified: Thu, 15 Apr 21 08:11:13 -0700
Current Computer Chess Club Forums at Talkchess. This site by Sean Mintz.