Opened 16 years ago

Closed 16 years ago

Last modified 16 years ago

#1340 closed defect (worksforme)

MI1VGA: Unable to read resource

Reported by: SF/fizzet Owned by: fingolfin
Priority: normal Component: Engine: SCUMM
Keywords: Cc:
Game: Monkey Island 1

Description

Hi,

I have a problem with the (german) VGA floppy version
of MI1. I am trying to get to the swordmaster,
following the merchant. I get to the point where he
pushes the sign to create the bridge across the chasm,
but whenever I try to follow him, ScummVM aborts with
an 'Unable to read resource' error.

I have checked both the 0.5.1 release and the daily
snapshot
from December 14. The problem remains. ScummVM was
compiled on Linux with gcc 2.95.3.

Savegame (0.5.7) is attached.

Ticket imported from: #859986. Ticket imported from: bugs/1340.

Attachments (1)

monkeyvga.s03 (8.0 KB) - added by SF/fizzet 16 years ago.
Savegame

Download all attachments as: .zip

Change History (6)

Changed 16 years ago by SF/fizzet

Attachment: monkeyvga.s03 added

Savegame

comment:1 Changed 16 years ago by fingolfin

Sounds as if your data files are damaged.

comment:2 Changed 16 years ago by SF/fizzet

Any chance to verify that?

comment:3 Changed 16 years ago by fingolfin

First indicator: the savegame works just fine for me.

A way to verify it: check the sizes/MD5 checksums of your data
files. Mine are:

000.LFL 8357 d0b531227a27c6662018d2bd05aac52a
901.LFL 2572 0d01659586aa770608acc8138daae8cc
902.LFL 4023 838b3d8ed6fa615ae561273ae29efafd
903.LFL 2572 6c72dd66cccae6308f962075c314ee16
904.LFL 4782 87edc5c6d4eb64361df02072e08732ce
DISK01.LEC 1101583 f4762f06c3de37d852ff16f093a06406
DISK02.LEC 1118422 b74e2034cac3bb3203ee28d4a7d18d4e
DISK03.LEC 1176753 b29b164bbd996e18c3387438e5d7a734
DISK04.LEC 1048787 a0c2a3b5dadaf6e09ecaa819752aa4a3

comment:4 Changed 16 years ago by fingolfin

Owner: set to fingolfin
Resolution: worksforme
Status: newclosed

comment:5 Changed 16 years ago by SF/fizzet

Alright. Never mind. Just copying the file to HD doesn't work.
Damn! Thanks for the quick response, anyway.

Note: See TracTickets for help on using tickets.