Logging DirectPlay calls?

Griffon26 · 11-04-2001, 03:36 PM

I was kinda hoping to make a proxy that could do the following:
- run on Windows
- connect to a server using DirectPlay
- allow connection from a Linux box using a user-defined protocol

It would be used to enable a Linux app to connect to a BattleCom server without having to reverse engineer DirectPlay (which is illegal anyway).

But now I need to know what calls a normal BattleCom client does to DirectPlay when connecting to the server. Does anyone know of a way to find out?

I was thinking of making a dplayx wrapper DLL, but although I already have such a DLL with the dplayx interface, BattleCom keeps crashing with an access violation somewhere outside of my code. (Probably got to do with those weird DllGetClassObject, DllCanUnloadNow, etc functions)

Any other ideas of how to log the DirectPlay calls?

Griffon26 · 11-12-2001, 02:13 PM

Quote:

Originally posted by Griffon26
I was thinking of making a dplayx wrapper DLL, but although I already have such a DLL with the dplayx interface, BattleCom keeps crashing with an access violation somewhere outside of my code.

I found the bug. It turned out that dplayx.dll uses the __stdcall convention (doh) and now the wrapper DLL works fine. I have been able to determine which calls are made and when and now have an application that can connect to a BattleCom server.

On to the next thing: reverse-engineering the audio compression. If anyone has any tips on how to do this, they're most welcome =]]