Ok, first thing you don't (shouldn't) use a pre-made menu.lst entry when experimenting, but rather use command line as in this way you have direct feedback from commands.
Disk numbers (hd0), (hd1), etc. are assigned by BIOS, so if grub4dos sees it as (hd1) it means that it is (as seen by BIOS) second disk.
The volume being ",4" means that it is the first logical volume in the Extended partition, I presume this is pretty much normal for a Linux install.
The fact that you see it as "first" partition doesn't mean that it is the first partition.
The first primary partition (actually the primary partition in first MBR partition table slot) is (hdn,0)
The second primary partition (actually the primary partition in second MBR partition table slot) is (hdn,1)
The third primary partition (actually the primary partition in third MBR partition table slot) is (hdn,2)
The fourth primary partition (actually the primary partition in fourth MBR partition table slot) is (hdn,3)
The first logical volume inside Extended (no matter in which MBR partition table slot is the Extended partition) is (hdn,4)
The second logical volume inside Extended (no matter in which MBR partition table slot is the Extended partition) is (hdn,5)
You will need to learn some grub4dos basics, the guide is a bit outdated, but the fundamentals remain the same:
It is advised to download either the .chm or the .htm version:
GRUB2 way of booting uses NOT the bootsector at all, part of the GRUB2 code is written to the MBR (+a number of following sectors) and it chainloads directly the GRUB2.
So, back to work.
1) check the contents of \boot\grub\grub.cfg
2) there must be an entry *like*:
linux <something containing "vmlinuz"> <parameters>
3) immediately followed by an entry *like*:
initrd <something containing "initrd">
the <something containing "vmlinuz"> is /boot/vmlinuz-5.5.0-kali2-amd64 or /vmlinuz
the <something containing "initrd"> is /boot/initrd.img-5.5.0-kali2-amd64 or /initrd.img
/vmlinuz should be a symlink to /boot/vmlinuz-5.5.0-kali2-amd64
/initrd.img shuld be a symlink to /boot/initrd.img-5.5.0-kali2-amd64
What is really-really needed is the <parameters>, an installed Kali Linux most probably will need a "root" parameter and a pointer to /install/initrd.gz (or maybe not), *like*:
echo 'Loading Linux 4.0.0-kali1-amd64 ...'
linux /boot/vmlinuz-4.0.0-kali1-amd64 root=UUID=5b71b454-853f-4724-a995-599c871cd5af ro single initrd=/install/initrd.gz
echo 'Loading initial ramdisk ...'
Then you get to grub4dos, press "c" to get to the command prompt and try typing the commands:
find --set-root %mykernel%
kernel %mykernel% root=UUID=%myUUID% ro initrd=/install/initrd.gz quiet
The red bolded part are the parameters that you MUST get from the grub.cfg, maybe they are correct maybe they are different, no way for me to know.