Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#6116 closed defect (fixed)

SCI: QFG2 (DOS/3.5/v1.102) Not Detected

Reported by: SF/digitoxin1 Owned by: digitall
Priority: normal Component: Engine: SCI
Keywords: detection Cc:
Game: Quest for Glory 2

Description

Details:
ScummVM Version: 1.5.0
Game: Quest for Glory II - Trial by Fire
Language of Game: English
Version of Game: Floppy (3.5), 1.102
Platform: DOS

I have a retail boxed version of Quest for Glory II for MS-DOS with 5.25 and 3.5 floppies. The version of the game is 1.102.

Here is the unknown checksum dump for the 3.5 version:
{"resource.002", 0, "df137dc7869cab07e1149ba2333c815c", 467461},
{"resource.003", 0, "df137dc7869cab07e1149ba2333c815c", 502560},
{"resource.000", 0, "a17e374c4d33b81208c862bc0ffc1a38", 212119},
{"resource.001", 0, "e08d7887e30b12008c40f9570447711a", 331995},
{"resource.map", 0, "367023314ea33e3156297402f6c1da49", 8166},
{"resource.007", 0, "cd2de58e27665d5853530de93fae7cd6", 490794},
{"resource.004", 0, "df137dc7869cab07e1149ba2333c815c", 488532},
{"resource.005", 0, "df137dc7869cab07e1149ba2333c815c", 478574},
{"resource.006", 0, "b1944bd664ddbd2859cdaa0c4a0d6281", 507489},

The 5.25 version detects fine.

Ticket imported from: #3554614. Ticket imported from: bugs/6116.

Attachments (1)

QFG2.md5 (1.9 KB ) - added by SF/digitoxin1 7 years ago.
QFG2 v1.102 3.5 floppy MD5

Download all attachments as: .zip

Change History (12)

comment:1 by digitall, 7 years ago

Summary: Quest for Glory 2 (DOS/3.5/v1.102)SCI: QFG2 (DOS/3.5/v1.102) Not Detected

comment:2 by digitall, 7 years ago

digitoxin1: Thank you for the bug report. To ensure that we can exactly identify this version, could you please attach a text file to this bug containing a file listing of your QFG2 DOS v1.102 5.25 datafiles along with file md5sums. The output of a tool such as http://md5summer.org/ would be optimal.

by SF/digitoxin1, 7 years ago

Attachment: QFG2.md5 added

QFG2 v1.102 3.5 floppy MD5

comment:3 by digitall, 7 years ago

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

comment:4 by digitall, 7 years ago

Owner: set to digitall
Resolution: fixed
Status: newpending

comment:5 by digitall, 7 years ago

Added detection entry in commit aedd0d2a16bc06617c30a3ed1a2fa8f2bf88ba68.

digitoxin1: Please download the next nightly build from the link below and report here if this is now detected correctly:
http://buildbot.scummvm.org/builds.html

Please note, that if this correctly detects and runs, 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.???.???

comment:6 by SF/digitoxin1, 7 years ago

From the disk label:
VER#1.102
INT#11.20.90

comment:7 by SF/digitoxin1, 7 years ago

Status: pendingnew

comment:8 by digitall, 7 years ago

Status: newpending

comment:9 by digitall, 7 years ago

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.

comment:10 by digitall, 7 years ago

User not responding for confirmation. Closing.

comment:11 by digitall, 7 years ago

Status: pendingclosed
Note: See TracTickets for help on using tickets.