>>>>Fred,
>>>>
>>>>>I really don't know where MSVCRT.DLL comes from, if it's part of the OS or not. All I know is FOXTOOLS.FLL shows it needs it if you use the Visual Studio tool DEPENDS.EXE on it. Certainly a better error message could be provided than what you get when you have a "missing piece" of the Windows jig-saw puzzle!
>>>>
>>>>According to the knowledgebase it is a c++ runtime library used for programs or DLL written in Visual C++ 4.2.
>>>>
>>>>Walter,
>>>
>>>I knew what it was, I just have no clue as to where it comes from. There are also usually many different versions of this file:
>>>
>>>MSVCRT.DLL
>>>MSVCRT10.DLL
>>>MSVCRT20.DLL
>>>MSVCRT40.DLL
>>>etc.
>>>
>>
>>Fred, these aren't versions; they actually implement different sections of the runtime environment referenced by the C++ compiler.
>>
>>>I also notice I have several different versions (date/size different) of these files on my system in various folders. Welcome to DLL HELL!
>
>Thanks for the clarification, Ed. I didn't think it really was "versions", but I guess a different term there would have been better used. Have you worked with W2K enough to know if their "solution" to DLL HELL works? I've not played with W2K yet, I've just heard it's supposed to be tons better in that regard.