Message100396
| Author |
Stephen.White |
| Recipients |
Stephen.White, carwyn, erluk, loewis, pje, srid, ssbarnea, tarek |
| Date |
2010年03月04日.16:29:44 |
| SpamBayes Score |
0.00082692306 |
| Marked as misclassified |
No |
| Message-id |
<1267720186.84.0.627398479688.issue6792@psf.upfronthosting.co.za> |
| In-reply-to |
| Content |
32bit apps can query the 64bit registry, using the appropriate security and access rights options such as KEY_WOW64_64KEY (0x0100).
Similarly KEY_WOW64_32KEY can be used for 64bit apps to read/write the 32bit registry without having to have knowledge of how the Wow6432Nodes are arranged .
These mean that a 64bit aware app, whether compiled as 64 or 32 bits, can access the alternative view of the registry.
http://msdn.microsoft.com/en-us/library/ms724897(VS.85).aspx
http://msdn.microsoft.com/en-us/library/ms724878(VS.85).aspx
For example if you have both 64 and 32 bit copies of Python installed then a Python app running under the 32bit copy of Python can query the location of the 64bit copy of Python using code like:
key64 = _winreg.OpenKey(_winreg.HKEY_LOCAL_MACHINE, "Software\\Python\\PythonCore\2円.6\\PythonPath", 0, _winreg.KEY_READ + 0x0100)
_winreg.QueryValue(key, "")
C code can do similarly. |
|
History
|
|---|
| Date |
User |
Action |
Args |
| 2010年03月04日 16:29:47 | Stephen.White | set | recipients:
+ Stephen.White, loewis, pje, tarek, carwyn, ssbarnea, srid, erluk |
| 2010年03月04日 16:29:46 | Stephen.White | set | messageid: <1267720186.84.0.627398479688.issue6792@psf.upfronthosting.co.za> |
| 2010年03月04日 16:29:45 | Stephen.White | link | issue6792 messages |
| 2010年03月04日 16:29:44 | Stephen.White | create |
|