Overhaul for MPF rename

2026-07-02 17:24:48 +00:00 · 2020-11-10 23:46:57 -08:00
parent da283b2397
commit ab53897c0c
12 changed files with 66 additions and 66 deletions
--- a/Development/Build-a-Local-Copy.md
+++ b/Development/Build-a-Local-Copy.md
@@ -1,10 +1,10 @@
 # Build a Local Copy

-Below is what is required to build the DICUI repo from scratch
+Below is what is required to build the MPF repo from scratch

 ## Prerequisites

-* The latest source for the DICUI GitHub page
+* The latest source for the MPF GitHub page
 * C# / .NET IDE of your choice (Visual Studio 2019 Community Edition strongly recommended)
 * .NET Framework 4.7.2, and 4.8, and .NET Core 3.1 for development
 * Working knowledge of C#, .NET, and UI design
--- a/Development/Coding-Practices.md
+++ b/Development/Coding-Practices.md
@@ -72,7 +72,7 @@ Comment code as often as necessary to clarify what functions or code blocks do.

 * **Avoid duplicating code.** If a block of code of significant size (3+ lines usually) is used multiple times within the code, create a method and abstract it. If the block is duplicated across multiple classes, create a helper class (if the function is significantly different than existing classes) to add the method to or add to an existing helper class.
 * **A class should represent a single function or set of highly related functions.** For example, a class should not contain importing and exporting DATs. On the contrary, having similar functions spread across multiple classes is unnecessary. If it's an edge case, contact the project lead for the official ruling.
-* **Namespacing should be reasonable.** Each of the internal namespaces of the library code represent (mostly)-distinct subsets of functionality. For example, the `DICUI.Library.DiscImageCraetor` namespace contains functionality specific to DiscImageCreator running and parsing.
+* **Namespacing should be reasonable.** Each of the internal namespaces of the library code represent (mostly)-distinct subsets of functionality. For example, the `MPF.Library.DiscImageCraetor` namespace contains functionality specific to DiscImageCreator running and parsing.

 ## Code Additions

--- a/Features/Components.md
+++ b/Features/Components.md
@@ -1,10 +1,10 @@
-# Components of the DICUI Project
+# Components of the MPF Project

-The DICUI project contains two actual programs: **DICUI** and **DICUI Check**. Both output the same, standardized `submissionInfo` format based on Redump submission criteria. Below is a brief comparison of both:
+The MPF project contains two actual programs: **MPF** and **MPF Check**. Both output the same, standardized `submissionInfo` format based on Redump submission criteria. Below is a brief comparison of both:

 | Program Name | Interface | OS Compatibility | Can Dump Directly | Notes |
 |--------------|-----------|------------------|-------------------|-------|
-| [DICUI](https://github.com/SabreTools/DICUI/wiki/DICUI) | GUI | Windows 7+ (.NET 4.6.2 and above) | Yes | Includes tailored profiles that can be selected from the main window for easier dumping with supported programs. It is able to access the disc post-dump to gather more information automatically, including versions and copy protection status. Configuration is done either using the Options window within the GUI or directly in the configuration file. |
-| [DICUI Check](https://github.com/SabreTools/DICUI/wiki/DICUI-Check) | Commandline | Windows 7+ (.NET 4.6.2 and above), `mono` | No | Meant as a wrapper around the post-dump steps of DICUI to be run on pre-existing dumps. It does not attempt to access original media to gather more information, so only data derived from the output files is included. Configuration is purely done by per-run parameters. |
+| [MPF](https://github.com/SabreTools/MPF/wiki/MPF) | GUI | Windows 7+ (.NET 4.6.2 and above) | Yes | Includes tailored profiles that can be selected from the main window for easier dumping with supported programs. It is able to access the disc post-dump to gather more information automatically, including versions and copy protection status. Configuration is done either using the Options window within the GUI or directly in the configuration file. |
+| [MPF Check](https://github.com/SabreTools/MPF/wiki/MPF-Check) | Commandline | Windows 7+ (.NET 4.6.2 and above), `mono` | No | Meant as a wrapper around the post-dump steps of MPF to be run on pre-existing dumps. It does not attempt to access original media to gather more information, so only data derived from the output files is included. Configuration is purely done by per-run parameters. |

 Please see the individual pages for more details on each program.
--- a/Features/DICUI-Check.md
+++ b/Features/DICUI-Check.md
@@ -1,10 +1,10 @@
-## DICUI Check
+## MPF Check

-**DICUI Check** is an optional commandline component in the DICUI project. This came about as a response to a lack of UI support on the Linux side. The goal of this program is to provide the same powerful library parsing and generation but without having to deal with the actual dumping part.
+**MPF Check** is an optional commandline component in the MPF project. This came about as a response to a lack of UI support on the Linux side. The goal of this program is to provide the same powerful library parsing and generation but without having to deal with the actual dumping part.

 ## Usage

-`DICUI.Check.exe [standalone] <mediatype> <system> [options] </path/to/output.bin> ...`
+`MPF.Check.exe [standalone] <mediatype> <system> [options] </path/to/output.bin> ...`

 Please note that when dealing with outputs that contain multiple, split tracks, you must specific the path to the `.cue` file instead of the first `.bin`. This is due to some internal logic that gets the name for the rest of the output files.

@@ -37,7 +37,7 @@ Below is a list of currently dumpable or verifiable media types along with a bri

 ## System Types

-There are a lot of systems that are technically supported for dumping and verification if only because a lot of media is similarly accessible. For convenience, the list of currently accepted systems below has been separated into categories. Each entry has the short name used for **DICUI Check** along with a brief description.
+There are a lot of systems that are technically supported for dumping and verification if only because a lot of media is similarly accessible. For convenience, the list of currently accepted systems below has been separated into categories. Each entry has the short name used for **MPF Check** along with a brief description.

 ### Arcade

@@ -179,7 +179,7 @@ There are a lot of systems that are technically supported for dumping and verifi
 | Flags | Short Description | Long Description |
 | ----- | ----------------- | ---------------- |
 | `-c <username> <password>`<br/>`--credentials <username> <password>` | Redump Credentials | Optionally, include Redump credentials for pulling extra information from the site when generating the submission information |
-| `-u <program>`<br/>`--use <program>` | Set dumping program | By default, **DICUI Check** will assume that you are verifying a DiscImageCreator output. If this is not the case, you can set the program using this flag. See [Overview](https://github.com/SabreTools/DICUI/wiki/Overview) for more details about supported programs. |
+| `-u <program>`<br/>`--use <program>` | Set dumping program | By default, **MPF Check** will assume that you are verifying a DiscImageCreator output. If this is not the case, you can set the program using this flag. See [Overview](https://github.com/SabreTools/MPF/wiki/Overview) for more details about supported programs. |
 | `-p <path>`<br/>`--path <path>` | Set drive path | Optionally, include the path that contains the original media related to the output. This can allow for extra information to be included that would otherwise be skipped without original media. |
 | `-s, --scan` | Scan for protection | **Requires `-p, --path`.** Optionally, scan the original media for copy protection using the built-in BurnOutSharp library. |

--- a/Features/DICUI.md
+++ b/Features/DICUI.md
@@ -1,8 +1,8 @@
-# DICUI
+# MPF

-**DICUI** is the main GUI component of the DICUI project. This confusing naming exists because originally, DICUI (the project) contained only a single component: DICUI (the GUI application). Since then, most of the specialzied logic has been abstracted into `DICUI.Library`, a shared DLL that contains parsing, scanning, and submission generation logic.
+**MPF** is the main GUI component of the Media Preservation Frontend (MPF) project. This confusing naming exists because originally, MPF (the project) contained only a single component: MPF (the GUI application). Since then, most of the specialzied logic has been abstracted into `MPF.Library`, a shared DLL that contains parsing, scanning, and submission generation logic. Both MPF the project and application used to be called **DICUI** since they were just wrappers for DiscImageCreator initially.

-Please note that **DICUI.Avalonia** is essentially the same thing as the regular GUI, except written in a different UI framework to try to achieve cross-platform compatibility. All of the notes below apply to both GUIs.
+Please note that **MPF.Avalonia** is essentially the same thing as the regular GUI, except written in a different UI framework to try to achieve cross-platform compatibility. All of the notes below apply to both GUIs.

 ## UI Overview

@@ -25,7 +25,7 @@ The main window allows the user to do almost everything they need to when it com
 The last item above, setting custom parameters have some quirks that need to be addressed:
 - In order to set custom parameters, the checkbox next to the parameter list needs to be toggled. Once you're done, it's recommended to toggle the checkbox again to ensure your changes are reflected back to the UI. Otherwise, if you start dumping, it will prompt you to make sure your edits are what you want to run instead of the settings in the UI.
 - Setting custom parameters overrides anything that is put into the UI. Even if it's not immediately reflected (such as path or system), it will still override anything set there. Keep that in mind if you set both custom parameters and other options in the UI. The recommendation is to do all UI options first, then do custom parameters, if applicable.
- Custom parameters are validated before attempting to run. This means that each wrapper implementation contains a full list of valid flags and combinations. This can lead to some issues if the base program has updated but DICUI has not. Use that at your own risk.
+- Custom parameters are validated before attempting to run. This means that each wrapper implementation contains a full list of valid flags and combinations. This can lead to some issues if the base program has updated but MPF has not. Use that at your own risk.

 ### Log Window
 [[dicui_log.png]]
@@ -36,16 +36,16 @@ The log window is an optional (but recommended) window that shows the current st

 [[dicui_options.png]]

-The options window contains most of the settings that can also be configured in the `DICUI.exe.config` file. The path, dump speed, and redump login sections are fairly self-describing. The options section may need more explanation, so see the list below for those details:
+The options window contains most of the settings that can also be configured in the `MPF.exe.config` file. The path, dump speed, and redump login sections are fairly self-describing. The options section may need more explanation, so see the list below for those details:

 - **Quiet Mode** - For dumping programs that support it, this setting adds the flag to remove any beeper or speaker sounds generated by the program.
 - **Paranoid Mode** - For adding flags that increase the amount of information displayed during a dump, help with super damaged discs, and for Aaru, also removes personally identifiable information from the output files.
 - **Reread Tries** - By default, most dumping programs allow for retrying damaged, misread, or otherwise errored sectors some set amount of times. This input allows users to set the value for programs that support it.
 - **Protection Scan** - Use the BurnOutSharp library to scan available discs after dumping. Due to the nature of the library, it cannot currently compete with Protection ID in terms of detection, but is still included to capture as much as possible. BurnOutSharp is currently a work in progress.
- **Skip Type Detect** - On loading of new media, DICUI can attempt to figure out what type of disc and system it is. If this is disabled, then it will default to the last selected options.
- **Add Placeholders** - When DICUI generates the submission information files, it can optionally include placeholder values to remind users to fill in certain bits of information that are not automatic. This will show up in both the submission information as well as the disc information popup.
+- **Skip Type Detect** - On loading of new media, MPF can attempt to figure out what type of disc and system it is. If this is disabled, then it will default to the last selected options.
+- **Add Placeholders** - When MPF generates the submission information files, it can optionally include placeholder values to remind users to fill in certain bits of information that are not automatic. This will show up in both the submission information as well as the disc information popup.
 - **Show Disc Info** - After dumping, there is an option to have a disc information popup appear that allows you to fill in common physical disc information, such as regions, langauges, titles, and ringcodes. It also allows users to see what information was pulled from Redump, if available.
 - **No Fixed Drives** - This option allows users to opt out of seeing fixed drives (such as hard drives) in their list of dumpable media. This can often help for users only interested in optical media.
 - **Reset After Dump** - For dumping programs that support it, this setting adds the ability to reset the drive after dumping. This can be useful for finicky and older drives that may have issues with reading multiple discs in a row. Currently, only DiscImageCreator supports this.

-Please note that changing which program is being used to dump can only be done in the `DICUI.exe.config` file manually. For more information about allowed values, see [Overview](https://github.com/SabreTools/DICUI/wiki/Overview).
+Please note that changing which program is being used to dump can only be done in the `MPF.exe.config` file manually. For more information about allowed values, see [Overview](https://github.com/SabreTools/MPF/wiki/Overview).
--- a/Home.md
+++ b/Home.md
@@ -1,21 +1,21 @@
-Welcome to the Wiki for the DICUI project! Here you will find information on the project, including how to build your own copy and other bits of helpful information.
+Welcome to the Wiki for the MPF project! Here you will find information on the project, including how to build your own copy and other bits of helpful information.

 ## Table of Contents
-* [Introduction](https://github.com/SabreTools/DICUI/wiki/Introduction)
-    * [History of the Project](https://github.com/SabreTools/DICUI/wiki/Introduction#history-of-the-project)
-    * [Future Development](https://github.com/SabreTools/DICUI/wiki/Introduction#future-development)
+* [Introduction](https://github.com/SabreTools/MPF/wiki/Introduction)
+    * [History of the Project](https://github.com/SabreTools/MPF/wiki/Introduction#history-of-the-project)
+    * [Future Development](https://github.com/SabreTools/MPF/wiki/Introduction#future-development)
 * Features
-    * [Components](https://github.com/SabreTools/DICUI/wiki/Components)
-    * [DICUI and DICUI.Avalonia](https://github.com/SabreTools/DICUI/wiki/DICUI)
-    * [DICUI Check](https://github.com/SabreTools/DICUI/wiki/DICUI-Check)
+    * [Components](https://github.com/SabreTools/MPF/wiki/Components)
+    * [MPF and MPF.Avalonia](https://github.com/SabreTools/MPF/wiki/MPF)
+    * [MPF Check](https://github.com/SabreTools/MPF/wiki/MPF-Check)
 * Supported Programs
-    * [Overview](https://github.com/SabreTools/DICUI/wiki/Overview)
-    * [Aaru](https://github.com/SabreTools/DICUI/wiki/Aaru)
-    * [CleanRip](https://github.com/SabreTools/DICUI/wiki/CleanRip)
-    * [DCDumper](https://github.com/SabreTools/DICUI/wiki/DCDumper)
-    * [dd for Windows](https://github.com/SabreTools/DICUI/wiki/dd)
-    * [DiscImageCreator](https://github.com/SabreTools/DICUI/wiki/DiscImageCreator)
-    * [UmdImageCreator](https://github.com/SabreTools/DICUI/wiki/UmdImageCreator)
+    * [Overview](https://github.com/SabreTools/MPF/wiki/Overview)
+    * [Aaru](https://github.com/SabreTools/MPF/wiki/Aaru)
+    * [CleanRip](https://github.com/SabreTools/MPF/wiki/CleanRip)
+    * [DCDumper](https://github.com/SabreTools/MPF/wiki/DCDumper)
+    * [dd for Windows](https://github.com/SabreTools/MPF/wiki/dd)
+    * [DiscImageCreator](https://github.com/SabreTools/MPF/wiki/DiscImageCreator)
+    * [UmdImageCreator](https://github.com/SabreTools/MPF/wiki/UmdImageCreator)
 * Development Information
-    * [Build a Local Copy](https://github.com/SabreTools/DICUI/wiki/Build-a-Local-Copy)
-    * [Coding Practices](https://github.com/SabreTools/DICUI/wiki/Coding-Practices)
+    * [Build a Local Copy](https://github.com/SabreTools/MPF/wiki/Build-a-Local-Copy)
+    * [Coding Practices](https://github.com/SabreTools/MPF/wiki/Coding-Practices)
--- a/Introduction.md
+++ b/Introduction.md
@@ -1,10 +1,10 @@
 # Introduction

-Hello and welcome to the latest info about **DICUI**! We are happy that you chose to use our software for your optical disc backup needs. But what exactly is **DICUI**? Why does it sound like a rude word? Are you feeling okay? Well, the first two can be answered, but the last one is up to you.
+Hello and welcome to the latest info about **MPF**! We are happy that you chose to use our software for your optical disc backup needs. But what exactly is **MPF**? Why does it sound like a rude word? Are you feeling okay? Well, the first two can be answered, but the last one is up to you.

 ## History of the Project

-DICUI was the brainchild of **ReignStumble**, who wanted to have a simple wrapper for the [DiscImageCreator](https://github.com/saramibreak/DiscImageCreator) program. At some point after a proof of concept, he recruited **darksabre76** who agreed to act as an advisor for coding stuff. Not long after they were joined by **Jakz** who had some big ideas around making the UI even better.
+MPF was the brainchild of **ReignStumble**, who wanted to have a simple wrapper for the [DiscImageCreator](https://github.com/saramibreak/DiscImageCreator) program. At some point after a proof of concept, he recruited **darksabre76** who agreed to act as an advisor for coding stuff. Not long after they were joined by **Jakz** who had some big ideas around making the UI even better.

 As time went on, **darksabre76** and **Jakz** did a lot more than they originally intended, eventually leading to a much more complete and technically impressive frontend for DiscImageCreator. It was at this point, things went a bit off the rails. **ReignStumble** decided to cede the project over to live under the [SabreTools](https://github.com/SabreTools/) project and gave the reigns over to **darksabre76**. Whether this was good or bad, we still don't know.

@@ -15,5 +15,5 @@ In the most recent history, **darksabre76** has been the primary maintainer of t
 ## Future Development

 Most of the work that needs to be done can be separated into two distinct areas:
- **UI Design** - A UI written and maintained by a backend programmer is not going to look good. It's stable, but needs a lot of love, so we encourage [Pull Requests](https://github.com/SabreTools/DICUI/pulls) for any new or updated functionality.
- **Program Support** - Unlike what its name suggests, **DICUI** does not just support DiscImageCreator anymore. Take a look at the [Overview](https://github.com/SabreTools/DICUI/wiki/Overview) for a handy chart about supported programs. Not all of those programs are supported as fully as DiscImageCreator, so help is requested there as well.
+- **UI Design** - A UI written and maintained by a backend programmer is not going to look good. It's stable, but needs a lot of love, so we encourage [Pull Requests](https://github.com/SabreTools/MPF/pulls) for any new or updated functionality.
+- **Program Support** - Unlike what its name suggests, **MPF** does not just support DiscImageCreator anymore. Take a look at the [Overview](https://github.com/SabreTools/MPF/wiki/Overview) for a handy chart about supported programs. Not all of those programs are supported as fully as DiscImageCreator, so help is requested there as well.
--- a/Supported/CleanRip.md
+++ b/Supported/CleanRip.md
@@ -4,8 +4,8 @@

 **Developer:** [emukidid](https://github.com/emukidid)

-**CleanRip** is a GameCube and Wii focused dumping program. Written in C/C++, it is meant to run directly off of a modified Wii console. Development is open, though there has been no development recently at time of writing. DICUI does not have the ability to run **CleanRip** but it can parse its outputs to generate submission information files.
+**CleanRip** is a GameCube and Wii focused dumping program. Written in C/C++, it is meant to run directly off of a modified Wii console. Development is open, though there has been no development recently at time of writing. MPF does not have the ability to run **CleanRip** but it can parse its outputs to generate submission information files.

-By default, **CleanRip** rips GameCube and Wii discs to a standard `ISO` format (possibly split, needs to be combined before parsing with DICUI). Also by default, media rips will include additional files representing various pieces of information about the image and the dumping process. It is recommended to include the hashes as part of the dumping process.
+By default, **CleanRip** rips GameCube and Wii discs to a standard `ISO` format (possibly split, needs to be combined before parsing with MPF). Also by default, media rips will include additional files representing various pieces of information about the image and the dumping process. It is recommended to include the hashes as part of the dumping process.

 For the purposes of Redump, **CleanRip** is the defacto standard for dumping GameCube and Wii discs. Most disc information required for submission is included in the output files.
--- a/Supported/DCDumper.md
+++ b/Supported/DCDumper.md
@@ -4,7 +4,7 @@

 **Developer:** jamjam

-**DCDumper** is a GD-ROM dumping program created specifically for Redump. Only a certain set of "swappable" drives are currently supported for the dumping process. Please see [GD-ROM Optical Disc Drive Compatibility](http://wiki.redump.org/index.php?title=DiscImageCreator:_Optical_Disc_Drive_Compatibility#GD-Rom) for more details. Development has ceased and no source code is available. DICUI does not have the ability to run **DCDumper** but it is planned to be able to parse its outputs to generate submission information files.
+**DCDumper** is a GD-ROM dumping program created specifically for Redump. Only a certain set of "swappable" drives are currently supported for the dumping process. Please see [GD-ROM Optical Disc Drive Compatibility](http://wiki.redump.org/index.php?title=DiscImageCreator:_Optical_Disc_Drive_Compatibility#GD-Rom) for more details. Development has ceased and no source code is available. MPF does not have the ability to run **DCDumper** but it is planned to be able to parse its outputs to generate submission information files.

 By default, **DCDumper** rips media to a split `BIN/CUE` format for the high-densitity area, such that every track has its own file. MORE INFORMATION ABOUT OUTPUT FILES IS REQUIRED, ALONG WITH ANY ADDITIONAL PROGRAMS THAT ARE NEEDED FOR DCDUMPER COMPLETE SUPPORT.

--- a/Supported/Overview.md
+++ b/Supported/Overview.md
@@ -1,15 +1,15 @@
 # Dumping Program Overview

-DICUI used to only be a frontend for DiscImageCreator (hence the name) but multiple dumpers and parsed outputs are now available. To make it easier on users, below is a table representing the various dumping programs and their relevant features.
+MPF used to only be a frontend for DiscImageCreator (hence the name) but multiple dumpers and parsed outputs are now available. To make it easier on users, below is a table representing the various dumping programs and their relevant features.

 | Program Name | Short Name | Can Dump | Can Check | Redump Compatible Output |
 |--------------|------------|----------|-----------|--------------------------|
-| [Aaru](https://github.com/SabreTools/DICUI/wiki/Aaru) | `aaru` | Yes | Yes | Partial |
-| [CleanRip](https://github.com/SabreTools/DICUI/wiki/CleanRip) | `cleanrip` | No | Yes | Partial |
-| [DCDumper](https://github.com/SabreTools/DICUI/wiki/DCDumper) | `dcd` | No | No | Yes |
-| [dd for Windows](https://github.com/SabreTools/DICUI/wiki/dd) | `dd` | Yes | No | No |
-| [DiscImageCreator](https://github.com/SabreTools/DICUI/wiki/DiscImageCreator) | `dic` | Yes | Yes | Yes |
-| [UmdImageCreator](https://github.com/SabreTools/DICUI/wiki/UmdImageCreator) | `uic` | No | Yes | Yes |
+| [Aaru](https://github.com/SabreTools/MPF/wiki/Aaru) | `aaru` | Yes | Yes | Partial |
+| [CleanRip](https://github.com/SabreTools/MPF/wiki/CleanRip) | `cleanrip` | No | Yes | Partial |
+| [DCDumper](https://github.com/SabreTools/MPF/wiki/DCDumper) | `dcd` | No | No | Yes |
+| [dd for Windows](https://github.com/SabreTools/MPF/wiki/dd) | `dd` | Yes | No | No |
+| [DiscImageCreator](https://github.com/SabreTools/MPF/wiki/DiscImageCreator) | `dic` | Yes | Yes | Yes |
+| [UmdImageCreator](https://github.com/SabreTools/MPF/wiki/UmdImageCreator) | `uic` | No | Yes | Yes |

 For users who are concerned about having exact matches to submit or verify against Redump, **DiscImageCreator** is essentially your only option. None of the other supported dumping tools can produce the full array of outputs that are used by Redump submissions. This is considered the standard for the Redump project which will likely not change anytime soon.

--- a/Supported/UmdImageCreator.md
+++ b/Supported/UmdImageCreator.md
@@ -4,7 +4,7 @@

 **Developer:** [Sarami](https://github.com/saramibreak)

-**UmdImageCreator** is a UMD focused dumping program created specifically for Redump. Written in C/C++, it is meant to run directly off of a modified PSP console. Development is semi-open, usually with the use of internal test versions before public commits, though there has been no active development recently. DICUI does not have the ability to run **UmdImageCreator** but it can parse its outputs to generate submission information files.
+**UmdImageCreator** is a UMD focused dumping program created specifically for Redump. Written in C/C++, it is meant to run directly off of a modified PSP console. Development is semi-open, usually with the use of internal test versions before public commits, though there has been no active development recently. MPF does not have the ability to run **UmdImageCreator** but it can parse its outputs to generate submission information files.

 By default, **UmdImageCreator** rips UMDs to a standard `ISO` format. Also by default, media rips will include additional files representing various pieces of information about the image, the dumping process, and the original hardware.

--- a/_Sidebar.md
+++ b/_Sidebar.md
@@ -1,18 +1,18 @@
-* [Introduction](https://github.com/SabreTools/DICUI/wiki/Introduction)
-    * [History of the Project](https://github.com/SabreTools/DICUI/wiki/Introduction#history-of-the-project)
-    * [Future Development](https://github.com/SabreTools/DICUI/wiki/Introduction#future-development)
+* [Introduction](https://github.com/SabreTools/MPF/wiki/Introduction)
+    * [History of the Project](https://github.com/SabreTools/MPF/wiki/Introduction#history-of-the-project)
+    * [Future Development](https://github.com/SabreTools/MPF/wiki/Introduction#future-development)
 * Features
-    * [Components](https://github.com/SabreTools/DICUI/wiki/Components)
-    * [DICUI and DICUI.Avalonia](https://github.com/SabreTools/DICUI/wiki/DICUI)
-    * [DICUI Check](https://github.com/SabreTools/DICUI/wiki/DICUI-Check)
+    * [Components](https://github.com/SabreTools/MPF/wiki/Components)
+    * [MPF and MPF.Avalonia](https://github.com/SabreTools/MPF/wiki/MPF)
+    * [MPF Check](https://github.com/SabreTools/MPF/wiki/MPF-Check)
 * Supported Programs
-    * [Overview](https://github.com/SabreTools/DICUI/wiki/Overview)
-    * [Aaru](https://github.com/SabreTools/DICUI/wiki/Aaru)
-    * [CleanRip](https://github.com/SabreTools/DICUI/wiki/CleanRip)
-    * [DCDumper](https://github.com/SabreTools/DICUI/wiki/DCDumper)
-    * [dd for Windows](https://github.com/SabreTools/DICUI/wiki/dd)
-    * [DiscImageCreator](https://github.com/SabreTools/DICUI/wiki/DiscImageCreator)
-    * [UmdImageCreator](https://github.com/SabreTools/DICUI/wiki/UmdImageCreator)
+    * [Overview](https://github.com/SabreTools/MPF/wiki/Overview)
+    * [Aaru](https://github.com/SabreTools/MPF/wiki/Aaru)
+    * [CleanRip](https://github.com/SabreTools/MPF/wiki/CleanRip)
+    * [DCDumper](https://github.com/SabreTools/MPF/wiki/DCDumper)
+    * [dd for Windows](https://github.com/SabreTools/MPF/wiki/dd)
+    * [DiscImageCreator](https://github.com/SabreTools/MPF/wiki/DiscImageCreator)
+    * [UmdImageCreator](https://github.com/SabreTools/MPF/wiki/UmdImageCreator)
 * Development Information
-    * [Build a Local Copy](https://github.com/SabreTools/DICUI/wiki/Build-a-Local-Copy)
-    * [Coding Practices](https://github.com/SabreTools/DICUI/wiki/Coding-Practices)
+    * [Build a Local Copy](https://github.com/SabreTools/MPF/wiki/Build-a-Local-Copy)
+    * [Coding Practices](https://github.com/SabreTools/MPF/wiki/Coding-Practices)