ScummVM Version: 1.5.0
Game: Hero's Quest I - So You Want to Be a Hero
Language of Game: English
Version of Game: Floppy (3.5 and 5.25), 1.102
Platform: DOS
I have a retail boxed version of Hero's Quest I for MS-DOS with 5.25 and 3.5 floppies. The version of the game is 1.102.
The 3.5 floppy version is misdetected as:
Quest for Glory I: So You Want to Be a Hero (Amiga/English)
Here is the unknown checksum dump for the 3.5 version:
{"resource.002", 0, "e64004e020fdf1813be52b639b08be89", 635561},
{"resource.003", 0, "f0af87c60ec869946da442833aa5afa8", 640502},
{"resource.000", 0, "40332d3ebfc70a4b6a6a0443c2763287", 78800},
{"resource.001", 0, "a270012fa74445d74c044d1b65a9ff8c", 459835},
{"resource.map", 0, "b162dbd4632250d4d83bed46d0783c10", 6396},
{"resource.004", 0, "f0af87c60ec869946da442833aa5afa8", 644575},
Here are the unknown checksums for the 5.25 version:
{"resource.002", 0, "d22695c53835dfdece056d86f26c251e", 271354},
{"resource.003", 0, "3cd085e27078f269b3ece5838812ff41", 258084},
{"resource.000", 0, "40332d3ebfc70a4b6a6a0443c2763287", 78800},
{"resource.001", 0, "a270012fa74445d74c044d1b65a9ff8c", 75090},
{"resource.map", 0, "5772a2c1bfae46f26582582c9901121e", 6858},
{"resource.007", 0, "f0af87c60ec869946da442833aa5afa8", 269237},
{"resource.004", 0, "8927c7a04a78f1e76f342db3ccc9d879", 267835},
{"resource.005", 0, "13d16cc9b90b51e2c8643cdf52a62957", 268807},
{"resource.006", 0, "48b2b3c964dcbeccb68e984e6d4e97db", 278473},
digitoxin1: Thank you for the bug report. To ensure that we can exactly identify this version, could you please do the following:
1. Attach a text file to this bug containing a file listing of your HQ1 DOS v1.102 5.25" datafiles along with file md5sums. The output of a tool such as http://md5summer.org/ would be optimal.
2. Attach a text file to this bug containing a file listing of your HQ1 DOS v1.102 3.5" datafiles along with file md5sums. The output of a tool such as http://md5summer.org/ would be optimal.
3. Attach a text file to this bug containing a file listing of your HQ1 DOS v1.102 5.25" datafiles along with _detection_ md5sums. Instructions on producing these can be found here: http://wiki.scummvm.org/index.php/Reporting_unknown_MD5_checksums
4. Attach a text file to this bug containing a file listing of your HQ1 DOS v1.102 3.5" datafiles along with _detection_ md5sums. Instructions on producing these can be found here: http://wiki.scummvm.org/index.php/Reporting_unknown_MD5_checksums
(In case you wonder, the full set of detection checksums will be needed to try and work out a way of ensuring that the entry doesn't conflict with the Amiga detection entry)
Thanks in advance.
Hero's Quest I v1.102 3.5 Floppy MD5
Hero's Quest I v1.102 5.25 Floppy MD5
Hero's Quest I v1.102 3.5 Floppy MD5Deep
Hero's Quest I v1.102 5.25 Floppy MD5Deep
digitoxin1: Thank you for providing this additional information. A SCI engine developer will now need to look at adding a detection entry for this version. Please be patient and standby...
Added detection entries in commit 611905aa9718afd0320f518af6976d3316035622.
digitoxin1: Please download the next nightly build from the link below and
report here if these are now detected correctly:
http://buildbot.scummvm.org/builds.html
Note that the main datafiles which detection is performed by appear to be identical between the Amiga and PC 3.5" versions, but now a dialog should appear allowing you to select PC or Amiga.
Please also note, that if these correctly detect and run, a full playthrough
would be a good idea as bad accesses or other script bugs present in this
version will cause ScummVM to halt and error out, and if you could find any
obvious ones, we can look at patching or working round these.
Also, can you please provide the "INT:" string from the disk label i.e.
release date and if you can, run "strings" or a similar tool on the binary
to determine the internal version number which should be of the form:
1.???.???
From the disk label: (This applies to both the 5.25 and 3.5 disks)
Ver#1.102
Int#0.000.629
digitoxin1: Thanks. Have added as comments on detection entries. Will await your results of testing the next nightly build. Note that if you are capable of compiling the latest Git master development codebase youself, then testing with this would be acceptable.
User not responding for confirmation. Closing.