Jump to content

- - - - -

Qemu only recognizes Floppy 1440kb format and not smaller 360kb images?!

  • Please log in to reply
1 reply to this topic

#1 davidm71

  • Members
  • 5 posts
    United States

Posted 12 March 2018 - 09:53 PM


I am trying to create Fat12 images of various sizes using MTools (MFormat) and if the file size of the image is less than 1.44 mb Qemu -fda or -device if floppy fails to recognize the disk image! Will work as an Hda image though. My best guess is that the disk characteristics become non-standard and confuses Qemu. Not sure what is the best way to format the image to get the characteristics needed to be accessed by a PnP option rom as an emulated drive. Using Qemu for time being to test out the code but eventually will have to go much smaller than 1.44 mb!


#2 Wonko the Sane

Wonko the Sane

    The Finder

  • Advanced user
  • 15465 posts
  • Location:The Outside of the Asylum (gate is closed)

Posted 13 March 2018 - 10:38 AM

Maybe the issue is not with Qemu, but rather with the BIOS it uses.


When it boots the VM uses the hardware that is recognized by the (virtual) BIOS.


The floppy driver in itself does support various formats:


including the 360 Kb


Depending on the Qemu version, it will normally use either SeaBios or PC-Bios, it is possible that the one (or the other) doesn't support that size/format:




Cannot say specifically how to solve the issue, but I believe you can use the 1.44 Mb size for development and then *somehow* have the thing loaded as option ROM "directly", similarly with what is done for PxE ROM's and similar, example:



Also maybe it depends on the specific build/version of Qemu. :unsure: , older versions used the BOCHS BIOS, and for some formats an ooption "-no-fd-bootchk" was needed, if I recall correctly.




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users