MFC 4.2 and Windows 95 OSR1

[Andrew Butel]

My MFC4.2 applications do not run on Windows 95 OSR1.
This must be a common problem amoung developers.
Could someone please share the solution to this problem with me.

Another common problem is when linking my app with statically linked
libraries, there are conflicts between certain functions in different
libraries. Does anyone have a suitable solution to this problem.

Many thanks,

Andrew Butel
abu...@xtra.co.nz

-----------------** -- Posted from CodeGuru -- **-----------------
http://www.codeguru.com/ The website for Visual C++ programmers.

[J.F. Gratton]

The problem is that Microsoft has named its MFC 6.0 DLL MFC42.DLL. It does
cause a lot of confusion.

I've checked a OSR1 system lately, and went throught the MFC42.DLL version
property. It gave me v4.21.7022 (MFC v4.21 I'd guess, the "real" MFC 4.2).
The MFC42.DLL file I have here is version 6.00.8168.0 (MFC 6.0).

So what I'm saying mainly is that you might have an application written with
a late version of MFCs and trying to run it with an early version of the DLL
file.

Your other problem might be caused by the same thing.

I know, it's a real pain in the butt, that version thing. MS didn't help
much by naming both versions of the MFC with the same filename. DLL
"versionitis" is a curse, IMHO.

Good luck !

Jeff

Andrew Butel a écrit dans le message <36de1...@209.66.99.126>...

[Matthias Wilde]

I have a similar problem on Win NT4.0, when i use MFC42.dll as a shared
DLL. Try to bind MFC static with your EXE and the problem shoul be
solved. I hope Microsoft will ever be able to give a running development
tool which is 'consistent' in all plattforms.
If this does not work, go back to Visual C++ 5.0 (after reinstalling your
system) and recompile your work (your project files of Visual C++6.0 wont
work with 5.0, so create makefiles first!)

So long
Matthias Wilde (Matthi...@bigfoot.de)

Andrew Butel schrieb: