On Mon, Jan 30, 2012 at 7:49 AM, Eric Borts <eborts@bltek.com> wrote:
> On 1/29/2012 3:02 AM, Dave Page wrote:
>>
>> On Sat, Jan 28, 2012 at 2:47 AM, Dharmendra Goyal
>> <dharmendra.goyal@enterprisedb.com> =A0wrote:
>>>
>>>
>>> Nice analysis Eric. ANy idea why (which program set this) this particul=
ar
>>> 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.
>>
>>
> I'd have to agree with Dave here. It was clearly a problem with my batch
> file association. I don't know *how* I got into this state, but at least
> there's a good log now of how to fix the problem for users that have the
> same problem!
>
> I suppose you could detect the problem and issue warning by running a test
> echo batch file and *not waiting* on the result, then pausing for a secon=
d,
> and checking to see if the output file was created. Heck or check the
> registry to see if there's a UserChoice key on the .bat extension.
>
> In any case, I'm satisfied that my computer was messed up and it's now
> fixed. And I've got my context menu back!
That's the most important thing! Thanks for the hard work and
excellent analysis of the problem.
Regards, Dave.
--=20
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
