/build/static/layout/Breadcrumb_cap_w.png

Add Qword registry value

I need to add a Qword registry value of "d7 62 45 55 00 00 00 00" to an msi. I'm using Orca and have added other types of registry values but I have never had to enter a Qword value.

0 Comments   [ + ] Show comments

Answers (4)

Posted by: joedown 15 years ago
Third Degree Brown Belt
0
Update: I tried to capture what the registry info would look like by doing a snapshot in AdminStudio 8.0 but the resulting msi created lays down the registry entry as a string value instead of a Qword value. here is the entry value in the MSI created by AdminStudio:

hex(11):AC,EF,48,55,00,00,00,00

So is a Qword registry value possible in an msi or does this require some sort of custom action?
Posted by: joedown 15 years ago
Third Degree Brown Belt
0
Ok, found this website: http://tarma.com/support/tin3/0100-using/0400-panes/registry_value_attributes.htm

It states that QWORD data type is not supported by MSI. WTF? So how do I write this value?
Posted by: reds4eva 15 years ago
Second Degree Blue Belt
0
It states that QWORD data type is not supported by MSI. WTF? So how do I write this value?

Thats not right.
Someone that uses Vista to package maybe able to help, but i wouldnt think that you'd be able to capture the qword value unless you are using Vista or 64 bit XP.
I would use a script to add this value.
Posted by: LLayr 13 years ago
Yellow Belt
0
Seems nearly everything I do l8ly brings me back to appdeploy... so I joined. :)
I agree totally w/reds4eva, and being a proud owner of Windows2000 for ALPHA, I can tell you that QWord in a Windows environment has been around a lot longer than most people think. Despite this being a two year old post, I thought I'ld contribute, as with the release of Windows7 there's a lot more QWording going around. The basic problem lies in the fact that old versions of regedit appear to have no way to directly handle one. I am completely unaware if newer versions of MSI handle QWord directly as I have always scripted this.

To handle directly entering a QWord via regedit, we use the binary data type. That's the history, now to try to be helpful to someone like joedown, here's a script...

QWord2Reg.vbs:
' Fetch Shell object
Dim oShell
Set oShell = CreateObject("WScript.Shell")
If Not oShell Is Nothing Then
' Write $tring to Reg
oShell.RegWrite "HKLM\SOFTWARE\My.MSI\MyKey\My$", "d7 62 45 55 00 00 00 00", "Binary"
' Release Object
Set oShell = Nothing
End If

Of course, replace MyMSI with, umm, your.msi and MyKey with your key and My$ with your string and joedown's QWord with your QWord.
The data type (in this case, "Binary") can of course be of any valid type as found in some of the examples on the following appdeploy page:
http://www.appdeploy.com/tips/detail-pf.asp?id=103

This should allow QWord for ALL 64bit Windows' from 2000 to 7
Tested on 2000 for Alpha, WXP X64ProSP1 and 7. Many people have tried to pay me to do things on Vista, but they'ld need to significantly increase that 'pay' thingy to get me to consider it. I sure hope they don't...
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