/build/static/layout/Breadcrumb_cap_w.png

System Search - Reading Raw Registry Values (DWORD)

Hi,

I have an issue where I read a DWORD registry value into a property upon installation so I can use this value within our software registry and basically the property gets stored as a string instead of the intended DWORD.

For Example

[HKEY_LOCAL_MACHINE\SOFTWARE\aaaa]
"TCPIPPort"=dword:00000004

When the value is stored using the raw registry read in WIS it is = "#4"

When I reimport the property into the registry:


[HKEY_LOCAL_MACHINE\SOFTWARE\xxxx]
"TCPIPPort"="#4"

Does anyone know how I can import the value back as a DWORD without the use of scripts?


Many Thanks

Paul

0 Comments   [ + ] Show comments

Answers (4)

Posted by: yuri 14 years ago
Orange Belt
0
If you set the data type to 'string' instead of 'Double Word' in the registry details it will write the registry key as a DWORD value.
Posted by: timmsie 14 years ago
Fourth Degree Brown Belt
0
I'm not sure if I'm reading you right but a value of #4 in the registry table is interpreted as a DWORD value

Registry table

So in your Registry table do you have the value of the reg key HKEY_LOCAL_MACHINE\SOFTWARE\TCPIPPort set to #[RESULT OF DWORD READ PROPERTY]
Posted by: HotSpot 14 years ago
Orange Senior Belt
0
Hi Yuri,

As illogical as it seems that worked?!

Thank you for your promt response

Paul
Posted by: ekniranjan 14 years ago
Purple Belt
0
Yuri,
Cool one dude, something i learn, i think this may be useful in future. I am not sure how it works, but definitely i will give a trial.
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ