POD (2 requests)

[Cowsheep]

Search for intermodular calls, type getdrivetypea, breakpoint on all calls to it, run app, and look where it stopps. Inside that function is a JNZ has to be NOPed.
Which one, you figure around by single stepping and compare how it behaves with disc ans without.
That have must be done twice (notice change of adress from getdrivetypea.)

If you dont manage that, tell me .exe name. size, version number under file properties and adress of getdrivetypea.
Then, i tell you the jnz to patch.

[Myloch]

Here are the executables I had time to look until now:

PODMMX.EXE (v.2.2.8.0)
1.317.888 bytes

cdchecks: 004A0F10
004A1655

Wpodd3d.exe
v 2.2.8.1
1.197.568 byte
address: 00467C22 - 0049EFB2

podd3dx.exe
v.2.2.8.1
1.468.416 bytes
address: 004672F2 - 0049E5C2




Update: I catched another cdcheck in winpod.exe. Found at address 004A26D5 (please insert pod cdrom when select ghost mode in the time attack and after winning last race in the normal championship too)
I'm testing but every other mode seems to work correctly.

[Cowsheep]

winpod.exe
004A27F5 . /75 0C JNZ SHORT winpod.004A2803


Podmmx.exe

004A1009 . /75 09 JNZ SHORT PODMMX.004A1014
004A1775 . /75 0C JNZ SHORT PODMMX.004A1783

Wpodd3d.exe
00467CC2 |. /75 19 JNZ SHORT wpodd3d.00467CDD
0049F0CA |. /75 0C JNZ SHORT wpodd3d.0049F0D8


podd3dx.exe
00467392 |. /75 19 JNZ SHORT podd3dx.004673AD
0049E6DA |. /75 0C JNZ SHORT podd3dx.0049E6E8

[Myloch]

here are all the remaining (I hope) cdchecks from:

Winpod: 004A216D
PODMMX: 004A10ED
Wpodd3d: 0049EA06 - 0049FC1C
Podd3dx: 0049E016 - 0049F22C

thank you sincerely for give some of your time for that, you are very kind
I'll check with olly the two remaining exes probably in the weekend (the 3dfx ones).
I don't and can't use ati, s3 and direct3d 5 versions so I will not touch them
The cracked exes so far work perfectly on a win98 machine, a windows xp one and on vista too.
Good job Cowsheep!

A weird and not important thing, I tried to debug the exes running them NOT in admin mode and I found some curious results, weird behaviors:

None of them went to main menu, they all asked for cdrom, obviously with modified exe: some executables gave old already NOP, some even gave
new addresses!
I use the vista pc for testing and debugging, I have the same phenomenon
in the Xp computer, starting the game using windows 95/98 compatibility mode or normal mode affects some previously found addresses (it asks for cdrom at that address even if that has been already edited).