If you have ever done any software development under Microsoft Windows you have
probably come across this famous error message:
"System.IO.FileNotFoundException : Could not load file or assembly 'Acme.dll'
or one of its dependencies. The specified module could not be found."
Modern software makes heavy use of dynamic link libraries, and the problem
with this kind of libraries is that for various reasons they might not be
there when you need them, resulting in runtime errors. This is the runtime
error you get under Windows when this happens.
Naturally, when you see this message, the first thing to do is to check
whether Acme.dll is there, and what you usually discover is that the file is
indeed there. When dealing with computers, most error messages that you come across tend to
leave some room for troubleshooting, but when the system is reporting that a
certain file does not exist on your very own filesystem, while the file is
most certainly there, the situation seems really hopeless. You are stymied.