Turok 3 - Shadow of Oblivion July 10th 2000 Prototype Corrective Patch

.: Introduction :.
  This patch corrects periodic and predictable corruption errors in the July 10, 2000 prototype of Turok 3 - Shadow of Oblivion.  22 of its 23178 compressed files were found damaged and repaired, as well as portions of the audio banks.  It should be a more accurate representation of the data on the prototype.

  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.

  Note the prototype's region is USA, and both the unmodified and patched ROM only run NTSC.  Also, although it will run on console not all emulators handle peculiar resolution changes as well as others.


.: 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 7.10.2000 build.

*Common Names
Turok 3 - Shadow of Oblivion (Jul 10, 2000 prototype)
Turok 3 - Shadow of Oblivion (U) (Prototype-WIP).z64
*MD5
C38ACBAE773CC3845EA354421E171998
*SHA512
34F05B7B998D3FE425953B7E8B8E41038DFA2219CA857C8482D3E54B50299080D19036C8B40A4962884A47405DB6C9002C76111EF4131437C85A2D9F6170975F

*Patched MD5
966C0BC757F8BB2F976935B2DBB51436
*Patched SHA512
4F8D9D36072D6055585AD37693253934B910AA306E56C9FAF5CEA40B8A45810F041236FB25ADC37912446FB3F6788BF0A9B56D1C4863FA26D5E8B5E8D1D4502F


.: 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