To make things easy, A2CLOUD has commands to “insert” disk image files into the virtual drives:
vsd1 imageFileName will “insert” imageFileName into S2,D1
vsd2 imageFileName will “insert” imageFileName into S2,D2
vsd2 by itself will show you the path to the disk image currently “in” the drive
Note that the disk image you “insert” can be either DOS-ordered or ProDOS-ordered. VSDRIVE will figure it out. The disk doesn’t need to even contain ProDOS, as long as you’re using ProDOS software which can access it — for example, System Utilities can copy files from a DOS 3.3 or Pascal image.
To make new image files, you can transfer real floppy disks from your Apple II using ADTPro. These will arrive in /usr/local/adtpro/disks, which you can also refer to as $ADTDISKS for short; if you have A2SERVER installed, this folder is also available on your network to other computers, so you can use the images you create with an emulator.
Also from another computer, you can copy an image into the ADTDISKS network folder and then insert it into a virtual drive by typing
vsd1 $ADTDISKS/imageFileName. (For virtual drive 2, use
vsd2 instead.) Or you can download disk images from the internet directly on your Pi, which I’ll explain in a later post.
You can always put the A2CLOUD disk image back in virtual drive 2 with:
vsd2 commands create a symbolic link, which is like a Windows shortcut or Mac alias, to whatever file you specify as imageFileName. The symlinks are in /usr/local/adtpro/disks, and are called Virtual.po or Virtual2.po, respectively.)