Is there any reason not to edit
***
The (sed) scripts for syslinux2grub4dos need several corrections.
***
I insist that the content of
Just as an example, with the recent changes to UBCD's cfg files (using some relative paths) a similar edition would be needed by someone adding UBCD to a multiboot UFD, IF all files were to be copied to some "/ubcd/" subdirectory (as you do with "/pmagic/").
Moreover, by using this duplicated Syslinux-related files, if PMagic updates its Syslinux version, UBCD 5.2 will fail to chain to it when a user updates pmagic in UBCD.
That's why I already suggested a generic procedure to update pmagic in UBCD (in which, BTW, I forgot to post about the additional boot entries that also point to pmagic's syslinux.cfg).
/boot/syslinux/syslinux.cfg?
***
The (sed) scripts for syslinux2grub4dos need several corrections.
***
I insist that the content of
/pmagic/boot/syslinux/is mostly unnecessary. Pmagic's syslinux.cfg is originally pointing to
/boot/syslinux/, whether explicitely or with relative paths. As in past betas, you have edited the (relative or absolute) paths to point to
/pmagic/boot/syslinux/, and in some cases that's correct (for the message*.txt, for example), but for the syslinux-related files, that path edition is not the best option.
Just as an example, with the recent changes to UBCD's cfg files (using some relative paths) a similar edition would be needed by someone adding UBCD to a multiboot UFD, IF all files were to be copied to some "/ubcd/" subdirectory (as you do with "/pmagic/").
Moreover, by using this duplicated Syslinux-related files, if PMagic updates its Syslinux version, UBCD 5.2 will fail to chain to it when a user updates pmagic in UBCD.
That's why I already suggested a generic procedure to update pmagic in UBCD (in which, BTW, I forgot to post about the additional boot entries that also point to pmagic's syslinux.cfg).