On 07.02.2018 20:52, Bo Berglund via Lazarus wrote:
> I had the impression before embarking on this that the 32 bit
> applications would read/write into Software/Wow6432Node/
> and would not be able to reach the Software/.
> But that seems not to be the case for my Lazarus program because in my
> v
On Tue, 6 Feb 2018 13:35:28 +0100, Alexander Hofmann via Lazarus
wrote:
>Hi,
>
>as stated in the MSDN article you cited, the REG_EXPAND_SZ type is a
>hint to the API/API-User, that the string (stored as any other string
>either 2-byte or 1-byte depending in the Version) might contain
>environment
Hi,
as stated in the MSDN article you cited, the REG_EXPAND_SZ type is a
hint to the API/API-User, that the string (stored as any other string
either 2-byte or 1-byte depending in the Version) might contain
environment variables, that need to be expanded before use.
Respective M$ PowerShell, REG.
On Tue, 06 Feb 2018 10:58:21 +0100, Bo Berglund via Lazarus
wrote:
>What I want to know is how to treat data of the type REG_EXPAND_SZ in
>the registry when reading it. There are not that many such but for
>completeness I want to be able to display these kinds of data too.
If I use Reg.ReadStrin
On Sun, 04 Feb 2018 20:44:03 +0100, Bo Berglund via Lazarus
wrote:
>So there is a case construct taht uses the data type reported on each
>item, but I don't know what to do about rdExpandString.
>In fact I don't know what kind of data may hide behind this data
>type...
What I want to know is how
I am writing a little Lazarus program to examine the registry values
stored by a program we use.
So far I have only used strings and integers in the registry, and I
have known in advance what type they are. Now I want to make a more
general kind of reader and so I have created a read function like
