![]() ![]() It would have been incredibly inefficient for a 32bit OS (*) to thunk down to 16 bit code to access floppy drives, but given the inherently poor performance of floppies I guess nobody would care. It's possible however that Windows has always relied on the BIOS to support floppy drives, just as DOS did. EFI is just the BIOS, it does not determine what hardware exists. In this case I'm not sure I see what EFI would have to do with it. Here we have access to the source code and the developers, why would we defer to anyone else? We don't accept that any such thing exists. Please be careful about references to external authorities. IMO it would be dumb for VirtualBox to include complex filesystem formatting code for a multitide of OS's and disk types, so I guess it must have template blank disk images stored somewhere, probably in some compacted form (e.g. I see no such option for creating formatted ISOs or hard disk images. (*) AFAIK, VirtualBox supplying a formatted disk is unique to this floppy creation feature. Which of course means it must work in Win10 as well, since the guest OS choice does not determine how the virtual hardware works. I just tested it in XP and it worked fine. Please expand on how did you accomplished that? Edit: I just tried it, and VirtualBox does indeed have a floppy image creation feature which I never knew it had, including choosing the FAT12 format for it (*). I've never heard of VirtualBox creating floppy images. ![]() In this case NTFS looks like some kind of default, since the file actually seems to be located in a network folder? VirtualBox doesn't know or care what filesystems are used inside the guest OS. No, in fact it says that the "floppy.img" file is located on an NTFS drive. One weird thing is that Virtualbox logs the file system of the floppy image as NTFS.
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |