Dual boot is hard. Dual boot on 2 different drives is harder. So do not feel bad. I started using linux on a IBM 390E.
It was a Linux dedicated laptop. Same on a Compaq 1540DM my wife gave me with Windows 95 on it.
Linux was a lot harder to learn then than now. Just my opinion.
What I am trying to say I guess. If you ever decide to try Linux-Lite again. Try it on a dedicated cheap linux laptop and learn linux that way. Then you may have something click in your head later for dual booting. Plus. How certain steps work like md5sum and such.
Here is a old example of my mutiboot dual drive boot config on a desktop computer that died from old age. A IBM Netvista.
Code:
# menu.lst produced by grub4dosconfig-v
color white/blue black/cyan white/black cyan/black
timeout 10
default 0
# Frugal installed Puppy
title Bruno pup-431 (sdb1/pup431)
find --set-root --ignore-floppies /pup431/initrd.gz
kernel /pup431/vmlinuz pmedia=atahd psubdir=pup431 pfix=fsck
initrd /pup431/initrd.gz
title Bruno pup-431 (sdb1/pup431) RAM mode\nBoot up Puppy withot pupsave
kernel /pup431/vmlinuz pmedia=atahd psubdir=pup431 pfix=ram,fsck
initrd /pup431/initrd.gz
title Macpup-511 (sda1/puppy511harry)
find --set-root --ignore-floppies /puppy511harry/initrd.gz
kernel /puppy511harry/vmlinuz pmedia=atahd psubdir=puppy511harry pfix=fsck
initrd /puppy511harry/initrd.gz
title NOP pup-431 (sdb2/puppy431)
find --set-root --ignore-floppies /puppy431/initrd.gz
kernel /puppy431/vmlinuz pmedia=atahd psubdir=puppy431 pfix=fsck
initrd /puppy431/initrd.gz
# Full installed Linux
title antiX at sdb7, kernel 2.6.36-1-mepis-smp
root (hd1,6)
kernel /boot/vmlinuz-2.6.36-1-mepis-smp root=UUID=e8710ae6-9aed-40ce-a34f-9f3f87b758c1 nomce quiet nosplash nouveau.modeset=0 vga=788
initrd /boot/initrd.img-2.6.36-1-mepis-smp
boot
title Debian GNU/Linux, kernel 2.6.38-3.dmz.1-liquorix-686
root (hd0,6)
kernel /boot/vmlinuz-2.6.38-3.dmz.1-liquorix-686 root=UUID=215cde80-eeb6-451f-929f-5fb9493e7932 nosplash quiet nomodeset nouveau.modeset=0
initrd /boot/initrd.img-2.6.38-3.dmz.1-liquorix-686
title Debian GNU/Linux, kernel 2.6.38-3.dmz.1-liquorix-686 (init-3)
root (hd0,6)
kernel /boot/vmlinuz-2.6.38-3.dmz.1-liquorix-686 root=UUID=215cde80-eeb6-451f-929f-5fb9493e7932 nosplash quiet nomodeset nouveau.modeset=0 3
initrd /boot/initrd.img-2.6.38-3.dmz.1-liquorix-686
title Debian GNU/Linux, kernel 2.6.37-0.dmz.5-liquorix-686
root (hd0,6)
kernel /boot/vmlinuz-2.6.37-0.dmz.5-liquorix-686 root=UUID=215cde80-eeb6-451f-929f-5fb9493e7932 nosplash quiet nomodeset nouveau.modeset=0
initrd /boot/initrd.img-2.6.37-0.dmz.5-liquorix-686
title Debian GNU/Linux, kernel 2.6.37-0.dmz.5-liquorix-686 (init-3)
root (hd0,6)
kernel /boot/vmlinuz-2.6.37-0.dmz.5-liquorix-686 root=UUID=215cde80-eeb6-451f-929f-5fb9493e7932 nosplash quiet nomodeset nouveau.modeset=0 3
initrd /boot/initrd.img-2.6.37-0.dmz.5-liquorix-686
title Debian GNU/Linux, kernel memtest86+
root (hd0,6)
kernel /boot/memtest86+.bin
title Quirky 120 (sda8/boot)
uuid 31821294-4cdf-49ff-b5f6-f6f05beb1b66
kernel /boot/vmlinuz root=/dev/sda8
# Windows
# this entry searches Windows on the HDD and boot it up
title Windows\nBoot up Windows if installed
errorcheck off
find --set-root --ignore-floppies --ignore-cd /bootmgr
chainloader /bootmgr
find --set-root --ignore-floppies --ignore-cd /ntldr
chainloader /ntldr
find --set-root --ignore-floppies --ignore-cd /io.sys
chainloader /io.sys
errorcheck on
# additionals
title Find Grub2\nBoot up grub2 if installed
find --set-root --ignore-floppies --ignore-cd /boot/grub/core.img
kernel /boot/grub/core.img
title Grub4Dos commandline\n(for experts only)
commandline
title Reboot computer
reboot
title Halt computer
halt
It took me some time to learn how to do this. It was not a few day endeavor. But was a long road traveled learning things like learning to be bilingual. You cannot learn another language in a few days. Same can said for learning linux proficiently.
So no biggy from me. I understand.
Happy trailz, Rok.
