How to expand variable in RegWrite?

[supraspecies]

Here is the line in my script I have problems with:

RegWrite("HKCUSOFTWAREMicrosoftWindows NTCurrentVersionAppCompatFlagsLayers", @tempdir & "VEMSetupVEMSetup.exe", "REG_SZ", "VISTARTM")

As you can see, I need to run the program in Vista compatibility mode. Problem is in *how* AutoIT script enters data in the registry. Upon execution, I get:

C:UsersCHRIST~1AppDataLocalTempVEMSetupVEMSetup.exe

And obviously it doesn't work, because the user name is not full. So how do I expand it to write a full user name? REG_EXPAND_SZ as value type does not work.

Thanks in advance!

P.S. I know it isn't exactly the same as expanding a variable, but I'm not sure how else to call it. Would appreciate a hint, by the way.

Edited August 14, 2012 by supraspecies

[BrewManNH]

That's a short name for the full name, I don't believe that's your problem because Windows will be able to translate that to the full name, normally without a problem. Also, it's quite possible that's how Windows stores that in the registry.

[supraspecies]

Checked four times, I'm absolutely positive that's my problem. When I enter full name, Windows reads it properly. When I enter short one, it doesn't. Entering full name does solve the issue, the only thing I need to know is how to do it via AutoIT. Apparently, I need to expand a macro, but that's a bit tricky for me.

Also, it could be possible Windows relies on full name and not just "Christ~1" because there could be, say, "Christopher" and "Christine" on the same computer, thus it would be unclear which user the value applies to. But that's just a guess.

Also, it's quite possible that's how Windows stores that in the registry.

No. When I was was writing to the registry using another application, I used Windows' original %Temp% variable, and it wrote a full name. Worked flawlessly.

Windows will be able to translate that to the full name, normally without a problem

I'm well aware of that. Maybe the problem is caused by a dash in the username. Looks like we've run into an exception from "normally".

EDIT:

Used the original Windows variable $temp = envget("TEMP") - still the same picture, yeah. Now it's the sixth time I made sure full name works where shortened one doesn't. Question is what the hell to do about it...

EDIT 2:

This works:

RegWrite("HKCUSOFTWAREMicrosoftWindows NTCurrentVersionAppCompatFlagsLayers", @UserProfileDir & "appdatalocaltempVEMSetupVEMSetup.exe", "REG_SZ", "VISTARTM")

But I'd still prefer to do it properly, by using an actual "TEMP" variable. Not to mention that the above won't work on Windows XP unless I modify it (not planning to use this particular one of course, I refer to compatibility overall). There has to be a simpler way.

Edited August 15, 2012 by supraspecies

[guinness]

FileGetLongName in the help file.

[supraspecies]

PERFECT! Thank you so much! I only had to add one short line to my script!

$LongName = FileGetLongName(@TempDir)

RegWrite("HKCUSOFTWAREMicrosoftWindows NTCurrentVersionAppCompatFlagsLayers", $LongName & "VEMSetupVEMSetup.exe", "REG_SZ", "VISTARTM")

[guinness]

You can do away with the variable and just insert where the variable was, unless you are using it multiple times.

[BrewManNH]

BTW, if there were a Christine and a Christopher, the short names would be different, Christ~1 and Christ~2, that's why there are numbers after the shortened name.