Anleitung : THEC64 modding:The C64 GameTool - Eigene Spiele hinzufügen, ohne UART, neue einfache Methode über Firmware update und Windows Tool

The C64 MOD - Modifizieren des C64 Maxi/Mini - NEUE Methode mit dem Windows Tool The C64 Game Tool- Spiele im Karussel austauschen

Obwohl der C64 Maxi nun Spiele von einem USB-Stick ausführen kann, ist es sinnvoll, die Spielesammlung neu zu organisieren und andere Spiele über den eingebauten Launcher zu starten. Hier erkläre ich den Prozess des Zugriffs auf den Core und das Hinzufügen von Spielen.
Hier wird eine einfache Methode beschrieben, die ohne UART-Adapter, also OHNE Löten funktioniert.

Das ganze funktioniert sehr einfach mit dem Windows Tool The C64 Game Tool
Es wir lediglich ein USB-Stick benötigt.

s1.PNG

Es handelt sich bei dem Tool um eine BETA Version !!!

Viel Spass beim ausprobieren !

ier mal ein Auszug was der Entwickler noch vorhat :

---------------

FWGUI

- Make retro gfx for buttons

- Add support for easyflash crt

- Store last window pos and size for next startup

- Add small border to description to make it look more like the original

- Fix unicode / UTF8 description problem

- Change user game folder to windows documents/TheC64GameTool

- Add support for loading bmp and jpg files and perhaps gif

- Menu for joystick

- Menu for machine type

- Convert screen shots png's to 16 colors

- Fix Basic .tsg for the mini so users can add it back. Basic does not have a game file attached!

ARM INSTALLER

- Check space left on nandb before installing games

* Make sure the TheC64 wont stop working if user adds to many games??

- Fix nanda backup. Atm it's not a valid image

---------

- Option to change carousel music (/usr/share/the64/ui/sounds/rgl.wav)

- Change startup picture (/usr/share/the64/ui/textures/rgl_splash.png)

- Change joystic definitions (/usr/share/the64/ui/data/gamecontrollerdb.txt)

- Search lemon64.com for cover and screen shots

Known issues:

- CRT files wont load in vice

- Large png files made the app crash / stop working??

* FIXED - Path to the tool can NOT contain space.

* FIXED - Some png images wont convert like "hawksmill_02.png"

Finished:

OK - More work on resize worker dialog

OK - Add edit support

OK - Add Delete support in GUI

OK - Add drop down menu with about

OK - Add new game when pressing insert key on kb

OK - Add support for .t64 files

OK - Add support for deleting games on the TheC64

OK - Make own arm installer with GUI that will run on the TheC64

OK - Add "run vice" so user can collect snapshot and screen shots

OK - if a .tsg file is missing a path then tell user what game it is that is broken

OK - Check number of games left after deleting and make sure it will never gow below 6!

OK - Check number of games before installing and make sure it wong go above 150.

OK - Sort games by name

OK - Backup nanda, nandb and the /usr/share/ directory

OK - hawksmill_02.png image wont convert!

@AntaBaka

coole Bastelseite hast du !!!!!

Ja, aber nur über UART...

Deswegen der Warnhinweis : max 150 !!!!!

Also, am besten mal mit diesem Tool (unten im Video) versuchen die Games zu löschen..

Musst halt ein bisschen fummeln..

Ja, du kannst sie hiermit Endpacken und wieder packen :

decodefw_v02.zip

------------------------------

TheC64 firmware encoder / decoder coded by raxrip.

How to use.

* For decoding a firmware file use: "decodefw.exe <firmware file>"

ex.

decodefw.exe theC64-1_3_1.bin

This should decode the firmware and create some files in your current dir. These files are:

installer.enc # The sfx installer that contain the encrypted version of the installer.dec

installer.dec # The decrypted installer in the sfx file. This is the file that will mount nandb and unpack the tar.gz file

payload0.tar.gz # The tar.gz container files that contains the new update for your system

# There might be up to four of these files numbered from 0 to 3

To modify the firmware then copy the tar.gz files to your favorite linux distro and unpack. When finish modifying create a tar.gz and use this file

when creating a new firmware. Make sure that you don't change any file access rights in the container file.

---------------------------------------------------------------------------------

* For encoding a new firmware file use: decodefw.exe <version> <installer.enc> <container0> <..> <..> <..> <outfile>

The <..> are optional container files and you can add a maximum of four containers.

IMPORTANT: Use the encrypted installer and NOT the decrypted version that you also can find in your current dir.

ex.

decodefw.exe 1003001 installer.enc payload0.tar.gz payload1.tar.gz payload2.tar.gz theC64-1_3_1.bin

Make sure that you enter the correct version number in the same way as you see it when decoding.

As far as I know the firmware file name must start with "theC64-" and contain the version number. I think this was checked when updating.

Pleas contact me on the forum if you have any questions regarding this.

- raxrip -