Turok 3 - Shadow of Oblivion June 6th 2000 Prototype Corrective Patch

.: Introduction :.
  This patch corrects periodic and predictable corruption errors in the June 6, 2000 prototype of Turok 3 - Shadow of Oblivion.  It will now run on console under its original checksum and without halting the SP two frames in.  25 of the 23170 compressed files were found damaged and repaired.  The header has been stripped to prevent false-positives against other versions applying specific fixes.

  There is NO replacement for a good dump.  As many errors as could be detected have been corrected, but it is possible some remain, especially within audio banks.


.: Patching :.
  Apply the xdelta patch using a current version of the xdelta patcher from the predictably named xdelta.org.  The patch will only apply to a ROM in native (big-endian) byteorder.
  There are many public prototypes of Turok 3.  Only apply to the 6.6.2000 build.

*Common Names
Turok 3 - Shadow of Oblivion (June 6, 2000 prototype)
Turok 3 - Shadow of Oblivion (2000)(Acclaim)(beta).bin
*MD5
69CE88C46A7C829C6F54004DE93EFCEF
*SHA512
B9CF37708203808985C9EE8A50FC8195E507D4393EA4F6E43AD8E00CCFA02BDD8558D2C43B9B12453D79C34FDD538F2A2178171A357F25FAA81541CE5CD1B681

*Patched MD5
3E6DF46D6071512B90EBFF60772391B0
*Patched SHA512
CA220AAE95FADD04E5BA9EFFADC1D350E1A3272AC68F629E69E21AF56786CB77EDF979023D7C745E8E93427CB4843E834A211B1251603285FC3345601ACBDB49


.: About the Project :.
  This is part of a series of corrective patches for prototypes exhibiting what's known as "address corruption" while dumping.  In short, when the values being read from the cart meet certain conditions, those values will be replaced with others at a mask of the current address.  Both the data and its source are predictable, unlike more common signal noise errors.  A longer (winded) explanation can be found here:
https://pastebin.com/UpzXVu3m

  These patches try to correct as much of this damage as possible.  The goals are:
*) the file is playable on hardware, in case the original data is lost before redumping,
*) act as a guide when a new dump is taken to help confirm it's accurate,
*) determine which methods or setups are subject to this problem, to either detect or avoid future problems,
*) and making a clear case a redump is necessary, as some people take this personally.
  This is NOT a criticism of any particular method or person.  These patches are only a stopgap to raise awareness that an issue exists, can be detected, and therefore prevented.

-Zoinkity