Hey Richard,
I tried both things, both same results as before :(
Hope there is a solution for this! Thanks for the replies so far :)
Looking forward to hearing from you, FF.
On Thu, Feb 19, 2009 at 9:45 PM, Richard Huxton
<dev@archonet.com> wrote:
First thing to do is to reduce the shared_buffers value that you will
find in your postgresql.conf file (Have a look in your start menu -
might be listed there, if not it's in the installation and you can edit
it with notepad - it's a simple text file).
Somewhere not too far down is a shared_buffers setting (might be "32M")
- try a small value ("16M" or even "8M"). If we can get the damn thing
started we can worry about its performance later. Now try to start the
system - see if you get the same problem.
OK - assuming that didn't work, the second thing I'm going to suggest is
that you download the latest windows version from
http://www.postgresql.org - we don't know precisely what's in your
installation and the "official" one should work fine with this card program.
Finally, if that doesn't work then I'll copy this thread onto the
hackers list and see if they have any great insights.
I'm afraid I'm not a Windows expert, but since we've ruled out your
antivirus I suspect either a slight difference in service-packs applied
to the two machines, or something strange with default permissions being
applied to the postgres user account. The Windows permissions system is
much more complex than a Unix-style system and it's not always obvious
what permissions are causing a problem. The situation isn't helped by
the fact that Windows' reported errors and the actual error aren't
always that similar.
--
Richard Huxton
Archonet Ltd