Verify Fantasy World Dizzy - #760
Open
flaviodnz1 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Verifying Fantasy World Dizzy (1991) (Codemasters)
Checklist
Have adequate installation instructions been provided to match any config files in the DOSZ?
Not applicable - the verified DOSZ contains a single executable (
DIZZY.EXE) and does not require installation/config files.Have any official patches been applied, if necessary?
Not applicable - no patch was applied as part of this verification.
Have digital versions (Steam, GOG) been checked for matching?
Not verified.
Can the game benefit from using embedded data or embedded patches in the datfile?
No known need for this version.
Can DoDAT build the game from the install media?
The original Add PR documents that DoDAT can build it directly from the disk image. This was not independently re-verified here because the installation image itself was not verified during this contribution.
If the game requires a yml in the DOSZ, has it been added to the yml folder in the repo?
Not applicable. The existing DOSC contains the required
DOS.YMLconfiguration.Are there .PIF or .ICO or Win32 .EXE files that could be excluded?
No. The verified DOSZ contains only
DIZZY.EXE.Do the file timestamps match the installation media?
Not independently verified against original media. The existing DAT timestamp was preserved unchanged.
Does the DOSZ run standalone?
Yes. The DOSZ was tested standalone in DOSBox Pure and the game launched and ran correctly.
For CD games, can the game be set up to run without a CD mounted?
Not applicable - this is not a CD game.
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 such files were observed during the functional test.
Does the DOSC contain problematic data (i.e. copyright issue)?
No. The DOSC contains only configuration data (
cpu_year,run_path, andrun_input).Does the DOSC have copy protection removed, if possible?
Not verified / no copy-protection change was made as part of this verification.
Is the game running at the correct speed? Is CPU year specified?
cpu_year: 1991is specified in the existing DOSC. The game ran normally during the functional test.Is the DOSC auto-running and skipping past any obstructions? Does it use WAITMODECHANGE if possible?
Yes, auto-start was tested successfully. The DOSC uses
run_path: C:\DIZZY.EXEandrun_inputto advance into the game. WAITMODECHANGE was not required for the tested sequence.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?
Not applicable to the tested configuration.
Does the game have General MIDI support?
Not applicable to the tested configuration.
Is the game set up to run with the best quality graphics options by default?
Not separately verified. The existing DOSC does not force a graphics mode, and the tested configuration displayed correctly.
For certain old games only - are the graphics/audio improved by specifying video_card: pcjr, tandy, or generic_cga?
Not verified; no such override is present in the existing DOSC.
Does the game have a mouse cursor that benefits from enabling input_directmouse?
Not applicable.
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 - there is a single executable.
Does the game share saves with a sequel, expansion, etc? If so, is it updated to use the .savename feature?
Not verified / not known to be applicable.
Is the game data in the root of the ZIP (unless game does not work that way)?
Yes.
DIZZY.EXEis in the root of the DOSZ.Is the entry in the right variant file (i.e. Freeware)?
Yes. The verified game entry is being promoted to the main
PureDOSDAT.xml.For games which include CD images, is there a smaller installation variant that offers the same features but needs less files?
Not applicable.
Comment
DIZZY.EXEwas checked against the existing PureDOS unverified DAT entry and matches exactly: size 336813 bytes, CRC32387b98db, MD5d614048d262945dccf069fe968f747cb, SHA1eaafbe4d2f8e31c074acf5e4a5d43fff3415f91d.unverified/PureDOSDAT_Unverified_Variants_Install.xmlbecause itsdisk1.imgwas not independently verified by hash here.This is one of my first PureDOS verification contributions. Please let me know if I misunderstood any part of the verification process or if anything else should be checked or changed. I'm happy to make any necessary adjustments.