Re: New pginstaller beta
"Dave Page" <[email protected]>
| Newsgroups | gmane.comp.db.postgresql.devel.win32 |
|---|---|
| Message-ID | <E7F85A1B5FF8D44C8A1AF6885BC9A0E41A761A@ratbert.vale-housing.co.uk> |
> -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf > Of [email protected] > Sent: 02 August 2004 23:18 > To: Magnus Hagander > Cc: [email protected]; > [email protected] > Subject: Re: [pgsql-hackers-win32] New pginstaller beta > > I tried three scenarios on XP Professional. > > 1) Install everything and use all defaults > > worked perfectly > > > 2) Install everything, use a custom path of 'c:\program > files\pgsql', and have an old version (1.0.2) or Pgadmin 3 > installed on the machine. > > This got things confused, not sure if it was due to me > leaving off the trailing '\' on the path, or having the old > Pgadmin 3 installed. > > What happened was the "setting permissions" scanned the > *entire* c drive, moer than once I think. The installer > showed a message saying Pg did not start (but it did). > > At this point I uninstalled, deleted the Postgres user and > proceeded to 3) > > > 3) Install everything, use a custom path of 'c:\program > files\pgsql\', and remove pgadmin 3 (1.0.2) *before* installing. Thanks for the report Mark. I can't reproduce this here - can anyone else confirm this problem? Regards, Dave. ---------------------------(end of broadcast)--------------------------- TIP 5: Have you checked our extensive FAQ? http://www.postgresql.org/docs/faqs/FAQ.html