@gmc
Hi, there are two suspects here: the configuration file (/netboot/udhcpd.conf) and the busybox applets (dhcp and tftp programs).
1. You need a good config file; try to google for dhcpd options like:
option tftp 192.168.1.65
boot_file /netboot/pxelinux.0different syntax!
2A. see the individual commands inside the tc-terminal-server script; then in a aterm (terminal) run each of them, one by one, manually (eventually with debug parameters); write down the error messages and look up for them on the internet.
2B. grab a NEW busybox, not from Tinycore, preferably statically linked, just for testing that the OLD applets are not the buggy ones.
(sample:
http://www.busybox.net/downloads/binaries/latest/ )
or build /compile one yourself (in few minutes), from a git/ snapshot one;
Remarks: I hope you did check that you do not run two (or many more) dhcpd or tftp demons (servers) simultaneous.
When you run tc-terminal-server script, it dynamically create a configuration file AND it starts the two servers; this means tc-terminal-server script will OVERWRITE your manual edited configuration. So first understand how tc-terminal-server works. Then after killing the servers from memory (use top / htop), try to mimic yourself what tc-terminal-server script did. When a dhcpd server is running, it has already read its configuration (/netboot/udhcpd.conf) so you need to kill it and start it again to read your new config.
TC is about learning yourself; If it is too demanding for you and it does not worth the effort, I advise you to wait until TC 5.0 will be issue and maybe busybox is updated/corrected. Or just use another combination of dhcp+tftp for PXE booting.
All the best.