You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the issue
Upon reading the documentation on QEMU website, -fda/fdb is deprecated, so the way to go now is:
-drive file=file,index=0,if=floppy
But when I use UTM's gui to mount it, the command is mounted a bit different:
hence none of my images are being read from a floppy drive and DOS fails to read it (FAIL ON INT24). These images were checked and have no issues loading on other emulators such as 86box and DOSBox.
When I used the command above from the QEMU documentation, a simple MS-DOS 6.22 boot disk was read:
-drive file=Disks/dos622.img,index=0,if=floppy
Which mounts it on drive A. For drive B, you just use index=1
Just mounted the floppy the way I described on both vanilla QEMU and UTM (manually adding the parameter), booted DOS and ran a dir a:. The contents of the floppy were listed.
The issue is present even when I used a Windows 98 SE virtual machine. Windows couldn't read the data, saying the drive was inacessible.
Configuration
UTM Version: 4.0.2 Beta
macOS Version: macOS Monterey 12.5.1
Mac Chip (Intel, M1, ...): MacBook Air M1 16GB/512GB (2020)
The text was updated successfully, but these errors were encountered:
Describe the issue
Upon reading the documentation on QEMU website,
-fda/fdb
is deprecated, so the way to go now is:But when I use UTM's gui to mount it, the command is mounted a bit different:
hence none of my images are being read from a floppy drive and DOS fails to read it
(FAIL ON INT24)
. These images were checked and have no issues loading on other emulators such as 86box and DOSBox.When I used the command above from the QEMU documentation, a simple MS-DOS 6.22 boot disk was read:
Which mounts it on drive A. For drive B, you just use
index=1
Just mounted the floppy the way I described on both vanilla QEMU and UTM (manually adding the parameter), booted DOS and ran a
dir a:
. The contents of the floppy were listed.The issue is present even when I used a Windows 98 SE virtual machine. Windows couldn't read the data, saying the drive was inacessible.
Configuration
The text was updated successfully, but these errors were encountered: