by fsmithred » Sat Sep 06, 2014 11:50 am
Yes, it may be related to that bug. We had to make some changes to refractasnapshot to adjust for changes in syslinux. In the older versions of syslinux, the *.c32 files are in /usr/lib/syslinux. In the newer version (6.0.3) there are three sets of those files, each in a subdirectory of /usr/lib/syslinux/modules. The subdirectories are bios, efi32 and efi64.
I haven't done anything with those files in refracta2usb yet, and I'm not even sure if I need to. What task in refracta2usb did you use to create your parted magic usb? Did you select ISO from the main menu, or did you use one of the tasks from the advanced menu? Boot_ISO or Multiboot from the advanced menu are possible choices.
If the iso is one that was made with refractasnapshot 9.1.2, then the necessary modules are already in the isolinux directory for the live CD. If the iso is from somewhere else, whatever files are needed for booting should be in the isolinux directory. They would get copied into the /syslinux folder on the usb if you used ISO from main menu, and they would go into a different directory (that you get to name) if you use Multiboot. And if you used Boot_ISO, those modules would still be inside that iso file.
Take a look at the end of the Help file in refracta2usb. It shows a few different ways that the directory tree on the usb can be arranged, depending on which task you choose. That might help you understand what I'm talking about. I'll probably need to look at it, too. Then I might have a better idea of what I'm talking about.