MFC, MFC42.DLL vs MFC42U.DLL

MFC42.DLL vs MFC42U.DLL

Author	Message
J. Merril #1 / 5	MFC42.DLL vs MFC42U.DLL I'm trying to figure out what's up with these. There are install instructions for lots of software components, and in VC++ docs, that tell me to put MFC42.DLL on a system (only if it's not there or has an older version than required one I'm possibly installing, of course). And some of them tell me to register it, which makes sense because it exports DLLRegisterServer. I re-formatted a crashed machine and installed Win2K Pro on it, and ended up with MFC42U.DLL in \winnt\system32 and had the registry entries of the GUIDs for the Property Pages for Font, Color, and Picture pointing to MFC42U.DLL. (I have not yet installed any SPs.) I have not (yet) put any service packs on. If I were to install the newest MFC42.DLL over the older one that came with Win2K Pro, and register it, the Property Pages would then point to MFC42.DLL. What will happen if Unicode-based software tries to use the PPs at that point? What if MFC42U.DLL (or MFC40U.DLL) is doing the PPs and Unicode-obvlivious software tries to use the PPs? MFC42.DLL and MFC42U.DLL each want the PP GUIDs pointing to them. The one registered last wins. Could I damage a system by registering MFC42.DLL on a Unicode system? I've done much searching and haven't found a discussion of whether these conflict or if it matters which are registered. Can anyone help?
Sat, 20 Nov 2004 06:44:39 GMT

Rick Armstron #2 / 5	MFC42.DLL vs MFC42U.DLL Hi J, Quote: > If I were to install the newest MFC42.DLL over the older one that > came with Win2K Pro Dunno if this answers any of your questions, but here's a tidbit: If I remember correctly, I don't think it's possible to do this on Win2k (see http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnw2... dlldanger1.asp). HTH Rick Armstrong (reply address is bogus)
Sat, 20 Nov 2004 13:35:00 GMT

David Crow [MCSD #3 / 5	MFC42.DLL vs MFC42U.DLL I've never heard of registering MFC42.DLL. Quote: > I'm trying to figure out what's up with these. There are install > instructions for lots of software components, and in VC++ docs, > that tell me to put MFC42.DLL on a system (only if it's not there > or has an older version than required one I'm possibly > installing, of course). And some of them tell me to register it, > which makes sense because it exports DLLRegisterServer. > I re-formatted a crashed machine and installed Win2K Pro on it, > and ended up with MFC42U.DLL in \winnt\system32 and had the > registry entries of the GUIDs for the Property Pages for Font, > Color, and Picture pointing to MFC42U.DLL. (I have not yet > installed any SPs.) I have not (yet) put any service packs on. > If I were to install the newest MFC42.DLL over the older one that > came with Win2K Pro, and register it, the Property Pages would > then point to MFC42.DLL. What will happen if Unicode-based > software tries to use the PPs at that point? What if MFC42U.DLL > (or MFC40U.DLL) is doing the PPs and Unicode-obvlivious software > tries to use the PPs? > MFC42.DLL and MFC42U.DLL each want the PP GUIDs pointing to them. > The one registered last wins. > Could I damage a system by registering MFC42.DLL on a Unicode > system? > I've done much searching and haven't found a discussion of > whether these conflict or if it matters which are registered. > Can anyone help?
Sat, 20 Nov 2004 21:30:41 GMT

J. Merril #4 / 5	MFC42.DLL vs MFC42U.DLL I hadn't either, other than on the web site of an OCX (TX Text Control), on the page discussing deployment. I found out that if you unregister MFC42.DLL, it will remove the Property Page settings that might point to it -- even if those settings don't point to it any more. That's bordering on a bug, I would think. I've never registered MFC42.DLL when installing it in the past, so I think I'll continue that practice. But I haven't done anything to make use of the "stock" property pages, either. Thanks for the feedback. message Quote: > I've never heard of registering MFC42.DLL. > > I'm trying to figure out what's up with these. There are install > > instructions for lots of software components, and in VC++ docs, > > that tell me to put MFC42.DLL on a system (only if it's not there > > or has an older version than required one I'm possibly > > installing, of course). And some of them tell me to register it, > > which makes sense because it exports DLLRegisterServer. > > I re-formatted a crashed machine and installed Win2K Pro on it, > > and ended up with MFC42U.DLL in \winnt\system32 and had the > > registry entries of the GUIDs for the Property Pages for Font, > > Color, and Picture pointing to MFC42U.DLL. (I have not yet > > installed any SPs.) I have not (yet) put any service packs on. > > If I were to install the newest MFC42.DLL over the older one that > > came with Win2K Pro, and register it, the Property Pages would > > then point to MFC42.DLL. What will happen if Unicode-based > > software tries to use the PPs at that point? What if MFC42U.DLL > > (or MFC40U.DLL) is doing the PPs and Unicode-obvlivious software > > tries to use the PPs? > > MFC42.DLL and MFC42U.DLL each want the PP GUIDs pointing to them. > > The one registered last wins. > > Could I damage a system by registering MFC42.DLL on a Unicode > > system? > > I've done much searching and haven't found a discussion of > > whether these conflict or if it matters which are registered. > > Can anyone help?
Sat, 20 Nov 2004 23:00:53 GMT

michk #5 / 5	MFC42.DLL vs MFC42U.DLL Thats not a bug, its just a limitation in the way they designed it. -- MichKa Michael Kaplan Trigeminal Software, Inc. -- http://www.trigeminal.com/ International VB? -- http://www.i18nWithVB.com/ C++? MSLU -- http://msdn.microsoft.com/msdnmag/issues/01/10/ Quote: > I hadn't either, other than on the web site of an OCX (TX Text > Control), on the page discussing deployment. > I found out that if you unregister MFC42.DLL, it will remove the > Property Page settings that might point to it -- even if those > settings don't point to it any more. That's bordering on a bug, > I would think. > I've never registered MFC42.DLL when installing it in the past, > so I think I'll continue that practice. But I haven't done > anything to make use of the "stock" property pages, either. > Thanks for the feedback. > message > > I've never heard of registering MFC42.DLL. > > > I'm trying to figure out what's up with these. There are > install > > > instructions for lots of software components, and in VC++ > docs, > > > that tell me to put MFC42.DLL on a system (only if it's not > there > > > or has an older version than required one I'm possibly > > > installing, of course). And some of them tell me to register > it, > > > which makes sense because it exports DLLRegisterServer. > > > I re-formatted a crashed machine and installed Win2K Pro on > it, > > > and ended up with MFC42U.DLL in \winnt\system32 and had the > > > registry entries of the GUIDs for the Property Pages for > Font, > > > Color, and Picture pointing to MFC42U.DLL. (I have not yet > > > installed any SPs.) I have not (yet) put any service packs > on. > > > If I were to install the newest MFC42.DLL over the older one > that > > > came with Win2K Pro, and register it, the Property Pages > would > > > then point to MFC42.DLL. What will happen if Unicode-based > > > software tries to use the PPs at that point? What if > MFC42U.DLL > > > (or MFC40U.DLL) is doing the PPs and Unicode-obvlivious > software > > > tries to use the PPs? > > > MFC42.DLL and MFC42U.DLL each want the PP GUIDs pointing to > them. > > > The one registered last wins. > > > Could I damage a system by registering MFC42.DLL on a Unicode > > > system? > > > I've done much searching and haven't found a discussion of > > > whether these conflict or if it matters which are registered. > > > Can anyone help?
Sat, 20 Nov 2004 23:21:34 GMT

Page 1 of 1

[ 5 post ]