The MBR code comes out in one of many attempts, Installing AROS on pendrivers or external USB HDs is not a problem for me, watch my two attached videos:
You keep writing in riddles my friend
I have watched those videos and they are (more or less) showing what i also do to prepare a pendrive. The only thing that i can see is in that in one of those video's you explicitly specify the size of the work partition (which i do not specify for the sake of keeping the process as clean as possible), and in the other you have an addition fat partition. Both can (under certain conditions) influence the boot-process.
Unfortunately neither of those two video's show me the actual native boot-process where you experienced a MBR boot-error. Neither am i able to see in those video's what the AROS installer actually created on the pendrive when you finished the installer (how does the partition (or partitions) look like after installation, for example by viewing the layout, for example, with (g)parted.
What I would like to do is what RUFUS or other programs do to "burn" an ISO
Yes, i understand that you wish to have such a thing but, that won't help you when you experience a MBR boot-error when you boot either an external HD (connected through usb) or pendrive native on your machine, simply because the root cause for your experienced error will not be taken away with software like RUFUS.
Tools like RUFUS are highly overrated, and can't currently be used with AROS. I am investigating how to create a hybrid grub ISO that works for all circumstances, but unfortunately is a slow process for me at the moment. In theory a correct created hybrid ISO can be 'burned' to a pendrive and boot AROS as intended.
I have enough experience on AMiGA OS and AROS OS and I think I've done all the possible tests, maybe my Pendrivers are not suitable at hardware level !
I have literally tried with the cheapest of the cheapest of pendrives (not fake ones though), and i only experienced one failure with an Integral pendrive. Once AROS was finished with installing grub the pendrive was completely ruined, and there was not a tool in the world that was able to resurrect the pendrive. This was not caused by AROS but due to faulty system logic that was present on the pendrive).
It was just broken so, i returned it to the store. I was lucky there because the store had just started selling Integral hardware and as a result were very keen on keeping their (and Integral's) reputation high, so if i could show them my pendrive was literally broken i could swap it for another one. I declined that swap offer, and explained to them that i had lost many valuable files (AROS is very valuable to me
) because of the integral pendrive being faulty and so they offered me a refund and some hush-hush-money (which i accepted).
But, the real issue here for you is that if you claim that you experience a MBR boot-error code, that this can be related to many other factors that you probably did not already consider. For example, even if the hardware i test is reluctant to boot AROS, i then literally tear out all hardware that is able to influence things, flash a custom BIOS or otherwise.
Another reason for me to think there goes something wrong at your end is that (if i remember correctly) you wrote that you experienced the MBR boot error-code on different machines. You could of course be very unfortunate in the choice of your hardware, but i personally do not believe in such coincidence.
So that leaves only one route to take, and that is to figure out what exactly goes wrong at your end. A "It does not work", is not a valid option/reason in my book
