LTKNotes: Difference between revisions

From Color 64 BBS Wiki
No edit summary
No edit summary
Line 13: Line 13:


: [[File:flatpak-vice.png|center|600px]]
: [[File:flatpak-vice.png|center|600px]]
:As you see above, the command <strong>net.sf.VICE</strong> is created as a result of the flatpak installation. Therefore, the new command in the vice.sh script can now be:
:As you see above, the command <strong>net.sf.VICE</strong> is created as a result of the flatpak installation. Therefore, the new command in the vice.sh script can now be:
:<strong>/var/lib/flatpak/exports/bin/net.sf.VICE -config Config/config.ini</strong> along withe the other options used in the script for the command.
:<strong>/var/lib/flatpak/exports/bin/net.sf.VICE -config Config/config.ini</strong> along withe the other options used in the script for the command.
Line 22: Line 23:
       -ltkimage1 DiskImages/ltkernal30-disk1.dlk \
       -ltkimage1 DiskImages/ltkernal30-disk1.dlk \
       -ltkimage2 DiskImages/ltkernal30-disk2.dlk
       -ltkimage2 DiskImages/ltkernal30-disk2.dlk
:Conversely, my Fedora script with flatpak installation of Vice had to be modified to the following:
:Conversely, my Fedora-version of the <strong>vice.sh</strong> script with flatpak installation of Vice had to be modified to the following:


  /var/lib/flatpak/exports/bin/net.sf.VICE -config Config/config.ini \
  /var/lib/flatpak/exports/bin/net.sf.VICE -config Config/config.ini \

Revision as of 01:46, 26 October 2025

Version 8.1a
Technical Support: Color 64 Discourse

Important LTK Notes

So I was a little naïve in thinking that the LTK install would be easy for everyone since it was easy for me. I had it originally installed on my Kubuntu 24.04 system. The problem is: there are a lot of Linux distro options, and they are unique in their ways and when I tested installation on my Fedora 43 KDE system, it failed to run. After some grooming, I got it to work. Out of those lessons-learned, here are some pointers to get your running:

1. Note location of your installation of the servers. Edit the batch (sh) files to match the location.
2. Likewise, ensure the command execution in the vice.sh file is correct. On my Fedora system, I used the Vice installation in Software manager which installs via Flatpak. When installed in this manner, Vice is normally launched with /bin/flatpack run --branch=stable --arch=x86_64 --command=x64sc net.sf.VICE" but it does not accept the -config attribute we need for the script. Because of this, my recommendation is to use the flatpak linked file created at /var/lib/flatpak/exports/bin location. See my picture below:
As you see above, the command net.sf.VICE is created as a result of the flatpak installation. Therefore, the new command in the vice.sh script can now be:
/var/lib/flatpak/exports/bin/net.sf.VICE -config Config/config.ini along withe the other options used in the script for the command.
To further clarify, in my Ubuntu configuration, the vice.sh script is as follows:
x64sc -config Config/config.ini \
      -cartcrt Bins/ltk.crt \
      -ltkimage0 DiskImages/ltkernal30-disk0.dlk \
      -ltkimage1 DiskImages/ltkernal30-disk1.dlk \
      -ltkimage2 DiskImages/ltkernal30-disk2.dlk
Conversely, my Fedora-version of the vice.sh script with flatpak installation of Vice had to be modified to the following:
/var/lib/flatpak/exports/bin/net.sf.VICE -config Config/config.ini \
      -cartcrt Bins/ltk.crt \
      -ltkimage0 DiskImages/ltkernal30-disk0.dlk \
      -ltkimage1 DiskImages/ltkernal30-disk1.dlk \
      -ltkimage2 DiskImages/ltkernal30-disk2.dlk
3. Ensure that the batch (sh) files have the appropriate "#!" call out (#!/bin/bash) for your system.
4. Perform chown and chmod 755 on all files downloaded as needed.
5. The primary script uses "xfce4-terminal" for the terminal windows. You don't have to install/use this. On my Fedora platform I used Konsole - so the command "xfce4-terminal -x" changed to "konsole -e". I also had to change the format of these commands where:
xfce4-terminal -x <location> <file> became
konsole -e <location/file>

Return to Software Installation