Installer works at our end without any issue.
I remember we had considered using "%COMSPEC% /c" earlier but dropped it
because command windows opens up for every new file execution.
On Fri, Jan 27, 2012 at 3:40 PM, Dave Page <dpage(at)pgadmin(dot)org> wrote:
> iirc, using %COMSPEC% /c will cause the scripts to run in a visible
> command window, which is pretty ugly, and doesn't seem to be necessary
> anywhere except on your machine!
> What's the output from the "set" command on that box?
> On Thu, Jan 26, 2012 at 6:54 PM, Eric Borts <eborts(at)bltek(dot)com> wrote:
> > Also, here is a link to the same issue on StackOverflow:
> > Also solved using %COMSPEC% /c, though it doesn't say why this is a
> > Cheers,
> > Eric
> > On 1/26/2012 11:37 AM, Eric Borts wrote:
> > 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
> > preinstalled with Norton Internet Security, but this was turned off when
> > ran the install. After further investigation to the .bat file, I realized
> > that I am also missing the "Edit" option when I right click a batch file.
> > I investigated, uninstalled stuff, disabled a lot of stuff in my
> > and nearly bricked my computer. After three hours, I'm going to have to
> > for suggestions. Here's what I found/tried:
> > 1. uninstalled Norton Internet Security (and rebooted)
> > 2. uninstalled Acrobat Reader
> > 3. disabled all ContextMenuHandlers by
> > a. renaming HKCR/*/shellex to oldshellex
> > b. renaming HKCR/AllFileSystemsObjects/shellex to oldshellex
> > c. tried, but was unable to rename HKCR/batfile/ShellEx, so renamed
> > HKCR/batfile/ShellEx/ContextMenuHandlers to oldContextMenuHandlers
> > 4. disabled all non-Microsoft shell extensions using ShellExView
> > 5. rebooted - computer bricked (black screen when Windows should be
> > 6. booted in safe mode
> > 7. tested script (from my original response) and right click.
> > a. no Edit option in batch file context menu
> > b. script hung as before
> > 8. Undid steps 3 and 4 in safe mode
> > 9. Rebooted - booted into windows properly
> > 10. Still no Edit in context menu and script still hangs
> > I'm open to suggestions. I think it might be related to Edit menu missing
> > from my batch file, as this is the only odd thing that I can tell about
> > machine. I have another similar machine (earlier model Vaio) that both
> > the Edit menu and runs the test script successfully. I compared the
> > HKCR/batfile registry trees (using TortoiseSVN diff) and they are
> > Short of comparing the entire registry I'm at a loss.
> > Would it be too dangerous to use WScript.Shell.Exec or to use
> > WScript.Shell.Run "%COMPSEC% /c" ? This has been an 11 hour struggle for
> > so far, and I know at least a few others have had this same problem.
> Here is
> > a link to my work around on enterprisedb.
> > Thanks,
> > Eric
> > Reference Links:
> > http://windowsxp.mvps.org/slowrightclick.htm
> > http://www.nirsoft.net/utils/shexview.html
> Dave Page
> Blog: http://pgsnake.blogspot.com
> Twitter: @pgsnake
> EnterpriseDB UK: http://www.enterprisedb.com
> The Enterprise PostgreSQL Company
Senior Software Engineer
The Enterprise Postgres Company
EnterpriseDB Blog: http://blogs.enterprisedb.com/
Follow us on Twitter: http://www.twitter.com/enterprisedb
This e-mail message (and any attachment) is intended for the use of the
individual or entity to whom it is addressed. This message contains
information from EnterpriseDB Corporation that may be privileged,
confidential, or exempt from disclosure under applicable law. If you are
not the intended recipient or authorized to receive this for the intended
recipient, any use, dissemination, distribution, retention, archiving, or
copying of this communication is strictly prohibited. If you have received
this e-mail in error, please notify the sender immediately by reply e-mail
and delete this message.
In response to
pgsql-bugs by date
|Next:||From: Robert Haas||Date: 2012-01-27 14:31:43|
|Subject: Re: BUG #6200: standby bad memory allocations on SELECT|
|Previous:||From: Dave Page||Date: 2012-01-27 10:10:03|
|Subject: Re: Windows x86-64 One-Click Install (9.1.2-1, 9.0.6-1) hangs
on "initialising the database cluster" (with work-around)|