LTK Build Notes
- TCPSER, included with the install is preset for port 8502. If you desire to change it, modify the tcpser bat file (mybbs-tcpser.bat for Windows, mybbstcpser.sh for Linux) to change the port.
- Both the Linux and Windows builds require Vice to be pre-installed.
- D64 images are included in the build to use as a resource.
Windows LTK Notes
The main thing you need to know for Windows use is that you must modify the "mybbs-vice.bat" file to have the correct path to the Vice file x64sc.exe. You may have to tweak other parameters for sound and video, depending on your configuration.
LINUX 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 BBS. You may need to adjust the location specifications within the commands of the script (sh) files. As long as you didn't move directories or files around after you unzipped, it should be okay - but review to make sure.
- 2. Ensure the command execution in the vice.sh file is correct. I had a definite difference between Kubuntu and my Fedora installs that had to be adjusted.
- On Ubuntu, with installation of Vice through sudo apt install, the command x64sc would successfully launch Vice. Likewise, adding the command-line options along with the x64sc command worked normally.
- On Fedora that utilized flatpak, this completely changed. I used the Vice installation in Software manager (again, uses 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 command-line arguments 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 - which is generated when you perform the install of Vice. 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 xfce4-terminal - just use what terminal your system uses. On my Fedora platform I use Konsole, so the command "xfce4-terminal -x" was changed to "konsole -e" along with some formatting changes required. You can see the differences below:
- xfce4:
xfce4-terminal -x ./mybbs-tcpser.sh & xfce4-terminal -x ./mybbs-vice.sh &
- Konsole:
konsole -e ./mybbs-tcpser.sh & konsole -e ./mybbs-vice.sh &