PokerTracker

Today I started a large manual import (10,300 files of 300 hhs each) before leaving for work. Upon returning home, I found that ZoneAlarm had flagged PT3 for suspicious behavior, the message being the standard "PokerTracker.exe is trying to access the trusted zone." It appears to have happened about 1/4 of the way through the import. I clicked "OK" to allow PT3 access to all zones of my computer, but then received the Windows-generated program death message "Poker Tracker has encountered an error and needs to close."

I have re-started the import. The error may not occur again, since PT3 is now in ZoneAlarm's list of Trusted Programs. If it happens again, what specific information should I post?

That's really strange that it happened way after the import started. ZoneAlarm should throw up a flag almost immediately on startup because PT3 connects to your database over the network.

If it crashes again, please attach the PokerTracker.log file in the main PT3 directory to a support ticket.

[quote="Josh"ylj]That's really strange that it happened way after the import started. ZoneAlarm should throw up a flag almost immediately on startup because PT3 connects to your database over the network.

If it crashes again, please attach the PokerTracker.log file in the main PT3 directory to a support ticket.[/quoteylj]

If I remember correctly, ZoneAlarm DID flag PT3 on first launch for attempting to access the Internet. I may well have clicked "OK" without checking the "Apply to all suspicious behaviors by this program" option. At any rate, I am running an import on 1,000 of the 10k files right now, and have gotten through about 200 of them without incident.

I should point out that if you were in the middle of an import and PT3 crashes, you either need to purge the database, or start with a new database, because data will be corrupt.

[quote="Josh"xl0]I should point out that if you were in the middle of an import and PT3 crashes, you either need to purge the database, or start with a new database, because data will be corrupt.[/quotexl0]

Ugh, is there no other way around this? The raw hand histories that I have contain a number of duplicates because of a botched export from PT2, and importing hh's with duplicate hands takes a long time with PT3.

Not at this time. I plan on writing a crash recovery routine to fix the database in the event of a crash, but that's backseat to all the other features that need added right now.