Available article translations:

How can I use floppy disks in VM?

  • Parallels Desktop 4 for Mac Standard Edition
  • Parallels Desktop 3 for Mac Standard Edition
  • Parallels Desktop 2.x for Mac Standard Edition


Parallels Desktop for Mac supports external USB floppy drives in your guest OS. Just plug the USB drive into your Mac computer, connect it to the virtual machine using the Devices menu on the toolbar, and it will appear in the guest OS as a new USB device.

If your guest OS doesn't support such a USB floppy drive, but you still need to boot the VM using a floppy, you have to create an image file of your floppy disk using the Disk Utility on your Mac and connect that image to the VM’s virtual floppy drive. Here’s how you do it:
  1. In the Finder open Macintosh HD - Applications - Utilities - Disk Utility
  2. Insert the source diskette (the image of which you want to create) into the external USB floppy 3.5 disk drive and connect the device to the idle USB port of your computer.
  3. Select this floppy from the Disk Utility device list.
  4. Click the New Image button on the top of the Disk Utility window. Specify the name and location for the image, then set Image Format to read / write, and Encryption to none.
  5. Click the Save button and wait until the image is created.
  6. Locate the new image, right-click (or Ctrl+click) it, and choose Get Info from the pop-up menu.
    Expand the Name & Extension sectioin, change the file's extension from .dmg to .fdd, press ENTER, and then click the Use .fdd button in the pop-up window.
  7. Launch Parallels Desktop, click the Floppy link in the main window to open Configuration Editor. Select the Connect at startup option and locate the floppy disk image file using the "..." button. Click Save to save changes and then OK to close Configuration Editor. You can also connect the floppy disk image file when the VM is running using the Devices menu in the Mac menu bar.

a9c6e0b6a5209e617a7c0dd5eace86cf 1e5db16426987d561060acdf56d947b4 98236a11050ecbd6a1bb76f41fd05550 d6e04a8c3a7f86de03d4731caa56d4ed 43a4cfd0d39eefbc844fb7740b79a4b9

Was this article helpful?
Tell us how we may improve it.
Yes No