The Official OpenVix image for the MIO has been released (see link below).
http://www.openvix.co.uk/index.php/d...ion-os-mio-4k/
The OpenVix image is OE Alliance based.
OE Alliance based images are packing the regular emmc.img file and the rootfs.tar.bz2 file in the same folder. I do not know why they do this, but I guess they do it so the download will work as the main or install image, and also work as the multiboot image. Doing it this way makes for a big download, but maybe having one download instead of two like the Pli images have makes for less confusion?
If you want multiboot, the emmc.img may be deleted, and the splash.bin files may be deleted form this folder.
If you want to use OpenVix as the main image, then the rootfs.tar.bz2 file may be deleted.
If you do not want to see the OpenVix logo for every boot on the other images that are stored in the receiver, then delete the splash.bin file too.
I do not think many MIO users have seen the Edision boot logo because OpenATV writes over it with the splash.bin file. The only problem with that is you see OpenATV logo on every boot for all images in multiboot.
The OS Mio is capable of reading both NTFS Windows type file systems, and Linux type file systems. My usb drives for image file loading are formatted to be used in any operating system, Windows or Linux.