View Full Version : "mfc42loc.dll"

01-05-2003, 02:49 PM
I am having trouble with my AutoCad programme (can't open it). Nortons Crashguard tells me:

Windows 98 Version 4.10.1998
ACAD caused an invalid page fault in
module AC1ST15.DLL at 017f:65fe1e3b.
EAX=00000000 CS=017f EIP=65fe1e3b EFLGS=00010246
EBX=bff7771a SS=0187 ESP=00e1f888 EBP=00e1fa54
ECX=00000000 DS=0187 ESI=00f403f0 FS=10bf
EDX=bff7024c ES=0187 EDI=00000001 GS=0000
Bytes at CS:EIP:
8b 10 8d 4e 04 8d 7e 14 89 11 8b 50 04 89 51 04
Stack dump:
00000001 00f404e0 00f40d50 64616f4c 7262694c 41797261 bfbebd00 c3c2c1c0 c7c6c5c4 cbcac9c8 cfcecdcc d3d2d1d0 d7d6d5d4 dbdad9d8 dfdedddc c3c2c1c0

Also "a required .dll file c:\windows\system\MFC42LOC.dll was not found"

I have had some problems with a finacial programme that I have had to uninstall and this could have taken the .dll file with it.

All help much appreciated. Keith Booth.

Graham L
01-05-2003, 03:10 PM
You are probably right. :D You need that DLL file. You obviously installed that financial programme afterAutocad, and it overwrote the one that Autocad was using.

The quickest fix might be to install that programme again, copy the mfc42loc.dll file to the Autocad programme directory, then uninstall the culprit again. (It will have replaced the file because it had a later version, and Autocad must have worked with that version. It will be smaller than Autocad, too, so quicker to install :D).

01-05-2003, 03:55 PM
Thanks, Graham, for your help. Unfortunately I am unable to re-load the financial programme due to a CD error, so I am having a running battle with the supplier. Will keep trying. KB.

Terry Porritt
01-05-2003, 04:34 PM
It's a little bit strange as mfc42loc.dll is not a "normal" part of Win98, it is a "location" file associated with using a foreign language dialogue.

Have a look here (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnvc60/html/redistribvc6.asp)

Here is an extract:

"There are several MFC DLLs supplied for various locales. For example, Mfc42deu.dll is the German version and contains version information that identifies it as German locale. If you install any locale DLL, you must ensure the locale for which the DLL is intended matches the locale of the installed Windows system. When you install the DLL, you must rename it to Mfc42loc.dll.

You should never install an Mfc42loc.dll on an English system. English resources are built into Mfc42.dll, and it is faster to load them from that DLL instead of searching (and loading) an MFC localization DLL first."

I suppose you could always make a copy of mfc42.dll and rename it mfc42loc.dll and see what happens.

Here (http://www.tek-tips.com/gpviewthread.cfm/qid/375545/pid/742/lev2/3/lev3/21) is a site describing your problem with a solution.

Terry Porritt
01-05-2003, 04:38 PM
Incidently, I forgot to say that "it is often said that" Norton Crashguard is the cause of most crashes it reports on. I dont think it is supplied by Symantec any more? I may be wrong.

02-05-2003, 10:22 AM
Thanks, Terry, for your reply. I followed your advice, and to summarise, once I disabled Crashguard all was sweet again. My Nortons Systemworks is 2000 version, but I recall that when my normal 2 weekly virus update came through from Symantec, there was also an update of SymEvent, which I believe is a common driver file. It was 2 hours or more afterwards that I tried to open AutoCad and got nothing. Suspect the SymEvent did something to Crashguard. Regards, Keith Booth.

Terry Porritt
02-05-2003, 11:13 AM
Oh good.
The last time I used AutoCad was when it was version 9 on an NEC 386 with a hardware dongle plugged into the parallel port :)