O.K. on further research it seems clear, that the way 32-bit apps interact with
the registry on a
64-bit Windows got changed, starting with W7 and WServer 2008 R2, cf.
<http://msdn.microsoft.com/en-us/library/windows/desktop/aa384232%28v=vs.85%29.aspx>.
---rony
On 03.04.2013 20:58, Rony G. Flatscher wrote:
> Stumboled over the following problems when trying to interact with the
> Windows registry on a 64
> bit Windows 7, SP 1, machine (German):
>
> * It seems that the WindowsRegistry class is not able to supply access to
> HKLM, i.e. local
> machine. The respective attribute is not set. This seems to happen with
> both, the 32 and the
> 64 bit ooRexx versions.
>
> * When using the "regRead" method fo an OLEObject of type "WScript.Shell"
> the following problem
> occurs:
>
> o ooRexx 32-Bit: cannot read any keys in the registry of that 64-bit W7
> machine, as an OLE
> error is raised with an error message that the root of the key cannot
> be found.
> o ooRexx 64-Bit can read those keys.
>
> Now, I seem to remember (but am not sure as this is more than two years ago)
> that it was possible
> to use a 32-bit ooRexx on a 64-bit Vista and W7 system to read and write
> registry entries.
>
> In theory, it should be possible to use 32 or 64 ooRexx to interface with the
> registry. Maybe I am
> missing something obvious?
>
> ---rony
>
------------------------------------------------------------------------------
Minimize network downtime and maximize team effectiveness.
Reduce network management and security costs.Learn how to hire
the most talented Cisco Certified professionals. Visit the
Employer Resources Portal
http://www.cisco.com/web/learning/employer_resources/index.html
_______________________________________________
Oorexx-users mailing list
Oorexx-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/oorexx-users
