Hardware - Revision history

Admin at 15:49, 27 February 2026

2026-02-27T15:49:15Z

← Older revision		Revision as of 15:49, 27 February 2026
Line 108:		Line 108:
	<li>Acia1Enable=1 </li>		<li>Acia1Enable=1 </li>
	<li>Acia1Mode=2 </li>		<li>Acia1Mode=2 </li>
	<li>LTKimage0="/~~home/Color64_81a_servers/production~~/DiskImages/kernal-disk0.dlk" </li>		<li>LTKimage0="/mydir/DiskImages/kernal-disk0.dlk" </li>
	<li>LTKimage1="/~~home/Color64_81a_servers/production~~/DiskImages/kernal-disk1.dlk" </li>		<li>LTKimage1="/mydir/DiskImages/kernal-disk1.dlk" </li>
	<li>LTKimage2="/~~home/Color64_81a_servers/production~~/DiskImages/kernal-disk2.dlk" </li>		<li>LTKimage2="/mydir/DiskImages/kernal-disk2.dlk" </li>
	<li>DriveSoundEmulation=1 </li>		<li>DriveSoundEmulation=1 </li>
	<li>DriveSoundEmulationVolume=2007 </li>		<li>DriveSoundEmulationVolume=2007 </li>
Line 121:		Line 121:
	\|-		\|-
	\|Vice Execution Command		\|Vice Execution Command
	\|x64sc -config /~~home/Color64_81a_servers/production/Config~~/config.ini -cartcrt /~~home/Color64_81a_servers/production~~/Bins/ltk.crt		\|x64sc -config /mydir/config.ini -cartcrt /mydir/Bins/ltk.crt
	\|}		\|}

			(in the above - change "mydir" to your installation directory)

	Next section: [[overlays\|The Program Overlays]]		Next section: [[overlays\|The Program Overlays]]

	[[Introduction\|Introduction]]		[[Introduction\|Introduction]]

Admin at 17:17, 23 February 2026

2026-02-23T17:17:56Z

Admin at 22:42, 15 February 2026

2026-02-15T22:42:11Z

Show changes

Admin at 21:17, 18 October 2025

2025-10-18T21:17:27Z

← Older revision		Revision as of 21:17, 18 October 2025
Line 1:		Line 1:
			{{DISPLAYTITLE:Hardware Support}}
	[[Introduction\|Introduction]] - <strong>Hardware Support</strong>		[[Introduction\|Introduction]] - <strong>Hardware Support</strong>

Admin at 03:02, 9 October 2025

2025-10-09T03:02:19Z

← Older revision		Revision as of 03:02, 9 October 2025
Line 69:		Line 69:
	\|x64sc -config /home/Color64_81a_servers/production/Config/config.ini -cartcrt /home/Color64_81a_servers/production/Bins/ltk.crt		\|x64sc -config /home/Color64_81a_servers/production/Config/config.ini -cartcrt /home/Color64_81a_servers/production/Bins/ltk.crt
	\|}		\|}

			Next section: [[overlays\|The Program Overlays]]

	[[Introduction\|Introduction]]		[[Introduction\|Introduction]]

Admin at 14:27, 4 October 2025

2025-10-04T14:27:03Z

← Older revision		Revision as of 14:27, 4 October 2025
Line 1:		Line 1:
	[[Introduction\|Introduction]] - <strong>Hardware Support</strong>		[[Introduction\|Introduction]] - <strong>Hardware Support</strong>

	~~<strong>Hardware Support</strong>~~

	This BBS system operates on native hardware (with almost any combination of disk drives to include SD2IEC), emulated hardware like VICE, or newer builds of the Commodore such as Commodore Ultimate Elite II with IEC capability. It operates well with 1581 disk drives (or D81 images), but they are not recommended for any sections of the BBS that require REL file creation (like the system’s PASSWORD file or games that create these types of files). You can potentially work around the limitation by creating the REL file on an alternate drive type (like 1541) and then copying the REL file over to the 1581 (or D81 image) with a good REL file copier like COPYALL.		This BBS system operates on native hardware (with almost any combination of disk drives to include SD2IEC), emulated hardware like VICE, or newer builds of the Commodore such as Commodore Ultimate Elite II with IEC capability. It operates well with 1581 disk drives (or D81 images), but they are not recommended for any sections of the BBS that require REL file creation (like the system’s PASSWORD file or games that create these types of files). You can potentially work around the limitation by creating the REL file on an alternate drive type (like 1541) and then copying the REL file over to the 1581 (or D81 image) with a good REL file copier like COPYALL.

Admin at 14:26, 4 October 2025

2025-10-04T14:26:45Z

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

	This BBS system operates on native hardware (with almost any combination of disk drives to include SD2IEC), emulated hardware like VICE, or newer builds of the Commodore such as Commodore Ultimate Elite II with IEC capability. It operates well with 1581 disk drives (or D81 images), but they are not recommended for any sections of the BBS that require REL file creation (like the system’s PASSWORD file or games that create these types of files). You can potentially work around the limitation by creating the REL file on an alternate drive type (like 1541) and then copying the REL file over to the 1581 (or D81 image) with a good REL file copier like COPYALL.		This BBS system operates on native hardware (with almost any combination of disk drives to include SD2IEC), emulated hardware like VICE, or newer builds of the Commodore such as Commodore Ultimate Elite II with IEC capability. It operates well with 1581 disk drives (or D81 images), but they are not recommended for any sections of the BBS that require REL file creation (like the system’s PASSWORD file or games that create these types of files). You can potentially work around the limitation by creating the REL file on an alternate drive type (like 1541) and then copying the REL file over to the 1581 (or D81 image) with a good REL file copier like COPYALL.



	Special configurations this system will support include:		Special configurations this system will support include:

Admin at 14:26, 4 October 2025

2025-10-04T14:26:29Z

← Older revision		Revision as of 14:26, 4 October 2025
Line 1:		Line 1:
			[[Introduction\|Introduction]] - <strong>Hardware Support</strong>

	<strong>Hardware Support</strong>		<strong>Hardware Support</strong>

Line 71:		Line 73:
	\|x64sc -config /home/Color64_81a_servers/production/Config/config.ini -cartcrt /home/Color64_81a_servers/production/Bins/ltk.crt		\|x64sc -config /home/Color64_81a_servers/production/Config/config.ini -cartcrt /home/Color64_81a_servers/production/Bins/ltk.crt
	\|}		\|}

			[[Introduction\|Introduction]]

Admin: Protected "Hardware" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

2025-10-03T21:52:44Z

Protected "Hardware" ([Edit=Allow only administrators] (indefinite) [Move=Allow only administrators] (indefinite))

← Older revision	Revision as of 21:52, 3 October 2025
(No difference)

Admin at 22:51, 30 September 2025

2025-09-30T22:51:57Z

← Older revision		Revision as of 22:51, 30 September 2025
Line 24:		Line 24:
	<li><u>Vice:</u> Vice works seamlessly with Color 64 when properly configured and either with Jim Brain’s TCPSER or BBS Server. The storage capacity for the BBS when run in a VICE environment can be extremely large depending on your configuration (example: running in a LT Kernal (LTK) or CMD drive environment). I have two BBS systems that run in the LTK environment. The advantage of this environment is the near-immediate loading times of modules which can nearly match loading times of a RAM expander/REU. Of course, you could also emulate a REU with VICE as well. Below is an example of my VICE settings for my BBS Systems, configured for LTK (with three disk images) and Swiftlink modem speed. It requires a cartridge image for LT Kernal and formatted disk images ready for use. The example is from Vice in a Linux environment using version 3.9.		<li><u>Vice:</u> Vice works seamlessly with Color 64 when properly configured and either with Jim Brain’s TCPSER or BBS Server. The storage capacity for the BBS when run in a VICE environment can be extremely large depending on your configuration (example: running in a LT Kernal (LTK) or CMD drive environment). I have two BBS systems that run in the LTK environment. The advantage of this environment is the near-immediate loading times of modules which can nearly match loading times of a RAM expander/REU. Of course, you could also emulate a REU with VICE as well. Below is an example of my VICE settings for my BBS Systems, configured for LTK (with three disk images) and Swiftlink modem speed. It requires a cartridge image for LT Kernal and formatted disk images ready for use. The example is from Vice in a Linux environment using version 3.9.

	~~<p style~~="~~text~~-~~align: center;"><strong>Vice~~ Settings Example~~</strong></p>~~		{\| class="wikitable
	~~<table>~~		\|-
	~~<tr><th>File</th><th>~~Settings~~</th></tr>~~		\|+VICE Settings Example
	~~<tr><td>~~config.ini~~</td>~~		! File
	~~<td>~~<ul style="list-style: none;">		! Settings
			\|-
			\| config.ini
			\| <ul style="list-style: none;">
	<li>[Version]</li>		<li>[Version]</li>
	<li></li>		<li></li>
Line 64:		Line 67:
	<li>DosName4000="901468-14-16.bin" </li>		<li>DosName4000="901468-14-16.bin" </li>
	</ul>		</ul>
	~~</td></tr>~~		\|-
	~~<tr><td>~~Vice Execution Command~~</td>~~		\|Vice Execution Command
	~~<td>~~x64sc -config /home/Color64_81a_servers/production/Config/config.ini -cartcrt /home/Color64_81a_servers/production/Bins/ltk.crt ~~</td></tr>~~		\|x64sc -config /home/Color64_81a_servers/production/Config/config.ini -cartcrt /home/Color64_81a_servers/production/Bins/ltk.crt
	~~</table>~~		\|}

← Older revision		Revision as of 17:17, 23 February 2026
Line 1:		Line 1:
	{{DISPLAYTITLE:Hardware Support}}		{{DISPLAYTITLE:Hardware Support}}
			== Hardware Support ==

	[[Introduction\|Introduction]] - <strong>Hardware Support</strong>		[[Introduction\|Introduction]] - <strong>Hardware Support</strong>

Line 5:		Line 7:

	1581 disk drives and D81 images are fully usable for most areas of the system. However, they are not recommended for components that require the creation of REL files, such as the system PASSWORD file or certain games that generate REL data. If necessary, this limitation can be addressed by creating the REL file on a 1541-compatible drive and then transferring it to the 1581 or D81 image using a reliable REL file copy utility such as COPYALL.		1581 disk drives and D81 images are fully usable for most areas of the system. However, they are not recommended for components that require the creation of REL files, such as the system PASSWORD file or certain games that generate REL data. If necessary, this limitation can be addressed by creating the REL file on a 1541-compatible drive and then transferring it to the 1581 or D81 image using a reliable REL file copy utility such as COPYALL.

			=== Specialized Configurations ===

	Special configurations this system will support include:		Special configurations this system will support include:
	* '''Commodore RAM Expansion Units (REU)~~'''~~		==== Commodore RAM Expansion Units (REU) ====
	** Requires a minimum of 256K capacity.		* Requires a minimum of 256K capacity.
	** Utilizes the REU as a high-speed virtual disk through the included RAMDOS utility and automated file transfer routines.		* Utilizes the REU as a high-speed virtual disk through the included RAMDOS utility and automated file transfer routines.
	** The bundled RAMDOS version supports REUs expanded up to 2MB, providing near-instant load and save performance.		* The bundled RAMDOS version supports REUs expanded up to 2MB, providing near-instant load and save performance.

	* '''CMD RamLink~~'''~~		==== CMD RamLink ====
	** Compatible with the CMD RamLink device from Creative Micro Designs.		* Compatible with the CMD RamLink device from Creative Micro Designs.
	** May be used with a CMD HD to take advantage of the parallel interface.		* May be used with a CMD HD to take advantage of the parallel interface.
	** If equipped with a RamCard and installed RAM, the automatic RAM-disk functionality may also be utilized.		* If equipped with a RamCard and installed RAM, the automatic RAM-disk functionality may also be utilized.

	* '''Skyles 1541 Flash!~~'''~~		==== Skyles 1541 Flash! ====
	** Supported on device number 8 only.		* Supported on device number 8 only.
	** Significantly improves 1541 performance.		* Significantly improves 1541 performance.
	** Once installed, the system automatically detects device 8 and adjusts operation accordingly.		* Once installed, the system automatically detects device 8 and adjusts operation accordingly.

	* '''Traditional Modems~~'''~~		==== Traditional Modems ====
	** Supports fully Hayes-compatible modems using the standard AT command set.		* Supports fully Hayes-compatible modems using the standard AT command set.
	** Some models may require configuration adjustments.		* Some models may require configuration adjustments.
	** Example requiring modification: Avatex 1200 Low-Cost modem (not the HC or 2400 variants).		* Example requiring modification: Avatex 1200 Low-Cost modem (not the HC or 2400 variants).

	* '''WiFi Modems~~'''~~		==== WiFi Modems ====
	** Compatible with Hayes AT–based WiFi modems such as WiModem.		* Compatible with Hayes AT–based WiFi modems such as WiModem.
	** Example initialization string: ate0x1s0=0s10=30v1		* Example initialization string: ate0x1s0=0s10=30v1

	* '''Emulated Modem (VICE)~~'''~~		==== Emulated Modem (VICE) ====
	** Requires TCPSER or BBS Server.		* Requires TCPSER or BBS Server.
	** SwiftLink emulation supports speeds up to 38,400 baud.		* SwiftLink emulation supports speeds up to 38,400 baud.
	** Example TCPSER initialization string: ate0v1h0x1m0b1		* Example TCPSER initialization string: ate0v1h0x1m0b1

	:<p>The best modem to use is one that can be programmed not to auto-answer (ATS0=0) and will accept the command ATA to answer the phone when the phone rings. For 1200 baud operation a Hayes Smartmodem 1200, Volksmodem 12, the Commodore 1670 modem (the version that has 4 switches on the back of it) and most other Hayes-compatibles modems will operate in this mode. If you are using a Hayes Smartmodem 1200, set the internal DIP switches 3, 5, and 8 down, all others up. If you are using the 1670, switch 3 up and all the other switches down.</p>		:<p>The best modem to use is one that can be programmed not to auto-answer (ATS0=0) and will accept the command ATA to answer the phone when the phone rings. For 1200 baud operation a Hayes Smartmodem 1200, Volksmodem 12, the Commodore 1670 modem (the version that has 4 switches on the back of it) and most other Hayes-compatibles modems will operate in this mode. If you are using a Hayes Smartmodem 1200, set the internal DIP switches 3, 5, and 8 down, all others up. If you are using the 1670, switch 3 up and all the other switches down.</p>
	:<p>For 2400 baud operation, a Hayes Smartmodem 2400 or good compatible is required. Without SwiftLink the C64 must be programmed very carefully to be able to support 2400 baud, and the quality of modem and phone line are very important. Please refer to the section in "Specific Hardware Requirements" for instructions on setting up for 2400 baud use.</p>		:<p>For 2400 baud operation, a Hayes Smartmodem 2400 or good compatible is required. Without SwiftLink the C64 must be programmed very carefully to be able to support 2400 baud, and the quality of modem and phone line are very important. Please refer to the section in "Specific Hardware Requirements" for instructions on setting up for 2400 baud use.</p>

	* '''CMD SwiftLink Interface~~'''~~		==== CMD SwiftLink Interface ====
	** Required for communication speeds above 2400 BPS.		* Required for communication speeds above 2400 BPS.
	** The SwiftLink RS-232 interface from Creative Micro Designs connects via the cartridge port.		* The SwiftLink RS-232 interface from Creative Micro Designs connects via the cartridge port.
	** Supports communication rates up to 38,400 BPS with improved reliability.		* Supports communication rates up to 38,400 BPS with improved reliability.
	** Enables use of modem compression protocols such as MNP (Microcom Networking Protocol).		* Enables use of modem compression protocols such as MNP (Microcom Networking Protocol).
	** Compatible with Hayes-compatible high-speed modems.		* Compatible with Hayes-compatible high-speed modems.

	* '''Schnedler TurboMaster CPU~~'''~~		==== Schnedler TurboMaster CPU ====
	** Supports operation at 4.09 MHz, increasing overall system speed significantly.		* Supports operation at 4.09 MHz, increasing overall system speed significantly.
	** Connects through the cartridge port.		* Connects through the cartridge port.
	** May be combined with SwiftLink for maximum performance.		* May be combined with SwiftLink for maximum performance.
	** Requires the Master Adaptor configured to GEORAM mode when used with SwiftLink.		* Requires the Master Adaptor configured to GEORAM mode when used with SwiftLink.
	** SwiftLink I/O address should remain at the factory default of $DE00 unless hardware compatibility has been verified.		* SwiftLink I/O address should remain at the factory default of $DE00 unless hardware compatibility has been verified.
	** Although no longer produced, used units may still be available.		* Although no longer produced, used units may still be available.

	* '''SD2IEC Drives~~'''~~		==== SD2IEC Drives ====
	** Supports both native directory mode and D64/D81 disk images.		* Supports both native directory mode and D64/D81 disk images.
	** Native mode offers substantial storage capacity.		* Native mode offers substantial storage capacity.
	** REL file creation in native mode may present issues.		* REL file creation in native mode may present issues.
	** Recommended workaround: create REL files on a 1541 disk or within VICE on a D64 image, then transfer using a reliable REL file copier.		* Recommended workaround: create REL files on a 1541 disk or within VICE on a D64 image, then transfer using a reliable REL file copier.
	** Directory navigation examples:		* Directory navigation examples:
	*** !CD// — change to root directory		** !CD// — change to root directory
	*** !CD//AUX3 — change to AUX3 directory		** !CD//AUX3 — change to AUX3 directory
	** In DOS Wedge mode, use:		* In DOS Wedge mode, use:
	*** CD//		** CD//
	*** CD//AUX3		** CD//AUX3

	* '''VICE Emulator~~'''~~		==== VICE Emulator ====
	** Fully compatible when configured with TCPSER or BBS Server.		* Fully compatible when configured with TCPSER or BBS Server.
	** Supports SwiftLink emulation up to 38,400 baud.		* Supports SwiftLink emulation up to 38,400 baud.
	** Storage capacity depends on configuration, including LT Kernal (LTK) or CMD drive environments.		* Storage capacity depends on configuration, including LT Kernal (LTK) or CMD drive environments.
	** LTK environments provide near-instant module loading similar to REU performance.		* LTK environments provide near-instant module loading similar to REU performance.
	** REU emulation is also supported within VICE.		* REU emulation is also supported within VICE.
	{\| class="wikitable		{\| class="wikitable
	\|-		\|-