search for: comboot16

...;dosutil/eltorito.txt' should be also > > copied to 'bios/dosutil/' when building. It's a binary object in the source tree. The closest alternative is to try copying to the bios/ path. > I am adding one more: > > _ If I am not mistaken, bios/memdump/memdump.com is a comboot16 > module(?). If this module is still relevant in 6.xx (which I don't > really know), I wonder whether perhaps there should be a better > location to the /memdump/ (sources of memdump.com) directory. Likely needs to be pruned considering ver.com and hexdump.c32 as you mentioned. --Gen...

...; Isn't this binary file built from 'mdiskchk.c' located in the same directory? Evidently I lack the knowledge to understand why this is so different from other binary files. > > I am adding one more: > > > > _ If I am not mistaken, bios/memdump/memdump.com is a comboot16 > > module(?). If this module is still relevant in 6.xx (which I don't > > really know), I wonder whether perhaps there should be a better > > location to the /memdump/ (sources of memdump.com) directory. > > Likely needs to be pruned considering ver.com and hexdump.c32...

In Syslinux 6.03-pre6: _ The txt/html/*.html files are currently created 3 times, one for each firmware. I think they should be created only once (under the main txt/html/ directory), just as the rest of the documentation is. In that case, the <respective_firmware>/txt/html/ subdirectories should not even be created. _ The bios/dosutil/ directory contains copybs.com and eltorito.sys,

...il/ > subdirectory, just as copybs.com and eltorito.sys are. I am unsure > whether 'dosutil/README' and 'dosutil/eltorito.txt' should be also > copied to 'bios/dosutil/' when building. I am adding one more: _ If I am not mistaken, bios/memdump/memdump.com is a comboot16 module(?). If this module is still relevant in 6.xx (which I don't really know), I wonder whether perhaps there should be a better location to the /memdump/ (sources of memdump.com) directory. TIA, Ady.