@REGQUERY with hostname fails

[vefatica]

This was working back in September. @REGQUERY fails whenever a hostname, local or remote, is given.

v:\> echo %@regquery[HKU\.DEFAULT\Environment\TEMP]
%USERPROFILE%\AppData\Local\Temp

v:\> echo %_winname
ZZ

v:\> echo %@regquery[\\zz\HKU\.DEFAULT\Environment\TEMP]
-1

v:\> echo %@regquery[\\lucky\HKU\.DEFAULT\Environment\TEMP]
-1

With a '.' as hostname, it seems to work but gives a result which is incorrect.

v:\> echo %@regquery[\\.\hklm\system\currentcontrolset\services\w32time\w32tmparams\ratedefault]
53 (incorrect)

v:\> echo %@regquery[hklm\system\currentcontrolset\services\w32time\w32tmparams\ratedefault]
156001 (correct)

And the help for many of the @REG functions contains a sentence apparently copied from @REGBREAD but not personalized for the function in question. For example, %REGQUERY's help says

If the key name begins with \\machinename, @REGBREAD opens ...

 

[vefatica]

P.S., I gather the "53" mentioned in the previous post is Windows error 53, "The network path was not found".

 

[rconn]

Fixed in build 68.

 

[vefatica]

Fixed in build 68.

The failure when it should work is fixed but @REGQUERY still evaluates to "53" (as if it had worked) when the network path couldn't be found. "53" is a Windows error code.

v:\> echo %@regquery[\\no-exist\HKU\.DEFAULT\Environment\TEMP]
53

 

[rconn]

I don't understand your point -- what did you want it to evaluate to when you pass it a bad argument?

 

[Charles Dye]

I don't understand your point -- what did you want it to evaluate to when you pass it a bad argument?

-1

 

[vefatica]

I don't understand your point -- what did you want it to evaluate to when you pass it a bad argument?

I'd expect

TCC: (Sys) The network path was not found.
 "\\no-exist"

or some indication that the evaluation of the variable function failed.

 

[vefatica]

-1

"-1" is a possible (somewhat common?) value of a registry value.

 

[vefatica]

P.S., The "53" is the return value of RegConnectRegistry(); it's not from GetLastError().

And when viewing a thread, the user names (under the avatar) are no longer centered ... don't know why but it sticks out like a sore thumb.

 

[Charles Dye]

"-1" is a possible (somewhat common?) value of a registry value.

Indeed it is. But it's also what @REGQUERY, and a lot of other functions, returns to indicate an error....

 

[dcantor]

You could use @REGEXIST to determine whether a -1 return from @REGQUERY is an indication of an error or the actual value.

 

[vefatica]

You could use @REGEXIST to determine whether a -1 return from @REGQUERY is an indication of an error or the actual value.

I don't want to, but even that seems to fail, not returning 0 or 1 as documented.

v:\> echo %@regexist[\\no-exist\HKU\.DEFAULT\Environment\TEMP]
53

That's the Windows error code for "The network path was not found".

 

[rconn]

-1

Well -- no. If a variable function fails, it doesn't return *anything* (just an error message). Some variable functions expect the occasional missing argument or result, and return -1 to indicate they didn't find something.

The question is whether a non-existent machine name is a fatal error (abort the command line) or an occasionally expected error (return some error code).