Ted's mod is HERE

In the past I used to analyze the patch 3, trying to see if it's going to be any good to make use of it. In fact, all it does is fix one single issue, there is nothing else added to it. On the other hand, moebius2778's and Drifter's fixes rely on the temple.dll from patch 2, AND they have the above-mentioned issue fixed as well. Also, the ToEE Frontend relies on Moebius2778's/Drifter's temple.dll. So, there is no real point in updating to patch 3. More than that, the temple.dll file from patch 3 could rely on different versions of supplementary dynamic link libraries (such as tio.dll, mss32.dll, etc.). Therefore, installing patch 3 and installing the moebius2778/Drifter fixed temple.dll into it is almost sure to have conflicts and errors.

So, my personal recommendation to everyone is to ignore patch 3 altogether and use patch 2 with the fixed DLL. This has been discussed tons of times here on the forum, and I don't think that it needs any specific clarification.

- Agetian

 

Yeah, that could be a problem then... Hmm, give it a try then and tell us how it all went. Anyway, patch #3 is generally considered to be not required and could cause problems due to DLL incompatibilities.

I guess someone here should look into a way to make a reverse patch from patchlevel 3 to 2 possible, so that autoinstall up to patch 3 won't be a problem anymore

- Agetian

 

Surely our stuff should 'ship' with those other .dlls?

 

Not really, this could cause internal errors in temple.dll (maybe it won't, though, but it's highly likely that it will). Those files (tio.dll, mss32.dll, etc.) are supplementary libraries: for example, 'tio.dll' is responsible for file I/O operations, 'mss32.dll' is responsible for (AFAIK) sound, 'binkw32.dll' is responsible for movie playback, and so on. The truth is: temple.dll relies highly on the version of each of those files, since all the above-mentioned operations are done the way they're done in certain specific DLL versions that shipped with a patch. So, patch 2 temple.dll is "taught" to use the patch 2 supplementary DLLs, while patch 3 temple.dll could be specific to patch 3 supplementary DLLs. I don't think it would be a good practice to mix these things in any way. If the differences are not big it may be possible to use newer DLLs, but it's highly unlikely.

This way or the other, since the DLL modded by moebius2778 and Drifter comes from the patch 2, and since all the mods, editors, and tools rely heavily on this DLL, we should by all means continue working with patch 2 and NOT patch 3, and surely we shouldn't mix DLLs from those two different patches.

- Agetian

 

Thats what I meant. Since the various mods rely on a modified patch 2 temple.dll, shouldn't they come with the other patch 2 dlls?

 

Hmm... I don't think so. What should be the reason to include other DLLs?...

- Agetian

 

This might explain Lord Spike's LSD-hallucination-like results while using patch 3 with the Co8 stuff. Spike - time to jump on the graveytrain! The top dawg has made the call!

We're talking about two different things here - Atari patches and Co8 mods. Remember, as far as Atari's concerned, Co8 is just another maker of "3rd party" mods and they "don't recommend" that their customers use them. Grok actually said that once.