Can you add these line to /etc/lilo.conf
# Trying to see if Windows NTLDR inside hdc1
other = /dev/hdc1
label = Windows_in_hdc1
# Trying to see if Windows NTLDR inside hdb1
other = /dev/hdb1
label = Windows_in_hdb1
Lilo will check the boot sector of hdc1 and hdb1 for a boot loader and clear it for implementation if it finds one. It will then report something like "Windows_in_hdc1 added".
I suspect between hdc1 and hdb1 one of the two partitions is your first boot disk and will have the necessary files to boot NYLDR. The other one may be just a data-only partition and Lilo will regard it as an error when no boot loader is found inside (thereby Lilo can't boot this alternative) and the configuration will not be implemented. Therefore if any of the hdc1 or hdb1 system is reported as error can you put a "#" in front of each line to disable that booting alternative.
If you do not want to go through the liloconfig everytime you can put Lilo in the MBR of either sda, hdb and hdc. Sda does not appear to be the 1st boot disk and my guess would be hdb. Thus I would try the Bash command on all three disk
lilo -b /dev/hdb
lilo -b /dev/hdc
lilo -b /dev/sda
If Lilo accepts it then it can boot regardless which disk you have arranged with the Bios to boot first.
The Lilo in the MBR can be replaced by MS's MBR as you did before so there is no harm to have Lilo to occupy the MBR of all three disks.
The commmand should compile Lilo's first 512 bytes, include an address to load partition sda3 and place the image in the MBR (first sector of 512 bytes) of the specified disk.
Lastly if you Windows in sda1 relies on NTLDR files in another partition then you must have two MS systems running. The PC boots to the first partition that stores the NTLDR and should show the MS choices available for you to boot. In that circmstance you have no need to boot sda1, just the partition that stores NTLDR.