[Scummvm-tracker] [ScummVM :: Bugs] #11307: SCI: GK1 Mac Unknown Varient

ScummVM :: Bugs trac at scummvm.org
Mon Jan 27 10:08:02 UTC 2020


#11307: SCI: GK1 Mac Unknown Varient
-------------------------------+-------------------------
  Reporter:  thevolumeremote   |      Owner:  sluicebox
      Type:  defect            |     Status:  closed
  Priority:  normal            |  Component:  Engine: SCI
Resolution:  invalid           |   Keywords:  sci32
      Game:  Gabriel Knight 1  |
-------------------------------+-------------------------
Changes (by sluicebox):

 * owner:  (none) => sluicebox
 * status:  new => closed
 * resolution:   => invalid

Comment:

 I was hoping to hear back about how this went so that we could establish
 that this isn't a case of a new Mac variant, but I investigated and can
 rule that out and close this.

 From the report we can see that the auto detector is reporting the raw
 file size instead of the size of the Mac data resource in the resource
 fork. Each file size matches the raw file size that I posted; which
 reveals that the reporter's files weren't set up right. (Understandable!
 We haven't documented how to do this!)

 When I md5sum the first 5000 bytes of the raw file (wrong), I get the same
 values:


 {{{
 head -c 5000 Data1 | md5sum
 c4aea5ab61a4ffcdcffc0ebaf66e06fe
 }}}


 The correct size in the detection tables is the size of the data resource,
 which is determined by the auto detector realizing it's dealing with a
 resource fork and parsing the size out of it. This is always a smaller
 value than the raw value. The md5sum is then taken from the first 5000
 bytes of the data resource within the file.

 I don't know the exact misconfiguration that generated this but it is just
 that, and not a new Mac version. Name the files the (unintuitive) way I
 posted and it will work.
-- 
Ticket URL: <https://bugs.scummvm.org/ticket/11307#comment:2>
ScummVM :: Bugs <https://bugs.scummvm.org>
ScummVM


More information about the Scummvm-tracker mailing list