LTKNotes - Revision history

Admin at 04:20, 26 October 2025

2025-10-26T04:20:56Z

← Older revision		Revision as of 04:20, 26 October 2025
Line 1:		Line 1:
	{{DISPLAYTITLE:~~Important~~ LTK Notes ~~for Running~~}}		{{DISPLAYTITLE:LTK Build Notes}}
	[[File:colorbanner.png\|center\|300px]]		[[File:colorbanner.png\|center\|300px]]
	<strong><center>Version 8.1a</center></strong>		<strong><center>Version 8.1a</center></strong>

Admin at 04:19, 26 October 2025

2025-10-26T04:19:58Z

← Older revision		Revision as of 04:19, 26 October 2025
Line 3:		Line 3:
	<strong><center>Version 8.1a</center></strong>		<strong><center>Version 8.1a</center></strong>
	<center>Technical Support: [https://www.itchybutt.org/c/bbs-corner/commodore-color-64/7 Color 64 Discourse]</center>		<center>Technical Support: [https://www.itchybutt.org/c/bbs-corner/commodore-color-64/7 Color 64 Discourse]</center>


	* TCPSER, included with the install is preset for port 8502. If you desire to change it, modify the tcpser bat file (<strong>mybbs-tcpser.bat</strong> for Windows, <strong>mybbstcpser.sh</strong> for Linux) to change the port.		* TCPSER, included with the install is preset for port 8502. If you desire to change it, modify the tcpser bat file (<strong>mybbs-tcpser.bat</strong> for Windows, <strong>mybbstcpser.sh</strong> for Linux) to change the port.
Line 9:		Line 10:

	* D64 images are included in the build to use as a resource.		* D64 images are included in the build to use as a resource.


	<strong>Windows LTK Notes</strong>		<strong>Windows LTK Notes</strong>

Admin at 04:19, 26 October 2025

2025-10-26T04:19:38Z

← Older revision		Revision as of 04:19, 26 October 2025
Line 3:		Line 3:
	<strong><center>Version 8.1a</center></strong>		<strong><center>Version 8.1a</center></strong>
	<center>Technical Support: [https://www.itchybutt.org/c/bbs-corner/commodore-color-64/7 Color 64 Discourse]</center>		<center>Technical Support: [https://www.itchybutt.org/c/bbs-corner/commodore-color-64/7 Color 64 Discourse]</center>

			* TCPSER, included with the install is preset for port 8502. If you desire to change it, modify the tcpser bat file (<strong>mybbs-tcpser.bat</strong> for Windows, <strong>mybbstcpser.sh</strong> 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.

	<strong>Windows LTK Notes</strong>		<strong>Windows LTK Notes</strong>

Admin at 04:14, 26 October 2025

2025-10-26T04:14:29Z

← Older revision		Revision as of 04:14, 26 October 2025
Line 6:		Line 6:
	<strong>Windows LTK Notes</strong>		<strong>Windows LTK Notes</strong>

	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 <strong>x64sc.exe</strong>. You may have to tweak other parameters for sound and video, depending on your configuration.		The main thing you need to know for Windows use is that you must modify the "<strong>mybbs-vice.bat</strong>" file to have the correct path to the Vice file <strong>x64sc.exe</strong>. You may have to tweak other parameters for sound and video, depending on your configuration.

	<strong>LINUX LTK Notes</strong>		<strong>LINUX LTK Notes</strong>

Admin at 04:14, 26 October 2025

2025-10-26T04:14:04Z

← Older revision		Revision as of 04:14, 26 October 2025
Line 5:		Line 5:

	<strong>Windows LTK Notes</strong>		<strong>Windows LTK Notes</strong>

	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 <strong>x64sc.exe</strong>. You may have to tweak other parameters for sound and video, depending on your configuration.		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 <strong>x64sc.exe</strong>. You may have to tweak other parameters for sound and video, depending on your configuration.

Admin at 04:13, 26 October 2025

2025-10-26T04:13:52Z

← Older revision		Revision as of 04:13, 26 October 2025
Line 4:		Line 4:
	<center>Technical Support: [https://www.itchybutt.org/c/bbs-corner/commodore-color-64/7 Color 64 Discourse]</center>		<center>Technical Support: [https://www.itchybutt.org/c/bbs-corner/commodore-color-64/7 Color 64 Discourse]</center>

	<strong>~~Important~~ LTK Notes</strong>		<strong>Windows LTK Notes</strong>
			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 <strong>x64sc.exe</strong>. You may have to tweak other parameters for sound and video, depending on your configuration.

			<strong>LINUX LTK Notes</strong>

	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:		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 ~~definitely groom~~ to make sure.		: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.		: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.

Admin at 02:28, 26 October 2025

2025-10-26T02:28:30Z

← Older revision		Revision as of 02:28, 26 October 2025
Line 37:		Line 37:
	:4. Perform <strong>chown</strong> and <strong>chmod 755</strong> on all files downloaded as needed.		:4. Perform <strong>chown</strong> and <strong>chmod 755</strong> 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~~:		: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:
	:: ~~<strong>~~xfce4-terminal -x ~~<location> <file><~~/~~strong> became~~
	:: ~~<strong>~~konsole -e ~~<location~~/~~file><~~/~~strong>~~		:xfce4:
			xfce4-terminal -x ./mybbs-tcpser.sh &
			xfce4-terminal -x ./mybbs-vice.sh &

			:Konsole:
			konsole -e ./mybbs-tcpser.sh &
			konsole -e ./mybbs-vice.sh &


	[[defaultsite\|Return to Software Installation]]		[[defaultsite\|Return to Software Installation]]

Admin at 02:18, 26 October 2025

2025-10-26T02:18:23Z

← Older revision		Revision as of 02:18, 26 October 2025
Line 12:		Line 12:
	: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.		: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 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 <strong>/bin/flatpack run --branch=stable --arch=x86_64 --command=x64sc net.sf.VICE"</strong> 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 <strong>/var/lib/flatpak/exports/bin</strong> location - which is generated when you perform the install of Vice. See my picture below:		::* 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 <strong>/bin/flatpack run --branch=stable --arch=x86_64 --command=x64sc net.sf.VICE</strong> 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 <strong>/var/lib/flatpak/exports/bin</strong> location - which is generated when you perform the install of Vice. See my picture below:

	:: [[File:flatpak-vice.png\|center\|600px]]		:: [[File:flatpak-vice.png\|center\|600px]]

Admin at 02:17, 26 October 2025

2025-10-26T02:17:48Z

← Older revision		Revision as of 02:17, 26 October 2025
Line 11:		Line 11:

	: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.		: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 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 <strong>/bin/flatpack run --branch=stable --arch=x86_64 --command=x64sc net.sf.VICE"</strong> 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 <strong>/var/lib/flatpak/exports/bin</strong> location - which is generated when you perform the install of Vice. See my picture below:		::* 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 <strong>/bin/flatpack run --branch=stable --arch=x86_64 --command=x64sc net.sf.VICE"</strong> 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 <strong>/var/lib/flatpak/exports/bin</strong> location - which is generated when you perform the install of Vice. See my picture below:

	:: [[File:flatpak-vice.png\|center\|600px]]		:: [[File:flatpak-vice.png\|center\|600px]]

Admin at 02:16, 26 October 2025

2025-10-26T02:16:52Z

← Older revision		Revision as of 02:16, 26 October 2025
Line 8:		Line 8:
	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:		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~~.		: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 definitely groom to make sure.

	: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 <strong>/bin/flatpack run --branch=stable --arch=x86_64 --command=x64sc net.sf.VICE"</strong> but it does not accept the ~~<strong>~~-~~config</strong> attribute~~ we need for the script. Because of this, my recommendation is to use the flatpak linked file created at <strong>/var/lib/flatpak/exports/bin</strong> location. See my picture below:		: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 <strong>/bin/flatpack run --branch=stable --arch=x86_64 --command=x64sc net.sf.VICE"</strong> 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 <strong>/var/lib/flatpak/exports/bin</strong> location - which is generated when you perform the install of Vice. See my picture below:

	: [[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.

	:To further clarify, in my Ubuntu configuration, the <strong>vice.sh</strong> script is as follows:		::To further clarify, in my Ubuntu configuration, the <strong>vice.sh</strong> script is as follows:
	x64sc -config Config/config.ini \		x64sc -config Config/config.ini \
	-cartcrt Bins/ltk.crt \		-cartcrt Bins/ltk.crt \
Line 23:		Line 25:
	-ltkimage1 DiskImages/ltkernal30-disk1.dlk \		-ltkimage1 DiskImages/ltkernal30-disk1.dlk \
	-ltkimage2 DiskImages/ltkernal30-disk2.dlk		-ltkimage2 DiskImages/ltkernal30-disk2.dlk
	:Conversely, my Fedora-version of the <strong>vice.sh</strong> 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 \