[Bug 9685] Punkbuster removes me from game for UNKNOWN WINDOWS API FUNCTION [131124]

[wine-bugs at winehq.org]

http://bugs.winehq.org/show_bug.cgi?id=9685





--- Comment #134 from Anastasius Focht <focht at gmx.net>  2008-07-16 16:22:02 ---
Hello,

--- quote ---
It's a little hard to understand which patches from here we need to make PB
work on Wine. Maybe you could write step by step which patches we need?
Something like that:
--- quote ---

The patch for CRYPT_QueryEmbeddedMessageObject is no longer needed.
This commit fixes the regression: 14a12b88614746375c8456a29324965cd61b652e

You need to apply the following patches:

http://bugs.winehq.org/attachment.cgi?id=14001
http://bugs.winehq.org/attachment.cgi?id=14002 
http://bugs.winehq.org/attachment.cgi?id=14003

e.g.:

patch -p1 < wine-ntdll-native-driver-loader.patch 
patch -p1 < wine-ntdll-correct-sbivalues.patch
patch -p1 < wine-ntoskrnl-required-punkbuster-fixes.patch

Then rebuild wine (make && make install)

======= PB service test (can be skipped) ==========
The PB service/driver install, loading and communication can be tested without
a game installed by using their service tool:

http://www.evenbalance.com/downloads/pbsvc/pbsvc.exe

Though that can you can skip this, it's only needed in case of diagnosing
general service problems/regressions ;-)

All 3 services should pass.
At the end of service test (when dynamic kmode driver service is stopped and
deleted from SCM) there is still a bug lurking in service code, which luckily
doesn't affect the overall functioning of PB.

You can verify the outcome by looking at generated log files in:

C:\windows\system32\LogFiles\PunkBuster\

pbsvc.log
PnkBstrA.log
PnkBstrB.log
======= PB service test (can be skipped) ==========

Install your game if it's not already installed.

Make sure the PB client files of the game are up to date.
The best way is to manually run the PB update GUI client:

http://www.evenbalance.com/index.php?page=pbsetup.php

Download "pbsetup.zip" (windows), unzip and run pbsetup.exe

Select the game and update the client as described on the EB website.

Start the game and pray.

EB doesn't issue API fingerprinting checks for all games.
Last time I tested AA PB servers they still had fingerprinting active.

If you get kicked with 131xxx error code, you're basically out of luck.
To get around this you need to hack the client itself.
There are some ways to accomplish this but I'm not inclined to publish details.
Such 'hacks' should remain private as they would immediately trigger
counter-action from EB (and if not correctly done they get you a global GUID
ban).

Regards


-- 
Configure bugmail: http://bugs.winehq.org/userprefs.cgi?tab=email
Do not reply to this email, post in Bugzilla using the
above URL to reply.
------- You are receiving this mail because: -------
You are watching all bug changes.