Verify King's Quest IV: The Perils of Rosella

[tomojira]

Verifying King's Quest IV - The Perils of Rosella (1988) (Sierra On-Line)

This game is already in the verified section, but giving it another look with the checklist since it was added early on.

Checklist

Have adequate installation instructions been provided to match any config files in the DOSZ?
Config files are not required in the DOSZ. RESOURCE.CFG can be created by INSTALL.EXE at any time.

GOG is different however - they didn't provide INSTALL.EXE, so RESOURCE.CFG needs to be in the DOSZ there.
I added a copy of it to the DOSC since it was missing there.

Have any official patches been applied, if necessary?
No official patches according to PCGamingWiki.

Is the game data in the root of the ZIP (unless game does not work that way)?
Yes.

For games which include CD images, is there a smaller installation variant that offers the same features but needs less files?
Not applicable.

Is the entry in the right variant file (i.e. Freeware)?
Yes.

Have digital versions (Steam, GOG) been checked for matching?
Yes, there is already a GOG variant.

Can the game benefit from using embedded data or embedded patches in the datfile?
Main variant: No.

GOG variant: I added embedded data to RESOURCE.CFG.

Can DoDAT build the game from the install media?
Yes.

If the game requires a yml in the DOSZ, has it been added to the yml folder in the repo?
Not applicable.

Are there .PIF or .ICO or Win32 .EXE files that could be excluded?
No.

Do the file timestamps match the installation media?
Yes.

Does the DOSZ run standalone?
Yes, after running the setup program to create the config file.

For CD games, can the game be set up to run without a CD mounted?
Not applicable.

Can the game benefit from using CHDtoOGG?
Not applicable.

Is the game creating a swap file in the .pure.zip that could be avoided by increasing memory size? Or is it creating other bloated files that could be prevented by adding them in the DOSZ?
No.

Does the DOSC contain problematic data (i.e. copyright issue)?
No.

Does the DOSC have copy protection removed, if possible?
Main variant: Yes, it's already removed.

GOG variant: Copy protection is still there, so I copied the patch over.

Is the game running at the correct speed? Is CPU year specified?
No CPU year was specified. I added cpu_year: 1988 to both variants since there didn't seem to be speed problems at the beginning of the game.

Is the DOSC auto-running and skipping past any obstructions? Is it updated to use WAITMODECHANGE if possible?
Yes.

Does the game have MT-32 support? If so, is it correctly using MT-32 (old) or CM-32L (new), going by the Vogons Wiki?
Main variant: Yes, it's using "old".

GOG variant: It was missing, so I copied it over.

Does the game have General MIDI support?
No.

Is the game set up to run with the best quality graphics options by default?
Not applicable.

For certain old games only - are the graphics/audio improved by specifying video_card: pcjr, tandy, or generic_cga?
No. There is a different version that benefits from Tandy over PC speaker, but this more advanced version supports Adlib and MT-32.

Does the game have a mouse cursor that benefits from enabling input_directmouse?
Yes, I added it to both variants.

Does a game with separate episodes/executables have the options named and ordered properly in the DOSZ? Do they use the run_utility feature?
Not applicable.

Does the game share saves with a sequel, expansion, etc? If so, is it updated to use the .savename feature?
Not applicable.

Summary of changes

• GOG variant: Added copy of RESOURCE.CFG to DOSC
• GOG variant: Added embedded data to RESOURCE.CFG for DOSZ
• GOG variant: Added copy protection removal to DOSC
• Both variants: Added cpu_year: 1988
• GOG variant: Added MT-32 option
• Both variants: Enabled direct mouse
• Edited comments and links

Other changes not mentioned in the checklist:

• GOG's Readme_new.txt was unnecessarily included in the DOSZ (not an original file from the game), so I removed it
• I noticed the config files in the main variant DOSC were missing some parameters from the installed version of the config file, particularly minHunk, which has caused problems in other Sierra games when it's missing. That didn't seem to be the case when starting this game, but just in case, I replaced the config files in the DOSC with these complete versions (only the directory path was edited)