SUF7 cannot reliably read the registry in 64bit os's
I thought I had a (aleit ugly) solution, which was to shell out to reg.exe and query values/trees and redirect it to a file.
I use Debug.Print() to put the exact command line I run in File.Run() if I copy/paste that debug output to a cmd.exe window -- all is fine (works as expected)
however, some entries don't properly get 'queried' when I use File.Run() from suf7 -- again; the exact same line works fine from cmd.exe (same user)
is file.run() a wrapper for ShellExecute() ? Is it operating at a different user / rights level than the current user?
I went so far as to write to a batch file, then call the batch file from SUF7 -- same results, that same batch file works perfectly from cmd.exe (again, same user, same login session etc)
I desperately need a viable & reliable way to read the registry under 32 & 64bit os's....
Anyone have any thoughts?
I thought I had a (aleit ugly) solution, which was to shell out to reg.exe and query values/trees and redirect it to a file.
I use Debug.Print() to put the exact command line I run in File.Run() if I copy/paste that debug output to a cmd.exe window -- all is fine (works as expected)
however, some entries don't properly get 'queried' when I use File.Run() from suf7 -- again; the exact same line works fine from cmd.exe (same user)
is file.run() a wrapper for ShellExecute() ? Is it operating at a different user / rights level than the current user?
I went so far as to write to a batch file, then call the batch file from SUF7 -- same results, that same batch file works perfectly from cmd.exe (again, same user, same login session etc)
I desperately need a viable & reliable way to read the registry under 32 & 64bit os's....
Anyone have any thoughts?
Comment