If you do not want to reinstall, and you do NOT have a windows\system directory (since you did not do an OS upgrade, but a clean install, correct?) I would search the registry for any references to MCW32 in c:\windows\system and THINK ABOUT (CAREFULLY!) changing it to c:\winnt\system32 for 32bit dlls or \winnt\system for the 16bit dlls. Or, you could create the directory windows\system and copy the mcw32.dll file to it and see if it works. That is the SAFEST route to go. What program is looking for it to be there? That is the problem program. Either the registry entry or .ini file is not correct. If it is a 32bit app, it should look for it in the \winnt\system32 directory. Is it possible you installed a 16bit communications app on your new os by mistake?
Tracy

>No, I am not. Never heard of it.
>
>
>>Are you running Sentinel 32 by any chance?
>>Tracy
>>
>>>I am the Win2K "guinea pig" for my company in testing out my development environment on the company-standard Win2K setup. When I attempt to run my application in the debugger, I'm getting the following error:
>>>
>>>Error: Unable to load MCW32.DLL
>>>Result: Comm Tools library not loading
>>>Remedy: Place MCW32.DLL in \WINDOWS\SYSTEM
>>>
>>>With my new operating system, I no longer have the \WINDOWS\SYSTEM directory.
>>>
>>>I develop in both VFP 5 and 6 and have been using VSS 6.0 rather successfully on my Win98 client.
>>>
>>>Is there a VSS and/or VFP upgrade I need to run in order for it to work on my new operating system?
>>>
>>>Thanks in advance for your help,
>>>
>>>Joe