Skip to content

Releases: Sappharad/GDIbuilder

GDIBuilder 2.1.1

18 Jan 04:47
Compare
Choose a tag to compare

This is a minor release that solves some problems with the extraction feature.

Fixed:

  • Attempting to extract .cue images with CDDA tracks previously failed. This has been corrected.
  • The "Extract Selection" option to extract only single file(s) or folders would fail if a file in a subfolder was selected. This now correctly extracts only the selected items directly into the destination folder.

What to download:

  • gdibuilder211_win.zip = Windows version (Requires .NET 8. The app to run is GDIBuilder.Wpf.exe)
  • gdibuilder211_cmd_win_x64.zip = Command Line Win64 version. Does not require .NET.
  • gdibuilder211_mac_arm.zip = macOS version for Apple Silicon (M1, etc.)
  • gdibuilder211_mac_Intel.zip = macOS version for Intel Macs (Made before 2020)
  • gdibuilder211_linux.tar.gz = Linux version (Requires .NET 8)

GDIBuilder 2.1

31 Dec 23:20
Compare
Choose a tag to compare

This is a critical update to GDIBuilder 2.1, where discs built with more than 492MB of data would not boot.

Fixed:

  • Fixed a bug introduced in 2.0 where the file table was written to the wrong place, causing it to be overwritten by files on the disc sometimes.

What to download:

  • gdibuilder21_win.zip = Windows version (Requires .NET 8. The app to run is GDIBuilder.Wpf.exe)
  • gdibuilder21_cmd_win_x64.zip = Command Line Win64 version. Does not require .NET.
  • gdibuilder21_mac_arm.zip = macOS version for Apple Silicon (M1, etc.)
  • gdibuilder21_mac_Intel.zip = macOS version for Intel Macs (Made before 2020)
  • gdibuilder21_linux.tar.gz = Linux version (Requires .NET 8)

GDIBuilder 2.0

04 Dec 04:16
Compare
Choose a tag to compare

This is a major new release of GDIBuilder with new features.

New:

  • Added the ability to build a patched copy of an existing .gdi
  • Added the ability to browse existing .gdi images and extract files from them. This can open .cue sheets for Naomi GD-ROMs as well
  • Added the ability to cancel building a disc
  • Rewrote the GUI in Eto, which provides a native UI using the same code on Windows, macOS and Linux

Backend:

  • Code has been migrated to .NET 8
  • DiscUtils has been updated to a more recent codebase that supported reading discs
  • Added GDReader
  • Added Nuget package for developers

Windows specific:

  • The GUI version requires the .NET 8 runtime and you will be prompted on launch to download it if you don't have it. Not bundling it significantly reduces the download size of the app

macOS specific:

  • The build has been signed and notarized for macOS 11 and later. If you need support for an older OS please download a previous release

What to download:

  • gdibuilder20_win.zip = Windows version (Requires .NET 8. The app to run is GDIBuilder.Wpf.exe)
  • gdibuilder20_cmd_win_x64.zip = Command Line Win64 version. Does not require .NET.
  • gdibuilder20_mac_AppleSilicon.zip = macOS version for Apple Silicon (M1, etc.)
  • gdibuilder20_mac_Intel.zip = macOS version for Intel Macs (Made before 2020)
  • gdibuilder20_linux.tar.gz = Linux version (Requires .NET 8)

GDIBuilder 2.0 release candidate 1

02 Dec 03:48
Compare
Choose a tag to compare
Pre-release

This is a prerelease build of the GUI version of GDIBuilder 2.
The Windows build requires .NET 8, and I'm hoping that it will tell you that if you don't have it.

BuildGDI 2.0 beta 4

13 Sep 02:44
Compare
Choose a tag to compare
BuildGDI 2.0 beta 4 Pre-release
Pre-release

A beta build of the command line "buildgdi" tool for 64-bit Windows machines, with new command line arguments:

The -extract argument can be used to extract files from the high density area of a GDI. Example:

buildgdi -extract -gdi "C:\discs\mygame\disc.gdi" -output "C:\discs\mygame\Data" -ip "C:\discs\mygame\IP.BIN"
This example extracts the GDI at C:\discs\mygame\disc.gdi into the folder C:\discs\mygame\Data\ and also extract IP.BIN to C:\discs\mygame\IP.BIN

The -rebuild argument can be used to rebuild an existing disc image to add or modify files without extracting the original disc first. Example:

buildgdi -rebuild -gdi "D:\discs\mygame\disc.gdi" -data "C:\discs\mygame\translationPatchData" -output "C:\discs\mygame_translated"
Create a copy of the .gdi at D:\discs\mygame\disc.gdi but add the files located in C:\discs\mygame\translationPatchData\ to the disc or replace them if they exist already. Output a new .gdi with all tracks to C:\discs\mygame_translated. Please note that you cannot rebuild a new GDI into the same folder as the source GDI, since the files are being copied from inside the source GDI.

The -date argument can be used to specify the build date on a built image. By default the build date on a GDI is set to the date and time that you build the image. If you always need the same output for the same input (building the same disc twice with the exact same files) then you can override the build date.

Example:
buildgdi -data "D:\discs\mygame\Data" -ip "D\discs\mygame\IP.BIN" -date "2001-12-25 16:15:22" -output "C:\discs\mynewgame"

Changes in Beta 4

  • The extraction feature now handles GDI files that contain quotes around the track filenames.

BuildGDI 2.0 beta 3

12 Sep 02:56
Compare
Choose a tag to compare
BuildGDI 2.0 beta 3 Pre-release
Pre-release

A beta build of the command line "buildgdi" tool for 64-bit Windows machines, with new command line arguments:

The -extract argument can be used to extract files from the high density area of a GDI. Example:

buildgdi -extract -gdi "C:\discs\mygame\disc.gdi" -output "C:\discs\mygame\Data" -ip "C:\discs\mygame\IP.BIN"
This example extracts the GDI at C:\discs\mygame\disc.gdi into the folder C:\discs\mygame\Data\ and also extract IP.BIN to C:\discs\mygame\IP.BIN

The -rebuild argument can be used to rebuild an existing disc image to add or modify files without extracting the original disc first. Example:

buildgdi -rebuild -gdi "D:\discs\mygame\disc.gdi" -data "C:\discs\mygame\translationPatchData" -output "C:\discs\mygame_translated"
Create a copy of the .gdi at D:\discs\mygame\disc.gdi but add the files located in C:\discs\mygame\translationPatchData\ to the disc or replace them if they exist already. Output a new .gdi with all tracks to C:\discs\mygame_translated. Please note that you cannot rebuild a new GDI into the same folder as the source GDI, since the files are being copied from inside the source GDI.

The -date argument can be used to specify the build date on a built image. By default the build date on a GDI is set to the date and time that you build the image. If you always need the same output for the same input (building the same disc twice with the exact same files) then you can override the build date.

Example:
buildgdi -data "D:\discs\mygame\Data" -ip "D\discs\mygame\IP.BIN" -date "2001-12-25 16:15:22" -output "C:\discs\mynewgame"

Changes in Beta 3

  • Fixed file extraction from discs with CDDA. This also would affect the rebuild feature when reading an existing disc.

BuildGDI 2.0 beta 2

29 Aug 03:06
Compare
Choose a tag to compare
BuildGDI 2.0 beta 2 Pre-release
Pre-release

A beta build of the command line "buildgdi" tool for 64-bit Windows machines, with new command line arguments:

The -extract argument can be used to extract files from the high density area of a GDI. Example:

buildgdi -extract -gdi "C:\discs\mygame\disc.gdi" -output "C:\discs\mygame\Data" -ip "C:\discs\mygame\IP.BIN"
This example extracts the GDI at C:\discs\mygame\disc.gdi into the folder C:\discs\mygame\Data\ and also extract IP.BIN to C:\discs\mygame\IP.BIN

The -rebuild argument can be used to rebuild an existing disc image to add or modify files without extracting the original disc first. Example:

buildgdi -rebuild -gdi "D:\discs\mygame\disc.gdi" -data "C:\discs\mygame\translationPatchData" -output "C:\discs\mygame_translated"
Create a copy of the .gdi at D:\discs\mygame\disc.gdi but add the files located in C:\discs\mygame\translationPatchData\ to the disc or replace them if they exist already. Output a new .gdi with all tracks to C:\discs\mygame_translated. Please note that you cannot rebuild a new GDI into the same folder as the source GDI, since the files are being copied from inside the source GDI.

The -date argument can be used to specify the build date on a built image. By default the build date on a GDI is set to the date and time that you build the image. If you always need the same output for the same input (building the same disc twice with the exact same files) then you can override the build date.

Example:
buildgdi -data "D:\discs\mygame\Data" -ip "D\discs\mygame\IP.BIN" -date "2001-12-25 16:15:22" -output "C:\discs\mynewgame"

Changes in Beta 2

  • Some official GD-ROMs have their date fields on files set incorrectly per ISO9660 spec. This caused extraction to FAT32 and ExFAT volumes to fail. The year is supposed to be stored as an 8-bit number representing the number of years since 1900, but these bad discs were storing the low byte of the full 16-bit year instead. This caused the year 2001 to be set as 2109. If a file date is set to over 50 years after the disc authoring date, the year is automatically converted to the correct year during extraction.
  • The modification date on the root directory is now set to the date on the source folder when building a disc
  • Added the -date argument to buildgdi, allowing the disc build date to be overridden.

BuildGDI 2.0 beta 1

26 Aug 00:06
Compare
Choose a tag to compare
BuildGDI 2.0 beta 1 Pre-release
Pre-release

A beta build of the command line "buildgdi" tool for Windows machines, with new command line arguments:

The -extract argument can be used to extract files from the high density area of a GDI. Example:

buildgdi -extract -gdi "C:\discs\mygame\disc.gdi" -output "C:\discs\mygame\Data" -ip "C:\discs\mygame\IP.BIN"

This example extracts the GDI at C:\discs\mygame\disc.gdi into the folder C:\discs\mygame\Data\ and also extract IP.BIN to C:\discs\mygame\IP.BIN

The -rebuild argument can be used to rebuild an existing disc image to add or modify files without extracting the original disc first. Example:

buildgdi -rebuild -gdi "D:\discs\mygame\disc.gdi" -data "C:\discs\mygame\translationPatchData" -output "C:\discs\mygame_translated"

Create a copy of the .gdi at D:\discs\mygame\disc.gdi but add the files located in C:\discs\mygame\translationPatchData\ to the disc or replace them if they exist already. Output a new .gdi with all tracks to C:\discs\mygame_translated. Please note that you cannot rebuild a new GDI into the same folder as the source GDI, since the files are being copied from inside the source GDI.

GDIBuilder 1.3

07 Dec 22:09
Compare
Choose a tag to compare

This is a modernization and bug fix release.

Fixes:

  • Empty folders are now included in the built disc image. Fixes #2
  • Timestamps for folders are now included in the disc image.

Backend:

  • Code has been migrated from .NET 4 to .NET Core 3.1

Windows specific:

  • The application now supports high-DPI displays.
  • The GUI application no longer requires .NET to be installed. (Embedded into the EXE)
  • The command line 'buildgdi' is now a native windows x64 application which also does not require .NET.

macOS specific:

  • The application now supports dark mode.
  • The build has been signed and notarized for macOS 10.15 Catalina and later. The minimum supported OS is now 10.11 El Capitan. If you need support for 10.7 to 10.10 download the previous release.

What to download:

  • gdibuilder13_win32.zip -> Windows version (Most common)
  • gdibuilder13_cmd_win64.zip -> Command Line Win64 version
  • gdibuilder13_macOS.zip -> macOS version