Powerbasic Museum 2020-B

General Category => General Discussion => Topic started by: Frederick J. Harris on November 01, 2013, 02:35:15 PM

Title: HKEY_CLASSES_ROOT\CLSID\{....}\InProcServer32
Post by: Frederick J. Harris on November 01, 2013, 02:35:15 PM
Just yesterday I was converting some C registry code to UNICODE and 64 bit and when I looked at the code to build the COM registry entries I wondered if the \InProcServer32 key might have been changed to \InProcServer64 in Windows 7 64 bit installations.  I looked through about 20 random entries and see its still listed as InProcServer32.  I guess even Microsoft figured in the late 1990s that 32 bit would go forever! 

I'm thinking of converting my grid code to C or C++ (or both, just to compare) 64 bit.
Title: Re: HKEY_CLASSES_ROOT\CLSID\{....}\InProcServer32
Post by: Charles Pegge on November 01, 2013, 02:47:59 PM
For portability reasons, the '32' tag remains. MS system DLLS are stuck with it on 64 bit platforms. Kernel32.dll, User32.dll etc.
Title: Re: HKEY_CLASSES_ROOT\CLSID\{....}\InProcServer32
Post by: Mike Stefanik on November 01, 2013, 04:49:49 PM
They really should have just bit the bullet, changed the names and did something more logical (like \windows\system64 for the 64-bit components). For backwards compatibility, they could simply create hard links just for existing 32-bit applications. There was also significant code changes required for compatibility with UAC when Vista was released, I think that would have been a good time for the transition. Kind of like ripping off the Band-Aid all at once. Yes, there would have been more hand-wringing, wailing and gnashing of teeth ... but that was happening anyway with Vista.

Title: Re: HKEY_CLASSES_ROOT\CLSID\{....}\InProcServer32
Post by: Theo Gottwald on November 01, 2013, 09:09:36 PM
Just like the geniouse idea with WOW64 that is in fact 32 ... ???