Releases: mitbailey/MMC
v0.4
Running the .exe will begin hardware detection. If auto-connect fails, the Device Manager will be presented. From here the user can select devices or re-try auto-connect. The user is also presented with the current status, a list of connected devices, and a list of compatible hardware. The user can choose to continue without hardware in 'dummy' mode (also known as Debug Mode). The program can also be started using Command Prompt opened in the .exe's directory and running mmc 1
to begin Debug Mode, which will allow use of the program with no communication with or need for hardware, or mmc
which will begin Hardware Mode.
Full Changelog: https://github.com/mitbailey/MMC/commits/v0.4
v0.3
Running the .exe will begin Hardware Mode, and will only work if the proper hardware is present and connected. Using Command Prompt opened in the .exe's directory and running mmc 1
will begin Debug Mode, which will allow use of the program with no communication with or need for hardware.
Full Changelog: https://github.com/mitbailey/MMC/commits/v0.3
v0.2
Running the .exe will begin Hardware Mode, and will only work if the proper hardware is present and connected. Using Command Prompt opened in the .exe's directory and running mmc 1
will begin Debug Mode, which will allow use of the program with no communication with or need for hardware.
Full Changelog: https://github.com/mitbailey/MMC/commits/v0.2
v0.1
Running the .exe will begin Hardware Mode, and will only work if the proper hardware is present and connected. Using Command Prompt opened in the .exe's directory and running mmc 1
will begin Debug Mode, which will allow use of the program with no communication with or need for hardware.
Full Changelog: https://github.com/mitbailey/MMC/commits/v0.1