nothing really useful from this direction I'm afraid
I've steered well away from third party bootloaders after experimenting back in the Win9x days and discovering that they don't simply work "out of the box"
I much prefer to have a single OS on machine.......however I guess thats easy when you have eight machines to play with
In this case, I'd hazard a guess that the issue is that the bootloader has created a folder which is "superprotected" and cannot be accessed directly. It has to be edited using the supplied tools. I've seen it before on the software I played with years ago. Essentially in that, the various OS bootloaders were locked away into a protected folder and copied to the root of the C: drive as/when an OS was selected. The protection was there to stop root kits - and simple file corruption. In essence on every boot, you were guaranteed a clean bootloader
I suspect - don't know - that you're coming across something similar here. You need to find the correct tools to edit the folder