Actually, it seems that I avoided installing GRUB in the normal install. On the second prompt, I exited to the install menu.

# extlinux --install /boot/extlinux

doesn't work. I get the error:

# extlinux --install /boot/extlinux
/bin/sh: 3: extlinux: not found

----
OK, I think I know where I went wrong. I should have done the following?

# chroot /target /bin/bash
# . /etc/profile 
# mkdir -p /boot/extlinux

Still a problem however:

# extlinux --install /boot/extlinux
bash: extlinux: command not found

@fsmithred Thanks for all the information. I installed Devuan ASCII-RC 64-bit netinstall with LXDE-QT and added the the KXStudio repo and enabled the GCC5 packages. After an apt update and upgrade, I added all of the packages that I could remember from Slackware's Studioware and Ubuntu Studio. Everything looked set to install, until tuxguitar kicked up a broken packages error that Synaptic couldn't recover from:
Unresolved dependencies, bla, bla:

If I get time tomorrow, I will try to complete an install of all of the packages, but as a point of departure, everything else looks good.

BTW, not crazy about LXDE-QT, but I really appreciate the ability to choose login managers during the expert install

$ command not found
# command not found

sxhkd was not in /usr/bin. Something is obviously wrong with the package. I originally had problems with so called "documentation", but I thought that I had overcome the problem. I tried re-cloning the git but all of a sudden, git was no longer installed (I didn't uninstall it) I tried reinstalling gcc and xcb, which also pulled in some dependencies that were not installed last time around for some reason. I cloned the git and then ran "make" but got some errors about missing lib.something.so files. I am not sure that sxhkd can be compiled under Devuan. I therefore gave up, and installed a .deb package that I had compiled under Ubuntu 16.04 before I eschewed systemd. Most things seem to be running as expected now (hot keys), but I have come across a weird quirk (only) when I try starting geany (installed with apt-get) from Dmenu:

Configuration directory could not be created (Permission denied). There could be some problems using Geany without a configuration directroy. Start Geany anyway?

As it is, I have had to create a ~/.local and a ~/.local/share share directory manually, as well as a ~/.config/leafpad directory, for some reason, which I do not understand as I had none of these problems with missing directories when I installed i3wm using the same method.

I followed the instructions and reduced my .xinitrc file to the following:

sxhkd &
lxterminal &
exec bspwm

The terminal fills the entire space (as it should), but I can't get any response from my hot keys, even when quitting the terminal. I compared the permissions for sxhkdrc on my Devuan install to the Slackware version and they are the same. I am at a loss as to why the hot keys aren't working.

Nice to hear from you MiyoLinux. I don't see any obvious candidate as you describe. The /etc/slim.conf file doesn't have any WMs listed at all and no obvious "session" candidates. This appears to be for setting the default shell:

login_cmd           exec /bin/bash -login /etc/X11/Xsession %session

Alternatively, there is:

sessionstart_cmd	some command

but the description states:

This seems to me a more likely candidate as it seems to interact with .xsession, but then again, I could be completely off.

Thanks. "nomodeset" worked. Unfortunately, the Nvidia installer wants a libc development package that I can't find. I tried libc6-dev, but Synaptic reports that it is a broken package for some reason. Any ideas?
----
Found it, I was missing libc6-dev. Thanks again.

Which is important on a computer like mine, where the /dev/sdX1 path changes, depending on (apparently) the BIOS's view of the situation.

I tried changing it to:

image=/media/username/9d2c1561-d6d7-4651-9373-bcd440c289dd/boot/vmlinuz

Unfortunately, there was some sort of panic during boot up:
"EOI panic+0x1b7/0x1f0
(...)
3.762164 -[end trace 6e0a640ecf8d150a]---"

I finally got a lilo.conf file to look at, in my case from a Salix OS install. The file seems to be able to be divided into three parts. The most important (bottom) appears to be the actual boot instructions, which I have attempted to modify for my setup:

# Linux bootable partition config begins
image = /boot/vmlinuz
# root = /dev/sda1
  root=UUID="cca59513-f81b-4cbd-9814-e72a3c6b3dfb"
  label = Devuan
  read-only
# Linux bootable partition config ends
# Linux bootable partition config begins
image = /boot/vmlinuz
# root = /dev/sdd1
  root=UUID="bfb77a63-55ab-4552-a3ac-72ab9277ad82"
  label = Salix
  read-only
# Linux bootable partition config ends
# Windows bootable partition config begins
other = /dev/sda1
  label = Windows
# table = /dev/sdc
  table=UUID="E6BCC326BCC2F05B"
# Windows bootable partition config ends

The next most important appears to be at the very top, telling lilo where to start lilo from:

# LILO configuration file
# generated by 'liloconfig'
#
# Start LILO global section
# Append any additional kernel parameters:
append="quiet  vt.default_utf8=1"
boot = /dev/sda

Next comes VGA configuration. This will have to be something generic as my NVIDIA driver/blob thingy kicks in later. I think the current setting should be safe:

# Standard menu.
# Or, you can comment out the bitmap menu above and 
# use a boot message with the standard menu:
#message = /boot/boot_message.txt

# Wait until the timeout to boot (if commented out, boot the
# first entry immediately):
prompt
# Timeout before the first entry boots.
# This is given in tenths of a second, so 600 for every minute:
timeout = 50
# Override dangerous defaults that rewrite the partition table:
change-rules
  reset
# VESA framebuffer console @ 1024x768x64k
vga = 791
# Normal VGA console
# vga = normal
# VESA framebuffer console @ 1024x768x64k
# vga=791
# VESA framebuffer console @ 1024x768x32k
# vga=790
# VESA framebuffer console @ 1024x768x256
# vga=773
# VESA framebuffer console @ 800x600x64k
# vga=788
# VESA framebuffer console @ 800x600x32k
# vga=787
# VESA framebuffer console @ 800x600x256
# vga=771
# VESA framebuffer console @ 640x480x64k
# vga=785
# VESA framebuffer console @ 640x480x32k
# vga=784
# VESA framebuffer console @ 640x480x256
# vga=769

Lastly comes the appearance. It would be nice with some purpy goodness with logo, but not sure how to configure that. Here is the stock code:

# Boot BMP Image.
# Bitmap in BMP format: 640x480x8
  bitmap = /boot/salix.bmp
# Menu colors (foreground, background, shadow, highlighted
# foreground, highlighted background, highlighted shadow):
  bmp-colors = 12,0,10,0,9,9
# Location of the option table: location x, location y, number of
# columns, lines per column (max 15), "spill" (this is how many
# entries must be in the first column before the next begins to
# be used.  We don't specify it here, as there's just one column.
  bmp-table = 5,6,1,16
# Timer location x, timer location y, foreground color,
# background color, shadow color.
  bmp-timer = 70,6,14,0

However, before I install Lilo or make the necessary changes to the /etc/lilo.conf file, I will need to run:

$ sudo apt-get purge grub2-common grub-pc grub-pc-bin

and

# dd if=/dev/zero of=/dev/sda bs=446 count=1

Am I on the right track?