Hi,
I burned 32-bit Ubuntu version 16 to a USB and successfully ran it on a 64-bit machine without installing.
This is to be expected as 32 bit Intel code will run on a 64 bit Intel machine as long as you stay in protected mode or go into legacy mode.
I checked the files burned on the USB and saw that under the dists/xenial/main and dists/xenial/restricted folders there is a binary-i386 folder.
This makes sense.
Then, I burned the 64-bit Ubuntu version 16 to a USB.
I checked the files burned on the USB and saw that under the dists/xenial/main and dists/xenial/restricted folders there is a binary-amd64 folder and a binary-i386 folder.
Apparently, the 64-bit version has both the 64-bit code and the 32-bit code.
Why?
What happens if you take the 64-bit version and try to run it on a 32 bit system?
Will the bootloader load the 32-bit version and successfully run the OS?
I burned 32-bit Ubuntu version 16 to a USB and successfully ran it on a 64-bit machine without installing.
This is to be expected as 32 bit Intel code will run on a 64 bit Intel machine as long as you stay in protected mode or go into legacy mode.
I checked the files burned on the USB and saw that under the dists/xenial/main and dists/xenial/restricted folders there is a binary-i386 folder.
This makes sense.
Then, I burned the 64-bit Ubuntu version 16 to a USB.
I checked the files burned on the USB and saw that under the dists/xenial/main and dists/xenial/restricted folders there is a binary-amd64 folder and a binary-i386 folder.
Apparently, the 64-bit version has both the 64-bit code and the 32-bit code.
Why?
What happens if you take the 64-bit version and try to run it on a 32 bit system?
Will the bootloader load the 32-bit version and successfully run the OS?