Skip to content

Verify Battlezone (1983) (Atari) - #844

Open
flaviodnz1 wants to merge 1 commit into
PureDOS:mainfrom
flaviodnz1:verify-battlezone-1983-atari
Open

flaviodnz1 wants to merge 1 commit into
PureDOS:mainfrom
flaviodnz1:verify-battlezone-1983-atari

Conversation

@flaviodnz1

Copy link
Copy Markdown

Verifying Battlezone (1983) (Atari)

Checklist

Have adequate installation instructions been provided to match any config files in the DOSZ?

No separate installation or configuration files are required. This IBM PC booter DOSZ contains only disk1.img; the existing DOSC boots it using run_boot: DISK1.IMG.

Have any official patches been applied, if necessary?

No applicable official patch was identified for this 1983 Atarisoft IBM PC release. Later Battlezone patches belong to different games and were not applied.

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

Yes. The single disk1.img is at the root of the DOSZ. File name, size and available hashes match the unverified DAT.

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

Yes. This is the commercial Atarisoft IBM PC release, so promotion to the primary PureDOSDAT.xml is appropriate; it is not a freeware variant.

Have digital versions (Steam, GOG) been checked for matching?

The Steam/GOG versions considered do not provide a matching 1983 IBM PC booter disk image. No digital storefront payload was independently hash-matched to this disk.

Can the game benefit from using embedded data or embedded patches in the datfile?

No additional embedded data or patch was identified as beneficial. The complete bootable disk image is preserved as one matching DAT member.

Can DoDAT build the game from the install media?

Yes. DoDAT successfully built Battlezone (1983) (Atari).dosz from disk1.img and reported one of one required files written. The same matching input was also packaged by the verification manager.

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

Not applicable. No separate external YML file is required. The existing DOSC already includes the DOS.YML boot configuration.

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

No. The DOSZ consists of one bootable disk image; there are no loose .PIF, .ICO or Windows executable files to exclude.

Do the file timestamps match the installation media?

Not independently verifiable from the DAT. The DAT entry does not specify an individual file timestamp for disk1.img, and the DOSZ container timestamp is not evidence of the original floppy's date.

Does the DOSZ run standalone?

Yes. The DOSZ was launched without the DOSC in DOSBox Pure, and the disk image booted; an interactive boot/video selection screen was observed.

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

Not applicable. This is a floppy-disk PC booter, not a CD game.

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

Not applicable. No CD image or CD-based installation variant is involved.

Can the game benefit from using CHDtoOGG?

Not applicable. This is not a CD-audio release and no CHD audio extraction is involved.

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 significant bloat was observed. The .pure.zip generated after gameplay contained one small member (47 uncompressed bytes; 165 bytes for the ZIP); no large swap/paging file was present in this inspected archive.

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

No problematic copyrighted payload was identified in the existing DOSC. The configuration supplies a DOS.YML for launching the game; the game disk remains in the DOSZ.

Does the DOSC have copy protection removed, if possible?

No copy-protection obstruction was encountered during the tested gameplay. The DAT already identifies the disk image as a cracked PC booter; no additional protection-removal patch was added to the DOSC.

Is the game running at the correct speed? Is CPU year specified?

Yes. The existing DOSC specifies cpu_year: 1982, and the game ran at an appropriate observed speed in DOSBox Pure during testing.

Is the DOSC auto-running and skipping past any obstructions? Does it use WAITMODECHANGE if possible?

Yes. The existing DOSC uses run_boot: DISK1.IMG and run_input: (WAITMODECHANGE); automatic startup was confirmed without manually navigating the earlier boot menu.

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 this 1983 IBM PC booter release. No MT-32 support or compatible driver was identified.

Does the game have General MIDI support?

Not applicable. No General MIDI support or driver was identified for this 1983 IBM PC release.

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

The game displays correctly using its original CGA-era graphics. No higher-quality graphics mode specific to this release was established during verification.

For certain old games only - are the graphics/audio improved by specifying video_card: pcjr, tandy, or generic_cga?

No PCjr or Tandy enhancement for this particular IBM PC booter edition was established. CGA is the documented original graphics reference; no video_card override is proposed.

Does the game have a mouse cursor that benefits from enabling input_directmouse?

Not applicable. The tested version uses keyboard/joystick-style controls and does not need a mouse cursor or input_directmouse.

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. The DOSZ contains a single self-booting disk image, with no separate episodes, utilities or executables to order.

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

Not applicable. No shared-save relationship with another title was identified; a .savename entry is not needed.

Comment

Verified Battlezone (1983) (Atari), the Atarisoft IBM PC booter release.

Summary of verification:

  • All 26 PureDOS checklist items were reviewed, with no unresolved items or issues recorded.
  • The single disk1.img matches the existing unverified DAT entry; the DOSZ was constructed successfully by DoDAT and by the verification manager.
  • The DOSZ booted and ran in DOSBox Pure, both standalone and with the existing DOSC. The DOSC auto-boots DISK1.IMG using WAITMODECHANGE, with cpu_year: 1982; gameplay speed, video, sound and controls were tested.
  • The runtime .pure.zip contained one small member (47 uncompressed bytes, 165-byte archive); no significant swap or storage bloat was observed in that session.
  • No applicable official patch or confirmed PCjr/Tandy-specific enhancement was identified in the sources reviewed.
  • The DAT specifies no timestamp for the disk image. Original-media timestamps were not independently verified.

Proposed changes:

  • Promote the matching entry from unverified/PureDOSDAT_Unverified.xml to PureDOSDAT.xml.
  • Move the existing DOSC from unverified/dosc/ to dosc/ without modifying its contents.
  • Preserve the recorded disk-image hashes and source information.

Source qualification: the DAT identifies this image as a cracked PC booter matching TGOD ID 144. The tests establish a matching, functional disk-image package, not an untouched original commercial floppy.

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

Successfully merging this pull request may close these issues.

1 participant