On Sat, Jan 28, 2012 at 2:47 AM, Dharmendra Goyal
<dharmendra.goyal@enterprisedb.com> wrote:
>
>
> On Sat, Jan 28, 2012 at 2:17 AM, Eric Borts <eborts@bltek.com> wrote:
>>
>> The installation now runs successfully after deleting that registry key.
>>
>> In addition, I tried changing the default action on batch files from
>> "Open" to "Edit" using the registry (Windows 7). Double-clicking a file
>> opens it in Notepad, but the installation runs successfully. 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.
>
> 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, though I'm concerned it may break more
systems than it fixes, eg. those where %COMSPEC% has been
intentionally changed because the use wants to use a different shell.
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
