PT3 on linux with wine

[Eriol]

Okay, the key is you need to enable PostgreSQL to over the network, then you need to use your IP address on your local network instead.

Edit the pg_hba.conf file (located in /etc/postgresql/8.3/main) as explained in this tutorial.

You can find your local ip by running ifconfig at the command prompt it'll be listed as inet addr under your first ethernet card (by default, that'd be eth0 and the first thing listed). Most likely it'll be something like 192.168.1.100.

Put that in instead of "localhost" or "127.0.0.1" and it should connect fine. I think what's going on is that when you use localhost wine looks within the virtual windows image -- which of course isn't running the PostgreSQL server -- so you need to point PT3 at your IP address as if it's going over the network and then it'll work fine.

I was able to connect up to my own DB and see my stats, but I haven't tested importing or anything else -- I suspect they should work fine though.

I runned ifconfig and my local ip is 192.168.1.4
So I edited the pg_hba.conf adding "host all all 192.168.1.0/24 md5"
And I edited the postgresql.conf file adding "listen_addresses = '*'"
I restarted postgresql, then I tried with these settings:
Server 192.168.1.4
port:5432
database user: postgres
password: my pwd

but I've the same error... Did I do anything wrong?

[xyious]

i haven't tried anything with wine and pt3 yet. however, i never managed to get postgre to work when i wanted to run the db on the linux machine.

what i ended up doing is removing postgre and installing from the postgre website. problem is that now the init script isn't working, which is upsetting. but i never restart that box anyway, so unless i get a power outtage or something it's fine

i suspect, since none of my changes in the pg_hba.conf file had any effects on the postgre server behavior that that file has no meaning at all.

so what i would suggest is .... find more files that belong to the postgre server, try to find one that looks a bit like the hba one.... and change settings in that one long enough to find any db.

unfortunately i don't have a virgin ubuntu machine to test on right now, but i might try later if i have the time.

[kraada]

eriol:

Try using "trust" instead of "md5" -- that will allow you to log in regardless of the password. It's not a security problem unless you're worried about other people on your local network (192.168.1.x IPs) trying to get into your PT3 database.

xyious,

What distribution are you using? The default install at least on ubuntu puts the pg_hba.conf in /etc/postgresql/8.3/main and I believe the Debian package puts it in /etc/postgresql directly (though I may be wrong about that; I haven't futzed with the config on that box in quite a while. I may boot it up later today though and if I do I'll try and remember to check for you.)

[Eriol]

ok it works, ty very much.

Only another question (I hope). I've the gray splash screen bug, how can I fix it? I read minimizing the splash screen will works, but I don't know how to do that.

[kraada]

I'm not sure about that one. Did you install Beta 24? Beta 24 worked flawlessly for me in Wine and I know prior Betas (and Build 3) all had problems.

[Eriol]

I'm not sure about that one. Did you install Beta 24? Beta 24 worked flawlessly for me in Wine and I know prior Betas (and Build 3) all had problems.

yes, I did...

[kraada]

I just restarted PT3 to check and I see a grey box there too. I'm not sure what's wrong with the splash screen image but if you just wait eventually it'll go away and PT3 should open normally.

I guess that's not flawlessly but at least that's a very minor bug in terms of actual usability, right?

[Eriol]

It works this way for me too, but it's very slow to open, something like 5-10 mins.
Tbh this happens on my virtualized winXP too since beta 24.

[kraada]

That's way longer than it should take.

Could you please enable logging (Configure --> Options --> Logging Enabled should be checked, then restart PT3) on the virtualized PT3, then after it starts up attach the C:\Program Files\PokerTracker 3\PokerTracker.log file to a support ticket with a description of your problem and we'll look into that for you.

[xyious]

i'm using ubuntu. as i wrote in my post i did make changes to the file that supposedly is responsible for the configuration. however i never managed to get remote access to that postgre server (local worked, but it wasn't a firewall issue). i ended up removing the postgre and installing from the website and i have made it work (not only with pt3, also with pto).
since i have always had problems reinstalling things on ubuntu after deleting the configuration i haven't bothered with it again. (it seems that there are configuration files that get installed at the first install, but are not actually part of the package. what i'm trying to say is.... after i made changes to that hba.conf file, i could never get the original one back. and the same thing happened with mysql a while back. my only sore spot with ubuntu)

either way it's not really a problem for me anymore, i was just throwing that out for consideration.