When first starting the software if you get an error message "missing MFC250.DLL" or "Invalid
Dynalink" or "Could not find xxx.EXE or one of it's
components..." please do the following:
"missing MFC250.DLL" error message >> On some PC's when starting the software for the first time you may get the error message "missing
MFC250.DLL". If so then:
1) Click the link below to download the zip file that contains MFC250.DLL :
www.UniSOFT-cim/download/mfc250.zip
2a) For Windows 3.x, 95, 98 or ME operating systems unzip the contents of the MFC250.ZIP file, MFC250.DLL to the \windows\system
directory then start the software again and it should be ok.
2b) For Windows NT or 2000 operating systems unzip the contents of the MFC250.ZIP file, MFC250.DLL to the
\winnt\system directory then start the software again and it should be ok.
"Invalid Dynalink" error message >> If you get the message "Invalid
Dynalink" when starting the software for the first time then the MFC250.DLL version is incorrect.
If so then:
1) Click the link below to download the zip file that contains MFC250.DLL :
www.UniSOFT-cim/download/mfc250.zip
2a) For Windows 3.x, 95, 98 or ME operating systems unzip the contents of the MFC250.ZIP file, MFC250.DLL to the \windows\system
directory then start the software again and it should be ok.
2b) For Windows NT or 2000 operating systems unzip the contents of the MFC250.ZIP file, MFC250.DLL to the
\winnt\system directory then start the software again and it should be ok.
"Could not find XXX.EXE or one of it's
components..." >> If you get the message "Could not
find XXX.EXE or one of it's components..." If so then:
1) Click the link below to download the zip file that contains MFC250.DLL :
www.UniSOFT-cim/download/mfc250.zip
2a) For Windows 3.x, 95, 98 or ME operating systems unzip the contents of the MFC250.ZIP file, MFC250.DLL to the \windows\system
directory then start the software again and it should be ok.
2b) For Windows NT or 2000 operating systems unzip the contents of the MFC250.ZIP file, MFC250.DLL to the
\winnt\system directory then start the software again and it should be ok.