Hi,
> 2) Automagically send over patch.001 ***
> *** Now I'm trying to figure out the best way to do this -- how does
> real SCI handle this? I know the sound server tells the game what
> patch to use, but how is this actually handled? Through what
> command(s)? Needless to say, we won't get anthing useful out of
> the mt32 unless we dump the patch over..
I'm not sure what exactly you're referring to there...
We have the following steps:
a) Sound system's initialization function is called
b) Sound system determines that it needs patch.X
c) Sound system retreives patch.X
d.GM) Sound system stores patch.X locally
d.native) Sound system installs path.X on the sound hardware
The steps a, b, and d.GM are relatively trivial. I don't know about
d.native, although much or possibly all of this appears to have been
implemented already (by Rickard; e.g. midi_mt32.c).
Regarding c:
In FreeSCI, you can use findResource() (see include/sciresource.h) to get
the resource you want. Don't worry too much about how findResource() is
implemented, as this might change eventually (also, I should change it to
find_resource() eventually to match the overall naming convention).
llap,
Christoph
-- Attached file included as plaintext by Listar --
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.4 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iEYEARECAAYFAjqdTMsACgkQg4EAPSSqEf+jyQCfRoY/XdxHniaTA1j8k/bmUx7F
lVgAn2eGZZgozro9RA+BA5oaquoFv0AV
=j9zZ
-----END PGP SIGNATURE-----
