OK. As a little side project, I've modified the disk image support a bit:
- sfdimg and normal static disk images now support having a global setting for different sector sizes (still defaulting to 512 bytes, but the data in the header is now effective and changable in new disk images). Software using custom values in said field will now change sector read/write behaviour, as the field is actually used instead of ignored (it used to be assumed to be set to 512 even if it wasn't). If using disk images with non-512 byte sectors on older versions of UniPCemu, they will be written as 512 byte sectors instead, so take caution on using these on newer versions.
Simply said, don't use sfdimg disks with non-512 byte sectors on older versions of UniPCemu, as it will write the data incorrectly on those (although by default it's already set to 512 on creating those disk images).
- Implemented FDI/HDI disk image support on the floppy and ATA hard drive controllers. Non-512 byte sectors will be handled accordingly now with the new support of these formats (as well as on the other formats that didn't support those, like static and dynamic disk images mentioned above).
- Implemented mounting of FDI/HDI disk images. FDI disk images are mounted on floppy disks (filtered actually) and HDI disk images on hard disks. The backend does actually support both on both disk types (when manually editing the SETTINGS.INI file), but the settings menu's own mounting option will only show the fdi in the list of floppy disk drives and hdi on the list of hard disk drives to make management and seperation easier. Both are handled in roughly the same way on the backend, so you can actually rename the files between the two extensions to change from hard disk and floppy disk and vise versa (the file format of both disk types is identical, minus a floppy unused field that isn't emulated, so both types of drives will mount the disk image is requested to). The floppy or hard disk drive controller itself might have problems doing that though (due to interface limitations of sector addressing and LBA addressing support).
The 808x still doesn't boot right now, so that's still to be fixed first for a new release to happen.