Full Tilt update for July 8 2009

[pokerisfun]

I guess I am unsure now, but I don't know what to do.

[ptrack pat]

I guess I am unsure now, but I don't know what to do.

Remove all the filters like it describes in this FAQ...
viewtopic.php?f=30&t=1375

[pokerisfun]

Ok so I checked and I didn't have any filters. I clicked "Remove All Filters" under ring and tournament stats just incase. I know I checked "Save My Hands History" under the "Hands History Options" in Stars. In Poker Tracker for Hand History Folder Location I chose C:\Program Files\PokerStars\HandHistory. I chose to move processed files to C:\Program Files\PokerStars\HandHistoryProcessedFiles. I figured this would work because HandHistoryProcessedFiles is its own category and not a subgroup under HandHistory. Maybe this is the problem, but I know it worked before without a problem. The only thing I can think of is that there was a problem when I chose to save the new patch it asked if I was sure I want to save it in C:\Program Files\Poker Tracker V2 because this folder already exists. I said yes because I read to do that somewhere if the forum. Could this have messed up the original program in any way? Could this have messed up the registration code at all? Does any of this information shed any light on what could be wrong? Also, do you want me to continue posting here or is there a better place you think I should be discussing this issue. Thank you for your help ptrack pat

[pokerisfun]

ptrack pat- Oh my god! Disregard everything. I was testing everything out on Play Money. I didn't realize it doesn't work on those tables since I usually play Real Money. Thank you for all your help anyway and I am sorry about the inconvenience.

[Megarana]

Hi all - has it been fixed ???
I can't use PT2 cos it keeps error code violation etc -
I uploaded Patch but still not working
PLEASE let me know what is going on

[ptrack pat]

Hi all - has it been fixed ???
I can't use PT2 cos it keeps error code violation etc -
I uploaded Patch but still not working
PLEASE let me know what is going on

No, it's not fixed. Use this workaround.
viewtopic.php?f=28&t=21074

[JimmyK]

Pat,

I just downloaded the patch from page 1 of this thread and everything worked perfectly. Am I good to go here or am I not out of the woods b/c I'm noticing that many others have or had problems.

[ptrack pat]

Pat,

I just downloaded the patch from page 1 of this thread and everything worked perfectly. Am I good to go here or am I not out of the woods b/c I'm noticing that many others have or had problems.

If you get the access violation errors, use the workaround link that I gave to the last person above until I can find a solution.

[doc freeman]

Pat,

Just had a thought that might help. Not trying to imply anything about my coding abilities and I certainly know almost nothing about the 7.x PowerBuilder used to create PT2 so it's a bit or a reach on my part.

But, just in case you hadn't thought of this. It seems by reading this thread that although the access violation occurs somewhat randomly, it seems to always occur during FromUnicode(), which if I understand correctly is a system call that converts a unicode string to an Ansi string. (I hope I spelled that right; don't wanna go back and check but you get the idea.) It occurs to me that it might provide interesting results if you print out the binary of the unicode "blob" in your debug messages before you send it to FromUnicode(). If possible, the resulting Ansi string could be useful as well before anythig else is done. I would be willing to wager a small amount that somehow, the strings are being corrupted either going in or out. Stack issues might very well cause this semi-random apperance. Other culplits are plentiful; buffer overflow, overwritting memory, invalid buffer to hold the new Ansi string, a file read that did not finish etc. Heck, its even possible there is a bug in the system call but since you said you have used it successfuly in other parts of the code, I would assume its more likely to work than not. Other dumb thoughts (on my part lol) might include invalid variables used as buffers to hold the strings, like local buffers that are no longer good outside of a function or not long enough etc... Maybe a global buffer for in and out could temporarily fix this. (Just kickin some ideas around since I have no actual knowledge of the code.) I am assuming that the old version of PowerBuilder does not include exception capture code (try, catch) so I won't even tread there.

Just some thoughts. Hope this helps even if its completely off base and yet, triggers some other thought that maybe had not occured to you. Sometimes, when I got stuck, input from a different set of eyes or thoughts frequently helped me out.

Good luck

[ptrack pat]

Pat,

Just had a thought that might help. Not trying to imply anything about my coding abilities and I certainly know almost nothing about the 7.x PowerBuilder used to create PT2 so it's a bit or a reach on my part.

But, just in case you hadn't thought of this. It seems by reading this thread that although the access violation occurs somewhat randomly, it seems to always occur during FromUnicode(), which if I understand correctly is a system call that converts a unicode string to an Ansi string. (I hope I spelled that right; don't wanna go back and check but you get the idea.) It occurs to me that it might provide interesting results if you print out the binary of the unicode "blob" in your debug messages before you send it to FromUnicode(). If possible, the resulting Ansi string could be useful as well before anythig else is done. I would be willing to wager a small amount that somehow, the strings are being corrupted either going in or out. Stack issues might very well cause this semi-random apperance. Other culplits are plentiful; buffer overflow, overwritting memory, invalid buffer to hold the new Ansi string, a file read that did not finish etc. Heck, its even possible there is a bug in the system call but since you said you have used it successfuly in other parts of the code, I would assume its more likely to work than not. Other dumb thoughts (on my part lol) might include invalid variables used as buffers to hold the strings, like local buffers that are no longer good outside of a function or not long enough etc... Maybe a global buffer for in and out could temporarily fix this. (Just kickin some ideas around since I have no actual knowledge of the code.) I am assuming that the old version of PowerBuilder does not include exception capture code (try, catch) so I won't even tread there.

Just some thoughts. Hope this helps even if its completely off base and yet, triggers some other thought that maybe had not occured to you. Sometimes, when I got stuck, input from a different set of eyes or thoughts frequently helped me out.

Good luck

Thanks doc freeman, you make some interesting points. You are right about what FromUnicode does. I too had thought about there being a problem with this call because it works just fine for me in development mode but not in the EXE which is very odd to me. I did use this function in the PokerStars notes import/export but that's only dealing with one file not all the hand history files so it's being called a lot more than what the notes import/export does.

What is interesting is that I had a user send me 200+ files from their hand history folder. I test the EXE and it always fails, but it fails on different files most of the time, so it's random on when it happens. Sometimes it gets near the end and I'm praying it will work and then it crashes and sometimes it happens right away. One thing that IS NOT random is that it ALWAYS crashes while reading the last "block" of the file (I have a FileRead that reads in stream mode and I loop through reading the file in blocks at a time). And it doesn't fail on the FileRead, it fails on the subsequent call to FromUnicode with that last blob that was read.

I've spent many hours trying different things/workarounds. I'm looking into some Windows API calls to try to convert the file but that's not working out too well, I can't get the function to work correctly. You've given me some great things to try though. Thanks!