[Scummvm-tracker] [ScummVM :: Bugs] #2062: SCUMM: SAM - Crash entering Frog Rock first time (Spanish version)

ScummVM :: Bugs trac at scummvm.org
Tue Aug 10 21:30:04 UTC 2021


#2062: SCUMM: SAM - Crash entering Frog Rock  first time (Spanish version)
----------------------+----------------------------
Reporter:  SF/loom2d  |       Owner:  (none)
    Type:  defect     |      Status:  new
Priority:  low        |   Component:  Engine: SCUMM
 Version:             |  Resolution:
Keywords:             |        Game:  Sam and Max
----------------------+----------------------------
Comment (by tag2015):

 I managed to find the OP's version (the one where SAMNMAX.001 md5 is
 6644ac9d0a233dc608b4684f35a1c69e).
 First of all, I doubt he could complete the game back then, as I played
 until frog rock using dosbox and it crashes exactly as it happens on
 scummvm (screenshot attached).
 Now, I don't know if this is a genuine release or some bootleg that got
 widespread, but the .001 file does not look normal.
 I compared the two versions using a hex editor, these are my findings:

 at the offset indicated by the error message 7081F0, there are 4
 additional bytes (ED 69 EF E9). Then the data is mostly the same , but
 every 0x800 bytes there are 4 different bytes. On the "normal" file there
 are no visible patterns, while in the "alternate" file there is an
 incremental pattern:
 7087FC : 22 01 52 01
 708FFC : 22 01 53 01
 7097FC : 22 01 54 01
 ...
 this occurs about 20 times.

 At address 71456C, there are 4 missing bytes : C5 68 78 69.

 At address 875000, there are 4 additional bytes: 22 11 31 01

 at address 8757FC, the "pattern" begins again:
 8757FC : 22 11 32 01
 875FFC : 22 11 33 01
 ...
 for about 5 times.

 Finally, at address 877FFD there are 4 missing bytes: E9 2F 6E 45

 The rest is identical.

 Fixing the 16 "misplaced" bytes and leaving the others intact, frog rock
 works correctly, but some graphical glitches are present (see screenshot).
 I then continued until the end, and found no other issues.

 Now I don't know what the best course of action could be... add a warning
 in scummvm that this version is glitchy? Ignore this obscure release?
 Provide a patch for SAMNMAX.001?
-- 
Ticket URL: <https://bugs.scummvm.org/ticket/2062#comment:34>
ScummVM :: Bugs <https://bugs.scummvm.org>
ScummVM


More information about the Scummvm-tracker mailing list