Titan Quest (Use this thread only! Do not start another Thread!)

[porgz]

Originally Posted by pooter

Originally Posted by hexum View Post
i got 1.15 to work perfectly with help from post #240 and others

1) install game
2) update to 1.15
3) right-click titanquest.exe and change to win2000 compatability
4) mount "Titan Quest [ENGLISH] No-DVD/Fixed Image #2" from gamecopyworld with daemon tools (all emulations off)
5) run alkisecurom.exe (download it) and double-click titanquest.exe

i didnt need Pr0t.St0p, but it has helped others...

This works perfectly for me without setting win2k mode.
It never crashed once neither with 1.11 nor with 1.15.

[Vortaka]

Well, misterXzibit, with the .exe, it works fine!

Thank you!

Hackers for ever! (Or... something like that!)

Vortaka

P.S. Oh, by the way, even though I'm sure it works fine, my computer is quite the bad guy when it comes to crack... I'll fully test it tomorrow... (But it should work fine right?) Just kidding!

[TippeX]

hmm, so how the hell did it work for some people when you forgot to include the exe in the initial 'release'.... odd odd odd odd odd odd

[MarsTheGod66]

i already had the 1.15 standalone patch, so i downloaded the crack from post #265 and the game starts without any problems, hooray for misterxzibit

[BarryB]

1.15 Crack only (plus the _asxdox folder) mirrored on TurboUpload:

http://d.turboupload.com/d/958928/test2.rar.html

Password is: GCW

[chron]

Seems that this is some kind of a loader and the files in asxdox dir are dvd copy protection information.

[Joe Forster/STA]

Actually, the files in the "_asxdox" subdirectory seem to be small chunks of a cracked executable... A very innovative way of cracking, if I may add...!

[TippeX]

hmm let me be the first to say this crack is shit heh
basically the code loads up, then virtualalloc's memory blocks
(with NO handling for failure... just a lame 'memory error' messagebox), then reads the file data into them
the dumped data is not dvd data as chron states, its basically
a dump of memory (virtualalloc hooked?) which they then reload again

needless to say if the virtualalloc fails (as they try and get the address on the same base as the dumped it from... which simply wont work on some pc's.. dll's might be loaded there etc..) then the entire thing will crash when that code is called...

the filenames of the files are the virtual memory address they were dumped from
and theres a lot of 00's which the cracker could have trimmed making the crack smaller, as virtualalloc'd memory is automatically zerofilled to begin with...

oh yeh and the data has the users environment dumped.. administrator... computer name flf, does noone even bother to crack properly anymore?

simple loader, injection approach... flawed

innovative... hardly, did you actually analyse it joe?.. its dumped vm fragments amongst other things...

[chron]

I do not have the knowledge to figure out how this crack works so I just assumed what it is.

But to assume it is a loader was not wrong at all

Thx for extending my knowledge TippeX.