Search

Language:  
Search for:

Available article translations:

Using floppy disks in VM

APPLIES TO:
  • Parallels Desktop 4 for Mac
  • Parallels Desktop 3 for Mac
  • Parallels Desktop 2.x for Mac

Resolution

Parallels Desktop for Mac supports external USB floppy drives in your guest OS. Just plug the USB drive to your Mac computer, connect it to the Virtual Machine using "Devices" menu on the menubar and it should be showed up in the guest OS as new USB device.

If your guest OS doesn't support USB floppy drive or you need to boot VM from floppy, you need to create an image file of your floppy disk at the MacOS X computer and connect it to the VM as virtual floppy drive:

  1. Open "Finder" -> "Applications" -> "Utilities" -> "Disk Utility".
  2. Insert source diskette from which the FDD image should be created into the External USB Floppy 3.5 disk drive and connect the device to the idle USB port of your computer.
  3. Select that floppy from the "Disk Utility" device list.
  4. Press "New Image" button on the top of the Disk Utility window. Select name and location for the image and set "Image Format" and “Encryption” to “read / write" and “none” respectively.
  5. Press "Save" button and wait for the image creation process to finish.
  6. Locate your created image, right-click on it (or Ctrl+click) and select "Get Info" option from the pop-up menu.
    Expand "Name & Extension" section, change file's extension from ".dmg" to ".fdd", press ENTER, then press “Use .fdd” button in the pop-up window.
  7. Launch Parallels Desktop for Mac, click on the "Floppy" link in the Parallels Desktop window, check "Connect at startup" option and specify the floppy disk image file using "..." button. Hit "OK" to close Configuration Editor. Or you can connect floppy disk image file when VM is running from the "Devices" menu on the Mac menubar or using the icon in the status bar.



6c0bc137413ef2b485c9418f5dd9403a 1e5db16426987d561060acdf56d947b4 33c4522b6fa9ca8e050f19b889fb58f1 279e509e1fbdf7d3ff4adbfcc21d2666 add78cd663c4b3736f2c866e82d5ef12

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