SabreTools

Introduction

This project is a desktop port of some core features of Wizard of DATz Redux. For more information about the parent project, see here.

Features

Currently, SabreTools consists of the following programs: SabreTools UI, DATabase, Headerer, DatSplit, and SingleGame.

SabreTools UI

A bare-bones attempt at providing a true GUI experience for the SabreTools suite. Currently only provides the following functions:

• Importing and Generating DAT files in RomVault and XML formats

DATabase

The main tool of the SabreTools suite. Performs the majority of the core features of the parent project, including the following:

• Importing and Generating DAT files in RomVault and XML formats
• Converting DATs from RomVault to XML format
• Add and remove sources and systems from the database
• Retrieve a list of all sources and systems that are available

This tool can both be used with command line parameters or with the built-in text menu system.

Headerer

A simple auxilary tool that detects and removes headers and also restores headers for the following systems:

• Atari 7800
• Atari Lynx
• NEC PC-Engine / TurboGrafx 16
• Nintendo Famicom Disk System
• Nintendo Entertainment System / Famicom
• Super Nintendo Entertainment System / Super Famicom

The saved headers are currently stored in a database; multiple headers allowed per file.

DatSplit

This tool doesn't do everything possible for splitting DATs, most of those functions are taken care of by third-party tool DatUtil.

• Split a DAT file using two different file extensions
• Works with RomVault and Logiqx XML DATs only because of current limitations

This is useful for splitting DAT files similar to the NonGood set that can have more than one system per DAT.

SingleGame

Hightly experimental tool for merging all games in a single DAT (RomVault or Loqiqx XML only) for use with a server environment. Requested by Kludge.

Contributions

Any feature suggestions or code contributions are accepted. Please take the time to look over the existing code to see proper coding and documentation patterns.