Re: BUG #5870: Cannot get the first popup window during install

From: Robert Haas <robertmhaas(at)gmail(dot)com>
To: T Zimmerman <zimmee_freepost(at)hotmail(dot)com>
Cc: pgsql-bugs(at)postgresql(dot)org
Subject: Re: BUG #5870: Cannot get the first popup window during install
Date: 2011-03-03 15:12:20
Message-ID: AANLkTik8=cK4qNRL8FW8ONtV6j0Enqxo9MaT-D62B3bf@mail.gmail.com
Views: Raw Message | Whole Thread | Download mbox | Resend email
Thread:
Lists: pgsql-bugs

On Tue, Feb 8, 2011 at 9:35 AM, T Zimmerman <zimmee_freepost(at)hotmail(dot)com> wrote:
>
> The following bug has been logged online:
>
> Bug reference:      5870
> Logged by:          T Zimmerman
> Email address:      zimmee_freepost(at)hotmail(dot)com
> PostgreSQL version: 8.4.1-2
> Operating system:   Vista Home Premium with SP2
> Description:        Cannot get the first popup window during install
> Details:
>
> I cannot get the first popup window during install.  I saw one person on
> your blog mention that but didn't see a response.  I just click on the .exe
> for 8.4.1 and nothing at all happens.  Things I've tried:
> o  Ensuring I am an administrator
> o  Run as administrator
> o  Creating another user as administrator for the install
> o  Turning off Windows User Access Control (UAC)
> o  Monitoring the Task Manager (see no evidence)
> o  Monitoring the Windows Event logs (see no evidence)
> o  Ensuring I have enough memory (3GB seems like enough)
> o  Verifying proper hardware which is HP Pavilion dv4 Notebook, 2GHz dual
> CPUs, 3GB memory, 32 bit OS
>
> What to do???
> THANKS!
> T

Can you check whether there's a log file in %TEMP% called something
like bitrock_installer_xxx.log, where xxx is a number?

--
Robert Haas
EnterpriseDB: http://www.enterprisedb.com
The Enterprise PostgreSQL Company

In response to

Browse pgsql-bugs by date

  From Date Subject
Next Message Robert Haas 2011-03-03 15:17:39 Re: BUG #5874: pg_dumpall CREATE DATABASE statements 'missing' parameters
Previous Message Robert Haas 2011-03-03 15:08:32 Re: BUG #5869: postgresql corrupts unquoted non-ascii chars in column aliases