The MASM Forum

Hi, everyone,...
...ARRRGGHH,...
I'm writing a Registry search routine, and, I've never retrieved a REG_EXPAND_SZ type before (a Registry Key Value) and tried to convert it to readable form.
The documentation Registry Value Types, MSDN (https://msdn.microsoft.com/en-us/library/windows/desktop/ms724884(v=vs.85).aspx), says that you use: ExpandEnvironmentStrings (https://msdn.microsoft.com/en-us/library/windows/desktop/ms724265(v=vs.85).aspx) to convert a string that contains unexpanded references to environment variables and replaces them with the "values defined for the current user".
...Have any of you ever attempted this ??? It sounds like a MAJOR pain-in-the-ass. Any tips ???

...Oh,...and a secondary question: when you are retrieving a Key Value (using, RegEnumValue (https://msdn.microsoft.com/en-us/library/windows/desktop/ms724865(v=vs.85).aspx)), and it is the "Default" name, does that mean that the name string is of zero length, or is there some other convention not described in the documentation ??? (I'm assuming that there can be ONLY ONE default Name, and the associated value, but, I COULD BE WRONG.)
Thanks,...

I recall using ExpandEnvironmentStrings, but don't have the code on the system I'm on, so I made a 32-bit macro version, that seems to work OK on my laptop under Windows 8.1-64 :

xenvstr MACRO envstr
    push    ebx
    push    edi
    push    esi
    mov     esi, reparg(envstr)
    invoke ExpandEnvironmentStrings, esi, 0, 0
    mov     ebx, eax
    mov     edi, alloc(ebx)
    invoke ExpandEnvironmentStrings, esi, edi, ebx
    printf("%s:\n\n%s\n\n", esi, edi)
    free    edi     
    pop     esi
    pop     edi
    pop     ebx
ENDM

include \masm32\include\masm32rt.inc
.data
.code
start:
    xenvstr "%ComSpec%"
    xenvstr "%NUMBER_OF_PROCESSORS%"
    xenvstr "%OS%"
    xenvstr "%Path%"
    xenvstr "%PATHEXT%"
    xenvstr "%PROCESSOR_ARCHITECTURE%"
    xenvstr "%PROCESSOR_IDENTIFIER%"
    xenvstr "%PROCESSOR_LEVEL%"
    xenvstr "%PROCESSOR_REVISION%"
    xenvstr "%PSModulePath%"
    xenvstr "%TEMP%"
    xenvstr "%TMP%"
    xenvstr "%USERNAME%"
    xenvstr "%windir%"
    inkey
    exit
end start


szDefaultName db 0,0

Raymond Chen: (http://blogs.msdn.com/b/oldnewthing/archive/2009/02/05/9397154.aspx)

QuoteThis simplicity in design pushes the responsibility onto the code that uses the registry. If you read a registry value and the data is tagged with the REG_EXPAND_SZ type, then it's up to you to expand it if that's what you want to do.

include \masm32\MasmBasic\MasmBasic.inc
  Init
  Let esi=GetRegVal (http://www.webalice.it/jj2006/MasmBasicQuickReference.htm#Mb1214)("HKLM\SYSTEM\CurrentControlSet\Control\Session Manager\Environment","TEMP", "not found")
  Print "TEMP=[", esi, "]", CrLf$
  Print "TEMP=[", ExpandEnv$ (http://www.webalice.it/jj2006/MasmBasicQuickReference.htm#Mb1069)(esi), "]"
  Exit
end start

TEMP=[%SystemRoot%\TEMP]
TEMP=[C:\Windows\TEMP]

Quote from: Zen on June 04, 2015, 08:15:02 AM(I'm assuming that there can be ONLY ONE default Name, and the associated value, but, I COULD BE WRONG.)

Try HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Nls\Locale

the "Default" value is a carry-over from windows 95
in early versions of the system registry, there were no data "Values", per se
each key had only one value - what we now call the Default value
i.e., it has no name

knowing that should help you understand its' use and meaning

Thanks guys,...again, just what I wanted to know,...
...And, JOCHEN, that blog entry from Raymond Chen explains everything,...I had gotten the impression that the Registry was unregulated (that you could basically write anything to it),...and, Raymond Chen confirmed that.     

I think somebody mentioned them in your previous thread, but the SHReg* functions are basically the Vista+ 'nice' registry functions, but available on XP.

For example, RegGetValue (https://msdn.microsoft.com/en-us/library/windows/desktop/ms724868(v=vs.85).aspx) will auto expand REG_EXPAND_SZ but it doesn't exist on XP. SHRegGetValue (https://msdn.microsoft.com/en-us/library/windows/desktop/bb773536(v=vs.85).aspx) on the other hand is (SP2 anyway), and does all of the same things and with the same parameters

OK,...I got ExpandEnvironmentStrings to decode an enormous number of path strings with environment-variables, and my List View looks a lot better and produces much more useful information.
...But,...I have a number of path strings of the form:   
C:\PROGRA~ 2\MICROS~3\Office12\OUTLCTL.DLL
...And, I don't even know what they are,...much less, what function to call to decode them,...
Any ideas ???

GetLongPathName (https://msdn.microsoft.com/en-us/library/windows/desktop/aa364980%28v=vs.85%29.aspx)

SINSI,
PERFECT ! THANKS !
I have never even heard of that function before,...it's just what I need.