Ltkernal: Difference between revisions

Latest revision as of 17:20, 23 February 2026

Specific System Requirements – Lt. Kernal HD

Lt. Kernal Hard Drive

The Xetec Lt. Kernal Hard Drive system is well suited for running Color 64. It supports up to nine Logical Units (LUs), each containing fifteen “users” that function similarly to subdirectories. This structure allows for as many as 135 distinct storage areas.

Color 64 cannot use Lt. Kernal and RAMDOS simultaneously if an REU is installed alongside the hard drive.

Hardware Requirements

When operating on a Commodore 64, the HIRAM connector must be properly installed as described in the Lt. Kernal documentation. Without the HIRAM connection, the system will not function correctly.

If you are using a Commodore 128 in 64 mode, the ribbon cable connecting the computer to the Host Adapter automatically handles the HIRAM signal.

Run the CONFIGURE utility and verify that the NMI TRAP setting is disabled (set to 0) for Commodore 64 mode. If NMI TRAP is not set to 0, callers may experience line noise during modem communication.

In the BOOTMAKER program, ensure that you answer “Y” to the Lt. Kernal configuration prompt. Failure to do so may result in garbled modem communication.

Accessing Logical Units

Color 64 accesses Lt. Kernal storage using the “ldlu” and “i” drive commands.

The syntax for the ldlu command is:

l<device><LU><USER>

Example: To access LU 2, USER 5 on device 8: l825

For users 10 through 15, hexadecimal values A through F are used.

Example: LU 3, USER 11 on device 8: l83b

For LUs 2 through 9, you must also include an initialization command in SETUP.

Example: To initialize LU 3: i3

When combined: l83b!i3

Separate individual disk commands with an exclamation point (!).

Faster Disk Access

If your Lt. Kernal uses DOS version 7.1 or later, faster disk access can be achieved by merging optional enhancement routines into specific overlays. These merges are not required for normal operation.

Merge the following files:

lkf.init → √bbs.init
lkf.msgs → √bbs.msgs
lkf.xfer → √bbs.xfer
lkf.ovl → √bbs.ovl
lkf.nw1 → √bbs.nw1
lkf.nw2 → √bbs.nw2

These routines replace the standard free blocks routine with a custom Lt. Kernal command. They assume the Lt. Kernal is configured as device 8.

The “lkf” merges are intended only for systems running Lt. Kernal DOS 7.1 or later.

Specific System Requirements

@@ Line 1: / Line 1: @@
-[[Specificsystemrequirements|Specific System Requirements]] - <strong>Lt. Kernal HD</strong>
+{{DISPLAYTITLE:Lt. Kernal Hard Drive System}}
+[[Specificsystemrequirements|Specific System Requirements]] – '''Lt. Kernal HD'''
-Xetec's Lt. Kernal Hard Drive system is an excellent choice to run your BBS system on.  It supports up to 9 different partitions of disk space called Logical Units, and each of these units has 15 "users" which are like subdirectories.  This can mean you can have up to 135 separate file directories.  Color 64 will NOT be able to use the Lt. Kernal and RAMDOS at the same time, if you have an REU in configuration with the HD.
+== Lt. Kernal Hard Drive ==
+The Xetec Lt. Kernal Hard Drive system is well suited for running Color 64. It supports up to nine Logical Units (LUs), each containing fifteen “users” that function similarly to subdirectories. This structure allows for as many as 135 distinct storage areas.
-To use the Lt. Kernal HD on the 64, you must have the HIRAM connector hooked up, as described in the Lt. Kernal manual.  If you do not have the HIRAM connection, then the system will not work correctly.  If you are using a Commodore 128 in 64 mode, then the ribbon cable connecting the computer and the Host Adaptor takes care of the HIRAM signal.
+Color 64 cannot use Lt. Kernal and RAMDOS simultaneously if an REU is installed alongside the hard drive.
-Another thing you need to do is run your CONFIGURE program and make sure that the NMI TRAP setting is off (set to 0) for the Commodore 64 mode of the Lt.  Kernal.  If this is not set to 0, then your users may experience "line noise" when calling your system.
+=== Hardware Requirements ===
-And finally, you need to make sure that you answer "Y" to the Lt. Kernal question in your boot-maker program.  If this is not set to "Y", then modem communications will be garbled.
+When operating on a Commodore 64, the HIRAM connector must be properly installed as described in the Lt. Kernal documentation. Without the HIRAM connection, the system will not function correctly.
-Color 64 can access any configuration that you may have in mind through the "ldlu" and "i" drive commands.  The "ldlu" command's syntax is l<device><LU><USER>.  For example, to access LU 2, USER 5 the command would be "l825", assuming you want to use device 8.  For users 10 through 15, you use the hexadecimal equivalent of A through F.  For example, LU 3, USER 11 would be "l83b".
+If you are using a Commodore 128 in 64 mode, the ribbon cable connecting the computer to the Host Adapter automatically handles the HIRAM signal.
-For LU's 2 through 9, you need to add an "i" command to the drive initialization command in setup.  If you wanted to use LU 3, then the command would be "i3".  When both commands are put together, the whole command would look like "l83b!i3", if you wanted to use LU 3, USER 11. Notice that you separate individual disk commands with an "!” exclamation point.
+Run the CONFIGURE utility and verify that the NMI TRAP setting is disabled (set to 0) for Commodore 64 mode. If NMI TRAP is not set to 0, callers may experience line noise during modem communication.
+In the BOOTMAKER program, ensure that you answer “Y” to the Lt. Kernal configuration prompt. Failure to do so may result in garbled modem communication.
-<strong>Faster Disk Access  </strong>
+=== Accessing Logical Units ===
-If your Lt.Kernal HD uses DOS version 7.1 or greater, then you can achieve faster disk access in some of the overlays by merging the following files into the specified overlays.  These merges are optional, so they are not absolutely required for your system to function normally:
+Color 64 accesses Lt. Kernal storage using the “ldlu” and “i” drive commands.
-<ul><li>lkf.init     -> √bbs.init </li>
-<li>lkf.msgs -> √bbs.msgs </li>
-<li>lkf.xfer    -> √bbs.xfer </li>
-<li>lkf.ovl      -> √bbs.ovl </li>
-<li>lkf.nw1   -> √bbs.nw1 </li>
-<li>lkf.nw2   -> √bbs.nw2 </li></ul>
+The syntax for the ldlu command is:
-These routines replace the standard free blocks routine with a custom Lt. Kernal command.  The routines assume that your Lt. Kernal is being used as device 8.  Remember: The "lkf" merges are for systems that use DOS version 7.1 or greater!
+l&lt;device&gt;&lt;LU&gt;&lt;USER&gt;
+Example:
+To access LU 2, USER 5 on device 8:
+l825
+For users 10 through 15, hexadecimal values A through F are used.
+Example:
+LU 3, USER 11 on device 8:
+l83b
+For LUs 2 through 9, you must also include an initialization command in SETUP.
+Example:
+To initialize LU 3:
+i3
+When combined:
+l83b!i3
+Separate individual disk commands with an exclamation point (!).
+----
+=== Faster Disk Access ===
+If your Lt. Kernal uses DOS version 7.1 or later, faster disk access can be achieved by merging optional enhancement routines into specific overlays. These merges are not required for normal operation.
+Merge the following files:
+* lkf.init → √bbs.init
+* lkf.msgs → √bbs.msgs
+* lkf.xfer → √bbs.xfer
+* lkf.ovl → √bbs.ovl
+* lkf.nw1 → √bbs.nw1
+* lkf.nw2 → √bbs.nw2
+These routines replace the standard free blocks routine with a custom Lt. Kernal command. They assume the Lt. Kernal is configured as device 8.
+The “lkf” merges are intended only for systems running Lt. Kernal DOS 7.1 or later.
 [[Specificsystemrequirements|Specific System Requirements]]