I'm using a 16GB CF, which has a first FAT32 partition and from that I was booting AntiX Live, using grub4dos and an entry like

kernel /linux/AntiX/vmlinuz blah blah
initrd /linux/AntiX/initrd.gz

So with that booting, I installed it to the CF. The rest of the CF is a Logical/Extended partition, with the first (sda5) another FAT32 partition, then I used gparted to create a 4GB root (sda6), 530MB Swap and 1GB home in the remainder.

Now I didn't want to mess up my existing g4d menu.lst, so I skipped that step when installing AntiX. Now I need to create an entry to boot the installed AntiX instead of the Live one. I looked in /boot/grub and found an example menu.lst, so copied that and edited it appropriately, so I've got

root (hd0,5)
kernel /boot/vmlinuz-3.5.1- blah blah (I can't remember the exact line but I only edited the version number, which was 3.3.1 in the example)
initrd /boot/initrd-3.5.1.gz

Now it starts to boot but then I see an error about sdb1 and then it says it can't find root and to check root= and drops me to the commandline. The example entry did say"title Boot Antix on sdb1" but I only have the single CF card so there's no sdb1 (as the version number was wrong as well, I didn't worry about this much and assumed it wasn't meant to be correct for my system, until I saw the error referring to sdb1 when booting).

So any assistance to fix it would be gratefully received (even if I have to start again!)

Ah, ignore me! Just noticed there's a root=/dev/sdb1 in the commandline __{{emoticon}}__