FPHG Version 2

[jukofyork]

Finally had some time today to implement the new hand-grabber code another 2+2er send me (he wishes to remain anonymous, but we have ALOT to thank him for!). The new method used in FPHG Version 2 is a huge improvement compared to the old FPHG code:

(1) Uses almost no CPU time.
(2) Never misses any hands (or hand endings).
(3) Has a simple GUI which minimizes to the system tray.
(4) I've packaged all the code using an installer, so it should be simpler for those who are not very computer literate (no more batch files, ect).

<u>RELEASE NOTES</u>

(A) All of the old V0.x options (such as '-o' and '-6max') have been removed due to the total re-write of the code. Alot of the old options are now redundant because of the new method, and the useful options will be added back after version 2 has been beta tested.

(B) I haven't as yet provided the source as I did for the old version. The reason I haven't done this is because it uses the same DLL injection techniques as Dollar2BB and PartyPopupBuster uses. These techniques can be abused, but overall I am leaning towards releasing the code for all three apps due to the fact I don't have a great deal of time, and by open-sourcing them others may be able to work on and improve the code.

(C) The main FPHG page has been updated with the new code, but just in case, I have also left both version 0.6b and version 0.7b up for the time being (in case some people can't get version 2 to work - it's beta at the moment...).

(D) Please make sure you don't block the DLL injection using ProcessGuard, as it needs to do this to function properly (just as Dollar2BB and PartyPopupBuster do).

(E) The hand histories are saved to a folder on the root of drive C: called 'C:\FPHG_HandHistories'. I know this is not ideal for some people, but it will be changed in the near future to save the hand histories to a sub-folder below the installation folder (eg: 'c:\program files\FreePHG\HandHistories\').

Please save this thread for posts related to problems, ideas and questions about <u>FPHG Version 2</u> ONLY. If the problem is related to PokerTracker not importing the hand histories, then the correct place to post those questions is in the PokerTracker forums or in the partner thread I have created here.

Juk [img]/images/graemlins/smile.gif[/img]

[_dave_]

Awesome work, seems good so far Juk (5 minute test lol)


I voted YES to source code, for two main reasons:

1) Evildoers will research DLL injection techniques of their own accord, not because they are published here. You learnt how to do it, after all? How could publishing your work prevent others from learning these methods?

2) Publishing of source code allows others to verify the legitimacy / security of this software. I MEAN NO INSULT. I DO NOT MEAN TO INDICATE THAT YOU MAY PUBLISH A KEYLOGGER, ETC. With your history of open publishing / GPL etc. I would hope you know by pointing this out I mean no untoward implications towards you and your software. Source code that can be user-compiled is an excellent way to verify the safe nature of an executable software.



Those who voted NO, pls explain your reasoning.


dave.

[PokerAce]

I voted no and I'll tell you why.

True software development is difficult. To know what you want to do and figure out all the details takes a great amount of time, dedication, skill and experience. The people who have these attributes are smart, intellegent people who are less likely to release something to our community that could cause problems. Simply because they know their time is better spent elsewhere.

Most "hacking" incidents are caused by script kiddies. These are hacker wannabes who know the bare basics of coding and can only do anything useful by cutting and pasting other people's code. These are the people who will take this code and write something malacious to be released.

DLL injection isn't an easy thing to code yourself from scratch. There's no reason to make it any easier for those who would use it to cause problems.

[yellowbluebus]

Juk,

Excellent job once again! Just in time for the Party reload bonus!

[jukofyork]

[ QUOTE ]
Juk,

Excellent job once again! Just in time for the Party reload bonus!

[/ QUOTE ]
NP, but I wish Party would offer me a reload! They been as tight as [censored] for the last 3/4 months with me! [img]/images/graemlins/frown.gif[/img]

Juk [img]/images/graemlins/smile.gif[/img]

[nobi]

could you adjust FreePHG for use at Everest or WPEX?
This would be a great thing.

[rvg72]

[ QUOTE ]
I voted no and I'll tell you why.

True software development is difficult. To know what you want to do and figure out all the details takes a great amount of time, dedication, skill and experience. The people who have these attributes are smart, intellegent people who are less likely to release something to our community that could cause problems. Simply because they know their time is better spent elsewhere.

Most "hacking" incidents are caused by script kiddies. These are hacker wannabes who know the bare basics of coding and can only do anything useful by cutting and pasting other people's code. These are the people who will take this code and write something malacious to be released.

DLL injection isn't an easy thing to code yourself from scratch. There's no reason to make it any easier for those who would use it to cause problems.

[/ QUOTE ]

I voted no for basically the same reasons. Releasing it removes one or two potential barriers of entry for "evildoers"

rvg

[PartyScout]

[ QUOTE ]
I voted no and I'll tell you why.

True software development is difficult. To know what you want to do and figure out all the details takes a great amount of time, dedication, skill and experience. The people who have these attributes are smart, intellegent people who are less likely to release something to our community that could cause problems. Simply because they know their time is better spent elsewhere.

Most "hacking" incidents are caused by script kiddies. These are hacker wannabes who know the bare basics of coding and can only do anything useful by cutting and pasting other people's code. These are the people who will take this code and write something malacious to be released.

DLL injection isn't an easy thing to code yourself from scratch. There's no reason to make it any easier for those who would use it to cause problems.

[/ QUOTE ]

Well said sir.Many thanks for both Juk and Josh's dedicated work and efforts [img]/images/graemlins/ooo.gif[/img]

[-zero-]

Juk, when I run FreePHG, PokerAce won't recognize any tables. PA works fine if PHG is off, but as soon as I run it PokerAce won't recognize any new tables, and for tables that were already open the stats disappear. Do you know some fix for this or should I ask Josh? Thanks.

[jukofyork]

[ QUOTE ]
Juk, when I run FreePHG, PokerAce won't recognize any tables. PA works fine if PHG is off, but as soon as I run it PokerAce won't recognize any new tables, and for tables that were already open the stats disappear. Do you know some fix for this or should I ask Josh? Thanks.

[/ QUOTE ]
This is the first time I've heard of this happening and in theory FPHG shouldn't change the state of the PP client - it just grabs certain strings as they pass through memcpy() function calls.

Juk [img]/images/graemlins/smile.gif[/img]