On 1/29/2012 3:02 AM, Dave Page wrote:
On Sat, Jan 28, 2012 at 2:47 AM, Dharmendra Goyal
wrote:
Nice analysis Eric. ANy idea why (which program set this) this particular
registry was set.
Dave, shall we consider using "%COMSPEC% /c" with 0 as second parameter..??
We can certainly try it, th
On 1/27/2012 7:47 PM, Dharmendra Goyal wrote:
Nice analysis Eric. ANy idea why (which program set this) this
particular registry was set.
Thanks Dharmendra! It was pretty exhausting.
I haven't a clue how this got changed. I tried goofing around with
shift, ctrl, etc. and I wasn't even able to
REG_SZ (Applications\cmd.exe)
Deleting the \UserChoice key restored my context menu and ability to run
a ".bat" directly instead of using %COMSPEC%.
I am going to un-install an re-install postgres to verify that this
solves my installation issues.
Eric
On 1/27/2012 12:41 PM,
y. So it looks
like the UserChoice registry key, however it got there, is the essence
of the problem.
Which, of course, %COMSPEC% /c would avoid because the program handling
batch files is explicit.
Thanks,
Eric
On 1/27/2012 1:16 PM, Eric Borts wrote:
I found the problem with my
menu."
http://support.microsoft.com/kb/320036
This advice would be likely to hang the PostgreSQL installer.
Cheers,
Eric
On 1/27/2012 12:32 PM, Eric Borts wrote:
Hi Dave and Dharmendra,
It is not the "%COMSPEC% /c" call that causes the window to popup, but
the WindowStyle paramete
Also, here is a link to the same issue on StackOverflow:
http://stackoverflow.com/questions/3559719/wscript-shell-run-doesnt-work-consistently
Also solved using %COMSPEC% /c, though it doesn't say why this is a problem.
Cheers,
Eric
On 1/26/2012 11:37 AM, Eric Borts wrote:
On 1/26/2012
On 1/26/2012 1:17 AM, Dave Page wrote:
Dharmendra, can you look into this please?
Eric, is there anything unusual about the configuration of your
machine? Suffice it to say, this doesn't normally happen.
Hi Dave, I'm guessing the answer to that question is "yes". The machine
came preinstalled
