Hi everyone!
I have made several modifications to MiSTer_Main to support the TapTo device:
- Detection of the ACR122U reader in the menu.
- x86 support through CMOS memory, using the TapTo API service.
I have not yet made a pull request to the official repository for two reasons. One, I would like it to be well tested, and second, because I am waiting for wizzo to make an API improvement that allows to identify the reader used, so that in the menu we do not only support the detection of the ACR122U reader.
I attach a basic application I have made to launch a game or application from MSDos, either from the ao486 kernel or the PCXT/Tandy cores.
You just have to call it from the autoexec.bat, and configure the tapto.cfg file, example:
Code: Select all
E388882F,C:\GAMES\CAT\TANDYCAT.EXE
A141882F,C:\GAMES\WOLF3D\WOLF3D.EXE
The first element of each line is the UUID of an NFC card, the second element is the mapping associated with the path to a game or application you want to run. If instead of a path, you indicate "SYSTEM", you will be telling the application that the card corresponds to one corresponding to the core, I for example have a specific card for ao486 and another one for PCXT/Tandy... in this way, it will not indicate anything and nothing will be executed, it will just show the command prompt. Any other unrecognised card in the list will show its UUID along with a message that it is unknown.
In addition:
-
In the autoexec.bat, at the end of it, tapto.exe must be executed for ao486 and tapto.exe 0x2c0 for PCXT/Tandy.
-
At the end of the autoexec.bat, after tapto.exe, tapto.bat must be executed, this file is auto-created by tapto.exe.
-
The cards must be previously configured from the taptui script with the core to be executed, the ao486 or the PCXT/Tandy one.
I attach also the sources of this application, in the future I will add it to my own GitHub repository.
Note:
From now on, all the news about the new-features fork in the following thread: