Re: "1-Click" installer problems

On Thu, Apr 1, 2010 at 10:35 AM, Nikhil G. Daddikar <ngd(at)celoxis(dot)com> wrote:
> It is not the count that matters. It is the quality. Even after giving logs,
> your folks are unable to figure out the problem.

No, because clearly it is not a simple issue.

> I am facing the same
> problem that was faced by a lot of users on the forum and not one was
> resolved successfully.

Actually, not you weren't. Of the cases you quoted, some were from
completely different pieces of software, one was a request for
information which a sales guy followed up, and the remaining ones
included some people for whom a fix was found, some for whom one
wasn't, and some who didn't provide the required information to
diagnose the problem.

Also, there are a number of different issues that can cause an initdb
failure. We've worked hard to work around as many of those as possible
in the installer, but some are just damn hard to track down - and
pretty much impossible if people won't help us when they see a
failure. Just because you see the same outward symptoms, it does not
mean that you have the same underlying problem.

> Otherwise I would've moved ahead on my own. I am
> interested in fixing the installer. I am not interested in manual steps to
> get it working on my PC because there are a hundred other PCs that I have to
> worry about and a fix in the installer would be right step ahead. But
> someone has to admit that there is a problem in the installer.

Noone has said there isn't some situation that the installer cannot
properly handle - I'm sure there are more than a few, knowing how
widely installations of Windows can vary from machine to machine, or
domain to domain.

We want to fix any issues in the installer - but we cannot simply
guess what's going wrong. That can take time and effort to understand.

> The reason I posted this in the general newsgroup is because I thought
> others would like to know what's going on. But I think this is a newsgroup
> with a bunch of inflated egos who want to do everything else rather than
> address the problem. A typical open-source group. Evangelizing PGSQL was a
> mistake.

You've had a people try to help you on the forum.

You've had people here try to suggest how you might help us to help you.

You've even had someone someone telephone your office to try to help
(again, for free), who you refused to talk to.

Unless you are prepared to help us understand exactly what is unique
about your systems so we can figure out what is going wrong, then we
cannot help you.

--
Dave Page
EnterpriseDB UK: http://www.enterprisedb.com