Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Quest for Glory MT-32 and Quest for Glory 2 MT-32 have Checksum error and sound issues #62

Open
TheGrimaceMWM opened this issue Apr 23, 2024 · 0 comments

Comments

@TheGrimaceMWM
Copy link

On both of these games the MT-32 loads too quickly causing a checksum error on the display. (LCD on the Mt-32Pi or on the screen if turned in in Mt-32 settings. The wrong sounds are then loaded. In Quest for Glory 2 this is very noticeable on the main menu where laser sounds play instead of the regular instruments.

I found both these games can run properly if I exit the game, turn off sysctl (i've been typing sysctl 0) then going to the Mister menu, custom configuration for hardware speed and manually setting it to 56Mhz L1 on and L2 off. Then no checksum error on the mt-32 screen appears and sounds play properly.

I imagine this problem will also happen on many more Sierra games of this period since they all run on very similar engines.

I have tried editing the rungame.bat to change sysctl to "sysctl sys 56mhz L1+ L2-" but for some reason this seems to run faster than the custom settings and still causes the checksum error and sound issues.
I'm not very familiar with sysctl but hopefully someone else can take all this info and run with it. If there's any documentation on how sysctl works I'm happy to work on this more if someone can point me in the right direction.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant