You would think that it would be as easy as using the KIX SETOPTION "WOW64ALTERNATEREGVIEW" command.  However, it appears that the Desktop Authority API function SLREGWRITEVAL ignores it and continues to write to the 32bit registry.  I haven't checked any of the other DA API registry functions.

With $RC = SETOPTION("WOW64ALTERNATEREGVIEW","ON") or $RC = SETOPTION("WOW64ALTERNATEREGVIEW","OFF")

The script command  : $rc=slregwriteval("HKLM\Software\Scriptlogic\LocalMachine", "ComputerType", "Desktop", "REG_SZ")

Returns the following in the slTrace : sub> slRegEdit: Action=[WriteValue] Key=[HKLM\Software\Scriptlogic\LocalMachine] Value=[ComputerType] Data=[Desktop] Type=[REG_SZ] Force32=[1]

Looks like there should be a 5th parameter passed to the function that would change "Force32=0".  Maybe some undocumented variable?  $slRegForce32=0?

I hadn't run into this before since all my scripts using the functions are reading and writing to the 32bit area of HKLM. (HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node).

Any input would be appreciated.  Yes, I've opened a support request with Dell and I'll let you know when I hear from them.

Dave

 

 

0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Answers

0

Found the answer :

slRegEdit($Action, $RegKey, OPTIONAL $RegVal, OPTIONAL$RegExp, OPTIONAL $RegTyp, OPTIONAL $NoDebug, OPTIONAL $Use32bitKey)

Action can be “ReadValue”, “WriteValue”, etc.

Set $Use32bitKey to 0 ot 1 depending on your needs.

Answered 03/14/2016 by: davidhobbs
White Belt

Please log in to comment
Answer this question or Comment on this question for clarity
Admin Script Editor
Admin Script Editor is an integrated scripting environment available free here at ITNinja

Share