Similarly, floppy1 is backed by floppy_b.flp created in the same way. I have floppy0 configured to be backed by a simple file floppy_a.flp, created for me by WS using the "Create." button in the WS Floppy Drive UI. Also check that the icons for the A: and B: drives in My Computer have little 5.25' and 3.5' floppies respectively. Make sure the BIOS has both A: and B: drives configured correctly. I can power-cycle the VM and the data are still intact on their respective disks afterwards (verified again using "dir a:" and "dir b:" and examining the volume label). It probably confused about what type the drive is, thinking its either a 1.2 MB 5.25' drive or a 3.5' drive. With the aforementioned MS-DOS 6.22 VM (and with the second FDD configured in BIOS setup), I can successfully "format a:" and give it a label (FLOPPY_A), then "format b:", give it a different label (FLOPPY_B), and "dir a:" will show the contents of the first floppy and "dir b:" will show the contents of the second floppy. Floppy drives are very much non-plug-and-play like that. I've tested an MS-DOS 6.22 VM with Workstation 9.0.1 (build 894247) on both a Debian 6.0 amd64 host and a Windows XP Pro SP3 host, and could not reproduce your findings.ĭid you go into the VM's BIOS and configure the second floppy drive? If you don't do that, MS-DOS goes into its crusty old "pretend we have two floppy drives when there's really only one" mode, you'll get occasional prompts to "Insert diskette for drive B: and press any key when ready", and all reads/writes will go to the first virtual floppy disk device.
0 kommentar(er)
