Re: problems with postgresql.msi (installing 8.0.2)

> >Try copying your MSI files to c:\temp and install from
> there. Sometimes
> >MSI can lose track of what drives are available, but c:\temp
> should fit
> >in any and all buffers.
>
> I tried that, but have the same problem.  I see a couple of
> places in the log file where the problem might be occurring:
>
> Here:
> MSI (c) (00:E4) [11:03:54:764]: Package to be registered:
> 'postgresql-8.0-int.msi'
> MSI (c) (00:E4) [11:03:54:764]: Note: 1: 2205 2:  3: Error
> MSI (c) (00:E4) [11:03:54:764]: Note: 1: 2729
>
> Or, farther along, here:
> Action start 11:03:55: Welcome_Dialog.
> MSI (c) (00:5C) [11:03:55:555]: Note: 1: 2205 2:  3: Error
> MSI (c) (00:5C) [11:03:55:555]: Note: 1: 2228 2:  3: Error 4:
> SELECT `Message` FROM `Error` WHERE `Error` = 2898 Info 2898.
> MSSansSerif8, MS Sans Serif, 0 MSI (c) (00:5C)
> [11:03:55:555]: Note: 1: 2205 2:  3: Error MSI (c) (00:5C)
> [11:03:55:555]: Note: 1: 2228 2:  3: Error 4: SELECT
> `Message` FROM `Error` WHERE `Error` = 2826

No, this is quite normal, and it's not really an error. It's a matter of
the bitmap image not being perfectly aligned on all screen resolutions.

> However, assuming that this will take a while for you to
> diagnose and/or fix, can you just send me some step-by-step
> instructions and a zip file with the Win32 executables, etc.
> (for 8.0.2) in it, so I can manually install the right
> pieces, add the non-admin user account, etc.?  If you tell me
> what to do, I should be able to manually install it as a
> service running on XP, no?

There is the -no-installer ZIP file available on the ftp site. You can
use that one - just unzip it in for example c:\program file\postgresql -
and then follow the unix guidelines for how to run initdb, and you
should be all set. To run it as a service, use pg_ctl register (see the
pg_ctl documentation). But if you do it manually, try starting it
interactive instead of service first (follow the unix guidelines and
replace with windows paths as necessary). When doing this (and initdb)
remember to be logged in as the non-admin user.


//Magnus